When i try to emerge xmms-alsa-1.2.10-r2 i get this: >>> emerge (1 of 1) media-plugins/xmms-alsa-1.2.10-r2 to / >>> md5 files ;-) xmms-alsa-1.2.10.ebuild !!! Digest verification Failed: !!! /usr/portage/media-plugins/xmms-alsa/xmms-alsa-1.2.10-r2.ebuild !!! Reason: Filesize does not match recorded size >>> Please ensure you have sync'd properly. Please try 'emerge sync' and >>> optionally examine the file(s) for corruption. A sync will fix most cases. I removed the ebuild, synced again but it didn't worked either. I read some forum stuff from simular things and i found: FEATURES=-strict emerge -l xmms-alsa. I did that and now it works but i don't know if this is a good way to do it. Reproducible: Always Steps to Reproduce: 1. emerge sync 2. emerge xmms-alsa 3. Actual Results: >>> emerge (1 of 1) media-plugins/xmms-alsa-1.2.10-r2 to / >>> md5 files ;-) xmms-alsa-1.2.10.ebuild !!! Digest verification Failed: !!! /usr/portage/media-plugins/xmms-alsa/xmms-alsa-1.2.10-r2.ebuild !!! Reason: Filesize does not match recorded size >>> Please ensure you have sync'd properly. Please try 'emerge sync' and >>> optionally examine the file(s) for corruption. A sync will fix most cases. Expected Results: Merge xmms-alsa correctly. Portage 2.0.51.19 (default-linux/amd64/2005.0, gcc-3.4.3, glibc-2.3.4.20041102-r1, 2.6.11-gentoo-r7 x86_64) ================================================================= System uname: 2.6.11-gentoo-r7 x86_64 AMD Athlon(tm) 64 Processor 3400+ Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Apr 7 2005, 21:21:44)] distcc 2.18.3 x86_64-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.3 [enabled] dev-lang/python: 2.3.4-r1 sys-apps/sandbox: [Not Present] sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.5 sys-devel/binutils: 2.15.92.0.2-r8 sys-devel/libtool: 1.5.16 virtual/os-headers: 2.6.8.1-r4 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CFLAGS="-march=k8 -pipe -O2" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=k8 -pipe -O2" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox strict" GENTOO_MIRRORS="http://ftp.belnet.be/packages/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.belnet.be/gentoo-portage" USE="amd64 X acpi alsa berkdb bitmap-fonts crypt font-server fortran gif gpm gtk imagemagick jp2 jpeg lzw lzw-tiff mp3 ncurses nls opengl oss pam perl png python readline ssl tcltk tcpd tiff truetype truetype-fonts type1-fonts usb userlocales xml2 xmms xpm xrandr xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
It's fixed in cvs, but the problem is that repoman commits, signs Manifest, then commits the Manifest. IMO, it SHOULD, commit, commit unsigned Manifest, sign Manifest, commit signed Manifest. Granted it was my fault for forgetting to enter the passphrase promptly =( but I still think this should be addressed.
Created attachment 58660 [details, diff] Patch to commit Manfiest thrice Does what you ask but needs testing before being released.
Created attachment 58664 [details, diff] Fixed patch (+more) Previous one was buggy. This has got some new checks and speedups in there as well that I was too lazy to separate out (but these are tested and guaranteed). Will do some testing of committing myself too.
Confirmed it works. Check the Manifest changes here after the page updates: http://www.gentoo.org/cgi-bin/viewcvs.cgi/www-client/rabbitticker/ Will confirm that it won't place too much extra load on the CVS server before committing.
*** Bug 92222 has been marked as a duplicate of this bug. ***
Fixed on or before 2.0.51.22-r1
Looking through the batch of bugs, I'm not sure that some of these are actually fixed in stable. Others, the requirements have possibly changed after the initial fix was committed. If you think this bug has been closed incorrectly, please reopen or ask that it be reopened.
