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
