digest for the jabber-1.4.2.tar.gz appears to be incorrect... How does one go about confirming which is correct... ( e.g. has jaber been compramized on dl severs, or is the ebuild borked )? ebuild -> MD5 10780dbdb93926ea5bb360e1186b939c jabber-1.4.2.tar.gz 690217 fresh -> MD5 e5a0f96ba804a1626e37806d17114e1e jabber-1.4.2.tar.gz 691919
Created attachment 11342 [details, diff] digest file patch assuming ebuild is borked diff -c3 digest-jabber-server-1.4.2-r2-borked digest-jabber-server-1.4.2-r2 > /root/digest.patch
Created attachment 11343 [details, diff] digest file patch assuming ebuild is borked diff -c3 digest-jabber-server-1.4.2-r2-borked digest-jabber-server-1.4.2-r2 > /root/digest.patch
Created attachment 11344 [details, diff] digest file patch assuming ebuild is borked diff -c3 digest-jabber-server-1.4.2-r2-borked digest-jabber-server-1.4.2-r2 > /root/digest.patch
avenj: i've added the new file in /space/distfiles it's a little bit smaller the old file is still in /home/gmirror do existing files get no updates ?
It should update. I don't know why it isn't. I did it manually and will look into it.
This bug has been "critical" and inactive for 6.5 months. Feedback please.
Wow this one is a tad old. I just verified the ebuild compiles, so it must have been addressed. Thanks, Doug
funny, i thought i closed this... sorry...