[gentoo-amd64] revdep-rebuild rebuilding nonsense

[gentoo-amd64] revdep-rebuild rebuilding nonsense

[Dieter Ries]

[-- Attachment #1: Type: text/plain, Size: 720 bytes --]

Hi,

on my gentoo server box i did an emerge --depclean and revdep-rebuild 
afterwards, but now, revdep rebuild gives me the following output:

All prepared. Starting rebuild...
emerge --oneshot  =gnome-base/gnome-libs-1.4.2 =kde-base/kdepim-3.5.5-r2 
=media-gfx/gimp-2.2.12 =media-gfx/imagemagick-6.3.0.5 
=media-libs/gdk-pixbuf-0.22.0-r5 =media-video/mplayer-1.0_rc1 
=x11-libs/wxGTK-2.6.2-r1
..........
Calculating dependencies
emerge: there are no ebuilds to satisfy "=gnome-base/gnome-libs-1.4.2".


revdep-rebuild failed to emerge all packages



so why would revdep-rebuild emerge ebuilds which don't exist???

any ideas?

cu
Dieter

-- 
Frank Castle is dead!
Call me 'The PUNISHER'!

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-amd64] Re: revdep-rebuild rebuilding nonsense

[Harm Geerts]

On Wednesday 31 January 2007, Dieter Ries wrote:
> Hi,
>
> on my gentoo server box i did an emerge --depclean and revdep-rebuild
> afterwards, but now, revdep rebuild gives me the following output:
>
> All prepared. Starting rebuild...
> emerge --oneshot  =gnome-base/gnome-libs-1.4.2 =kde-base/kdepim-3.5.5-r2
> =media-gfx/gimp-2.2.12 =media-gfx/imagemagick-6.3.0.5
> =media-libs/gdk-pixbuf-0.22.0-r5 =media-video/mplayer-1.0_rc1
> =x11-libs/wxGTK-2.6.2-r1
> ..........
> Calculating dependencies
> emerge: there are no ebuilds to satisfy "=gnome-base/gnome-libs-1.4.2".
>
>
> revdep-rebuild failed to emerge all packages
>
> so why would revdep-rebuild emerge ebuilds which don't exist???

Because revdep-rebuild always merges the exact same version.
Otherwise you'd have a lot of trouble rebuilding/detecting broken slotted 
packages.

And because it makes more sense to force manual interaction then creating a 
broken tool. e.g. emerge gnome-base/gnome-libs yourself.
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] revdep-rebuild rebuilding nonsense

[Bo Ørsted Andresen]

[-- Attachment #1: Type: text/plain, Size: 625 bytes --]

On Wednesday 31 January 2007 23:56:33 Dieter Ries wrote:
> emerge: there are no ebuilds to satisfy "=gnome-base/gnome-libs-1.4.2".
>
> revdep-rebuild failed to emerge all packages
>
> so why would revdep-rebuild emerge ebuilds which don't exist???

Because you have it installed and it's broken. It was masked 2½ months ago [1]
and removed from the tree 5 weeks ago [2]. Just unmerge it if you don't need
it.

[1] http://sources.gentoo.org/viewcvs.py/gentoo-x86/profiles/package.mask?r1=1.6274&r2=1.6275
[2] http://sources.gentoo.org/viewcvs.py/gentoo-x86/gnome-base/gnome-libs/?hideattic=0

-- 
Bo Andresen

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-amd64] revdep-rebuild rebuilding nonsense

[Daiajo Tibdixious]

On 2/1/07, Dieter Ries <clip2@gmx.de> wrote:
> on my gentoo server box i did an emerge --depclean and revdep-rebuild
> afterwards, but now, revdep rebuild gives me the following output:

Just when thru this myself.

> emerge --oneshot  =gnome-base/gnome-libs-1.4.2 =kde-base/kdepim-3.5.5-r2
> =media-gfx/gimp-2.2.12 =media-gfx/imagemagick-6.3.0.5
> =media-libs/gdk-pixbuf-0.22.0-r5 =media-video/mplayer-1.0_rc1
> =x11-libs/wxGTK-2.6.2-r1

The important part is the "broken blah (requires blah blah blah)" lines.

> emerge: there are no ebuilds to satisfy "=gnome-base/gnome-libs-1.4.2".
> so why would revdep-rebuild emerge ebuilds which don't exist???

It's stupid. :) Its great at detecting broken linkage, lousy at fixing
it. I NEVER allow revdep-rebuild to rebuild ANYTHING. If I think the
"broken ..." actually match the list of packages, I'll emerge them
manually with --update.

Much less hassle that way.
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] revdep-rebuild rebuilding nonsense

[Daiajo Tibdixious]

On 2/1/07, Daiajo Tibdixious <daiajo@gmail.com> wrote:
> On 2/1/07, Dieter Ries <clip2@gmx.de> wrote:
> > on my gentoo server box i did an emerge --depclean and revdep-rebuild
> > afterwards, but now, revdep rebuild gives me the following output:
>
> Just when thru this myself.
>
> > emerge --oneshot  =gnome-base/gnome-libs-1.4.2 =kde-base/kdepim-3.5.5-r2
> > =media-gfx/gimp-2.2.12 =media-gfx/imagemagick-6.3.0.5
> > =media-libs/gdk-pixbuf-0.22.0-r5 =media-video/mplayer-1.0_rc1
> > =x11-libs/wxGTK-2.6.2-r1
>
> The important part is the "broken blah (requires blah blah blah)" lines.
>
> > emerge: there are no ebuilds to satisfy "=gnome-base/gnome-libs-1.4.2".
> > so why would revdep-rebuild emerge ebuilds which don't exist???
>
> It's stupid. :) Its great at detecting broken linkage, lousy at fixing
> it. I NEVER allow revdep-rebuild to rebuild ANYTHING. If I think the
> "broken ..." actually match the list of packages, I'll emerge them
> manually with --update.
>
> Much less hassle that way.
>
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] revdep-rebuild rebuilding nonsense

[Dieter Ries]

[-- Attachment #1: Type: text/plain, Size: 1298 bytes --]

Am Donnerstag 01 Februar 2007 00:17 schrieb Bo Ørsted Andresen:
> On Wednesday 31 January 2007 23:56:33 Dieter Ries wrote:
> > emerge: there are no ebuilds to satisfy "=gnome-base/gnome-libs-1.4.2".
> >
> > revdep-rebuild failed to emerge all packages
> >
> > so why would revdep-rebuild emerge ebuilds which don't exist???
>
> Because you have it installed and it's broken. It was masked 2½ months ago
> [1] and removed from the tree 5 weeks ago [2]. Just unmerge it if you don't
> need it.

OK, Thank you. that makes sense.

Am Donnerstag 01 Februar 2007 00:06 schrieb Harm Geerts:
> Because revdep-rebuild always merges the exact same version.
> Otherwise you'd have a lot of trouble rebuilding/detecting broken slotted
> packages.

Yes, I knew about that.

>
> And because it makes more sense to force manual interaction then creating a
> broken tool. e.g. emerge gnome-base/gnome-libs yourself.

Localhorst dieter # eix gnome-libs
No matches found.
Localhorst dieter # emerge -s gnome-libs
Searching...
[ Results for search key : gnome-libs ]
[ Applications found : 0 ]

You see my problem?

But now I know about it being removed from the tree, there should not be any 
more problems.

cu 

Dieter

-- 
Frank Castle is dead!
Call me 'The PUNISHER'!

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-amd64] revdep-rebuild rebuilding nonsense

[Bo Ørsted Andresen]

[-- Attachment #1: Type: text/plain, Size: 329 bytes --]

On Thursday 01 February 2007 00:20:12 Daiajo Tibdixious wrote:
> I NEVER allow revdep-rebuild to rebuild ANYTHING. If I think the
> "broken ..." actually match the list of packages, I'll emerge them
> manually with --update.

You haven't noticed the --package-names switch for revdep-rebuild, have you?

-- 
Bo Andresen

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-amd64] revdep-rebuild rebuilding nonsense

[Daiajo Tibdixious]

On 2/1/07, Bo Ørsted Andresen <bo.andresen@zlin.dk> wrote:
> On Thursday 01 February 2007 00:20:12 Daiajo Tibdixious wrote:
> > I NEVER allow revdep-rebuild to rebuild ANYTHING. If I think the
> > "broken ..." actually match the list of packages, I'll emerge them
> > manually with --update.
> You haven't noticed the --package-names switch for revdep-rebuild, have you?
Not until after I got in the habit of doing it manually in another window.
Besides I don't want the "broken ..." lines to scroll off the scroll
back buffer,
I like to keep them handy in case something goes wrong with the merge.

The main problem is that revdep-rebuild only fixes the case where the
"(requires blah)" blah has a newer version lying around, so the broken
.so can just be rebuilt to pick up the newer version. It doesn't
handle the case where the broken .so is an orphan, or belongs to a
package and is supposed to be manually deleted, or where blah simply
does not exist anymore, and its that package that needs to be emerged.
It also may be that package with the broken .so needs to be unmerged,
rather than rebuilt, in the case where its something installed but not
used any more.

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: revdep-rebuild rebuilding nonsense

[Daniel Gryniewicz]

On Thu, 2007-02-01 at 00:06 +0100, Harm Geerts wrote:
> On Wednesday 31 January 2007, Dieter Ries wrote:
> > Hi,
> >
> > on my gentoo server box i did an emerge --depclean and revdep-rebuild
> > afterwards, but now, revdep rebuild gives me the following output:
> >
> > All prepared. Starting rebuild...
> > emerge --oneshot  =gnome-base/gnome-libs-1.4.2 =kde-base/kdepim-3.5.5-r2
> > =media-gfx/gimp-2.2.12 =media-gfx/imagemagick-6.3.0.5
> > =media-libs/gdk-pixbuf-0.22.0-r5 =media-video/mplayer-1.0_rc1
> > =x11-libs/wxGTK-2.6.2-r1
> > ..........
> > Calculating dependencies
> > emerge: there are no ebuilds to satisfy "=gnome-base/gnome-libs-1.4.2".
> >
> >
> > revdep-rebuild failed to emerge all packages
> >
> > so why would revdep-rebuild emerge ebuilds which don't exist???
> 
> Because revdep-rebuild always merges the exact same version.
> Otherwise you'd have a lot of trouble rebuilding/detecting broken slotted 
> packages.
> 
> And because it makes more sense to force manual interaction then creating a 
> broken tool. e.g. emerge gnome-base/gnome-libs yourself.

Consider revdep-rebuild -X, which will merge the newest version of the
package, rather then the exact version.

That said, gnome-libs is gone from the tree.  All you can do is remove
it.

Daniel

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: revdep-rebuild rebuilding nonsense

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 335 bytes --]

On Wed, 31 Jan 2007 21:58:06 -0500, Daniel Gryniewicz wrote:

> That said, gnome-libs is gone from the tree.  All you can do is remove
> it.

That's not really true, there are alternatives to removing it, such as
keeping the ebuild in your overlay.


-- 
Neil Bothwick

Facts are stubborn, but statistics are more pliable

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]