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
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
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
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
+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
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
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
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
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 unde
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
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,
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
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
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
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
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
> /etc/rc1.d/K04bind
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
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;
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
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
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
s are caused 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) ...
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
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
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,
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
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
/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 +0100
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
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
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
Package: cups-browsed
Version: 1.28.5-1
Severity: important
X-Debbugs-Cc: t...@mirbsd.de
Nov 23 20:34:11 tglase vmunix: [12181565.392373] cups-browsed[19303]: segfault
at 0 ip f7b5637c sp ffab2890 error 6 in
libcupsfilters.so.1.0.0[f7b3a000+24000]
Nov 23 20:34:11 tglase vmunix:
Hi vorlon,
> attached patch.
I’d have used PREPEND, not APPEND, for -O2. You already STRIP -O3,
so if dpkg-buildflags contains something like -Os or -Og it would
still be honoured with PREPEND.
But it’s almost certainly not worth changing this again; just for
the future, maybe?
bye,
Package: openjdk-11-jdk-headless
Version: 11.0.9.1+1-1
Followup-For: Bug #969038
X-Debbugs-Cc: t...@mirbsd.de
Yes, please *do* take care of this, ideally also in buster,
as this seriously degrades the usability of the software.
For example, JDK 8 had javah but JDK 11 doesn’t, and it’s
supposed
Hi Juhani,
> They've indeed removed src:musescore from unstable but it remains in
> experimental. Do you agree that this bug can be repurposed to request
> musescore be removed from experimental?
yes please.
Thanks,
//mirabilos
Package: firmware-iwlwifi
Version: 20200918-1
Followup-For: Bug #934781
X-Debbugs-Cc: t...@mirbsd.de
It still happens.
[583944.226966] iwl4965 :03:00.0: Microcode SW error detected. Restarting
0x200.
[583944.226974] iwl4965 :03:00.0: Loaded firmware version: 228.61.2.24
On Thu, 19 Nov 2020, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the libncurses6 package:
>
> #971672: ncurses: please add suitable Breaks for cowdancer (<< 0.89~)
Thanks, this does make apt order the package upgrades
On Thu, 19 Nov 2020, Felix Lechner wrote:
> Lintian points out only line 992, but not line 86 (see below). Does
> that mean Lintian was right but used a misleading tag name? Thanks!
Lintian pointed out the ‘'’ part, but it’s the ‘\\’ part which
this subthread was about for.
Background: I was
On Wed, 18 Nov 2020, Matthias Klose wrote:
> On 11/18/20 8:03 PM, Adrian Bunk wrote:
> > New OpenJDK versions tend to cause both buildtime and runtime breakages
> > in reverse dependencies, some of them hard to resolve and requiring
> > updates to new upstream versions which in turn require new
Andrea Bolognani dixit:
>I've taken a stab at addressing this:
Thanks!
> https://salsa.debian.org/libvirt-team/libvirt/-/merge_requests/78
>
>Thorsten, I would appreciate if you could take a look, especially
>since you seem to have some familiarity with this sort of situation
>already.
I’ve
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
Dear ftpmasters,
I had to change the package to little-endian only because it
would not work right on big-endian platforms due to hardcoded
assumptions too large to quickly fix. Upstream is informed.
In the meantime, please
>-- Forwarded message --
>Message-ID: <87k0unhopc@c6.deuxchevaux.org>
[…]
>If that's not possible, you probably need to add a dependency on
>"systemd | opensysusers" and check for "sysusers" or "opensysusers"
>instead of systemd-sysusers, too. opensysusers is an alternative
Package: bc
Version: 1.07.1-2+b2
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
For some reason, bc suddenly displays some lines sometimes in inverse
colour and behaves weird in general.
This happens in xterm directly, but not in GNU screen running in
xterm, so it’s probably $TERM-dependent, and
On Fri, 13 Nov 2020, Mark Hindley wrote:
> Thanks. This is a known issue and already reported with respect to
> wireshark-common.
Indeed. As a workaround one can keep the old version installed for
now.
> > since rsyslog Version 8.2010.0-1 has a versioned dependency on libsystemd0
> > (>= 246),
Package: firmware-misc-nonfree
Version: 20200918-1
Severity: minor
X-Debbugs-Cc: t...@mirbsd.de
I’m getting this during an upgrade in sid:
[…]
Processing triggers for initramfs-tools (0.139) ...
update-initramfs: Generating /boot/initrd.img-5.9.0-2-amd64
W: Possible missing firmware
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
Dear ftpmasters,
please g/c src:musescore from unstable; it’s been renamed
to src:musescore3 fully taking over every binary package
formerly built from there.
Thanks in advance,
//mirabilos
Hi Neil,
>First, regarding the rng-tools version looks rather out of date. From what
yes. As I explicitly wrote in the first message, this is about the
*heavily* patched “Debian classic” version of rng-tools 2.x; the
package with 5.x is called rng-tools5 currently, and updating it
is tracked
Johannes Berg dixit:
>There's virtio-rng in recent kernels, so you could just boot a VM and
>connect the host's /dev/random to that.
Right, I’d even tested that, but the other changes are still
rather intrusive, and I think testing those with real hardware
would be better.
bye,
//mirabilos
--
Hi all,
Henrique de Moraes Holschuh dixit:
>On Thu, Oct 1, 2020, at 21:05, Michael Stone wrote:
>> On Thu, Oct 01, 2020 at 11:20:44PM +, Thorsten Glaser wrote:
>> >Michael Stone dixit:
>> >
>> >> you can fix it right now!
>> >
>> >So
Henrique de Moraes Holschuh dixit:
>On Tue, Nov 10, 2020, at 16:05, Thorsten Glaser wrote:
>> So we additionally have the case where the character device
>> exists but is not usable… oh my.
>
>This was common enough that rngd should know about it and bail out with
>an
close 466946
# housekeeping while here anyway; cf. #911043
reassign 776597 rng-tools-debian
thanks
On Tue, 10 Nov 2020, Trek wrote:
> as far as I know, if the daemon does not have files opened for writing,
> the system should be able to unmount the filesystem correctly
lrwx-- 1 root root 64
Dixi quod…
>among these I (co‑)manage. With “modprobe virtio-rng”, I
>was able to get it on a VM though. Perhaps relevant info:
>
>$ ls -ld /dev/hw*; grep . /sys/devices/virtual/misc/hw_random/*
>crw--- 1 root root 10, 183 Nov 10 17:04 /dev/hwrng
All,
I think due to the complexity of this I’ll postpone
this for after bullseye. Maybe I can get my hands on
systems which Linux /dev/hwrng supports in the mean‐
time, too, and perhaps test both systemd and sysvinit
on those then (help welcome), but for now I’ll leave
this at the refactoring of
Hi Felipe,
>I'll comment only on the init stuff, as I have no idea what rng-tools does.
that’s fair. Thanks anyway.
>It is difficult to comment on this without more details. Maybe it would be
>possible to configure socket activation here? If not, the best option is
AIUI socket activation is
Hi *,
I’m copying this eMail to those who requested various starting
methods for rngd and those who can probably help me with it.
Background: I took over the heavily patched 2.x series of
rng-tools as “rng-tools-debian”, which is currently started
from a sysvinit script only.
Now I have got
tags 792406 + moreinfo
# while here anyway
tags 969568 + moreinfo
thanks
Hi gebi,
isn’t RDRAND/RDSEED supported/used by Linux itself nowadays?
If so, can I close this bug? (Otherwise I would have to move
it to rng-tools-debian for further consideration.)
Thanks,
//mirabilos
--
(gnutls can
On Sat, 7 Nov 2020, Mark Hindley wrote:
> On Sat, Nov 07, 2020 at 06:05:18PM +0100, Trek wrote:
> > have pm-utils installed you could try to run pm-hibernate to see if the
Again, I don’t have hibernation set up at all.
This must not be triggered and if auto-triggered must not do anything.
>
Package: openjdk-11-jre-headless
Version: 11.0.9.1+1-1
Followup-For: Bug #972245
X-Debbugs-Cc: t...@mirbsd.de
Just updating the version for this is still present.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500,
On Fri, 6 Nov 2020, Mark Hindley wrote:
> Can you provide the content of /proc/swaps please.
Sure:
tglase@tglase-nb:~ $ cat /proc/swaps
FilenameTypeSizeUsed
Priority
/dev/sda2 partition
Package: cmake
Version: 3.18.4-1
Severity: wishlist
Tags: upstream
User: reproducible-bui...@lists.alioth.debian.org
Usertags: toolchain, username
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
The musescore3 source package uses the following construct…
COMMAND "${CMAKE_COMMAND}" -E
Package: libvirt-daemon-system
Version: 6.8.0-1
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
I suspect this file should not have been a conffile, i.e. not
shipped in /etc (but somewhere under /usr and copied to /etc
during postinst).
NOTE: Migrating to _that_ setup is dangerous as well, see
Felix Lechner dixit:
>Feel free to try it. The test case is attached.
tglase@tglase-nb:~ $ perl /tmp/x
Wide character in say at /tmp/x line 13.
UTF-8: ✓ (☃)
So lintian maybe behaves different from that testcase?
bye,
//mirabilos
--
15:41⎜ Somebody write a testsuite for helloworld :-)
Felix Lechner dixit:
>The issues have been open since 2007 and 2011. We do not currently
>have a plan for mitigation.
AIUI this only affects buster anyway and not sid?
So it will just go away if we wait long enough.
bye,
//mirabilos
--
(gnutls can also be used, but if you are compiling lynx
On Tue, 27 Oct 2020, Andreas Tille wrote:
> > > Caused by: java.io.IOException: Unable to delete file:
> > > targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests/someDanglingLink
> > > at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:1425)
> > > at
Felix Lechner dixit:
>"wide-character" Perl warning?
No, the first few lines of lintian’s output are literally:
N: Using profile debian/main.
N: Starting on group musescore2/2.3.2+dfsg3-10
N: Finished processing group musescore2/2.3.2+dfsg3-10
E: musescore2 source: malformed-override Unknown
Felix Lechner dixit:
>We are unsure about the last bug, especially because you did not
>report it in unstable (and it would have been hard to miss). The Perl
Ehm, but I’m running unstable and reported it against the version
in unstable. (I was actually seeing this in a cowbuilder buildd
chroot.)
Package: lintian
Version: 2.99.0
I’ve been recompiling musescore2_2.3.2+dfsg3-10.dsc (currently
in sid) on latest sid, to test it for Qt 5.14 compatibility and
latest lintian overrides (modulo #969398, still unfixed).
I’m getting this:
N: Using profile debian/main.
N: Starting on group
>First reported by CrystalMath <~coderain@reactos/developer/theflash>
Here’s the patch they came up with and tested locally.--- ksh-93u+20120801.orig/src/cmd/ksh93/sh/jobs.c
+++ ksh-93u+20120801/src/cmd/ksh93/sh/jobs.c
@@ -,7 +,7 @@ static struct process *job_bystring(regi
int
Package: ksh
Version: 2020.0.0+really93u+20120801-8
Severity: normal
File: /bin/ksh93
X-Debbugs-Cc: t...@mirbsd.de
First reported by CrystalMath <~coderain@reactos/developer/theflash>
in IRC:
ksh93 -c 'kill %-4' segfaults (confirmed by me on sid)
03:18⎜«CrystalMath:#ksh» hi all, i may have
Bernhard Übelacker dixit:
>in options.c:792 the modulus of the rotating degrees is checked to
>be 0. But this is not triggered if degrees is already zero.
>Attached patch should avoid this issue and make xloadimage ignore
>the rotate request.
I’d probably do that for multiples of 360.
Nik,
Package: youtube-dl
Version: 2020.09.14-1
Severity: important
Tags: upstream
X-Debbugs-Cc: t...@mirbsd.de
This is playable from the website.
tglase@tglase-nb:/tmp $ youtube-dl -F
https://www.youtube.com/watch?v=umTVO7IUUJ0
[youtube] umTVO7IUUJ0: Downloading webpage
Control: tags -1 - moreinfo
>I've had a closer look now. The cited commit does correctly remove the
>conffile:
>+rm_conffile /etc/apt/apt.conf.d/01autoremove 215~ postgresql-common
Oh, interesting. Yes, I see that in
/var/lib/dpkg/info/postgresql-common.postinst
but while
Christoph Berg dixit:
>Re: Thorsten Glaser
>> I’ve not looked at createcluster.conf but it will, most likely, also
>> be caused by a similar packaging fault.
>
>Yes, but renaming is not an option there.
Right.
>I'll look into fixing this properly.
Thanks!
>Thanks f
Dixi quod…
>Looking at these files, especially the first, I’m honestly not sure
>whether I want to delete them. If they are not in the binary package
>any more but used to be this is probably a bug?
Looking at past changelogs, I found this:
reassign 971880 dash
affects 971880 debianutils
# focal on WSL 1
found 971880 0.5.10.2-6
# clean sid chroot
found 971880 0.5.10.2-7
retitle 971880 dash: fails to treat export as declaration utility, making
savelog fail with spaces in $PATH
thanks
Dixi quod…
>named 20.04 "focal" running under
Package: debianutils
Version: 4.9.1
Severity: normal
Admittedly, this bugreport comes from Debian derivate which cannot be
named 20.04 "focal" running under WSL 1, but it will certainly apply
to plain Debian as well.
tl;dr: I was trying to run popcon once:
root@DESKTOP-PN6OO9E:~ #
reopen 971672
retitle 971672 ncurses: please add suitable Breaks for cowdancer (<< 0.89~)
severity 971672 normal
thanks
On Thu, 8 Oct 2020, Debian FTP Masters wrote:
> cowdancer (0.89) unstable; urgency=medium
>* Check isatty(3) rather than rely on ncurses/tinfo (Closes: #970555)
Would
Hi *,
I’ve prepared a patch (MR!6) that fixes this issue by switching to
isatty(2) (unless $TERM is dumb, vt100 or vt220) and tested this.
I’d *really* prefer to upload this as 0.89 to sid, so that ncurses
then can place Breaks in the libraries, hoping that that will be
enough to magically fix
Package: postgresql-common
Version: 218
Severity: minor
User: debian...@lists.debian.org
Usertags: adequate obsolete-conffile
X-Debbugs-Cc: t...@mirbsd.de
[…]
Preparing to unpack .../30-postgresql-common_218_all.deb ...
Leaving 'diversion of /usr/bin/pg_config to /usr/bin/pg_config.libpq-dev by
On Sun, 4 Oct 2020, Sven Joachim wrote:
> Use the --no-cowdancer-update as suggested at the end of your log file.
Hrrm, but that’ll be fun if the upgrade fails.
> IMO this is not a bug in ncurses, libncurses6 and libtinfo6 are unpacked
> in the same dpkg run and the former is not guaranteed to
On Sun, 4 Oct 2020, Thorsten Glaser wrote:
> I personally am in favour of the latter. We don’t need colours in
It’s even worse: ncurses are only used to initialise terminfo
and determine whether the terminal supports colours, but the
actual colour calls are hardcoded and don’t use setaf and
found 971674 0.81
notfound 971674 0.80
thanks
> Definitively an issue as log.c (part of the DLL) uses curses
> making the whole thing fragile.
Jessica, you added this in e4b477ef7e77316c5171d15ac119b5766ee2ed73.
I think we either need to create a variant of the DLL without the
ncurses
clone 971672 -1
reassign -1 cowdancer
found -1 0.88
retitle -1 cowdancer: uses ncurses in the LD_PRELOADed DLL, making upgrades
unreliable
thanks
On Sun, 4 Oct 2020, Thorsten Glaser wrote:
> > This seems to actually be a cowbuilder problem thus…
Definitively an issue as log.c (part of t
On Sun, 4 Oct 2020, Thorsten Glaser wrote:
> I cannot update my cowbuilder sid chroot, with the following errors:
>
> […]
> Preparing to unpack .../libncursesw6_6.2+20200918-1_i386.deb ...
> Unpacking libncursesw6:i386 (6.2+20200918-1) over (6.2-1) ...
> Preparing to unpack .
> This seems to actually be a cowbuilder problem thus…
It *also* seems to be a bug in ncurses packages (ordering problem):
(pbuild4531-sid/i386)root@tglase:/# apt-get install libtinfo6
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following
Package: libncurses6
Version: 6.2+20200918-1
Severity: serious
Justification: does not install/upgrade
X-Debbugs-Cc: t.gla...@tarent.de
I cannot update my cowbuilder sid chroot, with the following errors:
[…]
Preparing to unpack .../libncursesw6_6.2+20200918-1_i386.deb ...
Unpacking
Mark Hindley dixit:
>Forwarded upstream.
Thanks.
>> Ib ve also just looked at the elogind.conf file I was told to change in
>> one of the two other bugreports I mentioned above. There is some config
>> regarding hibernation, so I guess, now that I know about the problem,
>> I could just turn
Package: elogind
Version: 243.7-1+debian1
Severity: critical
Justification: causes serious data loss
X-Debbugs-Cc: t...@mirbsd.de
Yay, I found another behavioural difference between just running Debian
(classic, that is, sysvinit withOUT elogind) and Debian with elogind (to
satisfy certain
Hi Adrian,
could you work around the problem by starting an i386 VM on
your amd64 system, and then running the qemu-user buildds on
that? The return values from the syscalls will natively be
correct 32 bit there…
In the meantime, someone found that this bug also hits without
any qemu
Package: debianutils
Version: 4.11.2
Severity: wishlist
X-Debbugs-Cc: t...@mirbsd.de
The recent change changes the application to send this
information to stdout. This however is not what normal
Unix users expect *and* probably will break users’ scripts.
The correct fix for #961872 is to do this
801 - 900 of 4557 matches
Mail list logo
