I am trying to emerge -auvD world but I'm having problems with
perl-cleaner-1.03. I've repeatedly tried to get it, but either the sites
that emerge goes to time out, or when I do get a copy of the file, the MD5
check fails. Any ideas?

Thanks!

Durk

I am having the same issue, at first the FTP download site seemed to be down
but now I am getting a message saying it was trying to resume the download
but the file had already completely been retrieved...... bummer right in the
middle of an emerge -e system too.


"Durk van Veen" <nospamplz@example.com> wrote in message
news:WOPdg.177735$bm6.70231@fed1read04...
>I am trying to emerge -auvD world but I'm having problems with
>perl-cleaner-1.03. I've repeatedly tried to get it, but either the sites
>that emerge goes to time out, or when I do get a copy of the file, the MD5
>check fails. Any ideas?
>
> Thanks!
>
> Durk
>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Don't forget "emerge --resume". You don't have to start over!

Just in case you didn't know.

Chris

Rick Born wrote:
> I am having the same issue, at first the FTP download site seemed
> to be down but now I am getting a message saying it was trying to
> resume the download but the file had already completely been
> retrieved...... bummer right in the middle of an emerge -e system
> too.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: GnuPT 2.7.2
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEeJMF6ZGQ8LKA8nwRAkjHAKCsd/UsysY8IfHoQFvZ6zi9NS6KBgCfVlzL
vE9UVUeUoC4wiRP86o3pl6M=
=TZYZ
-----END PGP SIGNATURE-----

Durk van Veen wrote:
> I am trying to emerge -auvD world but I'm having problems with
> perl-cleaner-1.03. I've repeatedly tried to get it, but either the
> sites that emerge goes to time out, or when I do get a copy of the
> file, the MD5 check fails. Any ideas?
>
> Thanks!
>
> Durk

OK, I hunted around google and the forums some more and it appears similar
situations have happened in the past. I was able to get around it by
recomputing the digest, manually merging the package, then rerunning the
main emerge, like so:

$ ebuild /usr/portage/app-admin/perl-cleaner/perl-cleaner-1.03.ebuild digest
$ ebuild /usr/portage/app-admin/perl-cleaner/perl-cleaner-1.03.ebuild merge
$ emerge -uvD world

Hope this helps other folks running into this as well.

Durk

Durk van Veen <nospamplz@example.com> wrote:
>
> OK, I hunted around google and the forums some more and it appears
> similar situations have happened in the past. I was able to get
> around it by recomputing the digest, manually merging the package,
> then rerunning the main emerge, like so:
>
> $ ebuild /usr/portage/app-admin/perl-cleaner/perl-cleaner-1.03.ebuild
> digest $ ebuild
> /usr/portage/app-admin/perl-cleaner/perl-cleaner-1.03.ebuild merge $
> emerge -uvD world
> Hope this helps other folks running into this as well.

The problem is that both 1.03 and 1.03-r1 uses the same package name,
perl-cleaner-1.03.tar.gz So if you have installed 1.03, and then try to
install 1.03-r1, the checksum fails, which it should.

The above will cause you to install using 1.03's package if already there,
which although it works, gives you the wrong version. Instead, I'd
recommend:

rm /usr/portage/distfiles/perl-cleaner-1.03.tar.gz
emerge --oneshot --update app-admin/perl-cleaner

Regards,
--
*Art

Arthur Hagen wrote:
> Durk van Veen <nospamplz@example.com> wrote:
>>
>> OK, I hunted around google and the forums some more and it appears
>> similar situations have happened in the past. I was able to get
>> around it by recomputing the digest, manually merging the package,
>> then rerunning the main emerge, like so:
>>
>> $ ebuild /usr/portage/app-admin/perl-cleaner/perl-cleaner-1.03.ebuild
>> digest $ ebuild
>> /usr/portage/app-admin/perl-cleaner/perl-cleaner-1.03.ebuild merge $
>> emerge -uvD world
>> Hope this helps other folks running into this as well.
>
> The problem is that both 1.03 and 1.03-r1 uses the same package name,
> perl-cleaner-1.03.tar.gz So if you have installed 1.03, and then try
> to install 1.03-r1, the checksum fails, which it should.
>
> The above will cause you to install using 1.03's package if already
> there, which although it works, gives you the wrong version. Instead, I'd
> recommend:
>
> rm /usr/portage/distfiles/perl-cleaner-1.03.tar.gz
> emerge --oneshot --update app-admin/perl-cleaner
>
> Regards,

Nice, I will try that when my in-progress emerge is done. Although since it
is working on KDE 3.5 that could take a little while, heh.

Over 400 years ago, Nostradamus predicted that on Sat, 27 May 2006
21:40:44 -0400, in message <e5av2r$fog$1@tree.broomstick.com>, Arthur
Hagen would say:

> The above will cause you to install using 1.03's package if already there,
> which although it works, gives you the wrong version. Instead, I'd
> recommend:
>
> rm /usr/portage/distfiles/perl-cleaner-1.03.tar.gz
> emerge --oneshot --update app-admin/perl-cleaner

Worked a treat. Thanks.

PRose

Arthur Hagen wrote:
<SNIP>
> The problem is that both 1.03 and 1.03-r1 uses the same package name,
> perl-cleaner-1.03.tar.gz So if you have installed 1.03, and then try
> to install 1.03-r1, the checksum fails, which it should.
>
> The above will cause you to install using 1.03's package if already
> there, which although it works, gives you the wrong version. Instead, I'd
> recommend:
>
> rm /usr/portage/distfiles/perl-cleaner-1.03.tar.gz
> emerge --oneshot --update app-admin/perl-cleaner
>
> Regards,

Hmm, on my box it didn't force the re-install. The package is listed as
1.03, not 1.03-r1. Does this mean I have r1 but it just lists it wrong
because I did that ebuild digest thing? See log below:

pacman ~ # equery list perl-cleaner
[ Searching for package 'perl-cleaner' in all categories among: ]
* installed packages
[I--] [ ] app-admin/perl-cleaner-1.03 (0)
pacman ~ # rm /usr/portage/distfiles/perl-cleaner-1.03.tar.gz
pacman ~ # emerge --oneshot --update app-admin/perl-cleaner
Calculating dependencies ...done!
>>> Auto-cleaning packages ...

>>> No outdated packages were found on your system.


* GNU info directory index is up-to-date.

pacman ~ #

Durk van Veen <nospamplz@example.com> wrote:
>
> Hmm, on my box it didn't force the re-install. The package is listed
> as 1.03, not 1.03-r1. Does this mean I have r1 but it just lists it wrong
> because I did that ebuild digest thing?

Probably, yes. After another "emerge --sync", you should get the corrected
version (or, rather, 1.04 which is out now).

Regards,
--
*Art

Arthur Hagen wrote:
>
> Probably, yes. After another "emerge --sync", you should get the
> corrected version (or, rather, 1.04 which is out now).
>
> Regards,

OK, did another emerge --sync and now the 1.04 version is slated for
installation. So that should take care of that. Interestingly enough I got a
block between pam-login and shadow this time around and when I tried to
"emerge -C pam-login && emerge -u shadow" I got a filesize mismatch on
shadow after pam-login uninstalled!!!! Argh!

I'm now trying to just install the other stuff (binutils & gcc, fun!) first
and then deal with shadow hopefully without having to re-login, since I have
no /bin/login right now.

Do I keep screwing these things up or is someone asleep at the wheel on the
ebuild side?

Durk