Bug#739663: Processed: libboinc7: fails to upgrade from 'wheezy' - trying to overwrite /usr/lib/libboinc_zip.so.7
Control: tag -1 + pending Hi, On Sat, Feb 22, 2014 at 11:13:01PM +0100, Andreas Beckmann wrote: On 2014-02-21 19:02, Gianfranco Costamagna wrote: I think because now boinc-dev is not a real package anymore, just a transition virtual package. no it's not virtual, only transitional ... This probably breaks if I torture-test it :-) And it will definitely break in case you add a transitional boing-dev package. mmm this is something I don't understand, with boinc-dev being a transitional package things need to be done the correct way and moreover the problem is that I manually try to upgrade packages with dpkg, and in this case I needed to add manually libboinc7 IIRC to the list. Running dpkg -i pkg1.deb pkg2.deb ... does not respect dependency ordering. You need to use a local repository and apt-get install for sane upgrade path tests. So I don't know exactly how to test for this bug, this is why help is really needed ;) Can you push the pending stuff (e.g. Replaces in addition to Breaks) to git? So I can build the package from git and push it into my piuparts engine. Andreas I've just corrected our debian/control[.in] file, and had an successful upgrade from wheezy to this current version. The commit is at http://anonscm.debian.org/gitweb/?p=pkg-boinc/boinc.git;a=commitdiff;h=49f36c765fcde2a9cc9dd179fd9932a0c02af1b8;hp=ac94be23b771e086fcd15121a72f878325bd2bc5 Thank you for your kind help on this bug! Cheers, GUO Yixuan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739663: Processed: libboinc7: fails to upgrade from 'wheezy' - trying to overwrite /usr/lib/libboinc_zip.so.7
On 2014-02-21 19:02, Gianfranco Costamagna wrote: I think because now boinc-dev is not a real package anymore, just a transition virtual package. no it's not virtual, only transitional ... This probably breaks if I torture-test it :-) And it will definitely break in case you add a transitional boing-dev package. mmm this is something I don't understand, with boinc-dev being a transitional package things need to be done the correct way and moreover the problem is that I manually try to upgrade packages with dpkg, and in this case I needed to add manually libboinc7 IIRC to the list. Running dpkg -i pkg1.deb pkg2.deb ... does not respect dependency ordering. You need to use a local repository and apt-get install for sane upgrade path tests. So I don't know exactly how to test for this bug, this is why help is really needed ;) Can you push the pending stuff (e.g. Replaces in addition to Breaks) to git? So I can build the package from git and push it into my piuparts engine. Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739663: Processed: libboinc7: fails to upgrade from 'wheezy' - trying to overwrite /usr/lib/libboinc_zip.so.7
Hi Andreas, I tried to add a Break+Replaces, but it didn't work, I think because now boinc-dev is not a real package anymore, just a transition virtual package. For this reason I only added a breaks on libboinc7, and I tested on a virtual machine. It seems to be working, but this is the first time I play with breaks/replaces fields, so I might be wrong somewhere. this is the commit, I'll upload a version in the next few days if no answer, since I think this bug is pretty serious. http://anonscm.debian.org/gitweb/?p=pkg-boinc/boinc.git;a=commitdiff;h=c993dd1d92d58a03562c52c3d2f8b180303eb84f Can I kindly ask you to review the patch? many thanks, Gianfranco Il Venerdì 21 Febbraio 2014 2:51, Debian Bug Tracking System ow...@bugs.debian.org ha scritto: Processing control commands: affects -1 + boinc-dev Bug #739663 [libboinc7] libboinc7: fails to upgrade from 'wheezy' - trying to overwrite /usr/lib/libboinc_zip.so.7 Added indication that 739663 affects boinc-dev -- 739663: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739663 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- pkg-boinc-devel mailing list pkg-boinc-de...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-boinc-devel
Bug#739663: Processed: libboinc7: fails to upgrade from 'wheezy' - trying to overwrite /usr/lib/libboinc_zip.so.7
On 2014-02-21 14:37, Gianfranco Costamagna wrote: Hi Andreas, I tried to add a Break+Replaces, but it didn't work, How did this look like? And how did it fail? I think because now boinc-dev is not a real package anymore, just a transition virtual package. Since the B+R you add are versioned, they only match against real packages. And the old one is a real package. For this reason I only added a breaks on libboinc7, and I tested on a virtual machine. It seems to be working, but this is the first time I play with breaks/replaces fields, so I might be wrong somewhere. This probably breaks if I torture-test it :-) And it will definitely break in case you add a transitional boing-dev package. this is the commit, I'll upload a version in the next few days if no answer, since I think this bug is pretty serious. http://anonscm.debian.org/gitweb/?p=pkg-boinc/boinc.git;a=commitdiff;h=c993dd1d92d58a03562c52c3d2f8b180303eb84f Can I kindly ask you to review the patch? 7.0.39+dfsg-1 is the version that split up boinc-dev? And this was the first upload of the new 7.0.39+dfsg upstream, i.e. there have not been any 7.0.39+dfsg-1~experimental0 or similar versions? So each package that got a bit of the previous content (and ships it at the same location) should have Breaks: boinc-dev ( 7.0.39+dfsg) Replaces: boinc-dev ( 7.0.39+dfsg) (in addition to other B+R it might already have). (this review is based solely on your reply and the commitdiff you linked, I haven't looked at the boinc package in more detail, but I might take a further look at the weekend) Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739663: Processed: libboinc7: fails to upgrade from 'wheezy' - trying to overwrite /usr/lib/libboinc_zip.so.7
Il Venerdì 21 Febbraio 2014 14:54, Andreas Beckmann a...@debian.org ha scritto: On 2014-02-21 14:37, Gianfranco Costamagna wrote: Hi Andreas, I tried to add a Break+Replaces, but it didn't work, How did this look like? And how did it fail? I dont't honestly remember, it failed with almost the same error, or something related to a missing boinc-dev package I think because now boinc-dev is not a real package anymore, just a transition virtual package. Since the B+R you add are versioned, they only match against real packages. And the old one is a real package. For this reason I only added a breaks on libboinc7, and I tested on a virtual machine. It seems to be working, but this is the first time I play with breaks/replaces fields, so I might be wrong somewhere. This probably breaks if I torture-test it :-) And it will definitely break in case you add a transitional boing-dev package. mmm this is something I don't understand, and moreover the problem is that I manually try to upgrade packages with dpkg, and in this case I needed to add manually libboinc7 IIRC to the list. So I don't know exactly how to test for this bug, this is why help is really needed ;) this is the commit, I'll upload a version in the next few days if no answer, since I think this bug is pretty serious. http://anonscm.debian.org/gitweb/?p=pkg-boinc/boinc.git;a=commitdiff;h=c993dd1d92d58a03562c52c3d2f8b180303eb84f Can I kindly ask you to review the patch? 7.0.39+dfsg-1 is the version that split up boinc-dev? And this was the first upload of the new 7.0.39+dfsg upstream, i.e. there have not been any 7.0.39+dfsg-1~experimental0 or similar versions? this is the version that has some library moved from one package to another, no, this is the first upload, nothing in experimental So each package that got a bit of the previous content (and ships it at the same location) should have Breaks: boinc-dev ( 7.0.39+dfsg) Replaces: boinc-dev ( 7.0.39+dfsg) (in addition to other B+R it might already have). ok, this seems reasonable, but we moved the libraries many times between versions, that boinc-dev, the libboinc introduction, the split between client and server libraries, the server-maker package introduction... Boinc has grown a lot since the old package, this is why I'm having this kind of troubles in thinking in a clean way for upgrade, the same can happen I think even in ubuntu, with different versions and so different files overridden. I don't like to fix just this bug and have a transition failure between somebody with backports enabled or other different repository. I hope to have explained my (maybe wrong, I'm here to learn :p) point thanks for your support and bug report so far! Cheers, Gianfranco (this review is based solely on your reply and the commitdiff you linked, I haven't looked at the boinc package in more detail, but I might take a further look at the weekend) Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
