On 11/02/14 15:41, Daniel Pocock wrote: > On 11/02/14 15:26, Andreas Beckmann wrote: >> On 2014-02-11 13:10, Markus Wanner wrote: >>> On 02/11/2014 01:01 PM, Andreas Beckmann wrote: >>>> Or if you want to avoid using epochs, reupload 1.4.8 using as >>>> 1.10.really.1.4.8 as the upstream version, and upload 1.10 as 1.10.release >>>> to >>>> experimental. Once you upload upstream 1.11 you are back to normal version >>>> numbers without having used an epoch inbetween. >>> Given that we are likely to switch to separate libasio1.4-dev and >>> libasio1.10-dev packages, I think the epoch approach is less confusing, >>> overall. >> Since it seems you need to introduce libasio1.4-dev anyway, it should be >> possible to fix this version mess without .really. versions and without >> using epochs. All it needs is a trip through NEW. >> >> Let me know if I should look into preparing a patch ... >> >> > > > I already made an upload using epoch > > It is 1:1.4.8-3 > >
I notice the upload hasn't actually built http://packages.qa.debian.org/a/asio.html reports that it is still 1.10.1-1 in unstable and no link to the build logs Has anybody else tried something else to deal with this package transition or reversion to 1.4.8? Or did I do something wrong when adding the epoch? -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52fa8c3a.5060...@pocock.com.au
