On Tue, Jan 22, 2013 at 2:24 AM, Christoph Anton Mitterer <cales...@scientia.net> wrote: > Hi. > > >> > tags 698536 wontfix > I don't quite understand why you close this (especially as it's not > fixed yet, and likely other people will report the same "bug", too). > Especially it's surely not a wontfix...
Because I read your bug report as "please upgrade openjpeg 1.x with openjpeg 2.x", which is a 'wontdo' :) >> > openjpeg 1.5 transition was scheduled, see #669348. However it occured >> > too late in the freeze process, and was postponed. 1.5 is ABI >> > incompatible with 1.3, however after doing a recompilation all >> > packages in debian should rebuild properly. so nothing prevents you >> > from using 1.5.x. >> > >> > technically speaking transition to 2.0 will not happen any time soon, >> > since API are so different, so packages 1.x and 2.x might have to live >> > together. > And why not simply providing all the libs with the different ABIs? Or at > least the newest one and those that are used in not yet transitioned > packages? As explain in my mail, this is my goal. With my openjpeg maint' hat on, this is not a short term goal, since 2.0.0 is not very stable. So: - You open a bug for having 1.5 in debian, which will be also closed since 1.5 is in experimental. Changelog for 1.5 will read with dates from 2012 - You can open a bug for openjpeg 2.x in debian, but I will not be the one to upload 2.0.0 ... Make sense ? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
