Bug#1053295: golang-ginkgo: dropped transitional package golang-ginkgo-dev, which is still used

[Paul Wise]

On Mon, 2023-10-02 at 16:46 +0100, Martina Ferrari wrote:

> Thanks for the report, I was scratching my head over the weekend 
> wondering why this package was not migrating.. I guess I was too eager 
> to remove the transitional package, "cme check dpkg" told me it was safe 
> to remove, but I did not think of the packages that have not been 
> updated in a long while.. I will apply your suggestion in a bit.

You may also want to file bugs against those packages or
transition them so that you can later drop the Provides?

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1052838: [debian-mysql] Bug#1052838: mariadb: FTBFS: make[1]: *** [debian/rules:161: override_dh_auto_test] Error 1

[Otto Kekäläinen]

Hi!

The relevant lines from log seems to be:

> main.bind_address_resolution w4 [ fail ]
...
> 2023-09-26  6:31:03 0 [ERROR] Can't start server: Bind on TCP/IP port. Got 
> error: 98: Address already in use
> 2023-09-26  6:31:03 0 [ERROR] Do you already have another server running on 
> port: 16020 ?
> 2023-09-26  6:31:03 0 [ERROR] Aborting

What might have been holding port 16020 during the test run?

Bug#1053267: marked as done (hickle: test_H5NodeFilterProxy fails with h5py 3.9.0: Unable to delete attribute (no write intent on file))

[Debian Bug Tracking System]

Your message dated Tue, 03 Oct 2023 08:09:13 +0530
with message-id 
and subject line Re: Bug#1053267 hickle: test_H5NodeFilterProxy fails with h5py 
3.9.0: Unable to delete attribute (no write intent on file)
has caused the Debian Bug report #1053267,
regarding hickle: test_H5NodeFilterProxy fails with h5py 3.9.0: Unable to 
delete attribute (no write intent on 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.)


-- 
1053267: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053267
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hickle
Version: 5.0.2-5
Severity: serious
Justification: debci

h5py 3.9.0 is triggering an error in hickle tests, found by debci,
https://ci.debian.net/data/autopkgtest/testing/amd64/h/hickle/38279474/log.gz

 62s  test_H5NodeFilterProxy 

 62s 
 62s h5_data = 
 62s 
 62s def test_H5NodeFilterProxy(h5_data):
 62s """
 62s tests H5NodeFilterProxy class. This class allows to temporarily 
rewrite
 62s attributes of h5py.Group and h5py.Dataset nodes before being 
loaded by
 62s hickle._load method.
 62s """
 62s 
 62s # load data and try to directly modify 'type' and 'base_type' 
Attributes
 62s # which will fail cause hdf5 file is opened for read only
 62s h5_node = h5_data['somedata']
 62s with pytest.raises(OSError):
 62s try:
 62s >   h5_node.attrs['type'] = pickle.dumps(list)
 62s 
 62s 
/tmp/autopkgtest-lxc.kwo7jiul/downtmp/build.aWU/src/hickle/tests/test_01_hickle_helpers.py:126:
 
 62s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ 
 62s h5py/_debian_h5py_serial/_objects.pyx:54: in 
h5py._debian_h5py_serial._objects.with_phil.wrapper
 62s ???
 62s h5py/_debian_h5py_serial/_objects.pyx:55: in 
h5py._debian_h5py_serial._objects.with_phil.wrapper
 62s ???
 62s /usr/lib/python3/dist-packages/h5py/_debian_h5py_serial/_hl/attrs.py:104: 
in __setitem__
 62s self.create(name, data=value)
 62s /usr/lib/python3/dist-packages/h5py/_debian_h5py_serial/_hl/attrs.py:200: 
in create
 62s h5a.delete(self._id, name)
 62s h5py/_debian_h5py_serial/_objects.pyx:54: in 
h5py._debian_h5py_serial._objects.with_phil.wrapper
 62s ???
 62s h5py/_debian_h5py_serial/_objects.pyx:55: in 
h5py._debian_h5py_serial._objects.with_phil.wrapper
 62s ???
 62s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ 
 62s 
 62s >   ???
 62s E   KeyError: 'Unable to delete attribute (no write intent on file)'
 62s 
 62s h5py/_debian_h5py_serial/h5a.pyx:145: KeyError
--- End Message ---
--- Begin Message ---

Version: 5.0.2-7

This should work with both the versions of h5py now. It was more of a test 
thing than anything else.--- End Message ---

Processed: Debian bugs control

[Debian Bug Tracking System]

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

> tags 1053183 ftbfs confirmed help upstream
Bug #1053183 [src:galera-4] galera-4: FTBFS on sparc64: one of sever post-build 
test fail
Added tag(s) upstream, confirmed, help, and ftbfs.
> tags 1007954 help
Bug #1007954 [src:galera-4] galera-4 FTBFS on IPV6-only buildds
Added tag(s) help.
> thanks
Stopping processing here.

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

Bug#1051612: marked as done (rust-papergrid: Unsatisifiable dependencies)

[Debian Bug Tracking System]

Your message dated Mon, 2 Oct 2023 16:01:47 -0400
with message-id 

and subject line Re: rust-papergrid: Unsatisifiable dependencies
has caused the Debian Bug report #1051612,
regarding rust-papergrid: Unsatisifiable dependencies
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.)


-- 
1051612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051612
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-papergrid
Version: 0.9.1-1
Severity: serious

rust-papergrid is uninstallable (and therefore unstable to migrate to
Testing) because it depends on librust-ansi-str-0.8+default-dev and
ibrust-ansitok-0.2+default-dev but rust-ansi-str and rust-ansitok are
not in Debian.

Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
https://tracker.debian.org/pkg/rust-ansitok and
https://tracker.debian.org/pkg/rust-ansi-str are now in Unstable.

Thank you,
Jeremy Bícha--- End Message ---

Bug#1052084: marked as done (oci-seccomp-bpf-hook: FTBFS: make[1]: *** [debian/rules:18: copyright-scan] Error 255)

[Debian Bug Tracking System]

Your message dated Mon, 02 Oct 2023 19:50:56 +
with message-id 
and subject line Bug#1052084: fixed in oci-seccomp-bpf-hook 1.2.9+ds-1
has caused the Debian Bug report #1052084,
regarding oci-seccomp-bpf-hook: FTBFS: make[1]: *** [debian/rules:18: 
copyright-scan] Error 255
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=oci-seccomp-bpf-hook=amd64=1.2.8%2Bds-1%2Bb7=1694886724=0

   debian/rules execute_before_dh_auto_configure
make[1]: Entering directory '/<>'
scan-copyrights >debian/copyright-scan.new.tmp 
2>debian/copyright-scan.new.todo.tmp
make[1]: *** [debian/rules:18: copyright-scan] Error 255
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: binary-arch] Error 2

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: oci-seccomp-bpf-hook
Source-Version: 1.2.9+ds-1
Done: Domenico Andreoli 

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

Debian distribution maintenance software
pp.
Domenico Andreoli  (supplier of updated oci-seccomp-bpf-hook 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 30 Sep 2023 08:42:59 +0200
Source: oci-seccomp-bpf-hook
Architecture: source
Version: 1.2.9+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Domenico Andreoli 
Closes: 1052084
Changes:
 oci-seccomp-bpf-hook (1.2.9+ds-1) unstable; urgency=medium
 .
   * New upstream version.
   * Update d/copyright. (Closes: #1052084)
   * Update standards version to 4.6.2, no changes needed.
Checksums-Sha1:
 0638ff6a43c200d4d5f2ee5a09952fdff42470c6 2523 
oci-seccomp-bpf-hook_1.2.9+ds-1.dsc
 5e0d51f07f33e04f389cb8debc7308e470114eb7 137440 
oci-seccomp-bpf-hook_1.2.9+ds.orig.tar.xz
 60e20c59b30ef17ba57e227c4b78188941fdb3bf 3268 
oci-seccomp-bpf-hook_1.2.9+ds-1.debian.tar.xz
 3cec9954764094e87a73fa6f421192eea05581dd 33322 
oci-seccomp-bpf-hook_1.2.9+ds-1_arm64.buildinfo
Checksums-Sha256:
 3c87a3de29f6b6edf43f5e28a9fddbcd52097640c919b1787e41fdcedc21bbc5 2523 
oci-seccomp-bpf-hook_1.2.9+ds-1.dsc
 0d01e4a979f60cdad6419bad8c1711f92a64e101e245f63080237a71daecc9dc 137440 
oci-seccomp-bpf-hook_1.2.9+ds.orig.tar.xz
 19a0bb9a164b908b7752c2375dd039bdebf47e1ef2a197883e74cc2f87809413 3268 
oci-seccomp-bpf-hook_1.2.9+ds-1.debian.tar.xz
 1c6bb5373ec4d02db06f7861c3f8efc93b055aa48a7419957373925ce54fc157 33322 
oci-seccomp-bpf-hook_1.2.9+ds-1_arm64.buildinfo
Files:
 0926b5a7d9df6515f0564f27ffd16e27 2523 golang optional 
oci-seccomp-bpf-hook_1.2.9+ds-1.dsc
 d19e8be29c02b68e36e275aaae13357d 137440 golang optional 
oci-seccomp-bpf-hook_1.2.9+ds.orig.tar.xz
 80b84cdad0cb9d68bbf47ba0d59c9e2b 3268 golang optional 
oci-seccomp-bpf-hook_1.2.9+ds-1.debian.tar.xz
 ea50c2125f7e0a1f65e77801eb5c9a42 33322 golang optional 
oci-seccomp-bpf-hook_1.2.9+ds-1_arm64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE0shRjWi8VJar72jypoxgteDmkTcFAmUbGSIRHGNhdm9rQGRl
Ymlhbi5vcmcACgkQpoxgteDmkTe7BRAAjhGRCiqN5CH+3VbM2SF+HzPzRvnzSEed
x2/KgUp1IgCIlGGHg8dIZtHAmEX0g1KjC7VcphLjsO4sqZ1Csc2x3jsl38mfm8QV
BTvfv644YPE4VunsnoNhuAtaBOW1B2pYF+7dn7F7iUbm5nPsZlIf1x/MVEijvJk2
q06GmPYAW4VicqWHYEPUSBjVnhb9Nl/qBjwyQ9R1sT5c8rJpdSiAqSxX/dF892yp
BrgH/OTh5vz7GKIPWKVQ7fbxB4Lpou2bKZAqBZ8amgjpqKq3LeSIXcf/B8WReJ4S
kJKoXvqgCPpPZhv7q+243Vo3hV5Db85Pedx7shDz3s/qwawZZ2CKFmp3d+sEkbJv
reYL3JeE3JA1ptOdrQPpuFCHQnZ6106HUzHYdcJZbr7ht+LVx8RamI1StPyXwdO2
3ti3yubUztpYRxy5Iq9twF3KMGAIhb/3eY4eC0uPLaoc+lVHko72fHmDXuz+DEz7
LjQdiJDKEJ278LqE+Ov2uJqfaLPid3NJjDHDI1lPrkGm4EPjXCTZjKWmiK6wiR77
uZPFjapAExH1RdpF7gRkuhj0r87ApeAKAjziQkgQ3U/AVP6Adxq17EOoEgdCiYqQ
p7UsHyNq6luc+inwPfq6OWFTYQUuyz/1avWPPTI2aq/r+QoY6X2wZMU4g9Zm3koZ
AqRKuQNAtFQ=
=pLUj
-END PGP 

Bug#1023021: closed by Gianfranco Costamagna (Re: gitit: FTBFS on mipsel)

[Sebastian Ramacher]

Control: reopen -1


On 2023-10-02 15:57:06 +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the src:gitit package:
> 
> #1023021: gitit: FTBFS on mipsel
> 
> It has been closed by Gianfranco Costamagna .
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Gianfranco Costamagna 
>  by
> replying to this email.
> 
> 
> -- 
> 1023021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023021
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

> Date: Mon, 2 Oct 2023 17:54:09 +0200
> From: Gianfranco Costamagna 
> To: 1023021-d...@bugs.debian.org
> Subject: Re: gitit: FTBFS on mipsel
> Message-ID: <041a848f-3548-5fc1-0454-f3b2cef2c...@debian.org>
> 
> Mipsel is not a thing anymore.

It still is for stable. Note that tags of the bug.

Cheers

> 
> Closing.
> 
> G.
> 
> On Sat, 29 Oct 2022 12:10:48 +0200 Sebastian Ramacher  
> wrote:
> > Source: gitit
> > Version: 0.15.1.0+dfsg-2
> > Severity: serious
> > Tags: ftbfs
> > Justification: fails to build from source (but built successfully in the 
> > past)
> > 
> > https://buildd.debian.org/status/fetch.php?pkg=gitit=mipsel=0.15.1.0%2Bdfsg-2=1664568646=0
> > 
> > [2 of 2] Compiling Main ( gitit.hs, 
> > dist-ghc/build/gitit/gitit-tmp/Main.o )
> > Linking dist-ghc/build/gitit/gitit ...
> > /usr/lib/ghc/rts/libHSrts_thr.a(NonMoving.thr_o): in function 
> > `nonmovingAllocate':
> > (.text.hot.nonmovingAllocate+0x270): relocation truncated to fit: R_MIPS_26 
> > against `.text.nonmovingAllocSegment.part.0'
> > (.text.hot.nonmovingAllocate+0x280): relocation truncated to fit: R_MIPS_26 
> > against `.text.nonmovingInitSegment'
> > /usr/lib/ghc/rts/libHSrts_thr.a(NonMovingMark.thr_o): in function 
> > `trace_PAP_payload':
> > (.text.hot.trace_PAP_payload+0xb0): relocation truncated to fit: R_MIPS_26 
> > against `markQueuePushClosure'
> > (.text.hot.trace_PAP_payload+0x22c): relocation truncated to fit: R_MIPS_26 
> > against `nonmovingAddUpdRemSetBlocks'
> > (.text.hot.trace_PAP_payload+0x3e4): relocation truncated to fit: R_MIPS_26 
> > against `nonmovingAddUpdRemSetBlocks'
> > (.text.hot.trace_PAP_payload+0x458): relocation truncated to fit: R_MIPS_26 
> > against `.text.push.part.0'
> > /usr/lib/ghc/rts/libHSrts_thr.a(NonMovingMark.thr_o): in function 
> > `updateRemembSetPushThunkEager':
> > (.text.updateRemembSetPushThunkEager+0x298): relocation truncated to fit: 
> > R_MIPS_26 against `.text.hot.trace_PAP_payload'
> > /usr/lib/ghc/rts/libHSrts_thr.a(NonMovingMark.thr_o): in function 
> > `trace_stack_':
> > (.text.hot.trace_stack_+0xf4): relocation truncated to fit: R_MIPS_26 
> > against `markQueuePushClosure'
> > (.text.hot.trace_stack_+0x128): relocation truncated to fit: R_MIPS_26 
> > against `markQueuePushClosure'
> > (.text.hot.trace_stack_+0x184): relocation truncated to fit: R_MIPS_26 
> > against `markQueuePushClosure'
> > (.text.hot.trace_stack_+0x1d8): additional relocation overflows omitted 
> > from the output
> > collect2: error: ld returned 1 exit status
> > `mipsel-linux-gnu-gcc' failed in phase `Linker'. (Exit code: 1)
> > -e: error: debian/hlibrary.setup build --builddir=dist-ghc returned exit 
> > code 1
> >  at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 852.
> > Debian::Debhelper::Dh_Lib::error("debian/hlibrary.setup build 
> > --builddir=dist-ghc returned exit"...) called at 
> > /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 596
> > Debian::Debhelper::Dh_Lib::error_exitcode("debian/hlibrary.setup build 
> > --builddir=dist-ghc") called at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm 
> > line 470
> > Debian::Debhelper::Dh_Lib::doit("debian/hlibrary.setup", "build", 
> > "--builddir=dist-ghc") called at 
> > /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 650
> > Debian::Debhelper::Buildsystem::Haskell::Recipes::build_recipe() called 
> > at -e line 1
> > make: *** [/usr/share/cdbs/1/class/hlibrary.mk:158: build-ghc-stamp] Error 
> > 25
> > 
> > 
> > Cheers
> > -- 
> > Sebastian Ramacher
> > 
> > 




> Date: Sat, 29 Oct 2022 12:10:48 +0200
> From: Sebastian Ramacher 
> To: Debian Bug Tracking System 
> Subject: gitit: FTBFS on mipsel
> Message-ID: 
> 
> Source: gitit
> Version: 0.15.1.0+dfsg-2
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> 
> https://buildd.debian.org/status/fetch.php?pkg=gitit=mipsel=0.15.1.0%2Bdfsg-2=1664568646=0
> 
> [2 of 2] Compiling Main ( gitit.hs, 
> dist-ghc/build/gitit/gitit-tmp/Main.o )
> Linking dist-ghc/build/gitit/gitit ...
> /usr/lib/ghc/rts/libHSrts_thr.a(NonMoving.thr_o): in function 
> `nonmovingAllocate':
> (.text.hot.nonmovingAllocate+0x270): relocation truncated to fit: R_MIPS_26 
> against 

Processed: Re: Bug#1023021 closed by Gianfranco Costamagna (Re: gitit: FTBFS on mipsel)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1023021 {Done: Gianfranco Costamagna } 
[src:gitit] gitit: FTBFS on mipsel
Bug reopened
Ignoring request to alter fixed versions of bug #1023021 to the same values 
previously set

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

Bug#1051543: grub2: Fails to load normal.mod from a XFS v5 parition.

[Jon DeVree]

On Mon, Oct 02, 2023 at 16:51:30 +, Lidong Chen wrote:
> The changes for the extent parsing looks good to me. But, I am not sure about 
> this change:
> 
> > - if (filename + direntry->len - 1 > (char *) tail)
> > + if (filename + direntry->len - 1 > (char *) end)
> 
> Looking at the grub_xfs_next_de(), should the ‘+1’ be ‘+3’?
> 

If you don't mind, I think this would be better discussed on grub-devel.

I only posted the update here because my original patch was linked here.

-- 
Jon
Doge Wrangler
X(7): A program for managing terminal windows. See also screen(1) and tmux(1).

Bug#1053267: hickle: test_H5NodeFilterProxy fails with h5py 3.9.0: Unable to delete attribute (no write intent on file)

[Edward Betts]

Thanks for the updated patch. I've uploaded a new version of hickle with 
it.

Bug#1052677: Fixed in 1.0.7-1

[Mathieu Malaterre]

Version: 1.0.7-1

> Looks like this was already fixed in 1.0.7-1 a couple of weeks ago. I
> updated and the problem went away. Sorry for the dupe.

Sorry for the mess. Just for reference, this is also fixed on 1.0.3-3+deb12u1

Bug#1052677: marked as done (libhwy1: baseline violation)

[Debian Bug Tracking System]

Your message dated Mon, 2 Oct 2023 20:34:20 +0200
with message-id 

and subject line Fixed in 1.0.7-1
has caused the Debian Bug report #1052677,
regarding libhwy1: baseline violation
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.)


-- 
1052677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052677
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ffmpeg
Version: 7:6.0-6
Severity: normal

Dear maintainer,

The current armhf build of ffmpeg uses NEON instructions, which
prevents it from running on some processors. See log below:

$ ulimit -c unlimited
$ ffmpeg
Illegal instruction (core dumped)
$ gdb /usr/bin/ffmpeg core
GNU gdb (Debian 13.2-1) 13.2
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "arm-linux-gnueabihf".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/ffmpeg...
(No debugging symbols found in /usr/bin/ffmpeg)
[New LWP 988]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
Core was generated by `ffmpeg'.
Program terminated with signal SIGILL, Illegal instruction.
#0  0xb4ba6fbe in ?? () from /lib/arm-linux-gnueabihf/libhwy.so.1
(gdb) layout asm
┌─┐
│  > 0xb4ba6fbe  vmov.i32d16, #0 @ 0x │
│0xb4ba6fc2  movsr6, #0   │
│0xb4ba6fc4  str r6, [sp, #16]│
│0xb4ba6fc6  ldr r2, [r1, r2] │
│0xb4ba6fc8  ldr r2, [r2, #0] │
│0xb4ba6fca  str r2, [sp, #44]   @ 0x2c   │
│0xb4ba6fcc  mov.w   r2, #0   │
│0xb4ba6fd0  vstrd16, [sp, #8]│
│0xb4ba6fd4  cmp.w   r9, #0   │
│0xb4ba6fd8  beq.w   0xb4ba7180   │
│0xb4ba6fdc  mov r4, r0   │
│0xb4ba6fde  mov r5, r6   │
│0xb4ba6fe0  mov r8, r6   │
│0xb4ba6fe2  mov.w   r10, #1  │
│0xb4ba6fe6  add.w   r11, sp, #24 │
│0xb4ba6fea  sub.w   r3, r0, #8   │
│0xb4ba6fee  str r3, [sp, #4] │
│0xb4ba6ff0  ldr r2, [sp, #4] │
│0xb4ba6ff2  subsr3, r5, r6   │
│0xb4ba6ff4  mov.w   r12, r3, asr #6  │
│0xb4ba6ff8  asrsr0, r3, #4   │
│0xb4ba6ffa  ldr.w   r1, [r2, #8]!│
│0xb4ba6ffe  cmp.w   r12, #0  │
└─┘
multi-thre Thread 0xb3031020 ( In:L??   PC: 0xb4ba6fbe
(gdb) exit
$ cat /proc/cpuinfo
processor   : 0
model name  : ARMv7 Processor rev 2 (v7l)
BogoMIPS: 50.00
Features: half thumb fastmult vfp edsp thumbee vfpv3 tls idivt
vfpd32 lpae
CPU implementer : 0x56
CPU architecture: 7
CPU variant : 0x2
CPU part: 0x584
CPU revision: 2

processor   : 1
model name  : ARMv7 Processor rev 2 (v7l)
BogoMIPS: 50.00
Features: half thumb fastmult vfp edsp thumbee vfpv3 tls idivt
vfpd32 lpae
CPU implementer : 0x56
CPU architecture: 7
CPU variant : 0x2
CPU part: 0x584
CPU revision: 2

Hardware: Marvell Armada 370/XP (Device Tree)
Revision: 
Serial  : 
--- End Message ---
--- Begin Message ---
Version: 1.0.7-1

> Looks like this was already fixed in 1.0.7-1 a couple of weeks ago. I
> updated and the problem went away. Sorry for the dupe.

Sorry for the mess. Just for reference, this is also fixed on 1.0.3-3+deb12u1--- End Message ---

Bug#1051543: grub2: Fails to load normal.mod from a XFS v5 parition.

[Lidong Chen]

The changes for the extent parsing looks good to me. But, I am not sure about 
this change:

> - if (filename + direntry->len - 1 > (char *) tail)
> + if (filename + direntry->len - 1 > (char *) end)

Looking at the grub_xfs_next_de(), should the ‘+1’ be ‘+3’?

grub_xfs_next_de(struct grub_xfs_data *data, struct grub_xfs_dir2_entry *de)
{
  int size = sizeof (struct grub_xfs_dir2_entry) + de->len + 2 /* Tag */;

  if (data->hasftype)
size++; /* File type */
  return (struct grub_xfs_dir2_entry *)(((char *)de) + ALIGN_UP(size, 8));
}

Thanks,

Lidong


On Sep 27, 2023, at 6:45 PM, Jon DeVree  wrote:

On Fri, Sep 15, 2023 at 23:43:28 +0200, Sebastian Andrzej Siewior wrote:
there's now a patch from Jon DeVree upstream, which might fix this for
you. Is it possible for you to test his patch?

https://lists.gnu.org/archive/html/grub-devel/2023-09/msg00059.html

Yes it sovles the issue, the box boots.


I posted an updated v3 version of the patch:

https://lists.gnu.org/archive/html/grub-devel/2023-09/msg00110.html

--
Jon
Doge Wrangler
X(7): A program for managing terminal windows. See also screen(1) and tmux(1).

Processed: src:cpphs: fails to migrate to testing for too long: stuck in haskell transition

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.20.9.1-3
Bug #1053370 [src:cpphs] src:cpphs: fails to migrate to testing for too long: 
stuck in haskell transition
Marked as fixed in versions cpphs/1.20.9.1-3.
Bug #1053370 [src:cpphs] src:cpphs: fails to migrate to testing for too long: 
stuck in haskell transition
Marked Bug as done

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

Bug#1053370: src:cpphs: fails to migrate to testing for too long: stuck in haskell transition

[Paul Gevers]

Source: cpphs
Version: 1.20.9.1-2
Severity: serious
Control: close -1 1.20.9.1-3
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:cpphs has been trying to migrate for 31 
days [2]. Hence, I am filing this bug.


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


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


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


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


Paul

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



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1053367: src:bnfc: fails to migrate to testing for too long: stuck in haskell transition

[Paul Gevers]

Source: bnfc
Version: 2.9.4-1
Severity: serious
Control: close -1 2.9.5-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:bnfc has been trying to migrate for 32 
days [2]. Hence, I am filing this bug.


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


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


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


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


Paul

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



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1053369: src:hdbc: fails to migrate to testing for too long: stuck in haskell transition

[Paul Gevers]

Source: hdbc
Version: 2.4.0.4-1
Severity: serious
Control: close -1 2.4.0.4-2
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:hdbc has been trying to migrate for 31 
days [2]. Hence, I am filing this bug.


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


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


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


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


Paul

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



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:hdbc: fails to migrate to testing for too long: stuck in haskell transition

[Debian Bug Tracking System]

Processing control commands:

> close -1 2.4.0.4-2
Bug #1053369 [src:hdbc] src:hdbc: fails to migrate to testing for too long: 
stuck in haskell transition
Marked as fixed in versions hdbc/2.4.0.4-2.
Bug #1053369 [src:hdbc] src:hdbc: fails to migrate to testing for too long: 
stuck in haskell transition
Marked Bug as done

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

Processed: src:xmonad: fails to migrate to testing for too long: stuck in haskell transition

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.17.2-1
Bug #1053368 [src:xmonad] src:xmonad: fails to migrate to testing for too long: 
stuck in haskell transition
Marked as fixed in versions xmonad/0.17.2-1.
Bug #1053368 [src:xmonad] src:xmonad: fails to migrate to testing for too long: 
stuck in haskell transition
Marked Bug as done

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

Bug#1053368: src:xmonad: fails to migrate to testing for too long: stuck in haskell transition

[Paul Gevers]

Source: xmonad
Version: 0.17.1-1
Severity: serious
Control: close -1 0.17.2-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:xmonad has been trying to migrate for 31 
days [2]. Hence, I am filing this bug.


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


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


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


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


Paul

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



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:bnfc: fails to migrate to testing for too long: stuck in haskell transition

[Debian Bug Tracking System]

Processing control commands:

> close -1 2.9.5-1
Bug #1053367 [src:bnfc] src:bnfc: fails to migrate to testing for too long: 
stuck in haskell transition
Marked as fixed in versions bnfc/2.9.5-1.
Bug #1053367 [src:bnfc] src:bnfc: fails to migrate to testing for too long: 
stuck in haskell transition
Marked Bug as done

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

Processed: src:ldap-haskell: fails to migrate to testing for too long: stuck in haskell transition

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.6.11-7
Bug #1053365 [src:ldap-haskell] src:ldap-haskell: fails to migrate to testing 
for too long: stuck in haskell transition
Marked as fixed in versions ldap-haskell/0.6.11-7.
Bug #1053365 [src:ldap-haskell] src:ldap-haskell: fails to migrate to testing 
for too long: stuck in haskell transition
Marked Bug as done

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

Bug#1053366: src:hscolour: fails to migrate to testing for too long: stuck in haskell transition

[Paul Gevers]

Source: hscolour
Version: 1.24.4-4
Severity: serious
Control: close -1 1.24.4-5
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:hscolour has been trying to migrate for 32 
days [2]. Hence, I am filing this bug.


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


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


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


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


Paul

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



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:hscolour: fails to migrate to testing for too long: stuck in haskell transition

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.24.4-5
Bug #1053366 [src:hscolour] src:hscolour: fails to migrate to testing for too 
long: stuck in haskell transition
Marked as fixed in versions hscolour/1.24.4-5.
Bug #1053366 [src:hscolour] src:hscolour: fails to migrate to testing for too 
long: stuck in haskell transition
Marked Bug as done

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

Bug#1053365: src:ldap-haskell: fails to migrate to testing for too long: stuck in haskell transition

[Paul Gevers]

Source: ldap-haskell
Version: 0.6.11-6
Severity: serious
Control: close -1 0.6.11-7
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:ldap-haskell has been trying to migrate 
for 32 days [2]. Hence, I am filing this bug.


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


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


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


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


Paul

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



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1051543: grub2: Fails to load normal.mod from a XFS v5 parition.

[Lidong Chen]

On Oct 2, 2023, at 9:51 AM, lidong.c...@oracle.com  
wrote:

The changes for the extent parsing looks good to me. But, I am not sure about 
this change:

> - if (filename + direntry->len - 1 > (char *) tail)
> + if (filename + direntry->len - 1 > (char *) end)

Sorry, I meant the change in v3:

-   if (filename + direntry->len - 1 > (char *) tail)
+   if (filename + direntry->len + 1 > (char *) end)

Looking at the grub_xfs_next_de(), should the ‘+1’ be ‘+3’?

grub_xfs_next_de(struct grub_xfs_data *data, struct grub_xfs_dir2_entry *de)
{
  int size = sizeof (struct grub_xfs_dir2_entry) + de->len + 2 /* Tag */;

  if (data->hasftype)
size++; /* File type */
  return (struct grub_xfs_dir2_entry *)(((char *)de) + ALIGN_UP(size, 8));
}

Thanks,

Lidong


On Sep 27, 2023, at 6:45 PM, Jon DeVree  wrote:

On Fri, Sep 15, 2023 at 23:43:28 +0200, Sebastian Andrzej Siewior wrote:
there's now a patch from Jon DeVree upstream, which might fix this for
you. Is it possible for you to test his patch?

https://lists.gnu.org/archive/html/grub-devel/2023-09/msg00059.html

Yes it sovles the issue, the box boots.


I posted an updated v3 version of the patch:

https://lists.gnu.org/archive/html/grub-devel/2023-09/msg00110.html

--
Jon
Doge Wrangler
X(7): A program for managing terminal windows. See also screen(1) and tmux(1).

Bug#1053295: marked as done (golang-ginkgo: dropped transitional package golang-ginkgo-dev, which is still used)

[Debian Bug Tracking System]

Your message dated Mon, 02 Oct 2023 17:49:47 +
with message-id 
and subject line Bug#1053295: fixed in golang-ginkgo 1.16.5-5
has caused the Debian Bug report #1053295,
regarding golang-ginkgo: dropped transitional package golang-ginkgo-dev, which 
is still used
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.)


-- 
1053295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053295
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-ginkgo
Version: 1.16.5-4
Severity: serious

golang-ginkgo is failing to migrate to testing, because it dropped the
transitional package golang-ginkgo-dev, which makes a lot of golang
packages uninstallable, because they haven't migrated to the new
package golang-github-onsi-ginkgo-dev yet. The britney log indicates
the src/bin packages with newly uninstallable Depends/Build-Depends
and the ftp-master cruft report confirms the problems in more detail.

https://release.debian.org/britney/update_output.txt
https://release.debian.org/doc/britney/short-intro-to-migrations.html#debugging-failed-migration-attempts
https://ftp-master.debian.org/cruft-report-daily.txt

Probably the solution to this is for golang-github-onsi-ginkgo-dev to
add Provides: golang-ginkgo-dev so it doesn't have to go through NEW.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: golang-ginkgo
Source-Version: 1.16.5-5
Done: Martina Ferrari 

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

Debian distribution maintenance software
pp.
Martina Ferrari  (supplier of updated golang-ginkgo 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: Mon, 02 Oct 2023 17:11:16 +
Source: golang-ginkgo
Architecture: source
Version: 1.16.5-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Martina Ferrari 
Closes: 1053295
Changes:
 golang-ginkgo (1.16.5-5) unstable; urgency=medium
 .
   * debian/control: Provide golang-ginkgo-dev, since many packages still
 (build-)depend on it. Closes: #1053295
Checksums-Sha1:
 914868d81a968fa9bc83b1514b1fb84e57e1d2f9 2196 golang-ginkgo_1.16.5-5.dsc
 f136754ee7f06e32704a75d8e943627498186335 6836 
golang-ginkgo_1.16.5-5.debian.tar.xz
 db22771fb136d5de7c90a69eded1ce6e4796b5dd 7005 
golang-ginkgo_1.16.5-5_amd64.buildinfo
Checksums-Sha256:
 83842e8b5776845a4be016d394a09bbbfe8911b3a0b8ee6d34508695480402bf 2196 
golang-ginkgo_1.16.5-5.dsc
 b21a4c9987a0e0fd60c56bf0398d53aa6b96b3d518484f71e1eef57348b6a186 6836 
golang-ginkgo_1.16.5-5.debian.tar.xz
 560c96ee54e1df660dcc0dfdc594aed73265c59867c5c9a2757ea78b62cdef52 7005 
golang-ginkgo_1.16.5-5_amd64.buildinfo
Files:
 66085dbeaf8f2a8ff8e8ae862dcd40d0 2196 golang optional 
golang-ginkgo_1.16.5-5.dsc
 903f55496d4a0dab9b952bfc7fb3e3e1 6836 golang optional 
golang-ginkgo_1.16.5-5.debian.tar.xz
 1d91b1a6e18a3e1dfdda874135632c3e 7005 golang optional 
golang-ginkgo_1.16.5-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE2qbv8cYn6hwmsaaSqiMPxF+MJ7EFAmUa/F4ACgkQqiMPxF+M
J7EH4BAAuyUQM1as3Ff/TSfcA4edjhV5SDw9wDGVuEZzmA6+pgvoxrfJnMTV8cnX
9dm1tMq3tKYZm3sQoClOhKYWGBeTJXqU61zHgqJ213nW0ePTZH4HApEoespI3X4+
AukzavMRnk7fvun/2qSclj4ZeIpEz2h6ZJLdsqNROFW+Gtb0EpOzUDDUdi5npyUm
y8PDvlugPAxpp5jLHT4+97VOC/eCP5WGcegfm1YSycdlQnWoyajDvfCXv2W0bYK2
Wxccn//rInlTiMQaShdQWy30/Ve2jm8XBeFkzRNUyhtMPLXA3AM9hXlZljIHugRB
D8rvFwdhZWKRa/D6qu50vPIG4q6GSikRkp/GUGHPSM/QLdWAayfpkJ/iLY3S6+VM
9o00Zmj8k/pg+TefmHmXk83nPQDqqKq+360Nul5eU+1Kz1QbMa8RVvc2Gj3AbuT4
Sijyv4Q+wInhdj4H8hEAExBDehWKlkA4B/Dyy1KM1k/XAu7WjlnEJRTWxAXP4igI
EySt9p2k59dK63OM+XDS0QcCWUtAm27uJZ4zlCbbrzpzT80XQiJmnasTDVAPmTbM
KdAhLkwgZVoPPvuXak+M6szuarB8Fy1oZN7HeGG2Iak5IGXwlgVOHfUR6SWc3xal
H/xX73f6eHmlvkXAxIgeZDTKpi2oOthKDpWyNRDRJHkyKuTwm0Y=
=lC03
-END PGP SIGNATURE End Message ---

Processed: tagging 1023021

[Debian Bug Tracking System]

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

> tags 1023021 + bullseye
Bug #1023021 {Done: Gianfranco Costamagna } 
[src:gitit] gitit: FTBFS on mipsel
Added tag(s) bullseye.
> thanks
Stopping processing here.

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

Processed: network-manager-strongswan: diff for NMU version 1.6.0-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1042044 + patch
Bug #1042044 [src:network-manager-strongswan] network-manager-strongswan: 
FTBFS: nm-strongswan.c:122:9: error: ‘gtk_combo_box_get_active’ is deprecated: 
Use 'GtkDropDown' instead [-Werror=deprecated-declarations]
Added tag(s) patch.
> tags 1042044 + pending
Bug #1042044 [src:network-manager-strongswan] network-manager-strongswan: 
FTBFS: nm-strongswan.c:122:9: error: ‘gtk_combo_box_get_active’ is deprecated: 
Use 'GtkDropDown' instead [-Werror=deprecated-declarations]
Added tag(s) pending.

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

Bug#1052896: marked as done (uhd: FTBFS: make[2]: *** [Makefile:25: refman.dvi] Error 1)

[Debian Bug Tracking System]

Your message dated Mon, 02 Oct 2023 17:00:14 +
with message-id 
and subject line Bug#1052896: fixed in uhd 4.5.0.0+ds1-1
has caused the Debian Bug report #1052896,
regarding uhd: FTBFS: make[2]: *** [Makefile:25: refman.dvi] Error 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.)


-- 
1052896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052896
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: uhd
Version: 4.4.0.0+ds1-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 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/docs/doxygen/latex'
> Makefile:41: warning: overriding recipe for target 'refman.ps'
> Makefile:18: warning: ignoring old recipe for target 'refman.ps'
> Makefile:44: warning: overriding recipe for target 'refman.pdf'
> Makefile:21: warning: ignoring old recipe for target 'refman.pdf'
> rm -f *.ps *.dvi *.aux *.toc *.idx *.ind *.ilg *.log *.out *.brf *.blg *.bbl 
> refman.pdf
> echo "Running latex..."
> Running latex...
> xelatex refman.tex
> This is XeTeX, Version 3.141592653-2.6-0.95 (TeX Live 2023/Debian) 
> (preloaded format=xelatex)
>  restricted \write18 enabled.
> entering extended mode
> (./refman.tex
> LaTeX2e <2023-06-01>
> L3 programming layer <2023-06-05>
> ! Undefined control sequence.
> l.4   \pdfminorversion
>   =7
> ? 
> ! Emergency stop.
> l.4 
> 
> No pages of output.
> Transcript written on refman.log.
> make[2]: *** [Makefile:25: refman.dvi] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/09/25/uhd_4.4.0.0+ds1-4_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: uhd
Source-Version: 4.5.0.0+ds1-1
Done: A. Maitland Bottoms 

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

Debian distribution maintenance software
pp.
A. Maitland Bottoms  (supplier of updated uhd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 30 Sep 2023 10:04:32 -0400
Source: uhd
Binary: libuhd-dev libuhd4.5.0 libuhd4.5.0-dbgsym libuhd4.5.0-dpdk 
libuhd4.5.0-dpdk-dbgsym libuhd4.5.0-dpdk-tests libuhd4.5.0-dpdk-tests-dbgsym 
python3-uhd python3-uhd-dbgsym uhd-doc uhd-host uhd-host-dbgsym
Architecture: source amd64 all
Version: 4.5.0.0+ds1-1
Distribution: experimental
Urgency: medium
Maintainer: A. Maitland Bottoms 
Changed-By: A. Maitland Bottoms 
Description:
 libuhd-dev - universal hardware driver for Ettus Research products - headers
 libuhd4.5.0 - universal hardware driver for Ettus Research products - library
 libuhd4.5.0-dpdk - universal hardware driver for Ettus Research products - DPDK
 libuhd4.5.0-dpdk-tests - universal hardware driver for Ettus Research products 
- DPDK test
 python3-uhd - universal hardware driver for Ettus Research products - Python3
 uhd-doc- universal hardware driver for Ettus Research products - doc
 uhd-host   - universal hardware driver for Ettus Research products - host apps
Closes: 1052896
Changes:
 uhd (4.5.0.0+ds1-1) experimental; urgency=medium
 .
   * New upstream release
   * not building Doxygen output refman.pdf (Closes: #1052896)
   * upload to experimental for soversion bump
Checksums-Sha1:
 

Bug#1042044: network-manager-strongswan: diff for NMU version 1.6.0-2.1

[Boyuan Yang]

Control: tags 1042044 + patch
Control: tags 1042044 + pending

Dear maintainer,

I've prepared an NMU for network-manager-strongswan (versioned as 1.6.0-2.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru network-manager-strongswan-1.6.0/debian/changelog 
network-manager-strongswan-1.6.0/debian/changelog
--- network-manager-strongswan-1.6.0/debian/changelog   2023-06-11 
04:20:41.0 -0400
+++ network-manager-strongswan-1.6.0/debian/changelog   2023-10-02 
12:51:54.0 -0400
@@ -1,3 +1,11 @@
+network-manager-strongswan (1.6.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Properly append CFLAGS to avoid build error
+on deprecated functions. (Closes: #1042044)
+
+ -- Boyuan Yang   Mon, 02 Oct 2023 12:51:54 -0400
+
 network-manager-strongswan (1.6.0-2) unstable; urgency=medium
 
   [ Debian Janitor ]
diff -Nru network-manager-strongswan-1.6.0/debian/rules 
network-manager-strongswan-1.6.0/debian/rules
--- network-manager-strongswan-1.6.0/debian/rules   2023-06-11 
04:20:41.0 -0400
+++ network-manager-strongswan-1.6.0/debian/rules   2023-10-02 
12:51:51.0 -0400
@@ -1,5 +1,9 @@
 #!/usr/bin/make -f
 
+# see ENVIRONMENT in dpkg-buildflags(1)
+# package maintainers to append CFLAGS
+export DEB_CFLAGS_MAINT_APPEND = -DGDK_DISABLE_DEPRECATION_WARNINGS
+
 %:
dh $@
 


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

Bug#1023021: marked as done (gitit: FTBFS on mipsel)

[Debian Bug Tracking System]

Your message dated Mon, 2 Oct 2023 17:54:09 +0200
with message-id <041a848f-3548-5fc1-0454-f3b2cef2c...@debian.org>
and subject line Re: gitit: FTBFS on mipsel
has caused the Debian Bug report #1023021,
regarding gitit: FTBFS on mipsel
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.)


-- 
1023021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023021
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gitit
Version: 0.15.1.0+dfsg-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=gitit=mipsel=0.15.1.0%2Bdfsg-2=1664568646=0

[2 of 2] Compiling Main ( gitit.hs, 
dist-ghc/build/gitit/gitit-tmp/Main.o )
Linking dist-ghc/build/gitit/gitit ...
/usr/lib/ghc/rts/libHSrts_thr.a(NonMoving.thr_o): in function 
`nonmovingAllocate':
(.text.hot.nonmovingAllocate+0x270): relocation truncated to fit: R_MIPS_26 
against `.text.nonmovingAllocSegment.part.0'
(.text.hot.nonmovingAllocate+0x280): relocation truncated to fit: R_MIPS_26 
against `.text.nonmovingInitSegment'
/usr/lib/ghc/rts/libHSrts_thr.a(NonMovingMark.thr_o): in function 
`trace_PAP_payload':
(.text.hot.trace_PAP_payload+0xb0): relocation truncated to fit: R_MIPS_26 
against `markQueuePushClosure'
(.text.hot.trace_PAP_payload+0x22c): relocation truncated to fit: R_MIPS_26 
against `nonmovingAddUpdRemSetBlocks'
(.text.hot.trace_PAP_payload+0x3e4): relocation truncated to fit: R_MIPS_26 
against `nonmovingAddUpdRemSetBlocks'
(.text.hot.trace_PAP_payload+0x458): relocation truncated to fit: R_MIPS_26 
against `.text.push.part.0'
/usr/lib/ghc/rts/libHSrts_thr.a(NonMovingMark.thr_o): in function 
`updateRemembSetPushThunkEager':
(.text.updateRemembSetPushThunkEager+0x298): relocation truncated to fit: 
R_MIPS_26 against `.text.hot.trace_PAP_payload'
/usr/lib/ghc/rts/libHSrts_thr.a(NonMovingMark.thr_o): in function 
`trace_stack_':
(.text.hot.trace_stack_+0xf4): relocation truncated to fit: R_MIPS_26 against 
`markQueuePushClosure'
(.text.hot.trace_stack_+0x128): relocation truncated to fit: R_MIPS_26 against 
`markQueuePushClosure'
(.text.hot.trace_stack_+0x184): relocation truncated to fit: R_MIPS_26 against 
`markQueuePushClosure'
(.text.hot.trace_stack_+0x1d8): additional relocation overflows omitted from 
the output
collect2: error: ld returned 1 exit status
`mipsel-linux-gnu-gcc' failed in phase `Linker'. (Exit code: 1)
-e: error: debian/hlibrary.setup build --builddir=dist-ghc returned exit code 1
 at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 852.
Debian::Debhelper::Dh_Lib::error("debian/hlibrary.setup build 
--builddir=dist-ghc returned exit"...) called at 
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 596
Debian::Debhelper::Dh_Lib::error_exitcode("debian/hlibrary.setup build 
--builddir=dist-ghc") called at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm 
line 470
Debian::Debhelper::Dh_Lib::doit("debian/hlibrary.setup", "build", 
"--builddir=dist-ghc") called at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 650
Debian::Debhelper::Buildsystem::Haskell::Recipes::build_recipe() called 
at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:158: build-ghc-stamp] Error 25


Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---

Mipsel is not a thing anymore.

Closing.

G.

On Sat, 29 Oct 2022 12:10:48 +0200 Sebastian Ramacher  
wrote:

Source: gitit
Version: 0.15.1.0+dfsg-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=gitit=mipsel=0.15.1.0%2Bdfsg-2=1664568646=0

[2 of 2] Compiling Main ( gitit.hs, 
dist-ghc/build/gitit/gitit-tmp/Main.o )
Linking dist-ghc/build/gitit/gitit ...
/usr/lib/ghc/rts/libHSrts_thr.a(NonMoving.thr_o): in function 
`nonmovingAllocate':
(.text.hot.nonmovingAllocate+0x270): relocation truncated to fit: R_MIPS_26 
against `.text.nonmovingAllocSegment.part.0'
(.text.hot.nonmovingAllocate+0x280): relocation truncated to fit: R_MIPS_26 
against `.text.nonmovingInitSegment'
/usr/lib/ghc/rts/libHSrts_thr.a(NonMovingMark.thr_o): in function 
`trace_PAP_payload':
(.text.hot.trace_PAP_payload+0xb0): relocation truncated to fit: R_MIPS_26 
against `markQueuePushClosure'
(.text.hot.trace_PAP_payload+0x22c): relocation truncated to fit: R_MIPS_26 
against `nonmovingAddUpdRemSetBlocks'
(.text.hot.trace_PAP_payload+0x3e4): relocation truncated to fit: R_MIPS_26 
against `nonmovingAddUpdRemSetBlocks'

Bug#1053295: golang-ginkgo: dropped transitional package golang-ginkgo-dev, which is still used

[Martina Ferrari]

Hi Pabs!

Thanks for the report, I was scratching my head over the weekend 
wondering why this package was not migrating.. I guess I was too eager 
to remove the transitional package, "cme check dpkg" told me it was safe 
to remove, but I did not think of the packages that have not been 
updated in a long while.. I will apply your suggestion in a bit.



Thanks!

On 01/10/2023 05:48, Paul Wise wrote:

Source: golang-ginkgo
Version: 1.16.5-4
Severity: serious

golang-ginkgo is failing to migrate to testing, because it dropped the
transitional package golang-ginkgo-dev, which makes a lot of golang
packages uninstallable, because they haven't migrated to the new
package golang-github-onsi-ginkgo-dev yet. The britney log indicates
the src/bin packages with newly uninstallable Depends/Build-Depends
and the ftp-master cruft report confirms the problems in more detail.

https://release.debian.org/britney/update_output.txt
https://release.debian.org/doc/britney/short-intro-to-migrations.html#debugging-failed-migration-attempts
https://ftp-master.debian.org/cruft-report-daily.txt

Probably the solution to this is for golang-github-onsi-ginkgo-dev to
add Provides: golang-ginkgo-dev so it doesn't have to go through NEW.



--
Martina Ferrari (Tina)

Bug#1051543: grub2: Fails to load normal.mod from a XFS v5 parition.

[Julian Andres Klode]

On Fri, Sep 29, 2023 at 10:36:03PM +0200, Sebastian Andrzej Siewior wrote:
> On 2023-09-27 21:45:03 [-0400], Jon DeVree wrote:
> > I posted an updated v3 version of the patch:
> > 
> > https://lists.gnu.org/archive/html/grub-devel/2023-09/msg00110.html
> 
> Just rebuilt grub with v3 of the patch and I can confirm that it works.
> Thank you.
> 
> Referencing the message-id or the link to lore
>   https://lore.kernel.org/all/20230928004354.32685-1-n...@vault24.org
> 
> makes it easier to grab the patch. The GNU list archive contains html
> encoding among other things which make it imposible…

Being subscribed to the mailing list, grabbing the patch and applying
it and shipping it isn't hard, but if you were wondering why it's
not fixed, it hasn't been merged or received a Reviewed-By yet;
and I don't really want to carry file system (parser) patches
outside of upstream for security reasons, needing separate
revocation if that is broken.
-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#1042293: marked as done (golang-github-libgit2-git2go: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/libgit2/git2go/v34 returned exit code 1)

[Debian Bug Tracking System]

Your message dated Mon, 02 Oct 2023 13:19:15 +
with message-id 
and subject line Bug#1042293: fixed in golang-github-libgit2-git2go 34.0.0-4
has caused the Debian Bug report #1042293,
regarding golang-github-libgit2-git2go: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/libgit2/git2go/v34 
returned exit code 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.)


-- 
1042293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-libgit2-git2go
Version: 34.0.0-3
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):
>  debian/rules binary
> dh binary --buildsystem=golang --with=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_autoreconf -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>   Copy checkout.go -> 
> obj-x86_64-linux-gnu/src/github.com/libgit2/git2go/v34/checkout.go
>   Copy indexer.go -> 
> obj-x86_64-linux-gnu/src/github.com/libgit2/git2go/v34/indexer.go
>   Copy patch_test.go -> 
> obj-x86_64-linux-gnu/src/github.com/libgit2/git2go/v34/patch_test.go
>   Copy remote.go -> 
> obj-x86_64-linux-gnu/src/github.com/libgit2/git2go/v34/remote.go
>   Copy commit.go -> 
> obj-x86_64-linux-gnu/src/github.com/libgit2/git2go/v34/commit.go
>   Copy clone_test.go -> 
> obj-x86_64-linux-gnu/src/github.com/libgit2/git2go/v34/clone_test.go
>   Copy cherrypick_test.go -> 
> obj-x86_64-linux-gnu/src/github.com/libgit2/git2go/v34/cherrypick_test.go
>   Copy note.go -> 
> obj-x86_64-linux-gnu/src/github.com/libgit2/git2go/v34/note.go
>   Copy handles.go -> 
> obj-x86_64-linux-gnu/src/github.com/libgit2/git2go/v34/handles.go
>   Copy patch.go -> 
> obj-x86_64-linux-gnu/src/github.com/libgit2/git2go/v34/patch.go
>   Copy blob_test.go -> 
> obj-x86_64-linux-gnu/src/github.com/libgit2/git2go/v34/blob_test.go
>   Copy repository_test.go -> 
> obj-x86_64-linux-gnu/src/github.com/libgit2/git2go/v34/repository_test.go
>   Copy graph_test.go -> 
> obj-x86_64-linux-gnu/src/github.com/libgit2/git2go/v34/graph_test.go
>   Copy reset_test.go -> 
> obj-x86_64-linux-gnu/src/github.com/libgit2/git2go/v34/reset_test.go
>   Copy blob.go -> 
> obj-x86_64-linux-gnu/src/github.com/libgit2/git2go/v34/blob.go
>   Copy credentials.go -> 
> obj-x86_64-linux-gnu/src/github.com/libgit2/git2go/v34/credentials.go
>   Copy graph.go -> 
> obj-x86_64-linux-gnu/src/github.com/libgit2/git2go/v34/graph.go
>   Copy push_test.go -> 
> obj-x86_64-linux-gnu/src/github.com/libgit2/git2go/v34/push_test.go
>   Copy config.go -> 
> obj-x86_64-linux-gnu/src/github.com/libgit2/git2go/v34/config.go
>   Copy reference.go -> 
> obj-x86_64-linux-gnu/src/github.com/libgit2/git2go/v34/reference.go
>   Copy submodule.go -> 
> obj-x86_64-linux-gnu/src/github.com/libgit2/git2go/v34/submodule.go
>   Copy signature.go -> 
> obj-x86_64-linux-gnu/src/github.com/libgit2/git2go/v34/signature.go
>   Copy diff_test.go -> 
> obj-x86_64-linux-gnu/src/github.com/libgit2/git2go/v34/diff_test.go
>   Copy describe_test.go -> 
> obj-x86_64-linux-gnu/src/github.com/libgit2/git2go/v34/describe_test.go
>   Copy transport_test.go -> 
> obj-x86_64-linux-gnu/src/github.com/libgit2/git2go/v34/transport_test.go
>   Copy Build_bundled_static.go -> 
> obj-x86_64-linux-gnu/src/github.com/libgit2/git2go/v34/Build_bundled_static.go
>   Copy features.go -> 
> obj-x86_64-linux-gnu/src/github.com/libgit2/git2go/v34/features.go
>   Copy packbuilder.go -> 
> obj-x86_64-linux-gnu/src/github.com/libgit2/git2go/v34/packbuilder.go
>   Copy rebase.go -> 
> obj-x86_64-linux-gnu/src/github.com/libgit2/git2go/v34/rebase.go
>   Copy Build_system_static.go -> 
> obj-x86_64-linux-gnu/src/github.com/libgit2/git2go/v34/Build_system_static.go
>   Copy rebase_test.go -> 
> obj-x86_64-linux-gnu/src/github.com/libgit2/git2go/v34/rebase_test.go
>   Copy branch_test.go -> 
> obj-x86_64-linux-gnu/src/github.com/libgit2/git2go/v34/branch_test.go
>   Copy tree_test.go -> 
> obj-x86_64-linux-gnu/src/github.com/libgit2/git2go/v34/tree_test.go
>   Copy merge_test.go -> 
> obj-x86_64-linux-gnu/src/github.com/libgit2/git2go/v34/merge_test.go
>   Copy revparse_test.go -> 
> 

Bug#1051364: marked as done (nvi uses Conflicts in violation of policy 10.1)

[Debian Bug Tracking System]

Your message dated Mon, 02 Oct 2023 13:05:11 +
with message-id 
and subject line Bug#1051364: fixed in nvi 1.81.6-19
has caused the Debian Bug report #1051364,
regarding nvi uses Conflicts in violation of policy 10.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.)


-- 
1051364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051364
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nvi
Version: 1.81.6-18
Severity: serious
Justification: policy 10.1

nvi has declared Conflicts with nex due to the duplicated use of
/usr/bin/nex. Since nvi has come first, this purely is a bug in the nex
package and it is tracked as #1022957. On the nvi side, such a conflict
is harmful, because a fixed nex (one that no longer contains
/usr/bin/nex) cannot be coinstalled. The conflict is declared in direct
violation of policy section 10.1 and should therefore be removed.

Helmut
--- End Message ---
--- Begin Message ---
Source: nvi
Source-Version: 1.81.6-19
Done: Amin Bandali 

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

Debian distribution maintenance software
pp.
Amin Bandali  (supplier of updated nvi 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: Sun, 01 Oct 2023 23:12:24 -0400
Source: nvi
Architecture: source
Version: 1.81.6-19
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Amin Bandali 
Closes: 1051364
Changes:
 nvi (1.81.6-19) unstable; urgency=medium
 .
   * QA upload.
   * debian/control: Remove 'Conflicts: nex' to comply with
 Debian Policy section 10.1. (Closes: #1051364)
Checksums-Sha1:
 cb6482be2031596f4dbea5a12f16a76531f2ff6d 1713 nvi_1.81.6-19.dsc
 cf3df440d918cbafff5d388d3ddd49f8ebcafee6 104656 nvi_1.81.6-19.debian.tar.xz
 c70a6a9cde0ea5aa2120203a5a44a06611d21858 5510 nvi_1.81.6-19_source.buildinfo
Checksums-Sha256:
 44fc757202f154ed6e63de08a812423663944f8abb52f98393e6b9b84625bbec 1713 
nvi_1.81.6-19.dsc
 33e6b71119b391a1c024b619565a2b9677ad169583ba1f73596d535ed1d6cd24 104656 
nvi_1.81.6-19.debian.tar.xz
 fe5744104a7e8627c168a5163c5c417ecbe135e2596388e4e23cc27aa668219f 5510 
nvi_1.81.6-19_source.buildinfo
Files:
 af21ae0d9d30a8b712c612a54acc7ff2 1713 editors optional nvi_1.81.6-19.dsc
 3f272ada6a7bbbf0c7d15d75cd6c305b 104656 editors optional 
nvi_1.81.6-19.debian.tar.xz
 303493171828aaf81be9857ba2f17c52 5510 editors optional 
nvi_1.81.6-19_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmUavAwQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFHGSDACEExUcqBldAaFDJ5ECVocUs5HYONseeZ6C
grA/mA6aYoon+VDZrGSVkJ9OWA6a5eD6xiJf4Ijni+iKwrPmonND10b2QmmuNe2Q
oSAiV8Z6/VYQz8jk/kCkjd6kkGIBqflyma6rndWkXoj1tik2comQ/D0HvoYVN2vx
U8iN7BdOYHK/0sTlQdoWYl/XUR+fS0/r68zaF75SX38ptqTSVDuuI9mKxum3Y7K0
wUlZ0SB8s0HOVFg14tDbPTNXePjjnfU1VIv9eRZDqTOAz9l6COZbJ2PI0B/5lE5i
DLICIP+df7mwJsf5APBWbpevLwMAJeldyjDb9unFTjWdMWJpKofuufXF46bTPwH5
wVK/J5Ki1JbMC3F/IftX+3iLLHeM5wy90Hgk2ObwSlELvqrfUYJ24Jk2K1jfDS1w
oGPTHwCekF92vf+rK3fWo2BEf/Wd9R9RcO116WKov0Y6apPP1FQjWati9c5sFgkv
rSrunoP1gOAXY9IHPW+Z1fnKDa/N4l0=
=nvmt
-END PGP SIGNATURE End Message ---

Processed: tagging 1051364 + patch

[Debian Bug Tracking System]

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

> tags 1051364 + patch
Bug #1051364 [nvi] nvi uses Conflicts in violation of policy 10.1
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#1051364: nvi uses Conflicts in violation of policy 10.1

[Amin Bandali]

X-Debbugs-CC: Tobias Frost 

Dear Tobi, all,

I've prepared a patch + QA upload for unstable to address this.

The upload is on mentors.debian.net:

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

And the patch against the https://salsa.debian.org/debian/nvi
repo is attached.

I plan on preparing a separate QA upload for some other small
improvements, like updating the debian/watch file to point to
the git repo on repo.or.cz rather than the current broken page.
Or if you prefer, I can amend this change and do these as part
of this one.

>From d625f9ea73c9957cc479d13e985565d4e703c563 Mon Sep 17 00:00:00 2001
From: Amin Bandali 
Date: Sun, 1 Oct 2023 23:16:05 -0400
Subject: [PATCH] debian/control: Remove 'Conflicts: nex' (Closes: #1051364)

---
 debian/changelog | 8 
 debian/control   | 1 -
 2 files changed, 8 insertions(+), 1 deletion(-)

diff --git a/debian/changelog b/debian/changelog
index 67be40cf..d54e939c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+nvi (1.81.6-19) unstable; urgency=medium
+
+  * QA upload.
+  * debian/control: Remove 'Conflicts: nex' to comply with
+Debian Policy section 10.1. (Closes: #1051364)
+
+ -- Amin Bandali   Sun, 01 Oct 2023 23:12:24 -0400
+
 nvi (1.81.6-18) unstable; urgency=medium
 
   * QA upload.
diff --git a/debian/control b/debian/control
index 45b12a9b..d64d8550 100644
--- a/debian/control
+++ b/debian/control
@@ -17,7 +17,6 @@ Architecture: any
 Pre-Depends: ${misc:Pre-Depends}
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Recommends: nvi-doc
-Conflicts: nex
 Description: 4.4BSD re-implementation of vi
  Vi is the original screen based text editor for Unix systems.
  It is considered the standard text editor, and is available on
-- 
2.39.2

Bug#1053349: AWStats.pl is corrupted

[Christian Marillat]

On 02 oct. 2023 14:33, Petros Pap  wrote:

> Package: awstats
> Version: 7.8-3
> Severity: critical
>
> File /usr/lib/cgi-bin/awstats.pl
> fils is corrupted, ends with unclosed function

Are you sure you don't have a hard drive or file system problem ?

Send me the output of :

md5sum /usr/lib/cgi-bin/awstats.pl

Christian

Bug#1053349: AWStats.pl is corrupted

[Christian Marillat]

On 02 oct. 2023 14:33, Petros Pap  wrote:

> Package: awstats
> Version: 7.8-3
> Severity: critical
>
> File /usr/lib/cgi-bin/awstats.pl
> fils is corrupted, ends with unclosed function

Are you sure you don't have a hard drive or file system problem ?

Send me the output of :

sha256sum /usr/lib/cgi-bin/awstats.pl

Christian

Bug#1000090: marked as done (coda: depends on obsolete pcre3 library)

[Debian Bug Tracking System]

Your message dated Mon, 2 Oct 2023 13:24:22 +0100
with message-id <67120e5a-457a-4b9e-997b-8553cf3ee...@mckinstry.ie>
and subject line Closing
has caused the Debian Bug report #190,
regarding coda: depends on obsolete pcre3 library
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.)


-- 
190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=190
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: coda
Severity: important
User: matthew-pcre...@debian.org
Usertags: obsolete-pcre3

Dear maintainer,

Your package still depends on the old, obsolete PCRE3[0] libraries
(i.e. libpcre3-dev). This has been end of life for a while now, and
upstream do not intend to fix any further bugs in it. Accordingly, I
would like to remove the pcre3 libraries from Debian, preferably in
time for the release of Bookworm.

The newer PCRE2 library was first released in 2015, and has been in
Debian since stretch. Upstream's documentation for PCRE2 is available
here: https://pcre.org/current/doc/html/

Many large projects that use PCRE have made the switch now (e.g. git,
php); it does involve some work, but we are now at the stage where
PCRE3 should not be used, particularly if it might ever be exposed to
untrusted input.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00176.html

Regards,

Matthew [0] Historical reasons mean that old PCRE is packaged as
pcre3 in Debian 
--- End Message ---
--- Begin Message ---

fixed 190

thanks


This was fixed in the latest upload.


--
Alastair McKinstry,
GPG: 82383CE9165B347C787081A2CBE6BB4E5D9AD3A5
ph: +353 87 6847928 e: alast...@mckinstry.ie, im: @alastair:mckinstry.ie--- End Message ---

Bug#1053178: marked as done (hg-git: incompatible with mercurial 6.5)

[Debian Bug Tracking System]

Your message dated Mon, 02 Oct 2023 12:18:58 +
with message-id 
and subject line Bug#1053178: fixed in hg-git 1.0.2-1.1
has caused the Debian Bug report #1053178,
regarding hg-git: incompatible with mercurial 6.5
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.)


-- 
1053178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hg-git
Version: 1.0.2-1
Severity: grave
X-Debbugs-Cc: jcris...@debian.org

Hi,

hg-git looks like it needs an update for compatibility with current
mercurial, see e.g. 
https://ci.debian.net/data/autopkgtest/testing/amd64/h/hg-git/38210693/log.gz

> ** Unknown exception encountered with possibly-broken third-party extension 
> "hggit" unknown (dulwich 0.21.6)
> ** which supports versions 6.4 of Mercurial.
> ** Please disable "hggit" and try your action again.
> ** If that fixes the bug please report it to 
> https://foss.heptapod.net/mercurial/hg-git/issues
> ** Python 3.11.5 (main, Aug 29 2023, 15:31:31) [GCC 13.2.0]
> ** Mercurial Distributed SCM (version 6.5.2)
> ** Extensions loaded: hggit unknown (dulwich 0.21.6)
> Traceback (most recent call last):
>   File "/usr/bin/hg", line 59, in 
> dispatch.run()
>   File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 143, in 
> run
> status = dispatch(req)
>  ^
>   File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 232, in 
> dispatch
> status = _rundispatch(req)
>  ^
>   File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 276, in 
> _rundispatch
> ret = _runcatch(req) or 0
>   ^^
>   File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 457, in 
> _runcatch
> return _callcatch(ui, _runcatchfunc)
>^
>   File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 467, in 
> _callcatch
> return scmutil.callcatch(ui, func)
>^^^
>   File "/usr/lib/python3/dist-packages/mercurial/scmutil.py", line 153, in 
> callcatch
> return func()
>^^
>   File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 447, in 
> _runcatchfunc
> return _dispatch(req)
>^^
>   File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 1272, in 
> _dispatch
> return runcommand(
>^^^
>   File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 905, in 
> runcommand
> ret = _runcommand(ui, options, cmd, d)
>   
>   File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 1284, in 
> _runcommand
> return cmdfunc()
>^
>   File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 1270, in 
> 
> d = lambda: util.checksignature(func)(ui, *args, **strcmdopt)
> ^
>   File "/usr/lib/python3/dist-packages/mercurial/util.py", line 1881, in check
> return func(*args, **kwargs)
>^
>   File "/usr/lib/python3/dist-packages/mercurial/commands.py", line 1992, in 
> clone
> r = hg.clone(
> ^
>   File "/usr/lib/python3/dist-packages/hggit/schemes.py", line 121, in clone
> srcpeer, destpeer = orig(*args, **opts)
> ^^^
>   File "/usr/lib/python3/dist-packages/mercurial/hg.py", line 727, in clone
> srcpeer = peer(ui, peeropts, src_path)
>   
>   File "/usr/lib/python3/dist-packages/hggit/schemes.py", line 112, in peer
> newpeer = orig(uiorrepo, *args, **opts)
>   ^
>   File "/usr/lib/python3/dist-packages/mercurial/hg.py", line 286, in peer
> peer = repo.peer(path=peer_path, remotehidden=remotehidden)
>
> TypeError: gitrepo.peer() got an unexpected keyword argument 'remotehidden'

Cheers,
Julien
--- End Message ---
--- Begin Message ---
Source: hg-git
Source-Version: 1.0.2-1.1
Done: Julien Cristau 

We believe that the bug you reported is fixed in the latest version of
hg-git, 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 1053...@bugs.debian.org,
and the maintainer will reopen the bug 

Bug#1053351: filelight: Crashes on launch

[Pepijn van Gijzen]

Package: filelight
Version: 4:23.04.2-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: pepijnleon...@gmail.com

Dear Maintainer,

When launching filelight, it crashes with the following error:

$ filelight
kf.kirigami: Failed to find a Kirigami platform plugin
Segmentation fault

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

Kernel: Linux 6.5.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.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 filelight depends on:
ii  kio 5.107.0-1
ii  libc6   2.37-10
ii  libkf5configcore5   5.107.0-1
ii  libkf5coreaddons5   5.107.0-1
ii  libkf5i18n5 5.107.0-1+b1
ii  libkf5kiocore5  5.107.0-1
ii  libkf5kiogui5   5.107.0-1
ii  libkf5kiowidgets5   5.107.0-1
ii  libkf5widgetsaddons55.107.0-1
ii  libkf5xmlgui5   5.107.0-1+b1
ii  libqt5core5a5.15.10+dfsg-3
ii  libqt5gui5  5.15.10+dfsg-3
ii  libqt5qml5  5.15.10+dfsg-2
ii  libqt5quick55.15.10+dfsg-2
ii  libqt5quickcontrols2-5  5.15.10+dfsg-2
ii  libqt5widgets5  5.15.10+dfsg-3
ii  libstdc++6  13.2.0-4
ii  qml-module-org-kde-kcoreaddons  5.107.0-1
ii  qml-module-org-kde-kirigami25.107.0-1+b1
ii  qml-module-org-kde-quickcharts  5.107.0-1
ii  qml-module-qt-labs-platform 5.15.10+dfsg-2

filelight recommends no packages.

filelight suggests no packages.

-- no debconf information

Bug#1053350: vulkan-memory-allocator FTBFS with gcc 13

[Adrian Bunk]

Source: vulkan-memory-allocator
Version: 3.0.1+dfsg-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=vulkan-memory-allocator=riscv64=3.0.1%2Bdfsg-1=1695533510=0

...
In file included from /<>/src/VmaUsage.h:91,
 from /<>/src/VmaUsage.cpp:30:
/<>/src/../include/vk_mem_alloc.h: In function ‘void 
VmaUint32ToStr(char*, size_t, uint32_t)’:
/<>/src/../include/vk_mem_alloc.h:2817:9: error: ‘snprintf’ was 
not declared in this scope
 2817 | snprintf(outStr, strLen, "%u", static_cast(num));
  | ^~~~
/<>/src/../include/vk_mem_alloc.h:2651:1: note: ‘snprintf’ is 
defined in header ‘’; did you forget to ‘#include ’?
 2650 | #include 
  +++ |+#include 
 2651 | #else
/<>/src/../include/vk_mem_alloc.h: In function ‘void 
VmaUint64ToStr(char*, size_t, uint64_t)’:
/<>/src/../include/vk_mem_alloc.h:2821:9: error: ‘snprintf’ was 
not declared in this scope
 2821 | snprintf(outStr, strLen, "%llu", static_cast(num));
  | ^~~~
/<>/src/../include/vk_mem_alloc.h:2821:9: note: ‘snprintf’ is 
defined in header ‘’; did you forget to ‘#include ’?
/<>/src/../include/vk_mem_alloc.h: In function ‘void 
VmaPtrToStr(char*, size_t, const void*)’:
/<>/src/../include/vk_mem_alloc.h:2825:9: error: ‘snprintf’ was 
not declared in this scope
 2825 | snprintf(outStr, strLen, "%p", ptr);
  | ^~~~
/<>/src/../include/vk_mem_alloc.h:2825:9: note: ‘snprintf’ is 
defined in header ‘’; did you forget to ‘#include ’?
make[3]: *** [src/CMakeFiles/VulkanMemoryAllocator.dir/build.make:79: 
src/CMakeFiles/VulkanMemoryAllocator.dir/VmaUsage.cpp.o] Error 1

Bug#1052931: marked as done (pyvenv-el: FTBFS: make: *** [debian/rules:4: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Mon, 02 Oct 2023 11:39:36 +
with message-id 
and subject line Bug#1052931: fixed in pyvenv-el 1.21+git20211014.31ea715-1
has caused the Debian Bug report #1052931,
regarding pyvenv-el: FTBFS: make: *** [debian/rules:4: binary] Error 25
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.)


-- 
1052931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052931
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyvenv-el
Version: 1.21+git20201124.37e7cb1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> skipping upstream build
> make[1]: Leaving directory '/<>'
>dh_elpa_test
>   emacs -batch -Q -l package --eval "(add-to-list 'package-directory-list 
> \"/usr/share/emacs/site-lisp/elpa\")" --eval "(add-to-list 
> 'package-directory-list \"/usr/share/emacs/site-lisp/elpa-src\")" -f 
> package-initialize -L . -L test --eval "(load-file \"test/test-helper.el\")" 
> -l test/pyvenv-workon-home-test.el -l test/pyvenv-mode-test.el -l 
> test/pyvenv-deactivate-test.el -l test/pyvenv-activate-test.el -l 
> test/pyvenv-hook-dir-test.el -l test/pyvenv-virtualenv-list-test.el -l 
> test/pyvenv-workon-test.el --eval \(ert-run-tests-batch-and-exit\)
> Loading /<>/test/test-helper.el (source)...
> 
> Error: error ("Test ‘pyvenv-hook-dir’ redefined")
>   mapbacktrace(#f(compiled-function (evald func args flags) # -0xf7995a214517817>))
>   debug-early-backtrace()
>   debug-early(error (error "Test ‘pyvenv-hook-dir’ redefined"))
>   error("Test `%s' redefined" pyvenv-hook-dir)
>   ert-set-test(pyvenv-hook-dir #s(ert-test :name pyvenv-hook-dir 
> :documentation nil :body (lambda nil (let ((process-environment (cons 
> "VIRTUALENVWRAPPER_HOOK_DIR=/hook_dir" process-environment))) (let* ((fn-154 
> #'equal) (args-155 (condition-case err (let ((signal-hook-function 
> #'ert--should-signal-hook)) (list (pyvenv-hook-dir) "/hook_dir")) (error 
> (progn (setq fn-154 #'signal) (list (car err) (cdr err))) (let 
> ((value-156 'ert-form-evaluation-aborted-157)) (let (form-description-158) 
> (if (unwind-protect (setq value-156 (apply fn-154 args-155)) (setq 
> form-description-158 (nconc (list '(should (equal (pyvenv-hook-dir) 
> "/hook_dir"))) (list :form (cons fn-154 args-155)) (if (eql value-156 
> 'ert-form-evaluation-aborted-157) nil (list :value value-156)) (if (eql 
> value-156 'ert-form-evaluation-aborted-157) nil (let* ((-explainer- (and t 
> (ert--get-explainer 'equal (if -explainer- (list :explanation (apply 
> -explainer- args-155)) nil) (ert--signal-should-execution 
> form-description-158)) nil (ert-fail form-description-158))) value-156))) 
> (let ((process-environment (append '("VIRTUALENVWRAPPER_HOOK_DIR" 
> "WORKON_HOME=/workon_home") process-environment))) (let* ((fn-159 #'equal) 
> (args-160 (condition-case err (let ((signal-hook-function 
> #'ert--should-signal-hook)) (list (pyvenv-hook-dir) "/workon_home")) (error 
> (progn (setq fn-159 #'signal) (list (car err) (cdr err))) (let 
> ((value-161 'ert-form-evaluation-aborted-162)) (let (form-description-163) 
> (if (unwind-protect (setq value-161 (apply fn-159 args-160)) (setq 
> form-description-163 (nconc (list '(should (equal (pyvenv-hook-dir) 
> "/workon_home"))) (list :form (cons fn-159 args-160)) (if (eql value-161 
> 'ert-form-evaluation-aborted-162) nil (list :value value-161)) (if (eql 
> value-161 'ert-form-evaluation-aborted-162) nil (let* ((-explainer- (and t 
> (ert--get-explainer 'equal (if -explainer- (list :explanation (apply 
> -explainer- args-160)) nil) (ert--signal-should-execution 
> form-description-163)) nil (ert-fail form-description-163))) value-161))) 
> (let ((process-environment (append '("VIRTUALENVWRAPPER_HOOK_DIR" 
> "WORKON_HOME") process-environment))) (let* ((fn-164 #'equal) (args-165 
> (condition-case err (let ((signal-hook-function #'ert--should-signal-hook)) 
> (list (pyvenv-hook-dir) (expand-file-name "~/.virtualenvs"))) (error (progn 
> (setq fn-164 #'signal) (list (car err) (cdr err))) (let ((value-166 
> 'ert-form-evaluation-aborted-167)) (let (form-description-168) (if 
> (unwind-protect (setq value-166 (apply fn-164 args-165)) (setq 
> form-description-168 (nconc (list '(should (equal (pyvenv-hook-dir) 
> (expand-file-name "~/.virtualenvs" (list :form (cons fn-164 args-165)) 
> (if (eql value-166 

Processed: Re: Bug#1053267 hickle: test_H5NodeFilterProxy fails with h5py 3.9.0: Unable to delete attribute (no write intent on file)

[Debian Bug Tracking System]

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

> reopen 1053267
Bug #1053267 {Done: Edward Betts } [src:hickle] hickle: 
test_H5NodeFilterProxy fails with h5py 3.9.0: Unable to delete attribute (no 
write intent on file)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions hickle/5.0.2-6.
> thanks
Stopping processing here.

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

Bug#1053267: hickle: test_H5NodeFilterProxy fails with h5py 3.9.0: Unable to delete attribute (no write intent on file)

[Drew Parsons]

reopen 1053267
thanks

hickle 5.0.2-6 was intended to fix the "No write intent on file" error 
in Bug#1053267.


But the error still occurs,
see 
https://ci.debian.net/data/autopkgtest/testing/amd64/h/hickle/38426042/log.gz


Note that this time the error occurred with old h5py 3.7.0, so there 
must be more to the problem than just h5py 3.9.0 on its own.

Bug#1053349: AWStats.pl is corrupted

[Petros Pap]

Package: awstats
Version: 7.8-3
Severity: critical

File /usr/lib/cgi-bin/awstats.pl
fils is corrupted, ends with unclosed function

sub HTMLMainBrowsers{
...
[--- fetched beginning 500 KiB of data, truncated 173.02 KiB out of 673.02
KiB ---]

dpkg --status awstats
Package: awstats
Status: install ok installed
Priority: optional
Section: web
Installed-Size: 6895
Maintainer: Debian QA Group 
Architecture: all
Version: 7.8-3
Depends: perl:any
Recommends: libnet-xwhois-perl
Suggests: apache2 | httpd, libnet-dns-perl, libnet-ip-perl,
libgeo-ipfree-perl, liburi-perl
Conffiles:
 /etc/awstats/awstats.conf 5c7c31f4f3614d9ecdfdc28ace6a6924
 /etc/awstats/awstats.conf.local a81e04b5114654f0fa2c958b06c278a4
 /etc/cron.d/awstats 85d807f22e26f7fda97f706fc4e9627a
 /etc/default/awstats d60311bc5d8dafd142da5fedf07d52b8
 /etc/logrotate.d/httpd-prerotate/awstats ba6e28347fe594c4ce57cd8fe1e32295
Description: powerful and featureful web server log analyzer
 Advanced Web Statistics (AWStats) is a powerful web server logfile
 analyzer written in perl that shows you all your web statistics including
 visits, unique visitors, pages, hits, rush hours, search engines, keywords
 used to find your site, robots, broken links and more. Gives more detailed
 information and better graphical charts than webalizer, and is easier to
use.
 Works with several web server log format as a CGI and/or from command line.
 Supports more than 30 languages.
Homepage: http://awstats.sourceforge.net/

6.1.0-12-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.52-1 (2023-09-07) x86_64
GNU/Linux


-- 
ppetros

Processed: your mail

[Debian Bug Tracking System]

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

> found 1053344 curl/8.3.0-2
Bug #1053344 [curl] curl: Block migration to testing until more information is 
publicly available about last CVE
Marked as found in versions curl/8.3.0-2.
> severity 1053344 serious
Bug #1053344 [curl] curl: Block migration to testing until more information is 
publicly available about last CVE
Severity set to 'serious' from 'normal'
> tags 1053344 upstream security
Bug #1053344 [curl] curl: Block migration to testing until more information is 
publicly available about last CVE
Added tag(s) security and upstream.
>
End of message, stopping processing here.

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

Bug#1053345: [debian bookworm] brcmfmac mmc2:0001:1: firmware: failed to load brcm/brcmfmac4330-sdio.cubietech,cubietruck-plus.bin (-2)

[Jean-Marc LACROIX]

Source: firmware-brcm80211
Version: 20230210-5
Severity: grave

Dear Debian team,

I am trying to install  firmware-brcm80211 on cubietruck-plus (cubie5)
SBC running Debian 12, because this target  contains one internal WIFI
based on Broadcom 4343 chip.

I have installed following  Debian kernel linux-image

root@Cubietruck-Plus:~# dpkg -l |grep linux-image
ii  linux-image-6.1.0-12-armmp-lpae 6.1.52-1   armhf  Linux 6.1 for 
ARMv7 multiplatform compatible SoCs supporting LPAE
ii  linux-image-armmp-lpae  6.1.52-1   armhf  Linux for ARMv7 
multiplatform compatible SoCs supporting LPAE (meta-package)


I have also installed firmware-brcm80211

root@Cubietruck-Plus:~# dpkg -l |grep firmware
ii  firmware-brcm80211  20230210-5  all Binary firmware for 
Broadcom/Cypress 802.11 wireless cards
ii  firmware-linux-free 20200122-1  all Binary firmware for 
various drivers in the Linux kernel


root@Cubietruck-Plus:~# apt policy
Fichiers du paquet :
 100 /var/lib/dpkg/status
 release a=now
Paquets épinglés :
 dbus-user-session -> 1.14.8-2~deb12u1 avec la priorité -1
 dbus-daemon -> 1.14.8-2~deb12u1 avec la priorité -1
 dbus-bin -> 1.14.8-2~deb12u1 avec la priorité -1
 systemd -> 252.12-1~deb12u1 avec la priorité -1
 dbus-session-bus-common -> 1.14.8-2~deb12u1 avec la priorité -1
 dbus-system-bus-common -> 1.14.8-2~deb12u1 avec la priorité -1
 dbus -> 1.14.8-2~deb12u1 avec la priorité -1
root@Cubietruck-Plus:~#

With  this  configuration,   when inserting  wifi   module (brcmfmac),
following kernel message is ...

root@Cubietruck-Plus:~# dmesg |tail -20
[110406.515521] sunxi-mmc 1c0f000.mmc: data error, sending stop command
[110406.521987] sunxi-mmc 1c0f000.mmc: send stop command failed
[110409.124049] mmc0: Card stuck being busy! __mmc_poll_for_busy
[110409.129871] I/O error, dev mmcblk0, sector 6060032 op 0x3:(DISCARD) 
flags 0x0 phys_seg 1 prio class 2

[110409.139464] sunxi-mmc 1c0f000.mmc: data error, sending stop command
[110409.145930] sunxi-mmc 1c0f000.mmc: send stop command failed
[143476.637560] 8021q: 802.1Q VLAN Support v1.8
[143493.253231] usbcore: deregistering interface driver brcmfmac
[143517.270761] brcmfmac: brcmf_fw_alloc_request: using 
brcm/brcmfmac4330-sdio for chip BCM4330/4
[143517.279750] brcmfmac mmc2:0001:1: firmware: failed to load 
brcm/brcmfmac4330-sdio.cubietech,cubietruck-plus.bin (-2)

[143517.283560] usbcore: registered new interface driver brcmfmac
[143517.291078] brcmfmac mmc2:0001:1: firmware: failed to load 
brcm/brcmfmac4330-sdio.cubietech,cubietruck-plus.bin (-2)
[143517.307491] brcmfmac mmc2:0001:1: Direct firmware load for 
brcm/brcmfmac4330-sdio.cubietech,cubietruck-plus.bin failed with error -2
[143517.321257] brcmfmac mmc2:0001:1: firmware: direct-loading firmware 
brcm/brcmfmac4330-sdio.bin
[143517.330276] brcmfmac mmc2:0001:1: firmware: failed to load 
brcm/brcmfmac4330-sdio.cubietech,cubietruck-plus.txt (-2)
[143517.341005] brcmfmac mmc2:0001:1: firmware: failed to load 
brcm/brcmfmac4330-sdio.cubietech,cubietruck-plus.txt (-2)
[143517.351760] brcmfmac mmc2:0001:1: firmware: failed to load 
brcm/brcmfmac4330-sdio.txt (-2)
[143517.360214] brcmfmac mmc2:0001:1: firmware: failed to load 
brcm/brcmfmac4330-sdio.txt (-2)
[143517.368617] brcmfmac mmc2:0001:1: Direct firmware load for 
brcm/brcmfmac4330-sdio.txt failed with error -2


It seems SDIO  chip is correctly detected,  but at the same time,  not
possible to  insert firmware.   As  a  result,  there  is no   network
interface.

Applying this command can do the correct job...

root@Cubietruck-Plus:~# cp 
/lib/firmware/brcm/brcmfmac4330-sdio.Prowise-PT301.txt 
/lib/firmware/brcm/brcmfmac4330-sdio.cubietech,cubietruck-plus.txt


Then...

root@Cubietruck-Plus:~# modprobe brcmfmac debug=1

[146667.262890] brcmfmac mmc2:0001:1: firmware: direct-loading firmware 
brcm/brcmfmac4330-sdio.bin
[146667.277164] brcmfmac mmc2:0001:1: firmware: direct-loading firmware 
brcm/brcmfmac4330-sdio.cubietech,cubietruck-plus.txt
[146667.288674] brcmfmac mmc2:0001:1: firmware: failed to load 
brcm/brcmfmac4330-sdio.cubietech,cubietruck-plus.clm_blob (-2)
[146667.35] brcmfmac mmc2:0001:1: firmware: failed to load 
brcm/brcmfmac4330-sdio.cubietech,cubietruck-plus.clm_blob (-2)
[146667.311405] brcmfmac mmc2:0001:1: firmware: failed to load 
brcm/brcmfmac4330-sdio.clm_blob (-2)
[146667.320559] brcmfmac mmc2:0001:1: firmware: failed to load 
brcm/brcmfmac4330-sdio.clm_blob (-2)
[146667.329501] brcmfmac mmc2:0001:1: Direct firmware load for 
brcm/brcmfmac4330-sdio.clm_blob failed with error -2
[146667.634013] brcmfmac: brcmf_c_process_clm_blob: no clm_blob 
available (err=-2), device may have limited channels available
[146667.645999] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4330/4 
wl0: Jan 23 2013 17:46:35 version 5.90.195.114 FWID 01-cafa6b3e

root@Cubietruck-Plus:~#

The bad news is of courre the same error, but ...

root@Cubietruck-Plus:~# ip link ls
1: lo:  mtu 65536 

Bug#1052878: marked as done (duplicity: FTBFS: mv: cannot stat 'lib/python*/dist-packages/duplicity/backends/README': No such file or directory)

[Debian Bug Tracking System]

Your message dated Mon, 02 Oct 2023 09:05:22 +
with message-id 
and subject line Bug#1052878: fixed in duplicity 1.2.2-2
has caused the Debian Bug report #1052878,
regarding duplicity: FTBFS: mv: cannot stat 
'lib/python*/dist-packages/duplicity/backends/README': No such file or directory
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.)


-- 
1052878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052878
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: duplicity
Version: 1.2.2-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> rm -r --verbose debian/duplicity/usr/share/doc/duplicity-*
> removed 'debian/duplicity/usr/share/doc/duplicity-1.2.2/COPYING'
> removed 'debian/duplicity/usr/share/doc/duplicity-1.2.2/CONTRIBUTING.md'
> removed 'debian/duplicity/usr/share/doc/duplicity-1.2.2/README-LOG.md'
> removed 'debian/duplicity/usr/share/doc/duplicity-1.2.2/CHANGELOG.md'
> removed 'debian/duplicity/usr/share/doc/duplicity-1.2.2/README-REPO.md'
> removed 'debian/duplicity/usr/share/doc/duplicity-1.2.2/README.md'
> removed 'debian/duplicity/usr/share/doc/duplicity-1.2.2/README-TESTING.md'
> removed directory 'debian/duplicity/usr/share/doc/duplicity-1.2.2'
> (cd debian/duplicity/usr  \
>  && mkdir -p share/doc/duplicity  \
>  && mv --verbose  \
>   lib/python*/dist-packages/duplicity/backends/README \
>   share/doc/duplicity/README.backends)
> mv: cannot stat 'lib/python*/dist-packages/duplicity/backends/README': No 
> such file or directory
> make[1]: *** [debian/rules:27: execute_after_dh_auto_install] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/09/25/duplicity_1.2.2-1_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: duplicity
Source-Version: 1.2.2-2
Done: Alexander Zangerl 

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

Debian distribution maintenance software
pp.
Alexander Zangerl  (supplier of updated duplicity 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: Mon, 02 Oct 2023 10:39:40 +0200
Source: duplicity
Architecture: source
Version: 1.2.2-2
Distribution: unstable
Urgency: medium
Maintainer: Alexander Zangerl 
Changed-By: Alexander Zangerl 
Closes: 1052878
Changes:
 duplicity (1.2.2-2) unstable; urgency=medium
 .
   * minor build adjustments (closes: #1052878)
Checksums-Sha1:
 9f2f37c2dada33a70c0de8757fdbf45530f9913c 2188 duplicity_1.2.2-2.dsc
 a8e629e7e3f5b1aa28d98e5f0061f8ff62b8206e 16328 duplicity_1.2.2-2.debian.tar.xz
 eba6edac06ad70d3f006100420750cc40df50b19 11298 
duplicity_1.2.2-2_amd64.buildinfo
Checksums-Sha256:
 b77b7e4bf9d23e5a53449f8517b7eb1809b181c4ec0e05cb657f7ffaadc94f21 2188 
duplicity_1.2.2-2.dsc
 69f052339f29bba74d95279ed6e111bb96455cf07857434b705a3c5ac94ed49f 16328 
duplicity_1.2.2-2.debian.tar.xz
 2837bf108550c5e0001334575fc2709450f0621202fa9187692df27f30e2c87e 11298 
duplicity_1.2.2-2_amd64.buildinfo
Files:
 01b1ddb88a55c2c47127266e98afe196 2188 utils optional duplicity_1.2.2-2.dsc
 

Bug#1050896: Packagesearch Copyright Statement

[Enrico Zini]

On Sun, Oct 01, 2023 at 12:42:39PM +0200, Benjamin Mesing wrote:

> Bug #1050896 now states that I should clarify copyright:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050896
> I would like to switch to GPL3+ and would like your approval for this
> license switch.

Sure, by all means please go ahead with the license switch to GPL3+.

If it can he helpful to you in the future, I'm hereby tranfering all my
copyright claims on packagesearch (if any) over to you.

Thank you for your work on packagesearch!

Enrico Zini

-- 
GPG key: 4096R/634F4BD1E7AD5568 2009-05-08 Enrico Zini 


signature.asc
Description: PGP signature

Bug#1052893: marked as done (orthanc-postgresql: FTBFS: make[1]: *** [debian/rules:38: override_dh_auto_configure] Error 2)

[Debian Bug Tracking System]

Your message dated Mon, 02 Oct 2023 08:49:53 +
with message-id 
and subject line Bug#1052893: fixed in orthanc-postgresql 5.0+dfsg-2
has caused the Debian Bug report #1052893,
regarding orthanc-postgresql: FTBFS: make[1]: *** [debian/rules:38: 
override_dh_auto_configure] 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.)


-- 
1052893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052893
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: orthanc-postgresql
Version: 5.0+dfsg-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_configure --sourcedirectory=PostgreSQL -- -DCMAKE_SKIP_RPATH:BOOL=ON 
> -DSTATIC_BUILD:BOOL=OFF -DUSE_GOOGLE_TEST_DEBIAN_PACKAGE:BOOL=ON 
> -DORTHANC_FRAMEWORK_SOURCE=system -DDEB_VERSION=5.0+dfsg-1 
> -DORTHANC_FRAMEWORK_USE_SHARED:BOOL=OFF 
> "-DORTHANC_FRAMEWORK_ADDITIONAL_LIBRARIES=boost_filesystem boost_iostreams 
> boost_locale boost_regex boost_thread jsoncpp pugixml uuid" 
> -DCMAKE_BUILD_TYPE=None  
>   cd Build && DEB_PYTHON_INSTALL_LAYOUT=deb cmake 
> -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None 
> -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
> -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF 
> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
> -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
> -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" 
> -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
> -DCMAKE_SKIP_RPATH:BOOL=ON -DSTATIC_BUILD:BOOL=OFF 
> -DUSE_GOOGLE_TEST_DEBIAN_PACKAGE:BOOL=ON -DORTHANC_FRAMEWORK_SOURCE=system 
> -DDEB_VERSION=5.0\+dfsg-1 -DORTHANC_FRAMEWORK_USE_SHARED:BOOL=OFF 
> "-DORTHANC_FRAMEWORK_ADDITIONAL_LIBRARIES=boost_filesystem boost_iostreams 
> boost_locale boost_regex boost_thread jsoncpp pugixml uuid" 
> -DCMAKE_BUILD_TYPE=None ../PostgreSQL
> CMake Deprecation Warning at CMakeLists.txt:21 (cmake_minimum_required):
>   Compatibility with CMake < 3.5 will be removed from a future version of
>   CMake.
> 
>   Update the VERSION argument  value or use a ... suffix to tell
>   CMake that the project does not need compatibility with older versions.
> 
> 
> -- The C compiler identification is GNU 13.2.0
> -- The CXX compiler identification is GNU 13.2.0
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Check for working C compiler: /usr/bin/cc - skipped
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Check for working CXX compiler: /usr/bin/c++ - skipped
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> CMake Warning (dev) at 
> /<>/Resources/Orthanc/CMake/DownloadOrthancFramework.cmake:478 
> (include):
>   Policy CMP0148 is not set: The FindPythonInterp and FindPythonLibs modules
>   are removed.  Run "cmake --help-policy CMP0148" for policy details.  Use
>   the cmake_policy command to set the policy and suppress this warning.
> 
> Call Stack (most recent call first):
>   /<>/Resources/CMake/DatabasesFrameworkParameters.cmake:26 
> (include)
>   /<>/Resources/CMake/DatabasesPluginParameters.cmake:31 
> (include)
>   CMakeLists.txt:39 (include)
> This warning is for project developers.  Use -Wno-dev to suppress it.
> 
> -- Found PythonInterp: /usr/bin/python3 (found version "3.11.5") 
> JsonCpp include dir: /usr/include/jsoncpp
> -- Looking for C++ include /usr/include/jsoncpp/json/reader.h
> -- Looking for C++ include /usr/include/jsoncpp/json/reader.h - found
> Orthanc framework include dir: /usr/include/orthanc-framework
> Path to the Debian Google Test sources: /usr/src/gtest
> Path to the Debian Google Test includes: /usr/include/gtest
> -- Found OpenSSL: /usr/lib/x86_64-linux-gnu/libcrypto.so (found version 
> "3.0.11")  
> -- Looking for C++ include google/protobuf/any.h
> -- Looking for C++ include google/protobuf/any.h - found
> -- Performing Test HAVE_PROTOBUF_LIB
> -- Performing Test HAVE_PROTOBUF_LIB - Success
> -- Found PostgreSQL: /usr/lib/x86_64-linux-gnu/libpq.so (found version 
> "16.0")  
> -- Looking for /usr/include/orthanc/OrthancCDatabasePlugin.h
> -- Looking for /usr/include/orthanc/OrthancCDatabasePlugin.h - found
> Setting the version of the libraries to 5.0
> -- Configuring done 

Bug#1052893: marked as pending in orthanc-postgresql

[Nilesh Patra]

Control: tag -1 pending

Hello,

Bug #1052893 in orthanc-postgresql 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/orthanc-postgresql/-/commit/66f5ff8ba3a7ca3c6383b8e8af88e812ab8f9117


Fix FTBFS with postgres 16 (Closes: #1052893)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1052893

Processed: Bug#1052893 marked as pending in orthanc-postgresql

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1052893 [src:orthanc-postgresql] orthanc-postgresql: FTBFS: make[1]: *** 
[debian/rules:38: override_dh_auto_configure] Error 2
Added tag(s) pending.

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

Processed: Re: Bug#1053341: h5py FTBFS on 32-bit archs: OverflowError: Python int too large to convert to C ssize_t

[Debian Bug Tracking System]

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

> forwarded 1053341 https://github.com/h5py/h5py/issues/2315
Bug #1053341 [src:h5py] h5py FTBFS on 32-bit archs: OverflowError: Python int 
too large to convert to C ssize_t
Set Bug forwarded-to-address to 'https://github.com/h5py/h5py/issues/2315'.
> thanks
Stopping processing here.

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

Bug#1053341: h5py FTBFS on 32-bit archs: OverflowError: Python int too large to convert to C ssize_t

[Drew Parsons]

forwarded 1053341 https://github.com/h5py/h5py/issues/2315
thanks

I suspect it can be resolved by casting the int returned by addressof to 
ctypes.c_int.  Waiting to hear what upstream thinks.


Note it's not quite as simple as "32-bit".  sparc64 is also affected.

Bug#1052232: marked as done (FTBFS with recent context)

[Debian Bug Tracking System]

Your message dated Mon, 02 Oct 2023 07:48:59 +
with message-id 
and subject line Bug#1052232: fixed in mlpost 0.9-5
has caused the Debian Bug report #1052232,
regarding FTBFS with recent context
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.)


-- 
1052232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052232
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mlpost
Version: 0.9-4
Severity: important
Tags: ftbfs
User: debian-ocaml-ma...@lists.debian.org
Usertags: ocaml-4.14.1-transition

Dear Maintainer,

Your package FTBFS with OCaml 4.14.1 with the following error:
> [...]
> File "examples/dune.boxes.inc", line 2, characters 0-205:
> 2 | (rule (targets  ps_boxes1.mps ps_boxes2.mps ps_boxes3.mps ps_boxes4.mps 
> ps_boxes5.mps ps_boxes6.mps ps_boxes7.mps ps_boxes8.mps ps_boxes9.mps) (deps 
> boxes.exe) (action (run ./boxes.exe -ps -prefix "ps_")))
> 
> ^
> (cd _build/default/examples && ./boxes.exe -ps -prefix ps_)
> Fatal error: exception Unix.Unix_error(Unix.ENOENT, "rename", "boxes.1")
> File "examples/dune.tree.inc", line 2, characters 0-264:
> 2 | (rule (targets  ps_tree1.mps ps_tree2.mps ps_tree3.mps ps_tree4.mps 
> ps_tree5.mps ps_tree6.mps ps_tree7.mps ps_tree8.mps ps_tree9.mps 
> ps_tree10.mps ps_tree11.mps ps_tree12.mps ps_tree13.mps ps_tree14.mps) (deps 
> tree.exe) (action (run ./tree.exe -ps -prefix "ps_")))
> 
> 
> (cd _build/default/examples && ./tree.exe -ps -prefix ps_)
> Fatal error: exception Unix.Unix_error(Unix.ENOENT, "rename", "tree.1")
> dh_auto_test: error: dune runtest -j 8 -p mlpost returned exit code 1
> make: *** [debian/rules:7: binary] Error 25
> dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
> 2

Packages rebuilt with OCaml 4.14.1 are available at:

  http://ocaml.debian.net/transitions/ocaml-4.14.1/


Cheers,

-- 
Stéphane

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

Kernel: Linux 6.4.0-4-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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
--- End Message ---
--- Begin Message ---
Source: mlpost
Source-Version: 0.9-5
Done: Stéphane Glondu 

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

Debian distribution maintenance software
pp.
Stéphane Glondu  (supplier of updated mlpost 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: Mon, 02 Oct 2023 09:29:59 +0200
Source: mlpost
Architecture: source
Version: 0.9-5
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Stéphane Glondu 
Closes: 1052232
Changes:
 mlpost (0.9-5) unstable; urgency=medium
 .
   * Fix compilation with recent context (Closes: #1052232)
Checksums-Sha1:
 43cc32874f4522cf4662b416ad4f2e397d2b1972 2148 mlpost_0.9-5.dsc
 f83c3f0f29444c5684b76a0ed78da84c7f5c7dc2 6272 mlpost_0.9-5.debian.tar.xz
Checksums-Sha256:
 040b9a653f48fd845cd4a81a8016c5b7d98d1d28f61b4ade08a8e73d069f2277 2148 
mlpost_0.9-5.dsc
 614dc9264dea96f862886a441313b07fc9eac2e5e0dee58770067b383e1e5504 6272 
mlpost_0.9-5.debian.tar.xz
Files:
 9ed0326c45d0651481e4e6261508fa41 2148 tex optional mlpost_0.9-5.dsc
 55d50ec1f700e4d8de376292939a3c11 6272 tex optional mlpost_0.9-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

Processed: Bug#1052232 marked as pending in mlpost

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1052232 [src:mlpost] FTBFS with recent context
Added tag(s) pending.

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

Bug#1052232: marked as pending in mlpost

[Stéphane Glondu]

Control: tag -1 pending

Hello,

Bug #1052232 in mlpost 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/ocaml-team/mlpost/-/commit/7feb66a76d05eacfe5cafcd0c16b7ae3820a2c4a


Fix compilation with recent context (Closes: #1052232)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1052232

Bug#1053267: hickle: test_H5NodeFilterProxy fails with h5py 3.9.0: Unable to delete attribute (no write intent on file)

[Nilesh Patra]

On 10/1/23 23:51, Edward Betts wrote:

Thanks for the patch.

I've applied it and uploaded a new version of hickle.


Now this new version seems to fail (its test[1]) against the older version of 
h5py (in testing)
and is unable to migrate along with it. In principle a versioned depends could 
be
added against h5py to fix this but this is IMHO _not_ needed since this was 
just a test
specific thing that chokes.
This was an oversight on my end.

I've attached a new patch which should get it passing with both the older and 
newer versions
of h5py. Could you please consider to apply it and upload if it looks OK to you?
Could you as well push your commits to salsa?

[1]: 
https://ci.debian.net/data/autopkgtest/testing/amd64/h/hickle/38396024/log.gz

Thanks,
Nilesh
--- a/hickle/tests/test_01_hickle_helpers.py
+++ b/hickle/tests/test_01_hickle_helpers.py
@@ -121,16 +121,17 @@
 # load data and try to directly modify 'type' and 'base_type' Attributes
 # which will fail cause hdf5 file is opened for read only
 h5_node = h5_data['somedata']
-with pytest.raises(OSError):
+pytest_errclass = KeyError if h5py.__version__ >= '3.9.0' else OSError
+with pytest.raises(pytest_errclass):
 try:
 h5_node.attrs['type'] = pickle.dumps(list)
 except RuntimeError as re:
-raise OSError(re).with_traceback(re.__traceback__)
-with pytest.raises(OSError):
+raise pytest_errclass(re).with_traceback(re.__traceback__)
+with pytest.raises(pytest_errclass):
 try:
 h5_node.attrs['base_type'] = b'list'
 except RuntimeError as re:
-raise OSError(re).with_traceback(re.__traceback__)
+raise pytest_errclass(re).with_traceback(re.__traceback__)
 
 # verify that 'type' expands to tuple before running
 # the remaining tests

Processed: Re: #1040057: slixmpp: autopkgtest regression on arm64: Segmentation fault

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #1040057 [src:slixmpp] slixmpp: autopkgtest regression on arm64: 
Segmentation fault
Severity set to 'normal' from 'serious'
> tag -1 + help
Bug #1040057 [src:slixmpp] slixmpp: autopkgtest regression on arm64: 
Segmentation fault
Added tag(s) help.
> tag -1 + moreinfo
Bug #1040057 [src:slixmpp] slixmpp: autopkgtest regression on arm64: 
Segmentation fault
Added tag(s) moreinfo.

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

Bug#1040057: #1040057: slixmpp: autopkgtest regression on arm64: Segmentation fault

[Martin]

Control: severity -1 normal
Control: tag -1 + help
Control: tag -1 + moreinfo

Finally, I had some time to run the autopkgtest suite on my own arm64
machine (MNT reform). It did not segfault, so I assume a specific
problem with the C/I system. I have no idea how to debug this, help is
appreciated!

Bug#1053341: h5py FTBFS on 32-bit archs: OverflowError: Python int too large to convert to C ssize_t

[Nilesh Patra]

Source: h5py
Version: 3.9.0-2
Severity: serious
X-Debbugs-Cc: dpars...@debian.org

Hi,

The new release of h5py FTBFS on all 32-bit archs.
In particular, it fails its test-suite with:

=== FAILURES ===
_ test_register_filter _

def test_register_filter():
filter_id = 256  # Test ID

@H5ZFuncT
def failing_filter_callback(flags, cd_nelemts, cd_values, nbytes, 
buf_size, buf):
return 0

dummy_filter_class = H5ZClass2T(
version=h5z.CLASS_T_VERS,
id_=filter_id,
encoder_present=1,
decoder_present=1,
name=b"dummy filter",
can_apply=None,
set_local=None,
filter_=failing_filter_callback,
)

>   h5z.register_filter(addressof(dummy_filter_class))

build/h5py/_debian_h5py_serial/tests/test_h5z.py:65: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
h5py/_debian_h5py_serial/_objects.pyx:54: in 
h5py._debian_h5py_serial._objects.with_phil.wrapper
???
h5py/_debian_h5py_serial/_objects.pyx:55: in 
h5py._debian_h5py_serial._objects.with_phil.wrapper
???
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

>   ???
E   OverflowError: Python int too large to convert to C ssize_t

h5py/_debian_h5py_serial/h5z.pyx:102: OverflowError

Full log: 
https://buildd.debian.org/status/fetch.php?pkg=h5py=armel=3.9.0-2=1696051380=0

-- System Information:
Debian Release: 12.0
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: amd64 (x86_64)

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