{"thread":{"id":"41914","subject":"[ANNOUNCE] Git v2.8.1 (and call-for-help to \"make rpmbuild\" users)","startedAt":"2016-04-03T19:21:49Z","lastAt":"2016-04-05T10:39:52Z","messageCount":3,"participants":["Junio C Hamano","Michael J Gruber","Elia Pinto"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"282570","messageId":"xmqqtwjiebw2.fsf@gitster.mtv.corp.google.com","threadId":"41914","inReplyTo":null,"subject":"[ANNOUNCE] Git v2.8.1 (and call-for-help to \"make rpmbuild\" users)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2016-04-03T19:21:49Z","receivedAt":"2016-04-03T19:21:49Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"If you do not build RPM binary packages from our pristine source,\nyou can safely ignore this release and stop reading this message.\n\nNow that the audience of this message has been limited to a narrow\ntarget, before I make an announcement, here is a call-for-help to\nyou.\n\nGit v2.8 removed README file and added a corresponding README.md\nfile.  The change however did not adjust git.spec.in that still\nreferred to README, causing \"make rpmbuild\" to fail.  The breakage\nwas not noticed by anybody who tested v2.8.0-rc0 and later release\ncandidates, and ended up in the final v2.8 release, and we saw a\nhandful of bug reports on the list after the release happened.\n\nThis maintenance release is to correct this bug for those who run\n\"make rpmbuild\". It has no other changes.\n\nIt is clear that nobody who relies on being able to \"make rpmbuild\"\never tried any of the 5 release candidate snapshots that happened\nduring Feb 26-Mar 28.  We had a whole month and nobody noticed?\n\nThis incident clearly shows that something needs to happen, if\npeople want \"make rpmbuild\" to keep working.  Even though this\nmaintenance release may fix this single bug, breakages similar to it\nthat only affect \"make rpmbuild\" users are guaranteed to appear in\nfuture releases, unless those who can prevent them from happening\nstart helping to test at least release candidate snapshots.\n\nIt is even more preferrable if they can test the tip of 'next'\nbranch regularly, in order to prevent such breakages from hitting\nthe 'master' branch to be included in the next release, which is\nwhat the other parts of the system aims at.\n\nThe other obvious option is for us to stop pretending that \"make\nrpmbuild\" does anything useful to do and drop the build target and\nthe unmaintained git.spec.in file on which nobody in the active\ndevelopment community keeps eyes.  I do not mean this as a threat\n\"help us or else\"; there is a precedent.  We used to ship our own\ndebian/rules and friends for those who wanted to debbuild from the\nsource, but the Debian packagers wanted to have their own proper\nones and ours ended up confusing the users, and we made the world\na better place by removing our copy.  If \"make rpmbuild\" people want\nus to take this route, that is also OK for us.\n\nSo that's the call for help.  Now to the announcement.\n\nThe latest maintenance release Git v2.8.1 is now available at\nthe usual places.\n\nThe tarballs are found at:\n\n    https://www.kernel.org/pub/software/scm/git/\n\nThe following public repositories all have a copy of the 'v2.8.1'\ntag and the 'maint' branch that the tag points at:\n\n  url = https://kernel.googlesource.com/pub/scm/git/git\n  url = git://repo.or.cz/alt-git.git\n  url = git://git.sourceforge.jp/gitroot/git-core/git.git\n  url = git://git-core.git.sourceforge.net/gitroot/git-core/git-core\n  url = https://github.com/gitster/git\n\n----------------------------------------------------------------\n\nGit v2.8.1 Release Notes\n========================\n\nFixes since v2.8\n----------------\n\n * \"make rpmbuild\" target was broken as its input, git.spec.in, was\n   not updated to match a file it describes that has been renamed\n   recently.  This has been fixed.\n\n----------------------------------------------------------------\n\nChanges since v2.8.0 are as follows:\n\nJunio C Hamano (1):\n      Git 2.8.1\n\nMatthieu Moy (1):\n      git.spec.in: use README.md, not README\n"},{"id":"282692","messageId":"57038A24.2030808@drmicha.warpmail.net","threadId":"41914","inReplyTo":"xmqqtwjiebw2.fsf@gitster.mtv.corp.google.com","subject":"Re: [ANNOUNCE] Git v2.8.1 (and call-for-help to \"make rpmbuild\" users)","fromName":"Michael J Gruber","fromEmail":"git@drmicha.warpmail.net","sentAt":"2016-04-05T09:49:24Z","receivedAt":"2016-04-05T09:49:24Z","isPatch":false,"sender":{"key":"git@grubix.eu","avatar":"https://avatars.githubusercontent.com/u/233215?v=4"},"body":"Junio C Hamano venit, vidit, dixit 03.04.2016 21:21:\n> If you do not build RPM binary packages from our pristine source,\n> you can safely ignore this release and stop reading this message.\n> \n> Now that the audience of this message has been limited to a narrow\n> target, before I make an announcement, here is a call-for-help to\n> you.\n> \n> Git v2.8 removed README file and added a corresponding README.md\n> file.  The change however did not adjust git.spec.in that still\n> referred to README, causing \"make rpmbuild\" to fail.  The breakage\n> was not noticed by anybody who tested v2.8.0-rc0 and later release\n> candidates, and ended up in the final v2.8 release, and we saw a\n> handful of bug reports on the list after the release happened.\n> \n> This maintenance release is to correct this bug for those who run\n> \"make rpmbuild\". It has no other changes.\n> \n> It is clear that nobody who relies on being able to \"make rpmbuild\"\n> ever tried any of the 5 release candidate snapshots that happened\n> during Feb 26-Mar 28.  We had a whole month and nobody noticed?\n> \n> This incident clearly shows that something needs to happen, if\n> people want \"make rpmbuild\" to keep working.  Even though this\n> maintenance release may fix this single bug, breakages similar to it\n> that only affect \"make rpmbuild\" users are guaranteed to appear in\n> future releases, unless those who can prevent them from happening\n> start helping to test at least release candidate snapshots.\n\nIn RedHat/Fedora land, we use our own spec files, \"make\" and \"make\ninstall\" into a special purpose tree and package that.\n\nE.g. in fedora, the packager noticed the README file name change in\n2.8.0, adjusted the corresponding \"%doc\" line, and that was basically\nall besides updating the sources.\n\nAs a fedora user, I either use rpms targetting fedora (possibly patched\nand rebuilt by myself), or I build from sources (--prefix=$HOME). With\n\"generic\" rpms you never know which guidelines they follow or where they\ninstall to. Also, naming schemes for dependencies may differ between\nRedHat land, SuSe land and other rpm based distros.\n\nSo, just like in the deb case, I'm wondering if there's a use case for\nmake rpmbuild in git.git.\n\nMichael\n"},{"id":"282695","messageId":"CA+EOSBndKHN1xR-iyyJQongSQJ7++BBjO3WtKK=g7Ki_A47E9A@mail.gmail.com","threadId":"41914","inReplyTo":"xmqqtwjiebw2.fsf@gitster.mtv.corp.google.com","subject":"Re: [ANNOUNCE] Git v2.8.1 (and call-for-help to \"make rpmbuild\" users)","fromName":"Elia Pinto","fromEmail":"gitter.spiros@gmail.com","sentAt":"2016-04-05T10:39:52Z","receivedAt":"2016-04-05T10:39:52Z","isPatch":false,"sender":{"key":"gitter.spiros@gmail.com","avatar":"https://avatars.githubusercontent.com/u/158490?v=4"},"body":"2016-04-03 21:21 GMT+02:00 Junio C Hamano <gitster@pobox.com>:\n> If you do not build RPM binary packages from our pristine source,\n> you can safely ignore this release and stop reading this message.\n>\n> Now that the audience of this message has been limited to a narrow\n> target, before I make an announcement, here is a call-for-help to\n> you.\n>\n> Git v2.8 removed README file and added a corresponding README.md\n> file.  The change however did not adjust git.spec.in that still\n> referred to README, causing \"make rpmbuild\" to fail.  The breakage\n> was not noticed by anybody who tested v2.8.0-rc0 and later release\n> candidates, and ended up in the final v2.8 release, and we saw a\n> handful of bug reports on the list after the release happened.\n>\n> This maintenance release is to correct this bug for those who run\n> \"make rpmbuild\". It has no other changes.\n>\n> It is clear that nobody who relies on being able to \"make rpmbuild\"\n> ever tried any of the 5 release candidate snapshots that happened\n> during Feb 26-Mar 28.  We had a whole month and nobody noticed?\n>\n> This incident clearly shows that something needs to happen, if\n> people want \"make rpmbuild\" to keep working.  Even though this\n> maintenance release may fix this single bug, breakages similar to it\n> that only affect \"make rpmbuild\" users are guaranteed to appear in\n> future releases, unless those who can prevent them from happening\n> start helping to test at least release candidate snapshots.\n>\n> It is even more preferrable if they can test the tip of 'next'\n> branch regularly, in order to prevent such breakages from hitting\n> the 'master' branch to be included in the next release, which is\n> what the other parts of the system aims at.\n>\n> The other obvious option is for us to stop pretending that \"make\n> rpmbuild\" does anything useful to do and drop the build target and\n> the unmaintained git.spec.in file on which nobody in the active\n> development community keeps eyes.  I do not mean this as a threat\n> \"help us or else\"; there is a precedent.  We used to ship our own\n> debian/rules and friends for those who wanted to debbuild from the\n> source, but the Debian packagers wanted to have their own proper\n> ones and ours ended up confusing the users, and we made the world\n> a better place by removing our copy.  If \"make rpmbuild\" people want\n> us to take this route, that is also OK for us.\n>\n> So that's the call for help.  Now to the announcement.\n\nHow old contributor to rpm5.org (as devzero2000) I have been following\nthese issues in the past.\nUnfortunately, to my knowledge, no one has ever come to a convergence\nof views between the distros\nthat use rpm on the various differences.\nKeeping for a project a spec file that then no distro uses (and i\nthink also a local sysadmin)\ni do not think it is worth the effort.\n\nhttp://lists.rpm.org/pipermail/rpm-maint/2008-June/002185.html\n\nIMHO\n\nBest\n\n>\n> The latest maintenance release Git v2.8.1 is now available at\n> the usual places.\n>\n> The tarballs are found at:\n>\n>     https://www.kernel.org/pub/software/scm/git/\n>\n> The following public repositories all have a copy of the 'v2.8.1'\n> tag and the 'maint' branch that the tag points at:\n>\n>   url = https://kernel.googlesource.com/pub/scm/git/git\n>   url = git://repo.or.cz/alt-git.git\n>   url = git://git.sourceforge.jp/gitroot/git-core/git.git\n>   url = git://git-core.git.sourceforge.net/gitroot/git-core/git-core\n>   url = https://github.com/gitster/git\n>\n> ----------------------------------------------------------------\n>\n> Git v2.8.1 Release Notes\n> ========================\n>\n> Fixes since v2.8\n> ----------------\n>\n>  * \"make rpmbuild\" target was broken as its input, git.spec.in, was\n>    not updated to match a file it describes that has been renamed\n>    recently.  This has been fixed.\n>\n> ----------------------------------------------------------------\n>\n> Changes since v2.8.0 are as follows:\n>\n> Junio C Hamano (1):\n>       Git 2.8.1\n>\n> Matthieu Moy (1):\n>       git.spec.in: use README.md, not README\n>\n> --\n> To unsubscribe from this list: send the line \"unsubscribe git\" in\n> the body of a message to majordomo@vger.kernel.org\n> More majordomo info at  http://vger.kernel.org/majordomo-info.html\n"}]}