Re: [gentoo-user] Digest verification failed

2016-10-29 Thread Peter Humphrey 
On Saturday 29 Oct 2016 12:56:46 Andrew Lowe wrote:

>   Anyone seeing this again? I've just sync'd to two servers in Australia,
> and then, for the hell of it, one in Canada and am getting it for:
> 
> dev-libs/botan
> app-arch/tar
> media-video/libav
> app-crypt/qca
> net-print/cups-filters

38,000 files were sync'd today here in UK, nearly all of them changelogs and 
manifests, and I now get three of your verification failures. The other ten 
upgrades are in progress at the moment.

> I suppose time will sort it out.

Indeed.

-- 
Regards
Peter

Re: [gentoo-user] Digest verification failed: Filesize does not match recorded size

2016-10-08 Thread Philip Webb 
Here in Toronto at c 2016-10-08 20:30 EDT ,
I successfully emerged  Bash Man-pages Cronbase ,
but ran into the digest problem with  7  'libX...' pkgs.
I've no idea which mirror it used for 'eix-sync',
but the source was probably downloaded from Waterloo Ont.
I'll simply leave them till next Sat, when hopefully the mirrors wb ok.

-- 
,,
SUPPORT ___//___,   Philip Webb
ELECTRIC   /] [] [] [] [] []|   Cities Centre, University of Toronto
TRANSIT`-O--O---'   purslowatchassdotutorontodotca

Re: [gentoo-user] Digest verification failed: Filesize does not match recorded size

2016-10-08 Thread Mick 
On Saturday 08 Oct 2016 15:59:59 Alexander Kapshuk wrote:
> On Sat, Oct 8, 2016 at 1:03 PM, Håkon Alstadheim
> 
>  wrote:
> > Den 08. okt. 2016 11:24, skrev Bill Kenworthy:
> >> On 08/10/16 16:49, Mick wrote:
> >>> On Saturday 08 Oct 2016 11:45:05 Alexander Kapshuk wrote:
>  On Sat, Oct 8, 2016 at 11:33 AM, Andrew Lowe  wrote:
> > On 08/10/16 15:59, Alexander Kapshuk wrote:
> >> I've been getting this output since last night.
> >> 
> >> Calculating dependencies  ... ... done!
> >> [ebuild U  ] app-shells/bash-4.3_p48 [4.3_p46-r1]
> > 
> > [snip]
> > ...
> > ...
> > [snip]
> > 
> >> Or is there some other way to fix this, like running 'ebuild
> >> /path/to/ebuild manifest', as suggested here:
> >> https://forums.gentoo.org/viewtopic-p-7414010.html
> >> 
> >> Thanks.
> >> 
> > Unless Alexander is in Perth, Australia, I can confirm the
> > same
> > 
> > thing, exactly as Alexander described, is happening here - Perth that
> > is.
> > 
> > Andrew
>  
>  Ha, ha. I'm not that Down Under. Pun intended.
>  
>  I used a European mirror.
> >>> 
> >>> I'm getting the same on a UK mirror this morning.
> >> 
> >> Worked for me - iinet mirror, Perth Australia.
> >> 
> >> Tried that one?
> >> 
> >> BillK
> >> 
> >   Same here, from Norway. I did not want to force accept of potentially
> > 
> > bad .emerge by running "emerge .emerge digest". Rather I
> > deleted the Manifest in the affected directories, and ran emerge --sync
> > again. Fixed.
> 
> This solution did not work for me unfortunately.

I didn't even try it.  I'll do what I've always done:  re-sync later and try 
running emerge again.
-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Digest verification failed: Filesize does not match recorded size

2016-10-08 Thread Andrew Lowe 

On 08/10/16 20:59, Alexander Kapshuk wrote:

On Sat, Oct 8, 2016 at 1:03 PM, Håkon Alstadheim
 wrote:

Den 08. okt. 2016 11:24, skrev Bill Kenworthy:

On 08/10/16 16:49, Mick wrote:

On Saturday 08 Oct 2016 11:45:05 Alexander Kapshuk wrote:

On Sat, Oct 8, 2016 at 11:33 AM, Andrew Lowe  wrote:

On 08/10/16 15:59, Alexander Kapshuk wrote:

I've been getting this output since last night.

Calculating dependencies  ... ... done!
[ebuild U  ] app-shells/bash-4.3_p48 [4.3_p46-r1]

[snip]
...
...
[snip]


Or is there some other way to fix this, like running 'ebuild
/path/to/ebuild manifest', as suggested here:
https://forums.gentoo.org/viewtopic-p-7414010.html

Thanks.


Unless Alexander is in Perth, Australia, I can confirm the same

thing, exactly as Alexander described, is happening here - Perth that is.

Andrew

Ha, ha. I'm not that Down Under. Pun intended.

I used a European mirror.

I'm getting the same on a UK mirror this morning.


Worked for me - iinet mirror, Perth Australia.

Tried that one?

BillK




  Same here, from Norway. I did not want to force accept of potentially
bad .emerge by running "emerge .emerge digest". Rather I
deleted the Manifest in the affected directories, and ran emerge --sync
again. Fixed.






This solution did not work for me unfortunately.


	Me neither. I also tried Bill K's suggestion, changing to iinet instead 
of Swinburne but maybe because I'm south of the river, that didn't work 
either. I think I'm going to let it rest for another 24 hours. In the 
past these sort of things manage to sort themselves out given time.


Andrew

Re: [gentoo-user] Digest verification failed: Filesize does not match recorded size

2016-10-08 Thread Alexander Kapshuk 
On Sat, Oct 8, 2016 at 1:03 PM, Håkon Alstadheim
 wrote:
> Den 08. okt. 2016 11:24, skrev Bill Kenworthy:
>> On 08/10/16 16:49, Mick wrote:
>>> On Saturday 08 Oct 2016 11:45:05 Alexander Kapshuk wrote:
 On Sat, Oct 8, 2016 at 11:33 AM, Andrew Lowe  wrote:
> On 08/10/16 15:59, Alexander Kapshuk wrote:
>> I've been getting this output since last night.
>>
>> Calculating dependencies  ... ... done!
>> [ebuild U  ] app-shells/bash-4.3_p48 [4.3_p46-r1]
> [snip]
> ...
> ...
> [snip]
>
>> Or is there some other way to fix this, like running 'ebuild
>> /path/to/ebuild manifest', as suggested here:
>> https://forums.gentoo.org/viewtopic-p-7414010.html
>>
>> Thanks.
>>
> Unless Alexander is in Perth, Australia, I can confirm the same
>
> thing, exactly as Alexander described, is happening here - Perth that is.
>
> Andrew
 Ha, ha. I'm not that Down Under. Pun intended.

 I used a European mirror.
>>> I'm getting the same on a UK mirror this morning.
>>>
>> Worked for me - iinet mirror, Perth Australia.
>>
>> Tried that one?
>>
>> BillK
>>
>>
>>
>   Same here, from Norway. I did not want to force accept of potentially
> bad .emerge by running "emerge .emerge digest". Rather I
> deleted the Manifest in the affected directories, and ran emerge --sync
> again. Fixed.
>
>
>
>

This solution did not work for me unfortunately.

Re: [gentoo-user] Digest verification failed: Filesize does not match recorded size

2016-10-08 Thread Håkon Alstadheim 
Den 08. okt. 2016 11:24, skrev Bill Kenworthy:
> On 08/10/16 16:49, Mick wrote:
>> On Saturday 08 Oct 2016 11:45:05 Alexander Kapshuk wrote:
>>> On Sat, Oct 8, 2016 at 11:33 AM, Andrew Lowe  wrote:
 On 08/10/16 15:59, Alexander Kapshuk wrote:
> I've been getting this output since last night.
>
> Calculating dependencies  ... ... done!
> [ebuild U  ] app-shells/bash-4.3_p48 [4.3_p46-r1]
 [snip]
 ...
 ...
 [snip]

> Or is there some other way to fix this, like running 'ebuild
> /path/to/ebuild manifest', as suggested here:
> https://forums.gentoo.org/viewtopic-p-7414010.html
>
> Thanks.
>
 Unless Alexander is in Perth, Australia, I can confirm the same

 thing, exactly as Alexander described, is happening here - Perth that is.

 Andrew
>>> Ha, ha. I'm not that Down Under. Pun intended.
>>>
>>> I used a European mirror.
>> I'm getting the same on a UK mirror this morning.
>>
> Worked for me - iinet mirror, Perth Australia.
>
> Tried that one?
>
> BillK
>
>
>
  Same here, from Norway. I did not want to force accept of potentially
bad .emerge by running "emerge .emerge digest". Rather I
deleted the Manifest in the affected directories, and ran emerge --sync
again. Fixed.

Re: [gentoo-user] Digest verification failed: Filesize does not match recorded size

2016-10-08 Thread Bill Kenworthy 
On 08/10/16 16:49, Mick wrote:
> On Saturday 08 Oct 2016 11:45:05 Alexander Kapshuk wrote:
>> On Sat, Oct 8, 2016 at 11:33 AM, Andrew Lowe  wrote:
>>> On 08/10/16 15:59, Alexander Kapshuk wrote:
 I've been getting this output since last night.

 Calculating dependencies  ... ... done!
 [ebuild U  ] app-shells/bash-4.3_p48 [4.3_p46-r1]
>>>
>>> [snip]
>>> ...
>>> ...
>>> [snip]
>>>
 Or is there some other way to fix this, like running 'ebuild
 /path/to/ebuild manifest', as suggested here:
 https://forums.gentoo.org/viewtopic-p-7414010.html

 Thanks.

>>> Unless Alexander is in Perth, Australia, I can confirm the same
>>>
>>> thing, exactly as Alexander described, is happening here - Perth that is.
>>>
>>> Andrew
>>
>> Ha, ha. I'm not that Down Under. Pun intended.
>>
>> I used a European mirror.
> 
> I'm getting the same on a UK mirror this morning.
> 

Worked for me - iinet mirror, Perth Australia.

Tried that one?

BillK

Re: [gentoo-user] Digest verification failed: Filesize does not match recorded size

2016-10-08 Thread Mick 
On Saturday 08 Oct 2016 11:45:05 Alexander Kapshuk wrote:
> On Sat, Oct 8, 2016 at 11:33 AM, Andrew Lowe  wrote:
> > On 08/10/16 15:59, Alexander Kapshuk wrote:
> >> I've been getting this output since last night.
> >> 
> >> Calculating dependencies  ... ... done!
> >> [ebuild U  ] app-shells/bash-4.3_p48 [4.3_p46-r1]
> > 
> > [snip]
> > ...
> > ...
> > [snip]
> > 
> >> Or is there some other way to fix this, like running 'ebuild
> >> /path/to/ebuild manifest', as suggested here:
> >> https://forums.gentoo.org/viewtopic-p-7414010.html
> >> 
> >> Thanks.
> >> 
> > Unless Alexander is in Perth, Australia, I can confirm the same
> > 
> > thing, exactly as Alexander described, is happening here - Perth that is.
> > 
> > Andrew
> 
> Ha, ha. I'm not that Down Under. Pun intended.
> 
> I used a European mirror.

I'm getting the same on a UK mirror this morning.
-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Digest verification failed: Filesize does not match recorded size

2016-10-08 Thread Alexander Kapshuk 
On Sat, Oct 8, 2016 at 11:33 AM, Andrew Lowe  wrote:
> On 08/10/16 15:59, Alexander Kapshuk wrote:
>>
>> I've been getting this output since last night.
>>
>> Calculating dependencies  ... ... done!
>> [ebuild U  ] app-shells/bash-4.3_p48 [4.3_p46-r1]
>
> [snip]
> ...
> ...
> [snip]
>>
>> Or is there some other way to fix this, like running 'ebuild
>> /path/to/ebuild manifest', as suggested here:
>> https://forums.gentoo.org/viewtopic-p-7414010.html
>>
>> Thanks.
>>
>>
>
> Unless Alexander is in Perth, Australia, I can confirm the same
> thing, exactly as Alexander described, is happening here - Perth that is.
>
> Andrew
>
>

Ha, ha. I'm not that Down Under. Pun intended.

I used a European mirror.

Re: [gentoo-user] Digest verification failed: Filesize does not match recorded size

2016-10-08 Thread Andrew Lowe 

On 08/10/16 15:59, Alexander Kapshuk wrote:

I've been getting this output since last night.

Calculating dependencies  ... ... done!
[ebuild U  ] app-shells/bash-4.3_p48 [4.3_p46-r1]

[snip]
...
...
[snip]

Or is there some other way to fix this, like running 'ebuild
/path/to/ebuild manifest', as suggested here:
https://forums.gentoo.org/viewtopic-p-7414010.html

Thanks.




	Unless Alexander is in Perth, Australia, I can confirm the same thing, 
exactly as Alexander described, is happening here - Perth that is.


Andrew

Re: [gentoo-user] Digest verification failed:

2016-04-07 Thread Sam Jorna 
On Thu, Apr 07, 2016 at 06:52:20PM -0400, Valmor de Almeida wrote:
>Hello,
>I have done several
>emerge --sync
>today but the digest verification problem below does not go away.
>Any thoughts?
>Thank you.

This has been reported in Bug 579204 [0] and, as far as I am aware, was either
caused by bad timing between commits and rsync metadata generation or some other
factor in generating the metadata being pushed out to rsync servers; though from
what I've seen it seems to only affect some mirrors.

0: https://bugs.gentoo.org/579204

--
Sam Jorna (wraeth)
GnuPG Key: D6180C26


signature.asc
Description: Digital signature

Re: [gentoo-user] Digest verification failed:

2008-11-06 Thread Markos Chandras 
On Thursday 06 November 2008 19:14:57 de Almeida, Valmor F. wrote:
 Hello,

 Any inputs on what this problem might be? Any use of --searchdesc will
 result in a similar output.

 Thanks,

 --
 Valmor

 - emerge --searchdesc eclipse
 Searching...  \!!! Digest verification failed:
 !!! /usr/portage/app-backup/bacula/bacula-2.4.1-r1.ebuild
 !!! Reason: Filesize does not match recorded size
 !!! Got: 15696
 !!! Expected: 15693
  /!!! Digest verification failed:
 !!!
 /usr/portage/local/layman/science/dev-cpp/growler-core/growler-core-0.3.
 7.ebuild
 !!! Reason: Filesize does not match recorded size
 !!! Got: 793
 !!! Expected: 916
 emerge: search: aux_get() failed, skipping

  |!!! Digest verification failed:

 !!!
 /usr/portage/local/layman/science/dev-cpp/growler-link/growler-link-0.3.
 7.ebuild
 !!! Reason: Filesize does not match recorded size
 !!! Got: 817
 !!! Expected: 940
 emerge: search: aux_get() failed, skipping
  /!!! Digest verification failed:
 !!!
 /usr/portage/local/layman/science/dev-cpp/growler-math/growler-math-0.3.
 4.1.ebuild
 !!! Reason: Filesize does not match recorded size
 !!! Got: 695

 -
 Valmor de Almeida, Ph.D.
 Oak Ridge National Laboratory
 1 Bethel Valley Road
 PO Box 2008
 Oak Ridge TN 37831-6181

 url: dealmeidav.ornl.gov
 tel: 865-241-2906
 fax: 865-241-4829
 -

Try layman -S later. growler-math seems to have wrong manifest. It should be 
fixed very soon else contact the maintener. You can find maintainers e-mail 
on 

/usr/portage/local/layman/science/dev-cpp/growler-math/ChangeLog file 
-- 
Markos Chandras

Re: [gentoo-user] Digest verification failed

2008-02-19 Thread Robert Stockdale IV 
On Feb 17, 2008 7:15 PM, Neil Bothwick [EMAIL PROTECTED] wrote:

 On Sun, 17 Feb 2008 09:57:13 -0500, Kenneth Prugh wrote:

  I also don't think straight without breakfast, so I'm sorry about the
  last email.. it wasn't very professional of me :

 How does that differ from the rest of us? :-)

  On a side note: the reason I hate -user is it completely breaks claws
  when it tries to thread it if there are unread

 I have no such problem here, but I have Claws set to show only unread
 messages.


 --
 Neil Bothwick

 Bad dog! Leave that wire [EMAIL PROTECTED] TERRIER


Thanks to everyone who helped. I realizes that a more recent version was
available and I'm emerging it now. When it is done I'll rerun glsa-check
again and let you know if it worked. I't has been some time since I ran a
Gentoo based system and I'm hoping I don't do something to break it. I hate
reinstalling as I usually loose files and time.
Bob

Re: [gentoo-user] Digest verification failed

2008-02-19 Thread Robert Stockdale IV 
On Feb 19, 2008 7:25 AM, Neil Bothwick [EMAIL PROTECTED] wrote:

 On Tue, 19 Feb 2008 07:08:41 -0500, Robert Stockdale IV wrote:

  I't has been some time since I ran a
  Gentoo based system and I'm hoping I don't do something to break it. I
  hate reinstalling as I usually loose files and time.

 With the time it takes for a full reinstall and the amount of
 documentation available to help fix problems, I find it difficult to
 think of a problem not involving dense smoke or horrible grinding noises
 that is best fixed with a reinstall.


 --
 Neil Bothwick

 Real women don't have hot flashes, they have power surges.


Sabayon takes about 3 hours for a complete install and most of it is
performed automatically. I run the setup configuration at the beginning and
it lets me know when to reboot into the fresh install. Correcting a trashed
system could take days.
Bob

Re: [gentoo-user] Digest verification failed

2008-02-19 Thread Neil Bothwick 
On Tue, 19 Feb 2008 07:08:41 -0500, Robert Stockdale IV wrote:

 I't has been some time since I ran a
 Gentoo based system and I'm hoping I don't do something to break it. I
 hate reinstalling as I usually loose files and time.

With the time it takes for a full reinstall and the amount of
documentation available to help fix problems, I find it difficult to
think of a problem not involving dense smoke or horrible grinding noises
that is best fixed with a reinstall.


-- 
Neil Bothwick

Real women don't have hot flashes, they have power surges.


signature.asc
Description: PGP signature

Re: [gentoo-user] Digest verification failed

2008-02-17 Thread Alexander Meinke 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Robert Stockdale IV wrote:
|  * checking firefox-2.0.0.11-source.tar.bz2 ;-)
| ...

| [ !! ]
|
| !!! Digest verification failed:
| !!! /usr/portage/distfiles/firefox-2.0.0.11-source.tar.bz2
| !!! Reason: Filesize does not match recorded size
| !!! Got: 37480419
| !!! Expected: 6794016
|
| Is there a problem with the digest? Is there a work around? Any help
| would be appreciated. If this is a bug, I'll report it.
| Bob

Maybe you should try emerge --sync before emerging firefox.


Regards,

acm.

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.7 (GNU/Linux)

iD8DBQFHuDGcYCx19pTB5PERAp7OAJ4/I2X0c9QewMTNonz1CBQsh/0EuACePrhC
8qR4bYIiHGLikM6CEo/vRm8=
=SU1q
-END PGP SIGNATURE-
--
gentoo-user@lists.gentoo.org mailing list

Re: [gentoo-user] Digest verification failed

2008-02-17 Thread Robert Stockdale IV 
On Feb 17, 2008 8:07 AM, Alexander Meinke [EMAIL PROTECTED] wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Robert Stockdale IV wrote:
 |  * checking firefox-2.0.0.11-source.tar.bz2 ;-)
 | ...

 | [ !! ]
 |
 | !!! Digest verification failed:
 | !!! /usr/portage/distfiles/firefox-2.0.0.11-source.tar.bz2
 | !!! Reason: Filesize does not match recorded size
 | !!! Got: 37480419
 | !!! Expected: 6794016
 |
 | Is there a problem with the digest? Is there a work around? Any help
 | would be appreciated. If this is a bug, I'll report it.
 | Bob

 Maybe you should try emerge --sync before emerging firefox.


 Regards,

 acm.

 -BEGIN PGP SIGNATURE-
 Version: GnuPG v2.0.7 (GNU/Linux)

 iD8DBQFHuDGcYCx19pTB5PERAp7OAJ4/I2X0c9QewMTNonz1CBQsh/0EuACePrhC
 8qR4bYIiHGLikM6CEo/vRm8=
 =SU1q
 -END PGP SIGNATURE-
 --
 gentoo-user@lists.gentoo.org mailing list


I did emerge --sync I also ran eix-sync as well which does that and
more.Still have the same issue.
Bob

Re: [gentoo-user] Digest verification failed

2008-02-17 Thread Kenneth Prugh 
On Sun, 17 Feb 2008 08:03:21 -0500
Robert Stockdale IV [EMAIL PROTECTED] wrote:

 I have been trying to complete a
 glsa-check -f affected
 for the past 2 days.
 The latest problem I have encountered is:
 
  Downloading '
 http://distfiles.gentoo.org/distfiles/firefox-2.0.0.11-source.tar.bz2'
 --02:17:55--
 http://distfiles.gentoo.org/distfiles/firefox-2.0.0.11-source.tar.bz2
= `/usr/portage/distfiles/firefox-2.0.0.11-source.tar.bz2'
 Resolving distfiles.gentoo.org... 156.56.247.195, 140.211.166.134,
 216.165.129.135, ...
 Connecting to distfiles.gentoo.org|156.56.247.195|:80... connected.
 HTTP request sent, awaiting response... 200 OK
 Length: 37,480,419 (36M) [application/x-tar]
 
 100%[]
 37,480,419   236.84K/sETA 00:00
 
 02:20:36 (228.12 KB/s) - `/usr/portage/distfiles/firefox-
 2.0.0.11-source.tar.bz2' saved [37480419/37480419]
 
  * mozilla-firefox-2.0.0.11-patches-0.5.tar.bz2 RMD160 SHA1 SHA256
 size ;-) ...
 [ ok ]
  * checking ebuild checksums ;-)
 ...
 [ ok ]
  * checking auxfile checksums ;-)
 ...
 [ ok ]
  * checking miscfile checksums ;-)
 ...
 [ ok ]
  * checking firefox-2.0.0.11-source.tar.bz2 ;-)
 ...
 [ !! ]
 
 !!! Digest verification failed:
 !!! /usr/portage/distfiles/firefox-2.0.0.11-source.tar.bz2
 !!! Reason: Filesize does not match recorded size
 !!! Got: 37480419
 !!! Expected: 6794016
 
 Is there a problem with the digest? Is there a work around? Any help
 would be appreciated. If this is a bug, I'll report it.
 Bob

A temporary solution:

cd /usr/portage/www-client/mozilla-firefox/  rm Manifest  ebuild
mozilla-firefox-2.0.0.12.ebuild manifest

Then try to emerge it. 

-- 
Ken69267
Gentoo AMD64 AT


signature.asc
Description: PGP signature

Re: [gentoo-user] Digest verification failed

2008-02-17 Thread Neil Bothwick 
On Sun, 17 Feb 2008 09:15:06 -0500, Kenneth Prugh wrote:

 A temporary solution:
 
 cd /usr/portage/www-client/mozilla-firefox/  rm Manifest  ebuild
 mozilla-firefox-2.0.0.12.ebuild manifest

s/temporary/terrible/

This message means that either the portage tree contains the wrong
checksum for a valid file, or that the file on your mirror has been
replaced by an altered version. Redigesting to fix this problem is like
fixing low oil pressure in your car by disconnecting the warning light.

By all means feel free to take his risk on your own system, but please
don't recommend others to do it without at least pointing out the
potentially serious consequences.

To the OP, it is possible that the Firefox archive was updated and you
still have an older one in $DISTDIR. Try deleting your copy and emerging
again. You could also try using a different mirror.


-- 
Neil Bothwick

F*ck it said Pooh, being more forthright than usual.


signature.asc
Description: PGP signature

Re: [gentoo-user] Digest verification failed

2008-02-17 Thread Etaoin Shrdlu 
On Sunday 17 February 2008, Kenneth Prugh wrote:

  !!! Digest verification failed:
  !!! /usr/portage/distfiles/firefox-2.0.0.11-source.tar.bz2
  !!! Reason: Filesize does not match recorded size
  !!! Got: 37480419
  !!! Expected: 6794016
 
  Is there a problem with the digest? Is there a work around? Any help
  would be appreciated. If this is a bug, I'll report it.
  Bob

 A temporary solution:

 cd /usr/portage/www-client/mozilla-firefox/  rm Manifest  ebuild
 mozilla-firefox-2.0.0.12.ebuild manifest

- he is having problem with 2.0.0.11, not 2.0.0.12
- wasn't manual digest regeneration considered a very Bad Thing?
- look at the expected size. It's much bigger than the actual size. This 
might be caused by a partially downloaded tarball 
in /usr/portage/distfiles. He might try 
rm /usr/portage/distfiles/firefox-2.0.0.11-source.tar.bz2 and try 
reemerging. That should download the correct tarball. 

To the OP: if you just synced, you can do emerge mozilla-firefox and 
get version 2.0.0.12, which is the current stable version, which I 
suppose also fixes the glsa problems (if the glsa is 200712-21).
-- 
gentoo-user@lists.gentoo.org mailing list

Re: [gentoo-user] Digest verification failed

2008-02-17 Thread Kenneth Prugh 
On Sun, 17 Feb 2008 14:25:11 +
Neil Bothwick [EMAIL PROTECTED] wrote:

 On Sun, 17 Feb 2008 09:15:06 -0500, Kenneth Prugh wrote:
 
  A temporary solution:
  
  cd /usr/portage/www-client/mozilla-firefox/  rm Manifest  ebuild
  mozilla-firefox-2.0.0.12.ebuild manifest
 
 s/temporary/terrible/
 
 This message means that either the portage tree contains the wrong
 checksum for a valid file, or that the file on your mirror has been
 replaced by an altered version. Redigesting to fix this problem is
 like fixing low oil pressure in your car by disconnecting the warning
 light.
 
 By all means feel free to take his risk on your own system, but please
 don't recommend others to do it without at least pointing out the
 potentially serious consequences.
 
 To the OP, it is possible that the Firefox archive was updated and you
 still have an older one in $DISTDIR. Try deleting your copy and
 emerging again. You could also try using a different mirror.
 
 

yawn, and if the download was invalid it would most likely fail to
untar or something similar. I fail to see the point. Either way, he can
delete it in distfiles and just remerge/remanifest so it grabs it off
the mirrors.

I also remember why I hate this mailing list and usually just mark all
read.

-- 
Ken69267
Gentoo AMD64 AT


signature.asc
Description: PGP signature

Re: [gentoo-user] Digest verification failed

2008-02-17 Thread Neil Bothwick 
On Sun, 17 Feb 2008 09:32:25 -0500, Kenneth Prugh wrote:

 yawn, and if the download was invalid it would most likely fail to
 untar or something similar. I fail to see the point.

That's because you are assuming that all file corruption is accidental,
whereas the manifest system is designed to protect against malicious
corruption.

 I also remember why I hate this mailing list and usually just mark all
 read.

That is safer that advising people to override portage's security
precautions.


-- 
Neil Bothwick

Paranoia: A healthy understanding of the nature of the universe.


signature.asc
Description: PGP signature

Re: [gentoo-user] Digest verification failed

2008-02-17 Thread Neil Bothwick 
On Sun, 17 Feb 2008 09:57:13 -0500, Kenneth Prugh wrote:

 I also don't think straight without breakfast, so I'm sorry about the
 last email.. it wasn't very professional of me :

How does that differ from the rest of us? :-)

 On a side note: the reason I hate -user is it completely breaks claws
 when it tries to thread it if there are unread

I have no such problem here, but I have Claws set to show only unread
messages.


-- 
Neil Bothwick

Bad dog! Leave that wire [EMAIL PROTECTED] TERRIER


signature.asc
Description: PGP signature

Re: [gentoo-user] digest verification failed for libgsf

2007-03-20 Thread Bo Ørsted Andresen 
On Tuesday 20 March 2007 19:28:26 Vikas Kumar wrote:
 today after emerge --sync when i did emerge -pvuDN world, i got this

 # emerge -pvuDN world

 These are the packages that would be merged, in order:

 Calculating world dependencies \!!! Digest verification failed:
 !!! /usr/portage/gnome-extra/libgsf/libgsf-1.14.0.ebuild
 !!! Reason: Filesize does not match recorded size
 !!! Got: 1441
 !!! Expected: 1472 
/!!! Digest verification failed: !!!
[SNIP]

Wow, what are the odds of that... The updated Manifest is shown in cvs as 
committed 9 seconds after the updated ebuild. Yet you seem to have the 
updated ebuild but the old Manifest... Just sync again.

-- 
Bo Andresen


pgphq1tSQ4oBh.pgp
Description: PGP signature

Re: [gentoo-user] digest verification failed for libgsf

2007-03-20 Thread Vikas Kumar 
On 19:54 Tue 20 Mar , Bo Ørsted Andresen wrote:
 On Tuesday 20 March 2007 19:28:26 Vikas Kumar wrote:
  today after emerge --sync when i did emerge -pvuDN world, i got this
 
  # emerge -pvuDN world
 
  These are the packages that would be merged, in order:
 
  Calculating world dependencies \!!! Digest verification failed:
  !!! /usr/portage/gnome-extra/libgsf/libgsf-1.14.0.ebuild
  !!! Reason: Filesize does not match recorded size
  !!! Got: 1441
  !!! Expected: 1472 
 /!!! Digest verification failed: !!!
 [SNIP]
 
 Wow, what are the odds of that... The updated Manifest is shown in cvs as 
 committed 9 seconds after the updated ebuild. Yet you seem to have the 
 updated ebuild but the old Manifest... Just sync again.

thanks Andresen. the local server i use to sync syncs once in 24 hrs due
to bandwidth limitations. i'll sync again tomorrow.



-- 
THE LESSER-KNOWN PROGRAMMING LANGUAGES #16: C-

This language was named for the grade received by its creator when he
submitted it as a class project in a graduate programming class.  C- is best
described as a low-level programming language.  In fact, the language
generally requires more C- statements than machine-code statements to
execute a given task.  In this respect, it is very similar to COBOL.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Digest verification failed: qt-x11-opensource-src-4.1.4.tar.gz

2006-10-25 Thread Régis Décamps 

On 10/25/06, Meino Christian Cramer [EMAIL PROTECTED] wrote:

Hi,

 I got this:

Downloading 
'ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo/distfiles/qt-x11-opensource-src-4.1.4.tar.gz'
   --06:23:28--  
ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo/distfiles/qt-x11-opensource-src-4.1.4.tar.gz
  = `/usr/portage/distfiles/qt-x11-opensource-src-4.1.4.tar.gz'
   Resolving sunsite.informatik.rwth-aachen.de... 137.226.34.227
   Connecting to sunsite.informatik.rwth-aachen.de|137.226.34.227|:21... 
connected.
   Logging in as anonymous ... Logged in!
   == SYST ... done.== PWD ... done.
   == TYPE I ... done.  == CWD /pub/Linux/gentoo/distfiles ... done.
   == PASV ... done.== RETR qt-x11-opensource-src-4.1.4.tar.gz ... done.
   Length: 32,174,985 (31M) (unauthoritative)

   100%[] 32,174,985   122.99K/sETA 
00:00

   06:27:46 (122.36 KB/s) - 
`/usr/portage/distfiles/qt-x11-opensource-src-4.1.4.tar.gz' saved [32174985]

* checking ebuild checksums ;-) ...  [ 
ok ]
* checking auxfile checksums ;-) ... [ 
ok ]
* checking miscfile checksums ;-) ...[ 
ok ]
* checking qt-x11-opensource-src-4.1.4.tar.gz ;-) ...[ 
!! ]

   !!! Digest verification failed:
   !!! /usr/portage/distfiles/qt-x11-opensource-src-4.1.4.tar.gz
   !!! Reason: Filesize does not match recorded size
   !!! Got: 32174985
   !!! Expected: 409784


Hello,


From Trolltech:

STORED: ftp://ftp.trolltech.com/qt/source/qt-x11-opensource-src-4.1.4.tar.gz
88f8c9c4622108baca2950baac3c02d6  qt-x11-opensource-src-4.1.4.tar.gz
Size: 32174985 bytes

So I'd say there is a problem in the ebuild. Maybe you should copy the
ebuild in an overlay directory and regenerate it with
ebuild qt-x11-opensource-src-4.1.4.ebuild digest


--
Régis

http://regis.decamps.info/blog/

--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Digest verification failed: qt-x11-opensource-src-4.1.4.tar.gz

2006-10-25 Thread Neil Bothwick 
On Wed, 25 Oct 2006 12:08:42 +0200, Régis Décamps wrote:

 So I'd say there is a problem in the ebuild. Maybe you should copy the
 ebuild in an overlay directory and regenerate it with
 ebuild qt-x11-opensource-src-4.1.4.ebuild digest

You don;t need to copy an ebuild to an overlay to re-digest it, you can
do it with the version i the portage tree. You can even do it when
emerging, with emerge --digest, but be aware this will redigest all
packages emerged, including dependencies.

However you do it, think very carefully first. Package digests are a
security measure, to ensure none of the files you are installing have
been tampered with. By regdigesting a package, you're discarding this
check. Before considering this, remove the file(s) from $DISTDIR, sync
again and try to emerge the package normally.


-- 
Neil Bothwick

WinErr 01F: Reserved for future mistakes of our developers.


signature.asc
Description: PGP signature

Re: [gentoo-user] Digest verification failed: qt-x11-opensource-src-4.1.4.tar.gz

2006-10-25 Thread Stuart Howard 

http://bugs.gentoo.org/show_bug.cgi?id=149809

Have a look at this, should help

On 25/10/06, Neil Bothwick [EMAIL PROTECTED] wrote:

On Wed, 25 Oct 2006 12:08:42 +0200, Régis Décamps wrote:

 So I'd say there is a problem in the ebuild. Maybe you should copy the
 ebuild in an overlay directory and regenerate it with
 ebuild qt-x11-opensource-src-4.1.4.ebuild digest

You don;t need to copy an ebuild to an overlay to re-digest it, you can
do it with the version i the portage tree. You can even do it when
emerging, with emerge --digest, but be aware this will redigest all
packages emerged, including dependencies.

However you do it, think very carefully first. Package digests are a
security measure, to ensure none of the files you are installing have
been tampered with. By regdigesting a package, you're discarding this
check. Before considering this, remove the file(s) from $DISTDIR, sync
again and try to emerge the package normally.


--
Neil Bothwick

WinErr 01F: Reserved for future mistakes of our developers.






--
There are 10 types of people in this world: those who understand
binary, those who don't

--Unknown

--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Digest verification failed: qt-x11-opensource-src-4.1.4.tar.gz

2006-10-25 Thread Meino Christian Cramer 
From: Stuart Howard [EMAIL PROTECTED]
Subject: Re: [gentoo-user] Digest verification failed: 
qt-x11-opensource-src-4.1.4.tar.gz
Date: Wed, 25 Oct 2006 11:55:50 +0100

Thanks a lot! qt is currently compiling! :)

Keep hacking!
mcc


 http://bugs.gentoo.org/show_bug.cgi?id=149809
 
 Have a look at this, should help
 
 On 25/10/06, Neil Bothwick [EMAIL PROTECTED] wrote:
  On Wed, 25 Oct 2006 12:08:42 +0200, Régis Décamps wrote:
 
   So I'd say there is a problem in the ebuild. Maybe you should copy the
   ebuild in an overlay directory and regenerate it with
   ebuild qt-x11-opensource-src-4.1.4.ebuild digest
 
  You don;t need to copy an ebuild to an overlay to re-digest it, you can
  do it with the version i the portage tree. You can even do it when
  emerging, with emerge --digest, but be aware this will redigest all
  packages emerged, including dependencies.
 
  However you do it, think very carefully first. Package digests are a
  security measure, to ensure none of the files you are installing have
  been tampered with. By regdigesting a package, you're discarding this
  check. Before considering this, remove the file(s) from $DISTDIR, sync
  again and try to emerge the package normally.
 
 
  --
  Neil Bothwick
 
  WinErr 01F: Reserved for future mistakes of our developers.
 
 
 
 
 
 -- 
 There are 10 types of people in this world: those who understand
 binary, those who don't
 
 --Unknown
 
 -- 
 gentoo-user@gentoo.org mailing list
 

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Digest verification failed:

2006-10-01 Thread David Relson 
On Sun, 1 Oct 2006 03:41:39 +0200
Bo Ørsted Andresen wrote:

...[snip]...

 Since the offending file is in the portage tree rather than in
 distfiles it doesn't make a lot of sense to delete it since only a
 sync will be able to refetch it anyway. Had it been in distfiles then
 Dales suggestions are correct.
 
 In this case, however, the problem isn't with the file rather it's
 with dev-util/pycrypto (which calculates the hash) [2]. And wow, that
 bug is really old by now! ;P The solution:
 
 # emerge -va1 =dev-python/pycrypto-2.0.1-r5
 
 [1]
 http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=2chap=1#doc_chap4
 [2] http://bugs.gentoo.org/show_bug.cgi?id=131293
 
 -- 
 Bo Andresen

Bo,

You've provided the solution!  Thanks.

David

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Digest verification failed:

2006-09-30 Thread Dale 
David Relson wrote:
 Greetings,

 In the last few days I've been encountering lots of Digest
 verification failed messages indicating SHA256 verification
 problems (see below).

 Searching the web, I've found the generate your own digest solution,
 i.e.  ebuild ...package...ebuild digest.  Since the checksums are
 present to ensure integrity, this seems like a bad idea.

 Is it a bad idea to generate my own digest values?

 If so, what are the alternatives?

 Thanks.

 David

 ... emerge gettext

  Calculating dependencies ... done!

   
 Emerging (1 of 1) sys-devel/gettext-0.15 to /
 Downloading
 'http://distfiles.gentoo.org/distfiles/gettext-0.15.tar.gz'
 
 --20:18:41--  http://distfiles.gentoo.org/distfiles/gettext-0.15.tar.gz
= `/usr/portage/distfiles/gettext-0.15.tar.gz'
 Resolving distfiles.gentoo.org... 216.165.129.135, 156.56.247.195,
 64.50.238.52, ... Connecting to
 distfiles.gentoo.org|216.165.129.135|:80... connected. 
 HTTP request sent, awaiting response... 200 
 OK Length: 8,081,941 (7.7M)
 [application/x-gzip]

 100%[] 8,081,941142.51K/s
 ETA 00:00

 20:19:36 (144.45 KB/s) - `/usr/portage/distfiles/gettext-0.15.tar.gz'
 saved [8081941/8081941]

  * checking ebuild checksums ;-) ... [ ok ]
  * checking auxfile checksums ;-) ... [ !! ]

 !!! Digest verification failed:
 !!! /usr/portage/sys-devel/gettext/files/gettext-0.12.1-without_java.patch
 !!! Reason: Failed on SHA256 verification
 !!! Got:
 6dfefe191bc9435a957f7f6ff0658a771cf6ccffbaf169cae79ce7017a0421ee 
 !!! Expected:
 c5a6a223c8be6ba11f1c180c7f381914abe127c0dffb0ec91d2e0a8e06892c92
   

I usually delete the offender from distfiles and let it download again. 
If it still fails, try sync'ing again.  After that, wait until portage
gets updated and try again.  You could also be nice and see if there is
a bug report about the offender and file one if not so the maintainer
knows about it.

That said, it could be that the server you are getting them from is
having problems.  I have ran into that a time or two as well.  Switching
servers may help.

That's my thoughts at least.

Dale

:-)  :-)
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Digest verification failed:

2006-09-30 Thread Bo Ørsted Andresen 
On Sunday 01 October 2006 02:23, David Relson wrote:
 In the last few days I've been encountering lots of Digest
 verification failed messages indicating SHA256 verification
 problems (see below).

 Searching the web, I've found the generate your own digest solution,
 i.e.  ebuild ...package...ebuild digest.  Since the checksums are
 present to ensure integrity, this seems like a bad idea.

 Is it a bad idea to generate my own digest values?

Yes. There is now a section about it in the handbook [1].

 If so, what are the alternatives?
[SNIP]
 !!! Digest verification failed:
 !!! /usr/portage/sys-devel/gettext/files/gettext-0.12.1-without_java.patch
 !!! Reason: Failed on SHA256 verification
 !!! Got:
 6dfefe191bc9435a957f7f6ff0658a771cf6ccffbaf169cae79ce7017a0421ee
 !!! Expected:
 c5a6a223c8be6ba11f1c180c7f381914abe127c0dffb0ec91d2e0a8e06892c92

Since the offending file is in the portage tree rather than in distfiles it
doesn't make a lot of sense to delete it since only a sync will be able to
refetch it anyway. Had it been in distfiles then Dales suggestions are correct.

In this case, however, the problem isn't with the file rather it's with
dev-util/pycrypto (which calculates the hash) [2]. And wow, that bug is really
old by now! ;P The solution:

# emerge -va1 =dev-python/pycrypto-2.0.1-r5

[1] 
http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=2chap=1#doc_chap4
[2] http://bugs.gentoo.org/show_bug.cgi?id=131293

-- 
Bo Andresen


pgpNFNyfLTT20.pgp
Description: PGP signature

RE: [gentoo-user] Digest verification failed!

2005-10-04 Thread Nick Rout 
On Mon, 2005-10-03 at 14:29 -0400, Dave Nebinger wrote:
  I can't figure out how to get past it.
 
 After changing the ebuild, type ebuild mailman-xxx.ebuild digest.  This
 fixes the digest values.
 
 You should then be able to emerge mailman w/o resync.
 
 

or type emerge --digest mailman


-- 
gentoo-user@gentoo.org mailing list

RE: [gentoo-user] Digest verification failed!

2005-10-03 Thread Dave Nebinger 
 I can't figure out how to get past it.

After changing the ebuild, type ebuild mailman-xxx.ebuild digest.  This
fixes the digest values.

You should then be able to emerge mailman w/o resync.


-- 
gentoo-user@gentoo.org mailing list

RE: [gentoo-user] Digest verification Failed

2005-07-19 Thread Dave Nebinger 
 Anyone know why the digests are failing so frequently? Are they packaged
 poorly? Is it the mirror I'm getting them from? But then that begs the
 question, aren't the mirrors synchronized and MD5 verified with each
 other?
 Shouldn't TCP/IP be safe in that it retries a packet until it gets it --
 and
 therefore, why is the MD5 different?

I haven't had any issues with md5 sums on recent packages and my systems are
updated pretty much daily (thus requiring frequent downloads).

When it has happened I had to delete the file from /usr/portage/distfiles in
order to fetch a clean copy.  And since I'm running http-replicator I will
also remove any cached copy and recycle http-replicator to ensure it is
starting from a clean state.  If you're using this or another cache/proxy
you'll want to ensure that you clean it out before retrying the fetch.

I'm not sure how the mirrors are synchronized but I would guess it's rsync
based.  There should not be any problems there.  I don't know if they check
the md5 sums on files pulled into the mirror, but I would guess they do not.

I'd look at your /var/log/emerge.log for errors dealing with the fetch.
Also check for filesystem errors if you're using a separate FS for the
/usr/portage space; it could be a read/write error associated with the disk
itself.




-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Digest verification Failed

2005-07-19 Thread Neil Bothwick 
On Tue, 19 Jul 2005 10:48:10 -0700, Daevid Vincent wrote:

 I would use --skipfirst, but that doesn't work with emerge -Davu
 world... *sigh*.

--skipfirst only works in conjunction with --resume

emerge -avuD world
something fails
emerge --resume --skipfirst


-- 
Neil Bothwick

Another casualty of applied metaphysics.


pgp9Egfat4BRm.pgp
Description: PGP signature