[Touch-packages] [Bug 2059417] Re: Sync xz-utils 5.6.1-1 (main) from Debian unstable (main)
It’s 5.4.5, so “no, but it does not contain the known backdoor”. Both Debian and Ubuntu are currently analysing what needs to be done. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xz-utils in Ubuntu. https://bugs.launchpad.net/bugs/2059417 Title: Sync xz-utils 5.6.1-1 (main) from Debian unstable (main) Status in xz-utils package in Ubuntu: Won't Fix Bug description: Please sync xz-utils 5.6.1-1 (main) from Debian unstable (main) Hello! I am one of the upstream maintainers for XZ Utils. Version 5.6.1 was recently released and uploaded to Debian as a bugfix only release. Notably, this fixes a bug that causes Valgrind to issue a warning on any application dynamically linked with liblzma. This includes a lot of important applications. This could break build scripts and test pipelines that expect specific output from Valgrind in order to pass. Additionally, this fixes a small typo for the man pages translations for Brazilian Portuguese, German, French, Korean, Romanian, and Ukrainian, and removes the need for patches applied for version 5.6.0-0.2. The other bugfixes in this release have no impact on Ubuntu. They involve building with CMake or when building on a system without Landlock system calls defined (these are defined in Ubuntu). Changelog entries since current noble version 5.6.0-0.2: xz-utils (5.6.1-1) unstable; urgency=medium * Non-maintainer upload. * Import 5.6.1 (Closes: #1067708). * Takeover maintenance of the package. -- Sebastian Andrzej Siewior Wed, 27 Mar 2024 22:53:21 +0100 Excerpt from the NEWS entry from upstream: 5.6.1 (2024-03-09) * liblzma: Fixed two bugs relating to GNU indirect function (IFUNC) with GCC. The more serious bug caused a program linked with liblzma to crash on start up if the flag -fprofile-generate was used to build liblzma. The second bug caused liblzma to falsely report an invalid write to Valgrind when loading liblzma. * xz: Changed the messages for thread reduction due to memory constraints to only appear under the highest verbosity level. * Build: - Fixed a build issue when the header file was present on the system but the Landlock system calls were not defined in . - The CMake build now warns and disables NLS if both gettext tools and pre-created .gmo files are missing. Previously, this caused the CMake build to fail. * Minor improvements to man pages. * Minor improvements to tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/2059417/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2032577] Re: xz crashed with SIGSEGV in lzma_lzma_optimum_normal
That sounds even more like a RAM issue (that it stopped occurring with the same kernel and software version). Perhaps when you switched away from Wayland, your graphics card is now used less heavily, and when the GPU was used more, the RAM got hotter or got minimally less power and therefore had issues, or something. (This is something people have indeed seen, so…) If you can trigger it reliably again, the changes would indeed be interesting. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xz-utils in Ubuntu. https://bugs.launchpad.net/bugs/2032577 Title: xz crashed with SIGSEGV in lzma_lzma_optimum_normal Status in xz-utils package in Ubuntu: New Bug description: xz segfaults. More details in https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2032379 From Dmesg.txt on that report [114838.184191] xz[431483]: segfault at 7f9a93f3701a ip 7f9b3f780c1a sp 7f9a957baa50 error 4 in liblzma.so.5.2.5[7f9b3f771000+1b000] ProblemType: Crash ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 ExecutablePath: /usr/bin/xz ExecutableTimestamp: 1649422298 InstallationDate: Installed on 2021-04-09 (863 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Package: xz-utils 5.2.5-2ubuntu1 ProcCmdline: xz --check=crc32 --threads=0 -c /var/tmp/mkinitramfs-MAIN_E1GbD9 ProcCwd: / ProcEnviron: LC_CTYPE=C.UTF-8 TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 SegvAnalysis: Segfault happened at: 0x7f9b3f780c1a:movzbl (%rdi,%r8,1),%r10d PC (0x7f9b3f780c1a) ok source "(%rdi,%r8,1)" (0x7f9a93f3701a) in non-readable VMA region: 0x7f9a90021000-0x7f9a9400 ---p None destination "%r10d" ok Stack memory exhausted (SP below stack segment) SegvReason: reading VMA None Signal: 11 SourcePackage: xz-utils Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to jammy on 2023-01-29 (204 days ago) UserGroups: N/A StacktraceTop: bt_find_func (len_limit=64, pos=9137198, cur=0x7f9a943edc3d "", cur_match=4194304, depth=24, son=son@entry=0x7f9a8afbd010, cyclic_pos=748589, cyclic_size=8388609, matches=0x7f9adc0ec324, len_best=11) at ../../../../src/liblzma/lz/lz_encoder_mf.c:483 lzma_mf_bt4_find (mf=0x7f9a9c70, matches=0x7f9adc0ec304) at ../../../../src/liblzma/lz/lz_encoder_mf.c:721 lzma_mf_find (mf=mf@entry=0x7f9a9c70, count_ptr=count_ptr@entry=0x7f9adc0ecb94, matches=matches@entry=0x7f9adc0ec304) at ../../../../src/liblzma/lz/lz_encoder_mf.c:28 lzma_lzma_optimum_normal (position=, len_res=, back_res=, mf=, coder=) at ../../../../src/liblzma/lzma/lzma_encoder_optimum_normal.c:846 lzma_lzma_optimum_normal (position=, len_res=, back_res=, mf=, coder=) at ../../../../src/liblzma/lzma/lzma_encoder_optimum_normal.c:804 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/2032577/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1307883] Re: ca-certificates-java misses runtime dependency on initscripts
openjdk-8 fixed this by introducing explicit dependencies on the package carrying mountpoint: ifneq (,$(filter $(distrel),wheezy jessie precise trusty)) control_vars += '-Vmountpoint:Depends=initscripts' else control_vars += '-Vmountpoint:Depends=util-linux (>= 2.26.2-4)' endif ** Changed in: openjdk-8 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1307883 Title: ca-certificates-java misses runtime dependency on initscripts Status in ca-certificates-java package in Ubuntu: Confirmed Status in openjdk-7 package in Ubuntu: Confirmed Status in openjdk-8 package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Triaged Bug description: Jitsi build-depends on openjdk-7-jre but the package fails to install in pbuilder and thus I currently cannot build the package. Here is the output I get while I am logged in to the trusty chroot. # aptitude install default-jdk [...] E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up ca-certificates-java (20130815ubuntu1) ... /var/lib/dpkg/info/ca-certificates-java.postinst: line 90: mountpoint: command not found the keytool command requires a mounted proc fs (/proc). dpkg: error processing package ca-certificates-java (--configure): subprocess installed post-installation script returned error exit status 1 Setting up openjdk-7-jre-headless:i386 (7u51-2.4.6-1ubuntu4) ... /var/lib/dpkg/info/openjdk-7-jre-headless:i386.postinst: 18: /var/lib/dpkg/info/openjdk-7-jre-headless:i386.postinst: mountpoint: not found the java command requires a mounted proc fs (/proc). dpkg: error processing package openjdk-7-jre-headless:i386 (--configure): subprocess installed post-installation script returned error exit status 1 Setting up default-jre-headless (2:1.7-51) ... dpkg: dependency problems prevent configuration of openjdk-7-jre:i386: openjdk-7-jre:i386 depends on openjdk-7-jre-headless (= 7u51-2.4.6-1ubuntu4); however: Package openjdk-7-jre-headless:i386 is not configured yet. dpkg: error processing package openjdk-7-jre:i386 (--configure): dependency problems - leaving unconfigured Setting up default-jre (2:1.7-51) ... dpkg: dependency problems prevent configuration of openjdk-7-jdk:i386: openjdk-7-jdk:i386 depends on openjdk-7-jre (= 7u51-2.4.6-1ubuntu4); however: Package openjdk-7-jre:i386 is not configured yet. dpkg: error processing package openjdk-7-jdk:i386 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of default-jdk: default-jdk depends on openjdk-7-jdk (>= 7~u3-2.1.1); however: Package openjdk-7-jdk:i386 is not configured yet. dpkg: error processing package default-jdk (--configure): dependency problems - leaving unconfigured Processing triggers for ca-certificates (20130906ubuntu2) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d /etc/ca-certificates/update.d/jks-keystore: 33: /etc/ca-certificates/update.d/jks-keystore: mountpoint: not found the keytool command requires a mounted proc fs (/proc). E: /etc/ca-certificates/update.d/jks-keystore exited with code 1. done. Errors were encountered while processing: ca-certificates-java openjdk-7-jre-headless:i386 openjdk-7-jre:i386 openjdk-7-jdk:i386 default-jdk # mount /proc on /proc type proc (rw,relatime) tmpfs on /run/shm type tmpfs (rw,relatime) /dev/pts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1307883/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2028571] Re: klibc-utils contains identical binaries
jdupes normally considers hardlinks as one. And, indeed, on my Debian system, I see: -rwxr-xr-x 1 root root 36656 May 27 2021 gunzip* -rwxr-xr-x 1 root root 36656 May 27 2021 gzip* These aren’t hardlinks. And indeed they aren’t hardlinks in the Debian binary package either: $ paxtar -xOf klibc-utils_2.0.8-6.1_amd64.deb data.tar.xz | xz -d | paxtar -tvf - | fgrep zip -rwxr-xr-x 1 root root 36656 May 27 2021 ./usr/lib/klibc/bin/gunzip -rwxr-xr-x 1 root root 36656 May 27 2021 ./usr/lib/klibc/bin/gzip debian/klibc-utils.install just has: usr/lib/klibc/bin/* These get placed there by: override_dh_auto_install: $(MAKE) install $(KLIBC_MAKEFLAGS) Upstream usr/gzip/Kbuild does hardlink them in the build directory: $(obj)/gunzip $(obj)/zcat: $(obj)/gzip $(call cmd,ln) The upstream “make install” call causes execution of: install -m 755 usr/gzip/gzip usr/gzip/gunzip usr/gzip/zcat ../tmp/usr/lib/klibc/bin And, indeed, this breaks up the hardlink. I see two actions arising from this: ① The Debian packaging probably should run something like… for pkgtopdir in debian/*/; do jdupes -rL "$pkgtopdir"; done … after installing all the files. @maximilian attems, are you reading? ② Upstream should probably not use install(1) to install hardlinked files; perhaps recreate the hardlinks in the destination like the BSDs do? I’ll forward this to the upstream mailing list. ** Changed in: klibc (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/2028571 Title: klibc-utils contains identical binaries Status in klibc package in Ubuntu: Confirmed Bug description: ``` $ jdupes -r /usr/lib/klibc/bin Scanning: 38 files, 1 items (in 1 specified) /usr/lib/klibc/bin/gunzip /usr/lib/klibc/bin/gzip /usr/lib/klibc/bin/zcat /usr/lib/klibc/bin/halt /usr/lib/klibc/bin/poweroff /usr/lib/klibc/bin/reboot ``` Please replace these binaries with symlinks to reduce the size of the uncompressed initramfs. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: klibc-utils 2.0.12-1 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Jul 24 21:14:36 2023 Dependencies: libklibc 2.0.12-1 InstallationDate: Installed on 2022-03-20 (491 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: klibc UpgradeStatus: Upgraded to lunar on 2023-04-20 (95 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/2028571/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2020814] Re: xmllint does not recognize emdash ( )
Hmm. I normally use libxml2 via xmlstarlet which has a somewhat nicer UX
than xmllint.
My guess is that you didn’t give a DTD, so it could only check that all
present entities are syntactically valid, but not expand them.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/2020814
Title:
xmllint does not recognize emdash ()
Status in libxml2 package in Ubuntu:
Invalid
Bug description:
I'm using Ubuntu 20.04.2 LTS, x85_64, fully patched. I'm using DocBook to
build a PDF. One of the steps I use in my build script is to validate and
format the XML using xmllint from libxml2-utils
2.9.13+dfsg-1ubuntu0.3:
echo "Validating book..."
if ! xmllint --xinclude --noout --postvalid book.xml
then
echo "Validation failed. Exiting."
exit 1
fi
echo "Complete."
echo "Formatting source code..."
for file in *.xml
do
if xmllint --format "${file}" --output "${file}.format"
then
mv "${file}.format" "${file}"
fi
done
echo "Complete."
When I added an emdash () the book failed to format:
Validating book...
Complete.
Formatting source code...
ch02.xml:58: parser error : Entity 'mdash' not defined
injections are remediated using several methods. And two output devices
^
ch02.xml:58: parser error : Entity 'mdash' not defined
methods. And two output devices the printer and plaintext email
^
Complete.
The text is:
... And two output devices the printer and plaintext
email do not require...
It seems like emdash should be recognized.
-
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04.2 LTS
Release:22.04
Codename: jammy
-
$ xmllint --version
xmllint: using libxml version 20913
compiled with: Threads Tree Output Push Reader Patterns Writer SAXv1 FTP
HTTP DTDValid HTML Legacy C14N Catalog XPath XPointer XInclude Iconv ICU
ISO8859X Unicode Regexps Automata Schemas Schematron Modules Debug Zlib Lzma
$ command -v xmllint
/usr/bin/xmllint
$ dpkg -S /usr/bin/xmllint
libxml2-utils: /usr/bin/xmllint
$ apt-cache show libxml2-utils
Package: libxml2-utils
Architecture: amd64
Version: 2.9.13+dfsg-1ubuntu0.3
Multi-Arch: foreign
Priority: optional
Section: text
Source: libxml2
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Debian XML/SGML Group
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 202
Depends: libc6 (>= 2.34), libxml2 (>= 2.9.0)
Filename:
pool/main/libx/libxml2/libxml2-utils_2.9.13+dfsg-1ubuntu0.3_amd64.deb
Size: 40192
MD5sum: 3ca7de07562010fcaabf255ea8fea9c4
SHA1: 128a9cfaff49e85f2ab08578f389eecb21f17766
SHA256: c279c07caf909545e2cedb7845b5ac652e0a70f9784e5faf799a1a01441b4649
SHA512:
51600d7206c9a5568fdaeee9adddbc48962fc094cc479f4bd42c0714b3725cd3200937f8c876a897db08fc50d891005d7dbabfb6ae12ad27ad6ed416f8b6a03d
Homepage: http://xmlsoft.org
...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/2020814/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2020814] Re: xmllint does not recognize emdash ( )
Yeah well, those portability problems were back in the 1990s when people
used latin1 or whatever codepages.
** Changed in: libxml2 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/2020814
Title:
xmllint does not recognize emdash ()
Status in libxml2 package in Ubuntu:
Invalid
Bug description:
I'm using Ubuntu 20.04.2 LTS, x85_64, fully patched. I'm using DocBook to
build a PDF. One of the steps I use in my build script is to validate and
format the XML using xmllint from libxml2-utils
2.9.13+dfsg-1ubuntu0.3:
echo "Validating book..."
if ! xmllint --xinclude --noout --postvalid book.xml
then
echo "Validation failed. Exiting."
exit 1
fi
echo "Complete."
echo "Formatting source code..."
for file in *.xml
do
if xmllint --format "${file}" --output "${file}.format"
then
mv "${file}.format" "${file}"
fi
done
echo "Complete."
When I added an emdash () the book failed to format:
Validating book...
Complete.
Formatting source code...
ch02.xml:58: parser error : Entity 'mdash' not defined
injections are remediated using several methods. And two output devices
^
ch02.xml:58: parser error : Entity 'mdash' not defined
methods. And two output devices the printer and plaintext email
^
Complete.
The text is:
... And two output devices the printer and plaintext
email do not require...
It seems like emdash should be recognized.
-
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04.2 LTS
Release:22.04
Codename: jammy
-
$ xmllint --version
xmllint: using libxml version 20913
compiled with: Threads Tree Output Push Reader Patterns Writer SAXv1 FTP
HTTP DTDValid HTML Legacy C14N Catalog XPath XPointer XInclude Iconv ICU
ISO8859X Unicode Regexps Automata Schemas Schematron Modules Debug Zlib Lzma
$ command -v xmllint
/usr/bin/xmllint
$ dpkg -S /usr/bin/xmllint
libxml2-utils: /usr/bin/xmllint
$ apt-cache show libxml2-utils
Package: libxml2-utils
Architecture: amd64
Version: 2.9.13+dfsg-1ubuntu0.3
Multi-Arch: foreign
Priority: optional
Section: text
Source: libxml2
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Debian XML/SGML Group
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 202
Depends: libc6 (>= 2.34), libxml2 (>= 2.9.0)
Filename:
pool/main/libx/libxml2/libxml2-utils_2.9.13+dfsg-1ubuntu0.3_amd64.deb
Size: 40192
MD5sum: 3ca7de07562010fcaabf255ea8fea9c4
SHA1: 128a9cfaff49e85f2ab08578f389eecb21f17766
SHA256: c279c07caf909545e2cedb7845b5ac652e0a70f9784e5faf799a1a01441b4649
SHA512:
51600d7206c9a5568fdaeee9adddbc48962fc094cc479f4bd42c0714b3725cd3200937f8c876a897db08fc50d891005d7dbabfb6ae12ad27ad6ed416f8b6a03d
Homepage: http://xmlsoft.org
...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/2020814/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2020814] Re: xmllint does not recognize emdash ( )
I doubt this is a bug: nowhere do you pass the validator a DTD, and
entities are defined in the DTD.
It’s best practice nowadays to not use entities but just write the UTF-8
characters directly.
An em dash surrounded by hair spaces is: “ — ” (for your copy/paste
convenience)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/2020814
Title:
xmllint does not recognize emdash ()
Status in libxml2 package in Ubuntu:
New
Bug description:
I'm using Ubuntu 20.04.2 LTS, x85_64, fully patched. I'm using DocBook to
build a PDF. One of the steps I use in my build script is to validate and
format the XML using xmllint from libxml2-utils
2.9.13+dfsg-1ubuntu0.3:
echo "Validating book..."
if ! xmllint --xinclude --noout --postvalid book.xml
then
echo "Validation failed. Exiting."
exit 1
fi
echo "Complete."
echo "Formatting source code..."
for file in *.xml
do
if xmllint --format "${file}" --output "${file}.format"
then
mv "${file}.format" "${file}"
fi
done
echo "Complete."
When I added an emdash () the book failed to format:
Validating book...
Complete.
Formatting source code...
ch02.xml:58: parser error : Entity 'mdash' not defined
injections are remediated using several methods. And two output devices
^
ch02.xml:58: parser error : Entity 'mdash' not defined
methods. And two output devices the printer and plaintext email
^
Complete.
The text is:
... And two output devices the printer and plaintext
email do not require...
It seems like emdash should be recognized.
-
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04.2 LTS
Release:22.04
Codename: jammy
-
$ xmllint --version
xmllint: using libxml version 20913
compiled with: Threads Tree Output Push Reader Patterns Writer SAXv1 FTP
HTTP DTDValid HTML Legacy C14N Catalog XPath XPointer XInclude Iconv ICU
ISO8859X Unicode Regexps Automata Schemas Schematron Modules Debug Zlib Lzma
$ command -v xmllint
/usr/bin/xmllint
$ dpkg -S /usr/bin/xmllint
libxml2-utils: /usr/bin/xmllint
$ apt-cache show libxml2-utils
Package: libxml2-utils
Architecture: amd64
Version: 2.9.13+dfsg-1ubuntu0.3
Multi-Arch: foreign
Priority: optional
Section: text
Source: libxml2
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Debian XML/SGML Group
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 202
Depends: libc6 (>= 2.34), libxml2 (>= 2.9.0)
Filename:
pool/main/libx/libxml2/libxml2-utils_2.9.13+dfsg-1ubuntu0.3_amd64.deb
Size: 40192
MD5sum: 3ca7de07562010fcaabf255ea8fea9c4
SHA1: 128a9cfaff49e85f2ab08578f389eecb21f17766
SHA256: c279c07caf909545e2cedb7845b5ac652e0a70f9784e5faf799a1a01441b4649
SHA512:
51600d7206c9a5568fdaeee9adddbc48962fc094cc479f4bd42c0714b3725cd3200937f8c876a897db08fc50d891005d7dbabfb6ae12ad27ad6ed416f8b6a03d
Homepage: http://xmlsoft.org
...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/2020814/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003826] [NEW] klibc/s390x on focal has broken setjmp/longjmp
Public bug reported: This is the same as https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=943425 which is fixed in Debian bullseye and Ubuntu impish but still present in focal. ** Affects: klibc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/2003826 Title: klibc/s390x on focal has broken setjmp/longjmp Status in klibc package in Ubuntu: New Bug description: This is the same as https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=943425 which is fixed in Debian bullseye and Ubuntu impish but still present in focal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/2003826/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1954716] Re: rpi nfsroot vers=4 not supported anymore?
Have you considered informing klibc upstream? (Granted, save for hpa that’s basically the Debian maintainers, but they don’t necessarily get Launchpad bugreports either.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1954716 Title: rpi nfsroot vers=4 not supported anymore? Status in klibc package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Invalid Bug description: I'm running `5.13.0-1011-raspi #13-Ubuntu SMP PREEMPT Fri Nov 19 18:40:23 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux` and have successfully set up netbooting on my RPi 4B (4GB). When I do not specify a `vers=` in cmdline.txt, NFS version 3 is used. I'd like to move to version 4, but unlike the setup described in https://forums.raspberrypi.com/viewtopic.php?p=1751741#p1751741, I cannot get `vers=4` (or any sub-version to work): the console logs `invalid value for vers.` for whatever I try. Current working cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp ro ip=dhcp rootwait fixrtc splash ``` Nonworking cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp,vers=4 ro ip=dhcp rootwait fixrtc splash ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1954716/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1729558] Re: [regression] In Java apps like Netbeans, dark menu bars don't look good for disabled elements
As far as I see, openjdk-8 (8u275-b01-1) contains this patch, so it was backported upstream. ** Changed in: openjdk-8 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1729558 Title: [regression] In Java apps like Netbeans, dark menu bars don't look good for disabled elements Status in Ubuntu theme: Invalid Status in openjdk-8 package in Ubuntu: Fix Released Status in openjdk-9 package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Invalid Bug description: This fix, #961679, specifically Ambiance/gtk-2.0/gtkrc:346 (http://bazaar.launchpad.net/~ubuntu-art-pkg/ubuntu- themes/trunk/revision/583), makes disabled elements in menus look terrible. Unfortunately I'm not aware of an easy way to get screenshots of open menus, so hopefully these attached phone pictures of Netbeans are enough to illustrate the issue. As you can see it is hard to tell the difference between what is disabled and what isn't, and the disabled items look fuzzy (easier to observe on monitor). I really don't see the issue with lighter menus, but if they must stay dark then the readability / contrast of disabled items needs to be fixed. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1729558/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850184] Re: losetup -f broken in 2.0.6-1ubuntu2
Yeah, I saw the mail; much better. I fixed one of these in dietlibc the other day… -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1850184 Title: losetup -f broken in 2.0.6-1ubuntu2 Status in klibc package in Ubuntu: Confirmed Status in klibc source package in Eoan: Confirmed Status in klibc source package in Focal: Confirmed Bug description: [Impact] * sudo /usr/lib/klibc/bin/losetup -vf, which appears to be missbuilt, as main(argc) is reset to zero, after ioctl() operations in a function call, quite unexpectadly. [Test Case] * $ sudo /usr/lib/klibc/bin/losetup -vf Loop device is /dev/loop20 loop: can't get info on device /dev/loop20: No such device or address is bad. Note that ioctl() must succeed, thus loop0 device must be configured to trigger the bug. [Regression Potential] * klibc is quite special, as it uses linux kernel headers/assembly. It seems like there is incompatibility between klibc sources, and gcc-9 with linux-5.3 when used to build userspace programmes. * disabling cf-protection and stack-clash-protection did not help. * building with gcc-8 does not exhibit the problem. * the workaround is quite simple in the code, keep a copy of argc to compare to it later in the code. [Other Info] * Original bug report http://autopkgtest.ubuntu.com/packages/c/casper/focal/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/amd64/c/casper/20191025_214555_df8b8@/log.gz ... [ 11.751912] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [ 11.761441] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) loop: can't get info on device /dev/loop1: No such device or address BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu4) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n+ mkdir result + set -x + read LINE + grep -e '^--OUT .* BEGIN-- .* --END--$' qemu-output.txt ++ grep -q /rofs result/lsblk.txt grep: result/lsblk.txt: No such file or directory autopkgtest [21:45:45]: test boot: ---] autopkgtest [21:45:45]: test boot: - - - - - - - - - - results - - - - - - - - - - boot FAIL non-zero exit status 2 autopkgtest [21:45:45]: summary boot FAIL non-zero exit status 2 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1850184/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850184] Re: losetup -f broken in 2.0.6-1ubuntu2
How is this even a fix? Also, does this affect other applications built against klibc? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1850184 Title: losetup -f broken in 2.0.6-1ubuntu2 Status in klibc package in Ubuntu: Confirmed Status in klibc source package in Eoan: Confirmed Status in klibc source package in Focal: Confirmed Bug description: [Impact] * sudo /usr/lib/klibc/bin/losetup -vf, which appears to be missbuilt, as main(argc) is reset to zero, after ioctl() operations in a function call, quite unexpectadly. [Test Case] * $ sudo /usr/lib/klibc/bin/losetup -vf Loop device is /dev/loop20 loop: can't get info on device /dev/loop20: No such device or address is bad. Note that ioctl() must succeed, thus loop0 device must be configured to trigger the bug. [Regression Potential] * klibc is quite special, as it uses linux kernel headers/assembly. It seems like there is incompatibility between klibc sources, and gcc-9 with linux-5.3 when used to build userspace programmes. * disabling cf-protection and stack-clash-protection did not help. * building with gcc-8 does not exhibit the problem. * the workaround is quite simple in the code, keep a copy of argc to compare to it later in the code. [Other Info] * Original bug report http://autopkgtest.ubuntu.com/packages/c/casper/focal/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/amd64/c/casper/20191025_214555_df8b8@/log.gz ... [ 11.751912] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [ 11.761441] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) loop: can't get info on device /dev/loop1: No such device or address BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu4) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n+ mkdir result + set -x + read LINE + grep -e '^--OUT .* BEGIN-- .* --END--$' qemu-output.txt ++ grep -q /rofs result/lsblk.txt grep: result/lsblk.txt: No such file or directory autopkgtest [21:45:45]: test boot: ---] autopkgtest [21:45:45]: test boot: - - - - - - - - - - results - - - - - - - - - - boot FAIL non-zero exit status 2 autopkgtest [21:45:45]: summary boot FAIL non-zero exit status 2 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1850184/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850184] Re: losetup -f broken in 2.0.6-1ubuntu2
Fun: this works with 2.0.7-1 built with gcc-9 in Debian. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1850184 Title: losetup -f broken in 2.0.6-1ubuntu2 Status in klibc package in Ubuntu: New Bug description: http://autopkgtest.ubuntu.com/packages/c/casper/focal/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/amd64/c/casper/20191025_214555_df8b8@/log.gz ... [ 11.751912] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [ 11.761441] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) loop: can't get info on device /dev/loop1: No such device or address BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu4) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n+ mkdir result + set -x + read LINE + grep -e '^--OUT .* BEGIN-- .* --END--$' qemu-output.txt ++ grep -q /rofs result/lsblk.txt grep: result/lsblk.txt: No such file or directory autopkgtest [21:45:45]: test boot: ---] autopkgtest [21:45:45]: test boot: - - - - - - - - - - results - - - - - - - - - - boot FAIL non-zero exit status 2 autopkgtest [21:45:45]: summary boot FAIL non-zero exit status 2 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1850184/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] Fwd: [Bug 1843743] Re: klibc ftbfs in eoan
-- Forwarded message -- From: Adam Conrad Message-ID: <157106879908.15546.2658970073129703906.mal...@soybean.canonical.com> 2.0.7-1 fails to build in the same way on Ubuntu 19.10. I'm assuming it's either glibc 2.30 (Debian is at 2.29) or linux 5.3 (Debian is at 5.2), with the latter being more likely. -- You received this bug notification because you are subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843743 Title: klibc ftbfs in eoan Status in klibc package in Ubuntu: Confirmed Status in klibc source package in Eoan: Confirmed Bug description: https://launchpadlibrarian.net/441262209/buildlog_ubuntu-eoan- amd64.klibc_2.0.6-1ubuntu1_BUILDING.txt.gz gcc -Wp,-MD,usr/klibc/.sigsuspend.o.d -nostdinc -iwithprefix include -I/<>/usr/include/arch/x86_64 -Iusr/include/arch/x86_64 -I/<>/usr/include/bits64 -Iusr/include/bits64 -I/<>/usr/klibc/../include -Iusr/klibc/../include -I/<>/usr/include -Iusr/include -I/<>/linux/include -Ilinux/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 -fno-stack-protector -fwrapv -fno-PIE -ggdb -m64 -Os -fomit-frame-pointer -mno-sse -falign-functions=1 -falign-jumps=1 -falign-loops=1 -fno-asynchronous-unwind-tables -W -Wall -Wno-sign-compare -Wno-unused-parameter -c -o usr/klibc/sigsuspend.o usr/klibc/sigsuspend.c usr/klibc/sigsuspend.c:8:10: fatal error: klibc/havesyscall.h: No such file or directory 8 | #include | ^ compilation terminated. make[4]: *** [/<>/scripts/Kbuild.klibc:252: usr/klibc/sigsuspend.o] Error 1 make[3]: *** [/<>/./Kbuild:9: all] Error 2 make[2]: *** [Makefile:118: klibc] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1843743/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1843743 Title: klibc ftbfs in eoan Status in klibc package in Ubuntu: Confirmed Status in klibc source package in Eoan: Confirmed Bug description: https://launchpadlibrarian.net/441262209/buildlog_ubuntu-eoan- amd64.klibc_2.0.6-1ubuntu1_BUILDING.txt.gz gcc -Wp,-MD,usr/klibc/.sigsuspend.o.d -nostdinc -iwithprefix include -I/<>/usr/include/arch/x86_64 -Iusr/include/arch/x86_64 -I/<>/usr/include/bits64 -Iusr/include/bits64 -I/<>/usr/klibc/../include -Iusr/klibc/../include -I/<>/usr/include -Iusr/include -I/<>/linux/include -Ilinux/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 -fno-stack-protector -fwrapv -fno-PIE -ggdb -m64 -Os -fomit-frame-pointer -mno-sse -falign-functions=1 -falign-jumps=1 -falign-loops=1 -fno-asynchronous-unwind-tables -W -Wall -Wno-sign-compare -Wno-unused-parameter -c -o usr/klibc/sigsuspend.o usr/klibc/sigsuspend.c usr/klibc/sigsuspend.c:8:10: fatal error: klibc/havesyscall.h: No such file or directory 8 | #include | ^ compilation terminated. make[4]: *** [/<>/scripts/Kbuild.klibc:252: usr/klibc/sigsuspend.o] Error 1 make[3]: *** [/<>/./Kbuild:9: all] Error 2 make[2]: *** [Makefile:118: klibc] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1843743/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843743] Re: klibc ftbfs in eoan
Probably fixed in 2.0.7 which fixed a parallel make issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1843743 Title: klibc ftbfs in eoan Status in klibc package in Ubuntu: Confirmed Status in klibc source package in Eoan: Confirmed Bug description: https://launchpadlibrarian.net/441262209/buildlog_ubuntu-eoan- amd64.klibc_2.0.6-1ubuntu1_BUILDING.txt.gz gcc -Wp,-MD,usr/klibc/.sigsuspend.o.d -nostdinc -iwithprefix include -I/<>/usr/include/arch/x86_64 -Iusr/include/arch/x86_64 -I/<>/usr/include/bits64 -Iusr/include/bits64 -I/<>/usr/klibc/../include -Iusr/klibc/../include -I/<>/usr/include -Iusr/include -I/<>/linux/include -Ilinux/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 -fno-stack-protector -fwrapv -fno-PIE -ggdb -m64 -Os -fomit-frame-pointer -mno-sse -falign-functions=1 -falign-jumps=1 -falign-loops=1 -fno-asynchronous-unwind-tables -W -Wall -Wno-sign-compare -Wno-unused-parameter -c -o usr/klibc/sigsuspend.o usr/klibc/sigsuspend.c usr/klibc/sigsuspend.c:8:10: fatal error: klibc/havesyscall.h: No such file or directory 8 | #include | ^ compilation terminated. make[4]: *** [/<>/scripts/Kbuild.klibc:252: usr/klibc/sigsuspend.o] Error 1 make[3]: *** [/<>/./Kbuild:9: all] Error 2 make[2]: *** [Makefile:118: klibc] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1843743/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799014] Re: bold font rendeing in Java is broken in Cosmic with OpenJDK 11
The testcase needs the “package test;” in the first line removed / commented-out, then it works. This works in 11.0.1+13-2 on Debian sid, as a new data point. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to freetype in Ubuntu. https://bugs.launchpad.net/bugs/1799014 Title: bold font rendeing in Java is broken in Cosmic with OpenJDK 11 Status in freetype package in Ubuntu: Confirmed Status in openjdk-lts package in Ubuntu: New Bug description: Since update to Cosmic, I see that bold fonts in Java have broken rendering. See attached 400% scaled PNG for illustration. The 'r' in bold rendering of "Hello World" shows basically a vertical line from the end of the hook end. I am not entirely sure this is freetype issue but some sources (https://github.com/adobe/brackets/issues/14290) suggest there is a bug in the 2.8.1 version that Cosmic seems to install (libfreetype6/cosmic,now 2.8.1-2ubuntu2 amd64 [installed]). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1799014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1701068] Re: motd.ubuntu.com currently shows media item (HBO's Silicon Valley using Ubuntu)
“The default configuration is that this "motd-news" feature is enabled and that it will check https://motd.ubuntu.com for updates.” is called “a useful feature” by the author of the LWN article, and in this bugreport. In the Debian world, we call this a phone-home privacy violation which is a security-relevant release-critical bug and an absolute MUST NOT. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1701068 Title: motd.ubuntu.com currently shows media item (HBO's Silicon Valley using Ubuntu) Status in base-files package in Ubuntu: Opinion Bug description: In Ubuntu 17.04 or newer, there is a script at /etc/update-motd.d/50 -motd-news that reads https://motd.ubuntu.com/ and displays that text with the rest of the MOTD. Currently, https://motd.ubuntu.com shows a news item about HBO's Silicon Valley which has a reference to Ubuntu. Instead, https://motd.ubuntu.com should show relevant items to those that use Ubuntu Server (relevant security issues, etc), instead of items for desktop users. = Welcome to Ubuntu 17.04 (GNU/Linux 4.10.0-21-generic x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage * How HBO's Silicon Valley built "Not Hotdog" with mobile TensorFlow, Keras & React Native on Ubuntu - https://ubu.one/HBOubu == ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: base-files 9.6ubuntu13 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Wed Jun 28 12:31:24 2017 InstallationDate: Installed on 2017-05-02 (56 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: base-files UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1701068/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1589836] Re: package libxml2-utils 2.9.3+dfsg1-1 failed to install/upgrade: krijg geen toegang tot archief: Bestand of map bestaat niet
AUB niet de files verwijderen tijdens apt nog aan’t werken is. Probeer es: $ sudo apt-get update $ sudo apt-get -f install -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1589836 Title: package libxml2-utils 2.9.3+dfsg1-1 failed to install/upgrade: krijg geen toegang tot archief: Bestand of map bestaat niet Status in libxml2 package in Ubuntu: Invalid Bug description: The package failed to upgrade in the terminal. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libxml2-utils 2.9.3+dfsg1-1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Jun 7 09:40:41 2016 ErrorMessage: krijg geen toegang tot archief: Bestand of map bestaat niet InstallationDate: Installed on 2016-04-23 (44 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: libxml2 Title: package libxml2-utils 2.9.3+dfsg1-1 failed to install/upgrade: krijg geen toegang tot archief: Bestand of map bestaat niet UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1589836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1589679] Re: package libxml2 2.9.3+dfsg1-1 failed to install/upgrade: unable to securely remove '/usr/share/doc/libxml2/AUTHORS.dpkg-new': Read-only file system
I suggest to learn to read. Mount your filesystems read-write when you install packages. ** Changed in: libxml2 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1589679 Title: package libxml2 2.9.3+dfsg1-1 failed to install/upgrade: unable to securely remove '/usr/share/doc/libxml2/AUTHORS.dpkg-new': Read-only file system Status in libxml2 package in Ubuntu: Invalid Bug description: occur when i update ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libxml2 2.9.3+dfsg1-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 Date: Mon Jun 6 17:10:44 2016 DuplicateSignature: package:libxml2:2.9.3+dfsg1-1 Unpacking libxml2:i386 (2.9.3+dfsg1-1ubuntu0.1) over (2.9.3+dfsg1-1) ... dpkg: error processing archive /var/cache/apt/archives/libxml2_2.9.3+dfsg1-1ubuntu0.1_i386.deb (--unpack): unable to securely remove '/usr/share/doc/libxml2/AUTHORS.dpkg-new': Read-only file system ErrorMessage: unable to securely remove '/usr/share/doc/libxml2/AUTHORS.dpkg-new': Read-only file system InstallationDate: Installed on 2016-05-26 (10 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: libxml2 Title: package libxml2 2.9.3+dfsg1-1 failed to install/upgrade: unable to securely remove '/usr/share/doc/libxml2/AUTHORS.dpkg-new': Read-only file system UpgradeStatus: Upgraded to xenial on 2016-05-27 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1589679/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1493999] Re: xz-utils package is really, really old
This is being discussed in Debian already. Please don’t do this separately. Instead, work with the Debian maintainer to do this, then do a SyncRequest. ** Bug watch added: Debian Bug tracker #731634 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731634 ** Also affects: xz-utils (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731634 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xz-utils in Ubuntu. https://bugs.launchpad.net/bugs/1493999 Title: xz-utils package is really, really old Status in xz-utils package in Ubuntu: Confirmed Status in xz-utils package in Debian: Unknown Bug description: Willy is currently using a really old version of xz-utils. The latest version at this time is 5.2.1 released on 2015-02-26 http://git.tukaani.org/?p=xz.git;a=blob;f=NEWS;hb=HEAD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/1493999/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1358762] Re: Included gzip 1.2.4 has several vulnerabilities
I have just looked at whether gzip can be replaced by BSD compress(1), which is a drop-in replacement under a more free licence, but even after adding fts and a lot of BSD functions it still needs funopen() which klibc doesn’t have ☹ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1358762 Title: Included gzip 1.2.4 has several vulnerabilities Status in “klibc” package in Ubuntu: Confirmed Bug description: The included gzip version is quite old (version 1.2.4) and has several security vulnerabilities. Check http://web.nvd.nist.gov/view/vuln/search- results?adv_search=truecves=oncpe_version=cpe:/a:gnu:gzip:1.2.4 for example. I explicitly checked for CVE-2001-1228, which was not fixed by a patch in the klibc package, so I assume the other vulnerabilities are not fixed either. I think it would be a good idea to update the included gzip to a current version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1358762/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1358762] Re: Included gzip 1.2.4 has several vulnerabilities
Nevermind. I hacked MirBSD compress to omit the BSD compress method (so it only does gzip), and replaced a few more things, and got a working gzip/gunzip under BSD licence. If there is any interest in the klibc side to include that, be my guest. Sizes are nice, too (dynamically linked): tglase@tglase:~/mbsd/src/usr.bin/compress $ size /usr/lib/klibc/bin/gzip obj/compress textdata bss dec hex filename 258283016 316552 345396 54534 /usr/lib/klibc/bin/gzip 18802 04208 2301059e2 obj/compress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1358762 Title: Included gzip 1.2.4 has several vulnerabilities Status in “klibc” package in Ubuntu: Confirmed Bug description: The included gzip version is quite old (version 1.2.4) and has several security vulnerabilities. Check http://web.nvd.nist.gov/view/vuln/search- results?adv_search=truecves=oncpe_version=cpe:/a:gnu:gzip:1.2.4 for example. I explicitly checked for CVE-2001-1228, which was not fixed by a patch in the klibc package, so I assume the other vulnerabilities are not fixed either. I think it would be a good idea to update the included gzip to a current version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1358762/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1358762] Re: Included gzip 1.2.4 has several vulnerabilities
As I mentioned in IRC: I can probably easily shave another 2½K off .text by removing stub support for multiple compressors and using the gzopen() API already shipped by klibc. Note that klibc bundles zlib 1.2.3 whereas even MirBSD has 1.2.8 already. That would also need updating. But at least, MirBSD compress uses zlib for gzip I/O instead of bundling its own inflate/deflate functions as GNU gzip does. All is 2-clause and 3-clause BSD and MIT licence. ** Also affects: klibc Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1358762 Title: Included gzip 1.2.4 has several vulnerabilities Status in klibc: New Status in “klibc” package in Ubuntu: Confirmed Bug description: The included gzip version is quite old (version 1.2.4) and has several security vulnerabilities. Check http://web.nvd.nist.gov/view/vuln/search- results?adv_search=truecves=oncpe_version=cpe:/a:gnu:gzip:1.2.4 for example. I explicitly checked for CVE-2001-1228, which was not fixed by a patch in the klibc package, so I assume the other vulnerabilities are not fixed either. I think it would be a good idea to update the included gzip to a current version. To manage notifications about this bug go to: https://bugs.launchpad.net/klibc/+bug/1358762/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1370012] Re: upstart: (mis)uses shell reserved word ”stop”
@dino99 no it’s not related. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1370012 Title: upstart: (mis)uses shell reserved word ”stop” Status in “upstart” package in Ubuntu: Confirmed Bug description: upstart (1.5-0ubuntu7.2) /lib/init/upstart-job uses “stop” (in line 93) which is a reserved shell word. If using mksh (actually /bin/lksh) as /bin/sh, which defines this as default alias, upgrading udev, which wants to restart the udev service, fails. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1370012/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1370012] [NEW] upstart: (mis)uses shell reserved word ”stop”
Public bug reported: upstart (1.5-0ubuntu7.2) /lib/init/upstart-job uses “stop” (in line 93) which is a reserved shell word. If using mksh (actually /bin/lksh) as /bin/sh, which defines this as default alias, upgrading udev, which wants to restart the udev service, fails. ** Affects: upstart (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1370012 Title: upstart: (mis)uses shell reserved word ”stop” Status in “upstart” package in Ubuntu: New Bug description: upstart (1.5-0ubuntu7.2) /lib/init/upstart-job uses “stop” (in line 93) which is a reserved shell word. If using mksh (actually /bin/lksh) as /bin/sh, which defines this as default alias, upgrading udev, which wants to restart the udev service, fails. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1370012/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
