It seems that the patches file for grub 0.97-r10 went missing although it's still the stable version. See: http://de-mirror.org/gentoo/distfiles/ Reproducible: Always Steps to Reproduce: 1. emerge grub 2. 3. Actual Results: Fails to download the patch archive and thus to build grub.
It really helps us if you provide some output or a file name. I see no problem. % wget de-mirror.org/gentoo/distfiles/grub-0.97-patches-1.12.tar.bz2 --2012-02-08 08:29:50-- http://de-mirror.org/gentoo/distfiles/grub-0.97-patches-1.12.tar.bz2 Resolving de-mirror.org... 87.106.54.147 Connecting to de-mirror.org|87.106.54.147|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 55811 (55K) [application/x-tar] Saving to: `grub-0.97-patches-1.12.tar.bz2' 100%[======================================>] 55,811 85.7K/s in 0.6s 2012-02-08 08:29:51 (85.7 KB/s) - `grub-0.97-patches-1.12.tar.bz2' saved [55811/55811] Please re-open if you have other information. Thanks.
Hmm. Sorry for the confusion, but my emerge was trying to get r10 of the file. Does this mean the requirement for the stable marked version was changed?
Not sure, I'd have to research the history of the ebuild at sources.gentoo.org. Still, is there a problem here with the mirrors? I see none.
Yup, nothing is wrong. % grep PATCHVER= * grub-0.92-r1.ebuild:PATCHVER=0.2 grub-0.94-r1.ebuild:PATCHVER=0.1 grub-0.96-r1.ebuild:PATCHVER=0.1 grub-0.96-r2.ebuild:PATCHVER=0.1 grub-0.96-r3.ebuild:PATCHVER=1.0 grub-0.97.ebuild:PATCHVER=1.0 grub-0.97-r10.ebuild:PATCHVER="1.12" # Should match the revision ideally grub-0.97-r2.ebuild:PATCHVER="1.2" grub-0.97-r3.ebuild:PATCHVER="1.4" grub-0.97-r4.ebuild:PATCHVER="1.4" grub-0.97-r5.ebuild:PATCHVER="1.7" grub-0.97-r6.ebuild:PATCHVER="1.7" grub-0.97-r8.ebuild:PATCHVER="1.8" # Should match the revision ideally grub-0.97-r9.ebuild:PATCHVER="1.9" # Should match the revision ideally PATCHVER was changed 4 weeks ago to 1.12. http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sys-boot/grub/grub-0.97-r10.ebuild?r1=1.11&r2=1.12 Mirror in question is up-to-date. http://mirrorstats.gentoo.org/#de
Just for my understanding: this change is valid WRT some policy? I was confused as we keep snapshots of the tree around and thus the "same", stable version of the ebuild would require different distfiles? Not sure what actually changed in those patches, but how would I notice I have to rebuild to get this change?
There is no bug here, so please stop re-opening it. (In reply to comment #5) > Just for my understanding: this change is valid WRT some policy? Yes. > I was confused as we keep snapshots of the tree around and thus the "same", > stable version of the ebuild would require different distfiles? If you are going to do that, you need to mirror the distfiles too. Old distfiles only stay on the mirrors for two weeks when no ebuild references it. > Not sure what actually changed in those patches, but how would I notice I have > to rebuild to get this change? If the patch is only for compilation fix for some issue, it would be a wasteful rebuild for you (since it works already). So, check the ChangeLog if you really care and you will see that 1.11 patchset fixes a gcc-4.6 compilation issue and 1.12 fixes compilation with newer automake versions. The dev community tries hard to make sure that users don't rebuild packages for no reason. You can see all this documented here: http://devmanual.gentoo.org/general-concepts/ebuild-revisions/index.html
