Re: .la file removal, multiarch for plugins
Hi Lionel, On Sun, Jul 10, 2011 at 04:48:16PM +0200, Lionel Elie Mamane wrote: > >>> To finish an old release goal from Squeeze, to comply with Policy > >>> 10.2 and to ease the introduction of MultiArch, I'm filing bugs > >>> against packages which contain .la files which can be either removed > >>> or stripped of the dependency_libs variable. > >> Policy 10.2 says: > >> These requirements for handling of .la files do not apply to loadable > >> modules or libraries not installed in directories searched by default > >> by the dynamic linker. > > All true, but (...) clearing the dependency_libs field in the .la > > file is still necessary even if the .la file is retained for the > > purposes of things like libltdl. (It is also safe for libltdl usage > > as this relies on a different part of the .la file.) > OK. What is slightly unclear to me, is that "being loaded by libltdl" > is a thing that is external to the package. If there is *one* program > anywhere (even not packaged in Debian or local to an enterprise) that > uses libltdl to load library foo, we break that program by removing > the .la file. So I don't really understand why we (we=Debian) consider > it a good thing to remove the .la file, even if nothing in Debian, or > nothing we know of, uses libltdl to load that library. If we're talking about shared libraries, this is a non issue. the .la file is named like the .so symlink, i.e. without the soname; dlopening a shared library without specifying an soname is Broken and Wrong. So there's no reason for us to worry about breaking something that's already entirely broken. For plugins / DSOs, it's important to not break compatibility with other software that might be opening them in a way that references the .la file, true; but in most cases these are plugins for a specific piece of software, so we know conclusively whether or not the .la file is used for the lookup. In this respect, ODBC is a special case. The UnixODBC documentation and examples certainly all use the .so, not the .la, but ODBC drivers can also be used directly without going through the driver manager, and if the .la exists on the system then it's always possible that someone has referenced it in their odbcinst.ini, too. So if you are concerned that users are referencing a .la file for an ODBC driver, it's not a bug for you to leave it in place indefinitely. However, I think this is a really small compatibility break and would personally not worry much that this would have an impact on users. > > With MultiArch, you may still get problems here because those > > directories will be changing. If those paths are within the sole > > control of this package, fine - both parts can change at the same time. > > If you're relying on paths which come from a separate source package, > > it'll likely break. > I suppose we'll have a controlled / synchronised migration for all > ODBC drivers? Or should each driver just unilaterally stick > $(dpkg-architecture -qDEB_HOST_MULTIARCH) somewhere in the path? > I presume that > /usr/lib/$(dpkg-architecture -qDEB_HOST_MULTIARCH)/odbc > is better than > /usr/lib/odbc/$(dpkg-architecture -qDEB_HOST_MULTIARCH) > This would work for ODBC drivers because they are registered anyway, > so really, (if I understand well) as far as the ODBC libraries and > applications are concerned, they can be anywhere. Nevertheless, IMHO, > it would be "cleaner" if all ODBC drivers made the same choice. I think it would be premature for ODBC drivers to switch to multiarch paths. There would be no benefit, because the ODBC driver manager doesn't have a search path for drivers that includes any multiarch paths, so you would have to hard-code the driver path in the odbcinst.ini - so then it's architecture-specific anyway and you've gained no ability to use drivers for multiple architectures side-by-side! Multiarch is a transition that will have a very long tail, and that's perfectly ok. There's certainly no need to rush to convert things to new paths where there isn't a clear and understood benefit. > Other loadable libraries (typically plugins / extensions; I'm thinking > of my xchat-guile package here) that are dlopen()ed or loaded using > libltdl, I presume the loading application will have to be fixed to > lead from a multiarch path anyway, so the plugins have to wait for the > app to do it first. Yes. For examples of how this can be done, feel free to look at the gdk-pixbuf and glib2.0 patches. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Bug#632073: marked as done (/usr/lib/python2.7/dist-packages/camelot/art/tango missing)
Your message dated Wed, 20 Jul 2011 21:32:28 + with message-id and subject line Bug#632073: fixed in camelot 11.05.13-c1-3 has caused the Debian Bug report #632073, regarding /usr/lib/python2.7/dist-packages/camelot/art/tango missing to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 632073: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632073 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-camelot Version: 11.05.13-c1-1 Severity: normal User: debian-pyt...@lists.debian.org Usertags: python2.7 Tags: patch /usr/lib/python2.6/dist-packages/camelot/art/tango exists, but /usr/lib/python2.7/dist-packages/camelot/art/tango does not. -- Jakub Wilk diff -u camelot-11.05.13-c1/debian/rules camelot-11.05.13-c1/debian/rules --- camelot-11.05.13-c1/debian/rules +++ camelot-11.05.13-c1/debian/rules @@ -56,8 +56,8 @@ echo "fixed interpreter: $$i"; \ fi; \ done - dh_python2 dh_link /usr/share/icons/Tango /usr/lib/python$(PYVER)/dist-packages/camelot/art/tango + dh_python2 dh_compress -X.py dh_fixperms dh_installdeb --- End Message --- --- Begin Message --- Source: camelot Source-Version: 11.05.13-c1-3 We believe that the bug you reported is fixed in the latest version of camelot, which is due to be installed in the Debian FTP archive: camelot_11.05.13-c1-3.diff.gz to main/c/camelot/camelot_11.05.13-c1-3.diff.gz camelot_11.05.13-c1-3.dsc to main/c/camelot/camelot_11.05.13-c1-3.dsc python-camelot-doc_11.05.13-c1-3_all.deb to main/c/camelot/python-camelot-doc_11.05.13-c1-3_all.deb python-camelot_11.05.13-c1-3_all.deb to main/c/camelot/python-camelot_11.05.13-c1-3_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 632...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Piotr Ożarowski (supplier of updated camelot package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 20 Jul 2011 23:11:39 +0200 Source: camelot Binary: python-camelot python-camelot-doc Architecture: source all Version: 11.05.13-c1-3 Distribution: unstable Urgency: low Maintainer: Debian QA Group Changed-By: Piotr Ożarowski Description: python-camelot - camelot - a GUI framework inspired by Django python-camelot-doc - camelot - a GUI framework inspired by Django - documentation Closes: 632073 Changes: camelot (11.05.13-c1-3) unstable; urgency=low . * QA upload. * Replace python-jinja with python-jinja2 in Depends (camelot module is using jinja2, not jinja) * Invoke dh_python2 after creating Tango symlink (fixes Python 2.7 support, closes: 632073, thanks to Jakub Wilk for the patch) Checksums-Sha1: 7a887d767f7759bca44f191acf3582244455a46d 1774 camelot_11.05.13-c1-3.dsc d2d64ee7be1fa491cf0da170ccdaec341c028382 7578 camelot_11.05.13-c1-3.diff.gz 0a8838bff7825fa19d98d8272350aa74cf221c9b 507954 python-camelot_11.05.13-c1-3_all.deb 8fff1fc3db7f18be9e1eff68002184eb04f7bb20 1319082 python-camelot-doc_11.05.13-c1-3_all.deb Checksums-Sha256: fb999ffd3212234a8e08f08a84d501f6ffeae4eb45fac62542dd2f78991d7134 1774 camelot_11.05.13-c1-3.dsc 2d026a3a08bf934e43f6061f90deea3cccb237150af0a12cb83819a92f70aa02 7578 camelot_11.05.13-c1-3.diff.gz 5df1929d5c78996b7fa8c945e0d1f26329a99b16af1b71fed3923fe680cbd24d 507954 python-camelot_11.05.13-c1-3_all.deb d65222ad1ad424d6e5016c2b28b9d3c915cd76e3f169a37d7c15a23f3cb7b3f1 1319082 python-camelot-doc_11.05.13-c1-3_all.deb Files: 4865fe14e8e5b86426f047f91dfe2baa 1774 python optional camelot_11.05.13-c1-3.dsc bc297e83b215a675b81f59b4875da0ea 7578 python optional camelot_11.05.13-c1-3.diff.gz cf26b3f0ff582bdac40b7b8f66b793b0 507954 python optional python-camelot_11.05.13-c1-3_all.deb b8d9acb3b5bb397f2f8d948e68ba9413 1319082 doc optional python-camelot-doc_11.05.13-c1-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCgAGBQJOJ0ZjAAoJEK728aKnRXZF9MAP/A7xwa6wJ4YCBrfKDE5gsg9S HCVRGrFIbpiBeUPx7nNYBrHmyT4p3oTiEnv8qOO1twBvCyswBjmV6ScreOWzp47i bucOOoEWZibyv/xXosDM4IA7ZcreZiQ8xLJeVtDZoEbx7y7ThFZ9O907+cDvndWp uNiPmFIq07bs3tCpwBg7P0NLKb9gpcC7UqRoyIjCVvX8MJGGHAD9xO2ukamcYh7p biujAi2h/tq3A7r44brDgIam/LkHYFfBD/ZsKayAflpJzcd6H6nPzcQgL8ATEV/q 91v7fUheohFxNR2UmLSqPtg
Processing of camelot_11.05.13-c1-3_amd64.changes
camelot_11.05.13-c1-3_amd64.changes uploaded successfully to localhost along with the files: camelot_11.05.13-c1-3.dsc camelot_11.05.13-c1-3.diff.gz python-camelot_11.05.13-c1-3_all.deb python-camelot-doc_11.05.13-c1-3_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1qjeeh-0006xr...@franck.debian.org
camelot_11.05.13-c1-3_amd64.changes ACCEPTED into unstable
Accepted: camelot_11.05.13-c1-3.diff.gz to main/c/camelot/camelot_11.05.13-c1-3.diff.gz camelot_11.05.13-c1-3.dsc to main/c/camelot/camelot_11.05.13-c1-3.dsc python-camelot-doc_11.05.13-c1-3_all.deb to main/c/camelot/python-camelot-doc_11.05.13-c1-3_all.deb python-camelot_11.05.13-c1-3_all.deb to main/c/camelot/python-camelot_11.05.13-c1-3_all.deb Override entries for your package: camelot_11.05.13-c1-3.dsc - source python python-camelot-doc_11.05.13-c1-3_all.deb - optional doc python-camelot_11.05.13-c1-3_all.deb - optional python Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 632073 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1qjeny-0007we...@franck.debian.org
Bug#627350: python-django-authority and python-camelot: error when trying to install together
clone 627350 -1 reassign 627350 python-camelot 11.05.13-c1-1 found 627350 11.05.13-c1-2 retitle 627350 python-camelot: ships Python module "example" reassign -1 python-django-authority 0.4-1 retitle -1 python-django-authority: ships Python module "example" thanks * Ralf Treinen , 2011-05-19, 21:36: dpkg: error processing /var/cache/apt/archives/python-django-authority_0.4-1_all.deb (--unpack): trying to overwrite '/usr/share/pyshared/example/settings.py', which is also in package python-camelot 11.05.13-c1-1 configured to not write apport reports Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/python-django-authority_0.4-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) I don't think it's appropriate for either of packages to ship a Python module with such a generic name. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110720221556.ga2...@jwilk.net
Processed: Re: Bug#627350: python-django-authority and python-camelot: error when trying to install together
Processing commands for cont...@bugs.debian.org: > clone 627350 -1 Bug#627350: python-django-authority and python-camelot: error when trying to install together Bug 627350 cloned as bug 634923. > reassign 627350 python-camelot 11.05.13-c1-1 Bug #627350 [python-camelot,python-django-authority] python-django-authority and python-camelot: error when trying to install together Bug reassigned from package 'python-camelot,python-django-authority' to 'python-camelot'. Bug No longer marked as found in versions python-camelot/11.05.13-c1-2. Bug #627350 [python-camelot] python-django-authority and python-camelot: error when trying to install together Bug Marked as found in versions camelot/11.05.13-c1-1. > found 627350 11.05.13-c1-2 Bug #627350 [python-camelot] python-django-authority and python-camelot: error when trying to install together Bug Marked as found in versions camelot/11.05.13-c1-2. > retitle 627350 python-camelot: ships Python module "example" Bug #627350 [python-camelot] python-django-authority and python-camelot: error when trying to install together Changed Bug title to 'python-camelot: ships Python module "example"' from 'python-django-authority and python-camelot: error when trying to install together' > reassign -1 python-django-authority 0.4-1 Bug #634923 [python-camelot,python-django-authority] python-django-authority and python-camelot: error when trying to install together Bug reassigned from package 'python-camelot,python-django-authority' to 'python-django-authority'. Bug No longer marked as found in versions python-camelot/11.05.13-c1-2. Bug #634923 [python-django-authority] python-django-authority and python-camelot: error when trying to install together Bug Marked as found in versions django-authority/0.4-1. > retitle -1 python-django-authority: ships Python module "example" Bug #634923 [python-django-authority] python-django-authority and python-camelot: error when trying to install together Changed Bug title to 'python-django-authority: ships Python module "example"' from 'python-django-authority and python-camelot: error when trying to install together' > thanks Stopping processing here. Please contact me if you need assistance. -- 634923: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634923 627350: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627350 -1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=-1 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.131120016030373.transcr...@bugs.debian.org
Bug#627350: python-django-authority and python-camelot: error when trying to install together
On Thu, Jul 21, 2011 at 12:15:56AM +0200, Jakub Wilk wrote: > >Processing triggers for man-db ... > >Errors were encountered while processing: > >/var/cache/apt/archives/python-django-authority_0.4-1_all.deb > >E: Sub-process /usr/bin/dpkg returned an error code (1) > > I don't think it's appropriate for either of packages to ship a > Python module with such a generic name. Agreed. -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110720230429.ga22...@scru.org
Bug#627350: python-django-authority and python-camelot: error when trying to install together
This has been changed in the trunk of Camelot to camelot_example when a new release is ready, this will be solved from the Camelot side On Thu, Jul 21, 2011 at 12:15 AM, Jakub Wilk wrote: > clone 627350 -1 > reassign 627350 python-camelot 11.05.13-c1-1 > found 627350 11.05.13-c1-2 > retitle 627350 python-camelot: ships Python module "example" reassign -1 > python-django-authority 0.4-1 > retitle -1 python-django-authority: ships Python module "example" > thanks > > * Ralf Treinen , 2011-05-19, 21:36: >> >> dpkg: error processing >> /var/cache/apt/archives/python-django-authority_0.4-1_all.deb (--unpack): >> trying to overwrite '/usr/share/pyshared/example/settings.py', which is >> also in package python-camelot 11.05.13-c1-1 >> configured to not write apport reports >> Processing triggers for man-db ... >> Errors were encountered while processing: >> /var/cache/apt/archives/python-django-authority_0.4-1_all.deb >> E: Sub-process /usr/bin/dpkg returned an error code (1) > > I don't think it's appropriate for either of packages to ship a Python > module with such a generic name. > > -- > Jakub Wilk > > > > -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cahubdb2hgimud7f7ch0i_k15cnh_mzknsbdmbai78kkqzn8...@mail.gmail.com
Processed: found 627350 in python-camelot/11.05.13-c1-3
Processing commands for cont...@bugs.debian.org: > found 627350 python-camelot/11.05.13-c1-3 Bug #627350 [python-camelot] python-camelot: ships Python module "example" The source python-camelot and version 11.05.13-c1-3 do not appear to match any binary packages Bug Marked as found in versions python-camelot/11.05.13-c1-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 627350: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627350 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.131122967328255.transcr...@bugs.debian.org
