Processed: tagging 1061764

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1061764 + fixed-upstream
Bug #1061764 [src:unattended-upgrades] unattended-upgrades ftbfs with Python 
3.12 as default
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1061764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061764
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1061519: shim: all CVEs fixed in upstream 15.8, please package

[Martin-Éric Racine]

Package: shim
Followup-For: Bug #1061519

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

shim 15.8 @vathpela vathpela released this 23 Jan 19:01

What's New

* Various CVE fixes:
  CVE-2023-40546 mok: fix LogError() invocation
  CVE-2023-40547 - avoid incorrectly trusting HTTP headers
  CVE-2023-40548 Fix integer overflow on SBAT section size on 32-bit system
  CVE-2023-40549 Authenticode: verify that the signature header is in bounds.
  CVE-2023-40550 pe: Fix an out-of-bound read in verify_buffer_sbat()
  CVE-2023-40551: pe-relocate: Fix bounds check for MZ binaries

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmXIZ50ACgkQrh+Cd8S0
17ZHWhAAge996R8VG8WR1eoqM13HYsAvDh/ITPOHEAInuAvxnxW2f77RQuAdh/lL
SK0++9aR6P2yQu1j+JjfRz7vBt4FQ1j08RkjYj3kpKq8nHdA6C0fg1OvqXKs5+lc
44noX5AfKGyYDu/EhNkmAdFmE98sRVRqLlu8Ilfg1r8/voYFLOeyplW1T5Pk9xqW
Uv+wvLFNyj5mxMakPRyuZWD0bjkw33GYHKHMG5uB1ElwKws8cS/Lh9ZjaDk0GBy+
m4v0mhsIghPCcrNSfNcxvBT7fzR0dsD/wO21rBLcJc3ExdCeA39U4+jO86TS2/39
cfJhaY5FO72F8kX5qDKsNJzvl8Bhq4gH7YtEqyZC9aYdQgSpUdAuU6RQu9zDvpZm
EKuJVmXlgc+4IhgYLzJDHH2rL9gI2IctMNPwlKPI89SVs5J+Ha11t8V6oC36Chgq
nWrJeWnAhgHiDoTwHwqsj2j3YAVE7lHrAcxqgN1Sl5knmO26qxf8ZgrjB3iR/lVR
ufjBnkN+MJaN5oSV4XUTOlOk8uDswtQ1b6ycJAHbA+XhyHcHLRFY4bLVuDviJFsd
c3HGcsjzEwepvkg5mmKBm9renLxyUkqhiXQ7JSr5nKWlkaz5DR/4t74sfPjm1qK2
jsugjusiKZG4D895vQ3QcDafL4hdpqgpfi8k4O/Xbq5ncFIjs4Y=
=bM7B
-END PGP SIGNATURE-

Processed: reassign 1063668 to nvidia-kernel-dkms, forcibly merging 1062932 1063668

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1063668 nvidia-kernel-dkms
Bug #1063668 [src:nvidia-graphics-drivers] linux-image-6.1.0-18-amd64: Nvidia 
525.147.05-4 issues
Bug reassigned from package 'src:nvidia-graphics-drivers' to 
'nvidia-kernel-dkms'.
Ignoring request to alter found versions of bug #1063668 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1063668 to the same values 
previously set
> forcemerge 1062932 1063668
Bug #1062932 {Done: Andreas Beckmann } [nvidia-kernel-dkms] 
nvidia-kernel-dkms: dkms module won't build against linux-image-6.1.0-18-amd64 
(6.1.76-1)
Bug #1063668 [nvidia-kernel-dkms] linux-image-6.1.0-18-amd64: Nvidia 
525.147.05-4 issues
Severity set to 'grave' from 'important'
1063668 was not blocked by any bugs.
1063668 was not blocking any bugs.
Added blocking bug(s) of 1063668: 1063675
Marked Bug as done
Marked as fixed in versions nvidia-graphics-drivers/535.54.03-1 and 
nvidia-graphics-drivers/525.147.05-6.
Marked as found in versions nvidia-graphics-drivers/525.147.05-4~deb12u1.
Added tag(s) patch.
Merged 1062932 1063668
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1062932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062932
1063668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063668
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed (with 1 error): reassign 1063668 to src:nvidia-graphics-drivers, forcibly merging 1062932 1063668

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1063668 src:nvidia-graphics-drivers
Bug #1063668 [linux-image-6.1.0-18-amd64] linux-image-6.1.0-18-amd64: Nvidia 
525.147.05-4 issues
Bug reassigned from package 'linux-image-6.1.0-18-amd64' to 
'src:nvidia-graphics-drivers'.
No longer marked as found in versions linux-image-6.1.0-18.
Ignoring request to alter fixed versions of bug #1063668 to the same values 
previously set
> forcemerge 1062932 1063668
Bug #1062932 {Done: Andreas Beckmann } [nvidia-kernel-dkms] 
nvidia-kernel-dkms: dkms module won't build against linux-image-6.1.0-18-amd64 
(6.1.76-1)
Unable to merge bugs because:
package of #1063668 is 'src:nvidia-graphics-drivers' not 'nvidia-kernel-dkms'
Failed to forcibly merge 1062932: Did not alter merged bugs.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1062932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062932
1063668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063668
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[Scott Kitterman]

It's been a couple of weeks and no action upstream.  I'll plan on uploading 
this unless you'd rather I hold off for some reason.

Scott K

On Wed, 24 Jan 2024 16:56:30 -0500 Scott Kitterman  
wrote:
> On Tue, 16 Jan 2024 20:41:58 +0100 Lucas Nussbaum  wrote:
> > Source: pycountry
> > Version: 23.12.11+ds1-1
> > Severity: serious
> > Justification: FTBFS
> > Tags: trixie sid ftbfs
> > User: lu...@debian.org
> > Usertags: ftbfs-20240115 ftbfs-trixie
> > 
> > Hi,
> > 
> > During a rebuild of all packages in sid, your package failed to build
> > on amd64.
> 
> This is due to changes in the recent iso-codes upload.  the patch below fixes 
> it so it should work with either version:
> 
> --- pycountry-23.12.11+ds1.orig/src/pycountry/__init__.py
> +++ pycountry-23.12.11+ds1/src/pycountry/__init__.py
> @@ -169,7 +169,8 @@ class SubdivisionHierarchy(pycountry.db.
>  kw["parent_code"] = None
>  super().__init__(**kw)
>  self.country_code = self.code.split("-")[0]
> -if self.parent_code is not None:
> +if (self.parent_code is not None and
> +self.country_code != self.parent_code.split("-")[0]):
>  self.parent_code = f"{self.country_code}-{self.parent_code}"
>  
>  @property
> 
> Please let me know if you don't want an NMU.  This will eventually cause 
> xml2rfc to be removed, so I'll NMU at some point unless you want to take 
care 
> of it first (thanks if you do).
> 
> Scott K
&references=<2567281.9CzbHMAgVU@zini-1880>

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

Processed: Updating bug ownership

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> owner 1018658 Nick Morrott 
Bug #1018658 [src:valinor] valinor: build-depends on python3-nose or uses it 
for autopkgtest
Owner recorded as Nick Morrott .
> owner 1018673 Nick Morrott 
Bug #1018673 [src:yotta] yotta: build-depends on python3-nose or uses it for 
autopkgtest
Owner recorded as Nick Morrott .
> owner 1027378 Nick Morrott 
Bug #1027378 [src:mu-editor] mu-editor: FTBFS (missing build-depends on mount)
Ignoring request to set the owner of bug #1027378 to the same value
> owner 1044498 Nick Morrott 
Bug #1044498 [src:gron] gron: Fails to build source after successful build
Owner recorded as Nick Morrott .
> owner 1045977 Nick Morrott 
Bug #1045977 [src:python-guizero] python-guizero: Fails to build source after 
successful build
Owner recorded as Nick Morrott .
> owner 1049655 Nick Morrott 
Bug #1049655 [src:python-guizero] python-guizero: Fails to build binary 
packages again after successful build
Owner recorded as Nick Morrott .
> owner 1052855 Nick Morrott 
Bug #1052855 [src:firmware-microbit-micropython] firmware-microbit-micropython: 
FTBFS: unsatisfiable build-dependencies: libstdc++-arm-none-eabi-dev (= 
15:12.2.rel1-1+23), gcc-arm-none-eabi (= 15:12.2.rel1-1)
Owner recorded as Nick Morrott .
> owner 1053224 Nick Morrott 
Bug #1053224 [nsxiv] Please sync supported MIME types with nsxiv.desktop
Owner recorded as Nick Morrott .
> owner 1056488 Nick Morrott 
Bug #1056488 [src:python-nudatus] python-nudatus autopkg tests fail with Python 
3.12
Owner recorded as Nick Morrott .
> owner 1058114 Nick Morrott 
Bug #1058114 [src:python-nudatus] python-nudatus: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit 
code 13
Owner recorded as Nick Morrott .
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1018658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018658
1018673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018673
1027378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027378
1044498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1044498
1045977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1045977
1049655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049655
1052855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052855
1053224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053224
1056488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056488
1058114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058114
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1063363: marked as done (nvidia-graphics-drivers: autopkgtest needs update for new version of linux)

[Debian Bug Tracking System]

Your message dated Sun, 11 Feb 2024 01:20:46 +
with message-id 
and subject line Bug#1063363: fixed in nvidia-graphics-drivers 535.54.03-1
has caused the Debian Bug report #1063363,
regarding nvidia-graphics-drivers: autopkgtest needs update for new version of 
linux
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1063363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063363
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: nvidia-graphics-drivers
Version: 525.147.05-5
Severity: serious
X-Debbugs-CC: li...@packages.debian.org
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:linux

Dear maintainer(s),

With a recent upload of linux the autopkgtest of nvidia-graphics-drivers 
fails in testing when that autopkgtest is run with the binary packages 
of linux from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
linux  from testing6.6.15-2
nvidia-graphics-drivers from testing525.147.05-5
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of linux to testing 
[1]. Of course, linux shouldn't just break your autopkgtest (or even 
worse, your package), but it seems to me that the change in linux was 
intended and your package needs to update to the new situation.


If this is a real problem in your package (and not only in your 
autopkgtest), the right binary package(s) from linux should really add a 
versioned Breaks on the unfixed version of (one of your) package(s). 
Note: the Breaks is nice even if the issue is only in the autopkgtest as 
it helps the migration software to figure out the right versions to 
combine in the tests.


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=linux

https://ci.debian.net/data/autopkgtest/testing/amd64/n/nvidia-graphics-drivers/42760274/log.gz


810s # MODPOST /usr/src/modules/nvidia-kernel/Module.symvers
810sscripts/mod/modpost -M -m   -o 
/usr/src/modules/nvidia-kernel/Module.symvers -T 
/usr/src/modules/nvidia-kernel/modules.order -i Module.symvers -e
811s ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only 
symbol '__rcu_read_unlock'
811s ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only 
symbol '__rcu_read_lock'
811s make[6]: *** 
[/usr/src/linux-headers-6.6.15-common/scripts/Makefile.modpost:145: 
/usr/src/modules/nvidia-kernel/Module.symvers] Error 1
811s make[5]: *** [/usr/src/linux-headers-6.6.15-common/Makefile:1890: 
modpost] Error 2
811s make[4]: *** [/usr/src/linux-headers-6.6.15-common/Makefile:246: 
__sub-make] Error 2

811s make[4]: Leaving directory '/usr/src/linux-headers-6.6.15-cloud-amd64'
811s make[3]: *** [Makefile:246: __sub-make] Error 2
811s make[3]: Leaving directory '/usr/src/linux-headers-6.6.15-common'
811s make[2]: *** [Makefile:82: modules] Error 2
811s make[2]: Leaving directory '/usr/src/modules/nvidia-kernel'
811s make[1]: *** [debian/rules:39: binary-modules] Error 2
811s make[1]: Leaving directory '/usr/src/modules/nvidia-kernel'
811s make: *** [/usr/share/modass/include/common-rules.make:56: 
kdist_build] Error 2

811s tput: No value for $TERM and no -T specified
811s BUILD FAILED!
811s tput: No value for $TERM and no -T specified
811s See 
/var/cache/modass/nvidia-kernel-source.buildlog.6.6.15-cloud-amd64.1707198843 
for details.

811s Build failed. Press Return to continue...
811s I: nvidia-kernel does not support the 6.6.15-rt-amd64 kernel 
(!CONFIG_PREEMPT_RT)

811s I: Summary:
811s I: FAIL nvidia-kernel 6.6.15-amd64 (7)
811s I: FAIL nvidia-kernel 6.6.15-cloud-amd64 (7)
811s I: SKIP nvidia-kernel 6.6.15-rt-amd64 (!CONFIG_PREEMPT_RT)
811s autopkgtest [05:58:24]: test m-a-autopkgtest



OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers
Source-Version: 535.54.03-1
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
nvidia-graphics-drivers, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1063...@bugs.debian.org,
and the maintainer will reo

Bug#1060164: (no subject)

[Gordon Ball]

Yes. I can see that there are API methods which expose nlohmann::json 
(eg, 
https://github.com/jupyter-xeus/xeus/blob/ebd21e9e7cfe143b4d0a6783112cc9006b456915/include/xeus/xdebugger.hpp#L55-L60) 
so changes the header library are going to cause ABI breakage.


I don't see much choice here but to binNMU xeus, xeus-zmq, xeus-python, 
which will presumably break custom kernels compiled against it and an 
older version of nl::json. I considered just updating everything to new 
versions and "rolling forward", but the latest version of xeus-zmq at 
least has an soversion bump so probably better to request binNMUs before 
waiting for NEW.

Bug#1052376: lxpanel: no longer obeys its geometry settings

[unknown]

Is there a way to help fixing that?

I get that the responsible DD(s) are ovewhelmed and unable to pay
attention to even a grave category bug. Could we somehow lend a hand?

Grigor

Bug#1063607: marked as done (igraph: FTBFS on i386: test::igraph_hrg (Failed))

[Debian Bug Tracking System]

Your message dated Sat, 10 Feb 2024 22:05:56 +
with message-id 
and subject line Bug#1063607: fixed in igraph 0.10.9+ds-2
has caused the Debian Bug report #1063607,
regarding igraph: FTBFS on i386: test::igraph_hrg (Failed)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1063607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063607
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: igraph
Version: 0.10.9+ds-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=igraph&arch=i386&ver=0.10.9%2Bds-1&stamp=1707132840&raw=0

526: Test timeout computed to be: 1500
521/554 Test #508: test::igraph_hrg 
...***Failed0.20 sec
-- Test case output differs from the expected output
-- See diff below:
-- ---
--- /<>/tests/unit/igraph_hrg.out  2024-02-04 21:40:29.0 
+
+++ /<>/_BUILD_STATIC/tests/test_igraph_hrg.out2024-02-05 
11:14:47.195150846 +
@@ -1,24 +1,24 @@
-Vertex # 25, left: # 29, right: # 43, prob: 0.0067
-Vertex # 26, left: # 13, right: # 46, prob:  1
-Vertex # 27, left: # 14, right: # 19, prob:  1
-Vertex # 28, left: # 15, right: # 16, prob:  0
-Vertex # 29, left: # 28, right: # 41, prob:   0.23
-Vertex # 30, left: # 33, right: # 37, prob:   0.13
-Vertex # 31, left: #  8, right: # 34, prob:  1
-Vertex # 32, left: # 23, right: # 24, prob:  0
-Vertex # 33, left: # 22, right: # 27, prob:  0
-Vertex # 34, left: #  7, right: # 44, prob:  1
-Vertex # 35, left: # 17, right: # 39, prob:0.1
-Vertex # 36, left: # 12, right: # 20, prob:  0
-Vertex # 37, left: # 26, right: # 36, prob:  0
-Vertex # 38, left: # 42, right: # 45, prob:  1
-Vertex # 39, left: # 21, right: # 48, prob:  0
-Vertex # 40, left: #  2, right: #  5, prob:  1
-Vertex # 41, left: # 32, right: # 35, prob:  0
-Vertex # 42, left: #  4, right: # 31, prob:  1
-Vertex # 43, left: #  0, right: # 47, prob:  1
-Vertex # 44, left: #  6, right: #  9, prob:  1
-Vertex # 45, left: #  1, right: # 40, prob:  1
-Vertex # 46, left: # 11, right: # 18, prob:  0
-Vertex # 47, left: #  3, right: # 38, prob:  1
-Vertex # 48, left: # 10, right: # 30, prob:   0.25
+Vertex # 25, left: # 33, right: # 36, prob:  0.029
+Vertex # 26, left: # 19, right: # 20, prob:  0
+Vertex # 27, left: # 14, right: # 26, prob:  1
+Vertex # 28, left: # 10, right: # 37, prob:   0.15
+Vertex # 29, left: # 21, right: # 30, prob:  0
+Vertex # 30, left: # 18, right: # 35, prob:  0
+Vertex # 31, left: #  1, right: # 42, prob:  1
+Vertex # 32, left: # 16, right: # 41, prob:  1
+Vertex # 33, left: # 32, right: # 39, prob:  0
+Vertex # 34, left: #  0, right: # 45, prob:  1
+Vertex # 35, left: # 11, right: # 17, prob:  0
+Vertex # 36, left: # 27, right: # 28, prob:  0
+Vertex # 37, left: # 43, right: # 48, prob:  0
+Vertex # 38, left: #  6, right: #  9, prob:  1
+Vertex # 39, left: # 13, right: # 29, prob:   0.75
+Vertex # 40, left: #  5, right: # 44, prob:  1
+Vertex # 41, left: # 23, right: # 24, prob:  0
+Vertex # 42, left: # 40, right: # 47, prob:  1
+Vertex # 43, left: #  3, right: # 31, prob:  1
+Vertex # 44, left: #  8, right: # 34, prob:  1
+Vertex # 45, left: #  2, right: #  4, prob:  1
+Vertex # 46, left: # 12, right: # 22, prob:  0
+Vertex # 47, left: #  7, right: # 38, prob:  1
+Vertex # 48, left: # 15, right: # 46, prob:  1
-- ---
CMake Error at /<>/etc/cmake/run_legacy_test.cmake:67 (message):
  Exiting test.


Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: igraph
Source-Version: 0.10.9+ds-2
Done: Jerome Benoit 

We believe that the bug you reported is fixed in the latest version of
igraph, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1063...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jerome Benoit  (supplier of updated igraph package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing 

Processed: bookworm-pu: package nvidia-graphics-drivers/525.147.05-6~deb12u1

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:nvidia-graphics-drivers
Bug #1063675 [release.debian.org] bookworm-pu: package 
nvidia-graphics-drivers/525.147.05-6~deb12u1
Added indication that 1063675 affects src:nvidia-graphics-drivers
> block 1063363 with -1
Bug #1063363 {Done: Andreas Beckmann } 
[src:nvidia-graphics-drivers] nvidia-graphics-drivers: autopkgtest needs update 
for new version of linux
1063363 was not blocked by any bugs.
1063363 was not blocking any bugs.
Added blocking bug(s) of 1063363: 1063675
> block 1062932 with -1
Bug #1062932 [nvidia-kernel-dkms] nvidia-kernel-dkms: dkms module won't build 
against linux-image-6.1.0-18-amd64 (6.1.76-1)
1062932 was not blocked by any bugs.
1062932 was not blocking any bugs.
Added blocking bug(s) of 1062932: 1063675

-- 
1062932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062932
1063363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063363
1063675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063675
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1061751: marked as done (python-django-debug-toolbar ftbfs with Python 3.12 as default)

[Debian Bug Tracking System]

Your message dated Sat, 10 Feb 2024 21:26:38 +
with message-id 
and subject line Bug#1061751: fixed in python-django-debug-toolbar 1:4.3-1
has caused the Debian Bug report #1061751,
regarding python-django-debug-toolbar ftbfs with Python 3.12 as default
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1061751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061751
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:python-django-debug-toolbar
Version: 1:4.2-1
Severity: serious
Tags: sid trixie ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12

With python3-defaults from experimental, the package fails to build:

[...]
==
FAIL: test_listcomp_escaped 
(tests.panels.test_profiling.ProfilingPanelTestCase.test_listcomp_escaped)

--
Traceback (most recent call last):
  File "/<>/tests/panels/test_profiling.py", line 59, in 
test_listcomp_escaped
self.assertIn('', 
content)
AssertionError: '' not 
found in '\n\n  \n\n  Call\n 
CumTime\n  Per\n  TotTime\n 
Per\n  Count\n\n  \n  \n 
 \n  id="profilingMain_0">\n\n  data-djdt-styles="paddingLeft:0px">\n\n  type="button" class="djProfileToggleDetails djToggleSwitch" 
data-toggle-name="profilingMain" data-toggle-id="0">-\n 
   \nclass="djdt-path">/<>/debug_toolbar/panels/class="djdt-file">__init__.py in class="djdt-func">process_request(class="djdt-lineno">195)\n  \n 
\n0.003\n0.003\n 
0.000\n0.000\n1\n 
\n\n  \n\n  data-djdt-styles="paddingLeft:16px">\n\n 
data-toggle-name="profilingMain" data-toggle-id="0_1">-\n 
 \nclass="djdt-path">/<>/tests/class="djdt-file">base.py in class="djdt-func">get_response(class="djdt-lineno">55)\n  \n\n 
   0.003\n0.003\n0.000\n 
   0.000\n1\n  \n\n  class="djdt-profile-row djdt-highlighted   djToggleDetails_0 
djToggleDetails_0_1" id="profilingMain_0_1_1">\n\n 
\n\n 
data-toggle-name="profilingMain" data-toggle-id="0_1_1">-\n 
   \nclass="djdt-path">/<>/tests/panels/class="djdt-file">test_profiling.py in class="djdt-func">(class="djdt-lineno">54)\n  \n\n 
   0.003\n0.003\n0.000\n 
   0.000\n1\n  \n\n  class="djdt-profile-row djdt-highlighted   djToggleDetails_0 
djToggleDetails_0_1 djToggleDetails_0_1_1" id="profilingMain_0_1_1_1">\n 
   \n  \n 
  \n  class="djProfileToggleDetails djToggleSwitch" 
data-toggle-name="profilingMain" data-toggle-id="0_1_1_1">-\n 
 \nclass="djdt-path">/<>/tests/class="djdt-file">views.py in class="djdt-func">listcomp_view(class="djdt-lineno">54)\n  \n\n 
   0.003\n0.003\n0.003\n 
   0.003\n1\n  \n\n  class="djdt-profile-row   djToggleDetails_0 djToggleDetails_0_1 
djToggleDetails_0_1_1 djToggleDetails_0_1_1_1" 
id="profilingMain_0_1_1_1_1">\n\n  data-djdt-styles="paddingLeft:64px">\n\n  class="djNoToggleSwitch">\n\nclass="djdt-stack">class="djdt-path">/usr/lib/python3/dist-packages/django/class="djdt-file">shortcuts.py in class="djdt-func">render(class="djdt-lineno">17)\n  \n\n 
   0.000\n0.000\n0.000\n 
   0.000\n1\n  \n\n 
\n\n'


--
Ran 142 tests in 1.281s

FAILED (failures=1, skipped=20)
--- End Message ---
--- Begin Message ---
Source: python-django-debug-toolbar
Source-Version: 1:4.3-1
Done: Carsten Schoenert 

We believe that the bug you reported is fixed in the latest version of
python-django-debug-toolbar, which is due to be installed in the Debian FTP 
archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1061...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Carsten Schoenert  (supplier of updated 
python-django-debug-toolbar package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please

Bug#1063671: FTBFS: 32 bit arm fail with undefined reference to `raise_func_trampoline'

[Petter Reinholdtsen]

Package: wine
Version: 9.0~repack-3
Severity: serious
Forwarded: https://gitlab.winehq.org/wine/wine/-/merge_requests/4928

The current build fail on 32 bit arm architectures with the following
error:

  /usr/bin/ld: dlls/ntdll/unix/signal_arm.o: in function 
`libunwind_virtual_unwind':
  ./dlls/ntdll/unix/signal_arm.c:724:(.text+0x69c): undefined reference to 
`raise_func_trampoline'
  collect2: error: ld returned 1 exit status
  make[2]: *** [Makefile:15978: dlls/ntdll/ntdll.so] Error 1

The problem seem to have been fixed upstream in 
https://gitlab.winehq.org/wine/wine/-/commit/4e9838fbc2d9ccca1e8b5a80d0e9000bfacc4938
 >
and the fix was included in the 9.2 release recently tagged.

-- 
Happy hacking
Petter Reinholdtsen

Bug#1062932: nvidia-graphics-drivers: Version 525.147.05-6 not available in stable, dkms fails with kernel 6.1.0-18

[M G]

Dear maintainers,

Debian 12.5 stable updated here from the main repo, impossible to
compile nvidia module with dkms on 6.1.0-18.


Same error as everyone else:
ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol
'__rcu_read_lock'
ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol
'__rcu_read_unlock'

In addition to here, they talk about it here:

https://forums.developer.nvidia.com/t/linux-6-7-3-545-29-06-550-40-07-error-modpost-gpl-incompatible-module-nvidia-ko-uses-gpl-only-symbol-rcu-read-lock/280908/55

Machines are stuck and can't boot up with the graphics cards working, you
have to apply the solution, everyone is going to be impacted.

Regards,
Maxime.

Bug#1063666: adwaita-icon-theme: 46 breaks gnome-shell cursor, fixed with mutter 44.8-3

[Jeremy Bícha]

Source: adwaita-icon-theme
Version: 46~beta-1
Severity: serious
Tags: pending trixie

I am filing this bug as a duplicate of https://bugs.debian.org/1063640
to prevent adwaita-icon-theme 46~beta-1 from migrating to Testing
until mutter 44.8-3 migrates first.

Thank you,
Jeremy Bícha

Bug#1063664: gcc-13-cross: file conflicts between gnat-13- and gnat-{9,10}-

[Andreas Beckmann]

Source: gcc-13-cross
Version: 14
Severity: serious

Hi,

there are undeclared file conflicts between gnat-13- and
gnat-{9,10}- in sid. (but not between -9- and -10-).
Maybe it would be sufficient to rebuild the package against gcc-13
13.2.0-13 which had some gnat conflict fixes.

The conflicting files e.g. for gnat-13-aarch64-linux-gnu on amd64 are

usr/aarch64-linux-gnu/lib/libgnarl.so
usr/aarch64-linux-gnu/lib/libgnat.so
usr/bin/aarch64-linux-gnu-gnat
usr/bin/aarch64-linux-gnu-gnatbind
usr/bin/aarch64-linux-gnu-gnatchop
usr/bin/aarch64-linux-gnu-gnatclean
usr/bin/aarch64-linux-gnu-gnatgcc
usr/bin/aarch64-linux-gnu-gnathtml
usr/bin/aarch64-linux-gnu-gnatkr
usr/bin/aarch64-linux-gnu-gnatlink
usr/bin/aarch64-linux-gnu-gnatls
usr/bin/aarch64-linux-gnu-gnatmake
usr/bin/aarch64-linux-gnu-gnatname
usr/bin/aarch64-linux-gnu-gnatprep
usr/share/man/man1/aarch64-linux-gnu-gnat.1.gz
usr/share/man/man1/aarch64-linux-gnu-gnatbind.1.gz
usr/share/man/man1/aarch64-linux-gnu-gnatchop.1.gz
usr/share/man/man1/aarch64-linux-gnu-gnatclean.1.gz
usr/share/man/man1/aarch64-linux-gnu-gnathtml.1.gz
usr/share/man/man1/aarch64-linux-gnu-gnatkr.1.gz
usr/share/man/man1/aarch64-linux-gnu-gnatlink.1.gz
usr/share/man/man1/aarch64-linux-gnu-gnatls.1.gz
usr/share/man/man1/aarch64-linux-gnu-gnatmake.1.gz
usr/share/man/man1/aarch64-linux-gnu-gnatname.1.gz
usr/share/man/man1/aarch64-linux-gnu-gnatprep.1.gz


Andreas

Processed: Bug 1061034

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 1061034 lcl-utils-3.0 Missing dependencies for lazbuild
Bug #1061034 [lcl-utils-3.0] c-evo-dh: FTBFS: make[1]: *** [debian/rules:39: 
override_dh_auto_build] Error 2
Changed Bug title to 'lcl-utils-3.0 Missing dependencies for lazbuild' from 
'c-evo-dh: FTBFS: make[1]: *** [debian/rules:39: override_dh_auto_build] Error 
2'.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1061034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061034
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 1062582 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1062582 serious
Bug #1062582 [src:mkdocs-material] mkdocs-material: Files installed under wrong 
dir (/usr/lib/python3.11), breaking reverse-deps
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1062582: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062582
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1063640: marked as done (adwaita-icon-theme: cursor theme not found)

[Debian Bug Tracking System]

Your message dated Sat, 10 Feb 2024 18:23:54 +
with message-id 
and subject line Bug#1063640: fixed in mutter 44.8-3
has caused the Debian Bug report #1063640,
regarding adwaita-icon-theme: cursor theme not found
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1063640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063640
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: adwaita-icon-theme
Version: 46~beta-1
Severity: normal

Hi,

After upgrading to 46~beta-1 gnome-shell doesn't find a cursor theme
anymore, I get this line in the journalctl output:

  feb 10 11:02:08 stab gnome-shell[999044]: No cursor theme available, please 
install a cursor theme

On X it then fallbacks to a default cursor theme, on Wayland it just
uses a white square as cursor.


   Frederic


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

Kernel: Linux 6.6.13-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.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 adwaita-icon-theme depends on:
ii  gtk-update-icon-cache  3.24.41-1
ii  hicolor-icon-theme 0.17-2

Versions of packages adwaita-icon-theme recommends:
ii  librsvg2-common  2.54.7+dfsg-2

adwaita-icon-theme suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: mutter
Source-Version: 44.8-3
Done: Jeremy Bícha 

We believe that the bug you reported is fixed in the latest version of
mutter, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1063...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated mutter package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 10 Feb 2024 07:56:05 -0500
Source: mutter
Built-For-Profiles: noudeb
Architecture: source
Version: 44.8-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bícha 
Closes: 1063640
Changes:
 mutter (44.8-3) unstable; urgency=medium
 .
   * Cherry-pick several cursor fix to fix compatibility with latest
 adwaita-icon-theme (Closes: #1063640)
Checksums-Sha1:
 cc24f335b5efe9edd4cb34e1c005db7c2eb02dd0 4424 mutter_44.8-3.dsc
 21cc4570ea53f89fbaf92f8a6a3bd9fb091efe50 91172 mutter_44.8-3.debian.tar.xz
 2faf3748da9f88f3dfac9a287d34663d5addad3e 22241 mutter_44.8-3_source.buildinfo
Checksums-Sha256:
 403a734e07ee2c4c57381dfc7d2b0205223b11b3f9a52f9504cb76dc719681ef 4424 
mutter_44.8-3.dsc
 ff1556ec066d0963e2c29bdf0818534b48a529895957303318928cb00923d15a 91172 
mutter_44.8-3.debian.tar.xz
 936c610b3c7231e9bb2c5e920a3798a1373300584e4bd68dc335a57524663e5f 22241 
mutter_44.8-3_source.buildinfo
Files:
 c0e3a4b26f1e7e700fa27297bba3e630 4424 x11 optional mutter_44.8-3.dsc
 721a0ae5ad55a17c76d18277e5720f18 91172 x11 optional mutter_44.8-3.debian.tar.xz
 d2f4c30a0eac56c63df9542bb9adced9 22241 x11 optional 
mutter_44.8-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmXHcx4ACgkQ5mx3Wuv+
bH05wBAA4b872A2sF2fcZdzKSo6T0weC3uQ4f0fAfvkLbXreAa41riBAGlWEAiVC
fqbol+CtsDjWP3irOe1vGt/TCBCLf4wteFd3SHIARHxsE1LWZWlPtoPljGOuvRo8
kqNSJ2RzY/wcbVsniB0Oy8CR+XUCxuw/Cs+IyvHLdcW/CA04jWExgqoHIj/pVrvC
yFl3PZbtnRgITXLDfYAy+yHBxFO2hKGY4YdBNqsc+PrCrDJsCzC5yoJ8/4v4L3WD
HeXP3205IYDNK9G+CP4jmMXnsBqZSzrG43U117ZmC09lskumT4voFI8eYHrbcz8d
UA9MiL/JybThbMPPW+fDaBOzfgDLC2NjaGo7prX+Wg4KWu3Ow/00rPb6vMObhPuh
BkXfP0KQImjazoSwg+W1ieVprGZz1JSviml3NN6CgQjwkZnc7QIzFacDy2IF4Zcx
JrFrR0nwHrJmoptetRYyq8dxOv4ctRTM4tTKemmzxG5PLxTwUI9h5sJx9y7NHZ0v
p87oTaLJ41Pg/YxuWam1NCV9nZKYOlkCs+LXVRLRkPGUNQjyzIMKKhog1cYmRANc
k3jYcUyB6v89gKRGHEIO4f4B90rOQF/iWSrXoic4d8ZwRXSGSii0y+MlBDwXDaln
2qrx5hxHWdnDk7LBNNaH2d8sU6G2pv16WJebJhE8xVqUyvBrn+s=
=ln6/
-END PGP SIGNATURE End Message ---

Bug#1058440: marked as done (python-aiosmtpd: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)

[Debian Bug Tracking System]

Your message dated Sat, 10 Feb 2024 18:24:12 +
with message-id 
and subject line Bug#1058440: fixed in python-aiosmtpd 1.4.4.post2-1
has caused the Debian Bug report #1058440,
regarding python-aiosmtpd: FTBFS: E: Build killed with signal TERM after 150 
minutes of inactivity
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1058440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058440
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-aiosmtpd
Version: 1.4.3-1.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> rootdir: /<>/.pybuild/cpython3_3.12_aiosmtpd/build
> configfile: pyproject.toml
> plugins: mock-3.12.0
> collected 563 items
> 
> aiosmtpd/qa/test_0packaging.py .s..  [  
> 0%]
> aiosmtpd/qa/test_1testsuite.py . [  
> 1%]
> aiosmtpd/tests/test_handlers.py  [  
> 8%]
> ..   [  
> 9%]
> aiosmtpd/tests/test_lmtp.py  [ 
> 10%]
> aiosmtpd/tests/test_main.py ..   [ 
> 17%]
> aiosmtpd/tests/test_proxyprotocol.py ... [ 
> 23%]
>  [ 
> 36%]
> .[ 
> 38%]
> aiosmtpd/tests/test_server.py ...
> E: Build killed with signal TERM after 150 minutes of inactivity


The full build log is available from:
http://qa-logs.debian.net/2023/12/12/python-aiosmtpd_1.4.3-1.1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20231212&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: python-aiosmtpd
Source-Version: 1.4.4.post2-1
Done: Jérémy Lal 

We believe that the bug you reported is fixed in the latest version of
python-aiosmtpd, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1058...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jérémy Lal  (supplier of updated python-aiosmtpd package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 10 Feb 2024 17:28:55 +0100
Source: python-aiosmtpd
Architecture: source
Version: 1.4.4.post2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Jérémy Lal 
Closes: 1056454 1058440
Changes:
 python-aiosmtpd (1.4.4.post2-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 1.4.4.post2.
   * Run pybuild testsuite, declare test files
   * Temporarily disable tests that hang with python 3.12.
 Other distributions are doing the same for now.
 Closes: #1056454, #1058440.
   * Standards-Version 4.6.2
Checksums-Sha1:
 753299d803a85f168c80efc36b15c34a6784c54c 2294 python-aiosmtpd_1.4.4.post2-1.dsc
 7a0c4817b0c3c427d080d3e985b25bd8c049a6b1 151613 
python-aiosmtpd_1.4.4.post2.orig.tar.gz
 38935409bc7f9194d4e325475cd525b894f8377a 6760 
python-aiosmtpd_1.4.4.post2-1.debian.tar.xz
 11a3a8f501bc9b00412f34861fe277c2f2c87770 9734 
python-aiosmtpd_1.4.4.post2-1_source.buildinfo
Checksums-Sha256:
 900b8c2f462158a6a0899a84dcf10eceaafc52eb

Bug#1056454: marked as done (python-smtpd's autopkg tests fail with Python 3.12)

[Debian Bug Tracking System]

Your message dated Sat, 10 Feb 2024 18:24:12 +
with message-id 
and subject line Bug#1056454: fixed in python-aiosmtpd 1.4.4.post2-1
has caused the Debian Bug report #1056454,
regarding python-smtpd's autopkg tests fail with Python 3.12
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1056454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056454
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:python-smtpd
Version: 1.4.3-1.1
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

python-smtpd's autopkg tests fail with Python 3.12:

[...]
359s autopkgtest [18:38:31]: test python3-aiosmtpd: [---
360s = test session starts 
==

360s platform linux -- Python 3.12.0+, pytest-7.4.3, pluggy-1.3.0
360s rootdir: /usr/lib/python3/dist-packages/aiosmtpd
360s plugins: mock-3.11.1
360s collected 554 items
360s
361s tests/test_handlers.py 
..[  8%]
361s tests/test_lmtp.py  
 [  9%]
374s tests/test_main.py .. 
 [ 15%]
374s tests/test_proxyprotocol.py 
 [ 23%]
383s 
 
[ 36%]
384s  
 [ 37%]
10364s tests/test_server.py ...autopkgtest 
[21:25:16]: ERROR: timed out on command "su -s /bin/bash ubuntu -c set 
-e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 || true;  . 
~/.profile >/dev/null 2>&1 || true; 
buildtree="/tmp/autopkgtest.OWMMXm/build.l6D/src"; mkdir -p -m 1777 -- 
"/tmp/autopkgtest.OWMMXm/python3-aiosmtpd-artifacts"; export 
AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest.OWMMXm/python3-aiosmtpd-artifacts"; 
export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755 
"/tmp/autopkgtest.OWMMXm/autopkgtest_tmp"; export 
AUTOPKGTEST_TMP="/tmp/autopkgtest.OWMMXm/autopkgtest_tmp"; export 
ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive; export 
LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=2; unset LANGUAGE 
LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE   LC_MONETARY LC_MESSAGES 
LC_PAPER LC_NAME LC_ADDRESS   LC_TELEPHONE LC_MEASUREMENT 
LC_IDENTIFICATION LC_ALL;rm -f /tmp/autopkgtest_script_pid; set -C; echo 
$$ > /tmp/autopkgtest_script_pid; set +C; trap "rm -f 
/tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd "$buildtree"; export 
'ADT_TEST_TRIGGERS=python3-defaults/3.11.4-5ubuntu1'; chmod +x 
/tmp/autopkgtest.OWMMXm/build.l6D/src/debian/tests/python3-aiosmtpd; 
touch /tmp/autopkgtest.OWMMXm/python3-aiosmtpd-stdout 
/tmp/autopkgtest.OWMMXm/python3-aiosmtpd-stderr; 
/tmp/autopkgtest.OWMMXm/build.l6D/src/debian/tests/python3-aiosmtpd 2> 
>(tee -a /tmp/autopkgtest.OWMMXm/python3-aiosmtpd-stderr >&2) > >(tee 
-a /tmp/autopkgtest.OWMMXm/python3-aiosmtpd-stdout);" (kind: test)
10364s autopkgtest [21:25:16]: test python3-aiosmtpd: 
---]
10364s autopkgtest [21:25:16]: test python3-aiosmtpd:  - - - - - - - - - 
- results - - - - - - - - - -

10364s python3-aiosmtpd FAIL timed out
--- End Message ---
--- Begin Message ---
Source: python-aiosmtpd
Source-Version: 1.4.4.post2-1
Done: Jérémy Lal 

We believe that the bug you reported is fixed in the latest version of
python-aiosmtpd, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1056...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jérémy Lal  (supplier of updated python-aiosmtpd package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 10 Feb 2024 17:28:55 +0100
Source: python-aiosmtpd
Architecture: source
Version: 1.4.4.post2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Jérémy Lal 
Closes: 1056454 1058440
Changes:
 python-aiosmtpd (1.4.4.post2-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 1.4.4.post2.
   * Run pybuild testsuite, declare test files
   * Temporarily disable tests that hang with python 3.12.
 Other distributions are doing the same for now.
 Closes: #1056454,

Bug#1042992: marked as done (micropython FTBFS with gcc 13)

[Debian Bug Tracking System]

Your message dated Sat, 10 Feb 2024 18:22:36 +
with message-id 
and subject line Bug#1042992: fixed in micropython 1.22.1+ds-1
has caused the Debian Bug report #1042992,
regarding micropython FTBFS with gcc 13
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1042992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042992
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: micropython
Version: 1.19.1+ds-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=micropython&arch=riscv64&ver=1.19.1%2Bds-1&stamp=1691093977&raw=0

...
../py/stackctrl.c: In function ‘mp_stack_ctrl_init’:
../py/stackctrl.c:32:32: error: storing the address of local variable 
‘stack_dummy’ in ‘mp_state_ctx.thread.stack_top’ [-Werror=dangling-pointer=]
   32 | MP_STATE_THREAD(stack_top) = (char *)&stack_dummy;
../py/stackctrl.c:31:18: note: ‘stack_dummy’ declared here
   31 | volatile int stack_dummy;
  |  ^~~
In file included from ../py/runtime.h:29,
 from ../py/stackctrl.c:27:
../py/mpstate.h:323:23: note: ‘mp_state_ctx’ declared here
  323 | extern mp_state_ctx_t mp_state_ctx;
  |   ^~~~
cc1: all warnings being treated as errors
make[2]: *** [../py/mkrules.mk:80: build/py/stackctrl.o] Error 1


micropython builds with the following two fixes:
https://github.com/micropython/micropython/commit/f1c6cb7725960487195daa5c5c196fd8d3563811
https://github.com/micropython/micropython/commit/32572439984e5640c6af46fbe7c27400c30112ce
--- End Message ---
--- Begin Message ---
Source: micropython
Source-Version: 1.22.1+ds-1
Done: Yangfl 

We believe that the bug you reported is fixed in the latest version of
micropython, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1042...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yangfl  (supplier of updated micropython package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 09 Feb 2024 21:23:24 +0800
Source: micropython
Architecture: source
Version: 1.22.1+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Yangfl 
Changed-By: Yangfl 
Closes: 1042992 1043530
Changes:
 micropython (1.22.1+ds-1) unstable; urgency=medium
 .
   * New upstream release
 * Fix FTBFS with gcc 13 (Closes: #1042992)
   * Enable manifest to ship uasyncio (Closes: #1043530)
   * Disable all tests due to buggy code quality
   * Bump Standards-Version to 4.6.2
Checksums-Sha1:
 9aa5d4405e25cd083f06e6fe9bc2f5c42ba92403 2119 micropython_1.22.1+ds-1.dsc
 4c8853d29afdd8c9b3094438968cae4fd8ca07b1 5645340 
micropython_1.22.1+ds.orig.tar.xz
 7447660f366924d1daa499d2b866b73a06ff8297 11760 
micropython_1.22.1+ds-1.debian.tar.xz
 aa035b06ce3d9f17c84eacbc22d80de9e9df7a71 9816 
micropython_1.22.1+ds-1_amd64.buildinfo
Checksums-Sha256:
 ac5d4c58cde5f21496192453cae9bffb79dc6e44b6707ba9a790efd89ccc2116 2119 
micropython_1.22.1+ds-1.dsc
 9010972e1b14159263667010d293a4291e8b5b1d0b220295af4b72909816afd8 5645340 
micropython_1.22.1+ds.orig.tar.xz
 00157dbb7b44bed15cbb6e7948a34b3f3e692de6162017d702ac5ea22d41a42d 11760 
micropython_1.22.1+ds-1.debian.tar.xz
 89dd0959c3f30d55b86f35118f2f8d44ec4795c44dd4324349221db527774ca8 9816 
micropython_1.22.1+ds-1_amd64.buildinfo
Files:
 de11e09281e7e24f81c127fe072781b4 2119 python optional 
micropython_1.22.1+ds-1.dsc
 c88090aaa1a2b762b0a7b92b5e3f88c1 5645340 python optional 
micropython_1.22.1+ds.orig.tar.xz
 da42838935e3f6e131245dbbfc282c17 11760 python optional 
micropython_1.22.1+ds-1.debian.tar.xz
 283bbbfadbfa614abef6f1a72b66336d 9816 python optional 
micropython_1.22.1+ds-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmXHkYcACgkQwpPntGGC
Ws6szA/+NHDkaGJIC97Rx5GafasPCMnX9LJH2lGcbGLUQmBxxog+psKkg1wqT9M6
xagWr90nBK3Xcqv8kxXDHYzmHt/0oUxe/EWPs1z4AoQELEatJ+63Vlyccqnvg7it
X8yz+mrQQsuQ9HMOSeS8mQsTNz6ccn4nH4N2QZnijorJlVCow5DNsKH4AAXPKrHa
AHrZF53ZyQfAYO8V2lIjbqQBVeSYTHSyV7TMA7PlTQfsdD+7AlfULi5H3tLeNtLs
UPVsMWQZV3GACIZna7ZVZz5kcZEANbe75KW4yl4klLEYbv3CoAYNlJxs+tj0zlYY
DNndM1zaz1E/AUIQnG1uKhSHZgHBtXhwoYsyJxWOaquFvciJA1jZV4IOapTnAzWE
Df1gf3Y

Processed (with 1 error): Re: Bug#1063662: bleachbit: Depends on transitional policykit-1

[Debian Bug Tracking System]

Processing control commands:

> merge -1 1025545
Bug #1063662 [bleachbit] bleachbit: Depends on transitional policykit-1
Unable to merge bugs because:
severity of #1025545 is 'serious' not 'important'
blocks of #1025545 is '1025540' not ''
done of #1025545 is 'Fabio Fantoni ' not ''
Failed to merge 1063662: Did not alter merged bugs.


-- 
1025545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025545
1063662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063662
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1052930: triton: FTBFS: make: *** [debian/rules:5: binary] Error 25

[Petter Reinholdtsen]

[Lucas Nussbaum]
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

Thank you for letting us know.  I have tried to figure out what is going wrong,
without success so far.  I can reproduce it in my sid chroot.

I tried replacing build dependencies libmlir-14-dev and mlir-14-tools with
libmlir-16-dev and mlir-16-tools to match the llvm version detected
during my build, but it still fail.  I do not undrestand cmake enough to
understand why it fail.

I also tried to fetch the latest upstream version, but it also fail to
build.

I would love some help figuring out what is going wrong here.
-- 
Happy hacking
Petter Reinholdtsen

Bug#1063416: marked as done (libgit2: CVE-2024-24577: Arbitrary code execution due to heap corruption in `git_index_add`)

[Debian Bug Tracking System]

Your message dated Sat, 10 Feb 2024 17:18:07 +
with message-id 
and subject line Bug#1063416: fixed in libgit2 1.1.0+dfsg.1-4+deb11u2
has caused the Debian Bug report #1063416,
regarding libgit2: CVE-2024-24577: Arbitrary code execution due to heap 
corruption in `git_index_add`
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1063416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063416
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgit2
Version: 1.7.1+ds-2
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 1.5.1+ds-1
Control: found -1 1.1.0+dfsg.1-4+deb11u1
Control: found -1 1.1.0+dfsg.1-4

Hi,

The following vulnerability was published for libgit2.

CVE-2024-24577[0]:
| libgit2 is a portable C implementation of the Git core methods
| provided as a linkable library with a solid API, allowing to build
| Git functionality into your application. Using well-crafted inputs
| to `git_index_add` can cause heap corruption that could be leveraged
| for arbitrary code execution. There is an issue in the
| `has_dir_name` function in `src/libgit2/index.c`, which frees an
| entry that should not be freed. The freed entry is later used and
| overwritten with potentially bad actor-controlled data leading to
| controlled heap corruption. Depending on the application that uses
| libgit2, this could lead to arbitrary code execution. This issue has
| been patched in version 1.6.5 and 1.7.2.


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-24577
https://www.cve.org/CVERecord?id=CVE-2024-24577
[1] https://github.com/libgit2/libgit2/security/advisories/GHSA-j2v7-4f6v-gpg8
[2] 
https://github.com/libgit2/libgit2/commit/eb4c1716cd92bf56f2770653a915d5fc01eab8f3
[3] 
https://github.com/libgit2/libgit2/commit/487af0cf6687dc48b0a960fa2f39894e2d84d77b

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libgit2
Source-Version: 1.1.0+dfsg.1-4+deb11u2
Done: Timo Röhling 

We believe that the bug you reported is fixed in the latest version of
libgit2, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1063...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Timo Röhling  (supplier of updated libgit2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 08 Feb 2024 18:22:27 +0100
Source: libgit2
Architecture: source
Version: 1.1.0+dfsg.1-4+deb11u2
Distribution: bullseye-security
Urgency: medium
Maintainer: Utkarsh Gupta 
Changed-By: Timo Röhling 
Closes: 1063416
Changes:
 libgit2 (1.1.0+dfsg.1-4+deb11u2) bullseye-security; urgency=medium
 .
   * Team upload.
   * Fix CVE-2024-24577: Use-after-free in git_index_add
 (Closes: #1063416)
Checksums-Sha1:
 f7a69de6a18130ce4a10aafb67c404b1cd8b4976 2102 
libgit2_1.1.0+dfsg.1-4+deb11u2.dsc
 b32593dbbf0e7a382118cc144cb9bcb4c22f33a7 2901284 
libgit2_1.1.0+dfsg.1.orig.tar.xz
 954b44ae15486815f7285209d6efedba2843f9d5 20560 
libgit2_1.1.0+dfsg.1-4+deb11u2.debian.tar.xz
 34ddd7c068e1ed32607fba15545684a39852ce5b 7443 
libgit2_1.1.0+dfsg.1-4+deb11u2_source.buildinfo
Checksums-Sha256:
 eb1c04a727f1f6f2b53ac590f907d4457476ffe824b34c45914d425432d74e14 2102 
libgit2_1.1.0+dfsg.1-4+deb11u2.dsc
 d3eba7909c5df1023c25a44ead8ee97cfc36da91a84ca50837d90f4521cf4e04 2901284 
libgit2_1.1.0+dfsg.1.orig.tar.xz
 5877ffeb58beba1b318d26e0da72ec8bccea488084330dff0c8340f4e90f8345 20560 
libgit2_1.1.0+dfsg.1-4+deb11u2.debian.tar.xz
 62c2b8bdeec8f9fa90ec26e40720f42016aed0f8afb43838972ca35de0963952 7443 
libgit2_1.1.0+dfsg.1-4+deb11u2_source.buildinfo
Files:
 c9ce9900f3c7b2e197a26fb903e507b2 2102 libs optional 
libgit2_1.1.0+dfsg.1-4+deb11u2.dsc
 950f6512ff615d6ad968b6f26eafff57 2901284 libs optional 
libgit2_1.1.0+dfsg.1.orig.tar.xz
 3536568eba5f489313dd45b7735fcaad 20560 libs optional 
libgit2_1.1.0+dfsg.1-4+deb11u2.debian.tar.xz
 23cc9fa3c38b0e78afec18e3bde15890 7443 libs optional 
libgit2_1.1.0+dfsg.1-4+deb11u2_source.buildinfo

-BE

Bug#1063416: marked as done (libgit2: CVE-2024-24577: Arbitrary code execution due to heap corruption in `git_index_add`)

[Debian Bug Tracking System]

Your message dated Sat, 10 Feb 2024 17:17:18 +
with message-id 
and subject line Bug#1063416: fixed in libgit2 1.5.1+ds-1+deb12u1
has caused the Debian Bug report #1063416,
regarding libgit2: CVE-2024-24577: Arbitrary code execution due to heap 
corruption in `git_index_add`
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1063416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063416
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgit2
Version: 1.7.1+ds-2
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 1.5.1+ds-1
Control: found -1 1.1.0+dfsg.1-4+deb11u1
Control: found -1 1.1.0+dfsg.1-4

Hi,

The following vulnerability was published for libgit2.

CVE-2024-24577[0]:
| libgit2 is a portable C implementation of the Git core methods
| provided as a linkable library with a solid API, allowing to build
| Git functionality into your application. Using well-crafted inputs
| to `git_index_add` can cause heap corruption that could be leveraged
| for arbitrary code execution. There is an issue in the
| `has_dir_name` function in `src/libgit2/index.c`, which frees an
| entry that should not be freed. The freed entry is later used and
| overwritten with potentially bad actor-controlled data leading to
| controlled heap corruption. Depending on the application that uses
| libgit2, this could lead to arbitrary code execution. This issue has
| been patched in version 1.6.5 and 1.7.2.


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-24577
https://www.cve.org/CVERecord?id=CVE-2024-24577
[1] https://github.com/libgit2/libgit2/security/advisories/GHSA-j2v7-4f6v-gpg8
[2] 
https://github.com/libgit2/libgit2/commit/eb4c1716cd92bf56f2770653a915d5fc01eab8f3
[3] 
https://github.com/libgit2/libgit2/commit/487af0cf6687dc48b0a960fa2f39894e2d84d77b

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libgit2
Source-Version: 1.5.1+ds-1+deb12u1
Done: Timo Röhling 

We believe that the bug you reported is fixed in the latest version of
libgit2, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1063...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Timo Röhling  (supplier of updated libgit2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 08 Feb 2024 12:31:43 +0100
Source: libgit2
Architecture: source
Version: 1.5.1+ds-1+deb12u1
Distribution: bookworm-security
Urgency: high
Maintainer: Utkarsh Gupta 
Changed-By: Timo Röhling 
Closes: 1063415 1063416
Changes:
 libgit2 (1.5.1+ds-1+deb12u1) bookworm-security; urgency=high
 .
   * Team upload.
   * Fix CVE-2024-24575: Denial of service attack in git_revparse_single
 (Closes: #1063415)
   * Fix CVE-2024-24577: Use-after-free in git_index_add
 (Closes: #1063416)
Checksums-Sha1:
 8d7b4020ea6712a2c9df2a791bb7bfc22d02477f 2112 libgit2_1.5.1+ds-1+deb12u1.dsc
 dd806b1ada676e13c58924f4b0326aafc236407f 3077056 libgit2_1.5.1+ds.orig.tar.xz
 9eed581e0778a7c8bf15a78b06102bd44f8e4d37 19664 
libgit2_1.5.1+ds-1+deb12u1.debian.tar.xz
 109e671818f976c5fa2b0b2be08d505481040f0b 7540 
libgit2_1.5.1+ds-1+deb12u1_source.buildinfo
Checksums-Sha256:
 b4de836d38cb2aca2687420754c5fa955f719934b92a4213d787d0b7dc2abebf 2112 
libgit2_1.5.1+ds-1+deb12u1.dsc
 96369433500bb528f036c16be9921bd437c098b745f1aaeccb91290815518970 3077056 
libgit2_1.5.1+ds.orig.tar.xz
 e869077309d8fa0bc56701970af7c6908d02674a89271f7cb29cb31814b69382 19664 
libgit2_1.5.1+ds-1+deb12u1.debian.tar.xz
 2e079099eb44ce076880d17d64bbce05ea6fce830a6ce6779acc1fa080cdca61 7540 
libgit2_1.5.1+ds-1+deb12u1_source.buildinfo
Files:
 0bf1984ee3362089aa4c5f769ede1037 2112 libs optional 
libgit2_1.5.1+ds-1+deb12u1.dsc
 e2c43b37fee144c89732adce700fba75 3077056 libs optional 
libgit2_1.5.1+ds.orig.tar.xz
 72c3b51c443d6129da0fe7038f2c7966 19664 libs optional 
libgit2_1.5.1+ds-1+deb12u1.debian.tar.xz
 267a637ab08981fb917804e3f19fbed9 7540 libs optional 
libgit2_1.5.1+ds-

Processed: Bug 1061034

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1061034 lcl-utils-3.0
Bug #1061034 [src:c-evo-dh] c-evo-dh: FTBFS: make[1]: *** [debian/rules:39: 
override_dh_auto_build] Error 2
Bug reassigned from package 'src:c-evo-dh' to 'lcl-utils-3.0'.
No longer marked as found in versions c-evo-dh/1.10-1.
Ignoring request to alter fixed versions of bug #1061034 to the same values 
previously set
> affects 1061034 c-evo-dh ddrescueview winff doublecmd
Bug #1061034 [lcl-utils-3.0] c-evo-dh: FTBFS: make[1]: *** [debian/rules:39: 
override_dh_auto_build] Error 2
Added indication that 1061034 affects c-evo-dh, ddrescueview, winff, and 
doublecmd
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1061034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061034
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1061034: Re Bug#1061034

[Peter B]

While Lazarus release (3.0+dfsg1-6) fixed the immediate problem
of ideconfig.lpk missing, lazbuilds still all fail, now with

"Note: (lazarus) Invalid Package Link: file 
"/usr/lib/lazarus/3.0/ide/packages/idedebugger/idedebugger.lpk" does not 
exist."


Builds fail on the firts missing (lazarus) package. Providing 
idedebugger.lpk alone may not be sufficient to fix builds


lazarus packages fail to build unless lazarus_src is included in build 
depends.

Affects c-evo-dh, ddrescueview, view3dscene, winff, doublecmd

Bug#1025084: ruby-graphlient fails to rebuild after updating ruby-faraday to upstream

[Pirate Praveen]

Control: fixed -1 0.7.0-1

On Wed, 7 Feb 2024 14:03:34 +0530 Praveen Arimbrathodiyil 
 wrote:

Control: severity -1 serious

On Sun, 18 Jun 2023 13:14:21 +0530 Pirate Praveen 
 wrote:
> 
> Since ruby-faraday-middleware is deprecated, we should update to 
> graphlient 0.7

ruby-faraday 2 is in unstable now.


Fixed in ruby-graphlient 0.7.0

Bug#1025084: marked as done (ruby-graphlient fails to rebuild after updating ruby-faraday to upstream)

[Debian Bug Tracking System]

Your message dated Sat, 10 Feb 2024 21:33:44 +0530
with message-id 
and subject line Re: ruby-graphlient fails to rebuild after updating 
ruby-faraday to upstream
has caused the Debian Bug report #1025084,
regarding ruby-graphlient fails to rebuild after updating ruby-faraday to 
upstream
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1025084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025084
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: ruby-graphlient
Version:  0.5.0-3
Severity: important

Dear Maintainer,

While updating ruby-faraday to new upstream, rebuild of ruby-graphlient 
fails

here is the log of the failed rebuild

cd gems/graphlient-0.5.0
rm -f
chmod 644 lib/graphlient/adapters/http/adapter.rb 
lib/graphlient/adapters/http/faraday_adapter.rb 
lib/graphlient/adapters/http/http_adapter.rb 
lib/graphlient/adapters/http.rb lib/graphlient/adapters.rb 
lib/graphlient/client.rb lib/graphlient/errors/client_error.rb 
lib/graphlient/errors/connection_failed_error.rb 
lib/graphlient/errors/error.rb lib/graphlient/errors/execution_error.rb 
lib/graphlient/errors/faraday_server_error.rb 
lib/graphlient/errors/graphql_error.rb 
lib/graphlient/errors/http_options_error.rb 
lib/graphlient/errors/http_server_error.rb 
lib/graphlient/errors/server_error.rb 
lib/graphlient/errors/timeout_error.rb lib/graphlient/errors.rb 
lib/graphlient/extensions/query.rb lib/graphlient/extensions.rb 
lib/graphlient/query.rb lib/graphlient/schema.rb 
lib/graphlient/version.rb lib/graphlient.rb

find lib/ -type d -empty -delete
cd -
cd -
dh_installchangelogs -pruby-graphlient /<>/CHANGELOG.md 
upstream

/usr/bin/ruby3.0 /usr/bin/gem2deb-test-runner

┌──┐
│ Checking Rubygems dependency resolution on 
ruby3.0   │

└──┘

GEM_PATH=/<>/debian/ruby-graphlient/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 
ruby3.0 -e gem\ \"graphlient\"
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:2248:in 
`raise_if_conflicts': Unable to activate faraday_middleware-1.0.0, 
because faraday-2.7.1 conflicts with faraday (~> 1.0) (Gem::ConflictError)
    from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1379:in 
`activate'
    from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1417:in 
`block in activate_dependencies'

    from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each'
    from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in 
`activate_dependencies'
    from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in 
`activate'
    from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `block 
in gem'
    from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
`synchronize'
    from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `gem'

    from -e:1:in `'
abbrev (default: 0.1.0)
activesupport (6.1.7)
addressable (2.8.0)
--- End Message ---
--- Begin Message ---

Control: fixed -1 0.7.0-1

On Wed, 7 Feb 2024 14:03:34 +0530 Praveen Arimbrathodiyil 
 wrote:

Control: severity -1 serious

On Sun, 18 Jun 2023 13:14:21 +0530 Pirate Praveen 
 wrote:
> 
> Since ruby-faraday-middleware is deprecated, we should update to 
> graphlient 0.7

ruby-faraday 2 is in unstable now.


Fixed in ruby-graphlient 0.7.0--- End Message ---

Processed: Re: ruby-graphlient fails to rebuild after updating ruby-faraday to upstream

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 0.7.0-1
Bug #1025084 [ruby-graphlient] ruby-graphlient fails to rebuild after updating 
ruby-faraday to upstream
There is no source info for the package 'ruby-graphlient' at version '0.7.0-1' 
with architecture ''
Unable to make a source version for version '0.7.0-1'
Marked as fixed in versions 0.7.0-1.

-- 
1025084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025084
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: unarchiving 1031888, tagging 1031888, affects 1031888

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> unarchive 1031888
Bug #1031888 {Done: Sean Whitton } [src:emacs] 
emacs-nox: bullseye-security update fails to install on mips64el
Unarchived Bug 1031888
> tags 1031888 + bullseye
Bug #1031888 {Done: Sean Whitton } [src:emacs] 
emacs-nox: bullseye-security update fails to install on mips64el
Added tag(s) bullseye.
> affects 1031888 + release.debian.org
Bug #1031888 {Done: Sean Whitton } [src:emacs] 
emacs-nox: bullseye-security update fails to install on mips64el
Ignoring request to set affects of bug 1031888 to the same value previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1031888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031888
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: RM: ruby-graphql-errors -- ROM; unmaintained upstream, incompatible with ruby-graphql 2.x

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:ruby-graphql-errors
Bug #1063655 [ftp.debian.org] RM: ruby-graphql-errors -- ROM; unmaintained 
upstream, incompatible with ruby-graphql 2.x
Added indication that 1063655 affects src:ruby-graphql-errors
> block 1063654 by -1
Bug #1063654 [ruby-graphql-errors] ruby-graphql-errors - upstream dead and 
incompatible with ruby-graphql 2.x
1063654 was not blocked by any bugs.
1063654 was not blocking any bugs.
Added blocking bug(s) of 1063654: 1063655

-- 
1063654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063654
1063655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1063654: ruby-graphql-errors - upstream dead and incompatible with ruby-graphql 2.x

[Pirate Praveen]

Package: ruby-graphql-errors
Version:  0.4.0-2
Severity: serious

source package has 1 unsatisfiable build dependency

Build dependencies in unstable cannot be satisfied on amd64 
because: unsatisfied dependency on ruby-graphql (< 2)


Last commint was 4 years ago and 
https://github.com/exAspArk/graphql-errors has a banner "This repository 
has been archived by the owner on Apr 8, 2020. It is now read-only."


This was originally packaged as build dependency for ruby-graphlient 
which no longer needs it.

Bug#1063609: marked as done (texstudio_4.7.2+ds-1_all-buildd.changes REJECTED)

[Debian Bug Tracking System]

Your message dated Sat, 10 Feb 2024 15:19:59 +
with message-id 
and subject line Bug#1063609: fixed in texstudio 4.7.2+ds-2
has caused the Debian Bug report #1063609,
regarding texstudio_4.7.2+ds-1_all-buildd.changes REJECTED
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1063609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063609
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: texstudio
Version: 4.7.2+ds-1
Severity: serious

On 2024-02-07 17:06, Debian FTP Masters wrote:
> 
> texstudio-doc_4.7.2+ds-1_all.deb: Built-Using refers to non-existing source 
> package python3-pygments (= 2.17.2+dfsg-1)
> 
> 
> Mapping sid to unstable.
> 
> ===
> 
> Please feel free to respond to this email if you don't understand why
> your files were rejected, or if you upload new files which address our
> concerns.
> 
> 
> 
--- End Message ---
--- Begin Message ---
Source: texstudio
Source-Version: 4.7.2+ds-2
Done: Tom Jampen 

We believe that the bug you reported is fixed in the latest version of
texstudio, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1063...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Tom Jampen  (supplier of updated texstudio package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 10 Feb 2024 11:07:30 +0100
Source: texstudio
Architecture: source
Version: 4.7.2+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Tom Jampen 
Changed-By: Tom Jampen 
Closes: 1063609
Changes:
 texstudio (4.7.2+ds-2) unstable; urgency=medium
 .
   * Improving version handling for Built-Using field (Closes: #1063609).
Checksums-Sha1:
 dc2683130248cfbf26a7e0be883f3aa3a3460ea0 2260 texstudio_4.7.2+ds-2.dsc
 079ee1464f3e59d198dfb051777926212cde2241 24784 
texstudio_4.7.2+ds-2.debian.tar.xz
 2f18ebe228701bbff8fa51e2428d79259a96b2de 17145 
texstudio_4.7.2+ds-2_source.buildinfo
Checksums-Sha256:
 ba5e560d92caf2a63c1f8e8af47e718c8af7316a2c1f01b32363f92107f11557 2260 
texstudio_4.7.2+ds-2.dsc
 311b465cb8d224bc5b3d2ad05fdeb97eec4ec2f48b71db7be32cac73fae5387e 24784 
texstudio_4.7.2+ds-2.debian.tar.xz
 1887026556fcb5b1d51878b7eb14ae16ac5bb5c8e2654e2982ed27caf4035e2b 17145 
texstudio_4.7.2+ds-2_source.buildinfo
Files:
 d723283bddfa67e454dd41b09d988122 2260 editors optional texstudio_4.7.2+ds-2.dsc
 1265561a62f740d429c93b698a42d662 24784 editors optional 
texstudio_4.7.2+ds-2.debian.tar.xz
 041afc71b74f23a3e7e755c06e3a87a4 17145 editors optional 
texstudio_4.7.2+ds-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEnpMtHgsxz4UK/Hmebz5hUxY+BXcFAmXHThQUHHRvbUBjcnlw
dG9ncmFwaHkuY2gACgkQbz5hUxY+BXfNKA/7B8Hv24eDVIlWHcZriQWvdfSE6+zr
5V03yEFr0y0bKIwmleGfN5yxu9rmRSCVRy/uJoSnx/CQ3i75tSPeWeQb/nKkk+mV
tyHd3YODg2P6kUY4/3dQnNEBdXRhZ49yaTHaGHyDqK4d2NLRo3JFG7ij9/+Bm6OZ
YH0BP7TrcJLL+o8Sdu95eN0MPkoUoyKSc4HNFhTnp/cTNf4U2DXZLHgOz/+1eH6Y
brVTS7HPc6vP0Bv7Vf4V2OuK2s8NOI7AGdD9vR7P7vkUzptQ3HbFvgjqpctpgQHK
UODOwExtncQvxUEEkGntNdAGoA8aIjwYVXyXXG5SYTp8N5qO8xzbS1xhx/a8t0ak
f3J82Ml9JPzSFp4tQAShiLziPMhxirGPA2gYGF3/vLINH2V+bnbaAJl7hK2gPwpN
RdPNmtuzYZ583OHcoafl9WLZ1tlKcsETq0T+00UvaCLFh9OI5gdwu31VC7r2NyGD
9g7KP/CLkOmP6BJyephcQLLY/DoZ3H21joq5zD7BBPoWAHgqhiKWmZe8EkuHzuiV
/cD4DTGMDTo/q5Sxll+yftwLDsOsyuPL3JQccjlsv0QECqbHD6S11nLZ2Re58TTK
vqSBA4H06gdPI84JbstOOacdt0gYweRb4feh45c29wfYwflPFyQYN1Q0UvOEfRA/
J4bz/9oI5qZ884w=
=Mzwq
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#1063361: nvidia-graphics-drivers-tesla-470: autopkgtest needs update for new version of linux

[Debian Bug Tracking System]

Processing control commands:

> tag 1063361 + bookworm
Bug #1063361 {Done: Andreas Beckmann } 
[src:nvidia-graphics-drivers-tesla-470] nvidia-graphics-drivers-tesla-470: 
autopkgtest needs update for new version of linux
Added tag(s) bookworm.

-- 
1063361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063361
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1063361: nvidia-graphics-drivers-tesla-470: autopkgtest needs update for new version of linux

[Florian Ernst]

Control: tag 1063361 + bookworm

On Sat, Feb 10, 2024 at 03:49:45PM +0100,  wrote:
> Control: found 1063361 470.223.02-2~deb12u1
> [...]
> Thus now marking this bug accordingly.

Not quite, but hopefully now.

FWIW, manually adding 0035-fix-build-w-kernel-6.1.76-6.6.15-6.7.3.patch[0]
fixes the build for me on bookworm as well.

Cheers,
Flo

[0] 
https://sources.debian.org/src/nvidia-graphics-drivers-tesla-470/470.223.02-4/debian/module/debian/patches/0035-fix-build-w-kernel-6.1.76-6.6.15-6.7.3.patch/


signature.asc
Description: PGP signature

Processed: tagging 1010120, tagging 985725, fixed 1062932 in 525.147.05-6

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1010120 + experimental
Bug #1010120 [src:thrift] thrift: FTBFS in bullseye (expired certificates in 
test suite)
Added tag(s) experimental.
> tags 985725 + trixie experimental
Bug #985725 {Done: Gennaro Oliva } [src:slurm-wlm] 
slurm-wlm: flaky autopkgtest: srun: Required node not available (down, drained 
or reserved)
Added tag(s) trixie and experimental.
> fixed 1062932 525.147.05-6
Bug #1062932 [nvidia-kernel-dkms] nvidia-kernel-dkms: dkms module won't build 
against linux-image-6.1.0-18-amd64 (6.1.76-1)
Marked as fixed in versions nvidia-graphics-drivers/525.147.05-6.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1010120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010120
1062932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062932
985725: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985725
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 1062932 is grave

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1062932 grave
Bug #1062932 [nvidia-kernel-dkms] nvidia-kernel-dkms: dkms module won't build 
against linux-image-6.1.0-18-amd64 (6.1.76-1)
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1062932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1063632: marked as done (spirv-llvm-translator-17 FTBFS: error: ‘CapabilityLongConstantCompositeINTEL’ was not declared in this scope)

[Debian Bug Tracking System]

Your message dated Sat, 10 Feb 2024 15:07:12 +
with message-id 
and subject line Bug#1063632: fixed in spirv-llvm-translator-17 17.0.0-4
has caused the Debian Bug report #1063632,
regarding spirv-llvm-translator-17 FTBFS: error: 
‘CapabilityLongConstantCompositeINTEL’ was not declared in this scope
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1063632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063632
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spirv-llvm-translator-17
Version: 17.0.0-3
Severity: serious
Tags: ftbfs
Forwarded: https://github.com/KhronosGroup/SPIRV-LLVM-Translator/issues/2261

https://buildd.debian.org/status/logs.php?pkg=spirv-llvm-translator-17&ver=17.0.0-3%2Bb1

...
In file included from /<>/lib/SPIRV/libSPIRV/SPIRVModule.h:44,
 from /<>/lib/SPIRV/LLVMToSPIRVDbgTran.h:42,
 from /<>/lib/SPIRV/LLVMToSPIRVDbgTran.cpp:38:
/<>/lib/SPIRV/libSPIRV/SPIRVEntry.h: In member function 
‘SPIRV::SPIRVCapVec 
SPIRV::SPIRVContinuedInstINTELBase::getRequiredCapability() const’:
/<>/lib/SPIRV/libSPIRV/SPIRVEntry.h:911:19: error: 
‘CapabilityLongConstantCompositeINTEL’ was not declared in this scope
  911 | return getVec(CapabilityLongConstantCompositeINTEL);
  |   ^~~~
...
--- End Message ---
--- Begin Message ---
Source: spirv-llvm-translator-17
Source-Version: 17.0.0-4
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
spirv-llvm-translator-17, which is due to be installed in the Debian FTP 
archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1063...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated 
spirv-llvm-translator-17 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 10 Feb 2024 10:17:54 +0100
Source: spirv-llvm-translator-17
Architecture: source
Version: 17.0.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenCL team 
Changed-By: Andreas Beckmann 
Closes: 1063632
Changes:
 spirv-llvm-translator-17 (17.0.0-4) unstable; urgency=medium
 .
   * Restrict watch file to 17.* releases.
   * Update .symbols control file.
   * Add build-needed autopkgtest for spirv-headers compat check.
   * Update from llvm_release_170 branch.  (Closes: #1063632)
   * Bump spirv-headers dependency to 1.6.1+1.3.275.0.
Checksums-Sha1:
 ff22293a687da72dae31e97041504ac5b77e0cb9 2597 
spirv-llvm-translator-17_17.0.0-4.dsc
 d88e27f81712dfa53fe7c6710e04187d402a0060 18452 
spirv-llvm-translator-17_17.0.0-4.debian.tar.xz
 26c26b13b4551d4531e125741fb89af3dc2a36c7 8159 
spirv-llvm-translator-17_17.0.0-4_source.buildinfo
Checksums-Sha256:
 4dd0c52d7ec3b81b4ce69b13b3c884043c99df603031963939f81f8cb46ffc6f 2597 
spirv-llvm-translator-17_17.0.0-4.dsc
 840dd93b6a9f98254f26e6866f3e9d1c51096c7903c1d5b6c5e98c3157b0cbf7 18452 
spirv-llvm-translator-17_17.0.0-4.debian.tar.xz
 7c150c6bfac94507d2ba3594cfbd0641c8c093b911ff572b146e04042fbb3be6 8159 
spirv-llvm-translator-17_17.0.0-4_source.buildinfo
Files:
 30de55f79a925491a081936fff0990cb 2597 libdevel optional 
spirv-llvm-translator-17_17.0.0-4.dsc
 d4d9e4f1875856688668811dd6c5e44a 18452 libdevel optional 
spirv-llvm-translator-17_17.0.0-4.debian.tar.xz
 7ab6ba1f54875029a638ba43b1690fbb 8159 libdevel optional 
spirv-llvm-translator-17_17.0.0-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmXHP/kQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCOLZD/9AEL8/CA4j5TXKEyV06IOl7dGuJIaAeNhU
/drsJ5pBPnRFY5h+Me7vKcVrSznGGSMhSjoZF+qlMCGUojvxRMVTWBVIbWpzHVxM
SaeLMFM5ysw2fUUF4YxwTnS9I0EQHKLGI3LqEvgUV2vWcvr/hKifS0nvqd73ZV0h
pHwGGv6UU3UgfHzDcCSZfZSksxs5rqlZsddISBwBvZTY8vusFEFbYyj7mTjw/UGU
3pS9NNsIFVwFDV+ZHEodb/QirhQpRkyWN6wR4Qhh/ashQTut1q+pvTjz6lloDQ/m
SD3cBCHWKHqs9ab0ZhFUnfwjU3wuYdjmfurga7pf+vYiCkG+atTOVH08ua5F2RGf
YOsH7MRXeAWbI/1/VGK7/Jw+Fw2+gbI0eJfr3iDWa7w5j6pXGWZ9cdkuKzAFZPq+
Z9w867GjisXYuyzfXaTL7ZsbLyAxaJUYY4AHPPNJ0+rXNmQZW0nRycaWgv6RuG+8
fnTcZkowwuJNuaUglGAFB7BimUqjwZpzqZ8KBP07kZqgzdTV/ffy/b3uESSI4b6U
/1fVgk7kMrVxRo21pCtjIFqhughTD5yTm5MIbCwDCDNpPfdQeeyfLoVEAe3D35VS
Yk05BIL4kpFf4e/DPnCXCf36pAtD

Bug#1063361: nvidia-graphics-drivers-tesla-470: autopkgtest needs update for new version of linux

[Florian Ernst]

Control: found 1063361 470.223.02-2~deb12u1

On Tue, Feb 06, 2024 at 09:18:15PM +0100, Paul Gevers wrote:
> Source: nvidia-graphics-drivers-tesla-470
> Version: 470.223.02-3
> Severity: serious
> X-Debbugs-CC: li...@packages.debian.org
> Tags: sid trixie
> User: debian...@lists.debian.org
> Usertags: needs-update
> Control: affects -1 src:linux
> [...]
> 320s # MODPOST
> /var/lib/dkms/nvidia-tesla-470/470.223.02/build/Module.symvers
> 320sscripts/mod/modpost -M -m   -o
> /var/lib/dkms/nvidia-tesla-470/470.223.02/build/Module.symvers -T
> /var/lib/dkms/nvidia-tesla-470/470.223.02/build/modules.order -i
> Module.symvers -e
> 320s ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol
> '__rcu_read_unlock'
> 320s ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol
> '__rcu_read_lock'
> 320s make[4]: ***
> [/usr/src/linux-headers-6.6.15-common/scripts/Makefile.modpost:145:
> /var/lib/dkms/nvidia-tesla-470/470.223.02/build/Module.symvers] Error 1

Well, now that Linux 6.1.76 has entered Bookworm as part of today's
point release[0] this bug eccurs there as well. Here the end of my
/var/lib/dkms/nvidia-tesla-470/470.223.02/build/make.log:

| sh /usr/src/linux-headers-6.1.0-18-common/scripts/modules-check.sh 
/var/lib/dkms/nvidia-tesla-470/470.223.02/build/modules.order
| make -f /usr/src/linux-headers-6.1.0-18-common/scripts/Makefile.modpost
|sed 's/ko$/o/'  
/var/lib/dkms/nvidia-tesla-470/470.223.02/build/modules.order | 
scripts/mod/modpost -m -o 
/var/lib/dkms/nvidia-tesla-470/470.223.02/build/Module.symvers -e -i 
Module.symvers -T -
| ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol 
'__rcu_read_lock'
| ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol 
'__rcu_read_unlock'
| make[3]: *** 
[/usr/src/linux-headers-6.1.0-18-common/scripts/Makefile.modpost:126: 
/var/lib/dkms/nvidia-tesla-470/470.223.02/build/Module.symvers] Error 1
| make[2]: *** [/usr/src/linux-headers-6.1.0-18-common/Makefile:1991: modpost] 
Error 2
| make[2]: Leaving directory '/usr/src/linux-headers-6.1.0-18-amd64'
| make[1]: *** [Makefile:250: __sub-make] Error 2
| make[1]: Leaving directory '/usr/src/linux-headers-6.1.0-18-common'
| make: *** [Makefile:80: modules] Error 2

Thus now marking this bug accordingly.

Cheers,
Flo


[0] 
https://tracker.debian.org/news/1499745/accepted-linux-6176-1-source-into-proposed-updates/


signature.asc
Description: PGP signature

Processed: Re: Bug#1063361: nvidia-graphics-drivers-tesla-470: autopkgtest needs update for new version of linux

[Debian Bug Tracking System]

Processing control commands:

> found 1063361 470.223.02-2~deb12u1
Bug #1063361 {Done: Andreas Beckmann } 
[src:nvidia-graphics-drivers-tesla-470] nvidia-graphics-drivers-tesla-470: 
autopkgtest needs update for new version of linux
Marked as found in versions 
nvidia-graphics-drivers-tesla-470/470.223.02-2~deb12u1.

-- 
1063361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063361
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1056793: False positive bug?

[Matthew Vernon]

Hi,

I looked at the build log, and the problems look to be disk related?

/usr/bin/ld: final link failed: No space left on device
collect2: error: ld returned 1 exit status

(there follow further ENOSPC and also some No such file or directory 
errors, which presumably relate to things not written because of running 
out of space).


...so maybe the answer is not to go to cython-legacy, but to try a build 
somewhere with more disk?


Regards,

Matthew

Processed: severity of 1062484 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1062484 important
Bug #1062484 [src:libnma] libnma: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1062484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062484
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 1052763 to src:gnuastro, fixed 1052763 in 0.22-1, reassign 1062350 to src:gnuastro ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1052763 src:gnuastro 0.20-1
Bug #1052763 {Done: Phil Wyett } [libgnuastro18] 
libgnuastro18 has an undeclared file conflict on 
/usr/lib/x86_64-linux-gnu/libgnuastro_make.so
Warning: Unknown package 'libgnuastro18'
Bug reassigned from package 'libgnuastro18' to 'src:gnuastro'.
No longer marked as found in versions gnuastro/0.20-1.
No longer marked as fixed in versions gnuastro/0.22-1.
Bug #1052763 {Done: Phil Wyett } [src:gnuastro] 
libgnuastro18 has an undeclared file conflict on 
/usr/lib/x86_64-linux-gnu/libgnuastro_make.so
Marked as found in versions gnuastro/0.20-1.
> fixed 1052763 0.22-1
Bug #1052763 {Done: Phil Wyett } [src:gnuastro] 
libgnuastro18 has an undeclared file conflict on 
/usr/lib/x86_64-linux-gnu/libgnuastro_make.so
Marked as fixed in versions gnuastro/0.22-1.
> reassign 1062350 src:gnuastro 0.20-1.1~exp1
Bug #1062350 {Done: Lukas Märdian } [libgnuastro18t64] 
libgnuastro18t64 has an undeclared file conflict on 
/usr/lib/x86_64-linux-gnu/libgnuastro_make.so
Warning: Unknown package 'libgnuastro18t64'
Bug reassigned from package 'libgnuastro18t64' to 'src:gnuastro'.
No longer marked as found in versions gnuastro/0.20-1.1~exp1.
No longer marked as fixed in versions gnuastro/0.20-1.1~exp2.
Bug #1062350 {Done: Lukas Märdian } [src:gnuastro] 
libgnuastro18t64 has an undeclared file conflict on 
/usr/lib/x86_64-linux-gnu/libgnuastro_make.so
Marked as found in versions gnuastro/0.20-1.1~exp1.
> fixed 1062350 0.20-1.1~exp2
Bug #1062350 {Done: Lukas Märdian } [src:gnuastro] 
libgnuastro18t64 has an undeclared file conflict on 
/usr/lib/x86_64-linux-gnu/libgnuastro_make.so
Marked as fixed in versions gnuastro/0.20-1.1~exp2.
> reassign 1062353 src:globus-common 18.13-2.1~exp1
Bug #1062353 {Done: Lukas Märdian } [libglobus-common0t64] 
libglobus-common0t64 has an undeclared file conflict
Warning: Unknown package 'libglobus-common0t64'
Bug reassigned from package 'libglobus-common0t64' to 'src:globus-common'.
No longer marked as found in versions globus-common/18.13-2.1~exp1.
No longer marked as fixed in versions globus-common/18.13-2.1~exp2.
Bug #1062353 {Done: Lukas Märdian } [src:globus-common] 
libglobus-common0t64 has an undeclared file conflict
Marked as found in versions globus-common/18.13-2.1~exp1.
> fixed 1062353 18.13-2.1~exp2
Bug #1062353 {Done: Lukas Märdian } [src:globus-common] 
libglobus-common0t64 has an undeclared file conflict
Marked as fixed in versions globus-common/18.13-2.1~exp2.
> tags 1063645 + experimental
Bug #1063645 [src:markdown] markdown: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) experimental.
> tags 1061605 - sid trixie
Bug #1061605 [src:scipy] scipy: tests skipped during build and autopkgtest not 
in sync
Removed tag(s) sid and trixie.
> tags 1063499 - sid trixie
Bug #1063499 {Done: Matthias Geiger } 
[src:rust-gobject-sys] rust-gobject-sys FTBFS with nocheck build profile: cp: 
cannot stat '/usr/share/gir-1.0/GObject-2.0.gir': No such file or directory
Removed tag(s) sid and trixie.
> tags 1063498 - sid trixie
Bug #1063498 {Done: Helmut Grohne } [src:rust-glib-sys] 
rust-glib-sys FTBFS with the nocheck build profile: cp: cannot stat 
'/usr/share/gir-1.0/GLib-2.0.gir': No such file or directory
Removed tag(s) trixie and sid.
> tags 1061760 + experimental
Bug #1061760 [src:sasview] sasview ftbfs with Python 3.12 as default
Added tag(s) experimental.
> tags 1029451 + experimental
Bug #1029451 [src:gnome-remote-desktop] gnome-remote-desktop FTBFS with nocheck 
profile: missing gudev-1.0.pc
Added tag(s) experimental.
> tags 1058327 - sid trixie
Bug #1058327 [python3-protobuf] python-limits: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit 
code 13
Removed tag(s) trixie and sid.
> tags 1063281 - sid trixie
Bug #1063281 {Done: Rene Engelhard } [src:xmlsec1] xmlsec1: 
NMU diff for 64-bit time_t transition
Removed tag(s) sid and trixie.
> tags 1063202 - sid trixie
Bug #1063202 {Done: Sam Hartman } [src:pam] pam: NMU diff 
for 64-bit time_t transition
Removed tag(s) trixie and sid.
> found 1061205 6.4.2-3
Bug #1061205 [src:qt6-tools] Please upgrade to llvm-toolchain-17
Marked as found in versions qt6-tools/6.4.2-3.
> tags 1061205 - sid trixie
Bug #1061205 [src:qt6-tools] Please upgrade to llvm-toolchain-17
Removed tag(s) sid and trixie.
> tags 1061464 - sid trixie
Bug #1061464 [src:tracker] tracker FTBFS with nocheck profile: 
../meson.build:99:26: ERROR: python3 is missing modules: gi
Removed tag(s) sid and trixie.
> tags 1044060 + experimental
Bug #1044060 [src:q2-quality-control] q2-quality-control: test failure with 
pandas 2.0
Added tag(s) experimental.
> tags 1059671 + experimental
Bug #1059671 [python3-capstone] python3-capstone: Python 3.12 has no module 
named 'distutils'
Added tag(s) experimental.
> tags 1061633 + experimental
Bug #1061633 [src:libtemplates-parser] libtemplates-parser: autopkgtest needs 
update

Processed: Re: adwaita-icon-theme: cursor theme not found

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 1063640 src:adwaita-icon-theme
Bug #1063640 [src:mutter] adwaita-icon-theme: cursor theme not found
Added indication that 1063640 affects src:adwaita-icon-theme
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1063640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063640
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1063603: marked as done (composer: CVE-2024-24821)

[Debian Bug Tracking System]

Your message dated Sat, 10 Feb 2024 13:11:21 +
with message-id 
and subject line Bug#1063603: fixed in composer 2.7.1-1
has caused the Debian Bug report #1063603,
regarding composer: CVE-2024-24821
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1063603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063603
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: composer
Version: 2.6.6-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for composer.

CVE-2024-24821[0]:
| Composer is a dependency Manager for the PHP language. In affected
| versions several files within the local working directory are
| included during the invocation of Composer and in the context of the
| executing user. As such, under certain conditions arbitrary code
| execution may lead to local privilege escalation, provide lateral
| user movement or malicious code execution when Composer is invoked
| within a directory with tampered files. All Composer CLI commands
| are affected, including composer.phar's self-update. The following
| scenarios are of high risk: Composer being run with sudo, Pipelines
| which may execute Composer on untrusted projects, Shared
| environments with developers who run Composer individually on the
| same project. This vulnerability has been addressed in versions
| 2.7.0 and 2.2.23. It is advised that the patched versions are
| applied at the earliest convenience. Where not possible, the
| following should be addressed: Remove all sudo composer privileges
| for all users to mitigate root privilege escalation, and avoid
| running Composer within an untrusted directory, or if needed, verify
| that the contents of `vendor/composer/InstalledVersions.php` and
| `vendor/composer/installed.php` do not include untrusted code.  A
| reset can also be done on these files by the following:```sh rm
| vendor/composer/installed.php vendor/composer/InstalledVersions.php
| composer install --no-scripts --no-plugins ```


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-24821
https://www.cve.org/CVERecord?id=CVE-2024-24821
[1] https://github.com/composer/composer/security/advisories/GHSA-7c6p-848j-wh5h
[2] 
https://github.com/composer/composer/commit/64e4eb356b159a30c766cd1ea83450a38dc23bf5

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: composer
Source-Version: 2.7.1-1
Done: David Prévot 

We believe that the bug you reported is fixed in the latest version of
composer, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1063...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
David Prévot  (supplier of updated composer package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 10 Feb 2024 11:18:19 +0100
Source: composer
Architecture: source
Version: 2.7.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: David Prévot 
Closes: 1061291 1063603
Changes:
 composer (2.7.1-1) unstable; urgency=medium
 .
   [ Jordi Boggiano ]
   * Merge pull request from GHSA-7c6p-848j-wh5h [CVE-2024-24821]
 (Closes: #1063603)
   * Release 2.7.1
 .
   [ David Prévot ]
   * Extend recommended packages list (Closes: #1061291)
Checksums-Sha1:
 2bb260346e20febbb761adf104fbe8bad497b8c7 2319 composer_2.7.1-1.dsc
 2ca791fcbda58871f8c3f2067c5aff50a99f 656568 composer_2.7.1.orig.tar.xz
 900c8ce598b05a97079154f7b074f72429917a75 14828 composer_2.7.1-1.debian.tar.xz
 2a086c71a8aee3b24e6fe14d40f9d1e52980dcd4 9780 composer_2.7.1-1_amd64.buildinfo
Checksums-Sha256:
 23efd15fbe114f027d680cd033414d8457828e65b01d369a8d73aa46489493a9 2319 
composer_2.7.1-1.dsc
 f5b6f31279976d5f7a7a94549919fdeb5ae93441f301106c2e00863a554401f3 656568 
composer_2.7.1.orig.tar.xz
 823b8a26ffcc9ce8e3d93eae611e1843ad0529280e50d53d0b526b76a29fb4f9 1

Bug#1063434: marked as done (src:389-ds-base: fails to migrate to testing for too long: FTBFS on 32 bits)

[Debian Bug Tracking System]

Your message dated Sat, 10 Feb 2024 13:10:16 +
with message-id 
and subject line Bug#1063434: fixed in 389-ds-base 2.4.4+dfsg1-3
has caused the Debian Bug report #1063434,
regarding src:389-ds-base: fails to migrate to testing for too long: FTBFS on 
32 bits
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1063434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063434
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: 389-ds-base
Version: 2.3.4+dfsg1-1.1
Severity: serious
Control: close -1 2.4.4+dfsg1-1
Tags: sid trixie ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:389-ds-base has been trying to migrate for 
31 days [2]. Hence, I am filing this bug. The version in unstable failed 
to build on armel, armhf and i386 (our 32 bit architectures).


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=389-ds-base



OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: 389-ds-base
Source-Version: 2.4.4+dfsg1-3
Done: Timo Aaltonen 

We believe that the bug you reported is fixed in the latest version of
389-ds-base, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1063...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated 389-ds-base package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 10 Feb 2024 11:04:23 +0200
Source: 389-ds-base
Built-For-Profiles: noudeb
Architecture: source
Version: 2.4.4+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian FreeIPA Team 
Changed-By: Timo Aaltonen 
Closes: 1063434
Changes:
 389-ds-base (2.4.4+dfsg1-3) unstable; urgency=medium
 .
   * rules: Fix build on 32bit. Thanks, Chris Peterson! (Closes:
 #1063434)
Checksums-Sha1:
 ff4a6c839940f8f73a81f1e5944e912c68fe1399 3160 389-ds-base_2.4.4+dfsg1-3.dsc
 90861998c2f290e03a13873ae922d38b849a7ea3 803204 
389-ds-base_2.4.4+dfsg1-3.debian.tar.xz
 3dde58322abdf0bbc7cd5d3e14af9bf926bfb7b7 9602 
389-ds-base_2.4.4+dfsg1-3_source.buildinfo
Checksums-Sha256:
 77170acaa8bde0f61a3d143f853dd9d27dfbfb7dd53ad723526f763da6be74ec 3160 
389-ds-base_2.4.4+dfsg1-3.dsc
 e24eb278bf5bacff4928277a02ade6c6420b2e0c4633a0c8a8d94210aa5e5e57 803204 
389-ds-base_2.4.4+dfsg1-3.debian.tar.xz
 01ee02f6fa5f91a18febcfb3c75e69c4fdc9afabc15bdebecd26510bc576a3c2 9602 
389-ds-base_2.4.4+dfsg1-3_source.buildinfo
Files:
 55b48424458f88b77e220f4eb0c46f10 3160 net optional 
389-ds-base_2.4.4+dfsg1-3.dsc
 8769c5b3c4c6f5f4c3b94eb4c5030e99 803204 net optional 
389-ds-base_2.4.4+dfsg1-3.debian.tar.xz
 de81307b89cd17057b0755b6f44caa41 9602 net optional 
389-ds-base_2.4.4+dfsg1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmXHPCMACgkQy3AxZaiJ
hNxr9BAAkMOD79euiWu15qcP5z6K4Lhl1At+Jz7JSeSygF/nS096RXcBeZQqzh8j
e8oi8rX46pJVZ

Bug#1042590: marked as done (django-session-security: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx')

[Debian Bug Tracking System]

Your message dated Sat, 10 Feb 2024 13:11:32 +
with message-id 
and subject line Bug#1042590: fixed in django-session-security 2.6.7+dfsg-1
has caused the Debian Bug report #1042590,
regarding django-session-security: FTBFS with Sphinx 7.1, docutils 0.20: error: 
invalid command 'build_sphinx'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1042590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042590
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-session-security
Version: 2.6.6+dfsg-2
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx7.1

Hi,

django-session-security fails to build with Sphinx 7.1 and docutils 0.20, both 
of which
are currently available in experimental.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11/build/session_security
> copying session_security/views.py -> 
> /<>/.pybuild/cpython3_3.11/build/session_security
> copying session_security/utils.py -> 
> /<>/.pybuild/cpython3_3.11/build/session_security
> copying session_security/middleware.py -> 
> /<>/.pybuild/cpython3_3.11/build/session_security
> copying session_security/__init__.py -> 
> /<>/.pybuild/cpython3_3.11/build/session_security
> copying session_security/urls.py -> 
> /<>/.pybuild/cpython3_3.11/build/session_security
> copying session_security/models.py -> 
> /<>/.pybuild/cpython3_3.11/build/session_security
> copying session_security/settings.py -> 
> /<>/.pybuild/cpython3_3.11/build/session_security
> creating /<>/.pybuild/cpython3_3.11/build/session_security/tests
> copying session_security/tests/test_base.py -> 
> /<>/.pybuild/cpython3_3.11/build/session_security/tests
> copying session_security/tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.11/build/session_security/tests
> copying session_security/tests/test_views.py -> 
> /<>/.pybuild/cpython3_3.11/build/session_security/tests
> copying session_security/tests/test_middleware.py -> 
> /<>/.pybuild/cpython3_3.11/build/session_security/tests
> copying session_security/tests/test_script.py -> 
> /<>/.pybuild/cpython3_3.11/build/session_security/tests
> creating 
> /<>/.pybuild/cpython3_3.11/build/session_security/templatetags
> copying session_security/templatetags/__init__.py -> 
> /<>/.pybuild/cpython3_3.11/build/session_security/templatetags
> copying session_security/templatetags/session_security_tags.py -> 
> /<>/.pybuild/cpython3_3.11/build/session_security/templatetags
> creating 
> /<>/.pybuild/cpython3_3.11/build/session_security/tests/project
> copying session_security/tests/project/__init__.py -> 
> /<>/.pybuild/cpython3_3.11/build/session_security/tests/project
> copying session_security/tests/project/urls.py -> 
> /<>/.pybuild/cpython3_3.11/build/session_security/tests/project
> copying session_security/tests/project/settings.py -> 
> /<>/.pybuild/cpython3_3.11/build/session_security/tests/project
> copying session_security/tests/project/wsgi.py -> 
> /<>/.pybuild/cpython3_3.11/build/session_security/tests/project
> running egg_info
> creating django_session_security.egg-info
> writing django_session_security.egg-info/PKG-INFO
> writing dependency_links to 
> django_session_security.egg-info/dependency_links.txt
> writing requirements to django_session_security.egg-info/requires.txt
> writing top-level names to django_session_security.egg-info/top_level.txt
> writing manifest file 'django_session_security.egg-info/SOURCES.txt'
> reading manifest file 'django_session_security.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching '*.txt'
> warning: no files found matching 'README'
> warning: no files found matching '*.mo' under directory 'session_security'
> adding license file 'LICENSE'
> adding license file 'AUTHORS'
> writing manifest file 'django_session_security.egg-info/SOURCES.txt'
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: 
> Package 'session_security.locale.cs.LC_MESSAGES' is absent from the 
> `packages` configuration.
> !!
> 
> 
> 
> 
> # Package would be ignored #
> 
> Python recognizes 'session_security.locale.cs.LC_MESSAGES' as an 
> importable package[^1],
> but it is absent from setuptools' `packages` configuration.
> 
> This

Bug#1063640: adwaita-icon-theme: cursor theme not found

[Jeremy Bícha]

Control: reassign -1 src:mutter 44.8-2

I found some mutter commits to fix this issue and am uploading now.

Thank you,
Jeremy Bícha

Processed: Bug#1063640 marked as pending in mutter

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1063640 [src:mutter] adwaita-icon-theme: cursor theme not found
Ignoring request to alter tags of bug #1063640 to the same tags previously set

-- 
1063640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063640
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1063640: marked as pending in mutter

[Jeremy Bicha]

Control: tag -1 pending

Hello,

Bug #1063640 in mutter reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/gnome-team/mutter/-/commit/56258609f901a8a6609a283f2b5b8fb8c40e3a78


Cherry-pick several cursor fix to fix compatibility with latest 
adwaita-icon-theme

Closes: #1063640


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1063640

Processed: Bug#1063640 marked as pending in mutter

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1063640 [src:mutter] adwaita-icon-theme: cursor theme not found
Added tag(s) pending.

-- 
1063640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063640
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1063640: marked as pending in mutter

[Jeremy Bicha]

Control: tag -1 pending

Hello,

Bug #1063640 in mutter reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/gnome-team/mutter/-/commit/38fb8f145592d437915b2b62bfed0b26f23ca646


Cherry-pick several cursor fix to fix compatibility with latest 
adwaita-icon-theme

Closes: #1063640


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1063640

Processed: Re: Bug#1063640: adwaita-icon-theme: cursor theme not found

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:mutter 44.8-2
Bug #1063640 [adwaita-icon-theme] adwaita-icon-theme: cursor theme not found
Bug reassigned from package 'adwaita-icon-theme' to 'src:mutter'.
No longer marked as found in versions adwaita-icon-theme/46~beta-1.
Ignoring request to alter fixed versions of bug #1063640 to the same values 
previously set
Bug #1063640 [src:mutter] adwaita-icon-theme: cursor theme not found
Marked as found in versions mutter/44.8-2.

-- 
1063640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063640
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1063401: atm-tools: has gained /usr/share/doc/libatm1/changelog.*

[Andreas Metzler]

Control: tags -1 patch

On 2024-02-07 Andreas Beckmann  wrote:
> Package: atm-tools
> Version: 1:2.5.1-5.1~exp1
[...]
> atm-tools/experimental has gained two unexpected files, causing file
> conflicts on upgrades:
[...]
> There is still an libatm1 dependency, and the new libatm1t64 dependency
> seems to miss the epoch.

Hello,

Both issues are fixed by a one-line-change, a dh_lintian call should
also be added.

diff -Nru linux-atm-2.5.1/debian/rules linux-atm-2.5.1/debian/rules
--- linux-atm-2.5.1/debian/rules2019-07-19 11:14:25.0 +0200
+++ linux-atm-2.5.1/debian/rules2024-02-10 13:31:02.0 +0100
@@ -72,7 +72,7 @@
dh_testroot
dh_install --sourcedir=debian/tmp
rm debian/atm-tools/usr/share/man/man8/br2684ctl.8
-   dh_installdocs --link-doc=libatm1
+   dh_installdocs --link-doc=libatm1t64
dh_installinit --init-script=atm
dh_installsystemd --name=atm
dh_installman
@@ -80,6 +80,7 @@
dh_link
dh_strip
dh_compress
+   dh_lintian
dh_fixperms
dh_makeshlibs -- -c4
dh_installdeb

cu Andreas

Processed: Re: atm-tools: has gained /usr/share/doc/libatm1/changelog.*

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1063401 [atm-tools] atm-tools: has gained 
/usr/share/doc/libatm1/changelog.*
Added tag(s) patch.

-- 
1063401: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063401
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1063640: adwaita-icon-theme: cursor theme not found

[Jeremy Bícha]

Control: affects -1 src:mutter src:gnome-shell

On Sat, Feb 10, 2024 at 5:51 AM Frederic Peters  wrote:
> After upgrading to 46~beta-1 gnome-shell doesn't find a cursor theme
> anymore, I get this line in the journalctl output:
>
>   feb 10 11:02:08 stab gnome-shell[999044]: No cursor theme available, please 
> install a cursor theme
>
> On X it then fallbacks to a default cursor theme, on Wayland it just
> uses a white square as cursor.

I believe this is fixed once we update to GNOME Shell 45. I see
references in the mutter 45 commit log to switching from hardware to
software cursors in that release. If that is what we need, then I
don't think it is reasonable to try to cherry-pick those changes to
44.

But maybe a more minimal fix can be found.

GNOME Shell 45 is blocked because we have been unable to get Magpie
into Debian which would break the Budgie Desktop. See
https://bugs.debian.org/1050237

I have increased the severity of this bug to serious and am leaving it
assigned to adwaita-icon-theme to warn people of the problem upgrading
to this version. Fortunately, adwaita-icon-theme is easy to downgrade
since it's just a single package without tight dependencies on other
things.

Thank you,
Jeremy Bicha

Processed: Re: Bug#1063640: adwaita-icon-theme: cursor theme not found

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:mutter src:gnome-shell
Bug #1063640 [adwaita-icon-theme] adwaita-icon-theme: cursor theme not found
Added indication that 1063640 affects src:mutter and src:gnome-shell

-- 
1063640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063640
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1063648: krb5: FTBFS on arm64, armel and ppc64el with "Can't resolve hostname" in dh_auto_test

[Johannes Schauer Marin Rodrigues]

Source: krb5
Version: 1.20.1-5+b1
Severity: serious
Tags: ftbfs

Hi,

there as a binNMU "Rebuild to sync binNMU versions" for krb5 and that
failed for arm64, armel and ppc64el:

https://buildd.debian.org/status/package.php?p=krb5

The error logs look very similar:

making check in lib/rpc...
make[4]: Entering directory '/<>/build/lib/rpc'
making check in lib/rpc/unit-test...
make[5]: Entering directory '/<>/build/lib/rpc/unit-test'
PYTHONPATH=../../../../src/util VALGRIND="" python3 
../../../../src/lib/rpc/unit-test/t_rpc.py 
*** Failure: ./client failed with code 1.
*** Last command (#10): ./client -t arm-conova-03 58621 host@arm-conova-03 1026
*** Output of last command:
Can't resolve hostname arm-conova-03
For details, see: /<>/build/lib/rpc/unit-test/testlog
Or re-run this test script with the -v flag:
cd /<>/build/lib/rpc/unit-test
PYTHONPATH=/<>/src/util /usr/bin/python3 
../../../../src/lib/rpc/unit-test/t_rpc.py -v

Use --debug=NUM to run a command under a debugger.  Use
--stop-after=NUM to stop after a daemon is started in order to
attach to it with a debugger.  Use --help to see other
options.
make[5]: *** [Makefile:644: check-pytests] Error 1
make[5]: Leaving directory '/<>/build/lib/rpc/unit-test'
make[4]: *** [Makefile:1595: check-recurse] Error 1
make[4]: Leaving directory '/<>/build/lib/rpc'
make[3]: *** [Makefile:973: check-recurse] Error 1
make[3]: Leaving directory '/<>/build/lib'
make[2]: *** [Makefile:1521: check-recurse] Error 1
make[2]: Leaving directory '/<>/build'
dh_auto_test: error: cd build && make -j1 check "TESTSUITEFLAGS=-j1 --verbose" 
VERBOSE=1 returned exit code 2
make[1]: *** [debian/rules:150: override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:153: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


Thanks!

cheers, josch

Bug#1063646: tix: missing required debian/rules targets build-arch and/or build-indep

[Guillem Jover]

Source: tix
Version: 8.4.3-11
Severity: serious
Justification: Debian Policy section 4.9
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep

Dear maintainer,

Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules

Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.

This mass bug filing was discussed on debian-devel@ in
.
(The severity of this bug at the time of the mass bug filing was set to
'important', and bumped to 'serious' after a month, but given that quite
some time has passed, I'm just setting it directly to 'serious' now, as
I'm planning to remove the fallback workaround for these targets in the
next dpkg upload.)

Thanks,
Guillem

Bug#1063647: sysconfig: missing required debian/rules targets build-arch and/or build-indep

[Guillem Jover]

Source: sysconfig
Version: 0.0.14
Severity: serious
Justification: Debian Policy section 4.9
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep

Dear maintainer,

Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules

Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.

This mass bug filing was discussed on debian-devel@ in
.
(The severity of this bug at the time of the mass bug filing was set to
'important', and bumped to 'serious' after a month, but given that quite
some time has passed, I'm just setting it directly to 'serious' now, as
I'm planning to remove the fallback workaround for these targets in the
next dpkg upload.)

Thanks,
Guillem

Bug#1063644: atitvout: missing required debian/rules targets build-arch and/or build-indep

[Guillem Jover]

Source: atitvout
Version: 0.4-13.2
Severity: serious
Justification: Debian Policy section 4.9
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep

Dear maintainer,

Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules

Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.

This mass bug filing was discussed on debian-devel@ in
.
(The severity of this bug at the time of the mass bug filing was set to
'important', and bumped to 'serious' after a month, but given that quite
some time has passed, I'm just setting it directly to 'serious' now, as
I'm planning to remove the fallback workaround for these targets in the
next dpkg upload.)

Thanks,
Guillem

Bug#1063645: markdown: missing required debian/rules targets build-arch and/or build-indep

[Guillem Jover]

Source: markdown
Version: 1.0.1-12
Severity: serious
Justification: Debian Policy section 4.9
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep

Dear maintainer,

Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules

Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.

This mass bug filing was discussed on debian-devel@ in
.
(The severity of this bug at the time of the mass bug filing was set to
'important', and bumped to 'serious' after a month, but given that quite
some time has passed, I'm just setting it directly to 'serious' now, as
I'm planning to remove the fallback workaround for these targets in the
next dpkg upload.)

Thanks,
Guillem

Processed: Re: Bug#1063640: adwaita-icon-theme: cursor theme not found

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1063640 serious
Bug #1063640 [adwaita-icon-theme] adwaita-icon-theme: cursor theme not found
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1063640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063640
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 1061888 is important, severity of 1061920 is important, severity of 1062060 is important ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1061888 important
Bug #1061888 [src:anfo] anfo: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> severity 1061920 important
Bug #1061920 [src:arrayfire] arrayfire: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> severity 1062060 important
Bug #1062060 [src:cinnamon-desktop] cinnamon-desktop: NMU diff for 64-bit 
time_t transition
Severity set to 'important' from 'serious'
> severity 1062066 important
Bug #1062066 [src:gegl] gegl: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> severity 1062095 important
Bug #1062095 [src:colord-gtk] colord-gtk: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> severity 1062125 important
Bug #1062125 [src:gimp] gimp: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> severity 1062127 important
Bug #1062127 [src:glade] glade: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> severity 1062134 important
Bug #1062134 [src:glib2.0] glib2.0: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> severity 1062135 important
Bug #1062135 [src:glibmm2.4] glibmm2.4: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> severity 1062137 important
Bug #1062137 [src:glibmm2.68] glibmm2.68: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> severity 1062179 important
Bug #1062179 [src:gnome-bluetooth] gnome-bluetooth: NMU diff for 64-bit time_t 
transition
Severity set to 'important' from 'serious'
> severity 1062187 important
Bug #1062187 [src:gsound] gsound: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> severity 1062191 important
Bug #1062191 [src:gtkmm2.4] gtkmm2.4: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> severity 1062193 important
Bug #1062193 [src:gtkmm3.0] gtkmm3.0: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> severity 1062242 important
Bug #1062242 [src:libcanberra] libcanberra: NMU diff for 64-bit time_t 
transition
Severity set to 'important' from 'serious'
> severity 1062271 important
Bug #1062271 [src:libdmapsharing] libdmapsharing: NMU diff for 64-bit time_t 
transition
Severity set to 'important' from 'serious'
> severity 1062308 important
Bug #1062308 [src:libgda5] libgda5: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> severity 1062309 important
Bug #1062309 [src:libgdamm5.0] libgdamm5.0: NMU diff for 64-bit time_t 
transition
Severity set to 'important' from 'serious'
> severity 1062318 important
Bug #1062318 [src:libgom] libgom: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> severity 1062360 important
Bug #1062360 [src:libgweather4] libgweather4: NMU diff for 64-bit time_t 
transition
Severity set to 'important' from 'serious'
> severity 1062363 important
Bug #1062363 [src:libgxps] libgxps: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> severity 1062450 important
Bug #1062450 [src:gnome-desktop] gnome-desktop: NMU diff for 64-bit time_t 
transition
Severity set to 'important' from 'serious'
> severity 1062541 important
Bug #1062541 [src:evince] evince: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> severity 1062542 important
Bug #1062542 [src:evolution-data-server] evolution-data-server: NMU diff for 
64-bit time_t transition
Severity set to 'important' from 'serious'
> severity 1062633 important
Bug #1062633 [src:libsoup2.4] libsoup2.4: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> severity 1062954 important
Bug #1062954 [src:syndication] : NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> severity 1062956 important
Bug #1062956 [src:sysprof] sysprof: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> severity 1063053 important
Bug #1063053 [src:volume-key] volume-key: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> severity 1063077 important
Bug #1063077 [src:syslog-ng] syslog-ng: identified for time_t transition but no 
ABI in shlibs
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1061888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061888
1061920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061920
1062060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062060
1062066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062066
1062095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062095
1062125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062125
1062127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062127
1062134: https:/

Processed: igraph: FTBFS on i386: test::igraph_hrg (Failed)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 1063607 https://github.com/igraph/igraph/issues/2482
Bug #1063607 [src:igraph] igraph: FTBFS on i386: test::igraph_hrg (Failed)
Set Bug forwarded-to-address to 'https://github.com/igraph/igraph/issues/2482'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1063607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063607
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#988817: (no subject)

[Steven Maddox]

As I've come to understand it... since fwupd is in main and it 
recommends a package not in main, then it violates policy 2.2.1


Since this directive is a 'must' I've changed the severity to 'serious' 
as per the meanings of those severity levels.

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 988817 serious
Bug #988817 [fwupd] fwupd: Recommends on nonexistent package secureboot-db
Severity set to 'serious' from 'minor'
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
988817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988817
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: limit source to composer, tagging 1063603, tagging 1061291

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> limit source composer
Limiting to bugs with field 'source' containing at least one of 'composer'
Limit currently set to 'source':'composer'

> tags 1063603 + pending
Bug #1063603 [src:composer] composer: CVE-2024-24821
Added tag(s) pending.
> tags 1061291 + pending
Bug #1061291 [composer] composer: recommends missing: php-curl
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1061291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061291
1063603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063603
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 1062485 is important, severity of 1062742 is important, severity of 1062573 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1062485 important
Bug #1062485 [src:libnova] libnova: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> severity 1062742 important
Bug #1062742 [src:libzia] libzia: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> severity 1062573 important
Bug #1062573 [src:libpqxx] libpqxx: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1062485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062485
1062573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062573
1062742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062742
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 1062572 is normal

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1062572 normal
Bug #1062572 [src:libpqtypes] libpqtypes: NMU diff for 64-bit time_t transition
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1062572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062572
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 1062388 is normal

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1062388 normal
Bug #1062388 [src:dsdcc] dsdcc: NMU diff for 64-bit time_t transition
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1062388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062388
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1040375: /usr/lib/x86_64-linux-gnu/simplescreenrecorder/libssr-glinject.so: Segmentation fault when used with anything

[Petter Reinholdtsen]

[Petter Reinholdtsen]
> I do not use ssr much myself, and have not had time to test.

I applied the upstream commit in git branch fix-1040375-glinject and
tested it on Bookworm, but alas, the .so file still segfaults with a
useless backtrace.  I might have applied the commit incorrectly, as it
did not apply without changes, but hope not.  Perhaps someone
who understand what is happening can have a look?

-- 
Happy hacking
Petter Reinholdtsen

Processed: found 1062033 in 2.12.0+ds-2

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 1062033 2.12.0+ds-2
Bug #1062033 [src:c-blosc2] c-blosc2: NMU diff for 64-bit time_t transition
Marked as found in versions c-blosc2/2.12.0+ds-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1062033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062033
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1063637: virglrenderer: FTBFS on mips64el: test failures

[Sebastian Ramacher]

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

https://buildd.debian.org/status/fetch.php?pkg=virglrenderer&arch=mips64el&ver=1.0.0-1%2Bb1&stamp=1707553944&raw=0

--- stderr ---
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
==

Processed: python-pynndescent: test_distances fails with scipy 1.11: Unknown Distance Metric: kulsinski

[Debian Bug Tracking System]

Processing control commands:

> block 1061605 by -1
Bug #1061605 [src:scipy] scipy: tests skipped during build and autopkgtest not 
in sync
1061605 was blocked by: 1063527 1063526 1063584
1061605 was not blocking any bugs.
Added blocking bug(s) of 1061605: 1063636

-- 
1061605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061605
1063636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063636
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1040375: marked as pending in simplescreenrecorder

[Petter Reinholdtsen]

Control: tag -1 pending

Hello,

Bug #1040375 in simplescreenrecorder reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/multimedia-team/simplescreenrecorder/-/commit/d0fd87b48f684087934e32fd4ae20e3f39d59b81


Added -switch-to-PLT-hooks-for-glinject.patch to fix segfault in glinject.

Closes: #1040375


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1040375

Processed: Bug#1040375 marked as pending in simplescreenrecorder

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1040375 [simplescreenrecorder-lib] 
/usr/lib/x86_64-linux-gnu/simplescreenrecorder/libssr-glinject.so: Segmentation 
fault when used with anything
Added tag(s) pending.

-- 
1040375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040375
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems