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

[Daniel Höpfl]

Hi Adrian,

Your answer is still faster than anything from Apple.

Just note that your links go to an unofficial repo.
The official repository is at 
.


HFS does not look like one of the projects that care about pull 
requests:



Bye,
   Daniel

On 2023-06-18 19:50, John Paul Adrian Glaubitz wrote:

Hi Daniel!

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


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


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


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

the Linux port to be complete yet.

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


My trust in Apple's feedback system is very low so I am sending the 
patch to you in the hopes

that you can forward it to Apple.


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




The patch I added should work, with offsets, on both, Debian's sources 
as well as Apple's sources.


My changes:

- Any hardlink inode with a parent other than the metadata directory 
is changed

  to have the correct parent.
  I have seen these. I can understand how this happens when a normal 
directory
  is hardlined for the first time. The journal SHOULD prevent this 
from being a

  problem but obviously this is not the case.

- Directory hardlink inodes named "temp..." get deleted.
  These directories were deleted while open when the volume was 
removed without
  unmounting. Since these directories have already been deleted, 
deleting them
  in fsck is the right thing to do. (Documented like that for files in 
the HFS+

  spec.)

- Directory hardlink inodes with names other than "temp..." or 
"dir_..." are moved

  to "lost+found".
  It would be better to rename them to "dir_..." in a first pass, 
there might still
  be valid links to them. These links are deleted by a different 
repair step and I
  did not see how to remove those other repair steps. Would probably 
lead to a bigger
  rewrite of the hardlink check code so I decided to just move these 
to l+f.

  I have never seen this anyways.

After all, none of the errors should happen in a journaled filesystem 
(directory
hardlinks require the Journal to be active). My guess is that using 
HFS+ over AFP
(as TimeMachine does) does not correctly persist the journal before 
persisting changes.
Thus loosing the connection during directory hardlink operation can 
result in partially

executed atomic operation.


Sounds like a very useful and welcome improvement. I will definitely 
incorporate this
patch once I'm ready with the new upstream version. But maybe we're 
lucky and you can

get your changes merged upstream with Apple in the mean time.

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


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

they work (sometimes).


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


Adrian


[1] https://github.com/apple-opensource/diskdev_cmds/tree/540.1
[2] https://github.com/apple-opensource/hfs
[3] https://github.com/glaubitz/hfs/tree/linux
[4] 
https://build.opensuse.org/package/show/home:glaubitz:branches:filesystems/hfsplus-tools

[5] 

Bug#1038685: plasma-nm: DNS priority is not properly set when multiple connections present

[LXYan]

Package: plasma-nm
Version: 4:5.27.5-2
Severity: normal
X-Debbugs-Cc: z00823...@outlook.com

Dear Maintainer,

   * What led up to the situation?
I have a laptop with wifi and 4G mobile network connected, and set the
wifi DNS in KDE settings, and leave the 4G DNS default. However, in the
/etc/resolve.conf, the 4G network's DNS server is listed before my wifi DNS,
even when I'm using wifi. Here is the resolve.conf:

lxyan@X1-Nano ~> cat /etc/resolv.conf
# Generated by NetworkManager
nameserver 221.6.4.66   # 4G's default DNS
nameserver 58.240.57.33 # 4G's default DNS
nameserver 223.6.6.6# wifi DNS
# NOTE: the libc resolver may not support more than 3 nameservers.
# The nameservers listed below may not be recognized.
nameserver 223.5.5.5
nameserver 172.20.10.1
nameserver 2400:3200:baba::1
nameserver 2400:3200::1
nameserver fe80::5ce9:1eff:fef3:3b64%wlp0s20f3

This lead to some apps, like apt and ping, to use 4G's DNS even when I'm using
wifi, causing a long latency when solving DNS.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I set the 4G's DNS to the same as wifi's DNS to workaround this issue.

   * What was the outcome of this action?
Issus workrounded

   * What outcome did you expect instead?
plasma-nm set the dns-priority accoring to current connection.



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

Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.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 plasma-nm depends on:
ii  kio 5.103.0-1
ii  libc6   2.36-9
ii  libglib2.0-02.74.6-2
ii  libkf5completion5   5.103.0-1
ii  libkf5configcore5   5.103.0-2
ii  libkf5configwidgets55.103.0-1
ii  libkf5coreaddons5   5.103.0-1
ii  libkf5dbusaddons5   5.103.0-1
ii  libkf5i18n5 5.103.0-1
ii  libkf5kiogui5   5.103.0-1
ii  libkf5kiowidgets5   5.103.0-1
ii  libkf5modemmanagerqt6   5.103.0-1
ii  libkf5networkmanagerqt6 5.103.0-1
ii  libkf5notifications55.103.0-1
ii  libkf5solid55.103.0-1
ii  libkf5wallet-bin5.103.0-1
ii  libkf5wallet5   5.103.0-1
ii  libkf5widgetsaddons55.103.0-1
ii  libkf5windowsystem5 5.103.0-1
ii  libnm0  1.42.4-1
ii  libopenconnect5 9.01-3
ii  libqca-qt5-22.3.5-2
ii  libqt5core5a5.15.8+dfsg-11
ii  libqt5dbus5 5.15.8+dfsg-11
ii  libqt5gui5  5.15.8+dfsg-11
ii  libqt5network5  5.15.8+dfsg-11
ii  libqt5qml5  5.15.8+dfsg-3
ii  libqt5quickwidgets5 5.15.8+dfsg-3
ii  libqt5widgets5  5.15.8+dfsg-11
ii  libqt5xml5  5.15.8+dfsg-11
ii  libstdc++6  12.2.0-14
ii  mobile-broadband-provider-info  20230416-1
ii  network-manager 1.42.4-1
ii  plasma-framework5.103.0-1
ii  qml-module-org-kde-kcoreaddons  5.103.0-1
ii  qml-module-org-kde-kirigami25.103.0-1
ii  qml-module-org-kde-prison   5.103.0-1

Versions of packages plasma-nm recommends:
ii  systemsettings  4:5.27.5-2

Versions of packages plasma-nm suggests:
pn  network-manager-fortisslvpn  
pn  network-manager-iodine   
pn  network-manager-l2tp 
pn  network-manager-openconnect  
pn  network-manager-openvpn  
pn  network-manager-pptp 
pn  network-manager-ssh  
pn  network-manager-strongswan   
pn  network-manager-vpnc 

-- no debconf information

Bug#1038673: nmu: console-setup_1.221

[Gunnar Hjalmarsson]

Control: -1 usertag + transition

On 2023-06-20 03:14, Gunnar Hjalmarsson wrote:

On 2023-06-20 01:18, Gunnar Hjalmarsson wrote:

nmu control-setup_1.221 . all . -m 'Rebuild against xkb-data 2.38-2'


Sorry about the typo. Should better be:

nmu console-setup_1.221 . all . -m 'Rebuild against xkb-data 2.38-2'

(don't do these things when you ought to sleep)


At last I realize that this is strictly a transition, and thus that I 
uploaded to unstable prematurely.


The autogenerated ben tracker looks as expected:

https://release.debian.org/transitions/html/auto-upperlimit-xkb-data.html

But the conclusion stands: Please do a binNMU of console-setup to help 
accomplish the transition.

Bug#1038684: firmware-ath9k-htc: TP-Link TL-WN722N is not reported by "iw dev".

[peter]

Package: firmware-ath9k-htc
Version: 1.4.0-106-gc583009+dfsg1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

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

   * What led up to the situation?
I'm interested to use the TP-Link TL-WN722N which has worked 
for several years in earlier Debian releases.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
As instructed in https://wiki.debian.org/ath9k_htc, I executed 
"iw dev".  The device was not reported.

   * What was the outcome of this action?
"iw dev" failed to report the device.

   * What outcome did you expect instead?
I expected to "iw dev" to report the device, as documented.

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


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

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

Versions of packages firmware-ath9k-htc is related to:
ii  network-manager  1.30.6-1+deb11u1
ii  wpasupplicant2:2.9.0-21

-- no debconf information

- 
mobile: +1 778 951 5147
VoIP:   +1 604 670 0140

Bug#1037945: bookworm-pu: package aide/aide_0.18.3-1+deb12u1

[Marc Haber]

On Wed, Jun 14, 2023 at 06:20:44PM +0100, Adam D. Barratt wrote:
> One small comment:
> 
> +if dpkg --compare-versions "$2" le 0.18.3-1; then
> +# we're updating from 0.18-3 or earlier, chown aideinit logs
> 
> That should presumably be "from 0.18.3".

In the mean time, 0.18.3-1 has reached testing. Are you ok with me
uploading 0.18.3-1+deb12u1 to bookworm-proposed-updates?

I guess that I should also file a bug for 0.17.3-4+deb11u2 because the
bullseye point release is planned earlier than the bookworm point
release, right?

Greetings
Marc

Bug#1004256: messages to dispatch+aide_cont...@tracker.debian.org get multiplied

[Marc Haber]

On Wed, Jan 26, 2022 at 06:33:25PM +0100, Marc Haber wrote:
> On Wed, Jan 26, 2022 at 03:19:12PM +0100, Raphael Hertzog wrote:
> > Let me know if the problem persists.
> 
> Will do!

It doesn't, just for the record.

Greetings
Marc

Bug#1038683: gosa-plugins-netgroups: Various PHP 8.2 warnings shown on screen / in syslog

[Mike Gabriel]

Package: gosa-plugins-netgroups
Version: 2.8~git20211022.3b6449d-4
Severity: important
Tags: patch

GOsa²'s netgroups plugin still shows various PHP 8.2 warnings when  
diving into deeper click paths.


Mike
--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpNiwG2vkJaG.pgp
Description: Digitale PGP-Signatur

Bug#1038682: Various PHP 8.2 warnings shown on screen / in syslog

[Mike Gabriel]

Package: gosa
Version: 2.8~git20230203.10abe45+dfsg-1
Severity: important
Tags: patch

GOsa² still shows various PHP 8.2 warnings and also partially breaks  
when diving into deeper click paths.


Mike

--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpY_lAIcYeIr.pgp
Description: Digitale PGP-Signatur

Bug#1038681: ITP: golang-github-bep-simplecobra -- simpler API for the popular Cobra CLI

[Anthony Fok]

Package: wnpp
Severity: wishlist
Owner: Anthony Fok 

* Package name: golang-github-bep-simplecobra
  Version : 0.3.2-1
  Upstream Author : Bjørn Erik Pedersen
* URL : https://github.com/bep/simplecobra
* License : Expat
  Programming Lang: Go
  Description : simpler API for the popular Cobra CLI

 So, Cobra (https://github.com/spf13/cobra) is a Go CLI library with a
 feature set that's hard to resist for bigger applications
 (autocompletion, docs and man pages auto generation etc.). But it's also
 complex to use beyond the simplest of applications. This package was
 built to help rewriting Hugo's (https://github.com/gohugoio/hugo)
 commands package to something that's easier to understand and maintain.

Reason for packaging: Needed by hugo v0.112.0 and up

Bug#1038680: ITP: golang-github-bep-helpers -- Go utils package with a less burdened name by @bep

[Anthony Fok]

Package: wnpp
Severity: wishlist
Owner: Anthony Fok 

* Package name: golang-github-bep-helpers
  Version : 0.4.0-1
  Upstream Author : Bjørn Erik Pedersen
* URL : https://github.com/bep/helpers
* License : Expat
  Programming Lang: Go
  Description : Go utils package with a less burdened name by @bep

 Some helper packages with some helper code that Bjørn Erik Pedersen
 (@bep) has had a tendency to copy from project to project over the years,
 prompting him to consider some reuse and create this Go package.

Reason for packaging: Needed by e.g. hugo v0.112.0 and up

Bug#1033305: chromium: try enabling use_thin_lto for faster build

[Daniel Richard G.]

In recent versions, enabling use_thin_lto causes a new linker flag to be
added, which as far as I've seen, Clang <= 15 doesn't recognize. (I have
not tested >= 16)

This is the build error I've observed:

[2789/56743] SOLINK ./libvulkan.so.1
FAILED: libvulkan.so.1 libvulkan.so.1.TOC 
"python3" "../../build/toolchain/gcc_solink_wrapper.py" --readelf="readelf" 
--nm="nm"  --sofile="./libvulkan.so.1" --tocfile="./libvulkan.so.1.TOC" 
--output="./libvulkan.so.1" -- clang++ -shared -Wl,-soname="libvulkan.so.1" 
-fuse-ld=lld -Wl,--fatal-warnings -Wl,--build-id=sha1 -fPIC -Wl,-z,noexecstack 
-Wl,-z,relro -Wl,-z,now -Wl,--icf=all -Wl,--color-diagnostics 
-Wl,-mllvm,-instcombine-lower-dbg-declare=0 -flto=thin -Wl,--thinlto-jobs=all 
-Wl,--thinlto-cache-dir=thinlto-cache 
-Wl,--thinlto-cache-policy=cache_size=10\%:cache_size_bytes=40g:cache_size_files=10
 -Wl,-mllvm,-import-instr-limit=30 -Wl,-mllvm,-disable-auto-upgrade-debug-info 
-fwhole-program-vtables -Wl,--undefined-version 
-Wl,--no-call-graph-profile-sort -m64 -no-canonical-prefixes -Wl,-O2 
-Wl,--gc-sections -rdynamic -Wl,-z,defs -Wl,--as-needed -Wl,--lto-O0 
-Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now -Wl,--stats -o 
"./libvulkan.so.1" @"./libvulkan.so.1.rsp"  
ld.lld: error: -mllvm: ld.lld: Unknown command line argument 
'-disable-auto-upgrade-debug-info'.  Try: '/usr/bin/ld.lld --help'
ld.lld: Did you mean '--disable-arm-parallel-dsp'?
clang++: error: linker command failed with exit code 1 (use -v to see 
invocation)


The following patch fixes the issue:

--- a/build/config/compiler/BUILD.gn
+++ b/build/config/compiler/BUILD.gn
@@ -726,14 +726,6 @@ config("compiler") {
   }
 
   ldflags += [ "-Wl,-mllvm,-import-instr-limit=$import_instr_limit" ]
-
-  if (!is_chromeos) {
-# TODO(https://crbug.com/972449): turn on for ChromeOS when that
-# toolchain has this flag.
-# We only use one version of LLVM within a build so there's no need to
-# upgrade debug info, which can be expensive since it runs the 
verifier.
-ldflags += [ "-Wl,-mllvm,-disable-auto-upgrade-debug-info" ]
-  }
 }
 
 # TODO(https://crbug.com/1211155): investigate why this isn't effective on


--Daniel


-- 
Daniel Richard G. || sk...@iskunk.org
My ASCII-art .sig got a bad case of Times New Roman.

Bug#1038679: bullseye node-acorn workaround breaks build on some systems

[Daniel Richard G.]

Package: chromium
Version: 114.0.5735.133-1
Severity: minor

Currently, the debian/rules file contains this bit under the
override_dh_auto_configure target:

# bullseye workarounds; delete this post-bullseye
cp -ra /usr/share/nodejs/acorn  third_party/node/node_modules/
cp -ra /usr/share/nodejs/acorn-walk third_party/node/node_modules/walk
sed -i -e "s#'acorn-walk'#'walk'#" 
third_party/node/node_modules/rollup/dist/es/shared/rollup.js
sed -i -e "s#'acorn-walk'#'walk'#" 
third_party/node/node_modules/rollup/dist/shared/rollup.js

When I build the chromium package on Ubuntu kinetic, I run into this:

# use system rollup
cp -ra /usr/share/nodejs/rollup third_party/node/node_modules/
# bullseye workarounds; delete this post-bullseye
cp -ra /usr/share/nodejs/acorn  third_party/node/node_modules/
cp: cannot stat '/usr/share/nodejs/acorn': No such file or directory
make[1]: *** [debian/rules:123: override_dh_auto_configure] Error 1
make[1]: Leaving directory '/home/build/chromium-114.0.5735.133'
make: *** [debian/rules:114: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

The /usr/share/nodejs/acorn directory comes from node-debbundle-acorn or
node-acorn. The former appears to have previously been a dependency of
the rollup package, and the latter is a direct dependency of (the much
newer) libnode108. In between, however, there is a gap in which no acorn
module is pulled in for the package build.

Solution: Either add "node-acorn | node-debbundle-acorn" to
Build-Depends, or remove the workaround from the post-bullseye suites.

(Incidentally, I was able to build the ~deb11u1 package on bullseye just
fine with the workaround disabled, so it's not clear to me that it is
still needed even there.)


--Daniel


-- 
Daniel Richard G. || sk...@iskunk.org
My ASCII-art .sig got a bad case of Times New Roman.

Bug#1028253: cryptsetup-nuke-password: [INTL:pt] Portuguese translation - debconf messages

[Paulo Henrique de Lima Santana]

Hi,

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

The debian/changelog is:

cryptsetup-nuke-password (4+nmu1) unstable; urgency=medium

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

  * Update po file into Italian translation. (Closes: #1017486)
  * Update po file into Portuguese translation. (Closes: #1028253)
  * debian/control
+ Bump Standards-Version 4.6.2

I attached a debdiff.

Thanks.

Regards,

--
Paulo Henrique de Lima Santana (phls)
Belo Horizonte - Brasil
Debian Developer
Site: http://phls.com.br
GPG ID: 0443C450
diff -Nru cryptsetup-nuke-password-4/debian/changelog 
cryptsetup-nuke-password-4+nmu1/debian/changelog
--- cryptsetup-nuke-password-4/debian/changelog 2022-07-16 18:00:36.0 
-0300
+++ cryptsetup-nuke-password-4+nmu1/debian/changelog2023-06-19 
23:00:28.0 -0300
@@ -1,3 +1,14 @@
+cryptsetup-nuke-password (4+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Update po file into Brazilian Portuguese translation. (Closes: #1026408)
+  * Update po file into Italian translation. (Closes: #1017486)
+  * Update po file into Portuguese translation. (Closes: #1028253)
+  * debian/control
++ Bump Standards-Version 4.6.2
+
+ -- Paulo Henrique de Lima Santana (phls)   Mon, 19 Jun 2023 
23:00:28 -0300
+
 cryptsetup-nuke-password (4) unstable; urgency=medium
 
   * d/tests/control: Change restriction for askpass autopkgtest from
diff -Nru cryptsetup-nuke-password-4/debian/control 
cryptsetup-nuke-password-4+nmu1/debian/control
--- cryptsetup-nuke-password-4/debian/control   2022-07-16 18:00:36.0 
-0300
+++ cryptsetup-nuke-password-4+nmu1/debian/control  2023-06-19 
23:00:28.0 -0300
@@ -4,7 +4,7 @@
 Maintainer: Debian Security Tools 
 Uploaders: Raphaël Hertzog , Jonas Meurer 

 Build-Depends: debhelper-compat (= 13), shunit2, po-debconf
-Standards-Version: 4.6.1
+Standards-Version: 4.6.2
 Homepage: https://salsa.debian.org/pkg-security-team/cryptsetup-nuke-password
 Vcs-Browser: 
https://salsa.debian.org/pkg-security-team/cryptsetup-nuke-password
 Vcs-Git: 
https://salsa.debian.org/pkg-security-team/cryptsetup-nuke-password.git
diff -Nru cryptsetup-nuke-password-4/debian/copyright 
cryptsetup-nuke-password-4+nmu1/debian/copyright
--- cryptsetup-nuke-password-4/debian/copyright 2022-07-16 18:00:36.0 
-0300
+++ cryptsetup-nuke-password-4+nmu1/debian/copyright2023-06-19 
23:00:28.0 -0300
@@ -9,6 +9,7 @@
 Files: debian/*
 Copyright: 2019 Offensive Security
2022 Jonas Meurer 
+   2023 Paulo Henrique de Lina Santana 
 License: GPL-3.0+
 
 License: GPL-3.0+
diff -Nru cryptsetup-nuke-password-4/debian/po/it.po 
cryptsetup-nuke-password-4+nmu1/debian/po/it.po
--- cryptsetup-nuke-password-4/debian/po/it.po  1969-12-31 21:00:00.0 
-0300
+++ cryptsetup-nuke-password-4+nmu1/debian/po/it.po 2023-06-19 
22:58:03.0 -0300
@@ -0,0 +1,134 @@
+# cryptsetup-nuke-password italian translation
+# Copyright (C) 2022 cryptsetup-nuke-password's copyright holder
+# This file is distributed under the same license as the 
cryptsetup-nuke-password package.
+# Ceppo , 2022.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: cryptsetup-nuke-password\n"
+"Report-Msgid-Bugs-To: cryptsetup-nuke-passw...@packages.debian.org\n"
+"POT-Creation-Date: 2019-07-05 15:24+0200\n"
+"PO-Revision-Date: 2022-08-02 23:00+\n"
+"Last-Translator: Ceppo \n"
+"Language-Team: Italian \n"
+"Language: it\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Type: password
+#. Description
+#: ../cryptsetup-nuke-password.templates:1001
+msgid "Nuke password:"
+msgstr "Password di distruzione:"
+
+#. Type: password
+#. Description
+#: ../cryptsetup-nuke-password.templates:1001
+msgid ""
+"If you setup a “nuke password”, you will be able to type this password at "
+"the early-boot prompt asking your passphrase to unlock your luks-encrypted "
+"partitions. Instead of decrypting the partitions, typing this password will "
+"instead wipe the encryption keys from the luks container so that it is no "
+"longer possible to unlock the encrypted partitions."
+msgstr ""
+"In caso di impostazione di una “password di distruzione”, sarà possibile "
+"inserire questa password nel prompt di avvio che chiede la passphrase per "
+"sbloccare le partizioni criptate con luks. Invece di decriptare le "
+"partizioni, l'inserimento di questa password eliminerà le chiavi di "
+"criptazione dal contenitore luks in modo che non sia più possibile sbloccare "
+"le partizioni criptate."
+
+#. Type: password
+#. Description
+#: ../cryptsetup-nuke-password.templates:1001
+msgid ""
+"This provides a relatively stealth way to make your data unreadable in case "
+"you fear that your computer is going to be seized."
+msgstr ""
+"Questo fornisce un mezzo relativamente discreto per rendere illeggibili i "
+"dati qualora 

Bug#1026408: cryptsetup-nuke-password: [INTL:pt_BR] Brazilian Portuguese debconf templates translation

[Paulo Henrique de Lima Santana]

Hi,

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

The debian/changelog is:

cryptsetup-nuke-password (4+nmu1) unstable; urgency=medium

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

  * Update po file into Italian translation. (Closes: #1017486)
  * Update po file into Portuguese translation. (Closes: #1028253)
  * debian/control
+ Bump Standards-Version 4.6.2

I attached a debdiff.

Thanks.

Regards,

--
Paulo Henrique de Lima Santana (phls)
Belo Horizonte - Brasil
Debian Developer
Site: http://phls.com.br
GPG ID: 0443C450
diff -Nru cryptsetup-nuke-password-4/debian/changelog 
cryptsetup-nuke-password-4+nmu1/debian/changelog
--- cryptsetup-nuke-password-4/debian/changelog 2022-07-16 18:00:36.0 
-0300
+++ cryptsetup-nuke-password-4+nmu1/debian/changelog2023-06-19 
23:00:28.0 -0300
@@ -1,3 +1,14 @@
+cryptsetup-nuke-password (4+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Update po file into Brazilian Portuguese translation. (Closes: #1026408)
+  * Update po file into Italian translation. (Closes: #1017486)
+  * Update po file into Portuguese translation. (Closes: #1028253)
+  * debian/control
++ Bump Standards-Version 4.6.2
+
+ -- Paulo Henrique de Lima Santana (phls)   Mon, 19 Jun 2023 
23:00:28 -0300
+
 cryptsetup-nuke-password (4) unstable; urgency=medium
 
   * d/tests/control: Change restriction for askpass autopkgtest from
diff -Nru cryptsetup-nuke-password-4/debian/control 
cryptsetup-nuke-password-4+nmu1/debian/control
--- cryptsetup-nuke-password-4/debian/control   2022-07-16 18:00:36.0 
-0300
+++ cryptsetup-nuke-password-4+nmu1/debian/control  2023-06-19 
23:00:28.0 -0300
@@ -4,7 +4,7 @@
 Maintainer: Debian Security Tools 
 Uploaders: Raphaël Hertzog , Jonas Meurer 

 Build-Depends: debhelper-compat (= 13), shunit2, po-debconf
-Standards-Version: 4.6.1
+Standards-Version: 4.6.2
 Homepage: https://salsa.debian.org/pkg-security-team/cryptsetup-nuke-password
 Vcs-Browser: 
https://salsa.debian.org/pkg-security-team/cryptsetup-nuke-password
 Vcs-Git: 
https://salsa.debian.org/pkg-security-team/cryptsetup-nuke-password.git
diff -Nru cryptsetup-nuke-password-4/debian/copyright 
cryptsetup-nuke-password-4+nmu1/debian/copyright
--- cryptsetup-nuke-password-4/debian/copyright 2022-07-16 18:00:36.0 
-0300
+++ cryptsetup-nuke-password-4+nmu1/debian/copyright2023-06-19 
23:00:28.0 -0300
@@ -9,6 +9,7 @@
 Files: debian/*
 Copyright: 2019 Offensive Security
2022 Jonas Meurer 
+   2023 Paulo Henrique de Lina Santana 
 License: GPL-3.0+
 
 License: GPL-3.0+
diff -Nru cryptsetup-nuke-password-4/debian/po/it.po 
cryptsetup-nuke-password-4+nmu1/debian/po/it.po
--- cryptsetup-nuke-password-4/debian/po/it.po  1969-12-31 21:00:00.0 
-0300
+++ cryptsetup-nuke-password-4+nmu1/debian/po/it.po 2023-06-19 
22:58:03.0 -0300
@@ -0,0 +1,134 @@
+# cryptsetup-nuke-password italian translation
+# Copyright (C) 2022 cryptsetup-nuke-password's copyright holder
+# This file is distributed under the same license as the 
cryptsetup-nuke-password package.
+# Ceppo , 2022.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: cryptsetup-nuke-password\n"
+"Report-Msgid-Bugs-To: cryptsetup-nuke-passw...@packages.debian.org\n"
+"POT-Creation-Date: 2019-07-05 15:24+0200\n"
+"PO-Revision-Date: 2022-08-02 23:00+\n"
+"Last-Translator: Ceppo \n"
+"Language-Team: Italian \n"
+"Language: it\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Type: password
+#. Description
+#: ../cryptsetup-nuke-password.templates:1001
+msgid "Nuke password:"
+msgstr "Password di distruzione:"
+
+#. Type: password
+#. Description
+#: ../cryptsetup-nuke-password.templates:1001
+msgid ""
+"If you setup a “nuke password”, you will be able to type this password at "
+"the early-boot prompt asking your passphrase to unlock your luks-encrypted "
+"partitions. Instead of decrypting the partitions, typing this password will "
+"instead wipe the encryption keys from the luks container so that it is no "
+"longer possible to unlock the encrypted partitions."
+msgstr ""
+"In caso di impostazione di una “password di distruzione”, sarà possibile "
+"inserire questa password nel prompt di avvio che chiede la passphrase per "
+"sbloccare le partizioni criptate con luks. Invece di decriptare le "
+"partizioni, l'inserimento di questa password eliminerà le chiavi di "
+"criptazione dal contenitore luks in modo che non sia più possibile sbloccare "
+"le partizioni criptate."
+
+#. Type: password
+#. Description
+#: ../cryptsetup-nuke-password.templates:1001
+msgid ""
+"This provides a relatively stealth way to make your data unreadable in case "
+"you fear that your computer is going to be seized."
+msgstr ""
+"Questo fornisce un mezzo relativamente discreto per rendere illeggibili i "
+"dati qualora 

Bug#1017486: cryptsetup-nuke-password: [INTL:it] Italian debconf translation

[Paulo Henrique de Lima Santana]

Hi,

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

The debian/changelog is:

cryptsetup-nuke-password (4+nmu1) unstable; urgency=medium

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

  * Update po file into Italian translation. (Closes: #1017486)
  * Update po file into Portuguese translation. (Closes: #1028253)
  * debian/control
+ Bump Standards-Version 4.6.2

I attached a debdiff.

Thanks.

Regards,

--
Paulo Henrique de Lima Santana (phls)
Belo Horizonte - Brasil
Debian Developer
Site: http://phls.com.br
GPG ID: 0443C450
diff -Nru cryptsetup-nuke-password-4/debian/changelog 
cryptsetup-nuke-password-4+nmu1/debian/changelog
--- cryptsetup-nuke-password-4/debian/changelog 2022-07-16 18:00:36.0 
-0300
+++ cryptsetup-nuke-password-4+nmu1/debian/changelog2023-06-19 
23:00:28.0 -0300
@@ -1,3 +1,14 @@
+cryptsetup-nuke-password (4+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Update po file into Brazilian Portuguese translation. (Closes: #1026408)
+  * Update po file into Italian translation. (Closes: #1017486)
+  * Update po file into Portuguese translation. (Closes: #1028253)
+  * debian/control
++ Bump Standards-Version 4.6.2
+
+ -- Paulo Henrique de Lima Santana (phls)   Mon, 19 Jun 2023 
23:00:28 -0300
+
 cryptsetup-nuke-password (4) unstable; urgency=medium
 
   * d/tests/control: Change restriction for askpass autopkgtest from
diff -Nru cryptsetup-nuke-password-4/debian/control 
cryptsetup-nuke-password-4+nmu1/debian/control
--- cryptsetup-nuke-password-4/debian/control   2022-07-16 18:00:36.0 
-0300
+++ cryptsetup-nuke-password-4+nmu1/debian/control  2023-06-19 
23:00:28.0 -0300
@@ -4,7 +4,7 @@
 Maintainer: Debian Security Tools 
 Uploaders: Raphaël Hertzog , Jonas Meurer 

 Build-Depends: debhelper-compat (= 13), shunit2, po-debconf
-Standards-Version: 4.6.1
+Standards-Version: 4.6.2
 Homepage: https://salsa.debian.org/pkg-security-team/cryptsetup-nuke-password
 Vcs-Browser: 
https://salsa.debian.org/pkg-security-team/cryptsetup-nuke-password
 Vcs-Git: 
https://salsa.debian.org/pkg-security-team/cryptsetup-nuke-password.git
diff -Nru cryptsetup-nuke-password-4/debian/copyright 
cryptsetup-nuke-password-4+nmu1/debian/copyright
--- cryptsetup-nuke-password-4/debian/copyright 2022-07-16 18:00:36.0 
-0300
+++ cryptsetup-nuke-password-4+nmu1/debian/copyright2023-06-19 
23:00:28.0 -0300
@@ -9,6 +9,7 @@
 Files: debian/*
 Copyright: 2019 Offensive Security
2022 Jonas Meurer 
+   2023 Paulo Henrique de Lina Santana 
 License: GPL-3.0+
 
 License: GPL-3.0+
diff -Nru cryptsetup-nuke-password-4/debian/po/it.po 
cryptsetup-nuke-password-4+nmu1/debian/po/it.po
--- cryptsetup-nuke-password-4/debian/po/it.po  1969-12-31 21:00:00.0 
-0300
+++ cryptsetup-nuke-password-4+nmu1/debian/po/it.po 2023-06-19 
22:58:03.0 -0300
@@ -0,0 +1,134 @@
+# cryptsetup-nuke-password italian translation
+# Copyright (C) 2022 cryptsetup-nuke-password's copyright holder
+# This file is distributed under the same license as the 
cryptsetup-nuke-password package.
+# Ceppo , 2022.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: cryptsetup-nuke-password\n"
+"Report-Msgid-Bugs-To: cryptsetup-nuke-passw...@packages.debian.org\n"
+"POT-Creation-Date: 2019-07-05 15:24+0200\n"
+"PO-Revision-Date: 2022-08-02 23:00+\n"
+"Last-Translator: Ceppo \n"
+"Language-Team: Italian \n"
+"Language: it\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Type: password
+#. Description
+#: ../cryptsetup-nuke-password.templates:1001
+msgid "Nuke password:"
+msgstr "Password di distruzione:"
+
+#. Type: password
+#. Description
+#: ../cryptsetup-nuke-password.templates:1001
+msgid ""
+"If you setup a “nuke password”, you will be able to type this password at "
+"the early-boot prompt asking your passphrase to unlock your luks-encrypted "
+"partitions. Instead of decrypting the partitions, typing this password will "
+"instead wipe the encryption keys from the luks container so that it is no "
+"longer possible to unlock the encrypted partitions."
+msgstr ""
+"In caso di impostazione di una “password di distruzione”, sarà possibile "
+"inserire questa password nel prompt di avvio che chiede la passphrase per "
+"sbloccare le partizioni criptate con luks. Invece di decriptare le "
+"partizioni, l'inserimento di questa password eliminerà le chiavi di "
+"criptazione dal contenitore luks in modo che non sia più possibile sbloccare "
+"le partizioni criptate."
+
+#. Type: password
+#. Description
+#: ../cryptsetup-nuke-password.templates:1001
+msgid ""
+"This provides a relatively stealth way to make your data unreadable in case "
+"you fear that your computer is going to be seized."
+msgstr ""
+"Questo fornisce un mezzo relativamente discreto per rendere illeggibili i "
+"dati qualora 

Bug#1038678: linux-image-6.1.0-9-amd64: Low pitch sound

[Eugenia Loli]

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

Dear Maintainer,

I'm having trouble with my audio. Everything is low pitch, every single app and 
browser.
I tried messing with Pulseaudio and sample rates and other suggestions found 
online, but they didn't work.
When I run vainfo, the app first tries to load the iHD driver instead of the 
i965, which is appropriate for this system (it does load i965, but not before 
trying first iHD).
So anyway, after lots of tries with pulseaudio and setting an environmental 
flag to force i965, nothing works still. The audio is too low pitch.
This problem has been on other debian-based distros too that I've tried on the 
same hardware, but not on any of the ubuntu flavors.

The kernel has loaded the i915 display driver btw (which works without issues, 
and for sound, the snd_hda_intel.


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

** Command line:
BOOT_IMAGE=/boot/vmlinuz-6.1.0-9-amd64 
root=UUID=68b555d4-8371-46d0-a442-23b520605c18 ro quiet

** Tainted: W (512)
 * kernel issued warning

** Kernel log:
[ 3555.814362]  
[ 3555.814368]  intel_disable_transcoder+0x9f/0x2c0 [i915]
[ 3555.814527]  ? _raw_spin_lock_irqsave+0x23/0x50
[ 3555.814535]  ? _raw_spin_unlock_irqrestore+0x23/0x40
[ 3555.814540]  ? drm_vblank_get+0x71/0xe0 [drm]
[ 3555.814615]  i9xx_crtc_disable+0x6a/0x260 [i915]
[ 3555.814774]  intel_old_crtc_state_disables+0x3b/0xa0 [i915]
[ 3555.814932]  intel_atomic_commit_tail+0x392/0xe30 [i915]
[ 3555.815126]  intel_atomic_commit+0x34f/0x390 [i915]
[ 3555.815288]  drm_atomic_commit+0x96/0xc0 [drm]
[ 3555.815361]  ? drm_plane_get_damage_clips.cold+0x1c/0x1c [drm]
[ 3555.815425]  drm_atomic_helper_commit_duplicated_state+0xc9/0xe0 
[drm_kms_helper]
[ 3555.815462]  __intel_display_resume+0x80/0xe0 [i915]
[ 3555.815621]  intel_display_resume+0xfc/0x140 [i915]
[ 3555.815801]  i915_drm_resume+0xe5/0x150 [i915]
[ 3555.815943]  ? pci_legacy_resume+0x80/0x80
[ 3555.815951]  dpm_run_callback+0x4a/0x150
[ 3555.815957]  device_resume+0x88/0x190
[ 3555.815962]  async_resume+0x19/0x30
[ 3555.815967]  async_run_entry_fn+0x30/0x130
[ 3555.815973]  process_one_work+0x1c7/0x380
[ 3555.815980]  worker_thread+0x4d/0x380
[ 3555.815986]  ? rescuer_thread+0x3a0/0x3a0
[ 3555.815991]  kthread+0xe9/0x110
[ 3555.815996]  ? kthread_complete_and_exit+0x20/0x20
[ 3555.816001]  ret_from_fork+0x22/0x30
[ 3555.816010]  
[ 3555.816012] ---[ end trace  ]---
[ 3555.816511] ACPI: \: failed to evaluate _DSM 
bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
[ 3555.816522] ACPI: \: failed to evaluate _DSM 
bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
[ 3555.816526] ACPI: \: failed to evaluate _DSM 
bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
[ 3555.816531] ACPI: \: failed to evaluate _DSM 
bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
[ 3555.816535] ACPI: \: failed to evaluate _DSM 
bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
[ 3555.816539] ACPI: \: failed to evaluate _DSM 
bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
[ 3555.816543] ACPI: \: failed to evaluate _DSM 
bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
[ 3555.883363] [ cut here ]
[ 3555.883366] primary A assertion failure (expected off, current on)
[ 3555.883383] usb 1-3: reset high-speed USB device number 3 using xhci_hcd
[ 3555.883439] WARNING: CPU: 0 PID: 3459 at 
drivers/gpu/drm/i915/display/intel_display.c:476 assert_plane+0x9a/0xb0 [i915]
[ 3555.883617] Modules linked in: ccm snd_seq_dummy snd_hrtimer snd_seq rfcomm 
snd_seq_device qrtr cmac algif_hash ecb algif_skcipher af_alg bnep btusb btrtl 
btbcm btintel btmtk bluetooth iwlmvm intel_rapl_msr jitterentropy_rng 
intel_rapl_common intel_soc_dts_thermal intel_soc_dts_iosf intel_powerclamp 
coretemp binfmt_misc kvm_intel kvm mac80211 irqbypass nls_ascii 
snd_soc_sst_cht_bsw_max98090_ti snd_soc_ts3a227e nls_cp437 ctr joydev 
snd_intel_sst_acpi snd_intel_sst_core vfat snd_soc_sst_atom_hifi2_platform 
snd_soc_max98090 ghash_clmulni_intel snd_soc_acpi_intel_match 
snd_hda_codec_hdmi snd_soc_acpi fat cryptd sha512_ssse3 drbg uvcvideo 
videobuf2_vmalloc videobuf2_memops snd_hda_intel sha512_generic libarc4 
snd_soc_core ansi_cprng iwlwifi intel_cstate videobuf2_v4l2 snd_hda_codec 
cdc_acm videobuf2_common pcspkr videodev mc snd_hda_core cfg80211 iTCO_wdt 
snd_intel_dspcfg snd_hwdep snd_compress snd_intel_sdw_acpi intel_pmc_bxt 
iTCO_vendor_support ecdh_generic snd_pcm ecc watchdog rfkill
[ 3555.883724]  snd_timer ac snd pwm_lpss_platform soundcore elan_i2c pwm_lpss 
evdev serio_raw parport_pc ppdev lp parport fuse loop efi_pstore dm_mod 
configfs efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 
crc32c_generic hid_generic usbhid hid mmc_block i915 drm_buddy i2c_algo_bit 
drm_display_helper cec rc_core ttm 

Bug#1036232: org.gnome.Shell.desktop[…]: Window manager warning: Failed to parse saved session file:

[AlMa]

severity 1036232 important
thanks

Same or similar bug on the current Debian stable 12 “bookworm” (so 
raising severity a tiny bit):


Jun 20 03:23:14 AnonymizedComputerName org.gnome.Shell.desktop[1077]: 
kmsro: driver missing
Jun 20 03:23:14 AnonymizedComputerName dbus-daemon[1037]: [session 
uid=119 pid=1037] Activating via systemd: service 
name='org.freedesktop.Tracker3.Miner.Files' 
unit='tracker-miner-fs-3.service' requested by ':1.3' (uid=119 pid=1032 
comm="/usr/libexec/tracker-extract-3")
Jun 20 03:23:14 AnonymizedComputerName gnome-shell[1077]: Device 
'/dev/dri/card0' prefers shadow buffer
Jun 20 03:23:14 AnonymizedComputerName gnome-shell[1077]: Added device 
'/dev/dri/card0' (ast) using atomic mode setting.
Jun 20 03:23:14 AnonymizedComputerName gnome-shell[1077]: Device 
'/dev/dri/card1' prefers shadow buffer
Jun 20 03:23:14 AnonymizedComputerName systemd[1013]: Starting 
tracker-miner-fs-3.service - Tracker file system data miner...
Jun 20 03:23:14 AnonymizedComputerName tracker-miner-f[1139]: Unable to 
get XDG user directory path for special directory  Ignoring 
this location.
Jun 20 03:23:14 AnonymizedComputerName tracker-miner-f[1139]: Unable to 
get XDG user directory path for special directory  Ignoring this 
location.
Jun 20 03:23:14 AnonymizedComputerName tracker-miner-f[1139]: Unable to 
get XDG user directory path for special directory  Ignoring 
this location.
Jun 20 03:23:14 AnonymizedComputerName tracker-miner-f[1139]: Unable to 
get XDG user directory path for special directory  Ignoring this 
location.
Jun 20 03:23:14 AnonymizedComputerName tracker-miner-f[1139]: Unable to 
get XDG user directory path for special directory  Ignoring 
this location.
Jun 20 03:23:14 AnonymizedComputerName tracker-miner-f[1139]: Unable to 
get XDG user directory path for special directory  Ignoring 
this location.
Jun 20 03:23:14 AnonymizedComputerName tracker-miner-f[1139]: Unable to 
get XDG user directory path for special directory  Ignoring this 
location.
Jun 20 03:23:14 AnonymizedComputerName tracker-miner-f[1139]: Unable to 
get XDG user directory path for special directory  Ignoring 
this location.
Jun 20 03:23:14 AnonymizedComputerName tracker-miner-f[1139]: Unable to 
get XDG user directory path for special directory  Ignoring this 
location.
Jun 20 03:23:14 AnonymizedComputerName avahi-daemon[869]: Server startup 
complete. Host name is AnonymizedComputerName.local. Local service 
cookie is 156463880.
Jun 20 03:23:14 AnonymizedComputerName gnome-shell[1077]: Added device 
'/dev/dri/card1' (nouveau) using non-atomic mode setting.
Jun 20 03:23:14 AnonymizedComputerName gnome-shell[1077]: Failed to 
initialize accelerated iGPU/dGPU framebuffer sharing: Not hardware 
accelerated
Jun 20 03:23:14 AnonymizedComputerName gnome-shell[1077]: Created gbm 
renderer for '/dev/dri/card0'
Jun 20 03:23:14 AnonymizedComputerName gnome-shell[1077]: Created gbm 
renderer for '/dev/dri/card1'
Jun 20 03:23:14 AnonymizedComputerName gnome-shell[1077]: Boot VGA GPU 
/dev/dri/card1 selected as primary
Jun 20 03:23:14 AnonymizedComputerName dbus-daemon[1037]: [session 
uid=119 pid=1037] Activating via systemd: service 
name='org.gtk.vfs.UDisks2VolumeMonitor' 
unit='gvfs-udisks2-volume-monitor.service' requested by ':1.11' (uid=119 
pid=1139 comm="/usr/libexec/tracker-miner-fs-3")
Jun 20 03:23:14 AnonymizedComputerName systemd[1013]: Starting 
gvfs-udisks2-volume-monitor.service - Virtual filesystem service - disk 
device monitor...
Jun 20 03:23:14 AnonymizedComputerName systemd[1]: Started gpm.service - 
Console Mouse manager.
Jun 20 03:23:14 AnonymizedComputerName dbus-daemon[1037]: [session 
uid=119 pid=1037] Successfully activated service 
'org.gtk.vfs.UDisks2VolumeMonitor'
Jun 20 03:23:14 AnonymizedComputerName systemd[1013]: Started 
gvfs-udisks2-volume-monitor.service - Virtual filesystem service - disk 
device monitor.
Jun 20 03:23:14 AnonymizedComputerName dbus-daemon[1037]: [session 
uid=119 pid=1037] Activating via systemd: service 
name='org.gtk.vfs.AfcVolumeMonitor' 
unit='gvfs-afc-volume-monitor.service' requested by ':1.11' (uid=119 
pid=1139 comm="/usr/libexec/tracker-miner-fs-3")
Jun 20 03:23:14 AnonymizedComputerName systemd[1013]: Starting 
gvfs-afc-volume-monitor.service - Virtual filesystem service - Apple 
File Conduit monitor...
Jun 20 03:23:14 AnonymizedComputerName dbus-daemon[1037]: [session 
uid=119 pid=1037] Successfully activated service 
'org.gtk.vfs.AfcVolumeMonitor'
Jun 20 03:23:14 AnonymizedComputerName systemd[1013]: Started 
gvfs-afc-volume-monitor.service - Virtual filesystem service - Apple 
File Conduit monitor.
Jun 20 03:23:14 AnonymizedComputerName dbus-daemon[1037]: [session 
uid=119 pid=1037] Activating via systemd: service 
name='org.gtk.vfs.MTPVolumeMonitor' 
unit='gvfs-mtp-volume-monitor.service' requested by ':1.11' (uid=119 
pid=1139 comm="/usr/libexec/tracker-miner-fs-3")
Jun 20 03:23:14 AnonymizedComputerName systemd[1013]: Starting 

Bug#1033186: bash-completion: Please add .pages as possible extension for libreoffice (writer)

[Gabriel F. T. Gomes]

Control: reassign -1 libreoffice

Hi, I believe the libreoffice package produces its own completion files
(which is awesome), thus reassigning.

A patch for this would probably look like:

--- bin/generate-bash-completion.py 2023-06-19 18:32:31.988021669 -0700
+++ bin/generate-bash-completion.py.PATCH   2023-06-19 18:32:21.816021649 
-0700
@@ -39,7 +39,7 @@
 
 WRITERDOCS = ["doc", "dot", "rtf", "sxw", "stw", "sdw", "vor", "txt", "htm?",
   "xml", "wp", "wpd", "wps", "odt", "ott", "fodt", "docm", "docx",
-  "dotm", "dotx"]
+  "dotm", "dotx", "pages"]
 
 TEMPLATES = ["stw", "dot", "vor", "stc", "xlt", "sti", "pot", "std", "stw",
  "dotm", "dotx", "potm", "potx", "xltm", "xltx"]

Best regards,
Gabriel


On Sun, 19 Mar 2023 08:50:13 +0100
Helge Kreutzmann  wrote:

> Package: bash-completion
> Version: 1:2.11-6
> Severity: wishlist
> 
> I got a .pages file a few days ago. I did not know how to handle it and
> by chance realized libreoffice can open it just fine. Unfortunately
> this is not clear in the shell, as bash refuses to complete the file
> name by default.
> 
> Probably the following change should do the trick:
> -_install_xspec 
> '!*.@(sxw|stw|sxg|sgl|doc?([mx])|dot?([mx])|rtf|txt|htm|html|?(f)odt|ott|odm|pdf)'
>  oowriter lowriter
> +_install_xspec 
> '!*.@(sxw|stw|sxg|sgl|doc?([mx])|dot?([mx])|rtf|txt|htm|html|?(f)odt|ott|odm|pdf|pages)'
>  oowriter lowriter
> 
> 
> 
> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers testing-security
>   APT policy: (500, 'testing-security'), (500, 'testing')
> Architecture: amd64 (x86_64)
> 
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: 
> LC_ALL set to de_DE.UTF-8), LANGUAGE not set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> 
> -- no debconf information
> 

Bug#1038677: gnome-applets-data: conffile not removed: /etc/dbus-1/system.d/org.gnome.CPUFreqSelector.conf

[Paul Wise]

Package: gnome-applets-data
Version: 3.46.0-2
Severity: normal
User: debian...@lists.debian.org
Usertags: obsolete-conffile adequate

The recent upgrade did not deal with obsolete conffiles properly.
Please use the dpkg-maintscript-helper support provided by
dh_installdeb to remove these obsolete conffiles on upgrade.

https://www.debian.org/doc/debian-policy/ch-files.html#s-config-files
https://manpages.debian.org/man/1/dh_installdeb

This bug report brought to you by adequate:

https://bonedaddy.net/pabs3/log/2013/02/23/inadequate-software/

$ p=gnome-applets-data ; adequate $p ; dpkg-query -W -f='${Conffiles}\n' $p | 
grep obsolete
gnome-applets-data: obsolete-conffile 
/etc/dbus-1/system.d/org.gnome.CPUFreqSelector.conf
 /etc/dbus-1/system.d/org.gnome.CPUFreqSelector.conf 
2df9b521753a323412317b1ef7acc2f6 obsolete

-- System Information:
Debian Release: trixie/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
merged-usr: no
Architecture: amd64 (x86_64)

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

Versions of packages gnome-applets-data depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4

gnome-applets-data recommends no packages.

gnome-applets-data suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1038673: nmu: console-setup_1.221

[Gunnar Hjalmarsson]

On 2023-06-20 01:18, Gunnar Hjalmarsson wrote:

nmu control-setup_1.221 . all . -m 'Rebuild against xkb-data 2.38-2'


Sorry about the typo. Should better be:

nmu console-setup_1.221 . all . -m 'Rebuild against xkb-data 2.38-2'

(don't do these things when you ought to sleep)

/ Gunnar

Bug#1038388: shotcut: Shotcut 23 timeline widget is blank

[Doug Larrick]

On Mon, 19 Jun 2023 15:46:40 +0200
Gürkan Myczko  wrote:
> I've uploaded -2 which should prevent more users running into the
> same issue.
> I hope to get to test/check the packaging rest of the week...
> 

Hmm, it seems you've named some packages that don't exist. See attached.

The following packages have unmet dependencies:
 shotcut : Depends: qml6-module-qtquick-controls2 but it is not installable
   Depends: qml6-module-qtquick2 but it is not installable
   Depends: qml6-module-qtgraphicaleffects but it is not installable
   Depends: qml6-module-qtquick-window2 but it is not installable
   Depends: qml6-module-qtquick-extras but it is not installable
   Depends: qml6-module-qtqml-models2 but it is not installable

-Doug
doug@watney:~$ sudo apt install -tunstable shotcut=23.06.14+git20230616+ds-2 shotcut-data=23.06.14+git20230616+ds-2 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 shotcut : Depends: qml6-module-qtquick-controls2 but it is not installable
   Depends: qml6-module-qtquick2 but it is not installable
   Depends: qml6-module-qtgraphicaleffects but it is not installable
   Depends: qml6-module-qtquick-window2 but it is not installable
   Depends: qml6-module-qtquick-extras but it is not installable
   Depends: qml6-module-qtqml-models2 but it is not installable
E: Unable to correct problems, you have held broken packages.
doug@watney:~$ sudo apt install -tunstable shotcut=23.06.14+git20230616+ds-2 shotcut-data=23.06.14+git20230616+ds-2 qml6-module-qtquick-controls2
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package qml6-module-qtquick-controls2 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'qml6-module-qtquick-controls2' has no installation candidate
doug@watney:~$ apt policy qml6-module-qtquick-controls2
qml6-module-qtquick-controls2:
  Installed: (none)
  Candidate: (none)
  Version table:

Bug#1038676: rocsparse: binary-all FTBFS

[Adrian Bunk]

Source: rocsparse
Version: 5.3.0+dfsg-6
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=rocsparse=all=5.3.0%2Bdfsg-6=1686900579=0

...
   debian/rules execute_before_dh_install
make[1]: Entering directory '/<>'
# Note the rpath field setting may cause reproducible build issues.
# This should be removed earlier in the toolchain if possible.
patchelf --remove-rpath 
./debian/tmp/usr/lib/x86_64-linux-gnu/librocsparse.so.0.1
patchelf: getting info about 
'./debian/tmp/usr/lib/x86_64-linux-gnu/librocsparse.so.0.1': No such file or 
directory
make[1]: *** [debian/rules:37: execute_before_dh_install] Error 1

Bug#1038675: coqeal FTBFS: Error: Cannot find a physical path bound to logical path mpoly with prefix SsrMultinomials.

[Adrian Bunk]

Source: coqeal
Version: 1.1.1-3
Severity: serious
Tags: ftbfs trixie sid

https://buildd.debian.org/status/logs.php?pkg=coqeal=1.1.1-3%2Bb2

...
COQC refinements/bareiss_eff.v
File "./refinements/seqmx_complements.v", line 46, characters 0-58:
Warning: The default value for Typeclasses Opaque and Typeclasses Transparent
locality is currently "local" in a section and "global" otherwise, but is
scheduled to change in a future release. For the time being, adding typeclass
transparency hints outside of sections without specifying an explicit
locality attribute is therefore deprecated. It is recommended to use "export"
whenever possible. Use the attributes #[local], #[global] and #[export]
depending on your choice. For example: "#[export] Typeclasses Transparent
foo.". This is supported since Coq 8.15.
[deprecated-typeclasses-transparency-without-locality,deprecated]
COQC refinements/multipoly.v
File "./refinements/multipoly.v", line 13, characters 0-48:
Error: Cannot find a physical path bound to logical path
mpoly with prefix SsrMultinomials.

make[3]: *** [Makefile.coq:844: refinements/multipoly.vo] Error 1

Bug#1038612: The hanging is of invoking another script

[Budi]

The hanging is of invoking another script, so need to trace it by
inserting set-x in  /usr/lib/os-probes/50mounted-tests

the trace:

+ partition=/dev/sda1
+ . /usr/share/os-prober/common.sh
++ cleanup_tmpdir=false
++ progname=
++ type mapdevfs
++ fs_type /dev/sda1
++ local fstype=
++ type lsblk
+++ lsblk --nodeps --noheading --output FSTYPE -- /dev/sda1
++ fstype=ntfs
++ '[' -z ntfs ']'
++ echo ntfs
++ return
+ types=ntfs
+ '[' ntfs = NOT-DETECTED ']'
+ '[' ntfs = swap ']'
+ '[' ntfs = crypto_LUKS ']'
+ '[' ntfs = LVM2_member ']'
+ '[' ntfs = ntfs ']'
+ type ntfs-3g
+ types='ntfs-3g ntfs'
+ tmpmnt=/var/lib/os-prober/mount
+ '[' '!' -d /var/lib/os-prober/mount ']'
+ mounted=
+ type grub-mount
+ type grub-probe
+ grub-mount /dev/sda1 /var/lib/os-prober/mount
+ mounted=1
++ grub-probe -d /dev/sda1 -t fs
+ type=ntfs
+ '[' ntfs ']'
+ debug 'mounted using GRUB ntfs filesystem driver'
+ '[' -z '' ']'
+ log 'debug: mounted using GRUB ntfs filesystem driver'
+ cache_progname
+ case $progname in
+ progname=50mounted-tests
+ logger -t 50mounted-tests 'debug: mounted using GRUB ntfs filesystem driver'
+ '[' 1 ']'
+ for test in /usr/lib/os-probes/mounted/*
+ debug 'running subtest /usr/lib/os-probes/mounted/05efi'
+ '[' -z '' ']'
+ log 'debug: running subtest /usr/lib/os-probes/mounted/05efi'
+ cache_progname
+ case $progname in
+ logger -t 50mounted-tests 'debug: running subtest
/usr/lib/os-probes/mounted/05efi'
+ '[' -f /usr/lib/os-probes/mounted/05efi ']'
+ '[' -x /usr/lib/os-probes/mounted/05efi ']'
+ /usr/lib/os-probes/mounted/05efi /dev/sda1 /var/lib/os-prober/mount ntfs
+ for test in /usr/lib/os-probes/mounted/*
+ debug 'running subtest /usr/lib/os-probes/mounted/10freedos'
+ '[' -z '' ']'
+ log 'debug: running subtest /usr/lib/os-probes/mounted/10freedos'
+ cache_progname
+ case $progname in
+ logger -t 50mounted-tests 'debug: running subtest
/usr/lib/os-probes/mounted/10freedos'
+ '[' -f /usr/lib/os-probes/mounted/10freedos ']'
+ '[' -x /usr/lib/os-probes/mounted/10freedos ']'
+ /usr/lib/os-probes/mounted/10freedos /dev/sda1 /var/lib/os-prober/mount ntfs
+ for test in /usr/lib/os-probes/mounted/*
+ debug 'running subtest /usr/lib/os-probes/mounted/10qnx'
+ '[' -z '' ']'
+ log 'debug: running subtest /usr/lib/os-probes/mounted/10qnx'
+ cache_progname
+ case $progname in
+ logger -t 50mounted-tests 'debug: running subtest
/usr/lib/os-probes/mounted/10qnx'
+ '[' -f /usr/lib/os-probes/mounted/10qnx ']'
+ '[' -x /usr/lib/os-probes/mounted/10qnx ']'
+ /usr/lib/os-probes/mounted/10qnx /dev/sda1 /var/lib/os-prober/mount ntfs
+ for test in /usr/lib/os-probes/mounted/*
+ debug 'running subtest /usr/lib/os-probes/mounted/20macosx'
+ '[' -z '' ']'
+ log 'debug: running subtest /usr/lib/os-probes/mounted/20macosx'
+ cache_progname
+ case $progname in
+ logger -t 50mounted-tests 'debug: running subtest
/usr/lib/os-probes/mounted/20macosx'
+ '[' -f /usr/lib/os-probes/mounted/20macosx ']'
+ '[' -x /usr/lib/os-probes/mounted/20macosx ']'
+ /usr/lib/os-probes/mounted/20macosx /dev/sda1 /var/lib/os-prober/mount ntfs
+ for test in /usr/lib/os-probes/mounted/*
+ debug 'running subtest /usr/lib/os-probes/mounted/20microsoft'
+ '[' -z '' ']'
+ log 'debug: running subtest /usr/lib/os-probes/mounted/20microsoft'
+ cache_progname
+ case $progname in
+ logger -t 50mounted-tests 'debug: running subtest
/usr/lib/os-probes/mounted/20microsoft'
+ '[' -f /usr/lib/os-probes/mounted/20microsoft ']'
+ '[' -x /usr/lib/os-probes/mounted/20microsoft ']'
+ /usr/lib/os-probes/mounted/20microsoft /dev/sda1 /var/lib/os-prober/mount ntfs
+ for test in /usr/lib/os-probes/mounted/*
+ debug 'running subtest /usr/lib/os-probes/mounted/30utility'
+ '[' -z '' ']'
+ log 'debug: running subtest /usr/lib/os-probes/mounted/30utility'
+ cache_progname
+ case $progname in
+ logger -t 50mounted-tests 'debug: running subtest
/usr/lib/os-probes/mounted/30utility'
+ '[' -f /usr/lib/os-probes/mounted/30utility ']'
+ '[' -x /usr/lib/os-probes/mounted/30utility ']'
+ /usr/lib/os-probes/mounted/30utility /dev/sda1 /var/lib/os-prober/mount ntfs
+ for test in /usr/lib/os-probes/mounted/*
+ debug 'running subtest /usr/lib/os-probes/mounted/40lsb'
+ '[' -z '' ']'
+ log 'debug: running subtest /usr/lib/os-probes/mounted/40lsb'
+ cache_progname
+ case $progname in
+ logger -t 50mounted-tests 'debug: running subtest
/usr/lib/os-probes/mounted/40lsb'
+ '[' -f /usr/lib/os-probes/mounted/40lsb ']'
+ '[' -x /usr/lib/os-probes/mounted/40lsb ']'
+ /usr/lib/os-probes/mounted/40lsb /dev/sda1 /var/lib/os-prober/mount ntfs
+ for test in /usr/lib/os-probes/mounted/*
+ debug 'running subtest /usr/lib/os-probes/mounted/70hurd'
+ '[' -z '' ']'
+ log 'debug: running subtest /usr/lib/os-probes/mounted/70hurd'
+ cache_progname
+ case $progname in
+ logger -t 50mounted-tests 'debug: running subtest
/usr/lib/os-probes/mounted/70hurd'
+ '[' -f /usr/lib/os-probes/mounted/70hurd ']'
+ '[' -x /usr/lib/os-probes/mounted/70hurd ']'
+ /usr/lib/os-probes/mounted/70hurd /dev/sda1 /var/lib/os-prober/mount 

Bug#1034904: ImportError: cannot import name 'util' from 'distutils' (/usr/lib/python3.11/distutils/__init__.py)

[AlMa]

severity 1034904 important
thanks

Same bug for me here:

$ diffuse
Traceback (most recent call last):
  File "/usr/bin/diffuse", line 36, in 
from diffuse import main
  File "/usr/share/diffuse/diffuse/main.py", line 33, in 
from diffuse import utils
  File "/usr/share/diffuse/diffuse/utils.py", line 32, in 
from diffuse.resources import theResources
  File "/usr/share/diffuse/diffuse/resources.py", line 33, in 
from distutils import util
ImportError: cannot import name 'util' from 'distutils' 
(/usr/lib/python3.11/distutils/__init__.py)


Raising severity because several folks seem to be affected.  I have 
version 0.7.7-1 installed.

Bug#1038660: desktop-base: please set a placeholder theme during development, different from any release

[Aurélien COUDERC]

Dear Simon,

Le lundi 19 juin 2023, 20:50:35 CEST Simon McVittie a écrit :
> Package: desktop-base
> Version: 12.0.6
> Severity: normal
> Tags: trixie sid
> 
> Now that Debian 12 has been released, the version of desktop-base in
> testing should no longer include Debian 12 branding, so that the testing
> installer will be visually distinct from the Debian 12 stable release.

I think this makes sense.

> The simplest possible implementation of this would be to remove the "12"
> from all the art components, but I think it would be better to use artwork
> that is obviously different.

Yes, I can do that.

> One simple "programmer-art" way to do that would be to desaturate the
> Debian 12 artwork down to greyscale to make it obviously a placeholder,
> or rotate the hue to make it a different colour.

I probably won’t do that.

> However, it might be nicer (and definitely more fun!) to have a theme
> specifically for Debian in its alpha/beta state, with a sense of "this is
> under construction", to be replaced by a proper Debian 13 theme closer
> to the Debian 13 freeze. Some of the contributors who were helping with
> debian-cd testing during the Debian 12 release process had a similar
> thought a while ago, and got as far as preparing a background image for
> this purpose - I'll ask them to follow up here.

Well I was not convinced at all by the last proposal I saw.

Obviously theming and art are very personal but I wouldn’t want to replace 
quality artwork we’ve been having for the last couple of releases with 
something I consider less attractive just for the sake of it.

OK for the artwort to convey the idea of work-in-progress but the art itself 
cannot be work-in-progress…

And yes I know people can change it if they like but defaults count, especially 
since it will be part first impressions for new users of testing.


Happy hacking,
--
Aurélien

Bug#972609: /lib/runit-helper/runit-helper: 74: sv: not found

[Colin Watson]

Control: reassign -1 runit-helper
Control: close -1 dh-runit/2.10.0

On Wed, Oct 21, 2020 at 08:59:31AM +0200, Marc Haber wrote:
> reconfiguring openssh-server gives the following output:
> 
> [5/5060]mh@fan:~ $ sudo dpkg-reconfigure -plow openssh-server
> rescue-ssh.target is a disabled or a static unit, not starting it.
> /lib/runit-helper/runit-helper: 74: sv: not found
> [6/5061]mh@fan:~ $
> 
> I am not sure wheter this is an issue in runit, or in openssh. A message
> like this is one that a trained administrator's eye will immediately
> lock on to, so it should not be there.

Sorry for missing this at the time.  This was a dh-runit issue, and was
fixed there:

dh-runit (2.10.0) experimental; urgency=medium

  * Add invoke-rc.d actions support into dh-runit (Closes: #969511)
  * Deprecate the noreplace option, coupled with onupgrade=nostop
  * Add onupgrade=reload
  * Bump our version to 2.10.0
  * Don't call sv if is runit is not installed (Closes: #968114)

 -- Lorenzo Puliti   Sun, 06 Sep 2020 00:58:07 +0200

-- 
Colin Watson (he/him)  [cjwat...@debian.org]

Bug#1038674: mirror listing update for ro.mirror.flokinet.net

[FlokiNET]

Package: mirrors
Severity: minor
User: mirr...@packages.debian.org
Usertags: mirror-list

Submission-Type: update
Site: ro.mirror.flokinet.net
Type: leaf
Archive-architecture: amd64
Archive-http: /debian/
Archive-rsync: debian/
Maintainer: FlokiNET 
Country: RO Romania
Location: Bucharest
Comment: We are currently rolling out new mirrors in different countries so we 
assigned our pre-existing mirror a location specific prefix. The old 
mirror.flokinet.net domain will remain valid but will at some point be 
converted to an anycast ip that routes to our closest by mirror




Trace Url: http://ro.mirror.flokinet.net/debian/project/trace/
Trace Url: 
http://ro.mirror.flokinet.net/debian/project/trace/ftp-master.debian.org
Trace Url: 
http://ro.mirror.flokinet.net/debian/project/trace/ro.mirror.flokinet.net

Bug#995670: What's the status of this ITP?

[Nick Hastings]

* Nick Hastings  [230620 08:18]:
> 
> My package is on salsa: https://github.com/NickHastings/zig-debian

While that statement is true, the link is clearly not the intended one.
https://salsa.debian.org/nickh/zig

Nick.

Bug#1030129: Additional information

[Scott Talbert]

On Tue, 20 Jun 2023, Vladimir Petko wrote:


Would it be possible to consider a temporary fix[1] until all relevant
openjdk packages are updated?

[1] https://salsa.debian.org/java-team/ca-certificates-java/-/merge_requests/8


A temporary fix would be appreciated as there at least a few packages 
blocked by this issue.  :)


Thanks,
Scott

Bug#1038603: Seems fixed in unstable

[Jeronimo Pellegrini]

The new uploaded libisl23 (version 0.26-3) seems to have fixed the
problem (I have successfully compiled darktable with GCC 12).

Thanks a lot Matthias for the really wuick fix to the problem!

J.

Bug#995670: What's the status of this ITP?

[Nick Hastings]

Hi,

* Abraham Raji  [230620 06:38]:
> 
> What's the status of this ITP? It seems like Nick is pulling a
> considerable amount of work himself.

I filed an RFS bug
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012286
There was some progress and some interest from a potential sponsor but
it seems that the copyright file has become a road block.

> I would personally love to see Zig in the Debian archives so I am
> ready to volunteer some of my time towards the effort.

My zig package is up to date with the current version of zig 0.10.1 and
this version of zig can bootstrap. However, it seems that the next
planned release of zig will not be able to bootstrap (in the usual
sense). See for example https://ziglang.org/news/goodbye-cpp/

> I feel we can move the work for this package to salsa if no one has any
> issues.

My package is on salsa: https://github.com/NickHastings/zig-debian

Cheers,

Nick.

Bug#1038673: nmu: console-setup_1.221

[Gunnar Hjalmarsson]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: debia...@lists.debian.org, gunna...@debian.org
Control: affects -1 src:xkeyboard-config src:control-setup

Hi!

I uploaded xkeyboard-config 2.38-2 to unstable (as an NMU), but before 
it can migrate, console-setup needs to be rebuilt against the new 
xkb-data version.


nmu control-setup_1.221 . all . -m 'Rebuild against xkb-data 2.38-2'

--
Thanks!

Gunnar Hjalmarsson

Bug#1034395: libkf5kcmutils-dev: need fix incorrect symlink

[Antonio Russo]

control: tag -1 patch

This breaks builds of many things including, e.g., kwin.

I'm attaching couc...@debian.org 's patch, which fixed 5.103.0-3, but
apparently never got into the git repository.

Best,
Antonio Russo
(hello other Antonio!)
--- ../kcmutils/debian/libkf5kcmutils-bin.install	2023-06-19 16:10:51.039117308 -0600
+++ kcmutils-5.103.0/debian/libkf5kcmutils-bin.install	2023-02-28 04:48:46.0 -0700
@@ -1 +1 @@
-usr/lib/*/libexec/kf5/kcmdesktopfilegenerator usr/libexec/kf5/kcmdesktopfilegenerator
+usr/lib/*/libexec/kf5/kcmdesktopfilegenerator usr/libexec/kf5


OpenPGP_0xB01C53D5DED4A4EE.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1037297: /usr/sbin/kea-dhcp6: socket error when starting or restarting the server

[Bruno Meirelles]

Hi Paride, thanks for the reply.

I checked the systemd file and it says After=network-online.target, it 
still doesn't work, I need to restart the service.


Is the problem in systemd?

Who should I report to?

Thanks.

Em 19/06/2023 09:51, Paride Legovini escreveu:

Bruno wrote on 10/06/2023:

Dear Maintainer,

when starting or restarting the server, kea-dhcp6-server does not work with the 
following error:

[...]

Hello Bruno and thanks for this bug report. I think this issue falls
under the "network-online ordering" category, which is due to the fact
that the "networking is ready" or "system is online" status is not well
defined. It may me tempting to use an After=network-online.target rule
in the systemd service file, but the point defining what that target
means. For example: if a secondary network interface of a server is
down, should this prevent systemd from starting kea?

Unfortunately I don't have a solution at hand at the moment which is
guaranteed to do more good than harm.

Paride

Bug#1028528: transition: libcotp

[Sebastian Ramacher]

Control: tags -1 = confirmed

On 2023-06-12 19:40:14 +, Francisco Vilmar Cardoso Ruviaro wrote:
> Hello Sebastian,
> 
> On Fri, 20 Jan 2023 20:26:50 +0100 Sebastian Ramacher  
> wrote:
> > Control: tags -1 trixie
> > 
> > On 2023-01-19 15:38:06 +, Francisco Vilmar Cardoso Ruviaro wrote:
> > > Hi Sebastian,
> > > 
> > > On 1/17/23 22:37, Sebastian Ramacher wrote:
> > > > Control: tags -1 moreinfo
> > > > 
> > > > On 2023-01-12 11:45:45 +, Francisco Vilmar Cardoso Ruviaro wrote:
> > > >> Package: release.debian.org
> > > >> Severity: normal
> > > >> User: release.debian@packages.debian.org
> > > >> Usertags: transition
> > > >> 
> > > >> Dear Release Team,
> > > >> 
> > > >> I would like to update libcotp in unstable to the 2.0.0-1.
> > > >> 
> > > >> I would like to request a transition slot for libcotp, changing the
> > > >> library name from libcotp12 to libcotp2. The version 2.0.0
> > > > 
> > > > Why is the SONAME going backwards?
> > > > 
> > > I believe this was an upstream decision, please check it out:
> > > 
> > > "the soversion is now set only from the $major version (e.g. 2),
> > > and not from $major$minor (e.g. 12) like it used to be."
> > > https://github.com/paolostivanin/libcotp/releases/tag/v2.0.0
> > 
> > Is upstream aware that the can never release with major versions 11 and
> > 12 (at least)? Please clarify this with upstream.
> > 
> Yes, upstream is aware of this.
> 
> 
> > In any case, let's postpone this transition to trixie.
> > 
> I just uploaded version 2.0.1-1~exp1 for experimental.
> I await your authorization to proceed with the transition.

Please go ahead.

Cheers
-- 
Sebastian Ramacher

Bug#1028489: transition: boost1.81

[Sebastian Ramacher]

Hi Anton

On 2023-01-30 19:28:37 +0100, Anton Gladky wrote:
> Hi Sebastian,
> 
> thanks for the information. Let's do it just after release.
> 
> Just for the record. The full test rebuild has been done (thanks to Lucas!).
> Results and logs are here:
> 
> http://qa-logs.debian.net/2023/01/15/

Have bugs been filed for the failing builds?

Cheers
-- 
Sebastian Ramacher

Bug#1027959: transition: libkiwix

[Sebastian Ramacher]

Control: tags -1 moreinfo

On 2023-01-15 15:35:30 +0100, Sebastian Ramacher wrote:
> Control: tags -1 trixie
> 
> Hi
> 
> On 2023-01-12 00:51:05 -0500, Kunal Mehta wrote:
> > On 1/5/23 04:48, Sebastian Ramacher wrote:
> > 
> > > > I'd like to do the transition for libkiwix (and sibling libzim) in time
> > > > for bookworm, it's fully self-contained.
> > > > 
> > > > I uploaded src:zimlib 8.1.0 to unstable last week, which unintentionally
> > > > had a breaking change in it (sorry!). libkiwix 12.0.0 is waiting in 
> > > > experimental.
> > > 
> > > If it had an ABI breaking change, you also have to do a transition for
> > > it. Please revert in unstable in the meantime and prepare the transition
> > > in experimental.
> > 
> > Ack and done. libzim 8.1.0 is in experimental now, and unstable is back to
> > 8.0.0.
> 
> libzim in experimental is still using libzim8. That would need to change
> if it broke the ABI.
> 
> Let's do this one properly during the trixie release cycle.

What's the status here?

Cheers
-- 
Sebastian Ramacher

Bug#1038672: mathcomp-abel FTBFS: Error: The reference fact_smonotone was not found in the current environment.

[Adrian Bunk]

Source: mathcomp-abel
Version: 1.2.1-1
Severity: serious
Tags: ftbfs trixie sid

https://buildd.debian.org/status/logs.php?pkg=mathcomp-abel=1.2.1-1%2Bb6

...
   dh_auto_build -a
make -j4 "INSTALL=install --strip-program=true"
make[1]: Entering directory '/<>'
coq_makefile -f _CoqProject -o Makefile.coq
make --no-print-directory -f Makefile.coq 
COQDEP VFILES
COQC theories/xmathcomp/various.v
COQC theories/xmathcomp/char0.v
File "./theories/xmathcomp/char0.v", line 104, characters 14-21:
Warning: Notation rmorphX is deprecated since mathcomp 1.17.0.
Use rmorphXn instead. [deprecated-syntactic-definition,deprecated]
File "./theories/xmathcomp/char0.v", line 104, characters 14-21:
Warning: Notation rmorphX is deprecated since mathcomp 1.17.0.
Use rmorphXn instead. [deprecated-syntactic-definition,deprecated]
File "./theories/xmathcomp/various.v", line 1168, characters 34-48:
Error: The reference fact_smonotone was not found in the current environment.

make[3]: *** [Makefile.coq:844: theories/xmathcomp/various.vo] Error 1

Bug#1038671: RM: pupnp-1.8 -- RoQA; replaced by pupnp

[Sebastian Ramacher]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
Control: block -1 by 1037511 1037538
Control: tags -1 moreinfo
X-Debbugs-Cc: pupnp-...@packages.debian.org, sramac...@debian.org
Control: affects -1 + src:pupnp-1.8

Please remove the source package pupnp-1.8 and the remaining two binary
packages, libixml10 and libupnp13, from the archive. The source package
was renamed to pupnp providing binary packages with bumped SONAMEs.

Cheers
-- 
Sebastian Ramacher

Bug#995670: What's the status of this ITP?

[Abraham Raji]

Hey folks o/,

What's the status of this ITP? It seems like Nick is pulling a
considerable amount of work himself. I would personally love to see Zig
in the Debian archives so I am ready to volunteer some of my time
towards the effort.

I feel we can move the work for this package to salsa if no one has any
issues.

Best,
Abraham

Bug#1014890: ITP: python3-looseversion -- Version numbering for anarchists and software realists

[Yaroslav Halchenko]

Thank you Alban,

done -- join/finish up 
https://salsa.debian.org/python-team/packages/python-looseversion
please 

On Mon, 19 Jun 2023, Alban Browaeys wrote:

> on January 4th of 2023 you retitled this RFP to ITP.

> > ITP: python3-looseversion -- Version numbering for anarchists and
> software realists

> Do you have an early package code or python3-looseversion to share (on
> debian salsa or else)?

> I will have to create such a package otherwise as salt 3006 depends
> upon python3 looseversion (I am building it based upon the salt 3005
> deb pacakging from
> openmediavault 
> https://github.com/openmediavault/packages/tree/master/pool/main/s/salt
> ).
> So even if you only did an early frame of it that would avoid duplicate
> effort.
-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
WWW:   http://www.linkedin.com/in/yarik



signature.asc
Description: PGP signature

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

[Dan Fandrich]

This dependency was removed upstream in v0.0.18 (and v0.0.19).

Bug#1038670: firefox-esr: Can't set Firefox as a default mailing application

[Dmitry K]

Package: firefox-esr
Version: 102.12.0esr-1~deb12u1
Severity: minor
Tags: patch upstream
X-Debbugs-Cc: kuteyni...@gmail.com

Dear Maintainer,

I have selected "Use Gmail" in Firefox Settings -> General -> Applications ->
mailto.
Then I wanted to assign Firefox as a default mailing app in Default
Applications of Gnome settings in order to launch Firefox with Gmail
automatically from external apps. However, Firefox wasn't listed among
available options for Mail.

The reason is probably in the fact that x-scheme-handler/mailto isn't listed in
MimeType field of /usr/share/applications/firefox-esr.desktop:

MimeType=text/html;text/xml;application/xhtml+xml;application/xml;application/vnd.mozilla.xul+xml;application/rss+xml;application/rdf+xml;image/gif;image/jpeg;image/png;x-scheme-
handler/http;x-scheme-handler/https;

The man page of xdg-mime says: "The application's desktop file must list
support for all the MIME types that it wishes to be the default handler for".
So the fix might look as follows:

MimeType=text/html;text/xml;application/xhtml+xml;application/xml;application/vnd.mozilla.xul+xml;application/rss+xml;application/rdf+xml;image/gif;image/jpeg;image/png;x-scheme-
handler/http;x-scheme-handler/https;x-scheme-handler/mailto;

As a workaround I had to assign Firefox manually via the configuration file
~/.config/mimeapps.list:
[Default Applications]
x-scheme-handler/mailto=firefox-esr.desktop

Only after this manual intervention Gnome accepted Firefox as a mail app.

Reported to Firefox Bugzilla too:
https://bugzilla.mozilla.org/show_bug.cgi?id=1839244


-- Package-specific info:


-- Addons package information

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

Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
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 firefox-esr depends on:
ii  debianutils  5.7-0.4
ii  fontconfig   2.14.1-4
ii  libasound2   1.2.8-1+b1
ii  libatk1.0-0  2.46.0-5
ii  libc62.36-9
ii  libcairo-gobject21.16.0-7
ii  libcairo21.16.0-7
ii  libdbus-1-3  1.14.6-1
ii  libdbus-glib-1-2 0.112-3
ii  libevent-2.1-7   2.1.12-stable-8
ii  libffi8  3.4.4-1
ii  libfontconfig1   2.14.1-4
ii  libfreetype6 2.12.1+dfsg-5
ii  libgcc-s112.2.0-14
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libglib2.0-0 2.74.6-2
ii  libgtk-3-0   3.24.37-2
ii  libnspr4 2:4.35-1
ii  libnss3  2:3.87.1-1
ii  libpango-1.0-0   1.50.12+ds-1
ii  libstdc++6   12.2.0-14
ii  libvpx7  1.12.0-1
ii  libx11-6 2:1.8.4-2
ii  libx11-xcb1  2:1.8.4-2
ii  libxcb-shm0  1.15-1
ii  libxcb1  1.15-1
ii  libxcomposite1   1:0.4.5-1
ii  libxdamage1  1:1.1.6-1
ii  libxext6 2:1.3.4-1+b1
ii  libxfixes3   1:6.0.0-2
ii  libxrandr2   2:1.5.2-2+b1
ii  libxtst6 2:1.2.3-1.1
ii  procps   2:4.0.2-3
ii  zlib1g   1:1.2.13.dfsg-1

Versions of packages firefox-esr recommends:
ii  libavcodec59  7:5.1.3-1

Versions of packages firefox-esr suggests:
pn  fonts-lmodern  
pn  fonts-stix | otf-stix  
ii  libcanberra0   0.30-10
ii  libgssapi-krb5-2   1.20.1-2
pn  pulseaudio 

-- no debconf information

Bug#1038669: RFS: veryfasttree/4.0-1 [ITP] -- Speeding up the estimation of phylogenetic trees from sequences

[PIÑEIRO POMAR CESAR ALFREDO]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

 * Package name : veryfasttree
   Version  : 4.0-1
   Upstream contact : César Pomar 
 * URL  : https://github.com/citiususc/veryfasttree
 * License  : MPL-2.0, Custom-License-2, BSD-2-clause, MIT, GPL-3.0, 
BSL-1.0, Custom-License-3, Custom-License-1
 * Vcs  : https://github.com/citiususc/veryfasttree
   Section  : science

The source builds the following binary packages:

  veryfasttree - Speeding up the estimation of phylogenetic trees from sequences

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/v/veryfasttree/veryfasttree_4.0-1.dsc

Changes for the initial release:

 veryfasttree (4.0-1) unstable; urgency=low
 .
   *Closes: #1038668
   *Introduction of new thread levels for improved parallelization.
   *Enhanced performance through new parallel regions (e.g., ML Lengths,
 ML splits, LogLk, etc.).
   *Threads used in tree creation: Top hits, TopHitNJSearch, FastNJSearch, and
 ExhaustiveNJSearch(-slow).
   *Implementation of a faster tree partitioning approach with significant
 speed improvements.
   *Tree partitioning limited to NNI, SPR, and upProfiles computations for
 memory conservation.
   *Parallel tree traversal implemented for remaining parts.
   *Replacement of disk storage for profiles with Disk Computing.
   *Shared and reused Top upProfiles among threads for memory efficiency and
 accelerated sequential parts.
   *Improved non-deterministic mode with removal of mutex usage.
   *Optimized performance by parallelizing non-deterministic parts in
 deterministic mode.
   *Also implemented non-deterministic parts in deterministic mode for
 improved performance.
   *Deterministic mode now outperforms non-deterministic mode in terms of speed.
   *Tree partitioning method logging now hidden by default.
   *Support for Fastq format and libBZ2 compression.
   *Support for reading trees from NEXUS block trees.
   *Nvidia CUDA GPU computing support. (Experimental)
   *Introduced parallel compilation.
   *Incorporation of changes from FastTree-2.11.
   *Clang Support
   *Addressed critical errors and implemented substantial corrections.

Regards,
--
  César Pomar

Bug#1033703: gffread: autopkgtest regression: test dependency not in testing

[Étienne Mollier]

Trying to resolve the situation by removing dependency on
trinityrnaseq-examples, I noticed that the autopkgtest setup now
fails with a conflict over boost versions, pulled by the game of
transitive dependencies:

The following packages have unmet dependencies:
 libboost1.81-dev : Conflicts: libboost1.74-dev but 1.74.0+ds1-21 is to 
be installed

I didn't manage to identify which packages cause this condition,
though.

Have a nice day,  :)
-- 
  .''`.  Étienne Mollier 
 : :' :  gpg: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/2, please excuse my verbosity
   `-on air: John Arch - Cheyenne


signature.asc
Description: PGP signature

Bug#1030129: Additional information

[Vladimir Petko]

Would it be possible to consider a temporary fix[1] until all relevant
openjdk packages are updated?

[1] https://salsa.debian.org/java-team/ca-certificates-java/-/merge_requests/8

Bug#1038668: ITP: veryfasttree -- Speeding up the estimation of phylogenetic trees for large alignments through parallelization and vectorization strategies

[PIÑEIRO POMAR CESAR ALFREDO]

Package: wnpp
Severity: wishlist
Owner: Cesar Pomar 

* Package name: veryfasttree
  Version : 4.0
  Upstream Author : Cesar Pomar 
* URL : https://github.com/citiususc/veryfasttree
* License : GPL
  Programming Lang: C++
  Description : Speeding up the estimation of phylogenetic trees for large 
alignments through parallelization and vectorization strategies

VeryFastTree is a highly efficient implementation inspired by the FastTree-2
tool, designed to expedite the inference of approximately-maximum-likelihood
phylogenetic trees from nucleotide or protein sequence alignments. It is an
optimized implementation designed to accelerate the estimation of phylogenies
for large alignments. By leveraging parallelization and vectorization
strategies, VeryFastTree significantly improves the performance and
scalability of phylogenetic analysis, allowing it to construct phylogenetic
trees in a fraction of the time previously required.

Maintaining the integrity of FastTree-2, VeryFastTree retains the same phases,
methods, and heuristics used for estimating phylogenetic trees. This ensures
that the topological accuracy of the trees produced by VeryFastTree remains
equivalent to that of FastTree-2. Moreover, unlike the parallel version of
FastTree-2, VeryFastTree guarantees deterministic results, eliminating any
potential variations in the output.

To facilitate a seamless transition for users, VeryFastTree adopts the exact
same command line arguments as FastTree-2. This means that by simply
substituting FastTree-2 with VeryFastTree, and using the same set of options,
users can significantly enhance the overall performance of their phylogenetic
analyses.


   - why is veryfasttree useful/relevant? if there are other packages providing
similar functionality, how does it compare?:

   VeryFastTree is a highly tuned implementation of the FastTree(which is 
already
   published in the Debian repositories). VeryFastTree takes advantage of
   parallelization and vectorization strategies to boost performance. In our
   publication[1], we demonstrated that VeryFastTree performs between 7.8x and 
3.5x
   times faster than FastTree for the same input and options. We are currently
   working on a second publication with version 4.0, where we show an even 
greater
   performance improvement, we can complete the creation of phylogenetic trees 
with
   2 million sequences in just a couple of days, whereas it would take FastTree 
more
   than two weeks.

   [1] VeryFastTree: speeding up the estimation of phylogenies for large 
alignments
   through parallelization and vectorization strategies, César Piñeiro, José M. 
Abuín,
   and Juan C. Pichel, Bioinformatics, vol. 36, no. 17, pages 4658-4659, 2020.

  -how do you plan to maintain it?. do you need a sponsor?:

   Until now, the tool has been maintained through GitHub issues. As the 
authors of the tool,
   we will resolve the problems that are reported.

   Yes, we are looking for a sponsor for the publication of the package.

Bug#832000: grip: new upstream release (4.5.2)

[Gürkan Myczko]

meanwhile there is 4.6.1 available, i'd really like this even in 
bookworm-backports once it's announced...


best,

Bug#1038132: qtwebengine-opensource-src: FTBFS: ../../3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125: Error: operand type mismatch for `shr'

[Gerardo Esteban Malazdrewicz]

Please apply ffmpeg-remove-x86-optimization.patch to qtwebengine-opensource-
src-5.15.14

Thanks,
Gerardo

Bug#1038667: O: zlmdb -- Object-relational in-memory database layer based on LMDB

[Bastian Germann]

Package: wnpp

I hereby orphan the zlmdb package. I do not use it anymore and do not have the 
time to maintain it properly.
Please keep it in the Python Team if you consider adopting it.

The package was introduced to satisfy labgrid's dependencies.

Bug#1038665: CONFIG_VIRTIO_MEM=m missing in debian 12 kernels

[Salvatore Bonaccorso]

Control: tags -1 + confirmed 

Hi,

On Mon, Jun 19, 2023 at 09:44:51PM +0200, Laurent GUERBY wrote:
> Package: linux-image-amd64
> Severity: important
> 
> Hi,
> 
> CONFIG_VIRTIO_MEM=m is missing in debian 12, it was there in debian 11
> and 10 and may be before.
> 
> It's still there unchanged in upstream kernel sources:
> 
>  18>
> 
> Browsing https://salsa.debian.org/kernel-team/linux.git I couldn't find
> VIRTIO_MEM in master or bookworm but I might not be looking at the
> right place.
> 

Appears to b be a consequence of the upstream change e7c552ec8978
("virtio: drop default for virtio-mem") in 5.17-rc8 ...

Regards,
Salvatore

Bug#1038666: O: labgrid -- Embedded board control programs

[Bastian Germann]

Package: wnpp

I hereby orphan the labgrid package. I do not use it anymore and do not have 
the time to maintain it properly.
Please keep it in the Python Team if you consider adopting it.

The package does not have the full feature set enabled; see #1026390.

Bug#1038665: CONFIG_VIRTIO_MEM=m missing in debian 12 kernels

[Laurent GUERBY]

Package: linux-image-amd64
Severity: important

Hi,

CONFIG_VIRTIO_MEM=m is missing in debian 12, it was there in debian 11
and 10 and may be before.

It's still there unchanged in upstream kernel sources:



Browsing https://salsa.debian.org/kernel-team/linux.git I couldn't find
VIRTIO_MEM in master or bookworm but I might not be looking at the
right place.

Sincerely,

Laurent GUERBY

Bug#1028231: unibilium: parse-terminfo test uses wrong terminfo directory

[Sven Joachim]

On 2023-01-08 18:17 +0100, Sven Joachim wrote:

> Source: unibilium
> Version: 2.1.0-1
>
> The parse-terminfo autopkgtest uses a wrong directory for terminfo files
> below /usr:
>
> ,
> | for term in ansi xterm screen rxvt-unicode; do
> |   libterm=/lib/terminfo/${term%${term#?}}/${term}
> |   usrterm=/usr/${libterm}
> `
>
> The (bulk of the) terminfo database is located below /usr/share/terminfo
> rather than /usr/lib/terminfo.  For now this does not matter as we
> install the basic terminfo files in ncurses-base under /lib/terminfo,
> but after the Bookworm release I plan to relocate them to
> /usr/share/terminfo, see https://bugs.debian.org/1028202.  Once that
> happens, your test will still succeed but not do anything, if I read it
> correctly.

FYI, the ncurses-base package in experimental has moved the terminfo
files to /usr/share/terminfo, and indeed the parse-terminfo autopkgtest
does not do anything[1].  Maybe it is time to upload the pending fixes,
now that Bookworm has been released?

Cheers,
   Sven


1. 
https://ci.debian.net/data/autopkgtest/unstable/amd64/u/unibilium/34445754/log.gz

Bug#1033316: Autopkgtest is flaky

[Christoph Berg]

Control: severity -1 serios

Re: To Debian Bug Tracking System
> ruby-moneta is currently showing up on
> https://qa.debian.org/excuses.php?package=postgresql-common as a
> regression in postgresql-common, but that's not true, the code hasn't
> changed.
> 
> https://ci.debian.net/packages/r/ruby-moneta/testing/amd64/
> 
> This has already happened last week. Clicking the retry buttons
> resolved the issue back then, on some architectures by making the test
> pass, and on other architectures by making even the "reference" test
> fail.
> 
> Please fix the tests to be stable.

Hi,

this has been hitting again and again intermittently during the
bookworm release. Please fix the package so it doesn't get in the way
of other package's testing migration.

Thanks,
Christoph

Bug#1038664: toot: save local copies of every new outbound message

[debbug . toot]

Package: toot
Version: 0.27.0-1
Severity: wishlist
X-Debbugs-Cc: debbug.t...@sideload.33mail.com

The Mastodon export feature is insufficient:

 * countless events can separate users from their data at any unannounced 
spontaneous moment
 * users can only request archives once every 7 days, thus ≥3½ days of dataloss 
is expected on avg.
 * the request is a cumbersome manual process (thus not done every 7 days)

There is a request to implement CLI-driven archival:

  https://github.com/ihabunek/toot/issues/201

That feature would be useful, but it’s still only a partial
solution. In addition to periodic archivals it would be very useful
for individual messages to be stored locally to mitigate the loss of
data generated since the last fetched archival, just as an email
client would do.

Bonus points if those messages are formatted in mbox format or maildir
format, so we can simply use a mail user agent to browse recent
outbound msgs.

Optionally, it would be interesting if users had the /option/ of
having these cached msgs deleted upon the successful fetching of their
archive (assuming GH bug 201 is satisfied).

-- System Information:
Debian Release: 11.5
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 
'testing'), (990, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages toot depends on:
ii  python3   3.9.2-3
ii  python3-bs4   4.9.3-1
ii  python3-requests  2.25.1+dfsg-2
ii  python3-urwid 2.1.2-1
ii  python3-wcwidth   0.1.9+dfsg1-2

toot recommends no packages.

toot suggests no packages.

-- no debconf information

Bug#1038534: pinball-table-hurd: Depends on SDL 1.2

[philippe.co...@ik.me]

Hi Simon or any maintainer,

Can you please upload the SDL2 packages that were stalling before
bookwork release:

https://mentors.debian.net/packages/uploader/r...@users.sf.net/

Regards

Bug#1038650: closed by Sebastiaan Couwenberg (Re: Bug#1038650: libnetcdf19: build support for parallel io)

[Sebastiaan Couwenberg]

On 6/19/23 20:02, Drew Parsons wrote:

On 2023-06-19 19:51, Sebastiaan Couwenberg :


No, see prior discussion on the debian-gis list:

https://lists.debian.org/debian-gis/2018/04/msg00020.html


Ok, thanks for the reference.


If you need MPI netcdf, use netcdf-parallel:

 https://tracker.debian.org/pkg/netcdf-parallel


That makes sense.

What I'm really looking for is the parallel support in the python 
module, python3-netcdf4, so I filed this bug against the wrong package. 
Multiple builds of the python package might be a bit trickier to manage. 
It was done for h5py, with some effort.


Like netcdf, I'm not willing to maintain MPI support in netcdf4-python.

Ideally netcdf upstream support building both serial and parallel 
variants of the library, and having both installed.


Library users can then choose which is best for their use case.

This is something upstream needs to support. As long as we need to 
choose one or the other for the package in Debian, we will choose the 
serial variant as the lowest common denominator. This also has the bonus 
of not having to bother choosing an MPI implementation.


Kind Regards,

Bas

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

Bug#1037052: minidlna: diff for NMU version 1.3.2+dfsg-1.1

[Salvatore Bonaccorso]

Control: tags 1037052 + patch
Control: tags 1037052 + pending


Dear maintainer,

I've prepared an NMU for minidlna (versioned as 1.3.2+dfsg-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards,
Salvatore
diff -Nru minidlna-1.3.2+dfsg/debian/changelog minidlna-1.3.2+dfsg/debian/changelog
--- minidlna-1.3.2+dfsg/debian/changelog	2023-04-12 13:01:40.0 +0200
+++ minidlna-1.3.2+dfsg/debian/changelog	2023-06-19 21:14:33.0 +0200
@@ -1,3 +1,10 @@
+minidlna (1.3.2+dfsg-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * upnphttp: Fix chunk length parsing (CVE-2023-33476) (Closes: #1037052)
+
+ -- Salvatore Bonaccorso   Mon, 19 Jun 2023 21:14:33 +0200
+
 minidlna (1.3.2+dfsg-1) unstable; urgency=medium
 
   * New upstream release (Closes: #1005219, #1011629, #1017183, #1024905).
diff -Nru minidlna-1.3.2+dfsg/debian/patches/12-upnphttp-Fix-chunk-length-parsing.patch minidlna-1.3.2+dfsg/debian/patches/12-upnphttp-Fix-chunk-length-parsing.patch
--- minidlna-1.3.2+dfsg/debian/patches/12-upnphttp-Fix-chunk-length-parsing.patch	1970-01-01 01:00:00.0 +0100
+++ minidlna-1.3.2+dfsg/debian/patches/12-upnphttp-Fix-chunk-length-parsing.patch	2023-06-19 21:14:33.0 +0200
@@ -0,0 +1,27 @@
+From: Justin Maggard 
+Date: Wed, 31 May 2023 00:40:03 -0700
+Subject: upnphttp: Fix chunk length parsing
+Origin: https://sourceforge.net/p/minidlna/git/ci/9bd58553fae5aef3e6dd22f51642d2c851225aec/
+Bug-Debian: https://bugs.debian.org/1037052
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2023-33476
+
+---
+ upnphttp.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/upnphttp.c b/upnphttp.c
+index 05b202067f14..477ebef4caee 100644
+--- a/upnphttp.c
 b/upnphttp.c
+@@ -432,7 +432,7 @@ next_header:
+ 		if (h->req_buflen <= h->req_contentoff)
+ 			return;
+ 		while( (line < (h->req_buf + h->req_buflen)) &&
+-		   (h->req_chunklen = strtol(line, , 16) > 0) &&
++		   ((h->req_chunklen = strtol(line, , 16)) > 0) &&
+ 		   (endptr != line) )
+ 		{
+ 			endptr = strstr(endptr, "\r\n");
+-- 
+2.40.1
+
diff -Nru minidlna-1.3.2+dfsg/debian/patches/series minidlna-1.3.2+dfsg/debian/patches/series
--- minidlna-1.3.2+dfsg/debian/patches/series	2023-04-12 12:57:50.0 +0200
+++ minidlna-1.3.2+dfsg/debian/patches/series	2023-06-19 21:14:33.0 +0200
@@ -5,3 +5,4 @@
 08-Fix-testupnpdescgen-build.patch
 10-do-not-close-socket-on-sighup.patch
 11-improve-nl-translation.patch
+12-upnphttp-Fix-chunk-length-parsing.patch

Bug#1038663: jtidy: CVE-2023-34623

[Moritz Mühlenhoff]

Source: jtidy
X-Debbugs-CC: t...@security.debian.org
Severity: important
Tags: security

Hi,

The following vulnerability was published for jtidy.

CVE-2023-34623[0]:
| An issue was discovered jtidy thru r938 allows attackers to cause a
| denial of service or other unspecified impacts via crafted object
| that uses cyclic dependencies.

https://github.com/trajano/jtidy/issues/4

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-34623
https://www.cve.org/CVERecord?id=CVE-2023-34623

Please adjust the affected versions in the BTS as needed.

Bug#1038662: iceoryx: FTBFS on 32bit archs (test issue)

[Gianfranco Costamagna]

Source: iceorvx
Version: 2.0.3+dfsg-1
Severity: serious

Hello, looks like some regression happened on armhf at least, and the failing 
test seems to indicate that it shouldn't be run on 32bit architectures.
I checked local pbuilder/qemu-armhf sid environment and I reproduced the issue, 
as well as in Ubuntu

https://launchpad.net/ubuntu/+source/iceoryx/2.0.3+dfsg-1/+build/26010105

[ Reserving shared memory successful ]
2023-06-19 13:47:04.351 [Warning]: Runnning RouDi on 32-bit 
architectures is not supported! Use at your own risk!
2023-06-19 13:47:04.351 [Warning]: Running applications on 
32-bit architectures is not supported! Use at your own risk!
2023-06-19 13:47:04.351 [Warning]: RouDi not found - waiting 
...
RouDi is ready for clients
2023-06-19 13:47:04.451 [Warning]: ... RouDi found.
[   OK ] iox_service_discovery_test.FindServiceReturnsOfferedService (379 
ms)
[ RUN  ] 
iox_service_discovery_test.FindServiceReturnsCorrectNumberOfServicesWhenServiceContainerTooSmall
Reserving 3432 bytes in the shared memory [iceoryx_mgmt]
[ Reserving shared memory successful ]
Reserving 149264720 bytes in the shared memory [buildd]
[ Reserving shared memory successful ]
2023-06-19 13:47:04.742 [Warning]: Runnning RouDi on 32-bit 
architectures is not supported! Use at your own risk!
2023-06-19 13:47:04.742 [Warning]: Running applications on 
32-bit architectures is not supported! Use at your own risk!
2023-06-19 13:47:04.743 [Warning]: RouDi not found - waiting 
...
RouDi is ready for clients
2023-06-19 13:47:04.843 [Warning]: ... RouDi found.
[   OK ] 
iox_service_discovery_test.FindServiceReturnsCorrectNumberOfServicesWhenServiceContainerTooSmall
 (385 ms)
[--] 7 tests from iox_service_discovery_test (2545 ms total)

[--] 25 tests from iox_sub_test
[ RUN  ] iox_sub_test.initSubscriberWithNullptrForStorageReturnsNullptr
2023-06-19 13:47:04.985 [Warning]: subscriber initialization 
skipped - null pointer provided for iox_sub_storage_t
[   OK ] iox_sub_test.initSubscriberWithNullptrForStorageReturnsNullptr (0 
ms)
[ RUN  ] iox_sub_test.initSubscriberWithDefaultOptionsWorks
Reserving 3432 bytes in the shared memory [iceoryx_mgmt]
[ Reserving shared memory successful ]
Reserving 149264720 bytes in the shared memory [buildd]
[ Reserving shared memory successful ]
2023-06-19 13:47:05.124 [Warning]: Runnning RouDi on 32-bit 
architectures is not supported! Use at your own risk!
2023-06-19 13:47:05.124 [Warning]: Running applications on 
32-bit architectures is not supported! Use at your own risk!
2023-06-19 13:47:05.124 [Warning]: RouDi not found - waiting 
...
RouDi is ready for clients
2023-06-19 13:47:05.225 [Warning]: ... RouDi found.
binding_c_moduletests: ./iceoryx_binding_c/source/c_subscriber.cpp:114: cpp2c_Subscriber* 
iox_sub_init(iox_sub_storage_t*, const char*, const char*, const char*, const iox_sub_options_t*): Assertion 
`reinterpret_cast(me) - reinterpret_cast(meWithStoragePointer) == 
sizeof(void*) && "Size mismatch for SubscriberWithStoragePointer!"' failed.
Aborted (core dumped)
make[1]: *** [debian/rules:55: override_dh_auto_test-arch] Error 134
make[1]: Leaving directory '/<>'


Can you please exclude it?

thanks

Gianfranco


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1033092: (no subject)

[Rowan Wookey]

There's a workaround posted on the forums 
https://forums.debian.net/viewtopic.php?p=774201#p774201


>https://github.com/systemd/systemd/issues/18791

>tl;dr: copy /etc/xdg/autostart/spice-vdagent.desktop to 
~/.config/autostart/ then comment out the "X-GNOME-Autostart-Phase" line.

Bug#1038661: interfaces.5: some remarks and fixes for the manual

[Bjarni Ingi Gislason]

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

Dear Maintainer,

here are some notes and editorial fixes for the manual

The patch is in the attachment as a compressed file.

#

Input file is interfaces.5

Output from "mandoc  -T lint interfaces.5":

mandoc: interfaces.5:207:2: WARNING: skipping paragraph macro: PP empty

and more lines about input lines being too long.

###

Remove space characters at the end of lines.

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

503:This method may be used to define the IPv4 loopback interface. 
511:This method may be used to define Ethernet interfaces with statically 
allocated IPv4 addresses. 
544:This method may be used to define interfaces for which no configuration is 
done by default. Such interfaces can be configured manually by means of 
\fBup\fP and \fBdown\fP commands or /etc/network/if-*.d scripts. 
556:This method may be used to obtain an address via DHCP with any of the 
tools: dhclient, udhcpc, dhcpcd. (They have been listed in their order of 
precedence.) If you have a complicated DHCP setup you should note that some of 
these clients use their own configuration files and do not obtain their 
configuration information via \fBifup\fP. 
580:This method may be used to obtain an address via bootp. 
595:This method is used to create GRE or IPIP tunnels. You need to have the 
\fBip\fP binary from the \fBiproute\fP package. For GRE tunnels, you will need 
to load the ip_gre module and the ipip module for IPIP tunnels. 
628:This method uses pon/poff to configure a PPP interface. See those commands 
for details. 
643:This method uses wvdial to configure a PPP interface. See that command for 
more details. 
652:This method uses avahi-autoipd to configure an interface with an IPv4 
Link-Layer address (169.254.0.0/16 family). This method is also known as APIPA 
or IPAC, and often colloquially referred to as "Zeroconf address". 
663:This method may be used to setup an IPX interface. It requires the 
\fIipx_interface\fP command. 
675:This method may be used to setup an IPX interface dynamically. 
687:This method may be used to define interfaces with automatically assigned 
IPv6 addresses. Using this method on its own doesn't mean that RDNSS options 
will be applied, too. To make this happen, \fBrdnssd\fP daemon must be 
installed, properly configured and running. If stateless DHCPv6 support is 
turned on, then additional network configuration parameters such as DNS and NTP 
servers will be retrieved from a DHCP server. Please note that on ifdown, the 
lease is not currently released (a known bug). 
711:This method may be used to define the IPv6 loopback interface. 
719:This method may be used to define interfaces with statically assigned IPv6 
addresses. By default, stateless autoconfiguration is disabled for this 
interface. 
767:This method may be used to define interfaces for which no configuration is 
done by default. Such interfaces can be configured manually by means of 
\fBup\fP and \fBdown\fP commands or /etc/network/if-*.d scripts. 
779:This method may be used to obtain network interface configuration via 
stateful DHCPv6 with dhclient. In stateful DHCPv6, the DHCP server is 
responsible for assigning addresses to clients. 
803:This method is used to create IP6GRE, IP6IP6 or IPIP6 tunnels. You need to 
have the \fBip\fP binary from the \fBiproute\fP package. For IP6GRE tunnels, 
you will need to load the ip6_gre module and the ip6_tunnel module for IP6IP6 
or IPIP6 tunnels. 
842:This method may be used to setup an IPv6-over-IPv4 tunnel. It requires the 
\fBip\fP command from the \fBiproute\fP package. 
875:This method may be used to setup a 6to4 tunnel. It requires the \fBip\fP 
command from the \fBiproute\fP package. 
899:This method may be used to setup a Controller Area Network (CAN) interface. 
It requires the the \fBip\fP command from the \fBiproute\fP package. 

#

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

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

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

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


669:\fItype\fP of Ethernet frames to use (e.g. \fB802.2\fP)
681:\fItype\fP of Ethernet frames to use (e.g. \fB802.2\fP)

#

Reduce space between words.

161:it is accompanied by a  suffix of the form \fI=LOGICAL\fR, in which case
164:mapping specifications,  until no further mappings are possible.  If the

#

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

293:The exception is when ifup is called with the --allow option,
312:when "ifup --allow hotplug eth0" is called (either manually or because udev 
triggers this when a 

Bug#1036069: gnat: 'gprconfig --show-targets' fails with constraint_error

[Nicolas Boulenguez]

Package: gnat
Followup-For: Bug #1036069
Control: reassign -1 gprbuild 2023.0.0-3

Bug#1038660: desktop-base: please set a placeholder theme during development, different from any release

[Simon McVittie]

Package: desktop-base
Version: 12.0.6
Severity: normal
Tags: trixie sid

Now that Debian 12 has been released, the version of desktop-base in
testing should no longer include Debian 12 branding, so that the testing
installer will be visually distinct from the Debian 12 stable release.

The simplest possible implementation of this would be to remove the "12"
from all the art components, but I think it would be better to use artwork
that is obviously different.

One simple "programmer-art" way to do that would be to desaturate the
Debian 12 artwork down to greyscale to make it obviously a placeholder,
or rotate the hue to make it a different colour.

However, it might be nicer (and definitely more fun!) to have a theme
specifically for Debian in its alpha/beta state, with a sense of "this is
under construction", to be replaced by a proper Debian 13 theme closer
to the Debian 13 freeze. Some of the contributors who were helping with
debian-cd testing during the Debian 12 release process had a similar
thought a while ago, and got as far as preparing a background image for
this purpose - I'll ask them to follow up here.

Prior art: GNOME applications built from their alpha/beta branches often
have yellow and black stripes (resembling hazard tape) overlaying part
of their icon, and a gear-wheel motif in the titlebar, to distinguish
them from the stable version of the same application.

smcv

Bug#1038659: toot: polls are useless in the CLI

[debbug . toot]

Package: toot
Version: 0.27.0-1
Severity: normal
X-Debbugs-Cc: debbug.t...@sideload.33mail.com

Polls are void in CLI output. The body is there, but the ballot is
simply omitted. And it’s omitted in a such a way that you don’t even
know there is a poll. So you end up seeing /part/ of a status that
ends up being confusing & useless.

I’m sure it’s not an oversight at this point. Perhaps there is some
complexity involved. If so, I suggest doing a quick placeholder of
some kind so users at least know that a poll is missing. E.g. print in
red letters somewhere: “[poll output not implemented in this
version]”. Users would at least then know to get a dump of the raw
post whenever this feature gets added:

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

or to view it in the tui.

In the long term, it’s worth noting that *no client* does polls
well. You only ever see the votes that your server has received. In
principle, these are subset and can be misleading. So ideally the
votes should be counted at the server that hosted the poll, not the
local server (if possible).

-- System Information:
Debian Release: 11.5
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 
'testing'), (990, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages toot depends on:
ii  python3   3.9.2-3
ii  python3-bs4   4.9.3-1
ii  python3-requests  2.25.1+dfsg-2
ii  python3-urwid 2.1.2-1
ii  python3-wcwidth   0.1.9+dfsg1-2

toot recommends no packages.

toot suggests no packages.

-- no debconf information

Bug#1037956: mailman3-web: SQL Syntax error installing mailman3-web on mariadb - posible fix

[Falk Hackenberger]

Hello,


i fix it with this patch:

https://gitlab.com/mailman/mailman-suite/-/commit/7f5dfd4992d4c454327233453608fc5f42ca29b6

and also configure the mailman3-web to use mysql use 127.0.0.1 and not 
localhost.

Bug#1037956: How to fix: mailman3-web: SQL Syntax error installing mailman3-web on mariadb

[Falk Hackenberger]

Hello,


i fix it with this patch:

https://gitlab.com/mailman/mailman-suite/-/commit/7f5dfd4992d4c454327233453608fc5f42ca29b6

and also configure the mailman3-web to use mysql use 127.0.0.1 and not 
localhost.

Bug#1028137: [Pkg-electronics-devel] Bug#1028137: nextpnr: Support for more FPGA architectures (esp. ECP5)

[Jonathan Neuschäfer]

On Tue, Jun 13, 2023 at 05:40:17PM +0200, Daniel Gröber wrote:
> Hi Jonathan,
>
> On Sat, Jan 07, 2023 at 06:01:11PM +0100, Jonathan Neuschäfer wrote:
> > to increase the usefulness of nextpnr in Debian, it would be nice to
> > package build nextpnr for more FPGA architectures, in addition to iCE40.
> > ECP5 comes to mind, because it seems to be fairly usable by now.
>
> I don't have an ECP5 devboard but what I have rediscovered recently is a
> Tang Nano 9k (Gowin GW1N) devboard. Hence I've been working on enabling
> gowin support. I've got project apicula and nextpnr packaged already but
> I'm waiting on a sponsor.
>
> In the meantime I'm having a look at prjtrellis too, but since I don't have
> any testing hardware I was wondering if you'd be able to do testing once I
> finish packaging?

Yes, I have a board, and I can do testing if I don't forget about it.
Feel free to ping me when the package is ready.


Jonathan

Bug#1038658: linux-image-6.1.0-8-amd64: Spammy warning: xhci_hcd 0000:09:00.3: WARN: HC couldn't access mem fast enough for slot 3 ep 3

[blastrock]

Package: src:linux
Version: 6.1.25-1
Severity: important
X-Debbugs-Cc: b...@ud2.org

Dear Maintainer,

This is a bug I have had for a long time (a year?) and that happens rarely but
is still very annoying.

I don't know if it's related to me plugging in or out USB devices, but at some
point, the kernel will spam this message:

Jun 19 19:33:00 bugstorm kernel: xhci_hcd :09:00.3: WARN: HC couldn't 
access mem fast enough for slot 3 ep 3
Jun 19 19:33:00 bugstorm kernel: xhci_hcd :09:00.3: WARN: HC couldn't 
access mem fast enough for slot 3 ep 3
Jun 19 19:33:00 bugstorm kernel: xhci_hcd :09:00.3: WARN: HC couldn't 
access mem fast enough for slot 3 ep 3
Jun 19 19:33:00 bugstorm kernel: xhci_hcd :09:00.3: WARN: HC couldn't 
access mem fast enough for slot 3 ep 3
Jun 19 19:33:00 bugstorm kernel: xhci_hcd :09:00.3: WARN: HC couldn't 
access mem fast enough for slot 3 ep 3
Jun 19 19:33:00 bugstorm kernel: xhci_hcd :09:00.3: WARN: HC couldn't 
access mem fast enough for slot 3 ep 3
Jun 19 19:33:00 bugstorm kernel: xhci_hcd :09:00.3: WARN: HC couldn't 
access mem fast enough for slot 3 ep 3
Jun 19 19:33:00 bugstorm kernel: xhci_hcd :09:00.3: WARN: HC couldn't 
access mem fast enough for slot 3 ep 3

around 7500 times per second!

It takes a few minutes for me to notice, but at some point I have no space left
on my root partition.

The only workaround I have is to delete the log files (if I can still use my
system) and reboot.

I can't be sure, but my system looks otherwise normal, I never noticed a device
stopping working. So this warning is very spammy for something that doesn't seem
to have any effect.

Regards,
Philippe


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

** Command line:
BOOT_IMAGE=/boot/vmlinuz-6.1.0-8-amd64 
root=UUID=3802ddd0-c1f4-4b2a-a176-a33d1893f1c7 ro nvidia-drm.modeset=1 
mitigations=off quiet

** Tainted: POE (12289)
 * proprietary module was loaded
 * externally-built ("out-of-tree") module was loaded
 * unsigned module was loaded

** Kernel log:
[4.076891] snd_hda_codec_realtek hdaudioC2D0:mono: mono_out=0x0
[4.076892] snd_hda_codec_realtek hdaudioC2D0:dig-out=0x11/0x0
[4.076893] snd_hda_codec_realtek hdaudioC2D0:inputs:
[4.076895] snd_hda_codec_realtek hdaudioC2D0:  Front Mic=0x19
[4.076896] snd_hda_codec_realtek hdaudioC2D0:  Rear Mic=0x18
[4.076897] snd_hda_codec_realtek hdaudioC2D0:  Line=0x1a
[4.088263] audit: type=1400 audit(1687196710.190:2): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="firejail-default" pid=872 
comm="apparmor_parser"
[4.088532] audit: type=1400 audit(1687196710.190:3): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-senddoc" 
pid=890 comm="apparmor_parser"
[4.089409] usbcore: registered new interface driver btusb
[4.089536] audit: type=1400 audit(1687196710.190:4): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-oosplash" 
pid=889 comm="apparmor_parser"
[4.089569] audit: type=1400 audit(1687196710.190:5): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="lsb_release" pid=874 
comm="apparmor_parser"
[4.090636] audit: type=1400 audit(1687196710.190:6): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/bin/redshift" pid=886 
comm="apparmor_parser"
[4.090676] audit: type=1400 audit(1687196710.190:7): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/bin/freshclam" pid=883 
comm="apparmor_parser"
[4.090871] audit: type=1400 audit(1687196710.190:8): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=885 
comm="apparmor_parser"
[4.090879] audit: type=1400 audit(1687196710.190:9): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="man_filter" pid=885 
comm="apparmor_parser"
[4.090883] audit: type=1400 audit(1687196710.190:10): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="man_groff" pid=885 
comm="apparmor_parser"
[4.092251] input: HD-Audio Generic Front Mic as 
/devices/pci:00/:00:08.1/:0a:00.3/sound/card2/input25
[4.128287] usbcore: registered new interface driver uvcvideo
[4.128367] input: HDA NVidia HDMI/DP,pcm=7 as 
/devices/pci:00/:00:03.1/:08:00.1/sound/card1/input22
[4.128605] input: HDA NVidia HDMI/DP,pcm=8 as 
/devices/pci:00/:00:03.1/:08:00.1/sound/card1/input23
[4.128692] input: HDA NVidia HDMI/DP,pcm=9 as 
/devices/pci:00/:00:03.1/:08:00.1/sound/card1/input24
[4.128705] input: Wacom Intuos5 touch M Pen as 
/devices/pci:00/:00:07.1/:09:00.3/usb3/3-1/3-1.3/3-1.3.2/3-1.3.2:1.0/0003:056A:0027.0009/input/input30
[4.128966] input: 

Bug#1038650: closed by Sebastiaan Couwenberg (Re: Bug#1038650: libnetcdf19: build support for parallel io)

[Drew Parsons]

On 2023-06-19 19:51, Sebastiaan Couwenberg :


No, see prior discussion on the debian-gis list:

https://lists.debian.org/debian-gis/2018/04/msg00020.html


Ok, thanks for the reference.


If you need MPI netcdf, use netcdf-parallel:

 https://tracker.debian.org/pkg/netcdf-parallel


That makes sense.

What I'm really looking for is the parallel support in the python 
module, python3-netcdf4, so I filed this bug against the wrong package.  
Multiple builds of the python package might be a bit trickier to manage. 
It was done for h5py, with some effort.


Drew

Bug#1038657: RM: bzr-git -- ROM; transitional package present since bullseye

[Jelmer Vernooij]

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

Please remove the bzr-git source package; it has been purely
transitional since bullseye.

Bug#1038653: php8.2: upgrade from bullseye w/ older libpcre breaks preg_match()

[Andres Salomon]

Btw, the same errors were also happening with php8.2-cli, when 
wordpress stuff was being executed from cron. Hence the report against 
src:php8.2, and not just against php8.2-fpm.

Bug#1038656: RM: bzr-fastimport -- ROM; transitional package since bullseye & bookworm

[Jelmer Vernooij]

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

Please remove the bzr-fastimport source package; it has been purely
transitional since bullseye

Bug#1038655: RM: bzr-email -- ROM; transitional package present in bookworm & bullseye

[Jelmer Vernooij]

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

Please remove the bzr-email package from the archive. It has been a
purely transitional package since bullseye.

Bug#1038654: RM: bzr-builddeb -- ROM; transitional package that was present for bullseye and bookworm

[Jelmer Vernooij]

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

Please remove the bzr-builddeb package from the archive. It has been a
purely transitional package since bullseye.

Bug#1038653: php8.2: upgrade from bullseye w/ older libpcre breaks preg_match()

[Andres Salomon]

Package: src:php8.2
Version: 8.2.7-1~deb12u1
Severity: normal
Control: tags -1 bookworm

Dear Maintainer,

I have a machine running Wordpress (6.2.2) that was originally 
installed with

buster (10), and then later upgraded to bullseye (11). It was running
php7.2-fpm with nginx.

I wanted to upgrade to bookworm (12) while keeping the system live, so 
I began
by manually upgrading a few key packages. Openssh-server, monit, 
certbot, and a
few others. I also upgraded nginx, and (after manually editing the 
php-fpm.sock

location) the site continued working.

Then I upgraded php. Specifically:

Install: libffi8:amd64 (3.4.4-1, automatic), php8.2-mysql:amd64 
(8.2.7-1~deb12u1, automatic), libaom3:amd64 (3.6.0-1, automatic), 
libheif1:amd64 (1.15.1-1, automatic), libodbc2:amd64 (2.3.11-2, 
automatic), libx265-199:amd64 (3.5-2+b1, automatic), php8.2-soap:amd64 
(8.2.7-1~deb12u1, automatic), libdav1d6:amd64 (1.0.0-2, automatic), 
libtiff6:amd64 (4.5.0-6, automatic), php8.2:amd64 (8.2.7-1~deb12u1, 
automatic), libnuma1:amd64 (2.0.16-1, automatic), libsvtav1enc1:amd64 
(1.4.1+dfsg-1, automatic), php8.2-mbstring:amd64 (8.2.7-1~deb12u1, 
automatic), php8.2-curl:amd64 (8.2.7-1~deb12u1, automatic), 
liblerc4:amd64 (4.0.0+ds-2, automatic), php8.2-opcache:amd64 
(8.2.7-1~deb12u1, automatic), php8.2-imap:amd64 (8.2.7-1~deb12u1, 
automatic), libgav1-1:amd64 (0.18.0-1+b1, automatic), 
php8.2-readline:amd64 (8.2.7-1~deb12u1, automatic), php8.2-odbc:amd64 
(8.2.7-1~deb12u1, automatic), php8.2-igbinary:amd64 (3.2.13-1, 
automatic), php8.2-redis:amd64 (5.3.7+4.3.0-3, automatic), 
libyuv0:amd64 (0.0~git20230123.b2528b0-1, automatic), libwebp7:amd64 
(1.2.4-0.2, automatic), libabsl20220623:amd64 (20220623.1-1, 
automatic), libavif15:amd64 (0.11.1-1, automatic), php8.2-gd:amd64 
(8.2.7-1~deb12u1, automatic), php8.2-sqlite3:amd64 (8.2.7-1~deb12u1, 
automatic), php8.2-bz2:amd64 (8.2.7-1~deb12u1, automatic), 
php8.2-cli:amd64 (8.2.7-1~deb12u1, automatic), php8.2-fpm:amd64 
(8.2.7-1~deb12u1, automatic), php8.2-common:amd64 (8.2.7-1~deb12u1, 
automatic), libde265-0:amd64 (1.0.11-1, automatic), libodbccr2:amd64 
(2.3.11-2, automatic), librav1e0:amd64 (0.5.1-6, automatic), 
php8.2-xml:amd64 (8.2.7-1~deb12u1, automatic), php8.2-zip:amd64 
(8.2.7-1~deb12u1, automatic)
Upgrade: libltdl7:amd64 (2.4.6-15, 2.4.7-5), php-redis:amd64 
(5.3.2+4.3.0-2+deb11u1, 5.3.7+4.3.0-3), php:amd64 (2:7.4+76, 2:8.2+93), 
libodbc1:amd64 (2.3.6-0.1+b1, 2.3.11-2), php-gd:amd64 (2:7.4+76, 
2:8.2+93), php-common:amd64 (2:76, 2:93), php-soap:amd64 (2:7.4+76, 
2:8.2+93), php-curl:amd64 (2:7.4+76, 2:8.2+93), php-readline:amd64 
(2:7.4+76, 2:8.2+93), php-igbinary:amd64 (3.2.1+2.0.8-2, 3.2.13-1), 
php-imap:amd64 (2:7.4+76, 2:8.2+93), php-odbc:amd64 (2:7.4+76, 
2:8.2+93), php-mbstring:amd64 (2:7.4+76, 2:8.2+93), php-bz2:amd64 
(2:7.4+76, 2:8.2+93), php-cli:amd64 (2:7.4+76, 2:8.2+93), php-fpm:amd64 
(2:7.4+76, 2:8.2+93), php-mysql:amd64 (2:7.4+76, 2:8.2+93), 
php-xml:amd64 (2:7.4+76, 2:8.2+93), php-json:amd64 (2:7.4+76, 
2:8.2+93), php-zip:amd64 (2:7.4+76, 2:8.2+93), libgd3:amd64 (2.3.0-2, 
2.3.3-9), php-sqlite3:amd64 (2:7.4+76, 2:8.2+93)
Remove: php7.4-soap:amd64 (7.4.33-1+deb11u4), php7.4-mbstring:amd64 
(7.4.33-1+deb11u4), php7.4-readline:amd64 (7.4.33-1+deb11u4), 
php7.4-gd:amd64 (7.4.33-1+deb11u4), php7.4-curl:amd64 
(7.4.33-1+deb11u4), php7.4-imap:amd64 (7.4.33-1+deb11u4), 
php7.4-odbc:amd64 (7.4.33-1+deb11u4), php7.4-opcache:amd64 
(7.4.33-1+deb11u4), php7.4:amd64 (7.4.33-1+deb11u4), php7.4-bz2:amd64 
(7.4.33-1+deb11u4), php7.4-cli:amd64 (7.4.33-1+deb11u4), 
php7.4-mysql:amd64 (7.4.33-1+deb11u4), php7.4-fpm:amd64 
(7.4.33-1+deb11u4), php7.4-json:amd64 (7.4.33-1+deb11u4), 
php7.4-xml:amd64 (7.4.33-1+deb11u4), php7.4-zip:amd64 
(7.4.33-1+deb11u4), php7.4-sqlite3:amd64 (7.4.33-1+deb11u4), 
php7.4-common:amd64 (7.4.33-1+deb11u4)

End-Date: 2023-06-18  23:25:00

After editing the various .ini and .conf files in /etc/php/8.2 for 
wordpress's
various needs, the site was using php8.2-fpm, but wordpress was broken 
and the

logs were filled with:

2023/06/18 23:25:02 [error] 16059#16059: *3330 FastCGI sent in stderr: 
" 0 in 
/srv/theurbanist.org/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/rules.php 
on line 773; PHP message: PHP Warning:  preg_match(): Compilation 
failed: unrecognised compile-time option bit(s) at offset 0 in 
/srv/theurbanist.org/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/rules.php 
on line 773; PHP message: PHP Warning:  preg_match(): Compilation 
failed: unrecognised compile-time option bit(s) at offset 0 in 
/srv/theurbanist.org/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/rules.php 
on line 773; PHP message: PHP Warning:  preg_match(): Compilation 
failed: unrecognised compile-time option bit(s) at offset 0 in 
/srv/theurbanist.org/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/rules.php 
on line 773; PHP message: PHP Warning:  preg_match(): Compilation 
failed: unrecognised 

Bug#1037980: transmission-daemon: memory leaks

[Sandro Tosi]

On Thu, 15 Jun 2023 14:09:47 +0800 tanying  wrote:
> Package: transmission-daemon
> Version: 3.00-2.1+b1
> Severity: normal
> X-Debbugs-Cc: pls...@hotmail.com

(resending to an open bug, didnt realize the original bug i replied to
is closed)

Sebastian,
it appears the NMU you performed at
https://tracker.debian.org/news/1326874/accepted-transmission-300-21-source-into-unstable/
is causing issues with transmission in stable -- are you going to
address these issues? ideally a fix should be committed to the repo
(or open an MR), a fix uploaded to proposed-updates, and the BTS bugs
should be consolidated into one and closed in the upload.

I'm sure users would also like to know a timeline for the fix, so it'd
be great if you can share that as well

thanks!

Bug#1038652: RM: odhcp6c/experimental -- ROM; unreleased, redundant with dhcpcd

[Ben Hutchings]

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

I originally packaged this program because I needed support for DHCPv6
PDs together with SLAAC.  I never integrated it with ifupdown, and the
same functionality is now available in dhcpcd and probably other
daemons.

Bug#1037980: transmission-daemon: memory leaks

[ilf]

Sounds like a duplicate of #1015003.

--
ilf

If you upload your address book to "the cloud", I don't want to be in it.

Bug#1035186: mpi4py-fft: please add autopkgtests (to add coverage for python3-numpy)

[Drew Parsons]

Package: python3-mpi4py-fft
Version: 2.0.5-1
Followup-For: Bug #1035186

Tests are currently failing inside openmpi libraries. Not sure if it
means hdf5 needs to be rebuilt against latest openmpi.

Tests should be launched from the tests subdir with
  H5PY_ALWAYS_USE_MPI=1 ./runtests.sh

Bug#1038624: netcdf-cxx-legacy: Should not be included in trixie

[Sebastiaan Couwenberg]

Patches have been submitted for the netcdf-cxx-legacy rdeps.

The netcdf-cxx-legacy-rm usertag tracks these bugreports:


https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-...@lists.debian.org=netcdf-cxx-legacy-rm

Bug#992131: R8169 CRASH! (rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100))

[Vincas Dargis]

I've just started getting this on Sid with 6.3:

Jun 19 20:17:43 kernel: r8169 :05:00.1: can't disable ASPM; OS doesn't have 
ASPM control
Jun 19 20:17:43 kernel: r8169 :05:00.1 enp5s0f1: rtl_rxtx_empty_cond == 0 
(loop: 42, delay: 100).

On Sat, 18 Jun 2022 16:02:28 +0200 "a...@prnet.info"  wrote:
I have seen these lines too yesterday on Debian 11, but on Linux 
5.15.0-0.bpo.3-amd64.
kernel: r8169 :03:00.1 eno1: rtl_txcfg_empty_cond == 0 (loop: 42, 
delay: 100).
kernel: r8169 :03:00.1 eno1: rtl_rxtx_empty_cond == 0 (loop: 42, 
delay: 100).
Out of sudden like 2 times, "nmcli network off && nmcli network on" 
helped to temporarily make interface working.
No big updates recently. Only these from apt log: 
https://paste.nolog.cz/?fc818de693f3fd26#ETu59xDaCm4Yeqv8PP4ch8ijdbwjaiuSLSgM2ESqWDhJ

Bug#947685: still occuring on Linux 6.1.0-9-amd64 x86_64

[Vincas Dargis]

I have started getting issues again with recent 6.3 upgrade in Sid, network 
become unstable:

Jun 19 20:17:43 kernel: r8169 :05:00.1: can't disable ASPM; OS doesn't have 
ASPM control
Jun 19 20:17:43 kernel: r8169 :05:00.1 enp5s0f1: rtl_rxtx_empty_cond == 0 
(loop: 42, delay: 100).

Bug#1038651: toot: a CLI mechanism to dump the raw source of a status would be useful

[debbug . toot]

Package: toot
Version: 0.27.0-1
Severity: wishlist
X-Debbugs-Cc: debbug.t...@sideload.33mail.com

The plaintext of a status given on the commandline is an incomplete
representation of the status. There are lots of metadata attributes
being hidden from view as well as poll data. Most of the time it’s
sufficient. But it would be very useful to be able to dump the raw
JSON record for a given status.  As the app matures, the need for raw
record dumps will diminish. But until then the full contents of the
JSON record would be useful.

-- System Information:
Debian Release: 11.5
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 
'testing'), (990, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages toot depends on:
ii  python3   3.9.2-3
ii  python3-bs4   4.9.3-1
ii  python3-requests  2.25.1+dfsg-2
ii  python3-urwid 2.1.2-1
ii  python3-wcwidth   0.1.9+dfsg1-2

toot recommends no packages.

toot suggests no packages.

-- no debconf information

Bug#962407: libhttp-tiny-perl: CVE-2023-31486: Does not default to verify SSL certificates

[gregor herrmann]

Control: tag -1 + fixed-upstream

On Thu, 26 May 2022 12:28:16 +, Damyan Ivanov wrote:

> > > https://github.com/chansen/p5-http-tiny/issues/134
> > Revisiting this issue now, the state seems to be:
> > The upstream ticket was closed with
> > "On reflection, we shouldn't make this change for backwards compatibility."

Update: This is now changed in HTTP::Tiny 0.083 (which also got
imported into perl core 5.38-RC1):
https://metacpan.org/release/DAGOLDEN/HTTP-Tiny-0.084/source/Changes#L11-12


Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#1038650: libnetcdf19: build support for parallel io

[Drew Parsons]

Package: libnetcdf19
Version: 1:4.9.2-1
Severity: normal

netcdf is currently built against the serial variant of hdf5
(libhdf5_serial.so.103).

But hdf5 provides a parallel build
e.g. libhdf5_openmpi.so.103.3.1
via libhdf5-mpi-dev

netcdf can be configured to support parallel io 
https://salsa.debian.org/debian-gis-team/netcdf/-/blob/master/INSTALL.md#building-with-parallel-io-support-build_parallel

In principle parallel io could allow for much faster reading and
writing of large data files.

Should netcdf be configured to start enabling parallel io?

Or would it be useful to provide both serial and parallel variants
like hdf5 does?

Bug#1015003: transmission-daemon: possible memory leaks in crypto-utils-openssl.c

[Sandro Tosi]

Sebastian,
it appears the NMU you performed at
https://tracker.debian.org/news/1326874/accepted-transmission-300-21-source-into-unstable/
is causing issues with transmission in stable -- are you going to
address these issues? ideally a fix should be committed to the repo
(or open an MR), a fix uploaded to proposed-updates, and the BTS bugs
should be consolidated into one and closed in the upload.

I'm sure users would also like to know a timeline for the fix, so it'd
be great if you can share that as well

On Fri, Jun 16, 2023 at 2:51 PM Алексей Шилин  wrote:
>
> Hi,
>
> This is still an issue in stable. Gentoo has a simpler patch [1, also
> attached for convenience] which also works and seems to not have this
> issue. Maybe it's worth dropping current patch in favor of the Gentoo
> one (which is also used by other distributions [2]) and do a stable PU
> upload.
>
>  [1]
> https://gitweb.gentoo.org/repo/gentoo.git/plain/net-p2p/transmission/files/transmission-3.00-openssl-3.patch
>
>  [2] https://github.com/NixOS/nixpkgs/pull/216953



-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

Bug#1037980: [Bug#1037980] Description of my bug

[ilf]

I can confirm this.

After upgrading from bullseye (oldstable) to bookworm (stable), 
transmission-daemon 3.00-2.1+b1 uses much more memory than 3.00-1 
before.


It used to average at about 700 MB and never used more than 1 GB.
Now it grows linearly. After a week of uptime it's currently at 3.2 GB.

I noticed because the machine started swapping for the first time ever.

--
ilf

If you upload your address book to "the cloud", I don't want to be in it.

Bug#1037439: r-cran-rstan/armhf FTBFS with r-cran-bh 1.74

[Dirk Eddelbuettel]

On 19 June 2023 at 16:37, Adrian Bunk wrote:
| On Tue, Jun 13, 2023 at 03:30:18PM -0500, Dirk Eddelbuettel wrote:
| > 
| > On 13 June 2023 at 13:15, Steve Langasek wrote:
| > | Control: reassign -1 r-cran-rstan r-cran-bh
| > | Control: found -1 r-cran-rstan/2.21.8-1
| > | 
| > | Unfortunately, at least in Ubuntu it appears the r-cran-rstan build still
| > | exhausts the 32-bit memory space even with boost 1.81.
| > | 
| > |   
https://launchpad.net/ubuntu/+source/r-cran-rstan/2.21.8-1/+build/26010118
| > 
| > :-/
| > 
| > Not sure that it is fair to point at BH / Boost though.  Anyway.
| > 
| > CRAN no longer checks / compiles 32 bit so upstream may not care, but they
| > are a good team (if busy).  You could ping Ben, he is at
| >Benjamin K Goodrich 
| >...
| 
| The patch below to r-base fixes the build of r-cran-rstan/i386 for me.

Shucks:  You missed a new upstream by a few days.  I'll consider a -2 but
note that ...
 
| This will reduce debug info in the R ecosystem on 32bit to what is 
| required for backtraces, but I assume realistically R on 32bit is
| anyway only sparsely used these days.

... 32 bit is no longer a release architecture for R upstream so this is
borderline either way.

Dirk


| 
| > Dirk
| 
| cu
| Adrian
| 
| --- debian/rules.old  2023-06-18 19:45:14.437261923 +
| +++ debian/rules  2023-06-18 19:51:30.097179612 +
| @@ -90,6 +90,11 @@
|  export DEB_CFLAGS_MAINT_APPEND = -ffloat-store
|  endif
|  
| +## fewer debug info on 32bit to workaround 2-4 GB address space limitation
| +ifeq ($(DEB_HOST_ARCH_BITS), 32)
| +export DEB_CFLAGS_MAINT_APPEND += -g1
| +endif
| +
|  ## edd 31 Mar 2014
|  ## edd 14 Oct 2022  disable LTO per email with Graham Inggs
|  #optimflags  = -O3 -pipe

-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1038649: php8.2: upgrade from bullseye w/ older libpcre breaks preg_match functions

[Andres Salomon]

Source: php8.2-common
Version: 8.2.7-1~deb12u1
Severity: normal
Control: tags -1 bookworm

Dear Maintainer,

I have a machine running wordpress (6.2.2) that was originally installed with
buster (10), and then later upgraded to bullseye (11). It was running
php7.2-fpm with nginx.

I wanted to upgrade to bookworm (12) while keeping the system live, so I began
by manually upgrading a few key packages. Openssh-server, monit, certbot, and a
few others. I also upgraded nginx, and (after manually editing the php-fpm.sock
location) the site continued working.

Then I upgraded php. Specifically:

Install: libffi8:amd64 (3.4.4-1, automatic), php8.2-mysql:amd64 
(8.2.7-1~deb12u1, automatic), libaom3:amd64 (3.6.0-1, automatic), 
libheif1:amd64 (1.15.1-1, automatic), libodbc2:amd64 (2.3.11-2, automatic), 
libx265-199:amd64 (3.5-2+b1, automatic), php8.2-soap:amd64 (8.2.7-1~deb12u1, 
automatic), libdav1d6:amd64 (1.0.0-2, automatic), libtiff6:amd64 (4.5.0-6, 
automatic), php8.2:amd64 (8.2.7-1~deb12u1, automatic), libnuma1:amd64 
(2.0.16-1, automatic), libsvtav1enc1:amd64 (1.4.1+dfsg-1, automatic), 
php8.2-mbstring:amd64 (8.2.7-1~deb12u1, automatic), php8.2-curl:amd64 
(8.2.7-1~deb12u1, automatic), liblerc4:amd64 (4.0.0+ds-2, automatic), 
php8.2-opcache:amd64 (8.2.7-1~deb12u1, automatic), php8.2-imap:amd64 
(8.2.7-1~deb12u1, automatic), libgav1-1:amd64 (0.18.0-1+b1, automatic), 
php8.2-readline:amd64 (8.2.7-1~deb12u1, automatic), php8.2-odbc:amd64 
(8.2.7-1~deb12u1, automatic), php8.2-igbinary:amd64 (3.2.13-1, automatic), 
php8.2-redis:amd64 (5.3.7+4.3.0-3, automatic), libyuv0:amd64 
(0.0~git20230123.b2528b0-1, automatic), libwebp7:amd64 (1.2.4-0.2, automatic), 
libabsl20220623:amd64 (20220623.1-1, automatic), libavif15:amd64 (0.11.1-1, 
automatic), php8.2-gd:amd64 (8.2.7-1~deb12u1, automatic), php8.2-sqlite3:amd64 
(8.2.7-1~deb12u1, automatic), php8.2-bz2:amd64 (8.2.7-1~deb12u1, automatic), 
php8.2-cli:amd64 (8.2.7-1~deb12u1, automatic), php8.2-fpm:amd64 
(8.2.7-1~deb12u1, automatic), php8.2-common:amd64 (8.2.7-1~deb12u1, automatic), 
libde265-0:amd64 (1.0.11-1, automatic), libodbccr2:amd64 (2.3.11-2, automatic), 
librav1e0:amd64 (0.5.1-6, automatic), php8.2-xml:amd64 (8.2.7-1~deb12u1, 
automatic), php8.2-zip:amd64 (8.2.7-1~deb12u1, automatic)
Upgrade: libltdl7:amd64 (2.4.6-15, 2.4.7-5), php-redis:amd64 
(5.3.2+4.3.0-2+deb11u1, 5.3.7+4.3.0-3), php:amd64 (2:7.4+76, 2:8.2+93), 
libodbc1:amd64 (2.3.6-0.1+b1, 2.3.11-2), php-gd:amd64 (2:7.4+76, 2:8.2+93), 
php-common:amd64 (2:76, 2:93), php-soap:amd64 (2:7.4+76, 2:8.2+93), 
php-curl:amd64 (2:7.4+76, 2:8.2+93), php-readline:amd64 (2:7.4+76, 2:8.2+93), 
php-igbinary:amd64 (3.2.1+2.0.8-2, 3.2.13-1), php-imap:amd64 (2:7.4+76, 
2:8.2+93), php-odbc:amd64 (2:7.4+76, 2:8.2+93), php-mbstring:amd64 (2:7.4+76, 
2:8.2+93), php-bz2:amd64 (2:7.4+76, 2:8.2+93), php-cli:amd64 (2:7.4+76, 
2:8.2+93), php-fpm:amd64 (2:7.4+76, 2:8.2+93), php-mysql:amd64 (2:7.4+76, 
2:8.2+93), php-xml:amd64 (2:7.4+76, 2:8.2+93), php-json:amd64 (2:7.4+76, 
2:8.2+93), php-zip:amd64 (2:7.4+76, 2:8.2+93), libgd3:amd64 (2.3.0-2, 2.3.3-9), 
php-sqlite3:amd64 (2:7.4+76, 2:8.2+93)
Remove: php7.4-soap:amd64 (7.4.33-1+deb11u4), php7.4-mbstring:amd64 
(7.4.33-1+deb11u4), php7.4-readline:amd64 (7.4.33-1+deb11u4), php7.4-gd:amd64 
(7.4.33-1+deb11u4), php7.4-curl:amd64 (7.4.33-1+deb11u4), php7.4-imap:amd64 
(7.4.33-1+deb11u4), php7.4-odbc:amd64 (7.4.33-1+deb11u4), php7.4-opcache:amd64 
(7.4.33-1+deb11u4), php7.4:amd64 (7.4.33-1+deb11u4), php7.4-bz2:amd64 
(7.4.33-1+deb11u4), php7.4-cli:amd64 (7.4.33-1+deb11u4), php7.4-mysql:amd64 
(7.4.33-1+deb11u4), php7.4-fpm:amd64 (7.4.33-1+deb11u4), php7.4-json:amd64 
(7.4.33-1+deb11u4), php7.4-xml:amd64 (7.4.33-1+deb11u4), php7.4-zip:amd64 
(7.4.33-1+deb11u4), php7.4-sqlite3:amd64 (7.4.33-1+deb11u4), 
php7.4-common:amd64 (7.4.33-1+deb11u4)
End-Date: 2023-06-18  23:25:00

After editing the various .ini and .conf files in /etc/php/8.2 for wordpress's
various needs, the site was using php8.2-fpm, but wordpress was broken and the
logs were filled with:

2023/06/18 23:25:02 [error] 16059#16059: *3330 FastCGI sent in stderr: ":  
preg_match(): Compilation failed: unrecognised compile-time option bit(s) at 
offset 0 in 
/srv/theurbanist.org/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php
 on line 1358; PHP message: PHP Warning:  preg_match(): Compilation failed: 
unrecognised compile-time option bit(s) at offset 0 in 
/srv/theurbanist.org/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/rules.php
 on line 773; PHP message: PHP Warning:  preg_match(): Compilation failed: 
unrecognised compile-time option bit(s) at offset 0 in 
/srv/theurbanist.org/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php
 on line 1506; PHP message: PHP Warning:  preg_match(): Compilation failed: 
unrecognised compile-time option bit(s) at offset 0 in 
/srv/theurbanist.org/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php
 on line 1358; PHP message: 

Bug#1038648: Xspice crashes on start

[Frank Heckenbach]

Package: xserver-xspice
Version: 0.1.5+git20200331-3
Severity: grave
Justification: renders package unusable

Since upgrading to bookworm, Xspice always crashes when I try to
start it:

Xspice --config xspice.1.conf :25

(EE) Caught signal 6 (Aborted). Server aborting

Full log: xspice.1.log

https://gitlab.freedesktop.org/xorg/driver/xf86-video-qxl/-/issues/14
describes a similar problem and suggest to add some options in the
config file. When I do this, I get a segfault instead:

Xspice --config xspice.2.conf :25

(EE) Caught signal 11 (Segmentation fault). Server aborting

Full log: xspice.2.log

The page above mentions this too and refers to
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-qxl/+bug/1967719

That report was closed since they were "confident it was fixed in
https://launchpad.net/ubuntu/+source/xserver-xorg-video-qxl/0.1.5+git20200331-3;.
However, the same version seems to be in bookworm (unless Debian
made its own changes to it), and the problem does occur.

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

Kernel: Linux 6.1.0-9-amd64 (SMP w/24 CPU threads; PREEMPT)
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xserver-xspice depends on:
ii  libc6  2.36-9
ii  libspice-server1   0.15.1-1
ii  libxfont2  1:2.0.6-1
ii  python33.11.2-1+b1
ii  xserver-xorg   1:7.7+23
ii  xserver-xorg-core [xorg-video-abi-25]  2:21.1.7-3

xserver-xspice recommends no packages.

xserver-xspice suggests no packages.

-- no debconf information


xspice.1.conf
Description: Binary data


xspice.1.log
Description: Binary data


xspice.2.conf
Description: Binary data


xspice.2.log
Description: Binary data

Bug#1038647: Sogo : Error at logon

[Joffrey]

Package: sogo
Version: 5.8.0-1Severity: important

Objet : Sogo error at logon

Paquet : sogo
Version : 5.8.0-1

Hi all,

I have upgrade my debian from Bullseye to Bookworm.

Now i have an error when i try to logon on sogo.

Versions :
sogo have been upgrade from 5.0.1-4 to 5.8.0-1
postgresql have been upgrade from v13 to v15.
php have been upgrade from 7.4 to 8.2

I have passed my question on the bug page project but with no serious response.

https://bugs.sogo.nu/view.php?id=5792


Today i run the bullseye version which is not really good thing.


The problem is the following.

Error log :

Jun 15 21:27:59 sogod [2397]: [ERROR] <0x0x5568f192b8f0[GCSSessionsFolder]> 
-[GCSSessionsFolder 
writeRecordForEntryWithID:value:creationDate:lastSeenDate:]: cannot write 
record:  NAME:PostgreSQL72FatalError 
REASON:fatal pgsql error (channel=<0x0x5568f1811b40[PostgreSQL72Channel]: 
connection=<0x0x5568f1770da0[PGConnection]:  connection=0x0x5568f17a3dd0>>): 
ERREUR:  valeur trop longue pour le type character varying(255)


Full log at logon :

Jun 15 21:27:59 sogod [2397]: |SOGo| starting method 'POST' on uri 
'/SOGo/connect'
Jun 15 21:27:59 sogod [2397]: |SOGo| traverse(acquire): SOGo => connect
Jun 15 21:27:59 sogod [2397]: |SOGo|   do traverse name: 'SOGo'
Jun 15 21:27:59 sogod [2397]: |SOGo|   do traverse name: 'connect'
Jun 15 21:27:59 sogod [2397]: |SOGo| set clientObject: 
2023-06-15 21:27:59.664 sogod[2397:2397] PG0x0x5568f1834420 SQL: SELECT 
c_password FROM sogo_users WHERE c_uid = 'MYUSE'
Jun 15 21:27:59 sogod [2397]: SOGoRootPage successful login from '127.0.0.1' 
for user 'MYUSE' - expire = -1  grace = -1
2023-06-15 21:27:59.667 sogod[2397:2397] PG0x0x5568f1834420 SQL: BEGIN 
TRANSACTION
2023-06-15 21:27:59.667 sogod[2397:2397] PG0x0x5568f1834420 SQL: SELECT 
t1.c_creationdate, t1.c_id, t1.c_lastseen, t1.c_value FROM  
sogo_sessions_folder t1 WHERE t1.c_id='Ih+0ExE6IXxvI4SP'
2023-06-15 21:27:59.667 sogod[2397:2397] PG0x0x5568f1834420 SQL: ROLLBACK 
TRANSACTION
2023-06-15 21:27:59.667 sogod[2397:2397] PG0x0x5568f1811b40 SQL: BEGIN 
TRANSACTION
2023-06-15 21:27:59.668 sogod[2397:2397] PG0x0x5568f1811b40 SQL: INSERT INTO 
sogo_sessions_folder (c_lastseen, c_creationdate, c_value, c_id) VALUES 
(1686857279, 1686857279, 
'6XyPpjOma6hzKi9D2zEKtaBCfq5HalKWnZwOWR/l6q9QwsWbTy1YzNbzg5RpDpbSKCM4OnyEcM2VnwE2QKQrxHqDD87XI1ZG+JkJ5dKeBmiZ/xN4aKbSQZ30XcUHu8z4jTcOKwfNjgufX9F/xAiqTgmQcEx7sZoVy9+uag3P8haYHnQJXk18giBrg3CrWskj7QKJjN0f7f0XINaiwPZMTOM1el+WwIP1e2sKBzE0A6Ght0luvaS5ykqWG4Qo+56tOrkw6/G4BP1Jt41ytVPV6dcy2rGxu5ilcDYsMhVvy4IUfEuCRebuJzg1yivBjx1WeJqhGai/DCzi8HXE8oTLG/NfpH2sGTeVEhYBSr5DPfNHHfzgePzGAJNp5KO6vyZ3n6/0JXrXktTZjE40hw6iygeK3DvLqpkvR5Aj/DYaE/Vj2sk0UAhvvMCiQ9sCfeu28eWZDhUuicq3ZnQlOkMTlS8YtB8UUeXAfM5sCzhG4CFRvG+TBLMNy7nGXb/ZjXFxqXHZ+LHcPVB/mHgX8pKE7PQogWQoYijlK+7inKt5fhnTZ8UKnLBl72h97HLrYu4Pwx5ZRZuqqoXfo34elUy8s/2uKteZfS76JbgaMoIoAks0ozc2WacJcS0gZ/jnNQeHlIwBAfCJ7ixTOak
..bKiocLsHDdUkPHhC9TFkWeqU86ObVzKQrkOPcpVq1RdSZwPAXkJh2dHGyI3SEoUPf8Kt8Y7D5IjdBgkxvvaMadP9uU+/Ki6DhS4Ut/VC5PQH0TdkHS0diwMdJmkeHD6rH7IFJmGFM5wZJBaJCiBMCedgDesqFj+wVsXv7QZOAGMqOpatZlRzc8bVTwZjkH2pOTEB7JGzY=',
 'Ih+0ExE6IXxvI4SP')
2023-06-15 21:27:59.668 sogod[2397:2397] PG0x0x5568f1811b40 SQL: ROLLBACK 
TRANSACTION
Jun 15 21:27:59 sogod [2397]: [ERROR] <0x0x5568f192b8f0[GCSSessionsFolder]> 
-[GCSSessionsFolder 
writeRecordForEntryWithID:value:creationDate:lastSeenDate:]: cannot write 
record:  NAME:PostgreSQL72FatalError 
REASON:fatal pgsql error (channel=<0x0x5568f1811b40[PostgreSQL72Channel]: 
connection=<0x0x5568f1770da0[PGConnection]:  connection=0x0x5568f17a3dd0>>): 
ERREUR:  valeur trop longue pour le type character varying(255)

Jun 15 21:27:59 sogod [2397]: |SOGo| request took 0.005227 seconds to execute
Jun 15 21:27:59 sogod [2397]: <0x0x5568f1898d50[WOResponse]> Zipping of 
response disabled
Jun 15 21:27:59 sogod [2397]: 127.0.0.1 "POST /SOGo/connect HTTP/1.1" 200 39/77 
0.006 - - 0 - 14
Jun 15 21:27:59 sogod [2397]: |SOGo| starting method 'POST' on uri 
'/SOGo/so/passwordRecoveryEnabled'
Jun 15 21:27:59 sogod [2397]: |SOGo| traverse(acquire): passwordRecoveryEnabled
Jun 15 21:27:59 sogod [2397]: |SOGo|   do traverse name: 
'passwordRecoveryEnabled'
Jun 15 21:27:59 sogod [2397]: |SOGo| request took 0.000506 seconds to execute
Jun 15 21:27:59 sogod [2397]: <0x0x5568f1762e70[WOResponse]> Zipping of 
response disabled
Jun 15 21:27:59 sogod [2397]: 127.0.0.1 "POST /SOGo/so/passwordRecoveryEnabled 
HTTP/1.1" 403 0/39 0.001 - - 0 - 14


Thank you a lot

Bug#1038646: pytest autopkg tests fail with setuptools from unstable

[Matthias Klose]

Package: src:pytest
Version: 7.3.2-1
Severity: serious
Tags: sid trixie

see
https://ci.debian.net/data/autopkgtest/testing/amd64/p/pytest/34610938/log.gz

at least two issues:

>   warnings.warn("pkg_resources is deprecated as an API", DeprecationWarning)
E   DeprecationWarning: pkg_resources is deprecated as an API

/usr/lib/python3/dist-packages/pkg_resources/__init__.py:121: DeprecationWarning

and


E   Failed: nomatch: 'test_hello.py::test_hello*PASSED*'
E   and: '= test session starts 
=='
E   and: 'platform linux -- Python 3.11.4, pytest-7.2.1, 
pluggy-1.0.0+repack -- /usr/bin/python3.11'

E   and: 'cachedir: .pytest_cache'
E   and: 'rootdir: 
/tmp/pytest-of-debci/pytest-0/test_cmdline_python_namespace_package0/world'

E   and: 'collecting ... collected 4 items'
E   and: ''
E   fnmatch: 'test_hello.py::test_hello*PASSED*'
E  with: 'test_hello.py::test_hello PASSED 
  [ 25%]'

E   fnmatch: 'test_hello.py::test_other*PASSED*'
E  with: 'test_hello.py::test_other PASSED 
  [ 50%]'

E   fnmatch: 'ns_pkg/world/test_world.py::test_world*PASSED*'
E  with: 'ns_pkg/world/test_world.py::test_world PASSED 
  [ 75%]'

E   fnmatch: 'ns_pkg/world/test_world.py::test_other*PASSED*'
E  with: 'ns_pkg/world/test_world.py::test_other PASSED 
  [100%]'

E   nomatch: '*4 passed in*'
E   and: ''
E   and: '=== warnings summary 
==='
E   and: 
'../../../../../usr/lib/python3/dist-packages/pkg_resources/__init__.py:121'
E   and: ' 
/usr/lib/python3/dist-packages/pkg_resources/__init__.py:121: 
DeprecationWarning: pkg_resources is deprecated as an API'
E   and: 'warnings.warn("pkg_resources is deprecated as an API", 
DeprecationWarning)'

E   and: ''
E   and: 
'../../../../../usr/lib/python3/dist-packages/pkg_resources/__init__.py:2870'
E   and: " 
/usr/lib/python3/dist-packages/pkg_resources/__init__.py:2870: 
DeprecationWarning: Deprecated call to `pkg_resources.declare_namespace('zope')`."
E   and: '  Implementing implicit namespace packages (as specified in 
PEP 420) is preferred to `pkg_resources.declare_namespace`. See 
https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages'

E   and: 'declare_namespace(pkg)'
E   and: ''
E   and: 'ns_pkg/__init__.py:1'
E   and: " 
/tmp/pytest-of-debci/pytest-0/test_cmdline_python_namespace_package0/world/ns_pkg/__init__.py:1: 
DeprecationWarning: Deprecated call to `pkg_resources.declare_namespace('ns_pkg')`."
E   and: '  Implementing implicit namespace packages (as specified in 
PEP 420) is preferred to `pkg_resources.declare_namespace`. See 
https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages'

E   and: "__import__('pkg_resources').declare_namespace(__name__)"
E   and: ''
E   and: '-- Docs: 
https://docs.pytest.org/en/stable/how-to/capture-warnings.html'
E   and: ' 4 passed, 3 warnings in 0.06s 
='

E   remains unmatched: '*4 passed in*'

/tmp/autopkgtest-lxc.sat21qx2/downtmp/build.Tna/src/testing/acceptance_test.py:699: 
Failed

- Captured stdout call -

Bug#992976: uscan: mode=git refs/heads/ instruction scans for tags instead, and fails

[Fab Stz]

Hello,

I'm facing this too.

```d/watch
version=4
options=uversionmangle=s/-?([^\d.]+)/~$1/;tr/A-Z/a-z/,\
mode=git,gitmode=full,gitexport=all \
https://github.com/bcit-ci/CodeIgniter \
heads/master
```

Upstream's main branch is "develop". uscan takes this one instead of the 
requested "master" branch

```$ uscan --debug --safe
uscan info: uscan (version 2.23.4) See uscan(1) for help
uscan info: Scan watch files in .
uscan debug: Found ./debian
uscan info: Check debian/watch and debian/changelog in .
uscan info: package="php-codeigniter-framework" 
version="0.0~git20230407.63d037565-1" (as seen in debian/changelog)
uscan info: package="php-codeigniter-framework" 
version="0.0~git20230407.63d037565" (no epoch/revision)
uscan info: ./debian/changelog sets package="php-codeigniter-framework" 
version="0.0~git20230407.63d037565"
uscan info: Process watch file at: debian/watch
package = php-codeigniter-framework
version = 0.0~git20230407.63d037565
pkg_dir = .
uscan debug: parse line options=uversionmangle=s/-?([^\d.]+)/~$1/;tr/A-Z/a-
z/,mode=git,gitmode=full,gitexport=all https://github.com/bcit-ci/CodeIgniter 
heads/master
uscan info: opts: uversionmangle=s/-?([^\d.]+)/~$1/;tr/A-Z/a-
z/,mode=git,gitmode=full,gitexport=all
uscan info: line: https://github.com/bcit-ci/CodeIgniter heads/master
uscan info: Parsing uversionmangle=s/-?([^\d.]+)/~$1/;tr/A-Z/a-z/
uscan info: Parsing mode=git
uscan info: Parsing gitmode=full
uscan info: Parsing gitexport=all
uscan info: line: https://github.com/bcit-ci/CodeIgniter heads/master
uscan debug: $self->{'pgpmode'}=default, $self->{'pgpsigurlmangle'}=undef
uscan info: Last orig.tar.* tarball version (from debian/changelog): 
0.0~git20230407.63d037565
uscan info: Last orig.tar.* tarball version (dversionmangled): 
0.0~git20230407.63d037565
uscan debug: watch file has:
$base= https://github.com/bcit-ci/CodeIgniter
$filepattern = heads/master
$lastversion = 0.0~git20230407.63d037565
$action  = 
mode = git
pgpmode  = default
versionmode  = newer
$site= https://github.com/bcit-ci/CodeIgniter
$basedir = 
uscan debug: line: search()
uscan debug: Execute: git clone --quiet --bare https://github.com/bcit-ci/
CodeIgniter ../php-codeigniter-framework-temporary.2454317.git...
uscan info: Looking at $base = https://github.com/bcit-ci/CodeIgniter with
$filepattern = heads/master found
$newfile = heads/master
$newversion  = 0.0~git20230407.63d037565
$lastversion = 0.0~git20230407.63d037565
uscan debug: line: get_upstream_url()
uscan info: Upstream URL(+tag) to download is identified ashttps://
github.com/bcit-ci/CodeIgniter heads/master
uscan debug: line: get_newfile_base()
uscan info: Filename (filenamemangled) for downloaded file: php-codeigniter-
framework-0.0~git20230407.63d037565.tar.xz
uscan debug: line: cmp_versions()
uscan info: Newest version of php-codeigniter-framework on remote site is 
0.0~git20230407.63d037565, local version is 0.0~git20230407.63d037565
uscan info:  => Package is up to date from:
 => https://github.com/bcit-ci/CodeIgniter heads/master
uscan debug: line: download_file_and_sig()
uscan debug: line: mkorigtargz()
uscan debug: Keep git repo (../php-codeigniter-framework-temporary.
2454317.git)
uscan info: Scan finished
```

Maybe the problem has something to do with this command?
Execute: git clone --quiet --bare https://github.com/bcit-ci/CodeIgniter ../
php-codeigniter-framework-temporary.2454317.git...

Regards
Fab

On Wed, 25 Aug 2021 22:15:42 +0200 Romain Porte  wrote:
> Package: devscripts
> Version: 2.21.3
> Severity: important
> X-Debbugs-Cc: deb...@microjoe.org
> 
> Dear Maintainer,
> 
> While trying to use uscan to scan for upstream commits on a specific
> branch instead of the default on, I tried to use refs/heads/ as
> explained in the uscan man page.
> 
> Here is the content of the d/watch file I am using:
> 
> version=4
> opts="mode=git, gitmode=full, pgpmode=none, pretty=8.994+git%cd.%h, 
repack, compression=xz" \
> https://bitbucket.org/jpcgt/flatcam.git \
> refs/heads/Beta
> 
> However when running uscan, the invocation fails with the following
> message:
> 
> uscan info: uscan (version 2.21.3) See uscan(1) for help
> uscan info: Scan watch files in .
> uscan info: Check debian/watch and debian/changelog in .
> uscan info: package="flatcam" version="8.994+ds-1" (as seen in debian/
changelog)
> uscan info: package="flatcam" version="8.994+ds" (no epoch/revision)
> uscan info: ./debian/changelog sets package="flatcam" version="8.994+ds"
> uscan info: Process watch file at: debian/watch
> package = flatcam
> version = 8.994+ds
> pkg_dir = .
> uscan info: opts: mode=git, gitmode=full, pgpmode=none, 
pretty=8.994+git%cd.%h, repack, compression=xz
> uscan info: line: https://bitbucket.org/jpcgt/flatcam.git refs/heads/
Beta
> uscan info: Parsing 

Bug#1038644: the missing patch

[Yury Shevchuk]

The patch attached with 'a' command in reportbug didn't seem to made it
to bugs.debian.org... here it is.

--- src/nfcapd/nfcapd.c~2022-12-24 15:30:59.0 +0300
+++ src/nfcapd/nfcapd.c 2023-06-17 22:45:08.759990742 +0300
@@ -605,7 +605,7 @@
 metricSocket = NULL;
 metricInterval = 60;
 
-while ((c = getopt(argc, argv, 
"46B:b:C:DeEf:g:hI:i:jJ:l:m:M:n:p:P:rRs:S:t:T:u:vVw:x:yzZ")) != EOF) {
+while ((c = getopt(argc, argv, 
"46B:b:C:DeEf:g:hI:i:jJ:l:m:M:n:p:P:rR:s:S:t:T:u:vVw:x:yzZ")) != EOF) {
 switch (c) {
 case 'h':
 usage(argv[0]);

Bug#1038453: Anyone interested in aeskulap DICOM viewer (Was: Bug#1038453: aeskulap: Is this package still desirable to have in Debian?)

[Andreas Tille]

Hi,

aeskulap is dead upstream for a long time Alexander Pipelka (in CC)
maintained a Github repository to enable maintaining the code but the
last commit was a Debian patch.  So it seems we will not see any
relevant upstream work in the foreseable future.

Since the package is blocking removal of some GTK+ 2 libraries its
probably tine to say goodbye to this package in Debian.  If nobody
will volunteer to do the porting work described below I'll ask for
removal in about two weeks.

Kind regards
 Andreas.

Am Sun, Jun 18, 2023 at 04:34:39PM +0100 schrieb Simon McVittie:
> Source: aeskulap
> Severity: normal
> Tags: trixie sid
> 
> I stumbled across aeskulap while checking which packages still depend on
> various GNOME-2-era (pre-2012) libraries.
> 
> According to its linked upstream website
> , aeskulap is a viewer for DICOM images,
> used in medical imaging. Its most recent release seems to have been in
> March 2006, and the version in Debian is a git snapshot from 2019 (which
> seems to be from some unoffical fork, I can't find any indication on
> Savannah that the nongnu.org version has a git repo).
> 
> Is this package still useful?
> 
> Is it still maintained upstream by someone? If the Debian package is
> tracking a maintained fork rather than the original upstream maintainers'
> version, then updating the Homepage field to point to that fork would
> be useful for people doing QA.
> 
> Thanks,
> smcv
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging
> 

-- 
http://fam-tille.de

Bug#1038645: haskell-tldr FTBFS: dh_installman: error: Cannot find (any matches for) "tldr-hs.1"

[Adrian Bunk]

Source: haskell-tldr
Version: 0.9.2-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=haskell-tldr=0.9.2-3

...
dh_installexamples -ptldr-hs 
dh_installman -ptldr-hs 
dh_installman: error: Cannot find (any matches for) "tldr-hs.1" (tried in .)

dh_installman: error: Aborting due to earlier error
make: *** [/usr/share/cdbs/1/rules/debhelper.mk:238: binary-install/tldr-hs] 
Error 25

Bug#755434: Echoing desire for exfat support

[Alexander Huemer]

The last update to this bug was made 3 (!) years ago.
Can we please finally have exfat support for pmount.