Bug#498700: [DRE-maint] Bug#498700: Missing upgrade path from libdb4.2-ruby1.8 to libdb-ruby1.8
On Tue, Oct 14, 2008 at 09:31:24PM +0200, Lucas Nussbaum wrote: On 11/10/08 at 22:34 +0200, Julian Andres Klode wrote: [...] Please note that I have almost no experience with SQL stuff. This is just the basic idea and needs real improvements. (Would be a good QA test, in my opinion). [...] Indeed. Do you have time to work on that? Yes. I'll take a closer look at it this weekend, and also try to write a script which outputs the old package and the new package(s) providing it. -- Julian Andres Klode - Free Software Developer Debian Developer - Contributing Member of SPI Ubuntu Member - Fellow of FSFE Website: http://jak-linux.org/ XMPP: [EMAIL PROTECTED] Debian: http://www.debian.org/ SPI: http://www.spi-inc.org/ Ubuntu: http://www.ubuntu.com/ FSFE: http://www.fsfe.org/ signature.asc Description: Digital signature
Bug#498700: [DRE-maint] Bug#498700: Missing upgrade path from libdb4.2-ruby1.8 to libdb-ruby1.8
On 11/10/08 at 22:34 +0200, Julian Andres Klode wrote: On Sun, Sep 28, 2008 at 05:30:10PM +0200, Lucas Nussbaum wrote: On 28/09/08 at 15:06 +0200, Frans Pop wrote: On Sunday 28 September 2008, Adeodato Simó wrote: Isn't this a bug of our upgrading tools, that should prefer to install a new, non-obsolete package A that Provides: B, rather than keeping a no-longer-present-in-the-lists B installed? Possibly. But as long as those tools don't support that it will have to be solved in the packages themselves. I'm wondering how many cases like that are still in lenny. That is: - binary package in etch - that is not in lenny - that is Replaced/Provided by another package You can use UDD to find it out. I failed to create something fast, but here is my code (it's too slow to output something): select package from packages_summary where ( release='etch' and package not in (select package from packages_summary where release='lenny') and exists ( select package from packages where ( release='lenny' and ARRAY[packages_summary.package] @ string_to_array(provides, ', ') ) ) ); Nice work :-) I made it return a result by splitting the query and using another table: select distinct package, string_to_array(replace(provides, ' ', ''), ',') into table packages_provides from packages where distribution = 'debian' and release = 'lenny' and provides != ''; select package into table missing_provides from packages_summary where distribution = 'debian' and release = 'etch' and package not in (select package from packages_summary where distribution = 'debian' and release = 'lenny') and exists (select package from packages_provides where ARRAY[packages_summary.package] @ packages_provides.string_to_array); There are 223 packages in that case: udd= select * from missing_provides; package -- abiword-gnome abiword-plugins-gnome arabtex aspell-ukr bglibs-dev blitz++ bootsplash collectd-apache collectd-hddtemp collectd-mysql collectd-ping collectd-sensors cracklib2 cracklib2-dev cvm-dev cvm-dev cyrus21-admin cyrus21-clients cyrus21-common cyrus21-dev cyrus21-doc cyrus21-imapd cyrus21-murder cyrus21-pop3d dbus-1-utils docbook-xsl-doc doom-package dosemu-freedos dviutils ethiop fftw3 fftw3-dev fftw3-doc fileutils freeze fvwm-gnome gimp-helpbrowser git-completion glacier2 gnome-sudoku grep-dctrl gs-afpl gtk2-engines-clearlooks gtk2-engines-crux gtk2-engines-highcontrast gtk2-engines-industrial gtk2-engines-lighthouseblue gtk2-engines-metal gtk2-engines-mist gtk2-engines-redmond95 gtk2-engines-smooth gtk2-engines-spherecrystal gtk2-engines-thinice gvr hat-ghc6 hugin-bin icegrid icepatch2 ice-slice icestorm ice-translators kile-i18n kinoplus kinoplus latex-ucs latex-ucs-contrib libadns1-bin liballegro-dev libaltlinuxhyph-dev libarchive-tar-perl libbluetooth2-dev libc-client-dev libcli1 libcurl3-dev libcurl3-gnutls-dev libcurl3-openssl-dev libcyrus-imap-perl21 libdb4.2-ruby1.8 libdb4.3-ruby1.8 libgd-dev libghc6-filepath-dev libghc6-filepath-prof libgle-doc libglew-dev libgpepimc0-dev libhd13 libhd13-dev libhd13-doc libhdf4g-run liblocale-maketext-simple-perl liblua5.1-sql-mysql2 liblua5.1-sql-sqlite2 liblua5.1-sql-sqlite-dev libmodule-load-perl libnss-pgsql1 libnunit2.2-cil libosgal-cvs1 libosgal-cvs-dev libpam-umask libparams-check-perl libpci2 libpgjava libplpc2a libpt-plugins-alsa libpt-plugins-avc libpt-plugins-dc libpt-plugins-oss libpt-plugins-v4l libpt-plugins-v4l2 librra0-dev librra0-tools librrd2-dev libsnmp9-dev libsoqt20 libsoqt20 libsoqt-dev libsoqt-dev libsvn-javahl libsylpheed-claws-gtk2-dev libtododb0-dev libufsparse-dev libumfpack4-dev libversion-perl libvorbis-perl libxmpp4r-ruby1.8-dev libzeroc-ice-dev liferea-gtkhtml liferea-mozilla linux-kernel-headers lxdoom mahoro-ruby mahoro-ruby1.8 med-common moinmoin-common muscle-doc nmapfe no-ip nut-dev nut-usb ocamlcvs ocaml-dbforge ocaml-report octave openmpi-dbg openmpi-dev openmpi-libs0 openoffice.org-filter-so52 openoffice.org-gtk-gnome osgal-cvs-doc pciutils-dev pdftohtml pdftohtml php5-json phpgroupware-addressbook phpgroupware-admin phpgroupware-calendar phpgroupware-email phpgroupware-filemanager phpgroupware-manual phpgroupware-news-admin phpgroupware-notes phpgroupware-preferences phpgroupware-setup phpgroupware-todo php-radius povray-3.5 povray-3.6 powstatd-crypt python-deb822 python-f2py python-numpy-dev python-zodb r-omegahat-ggobi rosegarden2 rosegarden4 schedutils scripturechecks scripturechecks shellutils slice2cpp slice2cs slice2docbook slice2freeze slice2freezej slice2java slice2py slice2vb squid3-client swf-player
Bug#498700: [DRE-maint] Bug#498700: Missing upgrade path from libdb4.2-ruby1.8 to libdb-ruby1.8
On Sun, Sep 28, 2008 at 05:30:10PM +0200, Lucas Nussbaum wrote: On 28/09/08 at 15:06 +0200, Frans Pop wrote: On Sunday 28 September 2008, Adeodato Simó wrote: Isn't this a bug of our upgrading tools, that should prefer to install a new, non-obsolete package A that Provides: B, rather than keeping a no-longer-present-in-the-lists B installed? Possibly. But as long as those tools don't support that it will have to be solved in the packages themselves. I'm wondering how many cases like that are still in lenny. That is: - binary package in etch - that is not in lenny - that is Replaced/Provided by another package You can use UDD to find it out. I failed to create something fast, but here is my code (it's too slow to output something): select package from packages_summary where ( release='etch' and package not in (select package from packages_summary where release='lenny') and exists ( select package from packages where ( release='lenny' and ARRAY[packages_summary.package] @ string_to_array(provides, ', ') ) ) ); Please note that I have almost no experience with SQL stuff. This is just the basic idea and needs real improvements. (Would be a good QA test, in my opinion). On the other hand, lots of libraries are probably in this case. Frans, did you just run into this bug by luck, or did you specifically looked for such cases? Feel free to clone the bug to apt/aptitude/whatever if you feel that should be implemented, but I'd think that would be squeeze material, not lenny. Agreed. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | signature.asc Description: Digital signature
Bug#498700: [DRE-maint] Bug#498700: Missing upgrade path from libdb4.2-ruby1.8 to libdb-ruby1.8
On 28/09/08 at 15:06 +0200, Frans Pop wrote: On Sunday 28 September 2008, Adeodato Simó wrote: Isn't this a bug of our upgrading tools, that should prefer to install a new, non-obsolete package A that Provides: B, rather than keeping a no-longer-present-in-the-lists B installed? Possibly. But as long as those tools don't support that it will have to be solved in the packages themselves. I'm wondering how many cases like that are still in lenny. That is: - binary package in etch - that is not in lenny - that is Replaced/Provided by another package On the other hand, lots of libraries are probably in this case. Frans, did you just run into this bug by luck, or did you specifically looked for such cases? Feel free to clone the bug to apt/aptitude/whatever if you feel that should be implemented, but I'd think that would be squeeze material, not lenny. Agreed. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#498700: [DRE-maint] Bug#498700: Missing upgrade path from libdb4.2-ruby1.8 to libdb-ruby1.8
On Sunday 28 September 2008, Lucas Nussbaum wrote: Frans, did you just run into this bug by luck, or did you specifically looked for such cases? I'd say by accident rather than luck :-P But I certainly did not go looking for it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#498700: [DRE-maint] Bug#498700: Missing upgrade path from libdb4.2-ruby1.8 to libdb-ruby1.8
On Fri, Sep 12, 2008 at 01:19:58PM +0200, Frans Pop wrote: Package: libdb-ruby1.8 Version: 0.6.5-1 Severity: serious Justification: Causes unclean upgrades I have dhelp installed on a Lenny system, which depends on libdb4.2-ruby1.8. After upgrading the system at some point I was left with libdb4.2-ruby1.8 still installed as obsolete package. At first I thought this was some temporary inconsistency in testing, but I now find that libdb4.2-ruby1.8 has been renamed to libdb-ruby1.8, which provides the old package. However, it seems that no upgrade path is provided to ensure that users that already had the old package installed will get the new package. Only if libdb-ruby1.8 is selected manually will the old package get replaced. The obvious fix (dummy transitional packages) is in our SVN; it’a bit ugly, but seems to work. It certainly deserves a second pair of eyes, I might easily have missed something. Cheers, -- Michael Schutte [EMAIL PROTECTED] signature.asc Description: Digital signature
