[gentoo-user] weird portage warning

[gentoo-user] weird portage warning

[Philip Webb]

For the past few weeks, I have noticed the following bizarre msg :

  root:503 ~> emerge -Dup world
  These are the packages that would be merged, in order:
  Calculating dependencies |
  * Please fix your ebuild to not inherit the deprecated qt3.eclass
  * Please fix your ebuild to not inherit the deprecated qt3.eclass
  * Please fix your ebuild to not inherit the deprecated qt3.eclass
  ... done!

Yes, I have the KDE 3 overlay installed,
but even so how can a mere user be expected to "fix an ebuild",
whatever that may mean anyway.  Can anyone enlighten me
as to the cause &/or purpose of these repeated msgs ?

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

Re: [gentoo-user] weird portage warning

[Volker Armin Hemmann]

On Sonntag 02 Mai 2010, Philip Webb wrote:
> For the past few weeks, I have noticed the following bizarre msg :
> 
>   root:503 ~> emerge -Dup world
>   These are the packages that would be merged, in order:
>   Calculating dependencies |
>   * Please fix your ebuild to not inherit the deprecated qt3.eclass
>   * Please fix your ebuild to not inherit the deprecated qt3.eclass
>   * Please fix your ebuild to not inherit the deprecated qt3.eclass
>   ... done!
> 
> Yes, I have the KDE 3 overlay installed,
> but even so how can a mere user be expected to "fix an ebuild",
> whatever that may mean anyway.  Can anyone enlighten me
> as to the cause &/or purpose of these repeated msgs ?

the cause: the qt3.eclass is deprecated (because qt3 and everything depending 
on it is 'dead'). The ebuilds use this eclass, portage warns about it.
There is nothing you can do about it.

But hopefully you have the eclass into your overlay too...

Re: [gentoo-user] weird portage warning

[Petric Frank]

Hello,

Am Sonntag 02 Mai 2010 08:56:29 schrieb Volker Armin Hemmann:
> On Sonntag 02 Mai 2010, Philip Webb wrote:
> > For the past few weeks, I have noticed the following bizarre msg :
> >
> >   root:503 ~> emerge -Dup world
> >   These are the packages that would be merged, in order:
> >   Calculating dependencies |
> >   * Please fix your ebuild to not inherit the deprecated qt3.eclass
> >   * Please fix your ebuild to not inherit the deprecated qt3.eclass
> >   * Please fix your ebuild to not inherit the deprecated qt3.eclass
> >   ... done!
> >
> > Yes, I have the KDE 3 overlay installed,
> > but even so how can a mere user be expected to "fix an ebuild",
> > whatever that may mean anyway.  Can anyone enlighten me
> > as to the cause &/or purpose of these repeated msgs ?
> 
> the cause: the qt3.eclass is deprecated (because qt3 and everything
>  depending on it is 'dead'). The ebuilds use this eclass, portage warns
>  about it. There is nothing you can do about it.

But there should a note *which* ebuild have to be fixed, right ?

regards

Re: [gentoo-user] weird portage warning

[Volker Armin Hemmann]

On Sonntag 02 Mai 2010, Petric Frank wrote:
> Hello,
> 
> Am Sonntag 02 Mai 2010 08:56:29 schrieb Volker Armin Hemmann:
> > On Sonntag 02 Mai 2010, Philip Webb wrote:
> > > For the past few weeks, I have noticed the following bizarre msg :
> > >   root:503 ~> emerge -Dup world
> > >   These are the packages that would be merged, in order:
> > >   Calculating dependencies |
> > >   * Please fix your ebuild to not inherit the deprecated qt3.eclass
> > >   * Please fix your ebuild to not inherit the deprecated qt3.eclass
> > >   * Please fix your ebuild to not inherit the deprecated qt3.eclass
> > >   ... done!
> > > 
> > > Yes, I have the KDE 3 overlay installed,
> > > but even so how can a mere user be expected to "fix an ebuild",
> > > whatever that may mean anyway.  Can anyone enlighten me
> > > as to the cause &/or purpose of these repeated msgs ?
> > 
> > the cause: the qt3.eclass is deprecated (because qt3 and everything
> > 
> >  depending on it is 'dead'). The ebuilds use this eclass, portage warns
> >  about it. There is nothing you can do about it.
> 
> But there should a note *which* ebuild have to be fixed, right ?
> 
> regards

that warning is not meant for you - the user - but devs. You don't fix the 
ebuild. Just ignore the warning. And if you are curios - grep is your friend.