[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
pkg/42894: bogus py25-gtk2 package created
>Synopsis: bogus py25-gtk2 package created
>Arrival-Date: Sat Feb 27 23:15:00 +0000 2010
>Originator: David A. Holland
>Release: NetBSD 4.99.72, pkgsrc 20100226
System: NetBSD valkyrie 4.99.72 NetBSD 4.99.72 (VALKYRIE) #32: Sat Oct 4
12:25:22 EDT 2008 root@valkyrie:/usr/src/sys/arch/amd64/compile/VALKYRIE amd64
I now have a py25-gtk2 package that has the following curious property:
% pkg_info -n py25-gtk2
Information for py25-gtk2-2.16.0:
This information appears to be lying:
% head -1 /usr/pkg/bin/pygtk-demo
so it is probably only administratively incorrect and not totally broken.
This package was generated as a result of 'make update' in gtk2 when
driconf was installed. gtk2 is used by py25-gtk2 is used by driconf.
driconf sets PYTHON_VERSIONS_ACCEPTED=25 24, so with the default
python now being 26 the straightforward things don't work.
The update first bombs out partway through because it thinks py25-gtk2
should be installed but it isn't -- this appears to be because it
builds and installs py26-gtk2 instead. Restarting the update allows it
to complete but produces the broken package described above.
dunno. Probably 'make update' needs to store python version numbers or
extra make defs or something in .DDIR/.DLIST (or something) so as to
accurately rebuild what was previously there.
I'm not sure what will happen if you have both py25-gtk2 and py26-gtk2
installed at once, have nothing pkgsrc knows about that depends on
either, and make update in gtk2; my guess however is that py25-gtk2
will silently evaporate. This is not particularly desirable.
(A complicating issue in this is that py25-gtk2 and py26-gtk2
shouldn't be allowed to be both installed at once, as they conflict
with one another. So do py25-gobject and py26-gobject, for that
matter. This is not however currently declared anywhere.)
Main Index |
Thread Index |