Bug#1067728: FTBFS: error: parsing package 'genomethreader' Built-Using field: vmatch (= )

[Andrey Rakhmatullin]

Source: genomethreader
Version: 1.7.3+dfsg-10
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=genomethreader=amd64=1.7.3%2Bdfsg-10%2Bb1=1711431231=0

dh_gencontrol
dpkg-gencontrol: warning: Depends field of package genomethreader: substitution
variable ${shlibs:Depends} used, but is not defined
dpkg-gencontrol: warning: Depends field of package genomethreader: substitution
variable ${misc:Depends} used, but is not defined
dpkg-gencontrol: warning: Built-Using field of package genomethreader:
substitution variable ${libvmatch-dev:Version} used, but is not defined
dpkg-gencontrol: warning: can't parse dependency vmatch (= )
dpkg-gencontrol: error: parsing package 'genomethreader' Built-Using field:
vmatch (= )
dh_gencontrol: error: dpkg-gencontrol -pgenomethreader -ldebian/changelog
-T/dev/null -Pdebian/.debhelper/genomethreader/dbgsym-root -UPre-Depends
-URecommends -USuggests -UEnhances -UProvides -UEssential -UConflicts
-DPriority=optional -UHomepage -UImportant -DAuto-Built-Package=debug-symbols
-UProtected -UBuilt-Using -UStatic-Built-Using -DPackage=genomethreader-dbgsym
"-DDepends=genomethreader (= \${binary:Version})" "-DDescription=debug symbols
for genomethreader" "-DBuild-Ids=2ee4c1bcccdbf8190fc6a4036987ac7f75960587
36abd29d64d350f0ef96705f25bfa944a35a2fa7
3f55917f3ab74482ed8a375c362046bfc5f67e47
43ff84a1a4d05e8263cef0da4e3302c502d52b5f
71af6ff5a8f1698bb121f4a97b56e2316d048a17
8a4d456df97d2b6b232fc20fade9b8c85f8bb67c
bc0a580e6ab4e5fc76d11779e5e78666b026aefe
c75088642ea8314303d7665a3e35225cabe73924
ce619c3962a58899a584b8c8a9c5507bd27cd413
e0f4b2eb01ea5f3c4ecc7cda63c2aa7c2083f6b6
efcf85d767b296dd800c886d6b0adf4ea92b0eed
fd16d48d798ddc22f38d24450abba10f52695396" -DSection=debug -UMulti-Arch
-UReplaces -UBreaks returned exit code 25
dh_gencontrol: error: Aborting due to earlier error


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

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

Bug#1067349: closed by Dima Kogan (Done)

[Andrey Rakhmatullin]

On Fri, Mar 22, 2024 at 07:03:09PM +, Debian Bug Tracking System wrote:
> This FTBFS issue has been fixed. See the discussion here:
> 
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067398
> 
> The fixes are in python3-numpy=1:1.26.4+ds-6 and mrbuild=1.9
It just failed again, and it used python3-numpy=1:1.26.4+ds-6 and
mrbuild=1.9-1:
https://buildd.debian.org/status/fetch.php?pkg=gl-image-display=amd64=0.17-1%2Bb2=1711428859=0


-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#1067727: RFS: tcpslice/1.7-1 -- extract pieces of and/or glue together tcpdump files

[Bruno Naibert]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name : tcpslice
   Version  : 1.7-1
   Upstream contact : https://github.com/the-tcpdump-group/tcpslice/issues
 * URL  : https://www.tcpdump.org
 * License  : BSD-3-Clause, BSD-2-Clause, BSD-4-Clause
 * Vcs  : https://salsa.debian.org/debian/tcpslice
   Section  : net

The source builds the following binary packages:

  tcpslice - extract pieces of and/or glue together tcpdump files

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/t/tcpslice/tcpslice_1.7-1.dsc

Changes since the last upload:

 tcpslice (1.7-1) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Use secure URI in Homepage field.
 .
   [ Bruno Naibert de Campos ]
   * New upstream version 1.7.
   * Update standards version to 4.6.2.
   * debian/copyright: updated the packaging and upstream copyright years.
   * debian/upstream/signing-key.asc: updated with key from The Tcpdump Group.

Regards,
-- 
  Bruno Naibert de Campos

Bug#1067726: python3-rdflib: extras/external_graph_libs.py: SyntaxWarning: invalid escape sequence '\*'

[Paul Wise]

Package: python3-rdflib
Version: 6.1.1-4
Severity: normal
Usertags: warnings
User: debian-pyt...@lists.debian.org
Usertags: python3.12

When upgrading python3-rdflib I got some warnings,
probably these are caused by the Python 3.12 transition.

   Preparing to unpack .../python3-rdflib_6.1.1-4_all.deb ...
   Unpacking python3-rdflib (6.1.1-4) over (6.1.1-3) ...
   Setting up python3-rdflib (6.1.1-4) ...
   /usr/lib/python3/dist-packages/rdflib/extras/external_graph_libs.py:75: 
SyntaxWarning: invalid escape sequence '\*'
 """Converts the given graph into a networkx.MultiDiGraph.
   /usr/lib/python3/dist-packages/rdflib/extras/external_graph_libs.py:132: 
SyntaxWarning: invalid escape sequence '\*'
 """Converts the given graph into a networkx.DiGraph.
   /usr/lib/python3/dist-packages/rdflib/extras/external_graph_libs.py:195: 
SyntaxWarning: invalid escape sequence '\*'
 """Converts the given graph into a networkx.Graph.

-- 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'), 
(500, 'stable-updates'), (500, 'stable-security-debug'), (500, 
'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), 
(500, 'proposed-updates'), (500, 'buildd-proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (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 python3-rdflib depends on:
ii  python3 [python3-supported-min]  3.11.6-1
ii  python3-importlib-metadata   4.12.0-1
ii  python3-isodate  0.6.1-2
ii  python3-pkg-resources68.1.2-2
ii  python3-pyparsing3.1.1-1

Versions of packages python3-rdflib recommends:
ii  python3-html5lib   1.1-6
pn  python3-sparqlwrapper  

Versions of packages python3-rdflib suggests:
pn  python-rdflib-doc  

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1067715: calibre: doesn't install DeACSM plugin

[yokota]

Hello, José.

I'm not maintain external plugins.
So I can't fix plugin codes.

But this bug might fix when you installs Debian
python3-oscrypto/1.3.0-1+deb12u1 package.
https://tracker.debian.org/pkg/oscrypto

DeACSM plugin seems to load properly on my Debian Calibre 7.7.0.


Here is my technical analysis about this issue.

1. This line shows Python oscrypto code fails to detect OpenSSL version.
> raise LibraryNotFoundError('Error detecting the version of libcrypto')
> oscrypto.errors.LibraryNotFoundError: Error detecting the version of libcrypto
   DeACSM plugin includes Python oscrypto module, and use it when required.

2. Current upstream oscrypto release code has some bugs about OpenSSL
version detection.
   OpenSSL has MAJOR.MINOR.PATCHLEVEL version scheme and each section
has 1 or more
   digits.
   But oscrypto code can only accepts 1 digit for each section. And it
fails to detect version numbers.
   Current Debian OpenSSL version in Debian stable is 3.0.11, and it
has 2 degits in PATCHLEVEL.

3. This bug was fixed in oscrypto upstream development codes, but not
in release codes.
   https://github.com/wbond/oscrypto/pull/76

4. This bug was also fixed in Debian bug 1055598. And released as
python3-oscrypto/1.3.0-1+deb12u1.
Use Debian oscrypto module instead of included oscrypto module
might fix the bug.
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055598

5. If it went wrong, fix manually oscrypto code in plugin code. The
oscrypto code is Zip-ed as oscrypto.zip
See previous GitHub pull request for fix.
   https://github.com/wbond/oscrypto/pull/76

--
YOKOTA

Bug#1067725: lintian: lintian should consider warning when one of many signing keys is missing

[Xiyue Deng]

Xiyue Deng  writes:

> Package: lintian
> Version: 2.116.3
> Severity: wishlist
> X-Debbugs-Cc: none, Xiyue Deng 
>
> We encountered a case that persist[1] from elpa has more than signing
> keys and one of the public keys is missing.  As the output of `gbp
> import-orig --uscan' shows[2], the EDDSA public key could not be found.
> Instead, the RSA was available in the repo[3] and passed the signature
> check.  So instead I used the `uscan --skip-signature' to get the
> upstream tarball and prepared the packaging.  Paul Wise asked me to
> check whether lintian would still warning about the missing key in the
> built package, and it didn't.
>
> This might be considered a rather rare case with multiple signing keys,
> and Paul suggested to file a bug against lintian nonetheless to keep a
> record on this case.
>
> [1] https://elpa.gnu.org/packages/persist.html
>
> [2] Command output:
> ,
> | $ gbp import-orig --uscan
> | gbp:info: Launching uscan...
> | Newest version of persist-el on remote site is 0.6, local version is 0.5
> |(mangled local version is 0.5)
> |  => Newer package available from:
> | => https://elpa.gnu.org/packages/persist-0.6.tar
> | gpgv: Signature made Sat 13 Jan 2024 02:05:03 AM PST
> | gpgv:using RSA key C433554766D3DDC64221BFAA066DAFCB81E42C40
> | gpgv: Good signature from "GNU ELPA Signing Agent (2019) 
> "
> | gpgv: Signature made Sat 13 Jan 2024 02:05:03 AM PST
> | gpgv:using EDDSA key 
> 0327BE68D64D9A1A66859F15645357D2883A0966
> | gpgv: Can't check signature: No public key
> | uscan die: OpenPGP signature did not verify. at 
> /usr/share/perl5/Devscripts/Uscan/Output.pm line 77.
> | gbp:error: Uscan failed: OpenPGP signature did not verify.
> `
>
> [3] 
> https://salsa.debian.org/emacsen-team/persist-el/-/blob/master/debian/upstream/signing-key.asc?ref_type=heads
>
> [..snip..]

CCing Paul which I forgot to do so in the first email.  Also Paul suggested
a new lintian tag for this use case:
"upstream-signature-uses-key-missing-from-upstream-signing-keys".

-- 
Xiyue Deng

Bug#1067725: lintian: lintian should consider warning when one of many signing keys is missing

[Xiyue Deng]

Package: lintian
Version: 2.116.3
Severity: wishlist
X-Debbugs-Cc: none, Xiyue Deng 

We encountered a case that persist[1] from elpa has more than signing
keys and one of the public keys is missing.  As the output of `gbp
import-orig --uscan' shows[2], the EDDSA public key could not be found.
Instead, the RSA was available in the repo[3] and passed the signature
check.  So instead I used the `uscan --skip-signature' to get the
upstream tarball and prepared the packaging.  Paul Wise asked me to
check whether lintian would still warning about the missing key in the
built package, and it didn't.

This might be considered a rather rare case with multiple signing keys,
and Paul suggested to file a bug against lintian nonetheless to keep a
record on this case.

[1] https://elpa.gnu.org/packages/persist.html

[2] Command output:
,
| $ gbp import-orig --uscan
| gbp:info: Launching uscan...
| Newest version of persist-el on remote site is 0.6, local version is 0.5
|(mangled local version is 0.5)
|  => Newer package available from:
| => https://elpa.gnu.org/packages/persist-0.6.tar
| gpgv: Signature made Sat 13 Jan 2024 02:05:03 AM PST
| gpgv:using RSA key C433554766D3DDC64221BFAA066DAFCB81E42C40
| gpgv: Good signature from "GNU ELPA Signing Agent (2019) 
"
| gpgv: Signature made Sat 13 Jan 2024 02:05:03 AM PST
| gpgv:using EDDSA key 0327BE68D64D9A1A66859F15645357D2883A0966
| gpgv: Can't check signature: No public key
| uscan die: OpenPGP signature did not verify. at 
/usr/share/perl5/Devscripts/Uscan/Output.pm line 77.
| gbp:error: Uscan failed: OpenPGP signature did not verify.
`

[3] 
https://salsa.debian.org/emacsen-team/persist-el/-/blob/master/debian/upstream/signing-key.asc?ref_type=heads

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

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

Versions of packages lintian depends on:
ii  binutils2.40-2
ii  bzip2   1.0.8-5+b1
ii  diffstat1.65-1
ii  dpkg1.21.22
ii  dpkg-dev1.21.22
ii  file1:5.44-3
ii  gettext 0.21-12
ii  gpg 2.2.40-1.1
ii  intltool-debian 0.35.0+20060710.6
ii  iso-codes   4.15.0-1
ii  libapt-pkg-perl 0.1.40+b2
ii  libarchive-zip-perl 1.68-1
ii  libberkeleydb-perl  0.64-2+b1
ii  libcapture-tiny-perl0.48-2
ii  libclass-xsaccessor-perl1.19-4+b1
ii  libclone-perl   0.46-1
ii  libconfig-tiny-perl 2.28-2
ii  libconst-fast-perl  0.014-2
ii  libcpanel-json-xs-perl  4.35-1
ii  libdata-dpath-perl  0.58-2
ii  libdata-validate-domain-perl0.10-1.1
ii  libdata-validate-uri-perl   0.07-2
ii  libdevel-size-perl  0.83-2+b1
pn  libdigest-sha-perl  
ii  libdpkg-perl1.21.22
ii  libemail-address-xs-perl1.05-1+b1
ii  libencode-perl  3.19-1+b1
ii  libfile-basedir-perl0.09-2
ii  libfile-find-rule-perl  0.34-3
ii  libfont-ttf-perl1.06-2
ii  libhtml-html5-entities-perl 0.004-3
ii  libhtml-tokeparser-simple-perl  3.16-4
ii  libio-interactive-perl  1.023-2
ii  libipc-run3-perl0.048-3
ii  libjson-maybexs-perl1.004004-1
ii  liblist-compare-perl0.55-2
ii  liblist-someutils-perl  0.59-1
ii  liblist-utilsby-perl0.12-2
ii  libmldbm-perl   2.05-4
ii  libmoo-perl 2.005005-1
ii  libmoox-aliases-perl0.001006-2
ii  libnamespace-clean-perl 0.27-2
ii  libpath-tiny-perl   0.144-1
ii  libperlio-gzip-perl 0.20-1+b1
ii  libperlio-utf8-strict-perl  0.010-1
ii  libproc-processtable-perl   0.634-1+b2
ii  libregexp-wildcards-perl1.05-3
ii  libsereal-decoder-perl  5.003+ds-1
ii  libsereal-encoder-perl  5.003+ds-1
ii  libsort-versions-perl   1.62-3
ii  libsyntax-keyword-try-perl  0.28-1
ii  libterm-readkey-perl2.38-2+b1
ii  libtext-levenshteinxs-perl  0.03-5+b1
ii  libtext-markdown-discount-perl  0.16-1
ii  libtext-xslate-perl 3.5.9-1+b2
ii  libtime-duration-perl   1.21-2
ii  libtime-moment-perl 0.44-2+b1
ii  libtimedate-perl2.3300-2
ii  libunicode-utf8-perl0.62-2
ii  liburi-perl 5.17-1
ii  libwww-mechanize-perl   2.16-1
ii  libwww-perl 

Bug#1067724: libopenvr-dev: Please upgrade opevr to version 2

[Safir Secerovic]

Package: libopenvr-dev
Version: 1.23.7~ds1-2.1
Severity: serious
Tags: upstream
Justification: Release Critical Issues for trixie
X-Debbugs-Cc: andre...@debian.org, lubosz.sarne...@collabora.com, 
christoph.h...@collabora.com

Dear opevr sdk maintainers,

Please consider upgrading openvr sdk to version 2.
It has been released last year and now my package, gamescope has switched to 
using it.
As a maintainer of gamescope, which has recently switched to openvr sdk version 
2
this is the way forward.

I also see that some of you are upstream author of the second package that 
depends on openvr sdk: 
libopenxr-loader1
I hope it would be possible for you to move wrapper to openvr sdk 2 as well.

Thank You,
Safir 


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

Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.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 libopenvr-dev depends on:
ii  libopenvr-api1t64  1.23.7~ds1-2.1

libopenvr-dev recommends no packages.

libopenvr-dev suggests no packages.

-- no debconf information

Bug#1067720: Don't hard-code the python version in d/control

[Michael Ablassmeier]

hi again,

On Tue, Mar 26, 2024 at 02:31:41AM +0100, Michael Ablassmeier wrote:
> On Mon, Mar 25, 2024 at 11:28:33PM +0100, Matthias Klose wrote:
> > Don't hard-code the python version in d/control, it will fail with 3.12
> > 
> > patch at
> > http://launchpadlibrarian.net/721153415/virtnbdbackup_2.0-1build1_2.0-1ubuntu1.diff.gz
> 
> thanks, but not hardcoding the python version makes build fail in dh_auto_test
> for me (using git-builpackage and debspawn as builder). For some reason yet
> unclear to me dh_auto_test attempts to run some made up testcases ..

dh_auto_test fails to test the module load because it seems python3-libnbd
required for virtnbdbackup is only available for python 3.11 yet:

 Package: python3-libnbd
 Depends: python3 (<< 3.12), python3 (>= 3.11~)

 > root@radiohead-unstable-buildd-amd64-la1a:/srv# python3.12
 > Python 3.12.2 (main, Mar 24 2024, 15:58:54) [GCC 13.2.0] on linux
 > Type "help", "copyright", "credits" or "license" for more information.
 > >>> import nbd
 > Traceback (most recent call last):
 >   File "", line 1, in 
 >   File "/usr/lib/python3/dist-packages/nbd.py", line 34, in 
 > import libnbdmod
 > ModuleNotFoundError: No module named 'libnbdmod'
 > 

bye,
- michael

Bug#1067720: Don't hard-code the python version in d/control

[Michael Ablassmeier]

hi,

On Mon, Mar 25, 2024 at 11:28:33PM +0100, Matthias Klose wrote:
> Don't hard-code the python version in d/control, it will fail with 3.12
> 
> patch at
> http://launchpadlibrarian.net/721153415/virtnbdbackup_2.0-1build1_2.0-1ubuntu1.diff.gz

thanks, but not hardcoding the python version makes build fail in dh_auto_test
for me (using git-builpackage and debspawn as builder). For some reason yet
unclear to me dh_auto_test attempts to run some made up testcases ..

before:

 >dh_auto_test -O--buildsystem=pybuild
 > I: pybuild base:305: cd 
 > /srv/build/virtnbdbackup-2.4/.pybuild/cpython3_3.11_virtnbdbackup/build; 
 > python3.11 -m unittest discover -v 
 > 
 > --
 > Ran 0 tests in 0.000s

with change:

 > dh_auto_test -O--buildsystem=pybuild
 > I: pybuild base:305: cd 
 > /srv/build/virtnbdbackup-2.4/.pybuild/cpython3_3.12_virtnbdbackup/build; 
 > python3.12 -m unittest discover -v 
 > libvirtnbdbackup.extenthandler 
 > (unittest.loader._FailedTest.libvirtnbdbackup.extenthandler) ... ERROR
 > libvirtnbdbackup.nbdcli 
 > (unittest.loader._FailedTest.libvirtnbdbackup.nbdcli) ... ERROR
 > 
 > ==
 > ERROR: libvirtnbdbackup.extenthandler 
 > (unittest.loader._FailedTest.libvirtnbdbackup.extenthandler)
 > --
 > ImportError: Failed to import test module: libvirtnbdbackup.extenthandler
 > Traceback (most recent call last):
 >   File "/usr/lib/python3.12/unittest/loader.py", line 427, in _find_test_path
 > package = self._get_module_from_name(name)
 >   
 >   File "/usr/lib/python3.12/unittest/loader.py", line 337, in 
 > _get_module_from_name
 > __import__(name)
 >   File 
 > "/srv/build/virtnbdbackup-2.4/.pybuild/cpython3_3.12_virtnbdbackup/build/libvirtnbdbackup/extenthandler/__init__.py",
 >  line 21, in 
 > from .extenthandler import ExtentHandler
 >   File 
 > "/srv/build/virtnbdbackup-2.4/.pybuild/cpython3_3.12_virtnbdbackup/build/libvirtnbdbackup/extenthandler/extenthandler.py",
 >  line 19, in 
 > from nbd import CONTEXT_BASE_ALLOCATION
 >   File "/usr/lib/python3/dist-packages/nbd.py", line 34, in 
 > import libnbdmod
 > ModuleNotFoundError: No module named 'libnbdmod'

of course i could skip dh_auto_test but i still wonder what
happens here..

bye,
- michael

Bug#1067663: org-mode: Org mode 9.6.23 that fixes several critical

[Nicholas D Steeves]

fixed 1067663 org-mode/9.5.2+dfsh-5
found 1067663 org-mode/9.6.7+dfsg-1
thanks

9.5.2+dfsh-5 in stable/bookworm is an empty package that depends on the
org-mode bundled with stable/bookworm's Emacs, so I'm marking this CVE
as fixed there.  Elpa-org in stable/bookworm will be fixed by a security
upload of Emacs.

I'm skipping 9.6.6+dfsg-1~exp1, since it's not relevant anymore.

Bug#1067723: kraft: please drop extraneous python3-six dependency

[Alexandre Detiste]

Source: kraft
Version: 1.1-1
Severity: important

Dear Maintainer,

It seams "six" was used during the Py2->3 transition,
but it's not used anymore by "kraft".

May you please remove the leftover reference in d/control ?

Greetings,

Alexandre



tchet@brix /tmp/kraft $ grep six -r
debian/changelog:- replace the python-reportlab, python-six, and 
python-pypdf2 dependencies
debian/changelog:  with python3-reportlab, python3-six, and python3-pypdf2
debian/control: python3-six,
tchet@brix /tmp/kraft $

Bug#1067722: opensnitch: please remove extraneous dependency on python3-six

[Alexandre Detiste]

Source: opensnitch
Version: 1.5.8.1-1
Severity: normal


python3-six is an obsolete python2+3 transilition layer
that was once use by opensnitch.

Please remove the leftover reference from d/control.

Greetings



tchet@brix /tmp/opensnitch $ grep six -r
debian/control: python3-six,
tchet@brix /tmp/opensnitch $

Bug#1051496: mailgraph: does not support the new syslog format

[michael]

Debian 12 Bookworm

Package: mailgraph

Version: 1.14-21

Severity: grave

Justification: renders package unusable

 

I installed mailgraph from Debian Trixie testing hoping to get the fixes
mentioned in: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051496

 

However, it still fails to run correctly.

 

mailgraph -v shows:

WARNING: line not in syslog format:

For every log entry.

 

And graphs don't create.

 

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

Says it was resolved, but this is not correct.

 

I compared/contrasted the 1.14-20 vs 1.14-21 line by line and I only saw:

$text =~ /^(?:[\dA-F]+|[\dB-DF-HJ-NP-TV-Zb-df-hj-np-tv-z]+):

Changing to:

$text =~ /^[0-9A-Z]+:

In a number of places.

 

Any insight would be appreciated.

 

Thank you

 

Michael

Bug#1067721: RFS: emacs-corfu/1.2-1 [Team] -- Completion Overlay Region FUnction in Emacs

[Xiyue Deng]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "emacs-corfu":

 * Package name : emacs-corfu
   Version  : 1.2-1
   Upstream contact : Daniel Mendler 
 * URL  : https://github.com/minad/corfu/
 * License  : GPL-3+
 * Vcs  : https://salsa.debian.org/emacsen-team/emacs-corfu
   Section  : editors

The source builds the following binary packages:

  elpa-corfu - Completion Overlay Region FUnction in Emacs

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

  https://mentors.debian.net/package/emacs-corfu/

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

  dget -x 
https://mentors.debian.net/debian/pool/main/e/emacs-corfu/emacs-corfu_1.2-1.dsc

Changes since the last upload:

 emacs-corfu (1.2-1) unstable; urgency=medium
 .
   * Team upload
   * New upstream release
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository-Browse
   * Update standards version to 4.6.2, no changes needed
   * Update copyright year in d/copyright
   * Modernize d/watch with special substitute strings to be more robust
   * Add d/gbp.conf to match current packaging practice
   * Mark vendored patch as "Forwarded: not-needed"
   * Add lintian-overrides for org format changelog

Regards,
-- 
Xiyue Deng

Bug#1067663: org-mode: Org mode 9.6.23 that fixes several critical

[Nicholas D Steeves]

reopen 1067663
found org-mode/9.1.14+dfsg-3
found org-mode/9.1.14+dfsg-3+deb10u1
found org-mode/9.4.0+dfsg-1+deb11u1
found org-mode/9.5.2+dfsh-5
thanks

Updating the affected versions from:

  https://security-tracker.debian.org/tracker/CVE-2024-30202

and

  https://security-tracker.debian.org/tracker/CVE-2024-30205

Bug#1067709: FTBFS in armel/armhf: some symbols disappeared

[Peter Pentchev]

Control: tag -1 + confirmed

On Tue, Mar 26, 2024 at 01:29:08AM +0500, Andrey Rakhmatullin wrote:
> Source: dante
> Version: 1.4.3+dfsg-1
> Severity: serious
> Tags: ftbfs
> 
> https://buildd.debian.org/status/fetch.php?pkg=dante=armhf=1.4.3%2Bdfsg-1=1710761774=0

Thanks for reporting this. I noticed it as soon as I uploaded this
version of dante, and I started looking into it; it is, at least partly,
fallout from the new "implicit function declarations are errors" GCC
option setting. FTR, I believe this is a good idea, no complaints here.
However, it turns out to be a bit more complicated than sprinkling
a couple of #include directives here and there; I will hopefully be
able to upload a fixed version within the next couple of days.

G'luck,
Peter

-- 
Peter Pentchev  r...@ringlet.net r...@debian.org p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13


signature.asc
Description: PGP signature

Bug#1000003: (no subject)

[Fredrik Roubert]

A new upstream release has now been made, with the switch to PCRE2:

https://gitlab.com/pdfgrep/pdfgrep/-/releases/v2.2.0

Bug#1058071: mirror submission for mirrors.cat.pdx.edu

[Amber Jennings]

Hi Adam,
Thanks for following up.
Responses are inline.

  We expect at least the Maintainer and Upstream-mirror values to be filled
> in,
>   and your trace file is missing one or both of them.
>

I've updated our ftpsync.conf, this shouldn't be an issue anymore.

armel, mipsel and s390x are all currently supported architectures and
> would be expected to appear on all Debian mirrors.
>

We don't currently have the disk space to support more architectures but
plan to be able to accommodate this in the future.

Let us know if you have more questions, thanks.
--
Amber Jennings (she/her) | Computer Action Team
(503) 725-5420 | CC: supp...@cat.pdx.edu
https://cat.pdx.edu | https://support.cat.pdx.edu

On Fri, Mar 22, 2024 at 10:33 AM Adam D. Barratt 
wrote:

> Control: tags -1 + moreinfo
>
> Hi,
>
> Apologies for the delay in getting back to you.
>
> On Mon, 2023-12-11 at 23:52 +, Sage Imel wrote:
> > Site: mirrors.cat.pdx.edu
> > Archive-architecture: amd64 arm64 armhf hurd-amd64 i386 riscv64
>
> Our automated checks noticed an issue with your mirror:
>
> o The trace file at
>   http://mirrors.cat.pdx.edu/debian/project/trace/mirrors.cat.pdx.edu
>   is missing some required information.
>
>   We expect at least the Maintainer and Upstream-mirror values to be
> filled in,
>   and your trace file is missing one or both of them.
>
> As an additional note, is there a reason that you only mirror a subset
> of Debian's official architectures?
>
> Architectures-Configuration: EXCLUDE alpha arm armel hppa hurd-i386 ia64
> kfreebsd-amd64 kfreebsd-i386 m68k mips mipsel powerpc s390 s390x sh sparc
>
> armel, mipsel and s390x are all currently supported architectures and
> would be expected to appear on all Debian mirrors.
>
> Regards,
>
> Adam
>

Bug#1067698: RFS: persist-el/0.6+dfsg-1 [Team] -- persist variables between Emacs Sessions

[Xiyue Deng]

Hi Nicholas,

Nicholas D Steeves  writes:

> Control: owner -1 !
>
> Xiyue Deng  writes:
>
>>[ Xiyue Deng ]
>>* New upstream release.
>>* Re-export upstream signing key without extra signatures.
>
> $ uscan --download-current-version 
> Newest version of persist-el on remote site is 0.6, specified download 
> version is 0.6
> gpgv: Signature made Sat 13 Jan 2024 05:05:03 EST
> gpgv:using RSA key C433554766D3DDC64221BFAA066DAFCB81E42C40
> gpgv: Good signature from "GNU ELPA Signing Agent (2019) 
> "
> gpgv: Signature made Sat 13 Jan 2024 05:05:03 EST
> gpgv:using EDDSA key 0327BE68D64D9A1A66859F15645357D2883A0966
> gpgv: Can't check signature: No public key
> uscan die: OpenPGP signature did not verify. at 
> /usr/share/perl5/Devscripts/Uscan/Output.pm line 77.

I have been in contact with upstream maintainer Joseph Turner
 about this issue.  He replied that he
recently took over the maintenance of persist and was not aware about
this key either.  I have followed his suggestion and filed a bug report
to bug-gnu-em...@gnu.org about this issue[1].

Meanwhile, as the RSA key signature is good, I resorted to use "uscan
--skip-signature" to get the current version, dropped the GFDL document
source and repacked the source tarball.  Hope this process sounds ok to
you.

-- 
Xiyue Deng

[1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=70003

Bug#1067571: applicability to stable and oldstable

[Dominic Hargreaves]

We had intended to update this via a DSA in stable and oldstable, but
I believe 
renders this unexploitable, so it'll probably go in as a point release
instead.

Dominic

Bug#1067720: Don't hard-code the python version in d/control

[Matthias Klose]

Package: src:virtnbdbackup
Version: 2.0-1
Severity: important
Tags: sid trixie patch
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Don't hard-code the python version in d/control, it will fail with 3.12

patch at
http://launchpadlibrarian.net/721153415/virtnbdbackup_2.0-1build1_2.0-1ubuntu1.diff.gz

Bug#1067719: RFP: libgourou and utils -- free implementation of Adobe's ADEPT protocol used to add DRM on ePub/PDF files

[José Luis González]

Package: wnpp
Version: unspecified
Severity: wishlist
Upstream Author: Grégory Soutadé
URL: https://forge.soutade.fr/soutade/libgourou/
License: LGPL3 / BSD
X-Debbugs-CC: debian-de...@lists.debian.org
Description: 

libgourou is a free implementation of Adobe's ADEPT protocol used to
add DRM on ePub/PDF files. It overcame the lack of Adobe support for
Linux platforms.

It's the first tool for free systems to be able to read Adobe DRM
protected ebooks (the industry standard for purchases and library
loans), and add them to your ereader.

It permits:

- Downloading an ePub/PDF from ACSM file
- Exporting your private key (for DeDRM software)
- Removing ADEPT DRM
- List loaned books
- Return a loaned book

Bug#1065308: RM: libtirpc-common [all] -- ROP; decruft for debootstrap installability

[Sebastian Ramacher]

Hi Samuel

On 2024-03-02 14:36:13 +0100, Samuel Thibault wrote:
> Package: ftp.debian.org
> Severity: normal
> X-Debbugs-Cc: libti...@packages.debian.org
> Control: affects -1 + src:libtirpc
> User: ftp.debian@packages.debian.org
> Usertags: remove
> 
> Hello,
> 
> Sorry I wasn't sure how to specify it exactly, but basically, could you
> please remove
> 
> libtirpc-common_1.3.4+ds-1 from unstable for arch:all
> 
> ? (now that libtirpc 1.3.4+ds-1.1 was built for all archs)
> 
> Currently debootstrap fails to create a chroot for various reasons, one
> of which being that we currently have both libtirpc-common_1.3.4+ds-1
> and libtirpc-common_1.3.4+ds-1.1 in unstable, and debootstrap isn't
> smart enough to determine that it's the latter that it should install,
> since libtirpc3t64_1.3.4+ds-1.1 depends on that one. Unfortunately
> debootstrap ends up choosing to install libtirpc-common_1.3.4+ds-1, and
> when libtirpc3t64_1.3.4+ds-1.1 is being configured we end up with
> 
> dpkg: dependency problems prevent configuration of libtirpc3t64:hurd-i386:
>  libtirpc3t64:hurd-i386 depends on libtirpc-common (>= 1.3.4+ds-1.1); however:
>   Version of libtirpc-common on system is 1.3.4+ds-1.
> 
> (here on hurd-i386, but other archs will have the same issue)

FWIW, the implementation of this removal also removed libtirp-common
1.3.4+ds-1.1 from the archive. I have uploaded -1.2 without any changes
to reintroduce the package and make libirpc3t64 installable again.

Cheers
-- 
Sebastian Ramacher

Bug#1067717: emacs-common: Security issues with emacs; remote code execution in Gnus

[John Goerzen]

Package: emacs-common
Version: 1:28.2+1-15
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: Debian Security Team 

Hello,

https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS?h=emacs-29 describes
some security issues addressed in emacs 29.3.

Among them:

** Gnus now treats inline MIME contents as untrusted.
To get back previous insecure behavior, 'untrusted-content' should be
reset to nil in the buffer.

** LaTeX preview is now by default disabled for email attachments.
To get back previous insecure behavior, set the variable
'org--latex-preview-when-risky' to a non-nil value.

I don't see anything that would explicitly indicate if the version in stable,
1.28.2, is vulnerable but the nature of this leads me to think that it is.

Thanks,

John

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

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

Versions of packages emacs-common depends on:
ii  emacs-el 1:28.2+1-15
ii  emacsen-common   3.0.5
ii  init-system-helpers  1.65.2
ii  install-info 6.8-6+b1

emacs-common recommends no packages.

Versions of packages emacs-common suggests:
pn  emacs-common-non-dfsg  
ii  ncurses-term   6.4-4

-- no debconf information

Bug#1067718: wsdd: Vcs points to 404 URL

[Bastian Germann]

Source: wsdd

wsdd's Vcs-Git points to https://salsa.debian.org/debian/wsdd.git which does 
not exist.

Bug#344783: bash3: the random number generator seems to be reseeded when a subshell is created

[Gioele Barabucci]

Control: tags -1 wontfix

On Mon, 26 Dec 2005 09:39:07 + mr_platelet+m689 
 wrote:

I would expect the following command to always give the same output,
because I seed RANDOM at the outset:

  bash3 -c 'RANDOM=1; set -x; true $RANDOM; true $RANDOM | true $RANDOM'

What I find in practise, however, is that, although the first line
printed is always the same, the next 2 lines are different on each run.

My guess is that a subshell is being created to run the pipeline, and
that bash, as part of its initialisation code for a subshell, seeds
RANDOM again, wiping out the seed I specified.


Bash holds its promise to provide a stable output once RANDOM is seeded 
inside the same shell:


$ cmd='RANDOM=1; set -x; true $RANDOM; true $RANDOM | true $RANDOM; 
true $RANDOM; true $RANDOM'

$ diff -u <(bash -c "$cmd" 2>&1) <(bash -c "$cmd" 2>&1)
--- /dev/fd/63
+++ /dev/fd/62
@@ -1,5 +1,5 @@
 + true 16807
-+ true 20358
-+ true 31354
++ true 8403
++ true 13062
 + true 10791
 + true 19566

As you noted, the evaluation of pipelines is a bit surprising, but the 
documentation clearly states:


> Each command in a multi-command pipeline, where pipes are created, is 
executed in a subshell, which is a separate process.


Exporting RANDOM does not help, but explicitly setting RANDOM inside 
each subshell fixes this issue:


$ cmd='RANDOM=1; set -x; true $RANDOM; { RANDOM=3; true $RANDOM;} | 
{ RANDOM=7; true $RANDOM;} ; true $RANDOM; true $RANDOM'

$ diff -u <(bash -c "$cmd" 2>&1) <(bash -c "$cmd" 2>&1) && echo same
same

Regards,

--
Gioele Barabucci

Bug#1066277: accountsservice: diff for NMU version 23.13.9-6.1

[Sebastian Ramacher]

Control: tags 1066277 + patch

Dear maintainer,

I've prepared an NMU for accountsservice (versioned as 23.13.9-6.1). The diff
is attached to this message.

Cheers
-- 
Sebastian Ramacher
diff -Nru accountsservice-23.13.9/debian/changelog accountsservice-23.13.9/debian/changelog
--- accountsservice-23.13.9/debian/changelog	2024-01-31 12:30:27.0 +0100
+++ accountsservice-23.13.9/debian/changelog	2024-03-25 22:57:03.0 +0100
@@ -1,3 +1,11 @@
+accountsservice (23.13.9-6.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches: Fix implicit function declarations in mocklibc. (Closes:
+#1066277)
+
+ -- Sebastian Ramacher   Mon, 25 Mar 2024 22:57:03 +0100
+
 accountsservice (23.13.9-6) unstable; urgency=medium
 
   * Team upload
diff -Nru accountsservice-23.13.9/debian/patches/implicit-funcs.patch accountsservice-23.13.9/debian/patches/implicit-funcs.patch
--- accountsservice-23.13.9/debian/patches/implicit-funcs.patch	1970-01-01 01:00:00.0 +0100
+++ accountsservice-23.13.9/debian/patches/implicit-funcs.patch	2024-03-25 22:53:41.0 +0100
@@ -0,0 +1,22 @@
+--- a/subprojects/mocklibc.wrap
 b/subprojects/mocklibc.wrap
+@@ -8,3 +8,5 @@
+ patch_url = https://wrapdb.mesonbuild.com/v1/projects/mocklibc/1.0/2/get_zip
+ patch_filename = mocklibc-1.0-2-wrap.zip
+ patch_hash = 0280f96a2eeb3c023e5acf4e00cef03d362868218d4a85347ea45137c0ef6c56
++
++diff_files = mocklibc-implicit-declarations.patch
+--- /dev/null
 b/subprojects/packagefiles/mocklibc-implicit-declarations.patch
+@@ -0,0 +1,11 @@
++--- mocklibc-1.0/src/netgroup-debug.c.orig	2024-03-25 22:48:31.515887807 +0100
+ mocklibc-1.0/src/netgroup-debug.c	2024-03-25 22:46:27.311037804 +0100
++@@ -21,6 +21,8 @@
++ #include 
++ #include 
++ 
+++extern void print_indent(FILE *stream, unsigned int indent);
+++
++ void netgroup_debug_print_entry(struct entry *entry, FILE *stream, unsigned int indent) {
++   print_indent(stream, indent);
++ 
diff -Nru accountsservice-23.13.9/debian/patches/series accountsservice-23.13.9/debian/patches/series
--- accountsservice-23.13.9/debian/patches/series	2024-01-31 12:30:27.0 +0100
+++ accountsservice-23.13.9/debian/patches/series	2024-03-25 22:49:52.0 +0100
@@ -2,3 +2,4 @@
 git_default_gdm.patch
 0002-create-and-manage-groups-like-on-a-debian-system.patch
 no-check-format.patch
+implicit-funcs.patch

Bug#1067716: RFS: fgetty/0.7-9 [QA] [RC] -- very small, efficient, console-only getty and login

[Lorenzo]

Package: sponsorship-requests
Severity: important

Dear mentors,

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

 * Package name : fgetty
   Version  : 0.7-9
   Upstream contact : Felix von Leitner 
 * URL  : https://www.fefe.de/fgetty
 * License  : GPL-2+
 * Vcs  : https://salsa.debian.org/debian/fgetty
   Section  : admin

The source builds the following binary packages:

  fgetty - very small, efficient, console-only getty and login

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

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

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

  dget -x
  https://mentors.debian.net/debian/pool/main/f/fgetty/fgetty_0.7-9.dsc

Git repo:
(I don't have permission to upload to salsa debian/fgetty so I
temporary forked in my namespace)

https://salsa.debian.org/Lorenzo.ru.g-guest/fgetty/-/tree/next?ref_type=heads

Changes since the last upload:

 fgetty (0.7-9) unstable; urgency=medium
 .
   * QA upload.
 .
   [ Francisco M Neto ]
   * quilt patches:
 - fix makefile to use dietlibc
 - add missing #include to fgetty.c
   (Closes: #1066518)
 - fix implict type declarations warnings
 .
   [ Lorenzo Puliti ]
   * Standards-Version: 4.6.2, no change required

Regards,
Lorenzo

Bug#1007664: lpr: please consider upgrading to 3.0 source format

[Bastian Germann]

I am uploading a NMU to DELAYED/10 in order to fix this.
Please find the debdiff attached.diff -Nru lpr-2008.05.17.3+nmu1/debian/README.Debian 
lpr-2008.05.17.3+nmu2/debian/README.Debian
--- lpr-2008.05.17.3+nmu1/debian/README.Debian  2008-05-20 00:44:10.0 
+
+++ lpr-2008.05.17.3+nmu2/debian/README.Debian  2024-03-25 21:31:09.0 
+
@@ -5,9 +5,6 @@
 as the upstream source.  This means that, as in the old days, filters are not
 run for remote printers.
 
-An up to date source code is available on
-  http://git.debian.org/?p=collab-maint/lpr.git;a=summary
-
 
 Configuration
 
diff -Nru lpr-2008.05.17.3+nmu1/debian/changelog 
lpr-2008.05.17.3+nmu2/debian/changelog
--- lpr-2008.05.17.3+nmu1/debian/changelog  2021-12-16 08:35:18.0 
+
+++ lpr-2008.05.17.3+nmu2/debian/changelog  2024-03-25 21:31:09.0 
+
@@ -1,3 +1,13 @@
+lpr (1:2008.05.17.3+nmu2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Convert to source format 3.0. (closes: #1007664)
+  * d/copyright: Convert to machine-readable format.
+  * d/copyright: Add missing ISC license.
+  * Remove outdated URL from README.Debian.
+
+ -- Bastian Germann   Mon, 25 Mar 2024 21:31:09 +
+
 lpr (1:2008.05.17.3+nmu1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru lpr-2008.05.17.3+nmu1/debian/copyright 
lpr-2008.05.17.3+nmu2/debian/copyright
--- lpr-2008.05.17.3+nmu1/debian/copyright  2005-01-29 04:40:20.0 
+
+++ lpr-2008.05.17.3+nmu2/debian/copyright  2024-03-25 21:31:09.0 
+
@@ -1,15 +1,56 @@
-This is Debian GNU/Linux's prepackaged version of lpr, the BSD line
-printing spool system.
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Comment:
+ This is Debian GNU/Linux's prepackaged version of lpr,
+ the BSD line printing spool system.
+Source:
+ This version of lpr is taken from OpenBSD, and was obtained via CVS from
+ anoncvs.usa.openbsd.org.
+ .
+ It also includes, from OpenBSD, the getcap.c file, which is part of the
+ OpenBSD C library.  It has been edited to remove its dependency on libdb.
+ The printcap.5 manpage is also from them.
 
-This package is maintained by Adam Klein .
+Files: *
+Copyright: The Regents of the University of California.
+ Copyright (c) 1995, 1996, 1998 Theo de Raadt.  All rights reserved.
+License: BSD-3-clause
+ Redistribution and use in source and binary forms, with or without
+ modification, are permitted provided that the following conditions
+ are met:
+ 1. Redistributions of source code must retain the above copyright
+notice, this list of conditions and the following disclaimer.
+ 2. Redistributions in binary form must reproduce the above copyright
+notice, this list of conditions and the following disclaimer in the
+documentation and/or other materials provided with the distribution.
+ 3. Neither the name of the University nor the names of its contributors
+may be used to endorse or promote products derived from this software
+without specific prior written permission.
+ .
+ THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+ ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+ IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+ FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+ DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+ OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+ HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+ LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+ OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+ SUCH DAMAGE.
 
-This version of lpr is taken from OpenBSD, and was obtained via CVS from
-anoncvs.usa.openbsd.org.
-
-It also includes, from OpenBSD, the getcap.c file, which is part of the
-OpenBSD C library.  It has been edited to remove its dependency on libdb.
-
-The printcap.5 manpage is also from them.
-
-The lpr package is distributed under the BSD licence. On Debian
-systems this licence is available in the file /usr/share/common-licenses/BSD.
+Files:
+ common_source/strlcat.c
+ common_source/strlcpy.c
+Copyright: (c) 1998 Todd C. Miller 
+License: ISC
+ Permission to use, copy, modify, and distribute this software for any
+ purpose with or without fee is hereby granted, provided that the above
+ copyright notice and this permission notice appear in all copies.
+ .
+ THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
+ WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
+ MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
+ ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
+ WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
+ ACTION OF 

Bug#810783:

[Yekini Bidemi nurudeen]

Bidemi Nurudeen


  1.  BabyGet Outlook for Android

Bug#1067715: calibre: doesn't install DeACSM plugin

[José Luis González]

Package: calibre
Version: 6.13.0+repack-2+deb12u3
Severity: important

I am unable to install the DeACSM plugin. It gives the following errors:


calibre, version 6.13.0
ERROR: Fallo en la instalación del complemento: Ha ocurrido un error al 
instalar este complemento y a continuación se desinstalará. Por favor, publique 
el mensaje de error que aparece en los detalles de más abajo en la conversación 
del foro para este complemento y reinicie calibre.

Traceback (most recent call last):
  File "/usr/lib/calibre/calibre/customize/ui.py", line 677, in 
initialize_plugin
p.initialize()
  File "calibre_plugins.deacsm.__init__", line 226, in initialize
from libadobe import createDeviceKeyFile, update_account_path, 
sendHTTPRequest
  File "/tmp/calibre_6.13.0_tmp_bazwlmj0/szujnx8a.zip/libadobe.py", line 59, in 

from oscrypto import keys
  File 
"/home/jlg/.config/calibre/plugins/DeACSM/modules/oscrypto/oscrypto/keys.py", 
line 5, in 
from ._asymmetric import parse_certificate, parse_private, parse_public
  File 
"/home/jlg/.config/calibre/plugins/DeACSM/modules/oscrypto/oscrypto/_asymmetric.py",
 line 27, in 
from .kdf import pbkdf1, pbkdf2, pkcs12_kdf
  File 
"/home/jlg/.config/calibre/plugins/DeACSM/modules/oscrypto/oscrypto/kdf.py", 
line 9, in 
from .util import rand_bytes
  File 
"/home/jlg/.config/calibre/plugins/DeACSM/modules/oscrypto/oscrypto/util.py", 
line 14, in 
from ._openssl.util import rand_bytes
  File 
"/home/jlg/.config/calibre/plugins/DeACSM/modules/oscrypto/oscrypto/_openssl/util.py",
 line 6, in 
from ._libcrypto import libcrypto, libcrypto_version_info, 
handle_openssl_error
  File 
"/home/jlg/.config/calibre/plugins/DeACSM/modules/oscrypto/oscrypto/_openssl/_libcrypto.py",
 line 24, in 
from ._libcrypto_ctypes import (
  File 
"/home/jlg/.config/calibre/plugins/DeACSM/modules/oscrypto/oscrypto/_openssl/_libcrypto_ctypes.py",
 line 47, in 
raise LibraryNotFoundError('Error detecting the version of libcrypto')
oscrypto.errors.LibraryNotFoundError: Error detecting the version of libcrypto

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/calibre/calibre/gui2/dialogs/plugin_updater.py", line 710, in 
_install_clicked
plugin = add_plugin(zip_path)
 
  File "/usr/lib/calibre/calibre/customize/ui.py", line 487, in add_plugin
plugin = initialize_plugin(plugin, path_to_zip_file, 
PluginInstallationType.EXTERNAL)
 

  File "/usr/lib/calibre/calibre/customize/ui.py", line 682, in 
initialize_plugin
raise InvalidPlugin((_('Initialization of plugin %s failed with traceback:')
calibre.customize.InvalidPlugin: La inicialización del complemento Traceback 
(most recent call last):
  File "/usr/lib/calibre/calibre/customize/ui.py", line 677, in 
initialize_plugin
p.initialize()
  File "calibre_plugins.deacsm.__init__", line 226, in initialize
from libadobe import createDeviceKeyFile, update_account_path, 
sendHTTPRequest
  File "/tmp/calibre_6.13.0_tmp_bazwlmj0/szujnx8a.zip/libadobe.py", line 59, in 

from oscrypto import keys
  File 
"/home/jlg/.config/calibre/plugins/DeACSM/modules/oscrypto/oscrypto/keys.py", 
line 5, in 
from ._asymmetric import parse_certificate, parse_private, parse_public
  File 
"/home/jlg/.config/calibre/plugins/DeACSM/modules/oscrypto/oscrypto/_asymmetric.py",
 line 27, in 
from .kdf import pbkdf1, pbkdf2, pkcs12_kdf
  File 
"/home/jlg/.config/calibre/plugins/DeACSM/modules/oscrypto/oscrypto/kdf.py", 
line 9, in 
from .util import rand_bytes
  File 
"/home/jlg/.config/calibre/plugins/DeACSM/modules/oscrypto/oscrypto/util.py", 
line 14, in 
from ._openssl.util import rand_bytes
  File 
"/home/jlg/.config/calibre/plugins/DeACSM/modules/oscrypto/oscrypto/_openssl/util.py",
 line 6, in 
from ._libcrypto import libcrypto, libcrypto_version_info, 
handle_openssl_error
  File 
"/home/jlg/.config/calibre/plugins/DeACSM/modules/oscrypto/oscrypto/_openssl/_libcrypto.py",
 line 24, in 
from ._libcrypto_ctypes import (
  File 
"/home/jlg/.config/calibre/plugins/DeACSM/modules/oscrypto/oscrypto/_openssl/_libcrypto_ctypes.py",
 line 47, in 
raise LibraryNotFoundError('Error detecting the version of libcrypto')
oscrypto.errors.LibraryNotFoundError: Error detecting the version of libcrypto
 falló y generó la siguiente traza:
Traceback (most recent call last):
  File "/usr/lib/calibre/calibre/customize/ui.py", line 677, in 
initialize_plugin
p.initialize()
  File "calibre_plugins.deacsm.__init__", line 226, in initialize
from libadobe import createDeviceKeyFile, update_account_path, 
sendHTTPRequest
  File "/tmp/calibre_6.13.0_tmp_bazwlmj0/szujnx8a.zip/libadobe.py", line 59, in 

from oscrypto import keys
  File 
"/home/jlg/.config/calibre/plugins/DeACSM/modules/oscrypto/oscrypto/keys.py", 
line 5, in 
   

Bug#929178: bash: in a subshell trap displays the trap definition of main

[Gioele Barabucci]

Control: tags -1 wontfix

The bash maintainer has confirmed in 
https://lists.gnu.org/archive/html/bug-bash/2024-03/msg00212.html that 
this behavior of trap is both intended and  allowed by the spec, 
although other shell behave differently.


Regards,

--
Gioele Barabucci

Bug#1067714: llvm-toolchain-17: Build should use at least one CPU

[Santiago Vila]

Package: src:llvm-toolchain-17
Version: 17.0.6-5
Tags: patch

Dear maintainer:

I tried to build this package on a machine with 2 CPUs, 4GB of RAM,
and some swap, and the build stopped unexpectedly with this strange
error message:

LD_LIBRARY_PATH=/<>/build-llvm/lib:$LD_LIBRARY_PATH \
VERBOSE=1  cmake --build build-llvm -j 0 --target stage2 || cat 
build-llvm/tools/clang/stage2-bins/CMakeFiles/CMakeOut
put.log
The  value requires a positive integer argument.

Usage: cmake --build  [options] [-- [native-options]]
   cmake --build --preset  [options] [-- [native-options]]
Options:
= Project binary directory to be built.
  --preset , --preset=
 = Specify a build preset.
  --list-presets[=]
 = List available build presets.
  --parallel [], -j []
 = Build in parallel using the given number of jobs.
   If  is omitted the native build tool's
   default number is used.
[...]

I would expect a message saying "not enough memory" instead,
not a "rant" about how I should use cmake.

However, I believe we could take for granted that the end user
knows what they are doing and simply ensure that NJOBS is
always >= 1 no matter what.

The attached patch tries to do that.

It changes "n==1 ? 1" to "n==1 || n2<=1 ? 1".

Also, it fixes a bug where in some cases the output is
greater than the number of available CPUs.

So, instead of "n2 n,
I propose "n2<=n ? n2 : n" which IMO is a little bit more readable.

Thanks.--- a/debian/rules
+++ b/debian/rules
@@ -59,7 +59,7 @@ else
 endif
 NJOBS := $(shell mt=`awk '/^(MemAvail|SwapFree)/ { mt += $$2 } END {print mt}' 
/proc/meminfo`; \
awk -vn=$(NCPUS) -vmt=$$mt -vm=$(MEM_PER_CPU) \
- 'END { mt/=1024; n2 = int(mt/m); print n==1 ? 1 : n2

Bug#1067713: ITP: python-rst2ansi -- Python module to render reStructuredText to ansi-escaped strings

[Boyuan Yang]

Package: wnpp
Owner: Boyuan Yang 
Severity: wishlist

* Package name: python-rst2ansi
  Version : 0.1.5
  Upstream Contact: Franklin "Snaipe" Mathieu
* URL : https://github.com/Snaipe/python-rst2ansi
* License : MIT/Expat
  Programming Lang: Python
  Description : Python module to render reStructuredText to ansi-escaped
strings

  The rst2ansi project is a python module dedicated to rendering RST
  (reStructuredText) documents to ansi-escaped strings suitable for display
  in a terminal.

This package is a dependency of src:backblaze-b2.

This package will be maintained under Debian Python Team umbrella.

Thanks,
Boyuan Yang


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

Bug#1067699: libllvm18:i386 contains files, also in libllvm18:amd64

[Torsten Wohlfarth]

libLLVM.so.1:i386 contains

should be

libllvm18:i386

Am 25.03.24 um 19:35 schrieb Torsten Wohlfarth:

libLLVM.so.1:i386 contains

Bug#1007513: logtools: please consider upgrading to 3.0 source format

[Bastian Germann]

I am uploading a NMU to DELAYED/10 in order to fix this.
Please find the debdiff attached.diff -Nru logtools-0.13e+nmu2/changes.txt logtools-0.13e+nmu3/changes.txt
--- logtools-0.13e+nmu2/changes.txt 2021-12-27 20:56:35.0 +
+++ logtools-0.13e+nmu3/changes.txt 2024-03-25 21:13:33.0 +
@@ -1,3 +1,14 @@
+logtools (0.13e+nmu3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Convert to source format 3.0. Closes: #1007513
+  * d/copyright: Convert to machine-readable format.
+
+  [ Helmut Grohne ]
+  * Fix FTCBFS: Let dh_auto_configure pass --host to configure. Closes: #977940
+
+ -- Bastian Germann   Mon, 25 Mar 2024 21:13:33 +
+
 logtools (0.13e+nmu2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru logtools-0.13e+nmu2/debian/changelog 
logtools-0.13e+nmu3/debian/changelog
--- logtools-0.13e+nmu2/debian/changelog2021-12-27 20:56:35.0 
+
+++ logtools-0.13e+nmu3/debian/changelog2024-03-25 21:13:33.0 
+
@@ -1,3 +1,14 @@
+logtools (0.13e+nmu3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Convert to source format 3.0. Closes: #1007513
+  * d/copyright: Convert to machine-readable format.
+
+  [ Helmut Grohne ]
+  * Fix FTCBFS: Let dh_auto_configure pass --host to configure. Closes: #977940
+
+ -- Bastian Germann   Mon, 25 Mar 2024 21:13:33 +
+
 logtools (0.13e+nmu2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru logtools-0.13e+nmu2/debian/copyright 
logtools-0.13e+nmu3/debian/copyright
--- logtools-0.13e+nmu2/debian/copyright2020-12-16 19:34:16.0 
+
+++ logtools-0.13e+nmu3/debian/copyright2024-03-25 21:13:33.0 
+
@@ -1,10 +1,11 @@
-This package was debianized by Russell Coker  on
-Fri, 25 Aug 2000 19:53:08 +0200.
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Comment:
+ This package was debianized by Russell Coker  on
+ Fri, 25 Aug 2000 19:53:08 +0200.
+Source:
+ http://www.coker.com.au/logtools/
 
-It was downloaded from http://www.coker.com.au/logtools/
-
-Upstream Author(s): Russell Coker 
-
-Copyright:
-
-GPL 2.0
+Files: *
+Copyright: Russell Coker 
+License: GPL-2
+ See /usr/share/common-licenses/GPL-2 on Debian systems.
diff -Nru logtools-0.13e+nmu2/debian/rules logtools-0.13e+nmu3/debian/rules
--- logtools-0.13e+nmu2/debian/rules2021-12-27 20:56:35.0 +
+++ logtools-0.13e+nmu3/debian/rules2024-03-25 21:13:33.0 +
@@ -9,7 +9,7 @@
 configure-stamp:
dh_testdir
# Add here commands to configure the package.
-   ./configure --prefix=`pwd`/debian/logtools/usr 
--mandir=\$${prefix}/share/man --sysconfdir=`pwd`/debian/logtools/etc
+   dh_auto_configure -- --prefix=`pwd`/debian/logtools/usr 
--sysconfdir=`pwd`/debian/logtools/etc
 
touch configure-stamp
 
diff -Nru logtools-0.13e+nmu2/debian/source/format 
logtools-0.13e+nmu3/debian/source/format
--- logtools-0.13e+nmu2/debian/source/format1970-01-01 00:00:00.0 
+
+++ logtools-0.13e+nmu3/debian/source/format2024-03-25 21:13:33.0 
+
@@ -0,0 +1 @@
+3.0 (native)

Bug#1067712: rust-stacker: FTBFS on mips64el: process didn't exit successfully: `/<>/target/mips64el-unknown-linux-gnuabi64/debug/deps/smoke-983e0e8761f2ceb1` (signal: 11, SIGSEGV: invali

[Sebastian Ramacher]

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

https://buildd.debian.org/status/fetch.php?pkg=rust-stacker=mips64el=0.1.15-1=1710415379=0

running 1 test
test foo ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; 
finished in 0.61s

 Running 
`/<>/target/mips64el-unknown-linux-gnuabi64/debug/deps/smoke-983e0e8761f2ceb1`

running 5 tests
error: test failed, to rerun pass `--test smoke`

Caused by:
  process didn't exit successfully: 
`/<>/target/mips64el-unknown-linux-gnuabi64/debug/deps/smoke-983e0e8761f2ceb1`
 (signal: 11, SIGSEGV: invalid memory reference)
dh_auto_test: error: /usr/share/cargo/bin/cargo test --all returned exit code 
101

Cheers
-- 
Sebastian Ramacher

Bug#1067698: RFS: persist-el/0.6+dfsg-1 [Team] -- persist variables between Emacs Sessions

[Nicholas D Steeves]

Control: owner -1 !

Xiyue Deng  writes:

>[ Xiyue Deng ]
>* New upstream release.
>* Re-export upstream signing key without extra signatures.

$ uscan --download-current-version 
Newest version of persist-el on remote site is 0.6, specified download version 
is 0.6
gpgv: Signature made Sat 13 Jan 2024 05:05:03 EST
gpgv:using RSA key C433554766D3DDC64221BFAA066DAFCB81E42C40
gpgv: Good signature from "GNU ELPA Signing Agent (2019) 
"
gpgv: Signature made Sat 13 Jan 2024 05:05:03 EST
gpgv:using EDDSA key 0327BE68D64D9A1A66859F15645357D2883A0966
gpgv: Can't check signature: No public key
uscan die: OpenPGP signature did not verify. at 
/usr/share/perl5/Devscripts/Uscan/Output.pm line 77.

Bug#781056: bash: undocumented deviation from upstream behaviour

[Gioele Barabucci]

Control: tags -1 moreinfo

On Mon, 23 Mar 2015 22:12:18 +0100 Christoph Anton Mitterer 
 wrote:

Apparently there's some strange patch applied against the Debian
version of bash, which allows suid scripts to be executed
(isn't that a security issue?).


Hi,

why would that be a security issues? Executing suid scripts is just as 
dangerous as executing suid binaries.



It also seems to invalidate that documented behaviour from the manpage:
>If the shell is started with the effective user (group) id not equal to
>the real user (group) id, and the -p option is not supplied, no startup
>files are read, shell functions are not inherited from the environment,
>the SHELLOPTS, BASHOPTS, CDPATH,  and  GLOBIGNORE  variables,  if  they
>appear  in  the  environment, are ignored, and the effective user id is
>set to the real user id.  If the -p option is supplied  at  invocation,
>the  startup  behavior  is  the  same, but the effective user id is not
>reset.

So could you please either correct the behaviour or accordingly remove
that documentation and add it to a secution of deviations between
upstream and Debian?


The documentation states what happens when bash acts as the interpreter 
for a suid script. Certain variables are cleared, some files are not read.


Did you find that any of the described measures are not applied when 
running suid scripts?


Regards,

--
Gioele Barabucci

Bug#1067711: mrpt: dpkg-gencontrol: warning: can't parse dependency fonts-roboto-fontface (= )

[Aurelien Jarno]

Source: mrpt
Version: 1:2.12.0+ds-1.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear maintainer,

mrpt fails to build from source with an error in dpkg-gencontrol. From
my build log on amd64:

| make[1]: Leaving directory '/<>'
|dh_gencontrol -O--buildsystem=pybuild
| dpkg-gencontrol: warning: Depends field of package libmrpt-topography2.12: 
substitution variable ${shlibs:Depends} used, but is not defined
| dpkg-gencontrol: warning: Depends field of package libmrpt-topography2.12: 
substitution variable ${misc:Depends} used, but is not defined
| dpkg-gencontrol: warning: Provides field of package libmrpt-topography2.12: 
substitution variable ${t64:Provides} used, but is not defined
| dpkg-gencontrol: warning: Depends field of package libmrpt-kinematics2.12: 
substitution variable ${shlibs:Depends} used, but is not defined
| dpkg-gencontrol: warning: Depends field of package libmrpt-kinematics2.12: 
substitution variable ${misc:Depends} used, but is not defined
| dpkg-gencontrol: warning: Provides field of package libmrpt-kinematics2.12: 
substitution variable ${t64:Provides} used, but is not defined
| dpkg-gencontrol: warning: Depends field of package libmrpt-poses2.12: 
substitution variable ${shlibs:Depends} used, but is not defined
| dpkg-gencontrol: warning: Depends field of package libmrpt-poses2.12: 
substitution variable ${misc:Depends} used, but is not defined
| dpkg-gencontrol: warning: Provides field of package libmrpt-poses2.12: 
substitution variable ${t64:Provides} used, but is not defined
| dpkg-gencontrol: warning: Provides field of package libmrpt-topography2.12: 
substitution variable ${t64:Provides} used, but is not defined
| dpkg-gencontrol: warning: Depends field of package libmrpt-nav2.12: 
substitution variable ${shlibs:Depends} used, but is not defined
| dpkg-gencontrol: warning: Depends field of package libmrpt-nav2.12: 
substitution variable ${misc:Depends} used, but is not defined
| dpkg-gencontrol: warning: Provides field of package libmrpt-nav2.12: 
substitution variable ${t64:Provides} used, but is not defined
| dpkg-gencontrol: warning: Depends field of package libmrpt-detectors2.12: 
substitution variable ${shlibs:Depends} used, but is not defined
| dpkg-gencontrol: warning: Depends field of package libmrpt-detectors2.12: 
substitution variable ${misc:Depends} used, but is not defined
| dpkg-gencontrol: warning: Provides field of package libmrpt-detectors2.12: 
substitution variable ${t64:Provides} used, but is not defined
| dpkg-gencontrol: warning: Depends field of package libmrpt-ros1bridge2.12: 
substitution variable ${shlibs:Depends} used, but is not defined
| dpkg-gencontrol: warning: Depends field of package libmrpt-ros1bridge2.12: 
substitution variable ${misc:Depends} used, but is not defined
| dpkg-gencontrol: warning: Provides field of package libmrpt-ros1bridge2.12: 
substitution variable ${t64:Provides} used, but is not defined
| dpkg-gencontrol: warning: Depends field of package libmrpt-system2.12: 
substitution variable ${shlibs:Depends} used, but is not defined
| dpkg-gencontrol: warning: Depends field of package libmrpt-system2.12: 
substitution variable ${misc:Depends} used, but is not defined
| dpkg-gencontrol: warning: Provides field of package libmrpt-system2.12: 
substitution variable ${t64:Provides} used, but is not defined
| dpkg-gencontrol: warning: Depends field of package libmrpt-config2.12: 
substitution variable ${shlibs:Depends} used, but is not defined
| dpkg-gencontrol: warning: Depends field of package libmrpt-config2.12: 
substitution variable ${misc:Depends} used, but is not defined
| dpkg-gencontrol: warning: Provides field of package libmrpt-config2.12: 
substitution variable ${t64:Provides} used, but is not defined
| dpkg-gencontrol: warning: Depends field of package libmrpt-hwdrivers2.12: 
substitution variable ${shlibs:Depends} used, but is not defined
| dpkg-gencontrol: warning: Depends field of package libmrpt-hwdrivers2.12: 
substitution variable ${misc:Depends} used, but is not defined
| dpkg-gencontrol: warning: Provides field of package libmrpt-hwdrivers2.12: 
substitution variable ${t64:Provides} used, but is not defined
| dpkg-gencontrol: warning: Depends field of package libmrpt-apps2.12: 
substitution variable ${shlibs:Depends} used, but is not defined
| dpkg-gencontrol: warning: Depends field of package libmrpt-apps2.12: 
substitution variable ${misc:Depends} used, but is not defined
| dpkg-gencontrol: warning: Provides field of package libmrpt-apps2.12: 
substitution variable ${t64:Provides} used, but is not defined
| dpkg-gencontrol: warning: Depends field of package libmrpt-graphslam2.12: 
substitution variable ${shlibs:Depends} used, but is not defined
| dpkg-gencontrol: warning: Depends field of package libmrpt-graphslam2.12: 
substitution variable ${misc:Depends} used, but is not defined
| dpkg-gencontrol: warning: Provides field of package 

Bug#1007071: lockfile-progs: please consider upgrading to 3.0 source format

[Bastian Germann]

I am uploading a NMU to DELAED/10 in order to fix this.
Please find the debdiff attached.diff -Nru lockfile-progs-0.1.19/.git/COMMIT_EDITMSG 
lockfile-progs-0.1.19+nmu1/.git/COMMIT_EDITMSG
--- lockfile-progs-0.1.19/.git/COMMIT_EDITMSG   2021-09-03 17:40:55.0 
+
+++ lockfile-progs-0.1.19+nmu1/.git/COMMIT_EDITMSG  1970-01-01 
00:00:00.0 +
@@ -1 +0,0 @@
-Update debian/changelog for 0.1.19 release
diff -Nru lockfile-progs-0.1.19/.git/FETCH_HEAD 
lockfile-progs-0.1.19+nmu1/.git/FETCH_HEAD
--- lockfile-progs-0.1.19/.git/FETCH_HEAD   2021-09-03 17:40:18.0 
+
+++ lockfile-progs-0.1.19+nmu1/.git/FETCH_HEAD  1970-01-01 00:00:00.0 
+
@@ -1 +0,0 @@
-940001c1f30c7d9cb7bd8b3c4ab679f7c1eb761e   not-for-merge   branch 'main' 
of /dv/u/rlb/git/lockfile-progs
diff -Nru lockfile-progs-0.1.19/.git/HEAD lockfile-progs-0.1.19+nmu1/.git/HEAD
--- lockfile-progs-0.1.19/.git/HEAD 2021-09-03 17:08:44.0 +
+++ lockfile-progs-0.1.19+nmu1/.git/HEAD1970-01-01 00:00:00.0 
+
@@ -1 +0,0 @@
-ref: refs/heads/main
diff -Nru lockfile-progs-0.1.19/.git/ORIG_HEAD 
lockfile-progs-0.1.19+nmu1/.git/ORIG_HEAD
--- lockfile-progs-0.1.19/.git/ORIG_HEAD2021-09-03 17:40:30.0 
+
+++ lockfile-progs-0.1.19+nmu1/.git/ORIG_HEAD   1970-01-01 00:00:00.0 
+
@@ -1 +0,0 @@
-2f46ab4619beba76580835be797629987f731344
diff -Nru lockfile-progs-0.1.19/.git/config 
lockfile-progs-0.1.19+nmu1/.git/config
--- lockfile-progs-0.1.19/.git/config   2021-09-03 17:15:23.0 +
+++ lockfile-progs-0.1.19+nmu1/.git/config  1970-01-01 00:00:00.0 
+
@@ -1,11 +0,0 @@
-[core]
-   repositoryformatversion = 0
-   filemode = true
-   bare = false
-   logallrefupdates = true
-[remote "rlb-u"]
-   url = /dv/u/rlb/git/lockfile-progs.git
-   fetch = +refs/heads/*:refs/remotes/rlb-u/*
-[remote "locke-u"]
-   url = /dv/u/locke/git/lockfile-progs.git/
-   fetch = +refs/heads/*:refs/remotes/locke-u/*
diff -Nru lockfile-progs-0.1.19/.git/config~ 
lockfile-progs-0.1.19+nmu1/.git/config~
--- lockfile-progs-0.1.19/.git/config~  2021-09-03 17:09:05.0 +
+++ lockfile-progs-0.1.19+nmu1/.git/config~ 1970-01-01 00:00:00.0 
+
@@ -1,11 +0,0 @@
-[core]
-   repositoryformatversion = 0
-   filemode = true
-   bare = false
-   logallrefupdates = true
-[remote "rlb-u"]
-   url = /dv/u/rlb/git/lockfile-progs.git
-   fetch = +refs/heads/*:refs/remotes/rlb-u/*
-[branch "main"]
-   remote = rlb-u
-   merge = refs/heads/master
diff -Nru lockfile-progs-0.1.19/.git/description 
lockfile-progs-0.1.19+nmu1/.git/description
--- lockfile-progs-0.1.19/.git/description  2018-09-03 18:10:55.0 
+
+++ lockfile-progs-0.1.19+nmu1/.git/description 1970-01-01 00:00:00.0 
+
@@ -1 +0,0 @@
-Unnamed repository; edit this file 'description' to name the repository.
diff -Nru lockfile-progs-0.1.19/.git/gitk.cache 
lockfile-progs-0.1.19+nmu1/.git/gitk.cache
--- lockfile-progs-0.1.19/.git/gitk.cache   2021-09-03 17:40:37.0 
+
+++ lockfile-progs-0.1.19+nmu1/.git/gitk.cache  1970-01-01 00:00:00.0 
+
@@ -1,5 +0,0 @@
-1 3
-6d88ceff08b50437faa8dc4b0a96a1b18d1b3d7e 
4ff2c9f2d0bfe86e6e10fae94daffee1a3ef6a65 
{a5968cbe2f6655bd128b573b3a58c033fb6d686b 
af1f5a513a2c00496c4007c6cebd0061995d007d 
6629c500f7487e118efe4e54e24ace43ef701a7e 
27ded567d6f81c4740611374987fcaee017ceef4 
c2b1a945c48a5bd1b50b65720e874305c3cbabb1 
1edd7d1357f64dd5ffb5bcccabecbabdc0081f04 
addb74fc065e36d272a35a8830d83bed2dee9957 
b8d79018f2593d9d5dc5bd92a9dc6a44e49176fa 
9fe1ff16b986991ae2a3f04e6bbdbdae6fa5afcc 
ad74bcc60e7c0d9a522284eb3a4ad8fdd59f7870 
2eab4d75323e278edbf637368daf1c9b66176dfc 
3c79d1df8b3566d226d2dc413ab687ddf3adbda5 
1ddc675392e49dcc681d284e187f88ec0b108294 
bb13aa40431a26ce842dc891bcdd348fed226946 
1feaa2029200b850e00e39bf9bc047b45f9d21f8 
8ca2a4310700d01ee973a0a183af95f0fd2c33fc 
188c92b290115114b4f1dc92e635514547df0684 
96b7ffdddbfe322ac8834e6624dad19b296d00ef 
88ebaaedb795641c666d13cad98d7f5a3595f4b8 
d6a4d9eb85528e978419d458f176ebbf9db128ce 
998202f6026b8495c146a30d58c1978e2adc045e 
d3e00ff2d758d1dbd66107904cf1c8f4b25481be 
33ea48b895743b7df2b79ae2cf2e590d4361244b 
d38b3ec8519e89f16e6691db8aed51890491249a 
0f85d28b70089e250c01ca7679b6a013a262478c 
ef8fd22688f631dfeb94157645fd7e9406ce7c01 
cf06841bc279fc85779ab960691bd72a56057e94 
0162cadb1cd045942da70f0cf8713a143a1b26ce 
57a7929c7ad440cec685f1164219b39b0ece9f77 
551a94379a050fce87bd8c0e493c8f11243141af 
dcdbac16fc5bc13d9d1fb61022f4bb8ed3c196d0 
54d03e4a395410b73d393ad33f964d7bf59feb7d 
8e34217d087763ab58e5b2acb7cf8ef31bcdd535 
410a42cbe931e1bfd6acb560c48c2a9c06fc9dff 
294cb02dcf1c3763bb0dd29284c73f9f10f9d842 
594e67dcebbb1a165392a659c41637582445ebd9 
a4a4fd365ac0cfaa5b851c497d1bec8e5e440a6f 
4dd6eeade9c00c60c0fe566f7fec83186b29b25e 
649fa6f9a3be4e45950090b3888b478c064f0d98 

Bug#1067534: Manual deps on lib* need updating for the time64 transition

[Axel Beckert]

Control: tag -1 + pending

Hi Andrey,

thanks for bringing this up.

Andrey Rakhmatullin wrote:
> All subpackages have manually specified deps like libqt5core5a, all of them
> need updating to lib*t64 ones.

I though disagree with the phrase "all subpackages". As far as I can
see there are solely two dependencies of only one binary package
(namely qutebrowser) affected: libqt5core5a and libqt5dbus5.

I neither see a package called libqt5webkit5t64 nor a package called.
libqt5webenginecore5t64.

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

Bug#1056192: slirp4netns: allow reusing an existing tap file descriptor

[Helmut Grohne]

Control: forwarded -1 
https://github.com/rootless-containers/slirp4netns/pull/340

On Sat, Nov 18, 2023 at 05:26:57PM +0100, Helmut Grohne wrote:
> Since patches speak louder than words, I am attaching a demo patch of
> how this is supposed to work. What do you think about it?

In the mean time, I've sent the patch upstream.

Helmut

Bug#1067710: libmtp FTCBFS: configures for the build architecture

[Helmut Grohne]

Source: libmtp
Version: 1.1.21-3.1
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

libmtp fails to cross build from source, because it configures for the
build architecture and thus fails finding required dependencies. It
actually configures twice. While the second time - issued by debhelper -
would configure for the host architecture, it is the first attempt
during autogen.sh that is both unnecessary and failing. Skipping it
makes the native build faster and the cross build succeed. I'm attaching
a patch for your convenience.

Helmut
diff --minimal -Nru libmtp-1.1.21/debian/changelog 
libmtp-1.1.21/debian/changelog
--- libmtp-1.1.21/debian/changelog  2024-02-28 15:18:19.0 +0100
+++ libmtp-1.1.21/debian/changelog  2024-03-25 07:43:18.0 +0100
@@ -1,3 +1,10 @@
+libmtp (1.1.21-3.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Configure only once for the host architecture. (Closes: #-1)
+
+ -- Helmut Grohne   Mon, 25 Mar 2024 07:43:18 +0100
+
 libmtp (1.1.21-3.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff --minimal -Nru libmtp-1.1.21/debian/rules libmtp-1.1.21/debian/rules
--- libmtp-1.1.21/debian/rules  2024-02-28 15:18:18.0 +0100
+++ libmtp-1.1.21/debian/rules  2024-03-25 07:43:17.0 +0100
@@ -32,7 +32,7 @@
dh $@
 
 execute_before_dh_autoreconf:
-   ./autogen.sh
+   NOCONFIGURE=1 ./autogen.sh
 
 override_dh_auto_configure:
# Save file modified by configure

Bug#1007318: keyboards-rg: please consider upgrading to 3.0 source format

[Bastian Germann]

I am uploading a NMU to DELAED/10 in order to fix this.
Please find the debdiff attached.diff -Nru keyboards-rg-0.3+nmu1/debian/changelog 
keyboards-rg-0.3+nmu2/debian/changelog
--- keyboards-rg-0.3+nmu1/debian/changelog  2021-01-05 10:58:15.0 
+
+++ keyboards-rg-0.3+nmu2/debian/changelog  2024-03-25 20:29:24.0 
+
@@ -1,3 +1,11 @@
+keyboards-rg (0.3+nmu2) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Move format file to make it effective (closes: #1007318)
+  * d/copyright: Convert to machine-readable format
+
+ -- Bastian Germann   Mon, 25 Mar 2024 20:29:24 +
+
 keyboards-rg (0.3+nmu1) unstable; urgency=medium
 
   * Non maintainer upload by the Reproducible Builds team.
@@ -25,7 +33,3 @@
   * Initial Release
 
  -- Radovan Garabik   Wed,  6 Nov 2002 
13:08:38 +0200
-
-Local variables:
-mode: debian-changelog
-End:
diff -Nru keyboards-rg-0.3+nmu1/debian/copyright 
keyboards-rg-0.3+nmu2/debian/copyright
--- keyboards-rg-0.3+nmu1/debian/copyright  2016-10-17 13:04:42.0 
+
+++ keyboards-rg-0.3+nmu2/debian/copyright  2024-03-25 20:29:24.0 
+
@@ -1,10 +1,39 @@
-This package was written by Radovan Garabík 
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Comment: This package was written by
+ Radovan Garabík 
 
+Files: *
 Copyright:
+Copyright © 2006--2016 Radovan Garabík
+License: GPL
 
+Files: layouts-xkb/*
 Copyright © 2006--2016 Radovan Garabík
+License: GPL or X11
 
-Copyright: 
-GPL (see see /usr/share/common-licenses/GPL for console layouts, GPL or
-XFree86 (whatever you wish) licence for xkb layouts.
+License: GPL
+ See /usr/share/common-licenses/GPL on Debian systems.
 
+License: X11
+ Redistribution and use in source and binary forms, with or without
+ modification, are permitted provided that the following conditions
+ are met:
+ .
+ Redistributions of source code must retain the above copyright notice,
+ this list of conditions and the following disclaimer.
+ .
+ Neither name of the copyright holders nor the names of its
+ contributors may be used to endorse or promote products derived from
+ this software without specific prior written permission.
+ .
+ THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND THE CONTRIBUTORS
+ "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
+ LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
+ A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
+ HOLDERS OR THE CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
+ INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
+ BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
+ OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+ ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
+ TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
+ USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
diff -Nru keyboards-rg-0.3+nmu1/debian/format 
keyboards-rg-0.3+nmu2/debian/format
--- keyboards-rg-0.3+nmu1/debian/format 2016-10-17 12:37:57.0 +
+++ keyboards-rg-0.3+nmu2/debian/format 1970-01-01 00:00:00.0 +
@@ -1 +0,0 @@
-3.0 (native)
diff -Nru keyboards-rg-0.3+nmu1/debian/source/format 
keyboards-rg-0.3+nmu2/debian/source/format
--- keyboards-rg-0.3+nmu1/debian/source/format  1970-01-01 00:00:00.0 
+
+++ keyboards-rg-0.3+nmu2/debian/source/format  2016-10-17 12:37:57.0 
+
@@ -0,0 +1 @@
+3.0 (native)

Bug#1067709: FTBFS in armel/armhf: some symbols disappeared

[Andrey Rakhmatullin]

Source: dante
Version: 1.4.3+dfsg-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=dante=armhf=1.4.3%2Bdfsg-1=1710761774=0

dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols
file: see diff output below
dpkg-gensymbols: warning: debian/libdsocksd0t64/DEBIAN/symbols doesn't match
completely debian/libdsocksd0t64.symbols
--- debian/libdsocksd0t64.symbols (libdsocksd0t64_1.4.3+dfsg-1_armhf)
+++ dpkg-gensymbolsuMr_d0   2024-03-18 11:36:08.476248857 +
@@ -8,16 +8,16 @@
  gethostbyname@Base 1.4.1+dfsg
  getpeername@Base 1.4.1+dfsg
  getsockname@Base 1.4.1+dfsg
- getsockopt@Base 1.4.1+dfsg
+#MISSING: 1.4.3+dfsg-1# getsockopt@Base 1.4.1+dfsg
  listen@Base 1.4.1+dfsg
  read@Base 1.4.1+dfsg
  readv@Base 1.4.1+dfsg
  recv@Base 1.4.1+dfsg
  recvfrom@Base 1.4.1+dfsg
- recvmsg@Base 1.4.1+dfsg
+#MISSING: 1.4.3+dfsg-1# recvmsg@Base 1.4.1+dfsg
  rresvport@Base 1.4.1+dfsg
  send@Base 1.4.1+dfsg
- sendmsg@Base 1.4.1+dfsg
+#MISSING: 1.4.3+dfsg-1# sendmsg@Base 1.4.1+dfsg
  sendto@Base 1.4.1+dfsg
  write@Base 1.4.1+dfsg
  writev@Base 1.4.1+dfsg


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

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

Bug#1067708: RFS: xz-utils/5.6.1-0.1 [NMU] -- XZ-format compression utilities

[Hans Jansen]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "xz-utils":

 * Package name : xz-utils
   Version  : 5.6.1-0.1
   Upstream contact : x...@tukaani.org
 * URL  : https://xz.tukaani.org/xz-utils/
 * License  : FSFUL, none, noderivs, permissive-nowarranty, 
LGPL-2.1+, CC-BY-SA-4.0, PD, 
GPL-3.0-or-later-WITH-Autoconf-exception-macro, 0BSD, GPL-2+, FSFULLR

 * Vcs  : https://salsa.debian.org/debian/xz-utils
   Section  : utils

The source builds the following binary packages:

  liblzma5 - XZ-format compression library
  liblzma5-udeb - XZ-format compression library
  xz-utils - XZ-format compression utilities
  xzdec - XZ-format compression utilities - tiny decompressors
  liblzma-dev - XZ-format compression library - development files
  liblzma-doc - XZ-format compression library - API documentation

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


  https://mentors.debian.net/package/xz-utils/

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

  dget -x 
https://mentors.debian.net/debian/pool/main/x/xz-utils/xz-utils_5.6.1-0.1.dsc


Changes since the last upload:

 xz-utils (5.6.1-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Import 5.6.1
   * Remove both patches, fixed in upstream.


This new version fixes a valgrind bug with liblzma that outputs a false 
warning that could affect existing testing frameworks for packages that 
test with valgrind requiring a specific output. This release only fixes 
bugs.



Regards,
--
  Hans Jansen

Bug#1067707: FTBFS: env: ‘-Wdate-time’: No such file or directory

[Andrey Rakhmatullin]

Source: gdb-avr
Version: 13.2-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=gdb-
avr=armhf=13.2-3%2Bb1=1710754002=0

cd build && env CC="gcc" CFLAGS="-v -Wno-error=unused-but-set-variable -Wno-
error=unused-but-set-parameter" CPPFLAGS=-D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2
../src/configure --host=arm-linux-gnueabihf --build=arm-linux-gnueabihf
--prefix=/usr --mandir='\${prefix}/share/man' --infodir='\${prefix}/share/info'
--target=avr --with-expat --disable-texinfo --with-system-zlib --with-
python=python3 ASFLAGS="" ASFLAGS_FOR_BUILD="" CFLAGS="-g -O2 -Werror=implicit-
function-declaration -ffile-prefix-map=/<>=. -fstack-protector-
strong -fstack-clash-protection -Wformat -Werror=format-security"
CFLAGS_FOR_BUILD="-g -O2" CPPFLAGS="-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2" CPPFLAGS_FOR_BUILD=""
CXXFLAGS="-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security"
CXXFLAGS_FOR_BUILD="-g -O2" DFLAGS="-frelease" DFLAGS_FOR_BUILD="-frelease"
FCFLAGS="-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection" FCFLAGS_FOR_BUILD="-g -O2" FFLAGS="-g -O2 -ffile-
prefix-map=/<>=. -fstack-protector-strong -fstack-clash-
protection" FFLAGS_FOR_BUILD="-g -O2" LDFLAGS="-Wl,-z,relro"
LDFLAGS_FOR_BUILD="" OBJCFLAGS="-g -O2 -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-
security" OBJCFLAGS_FOR_BUILD="-g -O2" OBJCXXFLAGS="-g -O2 -ffile-prefix-
map=/<>=. -fstack-protector-strong -fstack-clash-protection
-Wformat -Werror=format-security" OBJCXXFLAGS_FOR_BUILD="-g -O2"
env: ‘-Wdate-time’: No such file or directory


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

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

Bug#1050393: Unneeded dependency on "dconf-gsettings-backend | gsettings-backend"?

[Xiyue Deng]

Xiyue Deng  writes:

> Xiyue Deng  writes:
>
>> Control: tags -1 patch
>>
>> Hi,
>>
>> It looks like the gsettings-backend dependency was introduced since
>> Emacs 29.1.  Tried to debug this a little, and it looks like the
>> dependencies was pulled in through ${misc:Depends} due to the GSettings
>> schema file[1].  With helps from folks on IRC, we found that this file
>> was installed only in PGTK mode[2], so technically this is not required
>> by other modes and should be safe to be moved from emacs-common to
>> emacs-pgtk.
>>
>> I have prepared a MR[3] (patch also attached) as an attempt and verified
>> that it moved the "dconf-gsettings-backend | gsettings-backend" from
>> emacs-common to emacs-pgtk.  I'll try to use this locally with emacs-nox
>> to further verify that it doesn't cause any issues.
>>
>> Meanwhile, would be great to have people review the patch.  TIA!
>>
>> [1] Search for
>> "/usr/share/glib-2.0/schemas/org.gnu.emacs.defaults.gschema.xml" on
>> https://packages.debian.org/sid/all/emacs-common/filelist
>>
>> [2] 
>> https://salsa.debian.org/rlb/deb-emacs/-/blob/deb/emacs/d/sid/master/Makefile.in?ref_type=heads#L1334-1337
>>
>> [3] https://salsa.debian.org/rlb/deb-emacs/-/merge_requests/12
>
> I have made a few updates to the merge request, and please see the
> updated patch attached.  Do refer to the merge request[1] for the latest
> updates.
>
> [1] https://salsa.debian.org/rlb/deb-emacs/-/merge_requests/12

I have attached the refreshed patches after the release of 29.3+1-1.  TIA!

(Note that merge requests were closed so the salsa link is no longer valid.)

-- 
Xiyue Deng

>From 2ce769b9ea45d72ed54d6168875626b10c8e7321 Mon Sep 17 00:00:00 2001
From: Xiyue Deng 
Date: Wed, 13 Mar 2024 10:22:46 -0700
Subject: [PATCH] Install GSettings schema in pgtk build only (Closes:
 #1050393)

* In PGTK build it generates the GSettings schema file
"/usr/share/glib-2.0/schemas/org.gnu.emacs.defaults.gschema.xml" which
is not needed in other variant.
* Move the file from emacs-common to emacs-pgtk, and adds proper
breaks/replaces/conflicts to ensure a smooth upgrade.
---
 debian/changelog |  7 +++
 debian/control   | 12 ++--
 debian/rules |  9 -
 3 files changed, 25 insertions(+), 3 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 6ffab5c7af8..18c502de26d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+emacs (1:29.3+1-2) UNRELEASED; urgency=medium
+
+  * Team upload.
+  * Install GSettings schema in pgtk build only (Closes: #1050393)
+
+ -- Xiyue Deng   Wed, 13 Mar 2024 10:22:10 -0700
+
 emacs (1:29.3+1-1) unstable; urgency=high
 
   * Merge upstream version 29.3.  Thanks to David Bremner for the
diff --git a/debian/control b/debian/control
index e168717089f..0c6fab0bfeb 100644
--- a/debian/control
+++ b/debian/control
@@ -138,8 +138,15 @@ Provides: editor, emacs, emacsen, info-browser, mail-reader, news-reader
 Recommends: fonts-noto-color-emoji
 Suggests: emacs-common-non-dfsg
 Conflicts: emacs-gtk, emacs-lucid, emacs-nox
-Replaces: emacs-gtk, emacs-lucid, emacs-nox, emacs-bin-common (<< 1:29.2)
-Breaks: emacs-bin-common (<< 1:29.2)
+Replaces:
+ emacs-gtk,
+ emacs-lucid,
+ emacs-nox,
+ emacs-bin-common (<< 1:29.2),
+ emacs-common (<< 1:29.2+1-3~),
+Breaks:
+ emacs-bin-common (<< 1:29.2),
+ emacs-common (<< 1:29.2+1-3~),
 Description: GNU Emacs editor (with GTK+ Wayland GUI support)
  GNU Emacs is the extensible self-documenting text editor.  This
  package contains a version of Emacs with a graphical user interface
@@ -184,6 +191,7 @@ Breaks:
  emacs-gtk (<< 1:25),
  emacs-lucid (<< 1:25),
  emacs-nox (<< 1:25),
+ emacs-pgtk (<< 1:29.2+1-3~),
 Replaces:
  emacs-bin-common (<< 1:28)
 Description: GNU Emacs editor's shared, architecture independent infrastructure
diff --git a/debian/rules b/debian/rules
index 38965316f3d..8448d7c9be3 100755
--- a/debian/rules
+++ b/debian/rules
@@ -425,6 +425,9 @@ override_dh_auto_install: $(autogen_install_files)
 	  cp -a $(install_dir_pgtk)/* $(pkgdir_common)
 
 	  rm -r $(pkgdir_common)/usr/bin
+	  # PGTK builds a GSettings schema that is PGTK specific and
+	  # should not be shipped in emacs-common
+	  rm -r $(pkgdir_common)/usr/share/glib-2.0
 	  rm \
 	$(pkgdir_common)/$(libexec_dir_emacs)/hexl \
 	$(pkgdir_common)/$(libexec_dir_emacs)/emacs-*.pdmp \
@@ -548,7 +551,7 @@ override_dh_auto_install: $(autogen_install_files)
 
 ##
 # emacs-pgtk
-ifneq (,$(findstring emacs, $(shell dh_listpackages)))
+ifneq (,$(findstring emacs-pgtk, $(shell dh_listpackages)))
 	  $(call install_common_binpkg_bits,$(install_dir_pgtk),$(pkgdir_pgtk),emacs-pgtk,pgtk)
 
   # install desktop entries
@@ -557,6 +560,10 @@ override_dh_auto_install: $(autogen_install_files)
 	debian/emacs.desktop \
 	debian/emacs-term.desktop \
 	$(pkgdir_pgtk)/usr/share/applications/
+	  # install GSettings schema
+	  install 

Bug#1067706: O: python-isoweek -- Python module to provide the class Week (Python 3)

[Boyuan Yang]

Package: wnpp
Control: affects -1 + src:python-isoweek
X-Debbugs-Cc: python-isow...@packages.debian.org
Severity: normal

I intend to orphan the python-isoweek package. Its upstream is no longer
active, and it may should be removed later.

The package description is:
 The isoweek Python module provide the class Week. Instances
 represent specific weeks spanning Monday to Sunday. There are 52 or 53
 numbered weeks in a year. Week 1 is defined to be the first week with 4
 or more days in January.

Thanks,
Boyuan Yang



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

Bug#1067705: src:siridb-server: flaky autopkgtest: curl: (7) Failed to connect to localhost port 9020 after 0 ms: Couldn't connect to server

[Paul Gevers]

Source: siridb-server
Version: 2.0.51-2
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of your package. I noticed 
that it regularly fails. From a distance, this looks like a race 
condition. Should the test ensure the server is started?


Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

[1] https://ci.debian.net/packages/s/siridb-server/testing/amd64/44324499/

 19s autopkgtest [11:10:05]: test http-api: [---
 19s * fixing /etc/siridb/siridb.conf
 19s * restarting siridb-server
 19s * run queries
 19s   get-version
 19s curl: (7) Failed to connect to localhost port 9020 after 0 ms: 
Couldn't connect to server

 19s cat: res.txt: No such file or directory
 19s autopkgtest [11:10:05]: test http-api: ---]


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1007459: hp-ppd: please consider upgrading to 3.0 source format

[Bastian Germann]

I am uploading a NMU to DELAED/10 in order to fix this.
Please find the debdiff attached.diff -Nru hp-ppd-0.9+nmu1/debian/README.debian 
hp-ppd-0.9+nmu2/debian/README.debian
--- hp-ppd-0.9+nmu1/debian/README.debian2020-12-17 09:06:58.0 
+
+++ hp-ppd-0.9+nmu2/debian/README.debian1970-01-01 00:00:00.0 
+
@@ -1,9 +0,0 @@
-hp-ppd for Debian
---
-
-from http://www.linuxprinting.org/download/PPD/HP/
-
-licensed as  MIT open source license -- see www.opensource.org
-
-
-A Mennucc1 , Fri Jan 30 15:21:54 CET 2004
diff -Nru hp-ppd-0.9+nmu1/debian/changelog hp-ppd-0.9+nmu2/debian/changelog
--- hp-ppd-0.9+nmu1/debian/changelog2020-12-17 09:06:58.0 +
+++ hp-ppd-0.9+nmu2/debian/changelog2024-03-25 19:45:21.0 +
@@ -1,3 +1,12 @@
+hp-ppd (0.9+nmu2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop README.debian with redundant information.
+  * Drop misleading sentence from description (Closes: #715806).
+  * Convert to source format 3.0 (Closes: #1007459).
+
+ -- Bastian Germann   Mon, 25 Mar 2024 19:45:21 +
+
 hp-ppd (0.9+nmu1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru hp-ppd-0.9+nmu1/debian/control hp-ppd-0.9+nmu2/debian/control
--- hp-ppd-0.9+nmu1/debian/control  2020-12-17 09:06:58.0 +
+++ hp-ppd-0.9+nmu2/debian/control  2024-03-25 19:45:21.0 +
@@ -18,6 +18,3 @@
  A PPD (PostScript Printer Definitions) specify the device specific
  PostScript commands needed to utilize printer features (such as 
  printing quality, paper tray, duplex printing).
- .
- This package contains some PPDs for HP printers that are not in
- package linuxprinting.org-ppds
diff -Nru hp-ppd-0.9+nmu1/debian/copyright hp-ppd-0.9+nmu2/debian/copyright
--- hp-ppd-0.9+nmu1/debian/copyright2020-12-17 09:06:58.0 +
+++ hp-ppd-0.9+nmu2/debian/copyright2024-03-25 19:45:21.0 +
@@ -1,36 +1,30 @@
-This package was debianized by A Mennucc1 deb...@tonelli.sns.it on
-Wed,  4 Jul 2001 12:13:16 +0200.
-
-It was downloaded from sourceforge.net/projects/lpr
-
-and successively from http://www.linuxprinting.org/download/PPD/HP/
-
-Copyright:
-
-
-*% =
-*% Adobe Systems PostScript(R) Printer Description File
-*% Copyright 1999 Hewlett-Packard Company.
-
-*%
-*% Permission is hereby granted, free of charge, to any person obtaining
-*% a copy of this software and associated documentation files (the
-*% "Software"), to deal in the Software without restriction, including
-*% without limitation the rights to use, copy, modify, merge, publish,
-*% distribute, sublicense, and/or sell copies of the Software, and to
-*% permit persons to whom the Software is furnished to do so, subject to
-*% the following conditions:
-*%
-*% The above copyright notice and this permission notice shall be
-*% included in all copies or substantial portions of the Software.
-*%
-*% THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-*% EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-*% MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
-*% NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
-*% LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
-*% OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
-*%
-*% [this is the MIT open source license -- see www.opensource.org]
-*%
-
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Comment:
+ This package was debianized by A Mennucc1 deb...@tonelli.sns.it on
+ Wed,  4 Jul 2001 12:13:16 +0200.
+Source:
+ https://sourceforge.net/projects/lpr
+ successively from http://www.linuxprinting.org/download/PPD/HP/
+
+Files: *
+Comment: Adobe Systems PostScript(R) Printer Description File
+Copyright: Copyright 1999 Hewlett-Packard Company.
+License: Expat
+ Permission is hereby granted, free of charge, to any person obtaining
+ a copy of this software and associated documentation files (the
+ "Software"), to deal in the Software without restriction, including
+ without limitation the rights to use, copy, modify, merge, publish,
+ distribute, sublicense, and/or sell copies of the Software, and to
+ permit persons to whom the Software is furnished to do so, subject to
+ the following conditions:
+ .
+ The above copyright notice and this permission notice shall be
+ included in all copies or substantial portions of the Software.
+ .
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+ EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+ MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+ NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+ LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+ OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+ WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
diff -Nru 

Bug#1067704: aptitude manual displayed in iso-8859-1 instead of utf-8 in help tab

[H.-R. Oberhage]

Package: aptitude
Version: 0.8.13-6

Hello, contrary to the message in NEWS:

[2018-07-29]
Version 0.8.11
[...]
- Documentation:

  * Change en/README_encoding to use utf-8 as all the other languages, 
instead

of iso-8859-1

this problem is not solved.
Within aptitude in tab "Help -> User's Manual" the manual is not(!)
shown in utf-8, but (most likely) iso-8859-1.
The culprit part seems to be the file src/ui.cc in function

do_help_readme()

in lines 1184 and especially 1190, where "ISO_8859-1" should by replaced
by "UTF-8".

I'm a big fan of aptitude, so all the best!
Thanks.

Bug#1066973: reverse dependencies

[Thorsten Alteholz]

Control: tags -1 + moreinfo

Hi Drew,

there are reverse dependencies that need to be taken care of:


Checking reverse dependencies...
# Broken Depends:
python-emmet-core: python3-emmet-core
python-mp-api: python3-mp-api

# Broken Build-Depends:
custodian: python3-pymatgen
python-emmet-core: python3-pymatgen (2023.5.8~ >=)
python-mp-api: python3-pymatgen (2022.3.7~ >=)
xraylarch: python3-pymatgen

Dependency problem found.


In case they matter, this needs to be addressed first. Please remove the 
moreinfo tag once that is done.


  Thorsten

Bug#1065623: reverse dependencies

[Thorsten Alteholz]

Control: tags -1 + moreinfo

Hi,

there are reverse dependencies that need to be taken care of:


Checking reverse dependencies...
# Broken Depends:
baresip: baresip-x11

# Broken Build-Depends:
baresip: libomxil-bellagio-dev
kodi: libomxil-bellagio-dev
vlc: libomxil-bellagio-dev


In case they matter, this needs to be addressed first. Please remove the 
moreinfo tag once that is done.


  Thorsten

Bug#1007683: fortunes-bg: please consider upgrading to 3.0 source format

[Bastian Germann]

I am uploading a NMU to DELAYED/10 in order to fix this.
Please find the debdiff attached.diff -Nru fortunes-bg-1.4/changelog fortunes-bg-1.4+nmu1/changelog
--- fortunes-bg-1.4/changelog   2021-12-27 15:07:15.0 +
+++ fortunes-bg-1.4+nmu1/changelog  2024-03-25 19:02:15.0 +
@@ -1,3 +1,11 @@
+fortunes-bg (1.4+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Convert to source format 3.0, closes: #1007683.
+  * d/copyright: Convert to machine-readable format.
+
+ -- Bastian Germann   Mon, 25 Mar 2024 19:02:15 +
+
 fortunes-bg (1.4) unstable; urgency=medium
 
   * debian/rules: add build-indep and build-arch targets, closes: #999302.
diff -Nru fortunes-bg-1.4/copyright fortunes-bg-1.4+nmu1/copyright
--- fortunes-bg-1.4/copyright   2021-12-27 15:07:15.0 +
+++ fortunes-bg-1.4+nmu1/copyright  2024-03-25 19:02:15.0 +
@@ -1,276 +1,17 @@
-Copyright (C) 2004 Anton Zinoviev
-
-This package (fortunes-bg) is free software; you can redistribute it
-and/or modify it under the terms of the GNU General Public License as
-published by the Free Software Foundation; either version 1 of the
-License, or (at your option) any later version.
-
-This program is distributed in the hope that it will be useful,
-but WITHOUT ANY WARRANTY; without even the implied warranty of
-MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-GNU General Public License for more details.
-
-The complete text of the GNU General Public License follows:
-
-
- GNU GENERAL PUBLIC LICENSE
-
-   Version 1, February 1989
-
- Copyright (C) 1989 Free Software Foundation, Inc.
- 51 Franklin St, Fifth Floor, Boston, MA  02110-1301 USA
-
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
-Preamble
-
-
-   The license agreements of most software companies try to keep users
-at the mercy of those companies.  By contrast, our General Public
-License is intended to guarantee your freedom to share and change free
-software--to make sure the software is free for all its users.  The
-General Public License applies to the Free Software Foundation's
-software and to any other program whose authors commit to using it.
-You can use it for your programs, too.
-
-   When we speak of free software, we are referring to freedom, not
-price.  Specifically, the General Public License is designed to make
-sure that you have the freedom to give away or sell copies of free
-software, that you receive source code or can get it if you want it,
-that you can change the software or use pieces of it in new free
-programs; and that you know you can do these things.
-
-   To protect your rights, we need to make restrictions that forbid
-anyone to deny you these rights or to ask you to surrender the rights.
-These restrictions translate to certain responsibilities for you if you
-distribute copies of the software, or if you modify it.
-
-   For example, if you distribute copies of a such a program, whether
-gratis or for a fee, you must give the recipients all the rights that
-you have.  You must make sure that they, too, receive or can get the
-source code.  And you must tell them their rights.
-
-   We protect your rights with two steps: (1) copyright the software,
-and (2) offer you this license which gives you legal permission to copy,
-distribute and/or modify the software.
-
-   Also, for each author's protection and ours, we want to make certain
-that everyone understands that there is no warranty for this free
-software.  If the software is modified by someone else and passed on, we
-want its recipients to know that what they have is not the original, so
-that any problems introduced by others will not reflect on the original
-authors' reputations.
-
-   The precise terms and conditions for copying, distribution and
-modification follow.
-
- TERMS AND CONDITIONS
-
-  1. This License Agreement applies to any program or other work which
- contains a notice placed by the copyright holder saying it may be
- distributed under the terms of this General Public License.  The
- "Program", below, refers to any such program or work, and a "work
- based on the Program" means either the Program or any work
- containing the Program or a portion of it, either verbatim or with
- modifications.  Each licensee is addressed as "you".
-
-  2. You may copy and distribute verbatim copies of the Program's source
- code as you receive it, in any medium, provided that you
- conspicuously and appropriately publish on each copy an
- appropriate copyright notice and disclaimer of warranty; keep
- intact all the notices that refer to this General Public License
- and to the absence of any warranty; and give any other recipients
- of the Program a copy of this General Public License along with
- the Program.  You may 

Bug#1063951: fixed in barectf 3.1.2-2

[Michael Jeanson]

On 2024-03-24 18:28, Timo Röhling wrote:

Control: reopen -1
Control: notfixed -1 3.1.2-2

On Fri, 15 Mar 2024 21:44:05 + Debian FTP Masters 
 wrote:

   * [2375fb4] Disable pytest8 deprecation warnings (Closes:    #1063951)
 - Also (Closes: #1066742) built with pytest8
Unfortunately, this was not a permanent solution, because the features which 
PytestRemovedIn8Warning has been warning about, have been actually removed now 
(pytest 8.1).



Cheers
Timo




They seem to have renamed 'PytestRemovedIn8Warning' to
'PytestRemovedIn9Warning' and we can't ignore a non-existent exception
type without generating an error. When I remove it from the ignore list and 
just keep the 2 DeprecationWarning types, I can successfully run the test 
suite with pytest 8.1.1.


I'll go for this until upstream adds support for pytest8.

Michael

Bug#1067702: Explicit Depends: libqt5core5a needs to be updated for the time64 transition

[Andrey Rakhmatullin]

Source: anki
Version: 2.1.15+dfsg-4
Severity: serious

The package has Depends: libqt5core5a in d/control, this needs to be updated to
libqt5core5t64 if this explicit dep is needed at all.


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

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

Bug#1066938: Fwd: Bug#1066938: libfiu: FTBFS on arm{el,hf}: /tmp/cc54dEva.s:726: Error: symbol `open64' is already defined

[Chris Lamb]

Alberto Bertogli wrote:

> If you know of a functional official image that I can use to try to
> reproduce the problem, or recently-tested steps I can follow to get
> a working qemu install, please let me know.

Alas, I can't actually be helpful here. There are no official images
as far as I know… and somewhat annoyingly I (ie. a Debian Developer)
actually have access to some machines set aside for this purpose. I
call this "annoying" because I naturally can't then give you direct
SSH access transitively — but I can proxy ideas, of course.

Hm, googling the actual error message a little, I think this might be
a bigger issue... or perhaps more accurately, at least one that has
potentially been also solved elsewhere:

  * Same think in lightdm: 

  * Some kind of "_FILE_OFFSET_BITS"-related patch for v4l-utils


etc.

Does this spark anything worth trying? :-)


Regards,

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

Bug#1065131: electron: GPU process crash with AMDGPU, ac: Unknown GPU, using 0 for raster_config

[Fabio Pedretti]

Version: 24.0.3-1+b1

Great, they belong to the same source package and should be both upgraded.
Closing.

> With mesa-va-drivers:amd64 24.0.3-1+b1 and libgl1-mesa-dri:amd64
> 23.3.3-3, the result is the same.
>
> But with also updating libgl1-mesa-dri:amd64 to 24.0.3-1+b1, the issue
> is fixed.

Bug#1066110: tracker-extract: regular crash

[Patrice Duroux]

forcemerge 1066898 1066110
thanks

It is fixed on my side and looking at #1066898 it seems to me to be a
duplicate of my report.

Le lun. 25 mars 2024 à 15:35, Alban Browaeys
 a écrit :
>
> On Thu, 21 Mar 2024 20:51:23 +0100 Patrice Duroux
>  wrote:
> > So did a forcemerge 1066898 1066110 be a better way to proceed?
> >
>
>
> Yes, that would be fine too as far as I know (I am not a Debian
> Developer).
> I believe it will then close this bug report too.
>
> By the way I think your question implies that this bug is fixed by
> 3.7.0-1, isn't it?
>
> Cheers,
> Alban
>
> > Le jeu. 21 mars 2024 à 10:40, Alban Browaeys
> >  a écrit :
> > >
> > > On Thu, 14 Mar 2024 22:04:33 +0100 intrigeri 
> > > wrote:
> > > > Hi,
> > > >
> > > > I see a similar crash every 2-4 seconds on my sid system since
> some
> > > recent
> > > > upgrade.
> > > >
> > > > This looks like
> > > > https://gitlab.gnome.org/GNOME/tracker-miners/-/issues/312.
> > > >
> > >
> > >
> > > Looks like
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066898
> > >
> > > > I lack time to do this myself but it could be interesting to
> check if
> > > > the upstream fix resolves this for you:
> > > >
> > >
> https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/516/diffs
> > > > … which I understand will be included in 3.7 stable.
> > > >
> > >
> > >
> > > Should be fixed by 3.7.0-1 which is available in unstable since a
> day.
> > > Could you upgrade and clos this bug report if fixed?
> > >
> > > Regards,
> > > Alban
> >
> >
>

Bug#1065131: electron: GPU process crash with AMDGPU, ac: Unknown GPU, using 0 for raster_config

[Alexis Murzeau]

Hi,

On 17/03/2024 12:15 PM, Fabio Pedretti wrote:

Can you try again with 24.0.3-1 ?
Thanks.



With mesa-va-drivers:amd64 24.0.3-1+b1 and libgl1-mesa-dri:amd64 
23.3.3-3, the result is the same.


But with also updating libgl1-mesa-dri:amd64 to 24.0.3-1+b1, the issue 
is fixed.


Other packages were upgraded too, so maybe this is another one that 
fixed the issue, here is the complete list:

[UPGRADE] libd3dadapter9-mesa:amd64 24.0.1-1 -> 24.0.3-1+b1
[UPGRADE] libd3dadapter9-mesa:i386 24.0.1-1 -> 24.0.3-1+b1
[UPGRADE] libegl-mesa0:amd64 23.3.3-3 -> 24.0.3-1+b1
[UPGRADE] libegl-mesa0:i386 23.3.3-3 -> 24.0.3-1+b1
[UPGRADE] libgbm-dev:amd64 23.3.3-3 -> 24.0.3-1+b1
[UPGRADE] libgbm1:amd64 23.3.3-3 -> 24.0.3-1+b1
[UPGRADE] libgbm1:i386 23.3.3-3 -> 24.0.3-1+b1
[UPGRADE] libgl1-mesa-dri:amd64 23.3.3-3 -> 24.0.3-1+b1
[UPGRADE] libgl1-mesa-dri:i386 23.3.3-3 -> 24.0.3-1+b1
[UPGRADE] libglapi-mesa:amd64 23.3.3-3 -> 24.0.3-1+b1
[UPGRADE] libglapi-mesa:i386 23.3.3-3 -> 24.0.3-1+b1
[UPGRADE] libglx-mesa0:amd64 23.3.3-3 -> 24.0.3-1+b1
[UPGRADE] libglx-mesa0:i386 23.3.3-3 -> 24.0.3-1+b1
[UPGRADE] mesa-vulkan-drivers:amd64 24.0.1-1 -> 24.0.3-1+b1
[UPGRADE] mesa-vulkan-drivers:i386 24.0.1-1 -> 24.0.3-1+b1

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



OpenPGP_0xE7BD1904F480937F.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1067697: Update Build-Depends for the time64 library renames

[Thomas Ward]

For everyone's awareness: this same t64 transition is going on downstream in 
Ubuntu, and I'm also tracing rebuilds, etc. with changed dependencies there as 
well which are being done by other core devs there, so those changes may 
trickle back up into Debian here.


Thomas

(this email is the one behind my @ubuntu.com address)

Bug#1067564: bookworm-pu: package cpu/1.4.3-14~deb12u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Sat, 2024-03-23 at 18:40 +0100, Andreas Beckmann wrote:
> The last QA upload four years ago fixed a FTBFS (multiple definitions
> of
> a global variable) by replacing that variable with an extern
> declaration
> and zero definitions. This didn't result in a linker error (missing
> symbol) because it happens in a plugin library and thus is only
> detected
> at runtime when the plugin gets loaded (i.e. always).

Oh dear...

Please go ahead.

Regards,

Adam

Bug#1067149: bookworm-pu: package hovercraft/2.7-6~deb12u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Tue, 2024-03-19 at 12:03 +0100, Andreas Beckmann wrote:
> hovercraft is unusable w/o python3-setuptools
> 
> [ Impact ]
> hovercraft is unusable without manual installation of additional
> packages.

Please go ahead.

Regards,

Adam

Bug#1066096: bookworm-pu: package libpod/4.3.1+ds1-8+deb12u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Tue, 2024-03-12 at 10:24 -0400, Jérôme Charaoui wrote:
> podman in bookworm suffers from a race condition which causes the 
> "network ls" command to fail intermittently in certain scenarios

Please go ahead.

Regards,

Adam

Bug#1065052: nvidia-graphics-drivers-tesla-470 470.239.06-1~deb12u1 flagged for acceptance

[Adam D Barratt]

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

Hi,

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

Thanks for your contribution!

Upload details
==

Package: nvidia-graphics-drivers-tesla-470
Version: 470.239.06-1~deb12u1

Explanation: new upstream stable release; improve compatibility with newer 
kernel versions; security fixes [CVE-2022-42265 CVE-2024-0074 CVE-2024-0078]

Bug#1067697: Update Build-Depends for the time64 library renames

[Andrey Rakhmatullin]

On Mon, Mar 25, 2024 at 06:55:22PM +, Thomas Ward wrote:
> The only package that has a changed name that I can see is `libqt5sql5` to 
> `libqt5sql5t64`.  I have already put this in the revisions in Salsa at the 
> moment.
> 
> If `libqt5help5` has a rename pending to `libqt5help5t64` and that's not yet 
> in Unstable, then I can't make that revision safely.
You are right, libqt5help5 won't be renamed.
Thanks.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#1065653: bookworm-pu: package nvidia-modprobe/535.161.07-1~deb12u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Fri, 2024-03-08 at 09:42 +0100, Andreas Beckmann wrote:
> In preparation to switching bookworm from the nvidia-graphics-drivers
> 525.* series (production branch, EoL) to the 535.* series (long term
> support branch, receives updates until July 2026), we need to update
> nvidia-modprobe again. We already have a 535 release in bookworm, but
> there was recently a new option being added.

Please go ahead.

Regards,

Adam

Bug#1067697: Update Build-Depends for the time64 library renames

[Thomas Ward]

The only package that has a changed name that I can see is `libqt5sql5` to 
`libqt5sql5t64`.  I have already put this in the revisions in Salsa at the 
moment.

If `libqt5help5` has a rename pending to `libqt5help5t64` and that's not yet in 
Unstable, then I can't make that revision safely.



Thomas

-Original Message-
From: Andrey Rakhmatullin  
Sent: Monday, March 25, 2024 14:00
To: Debian Bug Tracking System 
Subject: Bug#1067697: Update Build-Depends for the time64 library renames

Source: xca
Version: 2.5.0-1
Severity: serious

The package explicitly Build-Depends: libqt5sql5, libqt5help5, this needs to be 
changed to the new names if it's needed at all.


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

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

Bug#1065264: bookworm-pu: package phpseclib/1.0.20-1+deb12u2

[Adam D. Barratt]

Control: tags -1 + confirmed

On Sat, 2024-03-02 at 11:19 +0100, David Prévot wrote:
> I’d like to see CVE-2024-27354 and CVE-2024-27355 addressed in the
> next
> point release. We agreed with the security team that these issues are
> not worth a DSA. This update also fixes an issue in dependency
> loading
> similar to CVE-2024-24821 as fixed in composer/DSA-5632-1.
> 

Please go ahead.

Regards,

Adam

Bug#1066377: argtable2: FTBFS: arg_int.c:60:12: error: implicit declaration of functions

[Étienne Mollier]

Control: tag -1 + patch

Hi Shachar,

I wrapped up a patch to resolve #1066377, the recently caught
build failure affecting argtable2.  You will find the diff in
attachment.

Hope this helps,
-- 
  .''`.  Étienne Mollier 
 : :' :  pgp: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/2, please excuse my verbosity
   `-
Description: fix multiple implicit function declarations.
Author: Étienne Mollier 
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066377
Forwarded: no
Last-Update: 2024-03-25
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- argtable2-13.orig/src/arg_int.c
+++ argtable2-13/src/arg_int.c
@@ -29,6 +29,7 @@
 /* #endif */
 
 #include "argtable2.h"
+#include 
 #include 
 
 /* local error codes */
--- argtable2-13.orig/tests/fntests.c
+++ argtable2-13/tests/fntests.c
@@ -1,5 +1,6 @@
 #include "../src/argtable2.h"
 #include 
+#include 
 
 /* for memory leak debugging */
 #ifdef DMALLOC
--- argtable2-13.orig/tests/test_file.c
+++ argtable2-13/tests/test_file.c
@@ -21,6 +21,7 @@
 
 #include "../src/argtable2.h"
 #include 
+#include 
 
 /* for memory leak debugging */
 #ifdef DMALLOC


signature.asc
Description: PGP signature

Bug#1065263: bookworm-pu: package php-phpseclib/2.0.42-1+deb12u2

[Adam D. Barratt]

Control: tags -1 + confirmed

On Sat, 2024-03-02 at 11:17 +0100, David Prévot wrote:
> I’d like to see CVE-2024-27354 and CVE-2024-27355 addressed in the
> next
> point release. We agreed with the security team that these issues are
> not worth a DSA.

Please go ahead.

Regards,

Adam

Bug#1065261: bookworm-pu: package php-phpseclib3/3.0.19-1+deb12u3

[Adam D. Barratt]

Control: tags -1 + confirmed

On Sat, 2024-03-02 at 11:15 +0100, David Prévot wrote:
> I’d like to see CVE-2024-27354 and CVE-2024-27355 addressed in the
> next
> point release. We agreed with the security team that these issues are
> not worth a DSA. This update also fixes an issue in dependency
> loading
> similar to CVE-2024-24821 as fixed in composer/DSA-5632-1.

Please go ahead.

Regards,

Adam

Bug#1065068: bookworm-pu: package php-doctrine-deprecations/1.0.0-2+deb12u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Thu, 2024-02-29 at 12:12 +0100, David Prévot wrote:
> This is a follow up from composer/DSA-5632-1 (the last one for
> Bookworm).
> 
> In order to fix a Debian-specific issue related to CVE-2024-24821, we
> agreed with the security team to push related dependencies via the
> next
> point release.

Please go ahead.

Regards,

Adam

Bug#1065067: bookworm-pu: package php-doctrine-lexer/2.1.0-2+deb12u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Thu, 2024-02-29 at 12:08 +0100, David Prévot wrote:
> This is a follow up from composer/DSA-5632-1.
> 
> In order to fix a Debian-specific issue related to CVE-2024-24821, we
> agreed with the security team to push related dependencies via the
> next
> point release.

Again the branch name probably wants adjusting.

Please go ahead.

Regards,

Adam

Bug#1065065: bookworm-pu: package php-doctrine-annotations/2.0.1-1+deb12u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Thu, 2024-02-29 at 12:05 +0100, David Prévot wrote:
> This is a follow up from composer/DSA-5632-1.
> 
> In order to fix a Debian-specific issue related to CVE-2024-24821, we
> agreed with the security team to push related dependencies via the
> next
> point release.

Please go ahead.

Regards,

Adam

Bug#1065062: bookworm-pu: package php-zend-code/4.8.0-1+deb12u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Thu, 2024-02-29 at 11:58 +0100, David Prévot wrote:
> This is a follow up from composer/DSA-5632-1.
> 
> In order to fix a Debian-specific issue related to CVE-2024-24821, we
> agreed with the security team to push related dependencies via the
> next
> point release.

Please go ahead.

Regards,

Adam

Bug#1065060: bookworm-pu: package php-proxy-manager/2.11.1+1.0.14-1+deb12u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Thu, 2024-02-29 at 11:50 +0100, David Prévot wrote:
> This is a follow up from composer/DSA-5632-1.
> 
> In order to fix a Debian-specific issue related to CVE-2024-24821, we
> agreed with the security team to push related dependencies via the
> next
> point release.

Please go ahead.

Regards,

Adam

Bug#1065059: bookworm-pu: package symfony/5.4.23+dfsg-1+deb12u2

[Adam D. Barratt]

Control: tags -1 + confirmed

On Thu, 2024-02-29 at 11:54 +0100, David Prévot wrote:
> Hi,
> 
> Le Thu, Feb 29, 2024 at 11:40:25AM +0100, David Prévot a écrit :
> >   [x] attach debdiff against the package in (old)stable
> 
> Now it’s true.

Please go ahead.

Regards,

Adam

Bug#1007066: dh-buildinfo: please consider upgrading to 3.0 source format

[Bastian Germann]

I am uploading a NMU to DELAYED/10 in order to fix this.
Please find the debdiff attached.diff -Nru dh-buildinfo-0.11+nmu2/.dh-buildinfo.prcs_aux 
dh-buildinfo-0.11+nmu3/.dh-buildinfo.prcs_aux
--- dh-buildinfo-0.11+nmu2/.dh-buildinfo.prcs_aux   2006-12-17 
15:38:14.0 +
+++ dh-buildinfo-0.11+nmu3/.dh-buildinfo.prcs_aux   1970-01-01 
00:00:00.0 +
@@ -1,21 +0,0 @@
-;; This file is automatically generated, editing may cause PRCS to do
-;; REALLY bad things.
-(Created-By-Prcs-Version 1 3 3)
-(debian/rules 1400 1139951704 6_rules 1.5)
-(debian/copyright 267 1057481110 4_copyright 1.1)
-(stats/lib/buildinfo-nb-files.gnuplot 232 1063198995 17_buildinfo- 1.2)
-(debian/compat 2 1057480823 5_compat 1.1)
-(stats/bin/check-buildinfo 1342 1166365617 10_check-buil 1.10)
-(stats/bin/fetch-buildinfo 2227 1063746792 13_fetch-buil 1.8)
-(private/upload 325 1063197804 12_upload 1.3)
-(stats/check-buildinfo 779 1060110460 10_check-buil 1.2)
-(stats/bin/buildinfo-packagetable 6206 1166369620 14_buildinfo- 1.2.1.17)
-(dh_buildinfo 7809 1073568157 2_dh_buildin 1.7)
-(debian/changelog 2925 1139952038 7_changelog 1.15)
-(stats/buildinfo-nb.gnuplot 221 1060032012 11_buildinfo- 1.1)
-(stats/lib/buildinfo-nb.gnuplot 221 1063198978 11_buildinfo- 1.2)
-(BuildDeps.pm 4814 1003610400 0_BuildDeps. 1.1)
-(dpkg-checkbuilddeps 4005 1003445118 1_dpkg-check 1.1)
-(buildinfo.html 26038 1063741835 9_buildinfo. 1.23)
-(debian/control 895 1073567609 8_control 1.6)
-(Makefile.PL 174 1139951911 3_Makefile.P 1.3)
diff -Nru dh-buildinfo-0.11+nmu2/debian/changelog 
dh-buildinfo-0.11+nmu3/debian/changelog
--- dh-buildinfo-0.11+nmu2/debian/changelog 2018-01-10 21:28:27.0 
+
+++ dh-buildinfo-0.11+nmu3/debian/changelog 2024-03-25 18:37:09.0 
+
@@ -1,3 +1,12 @@
+dh-buildinfo (0.11+nmu3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * d/copyright: Convert to machine-readable format.
+  * Convert to source format 3.0 (Closes: #1007066).
+  * Drop versioned B-D on build-essential.
+
+ -- Bastian Germann   Mon, 25 Mar 2024 18:37:09 +
+
 dh-buildinfo (0.11+nmu2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru dh-buildinfo-0.11+nmu2/debian/control 
dh-buildinfo-0.11+nmu3/debian/control
--- dh-buildinfo-0.11+nmu2/debian/control   2018-01-10 21:00:16.0 
+
+++ dh-buildinfo-0.11+nmu3/debian/control   2024-03-25 18:37:09.0 
+
@@ -1,7 +1,7 @@
 Source: dh-buildinfo
 Section: devel
 Priority: optional
-Build-Depends-Indep: perl, build-essential (>= 7)
+Build-Depends-Indep: perl
 Build-Depends: debhelper (>= 9)
 Maintainer: Yann Dirson 
 Rules-Requires-Root: no
diff -Nru dh-buildinfo-0.11+nmu2/debian/copyright 
dh-buildinfo-0.11+nmu3/debian/copyright
--- dh-buildinfo-0.11+nmu2/debian/copyright 2003-07-06 08:45:10.0 
+
+++ dh-buildinfo-0.11+nmu3/debian/copyright 2024-03-25 18:37:02.0 
+
@@ -1,5 +1,10 @@
-This is the debian package for dh-buildinfo.  It was initially created
-by Yann Dirson  using dh-make-perl.
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Comment:
+ This is the debian package for dh-buildinfo.  It was initially created
+ by Yann Dirson  using dh-make-perl.
 
-This package is covered by the GNU General Public Licence, version 2.
-On Debian systems, you'll find it in /usr/share/common-licenses/GPL-2
+Files: *
+Copyright: 2001 Yann Dirson 
+License: GPL-2
+ This package is covered by the GNU General Public Licence, version 2.
+ On Debian systems, you'll find it in /usr/share/common-licenses/GPL-2
diff -Nru dh-buildinfo-0.11+nmu2/debian/source/format 
dh-buildinfo-0.11+nmu3/debian/source/format
--- dh-buildinfo-0.11+nmu2/debian/source/format 1970-01-01 00:00:00.0 
+
+++ dh-buildinfo-0.11+nmu3/debian/source/format 2024-03-25 18:37:09.0 
+
@@ -0,0 +1 @@
+3.0 (native)

Bug#1065058: bookworm-pu: package php-symfony-contracts/2.5.2-1+deb12u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Thu, 2024-02-29 at 11:31 +0100, David Prévot wrote:
> This is a follow up from composer/DSA-5632-1, #1065056 and #1065057.
> 
> In order to fix a Debian-specific issue related to CVE-2024-24821, we
> agreed with the security team to push related dependencies via the
> next
> point release.

Please go ahead.

Regards,

Adam

Bug#1067701: FTBFS: _TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64

[Andrey Rakhmatullin]

Source: erlang
Version: 1:25.3.2.10+dfsg-1
Severity: serious
Tags: ftbfs


https://buildd.debian.org/status/fetch.php?pkg=erlang=armhf=1%3A25.3.2.10%2Bdfsg-1=1711383511=0

arm-linux-gnueabihf-gcc -Werror=undef -Werror=implicit -Werror=return-type
-fno-strict-aliasing -fno-common -g -O2 -fno-strict-aliasing
-I/<>/erts/arm-unknown-linux-gnueabihf  -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64  -D_GNU_SOURCE  -DHAVE_CONFIG_H -Wall -Wstrict-
prototypes -Wpointer-arith -Wmissing-prototypes -Wdeclaration-after-statement
-DUSE_THREADS -D_THREAD_SAFE -D_REENTRANT -DPOSIX_THREADS
-D_POSIX_THREAD_SAFE_FUNCTIONS   -Iarm-unknown-linux-gnueabihf/opt/emu -Ibeam
-Isys/unix -Isys/common -Iarm-unknown-linux-gnueabihf -Ipcre -Iryu
-Iopenssl/include -I../include -I../include/arm-unknown-linux-gnueabihf
-I../include/internal -I../include/internal/arm-unknown-linux-gnueabihf -c
sys/unix/sys_time.c -o obj/arm-unknown-linux-gnueabihf/opt/emu/sys_time.o
In file included from /usr/include/features.h:393,
 from /usr/include/arm-linux-gnueabihf/bits/libc-header-
start.h:33,
 from /usr/include/stdlib.h:26,
 from sys/unix/sys_time.c:35:
/usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed
only with _FILE_OFFSET_BITS=64"
   26 | #   error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"
  | ^


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

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

Bug#1067700: nmu: nfs-utils_1:2.6.4-3

[Andrey Rakhmatullin]

Package: release.debian.org
Severity: normal
X-Debbugs-Cc: nfs-ut...@packages.debian.org
Control: affects -1 + src:nfs-utils
User: release.debian@packages.debian.org
Usertags: binnmu

nmu nfs-utils_1:2.6.4-3 . ANY . unstable . -m "Rebuild for time_t"

Bug#1065057: bookworm-pu: package php-composer-xdebug-handler/3.0.3-2+deb12u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Thu, 2024-02-29 at 11:18 +0100, David Prévot wrote:
> This is a follow up from composer/DSA-5632-1.
> 
> In order to fix a Debian-specific issue related to CVE-2024-24821, we
> agreed with the security team to push related dependencies via the
> next
> point release.

+  * Track debian/bookworm-security

Even though this update isn't going to the security archive?

Please go ahead.

Regards,

Adam

Bug#1065056: bookworm-pu: package php-composer-class-map-generator/1.0.0-2+deb12u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Thu, 2024-02-29 at 11:10 +0100, David Prévot wrote:
> [1/9 for bookworm]
> 
> This is a follow up from composer/DSA-5632-1.
> 
> In order to fix a Debian-specific issue related to CVE-2024-24821, we
> agreed with the security team to push related dependencies via the
> next point release.

All 9 of them. :-/

Please go ahead.

Regards,

Adam

Bug#1067699: libllvm18:i386 contains files, also in libllvm18:amd64

[Torsten Wohlfarth]

Package: libllvm18
Version: 1:18.1.2-1
Severity: important
X-Debbugs-Cc: t...@siduction.org

Dear Maintainer,

libLLVM.so.1:i386 contains

/usr/lib/llvm-18/lib/libLLVM.so.1
/usr/lib/llvm-18/lib/libLLVM.so.18.1

which are also in libllvm18:amd64


That shouldn't be happen, since it makes installing of libllvm18:i386 on amd64
systems impossible.


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

Kernel: Linux 6.8.1-1-siduction-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libllvm18 depends on:
ii  libc6   2.37-15.1
ii  libedit23.1-20230828-1
ii  libffi8 3.4.6-1
ii  libgcc-s1   14-20240315-1
ii  libstdc++6  14-20240315-1
ii  libtinfo6   6.4+20240113-1
ii  libxml2 2.9.14+dfsg-1.3+b2
ii  libz3-4 4.8.12-3.1+b2
ii  libzstd11.5.5+dfsg2-2
ii  zlib1g  1:1.3.dfsg-3.1

libllvm18 recommends no packages.

libllvm18 suggests no packages.

Bug#1067698: RFS: persist-el/0.6+dfsg-1 [Team] -- persist variables between Emacs Sessions

[Xiyue Deng]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "persist-el":

 * Package name : persist-el
   Version  : 0.6+dfsg-1
   Upstream contact : Phillip Lord 
 * URL  : https://elpa.gnu.org/packages/persist.html
 * License  : GPL-3+
 * Vcs  : https://salsa.debian.org/emacsen-team/persist-el
   Section  : editors

The source builds the following binary packages:

  elpa-persist - persist variables between Emacs Sessions

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

  https://mentors.debian.net/package/persist-el/

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

  dget -x 
https://mentors.debian.net/debian/pool/main/p/persist-el/persist-el_0.6+dfsg-1.dsc

Changes since the last upload:

 persist-el (0.6+dfsg-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Debian Janitor ]
   * Remove constraints unnecessary since buster (oldstable):
 + elpa-persist: Drop versioned constraint on emacs in Recommends.
 .
   [ Xiyue Deng ]
   * New upstream release.
   * Re-export upstream signing key without extra signatures.
   * Update standards version to 4.6.2, no changes needed.

Regards,
-- 
Xiyue Deng

Bug#1066025: dh_installsystemd doesn't process user services in /usr/lib/systemd/user/

[Sergey Ponomarev]

Thank you, Neils,

> Ubuntu has patched debhelper

Sounds weird. I thought you guys had some communication with each other.

I changed the compact to 13 and indeed the scripts were generated and
included into the resulting package.
When changed to 14 scripts remains the same, no prerm script and nothing
about starting/stopping.

But when changed to 15 then the build failed:

dh_missing: warning: root/.ssh/sshtunnel.config.sh exists in debian/tmp but
is not installed to anywhere
dh_missing: error: missing files, aborting
The following debhelper tools have reported what they installed
(with files per package)
 * dh_installdocs: sshtunnel (0)

The debuild created /debian/tmp/ folder and copied all files there.
Previously it copied files to /debian/sshtunnel


I pushed the compact 14 version to a separate branch:
https://github.com/yurt-page/sshtunnel/tree/1.3.x

I'll use the old compact level for now because I want to support old
releases.
I wish to send the ssh tunnel script to the OpenSSH client itself and am
not sure what to do: require the compact 14 or again add scripts manually.

Thank you for the quick response.


On Mon, Mar 25, 2024 at 7:25 PM Niels Thykier  wrote:

> Sergey Ponomarev:
> > Hi Niels,
> >
> > I upgraded to Ubuntu 24.04 and now have debhelper 13.14.1ubuntu1.
>
>
> Hi,
>
> In case you are using Ubuntu, you should be filing the bug against
> Ubuntu for future reference. Notably, Ubuntu has patched debhelper and
> even monkey-patch(ed?) debhelper in their official builds on top that.
> Therefore, they have to screen incoming bug reports first to ensure the
> bug is not introduced by their patches.
>
> > Once executed the debuild nothing was generated.
> > When executed the dh_installsystemduser manually also nothing was
> generated.
> >  From it's sources I found that it looks for some dependency and I added
> to
> > the /debian/control:
> >
> >  Depends: ${misc:Depends}
> >
> > Now this helped and two install/uninstall scripts were generated
> > /debian/sshtunnel.postinst.debhelper
> > /debian/sshtunnel.postrm.debhelper
> >
> > I manually included the scripts to /debian/postinst and /debian/postrm
> and
> > built the deb.
>
>
> If you had to "manually" include those snippets into the deb in a clean
> build, then I think there is something seriously wrong with the
> packaging. Normally, `dh_installdeb` would do that for you if the
> commands are run in the correct sequence.
>
> Now, you mention you ran it manually. So it is possible you did that
> manually after building the deb, in which case you would see this
> behavior. This would also fit that your `debian/rules` likes quite
> standard without any room for mistakes of this kind when I checked it.
>
>
> > It was installed successfully but didn't start the service.
> > I started manually. During uninstall it has not been stopped. There is no
> > prerm script that will do that.
> >
>
> No, this feature is first added in compat 14 apparently (which is not
> stable yet). Sadly, this is not documented in the upgrade checklist for
> reasons I do not understand. The commit that introduced the feature
> recorded it in the wrong place and the remark seems to be completely gone.
>
> I will follow up on this part.
>
> > So the issues are:
> > 1. The debhelper did not execute the dh_installsystemduser. I guess I
> must
> > add it manually to /debian/rules
>
> Either that or you could use the proper debhelper-compat level.  That is
> compat 12 or later would do. The package you linked to used compat 11 as
> I recall.
>
> Remember to check the debhelper compat upgrade checklist before you
> update the compat level.
>
> It is in `man 7 debhelper-compat-upgrade-checklist` or `man 7 debhelper`
> (depending on the debhelper version).
>
> > 2. The generated scripts do not start the service after installation.
> > 3. Missing prerm script to stop the service.
>
> As mentioned above, this is compat 14 stuff.
>
> > 4. Surprising need for for ${misc:Depends}
> >
>
> There is no such need in the Debian version of debhelper for
> dh_installsystemduser to generate the snippets. However,
> dh_installsystemduser must either install the services files *or* be run
> after they are installed at the correct location.
>My best guess is that you ran dh_installsystemduser to "early" the
> first time, then the files were in place, followed by you tweaking
> debian/control and then running dh_installsystemduser without clean
> first. That is basically the one way I can make sense of what happened.
>
> That said, you ought have that dependency anyway for other reasons (at
> least up to compat 14, where it will be applied automatically).
>
> > So far I will anyway continue to use the manual scripts because I wish to
> > support old distros.
> > Anyway I wanted to have good and proper "official" scripts to install the
> > user service.
> >
> > You can play with my simple package here:
> > http://github.com/yurt-page/sshtunnel
> >
> > It can be a good 

Bug#970021: Seeking a small group to package Apache Arrow (was: Bug#970021: RFP: apache-arrow -- cross-language development platform for in-memory analytics)

[Julian Gilbey]

Hi all,

[NB: sent to d-science, d-python, d-devel and the RFP bug; reply-to
set to d-science and the RFP bug only]

An update on Apache Arrow, and in particular the Python library
PyArrow.  For those who don't know:

  Apache Arrow is a development platform for in-memory analytics. It
  contains a set of technologies that enable big data systems to
  process and move data fast. It specifies a standardized
  language-independent columnar memory format for flat and
  hierarchical data, organized for efficient analytic operations on
  modern hardware.

  The project is developing a multi-language collection of libraries
  for solving systems problems related to in-memory analytical data
  processing. This includes such topics as:

  * Zero-copy shared memory and RPC-based data movement

  * Reading and writing file formats (like CSV, Apache ORC, and Apache
Parquet)

  * In-memory analytics and query processing

  (from: https://arrow.apache.org/docs/index.html)

Pandas has announced that Pandas 3.x will depend on PyArrow
in a critical way (it will back the "string" datatype), and it is due
to be released imminently.

So this is a plea for anyone looking for something really helpful to
do: it would be great to have a group of developers finally package
this!  There was some initial work done (see the RFP bug report for
details: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970021),
but that is fairly old now.  As Apache Arrow supports numerous
languages, it may well benefit from having a group of developers with
different areas of expertise to build it.  (Or perhaps it would make
more sense to split the upstream source into a collection of different
Debian source packages for the different supported languages.  I don't
know.)  Unfortunately I don't have the capacity to devote any time to
it myself.

Thanks in advance for anyone who can step forward for this!

Best wishes,

   Julian

Bug#1067697: Update Build-Depends for the time64 library renames

[Andrey Rakhmatullin]

Source: xca
Version: 2.5.0-1
Severity: serious

The package explicitly Build-Depends: libqt5sql5, libqt5help5, this needs to be
changed to the new names if it's needed at all.


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

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

Bug#1067695: nmu: boost1.83_1.83.0-2.1

[Andrey Rakhmatullin]

Package: release.debian.org
Severity: normal
X-Debbugs-Cc: boost1...@packages.debian.org
Control: affects -1 + src:boost1.83
User: release.debian@packages.debian.org
Usertags: binnmu

nmu boost1.83_1.83.0-2.1 . ANY . unstable . -m "Rebuild for time_t"

For https://release.debian.org/transitions/html/auto-openmpi.html

Bug#1066983: monopd: Fails to start monopd.service

[Sylvain Rochet]

Hi Markus,

On Mon, Mar 25, 2024 at 02:36:59AM +0100, Markus Koschany wrote:
> Sylvain Rochet wrote:
> > Actually, the main problem is /lib/systemd/system/monopd.socket which 
> > set Accept=yes while monopd needs Accept=no (which is the default value).
> 
> I wonder if monopd needs a systemd socket file at all and if we should 
> disable the service after the installation. We have been using this 
> setting since the introduction of systemd. If monopd runs with 
> Accept=no then we also don't need a service template file. At some 
> point I also noticed the same warning as Shriram
> 
> "monopd.socket is a disabled or a static unit not running, not 
> starting it."  and then followed [1] and added the required template 
> file.

Yeah, socket activation is not really useful for public servers 
services, it is mostly used for local services that can be spawned on 
the fly later. Furthermore, socket activation breaks monopd metaserver 
registration because the daemon must be running to register, so better 
only ship the service file. I let you decide whether the service should 
be disabled or enabled by default (but unless something recently 
changed, daemon usually runs by default on Debian. I admit having lost 
track :D).


> I have been running monopd for the past decade and I also suspect the 
> daemon is affected by some bugs which might be remotely exploitable.

What makes you think that?

My daemon is running attached to gdb so I can easily catch and trace any 
issue that would kill the process. So far it's been over 10 years 
without a single issue, some process lived for several years between 
systems reboot.

I am not saying it is bug free because nothing is bug free, but if it is 
remotely exploitable and actively exploited, I would be aware of it on 
my running instance.


> Since users usually don't need the monopd server anyway, if they want 
> to play a game, they should make a conscious decision to start it if 
> they want to use it locally. For a simple internet game, the daemon is 
> not required.

Installing the server package isn't already a conscious decision?


Kind regards,
Sylvain


signature.asc
Description: Digital signature

Bug#1057548: closed by Debian FTP Masters (reply to Noah Meyerhans ) (Bug#1057548: fixed in cloud-init 24.1.1-1)

[Santiago Vila]

found 1057548 24.1.1-1
retitle 1057548 cloud-init: FTBFS: missing Build-Depends on passwd
tags 1057548 + patch
thanks

Hello.

I don't quite understand why this bug was closed with this changelog entry:

   * New upstream version 24.1 (Closes: #1057548)

I did not ask for a new upstream version to be packaged, and the upload
did not really fix the bug. I assume you just misdiagnosed it.

The build log contains this line:

RuntimeError: Unable to lock user account 'foo_user'. No tools available.   
Tried: ['passwd', 'usermod'].

and in fact such line disappears when passwd is present in the chroot.

The problem is that passwd is no longer build-essential in trixie/sid, so if 
it's
required for building, it needs to be added to Build-Depends.

To reproduce, please try using debootstrap from trixie/sid, which finally stops
installing a few of required-but-not-build-essential packages.

Trivial patch attached.

Thanks.--- a/debian/control
+++ b/debian/control
@@ -10,6 +10,7 @@ Build-Depends:
  debhelper-compat (= 13),
  dh-python,
  iproute2,
+ passwd,
  po-debconf,
  procps ,
  pylint,

Bug#1067694: Update Build-Depends for the time64 library renames

[Andrey Rakhmatullin]

Source: glogg
Version: 1.1.4-1.1
Severity: serious

The package explicitly Build-Depends: libqt5dbus5, this needs to be changed to
libqt5dbus5t64 if it's needed at all.


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

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

Bug#1067693: open-vm-tools version 12.4.0 has been released - please rebase

[John Wolfe Jr]

Package: open-vm-tools
Version: 2:12.4.0

open-vm-tools 12.4.0 was released on March 21, 2024.

There are no new features in the open-vm-tools 12.4.0 release. This is
primarily a maintenance release that addresses a single critical
problem:

For complete details, see:
https://github.com/vmware/open-vm-tools/releases/tag/stable-12.4.0

Release Notes are available at:
https://github.com/vmware/open-vm-tools/blob/stable-12.4.0/ReleaseNotes.md

The granular changes that have gone into the 12.4.0 release are in the
ChangeLog at: 
https://github.com/vmware/open-vm-tools/blob/stable-12.4.0/open-vm-tools/ChangeLog

Please rebase open-vm-tools to release 12.4.0 on supported Debian
releases as appropriate.

-- 
This electronic communication and the information and any files transmitted 
with it, or attached to it, are confidential and are intended solely for 
the use of the individual or entity to whom it is addressed and may contain 
information that is confidential, legally privileged, protected by privacy 
laws, or otherwise restricted from disclosure to anyone else. If you are 
not the intended recipient or the person responsible for delivering the 
e-mail to the intended recipient, you are hereby notified that any use, 
copying, distributing, dissemination, forwarding, printing, or copying of 
this e-mail is strictly prohibited. If you received this e-mail in error, 
please return the e-mail to the sender, delete it from your computer, and 
destroy any printed copy of it.

Bug#1067692: gcc-arm-none-eabi: inttypes.h fails to define PRIi64 on GCC 13.2.1 with newlib

[Jonathan Neuschäfer]

Package: gcc-arm-none-eabi
Version: 15:13.2.rel1-2
Severity: normal

After upgrading to Debian trixie (currently "testing") and thus GCC
13.2.1, inttypes.h doesn't define the 64-bit format specifiers such as
PRIi64 anymore, as demonstrated and explained by the following program:

// $ arm-none-eabi-gcc --version
// arm-none-eabi-gcc (15:13.2.rel1-2) 13.2.1 20231009
//
// $ arm-none-eabi-gcc -c test.c
// test.c: In function 'main':
// test.c:21:31: error: expected ')' before 'PRIi64'
//21 | printf("the answer: %" PRIi64 "\n", i);
//   |   ~   ^~~
//   |   )
// test.c:18:1: note: 'PRIi64' is defined in header ''; did you 
forget to '#include '?
//17 | #include 
//   +++ |+#include 
//18 |

#include 
#include 
#include 

int main(void) {
int64_t i = 42;
printf("the answer: %" PRIi64 "\n", i);
return 0;
}

//
// /usr/include/newlib/machine/_default_types.h correctly defines 
___int64_t_defined,
// (indentation for emphasis mine, in all code excerpts):
//
// #ifdef __INT64_TYPE__
//  typedef __INT64_TYPE__ __int64_t;
//  #ifdef __UINT64_TYPE__
//   typedef __UINT64_TYPE__ __uint64_t;
//  #else
//   typedef unsigned __INT64_TYPE__ __uint64_t;
//  #endif
//  #define ___int64_t_defined 1
// #elif __EXP(LONG_MAX) > 0x7fff
//  typedef signed long __int64_t;
//  typedef unsigned long __uint64_t;
//  #define ___int64_t_defined 1
//  ...
//
//
// Next, __int64_t_defined would be set in /usr/include/newlib/sys/_stdint.h:
//
// #ifdef ___int64_t_defined
//  #ifndef _INT64_T_DECLARED
//   typedef __int64_t int64_t ;
//   #define _INT64_T_DECLARED
//  #endif
//  #ifndef _UINT64_T_DECLARED
//   typedef __uint64_t uint64_t ;
//   #define _UINT64_T_DECLARED
//  #endif
//  #define __int64_t_defined 1
// #endif /* ___int64_t_defined */
//
//
// sys/_stdint.h would be included via , but that doesn't happen
// because GCC picks the wrong stdint.h, from 
/usr/lib/gcc/arm-none-eabi/13.2.1/include/stdint.h.
//
// Finally, PRIi64 and similar macros are not defined in
// /usr/include/newlib/inttypes.h, because __int64_t_defined wasn't defined:
//
// #if __int64_t_defined
//  #define PRId64  __PRI64(d)
//  #define PRIi64  __PRI64(i)
//  #define PRIo64  __PRI64(o)
//  #define PRIu64  __PRI64(u)
//  #define PRIx64  __PRI64(x)
//  #define PRIX64  __PRI64(X)
//
//  #define SCNd64  __SCN64(d)
//  #define SCNi64  __SCN64(i)
//  #define SCNo64  __SCN64(o)
//  #define SCNu64  __SCN64(u)
//  #define SCNx64  __SCN64(x)
// #endif
//
//
// As a workaround, #include  before #include  fixes 
the issue.


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

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

Versions of packages gcc-arm-none-eabi depends on:
ii  binutils-arm-none-eabi  2.41.90.20240115-1+23
ii  libc6   2.37-15
ii  libgcc-s1   14-20240201-3
ii  libgmp102:6.3.0+dfsg-2+b1
ii  libisl230.26-3+b2
ii  libmpc3 1.3.1-1+b2
ii  libmpfr64.2.1-1+b1
ii  libstdc++6  14-20240201-3
ii  zlib1g  1:1.3.dfsg-3+b1

Versions of packages gcc-arm-none-eabi recommends:
ii  libnewlib-arm-none-eabi  4.4.0.20231231-2

gcc-arm-none-eabi suggests no packages.

-- no debconf information

Bug#1067691: FTBFS: double free or corruption

[Andrey Rakhmatullin]

Source: spek
Version: 0.8.5+dfsg-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=spek=armel=0.8.5%2Bdfsg-3%2Bb3=1711383117=0

fft const
double free or corruption (!prev)
/bin/bash: line 6: 27223 Aborted ${dir}$tst
FAIL: test


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

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

Bug#1067688: firefox-esr: Cannot copy address bar link to other windows in Wayland

[Huey Chen]

Package: firefox-esr
Version: 115.9.1esr-1
Severity: normal
X-Debbugs-Cc: hueyche...@outlook.com

Dear Maintainer,
If anyone tries to copy the address bar in the top of Firefox, it will only 
copy within Firefox and not other windows. This happens in Wayland.
I want to copy and paste the link in the address bar to another window, but 
nothing is even copied. Text is copied everywhere in Firefox except the address 
bar.


-- Package-specific info:


-- Addons package information

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

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

Versions of packages firefox-esr depends on:
ii  debianutils  5.17
ii  fontconfig   2.15.0-1.1
ii  libasound2t641.2.11-1+b1
ii  libatk1.0-0t64   2.51.90-4
ii  libc62.37-15.1
ii  libcairo-gobject21.18.0-3
ii  libcairo21.18.0-3
ii  libdbus-1-3  1.14.10-4+b1
ii  libdbus-glib-1-2 0.112-3+b2
ii  libevent-2.1-7t642.1.12-stable-8.1+b1
ii  libffi8  3.4.6-1
ii  libfontconfig1   2.15.0-1.1
ii  libfreetype6 2.13.2+dfsg-1+b2
ii  libgcc-s114-20240315-1
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-3+b2
ii  libglib2.0-0t64  2.78.4-6
ii  libgtk-3-0t643.24.41-3
ii  libnspr4 2:4.35-1.1+b1
ii  libnss3  2:3.99-1
ii  libpango-1.0-0   1.52.1+ds-1
ii  libstdc++6   14-20240315-1
ii  libvpx8  1.13.1-2
ii  libx11-6 2:1.8.7-1
ii  libx11-xcb1  2:1.8.7-1
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.4-1
ii  libxtst6 2:1.2.3-1.1
ii  procps   2:4.0.4-4
ii  zlib1g   1:1.3.dfsg-3.1

Versions of packages firefox-esr recommends:
ii  libavcodec60  7:6.1.1-3

Versions of packages firefox-esr suggests:
pn  fonts-lmodern   
pn  fonts-stix | otf-stix   
ii  libcanberra0t64 [libcanberra0]  0.30-12.2
ii  libgssapi-krb5-21.20.1-6
pn  pulseaudio  

-- no debconf information