Dixi quod…
>Downgrading *only* the package ipxe-qemu to 1.0.0+git-20161027.b991c67-1
(the version in stretch)
>on that very sid system…
>
>… doesn’t make this succeed either. Huh.
Downgrading seabios along (need to remove -nographic to make that work)
also doesn’t yield netboot success, so there’
Package: ipxe-qemu
Version: 1.0.0+git-20190125.36a4c85-5.1
Followup-For: Bug #929983
X-Debbugs-Cc: t...@mirbsd.de
This is also broken on an up-to-date-enough sid system.
$ qemu-system-x86_64 -device virtio-net-pci,netdev=net0 -netdev user,id=net0
-nographic
boots.
$ qemu-system-x86_64 -device
reassign 706676 lxc
# don't set these; they are used by the release team, and the PTS
# uses version tracking, for which it also doesn't need the tags
tags 706676 - bullseye sid
# the submitted patch is not acceptable, it would break other
# packages, see below
tags 706676 - patch
thanks
On Fri, 2
Marc Haber dixit:
>> whereas sudo reads the
>> tty from it, making it fail in chroots using qemu-user-static.
>
>How exactly does sudo fail? Is this worth reporting upstream?
Basically sudo does not ask for the password because it cannot
find its tty. I’ve mailed to the bugreport with you in X-De
s dixit:
>On Tue, Sep 17, 2019 at 12:33:26AM +0200, Thorsten Glaser wrote:
>> linux-user/syscall.c:open_self_stat() fills the emulated
>> /proc/self/stat with a lot of 0s,
>
>So the contents of /proc/self/stat has the correct number of fields, but
>all zeroes?
chroot$ /bin/cat
On Thu, 18 Feb 2021, Salvatore Bonaccorso wrote:
> On Thu, Feb 11, 2021 at 08:33:58AM +0100, Sebastien Delafond wrote:
> > The recently applied patch still creates the file with the default
> > umask[0], before chmod'ing down to 0600, so an attacker could still open
> > it in the meantime.
>
> FTR
Dmitry Smirnov dixit:
>The relevant upstream bug is this:
>
> https://midnight-commander.org/ticket/4180
>
>Looks like it will be trivial to cherry-pick the patch for Bullseye.
https://github.com/MidnightCommander/mc/commit/a75071b3c07d7dc2795ad2c321e1e340eceadb24.patch
It’s not just that eithe
Dmitry Smirnov dixit:
>The relevant upstream bug is this:
>
> https://midnight-commander.org/ticket/4180
>
>Looks like it will be trivial to cherry-pick the patch for Bullseye.
Doesn’t seem so.
https://github.com/MidnightCommander/mc/commit/ec1938db8ef8171440e1a56aea94feec59d23f71.patch
seems t
Package: chai
Version: 4.2.0+ds+~4.2.14-2
Severity: serious
Justification: Policy 2.3
User: debian...@lists.debian.org
Usertags: adequate broken-symlink missing-copyright-file
X-Debbugs-Cc: t...@mirbsd.de
chai: broken-symlink /usr/share/doc/chai -> libjs-chai
chai: broken-symlink /usr/share/nodejs
reopen 970460
found 970460 1:5.2+dfsg-5
thanks
Hi again,
unfortunately, this seems to be not fixed, but I can’t figure out why.
When I call the -binfmt-P variant manually, everything works, and it
clearly uses its own argv[0], not /proc/self/exe, to determine what
to do, but when the kernel runs
Helge Deller dixit:
> For usage with buildd chroots, what will then be written to
> /proc/sys/fs/binfmt_misc/* ?
> Currently I see:
> interpreter /usr/bin/qemu-foo-static
> flags OCF
AIUI:
interpreter /usr/libexec/qemu-binfmt/foo-binfmt-P
flags OCFP
> With your idea,
Michael Tokarev dixit:
> 13.02.2021 13:19, Michael Tokarev wrote:
>>The problem with the wrapper is that it effectively nullifies
>>the F flag of binfmt. That is, with F and the binfmt interpreter
>>being the qemu binary directly, we can use regular, non-static,
>>qemu-user, or qemu-user-static, a
Hi Ondřej,
>I guess the small RSA keysize is causing the problem here generating
>invalid key.
oh, interesting. Right, with 512 it works.
Now… if I could recall what I was trying to test with this… ;-)
I should add notes what I was working on to bugreports…
>JFTR I had to specify path to workin
Dixi quod…
>built. Without the crash fix backporting polyphone makes
>no sense
I must correct myself here: polyphone is usable without
it *if* the user manually starts jackd first. (It will
still crash upon terminating, but that’s after saving
all data. I’m documenting this.)
>[ Tests ]
>No auto
+0100
+++ portaudio19-19.6.0/debian/changelog 2021-02-13 07:42:27.0 +0100
@@ -1,3 +1,9 @@
+portaudio19 (19.6.0-1+deb10u1) buster; urgency=medium
+
+ * Apply crash fix patch (Closes: #944509)
+
+ -- Thorsten Glaser Sat, 13 Feb 2021 07:42:27 +0100
+
portaudio19 (19.6.0-1) unstable; urgency
Package: devscripts
Version: 2.20.5
Severity: normal
File: /usr/bin/debdiff
X-Debbugs-Cc: t...@mirbsd.de
x=screen_4.8.0-5wtf1.dsc;
After doing…
TMPDIR=/var/tmp debdiff \
screen_4.8.0-5.dsc \
screen_4.8.0-5wtf1.dsc \
>screen_4.8.0-5wtf1.debdiff
… the created debdiff contains correct…
More on that test:
• Restoring /etc/mc/mc.ext from mc_4.8.25-1 (by copying
it to ~/.config/mc/mc.ext) does NOT fix the bug.
(Deleted it again for the next test.)
• Running /tmp/mc_4.8.25-1_x32-extracted/d/usr/bin/mc
*does* fix the issue, so it must be something compiled
into the mc binary
Package: mc
Version: 3:4.8.26-1
Followup-For: Bug #981711
X-Debbugs-Cc: t...@mirbsd.de
Control: severity -1 important
I just did an a/b test on a sid system I had not yet upgraded.
The versions of relevant packages before the upgrade:
tglase@tglase:~ $ dpkg-query -W mc\*
mc 3:4.8.25-1
mc-da
Hi Paul,
> FTBFS) but it avoids busywork for maintainers that are not involved in
> bootstrapping java. Machine time is cheap, volunteer time is not.
this is not for bootstrapping. This is to prevent building of language
bindings for e.g. Java on platforms where there is simply no Java.
This is a
Package: adequate
Version: 0.15.4
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
performous-composer: incompatible-licenses /usr/games/performous-composer
GPLv2+ + OpenSSL (libssl.so.1.1)
This is now permitted in Debian, as OpenSSL is now a System Library
(like in the BSDs).
-- System Informatio
Hi Faidon,
>I didn't make lowdown the default, because there is an outstanding bug
>specifically affecting libmaxminddb, for which I'm waiting for a new
>lowdown release to fix.
ouch, okay.
>It will become the default eventually, but I wanted to offer it as an
>alternative among a few other chan
reopen 956041
found 956041 1.5.0-2
thanks
Debian FTP Masters dixit:
> - Add lowdown as an alternative Markdown translator to be used instead of
> pandoc, to ease bootstrappability for new ports. (Closes: #956041)
Unfortunately not:
| Dependency installability problem for [145]libmaxmi
brian m. carlson dixit:
>Yeah, I'm aware of how to change it, but it ends up being a problem
>because it doesn't persist across files. Therefore, it needs to be
>changed again for every file.
Define “every file”. If you load scores made by others, you will
_of course_ get the paper size they set
brian m. carlson dixit:
>Moreover, immediately
>after setting it to Letter and printing, attempting to print again makes
>it go right back to A4, so it doesn't remember my settings, unlike every
>other program.
I think I *might* be able to help with this part of the report, though.
The paper siz
Package: alpine
Version: 2.24+dfsg1-1
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
Another regression against pine 4.64L:
In my .pinerc in pine I have:
customized-hdrs=[…],
Content-Language: "de-DE-1901, en-GB",
[…]
In pine, this leads to outgoing eMails containing the header…
This also occurs when starting/stopping it manually.
tglase@tglase-nb:~ $ sudo cleanenv / /etc/init.d/thinkfan stop
Stopping fan control tool: thinkfan.
tglase@tglase-nb:~ $ sudo cleanenv / /etc/init.d/thinkfan start
Starting fan control tool: thinkfan
ERROR: Error scanning /sys/devices/pci:00
Hello Dmitry,
thanks for the quick response!
>On Wednesday, 3 February 2021 1:16:18 PM AEDT Thorsten Glaser wrote:
>> Regression in sid: after an update, I cannot F3 on .jar files any more:
>
>Upstream advised to synchronize your local "~/.config/mc/mc.ext" with
>
Hi Evgeni,
>> thinkfan: obsolete-conffile /etc/thinkfan.conf
>
>No, it's not. According to your dpkg output your config was modified,
>and dpkg/debhelper doesn't remove modified configs.
Ah, point. Then, adequate output could use a distinguishing mark.
I’ll take that there, thanks.
>The config f
Package: adequate
Version: 0.15.3
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
Adequate reports obsolete-conffile if a package no longer ships a
conffile, but there are two cases to distinguish:
• the package’s buggy and didn’t clean up
• dpkg didn’t remove the conffile because it was locally ch
Dixi quod…
>Regression in sid: after an update, I cannot F3 on .jar files any more:
[…]
>I cannot Enter them any more either.
Copying it to x.zip allows all these things to work,
so the file extension must be misdetected.
From the extension file, it looks like mc parses file(1) output.
Maybe the
Package: mc
Version: 3:4.8.26-1
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
Regression in sid: after an update, I cannot F3 on .jar files any more:
║*ru ╔═══ Error
═══╗ :07║
║║
Package: thinkfan
Version: 1.2.1-2
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
$ sudo apt-get --purge dist-upgrade
[…]
Preparing to unpack .../thinkfan_1.2.1-2_amd64.deb ...
Unpacking thinkfan (1.2.1-2) over (1.2.1-1) ...
dpkg: warning: unable to delete old directory
'/etc/systemd/system/thinkf
Package: thinkfan
Version: 1.2.1-2
Followup-For: Bug #981251
X-Debbugs-Cc: t...@mirbsd.de
This bug is still pertinent:
thinkfan: obsolete-conffile /etc/thinkfan.conf
Why is this file obsolete anyway?
/usr/share/doc/thinkfan/NEWS.Debian.gz does not list
anything and I have configured my thinkfan
Package: pristine-tar
Version: 1.49
Severity: wishlist
Tags: upstream
X-Debbugs-Cc: t...@mirbsd.de
I’ve got a very slow pristine-tar commit operation I could speed
up by telling pristine-tar that it was produced with, for example,
-Hustar -b1 --numeric-owner --owner=0 --group=0 --mode='u=rwX,go=rX
Hi Michael,
> Mmm. Is there a fix? If there is, I for one don't know it.
AIUI using a wrapper around the qemu binary that adds the
option (I would say which but the qemu-m68k-static manpage
documents qemu 0.9.0 and so doesn’t have it *cough*) to the
invocation, then change the binfmt-misc registr
block 976811 by 980567
thanks
On Sat, 12 Dec 2020, Ondřej Surý wrote:
> And let me restate that it’s not my intent to make anyone’s life hell and
> I am willing to help with any package (as usual). I am just trying to do
> the most sane thing to do security and maintainer wise.
You probably shou
Package: bridge-utils
Version: 1.6-5+b1
Severity: important
X-Debbugs-Cc: t...@mirbsd.de, n...@naturalnet.de
I’m shocked to read this in apt-listchanges so shortly before a release:
bridge-utils (1.6-4) unstable; urgency=low
Linux kernel has changed bridge MAC address selection.
In older Li
Package: qemu-user
Version: 1:5.2+dfsg-3
Followup-For: Bug #970460
X-Debbugs-Cc: t...@mirbsd.de
Hi, what’s the status on this? It is still broken in sid.
Could we please get the fix?
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-de
Package: bugs.debian.org
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
Reporting a bug against a binary package that only exists on d-ports
architectures (such as libgcc2 which is m68k-specific) fails, the
report gets assigned to unknown-pack...@qa.debian.org instead of GCC.
I could understand if
Package: libgcc-s2
Version: 10.2.1-6
On upgrading an older (1 year or so) sid installation, I get this:
Preparing to unpack .../libgcc-s2_10.2.1-6_m68k.deb ...
Unpacking libgcc-s2:m68k (10.2.1-6) ...
dpkg: error processing archive
/var/cache/apt/archives/libgcc-s2_10.2.1-6_m68k.deb (--unpack):
Dixi quod…
>Hans-Christoph Steiner dixit:
>
>> I would accept a
>> merge request on salsa for this, if it passes in gitlab-ci.
>
>It’s a one-liner that changes package metadata only, so it’s
OK, it became three lines because the other two arch:all
packages also qualify for M-A:foreign.
https://s
Hans-Christoph Steiner dixit:
> Right now, we can only commit to supporting the arches that upstream supports
> (amd64 and arm64), so I'm downgrading the severity.
It’d be the same if you’d install either of these, it’s *not*
an architecture-specific problem.
> I could never wrap my head around
Package: android-sdk-platform-tools-common
Version: 28.0.2+2
Severity: serious
Justification: might not be as severe but fails a release goal
X-Debbugs-Cc: t...@mirbsd.de
I cannot upgrade adb:i386 on my x32 system because adb:i386
Depends android-sdk-platform-tools-common, however, because
android
Package: fwupd
Version: 1.5.5-2
Severity: normal
User: debian...@lists.debian.org
Usertags: adequate obsolete-conffile
X-Debbugs-Cc: t...@mirbsd.de
adequate reports:
fwupd: obsolete-conffile /etc/fwupd/ata.conf
Is this file really to be removed or is there a bug in the package
that it’s not ship
Package: lintian
Version: 2.104.0
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
The renaming of unknown-field-in-dsc and unknown-field-in-control
to unknown-field makes it not meaningfully overridable. We now get:
W: logind-considered-harmful: unknown-field
logind-considered-harmful_73_all.deb I
Package: mesa-vulkan-drivers
Version: 20.3.2-1
Severity: important
X-Debbugs-Cc: t...@mirbsd.de
Package: mesa-vulkan-drivers
[…]
Multi-Arch: same
The file /usr/share/vulkan/icd.d/intel_icd.x86_64.json differs.
amd64:
{
"ICD": {
"api_version": "1.2.145",
"library_path": "/
tags 979636 - unreproducible
thanks
Elimar Riesebieter dixit:
>I can quit alsamixer on two different ways:
>
>Hitting once or
Hitting Esc once does not do anything.
Oh wait, after… *retries and counts* hm no.
This is fun. I run alsamixer under GNU screen, and
it is gone if I press Esc then sw
Package: alsa-utils
Version: 1.2.4-1
Severity: minor
Tags: upstream
X-Debbugs-Cc: t...@mirbsd.de
alsamixer is terminated, according to its manual page, by
pressing Esc then pressing q (the manpage writes this as
Alt-q but there is no such thing as an Alt key on Unix).
alsamixer will also terminat
Hi Faidon,
> generating libmaxminddb's manpages with lowdown should be possible. I
> also pushed the lowdown package to NEW, so hopefully by the time that
> reaches the archive, I'll be able to push an even newer upstream that
> can be used by libmaxminddb.
good idea!
> You may be delighted to h
Package: iogerman
Version: 1:2-37
Severity: important
X-Debbugs-Cc: t...@mirbsd.de
During an upgrade:
[…]
Processing triggers for dictionaries-common (1.28.3) ...
ispell-autobuildhash: Processing 'british' dict.
ispell-autobuildhash: Processing 'ogerman' dict.
/usr/lib/ispell/ogerman.aff line 242
Package: dpkg
Version: 1.20.6
Severity: wishlist
X-Debbugs-Cc: t...@mirbsd.de
TIL (via apt-listchanges) that dpkg-realpath(1) exists.
I went on to reading its manual page.
It documents the options, sure, but… some words about
why it exists, when one would choose it over realpath(1)
or readlink(1)
Package: youtube-dl
Version: 2020.11.29-1
Severity: normal
Tags: fixed-upstream
X-Debbugs-Cc: t...@mirbsd.de
youtube-dl fails to find youtube automatic captions;
the upstream binary 2021.01.03 succeeds, so an update
will most likely fix this.
-- System Information:
Debian Release: bullseye/sid
Package: cups-filters
Version: 1.28.6-1
Followup-For: Bug #975578
X-Debbugs-Cc: t...@mirbsd.de
Jan 4 18:42:09 tglase vmunix: [15803628.091735] cups-browsed[7855]: segfault
at 0 ip f7b2f354 sp ffe47140 error 6 in
libcupsfilters.so.1.0.0[f7b13000+24000]
Jan 4 18:42:09 tglase vmun
Package: jackd2
Version: 1.9.16~dfsg-1
Severity: minor
X-Debbugs-Cc: t...@mirbsd.de
From the following information in the MuseScore fora…
> beatboxchad • Oct 17, 2020 - 20:52
>
>| In reply to Sorry - I thought the linked… by willy3
>
>> JACK does MIDI routing, but it doesn't implement a lot of li
=high
+
+ * Non-maintainer upload.
+ * Add upstream patch fixing a severe regression (Closes: #976895)
+
+ -- Thorsten Glaser Wed, 30 Dec 2020 14:14:11 +0100
+
alsa-lib (1.2.4-1) unstable; urgency=medium
* New upstream release.
diff -Nru alsa-lib-1.2.4/debian/patches/976895.diff
alsa-lib
Package: libjs-jquery
Version: 3.5.1+dfsg+~3.5.5-3
Followup-For: Bug #977960
X-Debbugs-Cc: t...@mirbsd.de
Even for the latest versions of these packages, adequate reports:
node-jquery: broken-symlink /usr/share/nodejs/jquery/dist/jquery.js ->
../../nodejs/jquery/dist/jquery.js
node-jquery: broke
Package: node-jquery
Version: 3.5.1+dfsg+~3.5.5-3
Followup-For: Bug #977960
X-Debbugs-Cc: t...@mirbsd.de
Even for the latest versions of these packages, adequate reports:
node-jquery: broken-symlink /usr/share/nodejs/jquery/dist/jquery.js ->
../../nodejs/jquery/dist/jquery.js
node-jquery: broken
Package: manpages-dev
Version: 5.10-1
Followup-For: Bug #973885
X-Debbugs-Cc: t...@mirbsd.de
This bug still exists.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'oldstable-updates'), (500,
'buildd-unstable'), (500,
Dixi quod…
>The values I get are:
>
>Array
>(
>[bbox] => Array
>(
>[0] => 1
>[1] => 0
>[2] => 185
>[3] => 0
>[4] => 185
>[5] => -11
>[6] => 1
>[7] => -11
>)
>
>[ascender] => 11
>
Package: php7.4-gd
Version: 7.4.11-1
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
I’m running the following script:
php -r '
$text = "2020-12-23T13:25:44Z";
$font = "Inconsolatazi4varl_qu-Regular.otf";// attached
$fontsize = 14;
$bbox = imageftbbox($fontsize,
On Wed, 23 Dec 2020, Andrius Merkys wrote:
> false-positives. Even dh_auto_configure appears to be used legitimately
dh_auto_configure is the one I’d expect to be used (with autotools).
dh_auto_build is the one that raises red flags, and for *some*
buildsystems dh_auto_test invokes a make/maven/
Matthias Klose dixit:
>> If you wish I can also update my packaging and upload this.
>> Should be quick enough…
>
>thanks, that would be appreciated.
OK, will put it on the short-term TODO then.
Do you wish to be added to Uploaders?
bye,
//mirabilos
--
"Using Lynx is like wearing a really go
Matthias Klose dixit:
[ #686777 ]
>so this bug discussion started in 2013, and stopped in 2016. Do you
>really think that this will pick up again?
Given how the last opus update happened (as an NMU), no.
But since multiple packages need this, maybe salvaging could
apply. The questions raised wrt
Hi Matthias,
>this is an ITP which didn't see any progress for the past eight months.
yes, sorry about that… I found some issues with it back then,
but don’t remember precisely which ones now. Could’ve been
network, not code-related.
Ah: #686777 blocks removal of the embedded libopus in favour
o
+0100
@@ -1,3 +1,10 @@
+alsa-lib (1.2.4-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Revert an upstream commit breaking applications (Closes: #976895)
+
+ -- Thorsten Glaser Tue, 22 Dec 2020 02:20:29 +0100
+
alsa-lib (1.2.4-1) unstable; urgency=medium
* New upstream
affects 976895 musescore
affects 976895 musescore3
thanks
Thorsten Glaser dixit:
>Hello maintainers,
>
>>The latest libasound2 introduced a severe regression:
>
>ping?
ping again, after another week… *any* response would have been
welcome, more than being ignored…
>This b
Picca Frédéric-Emmanuel dixit:
>thanks for considering
Not before bullseye. There are many regressions and problems
with the new releases. I plan on doing (at least) one more
upload with more individual fixes backported, though ☺
My current plan is to package 3.6.x after bullseye, providing
them
On Mon, 21 Dec 2020, Tom H wrote:
> >> But you want to disable an init script, start it manually, change
> >
> > (or start the daemon manually without that init script)
>
> That's irrelevant:
No, it’s not.
As I already wrote, start-stop-daemon can do more for
daemons running under different use
On Mon, 21 Dec 2020, Tom H wrote:
> > It means “do not call this init script in any runlevel”,
> > which *ought* to be very obvious.
>
> "do not call this init script in any runlevel" can be understood as
> "kill it in any runlevel".
No, absolutely not, NO, NO, *NO*. *GAH!*
> But you want to di
Thomas Dickey dixit:
>I'm guessing that it's timing, e.g., xterm could wait a few milliseconds
>to retry and then give up on that loop, in case the window events don't
>arrive rapidly enough.
“rapidly enough” as criterium isn’t going to help everyone.
We have multi-GHz desktop bolides, few-MHz m
On Sun, 20 Dec 2020, Ian Jackson wrote:
> Thorsten Glaser writes ("Bug#975591: update-rc.d disable"):
> > On Sun, 20 Dec 2020, Tom H wrote:
> > > It depends what's meant by "disable".
> >
> > Which part of “disable an init script” did you not
On Sun, 20 Dec 2020, Tom H wrote:
> > There *absolutely* HAS to be some way to disable an init script
> It depends what's meant by "disable".
Which part of “disable an init script” did you not understand?
> If it means "disable from starting at boot", then
No.
> If it means "disable from st
Thomas Dickey dixit:
>how far below?
>
>Just the window-decoration, or a line or so?
About a line, give or take (for the syslog window, the last line
is the cursor, so I don’t need it, and I took a bit more than a
line there; for that test, it’s a bit less).
>Looking at the changes for #361, the
On Sun, 20 Dec 2020, Thorsten Glaser wrote:
> corruption effects which vary (see screenshot).
Oops, attached.
Thomas Dickey dixit:
>I see that version in testing, but don't see a problem on the screen.
>I made a short script to cat those lines to the terminal, sleeping 0.2
>seconds between bursts, and the result looks ok, even with a magnifier.
Indeed, tricky. I experimented with this a bit.
I can repro
On Mon, 14 Dec 2020, Cristian Ionescu-Idbohrn wrote:
> > It doesn't depend on the init, but it links against the library to
> > parse the journal files,
>
> I have no journal files on my system (yet). So, that dependency is
> total nonsense to me.
Not on your system but in the packet stream it a
On Mon, 14 Dec 2020, Bob Proulx wrote:
> Some time ago someone made an argument similar to this for conffiles.
> That if a conffile were removed that it was an intentional change.
> Even if accidental. And then things were changed so that if a
> conffile is removed then that is now considered a l
Hello maintainers,
>The latest libasound2 introduced a severe regression:
ping?
This bug makes MuseScore (2 and 3) on an ALSA-only system
completely unusable. To have this fixed before freezing
would be massively appreciated.
TIA,
//mirabilos
--
[16:04:33] bkix: "veni vidi violini"
[16:04:45]
# I am almost considering RC severity here
severity 975591 important
retitle 975591 insserv: no way to fully disable an init script
thanks
On Mon, 14 Dec 2020, Lorenzo wrote:
> with update-rc.d remove you are not disabling the service, you are
> purging it while it's still installed.
Okay, I can
On Wed, 25 Nov 2020, Bob Proulx wrote:
> Thorsten Glaser wrote:
> > So using disable is correct, defaults-disabled and remove isn't,
Right, I now figured out it isn’t.
> root@angst:/etc# find /etc/rc?.d/ -name '*bind9'
> /etc/rc0.d/K04bind9
> /et
Package: qemu-user-static
Version: 1:5.2+dfsg-2
Followup-For: Bug #977015
X-Debbugs-Cc: t...@mirbsd.de
Control: reopen -1
This bug is still pertinent:
qemu-user-static: broken-binfmt-interpreter qemu-ppc64abi32 =>
/usr/bin/qemu-ppc64abi32-static (No such file or directory)
$ ll /usr/bin/qemu*
-
Package: libasound2
Version: 1.2.4-1
Severity: important
X-Debbugs-Cc: t...@mirbsd.de, debian-multime...@lists.debian.org
Control: notfound -1 1.2.3.2-1+b1
The latest libasound2 introduced a severe regression:
Starting musescore3 and loading a score, e.g. like this…
$ musescore3 /usr/sh
On Tue, 8 Dec 2020, Maxim Chintalov wrote:
> I am attempting to install libgnome-desktop-3-dev, which has a
> dependency on libsystemd-dev, but it ended in APT error. Although
> libelogind0 provides libsystemd0, libelogind-dev is not providing
> libsystemd-dev.
I think this is by design; applicat
Martin-Éric Racine dixit:
>This could probably be merged:
No, it can’t. There is still discussion about how this is
to be started in the first place; from udev is what looks
like what we want, and until this is settled, I’m keeping
the current startup setup, as I don’t want to transition
it twice
Martin-Éric Racine dixit:
>Since systemd 247, there is a very loud dmesg about this:
Yes, but as things are much too complicated, this will not
be changed before the freeze any more.
Solutions for bookworm are welcome, though. I cannot test
them easily, I don’t use systemd.
bye,
//mirabilos
--
On Mon, 7 Dec 2020, Andrius Merkys wrote:
> In general, autopkgtests should not depend on build tools: compilers,
Not entirely true; sometimes, tests need to be built but hopefully
against the installed code, only compiling the tests themselves.
I’m not entirely sure about pointing that out as a
Package: alpine
Version: 2.24+dfsg1-1
Followup-For: Bug #923481
X-Debbugs-Cc: t...@mirbsd.de
This bug still persists. This caused loss of connection between
a mailing list thread and a debbugs entry. This is becoming
really annoying.
-- System Information:
Debian Release: bullseye/sid
APT pref
sed and that the rebuilt code
is the code being tested.
Perhaps specialists for other buildsystems could also be asked
whether theirs do that, and errors tagged for those.
On Sun, 6 Dec 2020, Paul Wise wrote:
> On Sat, Dec 5, 2020 at 6:45 PM Thorsten Glaser wrote:
>
> > We probably
Package: libutempter0
Version: 1.2.1-1
Severity: wishlist
X-Debbugs-Cc: t...@mirbsd.de
Ever since a recent upgrade I see the following messages in syslog
every time I open/close a new xterm or GNU screen tab:
Dec 4 17:29:15 tglase-nb utempter: utmp/wtmp record removed for terminal
'pts/18'
Dec
Package: texlive-latex-base-doc
Version: 2020.20201203-1
Severity: serious
Justification: does not install
X-Debbugs-Cc: t...@mirbsd.de
Preparing to unpack .../088-texlive-latex-base-doc_2020.20201203-1_all.deb ...
Unpacking texlive-latex-base-doc (2020.20201203-1) over (2020.20201129-2) ...
dpkg:
On Thu, 3 Dec 2020, tony mancill wrote:
> Given that the JVM bug can affect any application seems to tilt the
> scale towards proceeding with the JDK update, so the release of an
> upgrade path for Jenkins is a relief.
How about versioning it differently? Make it 11.0.9-2 for a while?
Convince up
Package: src:linux
Version: 5.9.9-1
Severity: critical
Justification: causes serious data loss
X-Debbugs-Cc:
t...@mirbsd.de,reply+aagshfu5klm2qb2dozdxppf5z5jydevbnhhcvex...@reply.github.com
A bit of backstory, since this is not the first place I had to
report this to (feels like being sent from P
Package: libasound2
Version: 1.2.3.2-1+b1
Followup-For: Bug #870396
X-Debbugs-Cc: t...@mirbsd.de
This is still pertinent.
-- System Information:
Debian Release: bullseye/sid
APT prefers unreleased
APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable'),
(100, 'experimen
Hi Thomas,
>If you're going to compile it, the debug-trace can be useful
>(--enable-trace). If not, the -report-fonts option is helpful.
I hadn’t recompiled, at least not with actual changes.
The -report-fonts output is attached, fNorm is the one
in question.
I did a little bisecting: Debian’s
Thomas Dickey dixit:
>"Recently" could be something overlooked in #362's change
No, 362 is the current one, and I definitely had this in
the previous version shipped in Debian as well, but I can’t
narrow it down further than that. According to apt history
log, that was 361.
>On the other hand (i
Package: xterm
Version: 362-1
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
I’ve got the following in my ~/.xinitrc…
/usr/bin/xterm +sb -fg black -geom 78x10+1+637 \
-bg slateblue -e top &
/usr/bin/xterm +sb -fg black -geom 90x11+475+637 \
-bg cornflowerblu
ebian/changelog acpi-1.7/debian/changelog
--- acpi-1.7/debian/changelog
+++ acpi-1.7/debian/changelog
@@ -1,3 +1,10 @@
+acpi (1.7-1.2) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Display estimated end time for {,dis}charging, too
+
+ -- Thorsten Glaser Wed, 25 Nov 2020 02:24:31
Package: mlocate
Version: 0.26-4
Severity: normal
User: debian...@lists.debian.org
Usertags: adequate obsolete-conffile
X-Debbugs-Cc: t...@mirbsd.de
After today’s upgrade, adequate warns about:
mlocate: obsolete-conffile /etc/updatedb.conf
And, indeed, mlocate_0.26-4_amd64.deb no longer ships th
On Mon, 23 Nov 2020, Jesse Smith wrote:
> I'm the upstream insserv maintainer. The insserv program already has a
This is probably for http://bugs.debian.org/975591 then.
> flag for disabling warnings like the ones you are seeing. The "-q" or
> "--silent" flag should prevent the warnings about ru
Package: insserv
Version: 1.21.0-1
Severity: wishlist
X-Debbugs-Cc: t...@mirbsd.de, pkg-systemd-maintain...@lists.alioth.debian.org
Cc’ing init-system-helpers maintainer address, as
parts of this probably affect it as well.
From a discussion on debian-init-diversity, using…
sudo /usr/sbi
801 - 900 of 4616 matches
Mail list logo
