Bug#992469: debhelper: dh_installsystemd installs services in /usr/lib/systemd/system/

[intrigeri]

Hi,

I faced the same Lintian warning when preparing the apparmor 3.0.3-1
upload: debhelper moves the systemd unit to
/usr/lib/systemd/system/apparmor.service

I was wondering whether Lintian was correct and whether this would
actually cause trouble, especially on non-merged-/usr systems, so
I installed the resulting packages in an up-to-date sid VM with
non-merged-/usr.

At first glance, everything seems to work just fine:

 - The service starts at boot as expected.

 - The output of "systemctl show -p UnitPath --value" and
   "systemd-analyze unit-paths" does include /usr/lib/systemd/system.

So my impression at this point is that debhelper is doing the right
thing, while Lintian is incorrect when assuming that
/usr/lib/systemd/system is ignored. I'm wondering if I've
missed anything.

Theodore, you mentioned on -devel@ that this would "[break] on systems
that don't have usrmerge installed". Could you please explain
what it breaks?

I'll refrain from uploading apparmor 3.0.3-1 until this is clarified.

I've spotted one (somewhat cosmetic) problem though: the symlinks set
up for Wants=/WantedBy= still point to /lib so they are now broken:

  /etc/systemd/system/sysinit.target.wants/apparmor.service
  -> /lib/systemd/system/apparmor.service

This would of course not matter at all on a merged-/usr system.
Even on a non-merged-/usr system I could not spot any problem this
would cause, apart of some potential administrator confusion.
Should I report this separately?

Hoping it helps,
cheers!

Bug#992469: WARNING: dh_installsystemd is moving unit files to /usr/lib/systemd/system

[Peter Pentchev]

On Thu, Aug 19, 2021 at 12:18:51AM -0400, Theodore Ts'o wrote:
> There appears to be a rather major regression in debhelper 1.13.4 and
> 1.13.4nmu1, which is forcing unit files to go in
> /usr/lib/systemd/system, instead of /lib/systemd/systemd (where sytemd
> will actually pay attention to them).
> 
> On systems with ursmerge, things should still work, thanks to the
> compatibility symlink, but this will cause packages with unit files
> built since debhelper 1.13.4 was released to unstable, or uploaded as
> source builds, to be incorrect, triggering a Lintian error and
> breaking on systems that don't have usrmerge installed.
> 
> For more details and analysis, please see:
> 
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992469
> 
> I just wanted to post a warning that if you were planning on building
> or uploading new source-only uploads to unstable now that Bullseye has
> been released, and your package contains systemd unit files, you may
> want to hold off until this bug gets fixed...

Actually, I just reported #992465 against Lintian last night:
the Lintian error is outdated. See the original message in #987989 that
prompted the debhelper change:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987989#5

I got a scare yesterday, too, when I noticed a local rebuild moved
a unit file to /usr/lib/systemd/system/, but then I read #987989 and
then I actually tried it - and systemd happily found my service and
started it.

So, it's not as bad as it looks at first :)

G'luck,
Peter

-- 
Peter Pentchev  r...@ringlet.net r...@debian.org p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13


signature.asc
Description: PGP signature

Bug#986709: Rsnapshot removal

[Ryan Thoryk]

Upon upgrading my backup server tonight, I found that rsnapshot was 
removed from Debian Bullseye.  In my opinion, this shouldn't have happened.


I currently use it for backups on my main production server, and even in 
my previous Linux admin job, I had implemented it for company systems. 
There is no practical alternative to it, it's just a wrapper around 
rsync, nothing else works like that as far as I know.  I also noticed 
that a newer version is in sid, couldn't that have been migrated to 
testing and released?  I've been using it since 2014 (daily) as far as I 
know.  I could look for alternatives, but it works too well in my opinion.


To add what I think is a very good point for this, I recently opened a 
bug report for a package called statsvn, which didn't even work in both 
stable and testing, apparently nobody even verified that it worked 
before releasing it in Buster, it would fail with a java version check. 
 Rsnapshot, a fine working package, was removed, but a perpetually 
broken package wasn't.  Statsvn hasn't been released upstream for 
apparently 11 years.  For now, I might see if I can use the sid version 
on stable.


--
Ryan Thoryk
r...@thoryk.com
r...@tliquest.net

Bug#992479: override: libreadline8:libs/optional

[Daniel Lewart]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: override
X-Debbugs-Cc: readl...@packages.debian.org

FTP Team,

Please change libreadline8 from:
libs/required
to:
libs/optional

Reasons:
  1) readline debian/control has Priority: optional
  2) Debian Policy 2.5 Priorities

Also, discussed here:
https://lists.debian.org/debian-devel/2021/07/msg00046.html
https://lists.debian.org/debian-devel/2021/07/msg00048.html

Thank you!
Daniel Lewart
Urbana, Illinois

Bug#992480: debianutils: Translated man pages for which(1) not handled by alternatives

[Boyuan Yang]

Source: debianutils
Version: 5.1-1
Severity: normal
X-Debbugs-CC: cl...@debian.org

Hi,

Thanks for managing /usr/bin/which under alternatives system. However, the
translated man pages for which command (such as
/usr/share/man/pl/man1/which.1.gz) are not handled by alternatives system.
This won't cause issues in near future, but we have a possibility for file
collision after different which(1) implementations are packaged.

Currently I don't have a good solution for it. Maybe we can think more?

Thanks,
Boyuan Yang


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

Bug#992478: autopkgtest: Possible race condition leading to build-needed being ignored

[Kip Warner]

Package: autopkgtest
Version: 5.17
Severity: important
Tags: upstream
X-Debbugs-Cc: k...@thevertigo.com

Dear Maintainer,

My source tree contains DEP-8 tests in debian/tests. My debian/tests/control
contains the following test:

Tests: test-in-tree-unit-tests.sh
Depends: @builddeps@, postgresql-13
Restrictions: rw-build-tree, build-needed, allow-stderr, isolation-
container

I have another DEP-8 test, but it tests the installed artifacts without any
issue. The above test, however, calls a simple one liner (after the sh-bang),
to test local in-tree unit tests:

make -j check || { find . -iname "test-suite.log" -exec cat {} \; ; exit
99; }

Some times these tests are run as expected. Other times they don't ever run.
When they don't, it is because autopkgtest reports a failure when make(1) is
unable to run the `check` target. It appears as though there is no Makefile.

When I shell into the test bed into the location in which make was being run,
the source tarball has been unpacked as expected, but it has not been
configured. That is, I see my Makefile.am and other source files, but not the
generated Makefile or any other files generated after ./configure does its
thing.

Sometimes this happens and sometimes it does not. There does not appear to be
any rhyme or reason to it, so I suspect this may be a race condition.

-- System Information:
Debian Release: bullseye/sid
  APT prefers hirsute-updates
  APT policy: (500, 'hirsute-updates'), (500, 'hirsute-security'), (500,
'hirsute-proposed'), (500, 'hirsute'), (100, 'hirsute-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.11.0-25-generic (SMP w/16 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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages autopkgtest depends on:
ii  apt-utils   2.2.4ubuntu0.1
ii  libdpkg-perl1.20.9ubuntu1
ii  procps  2:3.3.16-5ubuntu3.1
ii  python3 3.9.4-1
ii  python3-debian  0.1.39

Versions of packages autopkgtest recommends:
ii  autodep8  0.24ubuntu1

Versions of packages autopkgtest suggests:
ii  fakemachine   0.0~git20201127.9e6ee78-1
ii  lxc   1:4.0.6-0ubuntu1
ii  lxd   1:0.9
ii  ovmf  2020.11-4
ii  ovmf-ia32 2020.11-4
ii  qemu-efi-aarch64  2020.11-4
ii  qemu-efi-arm  2020.11-4
ii  qemu-system   1:5.2+dfsg-9ubuntu3.1
ii  qemu-utils1:5.2+dfsg-9ubuntu3.1
ii  schroot   1.6.10-11ubuntu2
ii  vmdb2 0.22-1

Bug#992471: segmentation fault with "info -a ..."

[Norbert Preining]

Hi

>   "info -a automake" and "info -a bash"
> 
> info[9461]: segfault at 40 ip 557548b827ee sp 7fffef0e70f0 error
> 4 in info[557548b78000+34000]

Not reproducible here.

Can you run it in a gdb session
$ gdb info
...
(gdb) set args -a automake
(gdb) run
...

Then it should return at the segfault, and you can type
bt
for backtrace and capture the output.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#992477: override: gcc-10-base:libs/optional

[Daniel Lewart]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: override
X-Debbugs-Cc: debian-b...@lists.debian.org, gcc...@packages.debian.org

FTP Team,

Please change gcc-10-base from:
libs/required
to:
libs/optional

Reason: Debian Policy 2.5 Priorities

Also, discussed here:
https://lists.debian.org/debian-devel/2021/07/msg00046.html
https://lists.debian.org/debian-devel/2021/07/msg00048.html

Thank you!
Daniel Lewart
Urbana, Illinois

Bug#992476: override: gcc-9-base:libs/optional

[Daniel Lewart]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: override
X-Debbugs-Cc: debian-b...@lists.debian.org, gc...@packages.debian.org

FTP Team,

Please change gcc-9-base from:
libs/required
to:
libs/optional

Reason: Debian Policy 2.5 Priorities

Also, discussed here:
https://lists.debian.org/debian-devel/2021/07/msg00046.html
https://lists.debian.org/debian-devel/2021/07/msg00048.html

Thank you!
Daniel Lewart
Urbana, Illinois

Bug#992475: exim4-base recommends mailx, which often has heavy dependencies

[Daniel Lewart]

Source: exim4
Version: 4.94.2-7
Severity: normal
Tags: patch

Exim4 Maintainers,

Installing exim4-base often results in a boatload of unnecessary packages
being installed.

This is because exim4-base recommends virtual package mailx,
which mailutils (and its heavy dependencies) provides.

The solution is to recommend "bsd-mailx | mailx" instead.

Here are two similar bug reports:
  #677944 - bsd-mailx: should be a high-priority candidate to provide
the 'mailx' virtual package
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677944#28
  #849743 - logrotate: Please specify a default mailx provider
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849743

Below are the following:
  1) *untested* patch for debian/control
  2) "apt install exim4-base" debug output
  3) "apt install bsd-mailx exim4-base" debug output

Thank you!
Daniel Lewart
Urbana, Illinois

--- debian/control.orig 2021-07-13 11:12:50.0 -0500
+++ debian/control  2021-08-18 00:00:00.0 -0500
@@ -65,7 +65,7 @@
  ${misc:Depends},
  ${shlibs:Depends}
 # psmisc just for exiwhat.
-Recommends: mailx, psmisc
+Recommends: bsd-mailx | mailx, psmisc
 Suggests:
  exim4-doc-html | exim4-doc-info,
  eximon4,

$ apt -s -o Debug::pkgDepCache::AutoInstall=1 install exim4-base > /dev/null
  Installing exim4-config:amd64 as Depends of exim4-base:amd64
  Installing mailutils:amd64 as Recommends of exim4-base:amd64
Installing mailutils-common:amd64 as Depends of mailutils:amd64
Installing libfribidi0:amd64 as Depends of mailutils:amd64
Installing libgsasl7:amd64 as Depends of mailutils:amd64
  Installing gsasl-common:amd64 as Depends of libgsasl7:amd64
  Installing libidn11:amd64 as Depends of libgsasl7:amd64
  Installing libntlm0:amd64 as Depends of libgsasl7:amd64
Installing libmailutils7:amd64 as Depends of mailutils:amd64
  Installing guile-2.2-libs:amd64 as Depends of libmailutils7:amd64
Installing libgc1:amd64 as Depends of guile-2.2-libs:amd64
Installing libltdl7:amd64 as Depends of guile-2.2-libs:amd64
  Installing libmariadb3:amd64 as Depends of libmailutils7:amd64
Installing mariadb-common:amd64 as Depends of libmariadb3:amd64
  Installing mysql-common:amd64 as Depends of mariadb-common:amd64
  Installing libpython3.9:amd64 as Depends of libmailutils7:amd64
Installing exim4-daemon-light:amd64 as Recommends of mailutils:amd64
  Installing libgnutls-dane0:amd64 as Depends of exim4-daemon-light:amd64
Installing libunbound8:amd64 as Depends of libgnutls-dane0:amd64
  Installing libevent-2.1-7:amd64 as Depends of libunbound8:amd64
  Installing psmisc:amd64 as Recommends of exim4-base:amd64

$ apt -s -o Debug::pkgDepCache::AutoInstall=1 install bsd-mailx exim4-base > 
/dev/null
  Installing exim4-daemon-light:amd64 as Depends of bsd-mailx:amd64
Installing libgnutls-dane0:amd64 as Depends of exim4-daemon-light:amd64
  Installing libunbound8:amd64 as Depends of libgnutls-dane0:amd64
Installing libevent-2.1-7:amd64 as Depends of libunbound8:amd64
Installing libidn11:amd64 as Depends of exim4-daemon-light:amd64
  Installing liblockfile1:amd64 as Depends of bsd-mailx:amd64
  Installing exim4-config:amd64 as Depends of exim4-base:amd64
  Installing psmisc:amd64 as Recommends of exim4-base:amd64

Bug#992474: override: bind9-libs:libs/optional

[Daniel Lewart]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: override
X-Debbugs-Cc: debian-b...@lists.debian.org, bi...@packages.debian.org

FTP Team,

bind9-libs is libs/standard.

Debian Policy 2.5 Priorities says:
In particular, this means that C-like libraries will almost never
have a priority above optional, since they do not provide
functionality directly to users.

Also, discussed here:
https://lists.debian.org/debian-devel/2021/07/msg00046.html
https://lists.debian.org/debian-devel/2021/07/msg00048.html

Please change bind9-libs to:
libs/optional

Thank you!
Daniel Lewart
Urbana, Illinois

Bug#992469: debhelper: dh_installsystemd installs services in /usr/lib/systemd/system/

[Theodore Y. Ts'o]

Package: debhelper
Version: 13.4+nmu1
Followup-For: Bug #992469

I can confirm Samuel's analysis.  When I tried debugging why building
e2fsprogs was causing a new lintian error:

E: e2fsprogs: systemd-service-file-outside-lib 
usr/lib/systemd/system/e2scrub@.service
N:
E: systemd-service-file-outside-lib
N:
N:   The package ships a systemd service file outside /lib/systemd/system/
N:   
N:   Systemd in Debian searches for unit files in /lib/systemd/system/ and
N:   /etc/systemd/system. Notably, it does *not* look in
N:   /usr/lib/systemd/system/ for service files.
N:   
N:   System administrators should have the possibility to overwrite a
N:   service file (or parts of it, in newer systemd versions) by placing a
N:   file in /etc/systemd/system, so the canonical location used for
N:   service files is /lib/systemd/system/.
N:   
N:   Severity: error
N:   
N:   Check: systemd
N:

My service files were *originally* in debian/e2fsprogs/lib/systemd, as
they should have been:

 {/tmp/gbp/e2fsprogs-1.46.4}  
1008% dh_install -v -pe2fsprogs
cp --reflink=auto -a debian/tmp/etc debian/e2fsprogs//
install -d debian/e2fsprogs//lib/systemd
cp --reflink=auto -a debian/tmp/lib/systemd/system 
debian/e2fsprogs//lib/systemd/
...

But then dh_installsystemd is doing something cra-cra-crazy:

 {/tmp/gbp/e2fsprogs-1.46.4}  
1009% dh_installsystemd -v
cp --reflink=auto -a debian/e2fsprogs/usr/lib/systemd/system 
debian/e2fsprogs/lib/systemd
rm -fr debian/e2fsprogs/usr/lib/systemd
mv -f debian/e2fsprogs/lib/systemd debian/e2fsprogs/usr/lib/systemd
^^^

?!?

Please fix ASAP.  This is going to block anyone from being able to build
and upload packages that contain systemd service files.

Many thanks,

- Ted

Bug#992461: qa.debian.org: [udd] upload_date and date stalled

[Sebastiaan Couwenberg]

On 8/18/21 11:40 PM, Joao Eriberto Mota Filho wrote:
> The last registered date in 'upload_date' from 'bapase' is 2021-08-13. In my
> tests I can see the same problem in 'date' from 'upload_history'.

DSA disabled the UDD cronjob due to disk space usage, see:

 https://lists.debian.org/debian-qa/2021/08/msg0.html

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#991464: spdlog 1:1.8.5+ds-1 has no FTBFS on builddd

[肖盛文]

hi,

    After  spdlog new version 1:1.8.5+ds-1 uploaded, there is no FTBFS
on builddd.

https://buildd.debian.org/status/package.php?p=spdlog=sid

all passed.


The builddd status of hurd-i386 and  kfreebsd-amd64 arch had changed to
"Maybe-Successful"

https://buildd.debian.org/status/logs.php?pkg=spdlog=kfreebsd-amd64

https://buildd.debian.org/status/logs.php?pkg=spdlog=hurd-i386


Is this bug may be closed?

-- 
肖盛文 xiao sheng wen Faris Xiao 
微信(wechat)：atzlinux
《铜豌豆 Linux》https://www.atzlinux.com
基于 Debian 的 Linux 中文 桌面 操作系统
Debian QA page: https://qa.debian.org/developer.php?login=atzlinux%40sina.com
GnuPG Public Key: 0x00186602339240CB



OpenPGP_signature
Description: OpenPGP digital signature

Bug#992473: kmail: Unread messages suddenly pink

[Steve M. Robbins]

Package: kmail
Version: 4:20.08.3-1
Severity: normal

Dear Maintainer,

Today KMail decided to colour unread messages (in the message list) bright 
pink.  It was not pink previously.

-Steve


-- System Information:
Debian Release: 11.0
  APT prefers testing
  APT policy: (500, 'testing'), (200, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-8-amd64 (SMP w/16 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, 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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kmail depends on:
ii  akonadi-server   4:20.08.3-3
ii  kdepim-runtime   4:20.08.3-1
ii  kio  5.83.0-2
ii  libc62.31-16
ii  libgcc-s111.2.0-2
ii  libgpgmepp6  1.14.0-1+b2
ii  libkf5akonadiagentbase5 [libkf5akonadiagentbase5-20.08]  4:20.08.3-3
ii  libkf5akonadicontact5 [libkf5akonadicontact5-20.08]  4:20.08.3-1
ii  libkf5akonadicore5abi2 [libkf5akonadicore5-20.08]4:20.08.3-3
ii  libkf5akonadimime5 [libkf5akonadimime5-20.08]4:20.08.3-1
ii  libkf5akonadisearch-bin  4:20.08.3-1
ii  libkf5akonadisearch-plugins  4:20.08.3-1
ii  libkf5akonadisearchdebug5 [libkf5akonadisearchdebug5-20.08]  4:20.08.3-1
ii  libkf5akonadisearchpim5 [libkf5akonadisearchpim5-20.08]  4:20.08.3-1
ii  libkf5akonadiwidgets5abi1 [libkf5akonadiwidgets5-20.08]  4:20.08.3-3
ii  libkf5bookmarks5 5.83.0-2
ii  libkf5calendarcore5abi2  5:5.83.0-2
ii  libkf5calendarutils5 [libkf5calendarutils5-20.08]4:20.08.3-1
ii  libkf5codecs55.83.0-2
ii  libkf5completion55.83.0-2
ii  libkf5configcore55.83.0-2
ii  libkf5configgui5 5.83.0-2
ii  libkf5configwidgets5 5.83.0-3
ii  libkf5contacts5  5:5.83.0-2
ii  libkf5coreaddons55.83.0-2
ii  libkf5crash5 5.83.0-2
ii  libkf5dbusaddons55.83.0-2
ii  libkf5grantleetheme-plugins  20.08.3-1
ii  libkf5gravatar5abi2 [libkf5gravatar5-20.08]  4:20.08.3-1
ii  libkf5guiaddons5 5.83.0-2
ii  libkf5i18n5  5.83.0-3
ii  libkf5iconthemes55.83.0-2
ii  libkf5identitymanagement5 [libkf5identitymanagement5-20.08]  20.08.3-1
ii  libkf5itemmodels55.83.0-2
ii  libkf5itemviews5 5.83.0-2
ii  libkf5jobwidgets55.83.0-2
ii  libkf5kcmutils5  5.83.0-2
ii  libkf5kiocore5   5.83.0-2
ii  libkf5kiofilewidgets55.83.0-2
ii  libkf5kiogui55.83.0-2
ii  libkf5kiowidgets55.83.0-2
ii  libkf5kontactinterface5 [libkf5kontactinterface5-20.08]  20.08.3-1
ii  libkf5ksieveui5 [libkf5ksieveui5-20.08]  4:20.08.3-1
ii  libkf5ldap5abi1 [libkf5ldap5-20.08]  20.08.3-1
ii  libkf5libkdepim5 [libkf5libkdepim5-20.08]4:20.08.3-1
ii  libkf5libkleo5 [libkf5libkleo5-20.08]4:20.08.3-1
ii  libkf5mailcommon5abi2 [libkf5mailcommon5-20.08]  4:20.08.3-1
ii  libkf5mailtransport5 [libkf5mailtransport5-20.08]20.08.3-1
ii  libkf5mailtransportakonadi5 [libkf5mailtransportakonadi5-20  20.08.3-1
ii  libkf5messagecomposer5abi1 [libkf5messagecomposer5-20.08]4:20.08.3-5
ii  libkf5messagecore5abi1 [libkf5messagecore5-20.08]4:20.08.3-5
ii  libkf5messagelist5abi1 [libkf5messagelist5-20.08]4:20.08.3-5
ii  libkf5messageviewer5abi1 [libkf5messageviewer5-20.08]4:20.08.3-5
ii  libkf5mime5abi1 [libkf5mime5-20.08]  20.08.3-1
ii  libkf5mimetreeparser5abi1 [libkf5mimetreeparser5-20.08]  4:20.08.3-5
ii  libkf5notifications5 5.83.0-2
ii  libkf5notifyconfig5  

Bug#992472: fails to open file with relative path

[Joey Hess]

Package: bookworm
Version: 1.1.2+git20210715-1
Severity: normal

I ran
com.github.babluboy.bookworm foo.epub
and it complained:

[WARNING 22:12:14.238713] bookworm.vala:681: EBook not found at provided 
location:foo.epub
[FATAL 22:12:14.244095] [GLib-GIO] g_file_query_exists: assertion 
'G_IS_FILE(file)' failed

Using an absolute path worked. This is rather surprising behavior.

-- System Information:
Debian Release: 11.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-7-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (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 bookworm depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.38.0-2
ii  html2text1.3.2a-28
ii  libc62.31-12
ii  libgdk-pixbuf-2.0-0  2.42.2+dfsg-1
ii  libgee-0.8-2 0.20.4-1
ii  libglib2.0-0 2.66.8-1
ii  libgranite5  5.5.0-1+b1
ii  libgtk-3-0   3.24.24-4
ii  libpango-1.0-0   1.46.2-3
ii  libpoppler-glib8 20.09.0-3.1
ii  libsoup2.4-1 2.72.0-2
ii  libsqlite3-0 3.34.1-3
ii  libwebkit2gtk-4.0-37 2.32.1-2
ii  libxml2  2.9.10+dfsg-6.7
ii  poppler-utils20.09.0-3.1
ii  python3  3.9.2-3
ii  unar 1.10.1-2+b6
ii  unzip6.0-26

bookworm recommends no packages.

bookworm suggests no packages.

-- no debconf information

-- 
see shy jo


signature.asc
Description: PGP signature

Bug#992471: segmentation fault with "info -a ..."

[Bjarni Ingi Gislason]

Package: info
Version: 6.7.0.dfsg.2-6
Severity: normal


Dear Maintainer,

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?

  "info -a automake" and "info -a bash"

   * What was the outcome of this action?

info[9461]: segfault at 40 ip 557548b827ee sp 7fffef0e70f0 error
4 in info[557548b78000+34000]
Code: df e8 36 fe ff ff 85 c0 74 ae 48 8b 3d bb cd 03 00 48 85 ff 74 a2
5b e9 90 fb ff ff 41 57 41 56 41 55 41 54 55 53 48 83 ec 18 <48> 8b 5f
40 89 54 24 0c 48 85 db 0f 84 92 00 00 00 4c 8b 23 4d 85
Segmentation fault

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

Kernel: Linux 5.10.46-4 (SMP w/2 CPU threads)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages info depends on:
ii  install-info  6.7.0.dfsg.2-6
ii  libc6 2.31-13
ii  libtinfo6 6.2+20201114-2

info recommends no packages.

info suggests no packages.

-- no debconf information

-- 
Bjarni I. Gislason

Bug#992462: UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe2 in position 32: invalid continuation byte

[Michael Grant]

Package: libpython3.9-minimal
Version: 3.9.2-1
Severity: important

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

While running getmail which calls this library to download my spam
folder from a gmail acct for further processing, I ran across error in
header.py.  It's triggered when a message contains an invalid unicode
sequence.  For example:

b'Body Revolution - Medico Postura\xe2"\xa2 Body Posture Corrector'

Note the double-quote (") in the middle of the unicode sequence!  This
triggers the following condition:

Exception: please read docs/BUGS and include the following information
in any bug report:

  getmail version 6.14
Python version 3.9.2 (default, Feb 28 2021, 17:03:44)
[GCC 10.2.1 20210110]

Unhandled exception follows:
File "/usr/bin/getmail", line 932, in main
success = go(configs, options.idle)
File "/usr/bin/getmail", line 244, in go
msg = mail_filter.filter_message(msg, retriever)
File
"/usr/lib/python3/dist-packages/getmailcore/filters.py", line 79,
in filter_message
exitcode, newmsg, err = self._filter_message(msg)
File
"/usr/lib/python3/dist-packages/getmailcore/filters.py", line 289,
in _filter_message
msg.add_header('X-getmail-filter-classifier', line)
File
"/usr/lib/python3/dist-packages/getmailcore/message.py", line 210,
in add_header
self.__msg[name] = Header(content.rstrip(), 'utf-8')
File "/usr/lib/python3.9/email/header.py", line 217, in
__init__
self.append(s, charset, errors)
File "/usr/lib/python3.9/email/header.py", line 295, in
append
s = s.decode(input_charset, errors)
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe2 in
position 32: invalid continuation byte

Please also include configuration information from running getmail
with your normal options plus "--dump".

The code looks like this:

if not isinstance(s, str):
input_charset = charset.input_codec or 'us-ascii'
if input_charset == _charset.UNKNOWN8BIT:
s = s.decode('us-ascii', 'surrogateescape')
else:
s = s.decode(input_charset, errors)

I think you may need a try/accept around that last s.decode()
function or something to catch this case where it’s invalid utf-8.  I
don't think this should fail like this.  If it's not valid unicode
then probably it should default it back to latin-1.  I can't think of
anything better.

-- System Information:
Debian Release: 11.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable'), (250, 'testing'), (10, 
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages libpython3.9-minimal depends on:
ii  libc6  2.31-13
ii  libssl1.1  1.1.1k-1

Versions of packages libpython3.9-minimal recommends:
ii  libpython3.9-stdlib  3.9.2-1

libpython3.9-minimal suggests no packages.

-- no debconf information

Bug#985638: kdenlive: speed effect from right click does not change video speed

[Will C.]

Hi,

On Wed, Aug 18, 2021 at 8:29 AM Patrick Matthäi  wrote:
>
> Hi
>
> > [...]
> Could you please retest this with version 21.04.3-3 from unstable and
> 21.08.0-1 from experimental and give a feedback?
>
> Thanks
>

Just tested on both 21.04.3-3 in sid and 21.08.0-1 in experimental.
The function now works as intended, and I can't reproduce the bug
anymore.

Cheers!

Bug#992470: RFS: yuma123/2.12-1 -- NETCONF/YANG server/client development toolchain

[Vladimir Vassilev]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "yuma123":

 * Package name: yuma123
   Version : 2.12-1
   Upstream Author : Vladimir Vassilev 
 * URL : https://yuma123.org
 * License : public-domain, MIT, Artistic or GPL-1+, BSD-3-clause
 * Vcs : -
   Section : net

It builds those binary packages:

  libyangrpc-dev - NETCONF/YANG simple client applications development files
  libyangrpc2 - NETCONF/YANG library for simple client applications
  netconfd-module-ietf-system - SIL module for netconfd implementing 
ietf-system.yang
  netconfd-module-ietf-interfaces - SIL module for netconfd implementing 
ietf-interfaces.yang
  yangdump - Validate YANG modules and convert them to different formats
  yangcli - NETCONF/YANG command line client application
  netconfd - NETCONF (RFC-6241) agent
  libyuma-dev - NETCONF/YANG application development files
  libyuma2 - NETCONF/YANG library
  libyuma-base - Configuration script, YANG models and documentation

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/yuma123/

Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/y/yuma123/yuma123_2.12-1.dsc

Changes since the last upload:

 yuma123 (2.12-1) unstable; urgency=medium
 .
   * New upstream release.
   * Bump Standards version to 4.5.1
   * Updated homepage. Closes: #929522
   * Added "Multi-Arch: same" to -dev and module packages
   * Added 0005-Workaround-library-not-linked-against-libc.patch

Regards,
--
  Vladimir Vassilev

Bug#992469: debhelper: dh_installsystemd installs services in /usr/lib/systemd/system/

[Samuel Thibault]

Samuel Thibault, le jeu. 19 août 2021 03:19:52 +0200, a ecrit:
> Since recently (apparently between 13.3.4 and 13.4+nmu1),
> dh_installsystemd installs service files in /usr/lib/systemd/system/
> instead of /lib/systemd/system/.

(looking at the package log, I see “dh_installsystemd: Prefer
/usr/lib/systemd/ to /lib/systemd. (Closes: #987989)”, but AIUI
#987989 was not requesting to put files there, only to also check
dependencies etc. there.

At least, since lintian is complaining about services in
/usr/lib/systemd/, something needs to be done: either lintian stop
complainin, or debhelper revert to installing into /lib/systemd/system/
:)

Samuel

Bug#992469: debhelper: dh_installsystemd installs services in /usr/lib/systemd/system/

[Samuel Thibault]

Package: debhelper
Version: 13.4+nmu1
Severity: important

Hello,

Since recently (apparently between 13.3.4 and 13.4+nmu1),
dh_installsystemd installs service files in /usr/lib/systemd/system/
instead of /lib/systemd/system/. This can be seen for instance when
building the brltty package in a fresh sid chroot: the package merely
has a debian/brltty.service file, and now it ends up in
/usr/lib/systemd/system/brltty.service, and lintian complains about
that:

E: brltty: systemd-service-file-outside-lib 
usr/lib/systemd/system/brltty.service

Samuel

-- System Information:
Debian Release: 11.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 
'proposed-updates'), (500, 'oldstable-proposed-updates-debug'), (500, 
'oldstable-proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'), 
(500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 
'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages debhelper depends on:
ii  autotools-dev20180224.1+nmu1
ii  dh-autoreconf20
ii  dh-strip-nondeterminism  1.12.0-1
ii  dpkg 1.20.9
ii  dpkg-dev 1.20.9
ii  dwz  0.14-1
ii  file 1:5.39-3
ii  libdebhelper-perl13.3.4
ii  libdpkg-perl 1.20.9
ii  man-db   2.9.4-2
ii  perl 5.32.1-4
ii  po-debconf   1.0.21+nmu1

debhelper recommends no packages.

Versions of packages debhelper suggests:
ii  dh-make  2.202003

-- no debconf information

-- 
Samuel
 un driver qui fait quoi, alors ?
 ben pour les bips
 pour passer les oops en morse
 -+- #ens-mim - vive les rapports de bug -+-

Bug#992347: open-iscsi on upgrades fail to finish postinst script

[Jose M Calhariz]

On Wed, Aug 18, 2021 at 10:17:36PM +0530, Ritesh Raj Sarraf wrote:
> On Wed, 2021-08-18 at 19:35 +0530, Ritesh Raj Sarraf wrote:
> > On Wed, 2021-08-18 at 13:32 +0100, Jose M Calhariz wrote:
> > > I was expecting to be easy to collect the info in one or 2 files, but
> > > I am wrong.  I have 3 targets with multipath for 2 of them and I am
> > > not certain what is active.  I have multipath active, I am certain of
> > > that, because of the device I am mouting:
> > > /dev/mapper/mpath-X-part1
> > > 
> > > So I am expecting you need all files inside /etc/iscsi and some
> > > run-time info?
> > 
> > I am asking this information just for the sake of this task, to
> > ascertain why it failed in the first 30 seconds.
> > 
> > Since this worked for you, later, when you increased the timeout to 120
> > seconds; there's not much to do I suppose. But yes, from this bug
> > report's sake, having that information clarified will be good.

Giving that I have seen this bug before with my machines, it is only
the first time I am reporting and being the first reporter so I am
with you, this is some setting in my site or my machine.

With more reasearch with help from the local specialist I found a
an extra iSCSI setup to a local appliance that I not longer need.  So
I remove it from /etc/iscsi.  Doing again a:

dpkg --configure -a

Setting up open-iscsi (2.1.3-5) ...
open-iscsi postinst: since the check in preinst some iSCSI sessions have
 failed. -> will wait 30s for automatic recovery
Processing triggers for initramfs-tools (0.140) ...
update-initramfs: Generating /boot/initrd.img-5.10.0-8-amd64


This time it succeeds.  So this probably is a problem on my machine.
May I suggest for you to increase the timeout from 30s to 60 or 120s?

Mine reasoning is that my machine boots fast enough for me not
investigate more my iSCSI connections, but probably the iSCSI
appliance is giving authentication timeout and so the increased need
for a longer timeout on open-iscsi postinst.  Making the package more
robust.

We may talk more about this problem and I offer my time and machine to
do research on to improve the package if you see benefit on that.  But
I will not keep the bug open if you want to close it.

Kind regards
Jose M Calhariz

-- 
--
É difícil dizer o que e impossivel, pois a fantasia de
ontem e a esperanca de hoje e a realidade de
amanha.
-- Robert H. Goddard


signature.asc
Description: PGP signature

Bug#990784: universal-ctags: Follow-up patch fixing armhf FTBFS

[Athos Ribeiro]

Package: universal-ctags
Version: 0+git20200824-1.1
Followup-For: Bug #990784
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu impish ubuntu-patch
Control: tags -1 patch

The former patch did not fix the issue for armhf. This follow-up patch
appends a new patch to the debdiff to fix the issue in that platform as
well. This was forwarded upstream at 
https://github.com/universal-ctags/ctags/pull/3125

Thanks for considering the patch.

*** /tmp/tmpji1bibkw/universal-ctags_0+git20200824-1.1ubuntu1.debdiff
diff -Nru 
universal-ctags-0+git20200824/debian/patches/0001-main-add-newfstatat-to-seccomp-rules.patch
 
universal-ctags-0+git20200824/debian/patches/0001-main-add-newfstatat-to-seccomp-rules.patch
--- 
universal-ctags-0+git20200824/debian/patches/0001-main-add-newfstatat-to-seccomp-rules.patch
1969-12-31 21:00:00.0 -0300
+++ 
universal-ctags-0+git20200824/debian/patches/0001-main-add-newfstatat-to-seccomp-rules.patch
2021-07-06 16:48:58.0 -0300
@@ -0,0 +1,36 @@
+From f827e85fdee9bc438d3d28612c99478f9957e612 Mon Sep 17 00:00:00 2001
+From: Masatake YAMATO 
+Date: Sun, 2 May 2021 02:18:35 +0900
+Subject: [PATCH] main: add newfstatat to seccomp rules
+
+Close #2894.
+
+Signed-off-by: Masatake YAMATO 
+
+Origin: backport, 
https://github.com/universal-ctags/ctags/commit/f827e85fdee9bc438d3d28612c99478f9957e612
+Bug: https://github.com/universal-ctags/ctags/issues/2894
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990784
+Bug-Ubuntu: 
https://bugs.launchpad.net/ubuntu/+source/universal-ctags/+bug/1934829
+Last-Update: 2021-07-05
+
+---
+ main/seccomp.c | 3 +++
+ 1 file changed, 3 insertions(+)
+
+diff --git a/main/seccomp.c b/main/seccomp.c
+index 12e60982..27e704ea 100644
+--- a/main/seccomp.c
 b/main/seccomp.c
+@@ -43,6 +43,9 @@ int installSyscallFilter (void)
+   // The bowels of stdio want to know the size of a file, even for stdout.
+   seccomp_rule_add (ctx, SCMP_ACT_ALLOW, SCMP_SYS (fstat), 0);
+   seccomp_rule_add (ctx, SCMP_ACT_ALLOW, SCMP_SYS (fstat64), 0);
++#ifdef __SNR_newfstatat
++  seccomp_rule_add (ctx, SCMP_ACT_ALLOW, SCMP_SYS (newfstatat), 0);
++#endif
+ 
+   // seems unnecessary, but this comes from
+   // main/parse.c:2764 : tagFilePosition ();
+-- 
+2.25.1
+
diff -Nru 
universal-ctags-0+git20200824/debian/patches/0002-main-add-statx-to-seccomp-rules.patch
 
universal-ctags-0+git20200824/debian/patches/0002-main-add-statx-to-seccomp-rules.patch
--- 
universal-ctags-0+git20200824/debian/patches/0002-main-add-statx-to-seccomp-rules.patch
 1969-12-31 21:00:00.0 -0300
+++ 
universal-ctags-0+git20200824/debian/patches/0002-main-add-statx-to-seccomp-rules.patch
 2021-07-06 16:48:58.0 -0300
@@ -0,0 +1,19 @@
+Author: Athos Ribeiro 
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990784
+Bug-Ubuntu: 
https://bugs.launchpad.net/ubuntu/+source/universal-ctags/+bug/1934829
+Description: Add statx to seccomp rules as a fallback for newfstatat
+Forwarded: https://github.com/universal-ctags/ctags/pull/3125
+Last-Update: 2021-08-18
+--- a/main/seccomp.c
 b/main/seccomp.c
+@@ -46,6 +46,10 @@
+ #ifdef __SNR_newfstatat
+   seccomp_rule_add (ctx, SCMP_ACT_ALLOW, SCMP_SYS (newfstatat), 0);
+ #endif
++#ifdef __SNR_statx
++  // armhf fallback
++  seccomp_rule_add (ctx, SCMP_ACT_ALLOW, SCMP_SYS (statx), 0);
++#endif
+ 
+   // seems unnecessary, but this comes from
+   // main/parse.c:2764 : tagFilePosition ();
diff -Nru universal-ctags-0+git20200824/debian/patches/series 
universal-ctags-0+git20200824/debian/patches/series
--- universal-ctags-0+git20200824/debian/patches/series 1969-12-31 
21:00:00.0 -0300
+++ universal-ctags-0+git20200824/debian/patches/series 2021-07-06 
16:48:58.0 -0300
@@ -0,0 +1,2 @@
+0001-main-add-newfstatat-to-seccomp-rules.patch
+0002-main-add-statx-to-seccomp-rules.patch


-- System Information:
Debian Release: 11.0
  APT prefers impish
  APT policy: (500, 'impish')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.11.0-25-generic (SMP w/16 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- 
Athos Ribeiro

Bug#992439: libconfig-model-dpkg-perl: blocks fails autopkgtest with recent licensecheck

[gregor herrmann]

Control: tag -1 unreproducible

On Wed, 18 Aug 2021 17:41:06 +0200, Jonas Smedegaard wrote:

> Package: libconfig-model-dpkg-perl
> Version: 2.143
> Severity: important
> 
> Licensecheck seemingly gets blocked from entering stable currently, due
> to libconfig-model-dpkg-perl 2.143 fialing its autopkgtest:

I can't reproduce an autopkgtest failure of libconfig-model-dpkg-perl
locally, and I also don't see it at
https://ci.debian.net/packages/libc/libconfig-model-dpkg-perl/
(except for historical occurences but the last checks all seemed to
pass).

https://tracker.debian.org/pkg/licensecheck also shows no blocks from
libconfig-model-dpkg-perl.
 
(Not closing the bug as the earlier failures are a bit mysterious …
Maybe dod has an idea.)

I just did an upload for #992253, let's see what happens.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Bug#992449: cdimage.debian.org: sr kernel module is missing on install media for arm64 which prevents installation in KVM guest

[Steve McIntyre]

Hi Lance,

Sorry to hear that you're having problems here :-(

On Wed, Aug 18, 2021 at 12:49:05PM -0700, Lance Albertson wrote:
>I forgot to mention that the mini.iso image located here [1] does appear to
>work as expected FWIW. But the image found here [2] does not.
>
>[1] https://debian.osuosl.org/debian/dists/bullseye/main/installer-arm64/
>20210731/images/netboot/
>[2] https://debian.osuosl.org/debian-cdimage/11.0.0/arm64/iso-cd/

So, I'm surprised to read this. On release day I tested our arm64
media locally using qemu/KVM VMs on an arm64 host here. I've just
booted the netinst media again now (debian-11.0.0-arm64-netinst.iso)
and I can see the following modules loaded, clearly including sr_mod:

# lsmod
Module  Size  Used by
virtio_net 53248  0
net_failover   24576  1 virtio_net
failover   20480  1 net_failover
nls_utf8   16384  1
isofs  49152  1
sr_mod 32768  1
cdrom  61440  2 isofs,sr_mod
virtio_scsi24576  1
scsi_mod  221184  2 virtio_scsi,sr_mod
virtio_blk 28672  0
virtio_pci 28672  0
virtio_mmio24576  0
virtio_ring28672  5 
virtio_mmio,virtio_scsi,virtio_pci,virtio_blk,virtio_net
virtio 20480  5 
virtio_mmio,virtio_scsi,virtio_pci,virtio_blk,virtio_net

I'm curious why you might be seeing different. Could you share more
details of your setup please?

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"We're the technical experts.  We were hired so that management could
 ignore our recommendations and tell us how to do our jobs."  -- Mike Andrews

Bug#992468: python3-django-hyperkitty: 'Recent' and 'Popular' buttons hang forever.

[Peter Chubb]

Package: python3-django-hyperkitty
Version: 1.3.4-4
Severity: normal

Dear Maintainer,

I have a mailman3 plus hyperkitty installation, all installed from Debian.
When looking at the archives, I see a spinning wheel, for 'Activity Summary',
and 'Most active posters' on the left hand side, and for 
'Most recent discussions' in the middle.

Looking at the 'By month' lists works properly.

The lists are public, you can see one
at https://lists.sel4.systems/hyperkitty/list/devel@sel4.systems/



-- System Information:
Debian Release: 11.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-6-cloud-amd64 (SMP w/1 CPU thread)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-django-hyperkitty depends on:
ii  fonts-glyphicons-halflings   1.009~3.4.1+dfsg-2
ii  libjs-bootstrap4 4.5.2+dfsg1-8
ii  libjs-sphinxdoc  3.4.3-2
ii  python3  3.9.2-3
ii  python3-dateutil 2.8.1-6
ii  python3-django   2:2.2.24-1
ii  python3-django-compressor2.4-2
ii  python3-django-extensions3.0.3-3
ii  python3-django-gravatar2 1.4.4-2
ii  python3-django-haystack  3.0-1
ii  python3-django-mailman3  1.3.5-2
ii  python3-django-q 1.2.1-1
ii  python3-djangorestframework  3.12.1-1
ii  python3-elasticsearch7.1.0-3
ii  python3-flufl.lock   5.0.1-1
ii  python3-mailmanclient3.3.2-1
ii  python3-networkx 2.5+ds-2
ii  python3-robot-detection  0.4.0-2
ii  python3-tz   2021.1-1

Versions of packages python3-django-hyperkitty recommends:
ii  mailman3-web  0+20200530-2

python3-django-hyperkitty suggests no packages.

-- no debconf information

Bug#992401: alternative

[Jean-Francois Pirus]

use "command -v" as an alternative


DEPRECATION
  Since  type  and command -v were mandated by POSIX, this
utility is no longer useful for maintainer scripts and thus will be
removed from debianutils.

Bug#992422: device files not created

[Eriberto Mota]

Control: tag -1 confirmed

Hi Peter,

Thanks a lot for your messages about bugs in jailkit.

I confirmed this bug also using /dev/null. Consequently, I think any
creation around /dev will fail.

Thanks!

Regards,

Eriberto

Em qua., 18 de ago. de 2021 às 09:18, Peter Viskup
 escreveu:
>
> Package: jailkit
> Version: 2.21-4
>
> Running command to create jail with random and urandom devices produce 
> following errors:
>
> Creating device /chroot/dev/random
> mknod: invalid major device number ‘1.03125’
> Failed to create device /chroot/dev/random, this is a know problem with 
> python 2.1
> use "ls -l /dev/random" to find out the mode, major and minor for the device
> use "mknod /chroot/dev/random mode major minor" to create the device
> use chmod and chown to set the permissions as found by ls -l
> Creating device /chroot/dev/urandom
> mknod: invalid major device number ‘1.03515625’
> Failed to create device /chroot/dev/urandom, this is a know problem with 
> python 2.1
> use "ls -l /dev/urandom" to find out the mode, major and minor for the device
> use "mknod /chroot/dev/urandom mode major minor" to create the device
> use chmod and chown to set the permissions as found by ls -l
>
> Peter

Bug#992457: Broken by irresponsible removal of tempfile in debianutils

[Cyril Brulebois]

Joseph Carter  (2021-08-18):
> Presumably /installer-team/console-setup would be a better package to
> patch, unless cdebconf uses tempfile somehow.  I'll see what I can
> do this evening. 

Sure thing, miscompleted in my browser history plus slightly distracted,
sorry.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#992467: upgrade-reports: X crashes after startx is ran as a normal user bas well as when trying too loin with lightdm

[Matthew Dyer]

Package: upgrade-reports
Severity: important
X-Debbugs-Cc: ilovecountrymusic...@gmail.com

(Please provide enough information to help the Debian
maintainers evaluate the report efficiently - e.g., by filling
in the sections below.)

My previous release is: unstable/sid 
I am upgrading to: 
Archive date: 
Upgrade date: July 18 2021
uname -a before upgrade: Startx  launched mate desktop as expted.
uname -a after upgrade:  X 
crashes when running startx as normal user.
Method: 
apt full-upgrade.
Contents of /etc/apt/sources.list:


- Were there any non-Debian packages installed before the upgrade?  If
  so, what were they?

- Was the system pre-update a pure sarge system? If not, which packages
  were not from sarge?

- Did any packages fail to upgrade?
No.
- Were there any problems with the system after upgrading?
No.  Concle still works as expected.

Further Comments/Problems:
This One of the packaes that was upgraded was linux-firmware realtech nonfree 
from the non-free repo.

Please attach the output of "COLUMNS=200 dpkg -l" (or "env COLUMNS ...",
depending on your shell) from before and after the upgrade so that we
know what packages were installed on your system.

Bug#466407: Automated way to get suite names

[Oliver C.]

Dear Nye Liu

/usr/lib/os-release
does have enough informations to read the current suite name of the
installed system.

PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=debian
HOME_URL="https://www.debian.org/;
SUPPORT_URL="https://www.debian.org/support;
BUG_REPORT_URL="https://bugs.debian.org/;

and running a single command like
"apt search base-files"
will give you the information if it is oldstable, stable, testing or
something else.

Example:

apt search base-files
Sortierung... Fertig
Volltextsuche... Fertig
base-files/oldstable,now 10.3+deb10u10 amd64  [installiert]
  Debian base system miscellaneous files


oldstable is in the line base-files/oldstable.


If you combine both, you will know the stable/testing to suite name
mapping of the current installed system.

I hope this helps.

Best Regards
Oliver

Bug#992466: debianutils: add proper NEWS.Debian and release notes entry about dropped tools

[Christoph Anton Mitterer]

Package: debianutils
Version: 5.1-1
Severity: wishlist



Hi.

While I can understandt that it's desireable to get rid of custom legacy tools,
this should be more properly documented.

I guess a NEWS.Debian entry and some notes in the next release notes would be
appropriate.


The problems with xsessions has shown that the deprecation warning to stderr
might not have been enough, since the tool might be used in places where that
is never read.


In principle dropping it might be even security relevant, consider some (ab)use
like:
MYBASEDIR=/var/lib/foo  #being readable for anyone but writable only for some 
user
MYTMPDIR="$MYBASEDIR/$(tempfile -d)"
mkdir -p "$MYTMPDIR"
chown go= "$MYTMPDIR"

Now with tempfile gone and no proper error handling in above's example,
MYTMPDIR would be MYBASEDIR, and possibly sensitive data could end up in it
(now world readable).

Sure, the above would obviously be an abuse of tempfile,... but people might
still do it.
Thus, a big fat warning seems reasonable.


Cheers,
Chris.

Bug#992457: Broken by irresponsible removal of tempfile in debianutils

[Joseph Carter]

On Wed, Aug 18, 2021, at 14:01, Cyril Brulebois wrote:
> T. Joseph Carter  (2021-08-18):
> > It's debianutils' bug, really, and the bugs keep getting filed (and
> > resolved), but there's a half a dozen packages on my system that are
> > broken by it. Yours happens to be used at boot time and for general
> > system operation.
> 
> It's an ongoing conversation on IRC apparently, and yes, some kind of
> advance warning would have been appreciated.

O yes, I'm sure there is. I've missed those over the years. 
 

> That being said, it's not entirely crazy to attempt such changes very
> early in the release cycle, and if we ought to move away from those
> tools, I don't mind much.

Yes, but you "try" to do that by marking the packages deprecated and filing 
bugs that version 5, due out X weeks, and ask them to make changes or allow 
NMU.  Ideally, you then keep it around for a release or so AFTER you make 
Debian no longer dependent upon the tools.

Dunno who else would miss tempfile, but I'm kinda partial to which since 
command -v will NOT give you the path to a file if you typically alias that 
file, and type -P is not POSIX and does not work with dash.


> > If you're busy and debianutils' change doesn't get reverted, I can
> > prepare a patch. It's literally replacing tempfile and which with
> > their more generic equivalents, after all.
> 
> I think we'd be happy to have a patch or a merge request to review, even
> more so if you've tested it on a real system.
> 
> The git repo is at:
>   https://salsa.debian.org/installer-team/cdebconf/
> 
> but a patch against the source package would be fine too.
> 
> Thanks for the heads-up!

Presumably /installer-team/console-setup would be a better package to patch, 
unless cdebconf uses tempfile somehow.  I'll see what I can do this evening. 

Joseph

Bug#992465: [lintian] systemd-service-file-outside-lib should not flag /usr/lib/systemd/system/

[Peter Pentchev]

Package: lintian
Version: 2.104.0
Severity: normal
Tags: patch
X-Debbugs-Cc: r...@debian.org

Hi,

Thanks a lot for all your work on Lintian!

The systemd-service-file-outside-lib checks have, since 2015, flagged
unit files found in the /usr/lib/systemd/system/ directory. It seems
that at some point since then (I'm not exactly sure when), maybe because
of the merged-/usr layout, maybe for other reasons, systemd on Debian
has started actually paying attention to unit files found there.

I noticed this almost accidentally, when I rebuilt (still only locally,
although I do intend to upload it soon) my stunnel4 package with
debhelper 13.4 as found in unstable now: as part of fixing #987989,
debhelper now installs unit files in /usr/lib/systemd/system/ instead of
/lib/systemd/system/; see:

  
https://salsa.debian.org/debian/debhelper/-/commit/d70caa69c64b124e3611c967cfab93aef48346d8

So debhelper now produces packages that will place unit files into /usr,
and I have just verified that the systemd in testing does, indeed,
notice these files - I successfully enabled and started a stunnel@foo
service through a stunnel@.service file in /usr/lib/systemd/system/.

Maybe it's time to change the systemd-service-file-outside-lib check, at
least partially? (the "do not place unit files in /etc" part is still
very, very good advice for a package)  What do you think about the
attached patch? Tomorrow I will also send another one that adds
(?:usr/)? to a couple of other regular expression checks (with some more
work for at least one of them) so that these files are properly checked,
too.

G'luck,
Peter

-- System Information:
Debian Release: 11.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (500, 
'stable-security'), (500, 'oldoldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads)
Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.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 lintian depends on:
ii  binutils2.35.2-2
ii  bzip2   1.0.8-4
ii  diffstat1.64-1
ii  dpkg1.20.9
ii  dpkg-dev1.20.9
ii  file1:5.39-3
ii  gettext 0.21-4
ii  gpg 2.2.27-2
ii  intltool-debian 0.35.0+20060710.5
ii  libapt-pkg-perl 0.1.40
ii  libarchive-zip-perl 1.68-1
ii  libcapture-tiny-perl0.48-1
ii  libclass-xsaccessor-perl1.19-3+b7
ii  libclone-perl   0.45-1+b1
ii  libconfig-tiny-perl 2.26-1
ii  libcpanel-json-xs-perl  4.25-1+b1
ii  libdata-dpath-perl  0.58-1
ii  libdata-validate-domain-perl0.10-1.1
ii  libdevel-size-perl  0.83-1+b2
ii  libdpkg-perl1.20.9
ii  libemail-address-xs-perl1.04-1+b3
ii  libfile-basedir-perl0.08-1
ii  libfile-find-rule-perl  0.34-1
ii  libfont-ttf-perl1.06-1.1
ii  libhtml-html5-entities-perl 0.004-1.1
ii  libipc-run3-perl0.048-2
ii  libjson-maybexs-perl1.004003-1
ii  liblist-compare-perl0.55-1
ii  liblist-moreutils-perl  0.430-2
ii  liblist-utilsby-perl0.11-1
ii  libmoo-perl 2.004004-1
ii  libmoox-aliases-perl0.001006-1.1
ii  libnamespace-clean-perl 0.27-1
ii  libpath-tiny-perl   0.118-1
ii  libperlio-gzip-perl 0.19-1+b7
ii  libproc-processtable-perl   0.59-2+b1
ii  libsereal-decoder-perl  4.018+ds-1+b1
ii  libsereal-encoder-perl  4.018+ds-1+b1
ii  libtext-glob-perl   0.11-1
ii  libtext-levenshteinxs-perl  0.03-4+b8
ii  libtext-markdown-discount-perl  0.12-1+b1
ii  libtext-xslate-perl 3.5.8-1+b1
ii  libtime-duration-perl   1.21-1
ii  libtime-moment-perl 0.44-1+b3
ii  libtimedate-perl2.3300-2
ii  libtry-tiny-perl0.30-1
ii  libtype-tiny-perl   1.012002-1
ii  libunicode-utf8-perl0.62-1+b2
ii  liburi-perl 5.08-1
ii  libxml-libxml-perl  2.0134+dfsg-2+b1
ii  libyaml-libyaml-perl0.82+repack-1+b1
ii  lzip1.22-3
ii  lzop1.04-2
ii  man-db  2.9.4-2
ii  patchutils  0.4.2-1
ii  perl [libdigest-sha-perl]   5.32.1-4
ii  t1utils 1.41-4
ii  unzip   6.0-26
ii  xz-utils5.2.5-2

lintian recommends no packages.

Versions of packages lintian suggests:
ii  binutils-multiarch 2.35.2-2
ii  libtext-template-perl  1.59-1

-- no debconf information
From 85cb59f7bb09aaf97b0ea88f9ecd5c30cd453752 Mon 

Bug#992464: ITP: python-fastbencode -- Fast implementation of bencode serializer/deserializer

[Jelmer Vernooij]

Package: wnpp
Severity: wishlist
Owner: Jelmer Vernooij 
X-Debbugs-Cc: debian-de...@lists.debian.org, gzl...@googlemail.com

* Package name: python-fastbencode
  Version : 0.0.4
  Upstream Author : Breezy Developers
* URL : http://github.com/breezy-team/fastbencode
* License : GPL
  Programming Lang: Python/C/Cython
  Description : Fast implementation of bencode serializer/deserializer

A fast (C/Cython-based) implementation of the bencode serialization
mechanism used by e.g. BitTorrent.

This is a new dependency for Breezy.

Bug#992463: wbritish: Does not include the word 'shite'

[mooff]

Package: wbritish
Version: 2019.10.06-1
Severity: normal
X-Debbugs-Cc: mooff@awful.cooking

Dear Maintainer,

'Shite' is a fairly common British word, but does not appear in any of
the wbritish wordlists.

I propose the inclusion of 'shite' and 'shites' in wbritish 邏

With outbreaks of 'shitey' in one of the larger lists.

Thanks

Bug#758559: mlocate: updatedb option to exclude all filesystems not in /

[Steinar H. Gunderson]

On Mon, Aug 18, 2014 at 04:06:38PM -0400, John Kennerson wrote:
> It would be nice if updatedb had an option to prune all file systems
> not listed in /etc/fstab. There doesn't seem to be an easy way to
> achieve this at the moment.

mlocate has been removed from Debian, and has been replaced with plocate.
I'm going through the list of mlocate bugs to try to figure out if any of
them are relevant for plocate.

Is this still a desire? Can you explain a bit what the use case is?

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

Bug#992461: qa.debian.org: [udd] upload_date and date stalled

[Joao Eriberto Mota Filho]

Package: qa.debian.org
Severity: normal
X-Debbugs-Cc: nil...@debian.org

Dear UDD admin,

The last registered date in 'upload_date' from 'bapase' is 2021-08-13. In my
tests I can see the same problem in 'date' from 'upload_history'.

Can you check, please?

Thanks in advance.

Regards,

Eriberto

Bug#992371: transition: opensubdiv

[Matteo F. Vescovi]

Control: tags -1 -moreinfo

Hi again!

On 2021-08-18 at 21:46 (+02), Paul Gevers wrote:

[...]

> Please go ahead.

[...]

I've just uploaded the library to unstable/sid; thus removing
the 'moreinfo' tag accordingly.

Thanks.


-- 
Matteo F. Vescovi || Debian Developer
GnuPG KeyID: 4096R/0x8062398983B2CF7A


signature.asc
Description: PGP signature

Bug#992460: nmu: gemmi_0.4.5+ds-1 libemf2svg_1.1.0+ds-2

[Andrius Merkys]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

Hello,

I want to request binNMU on amd64 for recently accepted new packages, as
they cannot be migrated to testing due to missing builds on buildd.

  nmu gemmi_0.4.5+ds-1 . amd64 . unstable . -m "Rebuild on buildd"
  nmu libemf2svg_1.1.0+ds-2 . amd64 . unstable . -m "Rebuild on buildd"

Thanks,
Andrius

Bug#992445: libpam-mysql: Update package to 1.0.0~beta1 version to add support for blowfish and other encryptions

[Anton Avramov]

Package: libpam-mysql
Severity: wishlist
Tags: upstream

Dear Maintainer,

In order to increase security it would be great if you can update that
package to the latest upstream version. This would add blowfish and
other stronger encryption algorithms

Best Regards


-- System Information:
Debian Release: 10.10
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-17-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8), 
LANGUAGE=bg_BG.UTF-8 (charmap=UTF-8)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libpam-mysql depends on:
ii libc6 2.28-10
ii libmariadb3 1:10.4.17+maria~buster
ii libpam0g 1.3.1-5
ii libssl1.1 1.1.1d-0+deb10u6
ii zlib1g 1:1.2.11.dfsg-1

libpam-mysql recommends no packages.

libpam-mysql suggests no packages.

Bug#992457: Broken by irresponsible removal of tempfile in debianutils

[Cyril Brulebois]

Control: retitle -1 Broken by removal of tempfile in debianutils

Hi,

T. Joseph Carter  (2021-08-18):
> Debianutils >= 5 removes tempname and puts a deprecation notice on the
> which command. The setupcon script (at least) uses both of these,
> causing people's initramfs's to be subtly broken and leaving them
> without a keymap in the event of a boot error., Since the maintainer
> of Debianutils seems to be content to put out fires as they come up
> with the excuse that the stable version of Debian declares these to be
> deprecated (y'know, the one that was released a week ago at time of
> writing), it is apparently incumbent upon others to fix this in their
> packages.
> 
> It's debianutils' bug, really, and the bugs keep getting filed (and
> resolved), but there's a half a dozen packages on my system that are
> broken by it. Yours happens to be used at boot time and for general
> system operation.

It's an ongoing conversation on IRC apparently, and yes, some kind of
advance warning would have been appreciated.

That being said, it's not entirely crazy to attempt such changes very
early in the release cycle, and if we ought to move away from those
tools, I don't mind much.

> If you're busy and debianutils' change doesn't get reverted, I can
> prepare a patch. It's literally replacing tempfile and which with
> their more generic equivalents, after all.

I think we'd be happy to have a patch or a merge request to review, even
more so if you've tested it on a real system.

The git repo is at:
  https://salsa.debian.org/installer-team/cdebconf/

but a patch against the source package would be fine too.

Thanks for the heads-up!


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#992459: Do we really need a separate dino-im-common package?

[Pirate Praveen]

Package: dino
severity: wishlist

For example nheko (or most gnome apps) just ships the arch independent 
files also in nheko (or in their main package - for example 
gnome-calendar) binary package. I'm not really sure if splitting a 
separate package just for translations and icons is really a good idea 
(it does save some disk space, yes). Is there some document that 
recommends this kind of splitting?


The downside I see is users installing from backports will have to now 
install two binary packages or toggle priority of all packages in 
backports. I think we will be mostly likely pushing new upstream 
versions via bullseye-backports.

Bug#992371: transition: opensubdiv

[Matteo F. Vescovi]

Hi Paul!

On 2021-08-18 at 21:46 (+02), Paul Gevers wrote:

[...]

> Please go ahead. As you mentioned on IRC that you also maintain blender,
> do you intent to upload that too, or should we schedule the binNMU's as
> normal?

Blender 2.93.2 in experimental is actually ftbfs on mipsel and I've
pinged my upstream contacts to fix that, as well.
They told me that they'll try to implement the solution already provided
by sramacher (thanks Seb!) within next week. So I'll wait for it before
uploading the experimental package to unstable/sid.

My build tests were made as pure binNMU for the version of blender in
unstable/sid at the moment. So normal approach is the way to go, for
now. Thanks for asking.

Cheers.


-- 
Matteo F. Vescovi || Debian Developer
GnuPG KeyID: 4096R/0x8062398983B2CF7A


signature.asc
Description: PGP signature

Bug#992458: hoteldruid: use mktemp instead of tempfile in postinst

[Clint Adams]

Package: hoteldruid
Version: 3.0.1-1

tempfile is deprecated and mktemp is better

Bug#991696: Bug#991698: Possible CVE-2014-5461 in enigma-data

[Erich Schubert]

reassign 991698 enigma

merge 991698 991696

thanks

It does not make sense to report the bug against the *data* package. Its 
in the binary, not the data. No need to report it twice.


Also, why use a screenshot of the diff, and not just the diff directly, 
wtf? Why would you make a screenshot of a diff in the first place?


Clearly this should be fixed, but the security implications are very 
limited.



The enigma package currently is not maintained. A new upstream version 
exists.


Someone has indicated the intent to adopt the package, but not much has 
happened so far: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902855



Am 30.07.21 um 13:12 schrieb Movses Tovmasyan:

Package: enigma-data
Version: 1.20-dfsg.1-2.1
Tags: patch

enigma-data uses the obsolete version of minilua
(single-file port of Lua) which has CVE-2014-5461
Patch attached below.

Bug#992457: Broken by irresponsible removal of tempfile in debianutils

[T. Joseph Carter]

Package: console-setup
Version: 1.205
Severity: important
X-Debbugs-Cc: 

Debianutils >= 5 removes tempname and puts a deprecation notice on the
which command. The setupcon script (at least) uses both of these,
causing people's initramfs's to be subtly broken and leaving them
without a keymap in the event of a boot error., Since the maintainer of
Debianutils seems to be content to put out fires as they come up with
the excuse that the stable version of Debian declares these to be
deprecated (y'know, the one that was released a week ago at time of
writing), it is apparently incumbent upon others to fix this in their
packages.

It's debianutils' bug, really, and the bugs keep getting filed (and
resolved), but there's a half a dozen packages on my system that are
broken by it. Yours happens to be used at boot time and for general
system operation.

If you're busy and debianutils' change doesn't get reverted, I can
prepare a patch. It's literally replacing tempfile and which with their
more generic equivalents, after all.

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

Kernel: Linux 5.10.0-8-amd64 (SMP w/16 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 not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages console-setup depends on:
ii  console-setup-linux 1.205
ii  debconf 1.5.77
ii  keyboard-configuration  1.205
ii  xkb-data2.33-1

console-setup recommends no packages.

Versions of packages console-setup suggests:
ii  locales   2.31-16
ii  lsb-base  11.1.0

Versions of packages keyboard-configuration depends on:
ii  debconf 1.5.77
ii  liblocale-gettext-perl  1.07-4+b1

Versions of packages console-setup-linux depends on:
ii  init-system-helpers 1.60
ii  kbd 2.3.0-3
ii  keyboard-configuration  1.205

console-setup-linux suggests no packages.

Versions of packages console-setup is related to:
pn  console-common
pn  console-data  
pn  console-tools 
ii  gnome-control-center  1:3.38.4-1
ii  kbd   2.3.0-3
ii  systemd   247.9-1

-- debconf information:
  keyboard-configuration/layout:
  keyboard-configuration/unsupported_config_options: true
  keyboard-configuration/ctrl_alt_bksp: false
* console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic 
languages
* console-setup/fontsize-fb47: 16x32 (framebuffer only)
  keyboard-configuration/store_defaults_in_debconf_db: true
  debian-installer/console-setup-udeb/title:
  keyboard-configuration/xkb-keymap: us
  console-setup/fontsize: 16x32
  keyboard-configuration/unsupported_layout: true
  keyboard-configuration/switch: No temporary switch
  keyboard-configuration/model: Generic 105-key PC (intl.)
  keyboard-configuration/toggle: No toggling
  console-setup/framebuffer_only:
  keyboard-configuration/layoutcode: us
  keyboard-configuration/optionscode:
  keyboard-configuration/compose: No compose key
  keyboard-configuration/modelcode: pc105
  keyboard-configuration/variantcode:
  keyboard-configuration/unsupported_config_layout: true
  console-setup/fontsize-text47: 16x32 (framebuffer only)
  console-setup/store_defaults_in_debconf_db: true
  keyboard-configuration/altgr: The default for the keyboard layout
  keyboard-configuration/unsupported_options: true
  keyboard-configuration/other:
* console-setup/fontface47: TerminusBold
  console-setup/guess_font:
* keyboard-configuration/variant: English (US)
* console-setup/charmap47: UTF-8
  console-setup/codesetcode: Lat15
  console-setup/use_system_font:

Bug#992456: RFS: libonig/6.9.7.1-2 -- regular expressions library

[Jörg Frings-Fürst]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "libonig":

   Package name: libonig
   Version : 6.9.7.1-2
   Upstream Author : [fill in name and email of upstream]
   URL : https://github.com/kkos/oniguruma
   License : BSD-2-clause
   Vcs : https://jff.email/cgit/libonig.git
   Section : libs

It builds those binary packages:

  libonig-dev - regular expressions library — development files
  libonig5 - regular expressions library

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/libonig/

Alternatively, one can download the package with dget using this
command:

  dget -x 
https://mentors.debian.net/debian/pool/main/libo/libonig/libonig_6.9.7.1-2.dsc

or from 

 git https://jff.email/cgit/libonig.git/?h=release/debian/6.9.7.1-2

Changes since the last upload:

 libonig (6.9.7.1-2) unstable; urgency=medium
 .
   * Upload into unstable.
   * Declare compliance with Debian Policy 4.6.0 (No changes needed).


CU
Jörg
-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema: SYR8SJXB
Wire: @joergfringsfuerst
Skype: joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.



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

Bug#992455: canna: use mktemp instead of tempfile in postinst

[Clint Adams]

Package: canna
Version: 3.7p3-16

tempfile was deprecated and mktemp is better anyway

Bug#992454: clamsmtp: use mktemp in postinst instead of tempfile

[Clint Adams]

Package: clamsmtp
Version: 1.10-17

tempfile was deprecated and is no longer in debianutils; mktemp is
better anyway

Bug#992453: caja-rename: Sometimes pressing F2 on a file/folder does absolutely nothing

[Andreas Rönnquist]

Package: caja-rename
Version: 20.1.26-1
Severity: important

Dear Maintainer,

I am using caja on a Xfce desktop (still on Buster), and noticed that
sometimes I couldn't rename a file by simply pressing F2. This sent me
of on a wild goose-chase on permissions and whatnot in the affected
folder (it was on a nfs-share, if that matters).

By running caja in a terminal I have found that what I run into is a bug
in caja-rename - which already has been reported and fixed upstream:

https://bugs.launchpad.net/ubuntu/+source/caja-rename/+bug/1877718

which is a one-liner fix (2 counting whitespace):

https://github.com/tari01/caja-rename/pull/4/files

This seems to also still be a problem in both Buster / Bullseye, and
also in Sid.

If you need prepared packages / sponsoring for stable / old-stable, I
would gladly help out with this too.


-- System Information:
Debian Release: 11.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-1-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.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 caja-rename depends on:
ii  caja1.24.0-1+b1
ii  gir1.2-gtk-3.0  3.24.30-1
ii  python3 3.9.2-3
ii  python3-caja1.24.0-3
ii  python3-gi  3.38.0-2

caja-rename recommends no packages.

caja-rename suggests no packages.

Bug#976301: closed by Debian FTP Masters (reply to Sean Whitton ) (Bug#976301: fixed in debian-policy 4.6.0.0)

[Sean Whitton]

Hello Anatoli,

On Wed 18 Aug 2021 at 09:54AM +03, Anatoli Babenia wrote:

> My last comment is not addressed.

I'm afraid I still disagree with you about this.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#992452: Links between documents broken

[Carsten Leonhardt]

Package: bacula-doc
Version: 9.6.7-1

Links between the documents point to, for example,
../utility/utility.pdf but in the package the directory structure isn't
used and the pdfs are gzipped.

Example: main.pdf.gz, Chapter 25.1, there are links to bextract and
bscan.

Bug#992362: release-notes: Out of step wuth apt maintainers

[Brian Potkin]

On Wed 18 Aug 2021 at 10:19:06 +0300, Andrei POPESCU wrote:

> On Ma, 17 aug 21, 20:20:40, Brian Potkin wrote:
> > Package: release-notes
> > Severity: normal
> > 
> > 
> > Please see
> > 
> >   https://lists.debian.org/debian-doc/2021/08/msg00077.html
> > 
> > Then look at
> > 
> >   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758316
> > 
> > How abut a bit of consistency?
> 
> As I understand it the APT maintainers are just saying it doesn't bring 
> much (if any) security or privacy benefit, they don't explicitly 
> recommend against it.

They closed the report. That is sufficient reason to take notice of
their stance.
 
> For the Release Notes itself there is however a real benefit in avoiding 
> all future bug reports asking to use https:// everywhere ;)

A reasonable acceptable argument in this context.

> Kind regards,
> Andrei (just an occasional contributor to the Release Notes)

But a welcome one.

-- 
Brian.

Bug#992451: RFS: sane-backends/1.0.32-4 -- API library for scanners

[Jörg Frings-Fürst]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "sane-backends":

   Package name: sane-backends
   Version : 1.0.32-4
   Upstream Author : [fill in name and email of upstream]
   URL : http://www.sane-project.org
   License : Artistic, GPL-3+, GPL-2, GPL-2+,
 GPL-2+ with sane exception, GFDL-1.1, LGPL-2.1+
   Vcs : https://jff.email/cgit/sane-backends.git
   Section : graphics

It builds those binary packages:

  libsane - API library for scanners [transitional package]
  libsane-dev - API development library for scanners [development files]
  libsane1 - API library for scanners
  libsane-common - API library for scanners -- documentation and support files
  sane-utils - API library for scanners -- utilities

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/sane-backends/

Alternatively, one can download the package with dget using this
command:

 dget -x 
https://mentors.debian.net/debian/pool/main/s/sane-backends/sane-backends_1.0.32-4.dsc

or from 

 git https://jff.email/cgit/sane-backends.git?h=release/debian/1.0.32-4

Changes since the last upload:

 sane-backends (1.0.32-4) unstable; urgency=medium
 .
   * Upload into unstable.
   * Declare compliance with Debian Policy 4.6.0 (No changes needed).

CU
Jörg
-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema: SYR8SJXB
Wire: @joergfringsfuerst
Skype: joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.



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

Bug#992449: cdimage.debian.org: sr kernel module is missing on install media for arm64 which prevents installation in KVM guest

[Lance Albertson]

I forgot to mention that the mini.iso image located here [1] does appear to
work as expected FWIW. But the image found here [2] does not.

[1]
https://debian.osuosl.org/debian/dists/bullseye/main/installer-arm64/20210731/images/netboot/
[2] https://debian.osuosl.org/debian-cdimage/11.0.0/arm64/iso-cd/

-- 
Lance Albertson
Director
Oregon State University | Open Source Lab

Bug#992371: transition: opensubdiv

[Paul Gevers]

Control: tags -1 confirmed moreinfo

Hi Matteo,

On 17-08-2021 23:08, Matteo F. Vescovi wrote:
> Following advice/request from fellow DD elbrus, I'm filing this
> transition bug report to track down the one-package transition of
> opensubdiv library.

Thanks.

> The only reverse dependency for osd is blender, as in [1];
> I've already test-built it to check any FTBFS and it builds fine.
> 
> Thanks for your time and patience.

Please go ahead. As you mentioned on IRC that you also maintain blender,
do you intent to upload that too, or should we schedule the binNMU's as
normal?

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Bug#992432: RFS: frobby (NEW binary package)

[Torrance, Douglas]

Control: tags -1 pending

Due to [1], frobby needs a soname version bump and hence a NEW binary package
(libfrobby0 -> libfrobby1).  As a DM, I'm not able to upload packages to the
NEW queue.  Would anyone be able to review/sponsor?

https://salsa.debian.org/science-team/frobby

Thanks!
Doug

[1] https://bugs.debian.org/992432

Bug#992450: RFS: shotwell/0.30.14-1 -- digital photo organizer

[Jörg Frings-Fürst]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "shotwell":

   Package name: shotwell
   Version : 0.30.14-1
   Upstream Author : Jim Nelson 
   URL : https://wiki.gnome.org/Apps/Shotwell
   License : LGPL-2.1
   Vcs : https://jff.email/cgit/shotwell.git
   Section : gnome

It builds those binary packages:

  shotwell-common - digital photo organizer - common files
  shotwell - digital photo organizer

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/shotwell/

Alternatively, one can download the package with dget using this
command:

 dget -x 
https://mentors.debian.net/debian/pool/main/s/shotwell/shotwell_0.30.14-1.dsc

or from 

 git https://jff.email/cgit/shotwell.git/?h=release/debian/0.30.14-1

Changes since the last upload:

 shotwell (0.30.14-1) unstable; urgency=medium
 .
   * New upstream release.
   * Declare compliance with Debian Policy 4.6.0 (No changes needed).
   * debian/copyright:
 - Add year 2021 for debian/* to myself.

CU
Jörg

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema: SYR8SJXB
Wire: @joergfringsfuerst
Skype: joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.



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

Bug#930373: Shotwell: double clicking on the image viewer freezes an image of the picture. Reboot required

[Jörg Frings-Fürst]

fixed 930373 shotwell/0.30.4-1
thanks


Hello,

this bug is fixed since release 0.30.4-1.

Closed.

CU
Jörg
-- 
Jörg Frings-Fürst
IT
SNCT GmbH

Agnes-Karll-Straße 11, 19205 Gadebusch

+49 5766 6470901 (Phone)
+49 3886 715769  (Fax)
http://www.snct-gmbh.de

Zertifizierter Datenschutzbeauftragter (IHK)

GPG Fingerprint: 5599 046E DE76 C399 B55C  28E2 B6ED 6EB0 EF4D 23AF
GPG key : B6ED6EB0EF4D23AF

Social Network Catering Trade GmbH
Geschäftsführung: Stephan Jahnke
Eintrag: Amtsgericht Schwerin, HRB 11104
USt-Id.Nr.: DE 278140988

BNetzA DREG-Nr: 19/100


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

Bug#992449: cdimage.debian.org: sr kernel module is missing on install media for arm64 which prevents installation in KVM guest

[Lance Albertson]

Package: cdimage.debian.org
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

While attempting to use either the net install or DVD media on an arm64 guest 
on bullseye, the installer is unable to find the installation media found on 
the ISO (cdrom). I was able to get to the prompt and attempted to load the sr 
module (cdrom driver) but the module is missing. This prevents installation for 
any user using the ISO images for arm64.

Bug#985424: vorta: "Backup successful" notification even if return code is 1

[Nicholas D Steeves]

Hi Sandro,

Sandro Tosi  writes:

> Package: vorta
> Version: 0.7.5-1
> Severity: normal
>
> Hello,
> i have a few unaccessible files, so vorta during the backup records that, and
> the backup itself finished with a return code of 1.
>
> but the notification says "backup successful" -- that's rather confusing
>
> - does the return code of the backup not indicate the success or not of the
>   backup?
> - will the backup end up not being succesful only if a specific list of return
>   codes are returned?
>

I just uploaded 0.7.7-1, but I'm not convinced that upstream's chosen
implementation sufficiently addresses this bug.  Would you please give
it a try and let me know what you think?

Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#992448: agda: fails to compile hello world

[Francis Southern]

Source: agda
Version: 2.5.4.1-3
Severity: important

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

I installed the following packages:
agda/stable 2.5.4.1-3 all
agda-bin/stable 2.5.4.1-3+b1 amd64
agda-mode/stable 2.5.4.1-3 all
agda-stdlib/stable,now 0.17-1 all
agda-stdlib-doc/stable 0.17-1 all

I followed the instructions at 
.

The file  checked correctly within Emacs, but when I tried to 
compile the file  I received the following output:

$ agda --compile hello-world.agda
Compiling Agda.Primitive in 
/usr/share/libghc-agda-dev/lib/prim/Agda/Primitive.agdai to 
/home/$user/code/agda/MAlonzo/Code/Agda/Primitive.hs
Compiling Agda.Builtin.Unit in 
/usr/share/libghc-agda-dev/lib/prim/Agda/Builtin/Unit.agdai to 
/home/$user/code/agda/MAlonzo/Code/Agda/Builtin/Unit.hs
Compiling Agda.Builtin.IO in 
/usr/share/libghc-agda-dev/lib/prim/Agda/Builtin/IO.agdai to 
/home/$user/code/agda/MAlonzo/Code/Agda/Builtin/IO.hs
Compiling Agda.Builtin.Bool in 
/usr/share/libghc-agda-dev/lib/prim/Agda/Builtin/Bool.agdai to 
/home/$user/code/agda/MAlonzo/Code/Agda/Builtin/Bool.hs
Compiling Agda.Builtin.Nat in 
/usr/share/libghc-agda-dev/lib/prim/Agda/Builtin/Nat.agdai to 
/home/$user/code/agda/MAlonzo/Code/Agda/Builtin/Nat.hs
Compiling Agda.Builtin.Char in 
/usr/share/libghc-agda-dev/lib/prim/Agda/Builtin/Char.agdai to 
/home/$user/code/agda/MAlonzo/Code/Agda/Builtin/Char.hs
Compiling Agda.Builtin.List in 
/usr/share/libghc-agda-dev/lib/prim/Agda/Builtin/List.agdai to 
/home/$user/code/agda/MAlonzo/Code/Agda/Builtin/List.hs
Compiling Agda.Builtin.String in 
/usr/share/libghc-agda-dev/lib/prim/Agda/Builtin/String.agdai to 
/home/$user/code/agda/MAlonzo/Code/Agda/Builtin/String.hs
Compiling hello-world in /home/$user/code/agda/hello-world.agdai to 
/home/$user/code/agda/MAlonzo/Code/QhelloZ45Zworld.hs
agda: /usr/share/libghc-agda-dev/MAlonzo/src: 
getDirectoryContents:openDirStream: does not exist (No such file or directory)

A brief web search led me to believe that this was a problem with the Debian 
package and I uninstalled the packages listed above and installed Agda with 
cabal instead, which produces the expected output.


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

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

Bug#984182:

[Jose Luis Rivero]

Upstream bug: https://github.com/ignitionrobotics/ign-common/issues/239

Bug#992447: php-oscarotero-gettext build depends on the removed php-twig-extensions

[Adrian Bunk]

Source: php-oscarotero-gettext
Version: 4.8.2-4
Severity: serious
Tags: ftbfs

The following packages have unmet dependencies:
 builddeps:php-oscarotero-gettext : Depends: php-twig-extensions but it is not 
installable

Bug#992376: systemd-standalone-{sysusers, tmpfiles}: missing Breaks+Replaces: systemd (<< 249.3-2)

[Michael Biebl]

Am 18.08.21 um 01:28 schrieb Michael Biebl:

Am 18.08.2021 um 01:18 schrieb Andreas Beckmann:

On 18/08/2021 01.09, Michael Biebl wrote:

It's not a package split.


It looked like one.

systemd-standalone-* are new packages. They follow the debian policy 
recommended way using C/R/P against a virtual package.


You still need versioned B+R (or similar) against systemd versions not 
providing the new virtual package.


This is only relevant for partial upgrades which are semi-supported.



I'll probably try to get systemd in stable updated to have Provides: 
systemd-{sysusers,tmpfiles}





OpenPGP_signature
Description: OpenPGP digital signature

Bug#931749: [pkg-cryptsetup-devel] Bug#931749: cryptsetup: "no longer required" on encrypted system!

[Chris Hofstaedtler]

Hi,

* Guilhem Moulin  [210818 18:26]:
> On Wed, 10 Jul 2019 at 00:01:00 +0100, Conrad J.C. Hughes (for Debian package 
> stuff) wrote:
> > So this is probably a buster upgrade issue, but not sure where to report 
> > it..
> >
> > After upgrading to buster, deborphan --guess-dummy (seemingly correctly)
> > identified cryptsetup as a transitional dummy package, suitable for removal.
> > However after removing cryptsetup, apt now tells me all the time that
> > cryptsetup-bin, cryptsetup-initramfs and cryptsetup-run "were automatically
> > installed and are no longer required".  But my system's 
> > LUKS1-on-LVM-RAID-1..
> > Running "apt autoremove" at this point would surely cause chaos?
> 
> Sounds like a feature request for deborphan, reassigning and retitling
> accordingly.

[..]

> So if you remove the transition package you'll also need to `apt mark
> manual` the dependencies.  I guess deborphan could do that
> automatically?

It's unclear to me -how- the packages got removed. If just
"deborphan" was used: deborphan itself does not apply any changes.
If "orphaner" was used, then this is a duplicate of #617863, which I
will be closing soon because orphaner will go away.

Best,
Chris

Bug#992446: ITP: django-graphiql-debug-toolbar -- Django Debug Toolbar for GraphiQL IDE

[Carsten Schoenert]

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

* Package name: django-graphiql-debug-toolbar
  Version : 0.1.4
  Upstream Author : mongkok 
* URL : https://github.com/flavors/django-graphiql-debug-toolbar
* License : MIT
  Programming Lang: Python
  Description : Django Debug Toolbar for GraphiQL IDE

 This package adds a debug toolbar within your Django application for
 the GraphiQL IDE.

This package is an direct dependency for the next major version of
NetBox (will be version 3) which I consider to package.

The package will get maintained within the Debian Python Team.

Bug#988329: ITA: usbredir/0.9.0-1 -- Simple USB host TCP server

[Lin Qigang]

Hi Tobi,

> (- as said in the mail before, dont close the RFS bug in the changelog)
> 

> -   you could add yourself to the debian/* section in d/copyright,
> -   d/control
> -   has still the old S-V of 4.2.1...
> -   the long description for usbredirserver, the deprecation notice should
> 

> possibly have its own paragraph?
> -   is the B-D on cmake necessary? (as the package uses meson)

I made the changes, it should be good now

> As othewise the package looks good, so lets finish the polishing and 
> then do the upload!   


I retargeted the package to unstable since Debian released recently. I noticed 
there was a new version of usbredir released last week. Should I reupload the 
package with that version?

Lin Qigang 
GPG Fingerprint:  8CAD 1250 8EE0 3A41 7223  03EC 7096 F91E D75D 028F

signature.asc
Description: OpenPGP digital signature

Bug#992359: spdlog: Please package new upstream version (1.8.5)

[Michael R. Crusoe]

I did local testing of these packages and everything seems fine, so I've
uploaded spdlog 1:1.8.5+ds-1 to unstable. Thanks for the nudge!=

On Wed, Aug 18, 2021 at 4:48 PM Boyuan Yang  wrote:

> Hi,
>
> 在 2021-08-18星期三的 15:39 +0200，Michael R. Crusoe写道：
> > Thank you for your report.
> >
> > Have you tested the packages that use libspdlog-dev with 1.8.5 ?
> >
> > They are bear
> >
> > cherrytree
> > flameshot
> > hinge
> > intel-gmmlib
> > kodi
> > nheko
> > osmid
> > purify
> > rapmap
> > salmon
> > sopt
> > vast
> > waybar
>
> I haven't tested it since spdlog/1.8.5 is not in Debian yet. Could you
> please
> upload the new version into experimental so that we can test it, or could
> I do
> a spdlog/1.8.5 NMU into experimental?
>
> Thanks,
> Boyuan Yang
>
>
> > On Tue, Aug 17, 2021 at 8:39 PM Boyuan Yang  wrote:
> > > Source: spdlog
> > > Severity: normal
> > > Version: 1:1.8.1+ds-2.1
> > > X-Debbugs-CC: cru...@debian.org
> > >
> > > Dear Debian spdlog package maintainers,
> > >
> > > Current version of spdlog in Debian is 1.8.1, and a new version of
> 1.8.5
> > > is
> > > now available. One of my packages (flameshot) needs spdlog/1.8.5 in the
> > > new
> > > version. Could you please update spdlog to at least 1.8.5?
> > >
> > > I see that the git packaging repo in Salsa GitLab already has a 1.8.5
> > > version
> > > prepared. It would be great if it can be packaged in near future.
> Please
> > > let
> > > me know if I can provide with any help (such as package sponsorship).
> > >
> > > Thanks,
> > > Boyuan Yang
>
>
>

Bug#992400: fetchmail: segfault with specific .fetchmailrc

[Matthias Andree]

On Wed, 18 Aug 2021 19:20:01 +0200 Matthias Andree
 wrote:
> The attached patch should fix the crash. envelope is special in that it
> can take the value STRING_DISABLED == (char *)-1 for "no envelope", and
> the optmerge() function did not take this into account and tried to
> strdup(-1).

Minor detail, this happens in strlen(-1).

This is a regression that happened in 6.4.3 release (or 6.4.3-beta1, to
be precise) and affects all 6.4.x versions up to and including 6.4.21.

Bug#982813: Select All does not select all text any more

[Imre Jonk]

I've found this also affects the new Stable (Bullseye). One workaround
is to select the first line, then scroll all the way down, hold Shift
and click on the last line.

-- 
Imre Jonk
System Administrator

CipherMail email encryption
Email encryption with support for S/MIME,
OpenPGP, PDF encryption and Webmail Messenger.

W: https://www.ciphermail.com/
E: i...@ciphermail.com
T: +31 20 290 00 88


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

Bug#992400: fetchmail: segfault with specific .fetchmailrc

[Matthias Andree]

The attached patch should fix the crash. envelope is special in that it
can take the value STRING_DISABLED == (char *)-1 for "no envelope", and
the optmerge() function did not take this into account and tried to
strdup(-1).

This will likely become part of a future 6.4.22 and 6.5.0 release.


diff --git a/fetchmail.c b/fetchmail.c
index ac8e4607..71ecc1b0 100644
--- a/fetchmail.c
+++ b/fetchmail.c
@@ -996,7 +996,7 @@ static void optmerge(struct query *h2, struct query *h1, int force)
 list_merge(>antispam, >antispam, force);

 #define   FLAG_MERGE(fld) do { if (force ? !!h1->fld : !h2->fld) h2->fld = h1->fld; } while (0)
-#define STRING_MERGE(fld) do { if (force ? !!h1->fld : !h2->fld) { if (h2->fld) free((void *)h2->fld), h2->fld = 0; if (h1->fld) h2->fld = xstrdup(h1->fld); } } while (0)
+#define STRING_MERGE(fld) do { if (force ? !!h1->fld : !h2->fld) { if (h2->fld) free((void *)h2->fld), h2->fld = 0; if (h1->fld) { if (h1->fld != STRING_DISABLED) h2->fld = xstrdup(h1->fld); else h2->fld = STRING_DISABLED; } } } while (0)
 STRING_MERGE(server.via);
 FLAG_MERGE(server.protocol);
 STRING_MERGE(server.service);

Bug#992383: debianutils: which is noisy and doesn't suggest a different option

[Jason Riedy]

I've been using which for decades, including on SunOS and AIX. 
When I know it's a script, less `which foobar` is quick and easy.


None of the alternatives listed do the same thing.

Yes, which has issues, but you're breaking what people have used 
for a very, very long time.



From a bash session:
DEPRECATION
  Since type and command -v were mandated by POSIX, 
  this utility  is  no  longer
  useful for maintainer scripts and thus will be 
  removed from debianutils.


Debian   9 Jul 2021 
WHICH(1)

ejr@signbit:~/kernel/linux$ type ls
ls is aliased to `ls --color=auto --hyperlink=auto'
ejr@signbit:~/kernel/linux$ command -v ls
alias ls='ls --color=auto --hyperlink=auto'
ejr@signbit:~/kernel/linux$ which ls
/usr/bin/which: this version of 'which' is deprecated and should 
not be used.

/usr/bin/ls
ejr@signbit:~/kernel/linux$ whereis ls
ls: /usr/bin/ls /usr/share/man/man1/ls.1.gz
ejr@signbit:~/kernel/linux$ whence ls
bash: whence: command not found
ejr@signbit:~/kernel/linux$ command which ls
/usr/bin/which: this version of 'which' is deprecated and should 
not be used.

/usr/bin/ls
ejr@signbit:~/kernel/linux$ command -v which ls
/usr/bin/which
alias ls='ls --color=auto --hyperlink=auto'

Bug#992372: kst: Dirfile data sources (via libgetdata) are no longer recognized

[Graeme Smecher]

Update: this is a dependency-related bug in libgetdata, and a separate 
bug report has been filed here:


    https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992437

Depending on convention, please feel free to close this bug (it's not a 
KST bug) or leave it open until the dependency bug in libgetdata is 
resolved.


Thanks again for your time and effort.

Best,
Graeme

Bug#992347: open-iscsi on upgrades fail to finish postinst script

[Ritesh Raj Sarraf]

On Wed, 2021-08-18 at 19:35 +0530, Ritesh Raj Sarraf wrote:
> On Wed, 2021-08-18 at 13:32 +0100, Jose M Calhariz wrote:
> > I was expecting to be easy to collect the info in one or 2 files, but
> > I am wrong.  I have 3 targets with multipath for 2 of them and I am
> > not certain what is active.  I have multipath active, I am certain of
> > that, because of the device I am mouting:
> > /dev/mapper/mpath-X-part1
> > 
> > So I am expecting you need all files inside /etc/iscsi and some
> > run-time info?
> 
> I am asking this information just for the sake of this task, to
> ascertain why it failed in the first 30 seconds.
> 
> Since this worked for you, later, when you increased the timeout to 120
> seconds; there's not much to do I suppose. But yes, from this bug
> report's sake, having that information clarified will be good.

Given this bug report, I validated the upgrade on my local box. It is a
fairly complex configuration pulling in all bits: iSCSI, Multipath,
Root on Multipath (iSCSI) etc.

I can confirm that the upgrade went proper without any glitch. Relevant
snippets below:

Preparing to unpack .../20-libisns0_0.100-3_amd64.deb ...
Unpacking libisns0:amd64 (0.100-3) over (0.100-2) ...
Preparing to unpack .../21-libopeniscsiusr_2.1.3-5_amd64.deb ...
Unpacking libopeniscsiusr (2.1.3-5) over (2.1.2-1) ...
Preparing to unpack .../22-open-iscsi_2.1.3-5_amd64.deb ...
Unpacking open-iscsi (2.1.3-5) over (2.1.2-1) ...
Preparing to unpack .../23-pigz_2.6-1_amd64.deb ...
Unpacking pigz (2.6-1) over (2.4-1+b1) ...
Preparing to unpack .../24-popularity-contest_1.71_all.deb ...



Setting up vim-tiny (2:8.2.2434-3) ...
Setting up man-db (2.9.4-2) ...
Updating database of manual pages ...
man-db.service is a disabled or a static unit not running, not starting
it.
Setting up open-iscsi (2.1.3-5) ...
open-iscsi postinst: since the check in preinst some iSCSI sessions
have
 failed. -> will wait 30s for automatic recovery
Setting up usbutils (1:013-3) ...
Setting up fdisk (2.36.1-8) ...
Setting up grub-common (2.04-20) ...
Installing new version of config file /etc/grub.d/30_uefi-firmware ...


and

root@debian-sanboot:~# multipath -ll
sanroot (3600140561d8bb00b25143b38318ce2c0) dm-0 LIO-ORG,debsanboot
size=8.0G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| `- 2:0:0:0 sda 8:0  active ready running
|-+- policy='service-time 0' prio=50 status=enabled
| `- 3:0:0:0 sdb 8:16 active ready running
|-+- policy='service-time 0' prio=50 status=enabled
| `- 4:0:0:0 sdc 8:32 active ready running
`-+- policy='service-time 0' prio=50 status=enabled
  `- 5:0:0:0 sdd 8:48 active ready running

root@debian-sanboot:~# iscsiadm -m session
tcp: [1] 172.16.20.40:3260,1 iqn.2003-01.org.linux-iscsi.debian.sanboot
(non-flash)
tcp: [2] 172.16.20.41:3260,1 iqn.2003-01.org.linux-iscsi.debian.sanboot
(non-flash)
tcp: [3] 172.16.20.43:3260,1 iqn.2003-01.org.linux-iscsi.debian.sanboot
(non-flash)
tcp: [4] 172.16.20.42:3260,1 iqn.2003-01.org.linux-iscsi.debian.sanboot
(non-flash)


So from the information I have, my suspicion was correct. The oddity
must be in your setup. The defaults must have been overridden for a
good reason. There's also the possibility that your network may have a
glitch. It is not easy for me to guess.

And with limited volunteer time, there's only a subset of the default
settings/combinations I can test at my end.


I suggest this bug be done as I don't see any issue. But I'll let you
make that call.

-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System


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

Bug#992423: firewalld: drop iptables dependency

[Christian Göttsche]

Package: firewalld
Version: 1.0.1-1

Since upstream version 1.0.0 the iptables backend is deprecated.
Please drop (or reduce to recommends) the iptables dependency.

Bug#992444: make: Segmentation fault regression in make 4.3 vs. 4.2.1 (upstream bug 59093)

[Alex Thiessen]

Package: make
Version: 4.3-4.1
Severity: important
Tags: upstream
X-Debbugs-Cc: alex.thiessen.de+deb...@gmail.com

Dear Maintainer,

   * What led up to the situation?
 Using a "filter-out" function call in a makefile in context of
 buildroot.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 Building a rootfs using buildroot (by calling `make` after some
 specific setup).
   * What was the outcome of this action?
 Segmentation fault.
   * What outcome did you expect instead?
 Successful build.

The core dump (not attached) indicated that the whole stack space of 8MB
was consumed. Using current upstream master fixed this for me, locally.

The upstream bug is https://savannah.gnu.org/bugs/?59093, fix is already
merged to the upstream master.

-- System Information:
Debian Release: 11.0
  APT prefers stable-debug
  APT policy: (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 
'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-8-amd64 (SMP w/12 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 not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages make depends on:
ii  libc6  2.31-13

make recommends no packages.

Versions of packages make suggests:
pn  make-doc  

-- no debconf information

Bug#983910: rpcsvc-proto: uninstallable due to Conflicts: libc6

[Simon McVittie]

Control: found -1 1.4.2-3

Sorry, this is still failing, dependent on unpack order:

> Preparing to unpack .../rpcsvc-proto_1.4.2-3_amd64.deb ...
> Unpacking rpcsvc-proto (1.4.2-3) ...
> dpkg: error processing archive 
> /var/cache/apt/archives/rpcsvc-proto_1.4.2-3_amd64.deb (--unpack):
>  trying to overwrite '/usr/bin/rpcgen', which is also in package libc-dev-bin 
> 2.31-13

Doesn't the Breaks/Replaces need to be with versions (<< 2.31-14)
instead of (<< 2.31-13)? 2.31-13 is the version in bullseye, and 2.31-14
is the one with these changes:

>   * debian/rules.d/build.mk: stop passing --enable-obsolete-rpc.
>   * debian/debhelper.in/libc-dev.install{,.hurd-i386}: do not install
> librpcsvc.a.
>   * debian/debhelper.in/libc-dev-bin.manpage, debian/local/manpages/rpcgen.1:
> do not install rpcgen (1) manpage.
>   * debian/rules.d/build.mk: stop deleting  and
> .
>   * debian/control.in/libc, debian/rules.d/debhelper.mk: make libc6-dev to
> depend on rpcsvc-proto, except for stage1 and stage2.

smcv

Bug#991570: policykit-1-gnome: still depends on transitional package libgdk-pixbuf2.0-0

[Thomas Uhle]

Version: 0.105-7+b1

The binNMU has been built in connection with #981141. Thanks to Sebastian 
Ramacher!


Best regards,

Thomas Uhle

Bug#992443: Shouldn't depend on gvfs-backends

[Yuri D'Elia]

Package: siril
Version: 0.99.10.1-1
Severity: normal

In the latest package, siril depends on gvfs-backends, however I don't
see why this is the case.

Siril works fine without gvfs-backends installed.

-- System Information:
Debian Release: 11.0
  APT prefers unstable
  APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.13.0-trunk-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages siril depends on:
ii  libavcodec-extra58 [libavcodec58]  7:4.3.2-0+deb11u2
ii  libavformat58  7:4.3.2-0+deb11u2
ii  libavutil567:4.3.2-0+deb11u2
ii  libc6  2.31-16
ii  libcairo2  1.16.0-5
ii  libcfitsio93.490-3
ii  libconfig9 1.5-0.4
ii  libexiv2-270.27.3-3
ii  libffms2-4 2.23-5
ii  libfftw3-single3   3.3.8-2
ii  libgcc-s1  11.2.0-2
ii  libgdk-pixbuf-2.0-02.42.6+dfsg-2
ii  libglib2.0-0   2.68.3-2
ii  libgomp1   11.2.0-2
ii  libgsl25   2.7+dfsg-2
ii  libgtk-3-0 3.24.30-1
ii  libheif1   1.11.0-1
ii  libjpeg62-turbo1:2.0.6-4
ii  libjson-glib-1.0-0 1.6.2-1
ii  libopencv-calib3d4.5   4.5.1+dfsg-5
ii  libopencv-core4.5  4.5.1+dfsg-5
ii  libopencv-imgproc4.5   4.5.1+dfsg-5
ii  libpango-1.0-0 1.46.2-3
ii  libpangocairo-1.0-01.46.2-3
ii  libpng16-161.6.37-3
ii  libraw20   0.20.2-1
ii  librsvg2-2 2.50.3+dfsg-1
ii  libstdc++6 11.2.0-2
ii  libswresample3 7:4.3.2-0+deb11u2
ii  libswscale57:4.3.2-0+deb11u2
ii  libtiff5   4.2.0-1
ii  libwcs77.4+ds-2
ii  siril-common   0.99.10.1-1

siril recommends no packages.

Versions of packages siril suggests:
ii  gnuplot   5.4.1+dfsg1-1
ii  gnuplot-qt [gnuplot]  5.4.1+dfsg1-1

Bug#992442: bzip2: Use tempfile in /usr/bin/bzexe, which is no longer available

[Boyuan Yang]

Package: bzip2
Severity: grave
Version: 1.0.8-4
Control: tags -1 sid
X-Debbugs-CC: santi...@debian.org santi...@debian.org

Dear Debian bzip2 package maintainers,

As discussed in https://bugs.debian.org/992396 , the tempfile command has been
removed from debianutils package. However, it looks like the bzexe command
provided by Debian still uses it:

https://sources.debian.org/src/bzip2/1.0.8-4/debian/bzexe/#L123


set -C
umask=`umask`
umask 77
tmpfile=`tempfile -p gztmp -d /tmp` || exit 1


Please consider switching to mktemp(1) provided by GNU coreutils.

Thanks,
Boyuan Yang


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

Bug#992347: open-iscsi on upgrades fail to finish postinst script

[Jose M Calhariz]

On Wed, Aug 18, 2021 at 12:54:13PM +0100, Jose M Calhariz wrote:
> On Wed, Aug 18, 2021 at 01:57:35PM +0530, Ritesh Raj Sarraf wrote:
> > On Tue, 2021-08-17 at 19:02 +0100, Jose M Calhariz wrote:
> > > > Did you change/tweak any of the default timeout values ?
> > > > 
> > > 
> > > Most probably, it is not me that usually setup the iSCSI connections.
> > > What values do you want me to look into it and where?
> > 
> > All information should be available under `/etc/iscsi`.
> > There will be per target database created under that folder. And those
> > will have all the finer session and replacement timeouts defined. They
> > are usually generated/updated through the `iscsiadm` utility during
> > discovery.
> > 
> > PS: That db may also include CHAP secrets, if you set any.
> > 
> 
> OK,
> 
> I will send to you the iSCSI setup without secrets and we will put in
> the bug report the relevant info.
> 
> Kind regards
> Jose M Calhariz
> 
> 

Hi,

I was expecting to be easy to collect the info in one or 2 files, but
I am wrong.  I have 3 targets with multipath for 2 of them and I am
not certain what is active.  I have multipath active, I am certain of
that, because of the device I am mouting:
/dev/mapper/mpath-X-part1

So I am expecting you need all files inside /etc/iscsi and some
run-time info?

Kind regards
Jose M Calhariz

-- 
--
É difícil dizer o que e impossivel, pois a fantasia de
ontem e a esperanca de hoje e a realidade de
amanha.
-- Robert H. Goddard


signature.asc
Description: PGP signature

Bug#992410: closed by Debian FTP Masters (reply to Clint Adams ) (Bug#992396: fixed in debianutils 5.0.1-2)

[Felix Zielcke]

Control: unmerge -1
Control: reopen -1

> Changes:
> debianutils (5.0.1-2) unstable; urgency=medium
> .
>   * Redirect stderr from which in smoke test
>   * Add Breaks on x11-common still using `tempfile`.
> closes: #992396.

Sorry but my bug has with run-parts to do and nothing with tempfile in
x11-common.

Am Mittwoch, dem 18.08.2021 um 15:51 + schrieb Debian Bug Tracking
System:
> This is an automatic notification regarding your Bug report
> which was filed against the debianutils package:
> 
> #992410: move of /bin/run-parts to /usr/bin breaks network with ifup
> 
> It has been closed by Debian FTP Masters
>  (reply to Clint Adams
> ).
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Debian FTP
> Masters  (reply to Clint Adams
> ) by
> replying to this email.
> 
> 

Bug#800598: Please switch from --with-polkit=strict to --with-polkit=permissive

[Henry-Nicolas Tourneur]

X-Debbugs-CC: deba...@debian.org

Le mercredi 18 août 2021 à 10:50 +0200, Henry-Nicolas Tourneur a
écrit :
> Hello Laurent,
> 
> Regarding this bug, could you please kindly let us know what's the
> proper way forward you would be ok to support? I would be willing to
> help get there if needed.
> 
> 
Looking further into modemmanager, I see that the maintainer (Mathieu
Trudel-Lapierre) seems to be MIA. Last non-maintainer upload is from 
~3 years ago (Oct 2018).

Adding Martin in the loop since he did quite a bit of the recent non-
maintainer uploads.

I am not sure what is the best course of action regarding this bug.

Regards,

Henry-Nicolas Tourneur



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

Bug#992399: debianutils: removes interface from essential package without proper transition

[Michael Stone]

On Wed, Aug 18, 2021 at 03:25:22PM +, Clint Adams wrote:

On Wed, Aug 18, 2021 at 11:22:53AM -0400, Michael Stone wrote:

apologies, box I checked was buster and not bullseye


No problem, it seems evident that it did little good anyway.


well, the note is for users, most of whom aren't running bullseye yet. I 
obviously haven't upgraded all of mine, myself. :-D

Bug#972509: deborphaner is now broken

[Nelson A. de Oliveira]

severity 972509 important
thanks

Hi!

deborphan is now broken, since "tempfile" was removed from debianutils:
https://packages.qa.debian.org/d/debianutils/news/20210817T214836Z.html

=
# orphaner
/usr/bin/which: this version of 'which' is deprecated and should not be used.
/usr/bin/which: this version of 'which' is deprecated and should not be used.
/usr/sbin/orphaner: 1: tempfile: not found
=

Best regards,
Nelson

Bug#992347: open-iscsi on upgrades fail to finish postinst script

[Jose M Calhariz]

On Wed, Aug 18, 2021 at 01:57:35PM +0530, Ritesh Raj Sarraf wrote:
> On Tue, 2021-08-17 at 19:02 +0100, Jose M Calhariz wrote:
> > > Did you change/tweak any of the default timeout values ?
> > > 
> > 
> > Most probably, it is not me that usually setup the iSCSI connections.
> > What values do you want me to look into it and where?
> 
> All information should be available under `/etc/iscsi`.
> There will be per target database created under that folder. And those
> will have all the finer session and replacement timeouts defined. They
> are usually generated/updated through the `iscsiadm` utility during
> discovery.
> 
> PS: That db may also include CHAP secrets, if you set any.
> 

OK,

I will send to you the iSCSI setup without secrets and we will put in
the bug report the relevant info.

Kind regards
Jose M Calhariz


-- 
--
É difícil dizer o que e impossivel, pois a fantasia de
ontem e a esperanca de hoje e a realidade de
amanha.
-- Robert H. Goddard


signature.asc
Description: PGP signature

Bug#992440: RFP: WhiteSur-gtk-theme

[Wellington Almeida]

Package: wnpp
Version: N/A
Severity: wishlist

URL: https://github.com/vinceliuice/WhiteSur-gtk-theme

License : MIT

Description: Desktop Theme

WhiteSur-gtk-theme is a very elegant GTK theme that I would very much
like to see packaged and available in the repositories.

GitHub: https://github.com/vinceliuice/WhiteSur-gtk-theme


-- 
Wellington Almeida
Rio de Janeiro - Brasil

Bug#992439: libconfig-model-dpkg-perl: blocks fails autopkgtest with recent licensecheck

[Jonas Smedegaard]

Package: libconfig-model-dpkg-perl
Version: 2.143
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Licensecheck seemingly gets blocked from entering stable currently, due
to libconfig-model-dpkg-perl 2.143 fialing its autopkgtest:

not ok 14 - check scikit-learn copyright

#   Failed test 'check scikit-learn copyright'
#   at t/scanner/scan-copyright.t line 27.
# --- t/scanner/examples/scikit-learn.out   Mon Jan 25 17:34:01 2021
# +++ /tmp/9pPbiX1AYv   Tue Aug 17 04:10:11 2021
# @@ -2,3 +2,7 @@
#  Copyright: 2007-2019, The scikit-learn developers.
#  License: BSD-3-clause
#  
# +Files: sklearn/*
# +Copyright: no-info-found
# +License: BSD-3-clause
# +

I don't understand exactly what that test does, but seems licensecheck
identified the license for one of the files in the example directory:

$ licensecheck --lines 0 --deb-fmt --recursive t/scanner/examples/scikit-learn.d
t/scanner/examples/scikit-learn.d/COPYING: BSD-3-clause
t/scanner/examples/scikit-learn.d/doc/README.md: *No copyright* UNKNOWN
t/scanner/examples/scikit-learn.d/sklearn/base.py: *No copyright* UNKNOWN
t/scanner/examples/scikit-learn.d/doc/images/inria-small.png: UNKNOWN
t/scanner/examples/scikit-learn.d/sklearn/datasets/images/flower.jpg: UNKNOWN
t/scanner/examples/scikit-learn.d/sklearn/datasets/images/scikit-learn-logo.bmp:
 UNKNOWN
t/scanner/examples/scikit-learn.d/sklearn/datasets/images/sydney-primary.jpeg: 
UNKNOWN


If this is believed to be a bug in licensecheck, then please provide a
shell command to reproduce the issue, and reassign this bugreport to
licensecheck.


Kind regards,

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmEdKgsACgkQLHwxRsGg
ASFqtA//Wm1GrIACTRQvDNj6ZR0kSkF+9+hHg6l++VGqUWttP+A2bCQxAHCOTSJ8
h59KkCMATuz8BrbGBHB/Jv7M3zbAOGTIrGYt+AKPBw63kxbtSk/8P6yvpalvX2Zc
TTw7tBZ7kNxdN8un4SXU6kzbSCx2E8bwDSqd3dYMm0VtBkdF+6hguND9Tu920mVh
H2VMf70X0XVRn7uulBol4lFPpNLMSddFdohhIoH4cz4F4ZxX6aGGWC9AO38CDFAj
k3RQDNcAkv/pPokk/5cHPqRKVWIwObC9fOhAA/1CCCSXQVmLcRLKNf2ZNIzikt++
82kXJD6xZhCvRem5/zxh7FlnQiqvgk/7bNrayudxfybh9Q3qFQWXNx3kD/DG0/ti
c3MKauBlTT+F04NmdpaN8bxaAI7mupl262jG1bBOMmpw2DwnvSivHfqPwBjK4SCC
cuoksqtn8coo53wL4f9wmB3StEMs/r2P/J0u17xMPXnDCKCf1ZqUKoVHR88yxkc2
FPXRTrN3YpSsh8SGE/Yw6f6O8ln0VKIKGdrliLufG4W5lhlakwJkvfWsIJCf1ibk
hCSZnfVYuKfB4VovbpnSVEpPhaG34NIGrRzJ4az3yMdutda/j59/jAAC7Kyj7wi7
XbVE8p2D9q3RBse+f93eaTCDcWShZ5tNkz74MZXlAvmynBy3Aic=
=F+YP
-END PGP SIGNATURE-

Bug#992438: gmailieer FTBFS: help2man: can't get `--help' info from gmi

[Adrian Bunk]

Source: gmailieer
Version: 1.3-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=gmailieer=all

...
help2man --no-info --version-string=1.3-2 \
 --name="Fast fetch and two-way tag synchronization between notmuch and GMail" \
 --include=debian/gmi-man-include \
 --output=debian/gmi.1 gmi
help2man: can't get `--help' info from gmi
Try `--no-discard-stderr' if option outputs to stderr
make[1]: *** [debian/rules:11: debian/gmi.1] Error 127

Bug#992396: debianutils: tempfile binary is gone, breaks Xsession

[Andre Heider]

I guess more transitions are required, just by grep'ing in my local /usr 
I see these:


/usr/bin/vimtutor:TUTORCOPY=`mktemp $tmp/tutorXX || tempfile -p 
tutor || echo none`

/usr/bin/bzexe:tmpfile=`tempfile -p gztmp -d /tmp` || exit 1
/usr/bin/mupdf:tmp=$(tempfile -s .pdf)
/usr/sbin/install-keymap:TMP=`tempfile`
/usr/sbin/install-keymap:NEW=`tempfile --suffix .gz`

Bug#985638: kdenlive: speed effect from right click does not change video speed

[Patrick Matthäi]

Hi

Am 21.03.21 um 07:41 schrieb will:

Package: kdenlive
Version: 20.12.3-1
Severity: normal
X-Debbugs-Cc: wiiliamchung...@gmail.com

Dear Maintainer,

Changing the video speed in the timeline via right click menu does not change
the video speed, despite changing the corresponding time length. Playing back
the "slowed" or "sped up" video will only display the default video speed, but
cropped.

This happens on both 20.12.2-1, and 20.12.3-1

Could you please retest this with version 21.04.3-3 from unstable and 
21.08.0-1 from experimental and give a feedback?


Thanks



OpenPGP_0x12D9B04A90CBD8E4.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#992399: debianutils: removes interface from essential package without proper transition

[Michael Stone]

On Wed, Aug 18, 2021 at 03:06:07PM +, Clint Adams wrote:

On Wed, Aug 18, 2021 at 10:53:45AM -0400, Michael Stone wrote:

Adding a message to stderr telling people to use mktemp may be a reasonable
step.


You mean the thing it does in our stable release?


apologies, box I checked was buster and not bullseye

Bug#992399: debianutils: removes interface from essential package without proper transition

[Clint Adams]

On Wed, Aug 18, 2021 at 11:22:53AM -0400, Michael Stone wrote:
> apologies, box I checked was buster and not bullseye

No problem, it seems evident that it did little good anyway.

Bug#992396: debianutils: tempfile binary is gone, breaks Xsession

[Andre Heider]

On Wed, 18 Aug 2021 23:19:17 +1200 Jean-Francois Pirus 
 wrote:

Duplicate of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992385


No, not really.

This removes a tool which is still in use. I get the desire to remove 
deprecated stuff, but the user friendly way is to communicate the 
removal of the usage to packages using said tool first, and only then 
removing the tool itself.


Isn't that what transitions are used for?

This change broke X for everyone on testing, that's not a very nice way 
forward.


As a user I've never seen the deprecated output anywhere. It probably 
never for printed anywhere for Xsession?

Bug#992410: move of /bin/run-parts to /usr/bin breaks network with ifup

[Clint Adams]

On Wed, Aug 18, 2021 at 10:33:17AM +0200, fziel...@z-51.de wrote:
> After todays updates and a reboot my network didn't come up anymore.
> Problem is the move of /bin/run-parts to /usr/bin:
> 
> systemd[1]: Starting Raise network interfaces...
> ifup[1663]: /bin/sh: 1: /bin/run-parts: not found
> ifup[1661]: ifup: pre-up script failed
> systemd[1]: networking.service: Main process exited, code=exited, 
> status=1/FAILURE
> systemd[1]: networking.service: Failed with result 'exit-code'.
> systemd[1]: Failed to start Raise network interfaces.

Also see #992425

Bug#992437: libgetdata8: Patch for CVE-2021-20204 breaks many regression tests

[Graeme Smecher]

Package: libgetdata8
Version: 0.10.0-10
Severity: important

Dear Maintainer,

The current patch [1] for CVE-2021-20204 [2] breaks many (602 of 1638)
regression tests (via "make check") and impacts basic library function.
Downstream software is impacted (hence, Debian bug #992372 on KST.)

For example: any dirfile with LINCOM fails to be recognized as a dirfile.

Upstream has been notified of the CVE and will hopefully respond with their own
patch.

thanks,
Graeme

[1]: https://salsa.debian.org/science-
team/libgetdata/-/commit/61275e4c051090ce11467207eb361a6d81c405d9
[2]: https://nvd.nist.gov/vuln/detail/CVE-2021-20204



-- System Information:
Debian Release: 11.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages libgetdata8 depends on:
ii  libc6 2.31-11
ii  libltdl7  2.4.6-15

libgetdata8 recommends no packages.

libgetdata8 suggests no packages.

-- no debconf information

Bug#992436: myproxy FTBFS on IPV6-only buildds

[Adrian Bunk]

Source: myproxy
Version: 6.2.8-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=myproxy=amd64=6.2.8-1=1629290865=0

...
Bootstrapping MyProxy server root of trust.
Creating directory /tmp/OvpeL_vrlB/.globus/certificates.test.8637.10196
Attempting to connect to ::1:45721
Attempting to connect to 127.0.0.1:45721
Successfully connected to localhost:45721
trust root bootstrap failed
Unable to connect to ::1:45721 error:0200206F:system library:connect:Connection 
refused error:2008A067:BIO routines:BIO_connect:connect error 
error:0200206F:system library:connect:Connection refused hostname=localhost 
service=45721 error:20073067:BIO routines:conn_state:connect error 
error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Connection refused
Unable to connect to ::1:45721 error:0200206F:system library:connect:Connection 
refused error:2008A067:BIO routines:BIO_connect:connect error 
error:0200206F:system library:connect:Connection refused hostname=localhost 
service=45721 error:20073067:BIO routines:conn_state:connect error 
error:140E0197:SSL routines:SSL_shutdown:shutdown while in init Connection 
refused
MyProxy Test 41 (retrieve trustroots w/o authentication): FAILED
...