Hi Simon,
Le mardi 25 octobre 2016 18:55:39 EDT, vous avez écrit :
> So while this seems to have migrated into unstable, when building in the
> Zesty proposed pocket, it failed to build.
>
> This FTBFS is only on ppc64el and seems to be caused by symbols
> problems. You can take a look for
So while this seems to have migrated into unstable, when building in the
Zesty proposed pocket, it failed to build.
This FTBFS is only on ppc64el and seems to be caused by symbols
problems. You can take a look for yourself here:
- https://launchpad.net/ubuntu/+source/taglib/1.11.1-0.1
-
Control: severity -1 important
Control: tag -1 + upstream
Control: forwarded -1 https://github.com/taglib/taglib/issues/757
Le mercredi 12 octobre 2016, 14:33:36 EDT Christoph Egger a écrit :
> Control: reopen -1
> Control: reassign -1 libtag1v5
> Control: found -1 1.11+dfsg.1-0.1
>
> Christoph
Control: reopen -1
Control: reassign -1 libtag1v5
Control: found -1 1.11+dfsg.1-0.1
Christoph Egger writes:
> Which is exactly what happened in unstable ~1 day ago as part of the
> transition. So this seems to be a totally normal unstable disturbance
> and not a bug.
Hi!
Nick Black writes:
> I rebuilt the source package against current libtag, and it works once
> more.
Which is exactly what happened in unstable ~1 day ago as part of the
transition. So this seems to be a totally normal unstable disturbance
and not a bug.
Package: ncmpcpp
Version: 0.7.4-1
Followup-For: Bug #839767
I rebuilt the source package against current libtag, and it works once
more.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Package: ncmpcpp
Version: 0.7.4-1+b1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
ncmpcpp is not able to start at all. any attempt to start results into this:
bash$ ncmpcpp
ncmpcpp: symbol lookup error: ncmpcpp: undefined symbol:
_ZN6TagLib6String14WCharByteOrderE
7 matches
Mail list logo