Bug 280 – Updating PySide 0.4.0 from extras-devel repository report error

PySide Bugzilla Closed for New Bugs

PySide is now a Qt Add-on and uses the Qt Project's JIRA Bug Tracker instead of this Bugzilla instance. This Bugzilla is left for reference purposes.

Bug 280 - Updating PySide 0.4.0 from extras-devel repository report error

Summary:

Updating PySide 0.4.0 from extras-devel repository report error

Status:	CLOSED FIXED

Product:	PySide
Classification:	Unclassified
Component:	packaging
Version:	0.4.0
Platform:	Other Linux

Importance:	P5 major
Assigned To:	renato filho

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2010-08-05 01:34 EEST by Benoît HERVIER
Modified:	2010-10-13 13:48 EEST (History)
CC List:	12 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Benoît HERVIER 2010-08-05 01:34:53 EEST

On a Maemo Device running last Maemo version and using extras devel repository,
While upgrading to pyside 0.4.0 from pyside 0.3.2 with a simple apt-get upgrade
i got dpkg subprocess error as one file of libpyside0.4 already exist and is
owned by libpyside0.3.

I ve to apt-get remove every apps depending on pyside + python-pyside,
pyside-qt4*, libpyside0.3

Comment 1 Matti Airas 2010-08-05 04:08:39 EEST

According to the mailing list, the same bug also applies to the PPA deb
packages (reported on Linux Mint).

Comment 2 Didier Raboud 2010-08-05 04:12:48 EEST

Hi, 

this was very likely to happen on the Debian packages, so I preventively fixed
that with that commit:

http://svn.debian.org/wsvn/python-modules/?op=comp&compare%5B%5D=%2Fpackages%2Fpyside@14133&compare%5B%5D=%2Fpackages%2Fpyside@14134

Cheers, 

OdyX

Comment 3 Carlos Gonçalves 2010-08-05 07:34:30 EEST

JFYI, it was fixed on Maemo 6
(http://qt.gitorious.org/pyside/packaging/commit/b6c76771bb1ec9b85f67442814a2bdd9ac552d0e)
and Maemo, so just on Ubuntu it is missing.

Comment 4 Didier Raboud 2010-08-05 09:32:01 EEST

Re #3: IMHO that is not sufficient as it will produce new bugs at each soname
transition: look at my patch on the Debian side: I moved the "constantly named"
files from libpyside* to libpyside-dev.

Comment 5 renato filho 2010-08-05 09:37:11 EEST

We found this problem yesterday, and we decide to move the files like pyside.pc
to pysideX.Y.pc this will avoid that error in future release, what do you think
about that?

Comment 6 Didier Raboud 2010-08-05 12:09:32 EEST

Hrm. I'm not sure it still works with pkg-config… And I just put the
non-varying files to libpyside-dev, which "just works".

Comment 7 renato filho 2010-08-05 14:09:28 EEST

this work with glib-2.0, libxm-2.0 and others, it will be the same case to
libshiboken and libpyside.

but you need specify the complete package name.

Comment 8 Bruno Araujo 2010-09-04 12:09:01 EEST

As this problem isn't a packaging issue anymore at this point, reassigning it
to Renato.

Comment 9 renato filho 2010-09-21 16:52:59 EEST

Implemented a cmake flag "USE_VERSION_SUFFIX" to avoid this kind of error, now
you can use this flag to have more then one version of the same library
installed at the same time.

New packages generated and uploaded, I will close the bug, if the problem still
happening with new packages please fell free to reopen.

Comment 10 renato filho 2010-10-13 13:48:23 EEST

released on PySide 0.4.2