Mailinglist Archive: opensuse-packaging (171 mails)
| < Previous | Next > |
[opensuse-packaging] python-gobject 2.90.x hit Factory
- From: Dimstar / Dominique Leuenberger <dimstar@xxxxxxxxxxxx>
- Date: Fri, 19 Aug 2011 17:17:12 +0200
- Message-id: <1313767042.28189.32.camel@3120-3560.ams.tmf-group.com>
Hi all,
We submitted an update of python-gobject to Factory.
The new version, 2.90.2 is now based PURELY on the gobject-introspection
based bindings and is not compatible to code relying on the old
bindings.
This link explains it better than I could ever write it:
http://www.j5live.com/2011/08/14/announce-pygobject-2-90-1-released-3-0-pre-release/
As this is of course a big change for Factory and the time to a final
release is getting shorter, we do not expact everybody to change their
codes (just yet).
So we also submitted the 'old' version to Factory as python-gobject2
(the new version will become 3.0 when it's fully ready).
python-gobject2 is not yet available in Factory (as of now), but that is
likely to change in the not to distant future (SR pending).
A big amount of packages might have turned into 'Unresolvable' after
this change, as they were (still) BuildRequiring python-gobject2-devel
(which in turn was a virtual symbol provided) or they are BuildRequiring
pkgconfig(pygobject-2.0). For those packages, the virtue is patiance:
simply wait and the problem will get sorted for you with the 'old'
version being checked in.
The ones BuildRequiring python-gobject-devel will need to verify if
their code does what it is supposed to to. Failures to build or start
might hint that the other bindings are required.
I hopes not to many started debugging their new build Failures or
expansion errors yet.
Best regards,
Dominique
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-packaging+help@xxxxxxxxxxxx
We submitted an update of python-gobject to Factory.
The new version, 2.90.2 is now based PURELY on the gobject-introspection
based bindings and is not compatible to code relying on the old
bindings.
This link explains it better than I could ever write it:
http://www.j5live.com/2011/08/14/announce-pygobject-2-90-1-released-3-0-pre-release/
As this is of course a big change for Factory and the time to a final
release is getting shorter, we do not expact everybody to change their
codes (just yet).
So we also submitted the 'old' version to Factory as python-gobject2
(the new version will become 3.0 when it's fully ready).
python-gobject2 is not yet available in Factory (as of now), but that is
likely to change in the not to distant future (SR pending).
A big amount of packages might have turned into 'Unresolvable' after
this change, as they were (still) BuildRequiring python-gobject2-devel
(which in turn was a virtual symbol provided) or they are BuildRequiring
pkgconfig(pygobject-2.0). For those packages, the virtue is patiance:
simply wait and the problem will get sorted for you with the 'old'
version being checked in.
The ones BuildRequiring python-gobject-devel will need to verify if
their code does what it is supposed to to. Failures to build or start
might hint that the other bindings are required.
I hopes not to many started debugging their new build Failures or
expansion errors yet.
Best regards,
Dominique
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-packaging+help@xxxxxxxxxxxx
| < Previous | Next > |