On Sat, 3 Sep 2022, Helge Kreutzmann wrote:
> The upload of manpages-l10n (manpages-fr) was just accepted in
> unstable.
OK, thanks.
AIUI we now need another upload of src:sysvinit in which bin:bootlogd
gets a Replaces and Breaks on manpages-fr (<< 4.15.0-9~), correct?
I can do that this
Hi Helge,
[…]
> Yes, that would be the best option. A few days ago I informed all
> translation teams about the transfer of translations to sysvinit, so
> if the French team could integrate the translation of bootlogd there,
> that'll be great.
ok, great!
> For Debian, as stated above, I can
On Wed, 31 Aug 2022, Mark Hindley wrote:
> > there seems to be one manpage (in bootlogd) missing conflict handling:
> >
> > /usr/share/man/fr/man8/bootlogd.8.gz
>
> Thanks. I was under the impression that manpages-i10n had changed to
> systemd versions (which doesn't have bootlogd.8) but
On Wed, 31 Aug 2022, S. wrote:
> laptop. It would be great if the 20210818-1 firmware version could be offered
> in Backports.
Backports are not to fix bugs in stable. Issues like this should
be fixed via the normal stable channels if possible and the normal
bugtracker is used to track that.
Package: linux-headers-5.19.0-trunk-amd64
Version: 5.19-1~exp1
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
In building an out-of-tree kernel module I wrote on 5.19 (to test
compatibility), I noticed a new error message.
/usr/lib/linux-kbuild-5.19/scripts/Makefile.modfinal emits the
message,
Package: qa.debian.org
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
There used to be a box (or something, I mostly use this with lynx)
for testing migration status, but it’s apparently now missing.
I know tracker.d.o has it, but that site’s appalling in UI/UX and
looks awful and it’s much
outlook 1017537 some armel buildds are misconfigured and lack SWP emulation
thanks
Dixi quod…
># if __ARM_ARCH__ < 6
> swp r0, r1, [r2]
># else
And this, after some research, is it. This is needed for armel, which
is v5. Apparently, Linux has SWP emulation for v7/v8 hosts, but at
Dixi quod…
>In case this makes anyone immediately think of whatever it is:
Code looks right enough (with an explanation of why this only
fails on armel but not on armhf which is perfectly fine):
$ cat arm/__testandset.S
#include "arm-features.h"
FUNC_START __testandset
mov r2,
>but it ALSO fails in a bullseye chroot, so this is possibly not related
In case this makes anyone immediately think of whatever it is:
(gdb) r
Starting program: /home/tg/dietlibc-0.34~cvs20160606-el-11/debian/unittests/ttt
Program received signal SIGILL, Illegal instruction.
__testandset () at
outcome 1017537 fails on porterbox/bullseye as well, suspect 64-bit host to be
an issue
tags 1017537 + help
thanks
In contrast to armhf, which works fine on the porterbox (amdahl; abel,
which I normally use, is currently down) for me, this one also fails,
but it ALSO fails in a bullseye chroot,
tags 1017538 + unreproducible
thanks
This builds fine in a sid-armhf chroot on amdahl.
Markus Koschany dixit:
>The --add-opens error message was misleading and it turned out the underlying
>root cause for the FTBFS was a different one. Gradle currently fails to build
>because of a different jansi bug.
OK, so keep that one open and close this one?
>There is still some work to do
Markus Koschany dixit:
>The newly added --add-opens option is only valid for OpenJDK 17. I
>understand that we switch to it for Debian 12 but it currently breaks
>all packages that are built with OpenJDK 11. I am currently in the
Is this true? AFAIK --add-opens is for 11+ (probably even 9+). It
Package: src:linux
Version: 5.10.136-1
Severity: grave
Justification: causes non-serious data loss
X-Debbugs-Cc: t...@mirbsd.de
I’ve recently been getting filesystem corruption on this system, which,
incidentally, is a fresh-ish installation since I’ve been hit by the
“forgot LUKS password for
Arnd Bergmann dixit:
>The way the FPU type gets selected in gcc changed with recent versions,
>this was intentional and won't be reverted but it did break packages that
>used the old method.
Hmph.
>In most cases, it's sufficient to pass
>-march=armv7-a+fp instead of -march=armv7-a to pick the
Arnd Bergmann dixit:
>I tried cross-building it myself now and found the same issue with
>an older arm-linux-gnueabihf-gcc-11, which invokes the assembler as
>
>/usr/lib/gcc-cross/arm-linux-gnueabihf/11/../../../../arm-linux-gnueabihf/bin/as
>-v -march=armv7-a -mfloat-abi=hard -meabi=5 -o
Sebastian Ramacher dixit:
>This is already an issue with 0.34~cvs20160606-12.
It’s an incompatible toolchain change that broke this package.
I’m trying to find out why, but the ARM porters are not helpful.
bye,
//mirabilos
--
Support mksh as /bin/sh and RoQA dash NOW!
‣ src:bash (406 (433)
Arnd Bergmann dixit:
>-march=armv7-a+fp instead of -march=armv7-a to pick the right
“instead of”
We pass nothing there, and we need a solution (or two distinct
ones) for armel and armhf.
bye,
//mirabilos
--
[...] if maybe ext3fs wasn't a better pick, or jfs, or maybe reiserfs, oh but
what
tags 1017538 + help
forwarded 1017538 https://lists.debian.org/debian-arm/2022/07/msg00041.html
thanks
Hi Sebastian,
instead of filing a bug with the information we already have…
>arm/__longjmp.S: Assembler messages:
>arm/__longjmp.S:9: Error: selected processor does not support `vldm
Package: libqt5gui5
Version: 5.15.2+dfsg-9
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
Running a Qt application (musescore3) against Valgrind shows:
==27770== Conditional jump or move depends on uninitialised value(s)
==27770==at 0x7470A2E: __vfprintf_internal (vfprintf-internal.c:1687)
Dixi quod…
>I got a new version of logrotate on multiple systems due to the
>security/point release, and since then I get, every night, from
>all of them, this:
After a while, I can now say it’s only once for every system,
but I had upgraded several in waves and over nights, so the
eMails spread
Octavio Alvarez dixit:
> On 31/07/22 14:57, Thorsten Glaser wrote:
>> debdiff (±version) attached. Would you prefer for me to NMU, do a
>> maintainer-agreed regular upload (as -2), or handle this yourself,
>> Octavio?
>
> I can handle it. By the way, did the fix work f
On Wed, 3 Aug 2022, Adam Borowski wrote:
> On Wed, Aug 03, 2022 at 12:04:29AM +0200, GSR wrote:
> > Otherwise in cases like upgrading lvm2 (see bug #1014565) the full
This is weird, but I looked at how debootstrap resolves dependencies,
and this is indeed a problem. Did anyone look at whether
# bts-close because of the reason below
close 1016482
thanks
Bo YU dixit:
>The jamulus can be built on real riscv64 hardware successfully with the
>change attached, so could you please add riscv64 as a build target in
>new upload? thanks
It can also be built successfully on big-endian
p 1.10 compatibility (Closes: #1016129)
+
+ -- Thorsten Glaser Sun, 31 Jul 2022 21:43:23 +0200
+
ipv6toolkit (2.0+ds.1-1) unstable; urgency=medium
* Refreshed patches using gbp pq export. Added:
diff -Nru
ipv6toolkit-2.0+ds.1/debian/patches/03b0fdd42cf36c0070472afbb9b81a9ca62e1109.patch
ipv6toolk
Hi Simon,
>I guess something changed in 'dh' to cause this new behaviour. Any
>ideas?
good guess but no idea, I don’t follow dh development closely. Best
to ask that team then?
bye,
//mirabilos
--
15:41⎜ Somebody write a testsuite for helloworld :-)
Package: ovmf
Version: 2020.11-2+deb11u1
Severity: important
X-Debbugs-Cc: t...@mirbsd.de
Configuring a qemu/kvm amd64 VM in virt-manager with a SCSI controller
(lsilogic in my attempt, other people report¹ virtio-scsi to be affected
as well) makes the system not boot with EFI (BIOS boot works).
Package: dpkg
Version: 1.20.11
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
I had a filesystem corruption (had to run e2fsck -D for some reason, the
filesystem was otherwise intact, fresh install) that resulted in…
dpkg: unrecoverable fatal error, aborting:
files list file for package
Cc libpcap maintainers; context is #1016129 on debbugs.
From diffing around between a buster and a bullseye system, I could
track this bug down:
libpcap0.8:
1.10.0-2 500
500 http://deb.debian.org/debian bullseye/main amd64 Packages
1.10.0-2~bpo10+1 100
100
Package: libapache2-mod-jk
Version: 1:1.2.48-1
Severity: critical
Justification: breaks unrelated software
X-Debbugs-Cc: t...@mirbsd.de
After upgrading from buster to bullseye, apache2 does not start any more
if libapache2-mod-jk was installed and active prior to the upgrading:
$ sudo cleanenv /
Package: ipv6toolkit
Version: 2.0+ds.1-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: t...@mirbsd.de
Control: forwarded -1 https://github.com/fgont/ipv6toolkit/issues/78
$ sudo tcp6 -i eth1 -d fec0::1 -y 500 -a 13 -P 600
Error while performing Neighbor Discovery for the
Simon McVittie dixit:
>If that's what you want, here are diffs (these are only the xfonts-base
>subset, the remarkably similar diffs for the other packages will follow
>when I get round to it).
Thanks. Looking good.
>Or if you want to try the web UI, closing the file list/search on the
>left
Matthias Klose dixit:
>The goal is to enable this optimization by default in an upcoming
>Debian release in dpkg-buildflags for 64bit architectures. The goal
>is to get this package to build with link time optimizations, or to
>explicitly disable link time optimizations for this package build.
Package: libidn2-0
Version: 2.3.3-1
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
A new dependency on sgml-base was introduced to the shared library
package, and it’s not documented in the changelog. This raises red
flags.
-- System Information:
Debian Release: bookworm/sid
APT prefers
On Sun, 17 Jul 2022, Craig Sanders wrote:
> > You most likely want some pinning.
>
> I've never found pinning to be of much use. When I did have an actual use for
[…]
No, not that. You need it to get apt to not even consider systemd
installable.
> wanted. Far more work than it was worth - I
On Sun, 17 Jul 2022, Craig Sanders wrote:
> and, of course:
>
> apt-mark hold sysvinit-core
>
> To prevent systemd from being auto-installed in some future upgrade.
You most likely want some pinning. Just held in dpkg or even marked
as XB-Important: yes often brings apt to tears in sid,
Nicholas D Steeves dixit:
>Sorry for the extremely belated reply. I did read your reply soon after
>you sent it :)
No problem, we are all doing this in our spare time…
>Ah, now I see what you mean about 4.x being upstream focus.
They focus on it to the exclusion of 3.x support. It was similar
Package: distro-info-data
Version: 0.53
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de, raph...@freexian.com
Current information is:
$ column -ts, https://deb.freexian.com/extended-lts/docs/debian-8-support/ and
https://deb.freexian.com/extended-lts/docs/debian-9-support/ for more.
change jessie
Package: logrotate
Version: 3.18.0-2+deb11u1
Severity: important
X-Debbugs-Cc: t...@mirbsd.de, t...@security.debian.org
I got a new version of logrotate on multiple systems due to the
security/point release, and since then I get, every night, from
all of them, this:
│Subject: Anacron job
Package: jq
Version: 1.6-2.1
Followup-For: Bug #878091
X-Debbugs-Cc: t...@mirbsd.de
Still pertinent in latest version:
$ echo '[.1,0.2]' | jq -c .
[0.1,0.2]
-- System Information:
Debian Release: 11.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500,
Package: jq
Version: 1.5+dfsg-2+b1
Followup-For: Bug #878091
Same:
$ echo '[.1,0.2]' | jq -c .
[0.1,0.2]
With no flag to turn this off, I’d almost consider this serious.
-- System Information:
Debian Release: 10.12
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500,
Marco d'Itri dixit:
>On Jun 21, Thorsten Glaser wrote:
>
>> The /etc/inetd.conf file does not contain even commented-out
>> lines for the standard services.
>I am surely not going to encourage people configuring the UDP small
>services, which are a source of reflection
Diederik de Haas dixit:
>I proposed my patch to expedite things and (much) prefer that Thorsten would
I’m not the author…
>I can do it, but I would like Thorsten to test the patch and confirm it
It’s obviously correct, it moves the nil check to the correct place.
I tested “the reverse” by
Package: ffmpeg
Version: 7:4.3.4-0+deb11u1
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
I’ve seen people use ffmpeg to add metadata to .wav files
and wanted to try it.
ffmpeg -i /usr/share/sounds/alsa/Noise.wav -metadata comment='miau mäh mio'
foo.wav
It added an ICMT (good) and an ISFT
Emmanuel Bourg dixit:
> Because separate packages means separate responsibilities. I'd like not
It’s a *TEAM* responsibility. I joined the team at some point in the past.
> to maintain again sysvinit scripts in any Java package, we don't have
> the time for this (we barely keep up with the Java
Hi Emmanuel,
> With these changes I think it's now possible to detach the sysvinit script
> into an independent package (tomcat9-sysvinit?) enhancing tomcat9.
*WHY*?
The remaining changes do not change the way it is run under systemd
AT ALL.
Having an extra binary package just for a handfull
Debian FTP Masters dixit:
> tomcat9 (9.0.64-2) unstable; urgency=medium
> .
> * Fallback to the default log formatter when systemd isn't used
> * Depend on systemd-sysusers and systemd-tmpfiles instead of systemd
> * Depend on libeclipse-jdt-core-java (>= 3.26.0)
I guess it’s now also the
Diederik de Haas dixit:
>I'm talking here about 4.9, not 4.19 ...
Ah sorry, I can’t keep them distinguished in my head apparently, or
it’s too hot…
>> $ git tag --contains 92833e8b5db6
>> v4.19.221
>> […]
>
>Thanks for that command :-) I usually went through several manual steps to
>figure out
Diederik de Haas dixit:
>In branch 'linux-4.9.y' there is no qdisc_put function, so the above check
>seems rightly in qdisc_destroy there.
Not any more. Since…
$ git tag --contains 92833e8b5db6
v4.19.221
[…]
… qdisc_destroy was renamed to qdisc_put in 4.19, breaking modules (grr).
So yes,
Control: tag -1 - moreinfo
Diederik de Haas dixit:
>In Debian, the release before 4.19.235-1 was 4.19.232-1 which should also have
>this bug. The release before that was 4.19.208-1, which shouldn't.
>Can you verify that?
Not easily any more, but I know it worked some weeks ago, and I *think*
I
Diederik de Haas dixit:
>It's a bit 'above my paygrade', but if qdisk_put() can accept a NULL pointer
>then I'm curious whether that would be allowed for other functions in that file
>as well ... there are several having "struct Qdisc *qdisc" as (only)
>parameter, but only qdisk_put() checks for
Package: netcat-openbsd
Version: 1.217-3
Followup-For: Bug #747646
X-Debbugs-Cc: t...@mirbsd.de
Control: severity -1 important
This makes nc totally unusable for UDP.
-- System Information:
Debian Release: 11.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500,
Package: openbsd-inetd
Version: 0.20160825-5
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
The /etc/inetd.conf file does not contain even commented-out
lines for the standard services.
I’m attaching mildly tested sample lines that ought to be present
in the file when installing the package.
Package: src:linux
Version: 4.19.235-1
Severity: critical
Tags: upstream
Justification: breaks the whole system
A recent upstream “stable” upgrade backported the removal of the
qdisc_destroy() function (which, in itself, is questionable enough
already and caused no small amount of fun) using
Patrik Schindler dixit:
>What is your opinion about staying current with security updates for
>this specifically crafted package?
Not (that I can see) a security update, but I’ve updated it to match
today’s (yesterday’s?) sid upload.
The repository also has an RSS feed.
bye,
//mirabilos
--
Bastian Blank dixit:
>The pool size for an RPNG is only the size of the state, nothing else.
Yes, and that is the problem. It was small before, it’s ridiculous now.
>might not have had any value before anyway. You just need to reseed on
>a regular interval.
Ugh. I recall reading something
Package: src:linux
Version: 5.10.120-1
Severity: serious
Tags: security
X-Debbugs-Cc: Debian Security Team
/proc/sys/kernel/random/poolsize is now 256 instead of 4096 bits,
which was already small before.
Why was such a change allowed into stable?
This also breaks rngd’s --fill-watermark
Patrik Schindler dixit:
>a BIG and HUGE "THANK YOU" for your service to the community!
You’re welcome.
>> You wrote you need only tomcat and prefer pinning.
>
>Is there another way?
Not that I know of.
>> I’ve not had much success with pinning myself, other than to tell apt
>> to never
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Instructions back to the list, in case this is of more general interest.
Dixi quod…
>>What is your opinion about staying current with security updates for
>>this specifically crafted package?
>
>If I know I have users I can stay on top of other
Diederik de Haas dixit:
>and the patch proposed by Ben, more then 6 years ago, hasn't been merged.
>
>As I don't know the reason it wasn't closed last year, I won't do it, but
>maybe it's time to finally close it?
If the bug persists, it’s still a bug, so don’t close it.
Prod them occasionally.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Patrik Schindler dixit:
>Am 02.06.2022 um 16:47 schrieb Thorsten Glaser :
>
>> I’ll update the sysvinit branch and publish a new build of the
>> package in my personal APT repository then (I’ve not done so for a
>> w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Patrik Schindler dixit:
>Me also is highly interested a current tomcat not relying on systemd
>but also working with sysvinit. Today, we're at Deb 11 Bullseye, and
>the issue apparently has not been sorted out.
I’ll update the sysvinit branch and
Package: firefox-esr
Version: 91.9.1esr-1~deb11u1
Followup-For: Bug #993308
X-Debbugs-Cc: t...@mirbsd.de
This seems to indeed be required now, but not caught by
dpkg-shlibdeps as (web searches indicate at least) it’s
dlopened.
-- Package-specific info:
-- Extensions information
Name:
Package: fbterm
Version: 1.7-5
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
When logging in to a device over SSH and trying to render something
on the framebuffer, fbterm cannot be used because it shows the
error message “stdin isn't a interactive tty!” (which should also
be “isn’t an
On Wed, 18 May 2022, Carlo Stemberger wrote:
> I'd like to do it myself, but:
> 1) It's a very big project;
> 2) I have 0 experience in packaging;
> 3) I'm not a Java programmer
>
> Is there someone interested in helping me?
This is then probably quite a bit more than just helping…
> First
On Sun, 15 May 2022, Adam Borowski wrote:
> The tables are loaded on setlocale(LC_CTYPE, ""), iswalpha() is inoperative
> at the start of the program.
That is normal: at the beginning of main(), the program operates
in the C locale.
bye,
//mirabilos
--
Infrastrukturexperte • tarent solutions
Paul Gevers dixit:
> On 07-05-2022 10:53, Michael Tokarev wrote:
Huh, didn't get that message.
>> In this bugreport, I see it is/was broken with -machine pc-1.1.
>> There's no indication if it is broken with other machine types. As
>> of qemu 5.2 (bullseye) machine types below pc-1.3 are
On Sat, 7 May 2022, Adam Borowski wrote:
> I've proposed this myself several years ago but it was then rejected. IIRC
> one of the concerns raised was that eg. Postgresql tools do "unset LANG
> LC_ALL LC_CTYPE" to get the "C" locale.
File a bug against those then; POSIX explicitly states that
On Sat, 7 May 2022, Adam Borowski wrote:
> As of Bookworm, ancient encodings are no longer supported. There are
?
> But, as glibc still considers unset locale to mean "C" rather than
> "C.UTF-8", _something_ must set these variables. Debian-installer does
There's talk to chage that in
Package: molly-guard
Version: 0.7.2
Severity: wishlist
X-Debbugs-Cc: t...@mirbsd.de
For all active cryptsetup/luks/whatever discs
whose key is not random (such as in
#
cswap /dev/vg-tglase/lv-swap /dev/random
cipher=aes-xts-plain64,size=256,discard,plain,swap
in
On Fri, 29 Apr 2022, Evren Yurtesen wrote:
> > What is the problem with logrotate? It happily rotates files owned
> > by anyone in Debian.
>
> Because in Ubuntu rsyslog drops privileges to `syslog` user.
> Therefore, the log files generated by rsyslog are owned by the
> `syslog` user. But
(warning, bit of rambling, plus I was interruped multiple times while
writing this and not fully awake yet either)
Nicholas D Steeves dixit:
>In an earlier update you mentioned that there were numerous regressions
>and problems with these new releases. Are these limited to non-dfsg
No, they
On Fri, 22 Apr 2022, Mark Hindley wrote:
> > Or Replaces: but that has downsides on deinstallation.
>
> Yes. And I am unclear how dpkg would behave if sysvinit-core was installed
> Replacing the manpages-l10n versions but then manpages-l10n was upgraded.
Hm. Given that manpages-l10n would *not*
close 896907
thanks
Hi,
closing as the requested moreinfo was not provided in the last ~year
and we’re moving toward 17 as supported JDK/JRE.
bye,
//mirabilos
--
Gestern Nacht ist mein IRC-Netzwerk explodiert. Ich hatte nicht damit
gerechnet, darum bin ich blutverschmiert… wer konnte ahnen,
On Wed, 20 Apr 2022, Mark Hindley wrote:
> > The only solution I can imagine is the Alternatives system, so we
> > identify which man pages conflict and both manpages-l10n and sysvinit
> > establish alternatives for those translations.
>
> The other possibility might be dpkg-diverts. Perhaps
Dixi quod…
>ca-certificates setup. In fact, I’d prefer to control the files
>placed into the chroot, copying just the /usr/share/ca-bundle/certs/
>files and symlinks (which are already c_rehash’d) to get rid of
>the ssl-cert-snakeoil.pem presence (which Debian seems to insist
>on for some reason)
Dixi quod…
>smtpd_tls_CApath = /etc/ssl/certs
>smtp_tls_CApath = $smtpd_tls_CApath
It also seems to copy+rehash twice for this very common setup…
bye,
//mirabilos
--
(gnutls can also be used, but if you are compiling lynx for your own use,
there is no reason to consider using that package)
Package: postfix
Version: 3.5.6-1+b1
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
I was just debugging why Postfix (after finding first
smtpd_tls_received_header=yes then smtpd_tls_ask_ccert=yes)
does not properly verify the SSL certificates provided by
my sendmail servers.
Turns out that…
la...@debian.org dixit:
>On my bullseye machine sudo rpm -qa creates the subdirectory in
>/root/.rpmdb as root. So IMO this works correct.
Not with !env_reset in sudoers, though :( as I wrote in the last mail.
bye,
//mirabilos
--
Gestern Nacht ist mein IRC-Netzwerk explodiert. Ich hatte nicht
Hi Mark,
> On Mon, Apr 18, 2022 at 07:44:11AM +0100, Mark Hindley wrote:
> > There is already a wishlist bug with patch[1]. Maybe you could test and
> > refine
> > it?
>
> I have had a quick look at this today and have the attached patch (based on
> Patrick's original suggestions) for review and
reassign 1008818 rpm
found 1008818 4.16.1.2+dfsg1-3
affects 1008818 needrestart
thanks
Patrick Matthäi dixit:
> Since this file also comes from rpm itself I think you agree this is not a bug
> in needrestart?
Not sure.
On one side, “rpm -qa” will create the directory in my home directory as
On Thu, 14 Apr 2022, Utkarsh Gupta wrote:
> The submitter has provided a debdiff, too:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=1008668;filename=tomcat9_9.0.58-1ubuntu1.debdiff;msg=5.
This will break other syslog implementations, though.
What is the problem with logrotate? It
Patrick Matthäi dixit:
> But how did it happened, that .rpmdb is owned by root in your own user
> directory?
rpm is installed, I run sudo apt-get something.
> Same in my test, if I use $ sudo needrestart => .rpmdb of ~root/ is used
Hmm.
Maybe !env_reset in sudoers would do this…
bye,
On Sun, 3 Apr 2022, Elliott Mitchell wrote:
> Perhaps the test should be: "[A-Z][A-Z]*[A-Z][A-Z]=*"?
No, that’s a shellglob, no BRE.
I think it’s best here to update the list with whatever findfs(8)
comes up when it does come up; anything else would require either
ksh extglobs or really
Hi Wolfgang,
> The issue is caused because pdftops creates a PostScript file which
> contains the whole drawing as a single bitmap image (don't know why).
Oh, ouch. So, bug in poppler after all?
>> $ pdf2ps test1.pdf test4-1.ps
>> $ ps2eps test4-1.ps
Hm, not just poppler? test4-1.ps has a
Dixi quod…
>Package: pstoedit
>Version: 3.78-1
>Followup-For: Bug #1008280
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008280
for the full story and reproducer.
With the help of http://www.calvina.de/pstoedit/pstoedit.htm#section_69
I may have found a workaround (which indicates a bug in
Package: pstoedit
Version: 3.78-1
Followup-For: Bug #1008280
X-Debbugs-Cc: t...@mirbsd.de
This is reproducible on sid.
It also occurs on buster, although with a different failure mode:
-BEGIN cutting here may damage your screen surface-
$ purifyeps test1-a.eps test1-b.eps
pstoedit:
Package: libphp-jpgraph
Version: 1.5.2-13.1
Followup-For: Bug #631280
Control: severity -1 serious
It’s not just that:
PHP Deprecated: Methods with the same name as their class will not be
constructors in a future version of PHP; LinePlot has a deprecated constructor
in
Package: needrestart
Version: 3.5-4
Severity: grave
Justification: causes non-serious data loss
X-Debbugs-Cc: t...@mirbsd.de
I did notice root-owned .rpmdb directories in my user home and,
after log inspection, was able to track it down to apt-get runs.
Some reproducing and grepping later I
Package: python3-debianbts
Version: 3.1.0
Followup-For: Bug #949210
X-Debbugs-Cc: t...@mirbsd.de
Huh, this bug made it into a release. And Policy is very weird about
this: the MUST in §12.7 doesn’t apply, because this is a native package,
but this file is not used as both Debian and upstream
Package: dkms
Version: 2.6.1-4
Severity: important
When DKMS is successful, we see output like this:
-BEGIN cutting here may damage your screen surface-
Preparing to unpack .../iproute2-dbgsym_5.10.0-4~jens+6_amd64.deb ...
Unpacking iproute2-dbgsym (5.10.0-4~jens+6) over
Package: linux-headers-5.17.0-rc8-common
Version: 5.17~rc8-1~exp1
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
Trying to build a kernel module against 5.17 shows several warnings:
W: /bin/sh: /usr/src/linux-headers-5.17.0-rc8-common/scripts/pahole-flags.sh:
inaccessible or not found
According
Hi,
this bug still exists.
bye,
//mirabilos
--
15:41⎜ Somebody write a testsuite for helloworld :-)
Package: pstoedit
Version: 3.75-1
Severity: serious
Justification: unusable by some users
X-Debbugs-Cc: t...@mirbsd.de, hill...@web.de, debian-tex-ma...@lists.debian.org
Control: affects -1 purifyeps
I’ve noticed purifyeps (which is needed for Tₑχ/LᴬTᴇΧ to process .eps files)
fails on some inputs
On Wed, 23 Mar 2022, Emmanuel Bourg wrote:
> I vaguely remember that replacing a symlink with a file during a package
> update was causing some issues (i.e. the target is updated but the symlink
Wasn’t that only for directories?
bye,
//mirabilos
--
Infrastrukturexperte • tarent solutions GmbH
retitle 787511 libpython3.9-stdlib: double embarassing failure in RFC2047 eMail
header encoding
found 787511 3.9.10-2
tags 787511 + bookworm sid
thanks
The bug’s also still pertinent in bullseye, see previous message,
as well as sid:
(sid-amd64)tglase@tglase:~ $ python3 x.py3
pöstal foo bar
Hi,
I also get this warning… on a system that DOES NOT EVEN HAVE os-prober
INSTALLED IN THE FIRST PLACE.
This is *highly* misleading and irritating.
bye,
//mirabilos
--
Gestern Nacht ist mein IRC-Netzwerk explodiert. Ich hatte nicht damit
gerechnet, darum bin ich blutverschmiert… wer konnte
Hi Laurent,
> Thorsten do you think you could have a look?
sorry, I have absolutely no spoons left for that, what with
sid now requiring systemd’s idea of a filesystem layout,
which led to me leaving Debian-Ports entirely, and other
current discussions.
bye,
//mirabilos
--
"Using Lynx is
found 870787 4.2-build2017-2
thanks
Hi,
anything ever going to happen on this front? This is
hindering multiple packages on kFreeBSD and Hurd ☹
Sad seeing Xes in buildd status on DDPO,
//mirabilos
--
If Harry Potter gets a splitting headache in his scar
when he’s near Tom Riddle (aka
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm
X-Debbugs-Cc: t...@mirbsd.de
Please consider removing minify-maven-plugin from both buster and bullseye:
minify-maven-plugin is currently only in Debian to satisfy a Build-Depends
of
401 - 500 of 4557 matches
Mail list logo
