Marking as fixed released according tot he feedback here.
** Changed in: leveldb (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to taglib in Ubuntu.
** Changed in: thumbnailer (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to taglib in Ubuntu.
https://bugs.launchpad.net/bugs/1640326
Title:
FTBFS on zesty
Status in
** Changed in: thumbnailer (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to taglib in Ubuntu.
https://bugs.launchpad.net/bugs/1640326
Title:
FTBFS on zesty
Status in leveldb
leveldb 1.19-2 is stuck in zesty-proposed over autopackagetest failures
with the python bindings. Seems like it's stuffed. Requested the broken
leveldb to be removed from zesty-proposed, thus reverting to stable
1.18-5 which is in zesty (release). After removal is published, will
trigger
Sorry wrong link for upstream bug. It's here:
https://github.com/google/leveldb/issues/425
** Bug watch added: github.com/google/leveldb/issues #425
https://github.com/google/leveldb/issues/425
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Upstream bug here: https://github.com/Level/leveldown/issues/321
** Bug watch added: github.com/Level/leveldown/issues #321
https://github.com/Level/leveldown/issues/321
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
The builder uses libleveldb 1.19-2, but the zesty archives still have
libleveldb 1.18-5.
After installing 1.19-2 locally, I instantly got the same failure.
** Also affects: leveldb (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
After lots of debugging and tracing, I found the root cause with
valgrind. The interesting thing is that this happens only in the silo.
When I run the same code on my zesty VM, everything is fine. So, what is
different in the silo builders from a vanilla zesty install? (Installed
zesty about two
Almost certainly not related. The test that triggers this is far away
from the core dump. Still worth following up on though.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to taglib in Ubuntu.
I'm seeing this report from valgrind on zesty. On xenial, the test runs
clean. Not sure whether this might be related.
==63566== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 10 from 10)
==63463== Conditional jump or move depends on uninitialised value(s)
==63463==at 0x4C33E26:
I think we can rule out leveldb. It's at revision 1.18-5 in both xenial
and zesty.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to taglib in Ubuntu.
https://bugs.launchpad.net/bugs/1640326
Title:
FTBFS on zesty
Status in
Taglib fix is in the linked branch.
The thumbnailer test dumps core on all architectures on zesty. The fault
keeps moving around, looks like a race condition. We are not using
threads ourselves, so the problem likely is in a something we call into.
Candidates would be QT and (unlikely) leveldb.
** Branch linked: lp:~michihenning/thumbnailer/zesty-test-suppression
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to taglib in Ubuntu.
https://bugs.launchpad.net/bugs/1640326
Title:
FTBFS on zesty
Status in taglib
I have a fix for the taglib issue that does not require changes to
taglib. (taglib 1.11 added a new API for getting images out of
VorbisComments and broke the behavior (not API) of the existing one.)
Still looking at the other issues.
--
You received this bug notification because you are a
Taglib 1.11 has broken extraction of VorbisComments.
I've opened a bug here: https://github.com/taglib/taglib/issues/770
Looking at the taglib source now to see whether there is an easy fix.
** Changed in: thumbnailer (Ubuntu)
Assignee: (unassigned) => Michi Henning (michihenning)
**
Ubuntu and Debian are both at 1.11.1 upstream release version.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to taglib in Ubuntu.
https://bugs.launchpad.net/bugs/1640326
Title:
FTBFS on zesty
Status in taglib package in
@ Dimitri
24th of October the taglib-team released a bugfix version [1]:
TagLib 1.11.1 Release - October 24, 2016
Fixed binary incompatible change in TagLib::String.
Fixed reading ID3v2 CTOC frames with a lot of entries.
Fixed seeking ByteVectorStream from the end.
[1]
Adding taglib task for inspection, there was a big version bump in
taglib in zesty from 1.9 -> 1.11
** Also affects: taglib (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Unfortunately, just suppressing the Qt tests doesn't fix this. It turns
out that, on zesty, the tests for all architectures fail. It looks like
a problem with taglib. Every test that tries to extract artwork from an
ogg video file fails.
There is also a segfault in the thumbnailer test. That
Fix is in a silo: https://bileto.ubuntu.com/#/ticket/2175
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to thumbnailer in Ubuntu.
https://bugs.launchpad.net/bugs/1640326
Title:
FTBFS on zesty
Status in thumbnailer package
Thanks for that, will fix now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to thumbnailer in Ubuntu.
https://bugs.launchpad.net/bugs/1640326
Title:
FTBFS on zesty
Status in thumbnailer package in Ubuntu:
New
Bug
21 matches
Mail list logo
