Bug#1066838: hplip: Files remain after purge

[Scott Kitterman]

Package: hplip
Version: 3.22.10+dfsg0-2
Severity: important

After removing and then purging hplip, the __pycache__ directories
remain.

# apt purge hplip
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
  hplip*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 358577 files and directories currently installed.)
Purging configuration files for hplip (3.22.10+dfsg0-2) ...
Processing triggers for dbus (1.14.10-1~deb12u1) ...

# ls -R /usr/share/hplip/
/usr/share/hplip/:
base  copier  fax  installer  pcard  prnt  __pycache__  scan  ui5

/usr/share/hplip/base:
pexpect  __pycache__

/usr/share/hplip/base/pexpect:
__pycache__

/usr/share/hplip/base/pexpect/__pycache__:

/usr/share/hplip/base/__pycache__:

/usr/share/hplip/copier:
__pycache__

/usr/share/hplip/copier/__pycache__:

/usr/share/hplip/fax:
__pycache__

/usr/share/hplip/fax/__pycache__:

/usr/share/hplip/installer:
__pycache__

/usr/share/hplip/installer/__pycache__:

/usr/share/hplip/pcard:
__pycache__

/usr/share/hplip/pcard/__pycache__:

/usr/share/hplip/prnt:
__pycache__

/usr/share/hplip/prnt/__pycache__:

/usr/share/hplip/__pycache__:

/usr/share/hplip/scan:
__pycache__

/usr/share/hplip/scan/__pycache__:

/usr/share/hplip/ui5:
__pycache__

/usr/share/hplip/ui5/__pycache__:

Scott K


-- 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/4 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 hplip depends on:
ii  adduser3.134
ii  cups   2.4.2-3+deb12u5
pn  hplip-data 
ii  libc6  2.36-9+deb12u4
ii  libcups2   2.4.2-3+deb12u5
ii  libdbus-1-31.14.10-1~deb12u1
ii  libhpmud0  3.22.10+dfsg0-2
ii  libpython3.11  3.11.2-6
pn  libsane-hpaio  
ii  libsane1   1.2.1-2
ii  lsb-base   11.6
ii  printer-driver-hpcups  3.22.10+dfsg0-2
ii  python33.11.2-1+b1
ii  python3-dbus   1.3.2-4+b1
ii  python3-gi 3.42.2-3+b1
pn  python3-pexpect
ii  python3-pil9.4.0-1.1+b1
pn  python3-reportlab  
ii  sysvinit-utils [lsb-base]  3.06-4
ii  wget   1.21.3-1+b2
ii  xz-utils   5.4.1-0.2

Versions of packages hplip recommends:
ii  avahi-daemon  0.8-10
ii  policykit-1   122-3
ii  printer-driver-postscript-hp  3.22.10+dfsg0-2
ii  sane-utils1.2.1-2

Versions of packages hplip suggests:
pn  hplip-doc  
pn  hplip-gui  
ii  python3-notify20.3-5
ii  system-config-printer  1.5.18-1

Bug#1066842: Updating extrepo-offline-data in Debian Stable

[Wouter Verhelst]

Package: release.debian.org
Control: affects -1 + src:extrepo-data
User: release.debian@packages.debian.org
Usertags: pu
Tags: bookworm
Severity: normal
Subject: bookworm-pu: package extrepo-data/1.0.5
thanks

[making this an official stable update request; for the full backstory,
please see the thread starting at
https://lists.debian.org/debian-release/2024/03/msg00076.html]]

On Thu, Mar 07, 2024 at 07:10:28PM +0100, Thomas Goirand wrote:
> On 3/7/24 06:57, Paul Gevers wrote:
> > Having said that and not knowing if it doesn't already do that, if
> > extrepro would update a cache when online, it's offline option could
> > also be refreshed at a convenience moment without the need for an
> > up-to-date package in stable. I hope it's needless to say that I don't
> > mean that this mechanisme should replace the data package, merely
> > complement it.
> 
> It's actually a very good idea to have such cache. Though as you wrote, it
> doesn't replace the data package, especially when one wants to use local
> mirror, with something like this:
> 
> apt-get install extrepo extrepo-offline-data
> extrepo enable --offlinedata --mirror http://mirror.example.com/haproxy

To give a bit more background here:

extrepo was originally designed to use an online, GPG-signed, metadata
repository. When you run an extrepo command and it needs to, extrepo
will download the metadata index and the signature on that, and then
verify that the signature is correct. All further information that it
needs is hashed with a cryptographically secure hash, and so can be
assumed to be safe.

extrepo provides two things: a (checked and vetted) URI for a repository
of external packages, and a (checked and vetted) GPG key that can sign
packages in that repository.

Accessing the metadata repository in the way described above however
requires direct access to that metadata repository, which is complicated
for air-gapped systems. While the location of that repository is
configurable, and in theory it is possible to write a tool which will
download the metadata plus all signatures plus all external files that
exist, that seems like quite a bit of work, and Thomas therefore
suggested an alternate solution whereby the extrepo metadata is also
packaged in Debian. Doing so only requires a person to mirror the
repository that they want to enable, and to override the mirror URL by
way of the --mirror option passed to extrepo. This way, extrepo will
enable the repository on the given mirror, and will ensure that the
relevant GPG key for the repository in question is provided to apt,
which can still save the user some work of having to manually download
and verify the GPG key.

The downside here however, is that most repositories are updated to add
support for a particular Debian release only after that Debian release
has been promoted to stable. This unfortunately reduces the usability of
the extrepo-offline-data package, which could be remedied by updating
the package in stable.

The extrepo-offline-data package, as the name implies, is a data-only
package. Apart from the changelog and copyright in /usr/share/doc, it
only contains metadata files under /usr/share/extrepo/offline-data.

Thanks for your consideration,

-- 
 w@uter.{be,co.za}
wouter@{grep.be,fosdem.org,debian.org}

I will have a Tin-Actinium-Potassium mixture, thanks.

Bug#1066801: pandas: FTBFS: /usr/lib/python3/dist-packages/dateutil/zoneinfo/__init__.py:26: UserWarning: I/O error(2): No such file or directory

[Rebecca N. Palmer]

Control: retitle -1 pandas: test-failing warning with new xarray

This is a warning being treated as an error, but the one in 
test_to_xarray (probably due to the new version of xarray), not the 
zoneinfo one.  This is a FutureWarning, so it should be OK to *use* the 
current pandas with the new xarray.


The same warning happens in autopkgtest but isn't treated as an error 
there, so didn't block the new xarray.


I intend to try fixing this later.

Bug#1066814: plotly: Please upgrade to latest upstream version

[Andreas Tille]

Hi Josue,

Am Wed, Mar 13, 2024 at 06:19:05PM -0600 schrieb Josue Ortega:
> 
> Hopefully, I'll be uploading the latest version next weekend. I've been quite
> busy with $DAILY_JOB.

Thank you for your quick response.  As a volunteer your $DAILY_JOB has
definitely preference.  To cover such situations I recommend team
maintenance which would enable team members to simply do some team
upload.  It might help you concentrating on other things if your
available time is limited.

Thank you for maintaining the package in any case
   Andreas.

-- 
http://fam-tille.de

Bug#1066844: at-spi2-core: needs re-bootstrapping on armel, armhf for 64-bit time_t transition

[Simon McVittie]

Package: at-spi2-core
Version: 2.51.90-3
Severity: important
X-Debbugs-Cc: debian-...@lists.debian.org
Tags: patch

at-spi2-core has a circular build-dependency on itself when tests are
enabled, which makes its build-dependencies unsatisfiable (libglib2.0-dev
depends on libglib2.0-0t64, but at-spi2-core still depends on libglib2.0-0)
and prevents it from being rebuilt for the 64-bit time_t transition.
I think the easiest way to unblock this will be to disable tests on the
affected architectures temporarily, similar to what was done in stunnel4.

It's also affected by a longer cyclic build-dependency chain:
at-spi2-core, dbus-broker, systemd, cryptsetup, libssh, openssh-server,
gtk+3.0, back to at-spi-2-core. I think the easiest way to break this
one will be temporarily swapping back from dbus-broker to dbus-daemon
as preferred on the affected architectures. I confirmed that this makes
it buildable on a porterbox.

Proposed patches available on
https://salsa.debian.org/a11y-team/at-spi2-core/-/merge_requests/8,
I'll attach them to the bug when I've amdended them to include the
bug number.

After at-spi2-core has been rebuilt, I'm hoping that similar changes will
unblock the ability to rebuild gtk+2.0 and gtk+3.0.

smcv

Bug#1059308: Tag bugs pending

[Andreas Tille]

Control: tags -1 pending

I'm just marking these bugs pending for next upload.  They were even
closed in recent Debian package but since they are concerning CVEs it
might be better to close these inside a changelog of next upload.

Kind regards
   Andreas.

-- 
http://fam-tille.de

Bug#1066841: rpm: hard Build-Depends on unportable package pandoc

[Thorsten Glaser]

retitle 1066841 rpm: hard Build-Depends on unportable package pandoc
thanks

Hi,

rpm also exhibits the same portability problem. Please see
whether it’s possible to use pandoc only during arch:all
builds or otherwise not in arch:any…

Thanks,
//mirabilos
-- 
This space for rent.

https://paypal.me/mirabilos to support my work.

Bug#1066310: dx: FTBFS: _compparse.c:51:17: error: implicit declaration of function ‘_dxfcclex’ [-Werror=implicit-function-declaration]

[Bo YU]

On Wed, Mar 13, 2024 at 12:37:02PM +0100, Lucas Nussbaum wrote:
...

cc1: warning: command-line option ‘-std=c++11’ is valid for C++/ObjC++ but not 
for C
y.tab.c: In function ‘_dxfccparse’:
_compparse.c:51:17: error: implicit declaration of function ‘_dxfcclex’ 
[-Werror=implicit-function-declaration]
   51 | #define yylex   _dxfcclex
  | ^
y.tab.c:651:16: note: in expansion of macro ‘yylex’
y.tab.c:1107:16: note: in expansion of macro ‘YYLEX’
_compparse.c:52:17: error: implicit declaration of function ‘_dxfccerror’ 
[-Werror=implicit-function-declaration]
   52 | #define yyerror _dxfccerror
  | ^~~
y.tab.c:1682:2: note: in expansion of macro ‘yyerror’
./_compparse.y: In function ‘_dxfccerror’:
./_compparse.y:432:47: error: implicit declaration of function 
‘_dxfcclexerror’; did you mean ‘_dxfccerror’? 
[-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
make[6]: *** [Makefile:961: _compparse.lo] Error 1


I have attached one debdiff and it can be built with it. So could you
upload it with it? I can team upload if nobody response with this sor
some days.

BTW, dx upstream has dead, so refer to:
https://trac.macports.org/ticket/61842


--
Regards,
--
  Bo YU

diff -Nru dx-4.4.4/debian/changelog dx-4.4.4/debian/changelog
--- dx-4.4.4/debian/changelog   2024-02-29 07:06:03.0 +0800
+++ dx-4.4.4/debian/changelog   2024-03-14 14:17:17.0 +0800
@@ -1,3 +1,11 @@
+dx (1:4.4.4-15.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add -Wno-error=implicit-function-declaration into 
+DEB_CFLAGS_MAINT_APPEND. (Closes: #1066310)
+
+ -- Bo YU   Thu, 14 Mar 2024 14:17:17 +0800
+
 dx (1:4.4.4-15.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru dx-4.4.4/debian/rules dx-4.4.4/debian/rules
--- dx-4.4.4/debian/rules   2024-02-29 07:06:00.0 +0800
+++ dx-4.4.4/debian/rules   2024-03-14 14:17:05.0 +0800
@@ -4,6 +4,7 @@
 
 export DEB_BUILD_MAINT_OPTIONS=hardening=+all
 DEB_CFLAGS_MAINT_APPEND=-fsigned-char -fno-strict-aliasing -std=c++11
+DEB_CFLAGS_MAINT_APPEND=-Wno-error=implicit-function-declaration
 DEB_CXXFLAGS_MAINT_APPEND=-fsigned-char -fno-strict-aliasing -std=c++11
 DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
 ifeq ($(DEB_HOST_ARCH), alpha)


signature.asc
Description: PGP signature

Bug#1066840: no mention of iproute2 6.7.0-2.1 in changelog

[Luca Boccassi]

Control: tags -1 wontfix
Control: close -1

On Thu, 14 Mar 2024 at 07:30, Aníbal Monsalve Salazar  wrote:
>
> Package: iproute2
> Version: 6.8.0-1
> Severity: important
>
> Dear Maintainer,
>
> At https://tracker.debian.org/pkg/iproute2 it reads:
> [2024-03-12] Accepted iproute2 6.7.0-2.1 (source) into unstable (Helmut 
> Grohne)
>
> I cannot find the changelog entry listed below for iproute2 6.7.0-2.1 in
> the changelog of iproute2 6.8.0-1.
>
> iproute2 (6.7.0-2.1) unstable; urgency=medium
>
>   * Non-maintainer upload.
>   * Explicitly depend on libtirpc-dev. (Closes: #1065214)
>
>  -- Helmut Grohne   Tue, 12 Mar 2024 09:03:30 +0100

That was intentional and in agreement with Helmut as the same fix was
already queued in git before the NMU

Bug#1065831: document package specifiers for `upgrade`

[David Kalnischkies]

(this reply has nothing to do with the bugreport in question)

On Wed, Mar 13, 2024 at 10:00:56PM +0100, Miguel Angel Rojas wrote:
> >> Julian provided an explanation in #74,
> 20240312113620.ga1944...@debian.org
> 
> I can't access this link..

It isn't a link, it is a message id of an email. Your mail client (or
web frontend or whatever) should find the mail if you search for it
– assuming you got that mail and haven't deleted it in the meantime of
course.

You can also make it a link by prepending https://lists.debian.org/,
aka: https://lists.debian.org/20240312113620.ga1944...@debian.org
That will search for the mail in Debians mailing list archives.


Best regards

David Kalnischkies


signature.asc
Description: PGP signature

Bug#1041552: HFS/HFS+ are insecure

[Marco d'Itri]

On Mar 13, Michael Biebl  wrote:

> > So I propose this content for a file like
> > /usr/lib/udev/rules.d/75-insecure-fs.rules:
> Just curious: Why did you pick priority 75?
I can't remember.

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#1066789: pycoast: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

[Antonio Valentino]

Dear Lucas,
thanks for reporting.

On Wed, 13 Mar 2024 15:58:32 +0100 Lucas Nussbaum  wrote:

Source: pycoast
Version: 1.7.0+dfsg-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):


[CUT]


 ERRORS 
 ERROR collecting pycoast/tests/test_pycoast.py 
/usr/lib/python3/dist-packages/pluggy/_hooks.py:501: in __call__
return self._hookexec(self.name, self._hookimpls.copy(), kwargs, 
firstresult)
/usr/lib/python3/dist-packages/pluggy/_manager.py:119: in _hookexec
return self._inner_hookexec(hook_name, methods, kwargs, firstresult)
/usr/lib/python3/dist-packages/_pytest/python.py:278: in 
pytest_pycollect_makeitem
return list(collector._genfunctions(name, obj))
/usr/lib/python3/dist-packages/_pytest/python.py:507: in _genfunctions
self.ihook.pytest_generate_tests.call_extra(methods, 
dict(metafunc=metafunc))
/usr/lib/python3/dist-packages/pluggy/_hooks.py:562: in call_extra
return self._hookexec(self.name, hookimpls, kwargs, firstresult)
/usr/lib/python3/dist-packages/pluggy/_manager.py:119: in _hookexec
return self._inner_hookexec(hook_name, methods, kwargs, firstresult)
/usr/lib/python3/dist-packages/pytest_lazyfixture.py:74: in 
pytest_generate_tests
normalize_metafunc_calls(metafunc, 'funcargs')
/usr/lib/python3/dist-packages/pytest_lazyfixture.py:81: in 
normalize_metafunc_calls
calls = normalize_call(callspec, metafunc, valtype, used_keys)
/usr/lib/python3/dist-packages/pytest_lazyfixture.py:105: in normalize_call
valtype_keys = set(getattr(callspec, valtype).keys()) - used_keys
E   AttributeError: 'CallSpec2' object has no attribute 'funcargs'
=== warnings summary ===
../../../../../../usr/lib/python3/dist-packages/_pytest/python.py:507
  /usr/lib/python3/dist-packages/_pytest/python.py:507: 
PluggyTeardownRaisedWarning: A plugin raised an exception during an old-style 
hookwrapper teardown.
  Plugin: lazy-fixture, Hook: pytest_generate_tests
  AttributeError: 'CallSpec2' object has no attribute 'funcargs'
  For more information see 
https://pluggy.readthedocs.io/en/stable/api_reference.html#pluggy.PluggyTeardownRaisedWarning
self.ihook.pytest_generate_tests.call_extra(methods, 
dict(metafunc=metafunc))

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
=== short test summary info 
ERROR ../../../pycoast/tests/test_pycoast.py - AttributeError: 'CallSpec2' ob...
 Interrupted: 1 error during collection 
= 1 warning, 1 error in 0.26s ==


the issue seems to be related to the pytest-lazyfixture package.
See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063957.
I will reassign.


regards
--
Antonio Valentino

Bug#1066138: [pkg-gnupg-maint] Bug#1066138: gnupg1: fails to build gpgkeys_ldap, probably due to -Werror=implicit-function-declaration

[Sune Stolborg Vuorela]

On Wednesday, March 13, 2024 7:10:13 PM CET Andreas Metzler wrote:
> Hello Thorsten,
> I have upload a fix for 2.2, probably will not be able to spend any time
> on 1.x or 2.4 before the weekend.

Looks like 2.4 is fixed upstream a couple of years
https://dev.gnupg.org/rGddc6f7d194918791ac9dff0e5af4b80933189afd

/Sune
-- 
I didn’t stop pretending when I became an adult, it’s just that when I was a 
kid I was pretending that I fit into the rules and structures of this world. 
And now that I’m an adult, I pretend that those rules and structures exist.
   - zefrank

Bug#900568: Packaging PoC

[David Prevot]

control: tag -1 patch

Hi,

I’ve prepared a php-pdo-sqlsrv package for Bullseye (I had to stick with
version 5.10 for PHP 7.4), it should work almost out of the box for
Bookworm and unstable. I don’t intend to upload it to Debian proper, but
it’s available in a public repository.

https://gitea.evolix.org/dprevot/php-pdo-sqlsrv

Regards,
-- 
David Prévot
Marseille (37 rue Guibal, Pôle Média, 13003) / Paris / Montréal
http://evolix.com | Twitter: @Evolix @EvolixNOC | http://blog.evolix.com

Bug#900572: Packaging PoC

[David Prevot]

control: tag -1 patch

Hi,

I’ve prepared a php-sqlsrv package for Bullseye (I had to stick with
version 5.10 for PHP 7.4), it should work almost out of the box for
Bookworm and unstable. I don’t intend to upload it to Debian proper, but
it’s available in a public repository.

https://gitea.evolix.org/dprevot/php-sqlsrv

Regards,
-- 
David Prévot
Marseille (37 rue Guibal, Pôle Média, 13003) / Paris / Montréal
http://evolix.com | Twitter: @Evolix @EvolixNOC | http://blog.evolix.com

Bug#1065329: O: numpy -- Fast array facility to the Python 3 language

[Timo Röhling]

Hi Christian,

On Sat, 2 Mar 2024 23:11:15 +0100 Christian Kastner  
wrote:

Control: retitle -1 O: numpy -- Fast array facility to the Python 3 language
Control: tags -1 - pending

Having read up on debian-python, I have misread the situation. I think
there needs to be a policy resolution first.
I don't understand what you mean. The orphaning process is not tied 
to DPT policy, is it?


FWIW, I am a regular user of this package and would also like to 
help maintain it.



Cheers
Timo

--
⢀⣴⠾⠻⢶⣦⠀   ╭╮
⣾⠁⢠⠒⠀⣿⡁   │ Timo Röhling   │
⢿⡄⠘⠷⠚⠋⠀   │ 9B03 EBB9 8300 DF97 C2B1  23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄   ╰╯


signature.asc
Description: PGP signature

Bug#1065329: O: numpy -- Fast array facility to the Python 3 language

[Christian Kastner]

Hi Timo,

On 2024-03-14 10:06, Timo Röhling wrote:
>> Having read up on debian-python, I have misread the situation. I think
>> there needs to be a policy resolution first.
> I don't understand what you mean. The orphaning process is not tied to
> DPT policy, is it?
> 
> FWIW, I am a regular user of this package and would also like to help
> maintain it.

I underspecified -- what I meant is resolution of both policy and the
active team dynamics.

In any case, if this isn't resolved soon, I'm also happy to contribute.

Best,
Christian

Bug#1064946: morph's abandoned packages (list)

[Andreas Tille]

Control: tags -1 moreinfo

Hi,

this package is team maintained.  I have to assume its former maintainer
has decided to leave the team.  Please delay the removal until it is
perfectly clear that no other team member intends to take over this
package.

Thank you for your work as ftpmaster
 Andreas.

-- 
http://fam-tille.de

Bug#1066846: loudmouth: replace libidn11-dev with libidn-dev

[Simon Josefsson]

Package: loudmouth
Version: 1.5.4-1
Tags: patch

Hi!  I'd like to drop the transitional package 'libidn11-dev' as most
packages have already moved to use 'libidn-dev' which is in stable.

How about this patch?

/Simon

diff --git a/debian/control b/debian/control
index 853b197..963b1c3 100644
--- a/debian/control
+++ b/debian/control
@@ -7,7 +7,7 @@ Build-Depends: debhelper-compat (= 13),
gtk-doc-tools (>= 1.1-2),
libglib2.0-dev,
libgnutls28-dev (>= 3.0.20),
-   libidn11-dev,
+   libidn-dev,
libasyncns-dev,
check,
libkrb5-dev
@@ -25,7 +25,7 @@ Depends: ${misc:Depends},
  libloudmouth1-0 (= ${binary:Version}),
  libglib2.0-dev,
  libgnutls28-dev,
- libidn11-dev
+ libidn-dev
 Description: Development files for Loudmouth Jabber library
  The development headers and API documentation for the LoudMouth
  Jabber library. See the description of libloudmouth1-0 for a more detailed


signature.asc
Description: PGP signature

Bug#1064946: morph's abandoned packages (list)

[Julian Gilbey]

Dear all (and Bcc-ing the RM bugs),

For information, here is a list of packages that morph has either
requested removal of or orphaned.  If you are interested in taking one
or more of them on, that would be great!

Removal requested:

#1066146 RM: flask-basicauth -- ROM; RC buggy, dead upstream, leaf package
#1065141 RM: gmplot -- ROM; leaf package
#1064947 RM: nb2plots -- ROM; leaf package
#1065200 RM: overpass -- ROM; leaf package
#1065199 RM: pprintpp -- ROM; leaf package
#1065045 RM: pyannotate -- ROM; leaf package
#1065201 RM: python-overpy -- ROM; leaf package
#1065202 RM: python-ppmd -- ROM; leaf package
#1064946 RM: sphinx-a4doc -- ROM; leaf package

Recently-orphaned packages (removing those in wnpp which have been
retitled "ITA") sorted alphabetically; these could, of course, be
brought into team maintenance.

#1065235 O: basemap -- matplotlib toolkit to plot on map projections
#1065243 O: colorspacious -- library for doing colorspace conversions
#1065151 O: commonmark -- Python parser for the CommonMark Markdown spec
#1065246 O: contourpy -- Python library for calculating contours of 2D 
quadrilateral grids
#1065248 O: cppy -- C++ headers for (Python) C extension development
#1065139 O: dot2tex -- Graphviz to LaTeX converter
#1065140 O: fastkml -- fast KML processing
#1065142 O: html5lib -- HTML parser/tokenizer based on the WHATWG HTML5 
specification
#1065244 O: kiwisolver -- fast implementation of the Cassowary constraint 
solver
#1065238 O: lazy-object-proxy -- Python 3 fast and thorough lazy object 
proxy
#1065037 O: m2crypto -- Python wrapper for the OpenSSL library
#1065325 O: matplotlib -- Python based plotting system
#1065143 O: mkautodoc -- AutoDoc for MarkDown
#1065042 O: mpl-sphinx-theme -- documentation for the mpl-sphinx-theme 
Python library
#1065220 O: mpmath -- library for arbitrary-precision floating-point 
arithmetic
#1065224 O: mysql-connector-python -- pure Python implementation of MySQL 
Client/Server protocol
#1065198 O: networkx -- tool to create, manipulate and study complex 
networks
#1065329 O: numpy -- Fast array facility to the Python 3 language
#1065221 O: py7zr -- pure Python 7-zip library
#1065222 O: pychm -- Python binding for CHMLIB
#1065231 O: pydot -- Python interface to Graphviz's dot
#1065152 O: pygeoif -- basic implementation of the __geo_interface__
#1065036 O: pyopenssl -- Python wrapper around the OpenSSL library
#1065149 O: pyproject-metadata -- Dataclass for PEP 621 metadata with 
support for [core metadata] generation
#1065223 O: pysimplesoap -- simple and lightweight SOAP Library
#1064977 O: python-cryptography-vectors -- Test vectors for 
python-cryptography
#1065327 O: python-levenshtein -- extension for computing string 
similarities and edit distances
#1065025 O: sphinx-book-theme -- clean book theme for scientific 
explanations and documentation with Sphinx
#1065026 O: sphinx-bootstrap-theme -- bootstrap theme for Sphinx
#1065030 O: sphinxcontrib-log-cabinet -- Organize changelog directives in 
Sphinx docs
#1065027 O: sphinx-copybutton -- sphinx extension to add a "copy" button to 
code blocks
#1065028 O: sphinx-gallery -- extension that builds an HTML gallery of 
examples from Python scripts
#1065029 O: sphinx-panels -- documentation for the sphinx-panels Python 
library
#1065043 O: sphinxtesters -- utilities for testing Sphinx extensions
#1064948 O: texext -- sphinx extensions for working with LaTeX math

There's also an old ITP that was closed:

#1015231 ITP: sphinx-theme-builder -- tool for authoring Sphinx themes with 
a simple (opinionated) workflow

Best wishes,

   Julian

Bug#902240: html-xml-utils: don't Build-Depends: man2html

[Thorsten Glaser]

ping

this (s/man2html/man2html-base/) would IMMENSELY help with
the current transitions, and I might NMU if no reaction

Bug#1066843: util-linux: --delete option does not work

[Francesco Potortì]

Package: util-linux
Version: 2.39.3-6
Severity: normal
X-Debbugs-Cc: none, Francesco Potortì 
File: /usr/bin/findmnt

The man page for findmnt lists a --delete option which is necessary to me.  
Unfortunately, findmnt says it does not have such option, s (I resorted to 
using mount for that.

Either --delete should work for findmnt, or the man page should be amended to 
remove the --delete option and ideally suggest using mount for those needing it.

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

Kernel: Linux 6.5.0-5-amd64 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=it_IT.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 util-linux depends on:
ii  libblkid1  2.39.3-6
ii  libc6  2.37-15
ii  libcap-ng0 0.8.4-2
ii  libcrypt1  1:4.4.36-4
ii  libmount1  2.39.3-6
ii  libpam0g   1.5.2-9.1+b1
ii  libselinux13.5-2
ii  libsmartcols1  2.39.3-6
ii  libsystemd0255.4-1
ii  libtinfo6  6.4+20240113-1
ii  libudev1   255.4-1
ii  libuuid1   2.39.3-6
ii  zlib1g 1:1.3.dfsg-3+b1

Versions of packages util-linux recommends:
ii  sensible-utils  0.0.22

Versions of packages util-linux suggests:
ii  dosfstools  4.2-1
ii  kbd 2.6.4-2
ii  util-linux-extra2.39.3-6
pn  util-linux-locales  

-- debconf information:
  util-linux/noauto-with-nonzero-passnum:

Bug#1065395: [Pkg-opencl-devel] Bug#1065395: spirv-llvm-translator-14: autopkgtest on s390x uses huge amount of disk space

[Andreas Beckmann]

On 14/03/2024 10.54, Paul Gevers wrote:
I just did. The biggest rise I saw (and I didn't even stop parallel 
runners) was ~5 GB, so this version seems fine.


Please let me know when the other versions are fixed too.


Thanks. I'll upgrade the other ones over the next days, closing the 
existing bug again with each upload.


Don't hesitate to yell if you notice something suspiciously straining on 
the CI ;-)



Andreas

Bug#1066840: no mention of iproute2 6.7.0-2.1 in changelog

[Aníbal Monsalve Salazar]

Package: iproute2
Version: 6.8.0-1
Severity: important

Dear Maintainer,

At https://tracker.debian.org/pkg/iproute2 it reads:
[2024-03-12] Accepted iproute2 6.7.0-2.1 (source) into unstable (Helmut Grohne) 

I cannot find the changelog entry listed below for iproute2 6.7.0-2.1 in
the changelog of iproute2 6.8.0-1.

iproute2 (6.7.0-2.1) unstable; urgency=medium

  * Non-maintainer upload.
  * Explicitly depend on libtirpc-dev. (Closes: #1065214)

 -- Helmut Grohne   Tue, 12 Mar 2024 09:03:30 +0100

Thank you,

Aníbal

Bug#1066778: golang-github-containerd-go-runc: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/containerd/go-runc returned exit code 1

[Shengjing Zhu]

On Wed, Mar 13, 2024 at 11:05 PM Lucas Nussbaum  wrote:
>
> Source: golang-github-containerd-go-runc
> Version: 1.0.0-1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20240313 ftbfs-trixie
>
[...]
> > console_test.go:42: mkdir /tmp/foo: not a directory
> > --- FAIL: TestTempConsoleWithXdgRuntimeDir (0.00s)

I wonder if your chroot doesn't have the /tmp directory?

-- 
Shengjing Zhu

Bug#1064976:

[Colm Buckley]

Hey folks -

I see that linux-headers-* has been promoted to 6.6 in the BPO channel, but
this dependency is still in place.
Is it really the case that we want to drag in the image binaries and other
machinery as a dependency for a source package like linux-headers.
I feel that the BPF use case should really be addressed using vmlinux.h
(the "skipping BTF generation" message should be ignored as all of this
information *should* be included in vmlinux.h).
Any further thoughts?

Colm

Bug#1065395: spirv-llvm-translator-14: autopkgtest on s390x uses huge amount of disk space

[Paul Gevers]

Hi,

On 12-03-2024 10:18 a.m., Andreas Beckmann wrote:

On 06/03/2024 06.20, Paul Gevers wrote:

Unfortunately the test still takes upto 33 GB at least (see below).


Did you have time to test the -12 version, yet?


I just did. The biggest rise I saw (and I didn't even stop parallel 
runners) was ~5 GB, so this version seems fine.


Please let me know when the other versions are fixed too.

Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1066837: mpi4py: FTBFS: Unable to generate documentation

[Zixing Liu]

Package: mpi4py
Severity: serious
Tags: patch
User: zixing@canonical.com
Usertags: origin-ubuntu noble ubuntu-patch

Dear Maintainer,

mpi4py failed to build from source after Python 3.12 and Sphinx upgrade.
Please find the patch attached that fixes the Sphinx documentation generation
issue and also a partial fix to the InterSphinx online requirements.

Due to a packaging issue in numpy, the InterSphinx of numpy isn't included
in the package, so linking the documentation from numpy is not possible
at the moment.

  * Un-break Sphinx documentation generation by removing PYTHONPATH overrides.
  * Add a patch to make Intersphinx read the cross-documentation index
from local filesystem. (LP: #2057848)


Thanks for considering the patch.


-- System Information:
Debian Release: bookworm/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-25-generic (SMP w/10 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru mpi4py-3.1.5/debian/control mpi4py-3.1.5/debian/control
--- mpi4py-3.1.5/debian/control 2024-03-13 12:30:07.0 -0600
+++ mpi4py-3.1.5/debian/control 2024-03-13 15:33:29.0 -0600
@@ -17,7 +16,8 @@
python3-setuptools
 Build-Depends-Indep: texinfo, texlive,
  latexmk, tex-gyre,
- texlive-latex-extra
+ texlive-latex-extra,
+ python3-doc
 Standards-Version: 4.6.2
 Vcs-Browser: https://salsa.debian.org/science-team/mpi4py
 Vcs-Git: https://salsa.debian.org/science-team/mpi4py.git
diff -Nru mpi4py-3.1.5/debian/patches/intersphinx_use_local_inventory.patch 
mpi4py-3.1.5/debian/patches/intersphinx_use_local_inventory.patch
--- mpi4py-3.1.5/debian/patches/intersphinx_use_local_inventory.patch   
1969-12-31 17:00:00.0 -0700
+++ mpi4py-3.1.5/debian/patches/intersphinx_use_local_inventory.patch   
2024-03-13 15:33:29.0 -0600
@@ -0,0 +1,18 @@
+Description: Use local InterSphinx inventory data
+Author: Zixing Liu 
+Forwarded: not-needed
+Last-Update: 2024-03-13
+
+Index: mpi4py/docs/source/usrman/conf.py
+===
+--- mpi4py.orig/docs/source/usrman/conf.py
 mpi4py/docs/source/usrman/conf.py
+@@ -90,7 +90,7 @@ autosummary_context = {
+ }
+ 
+ intersphinx_mapping = {
+-'python': ('https://docs.python.org/3/', None),
++'python': ('https://docs.python.org/3/', 
('/usr/share/doc/python3/html/objects.inv', None)),
+ 'numpy': ('https://numpy.org/doc/stable/', None),
+ }
+ 
diff -Nru mpi4py-3.1.5/debian/patches/series mpi4py-3.1.5/debian/patches/series
--- mpi4py-3.1.5/debian/patches/series  2024-02-20 03:49:49.0 -0700
+++ mpi4py-3.1.5/debian/patches/series  2024-03-13 15:29:22.0 -0600
@@ -7,3 +7,4 @@
 docs_privacy.patch
 io_long_double_i386_2d868d7.patch
 skip_testPackUnpackExternal_sparc64.patch
+intersphinx_use_local_inventory.patch
diff -Nru mpi4py-3.1.5/debian/rules mpi4py-3.1.5/debian/rules
--- mpi4py-3.1.5/debian/rules   2024-02-20 03:49:49.0 -0700
+++ mpi4py-3.1.5/debian/rules   2024-03-13 15:28:23.0 -0600
@@ -64,8 +64,7 @@
--build-args "--mpicc=/usr/bin/mpicc$(MPI) 
--mpicxx=/usr/bin/mpicxx$(MPI)"
 
 override_dh_auto_build-indep: override_dh_auto_build-arch
-   PYTHONPATH=`pybuild --print "{build_dir}"` \
-make -C docs/source/usrman/ html man info latexpdf SPHINXOPTS="-D 
today=\"$(BUILD_DATE)\""
+   make -C docs/source/usrman/ html man info latexpdf SPHINXOPTS="-D 
today=\"$(BUILD_DATE)\""
 
 override_dh_auto_install:
dh_auto_install

Bug#1066839: pipewire: ftbfs with 64-bit time_t

[Steve Langasek]

Package: pipewire
Version: 1.0.3-1.1
Severity: serious
Tags: patch
Justification: ftbfs
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch

Dear maintainers,

pipewire fails to build from source on 32-bit architectures under 64-bit
time_t, because it has a module that legitimately un-sets _FILE_OFFSET_BITS
for building but this is not allowed without also unsetting _TIME_BITS.

Since this is a legitimate un-setting of _FILE_OFFSET_BITS in order to get
access to the necessary libc6 prototypes and macros, and since the functions
being intercepted are not sensitive to time_t, the simplest solution is to
also unset _TIME_BITS.

Please see the attached patch, which has been uploaded to Ubuntu to fix this
build failure.

Thanks for considering,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru pipewire-1.0.3/debian/control pipewire-1.0.3/debian/control
--- pipewire-1.0.3/debian/control   2024-03-04 08:54:55.0 -0800
+++ pipewire-1.0.3/debian/control   2024-03-13 23:11:56.0 -0700
@@ -1,8 +1,7 @@
 Source: pipewire
 Section: libs
 Priority: optional
-Maintainer: Ubuntu Developers 
-XSBC-Original-Maintainer: Utopia Maintenance Team 

+Maintainer: Utopia Maintenance Team 

 Uploaders: Jeremy Bicha ,
Dylan Aïssi 
 Build-Depends: dpkg-dev (>= 1.22.5), debhelper-compat (= 13),
diff -Nru pipewire-1.0.3/debian/patches/64-bit-time-t-compat.patch 
pipewire-1.0.3/debian/patches/64-bit-time-t-compat.patch
--- pipewire-1.0.3/debian/patches/64-bit-time-t-compat.patch1969-12-31 
16:00:00.0 -0800
+++ pipewire-1.0.3/debian/patches/64-bit-time-t-compat.patch2024-03-13 
23:11:47.0 -0700
@@ -0,0 +1,21 @@
+Description: 64-bit time_t compatibility for v4l2 module
+ The v4l2 build unsets _FILE_OFFSET_BITS, which is not allowed when setting
+ _TIME_BITS=64.  Having verified that nothing in this module is sensitive to
+ 64-bit time_t (none of the functions it intercepts handle time), we also
+ unset _TIME_BITS to allow this to build as before.
+Author: Steve Langasek 
+Forwarded: no
+Last-Update: 2024-03-13
+
+Index: pipewire-1.0.3/pipewire-v4l2/src/meson.build
+===
+--- pipewire-1.0.3.orig/pipewire-v4l2/src/meson.build
 pipewire-1.0.3/pipewire-v4l2/src/meson.build
+@@ -12,6 +12,7 @@
+   '-U_FILE_OFFSET_BITS',
+   '-D_FILE_OFFSET_BITS=32',
+   '-D_LARGEFILE64_SOURCE',
++  '-U_TIME_BITS',
+   '-fvisibility=hidden',
+ ]
+ 
diff -Nru pipewire-1.0.3/debian/patches/series 
pipewire-1.0.3/debian/patches/series
--- pipewire-1.0.3/debian/patches/series2024-03-04 08:54:55.0 
-0800
+++ pipewire-1.0.3/debian/patches/series2024-03-13 23:09:06.0 
-0700
@@ -19,3 +19,4 @@
 snap/snap-policy-Manage-ENOPROTOOPT-error-in-aa_getpeercon.patch
 snap/snap-policy-ensure-audio-works-with-.deb-snapd.patch
 snap/snap-policy-fix-memory-leak.patch
+64-bit-time-t-compat.patch

Bug#1066279: [Debian-zh-dev] Bug#1066279: Bug#1066279: unicon: FTBFS: cin2tab.c:238:13: error: implicit declaration of function ‘tolower’ [-Werror=implicit-function-declaration]

[Aron Xu]

On Thu, Mar 14, 2024 at 10:34 AM xiao sheng wen  wrote:
>
> Hi,
>
> Thanks for your report.
>
> I'd uploaded the new version in mentors to fix this bug.
>
> https://mentors.debian.net/package/unicon/
>
> Welcome to review and upload.
>

This has been sponsored to Sid, thanks for your contribution!

Regards,
Aron

Bug#1061769: Unexpected VLAN behavior with KEA DHCP

[kristofer.hansson]

Hi Paride.

Thanks for the answer and while it was not the answer I hoped for I completely 
understand and sympathize with your decision.

I'll see if I can get the ISC team to take another look at the issue.

Regards Kristofer

EQUANS Mail Disclaimer: https://www.equans.com/disclaimer/disclaimer-mail/en

Bug#1066845: gnome-genius: Is Genius really proprietary?

[Christian Böck]

Package: gnome-genius
Version: 1.0.27-1+b1
Severity: minor
X-Debbugs-Cc: deb...@funtech.org

Dear Maintainer,

According to the "Software"-tool Genius is proprietary software.
But when you visit its homepage it is licensed under the GPL and sources can be
downloaded.

Not realy a bug, but I think it should be fixed anyways.

Sincerely
Chris


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

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

Versions of packages gnome-genius depends on:
ii  genius-common 1.0.27-1
ii  libc6 2.36-9+deb12u4
ii  libcairo2 1.16.0-7
ii  libgdk-pixbuf-2.0-0   2.42.10+dfsg-1+b1
ii  libglib2.0-0  2.74.6-2
ii  libgmp10  2:6.2.1+dfsg1-1.1
ii  libgtk-3-03.24.38-2~deb12u1
ii  libgtksourceview-4-0  4.8.4-4
ii  libmpfr6  4.2.0-1
ii  libpango-1.0-01.50.12+ds-1
ii  libpangocairo-1.0-0   1.50.12+ds-1
ii  libreadline8  8.2-1.3
ii  libvte-2.91-0 0.70.6-2~deb12u1

gnome-genius recommends no packages.

gnome-genius suggests no packages.

-- no debconf information

Bug#1066263: xfonts-utils: FTBFS: ../fonttosfnt/util.c:89:10: error: implicit declaration of function ‘vasprintf’; did you mean ‘vsprintf’? [-Werror=implicit-function-declaration]

[Thomas Dickey]

On Wed, Mar 13, 2024 at 10:44:07PM +0500, Andrey Rakhmatullin wrote:
> On Wed, Mar 13, 2024 at 12:46:49PM +0100, Lucas Nussbaum wrote:
> > > ../fonttosfnt/util.c: In function ‘vsprintf_alloc’:
> > > ../fonttosfnt/util.c:89:10: error: implicit declaration of function 
> > > ‘vasprintf’; did you mean ‘vsprintf’? 
> > > [-Werror=implicit-function-declaration]
> Looks like it's caused by the lack of -D_GNU_SOURCE, not sure who should
> set it. There is a very old debian/changelog entry about temporarily
> setting it from d/rules and fonttosfnt/write.c sets it but
> fonttosfnt/util.c doesn't and there is nothing related in the autotools
> stuff.

The Debian rules file is rather old, which may be the problem.

https://salsa.debian.org/xorg-team/font/xfonts-utils

In my (other) test packages, I haven't had to add -D_DEFAULT_SOURCE,**
only for non-package builds has that been necessary.

** -D_GNU_SOURCE should only be used for the rare program relying upon
   non-POSIX interfaces.

-- 
Thomas E. Dickey 
https://invisible-island.net


signature.asc
Description: PGP signature

Bug#1066836: libcamera: ftbfs with 64-bit time_t

[Dylan Aïssi]

Hi Kieran,

I guess this task is for me ;-)
Yes, I will submit it.

Best,
Dylan


On 3/14/24 13:04, Kieran Bingham wrote:

Hi Steve,

do you also plan to submit this to the libcamera-devel mailing list?

--
Kieran

Quoting Steve Langasek (2024-03-14 05:35:04)

Package: libcamera
Version: 0.2.0-1
Severity: serious
Tags: patch
Justification: ftbfs
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch

Dear maintainers,

libcamera fails to build from source on 32-bit architectures under 64-bit
time_t, because it has a module that legitimately un-sets _FILE_OFFSET_BITS
for building but this is not allowed without also unsetting _TIME_BITS:

[...]
[267/430] c++ -Isrc/v4l2/v4l2-compat.so.p -Isrc/v4l2 -I../src/v4l2 -Iinclude -I../include -Iinclude/libcamera/ipa 
-Iinclude/libcamera -fdiagnostics-color=always -Wall -Winvalid-pch -Wextra -Werror -std=c++17 -Wno-redundant-move 
-Wno-psabi -Wshadow -include /<>/obj-arm-linux-gnueabihf/config.h -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security 
-fno-stack-clash-protection -fdebug-prefix-map=/<>=/usr/src/libcamera-0.2.0-1ubuntu3 
-Wno-error -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=3 -fPIC 
-DLIBCAMERA_BASE_PRIVATE -U_FILE_OFFSET_BITS -D_FILE_OFFSET_BITS=32 -D_LARGEFILE64_SOURCE -fvisibility=hidden -MD 
-MQ src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o -MF src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o.d -o 
src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o -c ../src/v4l2/v4l2_camera.cpp
FAILED: src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o
c++ -Isrc/v4l2/v4l2-compat.so.p -Isrc/v4l2 -I../src/v4l2 -Iinclude -I../include -Iinclude/libcamera/ipa 
-Iinclude/libcamera -fdiagnostics-color=always -Wall -Winvalid-pch -Wextra -Werror -std=c++17 -Wno-redundant-move 
-Wno-psabi -Wshadow -include /<>/obj-arm-linux-gnueabihf/config.h -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security 
-fno-stack-clash-protection -fdebug-prefix-map=/<>=/usr/src/libcamera-0.2.0-1ubuntu3 
-Wno-error -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=3 -fPIC 
-DLIBCAMERA_BASE_PRIVATE -U_FILE_OFFSET_BITS -D_FILE_OFFSET_BITS=32 -D_LARGEFILE64_SOURCE -fvisibility=hidden -MD 
-MQ src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o -MF src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o.d -o 
src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o -c ../src/v4l2/v4l2_camera.cpp
In file included from /usr/include/features.h:394,
  from 
/usr/include/arm-linux-gnueabihf/c++/13/bits/os_defines.h:39,
  from 
/usr/include/arm-linux-gnueabihf/c++/13/bits/c++config.h:679,
  from /usr/include/c++/13/bits/requires_hosted.h:31,
  from /usr/include/c++/13/deque:60,
  from ../src/v4l2/v4l2_camera.h:10,
  from ../src/v4l2/v4l2_camera.cpp:8:
/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"
   | ^
[...]

   
(https://launchpad.net/ubuntu/+source/libcamera/0.2.0-1ubuntu3/+build/27902670)

Since this is a legitimate un-setting of _FILE_OFFSET_BITS in order to get
access to the necessary libc6 prototypes and macros, and since the functions
being intercepted are not sensitive to time_t, the simplest solution is to
also unset _TIME_BITS.

Please see the attached patch, which has been uploaded to Ubuntu to fix this
build failure.

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


--
Dylan Aïssi
Software Engineer

Collabora Ltd.
Platinum Building, St John's Innovation Park, Cambridge CB4 0DS, UK
Registered in England & Wales, no. 5513718

Bug#1066852: don't hard-code the name of the shared library

[Matthias Klose]

Package: src:binwalk
Version: 2.3.4+dfsg1-4
Severity: serious
Tags: sid trixie

the package depends on libmagic1. The name was recently changed to 
libmagic1t64.  Please don't hard-code it, but try to b-d on 
libmagic-dev, and derive the name of the shared library package from the 
libmagic-dev package.

Bug#1066853: don't hard-code the name of the shared library

[Matthias Klose]

Package: src:roundcube
Version: 0.2.9-3
Severity: serious
Tags: sid trixie

the package depends on libmagic1. The name was recently changed to 
libmagic1t64.  Please don't hard-code it, but try to b-d on 
libmagic-dev, and derive the name of the shared library package from the 
libmagic-dev package.

Bug#1066854: don't hard-code the name of the shared library

[Matthias Klose]

Package: src:ruby-magic
Version: 0.2.9-3
Severity: serious
Tags: sid trixie

the package build-depends on libmagic1, and depends on it. The name was 
recently changed to libmagic1t64.  Please don't hard-code it, but try to 
b-d on libmagic-dev, and derive the name of the shared library package 
from the libmagic-dev package.

Bug#1065327: ITA: python-levenshtein

[Louis-Philippe Véronneau]

retitle 1065327 ITA: python-levenshtein -- extension for computing string 
similarities and edit distances (Python 3)
owner 1065327 Louis-Philippe Véronneau 
thanks

I need this package for sublime-music and since it's being orphaned, I'm 
planning to adopt it.

If someone else wants to maintain this package though, I won't fight you for it 
:)

Cheers (and thanks to morph for the work so far),

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄

Bug#1066411: webkit2gtk: FTBFS: SharedContextMutex.cpp:219:41: error: inlining failed in call to ‘always_inline’ ‘egl::SharedContextMutex* egl::SharedContextMutex::doTryLock() [with Mute

[Jeremy Bícha]

On Thu, Mar 14, 2024 at 10:51 AM Alberto Garcia  wrote:
> - Several undefined references at link time. This is reported upstream
>   as https://bugs.webkit.org/show_bug.cgi?id=270970 and is still not
>   fixed.
>
> I thought these were caused by the new version of gcc in sid but I
> tried downgrading the packages and the problem is still there. In
> trixie everything works fine.

It is caused by a changed in dpkg in Unstable

https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Thank you,
Jeremy Bícha

Bug#1066850: don't hard-code the name of the shared library

[Matthias Klose]

Package: src:python-magic
Version: 2:0.4.27-2
Severity: serious
Tags: sid trixie

the package build-depends on libmagic1, and depends on it. The name was 
recently changed to libmagic1t64.  Please don't hard-code it, but try to 
b-d on libmagic-dev, and derive the name of the shared library package 
from the libmagic-dev package.

Bug#1066851: don't hard-code the name of the shared library

[Matthias Klose]

Package: src:raku-readline
Version: 0.1.6-3
Severity: serious
Tags: sid trixie

the package build-depends on libreadline8, and depends on it. The name 
was recently changed to libreadline8t64.  Please don't hard-code it, but 
try to b-d on libreadline-dev, and derive the name of the shared library 
package from the libreadline-dev package.

Bug#1066836: libcamera: ftbfs with 64-bit time_t

[Kieran Bingham]

Hi Steve,

do you also plan to submit this to the libcamera-devel mailing list?

--
Kieran

Quoting Steve Langasek (2024-03-14 05:35:04)
> Package: libcamera
> Version: 0.2.0-1
> Severity: serious
> Tags: patch
> Justification: ftbfs
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu noble ubuntu-patch
> 
> Dear maintainers,
> 
> libcamera fails to build from source on 32-bit architectures under 64-bit
> time_t, because it has a module that legitimately un-sets _FILE_OFFSET_BITS
> for building but this is not allowed without also unsetting _TIME_BITS:
> 
> [...]
> [267/430] c++ -Isrc/v4l2/v4l2-compat.so.p -Isrc/v4l2 -I../src/v4l2 -Iinclude 
> -I../include -Iinclude/libcamera/ipa -Iinclude/libcamera 
> -fdiagnostics-color=always -Wall -Winvalid-pch -Wextra -Werror -std=c++17 
> -Wno-redundant-move -Wno-psabi -Wshadow -include 
> /<>/obj-arm-linux-gnueabihf/config.h -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -fno-stack-clash-protection 
> -fdebug-prefix-map=/<>=/usr/src/libcamera-0.2.0-1ubuntu3 
> -Wno-error -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 
> -Wdate-time -D_FORTIFY_SOURCE=3 -fPIC -DLIBCAMERA_BASE_PRIVATE 
> -U_FILE_OFFSET_BITS -D_FILE_OFFSET_BITS=32 -D_LARGEFILE64_SOURCE 
> -fvisibility=hidden -MD -MQ src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o -MF 
> src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o.d -o 
> src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o -c ../src/v4l2/v4l2_camera.cpp
> FAILED: src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o 
> c++ -Isrc/v4l2/v4l2-compat.so.p -Isrc/v4l2 -I../src/v4l2 -Iinclude 
> -I../include -Iinclude/libcamera/ipa -Iinclude/libcamera 
> -fdiagnostics-color=always -Wall -Winvalid-pch -Wextra -Werror -std=c++17 
> -Wno-redundant-move -Wno-psabi -Wshadow -include 
> /<>/obj-arm-linux-gnueabihf/config.h -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -fno-stack-clash-protection 
> -fdebug-prefix-map=/<>=/usr/src/libcamera-0.2.0-1ubuntu3 
> -Wno-error -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 
> -Wdate-time -D_FORTIFY_SOURCE=3 -fPIC -DLIBCAMERA_BASE_PRIVATE 
> -U_FILE_OFFSET_BITS -D_FILE_OFFSET_BITS=32 -D_LARGEFILE64_SOURCE 
> -fvisibility=hidden -MD -MQ src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o -MF 
> src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o.d -o 
> src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o -c ../src/v4l2/v4l2_camera.cpp
> In file included from /usr/include/features.h:394,
>  from 
> /usr/include/arm-linux-gnueabihf/c++/13/bits/os_defines.h:39,
>  from 
> /usr/include/arm-linux-gnueabihf/c++/13/bits/c++config.h:679,
>  from /usr/include/c++/13/bits/requires_hosted.h:31,
>  from /usr/include/c++/13/deque:60,
>  from ../src/v4l2/v4l2_camera.h:10,
>  from ../src/v4l2/v4l2_camera.cpp:8:
> /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"
>   | ^
> [...]
> 
>   
> (https://launchpad.net/ubuntu/+source/libcamera/0.2.0-1ubuntu3/+build/27902670)
> 
> Since this is a legitimate un-setting of _FILE_OFFSET_BITS in order to get
> access to the necessary libc6 prototypes and macros, and since the functions
> being intercepted are not sensitive to time_t, the simplest solution is to
> also unset _TIME_BITS.
> 
> Please see the attached patch, which has been uploaded to Ubuntu to fix this
> build failure.
> 
> Thanks for considering,
> -- 
> Steve Langasek   Give me a lever long enough and a Free OS
> Debian Developer   to set it on, and I can move the world.
> Ubuntu Developer   https://www.debian.org/
> slanga...@ubuntu.com vor...@debian.org

Bug#1066857: doc-debian: /usr/share/doc/debian/bug-reporting.txt should not be compressed

[Joost van Baal-Ilić]

Hi Vincent,

Thanks for this nice bugreport, will get to it.

Bye,

Joost

On Thu, Mar 14, 2024 at 02:31:11PM +0100, Vincent Lefevre wrote:
> Package: doc-debian
> Version: 11.3+nmu1
> Severity: wishlist
> 
> The bug-reporting.txt file is rather small, thus it does not need to
> be compressed. Having it compressed like currently breaks references,
> such as in the apt-get(8) man page, which says
> 
>   APT bug page[1]. If you wish to report a bug in APT, please see
>   /usr/share/doc/debian/bug-reporting.txt or the reportbug(1) command.
> 
> and in /usr/share/doc/debian/FAQ/support.en.html too, while only
> /usr/share/doc/debian/bug-reporting.txt.gz exists.
> 
> -- System Information:
> Debian Release: trixie/sid
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
> 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), 
> (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 6.6.15-amd64 (SMP w/12 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
> TAINT_UNSIGNED_MODULE
> Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> doc-debian depends on no packages.
> 
> Versions of packages doc-debian recommends:
> ii  debian-faq  11.1
> 
> Versions of packages doc-debian suggests:
> ii  atril [postscript-viewer]   1.26.2-1.1+b1
> ii  elinks [www-browser]0.16.1.1-4.1+b2
> ii  firefox [www-browser]   123.0.1-1
> hi  firefox-esr [www-browser]   92.0-local
> ii  ghostscript [postscript-viewer] 10.02.1~dfsg-3+b1
> ii  gv [postscript-viewer]  1:3.7.4-2+local1
> ii  links [www-browser] 2.29-1+b3
> ii  links2 [www-browser]2.29-1+b3
> ii  lynx [www-browser]  2.9.0rel.0-2+b1
> ii  qpdfview-ps-plugin [postscript-viewer]  0.5.0+ds-4
> ii  w3m [www-browser]   0.5.3+git20230121-2+b3
> ii  zathura-ps [postscript-viewer]  0.2.7-2+b2
> 
> -- no debconf information
> 
> -- 
> Vincent Lefèvre  - Web: 
> 100% accessible validated (X)HTML - Blog: 
> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
> 

Bug#1066859: ITP: lomiri-system-settings-online-accounts -- Online Accounts setup for Lomiri

[Mike Gabriel]

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

* Package name: lomiri-system-settings-online-accounts
  Version : 0.10
  Upstream Contact: Alberto Mardegan 
* URL : 
https://gitlab.com/ubports/development/core/lomiri-system-settings-online-accounts/
* License : GPL-3, LGPL-3
  Programming Lang: C++ / QML
  Description : Online Accounts setup for Lomiri

 Lomiri-system-settings is the System Settings application used in Lomiri
 operating environment. it's designed for phones, tablets and convergent
 devices.
 .
 This package will contains the online accounts setup utility for Lomiri
 System Settings as well as the OnlineAccountsClient shared library for
 plumbing OnlineAccounts functionality into client applications.
 .
 This package will be maintained under the umbrella of the Debian UBports
 Packaging Team.

Bug#1066337: tightvnc: FTBFS: vncconnect.c:17:5: error: implicit declaration of function ‘exit’ [-Werror=implicit-function-declaration]

[Sven Geuer]

Hi Lucas,

On Wed, 2024-03-13 at 12:45 +0100, Lucas Nussbaum wrote:
> Source: tightvnc
> Version: 1:1.3.10-7
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> This is most likely caused by a change in dpkg 1.22.6, that enabled
> -Werror=implicit-function-declaration. For more information, see
> https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

That is hard to correct,
- this software is abandonware
- there are about 250 warnings regarding implicit function declaration,
- there is no generic way to get rid of them.

I had a closer look revealing that there are many different cases to
consider. I am afraid it will take weeks or even months to fix this
bug.

On the other hand I could override dpkg by injecting
-Wno-error=implicit-function-declaration. Would that be acceptable?

Cheers,
Sven
-- 
GPG Fingerprint
3DF5 E8AA 43FC 9FDF D086 F195 ADF5 0EDA F8AD D585


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

Bug#1066829: ITP: assetfinder -- Find domains and subdomains related to a given domain

[Henrique de Moraes Holschuh]

Hello,

On Wed, Mar 13, 2024, at 21:47, aquilamac...@riseup.net wrote:
> * Package name: assetfinder
>   Version : 0.1.1
>   Upstream Contact: Tom Hudson 
> * URL : https://github.com/tomnomnom/assetfinder
> * License : MIT 
>   Programming Lang: Golang
>   Description : Find domains and subdomains related to a given
> domain

Please consider a less generic name, there are many assets in the world one 
might want to search for using software, dns domains and subdomains are not 
even remotely on the top of that list for most people.

May I humbly suggest "dns-assetfinder" ?

It might be a very good idea to talk to upstream first.

-- 
  Henrique de Moraes Holschuh 

Bug#1066847: openssh: please consider disabling ssh-askpass-gnome on 32-bit during the time_t transition

[Simon McVittie]

Source: openssh
Severity: wishlist
Tags: patch
X-Debbugs-Cc: debian-...@lists.debian.org

On the architectures affected by the 64-bit time_t transition, there
is at least one cyclic build-dependency involving this package:
openssh-server, gtk+3.0, at-spi2-core, dbus-broker, systemd, cryptsetup,
libssh, openssh-server.

I've tried to break this cycle at at-spi2-core (#1066844) but that's going
to require additional changes in gtk+3.0, to disable its test suite (which
requires librsvg, which requires Rust, which needs re-bootstrapping)
on the affected architectures, and at this stage I'm unsure whether other
relevant cycles exist.

I think it would be pragmatic to disable ssh-askpass-gnome on the affected
architectures for the duration of this transition: it's a low-popcon
leaf package which is the only thing pulling in "heavy" dependencies
to openssh. I attach a possible patch. I've verified that it compiles
successfully in an armhf porterbox chroot (without ssh-askpass-gnome)
and on amd64 (with ssh-askpass-gnome), but I haven't otherwise tested it.

Thanks,
smcv
>From bbefe785a6ab567677af77ccd12b1fbb59a42d8d Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Thu, 14 Mar 2024 10:48:03 +
Subject: [PATCH] d/control, d/rules: Disable ssh-askpass-gnome on 32-bit,
 except i386

On the architectures affected by the 64-bit time_t transition, there
is at least one cyclic build-dependency involving this package:
openssh-server, gtk+3.0, at-spi2-core, dbus-broker, systemd, cryptsetup,
libssh, openssh-server. Temporarily dropping a low-popcon binary package
that is already excludable by a build-profile seems like a convenient
place to break the cycle.

Closes: #-1
---
 debian/control | 2 +-
 debian/rules   | 6 ++
 2 files changed, 7 insertions(+), 1 deletion(-)

diff --git a/debian/control b/debian/control
index 0a785bcb2..38abe62ec 100644
--- a/debian/control
+++ b/debian/control
@@ -10,7 +10,7 @@ Build-Depends: debhelper (>= 13.1~),
libaudit-dev [linux-any],
libedit-dev,
libfido2-dev (>= 1.5.0) [linux-any],
-   libgtk-3-dev ,
+   libgtk-3-dev [!armel !armhf !hppa !m68k !powerpc !sh4] ,
libkrb5-dev | heimdal-dev,
libpam0g-dev | libpam-dev,
libselinux1-dev [linux-any],
diff --git a/debian/rules b/debian/rules
index fd9ab8d03..cd4c27b58 100755
--- a/debian/rules
+++ b/debian/rules
@@ -108,6 +108,10 @@ ifeq ($(shell dpkg-vendor --is Ubuntu && echo yes) $(DEB_HOST_ARCH), yes i386)
   BUILD_PACKAGES += -Nopenssh-tests
 endif
 
+ifeq ($(DEB_HOST_ARCH_BITS)$(filter i386,$(DEB_HOST_ARCH_CPU)),32)
+  BUILD_PACKAGES += -Nssh-askpass-gnome
+endif
+
 %:
 	dh $@ --with=runit $(BUILD_PACKAGES)
 
@@ -132,9 +136,11 @@ ifeq ($(filter noudeb,$(DEB_BUILD_PROFILES)),)
 	$(MAKE) -C debian/build-udeb $(PARALLEL) ASKPASS_PROGRAM='/usr/bin/ssh-askpass' ssh scp sftp sshd ssh-keygen
 endif
 
+ifneq ($(DEB_HOST_ARCH_BITS)$(filter i386,$(DEB_HOST_ARCH_CPU)),32)
 ifeq ($(filter pkg.openssh.nognome,$(DEB_BUILD_PROFILES)),)
 	$(MAKE) -C contrib gnome-ssh-askpass3 CC='$(CC) $(CPPFLAGS) $(CFLAGS) -Wall -Wl,--as-needed $(LDFLAGS)' PKG_CONFIG=$(PKG_CONFIG)
 endif
+endif
 
 override_dh_auto_build-indep:
 
-- 
2.43.0

Bug#1066848: freediameter: replace libidn11-dev with libidn-dev

[Simon Josefsson]

Package: freediameter
Version: 1.2.1-8
Tags: patch

Hi!  I'd like to drop the transitional package 'libidn11-dev' as most
packages have already moved to use 'libidn-dev' which is in stable.

How about this patch?

/Simon

diff --git a/debian/control b/debian/control
index 335362a..2856eae 100644
--- a/debian/control
+++ b/debian/control
@@ -8,7 +8,7 @@ Build-Depends: debhelper (>= 11),
libsctp-dev,
bison,
flex,
-   libidn11-dev,
+   libidn-dev,
libgcrypt20-dev,
libgnutls28-dev,
pkg-config,
@@ -63,7 +63,7 @@ Depends: libfdcore6 (= ${binary:Version}),
  libfdproto6 (= ${binary:Version}),
  libgnutls28-dev,
  libgcrypt20-dev,
- libidn11-dev,
+ libidn-dev,
  libsctp-dev,
  ${misc:Depends}
 Description: Library for the Diameter protocol (development files)


signature.asc
Description: PGP signature

Bug#1066849: libelf1 Version mismatch (0.190-1+b1 vs 0.191-1)

[Rémi DUCCESCHI]

Package: libelf1
Version: 0.190-1+b1

Hello,
It seems that since the last update (2 days ago), the version of the package
has not been updated.
When I check the version in Debian, it says 0.190-1+b1
(https://packages.debian.org/fr/sid/libelf1), but when I check the changelog,
I get .0191-1 
(https://metadata.ftp-master.debian.org/changelogs/main/e/elfutils/elfutils_0.191-1_changelog).

I guess libelf1 is linked to elfutils and should have the same version?

Apparently because of this, debootstrap is failing a new install of Debian Sid
from the daily mini.iso
(https://d-i.debian.org/daily-images/amd64/daily/netboot/):
dpkg --configure complains about mismatch versions.

Thanks for your work! If this is not the correct place for this, let me know
where to post it.

Best regards,

Bug#1007009: openboard: Wrongly displays "world map" image sample fixed upstream

[Martin Winter]

This bug is fixed upstream with commit 
741491539b129e4ecc7ffceb38ffc945177a7cf6 which is contained in the 
latest version 1.7.0.


OpenPGP_0x9DA10327E5DE0652.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1066074: ntfs-3g: broken shlibs (deb and udeb)

[Benjamin Drung]

On Tue, 12 Mar 2024 02:12:16 +0100 Cyril Brulebois 
wrote:
> Source: ntfs-3g
> Version: 1:2022.10.3-1.1
> Severity: serious
> Tags: d-i
> Justification: broken shlibs
> X-Debbugs-Cc: debian-b...@lists.debian.org, Benjamin Drung

> 
> Hi,
> 
> Here's what debian/libntfs-3g89t64/DEBIAN/shlibs looks like after
> a build:
> 
> libntfs-3g 89 libntfs-3g89
> udeb: libntfs-3g 89 libntfs-3g89
> 
> That doesn't match binaries shipped by the source package.
> 
> 
> See debian/rules:
> 
> SONAME = $(shell objdump -p debian/tmp/lib/*/libntfs-3g.so.*.* |
awk -Fso. '/SONAME/ { print $$2 }')
> 
> […]
> 
> override_dh_makeshlibs:
> dh_makeshlibs --add-udeb=ntfs-3g-udeb -Vlibntfs-
3g$(SONAME)
> 
> 
> In the previous version we had:
> 
> libntfs-3g 89 libntfs-3g89
> udeb: libntfs-3g 89 ntfs-3g-udeb
> 
> Adding 't64' at the end of the dh_makeshlibs line quoted above gives:
> 
> libntfs-3g 89 libntfs-3g89t64
> udeb: libntfs-3g 89 ntfs-3g-udeb
> 
> which certainly looks much better. I haven't performed any rebuild
test
> for the reverse dependencies of the library, nor runtime tests on the
> d-i side (other packages are broken right now). The Depends field of
> the udeb looks correct now though:
> 
> -Depends: libc6-udeb (>= 2.37), libntfs-3g89, fuse3-udeb
> +Depends: libc6-udeb (>= 2.37), fuse3-udeb
> 
> 
> I'll leave it up to the 64-bit time_t transition drivers to choose how
> to address this issue (add t64 on the SONAME line, or just in the
> dh_makeshlibs override, or something else), and to track down packages
> that might have been rebuilt against the broken library.

Attached the diff for the NMU upload.

-- 
Benjamin Drung
Debian & Ubuntu Developer
diff -Nru ntfs-3g-2022.10.3/debian/changelog ntfs-3g-2022.10.3/debian/changelog
--- ntfs-3g-2022.10.3/debian/changelog	2024-03-01 13:40:22.0 +0100
+++ ntfs-3g-2022.10.3/debian/changelog	2024-03-14 13:21:45.0 +0100
@@ -1,3 +1,11 @@
+ntfs-3g (1:2022.10.3-1.2) unstable; urgency=medium
+
+  [ Zixing Liu ]
+  * Non-maintainer upload.
+  * d/rules: add t64 suffix to the dh_makeshlib command. (Closes: #1066074)
+
+ -- Benjamin Drung   Thu, 14 Mar 2024 13:21:45 +0100
+
 ntfs-3g (1:2022.10.3-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru ntfs-3g-2022.10.3/debian/rules ntfs-3g-2022.10.3/debian/rules
--- ntfs-3g-2022.10.3/debian/rules	2022-10-31 15:14:06.0 +0100
+++ ntfs-3g-2022.10.3/debian/rules	2024-03-14 13:21:09.0 +0100
@@ -105,7 +105,7 @@
 	dh_link --remaining-packages
 
 override_dh_makeshlibs:
-	dh_makeshlibs --add-udeb=ntfs-3g-udeb -Vlibntfs-3g$(SONAME)
+	dh_makeshlibs --add-udeb=ntfs-3g-udeb -Vlibntfs-3g$(SONAME)t64
 
 .PHONY: override_dh_auto_configure override_dh_auto_install \
 	override_dh_installchangelogs \

Bug#1065309: transition: gnat 12 -> 13 + time_t64

[Graham Inggs]

Hi Nicolas, Matthias

On Sun, 3 Mar 2024 at 16:18, Nicolas Boulenguez  wrote:
> Ben file:
>
> title = "gnat-13";
> is_affected = .depends ~ 
> "libgnat-8/libgnat-9/libgnat-10/libgnat-11/libgnat-12" | .depends ~ 
> "libgnat-13";
> is_good = .depends ~ "libgnat-13";
> is_bad = .depends ~ "libgnat-8/libgnat-9/libgnat-10/libgnat-11/libgnat-12";

ben did not like the syntax, but I think I understood your intention
and set up a tracker [1].

After seeing the output, I tried to simplify it, and assumed that gcc
need not be included.  I set up a second version of the tracker [2].

Please let me know if these need further refinement.  If not, let me
know which tracker you prefer to keep.

Regards
Graham

[1] https://release.debian.org/transitions/html/gnat-13.html
[2] https://release.debian.org/transitions/html/gnat-13-v2.html

Bug#1066857: doc-debian: /usr/share/doc/debian/bug-reporting.txt should not be compressed

[Vincent Lefevre]

Package: doc-debian
Version: 11.3+nmu1
Severity: wishlist

The bug-reporting.txt file is rather small, thus it does not need to
be compressed. Having it compressed like currently breaks references,
such as in the apt-get(8) man page, which says

  APT bug page[1]. If you wish to report a bug in APT, please see
  /usr/share/doc/debian/bug-reporting.txt or the reportbug(1) command.

and in /usr/share/doc/debian/FAQ/support.en.html too, while only
/usr/share/doc/debian/bug-reporting.txt.gz exists.

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

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

doc-debian depends on no packages.

Versions of packages doc-debian recommends:
ii  debian-faq  11.1

Versions of packages doc-debian suggests:
ii  atril [postscript-viewer]   1.26.2-1.1+b1
ii  elinks [www-browser]0.16.1.1-4.1+b2
ii  firefox [www-browser]   123.0.1-1
hi  firefox-esr [www-browser]   92.0-local
ii  ghostscript [postscript-viewer] 10.02.1~dfsg-3+b1
ii  gv [postscript-viewer]  1:3.7.4-2+local1
ii  links [www-browser] 2.29-1+b3
ii  links2 [www-browser]2.29-1+b3
ii  lynx [www-browser]  2.9.0rel.0-2+b1
ii  qpdfview-ps-plugin [postscript-viewer]  0.5.0+ds-4
ii  w3m [www-browser]   0.5.3+git20230121-2+b3
ii  zathura-ps [postscript-viewer]  0.2.7-2+b2

-- no debconf information

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

Bug#1066858: RFA: python-ionoscloud

[Mattia Rizzolo]

Package: wnpp
Severity: wishlist

Hello!

So, I had to package this because of I needed the library.
However I have no particular attachments to it, and I'll happily hand it
over to anybody who has any interest.

It's a pretty straightforward python package, fully generated by
https://openapi-generator.tech and unless upstream changes they way to
work I doubt it will ever need any special expertise.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#1066411: webkit2gtk: FTBFS: SharedContextMutex.cpp:219:41: error: inlining failed in call to ‘always_inline’ ‘egl::SharedContextMutex* egl::SharedContextMutex::doTryLock() [with Mute

[Alberto Garcia]

Control: retitle -1 webkit2gtk: FTBFS due to several undefined references

On Wed, Mar 13, 2024 at 01:05:55PM +0100, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

Thanks, there are two build failures here:

- The one you reported (recursive inlining). This one is also
  affecting wpewebkit (#1066454) but I have a fix for it already.

- Several undefined references at link time. This is reported upstream
  as https://bugs.webkit.org/show_bug.cgi?id=270970 and is still not
  fixed.

I thought these were caused by the new version of gcc in sid but I
tried downgrading the packages and the problem is still there. In
trixie everything works fine.

Since the first problem is already taken care of I'm changing the
title of this bug to that of the second problem.

Berto

Bug#1066849: libelf1 Version mismatch (0.190-1+b1 vs 0.191-1)

[Matthias Klose]

time_t64 transitions in progress, you can't expect debootstrapping at 
this point.


On 14.03.24 12:04, Rémi DUCCESCHI wrote:

Package: libelf1
Version: 0.190-1+b1

Hello,
It seems that since the last update (2 days ago), the version of the package
has not been updated.
When I check the version in Debian, it says 0.190-1+b1
(https://packages.debian.org/fr/sid/libelf1), but when I check the changelog,
I get .0191-1 
(https://metadata.ftp-master.debian.org/changelogs/main/e/elfutils/elfutils_0.191-1_changelog).

I guess libelf1 is linked to elfutils and should have the same version?

Apparently because of this, debootstrap is failing a new install of Debian Sid
from the daily mini.iso
(https://d-i.debian.org/daily-images/amd64/daily/netboot/):
dpkg --configure complains about mismatch versions.

Thanks for your work! If this is not the correct place for this, let me know
where to post it.

Best regards,

Bug#1065309: transition: gnat 12 -> 13 + time_t64

[nicolas . boulenguez]

Hello.

Version 2 seems OK.

Thanks.

Bug#1036467: virtuoso-opensource: CVE-2023-31607 CVE-2023-31608 CVE-2023-31609 CVE-2023-31610 CVE-2023-31611 CVE-2023-31612 CVE-2023-31613 CVE-2023-31614 CVE-2023-31615 CVE-2023-31616 CVE-2023-31617 C

[Andreas Beckmann]

Control: severity -1 important
On Sun, 21 May 2023 20:43:40 +0200 Salvatore Bonaccorso 
 wrote:

Source: virtuoso-opensource
Version: 7.2.5.1+dfsg1-0.3
Severity: grave


Downgrading the severity since all CVEs are marked as no-dsa (minor issue).


Andreas

Bug#1066848: freediameter: replace libidn11-dev with libidn-dev

[Simon Josefsson]

Hi Ruben, all,

I have opened a merge request to resolve the bug below:

https://salsa.debian.org/debian-mobcom-team/freediameter/-/merge_requests/4

Are you able to merge and upload a new version?

If you agree, and add me to the Salsa group, I can merge it and prepare
the upload too.

/Simon

Simon Josefsson  writes:

> Package: freediameter
> Version: 1.2.1-8
> Tags: patch
>
> Hi!  I'd like to drop the transitional package 'libidn11-dev' as most
> packages have already moved to use 'libidn-dev' which is in stable.
>
> How about this patch?
>
> /Simon
>
> diff --git a/debian/control b/debian/control
> index 335362a..2856eae 100644
> --- a/debian/control
> +++ b/debian/control
> @@ -8,7 +8,7 @@ Build-Depends: debhelper (>= 11),
> libsctp-dev,
> bison,
> flex,
> -   libidn11-dev,
> +   libidn-dev,
> libgcrypt20-dev,
> libgnutls28-dev,
> pkg-config,
> @@ -63,7 +63,7 @@ Depends: libfdcore6 (= ${binary:Version}),
>   libfdproto6 (= ${binary:Version}),
>   libgnutls28-dev,
>   libgcrypt20-dev,
> - libidn11-dev,
> + libidn-dev,
>   libsctp-dev,
>   ${misc:Depends}
>  Description: Library for the Diameter protocol (development files)
>


signature.asc
Description: PGP signature

Bug#1066855: drop libidn11-dev

[Simon Josefsson]

Package: libidn
Version: 1.42-1

All packages should build against libidn-dev now, not libidn11-dev.
Current stable release of Debian ships libidn-dev.

The transitional libidn11-dev package can be dropped when all reverse
dependencies have stopped using it.

root@68d340bc8331:/# apt-cache rdepends libidn11-dev
libidn11-dev
Reverse Depends:
  libidn-dev
  libui-utilcpp-dev
  libloudmouth1-dev
  libidn-dev
  libfreediameter-dev
root@68d340bc8331:/# 

Loudmouth should be fixed by my team upload of 1.5.4-2.

ui-utilcpp maybe not a problem since they use 'libidn-dev|libidn11-dev'?

Remains freediameter, bug filed here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066848

I'm hoping we don't have to care about compatibility with oldstable.

/Simon


signature.asc
Description: PGP signature

Bug#1066016: python-rdflib-doc: please make the build reproducible.

[James Addison]

Package: python-rdflib-doc
Followup-For: Bug #1066016
X-Debbugs-Cc: cru...@debian.org

Hi Michael,

Thank you for merging and uploading this change.  Unfortunately it seems that
my suggestion didn't solve the problem (based on inspecting the results of a
recent reprotest[1] on Salsa - there's still a '' with
randomness in the built documentation).

That's my mistake for not testing the patch thoroughly enough.  Please let me
know how to proceed (for example, whether you'd prefer that I revert the
change).

This also means that the autodoc config setting may be more limited in
solving these kind of problems that I realized; I'll have to check some merge
requests that I have open for other packages.

Thank you,
James

[1] - https://salsa.debian.org/python-team/packages/rdflib/-/jobs/5445372

Bug#1066856: apt: please update the URLs in the man pages

[Vincent Lefevre]

Package: apt
Version: 2.7.13+b1
Severity: minor

The URLs in the man pages should be updated. For instance, concerning
the b.d.o URLs in the various man pages, "http" should be changed to
"https".

In the apt-cache(8) man page:

http://www.research.att.com/sw/tools/graphviz/ gives a "Page Not Found"
error.

http://rw4.cs.uni-sb.de/users/sander/html/gsvcg1.html should be
changed to
https://www.rw.cdl.uni-saarland.de/people/sander/private/html/gsvcg1.html


-- Package-specific info:

-- (no /etc/apt/preferences present) --


-- (/etc/apt/preferences.d/no-adobe-flash-plugin present, but not submitted) --


-- (/etc/apt/preferences.d/no-pipewire present, but not submitted) --


-- (/etc/apt/sources.list present, but not submitted) --


-- (/etc/apt/sources.list.d/local-i386.list present, but not submitted) --


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

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

Versions of packages apt depends on:
ii  adduser 3.137
ii  base-passwd 3.6.3
ii  debian-archive-keyring  2023.4
ii  gpgv2.2.40-2
ii  libapt-pkg6.0t642.7.13+b1
ii  libc6   2.37-15.1
ii  libgcc-s1   14-20240303-1
ii  libgnutls30t64  3.8.3-1.1
ii  libseccomp2 2.5.5-1
ii  libstdc++6  14-20240303-1
ii  libsystemd0 255.4-1+b1

Versions of packages apt recommends:
ii  ca-certificates  20240203

Versions of packages apt suggests:
ii  apt-doc 2.7.13
ii  aptitude0.8.13-5+b2
ii  dpkg-dev1.22.6
ii  gnupg   2.2.40-2
ii  powermgmt-base  1.37

-- no debconf information

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

Bug#1066016: python-rdflib-doc: please make the build reproducible.

[Michael R. Crusoe]

control: repopen -1

On Thu, 14 Mar 2024 13:04:29 + James Addison  wrote:
> Hi Michael,
>
> Thank you for merging and uploading this change. Unfortunately it 
seems that
> my suggestion didn't solve the problem (based on inspecting the 
results of a
> recent reprotest[1] on Salsa - there's still a 'identifier=>' with

> randomness in the built documentation).
>
> That's my mistake for not testing the patch thoroughly enough. Please 
let me

> know how to proceed (for example, whether you'd prefer that I revert the
> change).

Well, the build failed, so the CI on Salsa wasn't able to test your MR. 
No worries, it isn't your fault!


I think the patch still helped, we can keep it while you continue your 
investigations. I really appreciate it!



--
Michael R. Crusoe



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1066861: apt-get wants to remove packages instead of upgrading

[Vincent Lefevre]

Package: apt
Version: 2.7.13+b1
Severity: important

When I type "apt-get install libreoffice" to upgrade libreoffice,
apt-get wants to remove wine32:i386, while
"apt-get install libreoffice wine32:i386" shows that the upgrade
is actually possible without removing wine32:i386.

Debug information (attached) shows that in the former case:

Broken libgav1-1:i386 Depends on libabsl20220623:i386 < 20220623.1-3 @ii pmR > 
(>= 0~20220623.0-1)
  Considering libabsl20220623:i386 0 as a solution to libgav1-1:i386 2
  Added libabsl20220623:i386 to the remove list

while it could be upgraded to libabsl20220623t64:i386 instead.

I've attached the output of the following commands:

apt-get install -s -o Debug::pkgProblemResolver=true -o 
Debug::pkgDepCache::AutoInstall=true libreoffice >& out1

apt-get install -s -o Debug::pkgProblemResolver=true -o 
Debug::pkgDepCache::AutoInstall=true libreoffice wine32:i386 >& out2

-- Package-specific info:

-- apt-config dump --

APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "1";
APT::Install-Suggests "0";
APT::Key "";
APT::Key::Assert-Pubkey-Algo ">=rsa2048,ed25519,ed448";
APT::Sandbox "";
APT::Sandbox::User "_apt";
APT::Authentication "";
APT::Authentication::TrustCDROM "true";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*$";
APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*-[a-z0-9]*$";
APT::VersionedKernelPackages "";
APT::VersionedKernelPackages:: "linux-.*";
APT::VersionedKernelPackages:: "kfreebsd-.*";
APT::VersionedKernelPackages:: "gnumach-.*";
APT::VersionedKernelPackages:: ".*-modules";
APT::VersionedKernelPackages:: ".*-kernel";
APT::Never-MarkAuto-Sections "";
APT::Never-MarkAuto-Sections:: "metapackages";
APT::Never-MarkAuto-Sections:: "tasks";
APT::Move-Autobit-Sections "";
APT::Move-Autobit-Sections:: "oldlibs";
APT::AutoRemove "";
APT::AutoRemove::SuggestsImportant "false";
APT::Clean-Installed "false";
APT::Update "";
APT::Update::Post-Invoke-Success "";
APT::Update::Post-Invoke-Success:: "test -x /usr/bin/apt-show-versions || exit 
0 ; apt-show-versions -i";
APT::Architectures "";
APT::Architectures:: "amd64";
APT::Architectures:: "i386";
APT::Compressor "";
APT::Compressor::. "";
APT::Compressor::.::Name ".";
APT::Compressor::.::Extension "";
APT::Compressor::.::Binary "";
APT::Compressor::.::Cost "0";
APT::Compressor::zstd "";
APT::Compressor::zstd::Name "zstd";
APT::Compressor::zstd::Extension ".zst";
APT::Compressor::zstd::Binary "zstd";
APT::Compressor::zstd::Cost "60";
APT::Compressor::zstd::CompressArg "";
APT::Compressor::zstd::CompressArg:: "-19";
APT::Compressor::zstd::UncompressArg "";
APT::Compressor::zstd::UncompressArg:: "-d";
APT::Compressor::lz4 "";
APT::Compressor::lz4::Name "lz4";
APT::Compressor::lz4::Extension ".lz4";
APT::Compressor::lz4::Binary "false";
APT::Compressor::lz4::Cost "50";
APT::Compressor::gzip "";
APT::Compressor::gzip::Name "gzip";
APT::Compressor::gzip::Extension ".gz";
APT::Compressor::gzip::Binary "gzip";
APT::Compressor::gzip::Cost "100";
APT::Compressor::gzip::CompressArg "";
APT::Compressor::gzip::CompressArg:: "-6n";
APT::Compressor::gzip::UncompressArg "";
APT::Compressor::gzip::UncompressArg:: "-d";
APT::Compressor::xz "";
APT::Compressor::xz::Name "xz";
APT::Compressor::xz::Extension ".xz";
APT::Compressor::xz::Binary "xz";
APT::Compressor::xz::Cost "200";
APT::Compressor::xz::CompressArg "";
APT::Compressor::xz::CompressArg:: "-6";
APT::Compressor::xz::UncompressArg "";
APT::Compressor::xz::UncompressArg:: "-d";
APT::Compressor::bzip2 "";
APT::Compressor::bzip2::Name "bzip2";
APT::Compressor::bzip2::Extension ".bz2";
APT::Compressor::bzip2::Binary "bzip2";
APT::Compressor::bzip2::Cost "300";
APT::Compressor::bzip2::CompressArg "";
APT::Compressor::bzip2::CompressArg:: "-6";
APT::Compressor::bzip2::UncompressArg "";
APT::Compressor::bzip2::UncompressArg:: "-d";
APT::Compressor::lzma "";
APT::Compressor::lzma::Name "lzma";
APT::Compressor::lzma::Extension ".lzma";
APT::Compressor::lzma::Binary "xz";
APT::Compressor::lzma::Cost "400";
APT::Compressor::lzma::CompressArg "";
APT::Compressor::lzma::CompressArg:: "--format=lzma";
APT::Compressor::lzma::CompressArg:: "-6";
APT::Compressor::lzma::UncompressArg "";
APT::Compressor::lzma::UncompressArg:: "--format=lzma";
APT::Compressor::lzma::UncompressArg:: "-d";
Dir "/";
Dir::State "var/lib/apt";
Dir::State::lists "lists/";
Dir::State::cdroms "cdroms.list";
Dir::State::extended_states "extended_states";
Dir::State::status "/var/lib/dpkg/status";
Dir::Cache "var/cache/apt";
Dir::Cache::archives "archives/";
Dir::Cache::srcpkgcache "srcpkgcache.bin";
Dir::Cache::pkgcache "pkgcache.bin";
Dir::Etc "etc/apt";
Dir::Etc::sourcelist "sources.list";
Dir::Etc::sourceparts "sources.list.d";
Dir::Etc::main "apt.conf";
Dir::Etc::netrc "auth.conf";
Dir::Etc::netrcparts "auth.conf.d";
Dir::Etc::parts 

Bug#1066862: openstack-cluster-installer: Enhancement: Manage dnsmasq_dns_servers parameter

[Jim Scadden]

Package: openstack-cluster-installer
Tags: patch
Severity: wishlist

I've raised a Merge Request [1] to manage the dnsmasq_dns_servers option
of /etc/neutron/dhcp_agent.ini in the OCI cluster settings

This enables the user to configure Case 2a from
https://docs.openstack.org/neutron/latest/admin/config-dns-res.html

The MR includes an update to README.md with instructions on the use of
the new cluster option (--neutron-dnsmasq-dns-servers)

--

Regards
Jim Scadden (FloydianJim)

[1] 
https://salsa.debian.org/openstack-team/debian/openstack-cluster-installer/-/merge_requests/48

Bug#1064344: RFS: vzlogger/0.8.3 ITP #864255

[Tobias Frost]

Hi Joachim

&& dpkg --compare-versions $2 le-nl 0.8.3 \
&& dpkg --compare-versions $2 ge 0.8.2; then

- $2 might be empty, you need to quote it: use "$2" otherwise dpkg will
  fail:

$ dpkg --compare-versions $empty le-nl 0.8.3
dpkg: error: --compare-versions takes three arguments:   


Type dpkg --help for help about installing and deinstalling packages [*];
Use 'apt' or 'aptitude' for user-friendly package management;
Type dpkg -Dhelp for a list of dpkg debug flag values;
Type dpkg --force-help for a list of forcing options;
Type dpkg-deb --help for help about manipulating *.deb files;

Options marked [*] produce a lot of output - pipe it through 'less' or 'more' !
 
-- 
tobi

Bug#1066866: railway-gtk: FTBFS on i386 "type annotations needed"

[Peter Green]

Package: railway-gtk
Version: 2.4.0-1
Severity: serious

railway-gtk FTBFS on i386 (and will probablly FTBFS on other
32-bit architectures but builds on those architectures are
currently blocked by the time64 transition).


error[E0283]: type annotations needed for `std::option::Option`
   --> src/backend/journeys_result.rs:207:17
|
207 | let index = list
| ^
...
215 | if position <= index && index < position + n_items {
| -- type must be known at this point
|
= note: multiple `impl`s satisfying `u32: PartialOrd<_>` found in the 
following crates: `core`, `glib`:
- impl PartialOrd for u32;
- impl PartialOrd for u32;
help: consider giving `index` an explicit type, where the placeholders `_` are 
specified
|
207 | let index: std::option::Option = list
|  


Looking at the code, I'm pretty confident that the intended type was
Option. The attached debdiff adds the annotation. I have tested
that railway-gtk builds succesfully with this patch on both i386
and amd64.diff -Nru railway-gtk-2.4.0/debian/changelog railway-gtk-2.4.0/debian/changelog
--- railway-gtk-2.4.0/debian/changelog  2024-03-04 13:13:51.0 +
+++ railway-gtk-2.4.0/debian/changelog  2024-03-14 16:10:58.0 +
@@ -1,3 +1,10 @@
+railway-gtk (2.4.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with "type annotation needed" error on i386.
+
+ -- Peter Michael Green   Thu, 14 Mar 2024 16:10:58 +
+
 railway-gtk (2.4.0-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru railway-gtk-2.4.0/debian/patches/add-type-annotation.patch 
railway-gtk-2.4.0/debian/patches/add-type-annotation.patch
--- railway-gtk-2.4.0/debian/patches/add-type-annotation.patch  1970-01-01 
00:00:00.0 +
+++ railway-gtk-2.4.0/debian/patches/add-type-annotation.patch  2024-03-14 
16:10:58.0 +
@@ -0,0 +1,13 @@
+Index: railway-gtk-2.4.0/src/backend/journeys_result.rs
+===
+--- railway-gtk-2.4.0.orig/src/backend/journeys_result.rs
 railway-gtk-2.4.0/src/backend/journeys_result.rs
+@@ -204,7 +204,7 @@ mod imp {
+ let list = self.journeys.borrow();
+ let selection = self.selected.borrow();
+ 
+-let index = list
++let index: Option = list
+ .iter()
+ .position(|j| {
+ j.refresh_token() == selection.as_ref().and_then(|j| 
j.refresh_token())
diff -Nru railway-gtk-2.4.0/debian/patches/series 
railway-gtk-2.4.0/debian/patches/series
--- railway-gtk-2.4.0/debian/patches/series 2024-03-04 13:13:51.0 
+
+++ railway-gtk-2.4.0/debian/patches/series 2024-03-14 16:10:14.0 
+
@@ -1,3 +1,4 @@
 relax-deps.diff
 disable-cargo-home-meson-build.diff
 build-set-project-name-to-railway-gtk.patch
+add-type-annotation.patch

Bug#1066860: libprelude ftbfs on time_t64 archs

[Matthias Klose]

Package: src:libprelude
Version: 5.2.0-5.3
Severity: serious
Tags: sid trixie ftbfs patch

libprelude ftbfs on time_t64 archs with symbols file mismatches.  I 
don't know why some changes are only limited to arc and x32, but I made 
these all optional.


patch at
http://launchpadlibrarian.net/719321091/libprelude_5.2.0-5.3build2_5.2.0-5.3ubuntu1.diff.gz

Bug#1066203: recode: FTBFS: error.c:197:43: error: implicit declaration of function ‘strcmp’ [-Werror=implicit-function-declaration]

[Andrey Rakhmatullin]

On Wed, Mar 13, 2024 at 12:44:18PM +0100, Lucas Nussbaum wrote:
> > error.c:197:43: error: implicit declaration of function ‘strcmp’ 
> > [-Werror=implicit-function-declaration]
> >   197 |   (file_name == old_file_name || !strcmp (old_file_name, 
> > file_name)))
> >   |   ^~
 is included in that file under #if STDC_HEADERS || _LIBC. No
idea what is _LIBC as it's only mentioned in various .c files, but
STDC_HEADERS is set/unset by configure via AC_HEADER_STDC, and in this
case it's unset ("checking for ANSI C header files... no"):

configure:6168: gcc -o conftest -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/build/recode-ConsAw/recode-3.6=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
-Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro conftest.c  1>&5
configure: In function 'main':
configure:6163:67: error: implicit declaration of function 'exit' 
[-Werror=implicit-function-declaration]

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#1066358: graphviz: diff for NMU version 2.42.2-8.1

[Andrey Rakhmatullin]

Control: tags 1066358 + patch
Control: tags 1066358 + pending

Dear maintainer,

I've prepared an NMU for graphviz (versioned as 2.42.2-8.1) and
uploaded it to DELAYED/4. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
WBR, wRAR
diff -Nru graphviz-2.42.2/debian/changelog graphviz-2.42.2/debian/changelog
--- graphviz-2.42.2/debian/changelog	2024-01-27 01:26:42.0 +0500
+++ graphviz-2.42.2/debian/changelog	2024-03-14 21:33:50.0 +0500
@@ -1,3 +1,10 @@
+graphviz (2.42.2-8.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with -Werror=implicit-function-declaration (Closes: #1066358).
+
+ -- Andrey Rakhmatullin   Thu, 14 Mar 2024 21:33:50 +0500
+
 graphviz (2.42.2-8) unstable; urgency=medium
 
   * Fix CVE-2023-46045: buffer overflow via a crafted config6a file.
diff -Nru graphviz-2.42.2/debian/patches/fix-implicit-function-declaration.patch graphviz-2.42.2/debian/patches/fix-implicit-function-declaration.patch
--- graphviz-2.42.2/debian/patches/fix-implicit-function-declaration.patch	1970-01-01 05:00:00.0 +0500
+++ graphviz-2.42.2/debian/patches/fix-implicit-function-declaration.patch	2024-03-14 21:26:14.0 +0500
@@ -0,0 +1,17 @@
+Description: Add a missing prototype for makeTetrix().
+Author: Andrey Rakhmatullin 
+Bug-Debian: https://bugs.debian.org/1066358
+Origin: backport, https://gitlab.com/graphviz/graphviz/-/commit/be6f649995d00865e7c7d721f9b5bdb13fd715c0
+Forwarded: not-needed
+Last-Update: 2024-03-14
+
+--- graphviz-2.42.2.orig/cmd/tools/graph_generator.h
 graphviz-2.42.2/cmd/tools/graph_generator.h
+@@ -30,6 +30,7 @@ extern void makeRandom(int, int, edgefn)
+ extern void makeSquareGrid(int, int, int, int, edgefn);
+ extern void makeBinaryTree(int, edgefn);
+ extern void makeSierpinski(int, edgefn);
++extern void makeTetrix(int, edgefn);
+ extern void makeHypercube(int, edgefn);
+ extern void makeTree(int, int, edgefn);
+ extern void makeTriMesh(int, edgefn);
diff -Nru graphviz-2.42.2/debian/patches/series graphviz-2.42.2/debian/patches/series
--- graphviz-2.42.2/debian/patches/series	2024-01-27 01:26:42.0 +0500
+++ graphviz-2.42.2/debian/patches/series	2024-03-14 21:24:56.0 +0500
@@ -10,3 +10,4 @@
 update_documentation_link.patch
 fix_out-of-bounds_write_on_invalid_label.patch
 CVE-2023-46045.patch
+fix-implicit-function-declaration.patch


signature.asc
Description: PGP signature

Bug#1066498: dh-make-perl: autopkgtest regression due to time_t transition

[Niko Tyni]

On Thu, Mar 14, 2024 at 05:14:17PM +0100, gregor herrmann wrote:

> After some thinking, I think I makes to (temporarily) allow both
> libperl5.XXt64 and libperl5.XX, otherwise we'll have a mess during
> the 5.40 transition.
> (After that we can get rid of the option with the suffix again.)

Sure we need to allow for libperl5.XX to stay future-proof. I was just
thinking of hardcoding libperl5.38t64 as the (temporary) other option
rather than using a generic libperl5.XXt64 name.

But no worries :)
-- 
Niko

Bug#1065193: RFS: libhx/4.23-1 [RC] -- C library providing queue, tree, I/O and utility functions

[Tobias Frost]

Control: tags -1 moreinfo

Hi Jörg,

d/copyright:
you are changing history:

diff -Naur archive/libhx-4.19/debian/changelog new/libhx-4.23/debian/changelog
(...)
   * debian/rules:
 - Remove build of libhx-dev.symbols.

- -- Jörg Frings-Fürst   Sun, 17 Dec 2023 14:44:39 +0100
+ -- Jörg Frings-Fürst   Tue, 21 Nov 2023 10:41:07 +0100

 libhx (4.14-1) unstable; urgency=medium

- you git repository seems to missing commits. a debcheckout libhx
  gives me 4.17-1 in d/changelog.

- please don't drop the Build-Depends: dpkg-dev (>= 1.22.5), the
  time_t transition requires it, 

--
tobi

On Fri, Mar 01, 2024 at 06:50:24PM +0100, Jörg Frings-Fürst wrote:
> Package: sponsorship-requests
> Severity: important
> 
> Dear mentors,
> 
> I am looking for a sponsor for my package "libhx":
> 
>    Package name : libhx
>    Version  : 4.23-1
>    Upstream contact : Jan Engelhardt 
>    URL  : https://inai.de/projects/libhx/
>    License  : LGPL-2.1+, WTFPL-2+, GPL-2+
>    Vcs  : https://git.jff.email/cgit/libhx.git
>    Section  : libs
> 
> The source builds the following binary packages:
> 
>   libhx32t64 - C library providing queue, tree, I/O and utility functions
>   libhx-dev - Development files for libhx
>   libhx-doc - Documentation files for libhx
> 
> To access further information about this package, please visit the following
> URL:
> 
>  https://mentors.debian.net/package/libhx/
> 
> Alternatively, you can download the package with 'dget' using this command:
> 
>  dget -x 
> https://mentors.debian.net/debian/pool/main/libh/libhx/libhx_4.23-1.dsc
> 
> or from 
> 
>  git https://git.jff.email/cgit/libhx.git?h=release%2Fdebian%2F4.23-1
> 
> 
> 
> Changes since the last upload:
> 
>  libhx (4.23-1)  experimental; urgency=medium
>  .
>    * New upstream release (Closes: #1064734).
>    * Add debian/.gitignore
>    * Remove not longer needed debian/libhx-dev.lintian-overrides.
>    * Fix debian/libhx32t64.lintian-overrides.
>    * debian/copyright:
>  - Add 2024 to myself.
> 
> 
> 
> CU
> 
> Jörg
> 
> 
> -- 
> New:
> GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
> GPG key (long) : 09F89F3C8CA1D25D
> GPG Key: 8CA1D25D
> CAcert Key S/N : 0E:D4:56
> 
> 
> Jörg Frings-Fürst
> D-54470 Lieser
> 
> 
> git:  https://git.jff.email/cgit/
> 
> Skype:jff-skype@jff.email
> Jami: joergfringsfuerst
> Telegram: @joergfringsfuerst
> Matrix:   @joergff:matrix.snct-gmbh.de
> 
> My wish list: 
>  - Please send me a picture from the nature at your home.
> 
> 
> 
> 

Bug#1066264: cdrkit: diff for NMU version 9:1.1.11-3.5

[Andrey Rakhmatullin]

Control: tags 1066264 + patch
Control: tags 1066264 + pending

Dear maintainer,

I've prepared an NMU for cdrkit (versioned as 9:1.1.11-3.5) and
uploaded it to DELAYED/4. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
WBR, wRAR
diff -Nru cdrkit-1.1.11/debian/changelog cdrkit-1.1.11/debian/changelog
--- cdrkit-1.1.11/debian/changelog	2022-06-24 19:56:39.0 +0500
+++ cdrkit-1.1.11/debian/changelog	2024-03-14 21:53:13.0 +0500
@@ -1,3 +1,10 @@
+cdrkit (9:1.1.11-3.5) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with -Werror=implicit-function-declaration (Closes: #1066264).
+
+ -- Andrey Rakhmatullin   Thu, 14 Mar 2024 21:53:13 +0500
+
 cdrkit (9:1.1.11-3.4) unstable; urgency=low
 
   * Non-maintainer upload.
diff -Nru cdrkit-1.1.11/debian/patches/fix-implicit-function-declaration.patch cdrkit-1.1.11/debian/patches/fix-implicit-function-declaration.patch
--- cdrkit-1.1.11/debian/patches/fix-implicit-function-declaration.patch	1970-01-01 05:00:00.0 +0500
+++ cdrkit-1.1.11/debian/patches/fix-implicit-function-declaration.patch	2024-03-14 21:50:53.0 +0500
@@ -0,0 +1,29 @@
+Description: Add missing header includes.
+Author: Andrey Rakhmatullin 
+Bug-Debian: https://bugs.debian.org/1066264
+Last-Update: 2024-03-14
+
+Index: cdrkit-1.1.11/genisoimage/genisoimage.c
+===
+--- cdrkit-1.1.11.orig/genisoimage/genisoimage.c
 cdrkit-1.1.11/genisoimage/genisoimage.c
+@@ -54,6 +54,7 @@
+ #include 
+ #include "match.h"
+ #include "exclude.h"
++#include "checksum.h"
+ #include 	/* For UNICODE translation */
+ #include 
+ #ifdef UDF
+Index: cdrkit-1.1.11/genisoimage/jte.c
+===
+--- cdrkit-1.1.11.orig/genisoimage/jte.c
 cdrkit-1.1.11/genisoimage/jte.c
+@@ -27,6 +27,7 @@
+ #include "ifo_read.h"
+ #include "endianconv.h"
+ #include "checksum.h"
++#include "md5.h"
+ #endif
+ #ifdef APPLE_HYB
+ #include 
diff -Nru cdrkit-1.1.11/debian/patches/series cdrkit-1.1.11/debian/patches/series
--- cdrkit-1.1.11/debian/patches/series	2022-05-25 07:57:10.0 +0500
+++ cdrkit-1.1.11/debian/patches/series	2024-03-14 21:48:02.0 +0500
@@ -4,3 +4,4 @@
 add-efi-boot.patch
 gcc10.patch
 fix_format-security.patch
+fix-implicit-function-declaration.patch


signature.asc
Description: PGP signature

Bug#1065193: RFS: libhx/4.23-1 [RC] -- C library providing queue, tree, I/O and utility functions

[Tobias Frost]

On Fri, Mar 01, 2024 at 06:50:24PM +0100, Jörg Frings-Fürst wrote:
>  libhx (4.23-1)  experimental; urgency=medium

Note: the dsc file targets unstable, not experimental. The review was
using unstable as target.

-- 
tobi

Bug#1066865: knot-resolver ftbfs, wrong time_t type on 32bit archs with time_t64

[Matthias Klose]

Package: src:knot-resolver
Version: 5.7.1-1
Severity: serious
Tags: sid trixie ftbfs

seen trying to build knot-resolver on armhf with time_t64:

[...]
Program stderr:


Checking for size of "knot_pkt_t" with dependency libknot: 364
Program luajit found: YES (/usr/bin/luajit)
Running command: /usr/bin/luajit -e '
dofile('"'"'/<>/daemon/lua/kres-gen-32.lua'"'"')
local ffi = require('"'"'ffi'"'"')

  assert(ffi.sizeof(ffi.typeof('"'"'time_t'"'"')) == 8,
'"'"'Lua binding for C type '"'"' .. '"'"'time_t'"'"' .. '"'"' 
has incorrect size: '"'"'

.. ffi.sizeof(ffi.typeof('"'"'time_t'"'"'))
  )

  assert(ffi.sizeof(ffi.typeof('"'"'struct timeval'"'"')) == 16,
'"'"'Lua binding for C type '"'"' .. '"'"'struct timeval'"'"' 
.. '"'"' has incorrect size: '"'"'

.. ffi.sizeof(ffi.typeof('"'"'struct timeval'"'"'))
  )

  assert(ffi.sizeof(ffi.typeof('"'"'zs_scanner_t'"'"')) == 206056,
'"'"'Lua binding for C type '"'"' .. '"'"'zs_scanner_t'"'"' .. 
'"'"' has incorrect size: '"'"'

.. ffi.sizeof(ffi.typeof('"'"'zs_scanner_t'"'"'))
  )

  assert(ffi.sizeof(ffi.typeof('"'"'knot_pkt_t'"'"')) == 364,
'"'"'Lua binding for C type '"'"' .. '"'"'knot_pkt_t'"'"' .. 
'"'"' has incorrect size: '"'"'

.. ffi.sizeof(ffi.typeof('"'"'knot_pkt_t'"'"'))
  )
'
--- stdout ---

--- stderr ---
/usr/bin/luajit: (command line):5: Lua binding for C type time_t has 
incorrect size: 4

stack traceback:
[C]: in function 'assert'
(command line):5: in main chunk
[C]: at 0x00511b7d



../daemon/lua/meson.build:97:4: ERROR: Problem encountered: if you use 
released Knot* versions, please contact us: 
https://www.knot-resolver.cz/contact/
/usr/bin/luajit: (command line):5: Lua binding for C type time_t has 
incorrect size: 4

stack traceback:
[C]: in function 'assert'
(command line):5: in main chunk
[C]: at 0x00511b7d
dh_auto_configure: error: cd obj-arm-linux-gnueabihf && 
DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 meson setup .. 
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
--localstatedir=/var --libdir=lib/arm-linux-gnueabihf 
-Dpython.bytecompile=-1 -Dkeyfile_default=/usr/share/dns/root.key 
-Dinstall_root_keys=disabled -Dmanaged_ta=disabled 
-Droot_hints=/usr/share/dns/root.hints -Dinstall_kresd_conf=enabled 
-Dsystemd_files=enabled -Dclient=enabled -Dutils=enabled -Ddoc=enabled 
-Ddnstap=enabled -Dunit_tests=enabled -Dconfig_tests=enabled 
-Dextra_tests=disabled -Dmalloc=jemalloc returned exit code 1

make[1]: *** [debian/rules:26: override_dh_auto_configure] Error 25
make[1]: Leaving directory '/<>'

Bug#1066382: xserver-xorg-video-nouveau: FTBFS: ../../src/nv_driver.c:1451:23: error: implicit declaration of function ‘wfbScreenInit’; did you mean ‘fbScreenInit’? [-Werror=implicit-function-declarat

[Sven Joachim]

On 2024-03-13 18:07 +0100, Sven Joachim wrote:

> Control: forwarded -1 
> https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/569
>
> On 2024-03-13 12:47 +0100, Lucas Nussbaum wrote:
>
>> Source: xserver-xorg-video-nouveau
>> Version: 1:1.0.17-2
>> Severity: serious
>> Justification: FTBFS
>> Tags: trixie sid ftbfs
>> User: lu...@debian.org
>> Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
>>
>> Hi,
>>
>> During a rebuild of all packages in sid, your package failed to build
>> on amd64.
>>
>> This is most likely caused by a change in dpkg 1.22.6, that enabled
>> -Werror=implicit-function-declaration. For more information, see
>> https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
>>
>> Relevant part (hopefully):
>>> /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H
>>> -I. -I../../src -I..  -Wdate-time -D_FORTIFY_SOURCE=2
>>> -I/usr/include/xorg -fvisibility=hidden -I/usr/include/pixman-1
>>> -I/usr/include/X11/dri -I/usr/include/libdrm -I/usr/include/libdrm
>>> -I/usr/include/libdrm/nouveau -I/usr/include/libdrm -g -O2
>>> -Werror=implicit-function-declaration
>>> -ffile-prefix-map=/<>=. -fstack-protector-strong
>>> -fstack-clash-protection -Wformat -Werror=format-security
>>> -fcf-protection -Wall -minline-all-stringops -I/usr/include/xorg
>>> -fvisibility=hidden -I/usr/include/pixman-1 -I/usr/include/X11/dri
>>> -I/usr/include/libdrm -c -o nv04_xv_ovl.lo ../../src/nv04_xv_ovl.c
>>> ../../src/nv_driver.c: In function ‘NVScreenInit’:
>>> ../../src/nv_driver.c:1451:23: error: implicit declaration of
>>> function ‘wfbScreenInit’; did you mean ‘fbScreenInit’?
>>> [-Werror=implicit-function-declaration]
>>>  1451 | ret = wfbScreenInit(pScreen, FBStart, 
>>> pScrn->virtualX,
>>>   |   ^
>>>   |   fbScreenInit
>
> This has already been reported upstream, unfortunately without a
> followup so far.

Got a reply from Alan Coppersmith, and he mentioned a fix to xorg's fb.h
header file which is in the Xserver master branch, but has not yet been
applied to the server-21.1-branch.

> Adding -DFB_ACCESS_WRAPPER to CPPFLAGS lets the build
> succeed, but I have not tested the resulting binary package yet.

Tested it now, and it does not work at all, xinit fails to start:

,
| /usr/lib/xorg/Xorg: symbol lookup error: 
/usr/lib/xorg/modules/drivers/nouveau_drv.so: undefined symbol: wfbPictureInit
`

> See commit d7ba24fb6e4f ("wfb: Fix missing init function decls behind
> FB_ACCESS_WRAPPER") which noticed and fixed the missing function
> declaration, but got reverted in commit ca13913aaf7e.

For a good reason, the commit message mentions the same error which I
got.  So I think we should disable -Werror=implicit-function-declaration
in xserver-xorg-video-nouveau for now until there is a fix in the
xorg-server package.

Cheers,
   Sven

Bug#1066827: foot: mouse-click results in sequence 0;45;9M0;45;9m, displayed at the prompt

[Birger Schacht]

Hi,


can you clarify what "after a while" means? I can not reproduce the 
behavior and I'm using foot all the time...

Do you have a custom foot configuration?

cheers,
Birger

On 3/14/24 12:06 AM, Johann Hoermann wrote:

Dear Maintainer,

when i do a mouse-click in a just opened foot terminal, it highlights the 
text under the mouse-pointer which is the expected behaviour.

After a while, instead of highlighting, a new mouse-click results in a 
sequence 0;45;9M0;45;9m being displayed at the shell prompt.

Bug#1066849: Re: Bug#1066849: libelf1 Version mismatch (0.190-1+b1 vs 0.191-1)

[Rémi DUCCESCHI]

Hello,

Thanks for the info. So this may be linked to
?

Do you know where I can find information about the time_t64 transition?

Bug#1066498: dh-make-perl: autopkgtest regression due to time_t transition

[gregor herrmann]

On Wed, 13 Mar 2024 23:12:57 +0200, Niko Tyni wrote:

> > Reviews welcome; I'm not sure it's the most elegant and safe solution,
> > and also if this libperl5.38t64 naming has other effects.
> Thanks for fixing this.

Thanks for checking.
 
> Didn't dig deeply into what the test is actually doing, but I think it'd
> be fine to just hardcode libperl5.38t64 FWIW.

After some thinking, I think I makes to (temporarily) allow both
libperl5.XXt64 and libperl5.XX, otherwise we'll have a mess during
the 5.40 transition.
(After that we can get rid of the option with the suffix again.)
 
> But whatever works is good of course.

:)


Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#1065768: libauthen-krb5-perl: FTBFS on arm{el,hf}: Krb5.xs:1040:17: error: implicit declaration of function ‘krb5_free_address’; did you mean ‘krb5_free_addresses’? [-Werror=implicit-function-dec

[gregor herrmann]

On Sat, 09 Mar 2024 21:29:26 +0100, Sebastian Ramacher wrote:

> Source: libauthen-krb5-perl
> Version: 1.9-6
> 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=libauthen-krb5-perl=armhf=1.9-6%2Bb3=1709893977=0
> 
> Krb5.xs:1040:17: error: implicit declaration of function ‘krb5_free_address’; 
> did you mean ‘krb5_free_addresses’? [-Werror=implicit-function-declaration]
>  1040 | krb5_free_address(context,addr);
>   | ^
>   | krb5_free_addresses

Not sure there are many chances to fix this (short of disabling
-Werror=implicit-function-declaration). Cf. also in Fedora:
https://src.fedoraproject.org/rpms/perl-Authen-Krb5/commits/rawhide
https://bugzilla.redhat.com/show_bug.cgi?id=2172836

Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#1065374: RFS: sane-backends/1.3.0-1 -- API development library for scanners

[Tobias Frost]

Control: tags -1 moreinfo

Hi Jörg,

isfdtype(3) says the header you need to include is 
   #include 
   #include 

Any reason why you don't include the header but use a forward
declaration instead?

--
tobi

Bug#1066863: python3-pyqtgraph: SyntaxWarning: invalid escape sequence '\$'

[Taavi Väänänen]

Package: python3-pyqtgraph
Version: 0.13.4-2
Severity: normal

Hello,

The python3-pyqtgraph package printed this warning when it updated from
0.13.3-1 to 0.13.4-2:

Setting up python3-pyqtgraph (0.13.4-2) ...
/usr/lib/python3/dist-packages/pyqtgraph/examples/SpinBox.py:38:
  SyntaxWarning: invalid escape sequence '\$'
  regex='\$?(?P(-?\d+(\.\d+)?)|(-?\.\d+))$')),

-- 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/8 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 python3-pyqtgraph depends on:
ii  libpyside2-py3-5.15 [libpyside2-py3]  5.15.12-6
ii  pyqt5-dev-tools   5.15.10+dfsg-1
ii  pyqt6-dev-tools   6.6.1-2
ii  python3   3.11.6-1
ii  python3-numpy 1:1.24.2-2
ii  python3-pyqt5 5.15.10+dfsg-1
ii  python3-pyqt6 6.6.1-2
ii  python3-scipy 1.11.4-6
ii  qt6-base-dev-tools6.4.2+dfsg-21
ii  qtbase5-dev-tools 5.15.10+dfsg-7

Versions of packages python3-pyqtgraph recommends:
ii  python3-matplotlib  3.6.3-1+b2
ii  python3-opengl  3.1.7+dfsg-1
ii  python3-pyqt5.qtopengl  5.15.10+dfsg-1

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

-- no debconf information

Bug#1066249: libmediascan: FTBFS: api_test.c:80:3: error: implicit declaration of function ‘gettimeofday’ [-Werror=implicit-function-declaration]

[gregor herrmann]

On Wed, 13 Mar 2024 12:41:10 +0100, Lucas Nussbaum wrote:

> > api_test.c: In function ‘check_mimetypes’:
> > api_test.c:80:3: error: implicit declaration of function ‘gettimeofday’ 
> > [-Werror=implicit-function-declaration]
> >80 |   gettimeofday(, NULL);

> > api_test.c: In function ‘main’:
> > api_test.c:198:3: error: implicit declaration of function ‘run_unit_tests’ 
> > [-Werror=implicit-function-declaration]
> >   198 |   run_unit_tests();

> > test_background.c: In function ‘test_background_api’:
> > test_background.c:12:16: error: implicit declaration of function ‘mkdir’; 
> > did you mean ‘_mkdir’? [-Werror=implicit-function-declaration]
> >12 | #define _mkdir mkdir

> > test_background.c: In function ‘test_async_api’:
> > test_background.c:822:3: error: implicit declaration of function 
> > ‘gettimeofday’ [-Werror=implicit-function-declaration]
> >   822 |   gettimeofday(, NULL);

> > test.c: In function ‘TouchFile’:
> > test.c:512:3: error: implicit declaration of function ‘gettimeofday’ 
> > [-Werror=implicit-function-declaration]
> >   512 |   gettimeofday(, NULL);

> > test.c:513:3: error: implicit declaration of function ‘utimes’; did you 
> > mean ‘ctime’? [-Werror=implicit-function-declaration]
> >   513 |   utimes(filename  , );

I've pushed a patch to git which make the package compile without
errors.

Not going to upload as-is, as I hardly speak any C and don't really
know what I'm doing and this is more than adding a missing #include
or prototype and I don't understand the code.


Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#1066727: satpy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

[Sebastiaan Couwenberg]

reassign 1066727 src:python-pytest-lazy-fixture
found 1066727 python-pytest-lazy-fixture/0.6.3-2
affects 1066727 src:satpy
thanks

On 3/13/24 4:00 PM, Lucas Nussbaum wrote:

/usr/lib/python3/dist-packages/pytest_lazyfixture.py:105: in normalize_call
 valtype_keys = set(getattr(callspec, valtype).keys()) - used_keys
E   AttributeError: 'CallSpec2' object has no attribute 'funcargs'

Reassigning accordingly.

Kind Regards,

Bas

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

Bug#1066850: don't hard-code the name of the shared library

[Christoph Biedl]

Control: tags 1066850 moreinfo

Matthias Klose wrote...

> Package: src:python-magic
> Version: 2:0.4.27-2
> Severity: serious
> Tags: sid trixie
>
> the package build-depends on libmagic1, and depends on it. The name was
> recently changed to libmagic1t64.

This is not a real problem as libmagic1t64 provides libmagic1, so the
dependency can still be resolved.

> Please don't hard-code it, but try to b-d
> on libmagic-dev, (...)

About the build dependency src:python-magic -> libmagic1:

So that is ugly, and using libmagic-dev is a simple fix for it. Will do
in the next uplad.

> and derive the name of the shared library package from the
> libmagic-dev package.

Are you still talking about the build dependency here? Then it's no
issue as the -dev dependency will take care of that.


Question: What is the justifcation for the bug severity? To me, it
is rather "minor".

Christoph


signature.asc
Description: PGP signature

Bug#1066850: don't hard-code the name of the shared library

[Matthias Klose]

On 14.03.24 18:52, Christoph Biedl wrote:

Control: tags 1066850 moreinfo

Matthias Klose wrote...


Package: src:python-magic
Version: 2:0.4.27-2
Severity: serious
Tags: sid trixie

the package build-depends on libmagic1, and depends on it. The name was
recently changed to libmagic1t64.


This is not a real problem as libmagic1t64 provides libmagic1, so the
dependency can still be resolved.


this is not true on the 32bit time_t64 archs. Debian doesn't build 
binary-indep packages on these architectures, but this b-d prevents 
doing so (and it does so, because it's impossible to install 
python-magic's b-d's on the porter boxes).



Please don't hard-code it, but try to b-d
on libmagic-dev, (...)


About the build dependency src:python-magic -> libmagic1:

So that is ugly, and using libmagic-dev is a simple fix for it. Will do
in the next uplad.


and derive the name of the shared library package from the
libmagic-dev package.


Are you still talking about the build dependency here? Then it's no
issue as the -dev dependency will take care of that.


No, the idea was to b-d on libmagic-dev, and then get the dependency for 
python3-magic from it.



Question: What is the justifcation for the bug severity? To me, it
is rather "minor".


you can't install the package on the 32bit time_t64 architectures, some 
of them still being release architectures. On these archs, libmagic1t64 
doesn't provide libmagic1.


Matthias

Bug#1066874: miniupnpd-nftables: nft_init.sh clobbers all other FORWARD table rules by changing policy to deny

[Guyang Mao]

Package: miniupnpd-nftables
Version: 2.3.4-1
Severity: important

Dear Maintainer,

I've changed my system to use nftables for firewall rules and found out that 
miniupnpd-nftables
clobbered everything else on FORWARD.

(specifically, docker containers)

Looking at all the rules and nft_init.sh, it seems like creating the forward 
table for miniupnpd
and setting the default policy to deny breaks everything.  Changing the default 
policy to accept
makes everything work again.



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

Kernel: Linux 6.1.0-9-amd64 (SMP w/4 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 miniupnpd-nftables depends on:
ii  libc6   2.37-15.1
ii  libmnl0 1.0.5-2
ii  libnftnl11  1.2.6-2
ii  miniupnpd   2.3.4-1

miniupnpd-nftables recommends no packages.

miniupnpd-nftables suggests no packages.

-- Configuration Files:
/etc/miniupnpd/nft_init.sh changed:
. "$(dirname "$0")/miniupnpd_functions.sh"
$NFT --check list table inet $TABLE > /dev/null 2>&1
if [ $? -eq "0" ]
then
echo "Table $TABLE already exists"
exit 0
fi
echo "Creating nftables structure"
cat > /tmp/miniupnpd.nft <> /tmp/miniupnpd.nft <> /tmp/miniupnpd.nft <

Bug#1066875: devscripts: debsign tries to parse gpg version from human-readable output, should use machine-readable output

[Daniel Kahn Gillmor]

Package: devscripts
Version: 2.23.7
Tags: patch

(this is also
https://salsa.debian.org/debian/devscripts/-/merge_requests/394)

debsign currently tries to determine the version of gpg by parsing the
human-readable output of `gpg --version`.

For use in scripts and other code, the GnuPG project prefers the use
of machine-readable output, and has offered `--with-colons
--list-config` for many versions (back at least to 1.3.5 according to
/usr/share/doc/gnupg/DETAILS.gz).  That form of invocation produces a
lot of detail, including the actual version number:

cfg:version:2.2.40

This mode of output is what is used by libgpgme to determine the
version of gpg, so it is likely to remain stable and parseable.

The attached patch converts debsign to use the machine-parseable format,
rather than the human-readable format.

This issue came up when experimenting with sequoia-chameleon-gnupg,
which produces a human-readable string that doesn't match what debsign
was checking for.
(https://gitlab.com/sequoia-pgp/sequoia-chameleon-gnupg/-/issues/61).
they're fixing that now in the chameleon upstream, but it seems like
debsign should be using the more robust approach anyway.

Thanks for maintaining devscripts!

--dkg

From 6bed35a535962534883a5aa233cbbcbfc7b15624 Mon Sep 17 00:00:00 2001
From: Daniel Kahn Gillmor 
Date: Thu, 14 Mar 2024 14:10:59 -0400
Subject: [PATCH] debsign: check gpg version with machine-parseable format

debsign currently tries to determine the version of gpg by parsin the
human-readable output of `gpg --version`.

For use in scripts and other code, the GnuPG project prefers the use
of machine-readable output, and has offered `--with-colons
--list-config` for many versions (back at least to 1.3.5 according to
/usr/share/doc/gnupg/DETAILS.gz).  That form of invocation produces a
lot of detail, including the actual version number:

cfg:version:2.2.40

This mode of output is what is used by libgpgme to determine the
version of gpg, so it is likely to remain stable and parseable.

This change converts debsign to use the machine-parseable format,
rather than the human-readable format.
---
 scripts/debsign.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/debsign.sh b/scripts/debsign.sh
index 15b0dfc2..cc4d31ab 100755
--- a/scripts/debsign.sh
+++ b/scripts/debsign.sh
@@ -170,7 +170,7 @@ signfile() {
 ASCII_SIGNED_FILE="${UNSIGNED_FILE}.asc"
 (cat "$file" ; echo "") > "$UNSIGNED_FILE"
 
-gpgversion=$($signcommand --version | head -n 1 | cut -d' ' -f3)
+gpgversion=$($signcommand --with-colons --list-config | awk -F: '/^cfg:version:/ { print $3; exit }')
 gpgmajorversion=$(echo $gpgversion | cut -d. -f1)
 gpgminorversion=$(echo $gpgversion | cut -d. -f2)
 
-- 
2.43.0



signature.asc
Description: PGP signature

Bug#1066249: libmediascan: FTBFS: api_test.c:80:3: error: implicit declaration of function ‘gettimeofday’ [-Werror=implicit-function-declaration]

[Niko Tyni]

[Paul: copying you for eyeballs as this seems to have been your pet
 package at some point :)]

On Thu, Mar 14, 2024 at 06:21:35PM +0100, gregor herrmann wrote:
> On Wed, 13 Mar 2024 12:41:10 +0100, Lucas Nussbaum wrote:

> > > test_background.c: In function ‘test_background_api’:
> > > test_background.c:12:16: error: implicit declaration of function ‘mkdir’; 
> > > did you mean ‘_mkdir’? [-Werror=implicit-function-declaration]
> > >12 | #define _mkdir mkdir

> I've pushed a patch to git which make the package compile without
> errors.
> 
> Not going to upload as-is, as I hardly speak any C and don't really
> know what I'm doing and this is more than adding a missing #include
> or prototype and I don't understand the code.

I assume you mean the '#define _mkdir mkdir' part? The rest
seems straightforward.

AFAICS the code used to call mkdir(2) without the mode argument.
A simple test [1] indicates that will just put random garbage there,
so the resulting directory will have a different mode every time. Surely
that was always buggy.

I'm not convinced that affected functions in test/test_defects.c
or test/test_background.c ever get executed for us though? They have
unpatched horrific things like

  const char *test_path = "C:\\Siojej3";

  const char start_dir[] = "C:\\logitest";

In any case, your change

  +int _mkdir(const char *pathname)
  +{
  +mkdir(*pathname, 0775);
  +}

is not quite correct: I think it should read something like

  int _mkdir(const char *pathname)
  {
  return mkdir(pathname, 0775)
  }

to work properly.

But I think it would be easier to stick with the preprocessor and do

-#define _mkdir mkdir
+#include 
+#define _mkdir(x) mkdir((x), 0755)

instead.

Hope this helps :)

[1] echo 'int main(void) { mkdir("ttt"); }' | gcc -xc - && strace -e mkdir 
./a.out
-- 
Niko

Bug#1066264: cdrkit: diff for NMU version 9:1.1.11-3.5

[Steve McIntyre]

Thanks! If you think this is a good bugfix, please go ahead and upload
straight to unstable.

On Thu, Mar 14, 2024 at 09:55:13PM +0500, Andrey Rakhmatullin wrote:
>Control: tags 1066264 + patch
>Control: tags 1066264 + pending
>
>Dear maintainer,
>
>I've prepared an NMU for cdrkit (versioned as 9:1.1.11-3.5) and
>uploaded it to DELAYED/4. Please feel free to tell me if I
>should delay it longer.
>
>Regards.
>
>
>-- 
>WBR, wRAR

>diff -Nru cdrkit-1.1.11/debian/changelog cdrkit-1.1.11/debian/changelog
>--- cdrkit-1.1.11/debian/changelog 2022-06-24 19:56:39.0 +0500
>+++ cdrkit-1.1.11/debian/changelog 2024-03-14 21:53:13.0 +0500
>@@ -1,3 +1,10 @@
>+cdrkit (9:1.1.11-3.5) unstable; urgency=medium
>+
>+  * Non-maintainer upload.
>+  * Fix FTBFS with -Werror=implicit-function-declaration (Closes: #1066264).
>+
>+ -- Andrey Rakhmatullin   Thu, 14 Mar 2024 21:53:13 +0500
>+
> cdrkit (9:1.1.11-3.4) unstable; urgency=low
> 
>   * Non-maintainer upload.
>diff -Nru cdrkit-1.1.11/debian/patches/fix-implicit-function-declaration.patch 
>cdrkit-1.1.11/debian/patches/fix-implicit-function-declaration.patch
>--- cdrkit-1.1.11/debian/patches/fix-implicit-function-declaration.patch   
>1970-01-01 05:00:00.0 +0500
>+++ cdrkit-1.1.11/debian/patches/fix-implicit-function-declaration.patch   
>2024-03-14 21:50:53.0 +0500
>@@ -0,0 +1,29 @@
>+Description: Add missing header includes.
>+Author: Andrey Rakhmatullin 
>+Bug-Debian: https://bugs.debian.org/1066264
>+Last-Update: 2024-03-14
>+
>+Index: cdrkit-1.1.11/genisoimage/genisoimage.c
>+===
>+--- cdrkit-1.1.11.orig/genisoimage/genisoimage.c
> cdrkit-1.1.11/genisoimage/genisoimage.c
>+@@ -54,6 +54,7 @@
>+ #include 
>+ #include "match.h"
>+ #include "exclude.h"
>++#include "checksum.h"
>+ #include /* For UNICODE translation */
>+ #include 
>+ #ifdef UDF
>+Index: cdrkit-1.1.11/genisoimage/jte.c
>+===
>+--- cdrkit-1.1.11.orig/genisoimage/jte.c
> cdrkit-1.1.11/genisoimage/jte.c
>+@@ -27,6 +27,7 @@
>+ #include "ifo_read.h"
>+ #include "endianconv.h"
>+ #include "checksum.h"
>++#include "md5.h"
>+ #endif
>+ #ifdef APPLE_HYB
>+ #include 
>diff -Nru cdrkit-1.1.11/debian/patches/series 
>cdrkit-1.1.11/debian/patches/series
>--- cdrkit-1.1.11/debian/patches/series2022-05-25 07:57:10.0 
>+0500
>+++ cdrkit-1.1.11/debian/patches/series2024-03-14 21:48:02.0 
>+0500
>@@ -4,3 +4,4 @@
> add-efi-boot.patch
> gcc10.patch
> fix_format-security.patch
>+fix-implicit-function-declaration.patch



-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Can't keep my eyes from the circling sky,
Tongue-tied & twisted, Just an earth-bound misfit, I...

Bug#1061493: consolekit: install PAM module and udev files into /usr

[Mark Hindley]

Control: notfound -1 1.2.6-3

On Wed, Mar 13, 2024 at 10:40:40PM +0100, Andreas Beckmann wrote:
> Followup-For: Bug #1061493
> Control: found -1 1.2.6-3.1~exp1
> Control: severity -1 serious
> Control: tag -1 ftbfs
> 
> This change causes consolekit2 to to FTBFS in experimental:

Indeed. As it was an NMU, I think the etiquette is for the NMUer to fix.

In sid consolekit2 still builds cleanly. Therefore, marking notfound there.

Michael, perhaps you would fix your NMU, or provide a better patch?

Thanks

Mark

Bug#1066879: rpyc: CVE-2024-27758

[Salvatore Bonaccorso]

Source: rpyc
Version: 5.3.1-1
Severity: important
Tags: security upstream
Forwarded: https://github.com/tomerfiliba-org/rpyc/issues/551
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for rpyc.

CVE-2024-27758[0]:
| In RPyC before 6.0.0, when a server exposes a method that calls the
| attribute named __array__ for a client-provided netref (e.g.,
| np.array(client_netref)), a remote attacker can craft a class that
| results in remote code execution.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-27758
https://www.cve.org/CVERecord?id=CVE-2024-27758
[1] https://github.com/tomerfiliba-org/rpyc/issues/551
[2] 
https://github.com/tomerfiliba-org/rpyc/security/advisories/GHSA-h5cg-53g7-gqjw

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1036826: Please start handling \c

[Helge Kreutzmann]

Hello Martin,
Am Sun, Mar 10, 2024 at 10:14:20PM +0100 schrieb Martin Quinson:
> Instead, I'd appreciate if you could do a merge request with a test file, 
> along
> with the expected output. It'd save me the time to dig into the discussion of
> this bug. 
> 
> I'm not saying that I won't fix it w/o this test case. I'm just saying that
> providing a test case is a better approach to speedup the fix than severity
> abuse.

I hope explaining the test file in this bug is fine as well, because
I'm not sure what to do exactly merge and how.

The test case is groff(1) as it is in Debian unstable:

$ LC_ALL=C po4a-updatepo -f man --no-deprecation --option groff_code=verbatim 
--option generated --option 
untranslated="}1,Ds,zY,zZ,Ee,ES,dT,FN,NE,NS,EX,EE,Id,rstReportMargin,INDENT,UNINDENT,UN,a.RE,\|"
 --option unknown_macros=untranslated --master groff.1 -M utf-8 -p test.pot
groff.1:2279: (po4a::man)
  Escape sequence \c encountered. This is not completely
  handled yet.

And there is no output.

If I do a crude preprocessing, it kind of works:

$ cat groff.1 | perl -p -e 's/\\c\n//' > groff.test.1
$ LC_ALL=C po4a-updatepo -f man --no-deprecation --option groff_code=verbatim 
--option generated --option 
untranslated="}1,Ds,zY,zZ,Ee,ES,dT,FN,NE,NS,EX,EE,Id,rstReportMargin,INDENT,UNINDENT,UN,a.RE,\|"
 --option unknown_macros=untranslated --master groff.test.1 -M utf-8 -p test.pot
$ wc -l test.pot
3157 test.pot

I hope this helps you working on this, together with the discussion in
this bug.

Thanks for your support!

Greetings

  Helge
-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: PGP signature

Bug#1066249: libmediascan: FTBFS: api_test.c:80:3: error: implicit declaration of function ‘gettimeofday’ [-Werror=implicit-function-declaration]

[Paul Gevers]

Hi Niko, gregor,

On 14-03-2024 8:16 p.m., Niko Tyni wrote:

[Paul: copying you for eyeballs as this seems to have been your pet
  package at some point :)]


I'm receiving the bugs of this package, but thanks. It is (or I fear 
was) a dependency of a package I still have the ambition to package one day.



On Thu, Mar 14, 2024 at 06:21:35PM +0100, gregor herrmann wrote:

Not going to upload as-is, as I hardly speak any C


Neither do I.


Hope this helps :)


I'll have a look next time I have both time and energy (hopefully within 
a week).


Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1066869: RFS: hyprpaper/0.6.0-1 [ITP] -- Wallpaper utility for Hyprland

[Alan M Varghese]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: a...@digistorm.in

Dear mentors,

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

 * Package name : hyprpaper
   Version  : 0.6.0-1
   Upstream contact : vaxerski 
 * URL  : https://github.com/hyprwm/hyprpaper
 * License  : BSD-3-Clause
 * Vcs  : https://salsa.debian.org/NyxTrail/hyprpaper
   Section  : x11

The source builds the following binary packages:

  hyprpaper - Wallpaper utility for Hyprland

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/h/hyprpaper/hyprpaper_0.6.0-1.dsc

Changes for the initial release:

 hyprpaper (0.6.0-1) UNRELEASED; urgency=low
 .
   * Initial release. Closes: #1065699
   * Included a simple man page for hyprpaper (uses pandoc for building).

Regards,
-- 
  Alan M Varghese

Bug#1066870: RFS: libudis86/0~20221013-1 [ITP] -- Disassembler for x86 and x86-64 class ISA

[Alan M Varghese]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: a...@digistorm.in

Dear mentors,

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

 * Package name : libudis86
   Version  : 0~20221013-1
   Upstream contact : https://github.com/canihavesomecoffee/udis86/issues
 * URL  : https://github.com/canihavesomecoffee/udis86
 * License  : __AUTO_PERMISSIVE__, BSD-2-Clause, __UNKNOWN__
 * Vcs  : https://salsa.debian.org/NyxTrail/udis86
   Section  : misc

The source builds the following binary packages:

  libudis86-0 - Disassembler for x86 and x86-64 class ISA (library)
  libudis86-dev - Disassembler for x86 and x86-64 class ISA (development files)
  udcli - Disassembler for x86 and x86-64 class ISA (cli)
  libudis86-doc - Disassembler for x86 and x86-64 class ISA (documentation)

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/libu/libudis86/libudis86_0~20221013-1.dsc

Changes for the initial release:

 libudis86 (0~20221013-1) UNRELEASED; urgency=low
 .
   * Initial release. Closes: #1061940
   * This packaging is based on the fork
 https://github.com/canihavesomecoffee/udis86
 which includes "fixes and additions" from other forks.
   * The latest upstream release is v1.7.2 made on Sep 2, 2013. This build is
 however, based on the latest commit #5336633, made on Oct 13, 2022
   * Created a man page for udcli based on information from '--help' and
 additional information from the project's README.

Regards,
-- 
  Alan M Varghese

Bug#1066878: tomcat10: CVE-2024-24549

[Salvatore Bonaccorso]

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

Hi,

The following vulnerability was published for tomcat10.

CVE-2024-24549[0]:
| Denial of Service due to improper input validation vulnerability for
| HTTP/2 requests in Apache Tomcat. When processing an HTTP/2 request,
| if the request exceeded any of the configured limits for headers,
| the associated HTTP/2 stream was not reset until after all of the
| headers had been processed.This issue affects Apache Tomcat: from
| 11.0.0-M1 through 11.0.0-M16, from 10.1.0-M1 through 10.1.18, from
| 9.0.0-M1 through 9.0.85, from 8.5.0 through 8.5.98.  Users are
| recommended to upgrade to version 11.0.0-M17, 10.1.19, 9.0.86 or
| 8.5.99 which fix the issue.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-24549
https://www.cve.org/CVERecord?id=CVE-2024-24549
[1] https://lists.apache.org/thread/4c50rmomhbbsdgfjsgwlb51xdwfjdcvg

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1066877: tomcat10: CVE-2024-23672

[Salvatore Bonaccorso]

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

Hi,

The following vulnerability was published for tomcat10.

CVE-2024-23672[0]:
| Denial of Service via incomplete cleanup vulnerability in Apache
| Tomcat. It was possible for WebSocket clients to keep WebSocket
| connections open leading to increased resource consumption.This
| issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.0-M16, from
| 10.1.0-M1 through 10.1.18, from 9.0.0-M1 through 9.0.85, from 8.5.0
| through 8.5.98.  Users are recommended to upgrade to version
| 11.0.0-M17, 10.1.19, 9.0.86 or 8.5.99 which fix the issue.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-23672
https://www.cve.org/CVERecord?id=CVE-2024-23672
[1] https://lists.apache.org/thread/cmpswfx6tj4s7x0nxxosvfqs11lvdx2f

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1066882: bash: :: unrecognized history modifier

[Thorsten Glaser]

Package: bash
Version: 5.2.21-2
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de

I knew GNU bash had some issues with the exclamation mark,
but it’s even quoted here and still it weirdly fails:

bash$ echo "$BUILDUSERNAME:!:::"
bash: :: unrecognized history modifier

(This is from the pbuilder code to add the build user to
shadow, which I had to run by hand in a cowbuilder --login
chroot because I needed some manual work before the package
build and some packages refuse to be built by root.)


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

Kernel: Linux 6.6.15-m68k (UP)
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages bash depends on:
ii  base-files   13
ii  debianutils  5.17
ii  libc62.37-15.1
ii  libtinfo66.4+20240113-1

Versions of packages bash recommends:
pn  bash-completion  

Versions of packages bash suggests:
pn  bash-doc  

-- no debconf information

Bug#1066411: webkit2gtk: FTBFS: SharedContextMutex.cpp:219:41: error: inlining failed in call to ‘always_inline’ ‘egl::SharedContextMutex* egl::SharedContextMutex::doTryLock() [with Mute

[Alberto Garcia]

On Thu, Mar 14, 2024 at 11:00:26AM -0400, Jeremy Bícha wrote:
> > - Several undefined references at link time.
> It is caused by a changed in dpkg in Unstable
> 
> https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Indeed, we were incorrectly adding that flag to CXXFLAGS. I'm
confirming that this fixes everything and I'll upload the new package
asap.

Thanks!

Berto