Bug#1041508: tex-common: fmutil fails to rebuild formats

[Emmanuel Charpentier]

Package: tex-common
Version: 6.18
Followup-For: Bug #1041508

Dear Maintainer,

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

   * What led up to the situation?

routine upgrade of testing's tex-common

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

apt dist-upgrade -u -f


   * What was the outcome of this action?

Error during tex-common upgrade. excerpt :

=

Paramétrage de tex-common (6.18) ...
Running mktexlsr. This may take some time... done.
Running updmap-sys. This may take some time... done.
Running mktexlsr /var/lib/texmf ... done.
Building format(s) --all.
This may take some time...
fmtutil failed. Output has been stored in
/tmp/fmtutil.uslPitzz
Please include this file if you report a bug.

dpkg: erreur de traitement du paquet tex-common (--configure) :
 le sous-processus paquet tex-common script post-installation installé a
renvoyé
 un état de sortie d'erreur 1
=

then

=
Des erreurs ont été rencontrées pendant l'exécution :
 tex-common
 context-modules
 context
==

The file pointed in the error message shows a problem in HiTeX format build
Excerpt :

==

(hiplainpage.tex
! Missing { inserted.

   p
 p
refer

   e
l.48 prefere
d 0
?
! Emergency stop.

   p
 p
refer

   e
l.48 prefere
d 0
Transcript written on hitex.log.
fmtutil [INFO]: log file copied to: /var/lib/texmf/web2c/hitex/hitex.log



   * What outcome did you expect instead?

Routine upgrade.




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

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

Versions of packages tex-common depends on:
ii  ucf  3.0043+nmu1

tex-common recommends no packages.

Versions of packages tex-common suggests:
ii  debhelper  13.11.6

Versions of packages texlive-base depends on:
ii  debconf [debconf-2.0]  1.5.82
ii  libpaper-utils 1.1.29
ii  sensible-utils 0.0.20
ii  texlive-binaries   2023.20230311.66589-3
ii  ucf3.0043+nmu1
ii  xdg-utils  1.1.3-4.1

Versions of packages texlive-base recommends:
ii  lmodern  2.005-1

Versions of packages texlive-base suggests:
ii  evince [postscript-viewer]   45~alpha-2
ii  ghostscript [postscript-viewer]  10.01.2~dfsg-1
ii  perl-tk  1:804.036-1+b2
pn  xpdf | pdf-viewer
pn  xzdec

Versions of packages texlive-binaries depends on:
ii  libc6   2.37-7
ii  libcairo2   1.16.0-7
ii  libfontconfig1  2.14.2-4
ii  libfreetype62.13.2+dfsg-1
ii  libgcc-s1   13.2.0-2
ii  libgraphite2-3  1.3.14-1
ii  libharfbuzz0b   8.0.1-1
ii  libicu7272.1-3
ii  libkpathsea62023.20230311.66589-3
ii  libmpfr64.2.0-1
ii  libpaper1   1.1.29
ii  libpixman-1-0   0.42.2-1
ii  libpng16-16 1.6.40-1
ii  libpotrace0 1.16-2
ii  libptexenc1 2023.20230311.66589-3
ii  libstdc++6  13.2.0-2
ii  libsynctex2 2023.20230311.66589-3
ii  libteckit0  2.5.11+ds1-1+b1
ii  libtexlua53-5   2023.20230311.66589-3
ii  libtexluajit2   2023.20230311.66589-3
ii  libx11-62:1.8.6-1
ii  libxaw7 2:1.0.14-1
ii  libxi6  2:1.8-1+b1
ii  libxmu6 2:1.1.3-3
ii  libxpm4 1:3.5.12-1.1
ii  libxt6  1:1.2.1-1.1
ii  libzzip-0-130.13.72+dfsg.1-1.1
ii  perl5.36.0-7
ii  t1utils 1.41-4
ii  zlib1g  1:1.2.13.dfsg-3

Versions of packages texlive-binaries recommends:
ii  dvisvgm   3.1-1
ii  texlive-base  2022.20230122-3

-- debconf information:
  texlive-base/binary_chooser: pdftex, dvips, dvipdfmx, xdvi
  texlive-base/texconfig_ignorant:


fmtutil.uslPitzz.gz
Description: application/gzip
This is HiTeX, Version 3.141592653-2.6-2.0 (TeX Live 2023) (INITEX)  2 SEP 2023 
07:23
entering extended mode
entering Prote mode
**hitex.ini 
(hitex.ini (etex.src (plain.tex Preloading the plain format: codes, registers,
\maxdimen=\dimen10
\hideskip=\skip10
\centering=\skip11
\p@=\dimen11
\z@=\dimen12
\z@skip=\skip12
\voidb@x=\box10

parameters,
\smallskipamount=\skip13
\medskipamount=\skip14

Bug#1050937: protobuf: FTBFS: ModuleNotFoundError: No module named 'tzdata'

[Gianfranco Costamagna]

Hello, probably tzdata split in legacy made this package FTBFS.
Solutions are:
1) fix the test to work with main tzdata
2) add dependency on tzdata-legacy package

G.

On Thu, 31 Aug 2023 23:07:59 +0800 Bo YU  wrote:

Source: protobuf
Version: 3.21.12-6
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

protobuf fails to build from source. From my build log on amd64:

```
Traceback (most recent call last):
  File "/usr/lib/python3.11/zoneinfo/_common.py", line 12, in load_tzdata
return resources.files(package_name).joinpath(resource_name).open("rb")
   ^
  File "/usr/lib/python3.11/importlib/resources/_common.py", line 22, in files
return from_package(get_package(package))

  File "/usr/lib/python3.11/importlib/resources/_common.py", line 53, in 
get_package
resolved = resolve(package)
   
  File "/usr/lib/python3.11/importlib/resources/_common.py", line 44, in resolve
return cand if isinstance(cand, types.ModuleType) else 
importlib.import_module(cand)
   
^
  File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
   
  File "", line 1204, in _gcd_import
  File "", line 1176, in _find_and_load
  File "", line 1126, in _find_and_load_unlocked
  File "", line 241, in _call_with_frames_removed
  File "", line 1204, in _gcd_import
  File "", line 1176, in _find_and_load
  File "", line 1140, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'tzdata'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/<>/python3/setup.py", line 324, in 
setup(
  File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 107, in 
setup
return distutils.core.setup(**attrs)
   ^
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
185, in setup
return run_commands(dist)
   ^^
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
201, in run_commands
dist.run_commands()
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
969, in run_commands
self.run_command(cmd)
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in 
run_command
super().run_command(command)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
988, in run_command
cmd_obj.run()
  File "/usr/lib/python3/dist-packages/setuptools/command/test.py", line 223, 
in run
self.run_tests()
  File "/usr/lib/python3/dist-packages/setuptools/command/test.py", line 226, 
in run_tests
test = unittest.main(
   ^^


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1050602: linux: kernel 6.4.11-1 does not recognize TPM on lenovo 14IAU7 (Flex 7i)

[Justin King-Lacroix]

Thanks.

FYI bug is still present in 6.4.13-1

J


On Tue, Aug 29, 2023 at 7:30 AM Diederik de Haas 
wrote:

> Control: forwarded -1 https://bugzilla.kernel.org/show_bug.cgi?id=217804
> https://lore.kernel.org/stable/20230822231510.2263255-1-jar...@kernel.org/
> Control: tag -1 upstream
>
> On Saturday, 26 August 2023 23:26:51 CEST Justin King-Lacroix wrote:
> > Looks like this is an upstream bug that affects all Alder Lake (and maybe
> > newer) systems.
> >
> > https://bugzilla.kernel.org/show_bug.cgi?id=217804
>
> Thanks, I added that and also what appears to be the most current patch
> submission which will hopefully fix that issue.
>
> The issue is also on Thorsten Leemhuis' radar:
>
> https://lore.kernel.org/stable/fcf2f600-d1f0-de14-956b-4d4f3f0cb...@leemhuis.info/

Bug#1050897: OpenRC: Investigation on /lib/rc/tmp

[Timothy Kenno Handojo]

The complete removal of /lib/rc/tmp has been upstreamed!

I guess now we wait til the next version gets released.

Ref: https://github.com/OpenRC/openrc/pull/650

Bug#1042038: mfem: FTBFS: hash.hpp:1001:39: error: ISO C++ forbids declaration of ‘type name’ with no type [-fpermissive]

[Amin Bandali]

Please find attached a patch with an upstream patch to fix this.

Related: https://gcc.gnu.org/gcc-13/porting_to.html#header-dep-changes

>From b07acda4afb3056040bd2b07d209b76bec90a988 Mon Sep 17 00:00:00 2001
From: Amin Bandali 
Date: Fri, 1 Sep 2023 21:11:04 -0400
Subject: [PATCH] Add upstream patch to fix FTBFS with gcc-13 (Closes:
 #1042038)

---
 debian/changelog  |  7 
 debian/patches/fix-ftbfs-gcc-13.patch | 53 +++
 debian/patches/series |  1 +
 3 files changed, 61 insertions(+)
 create mode 100644 debian/patches/fix-ftbfs-gcc-13.patch

diff --git a/debian/changelog b/debian/changelog
index 7d95e4c1e..e30df4c4d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+mfem (4.5.2+ds-2) UNRELEASED; urgency=medium
+
+  * Add upstream patch to fix FTBFS with gcc-13 (Closes: #1042038)
+- debian/patches/fix-ftbfs-gcc-13.patch
+
+ -- Amin Bandali   Fri, 01 Sep 2023 21:10:21 -0400
+
 mfem (4.5.2+ds-1) unstable; urgency=medium
 
   * Initial release. (Closes: #1023223)
diff --git a/debian/patches/fix-ftbfs-gcc-13.patch b/debian/patches/fix-ftbfs-gcc-13.patch
new file mode 100644
index 0..5d202ab25
--- /dev/null
+++ b/debian/patches/fix-ftbfs-gcc-13.patch
@@ -0,0 +1,53 @@
+From 314a32af2ee80af8c9af7d8ad71babd51851154c Mon Sep 17 00:00:00 2001
+From: David Dement 
+Origin: https://github.com/mfem/mfem/commit/314a32af2ee80af8c9af7d8ad71babd51851154c
+Date: Thu, 27 Apr 2023 10:33:51 -0400
+Subject: [PATCH] Fixes comilation errors when compiling with gcc-13 on Fedora
+ 38
+
+When compiling with gcc-13, types such as uint64_t are not defined.
+It is likely that  is included implicitly with older compiler
+versions.
+---
+ general/hash.hpp| 1 +
+ general/mem_manager.cpp | 1 +
+ mesh/vtk.hpp| 2 ++
+ 3 files changed, 4 insertions(+)
+
+diff --git a/general/hash.hpp b/general/hash.hpp
+index 86d987d8029..288d51288df 100644
+--- a/general/hash.hpp
 b/general/hash.hpp
+@@ -16,6 +16,7 @@
+ #include "array.hpp"
+ #include "globals.hpp"
+ #include 
++#include 
+ 
+ namespace mfem
+ {
+diff --git a/general/mem_manager.cpp b/general/mem_manager.cpp
+index 416a6ac6203..37b80c878ad 100644
+--- a/general/mem_manager.cpp
 b/general/mem_manager.cpp
+@@ -16,6 +16,7 @@
+ #include  // std::memcpy, std::memcmp
+ #include 
+ #include  // std::max
++#include 
+ 
+ // Uncomment to try _WIN32 platform
+ //#define _WIN32
+diff --git a/mesh/vtk.hpp b/mesh/vtk.hpp
+index a59bed27592..50eeea5bc78 100644
+--- a/mesh/vtk.hpp
 b/mesh/vtk.hpp
+@@ -12,6 +12,8 @@
+ #ifndef MFEM_VTK
+ #define MFEM_VTK
+ 
++#include 
++
+ #include "../fem/geom.hpp"
+ #include "../general/binaryio.hpp"
+ 
diff --git a/debian/patches/series b/debian/patches/series
index 6f0d8f01a..d42e867b3 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1,3 @@
 static-no-shared-yes
 not-makefile
+fix-ftbfs-gcc-13.patch
-- 
2.39.2

Bug#1041249: cpp-httplib: FTBFS on s390x: ../test/test.cc:5462: Failure

[Jeremy Bícha]

Sebastian,

cpp-httplib has built on all release architectures now. This bug is
now blocking migration to Testing.

Thank you,
Jeremy Bícha

Bug#1001713: lxc-copy --ephemeral fail: Failed to create monitor cgroup 12

[Mathias Gibbens]

Control: forwarded -1 https://github.com/lxc/lxc/issues/4199
Control: tags -1 + confirmed

  This is the same issue as #1039737, although starting with the
foreground option (-F) produces a different error. I'll merge the two
bugs momentarily.

Mathias


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

Bug#1050571: [Pkg-nginx-maintainers] Bug#1050571: reportbug: nginx normalises "Status: 123 " and "Status: 123" to invalid "HTTP/1.1 123" (must be "HTTP/1.1 123 ")

[наб]

Control: tags -1 + upstream fixed-upstream

The thread bore fruit, fixed upstream in
  https://hg.nginx.org/nginx/rev/35bb47f65cab


signature.asc
Description: PGP signature

Bug#1050256: autopkgtest fails on debci

[Mathias Gibbens]

Control: block 1038315 by -1
Control: block 1042880 by -1

  I don't think we have a good understanding of the root cause of this
issue. Initially we thought this was a known upstream issue with all-
but very recent versions of apparmor and a corresponding lxc profile
fix [0]. However, it appears this is a different issue that somehow
depends on the interaction of bookworm's versions of the kernel,
apparmor, and/or lxc.

  A minimal reproducer is to install bookworm and create a container
with a systemd service using a hardening option like
PrivateNetwork=yes. With the latest bookworm kernel (6.1.38-4), the
service will fail. But, grab a kernel from testing (6.4.11-1) and then
things work -- with no other changes required. I tried the "oldest"
kernel on snapshot.d.o post 6.1 series (6.3.1+1~exp1 [1]) and the
service works properly with that version as well. So, something changed
in the kernel (either upstream or in Debian's packaging) between 6.1
and 6.3 that "unbreaks" services within lxc containers.

  Given that simply installing a newer kernel fixes things, I am
hesitant to start making changes to lxc until we actually understand
what's changed when running the newer kernel and how it's affecting
lxc's behavior.

On Thu, 2023-08-31 at 19:54 +0200, Christian Boltz wrote:
> That said - the DENIED log entry translates to
> 
> unix send type=dgram,
> 
> You could try if adding this rule to the lxc-autopkgtest-lxc-iomhit_*
> profile helps - but if the issue is really on the kernel side, my
> hope is limited).

  I have tried tweaking the apparmor profile that's generated for
containers (the relevant part is defined in the variable
AA_PROFILE_UNIX_SOCKETS in src/lxc/lsm/apparmor.c), but haven't had any
success in a workaround. I am not super familiar with apparmor, so
maybe I'm not specifying things right, but I've previously tried the
sort of rules Christian suggested, none of which have had any affect.

On Fri, 2023-09-01 at 13:23 +0200, Michael Biebl wrote:
> The only way to fix the container was to use the aforementioned 
> `lxc.apparmor.profile = unconfined`.
> I think we should do that as the breakage is rather widespread and I 
> already see individual packages trying to work around that to at
> least keep debci afloat.

  I strongly dislike the idea of blanketly disabling apparmor profiles
by default for all lxc installs, since apparmor is one of the ways of
helping to ensure isolation of containers. For the specific instance of
debci, /etc/lxc/default.conf can be modified post-lxc install to change
lxc.apparmor.profile from "generated" to "unconfined" for the time
being.

Mathias

---

[0] -- https://github.com/lxc/lxc/issues/4333
[1] -- https://snapshot.debian.org/package/linux-signed-amd64/6.3.1%2B1~exp1/


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

Bug#1042463: lintian does not accept overrides in the syntax used on ftp-master

[Axel Beckert]

Control: tag -1 + moreinfo

Hi Julian,

Julian Andres Klode wrote:
> lintian in the archive needs to restore support for the old override
> format, or ftpmaster needs to be updated to the new lintian.

We had a lengthy discussion about the override format changes made by
Felix (see https://bugs.debian.org/1007002) and there's no way back
(including "backwards compatibility") unless someone volunteers to
implement a fix for this. (I won't do that as mentioned in this
thread. See also below for some reasoning.)

> Normal source-only uploads do not trigger the issue usually, but
> there surely have been people adopting their overrides to the new
> format who now get stuck (like me) at binary-NEW with a reject when
> having to do a binary upload.

Please give an explicit example. I'm not sure if you and me think of
the same "new" and "old" format. → Tagged as "moreinfo".

As mentioned in #1007002 there's a script in the migrate-overrides
branch of https://salsa.debian.org/lintian/lintian/ which can
automatically migrate tags in override files.

But so far it only knows a few of the very annoying tags — which is also
the reason it's not in the package yet.

But I'm willing to extend that script and maybe even implement a mode
for ftp-masters if I get an example of a file which needs to be
migrated (including file name and maybe default path).

But for that I need old real-life examples. (Maybe ftp-masters can
give me the file/list Julian mentioned or tell me where to find it?)

> For an orderly transition, lintian needs to […]

Please tell this the previous lintian lead developer who decided and
implemented this inmidst of tons of other invasive changes (like
rewriting Lintian's internal module structure) without doing a release
for months or doing a release after one of these invasive changes.

It's anything but a simple "git revert" to get the old format back.
And a compatibility mode would require implementing the old override
format in the new framework from scratch.

Short said: IMHO we should do a forward escape instead of trying to
implement a very work-intensive backwards compatibility. For which we
don't seem to have the resources anyway unless someone volunteers.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#1040931: neochat: Encryption is not working with neochat

[z411]

On Wed, 12 Jul 2023 16:17:43 +0200 Enrique  wrote> Dear 
Maintainer,


It seems that neochat is not working with E2EE encrypted chats. There is a
message at the typing prompt which reads:

"This room is encrypted. Build libQuotient with encryption enabled to send
encrypted messages".

It would be great of neochat adds support for that.

Thank you!



libQuotient 0.7, which includes E2EE support is now in experimental. 
After it migrates to Sid I assume this package would start being built 
against libQuotient 0.7, thus prividing E2EE support.

Bug#1051067: knot: statistics output broken since 3.3.0?

[наб]

Control: forwarded -1 https://gitlab.nic.cz/knot/knot-dns/-/issues/874

Forwarded upstream, for now that SHA can be reversed in Debian with no
conflicts (cf. attached).
patch -p1 -R < 2decb9ea3da74d13f54316d86ad9e7f727254164.patch

--- knot-3.3.0.orig/src/knot/common/stats.c
+++ knot-3.3.0/src/knot/common/stats.c
@@ -36,20 +36,15 @@ typedef struct {
FILE *fd;
const list_t *query_modules;
const knot_dname_t *zone;
-   unsigned threads;
-   int level;
bool zone_emitted;
-   bool zone_name_emitted;
-   bool module_emitted;
 } dump_ctx_t;
 
 #define DUMP_STR(fd, level, name, ...) do { \
-   fprintf(fd, "%-.*s"name":\n", level, "", ##__VA_ARGS__); \
-} while (0)
-
-#define DUMP_CTR(fd, level, name, idx, val) do { \
-   fprintf(fd, "%-.*s"name": %"PRIu64"\n", level, "", idx, val); \
-} while (0)
+   fprintf(fd, "%-.*s"name": %s\n", level, "", ##__VA_ARGS__); \
+   } while (0)
+#define DUMP_CTR(fd, level, name, ...) do { \
+   fprintf(fd, "%-.*s"name": %"PRIu64"\n", level, "", ##__VA_ARGS__); \
+   } while (0)
 
 static uint64_t server_zone_count(server_t *server)
 {
@@ -86,78 +81,31 @@ uint64_t stats_get_counter(uint64_t **st
return res;
 }
 
-static void dump_common(dump_ctx_t *ctx, knotd_mod_t *mod)
-{
-   // Dump zone name.
-   if (ctx->zone != NULL) {
-   // Prevent from zone section override.
-   if (!ctx->zone_emitted) {
-   ctx->level = 0;
-   DUMP_STR(ctx->fd, ctx->level++, "zone");
-   ctx->zone_emitted = true;
-   }
-
-   if (!ctx->zone_name_emitted) {
-   ctx->level = 1;
-   knot_dname_txt_storage_t name;
-   if (knot_dname_to_str(name, ctx->zone, sizeof(name)) == 
NULL) {
-   return;
-   }
-   DUMP_STR(ctx->fd, ctx->level++, "\"%s\"", name);
-   ctx->zone_name_emitted = true;
-   }
-   }
-
-   if (!ctx->module_emitted) {
-   DUMP_STR(ctx->fd, ctx->level++, "%s", mod->id->name + 1);
-   ctx->module_emitted = true;
-   }
-}
-
-static void dump_counter(dump_ctx_t *ctx, knotd_mod_t *mod, mod_ctr_t *ctr)
-{
-   uint64_t counter = stats_get_counter(mod->stats_vals, ctr->offset, 
ctx->threads);
-   if (counter == 0) {
-   // Skip empty counter.
-   return;
-   }
-
-   dump_common(ctx, mod);
-
-   DUMP_CTR(ctx->fd, ctx->level, "%s", ctr->name, counter);
-}
-
-static void dump_counters(dump_ctx_t *ctx, knotd_mod_t *mod, mod_ctr_t *ctr)
+static void dump_counters(FILE *fd, int level, mod_ctr_t *ctr, uint64_t 
**stats_vals, unsigned threads)
 {
-   bool counter_emitted = false;
for (uint32_t j = 0; j < ctr->count; j++) {
-   uint64_t counter = stats_get_counter(mod->stats_vals, 
ctr->offset + j, ctx->threads);
+   uint64_t counter = stats_get_counter(stats_vals, ctr->offset + 
j, threads);
+
+   // Skip empty counters.
if (counter == 0) {
-   // Skip empty counter.
continue;
}
 
-   dump_common(ctx, mod);
-
-   if (!counter_emitted) {
-   DUMP_STR(ctx->fd, ctx->level, "%s", ctr->name);
-   counter_emitted = true;
-   }
-
if (ctr->idx_to_str != NULL) {
char *str = ctr->idx_to_str(j, ctr->count);
if (str != NULL) {
-   DUMP_CTR(ctx->fd, ctx->level + 1, "%s", str, 
counter);
+   DUMP_CTR(fd, level, "%s", str, counter);
free(str);
}
} else {
-   DUMP_CTR(ctx->fd, ctx->level + 1, "%u", j, counter);
+   DUMP_CTR(fd, level, "%u", j, counter);
}
}
 }
 
 static void dump_modules(dump_ctx_t *ctx)
 {
+   int level = 0;
knotd_mod_t *mod;
WALK_LIST(mod, *ctx->query_modules) {
// Skip modules without statistics.
@@ -165,12 +113,28 @@ static void dump_modules(dump_ctx_t *ctx
continue;
}
 
-   if (ctx->threads == 0) {
-   ctx->threads = knotd_mod_threads(mod);
+   // Dump zone name.
+   if (ctx->zone != NULL) {
+   // Prevent from zone section override.
+   if (!ctx->zone_emitted) {
+   DUMP_STR(ctx->fd, 0, "zone", "");
+   ctx->zone_emitted = true;
+   }
+   level = 1;
+
+   knot_dname_txt_storage_t name;
+   if 

Bug#1050807: r-bioc-biocstyle: autopkgtest fails since TL 2023

[Preuße]

On 29.08.2023 14:06, Hilmar Preusse wrote:

Hello,


I just noticed, that the autopkgtest of your package fail, since I uploaded
TL 2023 to unstable [1].


Attached is a debdiff implementing the suggestion. I run the autopkgtest as:

autopkgtest r-bioc-biocstyle_2.28.0+dfsg-1.1.dsc -- schroot 
unstable-amd64-sbuild


For any reason no test is found, so no test can fail.

Hilmar
--
sigfault

diff -Nru r-bioc-biocstyle-2.28.0+dfsg/debian/changelog 
r-bioc-biocstyle-2.28.0+dfsg/debian/changelog
--- r-bioc-biocstyle-2.28.0+dfsg/debian/changelog   2023-07-18 
12:51:59.0 +0200
+++ r-bioc-biocstyle-2.28.0+dfsg/debian/changelog   2023-09-01 
23:39:35.0 +0200
@@ -1,3 +1,9 @@
+r-bioc-biocstyle (2.28.0+dfsg-1.1) UNRELEASED; urgency=medium
+
+  * Patch Bioconductor.sty to fix autopkgtest.
+
+ -- Hilmar Preusse   Fri, 01 Sep 2023 23:39:35 +0200
+
 r-bioc-biocstyle (2.28.0+dfsg-1) unstable; urgency=medium
 
   * Disable reprotest
diff -Nru r-bioc-biocstyle-2.28.0+dfsg/debian/patches/fix_sty_file 
r-bioc-biocstyle-2.28.0+dfsg/debian/patches/fix_sty_file
--- r-bioc-biocstyle-2.28.0+dfsg/debian/patches/fix_sty_file1970-01-01 
01:00:00.0 +0100
+++ r-bioc-biocstyle-2.28.0+dfsg/debian/patches/fix_sty_file2023-09-01 
23:39:14.0 +0200
@@ -0,0 +1,11 @@
+--- r-bioc-biocstyle-2.28.0+dfsg.orig/inst/resources/tex/Bioconductor.sty
 r-bioc-biocstyle-2.28.0+dfsg/inst/resources/tex/Bioconductor.sty
+@@ -526,7 +526,7 @@
+ }
+ \patchcmd\SOUL@start{\SOUL@preamble}{\@inside@soultrue\SOUL@preamble}
+   {}{\errmessage{Cannot patch \protect\SOUL@start}}
+-\renewcommand{\@raggedtwoe@everyselectfont}{%
++\newcommand{\@raggedtwoe@everyselectfont}{%
+   \if@raggedtwoe@spaceskip
+ \ifdim\fontdimen\thr@@\font=\z@\relax
+   \if@inside@soul
diff -Nru r-bioc-biocstyle-2.28.0+dfsg/debian/patches/series 
r-bioc-biocstyle-2.28.0+dfsg/debian/patches/series
--- r-bioc-biocstyle-2.28.0+dfsg/debian/patches/series  1970-01-01 
01:00:00.0 +0100
+++ r-bioc-biocstyle-2.28.0+dfsg/debian/patches/series  2023-09-01 
23:37:15.0 +0200
@@ -0,0 +1 @@
+fix_sty_file


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1051067: knot: statistics output broken since 3.3.0?

[наб]

Control: tags -1 + upstream

On Sat, Sep 02, 2023 at 12:09:38AM +0200, наб wrote:
> which looks one hell of a lot like "we forgot to also close the scope
> for mod-cookies in this case" to me?
Yes, can confirm this. I apt sourced knot,
  curl 
https://gitlab.nic.cz/knot/knot-dns/-/commit/2decb9ea3da74d13f54316d86ad9e7f727254164.patch
 | patch -Rp1
rebuilt, and the new version has correct stats:
-- >8 --
---
time: 2023-09-02T00:34:56+0200
identity: szarotka.nabijaczleweli.xyz
server:
 zone-count: 25
mod-cookies:
 presence: 2
 dropped: 0
mod-rrl:
 slipped: 0
 dropped: 0
mod-stats:
 request-protocol:
  udp4: 4
 server-operation:
  query: 4
 request-bytes:
  query: 224
 response-bytes:
  reply: 395
 response-code:
  NOERROR: 3
  BADCOOKIE: 1
2023-09-02T00:34:56+0200 debug: stats, dumped into file 
'/run/knot-log-tail/debug.fifo'
-- >8 --


signature.asc
Description: PGP signature

Bug#1051066: netatalk: 9 outstanding CVEs in Bullseye with available patches

[Daniel Markstedt]

To add the justification for the critical severity of this ticket:
At least 6 of the 9 vulnerabilities grant theoretical root access of a Debian 
system running non-patched netatalk.

CVE-2022-43634, CVE-2022-23124, CVE-2022-23123, CVE-2022-23122, CVE-2022-23121, 
CVE-2022-0194

Bug#1051067: knot: statistics output broken since 3.3.0?

[наб]

In the upstream changelog I see
-- >8 --
Knot DNS 3.3.0 (2023-08-28)
===

Improvements:
-
 - knotd: stats no longer dump empty or zero counters
-- >8 --
which looks one hell of a lot like "we forgot to also close the scope
for mod-cookies in this case" to me?


signature.asc
Description: PGP signature

Bug#734401: postfix: debconf settings don't reflect main.cf if altered manually (e.g. relay_host)

[joeDoe]

It was suggested on the #freedombox IRC channel that my recent experience
with postfix on fbx might be related to this bug. I'll briefly relate
experience here, therefore, in case it might be useful. I hope it isn't
noise.

I had a working postfix setup on fbx 23.6.2 setup.  Because the Debian 11 ->
12 transition had frozen uploads, and because the change in the way apt
handles the labels stable and  changed in
bookworm and required making a config change to apt, I didn't get an upgrade
of my fbx package until 28 July 2023 at 01:38 UTC, which was from 23.6.2 to
23.13~bpo12+1.

Shortly after that I discovered that mail destined for users of my fbx was
being rejected by postfix with 

"Diagnostic-Code: smtp; 454 4.7.1 mailto:joe...@mydomain.com>>: Relay access denied"

It turns out that postfix's main.cf file had been overwritten on 28 July
2023 at UTC 01:41 with no real configuration in it.  At least, there was no
mention of mydomain.com in the file anymore, nor to any fqdn, for that
matter.  On IRC I learned that the postinst script in the postfix package is
run at each upgrade.  The suggestion was that possibly the postfix postinst
script was responsible for overwriting my working main.cf

The behaviour I would like to see is as with other Debian packages that are
about to overwrite an existing config file:

* A dialogue appears explaining the situation where you can choose to let
  the package overwrite the file, saving the original with a .dpkg-old
  suffix, to keep the original file, while writing the pkg maintainers
  version to .dpkg-new, or to examine the differences between the two
  files before deciding.

Fortunately I had a backup of the working main.cf, so recovery was much
simpler than figuring out why my setup had quit working.

If any interested parties would like more information about my experience,
ask,  and I will do my best to find that info for you.

--
joeDoe

Bug#1007596: NMU libdbd-sybase-perl 1.14-1.1

[Steve Langasek]

On Tue, Aug 22, 2023 at 09:04:33PM +0200, Bastian Germann wrote:
> I am uploading a NMU to DELAYED/10 in order to fix this.
> The debdiff is attached.

Thanks for this upload, Bastian!  I hadn't replied, but I did have a look at
the debdiff and it looked fine to me.  This is long overdue, so thank you
again for taking care of it.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#1051066: netatalk: 9 outstanding CVEs in Bullseye with available patches

[Daniel Markstedt]

Package: netatalk
Version: 3.1.12~ds-8
Severity: critical
Tags: patch security
Justification: root security hole
X-Debbugs-Cc: pkg-netatalk-de...@alioth-lists.debian.net, Debian Security Team 


Nine CVE security advisories were addressed in netatalk upstream
releases between 3.1.13 and 3.1.15. The full list is below:

CVE-2022-45188
CVE-2022-43634
CVE-2022-23125
CVE-2022-23124
CVE-2022-23123
CVE-2022-23122
CVE-2022-23121
CVE-2022-0194
CVE-2021-31439

Current status of patching these vulnerabilities:
- netatalk oldoldstable has already been patched by the Security Team.
- netatalk unstable has already been patched by the maintainer team.
- The netatalk package was excluded from stable, no action required.
- What remains is to patch oldstable, hence this ticket.

A debpatch has been attached to the related Release bug ticket,
where approval to proceed with an oldstable release has been requested.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049325

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

Kernel: Linux 6.1.0-11-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to C.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages netatalk depends on:
ii  init-system-helpers  1.60
ii  libacl1  2.2.53-10
ii  libavahi-client3 0.8-5+deb11u2
ii  libavahi-common3 0.8-5+deb11u2
ii  libc62.31-13+deb11u6
ii  libcrack22.9.6-3.4
ii  libcrypt11:4.4.18-4
ii  libdb5.3 5.3.28+dfsg1-0.8
ii  libdbus-glib-1-2 0.110-6
ii  libevent-2.1-7   2.1.12-stable-1
ii  libgcrypt20  1.8.7-6
ii  libglib2.0-0 2.66.8-1
ii  libgssapi-krb5-2 1.18.3-6+deb11u3
ii  libkrb5-31.18.3-6+deb11u3
ii  libldap-2.4-22.4.57+dfsg-3+deb11u1
ii  libmariadb3  1:10.5.19-0+deb11u2
ii  libpam-modules   1.4.0-9+deb11u1
ii  libpam0g 1.4.0-9+deb11u1
ii  libssl1.11.1.1n-0+deb11u4
ii  libtalloc2   2.3.1-2+b1
ii  libtdb1  1.4.3-1+b1
ii  libtracker-sparql-2.0-0  2.3.6-2
ii  libwrap0 7.6.q-31
ii  lsb-base 11.1.0
ii  netbase  6.3
ii  perl 5.32.1-4+deb11u2

Versions of packages netatalk recommends:
ii  avahi-daemon  0.8-5+deb11u2
ii  cracklib-runtime  2.9.6-3.4
ii  dbus  1.12.24-0+deb11u1
ii  lsof  4.93.2+dfsg-1.1
ii  procps2:3.3.17-5
ii  python3   3.9.2-3
ii  python3-dbus  1.2.16-5
ii  tracker   2.3.6-2

Versions of packages netatalk suggests:
pn  quota  

-- no debconf information

Bug#1051067: knot: statistics output broken since 3.3.0?

[наб]

Package: knot
Version: 3.3.0-2
Severity: normal

Dear Maintainer,

I have
-- >8 --
statistics:
  timer: 1h
  file: /run/knot-log-tail/debug.fifo
  append: true
-- >8 --
set, and appear to be losing metrics on my dashboard since the 3.3.0 upgrade:
-- >8 --
$ grep knot: /var/log/dpkg.log
2023-09-01 00:03:28 upgrade knot:x32 3.2.9-1 3.3.0-2
2023-09-01 00:03:28 status half-configured knot:x32 3.2.9-1
2023-09-01 00:03:28 status unpacked knot:x32 3.2.9-1
2023-09-01 00:03:28 status half-installed knot:x32 3.2.9-1
2023-09-01 00:03:28 status unpacked knot:x32 3.3.0-2
2023-09-01 00:03:40 configure knot:x32 3.3.0-2 
2023-09-01 00:03:40 status unpacked knot:x32 3.3.0-2
2023-09-01 00:03:40 status half-configured knot:x32 3.3.0-2
2023-09-01 00:03:44 status installed knot:x32 3.3.0-2
-- >8 --

Listening in, debug.fifo appears to now have
-- >8 --
---
time: 2023-09-01T23:03:44+0200
identity: szarotka.nabijaczleweli.xyz
server:
 zone-count: 25
mod-cookies:
 presence: 780
 mod-stats:
  request-protocol:
   udp4: 3776
   tcp4: 142
  server-operation:
   query: 3838
   axfr: 4
   ixfr: 76
  request-bytes:
   query: 208595
   other: 11080
  response-bytes:
   reply: 514727
   transfer: 13348
  response-code:
   NOERROR: 2755
   FORMERR: 1
   NXDOMAIN: 831
   REFUSED: 20
   NOTAUTH: 1
   BADCOOKIE: 310
-- >8 --

Notably: what on earth happened with the cookies?
mod-stats is clearly not /supposed/ to be a child of mod-cookies?
And where's the cookies' dropped statistic?
Where's mod-rrl?

For reference, a correct dump looks (looked) like
-- >8 --
---
time: 2023-08-29T00:19:44+0200
identity: szarotka.nabijaczleweli.xyz
server:
 zone-count: 24
mod-cookies:
 presence: 24
 dropped: 0
mod-rrl:
 slipped: 0
 dropped: 0
mod-stats:
 request-protocol:
  udp4: 24
 server-operation:
  query: 24
 request-bytes:
  query: 1632
 response-bytes:
  reply: 2292
 response-code:
  NOERROR: 12
  BADCOOKIE: 12
-- >8 --

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

Kernel: Linux 6.3.0-2-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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 knot depends on:
ii  adduser  3.137
ii  init-system-helpers  1.65.2
ii  libc62.37-6
ii  libcap-ng0   0.8.3-1+b3
ii  libdnssec9   3.3.0-2
ii  libedit2 3.1-20221030-2
ii  libgnutls30  3.8.1-4
ii  libknot143.3.0-2
ii  liblmdb0 0.9.31-1
ii  libsystemd0  254.1-3
ii  liburcu8 0.14.0-1
ii  libzscanner4 3.3.0-2

knot recommends no packages.

Versions of packages knot suggests:
ii  systemd  254.1-3

-- Configuration Files:
/etc/knot/knot.conf [Errno 13] Permission denied: '/etc/knot/knot.conf'

-- no debconf information


signature.asc
Description: PGP signature

Bug#1007543: daptup: please consider upgrading to 3.0 source format

[Bastian Germann]

On Tue, 15 Mar 2022 08:51:59 +0100 Lucas Nussbaum  wrote:

This package is a native package, so the likely target is 3.0 (native), not
3.0 (quilt).


There is no reason that the package should be native.
Please convert it to be non-native.

Bug#1051065: weex: d/copyright: Incorrect upstream source

[Bastian Germann]

Source: weex
Severity: serious
Version: 2.8.4.2

debian/copyright claims the upstream source is at http://weex.sourceforge.net.
I cannot find version 2.8.4, 2.8.4.1, or 2.8.4.2 at that website.
Please fix the copyright file. If there are no such versions, please fix your
source format to be non-native and have a Debian revision.

Bug#1051064: fonts-b612: The package is either missing or has mislabled the regular font style.

[Brad Sims]

Package: fonts-b612
Version: 1.008-3
Severity: important
X-Debbugs-Cc: brad.m.s...@gmail.com

Dear Maintainer,

After installing the package, the regular font style is italizised.
There is no regular font style available.

If I install the fonts manually from upstream it functions correctly.



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

Kernel: Linux 6.1.0-11-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: 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

-- no debconf information

Bug#1051063: vim-scripts: no license assumption must be non-free

[Bastian Germann]

Source: vim-scripts
Severity: serious
Version: 20210124.2

In vim-script's copyright file, the following assumption is written:

"Summary of license information of each script is reported below. For scripts
which license is "no license" it is assumed in good faith that having being
posted on vim.org their licence is at least as free as the licence of Vim
itself."

This assumption is wrong. International copyright agreements unfortunately make
those files non-DFSG-free.

Please move them affected files to a new source package with Section: 
non-free/editors.

Bug#1051062: shadow: CVE-2023-4641: gpasswd(1) password leak

[Salvatore Bonaccorso]

Source: shadow
Version: 1:4.13+dfsg1-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 1:4.8.1-1 

Hi,

The following vulnerability was published for shadow.

CVE-2023-4641[0]:
| gpasswd(1) password leak


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-4641
https://www.cve.org/CVERecord?id=CVE-2023-4641
[1] https://bugzilla.redhat.com/show_bug.cgi?id=2215945
[2] 
https://github.com/shadow-maint/shadow/commit/65c88a43a23c2391dcc90c0abda3e839e9c57904

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1051061: xrdp: CVE-2023-40184

[Salvatore Bonaccorso]

Source: xrdp
Version: 0.9.21.1-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for xrdp.

CVE-2023-40184[0]:
| xrdp is an open source remote desktop protocol (RDP) server. In
| versions prior to 0.9.23 improper handling of session establishment
| errors allows bypassing OS-level session restrictions. The
| `auth_start_session` function can return non-zero (1) value on,
| e.g., PAM error which may result in in session restrictions such as
| max concurrent sessions per user by PAM (ex
| ./etc/security/limits.conf) to be bypassed. Users (administrators)
| don't use restrictions by PAM are not affected. This issue has been
| addressed in release version 0.9.23. Users are advised to upgrade.
| There are no known workarounds for this issue.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-40184
https://www.cve.org/CVERecord?id=CVE-2023-40184
[1] https://github.com/neutrinolabs/xrdp/security/advisories/GHSA-f489-557v-47jq
[2] 
https://github.com/neutrinolabs/xrdp/commit/25a1fab5b6c5ef2a8bb109232b765cb8b332ce5e

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1051060: vde2: New upstream version available

[Bastian Germann]

Source: vde2
Severity: important
Version: 2.3.2+r586-8

The development has moved to GitHub and a new version 2.3.3 is available.
Please package the latest version.

Bug#1051059: vde2: d/copyright: Upstream source not mentioned

[Bastian Germann]

Source: vde2
Severity: serious
Version: 2.3.2+r586-8

Please add the upstream source to debian/copyright, as required by Policy §12.5.

Bug#1050729: gnome-terminal: shift-click in vim acts like page-down

[Jeremy Bícha]

Control: reassign -1 src:vte2.91 0.73.93-1
Control: severity -1 important

I was able to duplicate the gnome-terminal part of this bug on Debian
Testing with vte 0.73.93 but not with vte 0.72.2. The version of
gnome-terminal didn't matter.

Could you report this issue to the upstream developers?
https://gitlab.gnome.org/GNOME/vte/-/issues

The bug didn't occur for me on my Ubuntu 23.10 install though…

Thank you,
Jeremy Bícha

Bug#1051058: rails: CVE-2023-28362

[Salvatore Bonaccorso]

Source: rails
Version: 2:6.1.7.3+dfsg-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for rails.

CVE-2023-28362[0]:
| Possible XSS via User Supplied Values to redirect_to


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-28362
https://www.cve.org/CVERecord?id=CVE-2023-28362
[1] 
https://discuss.rubyonrails.org/t/cve-2023-28362-possible-xss-via-user-supplied-values-to-redirect-to/83132
[2] 
https://github.com/rails/rails/commit/1c3f93d1e90a3475f9ae2377ead25ccf11f71441

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1051057: rails: CVE-2023-38037

[Salvatore Bonaccorso]

Source: rails
Version: 2:6.1.7.3+dfsg-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for rails.

CVE-2023-38037[0]:
Active Support Possibly Discloses Locally Encrypted Files


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-38037
https://www.cve.org/CVERecord?id=CVE-2023-38037
[1] https://github.com/advisories/GHSA-cr5q-6q9f-rq6q
[2] 
https://github.com/rails/rails/commit/c85cc667ebfd3c270df37c7575d580ea6462e12f

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1051055: focalinux: non-free GFDL variant

[Bastian Germann]

Source: focalinux
Version: 2010-09-3.1
Severity: serious

Your package is licensed under the GFDL-1.1, not the GFDL-NIV-1.1 variant
(with no Front-Cover or Back-Cover Texts or Invariant Sections).
Please see https://www.debian.org/vote/2006/vote_001 on why this is a
non-free license. Please consider asking upstream for a change.

Bug#1049982: bullseye-pu: package riemann-c-client/1.10.4-2+b2

[Romain Tartière]

Control: retitle -1 bullseye-pu: package riemann-c-client/1.10.4-2+deb11u1
Control: tag -1 - moreinfo



signature.asc
Description: PGP signature

Bug#934736: initramfs-tools: MODULES=dep fails when rootfs is zfs

[Dustin Howett]

This is unfortunately still an issue with initramfs-tools 0.142 on
debian sid as of 2023-09-01.

Is there a process that the community can follow to propose Aron Xu's
patch (which works for v0.142 as well) for inclusion in mainline?

Thanks,
d

Bug#915370: Please drop anacron from task-desktop and task-laptop

[Alexandre Detiste]

>From: Gregor Riepl 
>To: Debian Bug Tracking System <915...@bugs.debian.org>
>Subject: Re: Please drop anacron from task-desktop and task-laptop
>Date: Thu, 19 Jan 2023 17:19:21 +0100
>
>On the other hand, the systemd-cron package provides anacron, so it could be
>installed instead, if the cron dependency should be kept.

Debootstrap would only take into account the first alternative I think,
even if systemd-cron Provides a virtual anacron.

Thanks to наб, systemd-cron has seen a lot of improvement recently
and been rewritten in C++, got an extensive test suite
and also extensive heuristic tables to avoid running useless
legacy crontabs that does nothing under systemd:
   https://wiki.debian.org/systemd-cron
(checkout v2.0+ in testing)

So can we just replace "anacron"
by "systemd-cron" and be done with this old bug ?

On a typical system, the only legacy crontab remaining
to translate is popularity-contest and the rest
is shadowed by native .timer/.service pairs.

Greetings,

Bug#1050660: fontconfig-config: dangling symlink /etc/fonts/conf.d/10-no-sub-pixel.conf

[Gunnar Hjalmarsson]

Jörg-Volker Peetz wrote:

the removal of /usr/share/fontconfig/conf.avail/10-no-sub-pixel.conf
left a dangling symlink:

/etc/fonts/conf.d/10-no-sub-pixel.conf


Thanks for your report! This commit:

https://gitlab.freedesktop.org/fontconfig/fontconfig/-/commit/030759b7

includes a filename change from 10-no-sub-pixel.conf to 
10-sub-pixel-none.conf. These files:


debian/fontconfig-config.config
debian/fontconfig-config.postinst
debian/fontconfig-config.postrm

include the old name, so there is indeed a need to adapt to the name 
change. And I suspect that your observation is a result of my omission 
to adjust it when upgrading to fontconfig 2.14.2.


I have submitted this merge request:

https://salsa.debian.org/freedesktop-team/fontconfig/-/merge_requests/12

While it doesn't remove the obsolete symlink, it ought to create the 
correct symlink going forward.


--
Rgds,
Gunnar Hjalmarsson

Bug#1049988: bookworm-pu: package riemann-c-client/1.10.4-2

[Romain Tartière]

Control: retitle -1 bookworm-pu: package riemann-c-client/1.10.4-2+deb12u1


signature.asc
Description: PGP signature

Bug#1051054: bindfs: New upstream version

[Bastian Germann]

Source: bindfs
Version: 1.14.7-1
Severity: important

There are several new upstream versions available.
Please import the latest version.

Bug#1049988: bookworm-pu: package riemann-c-client/1.10.4-2

[Romain Tartière]

Control: tag -1 - moreinfo



signature.asc
Description: PGP signature

Bug#1042513: fontconfig-config: wrong advice from dpkg-reconfigure

[Gunnar Hjalmarsson]

Control: tags -1 + pending

Thanks for your report!

I pushed a commit where I dropped the "(the default in Debian)" part:

https://salsa.debian.org/freedesktop-team/fontconfig/-/commit/45d8eda0

I consider a possible rewrite of the advice in other respects a separate 
thing. That would require a font expert (which I am not).


--
Cheers,
Gunnar Hjalmarsson

Bug#1031781: neurodebian-popcon.gpg'

[Yaroslav Halchenko]

Sorry for the delay. Somehow I even didn't get any message on this bug
report being filed ... odd



On Mon, 20 Feb 2023, Yaroslav Halchenko wrote:
> > How do I get rid of this message?

> apt-get install neurodebian-archive-keyring

> ?

> Let me know how it goes... I will look more in detail later. If still
> observe the issue, reportbug neurodebian-archive-keyring to provide
> detail and so I don't forget about it

I was wrong about what package to implicate here:

you reported

>neurodebian-popularity-contest  deinstall

and indeed that   /usr/share/popularity-contest/neurodebian-popcon.gpg
is from that package.  So I guess, you did/tried to 

dpkg --remove neurodebian-popularity-contest

(not --purge) and that left the cron script present but without key
shipped in the package. That lead to the error.

To resolve it, just 


dpkg --purge neurodebian-popularity-contest

which should also remove 

  /etc/popularity-contest.d/neurodebian.conf

and as a result to avoid that cron job script try to get that key and
report to our popcon server.

I think I have a fix... 

FTR: here is a Dockerfile with which I have created a "test env"

(git)smaug:~exppsy[master]neurodebian-trash/debian-1031781
$> cat Dockerfile
FROM debian:buster

ENV DEBIAN_FRONTEND=noninteractive
RUN apt-get -y update
RUN apt-get -y install eatmydata
RUN eatmydata apt-get -y install sudo gnupg wget locales

RUN wget -O /etc/apt/sources.list.d/neurodebian.sources.list 
http://neuro.debian.net/lists/buster.us-nh.li
bre  && \
apt-key adv --recv-keys --keyserver hkps://keyserver.ubuntu.com 
0xA5D32F012649A5A9 && \
apt-get update -qqq && \
apt-get install -y svgtune  # just to pull in neurodebian-popularity-contest


and here is invocation to try a "fixed up" version:

docker run -it --rm -v 
$PWD/popcon/neurodebian.conf:/etc/popularity-contest.d/neurodebian.conf 
neurodebian-debug:1 bash -c 'set -x; echo PARTICIPATE="yes" >> 
/etc/popularity-contest.conf; dpkg --remove --force
-depends neurodebian-popularity-contest; ls -l 
/etc/cron.daily/popularity-contest /usr/share/popularity-co
ntest/neurodebian-popcon.gpg; ls -l 
/usr/share/doc/neurodebian-popularity-contest; bash -x  /etc/cron.dail
y/popularity-contest'

-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
WWW:   http://www.linkedin.com/in/yarik

Bug#1050992: hwcap default search paths changed

[Aurelien Jarno]

Hi,

On 2023-09-01 09:14, Mathieu Malaterre wrote:
> Source: glibc
> Version: 2.37-1
> 
> Previously defined hwcap search paths have been changed. Those
> specified in `man 8 ld.so` are no longer accurate (bug #1050930).

[snip]

Yes, the old AT_HWCAP mechanism has been deprecated in glibc 2.33 in
favor of the glibc-hwcaps mechanism, and removed in glibc 2.37. Instead
of relying on a huge number of CPU feature combinations, the new
mechanism is based on architecture baseline level. For instance for
amd64 we have x86-64-v1 to x86-64-v4 levels defined directly in the ELF
x86-64-ABI psABI [1]. The supported directories can be queried by
running ld.so --help

That indeed means that the ld.so manpage need to be updated, thanks for
filling the bug against manpages-dev.

> Typical output on sid/i386:

> [...]

> Shared library search path:
>   (libraries located via /etc/ld.so.cache)
>   /lib/i386-linux-gnu (system search path)
>   /usr/lib/i386-linux-gnu (system search path)
>   /lib (system search path)
>   /usr/lib (system search path)
> 
> No subdirectories of glibc-hwcaps directories are searched.
> [...]

Indeed no level has been yet defined for i386 and I am afraid nobody is
really interested in doing so.

> If I understand correctly, this render the following .so file obsolete 
> (unused):
> 
> % file /usr/lib/i386-linux-gnu/i686/sse2/libx264.so.164
> /usr/lib/i386-linux-gnu/i686/sse2/libx264.so.164: ELF 32-bit LSB
> shared object, Intel 80386, version 1 (SYSV), dynamically linked,
> BuildID[sha1]=e66974d10aef77af7ed504266cde974d103484d6, stripped
> 
> Possibly other packages might be impacted.
> 
> I suspect the best upgrade path is simply to document the old hwcap
> search path have been removed, and Debian package(s) should not rely
> on them anymore (lintian warning?).

This is already documented in the upstream NEWS.gz, but it might warrant
an additional entry in NEWS.Debian.gz. The lintian warning might be a
good idea depending how widely this is used in the archive. I'll
investigate and report back.

Regards
Aurelien

[1] https://gitlab.com/x86-psABIs/x86-64-ABI 

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

Bug#1050901: libc6:amd64: install /usr/lib64 without including it

[Aurelien Jarno]

Hi,

On 2023-08-31 09:38, Luca Capello wrote:
> Package: libc6
> Version: 2.31-13+deb11u6
> Severity: minor
> User: l...@pca.it
> Usertags: unige.ch-backup
> User: stor...@unige.ch
> Usertags: unige.ch-backup
> 
> Hi there,
> 
> at UNIGE we use IBM Spectrum Protect (the old Tivoli Storage Manage) as
> the central backup solution, on Debian-based machines via the upstream
> Debian packages:
> 
>   
> 
> 
> Now, `/var/lib/dpkg/info/gsk(crypt|ssl)64.postinst` checks if
> `/usr/lib64` and it creates the `/usr/local/ibm/gsk8_64/lib64/lib*.so`
> symlinks there.
> 
> This was not a problem on non-usrmerged Debian installations, as
> confirmed by various machines of mine, since `/usr/lib64` was not
> shipped/created by any package:
> ```

Indeed, at the time of the amd64 port was created, it was decided to use
(/usr)/lib instead of (/usr)/lib64 to install the libraries. Since then
most of them have been moved to the multiarch path, but that still
stands.

/lib64 was still necessary to store the dynamic loader as part of the
specification.

> [snip]
 
> However, on a recent Debian 12/bookworm `/usr/lib64` is now present:
> ```

This is indeed the case, it is created by the usrmerge package, and not
shipped by glibc.

> [snip]

> 
> While the obvious solution would be for the TSM .debs...
> 
>   # echo '/usr/lib64' >/etc/ld.so.conf.d/local_tivsm_usr-lib64.conf
> 
> ..,I wonder why `/usr/lib64` is not included by default.

/lib64 or /usr/lib64 are not the place to put libraries on debian, so we
do not want to do that.

Regards
Aurelien

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


signature.asc
Description: PGP signature

Bug#1050936: udevadm trigger in initramfs udev script hangs the system

[Michael Biebl]

Am 31.08.23 um 16:14 schrieb thah...@t-online.de:

Package: udev
Version: 254.1-3
Severity: normal

After upgrading udev and sysadm from 252i.6-1 to 254-rc2-3 the system 
hangs during

the initramfs phase in init-top/udev.


Using echo and sleep statements I could find that the
udevadm trigger --verbose --type=devices --action=add
in /usr/share/initramfs-tools/scripts/init-top/udev hangs the system.

Before the upgrade on the 23rd of July the box worked without problems.


I had a cursory look at the log and didn't see any errors which would 
indicate an issue in systemd.
From the log you posted, at around the same time of the upgrade you 
also upgraded your kernel.

It's likely, that this is the real issue here.

Can you bump the log level to debug in init-top/udev, rebuild the 
initramfs and post a more verbose log?

Maybe add a "set -x" while at it.

Michael






OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1050974: binNMU: Rebuild against curl without NSS support

[Paul Gevers]

Hi,

On 01-09-2023 14:25, Samuel Henrique wrote:

These packages have a build dependency on the virtual package
"libcurl4-dev", which is satisfiable by any variant of the curl
binaries (openssl, gnutls, nss).


Policy 7.5 [1] says that "To specify which of a set of real packages 
should be the default to satisfy a particular dependency on a virtual 
package, list the real package as an alternative before the virtual 
one." It's best practice to specify which real package should be used to 
avoid apt choosing it on the buildd. We had variation because of 
temporary non-installability in the past (IIRC), it's better to wait 
with building.


I must admit I though the requirement was stronger and you *had to* 
specify a real package before a virtual build dependency.


Paul

[1] 
https://www.debian.org/doc/debian-policy/ch-relationships.html#virtual-packages-provides


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1043260: ink-generator: diff for NMU version 0.4-3

[Boyuan Yang]

Control: tags -1 +patch +pending

Dear maintainer,

I've prepared an NMU for ink-generator (versioned as 0.4-3) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru ink-generator-0.4/debian/changelog ink-generator-0.4/debian/changelog
--- ink-generator-0.4/debian/changelog  2023-09-01 13:43:46.0 -0400
+++ ink-generator-0.4/debian/changelog  2023-09-01 13:41:33.0 -0400
@@ -1,3 +1,11 @@
+ink-generator (0.4-3) unstable; urgency=medium
+
+  * Take over package maintenance via ITS process. (Closes: #1043260)
+  * debian/source/format: Use "3.0 (quilt)". (Closes: #1043191)
+  * debian/control: Drop dead homepage. (Closes: #804361)
+
+ -- Boyuan Yang   Fri, 01 Sep 2023 13:41:33 -0400
+
 ink-generator (0.4-2.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru ink-generator-0.4/debian/control ink-generator-0.4/debian/control
--- ink-generator-0.4/debian/control2023-09-01 13:43:46.0 -0400
+++ ink-generator-0.4/debian/control2023-09-01 13:41:30.0 -0400
@@ -1,10 +1,9 @@
 Source: ink-generator
 Section: graphics
 Priority: optional
-Maintainer: Aurélio A. Heckert 
+Maintainer: Boyuan Yang 
 Build-Depends: debhelper (>= 7)
 Standards-Version: 3.8.0
-Homepage: http://www.colivre.coop.br/Aurium/InkscapeGenerator
 
 Package: ink-generator
 Architecture: all
diff -Nru ink-generator-0.4/debian/source/format 
ink-generator-0.4/debian/source/format
--- ink-generator-0.4/debian/source/format  1969-12-31 19:00:00.0 
-0500
+++ ink-generator-0.4/debian/source/format  2023-09-01 13:38:53.0 
-0400
@@ -0,0 +1 @@
+3.0 (quilt)


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

Bug#1051053: RM: adapta-kde -- RoQA; Dead Upstream; Unmaintained

[Boyuan Yang]

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

Dear Debian FTP Masters,

As discussed in https://bugs.debian.org/1031184 and 
https://bugs.debian.org/1043020 ,
the development of adapta-kde has completely concluded in 2018. The original
package maintainer (in cc list) did not respond to any bug reports or make any
uploads. Its relevant package in Debian has already been removed due to similar
reasons (see https://tracker.debian.org/pkg/adapta-gtk-theme ). As a result,
please remove package adapta-kde from Debian Archive.

Thanks,
Boyuan Yang


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

Bug#1037213: Awstats bug #1037213 - is bug really fixed?

[Lourisvaldo Figueredo Junior]

Hi Christian,

I saw now that you adopted the awstats package and that you closed this bug 
(1037213).
But I believe the bug is not resolved yet. It happens on bookworm. I have two 
bugs open right now to fix this. [1]

Since you are the maintainer now, how do you want to resolve this issue?

[1]
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050384
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050591



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

Bug#1051052: iwyu: New upstream version: 0.20

[Alejandro Colomar]

Package: iwyu
Version: 8.18-2
Severity: wishlist
X-Debbugs-Cc: alx.manpa...@gmail.com

Hi,

Would you mind packaging the new upstream version, 0.20?

Thanks,
Alex


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

Kernel: Linux 6.3.0-2-amd64 (SMP w/4 CPU threads; PREEMPT)
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 iwyu depends on:
ii  clang   1:14.0-55.7
ii  clang-141:14.0.6-12
ii  libc6   2.37-6
ii  libclang-cpp14  1:14.0.6-12
ii  libllvm14   1:14.0.6-12
ii  libstdc++6  13.1.0-9
ii  python3 3.11.4-5

iwyu recommends no packages.

iwyu suggests no packages.

-- no debconf information

Bug#947706: Updating Debian ports - Debian for PA-RISC

[Boyuan Yang]

在 2019-12-30星期一的 20:22 +0100，Alban Vidal写道：
> Hi Dave,
> 
> Thanks for your reply.
> 
> Le 30/12/2019 à 19:26, John David Anglin a écrit :
> > Yes, ESIEE and HP Systems links can be removed.  The HOWTO documents
> > are in wiki. 
> 
> - The "ESIEE's HOWTO" link removed for the merge request [1],
> - For HP links, we have update them toward archive.org.
> 
> If all is good for you and for HPPA team, we merge it in the next few days.
> 
> Bests regards,
> Alban
> 
> [1] https://salsa.debian.org/webmaster-team/webwml/merge_requests/325


I see no reason of not merging it; merging as-is.

Thanks,
Boyuan Yang


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

Bug#1007061: dvidvi: please consider upgrading to 3.0 source format

[Bastian Germann]

I am uploading a LowNMU to DELAYED/10 to fix this and move the experimental 
changes to unstable.
The debdiff is attached.diff -Nru dvidvi-1.0/debian/changelog dvidvi-1.0/debian/changelog
--- dvidvi-1.0/debian/changelog 2023-09-01 17:14:53.0 +
+++ dvidvi-1.0/debian/changelog 2023-09-01 17:05:38.0 +
@@ -1,3 +1,10 @@
+dvidvi (1.0-10.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Convert to 3.0 source format. (Closes: #1007061)
+
+ -- Bastian Germann   Fri, 01 Sep 2023 17:05:38 +
+
 dvidvi (1.0-10.1) experimental; urgency=medium
 
   * Non-maintainer upload.
@@ -5,9 +12,6 @@
   - debian/compat: removed.
   - debian/control: changed from 'debhelper' to 'debhelper-compat' in
 Build-Depends field and bumped level to 13.
-  - Closes: #817441
-  * debian/control: depend on ${misc:Depends}.
-  * debian/rules: using dh_prep instead of dh_clean -k.
 
  -- Joao Eriberto Mota Filho   Mon, 21 Sep 2020 21:52:53 
-0300
 
@@ -24,6 +28,35 @@
 
  -- Lionel Elie Mamane   Tue, 20 Feb 2007 17:57:36 +0100
 
+dvidvi (1.0-8.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix the NMU version.
+  * Fix FTCBFS: Use triplet-prefixed compiler. Thanks to
+Helmut Grohne . (Closes: #843346)
+
+ -- Joao Eriberto Mota Filho   Thu, 22 Dec 2016 18:12:22 
-0200
+
+dvidvi (1.0-8etch2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Logan Rosen ]
+
+  * debian/control: depend on ${misc:Depends}.
+  * debian/rules:
+  - Add recommended build-arch and build-indep targets.
+  - Use dh_prep instead of dh_clean -k.
+
+  [ Joao Eriberto Mota Filho ]
+
+  * Bumped DH level to 10. (Closes: #817441)
+  * debian/control:
+  - Added the Homepage field.
+  - Bumped Standards-Version to 3.9.8.
+
+ -- Joao Eriberto Mota Filho   Wed, 26 Oct 2016 15:00:57 
-0200
+
 dvidvi (1.0-8etch2) unstable; urgency=low
 
   * Replace versions of texlive that contained dvidvi
@@ -116,14 +149,14 @@
 
 dvidvi (1.0-2) unstable; urgency=low
 
-  * Put original distribution in dvidvi_1.0.orig.tar.gz.  Changed rules
-to remove the executable as well.
+  * Put original distribution in dvidvi_1.0.orig.tar.gz.  Changed rules 
+to remove the executable as well. 
 
  -- David A. van Leeuwen   Sun, 9 Nov 1997 12:21:57 
+0100
 
 dvidvi (1.0-1) unstable; urgency=low
 
   * First compile.  Added script `a5booklet' that allows you to print two
-a5 pages on one a5 page side by side.
+a5 pages on one a5 page side by side. 
 
  -- David A. van Leeuwen   Mon, 13 Oct 1997 
23:05:41 +0200
diff -Nru dvidvi-1.0/debian/control dvidvi-1.0/debian/control
--- dvidvi-1.0/debian/control   2023-09-01 17:14:53.0 +
+++ dvidvi-1.0/debian/control   2023-09-01 16:56:04.0 +
@@ -2,12 +2,13 @@
 Section: tex
 Priority: optional
 Maintainer: Lionel Elie Mamane 
-Standards-Version: 3.7.2.2
+Standards-Version: 3.9.8
 Build-Depends: debhelper-compat (= 13)
+Homepage: https://www.ctan.org/tex-archive/dviware/dvidvi
 
 Package: dvidvi
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}
+Depends: ${misc:Depends}, ${shlibs:Depends}
 Replaces: texlive-extra-utils (<< 2005.dfsg.2-12)
 Description: Manipulate .dvi files
  Allows you to select, change the order, and/or shift the pages in
diff -Nru dvidvi-1.0/debian/patches/debian-with-kohm.patch 
dvidvi-1.0/debian/patches/debian-with-kohm.patch
--- dvidvi-1.0/debian/patches/debian-with-kohm.patch1970-01-01 
00:00:00.0 +
+++ dvidvi-1.0/debian/patches/debian-with-kohm.patch2023-09-01 
17:05:38.0 +
@@ -0,0 +1,572 @@
+--- dvidvi-1.0.orig/dvidvi.1
 dvidvi-1.0/dvidvi.1
+@@ -1,4 +1,4 @@
+-.TH DVIDVI L "March 1994"
++.TH DVIDVI 1 "March 1994"
+ .SH NAME
+ .PP
+ dvidvi \- selects and/or re-arranges pages in a TeX dvi file
+--- dvidvi-1.0.orig/dvidvi.c
 dvidvi-1.0/dvidvi.c
+@@ -14,52 +14,88 @@
+  *  print both on same page   -m 2:0,1(5.5in,0in)
+  *  do folded brochures   -m 4:-3,0(5.5in,0in)
+  *-m 4:1,-2(5.5in,0in)
++ *  round up number of pages to a
++ *multiple of n   -p n
++ *  sort pages to print one from top  -j
++ *next one from end
+  *  etc.
+  *
+  *The original program is by Tomas Rokicki (version 0.5) but it was
+  *modified and improved by Esteban ZIMANYI ezima...@rc1.vub.ac.be
+  *to give version 1.0.
++ *To give version 1.1 it was improved by markus_k...@ka.maus.de.
+  *
+  *This version has been tested for the IBM PC and compatibles under
+- *compilers Turbo C 2.0 and Microsoft C 6.0.
++ *compilers Turbo C 2.0 and Microsoft C 6.0 and for Atari ST under
++ *compiler Turbo C 2.0 with MiNTLIB.
+  *
+  */
+ #define SEEK_SET 0
+ #define SEEK_CUR 1
+ #define SEEK_END 2
+ 
+-#define BANNER "\nThis is dvidvi 1.0, Copyright (C) 1988-91, Radical Eye 
Software\n"
+-#define STRINGSIZE (500)  /* maximum number of 

Bug#1050001: Practical problems with proposed symlink farming: diversions

[Andreas Metzler]

On 2023-09-01 Ansgar  wrote:
> Hi,

> a practical thing with usrmerge and legacy layout[1] is the following:
> assume you do not want programs to find a specific program via PATH
> lookup or even a fully-qualified path.
> Then a user can just divert that single program away (or just remove
> it, depending on details).

> With Jackson's proposed symlink farms this property goes away:
> users now have to handle both the copy in / and /usr!
[...]


Hello,

I do not think this is the case.

A) The proposed /bin/ will not contain symlinks for everything in
/usr/bin but just for files that used to live there. I am not sure
how common it is  to divert one of this subset in the first place.

B) I Think diverting the real file in /usr/bin would be enough, the
now broken symlink in /bin should not be found by normal path search -
At least that is true for bash, dash and tcsh, also test -x does not
succeed on the symlink.

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#1051051: bullseye-pu: package rustc-mozilla/1.63.0+dfsg1-2~deb11u1

[Emilio Pozuelo Monfort]

Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: team+pkg-mozi...@tracker.debian.org

Hi,

The time has come for a new Firefox / Thunderbird ESR release in *stable.
This will require rustc/cargo/cbindgen backports as usual. For bookworm
we're in a good shape for this update, but for bullseye and buster we'll
need all three updates.

For rustc-mozilla, I've used the version from bookworm. Hopefully I got
all the stage0 binaries this time.

Risk is low as this package is only used to build FF/TB. I have
successfully built the whole chain up to FF 115 ESR on amd64.

I'm attaching a diff from rustc_1.63/bookworm to the proposed update. I don't 
think there's much value in a 1.59->1.63 diff, but if you want it say so and 
I'll prepare one.

Thanks,
Emilio
diff -ruNp debian.rustc/changelog debian/changelog
--- debian.rustc/changelog  2023-01-14 09:38:46.0 +0100
+++ debian/changelog2023-07-28 13:44:06.0 +0200
@@ -1,3 +1,13 @@
+rustc-mozilla (1.63.0+dfsg1-2~deb11u1) bullseye; urgency=medium
+
+  * Non-maintainer upload.
+  * Backport to bullseye as rustc-mozilla.
+  * Do a bootstrap build.
+  * Disable wasm.
+  * Disable new binary packages rustfmt, -clippy, -all.
+
+ -- Emilio Pozuelo Monfort   Fri, 28 Jul 2023 13:44:06 +0200
+
 rustc (1.63.0+dfsg1-2) unstable; urgency=medium
 
   [ Fabian Grünbichler ]
diff -ruNp debian.rustc/control debian/control
--- debian.rustc/control2023-01-14 09:38:46.0 +0100
+++ debian/control  2023-07-28 13:44:06.0 +0200
@@ -1,4 +1,4 @@
-Source: rustc
+Source: rustc-mozilla
 Section: devel
 Priority: optional
 Maintainer: Debian Rust Maintainers 

@@ -12,14 +12,14 @@ Build-Depends:
  debhelper-compat (= 13),
  dpkg-dev (>= 1.17.14),
  python3:native,
- cargo:native (>= 0.60.0)  ,
- rustc:native (>= 1.62.0+dfsg) ,
- rustc:native (<= 1.63.0++),
- llvm-14-dev:native,
- llvm-14-tools:native,
+# cargo:native (>= 0.60.0)  ,
+# rustc:native (>= 1.62.0+dfsg) ,
+# rustc:native (<= 1.63.0++),
+ llvm-13-dev:native,
+ llvm-13-tools:native,
  gcc-mingw-w64-x86-64-posix:native [amd64] ,
  gcc-mingw-w64-i686-posix:native [i386] ,
- libllvm14 (>= 1:14.0.0),
+ libllvm13 (>= 1:13.0.0),
  cmake (>= 3.0) | cmake3,
 # needed by some vendor crates
  pkg-config,
@@ -38,30 +38,32 @@ Build-Depends:
  curl ,
  ca-certificates ,
 Build-Depends-Indep:
- wasi-libc (>= 0.0~git20220510.9886d3d~~) ,
- wasi-libc (<= 0.0~git20220510.9886d3d++) ,
- clang-14:native,
+# wasi-libc (>= 0.0~git20220510.9886d3d~~) ,
+# wasi-libc (<= 0.0~git20220510.9886d3d++) ,
+ clang-13:native,
 Build-Conflicts: gdb-minimal 
 Standards-Version: 4.2.1
 Homepage: http://www.rust-lang.org/
 Vcs-Git: https://salsa.debian.org/rust-team/rust.git
 Vcs-Browser: https://salsa.debian.org/rust-team/rust
 
-Package: rustc
+Package: rustc-mozilla
 Architecture: any
 Multi-Arch: allowed
 Pre-Depends: ${misc:Pre-Depends}
 Depends: ${shlibs:Depends}, ${misc:Depends},
- libstd-rust-dev (= ${binary:Version}),
+ libstd-rust-mozilla-dev (= ${binary:Version}),
  gcc, libc-dev, binutils (>= 2.26)
 Recommends:
  cargo (>= 0.64.0~~), cargo (<< 0.65.0~~),
 # llvm is needed for llvm-dwp for -C split-debuginfo=packed
- llvm-14,
+ llvm-13,
 Suggests:
 # lld and clang are needed for wasm compilation
- lld-14, clang-14,
-Replaces: libstd-rust-dev (<< 1.25.0+dfsg1-2~~)
+ lld-13, clang-13,
+Conflicts: rustc
+Provides: rustc (= ${binary:Version})
+Replaces: libstd-rust-dev (<< 1.25.0+dfsg1-2~~), rustc
 Breaks: libstd-rust-dev (<< 1.25.0+dfsg1-2~~)
 Description: Rust systems programming language
  Rust is a curly-brace, block-structured expression language.  It
@@ -76,7 +78,7 @@ Description: Rust systems programming la
  generic programming and meta-programming, in both static and dynamic
  styles.
 
-Package: libstd-rust-1.63
+Package: libstd-rust-mozilla-1.63
 Section: libs
 Architecture: any
 Multi-Arch: same
@@ -98,12 +100,12 @@ Description: Rust standard libraries
  This package contains the standard Rust libraries, built as dylibs,
  needed to run dynamically-linked Rust programs (-C prefer-dynamic).
 
-Package: libstd-rust-dev
+Package: libstd-rust-mozilla-dev
 Section: libdevel
 Architecture: any
 Multi-Arch: same
 Depends: ${shlibs:Depends}, ${misc:Depends},
- libstd-rust-1.63 (= ${binary:Version}),
+ libstd-rust-mozilla-1.63 (= ${binary:Version}),
 Description: Rust standard libraries - development files
  Rust is a curly-brace, block-structured expression language.  It
  visually resembles the C language family, but differs significantly
@@ -121,7 +123,7 @@ Description: Rust standard libraries - d
  needed to compile Rust programs. It may also be installed on a system
  of another host architecture, for cross-compiling to this architecture.
 
-Package: libstd-rust-dev-windows
+Package: libstd-rust-mozilla-dev-windows
 Section: libdevel
 Architecture: amd64 i386
 Multi-Arch: same
@@ -129,6 +131,7 @@ Depends: 

Bug#894081: closing 894081

[Adam D. Barratt]

[BCCed to everyone that I'm aware of having expressed interest in the
bug log]

On Tue, 2023-08-29 at 11:49 +0100, Mark Hymers wrote:
> close 894081 
> thanks
> 
> The debian-security-debug archive is now enabled from the ftp-team
> POV.  Some mirroring
> infrastructure still needs to be set up, this is tracked by DSA in
> RT#7514.

For the record, that's now available via 
https://deb.debian.org/debian-security-debug/

Regards,

Adam

Bug#1050944: jtreg6: please make the build reproducible

[Chris Lamb]

Hey tony & Vagrant,

> > Maybe this should be restricted to only make it writeable to the
> > user ... e.g. chmod u+w or similar?

Ah, I mistakenly confused "+w" as a synonym for "u+w". (I used to know
all the octal codes like the back of my hand, but there seems to be
little call to use them in the 2020s…)

> […] I went with the following for symmetry:
>
> execute_before_dh_strip_nondeterminism:
> find  debian/ -type f -name jtreg.jar -print0 | xargs -0tr chmod u+w
>
> execute_after_dh_strip_nondeterminism:
> find  debian/ -type f -name jtreg.jar -print0 | xargs -0tr chmod u-w

As you like… Although the `execute_after` portion feels a little
redundant to me. After all, it doesn't seem right that the build
system is generating read-only build artefacts to begin with. But
it's your package. :)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-

Bug#1051050: RM: gudev-sharp-3.0 -- RoQA; dead upstream; unmaintained; RC-buggy

[Bastian Germann]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
Control: affects -1 + src:gudev-sharp-3.0

Please remove gudev-sharp-3.0. The package is dead upstream and unmaintained in Debian. It has only 
been in experimental for a decade, has a RC bug, and was never used by any other package.

Bug#912884: closed by Jan Mojzis ()

[Thorsten Glaser]

reopen 912884
found 912884 1:0.76-9
thanks

Debian Bug Tracking System dixit:

>If this explanation is unsatisfactory and you have not received a

Yes, this is *extremely* unsatisfactory, but…

>better one in a separate message then please contact Jan Mojzis 
> by

… Googlemail addresses should be forbidden for Debian maintainers,
as communication with them is impossible.


Jan Mojzis dixit:

>Hello,
>this bug seems to be obsolete,
>we will close it.

This bug is nowhere even NEAR obsolete.

>If the problem persists in the new version (>= 1:0.76-9),
>please reopen the bug.

Did you even READ the bugreport AT ALL, or did you just mass-close
all existing bugreports because you couldn’t be arsed to look at them?

Of COURSE this bug is still relevant and still exists!

Slightly appalled,
//mirabilos
-- 
Stéphane, I actually don’t block Googlemail, they’re just too utterly
stupid to successfully deliver to me (or anyone else using Greylisting
and not whitelisting their ranges). Same for a few other providers such
as Hotmail. Some spammers (Yahoo) I do block.

Bug#965701: log4net: Removal of obsolete debhelper compat 5 and 6 in bookworm

[Bastian Germann]

There is activity on the reverse dependency quickroute-linux, which is why I 
wanted to NMU this.
I have seen Mirco's changes in git and am sponsoring them instead.

Bug#1050001: Third-party tooling support for merged-/usr vs symlink farms

[Ansgar]

Hi,

On Fri, 2023-09-01 at 13:42 +0100, Luca Boccassi wrote:
> the claim that Ansible, Puppet, Chef, Docker, Rsync and whatnot no
> longer work on Debian/Ubuntu/Fedora/Arch/SUSE/CentOS/RHEL/etc

I think this is a valid point that should be discussed.

How do third-party tools cope with merged-/usr (as implemented in
Debian and elsewhere)?  And how is the support for the proposed symlink
farm layout?

Has anyone done prior investigation on this?

Are there already experimental systems converted to the new layout or
some way to convert an existing system to this for testing (not on a
production system)? It might be interesting to experiment with the new
layout.

Ansgar

Bug#1051049: lvm2: fails to boot on mirrored+snapshoted roofs

[Yoann Congal]

Package: lvm2
Version: 2.03.16-2
Severity: normal

Dear Maintainer,

* What led up to the situation?

My system has a mirrored rootfs LV. When snapshoting and merging this
snapshot, the system refuses to boot.

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

My rootfs is vg1/root (mirrored using raid1)

To simulate a snapshot, I do:
  lvcreate -s -n root-snap -L 100MB /dev/vg1/root

Simulation of modification :
  dd if=/dev/urandom of=/test bs=1M count=40

Merging snapshot :
  lvconvert --merge vg1/root-snap

Since rootfs is mounted, the following message is displayed:
  Delaying merge since origin is open.
  Merging of snapshot vg1/root-snap will occur on next activation of vg1/root.

  reboot

   * What was the outcome of this action?

Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... 
done.
Begin: Running /scripts/local-block ... done.
.../...
Begin: Running /scripts/local-block ... done.
done.
Gave up waiting for root file system device.  Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT!  /dev/mapper/vg1-root does not exist.  Dropping to a shell!


BusyBox v1.35.0 (Debian 1:1.35.0-4+b3) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs)

Notice that que root LV is not activated :

(initramfs) lvm lvs
  LV  VG  Attr   LSize   Pool Origin Data%  Meta%  Move Log 
Cpy%Sync Convert
  rootvg1 Owi---r---   3.71g
   
   * What outcome did you expect instead?
root LV is activated during boot and while system boots.

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

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

Versions of packages lvm2 depends on:
ii  dmeventd   2:1.02.185-2
ii  dmsetup2:1.02.185-2
ii  libaio10.3.113-4
ii  libblkid1  2.38.1-5+b1
ii  libc6  2.36-9+deb12u1
ii  libdevmapper-event1.02.1   2:1.02.185-2
ii  libedit2   3.1-20221030-2
ii  libselinux13.4-1+b6
ii  libsystemd0252.12-1~deb12u1
ii  libudev1   252.12-1~deb12u1
ii  sysvinit-utils [lsb-base]  3.06-4

Versions of packages lvm2 recommends:
pn  thin-provisioning-tools  

lvm2 suggests no packages.

-- no debconf information

Bug#1050001: Practical problems with proposed symlink farming: diversions

[Ansgar]

Hi,

a practical thing with usrmerge and legacy layout[1] is the following:
assume you do not want programs to find a specific program via PATH
lookup or even a fully-qualified path.
Then a user can just divert that single program away (or just remove
it, depending on details).

With Jackson's proposed symlink farms this property goes away:
users now have to handle both the copy in / and /usr!

What is worse: both entries could be managed by different means
(shipped by the package, created by maintscript, created by some
external process).

This will probably cause breakage with third party integrations of
management systems like Ansible.

It also seems like a nice property that I don't see any convincing
reason to lose so far; we should try to keep the system simple and not
introduce such complexities without reason (and rigorous reasoning that
it is safe to do so!).

Any thoughts about this?

Ansgar

  [1]: With some exceptions such as some programs have compat symlinks
in the legacy layout or between .../bin and .../sbin.

Bug#1051048: RM: dbus-sharp -- RoQA; dead upstream; unmaintained

[Bastian Germann]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
Control: affects -1 + src:dbus-sharp
Control: block -1 by 1051047

dbus-sharp is dead upstream and unmaintained in Debian.
After its last reverse dependency is removed (see blocks) it should be removed 
as well.

Bug#1049903: Acknowledgement (petsc: misbuild with gcc-13)

[Steve Langasek]

Hi Drew,

Sorry, your message didn't go to 1049903-submit...@bugs.debian.org so I
didn't receive it.

> With patching, wouldn't it be simpler to just add -lstdc++ to
> CXX_LINKER_FLAGS at configuration time (in debian/rules) rather than
> hacking the upstream detection code?  As you say, hardcoding in the
> upstream scripts doesn't really resolve the underlying problem.

Unfortunately, CXX_LINKER_FLAGS is the variable used to pass flags to the
*C++ linker*.  But what is being done here is invoking the *C linker* to
link to C++ code.

And if the code in question were being linked with the C++ linker, it
wouldn't need an explicit -lstdc++ argument anyway.

I tried every which way to get this to work via environment exports with no
luck.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#1051047: RM: dbus-sharp-glib -- RoQA; dead upstream; unmaintained

[Bastian Germann]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
Control: affects -1 + src:dbus-sharp-glib
Control: block -1 by 1049370 1043350

dbus-sharp-glib is dead upstream and unmaintained in Debian.
After its last reverse dependencies are removed (see blocks) it should be 
removed as well.

Bug#1050867: marked as pending in jekyll

[Sébastien Villemot]

Hi Antonio,

Le mercredi 30 août 2023 à 15:33 +, Antonio Terceiro a écrit :
> Bug #1050867 in jekyll reported by you has been fixed in the
> Git repository and is awaiting an upload. You can see the commit
> message below and you can check the diff of the fix at:
> 
> https://salsa.debian.org/ruby-team/jekyll/-/commit/78d57aff39390464d023660c55803806b6b7f06f
> 
> 
> Allow YAML aliases
> 
> Closes: #1050867
> 

Thanks for swiftly fixing this issue!

Shouldn’t the fix be backported to bookworm?

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



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

Bug#1007415: fortunes-it: please consider upgrading to 3.0 source format

[Bastian Germann]

I am uploading a NMU to DELAYED/10 to fix this.
The debdiff is attached.diff -Nru fortunes-it-1.99/debian/changelog fortunes-it-1.99/debian/changelog
--- fortunes-it-1.99/debian/changelog   2023-09-01 17:11:18.0 +0200
+++ fortunes-it-1.99/debian/changelog   2023-09-01 17:03:45.0 +0200
@@ -1,3 +1,19 @@
+fortunes-it (1.99-4.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Convert to source format 3.0. (Closes: #1007415)
+  * Do not claim that Franklin was a president. (Closes: #1016115)
+
+  [Raúl Benencia]
+  * Fix typo in testi/paolotedeschi. (Closes: #788097)
+  * Fix typo in testi/zuse. (Closes: #792271)
+  * Fix typo in testi/luke. (Closes: #833062)
+
+  [Vijeth T Aradhya]
+  * Fix typo in testi/italia. (Closes: #787140)
+
+ -- Bastian Germann   Fri, 01 Sep 2023 17:03:45 +0200
+
 fortunes-it (1.99-4.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru fortunes-it-1.99/debian/patches/debian.patch 
fortunes-it-1.99/debian/patches/debian.patch
--- fortunes-it-1.99/debian/patches/debian.patch1970-01-01 
01:00:00.0 +0100
+++ fortunes-it-1.99/debian/patches/debian.patch2023-09-01 
17:03:45.0 +0200
@@ -0,0 +1,691 @@
+--- /dev/null
 fortunes-it-1.99/Makefile
+@@ -0,0 +1,14 @@
++COOKIEDIR=$(prefix)/usr/share/games/fortunes
++OCOOKIEDIR=$(prefix)/usr/share/games/fortunes/off
++
++clean:
++  cd testi && $(MAKE) clean
++normal:
++  cd testi && $(MAKE) COOKIEDIR=$(COOKIEDIR) normal
++
++offensive:
++  cd testi && $(MAKE) OCOOKIEDIR=$(OCOOKIEDIR) offensive
++
++all: normal offensive
++
++.PHONY: clean normal offensive all
+--- /dev/null
 fortunes-it-1.99/testi/Makefile
+@@ -0,0 +1,56 @@
++
++COOKIES=adams banner computer definizioni formiche italia itatrek jackfr 
leggi luke \
++  luttazzi norm paolotedeschi zuse
++
++OCOOKIES=computer-o definizioni-o film-o formiche-o italia-o jackfr-o leggi-o 
luke-o luttazzi-o norm-o obsc-o paolotedeschi-o zuse-o
++
++STRFILE=`which strfile`
++
++.PHONY: clean normal offensive
++
++clean:
++  rm -f *.dat *.u8 *-stamp
++  for i in $(COOKIES) $(OCOOKIES) ; do \
++  if [ -f $$i.old ]; then \
++  mv -f $$i.old $$i; \
++  fi; \
++  done
++
++normal-stamp: 
++  for i in $(COOKIES) ; \
++do \
++if [ ! -f $$i.old ] ; then \
++cp $$i $$i.old; \
++fi; \
++recode latin1..u8 $$i ; \
++$(STRFILE) $$i ; \
++ln -s $$i $$i.u8 || exit $? ; \
++done
++  touch normal-stamp
++
++offensive-stamp: 
++  for i in $(OCOOKIES) ; \
++do \
++if [ ! -f $$i.old ] ; then \
++cp $$i $$i.old; \
++fi; \
++recode latin1..u8 $$i ; \
++$(STRFILE) $$i ; \
++ln -s $$i $$i.u8 || exit $? ; \
++done
++  touch offensive-stamp
++
++normal: normal-stamp
++  install -m 0755 -d $(COOKIEDIR)
++  for i in $(COOKIES) ; do \
++  install -m 0644 $$i $$i.dat $(COOKIEDIR) || exit $? ; \
++  cp -d $$i.u8 $(COOKIEDIR) ; \
++  done
++
++  
++offensive: offensive-stamp
++  install -m 0755 -d $(OCOOKIEDIR)
++  for i in $(OCOOKIES) ; do \
++  install -m 0644 $$i $$i.dat $(OCOOKIEDIR) || exit $? ; \
++  cp -d $$i.u8 $(OCOOKIEDIR) ; \
++  done
+--- fortunes-it-1.99.orig/testi/formiche
 fortunes-it-1.99/testi/formiche
+@@ -181,10 +181,6 @@ Reagan non sa dire la differenza.
+ - Allora hai superato anche me.
+   -- Lowell Ganz e Babaloo Mandel
+ %
+-Preferirei essere negro piuttosto che gay, perche' se sei negro non lo devi
+-dire a tua madre!
+-  -- Charles Pierce
+-%
+ Io ho un amico cosi' pigro, cosi' pigro, ma cosi' pigro, che ha sposato
+ una donna incinta.
+   -- Gino Bramieri
+@@ -610,7 +606,7 @@ Icaro credeva di essere un uccello, inve
+   -- Jean Charles
+ %
+ - Cara, se avessi saputo che eri vergine, ci avrei messo piu' tempo.
+-- Caro, se avessi saputo che c'era piu', tempo mi sarei tolta i collants.
++- Caro, se avessi saputo che c'era piu' tempo, mi sarei tolta i collants.
+   -- Anonimo
+ %
+ L'automobile del futuro sara' piu' veloce del suono.
+--- /dev/null
 fortunes-it-1.99/testi/formiche-o
+@@ -0,0 +1,4 @@
++Preferirei essere negro piuttosto che gay, perche' se sei negro non lo devi
++dire a tua madre!
++  -- Charles Pierce
++%
+--- fortunes-it-1.99.orig/testi/italia
 fortunes-it-1.99/testi/italia
+@@ -454,10 +454,6 @@ Meglio sapere un po' di tutto che tutto
+ Un classico e' qualcosa che tutti vogliono aver letto e nessuno vuole leggere.
+   -- Mark Twain
+ %
+-Mio padre era un creolo, suo padre un Negro, e suo padre una scimmia;
+-la mia famiglia, a quanto pare, inizia dove la tua e' finita.
+-  -- Alexandre Dumas, padre

Bug#1051046: Updating the zeitgeist-sharp Uploaders list

[Mattia Rizzolo]

Source: zeitgeist-sharp
Version: 0.8.0.0-5.1
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Jo Shields  has retired, so can't work on
the zeitgeist-sharp package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#1051045: Updating the xsp Uploaders list

[Mattia Rizzolo]

Source: xsp
Version: 4.2-2.4
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Jo Shields  has retired, so can't work on
the xsp package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#1051044: Updating the opentk Uploaders list

[Mattia Rizzolo]

Source: opentk
Version: 1.1.4c+dfsg-2.2
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Jo Shields  has retired, so can't work on
the opentk package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#1051043: Updating the nuget Uploaders list

[Mattia Rizzolo]

Source: nuget
Version: 2.8.7+md510+dhx1-1.1
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Jo Shields  has retired, so can't work on
the nuget package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#1051042: Updating the npgsql Uploaders list

[Mattia Rizzolo]

Source: npgsql
Version: 2.2.7+dfsg3-1.1
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Jo Shields  has retired, so can't work on
the npgsql package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#1051041: Updating the mono.reflection Uploaders list

[Mattia Rizzolo]

Source: mono.reflection
Version: 1.0+git20110407+d2343843-3.1
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Jo Shields  has retired, so can't work on
the mono.reflection package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#1051040: Updating the mono Uploaders list

[Mattia Rizzolo]

Source: mono
Version: 6.8.0.105+dfsg-3.3 6.8.0.105+dfsg-3.4
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Jo Shields  has retired, so can't work on
the mono package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#1051039: ITP: wlopm -- Wayland output power management

[Birger Schacht]

Package: wnpp
Severity: wishlist
Owner: Birger Schacht 
X-Debbugs-Cc: debian-de...@lists.debian.org, bir...@debian.org

* Package name: wlopm
  Version : 0.1.0
  Upstream Contact: Leon Henrik Plickat
* URL : https://git.sr.ht/~leon_plickat/wlopm
* License : GPL
  Programming Lang: C
  Description : Wayland output power management

wlopm - Wayland output power management
Simple client implementing zwlr-output-power-management-v1.
wlopm is licensed under the GPLv3.

This package will be maintained under the swaywm-team's umbrella.

Bug#1051037: Updating the libgdiplus Uploaders list

[Mattia Rizzolo]

Source: libgdiplus
Version: 6.1+dfsg-1
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Jo Shields  has retired, so can't work on
the libgdiplus package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#1051038: Updating the mod-mono Uploaders list

[Mattia Rizzolo]

Source: mod-mono
Version: 3.8-3
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Jo Shields  has retired, so can't work on
the mod-mono package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#999992: pike8.0: depends on obsolete pcre3 library

[Bastian Germann]

On Tue, 22 Aug 2023 14:20:15 +0200 Bastian Germann wrote:

Please find a patch enclosed with pike8.0-pcre dropped.

I am uploading a NMU with the previously sent debdiff.

Bug#1051036: opencc FTCBFS: opencc_dict not found

[Helmut Grohne]

Source: opencc
Version: 1.1.6+ds1-1
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

opencc fails to cross build from source. It normally runs its built
opencc_dict during build, but in a cross build that is not possible and
it expects a built opencc_dict for the build architecture to be
installed. I'm attaching a patch to add this dependency. Please
observe that since this dependency has a positive build profile, it is
normally inactive. It is only relevant to cross builds. Native builds
continue to use the built opencc_dict.

Helmut
diff --minimal -Nru opencc-1.1.6+ds1/debian/changelog 
opencc-1.1.6+ds1/debian/changelog
--- opencc-1.1.6+ds1/debian/changelog   2022-12-10 13:10:03.0 +0100
+++ opencc-1.1.6+ds1/debian/changelog   2023-09-01 14:32:04.0 +0200
@@ -1,3 +1,10 @@
+opencc (1.1.6+ds1-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Add B-D: opencc  for opencc_dict. (Closes: #-1)
+
+ -- Helmut Grohne   Fri, 01 Sep 2023 14:32:04 +0200
+
 opencc (1.1.6+ds1-1) unstable; urgency=medium
 
   * Team upload
diff --minimal -Nru opencc-1.1.6+ds1/debian/control 
opencc-1.1.6+ds1/debian/control
--- opencc-1.1.6+ds1/debian/control 2022-07-23 18:53:38.0 +0200
+++ opencc-1.1.6+ds1/debian/control 2023-09-01 14:32:02.0 +0200
@@ -17,6 +17,7 @@
  googletest ,
  libmarisa-dev,
  libtclap-dev,
+ opencc ,
  pkg-kde-tools,
  pybind11-dev,
  python3:any,

Bug#1051035: O: python-pyrdfa -- RDFa distiller and parser

[Bastian Germann]

Package: wnpp

The package was orphaned with revision 3.5.2+20220621~ds-1.

Description: RDFa distiller and parser for Python
 PyRDFA is an RDFa 1.1 parser,
 also referred to as an RDFa distiller.
 .
 Resource Description Framework in Attributes (RDFa)
 is a W3C Recommendation
 that adds a set of attribute-level extensions
 to HTML, XHTML and various XML-based document types
 for embedding rich metadata within Web documents.

Bug#1051034: O: libapreq2 -- generic Apache request library

[Bastian Germann]

Package: wnpp

The package libapreq2 was orphaned with revision 2.17-1.

Description: generic Apache request library
 The generic Apache request library (APR) contains modules for manipulating
 client request data with the Apache API from Perl and C. Functionality
 includes:
 .
  - parsing of application/x-www-form-urlencoded data
  - parsing of multipart/form-data
  - parsing of HTTP Cookies

Bug#1051033: O: tla -- GNU Arch revision control system

[Bastian Germann]

Package: wnpp

The package tla was orphaned long ago with revision 1.3.5+dfsg-10.

Description: GNU Arch revision control system
 Arch is a modern replacement for CVS, specifically designed for the
 distributed development. It supports development on branches,
 distributed repositories, changeset-oriented project management,
 and of course, file and directory renaming.

Bug#1050944: Additional information

[tony mancill]

On Fri, Sep 01, 2023 at 07:04:05PM +1200, Vladimir Petko wrote:
>  The debhelper-compat was intentionally set to >=11 in order to
> support backports.

Hi Vladimir,

Thank you for the reminder.  I can easily revert the change.  But to
make sure I understand the requirements, how far back do we want to
support backports of new uploads of jtreg6?

Although it wasn't part of the buster release, debhelper 13.x is
available in old-old-stable (buster) backports [0,1], which is as far as
I looked before making the change.  Is jtreg6 needed for stretch, which
is currently in EOL ELTS [2]?

Thank you,
tony

[0] https://packages.debian.org/source/buster-backports/debhelper
[1] https://packages.debian.org/source/oldoldstable-backports/debhelper
[2] https://wiki.debian.org/DebianReleases


signature.asc
Description: PGP signature

Bug#1051028: google-chrome-stable: Google Chrome does not respect prefers-color-scheme for webpages on KDE Plasma

[GwenDragon]

Testcase


1. Open f.ex. https://gwendragon.de/ or https://youtube.com in Google Chrome 
2. Page has white background and is not rendered in CSS dark scheme

Expected


Page is rendered in dark CSS scheme 

Current
---

Page is rendered in light CSS scheme 

Additional
--

Works in 
- Firefox 117

Fails in
- Edge 116
- Chrome 116.0.5845.140
- Chrome 117.0.5938.35 beta
- Chrome 118.0.5979.0 dev
- Vivaldi 6.2.3105.45 Stable

In all Chromium related browsers chrome://settings/appearance was set 
to GTK long time ago to get Breeze Dark theme working. 

With browsers before Chromium 116 core all was ok with rendering in KDE.

KDE was installed with Debian 11 netinstaller some months ago and 
rendering workd in older browsers. 

More strangeness is that prefers-color-scheme works in a Debian 11.7 
GNOME installation! 

-- 
Regards
GwenDragon


pgpLbuNIZM5xl.pgp
Description: PGP signature

Bug#1050256: [pkg-apparmor] Bug#1050256: autopkgtest fails on debci

[Michael Biebl]

Am 01.09.23 um 13:23 schrieb Michael Biebl:
The only way to fix the container was to use the aforementioned 
`lxc.apparmor.profile = unconfined`.
I think we should do that as the breakage is rather widespread and I 
already see individual packages trying to work around that to at least 
keep debci afloat.


See e.g.:
https://salsa.debian.org/systemd-team/systemd/-/merge_requests/211
https://salsa.debian.org/debian/pdns/-/commit/637e54ef73386541086da430553b82db78266bac

or disabling the systemd hardening options completely_
https://salsa.debian.org/utopia-team/polkit/-/blob/master/debian/patches/debian/Don-t-use-PrivateNetwork-yes-for-the-systemd-unit.patch

This is not a good outcome of this and the problem will become more 
apparent with debci running on bookworm now.




I went ahead and submitted
https://salsa.debian.org/lxc-team/lxc/-/merge_requests/18
since I don't see another solution atm.

Looping in the release team as well for their input.


Regards,
Michael


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1031747: python-socks: autopkgtest regression

[Benjamin Drung]

On Wed, 22 Feb 2023 00:45:20 +0200 Adrian Bunk  wrote:
> Source: python-socks
> Version: 2.1.1-1
> Severity: serious
> 
>
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-socks/31564223/log.gz
> 
> ...
> autopkgtest [18:13:28]: test unittests: [---
> === python3.11 ===
> ImportError while loading conftest '/tmp/autopkgtest-
lxc.hgtwobwo/downtmp/autopkgtest_tmp/tests/conftest.py'.
> tests/conftest.py:34: in 
> from tests.proxy_server import ProxyConfig, ProxyServer
> tests/proxy_server.py:9: in 
> from tiny_proxy import (
> E   ModuleNotFoundError: No module named 'tiny_proxy'
> autopkgtest [18:13:29]: test unittests: ---]
> autopkgtest [18:13:29]: test unittests:  - - - - - - - - - - results -
- - - - - - - - -
> unittests    FAIL non-zero exit status 4
> ...

This failure can be solved by packaging tiny_proxy:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051025

I have the tested that locally.

-- 
Benjamin Drung
Debian & Ubuntu Developer

Bug#1050378: python3-selenium package in Trixie

[Andrew King]

Just to confirm, I have the exact same problem as reported by Frank de
Bruijn . I have tried uninstalling and
reinstalling with no improvement.

Cheers,

Andrew King

Bug#1051031: libvmime: build-depends on old libgsasl7-dev

[Gianfranco Costamagna]

Source: libvmime
Version: 0.9.8-8
Severity: Serious
tags: patch

Hello, for some reasons, libgsasl7-dev was renamed in libgsasl-dev
$ sed s/libgsasl7-dev/libgsasl-dev/g -i debian/control

Should be enough to fix the issue.

G.


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1051029: libinfinity: build-depends on old libgsasl7-dev

[Gianfranco Costamagna]

Source: libinfinity
Version: 0.7.2-1
Severity: Serious
tags: patch

Hello, for some reasons, libgsasl7-dev was renamed in libgsasl-dev
$ sed s/libgsasl7-dev/libgsasl-dev/g -i debian/control

Should be enough to fix the issue.

G.


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1051030: evolution-ews: Split package?

[Jeremy Bícha]

Source: evolution-ews
Version: 3.49.3-1

https://gitlab.gnome.org/GNOME/evolution-ews/-/commit/d28287df
suggests that we could split evolution-ews into 2 binary packages to
allow people to use GNOME Calendar with EWS via GNOME Online Accounts
without needing to have the Evolution app installed.

Thank you,
Jeremy Bícha

Bug#1051028: google-chrome-stable: Google Chrome does not respect prefers-color-scheme for webpages on KDE Plasma

[GwenDragon]

Package: google-chrome-stable
Version: 116.0.5845.140-1
Severity: important
Tags: a11y upstream
X-Debbugs-Cc: d...@gwendragon.de

Dear Maintainer,

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

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

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


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

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

Versions of packages google-chrome-stable depends on:
ii  ca-certificates 20210119
ii  dpkg1.20.12
ii  fonts-liberation1:1.07.4-11
ii  libasound2  1.2.4-1.1
ii  libatk-bridge2.0-0  2.38.0-1
ii  libatk1.0-0 2.38.0-1~bpo11+1
ii  libatspi2.0-0   2.38.0-4+deb11u1
ii  libc6   2.31-13+deb11u6
ii  libcairo2   1.16.0-5
ii  libcups22.3.3op2-3+deb11u2
ii  libcurl3-gnutls 7.74.0-1.3+deb11u7
ii  libcurl47.74.0-1.3+deb11u7
ii  libdbus-1-3 1.12.24-0+deb11u1
ii  libdrm2 2.4.104-1
ii  libexpat1   2.2.10-2+deb11u5
ii  libgbm1 20.3.5-1
ii  libglib2.0-02.66.8-1
ii  libgtk-3-0  3.24.24-4+deb11u3
ii  libnspr42:4.29-1
ii  libnss3 2:3.61-1+deb11u3
ii  libpango-1.0-0  1.46.2-3
ii  libu2f-udev 1.1.10-3
ii  libvulkan1  1.2.162.0-1
ii  libx11-62:1.7.2-1+deb11u1
ii  libxcb1 1.14-3
ii  libxcomposite1  1:0.4.5-1
ii  libxdamage1 1:1.1.5-2
ii  libxext62:1.3.3-1.1
ii  libxfixes3  1:5.0.3-2
ii  libxkbcommon0   1.0.3-2
ii  libxrandr2  2:1.5.1-1
ii  wget1.21-1+deb11u1
ii  xdg-utils   1.1.3-4.1

google-chrome-stable recommends no packages.

google-chrome-stable suggests no packages.

-- no debconf information

---

Chromium bug report  at 
https://bugs.chromium.org/p/chromium/issues/detail?id=1477568

Bug#1051027: O: emacs-lsp-haskell -- Haskell support for lsp-mode

[Bastian Germann]

Package: wnpp

The package emacs-lsp-haskell was orphaned by David Bremner with revision 
1.0.20211214-2.

Bug#1050982: pdns-recursor: leaves behind pdns user and group

[наб]

On Fri, Sep 01, 2023 at 09:55:37AM +0200, Chris Hofstaedtler wrote:
> * наб  [230901 03:18]:
> > I'd just uninstalled pdns-recursor, so this is probably due to that.
> This is by design, as deleting users (in prerm)
Well then delete them in postrm, or in postrm-on-purge, or whatever.

> is generally unsafe.
Sure, but dh_sysuser(1) says that it is safe if the home directory
doesn't exist or is empty, and this is the case here.


signature.asc
Description: PGP signature

Bug#1050001: Unwinding directory aliasing [and 3 more messages] [and 1 more messages]

[Luca Boccassi]

On Fri, 1 Sept 2023 at 09:23, Helmut Grohne  wrote:
>
> Hi Luca,
>
> At least three DDs have asked you to stop. Why do you continue?
>
> In all of your mails to this bug, I've seen little attempt at trying to
> understand other participants. In a project as large as Debian, it is to
> be expected that disagreement arises. That's not the end of the world,
> but it is important to disagree respectfully. I'm not seeing that
> respect in your interactions.

Extraordinary claims require extraordinary evidence, as the saying
goes. Asking for such evidence when it's not provided, for example for
the claim that Ansible, Puppet, Chef, Docker, Rsync and whatnot no
longer work on Debian/Ubuntu/Fedora/Arch/SUSE/CentOS/RHEL/etc, is not
disrespectful.

Bug#1042443: ITP: pathos -- Framework for heterogeneous parallel computing

[Agathe Porte]

Hi Julian,

2023-07-28 10:59 CEST, Julian Gilbey:
> Package: wnpp
> Severity: wishlist
> Owner: Julian Gilbey 
> X-Debbugs-Cc: debian-de...@lists.debian.org, Debian Python Team 
> 
>
> * Package name: pathos
>   Version : 0.3.1
>   Upstream Contact: Mike McKerns 
> * URL : https://github.com/uqfoundation/pathos
> * License : BSD-3-clause
>   Programming Lang: Python
>   Description : Framework for heterogeneous parallel computing
>
> […]
>
>
> This is a package I've started using; it provides a very effective
> framework for parallel computing, allowing for constructs that the
> standard Python library does not support.
>
> I will maintain it within the Debian Python Team.

Like python-ppft, this was already packaged in the Python team but not
uploaded: https://salsa.debian.org/python-team/packages/python-pathos

Maybe you can find inspiration in it. I think we should only keep one of
the two repos in the DPT because it can be confusing to have the same
package twice.

Agathe.

Bug#1050974: binNMU: Rebuild against curl without NSS support

[Samuel Henrique]

Control: tags -1 - moreinfo

Hello Sebastian, I'm sending this same response to all 3 bugs related to this.

> Why does that require rebuilds?

These packages have a build dependency on the virtual package
"libcurl4-dev", which is satisfiable by any variant of the curl
binaries (openssl, gnutls, nss).

Our current builds ended up linking against the nss variant, so now
that we've dropped that, a rebuild is needed for the packages to pick
either openssl or gnutls.

Related bugs:
Main one where I'm tracking all changes:
libcurl4-nss-dev: NSS support will be dropped in August 2023
https://bugs.debian.org/1038907

Bugs against the packages I'm requesting the binNMUs:
llvm-toolchain-14: links against libcurl3-nss which will be dropped in
August 2023
https://bugs.debian.org/1043550

llvm-toolchain-15: links against libcurl3-nss which will be dropped in
August 2023
https://bugs.debian.org/1043551

eg25-manager: build-depends on deprecated libcurl4-nss-dev, will be
dropped in August 2023
https://bugs.debian.org/1043547

Thank you,

-- 
Samuel Henrique 

Bug#1050762: two more minor fixes in your upstream fixes

[Boud Roukema]

hi Guido,

On Fri, 1 Sep 2023, Guido Günther wrote:


(put the bug in cc: so we have a all the bits together)


OK.


On Thu, Aug 31, 2023 at 11:09:02PM +0200, Boud Roukema wrote:

hi Guido,

I agree with closing #1050762. But upstream I still see two minor fixes
needed (unless I misunderstand something):

https://source.puri.sm/Librem5/feedbackd/-/blob/main/doc/fbd-theme-validate.rst
- 'See also' is missing  fbd-theme-validate(1)


I assume you mean `missing `feedback-themes`, I've added that.


Yes, of course. There's no point having a recursive reference (except as a joke
in a reursion-related package).


The other bug, #1050601, still looks open to me. At least the upstream main


That's why I didn't close it yet.


OK. :)


The README isn't suitable to install
though as half of the information isn't relevant on the installed
system.


I'm not sure if there's a general Debian policy on this, but plenty of
packages have the upstream README in /usr/share/doc// even though
most of the info is about how to install the package rather than what to do
with an already installed packge. I initially found this a bit confusing,
but I got used to it.

I assume that seeing the upstream README, even the INSTALL file, in
/usr/share/doc// can encourage people to get the Debian
version of the source package, and then later, if they wish, the
upstream version.  After all, making the source available is a
condition of the GPL, and making it easy for people to make that
decision is in the spirit of the GPL. README files are small text
files, so file size is not an argument to avoid them.


The corresponding bits need to move to the manpages (which is
also an opportunity to disentangle those).


OK.

Cheers
Boud

Bug#1051026: O: fbi -- Linux frame buffer image viewer

[Bastian Germann]

Package: wnpp

The package fbi was orphaned by Moritz Mühlenhoff with revision 2.10-5.

Bug#1051025: ITP: tiny-proxy -- Simple proxy server (SOCKS4, SOCKS5, HTTP tunneling) for Python

[Benjamin Drung]

Package: wnpp
Severity: wishlist
Owner: Benjamin Drung 
X-Debbugs-Cc: debian-de...@lists.debian.org, bdr...@debian.org

* Package name: tiny-proxy
  Version : 0.2.0
  Upstream Contact: Roman Snegirev 
* URL : https://github.com/romis2012/tiny-proxy
* License : Apache2
  Programming Lang: Python
  Description : Simple proxy server (SOCKS4, SOCKS5, HTTP tunneling) for 
Python

 Simple proxy (SOCKS4(a), SOCKS5(h), HTTP tunnel) server built with anyio.
 It is used for testing python-socks, aiohttp-socks and httpx-socks packages.

This package is needed for running the test suite of python-socks. The
package will be maintained as part of the Debian Python Team. Feel free
to take over the maintenance after the initial packaging (and replace me
from the Uploaders field).

-- 
Benjamin Drung
Debian & Ubuntu Developer

Bug#1051024: bookworm-pu: package igtf-policy-bundle/1.22-1~deb12u1

[Dennis van Dok]

Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: igtf-policy-bun...@packages.debian.org
Control: affects -1 + src:igtf-policy-bundle


[ Reason ]

The IGTF bundle provides important trust anchors for the Research and
Education communities. Both for reliance on the identity of servers
for compute and storage services, as well as user identification based
on personal certificates.

A recent change in the rules for S/MIME certificates[1] has urged a
change in the profiles for end user and robot certificates, effectively
by 28 August 2023. Relying parties who need to authenticate users
should install this update as soon as possible.

1. https://cabforum.org/smime-br/

More details about the change can be found on the web page of the upstream
maintainer[2].

2. 
https://www.nikhef.nl/~davidg/tcsg4/GEANT-TCSG4-private-CA-extension-20230712.pdf



[ Impact ]

Normally I would not propose to update the package in Debian stable but
this change may break authentication for some users. They could install 
the package

from unstable or backports (if available).

[ Tests ]

I normally install the packages on my own systems to try out that they work.
Since the deployment is relatively straightforward there is rarely an issue.

[ Risks ]

There are no code changes between versions, it should be safe (in fact, 
recommended)

to always install the latest version of the bundle.

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

[ Changes ]

See the upstream CHANGES file (or d/changelog).

Bug#1050256: [pkg-apparmor] Bug#1050256: autopkgtest fails on debci

[Michael Biebl]

Am 31.08.23 um 19:54 schrieb Christian Boltz:

Hello,

Am Donnerstag, 31. August 2023, 08:41:59 CEST schrieb Michael Biebl:

What we found so far is, that the AppArmor policy of lxc breaks any
systemd service using PrivateNetwork=yes or PrivateIPC=yes when being
  run under lxc (running under bookworm using the bookworm kernel).
I wonder what the best course of action is here.
Should we disable the AA policy of lxc via a stable upload of the lxc
  package until the root cause is found?

Unfortunately I know too little about AppArmor and lxc's AppArmor
policy  and my attempts to ask around for help weren't successful so
far.


Two quick hints, but let me warn you that I'm not familiar with lxc and
also didn't check the content of the lxc-autopkgtest-lxc-iomhit_*
profile.

https://github.com/lxc/lxc/issues/4333 indicates that this issue was
fixed in (much) a newer kernel - but that's probably not news to you
since you wrote that comment ;-)


That said - the DENIED log entry translates to

 unix send type=dgram,

You could try if adding this rule to the lxc-autopkgtest-lxc-iomhit_*
profile helps - but if the issue is really on the kernel side, my hope is
limited).

For testing, you could also try with a more broad
 unix send,
or even
 unix,
rule - but please don't add these broader rules to the production
profile.


I have no idea, where to add that and what specific syntax I should use.
The profile above seems to be autogenerated and I only found a binary 
file with that name in /var/cache/apparmor.


The only way to fix the container was to use the aforementioned 
`lxc.apparmor.profile = unconfined`.
I think we should do that as the breakage is rather widespread and I 
already see individual packages trying to work around that to at least 
keep debci afloat.


See e.g.:
https://salsa.debian.org/systemd-team/systemd/-/merge_requests/211
https://salsa.debian.org/debian/pdns/-/commit/637e54ef73386541086da430553b82db78266bac

or disabling the systemd hardening options completely_
https://salsa.debian.org/utopia-team/polkit/-/blob/master/debian/patches/debian/Don-t-use-PrivateNetwork-yes-for-the-systemd-unit.patch

This is not a good outcome of this and the problem will become more 
apparent with debci running on bookworm now.



Regards,
Michael



OpenPGP_signature.asc
Description: OpenPGP digital signature