Package: texlive-base
Version: 2024.20240829-1
Severity: serious
There was a hiccup in today's upgrade:
,
| Vorbereitung zum Entpacken von .../10-texlive-base_2024.20240829-1_all.deb ...
| Entpacken von texlive-base (2024.20240829-1) über (2024.20240706-1) ...
| dpkg: Fehler beim Bearbeiten d
On 2024-08-24 01:47 -0400, Paul Dufresne wrote:
> Package: ncurses-base
> Version: 6.5-2
> Severity: wishlist
>
> Dear Maintainer,
>
> While trying to compile the haskell example program for module ncurses,
> I got the following error:
> While compiling: got:
> Failed to build ncurses-0.2.16.
> Bu
Package: login
Version: 1:4.16.0-2+really2.40.2-4
Severity: serious
Tags: patch
The login package no longer ships its PAM configuration file
/etc/pam.d/login, this will likely lead to breakage on new installations
(on upgrades the file remains as an obsolete conffile).
The following patch fixes t
Package: adequate
Version: 0.16.7
Severity: grave
The current version of adequate fails on any package for me, complaining
about unexpected output from update-binfmts:
,
| $ adequate ncurses-base
| 2024/08/02 17:20:41 Unexpected output from /usr/sbin/update-binfmts
--display: "mask =
Control: reassign -1 librecode0 3.6-27
Control: severity -1 serious
Control: retitle -1 librecode0: removal of symbol rpl_malloc breaks ABI
Control: affects -1 fortune-mod
On 2024-07-15 00:18 +0200, Michael Rasmussen wrote:
> Package: fortune-mod
> Version: 1:1.99.1-7.3
> Severity: important
>
>
Package: dpkg-dev
Version: 1.22.6
To work around FTBFS bug #1066382 in xserver-xorg-video-nouveau, I set
DEB_BUILD_MAINT_OPTIONS=qa=-bug-implicit-func. It seems this is no
longer sufficient with gcc-14, because
-Werror=implicit-function-declaration is actually the default, and so
xserver-xorg-vid
Package: elpa-debian-el
Version: 37.13
Severity: important
I wanted to report a bug against the dpkg-dev package, but that resulted
in a Lisp error before even running reportbug. Below is a backtrace
after loading the debian-bug.el source file.
Downgrading elpa-debian-el to version 37.12 fixes t
Control: tags -1 + patch
On 2024-06-26 11:54 +0200, Sven Joachim wrote:
> Package: elpa-dpkg-dev-el
> Version: 37.12
> Severity: normal
>
> I have started to use Emacs from the recently created emacs-30 branch,
> and noticed that in debian-changelog-mode buffers font-lock-mode
Package: elpa-dpkg-dev-el
Version: 37.12
Severity: normal
I have started to use Emacs from the recently created emacs-30 branch,
and noticed that in debian-changelog-mode buffers font-lock-mode is nil
(M-x font-lock mode fixes that for the current buffer). In the Emacs 30
NEWS file I found the fo
Package: libgl1-mesa-dri
Version: 24.1.1-1
Severity: serious
Control: block -1 by 1067699
I just had to downgrade a bunch of packages from src:mesa to version
24.1.0-2, because the installation of libllvm18:i386 failed due to a
file conflict that has been present for a few months, see #1067699.
P
On 2024-05-30 21:03 +0200, Chris Hofstaedtler wrote:
> Source: libutempter
> Severity: important
>
> Hi,
>
> per the discussion on debian-devel [1], we'll get a Y2038-safe
> replacement for wtmp, named wtmpdb / libwtmpdb etc.
> Please see if your package should integrate with it.
>
> It is unclear
On 2024-05-30 20:45 +0200, Chris Hofstaedtler wrote:
> Source: xterm
> Severity: important
>
> Per the discussion on debian-devel, Debian will switch to wtmpdb for
> Y2038-safe wtmp recording. If your package writes wtmp entries,
> please switch to libpam-wtmpdb or libwtmpdb.
Like most other prog
Control: found -1 1.20.2-1
On 2024-04-17 14:26 +0200, Chris Hofstaedtler wrote:
> Control: tags 1059417 + patch
> Control: tags 1059417 + pending
>
>
> Dear maintainer,
>
> I've prepared an NMU for ed (versioned as 1.20.1-1.1) and
> uploaded it to DELAYED/7. Please feel free to tell me if I
> sho
Package: elpa-magit
Version: 3.3.0+git20231219.1.c7ab6931-1
Severity: serious
After loading magit Emacs displayed the following message in the
*Warnings* buffer:
,
| Emergency (magit): Magit requires ‘transient’ >= 0.5.0,
| but due to bad defaults, Emacs’ package manager, refuses to
| upgrade
On 2024-04-08 14:13 -0600, Sam Hartman wrote:
>> "Professor" == Professor Jeebs writes:
>
>
> Professor> I prefer the way it is handled per user. There is a related,
> commented
> Professor> out, option in /etc/skel/.profile, which lands in new user
> directories,
> Professor>
On 2024-04-08 15:46 +0200, Chris Hofstaedtler wrote:
> To clarify, because I think there is still some ongoing
> confusion regarding binary files and binary packages, here a table:
>
> Debian package name | (primary) file(s)
>
>
On 2024-04-06 21:45 +0200, Santiago Vila wrote:
> El 6/4/24 a las 20:53, Sven Joachim escribió:
>> 1. https://www.debian.org/doc/debian-policy/ch-relationships.html#id11
>
> Ok, I had not read that part of Policy in a long time.
>
> One minor last thing:
>
> Assu
On 2024-04-06 19:49 +0200, Santiago Vila wrote:
>> Patch attached, I have tested that it builds on amd64 and i386. looked
>> at the generated Dependencies and verified that lintian does not go
>> crazy, but that's it. Note that I had to add libtool-bin rather than
>> just libtool to Build-Depends
ase in debian/copyright (Upstream-contact ⇒
Upstream-Contact).
.
[ Sven Joachim ]
* New upstream snapshot.
- Fixes FTBFS with -Werror=implicit-function-declaration
(Closes: #1066469).
* Update debian/watch to version 4, and look for tarballs on
https://invisible
On 2024-04-03 22:47 +0200, Alejandro Colomar wrote:
> On Wed, Apr 03, 2024 at 06:01:50PM +0200, Sven Joachim wrote:
>> Control: severity -1 normal
>>
>> On 2024-04-03 11:29 +0200, Alejandro Colomar wrote:
>>
>> > I now see that `apt-file show glibc-doc` shows s
Control: severity -1 normal
On 2024-04-03 11:29 +0200, Alejandro Colomar wrote:
> Hi,
>
> On Tue, Apr 02, 2024 at 08:58:32PM +0200, Aurelien Jarno wrote:
>> Thanks, that sounds great that we can finally get rid out of those in
>> the debian package.
>>
>> >$ git diff --stat b06cd070f..128a3ae
Package: bsdgames
Version: 2.17-31
Severity: serious
Your package fails to configure in a fresh installation (but not when
upgrading from a previous version). This is what happens in a throwaway
chroot (unrelated lines stripped from apt/dpkg output):
,
| # apt install bsdgames
| Selecting pr
On 2024-04-01 19:02 +0200, Alejandro Colomar wrote:
> Hi Sven,
>
> On Mon, Apr 01, 2024 at 06:38:52PM +0200, Sven Joachim wrote:
>> Makes perfect sense, but at the moment it can only be uploaded to
>> experimental.
>>
>> > We're not in a freeze, so I gue
On 2024-04-01 18:00 +0200, Alejandro Colomar wrote:
> Hi Sven,
>
> On Mon, Apr 01, 2024 at 05:35:18PM +0200, Sven Joachim wrote:
>> Obviously the manpages-dev package should not have shipped these files
>> as long as there are in glibc-doc; this is tracked in #1068166.
>
On 2024-04-01 16:23 +0200, Alejandro Colomar wrote:
> Package: glibc-doc
> Version: 2.38-6
> Severity: serious
> Justification: Policy 7.4
> X-Debbugs-Cc: a...@kernel.org, mar...@debian.org
>
> Dear Maintainer,
>
> The Linux man-pages project has recently added the pthread_*(3) manual
> pages that
Control: tags -1 + patch
On 2024-04-01 06:41 +0200, Sven Joachim wrote:
> Control: notfound -1 6.05.01-1
> Control: found -1 6.7-1
>
> On 2024-04-01 06:17 +0200, Bas Couwenberg wrote:
>
>> Source: manpages
>> Version: 6.05.01-1
>> Severity: serious
>> Justi
Control: notfound -1 6.05.01-1
Control: found -1 6.7-1
On 2024-04-01 06:17 +0200, Bas Couwenberg wrote:
> Source: manpages
> Version: 6.05.01-1
> Severity: serious
> Justification: makes the package in question unusable or mostly so
>
> Dear Maintainer,
>
> manpages-dev failed to upgrade due to a
On 2024-03-30 12:38 +0100, Santiago Vila wrote:
> El 30/3/24 a las 9:43, Sven Joachim escribió:
>> I think it would make sense for Debian to follow what Arch and Fedora
>> are doing, introduce a libdialog15 package with the shared library and a
>> libdialog-dev package wit
On 2023-01-05 20:32 -0500, Thomas Dickey wrote:
> - Original Message -
> | From: "Santiago Vila"
> | To: "Thomas Dickey" , 1012...@bugs.debian.org
> | Cc: "Sven Joachim"
> | Sent: Thursday, January 5, 2023 7:09:22 PM
> | Subject: Bug#101
On 2024-03-29 20:36 -0700, Steve Langasek wrote:
> On Sat, Mar 30, 2024 at 01:41:40AM +0100, Chris Hofstaedtler wrote:
>> Hi OpenSSH, shadow Maintainers,
>>
>> On Sat, Mar 30, 2024 at 01:32:08AM +0100, Chris Hofstaedtler wrote:
>> > On Fri, Mar 29, 2024 at 06:02:
Source: util-linux
Version: 2.40~rc2-8
Severity: wishlist
It seems desirable to ship liblastlog2 in trixie, considering that the
/var/log/lastlog file is not Y2038-safe and pam in unstable has already
dropped pam_lastlog.so, meaning that non-ssh logins are no longer
recorded in /var/log/lastlog.
Package: dh-debputy
Version: 0.1.22
Severity: important
Retrying xterm with dh-debputy (see
https://salsa.debian.org/joachim-guest/xterm/-/tree/debputy?ref_type=heads)
I noticed that no conffiles are registered, although xterm ships various
files in /etc:
,
| $ debdiff /var/cache/apt/archives
Control: severity -1 normal
Am 19.03.2024 um 22:15 schrieb Helge Deller:
> Source: xserver-xorg-video-nouveau
> Version: 1:1.0.17-3
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> X-Debbugs-Cc: del...@debian.org
>
> Failure can
Source: xserver-xorg-video-nouveau
Version: 1:1.0.17-3
Severity: normal
Control: block -1 by 1066966
As a stopgap measure for #1066382, xserver-xorg-nouveau currently
disables -Werror=implicit-function-declaration via
DEB_BUILD_MAINT_OPTIONS=qa=-bug-implicit-func. This is obviously
undesirable an
Package: xserver-xorg-dev
Version: 2:21.1.11-2
Severity: normal
Forwarded: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1222
File: /usr/include/xorg/fb.h
As noticed in #1066382, xserver-xorg-video-nouveau FTBFS with
-Werror=implicit-function-declaration, because wfbScreenInit is no
On 2024-03-13 18:07 +0100, Sven Joachim wrote:
> Control: forwarded -1
> https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/569
>
> On 2024-03-13 12:47 +0100, Lucas Nussbaum wrote:
>
>> Source: xserver-xorg-video-nouveau
>> Version: 1:1.
On 2024-03-13 21:11 +0200, Martin-Éric Racine wrote:
> Package: e2fsprogs
> Version: 1.47.0-2.4
> Severity: important
>
> The latest upload introduces a dependency loop between libss2t64
> versus libss2 which also results in the removal of e2fsprogs-l10n.
No, there is no dependency loop because l
On 2024-03-13 13:08 +0100, Lucas Nussbaum wrote:
> Source: tack
> Version: 1.08-1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20240313 ftbfs-trixie
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
>
Control: forwarded -1 https://gitlab.freedesktop.org/mesa/mesa/-/issues/10613
On 2024-02-17 18:53 +0100, Sven Joachim wrote:
> Control: severity -1 grave
>
> On 2024-02-17 13:35 +0100, Lorenzo Beretta wrote:
>
>> Package: libgl1-mesa-dri
>> Version: 24.0.1-1
>>
Control: forwarded -1
https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/569
On 2024-03-13 12:47 +0100, Lucas Nussbaum wrote:
> Source: xserver-xorg-video-nouveau
> Version: 1:1.0.17-2
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.or
Source: cups
Version: 2.4.7-1.2
Tags: patch
X-Debbugs-Cc: Sven Joachim , Michael Hudson-Doyle
Renaming libcups2 to libcups2t64 has caused several README.Debian.gz
symlinks to become broken:
,
| $ symlinks /usr/share/doc/cups*
| dangling: /usr/share/doc/cups/README.Debian.gz -> ../libcu
Control: tags -1 + patch
On 2024-03-07 18:49 +0100, Sven Joachim wrote:
> Package: wv
> Version: 1.2.9-6.1
> Severity: serious
> X-Debbugs-Cc: Sven Joachim , Steve Langasek
>
>
> After renaming the libwv-1.2-4 library package to libwv-1.2-4t64, the
> /usr/share/d
Package: wv
Version: 1.2.9-6.1
Severity: serious
X-Debbugs-Cc: Sven Joachim , Steve Langasek
After renaming the libwv-1.2-4 library package to libwv-1.2-4t64, the
/usr/share/doc/wv symlink has become dangling.
,
| $ file /usr/share/doc/wv
| /usr/share/doc/wv: broken symbolic link to libwv
Control: tags -1 + patch
On 2024-03-05 11:47 +0100, Sven Joachim wrote:
> Package: perl-base
> Version: 5.38.2-3.1
> Severity: serious
> X-Debbugs-Cc: Sven Joachim , Steve Langasek
>
>
> On i386, perl-base provides perlapi-5.38.2t64 rather than
> perlapi-5.38.2. Thi
Package: perl-base
Version: 5.38.2-3.1
Severity: serious
X-Debbugs-Cc: Sven Joachim , Steve Langasek
On i386, perl-base provides perlapi-5.38.2t64 rather than
perlapi-5.38.2. This makes tons of packages uninstallable or
unbuildable and is not what has been agreed upon in #1060246.
The reason
On 2024-03-04 16:01 +0100, Axel Beckert wrote:
> Source: aptitude
> Version: 0.8.13-5
> Severity: serious
> Tags: ftbfs
> X-Debbugs-Cc: a...@debian.org, z...@debian.org
>
> Citing from https://buildd.debian.org/status/package.php?p=aptitude:
>
> BinNMU changelog for aptitude on amd64, arm64, armel
On 2011-09-27 09:36 -0700, Steve Langasek wrote:
> tags 643560 confirmed
> thanks
>
> On Tue, Sep 27, 2011 at 03:27:47PM +0100, Ian Jackson wrote:
>> Personal groups are the default on Debian. The purpose of personal
>> groups is to allow users to run with a umask of 002 so that they can
>> sensi
Package: libuuid1
Version: 2.39.3-7
Severity: serious
The last upload renamed libuuid1t64 back to libuuid1, but because the
former has an unversioned Replaces: on the latter, it will not take the
library files back. Removing the libuuid1t64 package will therefore
silently lose the files.
It seem
Control: tags -1 + patch
On 2024-02-29 23:26 +0100, Sven Joachim wrote:
> Package: xdelta
> Version: 1.1.3-10.5
> Severity: serious
> X-Debbugs-Cc: Sven Joachim , Steve Langasek
>
>
> The xdelta package still depends on libxdelta2, rather than on
> libxdelta2t64 as it s
Package: xdelta
Version: 1.1.3-10.5
Severity: serious
X-Debbugs-Cc: Sven Joachim , Steve Langasek
The xdelta package still depends on libxdelta2, rather than on
libxdelta2t64 as it should.
The build log on m68k[1] shows that on this architecture libxdelta2t64
gained a dependency on libxdelta2
Control: severity -1 normal
On 2024-02-28 15:49 +0100, Vincent Lefevre wrote:
> Source: apt
> Version: 2.7.12+nmu1
> Severity: serious
>
> While there are no upgrade issues with apt itself (according
> to "apt install -s apt"), aptitude does not want to upgrade
> apt automatically, while this jus
I would like to add a few more points here, not to prolong the
discussion but rather for future reference and for myself.
On 2024-02-21 07:06 +0100, Adam Borowski wrote:
> On Tue, Feb 20, 2024 at 07:41:42PM +0100, Sven Joachim wrote:
>> The reason for including \E(B here is that sg
Control: severity -1 grave
On 2024-02-17 13:35 +0100, Lorenzo Beretta wrote:
> Package: libgl1-mesa-dri
> Version: 24.0.1-1
> Severity: important
>
> Dear Maintainer,
>
> after the latest upgrade it's impossible for me to run a display manager
> or startx any window manager; after at most a few s
On 2024-02-11 22:10 +0100, Rene Engelhard wrote:
> Source: gpgme1.0
> Version: 1.18.0-4.1~exp1
> Severity: important
>
> [ let's no get into a discussion on the sense of this transition. I
> actually believe this isn't needed and we can leave 32 bit die in 2038
> but anyways...
>
> The transition
Package: console-setup
Version: 1.225
Severity: grave
After the upgrade from 1.223, console-setup.service failed to start due
to a syntax error in the setupcon script:
,
| $ setupcon
| /usr/bin/setupcon: 1386: Syntax error: Missing '))'
`
It looks like dash does not like the construct in
Package: libnuma1
Version: 2.0.17-2
Severity: normal
Forwarded: https://github.com/numactl/numactl/issues/212
Tags: fixed-upstream
After today's upgrade I noticed the error message
get_mempolicy: Function not implemented
appearing on my terminal and wondered where it comes from. It turns out
th
On 2024-02-04 19:50 +, Steve Langasek wrote:
> Source: vte
> Version: 1:0.28.2-6
> Severity: serious
> Tags: patch pending sid trixie
> Justification: library ABI skew on upgrade
> User: debian-...@lists.debian.org
> Usertags: time-t
>
> diff -Nru vte-0.28.2/debian/control vte-0.28.2/debian/co
On 2024-01-31 20:15 +, Steve Langasek wrote:
> Source: libcdk5
> Version: 5.0.20180306-3
> Severity: serious
> Tags: patch pending
> Justification: library ABI skew on upgrade
> User: debian-...@lists.debian.org
> Usertags: time-t
>
> Dear maintainer,
Not the maintainer here, I think he is ra
Source: directfb
Version: 1.7.7-11.1~exp1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Sven Joachim , Michael Hudson-Doyle
, Steve Langasek
The experimental upload of directfb FTBFS on all architectures[1],
because debian/libdirectfb-1.7-7t64.install is supposed to be run by
dh-exec, but is
Package: debian-ports-archive-keyring
Version: 2024.01.31
Severity: normal
Upgrading from 2024.01.05 left the obsolete conffile
/etc/apt/trusted.gpg.d/debian-ports-archive-2023.gpg on my system,
because debian/debian-ports-archive-keyring.maintscript has not been
updated when the 2023 key was move
On 2024-01-01 05:14 +0100, наб wrote:
> Package: libncursesw6
> Version: 6.4+20231121-1
> Severity: normal
>
> Dear Maintainer,
>
> I am attaching a repro.c program that when built with
> cc -O3 -g -Wall -Wextra -DNCURSES_WIDECHAR -D_GNU_SOURCE repro.c
> -lncursesw -ltinfo -o repro
You might
On 2024-01-27 13:46 +0100, Sven Joachim wrote:
> Package: libdebhelper-perl
> Version: 13.12
> Severity: important
> X-Debbugs-Cc: Sven Joachim , debian-h...@lists.debian.org
>
> Commit 018a0c9a7164f ("Dh_Lib.pm: Fix warning from `cp -n`") uses cp's
>
Package: coreutils
Version: 9.4-3+b1
,
| $ cp -n /bin/true tmp
| cp: warning: behavior of -n is non-portable and may change in future; use
--update=none instead
`
The advice to use the --update=none option is highly questionable,
because this option is even less portable than -n. It is
Package: libdebhelper-perl
Version: 13.12
Severity: important
X-Debbugs-Cc: Sven Joachim , debian-h...@lists.debian.org
Commit 018a0c9a7164f ("Dh_Lib.pm: Fix warning from `cp -n`") uses cp's
--update=none option which has been introduced rather recently, namely
in coreutils 9.3.
Control: found -1 3.8.5-1
On 2023-12-31 15:31 +0100, Chris Hofstaedtler wrote:
> Source: postfix
> Version: 3.8.4-1
> User: helm...@debian.org
> Usertag: dep17m2
>
> Hi,
>
> postfix installs postfix-instance-generator into
> /lib/systemd/system-generators. This appears to be a hard-coded
> path.
Hi Hilmar,
Am 24.01.2024 um 12:42 schrieb Preuße, Hilmar:
> On 19.01.2024 17:23, Sven Joachim wrote:
>
> Hello,
>
>> Your package's autopkgtest runs the upstream test suite which is
>> nice. However, it first builds the program and then tests that,
>> rathe
Am 21.01.2024 um 15:25 schrieb Helmut Grohne:
> Source: glibc
> Version: 2.37-13
> Tags: patch
> User: helm...@debian.org
> Usertags: dep17m2
>
> Hi Aurelien,
>
> thanks for your answers on IRC to my design question. As promised here
> comes a patch that moves most files in binary packages built f
probably to use the dh_movetousr
tool added in debhelper 13.11.7, see the attached patch.
Cheers,
Sven
[1] https://wiki.debian.org/UsrMerge
From 4f14a04ac48d09e942ee25349862772c7e9448db Mon Sep 17 00:00:00 2001
From: Sven Joachim
Date: Sun, 21 Jan 2024 17:37:15 +0100
Subject: [PATCH] Move
Control: tags -1 + patch
On 2024-01-18 19:32 +0100, Sven Joachim wrote:
> Package: di-utils-terminfo
> Version: 1.148
> Control: block 887649 by -1
>
> Please include the xterm-256color in di-utils-terminfo. AFAICS this is
> a prerequisite for fixing #887649, because vte
Am 20.01.2024 um 10:22 schrieb Preuße, Hilmar:
> On 19.01.2024 18:04, Sven Joachim wrote:
>> On 2024-01-19 17:11 +0100, Sven Joachim wrote:
>
> Hi Sven,
>
>>> Your package has a test suite that probably should be run at build time,
>>> but it is not. I looked
On 2024-01-19 17:11 +0100, Sven Joachim wrote:
> Source: asymptote
> Version: 2.86+ds1-1
>
> Your package has a test suite that probably should be run at build time,
> but it is not. I looked at the git repository and found that it has
> been disabled since at least 2015:
&
Package: asymptote
Version: 2.86+ds1-1
Your package's autopkgtest runs the upstream test suite which is nice.
However, it first builds the program and then tests that, rather than
the package from the archive. This is not very useful, as changes in
reverse dependencies could cause breakage at run
Source: asymptote
Version: 2.86+ds1-1
Your package has a test suite that probably should be run at build time,
but it is not. I looked at the git repository and found that it has
been disabled since at least 2015:
,
| $ git show f69991bf3
| commit f69991bf3cf85c0560ac93a2b24d96ce67c061d9
| A
On 2022-02-03 11:10 +0100, Vincent Lefevre wrote:
> Package: ncurses-bin
> Version: 6.3-2
> Severity: minor
>
> In the infocmp(1) man page:
>
>Changing Databases [-A directory] [-B directory]
>Like other ncurses utilities, infocmp looks for the terminal
>descriptions in seve
Package: di-utils-terminfo
Version: 1.148
Control: block 887649 by -1
Please include the xterm-256color in di-utils-terminfo. AFAICS this is
a prerequisite for fixing #887649, because vte2.91 sets the TERM
environment variable to xterm-256color by default[1,2], while the old
vte package sets TERM
On 2024-01-11 17:59 +0100, Sven Joachim wrote:
> Package: devscripts
> Version: 2.23.7
>
> After upgrading perl from 5.36.0 to 5.38.2, debcheckout displays some
> twenty deprecation warnings:
>
> ,
> | $ debcheckout etckeeper
> | given is deprecated at /usr/bin/deb
Jan 2024 20:52:16 +0100, Sven Joachim wrote:
>
>> > After upgrading rxvt-unicode today, it's no longer displaying UTF-8
>> > properly. /var/log/apt/history.log shows:
>> > Upgrade: rxvt-unicode:amd64 (9.31-1, 9.31-1+b1)
>
> Same here. Which made me quite nervo
On 2024-01-11 19:18 +, Michael Gold wrote:
> Package: rxvt-unicode
> Version: 9.31-1+b1
> Severity: important
>
> Dear Maintainer,
>
> After upgrading rxvt-unicode today, it's no longer displaying UTF-8
> properly. /var/log/apt/history.log shows:
> Upgrade: rxvt-unicode:amd64 (9.31-1, 9.31-
Package: devscripts
Version: 2.23.7
After upgrading perl from 5.36.0 to 5.38.2, debcheckout displays some
twenty deprecation warnings:
,
| $ debcheckout etckeeper
| given is deprecated at /usr/bin/debcheckout line 419.
| when is deprecated at /usr/bin/debcheckout line 420.
| when is deprecate
17 00:00:00 2001
From: Sven Joachim
Date: Wed, 10 Jan 2024 17:31:53 +0100
Subject: [PATCH] Build-depend on dh-sequence-movetousr
This moves the systemd units into /usr/lib/systemd/system in trixie
and later, while keeping them in /lib/systemd/system in
bookworm-backports.
---
debian/control | 1
ll the way back to
version 5.7+20100313-1. Compare commit c8d4cb3d2f99 where this scheme
was introduced:
,
| Author: Sven Joachim
| Date: Sun Mar 14 08:36:49 2010 +0100
|
| Install ncursesw5-config manpage
|
| Since we're calling "make install.libs" rather than "make i
292037fa4fe629a25f9cfbe9e436688d9cdc99da Mon Sep 17 00:00:00 2001
From: Sven Joachim
Date: Sat, 6 Jan 2024 12:49:09 +0100
Subject: [PATCH] Add systemd-dev to Build-Depends
This ensures that the systemd units are installed into
/usr/lib/systemd/system in trixie and later, while keeping them in
/lib/systemd/system in bookworm
On 2011-03-17 18:05 -0400, Thomas Dickey wrote:
> On Wed, 16 Mar 2011, Sven Joachim wrote:
>
>> On 2011-03-15 03:54 +0100, Vincent Lefevre wrote:
>>
>>> Package: ncurses-doc
>>> Version: 5.8+20110307-1
>>
>> Note that none of this is new, the same
On 2023-12-05 23:03 +0100, Santiago Vila wrote:
> Package: src:ap-utils
> Version: 1.5-5
> Severity: serious
> Tags: ftbfs
>
> Dear maintainer:
>
> During a rebuild of all packages in unstable, your package failed to build:
>
> [snip]
>
> The above is just how the build ends and not necessarily th
On 2023-12-26 12:34 +0100, Gioele Barabucci wrote:
> Control: tags -1 moreinfo
> Control: retitle -1 libacl1, debhelper: changelog not detected as binNMU
>
> On Sun, 24 Dec 2023 14:27:22 + Simon McVittie wrote:
>> libacl1 was recently binNMU'd on all architectures to address version skew.
>>
s/src/watch/CMakeFiles/watch.dir/nc_windows/header_window.cpp.o]
> Error 1
The attached patch fixes these errors and similar ones in
analyzers/src/watch/nc_windows/statistics_window.cpp. Note that
getmaxx(window) returns window->_maxx + 1, and similar for getmaxy().
Disclaimer: I have only te
that dradio
builds, not if it works.
Cheers,
Sven
From 4baeee0b133b577e8c76dfec5bd92f77ba805bd9 Mon Sep 17 00:00:00 2001
From: Sven Joachim
Date: Wed, 20 Dec 2023 17:13:56 +0100
Subject: [PATCH] Fix FTBFS with opaque ncurses
Since ncurses patchlevel 20231021 the ITEM structure is opaque, its
members cannot be
Control: tags -1 + fixed-upstream
On 2023-12-05 23:06 +0100, Santiago Vila wrote:
> Package: src:libgnt
> Version: 2.14.3-2
> Severity: serious
> Tags: ftbfs
>
> Dear maintainer:
>
> During a rebuild of all packages in unstable, your package failed to build:
>
> --
On 2023-12-18 22:57 +0100, Christoph Anton Mitterer wrote:
> Package: debian-reference
> Version: 2.109
> Severity: normal
>
>
> Hey.
>
> Something looks odd with the package’s files registration in Debian.
> On upgrade from 2.108 to 2.109 I got:
> Unpacking debian-reference-common (2.109) over (2
ssed
directly anymore. The remedy is rather simple: instead of
item->index, use item_index(item) to retrieve the index. See the
attached patch which can be added to the series file.
Disclaimer: I have only tested that the package builds, not if it works.
Cheers,
Sven
From 037e6dd0794
ressed directly. Use the functions ncurses
provides for this purpose instead.
Author: Sven Joachim
Bug-Debian: https://bugs.debian.org/1057602
--- scm-5f3.orig/crs.c
+++ scm-5f3/crs.c
@@ -250,7 +250,7 @@ SCM owidth(arg)
if (UNBNDP(arg)) arg = cur_outp;
ASRTER(NIMP(arg) && OPOUTPORT
940:53: note: in expansion of macro ‘__MOUSE_IN’
> 940 | if
> (__MOUSE_IN(window_def, m_event, -2, 1, -3, 2) && !focus)
> | ^~
> ydpdict.c:856:67: error: invalid
Sven
From 676299deb4fa83c7f100011da2948c49ba97499c Mon Sep 17 00:00:00 2001
From: Sven Joachim
Date: Sun, 17 Dec 2023 16:15:43 +0100
Subject: [PATCH] Avoid accessing internal ncurses structures
Since ncurses patchlevel 20231021 the WINDOW structure is opaque, its
members cannot be addressed dir
, using the getcury()/getcurx() functions
rather than accessing the stdscr structure directly which no longer
works in current ncurses. It is straightforward, but I have only tested
that bosh builds, not if it works.
Cheers,
Sven
From 4e13fe3db4df26574709c107a24bed9eb8b1924b Mon Sep 17 00:00:00 2001
From: Sven Joachim
Dat
42 | typedef struct _win_st WINDOW;
The attached patch, which can be added to the series file fixes, these
errors and two additional ones in src/linpac.cc, but I have only tested
that the package builds, not if it works. Note that getmaxx(win)
returns win->_maxx + 1, and similar for getmaxy.
tailsWin->_maxy - 2;
> |^~
The attached patch, which can be added to the series file, fixes these
errors, but I have only tested that the package builds, not if it works.
Note that getmaxx(win) returns win->_maxx + 1, and similar f
On 2023-12-11 15:12 -0500, Thomas Dickey wrote:
> On Mon, Dec 11, 2023 at 05:47:23PM +0100, Sven Joachim wrote:
>>
>> I am not familiar with Mercurial, but most likely this has been
>> triggered by the following change in the 2023111 patchlevel:
>>
>> ,
>
Package: pulsemixer
Version: 1.5.1-1.1
Severity: normal
Sending SIGINT to pulsemixer (e.g. by pressing Ctrl-C) prints a
traceback on stdout:
,
| Traceback (most recent call last):
| File "/usr/lib/python3.11/curses/__init__.py", line 94, in wrapper
| return func(stdscr, *args, **kwds)
|
On 2023-12-11 17:47 +0100, Sven Joachim wrote:
> On 2023-12-11 16:22 +0100, Julien Cristau wrote:
>
>> Source: ncurses
>> Version: 6.4+20231121-1
>> Severity: important
>> Control: affects -1 mercurial
>> X-Debbugs-Cc: jcris...@debian.org
>>
>&
On 2023-12-11 16:22 +0100, Julien Cristau wrote:
> Source: ncurses
> Version: 6.4+20231121-1
> Severity: important
> Control: affects -1 mercurial
> X-Debbugs-Cc: jcris...@debian.org
>
> Hi,
>
> Since a ncurses upgrade in testing recently `hg histedit` seems to
> crash consistently, upon trying to
1 - 100 of 1716 matches
Mail list logo