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.
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
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
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
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
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
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
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
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
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
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
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
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
-- 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
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
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
“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
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.
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.
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
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
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):
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,
@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
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
25 matches
Mail list logo
