Bug#908980: transition: qrencode (ongoing, apparently uncoordinated)
Control: tags -1 confirmed pending
Control: block -1 with 908987
On 17/09/2018 00:58, peter green wrote:
> Package: release.debian.org
> Severity: normal
> User:release.debian.org@packages.debian.org
> Usertags: transition
> Control: forwarded -1https://release.debian.org/transitions/html/auto-qrencode.html
> Control: block -1 by 908929
> X-Debbugs-CC:qrencode@packages.debian.org
>
> oops, send this to the list instead of the bug submission address, resending.
>
> Hi debian-release,
> I thought I would let you know that there appears to be a libqrencode transition
> going on and this transition seems to be uncoordinated (at least I can find no
> recent mention of it in the debian-release archives). An automated transition
> tracker has been set-up at
> https://release.debian.org/transitions/html/auto-qrencode.html
>
> It appears that no binnmus have been scheduled in Debian for this transition
> yet, the packages listed as "good" either don't depend on the shared library or
> had a sourceful upload since the libqrencode upload.
>
> Over in raspbian our auto-binnmuer did schedule binnmus for this transition. All
> of them built successfully. However google-authenticator uses libqrencode
> through dlopen/dlsym rather than through the headers provided by libqrencode,
> so it needs sourceful changes (to both the upstream source and debian/control).
> Seehttps://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908929
litecoin failed to build on mips64el, which is blocking this transition.
Cheers,
Emilio
Reply to: