Package: libc-bin
Version: 2.31-10
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
I’m debugging a weird lintian problem and found the cause to be:
tglase@tglase-nb:~ $ ldd /tmp/libjsound.so
statically linked
tglase@tglase-nb:~ $ file /tmp/libjsound.so
/tmp/libjsound.so: ELF 64-bit LSB
Dixi quod…
>I imagine *many* other third-party addons do the same. Please
>make git search the old location after the new one (preferred)
Uhm, ping?
Package: git
Version: 1:2.31.0-1
Severity: important
X-Debbugs-Cc: t...@mirbsd.de
git (1:2.31.0-1) unstable; urgency=low
* install dashed commands to /usr/libexec instead of /usr/lib (thx
Chris Lamb for suggesting it through lintian).
While this is laudable, some commands now fail:
Adam D. Barratt dixit:
>Please go ahead.
Thanks, I’ve done so.
bye,
//mirabilos
Utkarsh Gupta dixit:
>Thanks to Thomas for his help, I've uploaded a fix for this regression
>(by reverting the backport of that part of the patch which was not
>necessary
It’s got some memory impact, but probably neglegible here, true.
> for this CVE fix). And thanks to Thorsten for his
Dixi quod…
>[ Other info ]
>I have another set of uploads for musescore2 and musescore3 fixing
>crash bugs coming up (not uploading them today, I want upstream to
>have a go at reviewing the change first). How should this be handled?
>Should I first wait until the current set of packages is
Hi Julien,
>Yes, they're different. I'm not sure what you're asking.
the reason for the difference; sorry if I was unclear.
Thanks,
//mirabilos
--
18:47⎜ well channels… you see, I see everything in the
same window anyway 18:48⎜ i know, you have some kind of
telnet with automatic pong
Hi Fabian,
>Am Sonntag, dem 14.03.2021 um 20:05 + schrieb Thorsten Glaser:
>> @Fabian since you were the driving force behind SF3 integration
>> into FluidSynth itself, you might wish to have a look at the
>> patch as well.
>
>forwarded to Fluidsynth upstream, th
error in prerm (Closes: #984592)
+ * Update from maintainer script template
+ * Do latest lintian tag rename churn
+
+ -- Thorsten Glaser Fri, 12 Mar 2021 20:58:58 +0100
+
musescore-general-soundfont (0.2-2) unstable; urgency=high
* Merge musescore-general-soundfont-small (0.2-2) changes
forwarded 985129 https://github.com/musescore/MuseScore/pull/7728
tags 985129 - moreinfo
tags 985129 + confirmed upstream pending
affects 985129 musescore
outlook 985129 a patch has been found and musescore{2,3} will be uploaded soon
thanks
@Fabian since you were the driving force behind SF3
@Igor, Jojo: this relates to commit 5aea0ab5b50b9037ba8ed9dd100dcf06396a4c9d
and the follow-up commit 48163e958f02b82e59d910176c5d806d0c9ef7b6 and to
https://musescore.org/en/node/89216 (see my comments there), I will of course
provide a PR if I manage to fix this correctly.
Dixi quod…
>> (gdb)
Hi Paul,
>> slowness), but, while Valgrind is very unhappy with both the X libraries
>> and MuseScore, showing *many*
>> Conditional jump or move depends on uninitialised value(s)
> Are there any suppression files, one could use?
I’ve got no idea, I barely know Valgrind.
>> 1816
Hi,
I have a patch also concerned with ÿ characters being output.
Is this the same issue? If so, someone (upstream) should check
which is more correct; mine doesn’t “simply move an assignment”.
Thanks,
//mirabilos who definitely should forward his other screen bugfixes…
--
18:47⎜ well channels…
Hi,
the changelogs seem to differ in re-added certificates:
ca-certificates (20210119) unstable; urgency=medium
[ Michael Shuler ]
* mozilla/blacklist:
Revert Symantec CA blacklist (#911289). Closes: #962596
The following root certificates were added back (+):
+ "GeoTrust
tags 985129 + unreproducible moreinfo
thanks
(Don’t let this scare you, let’s see whether we can get to the bottom…)
Hi Paul,
> Today *musescore-general-soundfont* was upgraded, and opening a file in
> MuseScore 3, and changing the sound font of a voice/part to *Oboe* MuseScore 3
> crashed with
retitle 929983 ipxe-qemu: virtio booting broken past jessie
notfound 929983 1.0.0+git-20141004.86285d1-1
notfound 929983 1.0.0+git-20150424.a25a16d-1
found 929983 1.0.0+git-20161027.b991c67-1
found 929983 1.0.0+git-20190125.36a4c85-5.1
thanks
On Fri, 26 Feb 2021, Thorsten Glaser wrote
Dixi quod…
>I noticed that multimedia-musiciantools Recommends: musescore
>
>It should instead
> Recommends: musescore3
> Suggests: musescore
>for bullseye.
multimedia-guitar=0.10 (built from the same source package)
Suggests musescore; it probably should Suggests musescore3
instead thus.
bye,
Package: multimedia-musiciantools
Version: 0.10
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
I noticed that multimedia-musiciantools Recommends: musescore
It should instead
Recommends: musescore3
Suggests: musescore
for bullseye.
Rationale: musescore3 is the recent version of MuseScore and
Package: shellcheck
Version: 0.7.1-1
Severity: important
X-Debbugs-Cc: t...@mirbsd.de
$ shellcheck –list-optional
–list-optional: –list-optional: openBinaryFile: does not exist (No such file or
directory)
This was copy/paste from the manual page:
–list-optional
Output a
Package: curl
Version: 7.64.0-4+deb10u1
Severity: important
This is a buster-only (AFAICT) bug: stretch (7.52.1-5+deb9u13)
doesn’t yet have the problem, and sid (7.74.0-1.1) works.
In a default buster installation /etc/ssl/openssl.cnf ends with
these fateful lines:
[system_default_sect]
Sven Joachim dixit:
>I see that this might be a problem (albeit unlikely to happen in
>practice), however I have trouble understanding exactly where a
>use-after-realloc bug comes into play. Maybe Thorsten can help me fix
>my blindness?
The next time something is selected, the code a little
Source: xterm
Version: 327-2+deb9u1
Severity: serious
Justification: introduces use-after-realloc
debian/patches/CVE-2021-27135.patch changes button.c line (after
patching) 3747 to:
line = realloc(line, screen->selection_size);
But “line” is a local variable, the address of the buffer
Andreas Beckmann dixit:
> Which is another point for *shipping* the directories to let dpkg do the
> refcounting, otherwise the manually created directory gets removed by dpkg
> removing a different package.
Hmh, good point.
> On 05/03/2021 16.17, Thorsten Glaser wrote:
>>&g
Andreas Beckmann dixit:
>during a test with piuparts I noticed your package fails to remove.
According to https://piuparts.debian.org/sid-strict/source/m/musescore2.html
the musescore-common package succeeds piuparts, too… huh… weird.
Fixing it at the moment,
//mirabilos
Andreas Beckmann dixit:
> Removing musescore-common (2.3.2+dfsg4-12) ...
> rmdir: failed to remove '/usr/share/sounds/sf2': No such file or directory
> dpkg: error processing package musescore-common (--remove):
> installed musescore-common package pre-removal script subprocess returned
>
Andreas Beckmann dixit:
>during a test with piuparts I noticed your package fails to remove.
>
>>From the attached log (scroll to the bottom...):
>
> Removing musescore-common (2.3.2+dfsg4-12) ...
> rmdir: failed to remove '/usr/share/sounds/sf2': No such file or directory
> dpkg: error
Evgeni Golov dixit:
>>>, exactly because neither the old nor the new configuration is in a
>>>state where it's supposed to work out of the box.
>>
>>But why? The pre-YAML thing *did* work out of the box, very finely
>>so, and I only changed the config one hot summer to have a little
>>more quiet.
Evgeni Golov dixit:
>>… without that it’ll also fail, which means it’ll fail package
>>installation, which is a serious (RC) bug.
>
>No, the daemon is not started on install
Did that change recently? Because when I reported this bug first
it was precisely because it was started on install…
>,
Evgeni Golov dixit:
>> No, this is about the *vanilla* config shipped by the package.
>> It used to work (my adjustment later was only regarding the levels
>> of temperature as I’ve got an SSD, not HDD, so it can become a bit
>> higher for quietness) and now the package doesn’t work at all.
>
Evgeni Golov dixit:
>> tglase@tglase-nb:~ $ sudo cleanenv / /etc/init.d/thinkfan start
>> Starting fan control tool: thinkfan
>> ERROR: Error scanning
>> /sys/devices/pci:00/:00:03.1/:27:00.0/hwmon: No such file or
>> directory
>> failed!
>
>-3 has a NEWS.Debian explaining the
With
cgroup_controllers = []
in /etc/libvirt/qemu.conf I could get it back to working
for the 6.9.0-4 version though. That didn’t (seem to) work
with 7.0.0-2 earlier… :/
bye,
//mirabilos
--
Infrastrukturexperte • tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn •
Package: libvirt-daemon
Version: 6.9.0-4
Followup-For: Bug #983871
X-Debbugs-Cc: t...@mirbsd.de
Ouch, after a reboot this stopped working again!
-- System Information:
Debian Release: bullseye/sid
APT prefers unreleased
APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500,
Package: thinkfan
Version: 1.2.1-3
Followup-For: Bug #981699
X-Debbugs-Cc: t...@mirbsd.de
Control: reopen 981699
Control: severity 981699 serious
Unfortunately, thinkfan still fails to work:
tglase@tglase-nb:~ $ sudo cleanenv / /etc/init.d/thinkfan stop
Stopping fan control tool: thinkfan.
Package: xrdp
Version: 0.9.15-1
Severity: minor
X-Debbugs-Cc: t...@mirbsd.de
$ sudo cleanenv / /etc/init.d/xrdp start
Starting Remote Desktop Protocol server: xrdp-sesmanlogging configuration:
LogFile: /var/log/xrdp-sesman.log
LogLevel: [INFO ]
ConsoleLevel:
notfound 983871 6.9.0-4
thanks
> Package: libvirt-daemon
> Version: 7.0.0-2
> After an upgrade+reboot I cannot start VMs *again* with some cgroup error:
Downgrading the entire bunch of involved packages fixes this:
tglase@tglase:~/a $ sudo apt-get install $PWD/*.deb
Reading package lists...
Dixi quod…
> After an upgrade+reboot I cannot start VMs *again* with some cgroup error:
>
> $ wirrsh start Netboot
>
> error: Failed to start domain 'Netboot'
> error: internal error: failed to get cgroup backend for
Package: libvirt-daemon
Version: 7.0.0-2
Severity: important
X-Debbugs-Cc: t...@mirbsd.de
After an upgrade+reboot I cannot start VMs *again* with some cgroup error:
$ wirrsh start Netboot
error: Failed to start domain
Package: manpages-dev
Version: 5.10-1
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
Besides those few found in the glibc-doc package (which probably should
just be taken over, given that that package really consists of only a
number of pthread manpages and… imperial tons of changelogs?!), there
maximilian attems dixit:
>are there other dangling symlinks besides this three mentioned ones?
adequate reported only these three for this package; you can find
dangling symlinks, generally, with: (thanks XTaran)
find -L . -type l -ls
bye,
//mirabilos
--
FWIW, I'm quite impressed with
Package: firmware-misc-nonfree
Version: 20210208-2
Severity: normal
User: debian...@lists.debian.org
Usertags: adequate broken-symlink
X-Debbugs-Cc: t...@mirbsd.de
firmware-misc-nonfree: broken-symlink /lib/firmware/cxgb4/t4-config.txt ->
configs/t4-config-default.txt
firmware-misc-nonfree:
Package: qdbus
Version: 4:5.15.2-4
Severity: serious
Justification: unupgradable
The new qdbus arch:all package is no longer Multi-Arch:foreign,
making it uninstallable on, for example, an amd64 system which
has an i386 package with Depends: qdbus installed.
Given qdbus 4:4.8.7+dfsg-20
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
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,
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
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.
>
>
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
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
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
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,
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
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
+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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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,
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
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.
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
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
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
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
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
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
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
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
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
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
=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:
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:
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'),
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
701 - 800 of 4557 matches
Mail list logo
