date:20231031

Processed: Not a bug

2023-10-31 Thread Debian Bug Tracking System

Processing control commands:

> severity -1 wishlist
Bug #1054432 [src:node-katex] node-katex: website is build with Docusaurus not 
packaged for debian
Severity set to 'wishlist' from 'serious'

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

Bug#1054432: Not a bug

2023-10-31 Thread Yadd


Control: severity -1 wishlist

Files are readable

Bug#1055123: marked as done (efivar builds with -march=native on !ia64)

2023-10-31 Thread Debian Bug Tracking System

Your message dated Wed, 01 Nov 2023 01:04:31 +
with message-id 
and subject line Bug#1055123: fixed in efivar 38-2
has caused the Debian Bug report #1055123,
regarding efivar builds with -march=native on !ia64
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.)


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

https://buildd.debian.org/status/logs.php?pkg=efivar=38-1

-march=native is a baseline violation on architectures where
it is supported, and causes a FTBFS on architectures where
it is not supported.

It also changes the set of architectures where the package
might run based on the capabilities of the buildd, e.g. on amd64
code built on an AMD buildd might not run on Intel hardware and
code built on Intel hardware might not run on AMD hardware.
--- End Message ---
--- Begin Message ---
Source: efivar
Source-Version: 38-2
Done: Steve McIntyre <93...@debian.org>

We believe that the bug you reported is fixed in the latest version of
efivar, 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 1055...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Steve McIntyre <93...@debian.org> (supplier of updated efivar 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: Wed, 01 Nov 2023 00:39:42 +
Source: efivar
Architecture: source
Version: 38-2
Distribution: unstable
Urgency: medium
Maintainer: Debian UEFI Maintainers 
Changed-By: Steve McIntyre <93...@debian.org>
Closes: 1055123
Changes:
 efivar (38-2) unstable; urgency=medium
 .
   * Don't compile with -march=native. Closes: #1055123
Checksums-Sha1:
 1d1bfb77e449377a20c2ede90a24ffef54c872bc 2785 efivar_38-2.dsc
 d3cc6cffa519826adce907b1dc184fffbed486a0 8756 efivar_38-2.debian.tar.xz
 6787852f1e30ad07cd5918cea22b66339dc39a96 6571 efivar_38-2_source.buildinfo
Checksums-Sha256:
 c051eb18909492e88fd55f1d5ee30ab00b4b8e64859506f2f0a2e479e7dcc7bb 2785 
efivar_38-2.dsc
 69b11e2f9501a8403d0631820d223c2d1334ea085088a8c3cda1d0ccd75d6bac 8756 
efivar_38-2.debian.tar.xz
 cb659a98753006e94a5b0dba570197cd9eba26bdef46d5c44d7571118a1ab163 6571 
efivar_38-2_source.buildinfo
Files:
 d0672167e62455ace1a2dfb85a928c03 2785 libs optional efivar_38-2.dsc
 6b981f40d6aae452742fc0cc2fdbb4ae 8756 libs optional efivar_38-2.debian.tar.xz
 3b935734a0d985e8294f296c74db7e7d 6571 libs optional 
efivar_38-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEEzrtSMB1hfpEDkP4WWHl5VzRCaE4FAmVBoDMRHDkzc2FtQGRl
Ymlhbi5vcmcACgkQWHl5VzRCaE6mZRAApft1t8B7oocJ6vSYzFppdJlOsTjKbfF8
2CV9u9xXcJH0K1ZDt7yoo/L2FjKXXFGv8ZveK7a4o3WKAchbkwmv01rtEdLaZog6
hMk2ESEAQucf8cDy7TPkviqZRBNSK9dsC2wrDrts5G999CmRQaPceYJ2iPAcXh/8
7NYKdhWRONiSxgBeJIGwwrmHCJqjw5ivHLRwv9BHJCl4aXgxlm2MF8J/BXn3xwuj
zKbrX4ADilM0pzIVnSCaIvEtigyH2e3XpIFQKSE9gHy8uyn0Z0JgTAUIeJY4goL2
0mVgRy0Y7Mxhwtfz8y1QrVzWfnFHGnTvlg64RBeZKz2QCBwsZcdlaphot3mxAnl6
KinhkKXz/6ZtHAThhIg/PeDkU7bEyELnKyPdXUNvvQufUmOBOAI1FpRfrAmqGBp9
2no+LkLMs//aAQRVSQ2RhNcUPGsNGTGAZFK2RdXQOT/G3FHoaxSyaKq1qiJZkT6l
Kkzujz6Fy8HPjEgfwJtPXmpHftuMTOcjzcCPhKsCZ/eOhGUj5FrZWNoeD9bmzT6U
IQv5PtmZ82cr/aEDrkPHSVr/n0TS1axW7VsLiAYr6NT/5yD55IBCJsOq5pUVQJAh
De1Nvt4A7ab/+OLQaeIb6eVyhl7JNoMuYgQsO2L/O2yAFTFDBUEVEGP7xWI9siUc
+p/Vnx9D9jM=
=R7Lw
-END PGP SIGNATURE End Message ---

Processed: bug due to missing dependency golang-golang-x-net-dev

2023-10-31 Thread Debian Bug Tracking System

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

> reassign 1054846 golang-github-gin-gonic-gin 1.8.1-1
Bug #1054846 [src:golang-github-gin-contrib-static] 
golang-github-gin-contrib-static: FTBFS: make: *** [debian/rules:4: build] 
Error 25
Bug reassigned from package 'src:golang-github-gin-contrib-static' to 
'golang-github-gin-gonic-gin'.
No longer marked as found in versions 
golang-github-gin-contrib-static/0.0~git20220829.3035101-1.
Ignoring request to alter fixed versions of bug #1054846 to the same values 
previously set
Bug #1054846 [golang-github-gin-gonic-gin] golang-github-gin-contrib-static: 
FTBFS: make: *** [debian/rules:4: build] Error 25
There is no source info for the package 'golang-github-gin-gonic-gin' at 
version '1.8.1-1' with architecture ''
Unable to make a source version for version '1.8.1-1'
Marked as found in versions 1.8.1-1.
> fixed 1054846 1.8.1-2
Bug #1054846 [golang-github-gin-gonic-gin] golang-github-gin-contrib-static: 
FTBFS: make: *** [debian/rules:4: build] Error 25
There is no source info for the package 'golang-github-gin-gonic-gin' at 
version '1.8.1-2' with architecture ''
Unable to make a source version for version '1.8.1-2'
Marked as fixed in versions 1.8.1-2.
> affects 1054846 golang-github-gin-contrib-static
Bug #1054846 [golang-github-gin-gonic-gin] golang-github-gin-contrib-static: 
FTBFS: make: *** [debian/rules:4: build] Error 25
Added indication that 1054846 affects golang-github-gin-contrib-static
> stop
Stopping processing here.

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

Bug#1055111: marked as done (ffmpeg FTBFS: makeinfo: Undefined subroutine ::Config::set_from_init_file called at doc/t2h.pm)

2023-10-31 Thread Debian Bug Tracking System

Your message dated Tue, 31 Oct 2023 23:20:52 +
with message-id 
and subject line Bug#1055111: fixed in ffmpeg 7:6.0-9
has caused the Debian Bug report #1055111,
regarding ffmpeg FTBFS: makeinfo: Undefined subroutine 
::Config::set_from_init_file called at doc/t2h.pm
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.)


-- 
1055111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055111
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ffmpeg
Version: 7:6.0-8
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Debian TeX Task Force 

https://buildd.debian.org/status/logs.php?pkg=ffmpeg=7%3A6.0-8

...
makeinfo --html -I doc --no-split -D config-not-all 
--init-file=/<>/doc/t2h.pm --output doc/ffmpeg.html 
/<>/doc/ffmpeg.texi
makeinfo: error parsing /<>/doc/t2h.pm: Undefined subroutine 
::Config::set_from_init_file called at /<>/doc/t2h.pm line 
24.
make[2]: *** [/<>/doc/Makefile:70: doc/ffmpeg.html] Error 1
--- End Message ---
--- Begin Message ---
Source: ffmpeg
Source-Version: 7:6.0-9
Done: Sebastian Ramacher 

We believe that the bug you reported is fixed in the latest version of
ffmpeg, 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 1055...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated ffmpeg 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: Wed, 01 Nov 2023 00:06:10 +0100
Source: ffmpeg
Architecture: source
Version: 7:6.0-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Sebastian Ramacher 
Closes: 1055111
Changes:
 ffmpeg (7:6.0-9) unstable; urgency=medium
 .
   * debian/patches: Workaround build issues with texinfo 7.1 (Closes:
 #1055111)
Checksums-Sha1:
 5ab09e46ac7be4a2b56e7195115993581eb250b9 5097 ffmpeg_6.0-9.dsc
 fbfc3308e2677531042e3a445eb41010b9a7ecb6 56956 ffmpeg_6.0-9.debian.tar.xz
Checksums-Sha256:
 09899e99fc6097e5246c1406b1ac4e68b95f2559e529341c894b52ae071a097c 5097 
ffmpeg_6.0-9.dsc
 4b63422956a41556548e97369760997684d05affe8176f23f1436b6c5d973d11 56956 
ffmpeg_6.0-9.debian.tar.xz
Files:
 45f1435478506a85b10840133747aa6c 5097 video optional ffmpeg_6.0-9.dsc
 15e1dd4fab8469ab93718ec8b2253199 56956 video optional 
ffmpeg_6.0-9.debian.tar.xz

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZUGKhwAKCRAhk2s2YA/N
iQL7AP9cuwVt0mEZpT3357Z5BTZvcVE9ZnEfo3ZoMenK+g/JcAD/W39EV5/BD0P/
HEe518sbVYeCarmmUXa6e9wPaMd6Vgo=
=IQTa
-END PGP SIGNATURE End Message ---

Bug#1055111: marked as pending in ffmpeg

2023-10-31 Thread Sebastian Ramacher

Control: tag -1 pending

Hello,

Bug #1055111 in ffmpeg 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/ffmpeg/-/commit/5a5de39526bd8ff5f3881cc611968062e076d9fe


Workaround build issues with texinfo 7.1

Closes: #1055111


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1055111

Processed: Bug#1055111 marked as pending in ffmpeg

2023-10-31 Thread Debian Bug Tracking System

Processing control commands:

> tag -1 pending
Bug #1055111 [src:ffmpeg] ffmpeg FTBFS: makeinfo: Undefined subroutine 
::Config::set_from_init_file called at doc/t2h.pm
Added tag(s) pending.

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

Bug#1055111: ffmpeg FTBFS: makeinfo: Undefined subroutine ::Config::set_from_init_file called at doc/t2h.pm

2023-10-31 Thread Sebastian Ramacher

Hi Hilmar

On 2023-10-31 23:15:03 +0100, Hilmar Preuße wrote:
> > https://buildd.debian.org/status/logs.php?pkg=ffmpeg=7%3A6.0-8
> > 
> > ...
> > makeinfo --html -I doc --no-split -D config-not-all 
> > --init-file=/<>/doc/t2h.pm --output doc/ffmpeg.html 
> > /<>/doc/ffmpeg.texi
> > makeinfo: error parsing /<>/doc/t2h.pm: Undefined subroutine 
> > ::Config::set_from_init_file called at /<>/doc/t2h.pm 
> > line 24.
> > make[2]: *** [/<>/doc/Makefile:70: doc/ffmpeg.html] Error 1
> > 
> Could it be caused the upload of TeXinfo 7.1, did it work with TeXinfo from
> testing? I don't see any change for this in the
> /usr/share/doc/texinfo/NEWS.gz .

It is caused by texinfo 7.1, yes. Builds with texinfo from testing work
fine.

Cheers
-- 
Sebastian Ramacher

Bug#1054253: marked as done (icu FTBFS with gcc 13 on i386)

2023-10-31 Thread Debian Bug Tracking System

Your message dated Tue, 31 Oct 2023 22:52:47 +
with message-id 
and subject line Bug#1054253: fixed in icu 74.1-1
has caused the Debian Bug report #1054253,
regarding icu FTBFS with gcc 13 on i386
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.)


-- 
1054253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054253
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: icu
Version: 72.1-3
Severity: serious
Tags: ftbfs patch trixie sid experimental

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/icu.html

...
-
| *** FAILING TEST SUMMARY FOR:  intltest  
 TestFixedDecimal
  IntlTestDecimalFormatAPI
 TestCurrencyFormatForMixParsing
  NumberFormatTest
 Test4118594
  MessageFormatRegressionTest
 Test4243108
  NumberFormatRegressionTest
roundingIncrementRegressionTest
 NumberFormatterApiTest
  NumberTest
   format
| *** END FAILING TEST SUMMARY FOR:  intltest
---
ALL TESTS SUMMARY:
ok:  testdata iotest cintltst
= ERRS:  intltest
make[3]: *** [Makefile:91: check-recursive] Error 1
...


Fix:

--- debian/rules.old2023-10-19 19:46:14.664980859 +
+++ debian/rules2023-10-19 19:46:34.536970355 +
@@ -16,6 +16,8 @@
 export DEB_CPPFLAGS_MAINT_APPEND = 
-DU_TIMEZONE_FILES_DIR=/usr/share/zoneinfo-icu/44/be/
 endif
 
+export DEB_CXXFLAGS_MAINT_APPEND += -fexcess-precision=fast
+
 include /usr/share/dpkg/buildflags.mk
 
 l_SONAME=70
--- End Message ---
--- Begin Message ---
Source: icu
Source-Version: 74.1-1
Done: Laszlo Boszormenyi (GCS) 

We believe that the bug you reported is fixed in the latest version of
icu, 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 1054...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated icu 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: Tue, 31 Oct 2023 22:07:13 +0100
Source: icu
Architecture: source
Version: 74.1-1
Distribution: experimental
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 1039624 1054253
Changes:
 icu (74.1-1) experimental; urgency=medium
 .
   * New major upstream release.
   * Building with Clang causes more problems, switch back to GCC.
 .
   [ Adrian Bunk  ]
   * Fix FTBFS with GCC 13 on i386 (closes: #1054253).
 .
   [ Vagrant Cascadian  ]
   * Make builds reproducible (closes: #1039624):
 - debian/rules: Remove build paths from .inc and .tag files,
 - debian/rules: Consistently use /bin/sh SHELL in .inc files.
Checksums-Sha1:
 517e245d5d2c166115aced393119f34b48573be9 2246 icu_74.1-1.dsc
 fc401757c2cddd993eb4524dc2462a4277126fb4 26625850 icu_74.1.orig.tar.gz
 0f384710717cfb5ca2254d18b3a22209b7908e91 659 icu_74.1.orig.tar.gz.asc
 4bb61124a57221f945ba6a1888b89f03cbad 62140 icu_74.1-1.debian.tar.xz
Checksums-Sha256:
 edac9f7d685c4913e282134aa8daac4cfebcc962bf1bbda94712203fa02c58ef 2246 
icu_74.1-1.dsc
 86ce8e60681972e60e4dcb2490c697463fcec60dd400a5f9bffba26d0b52b8d0 26625850 
icu_74.1.orig.tar.gz
 6745e2e9592182ab3494acf09848b1c50b50c912670c35260f46ef037a97a4ba 659 
icu_74.1.orig.tar.gz.asc
 62860b011f6c0dc591432eeecf236aac84eced5163391c7c87e002fd886edb04 62140 
icu_74.1-1.debian.tar.xz
Files:
 218227ef2383b56780c324a17176f235 2246 libs optional icu_74.1-1.dsc
 71e60b22697c4f35820a1897417dbab4 26625850 libs optional icu_74.1.orig.tar.gz
 42d2756503455d3641d5ec8125215539 659 libs optional icu_74.1.orig.tar.gz.asc
 1f80109de4334362d743ccdf8ba7a810 62140 libs optional icu_74.1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAmVBeIcACgkQ3OMQ54ZM
yL9fnw/+J0ubLJvZn4pWcWFDt5JS1+YY3sSQ6VW7eXZJx/3Wrup7W/LhOq9x/IYS
jQMdvG31LcKocxFtFrEALG7i1iGyWI3HSkoR1eB7ydfJU/ra3tVmMLjxZ3Tx8sxq
YOD6ZDPf+5wKT2KLuiCZKVkXkH7hSpSPadtsKLdUEnWgYfDCCE9YbpzIZmDt3UHT
xwKm6w6r+I19uagZ7FmpVPrOOXgr4f27BtDRCvHpyfhYbEQPYcPU4/rKkzluZxWA
XJM9mBPMhokz43ag8qucPKwkb9xfqcfMl/2NjrtLIdRVqL4+iYdSDj/JiJEAdGa9
tjyJJca0TERCAS2hxtXDX10dAA/8mCerUA4tshHMtaUo+IYekkcekZVpJGsfShzl

Bug#1025572: marked as done (hannah-foo2zjs: dependency on transitional policykit-1 package)

2023-10-31 Thread Debian Bug Tracking System

Your message dated Tue, 31 Oct 2023 22:52:19 +
with message-id 
and subject line Bug#1025572: fixed in hannah-foo2zjs 1:6
has caused the Debian Bug report #1025572,
regarding hannah-foo2zjs: dependency on transitional policykit-1 package
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.)


-- 
1025572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025572
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hannah-foo2zjs
Version: 1:4
Severity: normal
User: pkg-utopia-maintain...@lists.alioth.debian.org
Usertags: policykit-1
Control: block 1025540 by -1

This package has a Depends and/or Build-Depends on the transitional
package policykit-1, which has been separated into polkitd, pkexec and
(deprecated) polkitd-pkla packages.

If this package communicates with polkitd via D-Bus, please represent that
as a Depends, Recommends or Suggests on polkitd, whichever is appropriate
for the strength of the requirement.

If this package runs /usr/bin/pkexec, please represent that as a Depends,
Recommends or Suggests on pkexec, whichever is appropriate for the strength
of the requirement.

If this package requires polkit at build-time (usually for the gettext
extensions polkit.its and polkit.loc), please build-depend on both
libpolkit-gobject-1-dev and polkitd, even if the package does not
actually depend on libpolkit-gobject-1 at runtime. This is because
the gettext extensions are currently in polkitd, but might be moved to
libpolkit-gobject-1-dev in future (see #955204). pkexec is usually not
required at build-time.

For packages that are expected to be backported to bullseye, it's OK to
use an alternative dependency: polkitd | policykit-1 and/or
pkexec | policykit-1.

This is part of a mass bug filing, see
.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: hannah-foo2zjs
Source-Version: 1:6
Done: Thorsten Alteholz 

We believe that the bug you reported is fixed in the latest version of
hannah-foo2zjs, 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 1025...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated hannah-foo2zjs 
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: Tue, 31 Oct 2023 23:03:02 +0100
Source: hannah-foo2zjs
Architecture: source
Version: 1:6
Distribution: unstable
Urgency: medium
Maintainer: Debian Printing Team 
Changed-By: Thorsten Alteholz 
Closes: 1025572
Changes:
 hannah-foo2zjs (1:6) unstable; urgency=medium
 .
   * debian/control: replace dependency on policykit-1 by pkexec
 (Closes: #1025572)
Checksums-Sha1:
 03b637aa7a3f183fa5965d776869752d06f7643e 1813 hannah-foo2zjs_6.dsc
 b95c9d36ffde366c4d94a5f7dfb57cfd6f11caa8 5772 hannah-foo2zjs_6.tar.xz
 1f330bc38d6bb3d586fc6cf98e53556459a089cc 10527 hannah-foo2zjs_6_amd64.buildinfo
Checksums-Sha256:
 f24c507d530862b823ef2f76b4955427f42c91f2e6ca98bc3112ceee9c540ce3 1813 
hannah-foo2zjs_6.dsc
 f99975797e2679772bde116abbcf5af9a678bf1d930ac06548a77cbbc1bc9051 5772 
hannah-foo2zjs_6.tar.xz
 72de4ead111dd83256e97d7f89052406819eaa502593a7db702ddbcf60c51a0a 10527 
hannah-foo2zjs_6_amd64.buildinfo
Files:
 d1e5bcadc7b00980033b3dce7443b73e 1813 contrib/text optional 
hannah-foo2zjs_6.dsc
 156107b4bbbe40c0c31fb8d34bb98e91 5772 contrib/text optional 
hannah-foo2zjs_6.tar.xz
 1c67ac420c4ae110129b1dd68c559531 10527 contrib/text optional 
hannah-foo2zjs_6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKnBAEBCgCRFiEEYgH7/9u94Hgi6ruWlvysDTh7WEcFAmVBgZ9fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYy
MDFGQkZGREJCREUwNzgyMkVBQkI5Njk2RkNBQzBEMzg3QjU4NDcTHGRlYmlhbkBh
bHRlaG9sei5kZQAKCRCW/KwNOHtYRxR0EACB+qgNWLJNyBqclwA+bpvJy157yZ/+
zJGDxFh00wNIe4ir+2YO95Y30tIrRoP92b2RHEeY0MyDvBcFgowoHX0Rzccxlshm
Urw55qXS6+BtQ4Q5fxlu5Bg/z4qR9G3kW+b0xdSAodaLxuPlWs5Z8iGmINFJNVDg
Z2no/xgw50dBBKiolSaalFR/dp5jAY9eaY1ucvBBy+7EpzaQAaAIypJC9FtRZYyJ
KMxIEYw9N3xRcD0a8/2tkuMTtwWsgT9BY36EFLGWV8WgTPfgXLdcP5sNiFUV4nXE
h7nbdKMbPeMPiEkm4ahgEYlvqmzRKs7iUUk2jFwQt430q2uqWYa6D1Fv5Capt4+K

Bug#1055111: ffmpeg FTBFS: makeinfo: Undefined subroutine ::Config::set_from_init_file called at doc/t2h.pm

2023-10-31 Thread Hilmar Preuße


On 10/31/23 17:21, Adrian Bunk wrote:

Hi,


https://buildd.debian.org/status/logs.php?pkg=ffmpeg=7%3A6.0-8

...
makeinfo --html -I doc --no-split -D config-not-all --init-file=/<>/doc/t2h.pm 
--output doc/ffmpeg.html /<>/doc/ffmpeg.texi
makeinfo: error parsing /<>/doc/t2h.pm: Undefined subroutine 
::Config::set_from_init_file called at /<>/doc/t2h.pm line 24.
make[2]: *** [/<>/doc/Makefile:70: doc/ffmpeg.html] Error 1

Could it be caused the upload of TeXinfo 7.1, did it work with TeXinfo 
from testing? I don't see any change for this in the 
/usr/share/doc/texinfo/NEWS.gz .


Hilmar
--
Testmail



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1055123: efivar builds with -march=native on !ia64

2023-10-31 Thread Aurelien Jarno

Hi,

On 2023-10-31 22:43, Adrian Bunk wrote:
> Source: efivar
> Version: 38-1
> Severity: serious
> Tags: ftbfs
> 
> https://buildd.debian.org/status/logs.php?pkg=efivar=38-1
> 
> -march=native is a baseline violation on architectures where
> it is supported, and causes a FTBFS on architectures where
> it is not supported.

This is correct if the resulting binaries are shipped in the package
which is not the case here, so I am not sure this bug warrants the
serious severity.

Anyway at least for riscv64 there is a patch available upstream [1].

Regards
Aurelien

[1] 
https://github.com/rhboot/efivar/commit/aab4e9b10ac9e98588a1b19771cf6f4c8c0a3096

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://aurel32.net

Bug#1054701: marked as done (fenics-dolfinx: FTBFS: Could not find a configuration file for package "Catch2" that is compatible with requested version "2".)

2023-10-31 Thread Debian Bug Tracking System

Your message dated Tue, 31 Oct 2023 20:40:47 +
with message-id 
and subject line Bug#1054701: fixed in fenics-dolfinx 1:0.7.1-1
has caused the Debian Bug report #1054701,
regarding fenics-dolfinx: FTBFS: Could not find a configuration file for 
package "Catch2" that is compatible with requested version "2".
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.)


-- 
1054701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054701
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fenics-dolfinx
Version: 1:0.6.0-8
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[3]: Entering directory '/<>/obj-x86_64-linux-gnu-complex'
> make[3]: Nothing to be done for 'preinstall'.
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu-complex'
> Install the project...
> /usr/bin/cmake -P cmake_install.cmake
> -- Install configuration: "RelWithDebInfo"
> -- Installing: 
> /<>/debian/tmp-complex/usr/lib/x86_64-linux-gnu/libdolfinx_complex.so.0.6.0.13
> -- Installing: 
> /<>/debian/tmp-complex/usr/lib/x86_64-linux-gnu/libdolfinx_complex.so.0.6gcc13
> -- Installing: 
> /<>/debian/tmp-complex/usr/lib/x86_64-linux-gnu/libdolfinx_complex.so
> -- Installing: 
> /<>/debian/tmp-complex/usr/lib/x86_64-linux-gnu/cmake/dolfinx/DOLFINXTargets.cmake
> -- Installing: 
> /<>/debian/tmp-complex/usr/lib/x86_64-linux-gnu/cmake/dolfinx/DOLFINXTargets-relwithdebinfo.cmake
> -- Installing: /<>/debian/tmp-complex/usr/include/dolfinx.h
> -- Installing: 
> /<>/debian/tmp-complex/usr/include/dolfinx/common/defines.h
> -- Installing: 
> /<>/debian/tmp-complex/usr/include/dolfinx/common/dolfin_common.h
> -- Installing: 
> /<>/debian/tmp-complex/usr/include/dolfinx/common/dolfin_doc.h
> -- Installing: 
> /<>/debian/tmp-complex/usr/include/dolfinx/common/IndexMap.h
> -- Installing: 
> /<>/debian/tmp-complex/usr/include/dolfinx/common/log.h
> -- Installing: 
> /<>/debian/tmp-complex/usr/include/dolfinx/common/loguru.hpp
> -- Installing: 
> /<>/debian/tmp-complex/usr/include/dolfinx/common/sort.h
> -- Installing: 
> /<>/debian/tmp-complex/usr/include/dolfinx/common/math.h
> -- Installing: 
> /<>/debian/tmp-complex/usr/include/dolfinx/common/MPI.h
> -- Installing: 
> /<>/debian/tmp-complex/usr/include/dolfinx/common/Scatterer.h
> -- Installing: 
> /<>/debian/tmp-complex/usr/include/dolfinx/common/Table.h
> -- Installing: 
> /<>/debian/tmp-complex/usr/include/dolfinx/common/Timer.h
> -- Installing: 
> /<>/debian/tmp-complex/usr/include/dolfinx/common/TimeLogger.h
> -- Installing: 
> /<>/debian/tmp-complex/usr/include/dolfinx/common/TimeLogManager.h
> -- Installing: 
> /<>/debian/tmp-complex/usr/include/dolfinx/common/timing.h
> -- Installing: 
> /<>/debian/tmp-complex/usr/include/dolfinx/common/utils.h
> -- Installing: 
> /<>/debian/tmp-complex/usr/include/dolfinx/fem/Constant.h
> -- Installing: 
> /<>/debian/tmp-complex/usr/include/dolfinx/fem/CoordinateElement.h
> -- Installing: 
> /<>/debian/tmp-complex/usr/include/dolfinx/fem/DirichletBC.h
> -- Installing: 
> /<>/debian/tmp-complex/usr/include/dolfinx/fem/DofMap.h
> -- Installing: 
> /<>/debian/tmp-complex/usr/include/dolfinx/fem/ElementDofLayout.h
> -- Installing: 
> /<>/debian/tmp-complex/usr/include/dolfinx/fem/Expression.h
> -- Installing: 
> /<>/debian/tmp-complex/usr/include/dolfinx/fem/FiniteElement.h
> -- Installing: 
> /<>/debian/tmp-complex/usr/include/dolfinx/fem/Form.h
> -- Installing: 
> /<>/debian/tmp-complex/usr/include/dolfinx/fem/Function.h
> -- Installing: 
> /<>/debian/tmp-complex/usr/include/dolfinx/fem/FunctionSpace.h
> -- Installing: 
> /<>/debian/tmp-complex/usr/include/dolfinx/fem/assembler.h
> -- Installing: 
> /<>/debian/tmp-complex/usr/include/dolfinx/fem/assemble_matrix_impl.h
> -- Installing: 
> /<>/debian/tmp-complex/usr/include/dolfinx/fem/assemble_scalar_impl.h
> -- Installing: 
> /<>/debian/tmp-complex/usr/include/dolfinx/fem/assemble_vector_impl.h
> -- Installing: 
> /<>/debian/tmp-complex/usr/include/dolfinx/fem/discreteoperators.h
> -- Installing: 
> /<>/debian/tmp-complex/usr/include/dolfinx/fem/dofmapbuilder.h
> -- Installing: 
> /<>/debian/tmp-complex/usr/include/dolfinx/fem/dolfin_fem.h
> -- Installing: 
> /<>/debian/tmp-complex/usr/include/dolfinx/fem/interpolate.h
> -- Installing: 
> /<>/debian/tmp-complex/usr/include/dolfinx/fem/petsc.h
> -- Installing: 
> /<>/debian/tmp-complex/usr/include/dolfinx/fem/sparsitybuild.h
> -- Installing: 
>

Bug#1055123: efivar builds with -march=native on !ia64

2023-10-31 Thread Adrian Bunk

Source: efivar
Version: 38-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=efivar=38-1

-march=native is a baseline violation on architectures where
it is supported, and causes a FTBFS on architectures where
it is not supported.

It also changes the set of architectures where the package
might run based on the capabilities of the buildd, e.g. on amd64
code built on an AMD buildd might not run on Intel hardware and
code built on Intel hardware might not run on AMD hardware.

Processed: found 1051729 in 4.2.2-1, found 1051729 in 4.0.0-4.1

2023-10-31 Thread Debian Bug Tracking System

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

> found 1051729 4.2.2-1
Bug #1051729 {Done: Alastair McKinstry } [src:pmix] pmix: 
CVE-2023-41915
Marked as found in versions pmix/4.2.2-1.
> found 1051729 4.0.0-4.1
Bug #1051729 {Done: Alastair McKinstry } [src:pmix] pmix: 
CVE-2023-41915
Marked as found in versions pmix/4.0.0-4.1.
> thanks
Stopping processing here.

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

Processed: Raising severity to serious, ceres-solver has reached unstable

2023-10-31 Thread Debian Bug Tracking System

Processing control commands:

> severity -1 serious
Bug #1054556 [src:colmap] FTBFS against ceres-solver/2.2.0+dfsg-1 currently in 
experimental
Severity set to 'serious' from 'important'

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

Bug#1055120: rust-chrono breaks rust-pyo3 autopkgtest: panicked at 'called `Option::unwrap()` on a `None` value'

2023-10-31 Thread Paul Gevers


Source: rust-chrono, rust-pyo3
Control: found -1 rust-chrono/0.4.31-1
Control: found -1 rust-pyo3/0.19.0-3
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
rust-chronofrom testing0.4.31-1
rust-pyo3  from testing0.19.0-3
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 rust-chrono to 
testing [1]. Due to the nature of this issue, I filed this bug report 
against both packages. Can you please investigate the situation and 
reassign the bug to the right package?


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=rust-chrono

https://ci.debian.net/data/autopkgtest/testing/armel/r/rust-pyo3/39387157/log.gz

1099s failures:
1099s
1099s  conversions::chrono::tests::test_pyo3_datetime_topyobject 
stdout 
1099s thread 'conversions::chrono::tests::test_pyo3_datetime_topyobject' 
panicked at 'called `Option::unwrap()` on a `None` value', 
src/conversions/chrono.rs:574:26

1099s stack backtrace:
1099s0: rust_begin_unwind
1099s  at 
/usr/src/rustc-1.70.0/library/std/src/panicking.rs:578:5

1099s1: core::panicking::panic_fmt
1099s  at 
/usr/src/rustc-1.70.0/library/core/src/panicking.rs:67:14

1099s2: core::panicking::panic
1099s  at 
/usr/src/rustc-1.70.0/library/core/src/panicking.rs:117:5

1099s3: core::option::Option::unwrap
1099s  at 
/usr/src/rustc-1.70.0/library/core/src/option.rs:950:21
1099s4: 
pyo3::conversions::chrono::tests::test_pyo3_datetime_topyobject::{{closure}}::{{closure}}

1099s  at ./src/conversions/chrono.rs:571:36
1099s5: pyo3::marker::Python::with_gil
1099s  at ./src/marker.rs:433:9
1099s6: 
pyo3::conversions::chrono::tests::test_pyo3_datetime_topyobject::{{closure}}

1099s  at ./src/conversions/chrono.rs:570:17
1099s7: pyo3::conversions::chrono::tests::test_pyo3_datetime_topyobject
1099s  at ./src/conversions/chrono.rs:603:9
1099s8: 
pyo3::conversions::chrono::tests::test_pyo3_datetime_topyobject::{{closure}}

1099s  at ./src/conversions/chrono.rs:567:40
1099s9: core::ops::function::FnOnce::call_once
1099s  at 
/usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5

1099s   10: core::ops::function::FnOnce::call_once
1099s  at 
/usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
1099s note: Some details are omitted, run with `RUST_BACKTRACE=full` for 
a verbose backtrace.

1099s
1099s  conversions::chrono::tests::test_pyo3_time_topyobject stdout 
1099s thread 'conversions::chrono::tests::test_pyo3_time_topyobject' 
panicked at 'called `Option::unwrap()` on a `None` value', 
src/conversions/chrono.rs:798:22

1099s stack backtrace:
1099s0: rust_begin_unwind
1099s  at 
/usr/src/rustc-1.70.0/library/std/src/panicking.rs:578:5

1099s1: core::panicking::panic_fmt
1099s  at 
/usr/src/rustc-1.70.0/library/core/src/panicking.rs:67:14

1099s2: core::panicking::panic
1099s  at 
/usr/src/rustc-1.70.0/library/core/src/panicking.rs:117:5

1099s3: core::option::Option::unwrap
1099s  at 
/usr/src/rustc-1.70.0/library/core/src/option.rs:950:21
1099s4: 
pyo3::conversions::chrono::tests::test_pyo3_time_topyobject::{{closure}}::{{closure}}

1099s  at ./src/conversions/chrono.rs:797:28
1099s5: pyo3::marker::Python::with_gil
1099s  at ./src/marker.rs:433:9
1099s6: 
pyo3::conversions::chrono::tests::test_pyo3_time_topyobject::{{closure}}

1099s  at ./src/conversions/chrono.rs:796:13
1099s7: pyo3::conversions::chrono::tests::test_pyo3_time_topyobject
1099s  at ./src/conversions/chrono.rs:822:9
1099s8: 
pyo3::conversions::chrono::tests::test_pyo3_time_topyobject::{{closure}}

1099s  at ./src/conversions/chrono.rs:794:36
1099s9: core::ops::function::FnOnce::call_once
1099s  at 
/usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5

1099s   10: core::ops::function::FnOnce::call_once
1099s  at 
/usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
1099s note: Some details are omitted, run with `RUST_BACKTRACE=full` for 
a verbose backtrace.

1099s
1099s  conversions::chrono::tests::test_pyo3_datetime_frompyobject 
stdout 
1099s thread

Processed: rust-chrono breaks rust-pyo3 autopkgtest: panicked at 'called `Option::unwrap()` on a `None` value'

2023-10-31 Thread Debian Bug Tracking System

Processing control commands:

> found -1 rust-chrono/0.4.31-1
Bug #1055120 [src:rust-chrono, src:rust-pyo3] rust-chrono breaks rust-pyo3 
autopkgtest: panicked at 'called `Option::unwrap()` on a `None` value'
Marked as found in versions rust-chrono/0.4.31-1.
> found -1 rust-pyo3/0.19.0-3
Bug #1055120 [src:rust-chrono, src:rust-pyo3] rust-chrono breaks rust-pyo3 
autopkgtest: panicked at 'called `Option::unwrap()` on a `None` value'
Marked as found in versions rust-pyo3/0.19.0-3.

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

Bug#1054666: open-vm-tools: CVE-2023-34059 CVE-2023-34058

2023-10-31 Thread Moritz Muehlenhoff

On Tue, Oct 31, 2023 at 10:29:55AM +0100, Bernd Zeimetz wrote:
> 
> Both uploaded!

DSA has been released, thanks!

Cheers,
Moritz

Bug#1055107: crowdsec fails its autopkgtests on armel

2023-10-31 Thread Cyril Brulebois

Nilesh Patra  (2023-10-31):
> Since this means it is a flaky test and a recurring problem, would it
> make sense to skip those tests to save some cycles for debci?

I didn't say I was certain, quite the opposite.

> I had triggered it - we will see if it fixes itself.

Looking at https://ci.debian.net/packages/c/crowdsec/testing/armel/
it succeeded, 4 times in a row, within 2 minutes…


Cheers,
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/


signature.asc
Description: PGP signature

Bug#1053310: Fixes for stable/oldstable?

2023-10-31 Thread Andreas Metzler

On 2023-10-31 Tomas Pospisek  wrote:
[...]
> PS: I'd prefer this bugreport to be open as long as the stable and
> oldstable packages are still vulnerable...

Hello Thomas,
The Debian BTS does not use a simple open/close logic, it tracks which
specific versions a bug applies to. If you look at
https://bugs.debian.org/cgi-bin/1053310 there is both textual info
("Found in version exim4/4.94.2-7 Fixed in version exim4/4.97~RC2-2")
and a nice graph in red and green to display this and the overview pages
can also show bugs applying to specific distributions. (Menu items at
the bottom of the page.) e.g. 
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=stable;package=exim4-base
does not show this bug under "Resolved bugs".

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1052541: marked as done (apfs-dkms: Still not building)

2023-10-31 Thread Debian Bug Tracking System

Your message dated Tue, 31 Oct 2023 18:49:21 +
with message-id 
and subject line Bug#1043112: fixed in linux-apfs-rw 0.3.5-1
has caused the Debian Bug report #1043112,
regarding apfs-dkms: Still not building
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.)


-- 
1043112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043112
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apfs-dkms
Version: 0.3.3+git20230810+ds-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Dear Maintainer,

Module still does not build with the current unstable version and kernel 6.5.
Using latest upstream (0.3.4) seems to fix the problem though.


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

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

Versions of packages apfs-dkms depends on:
ii  dkms  3.0.11-3

apfs-dkms recommends no packages.

apfs-dkms suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: linux-apfs-rw
Source-Version: 0.3.5-1
Done: Gürkan Myczko 

We believe that the bug you reported is fixed in the latest version of
linux-apfs-rw, 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 1043...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gürkan Myczko  (supplier of updated linux-apfs-rw 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: Tue, 31 Oct 2023 19:30:14 +0100
Source: linux-apfs-rw
Architecture: source
Version: 0.3.5-1
Distribution: unstable
Urgency: medium
Maintainer: Gürkan Myczko 
Changed-By: Gürkan Myczko 
Closes: 1043112
Changes:
 linux-apfs-rw (0.3.5-1) unstable; urgency=medium
 .
   * New upstream version. (Closes: #1043112)
Checksums-Sha1:
 cb935ee2e0d265a448851534ed80044a6611507b 1927 linux-apfs-rw_0.3.5-1.dsc
 39a15ab041892a393484b9c84c5e08ac1c75b4c0 201976 linux-apfs-rw_0.3.5.orig.tar.gz
 cb6384048ea45c5a9a6b88e796c21e84747fda85 4072 
linux-apfs-rw_0.3.5-1.debian.tar.xz
 db2c07dec075643e7aa17ff9fabf5bb1657aeb85 6900 
linux-apfs-rw_0.3.5-1_source.buildinfo
Checksums-Sha256:
 ec5da4f858c9e1092888dbae1ada1b697fdbc42d51e78e388826a4cf4f8edb9a 1927 
linux-apfs-rw_0.3.5-1.dsc
 877334f0eaa855a19cd923166db910372d33d73f698b0134f52f1f77d618f2cb 201976 
linux-apfs-rw_0.3.5.orig.tar.gz
 941fbf4defcfb9aa4fc03bf99fcfce78513e5338e979c57ddd15f09575271ffd 4072 
linux-apfs-rw_0.3.5-1.debian.tar.xz
 e497b0fdff63a68c1fd24d02ad4a7d75bd77a84e9ca519170d5f39d75f913bb1 6900 
linux-apfs-rw_0.3.5-1_source.buildinfo
Files:
 c7beb9c224f2bcf8d53a38e1a8e0fb31 1927 kernel optional linux-apfs-rw_0.3.5-1.dsc
 d9f6774d8e284cfaceeebd5a057f2a9c 201976 kernel optional 
linux-apfs-rw_0.3.5.orig.tar.gz
 3416b76f935c32809494015e7c28fa20 4072 kernel optional 
linux-apfs-rw_0.3.5-1.debian.tar.xz
 fb86b19780d33d4818a960efe03461d7 6900 kernel optional 
linux-apfs-rw_0.3.5-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtgob82PcExn/Co6JEWhSvN91FcAFAmVBSSsACgkQEWhSvN91
FcA6TxAAmEK118k0MiGgoLgzzBPCji1OErA6kqIdyZmzXhtw/4/jLVP8srBqQVjw
W4moXMwMVrrZpWpbIDkeuF5Tl2cKzvpKGeEmOzka88lvPKokY4IVlOBUqTgSZAJl
nRCO3lTZtMPE6VqwAMygtOX+aApeCSXt46WOWm47hQ4qj4k2Ic/rkxYvUj08H3aF
r8yVUJHrV88iP4MPdTmfa0yATPk5Rfo+8MA7x5I5bPEnO6sBmLx3VJGphx1ZAcOM
Q+7RlYX8inPTYFCShBtKuuiRAqpQhDyuxYpzujFilh3YFszb8VvLbsM/IlvTLXx6
8YdCr8o2p+WSu/D2k/Mvl9J+Jj9CFu7RMQoz1ESwpRyB3ZspZyHIZWrFkN6HW2sp
CgOf9RJ8Ac1w6NSxXE3w+b1zktsw1MLmtZLLOUtClDqc+uikrjy2uk40+ri1LGqZ
UT1+UmbtSj7hhRysHFZs2Lyi/pwEdHHsWjNcSJg8CP1DlEXXTU4ehZMhLlsnHpnq
MXNgd7FOX0Zd3VN1KpiWYSggcnbmre6cqqL36+fQhOMTvToPkdxavY34jmDSg6VP
fuwZq4nAuWQI+6tJNLLt2Ocp2OpsM2/3fbd+oj7UgnAYPWZgIunXQBXHCXOT1P6G
mZdzE45/X1Z+pSi43FSuO/WXtGbB+NAvJ0MAasvBN4KF1fHhNxY=
=vc3a
-END PGP SIGNATURE End Message ---

Bug#1043112: marked as done (apfs-dkms: module fails to build for Linux 6.5: detected write beyond size of object)

2023-10-31 Thread Debian Bug Tracking System

Your message dated Tue, 31 Oct 2023 18:49:21 +
with message-id 
and subject line Bug#1043112: fixed in linux-apfs-rw 0.3.5-1
has caused the Debian Bug report #1043112,
regarding apfs-dkms: module fails to build for Linux 6.5: detected write beyond 
size of object
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.)


-- 
1043112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043112
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apfs-dkms
Version: 0.3.3-2
Severity: important

DKMS make.log for linux-apfs-rw-0.3.3-2 for kernel 6.5.0-0-amd64 (x86_64)
Sun Aug  6 08:39:02 UTC 2023
make: Entering directory '/usr/src/linux-headers-6.5.0-0-amd64'
  CC [M]  /var/lib/dkms/linux-apfs-rw/0.3.3-2/build/btree.o
  CC [M]  /var/lib/dkms/linux-apfs-rw/0.3.3-2/build/compress.o
  CC [M]  /var/lib/dkms/linux-apfs-rw/0.3.3-2/build/dir.o
  CC [M]  /var/lib/dkms/linux-apfs-rw/0.3.3-2/build/extents.o
  CC [M]  /var/lib/dkms/linux-apfs-rw/0.3.3-2/build/file.o
  CC [M]  /var/lib/dkms/linux-apfs-rw/0.3.3-2/build/inode.o
  CC [M]  /var/lib/dkms/linux-apfs-rw/0.3.3-2/build/key.o
  CC [M]  /var/lib/dkms/linux-apfs-rw/0.3.3-2/build/libzbitmap.o
  CC [M]  /var/lib/dkms/linux-apfs-rw/0.3.3-2/build/lzfse/lzfse_decode.o
  CC [M]  /var/lib/dkms/linux-apfs-rw/0.3.3-2/build/lzfse/lzfse_decode_base.o
  CC [M]  /var/lib/dkms/linux-apfs-rw/0.3.3-2/build/lzfse/lzfse_fse.o
  CC [M]  /var/lib/dkms/linux-apfs-rw/0.3.3-2/build/lzfse/lzvn_decode_base.o
  CC [M]  /var/lib/dkms/linux-apfs-rw/0.3.3-2/build/message.o
  CC [M]  /var/lib/dkms/linux-apfs-rw/0.3.3-2/build/namei.o
  CC [M]  /var/lib/dkms/linux-apfs-rw/0.3.3-2/build/node.o
  CC [M]  /var/lib/dkms/linux-apfs-rw/0.3.3-2/build/object.o
  CC [M]  /var/lib/dkms/linux-apfs-rw/0.3.3-2/build/snapshot.o
  CC [M]  /var/lib/dkms/linux-apfs-rw/0.3.3-2/build/spaceman.o
  CC [M]  /var/lib/dkms/linux-apfs-rw/0.3.3-2/build/super.o
  CC [M]  /var/lib/dkms/linux-apfs-rw/0.3.3-2/build/symlink.o
  CC [M]  /var/lib/dkms/linux-apfs-rw/0.3.3-2/build/transaction.o
  CC [M]  /var/lib/dkms/linux-apfs-rw/0.3.3-2/build/unicode.o
In file included from 
/usr/src/linux-headers-6.5.0-0-common/include/linux/string.h:254,
 from 
/usr/src/linux-headers-6.5.0-0-common/include/linux/bitmap.h:11,
 from 
/usr/src/linux-headers-6.5.0-0-common/include/linux/cpumask.h:12,
 from 
/usr/src/linux-headers-6.5.0-0-common/arch/x86/include/asm/paravirt.h:17,
 from 
/usr/src/linux-headers-6.5.0-0-common/arch/x86/include/asm/cpuid.h:62,
 from 
/usr/src/linux-headers-6.5.0-0-common/arch/x86/include/asm/processor.h:19,
 from 
/usr/src/linux-headers-6.5.0-0-common/arch/x86/include/asm/cpufeature.h:5,
 from 
/usr/src/linux-headers-6.5.0-0-common/arch/x86/include/asm/thread_info.h:53,
 from 
/usr/src/linux-headers-6.5.0-0-common/include/linux/thread_info.h:60,
 from 
/usr/src/linux-headers-6.5.0-0-common/arch/x86/include/asm/preempt.h:9,
 from 
/usr/src/linux-headers-6.5.0-0-common/include/linux/preempt.h:79,
 from 
/usr/src/linux-headers-6.5.0-0-common/include/linux/spinlock.h:56,
 from 
/usr/src/linux-headers-6.5.0-0-common/include/linux/mmzone.h:8,
 from 
/usr/src/linux-headers-6.5.0-0-common/include/linux/gfp.h:7,
 from 
/usr/src/linux-headers-6.5.0-0-common/include/linux/slab.h:16,
 from /var/lib/dkms/linux-apfs-rw/0.3.3-2/build/dir.c:6:
In function 'strcpy',
inlined from 'apfs_build_sibling_val' at 
/var/lib/dkms/linux-apfs-rw/0.3.3-2/build/dir.c:437:2,
inlined from 'apfs_create_sibling_link_rec' at 
/var/lib/dkms/linux-apfs-rw/0.3.3-2/build/dir.c:478:12,
inlined from 'apfs_create_sibling_recs' at 
/var/lib/dkms/linux-apfs-rw/0.3.3-2/build/dir.c:559:8:
/usr/src/linux-headers-6.5.0-0-common/include/linux/fortify-string.h:798:17: 
error: call to '__write_overflow' declared with attribute error: detected write 
beyond size of object (1st parameter)
  798 | __write_overflow();
  | ^~
In function 'strcpy',
inlined from 'apfs_build_dentry_hashed_key' at 
/var/lib/dkms/linux-apfs-rw/0.3.3-2/build/dir.c:300:2,
inlined from 'apfs_create_dentry_rec' at 
/var/lib/dkms/linux-apfs-rw/0.3.3-2/build/dir.c:386:13:
/usr/src/linux-headers-6.5.0-0-common/include/linux/fortify-string.h:798:17: 
error: call to '__write_overflow' declared with attribute error: detected write 
beyond size of object (1st parameter)
  798 |

Bug#1053310: Fixes for stable/oldstable?

2023-10-31 Thread Andreas Metzler

On 2023-10-31 Tomas Pospisek  wrote:
> On Tue, 31 Oct 2023, Salvatore Bonaccorso wrote:
[...]
>> Fixes for CVE-2023-42117 and CVE-2023-42119 are right now considered
>> no-dsa (see comment on the security-tracker about it), and are going
>> to be fixed in the next point releases.

> The notes say:

> ***
> [bookworm] - exim4  (Only an issue if Exim4 run behind an
>  untrusted proxy-protocol proxy)
[...]
> So I think I can parse from those that CVE-2023-42117 is only critical when
> exim is run behind a "untrusted proxy-protocol proxy".

> Questions if you will:

> * what does "no-dsa" mean? DSA seems to mean Debian Security Announce.
>   Does it mean there is no DSA for that problem yet? What does it mean
>   when a CVE is considered "no-dsa" then? That no DSA will be released for
>   it?

Hello Thomas,

Exactly. The severity was judged to be very low, not "worth" the effort
of a DSA.

> * what is a "untrusted proxy-protocol proxy" in the context of a mail
>   transport agent? So exim shouldn't be used behind an untrusted socks
>   proxy? Well I have no real control who connects how to a public MTA...
>   anybody can connect to it to try his luck sending me email. That
>   includes untrusted socks proxies...

This
https://www.exim.org/exim-html-current/doc/html/spec_html/ch-proxies.html
or more precisely part "1. Inbound proxies".

You need to explicitely configure exim to tell it that specific hosts
are acting as load-balancing proxy sitting in front of exim. I cannot
think of a szenario where these load-balancing proxies would not be
trusted machines. The issue is about weakening the chain a little bit -
take over the proxy first and then do something to the exim machines
behind.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1042627: marked as done (emscripten: FTBFS with Sphinx 7.1, docutils 0.20: make[1]: *** [debian/rules:210: execute_after_dh_auto_build-indep] Error 2)

2023-10-31 Thread Debian Bug Tracking System

Your message dated Tue, 31 Oct 2023 18:04:51 +
with message-id 
and subject line Bug#1042627: fixed in emscripten 3.1.6~dfsg-6
has caused the Debian Bug report #1042627,
regarding emscripten: FTBFS with Sphinx 7.1, docutils 0.20: make[1]: *** 
[debian/rules:210: execute_after_dh_auto_build-indep] Error 2
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.)


-- 
1042627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042627
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: emscripten
Version: 3.1.6~dfsg-5
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx7.1

Hi,

emscripten 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 '/<>'
> cmark-gfm README.md > README.html
> cmark-gfm --to plaintext README.md > README.txt
> cmark-gfm ChangeLog.md > ChangeLog.html
> cmark-gfm --to plaintext ChangeLog.md > ChangeLog.txt
> sphinx-build -b html site/source debian/doc/html
> Running Sphinx v7.1.1
> making output directory... done
> WARNING: The pre-Sphinx 1.0 'intersphinx_mapping' format is deprecated and 
> will be removed in Sphinx 8. Update to the current format as described in the 
> documentation. Hint: "intersphinx_mapping = {'': 
> ('http://docs.python.org/', 
> None)}".https://www.sphinx-doc.org/en/master/usage/extensions/intersphinx.html#confval-intersphinx_mapping
> loading intersphinx inventory from http://docs.python.org/objects.inv...
> intersphinx inventory has moved: http://docs.python.org/objects.inv -> 
> https://docs.python.org/3/objects.inv
> building [mo]: targets for 0 po files that are out of date
> writing output... 
> building [html]: targets for 78 source files that are out of date
> updating environment: [new config] 78 added, 0 changed, 0 removed
> [2Kreading sources... [  1%] docs/api_reference/Filesystem-API
> [2Kreading sources... [  3%] docs/api_reference/advanced-apis
> [2Kreading sources... [  4%] docs/api_reference/bind.h
> [2Kreading sources... [  5%] docs/api_reference/emscripten.h
> [2Kreading sources... [  6%] docs/api_reference/fetch
> [2Kreading sources... [  8%] docs/api_reference/fiber.h
> [2Kreading sources... [  9%] docs/api_reference/html5.h
> [2Kreading sources... [ 10%] docs/api_reference/index
> [2Kreading sources... [ 12%] docs/api_reference/module
> [2Kreading sources... [ 13%] docs/api_reference/preamble.js
> [2Kreading sources... [ 14%] docs/api_reference/trace.h
> [2Kreading sources... [ 15%] docs/api_reference/val.h
> [2Kreading sources... [ 17%] 
> docs/building_from_source/configuring_emscripten_settings
> [2Kreading sources... [ 18%] docs/building_from_source/index
> [2Kreading sources... [ 19%] 
> docs/building_from_source/toolchain_what_is_needed
> [2Kreading sources... [ 21%] 
> docs/building_from_source/verify_emscripten_environment
> [2Kreading sources... [ 22%] docs/compiling/Building-Projects
> [2Kreading sources... [ 23%] docs/compiling/Deploying-Pages
> [2Kreading sources... [ 24%] docs/compiling/Dynamic-Linking
> [2Kreading sources... [ 26%] docs/compiling/GitLab
> [2Kreading sources... [ 27%] docs/compiling/Running-html-files-with-emrun
> [2Kreading sources... [ 28%] docs/compiling/Travis
> [2Kreading sources... [ 29%] docs/compiling/WebAssembly
> [2Kreading sources... [ 31%] docs/compiling/index
> [2Kreading sources... [ 32%] docs/contributing/AUTHORS
> [2Kreading sources... [ 33%] docs/contributing/contributing
> [2Kreading sources... [ 35%] docs/contributing/developers_guide
> [2Kreading sources... [ 36%] docs/contributing/index
> [2Kreading sources... [ 37%] docs/debugging/Sanitizers
> [2Kreading sources... [ 38%] docs/getting_started/FAQ
> [2Kreading sources... [ 40%] docs/getting_started/Tutorial
> [2Kreading sources... [ 41%] docs/getting_started/bug_reports
> [2Kreading sources... [ 42%] docs/getting_started/downloads
> [2Kreading sources... [ 44%] docs/getting_started/index
> [2Kreading sources... [ 45%] docs/getting_started/test-suite
> [2Kreading sources... [ 46%] docs/index
> [2Kreading sources... [ 47%] 
> docs/introducing_emscripten/Talks-and-Publications
> [2Kreading sources... [ 49%] docs/introducing_emscripten/about_emscripten
> [2Kreading sources... [ 50%] docs/introducing_emscripten/community
> [2Kreading sources... [ 51%] docs/introducing_emscripten/emscripten_license
> [2Kreading sources... [ 53%] docs/introducing_emscripten/index
> [2Kreading sources... [ 54%] docs/introducing_emscripten/release_notes
>

Bug#1028212: proposed stable release update

2023-10-31 Thread Antoine Beaupré

I have filed #1055115 to update the package in bookworm.

a.
-- 
Nothing in life is to be feared, it is only to be understood.
Now is the time to understand more, so that we may fear less.
 - Marie Curie

Bug#1055107: crowdsec fails its autopkgtests on armel

2023-10-31 Thread Nilesh Patra

On Tue, Oct 31, 2023 at 05:32:53PM +0100, Cyril Brulebois wrote:
> Nilesh Patra  (2023-10-31):
> > On Tue, 31 Oct 2023 20:13:23 +0530 Nilesh Patra  wrote:
> > Full log at: 
> > https://ci.debian.net/data/autopkgtest/testing/armel/c/crowdsec/39385596/log.gz
> > 
> > > This is currently blocking golang-github-gin-gonic-gin to testing which
> > > fixes a bunch of RC bugs (of same kind).
> 
> I think we've had this issue showing up in a few cases (on other archs
> though), but I wasn't able to replicate it, possibly timing issues or
> something similar.

Since this means it is a flaky test and a recurring problem, would it
make sense to skip those tests to save some cycles for debci?

> I'd suggest a retry if that wasn't attempted already.

I had triggered it - we will see if it fixes itself.


Best,
Nilesh


signature.asc
Description: PGP signature

Bug#1054712: ensmallen: FTBFS: adam_test.cpp:17:10: fatal error: catch2/catch.hpp: No such file or directory

2023-10-31 Thread Drew Parsons

Source: ensmallen
Followup-For: Bug #1054712

Should be noted that the problem is linked to debian patch
0002-use-system-catch.patch, which disables upstream's local copy of
catch in order to use the system catch2 library.

So one workaround could be to disable 0002-use-system-catch.patch.

Bug#1055107: crowdsec fails its autopkgtests on armel

2023-10-31 Thread Cyril Brulebois

Hi,

Nilesh Patra  (2023-10-31):
> On Tue, 31 Oct 2023 20:13:23 +0530 Nilesh Patra  wrote:
> Full log at: 
> https://ci.debian.net/data/autopkgtest/testing/armel/c/crowdsec/39385596/log.gz
> 
> > This is currently blocking golang-github-gin-gonic-gin to testing which
> > fixes a bunch of RC bugs (of same kind).

I think we've had this issue showing up in a few cases (on other archs
though), but I wasn't able to replicate it, possibly timing issues or
something similar. I'd suggest a retry if that wasn't attempted already.

Cheers,
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/

signature.asc
Description: PGP signature

Processed: bug 1055111 is forwarded to https://trac.ffmpeg.org/ticket/10636, tagging 1055111

2023-10-31 Thread Debian Bug Tracking System

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

> forwarded 1055111 https://trac.ffmpeg.org/ticket/10636
Bug #1055111 [src:ffmpeg] ffmpeg FTBFS: makeinfo: Undefined subroutine 
::Config::set_from_init_file called at doc/t2h.pm
Set Bug forwarded-to-address to 'https://trac.ffmpeg.org/ticket/10636'.
> tags 1055111 + confirmed upstream
Bug #1055111 [src:ffmpeg] ffmpeg FTBFS: makeinfo: Undefined subroutine 
::Config::set_from_init_file called at doc/t2h.pm
Added tag(s) upstream and confirmed.
> thanks
Stopping processing here.

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

Bug#1055111: ffmpeg FTBFS: makeinfo: Undefined subroutine ::Config::set_from_init_file called at doc/t2h.pm

2023-10-31 Thread Adrian Bunk

Source: ffmpeg
Version: 7:6.0-8
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Debian TeX Task Force 

https://buildd.debian.org/status/logs.php?pkg=ffmpeg=7%3A6.0-8

...
makeinfo --html -I doc --no-split -D config-not-all 
--init-file=/<>/doc/t2h.pm --output doc/ffmpeg.html 
/<>/doc/ffmpeg.texi
makeinfo: error parsing /<>/doc/t2h.pm: Undefined subroutine 
::Config::set_from_init_file called at /<>/doc/t2h.pm line 
24.
make[2]: *** [/<>/doc/Makefile:70: doc/ffmpeg.html] Error 1

Bug#1055110: libgridxc builds with -march=native

2023-10-31 Thread Adrian Bunk

Source: libgridxc
Version: 2.0.0-1
Severity: serious
Tags: ftbfs

-march=native is a baseline violation on architectures where
it is supported, and causes a FTBFS on architectures where
it is not supported.

It also changes the set of architectures where the package
might run based on the capabilities of the buildd, e.g. on amd64
code built on an AMD buildd might not run on Intel hardware and
code built on Intel hardware might not run on AMD hardware.

Bug#1053774: spdlog: need new upstream release 1.12 for catch2 v3

2023-10-31 Thread Drew Parsons

Source: spdlog
Followup-For: Bug #1053774

Looks like you'll need to grab PR#2827 from upstream
https://github.com/gabime/spdlog/pull/2827

Processed: your mail

2023-10-31 Thread Debian Bug Tracking System

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

> unarchive 1051729
Bug #1051729 {Done: Alastair McKinstry } [src:pmix] pmix: 
CVE-2023-41915
Unarchived Bug 1051729
> thanks
Stopping processing here.

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

Processed: Re: ensmallen: FTBFS: adam_test.cpp:17:10: fatal error: catch2/catch.hpp: No such file or directory

2023-10-31 Thread Debian Bug Tracking System

Processing control commands:

> forwarded 1054712 https://github.com/mlpack/ensmallen/issues/372
Bug #1054712 [src:ensmallen] ensmallen: FTBFS: adam_test.cpp:17:10: fatal 
error: catch2/catch.hpp: No such file or directory
Set Bug forwarded-to-address to 
'https://github.com/mlpack/ensmallen/issues/372'.

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

Bug#1042651: marked as pending in python-pybedtools

2023-10-31 Thread Lance Lin

Control: tag -1 pending

Hello,

Bug #1042651 in python-pybedtools 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/med-team/python-pybedtools/-/commit/6b976a32668792cda4204a68c516c225bba5faac


Build docs with sphinx-build for Sphinx 7.1 (Closes: #1042651) and change 
sphinx docs location


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1042651

Processed: Bug#1042651 marked as pending in python-pybedtools

2023-10-31 Thread Debian Bug Tracking System

Processing control commands:

> tag -1 pending
Bug #1042651 [src:python-pybedtools] python-pybedtools: FTBFS with Sphinx 7.1, 
docutils 0.20: error: invalid command 'build_sphinx'
Added tag(s) pending.

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

Bug#1054712: ensmallen: FTBFS: adam_test.cpp:17:10: fatal error: catch2/catch.hpp: No such file or directory

2023-10-31 Thread Drew Parsons

Source: ensmallen
Followup-For: Bug #1054712
Control: forwarded 1054712 https://github.com/mlpack/ensmallen/issues/372

This error occurs because of the upgrade of catch2 from v2 to v3.

Unfortunately ensmallen upstream don't sound very enthusiastic about
dealing with it, https://github.com/mlpack/ensmallen/issues/372

Arguably the catch developers made life unjustifiablydifficult. Maybe
they should have released catch3 rather than catch2 v3.

On the other hand, judging by the patch for termpaint, the required
changes are likely to be essentially trivial, e.g. 
  #include "catch2/catch_all.hpp"
instead of 
  #include "catch2/catch.hpp"

cf.
https://github.com/termpaint/termpaint/commit/dc293554b745b3f010445e9445e620399f8ee2f7

Bug#1052942: insserv: FTBFS: insserv: Could not read script nolsbheader: No such file or directory

2023-10-31 Thread Mark Hindley

Control: tags -1 upstream
Control: retitle -1 Upstream testsuite fails to produce deterministic results

Santiago,

On Sun, Oct 29, 2023 at 02:39:44PM +0100, Santiago Vila wrote:
> However, I can create a machine for you to reproduce the problem.

Thanks. I have reproduced on your provided machine, but still not locally and I
can't identify the underlying difference between the builds.

In the failure case the problem is in the upstream testsuite, specifically the
test for #491391 in tests/run-testsuite which produces

init.d:
bootchart
four
one
rmnologin
three
two

insserv:
override

rc0.d:

rc1.d:

rc2.d:
S01one
S01three
S01two
S02four
S98rmnologin
S99bootchart

rc3.d:
S01one
S01three
S01two
S02four
S98rmnologin
S99bootchart

rc4.d:
S01one
S01three
S01two
S02four
S98rmnologin
S99bootchart

rc5.d:
S01one
S01three
S01two
S02four
S98rmnologin
S99bootchart

rc6.d:

rcS.d:
error: incorrect 5 sequence bootchart not before rmnologin

The same failure mode appears to be responsible for armel and armhf autopkgtest
failures logged on ci.debian.net[1]

As Ian pointed out[2], there are significant and surprising changes in looping
order and behaviour between the successful and failing testsuites. The diff is 
attached.

Having said that, I still can't reproduce locally or determine a good fix.
Hopefully Jesse will have a useful contribution

Mark

[1]  
https://ci.debian.net/data/autopkgtest/unstable/armel/i/insserv/38435862/log.gz

[2]  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052942#15

diff -u --label /sshx\:atlas\:/tmp/build.log --label /home/mark/src/debian/insserv/build.log /tmp/tramp.mDUEXG.log /home/mark/src/debian/insserv/build.log
--- /sshx:atlas:/tmp/build.log
+++ /home/mark/src/debian/insserv/build.log
@@ -4,8 +4,15 @@
 dpkg-buildpackage: info: source changed by Mark Hindley 
  dpkg-source --before-build .
 dpkg-buildpackage: info: host architecture amd64
- fakeroot debian/rules clean
-echo -g -O2 -ffile-prefix-map=/home/mark/insserv-1.24.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
+dpkg-source: info: using patch list from debian/patches/series
+dpkg-source: info: applying install-binaries-ignore-PREFIX.patch
+dpkg-source: info: applying 11_debian_conf.patch
+dpkg-source: info: applying 110_portmap.patch
+dpkg-source: info: applying warn_in_ignore_mode.patch
+dpkg-source: info: applying 0004-Fix-spurious-warnings-about-unknown-virtual-dependen.patch
+dpkg-source: info: applying 0005-Fix-spelling-error-in-manpage.patch
+ debian/rules clean
+echo -g -O2 -ffile-prefix-map=/home/mark/insserv-1.24.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
 -g -O2 -ffile-prefix-map=/home/mark/insserv-1.24.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
 dh clean --with=bash-completion
dh_auto_clean
@@ -18,7 +25,7 @@
 make[1]: Leaving directory '/home/mark/insserv-1.24.0'
dh_clean
  debian/rules build
-echo -g -O2 -ffile-prefix-map=/home/mark/insserv-1.24.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
+echo -g -O2 -ffile-prefix-map=/home/mark/insserv-1.24.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
 -g -O2 -ffile-prefix-map=/home/mark/insserv-1.24.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
 dh build --with=bash-completion
dh_update_autotools_config
@@ -31,14 +31,14 @@
 cc -W -Wall -Wunreachable-code -g -O2 -ffile-prefix-map=/home/mark/insserv-1.24.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2   -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64  -DINITDIR=\"/etc/init.d\" -DINSCONF=\"/etc/insserv.conf\" -pipe   -c map.c
 cc -W -Wall -Wunreachable-code -g -O2 -ffile-prefix-map=/home/mark/insserv-1.24.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2   -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64  -DINITDIR=\"/etc/init.d\" -DINSCONF=\"/etc/insserv.conf\" -pipe   -c listing.c
 cc -W -Wall -Wunreachable-code -g -O2 -ffile-prefix-map=/home/mark/insserv-1.24.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2   -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64  -DINITDIR=\"/etc/init.d\" -DINSCONF=\"/etc/insserv.conf\" -pipe   insserv.c -c 
-insserv.c: In function ‘main’:
-insserv.c:2923:20: warning: ignoring return value of ‘asprintf’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
+insserv.c: In function 'main':
+insserv.c:2923:20: warning: ignoring return value of 'asprintf' declared with attribute 'warn_unused_result' [-Wunused-result]
  2923 |asprintf(_path, "%s/.", optarg);
   |

Processed: Re: Bug#1052942: insserv: FTBFS: insserv: Could not read script nolsbheader: No such file or directory

2023-10-31 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 upstream
Bug #1052942 [src:insserv] insserv: FTBFS: insserv: Could not read script 
nolsbheader: No such file or directory
Added tag(s) upstream.
> retitle -1 Upstream testsuite fails to produce deterministic results
Bug #1052942 [src:insserv] insserv: FTBFS: insserv: Could not read script 
nolsbheader: No such file or directory
Changed Bug title to 'Upstream testsuite fails to produce deterministic 
results' from 'insserv: FTBFS: insserv: Could not read script nolsbheader: No 
such file or directory'.

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

Bug#1055107: crowdsec fails its autopkgtests on armel

2023-10-31 Thread Nilesh Patra

On Tue, 31 Oct 2023 20:13:23 +0530 Nilesh Patra  wrote:
> Source: crowdsec
> Version: 1.4.6-6
> Severity: serious
> X-Debbugs-Cc: k...@debian.org
> 
> Dear Maintainer,
> 
> crowdsec fails its autopkgtests on unstable with:
> 
> | 316s === RUN   TestOneShot
> | 316s journalctl_test.go:172: Expected log output 'journalctl: invalid 
> option' but got nothing !
> | 316s --- FAIL: TestOneShot (0.08s)
> | 316s === RUN   TestStreaming
> | 316s journalctl_test.go:181: unreliable test: 
> https://github.com/crowdsecurity/crowdsec/issues/2352
> | 316s --- SKIP: TestStreaming (0.00s)
> | 316s FAIL
> | 316s FAIL   
> github.com/crowdsecurity/crowdsec/pkg/acquisition/modules/journalctl0.225s
> | 319s ?  github.com/crowdsecurity/crowdsec/pkg/apiserver/controllers 
> [no test files]
> | 319s ?  github.com/crowdsecurity/crowdsec/pkg/apiserver/controllers/v1  
> [no test files]
> | 319s ?  github.com/crowdsecurity/crowdsec/pkg/apiserver/middlewares/v1  
> [no test files]
> | 319s ?  github.com/crowdsecurity/crowdsec/pkg/cstest[no test files]
> 

Full log at: 
https://ci.debian.net/data/autopkgtest/testing/armel/c/crowdsec/39385596/log.gz

> This is currently blocking golang-github-gin-gonic-gin to testing which
> fixes a bunch of RC bugs (of same kind).

Best,
Nilesh


signature.asc
Description: PGP signature

Processed: bug #1055106: downgrade severity

2023-10-31 Thread Debian Bug Tracking System

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

> severity 1055106 serious
Bug #1055106 [src:django-tables] Test failure prevents Django 4.x from entering 
in testing
Severity set to 'serious' from 'grave'
> thanks
Stopping processing here.

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

Bug#1055107: crowdsec fails its autopkgtests on armel

2023-10-31 Thread Nilesh Patra

Source: crowdsec
Version: 1.4.6-6
Severity: serious
X-Debbugs-Cc: k...@debian.org

Dear Maintainer,

crowdsec fails its autopkgtests on unstable with:

| 316s === RUN   TestOneShot
| 316s journalctl_test.go:172: Expected log output 'journalctl: invalid 
option' but got nothing !
| 316s --- FAIL: TestOneShot (0.08s)
| 316s === RUN   TestStreaming
| 316s journalctl_test.go:181: unreliable test: 
https://github.com/crowdsecurity/crowdsec/issues/2352
| 316s --- SKIP: TestStreaming (0.00s)
| 316s FAIL
| 316s FAIL 
github.com/crowdsecurity/crowdsec/pkg/acquisition/modules/journalctl0.225s
| 319s ?github.com/crowdsecurity/crowdsec/pkg/apiserver/controllers 
[no test files]
| 319s ?github.com/crowdsecurity/crowdsec/pkg/apiserver/controllers/v1  
[no test files]
| 319s ?github.com/crowdsecurity/crowdsec/pkg/apiserver/middlewares/v1  
[no test files]
| 319s ?github.com/crowdsecurity/crowdsec/pkg/cstest[no test files]

This is currently blocking golang-github-gin-gonic-gin to testing which
fixes a bunch of RC bugs (of same kind).

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

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

Bug#1055106: Test failure prevents Django 4.x from entering in testing

2023-10-31 Thread s3v

Package: src:django-tables
Version: 2.6.0-1
Severity: grave
Tags: patch


Dear Maintainer,
Tests fail on Debian CI infrastructure [1] and on my local machine as well
(full log attached).
This failure prevents python-django (3:4.2.6-1) from entering in testing [2].

$> autopkgtest --no-built-binaries django-tables_2.6.0-1.dsc -- null
...
...

ImportError: cannot import name 'url' from 'django.conf.urls' 
(/usr/lib/python3/dist-packages/django/conf/urls/__init__.py)
autopkgtest [14:12:24]: test test-run-py3: ---]
autopkgtest [14:12:24]: test test-run-py3:  - - - - - - - - - - results - - - - 
- - - - - -
test-run-py3 FAIL non-zero exit status 1
autopkgtest [14:12:24]:  summary
command1 PASS
test-run-py3 FAIL non-zero exit status 1


The root cause is that url() function was deprecated since Django 3.1 [3]
and removed in Django 4.x
Attached patch addresses the failure.

Kind Regards


[1] 
https://ci.debian.net/data/autopkgtest/unstable/amd64/d/django-tables/39070283/log.gz
[2] https://qa.debian.org/excuses.php?package=python-django
[3] https://code.djangoproject.com/ticket/31534--- django-tables-2.6.0/debian/tests/test-run-py3   2023-05-25 15:35:19.0 +
+++ django-tables-2.6.0/debian/tests/test-run-py3-new   2023-10-31 14:37:50.661433357 +
@@ -45,14 +45,14 @@
 
 
 cat > testproject/urls.py << __EOF__
-from django.conf.urls import url
+from django.urls import re_path
 from django.contrib import admin
 
 from tutorial.views import people
 
 urlpatterns = [
-url(r'^admin/', admin.site.urls),
-url(r'^people/', people)
+re_path(r'^admin/', admin.site.urls),
+re_path(r'^people/', people)
 ]
 __EOF__
 


full_log.tar.gz
Description: application/gzip

Bug#1042706: marked as done (kombu: FTBFS with Sphinx 7.1, docutils 0.20: make[1]: *** [debian/rules:13: override_dh_sphinxdoc] Error 2)

2023-10-31 Thread Debian Bug Tracking System

Your message dated Tue, 31 Oct 2023 14:34:18 +
with message-id 
and subject line Bug#1042706: fixed in kombu 5.3.2-2
has caused the Debian Bug report #1042706,
regarding kombu: FTBFS with Sphinx 7.1, docutils 0.20: make[1]: *** 
[debian/rules:13: override_dh_sphinxdoc] Error 2
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.)


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

Hi,

kombu 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 '/<>'
> http_proxy=127.0.0.1:9 https_proxy=127.0.0.1:9 PYTHONPATH=. python3 -m sphinx 
> -b html -d docs/.build/.doctrees -N docs 
> /<>/debian/python-kombu-doc/usr/share/doc/python-kombu-doc/html
> Running Sphinx v7.1.1
> making output directory... done
> 
> Extension error (sphinx.config):
> Handler  for event 
> 'config-inited' threw an exception (exception: string index out of range)
> make[1]: *** [debian/rules:13: override_dh_sphinxdoc] Error 2


The full build log is available from:
http://qa-logs.debian.net/2023/07/30/exp/kombu_5.3.1-2_unstable_sphinx-exp.log

Please see [1] for Sphinx changelog and [2] for Docutils changelog.

Also see [3] for the list of deprecated/removed APIs in Sphinx and possible
alternatives to them.

Some notable changes in Sphinx 6 and Sphinx 7:

- Sphinx no longer includes jquery.js and underscore.js by default.
  Please use python3-sphinxcontrib.jquery package if you are using a custom
  template and it still needs jquery.

- The setup.py build_sphinx command was removed. Please instead call
  sphinx-build or "python3 -m sphinx" directly.

- For packages using the extlinks extension, the caption should contain
  exactly one "%s" placeholder (if caption is not None).

In case you have questions, please Cc sph...@packages.debian.org on reply.

[1]: https://www.sphinx-doc.org/en/master/changes.html
[2]: 
https://repo.or.cz/docutils.git/blob/refs/tags/docutils-0.20.1:/RELEASE-NOTES.txt
[3]: 
https://www.sphinx-doc.org/en/master/extdev/deprecated.html#dev-deprecated-apis

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=sphinx7.1;users=python-modules-t...@lists.alioth.debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=sphinx7.1=python-modules-t...@lists.alioth.debian.org=1=1=1=1#results

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
--- End Message ---
--- Begin Message ---
Source: kombu
Source-Version: 5.3.2-2
Done: Michael Fladischer 

We believe that the bug you reported is fixed in the latest version of
kombu, 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.
Michael Fladischer  (supplier of updated kombu 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: Tue, 31 Oct 2023 09:20:05 +
Source: kombu
Architecture: source
Version: 5.3.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Michael Fladischer 
Closes: 1042706
Changes:
 kombu (5.3.2-2) unstable; urgency=medium
 .
   * Add patch to satisfy assinine sphinx 7.x parsing logic for copyright year
 substitution (Closes: #1042706).
Checksums-Sha1:
 99b6134f8f8a6a811eae2ce724dffa37b48bd78d 2519 kombu_5.3.2-2.dsc
 a7f98a35a49639b26baa513967b5e1e7b2e9a288 11836 kombu_5.3.2-2.debian.tar.xz
 0e7b62bfbf17e64a1d117f1c4f4f8851e8b6ff15 9718 kombu_5.3.2-2_arm64.buildinfo
Checksums-Sha256:
 698f10c6ef198f5503cdd00fc6fa71918647cc70c8a923ec9edce02eaae7cd5f 2519 
kombu_5.3.2-2.dsc
 c5a0535dc8f0467ace333b4f82995d07d0cd76d3830ec5f82b64e14495bbcbe0 11836 
kombu_5.3.2-2.debian.tar.xz
 4a2f490a5f343206f7bedba5383a3f2ba6136f4eca0ebe6775ce7e549c53cf25 9718 
kombu_5.3.2-2_arm64.buildinfo
Files:

Bug#1054689: therion: FTBFS: utest-proj.cxx:1:10: fatal error: catch2/catch.hpp: No such file or directory

2023-10-31 Thread Martin Budaj

Thanks, I'll check it out in a week or so.
Martin

On Fri, Oct 27, 2023, 21:21 Lucas Nussbaum  wrote:

> Source: therion
> Version: 6.1.8-1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20231027 ftbfs-trixie
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
>
> Relevant part (hopefully):
> > /usr/bin/c++ -DFMT_SHARED -DIMG_API_VERSION=1 -DPROJ_VER=9 -DTHLINUX
> -I/<>/build -I/<> -isystem /usr/include/webp
> -isystem /<>/extern/quickhull -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++17 -Wall -Wextra -MD -MT
> CMakeFiles/utest.dir/utest-proj.cxx.o -MF
> CMakeFiles/utest.dir/utest-proj.cxx.o.d -o
> CMakeFiles/utest.dir/utest-proj.cxx.o -c /<>/utest-proj.cxx
> > /<>/utest-proj.cxx:1:10: fatal error: catch2/catch.hpp: No
> such file or directory
> > 1 | #include 
> >   |  ^~
> > compilation terminated.
> > [113/168] /usr/bin/c++ -DFMT_SHARED -DIMG_API_VERSION=1 -DPROJ_VER=9
> -DTHLINUX -I/<>/build -I/<> -isystem
> /usr/include/webp -isystem /<>/extern/quickhull -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++17 -Wall -Wextra -MD -MT
> CMakeFiles/therion-common.dir/thwarppt.cxx.o -MF
> CMakeFiles/therion-common.dir/thwarppt.cxx.o.d -o
> CMakeFiles/therion-common.dir/thwarppt.cxx.o -c
> /<>/thwarppt.cxx
> > [114/168] /usr/bin/c++ -DFMT_SHARED -DIMG_API_VERSION=1 -DPROJ_VER=9
> -DTHLINUX -I/<>/build -I/<> -isystem
> /usr/include/webp -isystem /<>/extern/quickhull -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++17 -Wall -Wextra -MD -MT
> CMakeFiles/therion.dir/therion-main.cxx.o -MF
> CMakeFiles/therion.dir/therion-main.cxx.o.d -o
> CMakeFiles/therion.dir/therion-main.cxx.o -c
> /<>/therion-main.cxx
> > [115/168] /usr/bin/c++ -DFMT_SHARED -DIMG_API_VERSION=1 -DPROJ_VER=9
> -DTHLINUX -I/<>/build -I/<> -isystem
> /usr/include/webp -isystem /<>/extern/quickhull -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++17 -Wall -Wextra -MD -MT
> CMakeFiles/therion-common.dir/thsvg.cxx.o -MF
> CMakeFiles/therion-common.dir/thsvg.cxx.o.d -o
> CMakeFiles/therion-common.dir/thsvg.cxx.o -c /<>/thsvg.cxx
> > [116/168] /usr/bin/c++ -DFMT_SHARED -DIMG_API_VERSION=1 -DPROJ_VER=9
> -DTHLINUX -I/<>/build -I/<> -isystem
> /usr/include/webp -isystem /<>/extern/quickhull -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++17 -Wall -Wextra -MD -MT
> CMakeFiles/therion-common.dir/thtexfonts.cxx.o -MF
> CMakeFiles/therion-common.dir/thtexfonts.cxx.o.d -o
> CMakeFiles/therion-common.dir/thtexfonts.cxx.o -c
> /<>/thtexfonts.cxx
> > [117/168] /usr/bin/c++ -DFMT_SHARED -DIMG_API_VERSION=1 -DPROJ_VER=9
> -DTHLINUX -I/<>/build -I/<> -isystem
> /usr/include/webp -isystem /<>/extern/quickhull -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++17 -Wall -Wextra -MD -MT
> CMakeFiles/therion-common.dir/thpdf.cxx.o -MF
> CMakeFiles/therion-common.dir/thpdf.cxx.o.d -o
> CMakeFiles/therion-common.dir/thpdf.cxx.o -c /<>/thpdf.cxx
> > [118/168] /usr/bin/c++ -DFMT_SHARED -DIMG_API_VERSION=1 -DPROJ_VER=9
> -DTHLINUX -I/<>/build -I/<> -isystem
> /usr/include/webp -isystem /<>/extern/quickhull -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++17 -Wall -Wextra -MD -MT
> CMakeFiles/therion-common.dir/thwarpp.cxx.o -MF
> CMakeFiles/therion-common.dir/thwarpp.cxx.o.d -o
> CMakeFiles/therion-common.dir/thwarpp.cxx.o -c /<>/thwarpp.cxx
> > [119/168] /usr/bin/c++ -DFMT_SHARED -DIMG_API_VERSION=1 -DPROJ_VER=9
> -DTHLINUX -I/<>/build -I/<> -isystem
> /usr/include/webp -isystem /<>/extern/quickhull -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++17 -Wall -Wextra -MD -MT
> CMakeFiles/therion-common.dir/thsymbolset.cxx.o -MF
> CMakeFiles/therion-common.dir/thsymbolset.cxx.o.d -o
> CMakeFiles/therion-common.dir/thsymbolset.cxx.o -c
> /<>/thsymbolset.cxx
> > ninja: build stopped: subcommand failed.
> > dh_auto_build: error: cd build && LC_ALL=C.UTF-8 ninja -j8 -v returned
> exit code 1
> > make[1]: *** [debian/rules:33:

Processed: reopen 1042597

2023-10-31 Thread Debian Bug Tracking System

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

> reopen 1042597
Bug #1042597 {Done: Thomas Goirand } [src:python-amqp] 
python-amqp: FTBFS with Sphinx 7.1, docutils 0.20: make[1]: *** 
[debian/rules:20: override_dh_sphinxdoc] Error 2
Bug reopened
Ignoring request to alter fixed versions of bug #1042597 to the same values 
previously set
>
End of message, stopping processing here.

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

Bug#1042706: marked as pending in kombu

2023-10-31 Thread Michael Fladischer

Control: tag -1 pending

Hello,

Bug #1042706 in kombu 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/python-team/packages/kombu/-/commit/10aa991ff996dd54298e9b32fb7834b4ce7b8777


Add patch to satisfy assinine sphinx 7.x parsing logic for copyright year 
substitution (Closes: #1042706).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1042706

Processed: Bug#1042706 marked as pending in kombu

2023-10-31 Thread Debian Bug Tracking System

Processing control commands:

> tag -1 pending
Bug #1042706 [src:kombu] kombu: FTBFS with Sphinx 7.1, docutils 0.20: make[1]: 
*** [debian/rules:13: override_dh_sphinxdoc] Error 2
Added tag(s) pending.

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

Bug#1030129: marked as done (ca-certificates-java - Fails to install: Error loading java.security file)

2023-10-31 Thread Debian Bug Tracking System

Your message dated Tue, 31 Oct 2023 13:22:10 +
with message-id 
and subject line Re: ca-certificates-java - Fails to install: Error loading 
java.security file
has caused the Debian Bug report #1030129,
regarding ca-certificates-java - Fails to install: Error loading java.security 
file
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.)


-- 
1030129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030129
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ca-certificates-java
Version: 20230103
Severity: serious

ca-certificates-java fails to install with all dependencies fullfilled:

| Setting up ca-certificates-java (20230103) ...
| Exception in thread "main" java.lang.InternalError: Error loading 
java.security file
|   at java.base/java.security.Security.initialize(Security.java:105)
|   at java.base/java.security.Security.lambda$static$0(Security.java:84)
|   at 
java.base/java.security.AccessController.doPrivileged(AccessController.java:319)
|   at java.base/java.security.Security.(Security.java:83)
|   at java.base/sun.security.jca.ProviderList.(ProviderList.java:179)
|   at java.base/sun.security.jca.ProviderList$2.run(ProviderList.java:96)
|   at java.base/sun.security.jca.ProviderList$2.run(ProviderList.java:94)
|   at 
java.base/java.security.AccessController.doPrivileged(AccessController.java:319)
|   at 
java.base/sun.security.jca.ProviderList.fromSecurityProperties(ProviderList.java:93)
|   at java.base/sun.security.jca.Providers.(Providers.java:55)
|   at 
java.base/sun.security.jca.GetInstance.getInstance(GetInstance.java:156)
|   at 
java.base/java.security.cert.CertificateFactory.getInstance(CertificateFactory.java:193)
|   at org.debian.security.KeyStoreHandler.(KeyStoreHandler.java:50)
|   at 
org.debian.security.UpdateCertificates.(UpdateCertificates.java:65)
|   at 
org.debian.security.UpdateCertificates.main(UpdateCertificates.java:51)
| dpkg: error processing package ca-certificates-java (--configure):
|  installed ca-certificates-java package post-installation script subprocess 
returned error exit status 1
| dpkg: dependency problems prevent configuration of 
openjdk-21-jre-headless:arm64:
|  openjdk-21-jre-headless:arm64 depends on ca-certificates-java (>= 
20190405~); however:
|   Package ca-certificates-java is not configured yet.
| 
| dpkg: error processing package openjdk-21-jre-headless:arm64 (--configure):
|  dependency problems - leaving unconfigured
| dpkg: dependency problems prevent configuration of openjdk-21-jre:arm64:
|  openjdk-21-jre:arm64 depends on openjdk-21-jre-headless (= 21~7ea-1); 
however:
|   Package openjdk-21-jre-headless:arm64 is not configured yet.
| 
| dpkg: error processing package openjdk-21-jre:arm64 (--configure):
|  dependency problems - leaving unconfigured
| dpkg: dependency problems prevent configuration of 
openjdk-21-jdk-headless:arm64:
|  openjdk-21-jdk-headless:arm64 depends on openjdk-21-jre-headless (= 
21~7ea-1); however:
|   Package openjdk-21-jre-headless:arm64 is not configured yet.
| 
| dpkg: error processing package openjdk-21-jdk-headless:arm64 (--configure):
|  dependency problems - leaving unconfigured
| dpkg: dependency problems prevent configuration of openjdk-21-jdk:arm64:
|  openjdk-21-jdk:arm64 depends on openjdk-21-jre (= 21~7ea-1); however:
|   Package openjdk-21-jre:arm64 is not configured yet.
|  openjdk-21-jdk:arm64 depends on openjdk-21-jdk-headless (= 21~7ea-1); 
however:
|   Package openjdk-21-jdk-headless:arm64 is not configured yet.
| 
| dpkg: error processing package openjdk-21-jdk:arm64 (--configure):
|  dependency problems - leaving unconfigured
--- End Message ---
--- Begin Message ---

Version: 20230620~deb12u1

Hi,

I can reproduce this issue reliably using a snapshot of bookworm from 
2023-09-01 (i.e. Debian 12.0) and installing openjdk-17-jre into a fresh 
chroot. It has to be that package, the headless variant does not seem to 
trigger the issue so it seems to be related to package installation 
ordering.


I cannot reproduce it in a Debian 12.1 chroot as shipped later that 
month. Therefore, it seems solved by the stable version of 
ca-certificates-java and I'm marking this bug as so, although I am not 
the maintainer.


Hopefully that means we can all have Nice Things again now.

Thanks,

--
Jonathan Wiltshire MBCS
Operations Manager

Tiger Computing Ltd
ISO27001:2017 Certified

Tel: 01600 483 484
Web: http://www.tiger-computing.co.uk

Registered in England. Company number: 3389961
Registered address: Woodlands,

Bug#1055099: rust-async-task: Failing autopkgtests

2023-10-31 Thread Jeremy Bícha

Source: rust-async-task
Version: 4.5.0-1
Severity: serious

The autopkgtests for rust-async-task began failing after the upgrade
to from 4.4.1-1 to 4.5.0-1. This prevents its migration to Testing.

https://ci.debian.net/packages/r/rust-async-task/testing/amd64/

Autopkgtest log excerpt
--
showing two different errors:

157s error[E0425]: cannot find function `spawn_local` in crate `async_task`
157s   --> examples/spawn-local.rs:22:40
157s|
157s 22 | let (runnable, task) = async_task::spawn_local(future, schedule);
157s|^^^ not found
in `async_task`
157s
157s error[E0554]: `#![feature]` may not be used on the stable release channel
157s  --> benches/spawn.rs:1:12
157s   |
157s 1 | #![feature(test)]
157s   |
157s
157s For more information about this error, try `rustc --explain E0554`.
157s error: could not compile `async-task` due to previous error


Thank you,
Jeremy Bícha

Bug#1053310: Fixes for stable/oldstable?

2023-10-31 Thread Tomas Pospisek


Hi Salvatore,

thanks a lot for your reply (more below):

On Tue, 31 Oct 2023, Salvatore Bonaccorso wrote:


Hi Tomas,

On Tue, Oct 31, 2023 at 11:07:06AM +0100, Tomas Pospisek wrote:

Hello Exim maintainers,

this ticket, asking for packages with fixes for CVE-2023-42117 and other
security relavant issues is closed.

However only a package for unstable has been released:

https://security-tracker.debian.org/tracker/CVE-2023-42117

all other Debian releases (stable, oldstable) still seem to be carrying the
vulnerable Exim4 version.

What is the status of releasing fixed Exims for Debian stable, oldstable? Is
anybody working on it? Is help needed?


Fixes for CVE-2023-42117 and CVE-2023-42119 are right now considered
no-dsa (see comment on the security-tracker about it), and are going
to be fixed in the next point releases.


The notes say:

***
[bookworm] - exim4  (Only an issue if Exim4 run behind an
 untrusted proxy-protocol proxy)
[bullseye] - exim4  (Only an issue if Exim4 run behind an
 untrusted proxy-protocol proxy)
[buster] - exim4  (Only an issue if Exim4 run behind an untrusted
   proxy-protocol proxy)
https://www.zerodayinitiative.com/advisories/ZDI-23-1471/
https://bugs.exim.org/show_bug.cgi?id=3031
https://www.openwall.com/lists/oss-security/2023/09/29/5
https://www.openwall.com/lists/oss-security/2023/10/01/4
https://exim.org/static/doc/security/CVE-2023-zdi.txt
***

So I think I can parse from those that CVE-2023-42117 is only critical 
when exim is run behind a "untrusted proxy-protocol proxy".


Questions if you will:

* what does "no-dsa" mean? DSA seems to mean Debian Security Announce.
  Does it mean there is no DSA for that problem yet? What does it mean
  when a CVE is considered "no-dsa" then? That no DSA will be released for
  it?
* what is a "untrusted proxy-protocol proxy" in the context of a mail
  transport agent? So exim shouldn't be used behind an untrusted socks
  proxy? Well I have no real control who connects how to a public MTA...
  anybody can connect to it to try his luck sending me email. That
  includes untrusted socks proxies...

So to wrap I it /seems/ that I'm probably fine, however the details are so 
terse that my assessement seems to be rather shaky...



Does this help?


A bit. Thanks a lot

Best greetings!
*t

Bug#1042597: marked as done (python-amqp: FTBFS with Sphinx 7.1, docutils 0.20: make[1]: *** [debian/rules:20: override_dh_sphinxdoc] Error 2)

2023-10-31 Thread Debian Bug Tracking System

Your message dated Tue, 31 Oct 2023 13:03:35 +0100
with message-id 
and subject line Package builds fine
has caused the Debian Bug report #1042597,
regarding python-amqp: FTBFS with Sphinx 7.1, docutils 0.20: make[1]: *** 
[debian/rules:20: override_dh_sphinxdoc] Error 2
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.)


-- 
1042597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042597
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-amqp
Version: 5.1.1-1
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx7.1

Hi,

python-amqp 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 '/<>'
> PYTHONPATH=. python3 -m sphinx -D today="September 27, 2022" -b html -N docs/ 
> /<>/debian/python-amqp-doc/usr/share/doc/python-amqp-doc/html
> Running Sphinx v7.1.1
> making output directory... done
> 
> Extension error (sphinx.config):
> Handler  for event 
> 'config-inited' threw an exception (exception: string index out of range)
> make[1]: *** [debian/rules:20: override_dh_sphinxdoc] Error 2


The full build log is available from:
http://qa-logs.debian.net/2023/07/30/exp/python-amqp_5.1.1-1_unstable_sphinx-exp.log

Please see [1] for Sphinx changelog and [2] for Docutils changelog.

Also see [3] for the list of deprecated/removed APIs in Sphinx and possible
alternatives to them.

Some notable changes in Sphinx 6 and Sphinx 7:

- Sphinx no longer includes jquery.js and underscore.js by default.
  Please use python3-sphinxcontrib.jquery package if you are using a custom
  template and it still needs jquery.

- The setup.py build_sphinx command was removed. Please instead call
  sphinx-build or "python3 -m sphinx" directly.

- For packages using the extlinks extension, the caption should contain
  exactly one "%s" placeholder (if caption is not None).

In case you have questions, please Cc sph...@packages.debian.org on reply.

[1]: https://www.sphinx-doc.org/en/master/changes.html
[2]: 
https://repo.or.cz/docutils.git/blob/refs/tags/docutils-0.20.1:/RELEASE-NOTES.txt
[3]: 
https://www.sphinx-doc.org/en/master/extdev/deprecated.html#dev-deprecated-apis

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=sphinx7.1;users=python-modules-t...@lists.alioth.debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=sphinx7.1=python-modules-t...@lists.alioth.debian.org=1=1=1=1#results

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

I tried building this package, and it's working well, closing this bug.

Cheers,

Thomas Goirand (zigo)--- End Message ---

Bug#1053310: Fixes for stable/oldstable?

2023-10-31 Thread Salvatore Bonaccorso

Hi Tomas,

On Tue, Oct 31, 2023 at 11:07:06AM +0100, Tomas Pospisek wrote:
> Hello Exim maintainers,
> 
> this ticket, asking for packages with fixes for CVE-2023-42117 and other
> security relavant issues is closed.
> 
> However only a package for unstable has been released:
> 
> https://security-tracker.debian.org/tracker/CVE-2023-42117
> 
> all other Debian releases (stable, oldstable) still seem to be carrying the
> vulnerable Exim4 version.
> 
> What is the status of releasing fixed Exims for Debian stable, oldstable? Is
> anybody working on it? Is help needed?

Fixes for CVE-2023-42117 and CVE-2023-42119 are right now considered
no-dsa (see comment on the security-tracker about it), and are going
to be fixed in the next point releases.

Does this help?

Regards,
Salvatore

Bug#1053310: Fixes for stable/oldstable?

2023-10-31 Thread Tomas Pospisek


Hello Exim maintainers,

this ticket, asking for packages with fixes for CVE-2023-42117 and other 
security relavant issues is closed.


However only a package for unstable has been released:

https://security-tracker.debian.org/tracker/CVE-2023-42117

all other Debian releases (stable, oldstable) still seem to be carrying 
the vulnerable Exim4 version.


What is the status of releasing fixed Exims for Debian stable, oldstable? 
Is anybody working on it? Is help needed?

*t

PS: I'd prefer this bugreport to be open as long as the stable and
oldstable packages are still vulnerable...

Processed: affects 1050236

2023-10-31 Thread Debian Bug Tracking System

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

> affects 1050236 src:php-imagick
Bug #1050236 [inkscape] inkscape: FTBFS: 30 - test_lpe (Failed)
Added indication that 1050236 affects src:php-imagick
> thanks
Stopping processing here.

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

Processed: affects 1050236

2023-10-31 Thread Debian Bug Tracking System

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

> affects 1050236 imagemagick
Bug #1050236 [inkscape] inkscape: FTBFS: 30 - test_lpe (Failed)
Added indication that 1050236 affects imagemagick
> thanks
Stopping processing here.

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

Bug#1054673: marked as done (olm: FTBFS: emcc: error: '/usr/bin/clang++-14 -target wasm32-unknown-emscripten -DEMSCRIPTEN -D__EMSCRIPTEN_major=3 -DEMSCRIPTEN_minor=1 -DEMSCRIPTEN_tiny__=6 -fig

2023-10-31 Thread Debian Bug Tracking System

Your message dated Tue, 31 Oct 2023 10:04:37 +
with message-id 
and subject line Bug#1054673: fixed in olm 3.2.15~dfsg-1
has caused the Debian Bug report #1054673,
regarding olm: FTBFS: emcc: error: '/usr/bin/clang++-14 -target 
wasm32-unknown-emscripten -DEMSCRIPTEN -D__EMSCRIPTEN_major__=3 
-D__EMSCRIPTEN_minor__=1 -D__EMSCRIPTEN_tiny__=6 -fignore-exceptions 
-fvisibility=default -mllvm -combiner-global-alias-analysis=false -mllvm 
-enable-emscripten-sjlj -mllvm -disable-lsr -D_LIBCPP_ABI_VERSION=2 
-fno-threadsafe-statics -Dunix -D__unix -D__unix__ 
-Werror=implicit-function-declaration -Xclang -iwithsysroot/include/SDL 
--sysroot=/usr/share/emscripten/cache/sysroot -Xclang 
-iwithsysroot/include/compat -O2 -ffile-prefix-map=/<>=. 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall 
-Werror -std=c++11 -O3 -Wdate-time -D_FORTIFY_SOURCE=2 -Iinclude -Ilib 
-DOLMLIB_VERSION_MAJOR=3 -DOLMLIB_VERSION_MINOR=2 -DOLMLIB_VERSION_PATCH=13 
-MMD -c -DNDEBUG -DOLM_STATIC_DEFINE=1 src/account.cpp -o 
build/javascript/src/account.o' failed (returned 1)
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.)


-- 
1054673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054673
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: olm
Version: 3.2.13~dfsg-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> mkdir -p build/javascript/src/
> mkdir -p build/javascript/src/
> mkdir -p build/javascript/src/
> mkdir -p build/javascript/src/
> mkdir -p build/javascript/src/
> emcc -O2 -ffile-prefix-map=/<>=. -fstack-clash-protection 
> -Wformat -Werror=format-security -fcf-protection -Wall -Werror -std=c++11 -O3 
> -Wdate-time -D_FORTIFY_SOURCE=2 -Iinclude -Ilib -DOLMLIB_VERSION_MAJOR=3 
> -DOLMLIB_VERSION_MINOR=2 -DOLMLIB_VERSION_PATCH=13 -MMD -c -DNDEBUG 
> -DOLM_STATIC_DEFINE=1 -o build/javascript/src/account.o src/account.cpp
> emcc -O2 -ffile-prefix-map=/<>=. -fstack-clash-protection 
> -Wformat -Werror=format-security -fcf-protection -Wall -Werror -std=c++11 -O3 
> -Wdate-time -D_FORTIFY_SOURCE=2 -Iinclude -Ilib -DOLMLIB_VERSION_MAJOR=3 
> -DOLMLIB_VERSION_MINOR=2 -DOLMLIB_VERSION_PATCH=13 -MMD -c -DNDEBUG 
> -DOLM_STATIC_DEFINE=1 -o build/javascript/src/base64.o src/base64.cpp
> emcc -O2 -ffile-prefix-map=/<>=. -fstack-clash-protection 
> -Wformat -Werror=format-security -fcf-protection -Wall -Werror -std=c++11 -O3 
> -Wdate-time -D_FORTIFY_SOURCE=2 -Iinclude -Ilib -DOLMLIB_VERSION_MAJOR=3 
> -DOLMLIB_VERSION_MINOR=2 -DOLMLIB_VERSION_PATCH=13 -MMD -c -DNDEBUG 
> -DOLM_STATIC_DEFINE=1 -o build/javascript/src/cipher.o src/cipher.cpp
> emcc -O2 -ffile-prefix-map=/<>=. -fstack-clash-protection 
> -Wformat -Werror=format-security -fcf-protection -Wall -Werror -std=c++11 -O3 
> -Wdate-time -D_FORTIFY_SOURCE=2 -Iinclude -Ilib -DOLMLIB_VERSION_MAJOR=3 
> -DOLMLIB_VERSION_MINOR=2 -DOLMLIB_VERSION_PATCH=13 -MMD -c -DNDEBUG 
> -DOLM_STATIC_DEFINE=1 -o build/javascript/src/crypto.o src/crypto.cpp
> emcc -O2 -ffile-prefix-map=/<>=. -fstack-clash-protection 
> -Wformat -Werror=format-security -fcf-protection -Wall -Werror -std=c++11 -O3 
> -Wdate-time -D_FORTIFY_SOURCE=2 -Iinclude -Ilib -DOLMLIB_VERSION_MAJOR=3 
> -DOLMLIB_VERSION_MINOR=2 -DOLMLIB_VERSION_PATCH=13 -MMD -c -DNDEBUG 
> -DOLM_STATIC_DEFINE=1 -o build/javascript/src/memory.o src/memory.cpp
> mkdir -p build/javascript/src/
> mkdir -p build/javascript/src/
> mkdir -p build/javascript/src/
> emcc -O2 -ffile-prefix-map=/<>=. -fstack-clash-protection 
> -Wformat -Werror=format-security -fcf-protection -Wall -Werror -std=c++11 -O3 
> -Wdate-time -D_FORTIFY_SOURCE=2 -Iinclude -Ilib -DOLMLIB_VERSION_MAJOR=3 
> -DOLMLIB_VERSION_MINOR=2 -DOLMLIB_VERSION_PATCH=13 -MMD -c -DNDEBUG 
> -DOLM_STATIC_DEFINE=1 -o build/javascript/src/message.o src/message.cpp
> emcc -O2 -ffile-prefix-map=/<>=. -fstack-clash-protection 
> -Wformat -Werror=format-security -fcf-protection -Wall -Werror -std=c++11 -O3 
> -Wdate-time -D_FORTIFY_SOURCE=2 -Iinclude -Ilib -DOLMLIB_VERSION_MAJOR=3 
> -DOLMLIB_VERSION_MINOR=2 -DOLMLIB_VERSION_PATCH=13 -MMD -c -DNDEBUG 
> -DOLM_STATIC_DEFINE=1 -o build/javascript/src/olm.o src/olm.cpp
> emcc -O2 -ffile-prefix-map=/<>=. -fstack-clash-protection 
> -Wformat -Werror=format-security -fcf-protection -Wall -Werror -std=c++11 -O3 
> -Wdate-time -D_FORTIFY_SOURCE=2 -Iinclude -Ilib -DOLMLIB_VERSION_MAJOR=3

Processed: Re: Bug#1055066: usrmerge: Cannot update to version 38 on sbuild

2023-10-31 Thread Debian Bug Tracking System

Processing control commands:

> fixed -1 1.0.133
Bug #1055066 [src:debootstrap] usrmerge: Cannot update to version 38 on sbuild
Marked as fixed in versions debootstrap/1.0.133.
> fixed -1 1.0.128+nmu2+deb12u1
Bug #1055066 [src:debootstrap] usrmerge: Cannot update to version 38 on sbuild
Marked as fixed in versions debootstrap/1.0.128+nmu2+deb12u1.
> fixed -1 1.0.123+deb11u2
Bug #1055066 [src:debootstrap] usrmerge: Cannot update to version 38 on sbuild
Marked as fixed in versions debootstrap/1.0.123+deb11u2.
> close -1
Bug #1055066 [src:debootstrap] usrmerge: Cannot update to version 38 on sbuild
Marked Bug as done

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

Bug#1055066: usrmerge: Cannot update to version 38 on sbuild

2023-10-31 Thread Luca Boccassi

Control: fixed -1 1.0.133
Control: fixed -1 1.0.128+nmu2+deb12u1
Control: fixed -1 1.0.123+deb11u2
Control: close -1

On Tue, 31 Oct 2023 at 08:02, John Paul Adrian Glaubitz
 wrote:
>
> Hello!
>
> I am not sure whether this issue has been fixed.
>
> We're seeing this issue on buildds and porterboxes on Debian Ports,
> regenerating the chroots fails:
>
> dpkg: warning: ignoring pre-dependency problem!
> Preparing to unpack .../tar_1.34+dfsg-1.2_ppc64.deb ...
> Unpacking tar (1.34+dfsg-1.2) ...
> Selecting previously unselected package usr-is-merged.
> Preparing to unpack .../usr-is-merged_38_all.deb ...
>
>
> **
> *
> * The usr-is-merged package cannot be installed because this system does
> * not have a merged /usr.
> *
> * Please install the usrmerge package to convert this system to merged-/usr.
> *
> * For more information please read https://wiki.debian.org/UsrMerge.
> *
> **
>
>
> dpkg: error processing archive 
> /var/cache/apt/archives/usr-is-merged_38_all.deb (--unpack):
>  new usr-is-merged package pre-installation script subprocess returned error 
> exit status 1
> Selecting previously unselected package util-linux.
> dpkg: regarding .../util-linux_2.39.2-5_ppc64.deb containing util-linux, 
> pre-dependency problem:
>  util-linux pre-depends on libblkid1 (>= 2.37.2)
>   libblkid1:ppc64 is unpacked, but has never been configured.
>
> Could it be that debootstrap needs to be switched to enabled usrmerge by 
> default?

The buildds have already been updated with a new config ~3 weeks ago:

https://lists.debian.org/debian-devel/2023/10/msg00019.html
https://lists.debian.org/debian-devel/2023/10/msg00024.html

Are the ports buildds managed differently? If so, they either need
that change, or to take debootstrap from proposed-updates where the
defaults have been switched. There is nothing actionable in
debootstrap, as the relevant changes have already been made and
uploaded (pending the next stable release to make it out of p-u).

Bug#1054666: open-vm-tools: CVE-2023-34059 CVE-2023-34058

2023-10-31 Thread Bernd Zeimetz

On Mon, 2023-10-30 at 22:50 +0100, Moritz Muehlenhoff wrote:
> On Mon, Oct 30, 2023 at 07:09:53PM +0100, Bernd Zeimetz wrote:
> > Hi Moritz,
> > 
> > as usual, stable/oldstable updates prepared, diffs are attached to
> > this
> > mail as salsa seems to have some issues right now.
> > 
> > https://salsa.debian.org/vmware-packaging-team/pkg-open-vm-tools/ -
> > bookworm/bullseye branches are actually there.
> > 
> > Please let me know if/when I can upload.
> 
> Thanks, these look fine, please upload to security-master.
> 

Both uploaded!

Thanks,

Bernd


-- 
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F

Bug#1042639: marked as done (celery: FTBFS with Sphinx 7.1, docutils 0.20: make[1]: *** [debian/rules:21: override_dh_sphinxdoc] Error 2)

2023-10-31 Thread Debian Bug Tracking System

Your message dated Tue, 31 Oct 2023 09:19:15 +
with message-id 
and subject line Bug#1042639: fixed in celery 5.3.4-2
has caused the Debian Bug report #1042639,
regarding celery: FTBFS with Sphinx 7.1, docutils 0.20: make[1]: *** 
[debian/rules:21: override_dh_sphinxdoc] Error 2
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.)


-- 
1042639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042639
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: celery
Version: 5.3.1-1
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx7.1

Hi,

celery 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 '/<>'
> PYTHONPATH=. python3 -m sphinx -b html -d docs/.build/.doctrees -N docs 
> /<>/debian/python-celery-doc/usr/share/doc/python-celery-doc/html
> Running Sphinx v7.1.1
> making output directory... done
> 
> Extension error (sphinx.config):
> Handler  for event 
> 'config-inited' threw an exception (exception: string index out of range)
> make[1]: *** [debian/rules:21: override_dh_sphinxdoc] Error 2


The full build log is available from:
http://qa-logs.debian.net/2023/07/30/exp/celery_5.3.1-1_unstable_sphinx-exp.log

Please see [1] for Sphinx changelog and [2] for Docutils changelog.

Also see [3] for the list of deprecated/removed APIs in Sphinx and possible
alternatives to them.

Some notable changes in Sphinx 6 and Sphinx 7:

- Sphinx no longer includes jquery.js and underscore.js by default.
  Please use python3-sphinxcontrib.jquery package if you are using a custom
  template and it still needs jquery.

- The setup.py build_sphinx command was removed. Please instead call
  sphinx-build or "python3 -m sphinx" directly.

- For packages using the extlinks extension, the caption should contain
  exactly one "%s" placeholder (if caption is not None).

In case you have questions, please Cc sph...@packages.debian.org on reply.

[1]: https://www.sphinx-doc.org/en/master/changes.html
[2]: 
https://repo.or.cz/docutils.git/blob/refs/tags/docutils-0.20.1:/RELEASE-NOTES.txt
[3]: 
https://www.sphinx-doc.org/en/master/extdev/deprecated.html#dev-deprecated-apis

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=sphinx7.1;users=python-modules-t...@lists.alioth.debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=sphinx7.1=python-modules-t...@lists.alioth.debian.org=1=1=1=1#results

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
--- End Message ---
--- Begin Message ---
Source: celery
Source-Version: 5.3.4-2
Done: Michael Fladischer 

We believe that the bug you reported is fixed in the latest version of
celery, 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.
Michael Fladischer  (supplier of updated celery 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: Tue, 31 Oct 2023 08:28:14 +
Source: celery
Architecture: source
Version: 5.3.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Michael Fladischer 
Closes: 1042639
Changes:
 celery (5.3.4-2) unstable; urgency=medium
 .
   * Add patch to satisfy assinine sphinx 7.x parsing logic for copyright year
 substitution (Closes: #1042639).
Checksums-Sha1:
 e8ea0a1a9029b4c15d80b237c7fc4cba14d91224 2603 celery_5.3.4-2.dsc
 b9ffcd0b49200e3d06d33e29767fdcccaa06e334 23708 celery_5.3.4-2.debian.tar.xz
 a97b745bd6e5930e47147b1cbf26262f374953f1 13051 celery_5.3.4-2_arm64.buildinfo
Checksums-Sha256:
 3e736bcdfc0e5148f2f4827a265ce4e4d920399e49a807d9b0afb9dd7324f4b3 2603 
celery_5.3.4-2.dsc
 beb9860d017db16fe98d8f8dfa97d4a68044d5945204f63b95d38fc6a0c93ce3 23708 
celery_5.3.4-2.debian.tar.xz
 9cb3544ec3688234335483d4382ec7ee16c4df75aa69eabd356e9dc48fd254c9 13051 
celery_5.3.4-2_arm64.buildinfo
Files:
 a4e014872e7a8cf1e55db80dc3f5ea24 2603 python optional

Bug#1042115: marked as done (cross-toolchain-base-ports: FTBFS: build-dependency not installable: linux-source-6.3 (>= 6.3.7))

2023-10-31 Thread Debian Bug Tracking System

Your message dated Tue, 31 Oct 2023 09:19:29 +
with message-id 
and subject line Bug#1042115: fixed in cross-toolchain-base-ports 64
has caused the Debian Bug report #1042115,
regarding cross-toolchain-base-ports: FTBFS: build-dependency not installable: 
linux-source-6.3 (>= 6.3.7)
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.)


-- 
1042115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042115
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cross-toolchain-base-ports
Version: 63
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: binutils-multiarch, dpkg (>= 1.21.17), rdfind, 
> symlinks, lsb-release, binutils-source (>= 2.40.50.20230630-1~), glibc-source 
> (>= 2.37-3~), gcc-12-source (>= 12.3.0-5~), linux-source-6.3 (>= 6.3.7), 
> linux-libc-dev (>= 6.3.7), autoconf (>= 2.69), autoconf2.69, autogen, 
> automake, bison (>= 1:2.3), chrpath, debhelper-compat (= 13), dpkg-dev (>= 
> 1.15.3.1), fakeroot, file, flex, dwz, debugedit (>= 4.16), gawk, gettext, 
> gperf (>= 3.0.1), kernel-wedge (>= 2.24), libisl-dev, libmpc-dev, libelf-dev, 
> libmpfr-dev (>= 2.3.0), rsync, xmlto, libtool, lzma, m4, make (>= 3.81), kmod 
> | module-init-tools, patchutils, procps, quilt, coreutils (>= 2.26) | 
> realpath (>= 1.9.12), sed (>= 4.0.5-4), sharutils, tar (>= 1.22), xz-utils, 
> asciidoc, texinfo, cpio, python3, bc, time, libconfig-auto-perl, 
> libfile-temp-perl, libfile-homedir-perl, liblocale-gettext-perl, 
> libunwind-dev, libjansson-dev, pkg-config, build-essential, fakeroot
> Merged Build-Conflicts: binutils-alpha-linux-gnu, binutils-arc-linux-gnu, 
> binutils-hppa-linux-gnu, binutils-m68k-linux-gnu, binutils-powerpc-linux-gnu, 
> binutils-powerpc64-linux-gnu, binutils-riscv64-linux-gnu, 
> binutils-sh4-linux-gnu, binutils-sparc64-linux-gnu, 
> binutils-x86-64-linux-gnux32, dpkg-cross, libc6-alpha-cross, libc6-arc-cross, 
> libc6-hppa-cross, libc6-i386, libc6-m68k-cross, libc6-powerpc-cross, 
> libc6-ppc64-cross, libc6-riscv64-cross, libc6-sh4-cross, libc6-sparc64-cross, 
> libc6-x32, libc6-x32-cross, libdebian-dpkgcross-perl, 
> linux-libc-dev-alpha-cross, linux-libc-dev-arc-cross, 
> linux-libc-dev-hppa-cross, linux-libc-dev-m68k-cross, 
> linux-libc-dev-powerpc-cross, linux-libc-dev-ppc64-cross, 
> linux-libc-dev-riscv64-cross, linux-libc-dev-sh4-cross, 
> linux-libc-dev-sparc64-cross, linux-libc-dev-x32-cross
> Filtered Build-Depends: binutils-multiarch, dpkg (>= 1.21.17), rdfind, 
> symlinks, lsb-release, binutils-source (>= 2.40.50.20230630-1~), glibc-source 
> (>= 2.37-3~), gcc-12-source (>= 12.3.0-5~), linux-source-6.3 (>= 6.3.7), 
> linux-libc-dev (>= 6.3.7), autoconf (>= 2.69), autoconf2.69, autogen, 
> automake, bison (>= 1:2.3), chrpath, debhelper-compat (= 13), dpkg-dev (>= 
> 1.15.3.1), fakeroot, file, flex, dwz, debugedit (>= 4.16), gawk, gettext, 
> gperf (>= 3.0.1), kernel-wedge (>= 2.24), libisl-dev, libmpc-dev, libelf-dev, 
> libmpfr-dev (>= 2.3.0), rsync, xmlto, libtool, lzma, m4, make (>= 3.81), 
> kmod, patchutils, procps, quilt, coreutils (>= 2.26), sed (>= 4.0.5-4), 
> sharutils, tar (>= 1.22), xz-utils, asciidoc, texinfo, cpio, python3, bc, 
> time, libconfig-auto-perl, libfile-temp-perl, libfile-homedir-perl, 
> liblocale-gettext-perl, libunwind-dev, libjansson-dev, pkg-config, 
> build-essential, fakeroot
> Filtered Build-Conflicts: binutils-alpha-linux-gnu, binutils-arc-linux-gnu, 
> binutils-hppa-linux-gnu, binutils-m68k-linux-gnu, binutils-powerpc-linux-gnu, 
> binutils-powerpc64-linux-gnu, binutils-riscv64-linux-gnu, 
> binutils-sh4-linux-gnu, binutils-sparc64-linux-gnu, 
> binutils-x86-64-linux-gnux32, dpkg-cross, libc6-alpha-cross, libc6-arc-cross, 
> libc6-hppa-cross, libc6-i386, libc6-m68k-cross, libc6-powerpc-cross, 
> libc6-ppc64-cross, libc6-riscv64-cross, libc6-sh4-cross, libc6-sparc64-cross, 
> libc6-x32, libc6-x32-cross, libdebian-dpkgcross-perl, 
> linux-libc-dev-alpha-cross, linux-libc-dev-arc-cross, 
> linux-libc-dev-hppa-cross, linux-libc-dev-m68k-cross, 
> linux-libc-dev-powerpc-cross, linux-libc-dev-ppc64-cross, 
>

Bug#1042118: marked as done (cross-toolchain-base: FTBFS: build-dependency not installable: linux-source-6.3 (>= 6.3.7))

2023-10-31 Thread Debian Bug Tracking System

Your message dated Tue, 31 Oct 2023 09:19:22 +
with message-id 
and subject line Bug#1042118: fixed in cross-toolchain-base 68
has caused the Debian Bug report #1042118,
regarding cross-toolchain-base: FTBFS: build-dependency not installable: 
linux-source-6.3 (>= 6.3.7)
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.)


-- 
1042118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042118
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cross-toolchain-base
Version: 67
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: binutils-multiarch, dpkg (>= 1.21.17), rdfind, 
> symlinks, lsb-release, binutils-source (>= 2.40.50.20230630-1~), glibc-source 
> (>= 2.37-3~), gcc-12-source (>= 12.3.0-5~), linux-source-6.3 (>= 6.3.7), 
> linux-libc-dev (>= 6.3.7), autoconf (>= 2.69), autoconf2.69, autogen, 
> automake, bison (>= 1:2.3), chrpath, debhelper-compat (= 13), dpkg-dev (>= 
> 1.15.3.1), fakeroot, file, flex, dwz, debugedit (>= 4.16), gawk, gettext, 
> gperf (>= 3.0.1), kernel-wedge (>= 2.24), libisl-dev, libmpc-dev, libelf-dev, 
> libmpfr-dev (>= 2.3.0), rsync, xmlto, libtool, lzma, m4, make (>= 3.81), kmod 
> | module-init-tools, patchutils, procps, quilt, coreutils (>= 2.26) | 
> realpath (>= 1.9.12), sed (>= 4.0.5-4), sharutils, tar (>= 1.22), xz-utils, 
> asciidoc, texinfo, cpio, python3, bc, time, libconfig-auto-perl, 
> libfile-temp-perl, libfile-homedir-perl, liblocale-gettext-perl, 
> libunwind-dev, libjansson-dev, pkg-config, build-essential, fakeroot
> Merged Build-Conflicts: binutils-aarch64-linux-gnu, 
> binutils-arm-linux-gnueabi, binutils-arm-linux-gnueabihf, 
> binutils-i686-linux-gnu, binutils-powerpc64le-linux-gnu, 
> binutils-s390x-linux-gnu, dpkg-cross, libc6-amd64-cross, libc6-arm64-cross, 
> libc6-armel-cross, libc6-armhf-cross, libc6-i386, libc6-i386-cross, 
> libc6-ppc64el-cross, libc6-s390x-cross, libc6-x32, libdebian-dpkgcross-perl, 
> linux-libc-dev-amd64-cross, linux-libc-dev-arm64-cross, 
> linux-libc-dev-armel-cross, linux-libc-dev-armhf-cross, 
> linux-libc-dev-i386-cross, linux-libc-dev-ppc64el-cross, 
> linux-libc-dev-s390x-cross
> Filtered Build-Depends: binutils-multiarch, dpkg (>= 1.21.17), rdfind, 
> symlinks, lsb-release, binutils-source (>= 2.40.50.20230630-1~), glibc-source 
> (>= 2.37-3~), gcc-12-source (>= 12.3.0-5~), linux-source-6.3 (>= 6.3.7), 
> linux-libc-dev (>= 6.3.7), autoconf (>= 2.69), autoconf2.69, autogen, 
> automake, bison (>= 1:2.3), chrpath, debhelper-compat (= 13), dpkg-dev (>= 
> 1.15.3.1), fakeroot, file, flex, dwz, debugedit (>= 4.16), gawk, gettext, 
> gperf (>= 3.0.1), kernel-wedge (>= 2.24), libisl-dev, libmpc-dev, libelf-dev, 
> libmpfr-dev (>= 2.3.0), rsync, xmlto, libtool, lzma, m4, make (>= 3.81), 
> kmod, patchutils, procps, quilt, coreutils (>= 2.26), sed (>= 4.0.5-4), 
> sharutils, tar (>= 1.22), xz-utils, asciidoc, texinfo, cpio, python3, bc, 
> time, libconfig-auto-perl, libfile-temp-perl, libfile-homedir-perl, 
> liblocale-gettext-perl, libunwind-dev, libjansson-dev, pkg-config, 
> build-essential, fakeroot
> Filtered Build-Conflicts: binutils-aarch64-linux-gnu, 
> binutils-arm-linux-gnueabi, binutils-arm-linux-gnueabihf, 
> binutils-i686-linux-gnu, binutils-powerpc64le-linux-gnu, 
> binutils-s390x-linux-gnu, dpkg-cross, libc6-amd64-cross, libc6-arm64-cross, 
> libc6-armel-cross, libc6-armhf-cross, libc6-i386, libc6-i386-cross, 
> libc6-ppc64el-cross, libc6-s390x-cross, libc6-x32, libdebian-dpkgcross-perl, 
> linux-libc-dev-amd64-cross, linux-libc-dev-arm64-cross, 
> linux-libc-dev-armel-cross, linux-libc-dev-armhf-cross, 
> linux-libc-dev-i386-cross, linux-libc-dev-ppc64el-cross, 
> linux-libc-dev-s390x-cross
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [993 B]
> Get:5 copy:/<>/apt_archive ./ Packages [994 B]
> Fetched 2950 B in 0s (245 kB/s)
> Reading package

Processed: Bug#1042639 marked as pending in celery

2023-10-31 Thread Debian Bug Tracking System

Processing control commands:

> tag -1 pending
Bug #1042639 [src:celery] celery: FTBFS with Sphinx 7.1, docutils 0.20: 
make[1]: *** [debian/rules:21: override_dh_sphinxdoc] Error 2
Added tag(s) pending.

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

Bug#1042639: marked as pending in celery

2023-10-31 Thread Michael Fladischer

Control: tag -1 pending

Hello,

Bug #1042639 in celery 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/python-team/packages/celery/-/commit/f33e3dbb23b37fefecb6a2199320a1a18d710a26


Add patch to satisfy assinine sphinx 7.x parsing logic for copyright year 
substitution (Closes: #1042639).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1042639

Bug#1054763: marked as done (openmm: FTBFS: make[1]: *** [debian/rules:38: override_dh_auto_test] Error 2)

2023-10-31 Thread Debian Bug Tracking System

Your message dated Tue, 31 Oct 2023 08:26:10 +
with message-id 
and subject line Bug#1054763: fixed in openmm 8.0.0+dfsg-3
has caused the Debian Bug report #1054763,
regarding openmm: FTBFS: make[1]: *** [debian/rules:38: override_dh_auto_test] 
Error 2
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.)


-- 
1054763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054763
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openmm
Version: 8.0.0+dfsg-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
> Running tests...
> /usr/bin/ctest --force-new-ctest-process --verbose -j8
> UpdateCTestConfiguration  from 
> :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl
> Parse Config file:/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl
> UpdateCTestConfiguration  from 
> :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl
> Parse Config file:/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl
> Test project /<>/obj-x86_64-linux-gnu
> Constructing a list of tests
> Done constructing a list of tests
> Updating test list for fixtures
> Added 0 tests to meet fixture requirements
> Checking test dependency graph...
> Checking test dependency graph end
> test 1
> Start   1: TestReferenceAndersenThermostat
> 
> 1: Test command: 
> /<>/obj-x86_64-linux-gnu/TestReferenceAndersenThermostat
> 1: Working Directory: 
> /<>/obj-x86_64-linux-gnu/platforms/reference/tests
> 1: Test timeout computed to be: 1500
> test 2
> Start   2: TestReferenceBrownianIntegrator
> 
> 2: Test command: 
> /<>/obj-x86_64-linux-gnu/TestReferenceBrownianIntegrator
> 2: Working Directory: 
> /<>/obj-x86_64-linux-gnu/platforms/reference/tests
> 2: Test timeout computed to be: 1500
> test 3
> Start   3: TestReferenceCMAPTorsionForce
> 
> 3: Test command: 
> /<>/obj-x86_64-linux-gnu/TestReferenceCMAPTorsionForce
> 3: Working Directory: 
> /<>/obj-x86_64-linux-gnu/platforms/reference/tests
> 3: Test timeout computed to be: 1500
> test 4
> Start   4: TestReferenceCMMotionRemover
> 
> 4: Test command: 
> /<>/obj-x86_64-linux-gnu/TestReferenceCMMotionRemover
> 4: Working Directory: 
> /<>/obj-x86_64-linux-gnu/platforms/reference/tests
> 4: Test timeout computed to be: 1500
> test 5
> Start   5: TestReferenceCheckpoints
> 
> 5: Test command: 
> /<>/obj-x86_64-linux-gnu/TestReferenceCheckpoints
> 5: Working Directory: 
> /<>/obj-x86_64-linux-gnu/platforms/reference/tests
> 5: Test timeout computed to be: 1500
> test 6
> Start   6: TestReferenceCompoundIntegrator
> 
> 6: Test command: 
> /<>/obj-x86_64-linux-gnu/TestReferenceCompoundIntegrator
> 6: Working Directory: 
> /<>/obj-x86_64-linux-gnu/platforms/reference/tests
> 6: Test timeout computed to be: 1500
> test 7
> Start   7: TestReferenceCustomAngleForce
> 
> 7: Test command: 
> /<>/obj-x86_64-linux-gnu/TestReferenceCustomAngleForce
> 7: Working Directory: 
> /<>/obj-x86_64-linux-gnu/platforms/reference/tests
> 7: Test timeout computed to be: 1500
> test 8
> Start   8: TestReferenceCustomBondForce
> 
> 8: Test command: 
> /<>/obj-x86_64-linux-gnu/TestReferenceCustomBondForce
> 8: Working Directory: 
> /<>/obj-x86_64-linux-gnu/platforms/reference/tests
> 8: Test timeout computed to be: 1500
> 7: Done
> 4: Done
>   1/116 Test   #4: TestReferenceCMMotionRemover ..   Passed   
>  0.01 sec
> test 9
> Start   9: TestReferenceCustomCVForce
> 
> 9: Test command: 
> /<>/obj-x86_64-linux-gnu/TestReferenceCustomCVForce
> 9: Working Directory: 
> /<>/obj-x86_64-linux-gnu/platforms/reference/tests
> 9: Test timeout computed to be: 1500
>   2/116 Test   #7: TestReferenceCustomAngleForce .   Passed   
>  0.01 sec
> test 10
> Start  10: TestReferenceCustomCentroidBondForce
> 
> 10: Test command: 
> /<>/obj-x86_64-linux-gnu/TestReferenceCustomCentroidBondForce
> 10: Working Directory: 
> /<>/obj-x86_64-linux-gnu/platforms/reference/tests
> 10: Test timeout computed to be: 1500
> 8: Done
>   3/116 Test   #8: TestReferenceCustomBondForce ..   Passed   
>  0.01 sec
> test 11
> Start  11: TestReferenceCustomCompoundBondForce
> 
> 11: Test command: 
> /<>/obj-x86_64-linux-gnu/TestReferenceCustomCompoundBondForce
> 11: Working Directory: 
> /<>/obj-x86_64-linux-gnu/platforms/reference/tests
> 11: Test timeout computed to be: 1500
> 9: Done
>

Processed: Re: Bug#1055066: usrmerge: Cannot update to version 38 on sbuild

2023-10-31 Thread Debian Bug Tracking System

Processing control commands:

> reopen -1
Bug #1055066 {Done: Marco d'Itri } [src:usrmerge] usrmerge: 
Cannot update to version 38 on sbuild
Bug reopened
Ignoring request to alter fixed versions of bug #1055066 to the same values 
previously set
> reassign -1 src:debootstrap
Bug #1055066 [src:usrmerge] usrmerge: Cannot update to version 38 on sbuild
Bug reassigned from package 'src:usrmerge' to 'src:debootstrap'.
Ignoring request to alter found versions of bug #1055066 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1055066 to the same values 
previously set

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

Bug#1055066: usrmerge: Cannot update to version 38 on sbuild

2023-10-31 Thread John Paul Adrian Glaubitz

Control: reopen -1
Control: reassign -1 src:debootstrap

Hello!

On Tue, 2023-10-31 at 09:02 +0100, John Paul Adrian Glaubitz wrote:
> Could it be that debootstrap needs to be switched to enabled usrmerge by 
> default?

I can confirm that passing --merged-usr to debootstrap fixes the problem.

Reopening the bug and assigning accordingly.

Thanks,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#1055066: usrmerge: Cannot update to version 38 on sbuild

2023-10-31 Thread John Paul Adrian Glaubitz

Hello!

I am not sure whether this issue has been fixed.

We're seeing this issue on buildds and porterboxes on Debian Ports,
regenerating the chroots fails:

dpkg: warning: ignoring pre-dependency problem!
Preparing to unpack .../tar_1.34+dfsg-1.2_ppc64.deb ...
Unpacking tar (1.34+dfsg-1.2) ...
Selecting previously unselected package usr-is-merged.
Preparing to unpack .../usr-is-merged_38_all.deb ...


**
*
* The usr-is-merged package cannot be installed because this system does
* not have a merged /usr.
*
* Please install the usrmerge package to convert this system to merged-/usr.
*
* For more information please read https://wiki.debian.org/UsrMerge.
*
**


dpkg: error processing archive /var/cache/apt/archives/usr-is-merged_38_all.deb 
(--unpack):
 new usr-is-merged package pre-installation script subprocess returned error 
exit status 1
Selecting previously unselected package util-linux.
dpkg: regarding .../util-linux_2.39.2-5_ppc64.deb containing util-linux, 
pre-dependency problem:
 util-linux pre-depends on libblkid1 (>= 2.37.2)
  libblkid1:ppc64 is unpacked, but has never been configured.

Could it be that debootstrap needs to be switched to enabled usrmerge by 
default?

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

70 matches

Mail list logo