This bug was fixed in the package libxml2 - 2.9.10+dfsg-5
---
libxml2 (2.9.10+dfsg-5) unstable; urgency=medium
* Team upload.
[ Mattia Rizzolo ]
* d/rules:
+ Drop --disable-silent-rules, already passed by dh_auto_configure.
+ Drop --parallel, now default with debhelper
** Changed in: libxml2 (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869814
Title:
ubuntu-docs build failure - possible solution
To manage
sync'd. please close this bug once libxml2 has been accepted
https://launchpad.net/ubuntu/focal/+queue?queue_state=1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869814
Title:
ubuntu-docs build
** Changed in: libxml2
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869814
Title:
ubuntu-docs build failure - possible solution
To manage notifications about this
** Bug watch added: gitlab.gnome.org/GNOME/libxml2/issues #64
https://gitlab.gnome.org/GNOME/libxml2/issues/64
** Changed in: libxml2
Remote watch: bugzilla.gnome.org/ #789714 =>
gitlab.gnome.org/GNOME/libxml2/issues #64
--
You received this bug notification because you are a member of
** Also affects: libxml2 via
https://bugzilla.gnome.org/show_bug.cgi?id=789714
Importance: Unknown
Status: Unknown
** Bug watch removed: gitlab.gnome.org/GNOME/libxml2/issues #64
https://gitlab.gnome.org/GNOME/libxml2/issues/64
** Bug watch removed:
** No longer affects: itstool (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869814
Title:
ubuntu-docs build failure - possible solution
To manage notifications about this bug go to:
To the sponsor:
libxml2 2.9.10+dfsg-5, including the patch, is now available in Debian
unstable. So please sync libxml2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869814
Title:
ubuntu-docs
@Sebastien: Indeed, it's the very same thing. Then I spent several hours
on an issue that was already spotted and fixed. :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869814
Title:
ubuntu-docs
@Gunnar, looks like the patch I backported earlier in the cycle
https://launchpad.net/ubuntu/+source/libxml2/2.9.4+dfsg1-8ubuntu3
But apparently doko synced from Debian overlooking we had a delta...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This bug was fixed in the package ubuntu-docs - 20.04.1
---
ubuntu-docs (20.04.1) focal; urgency=medium
* scripts/update-translations.sh:
- Handle tarballs also from the package
* Bump version to 20.04 / focal
* debian/control.in, debian/control:
- Replace Vcs-Bzr with
** Tags added: ftbfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869814
Title:
ubuntu-docs build failure - possible solution
To manage notifications about this bug go to:
Thanks Shaun! It's indeed that bug. Why am I not surprised when seeing
that you filed it? :)
I grabbed a Fedora patch and submitted a Debian merge request:
https://salsa.debian.org/xml-sgml-team/libxml2/-/merge_requests/3
It looks pretty spot on, don't you think? At least, with that patch
So in general, syntax errors in translations just cause a warning, and
the original text is used. itstool only errors on syntax if you pass
--strict, and yelp.m4 doesn't even give you a way to pass --strict.
There's a chance this is itstool's fault. You do still have to do memory
management with
Thanks Sebastien!
Or https://gitlab.gnome.org/GNOME/libxml2/issues/64 (which is not yet
closed).
@Boyuan: Well, it does scream loudly in the sense that the build fails.
I wouldn't blame the build system in this case. It has worked in a
sensible and robust way for many years. The segfault issue
@Gunnar It seems that the root cause has been found, thanks! It's well
known that translation could be fragile when the build system is not
well defined; all I can think of is to make the build system robust
enough and yell out loudly enough whenever an error (e.g., segfault)
happens.
--
You
It's segfault in libxml code, their binding doesn't seem to handle
invalid files well, somewaht similar to
https://gitlab.gnome.org/GNOME/libxml2/-/issues/12
** Changed in: itstool (Ubuntu)
Status: New => Invalid
** Bug watch added: gitlab.gnome.org/GNOME/libxml2/-/issues #12
Uploaded a new version of ubuntu-docs, which builds on focal despite the
issue discussed in this bug report.
** Changed in: ubuntu-docs (Ubuntu)
Status: New => Fix Committed
** Changed in: ubuntu-docs (Ubuntu)
Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)
** Tags added:
@Shaun: Have you possibly stumbled into anything similar when building
e.g. gnome-user-docs?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869814
Title:
ubuntu-docs build failure - possible
Hmm.. I saw in the buildlog from the successful build that it skipped
the Chinese translation of a particular string. The reason proved to be
a missing '<' character, i.e. the translated string contains an instance
of '/em>' instead of ''. And that's the correct behavior; it should
check the
@Boyuan: Do you have any thoughts on the above?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869814
Title:
ubuntu-docs build failure - possible solution
To manage notifications about this bug go
21 matches
Mail list logo
