date:20230520

Package: munin
Severity: wishlist
Tags: patch l10n

Hello,

You can find enclosed the Spanish translation template to be uploaded with the 
latest package build.

Kindly place this file in debian/po/ as es.po for your next upload.

Cheers,
-- 
Camaleón# Translation of munin debconf templates to Spanish.
# Copyright (C) 2023 Camaleón 
# This file is distributed under the same license as the munin package.
# Camaleón , 2023.
#
msgid ""
msgstr ""
"Project-Id-Version: munin\n"
"Report-Msgid-Bugs-To: mu...@packages.debian.org\n"
"POT-Creation-Date: 2019-08-04 17:40+0200\n"
"PO-Revision-Date: 2023-05-12 15:39+0200\n"
"Language-Team: Debian Spanish \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 2.4.2\n"
"Last-Translator: Camaleón \n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
"Language: es\n"

#. Type: boolean
#. Description
#: ../munin.templates:1001
msgid "Remove all RRD database files?"
msgstr "¿Eliminar todos los archivos de la base de datos RRD?"

#. Type: boolean
#. Description
#: ../munin.templates:1001
msgid ""
"The /var/lib/munin directory which contains the RRD files with the data "
"accumulated by munin is about to be removed."
msgstr ""
"Se va a eliminar el directorio «/var/lib/munin» que contiene los archivos "
"RRD con los datos que ha acumulado munin."

#. Type: boolean
#. Description
#: ../munin.templates:1001
msgid ""
"If you want to install munin later again or if you want to use the content "
"of the RRD files for other purposes, the data should be kept."
msgstr ""
"Si quiere volver a instalar munin posteriormente o usar el contenido de "
"los archivos RRD para otros fines, debe conservar estos datos."

Bug#1036373: [INTL:es] Spanish translation of hyperscan debconf template

Package: hyperscan
Severity: wishlist
Tags: patch l10n

Hello,

You can find enclosed the Spanish translation template to be uploaded with the 
latest package build.

Kindly place this file in debian/po/ as es.po for your next upload.

Cheers,
-- 
Camaleón# Translation of hyperscan debconf templates to Spanish.
# Copyright (C) 2023 Camaleón 
# This file is distributed under the same license as the hyperscan package.
# Camaleón , 2023.
#
msgid ""
msgstr ""
"Project-Id-Version: hyperscan\n"
"Report-Msgid-Bugs-To: hypers...@packages.debian.org\n"
"POT-Creation-Date: 2016-07-26 23:46+0200\n"
"PO-Revision-Date: 2023-05-12 15:57+0200\n"
"Language-Team: Debian Spanish \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 2.4.2\n"
"Last-Translator: Camaleón \n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
"Language: es\n"

#. Type: boolean
#. Description
#: ../libhyperscan5.templates:1001
msgid "Really install package?"
msgstr "¿Desea realmente instalar el paquete?"

#. Type: boolean
#. Description
#: ../libhyperscan5.templates:1001
msgid ""
"This CPU lacks support for the Supplemental Streaming SIMD Extensions 3 "
"(SSSE3) instruction set that is required to execute programs linked against "
"hyperscan."
msgstr ""
"El procesador de su equipo no admite el conjunto de instrucciones "
"Extensiones SIMD de streaming 3 (SSSE3) necesario para ejecutar programas "
"enlazados con hyperscan."

Bug#1036374: [INTL:es] Spanish translation of qcumber debconf template

Package: qcumber
Severity: wishlist
Tags: patch l10n

Hello,

You can find enclosed the Spanish translation template to be uploaded with the 
latest package build.

Kindly place this file in debian/po/ as es.po for your next upload.

Cheers,
-- 
Camaleón# Translation of qcumber debconf templates to Spanish.
# Copyright (C) 2023 Camaleón 
# This file is distributed under the same license as the qcumber package.
# Camaleón , 2023.
#
msgid ""
msgstr ""
"Project-Id-Version: qcumber\n"
"Report-Msgid-Bugs-To: qcum...@packages.debian.org\n"
"POT-Creation-Date: 2016-11-29 14:47+0100\n"
"PO-Revision-Date: 2023-05-12 16:17+0200\n"
"Language-Team: Debian Spanish \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 2.4.2\n"
"Last-Translator: Camaleón \n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
"Language: es\n"

#. Type: string
#. Description
#: ../templates:1001
msgid "Installation directory of the minikraken database:"
msgstr "Directorio de instalación de la base de datos minikraken:"

#. Type: string
#. Description
#: ../templates:1001
msgid ""
"QCumber is using kraken which needs a database.  To simplyfy the process of "
"creating the database which requires a lot of computing power there is the "
"option to download this database (see https://ccb.jhu.edu/software/";
"kraken/).  If you want to run QCumber the directory of the kraken database "
"needs to be known to the program.  Please input the directory the database "
"is installed or should the database be installed by the script /usr/share/"
"doc/qcumber/get-minikrakendb."
msgstr ""
"QCumber utiliza kraken por lo que necesita una base de datos. Para "
"simplificar el proceso de creación de la base de datos, que hace requiere "
"un uso intensivo de los recursos del sistema, puede descargar la base de "
"datos (consulte «https://ccb.jhu.edu/software/kraken/»). Si quiere ejecutar "
"QCumber, el programa necesita conocer la ubicación del directorio de la "
"base de datos de kraken. Introduzca el directorio donde se encuentra "
"instalada la base de datos o si se debe instalar la base de datos "
"utilizando el guión «/usr/share/doc/qcumber/get-minikrakendb»."

Bug#35970: gnumach hangs because of Linux 2.0.36 adaptec drivers

2023-05-20 Thread Petter Reinholdtsen

[Guillem Jover 2005]
> Can you reproduce #35970 with the latest gnumach packages?

[Santiago Vila 2005]
> 
> I don't know, and it is going to be quite difficult for me to check, because
> the computer is currently running woody as a server for a lot of people...

Is there any use keeping this issue open?  I suspect the hardware in
question has long since been retired and no-one is using the
Adaptec driver any more.

The upstream bug is also flagged with 'need more info', and if no-one
can provide the info, it seem useless to keep the issue open.

-- 
Happy hacking
Petter Reinholdtsen

Bug#1036375: [INTL:es] Spanish translation of isa-support debconf template

Package: isa-support
Severity: wishlist
Tags: patch l10n

Hello,

You can find enclosed the Spanish translation template to be uploaded with the 
latest package build.

Kindly place this file in debian/po/ as es.po for your next upload.

Cheers,
-- 
Camaleón# Translation of isa-support debconf templates to Spanish
# Copyright (C) 2023 Camaleón 
# This file is distributed under the same license as the isa-support package.
#
# Camaleón , 2023.
#
msgid ""
msgstr ""
"Project-Id-Version: isa-support\n"
"Report-Msgid-Bugs-To: isa-supp...@packages.debian.org\n"
"POT-Creation-Date: 2022-08-17 11:25+\n"
"PO-Revision-Date: 2023-05-12 16:41+0200\n"
"Language-Team: Debian Spanish \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 2.4.2\n"
"Last-Translator: Camaleón \n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
"Language: es\n"

#. Type: note
#. Description
#: ../@n...@-support.templates.in:1001
msgid "Support for @NAME@ required"
msgstr "Se requiere compatibilidad con @NAME@"

#. Type: note
#. Description
#: ../@n...@-support.templates.in:1001
msgid ""
"Alas, your machine doesn't support the @NAME@ instruction set.  It is needed "
"by software that depends on this dummy package.  Sorry."
msgstr ""
"Lamentablemente, parece que su equipo no admite el conjunto de instrucciones "
"@NAME@, necesario para el programa que depende de este paquete «dummy»."

#. Type: note
#. Description
#: ../@n...@-support.templates.in:1001
msgid "Aborting installation."
msgstr "Abortando la instalación."

Bug#1036376: [INTL:es] Spanish translation of depthcharge-tools-installer debconf template

Package: depthcharge-tools-installer
Severity: wishlist
Tags: patch l10n

Hello,

You can find enclosed the Spanish translation template to be uploaded with the 
latest package build.

Kindly place this file in debian/po/ as es.po for your next upload.

Cheers,
-- 
Camaleón# Translation of depthcharge-tools-installer debconf templates to Spanish.
# Copyright (C) 2023 Camaleón 
# This file is distributed under the same license as the 
depthcharge-tools-installer package.
# Camaleón , 2023.
#
msgid ""
msgstr ""
"Project-Id-Version: depthcharge-tools-installer\n"
"Report-Msgid-Bugs-To: Debian Install System Team 
\n"
"POT-Creation-Date: 2023-05-11 18:21+\n"
"PO-Revision-Date: 2023-05-13 10:54+0200\n"
"Language-Team: Debian Spanish \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 2.4.2\n"
"Last-Translator: Camaleón \n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
"Language: es\n"

#. Type: note
#. Description
#. Main menu entry.
#. :sl4:
#: ../templates:1001
msgid "Make this ChromeOS board bootable"
msgstr "Hacer arrancable esta placa ChromeOS"

#. Type: note
#. Description
#. Progress bar title.
#. :sl4:
#: ../templates:2001
msgid "Making this ChromeOS board bootable"
msgstr "Haciendo arrancable esta placa ChromeOS"

#. Type: note
#. Description
#. Progress bar step.
#. :sl4:
#: ../templates:3001
msgid "Installing tools to manage ChromeOS boot images"
msgstr ""
"Instalando herramientas para gestionar imágenes de arranque de ChromeOS"

#. Type: note
#. Description
#. Progress bar step.
#. :sl4:
#: ../templates:4001
msgid "Checking ChromeOS kernel partitions"
msgstr "Comprobando particiones del núcleo ChromeOS"

#. Type: note
#. Description
#. Progress bar step.
#. :sl4:
#: ../templates:5001
msgid "Updating initramfs"
msgstr "Actualizando initramfs"

#. Type: note
#. Description
#. Progress bar step.
#. :sl4:
#: ../templates:6001
msgid "Building a boot image"
msgstr "Generando una imagen arrancable"

#. Type: note
#. Description
#. Progress bar step.
#. :sl4:
#: ../templates:7001
msgid "Writing the boot image to disk"
msgstr "Escribiendo la imagen arrancable en el disco"

#. Type: error
#. Description
#. Same as base-installer/kernel/failed-package-install.
#. :sl4:
#: ../templates:8001
msgid "Unable to install ${PACKAGE}"
msgstr "No se puede instalar ${PACKAGE}"

#. Type: error
#. Description
#. Same as base-installer/kernel/failed-package-install.
#. :sl4:
#: ../templates:8001
msgid ""
"An error was returned while trying to install the ${PACKAGE} package onto "
"the target system."
msgstr ""
"Se ha producido un error al intentar instalar el paquete ${PACKAGE} en el "
"sistema de destino."

#. Type: error
#. Description
#. Same as base-installer/kernel/failed-package-install.
#. :sl4:
#. Type: error
#. Description
#. :sl4:
#. Type: error
#. Description
#. :sl4:
#. Type: error
#. Description
#. :sl4:
#: ../templates:8001 ../templates:9001 ../templates:10001 ../templates:11001
msgid "Check /var/log/syslog or see virtual console 4 for the details."
msgstr ""
"Consulte el archivo «/var/log/syslog» o la consola virtual 4 para más "
"detalles."

#. Type: error
#. Description
#. :sl4:
#: ../templates:9001
msgid "No usable ChromeOS kernel partition is found"
msgstr "No se ha encontrado ninguna partición con núcleo ChromeOS usable"

#. Type: error
#. Description
#. :sl4:
#: ../templates:9001
msgid "An error was returned while searching for a ChromeOS kernel partition."
msgstr "Se ha producido un error al buscar una partición con núcleo ChromeOS."

#. Type: error
#. Description
#. :sl4:
#: ../templates:10001
msgid "Cannot build a boot image"
msgstr "No se puede generar una imagen de arranque"

#. Type: error
#. Description
#. :sl4:
#: ../templates:10001
msgid "An error was returned while building a boot image."
msgstr "Se ha producido un error al generar una imagen de arranque."

#. Type: error
#. Description
#. :sl4:
#: ../templates:11001
msgid "Cannot write boot image to disk"
msgstr "No se puede escribir la imagen de arranque en disco"

#. Type: error
#. Description
#. :sl4:
#: ../templates:11001
msgid "An error was returned while writing the boot image to disk."
msgstr ""
"Se ha producido un error al escribir la imagen de arranque en el disco."

#. Type: boolean
#. Description
#. :sl4:
#: ../templates:12001
msgid "Reconfigure initramfs policies?"
msgstr "¿Desea reconfigurar las políticas de initramfs?"

#. Type: boolean
#. Description
#. :sl4:
#: ../templates:12001
msgid ""
"Could not generate a small enough boot image for this board. Usually this "
"can be resolved by including less modules in the initramfs."
msgstr ""
"No se ha podido generar una imagen lo suficientemente pequeña para esta "
"placa. Normalmente esto puede resolverse incluyendo menos módulos en el "
"initramfs."

Bug#1035537: split -n k/N gives incorrect data on blocks after the first

2023-05-20 Thread Salvatore Bonaccorso

Hi,

On Fri, May 19, 2023 at 04:19:20PM -0400, Chris Frey wrote:
> Severity: grave
> 
> Updating severity as suggested on the debian-lts mailing list.

Leaving the severity judgement to Michael. I have as well merged
your bug with the #982300 one.
> 
> Do you think this bug warrants a security-related fix in stable,
> due to the potential for data corruption?

Speaking for stable security: I do no think this warrants a DSA. But a
fix might be scheduled in a point release for bullseye.

Regards,
Salvatore

Bug#1036377: software-properties-common: Feature Request: Add Option to Support Alternate Release/Codename

2023-05-20 Thread Michael D. Adams

Package: software-properties-common
Version: 0.99.27
Severity: wishlist
X-Debbugs-Cc: mdmko...@yahoo.com

Dear Maintainer,

This is a feature request to ask for an option to specify the release/codename
to use when adding a PPA.  Note that this option is likely to be useful for
other types of additions, but I will focus on the PPA case for simplicity.

## Use Case

The use-case to be solved is when a user on for example Ubuntu 23.04 (codename
"lunar") wants to add a PPA using a release/codename other than "lunar".  This
may be required to add PPAs like ppa:aos1/diff-so-fancy or
ppa:appimagelauncher-team/stable that do not yet have a "lunar" release.  (At
the time of this writing the latest releases of these are "jammy" and "kinetic"
respectively.)

However, invoking "apt-add-repository ppa:aos1/diff-so-fancy" always put a
"lunar" line in /etc/apt/sources.list.d/aos1-ubuntu-diff-so-fancy-kinetic.list,
and "apt update" will subsequently fail.

## Requested Feature

My request is that there be added an option similar to --component or --pocket
that allows the user to directly specify the release/codename.  For example,
the user could say "apt-add-repository ppa:aos1/diff-so-fancy --release jammy"
or "apt-add-repository ppa:aos1/diff-so-fancy --codename jammy".  (I am not
sure whether the preferred terminology is "release" or "codename".)

Note that the --pocket option does not solve this problem as that is for
specifying "--pocket updates" to get "lunar-updates".

The --sourceslist option does not fully solve this problem either as it does
not add the key for the PPA to /etc/apt/trusted.gpg.d.

## How to Implement

Note that the code for the base-class of the handlers (in
/usr/lib/python3/dist-packages/softwareproperties/shortcuthandler.py) already
has an argument for specifying the "codename", so I think implementing this
would be as simple as adding a "codename" entry to "shortcut_params" in
/usr/bin/apt-add-repository.


Thank you for your time,
Michael D. Adams


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

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

Versions of packages software-properties-common depends on:
ii  ca-certificates  20211016ubuntu0.22.10.1
ii  gir1.2-glib-2.0  1.74.0-2
ii  gir1.2-packagekitglib-1.01.2.5-2ubuntu2
ii  packagekit   1.2.5-2ubuntu2
ii  python-apt-common2.3.0ubuntu2.1
ii  python3  3.10.6-1
ii  python3-dbus 1.2.18-3build1
ii  python3-gi   3.42.2-2
ii  python3-software-properties  0.99.27

software-properties-common recommends no packages.

software-properties-common suggests no packages.

-- no debconf information

Bug#1036378: gmpc: Remove unneeded libayatana-appindicator


Source: gmpc
Version: 11.8.16-19
Severity: wishlist
Tags: patch
Control: block 967567 by -1

The package builds without the libayatana-appindicator-dev build dependency.
Dropping it would help with the removal of some gtk2 packages because
gmpc is one of the last few libayatana reverse dependencies.diff -Nru gmpc-11.8.16/debian/changelog gmpc-11.8.16/debian/changelog
--- gmpc-11.8.16/debian/changelog   2020-12-26 15:47:48.0 +0100
+++ gmpc-11.8.16/debian/changelog   2023-05-20 10:22:11.0 +0200
@@ -1,3 +1,10 @@
+gmpc (11.8.16-19.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Remove unneeded libayatana-appindicator.
+
+ -- Bastian Germann   Sat, 20 May 2023 10:22:11 +0200
+
 gmpc (11.8.16-19) unstable; urgency=medium
 
   * Set packaging branch to debian/latest
diff -Nru gmpc-11.8.16/debian/control gmpc-11.8.16/debian/control
--- gmpc-11.8.16/debian/control 2020-12-26 15:47:48.0 +0100
+++ gmpc-11.8.16/debian/control 2023-05-20 10:22:07.0 +0200
@@ -8,7 +8,6 @@
 Build-Depends: debhelper-compat (= 12),
gob2,
intltool,
-   libayatana-appindicator-dev,
libglib2.0-dev,
libgtk2.0-dev,
libmpd-dev,

Bug#1036379: parcellite: Remove unneeded libayatana-appindicator


Source: parcellite
Version: 1.2.1-4
Severity: wishlist
Control: block 967567 by -1

The package builds without the libayatana-appindicator-dev build dependency.
Dropping it would help with the removal of some gtk2 packages because
parcellite is one of the last few libayatana reverse dependencies.

Bug#1036380: unblock: texlive-bin/2022.20220321.62855-5.1

2023-05-20 Thread Salvatore Bonaccorso

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: texlive-...@packages.debian.org, Hilmar Preusse , 
car...@debian.org
Control: affects -1 + src:texlive-bin

Dear release team,

CC'ing Hilmar. I did contact Hilmar as well before releasing the NMU
(not strictly following the NMU guidelines, to get the fix into
bookworm, after the DSA release for bullseye-security). 

[ Reason ]
The upload fixes an issue discovered by Max Chernoff which may result
in arbitrary shell command execution in LuaTeX. This is DSA 5406-1:
https://lists.debian.org/debian-security-announce/2023/msg00097.html

[ Impact ]
As the fix landed in bullseye-security it would be good to have the
fix as well straight into first release of bookworm.

[ Tests ]
Done manual tests with the proof of concent for the CVE-2023-32700
issue both for luatex as as well lualatex.

[ Risks ]
We pick the upstream provided changes. Drawback for these kind of
updates to texlive-bin for the LuaTeX base was that the
lualatex-core.c needs to be patched as well for the updated bytecode.

[ 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 testing

[ Other info ]
None specific. Hilmar might override the -5.1 upload with -6
containing the same changes to have proper sync between packaging repo
import of the changes and archive. But other than that it would be
great to get the fix into bookworm. Hilmar mentioned another bugfix
possibly to be asked for bookworm, but I would suggest to discuss this
either here as followup or with a separate unblock request, Hilmar
does that work for you?

unblock texlive-bin/2022.20220321.62855-5.1

Regards,
Salvatore
diff -Nru texlive-bin-2022.20220321.62855/debian/changelog 
texlive-bin-2022.20220321.62855/debian/changelog
--- texlive-bin-2022.20220321.62855/debian/changelog2022-12-11 
09:33:59.0 +0100
+++ texlive-bin-2022.20220321.62855/debian/changelog2023-05-18 
23:15:13.0 +0200
@@ -1,3 +1,10 @@
+texlive-bin (2022.20220321.62855-5.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Fix improperly secured shell-escape in LuaTeX (CVE-2023-32700)
+
+ -- Salvatore Bonaccorso   Thu, 18 May 2023 23:15:13 +0200
+
 texlive-bin (2022.20220321.62855-5) unstable; urgency=medium
 
   [ Hilmar Preusse ]
diff -Nru texlive-bin-2022.20220321.62855/debian/patches/CVE-2023-32700.patch 
texlive-bin-2022.20220321.62855/debian/patches/CVE-2023-32700.patch
--- texlive-bin-2022.20220321.62855/debian/patches/CVE-2023-32700.patch 
1970-01-01 01:00:00.0 +0100
+++ texlive-bin-2022.20220321.62855/debian/patches/CVE-2023-32700.patch 
2023-05-18 23:15:13.0 +0200
@@ -0,0 +1,1316 @@
+Description: Fix improperly secured shell-escape in LuaTeX
+Origin: upstream, https://tug.org/~mseven/luatex.html
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2023-32700
+Forwarded: no
+Last-Update: 2023-05-18
+
+--- a/texk/web2c/luatexdir/lua/loslibext.c
 b/texk/web2c/luatexdir/lua/loslibext.c
+@@ -1047,6 +1047,111 @@ static int os_execute(lua_State * L)
+ }
+ 
+ 
++/*
++** ==
++** l_kpse_popen spawns a new process connected to the current
++** one through the file streams with some checks by kpse.
++** Almost verbatim from Lua liolib.c .
++** ===
++*/
++#if !defined(l_kpse_popen)   /* { */
++
++#if defined(LUA_USE_POSIX)  /* { */
++
++#define l_kpse_popen(L,c,m)  (fflush(NULL), popen(c,m))
++#define l_kpse_pclose(L,file)(pclose(file))
++
++#elif defined(LUA_USE_WINDOWS)  /* }{ */
++
++#define l_kpse_popen(L,c,m)  (_popen(c,m))
++#define l_kpse_pclose(L,file)(_pclose(file))
++
++#else   /* }{ */
++
++/* ISO C definitions */
++#define l_kpse_popen(L,c,m)  \
++  ((void)((void)c, m), \
++  luaL_error(L, "'popen' not supported"), \
++  (FILE*)0)
++#define l_kpse_pclose(L,file)((void)L, (void)file, -1)
++
++#endif  /* } */
++
++#endif  /* } */
++typedef luaL_Stream LStream;
++#define tolstream(L)((LStream *)luaL_checkudata(L, 1, LUA_FILEHANDLE))
++static LStream *newprefile (lua_State *L) {
++  LStream *p = (LStream *)lua_newuserdata(L, sizeof(LStream));
++  p->closef = NULL;  /* mark file handle as 'closed' */
++  luaL_setmetatable(L, LUA_FILEHANDLE);
++  return p;
++}
++static int io_kpse_pclose (lua_State *L) {
++  LStream *p = tolstream(L);
++  return luaL_execresult(L, l_kpse_pclose(L, p->f));
++}
++static int io_kpse_check_permissions(lua_State *L) {
++const char *filename = luaL_checkstring(L, 1);
++if (filename == NULL) {
++lua_pushboolean(L,0);
++lua_pushliteral(L,"no command name given");
++} else if (shellenabledp <= 0) {
++lua_pus

Bug#1035436: rkdeveloptool: diff for NMU version 1.32+git20210408.46bb4c0-2.1

Control: tags 1035436 + patch
Control: tags 1035436 + pending

Dear maintainer,

I've prepared an NMU for rkdeveloptool (versioned as
1.32+git20210408.46bb4c0-2.1) and uploaded it to DELAYED/1. Please feel
free to tell me if I should delay it longer.

kind regards

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'
diff -Nru rkdeveloptool-1.32+git20210408.46bb4c0/debian/changelog rkdeveloptool-1.32+git20210408.46bb4c0/debian/changelog
--- rkdeveloptool-1.32+git20210408.46bb4c0/debian/changelog	2022-10-31 13:04:40.0 +0100
+++ rkdeveloptool-1.32+git20210408.46bb4c0/debian/changelog	2023-05-20 11:03:08.0 +0200
@@ -1,3 +1,10 @@
+rkdeveloptool (1.32+git20210408.46bb4c0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add missing depends on adduser. Closes: #1035436
+
+ -- Andreas Metzler   Sat, 20 May 2023 11:03:08 +0200
+
 rkdeveloptool (1.32+git20210408.46bb4c0-2) unstable; urgency=medium
 
   [ Debian Janitor ]
diff -Nru rkdeveloptool-1.32+git20210408.46bb4c0/debian/control rkdeveloptool-1.32+git20210408.46bb4c0/debian/control
--- rkdeveloptool-1.32+git20210408.46bb4c0/debian/control	2022-10-31 13:03:52.0 +0100
+++ rkdeveloptool-1.32+git20210408.46bb4c0/debian/control	2023-05-20 11:03:01.0 +0200
@@ -14,7 +14,8 @@
 
 Package: rkdeveloptool
 Architecture: any
-Depends: ${shlibs:Depends},
+Depends: adduser,
+ ${shlibs:Depends},
  ${misc:Depends},
 Description: tools for working with Rockchip processors
  This package provides tools to communicate with various Rockchip processors


signature.asc
Description: PGP signature

Bug#1036381: gnubg: Remove libcanberra (sound support)


Source: gnubg
Version: 1.07.001-1
Severity: wishlist
Control: block 967569 by -1

The package builds without the libcanberra-gtk-dev build dependency.
Dropping it would help with the removal of libcanberra's gtk2 flavor because
gnubg is its last reverse dependency.

This will remove sound in the game but I do not think that this is important to 
play it.

Bug#1036293: [Pkg-pascal-devel] Bug#1036293: lazarus: LHelp needs CHM files to display online help

2023-05-20 Thread Abou Al Montacir

Control: -1 important

On Thu, 2023-05-18 at 22:41 +0100, Peter B wrote:
> Regarding the html help, looks to me that lazarus is looking in
> /usr/share/doc/lazarus/2.2.0/index.html
> a 2.2.0 folder, but the index is now in 2.2.6
This is an issue during the upgrade. You did configure your Lazarus help when
you were installing 2.2.0, then upon upgrade (the dialog message that appears)
this remained as is. You need just to go to Tools/Options.../Help/Help
Options and then check all entries replacing 2.2.0 by 2.2.6.

One normally should be able to use $(LazVer), but unfortunately this one has the
Debian full version (2.2.6+dfsg2-1) which is improper for that use.

On the other hand, the system wide configuration file seems OK for HTML help,
but the help files seems to be installed on the wrong location. This is probably
what forced people like you to change the path. However as no one complained, we
missed it.

This looks for me important rather than normal severity.
I'll try to fix this and issue and unblock request.

BTW: With correct path HTML help works well. I don't know if we need to fix CHM
help as FPC doc is already using the HTML format.
-- 
Cheers,
Abou Al Montacir

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

Bug#1036382: dillo: doesn't recognize XHTML 1.1 as HTML

Package: dillo
Version: 3.0.5-7
Severity: grave

When I open an XHTML 1.1 file dillo doesn't recognize it as HTML,
displaying it as plain text, despite the file being correct XHTML. It
happens with any extension, including .html and .xhtml.

Considering XHTML 1.1 is valid HTML 4, which dillo supports, and XHTML
is nowadays and shall be widely supported, this makes the package
mostly unusable.

Best regards,
José Luis

Bug#1036383: unblock: webdis/0.1.9+dfsg-1.1

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: web...@packages.debian.org, and...@senkovych.com
Control: affects -1 + src:webdis

Please unblock package webdis

[ Reason ]

In the context of #1035654, five source packages (including this one)
still fail to purge remove without adduser installed.

[ Impact ]

We want to avoid the situation where a user removes the package, then
upgrades to apt that doesn't depend on adduser, then removes adduser and
then attempts to purge this package.

[ Tests ]

See the script I posted in #1035654.

[ Risks ]

Low risk due to trivial change (see end of this mail) and because of low popcon
number (5 votes).

[ 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 testing

unblock webdis/0.1.9+dfsg-1.1

diff -Nru webdis-0.1.9+dfsg/debian/changelog webdis-0.1.9+dfsg/debian/changelog
--- webdis-0.1.9+dfsg/debian/changelog  2020-04-23 01:04:04.0 +0200
+++ webdis-0.1.9+dfsg/debian/changelog  2023-05-18 00:10:16.0 +0200
@@ -1,3 +1,10 @@
+webdis (0.1.9+dfsg-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * ignore deluser not being available in postrm purge (closes: #1035435)
+
+ -- Johannes Schauer Marin Rodrigues   Thu, 18 May 2023 
00:10:16 +0200
+
 webdis (0.1.9+dfsg-1) unstable; urgency=medium
 
   * d/copyright: acknowledge upstream files relocation
diff -Nru webdis-0.1.9+dfsg/debian/webdis.postrm 
webdis-0.1.9+dfsg/debian/webdis.postrm
--- webdis-0.1.9+dfsg/debian/webdis.postrm  2018-08-25 09:53:40.0 
+0200
+++ webdis-0.1.9+dfsg/debian/webdis.postrm  2023-05-17 23:56:44.0 
+0200
@@ -15,7 +15,7 @@
 fi
 rm -rf $WEBDIS_LOG
 
-deluser --system webdis
+deluser --system webdis || true
 ;;
 
 *)

Bug#967367: ganv: depends on deprecated GTK 2


ganv has no reverse dependencies anymore, so I would like to suggest its 
removal.

Bug#1036384: dillo: Open file dialog pops up in /tmp

Package: dillo
Version: 3.0.5-7
Severity: important

When I pop up the Open file dialog it always opens in /tmp, forcing you
to change to home, which is where it should open. The only exception is
when you have already opened a file and are still displaying it, then it
rightly opens in the same dir, but if you go back to another page and
return it forgets.

Besides, if I click on FLTK's shortcut for /, right up the Filename
text entry, it only displays kernel fs dirs: sys, proc, dev, run, and
subdirs of these.

The whole issue is a very serious usability issue.

Bug#956787: gtk-sharp-beans: Should this package be removed?


I would like to strongly support removing this package.
@Maintainer: Would you please say a word about it?

Bug#965794: python-ooolib: diff for NMU version 0.0.22-5.1

Control: tags -1 patch  pending

Dear maintainer,

I've prepared an NMU for python-ooolib (versioned as 0.0.22-5.1) and
uploaded it to DELAYED/1. Please feel free to tell me if I
should delay it longer.

Kind regards
Andreas
diff -u python-ooolib-0.0.22/debian/changelog python-ooolib-0.0.22/debian/changelog
--- python-ooolib-0.0.22/debian/changelog
+++ python-ooolib-0.0.22/debian/changelog
@@ -1,3 +1,12 @@
+python-ooolib (0.0.22-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use dh v11 compat level. Closes: #965794
+  * Add missing build-indep and build-arch targets.
+Closes: #998940
+
+ -- Andreas Metzler   Sat, 20 May 2023 11:31:16 +0200
+
 python-ooolib (0.0.22-5) unstable; urgency=medium
 
   * remove obsolete debian/pycompat and Python-Provides:
reverted:
--- python-ooolib-0.0.22/debian/compat
+++ python-ooolib-0.0.22.orig/debian/compat
@@ -1 +0,0 @@
-5
diff -u python-ooolib-0.0.22/debian/control python-ooolib-0.0.22/debian/control
--- python-ooolib-0.0.22/debian/control
+++ python-ooolib-0.0.22/debian/control
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Debian LibreOffice Team 
 Uploaders: Rene Engelhard , Chris Halls 
-Build-Depends: debhelper (>= 5), python3-all, python3, dh-python
+Build-Depends: debhelper-compat (= 11), python3-all, python3, dh-python
 Standards-Version: 3.7.2
 
 Package: python3-ooolib
diff -u python-ooolib-0.0.22/debian/rules python-ooolib-0.0.22/debian/rules
--- python-ooolib-0.0.22/debian/rules
+++ python-ooolib-0.0.22/debian/rules
@@ -17,6 +17,10 @@
 
 build: build-stamp
 
+build-indep: build-stamp
+
+build-arch: build-stamp
+
 build-stamp: configure-stamp 
 	dh_testdir
 	touch $@


signature.asc
Description: PGP signature

Bug#1032771: libzim7: Package name is wrong, should be 'libzim'

2023-05-20 Thread Kunal Mehta


tags 1032771 - wontfix
thanks

Hi,

On 3/22/23 11:41, Bastian Germann wrote:

Control: tags -1 wontfix

On Fri, 17 Mar 2023 20:12:26 -0400 James Valleroy 
 wrote:
Note that this request is about changing the source package name, from 
"zimlib" to "libzim". The bug was accidentally filed on the binary 
package instead of the source package.


There is no good reason to rename the source package.


I would like to do this for the trixie cycle, mostly to be in sync with 
upstream.


-- Kunal

Bug#1036385: python-aioredlock: FTBFS due to missing build dependency python3-setuptools

2023-05-20 Thread Hans Joachim Desserud


Source: python-aioredlock
Version: 0.7.3-1
Severity: serious
Justification: FTBFS
Tags: ftbfs sid

Dear Maintainer,

python-aioredlock currently fails to build with the following error 
message:

dh clean --buildsystem=pybuild
   dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:240: python3.11 setup.py clean
Traceback (most recent call last):
  File "/build/python-aioredlock-0.7.3/setup.py", line 4, in 
from setuptools import find_packages, setup
ModuleNotFoundError: No module named 'setuptools'
E: pybuild pybuild:388: clean: plugin distutils failed with: exit 
code=1: python3.11 setup.py clean
dh_auto_clean: error: pybuild --clean -i python{version} -p 3.11 
returned exit code 13

make: *** [debian/rules:4: clean] Error 25
dpkg-buildpackage: error: debian/rules clean subprocess returned exit 
status 2



After adding python3-setuptools to build dependencies the package builds 
successfully without any other issues


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

Kernel: Linux 6.1.0-9-amd64 (SMP w/3 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


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

Bug#35970: gnumach hangs because of Linux 2.0.36 adaptec drivers

2023-05-20 Thread Santiago Vila


El 20/5/23 a las 9:29, Petter Reinholdtsen escribió:

[Guillem Jover 2005]

Can you reproduce #35970 with the latest gnumach packages?


[Santiago Vila 2005]


I don't know, and it is going to be quite difficult for me to check, because
the computer is currently running woody as a server for a lot of people...


Is there any use keeping this issue open?


Not really.


I suspect the hardware in
question has long since been retired and no-one is using the
Adaptec driver any more.


The hardware was retired a long time ago indeed. When I reported this,
the computer was my personal computer at work. In 2005 it was working
as a printer server in my Department, and that's why it was not
possible for me to test.

Now I don't even work there.


The upstream bug is also flagged with 'need more info', and if no-one
can provide the info, it seem useless to keep the issue open.


I agree, so I'm closing this myself.

Thanks.

Bug#1036386: tools-deps-clojure: FTBFS without network access

2023-05-20 Thread Hans Joachim Desserud


Source: tools-deps-clojure
Version: 0.16.1264-2
Severity: serious
Justification: FTBFS
Tags: sid ftbfs

Dear Maintainer,

tools-deps-clojure currently fails to build on Sid. It looks like the 
tests attempt to clone the upstream repository and then it fails:

Testing clojure.tools.deps.extensions.test-git
Cloning: https://github.com/clojure/tools.deps.git

FAIL in (canonicalize-errors) (test_git.clj:72)
expected: (thrown-with-msg? ExceptionInfo #"Library 
io.github.clojure/tools.deps has coord with missing sha" 
(ext/canonicalize (quote io.github.clojure/tools.deps) #:git{:tag 
"tools.deps.alpha-0.5.317"} {}))

  actual: #error {
 :cause "Unable to clone 
/build/tools-deps-clojure-0.16.1264/.gitlibs/_repos/https/github.com/clojure/tools.deps\nfatal: 
unable to access 'https://github.com/clojure/tools.deps.git/': Could not 
resolve host: github.com\n"
 :data {:args ("git" "clone" "--quiet" "--mirror" 
"https://github.com/clojure/tools.deps.git"; 
"/build/tools-deps-clojure-0.16.1264/.gitlibs/_repos/https/github.com/clojure/tools.deps"), 
:exit 128, :out "", :err "fatal: unable to access 
'https://github.com/clojure/tools.deps.git/': Could not resolve host: 
github.com\n"}

 :via
 [{:type clojure.lang.ExceptionInfo
   :message "Unable to clone 
/build/tools-deps-clojure-0.16.1264/.gitlibs/_repos/https/github.com/clojure/tools.deps\nfatal: 
unable to access 'https://github.com/clojure/tools.deps.git/': Could not 
resolve host: github.com\n"
   :data {:args ("git" "clone" "--quiet" "--mirror" 
"https://github.com/clojure/tools.deps.git"; 
"/build/tools-deps-clojure-0.16.1264/.gitlibs/_repos/https/github.com/clojure/tools.deps"), 
:exit 128, :out "", :err "fatal: unable to access 
'https://github.com/clojure/tools.deps.git/': Could not resolve host: 
github.com\n"}
   :at [clojure.tools.gitlibs.impl$git_clone_bare invokeStatic 
"impl.clj" 103]}]

 :trace



I saw this when building locally on Sid, 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/tools-deps-clojure.html 
also has additional information.



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

Kernel: Linux 6.1.0-9-amd64 (SMP w/3 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

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

Bug#1035436: rkdeveloptool: diff for NMU version 1.32+git20210408.46bb4c0-2.1

2023-05-20 Thread Christopher Obbard

Hi,

On Sat, 2023-05-20 at 11:07 +0200, Andreas Metzler wrote:
> Control: tags 1035436 + patch
> Control: tags 1035436 + pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for rkdeveloptool (versioned as
> 1.32+git20210408.46bb4c0-2.1) and uploaded it to DELAYED/1. Please feel
> free to tell me if I should delay it longer.

Thank you for your contribution, but it seems like there is some parallel work 
(this morning in fact).

I am currently in the process of uploading and the fixes for this package. Is 
it possible to skip this delayed version in favour of the version I am about to 
upload ?

> 
> kind regards
> 
> Andreas

Bug#1036387: RM: hyena -- RoQA; low popcon; gtk2 dependency


Source: hyena

Please consider filing a removal bug (reassign this one to ftp.debian.org) for 
hyena.
It has no reverse dependencies and depends on gtk2, which should be removed 
some day.

Bug#1036388: sylpheed: account unadvertingly and unwantingly changed when email is received

Package: sylpheed
Version: 3.7.0-8
Severity: grave

If a new mail arrives to an account other than the current one it is
changed without permission nor warning to the one receiving the email,
which means all activity from then on is done unadvertingly on the
switched-to account.

Considering the consequences of sending email from an account different
from the one intended, like sending from a private one to a public
forum (like a mailing list available on the web, or the DBTS), or using
an account that is not permitted for what was unwantedly done, this
makes the package mostly unusable since the consequences of can't be
usually undone and can be very grave, which renders the program
unusable for any serious user.

Bug#1036389: sylpheed: new mail notification not working

Package: sylpheed
Version: 3.7.0-8
Severity: important

The new mail notification feature doesn't work for me at all. I have
set it to display a window for 10 seconds on new mail received and the
window does not pop up at all.

Bug#956788: RM: hocr -- RoQA; low popcon; gtk2 dependency


Control: retitle -1 RM: hocr -- RoQA; low popcon; gtk2 dependency

I do not think that upstream has answered the request.
If nobody object I am going to reassign this bug to ftp.debian.org after the 
bookworm release.

Bug#1036390: sylpheed: search bar has no close button

Package: sylpheed
Version: 3.7.0-8
Severity: important

Sylpheed's fast search bar has no close button, making it inconvenient
to close it, since the only way is through the View -> Show and hide
submenu, especially considering it is not meant to be open all the
time and consumes screen space.

Bug#1036391: sylpheed: Toggling edit search bar doesn't hide it

Package: sylpheed
Version: 3.7.0-8
Severity: important

"Edit -> Fast search" and "Ctrl + Shift + S" don't toggle the search
bar off when it is already displayed.

This, together with #1036390, is a major usability issue, since it is
inconvenient to turn it off and the feature can be needed very often.

Bug#965794: python-ooolib: diff for NMU version 0.0.22-5.1

2023-05-20 Thread Rene Engelhard


Hi,

Am 20.05.23 um 11:38 schrieb Andreas Metzler:

I've prepared an NMU for python-ooolib (versioned as 0.0.22-5.1) and
uploaded it to DELAYED/1. Please feel free to tell me if I
should delay it longer.


How is it unclear that noone seriously cares about this package?

Old upstream version, popcon 4, ignored by the maintainer. The fix is 
clear, I just want to get it AUTORMed. How difficult is it to understand 
that?



As I already said to Adrian when he last tagged the bug: stop resetting 
the autorm counter.


(which you did now again, sigh.)

 Besides that: it would miss the hard freeze anyway with medium urgency 
so it's a total waste of time.



Regards,


Rene

Bug#1036354: unblock: iptables-persistent/1.0.20

2023-05-20 Thread Luca Boccassi

On Fri, 19 May 2023, 15:39 gustavo panizzo,  wrote:

> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> X-Debbugs-Cc: bl...@debian.org
>
> Please unblock package iptables-persistent
>
> (Please provide enough (but not too much) information to help
> the release team to judge the request efficiently. E.g. by
> filling in the sections below.)
>
> [ Reason ]
> The package is using alternatives to manage (systemd) aliases,
> this is not recommended by the systemd maintainers.
>
> See bug report #1036147
>
>
> I've added alternatives to this package back in 2019 to solve #926927
> as a point of coordination with other firewall managers in Debian
> (see https://lists.debian.org/debian-firewall/2019/08/msg0.html) but
> the initiative never took off
>
>
> [ Impact ]
> This is (was) the only package in Debian which uses alternatives to
> manage aliases, which makes it different from what admins expect
>
> [ Tests ]
> This version of the package is clean in lintian and piuparts,
> I've upgraded my systems and found no problems
>
>
> [ Risks ]
> I see no risks, if an admin locally have changed the override files,
> we'll keep them as dpkg-bak
>
>
> [ 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 testing
>
>
> unblock iptables-persistent/1.0.20
>

Thanks for taking care of this - I just checked and cannot see the upload
to unstable though?

Kind regards,
Luca Boccassi

>

Bug#1036392: sylpheed: check new mail features should be an account preference, not a general

Package: sylpheed
Version: 3.7.0-8
Severity: normal

"Check new mail every X minutes" and "Check new mail on start" are
preferences that make sense and may be necessary to be account options,
not just common to all accounts, as it currently stands.

Bug#1036354: unblock: iptables-persistent/1.0.20

2023-05-20 Thread gustavo panizzo

Hi

On May 20, 2023 10:20:50 AM UTC, Luca Boccassi  wrote:
>On Fri, 19 May 2023, 15:39 gustavo panizzo,  wrote:
>
>> Package: release.debian.org
>> Severity: normal
>> User: release.debian@packages.debian.org
>> Usertags: unblock
>> X-Debbugs-Cc: bl...@debian.org
>>
>> Please unblock package iptables-persistent
>>
>> (Please provide enough (but not too much) information to help
>> the release team to judge the request efficiently. E.g. by
>> filling in the sections below.)
>>
>> [ Reason ]
>> The package is using alternatives to manage (systemd) aliases,
>> this is not recommended by the systemd maintainers.
>>
>> See bug report #1036147
>>
>>
>> I've added alternatives to this package back in 2019 to solve #926927
>> as a point of coordination with other firewall managers in Debian
>> (see https://lists.debian.org/debian-firewall/2019/08/msg0.html) but
>> the initiative never took off
>>
>>
>> [ Impact ]
>> This is (was) the only package in Debian which uses alternatives to
>> manage aliases, which makes it different from what admins expect
>>
>> [ Tests ]
>> This version of the package is clean in lintian and piuparts,
>> I've upgraded my systems and found no problems
>>
>>
>> [ Risks ]
>> I see no risks, if an admin locally have changed the override files,
>> we'll keep them as dpkg-bak
>>
>>
>> [ 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 testing
>>
>>
>> unblock iptables-persistent/1.0.20
>>
>
>Thanks for taking care of this - I just checked and cannot see the upload
>to unstable though?

I'd prefer to wait for an ack from the release team

>
>Kind regards,
>Luca Boccassi
>
>>

Bug#1036388: sylpheed: account unadvertingly and unwantingly changed when email is received

Hi again,

I have observed this happens with new coming from any account,
including the current one. So if I have an email account that is
private@gmail and I get new mail on my current one, it also switches
unwantingly and unadvertedly to private@gmail.

The problem is really serious and obnoxious.

Bug#1036393: RFP: gtksheet -- GTK+3 GtkSheet widget


Package: wnpp
Severity: wishlist

* Package name: gtksheet
  Upstream Contact: https://github.com/fpaquet/gtksheet/issues
* URL : http://fpaquet.github.io/gtksheet/
* License : GPL-2
  Programming Lang: C
  Description : GTK+3 GtkSheet widget

The gtksheet library is a fork of the GtkSheet widget included in the GTK+extra 
library.
It includes the GtkSheet widget for displaying a spreadsheet-like matrix.
The included GtkDataEntry widget supports formatted number display.

Bug#1016823: Thunar: add Lens Model to Image tab [patch attached]

> Control: forwarded -1 https://gitlab.xfce.org/xfce/thunar/-/issues/829
> Control: tags -1 upstream
>
> It looks like you already created an issue upstream. You can ask for
> fork and MR permissions by contacting the mailing list. See the
> instructions here:
> https://docs.xfce.org/contribute/dev/git/start#gitlab_forks_and_merge_requests

Thanks for the pointer, but the problem is I couldn't send the patch to
the person who assisted me because the sender he used accepted no
messages.

Did you forward the patch, or made it explicity at least that a patch
was available? The person who attended me was Alexander Schwinn.

Thanks a lot in advance.

Bug#1036354: unblock: iptables-persistent/1.0.20

2023-05-20 Thread Luca Boccassi

On Sat, 20 May 2023 at 11:29, gustavo panizzo  wrote:
>
> Hi
>
> On May 20, 2023 10:20:50 AM UTC, Luca Boccassi  wrote:
> >On Fri, 19 May 2023, 15:39 gustavo panizzo,  wrote:
> >
> >> Package: release.debian.org
> >> Severity: normal
> >> User: release.debian@packages.debian.org
> >> Usertags: unblock
> >> X-Debbugs-Cc: bl...@debian.org
> >>
> >> Please unblock package iptables-persistent
> >>
> >> (Please provide enough (but not too much) information to help
> >> the release team to judge the request efficiently. E.g. by
> >> filling in the sections below.)
> >>
> >> [ Reason ]
> >> The package is using alternatives to manage (systemd) aliases,
> >> this is not recommended by the systemd maintainers.
> >>
> >> See bug report #1036147
> >>
> >>
> >> I've added alternatives to this package back in 2019 to solve #926927
> >> as a point of coordination with other firewall managers in Debian
> >> (see https://lists.debian.org/debian-firewall/2019/08/msg0.html) but
> >> the initiative never took off
> >>
> >>
> >> [ Impact ]
> >> This is (was) the only package in Debian which uses alternatives to
> >> manage aliases, which makes it different from what admins expect
> >>
> >> [ Tests ]
> >> This version of the package is clean in lintian and piuparts,
> >> I've upgraded my systems and found no problems
> >>
> >>
> >> [ Risks ]
> >> I see no risks, if an admin locally have changed the override files,
> >> we'll keep them as dpkg-bak
> >>
> >>
> >> [ 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 testing
> >>
> >>
> >> unblock iptables-persistent/1.0.20
> >>
> >
> >Thanks for taking care of this - I just checked and cannot see the upload
> >to unstable though?
>
> I'd prefer to wait for an ack from the release team

Ok, in that case I think it should be explicitly mentioned that this
is a 'preapproval' request.

Kind regards,
Luca Boccassi

Bug#967565: lepton-eda: depends on deprecated GTK 2


lepton-eda has gtk3 support. With the lepton-attrib configuration active, 
gtksheet would have to be packaged (#1036393).
Or it could be moved to gtk3 without attrib.

Bug#1035802: RM: repsnapper -- RoQA; gtkglextmm dependency


Am 11.05.23 um 08:10 schrieb PaulLiu:

Why should this package be removed? Any replacement for using GL with GTK by a 
C++ wrapper or C++-style?


The same reason as your #967724: GTK 2 should be removed in the long run.
You have to start somewhere and leaf packages of language bindings for gtk2 are 
a good place to start.
I do not know of a replacement.

Bug#1036394: unblock: desktop-autoloader/0.0.4-2

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: desktop-autoloa...@packages.debian.org, sunwea...@debian.org
Control: affects -1 + src:desktop-autoloader

Please unblock package desktop-autoloader

[ Reason ]

In the context of #1035654, five source packages (including this one)
still fail to purge remove without adduser installed.

[ Impact ]

We want to avoid the situation where a user removes the package, then
upgrades to apt that doesn't depend on adduser, then removes adduser and
then attempts to purge this package.

[ Tests ]

See the script I posted in #1035654.

[ Risks ]

Low risk due to trivial change (see end of this mail) and because of low
popcon number (2 votes).

[ 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 testing

unblock desktop-autoloader/0.0.4-2

diff -Nru desktop-autoloader-0.0.4/debian/changelog 
desktop-autoloader-0.0.4/debian/changelog
--- desktop-autoloader-0.0.4/debian/changelog   2018-05-16 13:31:31.0 
+0200
+++ desktop-autoloader-0.0.4/debian/changelog   2023-05-16 22:37:00.0 
+0200
@@ -1,3 +1,10 @@
+desktop-autoloader (0.0.4-2) unstable; urgency=medium
+
+  * debian/desktop-autoloader.postrm:
++ Ignore failures during execution of deluser/delgroup: (Closes: #1035291).
+
+ -- Mike Gabriel   Tue, 16 May 2023 22:37:00 +0200
+
 desktop-autoloader (0.0.4-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru desktop-autoloader-0.0.4/debian/desktop-autoloader.postrm 
desktop-autoloader-0.0.4/debian/desktop-autoloader.postrm
--- desktop-autoloader-0.0.4/debian/desktop-autoloader.postrm   2018-04-03 
20:40:40.0 +0200
+++ desktop-autoloader-0.0.4/debian/desktop-autoloader.postrm   2023-05-16 
22:35:46.0 +0200
@@ -22,8 +22,8 @@
rm -Rf ~desktop-autoloader
fi
 
-   getent passwd desktop-autoloader >/dev/null && deluser 
desktop-autoloader
-   getent group desktop-autoloader >/dev/null && delgroup 
desktop-autoloader
+   getent passwd desktop-autoloader >/dev/null && deluser 
desktop-autoloader || true
+   getent group desktop-autoloader >/dev/null && delgroup 
desktop-autoloader || true
 
# there might be extra .desktop symlinks in 
/etc/desktop-autoloader/autostart,
# wiping them all...

Bug#1036395: RM: python-ooolib/0.0.22-5

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm
X-Debbugs-Cc: python-ooo...@packages.debian.org, ametz...@bebt.de
Control: affects -1 + src:python-ooolib

Please remove the package from testing, the maintainer was (silently)
waiting for it to autormed.
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965794#38

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'


signature.asc
Description: PGP signature

Bug#965794: python-ooolib: diff for NMU version 0.0.22-5.1

Control tags -1 - patch - pending

On 2023-05-20 Rene Engelhard  wrote:
> Hi,

> Am 20.05.23 um 11:38 schrieb Andreas Metzler:
> > I've prepared an NMU for python-ooolib (versioned as 0.0.22-5.1) and
> > uploaded it to DELAYED/1. Please feel free to tell me if I
> > should delay it longer.

> How is it unclear that noone seriously cares about this package?

> Old upstream version, popcon 4, ignored by the maintainer. The fix is clear,
> I just want to get it AUTORMed. How difficult is it to understand that?

How hard is it to communicate? Why didn't you simply write to the
bugreport that you wanted the pkg to be autormed instead of letting
me waste my time?

I have removed the upload.

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'


signature.asc
Description: PGP signature

Bug#63995: bugs.debian.org reveals e-mail addresses to spammers

severity 63995 grave
thanks

A solution is available and it's trivial. Just conceal the addresses
from the public web interface and mailing list archives, requiring
authentication to access the full report. This is
what's done in Ubuntu, Red Hat, XFCE, and about just any sensible
project I know of.

And requiring another account or manually reporting each spam is not
a solution. Firstly, another account is unnecessary and
cumbersome, and secondly, reporting spam is not always possible nor
effective to a regular user, and in some cases this "solution" takes
just too much time and effort to be feasible. It's just common sense
that you don't reveal email addresses publicly nor to spammers.

This makes the BTS unusable to anyone who doesn't set up and use an
email account separately and purposefully for that, and which handles
spam effectively. Additionally, this goes against point 4. of the
Debian Social Contract. Raising severity to grave accordingly.

Bug#1035436: rkdeveloptool: diff for NMU version 1.32+git20210408.46bb4c0-2.1

On 2023-05-20 Christopher Obbard  wrote:
[...] 
> > I've prepared an NMU for rkdeveloptool (versioned as
> > 1.32+git20210408.46bb4c0-2.1) and uploaded it to DELAYED/1.
[...]
> Thank you for your contribution, but it seems like there is some
> parallel work (this morning in fact).

> I am currently in the process of uploading and the fixes for this
> package. Is it possible to skip this delayed version in favour of the
> version I am about to upload ?

Hello Christopher,

if you upload before the NMU is accepted the NMU will simply be
rejected because there is already a higher numbered version of the
package in the archive. I can also simply cancel the NMU or bump the
delay if you want me to. - Just tell me what your preference is.

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'

signature.asc
Description: PGP signature

Bug#973822: ITP: dosbox-staging -- DOSBox Staging is a full x86 CPU emulator (independent of host architecture), capable of running DOS programs that require real or protected mode.

2023-05-20 Thread ntf1

On Thu, 05 Nov 2020 21:52:10 + Ben Hutchings <  b...@decadent.org.uk 
> wrote:  > DOSBox seems to be under active development even though it 
hasn't had a  > release for a while.  So this is an independent fork, 
not a successor  > to a dead project.  (If DOSBox had become dead upstream, 
I would have  > recommended rebasing the existing dosbox source package on 
DOSBox  > Staging instead.)   The last commit to the DOSBox SVN repository ( 
sourceforge.net https://sourceforge.net/p/dosbox/code-0/HEAD/ ) is dated March 
10th, 2023, previous one is July 14th, 2022. Looking at their bug tracker - 
since about mid January 2020 no bug reported was closed, hardly any of them got 
any response from the DOSBox team. The latest news on their web page ( 
www.dosbox.com https://www.dosbox.com/ ) is dated January 27th 2021. The 
previous one (June 26th, 2019) states:   > Ideally, 0.75 should have been 
released by now, but some bugs took a lot longer than expected.   This was 4 
years ago, release did not happen to this day. DOSBox was the best thing that 
happened to DOS retro-gamers, it severed us well for two decades, but it is now 
a 0xDEAD 0xBEEF.  -   DOSBox Staging and DOSBox-X are two really actively 
developed forks/successors - Staging progresses more carefully, has less 
features, but in my experience is more stable; X is harder to configure 
properly, and more like yolo-developed (but still fun to use by power users!).

Bug#1036396: unblock: x2gothinclient/1.5.0.1-10

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: x2gothincli...@packages.debian.org, sunwea...@debian.org
Control: affects -1 + src:x2gothinclient

Please unblock package x2gothinclient

[ Reason ]

In the context of #1035654, five source packages (including this one)
still fail to purge remove without adduser installed.

[ Impact ]

We want to avoid the situation where a user removes the package, then
upgrades to apt that doesn't depend on adduser, then removes adduser and
then attempts to purge this package.

[ Tests ]

See the script I posted in #1035654.

[ Risks ]

Low risk due to trivial changes (see end of this mail) and because of
low popcon number (36 votes).

In addition to the adduser changes, the diff to testing also includes removal
of lsb-base and policykit-1 (in favour of polkitd). I'll leave it up to the
release team whether those additional changes on top of the adduser changes are
permitted or whether they should be reverted before granting the unblock
request.

[ 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 testing

unblock x2gothinclient/1.5.0.1-10

diff -Nru x2gothinclient-1.5.0.1/debian/changelog 
x2gothinclient-1.5.0.1/debian/changelog
--- x2gothinclient-1.5.0.1/debian/changelog 2022-10-15 12:58:17.0 
+0200
+++ x2gothinclient-1.5.0.1/debian/changelog 2023-05-19 10:59:29.0 
+0200
@@ -1,9 +1,19 @@
-x2gothinclient (1.5.0.1-8.1) unstable; urgency=medium
+x2gothinclient (1.5.0.1-10) unstable; urgency=medium
 
-  * Non-maintainer upload.
-  * No source change upload to rebuild with debhelper 13.10.
+  * debian/changelog:
++ Fix wrong bug closure in upload of 1.5.0.1-9.
 
- -- Michael Biebl   Sat, 15 Oct 2022 12:58:17 +0200
+ -- Mike Gabriel   Fri, 19 May 2023 10:59:29 +0200
+
+x2gothinclient (1.5.0.1-9) unstable; urgency=medium
+
+  * debian/x2gothinclient-common.postrm:
++ Ignore failures during execution of deluser/delgroup. (Closes: #1034755).
+  * debian/control:
++ Drop from D: lsb-base (obsoleted package). Thanks, lintian.
++ Drop from D: policykit-1, replace by polkitd. Thanks, lintian.
+
+ -- Mike Gabriel   Tue, 16 May 2023 22:09:06 +0200
 
 x2gothinclient (1.5.0.1-8) unstable; urgency=medium
 
diff -Nru x2gothinclient-1.5.0.1/debian/control 
x2gothinclient-1.5.0.1/debian/control
--- x2gothinclient-1.5.0.1/debian/control   2022-10-03 11:54:53.0 
+0200
+++ x2gothinclient-1.5.0.1/debian/control   2023-05-16 22:14:12.0 
+0200
@@ -56,7 +56,6 @@
  ${misc:Pre-Depends},
 Depends:
  ${misc:Depends},
- lsb-base,
  nfs-common,
  patch,
  plymouth,
@@ -66,7 +65,7 @@
  dbus-user-session,
  x2gothinclient-displaymanager | x2gothinclient-minidesktop,
  locales,
- policykit-1,
+ polkitd,
 Recommends:
  acpid,
  gnupg-agent,
@@ -187,14 +186,13 @@
  ${misc:Pre-Depends},
 Depends:
  ${misc:Depends},
- lsb-base,
  psmisc,
  pinentry-x2go,
  xauth,
  xinit,
  locales,
  dbus-x11,
- policykit-1,
+ polkitd,
  libfile-path-expand-perl,
  x2gothinclient-common (>= ${source:Version}), x2gothinclient-common (<< 
${source:Version}.1),
 Provides:
@@ -265,7 +263,6 @@
 Depends:
  ${shlibs:Depends},
  ${misc:Depends},
- lsb-base,
  lsscsi,
  eject,
  libfile-path-expand-perl,
diff -Nru x2gothinclient-1.5.0.1/debian/x2gothinclient-common.postrm 
x2gothinclient-1.5.0.1/debian/x2gothinclient-common.postrm
--- x2gothinclient-1.5.0.1/debian/x2gothinclient-common.postrm  2019-12-13 
12:28:29.0 +0100
+++ x2gothinclient-1.5.0.1/debian/x2gothinclient-common.postrm  2023-05-16 
22:07:53.0 +0200
@@ -17,8 +17,8 @@
 
 case "$1" in
purge)
-   getent passwd x2gothinclient >/dev/null && deluser 
x2gothinclient
-   getent group x2gothinclient  >/dev/null && delgroup 
x2gothinclient
+   getent passwd x2gothinclient >/dev/null && deluser 
x2gothinclient || true
+   getent group x2gothinclient  >/dev/null && delgroup 
x2gothinclient || true
 
rm -Rf /var/lib/x2gothinclient

Bug#998940: Bug#965794: python-ooolib: diff for NMU version 0.0.22-5.1

2023-05-20 Thread Rene Engelhard


Hi,

Am 20.05.23 um 12:58 schrieb Andreas Metzler:

How hard is it to communicate? Why didn't you simply write to the
bugreport that you wanted the pkg to be autormed instead of letting
me waste my time?


The waste of time wsn't on my part. From all the QA data visible on DDPO 
this should have been abvious.


Admittedly, I shouldn't have just answered Adrian on his last reset *on 
the day it was supposed to be removed* but just also here, by bad there.



Still...


I have removed the upload.


No, you haven't. I had already.


Regards,


Rene

Bug#1036397: Package: installation-reports

2023-05-20 Thread thomas . chandesris

Package: installation-reports

Boot method: USB key
Image version: debian-bookworm-DI-alpha2-amd64-netinst.iso
Date: 05/19/2023 8:00 PM

Machine: HP HP Stream Notebook
Processor: Intel® Celeron® N2840  × 2
Memory: 2,0 Gio
Partitions:
Sys. de fichiers Type blocs de 1K Utilisé Disponible Uti% Monté sur
udev devtmpfs  921424   0 921424   0% /dev
tmpfstmpfs 1902841552 188732   1% /run
/dev/mmcblk0p2   ext428378028 5997764   20913384  23% /
tmpfstmpfs 951416   0 951416   0% /dev/shm
tmpfstmpfs   5120   8   5112   1% /run/lock
/dev/mmcblk0p1   vfat  5232486112 517136   2% /boot/efi
tmpfstmpfs 190280 120 190160   1%
/run/user/1000

Résultat de lspci -knn :
00:00.0 Host bridge [0600]: Intel Corporation Atom Processor
Z36xxx/Z37xxx Series SoC Transaction Register [8086:0f00] (rev 0e)
Subsystem: Hewlett-Packard Company Atom Processor
Z36xxx/Z37xxx Series SoC Transaction Register [103c:817b]
Kernel driver in use: iosf_mbi_pci
00:02.0 VGA compatible controller [0300]: Intel Corporation Atom
Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e)
DeviceName: Intel(R) HD Graphics
Subsystem: Hewlett-Packard Company Atom Processor
Z36xxx/Z37xxx Series Graphics & Display [103c:817b]
Kernel driver in use: i915
Kernel modules: i915
00:14.0 USB controller [0c03]: Intel Corporation Atom Processor
Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI [8086:0f35] (rev 0e)
Subsystem: Hewlett-Packard Company Atom Processor
Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI [103c:817b]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
00:1a.0 Encryption controller [1080]: Intel Corporation Atom Processor
Z36xxx/Z37xxx Series Trusted Execution Engine [8086:0f18] (rev 0e)
Subsystem: Hewlett-Packard Company Atom Processor
Z36xxx/Z37xxx Series Trusted Execution Engine [103c:817b]
Kernel driver in use: mei_txe
Kernel modules: mei_txe
00:1b.0 Audio device [0403]: Intel Corporation Atom Processor
Z36xxx/Z37xxx Series High Definition Audio Controller [8086:0f04] (rev
0e)
Subsystem: Hewlett-Packard Company Atom Processor
Z36xxx/Z37xxx Series High Definition Audio Controller [103c:817b]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation Atom Processor E3800
Series PCI Express Root Port 1 [8086:0f48] (rev 0e)
Subsystem: Hewlett-Packard Company Atom Processor E3800 Series
PCI Express Root Port 1 [103c:817b]
Kernel driver in use: pcieport
00:1c.1 PCI bridge [0604]: Intel Corporation Atom Processor E3800
Series PCI Express Root Port 2 [8086:0f4a] (rev 0e)
Subsystem: Hewlett-Packard Company Atom Processor E3800 Series
PCI Express Root Port 2 [103c:817b]
Kernel driver in use: pcieport
00:1c.3 PCI bridge [0604]: Intel Corporation Atom Processor E3800
Series PCI Express Root Port 4 [8086:0f4e] (rev 0e)
Subsystem: Hewlett-Packard Company Atom Processor E3800 Series
PCI Express Root Port 4 [103c:817b]
Kernel driver in use: pcieport
00:1f.0 ISA bridge [0601]: Intel Corporation Atom Processor
Z36xxx/Z37xxx Series Power Control Unit [8086:0f1c] (rev 0e)
Subsystem: Hewlett-Packard Company Atom Processor
Z36xxx/Z37xxx Series Power Control Unit [103c:817b]
Kernel driver in use: lpc_ich
Kernel modules: lpc_ich
00:1f.3 SMBus [0c05]: Intel Corporation Atom Processor E3800/CE2700
Series SMBus Controller [8086:0f12] (rev 0e)
Subsystem: Hewlett-Packard Company Atom Processor E3800/CE2700
Series SMBus Controller [103c:817b]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801
02:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries
BCM43142 802.11b/g/n [14e4:4365] (rev 01)
DeviceName: Broadcom WLAN Broadcom Nami 43142 bgn 1x1 + BT 4
LE PCIe+USB NGFF 1630 MOW
Subsystem: Hewlett-Packard Company BCM43142 802.11b/g/n
[103c:804a]
Kernel driver in use: wl
Kernel modules: bcma, wl
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd.
RTS5229 PCI Express Card Reader [10ec:5229] (rev 01)
Subsystem: Hewlett-Packard Company RTS5229 PCI Express Card
Reader [103c:817b]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci

Installation du système de base :
[O] = OK, [E] = Error, [ ] = non essayé

Initial boot:   [O]
Detect network card:[E] for wifi then use USB ethernet [O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Clock/timezone setup:   [O]
User/password setup:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

Still missing non free kernel driver wl for Broadc

Bug#1035975: [pre-approval] unblock: mmdebstrap/1.3.5-X

2023-05-20 Thread Sebastian Ramacher

Control: tags -1 moreinfo

Hi josch

On 2023-05-12 08:06:31 +0200, Johannes Schauer Marin Rodrigues wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> X-Debbugs-Cc: mmdebst...@packages.debian.org
> Control: affects -1 + src:mmdebstrap
> Control: block -1 by #1035654 #1035745 #1035710
> 
> Hi,
> 
> some of the packages uploaded to unstable or experimental are breaking the
> mmdebstrap autopkgtest:
> 
>  - doc-debian rebuilt with debhelper (>= 13.4) changes the doc-base paths. 
> This
>is recorded as #1035913 and the change is intentional. Thus the mmdebstrap
>autopkgtest has to be adjusted. The unblock bug for doc-debian was 
> #1035710.
>  - dash has an upload in experimental which removes its diversions. See bug
>#989632 for details. The unblock bug is #1035745. I also adjusted the
>autopkgtest to cope with those changes.
>  - if it is decided for adduser to become Essential:yes or pseudo-essential
>(instead of using Protected:yes) more changes are required. I didn't
>implement those yet, because I'm still hoping that it will be decided to 
> use
>Protected:yes (in which case no changes are needed). Please consider
>replying to my idea in #1035654
> 
> All of the needed changes only affect the autopkgtest. Nothing touches the
> functionality shipped by the mmdebstrap binary package and thus, this unblock
> cannot break anything (other than autopkgtest results).

Could you please provide a debdiff of the proposed changes?

Cheers
-- 
Sebastian Ramacher

Bug#1036389: sylpheed: notification window displayed as system dialog, not actually not displayed

Hi again,

The problem seems to be that it's not displayed as a window, as the
setting claims, but as a system dialog. Either an additional setting is
added to choose a system dialog/notification or the behaviour is
changed to a window, as the name implies. I would suggest a separate
tickbox for both if retaining the sytem dialog is wanted.

Best regards,
JL

Bug#1035975: [pre-approval] unblock: mmdebstrap/1.3.5-X

Hi,

Quoting Sebastian Ramacher (2023-05-20 13:38:20)
> > some of the packages uploaded to unstable or experimental are breaking the
> > mmdebstrap autopkgtest:
> > 
> >  - doc-debian rebuilt with debhelper (>= 13.4) changes the doc-base paths. 
> > This
> >is recorded as #1035913 and the change is intentional. Thus the 
> > mmdebstrap
> >autopkgtest has to be adjusted. The unblock bug for doc-debian was 
> > #1035710.
> >  - dash has an upload in experimental which removes its diversions. See bug
> >#989632 for details. The unblock bug is #1035745. I also adjusted the
> >autopkgtest to cope with those changes.
> >  - if it is decided for adduser to become Essential:yes or pseudo-essential
> >(instead of using Protected:yes) more changes are required. I didn't
> >implement those yet, because I'm still hoping that it will be decided to 
> > use
> >Protected:yes (in which case no changes are needed). Please consider
> >replying to my idea in #1035654
> > 
> > All of the needed changes only affect the autopkgtest. Nothing touches the
> > functionality shipped by the mmdebstrap binary package and thus, this 
> > unblock
> > cannot break anything (other than autopkgtest results).
> 
> Could you please provide a debdiff of the proposed changes?

this is the debdiff between mmdebstrap in testing and unstable:

diff -Nru mmdebstrap-1.3.5/debian/changelog mmdebstrap-1.3.5/debian/changelog
--- mmdebstrap-1.3.5/debian/changelog   2023-03-20 08:05:19.0 +0100
+++ mmdebstrap-1.3.5/debian/changelog   2023-05-11 14:53:04.0 +0200
@@ -1,3 +1,29 @@
+mmdebstrap (1.3.5-5) unstable; urgency=medium
+
+  * tests/jessie-or-older: dash 0.5.12-3 dropped diversions
+
+ -- Johannes Schauer Marin Rodrigues   Thu, 11 May 2023 
14:53:04 +0200
+
+mmdebstrap (1.3.5-4) unstable; urgency=medium
+
+  * tests/eatmydata-via-hook-dir: dash 0.5.12-3 dropped diversions
+
+ -- Johannes Schauer Marin Rodrigues   Thu, 11 May 2023 
06:57:42 +0200
+
+mmdebstrap (1.3.5-3) unstable; urgency=medium
+
+  * fix regex in debian/tests/copy_host_apt_config to first remove
+non-free-firmware and then non-free or otherwise components like
+"main-firmware" will be the result
+
+ -- Johannes Schauer Marin Rodrigues   Wed, 10 May 2023 
22:41:17 +0200
+
+mmdebstrap (1.3.5-2) unstable; urgency=medium
+
+  * fix for doc-debian 11.0 changing the doc-base paths
+
+ -- Johannes Schauer Marin Rodrigues   Sat, 06 May 2023 
19:15:48 +0200
+
 mmdebstrap (1.3.5-1) unstable; urgency=medium
 
   * New upstream version 1.3.5
diff -Nru 
mmdebstrap-1.3.5/debian/patches/0001-tests-doc-debian-11.0-changed-the-doc-base-paths.patch
 
mmdebstrap-1.3.5/debian/patches/0001-tests-doc-debian-11.0-changed-the-doc-base-paths.patch
--- 
mmdebstrap-1.3.5/debian/patches/0001-tests-doc-debian-11.0-changed-the-doc-base-paths.patch
 1970-01-01 01:00:00.0 +0100
+++ 
mmdebstrap-1.3.5/debian/patches/0001-tests-doc-debian-11.0-changed-the-doc-base-paths.patch
 2023-05-11 14:53:04.0 +0200
@@ -0,0 +1,81 @@
+From e27a8d34724673f4df07b5827c921a9b63903095 Mon Sep 17 00:00:00 2001
+From: Johannes Schauer Marin Rodrigues 
+Date: Sat, 6 May 2023 08:33:15 +0200
+Subject: [PATCH] tests: doc-debian 11.0 changed the doc-base paths
+
+---
+ tests/include   | 2 +-
+ tests/install-doc-debian| 2 +-
+ tests/install-doc-debian-and-test-hooks | 2 +-
+ tests/multiple-include  | 2 +-
+ tests/unpack-doc-debian | 2 +-
+ 5 files changed, 5 insertions(+), 5 deletions(-)
+
+diff --git a/tests/include b/tests/include
+index 95c9c69..e284b7d 100644
+--- a/tests/include
 b/tests/include
+@@ -3,7 +3,7 @@ set -eu
+ export LC_ALL=C.UTF-8
+ trap "rm -rf /tmp/debian-chroot" EXIT INT TERM
+ {{ CMD }} --mode=root --variant=apt --include=doc-debian {{ DIST }} 
/tmp/debian-chroot {{ MIRROR }}
+-rm /tmp/debian-chroot/usr/share/doc-base/debian-*
++rm /tmp/debian-chroot/usr/share/doc-base/doc-debian.debian-*
+ rm -r /tmp/debian-chroot/usr/share/doc/debian
+ rm -r /tmp/debian-chroot/usr/share/doc/doc-debian
+ rm /tmp/debian-chroot/var/lib/apt/extended_states
+diff --git a/tests/install-doc-debian b/tests/install-doc-debian
+index 81cb513..27d7f3e 100644
+--- a/tests/install-doc-debian
 b/tests/install-doc-debian
+@@ -24,7 +24,7 @@ tar -C /tmp/debian-chroot --owner=0 --group=0 
--numeric-owner --sort=name --clam
+ tar tvf /tmp/debian-chroot.tar > doc-debian.tar.list
+ rm /tmp/debian-chroot.tar
+ # delete contents of doc-debian
+-rm /tmp/debian-chroot/usr/share/doc-base/debian-*
++rm /tmp/debian-chroot/usr/share/doc-base/doc-debian.debian-*
+ rm -r /tmp/debian-chroot/usr/share/doc/debian
+ rm -r /tmp/debian-chroot/usr/share/doc/doc-debian
+ # delete real files
+diff --git a/tests/install-doc-debian-and-test-hooks 
b/tests/install-doc-debian-and-test-hooks
+index 6ad36eb..e69066c 100644
+--- a/tests/install-doc-debian-and-test-hooks
 b/tests/install-doc-debian-and-test-hooks
+@@ -27,7 +27,7 @

Bug#1035436: rkdeveloptool: diff for NMU version 1.32+git20210408.46bb4c0-2.1

2023-05-20 Thread Christopher Obbard

Hi Andreas,

I uploaded a new version this morning with the fix; it has a -3 suffix so it 
should reject your NMU which had a -2.1 suffix.

As I am fairly new to Debian processes, it is great you have walked me through 
it.

Thank you!

On 20 May 2023 12:07:03 BST, Andreas Metzler  wrote:
>On 2023-05-20 Christopher Obbard  wrote:
>[...] 
>> > I've prepared an NMU for rkdeveloptool (versioned as
>> > 1.32+git20210408.46bb4c0-2.1) and uploaded it to DELAYED/1.
>[...]
>> Thank you for your contribution, but it seems like there is some
>> parallel work (this morning in fact).
>
>> I am currently in the process of uploading and the fixes for this
>> package. Is it possible to skip this delayed version in favour of the
>> version I am about to upload ?
>
>Hello Christopher,
>
>if you upload before the NMU is accepted the NMU will simply be
>rejected because there is already a higher numbered version of the
>package in the archive. I can also simply cancel the NMU or bump the
>delay if you want me to. - Just tell me what your preference is.
>
>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#1036398: sylpheed: Messages menu entries don't belong logically to Tools

Package: sylpheed
Version: 3.7.0-8
Severity: important
Tags: upstream

There are six Tools menu entries that are not intrinsically tools
actions but Messages', and most are verbosely tagged as such in
their names instead of moving them their own menu, making Sylpheed hard
to use and inconvenient. A Messages menu would be necessary and
expected.

This seriously affects usability, so marking it as important.

Bug#1036358: release-notes: Debian 12 expected to be last release w/ installer for i386

2023-05-20 Thread RL

Ansgar  writes:

> On Fri, 2023-05-19 at 15:03 +0100, Steve McIntyre wrote:
>> My plan is therefore to ship i386 installer images
>> for bookworm as normal (including bookworm point releases going
>> forwards), but to disable those builds for testing/trixie
>> ~immediately after the release.
>
> I suggest to already document this in the release notes for bookworm,
> possibly in Section 2.1 (Supported architectures) or a subsection in
> Section 5 (Issues to be aware of for bookworm).

I suspect few would re-read 2.1 on upgrade... but is release-notes is
the best place to document what new installs can use? (maybe doesnt
matter as there wont be any new installs!)

> Maybe something along these lines:
>
> +---
> | Debian 12 is expected to be the last Debian release providing
> | full support for i386.  Debian 13 will only partially support
> | i386 and no longer provide installation media for i386.
> |
> | We recommend hosts still running the i386 port to be upgraded
> | to amd64.  Legacy i386 software can be run using multi-arch,
> | chroot environments or containers.
> +---

We already have a bit about i386 now meaning i686, but i think OK to
keep separate as that one is bookworm, and this is for the future

Adding links to explain jargon and adding markup: im hope ive got the right
arch-related entities right here...

Bookworm is the last Debian release with full support for &arch-title;

The next release, trixie, will not have full support for the
&architecture; architecture, for example there will be no official
installer. 

Debian recommends converting systems using the &architecture;
architecture to the 64-bit
PC architecture (known as amd64) before bookworm
becomes unsupported: 
most computers manufactured since 2000 can use
amd64.

You can still run legacy 32-bit software on 64-bit systems using containers

or in multi-arch
chroots.

(but shld use the &url-wiki; entity for wiki links)

Perhaps https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995397 (Xen no
longer supports 32-bit Xen PV guests) also relevent to the last para.

Bug#1036399: piuparts: false positives for unowned files left after purge

2023-05-20 Thread David Bremner

Package: piuparts
Version: 1.1.7
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

The following output from "piuparts -t /var/tmp --apt emacs" (also on 
piuparts.debian.org) looks suss to me:

0m43.8s INFO: Warning: Package purging left files on system:
  /root/.ssh/not owned
  /var/cache/private/not owned
  /var/lib/private/  not owned
  /var/lib/systemd/coredump/ not owned
  /var/lib/systemd/pstore/   not owned
  /var/log/private/  not owned


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

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

Versions of packages piuparts depends on:
ii  debootstrap  1.0.128+nmu2
ii  debsums  3.0.2
ii  libjs-sphinxdoc  5.3.0-4
ii  lsb-release  12.0-1
ii  lsof 4.95.0-1
ii  mount2.38.1-5+b1
ii  piuparts-common  1.1.7
ii  python3  3.11.2-1+b1
ii  python3-debian   0.1.49

Versions of packages piuparts recommends:
ii  adequate  0.15.7

Versions of packages piuparts suggests:
pn  docker.io  
ii  schroot1.6.13-3+b2

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmRouNgACgkQA0U5G1Wq
FSHw/g//YwVnH0E80KXR/8+Jd0wxln+7uV0RL4+37tTVUnDEW1zpRATFJ/fPvzaO
Oih497KyhqQMGyAmXHyBE1dAuzkdH5c5njOwx+5xJwNEs13GKf1AIo6g25g2vBWp
2205rcaguq47+IMBp0TvkvqO5rMKblzkKoV1v4yik4qNmxZXLHW/asFEeWkyy3aV
vrOcfHpt+znmwsx68AoXLyWGdYeK3Gvkm4i7fNssVOD3Ybfw/7Mr0Md2aexrcKB0
n4BpchI1zamvo5awgyqY8yhXAJWsZfeEkOhcyQ6d1+vr3+Kw9VFqCDkfPwN1nUb7
+EM/cVyHOM4WF2yaiSn4VQgHgpt4aec2hKJ9Fi0hXyTwFOpjMett0zB22LthR5aF
MgEYIzY2T4WiwsbdfO6v239qTc4KSDWrXNqO4dpND1tpun5XNXO4HKQJnwmglVhy
HMj0xhsH3TcEnf9aWgRW4uSOijAQ3zPMA0oHCzc53CFeBI8JQqegJNjLtJJ0djGs
Cc1iVc6lvW4nk7m5u8ZWkss2ywtjmEiHCJwA5qCY7R9hiCpfp1bSOpAuYsTL24j2
EkbUXM/AX7CRBD9YsGSK7yVRjygP7RN/3bgG+cac86mSrUPHs+51PpipqLaqcVur
XEqOUTDM/baxLIAPpqSYjeTPnVCKJI6X/YJ7nxlNpJX4t1ktSYc=
=rY+H
-END PGP SIGNATURE-

Bug#1036388: sylpheed: account is reset when mail is checked

retitle 1036388 account reset when mail is checked
tags 1036388 upstream
thanks

Hi again,

It turns out the bug doesn't happen when email is received, but rather
when it was checked by sylpheed, which makes it even more grave, since
it's resetting it every X minutes, 10 in my case.

Bug#932957: Please migrate Release Notes to reStructuredText

2023-05-20 Thread RL

The following message is a courtesy copy of an article
that has been posted to gmane.linux.debian.devel.documentation as well.

James Addison  writes:

> (someone who knows more may correct me, but I think it would be great to have
> the package available for install using apt in addition to the website)

Interesting idea, but who would use it - won't a release-notes package
always be a whole release out of date?

(and the build-dependencies take a huge amount of disk space for
something you only read once a cycle, alhtough maybe sphinx fixes that)

Bug#1036400: partman-jfs: JFS is on its way out, please remove from the installer

2023-05-20 Thread Adam Borowski

Package: partman-jfs
Severity: important

Hi!
The JFS filesystem is deprecated in the kernel: on life support since 2009
and with talks of removal altogether.  Thus, we really shouldn't offer to
format new setups with it.  There are people who kind-of remember JFS being
the fastest back in the day, and it's irresponsible to set them for failed
upgrades past Bookworm.

Thus: please remove JFS from the installer.


Meow!

Bug#1036401: tools-dep-clojure/0.16.1264-3

2023-05-20 Thread Jérôme Charaoui


Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: team+cloj...@tracker.debian.org
Control: affects -1 + src:tools-dep-clojure

I would like to request an unblock to upload 
tools-dep-clojure/0.16.1264-3 which fixes a FTBFS bug.


- #1036386 - tools-deps-clojure: FTBFS without network access

[ Reason ]
The package currently FTBFS because the testsuite which runs during 
build requires network access.


[ Impact ]
Accepting this release should not have any impact beyond 
tools-dep-clojure itself. libtools-dep-clojure has no rdeps in bookworm.


[ Tests ]
Test-related FTBFS issue was reproduced and fixed locally. Autopkgtest 
are passing.


[ Risks ]
None that I can imagine considering the very small delta.

[ 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 testing


Thanks!

-- Jérômediff -Nru tools-deps-clojure-0.16.1264/debian/changelog 
tools-deps-clojure-0.16.1264/debian/changelog
--- tools-deps-clojure-0.16.1264/debian/changelog   2023-01-22 
22:02:21.0 -0500
+++ tools-deps-clojure-0.16.1264/debian/changelog   2023-05-20 
08:54:30.0 -0400
@@ -1,3 +1,9 @@
+tools-deps-clojure (0.16.1264-3) unstable; urgency=medium
+
+  * d/run-build-tests: skip test that requires internet (Closes: #1036386)
+
+ -- Jérôme Charaoui   Sat, 20 May 2023 08:54:30 -0400
+
 tools-deps-clojure (0.16.1264-2) unstable; urgency=medium
 
   * Team upload.
diff -Nru tools-deps-clojure-0.16.1264/debian/run-build-tests 
tools-deps-clojure-0.16.1264/debian/run-build-tests
--- tools-deps-clojure-0.16.1264/debian/run-build-tests 2023-01-22 
22:02:21.0 -0500
+++ tools-deps-clojure-0.16.1264/debian/run-build-tests 2023-05-20 
08:54:30.0 -0400
@@ -12,6 +12,5 @@
 -e "(require '[clojure.tools.deps.util.dir-test])" \
 -e "(System/exit (if (clojure.test/successful? (clojure.test/run-tests
 'clojure.tools.deps.extensions.faken
-'clojure.tools.deps.extensions.test-git
 'clojure.tools.deps.gen.test-pom
 'clojure.tools.deps.util.dir-test)) 0 1))"

Bug#1036402: doc-debian: forwarded missing from tags lists

Package: doc-debian
Version: 6.5
Severity: important

Hi,

forwarded tag is missing from 

- tags list on tags command on bug-maint-mailcontrol.txt.gz
- the tags definition list from bug-maint-info.txt.gz

Regards,
JL

Bug#1036399: piuparts: false positives for unowned files left after purge

2023-05-20 Thread David Bremner

David Bremner  writes:

> Package: piuparts
> Version: 1.1.7
> Severity: normal
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> The following output from "piuparts -t /var/tmp --apt emacs" (also on 
> piuparts.debian.org) looks suss to me:
>
> 0m43.8s INFO: Warning: Package purging left files on system:
>   /root/.ssh/  not owned
>   /var/cache/private/  not owned
>   /var/lib/private/not owned
>   /var/lib/systemd/coredump/   not owned
>   /var/lib/systemd/pstore/ not owned
>   /var/log/private/not owned

I just verified that something creates /root/.ssh when I run "apt
install --no-install-recommends systemd" in a clean chroot.  So that
part is a bug in some other package (presumably systemd or a
dependency), not piuparts.

Bug#1036354: unblock: iptables-persistent/1.0.20

2023-05-20 Thread gustavo panizzo

Hi

On May 20, 2023 10:42:20 AM UTC, Luca Boccassi  wrote:
>On Sat, 20 May 2023 at 11:29, gustavo panizzo  wrote:
>>
>> Hi
>>
>> On May 20, 2023 10:20:50 AM UTC, Luca Boccassi  wrote:
>> >On Fri, 19 May 2023, 15:39 gustavo panizzo,  wrote:
>> >
>> >> Package: release.debian.org
>> >> Severity: normal
>> >> User: release.debian@packages.debian.org
>> >> Usertags: unblock
>> >> X-Debbugs-Cc: bl...@debian.org
>> >>
>> >> Please unblock package iptables-persistent
>> >>
>> >> (Please provide enough (but not too much) information to help
>> >> the release team to judge the request efficiently. E.g. by
>> >> filling in the sections below.)
>> >>
>> >> [ Reason ]
>> >> The package is using alternatives to manage (systemd) aliases,
>> >> this is not recommended by the systemd maintainers.
>> >>
>> >> See bug report #1036147
>> >>
>> >>
>> >> I've added alternatives to this package back in 2019 to solve #926927
>> >> as a point of coordination with other firewall managers in Debian
>> >> (see https://lists.debian.org/debian-firewall/2019/08/msg0.html) but
>> >> the initiative never took off
>> >>
>> >>
>> >> [ Impact ]
>> >> This is (was) the only package in Debian which uses alternatives to
>> >> manage aliases, which makes it different from what admins expect
>> >>
>> >> [ Tests ]
>> >> This version of the package is clean in lintian and piuparts,
>> >> I've upgraded my systems and found no problems
>> >>
>> >>
>> >> [ Risks ]
>> >> I see no risks, if an admin locally have changed the override files,
>> >> we'll keep them as dpkg-bak
>> >>
>> >>
>> >> [ 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 testing
>> >>
>> >>
>> >> unblock iptables-persistent/1.0.20
>> >>
>> >
>> >Thanks for taking care of this - I just checked and cannot see the upload
>> >to unstable though?
>>
>> I'd prefer to wait for an ack from the release team
>
>Ok, in that case I think it should be explicitly mentioned that this
>is a 'preapproval' request.


How to do that? I hope is done now 


>
>Kind regards,
>Luca Boccassi

Bug#1036403: Unable to accept server certificate in Kalendar

2023-05-20 Thread mikus mikuskowy

Package: kalendar
Version: 22.12.3-1
User: Mikolaj
Severity: important

When I try to add remote (from my Nextcloud instance) calendar in KDE's
Kalendar app, I am not able to accept the server's (self signed)
certificate - the window completely freezes (window's title:
Server-Authentifizierung -- akonadi_davgroupware_resource_4), I cannot
click any button, even the buttons don't change their state (appearance)
when I hover or click them. When I try to close the window by clicking the
close button, it doesn't work. I also noticed another probably related bug
- when I try to add remote directory (SFTP connection) in Dolphin (when you
open Dolphin, you have "Network" category on left), I wasn't able to accept
server's ssh certificate, because the window also freezes. After a few
tries (I don't know how) I accepted it, but also got the following message
from KDE Plasma Desktop:


KNetAttach
Prüfung (Fehlgeschlagen)
Die Anwendung wurde unerwartet beendet.


I think that the problem may also be related with apps like Akonadi and
KNetAttach (and Wayland?) and the bug may also affect other KDE
applications, that allow to connect with remote servers.

I am using Debian 12 Bookworm (testing), KDE Plasma Desktop (version:
4:5.27.2-2, but the bug occured also on version 4:5.27.2-1) and Wayland.
plasma-framework version: 5.103.0-1
Qt version: 5.18.8
Kernel version: 6.1.27-1 amd64

I am using swiss keyboard layout and system language is Schweizer
Hochdeutsch (swiss german).

Bug#1035757: unblock: org-mode/9.5.2+dfsh-5

2023-05-20 Thread David Bremner

David Bremner  writes:

> 1m1.2s ERROR: FAIL: Package purging left files on system:
>   /root/.ssh/ not owned
>   /var/cache/private/ not owned
>   /var/lib/private/   not owned
>   /var/lib/systemd/coredump/  not owned
>   /var/lib/systemd/pstore/not owned
>   /var/log/private/   not owned
>

I dove down this rabbit-hole a bit, not enough to figure the ultimate
cause, but enough to notice these files are also because of
"apt install systemd". So no related to org-mode. FWIW, systemd is
pulled in by emacs-gtk.

d

Bug#1036404: lxpanel segfaults when returning from suspend

2023-05-20 Thread Eric Van Buggenhaut

Package: lxpanel
Version: 0.10.1-2
Severity: normal
X-Debbugs-Cc: ericv...@gmail.com

After waking up from suspend, my lxpanel crashes, everytime. Segfaults seems to 
be related to libgtk2.0

 lxpanel[107889]: segfault at 7f6c616e ip 7fd337024823 sp 
7fff01f0dc70 error 4 in libgtk-x11-2.0.so.0.2400.33[7fd336e24000+275000]
[125195.305791] Code: 1f 84 00 00 00 00 00 41 54 55 48 83 ec 08 48 85 ff 74 4c 
48 89 fd 49 89 f4 e8 b9 23 ff ff 48 89 c6 48 8b 45 00 48 85 c0 74 05 <48> 39 30 
74 0c 48 89 ef e8 a0 3c e0 ff 85 c0 74 24 48 83 c4 08 4c



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

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

Versions of packages lxpanel depends on:
ii  libasound2   1.2.4-1.1
ii  libc62.36-9
ii  libcairo21.16.0-5
ii  libcurl3-gnutls  7.88.1-9
ii  libfm-gtk4   1.3.2-1
ii  libfm-modules1.3.2-1
ii  libfm4   1.3.2-1
ii  libgdk-pixbuf-2.0-0  2.42.2+dfsg-1+deb11u1
ii  libglib2.0-0 2.74.6-2
ii  libgtk2.0-0  2.24.33-2
ii  libiw30  30~pre9-13.1
ii  libkeybinder00.3.1-2.1
ii  libmenu-cache3   1.1.0-1.1
ii  libpango-1.0-0   1.46.2-3
ii  libwnck222.30.7-6
ii  libx11-6 2:1.8.4-2
ii  libxml2  2.9.10+dfsg-6.7+deb11u4
ii  lxmenu-data  0.1.5-2.1
ii  lxpanel-data 0.10.1-2

Versions of packages lxpanel recommends:
ii  dunst [notification-daemon]   1.5.0-1
ii  libnotify-bin 0.7.9-3
ii  lxterminal [x-terminal-emulator]  0.4.0-1
ii  notification-daemon   3.20.0-4
ii  pavucontrol   4.0-2
ii  xkb-data  2.29-2
ii  xterm [x-terminal-emulator]   366-1+deb11u1

Versions of packages lxpanel suggests:
ii  firefox-esr [www-browser]   102.10.0esr-1~deb11u1
ii  google-chrome-stable [www-browser]  113.0.5672.92-1
ii  menu2.1.48

-- no debconf information

Bug#1036405: sylpheed: message subject in compose windows get clipped in some window managers' list

Package: sylpheed
Version: 3.7.0-8
Tags: upstream

Compose windows feature the string "Compose *" after the subject in the
window's title. This string effectively clips the message's subject,
which is more important, in my Window's manager (xfwm4) working areas
list, which includes windows, because the width of the window list is
limited.

I'm going to file another bug to xfwm because of the artificial width
limit, but I suspect the clipping is a Sylpheed bug.

Bug#1036406: xfwm4: Working area list width artificially limited

Package: xfwm4
Version: 4.16.1-1
Severity: important
Tags: upstream

The width of the Working Area list displayed middle-clicking on desktop
is severely limited for no reason, preventing enough of the window
titles to be seen when they are long enough, which has a very major
effect on the usability of the feature.

This is a bit variable, since this list is displayed with a variable
width font, but it more or less displays only 22 characters from the
title. This is clipping 5 out of 10 windows on my desktop at this time.

It makes no sense to place a width limit on this list, since the space
needed is variable, can be actually a lot, and it's not known in
advance how much is needed. If anything only preventing the
window from being larger than the screen is necessary.

Bug#1036407: sylpheed: compose mail shortcut doesn't work in compose window

Package: sylpheed
Version: 3.7.0-8
Severity: important
Tags: upstream

Control + M shortcut doesn't work in compose windows, effectively
preventing from opening a new compose message window while composing a
current one. This is something that happens often so such a restriction
only makes it difficult and tiresome to use Sylpheed, as it forces
you to open Sylpheed's window to be able to create it, and locate the
existing compose window afterwards, as Sylpheed window is likely to have
concealed the already existing compose window.

Bug#1035710: unblock: doc-debian/11.3

2023-05-20 Thread Sebastian Ramacher

Control: tags -1 moreinfo cofnirmed

On 2023-05-14 06:47:18 +0200, Joost van Baal-Ilić wrote:
> reopen 1035710
> retitle 1035710 unblock: doc-debian/11.3
> thanks
> 
> Please unblock package doc-debian
> 
> [ Reason ]
> The doc-debian package claims to ship the Constitution for the Debian Project,
> the Debian Social Contract and other Debian documents.  The versions of those
> documents are obsolete [obsolete], which makes the package as now in testing
> very buggy.
> 
> [ Impact ]
> Shipping obsolete foundational documents is misleading and therefore might
> lead to confusion.
> 
> [ Tests ]
> None.  (The package ships documentation only, no code is shipped in the
> binary package.)
> 
> [ Risks ]
> None.  The doc-debian package is a key package due to Priority: standard.  It
> acts as a leaf package: Its only true reverse depends is the 
> live-task-standard
> package.[reverse-depends]  In bug #1035913 however, it was shown that some
> autopkgtests failed with the new doc-debian due to changes in build
> environment. This issue now has been properly documented.
> 
> [ 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 testing
> 
> [ Other info ] I made a mistake uploading doc-debian 11.0 to unstable; that 
> got
> accepted.  The version 11.3 is now available from experimental.  I've kept the
> diff minimal.  Earlier planned and implemented non-related fixes will, via
> experimental and unstable, end up in 13/trixie.
> 
> unblock doc-debian/11.3

Please go ahead with the upload to unstable. Remove the moreinfo tag
once the package is available.

Cheers
-- 
Sebastian Ramacher

Bug#1036358: release-notes: Debian 12 expected to be last release w/ installer for i386

2023-05-20 Thread Justin B Rye

RL wrote:
> Ansgar  writes:
>> On Fri, 2023-05-19 at 15:03 +0100, Steve McIntyre wrote:
>>> My plan is therefore to ship i386 installer images
>>> for bookworm as normal (including bookworm point releases going
>>> forwards), but to disable those builds for testing/trixie
>>> ~immediately after the release.
>>
>> I suggest to already document this in the release notes for bookworm,
>> possibly in Section 2.1 (Supported architectures) or a subsection in
>> Section 5 (Issues to be aware of for bookworm).
> 
> I suspect few would re-read 2.1 on upgrade... but is release-notes is
> the best place to document what new installs can use? (maybe doesnt
> matter as there wont be any new installs!)

I would expect a debian-announce message when it happens.

>> Maybe something along these lines:
>>
>> +---
>> | Debian 12 is expected to be the last Debian release providing
>> | full support for i386.  Debian 13 will only partially support
>> | i386 and no longer provide installation media for i386.
>> |
>> | We recommend hosts still running the i386 port to be upgraded
>> | to amd64.  Legacy i386 software can be run using multi-arch,
>> | chroot environments or containers.
>> +---
> 
> We already have a bit about i386 now meaning i686, but i think OK to
> keep separate as that one is bookworm, and this is for the future
> 
> Adding links to explain jargon and adding markup: im hope ive got the right
> arch-related entities right here...
> 
>   
>
> Bookworm is the last Debian release with full support for &arch-title;
> 
>

Title lines don't need to be full sentences; this could be just
"&arch-title; support to be reduced from trixie".

>
> The next release, trixie, will not have full support for the
> &architecture; architecture, for example there will be no official
> installer. 
>

Do we need a mention of the reason (i.e. that an increasing number of
upstreams are no longer supporting it)?

Perhaps the angle the Release Notes should be taking on this is to
announce what's going to happen for dist-upgrades to trixie/forkie.
When do we stop producing official Release Notes?

>
> Debian recommends converting systems using the &architecture;
> architecture to the 64-bit
> PC architecture (known as amd64) before bookworm
> becomes unsupported: 

How about "https://wiki.debian.org/CrossGrading";? I was worried that it
might be a pre-systemd relic, but apparently not.

> most computers manufactured since 2000 can use
> amd64.

I'd have guessed later, given that the i386 arch held the lead in
popcon until 2012 ("https://www.debian.org/News/weekly/2012/17/";), but
this may just be because I use junk hardware.

>
>
> You can still run legacy 32-bit software on 64-bit systems using  url="&url-wiki;SystemVirtualization">containers
> 
> or in  url="&url-wiki;Multiarch/HOWTO">multi-arch
> chroots.
>
>  
> 
> (but shld use the &url-wiki; entity for wiki links)
> 
> Perhaps https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995397 (Xen no
> longer supports 32-bit Xen PV guests) also relevent to the last para.

It would make a relevant link for the "increasing number of upstreams"
I was mentioning.
-- 
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package

Bug#1036381: gnubg: Remove libcanberra (sound support)

2023-05-20 Thread Russ Allbery

Bastian Germann  writes:

> The package builds without the libcanberra-gtk-dev build dependency.
> Dropping it would help with the removal of libcanberra's gtk2 flavor
> because gnubg is its last reverse dependency.

> This will remove sound in the game but I do not think that this is
> important to play it.

I'm still hoping that upstream will port to GTK+ 3 (or later) before I
have to start removing functionality.  I realize that it's on borrowed
time, though, and I totally understand if the GNOME maintainers want to
remove some of these old libraries before the next release.

-- 
Russ Allbery (r...@debian.org)

Bug#950268: sunxi-fel: commands spl and uboot does not work

2023-05-20 Thread Ian Campbell

On Fri, 2020-01-31 at 01:11 +0530, Arjun wrote:

Thank you for your report. I'm very sorry, I seem to have somehow
missed this bug when it originally arrived, I don't know how.

> Both commands fail with a "usb_bulk_send() ERROR -7: Operation timed out" but
> if i pull the code from upstream, even with the same commit as the one used in
> Debian(6d598a0), it works.

That is rather odd. There are no meaningful changes to the upstream
code in this version of the package.

Where did you get uart0-helloworld-sdboot.sunxi from, since it was not
shipped in version 1.4.2+git20181114.6d598a-3, did you use the same
binary in both tests?

Possibly your freshly built version ended up using a different libusb,
since that is what usb_bulk_send is reporting an error from.

Are you in a position to test 1.4.2+git20221128.530adf-2 from Bookworm?
It is a much newer upstream snapshot so may have resolved your issue.

Thanks,
Ian.

Bug#1036408: sylpheed: wrap paragraph doesn't format the paragraph on compose

Package: sylpheed
Version: 3.7.0-8
Severity: important
Tags: upstream

Format paragraph (Control + L & Control + Alt + L) on compose window
doesn't actually format paragraphs, which is what is needed most often,
and rather trivial to implement. The need for formatting is, actually,
rather common. I will elaborate.

I think this "feature", as it stands, is badly posed. It makes no sense
in a program to force the user to format manually with a ruler, which
by the way, doesn't extend for the whole editing window, and expecting
mails to be sent with no formatting would be a complete no sense as well
since line length is limited in the standard to 1023 characters, and
auto-formatting them on display is actually made with MIME-HTML, which
Sylpheed doesn't support.

Besides, a paragraph isn't usually "wrapped", but formatted. Wrapping
the last line is, basically, the unusual case. When you edit you
basically need to reformat the whole thing.

And turning on auto-wrap isn't the solution either, as it breaks lines
that need to be left longer, which happens often in the internet (a
URL, for instance). Turning it on by default is usually not an option.

Bug#1036409: sylpheed: spell check language detection badly missing

Package: sylpheed
Version: 3.7.0-8
Severity: wishlist
Tags: upstream

Hi,

I find it terribly cumbersome to have to choose the spelling language
of each email message I compose. Auto detection would be trivial to
implement. All is needed is to measure the number of spelling "errors"
in each language, choosing the one with least "mistakes".

I would appreciate if this is implemented.

Thank you so much in advance.

Bug#1035725: rdiff-backup bug

2023-05-20 Thread Otto Kekäläinen

Severity: important

Hi!

Yes, we could try push this into Bookworm, but importance needs to be
justified.

Can you explain the problem and severity of the issue, steps to reproduce
and maybe copy-paste the command and resulting error message too?

Bug#1036410: sylpheed: save message missing from the interface

Package: sylpheed
Version: 3.7.0-8
Severity: important
Tags: upstream

Hi,

Save message is missing from the interface. It's only possible to do
this with "File" -> "Export mail", and you would have to mark "Export
only selected messages". This is something quite usual, and it's not
that intuitive to do it in the existing way, so it makes a lot of sense
that it exists both in the Message menu and messages context menu.

With the number of features of Sylpheed, and at version 3.7, this is
something that shall have been there a long time ago, before
version 1 IMHO. Marking it as an important bug for that reason.

Bug#1036398: sylpheed: Messages menu entries don't belong logically to Tools

Hi again,

I mistakenly asked for a Messages menu to be added for this. Upon
review, I think it makes sense on the existing Message menu.

Sorry for the confusion.

Bug#1036411: sylpheed: no option for getting thrash emptied on messages older than X days

Package: sylpheed
Version: 3.7.0-8
Severity: important
Tags: upstream

I find no option for getting messages older than X days deleted from
Thrash, only on Sypheed's exit.

Like my recent save message report, this is something elementary that
should have been there since about version 1, and has a major effect on
the usability of the program, so marking as important.

Sorry Ricardo that I'm filing all these upstream bugs on Debian, but as
far as I know Sylpheed doesn't have a BTS.

Bug#1036411: sylpheed: no option for getting thrash emptied on messages older than X days

retitle 1036411 sylpheed: no option for getting messages deleted from thrash 
after X days of being deleted
thanks

On Sat, 20 May 2023 17:17:57 +0200
José Luis González  wrote:

> I find no option for getting messages older than X days deleted from
> Thrash, only on Sypheed's exit.

Sorry, I meant the messages from Thrash that had been deleted X days
ago or more, not the messages that were sent that days ago, obviously :)

Retitling consequently.

Bug#950268: sunxi-fel: commands spl and uboot does not work

2023-05-20 Thread Arjun


On 20/05/23 20:08, Ian Campbell wrote:

On Fri, 2020-01-31 at 01:11 +0530, Arjun wrote:

Thank you for your report. I'm very sorry, I seem to have somehow
missed this bug when it originally arrived, I don't know how.


Both commands fail with a "usb_bulk_send() ERROR -7: Operation timed out" but
if i pull the code from upstream, even with the same commit as the one used in
Debian(6d598a0), it works.


That is rather odd. There are no meaningful changes to the upstream
code in this version of the package.

Where did you get uart0-helloworld-sdboot.sunxi from, since it was not
shipped in version 1.4.2+git20181114.6d598a-3, did you use the same
binary in both tests?

Possibly your freshly built version ended up using a different libusb,
since that is what usb_bulk_send is reporting an error from.

Are you in a position to test 1.4.2+git20221128.530adf-2 from Bookworm?
It is a much newer upstream snapshot so may have resolved your issue.

Thanks,
Ian.



You may close this bug. Its been a long while and i don't remember what 
i was trying to do here. It might also be not reproducible anymore.


-
Arjun

Bug#1036412: appconfig: Missing copyright info in d/copyright


Source: appconfig
Version: 1.71-2.1
Severity: serious

Andy Wardley's copyright is missing from debian/copyright.
Please document it there.

Bug#1036413: asterisk-prompt-fr-armelle: please consider upgrading to 3.0 source format


Source: asterisk-prompt-fr-armelle
Version: 20070613-2.2
Severity: wishlist

Dear maintainer,

This package is among the few that still use source format 1.0 in
bookworm.  Please upgrade it to source format 3.0, as (1) this format has many
advantages, as documented in https://wiki.debian.org/Projects/DebSrc3.0 ; (2)
this contributes to standardization of packaging practices.

Thanks,
Bastian

Bug#1036356: stress-ng: autopkgtest failures on 32 bit architectures

2023-05-20 Thread Colin King (gmail)

Thanks for the update, I'm planning to make a stress-ng release that 
contains this fix before the end of next week to address this and 
several other issues.


Colin


On 19/05/2023 16:21, Benjamin Drung wrote:

Package: stress-ng
Version: 0.15.07-1
Severity: serious
Tags: patch
Justification: autopkgtest failures
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu mantic ubuntu-patch
X-Debbugs-Cc: bdr...@debian.org

Dear Maintainer,

The autopkg tests on 32 bit architectures fail. In Ubuntu, the attached
patch was applied to fix the autopkgtest:

   * Cherry-pick upstream commit "stress-pthread: use 64 bit tid_addr to fix
 stack clobbering on 32 bit platforms" and "stress-pthread: fix big endian
 tid addr for 32 bit systems" to fix test failures on 32 bit architectures
 (LP: #2019079)


Thanks for considering the patch.

Bug#1036414: sylpheed: Select all and Delete missing from Searched messages context menu

Package: sylpheed
Version: 3.7.0-8
Tags: upstream

The follwing entries are missing from search messages dialog on the
results context menu:

- Select all
- Delete

Delete is most important, since in this case the keyboard shorcut is
also missing (I'm reporting this as well), and you can't just move out
searched messages in Thrash to nowhere, which makes them impossible to
delete.

Bug#1036415: sylpheed: delete key doesn't work on esarch messages dialog

Package: sylpheed
Version: 3.7.0-8
Tags: upstream
Severity: important

Hi,

Delete key isn't mapped in the list of searched messages, so it just
doesn't work. This is most important in Thrash messages since you can't
use the workaround of moving them to the Thrash folder, and the context
menu entry is missing (recently reported), which makes them impossible
to delete.

Regards,
JL

Bug#1036416: baycomusb: please consider upgrading to 3.0 source format


Source: baycomusb
Version: 0.10-15
Severity: wishlist

Dear maintainer,

This package is among the few that still use source format 1.0 in
bookworm.  Please upgrade it to source format 3.0, as (1) this format has many
advantages, as documented in https://wiki.debian.org/Projects/DebSrc3.0 ; (2)
this contributes to standardization of packaging practices.

Thanks,
Bastian

Bug#1036417: binfmtc: please consider upgrading to 3.0 source format


Source: binfmtc
Version: 0.17-2.2
Severity: wishlist

Dear maintainer,

This package is among the few that still use source format 1.0 in
bookworm.  Please upgrade it to source format 3.0, as (1) this format has many
advantages, as documented in https://wiki.debian.org/Projects/DebSrc3.0 ; (2)
this contributes to standardization of packaging practices.

Thanks,
Bastian

Bug#1036418: bonnie++: please consider upgrading to 3.0 source format


Source: bonnie++
Version: 2.00a+nmu1
Severity: wishlist

Dear maintainer,

This package is among the few that still use source format 1.0 in
bookworm.  Please upgrade it to source format 3.0, as (1) this format has many
advantages, as documented in https://wiki.debian.org/Projects/DebSrc3.0 ; (2)
this contributes to standardization of packaging practices.

Thanks,
Bastian

Bug#1036419: bplay: please consider upgrading to 3.0 source format


Source: bplay
Version: 0.991-10.1
Severity: wishlist

Dear maintainer,

This package is among the few that still use source format 1.0 in
bookworm.  Please upgrade it to source format 3.0, as (1) this format has many
advantages, as documented in https://wiki.debian.org/Projects/DebSrc3.0 ; (2)
this contributes to standardization of packaging practices.

Thanks,
Bastian

Bug#1036415: sylpheed: all keymappings missing except Select all in searched messages list

retitle 1036415 sylpheed: all keymappings missing except Select all in search 
messages list
thanks

Hi again,

It seems all keyboard mappings are missing in this list except Select
all.

Retitling accordingly.

Bug#1036421: brag: please consider upgrading to 3.0 source format


Source: brag
Version: 1.4.1-2.2
Severity: wishlist

Dear maintainer,

This package is among the few that still use source format 1.0 in
bookworm.  Please upgrade it to source format 3.0, as (1) this format has many
advantages, as documented in https://wiki.debian.org/Projects/DebSrc3.0 ; (2)
this contributes to standardization of packaging practices.

Thanks,
Bastian

Bug#1036399: piuparts: false positives for unowned files left after purge

2023-05-20 Thread Patrice Duroux

Hi David,

My two cents as I am just a user, but I would like to say to not worry
too much about those messages.
Looking here: https://piuparts.debian.org/bookworm/, you will see that:

successfully-tested
[...]
- but logfile contains unowned files after purge: 4511 passed
[...]

failed-testing
[...]
- due to unowned files after purge: 1 failed
[...]

If you look at most of the 'successfully-tested' cases and the
'failed-testing' case, you will observe the same INFO messages.
This confirms that it is due to a dependency of the emacs package and
not from the package it-self.

Regards,
Patrice

Bug#563096: sylpheed: Hide update menu item

Hi Ricardo,

>  You can disable checking in configuration, no more spamming.
>  To me removing the option for checking is like self-cheating and
>  trusting the Debian version is always the latest.
>  As a user why should I trust the debian maintainer about that? :)
>  And as the debian maintainer I'd like to be notified by the users if
>  I miss some release [0], so really don't see the point of removing
>  the option.

There's a mailing list of release announcements:

  There is also the sylpheed-announce ML (sylpheed-annou...@sraoss.jp)
  which deals only with release announcements.

I suppose this has been added after the bug got reported. In any case
now you can disable it in configure, since I think makes little sense
in Debian, and close the bug.

Best regards,
José Luis

Bug#1036422: RM: cgilib -- RoQA; low popcon; orphaned


Package: ftp.debian.org
User: ftp.debian@packages.debian.org
Usertags: remove
Severity: normal

Please remove cgilib. The package has no reverse dependencies and a low popcon.
Upstream released a newer version 2009 but there has been no activity since.

Bug#1036313: php-slim-psr7: Useless (and harmful) dependency on (recent) php-symfony-polyfill-php80

2023-05-20 Thread William Desportes

Control: forwarded -1
https://salsa.debian.org/php-team/pear/php-slim-psr7/-/commit/d2e579fa2202265888baf9649cadce7f924fd93b
Control: found -1 php-slim-psr7/1.6.1-1~bpo11+1

Hi David,

This is a complicated subject that I already brought to you, but there is no
easy solution.

First, for the backports version: thank you for reporting this bug !
There is no change impacting the library in the diff:
https://github.com/symfony/polyfill-php80/compare/v1.22.0...v1.26.0
Lowering the version was already done for phpMyAdmin's PPA for Ubuntu jammy.
So I lowered the required version to symfony/polyfill-php80 1.22 available in
Bullseye to fix this bug.

Secondly, the subject that needs to be addressed: Users do what they want and
use php libraries on different versions that Debian was shipped with.
This is something some people want to avoid thinking about, but it's a reality.
- First point: Technically from a packaging stand point, there is no way to
block a library or app's usage with another version than the one shipped by
Debian.
It's only a deb file.
- Second point: if we could do that, the user could still run a library or app
on a different PHP version.

The only way is that the code must protect itself from being run on another
version of PHP.
So if "pkg-php-tools" autoloader tool would add some code in the autoloader to
ensure PHP classes are not run on a different PHP version then yes we can drop the
polyfill libraries.
The code would be protecting itself and we would avoid problems like:
https://bugs.launchpad.net/ubuntu/+source/phpmyadmin/+bug/2016016

The top stack solution we had to do on Ubuntu since one library did screw up
it's packaging was to force phpMyAdmin to require PHP 8.
Since the code did not protect itself, and this all resulted in a crash.
Ref:
https://code.launchpad.net/~athos-ribeiro/ubuntu/+source/phpmyadmin/+git/phpmyadmin/+merge/442711

I am awaiting the proper changes in Debian's packaging tools to be able to move
out of polyfills.

PHP multi version support is complicated. Users do what they want. And as a
maintainer of the tools, I have the angry
users to handle when the proper safeties and polyfills are not in place when
they decide to use another PHP version to run the tool/library packaged.

https://github.com/phpmyadmin/phpmyadmin/issues/17523 and
https://github.com/phpmyadmin/phpmyadmin/issues/17503 reflect that.

I will not be dropping the dependency on the polyfill because upstream is
requiring it, and because users will run the code on other versions.
And you can not even argue with the users, that will not understand. Upstream
says it supports PHP 7.4 so it does:
https://github.com/slimphp/Slim-Psr7/blob/1.6.x/composer.json#L31
And makes the polyfill required.
The users do not even know how things are packaged and will blame you for it
anyway.
Conclusion: I am not considering going blind about what users do with their
Debian and Ubuntu releases. They install tools from other sources. Ref: deb
sury for other PHP versions.

I hope you understand, maybe something can be done to ensure the code protects
itself for example adding a bit of code to abort execution when it's used on
another version that for example:
- The php constraint on composer.json
(https://github.com/slimphp/Slim-Psr7/blob/1.6.x/composer.json#L31)
- Or the Debian shipped version of PHP

Let me know your thoughts.

--
William

Bug#1036423: unblock: uwsgi/2.0.21-5.1

2023-05-20 Thread James Valleroy


Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: uw...@packages.debian.org
Control: affects -1 + src:uwsgi

Please unblock package uwsgi/2.0.21-5.1.

This is an update to fix RC bug #1035005. I did an NMU as suggested by
the package maintainer.

[ Reason ]

Upgrades from Bullseye to Bookworm failed when
uwsgi-plugin-jvm-openjdk-11 is installed. This is solved by adding
versioned Breaks and Replaces to uwsgi-plugin-jvm-openjdk-17 binary
package.

[ Impact ]

uwsgi removed from the release, affecting many packages that depend on
it.

[ Tests ]

I tested by unpacking the package into a Debian bullseye VM where
uwsgi-plugin-jvm-openjdk-11 was already installed.

[ Risks ]

It is a small change and low risk.

[ 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 testing

[ Other info ]

There is a piuparts regression, but it is due to a recent change in
adduser package, and not related at all to the change in uwsgi package.

unblock uwsgi/2.0.21-5.1
diff -Nru uwsgi-2.0.21/debian/changelog uwsgi-2.0.21/debian/changelog
--- uwsgi-2.0.21/debian/changelog   2023-02-24 06:50:43.0 -0500
+++ uwsgi-2.0.21/debian/changelog   2023-05-19 09:59:29.0 -0400
@@ -1,3 +1,10 @@
+uwsgi (2.0.21-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add Replaces on uwsgi-plugin-jvm-openjdk-11 (Closes: #1035005)
+
+ -- James Valleroy   Fri, 19 May 2023 09:59:29 -0400
+
 uwsgi (2.0.21-5) unstable; urgency=medium
 
   * skip shellcheck test when DEB_BUILD_OPTIONS=nocheck;
diff -Nru uwsgi-2.0.21/debian/control uwsgi-2.0.21/debian/control
--- uwsgi-2.0.21/debian/control 2023-02-24 06:49:44.0 -0500
+++ uwsgi-2.0.21/debian/control 2023-05-19 09:59:29.0 -0400
@@ -616,6 +616,8 @@
  uwsgi-core (= ${binary:Version}),
  ${misc:Depends},
  ${shlibs:Depends},
+Replaces: uwsgi-plugin-jvm-openjdk-11 (<< 2.0.21-1)
+Breaks: uwsgi-plugin-jvm-openjdk-11 (<< 2.0.21-1)
 Description: Java plugin for uWSGI (OpenJDK 17)
  uWSGI presents a complete stack for networked/clustered web applications,
  implementing message/object passing, caching, RPC and process management.


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1036424: sylpheed: replying to an email you sent doesn't set account accordingly