Bug#1070902: console-log: redundant iteration at stopping the initscript, leading to annoying message

[Alex Volkov]

Package: console-log
Version: 1.2-2.1
Severity: minor
Tags: patch

Dear Maintainer,

at the initscript's startup, `daemon` creates both regular and .clientpid
pidfiles for every daemon instance, for example:
/run/console-log/Debian-console-log/9-_-_var_-_log_-_syslog
and
/run/console-log/Debian-console-log/9-_-_var_-_log_-_sy.clientpid

(maybe this `daemon`'s behaviour depends on the system configuration, but on
mine it's how it is)

When stopping, `daemon` deletes both pidfiles. But `console-log`'s initscript
at stopping iterates through *every* file existing in /run/console-log/Debian-
console-log before stopping, including clientpids, leading to an error at the
last iteration, as the directory gets already deleted at that time. Not much of
an issue, but `daemon` in this case outputs the whole of its "usage" page,
filling the console and pushing out other shutdown messages, which potentially
can contain some valuable info about errors etc.

The included patch solves it by excluding *.clientpid files from the iteration.


-- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (991, 'stable-updates'), (991, 'stable-security'), (991, 
'stable'), (99, 'testing'), (90, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.6.13-bootes0-p-1000 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages console-log depends on:
ii  adduser3.134
ii  daemon 0.8-1+b1
ii  kbd2.5.1-1+b1
ii  less   590-2.1~deb12u2
ii  lsb-base   11.6
ii  passwd 1:4.13+dfsg1-1+b1
ii  sysvinit-utils [lsb-base]  3.08-3~bpo12+2

console-log recommends no packages.

console-log suggests no packages.

-- Configuration Files:
/etc/init.d/console-log changed [not included]

-- no debconf information
diff --git a/debian/console-log.init.d b/debian/console-log.init.d
index 6a00d07..5105468 100755
--- a/debian/console-log.init.d
+++ b/debian/console-log.init.d
@@ -245,7 +245,7 @@ do_from_running()
 log_action_begin_msg "checking console-log"
   fi
   CHECKRET=0
-  for PIDPATH in $(find . -maxdepth 2 -type f); do
+  for PIDPATH in $(find . -maxdepth 2 -type f -not -name '*.clientpid'); do
 FILENAME=$(echo $PIDPATH | sed -n 's/.*\/\(.*\)/\1/p')
 PIDFILEDIR=$(echo $PIDPATH | sed -n 's/^.*\/\(.*\)\/.*/\1/p')
 if [ -z "$PIDFILEDIR" ]; then


signature.asc
Description: This is a digitally signed message part.

Bug#1070768: bpfcc: ftbfs on ppc64el

[Luca Boccassi]

Control: tags -1 pending

On Sat, 11 May 2024 at 03:21, Vasudev Kamath
 wrote:
> > On 11 May 2024, at 01:29, Luca Boccassi  wrote:
> >
> > Unless there are objections, I am going to NMU to delayed/3 tomorrow
> > to remove ppc64el
> Please go ahead .
> Thanks and Regards
> Vasudev

Uploaded to DELAYED/3, will push to git once it is in unstable.

Bug#1036826: Please start handling \c

[Martin Quinson]

tag 1036826 fixed-upstream
thanks

Hello Helge,

I think I fixed this bug upstream, and it will be part of the next release,
later this month. I did not implement a full support for \c since it's
difficult in the current code base, but at least the groff.1 page proceeds. 

If you have other failures from other pages, please tell me so that I can check
whether my fix is enough even before the release.

Thanks for your help and patience,
Mt

Le jeudi 14 mars 2024 à 19:56 +, Helge Kreutzmann a écrit :
> Hello Martin,
> Am Sun, Mar 10, 2024 at 10:14:20PM +0100 schrieb Martin Quinson:
> > Instead, I'd appreciate if you could do a merge request with a test file,
> > along
> > with the expected output. It'd save me the time to dig into the discussion
> > of
> > this bug. 
> > 
> > I'm not saying that I won't fix it w/o this test case. I'm just saying that
> > providing a test case is a better approach to speedup the fix than severity
> > abuse.
> 
> I hope explaining the test file in this bug is fine as well, because
> I'm not sure what to do exactly merge and how.
> 
> The test case is groff(1) as it is in Debian unstable:
> 
> $ LC_ALL=C po4a-updatepo -f man --no-deprecation --option groff_code=verbatim
> --option generated --option
> untranslated="}1,Ds,zY,zZ,Ee,ES,dT,FN,NE,NS,EX,EE,Id,rstReportMargin,INDENT,U
> NINDENT,UN,a.RE,\|" --option unknown_macros=untranslated --master groff.1 -M
> utf-8 -p test.pot
> groff.1:2279: (po4a::man)
>   Escape sequence \c encountered. This is not completely
>     handled yet.
> 
> And there is no output.
> 
> If I do a crude preprocessing, it kind of works:
> 
> $ cat groff.1 | perl -p -e 's/\\c\n//' > groff.test.1
> $ LC_ALL=C po4a-updatepo -f man --no-deprecation --option groff_code=verbatim
> --option generated --option
> untranslated="}1,Ds,zY,zZ,Ee,ES,dT,FN,NE,NS,EX,EE,Id,rstReportMargin,INDENT,U
> NINDENT,UN,a.RE,\|" --option unknown_macros=untranslated --master
> groff.test.1 -M utf-8 -p test.pot
> $ wc -l test.pot
> 3157 test.pot
> 
> I hope this helps you working on this, together with the discussion in
> this bug.
> 
> Thanks for your support!
> 
> Greetings
> 
>   Helge



signature.asc
Description: This is a digitally signed message part

Bug#1070564: libqt5quick5-gles: attempt to upgrade to version 5.15.10+dfsg-3 tries to remove other packages

[Dmitry Shachnev]

Hi Cristian!

On Mon, May 06, 2024 at 04:18:32PM +0200, Cristian Ionescu-Idbohrn wrote:
> Package: libqt5quick5-gles
> Version: 5.15.10+dfsg-2+b3
> Severity: important
> 
> Hi,
> 
> I see this message:
> 
> The following packages have been kept back:
>   libqt5quick5-gles

I see you have installed libqt5quick5-gles and the non-GLES variant of
libqt5gui5t64. But your hardware does not really use OpenGL ES, right?

There was a period during the 64-bit time_t transition when apt could
replace libqt5quick5 with libqt5quick5-gles. On March 30th I tigthened
dependencies of libqt5quick5-gles to prevent that [1], but probably you
upgraded your system before then.

If my guess is right and you do not really need the GLES variant, the
right thing to do will be to install libqt5quick5, which will remove
libqt5quick5-gles and let the other packages be upgraded. Please try that
and let me know if it helps.

[1]: 
https://tracker.debian.org/news/1515848/accepted-qtdeclarative-opensource-src-gles-51510dfsg-3-source-into-unstable/

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#1070901: POP3 authentication failures due to binary blob transmission before credentials (2 bugs)

[Manny]

Package: curl
Version: 7.88.1-10+deb12u5
Severity: normal
Tags: upstream
X-Debbugs-Cc: dan...@haxx.se, debbug.c...@sideload.33mail.com

cURL is unable to get a list of emails via POP3 from any of the
onionmail.info servers¹. These servers are fragile with quality issues
that show astonishing behaviour in some cases, but fetchmail works
nonetheless. cURL should be able to emulate the working fetchmail
session.

The access instructions from the server (which may have changed):

  ===8<
  POP3 Server   yllvy3mhtamstbqzm4wucfwab57ap6zraxqvkjn2iobmrtxdsnb37dqd.onion
  Server type   POP3
  Server Port   110
  SSL Mode  Use SSL via STLS (TLS)
  Password type Clear
  Connect via   TOR network
  ===8<

Fetchmail has no problem accessing the server. A successful fetchmail
transcript looks like this:

  ===8<
  fetchmail: 6.4.37 querying onionmail (protocol POP3) at Sat 11 May 2024 
00:00:00 AM CEST: poll started
  fetchmail: Trying to connect to 127.0.0.1/12345...connected.
  fetchmail: POP3< +OK POP3 
yllvy3mhtamstbqzm4wucfwab57ap6zraxqvkjn2iobmrtxdsnb37dqd.onion INF N/A t2gi9
  fetchmail: POP3> CAPA
  fetchmail: POP3< +OK Capability list follows
  fetchmail: POP3< USER
  fetchmail: POP3< LOGIN-DELAY 900
  fetchmail: POP3< EXPIRE 30
  fetchmail: POP3< UIDL
  fetchmail: POP3< STLS
  fetchmail: POP3< STARTTLS
  fetchmail: POP3< RQUS
  fetchmail: POP3< RQEX
  fetchmail: POP3< IMPLEMENTATION POP3
  fetchmail: POP3< .
  fetchmail: POP3> STLS
  fetchmail: POP3< +OK Begin TLS negotiation
  fetchmail: Loaded OpenSSL library 0x30b0 newer than headers 0x3080, 
trying to continue.
  fetchmail: Server certificate:
  fetchmail: Issuer Organization: anonmail
  fetchmail: Issuer CommonName: 
yllvy3mhtamstbqzm4wucfwab57ap6zraxqvkjn2iobmrtxdsnb37dqd.onion
  fetchmail: Subject CommonName: 
yllvy3mhtamstbqzm4wucfwab57ap6zraxqvkjn2iobmrtxdsnb37dqd.onion
  fetchmail: Server CommonName mismatch: 
yllvy3mhtamstbqzm4wucfwab57ap6zraxqvkjn2iobmrtxdsnb37dqd.onion != 127.0.0.1
  fetchmail: onionmail key fingerprint: 
25:95:69:E6:A9:3A:97:7B:B1:4A:4B:36:09:14:EF:93
  fetchmail: Server certificate verification error: unable to get local issuer 
certificate
  fetchmail: Broken certification chain at: 
/ST=onionland/OU=anonmail/O=anonmail/C=XX/CN=yllvy3mhtamstbqzm4wucfwab57ap6zraxqvkjn2iobmrtxdsnb37dqd.onion
  fetchmail: This could mean that the server did not provide the intermediate 
CA's certificate(s), which is nothing fetchmail could do anything about.  For 
details, please see the README.SSL-SERVER document that ships with fetchmail.
  fetchmail: This could mean that the root CA's signing certificate is not in 
the trusted CA certificate location, or that c_rehash needs to be run on the 
certificate directory. For details, please see the documentation of 
--sslcertpath and --sslcertfile in the manual page. See README.SSL for details.
  fetchmail: Server certificate:
  fetchmail: Issuer Organization: anonmail
  fetchmail: Issuer CommonName: 
yllvy3mhtamstbqzm4wucfwab57ap6zraxqvkjn2iobmrtxdsnb37dqd.onion
  fetchmail: Subject CommonName: 
yllvy3mhtamstbqzm4wucfwab57ap6zraxqvkjn2iobmrtxdsnb37dqd.onion
  fetchmail: Server CommonName mismatch: 
yllvy3mhtamstbqzm4wucfwab57ap6zraxqvkjn2iobmrtxdsnb37dqd.onion != 127.0.0.1
  fetchmail: Server certificate verification error: hostname mismatch
  fetchmail: Server certificate:
  fetchmail: Issuer Organization: anonmail
  fetchmail: Issuer CommonName: 
yllvy3mhtamstbqzm4wucfwab57ap6zraxqvkjn2iobmrtxdsnb37dqd.onion
  fetchmail: Subject CommonName: 
yllvy3mhtamstbqzm4wucfwab57ap6zraxqvkjn2iobmrtxdsnb37dqd.onion
  fetchmail: Server CommonName mismatch: 
yllvy3mhtamstbqzm4wucfwab57ap6zraxqvkjn2iobmrtxdsnb37dqd.onion != 127.0.0.1
  fetchmail: Server certificate verification error: unable to verify the first 
certificate
  fetchmail: Server certificate:
  fetchmail: Issuer Organization: anonmail
  fetchmail: Issuer CommonName: 
yllvy3mhtamstbqzm4wucfwab57ap6zraxqvkjn2iobmrtxdsnb37dqd.onion
  fetchmail: Subject CommonName: 
yllvy3mhtamstbqzm4wucfwab57ap6zraxqvkjn2iobmrtxdsnb37dqd.onion
  fetchmail: Server CommonName mismatch: 
yllvy3mhtamstbqzm4wucfwab57ap6zraxqvkjn2iobmrtxdsnb37dqd.onion != 127.0.0.1
  fetchmail: SSL/TLS: using protocol TLSv1.2, cipher AES256-GCM-SHA384, 256/256 
secret/processed bits
  fetchmail: Warning: the connection is insecure, continuing anyways. (Better 
use --sslcertck!)
  fetchmail: 127.0.0.1: upgrade to TLS succeeded.
  fetchmail: POP3> CAPA
  fetchmail: POP3< +OK Capability list follows
  fetchmail: POP3< USER
  fetchmail: POP3< LOGIN-DELAY 900
  fetchmail: POP3< EXPIRE 30
  fetchmail: POP3< UIDL
  fetchmail: POP3< RQUS
  fetchmail: POP3< RQEX
  fetchmail: POP3< IMPLEMENTATION POP3
  fetchmail: POP3< .
  fetchmail: POP3> USER mannysUID
  fetchmail: POP3< +OK
  fetchmail: POP3> PASS *
  fetchmail: POP3< +OK
  fetchmail: POP3> STAT
  fetchmail: POP3< 

Bug#1070900: valentina: FTBFS: Error copying /<>/src/app/tape/bin/tape to /<>/debian/tmp/usr/bin/tape: Cannot create /<>/debian/tmp/usr/bin/tape for output

[Santiago Vila]

Package: src:valentina
Version: 0.7.52~dfsg-1
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
QT_SELECT=5 dh_auto_configure -- \
PREFIX_LIB=/usr/lib/valentina \
QMAKE_LFLAGS_RELEASE+=-Wl,-rpath,/usr/lib/valentina \
QMAKE_LFLAGS_DEBUG+=-Wl,-rpath,/usr/lib/valentina \
CONFIG+=noStripDebugSymbols CONFIG+=no_ccache CONFIG+=release
qmake -makefile "QMAKE_CFLAGS_RELEASE=-g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2" "QMAKE_CFLAGS_DEBUG=-g 
-O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2" "QMAKE_CXXFLAGS_RELEASE=-g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2" "QMAKE_CXXFLAGS_DEBUG=-g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time 
-D_FORTIFY_SOURCE=2" QMAKE_LFLAGS_RELEASE=-Wl,-z,relro QMAKE_LFLAGS_DEBUG=-Wl,-z,relro QMAKE_STRIP=: PREFIX=/usr PREFIX_LIB=/usr/lib/valentina 
QMAKE_LFLAGS_RELEASE\+=-Wl,-rpath,/usr/lib/valentina QMAKE_LFLAGS_DEBUG\+=-Wl,-rpath,/usr/lib/valentina CONFIG\+=noStripDebugSymbols CONFIG\+=no_ccache CONFIG\+=release
Info: creating stash file /<>/.qmake.stash
Project MESSAGE: g++ version 13.x found

[... snipped ...]

ln -s -f /<>/src/app/../../share/translations/measurements_p48_fi_FI.qm 
/<>/src/app/tape/bin/translations/measurements_p48_fi_FI.qm &
ln -s -f /<>/src/app/../../share/translations/measurements_p49_fi_FI.qm 
/<>/src/app/tape/bin/translations/measurements_p49_fi_FI.qm &
ln -s -f /<>/src/app/../../share/translations/measurements_p50_fi_FI.qm 
/<>/src/app/tape/bin/translations/measurements_p50_fi_FI.qm &
ln -s -f /<>/src/app/../../share/translations/measurements_p51_fi_FI.qm 
/<>/src/app/tape/bin/translations/measurements_p51_fi_FI.qm &
ln -s -f /<>/src/app/../../share/translations/measurements_p52_fi_FI.qm 
/<>/src/app/tape/bin/translations/measurements_p52_fi_FI.qm &
ln -s -f /<>/src/app/../../share/translations/measurements_p53_fi_FI.qm 
/<>/src/app/tape/bin/translations/measurements_p53_fi_FI.qm &
ln -s -f /<>/src/app/../../share/translations/measurements_p54_fi_FI.qm 
/<>/src/app/tape/bin/translations/measurements_p54_fi_FI.qm &
ln -s -f /<>/src/app/../../share/translations/measurements_p998_fi_FI.qm 
/<>/src/app/tape/bin/translations/measurements_p998_fi_FI.qm &
ln -s -f /<>/src/app/../../share/translations/measurements_p0_en_US.qm 
/<>/src/app/tape/bin/translations/measurements_p0_en_US.qm &
ln -s -f /<>/src/app/../../share/translations/measurements_p1_en_US.qm 
/<>/src/app/tape/bin/translations/measurements_p1_en_US.qm &
ln -s -f /<>/src/app/../../share/translations/measurements_p2_en_US.qm 
/<>/src/app/tape/bin/translations/measurements_p2_en_US.qm &
ln -s -f /<>/src/app/../../share/translations/measurements_p3_en_US.qm 
/<>/src/app/tape/bin/translations/measurements_p3_en_US.qm &
ln -s -f /<>/src/app/../../share/translations/measurements_p4_en_US.qm 
/<>/src/app/tape/bin/translations/measurements_p4_en_US.qm &
ln -s -f /<>/src/app/../../share/translations/measurements_p5_en_US.qm 
/<>/src/app/tape/bin/translations/measurements_p5_en_US.qm &
ln -s -f /<>/src/app/../../share/translations/measurements_p6_en_US.qm 
/<>/src/app/tape/bin/translations/measurements_p6_en_US.qm &
ln -s -f /<>/src/app/../../share/translations/measurements_p7_en_US.qm 
/<>/src/app/tape/bin/translations/measurements_p7_en_US.qm &
ln -s -f /<>/src/app/../../share/translations/measurements_p8_en_US.qm 
/<>/src/app/tape/bin/translations/measurements_p8_en_US.qm &
ln -s -f /<>/src/app/../../share/translations/measurements_p9_en_US.qm 
/<>/src/app/tape/bin/translations/measurements_p9_en_US.qm &
ln -s -f /<>/src/app/../../share/translations/measurements_p10_en_US.qm 
/<>/src/app/tape/bin/translations/measurements_p10_en_US.qm &
ln -s -f /<>/src/app/../../share/translations/measurements_p11_en_US.qm 
/<>/src/app/tape/bin/translations/measurements_p11_en_US.qm &
ln -s -f /<>/src/app/../../share/translations/measurements_p12_en_US.qm 
/<>/src/app/tape/bin/translations/measurements_p12_en_US.qm &
ln -s -f /<>/src/app/../../share/translations/measurements_p13_en_US.qm 
/<>/src/app/tape/bin/translations/measurements_p13_en_US.qm &
ln -s -f /<>/src/app/../../share/translations/measurements_p14_en_US.qm 

Bug#1070899: zfs-linux: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below

[Santiago Vila]

Package: src:zfs-linux
Version: 2.2.3-2
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary --with autoreconf,python3,sphinxdoc
   dh_update_autotools_config
cp: warning: behavior of -n is non-portable and may change in future; use 
--update=none instead
cp: warning: behavior of -n is non-portable and may change in future; use 
--update=none instead
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
dh_autoreconf
configure.ac: warning: AM_GNU_GETTEXT is used, but not AM_GNU_GETTEXT_VERSION 
or AM_GNU_GETTEXT_REQUIRE_VERSION
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'config'.
libtoolize: copying file 'config/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'config'.
libtoolize: copying file 'config/libtool.m4'
libtoolize: copying file 'config/ltoptions.m4'

[... snipped ...]

+ '[' -L /<>/debian/tmp/etc/zfs/zpool.d/fault_led ']'
+ ln -s /usr/lib/zfs-linux/zpool.d/fault_led 
/<>/debian/tmp/etc/zfs/zpool.d
+ for f in dm-deps enc encdev fault_led iostat iostat-1s iostat-10s label 
locate_led lsblk media model serial ses size slot smart smartx temp health 
r_proc w_proc r_ucor w_ucor nonmed defect hours_on realloc rep_ucor cmd_to 
pend_sec off_ucor ata_err nvme_err pwr_cyc upath vendor smart_test test_type 
test_status test_progress test_ended
+ '[' -f /<>/debian/tmp/etc/zfs/zpool.d/iostat ']'
+ '[' -L /<>/debian/tmp/etc/zfs/zpool.d/iostat ']'
+ ln -s /usr/lib/zfs-linux/zpool.d/iostat 
/<>/debian/tmp/etc/zfs/zpool.d
+ for f in dm-deps enc encdev fault_led iostat iostat-1s iostat-10s label 
locate_led lsblk media model serial ses size slot smart smartx temp health 
r_proc w_proc r_ucor w_ucor nonmed defect hours_on realloc rep_ucor cmd_to 
pend_sec off_ucor ata_err nvme_err pwr_cyc upath vendor smart_test test_type 
test_status test_progress test_ended
+ '[' -f /<>/debian/tmp/etc/zfs/zpool.d/iostat-1s ']'
+ '[' -L /<>/debian/tmp/etc/zfs/zpool.d/iostat-1s ']'
+ ln -s /usr/lib/zfs-linux/zpool.d/iostat-1s 
/<>/debian/tmp/etc/zfs/zpool.d
+ for f in dm-deps enc encdev fault_led iostat iostat-1s iostat-10s label 
locate_led lsblk media model serial ses size slot smart smartx temp health 
r_proc w_proc r_ucor w_ucor nonmed defect hours_on realloc rep_ucor cmd_to 
pend_sec off_ucor ata_err nvme_err pwr_cyc upath vendor smart_test test_type 
test_status test_progress test_ended
+ '[' -f /<>/debian/tmp/etc/zfs/zpool.d/iostat-10s ']'
+ '[' -L /<>/debian/tmp/etc/zfs/zpool.d/iostat-10s ']'
+ ln -s /usr/lib/zfs-linux/zpool.d/iostat-10s 
/<>/debian/tmp/etc/zfs/zpool.d
+ for f in dm-deps enc encdev fault_led iostat iostat-1s iostat-10s label 
locate_led lsblk media model serial ses size slot smart smartx temp health 
r_proc w_proc r_ucor w_ucor nonmed defect hours_on realloc rep_ucor cmd_to 
pend_sec off_ucor ata_err nvme_err pwr_cyc upath vendor smart_test test_type 
test_status test_progress test_ended
+ '[' -f /<>/debian/tmp/etc/zfs/zpool.d/label ']'
+ '[' -L /<>/debian/tmp/etc/zfs/zpool.d/label ']'
+ ln -s /usr/lib/zfs-linux/zpool.d/label 
/<>/debian/tmp/etc/zfs/zpool.d
+ for f in dm-deps enc encdev fault_led iostat iostat-1s iostat-10s label 
locate_led lsblk media model serial ses size slot smart smartx temp health 
r_proc w_proc r_ucor w_ucor nonmed defect hours_on realloc rep_ucor cmd_to 
pend_sec off_ucor ata_err nvme_err pwr_cyc upath vendor smart_test test_type 
test_status test_progress test_ended
+ '[' -f /<>/debian/tmp/etc/zfs/zpool.d/locate_led ']'
+ '[' -L /<>/debian/tmp/etc/zfs/zpool.d/locate_led ']'
+ ln -s /usr/lib/zfs-linux/zpool.d/locate_led 
/<>/debian/tmp/etc/zfs/zpool.d
+ for f in dm-deps enc encdev fault_led iostat iostat-1s iostat-10s label 
locate_led lsblk media model serial ses size slot smart smartx temp health 
r_proc w_proc r_ucor w_ucor nonmed defect hours_on realloc rep_ucor cmd_to 
pend_sec off_ucor ata_err nvme_err pwr_cyc upath vendor smart_test test_type 
test_status test_progress test_ended
+ '[' -f /<>/debian/tmp/etc/zfs/zpool.d/lsblk ']'
+ '[' -L /<>/debian/tmp/etc/zfs/zpool.d/lsblk ']'
+ ln -s /usr/lib/zfs-linux/zpool.d/lsblk 
/<>/debian/tmp/etc/zfs/zpool.d
+ for f in dm-deps enc encdev fault_led iostat iostat-1s iostat-10s label 
locate_led lsblk media model serial ses size slot smart smartx temp health 
r_proc w_proc r_ucor w_ucor nonmed defect hours_on realloc rep_ucor cmd_to 
pend_sec off_ucor ata_err nvme_err pwr_cyc upath vendor smart_test test_type 
test_status test_progress test_ended
+ '[' -f /<>/debian/tmp/etc/zfs/zpool.d/media ']'
+ '[' -L /<>/debian/tmp/etc/zfs/zpool.d/media ']'
+ ln -s /usr/lib/zfs-linux/zpool.d/media 
/<>/debian/tmp/etc/zfs/zpool.d
+ for f in dm-deps enc encdev fault_led iostat iostat-1s iostat-10s label 
locate_led lsblk media model serial ses size slot smart smartx temp health 
r_proc w_proc r_ucor w_ucor nonmed 

Bug#1070898: slurm-wlm: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below

[Santiago Vila]

Package: src:slurm-wlm
Version: 23.11.4-2
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules build
dh build --builddirectory --with bash-completion
   dh_update_autotools_config -O--builddirectory
cp: warning: behavior of -n is non-portable and may change in future; use 
--update=none instead
cp: warning: behavior of -n is non-portable and may change in future; use 
--update=none instead
   dh_autoreconf -O--builddirectory
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'auxdir'.
libtoolize: copying file 'auxdir/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'auxdir'.
libtoolize: copying file 'auxdir/libtool.m4'
libtoolize: copying file 'auxdir/ltoptions.m4'
libtoolize: copying file 'auxdir/ltsugar.m4'
libtoolize: copying file 'auxdir/ltversion.m4'
libtoolize: copying file 'auxdir/lt~obsolete.m4'

[... snipped ...]

copy from 
`debian/slurm-wlm-basic-plugins-dev/usr/lib/x86_64-linux-gnu/slurm-wlm/libslurm_pmi.a(list.o)'
 [elf64-x86-64] to 
`debian/slurm-wlm-basic-plugins-dev/usr/lib/x86_64-linux-gnu/slurm-wlm/stwwEn56/list.o'
 [elf64-x86-64]
copy from 
`debian/slurm-wlm-basic-plugins-dev/usr/lib/x86_64-linux-gnu/slurm-wlm/libslurm_pmi.a(log.o)'
 [elf64-x86-64] to 
`debian/slurm-wlm-basic-plugins-dev/usr/lib/x86_64-linux-gnu/slurm-wlm/stwwEn56/log.o'
 [elf64-x86-64]
copy from 
`debian/slurm-wlm-basic-plugins-dev/usr/lib/x86_64-linux-gnu/slurm-wlm/libslurm_pmi.a(mcs.o)'
 [elf64-x86-64] to 
`debian/slurm-wlm-basic-plugins-dev/usr/lib/x86_64-linux-gnu/slurm-wlm/stwwEn56/mcs.o'
 [elf64-x86-64]
copy from 
`debian/slurm-wlm-basic-plugins-dev/usr/lib/x86_64-linux-gnu/slurm-wlm/libslurm_pmi.a(mpi.o)'
 [elf64-x86-64] to 
`debian/slurm-wlm-basic-plugins-dev/usr/lib/x86_64-linux-gnu/slurm-wlm/stwwEn56/mpi.o'
 [elf64-x86-64]
copy from 
`debian/slurm-wlm-basic-plugins-dev/usr/lib/x86_64-linux-gnu/slurm-wlm/libslurm_pmi.a(net.o)'
 [elf64-x86-64] to 
`debian/slurm-wlm-basic-plugins-dev/usr/lib/x86_64-linux-gnu/slurm-wlm/stwwEn56/net.o'
 [elf64-x86-64]
copy from 
`debian/slurm-wlm-basic-plugins-dev/usr/lib/x86_64-linux-gnu/slurm-wlm/libslurm_pmi.a(node_conf.o)'
 [elf64-x86-64] to 
`debian/slurm-wlm-basic-plugins-dev/usr/lib/x86_64-linux-gnu/slurm-wlm/stwwEn56/node_conf.o'
 [elf64-x86-64]
copy from 
`debian/slurm-wlm-basic-plugins-dev/usr/lib/x86_64-linux-gnu/slurm-wlm/libslurm_pmi.a(node_features.o)'
 [elf64-x86-64] to 
`debian/slurm-wlm-basic-plugins-dev/usr/lib/x86_64-linux-gnu/slurm-wlm/stwwEn56/node_features.o'
 [elf64-x86-64]
copy from 
`debian/slurm-wlm-basic-plugins-dev/usr/lib/x86_64-linux-gnu/slurm-wlm/libslurm_pmi.a(node_info.o)'
 [elf64-x86-64] to 
`debian/slurm-wlm-basic-plugins-dev/usr/lib/x86_64-linux-gnu/slurm-wlm/stwwEn56/node_info.o'
 [elf64-x86-64]
copy from 
`debian/slurm-wlm-basic-plugins-dev/usr/lib/x86_64-linux-gnu/slurm-wlm/libslurm_pmi.a(oci_config.o)'
 [elf64-x86-64] to 
`debian/slurm-wlm-basic-plugins-dev/usr/lib/x86_64-linux-gnu/slurm-wlm/stwwEn56/oci_config.o'
 [elf64-x86-64]
copy from 
`debian/slurm-wlm-basic-plugins-dev/usr/lib/x86_64-linux-gnu/slurm-wlm/libslurm_pmi.a(openapi.o)'
 [elf64-x86-64] to 
`debian/slurm-wlm-basic-plugins-dev/usr/lib/x86_64-linux-gnu/slurm-wlm/stwwEn56/openapi.o'
 [elf64-x86-64]
copy from 
`debian/slurm-wlm-basic-plugins-dev/usr/lib/x86_64-linux-gnu/slurm-wlm/libslurm_pmi.a(optz.o)'
 [elf64-x86-64] to 
`debian/slurm-wlm-basic-plugins-dev/usr/lib/x86_64-linux-gnu/slurm-wlm/stwwEn56/optz.o'
 [elf64-x86-64]
copy from 
`debian/slurm-wlm-basic-plugins-dev/usr/lib/x86_64-linux-gnu/slurm-wlm/libslurm_pmi.a(pack.o)'
 [elf64-x86-64] to 
`debian/slurm-wlm-basic-plugins-dev/usr/lib/x86_64-linux-gnu/slurm-wlm/stwwEn56/pack.o'
 [elf64-x86-64]
copy from 
`debian/slurm-wlm-basic-plugins-dev/usr/lib/x86_64-linux-gnu/slurm-wlm/libslurm_pmi.a(parse_config.o)'
 [elf64-x86-64] to 
`debian/slurm-wlm-basic-plugins-dev/usr/lib/x86_64-linux-gnu/slurm-wlm/stwwEn56/parse_config.o'
 [elf64-x86-64]
copy from 
`debian/slurm-wlm-basic-plugins-dev/usr/lib/x86_64-linux-gnu/slurm-wlm/libslurm_pmi.a(parse_time.o)'
 [elf64-x86-64] to 
`debian/slurm-wlm-basic-plugins-dev/usr/lib/x86_64-linux-gnu/slurm-wlm/stwwEn56/parse_time.o'
 [elf64-x86-64]
copy from 
`debian/slurm-wlm-basic-plugins-dev/usr/lib/x86_64-linux-gnu/slurm-wlm/libslurm_pmi.a(parse_value.o)'
 [elf64-x86-64] to 
`debian/slurm-wlm-basic-plugins-dev/usr/lib/x86_64-linux-gnu/slurm-wlm/stwwEn56/parse_value.o'
 [elf64-x86-64]
copy from 
`debian/slurm-wlm-basic-plugins-dev/usr/lib/x86_64-linux-gnu/slurm-wlm/libslurm_pmi.a(partition_info.o)'
 [elf64-x86-64] to 
`debian/slurm-wlm-basic-plugins-dev/usr/lib/x86_64-linux-gnu/slurm-wlm/stwwEn56/partition_info.o'
 [elf64-x86-64]
copy from 
`debian/slurm-wlm-basic-plugins-dev/usr/lib/x86_64-linux-gnu/slurm-wlm/libslurm_pmi.a(plugin.o)'
 [elf64-x86-64] to 

Bug#1070897: netcdf: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below

[Santiago Vila]

Package: src:netcdf
Version: 1:4.9.2-5
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary --buildsystem=cmake
   dh_update_autotools_config -O--buildsystem=cmake
cp: warning: behavior of -n is non-portable and may change in future; use 
--update=none instead
cp: warning: behavior of -n is non-portable and may change in future; use 
--update=none instead
   dh_autoreconf -O--buildsystem=cmake
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'

[... snipped ...]

-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/group__error.html
-- Installing: /<>/debian/tmp/usr/share/doc/netCDF/html/dv2i_8c.js
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/md__2build_2netcdf-FDxGhm_2netcdf-4_89_82_2docs_2quantize.html
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/globals_a.html
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/dir_da7ee69c60c6cc261c862ec60d8c4bc7.js
-- Installing: /<>/debian/tmp/usr/share/doc/netCDF/html/deptree.jpg
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/dparallel_8c.js
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/dvarput_8c_source.html
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/globals_defs.js
-- Installing: /<>/debian/tmp/usr/share/doc/netCDF/html/pages.html
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/group__groups.html
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/folderclosedd.svg
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/dir_d28a4824dc47e487b107a5db32ef43c4_dep.md5
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/dv2i_8c__incl.png
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/credits.html
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/netcdf_8h__dep__incl.png
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/dcopy_8c_source.html
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/dir_631c2833e5f522ae960c02118f928d2b_dep.md5
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/nc-error-codes.html
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/globals_h.html
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/sfc_pres_temp_wr_8c-example.html
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/netcdf_8h__dep__incl.md5
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/dvarinq_8c.html
-- Installing: /<>/debian/tmp/usr/share/doc/netCDF/html/files.html
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/dattinq_8c_source.html
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/simple__xy__nc4__wr_8c__incl.md5
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/dvarget_8c__incl.map
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/dattget_8c_source.html
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/dcompound_8c__incl.map
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/dcopy_8c.html
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/dir_4af48c008ed9ab875dc6ef6de7ae2f59.html
-- Installing: /<>/debian/tmp/usr/share/doc/netCDF/html/tab_h.png
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/dir_d28a4824dc47e487b107a5db32ef43c4.js
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/simple_xy_rd_8c-example.html
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/nc4grp_8c_source.html
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/dir_d44c64559bbebec7f509842c48db8b23.js
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/nc4type_8c_source.html
-- Installing: /<>/debian/tmp/usr/share/doc/netCDF/html/terra.jpg
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/dvar_8c_source.html
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/dfile_8c__incl.md5
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/dir_4af48c008ed9ab875dc6ef6de7ae2f59.js
-- Installing: /<>/debian/tmp/usr/share/doc/netCDF/html/nav_g.png
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/dcompound_8c_source.html
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/dir_04_03.html
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/pres__temp__4D__rd_8c__incl.png
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/nc4internal_8c__incl.md5
-- Installing: /<>/debian/tmp/usr/share/doc/netCDF/html/tab_sd.png
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/nc4attr_8c__incl.map
-- Installing: /<>/debian/tmp/usr/share/doc/netCDF/html/open.png
-- Installing: 
/<>/debian/tmp/usr/share/doc/netCDF/html/simple__xy__nc4__wr_8c_source.html
-- Installing: 

Bug#1070896: labplot: FTBFS: dh_auto_configure fails

[Santiago Vila]

Package: src:labplot
Version: 2.10.1-2
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary --with kf5
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -Skf5 -- -DENABLE_REPRODUCIBLE=ON -DENABLE_VECTOR_BLF=OFF
cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb cmake 
-DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
-DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
-DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DCMAKE_BUILD_TYPE=Debian 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DKDE_INSTALL_USE_QT_SYS_PATHS=ON -DENABLE_REPRODUCIBLE=ON 
-DENABLE_VECTOR_BLF=OFF ..
CMake Warning (dev) at CMakeLists.txt:1 (project):
  cmake_minimum_required() should be called prior to this top-level project()
  call.  Please see the cmake-commands(7) manual for usage documentation of
  both commands.
This warning is for project developers.  Use -Wno-dev to suppress it.


[... snipped ...]

//system admin executables (EXECROOTDIR/sbin)
KDE_INSTALL_SBINDIR:PATH=

//modifiable architecture-independent data (com)
KDE_INSTALL_SHAREDSTATEDIR:PATH=

//sound files (DATAROOTDIR/sounds)
KDE_INSTALL_SOUNDDIR:PATH=

//read-only single-machine data (/etc)
KDE_INSTALL_SYSCONFDIR:PATH=/etc

//Systemd units (CMAKE_INSTALL_PREFIX/lib/systemd)
KDE_INSTALL_SYSTEMDUNITDIR:PATH=

//Systemd user units (SYSTEMDUNITDIR/user)
KDE_INSTALL_SYSTEMDUSERUNITDIR:PATH=

//templates (DATAROOTDIR/templates)
KDE_INSTALL_TEMPLATEDIR:PATH=

//Install mkspecs files, QCH files for Qt-based libs, Plugins and
// Imports to the Qt 5 install dir
KDE_INSTALL_USE_QT_SYS_PATHS:BOOL=ON

//desktop wallpaper images (DATAROOTDIR/wallpapers)
KDE_INSTALL_WALLPAPERDIR:PATH=

//Zsh functions and autocompletion definitions (DATAROOTDIR/zsh/site-functions)
KDE_INSTALL_ZSHAUTOCOMPLETEDIR:PATH=

//Prevent an "uninstall" target from being generated.
KDE_SKIP_UNINSTALL_TARGET:BOOL=OFF

//Tool to serialize resource-intensive commands in parallel builds
KDOCTOOLS_SERIALIZE_TOOL:STRING=

//The directory containing a CMake configuration file for KF5Archive.
KF5Archive_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/KF5Archive

//The directory containing a CMake configuration file for KF5Attica.
KF5Attica_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/KF5Attica

//The directory containing a CMake configuration file for KF5Auth.
KF5Auth_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/KF5Auth

//The directory containing a CMake configuration file for KF5Bookmarks.
KF5Bookmarks_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/KF5Bookmarks

//The directory containing a CMake configuration file for KF5Codecs.
KF5Codecs_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/KF5Codecs

//The directory containing a CMake configuration file for KF5Completion.
KF5Completion_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/KF5Completion

//The directory containing a CMake configuration file for KF5ConfigWidgets.
KF5ConfigWidgets_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/KF5ConfigWidgets

//The directory containing a CMake configuration file for KF5Config.
KF5Config_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/KF5Config

//The directory containing a CMake configuration file for KF5CoreAddons.
KF5CoreAddons_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/KF5CoreAddons

//The directory containing a CMake configuration file for KF5Crash.
KF5Crash_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/KF5Crash

//The directory containing a CMake configuration file for KF5DocTools.
KF5DocTools_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/KF5DocTools

//The directory containing a CMake configuration file for KF5I18n.
KF5I18n_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/KF5I18n

//The directory containing a CMake configuration file for KF5IconThemes.
KF5IconThemes_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/KF5IconThemes

//The directory containing a CMake configuration file for KF5ItemViews.
KF5ItemViews_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/KF5ItemViews

//The directory containing a CMake configuration file for KF5JobWidgets.
KF5JobWidgets_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/KF5JobWidgets

//The directory containing a CMake configuration file for KF5KIO.
KF5KIO_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/KF5KIO

//The directory containing a CMake configuration file for KF5NewStuffCore.
KF5NewStuffCore_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/KF5NewStuffCore

//The directory containing a CMake configuration file for KF5NewStuffQuick.
KF5NewStuffQuick_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/KF5NewStuffQuick

Bug#1070895: boxbackup: FTBFS: ERROR: SSL or crypto error: connecting: error:0A000086:SSL routines::certificate verify failed

[Santiago Vila]

Package: src:boxbackup
Version: 0.13~~git20231028.g3dd5194+ds-2
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary
   dh_update_autotools_config
cp: warning: behavior of -n is non-portable and may change in future; use 
--update=none instead
cp: warning: behavior of -n is non-portable and may change in future; use 
--update=none instead
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
echo "0.13~~git20231028.g3dd5194+ds-2" > VERSION.txt
echo "boxbackup" >> VERSION.txt
sh -x ./bootstrap
+ aclocal -I infrastructure/m4
+ autoheader
+ autoconf
configure.ac:12: warning: The macro `AC_CANONICAL_SYSTEM' is obsolete.

[... snipped ...]



== test_compare_detects_attribute_changes ==
WARNING: SSLSecurityLevel set very low (0-1). Your connection may not be 
secure. See https://bit.ly/sslseclevel
NOTICE:  skipping test on this platform
Waiting for server to die (pid 1933959): . done.
NOTICE:  test_compare_detects_attribute_changes passed


== test_sync_new_files ==
WARNING: SSLSecurityLevel set very low (0-1). Your connection may not be 
secure. See https://bit.ly/sslseclevel
WARNING: location path is not absolute: testfiles/TestDir1
WARNING: location path is not absolute: testfiles/TestDir1
WARNING: location path is not absolute: testfiles/TestDir1
WARNING: SSLSecurityLevel set very low (0-1). Your connection may not be 
secure. See https://bit.ly/sslseclevel
WARNING: Failed to determine the time of the last synchronisation -- checks not 
performed.
Waiting for server to die (pid 1933985): . done.
NOTICE:  test_sync_new_files passed


== test_rename_operations ==
WARNING: SSLSecurityLevel set very low (0-1). Your connection may not be 
secure. See https://bit.ly/sslseclevel
WARNING: location path is not absolute: testfiles/TestDir1
WARNING: SSLSecurityLevel set very low (0-1). Your connection may not be 
secure. See https://bit.ly/sslseclevel
WARNING: Failed to determine the time of the last synchronisation -- checks not 
performed.
WARNING: location path is not absolute: testfiles/TestDir1
WARNING: SSLSecurityLevel set very low (0-1). Your connection may not be 
secure. See https://bit.ly/sslseclevel
WARNING: Failed to determine the time of the last synchronisation -- checks not 
performed.
WARNING: SSLSecurityLevel set very low (0-1). Your connection may not be 
secure. See https://bit.ly/sslseclevel
WARNING: Failed to determine the time of the last synchronisation -- checks not 
performed.
WARNING: Quick compare used -- file attributes are not checked.
WARNING: location path is not absolute: testfiles/TestDir1
WARNING: SSLSecurityLevel set very low (0-1). Your connection may not be 
secure. See https://bit.ly/sslseclevel
WARNING: Failed to determine the time of the last synchronisation -- checks not 
performed.
Waiting for server to die (pid 1934065): . done.
NOTICE:  test_rename_operations passed


== test_sync_files_with_timestamps_in_future ==
WARNING: SSLSecurityLevel set very low (0-1). Your connection may not be 
secure. See https://bit.ly/sslseclevel
WARNING: location path is not absolute: testfiles/TestDir1
WARNING: location path is not absolute: testfiles/TestDir1
WARNING: Some files have modification times excessively in the future. Check 
clock synchronisation. Example file (only one shown): 
testfiles/TestDir1/sub23/in-the-future
WARNING: SSLSecurityLevel set very low (0-1). Your connection may not be 
secure. See https://bit.ly/sslseclevel
WARNING: Failed to determine the time of the last synchronisation -- checks not 
performed.
Waiting for server to die (pid 1934170): . done.
NOTICE:  test_sync_files_with_timestamps_in_future passed


== test_changing_client_store_marker_pauses_daemon ==
WARNING: SSLSecurityLevel set very low (0-1). Your connection may not be 
secure. See https://bit.ly/sslseclevel
WARNING: SSLSecurityLevel set very low (0-1). Your connection may not be 
secure. See https://bit.ly/sslseclevel
WARNING: SSLSecurityLevel set very low (0-1). Your connection may not be 
secure. See https://bit.ly/sslseclevel
WARNING: SSLSecurityLevel set very low (0-1). Your connection may not be 
secure. See https://bit.ly/sslseclevel
Waiting for server to die (pid 1934275): . done.
Waiting for server to die (pid 1934257): . done.
NOTICE:  test_changing_client_store_marker_pauses_daemon passed


== test_interrupted_restore_can_be_recovered ==
WARNING: SSLSecurityLevel set very low (0-1). Your connection may not be 
secure. See https://bit.ly/sslseclevel
WARNING: location path is not absolute: testfiles/TestDir1
WARNING: SSLSecurityLevel set very low (0-1). Your connection may not be 
secure. See https://bit.ly/sslseclevel
.
WARNING: SSLSecurityLevel set very low (0-1). Your connection may not be 
secure. See https://bit.ly/sslseclevel
WARNING: Failed to determine the time of the 

Bug#1070893: software-properties-gtk: SyntaxError warning with installing the package

[Sven Geuer]

Package: software-properties-gtk
Version: 0.99.30-4
Severity: normal
Tags: upstream

Dear Maintainer,


installing software-properties-gtk today per aptitude caused the
following warning message:

software-properties-gtk (0.99.30-4) wird eingerichtet ...
/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogMirror.py:197: 
SyntaxWarning: invalid escape sequence '\.'
  elif 
re.match("^((ftp)|(http)|(file)|(rsync)|(https))://([a-z]|[A-Z]|[0-9]|:|/|\.|~)+$",
 uri) == None:

It seems the installation completed successfully regardless.

Still this should be fixed, IMHO.


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.7.12-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages software-properties-gtk depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4+b2
ii  gir1.2-goa-1.0   3.50.1-1
ii  gir1.2-gtk-3.0   3.24.41-4
ii  gir1.2-handy-1   1.8.3-1+b1
ii  libgtk3-perl 0.038-3
ii  python3  3.11.8-1
ii  python3-dateutil 2.9.0-2
ii  python3-distro-info  1.7
ii  python3-gi   3.48.2-1
ii  python3-software-properties  0.99.30-4
ii  software-properties-common   0.99.30-4

Versions of packages software-properties-gtk recommends:
ii  gnome-keyring  46.1-2
ii  gnome-session-bin  46.0-2

Versions of packages software-properties-gtk suggests:
ii  gnome-software  46.1-1

-- no debconf information

-- 
GPG Fingerprint
3DF5 E8AA 43FC 9FDF D086 F195 ADF5 0EDA F8AD D585


signature.asc
Description: This is a digitally signed message part

Bug#1070727: reportbug: podman does not run wasm/wasi images because of missing crun-wasm - easy fix

[Faidon Liambotis]

Control: tags -1 confirmed

On Wed, May 08, 2024 at 03:10:40AM +0300, Eugen Stan wrote:
> I followed the guide to run wasm images on my system and it failed with
> errors.
> 
> I believe the issue is that podman looks for crun-wasm binary by default.
> I failed to configure podman to use crun instead of crun-wasm.
> I created a simbolic link named crun-wasm:
> 
> sudo ln -s /usr/bin/crun /usr/local/bin/crun-wasm

Ouch! You're right. This worked when I enabled WasmEdge in crun, but
was changed upstream at some point since.

Apparently Fedora/RedHat ship a "crun-wasm" package, which contains a) this
symlink, b) a dependency on WasmEdge.

In Debian, the main "crun" package has a Suggests on libwasmedge0.

I see three paths forward:
1) We do the same, creating a new (almost) empty package.
2) We ship a /usr/bin/crun-wasm symlink in the crun package.
3) We patch podman to use /usr/bin/crun instead of, or in addition to,
/usr/bin/crun-wasm.

I don't particularly love option (1). I'm split between options (2) and
(3), not loving either.

Thoughts?

Faidon

Bug#1070891: apt-show-versions: Permission denied on a bad pathname

[Vincent Lefevre]

Package: apt-show-versions
Version: 0.22.15
Severity: normal

When running "apt-show-versions -u" in a cron script, I got

Failed to open file 
/var/lib/apt/lists//debug.mirrors.debian.org_debian-debug_dists_stable-debug_InRelease
 for reading: Permission denied

I don't know why could cause the error, but the pathname with "//"
is incorrect.

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), 
(500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.7.12-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages apt-show-versions depends on:
ii  apt  2.9.2
ii  libapt-pkg-perl  0.1.40+b5
ii  perl [libstorable-perl]  5.38.2-4

apt-show-versions recommends no packages.

apt-show-versions suggests no packages.

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1070892: abiword: Please use pkg-config instead of libgcrypt-config to locate libgcrypt

[Andreas Metzler]

Source: abiword
Version: 3.0.5~dfsg-3.2
Severity: normal
Tags: patch
User: ametz...@debian.org
Usertags: libgcrypt-config-removal
Control: block 714589 by -1

Hello,

Please switch from using libgcrypt-config to pkg-config to locate
libgcrypt. libgcrypt-config will be dropped in the next libgcrypt major
release.

Upstream's AM_PATH_LIBGCRYPT() nowadays uses gpgrt-config iff
AM_PATH_GPG_ERROR() is also used. However a) abiword ships an old copy of
libgcrypt.m4 so the newer code is not used by autoreconf and b) abiword
does not use AM_PATH_GPG_ERROR(). Find attached a trivial patch to
simply switch to pkg-config (which is a lot faster than gpgrt-config.)

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
Description: Use pkg-config to locate gcrypt
 abiword has an old copy AM_PATH_LIBGCRYPT that alsways uses libgcrypt-config.
 Newer versions of that macro would use gpgrt-config when used with
 AM_PATH_GPG_ERROR() which abiword does not.
 pkgconf does the same job faster.
Author: Andreas Metzler 
Origin: vendor
Last-Update: 2024-05-11

--- a/configure.ac
+++ b/configure.ac
@@ -982,19 +982,16 @@ fi
 AM_CONDITIONAL(DEBUG, test "$abi_cv_debug" = "yes")
 
 #
 # Optional dependencies handling
 #
-AM_PATH_LIBGCRYPT( 1.4.5,
-		   [
-		   abi_cv_gcrypt=no
- 		   AC_DEFINE([HAVE_GCRYPT], [1], [Use gcrypt for the cryptos])
-		   ],
-		   [
-		   abi_cv_gcrypt=yes
-		   ] )
-AM_CONDITIONAL(HAVE_GCRYPT, test "$abi_cv_gcrypt" = "yes")
+PKG_CHECK_MODULES([LIBGCRYPT], [libgcrypt >= 1.4.5],
+	   [AC_DEFINE([HAVE_GCRYPT], [1], [Use gcrypt for the cryptos])]
+	   gcryptfound="yes",
+	   [AC_MSG_NOTICE([gcrypt not found])]
+	   gcryptfound="no")
+AM_CONDITIONAL(HAVE_GCRYPT, test "$gcryptfound" = "yes")
 
 if test "$abi_cv_gnomevfs" = "yes"; then 	 
 AC_DEFINE([WITH_GNOMEVFS], [1], [Define if using gnome-vfs]) 	 
 fi 	 
 	

Bug#698493: vym: cannot undo accidental removal of the root node

[Sven Hoexter]

Hi,
I can not reproduce the issue with the latest vym release. Removing and 
restoring via
undo seems to work just fine in new documents.

Can you confirm that as well?

Sven

Bug#1063004: synfig: NMU diff for 64-bit time_t transition

[Rodolfo Ribeiro Gomes]

Now imagemagick migrated to Testing [1] with t64 support, maybe your patch
now works for Synfig?

[1]
https://tracker.debian.org/news/1525573/imagemagick-8691298dfsg1-52-migrated-to-testing/

Bug#1069083: RFS: runit-services/0.7.2 -- UNIX init scheme with service supervision (services)

[Martin Steigerwald]

Hi Tobias, hi Lorenzo.

Tobias, thanks for looking into this sponsoring request! I appreciate it.

Tobias Frost - 11.05.24, 10:24:31 CEST:
> On Tue, Apr 16, 2024 at 09:39:58AM +0200, Lorenzo wrote:
> > Control: block -1 by 1067525
> > 
> > this fix need to go to unstable because elogind 255.4.1 is already
> > there, but runit-services depends on runit > 2.1.2-56 (unstable is at
> > 2.1.2-54) so 1067525 needs to be uploaded first or together with this
> > one, otherwise runit-services is not installable
> 
> Ok, just saw that one.
> Please note that this fact must be stated in d/changelog, something like
> "Upload to unstable."

FWIW I run runit 2.1.2-59 and runit-services together with elogind 255.5-2 
on two Devuan Ceres systems with KDE's Plasma desktop. One I had patched 
manually, but I made sure the package version of the run dir for elogind 
was installed after the upgrade. The other one was upgraded regularly from 
elogind 252 and older runit / runit-services packages.

Runsvdir starts elogind correctly from the new path. I also reviewed the 
changes to the package for the updated path for elogind and I think they 
are correct. I am certainly no expert with runit, but as I contributed 
zcfan service dir at least I know something.

Devuan uses the upstream packages for runit, runit-services, dash, bash so 
I expect that runit-services 0.7.2 will work just fine on Debian, too. It 
would unbreak running elogind for runit users that did not patch their 
systems manually already. I bet most of them did by now, as many desktop 
environments do not work well, if at all, without some systemd-logind 
replacement. And the timeouts with login into a TTY or SSH session without 
some systemd-logind replacement are quite annoying as well. Sure we are 
still talking about a (small) minority of Debian users here.

Hope this helps regarding the review of the package and the sponsoring. In 
case any further changes need to be tested before upload, I am willing to 
do that.

Best,
-- 
Martin

Bug#1070890: qabc: [src:qabc] VCS-* in d/control is not pointing to the packaging repository

[Tobias Frost]

Source: qabc
Severity: minor

Dear Maintainer,

during review I've seen that VCS-* is pointing to the upstream repo,
according to Policy §5.6.26 "The purpose of the following fields is to
indicate a publicly accessible repository where the Debian source
package is developed." -- IOW where the debian package is maintained.

(It seems you are just missing to sepcify the branch, see Policy for
details how to do that.)

-- 
tobi

Bug#1068922: runit-init: configuring network interfaces at boot inside LXC with runit as init system fails

[Martin Steigerwald]

Hi Lorenzo.

Lorenzo - 11.05.24, 02:16:15 CEST:
> On Tue, 07 May 2024 15:08:37 +0200
> Martin Steigerwald  wrote:
> >[...]
> > Are init scripts supposed to be started with PATH variable set up and
> > exported or not? How is it done with SysVInit? I bet it would be best
> > to match as close as possible what SysVInit is doing to be as
> > compatible as possible.
> 
> I checked this and in sysvinit you don't have this bug because during
> boot sysvscripts are run via /etc/ini.d/rc script, and there is an
> 'export PATH' there. It could probably be triggered by calling the
> script directly during runtime.
> In runit we are calling scripts directly in stage1 so we have this bug

I see. 

> > Otherwise it might be challenging to chase and find all the corner
> > cases with existing setups. And as there is no issue initializing the
> > network in the container with SysVInit instead of Runit used as PID
> > 1, I'd consider a change in Runit. At least it could be challenging
> > to find whether networking inside a container is the only thing that
> > breaks.
> 
> I want to dig this further, I don't recall broken network under docker
> and I don't think is broken under qemu, but I can be wrong or remember
> something from before /etc/init.d/rc usage was dropped from stage1

Could have something to do with Incus / LXD then. I used Incus in Devuan 
testing (upcoming Excalibur), which is based on Debian testing (upcoming 
Trixie).

In case it is helpful for you I could post a step to step guide for a 
minimal Incus setup and/or at least some pointers.

> > > > I just wonder why stage 2 contains /usr/local bin directories. I
> > > > think that should not be the case. Shall I report this as a
> > > > different issue?
> > > 
> > > PATH is passed to env call for runsvdir, so I guess one can exec a
> > > bin from local as runscript (not sure) without setting the PATH. I
> > > can't think of other use cases..
[…]
> > Hmm, I get that. I am just a bit concerned as it may be a security
> > issue.
> 
> not urgent, but could you elaborate this (security implications)? is
> something like an attacker placing a modified foo in /usr/local/ that
> overrides the legit foo in /usr/bin or is something else? one still
> needs root privileges to write to /usr/local..

Good question. It is how I learned it. :)

Yes, usually /usr/local is only writable by root, however… maybe an admin 
or user with root privileges put some own version of say coreutils or 
whatever in there for whatever reason and forgot about it. And later on it 
has some security whole that remains unpatched. With

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/sbin:/usr/bin:/bin

a vulnerable command might be picked up from /usr/local's s(bin) as it is 
even before the regular system managed (s)bin directories.

Yes, you can consider that an user error, but there might even be other 
scenarios, like an user or admin installed some special version of ls or 
some other command in there as they prefer it. Even if the behavior or 
such a special replacement command is only slightly different than of the 
original system default command it could cause all kinds of trouble.

I believe this may be some of the reasoning behind the rule I learned 
about to only have system directories in PATH for system provided scripts 
and programs. It at least appears to me like the approach of least 
surprise. /usr/local, only root-writable or not, is user managed. There 
could be anything in there causing all kinds of various trouble.

A compromise here would be to change the path like this:

PATH=/usr/sbin:/sbin:/usr/bin:/bin:/usr/local/sbin:/usr/local/bin

With that order at least a modified "ls" from /usr/local/bin would not be 
picked up as there is a system managed one available. But a command that 
is not available in system managed directories would still be picked up 
from /usr/local directories.

As one point of practical experience, I changed path to

PATH=/sbin:/usr/sbin:/bin:/usr/bin

in one Incus managed Devuan container which runs a Wordpress blog on 
Apache and PHP FPM and I see no issues. However as I also don't have 
anything in /usr/local that is to be expected. One approach could be to 
just change the path to the above system managed directories only path, 
add some NEWS.Debian entry about it and see whether someone complains :)

I do think this discussion belongs into a different bug report though. I am 
willing to open a low priority report about this and include the previous 
relevant discussion to it, so it does not get lost and you can take your 
time to ponder about it. There is no need to rush it.

Have a great weekend!
-- 
Martin

Bug#1069620: RFS: lua-mode/20231023~git-1 -- Emacs major-mode for editing Lua programs

[Tobias Frost]

Hi Xiyue,

when packaging a git snapshot, I feel this should be indicated in the
upstream version that it is based on the old one, something like
+

In your case I'd 20210802+git20231023 as upstream version.

Long time ago I did something like that for dhewm3, you 
can see the watch file here:
https://salsa.debian.org/games-team/dhewm3/-/blob/debian/1.5.0+git20181221+dfsg-1/debian/watch?ref_type=tags

(not marking moreinfo, as other people might see that differently.)

--
tobi

On Sun, Apr 21, 2024 at 10:02:48AM -0700, Xiyue Deng wrote:
> Package: sponsorship-requests
> Severity: normal
> 
> Dear mentors,
> 
> I am looking for a sponsor for my package "lua-mode":
> 
>  * Package name : lua-mode
>Version  : 20231023~git-1
>Upstream contact : immerrr 
>  * URL  : https://github.com/immerrr/lua-mode
>  * License  : GPL-3+
>  * Vcs  : https://salsa.debian.org/emacsen-team/lua-mode
>Section  : lisp
> 
> The source builds the following binary packages:
> 
>   elpa-lua-mode - Emacs major-mode for editing Lua programs
> 
> To access further information about this package, please visit the following 
> URL:
> 
>   https://mentors.debian.net/package/lua-mode/
> 
> Alternatively, you can download the package with 'dget' using this command:
> 
>   dget -x 
> https://mentors.debian.net/debian/pool/main/l/lua-mode/lua-mode_20231023~git-1.dsc
> 
> Changes since the last upload:
> 
>  lua-mode (20231023~git-1) unstable; urgency=medium
>  .
>* Sync to latest upstream snapshot (d074e41)
>* Drop the patch applied upstream and reorder the remaining patch
>* Update upstream license to GPL-3+ following upstream change
>* Add a missing upstream copyright holder
> 
> Regards,
> -- 
> Xiyue Deng
> 

Bug#1067842: transition: octave-9

[Sébastien Villemot]

Hi Graham,

Le vendredi 10 mai 2024 à 09:57 +, Graham Inggs a écrit :
> On Thu, 9 May 2024 at 08:09, Sebastian Ramacher  wrote:
> > plplot is involved in the gnat and octave transitions. So let's do this
> > one after gnat is done.
> 
> gnat 13 has migrated, please go ahead.

Thanks. Uploaded and built on all release architectures.

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
⠈⠳⣄  https://www.debian.org




signature.asc
Description: This is a digitally signed message part

Bug#1070889: aptitude: bind() buggy

[Wu Shunchao]

Package: aptitude
Version: 0.8.13-6
Severity: important
X-Debbugs-Cc: infoa...@qq.com

search pattern
  " ^libc6$ ?for x: ?depends( ?for y: ?depends( ?=x ) ) "
will match libc6,

but after bind() added, the pattern
  " ^libc6$ ?for x: ?depends( ?for y: ?y:depends( ?=x ) ) "
returns nothing.

And Example 2.3 & 2.5 on page "Search term reference" behave the same.
https://www.debian.org/doc/manuals/aptitude/ch02s04s05.en.html

I think there's a bug somewhere.

-- Package-specific info:
Terminal: linux
$DISPLAY not set.
which aptitude: /usr/bin/aptitude

aptitude version information:
aptitude 0.8.13
Compiler: g++ 13.2.0
Compiled against:
  apt version 6.0.0
  NCurses version 6.4
  libsigc++ version: 2.12.1
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.4.20240414
  cwidget version: 0.5.18
  Apt version: 6.0.0

aptitude linkage:
linux-vdso.so.1 (0x711f4000)
libapt-pkg.so.6.0 => /lib/x86_64-linux-gnu/libapt-pkg.so.6.0 
(0x7f71d180)
libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6 
(0x7f71d2162000)
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 
(0x7f71d212d000)
libsigc-2.0.so.0 => /lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7f71d2124000)
libcwidget.so.4 => /lib/x86_64-linux-gnu/libcwidget.so.4 
(0x7f71d1afe000)
libsqlite3.so.0 => /lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7f71d168a000)
libboost_iostreams.so.1.83.0 => 
/lib/x86_64-linux-gnu/libboost_iostreams.so.1.83.0 (0x7f71d2108000)
libxapian.so.30 => /lib/x86_64-linux-gnu/libxapian.so.30 
(0x7f71d140)
libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f71d100)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f71d1321000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f71d20db000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f71d0e1c000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f71d20ba000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7f71d20a7000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f71d2077000)
liblz4.so.1 => /lib/x86_64-linux-gnu/liblz4.so.1 (0x7f71d2051000)
libzstd.so.1 => /lib/x86_64-linux-gnu/libzstd.so.1 (0x7f71d0d5b000)
libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x7f71d1acb000)
libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 
(0x7f71d0c79000)
libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 
(0x7f71d0b31000)
libxxhash.so.0 => /lib/x86_64-linux-gnu/libxxhash.so.0 
(0x7f71d1ab8000)
/lib64/ld-linux-x86-64.so.2 (0x7f71d21a4000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7f71d1aae000)
libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x7f71d1aa2000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 
(0x7f71d1a79000)

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.7.12-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages aptitude depends on:
ii  aptitude-common   0.8.13-6
ii  libapt-pkg6.0t64  2.9.2
ii  libboost-iostreams1.83.0  1.83.0-2.1+b1
ii  libc6 2.38-7
ii  libcwidget4   0.5.18-6+b1
ii  libgcc-s1 14-20240330-1
ii  libncursesw6  6.4+20240414-1
ii  libsigc++-2.0-0v5 2.12.1-2
ii  libsqlite3-0  3.45.3-1
ii  libstdc++614-20240330-1
ii  libtinfo6 6.4+20240414-1
ii  libxapian30   1.4.25-1

Versions of packages aptitude recommends:
ii  libdpkg-perl1.22.6
ii  sensible-utils  0.0.22

Versions of packages aptitude suggests:
pn  apt-xapian-index
pn  aptitude-doc-en | aptitude-doc  
pn  debtags 
ii  tasksel 3.75

-- no debconf information

Bug#1068724: RFS: gensync/2.0.5-1 [ITP] -- a library for efficient synchronization of data over a network.

[Tobias Frost]

Control: reopen -1
Control: forcemerge 1069696 -1

Hi Chen,

In future, please do not file new RFS bugs, instead modify the existing
one until a package has been sponsored.

(forcemerge: FTR, the new one is #1069696, let that one be the leading one)

-- 
tobi


On Tue, Apr 09, 2024 at 06:53:58PM +, Chen, Xingyu wrote:
> Package: sponsorship-requests
> Severity: wishlist
> 
> Dear mentors,
> 
> I am looking for a sponsor for my package "gensync":
> 
>  * Package name : gensync
>Version  : 2.0.5-1
>Upstream contact :  project>
>  * URL  : https://github.com/nislab/gensync
>  * License  : 
>  * Vcs  : [fill in URL of packaging vcs]
>Section  : libs
> 
> The source builds the following binary packages:
> 
>   gensync - a library for efficient synchronization of data over a network. 
> Gensync is a library that uses many different syncing algorithms to sync data 
> between two nodes in a network. These algorithms include IBLTs, CPISyncs, 
> HashSyncs, Cuckoo Syncs, and more.
> 
> To access further information about this package, please visit the following 
> URL:
> 
>   https://mentors.debian.net/package/gensync/
> 
> Alternatively, you can download the package with 'dget' using this command:
> 
>   dget -x 
> https://mentors.debian.net/debian/pool/main/g/gensync/gensync_2.0.5-1.dsc
> 
> Changes for the initial release:
> 
>  gensync (2.0.5-1) UNRELEASED; urgency=medium
>  .
>* Initial release (Closes: #)  
> 
> Regards,
> --
>   Kevin Chen
> 

Bug#1069083: RFS: runit-services/0.7.2 -- UNIX init scheme with service supervision (services)

[Tobias Frost]

On Tue, Apr 16, 2024 at 09:39:58AM +0200, Lorenzo wrote:
> Control: block -1 by 1067525
> 
> this fix need to go to unstable because elogind 255.4.1 is already
> there, but runit-services depends on runit > 2.1.2-56 (unstable is at
> 2.1.2-54) so 1067525 needs to be uploaded first or together with this
> one, otherwise runit-services is not installable

Ok, just saw that one.
Please note that this fact must be stated in d/changelog, something like
"Upload to unstable."

-- 
tobi

> On Tue, 16 Apr 2024 09:30:08 +0200 Lorenzo  wrote:
> > Package: sponsorship-requests
> > Severity: normal
> > 
> > Dear mentors,
> > 
> > I am looking for a sponsor for my package "runit-services":
> > 
> >  * Package name : runit-services
> >Version  : 0.7.2
> >Upstream contact : [fill in name and email of upstream]
> >  * URL  : [fill in URL of upstream's web site]
> >  * License  : BSD-3-Clause, GPL-2.0+, GPL-3+, CC0-1.0
> >  * Vcs  :
> >https://salsa.debian.org/Lorenzo.ru.g-guest/runit-services Section
> >   : admin
> > 
> > The source builds the following binary packages:
> > 
> >   runit-services - UNIX init scheme with service supervision
> > (services)
> > 
> > To access further information about this package, please visit the
> > following URL:
> > 
> >   https://mentors.debian.net/package/runit-services/
> > 
> > Alternatively, you can download the package with 'dget' using this
> > command:
> > 
> >   dget -x
> >   
> > https://mentors.debian.net/debian/pool/main/r/runit-services/runit-services_0.7.2.dsc
> > 
> > Git repo:
> >   
> > https://salsa.debian.org/Lorenzo.ru.g-guest/runit-services/-/tree/next?ref_type=heads
> > 
> > Changes since the last upload:
> > 
> >  runit-services (0.7.2) unstable; urgency=medium
> >  .
> >* Fix elogind service (Closes: #1069075)
> > 
> > Regards,
> > Lorenzo
> > 
> > 
> 

Bug#1069083: RFS: runit-services/0.7.2 -- UNIX init scheme with service supervision (services)

[Tobias Frost]

Control: tags -1 moreinfo

Hi Lorenzo,

the last uploads where to experimental, this one targets unstable but
that is not mentioned in the changelog, so I guess this was accidential?

-- 
tobi

On Tue, Apr 16, 2024 at 09:30:08AM +0200, Lorenzo wrote:
> Package: sponsorship-requests
> Severity: normal
> 
> Dear mentors,
> 
> I am looking for a sponsor for my package "runit-services":
> 
>  * Package name : runit-services
>Version  : 0.7.2
>Upstream contact : [fill in name and email of upstream]
>  * URL  : [fill in URL of upstream's web site]
>  * License  : BSD-3-Clause, GPL-2.0+, GPL-3+, CC0-1.0
>  * Vcs  :
>https://salsa.debian.org/Lorenzo.ru.g-guest/runit-services Section
>   : admin
> 
> The source builds the following binary packages:
> 
>   runit-services - UNIX init scheme with service supervision (services)
> 
> To access further information about this package, please visit the
> following URL:
> 
>   https://mentors.debian.net/package/runit-services/
> 
> Alternatively, you can download the package with 'dget' using this
> command:
> 
>   dget -x
>   
> https://mentors.debian.net/debian/pool/main/r/runit-services/runit-services_0.7.2.dsc
> 
> Git repo:
>   
> https://salsa.debian.org/Lorenzo.ru.g-guest/runit-services/-/tree/next?ref_type=heads
> 
> Changes since the last upload:
> 
>  runit-services (0.7.2) unstable; urgency=medium
>  .
>* Fix elogind service (Closes: #1069075)
> 
> Regards,
> Lorenzo
> 

Bug#1069696: RFS: gensync/2.0.5-1 [ITP] -- a library for efficient synchronization of data over a network.

[Tobias Frost]

Control: tags -1 moreinfo

Hi Chen,

please take a look at [1] -- the page indicates a lots of problems
with your package, especially the lintian errors, warnings and
informational tags. That means your package is not yet ready to
be reviewed in depth.

Please fix those linitian erros, then remove the moreinfo tag.
 
As you seems to be upstream, please read https://wiki.debian.org/UpstreamGuide

Cheers,
-- 
tobi



[1] https://mentors.debian.net/package/gensync/


On Mon, Apr 22, 2024 at 09:43:03PM +, Chen, Xingyu wrote:
> Package: sponsorship-requests
> Severity: wishlist
> 
> Dear mentors,
> 
> I am looking for a sponsor for my package "gensync":
> 
>  * Package name : gensync
>Version  : 2.0.5-1
>Upstream contact : Kevin Chen 
>  * URL  : https://github.com/nislab/gensync-lib
>  * License  : GPL
>  * Vcs  :
>Section  : libs
> 
> The source builds the following binary packages:
> 
>   gensync - a library for efficient synchronization of data over a network. 
> Gensync is a library that uses many different syncing algorithms to sync data 
> between two nodes in a network. These algorithms include IBLTs, CPISyncs, 
> HashSyncs, Cuckoo Syncs, and more.
> 
> To access further information about this package, please visit the following 
> URL:
> 
>   https://mentors.debian.net/package/gensync/
> 
> Alternatively, you can download the package with 'dget' using this command:
> 
>   dget -x 
> https://mentors.debian.net/debian/pool/main/g/gensync/gensync_2.0.5-1.dsc
> 
> Changes for the initial release:
> 
>  gensync (2.0.5-1) UNRELEASED; urgency=medium
>  .
>* Initial release (Closes: #1069684)  
> 
> Regards,
> --
>   Kevin Chen
> 
> 

Bug#1070869: libpam-modules: pam_lastlog.so does not exist

[Francois Mescam]

I've tried again to login root on a virtual console. Every login produce 
the logs in auth.log.


Thanks for your help

--
Francois

Bug#1070888: libreoffice-base: Since 2024-05-10, testing's libreoffice crashes when opening an sqlite-ODBC database.

[Emmanuel Charpentier]

Package: libreoffice-base  
Version: 4:24.2.3-1  
Severity: important

Dear Maintainer,

Setup : Debian testing running on core i7 + 16 GB RAM, *updated daily.*

I use libreoffice-base to update *daily* a small sqlite database accessed via  
an ODBC link.

This setup has been stable for more than 3 years. I usually start my daily  
update by opening Libreoffice's main interface, then opening the relevant  
database object in this interface, then opening the relevant form.

Starting today :

 - libreoffice crashed when opening the database object in the main  
libreoffice interface.

 - Starting libreoffice from a command line leads to the same result, with  
no error message in the console.

    - Starting directly `lobase` from the command line opens the dialog box  
allowing to select the right (existing) database, then fails, opening a message 
 
box mentioning the crash and displaying an empty list  of files to be recovered 
 
; clicking "OK" leads to the main Libreoffice interface. Trying again to open  
the database objects crashes libreoffice. *No error message in the terminal.*

    - Same behaviour when passing the `.odb` database file as an argument to  
`lobase`.

FWIW :

```
[charpent@zen-book-flip](mailto:charpent@zen-book-flip):~$ dpkg -l 
"*libreoffice*base*" | cat  
Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder  
| État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-  
installé/W=attend-traitement-déclenchements  
|/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais)  
||/ Nom   Version  Architecture Description  
+++-=---=
  
ii  libreoffice-base  4:24.2.3-1   amd64    office productivity  
suite -- database  
ii  libreoffice-base-core 4:24.2.3-1   amd64    office productivity  
suite -- shared library  
ii  libreoffice-base-drivers  4:24.2.3-1   amd64    Database connectivity  
drivers for LibreOffice  
un  libreoffice-base-nogui      (aucune description  
n'est disponible)  
ii  libreoffice-uiconfig-base 4:24.2.3-1   all  UI data ("config") for  
LibreOffice Base

```

HTH,


-- Package-specific info:  
Configuration file    Package Exists 
Changed  
/etc/libreoffice/registry/base.xcd    libreoffice-base    Yes No  
All deployed bundled extensions:

Identifier: com.sun.wiki-publisher  
  Version: 1.2.0  
  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher  
  is registered: yes  
  Media-Type: application/vnd.sun.star.package-bundle  
  Description: Le Wiki Publisher vous permet de cr\xe9er des articles de Wiki 
sur un serveur MediaWiki sans avoir \xe0 conna\xeetre la syntaxe du langage 
markup Mediawiki. Publiez de nouveaux documents ou des documents existants de 
fa\xe7on transparente depuis Writer vers une page de wiki.

  bundled Packages: {  
  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/help  
  is registered: yes  
  Media-Type: application/vnd.sun.star.help  
  Description:

  URL: 
vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/WikiExtension.xcs  
  is registered: yes  
  Media-Type: application/vnd.sun.star.configuration-schema  
  Description:

  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/WikiEditor/  
  is registered: yes  
  Media-Type: application/vnd.sun.star.basic-library  
  Description:

  URL: 
vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/components.rdb  
  is registered: yes  
  Media-Type: application/vnd.sun.star.uno-components  
  Description:

  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/Addons.xcu  
  is registered: yes  
  Media-Type: application/vnd.sun.star.configuration-data  
  Description:

  URL: 
vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/ProtocolHandler.xcu  
  is registered: yes  
  Media-Type: application/vnd.sun.star.configuration-data  
  Description:

  URL: 
vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/WikiExtension.xcu  
  is registered: yes  
  Media-Type: application/vnd.sun.star.configuration-data  
  Description:

  URL: 
vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/OptionsDialog.xcu  
  is registered: yes  
  Media-Type: application/vnd.sun.star.configuration-data  
  Description:

  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/Filter.xcu  
  is registered: yes  
  Media-Type: application/vnd.sun.star.configuration-data  
  Description:

  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/Types.xcu  
  is registered: yes  
  Media-Type: application/vnd.sun.star.configuration-data  
  Description:

  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/Paths.xcu  
  is registered: yes  
  

Bug#1069942: RFS: imsprog/1.3.7-1 -- Linux chip programmer for CH341a devices

[Tobias Frost]

Control: tags -1 moreinfo

Hi Mikhail,

Thanks for the update. There is one thing I'd like to fixed:
The qm language files needs to be recreated at build time.

As you are upstream, you can incoorporate that change upstream
(and drop the binary files from your tarball)

There is a spelling error "copyed" in in 99-CH341.rules.

Linitian to be checked (verified and if not a false positive fixed
otherwise overriden)

W: imsprog: appstream-metadata-missing-modalias-provide 
usr/lib/udev/rules.d/99-CH341.rules
(likekly false positive)

I: imsprog: hardening-no-bindnow [usr/bin/IMSProg]
I: imsprog: hardening-no-bindnow [usr/bin/IMSProg_editor]

P: imsprog source: package-uses-old-debhelper-compat-version 12
P: imsprog source: trailing-whitespace [debian/changelog:12]


As you are upstream, please consider signing your tarballs:
X: imsprog source: debian-watch-does-not-check-openpgp-signature [debian/watch]


As you are upstream, you could wrap README.md at 80 chars per line :)
X: imsprog source: very-long-line-length-in-source-file 577 > 512 
[README.md:103]

--
tobi

On Sat, Apr 27, 2024 at 02:19:07PM +0300, Михаил Медведев wrote:
> Package: sponsorship-requests
> Severity: normal
> 
> Dear mentors,
> 
> I am looking for a sponsor for my package "imsprog":
> 
>  * Package name : imsprog
>Version  : 1.3.7-1
>Upstream contact : Mikhail medvedeve-ink-rea...@yandex.ru
>  * URL  :https://github.com/bigbigmdm/IMSProg
>  * License  : GPL-2+, GPL-3+, LGPL-2.1
>  * Vcs  :https://github.com/bigbigmdm/IMSProg/
>Section  : devel
> 
> The source builds the following binary packages:
> 
>   imsprog - Linux chip programmer for CH341a devices
> 
> To access further information about this package, please visit the following 
> URL:
> 
>   https://mentors.debian.net/package/imsprog/
> 
> Alternatively, you can download the package with 'dget' using this command:
> 
>   dget 
> -xhttps://mentors.debian.net/debian/pool/main/i/imsprog/imsprog_1.3.7-1.dsc
> 
> Changes since the last upload:
> 
>  imsprog (1.3.7-1) unstable; urgency=medium
>  .
>* New upstream release
> 
> Regards,
> -- 
>   Mikhail Medvedev

Bug#1070887: libreoffice-base: Since 2024-05-10, testing's libreoffice crashes when opening an sqlite-ODBC database.

[Emmanuel Charpentier]

Package: libreoffice-base
Version: 4:24.2.3-1
Severity: important

Dear Maintainer,

Setup : Debian testing running on core i7 + 16 GB RAM, *updated daily.*

I use libreoffice-base to update *daily* a small sqlite database accessed via
an ODBC link.

This setup has been stable for more than 3 years. I usually start my daily
update by opening Libreoffice's main interface, then opening the relevant
database object in this interface, then opening the relevant form.

Starting today :

 - libreoffice crashed when opening the database object in the main
libreoffice interface.

 - Starting libreoffice from a command line leads to the same result, with
no error message in the console.

- Starting directly `lobase` from the command line opens the dialog box
allowing to select the right (existing) database, then fails, opening a message
box mentioning the crash and displaying an empty list  of files to be recovered
; clicking "OK" leads to the main Libreoffice interface. Trying again to open
the database objects crashes libreoffice. *No error message in the terminal.*

- Same behaviour when passing the `.odb` database file as an argument to
`lobase`.

FWIW :

```
charpent@zen-book-flip:~$ dpkg -l "*libreoffice*base*" | cat
Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder
| État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-
installé/W=attend-traitement-déclenchements
|/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais)
||/ Nom   Version  Architecture Description
+++-=---=
ii  libreoffice-base  4:24.2.3-1   amd64office productivity
suite -- database
ii  libreoffice-base-core 4:24.2.3-1   amd64office productivity
suite -- shared library
ii  libreoffice-base-drivers  4:24.2.3-1   amd64Database connectivity
drivers for LibreOffice
un  libreoffice-base-nogui  (aucune description
n'est disponible)
ii  libreoffice-uiconfig-base 4:24.2.3-1   all  UI data ("config") for
LibreOffice Base

```

HTH,


-- Package-specific info:
Configuration filePackage Exists Changed
/etc/libreoffice/registry/base.xcdlibreoffice-baseYes No
All deployed bundled extensions:

Identifier: com.sun.wiki-publisher
  Version: 1.2.0
  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher
  is registered: yes
  Media-Type: application/vnd.sun.star.package-bundle
  Description: Le Wiki Publisher vous permet de cr\xe9er des articles de Wiki 
sur un serveur MediaWiki sans avoir \xe0 conna\xeetre la syntaxe du langage 
markup Mediawiki. Publiez de nouveaux documents ou des documents existants de 
fa\xe7on transparente depuis Writer vers une page de wiki.

  bundled Packages: {
  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/help
  is registered: yes
  Media-Type: application/vnd.sun.star.help
  Description: 

  URL: 
vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/WikiExtension.xcs
  is registered: yes
  Media-Type: application/vnd.sun.star.configuration-schema
  Description: 

  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/WikiEditor/
  is registered: yes
  Media-Type: application/vnd.sun.star.basic-library
  Description: 

  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/components.rdb
  is registered: yes
  Media-Type: application/vnd.sun.star.uno-components
  Description: 

  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/Addons.xcu
  is registered: yes
  Media-Type: application/vnd.sun.star.configuration-data
  Description: 

  URL: 
vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/ProtocolHandler.xcu
  is registered: yes
  Media-Type: application/vnd.sun.star.configuration-data
  Description: 

  URL: 
vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/WikiExtension.xcu
  is registered: yes
  Media-Type: application/vnd.sun.star.configuration-data
  Description: 

  URL: 
vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/OptionsDialog.xcu
  is registered: yes
  Media-Type: application/vnd.sun.star.configuration-data
  Description: 

  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/Filter.xcu
  is registered: yes
  Media-Type: application/vnd.sun.star.configuration-data
  Description: 

  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/Types.xcu
  is registered: yes
  Media-Type: application/vnd.sun.star.configuration-data
  Description: 

  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/Paths.xcu
  is registered: yes
  Media-Type: application/vnd.sun.star.configuration-data
  Description: 

  }

Identifier: com.sun.star.comp.Calc.NLPSolver
  Version: 0.9
  URL: 

Bug#1032662: elpa-debian-el: deb-view fails on zstd compressed debs

[Xiyue Deng]

Hi Sven,

I'd like to experiment an implementation to add zstd support (as well
as lzma if possible).  Do you know which ubuntu deb files are using zstd
or lzma compressions so that I can use to test?

-- 
Xiyue Deng

Bug#1070886: firefox: crashreporter crashes

[Nicolas Patrois]

Package: firefox
Version: 125.0.3-1+b1
Severity: minor
Tags: upstream

Dear Maintainer,

When I close firefox, it crashes and I see the crashreporter window.
When I send the crash report, it crashes too and I read this in the journal:

[…] kernel: crashreporter[8625]: segfault at acca6c80 ip acca6c80 sp ada0e10c
error 14 in libdbus-glib-1.so.2.3.5[ad099000+6000]
[…] kernel: Code: Unable to access opcode bytes at RIP 0xacca6c56.
[…]
[…] systemd[1]: Started systemd-coredump@8-8662-0.service - Process Core Dump
(PID 8662/UID 0).
[…]
[…] systemd-coredump[8689]: [] Process 8345 (crashreporter) of user 1000
dumped core.

 Module
libnss_myhostname.so.2 from deb systemd-255.5-1.i386
 Module libzstd.so.1 from
deb libzstd-1.5.5+dfsg2-2.i386
 Module libsystemd.so.0
from deb systemd-255.5-1.i386
 Module libblkid.so.1 from
deb util-linux-2.40-8.i386
 Module libmount.so.1 from
deb util-linux-2.40-8.i386
 Stack trace of thread
8625:
 #0  0xacca6c80 n/a
(n/a + 0x0)
 ELF object binary
architecture: Intel 80386
[…]
[…] systemd[1]: systemd-coredump@8-8662-0.service: Deactivated successfully.
[…] systemd[1]: systemd-coredump@8-8662-0.service: Consumed 2.106s CPU time.

I cut not important logs and information.

Yours,
nicolas patrois


-- Package-specific info:


-- Addons package information

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 5.16.0-6-686-pae (SMP w/3 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR:fr:en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages firefox depends on:
ii  debianutils  5.17
ii  fontconfig   2.15.0-1.1
ii  libasound2t641.2.11-1+b1
ii  libatk1.0-0t64   2.52.0-1
ii  libc62.38-10
ii  libcairo-gobject21.18.0-3+b1
ii  libcairo21.18.0-3+b1
ii  libdbus-1-3  1.14.10-4+b1
ii  libevent-2.1-7t642.1.12-stable-8.1+b3
ii  libffi8  3.4.6-1
ii  libfontconfig1   2.15.0-1.1
ii  libfreetype6 2.13.2+dfsg-1+b4
ii  libgcc-s114-20240429-1
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-3+b3
ii  libglib2.0-0t64  2.80.2-1
ii  libgtk-3-0t643.24.41-4
ii  libnspr4 2:4.35-1.1+b1
ii  libnss3  2:3.99-1
ii  libpango-1.0-0   1.52.2+ds-1
ii  libstdc++6   14-20240429-1
ii  libvpx9  1.14.0-2
ii  libx11-6 2:1.8.7-1+b1
ii  libx11-xcb1  2:1.8.7-1+b1
ii  libxcb-shm0  1.17.0-1
ii  libxcb1  1.17.0-1
ii  libxcomposite1   1:0.4.5-1+b1
ii  libxdamage1  1:1.1.6-1+b1
ii  libxext6 2:1.3.4-1+b1
ii  libxfixes3   1:6.0.0-2+b1
ii  libxrandr2   2:1.5.4-1
ii  procps   2:4.0.4-4
ii  zlib1g   1:1.3.dfsg+really1.3.1-1

Versions of packages firefox recommends:
ii  libavcodec53  7:0.10.3-dmo1
ii  libavcodec54  10:1.2.6-dmo4
ii  libavcodec55  10:2.3.3-dmo3
ii  libavcodec56  10:2.8.6-dmo2
ii  libavcodec57  10:3.4.2-dmo3
ii  libavcodec60  10:6.1.1-dmo5

Versions of packages firefox suggests:
ii  fonts-lmodern  2.005-1
ii  fonts-stix [otf-stix]  1.1.1-5
ii  libcanberra0   0.30-17
ii  libgssapi-krb5-2   1.20.1-6+b1
ii  otf-stix   1.1.1-1
ii  pulseaudio 16.1+dfsg1-5

-- no debconf information

Bug#1070885: openocd: FTBFS with libgpiod/2.1

[賴建宇]

Source: openocd
Version: 0.12.0-1
Severity: important

Dear Maintainer,

I am planning to have a transition for libgpiod.
https://release.debian.org/transitions/html/auto-libgpiod.html

Many APIs were changed in this transition.
I tested libgpiod with openocd 0.12.0.
As a result, it seems FTBFS. Please have a check.
Feel free to let me know if any information is needed.
Thanks.

=
/bin/bash ./libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.   
-I./src -I./src -DPKGDATADIR=\"/usr/share/openocd\" -DBINDIR=\"/usr/bin\"  
-isystem /usr/include/libusb-1.0 -I/usr/include/libftdi1 
-I/usr/include/libusb-1.0   -I/usr/include/hidapi  -I/usr/include/libusb-1.0   
-Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wstrict-prototypes -Wformat-security 
-Wshadow -Wextra -Wno-unused-parameter -Wbad-function-cast -Wcast-align 
-Wredundant-decls -Wpointer-arith -Wundef -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/build/openocd-0.12.0=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -c -o 
src/jtag/drivers/libocdjtagdrivers_la-ft232r.lo `test -f 
'src/jtag/drivers/ft232r.c' || echo './'`src/jtag/drivers/ft232r.c
src/jtag/drivers/linuxgpiod.c: In function 'linuxgpiod_read':
src/jtag/drivers/linuxgpiod.c:51:18: error: implicit declaration of function 
'gpiod_line_get_value'; did you mean 'gpiod_line_request_get_value'? 
[-Werror=implicit-function-declaration]
   51 | retval = gpiod_line_get_value(gpiod_line[ADAPTER_GPIO_IDX_TDO]);
  |  ^~~~
  |  gpiod_line_request_get_value
src/jtag/drivers/linuxgpiod.c: In function 'linuxgpiod_write':
src/jtag/drivers/linuxgpiod.c:84:26: error: implicit declaration of function 
'gpiod_line_set_value'; did you mean 'gpiod_line_request_set_value'? 
[-Werror=implicit-function-declaration]
   84 | retval = 
gpiod_line_set_value(gpiod_line[ADAPTER_GPIO_IDX_TDI], tdi);
  |  ^~~~
  |  gpiod_line_request_set_value
src/jtag/drivers/linuxgpiod.c: In function 'linuxgpiod_swdio_drive':
src/jtag/drivers/linuxgpiod.c:131:9: error: implicit declaration of function 
'gpiod_line_release'; did you mean 'gpiod_line_request_release'? 
[-Werror=implicit-function-declaration]
  131 | gpiod_line_release(gpiod_line[ADAPTER_GPIO_IDX_SWDIO]);
  | ^~
  | gpiod_line_request_release
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I./src -I./src 
-DPKGDATADIR=\"/usr/share/openocd\" -DBINDIR=\"/usr/bin\" -isystem 
/usr/include/libusb-1.0 -I/usr/include/libftdi1 -I/usr/include/libusb-1.0 
-I/usr/include/hidapi -I/usr/include/libusb-1.0 -Wdate-time -D_FORTIFY_SOURCE=2 
-Wall -Wstrict-prototypes -Wformat-security -Wshadow -Wextra 
-Wno-unused-parameter -Wbad-function-cast -Wcast-align -Wredundant-decls 
-Wpointer-arith -Wundef -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/build/openocd-0.12.0=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c 
src/jtag/drivers/ft232r.c -o src/jtag/drivers/libocdjtagdrivers_la-ft232r.o
src/jtag/drivers/linuxgpiod.c:139:26: error: implicit declaration of function 
'gpiod_line_request_output'; did you mean 'gpiod_line_request_get_fd'? 
[-Werror=implicit-function-declaration]
  139 | retval = 
gpiod_line_request_output(gpiod_line[ADAPTER_GPIO_IDX_SWDIO], "OpenOCD", 1);
  |  ^
  |  gpiod_line_request_get_fd
src/jtag/drivers/linuxgpiod.c:143:26: error: implicit declaration of function 
'gpiod_line_request_input'; did you mean 'gpiod_line_request_get_fd'? 
[-Werror=implicit-function-declaration]
  143 | retval = 
gpiod_line_request_input(gpiod_line[ADAPTER_GPIO_IDX_SWDIO], "OpenOCD");
  |  ^~~~
  |  gpiod_line_request_get_fd
src/jtag/drivers/linuxgpiod.c: In function 'helper_get_line':
src/jtag/drivers/linuxgpiod.c:283:19: error: 
'GPIOD_LINE_REQUEST_DIRECTION_INPUT' undeclared (first use in this function); 
did you mean 'GPIOD_LINE_DIRECTION_INPUT'?
  283 | int dir = GPIOD_LINE_REQUEST_DIRECTION_INPUT, flags = 0, val = 
0, retval;
  |   ^~
  |   GPIOD_LINE_DIRECTION_INPUT
src/jtag/drivers/linuxgpiod.c:283:19: note: each undeclared identifier is 
reported only once for each function it appears in
src/jtag/drivers/linuxgpiod.c:285:27: error: implicit declaration of function 
'gpiod_chip_open_by_number' [-Werror=implicit-function-declaration]
  285 | gpiod_chip[idx] = 
gpiod_chip_open_by_number(adapter_gpio_config[idx].chip_num);
  |   ^
src/jtag/drivers/linuxgpiod.c:285:25: warning: assignment to 'struct gpiod_chip 
*' from 'int' makes 

Bug#1070884: Issues about compiling Intel CET-enabled binary

[김형석]

Package: gcc (Debian 12.2.0-14) 12.2.0
OS: debian:stable-20240423-slim

When I build CET-enable binary by enabling '-fcf-protection' option, the
gcc compiler failed to generate the binary properly. The output binary
should ideally have IBT and SHSTK properties, but it does not have the
properties.

```
# gcc hello.c -fcf-protection=full -o hello
# readelf -n hello

Displaying notes found in: .note.gnu.property
  OwnerData size Description
  GNU  0x0010 NT_GNU_PROPERTY_TYPE_0
  Properties: x86 ISA needed: x86-64-baseline
...
```

If the output binary was properly compiled, it should have IBT and
SHSTK properties as follows.
```
Displaying notes found in: .note.gnu.property
  OwnerData size Description
  GNU  0x0010 NT_GNU_PROPERTY_TYPE_0
  Properties: x86 feature: IBT, SHSTK


Upon further investigation, I discovered that the C runtime in Debian lacks
the IBT and SHSTK properties, which led to the issue.
```
# gcc hello.c -fcf-protection=full  -z cet-report=error
/usr/bin/ld:
/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/Scrt1.o: error:
missing IBT and SHSTK properties
/usr/bin/ld:
/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/crti.o: error:
missing IBT and SHSTK properties
/usr/bin/ld:
/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/crtn.o: error:
missing IBT and SHSTK properties
collect2: error: ld returned 1 exit status
```

Furthermore, it was observed that none of the packages in Debian had IBT
and SHSTK properties, despite containing ENDBR instructions.

Given this situation, I would like to inquire about Debian's official
support for Intel CET. If Debian does not currently support Intel CET, I am
curious to know if there are any plans in place to provide support for
Intel CET in the future.

I appreciate your attention to this matter and look forward to hearing from
you soon.

Best regards,
Hyungseok Kim

Bug#1070883: src:imsprog: Does not rebuild qt language files

[Tobias Frost]

Source: imsprog
Severity: important

Dear Maintainer,

When reviewing #1069942 I saw the the build process does not redbuilt
the qt language files.

In Debian it is important to rebuild everything from source, that
includes those files.

(As you are upstream, you could incoorpoate this into your build system
and then drop the qm files from the tarball, which will everyone allow to
benefit from this)

Bug#1070667: [Pkg-openssl-devel] Bug#1070667: closed by Sebastian Andrzej Siewior (Re: Bug#1070667: libssl3: Cannot remove system package:)

[Sebastian Andrzej Siewior]

On 2024-05-09 15:14:54 [+0300], Odysseas Romanos wrote:
> Dear Sebastian
Hi,

> Thank you very much for your support. I will try manually as you
> suggested. Do you need me to keep you updated or leave it as it is?

You can let me know how it went but the bug report closed and does not
require further updates.

> Odysseus
> Στάλθηκε από το iPhone μου

Sebastian

Bug#1070331: RFS: nq/0.5-0.1 [NMU] -- Lightweight queue system

[Tobias Frost]

Please also announce the NMU / RFS to the package maintainer, preferable
as bug reported against it. Thanks!

On Sat, May 04, 2024 at 02:19:00PM +0200, 
=?UTF-8?Q?Preu=C3=9...@buxtehude.debian.org wrote:
> Control: block -1 by 1005961
> 
> On 03.05.2024 23:45, Christoph Biedl wrote:
> 
> Hi,
> 
> > That would be necessary - although I don't know how to solve this in a
> > sensible way.
> > 
> > Sorry for disturbing your best intentions to bring nq back in shape -
> > but this problem will not disappear by ignoring it.
> > 
> Completely agree. Let's see if there are reactions for the re-opened bug.
> 
> Hilmar
> -- 
> sigfault
> 

Bug#1052029: c-evo-dh: depends on deprecated GTK 2

[Tobias Frost]

Severity: -1 important

Hi Peter,

please bring this issue to the attention of upstream to get it working
using gtk3 or qt.

I agree with Bastian that we should avoid making the GTK2 problem space
bigger.

-- 
tobi


On Sun, 17 Sep 2023 15:39:48 +0100 Peter B 
wrote:
> On 16/09/2023 11:31, Bastian Germann wrote:
> > Please consider switching to lcl=qt5 to build with qt5 interface.
> > Please rename c-evo-dh-gtk2 to c-evo-dh when implementing this. We
really
> > do not need to know the toolkit that it uses by looking at the pkg
name.
> 
> Hi Bastian,
> 
> Lazarus can build packages against various toolkits, and if more than
one is viable,
> building those gives users some choice, as they all have various
quirks.
> The toolkit in the package name allows that differentiation.
> 
> C-evo-dh will build against all supported Lazarus toolkits, however,
> gtk3 & fpgui builds crash on startup, and qt5 & qt6 have corrupted
graphics.
> gtk2 is the only Linux toolkit version that currently runs OK.
> 
> C-evo-dh has been intentionally packaged to allow co-installation of
multiple front-ends.
> I will certainly include others when they become viable.
> I tested the Qt6 build today with Lazarus 3.0RC1, but have the same
display issues as with Qt5.
> gtk3 is being worked on upstream. That may become a possibility.
> 
> Cheers,
> Peter
> 
> 
> 



signature.asc
Description: PGP signature

Bug#1070879: please make mail-transfer-agent optional

[Michael Tokarev]

11.05.2024 09:14, Michael Tokarev wrote:
..

Please note the function gnupg uses email for is very rarely used, -
it's been many years when gpg-wks-server has been built without even
specifying path to sendmail binary, it's been fixed only in #1025782
in 2024.


Okay, it looks like I was wrong.  gpg-wks-server is the one which actually
uses email (for confirmation)...


Even better if gpg-wks-server itself becomes "more optional", - right
now it is installed on all my (at least desktop) systems.  But this
is a different matter it seems (looks more like bugs in other packages
who blindly depend on whole gnupg instead of certain components they
actually use).


but it is the other packages which wrongly require whole gnupg, including
gpg-wks-server, while actually using only main part of it.  I just filed
#1070882 against devscripts - which seems to be the main reason all my
desktop systems has gpg-wks-server which is not used by anything.  Also
#1070880 against dput-ng.

Thanks,

/mjt
--
GPG Key transition (from rsa2048 to rsa4096) since 2024-04-24.
New key: rsa4096/61AD3D98ECDF2C8E  9D8B E14E 3F2A 9DD7 9199  28F1 61AD 3D98 
ECDF 2C8E
Old key: rsa2048/457CE0A0804465C5  6EE1 95D1 886E 8FFB 810D  4324 457C E0A0 
8044 65C5
Transition statement: http://www.corpit.ru/mjt/gpg-transition-2024.txt

Bug#1064297: RFS: foolsm/1.0.21-1 -- Link connectivity monitor tool

[Tobias Frost]

On Mon, May 06, 2024 at 08:02:17PM +0200, Daniel Gröber wrote:
> On Mon, May 06, 2024 at 02:10:53PM -0300, Lucas Castro wrote:
> 
>  [DEFAULT]
>  debian-branch = gnuabordo/latest
>  debian-tag = gnuabordo/%(version)s

Please let me suggest to use DEP14 for branch naming:
https://dep-team.pages.debian.net/deps/dep14/

--
tobi

Bug#1064297: RFS: foolsm/1.0.21-1 -- Link connectivity monitor tool

[Tobias Frost]

On Mon, May 06, 2024 at 04:31:26PM +0200, Daniel Gröber wrote:
> Hi Lucas,
> d/changelog:
> > lsm (1.0.21-1) unstable; urgency=medium
> > .
> >   * New upstream release (Closes: #1041221)
> >   * Usrmerge compliance (Closes: #1054086)
> 
> Could be more specific. "Use dh_installsystemd to install units" maybe?
> 
> >   * Package rename
> 
> Use imperative in changelogs and be more specific: "Rename package to
> 'foolsm' to stay consistent with upstream" or some such.
> 
> >  - Added transitional package for renaming process
> 
> More specific please. I'd go with straight prose and not bullet-points
> myself. Say: "The old 'lsm' package is now transitional and installs the
> new 'foolsm' package.
> 
> >  - Debian package was modified after upstream project rename.
> 
> I'm not sure what you're trying to tell me here?
> 
> >   * debian/watch updated
> >   * debian/patches/ cleaned out
> 
> IMO these are implied. Ofc. we're going to do that when we update a package
> in Debian so while these would make good git commits I don't think they
> should be in d/changelog since that's mostly user-facing.
> 
> Maybe that's just my git sensibilities showing and it's perfectly
> appropriate to note this in d/changelog for the old dsc focused workflow?
> Feel free to rebuttle this point.
> 
d/changelog should reflect all changes made to the packaging, so if
d/watch and d/patches are changed, it should be mentioned in d/changelog

However, the changelog should say "WHY" something has changed.
Do "d/watch updated" should be improved to "updated d/watch due to $x"
or like.
Same for d/parchs: Explain the why - for example "patch abc.patch has
been removed, applied upstream".

--
tobi

Bug#1070882: please do not depend on whole gnupg suite while using gpg only

[Michael Tokarev]

Package: devscripts
Version: 2.23.7
Severity: normal

devscripts Depends on gnupg (|gnupg2), which is:

 This package contains the full suite of GnuPG tools for cryptographic
 communications and data storage.

The "full" means it includes things like gpg-wks-server or gpgsm which
are unnecessarily installed.

It looks like devscripts actually needs only the main gpg binary, which
is provided by gpg package.  Unless I'm mistaken, this is all what's
needed.

Filing this bug with 'normal' severity, because of other complications
in this area, for example see #1070879.

Thanks,

/mjt

Bug#1070881: reportbug: Provide an option to skip loading configuration files

[Xiyue Deng]

Package: reportbug
Version: 12.0.0
Severity: wishlist

I'd like to propose adding an option to skip loading configuration files
(/etc/reportbug.conf and ~/.reportbugrc).  The use case is for external
programs that runs reportbug (e.g. debian-bug in elpa-debian-el) which
provides its own command line switches and have an assumption on the
output.  When a user set some custom options, notably CC related ones,
it may interfere with how X-Debbugs-Cc is handled and broke some of the
assumptions of external tools (see https://bugs.debian.org/1032662).

With an option to disable loading any configuration files we ensure the
default behavior so that external tools have a way to maintain some
assumptions.  There are probably other ways to assist external tools,
but as some have been working in this way having this option may be an
easier way to help.



-- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-21-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages reportbug depends on:
ii  apt2.6.1
ii  python33.11.2-1+b1
ii  python3-reportbug  12.0.0
ii  sensible-utils 0.0.17+nmu1

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail  
ii  debconf 1.5.82
ii  debsums 3.0.2.1
pn  dlocate 
ii  emacs-bin-common1:29.3+1-3~bpo12+0manphiz1
ii  file1:5.44-3
ii  gnupg   2.2.40-1.1
ii  postfix [mail-transport-agent]  3.7.10-0+deb12u1
pn  python3-urwid   
pn  reportbug-gtk   
ii  xdg-utils   1.1.3-4.1

Versions of packages python3-reportbug depends on:
ii  apt2.6.1
ii  file   1:5.44-3
ii  python33.11.2-1+b1
ii  python3-apt2.6.0
ii  python3-debian 0.1.49
ii  python3-debianbts  4.0.1
ii  python3-requests   2.28.1+dfsg-1
ii  sensible-utils 0.0.17+nmu1

python3-reportbug suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature

Bug#1070880: dput-ng wrongly depends on whole gnupg package

[Michael Tokarev]

Package: python3-dput
Version: 1.39
Severity: normal

python3-dput has Depends: gnupg, which feels wrong. As stated in gnupg
package description:

 This package contains the full suite of GnuPG tools for cryptographic
 communications and data storage.

It seems dput-ng only needs signing command-line interface of gpg, which
is provided by gpg package (the main /usr/bin/gpg binary).  Or if it uses
python interface, this is python3-gnupg.  It definitely does not need,
for example, gpg-wks-server or gpgsm or other parts of gnupg which gets
unnecessarily installed.

Filing this with Severity: normal instead of wishlist because of other
interdependencies, - for example, see #1070879.

Thanks,

/mjt

Bug#1070879: please make mail-transfer-agent optional

[Michael Tokarev]

Source: gnupg2
Version: 2.4.4-1
Severity: minor

Starting 2.4.4-1, gnupg depends on mail-transfer-agent.  Unfortunately,
these days, less and less systems actually have email system configured,
especially home/laptop/etc systems (when email is done though a web UI).
We had mail-transfer-agent almost mandatory in debian for quite a while,
because cron used to depend on it for emailing status of failing jobs
(among others), - now cron is finally optional itself, and it's possible
to install a system without email.

And now it becomes mandatory once again, now coming from gnupg side.

Please note the function gnupg uses email for is very rarely used, -
it's been many years when gpg-wks-server has been built without even
specifying path to sendmail binary, it's been fixed only in #1025782
in 2024.

Please make m-t-a at least Recommends (instead of Depends), or even
better, - Suggests, because about 99.99% of gnupg users will never
need it but configuring mta is a real burden (and it even can't be
done in many cases).

Even better if gpg-wks-server itself becomes "more optional", - right
now it is installed on all my (at least desktop) systems.  But this
is a different matter it seems (looks more like bugs in other packages
who blindly depend on whole gnupg instead of certain components they
actually use).

Thanks,

/mjt