On 31/01/17 10:08, Jonas Smedegaard wrote: > Quoting Emilio Pozuelo Monfort (2017-01-31 09:49:25) >> On 31/01/17 09:36, Jonas Smedegaard wrote: >>> Quoting Emilio Pozuelo Monfort (2017-01-31 00:41:57) >>>> On Tue, 10 Jan 2017 18:01:38 +0100 Jonas Smedegaard <d...@jones.dk> wrote: >>>>> Source: raptor >>>>> Severity: serious >>>>> >>>>> Raptor 1.x has not had an upstream release in 6 years, is superceded by >>>>> Raptor 2.x, and since earlier today no other package depend on it. >>>> >>>> Looks like you're wrong: >>>> >>>> emilio@tatooine:~$ dak rm -Rn -s testing raptor >>>> Will remove the following packages from testing: >>>> >>>> libraptor1 | 1.4.21-11 | mips64el >>>> libraptor1 | 1.4.21-11+b1 | amd64, arm64, armel, armhf, i386, ppc64el >>>> libraptor1 | 1.4.21-11+b2 | mips, mipsel, s390x >>>> libraptor1-dbg | 1.4.21-11 | mips64el >>>> libraptor1-dbg | 1.4.21-11+b1 | amd64, arm64, armel, armhf, i386, ppc64el >>>> libraptor1-dbg | 1.4.21-11+b2 | mips, mipsel, s390x >>>> libraptor1-dev | 1.4.21-11 | mips64el >>>> libraptor1-dev | 1.4.21-11+b1 | amd64, arm64, armel, armhf, i386, ppc64el >>>> libraptor1-dev | 1.4.21-11+b2 | mips, mipsel, s390x >>>> libraptor1-doc | 1.4.21-11 | all >>>> raptor | 1.4.21-11 | source >>>> raptor-utils | 1.4.21-11 | mips64el >>>> raptor-utils | 1.4.21-11+b1 | amd64, arm64, armel, armhf, i386, ppc64el >>>> raptor-utils | 1.4.21-11+b2 | mips, mipsel, s390x >>>> >>>> Maintainer: Dave Beckett <daj...@debian.org> >>>> >>>> ------------------- Reason ------------------- >>>> >>>> ---------------------------------------------- >>>> >>>> Checking reverse dependencies... >>>> # Broken Depends: >>>> flickcurl: libflickcurl-dev >>>> >>>> # Broken Build-Depends: >>>> soprano: libraptor1-dev (>= 1.4.16) >>>> >>>> Dependency problem found. >>> >>> Ah, indeed I missed some. >>> >>> Since we are now past freeze, it seems raptor 1.x will bitrot another >>> few years - unless someone else does the work of getting those few >>> remaining packages relinked (likely needs very small patches) and >>> negotiate with release managers to let those changes through (too big a >>> mental challenge for me). >> >> If the changes are not too invasive and happen soon, I will strongly >> consider it. > > "I" as in you are part of the release team, or...?
Yes. soprano build-deps on libraptor1-dev but is actually using and linking against raptor2, so the build-dep can probably be changed to libraptor2-dev safely. flickcurl seems to be using raptor2 as well (build-deps on libraptor2-dev, libflickcurl0 depends on libraptor2-0), but libflickcurl-dev still depends on libraptor1-dev, probably a mistake from the raptor1 -> raptor2 port. I assume that dependency can be safely changed to libraptor2-dev. Cheers, Emilio
