Bug#950174: gvfs-udisks2-volume-monitor.service crashes: No GSettings schemas are installed on the system

[Pascal Dormeau]

Hello,

I do not know if the following can help. So just in case.
I met the same problem recently on a xfce4 setup. Digging in the
bug reports I found this one that matches the same error messages I had.
I finally solved my problem noticing that it happened after modifying
the XDG_DATA_DIRS variable and after some some paths in that variable
were deleted on my system. Removing the non-existing
paths from XDG_DATA_DIRS variable solved my problem.
Therefore, it might be worth verifying if all paths in the XDG_DATA_DIRS
actually exit (or can be accessed).

Best regards
Pascal

Bug#1004536: lintian: suggest Testsuite: autopkgtest-pkg-* when autodep8 detects it should be added

[Paul Wise]

Package: lintian
Severity: wishlist
Usertags: feature
X-Debbugs-CC: autod...@packages.debian.org

I noticed while packaging some Python modules recently that they were
not tested by debci. This is because debci only tests source packages
that contain a Testsuite field. The autodep8 tool is able to generate
the needed tests, but debci only runs it when the Testsuite field is
present and contains an autopkgtest-pkg-* value. The autodep8 tool also
contains heuristics to detect packages that could have autopkgtests but
right now there is nothing suggesting to maintainers that they should
add tests based on autodep8. I suggest that when the Testsuite field is
missing, lintian run autodep8 from the unpacked source package dir and
when autodep8 prints a test stanza on stdout, emit a tag suggesting
that the maintainer add the Testsuite field. If the Testsuite is
already present, presumably the maintainer already added some tests
that are better than the autodep8 ones. Since autodep8 also prints
warnings/errors on stderr, lintian could also emit tags there too. 

Here is an example of an affected package:

$ debsnap python-circuitbreaker 1.3.2-1
$ chronic dpkg-source -x python-circuitbreaker_1.3.2-1.dsc 
$ cd python-circuitbreaker*/
$ grep Testsuite debian/control
$ find debian/tests
find: ‘debian/tests’: No such file or directory
python-circuitbreaker-1.3.2 $ autodep8 
Test-Command: set -e ; for py in $(py3versions -r 2>/dev/null) ; do cd 
"$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -c "import circuitbreaker; 
print(circuitbreaker)" ; done
Depends: python3-all, python3-circuitbreaker, 
Restrictions: allow-stderr, superficial, 
Features: test-name=autodep8-python3

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1004537: exim4: Does not reload expiring TLS certificate; clients cannot connect

[Harri Suutari]

Package: exim4
Version: 4.92-8+deb10u6
Severity: normal

During long server uptime TLS certificate can expire and clients cannot connect
anymore. For example Let's Encrypt offers only three months valid time for
certificates.

Manual fix if is to restart the server manually or by Cron, but maybe this
should be handled as default by the package configuration.

In Debian I have noticed this bug affecting Exim, Docevot and Ejabberd so far.



-- Package-specific info:
Exim version 4.92 #3 built 01-May-2021 09:42:39
Copyright (c) University of Cambridge, 1995 - 2018
(c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2018
Berkeley DB: Berkeley DB 5.3.28: (September  9, 2013)
Support for: crypteq iconv() IPv6 PAM Perl Expand_dlfunc GnuTLS 
move_frozen_messages Content_Scanning DANE DKIM DNSSEC Event OCSP PRDR PROXY 
SOCKS TCP_Fast_Open
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz 
dbmnz dnsdb dsearch ldap ldapdn ldapm mysql nis nis0 passwd pgsql sqlite
Authenticators: cram_md5 cyrus_sasl dovecot plaintext spa tls
Routers: accept dnslookup ipliteral iplookup manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore/mbx autoreply lmtp pipe smtp
Malware: f-protd f-prot6d drweb fsecure sophie clamd avast sock cmdline
Fixed never_users: 0
Configure owner: 0:0
Size of off_t: 8
Configuration file search path is 
/etc/exim4/exim4.conf:/var/lib/exim4/config.autogenerated
Configuration file is /var/lib/exim4/config.autogenerated

-- System Information:
Debian Release: 10.11
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable'), (100, 
'buster-fasttrack')
Architecture: i386 (x86_64)
Foreign Architectures: amd64

Kernel: Linux 4.19.0-18-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_DK.utf8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_DK.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages exim4 depends on:
ii  debconf [debconf-2.0]  1.5.71+deb10u1
ii  exim4-base 4.92-8+deb10u6
ii  exim4-daemon-heavy 4.92-8+deb10u6

exim4 recommends no packages.

exim4 suggests no packages.

-- debconf information excluded

Bug#1004538: dovecot-imapd: Does not reload expiring TLS certificate; clients cannot connect

[Harri Suutari]

Package: dovecot-imapd
Version: 1:2.3.4.1-5+deb10u6
Severity: normal

Dear Maintainer,

During long server uptime TLS certificate can expire and clients cannot connect
anymore. For example Let's Encrypt offers only three months valid time for
certificates.

Manual fix if is to restart the server manually or by Cron, but maybe this
should be handled as default by the package configuration.

In Debian I have noticed this bug affecting Exim, Dovecot and Ejabberd so far.





-- Package-specific info:

-- System Information:
Debian Release: 10.11
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable'), (100, 
'buster-fasttrack')
Architecture: i386 (x86_64)
Foreign Architectures: amd64

Kernel: Linux 4.19.0-18-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_DK.utf8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_DK.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dovecot-imapd depends on:
ii  dovecot-core  1:2.3.4.1-5+deb10u6
ii  libbz2-1.01.0.6-9.2~deb10u1
ii  libc6 2.28-10
ii  liblz4-1  1.8.3-1+deb10u1
ii  liblzma5  5.2.4-1
ii  ucf   3.0038+nmu1
ii  zlib1g1:1.2.11.dfsg-1

dovecot-imapd recommends no packages.

Versions of packages dovecot-imapd suggests:
pn  ufw  

Versions of packages dovecot-imapd is related to:
ii  dovecot-core [dovecot-common]  1:2.3.4.1-5+deb10u6
pn  dovecot-dev
pn  dovecot-gssapi 
ii  dovecot-imapd  1:2.3.4.1-5+deb10u6
pn  dovecot-ldap   
pn  dovecot-lmtpd  
pn  dovecot-managesieved   
pn  dovecot-mysql  
pn  dovecot-pgsql  
pn  dovecot-pop3d  
pn  dovecot-sieve  
pn  dovecot-sqlite 

-- no debconf information

Bug#1004539: ejabberd: Does not reload expiring TLS certificate; clients cannot connect

[Harri Suutari]

Package: ejabberd
Version: 18.12.1-2
Severity: normal

During long server uptime TLS certificate can expire and clients cannot connect
anymore. For example Let's Encrypt offers only three months valid time for
certificates.

Manual fix if is to restart the server manually or by Cron, but maybe this
should be handled as default by the package configuration.

In Debian I have noticed this bug affecting Exim, Dovecot and Ejabberd so far.



-- System Information:
Debian Release: 10.11
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable'), (100, 
'buster-fasttrack')
Architecture: i386 (x86_64)
Foreign Architectures: amd64

Kernel: Linux 4.19.0-18-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_DK.utf8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_DK.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ejabberd depends on:
ii  adduser3.118
ii  debconf [debconf-2.0]  1.5.71+deb10u1
ii  erlang-asn11:21.2.6+dfsg-1
ii  erlang-base [erlang-abi-17.0]  1:21.2.6+dfsg-1
ii  erlang-base64url   1.0-3
ii  erlang-crypto  1:21.2.6+dfsg-1
ii  erlang-goldrush0.2.0-1
ii  erlang-inets   1:21.2.6+dfsg-1
ii  erlang-jiffy   0.14.11+dfsg-4
ii  erlang-jose1.9.0-1
ii  erlang-lager   3.6.8-1
ii  erlang-mnesia  1:21.2.6+dfsg-1
ii  erlang-odbc1:21.2.6+dfsg-1
ii  erlang-os-mon  1:21.2.6+dfsg-1
ii  erlang-p1-cache-tab1.0.17-1
ii  erlang-p1-eimp 1.0.9-1
ii  erlang-p1-iconv1.0.10-1
ii  erlang-p1-pkix 1.0.0-3+deb10u1
ii  erlang-p1-stringprep   1.0.14-1
ii  erlang-p1-tls  1.0.26-1
ii  erlang-p1-utils1.0.13-1
ii  erlang-p1-xml  1.1.34-1
ii  erlang-p1-xmpp 1.2.8-1
ii  erlang-p1-yaml 1.0.17-1
ii  erlang-p1-zlib 1.0.4-3
ii  erlang-public-key  1:21.2.6+dfsg-1
ii  erlang-ssl 1:21.2.6+dfsg-1
ii  erlang-syntax-tools1:21.2.6+dfsg-1
ii  erlang-xmerl   1:21.2.6+dfsg-1
ii  lsb-base   10.2019051400
ii  openssl1.1.1d-0+deb10u7
ii  ucf3.0038+nmu1

ejabberd recommends no packages.

Versions of packages ejabberd suggests:
ii  apparmor 2.13.2-10
ii  apparmor-utils   2.13.2-10
pn  ejabberd-contrib 
pn  erlang-luerl 
pn  erlang-p1-mysql  
pn  erlang-p1-oauth2 
ii  erlang-p1-pam1.0.4-3
pn  erlang-p1-pgsql  
pn  erlang-p1-sip
pn  erlang-p1-sqlite3
pn  erlang-p1-stun   
pn  erlang-redis-client  
ii  imagemagick  8:6.9.10.23+dfsg-2.1+deb10u1
ii  imagemagick-6.q16 [imagemagick]  8:6.9.10.23+dfsg-2.1+deb10u1
ii  libunix-syslog-perl  1.1-3+b1
pn  yamllint 

-- Configuration Files:
/etc/default/ejabberd changed [not included]
/etc/ejabberd/inetrc [Errno 13] Permission denied: '/etc/ejabberd/inetrc'
/etc/ejabberd/modules.d/README.modules [Errno 13] Permission denied: 
'/etc/ejabberd/modules.d/README.modules'

-- debconf information excluded

Bug#1004103: calcurse FTBFS on big endian

[Rajendra Kharat1]

Hi Adrian,
 
Below mentioned issue is occurring due to endian missmatch. 
s390x is an big endian architecture. In calcurse source under src/sha1.c file custom macro is used(WORDS_BIGENDIAN) to determine host byte order and needs to set manually. If the macro is not defined , littel endian byte order is silently assumed. Hence we can use __BYTE_ORDER__ macro which is commonly available on many systems.
 
 
Alternatively, as we're already using Autoconf, we can add the AC_C_BIGENDIAN macro to configure.ac instead, which should auto-detect endianness and set  WORDS_BIGENDIAN accordingly.
 
Thanks,
Rajendra
 
- Original message -From: "Adrian Bunk" To: "Debian Bug Tracking System" Cc:Subject: [EXTERNAL] Bug#1004103: calcurse FTBFS on big endianDate: Fri, Jan 21, 2022 3:00 AM 
Source: calcurseVersion: 4.7.1-1Severity: seriousTags: ftbfsControl: block 1002519 by -1https://buildd.debian.org/status/logs.php?pkg=calcurse&ver=4.7.1-1 ...FAIL: ical-003.sh=Running ./ical-003.sh... FAILFAIL ical-003.sh (exit status: 1)Testsuite summary for calcurse 4.7.1# TOTAL: 77# PASS:  76# SKIP:  0# XFAIL: 0# FAIL:  1# XPASS: 0# ERROR: 0See test/test-suite.logPlease report to b...@calcurse.orgmake[6]: *** [Makefile:761: test-suite.log] Error 1s390x porters Cc'ed to debug this issue. 
 

Bug#1004521: lsof: New upstream release (4.94.0, 2020 Nov 10)

[Florian Ernst]

On Sat, Jan 29, 2022 at 03:10:46PM -0500, Andres Salomon wrote:
> Thanks, I'm aware. I pushed a bunch of patches upstream and was waiting for
> 4.95 to get released, but it's taking longer than expected. :(

Thanks for the feedback, and thanks for taking care. I trust you know
best. :-)

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1002445: About shortuuid (was: FTBFS: AssertionError...)

[Martin]

Dear Kouhei Maeda,

one of my packages, libervia-backend resp. salutatoi, depends on
shortuuid and due to bug #1002445 of 2021-12-22 in shortuuid it will be
removed from testing soon.

If you don't have the time to fix the bug right now, I could make an NMU
(non-maintainer upload), but I wonder, if it would be better to move the
package to the "Debian Python Team"? That would allow many people to
make changes, whenever necessary. You would remain in charge of the
package, of course.

Please, if you don't mind, just send me a short note "go ahead", and I
would move the package to the team, fix the bug and update it!

Many thanks in advance!

Cheers, Martin

Bug#1004088: [Pkg-nagios-devel] Bug#1004088: no plugin to remote monitor chrony

[Jan Wagner]

Hi Marc,

Am 20.01.22 um 18:00 schrieb Marc Haber:

according to discussions on debian-devel, Debian is kind of planning to
move away from src:ntp as NTP server implementation. chrony is among the
candidates to be a replacement, and it already has significant coverage
since it's installed in the Debian Cloud images.

However, chrony doesn't support ntp mode 6, and thus check_ntp_peer does
not work with chrony servers. It would be lovely if there would be a
plugin that allows remote monitoring of a chrony server.


looking at 
https://www.mail-archive.com/chrony-users@chrony.tuxfamily.org/msg01506.html 
seems not to indicate, that there might be an easy solution for the 
problem you mentioned.



There is an open github issue upstream since 2018, so it seems unlikely
that upstream will provide such a plugin in the near future. Reference: 
https://github.com/monitoring-plugins/monitoring-plugins/issues/1526


If upstream might not handle this, what do you expact from the 
monitoring-plugins maintainers? Feel free to push things forward 
upstream, for example providing patches there.


In the meantime, if there is another plugin which can handle this, feel 
free to request to add it to nagios-plugin-contrib?


Cheers, Jan.
--
Never write mail to , you have been warned!
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GIT d-- s+: a C+++ UL P+ L+++ E--- W+++ N+++ o++ K++ w--- O M+ V- PS 
PE Y++

PGP++ t-- 5 X R tv- b+ DI D+ G++ e++ h r+++ y
--END GEEK CODE BLOCK--

Bug#1004541: lowdown.pc should Require bsd(?)

[Thomas Koch]

Package: liblowdown-dev
Version: 0.10.0-1
Severity: normal

While packaging nix I encountered this problem:
https://github.com/NixOS/nix/issues/5931

/usr/bin/ld: /usr/lib/x86_64-linux-gnu/liblowdown.a(document.o): in function 
`parse_list':
(.text+0x49ad): undefined reference to `strtonum'

The strtonum function is in libbsd and lowdown comes with polyfills for bsd
functions for non-bsd systems. However it was decided not to use the polyfills:
https://sources.debian.org/src/lowdown/0.10.0-1/debian/rules/#L10

In turn lowdown should somehow declare it's dependency on bsd in it's
pkg-config file. I'm not sure how to do this correctly.

(In the particular case of nix this alone would not help since upstream's
build system does not expect lowdown to have any dependencies and thus does
not call pkg-config to collect them. This could of course also be reported to
nix upstream.)

BTW: Apparently the next release of lowdown will also come with a shared 
library:
https://github.com/kristapsdz/lowdown/issues/45

Bug#1004543: telegram: unsuccessfully tries to set oom_score_adj

[Francesco Potortì]

Package: telegram
Version: 3.4.8-0ubuntu1
Severity: normal
X-Debbugs-Cc: none, Francesco Potortì 

I observe this on the syslog:

Jan 29 18:13:41 tucano dbus-daemon[5321]: [session uid=1000 pid=5321] 
Activating service name='org.freedesktop.Notifications' requested by ':1.47' 
(uid=1000 pid=6705 comm="/opt/telegram/telegram -workdir /home/pot/.Telegra")   

 
Jan 29 18:13:41 tucano dbus-daemon[3502832]: writing oom_score_adj error: 
Permission denied   
Jan 29 18:13:41 tucano dbus-daemon[5321]: [session uid=1000 pid=5321] 
Successfully activated service 'org.freedesktop.Notifications'  
 

This happens many times a day.

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (101, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages telegram depends on:
ii  dbus-x11  1.12.20-3

telegram recommends no packages.

telegram suggests no packages.

-- no debconf information

-- debsums errors found:
debsums: missing file /opt/telegram/Telegram.sh (from telegram package)
debsums: missing file /opt/telegram/telegram.tar.xz (from telegram package)

Bug#1004544: libgsm: New upstream release (1.0 Patchlevel 19, 2020 Mar 27)

[Florian Ernst]

Source: libgsm
Version: 1.0.18-2
Severity: wishlist

Dear maintainer,

there is a new upstream release available, cf.
. The ChangeLog merely contains

| Fri Mar 27 15:18:06  2020
| 
| * Release 1.0 Patchlevel 19
| Make it easier to include gsm.h from C++ by wrapping it with macros.
| Throw a #define _POSIX_C_SOURCE 200809L into toast.h to make it
| possible for Linux glibc to just work.
| (Thanks to e...@google.com for the suggestion; errors are mine.)
| Switch from compress/.Z to gzip/.gz

but the first item seems to implement a more complete solution to
debbug#202712 than debian/patches/02_cplusplus.patch contains.

Please update the package when you think it is due time.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1004545: libogg: New upstream release (1.3.5, 2020 June 3)

[Florian Ernst]

Source: libogg
Version: 1.3.4-0.1
Severity: wishlist

Dear maintainer,

there is a new upstream release available, cf.
. Its CHANGES merely contain

| Version 1.3.5 (2020 June 3)
| 
|  * Fix unsigned typedef problem on macOS.
|  * Fix overflow check in ogg_sync_buffer.
|  * Clean up cmake and autotools build files.
|  * Remove Symbian and Apple XCode build files.
|  * Fix documentation cross-reference links.

but this "overflow check in ogg_sync_buffer" here seems worthwhile:

| diff -ruN libogg-1.3.4/src/framing.c libogg-1.3.5/src/framing.c
| --- libogg-1.3.4/src/framing.c  2019-08-12 20:56:41.0 +0200
| +++ libogg-1.3.5/src/framing.c  2020-11-23 19:41:04.0 +0100
| @@ -597,9 +597,14 @@
| 
|if(size>oy->storage-oy->fill){
|  /* We need to extend the internal buffer */
| -long newsize=size+oy->fill+4096; /* an extra page to be nice */
| +long newsize;
|  void *ret;
| 
| +if(size>INT_MAX-4096-oy->fill){
| +  ogg_sync_clear(oy);
| +  return NULL;
| +}
| +newsize=size+oy->fill+4096; /* an extra page to be nice */
|  if(oy->data)
|ret=_ogg_realloc(oy->data,newsize);
|  else
| @@ -1564,7 +1569,7 @@
|  byteskipcount=byteskip;
|}
| 
| -  ogg_sync_wrote(&oy,next-buf);
| +  ogg_sync_wrote(&oy,(long)(next-buf));
| 
|while(1){
|  int ret=ogg_sync_pageout(&oy,&og_de);

In addition this new release refers to its collection of automated tests
that could be executed during build time, cf README.md.

Please update the package when you think it is due time.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1004546: php8.1: I would like to have PHP7.4 (or at least PHP8.0) AND PHP 8.1 together

[Matteo Calorio]

Package: php8.1-common
Version: 8.1.2-1
Severity: wishlist

Dear Maintainer,

since PHP8.1 removed PHP7.4 from my Debian testing installation I can not run
Nextcloud anymore bacause it support just PHP8.0 and below.

I couldn't find a way to reinstall PHP7.4 together PHP8.1: is there any?

Thanks,
  Matteo



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

Kernel: Linux 5.15.0-3-amd64 (SMP w/8 CPU threads)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages php8.1 depends on:
ii  libapache2-mod-php8.1  8.1.2-1+b1
ii  php8.1-cgi 8.1.2-1+b1
ii  php8.1-common  8.1.2-1+b1
ii  php8.1-fpm 8.1.2-1+b1

php8.1 recommends no packages.

php8.1 suggests no packages.

Versions of packages php8.1-common depends on:
ii  libc6   2.33-5
ii  libffi8 3.4.2-4
ii  libssl1.1   1.1.1m-1
ii  php-common  2:92
ii  ucf 3.0043

-- no debconf information

Bug#1004548: Security Vulnerability /_data_/…/storage/cfg/…/…/accounts

[Mathieu ROY]

Package: rainloop
Version: 1.16.0+dfsg-1

Hello,

According to https://github.com/RainLoop/rainloop-webmail/issues/2134 there is 
a security issue in the package:

- 
Expected behavior:
File can't be decrypted on (backup) server.

actual behavior:
File can be decrypted on (backup) server.

Steps to reproduce the problem:
When calling \RainLoop\Actions->SetAccounts()
It will store an array of values from \RainLoop\Model\Account->GetAuthToken()
Which in turn calls \RainLoop\Utils::EncodeKeyValues()
And that calls \RainLoop\Utils::EncryptString(@\serialize($aValues), 
\md5(APP_SALT))

When someone/something has access to the SALT.php file,
it can decode the encrypted accounts and gain all passwords.

These days with server breaches, ransomware, other attacks and the increase of 
backup behavior, the chance of being listed on "have i been pwned" has 
increased and the above mentioned issue becomes a bigger vulnerability.

Solutions:

Encrypting the file based on user cookie is very unreliable and has a high 
fail rate.
Encrypting with a server stored key (like the SALT.php) opens this issue
Encrypting using the main account password (the login) fails when password 
is changed or when using OAUTHBEARER/XOAuth2
Only encrypting the account passwords with (3) keeps the accounts, but only 
login will fail.

With (4) you could store an HMAC of the encrypted password to check if the 
account login works.
Same issue applies to the 'contacts_sync' file
- 

This was reported in november 2021 and left with no public reply.
This problem is reportedly fixed in rainloop fork named Snappymail 
https://snappymail.eu/

There is also another pending security issue, not yet published, 
https://github.com/RainLoop/rainloop-webmail/issues/2142 also left with no 
public reply.




Regards

Bug#1004546: php8.1: I would like to have PHP7.4 (or at least PHP8.0) AND PHP 8.1 together

[Ondřej Surý]

Control: close -1

No[*], you should not be using testing if you don’t want software to changes. 
Debian supports a single PHP release in a single Debian release.

Also this is not a bug.

Ondrej
--
Ondřej Surý  (He/Him)

> On 30. 1. 2022, at 11:48, Matteo Calorio  wrote:
> 
> Package: php8.1-common
> Version: 8.1.2-1
> Severity: wishlist
> 
> Dear Maintainer,
> 
> since PHP8.1 removed PHP7.4 from my Debian testing installation I can not run
> Nextcloud anymore bacause it support just PHP8.0 and below.
> 
> I couldn't find a way to reinstall PHP7.4 together PHP8.1: is there any?
> 
> Thanks,
>  Matteo
> 
> 
> 
> -- System Information:
> Debian Release: bookworm/sid
>  APT prefers testing
>  APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 5.15.0-3-amd64 (SMP w/8 CPU threads)
> Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not 
> set
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages php8.1 depends on:
> ii  libapache2-mod-php8.1  8.1.2-1+b1
> ii  php8.1-cgi 8.1.2-1+b1
> ii  php8.1-common  8.1.2-1+b1
> ii  php8.1-fpm 8.1.2-1+b1
> 
> php8.1 recommends no packages.
> 
> php8.1 suggests no packages.
> 
> Versions of packages php8.1-common depends on:
> ii  libc6   2.33-5
> ii  libffi8 3.4.2-4
> ii  libssl1.1   1.1.1m-1
> ii  php-common  2:92
> ii  ucf 3.0043
> 
> -- no debconf information
> 

Bug#1004549: ITP: pre-commit-hooks -- out-of-the-box hooks for pre-commit

[Daniel Baumann]

Package: wnpp
Severity: wishlist
Owner: Daniel Baumann 

* Package name : pre-commit-hooks
  Upstream Author  : Anthony Sottile, Ken Struys
* URL  : https://pre-commit.com/
* License  : MIT
  Programming Lang : Python
  Description  : Some out-of-the-box hooks for pre-commit

Regards,
Daniel

Bug#1004503: [Pkg-javascript-devel] Bug#1004503: node-tap: Please update to version 15

[Yadd]

On 29/01/2022 18:26, Yadd wrote:

Package: node-tap
Version: 12.0.1+ds-4
Severity: normal

node-tap is outdated, version 15 is needed for some package (npm at
least).

Dependencies state:

# tap@15.1.6 (node-tap)
DEPENDENCIES:
   node-ansi-escapes (ansi-escapes)
   node-auto-bind (auto-bind)
   node-babel7
   node-chalk (chalk)
   node-chokidar (chokidar)
   node-cli-boxes (cli-boxes)
   node-cli-cursor (cli-cursor)
   node-cli-truncate (cli-truncate)
   node-cliui (cliui)
   node-convert-source-map (convert-source-map)
   node-coveralls (coveralls)
   node-decamelize (decamelize)
   node-diff (diff)
   node-es6-error (es6-error)
   node-esprima (esprima)
   node-find-cache-dir (find-cache-dir)
   node-find-up (find-up)
   node-foreground-child (foreground-child)
   node-glob (glob)
   node-graceful-fs (graceful-fs)
   node-indent-string (indent-string)
   node-is-windows (is-windows)
   node-isexe (isexe)
   node-istanbul
   node-jest-debbundle (is-ci)
   node-lodash (lodash)
   node-lodash-packages (lodash.flattendeep)
   node-make-dir (make-dir)
   node-minipass (minipass)
   node-mkdirp (mkdirp)
   node-ms (ms)
   node-opener (opener)
   node-p-map (p-map)
   node-punycode (punycode)
   node-react (@types/react, react, react-reconciler, scheduler)
   node-read-pkg (type-fest)
   node-resolve-from (callsites, resolve-from)
   node-rimraf (rimraf)
   node-shell-quote (shell-quote)
   node-signal-exit (signal-exit)
   node-slice-ansi (slice-ansi)
   node-source-map-support (source-map-support)
   node-stack-utils (stack-utils)
   node-string-width (string-width)
   node-strip-ansi (strip-ansi)
   node-tap-mocha-reporter (tap-mocha-reporter)
   node-tap-parser (tap-parser)
   node-which (which)
   node-widest-line (widest-line)
   node-wrap-ansi (wrap-ansi)
   node-write-file-atomic (write-file-atomic)
   node-ws (ws)
   node-yaml (yaml)
   node-yargs (yargs)


I added nyc into node-istanbul (nyc is the new istanbul command line). 
New missing modules list


MISSING:
tap
 └── @isaacs/import-jsx (4.0.1)
 └── caller-path (3.0.1)
 └── caller-callsite (4.1.0)
 └── findit (2.0.0)
 └── ink (3.2.0)
 └── code-excerpt (3.0.0)
 └── convert-to-spaces (1.0.2)
 └── patch-console (1.0.0)
 └── react-devtools-core (4.23.0)
 └── yoga-layout-prebuilt (1.10.0)
 └── @types/yoga-layout (1.9.2)
 └── jackspeak (1.4.1)
 └── libtap (1.1.4)
 └── async-hook-domain (2.0.4)
 └── tap-yaml (1.0.0)
 └── tcompare (5.0.7)
 └── (^) tap-yaml (1.0.0)
 └── (^) tcompare (5.0.7)
 └── treport (3.0.2)
 └── (^) @isaacs/import-jsx (4.0.1)
 └── cardinal (2.1.1)
 └── ansicolors (0.3.2)
 └── redeyed (2.1.1)
 └── (^) ink (3.2.0)
 └── unicode-length (2.0.2)

Bug#1004503: [Pkg-javascript-devel] Bug#1004503: node-tap: Please update to version 15

[Yadd]

On 30/01/2022 12:34, Yadd wrote:

On 29/01/2022 18:26, Yadd wrote:

Package: node-tap
Version: 12.0.1+ds-4
Severity: normal

node-tap is outdated, version 15 is needed for some package (npm at
least).

Dependencies state:

# tap@15.1.6 (node-tap)
DEPENDENCIES:
   node-ansi-escapes (ansi-escapes)
   node-auto-bind (auto-bind)
   node-babel7
   node-chalk (chalk)
   node-chokidar (chokidar)
   node-cli-boxes (cli-boxes)
   node-cli-cursor (cli-cursor)
   node-cli-truncate (cli-truncate)
   node-cliui (cliui)
   node-convert-source-map (convert-source-map)
   node-coveralls (coveralls)
   node-decamelize (decamelize)
   node-diff (diff)
   node-es6-error (es6-error)
   node-esprima (esprima)
   node-find-cache-dir (find-cache-dir)
   node-find-up (find-up)
   node-foreground-child (foreground-child)
   node-glob (glob)
   node-graceful-fs (graceful-fs)
   node-indent-string (indent-string)
   node-is-windows (is-windows)
   node-isexe (isexe)
   node-istanbul
   node-jest-debbundle (is-ci)
   node-lodash (lodash)
   node-lodash-packages (lodash.flattendeep)
   node-make-dir (make-dir)
   node-minipass (minipass)
   node-mkdirp (mkdirp)
   node-ms (ms)
   node-opener (opener)
   node-p-map (p-map)
   node-punycode (punycode)
   node-react (@types/react, react, react-reconciler, scheduler)
   node-read-pkg (type-fest)
   node-resolve-from (callsites, resolve-from)
   node-rimraf (rimraf)
   node-shell-quote (shell-quote)
   node-signal-exit (signal-exit)
   node-slice-ansi (slice-ansi)
   node-source-map-support (source-map-support)
   node-stack-utils (stack-utils)
   node-string-width (string-width)
   node-strip-ansi (strip-ansi)
   node-tap-mocha-reporter (tap-mocha-reporter)
   node-tap-parser (tap-parser)
   node-which (which)
   node-widest-line (widest-line)
   node-wrap-ansi (wrap-ansi)
   node-write-file-atomic (write-file-atomic)
   node-ws (ws)
   node-yaml (yaml)
   node-yargs (yargs)


I added nyc into node-istanbul (nyc is the new istanbul command line). 
New missing modules list


MISSING:
tap
  └── @isaacs/import-jsx (4.0.1)
  └── caller-path (3.0.1)
  └── caller-callsite (4.1.0)
  └── findit (2.0.0)
  └── ink (3.2.0)
  └── code-excerpt (3.0.0)
  └── convert-to-spaces (1.0.2)
  └── patch-console (1.0.0)
  └── react-devtools-core (4.23.0)
  └── yoga-layout-prebuilt (1.10.0)
  └── @types/yoga-layout (1.9.2)
  └── jackspeak (1.4.1)
  └── libtap (1.1.4)
  └── async-hook-domain (2.0.4)
  └── tap-yaml (1.0.0)
  └── tcompare (5.0.7)
  └── (^) tap-yaml (1.0.0)
  └── (^) tcompare (5.0.7)
  └── treport (3.0.2)
  └── (^) @isaacs/import-jsx (4.0.1)
  └── cardinal (2.1.1)
  └── ansicolors (0.3.2)
  └── redeyed (2.1.1)
  └── (^) ink (3.2.0)
  └── unicode-length (2.0.2)


ink is a command-line test utility for react

Bug#1004550: Installation of sid successfully at Asus ZenbookPro

[Bernhard]

Package: installation-reports

Boot method: Network PXE Boot
Image version: PXE Boot with daily:

> https://d-i.debian.org/daily-images/amd64/daily/netboot/debian-installer/amd64/initrd.gz
> https://d-i.debian.org/daily-images/amd64/daily/netboot/debian-installer/amd64/linux

Date: 2022-01-29

Machine: Asus Zenbook Pro UX501J
Processor: Intel(R) Core(TM) i7-4720HQ CPU @ 2.60GHz
Memory: 16GB
Partitions:

> DateisystemTyp  1K-Blöcke Benutzt Verfügbar Verw% Eingehängt auf
> udev   devtmpfs   8114212   0   81142120% /dev
> tmpfs  tmpfs  16276681076   16265921% /run
> /dev/sda2  ext4 120983240 9444244 1053471769% /
> tmpfs  tmpfs  81383408288   81300521% /dev/shm
> tmpfs  tmpfs 5120   4  51161% /run/lock
> /dev/sda1  vfat523244 1445231001% /boot/efi
> tmpfs  tmpfs  1627668  56   16276121% /run/user/1000

Output of lspci -knn:

> 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
> Processor DRAM Controller [8086:0c04] (rev 06)
>   Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
> DRAM Controller [1043:18dd]
>   Kernel modules: ie31200_edac
> 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
> Processor PCI Express x16 Controller [8086:0c01] (rev 06)
>   Kernel driver in use: pcieport
> 00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core 
> Processor Integrated Graphics Controller [8086:0416] (rev 06)
>   Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
> Graphics Controller [1043:18dd]
>   Kernel driver in use: i915
>   Kernel modules: i915
> 00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
> Processor HD Audio Controller [8086:0c0c] (rev 06)
>   Subsystem: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD 
> Audio Controller [8086:2010]
>   Kernel driver in use: snd_hda_intel
>   Kernel modules: snd_hda_intel
> 00:14.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset 
> Family USB xHCI [8086:8c31] (rev 05)
>   Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family 
> USB xHCI [1043:18dd]
>   Kernel driver in use: xhci_hcd
>   Kernel modules: xhci_pci
> 00:16.0 Communication controller [0780]: Intel Corporation 8 Series/C220 
> Series Chipset Family MEI Controller #1 [8086:8c3a] (rev 04)
>   Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family 
> MEI Controller [1043:18dd]
>   Kernel driver in use: mei_me
>   Kernel modules: mei_me
> 00:1a.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset 
> Family USB EHCI #2 [8086:8c2d] (rev 05)
>   Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family 
> USB EHCI [1043:18dd]
>   Kernel driver in use: ehci-pci
>   Kernel modules: ehci_pci
> 00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset 
> High Definition Audio Controller [8086:8c20] (rev 05)
>   Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset High 
> Definition Audio Controller [1043:18dd]
>   Kernel driver in use: snd_hda_intel
>   Kernel modules: snd_hda_intel
> 00:1c.0 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset 
> Family PCI Express Root Port #1 [8086:8c10] (rev d5)
>   Kernel driver in use: pcieport
> 00:1c.2 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset 
> Family PCI Express Root Port #3 [8086:8c14] (rev d5)
>   Kernel driver in use: pcieport
> 00:1c.3 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset 
> Family PCI Express Root Port #4 [8086:8c16] (rev d5)
>   Kernel driver in use: pcieport
> 00:1d.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset 
> Family USB EHCI #1 [8086:8c26] (rev 05)
>   Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family 
> USB EHCI [1043:18dd]
>   Kernel driver in use: ehci-pci
>   Kernel modules: ehci_pci
> 00:1f.0 ISA bridge [0601]: Intel Corporation HM87 Express LPC Controller 
> [8086:8c4b] (rev 05)
>   Subsystem: ASUSTeK Computer Inc. HM87 Express LPC Controller [1043:18dd]
>   Kernel driver in use: lpc_ich
>   Kernel modules: lpc_ich
> 00:1f.2 SATA controller [0106]: Intel Corporation 8 Series/C220 Series 
> Chipset Family 6-port SATA Controller 1 [AHCI mode] [8086:8c03] (rev 05)
>   Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family 
> 6-port SATA Controller 1 [AHCI mode] [1043:18dd]
>   Kernel driver in use: ahci
>   Kernel modules: ahci
> 00:1f.3 SMBus [0c05]: Intel Corporation 8 Series/C220 Series Chipset Family 
> SMBus Controller [8086:8c22] (rev 05)
>   Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family 
> SMBus Controller [1043:18dd]
>   Kernel driver in use: i801_smbus
>   Kernel modu

Bug#1004548: Acknowledgement (Security Vulnerability/_data_/…/storage/cfg/…/…/accounts)

[Mathieu ROY]

Further inquiry shows that several differents persons tried to get in touch 
with Rainloop team regarding security issue (one qualified "high" by said 
person) with no answer, to the point that rainloop seems to be completely 
abandoned

Read more at https://github.com/RainLoop/rainloop-webmail/issues/2162

Bug#1004551: ITP: node-ink -- command-line utility to test react.js component

[Yadd]

Package: wnpp
Severity: wishlist
Owner: Yadd 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: node-ink
  Version : 3.2.0
  Upstream Author : Vadim Demedes 
* URL : https://github.com/vadimdemedes/ink
* License : Expat
  Programming Lang: JavaScript
  Description : command-line utility to test react.js component

Ink provides the same component-based UI building experience that React offers
in the browser, but for command-line apps. It uses Yoga to build Flexbox
layouts in the terminal, so most CSS-like props are available in Ink as well.
If you are already familiar with React, you already know Ink.

Since Ink is a React renderer, it means that all features of React are
supported. Head over to React website for documentation on how to use it. Only
Ink's methods will be documented in this readme.

This package is a dependency of node-tap 15. It will be maintained under
JS team umbrella

Bug#1004522: debian-policy: Proposing new virtual package: wayland-session

[Stephan Lachnit]

I like the idea. Just another idea for the naming, about
wayland-desktop-session?

Regards,
Stephan


On Sat, 29 Jan 2022, 21:15 Simon McVittie,  wrote:

> Package: debian-policy
> Version: 4.6.0.1
> Severity: wishlist
> X-Debbugs-Cc: debian-de...@lists.debian.org
>
> GNOME's gdm3 and KDE's sddm both enumerate possible Wayland sessions in
> /usr/{,local/}share/wayland-sessions/*.desktop and make them available
> as desktop sessions that users can choose, in addition to listing the
> X11 sessions that they traditionally did.
>
> At the moment, installing gdm3 pulls in either gnome-session (a minimal
> GNOME desktop), or some sort of X11 thing (usually a session manager,
> but sometimes a window manager or an xterm), but it should ideally
> be possible to install gdm3 as a login prompt from which to launch a
> non-GNOME Wayland session like weston or sway.
>
> I propose this entry for virtual-package-names-list.yaml:
>
> - name: wayland-session
>   description: a Wayland desktop session
> (/usr/share/wayland-sessions/*.desktop)
>
> According to `apt-file search`, it should initially be provided by these:
>
> gnome-session: /usr/share/wayland-sessions/gnome.desktop
> phosh: /usr/share/wayland-sessions/phosh.desktop
> plasma-workspace-wayland: /usr/share/wayland-sessions/plasmawayland.desktop
> sway: /usr/share/wayland-sessions/sway.desktop
> weston: /usr/share/wayland-sessions/weston.desktop
>
> and perhaps also (I don't know how practical this one is for actual use):
>
> mir-demos: /usr/share/wayland-sessions/mir-shell.desktop
>
> Rationale for not using the names people are probably going to suggest:
>
> - wayland-compositor would be wrong, because it's too low-level. Some
>   Wayland compositors are a somewhat complete desktop environment in their
>   own right, but for example plasma-workspace-wayland and gnome-session
>   are larger components that merely *depend on* a Wayland compositor, plus
>   the additional components needed to get a practical desktop environment;
>   meanwhile, kwin-wayland and gnome-shell are Wayland compositors, but
>   are not desktop environments on their own.
>
> - wayland-session-manager seems like it would be misleading, because an X
>   session manager has specific functional expectations (XSMP) separating
>   it from an mere x-window-manager, but there's no such thing in Wayland.
>
> smcv
>
>

Bug#1000521: libpod: please provide podman-remote binary

[Reinhard Tartler]

Hi Antonio,

thanks for reaching out,

On Wed, Nov 24, 2021 at 8:45 AM Antonio Terceiro 
wrote:

> Source: libpod
> Version: 3.4.1+ds1-2
> Severity: wishlist
>
> Dear Maintainer,
>
> Recent podman upstream releases provide a new podman-remote binary, but
> the Debian package does not even build it.
>
> I'm used to packages providing binaries without a manpage, but this is
> the first time I have seen the opposite! :-)
>
> $ dpkg -S podman-remote
> podman: /usr/share/zsh/vendor-completions/_podman-remote
> podman: /usr/share/man/man1/podman-remote.1.gz
>

I plan to remove the manpage in a future upload. The remote functionality
is backed into the podman binary directly, please refer to podman(1) how to
use the 'podman --remote' functionality.

Background: I brought this up to the podman cabal meeting (cf. meeting
notes at https://hackmd.io/gQCfskDuRLm7iOsWgH2yrg?both) -- Fedora does ship
indeed a smaller podman-remote binary which the manpage is pointing to. Dan
suggested to use  use "podman --remote" instead. I couldn't figure out how
to build the smaller executable. Fedora is using the upstream Makefiles,
which we don't use in the Debian packaging. Instead, we are using the
golang debhelper which takes care of all the unbundling.

Best,
-rt

Bug#1004552: Package: installation-reports

[Charles Champness (TheRedRightHand)]

Package: installation-reports

Boot method: USB stick
Image version: 
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/11.2.0+nonfree/amd64/bt-dvd/firmware-11.2.0-amd64-DVD-1.iso.torrent

Date: 28.Jan.2022

Machine: Intel NUC i5 generation 11 NUC11TNKv5 - (Intel #BNUC11TNKV50002)
Processor: 11th Gen Intel i5-1145G7 (8) @ 4.400GHz
Memory: 64GB (2x 32GB) SO DDR4 PC 3200 CL22 - (G.Skill #F4-3200C22D-64GRS)
SSD1: NVMe M.2 2280 7000 MB/s 1TB - (Kingston #SKC3000S/1024G)
SSD2: SATA M.2 2242 560 MB/s 512GB - (Transcend #TS512GMTS430S)
Partitions: Filesystem Type 1K-blocksUsed Available Use% Mounted on
udev   devtmpfs  32720132   0  32720132   0% /dev
tmpfs  tmpfs  65474241088   6546336   1% /run
/dev/nvme0n1p2 ext4  61203268 1799240  56262652   4% /
tmpfs  tmpfs 32737116   0  32737116   0% /dev/shm
tmpfs  tmpfs 5120   0  5120   0% /run/lock
/dev/nvme0n1p3 ext4  61203268  24  58061868   1% /dat
/dev/sda2  ext2   3837560 1680772   1961460  47% /media/recovery
/dev/sda3  ext4  95535524 6705560  83930792   8% /media/backup
/dev/sda1  vfat5355043484532020   1% /boot/efi
tmpfs  tmpfs  6547420   0   6547420   0% /run/user/1000

Output of lspci -knn (or lspci -nn):00:00.0 Host bridge [0600]: Intel 
Corporation 11th Gen Core Processor Host Bridge/DRAM Registers [8086:9a14] (rev 
01) DeviceName: Onboard - Other Subsystem: Intel Corporation 11th Gen Core 
Processor Host Bridge/DRAM Registers [8086:3003] 00:02.0 VGA compatible 
controller [0300]: Intel Corporation TigerLake GT2 [Iris Xe Graphics] 
[8086:9a49] (rev 01) DeviceName: Onboard - Video Subsystem: Intel Corporation 
Iris Xe Graphics [8086:3003] Kernel driver in use: i915 Kernel modules: i915 
00:06.0 PCI bridge [0604]: Intel Corporation 11th Gen Core Processor PCIe 
Controller [8086:9a09] (rev 01) Kernel driver in use: pcieport 00:07.0 PCI 
bridge [0604]: Intel Corporation Tiger Lake-LP Thunderbolt 4 PCI Express Root 
Port #1 [8086:9a25] (rev 01) Kernel driver in use: pcieport 00:07.2 PCI bridge 
[0604]: Intel Corporation Tiger Lake-LP Thunderbolt 4 PCI Express Root Port #2 
[8086:9a27] (rev 01) Kernel driver in use: pcieport 00:08.0 System peripheral 
[0880]: Intel Corporation Device [8086:9a11] (rev 01) DeviceName: Onboard - 
Other Subsystem: Intel Corporation Device [8086:3003] 00:0d.0 USB controller 
[0c03]: Intel Corporation Tiger Lake-LP Thunderbolt 4 USB Controller 
[8086:9a13] (rev 01) DeviceName: Onboard - Other Kernel driver in use: xhci_hcd 
Kernel modules: xhci_pci 00:0d.2 USB controller [0c03]: Intel Corporation Tiger 
Lake-LP Thunderbolt 4 NHI #0 [8086:9a1b] (rev 01) DeviceName: Onboard - Other 
Subsystem: Device [:] Kernel driver in use: thunderbolt Kernel modules: 
thunderbolt 00:0d.3 USB controller [0c03]: Intel Corporation Tiger Lake-LP 
Thunderbolt 4 NHI #1 [8086:9a1d] (rev 01) DeviceName: Onboard - Other 
Subsystem: Device [:] Kernel driver in use: thunderbolt Kernel modules: 
thunderbolt 00:14.0 USB controller [0c03]: Intel Corporation Tiger Lake-LP USB 
3.2 Gen 2x1 xHCI Host Controller [8086:a0ed] (rev 20) DeviceName: Onboard - 
Other Subsystem: Intel Corporation Tiger Lake-LP USB 3.2 Gen 2x1 xHCI Host 
Controller [8086:3003] Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 
00:14.2 RAM memory [0500]: Intel Corporation Tiger Lake-LP Shared SRAM 
[8086:a0ef] (rev 20) DeviceName: Onboard - Other 00:14.3 Network controller 
[0280]: Intel Corporation Wi-Fi 6 AX201 [8086:a0f0] (rev 20) DeviceName: 
Onboard - Ethernet Subsystem: Intel Corporation Wi-Fi 6 AX201 [8086:0070] 
Kernel driver in use: iwlwifi Kernel modules: iwlwifi 00:15.0 Serial bus 
controller [0c80]: Intel Corporation Tiger Lake-LP Serial IO I2C Controller #0 
[8086:a0e8] (rev 20) DeviceName: Onboard - Other Subsystem: Intel Corporation 
Tiger Lake-LP Serial IO I2C Controller [8086:3003] Kernel driver in use: 
intel-lpss Kernel modules: intel_lpss_pci 00:15.1 Serial bus controller [0c80]: 
Intel Corporation Tiger Lake-LP Serial IO I2C Controller #1 [8086:a0e9] (rev 
20) DeviceName: Onboard - Other Subsystem: Intel Corporation Tiger Lake-LP 
Serial IO I2C Controller [8086:3003] Kernel driver in use: intel-lpss Kernel 
modules: intel_lpss_pci 00:16.0 Communication controller [0780]: Intel 
Corporation Tiger Lake-LP Management Engine Interface [8086:a0e0] (rev 20) 
DeviceName: Onboard - Other Subsystem: Intel Corporation Tiger Lake-LP 
Management Engine Interface [8086:3003] Kernel driver in use: mei_me Kernel 
modules: mei_me 00:16.3 Serial controller [0700]: Intel Corporation Device 
[8086:a0e3] (rev 20) DeviceName: Onboard - Other Subsystem: Intel Corporation 
Device [8086:3003] Kernel driver in use: serial 00:17.0 SATA controller [0106]: 
Intel Corporation Device [8086:a0d3] (rev 20) DeviceName: Onboard - SATA 
Subsystem: Intel Corporation Device [8086:3003] Kernel driver in use: ahci 
Kernel m

Bug#1004551: ITP: node-ink -- command-line utility to test react.js component

[Jonas Smedegaard]

Quoting Yadd (2022-01-30 13:14:04)
> Package: wnpp
> Severity: wishlist
> Owner: Yadd 
> X-Debbugs-Cc: debian-de...@lists.debian.org
> 
> * Package name: node-ink
>   Version : 3.2.0
>   Upstream Author : Vadim Demedes 
> * URL : https://github.com/vadimdemedes/ink
> * License : Expat
>   Programming Lang: JavaScript
>   Description : command-line utility to test react.js component
> 
> Ink provides the same component-based UI building experience that React offers
> in the browser, but for command-line apps. It uses Yoga to build Flexbox
> layouts in the terminal, so most CSS-like props are available in Ink as well.
> If you are already familiar with React, you already know Ink.
> 
> Since Ink is a React renderer, it means that all features of React are
> supported. Head over to React website for documentation on how to use it. Only
> Ink's methods will be documented in this readme.
^

Remember to adjust the text to better fit package long description :-)


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1004553: new upstream version available (3.6.0)

[Ramakrishnan Muthukrishnan]

Package: libcw6
Version: 3.5.1-4
Severity: wishlist
X-Debbugs-Cc: r...@rkrishnan.org

A new upstream version is available which has some nice fixes for latency etc.



It will be great if this can be packaged up in Debian!

Thanks so much for the nice work of packaging ham radio software in Debian.

73
Ram VU3RDD


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

Kernel: Linux 5.15.0-3-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_IN:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libcw6 depends on:
ii  libc6  2.33-5

libcw6 recommends no packages.

Versions of packages libcw6 suggests:
pn  cw 
pn  cwcp   
pn  xcwcp  

-- no debconf information

Bug#1004554: ITP: libpdfbox-graphics2d-java -- Java library to embed graphics as vector drawing in a PDF

[Pierre Gruet]

Package: wnpp
Severity: wishlist
Owner: Debian Java team 
X-Debbugs-Cc: debian-de...@lists.debian.org, 
pkg-java-maintain...@lists.alioth.debian.org

* Package name: libpdfbox-graphics2d-java
  Version : 0.34
  Upstream Author : Emmeran Seehuber
* URL : https://github.com/rototor/pdfbox-graphics2d/
* License : Apache-2.0
  Programming Lang: Java
  Description : Java library to embed graphics as vector drawing in a PDF

Using this library one can use any Graphics2D API based SVG / graph /
chart library to embed those graphics as vector drawing in a PDF. In
combination with PDFBox PDFRenderer/PageDrawer one can also "rerender"
PDF pages and change certain aspects (e.g. change the color mapping and
perform an overfill) .

The following features are supported:

* Drawing any shape using draw...() and fill...() methods from
  Graphics2D.
* Drawing images. The default is to always lossless compress them. One
  could plugin one's own Image -> PDImageXObject conversion if one wants
  to encode the images as jpeg.
* All BasicStroke attributes.
* Paint:
   - Color. One can specify one's own color mapping implementation to
 special map the (RGB) colors to PDColor. Beside using CMYK colors
 one can also use spot colors.
   - GradientPaint, LinearGradientPaint and RadialGradientPaint. There
 are some restrictions.
   - TexturePaint.
* Drawing text. By default all text is drawn as vector shapes, so no
  fonts are embedded. RTL languages are supported. It's possible to use
  fonts, but this loses some features (especially RTL support) and one
  must provide the TTF files of the fonts if the default PDF fonts are
  not enough.

The package will be team-maintained in the Debian Java team.

Bug#1004350: php-common: Conflict with php7.4

[Timo van Roermund]

Hi Ondřej,

First of all, thanks for maintaining the PHP packages. Much appreciated.

I understand from this thread, as well as bug #1004350) that it's 
intentional that only one version of PHP can be installed on Debian.


Nonetheless, I had to find a way to run PHP 7.4 next to PHP 8.1, as two 
web applications I frequently use (Horde and phpLDAPadmin) are not yet 
compatible with PHP 8.x.


Below a summary of what I did, as this may be useful for others having 
similar issues as well:
1. manually modify the dependencies of php-common to allow PHP 7.4 to be 
installed
2. install PHP 7.4 and configure Apache to use PHP 7.4 for these two web 
applications (only)


These steps in detail:

1. Modify dependencies of php-common

# download the package (php-common_2%3a92_all.deb)
cd /tmp
apt download php-common
# Unpack the package (this will create three files: debian-binary 
control.tar.xz data.tar.xz)

mkdir deb && cd deb/
ar x ../php-common_2%3a92_all.deb
# Unpack control archive
mkdir control && cd control/
tar xf ../control.tar.xz
# Fix dependencies in control using a text editor (I used vim):
# - remove "php7.4-common" from the "Break: " statement
# - also append "-compat" after the version to prevent this package from 
being overwritten with the original one

vim control
# Repack control.tar.gz
tar c * | xz -c > ../control.tar.xz
cd ..
rm -rf -- control/
# Repack deb (order important!)
ar rcs ../php-common_2%3a92_all-compat.deb debian-binary control.tar.xz 
data.tar.xz

cd ..
# clean up
rm -rf -- deb/
# install package
dpkg -i php-common_2%3a92_all-compat.deb


2. Install PHP 7.4

# install PHP 7.4 packages as well as mod_fcgi (FastCGI) for Apache
apt-get install libapache2-mod-fcgid php7.4 php7.4-fpm php7.4-* packages required by your web applications>


# enable Apache2 modules
a2enmod actions fcgid alias proxy_fcgi

# note: I was already using mpm_event; but if you are using the mod_php 
(prefork MPM) module with Apache, then you also need to do the following:

a2dismod php8.1 mpm_prefork
a2enmod mpm_event proxy_fcgi setenvif
a2enconf php8.1-fpm
systemctl restart apache2


3. Configure Apache to use PHP 7.4 for specific web applications (In my 
case: horde and phpLDAPadmin):


I edited my site configuration (file under /etc/apache2/sites-enabled/) 
and added:


    
    
    SetHandler 
"proxy:unix:/run/php/php7.4-fpm.sock|fcgi://localhost"

    
    

Cheers,

Timo

Bug#1004555: ITP: cryptsetup-nuke-password -- Erase the LUKS keys with a special password on the unlock prompt

[Jonas Meurer]

Package: wnpp
Severity: wishlist
Owner: Jonas Meurer 
X-Debbugs-Cc: debian-de...@lists.debian.org, Raphael Hertzog 


* Package name: cryptsetup-nuke-password
  Version : 2-1
  Upstream Author : Offensive Security // Raphael Hertzog
* URL : 
https://gitlab.com/kalilinux/packages/cryptsetup-nuke-password/
* License : GPLv3+
  Programming Lang: C, Shell
  Description : Erase the LUKS keys with a special password on the unlock 
prompt

Installing this package lets you configure a special "nuke password" that
can be used to destroy the encryption keys required to unlock the encrypted
partitions. This password can be entered in the usual early-boot prompt
asking the passphrase to unlock the encrypted partition(s).

This provides a relatively stealth way to make your data unreadable in
case you fear that your computer is going to be seized.

After installation, use “dpkg-reconfigure cryptsetup-nuke-password” to
configure your nuke password.

I intend to maintain this package under the pkg-security umbrella so it's easy
to co-maintain.

Kind regards
 Jonas

Bug#1004556: libmpich-dev: The simplest MPI program compiled with mpich crashes

[Julien Bigot]

Package: libmpich-dev
Version: 4.0-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: jul...@julien-bigot.fr

Dear Maintainer,

When running the simplest MPI program,
```
#include 
int main(int argc, char* argv[])
{
MPI_Init(&argc, &argv);
MPI_Finalize();
return 0;
}
```

it crashes with output:
```
Abort(874106383): Fatal error in internal_Init: Other MPI error, error stack:
internal_Init(59): MPI_Init(argc=0x7ffc82ed999c, argv=0x7ffc82ed9990) failed
MPII_Init_thread(209): 
MPID_Init(359)...: 
MPIR_pmi_init(151)...: PMIX_Init returned -25
```

See attached reproduction log for full details

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'stable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages libmpich-dev depends on:
ii  g++4:11.2.0-2
ii  gfortran [gfortran-mod-15] 4:11.2.0-2
ii  gfortran-10 [gfortran-mod-15]  10.3.0-14
ii  gfortran-11 [gfortran-mod-15]  11.2.0-14
ii  gfortran-9 [gfortran-mod-15]   9.4.0-4+b1
ii  libmpich12 4.0-1
ii  mpich  4.0-1

libmpich-dev recommends no packages.

libmpich-dev suggests no packages.

-- no debconf information
docker run --rm -ti debian:sid  
   
[14:10]
Unable to find image 'debian:sid' locally
sid: Pulling from library/debian
48c02bc8c594: Pull complete 
Digest: sha256:0e6e082a988ec6f880c76864c68705f47e4af4a319e0a56d5a1817282767336c
Status: Downloaded newer image for debian:sid
root@23bd1ec5a8ce:/# apt update
Get:1 http://deb.debian.org/debian sid InRelease [165 kB]
Get:2 http://deb.debian.org/debian sid/main amd64 Packages [8898 kB]
Fetched 9063 kB in 1s (8372 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
13 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@23bd1ec5a8ce:/# apt upgrade
Reading package lists... Done
Building dependency tree... 50%
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  bsdutils libblkid1 libc-bin libc6 libgnutls30 libmount1 libsmartcols1 
libsystemd0 libudev1 libuuid1 mawk mount util-linux
13 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 7946 kB of archives.
After this operation, 1207 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian sid/main amd64 bsdutils amd64 1:2.37.3-1+b1 
[149 kB]
Get:2 http://deb.debian.org/debian sid/main amd64 util-linux amd64 2.37.3-1+b1 
[1200 kB]
Get:3 http://deb.debian.org/debian sid/main amd64 libc6 amd64 2.33-5 [2831 kB]
Get:4 http://deb.debian.org/debian sid/main amd64 libc-bin amd64 2.33-5 [834 kB]
Get:5 http://deb.debian.org/debian sid/main amd64 libsystemd0 amd64 250.3-2 
[404 kB]
Get:6 http://deb.debian.org/debian sid/main amd64 mount amd64 2.37.3-1+b1 [191 
kB]
Get:7 http://deb.debian.org/debian sid/main amd64 libblkid1 amd64 2.37.3-1+b1 
[202 kB]
Get:8 http://deb.debian.org/debian sid/main amd64 libgnutls30 amd64 3.7.3-4+b1 
[1377 kB]
Get:9 http://deb.debian.org/debian sid/main amd64 libmount1 amd64 2.37.3-1+b1 
[220 kB]
Get:10 http://deb.debian.org/debian sid/main amd64 libsmartcols1 amd64 
2.37.3-1+b1 [162 kB]
Get:11 http://deb.debian.org/debian sid/main amd64 libudev1 amd64 250.3-2 [178 
kB]
Get:12 http://deb.debian.org/debian sid/main amd64 libuuid1 amd64 2.37.3-1+b1 
[85.4 kB]
Get:13 http://deb.debian.org/debian sid/main amd64 mawk amd64 
1.3.4.20200120-3+b1 [113 kB]
Fetched 7946 kB in 0s (73.9 MB/s)
debconf: delaying package configuration, since apt-utils is not installed
(Reading database ... 6684 files and directories currently installed.)
Preparing to unpack .../bsdutils_1%3a2.37.3-1+b1_amd64.deb ...
Unpacking bsdutils (1:2.37.3-1+b1) over (1:2.37.3-1) ...
Setting up bsdutils (1:2.37.3-1+b1) ...
(Reading database ... 6685 files and directories currently installed.)
Preparing to unpack .../util-linux_2.37.3-1+b1_amd64.deb ...
Unpacking util-linux (2.37.3-1+b1) over (2.37.3-1) ...
Setting up util-linux (2.37.3-1+b1) ...
(Reading database ... 6686 files and directories currently installed.)
Preparing to unpack .../libc6_2.33-5_amd64.deb ...
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based 
frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 
78.)
debconf: falling back to front

Bug#1004557: man-db: please make index.db installations reproducible

[Johannes Schauer Marin Rodrigues]

Source: man-db
Version: 2.9.4-4
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: jo...@debian.org, reproducible-b...@lists.alioth.debian.org

Hi,

currently, the index.db files created by man-db -c are unreproducible
when creating a Debian chroot. This means that tools that attempt to
create reproducible system images delete all index.db files:

https://gitlab.tails.boum.org/tails/tails/-/blob/stable/config/chroot_local-hooks/99-zz_reproducible-builds-post-processing#L28
https://salsa.debian.org/live-team/live-build/-/blob/master/share/hooks/normal/0190-remove-temporary-files.hook.chroot#L6

This could be avoided if the index.db files after installation would be
bit-by-bit reproducible. The attached patch fixes the problem by
truncating the timestamp set in index.db to the value of
SOURCE_DATE_EPOCH if the variable is set.

This means that this patch does not change anything during normal
operation but only comes into play if a utility that sets
SOURCE_DATE_EPOCH is installing packages.

Thanks!

cheers, josch
--- a/libdb/db_store.c
+++ b/libdb/db_store.c
@@ -29,6 +29,8 @@
 #include 
 #include 
 #include 
+#include 
+#include 
 
 #include "timespec.h"
 #include "xvasprintf.h"
@@ -134,13 +136,45 @@ static datum make_content (struct mandat
if (!in->whatis)
in->whatis = dash + 1;
 
+   struct timespec ts = { .tv_sec = in->mtime.tv_sec, .tv_nsec = 
in->mtime.tv_nsec };
+   char *source_date_epoch = getenv("SOURCE_DATE_EPOCH");
+   unsigned long long epoch;
+   char *endptr;
+   if (source_date_epoch) {
+   // if SOURCE_DATE_EPOCH is set, replace the timestamp with it if
+   // SOURCE_DATE_EPOCH is smaller than the file timestamp
+   errno = 0;
+   epoch = strtoull(source_date_epoch, &endptr, 10);
+   if ((errno == ERANGE && (epoch == ULLONG_MAX || epoch == 0))
+   || (errno != 0 && epoch == 0)) {
+   fprintf(stderr, "Environment variable 
$SOURCE_DATE_EPOCH: strtoull: %s\n", strerror(errno));
+   exit(EXIT_FAILURE);
+   }
+   if (endptr == source_date_epoch) {
+   fprintf(stderr, "Environment variable 
$SOURCE_DATE_EPOCH: No digits were found: %s\n", endptr);
+   exit(EXIT_FAILURE);
+   }
+   if (*endptr != '\0') {
+   fprintf(stderr, "Environment variable 
$SOURCE_DATE_EPOCH: Trailing garbage: %s\n", endptr);
+   exit(EXIT_FAILURE);
+   }
+   if (epoch > ULONG_MAX) {
+   fprintf(stderr, "Environment variable 
$SOURCE_DATE_EPOCH: value must be smaller than or equal to: %lu but was found 
to be: %llu \n", ULONG_MAX, epoch);
+   exit(EXIT_FAILURE);
+   }
+   if (ts.tv_sec > epoch || (ts.tv_sec == epoch && ts.tv_nsec > 
0)) {
+   ts.tv_sec = epoch;
+   ts.tv_nsec = 0;
+   }
+   }
+
MYDBM_SET (cont, xasprintf (
"%s\t%s\t%s\t%ld\t%ld\t%c\t%s\t%s\t%s\t%s",
dash_if_unset (in->name),
in->ext,
in->sec,
-   (long) in->mtime.tv_sec,
-   (long) in->mtime.tv_nsec,
+   (long) ts.tv_sec,
+   (long) ts.tv_nsec,
in->id,
in->pointer,
in->filter,

Bug#983985: bctoolbox: ftbfs with GCC-11

[Bernhard Schmidt]

Hi,


bctoolbox 5.0.37 builds perfectly with mbedtls 2.28.0-0.1 here, I will
test with 2.28.0-0.2 ASAP.


4.4.13-3 (just uploaded) builds fine against mbedtls 2.28.0-0.2 in 
experimental, so go ahead and sorry for the delay.


Bernhard

Bug#1004558: python3.10: reproducible pyc files -- please consider applying this backported patch

[Johannes Schauer Marin Rodrigues]

Source: python3.10
Version: 3.10.2-1
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: randomness
X-Debbugs-Cc: jo...@debian.org, reproducible-b...@lists.alioth.debian.org

Hi,

currently, pyc files generated after installation are not reproducible.
Namely, the elements in frozen sets are not ordered reproducibly. This
means that to create a bit-by-bit reproducible Debian chroot including
Python one has to remove all *.pyc files:

https://gitlab.tails.boum.org/tails/tails/-/blob/stable/config/chroot_local-hooks/99-remove_pyc
https://salsa.debian.org/live-team/live-build/-/blob/master/share/hooks/normal/0170-remove-python-py.hook.chroot

Fortunately, there is a patch that is already accepted upstream that
fixes this problem:

https://github.com/python/cpython/pull/27926
https://bugs.python.org/issue37596

That patch also cleanly applies to Python 3.10 as well as to 3.9. I
tested it for both versions. Please consider carrying the attached patch
for 3.9 and 3.10 so that we can have reproducible Debian chroots before
the Python 3.11 release.

Thanks!

cheers, josch
>From 36ae9beb04763d498df2114657bfbbcfe58bf913 Mon Sep 17 00:00:00 2001
From: Brandt Bucher 
Date: Mon, 23 Aug 2021 18:34:17 -0700
Subject: [PATCH] Serialize frozenset elements deterministically

---
 Lib/test/test_marshal.py  | 25 +++
 .../2021-08-23-21-39-59.bpo-37596.ojRcwB.rst  |  2 ++
 Python/marshal.c  | 32 +++
 3 files changed, 59 insertions(+)
 create mode 100644 
Misc/NEWS.d/next/Library/2021-08-23-21-39-59.bpo-37596.ojRcwB.rst

diff --git a/Lib/test/test_marshal.py b/Lib/test/test_marshal.py
index 7bcf8e8..8252be3 100644
--- a/Lib/test/test_marshal.py
+++ b/Lib/test/test_marshal.py
@@ -318,6 +318,31 @@ class BugsTestCase(unittest.TestCase):
 for i in range(len(data)):
 self.assertRaises(EOFError, marshal.loads, data[0: i])
 
+def test_deterministic_sets(self):
+# bpo-37596: To support reproducible builds, sets and frozensets need 
to
+# have their elements serialized in a consistent order (even when they
+# have been scrambled by hash randomization):
+for kind in ("set", "frozenset"):
+for elements in (
+"float('nan'), b'a', b'b', b'c', 'x', 'y', 'z'",
+# Also test for bad interactions with backreferencing:
+"('string', 1), ('string', 2), ('string', 3)",
+):
+s = f"{kind}([{elements}])"
+with self.subTest(s):
+# First, make sure that our test case still has different
+# orders under hash seeds 0 and 1. If this check fails, we
+# need to update this test with different elements:
+args = ["-c", f"print({s})"]
+_, repr_0, _ = assert_python_ok(*args, PYTHONHASHSEED="0")
+_, repr_1, _ = assert_python_ok(*args, PYTHONHASHSEED="1")
+self.assertNotEqual(repr_0, repr_1)
+# Then, perform the actual test:
+args = ["-c", f"import marshal; print(marshal.dumps({s}))"]
+_, dump_0, _ = assert_python_ok(*args, PYTHONHASHSEED="0")
+_, dump_1, _ = assert_python_ok(*args, PYTHONHASHSEED="1")
+self.assertEqual(dump_0, dump_1)
+
 LARGE_SIZE = 2**31
 pointer_size = 8 if sys.maxsize > 0x else 4
 
diff --git a/Misc/NEWS.d/next/Library/2021-08-23-21-39-59.bpo-37596.ojRcwB.rst 
b/Misc/NEWS.d/next/Library/2021-08-23-21-39-59.bpo-37596.ojRcwB.rst
new file mode 100644
index 000..81fdfeb
--- /dev/null
+++ b/Misc/NEWS.d/next/Library/2021-08-23-21-39-59.bpo-37596.ojRcwB.rst
@@ -0,0 +1,2 @@
+Ensure that :class:`set` and :class:`frozenset` objects are always
+:mod:`marshalled ` reproducibly.
diff --git a/Python/marshal.c b/Python/marshal.c
index 4125240..6bd4537 100644
--- a/Python/marshal.c
+++ b/Python/marshal.c
@@ -502,9 +502,41 @@ w_complex_object(PyObject *v, char flag, WFILE *p)
 W_TYPE(TYPE_SET, p);
 n = PySet_GET_SIZE(v);
 W_SIZE(n, p);
+// bpo-37596: To support reproducible builds, sets and frozensets need
+// to have their elements serialized in a consistent order (even when
+// they have been scrambled by hash randomization). To ensure this, we
+// use an order equivalent to sorted(v, key=marshal.dumps):
+PyObject *pairs = PyList_New(0);
+if (pairs == NULL) {
+p->error = WFERR_NOMEMORY;
+return;
+}
 while (_PySet_NextEntry(v, &pos, &value, &hash)) {
+PyObject *dump = PyMarshal_WriteObjectToString(value, p->version);
+if (dump == NULL) {
+p->error = WFERR_UNMARSHALLABLE;
+goto anyset_done;
+}
+PyObject *pair = PyTuple_Pack(2, dump, value);
+Py

Bug#893058: ITP: libdecaf -- implementation of Montgomery and Edwards elliptic curve cryptography

[Bernhard Schmidt]

On 15/03/18 11:06 PM, Christopher Hoskin wrote:

Hi Christopher,

> Package: wnpp
> Severity: wishlist
> Owner: Christopher Hoskin 
> 
> * Package name: libdecaf
>   Version : 0.9.4
>   Upstream Author : Cryptography Research, Inc.
> * URL : http://ed448goldilocks.sourceforge.net/
> * License : expat
>   Programming Lang: C
>   Description : implementation of Montgomery and Edwards elliptic curve 
> cryptography

I have found your repository at
https://salsa.debian.org/debian/libdecaf/ , however it looks like it has
never been uploaded.

Dennis Filder (CC) has independently prepared a packaging of libdecaf at
https://salsa.debian.org/pkg-voip-team/linphone-stack/libdecaf because
it is necessary for the next major version of the linphone stack.

Would you be fine with uploading Dennis' version? I would have no
objections to move this to the Debian group on salsa if you want to
co-maintain it.

Bernhard

Bug#1004559: lightdm: Installing lightdm adds a confusing "Default Xsession" option in other display managers

[Simon McVittie]

Package: lightdm
Version: 1.26.0-8
Severity: normal
Control: affects -1 + gdm3 sddm slim lxdm

Steps to reproduce:

* Install lightdm
* Install another display manager that lists sessions based on
  /usr/share/xsessions/*.desktop
  - currently this means: gdm3 | sddm | slim | lxdm
* Use dpkg-reconfigure to select the other display manager to be used
* Reboot

Expected result:

* The sessions listed by the other display manager are not affected by
  having installed lightdm

Actual result:

* The other display manager now lists "Default Xsession" as an option
* Users cannot predict what desktop environment will result from choosing
  this option
* This is particularly confusing in display managers like gdm3 where the
  default is something different (e.g. gdm3 defaults to GNOME-on-Wayland),
  so "Default Xsession" is in fact a non-default X session :-)



I suspect this might be the root cause of #973812.

I personally think this "Default Xsession" option is more confusing than
it is useful, even for lightdm-only systems, because users cannot predict
from its name what it will do. Older versions of gdm3 had a similar
option, but I removed it from the versions in testing/unstable. Instead,
gdm3 now ships /usr/share/doc/gdm3/examples/custom-x11-session.desktop,
which sysadmins are invited to copy to /etc/X11/sessions and customize
if they want that. This is the approach I would personally recommend
for lightdm too.

If the maintainers of lightdm do not want to remove this option, then
I think lightdm should behave like older versions of gdm3: it should
list a "Default Xsession" option *in lightdm only*, without providing
that option in other display managers. To achieve that, please install
/debian/lightdm-xsession.desktop into /usr/share/lightdm/sessions/
(which is already searched by lightdm, as far as I can see) instead of
into /usr/share/xsessions/ (which is searched by all display managers).

Thanks,
smcv

Bug#768376: [Pkg-libvirt-maintainers] Bug#768376: [libvirt-daemon-system]

[Andrei POPESCU]

On Mi, 26 ian 22, 20:30:37, de...@sumpfralle.de wrote:
> Hello,
> 
> given the recent CVE-2021-4034 (gaining local root access via "policykit-1"), 
> I
> would like to raise this request again: it would be great, if the
> libvirt-daemon-system package would reduce its hard dependency ("Depends") on
> "policykit-1" to a soft dependency ("Recommends").
> 
> If I understand your previous comment correctly, then this is technically
> feasible (i.e. "it just works"):
> 
> On Tue, 7 Jul 2015 07:15:06 +0200 Guido Günther  wrote:
> > I do agree that being able to go without polkit would be nice but a
> > similar situation with virt-manger showed that Recommends: are just not
> > enough. Many people skip them and then report bugs if you use Recommends
> > for a package that's needed in 95% of the installations. I'm just not up
> > to handle these.
> 
> 
> I understand, that such bug reports can take effort.
> But I think, the circumstances changed meanwhile (since 2015): "apt" installs
> "Recommends" by default (see `apt-config dump | grep -w Recommends`), thus 
> there
> should be only very few users who are manually overriding this setting.
> And I think, there is a fair chance, that these users know what they are 
> doing.
> 
> The Debian Policy [2] also advises to use "Recommends" in this case.
> 
> Please reduce the "Depends" relationship towards "policykit-1" down to
> "Recommends".
> 
> Thank you for maintaining this package!

Yes!
 
> [1] https://www.debian.org/security/2022/dsa-5059
> [2] https://www.debian.org/doc/debian-policy/ch-relationships.html

This bug came up in a sub-thread on debian-user, also in relation to 
DSA-5059:

https://lists.debian.org/debian-user/2022/01/msg01166.html

Just in case it helps, anecdotally I can confirm that at least on 
debian-user problems due to missing packages that are only Recommends: 
have been both extremely rare in the past years and treated as an 
unsupported configuration.

Hope this helps,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Bug#1004557: man-db: please make index.db installations reproducible

[Colin Watson]

On Sun, Jan 30, 2022 at 02:27:05PM +0100, Johannes Schauer Marin Rodrigues 
wrote:
> currently, the index.db files created by man-db -c are unreproducible
> when creating a Debian chroot. This means that tools that attempt to
> create reproducible system images delete all index.db files:
> 
> https://gitlab.tails.boum.org/tails/tails/-/blob/stable/config/chroot_local-hooks/99-zz_reproducible-builds-post-processing#L28
> https://salsa.debian.org/live-team/live-build/-/blob/master/share/hooks/normal/0190-remove-temporary-files.hook.chroot#L6
> 
> This could be avoided if the index.db files after installation would be
> bit-by-bit reproducible. The attached patch fixes the problem by
> truncating the timestamp set in index.db to the value of
> SOURCE_DATE_EPOCH if the variable is set.
> 
> This means that this patch does not change anything during normal
> operation but only comes into play if a utility that sets
> SOURCE_DATE_EPOCH is installing packages.

I'm a bit confused, because this seems to work at the wrong layer.
Debian packages are supposed to preserve timestamps from the source
package wherever possible, and failing that it would be possible to
ensure that the timestamp of generated manual pages in binary packages
is set to SOURCE_DATE_EPOCH.  Flattening timestamps to an epoch at mandb
time seems like the wrong place for this at first inspection, and I'd
like some clearer rationale for why you ended up with this approach.

I would suggest instead ensuring that mtimes of manual pages are
reproducible, after which mandb should produce reproducible databases
(and if it doesn't I'd consider that a bug).

Deliberately setting database timestamps that don't match the filesystem
will confuse mandb into doing unnecessary work in later runs, so I don't
like this approach.

-- 
Colin Watson (he/him)  [cjwat...@debian.org]

Bug#1003907: fails to successfully associate

[Michael Biebl]

On Wed, 19 Jan 2022 11:13:05 +0100 Michael Biebl  wrote:


I tried the various versions from snapshots.d.o

2:2.9.0-23 - works
2:2.9.0+git20200221+f65da0c-1 - works
2:2.9.0+git20200517+dd2daf0-1 - doesn't work
2:2.9.0+git20210909+a75fdcd-1 - doesn't work
2:2.9.0+git20211018+2e122945fa53-1 - doesn't work
2:2.9.0+git2026+0b853303ae31-1 - doesn't work
2:2.10-1 - doesn't work


I then went on and disabled WPA2+WPA3 mode on the Wi-Fi router and set 
it to WPA2 (CCMP).


After that, the connection was established successfully with 2.10.

If I remember correctly, my hardware doesn't support WPA3, but since I 
enabled support for both WPA2+WPA3, it should fall back to WPA2.


Obviously I'd like to keep WPA3 enabled for newer clients.


https://en.avm.de/service/knowledge-base/dok/FRITZ-Box-7590-AX/509_Wireless-device-cannot-establish-a-connection-to-the-FRITZ-Box/
sounds related:

"
5 Adjusting FRITZ!Box's Wi-Fi security settings

If the wireless device still does not establish a connection to the 
FRITZ!Box, it does not support the modern security functions used by the 
FRITZ!Box. To connect the wireless device anyway, you must adjust the 
security settings in the FRITZ!Box:

Disabling WPA3 transition mode (WPA2 + WPA3)

WPA transition mode allows simultaneous connections with WPA3 and WPA2 
encryption using the same Wi-Fi network name and network key. With 
connections with WPA2 encryption, however, WPA3 transition mode has 
higher security requirements than usual for WPA2 (CCMP).


Some wireless devices cannot establish a Wi-Fi connection if WPA3 
transition mode is enabled. This is the case with iPhones and iPads with 
iOS older than 12.1.1, older wireless printers, IP cameras, and wireless 
plugs, for example:

"

Still curious, why this worked flawlessly with this device with 2.9.0-23

Bug#973812: Bug#973485: gdm3: options for both "System X11 Default" and "Default X11 Session"

[Simon McVittie]

Control: tags -1 + moreinfo

On Thu, 05 Nov 2020 at 11:39:59 +, Simon McVittie wrote:
> Control: retitle -2 gdm3: options for both "System X11 Default" and "Default 
> X11 Session"
> 
> On Thu, 05 Nov 2020 at 11:32:37 +0100, Christoph Berg wrote:
> > I confirm that both the "System X11 Default" and "Default X11 Session"
> > options start my .Xsession file. (Iirc the second option was missing
> > in the old version.)
>
> I don't have this. I currently have options for:
> 
> * System X11 Default
> * GNOME
> [and some others]
> 
> which come from
> 
> * /usr/share/gdm/BuiltInSessions/default.desktop
> * /usr/share/wayland-sessions/gnome.desktop or 
> /usr/share/xsessions/gnome.desktop
> [and some others]

I think I might have found the root cause for this. Do you perhaps have
lightdm installed, even though you are not actively using it?

lightdm installs /usr/share/xsessions/lightdm-xsession.desktop, labelled
"Default Xsession", which starts the traditional x11-common session
(~/.xsessionrc or similar).

Unfortunately, it installs this into a location where *all* display
managers that work like this (including gdm3, sddm, lxdm, slim) will
load that session definition, even though it is not intended for them.

I think this is a lightdm bug (#1004559) and it should either not install
that session definition at all, or install it into a location where only
lightdm will see it (such as /usr/share/lightdm/sessions).

> It isn't ideal that we have an option for "it does something but we
> can't tell you what", but we don't have enough information to do better,
> and even if we could look into individual users' home directories to
> see whether they have ~/.xsession and display that in the greeter,
> that would be an information leak.

Following this logic, I removed the "System X11 Default" option in
gdm3/41.0-1. Instead, there is now an example file
/usr/share/doc/gdm3/examples/custom-x11-session.desktop which can be
copied into /etc/X11/sessions and customized as needed. This is the
method recommended in upstream GNOME documentation for defining local
sessions.

smcv

Bug#1004401: ITP: nicotine -- graphical client for the SoulSeek peer-to-peer system

[Bastian Germann]

On Wed, 26 Jan 2022 22:01:12 +0100 Francois Mazen  wrote:

Someone already opened an RFP, see #966000.


The correct way to express your intend to package would then be retitling and 
owning that RFP bug.

Bug#1004560: konsole: Unable to enter tilde (~) on LXDE

[TimoP]

Package: konsole
Version: 4:20.12.3-1
Severity: important
X-Debbugs-Cc: debian-b...@ig.fi

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
I installed fresh Debian 11 to my fresh laptop. For various
reasons, I want to use Konsole and LXDE. However, with this 
combination (Debian 11, LXDE and Konsole) I'm unable to write
tilde (~). With Finnish keyboard etc a tilde shoud appear
if I press AltGr and key with ^~ and then space. It works as it should
using LX Terminal (with exactly same locale etc settings)

This (Konsole, LXDE, ~) works perfectly with the Debian 10.

   * What was the outcome of this action?
A plain space
   * What outcome did you expect instead?
A tilde
*** End of the template - remove these template lines ***


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

Kernel: Linux 5.10.0-10-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_DK, LC_CTYPE=en_DK (charmap=ISO-8859-1), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages konsole depends on:
ii  kio5.78.0-5
ii  konsole-kpart  4:20.12.3-1
ii  libc6  2.31-13+deb11u2
ii  libkf5configcore5  5.78.0-4
ii  libkf5configwidgets5   5.78.0-2
ii  libkf5coreaddons5  5.78.0-4
ii  libkf5crash5   5.78.0-3
ii  libkf5dbusaddons5  5.78.0-2
ii  libkf5globalaccel-bin  5.78.0-3
ii  libkf5globalaccel5 5.78.0-3
ii  libkf5i18n55.78.0-2
ii  libkf5iconthemes5  5.78.0-2
ii  libkf5kiowidgets5  5.78.0-5
ii  libkf5notifyconfig55.78.0-2
ii  libkf5widgetsaddons5   5.78.0-2
ii  libkf5windowsystem55.78.0-2
ii  libkf5xmlgui5  5.78.0-2
ii  libqt5core5a   5.15.2+dfsg-9
ii  libqt5gui5 5.15.2+dfsg-9
ii  libqt5widgets5 5.15.2+dfsg-9
ii  libstdc++6 10.2.1-6

konsole recommends no packages.

Versions of packages konsole suggests:
pn  lrzsz  

-- no debconf information

Bug#1004522: debian-policy: Proposing new virtual packages: wayland-session, x-session

[Simon McVittie]

On Sat, 29 Jan 2022 at 20:12:21 +, Simon McVittie wrote:
> I propose this entry for virtual-package-names-list.yaml:
> 
> - name: wayland-session
>   description: a Wayland desktop session 
> (/usr/share/wayland-sessions/*.desktop)

Having looked more closely at display managers, I think we should also
consider adding:

- name: x-session
  description: an X11 desktop session registered via 
/usr/share/xsessions/*.desktop

because there are three common ways for an x-display-manager to choose what
sessions to offer:

1. Older or simpler display managers (xdm, nodm) unconditionally run
   /etc/X11/Xsession or equivalent, which results in running ~/.xsessionrc,
   /etc/alternatives/x-session-manager or various similar things

2. Newer display managers (gdm3, sddm, slim, lxdm) look for Wayland
   sessions and/or X11 sessions represented by .desktop files in various
   locations[1], of which the most suitable for distribution packagers are
   /usr/share/xsessions and /usr/share/wayland-sessions

3. Some of the .desktop-based display managers (lightdm and historically
   gdm3) additionally install their own .desktop file to make the
   xdm-style /etc/X11/Xsession or equivalent (from 1.) appear in the menu
   of .desktop files (from 2.)

If a display manager is in category 1, it would be appropriate for it to
depend on x-session-manager | x-window-manager | x-terminal-emulator.

However, if a display manager is in category 2, then that dependency is
actually incorrect, because not every x-window-manager is designed to
be usable as a desktop session in its own right (some of them are just
components of a larger desktop environment, like KDE's kwin-x11 as a
component of the Plasma desktop), and therefore not every x-window-manager
has (or should have!) a file in /usr/share/xsessions/*.desktop.

Strictly speaking I don't think there's any guarantee that every
x-session-manager has /usr/share/xsessions/*.desktop either, although
it seems to be 90% true for current packages in unstable[2].

So I think x-display-manager implementations in category 2 should be
depending on [their preferred session] | wayland-session | x-session
(omitting wayland-session if they are X11-only), perhaps with
x-session-manager as an additional alternative for backwards compatibility.

Alternatively, display managers could relax that dependency to a Recommends
or Suggests, or omit it completely (in fact this seems to be what most
display managers do at the moment). However, gdm3 has historically had a
dependency on something resembling a desktop environment, and I would not
want to drop that dependency unless there is consensus that installing
gdm3, without also installing a desktop environment that it can log into,
is a sysadmin error rather than a bug in gdm3.

I tested all x-display-manager implementations in sid and it looks like
they break down like this:

1. traditional /etc/X11/Xsession: xdm, nodm
1a. /etc/X11/Xsession plus a hard-coded list of extra options?: wdm
2. xsessions/*.desktop: gdm3, sddm, slim, lxdm
3. combining (1.) and (2.): lightdm

I think category 3 leads to a bad user experience, which is why I removed
the equivalent from gdm3: the display manager cannot predict what will
happen if /etc/X11/Xsession is chosen, so it has to name the option
something very general, like lightdm's "Default Xsession" or older gdm3
versions' "System X11 Default". This is particularly misleading if the
display manager actually has a different default, as gdm3 has done since
the switch to Wayland-by-default. (See also lightdm bug #1004559.)

smcv

[1] For example gdm3 currently searches /usr/{,local/}share/xsessions,
/etc/X11/sessions, /etc/gdm3/Sessions, /usr/share/gdm/BuiltInSessions
and /usr/{,local/}share/wayland-sessions, some of which are gdm-specific
[2] cinnamon-session Provides x-session-manager, but
/usr/share/xsessions/cinnamon.desktop is in cinnamon-common, a
"larger" package.
lxsession Provides x-session-manager, but
/usr/share/xsessions/LXDE.desktop is in openbox-lxde-session, again
a "larger" package.

Bug#1004561: lazarus: autopkgtest regression on all architectures

[Adrian Bunk]

Source: lazarus
Version: 2.2.0+dfsg1-4
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/l/lazarus/18809201/log.gz

...
TExternalToolsConsole.HandleMesages: Calling CheckSynchronize!
/tmp/autopkgtest-lxc.dnt01_gt/downtmp/build.RVT/src/debian/tests/build-lpk-lpi: 
36: Syntax error: ";;" unexpected (expecting "fi")
autopkgtest [03:21:52]: test build-lpk-lpi: ---]
autopkgtest [03:21:52]: test build-lpk-lpi:  - - - - - - - - - - results - - - 
- - - - - - -
build-lpk-lpiFAIL non-zero exit status 2

Bug#1004023: new mender-artifact build log fail with old gcp

[Andreas Henriksson]

For the record,

Here's the relevant error message when building newer mender-artifact (3.7.0) 
with older dependencies from unstable:

```
# github.com/mendersoftware/mender-artifact/artifact/gcp
src/github.com/mendersoftware/mender-artifact/artifact/gcp/signer.go:81:3: 
unknown field 'DigestCrc32C' in struct literal of type 
"google.golang.org/genproto/googleapis/cloud/kms/v1".AsymmetricSignRequest
src/github.com/mendersoftware/mender-artifact/artifact/gcp/signer.go:86:12: 
result.VerifiedDigestCrc32C undefined (type 
*"google.golang.org/genproto/googleapis/cloud/kms/v1".AsymmetricSignResponse 
has no field or method VerifiedDigestCrc32C)
src/github.com/mendersoftware/mender-artifact/artifact/gcp/signer.go:89:41: 
result.SignatureCrc32C undefined (type 
*"google.golang.org/genproto/googleapis/cloud/kms/v1".AsymmetricSignResponse 
has no field or method SignatureCrc32C)
src/github.com/mendersoftware/mender-artifact/artifact/gcp/signer.go:140:47: 
response.PemCrc32C undefined (type 
*"google.golang.org/genproto/googleapis/cloud/kms/v1".PublicKey has no field or 
method PemCrc32C)
dh_auto_build: error: cd obj-x86_64-linux-gnu && go install -trimpath -v -p 5 
-ldflags "-X github.com/mendersoftware/mender-artifact/cli.Version=3.7.0+ds1-1" 
github.com/mendersoftware/mender-artifact 
github.com/mendersoftware/mender-artifact/areader 
github.com/mendersoftware/mender-artifact/artifact 
github.com/mendersoftware/mender-artifact/artifact/gcp 
github.com/mendersoftware/mender-artifact/artifact/stage 
github.com/mendersoftware/mender-artifact/awriter 
github.com/mendersoftware/mender-artifact/cli 
github.com/mendersoftware/mender-artifact/cli/util 
github.com/mendersoftware/mender-artifact/handlers 
github.com/mendersoftware/mender-artifact/utils returned exit code 2
make[1]: *** [debian/rules:15: override_dh_auto_build] Error 25
make[1]: Leaving directory 
'/build/golang-github-mendersoftware-mender-artifact-3.7.0+ds1'
```

Regards,
Andreas Henriksson

Bug#1004522: debian-policy: Proposing new virtual package: wayland-session

[Andrei POPESCU]

On Du, 30 ian 22, 13:21:40, Stephan Lachnit wrote:
> 
> On Sat, 29 Jan 2022, 21:15 Simon McVittie,  wrote:
> >
> > According to `apt-file search`, it should initially be provided by these:
> >
> > gnome-session: /usr/share/wayland-sessions/gnome.desktop
> > phosh: /usr/share/wayland-sessions/phosh.desktop
> > plasma-workspace-wayland: /usr/share/wayland-sessions/plasmawayland.desktop
> > sway: /usr/share/wayland-sessions/sway.desktop
> > weston: /usr/share/wayland-sessions/weston.desktop
>
> I like the idea. Just another idea for the naming, about
> wayland-desktop-session?

It's longer and Phosh is not exactly a "desktop" ;)

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Bug#1004562: libguestfs: autopkgtest regression

[Adrian Bunk]

Source: libguestfs
Version: 1:1.46.2-11
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/libg/libguestfs/18786402/log.gz

...
+ ssh -oUserKnownHostsFile=/dev/null -oStrictHostKeyChecking=no -i id_rsa -T -p 
10022 -o ConnectTimeout=5 root@localhost echo success
Connection timed out during banner exchange
Connection to 127.0.0.1 port 10022 timed out
+ rv=1
+ [ 1 -eq 0 ]
+ sleepenh 1643405863.414064 5
+ [ 1 -eq 1 ]
+ TIMESTAMP=1643405868.414064
+ i=39
+ [ 39 -ge 40 ]
+ true
+ rv=0
+ ssh -oUserKnownHostsFile=/dev/null -oStrictHostKeyChecking=no -i id_rsa -T -p 
10022 -o ConnectTimeout=5 root@localhost echo success
Connection timed out during banner exchange
Connection to 127.0.0.1 port 10022 timed out
+ rv=1
+ [ 1 -eq 0 ]
+ sleepenh 1643405868.414064 5
+ [ 1 -eq 1 ]
+ TIMESTAMP=1643405873.414064
+ i=40
+ [ 40 -ge 40 ]
+ break
+ [ 40 -eq 40 ]
+ echo timeout reached: unable to connect to qemu via ssh
+ exit 1
+ cat --show-nonprinting qemu.log
+ kill 26114
autopkgtest [21:37:54]:  summary
extlinux FAIL non-zero exit status 1

Bug#1004565: [memtest86] Stable hangs just after starting

[Roman Savochenko]

Package: memtest86+, memtest86
Version: 5.01-3.1, 4.3.7-3+b1
Severity: important

--- Please enter the report below this line. ---
The memory testing hangs just after starting on Test 2 progress from 20 
to 40 percent and on all hardware seems, in my case that is Intel 
i7-5600U and AMD A8-6500.


memtest86+ versions from Debian 10,9,8,7 work correctly.

--- System information. ---
Debian Release: 11.2

Bug#1001830: transition: libtorrent-rasterbar

[Sebastian Ramacher]

Control: tags -1 confirmed

On 2022-01-28 11:36:55 +0100, Sebastian Ramacher wrote:
> Hi
> 
> On 2022-01-28 10:13:31, Christian Marillat wrote:
> > Hi,
> > 
> > libtorrent-rasterbar 2.0.5 is now in experimental.
> > 
> > The moreinfo tag has been removed.
> > 
> > libtorrent-rasterbar build for all release arches except mips64el and
> > mipsel (Needs-Build).
> > 
> > Should we wait for these arches to start the transition ?
> 
> Yes. Before starting the transition we want to be sure that there are at
> least no build regression on those architectures for
> libtorrent-rasterbar. But as we are currently rebuilding hundreds of
> packages for #1004272, the buildds are busy.

libtorrent-rasterbar was built successfully on mips*el. Please go ahead.

Cheers

> 
> Cheers
> -- 
> Sebastian Ramacher
> 

-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#1004566: wesnoth-1.16-data: '/usr/share/icons/HighContrast/scalable/apps/wesnoth-icon.svg', which is also in package wesnoth-1.14-data 1:1.14.17-2

[Jean-Marc]

Package: wesnoth-1.16-data
Version: 1:1.16.1-1
Severity: grave
Tags: a11y
Justification: renders package unusable

Dear Maintainer,

During the upgrade from wesnoth-1.14 to wesnoth-1.16 in sid, I got the 
following message:

Unpacking wesnoth-1.16-data (1:1.16.1-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/wesnoth-1.16-data_1%3a1.16.1-1_all.deb (--unpack):
 trying to overwrite 
'/usr/share/icons/HighContrast/scalable/apps/wesnoth-icon.svg', which is also 
in package wesnoth-1.14-data 1:1.14.17-2
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

It broke the upgrade in the middle.

I guess it will be solved in first removing wesnoth-1.14* packages and running 
an 'apt --fix-broken install'.

Regards,

Jean-Marc


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.15.0-3-amd64 (SMP w/8 CPU threads)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages wesnoth-1.16-data depends on:
ii  fonts-adf-oldania 0.20190904-2
ii  fonts-dejavu-core 2.37-2
ii  fonts-dejavu-extra2.37-2
ii  fonts-droid-fallback  1:6.0.1r16-1.1
ii  fonts-lato2.0-2.1

wesnoth-1.16-data recommends no packages.

Versions of packages wesnoth-1.16-data suggests:
iu  wesnoth-1.16-music  1:1.16.1-1

Bug#1003907: fails to successfully associate

[Michael Biebl]

Since I could easily reproduce it, I ran git bisect.

7a9c36722511ce4df88b76cceceb241d6c6a151e is the first bad commit
commit 7a9c36722511ce4df88b76cceceb241d6c6a151e
Author: Brian Norris 
Date:   Fri Feb 28 15:50:47 2020 -0800

DBus: Add "sae" to interface key_mgmt capabilities

This will be present when the driver supports SAE and it's included in
the wpa_supplicant build.

Signed-off-by: Brian Norris 


Reverting that commit on top of 2.10 I was again able to successfully 
establish a connection.


The debian build uses CONFIG_SAE=y.
Is it possible that wpasupplicant reports that the driver (iwlwifi) 
supports SAE but my hardware does not actually support SAE?


https://www.intel.com/content/www/us/en/support/articles/54783/wireless.html

My network controller is an "Intel Corporation Centrino Advanced-N 6205"


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1004567: libnzb: Should the package be removed?

[Boyuan Yang]

Source: libnzb
Severity: important
Version: 0.0.20050629-6.2
X-Debbugs-CC: mnord...@debian.org

Dear Debian libnzb package maintainer,

I noticed that package libnzb received no maintainer upload in the past 11
years, and that this package is unmaintained by its upstream. Since no other
package (including nzb) depends on it, perhaps we should have it removed.

Please feel free to let me know if you have any ideas. I will open a removal
bug to FTP Masters if there's no other issues.

Thanks,
Boyuan Yang


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

Bug#692765: Weird table rendering in translated page

[Colin Watson]

Control: reassign -1 src:manpages-l10n
Control: clone -1 -2
Control: reassign -2 manpages

On Thu, Nov 08, 2012 at 12:37:39PM -0400, David Prévot wrote:
> The last table (decimal) rendering of ascii(7) is weird: the 3 and 6
> lines not aligned correctly:
> 
> v   v
>3: # 3 C S c s 3: ! +  5  ? I  S  ]  g   q   {
>4: $ 4 D T d t 4: "  ,  6  @  J  T  ^  h   r   |
>5: % 5 E U e u 5: #  -  7  A  K  U  _  i   s   }
>6: & 6 F V f v 6: $  . 8  B  L  V  `  j   t   ~
>  ^ 
> instead of:
> 
>3: # 3 C S c s 3: !  +  5  ?  I  S  ]  g   q   {
>4: $ 4 D T d t 4: "  ,  6  @  J  T  ^  h   r   |
>5: % 5 E U e u 5: #  -  7  A  K  U  _  i   s   }
>6: & 6 F V f v 6: $  .  8  B  L  V  `  j   t   ~
> 
> I can reproduce it on Wheezy and Sid for the French (from manpages-fr)
> and German (from manpages-de) translations of ascii(7). The layout is
> also broken when displaying it from its full path
> (/usr/share/man/fr/man7/ascii.7.gz), but it displays fine after copying
> the page to another place (e.g. to /tmp). Please find attach the diff
> between the two debug output in case you notice something interesting
> (I'd bet on the page_encoding, but am not aware of man internals).

Only nine years later, I finally got round to investigating this.  (I
think I'd tried to look before but been stumped.)  Sorry for the long
delay!

When you display a page from its normal locale-specific directory, man
automatically loads the corresponding set of locale macros provided by
groff.  In this case (and for several other languages), that includes:

  .ss 12 0

That changes the amount of space inserted after end-of-sentence
characters, which by default are '!', '?', and '.'.  As it happens,
those are exactly the characters after which the table rendering has
gone wrong above.

I think the following patch is probably the best approach: it puts a
zero-width character after characters that would otherwise be
misinterpreted as an end-of-sentence character, which is groff's
documented way to prevent misinterpretation of those characters.  It's
possible that some other approach would work as well, but this is simple
enough.  I hope it's clear how to apply this to the corresponding tables
in other languages.

I've reassigned the primary bug here to src:manpages-l10n (covering
manpages-fr, manpages-de, etc.) since this typically goes wrong in
translation, but I think it would be a good idea to do the same thing in
the base ascii(7) page in manpages as a defensive measure against
translators not being aware of this subtle detail, so I've reassigned a
clone of this bug to manpages as well.

--- ascii.7.orig
+++ ascii.7
@@ -141,10 +141,10 @@
 0:   0 @ P \` p 0:(  2  <  F  P  Z  d   n   x
 1: ! 1 A Q a q 1:)  3  =  G  Q  [  e   o   y
 2: " 2 B R b r 2:*  4  >  H  R  \e  f   p   z
-3: # 3 C S c s 3: !  +  5  ?  I  S  ]  g   q   {
+3: # 3 C S c s 3: !\&  +  5  ?\&  I  S  ]  g   q   {
 4: $ 4 D T d t 4: "  ,  6  @  J  T  \(ha  h   r   |
 5: % 5 E U e u 5: #  \-  7  A  K  U  _  i   s   }
-6: & 6 F V f v 6: $  .  8  B  L  V  \`  j   t   \(ti
+6: & 6 F V f v 6: $  .\&  8  B  L  V  \`  j   t   \(ti
 7: \(aq 7 G W g w 7: %  /  9  C  M  W  a  k   u  DEL
 8: ( 8 H X h x 8: &  0  :  D  N  X  b  l   v
 9: ) 9 I Y i y 9: \(aq  1  ;  E  O  Y  c  m   w

Let me know if you have any other questions about this, and I'll try to
reply in slightly less than nine years this time.

-- 
Colin Watson (he/him)  [cjwat...@debian.org]

Bug#1004537: exim4: Does not reload expiring TLS certificate; clients cannot connect

[Marc Haber]

severity #1004537 minor
thanks

On Sun, Jan 30, 2022 at 10:43:02AM +0200, Harri Suutari wrote:
> During long server uptime TLS certificate can expire and clients cannot 
> connect
> anymore. For example Let's Encrypt offers only three months valid time for
> certificates.
> 
>  Manual fix if is to restart the server manually or by Cron, but maybe this
> should be handled as default by the package configuration.

Not even Apache reloads automatically.

Restarting the mail server can trivially be accomplished by the process
that renews the certificate.

I don't see this as a bug or an item that is worth spending developer
time on.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1004557: man-db: please make index.db installations reproducible

[Johannes Schauer Marin Rodrigues]

Hi Colin,

thank you for your quick reply! :)

Quoting Colin Watson (2022-01-30 15:03:30)
> On Sun, Jan 30, 2022 at 02:27:05PM +0100, Johannes Schauer Marin Rodrigues 
> wrote:
> > currently, the index.db files created by man-db -c are unreproducible
> > when creating a Debian chroot. This means that tools that attempt to
> > create reproducible system images delete all index.db files:
> > 
> > https://gitlab.tails.boum.org/tails/tails/-/blob/stable/config/chroot_local-hooks/99-zz_reproducible-builds-post-processing#L28
> > https://salsa.debian.org/live-team/live-build/-/blob/master/share/hooks/normal/0190-remove-temporary-files.hook.chroot#L6
> > 
> > This could be avoided if the index.db files after installation would be
> > bit-by-bit reproducible. The attached patch fixes the problem by
> > truncating the timestamp set in index.db to the value of
> > SOURCE_DATE_EPOCH if the variable is set.
> > 
> > This means that this patch does not change anything during normal
> > operation but only comes into play if a utility that sets
> > SOURCE_DATE_EPOCH is installing packages.
> 
> I'm a bit confused, because this seems to work at the wrong layer.
> Debian packages are supposed to preserve timestamps from the source
> package wherever possible, and failing that it would be possible to
> ensure that the timestamp of generated manual pages in binary packages
> is set to SOURCE_DATE_EPOCH.  Flattening timestamps to an epoch at mandb
> time seems like the wrong place for this at first inspection, and I'd
> like some clearer rationale for why you ended up with this approach.
> 
> I would suggest instead ensuring that mtimes of manual pages are
> reproducible, after which mandb should produce reproducible databases
> (and if it doesn't I'd consider that a bug).
> 
> Deliberately setting database timestamps that don't match the filesystem
> will confuse mandb into doing unnecessary work in later runs, so I don't like
> this approach.

My reasoning was, that tools that care about reproducible index.db will
"flatten" the mtimes to SOURCE_DATE_EPOCH in the tarball or image they produce,
so setting the timestamp in index.db to SOURCE_DATE_EPOCH for those timestamps
larger than SOURCE_DATE_EPOCH seemed like the approach that would result in a
consistent overall state.

But if that's the wrong approach, lets think of the alternative: making sure
that the mtimes of manual pages is reproducible. If I use gdbm_dump on the
index.db of two different chroots, then it looks like the following manual pages
have differing timestamps:

bash-builtins, which, dash, mawk, pager, awk, sh, more, nawk, builtins

Most of those seem to be symlinks into /etc/alternatives and those symlinks get
created by maintainer scripts using update-alternatives. Are you suggesting
that update-alternatives should gain support for setting the mtime of the files
it creates to SOURCE_DATE_EPOCH?

I'm puzzled by bash-builtins though because that one is not a symlink. So I
don't understand why the timestamp differs there.

Thanks!

cheers, josch

signature.asc
Description: signature

Bug#1004570: indi-webcam: FTBFS with ffmpeg 5.0

[Sebastian Ramacher]

Source: indi-webcam
Version: 1.0+20220129131520-1
Severity: important
Tags: sid bookworm ftbfs
X-Debbugs-Cc: sramac...@debian.org
Usertags: ffmpeg5.0

indi-webcam FTBFS with ffmpeg 5.0 (available in experimental):
| [ 50%] Building CXX object CMakeFiles/indi_webcam_ccd.dir/indi_webcam.cpp.o
| /usr/lib/ccache/c++  -I/<>/obj-x86_64-linux-gnu 
-I/<> -I/usr/include/libindi -g -std=c++0x -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-Wno-deprecated-declarations -MD -MT 
CMakeFiles/indi_webcam_ccd.dir/indi_webcam.cpp.o -MF 
CMakeFiles/indi_webcam_ccd.dir/indi_webcam.cpp.o.d -o 
CMakeFiles/indi_webcam_ccd.dir/indi_webcam.cpp.o -c 
/<>/indi_webcam.cpp
| /<>/indi_webcam.cpp: In member function ‘void 
indi_webcam::findAVFoundationVideoSources()’:
| /<>/indi_webcam.cpp:128:50: error: invalid conversion from 
‘const AVInputFormat*’ to ‘AVInputFormat*’ [-fpermissive]
|   128 | AVInputFormat *iformat = av_find_input_format("avfoundation");
|   |  ^~~~
|   |  |
|   |  const AVInputFormat*
| /<>/indi_webcam.cpp: In constructor ‘indi_webcam::indi_webcam()’:
| /<>/indi_webcam.cpp:157:3: error: ‘av_register_all’ was not 
declared in this scope
|   157 |   av_register_all();
|   |   ^~~
| /<>/indi_webcam.cpp:161:3: error: ‘avcodec_register_all’ was not 
declared in this scope; did you mean ‘avdevice_register_all’?
|   161 |   avcodec_register_all();
|   |   ^~~~
|   |   avdevice_register_all
| /<>/indi_webcam.cpp: In member function ‘bool 
indi_webcam::ConnectToSource(std::string, std::string, int, std::string, 
std::string)’:
| /<>/indi_webcam.cpp:247:39: error: invalid conversion from 
‘const AVInputFormat*’ to ‘AVInputFormat*’ [-fpermissive]
|   247 | iformat = av_find_input_format(device.c_str());
|   |   ^~~~
|   |   |
|   |   const AVInputFormat*
| /<>/indi_webcam.cpp:290:32: error: invalid conversion from 
‘const AVCodec*’ to ‘AVCodec*’ [-fpermissive]
|   290 | 
pCodec=avcodec_find_decoder(pFormatCtx->streams[videoStream]->codecpar->codec_id);
|   |
^~
|   ||
|   |const AVCodec*
| /<>/indi_webcam.cpp: In member function ‘bool 
indi_webcam::refreshInputDevices()’:
| /<>/indi_webcam.cpp:513:43: error: invalid conversion from 
‘const AVInputFormat*’ to ‘AVInputFormat*’ [-fpermissive]
|   513 | while ((d = av_input_video_device_next(d))) {
|   | ~~^~~
|   |   |
|   |   const AVInputFormat*
| /<>/indi_webcam.cpp: In member function ‘int 
indi_webcam::getNumOfInputDevices()’:
| /<>/indi_webcam.cpp:534:43: error: invalid conversion from 
‘const AVInputFormat*’ to ‘AVInputFormat*’ [-fpermissive]
|   534 | while ((d = av_input_video_device_next(d)))
|   | ~~^~~
|   |   |
|   |   const AVInputFormat*
| /<>/indi_webcam.cpp: In member function ‘bool 
indi_webcam::refreshInputSources()’:
| /<>/indi_webcam.cpp:578:54: error: invalid conversion from 
‘const AVInputFormat*’ to ‘AVInputFormat*’ [-fpermissive]
|   578 | AVInputFormat *iformat = 
av_find_input_format(videoDevice.c_str());
|   |  
^
|   |  |
|   |  const 
AVInputFormat*
| make[3]: *** [CMakeFiles/indi_webcam_ccd.dir/build.make:79: 
CMakeFiles/indi_webcam_ccd.dir/indi_webcam.cpp.o] Error 1

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#1004571: ITP: python-pytest-click

[Jerome Charaoui]

Package: wnpp
Severity: wishlist
Owner: Jerome Charaoui 

  Package name : python-pytest-click
  Version  : 1.0.2
  Upstream author  : Dmitry Dygalo 
  URL  : https://github.com/Stranger6667/pytest-click
  License  : MIT
  Programming Lang : Python
  Description  : Click plugin for py.test

Click is a Python package for creating beautiful command line interfaces 
in a composable way with as little code as necessary. pytest-click 
provides fixtures for easy integration with the py.test framework.


Thanks,

-- Jerome


OpenPGP_signature
Description: OpenPGP digital signature

Bug#294919: libgd2-noxpm-dev: Allow const strings to be passed to gdImageStringFT()

[Florian Ernst]

On Sat, Feb 12, 2005 at 01:51:42PM +0100, Petter Reinholdtsen wrote:
> At the moment, the gcc will issue a warning when using gdImageStringFT()
> with const strings.  I discovered this while compiling mapserver with
> lots of warning flags.
> 
> The declaration in /usr/include/gd.h currently look like this:
> 
>   /* FreeType 2 text output */
>   BGD_DECLARE(char *) gdImageStringFT (gdImage * im, int *brect, int fg,
>  char *fontlist, double ptsize, double angle, int x,
>  int y, char *string);
> 
> The problem is the use of 'char *' instead of 'const char *'.  This
> example program demonstrate the problem.  As far as I can see, the
> code do not write to the strings, so it should be safe to convert the
> function to use 'const char *'.

FWIW, as of gd-2.3.0 the function accepts 'const char *', cf.
,
and I can confirm that with libgd-dev_2.3.0-2 Petter's example program
does not trigger any gcc warnings anymore.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1004572: libgd2: New upstream release (2.3.3, 2021 Sep 12)

[Florian Ernst]

Source: libgd2
Version: 2.3.0-2
Severity: wishlist

Dear maintainer,

there are new upstream releases available, cf.
.

The most recent 2.3.3 supposedly fixes 
(CVE-2021-38115) and seems to contain some more worthwhile fixes, the
full Changelog reads:

| ## [2.3.3] - 2021-09-12
| 
| ### Fixed
| 
| - [#759](https://github.com/libgd/libgd/issues/759) update cmake to generate 
config.h in the build dir
| - [#756](https://github.com/libgd/libgd/issues/756) 2.3.3 release
| - [#750](https://github.com/libgd/libgd/issues/750) gdPutBuf return value 
check
| - [#729](https://github.com/libgd/libgd/issues/729) HEIF builds fail with 
latest distros
| - [#678](https://github.com/libgd/libgd/issues/678) segfault in heif tests 
due to missing label.heic
| - [#677](https://github.com/libgd/libgd/issues/677) Test failure 
avif/compare_avif_to_png with libavif-0.8.2
| - [#661](https://github.com/libgd/libgd/issues/661) imagecopyresampled() 
produce artifacts on transparent PNG
| - [#611](https://github.com/libgd/libgd/issues/611) Fixes to build v2.3.0 on 
Windows with MinGW-w64
| - [#415](https://github.com/libgd/libgd/issues/415) optimize option in gif 
animation causes segfault
| - [#331](https://github.com/libgd/libgd/issues/331) _gdContributionsCalc() 
always uses DEFAULT_BOX_RADIUS
| - [#320](https://github.com/libgd/libgd/issues/320) 
gdImageRotateInterpolated() converts the source image to truecolor
| - [#249](https://github.com/libgd/libgd/issues/249) CMake and Makefiles build 
broken on Windows
| - [#93 ](https://github.com/libgd/libgd/issues/93) gdImageScaleTwoPass() 
looses top row and left column
| 
| ## [2.3.2] - 2021-03-06
| 
| ### Fixed
| 
| - gif: allow decodin when both Global and Local Colormaps (#494)
| 
| ### Added
| 
| - avif: Support for AVIF images via libavif (#557)
| - heif: Support for HEIF/AVIF images via libheif (#395) (#557)
| - webp: Drop ../deps/ search when building with cmake
| - Windows: Remove unused snprintf fallback
| 
| ## [2.3.1] - 2021-01-30
| 
| ### Fixed
| 
| - Fix potential integer overflow detected by oss-fuzz
| - Fix #615 using libraqm
| - Fix #303: gdlib.pc: use Requires instead of Libs (#537)
| - Fixed #472: Adjusting CMakeLists.txt (#582)
| - Fix #615: gdImageStringFT() fails for empty strings as of libgd 2.3.0 (#633)
| - Fix typo but preserve BC
| - Compute average in gdGuessBackgroundColorFromCorners properly (#483)
| - CMakeLists.txt: zlib is enabled implicitly
| - src/config.h.cmake: replace #cmakedefine01 with #define in macro 
ENABLE_GD_FOORMATS (#622)
| - gdlib.pc: use prefixes for pkgconfig file
| - cmake: remove required host includes (#617)
| - Move initial declaration out of `for` loop
| - distribute getlib script
| - Make gd_nnquant.c less likely to introduce duplicate definitions (#601)
| - webp: support pkg-config file
| - gd_io: replace internal Putchar with gdPutC
| - gd_io: trim unused Putword function
| 
| ### Added
| 
| - Add REQUIRED to FIND_PACKAGE(ZLIB)
| - README: add some libraries info (#631)
| - VMS/README.VMS: Add dropping support information (#614)

Please update the package when you think it is due time.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1004573: ocaml-ffmpeg: FTBFS with ffmpeg 5.0

[Sebastian Ramacher]

Source: ocaml-ffmpeg
Version: 1.1.1-1
Severity: important
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs
Usertags: ffmpeg5.0

ocaml-ffmpeg FTBFS with ffmpeg 5.0 (available in experimental):
| x86_64-linux-gnu-gcc avdevice/avdevice_stubs.o
| In file included from avdevice_stubs.c:5:
| avdevice_stubs.c: In function ‘ocaml_avdevice_get_audio_input_formats’:
| avdevice_stubs.c:49:32: warning: passing argument 1 of ‘get_input_devices’ 
from incompatible pointer type [-Wincompatible-pointer-types]
|49 |   CAMLreturn(get_input_devices(av_input_audio_device_next));
|   |^~
|   ||
|   |const AVInputFormat * (*)(const 
AVInputFormat *)
| /usr/lib/ocaml/caml/memory.h:460:29: note: in definition of macro 
‘CAMLreturnT’
|   460 |   type caml__temp_result = (result); \
|   | ^~
| avdevice_stubs.c:49:3: note: in expansion of macro ‘CAMLreturn’
|49 |   CAMLreturn(get_input_devices(av_input_audio_device_next));
|   |   ^~
| avdevice_stubs.c:23:36: note: expected ‘AVInputFormat * (*)(AVInputFormat *)’ 
but argument is of type ‘const AVInputFormat * (*)(const AVInputFormat *)’
|23 | get_input_devices(AVInputFormat *(*input_device_next)(AVInputFormat 
*)) {
|   |   ~^~~
| In file included from avdevice_stubs.c:5:
| avdevice_stubs.c: In function ‘ocaml_avdevice_get_video_input_formats’:
| avdevice_stubs.c:54:32: warning: passing argument 1 of ‘get_input_devices’ 
from incompatible pointer type [-Wincompatible-pointer-types]
|54 |   CAMLreturn(get_input_devices(av_input_video_device_next));
|   |^~
|   ||
|   |const AVInputFormat * (*)(const 
AVInputFormat *)
| /usr/lib/ocaml/caml/memory.h:460:29: note: in definition of macro 
‘CAMLreturnT’
|   460 |   type caml__temp_result = (result); \
|   | ^~
| avdevice_stubs.c:54:3: note: in expansion of macro ‘CAMLreturn’
|54 |   CAMLreturn(get_input_devices(av_input_video_device_next));
|   |   ^~
| avdevice_stubs.c:23:36: note: expected ‘AVInputFormat * (*)(AVInputFormat *)’ 
but argument is of type ‘const AVInputFormat * (*)(const AVInputFormat *)’
|23 | get_input_devices(AVInputFormat *(*input_device_next)(AVInputFormat 
*)) {
|   |   ~^~~
| In file included from avdevice_stubs.c:5:
| avdevice_stubs.c: In function ‘ocaml_avdevice_get_audio_output_formats’:
| avdevice_stubs.c:83:33: warning: passing argument 1 of ‘get_output_devices’ 
from incompatible pointer type [-Wincompatible-pointer-types]
|83 |   CAMLreturn(get_output_devices(av_output_audio_device_next));
|   | ^~~
|   | |
|   | const AVOutputFormat * (*)(const 
AVOutputFormat *)
| /usr/lib/ocaml/caml/memory.h:460:29: note: in definition of macro 
‘CAMLreturnT’
|   460 |   type caml__temp_result = (result); \
|   | ^~
| avdevice_stubs.c:83:3: note: in expansion of macro ‘CAMLreturn’
|83 |   CAMLreturn(get_output_devices(av_output_audio_device_next));
|   |   ^~
| avdevice_stubs.c:58:38: note: expected ‘AVOutputFormat * (*)(AVOutputFormat 
*)’ but argument is of type ‘const AVOutputFormat * (*)(const AVOutputFormat *)’
|58 | get_output_devices(AVOutputFormat 
*(*output_device_next)(AVOutputFormat *)) {
|   |
~~^
| In file included from avdevice_stubs.c:5:
| avdevice_stubs.c: In function ‘ocaml_avdevice_get_video_output_formats’:
| avdevice_stubs.c:88:33: warning: passing argument 1 of ‘get_output_devices’ 
from incompatible pointer type [-Wincompatible-pointer-types]
|88 |   CAMLreturn(get_output_devices(av_output_video_device_next));
|   | ^~~
|   | |
|   | const AVOutputFormat * (*)(const 
AVOutputFormat *)
| /usr/lib/ocaml/caml/memory.h:460:29: note: in definition of macro 
‘CAMLreturnT’
|   460 |   type caml__temp_result = (result); \
|   | ^~
| avdevice_stubs.c:88:3: note: in expansion of macro ‘CAMLreturn’
|88 |   CAMLreturn(get_output_devices(av_output_video_device_next));
|   |   ^~
| avdevice_stubs.c:58:38: note: expected ‘AVOutputFormat * (*)(AVOutputFormat 
*)’ but argument is of type ‘const AVOutputFormat * (*)(const AVOutputFormat *)’
|58 | get_output_devices(AVOutputFormat 
*(*output_device_next)(AVOutputFormat *)) {
|   |  

Bug#1004574: rbdoom3bfg: FTBFS with ffmpeg 5.0

[Sebastian Ramacher]

Source: rbdoom3bfg
Version: 1.3.0+dfsg-2
Severity: important
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs
Usertags: ffmpeg5.0

rbdoom3bfg FTBFS with ffmpeg 5.0 (available in experimental):
| /<>/neo/renderer/Cinematic.cpp:239:9: error: 
‘avcodec_register_all’ was not declared in this scope
|   239 | avcodec_register_all();
|   | ^~~~
| /<>/neo/renderer/Cinematic.cpp:240:9: error: ‘av_register_all’ 
was not declared in this scope
|   240 | av_register_all();
|   | ^~~
| /<>/neo/renderer/Cinematic.cpp: In member function ‘bool 
idCinematicLocal::InitFromFFMPEGFile(const char*, bool)’:
| /<>/neo/renderer/Cinematic.cpp:588:73: error: invalid conversion 
from ‘AVCodec**’ to ‘const AVCodec**’ [-fpermissive]
|   588 | ret = av_find_best_stream( fmt_ctx, AVMEDIA_TYPE_VIDEO, -1, 
-1, &dec, 0 );
|   |   
  ^~~~
|   |   
  |
|   |   
  AVCodec**
| In file included from /<>/neo/renderer/Cinematic.cpp:64:
| /usr/include/x86_64-linux-gnu/libavformat/avformat.h:2161:41: note:   
initializing argument 5 of ‘int av_find_best_stream(AVFormatContext*, 
AVMediaType, int, int, const AVCodec**, int)’
|  2161 | const AVCodec **decoder_ret,
|   | ^~~
| /<>/neo/renderer/Cinematic.cpp:595:57: error: ‘AVStream’ {aka 
‘struct AVStream’} has no member named ‘codec’
|   595 | dec_ctx = fmt_ctx->streams[video_stream_index]->codec;
|   | ^
| /<>/neo/renderer/Cinematic.cpp:630:27: error: ‘AVPicture’ was 
not declared in this scope; did you mean ‘AVPictureType’?
|   630 | avpicture_fill( ( AVPicture* )frame2, image, 
AV_PIX_FMT_BGR32, CIN_WIDTH, CIN_HEIGHT );
|   |   ^
|   |   AVPictureType
| /<>/neo/renderer/Cinematic.cpp:630:38: error: expected 
primary-expression before ‘)’ token
|   630 | avpicture_fill( ( AVPicture* )frame2, image, 
AV_PIX_FMT_BGR32, CIN_WIDTH, CIN_HEIGHT );
|   |  ^
| /<>/neo/renderer/Cinematic.cpp:630:9: error: ‘avpicture_fill’ 
was not declared in this scope
|   630 | avpicture_fill( ( AVPicture* )frame2, image, 
AV_PIX_FMT_BGR32, CIN_WIDTH, CIN_HEIGHT );
|   | ^~
| /<>/neo/renderer/Cinematic.cpp: In member function ‘cinData_t 
idCinematicLocal::ImageForTimeFFMPEG(int)’:
| /<>/neo/renderer/Cinematic.cpp:1143:33: error: 
‘avcodec_decode_video2’ was not declared in this scope; did you mean 
‘avcodec_decode_subtitle2’?
|  1143 | avcodec_decode_video2( dec_ctx, 
frame, &frameFinished, &packet );
|   | ^
|   | avcodec_decode_subtitle2
| /<>/neo/renderer/Cinematic.cpp:1146:25: error: ‘av_free_packet’ 
was not declared in this scope; did you mean ‘av_new_packet’?
|  1146 | av_free_packet( &packet );
|   | ^~
|   | av_new_packet
| make[3]: *** [CMakeFiles/rbdoom3bfg.dir/build.make:821: 
CMakeFiles/rbdoom3bfg.dir/renderer/Cinematic.cpp.o] Error 1

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#978172: Decide whether libphonenumber or its users should B-D against libboost dev packages

[tony mancill]

On Thu, Jan 21, 2021 at 10:30:32AM +0100, Laurent Bigonville wrote:
> EDS builds fine again, now that libphonenumber has reintroduced the B-D
> against libboost dev packages
> 
> libphonenumber maintainer wants use to depend on boost dev package, let's
> discuss that after bullseye release

Hi Laurent, Matthias, Andreas:

I am reviving the discussion now that bullseye has been released.  The
commit that added the B-D on libboost-thread-dev to libphonenumber-dev
is [1].

What are the drawbacks to leaving the boost B-D in libphonenumber-dev
and closing the bug?

Thank you,
tony

[1] 
https://salsa.debian.org/debian/libphonenumber/-/commit/be4e4215dcf0260344499ac05d9199ff55748cb7

Bug#783178: gdlib-config --libs reports wrong library list

[Florian Ernst]

On Thu, Apr 23, 2015 at 02:38:27PM +0200, Jan Engelhardt wrote:
> Running `gdlib-config --libs` outputs:
> 
>   -lXpm -lX11 -ljpeg -lfontconfig -lfreetype -lpng12 -lz -lm
> 
> On Debian, this list is lacking -lgd itself, which means third-party 
> software that uses this command to link to GD fails to link.

Considering that gdlib-config is obsolete for quite some time and
nowadays not even present anymore maybe this bug can just be closed?

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1004575: bullseye-pu: package mutter/3.38.6-2~deb11u2

[Simon McVittie]

Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu

[ Reason ]
Bug fix updates from upstream gnome-3-38 branch, prompted by user request
in #1002651.

[ Impact ]
The first few patches resolve crashes (of either Firefox or the whole
desktop) with newer Firefox versions in Wayland mode, which might be
installed via Flatpak or future bullseye updates. I have not reproduced
these myself, but they seem to be the main reason for the user request.

d/p/surface-actor-Fix-unobscurred_fraction-calculation.patch fixes
incorrect refresh rates in multi-monitor setups; upstream asked me to
get this into Debian 11 "for multimedia folks".

d/p/xwayland-Fix-condition-for-queuing-a-window-to-META_QUEUE.patch
avoids a flood of X11 events which can cause performance problems for
Xwayland apps.

The last few patches fix visual glitches when Wayland clients use certain
protocols; I was able to reproduce this with GStreamer waylandsink, which
draws video frames incorrectly when its window is resized.

[ Tests ]
mutter has autopkgtests, which pass.

The updated version resolves the waylandsink issue and seems to work OK
in general on Intel hardware. I'll put it through some more manual testing
on Intel/Mesa/Wayland and NVIDIA/proprietary/Xorg before uploading.

[ Risks ]
It's a key package and part of our default desktop environment, but
upstream are generally conservative about backporting bug fixes to stable
branches. These fixes have all been in unstable for a while.

I can drop some of these changes if the release team would prefer to only
take a subset of them.

[ Checklist ]
  [x] *all* changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in (old)stable
  [x] the issue is verified as fixed in unstable

[ Changes ]
All changes are patches against upstream source, see d/changelog for
how they fit together in batches.
diffstat for mutter-3.38.6 mutter-3.38.6

 changelog   |   30 +
 patches/series  |9 
 patches/surface-actor-Fix-unobscurred_fraction-calculation.patch|   29 +
 patches/wayland-data-offer-Accept-final-preferrence-of-drop-desti.patch |   45 ++
 patches/wayland-subsurface-Check-for-parent-actor-before-unparent.patch |   29 +
 patches/wayland-subsurface-Handle-node-unlinking-on-parent-destro.patch |   62 +++
 patches/wayland-surface-Do-not-uncoditionally-process-surface-dam.patch |  163 ++
 patches/wayland-surface-Switch-order-for-calculating-surface-dama.patch |   64 +++
 patches/wayland-surface-Use-correct-default-viewport-for-surface-.patch |   53 +++
 patches/window-actor-wayland-Remove-subsurface-actors-on-dispose.patch  |   66 
 patches/xwayland-Fix-condition-for-queuing-a-window-to-META_QUEUE.patch |   33 ++
 11 files changed, 583 insertions(+)

diff -Nru mutter-3.38.6/debian/changelog mutter-3.38.6/debian/changelog
--- mutter-3.38.6/debian/changelog	2021-09-01 21:25:34.0 +0100
+++ mutter-3.38.6/debian/changelog	2022-01-30 16:58:45.0 +
@@ -1,3 +1,33 @@
+mutter (3.38.6-2~deb11u2) bullseye; urgency=medium
+
+  * d/patches: Update to commit 3.38.6-9-g0b26ad635 from gnome-3-38 branch
+(Closes: #1002651)
+- d/p/wayland-subsurface-Check-for-parent-actor-before-unparent.patch,
+  d/p/wayland-subsurface-Handle-node-unlinking-on-parent-destro.patch,
+  d/p/window-actor-wayland-Remove-subsurface-actors-on-dispose.patch:
+  Fix a crash involving Wayland subsurfaces, which can be triggered by
+  Firefox in Wayland mode (fix backported from 41~beta and 40.5)
+- d/p/wayland-data-offer-Accept-final-preferrence-of-drop-desti.patch:
+  Fix protocol error during Alt + drag-and-drop from Firefox in
+  Wayland mode, which would result in Firefox being terminated
+  (fix backported from 41.1 and 40.6)
+- d/p/surface-actor-Fix-unobscurred_fraction-calculation.patch:
+  When an app/game using VSync is full-screen in a multi-monitor setup,
+  use the refresh rate of the correct monitor (LP: #1788535)
+  (fix backported from 41.3)
+- d/p/xwayland-Fix-condition-for-queuing-a-window-to-META_QUEUE.patch:
+  Avoid flooding Xwayland clients (X11 apps under Wayland) with window
+  management events, which can cause performance problems
+  (fix backported from 41.1 and 40.6)
+- d/p/wayland-surface-Switch-order-for-calculating-surface-dama.patch,
+  d/p/wayland-surface-Use-correct-default-viewport-for-surface-.patch,
+  d/p/wayland-surface-Do-not-uncoditionally-process-surface-dam.patch:
+  Fix visible glitches for Wayland clients that use the wp_viewporter
+  protocol in combination with wl_surface_damage(), such as the
+  GStreamer waylandsink element (fix backported from 41.3)
+
+ -- Simon McVittie   Sun, 30 Jan 2022 16:58:45 +
+
 mutter (3.3

Bug#1004503: [Pkg-javascript-devel] Bug#1004503: Bug#1004503: node-tap: Please update to version 15

[Yadd]

On 30/01/2022 12:36, Yadd wrote:

On 30/01/2022 12:34, Yadd wrote:

On 29/01/2022 18:26, Yadd wrote:

Package: node-tap
Version: 12.0.1+ds-4
Severity: normal

node-tap is outdated, version 15 is needed for some package (npm at
least).

Dependencies state:

# tap@15.1.6 (node-tap)
DEPENDENCIES:
   node-ansi-escapes (ansi-escapes)
   node-auto-bind (auto-bind)
   node-babel7
   node-chalk (chalk)
   node-chokidar (chokidar)
   node-cli-boxes (cli-boxes)
   node-cli-cursor (cli-cursor)
   node-cli-truncate (cli-truncate)
   node-cliui (cliui)
   node-convert-source-map (convert-source-map)
   node-coveralls (coveralls)
   node-decamelize (decamelize)
   node-diff (diff)
   node-es6-error (es6-error)
   node-esprima (esprima)
   node-find-cache-dir (find-cache-dir)
   node-find-up (find-up)
   node-foreground-child (foreground-child)
   node-glob (glob)
   node-graceful-fs (graceful-fs)
   node-indent-string (indent-string)
   node-is-windows (is-windows)
   node-isexe (isexe)
   node-istanbul
   node-jest-debbundle (is-ci)
   node-lodash (lodash)
   node-lodash-packages (lodash.flattendeep)
   node-make-dir (make-dir)
   node-minipass (minipass)
   node-mkdirp (mkdirp)
   node-ms (ms)
   node-opener (opener)
   node-p-map (p-map)
   node-punycode (punycode)
   node-react (@types/react, react, react-reconciler, scheduler)
   node-read-pkg (type-fest)
   node-resolve-from (callsites, resolve-from)
   node-rimraf (rimraf)
   node-shell-quote (shell-quote)
   node-signal-exit (signal-exit)
   node-slice-ansi (slice-ansi)
   node-source-map-support (source-map-support)
   node-stack-utils (stack-utils)
   node-string-width (string-width)
   node-strip-ansi (strip-ansi)
   node-tap-mocha-reporter (tap-mocha-reporter)
   node-tap-parser (tap-parser)
   node-which (which)
   node-widest-line (widest-line)
   node-wrap-ansi (wrap-ansi)
   node-write-file-atomic (write-file-atomic)
   node-ws (ws)
   node-yaml (yaml)
   node-yargs (yargs)


I added nyc into node-istanbul (nyc is the new istanbul command line). 
New missing modules list


MISSING:
tap
  └── @isaacs/import-jsx (4.0.1)
  └── caller-path (3.0.1)
  └── caller-callsite (4.1.0)
  └── findit (2.0.0)
  └── ink (3.2.0)
  └── code-excerpt (3.0.0)
  └── convert-to-spaces (1.0.2)
  └── patch-console (1.0.0)
  └── react-devtools-core (4.23.0)
  └── yoga-layout-prebuilt (1.10.0)
  └── @types/yoga-layout (1.9.2)
  └── jackspeak (1.4.1)
  └── libtap (1.1.4)
  └── async-hook-domain (2.0.4)
  └── tap-yaml (1.0.0)
  └── tcompare (5.0.7)
  └── (^) tap-yaml (1.0.0)
  └── (^) tcompare (5.0.7)
  └── treport (3.0.2)
  └── (^) @isaacs/import-jsx (4.0.1)
  └── cardinal (2.1.1)
  └── ansicolors (0.3.2)
  └── redeyed (2.1.1)
  └── (^) ink (3.2.0)
  └── unicode-length (2.0.2)


ink is a command-line test utility for react


ink requires yoga-layout-prebuilt which is hard to rebuild: I got a lot 
of error when trying to `node-gyp build` yoga-layout. It seems at least 
that it requires a newer nodejs.


For now, I'll try to update node-tap without ink. It will be able to 
test many things except react components (AFAIK...)

Bug#1004576: elpa-message-templ: homepage is https://git.tethera.net/message-templ.git/

[David Bremner]

Package: elpa-message-templ
Version: 0.3.20161104-3
Severity: wishlist
Tags: upstream newcomer

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

I've (finally) fixed the git hosting for message-templ and it should be stable 
at

https://git.tethera.net/message-templ.git/

- -- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.15.0-3-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages elpa-message-templ depends on:
ii  dh-elpa-helper  2.0.10
ii  emacsen-common  3.0.4

Versions of packages elpa-message-templ recommends:
ii  emacs  1:27.1+1-3.1
ii  emacs-gtk [emacs]  1:27.1+1-3.1+b1

elpa-message-templ suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmH20eMACgkQA0U5G1Wq
FSFWURAAsVAi5H4PAfyzvucZ7voSHjywj8IzlbuSbc2gVuWu5FDTYG7BwSrpTpAP
JebPCYK52RjoR4WWRBzJRSc3PkBgUSPywwZtQzHeqXNZu3qwlgN2cFcMUneshQDc
sPOsomYpBybtiGLDysR/PFcAXDMVLIfs4BgL8oiOp6gwW+vUXOeiqtmc5ftQwaWe
/8j5hm2wFb7Nq/2TtrQYptnAd5SGlVQML4Ri0eRk+jzGqTYsVhvaRNwI4a+1Liln
QoGwYRmpSp3q2PTvY4e5Dz50YCFiD1J4Yo4aHMM6G/axkyvU7FpzvklUBVs4edHt
S7vWNqqVFwFURAC2EWJpjoaCuDiddn+ox6c0rozfoicTGS5YJM5z/McDFO85Lg75
bbrVHmkAHmm8AXOcjwfELiOQ/ytVfZTPQG/Zxs75GToiY/IjJmqakYIKiMuimr89
/iPQCvbT4A1716pa1/xlWjpe6/1HnW3jcSH8tAVgO6D86ZKuZryxtPaLFfibWJsR
O2AeRjYVMyl02B3IrXvjRuvH17IiPtJAwTpZFCS4ocFuVkTQMfHjPei7+uhbWQ+E
wQEEA4R4CcHuimoru52AH3IeUC+WRmTlQuf9OeOR60tTDL+Vlb6v3E6Spd6PSYV5
D3KUYQP8uquKkmpO00cjSnlMKk2MKIfuGVlNVqe/Ys2ehSNND/8=
=40jU
-END PGP SIGNATURE-

Bug#1004577: ldconfig -p coredumps

[Christoph Berg]

Package: libc-bin
Version: 2.33-3
Severity: important

In https://salsa.debian.org/python-team/packages/python-telethon/-/jobs/2413916
there is a diff generated between the two builds because a core file
from `ldconfig -p` appears as /usr/lib/python3.10/dist-packages/core.

Backtrace:

[0] 18:56 myon@sid-amd64.maxwell:~/de/py/debian/output/reprotest 1j $ gdb 
/sbin/ldconfig core
GNU gdb (Debian 10.1-2) 10.1.90.20210103-git
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /sbin/ldconfig...
Reading symbols from 
/usr/lib/debug/.build-id/f3/4bf815c30c307353fa1703469d5f1f4b3c9356.debug...
[New LWP 12315]
Core was generated by `/sbin/ldconfig -p'.
Program terminated with signal SIGABRT, Aborted.
#0  0x7f205bb9f621 in ?? ()
(gdb) bt
#0  0x7f205bb9f621 in ?? ()
#1  0x in ?? ()

The build artifacts are available from the salsa page; I don't have
any access to the system there.

There is another ldconfig segfault reported in #806911, I don't
know if that is related.

Christoph

Bug#1004083: plocate: stops with misleading error on pruned filesystem

[Steinar H. Gunderson]

On Thu, Jan 20, 2022 at 08:05:14AM -0700, Kevin Locke wrote:
> It turns out this the failure was due to a network issue which
> prevented contacting the host for the CIFS mount on /mnt.  However,
> this presents several issues that might be worth addressing:
> 
> 1. The error message contains the parent directory, rather than the
>directory which could not be read, which makes the error harder to
>diagnose.

This is a real bug, and should be easy to fix.

> 2. The error occurred on a CIFS filesystem, which is excluded by
>PRUNEFS in /etc/updatedb.conf.  Presumably it should be skipped
>rather than causing an error.

The problem is that updatedb doesn't really know for sure it entered a new
filesystem until it's stat-ed the directory. This is logic that's inherited
from mlocate, and I guess it would be possible to rewrite it in theory, but
such changes tend to be at great peril :-) So what's happening is basically
that it stats the directory, checks if is device number is different from the
parent, and if so, checks the filesystem from /proc/mounts.

You can't just scan it once at the start and be done with it, because someone
could be mounting new paths while you're doing updatedb (remember, updatedb
can take hours), so you'd need a way to deal with new mounts appearing.
(I already have complaints it doesn't immediately skip out if someone
_unmounts_ something it's in the process of scanning!) The bind mount code
has some special checks for this, since it cannot rely on st_dev (there's a
separate thread waiting for changes to mountinfo), but it's fundamentally
racy.

> 3. updatedb immediately aborts, rather than updating the database for
>the rest of the filesystem.  In this case, since the failing mount
>was at the root, the entire tree is skipped.

I don't honestly think this is a bug. If updatedb goes wrong for whatever
reason, it's not good to just silently discard parts of the database.
If nothing else, the next rescan could become very expensive.

/* Steinar */
-- 
Homepage: https://www.sesse.net/

Bug#1004553: new upstream version available (3.6.0)

[tony mancill]

Hello Ram,

On Sun, Jan 30, 2022 at 06:12:12PM +0530, Ramakrishnan Muthukrishnan wrote:
> Package: libcw6
> Version: 3.5.1-4
> Severity: wishlist
> X-Debbugs-Cc: r...@rkrishnan.org
> 
> A new upstream version is available which has some nice fixes for latency etc.
> 
> 
> 
> It will be great if this can be packaged up in Debian!

The packaging work for unixcw 3.6.0 is complete and the package is
already part of the testing and unstable distributions.  The next Debian
stable release (bookworm) will contain 3.6.0 or newer.

You can view the state of the package via the Debian Package Tracker
page for unixcw here: 

  https://tracker.debian.org/pkg/unixcw

If you would like to use the newer version on Debian stable, I don't see
any packaging changes that would prevent it's compilation on for
bullseye.  In fact, I just did a test build against bullseye and it
built correctly.

Cheers,
tony KG7IEL

Bug#1004083: plocate: stops with misleading error on pruned filesystem

[Kevin Locke]

Thanks for the thoughtful response!

On Sun, 2022-01-30 at 18:47 +0100, Steinar H. Gunderson wrote:
> On Thu, Jan 20, 2022 at 08:05:14AM -0700, Kevin Locke wrote:
>> 2. The error occurred on a CIFS filesystem, which is excluded by
>>PRUNEFS in /etc/updatedb.conf.  Presumably it should be skipped
>>rather than causing an error.
> 
> The problem is that updatedb doesn't really know for sure it entered a new
> filesystem until it's stat-ed the directory. [...]
> 
>> 3. updatedb immediately aborts, rather than updating the database for
>>the rest of the filesystem.  In this case, since the failing mount
>>was at the root, the entire tree is skipped.
> 
> I don't honestly think this is a bug. If updatedb goes wrong for whatever
> reason, it's not good to just silently discard parts of the database.
> If nothing else, the next rescan could become very expensive.

I think the behavior is understandable in both of the above cases,
although it's unfortunate that a flakey mount on an excluded
filesystem at an otherwise always empty directory causes updatedb to
fail entirely.  I'm not sure if it might be worth the effort to check
/proc/mounts or statfs(2) on stat(2) failure (for certain error
codes?), or to consider whether the directory is currently empty in
the database, or to skip it without discarding previous entries, or
something else.  I'll defer to your judgement.

It's not a common or major issue for me.  Feel free to close or treat
as low-priority.  I thought it was worth raising the issue for
consideration, but don't have strong feelings about it.

Cheers,
Kevin

Bug#1004578: silan: FTBFS with ffmpeg 5.0

[Sebastian Ramacher]

Source: silan
Version: 0.4.0-2
Severity: important
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs
Usertags: ffmpeg5.0

silan FTBFS with ffmpeg 5.0 (available in experimental):
| gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -g -Wall -O2 
-I.. -I/usr/include/opus -I/usr/include/x86_64-linux-gnu -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DNDEBUG -pipe  -fmessage-length=139 
-fdiagnostics-show-location=every-line -c -o ad_soundfile.o ad_soundfile.c
| ad_ffmpeg.c: In function ‘ad_open_ffmpeg’:
| ad_ffmpeg.c:117:40: error: ‘AVStream’ has no member named ‘codec’
|   117 | if (priv->formatContext->streams[i]->codec->codec_type == 
AVMEDIA_TYPE_AUDIO) {
|   |^~
| ad_ffmpeg.c:128:71: error: ‘AVStream’ has no member named ‘codec’
|   128 |   priv->codecContext = 
priv->formatContext->streams[priv->audioStream]->codec;
|   |   
^~
| ad_ffmpeg.c:129:22: warning: assignment discards ‘const’ qualifier from 
pointer target 
| ad_ffmpeg.c:129:22: warning: type [-Wdiscarded-qualifiers]
|   129 |   priv->codec= 
avcodec_find_decoder(priv->codecContext->codec_id);
|   |  ^
| ad_ffmpeg.c: In function ‘ad_read_ffmpeg’:
| ad_ffmpeg.c:205:32: warning: implicit declaration of function 
‘av_free_packet’; did you 
| ad_ffmpeg.c:205:32: warning: mean ‘av_get_packet’? [
| ad_ffmpeg.c:205:32: warning: -Wimplicit-function-declaration]
|   205 | if (priv->packet.data) av_free_packet(&priv->packet);
|   |^~
|   |av_get_packet
| ad_ffmpeg.c:225:13: warning: implicit declaration of function 
‘avcodec_decode_audio4’; 
| ad_ffmpeg.c:225:13: warning: did you mean ‘avcodec_decode_subtitle2’? [
| ad_ffmpeg.c:225:13: warning: -Wimplicit-function-declaration]
|   225 |   ret = avcodec_decode_audio4(priv->codecContext, &avf, 
&got_frame, &priv->packet);
|   | ^
|   | avcodec_decode_subtitle2
| ad_ffmpeg.c: In function ‘adp_get_ffmpeg’:
| ad_ffmpeg.c:380:5: warning: implicit declaration of function 
‘av_register_all’ [
| ad_ffmpeg.c:380:5: warning: -Wimplicit-function-declaration]
|   380 | av_register_all();
|   | ^~~
| ad_ffmpeg.c:381:5: warning: implicit declaration of function 
‘avcodec_register_all’ [
| ad_ffmpeg.c:381:5: warning: -Wimplicit-function-declaration]
|   381 | avcodec_register_all();
|   | ^~~~
| make[3]: *** [Makefile:388: ad_ffmpeg.o] Error 1

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#1004579: mplayer: FTBFS with ffmpeg 5.0

[Sebastian Ramacher]

Source: mplayer
Version: 2:1.4+ds1-3
Severity: important
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs
Usertags: ffmpeg5.0

mplayer FTBFS with ffmpeg 5.0 (available in experimental):
| cc -MMD -MP -Wundef -W -Wall -Wall -Wno-switch -Wno-parentheses 
-Wpointer-arith -Wredundant-decls -Werror=format-security -Wstrict-prototypes 
-Wmissing-prototypes -Wdisabled-optimization -Wno-pointer-sign 
-Wdeclaration-after-statement -std=gnu99 -Werror-implicit-function-declaration 
-D_POSIX_C_SOURCE=200112 -D_XOPEN_SOURCE=600 -D_ISOC99_SOURCE -I. -Iffmpeg -O2 
-march=x86-64 -mtune=generic -pipe -g  -fno-tree-vectorize 
-fno-asynchronous-unwind-tables -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE64_SOURCE -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -fpie -DPIC -D_REENTRANT 
-I/usr/include/p11-kit-1 -I/usr/include/samba-4.0 -I/usr/include/   
-D_REENTRANT  -I/usr/include/freetype2 -I/usr/include/libpng16 -DZLIB_CONST 
-I/usr/include/bs2b -I/usr/include/x86_64-linux-gnu 
-I/usr/include/x86_64-linux-gnu -pthread -I/usr/include/gtk-2.0 
-I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
-I/usr/include/x86_64-linux-gnu -I/usr/include/pango-1.0 
-I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/libmount 
-I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo 
-I/usr/include/pixman-1 -I/usr/include/harfbuzz -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/uuid 
-I/usr/include/freetype2 -I/usr/include/libpng16  -c -o libvo/vo_gl.o 
libvo/vo_gl.c
| libvo/vo_fbdev2.c:103:15: warning: missing initializer for field 'transp' of 
'struct fb_cmap' [-Wmissing-field-initializers]
|   103 | static struct fb_cmap fb_oldcmap = { 0, 256, fb_ored, fb_ogreen, 
fb_oblue };
|   |   ^~~
| In file included from libvo/vo_fbdev2.c:31:
| /usr/include/linux/fb.h:286:16: note: 'transp' declared here
|   286 | __u16 *transp;  /* transparency, can be NULL 
*/
|   |^~
| libvo/vo_fbdev2.c: In function 'config':
| libvo/vo_fbdev2.c:224:27: warning: comparison of integer expressions of 
different signedness: '__u32' {aka 'unsigned int'} and 'int' [-Wsign-compare]
|   224 | if (fb_vinfo.xres < in_width || fb_vinfo.yres < in_height) {
|   |   ^
| libvo/vo_fbdev2.c:224:55: warning: comparison of integer expressions of 
different signedness: '__u32' {aka 'unsigned int'} and 'int' [-Wsign-compare]
|   224 | if (fb_vinfo.xres < in_width || fb_vinfo.yres < in_height) {
|   |   ^
| libvo/vo_fbdev2.c:211:58: warning: unused parameter 'title' 
[-Wunused-parameter]
|   211 | uint32_t d_height, uint32_t flags, char *title,
|   |~~^
| libvo/vo_fbdev2.c: In function 'set_bpp':
| libvo/vo_fbdev2.c:61:42: warning: this statement may fall through 
[-Wimplicit-fallthrough=]
|61 | p->transp.length = 8;
|   | ~^~~
| libvo/vo_fbdev2.c:63:17: note: here
|63 | case 24:
|   | ^~~~
| In file included from ./mp_core.h:27,
|  from libvo/vo_png.c:35:
| ./libmpdemux/demuxer.h: In function 'new_demux_packet':
| ./libmpdemux/demuxer.h:98:29: warning: left shift of negative value 
[-Wshift-negative-value]
|98 | #define MP_NOPTS_VALUE (-1LL<<63) //both int64_t and double should be 
able to represent this exactly
|   | ^~
| ./libmpdemux/demuxer.h:289:11: note: in expansion of macro 'MP_NOPTS_VALUE'
|   289 |   dp->pts=MP_NOPTS_VALUE;
|   |   ^~
| ./libmpdemux/demuxer.h:98:29: warning: left shift of negative value 
[-Wshift-negative-value]
|98 | #define MP_NOPTS_VALUE (-1LL<<63) //both int64_t and double should be 
able to represent this exactly
|   | ^~
| ./libmpdemux/demuxer.h:290:14: note: in expansion of macro 'MP_NOPTS_VALUE'
|   290 |   dp->endpts=MP_NOPTS_VALUE;
|   |  ^~
| ./libmpdemux/demuxer.h:98:29: warning: left shift of negative value 
[-Wshift-negative-value]
|98 | #define MP_NOPTS_VALUE (-1LL<<63) //both int64_t and double should be 
able to represent this exactly
|   | ^~
| ./libmpdemux/demuxer.h:291:20: note: in expansion of macro 'MP_NOPTS_VALUE'
|   291 |   dp->stream_pts = MP_NOPTS_VALUE;
|   |^~
| libvo/vo_png.c: In function 'config':
| libvo/vo_png.c:113:50: warning: unused parameter 'd_width' 
[-Wunused-parameter]
|   113 | config(uint32_t width, uint32_t height, uint32_t d_width, uint32_t 
d_height, uint32_t flags, char 

Bug#1004083: plocate: stops with misleading error on pruned filesystem

[Steinar H. Gunderson]

On Sun, Jan 30, 2022 at 11:10:00AM -0700, Kevin Locke wrote:
> I think the behavior is understandable in both of the above cases,
> although it's unfortunate that a flakey mount on an excluded
> filesystem at an otherwise always empty directory causes updatedb to
> fail entirely.  I'm not sure if it might be worth the effort to check
> /proc/mounts or statfs(2) on stat(2) failure (for certain error
> codes?), or to consider whether the directory is currently empty in
> the database, or to skip it without discarding previous entries, or
> something else.  I'll defer to your judgement.

Yes, I wonder if this is the best fix for this specific issue.
If there's an error, there's no performance issue, since the alternative
is total failure; we can check /proc/mounts before deciding to crash out
or nt.

/* Steinar */
-- 
Homepage: https://www.sesse.net/

Bug#1004581: ccextractor: FTBFS with ffmpeg 5.0

[Sebastian Ramacher]

Source: ccextractor
Version: 0.93+ds2-1
Severity: important
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs
Usertags: ffmpeg5.0

ccextractor FTBFS with ffmpeg 5.0:
| gcc-10 -DPACKAGE_NAME=\"CCExtractor\" -DPACKAGE_TARNAME=\"ccextractor\" 
-DPACKAGE_VERSION=\"0.93\" -DPACKAGE_STRING=\"CCExtractor\ 0.93\" 
-DPACKAGE_BUGREPORT=\"car...@ccextractor.org\" -DPACKAGE_URL=\"\" 
-DPACKAGE=\"ccextractor\" -DVERSION=\"0.93\" -DHAVE_LIBM=1 -DHAVE_STDIO_H=1 
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
-DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 
-DHAVE_SYS_TIME_H=1 -DSTDC_HEADERS=1 -DHAVE_ARPA_INET_H=1 -DHAVE_FCNTL_H=1 
-DHAVE_FLOAT_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_LIMITS_H=1 -DHAVE_LOCALE_H=1 
-DHAVE_MALLOC_H=1 -DHAVE_NETDB_H=1 -DHAVE_NETINET_IN_H=1 -DHAVE_STDDEF_H=1 
-DHAVE_STDINT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_SYS_SOCKET_H=1 
-DHAVE_SYS_TIME_H=1 -DHAVE_SYS_TIMEB_H=1 -DHAVE_TERMIOS_H=1 -DHAVE_UNISTD_H=1 
-DHAVE_WCHAR_H=1 -DHAVE__BOOL=1 -DHAVE_PTRDIFF_T=1 -DHAVE_FSEEKO=1 
-DHAVE_MALLOC=1 -DHAVE_ALARM=1 -DHAVE_REALLOC=1 -DHAVE_DECL_STRERROR_R=1 
-DHAVE_STRERROR_R=1 -DHAVE_FLOOR=1 -DHAVE_FTRUNCATE=1 -DHAVE_GETHOSTBYNAME=1 
-DHAVE_GETTIMEOFDAY=1 -DHAVE_INET_NTOA=1 -DHAVE_MBLEN=1 -DHAVE_MEMCHR=1 
-DHAVE_MEMMOVE=1 -DHAVE_MEMSET=1 -DHAVE_MKDIR=1 -DHAVE_MODF=1 -DHAVE_POW=1 
-DHAVE_REALPATH=1 -DHAVE_RMDIR=1 -DHAVE_SELECT=1 -DHAVE_SETLOCALE=1 
-DHAVE_SOCKET=1 -DHAVE_SQRT=1 -DHAVE_STRCASECMP=1 -DHAVE_STRCHR=1 
-DHAVE_STRDUP=1 -DHAVE_STRERROR=1 -DHAVE_STRNDUP=1 -DHAVE_STRRCHR=1 
-DHAVE_STRSTR=1 -DHAVE_STRTOL=1 -I.  -I../src/lib_ccx/ 
-I../src/thirdparty/zvbi/ -I../src/thirdparty/lib_hash/ 
-I../src/thirdparty/protobuf-c/ -I../src/thirdparty -I../src/ 
-I/usr/include/freetype2 -I/usr/include/gpac -I/usr/include/x86_64-linux-gnu 
-I/usr/include/x86_64-linux-gnu  -I/usr/include/x86_64-linux-gnu 
-I/usr/include/tesseract -I/usr/include/leptonica -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=gnu99 -Wno-write-strings -Wno-pointer-sign 
-D_FILE_OFFSET_BITS=64 -DVERSION_FILE_PRESENT -DGPAC_DISABLE_VTT 
-DGPAC_DISABLE_OD_DUMP -DGPAC_DISABLE_REMOTERY -DNO_GZIP -O3 
-DGPAC_CONFIG_LINUX  -DGPAC_64_BITS -DENABLE_HARDSUBX -DENABLE_OCR 
-DPN3G_NO_CONFIG_H -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
../src/lib_ccx/ccextractor-hardsubx_imgops.o `test -f 
'../src/lib_ccx/hardsubx_imgops.c' || echo './'`../src/lib_ccx/hardsubx_imgops.c
| ../src/lib_ccx/hardsubx.c: In function ‘hardsubx_process_data’:
| ../src/lib_ccx/hardsubx.c:16:2: warning: implicit declaration of function 
‘av_register_all’ [-Wimplicit-function-declaration]
|16 |  av_register_all();
|   |  ^~~
| ../src/lib_ccx/hardsubx.c:35:34: error: ‘AVStream’ has no member named ‘codec’
|35 |   if (ctx->format_ctx->streams[i]->codec->codec_type == 
AVMEDIA_TYPE_VIDEO)
|   |  ^~
| ../src/lib_ccx/hardsubx.c:46:65: error: ‘AVStream’ has no member named ‘codec’
|46 |  ctx->codec_ctx = 
ctx->format_ctx->streams[ctx->video_stream_id]->codec;
|   | ^~
| ../src/lib_ccx/hardsubx.c:47:13: warning: assignment discards ‘const’ 
qualifier from pointer target type [-Wdiscarded-qualifiers]
|47 |  ctx->codec = avcodec_find_decoder(ctx->codec_ctx->codec_id);
|   | ^
| ../src/lib_ccx/hardsubx.c: In function ‘_init_hardsubx’:
| ../src/lib_ccx/hardsubx.c:224:15: warning: initialization discards ‘const’ 
qualifier from pointer target type [-Wdiscarded-qualifiers]
|   224 |  char *lang = options->ocrlang;
|   |   ^~~
| make[1]: *** [Makefile:1927: ../src/lib_ccx/ccextractor-hardsubx.o] Error 1
| make[1]: *** Waiting for unfinished jobs
| ../src/lib_ccx/hardsubx_decoder.c: In function 
‘hardsubx_process_frames_tickertext’:
| ../src/lib_ccx/hardsubx_decoder.c:385:4: warning: implicit declaration of 
function ‘avcodec_decode_video2’; did you mean ‘avcodec_decode_subtitle2’? 
[-Wimplicit-function-declaration]
|   385 |avcodec_decode_video2(ctx->codec_ctx, ctx->frame, &got_frame, 
&ctx->packet);
|   |^
|   |avcodec_decode_subtitle2
| make[1]: Leaving directory '/<>/linux'

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#1001830: transition: libtorrent-rasterbar

[Christian Marillat]

On 30 janv. 2022 16:55, Sebastian Ramacher  wrote:

[...]

> libtorrent-rasterbar was built successfully on mips*el. Please go ahead.

Done.

Christian

Bug#952169: libmodule-starter-plugin-cgiapp-perl: FTBFS: dh_auto_test: error: perl Build test --verbose 1 returned exit code 1

[Nilesh Patra]

Hi Jaldhar,

On Wed, 26 Feb 2020 00:16:04 -0500 (EST) "Jaldhar H. Vyas"  
wrote:
> On Sun, 23 Feb 2020, Lucas Nussbaum wrote:
> 
> > Hi,
> >
> > During a rebuild of all packages in sid, your package failed to build
> > on amd64.
> >
> 
> Hi Lucas, because I have been long in responding, I just wanted to drop a 
> quick note that I acknowledge your bug report.  I need to do an upstream 
> release to fix all the issues and I will try and do this ASAP.

Since this bug has been open for a (very)long time, and this package even 
missed the last release,
I NMU'd what I found working. The fix seems to be already there on your 
corresponding github repository
here[1]

I have attached the debdiff of my NMU, could you please consider merging?

[1]: 
https://github.com/jaldhar/Module-Starter-Plugin-CGIApp/commit/73ec81f8e648fbda430f3f81ba59428828ea0c18

Regards,
Nilesh
diff -Nru libmodule-starter-plugin-cgiapp-perl-0.44/debian/changelog 
libmodule-starter-plugin-cgiapp-perl-0.44/debian/changelog
--- libmodule-starter-plugin-cgiapp-perl-0.44/debian/changelog  2015-09-20 
09:29:56.0 +
+++ libmodule-starter-plugin-cgiapp-perl-0.44/debian/changelog  2022-01-30 
16:54:46.0 +
@@ -1,3 +1,14 @@
+libmodule-starter-plugin-cgiapp-perl (0.44-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add patch to fix FTBFS (Closes: #952169)
+  * d/control: Update versioned dep on libmodule-starter-perl
+  * d/tests/pkg-perl/SKIP: skip build-deps and syntax.t
++ build-deps is skipped since it seems to be tested on itself
++ syntax.t: One check on titanium/Modules.pm needs fixing upstream
+
+ -- Nilesh Patra   Sun, 30 Jan 2022 22:24:46 +0530
+
 libmodule-starter-plugin-cgiapp-perl (0.44-1) unstable; urgency=medium
 
   * New upstream version that works properly with Module::Starter 1.70
diff -Nru libmodule-starter-plugin-cgiapp-perl-0.44/debian/control 
libmodule-starter-plugin-cgiapp-perl-0.44/debian/control
--- libmodule-starter-plugin-cgiapp-perl-0.44/debian/control2015-09-20 
09:29:56.0 +
+++ libmodule-starter-plugin-cgiapp-perl-0.44/debian/control2022-01-30 
16:54:46.0 +
@@ -2,7 +2,7 @@
 Section: perl
 Priority: optional
 Build-Depends: debhelper (>= 8), libmodule-build-perl
-Build-Depends-Indep: perl (>= 5.6.10-12), libfile-copy-recursive-perl, 
libfile-dircompare-perl, libmodule-starter-perl (>= 1.700), 
libhtml-template-perl, libtest-pod-perl (>= 1.22), libtest-pod-coverage-perl 
(>= 1.08), libtest-mocktime-perl
+Build-Depends-Indep: perl (>= 5.6.10-12), libfile-copy-recursive-perl, 
libfile-dircompare-perl, libmodule-starter-perl (>= 1.760), 
libhtml-template-perl, libtest-pod-perl (>= 1.22), libtest-pod-coverage-perl 
(>= 1.08), libtest-mocktime-perl
 Maintainer: Jaldhar H. Vyas 
 Standards-Version: 3.9.6
 Homepage: http://search.cpan.org/dist/Module-Starter-Plugin-CGIApp/
diff -Nru 
libmodule-starter-plugin-cgiapp-perl-0.44/debian/patches/adapt-to-module-starter-1.76
 
libmodule-starter-plugin-cgiapp-perl-0.44/debian/patches/adapt-to-module-starter-1.76
--- 
libmodule-starter-plugin-cgiapp-perl-0.44/debian/patches/adapt-to-module-starter-1.76
   1970-01-01 00:00:00.0 +
+++ 
libmodule-starter-plugin-cgiapp-perl-0.44/debian/patches/adapt-to-module-starter-1.76
   2022-01-30 16:54:46.0 +
@@ -0,0 +1,98 @@
+From 13af756ba3800b112c7952a5a2c6bf76b4a0ecde Mon Sep 17 00:00:00 2001
+From: Petr Pisar 
+Date: Tue, 19 Mar 2019 11:25:09 +0100
+Subject: [PATCH] Adapt to changes in Module-Starter-1.76
+
+Module::Starter::Simple changed _license_record() API. Now it returns
+a Software::License object or undef. This caused
+Module-Starter-Plugin-CGIApp test failures:
+
+Use of uninitialized value in string eq at 
/builddir/build/BUILD/Module-Starter-Plugin-CGIApp-0.44/blib/lib/Module/Starter/Plugin/CGIApp.pm
 line 468.
+Use of uninitialized value $license_blurb in scalar chomp at 
/builddir/build/BUILD/Module-Starter-Plugin-CGIApp-0.44/blib/lib/Module/Starter/Plugin/CGIApp.pm
 line 488.
+[...]
+#   Failed test 'different files'
+#   at t/common.pm line 114.
+#  got: '4'
+# expected: '0'
+
+This patch adapts to the chanegs and increaes a dependency on Module::Starter
+to 1.76 version.
+
+CPAN RT#128881
+---
+ Build.PL| 2 +-
+ META.json   | 2 +-
+ META.yml| 2 +-
+ lib/Module/Starter/Plugin/CGIApp.pm | 6 +++---
+ 4 files changed, 6 insertions(+), 6 deletions(-)
+
+diff --git a/Build.PL b/Build.PL
+index f13c4bf..1eee1ee 100644
+--- a/Build.PL
 b/Build.PL
+@@ -26,7 +26,7 @@ my $builder = Module::Build->new(
+ requires=> {
+ 'perl'  => 5.008,
+ 'File::ShareDir'=> 0,
+-'Module::Starter'   => 1.70,
++'Module::Starter'   => 1.76,
+ 'HTML::Template'=> 0,
+ },
+ meta_merge => {
+diff --git a/META.json b/META.json
+index d34

Bug#1004541:

[Thomas Koch]

I added "libbsd" to the "Requires:" line in lowdown.pc and could compile nix 
(after making the necessary changes in the nix build system to propagate 
LOWDOWN_LIBS):

prefix=/usr
exec_prefix=${prefix}
libdir=/usr/lib/x86_64-linux-gnu
includedir=/usr/include

Name: lowdown
Description: simple markdown translator library
URL: https://kristaps.bsd.lv/lowdown
Version: 0.10.0
Requires: libbsd
Libs.private:
Libs: -L${libdir} -llowdown -lm
Cflags: -I${includedir}

Bug#1004582: htop: New upstream release (3.1.2, 2021 Nov 30)

[Florian Ernst]

Package: htop
Version: 3.0.5-7
Severity: wishlist

Dear maintainer,

there are new upstream releases available, cf.
.

The ChangeLog lists

| What's new in version 3.1.2
| 
| * Bugfix for crash when storing modified settings at exit
| * Generate xz-compressed source tarball (with configure) using github actions
| * Allow -u UID with numerical value as argument
| * Added documentation for obsolete/state libraries/program files highlighting
| * Some obsolete/stale library highlighting refinements
| * Column width issues resolved
| * Dynamic UID column sizing improved
| * Discard stale information from Disk and Network I/O meters
| * Refined Linux kernel thread detection
| * Reworked process state handling
| * New CCGROUP column showing abbreviated cgroup name
| * New OFFSET column in the list of open files screen
| 
| What's new in version 3.1.1
| 
| * Update license headers to explicitly say GPLv2+
| * Document minimum version for libcap (thanks to James Brown)
| * Fix mouse wheel collision with autogroups nice adjustment
| * Adjust Makefile.am macro definitions for older automake versions
| * Ensure consistent reporting of MemoryMeter 'used' memory
| * Report hugepage memory as real and used memory (as before)
| * Handle procExeDeleted, usesDeletedLib without mergedCommandline mode
| * Validate meter configuration before proceeding beyond htoprc parsing
| * Properly release memory on partially read configuration
| * Handle interrupted sampling from within libpcp PDU transfers
| * On Linux, provide O_PATH value if not defined
| * On Linux, always compute procExeDeleted if already set
| * Workaround for Rosetta 2 on Darwin (thanks to Alexander Momchilov)
| * Fix FreeBSD cmdline memory leak in Process_updateCmdline, and
| * Plug a Disk I/O meter memory leak on FreeBSD (thanks to Ximalas)
| 
| What's new in version 3.1.0
| 
| * Updated COPYING file to remove the PLPA exemption (appendix 2)
|   With this change the license is now GPLv2 without any additional wording.
| * Improved default sort ordering
|   Note for users: This may lead to an inverted sort order on startup of
|   htop 3.1.0 compared to previous versions.
|   This is due to what is stored in your htoprc file. Solution: Press I
|   (to invert sort order).
|   This changed setting will be saved by htop on exit as long as it can
|   write to your htoprc file.
| * The compile-time option to cater specifically for running htop as
|   setuid has been removed
| * Add read-only option
|   This allows htop to be run in an non-intrusive fashion where it acts only
|   as a process viewer disabling all functions to manipulate system state.
|   Note: This is not a security feature!
| * Move the code for handling the command line formatting related tasks
|   to be shared across all platforms
|   This means important features like stale binary/library highlighting
|   can now be available on all supported platforms.
| * Make the EXE and COMM columns available on all platforms
|   All supported platforms have the name of the executable (EXE) and a
|   self-chosen thread/command name (COMM) available one way or the other.
|   Moving this column to be handled as a platform-independently available
|   information simplifies the markup of the command line.
| * Introduce configuration file versioning and config_reader_min_version
|   Starting with this version the configuration file contains a version
|   identifying the minimum version of the configuration parser needed to
|   fully understand the configuration file format.
|   Old configuration file formats are automatically upgraded when
|   saving the config file (htoprc).
| * Make the configuration parser friendlier to users (thanks to Bart Bakker)
|   With this change only settings that cannot be parsed properly are
|   reset to their defaults.
| * Improve default display for systems with many CPUs
| * Add the process ELAPSED time column
| * Improve the process STATE column sorting
| * Reworked handling resize and redrawing of the UI
| * Fixed an issue where the LED meter mode could overflow allotted space
| * Allow text mode Meters to span empty neighbors to the right
| * Rescale graph meters when value of total changes
|   (thanks to Michael Schönitzer)
| * Update generic process field display
|   Usually "uninteresting" values in columns like 1 thread, nice value
|   of 0, CPU and memory of 0%, idle/sleeping state, etc. are shown with
|   reduced intensity (dark grey)
| * Option and key ("*") to collapse / expand all branches under PID 1
|   (and PID 2 if kernel threads are shown) (thanks to Krishna Chaitanya)
| * Keep following a process when inverting the sort order, displaying
|   the help screen or hiding/unhiding userland threads.
|   If a thread is currently selected the selection is updated to point
|   to the thread's parent process. (thanks to Gonzalo, et.al.)
| * Reorder process scanning to be performed before updating the display
|   of the meters in the h

Bug#1004583: overwriting {,src}pkgcache.bin on near-every APT call strains flash

[Ivan Shmakov]

Package: apt
Version: 2.3.14
Severity: minor
Control: found -1 1.8.2.3

[Please do not Cc: me, for I’m “on the list,” so to say, and
I try to reserve my inbox for private communication only.
I’d have set up Mail-Followup-To:, but there doesn’t seem to
be a way to make it point to the bug being filed.]

As of this writing, pkgcache.bin and srcpkgcache.bin files for
an APT instance configured for testing / Sid are 61 MiB combined.

The way those caches are updated is by writing a new version
into a temporary file and then calling rename(2) to atomically
replace the old version with the new.  As such, every time the
caches are updated, some 61 MiB gets written to the filesystem

While it could be argued that such an amount written makes
no measurable impact on HDDs, and rather marginally affects
the lifetime of contemporary SSDs, it’s not uncommon to start
Debian from a micro-SD card on single-board computers, where
write cycles may be considerably more limited.

Similarly, when filesystems-level snapshots are supported
(Btrfs, Nilfs, etc.), the issue described prevents space (and
bandwidth, when snapshots are transferred with btrfs-send(8) /
btrfs-receive(8)) savings by getting in the way of the
filesystem’s copy-on-write behavior.

(FWIW, apt is by no means the only package with such an issue:
dpkg’s status file is updated the same way, and so is the
templates.dat file debconf uses by default; yet dpkg/status is
smaller, and debconf can be configured to use Driver: PackageDir,
also lowering the impact.  Outside of the Debian infrastructure,
tor caches are also ill-suited for write-limited media.)

Consider, for example, the following chroot environment with a
freshly installed Debian Bookworm (--arch=amd64 --variant=minbase
and a couple of packages on top of that):

chroot# apt-get update 
Hit:1 http://cdn-fastly.deb.debian.org/debian bookworm InRelease
Hit:2 http://security.debian.org/debian-security bookworm-security/updates 
InRelease
Reading package lists...
chroot# 

Now, let’s try to install some lightweight packages, checking
the ‘lifetime writes’ meter before and after the apt-get call:

base# mount -o remount,ro -- /dev/vgfoo/lvchild-z61f590 \
  && dumpe2fs -- /dev/vgfoo/lvchild-z61f590 | grep -E -- ^Lifetime 
Lifetime writes:  5418 MB
base# 

chroot# apt-get install -- jpeginfo 
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  libjpeg62-turbo
The following NEW packages will be installed:
  jpeginfo libjpeg62-turbo
0 upgraded, 2 newly installed, 0 to remove and 5 not upgraded.
Need to get 0 B/177 kB of archives.
After this operation, 725 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
debconf: delaying package configuration, since apt-utils is not installed
E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No such device)
Selecting previously unselected package libjpeg62-turbo:amd64.
(Reading database ... 6737 files and directories currently installed.)
Preparing to unpack .../libjpeg62-turbo_1%3a2.1.2-1_amd64.deb ...
Unpacking libjpeg62-turbo:amd64 (1:2.1.2-1) ...
Selecting previously unselected package jpeginfo.
Preparing to unpack .../jpeginfo_1.6.1-1_amd64.deb ...
Unpacking jpeginfo (1.6.1-1) ...
Setting up libjpeg62-turbo:amd64 (1:2.1.2-1) ...
Setting up jpeginfo (1.6.1-1) ...
Processing triggers for libc-bin (2.33-3) ...
chroot# 

base# mount -o remount,ro -- /dev/vgfoo/lvchild-z61f590 \
  && dumpe2fs -- /dev/vgfoo/lvchild-z61f590 | grep -E -- ^Lifetime 
Lifetime writes:  5740 MB
base# 

By the looks of it, installing 725 KiB worth of Debian packages
resulted in some 322 MiB getting written to the filesystem,
for which I’m inclined to think that APT cache update behavior
is in no small part responsible.  (I suppose running apt-get
under strace would allow for a more accurate estimate.)

For instance, largest recently changed files on the FS right
after the # apt-get install call were (note that the .deb files
to be installed were obtained earlier, and also that
/var/cache/apt/archives was on a separate FS anyway):

chroot# find / -xdev -cmin -4 -printf %k\\t%p\\n | sort -srn 
31568   /var/cache/apt/pkgcache.bin
31548   /var/cache/apt/srcpkgcache.bin
580 /usr/lib/x86_64-linux-gnu/libjpeg.so.62.3.0
88  /var/lib/dpkg/status-old
88  /var/lib/dpkg/status
52  /var/log/dpkg.log
40  /usr/share/doc/libjpeg62-turbo/copyright

A proper solution would be to move to some file format that
allows in-place updates, such as Berkeley DB or SQLite.

As a work-around, it’s possible to move the cach

Bug#1004582: htop: New upstream release (3.1.2, 2021 Nov 30)

[Daniel Lange]

Am 30.01.22 um 20:13 schrieb Florian Ernst:

| * Rework the libsensors parsing on Linux
which fixes


https://github.com/htop-dev/htop/issues/806
and
https://github.com/htop-dev/htop/issues/863
are the reasons I have not updated htop in sid yet.
Waiting for these to get fixed.

Bug#1004585: mrpt: FTBFS in ffmpeg 5.0

[Sebastian Ramacher]

Source: mrpt
Version: 1:2.4.1+ds-1
Severity: important
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs
Usertags: ffmpeg5.0

mrpt FTBFS with ffmpeg 5.0 (available in experimental):
| cd /<>/obj-x86_64-linux-gnu/libs/hwdrivers && ccache 
/usr/lib/ccache/c++ -DWXUSINGDLL -D_FILE_OFFSET_BITS=64 -D__WXGTK__ 
-Dhwdrivers_EXPORTS -I/usr/include/suitesparse 
-I/<>/libs/hwdrivers/src -I/<>/libs/hwdrivers/include 
-I/<>/libs/comms/include -I/<>/libs/io/include 
-I/<>/libs/core/include 
-I/<>/obj-x86_64-linux-gnu/include/mrpt-configuration 
-I/<>/libs/system/include -I/<>/libs/typemeta/include 
-I/<>/libs/containers/include -I/<>/libs/maps/include 
-I/<>/libs/obs/include -I/<>/libs/opengl/include 
-I/<>/libs/poses/include -I/<>/libs/bayes/include 
-I/<>/libs/math/include 
-I/<>/libs/serialization/include 
-I/<>/libs/rtti/include -I/<>/libs/random/include 
-I/<>/libs/config/include -I/<>/libs/expr/include 
-I/<>/libs/img/include -I/<>/libs/tfest/include 
-I/<>/libs/graphs/include -I/<>/libs/gui/include 
-I/<>/3rdparty/nanogui/ext/nanovg/src 
-I/<>/3rdparty/nanogui/include 
-I/<>/obj-x86_64-linux-gnu/3rdparty/nanogui 
-I/<>/libs/vision/include -isystem /usr/include/eigen3 -isystem 
/<>/3rdparty/xspublic -isystem 
/<>/3rdparty/xspublic/xstypes -isystem 
/<>/3rdparty/xspublic/xscommon -isystem 
/<>/3rdparty/xspublic/xscontroller -isystem /usr/include/opencv4 
-isystem /usr/include/openni2 -isystem 
/<>/3rdparty/rplidar_sdk/sdk/sdk/include -isystem 
/<>/3rdparty/rplidar_sdk/sdk/sdk/src -isystem 
/usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.0 -isystem 
/usr/include/wx-3.0 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -fPIC -Wall -Wno-long-long -Wno-variadic-macros -Wshadow 
-Wreturn-local-addr -Werror=return-local-addr -Wno-psabi -Wno-write-strings 
-Wreturn-type -Werror=return-type -Wformat -Werror=format-security -Wextra 
-Wtype-limits -Wcast-align -Wparentheses -Wno-unused-parameter -mtune=native 
-O3 -fPIC -pthread -MD -MT 
libs/hwdrivers/CMakeFiles/hwdrivers.dir/src/CGPSInterface.cpp.o -MF 
CMakeFiles/hwdrivers.dir/src/CGPSInterface.cpp.o.d -o 
CMakeFiles/hwdrivers.dir/src/CGPSInterface.cpp.o -c 
/<>/libs/hwdrivers/src/CGPSInterface.cpp
| /<>/libs/hwdrivers/src/CFFMPEG_InputStream.cpp: In member 
function ‘bool mrpt::hwdrivers::CFFMPEG_InputStream::openURL(const string&, 
bool, bool, const std::map, 
std::__cxx11::basic_string >&)’:
| /<>/libs/hwdrivers/src/CFFMPEG_InputStream.cpp:181:43: error: 
invalid conversion from ‘const AVCodec*’ to ‘AVCodec*’ [-fpermissive]
|   181 | ctx->pCodec = avcodec_find_decoder(ctx->pCodecPars->codec_id);
|   |   ^~~
|   |   |
|   |   const AVCodec*
| make[4]: *** [libs/hwdrivers/CMakeFiles/hwdrivers.dir/build.make:177: 
libs/hwdrivers/CMakeFiles/hwdrivers.dir/src/CFFMPEG_InputStream.cpp.o] Error 1

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#1004584: vlc: FTBFS with ffmpeg 5.0

[Sebastian Ramacher]

Source: vlc
Version: 3.0.16-1
Severity: important
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs
Usertags: ffmpeg5.0

vlc FTBFS with ffmpeg 5. 0 (available in experimental):
| checking for libavutil variant... ffmpeg
| checking for libavcodec >= 57.37.100 libavutil >= 52.0.0... yes
| checking for libavcodec/avcodec.h... yes
| checking for libavutil/avutil.h... yes
| checking for libva >= 0.38... yes
| checking for libva-drm... yes
| checking for libva-x11... yes
| checking for libva-wayland... yes
| checking for libavcodec/vaapi.h... no
| configure: error: libva is present but libavcodec/vaapi.h is missing

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#1004587: pyglet: FTBFS with ffmpeg 5.0

[Sebastian Ramacher]

Source: pyglet
Version: 1.5.14-2
Severity: important
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs
Usertags: ffmpeg5.0

pyglet FTBFS with ffmpeg 5.0 (available in experimental):
|dh_auto_test -O--buildsystem=pybuild
| I: pybuild base:237: cd /<>/.pybuild/cpython3_3.10_pyglet/build; 
python3.10 -m pytest >/dev/null 2>&1; cd 
/<>/.pybuild/cpython3_3.10_pyglet/build; xvfb-run --auto-servernum 
--server-num=20 -s "-screen 0 1024x768x24 -ac +extension GLX +render -noreset" 
python3.10 -m pytest -v -k "not interactive and not PulseAudio and not 
test_pulse and not test_player_play and not test_player_play_multiple and not 
test_player_silent_audio_driver and not test_freetype_face and not 
test_fontconfig and not test_linux_fontconfig and not test_driver and not 
test_openal and not ClockTimingTestCase" --ignore=tests/interactive
| = test session starts 
==
| platform linux -- Python 3.10.2, pytest-6.2.5, py-1.10.0, pluggy-0.13.0 -- 
/usr/bin/python3.10
| cachedir: .pytest_cache
| rootdir: /<>
| collecting ... collected 400 items / 5 errors / 87 deselected / 308 selected

|  ERRORS 

| _ ERROR collecting 
.pybuild/cpython3_3.10_pyglet/build/tests/integration/media/test_directsound.py 
_
| tests/integration/media/test_directsound.py:11: in 
| from pyglet.media.codecs import AudioFormat
| pyglet/media/__init__.py:143: in 
| add_default_media_codecs()
| pyglet/media/codecs/__init__.py:102: in add_default_media_codecs
| if have_ffmpeg():
| pyglet/media/codecs/__init__.py:118: in have_ffmpeg
| from . import ffmpeg_lib
| pyglet/media/codecs/ffmpeg_lib/__init__.py:36: in 
| from .libavcodec import *
| pyglet/media/codecs/ffmpeg_lib/libavcodec.py:46: in 
| from . import libavutil
| pyglet/media/codecs/ffmpeg_lib/libavutil.py:206: in 
| avutil.av_frame_get_best_effort_timestamp.restype = c_int64
| /usr/lib/python3.10/ctypes/__init__.py:387: in __getattr__
| func = self.__getitem__(name)
| /usr/lib/python3.10/ctypes/__init__.py:392: in __getitem__
| func = self._FuncPtr((name_or_ordinal, self))
| E   AttributeError: /usr/lib/x86_64-linux-gnu/libavutil.so.57: undefined 
symbol: av_frame_get_best_effort_timestamp
| _ ERROR collecting 
.pybuild/cpython3_3.10_pyglet/build/tests/integration/media/test_player.py _
| tests/integration/media/test_player.py:11: in 
| from pyglet.media import Player
| pyglet/media/__init__.py:143: in 
| add_default_media_codecs()
| pyglet/media/codecs/__init__.py:102: in add_default_media_codecs
| if have_ffmpeg():
| pyglet/media/codecs/__init__.py:118: in have_ffmpeg
| from . import ffmpeg_lib
| pyglet/media/codecs/ffmpeg_lib/__init__.py:36: in 
| from .libavcodec import *
| pyglet/media/codecs/ffmpeg_lib/libavcodec.py:46: in 
| from . import libavutil
| pyglet/media/codecs/ffmpeg_lib/libavutil.py:206: in 
| avutil.av_frame_get_best_effort_timestamp.restype = c_int64
| /usr/lib/python3.10/ctypes/__init__.py:387: in __getattr__
| func = self.__getitem__(name)
| /usr/lib/python3.10/ctypes/__init__.py:392: in __getitem__
| func = self._FuncPtr((name_or_ordinal, self))
| E   AttributeError: /usr/lib/x86_64-linux-gnu/libavutil.so.57: undefined 
symbol: av_frame_get_best_effort_timestamp
| _ ERROR collecting 
.pybuild/cpython3_3.10_pyglet/build/tests/integration/media/test_pulse.py _
| tests/integration/media/test_pulse.py:12: in 
| from pyglet.media.drivers.pulse import interface
| pyglet/media/drivers/pulse/__init__.py:36: in 
| from .adaptation import PulseAudioDriver
| pyglet/media/drivers/pulse/adaptation.py:39: in 
| from pyglet.media.events import MediaEvent
| pyglet/media/__init__.py:143: in 
| add_default_media_codecs()
| pyglet/media/codecs/__init__.py:102: in add_default_media_codecs
| if have_ffmpeg():
| pyglet/media/codecs/__init__.py:118: in have_ffmpeg
| from . import ffmpeg_lib
| pyglet/media/codecs/ffmpeg_lib/__init__.py:36: in 
| from .libavcodec import *
| pyglet/media/codecs/ffmpeg_lib/libavcodec.py:46: in 
| from . import libavutil
| pyglet/media/codecs/ffmpeg_lib/libavutil.py:206: in 
| avutil.av_frame_get_best_effort_timestamp.restype = c_int64
| /usr/lib/python3.10/ctypes/__init__.py:387: in __getattr__
| func = self.__getitem__(name)
| /usr/lib/python3.10/ctypes/__init__.py:392: in __getitem__
| func = self._FuncPtr((name_or_ordinal, self))
| E   AttributeError: /usr/lib/x86_64-linux-gnu/libavutil.so.57: undefined 
symbol: av_frame_get_best_effort_timestamp
| _ ERROR collecting 
.pybuild/cpython3_3.10_pyglet/build/tests/unit/media/test_listener.py _
| tests/unit/media/test_listener.py:7: in 
| from pyglet.media.drivers import pulse
| pyglet/media/drivers/pulse/__init__.py:36: in 
| from .adaptation import PulseAudioDriver
| pyglet/media/drivers/pulse/adaptation.py:39: in 
| from pyglet.media.events import Medi

Bug#705913: Choosing -ize/-ise has no effect

[Florian Ernst]

Package: aspell-en
Followup-For: Bug #705913

Hello all,

FWIW, for me the same invocation now yields

| enen-variant_0  en-variant_1  en-variant_2  en-w_accents  
en-wo_accents  en_AU  organization
| en_AU-variant_0   organization
| en_AU-variant_1   organization
| en_AU-w_accents   organization
| en_AU-wo_accents  organization
| en_CA analysed
| en_CA-variant_0   analysed
| en_CA-variant_1   analysed
| en_CA-w_accents   analysed
| en_CA-wo_accents  analysed
| en_GB organization
| en_GB-ise organization
| en_GB-ise-w_accents   organization
| en_GB-ise-wo_accents  organization
| en_GB-ize organization
| en_GB-ize-w_accents   organization
| en_GB-ize-wo_accents  organization
| en_GB-variant_0   organization
| en_GB-variant_1   organization
| en_GB-w_accents   organization
| en_GB-wo_accents  organization
| en_US analysed  labour
| en_US-variant_0   analysed  labour
| en_US-variant_1   analysed  labour
| en_US-w_accents   analysed  labour
| en_US-wo_accents  analysed  labour

which to me (yes, I not a native speaker) looks OK.

Maybe I'm missing something here, though ...

Cheers,
Flo

-- System Information:
Debian Release: 11.2
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 
'stable'), (50, 'testing-proposed-updates'), (50, 'proposed-updates'), (50, 
'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-10-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages aspell-en depends on:
ii  aspell   0.60.8-3
ii  dictionaries-common  1.28.4

aspell-en recommends no packages.

aspell-en suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature

Bug#1004536: lintian: suggest Testsuite: autopkgtest-pkg-* when autodep8 detects it should be added

[Paul Gevers]

Hi Paul,

On Sun, 30 Jan 2022 16:28:54 +0800 Paul Wise  wrote:

I noticed while packaging some Python modules recently that they were
not tested by debci. This is because debci only tests source packages
that contain a Testsuite field. The autodep8 tool is able to generate
the needed tests, but debci only runs it when the Testsuite field is
present and contains an autopkgtest-pkg-* value. The autodep8 tool also
contains heuristics to detect packages that could have autopkgtests but
right now there is nothing suggesting to maintainers that they should
add tests based on autodep8. I suggest that when the Testsuite field is
missing, lintian run autodep8 from the unpacked source package dir and
when autodep8 prints a test stanza on stdout, emit a tag suggesting
that the maintainer add the Testsuite field. If the Testsuite is
already present, presumably the maintainer already added some tests
that are better than the autodep8 ones. Since autodep8 also prints
warnings/errors on stderr, lintian could also emit tags there too. 


Here is an example of an affected package:

$ debsnap python-circuitbreaker 1.3.2-1
$ chronic dpkg-source -x python-circuitbreaker_1.3.2-1.dsc 
$ cd python-circuitbreaker*/

$ grep Testsuite debian/control
$ find debian/tests
find: ‘debian/tests’: No such file or directory
python-circuitbreaker-1.3.2 $ autodep8 
Test-Command: set -e ; for py in $(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -c "import circuitbreaker; print(circuitbreaker)" ; done
Depends: python3-all, python3-circuitbreaker, 
Restrictions: allow-stderr, superficial, 
Features: test-name=autodep8-python3


But this is only useful if the test actually passes. We don't want 
people to add the field if the test is broken. So if this is 
implemented, make sure the priority/certainty/whatever is low enough 
that people will *not* just blindly do this.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1004588: libzip: New upstream release (1.8.0, 2021 Jun 18)

[Florian Ernst]

Source: libzip
Version: 1.7.3-1
Severity: wishlist

Dear maintainer,

there is a new upstream release available, cf.
.

The changes contain

| Add support for zstd (Zstandard) compression.
| Add support for lzma (ID 14) compression.
| Add zip_source_window_create().
| Add zip_source_zip_create() variant to zip_source_zip().
| Allow method specific comp_flags in zip_set_file_compression().
| Allow zip_source_tell() on sources that don't support seeking and zip_ftell() 
on compressed data.
| Provide more details for consistency check errors.
| Improve output of zipcmp.
| In zipcmp, don’t ignore empty directories when comparing directory listing.
| Treat empty string as no password given in zip_file_set_encryption(), 
zip_fopen_encrypted(), and zip_set_default_password().

which seem nice enough to eventually have in Debian.

Please update the package when you think it is due time.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1004589: GNUnet daemon doesn't start successfully

[Sven Grewe]

Package: gnunet
Version: 0.15.3-4
Severity: important

I installed the gnunet package and the GNUnet daemon probably didn't 
start successfully. I haven't change any config files.


"# service gnunet status" on a Debian Sid system reports:

●gnunet.service - A framework for secure peer-to-peer networking
Loaded: loaded (/lib/systemd/system/gnunet.service; enabled; vendor 
preset: enabled)
Active: failed(Result: exit-code) since Sun 2022-01-30 19:54:54 
CET; 30min ago
   Process: 448 ExecStart=/usr/bin/gnunet-arm -s -c /etc/gnunet.conf 
(code=exited, status=217/USER)

   CPU: 1ms

Jan 30 19:54:54 debian systemd[1]: Starting A framework for secure 
peer-to-peer networking...
Jan 30 19:54:54 debian systemd[448]: gnunet.service: Failed to determine 
user credentials: No such process
Jan 30 19:54:54 debian systemd[448]: gnunet.service: Failed at step USER 
spawning /usr/bin/gnunet-arm: No such process
Jan 30 19:54:54 debian systemd[1]: gnunet.service: Control process 
exited, code=exited, status=217/USER
Jan 30 19:54:54 debian systemd[1]: gnunet.service: Failed with result 
'exit-code'.
Jan 30 19:54:54 debian systemd[1]: Failed to start A framework for 
secure peer-to-peer networking.



I belief that this behavior is not intended.

I first backported the package for myself to my Bullseye system and 
tested it there. It probably has similar problems to the original 
package from unstable. After that I installed the package on a freshly 
installed (Debian 11 without GUI) and upgraded (to Unstable) VM. The 
GNUnet daemon seems not to work out of the box there too I guess.

Bug#1004582: htop: New upstream release (3.1.2, 2021 Nov 30)

[Florian Ernst]

On Sun, Jan 30, 2022 at 08:26:27PM +0100, Daniel Lange wrote:
> https://github.com/htop-dev/htop/issues/806
> and
> https://github.com/htop-dev/htop/issues/863
> are the reasons I have not updated htop in sid yet.
> Waiting for these to get fixed.

Thanks for the feedback and thanks for taking care.

I trust you know best. :-)

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1004363: ibus: pops up window with accent mark

[brian m. carlson]

On 2022-01-26 at 23:47:41, Gunnar Hjalmarsson wrote:
> Oh no, not Zoom again. :( Saying that because zoom depending on ibus was the
> reason why the reporter of  run into
> problems.

It is unclear to me as well why it's needed, but maybe that's because I
don't speak a language for which it's necessary.  All the languages I
know happen to use the Latin alphabet.

> I think you can fix it for yourself by running this command:
> 
> im-config -n none

I picked xim here instead, since I think that's what I used to use and
it seemed to work.

> With that said, and as you rightly point out, this is still a valid bug. So
> let's keep it open and see if others run into the same issue and are able to
> shed some light on the root cause.

Sounds good.
-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA


signature.asc
Description: PGP signature

Bug#1004590: librabbitmq: New upstream release (0.11.0, 2021 Apr 01)

[Florian Ernst]

Source: librabbitmq
Version: 0.10.0-1
Severity: wishlist

Dear maintainer,

there is a new upstream release available which uscan did not detect,
cf. .

The changes contain

| Added:
| - rabbitmq-c-config.cmake is now generated (#611)
| - rabbitmq-c can be compiled on Win32 using pthreads (#613)
| - Add amqp_set_ssl_engine API to allow setting OpenSSL engine (#618)
| - Add amqp_ssl_socket_set_key_engine API to allow setting OpenSSL engine 
(#618)
| - Add support use of password-protected SSL keys (#661)
| Changed
| - Update OpenSSL library initialization to current best practices (#603)
| - Updates to OpenSSL to support v3.0.0 (#654, 627)
| Fixed:
| - OpenSSL symbol clash when compiling on Win32 (#583)
| - Restore correct non-blocking behavior using OpenSSL v1.1.1 (#586)
| - Disable harmless secure CRT compile warnings on Win32 (#588)
| - Fix unused parameter warnings on Win32 (#591)
| - Fix invalid format in generated pkg-config file (#599)
| - Fix invalid AMQP_STATUS_HEARTBEAT_TIMEOUT (#557)
| - Fix incorrect port when using --server flag in CLI tools

Please update the package when you think it is due time.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1004591: ITP: r-cran-simplermarkdown -- GNU R package with simple engine for generating reports

[Dirk Eddelbuettel]

Package: wnpp
Owner: Dirk Eddelbuettel 
Severity: wishlist

* Package name: r-cran-simplermarkdown
  Version : 0.0.4
  Upstream Author : Jan van der Laan
* URL or Web page : https://cran.r-project.org/package=simplermarkdown
* License : GPL (>= 3)
  Description : GNU R Package for Simple Engine for Generating Reports

This is a reasonably new package, but started to be used across CRAN
(including by six packages of mine) and package I intend package for Debian.

Cheers, Dirk

-- 
https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1004592: Please ship README.md, not README

[Christoph Biedl]

Package: jabberd2
Version: 2.7.0-3
Severity: wishlist

Greetings,

allow be to be brief: The file /usr/share/doc/jabberd2/README just
contains "See README.md", but that file is not part of the package.
It certainly should be.

Cheers,



signature.asc
Description: PGP signature

Bug#1004593: network-manager: [global-dns] searches=... configuration variable appears to have no effect

[Norbert Bollow]

Package: network-manager
Version: 1.30.0-2, 1.34.0-2
Severity: normal
X-Debbugs-Cc: n...@bollow.ch

Dear Maintainer,

I'm whether this might be a usability bug with the documentation or a
fuctional buf with the software itself:

According to 'man NetworkManager.conf', I expected that creating a
configuration file /etc/NetworkManager/conf.d/deeperpurpose.conf with contents

[global-dns]
searches=example.org

would result in /etc/resolv.conf in a line like

search example.org

However, adding that configuration file has proved ineffective (i.e. it
does not result in any change to /etc/resolv.conf), although it appears
that NetworkManager reads it.
[Syslog entry:
Jan 30 20:19:22 quill NetworkManager[806]:   [1643570362.0630] Read config
: /etc/NetworkManager/NetworkManager.conf (lib: no-mac-addr-change.conf) (etc: d
eeperpurpose.conf)
]

The /etc/resolv.conf file which NetworkManager generates is exactly the
same independently of whether or not that configuration file is added:

# Generated by NetworkManager
search home
nameserver 192.168.1.1
nameserver fe80::125a:f7ff:fe4f:1417%enp14s0

By contrast, I have found that the following are effective ways for adding
a domain name to the "search" line in /etc/resolv.conf or adding to it:
- adding it to /etc/hostname (that adds it to the "search" line after
  the "home" — found out about through taking a look at the source code of
  NetworkManager, see line 1263 and following in
  NetworkManager-1.30.0/src/core/dns/nm-dns-manager.c — is that
  behavior documented at all in the man pages for NetworkMananger?)
- using nm-connection-editor (putting the domain name I want in the
  "additonal search domains" field actually *replaces* the "home"
  which is precisely what I wanted, even though that does not quite
  correspond to the "additonal search domains" field description.) 

The issue came up during a fresh install of Debian 11.2 on a laptop
computer. I have also tested (using a separate test system) the
version 1.34.0-2 which is in testing and unstable and found the exact
same behavior.

I suggest that at the very least, the man pages should be updated
with information that explains how to get a desired domain name into
the "search" line of /etc/resolv.conf .

Best regards,

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

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

Versions of packages network-manager depends on:
ii  adduser  3.118
ii  dbus 1.12.20-2
ii  libaudit11:3.0-2
ii  libbluetooth35.55-3.1
ii  libc62.31-13+deb11u2
ii  libcurl3-gnutls  7.74.0-1.3+deb11u1
ii  libglib2.0-0 2.66.8-1
ii  libgnutls30  3.7.1-5
ii  libjansson4  2.13.1-1.1
ii  libmm-glib0  1.14.12-0.2
ii  libndp0  1.6-1+b1
ii  libnewt0.52  0.52.21-4+b3
ii  libnm0   1.30.0-2
ii  libpsl5  0.21.0-1.2
ii  libreadline8 8.1-1
ii  libselinux1  3.1-3
ii  libsystemd0  247.3-6
ii  libteamdctl0 1.31-1
ii  libudev1 247.3-6
ii  libuuid1 2.36.1-8+deb11u1
ii  policykit-1  0.105-31+deb11u1
ii  udev 247.3-6
ii  wpasupplicant2:2.9.0-21

Versions of packages network-manager recommends:
ii  dnsmasq-base [dnsmasq-base]  2.85-1
ii  iptables 1.8.7-1
ii  libpam-systemd   247.3-6
ii  modemmanager 1.14.12-0.2
ii  ppp  2.4.9-1+1
ii  wireless-regdb   2020.04.29-2

Versions of packages network-manager suggests:
ii  isc-dhcp-client  4.4.1-2.3
pn  libteam-utils

-- no debconf information

Bug#1004083: plocate: stops with misleading error on pruned filesystem

[Steinar H. Gunderson]

On Sun, Jan 30, 2022 at 07:25:55PM +0100, Steinar H. Gunderson wrote:
> Yes, I wonder if this is the best fix for this specific issue.
> If there's an error, there's no performance issue, since the alternative
> is total failure; we can check /proc/mounts before deciding to crash out
> or nt.

I've pushed a change for this to upstream git; are you in a position to try
it out?

/* Steinar */
-- 
Homepage: https://www.sesse.net/

Bug#1003685: What about bullseye ?

[Rogier]

Dear maintainer.

I am a bit surprised that this bug has been closed, even 
though it has not yet been fixed in bullseye.

Is a security update for bullseye still in the making ?

Kind regards,

Rogier.

Bug#1004594: qtwebengine-opensource-src: FTBFS with ffmpeg 5.0

[Sebastian Ramacher]

Source: qtwebengine-opensource-src
Version: 5.15.8+dfsg-1
Severity: important
Tags: ftbfs sid bookworm
X-Debbugs-Cc: sramac...@debian.org

qtwebengine-opensource-src FTBFS with ffmpeg 5.0 (available in
experimental):
| FAILED: 
obj/third_party/webrtc/modules/video_coding/webrtc_h264/h264_decoder_impl.o 
| /usr/lib/ccache/g++ -MMD -MF 
obj/third_party/webrtc/modules/video_coding/webrtc_h264/h264_decoder_impl.o.d 
-DUSE_UDEV -DUSE_AURA=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 -DOFFICIAL_BUILD 
-DTOOLKIT_QT -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-DNO_UNWIND_TABLES -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -DNDEBUG 
-DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DWEBRTC_ENABLE_PROTOBUF=1 
-DRTC_ENABLE_VP9 -DHAVE_SCTP -DENABLE_EXTERNAL_AUTH -DWEBRTC_USE_H264 
-DHAVE_WEBRTC_VIDEO -DLOGGING_INSIDE_WEBRTC -DWEBRTC_LIBRARY_IMPL 
-DWEBRTC_NON_STATIC_TRACE_EVENT_HANDLERS=0 -DWEBRTC_CHROMIUM_BUILD 
-DWEBRTC_POSIX -DWEBRTC_LINUX -DABSL_ALLOCATOR_NOTHROW=1 
-DNO_MAIN_THREAD_WRAPPING -Igen -I../../3rdparty/chromium 
-I../../3rdparty/chromium/third_party/webrtc_overrides 
-I../../3rdparty/chromium/third_party/webrtc -Igen/third_party/webrtc 
-I../../3rdparty/chromium/third_party/abseil-cpp 
-I../../3rdparty/chromium/third_party/perfetto/include 
-Igen/third_party/perfetto/build_config -Igen/third_party/perfetto -Igen -Igen 
-Igen -Igen -I../../3rdparty/chromium/third_party/libyuv/include -Igen -Igen 
-Igen -Igen -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector 
-fno-unwind-tables -fno-asynchronous-unwind-tables -fPIC -pipe -pthread -m64 
-Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wno-unused-local-typedefs 
-Wno-maybe-uninitialized -Wno-deprecated-declarations 
-fno-delete-null-pointer-checks -Wno-comments -Wno-packed-not-aligned 
-Wno-dangling-else -Wno-missing-field-initializers -Wno-unused-parameter -O2 
-fno-ident -fdata-sections -ffunction-sections -fno-omit-frame-pointer -g0 
-fvisibility=hidden -I/usr/include/x86_64-linux-gnu -std=gnu++14 -Wno-narrowing 
-Wno-class-memaccess -Wno-attributes -Wno-class-memaccess 
-Wno-subobject-linkage -Wno-invalid-offsetof -Wno-return-type 
-Wno-deprecated-copy -fno-exceptions -fno-rtti -fvisibility-inlines-hidden -c 
../../3rdparty/chromium/third_party/webrtc/modules/video_coding/codecs/h264/h264_decoder_impl.cc
 -o obj/third_party/webrtc/modules/video_coding/webrtc_h264/h264_decoder_impl.o
| 
../../3rdparty/chromium/third_party/webrtc/modules/video_coding/codecs/h264/h264_decoder_impl.cc:
 In member function ‘virtual int32_t webrtc::H264DecoderImpl::InitDecode(const 
webrtc::VideoCodec*, int32_t)’:
| 
../../3rdparty/chromium/third_party/webrtc/modules/video_coding/codecs/h264/h264_decoder_impl.cc:206:40:
 error: invalid conversion from ‘const AVCodec*’ to ‘AVCodec*’ [-fpermissive]
|   206 |   AVCodec* codec = avcodec_find_decoder(av_context_->codec_id);
|   |^~~
|   ||
|   |const AVCodec*

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#1004595: moc: FTBFS with ffmpeg 5.0

[Sebastian Ramacher]

Source: moc
Version: 1:2.6.0~svn-r3005-1
Severity: important
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs
Usertags: ffmpeg5.0

moc FTBFS with ffmpeg 5.0 (available in experimental):
| make[4]: Entering directory '/<>/decoder_plugins/ffmpeg'
| /bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../..  -I/usr/include/x86_64-linux-gnu -I../.. -Wdate-time 
-D_FORTIFY_SOURCE=2  -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 
-I/usr/include/x86_64-linux-gnu -I../.. -pthread -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -pedantic -Wextra 
-I/usr/include/x86_64-linux-gnu -c -o libffmpeg_decoder_la-ffmpeg.lo `test -f 
'ffmpeg.c' || echo './'`ffmpeg.c
| libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. 
-I/usr/include/x86_64-linux-gnu -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 
-D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -I/usr/include/x86_64-linux-gnu -I../.. 
-pthread -g -O2 "-ffile-prefix-map=/<>=." -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -pedantic -Wextra 
-I/usr/include/x86_64-linux-gnu -c ffmpeg.c  -fPIC -DPIC -o 
.libs/libffmpeg_decoder_la-ffmpeg.o
| ffmpeg.c:80:9: error: unknown type name ‘AVCodecContext’
|80 | AVCodecContext *enc;
|   | ^~
| ffmpeg.c: In function ‘fmt_from_sample_fmt’:
| ffmpeg.c:498:26: error: request for member ‘sample_fmt’ in something not a 
structure or union
|   498 | switch (data->enc->sample_fmt) {
|   |  ^~
| ffmpeg.c: In function ‘is_seek_broken’:
| ffmpeg.c:548:13: warning: implicit declaration of function ‘avcodec_version’; 
did you mean ‘avformat_version’? [-Wimplicit-function-declaration]
|   548 | if (avcodec_version () < AV_VERSION_INT(55,8,100))
|   | ^~~
|   | avformat_version
| ffmpeg.c: In function ‘set_downmixing’:
| ffmpeg.c:564:57: error: request for member ‘channel_layout’ in something not 
a structure or union
|   564 | if (av_get_channel_layout_nb_channels 
(data->enc->channel_layout) <= 2)
|   | ^~
| ffmpeg.c:567:18: error: request for member ‘request_channel_layout’ in 
something not a structure or union
|   567 | data->enc->request_channel_layout = AV_CH_LAYOUT_STEREO;
|   |  ^~
| ffmpeg.c: In function ‘ffmpeg_open_internal’:
| ffmpeg.c:711:21: warning: implicit declaration of function 
‘avcodec_alloc_context3’; did you mean ‘avio_alloc_context’? 
[-Wimplicit-function-declaration]
|   711 | data->enc = avcodec_alloc_context3 (NULL);
|   | ^~
|   | avio_alloc_context
| ffmpeg.c:711:19: warning: assignment to ‘int *’ from ‘int’ makes pointer from 
integer without a cast [-Wint-conversion]
|   711 | data->enc = avcodec_alloc_context3 (NULL);
|   |   ^
| ffmpeg.c:719:15: warning: implicit declaration of function 
‘avcodec_parameters_to_context’; did you mean ‘avcodec_parameters_copy’? 
[-Wimplicit-function-declaration]
|   719 | err = avcodec_parameters_to_context (data->enc, 
data->stream->codecpar);
|   |   ^
|   |   avcodec_parameters_copy
| ffmpeg.c:734:54: error: request for member ‘codec_id’ in something not a 
structure or union
|   734 | data->codec = avcodec_find_decoder (data->enc->codec_id);
|   |  ^~
| ffmpeg.c:765:26: error: request for member ‘flags’ in something not a 
structure or union
|   765 | data->enc->flags |= AV_CODEC_FLAG_TRUNCATED;
|   |  ^~
| ffmpeg.c:66:34: error: ‘CODEC_FLAG_TRUNCATED’ undeclared (first use in this 
function); did you mean ‘AV_CODEC_FLAG_TRUNCATED’?
|66 | # define AV_CODEC_FLAG_TRUNCATED CODEC_FLAG_TRUNCATED
|   |  ^~~~
| ffmpeg.c:765:37: note: in expansion of macro ‘AV_CODEC_FLAG_TRUNCATED’
|   765 | data->enc->flags |= AV_CODEC_FLAG_TRUNCATED;
|   | ^~~
| ffmpeg.c:66:34: note: each undeclared identifier is reported only once for 
each function it appears in
|66 | # define AV_CODEC_FLAG_TRUNCATED CODEC_FLAG_TRUNCATED
|   |  ^~~~
| ffmpeg.c:765:37: note: in expansion of macro ‘AV_CODEC_FLAG_TRUNCATED’
|   765 | data->enc->flags |= AV_CODEC_FLAG_TRUNCATED;
|   | ^~~
| ffmpeg.c:767:13: warning: implicit declaration of function ‘avcodec_open2’; 
did you mean ‘avio_open2’? [-Wimplicit-function-declaration]
|   767 | if (avcodec_open2 (data->enc, data->codec, NULL) < 0)
|   | ^
|   | avio_open2
| ffmpeg.c:777:65: error: requ

Bug#1003685: What about bullseye ?

[Guilhem Moulin]

Hi,

On Sun, 30 Jan 2022 at 21:23:55 +0100, Rogier wrote:
> I am a bit surprised that this bug has been closed, even 
> though it has not yet been fixed in bullseye.

That's how the BTS works.  It's marked as fixed cryptsetup/2:2.4.3-1
(bookworm, unstable), but still marked as found in cryptsetup/2:2.3.5-1
(bullseye).

> Is a security update for bullseye still in the making ?

Yes, see https://bugs.debian.org/1003686#5 and
https://alioth-lists.debian.net/pipermail/pkg-cryptsetup-devel/2022-January/009292.html
 .

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#1004596: kino: FTBFS with ffmpeg 5.0

[Sebastian Ramacher]

Source: kino
Version: 1.3.4+dfsg0-1.1
Severity: important
Tags: ftbfs sid bookworm
X-Debbugs-Cc: sramac...@debian.org
Usertags: ffmpeg5.0

kino FTBFS with ffmpeg 5.0 (in experimental):
| g++ -DHAVE_CONFIG_H -I. -I.. -Wall -I/usr/include/lqt  
-I/usr/include/libxml2 -pthread -I/usr/include/libglade-2.0 
-I/usr/include/libxml2 -I/usr/include/gtk-2.0 
-I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
-I/usr/include/x86_64-linux-gnu -I/usr/include/pango-1.0 
-I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/libmount 
-I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo 
-I/usr/include/pixman-1 -I/usr/include/harfbuzz -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/uuid 
-I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/x86_64-linux-gnu -I/usr/include/x86_64-linux-gnu  
-D_FILE_OFFSET_BITS=64 -DKINO_PLUGINDIR=\""/usr/lib/kino-gtk2"\" 
-DDATADIR=\""/usr/share"\" -D_REENTRANT -D__STDC_CONSTANT_MACROS-g -O2 -MT 
frame.o -MD -MP -MF .deps/frame.Tpo -c -o frame.o frame.cc
| frame.cc: In constructor ‘Frame::Frame()’:
| frame.cc:103:9: error: ‘av_register_all’ was not declared in this scope
|   103 | av_register_all();
|   | ^~~
| frame.cc: In member function ‘void Frame::GetUpperField(void*, int)’:
| frame.cc:898:22: warning: ISO C++17 does not allow ‘register’ storage class 
specifier [-Wregister]
|   898 | register int width = GetWidth( ) * bpp;
|   |  ^
| frame.cc:899:22: warning: ISO C++17 does not allow ‘register’ storage class 
specifier [-Wregister]
|   899 | register int height = GetHeight( );
|   |  ^~
| frame.cc:900:28: warning: ISO C++17 does not allow ‘register’ storage class 
specifier [-Wregister]
|   900 | for ( register int i = 0; i < height; i += 2 )
|   |^
| frame.cc: In member function ‘void Frame::GetLowerField(void*, int)’:
| frame.cc:907:22: warning: ISO C++17 does not allow ‘register’ storage class 
specifier [-Wregister]
|   907 | register int width = GetWidth( ) * bpp;
|   |  ^
| frame.cc:908:22: warning: ISO C++17 does not allow ‘register’ storage class 
specifier [-Wregister]
|   908 | register int height = GetHeight( );
|   |  ^~
| frame.cc:909:28: warning: ISO C++17 does not allow ‘register’ storage class 
specifier [-Wregister]
|   909 | for ( register int i = 0; i < height; i += 2 )
|   |^
| frame.cc: In member function ‘void Frame::Deinterlace(uint8_t*, uint8_t*, 
int, int)’:
| frame.cc:932:22: warning: ISO C++17 does not allow ‘register’ storage class 
specifier [-Wregister]
|   932 | register int x, y;
|   |  ^
| frame.cc:932:25: warning: ISO C++17 does not allow ‘register’ storage class 
specifier [-Wregister]
|   932 | register int x, y;
|   | ^
| frame.cc:933:27: warning: ISO C++17 does not allow ‘register’ storage class 
specifier [-Wregister]
|   933 | register uint8_t *l0, *l1, *l2, *l3;
|   |   ^~
| frame.cc:933:32: warning: ISO C++17 does not allow ‘register’ storage class 
specifier [-Wregister]
|   933 | register uint8_t *l0, *l1, *l2, *l3;
|   |^~
| frame.cc:933:37: warning: ISO C++17 does not allow ‘register’ storage class 
specifier [-Wregister]
|   933 | register uint8_t *l0, *l1, *l2, *l3;
|   | ^~
| frame.cc:933:42: warning: ISO C++17 does not allow ‘register’ storage class 
specifier [-Wregister]
|   933 | register uint8_t *l0, *l1, *l2, *l3;
|   |  ^~
| frame.cc: In member function ‘int Frame::ExtractRGB(void*)’:
| frame.cc:1063:9: error: ‘AVPicture’ was not declared in this scope; did you 
mean ‘AVPictureType’?
|  1063 | AVPicture dest;
|   | ^
|   | AVPictureType
| frame.cc:1067:23: warning: ‘void av_init_packet(AVPacket*)’ is deprecated 
[-Wdeprecated-declarations]
|  1067 | av_init_packet(&pkt);
|   | ~~^~
| In file included from /usr/include/x86_64-linux-gnu/libavcodec/avcodec.h:45,
|  from frame.h:51,
|  from frame.cc:56:
| /usr/include/x86_64-linux-gnu/libavcodec/packet.h:506:6: note: declared here
|   506 | void av_init_packet(AVPacket *pkt);
|   |  ^~
| frame.cc:1071:9: error: ‘avcodec_decode_video2’ was not declared in this 
scope; did you mean ‘avcodec_decode_subtitle2’?
|  1071 | avcodec_decode_video2( libavcodec, frame, &got_picture, &pkt 
);
|   | ^
|   | avcodec_decode_subtitle2
| frame.cc:1074:34: e

Bug#1004597: amide: FTBFS with ffmpeg 5.0

[Sebastian Ramacher]

Source: amide
Version: 1.0.5-15
Severity: important
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs
Usertags: ffmpeg5.0

amide FTBFS with ffmpeg 5.0 (available in experimental):
| libtool: link: g++ -O2 -I/usr/include -pthread -I/usr/include/libxml2 
-I/usr/include/libgnomecanvas-2.0 -I/usr/include/gail-1.0 
-I/usr/include/libart-2.0 -I/usr/include/gtk-2.0 
-I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
-I/usr/include/x86_64-linux-gnu -I/usr/include/pango-1.0 
-I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/libmount 
-I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo 
-I/usr/include/pixman-1 -I/usr/include/harfbuzz -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/uuid 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/dcmtk/dcmdata 
-I/usr/include/libpng16 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -DG_DISABLE_DEPRECATED -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,-z -Wl,defs -Wl,-z -Wl,relro -Wl,-z -Wl,now -o 
amide amitk_marshal.o amitk_type_builtins.o amitk_raw_data_UBYTE.o 
amitk_raw_data_SBYTE.o amitk_raw_data_USHORT.o amitk_raw_data_SSHORT.o 
amitk_raw_data_UINT.o amitk_raw_data_SINT.o amitk_raw_data_FLOAT.o 
amitk_raw_data_DOUBLE.o amitk_data_set_UBYTE_0D_SCALING.o 
amitk_data_set_UBYTE_1D_SCALING.o amitk_data_set_UBYTE_2D_SCALING.o 
amitk_data_set_SBYTE_0D_SCALING.o amitk_data_set_SBYTE_1D_SCALING.o 
amitk_data_set_SBYTE_2D_SCALING.o amitk_data_set_USHORT_0D_SCALING.o 
amitk_data_set_USHORT_1D_SCALING.o amitk_data_set_USHORT_2D_SCALING.o 
amitk_data_set_SSHORT_0D_SCALING.o amitk_data_set_SSHORT_1D_SCALING.o 
amitk_data_set_SSHORT_2D_SCALING.o amitk_data_set_UINT_0D_SCALING.o 
amitk_data_set_UINT_1D_SCALING.o amitk_data_set_UINT_2D_SCALING.o 
amitk_data_set_SINT_0D_SCALING.o amitk_data_set_SINT_1D_SCALING.o 
amitk_data_set_SINT_2D_SCALING.o amitk_data_set_FLOAT_0D_SCALING.o 
amitk_data_set_FLOAT_1D_SCALING.o amitk_data_set_FLOAT_2D_SCALING.o 
amitk_data_set_DOUBLE_0D_SCALING.o amitk_data_set_DOUBLE_1D_SCALING.o 
amitk_data_set_DOUBLE_2D_SCALING.o amitk_data_set_UBYTE_0D_SCALING_INTERCEPT.o 
amitk_data_set_UBYTE_1D_SCALING_INTERCEPT.o 
amitk_data_set_UBYTE_2D_SCALING_INTERCEPT.o 
amitk_data_set_SBYTE_0D_SCALING_INTERCEPT.o 
amitk_data_set_SBYTE_1D_SCALING_INTERCEPT.o 
amitk_data_set_SBYTE_2D_SCALING_INTERCEPT.o 
amitk_data_set_USHORT_0D_SCALING_INTERCEPT.o 
amitk_data_set_USHORT_1D_SCALING_INTERCEPT.o 
amitk_data_set_USHORT_2D_SCALING_INTERCEPT.o 
amitk_data_set_SSHORT_0D_SCALING_INTERCEPT.o 
amitk_data_set_SSHORT_1D_SCALING_INTERCEPT.o 
amitk_data_set_SSHORT_2D_SCALING_INTERCEPT.o 
amitk_data_set_UINT_0D_SCALING_INTERCEPT.o 
amitk_data_set_UINT_1D_SCALING_INTERCEPT.o 
amitk_data_set_UINT_2D_SCALING_INTERCEPT.o 
amitk_data_set_SINT_0D_SCALING_INTERCEPT.o 
amitk_data_set_SINT_1D_SCALING_INTERCEPT.o 
amitk_data_set_SINT_2D_SCALING_INTERCEPT.o 
amitk_data_set_FLOAT_0D_SCALING_INTERCEPT.o 
amitk_data_set_FLOAT_1D_SCALING_INTERCEPT.o 
amitk_data_set_FLOAT_2D_SCALING_INTERCEPT.o 
amitk_data_set_DOUBLE_0D_SCALING_INTERCEPT.o 
amitk_data_set_DOUBLE_1D_SCALING_INTERCEPT.o 
amitk_data_set_DOUBLE_2D_SCALING_INTERCEPT.o amitk_roi_ELLIPSOID.o 
amitk_roi_CYLINDER.o amitk_roi_BOX.o amitk_roi_ISOCONTOUR_2D.o 
amitk_roi_ISOCONTOUR_3D.o amitk_roi_FREEHAND_2D.o amitk_roi_FREEHAND_3D.o 
amide.o amide_gconf.o amide_gnome.o amitk_common.o amitk_canvas.o 
amitk_canvas_object.o amitk_color_table.o amitk_color_table_menu.o 
amitk_data_set.o amitk_dial.o amitk_fiducial_mark.o amitk_filter.o 
amitk_line_profile.o amitk_object.o amitk_object_dialog.o amitk_point.o 
amitk_preferences.o amitk_progress_dialog.o amitk_raw_data.o amitk_roi.o 
amitk_space.o amitk_space_edit.o amitk_study.o amitk_threshold.o 
amitk_tree_view.o amitk_volume.o amitk_window_edit.o 
alignment_mutual_information.o alignment_procrustes.o analysis.o 
dcmtk_interface.o fads.o image.o legacy.o libecat_interface.o 
libmdc_interface.o mpeg_encode.o pixmaps.o raw_data_import.o render.o 
tb_alignment.o tb_crop.o tb_distance.o tb_export_data_set.o tb_fads.o 
tb_filter.o tb_fly_through.o tb_math.o tb_profile.o tb_roi_analysis.o 
ui_common.o ui_gate_dialog.o ui_preferences_dialog.o ui_render.o 
ui_render_dialog.o ui_render_movie.o ui_series.o ui_study.o ui_study_cb.o 
ui_time_dialog.o xml.o  -L/usr/lib/x86_64-linux-gnu -lgsl -lgslcblas -lvolpack 
-lxml2 -lgnomecanvas-2 -lart_lgpl_2 -lgtk-x11-2.0 -lgdk-x11-2.0 
-lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 
-lpango-1.0 -lgobject-2.0 -lharfbuzz -lfontconfig -lfreetype -lmdc -lm 
-lglib-2.0 -lpng16 -ldcmdata -lofstd -loflog -lavcodec -lavutil -lz -lpthread 
-pthread
| /usr/bin/ld: mpeg_encode.o: in function `mpeg_encoding_init':
| ./src/mpeg_encode.c:219: undefined reference to `avcodec_register_all'
| /usr/bin/ld: ./src/mp