SEO

#1 (**permalink**) 02-21-2008, 10:05 AM

I keep getting this message when I emerge packages, for example

Please upgrade your package (libmpeg3-1.5.2) to use toolchain-funcs.eclass

While every thing seems to work ok, I can't help but be a
little concerned that there is something wrong. Is there something else
that is out of date causing this?

#2 (**permalink**) 02-21-2008, 10:05 AM

Andrew Walker wrote:

> I keep getting this message when I emerge packages, for example
>
> Please upgrade your package (libmpeg3-1.5.2) to use
> toolchain-funcs.eclass
>
> While every thing seems to work ok, I can't help but be a little
> concerned that there is something wrong. Is there something else that
> is out of date causing this?

You'll probably see a lot of these messages during unmerge of old
packages, as they use the ebuilds that are stored in /var/db/pkg/.
These can be quite obsolete by the time they're unmerged. At any rate,
those kinds of notices are probably intended for the developers, so I
don't think it's something you need to worry about.

--
PeKaJe

"No OS is immune to stupidity, but at least in Linux you have to
actually make an effort to be stupid." -- Philip Callan in COLA

#3 (**permalink**) 02-21-2008, 10:05 AM

Peter Jensen wrote:
> Andrew Walker wrote:
>
>
>>I keep getting this message when I emerge packages, for example
>>
>>Please upgrade your package (libmpeg3-1.5.2) to use
>>toolchain-funcs.eclass
>>
>>While every thing seems to work ok, I can't help but be a little
>>concerned that there is something wrong. Is there something else that
>>is out of date causing this?
>
>
> You'll probably see a lot of these messages during unmerge of old
> packages, as they use the ebuilds that are stored in /var/db/pkg/.
> These can be quite obsolete by the time they're unmerged. At any rate,
> those kinds of notices are probably intended for the developers, so I
> don't think it's something you need to worry about.
>

Not all the maintainers do update their scripts in the same speed as there are
changes in the portage system, so those messages will be output while emerging
new packages.

//Aho

#4 (**permalink**) 02-21-2008, 10:05 AM

J.O. Aho wrote:

>> You'll probably see a lot of these messages during unmerge of old
>> packages, as they use the ebuilds that are stored in /var/db/pkg/.
>> These can be quite obsolete by the time they're unmerged. At any
>> rate, those kinds of notices are probably intended for the
>> developers, so I don't think it's something you need to worry about.
>
> Not all the maintainers do update their scripts in the same speed as
> there are changes in the portage system, so those messages will be
> output while emerging new packages.

Ah yes, if that was the case here, then it's probably time to check out
bugzilla for reports and report it if it's not mentioned. However, most
of the time you'll only see QA messages when you're unmerging old
packages. Still, if you're not the type that reads and reports bugs,
then it's probably safe to ignore the warnings.

--
PeKaJe

There is a new service pack that fixes all of IIS's problems
permanently. Go here to download it: http://www.apache.org

#5 (**permalink**) 02-21-2008, 10:05 AM

On Wed, 15 Jun 2005 11:00:04 +0000, Peter Jensen wrote:

> Andrew Walker wrote:
>
>> I keep getting this message when I emerge packages, for example
>>
>> Please upgrade your package (libmpeg3-1.5.2) to use
>> toolchain-funcs.eclass
>>
>> While every thing seems to work ok, I can't help but be a little
>> concerned that there is something wrong. Is there something else that
>> is out of date causing this?
>
> You'll probably see a lot of these messages during unmerge of old
> packages, as they use the ebuilds that are stored in /var/db/pkg/.
> These can be quite obsolete by the time they're unmerged. At any rate,
> those kinds of notices are probably intended for the developers, so I
> don't think it's something you need to worry about.

I'm not sure if I've been misunderstood. I get these messages when
actually installing packages, ie emerging, not unmerging.
For example when I did

emerge libmpeg3

it output

Please upgrade your package (libmpeg3-1.5.2) to use toolchain-funcs.eclass

during the compiling. I also noted it repeatedly when emerging alsa even
though it was the most up to date package available.
If you were refering to when emerge removes the previous version after a
successful install of a newer version, well, the previous version of alsa
was only a few months old if that.
I hope I explained that properly!

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

Please upgrade your package xxx to use toolchain-funcs.eclass?