| Summary: | dev-python/libgnome-python-2.28.0: Deprecation Warning: Not passing of paths to python_mod_cleanup() is deprecated | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Lasse Bigum <lasse> |
| Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Lasse Bigum
2010-07-05 18:22:29 UTC
Are you sure it wasn't due to unmerge of previous version ? It happened as part of a revdep-rebuild due to libpng12 So no, it did not remove an older version. emerge.log: 1278321969: === (1 of 29) Post-Build Cleaning (x11-libs/cairo-1.8.8::/usr/portage/x11-libs/cairo/cairo-1.8.8.ebuild) 1278321969: ::: completed emerge (1 of 29) x11-libs/cairo-1.8.8 to / 1278321969: >>> emerge (2 of 29) dev-python/libgnomecanvas-python-2.28.0 to / 1278321972: === (2 of 29) Cleaning (dev-python/libgnomecanvas-python-2.28.0::/usr/portage/dev-python/libgnomecanvas-python/libgnomecanvas-python-2.28.0.ebuild) 1278321972: === (2 of 29) Compiling/Merging (dev-python/libgnomecanvas-python-2.28.0::/usr/portage/dev-python/libgnomecanvas-python/libgnomecanvas-python-2.28.0.ebuild) 1278322025: *** Finished. Cleaning up... 1278322025: *** exiting unsuccessfully with status '1'. 1278322027: *** terminating. 1278322223: Started emerge on: Jul 05, 2010 11:30:23 1278322223: *** emerge --oneshot dev-dotnet/libgdiplus:0 dev-lang/php:5 dev-perl/perl-tk:0 dev-python/libbonobo-python:2 dev-python/libgnomecanvas-python:2 dev-python/libgnome-python:2 dev-python/pygtk:2 gnome-base/gconf:2 gnome-base/gd m:0 gnome-base/gnome-desktop:0 gnome-base/gnome-mount:0 gnome-base/libbonoboui:0 gnome-base/libgnomeui:0 gnome-base/librsvg:2 media-gfx/graphviz:0 media-gfx/imagemagick:0 media-libs/gd:2 media-libs/imlib2:0 media-libs/netpbm:0 media-libs /sdl-image:0 net-analyzer/ntop:0 net-analyzer/rrdtool:0 net-im/pidgin:0 www-client/links:2 x11-libs/cairo:0 x11-libs/gksu:0 x11-libs/gtk+:2 x11-libs/libgksu:2 x11-libs/pango:0 1278322248: >>> emerge (1 of 29) x11-libs/cairo-1.8.8 to / 1278322253: === (1 of 29) Cleaning (x11-libs/cairo-1.8.8::/usr/portage/x11-libs/cairo/cairo-1.8.8.ebuild) 1278322253: === (1 of 29) Compiling/Merging (x11-libs/cairo-1.8.8::/usr/portage/x11-libs/cairo/cairo-1.8.8.ebuild) 1278322539: === (1 of 29) Merging (x11-libs/cairo-1.8.8::/usr/portage/x11-libs/cairo/cairo-1.8.8.ebuild) 1278322547: >>> AUTOCLEAN: x11-libs/cairo:0 1278322547: === Unmerging... (x11-libs/cairo-1.8.8) 1278322550: >>> unmerge success: x11-libs/cairo-1.8.8 1278322555: === (1 of 29) Post-Build Cleaning (x11-libs/cairo-1.8.8::/usr/portage/x11-libs/cairo/cairo-1.8.8.ebuild) 1278322555: ::: completed emerge (1 of 29) x11-libs/cairo-1.8.8 to / 1278322555: >>> emerge (2 of 29) dev-python/libgnomecanvas-python-2.28.0 to / 1278322558: === (2 of 29) Cleaning (dev-python/libgnomecanvas-python-2.28.0::/usr/portage/dev-python/libgnomecanvas-python/libgnomecanvas-python-2.28.0.ebuild) 1278322558: === (2 of 29) Compiling/Merging (dev-python/libgnomecanvas-python-2.28.0::/usr/portage/dev-python/libgnomecanvas-python/libgnomecanvas-python-2.28.0.ebuild) 1278322609: *** Finished. Cleaning up... 1278322609: *** exiting unsuccessfully with status '1'. 1278322610: *** terminating. When it finally succeeded, but gave me the error warning, it was this: 1278336116: >>> emerge (9 of 16) dev-python/pygtk-2.16.0-r1 to / 1278336119: === (9 of 16) Cleaning (dev-python/pygtk-2.16.0-r1::/usr/portage/dev-python/pygtk/pygtk-2.16.0-r1.ebuild) 1278336119: === (9 of 16) Compiling/Merging (dev-python/pygtk-2.16.0-r1::/usr/portage/dev-python/pygtk/pygtk-2.16.0-r1.ebuild) 1278336539: === (9 of 16) Merging (dev-python/pygtk-2.16.0-r1::/usr/portage/dev-python/pygtk/pygtk-2.16.0-r1.ebuild) 1278336555: >>> AUTOCLEAN: dev-python/pygtk:2 1278336555: === Unmerging... (dev-python/pygtk-2.16.0-r1) 1278336560: >>> unmerge success: dev-python/pygtk-2.16.0-r1 1278336568: === (9 of 16) Post-Build Cleaning (dev-python/pygtk-2.16.0-r1::/usr/portage/dev-python/pygtk/pygtk-2.16.0-r1.ebuild) 1278336568: ::: completed emerge (9 of 16) dev-python/pygtk-2.16.0-r1 to / 278322539: === (1 of 29) Merging (x11-libs/cairo-1.8.8::/usr/portage/x11-libs/cairo/cairo-1.8.8.ebuild) 1278322547: >>> AUTOCLEAN: x11-libs/cairo:0 1278322547: === Unmerging... (x11-libs/cairo-1.8.8) 1278322550: >>> unmerge success: x11-libs/cairo-1.8.8 You were saying ? As seen above, unmerge of the old version happens even during rebuild, it simply has a more narrow scope then. Are we misunderstanding each other now? Why are you being condescending? You asked: Are you sure it wasn't due to unmerge of previous version ? You wrote previous version, which I took to mean "older", sorry if I misunderstood that part. I then quote the log, and then you quote a totally different module? What has cairo got to do with this? I agree that I unmerge a "previous version" if that also includes the same version being removed due to a rebuild. Can we please restart the discussion now as I hope I made more sense now. Today I'm bit short on patience. In your paste, there was no libgnome-python block, but you should have noticed the pattern: after merging an already existing package (with no slot change), unmerge of the old version is run - that holds for rebuilds. What I'm saying is that most likely that message came from unmerge phase, that was using a stored old ebuild. Try to reemerge it again, if there's no message, that was the cause. Tried reinstalling, and you are correct, no warnings. Closing as INVALID. |