Bug#1051592: Regression: Commit "netfilter: nf_tables: disallow rule addition to bound chain via NFTA_RULE_CHAIN_ID" breaks ruleset loading in linux-stable

[Arturo Borrero Gonzalez]

On Sat, Sep 16, 2023, 08:37 Salvatore Bonaccorso  wrote:

> Hi
>
> Dropping some recipients for the Debian specific handling of this
> issue. So AFAIU upstream will not consider this on src:linux side to
> be further handled and needs to be addressed in nftables.
>
> Arturo: With the patches provided I prepared (as Timo) an update
> targetting bookworm for the next point release (bug for release.d.o to
> be submitted soon).
>
> Attached is the proposed debdiff, ans as well as MR on salsa.
>
>
> https://salsa.debian.org/pkg-netfilter-team/pkg-nftables/-/merge_requests/11
> (note not touching thte salsa-ci part was deliberate, but to make the
> piuparts test one would need adjustment of the target release. But as
> itwas not done for the +deb12u1 itself, I have not touched this)
>
> The same would be needed OTOH for bullseye as well.


Hi Salvatore,

thanks for working on this. I just approved the salsa MR

Please go ahead an upload to the archive via NMU as required ASAP. I won't
be near the keyboard today.

really appreciated,

thanks, regards.

Bug#1052020: rust-tree-sitter: enters infinite loop in certain scenarios

[Jonas Smedegaard]

Source: rust-tree-sitter
Version: 0.20.10-1
Severity: important
Tags: patch upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

- From accepted MR https://github.com/tree-sitter/tree-sitter/pull/2429:
> `earlier_node` must be reset when backtracking up the tree or else
> `ts_node__prev_child` may loop infinitely on a subtree which contains
> zero-width tokens.

Please consider cherry-picking that MR until a new upstream release
comes out.

 - Jonas
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmUFVCkACgkQLHwxRsGg
ASH+rBAAnzuMEpvW8TeWYPuHpngzkbkHBBMzlQXyDas3flXwyyapV9bC5zkd0X9g
O59ogTRlMyWG3J3OKT+tOQmIfBsrn+JCtpgOIYaxu7AOUEZvIRKKWSKSClq81Yfg
P8fX04mSUu/n7MEAd1XrNuJELqVTrtBdajK3ByOJzfXIkbrE+DdiPsuLanOrdyVJ
Gf3fe6u1KSPAQh5fWr7JQQoiPVLeu6pSYNHCT4kTC8ymHH/v5ChLuDRtZ0cm1/FJ
ya7lWXEFMy+6QDALeDhtZJNVxprlT2eQut+DTu39wJC5CqbTjGzSaU7HLM8EVxHo
CSIoAXZeWH53rAwXfDJR5+7/qunnC1vN0RZP+/BVYJ0WWFfxhK4IWLF3DIdeLjNI
h+KbkiA9wqBVfhKWDgJUmH7mlvf8BO+jRqD8OSRemutRND5hUbASgLlJsUBIVANt
j2Gxl3ddgqxy+C83Gm8JgaPsCoMLBpC7jYHRWndA95OJ9Ce574hDOjFnMgxw4KKC
F4BJJw8a5S8CjAP68gcaeA4PfYcCsKsj0twv3ooiFqP+hEqqDY9Wl4s7SDRvsF4t
uzcOie2Ho0vmekKHzM5g/3+jkBp6pIkOlFKMqGXnivBdUdhzbjQR0wEdWuQwjk15
HLt3liZfnRkrFT0f9TDmmZVs6WxhHJiR9wIvDzbwRUAxqaHAYqU=
=a5Xb
-END PGP SIGNATURE-

Bug#1051980: FTBFS on i386: angle-test/bezier-test fail

[Shengjing Zhu]

Control: tag -1 + patch

Hi,

On Fri, Sep 15, 2023 at 4:27 PM Shengjing Zhu  wrote:
> The following tests FAILED:
>   2 - angle-test (Failed)
>   3 - bezier-test (Failed)

They are caused by gcc-13 which defaults to -fexcess-precision=standard for c++.

Please see the attached patch.

-- 
Shengjing Zhu


lib2geom_1.2.2-3.1.debdiff
Description: Binary data

Bug#1051374: breaks existing setups using /etc/default/mini-httpd

[Johannes Schauer Marin Rodrigues]

Hi Alexandru & Nicholas,

On Thu, 07 Sep 2023 00:58:34 +0200 Johannes Schauer Marin Rodrigues 
 wrote:
> after an upgrade to mini-httpd 1.30-4 my setup stopped working. It seems that
> this new version changed the init script for a systemd unit where the latter
> ignores the contents of /etc/default/mini-httpd.
> 
> If that is intentional and not an oversight, there should at least be a
> NEWS entry so that users upgrading to 1.30-4 learn about this breaking
> change and are also told how to convert their existing configuration to
> the new style.
> 
> If possible it would of course be nice if the systemd service would not break
> user's setups and would continue to consume /etc/default/mini-httpd.

this issue has now made the mmdebstrap jenkins job fail for 10 days in a row:

https://jenkins.debian.net/job/mmdebstrap-jenkins-worker/

Even if you do not have time to fix this soon, could you maybe advise on how
you plan to fix this? Is the behaviour change introduced by the last upload
supposed to stay and I should adjust my setup accordingly? Or will you restore
compatibility with existing setups using /etc/default/mini-httpd so that I need
to do nothing and just wait for an upload fixing this?

Thanks!

cheers, josch

signature.asc
Description: signature

Bug#1052021: bookworm-pu: package nftables/1.0.6-2+deb12u2

[Salvatore Bonaccorso]

Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: nftab...@packages.debian.org, Timo Sigurdsson 
, Arturo Borrero Gonzalez , 
car...@debian.org
Control: affects -1 + src:nftables

Dear stable release managers,

[ Reason ]
Timo Sigurdsson reported, after I released DSA 5492-1 for linux, that
in his case nftables rules won't be loaded anymore:

https://bugs.debian.org/1051592

This was tracked down with a Linux change, 0ebc1064e487 ("netfilter:
nf_tables: disallow rule addition to bound chain via
NFTA_RULE_CHAIN_ID"), which is to address CVE-2023-4147, but uncovered
an issue with nftables releases before v1.0.7 upstream. nftables is
generating incorrect bytecode, which is hit with this new kernel check
that rejects adding rules to bound chains.

Following https://lore.kernel.org/stable/ZP+bUpxJiFcmTWhy@calendula/
and further discussion on the Linux kernel mailinglists it looks this
has to be addressed in netfilter itself (arguably the change should
not break userspace, but see Florian Westphal in the thread).

[ Impact ]
Users which have such rules, running unpatched nftables but updated
the linux kernel due to address security fixes (and later to be
included in the point release as well) are left without loaded
nftables rules.

[ Tests ]
Explicit tests with the rules provided by Timo to verify they
correctly get loaded with updated nftables userland and the updated
kernel.

[ Risks ]
Pablo Neira Ayuso provided the series of commits required to address
the issue. They apply cleanly for the bookworm version.

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

[ Changes ]
See above.

[ Other info ]
Unfortunately this will be needed as well for bullseye, but the
version of nftables there is substantial older, I have not yet
verified how the patches apply, but will need to be asked anyway in a
separate bullseye-pu update request.

Regards,
Salvatore
diff -Nru nftables-1.0.6/debian/changelog nftables-1.0.6/debian/changelog
--- nftables-1.0.6/debian/changelog 2023-06-20 16:55:52.0 +0200
+++ nftables-1.0.6/debian/changelog 2023-09-16 07:47:15.0 +0200
@@ -1,3 +1,13 @@
+nftables (1.0.6-2+deb12u2) bookworm; urgency=medium
+
+  * [136245a] Fix incorrect bytecode generation hit with new kernel check that
+rejects adding rules to bound chains (Closes: #1051592)
+- rule: add helper function to expand chain rules intoi commands
+- rule: expand standalone chain that contains rules
+- src: expand table command before evaluation
+
+ -- Salvatore Bonaccorso   Sat, 16 Sep 2023 07:47:15 +0200
+
 nftables (1.0.6-2+deb12u1) bookworm; urgency=medium
 
   * [7edf72e] d/patches: add 0001-debian-bug-1038724.patch (Closes: #1038724)
diff -Nru 
nftables-1.0.6/debian/patches/rule-add-helper-function-to-expand-chain-rules-into-.patch
 
nftables-1.0.6/debian/patches/rule-add-helper-function-to-expand-chain-rules-into-.patch
--- 
nftables-1.0.6/debian/patches/rule-add-helper-function-to-expand-chain-rules-into-.patch
1970-01-01 01:00:00.0 +0100
+++ 
nftables-1.0.6/debian/patches/rule-add-helper-function-to-expand-chain-rules-into-.patch
2023-09-16 07:47:15.0 +0200
@@ -0,0 +1,82 @@
+From 4e5b0a64227dde250f94bec45b3fb127d78b7fd2 Mon Sep 17 00:00:00 2001
+From: Pablo Neira Ayuso 
+Date: Mon, 6 Feb 2023 15:28:40 +0100
+Subject: [PATCH 1/3,nft] rule: add helper function to expand chain rules intoi
+ commands
+
+[ upstream commit 784597a4ed63b9decb10d74fdb49a1b021e22728 ]
+
+This patch adds a helper function to expand chain rules into commands.
+This comes in preparation for the follow up patch.
+
+Signed-off-by: Pablo Neira Ayuso 
+---
+ src/rule.c | 39 ++-
+ 1 file changed, 22 insertions(+), 17 deletions(-)
+
+diff --git a/src/rule.c b/src/rule.c
+index 1402210acd8d..43c6520517ce 100644
+--- a/src/rule.c
 b/src/rule.c
+@@ -1310,13 +1310,31 @@ void cmd_add_loc(struct cmd *cmd, uint16_t offset, 
const struct location *loc)
+   cmd->num_attrs++;
+ }
+ 
++static void nft_cmd_expand_chain(struct chain *chain, struct list_head 
*new_cmds)
++{
++  struct rule *rule;
++  struct handle h;
++  struct cmd *new;
++
++  list_for_each_entry(rule, &chain->rules, list) {
++  memset(&h, 0, sizeof(h));
++  handle_merge(&h, &rule->handle);
++  if (chain->flags & CHAIN_F_BINDING) {
++  rule->handle.chain_id = chain->handle.chain_id;
++  rule->handle.chain.location = chain->location;
++  }
++  new = cmd_alloc(CMD_ADD, CMD_OBJ_RULE, &h,
++  &rule->location, rule_get(rule));
++  list_add_tail(&new->list, new_cmds);
++  }
++}
++
+ void nft_cmd_expand(struct

Bug#1052022: ncdu: Update to latest LTS (C) version

[Bastian Germann]

Source: ncdu
Version: 1.18-0.2

Please update to the latest LTS version which is 1.19 currently.

Bug#1051592: Regression: Commit "netfilter: nf_tables: disallow rule addition to bound chain via NFTA_RULE_CHAIN_ID" breaks ruleset loading in linux-stable

[Salvatore Bonaccorso]

Hi ARturo,

On Sat, Sep 16, 2023 at 09:02:34AM +0200, Arturo Borrero Gonzalez wrote:
> On Sat, Sep 16, 2023, 08:37 Salvatore Bonaccorso  wrote:
> 
> > Hi
> >
> > Dropping some recipients for the Debian specific handling of this
> > issue. So AFAIU upstream will not consider this on src:linux side to
> > be further handled and needs to be addressed in nftables.
> >
> > Arturo: With the patches provided I prepared (as Timo) an update
> > targetting bookworm for the next point release (bug for release.d.o to
> > be submitted soon).
> >
> > Attached is the proposed debdiff, ans as well as MR on salsa.
> >
> >
> > https://salsa.debian.org/pkg-netfilter-team/pkg-nftables/-/merge_requests/11
> > (note not touching thte salsa-ci part was deliberate, but to make the
> > piuparts test one would need adjustment of the target release. But as
> > itwas not done for the +deb12u1 itself, I have not touched this)
> >
> > The same would be needed OTOH for bullseye as well.
> 
> 
> Hi Salvatore,
> 
> thanks for working on this. I just approved the salsa MR
> 
> Please go ahead an upload to the archive via NMU as required ASAP. I won't
> be near the keyboard today.
> 
> really appreciated,

Thank to you! I just filled the request for the release team, and
uploaded the version (following the procedure where one is almost sure
that the upload can be accepted as is).

I have as well pushed a signed tag to my repo in case you want to
fetch that as well.

Next we need to look as well to bullseye, feat that it will be more
complex there.

Regards,
Salvatore

Bug#1036450: The network-online patch is missing

[Joachim Zobel]

It was applied upstream (thanks for that) but it did not make it into
the release 2.0.17-3.

Since I am in the lucky situation that it currently happens always on
my laptop I could verify that the fix is working.

Bug#1036450: Correction

[Joachim Zobel]

Correction: The network-online patch was not applied upstream, but in
LocutusOfBorg/mosquitto.

Bug#1051374: breaks existing setups using /etc/default/mini-httpd

[Johannes Schauer Marin Rodrigues]

Hi,

Quoting Johannes Schauer Marin Rodrigues (2023-09-16 09:23:43)
> On Thu, 07 Sep 2023 00:58:34 +0200 Johannes Schauer Marin Rodrigues
>  wrote:
> > after an upgrade to mini-httpd 1.30-4 my setup stopped working. It seems 
> > that
> > this new version changed the init script for a systemd unit where the latter
> > ignores the contents of /etc/default/mini-httpd.
> > 
> > If that is intentional and not an oversight, there should at least be a
> > NEWS entry so that users upgrading to 1.30-4 learn about this breaking
> > change and are also told how to convert their existing configuration to
> > the new style.
> > 
> > If possible it would of course be nice if the systemd service would not 
> > break
> > user's setups and would continue to consume /etc/default/mini-httpd.
> 
> this issue has now made the mmdebstrap jenkins job fail for 10 days in a row:
> 
> https://jenkins.debian.net/job/mmdebstrap-jenkins-worker/
> 
> Even if you do not have time to fix this soon, could you maybe advise on how
> you plan to fix this? Is the behaviour change introduced by the last upload
> supposed to stay and I should adjust my setup accordingly? Or will you restore
> compatibility with existing setups using /etc/default/mini-httpd so that I
> need to do nothing and just wait for an upload fixing this?

I asked in #debian-systemd and the fix could be as simple as setting the
following in the .service file:

EnvironmentFile=-/etc/default/mini-httpd

Can you confirm?

Thanks!

cheers, josch

signature.asc
Description: signature

Bug#1052023: libglib2.0-0: gnome-shell crashed while browsing YouTube or LinkedIn in Firefox

[Amr Ibrahim]

Package: libglib2.0-0
Version: 2.78.0-1
Severity: important
Tags: upstream

Dear Maintainer,

I have filed this bug upstream against gnome-shell, then it turned out to be a
duplicate bug in glib. A stack trace is attached in the upstream bug report.

Please cherry-pick the fix in glib to Debian unstable.

https://gitlab.gnome.org/GNOME/glib/-/issues/3113

Best,
Amr


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

Kernel: Linux 6.4.0-4-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 libglib2.0-0 depends on:
ii  libc6 2.37-8
ii  libffi8   3.4.4-1
ii  libmount1 2.39.2-1
ii  libpcre2-8-0  10.42-4
ii  libselinux1   3.5-1
ii  zlib1g1:1.2.13.dfsg-3

Versions of packages libglib2.0-0 recommends:
ii  libglib2.0-data   2.78.0-1
ii  shared-mime-info  2.2-1
ii  xdg-user-dirs 0.18-1

Versions of packages libglib2.0-0 suggests:
pn  low-memory-monitor  

-- no debconf information

Bug#1052024: RM: grun -- RoQA; dead upstream; orphaned; depends on gtk2

[Bastian Germann]

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

grun is dead upstream, orphaned, and depends on gtk2. Please remove it.
There should be enought alternatives in Debian.

Bug#1043124: The related openzfs issue

[grin]

6.5 under review:
https://github.com/openzfs/zfs/pull/15268

(Completely unrelated, but browsing the issues it popped up that encryption is 
very broken above 6.3,
and it has been somewhat broken on older kernels too; not one people lost their 
data due to upgrading
beyond 6.3, so beware. 
https://github.com/openzfs/zfs/issues/15275
https://github.com/openzfs/zfs/issues/15140)

Bug#1051051: rustc-mozilla 1.63.0+dfsg1-2~deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1051051 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: rustc-mozilla
Version: 1.63.0+dfsg1-2~deb11u1

Explanation: new "upstream" version, to support newer firefox-esr builds

Bug#1051979: Do not suggest APT::Default-Release setting

[Osamu Aoki]

Hi,

Thank you for careful review.


On Fri, 2023-09-15 at 15:01 +0700, Max Nikulin wrote:
> Package: debian-reference
> Version: 2.100
> 
> The "2.7.7. Tweaking candidate version with apt-pinning" section
> in "Chapter 2. Debian package management" recommends
> 
> > The target release archive can be set by several methods.
> > 
> > - "/etc/apt/apt.conf" configuration file with "APT::Default-Release
> > "stable";" line
> > - command line option, e.g., "apt-get install -t testing some-package"
> 
> https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_tweaking_candidate_version
> 
> Unfortunately "APT::Default-Release "stable";" prevents installing of 
> updates from stable-security and stable-updates repositories. So this 
> option should be either just dropped or a warning should be added to 
> alert users who remembers it from previous release.

I see your concern.  I merely meant to point out "APT::Default-Release
> > "...";" line sets "Default-Release".  I don't meant to use it with "stable"

So my first thought was replace it with:

- Release definition in "/etc/apt/apt.conf" configuration file started with
"APT::Default-Release"

But As I read complicationa it causes from your messages, let's drop it.  I
don't use it anyway.

Bug#1052025: redmine: upgrade from bullseye(-backports) to bookworm fails

[wim]

Package: redmine
Version: 5.0.4-5
Severity: normal
X-Debbugs-Cc: wim.bert...@ucll.be

Hello,

upgrading a relative pristine redmine instance from deb 11 to 12 fails 
with the following:

debian 11: redmine via bullseye-backports
debian 12: apt upgrade --without-new-pkgs step

"
Do you want to continue? [Y/n] 
Setting up redmine (5.0.4-5) ...
Don't run Bundler as root. Bundler can ask for sudo if it is needed, and 
installing your bundle as root
will break this application for all non-root users on this machine.
Could not find gem 'net-imap' in cached gems or installed locally.
dpkg: error processing package redmine (--configure):
 installed redmine package post-installation script subprocess returned error 
exit status 1
Errors were encountered while processing:
 redmine
E: Sub-process /usr/bin/dpkg returned an error code (1)
"


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

Kernel: Linux 5.10.0-25-cloud-amd64 (SMP w/1 CPU thread)
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 redmine depends on:
ii  dbconfig-common 2.0.24
ii  debconf [debconf-2.0]   1.5.82
ii  libjs-chart.js  3.9.1+~0.2.1-2
ii  libjs-jquery3.6.1+dfsg+~3.5.14-1
ii  libjs-jquery-ui 1.13.2+dfsg-1
ii  libjs-raphael   2.3.0-4
ii  libruby2.7 [ruby-csv]   2.7.4-1+deb11u1
ii  redmine-pgsql   5.0.4-5
ii  ruby1:2.7+2
ii  ruby-actionpack-action-caching  1.2.2-1
ii  ruby-actionpack-xml-parser  2.0.1-4
ii  ruby-addressable2.8.1-1
ii  ruby-bundler2.3.15-2
ii  ruby-coderay1.1.3-8
ii  ruby-commonmarker   0.23.6-1~bpo11+1
ii  ruby-csv3.2.2-1
ii  ruby-html-pipeline  2.14.3-1
ii  ruby-i18n   1.10.0-2
ii  ruby-jquery-rails   4.3.5-4
ii  ruby-mail   2.7.1+dfsg1-2
ii  ruby-marcel 1.0.1+dfsg-2
ii  ruby-mini-magick4.11.0-1
ii  ruby-mini-mime  1.1.1-2
ii  ruby-mocha  1.16.1-1
ii  ruby-net-ldap   0.17.0-1
ii  ruby-nokogiri   1.13.5+dfsg-2~bpo11+1
ii  ruby-rack   2.2.6.4-1
ii  ruby-rack-test  2.0.2-2
ii  ruby-rails  2:6.1.7.3+dfsg-1
ii  ruby-rails-dom-testing  2.0.3-4
ii  ruby-rails-observers0.1.5-1.1
ii  ruby-rbpdf  1.20.1-2
ii  ruby-redcarpet  3.5.1-1
ii  ruby-request-store  1.5.1-1
ii  ruby-rmagick2.16.0-7
ii  ruby-roadie 5.1.0-1
ii  ruby-roadie-rails   3.0.0-1
ii  ruby-rotp   6.2.0-2
ii  ruby-rouge  3.30.0-2
ii  ruby-rqrcode1.2.0-1
ii  ruby-sanitize   6.0.0-1.1
ii  ruby-task-list  2.3.2-2
ii  ruby-zip2.3.2-1

Versions of packages redmine recommends:
ii  passenger  5.0.30-1.2+deb11u1

Versions of packages redmine suggests:
pn  bzr 
pn  cvs 
pn  darcs   
ii  git 1:2.30.2-1+deb11u2
pn  mercurial   
pn  ruby-fcgi   
ii  subversion  1.14.1-3+deb11u1

-- debconf information:
  redmine/instances/default/passwords-do-not-match:
  redmine/instances/default/dbconfig-reinstall: false
  redmine/instances/default/pgsql/method: TCP/IP
  redmine/instances/default/pgsql/manualconf:
  redmine/instances/default/db/app-user: redmine/instances/default@localhost
  redmine/instances/default/pgsql/authmethod-user: password
  redmine/current-instances: default
  redmine/default-language: en
* redmine/instances/default/database-type: pgsql
  redmine/instances/default/missing-db-package-error: abort
  redmine/instances/default/db/dbname: redmine_default
  redmine/instances/default/pgsql/authmethod-admin: ident
  redmine/instances/default/remote/port:
  redmine/instances/default/pgsql/changeconf: false
* redmine/instances/default/remote/host: localhost
  redmine/instances/default/internal/skip-preseed: true
  redmine/instances/default/upgrade-error: abort
  redmine/instances/default/install-error: abort
  redmine/instances/default/dbconfig-remove: true
  redmine/instances/default/remote/newhost: localhost
  redmine/instances/default/internal/reconfiguring: false
  redmine/instances/default/dbconfig-upgrade: true
* redmine/instances/default/dbconfig-install: true
  redmine/instances/default/purge: false
  redmine/instances/default/default-language: en
  redmine/instances/default/remove-error: abort
  redmine/instances/default/pgsql/admin-user: postgres
  redmine/instances/default/pgsql/no-empty-passwords:
  redmine/instances/default/upgrade-b

Bug#1052026: transition: thrift

[GCS]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Control: affects -1 + src:thrift

Hi RMs,

Small transition to 0.19.0 release of thrift. The only reverse
dependency is gnuradio which builds fine with the new thrift release.
There are two things to consider. First is that gnuradio is also
involved in the fmtlib, qwt and boost1.81 transitions as well. Then it
is scheduled to be removed from testing on 14th of October due to
depending on bladerf which has an open RC bug [1].with a patch since
the end of August.

Thanks for considering,
Laszlo/GCS
[1] https://bugs.debian.org/1050943

Bug#1052027: bullseye-pu: package cargo-mozilla/0.66.0+ds1-1~deb11u1

[Emilio Pozuelo Monfort]

Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: pkg-rust-maintain...@alioth-lists.debian.net

Hi,

Following up on #1051051, this updates cargo-mozilla for the upcoming
Firefox ESR 115. Just like for rustc-mozilla, the risk here is small
as this package is only used to build firefox-esr and thunderbird.

I have used the resulting package to successfully build and test
firefox-esr 115.0.2 on bullseye.

Attached is the diff from 0.66 itself so that the changes in the
backport are easier to review. A diff from 0.47 is not attached.

Cheers,
Emilio
diff -ruNp cargo-0.66.0+ds1/debian/cargo.bash-completion 
cargo-mozilla-0.66.0+ds1/debian/cargo.bash-completion
--- cargo-0.66.0+ds1/debian/cargo.bash-completion   2023-01-11 
18:55:09.0 +0100
+++ cargo-mozilla-0.66.0+ds1/debian/cargo.bash-completion   1970-01-01 
01:00:00.0 +0100
@@ -1 +0,0 @@
-src/etc/cargo.bashcomp.sh cargo
diff -ruNp cargo-0.66.0+ds1/debian/cargo.dirs 
cargo-mozilla-0.66.0+ds1/debian/cargo.dirs
--- cargo-0.66.0+ds1/debian/cargo.dirs  2023-01-11 18:55:09.0 +0100
+++ cargo-mozilla-0.66.0+ds1/debian/cargo.dirs  1970-01-01 01:00:00.0 
+0100
@@ -1 +0,0 @@
-usr/bin
diff -ruNp cargo-0.66.0+ds1/debian/cargo-doc.docs 
cargo-mozilla-0.66.0+ds1/debian/cargo-doc.docs
--- cargo-0.66.0+ds1/debian/cargo-doc.docs  2023-01-11 18:55:09.0 
+0100
+++ cargo-mozilla-0.66.0+ds1/debian/cargo-doc.docs  1970-01-01 
01:00:00.0 +0100
@@ -1 +0,0 @@
-target/doc
diff -ruNp cargo-0.66.0+ds1/debian/cargo.manpages 
cargo-mozilla-0.66.0+ds1/debian/cargo.manpages
--- cargo-0.66.0+ds1/debian/cargo.manpages  2023-01-11 18:55:09.0 
+0100
+++ cargo-mozilla-0.66.0+ds1/debian/cargo.manpages  1970-01-01 
01:00:00.0 +0100
@@ -1,2 +0,0 @@
-src/etc/man/cargo-*.1
-src/etc/man/cargo.1
diff -ruNp cargo-0.66.0+ds1/debian/cargo-mozilla.bash-completion 
cargo-mozilla-0.66.0+ds1/debian/cargo-mozilla.bash-completion
--- cargo-0.66.0+ds1/debian/cargo-mozilla.bash-completion   1970-01-01 
01:00:00.0 +0100
+++ cargo-mozilla-0.66.0+ds1/debian/cargo-mozilla.bash-completion   
2023-01-11 18:55:09.0 +0100
@@ -0,0 +1 @@
+src/etc/cargo.bashcomp.sh cargo
diff -ruNp cargo-0.66.0+ds1/debian/cargo-mozilla.dirs 
cargo-mozilla-0.66.0+ds1/debian/cargo-mozilla.dirs
--- cargo-0.66.0+ds1/debian/cargo-mozilla.dirs  1970-01-01 01:00:00.0 
+0100
+++ cargo-mozilla-0.66.0+ds1/debian/cargo-mozilla.dirs  2023-01-11 
18:55:09.0 +0100
@@ -0,0 +1 @@
+usr/bin
diff -ruNp cargo-0.66.0+ds1/debian/cargo-mozilla-doc.docs 
cargo-mozilla-0.66.0+ds1/debian/cargo-mozilla-doc.docs
--- cargo-0.66.0+ds1/debian/cargo-mozilla-doc.docs  1970-01-01 
01:00:00.0 +0100
+++ cargo-mozilla-0.66.0+ds1/debian/cargo-mozilla-doc.docs  2023-01-11 
18:55:09.0 +0100
@@ -0,0 +1 @@
+target/doc
diff -ruNp cargo-0.66.0+ds1/debian/cargo-mozilla.manpages 
cargo-mozilla-0.66.0+ds1/debian/cargo-mozilla.manpages
--- cargo-0.66.0+ds1/debian/cargo-mozilla.manpages  1970-01-01 
01:00:00.0 +0100
+++ cargo-mozilla-0.66.0+ds1/debian/cargo-mozilla.manpages  2023-01-11 
18:55:09.0 +0100
@@ -0,0 +1,2 @@
+src/etc/man/cargo-*.1
+src/etc/man/cargo.1
diff -ruNp cargo-0.66.0+ds1/debian/changelog 
cargo-mozilla-0.66.0+ds1/debian/changelog
--- cargo-0.66.0+ds1/debian/changelog   2023-01-11 18:55:09.0 +0100
+++ cargo-mozilla-0.66.0+ds1/debian/changelog   2023-07-30 10:37:52.0 
+0200
@@ -1,3 +1,15 @@
+cargo-mozilla (0.66.0+ds1-1~deb11u1) bullseye; urgency=medium
+
+  * Non-maintainer upload.
+  * Backport to bullseye as cargo-mozilla.
+  * Build-dep on rustc-mozilla.
+  * Don't build the doc package.
+  * Vendor libgit2 1.5.1, the system one is too old.
+  * Build-dep on libpcre3-dev, for libgit2.
+  * Don't use namespaced features.
+
+ -- Emilio Pozuelo Monfort   Sun, 30 Jul 2023 10:37:52 +0200
+
 cargo (0.66.0+ds1-1) unstable; urgency=medium
 
   [ Fabian Grünbichler ]
diff -ruNp cargo-0.66.0+ds1/debian/control 
cargo-mozilla-0.66.0+ds1/debian/control
--- cargo-0.66.0+ds1/debian/control 2023-01-11 18:55:09.0 +0100
+++ cargo-mozilla-0.66.0+ds1/debian/control 2023-07-30 10:37:52.0 
+0200
@@ -1,4 +1,4 @@
-Source: cargo
+Source: cargo-mozilla
 Section: devel
 Maintainer: Rust Maintainers 
 Uploaders: Luca Bruno ,
@@ -10,17 +10,18 @@ Priority: optional
 Build-Depends:
  debhelper (>= 12~),
  dpkg-dev (>= 1.17.14),
- cargo:native(>= 0.56.0),
- rustc:native(>= 1.63),
- libstd-rust-dev (>= 1.63),
+ cargo-mozilla:native(>= 0.56.0),
+ rustc-mozilla:native(>= 1.63),
+ libstd-rust-mozilla-dev (>= 1.63),
  pkg-config,
  bash-completion,
  python3:native,
  libcurl4-gnutls-dev | libcurl4-openssl-dev,
  libssh2-1-dev,
- libgit2-dev (>= 1.5.0),
- libgit2-dev (<< 1.6~~),
+# libgit2-dev (>= 1.5.0),
+# libgit2-dev (<< 1.6~~),
  libhttp-parser-dev,
+ libpcre3-dev,
  libssl-dev,
  zlib1g-dev

Bug#1051251: /usr/sbin/grub-mkconfig: 300: /etc/grub.d/25_bli: not found due to wrong shell location

[Drew Parsons]

Source: grub2
Version: 2.12~rc1-7
Followup-For: Bug #1051251
Control: severity 1051251 critical

This is a critical bug.  apt fails on this bug early in its run, and
therefore this one bug is preventing *every* *other* package from updating.

If the fix can't be uploaded to unstable, then please upload to
experimental.




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

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

Bug#1050709: tar-ignore debian/source/options

[Sean Whitton]

Hello Niels,

On Mon 28 Aug 2023 at 06:56pm +02, Niels Thykier wrote:

> So this is a common pattern in my packages although it sometimes appears in
> d/s/local-options rather than d/s/options.
>
> Basically, the issue is when you have something you want to have locally, not
> in git and also not in the archive.  In one my other packages, I have a
> "local" directory filled with local work items (including a full copy of the
> sudo deb package for testing purposes). Here the "local" directory is listed
> both in .gitignore and in "tar-ignore", because I do not want it in git nor in
> the archive when I do an upload.
>
> To solve this, I add `tar-ignore=...` (for native packages) to
> debian/source/(local-)options.  However, if you add that option, you end up
> with the entire *.git* directory in the tarball.  To avoid that, I add the
> `tar-ignore` on its own to get the sane defaults back.
>
> This then breaks dgit leading to this bug, which is kind of a catch-22 if you
> want local specific things (IDE files or local prototype stuff) that you
> guarantee is excluded from git and dpkg-source automatically and also support
> dgit at the same time.

dgit will never let you accidentally perform an upload containing
something that's in the tree but not in git, and you can use
.git/info/exclude as a local way to ensure it's never in git.  So a
simple policy of always doing uploads with dgit might achieve what you
want, without introducing all these deltas between source packages, git,
local trees etc.?

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#1051251: /usr/sbin/grub-mkconfig: 300: /etc/grub.d/25_bli: not found due to wrong shell location

[Julian Andres Klode]

Control: severity -1 wishlist

On Sat, Sep 16, 2023 at 10:36:39AM +0200, Drew Parsons wrote:
> Source: grub2
> Version: 2.12~rc1-7
> Followup-For: Bug #1051251
> Control: severity 1051251 critical
> 
> This is a critical bug.  apt fails on this bug early in its run, and
> therefore this one bug is preventing *every* *other* package from updating.

You have literally hacked around the dependencies of the packages by
inserting a fake package to pretend to have merged-usr installed to be
able to maintain a file system layout the project has decided is no
longer supported.

FWIW, if you people keep being annoying I (with my apt head on) am
just going to deliberately make apt error out and refuse any operation
on unmerged systems.

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#1006202: mesa-amber status

[Alexis Murzeau]

Hi,

I second this too as I use a i5 3230m as main computer.
I don't see mesa-amber in NEW, was it rejected with some reason ?

--
Alexis Murzeau
PGP: B7E6 0EBB 9293 7B06 BDBC  2787 E7BD 1904 F480 937F |

Bug#1051006: smuxi: useless empty package

[Bastian Germann]

Control: severity -1 normal

The package is not migrating even though it is fixed.

Bug#1052006: linux-image-6.5.0-1-amd64 breaks X on amd GPU

[Bastian Blank]

Control: tag -1 moreinfo

Hi Klaus

On Fri, Sep 15, 2023 at 10:18:55PM +0100, Klaus Ethgen wrote:
> Booting with the new kernel makes the display (1920x1200) heavily
> flckering, diplaying two times the same one above the other and only
> displaying about 1/4 of the screen smashed together on the left border
> of the screen.

Does it work with native resolution?  Does it work with Wayland?

> Note that the broken setup has 3 lines of 3840x2400, althogh I use
> 1920x1200 as resolution.

With different refresh frequencies, so nothing uncommon.

> 3840x2400 is no usable resolution as the display content is much to
> small to be usable.

That's why we now have scaling and don't need to play with resolutions.

Bastian

-- 
The idea of male and female are universal constants.
-- Kirk, "Metamorphosis", stardate 3219.8

Bug#1051251: /usr/sbin/grub-mkconfig: 300: /etc/grub.d/25_bli: not found due to wrong shell location

[Drew Parsons]

Control: severity -1 critical


On 2023-09-16 11:43, Julian Andres Klode wrote:

Control: severity -1 wishlist

On Sat, Sep 16, 2023 at 10:36:39AM +0200, Drew Parsons wrote:

Source: grub2
Version: 2.12~rc1-7
Followup-For: Bug #1051251
Control: severity 1051251 critical

This is a critical bug.  apt fails on this bug early in its run, and
therefore this one bug is preventing *every* *other* package from 
updating.


You have literally hacked around the dependencies of the packages by
inserting a fake package to pretend to have merged-usr installed to be
able to maintain a file system layout the project has decided is no
longer supported.


I have done literally nothing to change merged-usr status, apart from 
regularly upgrade packages as they come along.



FWIW, if you people keep being annoying I (with my apt head on) am
just going to deliberately make apt error out and refuse any operation
on unmerged systems.


We are annoyed.  Please do what you must do.

Bug#1051563: Backporting mutt patches to Debian Buster

[Utkarsh Gupta]

Hi Chris,

On Fri, Sep 15, 2023 at 8:09 PM Chris Frey  wrote:
> Attached is a patch that applies to the unpackaged sources of Debian Buster's
> version of mutt 1.10.
>
> It includes 3 patches:
>
> upstream/Fix-rfc2047-base64-decoding-to-abort-on-illegal-char.patch
> debian-specific/Check-for-NULL-userhdrs.patch
> debian-specific/Fix-write_one_header-illegal-header-check.patch
>
> First one applied from Bullseye.  The other two I modified slightly
> to match the older sources.

Many thanks, as usual. I'll look into it and let you know if we hit a
bump backporting it.


- u

Bug#1051251: /usr/sbin/grub-mkconfig: 300: /etc/grub.d/25_bli: not found due to wrong shell location

[Drew Parsons]

On 2023-09-16 12:12, Julian Andres Klode wrote:

Control: severity -1 wishlist

On Sat, Sep 16, 2023 at 12:01:36PM +0200, Drew Parsons wrote:

Control: severity -1 critical


On 2023-09-16 11:43, Julian Andres Klode wrote:
> Control: severity -1 wishlist
>
> On Sat, Sep 16, 2023 at 10:36:39AM +0200, Drew Parsons wrote:
> > Source: grub2
> > Version: 2.12~rc1-7
> > Followup-For: Bug #1051251
> > Control: severity 1051251 critical
> >
> > This is a critical bug.  apt fails on this bug early in its run, and
> > therefore this one bug is preventing *every* *other* package from
> > updating.
>
> You have literally hacked around the dependencies of the packages by
> inserting a fake package to pretend to have merged-usr installed to be
> able to maintain a file system layout the project has decided is no
> longer supported.

I have done literally nothing to change merged-usr status, apart from
regularly upgrade packages as they come along.


This is not true. init-system-helpers depends on usrmerge | merged-usr, 
and

merged-usr only installs if your usr is merged, and usrmerge will
convert your system to the supported layout.

And that package is essential.

The only way you end up in that situation is by messing with the
package management system so that you generate a fake package using
equivs or similar that Provides: usrmerge or merged-usr, or using
the buildd workaround.

Maybe you have followed the warnigns from dpkg that were added by
his hostile maintainer declaring merged-usr to be unsupported and
asking you to run a dangerous dpkg-fsys-usrunmess to mess up your
system.

Bug#1051251: /usr/sbin/grub-mkconfig: 300: /etc/grub.d/25_bli: not found due to wrong shell location

[Julian Andres Klode]

Control: severity -1 wishlist

On Sat, Sep 16, 2023 at 12:01:36PM +0200, Drew Parsons wrote:
> Control: severity -1 critical
> 
> 
> On 2023-09-16 11:43, Julian Andres Klode wrote:
> > Control: severity -1 wishlist
> > 
> > On Sat, Sep 16, 2023 at 10:36:39AM +0200, Drew Parsons wrote:
> > > Source: grub2
> > > Version: 2.12~rc1-7
> > > Followup-For: Bug #1051251
> > > Control: severity 1051251 critical
> > > 
> > > This is a critical bug.  apt fails on this bug early in its run, and
> > > therefore this one bug is preventing *every* *other* package from
> > > updating.
> > 
> > You have literally hacked around the dependencies of the packages by
> > inserting a fake package to pretend to have merged-usr installed to be
> > able to maintain a file system layout the project has decided is no
> > longer supported.
> 
> I have done literally nothing to change merged-usr status, apart from
> regularly upgrade packages as they come along.

This is not true. init-system-helpers depends on usrmerge | merged-usr, and
merged-usr only installs if your usr is merged, and usrmerge will
convert your system to the supported layout.

And that package is essential.

The only way you end up in that situation is by messing with the
package management system so that you generate a fake package using
equivs or similar that Provides: usrmerge or merged-usr, or using
the buildd workaround. 

Maybe you have followed the warnigns from dpkg that were added by
his hostile maintainer declaring merged-usr to be unsupported and
asking you to run a dangerous dpkg-fsys-usrunmess to mess up your
system.

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#1051251: /usr/sbin/grub-mkconfig: 300: /etc/grub.d/25_bli: not found due to wrong shell location

[Drew Parsons]

apologies for the preceding empty message.  Sent button pressed by 
accident.


On 2023-09-16 12:12, Julian Andres Klode wrote:


Maybe you have followed the warnigns from dpkg that were added by
his hostile maintainer declaring merged-usr to be unsupported and
asking you to run a dangerous dpkg-fsys-usrunmess to mess up your
system.


I will accept that as a workaround.  dpkg-fsys-usrunmess is indeed 
installed


If there is a war between dpkg and apt, do we need to invoke the 
Technical Committee to either force removal or dpkg-fsys-usrunmess or 
force uploading fixes like the one to this bug ?  It sounds like it is 
needed.

Bug#1051251: /usr/sbin/grub-mkconfig: 300: /etc/grub.d/25_bli: not found due to wrong shell location

[Drew Parsons]

On 2023-09-16 12:16, Drew Parsons wrote:
apologies for the preceding empty message.  Sent button pressed by 
accident.


On 2023-09-16 12:12, Julian Andres Klode wrote:


Maybe you have followed the warnigns from dpkg that were added by
his hostile maintainer declaring merged-usr to be unsupported and
asking you to run a dangerous dpkg-fsys-usrunmess to mess up your
system.


I will accept that as a workaround.  dpkg-fsys-usrunmess is indeed 
installed


If there is a war between dpkg and apt, do we need to invoke the
Technical Committee to either force removal or dpkg-fsys-usrunmess or
force uploading fixes like the one to this bug ?  It sounds like it is
needed.


I see now it has been resolved. dpkg-fsys-usrunmess is no longer 
available, it is now marked as a "local or obselete" package.


Perhaps the most practical resolution is to mark
  apt Conflicts: dpkg-fsys-usrunmess  ?

Bug#1052028: please update to pydantic 2.x

[Timo Röhling]

Source: pydantic
Version: 1.10.4-1
Severity: wishlist
X-Debbugs-Cc: debian-pyt...@lists.debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer,

I would like to have pydantic updated to the latest 2.x major release,
because rstcheck depends on it.

The 2.x API has some breaking changes, but according to the pydantic
README, version 1.10.4 is shipped as pydantic.v1 legacy module.
Therefore, any reverse dependency which is incompatible with the 2.x API
can be fixed trivially at import level.

As pydantic is only weakly team managed, I am submitting this wishlist
bug, but I am willing to do the grunt work for this and provide the
necessary team uploads.

I cc'd the Python team mailing list as advance notice for the
maintainers of affected reverse dependencies.


Cheers
Timo


-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmUFgtIACgkQ+C8H+466
LVlPWgwA48KvUKxcwuy9DEQKH6jPaa7g8vNJXIz7EdXnqhUJAVUlDV+7nJ4T5+rJ
aesvqHpC6NE76Okkm76UhPk3wwCvsvoww+Ib4OHMKfYt9f1QS3FvQvMRSQWZrUpq
+AB0nPfUxc5HepCcH+prshDeUkJ5QmotqeMZTmDbdmZmpHyyF1hAz+0BfgXuJlSg
Gpyew8M/qm4IiN04wdG34JwyVTSGutxcHNV8o4cnupp7TuiYpLFVDVYkeJkdWYq1
vFIH80pHfTvDX+2Gk+KlfJA4tcPxvMu2sZm3S4OvIYSq97FeVWLHBUiZmNYboXIe
doiAC87EFEo/NTjv1xFXzjKYz27ae/XTpTVgS2FD2U1YUYyYUtr88423QrtvUGnz
gDiz+efixPsdy3H26yH1x/Y6qRLQWnag3dyXjPx3xUZgDe0Merhrm5C9Djk8ZKD4
9WuSLNVwXit3n6MMZRZHIdNO/QVxYyFsPSobytXRluroxWVYhOYeSH+uEOhvBYLl
qhf317wZ
=6qsd
-END PGP SIGNATURE-

Bug#1052029: c-evo-dh: depends on deprecated GTK 2

[Bastian Germann]

Source: c-evo-dh
Version: 1.7-1
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gtk2 oldlibs
Control: block 947713 by -1

This package has Build-Depends on GTK 2 (libgtk2.0-dev), or produces
binary packages with a Depends on GTK 2. Honestly, this package should
not have entered Debian with gtk2 in 2023.

GTK 2 was superseded by GTK 3 in 2011 (see
). It no longer receives any significant
upstream maintenance, and in particular does not get feature development
for new features like UI scaling on high-pixel-density displays (HiDPI)
and native Wayland support. GTK 3 is in maintenance mode and GTK 4 is
approaching release, so it seems like a good time to be thinking about
minimizing the amount of GTK 2 in the archive.

Please consider switching to lcl=qt5 to build with qt5 interface.
Please rename c-evo-dh-gtk2 to c-evo-dh when implementing this. We really
do not need to know the toolkit that it uses by looking at the pkg name.

I would gladly sponsor this.

Bug#1052030: delve: FTBFS

[Sebastian Ramacher]

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

https://buildd.debian.org/status/fetch.php?pkg=delve&arch=amd64&ver=1.21.0-2%2Bb2&stamp=1694856639&raw=0

--- PASS: TestIssue406 (0.40s)
=== RUN   TestEvalExprName
common_test.go:20: failed assertion at integration2_test.go:1651: 
EvalVariable - could not find symbol value for i1
--- FAIL: TestEvalExprName (0.42s)

Cheers
-- 
Sebastian Ramacher

Bug#1052031: python-libcst: FTBFS: error: no matching package named `thiserror` found

[Sebastian Ramacher]

Source: python-libcst
Version: 1.0.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=python-libcst&arch=amd64&ver=1.0.1-1%2Bb2&stamp=1694694414&raw=0

cargo rustc --lib --message-format=json-render-diagnostics --manifest-path 
native/libcst/Cargo.toml --release -v --features pyo3/extension-module -- 
--crate-type cdylib
error: no matching package named `thiserror` found
location searched: registry `crates-io`
required by package `libcst v0.5.0 (/<>/native/libcst)`
error: `cargo rustc --lib --message-format=json-render-diagnostics 
--manifest-path native/libcst/Cargo.toml --release -v --features 
pyo3/extension-module -- --crate-type cdylib` failed with code 101

ERROR Backend subprocess exited when trying to invoke build_wheel
E: pybuild pybuild:395: build: plugin pyproject failed with: exit code=1: 
python3.11 -m build --skip-dependency-check --no-isolation --wheel --outdir 
/<>/.pybuild/cpython3_3.11 
dh_auto_build: error: pybuild --build -i python{version} -p 3.11 returned exit 
code 13
make[1]: *** [debian/rules:16: override_dh_auto_build] Error 25

Cheers
-- 
Sebastian Ramacher

Bug#1052032: msc-generator: FTBFS: [Makefile:793: check-local] Error 1

[Sebastian Ramacher]

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

https://buildd.debian.org/status/fetch.php?pkg=msc-generator&arch=amd64&ver=8.4.1-3&stamp=1694294426&raw=0

echo doc/ex01.exit doc/ex02.exit doc/ex03.exit doc/ex04.exit doc/ex05.exit 
doc/ex06.exit doc/ex07.exit doc/ex08.exit doc/ex09.exit doc/ex10.exit 
doc/ex11.exit doc/ex12.exit doc/ex13.exit doc/ex14.exit doc/ex15.exit 
doc/ex16.exit doc/ex17.exit doc/ex18.exit doc/ex19.exit doc/ex20.exit 
doc/ex21.exit doc/ex22.exit doc/ex23.exit doc/ex24.exit doc/ex25.exit 
doc/ex26.exit doc/ex27.exit doc/ex29.exit doc/ex30.exit doc/ex31.exit 
doc/ex32.exit doc/ex33.exit doc/ex34.exit doc/ex35.exit doc/ex36.exit 
doc/ex37.exit doc/ex38.exit doc/ex39.exit doc/ex40.exit doc/ex41.exit 
doc/ex42.exit doc/ex43.exit doc/ex44.exit doc/ex45.exit doc/ex46.exit 
doc/ex47.exit doc/ex48.exit doc/ex49.exit doc/ex50.exit doc/ex51.exit 
doc/ex52.exit doc/ex53.exit doc/ex54.exit doc/ex55.exit doc/ex56.exit 
doc/ex57.exit doc/ex58.exit doc/ex59.exit doc/ex60.exit doc/ex61.exit 
doc/ex62.exit doc/ex63.exit doc/ex64.exit doc/ex65.exit doc/ex66.exit 
doc/ex67.exit doc/ex68.exit doc/ex69.exit doc/ex70.exit doc/ex71.exit 
doc/ex72.exit doc/ex73.exit doc/ex74.exit doc/ex75.exit doc/ex76.exit 
doc/ex77.exit doc/ex78.exit doc/ex79.exit doc/ex80.exit doc/ex81.exit 
doc/ex82.exit doc/ex83.exit doc/ex84.exit doc/ex85.exit doc/ex86.exit 
doc/ex87.exit doc/ex88.exit doc/ex89.exit doc/ex90.exit doc/ex91.exit 
doc/ex92.exit doc/ex93.exit doc/ex94.exit doc/ex95.exit doc/ex96.exit 
doc/ex97.exit doc/ex98.exit doc/ex99.exit doc/exA0.exit doc/exA1.exit 
doc/exA2.exit doc/exA3.exit doc/exA4.exit doc/exA5.exit doc/exA6.exit 
doc/exB1.exit doc/exB2.exit doc/exB3.exit doc/exB4.exit doc/exB5.exit 
doc/exB6.exit doc/exB7.exit doc/exB8.exit doc/exB9.exit doc/exBA.exit 
doc/exBD.exit doc/exBE.exit doc/exBF.exit doc/exH0.exit doc/exC0.exit 
doc/exC1.exit doc/exC2.exit doc/exC3.exit doc/exC4.exit doc/exC5.exit 
doc/exC6.exit doc/exC7.exit doc/exC8.exit doc/exC9.exit doc/exD0.exit 
doc/exD1.exit doc/exD2.exit doc/exD3.exit doc/exD4.exit doc/exD5.exit 
doc/exD6.exit doc/exD7.exit doc/exD8.exit doc/exD9.exit doc/exE0.exit 
doc/exE1.exit doc/exE2.exit doc/exE3.exit doc/exE4.exit doc/exE5.exit 
doc/exE6.exit doc/exE7.exit doc/exE8.exit doc/exE9.exit doc/exF0.exit 
doc/exF1.exit doc/exF2.exit doc/exF3.exit doc/exF4.exit doc/exF5.exit 
doc/exF6.exit doc/exF7.exit doc/exF8.exit doc/exF9.exit doc/exG0.exit 
doc/exG1.exit doc/exG2.exit doc/exG3.exit doc/exG4.exit doc/exG5.exit 
doc/exG6.exit doc/exG7.exit doc/exG8.exit doc/exG9.exit doc/exH1.exit 
doc/exH2.exit doc/exH3.exit doc/exH4.exit doc/exH5.exit doc/exH6.exit 
doc/exH7.exit doc/exH8.exit doc/exH9.exit doc/exI0.exit doc/exI1.exit 
doc/exI2.exit doc/exI3.exit doc/exI4.exit doc/exI5.exit doc/exI6.exit 
doc/exI7.exit doc/exI8.exit doc/exI9.exit doc/exJ0.exit doc/exJ1.exit 
doc/exA7.exit doc/exA8.exit doc/exA9.exit doc/exB0.exit doc/exBB.exit 
doc/exBC.exit basic/Block_arrows.exit basic/CDIV_Uncond_online.exit 
basic/Complex.exit basic/Dinand.exit basic/Grouped_entities.exit 
basic/Grouped_entities_2.exit basic/Grouped_entities_3.exit 
basic/International1.exit basic/International1_utf16.exit 
basic/SpecialEndings.exit basic/WidthCalcAlgo.exit basic/actor.exit 
basic/aline.exit basic/arrow_joins.exit basic/arrows.exit basic/boxes.exit 
basic/dini.exit basic/entities.exit basic/ex28_color2.exit basic/g_mini.exit 
basic/gvarrows.exit basic/links.exit basic/looong_note_arrow.exit 
basic/lost_note_arrowhead.exit basic/m2m.exit basic/m_mini.exit 
basic/m_nocomment_small.exit basic/mscgen.exit basic/nested_if.exit 
basic/notes_joins.exit basic/old_test.exit basic/pipes.exit 
basic/self-arrow-join.exit basic/shapes.exit basic/symbols.exit 
basic/test1.exit basic/test_small.exit basic/v5.2features.exit 
basic/variables.exit basic/verticals.exit basic/wonkiness.exit 
basic/wonkiness2.exit basic/wonkiness3.exit basic/wonkiness4.exit 
basic/wonkiness5.exit basic/cshfix.exit basic/variables_block.exit 
basic/escapes.exit basic/record.exit basic/variables_graph.exit 
notes/Block_arrows_note.exit notes/Dinand_note.exit 
notes/Grouped_entities_2_note.exit notes/Grouped_entities_note.exit 
notes/arrows_note.exit notes/boxcollapse_notes.exit notes/boxes_note.exit 
notes/dini_note.exit notes/entities_note.exit notes/ex37_note.exit 
notes/old_test_note.exit notes/pipes_note.exit notes/symbols_note.exit 
notes/test1_note.exit procedures/Block_arrows_proc.exit 
procedures/CDIV_Uncond_online_proc.exit procedures/Complex_proc.exit 
procedures/Dinand_proc.exit procedures/Grouped_entities_2_proc.exit 
procedures/Grouped_entities_3_proc.exit procedures/Grouped_entities_proc.exit 
procedures/International1_proc.exit procedures/International1_utf16_proc.exit 
procedures/SpecialEndings_proc.exit procedures/WidthCalcAlgo_proc.exit 
procedures/actor_proc.exit procedures

Bug#1050876: apt-doc:[INTL:fr] updated translation of apt-doc 2.6.1

[Julian Andres Klode]

Control: tag -1 moreinfo

On Wed, Aug 30, 2023 at 07:14:59PM +0200, bu...@no-log.org wrote:
> Package: apt-doc
> Version:2.6.1
> Severity: wishlist
> Tags: patch l10n
> 
> Dear mainteners,
> Hello, please find the updated french translation for apt-doc attached,
> proofread by the debian-l10n-french mailing list contributors.

It doesn't seem we have interacted before and you haven't provided
any proofs to the review claims nor your real name, so I won't be 
picking this up for the time being.

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#1052033: davmail: Davmail uses too much memory

[Christophe TROESTLER]

Package: davmail
Version: 6.1.0.3423-4
Severity: normal
X-Debbugs-Cc: none, Christophe Troestler 

Dear Maintainer,

Upon launch Davmail uses 7.5GiB of virtual memory and 107.8MiB of resident 
memory but, after using it for about a day, 7.6GiB of virtual memory and 686MiB 
of resident memory.  Given that davmail only needs to keep a very small state, 
that seems to point to a memory leak.

As a complement of information:

java --version
openjdk 17.0.9-ea 2023-10-17
OpenJDK Runtime Environment (build 17.0.9-ea+4-Debian-1)
OpenJDK 64-Bit Server VM (build 17.0.9-ea+4-Debian-1, mixed mode, sharing)

Best regards,
C.


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

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

Versions of packages davmail depends on:
ii  davmail-server  6.1.0.3423-4
ii  default-jre 2:1.17-74
ii  libopenjfx-java 11.0.11+1-3.1
ii  libswt-cairo-gtk-4-jni  4.26.0-1

davmail recommends no packages.

davmail suggests no packages.

-- no debconf information

Bug#1051731: apt: [INTL:pt] Update on Portuguese translation of MANPAGE

[Julian Andres Klode]

Control: tag -1 moreinfo

On Mon, Sep 11, 2023 at 09:01:54PM +0100, Américo Monteiro wrote:
> Package: apt
> Version: 2.7.3
> Tags: l10n, patch
> Severity: wishlist
> 
> Updated Portuguese translation for apt's manpage
> Translator: Américo Monteiro 
> Feel free to use it.

Please provide evidence of peer review by the pt translator
email list, I cannot merge translations from a new third party.
-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#1052034: procps: FTBFS on amd64, i386: # of unexpected failures 1

[Sebastian Ramacher]

Source: procps
Version: 2:4.0.4-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=procps&arch=amd64&ver=2%3A4.0.4-1&stamp=1694089907&raw=0

WARNING: Couldn't find tool init file
Test run by buildd on Thu Sep  7 12:31:32 2023
Native configuration is x86_64-pc-linux-gnu

=== pmap tests ===

Schedule of variations:
unix

Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for 
target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using /<>/testsuite/config/unix.exp as tool-and-target-specific 
interface file.
Running /<>/testsuite/pmap.test/pmap.exp ...
FAIL: pmap XX pid pid has same total

=== pmap Summary ===

# of expected passes13
# of unexpected failures1
/<>/src/pmap version 4.0.4

WARNING: Couldn't find tool init file
Test run by buildd on Thu Sep  7 12:31:32 2023
Native configuration is x86_64-pc-linux-gnu


Cheers
-- 
Sebastian Ramacher

Bug#1052035: ulex0.8: FTBFS: Error: This expression has type char Stream.t -> (MLast.str_item * MLast.loc) list * Pcaml.status but an expression was expected of type 'a ref

[Sebastian Ramacher]

Source: ulex0.8
Version: 1.2-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=ulex0.8&arch=amd64&ver=1.2-2%2Bb5&stamp=1694049779&raw=0

ocamlfind ocamlc -c -package camlp5 -pp 'camlp5o pa_macro.cmo pa_extend.cmo 
q_MLast.cmo' -o pa_ulex.cmo pa_ulex.ml
+ ocamlfind ocamlc -c -package camlp5 -pp 'camlp5o pa_macro.cmo pa_extend.cmo 
q_MLast.cmo' -o pa_ulex.cmo pa_ulex.ml
findlib: [WARNING] Interface topdirs.cmi occurs in several directories: 
/usr/lib/ocaml, /usr/lib/ocaml/compiler-libs
File "pa_ulex.ml", line 267, characters 26-44:
267 |   let old_parse_implem = !Pcaml.parse_implem in
^^
Error: This expression has type
 char Stream.t -> (MLast.str_item * MLast.loc) list * Pcaml.status
   but an expression was expected of type 'a ref
Command exited with code 2.
make[2]: *** [Makefile:5: all] Error 10

Cheers
-- 
Sebastian Ramacher

Bug#1016703: mkdocs-material: Please package recent version

[Carsten Schoenert]

Hello Sandro,

Am Fri, Aug 05, 2022 at 08:06:20PM +0200 schrieb Carsten Schoenert:
> Package: mkdocs-material
> Version: 8.2.5-1
> Severity: wishlist
> 
> Hello Sandro,
> 
> could you please consider to package the recent upstream version of
> mkdocs-material?
> 
> Could you also please (re)close the issue #1008691 by the newer version
> within the new changelog entry?
> 
> As Paul Grevers explained to me has the BTS a problem if a bug report
> has the same version marked fixes as the report has been open against before.
> That's currently the reason the package isn't midrating to testing.

this bug report is now open for one year, is there something you need
help with?

I'd really appreciate a recent version could make it's way into the
archive.

Regards
Carsten

Bug#1052012: plasma-workspace: sddm presents a white screen with no background nor buttons

[Alexis Murzeau]

Hi,

On Sat, 16 Sep 2023 00:55:12 +0200 Miguel Angel Rojas  
wrote:

Hi there,

Downgrading the following packages:

   - sddm-themes-breeze
   - sddm-theme-debian-breeze

to version 4:5.27.7-2 makes sddm fully usable again with no issues.

It seems some changes have been made on version 4:5.27.8-1 that have broken
sddm.

I hope this helps.

Regards



I have issues too with sddm-theme-debian-breeze 5.27.8-1, but the symptom is 
different.
I get a correct screen, but the password field has a very small font size and 
each character is 1 pixel.

Using diffoscope, it appears sddm-theme-debian-breeze 5.27.8-1 doesn't have the 
theme.conf file.
Adding back theme.conf from version 5.27.7-2 with 5.27.8-1 installed fix the 
issue for me.

Note: metadata.desktop was also removed in 5.27.8-1, maybe it shouldn't too.


@Miguel, can you try to do the same to check if theme.conf is also the cause of 
your issues ?

That is, adding `/usr/share/sddm/themes/debian-breeze/theme.conf` with this 
content:

```
[General]
showlogo=hidden
logo=/usr/share/sddm/themes/breeze/default-logo.svg
type=image
color=#1d99f3
fontSize=10
background=/usr/share/desktop-base/active-theme/login/background.svg
needsFullUserModel=false
```


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

Kernel: Linux 6.5.0-1-amd64 (SMP w/4 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)

Versions of packages sddm-theme-debian-breeze depends on:
ii  plasma-framework   5.107.0-1
ii  plasma-workspace   4:5.27.8-1
ii  sddm-theme-breeze  4:5.27.8-1

Versions of packages sddm-theme-debian-breeze recommends:
ii  desktop-base  12.0.6+nmu1
ii  sddm  0.20.0-1

sddm-theme-debian-breeze suggests no packages.

-- no debconf information


--
Alexis Murzeau
PGP: B7E6 0EBB 9293 7B06 BDBC  2787 E7BD 1904 F480 937F |

Bug#1050709: tar-ignore debian/source/options

[Niels Thykier]

Sean Whitton:

Hello Niels,

[...]

dgit will never let you accidentally perform an upload containing
something that's in the tree but not in git, and you can use
.git/info/exclude as a local way to ensure it's never in git.  So a
simple policy of always doing uploads with dgit might achieve what you
want, without introducing all these deltas between source packages, git,
local trees etc.?



Hi Sean

Appreciate the suggestion.

The suggestion assumes that I am using dgit or ready to migrate my 
workflow to use dgit, which I am not at this stage.


I was open to doing to making my package work better for people that use 
dgit if it has a "near zero cost" to my current packaging work flow. It 
is regular that other people upload debhelper and some of them use dgit.


The proposal of replacing `tar-ignore` with its expanded version minus 
`tar-ignore=.gitignore` sadly does not fit that "near zero cost" bill 
for me.  For now, I am afraid my packages will not be compatible with 
dgit until the feature interaction between dpkg-source -I/tar-ignore and 
dgit is resolved.



Best regards,
Niels

Bug#1052035: ulex0.8: FTBFS: Error: This expression has type char Stream.t -> (MLast.str_item * MLast.loc) list * Pcaml.status but an expression was expected of type 'a ref

[Stéphane Glondu]

Hi,

Le 16/09/2023 à 12:54, Sebastian Ramacher a écrit :

Source: ulex0.8
Version: 1.2-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
[...]


See https://bugs.debian.org/1051377


Cheers,

--
Stéphane

Bug#1036076: rust-mysqlclient-sys appears to be unsound when used with mariadb.

[Matthias Geiger]

On Mon, 15 May 2023 05:47:10 +0100 Peter Green  wrote:
> Package: rust-mysqlclient-sys
> Severity: serious
>
> I was looking at why rust-diesel was not migrating to testing
> (other than the freeze obviously) and noticed that rust-mysqlclient-sys
> was not built on 32-bit architectures. As with a bunch of other
> packages I correctly suspected this was mostly a case of unportable
> bindgen-generated tests and started preparing fixes for them.
>
> However while doing so, I rapidly came to the conclusion that something
> else was wrong. Specifically I noticed significant discrepancies
> between the "mysql" (actually mariadb) C headers on my system and the
> rust bindings in rust-mysqlclient-sys.
>
> The tests in the crate only test that the size/alignment of the
> structures defined in the crate are consistent with what they were
> when the bindings were generated. They do not check in any way that
> they are consistent with the structures defined by the C headers on
> the user's system. There are no functional tests either.
>
> My conclusion is that attempting to use this crate with mariadb
> is highly unsound, though I don't know enough about how the mysql
> client library is used to determine in what way exactly it will break
> and whether the breakage is likely to be immediately apparent or more
> subtle.
>
>

>

Control: severity -1 important

lowering severity so it and rdeps can migrate. I skipped the failing 
tests for now.


--
Matthias Geiger (werdahias)
Debian Maintainer
"Freiheit ist immer Freiheit des anders Denkenden" -- Rosa Luxemburg



OpenPGP_0x18BD106B3B6C5475.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1052036: cmospwd: Drop kfreebsd from Arch list

[Bastian Germann]

Source: cmospwd
Severity: important
Version: 5.0+dfsg-2

kfreebsd is gone from Debian. Please drop it from the architecture list.

Bug#1051630: transition: qtwebengine-abi-5-15-15

[Dmitry Shachnev]

On Sat, Sep 16, 2023 at 09:52:22AM +0200, Sebastian Ramacher wrote:
> qtwebengine-opensource-src and binNMUs of the reverse dependencies
> migrated. Closing.

Thank you, Sebastian!

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#1052037: Can't be imported on armel

[Andrey Rakhmatullin]

Package: python3-fasttext
Version: 0.9.2+ds-4
Severity: serious

Found in dateparser autopkgtest logs and confirmed on the armel porterbox:

>>> import fasttext_pybind
Traceback (most recent call last):
  File "", line 1, in 
ImportError: /usr/lib/python3/dist-packages/fasttext_pybind.cpython-311-arm-
linux-gnueabi.so: undefined symbol: __atomic_load_8


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

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

Versions of packages python3-fasttext depends on:
ii  libc6  2.37-8
ii  libgcc-s1  13.2.0-3
ii  libstdc++6 13.2.0-3
ii  python33.11.4-5+b1
ii  python3-numpy  1:1.24.2-1
ii  python3-pkg-resources  68.1.2-1
pn  python3-pybind11   

python3-fasttext recommends no packages.

python3-fasttext suggests no packages.

Bug#1052038: lxpanel: Segmentation fault when startup

[陳昌倬]

Package: lxpanel
Version: 0.10.1-4
Severity: grave
Justification: renders package unusable


lxpanel receives signal SIGSEGV, Segmentation fault when startup, and
cause it unusable.


  $ gdb lxpanel
  Reading symbols from lxpanel...
  Reading symbols from 
/usr/lib/debug/.build-id/e2/41004afdf79e3c7d83166b0fec1c7d09733a4b.debug...
  (gdb) r
  Starting program: /usr/bin/lxpanel 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  [New Thread 0x757ff6c0 (LWP 315599)]
  [New Thread 0x7fffe6c0 (LWP 315600)]
  [New Thread 0x74ffe6c0 (LWP 315601)]
  [New Thread 0x7fffef7fe6c0 (LWP 315602)]
  [New Thread 0x7fffeeffd6c0 (LWP 315603)]
  
  Thread 1 "lxpanel" received signal SIGSEGV, Segmentation fault.
  0x0003 in ?? ()
  (gdb) bt
  #0  0x0003 in ?? ()
  #1  0x76f1bb6f in XInternAtoms () from 
/lib/x86_64-linux-gnu/libX11.so.6
  #2  0x77fa60ef in resolve_atoms () at ./src/misc.c:380
  #3  0x55563212 in main (argc=, argv=, 
env=0x7fffd208) at ./src/main.c:489




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

Kernel: Linux 6.5.0-1-amd64 (SMP w/16 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 lxpanel depends on:
ii  libasound2   1.2.10-1
ii  libc62.37-9
ii  libcairo21.17.8-3
ii  libcurl3-gnutls  8.3.0-1
ii  libfm-gtk3-4 1.3.2-4
ii  libfm-modules1.3.2-4
ii  libfm4   1.3.2-4
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libglib2.0-0 2.78.0-1
ii  libgtk-3-0   3.24.38-5
ii  libiw30  30~pre9-14
ii  libkeybinder-3.0-0   0.3.2-1.1
ii  libmenu-cache3   1.1.0-1.1
ii  libpango-1.0-0   1.51.0+ds-2
ii  libwnck-3-0  43.0-3
ii  libx11-6 2:1.8.6-1
ii  libxml2  2.9.14+dfsg-1.3
ii  lxmenu-data  0.1.5-2.1
ii  lxpanel-data 0.10.1-4

Versions of packages lxpanel recommends:
ii  gnome-shell [notification-daemon] 44.4-1
ii  gnome-terminal [x-terminal-emulator]  3.49.99-1
ii  libnotify-bin 0.8.2-1
ii  lxqt-notificationd [notification-daemon]  1.3.0-1
ii  lxterminal [x-terminal-emulator]  0.4.0-2
ii  notification-daemon   3.20.0-4+b1
ii  pavucontrol   5.0-2
ii  qterminal [x-terminal-emulator]   1.3.0-1
ii  xkb-data  2.38-2
ii  xterm [x-terminal-emulator]   384-1

Versions of packages lxpanel suggests:
ii  firefox-esr [www-browser]   115.2.1esr-1
ii  google-chrome-stable [www-browser]  117.0.5938.88-1
ii  lynx [www-browser]  2.9.0dev.12-1

-- no debconf information

-- 
ChangZhuo Chen (陳昌倬) czchen@{czchen,debian}.org
https://czchen.org/
Key fingerprint = BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


signature.asc
Description: PGP signature

Bug#1051819: fluidsynth: Consider building with pipewire support

[Nicholas D Steeves]

Hi Gianfranco,

Oh my, yes, it seems I forgot to add the new pipewire -dev package to the
fluidsynth -dev package.  'not sure how that happened, but my mistake!
Isn't only waiting 48h a bit rushed for an NMU though?  I can of course
import your fix and upload in the next 48h, and I'd like to improve your
changelog entry, because I think you'll agree that the concept of "runtime"
doesn't make sense for headers ;)  If this is truly 0-day urgent, I'm
confident a team member (IIRC Josch is a multimedia-team member) will
upload.

Cheers,
Nicholas

('hope this isn't HTML email, since I'm currently AFK on a phone)

Bug#1052039: okular: Okular cannot open PDF files.

[Frédéric Tronel]

Package: okular
Version: 4:22.12.3-1
Severity: important

Dear Maintainer,

Okular is not able to open PDF files in the current bookworm release.
When opening a PDF file with Okular, the following error message appears
on terminal:

org.kde.okular.core: Invalid plugin factory for 
"/usr/lib/x86_64-linux-gnu/qt5/plugins/okular/generators/okularGenerator_poppler.so":"Cannot
 load library 
/usr/lib/x86_64-linux-gnu/qt5/plugins/okular/generators/okularGenerator_poppler.so:
 (libtiff.so.5: cannot open shared object file: No such file or directory)"

Indeed, libtiff.so.5 is not provided by Debian Bookworm (only
libtiff.so.6 exists).

We can confirm that "okularGenerator_poppler.so" was built with libtiff.so.5:

$ ldd 
/usr/lib/x86_64-linux-gnu/qt5/plugins/okular/generators/okularGenerator_poppler.so
linux-vdso.so.1 (0x7ffc69b3d000)
libOkular5Core.so.10 => /lib/x86_64-linux-gnu/libOkular5Core.so.10 
(0x7f8e7768a000)
libKF5KIOWidgets.so.5 => /lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5 
(0x7f8e77529000)
[...]
libtiff.so.5 => not found
[...]

$ LANG=C apt-cache show libtiff6
Package: libtiff6
Source: tiff
Version: 4.5.0-6
Installed-Size: 711
Maintainer: Laszlo Boszormenyi (GCS) 
Architecture: amd64
Depends: libc6 (>= 2.33), libdeflate0 (>= 1.0), libjbig0 (>= 2.0), 
libjpeg62-turbo (>= 1.3.1), liblerc4 (>= 3.0), liblzma5 (>= 
5.1.1alpha+20120614), libwebp7 (>= 1.2.4), libzstd1 (>= 1.5.2), zlib1g (>= 
1:1.1.4)
Description-en: Tag Image File Format (TIFF) library
 libtiff is a library providing support for the Tag Image File Format
 (TIFF), a widely used format for storing image data.  This package
 includes the shared library.
Description-md5: bdf182da5cc17db1c9eb4ccb03647efc
Multi-Arch: same
Homepage: https://libtiff.gitlab.io/libtiff/
Tag: role::shared-lib
Section: libs
Priority: optional
Filename: pool/main/t/tiff/libtiff6_4.5.0-6_amd64.deb
Size: 315592
MD5sum: 7d0a2b82f10cde5e6dfbc1f1e30d3016
SHA256: 5b88709ff346b43f15a415a4b415260bbf260d7f407f767b055383c57ab1bc9b



-- System Information:
Debian Release: 12.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable'), (100, 'bookworm-fasttrack'), (100, 'bookworm-backports-staging')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-12-amd64 (SMP w/12 CPU threads; PREEMPT)
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 okular depends on:
ii  kinit 5.103.0-1
ii  kio   5.103.0-1
ii  libc6 2.36-9+deb12u1
ii  libfreetype6  2.12.1+dfsg-5
ii  libjpeg62-turbo   1:2.1.5-2
ii  libkf5activities5 5.103.0-1
ii  libkf5archive55.103.0-1
ii  libkf5bookmarks5  5.103.0-1
ii  libkf5codecs5 5.103.0-1
ii  libkf5completion5 5.103.0-1
ii  libkf5configcore5 5.103.0-2
ii  libkf5configgui5  5.103.0-2
ii  libkf5configwidgets5  5.103.0-1
ii  libkf5coreaddons5 5.103.0-1
ii  libkf5crash5  5.103.0-1
ii  libkf5i18n5   5.103.0-1
ii  libkf5itemviews5  5.103.0-1
ii  libkf5jobwidgets5 5.103.0-1
ii  libkf5kexiv2-15.0.0   22.12.3-1
ii  libkf5kiocore55.103.0-1
ii  libkf5kiogui5 5.103.0-1
ii  libkf5kiowidgets5 5.103.0-1
ii  libkf5parts5  5.103.0-1
ii  libkf5pty55.103.0-1
ii  libkf5purpose-bin 5.103.0-1
ii  libkf5purpose55.103.0-1
ii  libkf5textwidgets55.103.0-1
ii  libkf5wallet-bin  5.103.0-1
ii  libkf5wallet5 5.103.0-1
ii  libkf5widgetsaddons5  5.103.0-1
ii  libkf5windowsystem5   5.103.0-1
ii  libkf5xmlgui5 5.103.0-1
ii  libokular5core10  4:22.12.3-1
ii  libphonon4qt5-4   4:4.11.1-4
ii  libpoppler-qt5-1  22.12.0-2+b1
ii  libqmobipocket2   4:22.12.3-1
ii  libqt5core5a  5.15.8+dfsg-11
ii  libqt5dbus5   5.15.8+dfsg-11
ii  libqt5gui55.15.8+dfsg-11
ii  libqt5printsupport5   5.15.8+dfsg-11
ii  libqt5texttospeech5   5.15.8-2
ii  libqt5widgets55.15.8+dfsg-11
ii  libqt5xml55.15.8+dfsg-11
ii  libspectre1   0.2.12-1
ii  libstdc++612.2.0-14
ii  phonon4qt54:4.11.1-4
ii  zlib1g1:1.2.13.dfsg-1

Versions of packages okular recommends:
ii  cups-bsd  2.4.2-3+deb12u1

Versions of packages okular suggests:
ii  ghostscript10.0.0~dfsg-11+deb12u1
ii  okular-extra-backends  4:22.12.3-1
ii  poppler-data   0.4.12-1
ii  texlive-binaries   2022.20220321.62855-5.1+deb12u1
pn  unrar  

-- no debconf information

Bug#933347: -d option doesn't work as expected for gettext with -M

[Sébastien Villemot]

On Mon, 29 Jul 2019 23:46:57 +0900 Osamu Aoki  wrote:
> Package: src:sphinx
> Version: 1.8.4-1
> Severity: normal
> 
> -M option doesn't work well except for a very simple case.  I faced
this
> problem while building multi-language source.
[…]
> I wanted to move the cache directory to a particular FOO, so I did:
>  $ sphinx-build -M gettext -d FOO source build
> 
> This creates:
> new file:   FOO/gettext/environment.pickle
> new file:   FOO/gettext/index.doctree
> new file:   FOO/gettext/scope.doctree
> new file:   build/index.pot
> new file:   build/scope.pot

I experience a similar problem with -M latexpdf in combination with the
-D option. If I do:

sphinx-build -M latexpdf -D release=v1.0 source build

Then a directory “release=v1.0” is created (populated by doctrees) and
the build breaks when trying to compile the LaTeX source to PDF.

Experienced with sphinx-build 5.3.0-7.

Cheers,

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



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

Bug#1051719: markdown-mode.el produces excessive warnings

[Nicholas D Steeves]

Hi Daniel and David,

On Wed, 13 Sept 2023 at 04:17, Daniel Kahn Gillmor 
wrote:


> thanks for the review!  I poked around at
> https://github.com/jrblevin/markdown-mode and it looks like
> 518191bfd69130a6f788f7cea88033c183e43736 was intended to resolve these
> issues (see the PR i've linked here too). Maybe we just need version 2.6
> packaged for debian?
>

Wow, thank you for your investigation!  Yes,  you're right, 2.6 contains
commit:518191b, thus this is the correct action.


> Thanks for maintaining elpa-markdown-mode in debian!
>

It's a team effort, so on behalf of the team, you're welcome! :)

David, do you think you'll be able to find time for this or do you want me
to come back to it in a week or so?

Cheers,
Nicholas

P.S. I'm AFK at the moment, and I hope my phone doesn't do anything weird
to the email.

Bug#1052040: mmm-mode: post-install script fails

[mister01x]

Package: mmm-mode
Version: 0.5.9-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: mister...@web.de

Dear Maintainer,

installation/upgrading of the package fails with the following output
(please excuse the automatic line wrapping of thunderbirds plain text mode):

# LANG=C apt -f install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up mmm-mode (0.5.9-1) ...
Install emacsen-common for emacs
emacsen-common: Handling install of emacsen flavor emacs
Install mmm-mode for emacs
install/mmm-mode: Handling install of emacsen flavor emacs
install/mmm-mode: byte-compiling for emacs

In toplevel form:
mmm-auto.el:178:4: Error: Wrong number of arguments: (3 . 4), 2

In toplevel form:
mmm-class.el:36:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
mmm-cmds.el:36:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
mmm-cweb.el:35:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
mmm-defaults.el:37:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
mmm-erb.el:62:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
mmm-mason.el:36:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
mmm-mode.el:93:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
mmm-myghty.el:41:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
mmm-noweb.el:44:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
mmm-region.el:42:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
mmm-rpm.el:45:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
mmm-sample.el:38:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
mmm-univ.el:35:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)
ERROR: install script from mmm-mode package failed
dpkg: error processing package mmm-mode (--configure):
 installed mmm-mode package post-installation script subprocess returned
error exit status 1
Errors were encountered while processing:
 mmm-mode
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)



Thanks for maintaining mmm-mode

Marcel

-- 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.5.3-1-siduction-amd64 (SMP w/12 CPU threads; PREEMPT)
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 mmm-mode depends on:
ii  emacs-gtk [emacsen]  1:29.1+1-5
ii  emacsen-common   3.0.5

mmm-mode recommends no packages.

mmm-mode suggests no packages.

-- no debconf information

Bug#1050676: enblend-enfuse: FTBFS: dot: maze.c:311: chkSgraph: Assertion `np->cells[0]' failed.

[Andreas Metzler]

On 2023-09-15 "László Böszörményi (GCS)"  wrote:
[...]
>  There's still a font issue, you will get something like:
> fontconfig: Didn't find expected font family. Perhaps URW Type 1 fonts
> need installing?

> I don't know why this is happening, as if I check the intermediate dot
> file then only the node font settings cause this error. Other uses of
> the Helvetica font are fine. As per source change, you will need this
> patch for enblend-enfuse.
> Please check if the resulting package works as you expected or not and
> report back your findings.
[...]

except for the expect font difference (Times) this seems to work ok. -
Thanks.

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#1051153: (sagemath) crash on startup due to a python error

[Jean-Paul Vincent]

Hi,

Here, same system, trixie, same bug. 
One remark. From the terminal :

from sage.rings.polynomial.multi_polynomial_libsingular 
import MPolynomialRing_libsingular
ImportError: libsingular-Singular-4.3.1.so: cannot open 
shared object file: No such file or directory

Normal because:
~% locate  libsingular-Singular-4.3
/usr/lib/x86_64-linux-gnu/libsingular-Singular-4.3.2.so

Regards

Bug#1052041: RM: rust-sequoia-sq [mips64el ppc64el s390x] -- RoM; build-depends on rust-sequoia-net which is NBS on those arches

[Jeremy Bícha]

Package: ftp.debian.org
Affects: src:rust-sequoia-sq

Please remove rust-sequoia-sq source and binaries on mips64el ppc64el
and s390x because it Build-Depends on rust-sequoia-net.

rust-sequoia-net now Build-Depends on rust-trust-dns-client which
Build-Depends on rust-trust-dns-proto which Build-Depends on rust-ring
which has never been built on those architectures in Debian.

This issue is blocking the migration of rust-sequoia-net to Testing.

Reverse-Depends
==
There is only one reverse build-depends: archlinux-keyring, an arch:all package.

debsig-verify has an alternate Build-Depends but the first in the list
of alternates is gnupg
dpkg-dev has an alternate Recommends but the first in the list of
alternates is gnupg

codesearch since many tools don't handle Provides which Debian Rust
packages use extensively:
https://codesearch.debian.net/search?q=path%3Adebian%2Fcontrol+rust-sequoia-sq&literal=1

On behalf of the Debian Rust team,
Jeremy Bicha

Bug#1052042: ITS: gdebi

[Bastian Germann]

Source: gdebi

I intend to salvage gdebi with the plan to orphan it in three weeks.
Please notify me if you object.

Bug#1052043: RM: rust-sequoia-net [mips64el ppc64el s390x] -- RoM; build-depends on rust-trust-dns-client which is NBS there

[Jeremy Bícha]

Package: ftp.debian.org
Affects: src:rust-sequoia-net
Control: block -1 by 1052041

Please remove rust-sequoia-net source and binaries on mips64el ppc64el
and s390x because it now Build-Depends on rust-trust-dns-client which
Build-Depends on rust-trust-dns-proto which Build-Depends on rust-ring
which has never been built on those architectures in Debian.

Reverse-Depends
==
There is only one reverse build-depends: rust-sequoia-sq. See
https://bugs.debian.org/1052041

codesearch since many tools don't handle Provides which Debian Rust
packages use extensively:
https://codesearch.debian.net/search?q=path%3Adebian%2Fcontrol+rust-sequoia-net&perpkg=1

On behalf of the Debian Rust team,
Jeremy Bicha

Bug#1049332: alg: self-tests for stdrng using drbg_nopr_hmac_sha512 failed (rc=-22)

[Salvatore Bonaccorso]

Control: tags -1 + unreproducible 

Hi,

On Fri, Sep 15, 2023 at 06:21:02PM +0200, in.cognit...@arcor.de wrote:
> Since reporting this issue I never got that error again in the journal.
> 
> Feel free to close as "not reproducible".

Thanks, to do some src:linux BTS housekeeping I following this
closing this report.

Regards,
Salvatore

Bug#1042909: RM: rust-sha3-0.9 -- NVIU; obsolete package, no rdeps

[Jeremy Bícha]

You could also see https://bugs.debian.org/1051625 which I'm closing
in favor of this one.

Thank you,
Jeremy Bícha

Bug#1052038: lxpanel: Segmentation fault in Gnome desktop

[陳昌倬]

control: retitle -1 lxpanel: Segmentation fault in Gnome desktop
control: severity -1 minor


After testing, lxpanel works in sddm + LXDE desktop. It only has
segfault in gdm3 + gnome.


-- 
ChangZhuo Chen (陳昌倬) czchen@{czchen,debian}.org
https://czchen.org/
Key fingerprint = BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


signature.asc
Description: PGP signature

Bug#1043124: zfs-dkms: module fails to build for Linux 6.5: None of the expected "bops->release()" interfaces were detected.

[Francesco C]

>(Completely unrelated, but browsing the issues it popped up that encryption is
>very broken above 6.3,
>and it has been somewhat broken on older kernels too; not one people lost their
>data due to upgrading
> beyond 6.3, so beware.

"Encryption is very broken" seems too generic : it seems (to me) that
the reported issue affects zfs "native" encryption , not luks with
[(plain) zfs].

Bug#1051819: fluidsynth: Consider building with pipewire support

[Johannes Schauer Marin Rodrigues]

Hi Nicholas,

Quoting Nicholas D Steeves (2023-09-16 14:06:00)
> Oh my, yes, it seems I forgot to add the new pipewire -dev package to the
> fluidsynth -dev package.  'not sure how that happened, but my mistake!  Isn't
> only waiting 48h a bit rushed for an NMU though?

the number of delayed days are documented here:

https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#when-and-how-to-do-an-nmu

It seems that indeed a 0-day nmu was a bit too quick here.

> I can of course import your fix and upload in the next 48h, and I'd like to
> improve your changelog entry, because I think you'll agree that the concept
> of "runtime" doesn't make sense for headers ;)

It does make sense as we have two types of dependencies in Debian: build
dependencies and runtime dependencies. A header package is also a binary
package so it has runtime dependencies like all other binary packages do.

But indeed the term "runtime dependency" is not very widely used. I do not
think that Debian policy uses it. I think the term is mostly used by people
like me who work on dependency resolution software.

> If this is truly 0-day urgent, I'm confident a team member (IIRC Josch is a
> multimedia-team member) will upload.

I'm afraid it was already uploaded and is now in unstable. :(

> ('hope this isn't HTML email, since I'm currently AFK on a phone)

It was HTML but it also had a text/plain part. :)

Thanks!

cheers, josch

signature.asc
Description: signature

Bug#1052044: Without git, pybuild does not include data files into wheel

[Ole Streicher]

Package: python3-build
Version:  0.10.0-1
Severity: important

Dear maintainer,

I am trying to build the package "asdf-wcs-schema"

https://salsa.debian.org/debian-astro-team/asdf-wcs-schemas

which includes a lot of metadata, f.e.

resources/manifests/gwcs-1.0.0.yaml

With the normal build procedure, the build does not include the data 
files see f.e.


https://salsa.debian.org/debian-astro-team/asdf-wcs-schemas/-/jobs/4706731

I traced this down to the "python3 -m build" call, which is

python3.11 -m build --skip-dependency-check --no-isolation --wheel 
--outdir 
/builds/debian-astro-team/asdf-wcs-schemas/debian/output/source_dir/.pybuild/cpython3_3.11 



Running this command locally on a system with just the build deps 
installed does (with the environment variable 
SETUPTOOLS_SCM_PRETEND_VERSION=0.2.0) not include the data files. 
However, when I install the "git" package, the data files are included.


The packages uses pyproject.toml, and the data files are specified as

8<---
[tool.setuptools]
packages = ["asdf_wcs_schemas", "asdf_wcs_schemas.resources"]

[tool.setuptools.package-data]
"asdf_wcs_schemas.resources" = ["resources/**/*.yaml"]

[tool.setuptools.package-dir]
'' = "src"
"asdf_wcs_schemas.resources" = "resources"
8<---

which looks reasonable to me.

I am not sure if python3-build is the relevant package for the bug; 
however I could not find out more from the output. Please re-assign if 
required.

Bug#1052045: ITP: rust-ed25519-dalek -- fast and efficient ed25519 EdDSA key handling

[Jonas Smedegaard]

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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: rust-ed25519-dalek
  Version : 2.0.0
  Upstream Contact: isis agora lovecruft 
* URL : https://github.com/dalek-cryptography/curve25519-dalek
* License : BSD-3-clause
  Programming Lang: Rust
  Description : fast and efficient ed25519 EdDSA key handling

 ed25519-dalek is a fast and efficient Rust implementation
 of ed25519 key generation, signing, and verification.
 .
 Edwards-curve Digital Signature Algorithm (EdDSA)
 is a digital signature scheme
 using the elliptic curve Curve25519.

This package will be maintained in the collaborative debian section of
Salsa, at .
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmUFtw0ACgkQLHwxRsGg
ASEMeA//V6RHC+y4TRyY4rUBxyRY0IXq7kj7FQhvOIt/jSrOx6Vc5yKFimb5Zd9n
QpJ98CQxuIpx+EGA5bX54iiQBrDzU/1gwJ1NS3KsugwN2/xzh67s3kbNgxMGDewl
JUntRsg1SI2en5P+ZqlQjtmlbqQuB7+9rVUsb6LSGxsnK842c3/0Y7tdNNomrNkH
TIUrhW0PKRdGjX3QtELsQlySotdUNp5i36UhRPOOz06ltTPWu9f23w8f5hfILd0Q
va2Rx76t7JpMafgL4MRoRr70HiiiPm5HGdLUk+pCrzUNLsv4kWKAOAFkC+dtda31
2wboqzReGhpu0eagZkxZtqRPpeGv4/0YWlwJwb1Xr5H/yMcIfa6OGTUDppCELk2a
HCdCb06MljwC9NK6wnyMg3gPhgL8JcYjeRwP8gymevOg4X5joE9l5NXFRaxGOBo/
JT7V9PlzR5lHajVYvX/B9lbqAwxhtXTgD4ntBZWZWNOzjSWUHPnLvG8FNRQaZYAs
cDsxQ8n8VYQlKbSEhNc8NXmbqhTX7DmvNNgitSM77su8dL5dIZ91r3kvxlTtquuy
MENFshzg5PSYjul0WP1PjI0nYnsx2EJf7HzHINiSkIZ+Oayx16KcMu59OFemuJm4
Pb/11kljMaI9ELf5MfZOXIFhnbM/rS077bC7QpxfTXlzZgfToP8=
=u5Ku
-END PGP SIGNATURE-

Bug#1037400: spacefm: build-depends on transitional package libgdk-pixbuf2.0-dev

[Bastian Germann]

On Mon, 12 Jun 2023 11:55:56 +0100 Simon McVittie wrote:

If this package only requires functionality from gdk-pixbuf-2.0.pc
and , please update the build-dependency to
libgdk-pixbuf-2.0-dev.

If it also requires the Xlib integration gdk-pixbuf-xlib-2.0.pc and
 (unlikely), then you can also build-depend on
libgdk-pixbuf-xlib-2.0-dev until the package can be updated to remove
that requirement.


Only libgdk-pixbuf-2.0-dev is required. Please update the package.

Bug#1052012: plasma-workspace: sddm presents a white screen with no background nor buttons

[Miguel A. Rojas]

Hi,

When I described it as "horrible", I wanted to mean what you described 
(very small size and each character is 1 pixel or less, ;)). In my case, 
I have no background either and the button to select between X11 and 
Wayland can't be seen.


# ls -l /usr/share/sddm/themes/debian-breeze(4:5.27.7-2)
total 32
-rw-r--r-- 1 root root 23515 Aug  7 16:42 Main.qml
-rw-r--r-- 1 root root   543 Aug  7 16:42 metadata.desktop
-rw-r--r-- 1 root root   209 Aug  7 16:42 theme.conf


# ls -l /usr/share/sddm/themes/debian-breeze(4:5.27.8-1)
total 24
-rw-r--r-- 1 root root 23515 Sep 13 22:24 Main.qml

At least, metadata.desktop and theme.conf have disappeared with the new 
version of the package. When you restored those files from the previous 
packages, sddm seems to work fine (I haven't done any additional testing 
beside that the screen seems to look as it was).


Regards

On 16/9/23 12:55, Alexis Murzeau wrote:

Hi,

On Sat, 16 Sep 2023 00:55:12 +0200 Miguel Angel Rojas 
 wrote:

Hi there,

Downgrading the following packages:

   - sddm-themes-breeze
   - sddm-theme-debian-breeze

to version 4:5.27.7-2 makes sddm fully usable again with no issues.

It seems some changes have been made on version 4:5.27.8-1 that have 
broken

sddm.

I hope this helps.

Regards



I have issues too with sddm-theme-debian-breeze 5.27.8-1, but the 
symptom is different.
I get a correct screen, but the password field has a very small font 
size and each character is 1 pixel.


Using diffoscope, it appears sddm-theme-debian-breeze 5.27.8-1 doesn't 
have the theme.conf file.
Adding back theme.conf from version 5.27.7-2 with 5.27.8-1 installed 
fix the issue for me.


Note: metadata.desktop was also removed in 5.27.8-1, maybe it 
shouldn't too.



@Miguel, can you try to do the same to check if theme.conf is also the 
cause of your issues ?


That is, adding `/usr/share/sddm/themes/debian-breeze/theme.conf` with 
this content:


```
[General]
showlogo=hidden
logo=/usr/share/sddm/themes/breeze/default-logo.svg
type=image
color=#1d99f3
fontSize=10
background=/usr/share/desktop-base/active-theme/login/background.svg
needsFullUserModel=false
```


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

Kernel: Linux 6.5.0-1-amd64 (SMP w/4 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)

Versions of packages sddm-theme-debian-breeze depends on:
ii  plasma-framework   5.107.0-1
ii  plasma-workspace   4:5.27.8-1
ii  sddm-theme-breeze  4:5.27.8-1

Versions of packages sddm-theme-debian-breeze recommends:
ii  desktop-base  12.0.6+nmu1
ii  sddm  0.20.0-1

sddm-theme-debian-breeze suggests no packages.

-- no debconf information

Bug#1051719: markdown-mode.el produces excessive warnings

[David Bremner]

Nicholas D Steeves  writes:
>
> David, do you think you'll be able to find time for this or do you want me
> to come back to it in a week or so?

I'm not likely to look at it soon, go ahead.

d

Bug#1051374: breaks existing setups using /etc/default/mini-httpd

[Alexandru Mihail]

Hello, 
> 
> > > 
> > > If possible it would of course be nice if the systemd service
> > > would not break
> > > user's setups and would continue to consume /etc/default/mini-
> > > httpd.
> > 
> > this issue has now made the mmdebstrap jenkins job fail for 10 days
> > in a row:
> > 
> > https://jenkins.debian.net/job/mmdebstrap-jenkins-worker/
I can confirm the issue and this will be addressed. This is NOT
intentional, thus no NEWS entry will be added.

> 
> > Or will you restore
> > compatibility with existing setups using /etc/default/mini-httpd so
> > that I
> > need to do nothing and just wait for an upload fixing this?
> 
Yes, this is the intended course of action.
> I asked in #debian-systemd and the fix could be as simple as setting
> the
> following in the .service file:
> 
> EnvironmentFile=-/etc/default/mini-httpd
> 
> Can you confirm?
I will test this and get back to you as soon as I can confirm the fix.
Documentation on /etc/default/mini-httpd options is rather scarce, do
you mind posting a minimal /etc/default/mini-httpd file with which I
could confirm the fix (a path or port setting perhaps)? It would speed
up my work here as the package does not provide a default one.
> 
> Thanks!
> 
> cheers, josch
Cheers,
Alexandru Mihail



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

Bug#1051219: ITA: gumbo-parser -- pure-C HTML5 parser

[Bastian Germann]

Control: retitle -1 ITA: gumbo-parser -- pure-C HTML5 parser
Control: owner -1 Aymeric Agon-Rambosson 

On Mon, 11 Sep 2023 00:23:23 +0200 Aymeric Agon-Rambosson wrote:
I have forked the salsa repo to 
https://salsa.debian.org/ricorambo/gumbo-parser, where my changes 
are (new upstream versions and minor packaging improvements).


I have decided to import another upstream 
(https://codeberg.org/grisha/gumbo-parser) according to the 
recommendation of Mr. Kirillov (the upstream maintainer), which I 
preferred to the idea of Mr. Lefevre to follow sigil-gumbo.


That is okay.

However, it turns out that Mr. Kirillov bumped the shared library 
version in the last release. I changed the binary package name 
accordingly (libgumbo1 to libgumbo2), along with the symbols file, 
but since I am only Debian Maintainer 
(DC184C7074DC4FD338D86CF97E32B4D596D6F8F6), I don't think I will 
be able to upload (If I'm not mistaken, the package will have to 
go through NEW because of the new libgumbo2 binary package). Would 
it be possible for you to upload my changes to the archive (if you 
agree with them, of course) ?


If you grant me access to the salsa repo, I'll push my changes to 
it.


Please push your changes and make it an experimental upload.
When that is done, please ping me again so that I can upload the pkg.
Please do not forget to push an upstream/... tag.

After the experimental version is uploaded, you will have to request
a transition slot from the release team.

Bug#1052040: mmm-mode: post-install script fails

[Vincent Lefevre]

Ditto here.

On 2023-09-16 14:31:11 +0200, mister...@web.de wrote:
> In toplevel form:
> mmm-auto.el:178:4: Error: Wrong number of arguments: (3 . 4), 2

This seems to be due to this change:

-(defalias 'mmm-add-find-file-hooks #'mmm-add-find-file-hook)
+(if (not (string-match "XEmacs" (emacs-version)))
+(define-obsolete-function-alias 'mmm-add-find-file-hooks 
'mmm-add-find-file-hook
+  "0.3.8"
+  "Both `mmm-add-find-file-hooks' and `mmm-add-find-file-hook' are 
deprecated.")
+  (define-obsolete-function-alias 'mmm-add-find-file-hooks 
'mmm-add-find-file-hook))

If I understand correctly, the second define-obsolete-function-alias
(with 2 arguments) is executed instead of the first one (with 4
arguments). This would mean that

  (string-match "XEmacs" (emacs-version))

finds a match. Is there any reason?

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1051219: ITA: gumbo-parser -- pure-C HTML5 parser

[Bastian Germann]

Oh, and please make the CI pipeline run by adding repacksuffix=+dfsg to 
d/watch's opts.
You can also get rid of the filenamemangle.

Bug#1052040: mmm-mode: post-install script fails

[Vincent Lefevre]

On 2023-09-16 16:53:33 +0200, Vincent Lefevre wrote:
> If I understand correctly, the second define-obsolete-function-alias
> (with 2 arguments) is executed instead of the first one (with 4
> arguments). This would mean that
> 
>   (string-match "XEmacs" (emacs-version))
> 
> finds a match. Is there any reason?

Actually, it doesn't.

This appears to be related to macro expansion, which seems to
occur even if the code is not executed.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1052046: RM: Time to remove from unstable too?

[Ben Tris]

Package: mutextrace
Severity: normal
X-Debbugs-Cc: benatt...@gezapig.nl, m...@qa.debian.org

Dear Maintainer,

This package was removed from testing in 2016.
No vcs or website to be found.


-- 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-12-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1052047: libreoffice-calc: background color not (always) rendered

[Fabrice Aeschbacher]

Package: libreoffice-calc
Version: 4:7.4.7-1
Severity: normal
X-Debbugs-Cc: fabrice.aeschbac...@gmail.com

Dear Maintainer,

Please note that I'm unsure whether the bug should be filled against 
xfce4 or

libreoffice-calc.

I'm running libreoffice-calc under XFCE4 with default theme (High Contrast)

- If I set the cell background color to any color except white, say 
"yellow",

the cell's background color stays white.

- When clicking "File => Print Preview", the cell's background stays white.

- Under "Tools => Options => Accessibility", if I unselect "Use system 
colors

for page previews", the cell's background is rendered correctly (yellow) in
Print Preview, but not in the sheet.

- In XFCE Settings => Appearance, If I change the default style (High 
Contrast)

to say Adwaita (which is another style installed by default), the cell's
background  is rendered correctly, in the sheet like in Print Preview.

The bug happens in versions 4:7.4.7-1 (bookworm) and also with
4:7.5.6-1~bpo12+1 (bookworm-backports). It used to work fine with 
bullseye versions.



-- Package-specific info:
Configuration file    Package Exists Changed
/etc/libreoffice/registry/calc.xcd    libreoffice-calc Yes No
All deployed bundled extensions:


All deployed shared extensions:


All deployed user extensions:



Experimental features enabled:

Installed VCLplugs:
Desired=Unknown/Install/Remove/Purge/Hold
| 
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend

|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version  Architecture Description
+++----===
ii  libreoffice-gtk3 4:7.4.7-1    amd64    office productivity suite 
-- GTK+ 3 integration

un  libreoffice-kf5        (no description available)
un  libreoffice-qt5        (no description available)

-- 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/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER
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 libreoffice-calc depends on:
ii  coinor-libcoinmp1v5  1.8.3-3
ii  libc6    2.36-9+deb12u1
ii  libetonyek-0.1-1 0.1.10-3+b1
ii  libgcc-s1    12.2.0-14
ii  libicu72 72.1-3
ii  libmwaw-0.3-3    0.3.21-1
ii  libodfgen-0.1-1  0.1.8-2
ii  liborcus-0.17-0  0.17.2-2+b2
ii  liborcus-parser-0.17-0   0.17.2-2+b2
ii  libreoffice-base-core    4:7.4.7-1
ii  libreoffice-common   4:7.4.7-1
ii  libreoffice-core 4:7.4.7-1
ii  librevenge-0.0-0 0.0.5-3
ii  libstaroffice-0.0-0  0.0.7-1
ii  libstdc++6   12.2.0-14
ii  libuno-cppu3 4:7.4.7-1
ii  libuno-cppuhelpergcc3-3  4:7.4.7-1
ii  libuno-sal3  4:7.4.7-1
ii  libuno-salhelpergcc3-3   4:7.4.7-1
ii  libwps-0.4-4 0.4.13-1
ii  libxml2  2.9.14+dfsg-1.3~deb12u1
ii  lp-solve 5.5.2.5-2
ii  ucf  3.0043+nmu1
ii  uno-libs-private 4:7.4.7-1

libreoffice-calc recommends no packages.

Versions of packages libreoffice-calc suggests:
ii  ocl-icd-libopencl1  2.3.1-1

Versions of packages libreoffice-core depends on:
ii  fontconfig  2.14.1-4
ii  fonts-opensymbol    4:102.12+LibO7.4.7-1
ii  libabsl20220623 20220623.1-1
ii  libboost-locale1.74.0   1.74.0+ds1-21
ii  libc6   2.36-9+deb12u1
ii  libcairo2   1.16.0-7
ii  libclucene-contribs1v5  2.3.3.4+dfsg-1.1
ii  libclucene-core1v5  2.3.3.4+dfsg-1.1
ii  libcups2    2.4.2-3+deb12u1
ii  libcurl3-gnutls 7.88.1-10+deb12u1
ii  libdbus-1-3 1.14.8-2~deb12u1
ii  libdconf1   0.40.0-4
ii  libeot0 0.01-5+b1
ii  libepoxy0   1.5.10-1
ii  libexpat1   2.5.0-1
ii  libexttextcat-2.0-0 3.4.5-1
ii  libfontconfig1  2.14.1-4
ii  libfreetype6    2.12.1+dfsg-5
ii  libgcc-s1   12.2.0-14
ii  libglib2.0-0    2.74.6-2
ii  libgpgmepp6 1.18.0-3+b1
ii  libgraphite2-3  1.3.14-1
ii  libgstreamer-plugins-base1.0-0  1.22.0-3+deb12u1
ii  libgstreamer1.0-0   1.22.0-2
ii  libharfbuzz-icu0    6.0.0+dfsg-3
ii  libharfbuzz0b   6.0.0+dfsg-3
ii  libhunspell-1.7-0   1.7.1-1
ii  libhyphen0  2.8.8-7
ii  libice6 2:1.0.10-1
ii  libicu

Bug#1037570: afnix: ftbfs with GCC-13

[Jonathan Bergh]

Control: tags -1 + patch

Fixes FTBFS with gcc-13 and closes 1037570


patch1.debdiff
Description: Binary data

Bug#1052048: texlive-bibtex-extra: Can't generate bibliography since last upgrade at trixie

[Mechtilde Stehmann]

Package: texlive-bibtex-extra
Version: 2023.20230613-2
Severity: grave
X-Debbugs-Cc: mechti...@debian.org

After last update at trixie I can't proper build https://salsa.debian.org/ddp-
team/dpb/ locally.

It builds correct on trixie at the Salsa CI at 03.09.2023. The last upload to
trixie was at 05.09.2023.

I lost the bibliography in the pdf of this big document.

That's why I set it to grave.

Kind regards

Mechtilde


-- Package-specific info:
IMPORTANT INFORMATION: We will only consider bug reports concerning
the packaging of TeX Live as relevant. If you have problems with
combination of packages in a LaTeX document, please consult your
local TeX User Group, the comp.text.tex user group, the author of
the original .sty file, or any other help resource. 

In particular, bugs that are related to up-upstream, i.e., neither
Debian nor TeX Live (upstream), but the original package authors,
will be closed immediately.

   *** The Debian TeX Team is *not* a LaTeX Help Desk ***

If you report an error when running one of the TeX-related binaries 
(latex, pdftex, metafont,...), or if the bug is related to bad or wrong
output, please include a MINIMAL example input file that produces the
error in your report.

Please run your example with
(pdf)latex -recorder ...
(or any other program that supports -recorder) and send us the generated
file with the extension .fls, it lists all the files loaded during
the run and can easily explain problems induced by outdated files in
your home directory.

Don't forget to also include minimal examples of other files that are 
needed, e.g. bibtex databases. Often it also helps
to include the logfile. Please, never send included pictures!

If your example file isn't short or produces more than one page of
output (except when multiple pages are needed to show the problem),
you can probably minimize it further. Instructions on how to do that
can be found at

http://www.minimalbeispiel.de/mini-en.html (english)

or 

http://www.minimalbeispiel.de/mini.html (german)

##
minimal input file


##
other files

##
 List of ls-R files

-rw-r--r-- 1 root root 1956 Sep 10 08:48 /var/lib/texmf/ls-R
lrwxrwxrwx 1 root root 29 Oct 12  2022 /usr/share/texmf/ls-R -> 
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 31 Aug 27 23:39 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
lrwxrwxrwx 1 root root 31 Aug 27 23:39 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
##
 Config files
-rw-r--r-- 1 root root 475 Oct 18  2022 /etc/texmf/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 Aug 27 23:39 /usr/share/texmf/web2c/fmtutil.cnf -> 
/var/lib/texmf/fmtutil.cnf-DEBIAN
lrwxrwxrwx 1 root root 32 Aug 27 23:39 /usr/share/texmf/web2c/updmap.cfg -> 
/var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 3197 Sep 10 08:47 
/var/lib/texmf/tex/generic/config/language.dat
##
 Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 Sep  4  2021 mktex.cnf
-rw-r--r-- 1 root root 475 Oct 18  2022 texmf.cnf
##
 md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c  /etc/texmf/texmf.d/00debian.cnf

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (400, 'testing'), (300, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.4.0-4-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 texlive-bibtex-extra depends on:
ii  tex-common  6.18
ii  texlive-base2023.20230613-3
ii  texlive-binaries2023.20230311.66589-4
ii  texlive-latex-base  2023.20230613-3

texlive-bibtex-extra recommends no packages.

texlive-bibtex-extra suggests no packages.

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

Versions of packages tex-common suggests:
ii  debhelper  13.11.6

Versions of packages texlive-bibtex-extra is related to:
ii  tex-common6.18
ii  texlive-binaries  2023.20230311.66589-4

-- no debconf information

Bug#1043836: cmospwd: Fails to build source after successful build

[Bastian Germann]

I am uploading a NMU to DELAYED/10 in order to fix this.
The debdiff is attached.diff -Nru cmospwd-5.0+dfsg/debian/changelog cmospwd-5.0+dfsg/debian/changelog
--- cmospwd-5.0+dfsg/debian/changelog   2010-05-10 14:55:37.0 +
+++ cmospwd-5.0+dfsg/debian/changelog   2023-09-16 11:44:58.0 +
@@ -1,3 +1,13 @@
+cmospwd (5.0+dfsg-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Update maintainer field and unset DMUA
+  * Drop kfreebsd from Architectures and patches (Closes: #1052036)
+  * d/watch: Scan HTTPS
+  * Clean binary (Closes: #1043836)
+
+ -- Bastian Germann   Sat, 16 Sep 2023 11:44:58 +
+
 cmospwd (5.0+dfsg-2) unstable; urgency=low
 
   * Include fix for FTBFS on KFreeBSD (Closes: #580673) 
diff -Nru cmospwd-5.0+dfsg/debian/clean cmospwd-5.0+dfsg/debian/clean
--- cmospwd-5.0+dfsg/debian/clean   1970-01-01 00:00:00.0 +
+++ cmospwd-5.0+dfsg/debian/clean   2023-09-16 11:44:58.0 +
@@ -0,0 +1 @@
+src/cmospwd
diff -Nru cmospwd-5.0+dfsg/debian/control cmospwd-5.0+dfsg/debian/control
--- cmospwd-5.0+dfsg/debian/control 2010-05-10 14:55:37.0 +
+++ cmospwd-5.0+dfsg/debian/control 2023-09-16 11:44:58.0 +
@@ -1,15 +1,14 @@
 Source: cmospwd
 Section: utils
 Priority: optional
-Maintainer: Luke Faraone 
+Maintainer: Luke Faraone 
 Build-Depends: cdbs (>= 0.4.49), debhelper (>= 7)
 Standards-Version: 3.8.4
-DM-Upload-Allowed: yes
 Vcs-Bzr: https://code.launchpad.net/~lfaraone/cmospwd/debian
 Homepage: http://www.cgsecurity.org/wiki/CmosPwd
 
 Package: cmospwd
-Architecture: amd64 i386 kfreebsd-amd64 kfreebsd-i386 
+Architecture: amd64 i386
 Depends: ${shlibs:Depends},  ${misc:Depends},
 Description: decrypt BIOS passwords from CMOS
  CmosPwd is a cross-platform tool to decrypt password stored in CMOS used 
@@ -18,4 +17,3 @@
  This application should work out of the box on most modern systems, but 
  some more esoteric BIOSes may not be supported or may require additional 
  steps. 
- 
diff -Nru cmospwd-5.0+dfsg/debian/patches/ftbfs_kfreebsd.patch 
cmospwd-5.0+dfsg/debian/patches/ftbfs_kfreebsd.patch
--- cmospwd-5.0+dfsg/debian/patches/ftbfs_kfreebsd.patch2010-05-10 
14:55:37.0 +
+++ cmospwd-5.0+dfsg/debian/patches/ftbfs_kfreebsd.patch1970-01-01 
00:00:00.0 +
@@ -1,51 +0,0 @@
 a/src/cmospwd.c
-+++ b/src/cmospwd.c
-@@ -37,7 +37,11 @@
- #define HAVE_SYS_IO_H 1
- #endif
- 
--#ifdef __FreeBSD__
-+#if defined(__FreeBSD__) && ! defined(__FreeBSD_kernel__)
-+# define __FreeBSD_kernel__ __FreeBSD__
-+#endif
-+
-+#ifdef __FreeBSD_kernel__
- #define HAVE_CTYPE_H 1
- #endif
- 
-@@ -181,7 +185,7 @@
- #define GWIOPM_PARAMCOUNT 3// for most functions
- #define GWIOPM_PARAMCOUNT_BYTES GWIOPM_PARAMCOUNT * 4  // for most functions
- 
--#elif defined(__FreeBSD__)
-+#elif defined(__FreeBSD_kernel__)
- FILE *cmos_fd;
- #endif
- 
-@@ -358,7 +362,7 @@
- };
- 
- 
--#if 
defined(__linux__)||defined(__FreeBSD__)||defined(__NetBSD__)||defined(__CYGWIN32__)||defined(__MINGW32__)
-+#if 
defined(__linux__)||defined(__FreeBSD_kernel__)||defined(__NetBSD__)||defined(__CYGWIN32__)||defined(__MINGW32__)
- static __inline__ void outportb(uint16_t port,uint8_t value)
- {
-   __asm__ volatile ("outb %0,%1"
-@@ -1471,7 +1475,7 @@
- perror("i386_iopl");
- exit(1);
-   }
--#elif defined(__FreeBSD__)
-+#elif defined(__FreeBSD_kernel__)
- cmos_fd = fopen("/dev/io", "r");
- if(cmos_fd==NULL){
-perror("fopen /dev/io failed");
-@@ -1485,7 +1489,7 @@
- {
- #ifdef __linux__
-   ioperm(PORT_CMOS_0,4*2,0);
--#elif defined(__FreeBSD__)
-+#elif defined(__FreeBSD_kernel__)
-   fclose(cmos_fd);
- #endif
- }
diff -Nru cmospwd-5.0+dfsg/debian/patches/series 
cmospwd-5.0+dfsg/debian/patches/series
--- cmospwd-5.0+dfsg/debian/patches/series  2010-05-10 14:55:37.0 
+
+++ cmospwd-5.0+dfsg/debian/patches/series  1970-01-01 00:00:00.0 
+
@@ -1 +0,0 @@
-ftbfs_kfreebsd.patch
diff -Nru cmospwd-5.0+dfsg/debian/watch cmospwd-5.0+dfsg/debian/watch
--- cmospwd-5.0+dfsg/debian/watch   2010-05-10 14:55:37.0 +
+++ cmospwd-5.0+dfsg/debian/watch   2023-09-16 11:44:58.0 +
@@ -1,3 +1,3 @@
 version=3
 opts=dversionmangle=s/\+dfsg$// \
-http://www.cgsecurity.org/wiki/CmosPwd 
http://www.cgsecurity.org/cmospwd-(.*)\.tar\.bz2
+https://www.cgsecurity.org/wiki/CmosPwd 
https://www.cgsecurity.org/cmospwd-(.*)\.tar\.bz2

Bug#1052049: bacula-director: Please amend bacula-dir.conf to include subfiles

[Niels S. Richthof]

Package: bacula-director
Version: 9.6.7-7
Severity: wishlist

Dear Maintainer,

The bacula director configuration file can get very big and messy, especially 
when backing up many clients.

bacula-director supports the inclusion of subfiles in configuration files,
as documented here:
https://www.bacula.org/9.6.x-manuals/en/main/Customizing_Configuration_F.html#SECTION002023000
(This is also the case in all newer upstream versions.)

Therefore, could you please, in keeping with the way other Debian packages are 
doing this:

1. Create a new (empty) directory "/etc/bacula/bacula-dir.conf.d/"
2. Add the following snipped to "/etc/bacula/bacula-dir.conf":

   # Include subfiles associated with configuration of clients.
   # They define the bulk of the Clients, Jobs, and FileSets.
   # Remember to "reload" the Director after adding a client file.
   #
   @|"sh -c 'for f in /etc/bacula/bacula-dir.conf.d/*.conf ; do echo @${f} ; 
done'"


Thank you
Niels

-- 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 5.10.0-23-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages bacula-director depends on:
ii  bacula-common  9.6.7-7
ii  bacula-director-mysql  9.6.7-7
ii  bsd-mailx [mailx]  8.1.2-0.20220412cvs-1
ii  init-system-helpers1.65.2
ii  libc6  2.36-9+deb12u1
ii  libstdc++6 12.2.0-14
ii  sysvinit-utils 3.06-4
ii  ucf3.0043+nmu1

bacula-director recommends no packages.

Versions of packages bacula-director suggests:
pn  bacula-doc  

-- no debconf information

Bug#1052050: multiple problem with GTK3 enabled

[Mikhail Kshevetskiy]

Package: lxpanel
Version: 0.10.1-4
Severity: important
Tags: patch
X-Debbugs-Cc: ChangZhuo Chen (陳昌倬) 

There are a lot of issues with GTK3 version of lxpanel that makes it almost
unusable. The following patches required to apply to fix an issues:
 * 02-Correct-icon-grid-width-under-GTK3.-Fixes-Github-29.patch
 * 03-Correct-panel-size-under-GTK3.-Fixes-Sourceforge-773.patch
 * 04-Support-HiDPI-on-GTK-3.patch
 * 05-Highlight-selected-workspace-in-pager.patch
 * 06-fix-alsa-volume-issue.patch
 * 07-Fix-division-by-zero-with-broken-batteries.patch
 * 08-Use-XkbRF_GetNamesProp-instead-of-xkb_symbols.patch

This patches was taken from https://github.com/lxde-continued/lxpanel.git.
You may look there for more patches/details.

Mikhail Kshevetskiy

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

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

Versions of packages lxpanel depends on:
ii  libasound2   1.2.9-2
ii  libc62.37-8
ii  libcairo21.17.8-3
ii  libcurl3-gnutls  8.2.1-2
ii  libfm-gtk3-4 1.3.2-4
ii  libfm-modules1.3.2-4
ii  libfm4   1.3.2-4
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libglib2.0-0 2.78.0-1
ii  libgtk-3-0   3.24.38-5
ii  libiw30  30~pre9-14
ii  libkeybinder-3.0-0   0.3.2-1.1
ii  libmenu-cache3   1.1.0-1.1
ii  libpango-1.0-0   1.51.0+ds-2
ii  libwnck-3-0  43.0-3
ii  libx11-6 2:1.8.6-1
ii  libxkbfile1  1:1.1.0-1
ii  libxml2  2.9.14+dfsg-1.3
ii  lxmenu-data  0.1.5-2.1
ii  lxpanel-data 0.10.1-4

Versions of packages lxpanel recommends:
ii  foot [x-terminal-emulator]  1.15.3-1
ii  gnome-flashback [notification-daemon]   3.49.1-1+b1
ii  gnome-shell [notification-daemon]   44.4-1
ii  gnome-terminal [x-terminal-emulator]3.49.99-1
ii  konsole [x-terminal-emulator]   4:22.12.3-1
ii  libnotify-bin   0.8.2-1
ii  mate-notification-daemon [notification-daemon]  1.26.0-1
ii  mate-terminal [x-terminal-emulator] 1.26.1-1
ii  pavucontrol 5.0-2
ii  plasma-workspace [notification-daemon]  4:5.27.7-2
ii  xfce4-notifyd [notification-daemon] 0.8.2-1
ii  xfce4-terminal [x-terminal-emulator]1.1.0-1
ii  xkb-data2.38-2
ii  xterm [x-terminal-emulator] 384-1

Versions of packages lxpanel suggests:
ii  dillo [www-browser]3.0.5-7+b1
ii  firefox-esr [www-browser]  115.2.0esr-1
ii  konqueror [www-browser]4:22.12.3-2
ii  links [www-browser]2.29-1
ii  lynx [www-browser] 2.9.0dev.12-1

-- no debconf information
>From 3c1ad6bc7c8b4b3ba66c04e6e10aa741f028ba75 Mon Sep 17 00:00:00 2001
From: Ben Walsh 
Date: Mon, 7 Feb 2022 07:02:05 +
Subject: [PATCH] Correct icon-grid width under GTK3. Fixes Github #29.

---
 src/icon-grid.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/icon-grid.c b/src/icon-grid.c
index 2177971e..5948fee6 100644
--- a/src/icon-grid.c
+++ b/src/icon-grid.c
@@ -392,7 +392,7 @@ static void panel_icon_grid_get_preferred_width(GtkWidget *widget,
 }
 panel_icon_grid_size_request(widget, &requisition);
 if (minimal_width)
-*minimal_width = requisition.width;
+*minimal_width = ig->constrain_width ? 2 : requisition.width;
 if (natural_width)
 *natural_width = requisition.width;
 }
-- 
2.40.1

>From 12576de7b83c634437217e23d74954070a1be2d5 Mon Sep 17 00:00:00 2001
From: Ben Walsh 
Date: Sat, 6 Jun 2020 10:38:15 +0100
Subject: [PATCH] Correct panel size under GTK3. Fixes Sourceforge #773.

---
 src/panel.c | 7 +++
 1 file changed, 7 insertions(+)

diff --git a/src/panel.c b/src/panel.c
index 45188dbe..2b5fc9be 100644
--- a/src/panel.c
+++ b/src/panel.c
@@ -293,6 +293,12 @@ lxpanel_get_preferred_height (GtkWidget *widget,
   if (natural_height)
   *natural_height = requisition.height;
 }
+
+static GtkSizeRequestMode
+lxpanel_get_request_mode (GtkWidget *widget)
+{
+return GTK_SIZE_REQUEST_CONSTANT_SIZE;
+}
 #endif
 
 static void lxpanel_size_allocate(GtkWidget *widget, GtkAllocation *a)
@@ -413,6 +419,7 @@ static void lxpanel_class_init(PanelToplevelClass *klass)
 #if GTK_CHECK_VERSION(3, 0, 0)
 widget_class->get_preferred_width = lxpanel_get_preferred_width;
 widget_class->get_preferred_height = lxpanel_get_preferred_height;
+widget_class->get_request_mode = lxpanel_get_request_mode;
 #else
 widget_class->size_request = lxpanel_size_request;
 #endif
-- 
2.40.1

>From

Bug#1052051: sagemath: Sagemath 9.5-6 expects libsingular-Singular-4.3.1.so but libsingular-Singular-4.3.2.so is installed

[jagv]

Package: sagemath
Version: 9.5-6
Severity: normal

Dear Maintainer,

   * What led up to the situation?
Typing "sage" and pressing Enter

   * What was the outcome of this action?
Sagemath did not start

   * What outcome did you expect instead?
Sagemath should start

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


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

Kernel: Linux 6.4.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.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 sagemath depends on:
ii  python3   3.11.4-5+b1
ii  python3-sage  9.5-6

Versions of packages sagemath recommends:
ii  sagemath-doc9.5-6
ii  sagemath-jupyter9.5-6
ii  sagetex 3.6.1+ds-1
ii  texlive-latex-base  2023.20230613-3

Versions of packages sagemath suggests:
pn  dot2tex  
pn  gap-design   
ii  gap-factint  1.6.3+ds-2
pn  gap-grape
pn  gap-guava
ii  gap-laguna   3.9.6+ds-1
pn  gap-sonata   
pn  gap-toric

-- no debconf information

Bug#986736: RFP: xmake -- A cross-platform build utility based on Lua

[Bastian Germann]

xmake was once part of Debian and was deliberately removed because it was not 
used.
If you want to package software that actually uses xmake please indicate this by blocking this ITP 
by that software's RFP/ITP bug.

Bug#1052048: texlive-bibtex-extra: Can't generate bibliography since last upgrade at trixie

[Preuße]

On 16.09.2023 17:16, Mechtilde Stehmann wrote:

Hello Mechtilde,


After last update at trixie I can't proper build https://salsa.debian.org/ddp-
team/dpb/ locally.

It builds correct on trixie at the Salsa CI at 03.09.2023. The last upload to
trixie was at 05.09.2023.

Do you have some kind of log file, showing an error message? Please 
don't send files having a size of > 100KB.



I lost the bibliography in the pdf of this big document.

That's why I set it to grave.


For now I leave it at this severity, although I don't share you opinion.

Hilmar
--
sigfault



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1037699: intel-mediasdk: ftbfs with GCC-13

[Jonathan Bergh]

Control: tags -1 + patch

Fixes FTBFS due to gcc-13 upgrade and closes #1037699


patch1.debdiff
Description: Binary data

Bug#1052040: mmm-mode: post-install script fails

[Vincent Lefevre]

Control: forwarded -1 https://github.com/dgutov/mmm-mode/issues/137
Control: tags -1 upstream

On 2023-09-16 17:02:54 +0200, Vincent Lefevre wrote:
> This appears to be related to macro expansion, which seems to
> occur even if the code is not executed.

An easy solution would be to avoid the XEmacs form (marked as
obsolete in GNU Emacs since 23.1 and whose support was removed
in GNU Emacs 28[*]), i.e. change

(if (not (string-match "XEmacs" (emacs-version)))
(define-obsolete-function-alias 'mmm-add-find-file-hooks 
'mmm-add-find-file-hook
  "0.3.8"
  "Both `mmm-add-find-file-hooks' and `mmm-add-find-file-hook' are 
deprecated.")
  (define-obsolete-function-alias 'mmm-add-find-file-hooks 
'mmm-add-find-file-hook))

to just

(define-obsolete-function-alias 'mmm-add-find-file-hooks 'mmm-add-find-file-hook
  "0.3.8"
  "Both `mmm-add-find-file-hooks' and `mmm-add-find-file-hook' are deprecated.")

[*] https://github.com/emacs-mirror/emacs/commit/32c6732

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1052052: libreoffice-parlatype-extension: FTBFS/autopkgtest failure: needs tos (build-)depend on libreoffice-core

[Rene Engelhard]

Source: libreoffice-parlatype-extension
Version: 3.1.1-1
Severity: important

Dear Maintainer,

I see parlatype-libreoffice-extension failing with the new  upstream
release of libreoffice in experimental (see 
https://ci.debian.net/data/autopkgtest/unstable/amd64/p/parlatype-libreoffice-extension/37751215/log.gz):

 82s autopkgtest [18:31:18]: test unit-tests: [---
 83s Warning: failed to launch javaldx - java may not function correctly
 85s test_extractTimestamp 
(test_parlatype_utils.TestUtils.test_extractTimestamp)
 85s Test extractTimestamp() ... ERROR
 85s test_isValidCharacter 
(test_parlatype_utils.TestUtils.test_isValidCharacter)
 85s Test _isValidCharacter() ... ok
 85s starting LibreOffice with channel:  
pipe,name=pytest6667d0ae-50d1-11ee-8852-00163ebb4c1a
 85s Connecting to:  
uno:pipe,name=pytest6667d0ae-50d1-11ee-8852-00163ebb4c1a;urp;StarOffice.ComponentContext
 85s WARN: NoConnectException: sleeping...
 85s WARN: NoConnectException: sleeping...
 85s tearDown: calling terminate()...
 85s ...done
 85s
 85s ==
 85s ERROR: test_extractTimestamp 
(test_parlatype_utils.TestUtils.test_extractTimestamp)
 85s Test extractTimestamp()
 85s --
 85s Traceback (most recent call last):
 85s   File 
"/tmp/autopkgtest-lxc.djpobicb/downtmp/build.oGP/src/tests/test_parlatype_utils.py",
 line 61, in test_extractTimestamp
 85s text = doc.Text
 85s
 85s AttributeError: 'NoneType' object has no attribute 'Text'
 85s
 85s --
 85s Ran 2 tests in 2.082s
 85s
 85s FAILED (errors=1)
 85s Warning: failed to launch javaldx - java may not function correctly
 86s test_empty_get (test_document_link.TestUtils.test_empty_get)
 86s Get empty custom property "Parlatype" ... ERROR
 86s test_remove_and_get (test_document_link.TestUtils.test_remove_and_get)
 86s Remove custom property "Parlatype" ... ERROR
 86s test_set_and_get (test_document_link.TestUtils.test_set_and_get)
 86s Set custom property "Parlatype" ... ERROR
 86s
 86s ==
 86s ERROR: test_empty_get (test_document_link.TestUtils.test_empty_get)
 86s Get empty custom property "Parlatype"
 86s --
 86s Traceback (most recent call last):
 86s   File 
"/tmp/autopkgtest-lxc.djpobicb/downtmp/build.oGP/src/tests/test_document_link.py",
 line 48, in test_empty_get
 86s self.assertIsNone(getDocumentLink(doc))
 86s   
 86s   File 
"/usr/lib/libreoffice/share/extensions/parlatype/python/components/Parlatype.py",
 line 131, in getDocumentLink
 86s doc_prop = doc.getDocumentProperties()
 86s^
 86s AttributeError: 'NoneType' object has no attribute 'getDocumentProperties'
 86s
 86s ==
 86s ERROR: test_remove_and_get 
(test_document_link.TestUtils.test_remove_and_get)
 86s Remove custom property "Parlatype"
 86s --
 86s Traceback (most recent call last):
 86s   File 
"/tmp/autopkgtest-lxc.djpobicb/downtmp/build.oGP/src/tests/test_document_link.py",
 line 67, in test_remove_and_get
 86s setDocumentLink(doc, "http://test";)
 86s   File 
"/usr/lib/libreoffice/share/extensions/parlatype/python/components/Parlatype.py",
 line 119, in setDocumentLink
 86s doc_prop = doc.getDocumentProperties()
 86s^
 86s AttributeError: 'NoneType' object has no attribute 'getDocumentProperties'
 86s
 86s ==
 86s ERROR: test_set_and_get (test_document_link.TestUtils.test_set_and_get)
 86s Set custom property "Parlatype"
 86s --
 86s Traceback (most recent call last):
 86s   File 
"/tmp/autopkgtest-lxc.djpobicb/downtmp/build.oGP/src/tests/test_document_link.py",
 line 57, in test_set_and_get
 86s setDocumentLink(doc, "http://test";)
 86s   File 
"/usr/lib/libreoffice/share/extensions/parlatype/python/components/Parlatype.py",
 line 119, in setDocumentLink
 86s doc_prop = doc.getDocumentProperties()
 86s^
 86s AttributeError: 'NoneType' object has no attribute 'getDocumentProperties'
 86s
 86s --
 86s Ran 3 tests in 1.075s
 86s
 86s FAILED (errors=3)
 86s WARN: NoConnectException: sleeping...
 86s autopkgtest [18:31:22]: test unit-tests: ---]
 86s unit-tests   FAIL non-zero exit status 1
 86s autopkgtest [18:31:22]: test unit-tests:  - - - - - - - - - - results - - 
- - - - - - - -
 87s autop

Bug#1052027: bullseye-pu: package cargo-mozilla/0.66.0+ds1-1~deb11u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Sat, 2023-09-16 at 11:15 +0200, Emilio Pozuelo Monfort wrote:
> Following up on #1051051, this updates cargo-mozilla for the upcoming
> Firefox ESR 115. Just like for rustc-mozilla, the risk here is small
> as this package is only used to build firefox-esr and thunderbird.
> 
> I have used the resulting package to successfully build and test
> firefox-esr 115.0.2 on bullseye.
> 

Please go ahead.

Regards,

Adam

Bug#1049899: bookworm-pu: package exim4/4.96-15+deb12u2

[Adam D. Barratt]

Control: tags -1 + confirmed

On Sun, 2023-09-03 at 14:03 +0200, Andreas Metzler wrote:
> On 2023-08-16 Andreas Metzler  wrote:
> [...]
> > I would like to push another round of cherry-picked upstream fixes
> > to
> > bookworm. They have been part of the uploads to sid up to and
> > including
> > 4.96-19.
> [...]
> 
> Hello,
> 
> I had to update the update since 75_78-Fix-free-of-value-after-
> run.patch
> broke a specific expansion. While at it I also pulled the CI related
> changes from -21.
> 

Please go ahead; sorry for the delay.

Regards,

Adam

Bug#986740: forked-daapd : please package new upstream release

[Bastian Germann]

On Thu, 02 Mar 2023 23:14:10 +0100 =?ISO-8859-1?Q?S=E9bastien?= Noel 
 wrote:

Ok it's been 2 years now, without even an ACK of some sort
If there isn't any interest on your part in this package,
i'm more than willing to adopt it.


I am happy to review and sponsor your upload.
Please add yourself as Uploader and keep it in the Multimedia Team.
Also, please rename the binary package to owntone.
There is a Debian package available from upstream:
https://github.com/owntone/owntone-apt
Maybe you can use parts of it.

Bug#1051374: breaks existing setups using /etc/default/mini-httpd

[Johannes Schauer Marin Rodrigues]

Hi,

Quoting Alexandru Mihail (2023-09-16 16:40:38)
> > I asked in #debian-systemd and the fix could be as simple as setting the
> > following in the .service file:
> > 
> > EnvironmentFile=-/etc/default/mini-httpd
> > 
> > Can you confirm?
> I will test this and get back to you as soon as I can confirm the fix.
> Documentation on /etc/default/mini-httpd options is rather scarce, do
> you mind posting a minimal /etc/default/mini-httpd file with which I
> could confirm the fix (a path or port setting perhaps)? It would speed
> up my work here as the package does not provide a default one.

here is my /etc/default/mini-httpd:

START=1
DAEMON_OPTS="-h 127.0.0.1 -p 80 -u nobody -dd /mnt/cache -i 
/var/run/mini-httpd.pid -T UTF-8"

I successfully tested the following patch to the .service file:

@@ -5,7 +5,8 @@
 [Service]
 Type=forking
 PIDFile=/run/mini_httpd.pid
-ExecStart=/usr/sbin/mini_httpd -C /etc/mini-httpd.conf
+EnvironmentFile=-/etc/default/mini-httpd
+ExecStart=/usr/sbin/mini_httpd -C /etc/mini-httpd.conf $DAEMON_OPTS -i 
/run/mini_httpd.pid
 
 [Install]
 WantedBy=multi-user.target

The EnvironmentFile uses "=-" to support a non-existant
/etc/default/mini-httpd. The ExecStart line also adds a -i option to make sure
that neither /etc/mini-httpd.conf nor $DAEMON_OPTS can set -i to something that
is different from the path in PIDFile.

What do you think?

Thanks!

cheers, josch

signature.asc
Description: signature

Bug#1050928: enlightenment-data: please provide an enlightenment-portals.conf for xdg-desktop-portal

[Ross Vandegrift]

Hi Simon,

On Thu, Aug 31, 2023 at 02:20:51PM +0100, Simon McVittie wrote:
> xdg-desktop-portal 1.17.x introduces a new way to select which portals will
> be used for which desktop environments, modelled on mimeapps.list:
> 
> - each desktop environment should provide a file like
>   /usr/share/xdg-desktop-portal/enlightenment-portals.conf
> 
> - the filename is ${DESKTOP}-portals.conf where ${DESKTOP} is the desktop
>   environment's entry in $XDG_CURRENT_DESKTOP (the same as the DesktopNames
>   from /usr/share/{x,wayland-}sessions/*.desktop), folded to lower case
> 
> - sysadmins and users can override this via files named portals.conf or
>   ${DESKTOP}-portals.conf in various locations like /etc/xdg-desktop-portal
>   and ~/.config/xdg-desktop-portal
> 
> Please see portals.conf(5) or its source code
> https://github.com/flatpak/xdg-desktop-portal/blob/main/doc/portals-conf.rst
> for full details.
> 
> If I'm reading its code correctly, I think Enlightenment asks the display 
> manager
> to set XDG_CURRENT_DESKTOP to "Enlightenment"? (But if I'm wrong, please
> adjust my suggestions accordingly.)

That's correct - but I'm afraid this is the only item in this bug report that I
understand.  I tried to read the documentation you linked, but both assume
general familiarity with what's going on here.  For me, this all might as well
be greek.  :)

I don't know of any portal requirements for Enlightenment, but I'm not really
clear whether or not that's what you're asking for.  Is there a more basic
description of what this does?  How would I test a change that implemented what
you're requesting?  And what are the consequences of not doing this?

Thanks,
Ross

Bug#1051552: timg 1.4.5-1+deb12u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1051552 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: timg
Version: 1.4.5-1+deb12u1

Explanation: fix buffer overflow vulnerability [CVE-2023-40968]

Bug#1037799: opencollada: ftbfs with GCC-13

[Jonathan Bergh]

Control: tags -1 + patch

Fixes 1037799 due to change to gcc-13


patch1.debdiff
Description: Binary data

Bug#1052053: popularity-contest: race condition between the two cron jobs

[Alexandre Detiste]

Package: popularity-contest
Version: 1.77
Severity: normal

Hi,

I have been unlucky and the two instance of the cronjob
triggered at the same time, stepping on eachother feets.

(at the "savelog -c 7 popularity-contest >/dev/null" step precisely)

Can you implement some locking ?

Or alternatively #923014 will get you locking for free
on systemd running systems.


Greetings,


> PS: the error handling is well lacking in 'savelog':
>
># compress the old uncompressed log if needed
>if test -n "$datum" && test -n "$COMPRESS"; then
>$COMPRESS $COMPRESS_OPTS -- 
> "$newname".[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]
>fi


root@antec:~# journalctl  | grep popul | grep service
sep 16 17:02:28 antec systemd[1]: Starting cron-daily-popularity-contest.service
- [Cron] /etc/cron.daily/popularity-contest...
sep 16 17:02:28 antec systemd[1]: Starting 
cron-popularity-contest-root-d2f25b2334da37b6f3ef98c2dc14fad3.service
- [Cron] "56 18 * * *   roottest -x /etc/cron.daily/popularity-contest 
&& /etc/cron.daily/popularity-contest --crond"...


○ cron-daily-popularity-contest.service - [Cron] 
/etc/cron.daily/popularity-contest
 Loaded: loaded (/etc/cron.daily/popularity-contest; generated)
 Active: inactive (dead) since Sat 2023-09-16 17:05:50 CEST; 95ms ago
TriggeredBy: ● cron-daily-popularity-contest.timer
Process: 793 ExecStart=/etc/cron.daily/popularity-contest (code=exited, 
status=0/SUCCESS)
   Main PID: 793 (code=exited, status=0/SUCCESS)
CPU: 9.798s
2023-09-16T17:02:28+0200 antec systemd[1]: Starting 
cron-daily-popularity-contest.service - [Cron] 
/etc/cron.daily/popularity-contest...
2023-09-16T17:02:28+0200 antec popularity-contest[881]: gzip: 
.//popularity-contest.0: No such file or directory
2023-09-16T17:02:28+0200 antec popularity-contest[892]: mv: impossible 
d'évaluer './/popularity-contest.0.gz': Aucun fichier ou dossier de ce type
2023-09-16T17:02:28+0200 antec popularity-contest[897]: mv: impossible 
d'évaluer 'popularity-contest': Aucun fichier ou dossier de ce type
2023-09-16T17:05:50+0200 antec systemd[1]: 
cron-daily-popularity-contest.service: Deactivated successfully.
2023-09-16T17:05:50+0200 antec systemd[1]: Finished 
cron-daily-popularity-contest.service - [Cron] 
/etc/cron.daily/popularity-contest.
2023-09-16T17:05:50+0200 antec systemd[1]: 
cron-daily-popularity-contest.service: Consumed 9.798s CPU time.

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

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

Versions of packages popularity-contest depends on:
ii  debconf [debconf-2.0]  1.5.82
ii  dpkg   1.22.0

Versions of packages popularity-contest recommends:
ii  gpg2.2.40-1.1
ii  nullmailer [mail-transport-agent]  1:2.2+10~g7ed88a0-1
ii  systemd-cron [cron-daemon] 2.1.3-1

Versions of packages popularity-contest suggests:
ii  systemd-cron [anacron]  2.1.3-1
pn  tor 
pn  torsocks

-- debconf information:
* popularity-contest/participate: true
  popularity-contest/submiturls:

Bug#1037506: Bug#1037306: ITP: apycula -- Tools to generate Gowin FPGA bitstreams

[Simon Richter]

Hi Daniel,

On 06.09.23 17:50, Daniel Gröber wrote:


I've pushed apycula 0.9.0 to https://salsa.debian.org/electronics-team/apycula/



FYI: prjtrellis is also waiting for another upload to appease ftp-master
review https://salsa.debian.org/electronics-team/prjtrellis/


I've uploaded both, and made a test build with nextpnr as well, seems good.

   Simon


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1052048: Close Bug#1052048:

[Mechtilde Stehmann]

Package: texlive-bibtex-extra
Version: 2023.20230613-2

Comment: Sorry for noise



Am 16.09.23 um 17:21 schrieb Debian Bug Tracking System:

Thank you for filing a new Bug report with Debian.

You can follow progress on this Bug here: 1052048: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052048.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

As you requested using X-Debbugs-CC, your message was also forwarded to
   mechti...@debian.org
(after having been given a Bug report number, if it did not have one).

Your message has been sent to the package maintainer(s):
  Debian TeX Task Force 

If you wish to submit further information on this problem, please
send it to 1052...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.



--
Mechtilde Stehmann
## Debian Developer
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1052048: Close Bug#1052048:

[Mechtilde Stehmann]

Package: texlive-bibtex-extra
Version: 2023.20230613-2

Comment: Sorry for noise



Am 16.09.23 um 17:21 schrieb Debian Bug Tracking System:

Thank you for filing a new Bug report with Debian.

You can follow progress on this Bug here: 1052048: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052048.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

As you requested using X-Debbugs-CC, your message was also forwarded to
   mechti...@debian.org
(after having been given a Bug report number, if it did not have one).

Your message has been sent to the package maintainer(s):
  Debian TeX Task Force 

If you wish to submit further information on this problem, please
send it to 1052...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.



--
Mechtilde Stehmann
## Debian Developer
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1052054: ITP: node-sort-package-json -- Node.js library to sort package.json

[Yadd]

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

* Package name: node-sort-package-json
  Version : 2.5.1
  Upstream Contact: Keith Cirkel 
* URL : https://github.com/fisker/git-hooks-list
* License : Expat
  Programming Lang: JavaScript
  Description : Node.js library to sort package.json

node-sort-package-json is a small library useful to sort package.json files
of Node.js modules, not in alphabetic order but in logical order (starting
by name and version).

It's a dependency of node-jupyterlab and will be maintained under JS
Team umbrella.

Bug#1052055: Webkit output fully white

[R Pi]

Package: libwebkit2gtk-4.0-dev
Version: 2.42.0-1
Severity: important

I'm currently developing an app using Tauri. Since upgrading
libwebkit2gtk-4.0-dev from version 2.40.5-1~deb12u1 to version 2.42.0-1,
whenever I launch my app I'm getting the following messages:

KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
Failed to create GBM buffer of size 1024x741: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
Failed to create GBM buffer of size 1024x741: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
Failed to create GBM buffer of size 1024x741: Permission denied
Failed to create EGL images for DMABufs with file descriptors -1, -1 and -1

The output of the webkit area is fully white, otherwise the content of the
webkit viewport appears to be working underneath (ie: I can interact with my app
but simply cannot see anything).

I was able to rollback to the previous version and keep working on my project
with the following command:

sudo apt-get install libwebkit2gtk-4.0-dev=2.40.5-1~deb12u1 \
libwebkit2gtk-4.0-37=2.40.5-1~deb12u1 \
libjavascriptcoregtk-4.0-18=2.40.5-1~deb12u1 \
gir1.2-webkit2-4.0=2.40.5-1~deb12u1 \
gir1.2-javascriptcoregtk-4.0=2.40.5-1~deb12u1 \
libjavascriptcoregtk-4.0-dev=2.40.5-1~deb12u1

I am using Debian GNU/Linux trixie/sid, kernel 6.5.0-1-amd64
and libc6 2.37-10. I am running the non-free nvidia-driver 525.125.06-2.

-- 
- Romain