Bug#1038622: RM: itksnap -- RoQA; Blocks removal of vtk6

[Bas Couwenberg]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: itks...@packages.debian.org
Control: affects -1 + src:itksnap

Please remove itksnap from the archive to unblock the removal of vtk6.

itksnap can be reintroduced once its updated to 4.0 which claims to support 
vtk9.

Kind Regards,

Bas

Bug#1038621: Please ACTUALLY remove the Depends: binutils

[Trent W. Buck]

Package: needrestart
Version: 3.6-4
Severity: minor

I upgraded to Debian 12, hoping this stupid error would finally go away:

bash5$ check-support-status
Limited security support for one or more packages

Unfortunately, it has been necessary to limit security support for some
packages.

The following packages found on this system are affected by this:

* Source:binutils
  Details: Only suitable for trusted content; see 
https://lists.debian.org/msgid-search/87lfqsomtg@mid.deneb.enyo.de
  Affected binary packages:
  - binutils (installed version: 2.40-2)
  - binutils-common:amd64 (installed version: 2.40-2)
  - binutils-x86-64-linux-gnu (installed version: 2.40-2)
  - libbinutils:amd64 (installed version: 2.40-2)
  - libctf-nobfd0:amd64 (installed version: 2.40-2)
  - libctf0:amd64 (installed version: 2.40-2)
  - libgprofng0:amd64 (installed version: 2.40-2)

Because I knew this had happened some time ago:


https://github.com/liske/needrestart/commit/e6176258e6b9f9f907736cbe1f8d148582a057d9
https://sources.debian.org/src/needrestart/3.6-4/debian/changelog/#L39-L40
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986507

However, the binutils dependency was not actually removed!

https://sources.debian.org/src/needrestart/3.6-4/debian/control/#L24

Can you please fix this (remove "Depends: binutils")?
I can't find the git repo with the debian/ tree in it (there's no VCS-Git in 
debian/control).
So I'm not 100% sure if this was intentional (needrestart needs binutils for 
something else), or simply an oversight.


-- Package-specific info:
needrestart output:

checkrestart output:


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

Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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 needrestart depends on:
ii  binutils   2.40-2
ii  dpkg   1.21.22
ii  gettext-base   0.21-12
ii  libintl-perl   1.33-1
ii  libmodule-find-perl0.16-2
ii  libmodule-scandeps-perl1.31-2
ii  libproc-processtable-perl  0.634-1+b2
ii  libsort-naturally-perl 1.03-4
ii  libterm-readkey-perl   2.38-2+b1
ii  perl   5.36.0-7
ii  xz-utils   5.4.1-0.2

Versions of packages needrestart recommends:
ii  libpam-systemd  252.6-1
ii  systemd 252.6-1

Versions of packages needrestart suggests:
ii  iucode-tool  2.3.1-3
ii  needrestart-session  0.3-11

-- no debconf information

Bug#1038614: vtk9: Stop using netcdf-cxx-legacy

[Sebastiaan Couwenberg]

Control: tags -1 pending

This is fixed in the experimental branch:


https://salsa.debian.org/science-team/vtk9/-/commit/b4d5c6bf1de79c3ef0e75cd94d176f0c2fbc99f4

Anton, please pull the changes to ensure they're included when you move 
the package from experimental to unstable.


Kind Regards,

Bas

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

Bug#1038620: ITP: x2gokdriveclient -- KDrive graphical client backend for X2Go Client

[Mike Gabriel]

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

* Package name: x2gokdriveclient
  Version : 0.0.0.1
  Upstream Contact: Oleksandr Shneyder 
* URL : 
https://code.x2go.org/gitweb?p=x2gokdriveclient.git;a=summary
* License : GPL-3+
  Programming Lang: C++
  Description : KDrive graphical client backend for X2Go Client

 X2Go is a server based computing environment with
- session resuming
- low bandwidth support
- session brokerage support
- client-side mass storage mounting support
- client-side printing support
- audio support
- authentication by smartcard and USB stick
 .
 X2Go KDrive Client is the KDrive graphical backend for X2Go Client that
 provides support for running modern desktop environments like GNOME, KDE
 Plasma, Cinnamon, etc. in X2Go Sessions.
 .
 The X2Go KDrive graphical backend is not suitable for low bandwidth WAN
 connections between X2Go Client and X2Go Server. It is supposed for X2Go
 being used on the local area network or on highbandwidth WAN
 connections.
 .
 This package will be maintained under the umbrella of the Debian Remote
 Package Team.

Bug#994685: [INTL:sv] Swedish strings for colplot debconf

[Paulo Henrique de Lima Santana]

Hi,

I uploaded a NMU to 10-day/delay queue. Feel free to cancel this
upload if needed.

The debian/changelog is:

colplot (5.2.0-1.2) unstable; urgency=medium

  * Non-maintainer upload.
  * Update Brazilian Portuguese translation. (Closes: #1025725)
  * Update Swedish translation. (Closes: #994685
  * debian/compat: deleted.
  * debian/copyright: update the copyright of the translators.
  * debian/control
  - Bump Standards-Version 4.6.2.
  - Change from Build-Depends to Build-Depends.
  - New format to debhelper-compat and updated level to 13.

I attached a debdiff.

Thanks.

Regards,


--
Paulo Henrique de Lima Santana (phls)
Belo Horizonte - Brasil
Debian Developer
Site: http://phls.com.br
GPG ID: 0443C450
diff -u colplot-5.2.0/debian/changelog colplot-5.2.0/debian/changelog
--- colplot-5.2.0/debian/changelog
+++ colplot-5.2.0/debian/changelog
@@ -1,5 +1,20 @@
+colplot (5.2.0-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Update Brazilian Portuguese translation. (Closes: #1025725)
+  * Update Swedish translation. (Closes: #994685 
+  * debian/compat: deleted.
+  * debian/copyright: update the copyright of the translators.
+  * debian/control
+  - Bump Standards-Version 4.6.2.
+  - Change from Build-Depends to Build-Depends.
+  - New format to debhelper-compat and updated level to 13.
+
+ -- Paulo Henrique de Lima Santana (phls)   Mon, 19 Jun 2023 
01:40:28 -0300
+
 colplot (5.2.0-1.1) unstable; urgency=medium
 
+  * Non-maintainer upload.
   * Non maintainer upload by the Reproducible Builds team.
   * No source change upload to rebuild on buildd with .buildinfo files.
 
reverted:
--- colplot-5.2.0/debian/compat
+++ colplot-5.2.0.orig/debian/compat
@@ -1 +0,0 @@
-9
diff -u colplot-5.2.0/debian/control colplot-5.2.0/debian/control
--- colplot-5.2.0/debian/control
+++ colplot-5.2.0/debian/control
@@ -2,8 +2,8 @@
 Section: admin
 Priority: optional
 Maintainer: Troy Heber 
-Build-Depends-Indep: debhelper (>= 9), quilt (>= 0.40), po-debconf
-Standards-Version: 4.2.1.1
+Build-Depends: debhelper-compat (= 13), quilt (>= 0.40), po-debconf
+Standards-Version: 4.6.2
 
 Package: colplot
 Architecture: all
diff -u colplot-5.2.0/debian/copyright colplot-5.2.0/debian/copyright
--- colplot-5.2.0/debian/copyright
+++ colplot-5.2.0/debian/copyright
@@ -16,6 +16,7 @@
 
 Files: debian/*
 Copyright: 2012 Troy Heber 
+   2023 Paulo Henrique de Lima Santana 
 License: GPL-2
 
 Files: debian/po/cs.po
@@ -73,6 +74,7 @@
 
 Files: debian/po/pt_BR.po
 Copyright: 2005 André Luís Lopes 
+   2022 Paulo Henrique de Lima Santana 
 License: GPL-2
 
 Files: debian/po/pt.po
@@ -86,7 +88,7 @@
 
 Files: debian/po/sv.po
 Copyright: 2005 Daniel Nylander 
-   2011-2012 Martin Bagge ,
+   2011-2021 Martin Bagge ,
 License: GPL-2
 
 Files: debian/po/vi.po
diff -u colplot-5.2.0/debian/po/pt_BR.po colplot-5.2.0/debian/po/pt_BR.po
--- colplot-5.2.0/debian/po/pt_BR.po
+++ colplot-5.2.0/debian/po/pt_BR.po
@@ -10,45 +10,47 @@
 # or http://www.debian.org/intl/l10n/po-debconf/README-trans
 #
 #Developers do not need to manually edit POT or PO files.
+# Paulo Henrique de Lima Santana (phls) , 2022.
 #
 msgid ""
 msgstr ""
-"Project-Id-Version: colplot\n"
+"Project-Id-Version: colplot_5.2.0-1.1\n"
 "Report-Msgid-Bugs-To: colp...@packages.debian.org\n"
 "POT-Creation-Date: 2016-02-11 11:28-0700\n"
-"PO-Revision-Date: 2005-03-25 21:33-0300\n"
-"Last-Translator: André Luís Lopes \n"
-"Language-Team: Debian-BR Project\n"
-"Language: \n"
+"PO-Revision-Date: 2022-11-28 23:31-0300\n"
+"Last-Translator: Paulo Henrique de Lima Santana (phls) \n"
+"Language-Team: Brazilian Portuguese \n"
+"Language: pt_BR\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n > 1)\n"
+"X-Generator: Gtranslator 42.0\n"
 
 #. Type: select
 #. Choices
 #: ../colplot.templates:2001
 msgid "apache2"
-msgstr ""
+msgstr "apache2"
 
 #. Type: select
 #. Choices
 #: ../colplot.templates:2001
 msgid "lighttpd"
-msgstr ""
+msgstr "lighttpd"
 
 #. Type: select
 #. Choices
 #: ../colplot.templates:2001
 msgid "None"
-msgstr ""
+msgstr "Nenhum"
 
 #. Type: select
 #. Description
 #: ../colplot.templates:2002
-#, fuzzy
-#| msgid "Webserver type"
 msgid "Web server:"
-msgstr "Tipo do servidor Web"
+msgstr "Servidor web:"
 
 #. Type: select
 #. Description
@@ -59,12 +61,11 @@
 msgstr ""
+"Por favor, selecione o servidor web para o qual o Colplot deve ser "
+"configurado automaticamente."
 
 #. Type: select
 #. Description
 #: ../colplot.templates:2002
-#, fuzzy
-#| msgid ""
-#| "Select \"None\" if you would like to configure your webserver by hand."
 msgid "Select \"None\" if you would like to configure the web server manually."
 msgstr ""
-"Selecione \"Nenhum\" caso você queira configurar seu servidor Web "
+"Selecione \"Nenhum\" caso você queira configurar seu servidor web "
 "manualmente."
diff -u 

Bug#1025725: colplot: [INTL:pt_BR] Brazilian Portuguese debconf templates translation

[Paulo Henrique de Lima Santana]

Hi,

I uploaded a NMU to 10-day/delay queue. Feel free to cancel this
upload if needed.

The debian/changelog is:

colplot (5.2.0-1.2) unstable; urgency=medium

  * Non-maintainer upload.
  * Update Brazilian Portuguese translation. (Closes: #1025725)
  * Update Swedish translation. (Closes: #994685
  * debian/compat: deleted.
  * debian/copyright: update the copyright of the translators.
  * debian/control
  - Bump Standards-Version 4.6.2.
  - Change from Build-Depends to Build-Depends.
  - New format to debhelper-compat and updated level to 13.

I attached a debdiff.

Thanks.

Regards,

--
Paulo Henrique de Lima Santana (phls)
Belo Horizonte - Brasil
Debian Developer
Site: http://phls.com.br
GPG ID: 0443C450
diff -u colplot-5.2.0/debian/changelog colplot-5.2.0/debian/changelog
--- colplot-5.2.0/debian/changelog
+++ colplot-5.2.0/debian/changelog
@@ -1,5 +1,20 @@
+colplot (5.2.0-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Update Brazilian Portuguese translation. (Closes: #1025725)
+  * Update Swedish translation. (Closes: #994685 
+  * debian/compat: deleted.
+  * debian/copyright: update the copyright of the translators.
+  * debian/control
+  - Bump Standards-Version 4.6.2.
+  - Change from Build-Depends to Build-Depends.
+  - New format to debhelper-compat and updated level to 13.
+
+ -- Paulo Henrique de Lima Santana (phls)   Mon, 19 Jun 2023 
01:40:28 -0300
+
 colplot (5.2.0-1.1) unstable; urgency=medium
 
+  * Non-maintainer upload.
   * Non maintainer upload by the Reproducible Builds team.
   * No source change upload to rebuild on buildd with .buildinfo files.
 
reverted:
--- colplot-5.2.0/debian/compat
+++ colplot-5.2.0.orig/debian/compat
@@ -1 +0,0 @@
-9
diff -u colplot-5.2.0/debian/control colplot-5.2.0/debian/control
--- colplot-5.2.0/debian/control
+++ colplot-5.2.0/debian/control
@@ -2,8 +2,8 @@
 Section: admin
 Priority: optional
 Maintainer: Troy Heber 
-Build-Depends-Indep: debhelper (>= 9), quilt (>= 0.40), po-debconf
-Standards-Version: 4.2.1.1
+Build-Depends: debhelper-compat (= 13), quilt (>= 0.40), po-debconf
+Standards-Version: 4.6.2
 
 Package: colplot
 Architecture: all
diff -u colplot-5.2.0/debian/copyright colplot-5.2.0/debian/copyright
--- colplot-5.2.0/debian/copyright
+++ colplot-5.2.0/debian/copyright
@@ -16,6 +16,7 @@
 
 Files: debian/*
 Copyright: 2012 Troy Heber 
+   2023 Paulo Henrique de Lima Santana 
 License: GPL-2
 
 Files: debian/po/cs.po
@@ -73,6 +74,7 @@
 
 Files: debian/po/pt_BR.po
 Copyright: 2005 André Luís Lopes 
+   2022 Paulo Henrique de Lima Santana 
 License: GPL-2
 
 Files: debian/po/pt.po
@@ -86,7 +88,7 @@
 
 Files: debian/po/sv.po
 Copyright: 2005 Daniel Nylander 
-   2011-2012 Martin Bagge ,
+   2011-2021 Martin Bagge ,
 License: GPL-2
 
 Files: debian/po/vi.po
diff -u colplot-5.2.0/debian/po/pt_BR.po colplot-5.2.0/debian/po/pt_BR.po
--- colplot-5.2.0/debian/po/pt_BR.po
+++ colplot-5.2.0/debian/po/pt_BR.po
@@ -10,45 +10,47 @@
 # or http://www.debian.org/intl/l10n/po-debconf/README-trans
 #
 #Developers do not need to manually edit POT or PO files.
+# Paulo Henrique de Lima Santana (phls) , 2022.
 #
 msgid ""
 msgstr ""
-"Project-Id-Version: colplot\n"
+"Project-Id-Version: colplot_5.2.0-1.1\n"
 "Report-Msgid-Bugs-To: colp...@packages.debian.org\n"
 "POT-Creation-Date: 2016-02-11 11:28-0700\n"
-"PO-Revision-Date: 2005-03-25 21:33-0300\n"
-"Last-Translator: André Luís Lopes \n"
-"Language-Team: Debian-BR Project\n"
-"Language: \n"
+"PO-Revision-Date: 2022-11-28 23:31-0300\n"
+"Last-Translator: Paulo Henrique de Lima Santana (phls) \n"
+"Language-Team: Brazilian Portuguese \n"
+"Language: pt_BR\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n > 1)\n"
+"X-Generator: Gtranslator 42.0\n"
 
 #. Type: select
 #. Choices
 #: ../colplot.templates:2001
 msgid "apache2"
-msgstr ""
+msgstr "apache2"
 
 #. Type: select
 #. Choices
 #: ../colplot.templates:2001
 msgid "lighttpd"
-msgstr ""
+msgstr "lighttpd"
 
 #. Type: select
 #. Choices
 #: ../colplot.templates:2001
 msgid "None"
-msgstr ""
+msgstr "Nenhum"
 
 #. Type: select
 #. Description
 #: ../colplot.templates:2002
-#, fuzzy
-#| msgid "Webserver type"
 msgid "Web server:"
-msgstr "Tipo do servidor Web"
+msgstr "Servidor web:"
 
 #. Type: select
 #. Description
@@ -59,12 +61,11 @@
 msgstr ""
+"Por favor, selecione o servidor web para o qual o Colplot deve ser "
+"configurado automaticamente."
 
 #. Type: select
 #. Description
 #: ../colplot.templates:2002
-#, fuzzy
-#| msgid ""
-#| "Select \"None\" if you would like to configure your webserver by hand."
 msgid "Select \"None\" if you would like to configure the web server manually."
 msgstr ""
-"Selecione \"Nenhum\" caso você queira configurar seu servidor Web "
+"Selecione \"Nenhum\" caso você queira configurar seu servidor web "
 "manualmente."
diff -u 

Bug#1038619: vtk7: Stop using netcdf-cxx-legacy

[Bas Couwenberg]

Source: vtk7
Version: 7.1.1+dfsg2-10.2
Severity: important
Tags: patch
User: debian-...@lists.debian.org
Usertags: netcdf-cxx-legacy-rm

Dear Maintainer,

Your package uses netcdf-cxx-legacy which is dead upstream and will be removed 
during the trixie development cycle.

The attached patch switches to the embedded copy, because the build actually 
requires the CXX component.

Kind Regards,

Bas
diff -Nru vtk7-7.1.1+dfsg2/debian/changelog vtk7-7.1.1+dfsg2/debian/changelog
--- vtk7-7.1.1+dfsg2/debian/changelog   2022-08-03 21:41:56.0 +0200
+++ vtk7-7.1.1+dfsg2/debian/changelog   2023-06-18 19:53:15.0 +0200
@@ -1,3 +1,10 @@
+vtk7 (7.1.1+dfsg2-10.3) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Don't use netcdf-cxx-legacy.
+
+ -- Bas Couwenberg   Sun, 18 Jun 2023 19:53:15 +0200
+
 vtk7 (7.1.1+dfsg2-10.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru vtk7-7.1.1+dfsg2/debian/control vtk7-7.1.1+dfsg2/debian/control
--- vtk7-7.1.1+dfsg2/debian/control 2022-08-03 19:39:40.0 +0200
+++ vtk7-7.1.1+dfsg2/debian/control 2023-06-18 19:50:44.0 +0200
@@ -32,7 +32,6 @@
libjsoncpp-dev,
libmrmpi-dev,
libnetcdf-dev,
-   libnetcdf-cxx-legacy-dev,
libogg-dev,
libosmesa6-dev,
libpng-dev,
@@ -101,7 +100,6 @@
  libjpeg-dev,
  libjsoncpp-dev,
  libnetcdf-dev,
- libnetcdf-cxx-legacy-dev,
  libogg-dev,
  libpng-dev,
  libpq-dev,
diff -Nru vtk7-7.1.1+dfsg2/debian/copyright vtk7-7.1.1+dfsg2/debian/copyright
--- vtk7-7.1.1+dfsg2/debian/copyright   2020-12-15 18:57:22.0 +0100
+++ vtk7-7.1.1+dfsg2/debian/copyright   2023-06-18 19:53:15.0 +0200
@@ -13,7 +13,6 @@
   ThirdParty/jpeg/vtkjpeg
   ThirdParty/jsoncpp/vtkjsoncpp
   ThirdParty/libxml2/vtklibxml2
-  ThirdParty/netcdf/vtknetcdf
   ThirdParty/oggtheora/vtkoggtheora
   ThirdParty/png/vtkpng
   ThirdParty/sqlite/vtksqlite
diff -Nru vtk7-7.1.1+dfsg2/debian/rules vtk7-7.1.1+dfsg2/debian/rules
--- vtk7-7.1.1+dfsg2/debian/rules   2020-12-15 18:57:22.0 +0100
+++ vtk7-7.1.1+dfsg2/debian/rules   2023-06-18 19:53:15.0 +0200
@@ -74,7 +74,7 @@
-DVTK_USE_SYSTEM_LIBPROJ4=OFF \
-DVTK_USE_SYSTEM_LIBXML2=ON \
-DVTK_USE_SYSTEM_MPI4PY=ON \
-   -DVTK_USE_SYSTEM_NETCDF=ON \
+   -DVTK_USE_SYSTEM_NETCDF=OFF \
-DVTK_USE_SYSTEM_OGGTHEORA=ON \
-DVTK_USE_SYSTEM_PNG=ON \
-DVTK_USE_SYSTEM_SIX=ON \

Bug#1038618: vtk6: Stop using netcdf-cxx-legacy

[Bas Couwenberg]

Source: vtk6
Version: 6.3.0+dfsg2-8.1
Severity: important
Tags: patch
User: debian-...@lists.debian.org
Usertags: netcdf-cxx-legacy-rm

Dear Maintainer,

Your package uses netcdf-cxx-legacy which is dead upstream and will be removed 
during the trixie development cycle.

The attached patch switches to the embedded copy, because the build actually 
requires the CXX component.

Kind Regards,

Bas
diff -Nru vtk6-6.3.0+dfsg2/debian/changelog vtk6-6.3.0+dfsg2/debian/changelog
--- vtk6-6.3.0+dfsg2/debian/changelog   2021-04-24 23:09:44.0 +0200
+++ vtk6-6.3.0+dfsg2/debian/changelog   2023-06-18 19:53:55.0 +0200
@@ -1,3 +1,10 @@
+vtk6 (6.3.0+dfsg2-8.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Don't use netcdf-cxx-legacy.
+
+ -- Bas Couwenberg   Sun, 18 Jun 2023 19:53:55 +0200
+
 vtk6 (6.3.0+dfsg2-8.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru vtk6-6.3.0+dfsg2/debian/control vtk6-6.3.0+dfsg2/debian/control
--- vtk6-6.3.0+dfsg2/debian/control 2020-12-11 22:46:17.0 +0100
+++ vtk6-6.3.0+dfsg2/debian/control 2023-06-18 19:53:28.0 +0200
@@ -28,7 +28,6 @@
libjsoncpp-dev,
libmrmpi-dev,
libnetcdf-dev,
-   libnetcdf-cxx-legacy-dev,
libogg-dev,
libosmesa6-dev,
libpng-dev,
@@ -79,7 +78,6 @@
  libjpeg-dev,
  libjsoncpp-dev,
  libnetcdf-dev,
- libnetcdf-cxx-legacy-dev,
  libogg-dev,
  libpng-dev,
  libpq-dev,
diff -Nru vtk6-6.3.0+dfsg2/debian/copyright vtk6-6.3.0+dfsg2/debian/copyright
--- vtk6-6.3.0+dfsg2/debian/copyright   2020-12-11 22:46:17.0 +0100
+++ vtk6-6.3.0+dfsg2/debian/copyright   2023-06-18 19:53:55.0 +0200
@@ -13,7 +13,6 @@
   ThirdParty/jpeg/vtkjpeg
   ThirdParty/jsoncpp/vtkjsoncpp
   ThirdParty/libxml2/vtklibxml2
-  ThirdParty/netcdf/vtknetcdf
   ThirdParty/oggtheora/vtkoggtheora
   ThirdParty/png/vtkpng
   ThirdParty/sqlite/vtksqlite
diff -Nru vtk6-6.3.0+dfsg2/debian/rules vtk6-6.3.0+dfsg2/debian/rules
--- vtk6-6.3.0+dfsg2/debian/rules   2020-12-11 22:46:17.0 +0100
+++ vtk6-6.3.0+dfsg2/debian/rules   2023-06-18 19:53:55.0 +0200
@@ -30,7 +30,7 @@
-DVTK_USE_SYSTEM_TIFF=ON \
-DVTK_USE_SYSTEM_ZLIB=ON \
-DVTK_USE_SYSTEM_JSONCPP=ON \
-   -DVTK_USE_SYSTEM_NETCDF=ON \
+   -DVTK_USE_SYSTEM_NETCDF=OFF \
-DVTK_USE_SYSTEM_GLEW=ON \
-DVTK_EXTRA_COMPILER_WARNINGS=ON \
-DVTK_Group_Imaging=ON \

Bug#1038617: linux-image-6.1.0-9-amd64: [ath9k] wifi soft toggle on HP Envy dv6 doesn't switch on or off

[Efly]

Package: src:linux
Version: 6.1.27-1
Severity: normal
X-Debbugs-Cc: powerrangersisb...@gmail.com

Hello Maintainer,

Ever sense I upgraded from Bullseye to Bookworm, the wifi toggle on my HP Envy 
dv6 keyboard 
stopped switching the wifi on or off while on the 6.1 kernel. I tried the 6.3 
unstable kernel and the problem still persists.
None of my hardware has changed and switching back to the 5.10 kernel in the 
advanced options makes it work again.
Also when I turn off the laptop, an error shows up about a dozen times right 
before it shuts
off that says
[ 56.101163] ACPI Warning: Time Parameter 255 us > 100 us violating ACPI Spec, 
please fix the firmware. (20220331/exsystem- 141)

Thank you for your time and patience.

** Kernel log:
[9.983303] device-mapper: ioctl: 4.47.0-ioctl (2022-07-28) initialised: 
dm-de...@redhat.com
[9.999215] systemd[1]: Mounting sys-fs-fuse-connections.mount - FUSE 
Control File System...
[   10.001474] systemd[1]: Mounting sys-kernel-config.mount - Kernel 
Configuration File System...
[   10.002496] systemd[1]: modprobe@dm_mod.service: Deactivated successfully.
[   10.006457] EXT4-fs (sda6): re-mounted. Quota mode: none.
[   10.007896] systemd[1]: Finished modprobe@dm_mod.service - Load Kernel 
Module dm_mod.
[   10.011143] systemd[1]: Finished systemd-modules-load.service - Load Kernel 
Modules.
[   10.015482] systemd[1]: Finished systemd-remount-fs.service - Remount Root 
and Kernel File Systems.
[   10.019973] systemd[1]: Mounted sys-fs-fuse-connections.mount - FUSE Control 
File System.
[   10.022660] systemd[1]: systemd-firstboot.service - First Boot Wizard was 
skipped because of an unmet condition check (ConditionFirstBoot=yes).
[   10.022745] systemd[1]: systemd-pstore.service - Platform Persistent Storage 
Archival was skipped because of an unmet condition check 
(ConditionDirectoryNotEmpty=/sys/fs/pstore).
[   10.028263] systemd[1]: Starting systemd-random-seed.service - Load/Save 
Random Seed...
[   10.028459] systemd[1]: systemd-repart.service - Repartition Root Disk was 
skipped because no trigger condition checks were met.
[   10.036365] systemd[1]: Starting systemd-sysctl.service - Apply Kernel 
Variables...
[   10.043494] systemd[1]: Starting systemd-sysusers.service - Create System 
Users...
[   10.045428] systemd[1]: Mounted sys-kernel-config.mount - Kernel 
Configuration File System.
[   10.096713] systemd[1]: Finished systemd-sysctl.service - Apply Kernel 
Variables.
[   10.126425] systemd[1]: Finished systemd-sysusers.service - Create System 
Users.
[   10.135334] systemd[1]: Starting systemd-tmpfiles-setup-dev.service - Create 
Static Device Nodes in /dev...
[   10.193481] systemd[1]: Finished systemd-tmpfiles-setup-dev.service - Create 
Static Device Nodes in /dev.
[   10.207372] systemd[1]: Starting systemd-udevd.service - Rule-based Manager 
for Device Events and Files...
[   10.320587] systemd[1]: Started systemd-journald.service - Journal Service.
[   10.362207] systemd-journald[244]: Received client request to flush runtime 
journal.
[   10.737838] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   10.739781] sr 1:0:0:0: Attached scsi generic sg1 type 5
[   10.974468] acpi_cpufreq: overriding BIOS provided _PSD data
[   11.020331] hp_accel: laptop model unknown, using default axes configuration
[   11.074891] random: crng init done
[   11.080763] lis3lv02d: 8 bits 3DC sensor found
[   11.155185] ACPI: AC: AC Adapter [ADP1] (off-line)
[   11.165384] input: ST LIS3LV02DL Accelerometer as 
/devices/platform/lis3lv02d/input/input7
[   11.251069] sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver
[   11.251281] sp5100-tco sp5100-tco: Using 0xfed80b00 for watchdog MMIO address
[   11.251436] sp5100-tco sp5100-tco: initialized. heartbeat=60 sec (nowayout=0)
[   11.317666] wdat_wdt wdat_wdt: can't request region for resource [mem 
0xfec000f0-0xfec000f3]
[   11.317725] wdat_wdt: probe of wdat_wdt failed with error -16
[   11.441136] cryptd: max_cpu_qlen set to 1000
[   11.583120] AVX version of gcm_enc/dec engaged.
[   11.583160] AES CTR mode by8 optimization enabled
[   11.700357] snd_hda_intel :00:01.1: Force to non-snoop mode
[   11.785299] Adding 8429568k swap on /dev/sda7.  Priority:-2 extents:1 
across:8429568k SSFS
[   11.970772] snd_hda_codec_idt hdaudioC1D0: autoconfig for 92HD91BXX: 
line_outs=1 (0xd/0x0/0x0/0x0/0x0) type:speaker
[   11.970783] snd_hda_codec_idt hdaudioC1D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[   11.970788] snd_hda_codec_idt hdaudioC1D0:hp_outs=1 (0xb/0x0/0x0/0x0/0x0)
[   11.970793] snd_hda_codec_idt hdaudioC1D0:mono: mono_out=0x0
[   11.970797] snd_hda_codec_idt hdaudioC1D0:inputs:
[   11.970801] snd_hda_codec_idt hdaudioC1D0:  Internal Mic=0x11
[   11.970806] snd_hda_codec_idt hdaudioC1D0:  Mic=0xa
[   11.979835] input: HDA ATI HDMI HDMI/DP,pcm=3 as 
/devices/pci:00/:00:01.1/sound/card0/input9
[   11.994202] cfg80211: Loading compiled-in X.509 certificates for regulatory 
database
[  

Bug#996976: vtk6: Remove vtk6 from the Debian 12

[Sebastiaan Couwenberg]

itksnap is the only remain rdep of vtk6:

 sebastic@coccia:~$ dak rm -Rn vtk6
 Will remove the following packages from unstable:

 libvtk6-dev | 6.3.0+dfsg2-8.1+b1 | amd64, arm64, armel, armhf, i386, 
mips64el, mipsel, ppc64el, s390x
 libvtk6-qt-dev | 6.3.0+dfsg2-8.1+b1 | amd64, arm64, armel, armhf, 
i386, mips64el, mipsel, ppc64el, s390x
  libvtk6.3 | 6.3.0+dfsg2-8.1+b1 | amd64, arm64, armel, armhf, i386, 
mips64el, mipsel, ppc64el, s390x
 libvtk6.3-qt | 6.3.0+dfsg2-8.1+b1 | amd64, arm64, armel, armhf, i386, 
mips64el, mipsel, ppc64el, s390x

   vtk6 | 6.3.0+dfsg2-8.1 | source

 Maintainer: Debian Science Team 



 --- Reason ---

 --

 Checking reverse dependencies...
 # Broken Depends:
 itksnap: itksnap [amd64 i386]

 # Broken Build-Depends:
 itksnap: libvtk6-dev

 Dependency problem found.

The maintainer has not responded to the RC bugs affecting itksnap 
(#1013152 & #1010549).


itksnap should be removed from Debian along with vtk6, or itksnap should 
be update to 4.0 which claims to support VTK 9:


"
 * Updated library references to ITK 5, VTK 9, and Qt 6
"

https://github.com/pyushkevich/itksnap/blob/v4.0.0/ReleaseNotes.md#version-400

Kind Regards,

Bas

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

Bug#1038616: bookworm-pu: package network-manager-strongswan/1.6.0-1+deb12u1

[Harald Dunkel]

Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: network-manager-strongs...@packages.debian.org, 
ijack...@chiark.greenend.org.uk, harald.dun...@aixigo.com
Control: affects -1 + src:network-manager-strongswan

[ Reason ]
The old network-manager-strongswan 1.6.0-1 was built for GTK3 only,
leaving the Gnome Netork Settings menu (GTK4) behind, see #1020495.
The package worked fine with the nm-connection-editor, but using
Gnome Network Settings there was just a message "Error: unable to
load VPN connection editor" instead of the expected config menu.

The bug was introduced on the integration of the new upstream version
on July 16th 2022. 

[ Impact ]
Configuring an IPsec network connection using the Gnome Network
Settings on the Gnome desktop is not possible. You have to use
the nm-connection-editor instead.

[ Tests ]
I could reproduce the bug in the old package. Trying to configure an
IPsec connection Gnome Network Settings showed "Error: unable to load
VPN connection editor" instead of the config menu provided by network-
manager-strongswan. 

I have built the proposed new package for Bookworm (pbuilder).

I have verified it on Bookworm using nm-connection-editor (GTK3) on
Gnome, Gnome Network Settings (GTK4), and xfce4 network settings.
n-m-s worked for all, esp the error message in Gnome Network Settings
is gone. The expected config menu is shown instead.

[ Risks ]
Upstreams code is identical to the current package in Stable. No
source code changes have been introduced. The fix affects just
debian/control and debian/rules.

The binaries provided by the proposed new package support GTK4 in
addition to GTK3. Risk is low.

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

[ Changes ]
debian/control adds a several GTK4 packages to the build environment.
debian/rules adds an option to the configure command line 

[ Other info ]
none
diff -Nru network-manager-strongswan-1.6.0/debian/changelog 
network-manager-strongswan-1.6.0/debian/changelog
--- network-manager-strongswan-1.6.0/debian/changelog   2022-07-16 
14:07:25.0 +0200
+++ network-manager-strongswan-1.6.0/debian/changelog   2023-06-11 
10:20:41.0 +0200
@@ -1,3 +1,11 @@
+network-manager-strongswan (1.6.0-1+deb12u1) bookworm; urgency=medium
+
+  [ Harald Dunkel ]
+  * Build editor component with GTK 4, too (fix provided by Moritz Schlarb)
+(Closes: #1020495, #1036607)
+
+ -- Harald Dunkel   Sun, 11 Jun 2023 10:20:41 +0200
+
 network-manager-strongswan (1.6.0-1) unstable; urgency=medium
 
   * new upstream version 1.6.0:
diff -Nru network-manager-strongswan-1.6.0/debian/control 
network-manager-strongswan-1.6.0/debian/control
--- network-manager-strongswan-1.6.0/debian/control 2022-07-16 
14:07:25.0 +0200
+++ network-manager-strongswan-1.6.0/debian/control 2023-06-11 
10:20:41.0 +0200
@@ -6,9 +6,12 @@
 Build-Depends: debhelper-compat (= 13)
, network-manager-dev (>= 1.14)
, libnma-dev (>= 1.8)
+   , libnma-gtk4-dev (>= 1.8)
, libnm-dev (>= 1.14)
, libdbus-glib-1-dev
, libgtk-3-dev
+   , libgtk-4-dev
+   , libgtk-4-bin
, libsecret-1-dev
, automake
, gnome-common
diff -Nru network-manager-strongswan-1.6.0/debian/rules 
network-manager-strongswan-1.6.0/debian/rules
--- network-manager-strongswan-1.6.0/debian/rules   2022-07-16 
14:07:25.0 +0200
+++ network-manager-strongswan-1.6.0/debian/rules   2023-06-11 
10:20:41.0 +0200
@@ -4,7 +4,7 @@
dh $@ --with autoreconf
 
 override_dh_auto_configure:
-   dh_auto_configure -- --without-libnm-glib 
--with-charon=/usr/lib/ipsec/charon-nm 
--libexecdir="\$$(prefix)/lib/NetworkManager"
+   dh_auto_configure -- --with-gtk4 --without-libnm-glib 
--with-charon=/usr/lib/ipsec/charon-nm 
--libexecdir="\$$(prefix)/lib/NetworkManager"
 
 override_dh_clean:
dh_clean -XNetworkManager-strongswan.metainfo.xml 
nm-strongswan-service.name

Bug#1026405: calamaris: [INTL:pt_BR] Brazilian Portuguese debconf templates translation

[Paulo Henrique de Lima Santana]

Hi,

I uploaded a NMU to 10-day/delay queue. Feel free to cancel this
upload if needed.

The debian/changelog is:

calamaris (2.99.4.7-1.1) unstable; urgency=medium

  * Non-maintainer upload.
  * Update po file into Brazilian Portuguese translation. (Closes: 
#1026405)

  * debian/control
+ Bump Standards-Version 4.6.2

I attached a debdiff.

Thanks.

Regards,

--
Paulo Henrique de Lima Santana (phls)
Belo Horizonte - Brasil
Debian Developer
Site: http://phls.com.br
GPG ID: 0443C450
diff -Nru calamaris-2.99.4.7/debian/changelog 
calamaris-2.99.4.7/debian/changelog
--- calamaris-2.99.4.7/debian/changelog 2021-12-25 19:08:43.0 -0300
+++ calamaris-2.99.4.7/debian/changelog 2023-06-19 01:00:45.0 -0300
@@ -1,3 +1,12 @@
+calamaris (2.99.4.7-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Update po file into Brazilian Portuguese translation. (Closes: #1026405)
+  * debian/control
++ Bump Standards-Version 4.6.2
+
+ -- Paulo Henrique de Lima Santana (phls)   Mon, 19 Jun 2023 
01:00:45 -0300
+
 calamaris (2.99.4.7-1) unstable; urgency=medium
 
   * New upstream release. (Closes: #1001935)
diff -Nru calamaris-2.99.4.7/debian/control calamaris-2.99.4.7/debian/control
--- calamaris-2.99.4.7/debian/control   2021-12-25 19:08:43.0 -0300
+++ calamaris-2.99.4.7/debian/control   2023-06-19 01:00:45.0 -0300
@@ -2,7 +2,7 @@
 Section: utils
 Priority: optional
 Maintainer: Daniel Echeverri 
-Standards-Version: 4.6.0.1
+Standards-Version: 4.6.2
 Build-Depends: debconf, debhelper-compat (= 13), po-debconf
 Homepage: http://cord.de/tools/squid/calamaris/
 Rules-Requires-Root: binary-targets
diff -Nru calamaris-2.99.4.7/debian/copyright 
calamaris-2.99.4.7/debian/copyright
--- calamaris-2.99.4.7/debian/copyright 2021-12-25 19:08:43.0 -0300
+++ calamaris-2.99.4.7/debian/copyright 2023-06-19 01:00:45.0 -0300
@@ -10,6 +10,7 @@
 Files: debian/*
 Copyright: 1998-2011 Philipp Frauenfelder 
   2011-2021 Daniel Echeverry 
+  2023  Paulo Henrique de Lima Santana 
 License: GPL-2.0+
 
 Files: calAxestype.pm calAxestype3d.pm calBars3d.pm
diff -Nru calamaris-2.99.4.7/debian/po/pt_BR.po 
calamaris-2.99.4.7/debian/po/pt_BR.po
--- calamaris-2.99.4.7/debian/po/pt_BR.po   2021-12-25 19:08:43.0 
-0300
+++ calamaris-2.99.4.7/debian/po/pt_BR.po   2023-06-19 00:59:50.0 
-0300
@@ -10,64 +10,68 @@
 # or http://www.debian.org/intl/l10n/po-debconf/README-trans
 #
 #Developers do not need to manually edit POT or PO files.
+# Paulo Henrique de Lima Santana (phls) , 2022.
 #
 msgid ""
 msgstr ""
-"Project-Id-Version: calamaris_2.56-1\n"
-"Report-Msgid-Bugs-To: calama...@packages.debian.org\n"
-"POT-Creation-Date: 2011-06-26 00:29-0500\n"
-"PO-Revision-Date: 2005-O5-11 18:07-0200\n"
-"Last-Translator: André Luís Lopes \n"
-"Language-Team: Debian-BR Project \n"
-"Language: \n"
+"Project-Id-Version: calamaris_2.99.4.7-1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-11-28 14:53+\n"
+"PO-Revision-Date: 2022-12-19 13:10-0300\n"
+"Last-Translator: Paulo Henrique de Lima Santana (phls) \n"
+"Language-Team: Brazilian Portuguese \n"
+"Language: pt_BR\n"
 "MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=ISO-8859-1\n"
+"Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
+"X-Generator: Gtranslator 42.0\n"
+"Plural-Forms: nplurals=2; plural=(n > 1)\n"
 
 #. Type: select
 #. Choices
-#: ../templates:2001
+#: ../calamaris.templates:2001
 msgid "auto"
-msgstr ""
+msgstr "auto"
 
 #. Type: select
 #. Choices
-#: ../templates:2001
+#: ../calamaris.templates:2001
 msgid "squid"
-msgstr ""
+msgstr "squid"
 
 #. Type: select
 #. Choices
-#: ../templates:2001
+#: ../calamaris.templates:2001
 msgid "squid3"
-msgstr ""
+msgstr "squid3"
 
 #. Type: select
 #. Description
-#: ../templates:2002
-#, fuzzy
-#| msgid "What type of proxy log files do you want to analyse?"
+#: ../calamaris.templates:2002
 msgid "Type of proxy log files to analyze:"
-msgstr "Qual tipo de arquivo de log de proxy você quer analisar ?"
+msgstr "Tipo de arquivos de log do proxy para analisar:"
 
 #. Type: select
 #. Description
-#: ../templates:2002
+#: ../calamaris.templates:2002
 msgid ""
 "Calamaris is able to process log files from Squid or Squid3. If you choose "
 "'auto' it will look first for Squid log files and then for Squid3 log files."
 msgstr ""
-"O Calamaris é capaz de processar arquivos de log do Squid ou do Squid3. Caso "
-"você escolha 'auto'o Calamaris irá procurar primeiro por arquivos de log do "
-"Squid e depois por arquivos de log do Squid3."
+"O Calamaris é capaz de processar arquivos de log do Squid ou Squid3. Se você "
+"escolher \"auto\", ele procurará primeiro pelos arquivos de log do Squid e "
+"depois pelos arquivos de log do Squid3."
 
 #. Type: select
 #. Description
-#: ../templates:2002
+#: ../calamaris.templates:2002
 msgid ""
 "Choosing 'auto' is recommended when only one proxy is installed. 

Bug#1037287: AttributeError: 'NoneType' object has no attribute 'hardlink_target'

[Robert Edmonds]

Nicholas Guriev wrote:
> Since some time bup is unable to backup my data. This is apparently related to
> hard links somehow.

> bup "-d" 
> "/media/mymedia/a3907ce1-af8b-40b1-b26b-f37322e39382/barberry-kde-backups" 
> "save" "-n" "kup" "-vv" "/home/mymedia" "/home/mymedia/.steam/steam/config" 
> "/home/mymedia/.steam/steam/userdata"
> Traceback (most recent call last):
>   File "/usr/lib/bup/cmd/bup-save", line 413, in 
> meta.hardlink_target = find_hardlink_target(hlink_db, ent)
> AttributeError: 'NoneType' object has no attribute 'hardlink_target'
> Exception ignored in: 
> Traceback (most recent call last):
>   File "/usr/lib/bup/cmd/../bup/git.py", line 722, in __del__
>   File "/usr/lib/bup/cmd/../bup/git.py", line 919, in close
>   File "/usr/lib/bup/cmd/../bup/git.py", line 897, in _end
>   File "/usr/lib/bup/cmd/../bup/git.py", line 942, in write
> NameError: name 'open' is not defined

Hi,

I'd suggest normal bug debugging steps like "bup fsck" or "bup index
--clear" and if that doesn't fix the problem, try posting on the
upstream bup mailing list (https://groups.google.com/g/bup-list).

-- 
Robert Edmonds
edmo...@debian.org

Bug#1038615: gcc-12-aarch64-linux-gnu: :amd64 package not installable on arm64

[Ian Gulliver]

Package: gcc-12-aarch64-linux-gnu
Version: 12.2.0-14cross1
Severity: normal
X-Debbugs-Cc: deb...@flamingcow.io

When attempting to install gcc-12-aarch64-linux-gnu:amd64 on an arm64
system, conflicts prevent installation. I realize this is a silly thing
to want to do; this is attempt to simplify a cross-compile build, and
it works fine the other way (installing gcc-12-i686-linux-gnu:arm64 on
amd64).

The following packages have unmet dependencies:
 gcc-12-aarch64-linux-gnu:amd64 : Depends: binutils-aarch64-linux-gnu:amd64 (>= 
2.40) but it is not going to be installed
  Depends: libgcc-12-dev-arm64-cross:amd64 (>= 
12.2.0-14cross1) but it is not installable
E: Unable to correct problems, you have held broken packages.

-- System Information:
Debian Release: 12.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: arm64 (aarch64)
Foreign Architectures: amd64

Kernel: Linux 6.1.0-9-arm64 (SMP w/16 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)
LSM: AppArmor: enabled

Bug#1038614: vtk9: Stop using netcdf-cxx-legacy

[Bas Couwenberg]

Source: vtk9
Version: 9.1.0+really9.1.0+dfsg2-5
Severity: important
Tags: patch
User: debian-...@lists.debian.org
Usertags: netcdf-cxx-legacy-rm

Dear Maintainer,

Your package uses netcdf-cxx-legacy which is dead upstream and will be removed 
during the trixie development cycle.

The attached patch only drops the build dependency, as your package doesn't 
actually link to netcdf-cxx-legacy.

Kind Regards,

Bas
diff -Nru vtk9-9.1.0+really9.1.0+dfsg2/debian/changelog 
vtk9-9.1.0+really9.1.0+dfsg2/debian/changelog
--- vtk9-9.1.0+really9.1.0+dfsg2/debian/changelog   2023-02-25 
09:59:35.0 +0100
+++ vtk9-9.1.0+really9.1.0+dfsg2/debian/changelog   2023-06-18 
19:47:19.0 +0200
@@ -1,3 +1,10 @@
+vtk9 (9.1.0+really9.1.0+dfsg2-5.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Don't use netcdf-cxx-legacy.
+
+ -- Bas Couwenberg   Sun, 18 Jun 2023 19:47:19 +0200
+
 vtk9 (9.1.0+really9.1.0+dfsg2-5) unstable; urgency=medium
 
   [ Elvis Stansvik ]
diff -Nru vtk9-9.1.0+really9.1.0+dfsg2/debian/control 
vtk9-9.1.0+really9.1.0+dfsg2/debian/control
--- vtk9-9.1.0+really9.1.0+dfsg2/debian/control 2023-02-25 09:57:02.0 
+0100
+++ vtk9-9.1.0+really9.1.0+dfsg2/debian/control 2023-06-18 19:47:19.0 
+0200
@@ -41,7 +41,6 @@
libjsoncpp-dev,
liblz4-dev,
libmrmpi-dev,
-   libnetcdf-cxx-legacy-dev,
libnetcdf-dev (>= 1:4.9.0),
libogg-dev,
libosmesa6-dev,
@@ -108,7 +107,6 @@
  libjpeg-dev,
  libjsoncpp-dev,
  liblz4-dev,
- libnetcdf-cxx-legacy-dev,
  libnetcdf-dev,
  libpng-dev,
  libpq-dev,

Bug#1038613: ifup.8: some remarks and editing fixes for the manual

[Bjarni Ingi Gislason]

Package: ifupdown
Version: 0.8.41
Severity: minor
Tags: patch

Dear Maintainer,

here are some notes and fixes for the manual.

Input file is ifup.8

Output from "mandoc  -T lint ifup.8":

mandoc: ifup.8:9:9: STYLE: whitespace at end of input line
mandoc: ifup.8:18:9: STYLE: whitespace at end of input line
mandoc: ifup.8:21:9: STYLE: whitespace at end of input line
mandoc: ifup.8:91:8: STYLE: whitespace at end of input line
mandoc: ifup.8:95:32: STYLE: whitespace at end of input line
mandoc: ifup.8:107:82: STYLE: input text line longer than 80 bytes: Exclude 
interfaces f...
mandoc: ifup.8:128:86: STYLE: input text line longer than 80 bytes: Disable 
special hand...
mandoc: ifup.8:129:85: STYLE: input text line longer than 80 bytes: (\fIlo\fR 
on Linux) ...
mandoc: ifup.8:130:85: STYLE: input text line longer than 80 bytes: on \fBifup 
-a\fR aut...
mandoc: ifup.8:131:84: STYLE: input text line longer than 80 bytes: the 
interface is con...
mandoc: ifup.8:132:83: STYLE: input text line longer than 80 bytes: defined as 
loopback,...
mandoc: ifup.8:146:82: STYLE: input text line longer than 80 bytes: For 
\fBifquery\fR, d...
mandoc: ifup.8:147:85: STYLE: input text line longer than 80 bytes: lists all 
interfaces...
mandoc: ifup.8:148:81: STYLE: input text line longer than 80 bytes: exits with 
a status ...
mandoc: ifup.8:149:88: STYLE: input text line longer than 80 bytes: display 
state of the...
mandoc: ifup.8:156:3: STYLE: whitespace at end of input line
mandoc: ifup.8:218:124: STYLE: input text line longer than 80 bytes: Ifupdown 
uses per-in...
mandoc: ifup.8:225:120: STYLE: input text line longer than 80 bytes: the exit 
status will...
mandoc: ifup.8:228:92: STYLE: input text line longer than 80 bytes: on an 
interface that...
mandoc: ifup.8:233:119: STYLE: input text line longer than 80 bytes: will 
normally return...
mandoc: ifup.8:235:84: STYLE: input text line longer than 80 bytes: will also 
return wit...
mandoc: ifup.8:275:56: STYLE: whitespace at end of input line

###

Remove space characters at the end of lines.

Use "git apply ... --whitespace=fix" to fix extra space issues, or use
global configuration "core.whitespace".

9:.B ifup 
18:.B ifup 
21:.B ifup 
91:line in 
95:Read interface definitions from 
156:in 
275:that appear as a result of hardware being installed and 

#

Mark a full stop (.) with "\&",
if it does not mean an end of a sentence.
This is a preventive action,
the paragraph could be reshaped, e.g., after changes.

When typing, one does not always notice when the line wraps after the
period.
There are too many examples of input lines in manual pages,
that end with an abbreviation point.

This marking is robust, and independent of the position on the line.

It corresponds to "\ " in TeX, and to "@:" in Texinfo.


60:.IR /etc/network/interfaces ". "

#

Change -- in x--y to \(em (em-dash), or, if an
option, to \-\-

175:.B ifquery -l --allow=hotplug
234:.B ifquery --state

#

Use the correct macro for the font change of a single argument or
split the argument into two.

145:.BR \-\-state
186:.BR ifquery
191:.BR ip
203:.BR ifdown

#

Change a HYPHEN-MINUS (code 0x55, 2D) to a minus (\-), if in front of a
name for an option.

130:on \fBifup -a\fR automatically. In the case the loopback device is 
redefined by user,
153:.B ifup -a
169:.B ifdown -a
172:.B ifquery -l
175:.B ifquery -l --allow=hotplug

#

Wrong distance between sentences.

  Separate the sentences and subordinate clauses; each begins on a new
line.  See man-pages(7) ("Conventions for source file layout") and
"info groff" ("Input Conventions").

  The best procedure is to always start a new sentence on a new line,
at least, if you are typing on a computer.

Remember coding: Only one command ("sentence") on each (logical) line.

E-mail: Easier to quote exactly the relevant lines.

Generally: Easier to edit the sentence.

Patches: Less unaffected text.

  The amount of space between sentences in the output can then be
controlled with the ".ss" request.

74:currently listed in the state file. Only interfaces defined
108:\fIPATTERN\fR uses a usual shell glob syntax. If shell wildcards are not 
used, it
109:must match the exact interface name. This option may be specified multiple 
times
128:Disable special handling of the loopback interface. By default, the 
loopback interface
130:on \fBifup -a\fR automatically. In the case the loopback device is 
redefined by user,
131:the interface is configured just once anyway. If, however, another 
interface is also
132:defined as loopback, it's configured as usual. Specifying this option 
disables this
146:For \fBifquery\fR, dump the state of the interfaces. When no interfaces 
specified,
148:exits with a status code indicating success. If one or more interfaces 
specified,
150:given as arguments are up. Otherwise, 0 is returned.
180:configuration. Each key-value pair is printed out on individual
198:is still running. In that case,

#

Add a thin space 

Bug#1035587: linux: broken AHCI controller on MIPS Loongson 3 (regression from 5.10.162-1)

[Huacai Chen]

On Sun, Jun 18, 2023 at 5:24 PM Aurelien Jarno  wrote:
>
> Hi,
>
> On 2023-05-07 19:22, Jiaxun Yang wrote:
> >
> >
> > > 2023年5月6日 01:58，YunQiang Su  写道：
> > >
> > > Aurelien Jarno  于2023年5月6日周六 04:30写道：
> > >>
> > >> Source: linux
> > >> Version: 5.10.178-3
> > >> Severity: important
> > >> X-Debbugs-Cc: d...@debian.org, debian-m...@lists.debian.org, 
> > >> s...@debian.org
> > >>
> > >> Following the point release, the buildd mipsel-osuosl-03.d.o does not
> > >> boot anymore, with errors in the AHCI controller:
> > >>
> > >> [   35.912147] ata4.00: exception Emask 0x0 SAct 0x2000 SErr 0x0 
> > >> action 0x6 frozen
> > >> [   35.919769] ata4.00: failed command: WRITE FPDMA QUEUED
> > >> [   35.924968] ata4.00: cmd 61/20:e8:00:f0:e1/00:00:00:00:00/40 tag 29 
> > >> ncq dma 16384 out
> > >> [   35.924968]  res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 
> > >> 0x4 (timeout)
> > >> [   35.940097] ata4.00: status: { DRDY }
> > >> [   35.943743] ata4: hard resetting link
> > >>
> > >> While that initially looks like a hardware issue, it appears that
> > >> reverting the kernel to 5.10.162-1 (from 5.10.178-3) fixes the issue.
> > >> Strangely mipsel.osuosl-05.d.o, which seems to be similar hardware (CPU,
> > >> motherboard and SATA drive), does not exhibit the same issue.
> > >>
> > >
> > > Maybe the different firmwares are used for them...
> > > CCed Huacai and Jiaxun.
> >
> > I’m unable to reproduce on my side. Perhaps different hardware.
> > Is it possible to bisect Kernel on that machine to see of reverting that 
> > two commits do help?
>
> I have bisected the issue and I confirm the intuition from Cyril. The
> first bad commit is 654ae539254d10042869fdc77ad04c09e7eff1fd. Reverting
> both commits (they are linked) indeed fixes the issue.
Seems a firmware bug, latest firmware should configure a suitable MRRS.

Huacai
>
> Aurelien
>
> --
> Aurelien Jarno  GPG: 4096R/1DDD8C9B
> aurel...@aurel32.net http://aurel32.net

Bug#1038612: Reporting a unworkable / bug

[Budi]

Package: Debian installer

but only its more specific part:   os-prober

Version:  unknown
because os-prober has no feature to give version

It'll hanging, at a condition / here at or mavbe after the scanning of ESP

The partition /dev/sda6 is live/running OS where it's done

The bash trace (by set -x insert in it):

+ . /usr/share/os-prober/common.sh
++ cleanup_tmpdir=false
++ progname=
++ type mapdevfs
+ newns
+ '[' '' ']'
+ exec /usr/lib/os-prober/newns /usr/local/bin/os-prober
+ . /usr/share/os-prober/common.sh
++ cleanup_tmpdir=false
++ progname=
++ type mapdevfs
+ newns
+ '[' 1 ']'
+ require_tmpdir
+ '[' -z '' ']'
+ type mktemp
++ mktemp -d /tmp/os-prober.XX
+ export OS_PROBER_TMP=/tmp/os-prober.JJ6Qg1
+ OS_PROBER_TMP=/tmp/os-prober.JJ6Qg1
+ cleanup_tmpdir=:
+ trap cleanup EXIT HUP INT QUIT TERM
+ :
+ type dmraid
+ dmraid -r -c
+ true
+ rm -f /var/lib/os-prober/labels
+ for prog in /usr/lib/os-probes/init/*
+ '[' -x /usr/lib/os-probes/init/10filesystems ']'
+ '[' -f /usr/lib/os-probes/init/10filesystems ']'
+ /usr/lib/os-probes/init/10filesystems
+ grep '^/dev/' /proc/mounts
+ parse_proc_mounts
+ read -r line
+ set -f
+ set -- /dev/sda6 / ext4 rw,noatime 0 0
+ set +f
++ mapdevfs /dev/sda6
++ readlink -f /dev/sda6
+ printf '%s %s %s\n' /dev/sda6 / ext4
+ read -r line
+ set -f
+ set -- /dev/sda2 /boot/efi vfat
rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro
0 0
+ set +f
++ mapdevfs /dev/sda2
++ readlink -f /dev/sda2
+ printf '%s %s %s\n' /dev/sda2 /boot/efi vfat
+ read -r line
+ set -f
+ set -- /dev/sda10 /home ext4 rw,noatime 0 0
+ set +f
++ mapdevfs /dev/sda10
++ readlink -f /dev/sda10
+ printf '%s %s %s\n' /dev/sda10 /home ext4
+ read -r line
+ set -f
+ set -- /dev/sda11 /opt xfs
rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0
+ set +f
++ mapdevfs /dev/sda11
++ readlink -f /dev/sda11
+ printf '%s %s %s\n' /dev/sda11 /opt xfs
+ read -r line
+ :
+ '[' -f /proc/swaps ']'
+ grep '^/dev/' /proc/swaps
+ parse_proc_swaps
+ read line
+ set -f
+ set -- /dev/sda5 partition 6800380 0 -2
+ set +f
++ mapdevfs /dev/sda5
++ readlink -f /dev/sda5
+ echo '/dev/sda5 swap'
+ read line
+ :
+ '[' -f /proc/mdstat ']'
++ partitions
+++ uname -s
++ os_name=Linux
++ '[' -d /sys/block ']'
++ for part in /sys/block/*/*[0-9]
++ '[' -f /sys/block/sda/sda1/start ']'
++ '[' '!' -f /sys/block/sda/sda1/whole_disk ']'
++ on_sataraid /sys/block/sda/sda1
++ local parent=/sys/block/sda
++ local device=/dev/sda
++ grep -q /dev/sda /tmp/os-prober.JJ6Qg1/dmraid-map
++ return 1
+++ echo sda1
+++ sed 's,[!.],/,g'
++ name=sda1
++ '[' -e /dev/sda1 ']'
++ echo /dev/sda1
++ for part in /sys/block/*/*[0-9]
++ '[' -f /sys/block/sda/sda10/start ']'
++ '[' '!' -f /sys/block/sda/sda10/whole_disk ']'
++ on_sataraid /sys/block/sda/sda10
++ local parent=/sys/block/sda
++ local device=/dev/sda
++ grep -q /dev/sda /tmp/os-prober.JJ6Qg1/dmraid-map
++ return 1
+++ echo sda10
+++ sed 's,[!.],/,g'
++ name=sda10
++ '[' -e /dev/sda10 ']'
++ echo /dev/sda10
++ for part in /sys/block/*/*[0-9]
++ '[' -f /sys/block/sda/sda11/start ']'
++ '[' '!' -f /sys/block/sda/sda11/whole_disk ']'
++ on_sataraid /sys/block/sda/sda11
++ local parent=/sys/block/sda
++ local device=/dev/sda
++ grep -q /dev/sda /tmp/os-prober.JJ6Qg1/dmraid-map
++ return 1
+++ echo sda11
+++ sed 's,[!.],/,g'
++ name=sda11
++ '[' -e /dev/sda11 ']'
++ echo /dev/sda11
++ for part in /sys/block/*/*[0-9]
++ '[' -f /sys/block/sda/sda12/start ']'
++ '[' '!' -f /sys/block/sda/sda12/whole_disk ']'
++ on_sataraid /sys/block/sda/sda12
++ local parent=/sys/block/sda
++ local device=/dev/sda
++ grep -q /dev/sda /tmp/os-prober.JJ6Qg1/dmraid-map
++ return 1
+++ sed 's,[!.],/,g'
+++ echo sda12
++ name=sda12
++ '[' -e /dev/sda12 ']'
++ echo /dev/sda12
++ for part in /sys/block/*/*[0-9]
++ '[' -f /sys/block/sda/sda13/start ']'
++ '[' '!' -f /sys/block/sda/sda13/whole_disk ']'
++ on_sataraid /sys/block/sda/sda13
++ local parent=/sys/block/sda
++ local device=/dev/sda
++ grep -q /dev/sda /tmp/os-prober.JJ6Qg1/dmraid-map
++ return 1
+++ echo sda13
+++ sed 's,[!.],/,g'
++ name=sda13
++ '[' -e /dev/sda13 ']'
++ echo /dev/sda13
++ for part in /sys/block/*/*[0-9]
++ '[' -f /sys/block/sda/sda2/start ']'
++ '[' '!' -f /sys/block/sda/sda2/whole_disk ']'
++ on_sataraid /sys/block/sda/sda2
++ local parent=/sys/block/sda
++ local device=/dev/sda
++ grep -q /dev/sda /tmp/os-prober.JJ6Qg1/dmraid-map
++ return 1
+++ sed 's,[!.],/,g'
+++ echo sda2
++ name=sda2
++ '[' -e /dev/sda2 ']'
++ echo /dev/sda2
++ for part in /sys/block/*/*[0-9]
++ '[' -f /sys/block/sda/sda3/start ']'
++ '[' '!' -f /sys/block/sda/sda3/whole_disk ']'
++ on_sataraid /sys/block/sda/sda3
++ local parent=/sys/block/sda
++ local device=/dev/sda
++ grep -q /dev/sda /tmp/os-prober.JJ6Qg1/dmraid-map
++ return 1
+++ echo sda3
+++ sed 's,[!.],/,g'
++ name=sda3
++ '[' -e /dev/sda3 ']'
++ echo /dev/sda3
++ for part in /sys/block/*/*[0-9]
++ '[' -f /sys/block/sda/sda4/start ']'
++ '[' '!' -f 

Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0

[Adilson dos Santos Dantas]

Package: lightdm
Version: 1.32.0-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After upgrading lightdm to the latest upstream version (1.32.0-2) fails to
start X session leading only to console mode.

Downgrading to 1.26.0-8, from testing, fixes this bug.



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

Kernel: Linux 6.3.8 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8),
LANGUAGE=pt_BR:p
t:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lightdm depends on:
ii  adduser3.134
ii  dbus   1.14.8-1
ii  debconf [debconf-2.0]  1.5.82
ii  libaudit1  1:3.0.9-1
ii  libc6  2.36-9
ii  libgcrypt201.10.2-2
ii  libglib2.0-0   2.74.6-2
ii  libpam-systemd [logind]252.11-1
ii  libpam0g   1.5.2-6
ii  libxcb11.15-1
ii  libxdmcp6  1:1.1.2-3
ii  lightdm-gtk-greeter [lightdm-greeter]  2.0.8-3

Versions of packages lightdm recommends:
ii  xserver-xorg  1:7.7+23

Versions of packages lightdm suggests:
ii  accountsservice  22.08.8-6
ii  upower   0.99.20-2
ii  xserver-xephyr   2:21.1.7-3

-- debconf information:
* shared/default-x-display-manager: lightdm
 lightdm/daemon_name: /usr/sbin/lightdm

Bug#1038160: googletest build fails on some 32bit architectures

[Marius Gripsgard]

Hi,


This is a bit of a ouch, many packages fails due to this.


I did some digging and found that the issues on i386 and armel are different

for i386 is a issue with printing floating point see [0]

for armel something upstream changed but the cause is unknown, i have 
reported this upstream see [1]



Not sure if this is "ok" for a short term fix, but i have attached a 
"fix" that skips the problematic test on these architectures.


[0] https://github.com/google/googletest/issues/4210

[1] https://github.com/google/googletest/issues/4285
From 550cad54dfe5c129346bc6f684664385558e361c Mon Sep 17 00:00:00 2001
From: Marius Gripsgard 
Date: Mon, 19 Jun 2023 02:13:59 +0200
Subject: [PATCH] debian/rules: Skip problematic test on armel and i386

---
 debian/rules | 10 ++
 1 file changed, 10 insertions(+)

diff --git a/debian/rules b/debian/rules
index 9ffbcc6..defc372 100755
--- a/debian/rules
+++ b/debian/rules
@@ -11,8 +11,18 @@ override_dh_auto_configure:
 
 override_dh_auto_test:
 ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
+# Skip printers tests on i386 due to upstream bug
+# See https://github.com/google/googletest/issues/4210
+ifneq (,$(filter $(DEB_HOST_ARCH_CPU),i386))
+   cd obj-* && ctest -E "googletest-printers-test" || (cat Testing/Temporary/LastTest.log; exit 1)
+# Skip gmock-matchers-misc on armel due to upstream bug
+# See https://github.com/google/googletest/issues/4285
+else ifneq (,$(filter $(DEB_HOST_ARCH),armel))
+cd obj-* && ctest -E "gmock-matchers-misc_test" || (cat Testing/Temporary/LastTest.log; exit 1)
+else
cd obj-* && ctest || (cat Testing/Temporary/LastTest.log; exit 1)
 endif
+endif
 
 override_dh_prep:
dh_prep
-- 
2.40.1

Bug#1038252: librsvg: FTBFS on i386: transform::tests::parses_transform_list, transform::tests::parses_valid_transform failed

[Simon McVittie]

Control: severity -1 important

On Sun, 18 Jun 2023 at 12:42:12 +0100, Simon McVittie wrote:
> On Fri, 16 Jun 2023 at 21:11:21 +0100, Simon McVittie wrote:
> > On Fri, 16 Jun 2023 at 21:00:13 +0200, Sebastian Ramacher wrote:
> > > https://buildd.debian.org/status/fetch.php?pkg=librsvg=i386=2.54.5%2Bdfsg-2=1686829500=0
> > > 
> > >  transform::tests::parses_transform_list stdout 
> > > thread 'transform::tests::parses_transform_list' panicked at 'assertion 
> > > failed: t1.y0.approx_eq(t2.y0, (epsilon, 1))', src/transform.rs:716:9
> > > 
> > >  transform::tests::parses_valid_transform stdout 
> > > thread 'transform::tests::parses_valid_transform' panicked at 'assertion 
> > > failed: t1.y0.approx_eq(t2.y0, (epsilon, 1))', src/transform.rs:716:9
> > 
> > This might be i387 excess precision resulting in rounding errors on i386
> > that differ from what happens on other architectures, or it might be
> > something unrelated.
> 
> Rebuilding 2.54.5+dfsg-1 in bookworm has similar behaviour, which means
> this is a behaviour change in build-dependency packages, rather than a
> result of a change in librsvg. One possible trigger is the upgrade of rustc
> 1.61 to 1.63.

I've uploaded 2.54.5+dfsg-3 with those two tests skipped on i386. It's
still a bug that we have to do that, and investigation by someone who
knows i386 quirks and/or Rust would be useful, but skipping those tests
makes this non-RC.

smcv

Bug#1038419: installation-reports: [arm64] Installation hangs on "Configuring grub-efi-arm64 (arm64)"

[Joel May]

Upon further investigation, this problem appears to be related to the kernel 
version (6.1.0-9-arm64).

After booting into my new Debian 12 installation, efibootmgr hung with no 
output when I attempted to delete a boot entry (`sudo efibootmgr -Bb 0006`).  I 
downloaded the Bullseye kernel deb package and downgraded to 5.10.0-23-arm64.  
Using the older kernel with Debian 12 allowed me to delete the boot entry with 
efibootmgr.

After a few seconds of efibootmgr hanging with kernel 6.1.0-9-arm64, dmesg 
starts logging:
[  220.565406] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[  220.571320] rcu: 31-...0: (1 GPs behind) idle=de3c/1/0x4000 
softirq=453/453 fqs=2582
[  220.580182]  (detected by 28, t=5255 jiffies, g=2537, q=452 ncpus=32)
[  220.580186] Task dump for CPU 31:
[  220.580188] task:kworker/u64:5   state:R  running task stack:0 
pid:378   ppid:2  flags:0x000a
[  220.580194] Workqueue: efi_rts_wq efi_call_rts
[  220.580203] Call trace:
[  220.580204]  __switch_to+0xf0/0x170
[  220.580211]  0x0
[  283.592504] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[  283.598416] rcu: 31-...0: (1 GPs behind) idle=de3c/1/0x4000 
softirq=453/453 fqs=10186
[  283.607364]  (detected by 18, t=21013 jiffies, g=2537, q=644 ncpus=32)
[  283.607368] Task dump for CPU 31:
[  283.607369] task:kworker/u64:5   state:R  running task stack:0 
pid:378   ppid:2  flags:0x000a
[  283.607376] Workqueue: efi_rts_wq efi_call_rts
[  283.607382] Call trace:
[  283.607383]  __switch_to+0xf0/0x170
[  283.607388]  0x0
[  346.620541] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[  346.626453] rcu: 31-...0: (1 GPs behind) idle=de3c/1/0x4000 
softirq=453/453 fqs=16943
[  346.635401]  (detected by 22, t=36771 jiffies, g=2537, q=1673 ncpus=32)
[  346.635404] Task dump for CPU 31:
[  346.635405] task:kworker/u64:5   state:R  running task stack:0 
pid:378   ppid:2  flags:0x000a
[  346.635411] Workqueue: efi_rts_wq efi_call_rts
[  346.635417] Call trace:
[  346.635419]  __switch_to+0xf0/0x170
[  346.635424]  0x0
[  363.463544] INFO: task khugepaged:188 blocked for more than 120 seconds.
[  363.470242]   Not tainted 6.1.0-9-arm64 #1 Debian 6.1.27-1
[  363.476069] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  363.483894] task:khugepaged  state:D stack:0 pid:188   ppid:2  
flags:0x0008
[  363.483901] Call trace:
[  363.483902]  __switch_to+0xf0/0x170
[  363.483909]  __schedule+0x340/0x940
[  363.483913]  schedule+0x58/0xf0
[  363.483916]  schedule_timeout+0x14c/0x180
[  363.483919]  __wait_for_common+0xd4/0x254
[  363.483922]  wait_for_completion+0x28/0x3c
[  363.483926]  __flush_work.isra.0+0x180/0x2dc
[  363.483931]  flush_work+0x18/0x2c
[  363.483934]  __lru_add_drain_all+0x1a0/0x260
[  363.483938]  lru_add_drain_all+0x1c/0x30
[  363.483941]  khugepaged+0xa4/0x9d0
[  363.483945]  kthread+0xe0/0xe4
[  363.483948]  ret_from_fork+0x10/0x20
[  363.483986] INFO: task efibootmgr:956 blocked for more than 120 seconds.
[  363.490681]   Not tainted 6.1.0-9-arm64 #1 Debian 6.1.27-1
[  363.496510] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  363.504335] task:efibootmgr  state:D stack:0 pid:956   ppid:955
flags:0x0004
[  363.504341] Call trace:
[  363.504342]  __switch_to+0xf0/0x170
[  363.504347]  __schedule+0x340/0x940
[  363.504351]  schedule+0x58/0xf0
[  363.504354]  schedule_timeout+0x14c/0x180
[  363.504357]  __wait_for_common+0xd4/0x254
[  363.504360]  wait_for_completion+0x28/0x3c
[  363.504363]  virt_efi_set_variable+0x134/0x1b0
[  363.504367]  efivar_set_variable_locked+0x7c/0xfc
[  363.504370]  efivar_entry_delete+0x5c/0xec [efivarfs]
[  363.504380]  efivarfs_unlink+0x28/0x5c [efivarfs]
[  363.504385]  vfs_unlink+0x124/0x300
[  363.504390]  do_unlinkat+0x19c/0x2c0
[  363.504393]  __arm64_sys_unlinkat+0x44/0x90
[  363.504396]  invoke_syscall+0x78/0x100
[  363.504401]  el0_svc_common.constprop.0+0x4c/0xf4
[  363.504405]  do_el0_svc+0x34/0xd0
[  363.504408]  el0_svc+0x34/0xd4
[  363.504411]  el0t_64_sync_handler+0xf4/0x120
[  363.504414]  el0t_64_sync+0x18c/0x190
[  409.648706] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[  409.654617] rcu: 31-...0: (1 GPs behind) idle=de3c/1/0x4000 
softirq=453/453 fqs=22740
[  409.663565]  (detected by 20, t=52529 jiffies, g=2537, q=1895 ncpus=32)
[  409.663568] Task dump for CPU 31:
[  409.663570] task:kworker/u64:5   state:R  running task stack:0 
pid:378   ppid:2  flags:0x000a
[  409.663576] Workqueue: efi_rts_wq efi_call_rts
[  409.663582] Call trace:
[  409.663583]  __switch_to+0xf0/0x170
[  409.663589]  0x0

Bug#1038610: firmware-bnx2x has an older version of broadcom drivers. This has been fixed for bookworm but not bullseye

[tomas347]

Package: firmware-bnx2x
Version: 20210315-3
Severity: minor
Tags: patch
X-Debbugs-Cc: tomas.leite.cas...@tecnico.ulisboa.pt

Dear Maintainer,


   * What led up to the situation?
   I found that my network card was crashing and eventually lost all
   network connectivity and the OS stopped recognizing the card. I
   initially had to replace the card but the same thing happened on
   bullseye.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 I manually installed bnx2x-e1-7.13.21.0.fw, bnx2x-e1h-7.13.21.0.fw,
 bnx2x-e2-7.13.21.0.fw, and now it works perfectly. This has been
 fixed for bookworm but not bullseye. There are many people with
 this issue and I found this workaround after many people debugged
 it.
   * What was the outcome of this action?
   Fixed my network card and I never had any more issues.
   * What outcome did you expect instead?
   Is it possible to update this package on bullseye?
   Note: I did not submit this report on the machine that had these
   issues, please disregard the kernel info from where this bug has been
   generated.

Thanks for your time,

Best regards,


Tomas Leite de Castro

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

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

Bug#1038609: POSIX1e ACL correctness fixes (0.32.1, 0.33.1)

[Robert Edmonds]

Package: bup
Version: 0.32-3
Severity: important
Tags: upstream
X-Debbugs-Cc: r...@defaultvalue.org

bup upstream has released two related point releases of bup (0.32.1,
0.33.1) which more correctly save and restore POSIX1e ACLs. bup 0.32
(oldstable) and bup 0.33 (stable, unstable) are currently affected and
should be updated to the point releases.

The upstream notes for 0.32.1 [0] and 0.33.1 [1] are reproduced below.

[0]: https://github.com/bup/bup/blob/main/note/0.32.1-from-0.32.md

[1]: https://github.com/bup/bup/blob/main/note/0.33.1-from-0.33.md

Notable changes in 0.32.1 since 0.32


Bugs


* POSIX1e ACLs should be restored more correctly now.

  Previously bup incorrectly restored default (`ACL_TYPE_DEFAULT`)
  ACLs as access acls (`ACL_TYPE_ACCESS`).  When both existed, it
  restored the access ACL first and then the default ACL as an access
  ACL.  Now, bup should restore each with the proper type.  This issue
  only affects saves created on platforms where bup currently supports
  ACLs, so presumably mostly just saves created on Linux since the
  current ACL support depends on non-standard functions like
  `acl_extended(3)`.

  There is one remaining issue, which isn't fixed in this release, but
  is fixed in 0.33.1 (because fixing it here could create saves that
  are backward incompatible with 0.33).

  The problem is that in this version and older versions, bup stores
  ACLs in the `acl_to_any_text(3)` format with a newline delimiter,
  when the standard (and `acl_from_text(3)` which restore depends on)
  requires commas.  This may cause restores that include ACLs (likely
  only those from Linux right now) to fail on some platforms
  (e.g. Cygwin).

Notable changes in 0.33.1 since 0.33


Bugs


* POSIX1e ACLs should be restored correctly now.  Previously there
  were two problems.

  First, bup incorrectly restored default (`ACL_TYPE_DEFAULT`) ACLs as
  access acls (`ACL_TYPE_ACCESS`).  When both existed, it restored the
  access ACL first and then the default ACL as an access ACL.  Now,
  bup should restore each with the proper type.  This issue only
  affects saves created on platforms where bup currently supports
  ACLs, so presumably mostly just saves created on Linux since the
  current ACL support depends on non-standard functions like
  `acl_extended(3)`.

  Second, bup stored ACLs in the `acl_to_any_text(3)` format with a
  newlne delimiter, when the standard (and `acl_from_text(3)` which
  restore depends on) requires commas.  Now bup uses commas, and
  translates previously created saves during restore when possible.
  If a previously created ACL entry contains a comma, then bup will
  give up, report an error, and skip it.  If nothing else, this could
  cause restores of relevant saves to fail on some platforms.

Bug#1037524: libortp: still missing -lbctoolbox (was: Bug#994437: fixed in ortp 1:5.0.37-1)

[Frank Heckenbach]

> > You added a "Requires.private" in the .pc, but that doesn't help.
> > "Requires" is required (sic!) because a program that links to ortp
> > apparently must also link to bctoolbox.
> 
> Dude, did you not see that the string "bctbx_set_log_level_mask" does
> not occur anywhere in your program?  And that as a consequence the
> error message does not really make any sense?  Because if you did see
> it then you could have said something.

Sorry, I did suggest to add it as "Requires:" (not private) and
added a simple demo program to check it.

> It was not immediately obvious to me that ortp_set_log_level_mask() in
> the distant past was provided by libortp.so, but then replaced with
> bctbx_set_log_level_mask() from libbctoolbox.so and the name change
> papered over with a macro (instead of a wrapper function which would
> have preserved the old linkage relationship).

I didn't know these details and history either (my code using the
library was a few years old then, so I didn't remember all of it at
the time), just saw the error message and found that adding
-lbctoolbox fixed it.

> Anyway, I'll fix it when preparing 1:5.2.x which I'll try to get to in
> the coming weeks.

Thanks.

Bug#1038608: rust-coretuils: FTBFS: error: no matching package named `remove_dir_all` found

[Sebastian Ramacher]

Source: rust-coreutils
Version: 0.0.17-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=rust-coreutils=amd64=0.0.17-3=1686775495=0

cargo build  --features "arch base32 base64 basename basenc cat chcon chgrp 
chmod chown chroot cksum comm cp csplit cut date dd df dir dircolors dirname du 
echo env expand expr factor false fmt fold groups hashsum head hostid hostname 
id install join kill link ln logname ls mkdir mkfifo mknod mktemp more mv nice 
nl nohup nproc numfmt od paste pathchk pinky pr printenv printf ptx pwd 
readlink realpath relpath rm rmdir runcon seq shred shuf sleep sort split stat 
stdbuf sum sync tac tail tee test timeout touch tr true truncate tsort tty 
uname unexpand uniq unlink uptime users vdir wc who whoami yes" --release 
--no-default-features
error: no matching package named `remove_dir_all` found
location searched: registry `crates-io`
required by package `uu_rm v0.0.17 (/<>/src/uu/rm)`
make[2]: *** [GNUmakefile:283: build-coreutils] Error 101

Cheers
-- 
Sebastian Ramacher

Bug#1038317: nautilus: new tab with ctrl+t keyboard set completely gray window

[Sergio Zamora]

Hi Simon, good day


*# Opening nautilus*

Hint: You are currently not seeing messages from other users and the system.
  Users in groups 'adm', 'systemd-journal' can see all messages.
  Pass -q to turn off this notice.
jun 18 16:44:52 debian gnome-character[12346]: JS LOG: Characters 
Application started
jun 18 16:45:02 debian gnome-character[12346]: JS LOG: Characters 
Application exiting
jun 18 16:46:52 debian dbus-daemon[2486]: [session uid=1000 pid=2486] 
Failed to activate service 'org.gnome.Weather.BackgroundService': timed 
out (service_start_timeout=12ms)
jun 18 16:48:20 debian dbus-daemon[2486]: [session uid=1000 pid=2486] 
Activating service name='org.gnome.Console' requested by ':1.44' 
(uid=1000 pid=2758 comm="/usr/bin/gnome-shell")
jun 18 16:48:20 debian dbus-daemon[2486]: [session uid=1000 pid=2486] 
Successfully activated service 'org.gnome.Console'
jun 18 16:48:20 debian systemd[2445]: Started 
vte-spawn-7dd1f5d2-31d9-4a33-8cc5-9d3b5036179b.scope - VTE child process 
13418 launched by kgx process 13393.
jun 18 16:48:20 debian gnome-shell[2758]: Window manager warning: Buggy 
client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x224
jun 18 16:48:21 debian gnome-shell[2758]: Can't update stage views actor 
[:0x55a4ac377450] is on because it needs an 
allocation.
jun 18 16:48:21 debian gnome-shell[2758]: Can't update stage views actor 
[:0x55a4ac0e3e00] is on because it needs 
an allocation.






*# Clicking/opening/mounting nextcloud files account option at left panel.**
**#     After a few seconds it lists all remote content ok.*

jun 18 16:44:52 debian gnome-character[12346]: JS LOG: Characters 
Application started
jun 18 16:44:53 debian systemd[2445]: Started 
app-gnome-org.keepassxc.KeePassXC-12503.scope - Application launched by 
gnome-shell.
jun 18 16:45:02 debian gnome-character[12346]: JS LOG: Characters 
Application exiting
jun 18 16:46:52 debian dbus-daemon[2486]: [session uid=1000 pid=2486] 
Failed to activate service 'org.gnome.Weather.BackgroundService': timed 
out (service_start_timeout=12ms)
jun 18 16:48:20 debian dbus-daemon[2486]: [session uid=1000 pid=2486] 
Activating service name='org.gnome.Console' requested by ':1.44' 
(uid=1000 pid=2758 comm="/usr/bin/gnome-shell")
jun 18 16:48:20 debian dbus-daemon[2486]: [session uid=1000 pid=2486] 
Successfully activated service 'org.gnome.Console'
jun 18 16:48:20 debian systemd[2445]: Started 
vte-spawn-7dd1f5d2-31d9-4a33-8cc5-9d3b5036179b.scope - VTE child process 
13418 launched by kgx process 13393.
jun 18 16:48:20 debian gnome-shell[2758]: Window manager warning: Buggy 
client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x224
jun 18 16:48:21 debian gnome-shell[2758]: Can't update stage views actor 
[:0x55a4ac377450] is on because it needs an 
allocation.
jun 18 16:48:21 debian gnome-shell[2758]: Can't update stage views actor 
[:0x55a4ac0e3e00] is on because it needs 
an allocation.
jun 18 16:50:04 debian tracker-miner-f[2542]: g_str_has_suffix: 
assertion 'str != NULL' failed
jun 18 16:50:04 debian tracker-miner-f[2542]: g_str_has_suffix: 
assertion 'str != NULL' failed
jun 18 16:50:10 debian gnome-shell[2758]: Window manager warning: Buggy 
client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x6009b4






*# When all remote folders/files contents are fully loaded on current 
window,**
**#    went to a local folder using same window and left panel ( leaving 
previous remote files view)**

**#        and then ctrl+t for a new tab**
**# _It Freeze_: Entire gray window. Only gtk borders.!**!
**# Waited for 1 minute if something happens*

jun 18 16:51:11 debian gnome-text-edit[8707]: Trying to snapshot 
GtkGizmo 0x55c4cdd63860 without a current allocation
jun 18 16:51:26 debian nautilus[8573]: Trying to snapshot AdwFlap 
0x562c079ca670 without a current allocation
jun 18 16:51:33 debian nautilus[8573]: Trying to snapshot AdwFlap 
0x562c079ca670 without a current allocation
jun 18 16:51:37 debian nautilus[8573]: Trying to snapshot AdwFlap 
0x562c079ca670 without a current allocation
jun 18 16:51:37 debian nautilus[8573]: Trying to snapshot AdwFlap 
0x562c079ca670 without a current allocation
jun 18 16:51:37 debian nautilus[8573]: Trying to snapshot AdwFlap 
0x562c079ca670 without a current allocation
jun 18 16:51:37 debian nautilus[8573]: Trying to snapshot AdwFlap 
0x562c079ca670 without a current allocation
jun 18 16:51:37 debian nautilus[8573]: Trying to snapshot AdwFlap 
0x562c079ca670 without a current allocation
jun 18 16:51:37 debian nautilus[8573]: Trying to snapshot AdwFlap 
0x562c079ca670 without a current allocation
jun 18 16:51:37 debian nautilus[8573]: Trying to snapshot AdwFlap 
0x562c079ca670 without a current allocation
jun 18 16:51:37 debian nautilus[8573]: Trying to snapshot AdwFlap 
0x562c079ca670 without a current allocation
jun 18 16:51:37 debian nautilus[8573]: Trying to snapshot AdwFlap 
0x562c079ca670 without a current allocation
jun 

Bug#1017613: kwin/plasma still crashing with latest meta (kubuntu)

[Michael McCallum]

I don't think that mesa upgrade changed anything, I still get the
hang regularly. Restarting plasmashell sorts it out.
Ø dpkg -l | grep mesa
ii  libegl-mesa0:amd6423.0.2-1ubuntu1
amd64free implementation of the EGL API
-- Mesa vendor library
ii  libgl1-mesa-dri:amd64 23.0.2-1ubuntu1
amd64free implementation of the OpenGL
API -- DRI modules
ii  libglapi-mesa:amd64   23.0.2-1ubuntu1
amd64free implementation of the GL API
-- shared library
ii  libglu1-mesa:amd649.0.2-1.1
  amd64Mesa OpenGL utility library
(GLU)
ii  libglx-mesa0:amd6423.0.2-1ubuntu1
amd64free implementation of the OpenGL
API -- GLX vendor library
ii  mesa-utils8.5.0-1
amd64Miscellaneous Mesa
utilities -- symlinks
ii  mesa-utils-bin:amd64  8.5.0-1
amd64Miscellaneous Mesa
utilities -- native applications
ii  mesa-va-drivers:amd64 23.0.2-1ubuntu1
amd64Mesa VA-API video acceleration
drivers
ii  mesa-vdpau-drivers:amd64  23.0.2-1ubuntu1
amd64Mesa VDPAU video acceleration
drivers
ii  mesa-vulkan-drivers:amd64 23.0.2-1ubuntu1
amd64Mesa Vulkan graphics drivers

Bug#1038440: debian-cd: debian-12.0.0-amd64-netinst.iso is too big for a CD

[Cyril Brulebois]

Claude Heiland-Allen  (2023-06-18):
> I'm not sure if I will actually need a CD,
> (refurbishing someone's old laptop,
> I don't know yet if it will boot from USB stick or not),
> but if it can only boot from CD I will have to
> install Bullseye (whose netinst does fit on a CD)
> and then upgrade, which is not ideal.

https://salsa.debian.org/installer-team/debian-installer/-/issues/3 has:

> Revisit firmware packages included in the netinst (amd64 is 738M for
> 12.0.0): at least nvidia stuff wasn't planned in the beginning, and
> could be removed.


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


signature.asc
Description: PGP signature

Bug#1038271: linux-image-6.1.0-9-amd64: Logitech trackpad T651 doesn't work anymore

[Diederik de Haas]

Control: forwarded -1 
https://lore.kernel.org/all/20230617230957.6mx73th4blv7o...@glandium.org/
Control: tag -1 upstream

On Sunday, 18 June 2023 02:14:22 CEST Mike Hommey wrote:
> > > I was able to build the relevant module only. The regression comes from
> > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/
> > > ?id=337c3624bcb008f92bab38c8fc4cdf97ae5313a2> 
> > I sent a patch upstream, but it's not showing up on the archives yet.
> > I'll update with a link when I have one.
> 
> Here we go:
> https://patchwork.kernel.org/project/linux-input/patch/20230617230957.6mx73t
> h4blv7o...@glandium.org/

That was awesome :) Updated bug metadata accordingly

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

Bug#1038607: digikam: Creating new tag in captions menu reports it already exists

[Matthieu LAPADU-HARGUES]

Package: digikam
Version: 4:7.9.0-1+b2
Severity: minor

Dear Maintainer,

Using "captions" menu in order to complete IPTC and XMP metadata, I had to
create a new tag in the existing list.
After typing the word and validating with "enter", a popup windows appeared
with a warning about already created and existing tag.
But it was really a new tag because not proposed by the auto-completing menu.
After acknowledging the warning, the tag had been created.
It looks like a kind of "false postive warning" always active for each new tag.


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

Kernel: Linux 6.1.0-9-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr:en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages digikam depends on:
ii  digikam-data  4:7.9.0-1
ii  digikam-private-libs  4:7.9.0-1+b2
ii  libc6 2.36-9
ii  libgcc-s1 12.2.0-14
ii  libkf5configcore5 5.103.0-2
ii  libkf5coreaddons5 5.103.0-1
ii  libkf5i18n5   5.103.0-1
ii  libmagick++-6.q16-8   8:6.9.11.60+dfsg-1.6
ii  libqt5core5a  5.15.8+dfsg-11
ii  libqt5gui55.15.8+dfsg-11
ii  libqt5sql55.15.8+dfsg-11
ii  libqt5sql5-mysql  5.15.8+dfsg-11
ii  libqt5sql5-sqlite 5.15.8+dfsg-11
ii  libqt5widgets55.15.8+dfsg-11
ii  libstdc++612.2.0-14
ii  perl  5.36.0-7

Versions of packages digikam recommends:
ii  chromium [www-browser] 114.0.5735.133-1~deb12u1
ii  ffmpegthumbs   4:22.12.3-1
ii  firefox-esr [www-browser]  102.12.0esr-1~deb12u1
ii  konqueror [www-browser]4:22.12.3-1
ii  lynx [www-browser] 2.9.0dev.12-1

Versions of packages digikam suggests:
ii  breeze-icon-theme  4:5.103.0-1
pn  digikam-doc
ii  systemsettings 4:5.27.5-2

-- no debconf information

Bug#1038603: gcc-12 but - forgot one detail

[Jeronimo Pellegrini]

I forgot: the steps to reproduce are these

git clone https://github.com/darktable-org/darktable.git
git submodule update
cd darktable
./build.sh --prefix /usr/local --build-type Release

but of course, one needs the darktable dependencies before --

apt-get build-dep darktable

J.

Bug#1038068: linux-image-6.3.0-1-amd64: vlc+dvb freezes when changing channels (systemd-shutdown hangs then due to VLC)

[Diederik de Haas]

Control: upstream fixed-upstream
Control: forcemerge -1 1038593
Control: forcemerge -1 1038595

On Fri Jun 16, 2023 at 6:53 PM CEST, Holger Schröder wrote:
> Found this patch which probably fixes the problem.
> https://github.com/fullstory/linux-aptosid/blob/master/debian/patches/bugfix/
0001-Revert-media-dvb-core-Fix-use-after-free-on-race-con.patch

The fix (a revert) is queued up for the next 6.3 version:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/
commit/queue-6.3/revert-media-dvb-core-fix-use-after-free-on-race-con.patch?
id=c9f3dc7168a7fc2d7c7ff1ea1249976476812f63


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

Bug#1038343: fim: Depends on SDL 1.2

[Rafael Laboissière]

* Simon McVittie  [2023-06-18 17:10]:


On Sat, 17 Jun 2023 at 21:11:25 +0200, Rafael Laboissière wrote:

Thanks for this bug report. I forwarded it upstream and I am also sending
this message with Cc to the upstream author.


Thanks. In the meantime, please could you check whether fim works as 
intended with libsdl1.2-compat-shim, which is meant to be a drop-in 
replacement? I'm trying to track whether there are any blockers to 
replacing "classic" SDL 1.2.


The package builds fine against libsdl1.2-compat-dev on my sid amd64 
system. All tests also passed, but I am not sure this would be enough. I 
would rather let the upstream author have the final word, but if you 
think I should upload a new version of the package with that 
build-dependency, please tell me.


Best,

Rafael Laboissière

Bug#1038606: tortoisehg: Depends: mercurial (< 6.4~) but 6.4.4-1 is to be installed

[Adrian Bunk]

Package: tortoisehg
Version: 6.3.1-1
Severity: serious
Tags: trixie sid

The following packages have unmet dependencies:
 tortoisehg : Depends: mercurial (< 6.4~) but 6.4.4-1 is to be installed

Bug#1038605: bookworm-pu: package mate-power-manager/1.26.0-2+deb12u1

[Mike Gabriel]

Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: mate-power-mana...@packages.debian.org
Control: affects -1 + src:mate-power-manager

[ Reason ]
In mate-power-manager 1.26.1 two memory leaks have been fixed recently.
The patches for this shall be provided for mate-power-manager in Debian
bookworm.

[ Impact ]
Memory management improved for MATE users.

[ Tests ]
Code review, installation + runtime smoketests.

[ Risks ]
MATE power statistics and preferences could be affected by a regression.

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

[ Changes ]

+  * debian/patches:
++ Add 0002_gpm-statistics-fix-memory-leak.patch (gpm-prefs: fix memory 
leak)
+  and 0003_gpm-prefs-fix-memory-leak.patch (gpm-statistics: fix memory
+  leak). Cherry-picked and simplified from v1.26.1. (Closes: #1038444).
++ Document simplification in patch 0002_gpm-statistics-fix-memory-
+  leak.patch.
++ Trivial rebase of 0001_add-gaming-input-devices.patch.

[ Other info ]
None
diff -Nru mate-power-manager-1.26.0/debian/changelog 
mate-power-manager-1.26.0/debian/changelog
--- mate-power-manager-1.26.0/debian/changelog  2022-04-06 22:43:14.0 
+0200
+++ mate-power-manager-1.26.0/debian/changelog  2023-06-18 21:40:10.0 
+0200
@@ -1,3 +1,15 @@
+mate-power-manager (1.26.0-2+deb12u1) bookworm; urgency=medium
+
+  * debian/patches:
++ Add 0002_gpm-statistics-fix-memory-leak.patch (gpm-prefs: fix memory 
leak)
+  and 0003_gpm-prefs-fix-memory-leak.patch (gpm-statistics: fix memory
+  leak). Cherry-picked and simplified from v1.26.1. (Closes: #1038444).
++ Document simplification in patch 0002_gpm-statistics-fix-memory-
+  leak.patch.
++ Trivial rebase of 0001_add-gaming-input-devices.patch.
+
+ -- Mike Gabriel   Sun, 18 Jun 2023 21:40:10 +0200
+
 mate-power-manager (1.26.0-2) unstable; urgency=medium
 
   [ Martin Wimpress ]
diff -Nru 
mate-power-manager-1.26.0/debian/patches/0001_add-gaming-input-devices.patch 
mate-power-manager-1.26.0/debian/patches/0001_add-gaming-input-devices.patch
--- 
mate-power-manager-1.26.0/debian/patches/0001_add-gaming-input-devices.patch
2022-04-06 22:42:39.0 +0200
+++ 
mate-power-manager-1.26.0/debian/patches/0001_add-gaming-input-devices.patch
2023-06-18 21:37:17.0 +0200
@@ -1,6 +1,3 @@
-diff --git a/data/icons/scalable/status/gpm-gaming-input-000.svg 
b/data/icons/scalable/status/gpm-gaming-input-000.svg
-new file mode 100644
-index ..fdcaa77f
 --- /dev/null
 +++ b/data/icons/scalable/status/gpm-gaming-input-000.svg
 @@ -0,0 +1,507 @@
@@ -511,9 +508,6 @@
 +  
 +
-diff --git a/data/icons/scalable/status/gpm-gaming-input-020.svg 
b/data/icons/scalable/status/gpm-gaming-input-020.svg
-new file mode 100644
-index ..d5e8f506
 --- /dev/null
 +++ b/data/icons/scalable/status/gpm-gaming-input-020.svg
 @@ -0,0 +1,792 @@
@@ -1309,9 +1303,6 @@
 +
 +  
 +
-diff --git a/data/icons/scalable/status/gpm-gaming-input-040.svg 
b/data/icons/scalable/status/gpm-gaming-input-040.svg
-new file mode 100644
-index ..4a7ae617
 --- /dev/null
 +++ b/data/icons/scalable/status/gpm-gaming-input-040.svg
 @@ -0,0 +1,673 @@
@@ -1988,9 +1979,6 @@
 +
 +  
 +
-diff --git a/data/icons/scalable/status/gpm-gaming-input-060.svg 
b/data/icons/scalable/status/gpm-gaming-input-060.svg
-new file mode 100644
-index ..901ad0f2
 --- /dev/null
 +++ b/data/icons/scalable/status/gpm-gaming-input-060.svg
 @@ -0,0 +1,521 @@
@@ -2515,9 +2503,6 @@
 +  
 +
-diff --git a/data/icons/scalable/status/gpm-gaming-input-080.svg 
b/data/icons/scalable/status/gpm-gaming-input-080.svg
-new file mode 100644
-index ..5d209e23
 --- /dev/null
 +++ b/data/icons/scalable/status/gpm-gaming-input-080.svg
 @@ -0,0 +1,673 @@
@@ -3194,9 +3179,6 @@
 +
 +  
 +
-diff --git a/data/icons/scalable/status/gpm-gaming-input-100.svg 
b/data/icons/scalable/status/gpm-gaming-input-100.svg
-new file mode 100644
-index ..b0201af3
 --- /dev/null
 +++ b/data/icons/scalable/status/gpm-gaming-input-100.svg
 @@ -0,0 +1,501 @@
@@ -3701,11 +3683,9 @@
 +  
 +
-diff --git a/src/gpm-statistics.c b/src/gpm-statistics.c
-index ae144cb8..e87651bb 100644
 --- a/src/gpm-statistics.c
 +++ b/src/gpm-statistics.c
-@@ -894,6 +894,9 @@ gpm_stats_add_device (UpDevice *device, GPtrArray *devices)
+@@ -895,6 +895,9 @@
if ((vendor != NULL && strlen(vendor) != 0) && (model != NULL && 
strlen(model) != 0)) {
label = g_strdup_printf ("%s %s", vendor, model);
}
@@ -3715,11 +3695,9 @@
else {
label = g_strdup_printf ("%s", 
gpm_device_kind_to_localised_string (kind, 1));
}
-diff --git a/src/gpm-tray-icon.c b/src/gpm-tray-icon.c
-index 258c2424..9f5fe388 

Bug#1038604: cinnamon-session from command line (multi-user.target) NOT start Cinnamon X session

[kachatelq]

Package: cinnamon
Version: 5.6.8-1
Severity: normal
X-Debbugs-Cc: kachat...@hotmail.com

I like boot my computer to multi-user.target ( it is command line )
and I like Cinnamon desktop environment.
But I can NOT to start Cinnamon desktop environment from command line :
   root@ferrum:~# cinnamon-session
   **(cinnamon-session:51470):WARNING**:Cannot open display:
This notification is the single result of command cinnavon-session,
Cinnamon X session does NOT start !
. . . This does NOT depend from existence or value
of the DISPLAY environment variable.


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

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

Versions of packages cinnamon depends on:
ii  cinnamon-common  5.6.8-1
ii  cinnamon-control-center  5.6.1-1
ii  cinnamon-desktop-data5.6.1-1
ii  cinnamon-screensaver 5.6.3-1
ii  cinnamon-session 5.6.0-1
ii  cinnamon-settings-daemon 5.6.2-2
ii  cjs  5.6.0-1
ii  cups-pk-helper   0.2.6-1+b1
ii  dbus 1.14.6-1
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
ii  gir1.2-accountsservice-1.0   22.08.8-6
ii  gir1.2-caribou-1.0   0.4.21-8
ii  gir1.2-cmenu-3.0 5.6.0-1
ii  gir1.2-cvc-1.0   5.6.1-1
ii  gir1.2-ecal-2.0  3.46.4-2
ii  gir1.2-edataserver-1.2   3.46.4-2
ii  gir1.2-gdkpixbuf-2.0 2.42.10+dfsg-1+b1
ii  gir1.2-gkbd-3.0  3.28.1-1
ii  gir1.2-glib-2.0  1.74.0-3
ii  gir1.2-gnomedesktop-3.0  43.2-2
ii  gir1.2-goa-1.0   3.46.0-1
ii  gir1.2-gsound-1.01.0.3-2
ii  gir1.2-gtk-3.0   3.24.37-2
ii  gir1.2-ical-3.0  3.0.16-1+b1
ii  gir1.2-keybinder-3.0 0.3.2-1.1
ii  gir1.2-nemo-3.0  5.6.4-1
ii  gir1.2-nm-1.01.42.4-1
ii  gir1.2-nma-1.0   1.10.6-1
ii  gir1.2-notify-0.70.8.1-1
ii  gir1.2-pango-1.0 1.50.12+ds-1
ii  gir1.2-polkit-1.0122-3
ii  gir1.2-soup-2.4  2.74.3-1
ii  gir1.2-timezonemap-1.0   0.4.6-3
ii  gir1.2-upowerglib-1.00.99.20-2
ii  gir1.2-xapp-1.0  2.4.2-3
ii  gkbd-capplet 3.28.1-1
ii  gnome-backgrounds43.1-1
ii  gnome-themes-extra   3.28-2
ii  gsettings-desktop-schemas43.0-1
ii  iso-flags-png-320x2401.0.2-2
ii  libatk-bridge2.0-0   2.46.0-5
ii  libatk1.0-0  2.46.0-5
ii  libc62.36-9
ii  libcairo21.16.0-7
ii  libcinnamon-desktop4 5.6.1-1
ii  libcinnamon-menu-3-0 5.6.0-1
ii  libcjs0  5.6.0-1
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libgirepository-1.0-11.74.0-3
ii  libgles2 1.6.0-1
ii  libglib2.0-0 2.74.6-2
ii  libglib2.0-bin   2.74.6-2
ii  libgstreamer1.0-01.22.0-2
ii  libgtk-3-0   3.24.37-2
ii  libmuffin0   5.6.4-1
ii  libpango-1.0-0   1.50.12+ds-1
ii  libpangocairo-1.0-0  1.50.12+ds-1
ii  libx11-6 2:1.8.4-2
ii  libxapp1 2.4.2-3
ii  libxfixes3   1:6.0.0-2
ii  libxml2  2.9.14+dfsg-1.2
ii  mesa-utils   8.5.0-1
ii  muffin   5.6.4-1
ii  nemo 5.6.4-1
ii  network-manager-gnome1.30.0-2
ii  pkexec   122-3
ii  policykit-1-gnome0.105-8
ii  psmisc   23.6-1
ii  python3

Bug#1038603: gcc-12 was compiled with BMI instructions, which seems to it sometimes crashing in older CPUs

[Jeronimo Pellegrini]

Package: gcc-12
Version: 12.3.0-4
Severity: important

Dear Maintainer,

It seems that the Debian package of GCC 12 was compiled with BMI1 (and
BMI2) instructions (perhaps the wrong -march setting is being
used?). At least apparently (see below). Those are relatively new
instruction sets, and are not supported by older CPUs.

* What led up to the situation?

Compiling darktable from the git repository (I am a darktable
translator, so installing the pre-packaged version doesn't work for
me). I noticed another darktable submitted an issue to darktable:

https://github.com/darktable-org/darktable/issues/14701

and realized it was exactly the same error that occurred when I tried
to compile darktable on my machine.

* What exactly did you do (or not do) that was effective (or
  ineffective)?

Just cloned and tried to compile darktable:

git clone https://github.com/darktable-org/darktable.git
git submodule update
cd darktable
./build.sh --prefix /usr/local --build-type Release

* What was the outcome of this action?

Illegal instruction while compiling:

[ 20%] Building C object bin/CMakeFiles/lib_darktable.dir/common/iop_order.c.o
during GIMPLE pass: graphite
/home/magnus/camera2/test2/darktable-debian12/darktable/src/common/iop_order.c: 
In function ‘_insert_before.isra’:
/home/magnus/camera2/test2/darktable-debian12/darktable/src/common/iop_order.c:404:15:
 internal compiler error: Illegal instruction
  404 | static GList *_insert_before(GList *iop_order_list,
  |   ^~
0x7f1fc963ef8f ???
./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0
0x7f1fc962a189 __libc_start_call_main
../sysdeps/nptl/libc_start_call_main.h:58
0x7f1fc962a244 __libc_start_main_impl
../csu/libc-start.c:381
Please submit a full bug report, with preprocessed source (by using 
-freport-bug).
Please include the complete backtrace with any bug report.
See  for instructions.
make[2]: *** [bin/CMakeFiles/lib_darktable.dir/build.make:726: 
bin/CMakeFiles/lib_darktable.dir/common/iop_order.c.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:2473: bin/CMakeFiles/lib_darktable.dir/all] 
Error 2
make: *** [Makefile:156: all] Error 2


* What outcome did you expect instead?

Full compilation without problems.

Some more info:

- Clang compiles darktable without problems
- Could not test gcc-11, because 12 is the minimum version that
  the darktable build script accepts
- The darktable issue has some more information on this, incuding
  some guided debugging (a darktable maintainer helped me and
  the issue submitter find the exact problem, which was BMI1 and
  BMI2 instructions being executed during compilation):
  https://github.com/darktable-org/darktable/issues/14701

For me the illegal instruction was blsr, and for the issue submitter,
it was shlx (see the issue).

My CPU is an AMD FX-8320E. The original issue submitter had an Intel
i7-3770K CPU.

The illegal instruction is in 'isl_hash_table_init'. Now, the strange
part is that

grep -r isl_hash_table_init *

inside gcc sources doesn't return anything. But as the original
darktable issue reporter mentioned, recompiling GCC manually seems to
fix the issue. For lack of better information, and since recompiling
gcc seems to have fixed the issue for one person, I am submitting this
bug to the gcc-12 package. Sorry if it's not the correct place.

Please tell me if there is anything else I can do to help.

Thank you!
Jeronimo

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

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

Versions of packages gcc-12 depends on:
ii  binutils   2.40.50.20230611-2
ii  cpp-12 12.3.0-4
ii  gcc-12-base12.3.0-4
ii  libc6  2.36-9
ii  libcc1-0   13.1.0-6
ii  libgcc-12-dev  12.3.0-4
ii  libgcc-s1  13.1.0-6
ii  libgmp10   2:6.2.1+dfsg1-1.1
ii  libisl23   0.26-2
ii  libmpc31.3.1-1
ii  libmpfr6   4.2.0-1
ii  libstdc++6 13.1.0-6
ii  libzstd1   1.5.4+dfsg2-5
ii  zlib1g 1:1.2.13.dfsg-1

Versions of packages gcc-12 recommends:
ii  libc6-dev  2.36-9

Versions of packages gcc-12 suggests:
ii  gcc-12-doc   12.2.0-1
pn  gcc-12-locales   
ii  gcc-12-multilib  12.3.0-4

-- no debconf information

Bug#1038602: paraview: Stop using netcdf-cxx-legacy

[Bas Couwenberg]

Source: paraview
Version: 5.11.0+dfsg-1
Severity: important
Tags: patch
User: debian-...@lists.debian.org
Usertags: netcdf-cxx-legacy-rm

Dear Maintainer,

Your package uses netcdf-cxx-legacy which is dead upstream and will be removed 
during the trixie development cycle.

The attached patch only drops the build dependency, as your package doesn't 
actually link to netcdf-cxx-legacy.

Kind Regards,

Bas
diff -Nru paraview-5.11.0+dfsg/debian/changelog 
paraview-5.11.0+dfsg/debian/changelog
--- paraview-5.11.0+dfsg/debian/changelog   2023-01-21 12:41:21.0 
+0100
+++ paraview-5.11.0+dfsg/debian/changelog   2023-06-18 16:07:08.0 
+0200
@@ -1,3 +1,10 @@
+paraview (5.11.0+dfsg-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Stop using netcdf-cxx-legacy.
+
+ -- Bas Couwenberg   Sun, 18 Jun 2023 16:07:08 +0200
+
 paraview (5.11.0+dfsg-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru paraview-5.11.0+dfsg/debian/control 
paraview-5.11.0+dfsg/debian/control
--- paraview-5.11.0+dfsg/debian/control 2023-01-21 12:41:21.0 +0100
+++ paraview-5.11.0+dfsg/debian/control 2023-06-18 16:06:56.0 +0200
@@ -55,7 +55,6 @@
libgl2ps-dev,
libeigen3-dev,
libnetcdf-dev (>= 1:4.9.0),
-   libnetcdf-cxx-legacy-dev,
libjsoncpp-dev,
libglew-dev,
libxdmf-dev,

Bug#1038601: tcpspy.8: remarks and editing fixes for the manual

[Bjarni Ingi Gislason]

Package: tcpspy
Version: 1.7d-15
Severity: minor
Tags: patch

Dear Maintainer,

here are some remarks and fixes for the manual.

Input file is tcpspy.8

Output from "mandoc  -T lint tcpspy.8":

mandoc: tcpspy.8:3:51: STYLE: whitespace at end of input line
mandoc: tcpspy.8:52:2: WARNING: skipping paragraph macro: PP empty
mandoc: tcpspy.8:117:2: WARNING: skipping paragraph macro: PP empty
mandoc: tcpspy.8:176:81: STYLE: input text line longer than 80 bytes: a default 
mask with ...
mandoc: tcpspy.8:187:71: STYLE: whitespace at end of input line
mandoc: tcpspy.8:194:73: STYLE: whitespace at end of input line
mandoc: tcpspy.8:260:85: STYLE: input text line longer than 80 bytes: tcpspy 
\-e 'not radd...

###

Remove space characters at the end of lines.

Use "git apply ... --whitespace=fix" to fix extra space issues, or use
global configuration "core.whitespace".

3:.\" Copyright (c) 2000, 2001, 2002 Tim J. Robbins. 
5:.\" 
16:.\" 
187:True if the full filename (including directory) of the executable that 
194:The pattern "" (an empty string) matches connections created/accepted by 

#

Reduce space between words.

202:Expressions (including the  comparisons listed above) may be joined together

#

Use the correct macro for the font change of a single argument or
split the argument into two.

135:.BI ip
138:.BI ip6

#

Change a HYPHEN-MINUS (code 0x55, 2D) to a minus (\-), if in front of a
name for an option.

34:.RB [ "-dp" ]
35:.RB [ "-e"
37:.RB [ "-f"
39:.RB [ "-F"
41:.RB [ "-I"
43:.RB [ "-U"
45:.RB [ "-G"
55:.BI -e " 'rule'"
60:.BI -f " rulefile"
67:.B -e
69:.B -f
72:.BI -F " facility"
79:.BI -I " interval"
89:.BI -U " user"
94:.BI -G " group"
99:.B -U
101:.B -G
104:.B -d
109:.B -p
120:.B -e
155:.I -high
198:.B -p

#

Wrong distance between sentences.

  Separate the sentences and subordinate clauses; each begins on a new
line.  See man-pages(7) ("Conventions for source file layout") and
"info groff" ("Input Conventions").

  The best procedure is to always start a new sentence on a new line,
at least, if you are typing on a computer.

Remember coding: Only one command ("sentence") on each (logical) line.

E-mail: Easier to quote exactly the relevant lines.

Generally: Easier to edit the sentence.

Patches: Less unaffected text.

  The amount of space between sentences in the output can then be
controlled with the ".ss" request.

50:syslog. The following information is logged: username, local address and 
port,
56:Log only connections matching the specified rule. Rule syntax is outlined
57:below. If this option is specified more than once, connections matching any
58:of the specified rules are logged. You should quote the rule, as shown above.
63:Each rule is on a new line. The `#' character may be used to add comments;
75:instead of the compile-time default setting. See the
82:milliseconds, instead of the default of 1000 ms. Connections that last less
156:is used, low is assumed to be 0. It is an error to omit both
175:AND of the local address of the connection and "mask". If no mask is 
specified,
176:a default mask with all bits set (255.255.255.255) is used. The CIDR type 
netmask
177:is also possible. With IPv6 only a prefix length netmask is allowed, and the
178:length defaults to 128. Depending on the address family, these rules contain
224:Rules are evaluated from left to right. Whitespace (space, tab and newline)
225:characters are ignored between "words". Rules consisting of only whitespace
273:Tim J. Robbins 

#

Use \(en for a dash (en-dash) between space characters, not a minus
(\-) or a hyphen (-), except in the NAME section.

tcpspy.8:145:.BI lport " [low] - [high]"

#

Protect a period (.) or a apostrophe (') with '\&' from becoming a
control character, if it could end up at the start of a line (by
splitting the line into more lines).

227:Parentheses, '(' and ')' may be placed around expressions to affect the 
order

#

"[" and "]", showing optional arguments to options, should be typeset in roman.

145:.BI lport " [low] - [high]"
169:.BI laddr " n.n.n.n[/m.m.m.m]"
173:.BI laddr " ip6-addr[/m]"

#

--- tcpspy.82023-06-18 17:56:03.0 +
+++ tcpspy.8.new2023-06-18 19:01:15.0 +
@@ -1,8 +1,8 @@
 .\" This file is part of tcpspy, a TCP/IP connection monitor.
 .\"
-.\" Copyright (c) 2000, 2001, 2002 Tim J. Robbins. 
+.\" Copyright (c) 2000, 2001, 2002 Tim J. Robbins.
 .\" All rights reserved.
-.\" 
+.\"
 .\" Redistribution and use in source and binary forms, with or without
 .\" modification, are permitted provided that the following conditions
 .\" are met:
@@ -13,7 +13,7 @@
 .\"documentation and/or other materials provided with the distribution.
 .\" 3. The name of the author may not be used to endorse or promote products
 .\"derived from this software without specific prior written permission.
-.\" 
+.\"
 .\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES,
 .\" INCLUDING, BUT NOT LIMITED 

Bug#1038600: opm-simulators: missing build-dependency on bc

[Graham Inggs]

Source: opm-simulators
Version: 2022.10+ds-2

Hi Maintainer

As can be seen in recent build logs [1], opm-simulators 2022.10+ds-2
is missing a build-dependency on bc.  I've copied what I hope is the
relevant part of the log below.  I can confirm that adding a
build-dependency on bc allows the build to succeed on Ubuntu's build
architectures.

Regards
Graham


[1] https://buildd.debian.org/status/package.php?p=opm-simulators


dpkg-buildpackage: info: host architecture amd64
 debian/rules clean
/bin/sh: 1: bc: not found
/bin/sh: 1: bc: not found
/bin/sh: 1: test: Illegal number:
/bin/sh: 1: bc: not found
/bin/sh: 1: bc: not found
/bin/sh: 1: test: Illegal number:
echo "ram in gb: 7, needed ram per thread: 4, threads: "
ram in gb: 7, needed ram per thread: 4, threads:

Bug#1038599: graphite-web: RuntimeError logged in stock configuration

[Kevin Otte]

Package: graphite-web
Version: 1.1.8-2
Severity: important
Tags: patch

The error
  RuntimeError("populate() isn't reentrant")
is logged in the Apache log file when attempting to use the stock
/usr/share/graphite-web/graphite.wsgi file.

https://wiki.rockstable.it/Icinga2 in the section "Graphite troubleshooting"
contains a workaround to fix the problem, namely changing

os.environ.setdefault('GRAPHITE_SETTINGS_MODULE', 'graphite.local_settings')

to

os.environ.setdefault('GRAPHITE_SETTINGS_MODULE', 'local_settings')

After making this change on my system the package works.


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

Kernel: Linux 6.1.0-9-amd64 (SMP w/1 CPU thread; PREEMPT)
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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages graphite-web depends on:
ii  adduser 3.134
ii  python3 3.11.2-1+b1
ii  python3-cairo   1.20.1-5+b1
ii  python3-cairocffi   1.4.0-1
ii  python3-django  3:3.2.19-1
ii  python3-django-tagging  1:0.5.0-4
ii  python3-pyparsing   3.0.9-1
ii  python3-simplejson  3.18.3-1
ii  python3-six 1.16.0-4
ii  python3-tz  2022.7.1-4
ii  python3-urllib3 1.26.12-1
ii  python3-whisper 1.1.4-2.2

graphite-web recommends no packages.

Versions of packages graphite-web suggests:
ii  graphite-carbon  1.1.7-1.1
ii  libapache2-mod-wsgi-py3  4.9.4-1+b2
pn  python3-ldap 
pn  python3-memcache 
pn  python3-mysqldb  

-- Configuration Files:
/etc/graphite/local_settings.py changed [not included]

-- no debconf information

Bug#1036378: gmpc: Remove unneeded libayatana-appindicator

[Bastian Germann]

I am uploading a NMU to DELAYED/10 to fix this.

Bug#1036379: parcellite: Remove unneeded libayatana-appindicator

[Bastian Germann]

I am uploading a NMU to fix this to DELAYED/10. The debdiff is attached.diff -Nru parcellite-1.2.1/debian/changelog parcellite-1.2.1/debian/changelog
--- parcellite-1.2.1/debian/changelog   2021-01-11 14:20:14.0 +0100
+++ parcellite-1.2.1/debian/changelog   2023-06-18 20:27:24.0 +0200
@@ -1,3 +1,10 @@
+parcellite (1.2.1-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop libayatana-appindicator (Closes: #1036379).
+
+ -- Bastian Germann   Sun, 18 Jun 2023 20:27:24 +0200
+
 parcellite (1.2.1-4) unstable; urgency=medium
 
   [ Hugo Lefeuvre ]
diff -Nru parcellite-1.2.1/debian/control parcellite-1.2.1/debian/control
--- parcellite-1.2.1/debian/control 2021-01-11 14:20:14.0 +0100
+++ parcellite-1.2.1/debian/control 2023-06-18 20:27:15.0 +0200
@@ -5,7 +5,6 @@
 Uploaders: Thomas Koch 
 Build-Depends: debhelper (>= 11),
intltool,
-   libayatana-appindicator-dev,
libgtk2.0-dev
 Standards-Version: 4.2.1
 Testsuite: autopkgtest-pkg-python

Bug#1034128: marked as done (memcached breaks cachelib autopkgtest: TimeoutError)

[Moisés Guimarães]

unsubscribe

On Sun, Jun 18, 2023 at 18:39, Debian Bug Tracking System 
<[ow...@bugs.debian.org](mailto:On Sun, Jun 18, 2023 at 18:39, Debian Bug 
Tracking System < wrote:

> Your message dated Sun, 18 Jun 2023 16:34:55 +
> with message-id 
> and subject line Bug#1034128: fixed in cachelib 0.9.0-2
> has caused the Debian Bug report #1034128,
> regarding memcached breaks cachelib autopkgtest: TimeoutError
> to be marked as done.
>
> This means that you claim that the problem has been dealt with.
> If this is not the case it is now your responsibility to reopen the
> Bug report if necessary, and/or fix the problem forthwith.
>
> (NB: If you are a system administrator and have no idea what this
> message is talking about, this may indicate a serious mail system
> misconfiguration somewhere. Please contact ow...@bugs.debian.org
> immediately.)
>
> --
> 1034128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034128
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

Bug#1003403: maven: Warning running mvn about which beeing deprecated

[Hans Joachim Desserud]

I must admit I wasn't able to reproduce this even when testing with 
older maven versions.


However, it looks like the most obvious usage of which was replaced 
upstream in 3.8.4, see for 
https://salsa.debian.org/java-team/maven/-/commit/e0a4b1763cfa9e730faa9526082ee793410fe1d1


So unless someone can still trigger this warning it might be fixed.

--
mvh / best regards
Hans Joachim Desserud
http://desserud.org

Bug#1038598: evolution: need 3.48.3 to fix issue

[Tim McConnell]

Package: evolution
Version: 3.48.2-1
Severity: normal

I reported an issue to the Evolution Mailing list and Milan Chra states:
Hi,
I suppose the mails also grow the vertical scrollbar (indefinitely) and
cannot be scrolled. Update to 3.48.3, which contains related fixes:
https://gitlab.gnome.org/GNOME/evolution/-/commit/e9b7c6bbcc0ed477182470ee6080999560f8b5d8

A workaround: change width of the preview panel, it sometimes helps,
but the size can differ per viewed mail.
Bye,
Milan
The workaround doesn't help the issue I'm having. The High  CPU usage goes away
but I'm still unable to scroll on certain HTML emails


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

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

Versions of packages evolution depends on:
ii  dbus [default-dbus-system-bus]  1.14.6-1
ii  dbus-broker [dbus-system-bus]   33-1
ii  evolution-common3.48.2-1
ii  evolution-data-server   3.48.2-1
ii  libc6   2.36-9
ii  libcamel-1.2-64 3.48.2-1
ii  libecal-2.0-2   3.48.2-1
ii  libedataserver-1.2-27   3.48.2-1
ii  libevolution3.48.2-1
ii  libglib2.0-02.74.6-2
ii  libgtk-3-0  3.24.37-2
ii  libical33.0.16-1+b1
ii  libnotify4  0.8.2-1
ii  libwebkit2gtk-4.1-0 2.40.2-1
ii  libxml2 2.9.14+dfsg-1.2
ii  psmisc  23.6-1

Versions of packages evolution recommends:
ii  evolution-plugin-bogofilter  3.48.2-1
ii  evolution-plugin-pstimport   3.48.2-1
ii  evolution-plugins3.48.2-1
ii  yelp 42.2-1

Versions of packages evolution suggests:
pn  evolution-ews   
ii  evolution-plugins-experimental  3.48.2-1
ii  gnupg   2.2.40-1.1
ii  network-manager 1.42.6-1

-- debconf-show failed

Bug#1038597: tcpspy.rules.5: some remarks and editing fixes for the manual

[Bjarni Ingi Gislason]

Package: tcpspy
Version: 1.7d-15
Severity: minor
Tags: patch

Dear Maintainer,

here are some editing fixes of the man page with remarks.

Input file is tcpspy.rules.5

Output from "mandoc  -T lint tcpspy.rules.5":

mandoc: tcpspy.rules.5:36:2: WARNING: skipping paragraph macro: PP after SH
mandoc: tcpspy.rules.5:40:24: STYLE: whitespace at end of input line
mandoc: tcpspy.rules.5:69:2: WARNING: skipping paragraph macro: PP empty
mandoc: tcpspy.rules.5:70:2: WARNING: skipping paragraph macro: PP empty
mandoc: tcpspy.rules.5:124:81: STYLE: input text line longer than 80 bytes: a 
default mask with ...
mandoc: tcpspy.rules.5:135:71: STYLE: whitespace at end of input line
mandoc: tcpspy.rules.5:142:73: STYLE: whitespace at end of input line
mandoc: tcpspy.rules.5:177:2: WARNING: skipping paragraph macro: PP empty

###

Remove space characters at the end of lines.

Use "git apply ... --whitespace=fix" to fix extra space issues, or use
global configuration "core.whitespace".

40:.IR /etc/init.d/tcpspy 
135:True if the full filename (including directory) of the executable that 
142:The pattern "" (an empty string) matches connections created/accepted by 

#

Reduce space between words.

150:Expressions (including the  comparisons listed above) may be joined together
196:Pablo Lorenzzoni (this manpage) and  Mats Erik Andersson (changes for IPv6)

#

Use the correct macro for the font change of a single argument or
split the argument into two.

40:.IR /etc/init.d/tcpspy 
83:.BI ip
86:.BI ip6

#

Change a HYPHEN-MINUS (code 0x55, 2D) to a minus (\-), if in front of a
name for an option.

103:.I -high
146:.B -p

#

Wrong distance between sentences.

  Separate the sentences and subordinate clauses; each begins on a new
line.  See man-pages(7) ("Conventions for source file layout") and
"info groff" ("Input Conventions").

  The best procedure is to always start a new sentence on a new line,
at least, if you are typing on a computer.

Remember coding: Only one command ("sentence") on each (logical) line.

E-mail: Easier to quote exactly the relevant lines.

Generally: Easier to edit the sentence.

Patches: Less unaffected text.

  The amount of space between sentences in the output can then be
controlled with the ".ss" request.

104:is used, low is assumed to be 0. It is an error to omit both
123:AND of the local address of the connection and "mask". If no mask is 
specified,
124:a default mask with all bits set (255.255.255.255) is used. The CIDR type 
netmask
125:is also possible. With IPv6 only a prefix length netmask is allowed, and the
126:length defaults to 128. Depending on the address family, these rules contain
172:Rules are evaluated from left to right. Whitespace (space, tab and newline)
173:characters are ignored between "words". Rules consisting of only whitespace
195:Tim J. Robbins (tcpspy),

#

Use \(en for a dash (en-dash) between space characters, not a minus
(\-) or a hyphen (-), except in the NAME section.

tcpspy.rules.5:55:to 4 rules (line 1 to line 4 - one per each line) using the 
boolean
tcpspy.rules.5:60:line 1 - for user "joedoe" connecting to 192.168.1.10:22 
(remote)
tcpspy.rules.5:62:line 2 - for user whose UID is 1003
tcpspy.rules.5:64:line 3 - to *:22 or *:21 (both locally)
tcpspy.rules.5:66:line 4 - for user "joedoe" to *:23 (local) or to 192.168.1.20 
(remote)
tcpspy.rules.5:71:.SS "Rule Syntax - just extracted from tcpspy(8)"
tcpspy.rules.5:93:.BI lport " [low] - [high]"

#

The name of a man page is set in bold type and the section in roman (see
man-pages(7)).

42:tcpspy (see tcpspy(8)) logger filtering rules.

#

Protect a period (.) or a apostrophe (') with '\&' from becoming a
control character, if it could end up at the start of a line (by
splitting the line into more lines).

175:Parentheses, '(' and ')' may be placed around expressions to affect the 
order

#

--- tcpspy.rules.5  2023-06-18 02:25:13.0 +
+++ tcpspy.rules.5.new  2023-06-18 17:42:52.0 +
@@ -33,13 +33,15 @@
 .SH NAME
 tcpspy.rules \- configuration file for tcpspy
 .SH DESCRIPTION
-.LP
 This file, by default
 .IR /etc/tcpspy.rules ,
 is read by the
-.IR /etc/init.d/tcpspy 
+.I /etc/init.d/tcpspy
 script at init time in order to configure
-tcpspy (see tcpspy(8)) logger filtering rules.
+tcpspy
+(see
+.BR tcpspy (8))
+logger filtering rules.
 .LP
 It might look like:
 .IP
@@ -52,23 +54,21 @@ lport 22 or lport 21
 .fi
 .LP
 This rules file specifies that tcpspy logs tcp connections according
-to 4 rules (line 1 to line 4 - one per each line) using the boolean
+to 4 rules (line 1 to line 4 \(en one per each line) using the boolean
 logic (see below) to evaluate each rule.
 .LP
 This particular example logs connections:
 .TP
-line 1 - for user "joedoe" connecting to 192.168.1.10:22 (remote)
+line 1 \(en for user "joedoe" connecting to 192.168.1.10:22 (remote)
 .TP
-line 2 - for user whose UID is 1003
+line 2 \(en for user whose UID is 1003
 .TP
-line 3 - to 

Bug#995159: hfsprogs: Directory hardlink problems cannot be repaired.

[John Paul Adrian Glaubitz]

Hi Daniel!

Apologies for the late reply. I had seen your message back then but it
somehow fell of the table and eventually forgot to answer. I just now
found your report again since I resumed working on the hfsprogs package.

On Mon, 2021-09-27 at 12:45 +0200, Daniel Höpfl wrote:
> Apple (the upstream) never finished the implementation of the directory 
> hardlink support
> in fsck_hfs. Since, once again, my TimeMachine backup rendered unrepairable 
> due to directory
> hardlink errors, I implemented what was required to fix the errors I 
> encountered.

The current hfsprogs package in Debian is based on a patched version 540.1 of 
Apple's
»diskdev_cmds« package [1] while Apple has actually continued their work on the 
HFS code.
in that package. However, after version 557.3.1 Apple decided to move the HFS 
code into a
separate package called just »hfs« [2] which makes sense given the fact that 
Apple switched
their default filesystem to APFS instead and diskdev_cms is no longer strictly 
tied to HFS.

I have started working on an updated Debian hfsprogs package which is based on 
the latest version
556.100.11 of the hfs package [3]. The code already compiles in openSUSE [4] 
but I don't consider
the Linux port to be complete yet.

However, you may want to try whether the latest version of Apple's own fsck_hfs 
has support for
fixing hardlink problems. If not, you may want to rebase your patch on top of 
hfs 560.100.11.

> My trust in Apple's feedback system is very low so I am sending the patch to 
> you in the hopes
> that you can forward it to Apple.

Try opening a pull request on Github [5]. Apple has actually moved their open 
source projects to
Github and it seems they're actually accepting pull requests for some projects.

> 
> The patch I added should work, with offsets, on both, Debian's sources as 
> well as Apple's sources.
> 
> My changes:
> 
> - Any hardlink inode with a parent other than the metadata directory is 
> changed
>   to have the correct parent.
>   I have seen these. I can understand how this happens when a normal directory
>   is hardlined for the first time. The journal SHOULD prevent this from being 
> a 
>   problem but obviously this is not the case.
> 
> - Directory hardlink inodes named "temp..." get deleted.
>   These directories were deleted while open when the volume was removed 
> without
>   unmounting. Since these directories have already been deleted, deleting them
>   in fsck is the right thing to do. (Documented like that for files in the 
> HFS+
>   spec.)
> 
> - Directory hardlink inodes with names other than "temp..." or "dir_..." are 
> moved
>   to "lost+found".
>   It would be better to rename them to "dir_..." in a first pass, there might 
> still
>   be valid links to them. These links are deleted by a different repair step 
> and I
>   did not see how to remove those other repair steps. Would probably lead to 
> a bigger
>   rewrite of the hardlink check code so I decided to just move these to l+f.
>   I have never seen this anyways.
> 
> After all, none of the errors should happen in a journaled filesystem 
> (directory
> hardlinks require the Journal to be active). My guess is that using HFS+ over 
> AFP
> (as TimeMachine does) does not correctly persist the journal before 
> persisting changes.
> Thus loosing the connection during directory hardlink operation can result in 
> partially
> executed atomic operation.

Sounds like a very useful and welcome improvement. I will definitely 
incorporate this
patch once I'm ready with the new upstream version. But maybe we're lucky and 
you can
get your changes merged upstream with Apple in the mean time.

FWIW, I have also reached out to Apple Legal trying to convince them to 
relicense the
hfs package to a more permissive license such as the Apache License like they 
have done
for other projects such as mDNSResponder [6]. Apple's own APSL license is 
considered
non-free by Debian [7] which makes redistribution of the package more 
complicated.

> I will attach the patch and test cases for each of the three fixed errors. 
> These test
> cases have been constructed in a hex editor, they might not be what a real 
> error looks
> like. The first two repairs successfully repaired my broken backup file so I 
> guess
> they work (sometimes).

Thanks, having test cases will be very useful for verifying my patched hfs 
package!

Adrian

> [1] https://github.com/apple-opensource/diskdev_cmds/tree/540.1
> [2] https://github.com/apple-opensource/hfs
> [3] https://github.com/glaubitz/hfs/tree/linux
> [4] 
> https://build.opensuse.org/package/show/home:glaubitz:branches:filesystems/hfsplus-tools
> [5] https://github.com/apple-opensource/hfs
> [6] https://github.com/apple-oss-distributions/mDNSResponder/
> [7] 
> https://wiki.debian.org/DFSGLicenses#Apple_Public_Source_License_.28APSL.29

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 

Bug#1038596: metview: Stop using netcdf-cxx-legacy

[Bas Couwenberg]

Source: metview
Version: 5.19.1-2
Severity: important
Tags: patch
User: debian-...@lists.debian.org
Usertags: netcdf-cxx-legacy-rm

Dear Maintainer,

Your package uses netcdf-cxx-legacy which is dead upstream and will be removed 
during the trixie development cycle.

The attached patch only drops the build dependency, as your package doesn't 
actually link to netcdf-cxx-legacy.

Kind Regards,

Bas
diff -Nru metview-5.19.1/debian/changelog metview-5.19.1/debian/changelog
--- metview-5.19.1/debian/changelog 2023-06-11 13:28:05.0 +0200
+++ metview-5.19.1/debian/changelog 2023-06-18 18:00:35.0 +0200
@@ -1,3 +1,10 @@
+metview (5.19.1-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Don't use netcdf-cxx-legacy.
+
+ -- Bas Couwenberg   Sun, 18 Jun 2023 18:00:35 +0200
+
 metview (5.19.1-2) unstable; urgency=medium
 
   * Push to unstable
diff -Nru metview-5.19.1/debian/control metview-5.19.1/debian/control
--- metview-5.19.1/debian/control   2023-06-11 13:28:05.0 +0200
+++ metview-5.19.1/debian/control   2023-06-18 18:00:35.0 +0200
@@ -51,7 +51,7 @@
   libproj-dev, libqt5svg5-dev,
   libgd-dev, 
   imagemagick, 
-  libnetcdf-dev, libnetcdf-cxx-legacy-dev,
+  libnetcdf-dev,
   flextra, 
   flexpart,
   libgeotiff-dev

Bug#614070: asunder: segfault on cddb resolver failure

[Peter B]

On Tue, 28 Feb 2017 11:06:22 + Alan Sermons 
 wrote:
> Package: asunder
> Version: 2.8-5
> Followup-For: Bug #614070
>
> Apologies for the late reply (and more if this appears twice).
>
> I've just tried this a couple of times, on a laptop that has only recently 
been
> installed. If the computer is aware that it has no connection to the Internet,
> then clicking "CDDB lookup" fails silently, but asunder keeps running. As soon
> as the connection comes back up (I'd turned the RF kill switch on the laptop
> off), it works as expected.
>
> If there is no Internet connection, but the computer does not know this (I
> rebooted the router while attempting this, but the Wifi stayed up) then the
> software aborts, as shown in the attached file. I have attached the output 
from
> gdb and the backtrace, as shown in the attached file.
>
> Please let me know what other information would be required.
>

Thanks for providing a backtrace.

The backtrace shows that lookup_disc called a library routine usleep which 
segfaulted.

Lookup_dsic has been rewritten and no longer calls usleep,
so its possible this bug is now fixed.

Can it still be reproduced?
If not, I'm inclined to close this bug now.



Cheers,
Peter

P.S. Googling "usleep segfault" gives over 13,000 results!!

Bug#1038595: linux-image-amd64: DVB broken with 6.3.7

[Eric Valette]

Package: linux-image-6.3.0-1-amd64
Version: 6.3.7-1
Severity: normal
Tags: patch


tvheadend does not work  with this kernel. 6.1.27 does.
The patch and the probme is also found by other 
https://bbs.archlinux.org/viewtopic.php?id=286421




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

Kernel: Linux 5.15.117 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-6.1.0-9-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.142
ii  kmod30+20230519-1
ii  linux-base  4.9

Versions of packages linux-image-6.1.0-9-amd64 recommends:
ii  apparmor 3.0.8-3
ii  firmware-linux-free  20200122-1

Versions of packages linux-image-6.1.0-9-amd64 suggests:
pn  debian-kernel-handbook  
ii  extlinux3:6.04~git20190206.bf6db5b4+dfsg1-3+b1
ii  grub-efi-amd64  2.06-13
pn  linux-doc-6.1   

Bug#1038594: gnome-shell extensions: right triangle has two different meanings; the two symbols need a redesign

[AlMa]

Package: gnome-shell-extension-freon
Version: 50+dfsg-1
Control: Affects: -1 gnome-shell-extension-pomodoro

The right-pointing white triangle ⏵ of Freon means: expand a submenu. 
The right-pointing white triangle ⏵ of Pomodoro means: start the timer. 
However, these two triangles look very similar (cf. the attached 
screenshots screenshot-freon.png and screenshot-pomodoro.png), 
suggesting that their meaning would be the same.


It took me, perhaps, 10-20 minutes, including a reboot, to understand 
that Pomodoro's triangle ⏵ itself means to be clicked, and the text 
“Pomodoro-Timer” to its left is NOT supposed to be clickable and that 
the absence of reaction to a click on “Pomodoro-Timer” might be intentional.


On the contrary, the text “Temperature …°” to the left of ⏵ in Freon 
IS supposed to be clickable.


Suggestion:
- Make ⏵ in Pomodoro more like the media-play symbol U+23F5 in the 
current Gnome font if not yet done.
- Replace the text “Pomodoro-Timer” with “Start timer” and make it 
clickable.
- Replace the filled right triangle ⏵ in Freon by the usual Gnome 
submenu right angle ⟩ or ›, which we see when we click on the settings 
in the right upper corner of the Screen (cf. attachment 
screenshot-gnome.png). It doesn't matter which symbol exactly GNOME uses 
(it may ever be drawn) – Freon should simply use the very same symbol.


Gratefully,
AlMa

Bug#1038593: linux-image-amd64: DVB broken with 6.3.7

[Eric Valette]

Package: linux-image-amd64
Version: 6.3.7-1
Severity: normal
Tags: patch

tvheadend does not work  with this kernel. 6.1.27 does.
The patch and the probme is also found by other 
https://bbs.archlinux.org/viewtopic.php?id=286421


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

Kernel: Linux 5.15.117 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-headers-rt-amd64 depends on:
pn  linux-headers-6.1.0-9-rt-amd64  
pn  linux-headers-6.3.0-1-rt-amd64  
pn  linux-headers-6.4.0-0-rt-amd64  

linux-headers-rt-amd64 recommends no packages.

linux-headers-rt-amd64 suggests no packages.

Bug#1011323: lablgtk2: Please remove the obsolete gtkgl/glarea component

[Bastian Germann]

I have just uploaded a NMU with the attached debdiff to fix this.diff -Nru lablgtk2-2.18.13/debian/changelog lablgtk2-2.18.13/debian/changelog
--- lablgtk2-2.18.13/debian/changelog   2023-01-21 08:58:55.0 +0100
+++ lablgtk2-2.18.13/debian/changelog   2023-06-18 19:12:29.0 +0200
@@ -1,3 +1,12 @@
+lablgtk2 (2.18.13-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+
+  [ Nicolas Boulenguez ]
+  * Remove the gtkgl/glarea component (Closes: #1011323)
+
+ -- Bastian Germann   Sun, 18 Jun 2023 19:12:29 +0200
+
 lablgtk2 (2.18.13-1) unstable; urgency=medium
 
   [ Stéphane Glondu ]
diff -Nru lablgtk2-2.18.13/debian/control lablgtk2-2.18.13/debian/control
--- lablgtk2-2.18.13/debian/control 2023-01-21 08:58:55.0 +0100
+++ lablgtk2-2.18.13/debian/control 2023-06-18 19:09:25.0 +0200
@@ -10,10 +10,8 @@
  dh-ocaml,
  ocaml,
  libcamlp-streams-ocaml-dev,
- liblablgl-ocaml-dev,
- libncurses5-dev,
+ libncurses-dev,
  libgtk2.0-dev,
- libgtkgl2.0-dev,
  librsvg2-dev,
  libgtkspell-dev,
  ocaml-findlib
@@ -36,19 +34,6 @@
  This package include only the dynamic libraries needed for running dynamic
  bytecode executables.
 
-Package: liblablgtk2-gl-ocaml
-Architecture: any
-Depends:
- ${ocaml:Depends},
- ${shlibs:Depends},
- ${misc:Depends}
-Provides: ${ocaml:Provides}
-Description: runtime libraries for OCaml bindings to GtkGL
- lablgtk2 contains bindings for GTK+ 2.x and Objective Caml.
- .
- This package include only the dynamic libraries needed for running dynamic
- bytecode executables using GtkGL functionalities.
-
 Package: liblablgtk2-gnome-ocaml
 Architecture: any
 Depends:
@@ -64,7 +49,7 @@
 
 Package: liblablgtk2-ocaml-dev
 Architecture: any
-Suggests: liblablgtk2-gl-ocaml-dev, liblablgtk2-gnome-ocaml-dev
+Suggests: liblablgtk2-gnome-ocaml-dev
 Depends:
  libgtk2.0-dev,
  libgtkspell-dev,
@@ -78,22 +63,6 @@
  .
  This package contains the development files of lablgtk.
 
-Package: liblablgtk2-gl-ocaml-dev
-Architecture: any
-Suggests: liblablgtk2-gnome-ocaml-dev
-Depends:
- libgtkgl2.0-dev,
- ${ocaml:Depends},
- ${shlibs:Depends},
- ${misc:Depends}
-Provides: ${ocaml:Provides}
-Recommends: liblablgtk2-ocaml-doc
-Description: OCaml bindings to GtkGL
- lablgtk2 contains bindings for GTK+ 2.x and OCaml.
- .
- This package contains the development files of lablgtk for libraries using
- GtkGL.
-
 Package: liblablgtk2-gnome-ocaml-dev
 Architecture: any
 Depends:
@@ -115,7 +84,6 @@
 Depends: ${misc:Depends}
 Enhances:
  liblablgtk2-ocaml-dev,
- liblablgtk2-gl-ocaml-dev,
  liblablgtk2-gnome-ocaml-dev,
 Multi-Arch: foreign
 Description: OCaml bindings to Gtk+ version 2 (documentation)
diff -Nru lablgtk2-2.18.13/debian/liblablgtk2-gl-ocaml-dev.docs 
lablgtk2-2.18.13/debian/liblablgtk2-gl-ocaml-dev.docs
--- lablgtk2-2.18.13/debian/liblablgtk2-gl-ocaml-dev.docs   2023-01-21 
08:58:55.0 +0100
+++ lablgtk2-2.18.13/debian/liblablgtk2-gl-ocaml-dev.docs   1970-01-01 
01:00:00.0 +0100
@@ -1 +0,0 @@
-README
diff -Nru lablgtk2-2.18.13/debian/liblablgtk2-gl-ocaml-dev.install.in 
lablgtk2-2.18.13/debian/liblablgtk2-gl-ocaml-dev.install.in
--- lablgtk2-2.18.13/debian/liblablgtk2-gl-ocaml-dev.install.in 2023-01-21 
08:58:55.0 +0100
+++ lablgtk2-2.18.13/debian/liblablgtk2-gl-ocaml-dev.install.in 1970-01-01 
01:00:00.0 +0100
@@ -1,4 +0,0 @@
-@OCamlStdlibDir@/lablgtk2/glGtk.*
-@OCamlStdlibDir@/lablgtk2/liblablgtkgl2*
-OPT: @OCamlStdlibDir@/lablgtk2/lablgtkgl.a
-OPT: @OCamlStdlibDir@/lablgtk2/lablgtkgl.cmxa
diff -Nru lablgtk2-2.18.13/debian/liblablgtk2-gl-ocaml.docs 
lablgtk2-2.18.13/debian/liblablgtk2-gl-ocaml.docs
--- lablgtk2-2.18.13/debian/liblablgtk2-gl-ocaml.docs   2023-01-21 
08:58:55.0 +0100
+++ lablgtk2-2.18.13/debian/liblablgtk2-gl-ocaml.docs   1970-01-01 
01:00:00.0 +0100
@@ -1 +0,0 @@
-README
diff -Nru lablgtk2-2.18.13/debian/liblablgtk2-gl-ocaml.install.in 
lablgtk2-2.18.13/debian/liblablgtk2-gl-ocaml.install.in
--- lablgtk2-2.18.13/debian/liblablgtk2-gl-ocaml.install.in 2023-01-21 
08:58:55.0 +0100
+++ lablgtk2-2.18.13/debian/liblablgtk2-gl-ocaml.install.in 1970-01-01 
01:00:00.0 +0100
@@ -1,4 +0,0 @@
-debian/META.lablgtk2-gl@OCamlStdlibDir@/METAS
-@OCamlStdlibDir@/lablgtk2/dlllablgtkgl2.so @OCamlDllDir@
-@OCamlStdlibDir@/lablgtk2/lablgtkgl.cma
-DYN: @OCamlStdlibDir@/lablgtk2/lablgtkgl.cmxs
diff -Nru lablgtk2-2.18.13/debian/liblablgtk2-ocaml-dev.install.in 
lablgtk2-2.18.13/debian/liblablgtk2-ocaml-dev.install.in
--- lablgtk2-2.18.13/debian/liblablgtk2-ocaml-dev.install.in2023-01-21 
08:58:55.0 +0100
+++ lablgtk2-2.18.13/debian/liblablgtk2-ocaml-dev.install.in2023-06-18 
19:07:11.0 +0200
@@ -43,7 +43,6 @@
 @OCamlStdlibDir@/lablgtk2/gtkEdit.*
 @OCamlStdlibDir@/lablgtk2/gtkEnums.*
 @OCamlStdlibDir@/lablgtk2/gtkFile.*
-@OCamlStdlibDir@/lablgtk2/gtkgl_tags.h
 @OCamlStdlibDir@/lablgtk2/gtkInit.*
 @OCamlStdlibDir@/lablgtk2/gtkList.*
 

Bug#1038591: virtualbox: Build-Depends (unnecessarily?) on SDL 1.2

[Simon McVittie]

Package: virtualbox
Tags: trixie sid
User: pkg-sdl-maintain...@lists.alioth.debian.org
Usertags: libsdl1.2

This package has a Build-Depends on SDL version 1.2, which
is unmaintained upstream. I don't see any sign of a runtime dependency
on SDL 1.2, though, only SDL 2 - is the build-dependency left over from
before the upstream package was converted to SDL 2?

If the dependency isn't actually necessary, please remove it and close
this bug.

Or, if there is a reason I'm not seeing why SDL is required, please
complete the update to SDL 2 and close this bug. There is a migration
guide at , and examples
of successful ports from SDL 1.2 to SDL 2 can be found in the commit
history of packages like darkplaces and ioquake3.

If it is not possible to port to SDL 2, please test the package with
libsdl1.2-compat-shim (preferably version 1.2.64 or later), and leave
this bug open to track the package as still using SDL 1.2 APIs.

libsdl1.2-compat-shim is a compatibility layer that provides the SDL 1.2
API/ABI by using SDL 2: it has already replaced the "classic" SDL 1.2
library in some other distributions like Fedora and Arch, and my intention
is to do the same in Debian during the trixie release cycle.

It is *not* necessary to change dependencies from libsdl1.2debian to
libsdl1.2-compat-shim, or from libsdl1.2-dev to libsdl1.2-compat-dev.
My intention is to make a future version of sdl12-compat take over
the old package names, to minimize the changes that are required in
dependent packages.

The interesting scenarios to test with libsdl1.2-compat-shim are:

1. Install libsdl1.2-compat-shim and run the program in an X11 environment,
   such as "GNOME on Xorg" or XFCE.
   ($XDG_RUNTIME_DIR/wayland-* should not exist)
2. Install libsdl1.2-compat-shim and run the program in a Wayland
   environment such as GNOME's default mode, using Xwayland.
   ($XDG_RUNTIME_DIR/wayland-* should exist)
3. Install libsdl1.2-compat-shim and run the program in a Wayland
   environment, but this time with environment variable
   SDL_VIDEODRIVER=wayland so that it uses the native Wayland interface
   (this is not currently the default for SDL 2).
4. Install libsdl1.2-compat-dev and recompile the package.

If any of those fail, please report it as a bug in the
libsdl1.2-compat-shim or libsdl1.2-compat-dev package as appropriate,
with "affects" pointing to the program that is affected.

Thanks,
smcv

-- 
This bug report is part of a mass-bug-filing:

Bug#1038553: ITS: debianutils

[Bastian Germann]

Source: debianutils
Severity: important

debianutils is obviously not maintained anymore and qualifies for salvaging.
I intend to salvage the package and will upload a new version in 3 weeks if 
nobody objects.

Bug#1038440: debian-cd: debian-12.0.0-amd64-netinst.iso is too big for a CD

[Thomas Schmitt]

Hi,

when comparing 12.0.0 with 11.5.0 i see three file trees which have grown
substantially:

du of mounted debian-11.5.0-amd64-netinst.iso :
  5   /firmware
  126611  /install.amd
  308479  /pool

du of mounted debian-12.0.0-amd64-netinst.iso :
  221108  /firmware
  156509  /install.amd
  589416  /pool

In pool of 12.0.0 i see another firmware tree
  220570  /pool/non-free-firmware
but this does not cost much media capacity, because the file content is
shared with the files in the /firmware tree:

  $ xorriso -indev debian-12.0.0-amd64-netinst.iso \
-find / -sort_lba -exec report_lba --
  ...
  Report layout: xt , Startlba ,   Blocks , Filesize , ISO image path
  ...
  File data lba:  0 ,18420 , 8217 , 16827872 , 
'/firmware/firmware-atheros_20230210-5_all.deb'
  File data lba:  0 ,18420 , 8217 , 16827872 , 
'/pool/non-free-firmware/f/firmware-nonfree/firmware-atheros_20230210-5_all.deb'
  ...

Such deduplication of hard links also happens with initrd.gz and vmlinuz
files in /install.amd. The real storage sizes as measured in above -find
output are:
   11.5.0   12.0.0  Growth
  /firmware 0 MiB  216 MiB 216 MiB
  /install.amd 67 MiB  138 MiB  71 MiB
  /pool   301 MiB  360 MiB  59 MiB

To fit on a regular "700 MB" (~ 702 MiB) CD-R/CD-RW these would have to
shrink by at least 36 MiB.


Have a nice day :)

Thomas

Bug#1038506: libmlt7: Contains a plugin for an obsolete version of SDL

[Simon McVittie]

Package: libmlt7
Version: 7.14.0-1
Tags: trixie sid
User: pkg-sdl-maintain...@lists.alioth.debian.org
Usertags: libsdl1.2

libmlt7 appears to contain plugins for both SDL 1.2 and SDL 2, and as a
result, it depends on both libsdl1.2debian and libsdl2-2.0-0.
SDL 1.2 is unmaintained upstream and we should be trying to move away
from it.

Various Debian packages depend on mlt:

- flowblade
- kdenlive
- shotcut
- synfig
- synfigstudio

but as far as I can see, none of them need SDL 1.2 specifically. Would
it be possible to disable/remove the SDL 1.2 plugin in mlt?

Thanks,
smcv

-- 
This bug report is part of a mass-bug-filing:

Bug#883736: gtk2-engines-aurora: Please don't depend on gtk2

[Bastian Germann]

I am uploading a NMU to DELAYED/10. The debdiff is attached.diff -Nru gtk2-engines-aurora-1.5.1/debian/changelog 
gtk2-engines-aurora-1.5.1/debian/changelog
--- gtk2-engines-aurora-1.5.1/debian/changelog  2013-10-27 18:37:37.0 
+0100
+++ gtk2-engines-aurora-1.5.1/debian/changelog  2023-06-18 18:29:19.0 
+0200
@@ -1,3 +1,16 @@
+gtk2-engines-aurora (1.5.1-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Jeremy Bicha ]
+  * Bump debhelper compat to 10.
+  * Don't depend on libgtk2.0-0. (Closes: #883736)
+
+  [ Jelmer Vernooij ]
+  * Migrate repository from alioth to salsa.
+
+ -- Bastian Germann   Sun, 18 Jun 2023 18:29:19 +0200
+
 gtk2-engines-aurora (1.5.1-4) unstable; urgency=low
 
   * [4411acc] Use --with=autotools_dev.
diff -Nru gtk2-engines-aurora-1.5.1/debian/compat 
gtk2-engines-aurora-1.5.1/debian/compat
--- gtk2-engines-aurora-1.5.1/debian/compat 2013-10-27 18:37:37.0 
+0100
+++ gtk2-engines-aurora-1.5.1/debian/compat 2023-06-18 18:28:39.0 
+0200
@@ -1 +1 @@
-9
+10
diff -Nru gtk2-engines-aurora-1.5.1/debian/control 
gtk2-engines-aurora-1.5.1/debian/control
--- gtk2-engines-aurora-1.5.1/debian/control2013-10-27 18:37:37.0 
+0100
+++ gtk2-engines-aurora-1.5.1/debian/control2023-06-18 18:28:39.0 
+0200
@@ -2,18 +2,16 @@
 Section: x11
 Priority: optional
 Maintainer: Chow Loong Jin 
-Build-Depends: debhelper (>= 9),
-   autotools-dev,
+Build-Depends: debhelper (>= 10),
libgtk2.0-dev (>= 2.10.0)
 Standards-Version: 3.9.4
 Homepage: http://www.gnome-look.org/content/show.php?content=56438
-Vcs-Git: git://git.debian.org/git/collab-maint/gtk2-engines-aurora.git
-Vcs-Browser: http://git.debian.org/?p=collab-maint/gtk2-engines-aurora.git
+Vcs-Git: https://salsa.debian.org/debian/gtk2-engines-aurora.git
+Vcs-Browser: https://salsa.debian.org/debian/gtk2-engines-aurora
 
 Package: gtk2-engines-aurora
 Architecture: any
-Depends: gtk2.0-binver-2.10.0,
- ${shlibs:Depends}, ${misc:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends}
 Description: Aurora gtk+-2.0 theme engine
  "Aurora" refers to the natural light displays in the sky in polar regions. 
This
  package contains the Aurora theme engine for the GTK+ toolkit, version 2.0.
diff -Nru gtk2-engines-aurora-1.5.1/debian/rules 
gtk2-engines-aurora-1.5.1/debian/rules
--- gtk2-engines-aurora-1.5.1/debian/rules  2013-10-27 18:37:37.0 
+0100
+++ gtk2-engines-aurora-1.5.1/debian/rules  2023-06-18 18:28:39.0 
+0200
@@ -21,7 +21,10 @@
dh_auto_install
find debian/gtk2-engines-aurora -name '*.la' -delete
 
+override_dh_shlibdeps:
+   dh_shlibdeps -- -xlibgtk2.0-0
+
 %:
-   dh $@ --with=autotools_dev
+   dh $@
 
 .PHONY: get-orig-source

Bug#1038505: mlv: Extends an obsolete version of SDL

[Simon McVittie]

Source: mlv
Tags: trixie sid wontfix
User: pkg-sdl-maintain...@lists.alioth.debian.org
Usertags: libsdl1.2

mlv is a convenience wrapper around SDL 1.2, which is unmaintained
upstream. It seems quite likely that mlv is unmaintained upstream as well;
there don't seem to have been any releases since 2017.

mlv seems to include SDL 1.2 objects in its API/ABI, for example in
MLV_mouse.h, so it will not be possible to convert it to SDL 2 without
breaking API/ABI. As a result, if there is a version or replacement that
targets SDL 2, it should probably be packaged separately, which is why
I'm marking this bug as "won't fix".

There does not seem to be anything in Debian that depends or build-depends
on mlv:

> smcv@coccia ~ % dak rm -R -n mlv
...
> Checking reverse dependencies...
> No dependency problem found.

and its homepage says:

> If you are not a C beginner, better use the SDL librairy (SDL, SDL_gfx,
> SDL_sound, SDL_ttf).

Is there still any benefit to Debian from having this library in the
distribution? If not, then we should probably remove it, to avoid it
taking up contributors' time during archive-wide QA (for example #1015546).

Thanks,
smcv

-- 
This bug report is part of a mass-bug-filing:

Bug#991428: Consider migrating to original 7-Zip for Linux

[yokota]

Hello,

> Now that the 7zip package is feature-compatible with p7zip please move this 
> forward
> and convert the p7zip packages to transitional packages.

I was uploaded experimental 7zip package (22.01+dfsg-10~exp1) to replace p7zip.
This package also adds alternative selection to allow other 7-Zip
implementation like p7zip or forked p7zip.

Updated codes are also available from salsa.
  https://salsa.debian.org/debian/7zip/-/tree/experimental

--
YOKOTA

Bug#1038343: fim: Depends on SDL 1.2

[Simon McVittie]

On Sat, 17 Jun 2023 at 21:11:25 +0200, Rafael Laboissière wrote:
> Thanks for this bug report. I forwarded it upstream and I am also sending
> this message with Cc to the upstream author.

Thanks. In the meantime, please could you check whether fim works as
intended with libsdl1.2-compat-shim, which is meant to be a drop-in
replacement? I'm trying to track whether there are any blockers to
replacing "classic" SDL 1.2.

smcv

Bug#1038504: liblavplay-2.1-0: Depends on SDL 1.2

[Simon McVittie]

Package: liblavplay-2.1-0
Tags: trixie sid
User: pkg-sdl-maintain...@lists.alioth.debian.org
Usertags: libsdl1.2

The liblavplay-2.1-0 and mjpegtools binary packages depend on SDL version
1.2, which is unmaintained upstream.

If possible, please port this package to SDL 2 and close this bug. There
is a migration guide at ,
and examples of successful ports from SDL 1.2 to SDL 2 can be found in
the commit history of packages like darkplaces and ioquake3.
If SDL is included in the API/ABI (I haven't checked), then switching
to SDL 2 is likely to involve a SONAME bump which should be coordinated
with upstream.

If it is not possible to port to SDL 2, please test the package with
libsdl1.2-compat-shim (preferably version 1.2.64 or later), and leave
this bug open to track the package as still using SDL 1.2 APIs.

libsdl1.2-compat-shim is a compatibility layer that provides the SDL 1.2
API/ABI by using SDL 2: it has already replaced the "classic" SDL 1.2
library in some other distributions like Fedora and Arch, and my intention
is to do the same in Debian during the trixie release cycle.

It is *not* necessary to change dependencies from libsdl1.2debian to
libsdl1.2-compat-shim, or from libsdl1.2-dev to libsdl1.2-compat-dev.
My intention is to make a future version of sdl12-compat take over
the old package names, to minimize the changes that are required in
dependent packages.

The interesting scenarios to test with libsdl1.2-compat-shim are:

1. Install libsdl1.2-compat-shim and run the program in an X11 environment,
   such as "GNOME on Xorg" or XFCE.
   ($XDG_RUNTIME_DIR/wayland-* should not exist)
2. Install libsdl1.2-compat-shim and run the program in a Wayland
   environment such as GNOME's default mode, using Xwayland.
   ($XDG_RUNTIME_DIR/wayland-* should exist)
3. Install libsdl1.2-compat-shim and run the program in a Wayland
   environment, but this time with environment variable
   SDL_VIDEODRIVER=wayland so that it uses the native Wayland interface
   (this is not currently the default for SDL 2).
4. Install libsdl1.2-compat-dev and recompile the package.

If any of those fail, please report it as a bug in the
libsdl1.2-compat-shim or libsdl1.2-compat-dev package as appropriate,
with "affects" pointing to the program that is affected.

Thanks,
smcv

-- 
This bug report is part of a mass-bug-filing:

Bug#984748: gettext is wrongly marked Multi-Arch: foreign

[roucaries bastien]

Hi,

Time to get to unstable post release

Bastien

Le dim. 26 févr. 2023 à 14:44, Bastien Roucariès
 a écrit :
>
> Source: gettext
> Followup-For: Bug #984748
> Control: tags -1 + patch
>
> Dear Maintainer,
>
> I havve done a few patches for improving the situation. Patch 2 may be 
> reported
> upstream.

Bug#1038486: devscripts: FTBFS + autopkgtest failure with libgitlab-api-v4-perl 0.27-1

[gregor herrmann]

Source: devscripts
Version: 2.23.5
Severity: serious
Tags: patch ftbfs trixie sid
Justification: fails to build from source (but built successfully in the past)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Since the upload of libgitlab-api-v4-perl 0.27-1, devscripts has test
failures both in autopkgtests and during build, c.f.

https://ci.debian.net/data/autopkgtest/testing/i386/d/devscripts/34359109/log.gz

Undefined subroutine ::to_json called at ./t/salsa.pm line 49.
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 255 just after 1.
t/salsa.t . 
Dubious, test returned 255 (wstat 65280, 0xff00)
All 1 subtests passed 
make[1]: *** [Makefile:44: test_perl.test_installed] Error 1
make: *** [Makefile:47: test-installed] Error 2


The reason is that test/t/salsa.pm calls JSON::to_json without
importing the JSON module (and without a dependency); this has
worked so far because libgitlab-api-v4-perl dependend on and loaded
JSON, but 0.27 has switched to JSON::MaybeXS.


Trivial and tested patch attached.


Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmSPKnZfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgZ69BAAlCCHtwE+ZqffD+umkpcPwY9s892wrLhhKCYOqpEWqN+Ykarz6UMjBisH
RubNjUVceR+rsoWUqWcenjvPSTvqU3ctp9FeFAElh9DD161oOogmljqYGovR9ZaA
ZCgNCZcNHuKBVzIScFK8pnI2C4mAq8KHC3US/ewu7cv1U0ijY+N6bJQ7Ge1HiAN8
nRZSEwLFTLZ84GKsm/1nHNrays/2Q6G/QhZr1q0lllLvFQdViv3O8m4Xp76YMNF7
Bk2rcQjHx3q28B5avj4aze+Mx66QCVHKMv7CA7R6RmKvPpMdrdOfTCzwbsydWowc
0Sh7ecrrnCuwSwFyDcofssMwEdDOD3gLvvvDOqcNb6OCxtZYHILhsm+SEA7eNsPK
XRWptGINYKd1lNoY/1mQ1kaj9z6PU++v0skcgnA4NYqcohjKRjtBdLSJUkFH6DRS
4D/CQNtgHYM0yNOqYuZdhTDAZYD4G4YXJWsP6FPRkKnZ8nM4RugWtY05F6Ez4gQ4
IhJ0ousPUiY+G38mIVypdz1PmkMVehhEglyrM8ZuXpslZopHGHzfOojlAnlwUWEX
RFrkF4eHYw4DI34TVfNut3MxekMcWqwLXhzx1cr3msI4KtrMqT2PKNaxDW0cXuO1
OhmseAgrdWqWRV2u6g3Jf7gdjlsrUhSDvqVbwd+zUnZoVk/wUv8=
=3FK+
-END PGP SIGNATURE-
diff --git a/debian/control b/debian/control
index fce9de12..c494055d 100644
--- a/debian/control
+++ b/debian/control
@@ -29,6 +29,7 @@ Build-Depends:
  libgit-wrapper-perl ,
  libgitlab-api-v4-perl (>= 0.13) ,
  libipc-run-perl ,
+ libjson-perl ,
  liblist-compare-perl ,
  libmoo-perl ,
  libstring-shellquote-perl ,
diff --git a/debian/tests/control b/debian/tests/control
index eb8095b0..2b09c1de 100644
--- a/debian/tests/control
+++ b/debian/tests/control
@@ -9,6 +9,7 @@ Depends:
  libdistro-info-perl,
  libgitlab-api-v4-perl,
  libipc-run-perl,
+ libjson-perl,
  libtest-output-perl,
  libwww-perl,
  mozilla-devscripts,
diff --git a/test/t/salsa.pm b/test/t/salsa.pm
index 800d1e59..b737e262 100644
--- a/test/t/salsa.pm
+++ b/test/t/salsa.pm
@@ -3,6 +3,7 @@
 package MockRESTClient;
 use URI;
 use Moo;
+use JSON;
 extends 'GitLab::API::v4::RESTClient';
 
 has _mocks => (

Bug#1038468: python-escript: Stop using netcdf-cxx-legacy

[Bas Couwenberg]

Source: python-escript
Version: 5.6-4
Severity: important
Tags: patch
User: debian-...@lists.debian.org
Usertags: netcdf-cxx-legacy-rm

Dear Maintainer,

Your package uses netcdf-cxx-legacy which is dead upstream and will be removed 
during the trixie development cycle.

The attached patch only drops the build dependency, as your package doesn't 
actually link to netcdf-cxx-legacy.

Kind Regards,

Bas
diff -ruN python-escript-5.6/debian/changelog 
python-escript-5.6.new/debian/changelog
--- python-escript-5.6/debian/changelog 2022-01-01 12:40:25.0 +0100
+++ python-escript-5.6.new/debian/changelog 2023-06-18 17:53:26.631234221 
+0200
@@ -1,3 +1,10 @@
+python-escript (5.6-4.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Don't use netcdf-cxx-legacy.
+
+ -- Bas Couwenberg   Sun, 18 Jun 2023 17:53:18 +0200
+
 python-escript (5.6-4) unstable; urgency=medium
 
   * Standards-Version: 4.6.0
diff -ruN python-escript-5.6/debian/control 
python-escript-5.6.new/debian/control
--- python-escript-5.6/debian/control   2022-01-01 12:40:25.0 +0100
+++ python-escript-5.6.new/debian/control   2023-06-18 16:14:47.514101664 
+0200
@@ -20,7 +20,6 @@
   libboost-numpy-dev,
libboost-iostreams-dev,
libnetcdf-dev,
-   libnetcdf-cxx-legacy-dev,
   libnetcdf-c++4-dev,
   libsilo-dev (>= 4.10.2.real-5),
   libscotchparmetis-dev,

Bug#1038464: /usr/bin/uscan: allow using multiple captures in downloadurlmangle

[Patrice Duroux]

Package: devscripts
Version: 2.23.5
Severity: wishlist
File: /usr/bin/uscan

Dear Maintainer,

Could it be possible to do the following:

version=4
opts="uversionmangle=s/-rc/~rc/;s/-alpha/~alpha/;s/-beta/~beta/,
downloadurlmangle=s%archive/refs/tags/(v?@ANY_VERSION@)(@ARCHIVE_EXT@)%releases/download/$1/SuperTux-$1-Source$2%,
filenamemangle=s%(?:.*?)?v?@ANY_VERSION@(@ARCHIVE_EXT@)%@PACKAGE@-$1$2%" \
https://github.com/SuperTux/@PACKAGE@/tags
(?:.*?/)?v?@ANY_VERSION@@ARCHIVE_EXT@

(see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038393#15)
or am I doing it wrong?

$ uscan --report-status
uscan info: uscan (version 2.23.5) See uscan(1) for help
[...]

Got:
uscan info: Matching target for downloadurlmangle:
https://github.com/SuperTux/supertux/archive/refs/tags/v0.6.3.tar.gz
uscan info: Upstream URL(+tag) to download is identified as
https://github.com/SuperTux/supertux/releases/download/v0.6.3/SuperTux-v0.6.3-Source0.6.3
[...]

Expected:
uscan info: Matching target for downloadurlmangle:
https://github.com/SuperTux/supertux/archive/refs/tags/v0.6.3.tar.gz
uscan info: Upstream URL(+tag) to download is identified as
https://github.com/SuperTux/supertux/releases/download/v0.6.3/SuperTux-v0.6.3-Source.tar.gz
[...]

Thanks,
Patrice


-- Package-specific info:

--- /etc/devscripts.conf ---
Empty.

--- ~/.devscripts ---
export DEBFULLNAME="Patrice Duroux"
export DEBEMAIL="patrice.dur...@gmail.com"

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

Kernel: Linux 6.3.0-1-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
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 devscripts depends on:
ii  dpkg-dev  1.21.22
ii  fakeroot  1.31-1.2
ii  file  1:5.44-3
ii  gnupg 2.2.40-1.1
ii  gpgv  2.2.40-1.1
ii  libfile-dirlist-perl  0.05-3
ii  libfile-homedir-perl  1.006-2
ii  libfile-touch-perl0.12-2
ii  libfile-which-perl1.27-2
ii  libipc-run-perl   20220807.0-1
ii  libmoo-perl   2.005005-1
ii  libwww-perl   6.70-1
ii  patchutils0.4.2-1
ii  perl  5.36.0-7
ii  python3   3.11.2-1+b1
ii  sensible-utils0.0.17+nmu1
ii  wdiff 1.2.2-5

Versions of packages devscripts recommends:
ii  apt 2.6.1
ii  curl7.88.1-10
ii  dctrl-tools 2.24-3+b1
ii  debian-keyring  2023.05.26
pn  dput | dupload  
ii  equivs  2.3.1
ii  libdistro-info-perl 1.5
ii  libdpkg-perl1.21.22
ii  libencode-locale-perl   1.05-3
ii  libgit-wrapper-perl 0.048-2
ii  libgitlab-api-v4-perl   0.27-1
ii  liblist-compare-perl0.55-2
ii  liblwp-protocol-https-perl  6.10-1
ii  libsoap-lite-perl   1.27-3
ii  libstring-shellquote-perl   1.04-3
ii  libtry-tiny-perl0.31-2
ii  liburi-perl 5.19-1
ii  licensecheck3.3.5-1
ii  lintian 2.116.3
ii  man-db  2.11.2-2
ii  patch   2.7.6-7
ii  pristine-tar1.50
ii  python3-apt 2.6.0
ii  python3-debian  0.1.49
ii  python3-magic   2:0.4.26-3
ii  python3-requests2.28.1+dfsg-1
ii  python3-unidiff 0.7.3-1
ii  python3-xdg 0.28-2
ii  strace  6.1-0.1
ii  unzip   6.0-28
ii  wget1.21.3-1+b2
ii  xz-utils5.4.1-0.2

Versions of packages devscripts suggests:
ii  adequate  0.15.7
ii  at3.2.5-1+b1
ii  autopkgtest   5.29
pn  bls-standalone
ii  build-essential   12.9
pn  check-all-the-things  
pn  cvs-buildpackage  
ii  debhelper 13.11.4
pn  diffoscope
pn  disorderfs
pn  dose-extra
pn  duck  
pn  elpa-devscripts   
pn  faketime  
pn  gnuplot   
pn  how-can-i-help
ii  libauthen-sasl-perl   2.1600-3
ii  libdbd-pg-perl3.16.3-1
ii  libfile-desktopentry-perl 0.22-3
pn  libterm-size-perl 
ii  libtimedate-perl  2.3300-2
pn  

Bug#1038463: cegui-mk2: Is this library still useful to have in Debian?

[Simon McVittie]

Source: cegui-mk2
Severity: normal
X-Debbugs-Cc: irrli...@packages.debian.org

While opening bugs for packages that depend on libsdl1.2, I noticed
that cegui-mk2 seems to be a library that is not depended on by anything
in Debian. Is it still useful to have in the distribution?

Looking at https://qa.debian.org/popcon.php?package=cegui-mk2, there
were a relatively large number of installations in the 2008-2010 period,
and a dramatic drop after 2010. I assume this is a result of some game
that used to use cegui-mk2 either switching away from it or being removed
from Debian.

If cegui-mk2 is no longer useful, we could remove it from the archive to
avoid it taking up QA time.

If it's removed, as far as I can see, we could also remove irrlicht (which
was previously a dependency for minetest, but minetest has switched to
a vendored fork of irrlicht).

smcv

Bug#1038163:

[Michael Biebl]

Am 18.06.23 um 16:52 schrieb Richard Lewis:
ill reply later,  with a proper patch (or MR if i can find the right 
place on salsa) but in the meantime, the NEWS.Debian in the 
logcheck-database package has details of how to support both formats in 
case people find this an issue





A MR on salsa would be great:
https://salsa.debian.org/debian/rsyslog/-/merge_requests

As the logcheck have been broken a couple of times in the past, I would 
really appreciate if you could add an autopkgtest for it, while at it.


See also my comments in 
https://salsa.debian.org/debian/rsyslog/-/merge_requests/6 (where 
unfortunately there was no more follow-up by the submitter)


Regards,
Michael


OpenPGP_signature
Description: OpenPGP digital signature

Bug#986582: nethack-x11: Missing symlink /usr/games/nethack-x11 -> /usr/lib/games/nethack/nethack-x11.sh

[Reiner Herrmann]

Hi Tobi,

there is actually a symlink to nethack-x11.sh, it's just called
xnethack (and not nethack-x11). xnethack is also used in the .desktop
file to start the game.
I think there are historical reasons why it's called that way.
Do you think an additional symlink (and .desktop file) would make sense?
Or should we just keep xnethack?

Kind regards,
  Reiner


signature.asc
Description: PGP signature

Bug#1038393: supertux: improve d/watch file

[Patrice Duroux]

Source: supertux
Version: 0.6.3-2
Followup-For: Bug #1038393

Hi,

Sorry for that. Here is a second version of the patch.

I suspect a bug in uscan because using the following rule in the d/watch file:

downloadurlmangle=s%archive/refs/tags/v?(@ANY_VERSION@)(@ARCHIVE_EXT@)%releases/download/v$1/SuperTux-v$1-Source$2%

gives the following message from uscan:

uscan info: Upstream URL(+tag) to download is identified as
https://github.com/SuperTux/supertux/releases/download/v0.6.3/SuperTux-v0.6.3-Source0.6.3

in place of the expected one:

uscan info: Upstream URL(+tag) to download is identified as
https://github.com/SuperTux/supertux/releases/download/v0.6.3/SuperTux-v0.6.3-Source.tar.gz


For this reason, the extension (.tar.gz) is hard-coded in the rule of this
second version.

Regards,
Patrice


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

Kernel: Linux 6.3.0-1-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
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
diff --git a/debian/watch b/debian/watch
index 83aa7f1..21a157b 100644
--- a/debian/watch
+++ b/debian/watch
@@ -1,3 +1,5 @@
 version=4
-opts="uversionmangle=s/-rc/~rc/;s/-alpha/~alpha/;s/-beta/~beta/;s/-Source//" \
-https://github.com/SuperTux/supertux/releases 
.*/SuperTux-v?@ANY_VERSION@-Source@ARCHIVE_EXT@
+#https://github.com/SuperTux/supertux/releases/download/v0.6.3/SuperTux-v0.6.3-Source.tar.gz
+#  
//github.com/SuperTux/supertux/releases/download/SuperTux-v0.6.3-Source.tar.gz
+opts="uversionmangle=s/-rc/~rc/;s/-alpha/~alpha/;s/-beta/~beta/, 
downloadurlmangle=s%archive/refs/tags/v?(@ANY_VERSION@).tar.gz%releases/download/v$1/SuperTux-v$1-Source.tar.gz%,
 filenamemangle=s%(?:.*?)?v?@ANY_VERSION@(@ARCHIVE_EXT@)%@PACKAGE@-$1$2%" \
+https://github.com/SuperTux/@PACKAGE@/tags 
(?:.*?/)?v?@ANY_VERSION@@ARCHIVE_EXT@

Bug#1038453: aeskulap: Is this package still desirable to have in Debian?

[Simon McVittie]

Source: aeskulap
Severity: normal
Tags: trixie sid

I stumbled across aeskulap while checking which packages still depend on
various GNOME-2-era (pre-2012) libraries.

According to its linked upstream website
, aeskulap is a viewer for DICOM images,
used in medical imaging. Its most recent release seems to have been in
March 2006, and the version in Debian is a git snapshot from 2019 (which
seems to be from some unoffical fork, I can't find any indication on
Savannah that the nongnu.org version has a git repo).

Is this package still useful?

Is it still maintained upstream by someone? If the Debian package is
tracking a maintained fork rather than the original upstream maintainers'
version, then updating the Homepage field to point to that fork would
be useful for people doing QA.

Thanks,
smcv

Bug#1032010: gettext: binary in /usr/lib should move to libexec

[Bruno Haible]

Hi,

Bastien Roucariès wrote in
:

> /usr/lib/x86_64-linux-gnu/gettext/cldr-plurals
> /usr/lib/x86_64-linux-gnu/gettext/hostname
> /usr/lib/x86_64-linux-gnu/gettext/project-id
> /usr/lib/x86_64-linux-gnu/gettext/urlget
> /usr/lib/x86_64-linux-gnu/gettext/user-email
> should go to:
> /usr/libexec/x86_64-linux-gnu/gettext/cldr-plurals
> /usr/libexec/x86_64-linux-gnu/gettext/hostname
> /usr/libexec/x86_64-linux-gnu/gettext/project-id
> /usr/libexec/x86_64-linux-gnu/gettext/urlget
> /usr/libexec/x86_64-linux-gnu/gettext/user-email

Upstream, this will be fixed in the next release, through
https://git.savannah.gnu.org/gitweb/?p=gettext.git;a=commitdiff;h=43a4b5eeecaf9805064ec718755d0a033e8f2f9b

But upstream, the file names before and after are these:

before:
 /usr/lib/gettext/cldr-plurals
 /usr/lib/gettext/hostname
 /usr/lib/gettext/project-id
 /usr/lib/gettext/urlget
 /usr/lib/gettext/user-email
after:
 /usr/libexec/gettext/cldr-plurals
 /usr/libexec/gettext/hostname
 /usr/libexec/gettext/project-id
 /usr/libexec/gettext/urlget
 /usr/libexec/gettext/user-email

IMO, there's no point in having a per-architecture subdir under /usr/libexec.
You don't have one under /bin either. This means, a user can't install the
32-bit binaries and the 64-binaries or the x32 binaries of the gettext-tools
package together; they conflict with each other.

Bruno

Bug#1038452: bepasty: 500 Internal Server Error when displaying text

[valhalla]

Package: bepasty
Version: 1.0.0-1
Severity: important
X-Debbugs-Cc: valha...@debian.org

Dear Maintainer,

Displaying a text file with bepasty fails with 500, and a traceback ending in 

  File "/usr/lib/python3/dist-packages/bepasty/utils/formatters.py", 
line 43, in format_unencoded
source = self.wrap(source, outfile)
 ^^
TypeError: HtmlFormatter.wrap() takes 2 positional arguments but 3 were 
given

in the logs; if this was triggered while doing an upload the upload worked, and 
displaying the text inline works.
Uploading images (and possibly other data types) still works).

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

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

Versions of packages bepasty depends on:
ii  fonts-font-awesome5.0.10+really4.7.0~dfsg-4.1
ii  libjs-bootbox 5.5.3~ds-1
ii  libjs-bootstrap4  4.6.1+dfsg1-4
ii  libjs-bootswatch  3.3.7+dfsg2-1.1
ii  libjs-jquery  3.6.1+dfsg+~3.5.14-1
ii  libjs-jquery-file-upload  10.32.0-1
ii  libjs-jquery-ui   1.13.2+dfsg-1
ii  libjs-sphinxdoc   5.3.0-4
ii  python3   3.11.2-1+b1
ii  python3-flask 2.2.2-3
ii  python3-pygments  2.14.0+dfsg-1

bepasty recommends no packages.

bepasty suggests no packages.

-- no debconf information

Bug#1032972: handbrake: debian version of handbrake does NOT handle subtitles correctly

[Alain Ducharme]

Package: handbrake-cli
Version: 1.6.1+ds1-1

Ouch, yes, to confirm, upgraded to bookworm and now subtitles are broken
when using HandBrake to convert DVD to .mkv
(worked in bullseye handbrake-cli 1.3.1+ds1-2 and previous versions)

The problem occurs with all DVD subs I tried, both types: VOBSUB and CC608

# Example command:
HandBrakeCLI -i /dev/sr0 -o "7r0N.mkv" -t 1 -s 1 # Title 1, subtitle track 1

Produces lots of decavsub warnings (I'm guessing for every subtitle frame):
[warning] decavsub: track 1, invalid PTS

Result: video ok, but subtitles do not appear and/or not at the correct times.

upstream: https://github.com/HandBrake/HandBrake/issues/4029
...Handbrake depends on custom ffmpeg patches, hmmm...?

Bug#1027731: aeskulap: Depends on deprecated libglademm2.4

[Simon McVittie]

On Mon, 02 Jan 2023 at 16:12:54 +0100, Bastian Germann wrote:
> aeskulap is one of two packages that depend on libglademm2.4.
> Can we get rid of this dependency to eliminate it from the archive?

It is now the only package that depends on libglademm2.4:

smcv@coccia ~ % dak rm -R -n libglademm2.4
...
Checking reverse dependencies...
# Broken Depends:
aeskulap: aeskulap

# Broken Build-Depends:
aeskulap: libglademm-2.4-dev

so porting it from libglade('s C++ bindings) to GtkBuilder would have a
disproportionate impact on the number of unmaintained libraries needed
in the archive.

libglade was superseded by GtkBuilder in GTK 2.12, released in 2007.
Moving from libglade to GtkBuilder would be a good first step towards
replacing GTK 2 with GTK 3.

A porting guide is provided in the GTK 2 documentation:
https://developer.gnome.org/gtk2/stable/gtk-migrating-GtkBuilder.html

smcv

Bug#1038451: bullseye-pu: package systemd/247.3-7+deb11u4

[Luca Boccassi]

Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian.org at packages.debian.org
Usertags: pu
X-Debbugs-CC: pkg-systemd-maintainers at lists.alioth.debian.org

Dear release team,

I have uploaded one new bugfix for systemd in bullseye. It is a
backport of two upstream patches to fix a calendar spec calculation
hang on DST change when TZ=Europe/Dublin as reported by Bullseye users
at #1033540.

The source debdiff is attached.

-- 
Kind regards,
Luca Boccassi
diff -Nru systemd-247.3/debian/changelog systemd-247.3/debian/changelog
--- systemd-247.3/debian/changelog	2023-04-30 13:56:31.0 +0100
+++ systemd-247.3/debian/changelog	2023-06-18 15:55:54.0 +0100
@@ -1,3 +1,10 @@
+systemd (247.3-7+deb11u4) bullseye; urgency=medium
+
+  * backport patches to fix a calendar spec calculation hang on DST change
+if TZ=Europe/Dublin (Closes: #1033540)
+
+ -- Luca Boccassi   Sun, 18 Jun 2023 15:55:54 +0100
+
 systemd (247.3-7+deb11u3) bullseye; urgency=medium
 
   * udev: fix creating /dev/serial/by-id/ symlinks for USB devices.
diff -Nru systemd-247.3/debian/patches/series systemd-247.3/debian/patches/series
--- systemd-247.3/debian/patches/series	2023-04-30 13:51:17.0 +0100
+++ systemd-247.3/debian/patches/series	2023-06-18 15:55:16.0 +0100
@@ -37,6 +37,8 @@
 time-util-fix-buffer-over-run.patch
 machined-varlink-fix-double-free.patch
 Always-free-deserialized_subscribed-on-reload.patch
+shared-calendarspec-abort-calculation-after-1000-iteratio.patch
+shared-calendarspec-when-mktime-moves-us-backwards-jump-f.patch
 debian/Use-Debian-specific-config-files.patch
 debian/Bring-tmpfiles.d-tmp.conf-in-line-with-Debian-defaul.patch
 debian/Make-run-lock-tmpfs-an-API-fs.patch
diff -Nru systemd-247.3/debian/patches/shared-calendarspec-abort-calculation-after-1000-iteratio.patch systemd-247.3/debian/patches/shared-calendarspec-abort-calculation-after-1000-iteratio.patch
--- systemd-247.3/debian/patches/shared-calendarspec-abort-calculation-after-1000-iteratio.patch	1970-01-01 01:00:00.0 +0100
+++ systemd-247.3/debian/patches/shared-calendarspec-abort-calculation-after-1000-iteratio.patch	2023-06-18 15:55:16.0 +0100
@@ -0,0 +1,55 @@
+From: =?utf-8?q?Zbigniew_J=C4=99drzejewski-Szmek?= 
+Date: Sun, 21 Mar 2021 20:59:32 +0100
+Subject: shared/calendarspec: abort calculation after 1000 iterations
+
+We have a bug where we seem to enter an infinite loop when running in the
+Europe/Dublin timezone. The timezone is "special" because it has negative SAVE
+values. The handling of this should obviously be fixed, but let's use a
+belt-and-suspenders approach, and gracefully fail if we fail to find an answer
+within a specific number of attempts. The code in this function is rather
+complex, and it's hard to rule out another bug in the future.
+
+(cherry picked from commit 169615c9a8cdc54d748d4dfc8279be9b3c2bec44)
+---
+ src/shared/calendarspec.c | 14 +-
+ 1 file changed, 13 insertions(+), 1 deletion(-)
+
+diff --git a/src/shared/calendarspec.c b/src/shared/calendarspec.c
+index 7162592..80acc57 100644
+--- a/src/shared/calendarspec.c
 b/src/shared/calendarspec.c
+@@ -1211,6 +1211,10 @@ static bool matches_weekday(int weekdays_bits, const struct tm *tm, bool utc) {
+ return (weekdays_bits & (1 << k));
+ }
+ 
++/* A safety valve: if we get stuck in the calculation, return an error.
++ * C.f. https://bugzilla.redhat.com/show_bug.cgi?id=1941335. */
++#define MAX_CALENDAR_ITERATIONS 1000
++
+ static int find_next(const CalendarSpec *spec, struct tm *tm, usec_t *usec) {
+ struct tm c;
+ int tm_usec;
+@@ -1224,7 +1228,7 @@ static int find_next(const CalendarSpec *spec, struct tm *tm, usec_t *usec) {
+ c = *tm;
+ tm_usec = *usec;
+ 
+-for (;;) {
++for (unsigned iteration = 0; iteration < MAX_CALENDAR_ITERATIONS; iteration++) {
+ /* Normalize the current date */
+ (void) mktime_or_timegm(, spec->utc);
+ c.tm_isdst = spec->dst;
+@@ -1321,6 +1325,14 @@ static int find_next(const CalendarSpec *spec, struct tm *tm, usec_t *usec) {
+ *usec = tm_usec;
+ return 0;
+ }
++
++/* It seems we entered an infinite loop. Let's gracefully return an error instead of hanging or
++ * aborting. This code is also exercised when timers.target is brought up during early boot, so
++ * aborting here is problematic and hard to diagnose for users. */
++_cleanup_free_ char *s = NULL;
++(void) calendar_spec_to_string(spec, );
++return log_warning_errno(SYNTHETIC_ERRNO(EDEADLK),
++ "Infinite loop in calendar calculation: %s", strna(s));
+ }
+ 
+ static int calendar_spec_next_usec_impl(const CalendarSpec *spec, usec_t usec, usec_t *ret_next) {
diff -Nru systemd-247.3/debian/patches/shared-calendarspec-when-mktime-moves-us-backwards-jump-f.patch 

Bug#1038163:

[Richard Lewis]

ill reply later,  with a proper patch (or MR if i can find the right place
on salsa) but in the meantime, the NEWS.Debian in the logcheck-database
package has details of how to support both formats in case people find this
an issue

Bug#1038450: coq-unimath FTBFS on 32bit

[Adrian Bunk]

Source: coq-unimath
Version: 20230420-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=coq-unimath=20230420-2

...
COQC 
UniMath/CategoryTheory/Monoidal/AlternativeDefinitions/EquivalenceWhiskeredNonCurriedMonoidalCategories.v
File 
"./UniMath/CategoryTheory/Monoidal/AlternativeDefinitions/EquivalenceWhiskeredNonCurriedMonoidalCategories.v",
 line 333, characters 2-10:
Error: Anomaly "Uncaught exception Invalid_argument("String.create")."
Please report at http://coq.inria.fr/bugs/.

make[4]: *** [build/CoqMakefile.make:844: 
UniMath/CategoryTheory/Monoidal/AlternativeDefinitions/EquivalenceWhiskeredNonCurriedMonoidalCategories.vo]
 Error 129

Bug#1038393: supertux: improve d/watch file

[Reiner Herrmann]

Hi Patrick,

thank you for the watch file improvement.
With your change the auto-generated tarball from Github is getting
downloaded, not the official release tarball (e.g.
SuperTux-v0.6.3-Source.tar.gz), which also contains the git submodules
(some of them are needed in the build).
Can you please try to change it so that the official tarball can be
downloaded?

Thanks!

Kind regards,
  Reiner


signature.asc
Description: PGP signature

Bug#1020495: Duplicate of #1036607, of closing via forcemerge

[Ian Jackson]

Control: reassign -1 network-manager-strongswan
Control: forcemerge 1036607 -1

This bug is a duplicate of #1036607, which has been fixed in
unstable.  We're also preparing an update to stable.

Ian.

-- 
Ian JacksonThese opinions are my own.  

Pronouns: they/he.  If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.

Bug#1038383: lsb_release: please add the ability to guess_release_from_apt()

[Gioele Barabucci]

On 18/06/23 12:58, Harshula wrote:
Perhaps the best option is to refer this to the Technical Committee to 
see if there's a way we can move forward?


Hi Harshula,

there are three open questions here:

1) should Debian provide a way to distinguish between the two 
similar-but-not-identical, rolling, ephemeral releases called "testing" 
and "staging" via /etc/os-release, the current cross-distro facility for 
this purpose? (I believe it should)


and

2) is it acceptable to ask 3rd party software (e.g., ansible [1]) to 
deal with the fact that Debian is the only major distro that does not 
provide a cross-distro way to tell apart its two development releases? 
(I believe it is not reasonable)


and

3) should the Debian packaging of lsb-release-minimal include an ad-hoc 
patch that extends it to use heuristics to guess a piece of info what 
Debian explicitly does not want to provide? (I believe it should not)


I doubt that these issues are important enough to be worth the attention 
of the Technical Committee, in particular issue 3 (Debian stopped 
supporting LSB in 2015, there are way better cross-distro facilities).


But if in your opinion these issues are important and you are willing to 
coordinate (off-BTS) the writing of a summary of this issue to refer to 
tech-ctte, I'll be happy to provide you with all the context and 
information I have.


[1] https://bugs.debian.org/931197#37

Regards,

--
Gioele Barabucci

Bug#1038449: magics++: Stop using netcdf-cxx-legacy

[Bas Couwenberg]

Source: magics++
Version: 4.13.0-1
Severity: important
Tags: patch
User: debian-...@lists.debian.org
Usertags: netcdf-cxx-legacy-rm

Dear Maintainer,

Your package uses netcdf-cxx-legacy which is dead upstream and will be removed 
during the trixie development cycle.

The attached patch only drops the build dependency, as your package doesn't 
actually link to netcdf-cxx-legacy.

Kind Regards,

Bas
diff -Nru magics++-4.13.0/debian/changelog magics++-4.13.0/debian/changelog
--- magics++-4.13.0/debian/changelog2022-11-23 16:01:57.0 +0100
+++ magics++-4.13.0/debian/changelog2023-06-18 15:26:12.0 +0200
@@ -1,3 +1,10 @@
+magics++ (4.13.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Stop using netcdf-cxx-legacy.
+
+ -- Bas Couwenberg   Sun, 18 Jun 2023 15:26:12 +0200
+
 magics++ (4.13.0-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru magics++-4.13.0/debian/control magics++-4.13.0/debian/control
--- magics++-4.13.0/debian/control  2022-11-23 16:01:57.0 +0100
+++ magics++-4.13.0/debian/control  2023-06-18 15:25:58.0 +0200
@@ -7,7 +7,7 @@
  gfortran | fortran-compiler, 
  python3-all-dev,
  libhdf5-dev | libhdf5-mpi-dev, 
- libnetcdf-dev, libnetcdf-cxx-legacy-dev,
+ libnetcdf-dev,
  libgl1-mesa-dev, libgd-dev, 
  libemos-dev (>=  2:4.3.9), libgeotiff-dev,
  libeccodes-dev (>= 2.13.0-3),

Bug#1038447: librsvg: FTBFS on big-endian architectures: multiple test regressions since September 2022

[John Paul Adrian Glaubitz]

> On Jun 18, 2023, at 3:53 PM, Simon McVittie  wrote:
> 
> On Sun, 18 Jun 2023 at 14:47:00 +0100, Simon McVittie wrote:
>> I rebuilt librsvg in bookworm on the s390x porterbox zelenka, and can
>> confirm that 2.54.5+dfsg-1 now fails in bookworm too. So something must
>> have triggered a regression between September 2022 and now.
> 
> It would be helpful if someone with suitable hardware could put this
> through debbisect or similar to find out which build-dependency triggered
> this.

TIL about debbisect. I can try to bisect this on big-endian PowerPC, I have 
root on multiple big-endian machines.

Adrian

Bug#1038447: librsvg: FTBFS on big-endian architectures: multiple test regressions since September 2022

[Simon McVittie]

On Sun, 18 Jun 2023 at 14:47:00 +0100, Simon McVittie wrote:
> I rebuilt librsvg in bookworm on the s390x porterbox zelenka, and can
> confirm that 2.54.5+dfsg-1 now fails in bookworm too. So something must
> have triggered a regression between September 2022 and now.

It would be helpful if someone with suitable hardware could put this
through debbisect or similar to find out which build-dependency triggered
this. I don't intend to do this myself, since emulating a big-endian
architecture on x86 is going to be a lot slower and more power-hungry, and
as far as I'm aware I don't have the ability to install older packages of
my choice on a porterbox (which don't allow unprivileged users to create
new user namespaces).

Thanks,
smcv

Bug#1038447: librsvg: FTBFS on big-endian architectures: multiple test regressions since September 2022

[Simon McVittie]

On Sun, 18 Jun 2023 at 13:40:09 +0100, Simon McVittie wrote:
> librsvg 2.54.5+dfsg-2 failed to build on s390x, powerpc and ppc64 with
> multiple test failures. At first glance, they seem to be the same test
> failures, meaning this is about endianness rather than any specific
> architecture.
> 
> 2.54.5+dfsg-2 only contains packaging changes and no code changes,
> so I strongly suspect (but have not actually proved) that rebuilding
> 2.54.5+dfsg-1 with current versions of its dependencies would also
> exhibit the same test failures, similar to #1038252 on i386.

I rebuilt librsvg in bookworm on the s390x porterbox zelenka, and can
confirm that 2.54.5+dfsg-1 now fails in bookworm too. So something must
have triggered a regression between September 2022 and now.

smcv

Bug#1038448: aptitude: sometimes aptitude prefers foreign architectures when using safe-upgrade

[Konomi]

Package: aptitude
Version: 0.8.13-5
Severity: important
X-Debbugs-Cc: konomikit...@gmail.com

Dear Maintainer,

Sometimes aptitude makes bad choices when safe-upgrade is used, the problem
is probably in the aptitude resolver. Here is an example of this happening:

$ sudo aptitude safe-upgrade linux-headers-amd64
Resolving dependencies...
The following NEW packages will be installed:
  linux-headers-6.3.0-1-amd64{a} linux-headers-6.3.0-1-common{a} linux-
kbuild-6.3:i386{a}
The following packages will be upgraded:
  linux-headers-amd64
1 packages upgraded, 3 newly installed, 0 to remove and 33 not upgraded.
Need to get 0 B/12.0 MB of archives. After unpacking 63.8 MB will be used.

Here aptitude wants to install linux-kbuild-6.3:i386 instead of
linux-kbuild-6.3:amd64. If I switch to using full-upgrade I get the following:

$ sudo aptitude full-upgrade linux-headers-amd64
The following NEW packages will be installed:
  linux-doc-6.3{a} linux-headers-6.3.0-1-amd64{a} linux-
headers-6.3.0-1-common{a}
  linux-image-6.3.0-1-amd64{a} linux-kbuild-6.3{a}
The following packages will be upgraded:
  libcpupower1 linux-cpupower linux-doc linux-headers-amd64 linux-image-amd64
linux-libc-dev
6 packages upgraded, 5 newly installed, 0 to remove and 28 not upgraded.
Need to get 914 kB/124 MB of archives. After unpacking 718 MB will be used.

This actually caused a dkms module to stop compiling:

DKMS make.log for it87-20230126 for kernel 6.3.0-1-amd64 (x86_64)
Thu 15 Jun 2023 14:12:15 AEST
  CC [M]  /var/lib/dkms/it87/20230126/build/it87.o
  MODPOST /var/lib/dkms/it87/20230126/build/Module.symvers
FATAL: modpost: /var/lib/dkms/it87/20230126/build/it87: sizeof(struct
dmi_device_id)=332 is not a modulo of the size of section
__mod_dmi___device_table=7224.
Fix definition of struct dmi_device_id in mod_devicetable.h
make[2]: *** [/usr/src/linux-
headers-6.3.0-1-common/scripts/Makefile.modpost:136:
/var/lib/dkms/it87/20230126/build/Module.symvers] Error 1
make[1]: *** [/usr/src/linux-headers-6.3.0-1-common/Makefile:2002: modpost]
Error 2
make: *** [Makefile:73: modules] Error 2

After changing linux-kbuild to amd64 the module builds correctly again:

Building module:
Cleaning build area...
make -j12 KERNELRELEASE=6.3.0-1-amd64 TARGET=6.3.0-1-amd64...
Signing module /var/lib/dkms/it87/20230126/build/it87.ko
Cleaning build area...

it87.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/6.3.0-1-amd64/updates/dkms/
depmod...
Sign command: /usr/lib/linux-kbuild-6.3/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

A Debian user in #debian-apt suggested I try pinning the i386 architecture to
400 but this had no effect on aptitude's resolver choices. The concern here
being in what ways could aptitude break a Debian install if it decides to
install foreign packages over native ones?


-- Package-specific info:
Terminal: xterm-256color
$DISPLAY is set.
which aptitude: /usr/bin/aptitude

aptitude version information:
aptitude 0.8.13
Compiler: g++ 12.1.0
Compiled against:
  apt version 6.0.0
  NCurses version 6.3
  libsigc++ version: 2.10.8
  Gtk+ support disabled.
  Qt support disabled.

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

aptitude linkage:
linux-vdso.so.1 (0x7ffd3e8d5000)
libapt-pkg.so.6.0 => /lib/x86_64-linux-gnu/libapt-pkg.so.6.0 
(0x7f9b85c05000)
libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6 
(0x7f9b85bcb000)
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 
(0x7f9b85b98000)
libsigc-2.0.so.0 => /lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7f9b8623f000)
libcwidget.so.4 => /lib/x86_64-linux-gnu/libcwidget.so.4 
(0x7f9b85aa6000)
libsqlite3.so.0 => /lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7f9b85947000)
libboost_iostreams.so.1.74.0 => 
/lib/x86_64-linux-gnu/libboost_iostreams.so.1.74.0 (0x7f9b86225000)
libxapian.so.30 => /lib/x86_64-linux-gnu/libxapian.so.30 
(0x7f9b8560)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f9b8622)
libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f9b8520)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f9b85868000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f9b85844000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f9b8501f000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f9b855e1000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7f9b85831000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f9b855b2000)
liblz4.so.1 => /lib/x86_64-linux-gnu/liblz4.so.1 (0x7f9b8558c000)
libzstd.so.1 => /lib/x86_64-linux-gnu/libzstd.so.1 (0x7f9b854d)
libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 

Bug#1038426: renpy: Uncaught exception occurred when attempting to start

[Markus Koschany]

Control: severity -1 grave
Control: tags -1 help

Am Sonntag, dem 18.06.2023 um 04:23 + schrieb Zach:
>  File "/usr/share/games/renpy/renpy/sl2/slast.py", line 84, in compile_expr
>     return compile(expr, filename, "eval", flags, 1)
> ValueError: AST node line range (628, 1) is not valid

Thanks for the report. I can reproduce this problem in stable and unstable but
I don't know what is causing the Python error at the moment. In any case this
makes the game unusable and must be fixed eventually.

Regards,

Markus


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

Bug#1038447: librsvg: FTBFS on big-endian architectures: multiple test regressions since September 2022

[Simon McVittie]

Source: librsvg
Version: 2.54.5+dfsg-1
Severity: serious
Tags: ftbfs help
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: debian-s...@lists.debian.org, debian-powe...@lists.debian.org, 
ru...@packages.debian.org
Forwarded: https://gitlab.gnome.org/GNOME/librsvg/-/issues/972

librsvg 2.54.5+dfsg-2 failed to build on s390x, powerpc and ppc64 with
multiple test failures. At first glance, they seem to be the same test
failures, meaning this is about endianness rather than any specific
architecture.

2.54.5+dfsg-2 only contains packaging changes and no code changes,
so I strongly suspect (but have not actually proved) that rebuilding
2.54.5+dfsg-1 with current versions of its dependencies would also
exhibit the same test failures, similar to #1038252 on i386.
The specific tests that are failing here are not the same as #1038252.

The failing tests here are "reftests", which render a SVG image to PNG
and compare the result with a known-good PNG. These are difficult to
investigate in a buildd log, because they're very visual, but the librsvg
buildd logs export the output images using uuencode, and I have extracted
them from the s390x log and used them to open upstream bugs which show
the rendering issue visually:

- https://gitlab.gnome.org/GNOME/librsvg/-/issues/972
- https://gitlab.gnome.org/GNOME/librsvg/-/issues/973
- https://gitlab.gnome.org/GNOME/librsvg/-/issues/974
- https://gitlab.gnome.org/GNOME/librsvg/-/issues/975
- https://gitlab.gnome.org/GNOME/librsvg/-/issues/976
- https://gitlab.gnome.org/GNOME/librsvg/-/issues/977
- https://gitlab.gnome.org/GNOME/librsvg/-/issues/978
- https://gitlab.gnome.org/GNOME/librsvg/-/issues/979
- https://gitlab.gnome.org/GNOME/librsvg/-/issues/980
- https://gitlab.gnome.org/GNOME/librsvg/-/issues/981
- https://gitlab.gnome.org/GNOME/librsvg/-/issues/982
- https://gitlab.gnome.org/GNOME/librsvg/-/issues/983
- https://gitlab.gnome.org/GNOME/librsvg/-/issues/984

In all cases, the standalone steps to reproduce would be: render the SVG
to PNG; look at the SVG and its reference rendering side-by-side; and the
expected result is that they look the same.

The most likely trigger for regressions between September 2022 and now
would seem to be the upgrade of rustc from 1.61 to 1.63, since Cairo
has not had significant changes for a while, none of the rendering
differences involve text/fonts, and librsvg seems to do all its non-text
rendering using vendored Rust libraries or its own Rust code rather than
an external library like libpng.

smcv

Bug#945269: debian-policy: packages should use tmpfiles.d(5) to create directories below /var

[Luca Boccassi]

On Sun, 18 Jun 2023 at 13:03, Sean Whitton  wrote:
>
> Hello,
>
> On Fri 16 Jun 2023 at 05:57PM +01, Luca Boccassi wrote:
>
> > Is there anything needed from me to make progress on this? Any changes
> > required to the last revision posted?
>
> Yes, Russ posted some comments on your most recent revision, I believe.

Last one I can find with specifics is:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945269#140

Which I think I have addressed in a follow-up. Did I miss something?

Kind regards,
Luca Boccassi

Bug#932957: no longer build arch-dependent variants of r-n?

[Holger Wansing]

Hi,

Holger Wansing  wrote (Wed, 14 Jun 2023 21:50:18 +0200):
> Paul Gevers  wrote (Wed, 14 Jun 2023 21:19:00 +0200):
> > Also, on the topic of arch-specific builds, I not convinced it's worth a 
> > lot of effort. The amount of arch specific pieces is rather limited, so 
> > I wouldn't mind if we drop that altogether. Currently, we don't do a 
> > great service to people that need to support multiple architectures, 
> > because they need to *search* for the delta's, so I wouldn't be 
> > surprised if it is even better if we drop it.
> 
> From the technical side, I managed to get the arch-specific builds done in
> the meantime basically; so no problem anymore there - theoretically.
> 
> On the other side, I also thought about the arch-specific differences, and
> given they are only rather small, my assumption was, that it's maybe not worth
> it to differentiate between archs, when it comes to filtering out content
> of r-n depending on the architecture.
> But even if we leave that point out, there are some arch-dependent links like
> http://mirrors.kernel.org/debian/dists/bookworm/main/binary-amd64/...
> in chapter 4.3.1
> https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html#network
> 
> So, we still need to build the release-notes differentiated by archs
> (based on the current content).
> 
> 
> 
> However, that does not mean, we could not change our base rules, so that
> filtering out chapters based on architecture is no longer used.
> I would vote for this solution, yes.

Thinking a bit more about this, I wonder if we could indeed get rid of 
architecture-dependent r-n at all.

If all paragraphs/chapters are visible for all archs anyway, there are
only two situations where the arch shortname (amd64, i386 etc.) is used
in URLs. That is in
https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html#network
and
https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html#localmirror


   For example, suppose your closest Debian mirror is 
http://mirrors.kernel.org. 
   If you inspect that mirror with a web browser, you will notice that the main 
   directories are organized like this:

   http://mirrors.kernel.org/debian/dists/bookworm/main/binary-amd64/...
   http://mirrors.kernel.org/debian/dists/bookworm/contrib/binary-amd64/...

   To configure APT to use a given mirror, add a line like this (again, 
   assuming you are using main and contrib):

   deb http://mirrors.kernel.org/debian bookworm main contrib


So, the arch-dependent directories on the mirrors are mentioned here, but the
arch part is not really relevant here. We could just skip the last part of 
the URL and point to
http://mirrors.kernel.org/debian/dists/bookworm/main/..
and that's it. The same counts for the second occurrence of arch shortname.

That gives us the possibility, to simplify the whole r-n thing to only build 
one generic release-notes variant for all archs, in the different languages, 
and we are done.

How does that sound?


Holger



-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Bug#1037917: gnutls28: leaves processes running after build: gnutls-serv, openssl s_server

[Andreas Metzler]

On 2023-06-14 Andreas Metzler  wrote:
> On 2023-06-14 Andreas Beckmann  wrote:
[...]
> > after building gnutls28/experimental with pbuilder, there are a lot of
> > gnutls-serv and a few openssl s_server processes running, preventing
> > pbuilder to cleanup the chroot.

> This was caused by the changes related to fixing #1031553 (supporting
> either datefudge or faketime.

The reasons for breakage are twofold:

when using a wrapper shell-function instead of an executable like this:

wrapme() {
foo "$@"
}

This kind of code breaks

wrapme server &
PID=$!
...
kill $PID

since PID will contain the process ID of the currently running script
instead of "foo server".

The second one is a similar one. While
datefudge ... server
gives you one process - the server one (datefudge is a shell script
which sets some environment variables and exec-s the a binary.) OTOH
faketime  ... server
starts a faketime process and a forked "server" as child process and
killing faketime does not kill the child process (Reported as
https://github.com/wolfcw/libfaketime/issues/428 ). This also breaks the
idiom mentioned above.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1038446: linux-image-6.1.0-9-amd64: "SGX disabled by BIOS" message is printed at boot, but SGX is set to Software Controlled in UEFI.

[Yura]

Package: src:linux
Version: 6.1.27-1
Severity: minor
Tags: upstream
X-Debbugs-Cc: splashed_overbuilt...@simplelogin.com

Dear Maintainer,

When system boots before the Plymouth screen is shown, it prints "SGX
disabled by BIOS" message. This doesn't affect the boot process.

In my BIOS/UEFI settings Software Guard Extensions are set to "Software
Controlled". There are only "Software Controlled" and "Disable" options
available. The situation wasn't reproducible with Bullseye. It only
appeared with upgrade to Bookworm.

This message shouldn't be printed if SGX is set to "Software
Controlled", or, ideally, it shouldn't be printed at all.

Best Regards,
Yura

-- Package-specific info:
** Version:
Linux version 6.1.0-9-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 
12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP 
PREEMPT_DYNAMIC Debian 6.1.27-1 (2023-05-08)

** Command line:
BOOT_IMAGE=/vmlinuz-6.1.0-9-amd64 root=/dev/mapper/MainVG-root ro quiet splash

** Not tainted

** Model information
sys_vendor: System manufacturer
product_name: System Product Name
product_version: System Version
chassis_vendor: Default string
chassis_version: Default string
bios_vendor: American Megatrends Inc.
bios_version: 3805
board_vendor: ASUSTeK COMPUTER INC.
board_name: Z170-K
board_version: Rev X.0x

** Loaded modules:
exfat
xt_CHECKSUM
xt_MASQUERADE
nft_chain_nat
nf_nat
bridge
stp
llc
qrtr
ip6t_REJECT
nf_reject_ipv6
xt_hl
ip6_tables
ip6t_rt
ipt_REJECT
nf_reject_ipv4
xt_LOG
nf_log_syslog
xt_comment
nft_limit
xt_limit
xt_addrtype
xt_tcpudp
xt_conntrack
nf_conntrack
nf_defrag_ipv6
nf_defrag_ipv4
nft_compat
nf_tables
libcrc32c
nfnetlink
binfmt_misc
nls_ascii
nls_cp437
vfat
fat
intel_rapl_msr
snd_hda_codec_realtek
intel_rapl_common
snd_hda_codec_generic
x86_pkg_temp_thermal
intel_powerclamp
snd_hda_codec_hdmi
coretemp
snd_hda_intel
kvm_intel
snd_intel_dspcfg
snd_intel_sdw_acpi
snd_hda_codec
uvcvideo
kvm
snd_usb_audio
eeepc_wmi
snd_hda_core
videobuf2_vmalloc
asus_wmi
snd_usbmidi_lib
videobuf2_memops
irqbypass
snd_rawmidi
videobuf2_v4l2
snd_hwdep
platform_profile
snd_seq_device
rapl
battery
videobuf2_common
mei_hdcp
sparse_keymap
snd_pcm
intel_cstate
iTCO_wdt
ledtrig_audio
snd_timer
intel_pmc_bxt
rfkill
intel_uncore
videodev
iTCO_vendor_support
mei_me
snd
watchdog
pcspkr
wmi_bmof
ee1004
mc
mei
soundcore
intel_pmc_core
acpi_pad
evdev
sg
parport_pc
ppdev
lp
parport
fuse
loop
efi_pstore
configfs
efivarfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
hid_logitech_hidpp
dm_crypt
dm_mod
hid_logitech_dj
hid_generic
usbhid
hid
uas
usb_storage
sd_mod
t10_pi
crc64_rocksoft_generic
crc64_rocksoft
crc_t10dif
crct10dif_generic
crc64
amdgpu
crct10dif_pclmul
crct10dif_common
crc32_pclmul
crc32c_intel
ghash_clmulni_intel
sha512_ssse3
sha512_generic
gpu_sched
drm_buddy
i2c_algo_bit
drm_display_helper
cec
rc_core
ahci
drm_ttm_helper
libahci
ttm
xhci_pci
drm_kms_helper
libata
xhci_hcd
r8169
aesni_intel
drm
mxm_wmi
realtek
usbcore
crypto_simd
mdio_devres
scsi_mod
cryptd
libphy
i2c_i801
i2c_smbus
usb_common
scsi_common
fan
video
wmi
button

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:591f] (rev 05)
Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers [1043:8694]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

00:01.0 PCI bridge [0604]: Intel Corporation 6th-10th Gen Core Processor PCIe 
Controller (x16) [8086:1901] (rev 05) (prog-if 00 [Normal decode])
Subsystem: ASUSTeK Computer Inc. 6th-10th Gen Core Processor PCIe 
Controller (x16) [1043:8694]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:14.0 USB controller [0c03]: Intel Corporation 100 Series/C230 Series Chipset 
Family USB 3.0 xHCI Controller [8086:a12f] (rev 31) (prog-if 30 [XHCI])
Subsystem: ASUSTeK Computer Inc. 100 Series/C230 Series Chipset Family 
USB 3.0 xHCI Controller [1043:8694]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

00:16.0 Communication controller [0780]: Intel Corporation 100 Series/C230 
Series Chipset Family MEI Controller #1 [8086:a13a] (rev 31)
Subsystem: ASUSTeK Computer Inc. 100 Series/C230 Series Chipset Family 
MEI Controller [1043:8694]
Control: I/O- Mem+ 

Bug#907384: Bug#1037996: Acknowledgement (xfce4: xfce-Desktop will be crashed at start and than black Desktop)

[Dr. Hanisch]

Hello,
the Str+Alt+h is only a pragmatic solution for the problem.
Please fix the bug in xfce4-session, xfce-panel or other package.

--
Mein öffentlicher Schlüssel ist auf dem Keyserver 'https://keys.openpgp.org' 
unterch-hani...@t-online.de  (E53DF487)

Bug#945269: debian-policy: packages should use tmpfiles.d(5) to create directories below /var

[Sean Whitton]

Hello,

On Fri 16 Jun 2023 at 05:57PM +01, Luca Boccassi wrote:

> Is there anything needed from me to make progress on this? Any changes
> required to the last revision posted?

Yes, Russ posted some comments on your most recent revision, I believe.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#1028132: now ready

[Rene Engelhard]

Hi,

hunspell-dict-ko was fixed/worked around the issue (0.7.94-1) so we can 
do this now.


As said it's a no-op for anything except r-cran-hunspell which also is 
prepared in experimental together with hunspell itself.


I might add a libhunspell-private-dev package later when I figured out 
how to best prevent this by adding a strict dependency there instead of 
hardcoding it... But even without that it's better to not have a copy of 
private headers in r-cran-hunspell.


Can I upload to unstable?

Regards,

Rene

Bug#1033560: kup-backup: not translated while upstream translation exists

[Frédéric Mesplède]

Package: kup-backup
Version: 0.9.1-1+b3
Followup-For: Bug #1033560
X-Debbugs-Cc: fredericmespl...@gmail.com

Dear Maintainer,
Kup is not translated when accessed from the tray icon.

*** 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 ***


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

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

Versions of packages kup-backup depends on:
ii  kio5.103.0-1
ii  libc6  2.36-9
ii  libgcc-s1  12.2.0-14
ii  libgit2-1.51.5.1+ds-1
ii  libkf5completion5  5.103.0-1
ii  libkf5configcore5  5.103.0-2
ii  libkf5configwidgets5   5.103.0-1
ii  libkf5coreaddons5  5.103.0-1
ii  libkf5dbusaddons5  5.103.0-1
ii  libkf5i18n55.103.0-1
ii  libkf5idletime55.103.0-2
ii  libkf5jobwidgets5  5.103.0-1
ii  libkf5kiocore5 5.103.0-1
ii  libkf5kiofilewidgets5  5.103.0-1
ii  libkf5kiowidgets5  5.103.0-1
ii  libkf5notifications5   5.103.0-1
ii  libkf5plasma5  5.103.0-1
ii  libkf5solid5   5.103.0-1
ii  libkf5widgetsaddons5   5.103.0-1
ii  libkf5xmlgui5  5.103.0-1
ii  libqt5core5a   5.15.8+dfsg-11
ii  libqt5dbus55.15.8+dfsg-11
ii  libqt5gui5 5.15.8+dfsg-11
ii  libqt5network5 5.15.8+dfsg-11
ii  libqt5widgets5 5.15.8+dfsg-11
ii  libstdc++6 12.2.0-14

Versions of packages kup-backup recommends:
ii  bup0.33-2+b1
ii  rsync  3.2.7-1

kup-backup suggests no packages.

-- no debconf information

Bug#1038252: librsvg: FTBFS on i386: transform::tests::parses_transform_list, transform::tests::parses_valid_transform failed

[Simon McVittie]

Control: found -1 2.54.5+dfsg-1
Control: forwarded -1 https://gitlab.gnome.org/GNOME/librsvg/-/issues/871

On Fri, 16 Jun 2023 at 21:11:21 +0100, Simon McVittie wrote:
> On Fri, 16 Jun 2023 at 21:00:13 +0200, Sebastian Ramacher wrote:
> > https://buildd.debian.org/status/fetch.php?pkg=librsvg=i386=2.54.5%2Bdfsg-2=1686829500=0
> > 
> >  transform::tests::parses_transform_list stdout 
> > thread 'transform::tests::parses_transform_list' panicked at 'assertion 
> > failed: t1.y0.approx_eq(t2.y0, (epsilon, 1))', src/transform.rs:716:9
> > 
> >  transform::tests::parses_valid_transform stdout 
> > thread 'transform::tests::parses_valid_transform' panicked at 'assertion 
> > failed: t1.y0.approx_eq(t2.y0, (epsilon, 1))', src/transform.rs:716:9
> 
> This might be i387 excess precision resulting in rounding errors on i386
> that differ from what happens on other architectures, or it might be
> something unrelated.

Rebuilding 2.54.5+dfsg-1 in bookworm has similar behaviour, which means
this is a behaviour change in build-dependency packages, rather than a
result of a change in librsvg. One possible trigger is the upgrade of rustc
1.61 to 1.63.

smcv

Bug#1038445: When in full-screen mode mpv gets minimized after switching Xfce workspaces

[Yura]

Package: mpv
Version: 0.35.1-4
Severity: normal
Tags: upstream
X-Debbugs-Cc: splashed_overbuilt...@simplelogin.com

Dear Maintainer,

The issue could be reproduced at the very least for users of Xfce
desktop environment, who have the mpv player opened on one workspace in a 
full-screen
mode. In addition, users of other distributions like Fedora Xfce might
also be affected.

If the user switches to a different workspace, for example, a second one
and then goes back to the one where mpv is opened, the player gets minimized. 

The expected behavior is that the application should remain in a full-screen 
mode without being minimized.

Best Regards,
Yura

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

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

Versions of packages mpv depends on:
ii  libarchive13   3.6.2-1
ii  libasound2 1.2.8-1+b1
ii  libass91:0.17.1-1
ii  libavcodec-extra59 [libavcodec59]  7:5.1.3-1
ii  libavdevice59  7:5.1.3-1
ii  libavfilter8   7:5.1.3-1
ii  libavformat59  7:5.1.3-1
ii  libavutil577:5.1.3-1
ii  libbluray2 1:1.3.4-1
ii  libc6  2.36-9
ii  libcaca0   0.99.beta20-3
ii  libcdio-cdda2  10.2+2.0.1-1
ii  libcdio-paranoia2  10.2+2.0.1-1
ii  libcdio19  2.1.0-4
ii  libdrm22.4.114-1+b1
ii  libdvdnav4 6.1.1-1
ii  libegl11.6.0-1
ii  libgbm122.3.6-1+deb12u1
ii  libjack-jackd2-0 [libjack-0.125]   1.9.21~dfsg-3
ii  libjpeg62-turbo1:2.1.5-2
ii  liblcms2-2 2.14-2
ii  liblua5.2-05.2.4-3
ii  libmujs2   1.3.2-1
ii  libpipewire-0.3-0  0.3.65-3
ii  libplacebo208  4.208.0-3
ii  libpulse0  16.1+dfsg1-2+b1
ii  librubberband2 3.1.2+dfsg0-1
ii  libsdl2-2.0-0  2.26.5+dfsg-1
ii  libsixel1  1.10.3-3
ii  libswresample4 7:5.1.3-1
ii  libswscale67:5.1.3-1
ii  libuchardet0   0.0.7-1
ii  libva-drm2 2.17.0-1
ii  libva-wayland2 2.17.0-1
ii  libva-x11-22.17.0-1
ii  libva2 2.17.0-1
ii  libvdpau1  1.5-2
ii  libvulkan1 1.3.239.0-1
ii  libwayland-client0 1.21.0-1
ii  libwayland-cursor0 1.21.0-1
ii  libwayland-egl11.21.0-1
ii  libx11-6   2:1.8.4-2
ii  libxext6   2:1.3.4-1+b1
ii  libxinerama1   2:1.1.4-3
ii  libxkbcommon0  1.5.0-1
ii  libxpresent1   1.0.0-2+b10
ii  libxrandr2 2:1.5.2-2+b1
ii  libxss11:1.2.3-1
ii  libxv1 2:1.0.11-1.1
ii  libzimg2   3.0.4+ds1-1
ii  zlib1g 1:1.2.13.dfsg-1

Versions of packages mpv recommends:
ii  xdg-utils  1.1.3-4.1
ii  yt-dlp 2023.03.04-1

Versions of packages mpv suggests:
pn  libcuda1  

-- no debconf information