Processed: Debian bugs control

2024-04-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> fixed 1053183 galera-4/26.4.18-1
Bug #1053183 [src:galera-4] galera-4: FTBFS on sparc64: one of sever post-build 
test fail
Marked as fixed in versions galera-4/26.4.18-1.
> tags 1069535 wontfix
Bug #1069535 [src:galera-3] galera-3: FTBFS on armel: dh_auto_test: error: cd 
obj-arm-linux-gnueabi && make -j1 test ARGS\+=--verbose ARGS\+=-j1 
ARGS=--output-on-failure returned exit code 2
Added tag(s) wontfix.
> thanks
Stopping processing here.

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



Bug#1069368: marked as done (golang-github-golang-protobuf-1-5: FTBFS on arm64: make: *** [debian/rules:6: binary] Error 25)

2024-04-21 Thread Debian Bug Tracking System
Your message dated Mon, 22 Apr 2024 04:34:06 +
with message-id 
and subject line Bug#1069368: fixed in golang-github-golang-protobuf-1-5 1.5.4-1
has caused the Debian Bug report #1069368,
regarding golang-github-golang-protobuf-1-5: FTBFS on arm64: make: *** 
[debian/rules:6: 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.)


-- 
1069368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069368
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-golang-protobuf-1-5
Version: 1.5.3-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --builddirectory=_build --buildsystem=golang
>dh_update_autotools_config -O--builddirectory=_build -O--buildsystem=golang
>dh_autoreconf -O--builddirectory=_build -O--buildsystem=golang
>dh_auto_configure -O--builddirectory=_build -O--buildsystem=golang
>dh_auto_build -O--builddirectory=_build -O--buildsystem=golang
>   cd _build && go install -trimpath -v -p 4 
> github.com/golang/protobuf/descriptor 
> github.com/golang/protobuf/internal/gengogrpc 
> github.com/golang/protobuf/internal/testprotos/jsonpb_proto 
> github.com/golang/protobuf/internal/testprotos/proto2_proto 
> github.com/golang/protobuf/internal/testprotos/proto3_proto 
> github.com/golang/protobuf/jsonpb github.com/golang/protobuf/proto 
> github.com/golang/protobuf/protoc-gen-go 
> github.com/golang/protobuf/protoc-gen-go/descriptor 
> github.com/golang/protobuf/protoc-gen-go/generator 
> github.com/golang/protobuf/protoc-gen-go/generator/internal/remap 
> github.com/golang/protobuf/protoc-gen-go/grpc 
> github.com/golang/protobuf/protoc-gen-go/plugin 
> github.com/golang/protobuf/ptypes github.com/golang/protobuf/ptypes/any 
> github.com/golang/protobuf/ptypes/duration 
> github.com/golang/protobuf/ptypes/empty 
> github.com/golang/protobuf/ptypes/struct 
> github.com/golang/protobuf/ptypes/timestamp 
> github.com/golang/protobuf/ptypes/wrappers
> internal/goarch
> internal/cpu
> internal/unsafeheader
> internal/coverage/rtcov
> internal/chacha8rand
> internal/abi
> internal/godebugs
> internal/goexperiment
> internal/goos
> internal/bytealg
> runtime/internal/atomic
> runtime/internal/math
> runtime/internal/sys
> runtime/internal/syscall
> internal/race
> sync/atomic
> unicode
> unicode/utf8
> internal/itoa
> math/bits
> cmp
> encoding
> runtime
> slices
> math
> unicode/utf16
> google.golang.org/protobuf/internal/flags
> google.golang.org/protobuf/internal/set
> internal/gover
> internal/goversion
> crypto/internal/alias
> crypto/subtle
> crypto/internal/boring/sig
> internal/platform
> log/internal
> internal/reflectlite
> sync
> internal/testlog
> google.golang.org/protobuf/internal/pragma
> internal/bisect
> errors
> sort
> internal/godebug
> io
> strconv
> internal/oserror
> syscall
> bytes
> strings
> internal/safefilepath
> reflect
> path
> bufio
> hash
> hash/crc32
> hash/fnv
> go/build/constraint
> text/tabwriter
> container/heap
> math/rand
> go/version
> internal/types/errors
> regexp/syntax
> internal/syscall/unix
> time
> internal/syscall/execenv
> crypto
> regexp
> io/fs
> internal/poll
> internal/fmtsort
> encoding/binary
> embed
> context
> google.golang.org/protobuf/internal/editiondefaults
> os
> encoding/base64
> crypto/cipher
> crypto/internal/boring
> crypto/sha256
> google.golang.org/protobuf/internal/detrand
> io/ioutil
> fmt
> path/filepath
> internal/lazyregexp
> os/exec
> internal/goroot
> google.golang.org/protobuf/internal/errors
> go/token
> encoding/json
> compress/flate
> google.golang.org/protobuf/encoding/protowire
> google.golang.org/protobuf/reflect/protoreflect
> google.golang.org/protobuf/internal/version
> go/scanner
> compress/gzip
> go/doc/comment
> go/ast
> google.golang.org/protobuf/internal/encoding/messageset
> google.golang.org/protobuf/internal/strs
> google.golang.org/protobuf/internal/encoding/text
> google.golang.org/protobuf/internal/genid
> google.golang.org/protobuf/internal/order
> google.golang.org/protobuf/reflect/protoregistry
> google.golang.org/protobuf/runtime/protoiface
> google.golang.org/protobuf/internal/descfmt
> google.golang.org/protobuf/internal/descopts
> google.golang.org/protobuf/internal/encoding/defval
> go/internal/typeparams
> go/printer
> google.golang.org/protobuf/proto
> go/parser
> math/big
> 

Processed: add patch

2024-04-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 1061025 patch
Bug #1061025 [src:libcommons-logging-java] httpcomponents-client: FTBFS: make: 
*** [debian/rules:4: build] Error 25
Added tag(s) patch.
>
End of message, stopping processing here.

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



Bug#1069368: Updating golang-github-golang-protobuf-1-5 to fix FTBFS

2024-04-21 Thread Anthony Fok
On Sun, Apr 21, 2024 at 10:03 AM Mathias Gibbens  wrote:
>
> On Sat, 2024-04-20 at 22:40 +0800, Shengjing Zhu wrote:
> > On Sat, Apr 20, 2024 at 10:28 PM Mathias Gibbens  wrote:
> > >
> > > Hi Anthony,
> > >
> > >   A few weeks ago you uploaded a new version of golang-google-protobuf
> > > to unstable which caused a FTBFS in golang-github-golang-protobuf-1-5
> > > v1.5.3 [1,2,3]. This has been blocking the transition of various golang
> > > packages from unstable to testing.
> > >
> > >   I've verified that v1.5.4 of golang-github-golang-protobuf-1-5 builds
> > > fine on my amd64 system. `build-rdeps golang-github-golang-protobuf-1-
> > > 5-dev` identifies 219 rdeps in main, so I haven't kicked off a `ratt`
> > > run testing for any build regressions with the newer version yet.
> > >
> >
> > This is a known regression in 1.5.3, see
> > https://github.com/golang/protobuf/issues/1596#issuecomment-1981208282
>
>   Since that appears to be the only change in v1.5.4, would there be
> any concerns with uploading that version to unstable? This breakage is
> starting to cause FTBFS bugs to be filed against affected packages,
> such as hugo (#1069371).
>
> Mathias

Hi Reinhard, Mathias and Shengjing,

Thank you for bringing this to my attention, and sorry for my late response!
Thank you also for your detailed investigation!  Very much appreciated!

I don't see any concern uploading v1.5.4 especially how it fixes the
regression and FTBFS
with v1.5.3, and I'll be uploading golang-github-golang-protobuf-1-5
1.5.4-1 very shortly.

Cheers,
Anthony



Bug#1065799: marked as done (ncrack: FTBFS on arm{el,hf}: configure: error: *** compiler cannot create working executables, check config.log ***)

2024-04-21 Thread Debian Bug Tracking System
Your message dated Mon, 22 Apr 2024 02:34:24 +
with message-id 
and subject line Bug#1065799: fixed in ncrack 0.7+debian-6
has caused the Debian Bug report #1065799,
regarding ncrack: FTBFS on arm{el,hf}: configure: error: *** compiler cannot 
create working executables, check config.log ***
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=ncrack=armhf=0.7%2Bdebian-5%2Bb1=1709992455=0

checking for utmpx.h... yes
checking for vis.h... no
checking for lastlog.h... yes
checking for sys/ptms.h... no
checking for login_cap.h... no
checking for sys/mount.h... yes
checking for sys/un.h... yes
checking for linux/if_tun.h... yes
checking for linux/seccomp.h... yes
checking for linux/filter.h... yes
checking for linux/audit.h... yes
checking for prctl... yes
checking for seccomp architecture... "AUDIT_ARCH_ARM"
checking compiler and flags for sanity... no
configure: error: *** compiler cannot create working executables, check 
config.log ***
configure: error: ./configure failed for opensshlib
tail -v -n \+0 config.log
==> config.log <==

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: ncrack
Source-Version: 0.7+debian-6
Done: Arnaud Rebillout 

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

Debian distribution maintenance software
pp.
Arnaud Rebillout  (supplier of updated ncrack 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, 22 Apr 2024 08:59:25 +0700
Source: ncrack
Architecture: source
Version: 0.7+debian-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Arnaud Rebillout 
Closes: 1065799
Changes:
 ncrack (0.7+debian-6) unstable; urgency=medium
 .
   [ Vladimir Petko ]
   * d/p/{implicit-declaration-in-configure.patch, implicit-declaration-
 xmalloc.patch}: add missing headers and defines to resolve -
 Werror=implicit-function-declaration build failures (Closes:
 #1065799).
Checksums-Sha1:
 ca7dcf02216a45c8604a473b6313856476ef745e 1981 ncrack_0.7+debian-6.dsc
 b86cbe496f10b1e91698aa47241c79deaf1406c1 18368 
ncrack_0.7+debian-6.debian.tar.xz
 dc71067d66e5a508cea23175be51ea42f12613f1 6521 
ncrack_0.7+debian-6_source.buildinfo
Checksums-Sha256:
 60a6ac3348db68e6305bfb4a5afe7051ed6b3f83b050ae03282655580fab29e3 1981 
ncrack_0.7+debian-6.dsc
 94aa57df05fea534664dcb93f70880a22e80cbc144fda2254c89d65030bb2f1f 18368 
ncrack_0.7+debian-6.debian.tar.xz
 5ef07a634dcfb5789e2fe1078a42f1ec297e2f28f94f86ab4ce0c6d052041c36 6521 
ncrack_0.7+debian-6_source.buildinfo
Files:
 9a4414d222032421e81621d040cdfaf6 1981 net optional ncrack_0.7+debian-6.dsc
 4214d0ed4ac01aec244ffc0412d8a385 18368 net optional 
ncrack_0.7+debian-6.debian.tar.xz
 678cae5ed5c62d5638955d07396d486c 6521 net optional 
ncrack_0.7+debian-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE0Kl7ndbut+9n4bYs5yXoeRRgAhYFAmYlxNARHGFybmF1ZHJA
a2FsaS5vcmcACgkQ5yXoeRRgAhZdCxAAkY7IJTo0vtd82E4ddzeKtS2AxyGaTGbR
fXukJFYMmyjRAO/lZpd3RM+1j0KDgbG6eZr+gAv/+YFP+WOJK1gwSoiTBJcAZyWC
LW0Re6gl/WuxSDOMRuiEd2AS7CtMfvlTmfZmTCEtnnAcHUuE2HYH33SsoQYcp9ys
hiep8AdtbLG8UbEoCU7hCHXStqXcAeZPEWRtiCeIvsla1pczmIbUCQVf7wrS2bN/
zIWO/rRsdH7GY1pKW6T0Cz+lb6MU17bBs9wZBPxMzIDBc1005FqayU4JAANpUpq9
xmZv4koNCjmEOrFrfKtfuyB+C0xoAVigC8rWOgJmmO8F6DK81+dMoVGtP/DgeqKr
niDlY+nHdFxhjgV8/b567P3VMcCXDy5dY7Ebb9+jOrelaY/svW8Mq4Sa01lqgY2o
NW1mXGXFwqZou6s0lr5P/oBGQS+ttoRmgaRaYb7sQEUXHlSiyJNLKNMekILRHKcx
EuTwn+wwcufIhyDKze5vGNIKUjDQl6dRnzPfBH66JaEYhY6dwG6rFr6S8C33QmAt
mj1yf0pcM30tCZjH7c3i6HGkkt9PDIhOvnuoJnwHy5/mgEw5Nuy+bGlBT30VziL7
TrFsd0RlTEjSBfYMDr0kxEs36nEOIaDv7DD7oE6OwhETWFOBBiq5BgQY6rJMwV45
7E0Y/gUn12M=
=GkUR
-END PGP SIGNATURE-



pgpGVfCDXsnVQ.pgp

Bug#1066613: marked as done (ncrack: FTBFS: configure: error: *** compiler cannot create working executables, check config.log ***)

2024-04-21 Thread Debian Bug Tracking System
Your message dated Mon, 22 Apr 2024 02:34:24 +
with message-id 
and subject line Bug#1065799: fixed in ncrack 0.7+debian-6
has caused the Debian Bug report #1065799,
regarding ncrack: FTBFS: configure: error: *** compiler cannot create working 
executables, check config.log ***
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.)


-- 
1065799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065799
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ncrack
Version: 0.7+debian-5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> checking for linux/filter.h... yes
> checking for linux/audit.h... yes
> checking for prctl... yes
> checking for seccomp architecture... "AUDIT_ARCH_X86_64"
> checking compiler and flags for sanity... no
> configure: error: *** compiler cannot create working executables, check 
> config.log ***
> configure: error: ./configure failed for opensshlib
>   tail -v -n \+0 config.log


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/ncrack_0.7+debian-5_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=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: ncrack
Source-Version: 0.7+debian-6
Done: Arnaud Rebillout 

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

Debian distribution maintenance software
pp.
Arnaud Rebillout  (supplier of updated ncrack 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, 22 Apr 2024 08:59:25 +0700
Source: ncrack
Architecture: source
Version: 0.7+debian-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Arnaud Rebillout 
Closes: 1065799
Changes:
 ncrack (0.7+debian-6) unstable; urgency=medium
 .
   [ Vladimir Petko ]
   * d/p/{implicit-declaration-in-configure.patch, implicit-declaration-
 xmalloc.patch}: add missing headers and defines to resolve -
 Werror=implicit-function-declaration build failures (Closes:
 #1065799).
Checksums-Sha1:
 ca7dcf02216a45c8604a473b6313856476ef745e 1981 ncrack_0.7+debian-6.dsc
 b86cbe496f10b1e91698aa47241c79deaf1406c1 18368 
ncrack_0.7+debian-6.debian.tar.xz
 dc71067d66e5a508cea23175be51ea42f12613f1 6521 
ncrack_0.7+debian-6_source.buildinfo
Checksums-Sha256:
 60a6ac3348db68e6305bfb4a5afe7051ed6b3f83b050ae03282655580fab29e3 1981 
ncrack_0.7+debian-6.dsc
 94aa57df05fea534664dcb93f70880a22e80cbc144fda2254c89d65030bb2f1f 18368 
ncrack_0.7+debian-6.debian.tar.xz
 5ef07a634dcfb5789e2fe1078a42f1ec297e2f28f94f86ab4ce0c6d052041c36 6521 
ncrack_0.7+debian-6_source.buildinfo
Files:
 9a4414d222032421e81621d040cdfaf6 1981 net optional ncrack_0.7+debian-6.dsc
 4214d0ed4ac01aec244ffc0412d8a385 18368 net optional 
ncrack_0.7+debian-6.debian.tar.xz
 678cae5ed5c62d5638955d07396d486c 6521 net optional 
ncrack_0.7+debian-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE0Kl7ndbut+9n4bYs5yXoeRRgAhYFAmYlxNARHGFybmF1ZHJA
a2FsaS5vcmcACgkQ5yXoeRRgAhZdCxAAkY7IJTo0vtd82E4ddzeKtS2AxyGaTGbR
fXukJFYMmyjRAO/lZpd3RM+1j0KDgbG6eZr+gAv/+YFP+WOJK1gwSoiTBJcAZyWC
LW0Re6gl/WuxSDOMRuiEd2AS7CtMfvlTmfZmTCEtnnAcHUuE2HYH33SsoQYcp9ys
hiep8AdtbLG8UbEoCU7hCHXStqXcAeZPEWRtiCeIvsla1pczmIbUCQVf7wrS2bN/

Bug#1068037: marked as done (FTBFS: error: implicit declaration of function ‘get_file_lines’)

2024-04-21 Thread Debian Bug Tracking System
Your message dated Mon, 22 Apr 2024 02:34:12 +
with message-id 
and subject line Bug#1068037: fixed in mdk4 4.2-4
has caused the Debian Bug report #1068037,
regarding FTBFS: error: implicit declaration of function ‘get_file_lines’
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.)


-- 
1068037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068037
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mdk4
Version: 4.2-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=mdk4=arm64=4.2-3%2Bb2=1711715545=0

poc.c:148:30: error: implicit declaration of function ‘get_file_lines’
[-Werror=implicit-function-declaration]
  148 | file_lines = get_file_lines(file_name);
  |  ^~
poc.c:160:38: warning: pointer targets in passing argument 1 of ‘fgets’ differ
in signedness [-Wpointer-sign]
  160 | if(fgets(buf, sizeof(buf), fp1))
  |  ^~~
  |  |
  |  unsigned char *
In file included from /usr/include/stdio.h:906,
 from poc.c:1:
/usr/include/aarch64-linux-gnu/bits/stdio2.h:209:25: note: expected ‘char *
restrict’ but argument is of type ‘unsigned char *’
  209 | fgets (char *__restrict __s, int __n, FILE *__restrict __stream)
  |~^~~
poc.c:165:59: error: implicit declaration of function ‘str_to_hex’
[-Werror=implicit-function-declaration]
  165 | poc_pkts[i].pkts[j].len =
str_to_hex(buf, poc_pkts[i].pkts[j].data, sizeof(poc_pkts[i].pkts[j].data));
  |   ^~


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

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

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

Debian distribution maintenance software
pp.
Arnaud Rebillout  (supplier of updated mdk4 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, 22 Apr 2024 08:48:30 +0700
Source: mdk4
Architecture: source
Version: 4.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Arnaud Rebillout 
Closes: 1068037
Changes:
 mdk4 (4.2-4) unstable; urgency=medium
 .
   * Import upstream patch "fix x mode bug"
   * Add patch to fix implicit-function-declaration (Closes: #1068037)
   * Build-Depends: pkg-config => pkgconf
Checksums-Sha1:
 44fbcfd2f317a513527cbf88538c46eb947ce650 1940 mdk4_4.2-4.dsc
 0ec920142dd3f9e657f33359a6fd0775959ab4ab 6216 mdk4_4.2-4.debian.tar.xz
 7fe1b3a2b79800e6aa9425932a8d8bb0834d991f 6508 mdk4_4.2-4_source.buildinfo
Checksums-Sha256:
 18a5284ef23d6800fd0d9cd39753f832e8e05a39baa5e6ab24395ac350754b9f 1940 
mdk4_4.2-4.dsc
 9fd5512b8f0d7c9f008616f57868d09b3563daa8e461b536afd821890bf42e0b 6216 
mdk4_4.2-4.debian.tar.xz
 e5670dcf47de6bc32b2e43d3a73f72f93a62488bee70e94f9d6eddf976dc6dfa 6508 
mdk4_4.2-4_source.buildinfo
Files:
 4adf352b95f76d79232db9003155cc7c 1940 net optional mdk4_4.2-4.dsc
 e6bd686ee1056c069e265e19a149bb57 6216 net optional mdk4_4.2-4.debian.tar.xz
 c5009f8e27348f56f5addc51eda7dc90 6508 net optional mdk4_4.2-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE0Kl7ndbut+9n4bYs5yXoeRRgAhYFAmYlwtIRHGFybmF1ZHJA
a2FsaS5vcmcACgkQ5yXoeRRgAhZeEg/+KmovqKqY3LZFt64F63jKjtMoNjw5eN3u

Bug#1069444: marked as done (rust-libpulse-binding: FTBFS on armhf: dh_auto_test: error: /usr/share/cargo/bin/cargo test --all returned exit code 101)

2024-04-21 Thread Debian Bug Tracking System
Your message dated Mon, 22 Apr 2024 01:50:38 +
with message-id 
and subject line Bug#1069444: fixed in rust-libpulse-binding 2.28.1-3
has caused the Debian Bug report #1069444,
regarding rust-libpulse-binding: FTBFS on armhf: dh_auto_test: error: 
/usr/share/cargo/bin/cargo test --all returned exit code 101
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.)


-- 
1069444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069444
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-libpulse-binding
Version: 2.28.1-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test -- test --all
> debian cargo wrapper: options, profiles, parallel, lto: ['parallel=4'] [] 
> ['-j4'] 0
> debian cargo wrapper: rust_type, gnu_type: armv7-unknown-linux-gnueabihf, 
> arm-linux-gnueabihf
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', 
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'test', '--verbose', '--verbose', 
> '-j4', '--target', 'armv7-unknown-linux-gnueabihf', '--all'],) {}
>Compiling proc-macro2 v1.0.76
>Compiling unicode-ident v1.0.12
>Compiling autocfg v1.1.0
>Compiling syn v1.0.109
>  Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=build_script_build 
> CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/proc-macro2-1.0.76 
> CARGO_PKG_AUTHORS='David Tolnay :Alex Crichton 
> ' CARGO_PKG_DESCRIPTION='A substitute implementation 
> of the compiler'\''s `proc_macro` API to decouple token-based libraries from 
> the procedural macro use case.' CARGO_PKG_HOMEPAGE='' CARGO_PKG_LICENSE='MIT 
> OR Apache-2.0' CARGO_PKG_LICENSE_FILE='' CARGO_PKG_NAME=proc-macro2 
> CARGO_PKG_REPOSITORY='https://github.com/dtolnay/proc-macro2' 
> CARGO_PKG_RUST_VERSION=1.56 CARGO_PKG_VERSION=1.0.76 
> CARGO_PKG_VERSION_MAJOR=1 CARGO_PKG_VERSION_MINOR=0 
> CARGO_PKG_VERSION_PATCH=76 CARGO_PKG_VERSION_PRE='' 
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' rustc 
> --crate-name build_script_build --edition=2021 
> /<>/debian/cargo_registry/proc-macro2-1.0.76/build.rs 
> --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat 
> --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 
> --cfg 'feature="default"' --cfg 'feature="proc-macro"' -C 
> metadata=5af698d564d3f59d -C extra-filename=-5af698d564d3f59d --out-dir 
> /<>/target/debug/build/proc-macro2-5af698d564d3f59d -L 
> dependency=/<>/target/debug/deps --cap-lints warn`
>  Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=unicode_ident 
> CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/unicode-ident-1.0.12
>  CARGO_PKG_AUTHORS='David Tolnay ' 
> CARGO_PKG_DESCRIPTION='Determine whether characters have the XID_Start or 
> XID_Continue properties according to Unicode Standard Annex #31' 
> CARGO_PKG_HOMEPAGE='' CARGO_PKG_LICENSE='(MIT OR Apache-2.0) AND 
> Unicode-DFS-2016' CARGO_PKG_LICENSE_FILE='' CARGO_PKG_NAME=unicode-ident 
> CARGO_PKG_REPOSITORY='https://github.com/dtolnay/unicode-ident' 
> CARGO_PKG_RUST_VERSION=1.31 CARGO_PKG_VERSION=1.0.12 
> CARGO_PKG_VERSION_MAJOR=1 CARGO_PKG_VERSION_MINOR=0 
> CARGO_PKG_VERSION_PATCH=12 CARGO_PKG_VERSION_PRE='' 
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' rustc 
> --crate-name unicode_ident --edition=2018 
> /<>/debian/cargo_registry/unicode-ident-1.0.12/src/lib.rs 
> --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat 
> --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C 
> debuginfo=2 -C metadata=ba2991cf6fcfddae -C extra-filename=-ba2991cf6fcfddae 
> --out-dir /<>/target/debug/deps -L 
> dependency=/<>/target/debug/deps --cap-lints warn`
>  Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=autocfg 
> CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/autocfg-1.1.0 
> CARGO_PKG_AUTHORS='Josh Stone ' 
> CARGO_PKG_DESCRIPTION='Automatic cfg for Rust compiler features' 
> CARGO_PKG_HOMEPAGE='' CARGO_PKG_LICENSE='Apache-2.0 OR MIT' 
> CARGO_PKG_LICENSE_FILE='' CARGO_PKG_NAME=autocfg 
> CARGO_PKG_REPOSITORY='https://github.com/cuviper/autocfg' 
> CARGO_PKG_RUST_VERSION='' CARGO_PKG_VERSION=1.1.0 CARGO_PKG_VERSION_MAJOR=1 
> CARGO_PKG_VERSION_MINOR=1 CARGO_PKG_VERSION_PATCH=0 CARGO_PKG_VERSION_PRE='' 
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' rustc 
> --crate-name autocfg 
> /<>/debian/cargo_registry/autocfg-1.1.0/src/lib.rs 
> --error-format=json 

Processed: Bug#1068037 marked as pending in mdk4

2024-04-21 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1068037 [src:mdk4] FTBFS: error: implicit declaration of function 
‘get_file_lines’
Added tag(s) pending.

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



Bug#1068037: marked as pending in mdk4

2024-04-21 Thread Arnaud Rebillout
Control: tag -1 pending

Hello,

Bug #1068037 in mdk4 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/pkg-security-team/mdk4/-/commit/c3cb41f86f68603dedef371145af1143ec4a6247


Add patch to fix implicit-function-declaration

Closes: #1068037


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1068037



Bug#1069347: marked as done (rust-servo-freetype-sys: FTBFS on armel,armhf CMake Error: The source directory "/<>/freetype2" does not exist.)

2024-04-21 Thread Debian Bug Tracking System
Your message dated Mon, 22 Apr 2024 01:50:46 +
with message-id 
and subject line Bug#1069347: fixed in rust-servo-freetype-sys 4.0.5-3
has caused the Debian Bug report #1069347,
regarding rust-servo-freetype-sys: FTBFS on armel,armhf CMake Error: The source 
directory "/<>/freetype2" does not exist.
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.)


-- 
1069347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069347
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-servo-freetype-sys
Severity: serious
Tags: ftbfs
Control: found -1 4.0.5-2
X-Debbugs-Cc: ken...@xdump.org

Dear Maintainer,

rust-servo-freetype-sys fails to build on armhf.

FYI:

https://buildd.debian.org/status/fetch.php?pkg=rust-servo-freetype-sys=armel=4.0.5-2=1688825741=0
https://buildd.debian.org/status/fetch.php?pkg=rust-servo-freetype-sys=armhf=4.0.5-2=1688826040=0

Regards,
--- End Message ---
--- Begin Message ---
Source: rust-servo-freetype-sys
Source-Version: 4.0.5-3
Done: Peter Michael Green 

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

Debian distribution maintenance software
pp.
Peter Michael Green  (supplier of updated 
rust-servo-freetype-sys 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, 22 Apr 2024 00:56:24 +
Source: rust-servo-freetype-sys
Architecture: source
Version: 4.0.5-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Peter Michael Green 
Closes: 1069347
Changes:
 rust-servo-freetype-sys (4.0.5-3) unstable; urgency=medium
 .
   * Team upload.
   * Package servo-freetype-sys 4.0.5 from crates.io using debcargo 2.6.1
   * Allow use of pkg-config on arm eabi (Closes: #1069347)
Checksums-Sha1:
 37f4e3cae255a26dbbf4e42b90e3f4cd738ce6de 2405 
rust-servo-freetype-sys_4.0.5-3.dsc
 a8d782506354f82b1d06d26838a004aa237b4deb 5664 
rust-servo-freetype-sys_4.0.5-3.debian.tar.xz
 32b312c021770023467cb7d32c97175550b0b894 8864 
rust-servo-freetype-sys_4.0.5-3_source.buildinfo
Checksums-Sha256:
 828a07400bbb8301708563bf0414e4e441506c8da797e2d248b3041fb3cb2c7d 2405 
rust-servo-freetype-sys_4.0.5-3.dsc
 3912432774854479813e2b1509493dd700699f14fa12f90b36e44a0676ffb0ac 5664 
rust-servo-freetype-sys_4.0.5-3.debian.tar.xz
 f9e285d5e3af1dd6e129980894b1cad085e421f881572036f13296410700e60d 8864 
rust-servo-freetype-sys_4.0.5-3_source.buildinfo
Files:
 864a459b0c629a397cd2061ca804ae62 2405 rust optional 
rust-servo-freetype-sys_4.0.5-3.dsc
 5652f64de491e89557ec12877721dbdf 5664 rust optional 
rust-servo-freetype-sys_4.0.5-3.debian.tar.xz
 aea35197877d5d312386489ccc835f62 8864 rust optional 
rust-servo-freetype-sys_4.0.5-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmYlu7MUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XtXkA/9G2XDEaSzZxF053XTZG9oUBmmCYEz
YbtIi3zXEVoLvg2wyn3Gjq/PicKfsK5Cwnnzse4M8TPKB4LjZcT8gxcsyuAX3rd6
nztx6Z3eJSikBzUjosT1hQRt1G/9Ya6aMgCGKeUzrQCrqPdM/nAanTtZDW8Ducek
07CPwGmvNkTHuNUjrLmM4+G2Qf1BszettbwPnqeOkRN1wgNlKkQ0GJ51tzW4cyy8
l5N/ZlUB3oszo34+IZCqbbzseOwu7vs68Ei3866iBtlQXkBYbdfbKX3wniH4cMCA
dZNYwBVIeyOybF1YwRuqi+FPYLsSlLbQQBDtWR17OskEE27LMq63aKXPfYZhA88H
QhSQhuxzijtH5LBl21fl+OiEu5POq3MIPcsrzi8u069yuMZEjnTevZZXjm24BboM
FuSBIvnHPFbNJsY2NH9FN/+rnSsesOvZoRh0k/k3/w6Rv+920EXVuQi3hXp5+uyO
YQD/AwFcqOsilbXQTmuew4+pUA7MsFGcbpKDJlaQmJ1lNsWlZm4KBj1k0JQQh5GX
iajr6si4i4oDsrYda3qqrcR6AMDiTpJd9xoQQ2lSiedm6oRvdtfW4uO6nW2Bgwuu
XXH8XLhSe7BpSdAHVhSULcKQBkgG2Wp0EBA4S//jv28UX7pk83QHIznGl5JEU+Ls
m/8m0nRZYcFJ3mQ=
=4lAb
-END PGP SIGNATURE-



pgp1EyvHlTzD6.pgp
Description: PGP signature
--- End Message ---


Processed: Re: appstream-generator FTBFS with gdc

2024-04-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 966249 serious
Bug #966249 [src:appstream-generator] appstream-generator FTBFS with gdc: 
error: undefined identifier ‘JSONType’
Severity set to 'serious' from 'wishlist'
> thanks
Stopping processing here.

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



Bug#1066586: marked as done (francine: FTBFS: after_login.c:132:7: error: implicit declaration of function ‘get_check_email’; did you mean ‘check_mail’? [-Werror=implicit-function-declaration])

2024-04-21 Thread Debian Bug Tracking System
Your message dated Mon, 22 Apr 2024 01:04:51 +
with message-id 
and subject line Bug#1066586: fixed in francine 0.99.8+orig-2.2
has caused the Debian Bug report #1066586,
regarding francine: FTBFS: after_login.c:132:7: error: implicit declaration of 
function ‘get_check_email’; did you mean ‘check_mail’? 
[-Werror=implicit-function-declaration]
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.)


-- 
1066586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066586
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: francine
Version: 0.99.8+orig-2.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

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

This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -c -o after_login.o after_login.c
> after_login.c: In function ‘print_lastlog’:
> after_login.c:90:20: warning: passing argument 1 of ‘ctime’ from incompatible 
> pointer type [-Wincompatible-pointer-types]
>90 |   strtime = ctime (&(oldlog->ll_time));
>   |^~
>   ||
>   |int32_t * {aka int *}
> In file included from after_login.c:45:
> /usr/include/time.h:183:35: note: expected ‘const time_t *’ {aka ‘const long 
> int *’} but argument is of type ‘int32_t *’ {aka ‘int *’}
>   183 | extern char *ctime (const time_t *__timer) __THROW;
>   | ~~^~~
> after_login.c: In function ‘check_mail’:
> after_login.c:132:7: error: implicit declaration of function 
> ‘get_check_email’; did you mean ‘check_mail’? 
> [-Werror=implicit-function-declaration]
>   132 |   if (get_check_email())
>   |   ^~~
>   |   check_mail
> cc1: some warnings being treated as errors
> make[3]: *** [Makefile:391: after_login.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/francine_0.99.8+orig-2.1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=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: francine
Source-Version: 0.99.8+orig-2.2
Done: Chris Hofstaedtler 

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

Debian distribution maintenance software
pp.
Chris Hofstaedtler  (supplier of updated francine 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, 22 Apr 2024 02:40:03 +0200
Source: francine
Architecture: source
Version: 0.99.8+orig-2.2
Distribution: unstable
Urgency: medium
Maintainer: Rhonda D'Vine 
Changed-By: Chris Hofstaedtler 
Closes: 1060194 1066586
Changes:
 francine (0.99.8+orig-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Install bin/francine into canonical location for DEP17. (Closes: #1060194)
   * Fix FTBFS with -Werror=implicit-function-declaration (Closes: #1066586)
Checksums-Sha1:
 

Bug#1066601: marked as done (gnunet-gtk: FTBFS: plugin_gtk_namestore_tlsa.c:617:12: error: implicit declaration of function ‘memmem’; did you mean ‘memset’? [-Werror=implicit-function-declaration])

2024-04-21 Thread Debian Bug Tracking System
Your message dated Mon, 22 Apr 2024 00:50:21 +
with message-id 
and subject line Bug#1066601: fixed in gnunet-gtk 0.20.0-4
has caused the Debian Bug report #1066601,
regarding gnunet-gtk: FTBFS: plugin_gtk_namestore_tlsa.c:617:12: error: 
implicit declaration of function ‘memmem’; did you mean ‘memset’? 
[-Werror=implicit-function-declaration]
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.)


-- 
1066601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066601
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnunet-gtk
Version: 0.20.0-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

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

This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Relevant part (hopefully):
> /bin/bash ../../libtool  --tag=CC   --mode=link gcc -I/usr/include/gtk-3.0 
> -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount 
> -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo 
> -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 
> -I/usr/include/x86_64-linux-gnu -I/usr/include/webp 
> -I/usr/include/gio-unix-2.0 -I/usr/include/cloudproviders 
> -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 
> -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -pthread 
> -I/usr/include/libgladeui-2.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gtk-3.0 
> -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/freetype2 
> -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid 
> -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 
> -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/x86_64-linux-gnu 
> -I/usr/include/webp -I/usr/include/gio-unix-2.0 -I/usr/include/cloudproviders 
> -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 
> -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -pthread  -fno-strict-aliasing 
> -Wall -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount 
> -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo 
> -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 
> -I/usr/include/x86_64-linux-gnu -I/usr/include/webp 
> -I/usr/include/gio-unix-2.0 -I/usr/include/cloudproviders 
> -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 
> -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -pthread  -export-dynamic 
> -avoid-version -module -no-undefined -Wl,-z,relro -o 
> libgnunet_plugin_gtk_namestore_a.la -rpath /usr/lib/x86_64-linux-gnu/gnunet 
> libgnunet_plugin_gtk_namestore_a_la-plugin_gtk_namestore_a.lo -lgnunetutil 
> -lgnunetutil -lgtk-3 -lgdk-3 -lz -lpangocairo-1.0 -lpango-1.0 -lharfbuzz 
> -latk-1.0 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 
> -lglib-2.0 
> plugin_gtk_namestore_tlsa.c: In function ‘import_x509_certificate’:
> plugin_gtk_namestore_tlsa.c:617:12: error: implicit declaration of function 
> ‘memmem’; did you mean ‘memset’? [-Werror=implicit-function-declaration]
>   617 |   cn = memmem (str.data, str.size, ",CN=", 4);
>   |^~
>   |memset
> plugin_gtk_namestore_tlsa.c:617:10: warning: assignment to ‘const char *’ 
> from ‘int’ makes pointer from integer without a cast [-Wint-conversion]
>   617 |   cn = memmem (str.data, str.size, ",CN=", 4);
>   |  ^
> /bin/bash ../../libtool  --tag=CC   --mode=link gcc -I/usr/include/gtk-3.0 
> -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount 
> -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo 
> -I/usr/include/pixman-1 

Bug#1057850: libnss-db: Uses db5.3, no replacement in sight

2024-04-21 Thread Chris Hofstaedtler
On Thu, Apr 04, 2024 at 07:16:34PM -0300, Paulo Henrique de Lima Santana wrote:
> Would be possible reintroduce libnss-db to testing?
> 
> I'm asking because I'm maintainer of the pglistener package and I know there
> aren't plans to update the sofwtare with another database solution.

Well what's your plan forward? db5.3 is supposed to be removed.

Chris



Bug#1069481: marked as done (freecdb: FTBFS on armhf: dh_auto_test: error: make -j4 check returned exit code 2)

2024-04-21 Thread Debian Bug Tracking System
Your message dated Mon, 22 Apr 2024 00:19:14 +
with message-id 
and subject line Bug#1069481: fixed in freecdb 0.77
has caused the Debian Bug report #1069481,
regarding freecdb: FTBFS on armhf: dh_auto_test: error: make -j4 check returned 
exit code 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.)


-- 
1069481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069481
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freecdb
Version: 0.76
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> ./check-local cdbmake cdbdump cdbget cdbstats
> Checking cdbmake...
> cdbmake: fatal: unable to create tmp: invalid argument
> 111
> cdbmake: fatal: unable to create tmp: invalid argument
> 111
> cdbmake: fatal: unable to create tmp: invalid argument
> 111
> cdbmake: fatal: unable to create loop: symbolic link loop
> 111
> cdbmake: fatal: unable to create tmp: invalid argument
> 111
> cdbmake: fatal: unable to create tmp: invalid argument
> 111
> cdbmake: fatal: unable to create tmp: invalid argument
> 111
> cdbmake: fatal: unable to create tmp: invalid argument
> 111
> cdbmake failed.
> make[1]: *** [Makefile:25: check] Error 1
> make[1]: Leaving directory '/<>'
> dh_auto_test: error: make -j4 check returned exit code 2


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/freecdb_0.76_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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: freecdb
Source-Version: 0.77
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated freecdb 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, 22 Apr 2024 01:55:29 +0200
Source: freecdb
Architecture: source
Version: 0.77
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Closes: 1011493 1069481
Changes:
 freecdb (0.77) unstable; urgency=medium
 .
   * QA upload.
   * Explicitly pass CFLAGS to the build.  (Closes: #1011493, #1069481)
   * Fix building with -Werror=implicit-function-declaration.
   * Declare Rules-Requires-Root: no.
Checksums-Sha1:
 585b79d52820daba1389e4535a0160ec52eafec8 1531 freecdb_0.77.dsc
 ee987a46da1db0ba45cea13e0cd7362399309cb7 218108 freecdb_0.77.tar.xz
 b8f1b39c2725c21dfea4d333ab847059ce06dc55 5613 freecdb_0.77_source.buildinfo
Checksums-Sha256:
 26b7bea273740144f4b93be3bfa71d61c491a2438c5f557802f68bdaba7cfdfa 1531 
freecdb_0.77.dsc
 8a8805a521ccc49f54b28abd9ab4ff0ceebdc14267bc72b946ccf3efd35aed95 218108 
freecdb_0.77.tar.xz
 2ccc40d887ac4cb22b4db1f64bfd9f2edfc260248213d1d7bedb00cb31b4cb7a 5613 
freecdb_0.77_source.buildinfo
Files:
 d8f2435204bc3e531946b7c4c129429d 1531 utils optional freecdb_0.77.dsc
 145be443c590812b2df3d7d3c6eb4b6c 218108 utils optional freecdb_0.77.tar.xz
 6e8fd572ce43b2c469bb41d1d8d811a3 5613 utils optional 
freecdb_0.77_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmYlqBIQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCK+oD/0QoBsB4d0XzP3hs+EkfW5bxLF53TE3htU5

Processed: Re: Bug#966288: [Pkg-puppet-devel] Bug#966288: mcollective - RM for bullseye?

2024-04-21 Thread Debian Bug Tracking System
Processing control commands:

> clone -1 -2
Bug #966288 [src:mcollective] mcollective - RM for bullseye?
Bug 966288 cloned as bug 1069635
> severity -1 serious
Bug #966288 [src:mcollective] mcollective - RM for bullseye?
Severity set to 'serious' from 'normal'
> reassign -2 ftp.debian.org
Bug #1069635 [src:mcollective] mcollective - RM for bullseye?
Bug reassigned from package 'src:mcollective' to 'ftp.debian.org'.
Ignoring request to alter found versions of bug #1069635 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1069635 to the same values 
previously set
> retitle -2 RM: mcollective -- ROQA; dead upstream, alternatives exist
Bug #1069635 [ftp.debian.org] mcollective - RM for bullseye?
Changed Bug title to 'RM: mcollective -- ROQA; dead upstream, alternatives 
exist' from 'mcollective - RM for bullseye?'.
> tags -2 = moreinfo
Bug #1069635 [ftp.debian.org] RM: mcollective -- ROQA; dead upstream, 
alternatives exist
Added tag(s) moreinfo.

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



Processed: tagging 1069313, tagging 1056898, tagging 1069339, tagging 1069313, tagging 1069335, tagging 1069333 ...

2024-04-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 1069313 + sid trixie
Bug #1069313 [src:jskeus] FTBFS: implicit declaration of function 
‘jpeg_memio_dest’; did you mean ‘jpeg_mem_dest’?
Ignoring request to alter tags of bug #1069313 to the same tags previously set
> tags 1056898 + sid trixie
Bug #1056898 {Done: Christoph Biedl } 
[src:pptpd] pptpd: Build failures with ppp-2.5.0
Added tag(s) sid and trixie.
> tags 1069339 + sid trixie
Bug #1069339 [libvdeplug-pcap] Not installable due to hardcoded pre-t64 library 
deps
Ignoring request to alter tags of bug #1069339 to the same tags previously set
> tags 1069313 + sid trixie
Bug #1069313 [src:jskeus] FTBFS: implicit declaration of function 
‘jpeg_memio_dest’; did you mean ‘jpeg_mem_dest’?
Ignoring request to alter tags of bug #1069313 to the same tags previously set
> tags 1069335 + sid trixie
Bug #1069335 [prads] Not installable due to hardcoded pre-t64 library deps
Ignoring request to alter tags of bug #1069335 to the same tags previously set
> tags 1069333 + sid trixie
Bug #1069333 [ippsample] Not installable due to hardcoded pre-t64 library deps
Ignoring request to alter tags of bug #1069333 to the same tags previously set
> tags 1069073 + sid trixie
Bug #1069073 {Done: Sean Whitton } [src:lua-mode] 
lua-mode: FTBFS: failing tests
Added tag(s) sid and trixie.
> notfound 1069344 6.2.2401+dfsg1-1.1+b1
Bug #1069344 [src:netgen] netgen: FTBFS on armhf [debian/rules:66: 
override_dh_auto_test]
The source 'netgen' and version '6.2.2401+dfsg1-1.1+b1' do not appear to match 
any binary packages
No longer marked as found in versions netgen/6.2.2401+dfsg1-1.1+b1.
> found 1069344 6.2.2401+dfsg1-1.1
Bug #1069344 [src:netgen] netgen: FTBFS on armhf [debian/rules:66: 
override_dh_auto_test]
Marked as found in versions netgen/6.2.2401+dfsg1-1.1.
> found 1069310 2.4.2-2
Bug #1069310 [golang-github-hanwen-go-fuse-dev] FTBFS: tests failed
Marked as found in versions golang-github-hanwen-go-fuse/2.4.2-2.
> reassign 1032742 src:openldap 2.5.13+dfsg-5
Bug #1032742 {Done: Ryan Tandy } [slapd-smbk5pwd] please drop 
transitional package slapd-smbk5pwd from src:openldap
Bug reassigned from package 'slapd-smbk5pwd' to 'src:openldap'.
No longer marked as found in versions openldap/2.5.13+dfsg-5.
No longer marked as fixed in versions openldap/2.5.16+dfsg-1.
Bug #1032742 {Done: Ryan Tandy } [src:openldap] please drop 
transitional package slapd-smbk5pwd from src:openldap
Marked as found in versions openldap/2.5.13+dfsg-5.
> fixed 1032742 2.5.16+dfsg-1
Bug #1032742 {Done: Ryan Tandy } [src:openldap] please drop 
transitional package slapd-smbk5pwd from src:openldap
Marked as fixed in versions openldap/2.5.16+dfsg-1.
> tags 1069308 + sid trixie
Bug #1069308 [src:gnome-subtitles] FTBFS: tests failed
Ignoring request to alter tags of bug #1069308 to the same tags previously set
> retitle 1069471 nfs-ganesha: FTBFS on 32-bit: build-dependency not 
> installable: libcephfs-dev
Bug #1069471 [src:nfs-ganesha] nfs-ganesha: FTBFS on armhf: build-dependency 
not installable: libcephfs-dev
Changed Bug title to 'nfs-ganesha: FTBFS on 32-bit: build-dependency not 
installable: libcephfs-dev' from 'nfs-ganesha: FTBFS on armhf: build-dependency 
not installable: libcephfs-dev'.
> retitle 1069385 FTBFS: dh_installdocs: error: Requested unknown package 
> libclanapp-1.0v5 via --link-doc, expected one of: libclanapp-1.0t64 ...
Bug #1069385 [src:clanlib] clanlib: FTBFS on arm64: dh_installdocs: error: 
Requested unknown package libclanapp-1.0v5 via --link-doc, expected one of: 
libclanapp-1.0t64 libclanlib-dev clanlib-doc
Changed Bug title to 'FTBFS: dh_installdocs: error: Requested unknown package 
libclanapp-1.0v5 via --link-doc, expected one of: libclanapp-1.0t64 ...' from 
'clanlib: FTBFS on arm64: dh_installdocs: error: Requested unknown package 
libclanapp-1.0v5 via --link-doc, expected one of: libclanapp-1.0t64 
libclanlib-dev clanlib-doc'.
> tags 1042415 - patch
Bug #1042415 [ruby-aws-partitions] ruby-aws-partitions: Package missing 
partitions.json
Removed tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1032742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032742
1042415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042415
1056898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056898
1069073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069073
1069308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069308
1069310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069310
1069313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069313
1069333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069333
1069335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069335
1069339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069339
1069344: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069344
1069385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069385
1069471: 

Bug#1069470: marked as done (nodejs: FTBFS on armhf: build-dependency not installable: libc-ares2 (>= 1.18.1~))

2024-04-21 Thread Debian Bug Tracking System
Your message dated Mon, 22 Apr 2024 00:13:11 +0200
with message-id 

and subject line Re: [Pkg-javascript-devel] Bug#1069470: nodejs: FTBFS on 
armhf: build-dependency not installable: libc-ares2 (>= 1.18.1~)
has caused the Debian Bug report #1069470,
regarding nodejs: FTBFS on armhf: build-dependency not installable: libc-ares2 
(>= 1.18.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.)


-- 
1069470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069470
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nodejs
Version: 18.20.1+dfsg-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: dpkg-dev (>= 1.22.5), debhelper-compat (= 13), 
> dh-buildinfo, bash-completion, ca-certificates, curl, gyp (>= 0.1~svn1773), 
> jq, libbrotli-dev, libbrotli-dev, libc-ares-dev (>= 1.18.1~), libc-ares-dev, 
> libhttp-parser-dev (>= 2.9.2~), libicu-dev (>= 70.1~), libicu-dev, 
> libnghttp2-dev (>= 1.41.0~), libnghttp2-dev, libssl-dev (>= 1.1.1~), 
> libssl-dev, libuv1-dev (>= 1.43.0~), libuv1-dev, node-acorn (>= 6.2.1~), 
> node-cjs-module-lexer (>= 1.2.2~), node-undici (>= 5.0.0~), openssl (>= 
> 1.1.1~), pkgconf, pkg-js-tools (>= 0.8.2~), python3, procps, zlib1g-dev, 
> zlib1g-dev, build-essential, fakeroot, node-js-yaml (>= 4.1.0+dfsg+~4.0.5-6), 
> node-marked (>= 4~), node-highlight.js
> Filtered Build-Depends: dpkg-dev (>= 1.22.5), debhelper-compat (= 13), 
> dh-buildinfo, bash-completion, ca-certificates, curl, gyp (>= 0.1~svn1773), 
> jq, libbrotli-dev, libbrotli-dev, libc-ares-dev (>= 1.18.1~), libc-ares-dev, 
> libhttp-parser-dev (>= 2.9.2~), libicu-dev (>= 70.1~), libicu-dev, 
> libnghttp2-dev (>= 1.41.0~), libnghttp2-dev, libssl-dev (>= 1.1.1~), 
> libssl-dev, libuv1-dev (>= 1.43.0~), libuv1-dev, node-acorn (>= 6.2.1~), 
> node-cjs-module-lexer (>= 1.2.2~), node-undici (>= 5.0.0~), openssl (>= 
> 1.1.1~), pkgconf, pkg-js-tools (>= 0.8.2~), python3, procps, zlib1g-dev, 
> zlib1g-dev, build-essential, fakeroot, node-js-yaml (>= 4.1.0+dfsg+~4.0.5-6), 
> node-marked (>= 4~), node-highlight.js
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [615 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [1587 B]
> Get:5 copy:/<>/apt_archive ./ Packages [1270 B]
> Fetched 3472 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  libnode109 : Depends: libc-ares2 (>= 1.18.1~) but it is not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/nodejs_18.20.1+dfsg-4_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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 

Bug#1069631: loki-ecmwf: Unsatisfiable dependency: python3-loki etc

2024-04-21 Thread Jeremy Bícha
Source: loki-ecmwf
Version: 0.2.0-1
Severity: serious

After https://salsa.debian.org/science-team/loki-ecmwf/-/commit/fd228e81dcb,
python3-loki-ecmwf-lint-rules has Depends: python3-loki but that
package is not available in Debian.

https://qa.debian.org/excuses.php?package=loki-ecmwf complains about
other uninstallable packages but I did not check them.

Thank you,
Jeremy Bícha



Bug#1069630: libcupsfilters-dev and libcupsfilters2-dev have an undeclared file conflict on /usr/lib/x86_64-linux-gnu/libcupsfilters.a, /usr/lib/x86_64-linux-gnu/libcupsfilters.so and /usr/lib/x86_64-

2024-04-21 Thread Helmut Grohne
Package: libcupsfilters2-dev
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + libcupsfilters-dev

The files
 * /usr/lib/x86_64-linux-gnu/libcupsfilters.a
 * /usr/lib/x86_64-linux-gnu/libcupsfilters.so
 * /usr/lib/x86_64-linux-gnu/pkgconfig/libcupsfilters.pc
are contained in the packages
 * libcupsfilters-dev/1.28.17-4 as present in unstable
 * libcupsfilters2-dev/2.0.0-1 as present in unstable

These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected files.

Please figure out which of these packages should properly own the
affected files and reassign the bug as appropriate. When doing so,
please add the other package to the set of affected packages using
"Control: affects -1 + " to avoid the filing of duplicates.

The other package should stop installing the files. In case the files
are being moved between packages, Breaks and Replaces should be
declared. In this case, please refer to policy section 7.6 for details.
Another useful resource is https://wiki.debian.org/PackageTransition.

Kind regards

The Debian Usr Merge Analysis Tool

This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
hel...@subdivi.de for assistance.



Processed: libcupsfilters-dev and libcupsfilters2-dev have an undeclared file conflict on /usr/lib/x86_64-linux-gnu/libcupsfilters.a, /usr/lib/x86_64-linux-gnu/libcupsfilters.so and /usr/lib/x86_64-li

2024-04-21 Thread Debian Bug Tracking System
Processing control commands:

> affects -1 + libcupsfilters-dev
Bug #1069630 [libcupsfilters2-dev] libcupsfilters-dev and libcupsfilters2-dev 
have an undeclared file conflict on /usr/lib/x86_64-linux-gnu/libcupsfilters.a, 
/usr/lib/x86_64-linux-gnu/libcupsfilters.so and 
/usr/lib/x86_64-linux-gnu/pkgconfig/libcupsfilters.pc
Added indication that 1069630 affects libcupsfilters-dev

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



Bug#1066468: marked as done (searchmonkey: FTBFS: callbacks.c:195:11: error: implicit declaration of function ‘clearComboBox2’; did you mean ‘clearComboBox’? [-Werror=implicit-function-declaration])

2024-04-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Apr 2024 20:43:24 +
with message-id 
and subject line Bug#1066468: fixed in searchmonkey 0.8.3-1.2
has caused the Debian Bug report #1066468,
regarding searchmonkey: FTBFS: callbacks.c:195:11: error: implicit declaration 
of function ‘clearComboBox2’; did you mean ‘clearComboBox’? 
[-Werror=implicit-function-declaration]
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.)


-- 
1066468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066468
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: searchmonkey
Version: 0.8.3-1.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

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

This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I..  -DPACKAGE_DATA_DIR=\""/usr/share"\" 
> -DPACKAGE_LOCALE_DIR=\""/usr/share/locale"\" -I/usr/include/poppler/glib 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/cairo -I/usr/include/libpng16 -I/usr/include/freetype2 
> -I/usr/include/pixman-1 -I/usr/include/poppler -I/usr/include/gtk-2.0 
> -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0 
> -I/usr/include/harfbuzz -I/usr/include/libmount -I/usr/include/blkid 
> -I/usr/include/fribidi -I/usr/include/gdk-pixbuf-2.0 
> -I/usr/include/x86_64-linux-gnu -I/usr/include/webp -I/usr/include/atk-1.0 
> -pthread  -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -c -o callbacks.o callbacks.c
> In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37,
>  from /usr/include/gtk-2.0/gtk/gtkwidget.h:36,
>  from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35,
>  from /usr/include/gtk-2.0/gtk/gtkbin.h:35,
>  from /usr/include/gtk-2.0/gtk/gtkwindow.h:36,
>  from /usr/include/gtk-2.0/gtk/gtkdialog.h:35,
>  from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32,
>  from /usr/include/gtk-2.0/gtk/gtk.h:33,
>  from callbacks.c:5:
> /usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: warning: ‘GTypeDebugFlags’ is 
> deprecated [-Wdeprecated-declarations]
>   236 | voidgtk_type_init   (GTypeDebugFlagsdebug_flags);
>   | ^~~~
> In file included from /usr/include/glib-2.0/gobject/gobject.h:26,
>  from /usr/include/glib-2.0/gobject/gbinding.h:31,
>  from /usr/include/glib-2.0/glib-object.h:24,
>  from /usr/include/glib-2.0/gio/gioenums.h:30,
>  from /usr/include/glib-2.0/gio/giotypes.h:30,
>  from /usr/include/glib-2.0/gio/gio.h:28,
>  from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
>  from /usr/include/gtk-2.0/gdk/gdk.h:32,
>  from /usr/include/gtk-2.0/gtk/gtk.h:32:
> /usr/include/glib-2.0/gobject/gtype.h:723:1: note: declared here
>   723 | {
>   | ^
> In file included from /usr/include/gtk-2.0/gtk/gtktoolitem.h:31,
>  from /usr/include/gtk-2.0/gtk/gtktoolbutton.h:30,
>  from /usr/include/gtk-2.0/gtk/gtkmenutoolbutton.h:30,
>  from /usr/include/gtk-2.0/gtk/gtk.h:126:
> /usr/include/gtk-2.0/gtk/gtktooltips.h:73:3: warning: ‘GTimeVal’ is 
> deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations]
>73 |   GTimeVal last_popdown;
>   |   ^~~~
> In file included from /usr/include/glib-2.0/glib/galloca.h:34,
>  from /usr/include/glib-2.0/glib.h:32,
>  from /usr/include/glib-2.0/gobject/gbinding.h:30:
> /usr/include/glib-2.0/glib/gtypes.h:580:8: note: declared here
>   580 | struct _GTimeVal
>   |^
> callbacks.c: In function ‘on_cl_ear_history1_activate’:
> callbacks.c:195:11: error: implicit declaration of function ‘clearComboBox2’; 
> did you mean ‘clearComboBox’? [-Werror=implicit-function-declaration]
>   195 |   clearComboBox2(lookup_widget(GTK_WIDGET(menuitem), 
> "fileName"));
>   |   ^~
>   |   clearComboBox
> In file included from support.h:15,
>

Bug#1067628: marked as done (FTBFS: Error: symbol `open64' is already define)

2024-04-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Apr 2024 20:35:15 +
with message-id 
and subject line Bug#1067628: fixed in cctools 9.9-4.1
has caused the Debian Bug report #1067628,
regarding FTBFS: Error: symbol `open64' is already define
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.)


-- 
1067628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067628
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cctools
Version: 9.9-4
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=cctools=armel=9.9-4%2Bb2=1711271394=0


/tmp/ccxWFvuU.s: Assembler messages:
/tmp/ccxWFvuU.s:1927: Error: symbol `open64' is already defined


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

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

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated cctools 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, 21 Apr 2024 22:18:03 +0200
Source: cctools
Architecture: source
Version: 9.9-4.1
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Sebastian Ramacher 
Closes: 1067628
Changes:
 cctools (9.9-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload
 .
   [ Michael Hudson-Doyle ]
   * Undefine _FILE_OFFSET_BITS and _TIME_BITS in rmonitor_helper.c so the 
library's
 interposition of open/open64 still works. (Closes: #1067628)
Checksums-Sha1:
 b65ef643929d4612639f170af80507f0152fe38a 2005 cctools_9.9-4.1.dsc
 371cb2123b2916822ca0c031377cea39a702c1ea 22480 cctools_9.9-4.1.debian.tar.xz
 c562a8f7faa8f10c03a2ddfc20f8fd13ac4c4cde 13269 cctools_9.9-4.1_amd64.buildinfo
Checksums-Sha256:
 718188780ac73197d28d8deb73c8ce1ed0c5e6b48760c575a13227ad7b9ddf48 2005 
cctools_9.9-4.1.dsc
 01650b185d30783f3f364371a97e2403e117d5200386948289f0b454ec0ae537 22480 
cctools_9.9-4.1.debian.tar.xz
 ba45c1a7a4fcb41c011442dd01ec1bed2c49fc97e9834297144abe7b932eac3d 13269 
cctools_9.9-4.1_amd64.buildinfo
Files:
 43350623d1b0d40327adf56ed5ac522e 2005 utils optional cctools_9.9-4.1.dsc
 9b2ad7094a3f115b33ac52900b93e1f3 22480 utils optional 
cctools_9.9-4.1.debian.tar.xz
 dd0798f95c14c9dcc289c5355272cb9f 13269 utils optional 
cctools_9.9-4.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZiV1/wAKCRAhk2s2YA/N
iWH3AQCdsApltk48utFVvBao/mpiTFFuwBD7yT6t3cLVsHoPzQEA5GQ0wvkVdI8F
Srt+X+P/cVM++JY39kgJ9n6JDBO8rAI=
=DZ1h
-END PGP SIGNATURE-



pgpj5dmVZuMy9.pgp
Description: PGP signature
--- End Message ---


Processed: cctools: diff for NMU version 9.9-4.1

2024-04-21 Thread Debian Bug Tracking System
Processing control commands:

> tags 1067628 + patch
Bug #1067628 [src:cctools] FTBFS: Error: symbol `open64' is already define
Added tag(s) patch.

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



Bug#1067628: cctools: diff for NMU version 9.9-4.1

2024-04-21 Thread Sebastian Ramacher
Control: tags 1067628 + patch


Dear maintainer,

I've prepared an NMU for cctools (versioned as 9.9-4.1). The diff
is attached to this message.

Regards.


-- 
Sebastian Ramacher
diff -Nru cctools-9.9/debian/changelog cctools-9.9/debian/changelog
--- cctools-9.9/debian/changelog	2023-12-06 11:26:18.0 +0100
+++ cctools-9.9/debian/changelog	2024-04-21 22:18:03.0 +0200
@@ -1,3 +1,13 @@
+cctools (9.9-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+
+  [ Michael Hudson-Doyle ]
+  * Undefine _FILE_OFFSET_BITS and _TIME_BITS in rmonitor_helper.c so the library's
+interposition of open/open64 still works. (Closes: #1067628)
+
+ -- Sebastian Ramacher   Sun, 21 Apr 2024 22:18:03 +0200
+
 cctools (9.9-4) unstable; urgency=medium
 
   * Fix to build to correct globus configuration, enable broken
diff -Nru cctools-9.9/debian/patches/globus-flags.patch cctools-9.9/debian/patches/globus-flags.patch
--- cctools-9.9/debian/patches/globus-flags.patch	2023-12-06 11:26:18.0 +0100
+++ cctools-9.9/debian/patches/globus-flags.patch	2024-03-20 03:59:10.0 +0100
@@ -15,3 +15,17 @@
  CCTOOLS_GLOBUS_CCFLAGS=${globus_ccflags}
  
  export CCTOOLS_TEST_CCFLAGS=${test_ccflags}
+--- a/resource_monitor/src/rmonitor_helper.c
 b/resource_monitor/src/rmonitor_helper.c
+@@ -13,6 +13,11 @@
+ #define _GNU_SOURCE // Aah!!
+ #endif
+ 
++/* Building with these macros defines interferes with this files attempt to
++   interpose both open and open64 */
++#undef _FILE_OFFSET_BITS
++#undef _TIME_BITS
++
+ #include 
+ #include 
+ #include 


Processed: found 1064293 in 551-2

2024-04-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> found 1064293 551-2
Bug #1064293 {Done: Salvatore Bonaccorso } [src:less] less: 
CVE-2022-48624
Marked as found in versions less/551-2.
> thanks
Stopping processing here.

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



Processed: found 1068938 in 551-2

2024-04-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> found 1068938 551-2
Bug #1068938 {Done: Salvatore Bonaccorso } [src:less] less: 
CVE-2024-32487: with LESSOPEN mishandles \n in paths
Marked as found in versions less/551-2.
> thanks
Stopping processing here.

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



Bug#1068818: sngrep: CVE-2024-3119 CVE-2024-3120

2024-04-21 Thread Moritz Muehlenhoff
On Sun, Apr 21, 2024 at 07:35:43PM +, Victor Seva wrote:
> Hi,
> 
> 
> I've just uploaded sngrep 1.8.1-1 to sid and prepared 1.6.0-1+deb12u1 for 
> bookworms-security [0].
> 
> Attached debdiff file.
> 
> Waiting for you reply,
> Victor
> 
> [0] 
> https://salsa.debian.org/pkg-voip-team/sngrep/-/tags/debian%2F1.6.0-1+deb12u1

Hi Victor,
diff looks fine, but I don't believe this really needs a DSA; it's rather 
obscure attack vector.
I think addressing this via the next Bookworm point release is perfectly fine, 
what do you think?

Procedure is outlined at
https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#special-case-uploads-to-the-stable-and-oldstable-distributions

Cheers,
Moritz



Processed: found 1068818 in 1.4.8-1

2024-04-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> found 1068818 1.4.8-1
Bug #1068818 {Done: Victor Seva } [src:sngrep] sngrep: 
CVE-2024-3119 CVE-2024-3120
Marked as found in versions sngrep/1.4.8-1.
> thanks
Stopping processing here.

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



Processed: found 1068818 in 1.6.0-1

2024-04-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> found 1068818 1.6.0-1
Bug #1068818 {Done: Victor Seva } [src:sngrep] sngrep: 
CVE-2024-3119 CVE-2024-3120
Marked as found in versions sngrep/1.6.0-1.
> thanks
Stopping processing here.

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



Bug#1064676: marked as done (android-platform-tools-apksig: FTBFS: dh_auto_test: error: gradle --info --console plain --offline --stacktrace --no-daemon --refresh-dependencies --gradle-user-home .grad

2024-04-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Apr 2024 19:49:08 +
with message-id 
and subject line Bug#1064676: fixed in android-platform-tools-apksig 31.0.2-2
has caused the Debian Bug report #1064676,
regarding android-platform-tools-apksig: FTBFS: dh_auto_test: error: gradle 
--info --console plain --offline --stacktrace --no-daemon 
--refresh-dependencies --gradle-user-home .gradle -Duser.home=. 
-Duser.name=debian -Ddebian.package=android-platform-tools-apksig 
-Dfile.encoding=UTF-8 --parallel --max-workers=8 test 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.)


-- 
1064676: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064676
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: android-platform-tools-apksig
Version: 31.0.2-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 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_test
>   mkdir -p .gradle/init.d
>   cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/
>   gradle --info --console plain --offline --stacktrace --no-daemon 
> --refresh-dependencies --gradle-user-home .gradle -Duser.home=. 
> -Duser.name=debian -Ddebian.package=android-platform-tools-apksig 
> -Dfile.encoding=UTF-8 --parallel --max-workers=8 test
> openjdk version "17.0.10" 2024-01-16
> OpenJDK Runtime Environment (build 17.0.10+7-Debian-1)
> OpenJDK 64-Bit Server VM (build 17.0.10+7-Debian-1, mixed mode, sharing)
> Initialized native services in: /<>/.gradle/native
> To honour the JVM settings for this build a new JVM will be forked. Please 
> consider using the daemon: 
> https://docs.gradle.org/4.4.1/userguide/gradle_daemon.html.
> Starting process 'Gradle build daemon'. Working directory: 
> /<>/.gradle/daemon/4.4.1 Command: 
> /usr/lib/jvm/java-17-openjdk-amd64/bin/java --add-opens 
> java.base/java.lang=ALL-UNNAMED 
> -Xbootclasspath/a:/usr/share/java/gradle-helper-hook.jar:/usr/share/java/maven-repo-helper.jar
>  -Dfile.encoding=UTF-8 -Duser.country -Duser.language=en -Duser.variant -cp 
> /usr/share/gradle/lib/gradle-launcher-4.4.1.jar 
> org.gradle.launcher.daemon.bootstrap.GradleDaemon 4.4.1
> Successfully started process 'Gradle build daemon'
> An attempt to start the daemon took 0.855 secs.
> The client will now receive all logging from the daemon (pid: 2519692). The 
> daemon log file: /<>/.gradle/daemon/4.4.1/daemon-2519692.out.log
> Daemon will be stopped at the end of the build stopping after processing
> Closing daemon's stdin at end of input.
> The daemon will no longer process any standard input.
> Using 8 worker leases.
> Creating new cache for fileHashes, path 
> /<>/.gradle/caches/4.4.1/fileHashes/fileHashes.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@266cd8b5
> Creating new cache for resourceHashesCache, path 
> /<>/.gradle/caches/4.4.1/fileHashes/resourceHashesCache.bin, 
> access org.gradle.cache.internal.DefaultCacheAccess@266cd8b5
> Creating new cache for fileHashes, path 
> /<>/.gradle/4.4.1/fileHashes/fileHashes.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@2b8cbb70
> Starting Build
> Creating new cache for metadata-1.1/results, path 
> /<>/.gradle/caches/transforms-1/metadata-1.1/results.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@57940052
> Settings evaluated using settings file '/<>/settings.gradle'.
>   Settings file not found (/<>/settings.gradle)
>   Root project name not defined in settings.gradle, defaulting to 
> 'android-platform-tools-apksig' instead of the name of the root directory 
> 'android-platform-tools-apksig-31.0.2'
> Projects loaded. Root project using build file 
> '/<>/build.gradle'.
> Included projects: [root project 'android-platform-tools-apksig']
>   Keep-alive timer started
>   Adding Debian repository to project 'android-platform-tools-apksig'
> Parallel execution is an incubating feature.
> Evaluating root project 'android-platform-tools-apksig' using build file 
> '/<>/build.gradle'.
>   Adding Maven pom generation to project 'android-platform-tools-apksig'
>   Linking the generated javadoc to the system JDK API documentation
> All projects evaluated.
> Selected primary task 'test' from project :
> Creating new cache for annotation-processors, path 
> /<>/.gradle/4.4.1/fileContent/annotation-processors.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@21366fbb
> Tasks to be executed: [task ':compileJava', 

Bug#1068818: marked as done (sngrep: CVE-2024-3119 CVE-2024-3120)

2024-04-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Apr 2024 19:24:53 +
with message-id 
and subject line Bug#1068818: fixed in sngrep 1.8.1-1
has caused the Debian Bug report #1068818,
regarding sngrep: CVE-2024-3119 CVE-2024-3120
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.)


-- 
1068818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068818
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sngrep
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for sngrep.

CVE-2024-3119[0]:
| A buffer overflow vulnerability exists in all versions of sngrep
| since v0.4.2, due to improper handling of 'Call-ID' and 'X-Call-ID'
| SIP headers. The functions sip_get_callid and sip_get_xcallid in
| sip.c use the strncpy function to copy header contents into fixed-
| size buffers without checking the data length. This flaw allows
| remote attackers to execute arbitrary code or cause a denial of
| service (DoS) through specially crafted SIP messages.

https://github.com/irontec/sngrep/commit/dd5fec92730562af6f96891291cd4e102b80bfcc
 (v1.8.1)

CVE-2024-3120[1]:
| A stack-buffer overflow vulnerability exists in all versions of
| sngrep since v1.4.1. The flaw is due to inadequate bounds checking
| when copying 'Content-Length' and 'Warning' headers into fixed-size
| buffers in the sip_validate_packet and sip_parse_extra_headers
| functions within src/sip.c. This vulnerability allows remote
| attackers to execute arbitrary code or cause a denial of service
| (DoS) via crafted SIP messages.

https://github.com/irontec/sngrep/commit/f3f8ed8ef38748e6d61044b39b0dabd7e37c6809
 (v1.8.1)

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-3119
https://www.cve.org/CVERecord?id=CVE-2024-3119
[1] https://security-tracker.debian.org/tracker/CVE-2024-3120
https://www.cve.org/CVERecord?id=CVE-2024-3120

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: sngrep
Source-Version: 1.8.1-1
Done: Victor Seva 

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

Debian distribution maintenance software
pp.
Victor Seva  (supplier of updated sngrep 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, 21 Apr 2024 21:00:43 +0200
Source: sngrep
Architecture: source
Version: 1.8.1-1
Distribution: unstable
Urgency: high
Maintainer: Debian VoIP Team 
Changed-By: Victor Seva 
Closes: 1068818
Changes:
 sngrep (1.8.1-1) unstable; urgency=high
 .
   * New upstream version 1.8.1
   * fixes for CVE-2024-3119 and CVE-2024-3120 (Closes: #1068818)
Checksums-Sha1:
 077c2ddfa42c284a462c8a4c11781e311313ac9b 1670 sngrep_1.8.1-1.dsc
 88c61d7184ef1ad1c76f986bbe8f12bd2269367a 254097 sngrep_1.8.1.orig.tar.gz
 683f8cdbd90707ddfcc4059919050aa1d649a243 488 sngrep_1.8.1.orig.tar.gz.asc
 2f8e4703d0ee3063a294e97d41ca66a78e992b03 5072 sngrep_1.8.1-1.debian.tar.xz
 1a104d726f2a4f3bc7d9c62e3578bc22572f82ea 6781 sngrep_1.8.1-1_amd64.buildinfo
Checksums-Sha256:
 254c2a5d27c3230321b791dfb98275110cbabdfb35f5ab05273524b662e6518f 1670 
sngrep_1.8.1-1.dsc
 678875d44c6fdacb533f2d9e1b8db33ee8252723bb95653368fd43fae58969fe 254097 
sngrep_1.8.1.orig.tar.gz
 771e34ff50b00945313a0183df18cf2eda0a7b2ce89214e4a61e2a731ac782a5 488 
sngrep_1.8.1.orig.tar.gz.asc
 d4dbebae8c12af38985c9622115e9d25a5cb4f44046acb18721d9370216d4713 5072 
sngrep_1.8.1-1.debian.tar.xz
 99ebb79656660f6fc8248688029a692bd8a8e16e7bed7dfc64848e6f87ca1db8 6781 
sngrep_1.8.1-1_amd64.buildinfo
Files:
 5a7f39576373f783865fdaf78e95497d 1670 comm optional sngrep_1.8.1-1.dsc
 1c1fb7e5a6ede73e86fa319d096ff552 254097 comm optional sngrep_1.8.1.orig.tar.gz
 76e1710ace45c59f4a35af1d0ef7c337 488 comm optional sngrep_1.8.1.orig.tar.gz.asc
 4178034dadbe6e0d60e859a3ef0837b9 5072 comm optional 
sngrep_1.8.1-1.debian.tar.xz
 ff61388ddb6e64eef76b16fd8cd75d9f 

Bug#1066672: marked as done (httest: FTBFS: socks_module.c:115:21: error: implicit declaration of function ‘atoi’ [-Werror=implicit-function-declaration])

2024-04-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Apr 2024 19:20:01 +
with message-id 
and subject line Bug#1066672: fixed in httest 2.4.23-1.6
has caused the Debian Bug report #1066672,
regarding httest: FTBFS: socks_module.c:115:21: error: implicit declaration of 
function ‘atoi’ [-Werror=implicit-function-declaration]
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.)


-- 
1066672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066672
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: httest
Version: 2.4.23-1.5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

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

This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I../config   -DLINUX -D_REENTRANT -D_GNU_SOURCE 
> -Wdate-time -D_FORTIFY_SOURCE=2 -I../include -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection  -I/usr/include/apr-1.0   
> -I/usr/include/apr-1.0 -I/usr/include   -c -o annotation_module.o 
> annotation_module.c
> socks_module.c: In function ‘block_SOCKS_CONNECT’:
> socks_module.c:115:21: error: implicit declaration of function ‘atoi’ 
> [-Werror=implicit-function-declaration]
>   115 |   ip.digit[i] = atoi(digit);
>   | ^~~~
> dbg_module.c: In function ‘dbg_interpreter’:
> dbg_module.c:97:7: error: implicit declaration of function ‘exit’ 
> [-Werror=implicit-function-declaration]
>97 |   exit(0);
>   |   ^~~~
> dbg_module.c:29:1: note: include ‘’ or provide a declaration of 
> ‘exit’
>28 | #include "module.h"
>   +++ |+#include 
>29 | 
> dbg_module.c:97:7: warning: incompatible implicit declaration of built-in 
> function ‘exit’ [-Wbuiltin-declaration-mismatch]
>97 |   exit(0);
>   |   ^~~~
> dbg_module.c:97:7: note: include ‘’ or provide a declaration of 
> ‘exit’
> cc1: some warnings being treated as errors
> make[2]: *** [Makefile:628: socks_module.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/httest_2.4.23-1.5_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=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: httest
Source-Version: 2.4.23-1.6
Done: Sebastian Ramacher 

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated httest 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, 21 Apr 2024 21:15:11 +0200
Source: httest
Architecture: source
Version: 2.4.23-1.6
Distribution: unstable
Urgency: medium
Maintainer: Eva Ramon Salinas 
Changed-By: Sebastian Ramacher 
Closes: 1066672
Changes:
 httest (2.4.23-1.6) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Steve Langasek ]
   * debian/patches: Fix implicit definitions (Closes: #1066672)
Checksums-Sha1:
 5758c5747ed5fb9802aafbfb5f3168bbf28c1556 1210 httest_2.4.23-1.6.dsc
 759e7dfc742f56cd3d613346556ad0423e3a66e0 6668 

Bug#1066672: httest: diff for NMU version 2.4.23-1.6

2024-04-21 Thread Sebastian Ramacher



Dear maintainer,

I've prepared an NMU for httest (versioned as 2.4.23-1.6). The diff
is attached to this message.

Regards.


-- 
Sebastian Ramacher
diff -Nru httest-2.4.23/debian/changelog httest-2.4.23/debian/changelog
--- httest-2.4.23/debian/changelog	2023-12-12 10:52:16.0 +0100
+++ httest-2.4.23/debian/changelog	2024-04-21 21:15:11.0 +0200
@@ -1,3 +1,12 @@
+httest (2.4.23-1.6) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Steve Langasek ]
+  * debian/patches: Fix implicit definitions (Closes: #1066672)
+
+ -- Sebastian Ramacher   Sun, 21 Apr 2024 21:15:11 +0200
+
 httest (2.4.23-1.5) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru httest-2.4.23/debian/patches/no-implicit-declarations.patch httest-2.4.23/debian/patches/no-implicit-declarations.patch
--- httest-2.4.23/debian/patches/no-implicit-declarations.patch	1970-01-01 01:00:00.0 +0100
+++ httest-2.4.23/debian/patches/no-implicit-declarations.patch	2024-04-21 21:14:30.0 +0200
@@ -0,0 +1,43 @@
+Description: add missing includes
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/1066672
+Last-Update: 2024-04-10
+Forwarded: no
+
+Index: httest-2.4.23/src/socks_module.c
+===
+--- httest-2.4.23.orig/src/socks_module.c
 httest-2.4.23/src/socks_module.c
+@@ -25,6 +25,8 @@
+ /
+  * Includes
+  ***/
++#include 
++
+ #include "module.h"
+ #ifndef HAVE_NO_NETINET
+   #include 
+Index: httest-2.4.23/src/annotation_module.c
+===
+--- httest-2.4.23.orig/src/annotation_module.c
 httest-2.4.23/src/annotation_module.c
+@@ -25,6 +25,7 @@
+ /
+  * Includes
+  ***/
++#include 
+ #include "module.h"
+ 
+ /
+Index: httest-2.4.23/src/dbg_module.c
+===
+--- httest-2.4.23.orig/src/dbg_module.c
 httest-2.4.23/src/dbg_module.c
+@@ -24,6 +24,7 @@
+ /
+  * Includes
+  ***/
++#include 
+ #include "store.h"
+ #include "module.h"
+ 
diff -Nru httest-2.4.23/debian/patches/series httest-2.4.23/debian/patches/series
--- httest-2.4.23/debian/patches/series	2023-12-12 10:52:16.0 +0100
+++ httest-2.4.23/debian/patches/series	2024-04-21 21:14:30.0 +0200
@@ -4,3 +4,4 @@
 fix-gcc-10.patch
 autoconf-2.70.patch
 pcre2.patch
+no-implicit-declarations.patch


Bug#1052746: marked as done (loadlin: FTBFS: cc1: error: ‘-fcf-protection’ is not compatible with this target)

2024-04-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Apr 2024 19:07:18 +
with message-id 
and subject line Bug#1052746: fixed in loadlin 1.6f-12
has caused the Debian Bug report #1052746,
regarding loadlin: FTBFS: cc1: error: ‘-fcf-protection’ is not compatible with 
this target
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.)


-- 
1052746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052746
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: loadlin
Version: 1.6f-10
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):
> gcc -m32 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -D__KERNEL__ -march=i386 -Os -DSTDC_HEADERS -fomit-frame-pointer 
> -fno-strength-reduce -fPIC -ffreestanding -fno-stack-protector -c pgadjust.c 
> -o pgadjust.o
> cc1: error: ‘-fcf-protection’ is not compatible with this target
> make[2]: *** [Makefile:36: pgadjust.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/09/25/loadlin_1.6f-10_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: loadlin
Source-Version: 1.6f-12
Done: Samuel Thibault 

We believe that the bug you reported is fixed in the latest version of
loadlin, 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.
Samuel Thibault  (supplier of updated loadlin package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 08 Aug 2023 23:53:59 +0200
Source: loadlin
Architecture: source
Version: 1.6f-12
Distribution: unstable
Urgency: medium
Maintainer: Samuel Thibault 
Changed-By: Samuel Thibault 
Closes: 1016428 1052746 1059172
Changes:
 loadlin (1.6f-12) unstable; urgency=medium
 .
   * rules: Set BYHAND back to no.
   * rules: Fix time of patched files.
   * control: Replace bsdmainutils build-dep with bsdextrautils
 (Closes: #1016428)
   * patches/flags: Also disable cf-protection, not supported on i386.
 (closes: #1052746)
   * loadlin.install: Install freeramdisk to /usr/sbin (Closes: #1059172)
   * patches/implicit-function-declaration: Fix build with
 -Werror=implicit-function-declaration.
   * source/lintian-overrides: Update override.
Checksums-Sha1:
 5171c1a0da85249b87ac0c45b0ba681b0aea1306 1883 loadlin_1.6f-12.dsc
 1ea43172f32ca50da5359cf2576727aa7c752825 20136 loadlin_1.6f-12.debian.tar.xz
 aee9393a31716a573e2d65ee26f9a60666cfc70b 6189 loadlin_1.6f-12_amd64.buildinfo
Checksums-Sha256:
 246624cb0cf765917c6c138348e97705f6797f45ccee0b22974697b0631608fb 1883 
loadlin_1.6f-12.dsc
 566d7117139df13c22f879480c7e9230082c6b9e921e47701d57d0d57a8c257d 20136 
loadlin_1.6f-12.debian.tar.xz
 f6c760304282c0ae82a1c2d376e120e3f31525f4f0f8a99e3e01c5316026a376 6189 
loadlin_1.6f-12_amd64.buildinfo
Files:
 6e45cf9f0375abb955ee9853fda3261b 1883 admin optional loadlin_1.6f-12.dsc
 ad926cf03d14943770fbe0699d9b5cb5 20136 admin optional 
loadlin_1.6f-12.debian.tar.xz
 b3bc793b2432b3536b12184df6a21008 6189 admin optional 
loadlin_1.6f-12_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEi6MnFvk67auaclLJ5pG0tXV4H2IFAmYlYhoACgkQ5pG0tXV4

Bug#1069549: racket: FTBFS on armel: dh_install: error: missing files, aborting

2024-04-21 Thread David Bremner


Control: tag -1 confirmed

Lucas Nussbaum  writes:

> Source: racket
> Version: 8.12+dfsg1-7
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armel
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on armel.

Thanks for the report. I don't know why it wasn't triggered previously,
but I can confirm the problem is not architecture specific, and I can
replicate it on amd64 with

CONFIG_ARGS_amd64 := --disable-docs --enable-bc

Rather than being architecture specific it seems related to the
configuration options that happen to only be used for armel at the
moment.



Processed: Re: Bug#1069549: racket: FTBFS on armel: dh_install: error: missing files, aborting

2024-04-21 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 confirmed
Bug #1069549 [src:racket] racket: FTBFS on armel: dh_install: error: missing 
files, aborting
Added tag(s) confirmed.

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



Bug#1069624: rapidfuzz: Fails to build on arch: all

2024-04-21 Thread Julian Gilbey
Hi Jeremy,

On Sun, Apr 21, 2024 at 02:01:26PM -0400, Jeremy Bícha wrote:
> Source: rapidfuzz
> Version: 3.6.2+ds-2
> Severity: serious
> Tags: ftbfs
> 
> The arch: all build for rapidfuzz is failing:
> 
> https://buildd.debian.org/status/package.php?p=rapidfuzz
> 
> If you use sbuild, I believe you can test this with
> sbuild -arch-all --no-arch-any

Thanks for flagging this.  I've only just fixed taskflow, and will be
able to look at rapidfuzz later this week, all being well.  It's
surprising how many issues new packages can throw up when they're
first build on the multiple archs by the buildds!

Best wishes,

   Julian



Processed: 1069613

2024-04-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 1069613 minor
Bug #1069613 [systemd] systemd: Startup fails after apt full-upgrade
Severity set to 'minor' from 'critical'
>
End of message, stopping processing here.

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



Bug#1069517: closing 1067401, closing 1069517

2024-04-21 Thread Sebastian Ramacher
close 1067401 1.5.12+ds-1.1
close 1069517 1.5.12+ds-1.1
thanks


-- 
Sebastian Ramacher



Bug#1068537: marked as done (ruby-ethon: arch:all package depends on pre-t64 library)

2024-04-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Apr 2024 18:05:37 +
with message-id 
and subject line Bug#1068537: fixed in ruby-ethon 0.16.0-2
has caused the Debian Bug report #1068537,
regarding ruby-ethon: arch:all package depends on pre-t64 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.)


-- 
1068537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-ethon
Version: 0.16.0-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

ruby-ethon builds an Architecture: all package that depends on a library
that is involved in the t64 package (libcurl4). Please make sure that
the packages works with the package using the new 64 time_t ABI and
update the dependencies accordingly.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: ruby-ethon
Source-Version: 0.16.0-2
Done: Antonio Terceiro 

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

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated ruby-ethon 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: Sun, 21 Apr 2024 14:47:38 -0300
Source: ruby-ethon
Architecture: source
Version: 0.16.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Antonio Terceiro 
Closes: 1068537
Changes:
 ruby-ethon (0.16.0-2) unstable; urgency=medium
 .
   * Don't hardcode a dependency on libcurl4 (Closes: #1068537)
Checksums-Sha1:
 0a4d15b017ade9303b14048c0ea7c04041043db3 2172 ruby-ethon_0.16.0-2.dsc
 1c96cb094b68dfd7e6ccb256169b7b8690faca80 4112 ruby-ethon_0.16.0-2.debian.tar.xz
 135c511c1f978311e8b664e8c2e782f29b0e23cf 14158 
ruby-ethon_0.16.0-2_source.buildinfo
Checksums-Sha256:
 e77b5ef353c3f6eae44bc572decb3f4a72dcca2186b55fc32036d37040685d81 2172 
ruby-ethon_0.16.0-2.dsc
 7ea682ad83931c30865bf7431a8870f530c06fddbafa50fd35ceab7361451e3b 4112 
ruby-ethon_0.16.0-2.debian.tar.xz
 8e242c1e1f58500e06b9e853178b58178671d493597796ae9aa6cca003fb6df6 14158 
ruby-ethon_0.16.0-2_source.buildinfo
Files:
 3a3274240be6e2027e4d696f5f165763 2172 ruby optional ruby-ethon_0.16.0-2.dsc
 349fcd9f33aa0a7fe05e757c8e3a5031 4112 ruby optional 
ruby-ethon_0.16.0-2.debian.tar.xz
 718b11e0d8405e0388c8b8641faa0424 14158 ruby optional 
ruby-ethon_0.16.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAmYlUfkACgkQ/A2xu81G
C96O/BAAzkPmpsNVwMb14oF34AYDeGoPd8beSTeSlKBmM7dlR1m0fVVV4Txwan7l
zy1rsE/NWZ6GFVui1P94L1ctRQeEWuUYkOlZkS8ad0F+VE0Xdgss0nnFZWNfOCfr
W2DxGplDSvNcj9r3bepA+JvVzegKrxbc0FNzBXE5eedrIxn98490UTiDA8STI+fG
HGcIJBzCAcyJ6YpVclnFSM4CHyoV5MR7wB9z8x9oEUuB+O14l2YO8qb8CjhnYnEU
c6cCxQ1stE1k9N0o6aDYu/XvOu4TBr1BumVZPW/9FOG8pRd7NIXBbFP8odxm9Of1
TODJd9FFvZWT0UkwVVxBADfi0kVT6ZqnxI90FqCB6YBse7OpMt4I0mJa5TmTqsI6
ilRGnjaXo2W+KIIpumiu81JhXNDk0V4Jy8DuW5thZyWSAkPkmV8FN9V8MfScjsdX
dz3bPBA13JtRBnLbwQm4r2Li68OVGx2eLqpNFRzaYsBP0jdJap1K4vwr6HlAiwUE
j4VMZ0Y7QEnqOzzbcw8TX97cxN7/6pGdWkOkk44iccPcWS0y2B1Rojx3M6ytjOcQ
OXOBV3cHCwEcUdnSC8B0ZUUHiCtLOfWiY8tQLjAekv7RUY+jg9UXWlovXurY9ShT
NPulRohL5pPE8AQH5xpnjzC1L9f3WSoZB6D5z6+SFP/jj6ghRdI=
=YUgJ
-END PGP SIGNATURE-



pgpzLPFUUhRPU.pgp
Description: PGP signature
--- End Message ---


Processed: closing 1067401, closing 1069517

2024-04-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> close 1067401 1.5.12+ds-1.1
Bug #1067401 [trantor] trantor: libtrantor1 has spurious depends on libssl3
There is no source info for the package 'trantor' at version '1.5.12+ds-1.1' 
with architecture ''
Unable to make a source version for version '1.5.12+ds-1.1'
Marked as fixed in versions 1.5.12+ds-1.1.
Bug #1067401 [trantor] trantor: libtrantor1 has spurious depends on libssl3
Marked Bug as done
> close 1069517 1.5.12+ds-1.1
Bug #1069517 [libtrantor1] drogon: FTBFS on armhf: build-dependency not 
installable: libssl3
Marked as fixed in versions trantor/1.5.12+ds-1.1.
Bug #1069517 [libtrantor1] drogon: FTBFS on armhf: build-dependency not 
installable: libssl3
Marked Bug as done
> thanks
Stopping processing here.

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



Bug#1069624: rapidfuzz: Fails to build on arch: all

2024-04-21 Thread Jeremy Bícha
Source: rapidfuzz
Version: 3.6.2+ds-2
Severity: serious
Tags: ftbfs

The arch: all build for rapidfuzz is failing:

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

If you use sbuild, I believe you can test this with
sbuild -arch-all --no-arch-any

Thank you,
Jeremy Bícha



Bug#1069448: marked as done (ipsvd: FTBFS on armhf: make[1]: *** [Makefile:7: check] Error 1)

2024-04-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Apr 2024 17:49:55 +
with message-id 
and subject line Bug#1069448: fixed in ipsvd 1.0.0-6
has caused the Debian Bug report #1069448,
regarding ipsvd: FTBFS on armhf: make[1]: *** [Makefile:7: check] 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.)


-- 
1069448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069448
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ipsvd
Version: 1.0.0-5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>/ipsvd-1.0.0/compile'
> ./compile check-tcpsvd.c
> ./load check-tcpsvd unix.a byte.a `cat socket.lib`
> ./compile check-udpsvd.c
> ./load check-udpsvd unix.a byte.a `cat socket.lib`
> ./compile check-ipsvd-cdb.c
> ./load check-ipsvd-cdb uint32_unpack.o unix.a byte.a
> ./check-local tcpsvd udpsvd ipsvd-cdb `grep -v nossl  Checking tcpsvd...
> Checking udpsvd...
> Checking ipsvd-cdb...
> usage: ipsvd-cdb cdb cdb.tmp dir
> 
> 111
> ipsvd-cdb: fatal: unable to create: 
> /<>/ipsvd/compile/check-tmp.cdb.tmp: invalid argument
> 111
> /<>/ipsvd/compile/ipsvd-cdb.check: 24: cannot open 
> /<>/ipsvd/compile/check-tmp.cdb: No such file
> 0
> ipsvd-cdb failed.
> make[1]: *** [Makefile:7: check] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/ipsvd_1.0.0-5_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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: ipsvd
Source-Version: 1.0.0-6
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated ipsvd 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: Sun, 21 Apr 2024 19:32:53 +0200
Source: ipsvd
Architecture: source
Version: 1.0.0-6
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Closes: 1024283 1069448
Changes:
 ipsvd (1.0.0-6) unstable; urgency=medium
 .
   * QA upload.
   * Re-import package history into GIT.
   * Make the build verbose.
   * Do not omit the hardening flags.  (Closes: #1024283, #1069448)
   * Fix building with -Werror=implicit-function-declaration.
Checksums-Sha1:
 9d2c2fccbdde0538130c422ce455d88d0672de2a 1734 ipsvd_1.0.0-6.dsc
 bff9a3f77d92c787f8e79d36bc2907752827b4ff 6108 ipsvd_1.0.0-6.debian.tar.xz
 91712c6e472ca9e91779dfa650c3d63bfe09e30f 4717 ipsvd_1.0.0-6_source.buildinfo
Checksums-Sha256:
 f31abc6d7790260120fe69753ae709474920ef0c8ebd1881fbbfd9fc8d5a946b 1734 
ipsvd_1.0.0-6.dsc
 d16f38bbaad1066ea29ed5b7ce8955f72104954e8bfddbdd8cc953b4eb6f3c2c 6108 
ipsvd_1.0.0-6.debian.tar.xz
 09de445abaa3efa1fa974bd82bd1bb0c2c777beb1fc3cbf3f080aadb7dbfaf82 4717 
ipsvd_1.0.0-6_source.buildinfo
Files:
 2f924aadfea9d5e807fa4c17101ec56e 1734 net optional ipsvd_1.0.0-6.dsc
 628f662a5c4b036407a1030fe0ac6810 6108 net optional ipsvd_1.0.0-6.debian.tar.xz
 eef4ffe496704e271b5b374ed2025477 4717 net optional 
ipsvd_1.0.0-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmYlTlMQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCNhnD/9TCIp3CNC6Yl5pyGdd3Ac3TpZJtFccaS1C

Bug#1069621: rust-event-listener: no-default-features autopkgtest fails

2024-04-21 Thread Jeremy Bícha
Simple patch attached.

Thank you,
Jeremy Bícha
From: Jeremy Bicha 
Date: Sun, 21 Apr 2024 13:37:18 -0400
Subject: [PATCH] Mark no-default-features autopkgtest as flaky

Closes: #1069621
---
 debian/tests/control | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/tests/control b/debian/tests/control
index e97cdaa..e5008bc 100644
--- a/debian/tests/control
+++ b/debian/tests/control
@@ -18,7 +18,7 @@ Depends:
  librust-futures-lite-1+default-dev,
  librust-try-lock-0.2+default-dev,
  librust-waker-fn-1+default-dev,
-Restrictions: allow-stderr
+Restrictions: allow-stderr, flaky
 
 Test-Command: /usr/share/cargo/bin/cargo-auto-test event-listener 5.3.0
  --all-targets


Bug#1069621: rust-event-listener: no-default-features autopkgtest fails

2024-04-21 Thread Jeremy Bícha
Source: rust-event-listener
Version: 5.3.0-2
Severity: serious
Tags: experimental patch
X-Debbugs-CC: werdah...@riseup.net

rust-event-listener's --no-default-features autopkgtest is failing:

https://ci.debian.net/packages/r/rust-event-listener/unstable/amd64/

This issue will block the rust-event-listener transition. I suggest
marking the autopkgtest as flaky and reporting the issue upstream.

Thank you,
Jeremy Bícha



Bug#1069463: marked as done (blobwars: FTBFS on armhf: src/CReplayData.cpp:41:34: error: cannot convert ‘long int*’ to ‘const time_t*’ {aka ‘const long long int*’})

2024-04-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Apr 2024 17:34:10 +
with message-id 
and subject line Bug#1069463: fixed in blobwars 2.00-4
has caused the Debian Bug report #1069463,
regarding blobwars: FTBFS on armhf: src/CReplayData.cpp:41:34: error: cannot 
convert ‘long int*’ to ‘const time_t*’ {aka ‘const long long int*’}
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.)


-- 
1069463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069463
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: blobwars
Version: 2.00-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security `pkg-config 
> --cflags sdl2 SDL2_mixer SDL2_image SDL2_ttf SDL2_net` -DVERSION=2.00 
> -DRELEASE=1 -DUSEPAK=0 -DPAKNAME=\"blobwars.pak\" 
> -DPAKLOCATION=\"/usr/share/games/blobwars/\" -DUNIX 
> -DGAMEPLAYMANUAL=\"/usr/share/doc/blobwars/index.html\" -Wall 
> -DLOCALEDIR=\"/usr/share/locale/\" 
> -DMEDAL_SERVER_HOST=\"www.parallelrealities.co.uk\" -DMEDAL_SERVER_PORT=80 -g 
> -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -O2 -g -flto -c 
> src/CSwitch.cpp
> cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ 
> is not valid for C++
> src/CReplayData.cpp: In member function ‘void 
> ReplayData::printReplayInformation()’:
> src/CReplayData.cpp:41:34: error: cannot convert ‘long int*’ to ‘const 
> time_t*’ {aka ‘const long long int*’}
>41 | tm *timeinfo = localtime();
>   |  ^~
>   |  |
>   |  long int*
> In file included from /usr/include/features.h:490,
>  from /usr/include/errno.h:25,
>  from src/headers.h:22,
>  from src/CReplayData.cpp:1:
> /usr/include/time.h:141:19: note:   initializing argument 1 of ‘tm* 
> localtime(const time_t*)’
>   141 | extern struct tm *__REDIRECT_NTH (localtime, (const time_t *__timer),
>   |   ^~
> make[1]: *** [Makefile:83: CReplayData.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/blobwars_2.00-3_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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: blobwars
Source-Version: 2.00-4
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated blobwars 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: Sun, 21 Apr 2024 19:08:57 +0200
Source: blobwars
Architecture: source
Version: 2.00-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Closes: 1069463
Changes:
 blobwars (2.00-4) unstable; urgency=medium
 .
   * QA upload.
   * Import package history into GIT.
   * Ignore RELEASE environment variable from salsa CI.
   * Fix FTBFS with 64-bit time_t on 32-bit architectures.  

Bug#1069603: [Pkg-openssl-devel] Bug#1069603: openssl breaks libcrypt-smime-perl autopkgtest: Crypt::SMIME#setPublicKeyStore: failed to store the public cert

2024-04-21 Thread Paul Gevers

Hi

On 21-04-2024 5:56 p.m., Sebastian Andrzej Siewior wrote:

The problem is that libcrypt-smime-perl < 0.29 fails with openssl >= 3.2.0.
This was solved by the Perl team with their 0.29 upload. This and 0.30
didn't migrate to testing and in the meantime we got OpenSSL into
unstable which relies on that fix.
The migration was delayed by the time_t transition.


Ack. I figured that out too.


Could britney be hinted to migrate both at the same time? This should
solve the issue you pointed out.


There is no "please test together" knob if that's what you mean (is that 
what you mean?). I have triggered the test manually, so for now the 
lights are green. Because those expire, I have added a hint to ignore 
the failure of the old version in testing.


Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1063900: gstreamer1.0-plugins-good: missing Breaks+Replaces: gstreamer1.0-plugins-ugly (<< 1.23)

2024-04-21 Thread Jean-Marc

On Wed, 14 Feb 2024 14:58:16 +0100 Andreas Beckmann  wrote:

Package: gstreamer1.0-plugins-good
Version: 1.23.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,
[...]


Current version in sid are the following ones:

$ apt policy gstreamer1.0-plugins-good gstreamer1.0-plugins-ugly
gstreamer1.0-plugins-good:
 Table de version :
 1.24.2-1 500
500 https://deb.debian.org/debian unstable/main amd64 Packages

gstreamer1.0-plugins-ugly:
 Table de version :
 1.24.2-1+b1 500
500 https://deb.debian.org/debian unstable/main amd64 Packages


The following files are in conflict:

/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstamrnb.so
/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstamrwbdec.so
/usr/share/gstreamer-1.0/presets/GstAmrnbEnc.prs


Files mentioned here in the bug report are not present in 
gstreamer1.0-plugins-ugly:1.24.2-1+b1 anymore.


Can you confirm I am not wrong and update the bug report accordingly ?


cheers,


Regards,


Andreas


--
Jean-Marc

(*)
/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstamrnb.so
/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstamrwbdec.so
/usr/share/gstreamer-1.0/presets/GstAmrnbEnc.prs


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1063088: marked as done (weston: NMU diff for 64-bit time_t transition)

2024-04-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Apr 2024 18:37:58 +0200
with message-id 
and subject line Re: Bug#1063088: weston: NMU diff for 64-bit time_t transition
has caused the Debian Bug report #1063088,
regarding weston: NMU diff for 64-bit time_t transition
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.)


-- 
1063088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063088
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: weston
Version: 13.0.0-1
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t

NOTICE: these changes must not be uploaded to unstable yet!

Dear maintainer,

As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
weston as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).

To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.

Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time.  Therefore I have prepared a 0-day NMU for weston
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.

Please find the patch for this NMU attached.

If you have any concerns about this patch, please reach out ASAP.  Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.



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

Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru weston-13.0.0/debian/changelog weston-13.0.0/debian/changelog
--- weston-13.0.0/debian/changelog  2024-01-22 09:00:54.0 +
+++ weston-13.0.0/debian/changelog  2024-02-05 01:50:20.0 +
@@ -1,3 +1,10 @@
+weston (13.0.0-1.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Mon, 05 Feb 2024 01:50:20 +
+
 weston (13.0.0-1) unstable; urgency=medium
 
   * Upload to unstable
diff -Nru weston-13.0.0/debian/control weston-13.0.0/debian/control
--- weston-13.0.0/debian/control2024-01-22 09:00:54.0 +
+++ weston-13.0.0/debian/control2024-02-05 01:50:19.0 +
@@ -72,13 +72,14 @@
  and fast compositor and is suitable for many embedded and mobile use
  cases.
 
-Package: libweston-13-0
+Package: libweston-13-0t64
+Provides: ${t64:Provides}
 Section: libs
 Architecture: linux-any
 Multi-Arch: same
 Depends: ${misc:Depends}, ${shlibs:Depends}
-Replaces: weston (<< 1.12.0-1)
-Breaks: weston (<< 1.12.0-1)
+Replaces: libweston-13-0, weston (<< 1.12.0-1)
+Breaks: libweston-13-0 (<< ${source:Version}), weston (<< 1.12.0-1)
 Description: reference implementation of a wayland compositor (shared libs)
  Part of the Wayland project is also the Weston reference implementation
  of a Wayland compositor. Weston can run as an X client or under Linux
@@ -93,7 +94,7 @@
 Architecture: linux-any
 Depends: libpixman-1-dev,
  libwayland-dev,
- libweston-13-0 (= ${binary:Version}),
+ libweston-13-0t64 (= ${binary:Version}),
  libxkbcommon-dev,
  ${misc:Depends},
  ${shlibs:Depends}
diff -Nru weston-13.0.0/debian/libweston-13-0.install 
weston-13.0.0/debian/libweston-13-0.install
--- weston-13.0.0/debian/libweston-13-0.install 2024-01-22 09:00:54.0 
+
+++ weston-13.0.0/debian/libweston-13-0.install 1970-01-01 00:00:00.0 
+
@@ -1,13 +0,0 @@
-usr/lib/*/libweston-13.so.*

Bug#1068608: marked as done (tfortune dependencies unsatisfiable on 32-bit non-i386 architectures.)

2024-04-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Apr 2024 16:35:59 +
with message-id 
and subject line Bug#1068608: fixed in tfortune 1.0.1-2
has caused the Debian Bug report #1068608,
regarding tfortune dependencies unsatisfiable on 32-bit non-i386 architectures.
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.)


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

Package: tfortune
Version: 1.0.1-1
Tags: trixie, sid
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t

After being rebuilt for the time64 transition, tfortune
depends on both liblopsub1 and liblopsub1t64. As a
result it is uninstallable on architectures that are undergoing
the time64 transition (armel, armhf and some debian-ports
architectures).

Ubuntu has already fixed this issue by removing the hardcoded
dependency on liblopsub1.

https://launchpadlibrarian.net/720835658/tfortune_1.0.1-1build1_1.0.1-1ubuntu1.diff.gz
--- End Message ---
--- Begin Message ---
Source: tfortune
Source-Version: 1.0.1-2
Done: Andre Noll 

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

Debian distribution maintenance software
pp.
Andre Noll  (supplier of updated tfortune 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, 21 Apr 2024 15:52:20 +0200
Source: tfortune
Architecture: source
Version: 1.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Andre Noll 
Changed-By: Andre Noll 
Closes: 1032160 1068608
Changes:
 tfortune (1.0.1-2) unstable; urgency=medium
 .
   [ Helmut Grohne ]
   * Fix FTCBFS: (Closes: #1032160)
 + Also ask for generating config.h.in, which otherwise goes missing in
   cross builds.
 + Pass --build and --host to configure as we cannot use dh_auto_configure.
 + Also export cross tools for make.
 .
   [ Andre Noll ]
   * Remove hard-coded dependency on liblopsub1. (Closes: #1068608)
Checksums-Sha1: 
 6c3de0fc859feabf86c6fefd8c7c47b6792eb3ba 1915 tfortune_1.0.1-2.dsc
 36f6347e05691ed081299e6301158b09fcd5ef63 2088 tfortune_1.0.1-2.debian.tar.xz
Checksums-Sha256: 
 6b42141dc939119fc2bd403002296ef5057a6a35bbbc3ceabfd3ef524e40af61 1915 
tfortune_1.0.1-2.dsc
 2ac1d82cdd5902274f34233cbb0fc3b54a83ed91be1be82a0e1af29dcea27fb1 2088 
tfortune_1.0.1-2.debian.tar.xz
Files: 
 ec74e66272206587ec844ad5f8270d65 1915 games optional tfortune_1.0.1-2.dsc
 e463df6cb6159eae991025db58e6831e 2088 games optional 
tfortune_1.0.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmYlG9sACgkQpU8BhUOC
FIQONBAAoRmXW/SB94oDDhmZToGCuaNLzI1XMKn4u2aQEn8tGITWf5snHqL5ZWey
/0b221EDNd5oSgekeIi0RVF1GuxIMUHBa8mLwJHS6T8kdREcSNrvH6rN04qkgoL1
9OwOjip1v5/6a7X8POdnWQVK6qhdacB+JOv2CWGCa8oBGUtqp89UwzffQSKiqFlw
Dbl8FTO4EnBjd2bSQxrpb4vlIydNjs87lM1jTgOx2XS3TxF13bF0ONSAUD21ag3/
JqWWtnpxYYTUw6wSMciB2FLjHs3Jq6HElhe4trpP/bXB0p1HTlQccoq58jPtTbMJ
W8zLbVsG1mYzMOln9AYAdsXZk7KiL/DUair0Fz2hH+LTTptobDS5JxCrgVYzgN6i
P0GSFdd7G+HsACfHd9uIe0uCZL/3vLL+pMnbzsVab6BYKxcGHxjr0P5z42TiBP/r
a7PfBUJGboq64Z8wgpmESXrmCPI/doTFeRpFRQtC1V0Q/81hdjNGTMbu0Zhu/QxB
ewAj3wOUxR33LwDaCWYGYMv0kApNhh2JUblVbtIVDv80HhnTQ48qqy+hIoYDwEP9
r1eWcJkQOMK/u8ZC2GrK1nB5G6tabE+tmJ/4SqmylYsD13mJ2DkUZhlE3uYXQJ8p
FANlxI7X8oMUIy8e9oTuYwrHgwSiMT1PW5q/KCgZW8eLJSO1u2E=
=H5ek
-END PGP SIGNATURE-



pgpHs12H60_oM.pgp
Description: PGP signature
--- End Message ---


Bug#1069354: notfound 1069375 in 3.1.10-2, closing 1069375, notfound 1069396 in 3.0.1.2-6, closing 1069396 ...

2024-04-21 Thread Ilias Tsitsimpis
notfound 1069375 3.1.10-2
close 1069375 
notfound 1069396 3.0.1.2-6
close 1069396 
close 1069392 
notfound 1069392 1.6.1-2
close 1069380 
notfound 1069380 1.6.0.8-2
close 1069354 
notfound 1069354 4.0.3-2
close 1069420 
notfound 1069420 0.19.1-3
close 1069455 
notfound 1069455 5.0.18.3+dfsg1-5
close 1069494 
notfound 1069494 3.1.3-1
close 1069491 
notfound 1069491 2.9.3.1-1
close 1069489 
notfound 1069489 0.9.2-5
close 1069461 
notfound 1069461 1.6.7-2
close 1069443 
notfound 1069443 1.6.12-2
close 1069500 
notfound 1069500 0.3.0.1-1
close 1069430 
notfound 1069430 0.3.16-1
close 1069442 
notfound 1069442 0.28.0.1-1
close 1069503 
notfound 1069503 0.1.3.2-2
close 1069428 
notfound 1069428 4.16.2.0-2
close 1069459 
notfound 1069459 0.35.2-1
close 1069464 
notfound 1069464 5.3.1.1-1
close 1069431 
notfound 1069431 0.5.8-3
close 1069493 
notfound 1069493 0.2.0.1-1
close 1069501 
notfound 1069501 0.1.0.2-3
close 1069457 
notfound 1069457 3.3.25-1
close 1069522 
notfound 1069522 1.6.2.2-2
close 1069541 
notfound 1069541 0.4.14-1
close 1069537 
notfound 1069537 1.6.9-2
close 1069543 
notfound 1069543 2.91.31-1
close 1069548 
notfound 1069548 1.7.1.7-2
thanks



Processed: RM: ruby-sigar -- ROM; rc-buggy, not needed anymore

2024-04-21 Thread Debian Bug Tracking System
Processing control commands:

> affects -1 + src:ruby-sigar
Bug #1069619 [ftp.debian.org] RM: ruby-sigar -- ROM; rc-buggy, not needed 
anymore
Added indication that 1069619 affects src:ruby-sigar
> block -1 by 1069616
Bug #1069619 [ftp.debian.org] RM: ruby-sigar -- ROM; rc-buggy, not needed 
anymore
1069619 was not blocked by any bugs.
1069619 was not blocking any bugs.
Added blocking bug(s) of 1069619: 1069616
> block 1067084 by -1
Bug #1067084 [src:ruby-sigar] ruby-sigar: FTBFS on arm{el,hf}: 
/usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed 
only with _FILE_OFFSET_BITS=64"
1067084 was not blocked by any bugs.
1067084 was not blocking any bugs.
Added blocking bug(s) of 1067084: 1069619

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



Processed: notfound 1069375 in 3.1.10-2, closing 1069375, notfound 1069396 in 3.0.1.2-6, closing 1069396 ...

2024-04-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> notfound 1069375 3.1.10-2
Bug #1069375 [src:haskell-wai-app-file-cgi] haskell-wai-app-file-cgi: FTBFS on 
arm64: unsatisfiable build-dependencies: 
libghc-http-client-tls-dev-0.3.6.1-cbb7c, 
libghc-http-client-tls-prof-0.3.6.1-cbb7c
No longer marked as found in versions haskell-wai-app-file-cgi/3.1.10-2.
> close 1069375
Bug #1069375 [src:haskell-wai-app-file-cgi] haskell-wai-app-file-cgi: FTBFS on 
arm64: unsatisfiable build-dependencies: 
libghc-http-client-tls-dev-0.3.6.1-cbb7c, 
libghc-http-client-tls-prof-0.3.6.1-cbb7c
Marked Bug as done
> notfound 1069396 3.0.1.2-6
Bug #1069396 [src:haskell-wai-websockets] haskell-wai-websockets: FTBFS on 
arm64: unsatisfiable build-dependencies: libghc-wai-extra-dev-3.1.13.0-14e41, 
libghc-warp-dev-3.3.25-6d963
No longer marked as found in versions haskell-wai-websockets/3.0.1.2-6.
> close 1069396
Bug #1069396 [src:haskell-wai-websockets] haskell-wai-websockets: FTBFS on 
arm64: unsatisfiable build-dependencies: libghc-wai-extra-dev-3.1.13.0-14e41, 
libghc-warp-dev-3.3.25-6d963
Marked Bug as done
> close 1069392
Bug #1069392 [src:haskell-yesod-auth-oauth] haskell-yesod-auth-oauth: FTBFS on 
arm64: unsatisfiable build-dependencies
Marked Bug as done
> notfound 1069392 1.6.1-2
Bug #1069392 {Done: Ilias Tsitsimpis } 
[src:haskell-yesod-auth-oauth] haskell-yesod-auth-oauth: FTBFS on arm64: 
unsatisfiable build-dependencies
No longer marked as found in versions haskell-yesod-auth-oauth/1.6.1-2.
> close 1069380
Bug #1069380 [src:haskell-yesod-persistent] haskell-yesod-persistent: FTBFS on 
arm64: unsatisfiable build-dependencies: libghc-wai-extra-dev-3.1.13.0-14e41, 
libghc-warp-dev-3.3.25-6d963, libghc-wai-extra-prof-3.1.13.0-14e41, 
libghc-warp-prof-3.3.25-6d963
Marked Bug as done
> notfound 1069380 1.6.0.8-2
Bug #1069380 {Done: Ilias Tsitsimpis } 
[src:haskell-yesod-persistent] haskell-yesod-persistent: FTBFS on arm64: 
unsatisfiable build-dependencies: libghc-wai-extra-dev-3.1.13.0-14e41, 
libghc-warp-dev-3.3.25-6d963, libghc-wai-extra-prof-3.1.13.0-14e41, 
libghc-warp-prof-3.3.25-6d963
No longer marked as found in versions haskell-yesod-persistent/1.6.0.8-2.
> close 1069354
Bug #1069354 [src:mighttpd2] mighttpd2: FTBFS on arm64: unsatisfiable 
build-dependencies
Marked Bug as done
> notfound 1069354 4.0.3-2
Bug #1069354 {Done: Ilias Tsitsimpis } [src:mighttpd2] 
mighttpd2: FTBFS on arm64: unsatisfiable build-dependencies
No longer marked as found in versions mighttpd2/4.0.3-2.
> close 1069420
Bug #1069420 [src:elm-compiler] elm-compiler: FTBFS on armhf: unsatisfiable 
build-dependencies
Marked Bug as done
> notfound 1069420 0.19.1-3
Bug #1069420 {Done: Ilias Tsitsimpis } [src:elm-compiler] 
elm-compiler: FTBFS on armhf: unsatisfiable build-dependencies
No longer marked as found in versions elm-compiler/0.19.1-3.
> close 1069455
Bug #1069455 [src:haskell-hoogle] haskell-hoogle: FTBFS on armhf: unsatisfiable 
build-dependencies
Marked Bug as done
> notfound 1069455 5.0.18.3+dfsg1-5
Bug #1069455 {Done: Ilias Tsitsimpis } 
[src:haskell-hoogle] haskell-hoogle: FTBFS on armhf: unsatisfiable 
build-dependencies
No longer marked as found in versions haskell-hoogle/5.0.18.3+dfsg1-5.
> close 1069494
Bug #1069494 [src:haskell-pandoc] haskell-pandoc: FTBFS on armhf: unsatisfiable 
build-dependencies
Marked Bug as done
> notfound 1069494 3.1.3-1
Bug #1069494 {Done: Ilias Tsitsimpis } 
[src:haskell-pandoc] haskell-pandoc: FTBFS on armhf: unsatisfiable 
build-dependencies
No longer marked as found in versions haskell-pandoc/3.1.3-1.
> close 1069491
Bug #1069491 [src:haskell-stack] haskell-stack: FTBFS on armhf: unsatisfiable 
build-dependencies
Marked Bug as done
> notfound 1069491 2.9.3.1-1
Bug #1069491 {Done: Ilias Tsitsimpis } [src:haskell-stack] 
haskell-stack: FTBFS on armhf: unsatisfiable build-dependencies
No longer marked as found in versions haskell-stack/2.9.3.1-1.
> close 1069489
Bug #1069489 [src:haskell-tldr] haskell-tldr: FTBFS on armhf: unsatisfiable 
build-dependencies
Marked Bug as done
> notfound 1069489 0.9.2-5
Bug #1069489 {Done: Ilias Tsitsimpis } [src:haskell-tldr] 
haskell-tldr: FTBFS on armhf: unsatisfiable build-dependencies
No longer marked as found in versions haskell-tldr/0.9.2-5.
> close 1069461
Bug #1069461 [src:haskell-crypton-x509-system] haskell-crypton-x509-system: 
FTBFS on armhf: unsatisfiable build-dependencies: 
libghc-asn1-encoding-dev-0.9.6-4f999, libghc-asn1-types-dev-0.3.4-aa235, 
libghc-base-dev-4.17.2.0-38dbb, libghc-bytestring-dev-0.11.5.2-302b4, 
libghc-containers-dev-0.6.7-e92e7, libghc-crypton-dev-0.33-57ec1, 
libghc-crypton-x509-dev-1.7.6-e20c2, libghc-directory-dev-1.3.7.1-a6844, 
libghc-pem-dev-0.2.4-d84c7, libghc-asn1-encoding-prof-0.9.6-4f999, 
libghc-asn1-types-prof-0.3.4-aa235, libghc-base-prof-4.17.2.0-38dbb, 
libghc-bytestring-prof-0.11.5.2-302b4, libghc-containers-prof-0.6.7-e92e7, 
libghc-crypton-prof-0.33-57ec1, libghc-crypton-x509-prof-1.7.6-e20c2, 

Bug#1066375: marked as done (canna: FTBFS: context.c:105:13: error: implicit declaration of function ‘mkdir’ [-Werror=implicit-function-declaration])

2024-04-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Apr 2024 16:19:08 +
with message-id 
and subject line Bug#1066375: fixed in canna 3.7p3-21
has caused the Debian Bug report #1066375,
regarding canna: FTBFS: context.c:105:13: error: implicit declaration of 
function ‘mkdir’ [-Werror=implicit-function-declaration]
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.)


-- 
1066375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066375
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: canna
Version: 3.7p3-20
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

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

This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Relevant part (hopefully):
> gcc -c -g -Wall -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2   -I../../include -Dlinux -D__amd64__ 
> -D_POSIX_C_SOURCE=199309L  -D_POSIX_SOURCE 
> -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE  
>-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
>   -DFUNCPROTO=15 
> -DNARROWPROTO   context.c
> In file included from /usr/include/inttypes.h:25,
>  from ../../include/canna/sysdep.h:30,
>  from ../../include/canna/RK.h:44,
>  from RKintern.h:58,
>  from context.c:28:
> /usr/include/features.h:195:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   195 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> context.c: In function ‘_RkInitialize’:
> context.c:105:13: error: implicit declaration of function ‘mkdir’ 
> [-Werror=implicit-function-declaration]
>   105 | if (mkdir(path, MKDIR_MODE) < 0 &&
>   | ^
> context.c: At top level:
> context.c:24:13: warning: ‘rcsid’ defined but not used [-Wunused-variable]
>24 | static char rcsid[]="$Id: context.c,v 1.5 2003/09/17 08:50:52 aida_s 
> Exp $";
>   | ^
> cc1: some warnings being treated as errors
> make[5]: *** [Makefile:1123: context.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/canna_3.7p3-20_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=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: canna
Source-Version: 3.7p3-21
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated canna 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: Sun, 21 Apr 2024 17:43:26 +0200
Source: canna
Architecture: source
Version: 3.7p3-21
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Closes: 746999 1035504 1043711 1066375
Changes:
 canna (3.7p3-21) unstable; 

Bug#1066224: marked as done (radvd: FTBFS: gram.c:1531:16: error: implicit declaration of function ‘yylex’ [-Werror=implicit-function-declaration])

2024-04-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Apr 2024 16:08:30 +
with message-id 
and subject line Bug#1066224: fixed in radvd 1:2.19-2
has caused the Debian Bug report #1066224,
regarding radvd: FTBFS: gram.c:1531:16: error: implicit declaration of function 
‘yylex’ [-Werror=implicit-function-declaration]
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.)


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

Hi,

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

This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Relevant part (hopefully):
> gcc -DINET6=1 -DLOG_FACILITY=LOG_DAEMON -DPATH_RADVD_CONF=\"/etc/radvd.conf\" 
> -DPATH_RADVD_LOG=\"/var/log/radvd.log\" -DPATH_RADVD_PID=\"/run/radvd.pid\" 
> -DVERSION=\"2.19\" -I.   -Wdate-time -D_FORTIFY_SOURCE=2 
> -Wno-implicit-function-declaration -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -c -o libradvd_parser_a-gram.o `test 
> -f 'gram.c' || echo './'`gram.c
> gram.c: In function ‘yyparse’:
> gram.c:1531:16: error: implicit declaration of function ‘yylex’ 
> [-Werror=implicit-function-declaration]
>  1531 |   yychar = yylex ();
>   |^
> gram.y: In function ‘readin_config’:
> gram.y:957:17: error: implicit declaration of function ‘yyset_in’ 
> [-Werror=implicit-function-declaration]
>   957 | yyset_in(in);
>   | ^~~~
> gram.y:965:17: error: implicit declaration of function ‘yylex_destroy’ 
> [-Werror=implicit-function-declaration]
>   965 | yylex_destroy();
>   | ^
> cc1: some warnings being treated as errors
> make[2]: *** [Makefile:977: libradvd_parser_a-gram.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/radvd_2.19-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=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: radvd
Source-Version: 1:2.19-2
Done: Geert Stappers 

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

Debian distribution maintenance software
pp.
Geert Stappers  (supplier of updated radvd 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: Sun, 21 Apr 2024 11:16:14 +0200
Source: radvd
Binary: radvd radvd-dbgsym radvdump radvdump-dbgsym
Architecture: source amd64
Version: 1:2.19-2
Distribution: unstable
Urgency: medium
Maintainer: Geert Stappers 
Changed-By: Geert Stappers 
Description:
 radvd  - Router Advertisement Daemon
 radvdump   - dumps Router Advertisements
Closes: 1066224
Changes:
 radvd (1:2.19-2) unstable; urgency=medium
 .
   [Miriam España Acebal]
   * Fix a FTBFS at Trixie  Closes: #1066224
Checksums-Sha1:
 ba346c1379355b96ed00bd0392d98d38eeb47168 2127 radvd_2.19-2.dsc
 6114cc4678012ce6c615ef3b04e7a06c850cce06 168264 radvd_2.19.orig.tar.xz
 

Bug#1069247: libconfig-model-dpkg-perl: test failures

2024-04-21 Thread Julian Andres Klode
On Sun, Apr 21, 2024 at 04:32:48PM +0300, Niko Tyni wrote:
> [Copying Julian as the apt maintainer.]
> 
> On Sat, Apr 20, 2024 at 09:02:35PM +0300, Niko Tyni wrote:
> > On Sat, Apr 20, 2024 at 11:09:17AM +0200, Dominique Dumont wrote:
> > > On Thursday, 18 April 2024 19:21:55 CEST you wrote:
> > > > Source: libconfig-model-dpkg-perl
> > > > Version: 3.004
> > > > Severity: serious
> > > > Tags: ftbfs
> > > > Justification: fails to build from source
> > > 
> > > This really looks like a bug with prove:
> > > 
> > > $ perl t/reorder.t 
> > > ok 1 -  test re-ordered list
> > > 1..1
> > 
> > > I can't see what's wrong with the output of reorder test...
> > 
> > Looks like something is injecting apt progress messages to stdout with
> > CR characters hiding it on the terminal but obviously not from `prove`.
> > 
> > $ perl t/reorder.t |od -c
> 
> > 460   f   o   r   m   a   t   i   o   n   .   .   .   0   %  \r
> > 500
> > *
> > 540  \r   o   k   1   -   t   e   s   t   r   e
> > 560   -   o   r   d   e   r   e   d   l   i   s   t  \n   1   .
> > 600   .   1  \n
> 
> These come from apt, via libapt-pkg-perl which I don't think has ever
> filtered them away. The thing that broke this is surely output changes
> in apt 2.9.
> 
> The crucial difference wrt. at least bookworm seems to be that the
> apt messages used to end with a line feed "\n" before the actual TAP
> format started.  Now it only has a carriage return "\r" there. Apparently
> `prove` ignores unknown lines, but now interprets all the apt output to
> be part of the first line that ends with the 'ok 1' part. So that gets
> ignored as well.
> 
> I see the TAP format spec says at
> 
>   https://testanything.org/tap-version-14-specification.html
> 
>   A Harness should normalize line endings by replacing any instances of
>   \r\n or \r in the TAP document with \n.
> 
> so I suppose this might be a normal/wishlist bug in `prove`. In that case,
> please note that it needs to be fixed in libtest-harness-perl first as
> src:perl just bundles an older version of it.
> 
> Not sure if apt should go back to ending its output with a line
> feed. Julian, what do you think?
> -- 
> Niko

This should be fixed in apt git already, just needs an upload,
which is waiting-ish for some more merges
-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en



Bug#1069368: Updating golang-github-golang-protobuf-1-5 to fix FTBFS

2024-04-21 Thread Mathias Gibbens
On Sat, 2024-04-20 at 22:40 +0800, Shengjing Zhu wrote:
> On Sat, Apr 20, 2024 at 10:28 PM Mathias Gibbens  wrote:
> > 
> > Hi Anthony,
> > 
> >   A few weeks ago you uploaded a new version of golang-google-protobuf
> > to unstable which caused a FTBFS in golang-github-golang-protobuf-1-5
> > v1.5.3 [1,2,3]. This has been blocking the transition of various golang
> > packages from unstable to testing.
> > 
> >   I've verified that v1.5.4 of golang-github-golang-protobuf-1-5 builds
> > fine on my amd64 system. `build-rdeps golang-github-golang-protobuf-1-
> > 5-dev` identifies 219 rdeps in main, so I haven't kicked off a `ratt`
> > run testing for any build regressions with the newer version yet.
> > 
> 
> This is a known regression in 1.5.3, see
> https://github.com/golang/protobuf/issues/1596#issuecomment-1981208282

  Since that appears to be the only change in v1.5.4, would there be
any concerns with uploading that version to unstable? This breakage is
starting to cause FTBFS bugs to be filed against affected packages,
such as hugo (#1069371).

Mathias


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


Bug#1069603: [Pkg-openssl-devel] Bug#1069603: openssl breaks libcrypt-smime-perl autopkgtest: Crypt::SMIME#setPublicKeyStore: failed to store the public cert

2024-04-21 Thread Sebastian Andrzej Siewior
On 2024-04-21 13:42:03 [+0200], Paul Gevers wrote:

> opensslfrom testing3.2.1-3
> libcrypt-smime-perlfrom testing0.28-1
> all others from testingfrom testing
> 
> I copied some of the output at the bottom of this report.
> 
> Currently this regression is blocking the migration of openssl to testing
> [1]. Due to the nature of this issue, I filed this bug report against both
> packages. Can you please investigate the situation and reassign the bug to
> the right package?

The problem is that libcrypt-smime-perl < 0.29 fails with openssl >= 3.2.0. 
This was solved by the Perl team with their 0.29 upload. This and 0.30
didn't migrate to testing and in the meantime we got OpenSSL into
unstable which relies on that fix.
The migration was delayed by the time_t transition.

Could britney be hinted to migrate both at the same time? This should
solve the issue you pointed out.

Sebastian



Bug#1066564: marked as done (gamazons: FTBFS: moves.c:100:10: error: implicit declaration of function ‘countobst’; did you mean ‘count_bits’? [-Werror=implicit-function-declaration])

2024-04-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Apr 2024 15:49:05 +
with message-id 
and subject line Bug#1066564: fixed in gamazons 0.83-12
has caused the Debian Bug report #1066564,
regarding gamazons: FTBFS: moves.c:100:10: error: implicit declaration of 
function ‘countobst’; did you mean ‘count_bits’? 
[-Werror=implicit-function-declaration]
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.)


-- 
1066564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066564
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gamazons
Version: 0.83-11
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

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

This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I. -I.. -DPACKAGE_DATA_DIR=\""/usr/share"\" 
> -DPACKAGE_LOCALE_DIR=\""/usr/share/locale"\" -I/usr/include/goocanvas-2.0 
> -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount 
> -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo 
> -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 
> -I/usr/include/x86_64-linux-gnu -I/usr/include/webp 
> -I/usr/include/gio-unix-2.0 -I/usr/include/cloudproviders 
> -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 
> -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -pthread   -Wdate-time 
> -D_FORTIFY_SOURCE=2  -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c 
> moves.c
> moves.c: In function ‘obst_heval’:
> moves.c:100:10: error: implicit declaration of function ‘countobst’; did you 
> mean ‘count_bits’? [-Werror=implicit-function-declaration]
>   100 |t1 =  countobst(s);
>   |  ^
>   |  count_bits
> moves.c: In function ‘init_engine’:
> moves.c:1734:17: error: implicit declaration of function ‘create_hash’ 
> [-Werror=implicit-function-declaration]
>  1734 |state_hash = create_hash(s);
>   | ^~~
> moves.c: In function ‘load_values_from_file’:
> moves.c:1810:10: warning: ignoring return value of ‘fscanf’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>  1810 |  fscanf(rc_fd, "%d", );
>   |  ^~~
> moves.c:1815:10: warning: ignoring return value of ‘fscanf’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>  1815 |  fscanf(rc_fd, "%d", );
>   |  ^~~
> moves.c:1820:10: warning: ignoring return value of ‘fscanf’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>  1820 |  fscanf(rc_fd, "%d", );
>   |  ^~~
> moves.c:1828:10: warning: ignoring return value of ‘fscanf’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>  1828 |  fscanf(rc_fd, "%d", );
>   |  ^~~
> moves.c:1836:10: warning: ignoring return value of ‘fscanf’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>  1836 |  fscanf(rc_fd, "%d", );
>   |  ^~~
> moves.c:1844:10: warning: ignoring return value of ‘fscanf’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>  1844 |  fscanf(rc_fd, "%d", );
>   |  ^~~
> moves.c:1852:10: warning: ignoring return value of ‘fscanf’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>  1852 |  fscanf(rc_fd, "%d", );
>   |  ^~~
> moves.c:1860:10: warning: ignoring return value of ‘fscanf’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>  1860 |  fscanf(rc_fd, "%s", buffer);
>   |  ^~~
> moves.c:1865:10: warning: ignoring return value of ‘fscanf’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>  1865 |  fscanf(rc_fd, "%s", buffer);
>   |  ^~~
> moves.c:1870:10: warning: 

Bug#1068938: marked as done (less: CVE-2024-32487: with LESSOPEN mishandles \n in paths)

2024-04-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Apr 2024 15:49:35 +
with message-id 
and subject line Bug#1068938: fixed in less 590-2.1
has caused the Debian Bug report #1068938,
regarding less: CVE-2024-32487: with LESSOPEN mishandles \n in paths
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.)


-- 
1068938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068938
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: less
Version: 590-2
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for less.

CVE-2024-32487[0]:
| less through 653 allows OS command execution via a newline character
| in the name of a file, because quoting is mishandled in filename.c.
| Exploitation typically requires use with attacker-controlled file
| names, such as the files extracted from an untrusted archive.
| Exploitation also requires the LESSOPEN environment variable, but
| this is set by default in many common cases.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-32487
https://www.cve.org/CVERecord?id=CVE-2024-32487
[1] https://www.openwall.com/lists/oss-security/2024/04/12/5

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: less
Source-Version: 590-2.1
Done: Salvatore Bonaccorso 

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated less package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 19 Apr 2024 15:09:49 +0200
Source: less
Architecture: source
Version: 590-2.1
Distribution: unstable
Urgency: medium
Maintainer: Milan Kupcevic 
Changed-By: Salvatore Bonaccorso 
Closes: 1064293 1068938
Changes:
 less (590-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Shell-quote filenames when invoking LESSCLOSE (CVE-2022-48624)
 (Closes: #1064293)
   * Fix bug when viewing a file whose name contains a newline (CVE-2024-32487)
 (Closes: #1068938)
Checksums-Sha1: 
 adea696b73ad5c355d91a6aa8a2e5042f8f91af6 1967 less_590-2.1.dsc
 1ebafcce1da00f6a25fd35fe0c6c71a244727748 23072 less_590-2.1.debian.tar.xz
Checksums-Sha256: 
 6f44ded535db6b44364f2b4e8c14ec2ee45bb42aa06e97fd5db721931b63826f 1967 
less_590-2.1.dsc
 b742b498e1f5611ba9e67d0722e13c9fec1b963fe4425fa3864301aa3db09ac4 23072 
less_590-2.1.debian.tar.xz
Files: 
 e942c2c432580ab1b7a130e0985d8d43 1967 text important less_590-2.1.dsc
 f8c14ba0fb8f626ed23d0328991749e8 23072 text important 
less_590-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmYieEFfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89E0s4P/1YpmB3EFprl6ap/4u7flSxmNs6p4/oG
hr06cRgZqPYz08iq8Ek7HGn3ZWqzJpFyqgzycQJo8w3yli5IRdcG4HFHXvHz32fH
b7sND8XZ9JBI76z+NvzBgPBNu/RPCHGLeWAqHfgFovK8op3s6PlmQzC5sgQFt3Dh
6Rt+psNbsBNlTdZWDBd9AF8D0FXTGMZc1OB8Kfwobx3y7C0sXVpqgTST5pgmfQYj
HmVljQ1TBoRs5lQR5tGJY6Tje6swvf2HtGpVTTK/QHi5hofm3v47BTb36txnbUbY
NDYpQwShArieaSGT5f8rg97dvF2Z4eW4Xdz9jG7X0P+fbqmwNx2ozHhacrmwAGlU
j8Bi6UWauhTNFy9UbRWGiF4AF3XQUWWx/afd5jHUYN7y2jROkOCKZ4kLnOZDaln1
N6Fbx4C05hvYFP3GbtPTlwkPUE68yLh7IAmwm6KrMx/IHppcRq+r1kyWa+Qm4zXF
3lil/BFSQYjXfVVLvaKT8C0P7PoVkxQfIkE2wJ8gDtK7rJ4Z20I1CYxirAv5Gl6J
Po6SA0eeTODv4BHoNHjwXN/8qTjF5u/M28RwoO+sYCnjYukSeI5tbd+r7FssEaI1
k9eiZ4zjwIf4vmlYOyrWNOPU7+6a5vLXoZbxtJxzRsQpZ+/IIomq7u0Xddr54NEM
190L5/TLVvaY
=SqSG
-END PGP SIGNATURE-



pgpaW3xpfwmAz.pgp
Description: PGP signature
--- End Message ---


Bug#1064293: marked as done (less: CVE-2022-48624)

2024-04-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Apr 2024 15:49:35 +
with message-id 
and subject line Bug#1064293: fixed in less 590-2.1
has caused the Debian Bug report #1064293,
regarding less: CVE-2022-48624
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.)


-- 
1064293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: less
Version: 590-2
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for less.

CVE-2022-48624[0]:
| close_altfile in filename.c in less before 606 omits shell_quote
| calls for LESSCLOSE.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-48624
https://www.cve.org/CVERecord?id=CVE-2022-48624
[1] https://github.com/gwsw/less/commit/c6ac6de49698be84d264a0c4c0c40bb870b10144

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: less
Source-Version: 590-2.1
Done: Salvatore Bonaccorso 

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated less package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 19 Apr 2024 15:09:49 +0200
Source: less
Architecture: source
Version: 590-2.1
Distribution: unstable
Urgency: medium
Maintainer: Milan Kupcevic 
Changed-By: Salvatore Bonaccorso 
Closes: 1064293 1068938
Changes:
 less (590-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Shell-quote filenames when invoking LESSCLOSE (CVE-2022-48624)
 (Closes: #1064293)
   * Fix bug when viewing a file whose name contains a newline (CVE-2024-32487)
 (Closes: #1068938)
Checksums-Sha1: 
 adea696b73ad5c355d91a6aa8a2e5042f8f91af6 1967 less_590-2.1.dsc
 1ebafcce1da00f6a25fd35fe0c6c71a244727748 23072 less_590-2.1.debian.tar.xz
Checksums-Sha256: 
 6f44ded535db6b44364f2b4e8c14ec2ee45bb42aa06e97fd5db721931b63826f 1967 
less_590-2.1.dsc
 b742b498e1f5611ba9e67d0722e13c9fec1b963fe4425fa3864301aa3db09ac4 23072 
less_590-2.1.debian.tar.xz
Files: 
 e942c2c432580ab1b7a130e0985d8d43 1967 text important less_590-2.1.dsc
 f8c14ba0fb8f626ed23d0328991749e8 23072 text important 
less_590-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmYieEFfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89E0s4P/1YpmB3EFprl6ap/4u7flSxmNs6p4/oG
hr06cRgZqPYz08iq8Ek7HGn3ZWqzJpFyqgzycQJo8w3yli5IRdcG4HFHXvHz32fH
b7sND8XZ9JBI76z+NvzBgPBNu/RPCHGLeWAqHfgFovK8op3s6PlmQzC5sgQFt3Dh
6Rt+psNbsBNlTdZWDBd9AF8D0FXTGMZc1OB8Kfwobx3y7C0sXVpqgTST5pgmfQYj
HmVljQ1TBoRs5lQR5tGJY6Tje6swvf2HtGpVTTK/QHi5hofm3v47BTb36txnbUbY
NDYpQwShArieaSGT5f8rg97dvF2Z4eW4Xdz9jG7X0P+fbqmwNx2ozHhacrmwAGlU
j8Bi6UWauhTNFy9UbRWGiF4AF3XQUWWx/afd5jHUYN7y2jROkOCKZ4kLnOZDaln1
N6Fbx4C05hvYFP3GbtPTlwkPUE68yLh7IAmwm6KrMx/IHppcRq+r1kyWa+Qm4zXF
3lil/BFSQYjXfVVLvaKT8C0P7PoVkxQfIkE2wJ8gDtK7rJ4Z20I1CYxirAv5Gl6J
Po6SA0eeTODv4BHoNHjwXN/8qTjF5u/M28RwoO+sYCnjYukSeI5tbd+r7FssEaI1
k9eiZ4zjwIf4vmlYOyrWNOPU7+6a5vLXoZbxtJxzRsQpZ+/IIomq7u0Xddr54NEM
190L5/TLVvaY
=SqSG
-END PGP SIGNATURE-



pgpESqHgFEIGh.pgp
Description: PGP signature
--- End Message ---


Bug#1061421: Fails to start after an upgrade

2024-04-21 Thread Jeremy Bícha
On Sun, Apr 21, 2024 at 2:36 AM Arto Jantunen  wrote:
>
> Jeremy Bícha  writes:
> > Please verify whether wlgreet is working for you now.
>
> Was something changed somewhere? What, where?
>
> On trixie the issue reproduces exactly the same (even with sway upgraded
> to the binNMU'd version from sid).

There have been a huge amount of changes, but most of those changes
were in Unstable and haven't reached Testing yet.

Marc, there is a fix for sway 1.9 in wlgreet 0.5. Do you want to try
if that improves anything here?

Thank you,
Jeremy Bícha



Processed: time_t patch was never applied

2024-04-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 1062405 important
Bug #1062405 [src:dolfin] dolfin: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
>
End of message, stopping processing here.

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



Bug#1066224: radvd_2.19-2_amd64.changes REJECTED

2024-04-21 Thread Geert Stappers
tags 1066224 pending
stop

On Sun, Apr 21, 2024 at 10:19:31AM +, Debian FTP Masters wrote:
> radvd_2.19-2_amd64.deb: trying to install to unstable, but could not find 
> source (radvd 1:2.19-2)

Oops.  On the upside: an opportunity to add an tag


Groeten
Geert Stappers
-- 
Silence is hard to parse



Processed: Re: radvd_2.19-2_amd64.changes REJECTED

2024-04-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 1066224 pending
Bug #1066224 [src:radvd] radvd: FTBFS: gram.c:1531:16: error: implicit 
declaration of function ‘yylex’ [-Werror=implicit-function-declaration]
Added tag(s) pending.
> stop
Stopping processing here.

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



Bug#1069440: marked as done (olpc-kbdshim: FTBFS on armhf: common.c:342:24: error: ‘struct input_event’ has no member named ‘time’)

2024-04-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Apr 2024 14:51:43 +
with message-id 
and subject line Bug#1069440: fixed in olpc-kbdshim 27-3
has caused the Debian Bug report #1069440,
regarding olpc-kbdshim: FTBFS on armhf: common.c:342:24: error: ‘struct 
input_event’ has no member named ‘time’
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.)


-- 
1069440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069440
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: olpc-kbdshim
Version: 27-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> cc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -Wall -O2 -g 
> -DVERSION=27 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 
> -Wdate-time -D_FORTIFY_SOURCE=2  -c -o olpc-kbdshim-udev.o olpc-kbdshim-udev.c
> common.c: In function ‘inject_uinput_event’:
> common.c:342:24: error: ‘struct input_event’ has no member named ‘time’
>   342 | gettimeofday(, NULL);
>   |^
> make[1]: *** [: common.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/olpc-kbdshim_27-2_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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: olpc-kbdshim
Source-Version: 27-3
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated olpc-kbdshim 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: Sun, 21 Apr 2024 16:05:16 +0200
Source: olpc-kbdshim
Architecture: source
Version: 27-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Closes: 1069440
Changes:
 olpc-kbdshim (27-3) unstable; urgency=medium
 .
   * QA upload.
   * Import package history into GIT.
   * Tune (Pre-)Depends.
   * Do not omit hardening flags.
   * Update Lintian overrides.
   * Add upstream metadata, Homepage and watch file.
   * Work around struct input_event.time kernel api change.  (Closes: #1069440)
Checksums-Sha1:
 cae724493ba030f5a98dd0a9afdcce9c7e7ab605 1904 olpc-kbdshim_27-3.dsc
 2de22160aa93ca7d2a0127c2174c5fa46c765265 3644 olpc-kbdshim_27-3.debian.tar.xz
 6eb40048a37db9dbd68e7c45cd4f4fa7f8222d97 5665 
olpc-kbdshim_27-3_source.buildinfo
Checksums-Sha256:
 49b3e68d9ea7f467d27b1666517bbfaf2861863df661ad93b4242a8192a15d37 1904 
olpc-kbdshim_27-3.dsc
 a98a53fbbf40ab61190f84d21040e08de5638e89da1b25d7028959d80f9fab09 3644 
olpc-kbdshim_27-3.debian.tar.xz
 5e6b98191e67a8ebcf7631c6b41bdb51c8edf3b340bb8b7087d3c5816378cd8c 5665 
olpc-kbdshim_27-3_source.buildinfo
Files:
 f78ef5ef4d019b9cbeaa42304c389a48 1904 admin optional olpc-kbdshim_27-3.dsc
 03fe53787467c9e6773f7fbb67d993d6 3644 admin optional 
olpc-kbdshim_27-3.debian.tar.xz
 a2e92314eeca38e3242b8af8d36bf149 5665 admin optional 
olpc-kbdshim_27-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmYlHY0QHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCJXvD/9FGgyssqgDjA6PheTa7EfPcidtOQXbRpJu

Bug#1067691: FTBFS: double free or corruption

2024-04-21 Thread Bernhard Übelacker

Hello,
I found this one interesting and tried to reproduce it,
and hit this issue quite reliable with an unstable armel chroot,
inside an armhf unstable qemu VM,
or with a Android/LineageOS with real arm CPU.

Unfortunately valgrind is no longer built for armel, and a local armel rebuild
shows issues with latest "-fstack-protector-strong -fstack-clash-protection".

Finally I found this issue leads not to a crash at amd64, but
valgrind uncovers it there reliable [1].

dpkg-buildpackage with valgrind installed uses it automatically.
Therefore the change in [2] might be an improvement?


Increasing the allocation of the input buffer like in [3]
makes the valgrind errors go away.
Unfortunately I don't know what exact size this buffer is expected to have.

Kind regards,
Bernhard




[1]
...
fft const
==1105453== Invalid write of size 4
==1105453==at 0x60BFC25: ??? (in 
/usr/lib/x86_64-linux-gnu/libavutil.so.58.29.100)
==1105453==by 0x4CE1880: av_rdft_calc (in 
/usr/lib/x86_64-linux-gnu/libavcodec.so.60.31.102)
==1105453==by 0x11246F: FFTPlanImpl::execute() (spek-fft.cc:38)
==1105453==by 0x110A76: test_const() (test-fft.cc:21)
==1105453==by 0x1105F5: test_fft() (test-fft.cc:77)
==1105453==by 0x10BF5C: main (test.cc:11)
==1105453==  Address 0x11a828c4 is 4 bytes after a block of size 64 alloc'd
==1105453==at 0x4845DA0: memalign (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==1105453==by 0x4845F01: posix_memalign (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==1105453==by 0x608CC14: av_malloc (in 
/usr/lib/x86_64-linux-gnu/libavutil.so.58.29.100)
==1105453==by 0x1126A0: FFTPlan (spek-fft.h:29)
==1105453==by 0x1126A0: FFTPlanImpl::FFTPlanImpl(int) (spek-fft.cc:27)
==1105453==by 0x112745: FFT::create(int) (spek-fft.cc:24)
==1105453==by 0x1109AE: test_const() (test-fft.cc:13)
==1105453==by 0x1105F5: test_fft() (test-fft.cc:77)
==1105453==by 0x10BF5C: main (test.cc:11)
...


[2]
--- debian/control.orig 2023-01-11 07:25:51.0 +0100
+++ debian/control  2024-04-21 16:30:57.545576734 +0200
@@ -11,3 +11,4 @@ Build-Depends: debhelper-compat (= 13),
libwxgtk3.2-dev,
-   wx-common
+   wx-common,
+   valgrind-if-available
 Standards-Version: 4.6.2


[3]
--- src/spek-fft.h.orig 2023-01-10 05:00:39.0 +0100
+++ src/spek-fft.h  2024-04-21 16:28:07.0 +0200
@@ -28,3 +28,3 @@ public:
 // input data to be aligned by up to 32 bytes (e.g. AVX)
-this->input = (float*) av_malloc(sizeof(float) * input_size);
+this->input = (float*) av_malloc(sizeof(float) * (input_size + 2));
 }



Bug#1067084: ruby-sigar: FTBFS on arm{el,hf}: /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"

2024-04-21 Thread Praveen Arimbrathodiyil
On Mon, 18 Mar 2024 09:13:47 +0100 Sebastian Ramacher 
 wrote:

Justification: fails to build from source (but built successfully in the past)
This packaged can be removed once ruby-eye is removed. RM request filed 
for its only reverse dependency ruby-eye.


OpenPGP_0x8F53E0193B294B75.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1069613: systemd: Startup fails after apt full-upgrade

2024-04-21 Thread Bud Heal
Package: systemd
Version: 252.22-1~deb12u1
Severity: critical
Justification: breaks the whole system
X-Debbugs-Cc: budheal...@gmail.com

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
A couple of non-Debian packages needed libc > 2.31, so I upgraded this
laptop.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I changed sources.list to point to bullseye, apt-get update, apt-get
upgrade --without-new-pkgs, apt-get full-update. Reboot at each upgrade.
I changed sources.list to point to bookworm, including non-free and
non-free-firmware, apt-get update, apt-get upgrade --without-new-pkgs,
reboot, noted that GLIB (libc) had budged to 2.36 and debian_version was
12.5, so time for apt-get full-upgrade. Things were still working fine, 
but not after another reboot.
   * What was the outcome of this action?
Now startup does not complete to login. After I enter the disk password,
a long list of messages come up as usual and the first error was that
apache could not be started. Later boots add a line, Error ucsi_acpi
USBC000:00 PPM init failed (-110)
I used a Bookworm RC3 disk (DLBD) for triage, and tail var/log/syslog
informs that gnome crashed.
I then did apt-get update, upgrade --without-new-pkgs, full-upgrade on a
laptop (installed from Bookworm RC3 and set aside because I had work to
do) and those steps worked fine.
Now, this HP Omen 6-core has been problematic, or at least difficult, in
the past, but I was able to find its firmware and I think Debian now
includes them.
When time allows, I can compare the config and binary files to see what
is different but that startup goes into an endless loop is peculiar.
   * What outcome did you expect instead?
Obviously, init should proceed to login.


-- Package-specific info:

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

Kernel: Linux 6.1.0-9-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages systemd depends on:
ii  libacl12.3.1-3
ii  libaudit1  1:3.0.9-1
ii  libblkid1  2.38.1-5+deb12u1
ii  libc6  2.36-9+deb12u4
ii  libcap21:2.66-4
ii  libcryptsetup122:2.6.1-4~deb12u2
ii  libfdisk1  2.38.1-5+deb12u1
ii  libgcrypt201.10.1-3
ii  libkmod2   30+20221128-1
ii  liblz4-1   1.9.4-1
ii  liblzma5   5.4.1-0.2
ii  libmount1  2.38.1-5+deb12u1
ii  libp11-kit00.24.1-2
ii  libseccomp22.5.4-1+b3
ii  libselinux13.4-1+b6
ii  libssl33.0.11-1~deb12u2
ii  libsystemd-shared  252.22-1~deb12u1
ii  libsystemd0252.22-1~deb12u1
ii  libzstd1   1.5.4+dfsg2-5
ii  mount  2.38.1-5+deb12u1

Versions of packages systemd recommends:
ii  dbus [default-dbus-system-bus]  1.14.10-1~deb12u1
ii  ntpsec [time-daemon]1.2.2+dfsg1-1+deb12u1

Versions of packages systemd suggests:
ii  libfido2-11.12.0-2+b1
ii  libqrencode4  4.1.1-1
ii  libtss2-esys-3.0.2-0  3.2.1-3
ii  libtss2-mu0   3.2.1-3
ii  libtss2-rc0   3.2.1-3
ii  policykit-1   122-3
ii  polkitd   122-3
pn  systemd-boot  
pn  systemd-container 
pn  systemd-homed 
pn  systemd-resolved  
pn  systemd-userdbd   

Versions of packages systemd is related to:
ii  dbus-user-session  1.14.10-1~deb12u1
pn  dracut 
ii  initramfs-tools0.142
ii  libnss-systemd 252.22-1~deb12u1
ii  libpam-systemd 252.22-1~deb12u1
ii  udev   252.22-1~deb12u1

-- no debconf information
[EQUIVALENT] /etc/systemd/system/mysql.service -> 
/usr/lib/systemd/system/mysql.service
[EQUIVALENT] /etc/systemd/system/mysqld.service -> 
/usr/lib/systemd/system/mysqld.service
[EXTENDED]   /usr/lib/systemd/system/rc-local.service -> 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
[EXTENDED]   /usr/lib/systemd/system/systemd-localed.service -> 
/usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf
[EXTENDED]   /usr/lib/systemd/system/user@.service -> 
/usr/lib/systemd/system/user@.service.d/10-login-barrier.conf

5 overridden configuration files found.
==> /var/lib/systemd/deb-systemd-helper-enabled/fstrim.timer.dsh-also <==
/etc/systemd/system/timers.target.wants/fstrim.timer

==> /var/lib/systemd/deb-systemd-helper-enabled/sysstat-collect.timer.dsh-also 
<==
/etc/systemd/system/sysstat.service.wants/sysstat-collect.timer

==> /var/lib/systemd/deb-systemd-helper-enabled/e2scrub_all.timer.dsh-also <==
/etc/systemd/system/timers.target.wants/e2scrub_all.timer

==> /var/lib/systemd/deb-systemd-helper-enabled/mysql.service <==

==> 

Processed: your mail

2024-04-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> block 1069371 by 1069368
Bug #1069371 [src:hugo] hugo: FTBFS on arm64: make[1]: *** [debian/rules:89: 
override_dh_auto_build] Error 25
1069371 was not blocked by any bugs.
1069371 was not blocking any bugs.
Added blocking bug(s) of 1069371: 1069368
>
End of message, stopping processing here.

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



Bug#1041027: marked as done (rapidjson FTBFS with googletest 1.13.0)

2024-04-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Apr 2024 13:34:29 +
with message-id 
and subject line Bug#1041027: fixed in rapidjson 1.1.0+dfsg2-7.2
has caused the Debian Bug report #1041027,
regarding rapidjson FTBFS with googletest 1.13.0
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.)


-- 
1041027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041027
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rapidjson
Version: 1.1.0+dfsg2-7.1
Severity: serious
Tags: ftbfs trixie sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rapidjson.html

...
In file included from /usr/src/gtest/include/gtest/gtest-message.h:57,
 from /usr/src/gtest/include/gtest/gtest-assertion-result.h:46,
 from /usr/src/gtest/include/gtest/gtest.h:64,
 from 
/build/1st/rapidjson-1.1.0+dfsg2/test/unittest/unittest.h:47,
 from 
/build/1st/rapidjson-1.1.0+dfsg2/test/unittest/namespacetest.cpp:15:
/usr/src/gtest/include/gtest/internal/gtest-port.h:270:2: error: #error C++ 
versions less than C++14 are not supported.
  270 | #error C++ versions less than C++14 are not supported.
  |  ^
...
--- End Message ---
--- Begin Message ---
Source: rapidjson
Source-Version: 1.1.0+dfsg2-7.2
Done: Micha Lenk 

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

Debian distribution maintenance software
pp.
Micha Lenk  (supplier of updated rapidjson 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: Sun, 21 Apr 2024 15:12:21 +0200
Source: rapidjson
Architecture: source
Version: 1.1.0+dfsg2-7.2
Distribution: unstable
Urgency: medium
Maintainer: Alexander GQ Gerasiov 
Changed-By: Micha Lenk 
Closes: 1041027
Changes:
 rapidjson (1.1.0+dfsg2-7.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * d/rules: Switch to C++ 14 to fix FTBFS with googletest >= 1.13.0
 (Closes: #1041027)
Checksums-Sha1:
 aa33adebf9d35b4f0768e3d259a5e2274d1a423b 2000 rapidjson_1.1.0+dfsg2-7.2.dsc
 68f0a61bb64a0282e88d314122b7347083ba4cc0 11572 
rapidjson_1.1.0+dfsg2-7.2.debian.tar.xz
 5ac5a42da5e059c51cb19c879b6623b3c54e502e 7459 
rapidjson_1.1.0+dfsg2-7.2_source.buildinfo
Checksums-Sha256:
 29e7433268d674e0ccfa025711b7ccaa48288f83eaa971a005a03aca549c2f79 2000 
rapidjson_1.1.0+dfsg2-7.2.dsc
 d00fb387062a16bc5c1a4c532b86359951b5f92379af9ae88d3524dbc38f7e37 11572 
rapidjson_1.1.0+dfsg2-7.2.debian.tar.xz
 8c1a0f8c473527f838235e53cb99d2e2aae201d60db6e8201099d00372e67369 7459 
rapidjson_1.1.0+dfsg2-7.2_source.buildinfo
Files:
 11fc184dac0742306d2826c716a0a25d 2000 libs optional 
rapidjson_1.1.0+dfsg2-7.2.dsc
 00dceb961335de1d3ca9e3ba74e67bca 11572 libs optional 
rapidjson_1.1.0+dfsg2-7.2.debian.tar.xz
 84943c4a5b0e29c8d830e5e61a57cc53 7459 libs optional 
rapidjson_1.1.0+dfsg2-7.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEo+u0H8Wr1nXO5BxF6mymuVG4UTkFAmYlE54ACgkQ6mymuVG4
UTnEoQ//Vy6Y2MBhSw4pKomekv4GHrvm0bAgffo46JzY5c6pZJynyEwiEoz2YzZb
ues5fj6NXhqfEiBlQREsHGyiaAj1o8m/SeqDZolEACmU9Rvp13YEUEUq2dXpexVp
q01bGbsjirzY6/nx+yBPDjY6jsctiX1kTAEozuKz17J/duAt5c/ZJGfLsfz1KOut
SZA9LQK0OFIRASBIksmlIYFl+qw03YVVWElZhea6VEQLmAp2EHM2l9CidKIiTqX1
U7qTJlTZ4KPdTfepKsDE1G3HWDz+aeCkhwlzMn2fnhuTXjeo/R6T1HFvgcMSEKBx
+8I2Uj0SsV7xLZ+fkMAbQHfsfx78WRLzoDMsnY6a/FzfekZUqDm6cv09DmlZwjFU
shoFirvkfLCv/Qr7qpUbYL4tXQ1axv4+yNVrlmTs+xjjNZXOW9Ii1HEZnY4f8p6V
+xDGx5dJOgalIP35Bn6Bc6RvBIFD9/yJzc6st7mab1zLWEUo2PTR2tHbqvCHWNoj
DlUg6WfvSGmTcUYnVftxwF2omJNdRVlYWaFTY/gTQcv8rmVyDIVQcTAoLYqm6Zff
ie8bhz1tKk8F8SfJG2euop03aRfI8XDrrR41D9Z7Xf7JWf+EjyAJFXisdV/fzFPf
UDcjfwZpBQpeLeRxupgHJhcB7iArtbjvHnYEX6DxIByfgRnwmK8=
=0EVA
-END PGP SIGNATURE-



pgpu4V1ybWmyl.pgp
Description: PGP signature
--- End Message ---


Bug#1069247: libconfig-model-dpkg-perl: test failures

2024-04-21 Thread Niko Tyni
[Copying Julian as the apt maintainer.]

On Sat, Apr 20, 2024 at 09:02:35PM +0300, Niko Tyni wrote:
> On Sat, Apr 20, 2024 at 11:09:17AM +0200, Dominique Dumont wrote:
> > On Thursday, 18 April 2024 19:21:55 CEST you wrote:
> > > Source: libconfig-model-dpkg-perl
> > > Version: 3.004
> > > Severity: serious
> > > Tags: ftbfs
> > > Justification: fails to build from source
> > 
> > This really looks like a bug with prove:
> > 
> > $ perl t/reorder.t 
> > ok 1 -  test re-ordered list
> > 1..1
> 
> > I can't see what's wrong with the output of reorder test...
> 
> Looks like something is injecting apt progress messages to stdout with
> CR characters hiding it on the terminal but obviously not from `prove`.
> 
> $ perl t/reorder.t |od -c

> 460   f   o   r   m   a   t   i   o   n   .   .   .   0   %  \r
> 500
> *
> 540  \r   o   k   1   -   t   e   s   t   r   e
> 560   -   o   r   d   e   r   e   d   l   i   s   t  \n   1   .
> 600   .   1  \n

These come from apt, via libapt-pkg-perl which I don't think has ever
filtered them away. The thing that broke this is surely output changes
in apt 2.9.

The crucial difference wrt. at least bookworm seems to be that the
apt messages used to end with a line feed "\n" before the actual TAP
format started.  Now it only has a carriage return "\r" there. Apparently
`prove` ignores unknown lines, but now interprets all the apt output to
be part of the first line that ends with the 'ok 1' part. So that gets
ignored as well.

I see the TAP format spec says at

  https://testanything.org/tap-version-14-specification.html

  A Harness should normalize line endings by replacing any instances of
  \r\n or \r in the TAP document with \n.

so I suppose this might be a normal/wishlist bug in `prove`. In that case,
please note that it needs to be fixed in libtest-harness-perl first as
src:perl just bundles an older version of it.

Not sure if apt should go back to ending its output with a line
feed. Julian, what do you think?
-- 
Niko



Bug#1041027: rapidjson: diff for NMU version 1.1.0+dfsg2-7.2

2024-04-21 Thread Micha Lenk

Dear maintainer,

On Sun, 21 Apr 2024 15:23:27 +0200 Micha Lenk  wrote:

I've prepared an NMU for rapidjson (versioned as 1.1.0+dfsg2-7.2). The diff
is attached to this message.


I forgot to mention, I've pushed my changes to salsa on branch 
'NMU_fix_for_debbug_1041027':

https://salsa.debian.org/debian/rapidjson/-/commits/NMU_fix_for_debbug_1041027?ref_type=heads

Regards,
Micha



Bug#1041027: rapidjson: diff for NMU version 1.1.0+dfsg2-7.2

2024-04-21 Thread Micha Lenk
Dear maintainer,

I've prepared an NMU for rapidjson (versioned as 1.1.0+dfsg2-7.2). The diff
is attached to this message.

Regards,
Micha
diff -Nru rapidjson-1.1.0+dfsg2/debian/changelog rapidjson-1.1.0+dfsg2/debian/changelog
--- rapidjson-1.1.0+dfsg2/debian/changelog	2022-10-15 18:10:14.0 +0200
+++ rapidjson-1.1.0+dfsg2/debian/changelog	2024-04-21 15:12:21.0 +0200
@@ -1,3 +1,11 @@
+rapidjson (1.1.0+dfsg2-7.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * d/rules: Switch to C++ 14 to fix FTBFS with googletest >= 1.13.0
+(Closes: #1041027)
+
+ -- Micha Lenk   Sun, 21 Apr 2024 15:12:21 +0200
+
 rapidjson (1.1.0+dfsg2-7.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru rapidjson-1.1.0+dfsg2/debian/rules rapidjson-1.1.0+dfsg2/debian/rules
--- rapidjson-1.1.0+dfsg2/debian/rules	2019-01-31 21:17:42.0 +0100
+++ rapidjson-1.1.0+dfsg2/debian/rules	2024-04-21 15:10:49.0 +0200
@@ -3,6 +3,12 @@
 # output every command that modifies files on the build system.
 #DH_VERBOSE = 1
 
+# Needed since googletest 1.13.0 (see #1041027)
+export DEB_CXXFLAGS_MAINT_APPEND = -std=c++14
+
 %:
 	dh $@
 
+override_dh_auto_configure:
+	# Needed since googletest 1.13.0 (see #1041027)
+	dh_auto_configure -- -DRAPIDJSON_BUILD_CXX11=OFF


Processed: Bug#1041027 marked as pending in rapidjson

2024-04-21 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1041027 [src:rapidjson] rapidjson FTBFS with googletest 1.13.0
Ignoring request to alter tags of bug #1041027 to the same tags previously set

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



Bug#1041027: marked as pending in rapidjson

2024-04-21 Thread Micha Lenk
Control: tag -1 pending

Hello,

Bug #1041027 in rapidjson 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/debian/rapidjson/-/commit/1084c76f4a0cd4ae30f650cfa9054868d7342419


d/rules: Switch to C++ 14 to fix FTBFS with googletest >= 1.13.0

Closes: #1041027


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1041027



Bug#1069608: topplot: missing test-depends on python3-all

2024-04-21 Thread Rebecca N. Palmer

Source: topplot
Version: 0.2.2+repack-1
Tags: patch
Severity: serious
Justification: blocks testing migration of other packages

topplot tries to run its autopkgtest in all versions of Python (which is 
good), but does not test-depend on all those versions of Python.


This previously worked because numpy depended on them.  However, this 
has now been removed (see #945824), causing topplot's autopkgtests to fail.


Adding python3-all to the Depends in debian/*tests*/control should fix 
this bug, but I have not actually tested this.




Processed: Re: Bug#1069558: lomiri-ui-toolkit: FTBFS on armel: QWARN : components::UnknownTestFunc() file:///usr/lib/arm-linux-gnueabi/qt5/qml/QtTest/SignalSpy.qml:258: Error: Invalid write to global

2024-04-21 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 important
Bug #1069558 [src:lomiri-ui-toolkit] lomiri-ui-toolkit: FTBFS on armel: QWARN  
: components::UnknownTestFunc() 
file:///usr/lib/arm-linux-gnueabi/qt5/qml/QtTest/SignalSpy.qml:258: Error: 
Invalid write to global property "qtest_count"
Severity set to 'important' from 'serious'
> tags -1 moreinfo
Bug #1069558 [src:lomiri-ui-toolkit] lomiri-ui-toolkit: FTBFS on armel: QWARN  
: components::UnknownTestFunc() 
file:///usr/lib/arm-linux-gnueabi/qt5/qml/QtTest/SignalSpy.qml:258: Error: 
Invalid write to global property "qtest_count"
Added tag(s) moreinfo.

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



Bug#1067915: marked as done (Update Build-Depends for the time64 library renames)

2024-04-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Apr 2024 12:52:47 +
with message-id 
and subject line Bug#1067915: fixed in veusz 3.6.2-1.1
has caused the Debian Bug report #1067915,
regarding Update Build-Depends for the time64 library renames
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.)


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

The package explicitly Build-Depends: libqt5*, these need to be changed to
libqt5*t64 (where applicable) if these deps are needed at all.


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

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

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

Debian distribution maintenance software
pp.
Andreas Metzler  (supplier of updated veusz 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, 21 Apr 2024 14:19:21 +0200
Source: veusz
Architecture: source
Version: 3.6.2-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Andreas Metzler 
Closes: 1067915
Changes:
 veusz (3.6.2-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop runtime library packages (not -dev) from b-d. Closes: #1067915
Checksums-Sha1: 
 7df18445dde24d754994555457f83b1eccfe58b2 2641 veusz_3.6.2-1.1.dsc
 b42044b1ac16da4d5945b3711fcffb4315789edf 18952 veusz_3.6.2-1.1.debian.tar.xz
Checksums-Sha256: 
 025c37da41610e1243805cc095ee584b2bb75ef4cdbc2ca8ad6ae5c02fa17d42 2641 
veusz_3.6.2-1.1.dsc
 6c551080767a381bfcda583b6520bdf943e131f24fbbc1d9bbdf68dabff82aee 18952 
veusz_3.6.2-1.1.debian.tar.xz
Files: 
 c44b525b73c608ee54493362fa613f8d 2641 science optional veusz_3.6.2-1.1.dsc
 9bebbe616f6c84a1f8f824d8dc55cd68 18952 science optional 
veusz_3.6.2-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmYlBWkACgkQpU8BhUOC
FIRKpQ//SatCuI0IonNihe7XQ+lc2MPF2m/tJjFdB9WsH6n73v4jez5IZny6tbcQ
9QucxMoeAbS+cKLlhiIkLbmoHv+45RSaBpAyXUG8DyYsttH5eJD455VV/+L/Xm0a
YcrTtuaL0zw+5J5UOVLZFARic0xxPPc/hzNsY6g77N29qiCrovJpvCz7MdMFQcmH
O1cSrhCdq3HhtdbtL/TqfRJ24x9qAGfbVnQV8FcnFimkvSu3phIex3LhyJX9MO7L
s8wzTAOo5N+puGPStVhi9oDGt7XZo47WMS2AeivY0OTvzrAJn0aGFZlvdqHt0M+Z
X5Wx4++rH7ugTUCAqorbiSVQd6O8iCZpRU0sI94OtchxsEmDRakc3wNZQUmM71wL
XJcD1x+ztfzhHZ0mAS0Hg0evK8+XjV6UowWtvf7M9FpB0GAoWcAD0Ii6ZMtnCgHI
Qb0WHopFcNjDE6NPHLpOnf9u54rocTMyRgQB4Vsh2eXXLkeirH2OlbJSyCUv7qdg
8la7KAersaumQ5V+DWEYFPppGkvgVnJdtioDJ9zF8/kYfFrmmCIGgYuKBXShLVj0
ZttJIi699J999BXwFjbMutTgRmXEmoBbcg0RdfGtDnG/RlL/b5Ts4SKU4Nd/ivjm
QF41Yuq7kNNGVlzx+SKx3s1AoxPoYfCKrXApiHSfQqngkSnLM3E=
=txSs
-END PGP SIGNATURE-



pgpZwX8tWqXAE.pgp
Description: PGP signature
--- End Message ---


Bug#1069558: lomiri-ui-toolkit: FTBFS on armel: QWARN : components::UnknownTestFunc() file:///usr/lib/arm-linux-gnueabi/qt5/qml/QtTest/SignalSpy.qml:258: Error: Invalid write to global property "qtest

2024-04-21 Thread Mike Gabriel

Control: severity -1 important
Control: tags -1 moreinfo

Hi Lucas,

On  Sa 20 Apr 2024 15:21:10 CEST, Lucas Nussbaum wrote:


Source: lomiri-ui-toolkit
Version: 1.3.5100+dfsg-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armel

Hi,

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


Relevant part (hopefully):



[...]


The bug title seems misleading. Causes of the FTBFS are these test  
failures of the following kind:


QWARN  : components::AbstractButtonAPI::test_sensing_area(zero size,  
no margins, tap in visual) "No touch device registered. Register one  
using registerTouchDevice() before using touchClick"
FAIL!  : components::AbstractButtonAPI::test_sensing_area(zero size,  
no margins, tap in visual) 'wait for signal clicked' returned FALSE.  
()


Can this be related to a slightly different test bed? A VM without  
evdev device? (Not sure if a PC-like hardware is required for  
successfully running those tests).


Mike


--

mike gabriel aka sunweaver (Debian Developer)
mobile: +49 (1520) 1976 148
landline: +49 (4351) 486 14 27

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: sunwea...@debian.org, http://sunweavers.net



pgpV5R7jeo7z6.pgp
Description: Digitale PGP-Signatur


Processed: Bug#1041027 marked as pending in rapidjson

2024-04-21 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1041027 [src:rapidjson] rapidjson FTBFS with googletest 1.13.0
Added tag(s) pending.

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



Bug#1041027: marked as pending in rapidjson

2024-04-21 Thread Micha Lenk
Control: tag -1 pending

Hello,

Bug #1041027 in rapidjson 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/debian/rapidjson/-/commit/73905f5cd7babe18f4b1112c67bd535e2ec205f4


d/rules: Switch to C++ 14 to fix FTBFS with googletest >= 1.13.0

Closes: #1041027


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1041027



Bug#1068916: marked as done (phosh: FTBFS on mips64el, riscv64, s390x: 24/26 phosh:tools / check-exported-symbols FAIL 0.03s exit status 1)

2024-04-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Apr 2024 12:35:26 +
with message-id 
and subject line Bug#1068916: fixed in phosh 0.38.0-2
has caused the Debian Bug report #1068916,
regarding phosh: FTBFS on mips64el, riscv64, s390x: 24/26 phosh:tools / 
check-exported-symbols FAIL0.03s   exit status 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.)


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

https://buildd.debian.org/status/fetch.php?pkg=phosh=mips64el=0.37.1-1=1712010515=0


=== 24/26 
test: phosh:tools / check-exported-symbols
start time:   22:28:24
duration: 0.03s
result:   exit status 1
command:  
UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1
 MALLOC_PERTURB_=35 
ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 
/<>/tools/check-exported-symbols src/phosh
--- stdout ---
000a5ed0 gDF .text  009c  Base
phosh_toplevel_get_handle
000ec388 gDF .text  00a4  Base
phosh_arrow_get_progress
00088b50 gDF .text  0094  Base
phosh_mpris_dbus_media_player2_player_call_seek
000c8538 gDF .text  00d8  Base
phosh_lockscreen_get_page
0014c288 gDF .text  00a8  Base
cui_keypad_get_row_spacing
00053d80 gDF .text  0094  Base
phosh_dbus_session_manager_call_register_client
000b6170 gDF .text  0098  Base
phosh_app_tracker_get_type
000907c8 gDF .text  00e0  Base
phosh_osk0_sm_puri_osk0_get_type
000fa8f8 gDF .text  0098  Base
phosh_drag_surface_get_type
00119ed0 gDF .text  0098  Base
phosh_vpn_info_get_type
00100a08 gDF .text  0098  Base
phosh_docked_manager_get_type
000d71a0 gDF .text  00bc  Base
phosh_polkit_auth_prompt_new
0006a880 gDF .text  00d8  Base
phosh_geo_clue_dbus_manager_get_in_use
00141ad0 gDF .text  00cc  Basegtk_rb_tree_unref
000a6168 gDF .text  00a8  Base
phosh_toplevel_is_fullscreen
0011bd48 gDF .text  009c  Base
phosh_vpn_manager_get_icon_name
0006ffb8 gDF .text  00f4  Base
phosh_mm_dbus_modem_proxy_new_for_bus
0012ad40 gDF .text  00d8  Base
phosh_notification_set_id
0012d9c8 gDF .text  01bc  Base
phosh_notification_banner_new
00128548 gDF .text  0098  Base
phosh_monitor_get_type
00110ee8 gDF .text  0098  Base
phosh_overview_get_type
00070210 gDF .text  0098  Base
phosh_mm_dbus_modem_skeleton_get_type
00133798 gDF .text  0058  Base
phosh_notify_feedback_new
00120cb8 gDF .text  00fc  Base
phosh_swipe_away_bin_remove
001000e8 gDF .text  0098  Base
phosh_docked_info_get_type
000a9b10 gDF .text  009c  Base
phosh_wifi_manager_get_icon_name
000d7d18 gDF .text  0098  Base
phosh_portal_request_get_type
0012b180 gDF .text  0118  Base
phosh_notification_set_image
000cade8 gDF .text  0030  Base
phosh_monitor_manager_get_monitor
0007bc10 gDF .text  0068  Base
phosh_session_client_private_dbus_client_private_call_end_session_response_finish
0008c390 gDF .text  0094  Base
phosh_ofono_dbus_sim_manager_call_get_properties
0015fa70 gDF .text  0128  Base
gvc_channel_map_new_from_pa_channel_map
00141d60 gDF .text  0018  Base
gtk_rb_tree_get_root
00121c48 gDF .text  0104  Base
phosh_util_gesture_is_touch
00158860 gDF .text  0088  Base
gvc_mixer_source_new
00157b58 g   

Processed: veusz: diff for NMU version 3.6.2-1.1

2024-04-21 Thread Debian Bug Tracking System
Processing control commands:

> tags 1067915 + patch
Bug #1067915 [src:veusz] Update Build-Depends for the time64 library renames
Added tag(s) patch.
> tags 1067915 + pending
Bug #1067915 [src:veusz] Update Build-Depends for the time64 library renames
Added tag(s) pending.

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



Bug#1067915: veusz: diff for NMU version 3.6.2-1.1

2024-04-21 Thread Andreas Metzler
Control: tags 1067915 + patch
Control: tags 1067915 + pending

Dear maintainer,

I've prepared an NMU for veusz (versioned as 3.6.2-1.1) and
uploaded it to DELAYED/00.

kind regards Andreas
diff -Nru veusz-3.6.2/debian/changelog veusz-3.6.2/debian/changelog
--- veusz-3.6.2/debian/changelog	2023-03-20 07:10:18.0 +0100
+++ veusz-3.6.2/debian/changelog	2024-04-21 14:19:21.0 +0200
@@ -1,3 +1,10 @@
+veusz (3.6.2-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop runtime library packages (not -dev) from b-d. Closes: #1067915
+
+ -- Andreas Metzler   Sun, 21 Apr 2024 14:19:21 +0200
+
 veusz (3.6.2-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru veusz-3.6.2/debian/control veusz-3.6.2/debian/control
--- veusz-3.6.2/debian/control	2023-03-20 07:10:18.0 +0100
+++ veusz-3.6.2/debian/control	2024-04-21 14:18:16.0 +0200
@@ -6,12 +6,6 @@
 Build-Depends: debhelper-compat (= 13),
dh-exec,
dh-python,
-   libqt5core5a,
-   libqt5dbus5,
-   libqt5gui5,
-   libqt5svg5,
-   libqt5widgets5,
-   libqt5xml5,
python3-all,
python3-all-dev,
python3-astropy,


signature.asc
Description: PGP signature


Bug#1069496: marked as done (libmatthew-java: FTBFS on armhf: make[3]: *** [Makefile:104: .enabledebug] Error 2)

2024-04-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Apr 2024 12:20:24 +
with message-id 
and subject line Bug#1069496: fixed in libmatthew-java 0.8.1-3
has caused the Debian Bug report #1069496,
regarding libmatthew-java: FTBFS on armhf: make[3]: *** [Makefile:104: 
.enabledebug] 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.)


-- 
1069496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069496
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libmatthew-java
Version: 0.8.1-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> make[3]: Entering directory '/<>'
> mkdir -p classes
> cpp  -C -P -DDEBUGSETTING=true < cx/ath/matthew/debug/Debug.jpp > 
> cx/ath/matthew/debug/Debug.java
> javac -source 1.5  -cp classes -d classes cx/ath/matthew/debug/Debug.java 
> cx/ath/matthew/utils/Hexdump.java
> warning: [options] bootstrap class path not set in conjunction with -source 5
> error: Source option 5 is no longer supported. Use 7 or later.
> make[3]: *** [Makefile:104: .enabledebug] Error 2


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/libmatthew-java_0.8.1-2_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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: libmatthew-java
Source-Version: 0.8.1-3
Done: Thorsten Alteholz 

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

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated libmatthew-java 
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, 21 Apr 2024 12:42:46 +0200
Source: libmatthew-java
Architecture: source
Version: 0.8.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian IoT Maintainers 

Changed-By: Thorsten Alteholz 
Closes: 1052581 1069496
Changes:
 libmatthew-java (0.8.1-3) unstable; urgency=medium
 .
   [ Vladimir Petko ]
   * debian/rules: use java_compat_level variable provided by java-common to
   adjust --release level to the minimum required by the
   default Java (Closes: #1052581).
   (Closes: #1069496)
   [ Thorsten Alteholz ]
   * debian/control: bump standard to 4.7.0 (no changes)
Checksums-Sha1:
 2c6df0046d6ac6d0133e6ebd9af997ff9d0a8547 2514 libmatthew-java_0.8.1-3.dsc
 9e701bf55a8fe311c4a3c6da4c965c4c675df7bc 29064 
libmatthew-java_0.8.1.orig.tar.gz
 0176ab6ffa05e17cddb616fec825e513ae223e4f 4848 
libmatthew-java_0.8.1-3.debian.tar.xz
 3c2e30396dfe11ce7f6f5327f427a3ba26611152 14707 
libmatthew-java_0.8.1-3_amd64.buildinfo
Checksums-Sha256:
 8b5143b15ea5345bb5db771a6d5a78c221c2f6d7f4fea9550ee0689d1714e7ac 2514 
libmatthew-java_0.8.1-3.dsc
 46782b940c71d8db07470633efcf65c2aeda94de9a846fe178a5918fb2ad026f 29064 
libmatthew-java_0.8.1.orig.tar.gz
 b23c041a7fd9f3b29647b220379b9cc9ac9024f2d757404899658ad2aa020e3e 4848 
libmatthew-java_0.8.1-3.debian.tar.xz
 93cb05769d26df6609358bb2ca6c0fedc1bd1b3312be96b2729e2b0e7bb093c9 14707 
libmatthew-java_0.8.1-3_amd64.buildinfo
Files:
 0f58449b62bd3e8cdd7c587240ecdda4 2514 java optional libmatthew-java_0.8.1-3.dsc
 ba33e325acc6689cc3cdd5226cfe8cb1 29064 java optional 
libmatthew-java_0.8.1.orig.tar.gz
 

Processed: Re: openmpi: 32 bit pmix_init:startup:internal-failure: help-pmix-runtime.txt: No such file

2024-04-21 Thread Debian Bug Tracking System
Processing control commands:

> reopen 1069106
Bug #1069106 {Done: Alastair McKinstry } [src:openmpi] 
openmpi: 32 bit pmix_init:startup:internal-failure: help-pmix-runtime.txt: No 
such 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 openmpi/4.1.6-11.

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



Bug#1069106: openmpi: 32 bit pmix_init:startup:internal-failure: help-pmix-runtime.txt: No such file

2024-04-21 Thread Drew Parsons
Source: openmpi
Version: 4.1.6-12
Followup-For: Bug #1069106
Control: reopen 1069106

4.1.6-12 was intended to fix this bug, but it's still occuring

e.g.
https://ci.debian.net/packages/o/openmpi/unstable/i386/45630865/
https://ci.debian.net/packages/o/openmpi/unstable/armhf/45630866/



Processed: Bug#1068916 marked as pending in phosh

2024-04-21 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1068916 [src:phosh] phosh: FTBFS on mips64el, riscv64, s390x: 24/26 
phosh:tools / check-exported-symbols FAIL0.03s   exit status 1
Ignoring request to alter tags of bug #1068916 to the same tags previously set

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



Bug#1068916: marked as pending in phosh

2024-04-21 Thread Guido Günther
Control: tag -1 pending

Hello,

Bug #1068916 in phosh 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/DebianOnMobile-team/phosh/-/commit/4aa47c933c49566e476f006e65348280fe1dcf67


tests: Skip symbol check on some architectures

Closes: #1068916


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1068916



Bug#1068422: possibly caused by python 3.12.3 Re: Bug#1068422: can't import dask.dataframe - TypeError: descriptor '__call__' for 'type' objects doesn't apply to a 'property' object

2024-04-21 Thread Rebecca N. Palmer
This bug is not *obviously* known to dask upstream, but their CI is 
failing and I haven't checked why.


It happens only in Python 3.12, not 3.11:
https://ci.debian.net/packages/d/dask/unstable/amd64/45013666/
and still doesn't happen in testing, but does happen in mostly-testing 
with 
src:python3-defaults,src:db5.3,src:keras,src:nodejs,src:openssl,src:python3-stdlib-extensions,src:python3.11,src:python3.12,src:readline,src:udisks2,src:viagee 
from unstable:

https://ci.debian.net/packages/d/dask/testing/amd64/45564690/

This suggests that the trigger may be the upgrade of Python itself 
(3.12.2-1 in testing -> 3.12.3-1 in unstable).


*Possibly* related items from the upstream Python changelog:
https://github.com/python/cpython/issues/101293
https://github.com/python/cpython/issues/117110



Bug#1069603: marked as done (openssl breaks libcrypt-smime-perl autopkgtest: Crypt::SMIME#setPublicKeyStore: failed to store the public cert)

2024-04-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Apr 2024 14:00:25 +0200
with message-id <3e4139f7-77f3-45ab-b94c-f531c78fe...@debian.org>
and subject line Re: openssl breaks libcrypt-smime-perl autopkgtest: 
Crypt::SMIME#setPublicKeyStore: failed to store the public cert
has caused the Debian Bug report #1069603,
regarding openssl breaks libcrypt-smime-perl autopkgtest: 
Crypt::SMIME#setPublicKeyStore: failed to store the public cert
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.)


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

Source: openssl, libcrypt-smime-perl
Control: found -1 openssl/3.2.1-3
Control: found -1 libcrypt-smime-perl/0.28-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
opensslfrom testing3.2.1-3
libcrypt-smime-perlfrom testing0.28-1
all others from testingfrom testing

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

Currently this regression is blocking the migration of openssl to 
testing [1]. Due to the nature of this issue, I filed this bug report 
against both packages. Can you please investigate the situation and 
reassign the bug to the right package?


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/libc/libcrypt-smime-perl/45599656/log.gz


 50s not ok 14 - Load the default public key store
 50s=20
 50s #   Failed test 'Load the default public key store'
 50s #   at t/04-taint.t line 257.
 50s # died: Crypt::SMIME#setPublicKeyStore: failed to store the 
public cert at t/04-taint.t line 257.

 50s Failed 2/7 subtests=20


OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---

Hi all,

On Sun, 21 Apr 2024 13:42:03 +0200 Paul Gevers  wrote:
With a recent upload of openssl the autopkgtest of libcrypt-smime-perl 
fails in testing when that autopkgtest is run with the binary packages 
of openssl from unstable. It passes when run with only packages from 
testing. In tabular form:


Sorry for the noise, this is already fixed in unstable (which I forgot 
to check).


Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---


Processed: bug 1069449 is forwarded to https://github.com/netblue30/firejail/issues/5906

2024-04-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 1069449 https://github.com/netblue30/firejail/issues/5906
Bug #1069449 [src:firejail] firejail: FTBFS on armhf: ccnMX2lv.s:1765: Error: 
symbol `fopen64' is already defined
Set Bug forwarded-to-address to 
'https://github.com/netblue30/firejail/issues/5906'.
> thanks
Stopping processing here.

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



Bug#1069435: marked as done (olpc-powerd: FTBFS on armhf: olpc-switchd.c:311:14: error: ‘struct input_event’ has no member named ‘time’)

2024-04-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Apr 2024 11:51:41 +
with message-id 
and subject line Bug#1069435: fixed in olpc-powerd 23-5
has caused the Debian Bug report #1069435,
regarding olpc-powerd: FTBFS on armhf: olpc-switchd.c:311:14: error: ‘struct 
input_event’ has no member named ‘time’
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.)


-- 
1069435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069435
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: olpc-powerd
Version: 23-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> cc -Wall -O2 -g -DVERSION=23 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
> -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro  pnmto565fb.c   
> -o pnmto565fb
> pnmto565fb.c: In function ‘showimage’:
> pnmto565fb.c:374:5: warning: implicit declaration of function ‘readahead’ 
> [-Wimplicit-function-declaration]
>   374 | readahead(fd, 0, sb.st_size);
>   | ^
> olpc-switchd.c: In function ‘round_secs’:
> olpc-switchd.c:311:14: error: ‘struct input_event’ has no member named ‘time’
>   311 | return ev->time.tv_sec + ((ev->time.tv_usec > 50) ? 1 : 0);
>   |  ^~
> olpc-switchd.c:311:34: error: ‘struct input_event’ has no member named ‘time’
>   311 | return ev->time.tv_sec + ((ev->time.tv_usec > 50) ? 1 : 0);
>   |  ^~
> olpc-switchd.c: In function ‘power_button_event’:
> olpc-switchd.c:323:11: error: ‘struct input_event’ has no member named ‘time’
>   323 | ev->time.tv_sec, ev->time.tv_usec,
>   |   ^~
> olpc-switchd.c:323:28: error: ‘struct input_event’ has no member named ‘time’
>   323 | ev->time.tv_sec, ev->time.tv_usec,
>   |^~
> pnmto565fb.c:312:25: warning: variable ‘rightfillcols’ set but not used 
> [-Wunused-but-set-variable]
>   312 | int bottomfillrows, rightfillcols;
>   | ^
> olpc-switchd.c: In function ‘lid_event’:
> olpc-switchd.c:339:11: error: ‘struct input_event’ has no member named ‘time’
>   339 | ev->time.tv_sec, ev->time.tv_usec,
>   |   ^~
> olpc-switchd.c:339:28: error: ‘struct input_event’ has no member named ‘time’
>   339 | ev->time.tv_sec, ev->time.tv_usec,
>   |^~
> olpc-switchd.c: In function ‘ebook_event’:
> olpc-switchd.c:359:11: error: ‘struct input_event’ has no member named ‘time’
>   359 | ev->time.tv_sec, ev->time.tv_usec,
>   |   ^~
> olpc-switchd.c:359:28: error: ‘struct input_event’ has no member named ‘time’
>   359 | ev->time.tv_sec, ev->time.tv_usec,
>   |^~
> olpc-switchd.c: In function ‘acpwr_event’:
> olpc-switchd.c:379:11: error: ‘struct input_event’ has no member named ‘time’
>   379 | ev->time.tv_sec, ev->time.tv_usec,
>   |   ^~
> olpc-switchd.c:379:28: error: ‘struct input_event’ has no member named ‘time’
>   379 | ev->time.tv_sec, ev->time.tv_usec,
>   |^~
> olpc-switchd.c: In function ‘round_secs’:
> olpc-switchd.c:312:1: warning: control reaches end of non-void function 
> [-Wreturn-type]
>   312 | }
>   | ^
> make[1]: *** [: olpc-switchd] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/olpc-powerd_23-4_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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: olpc-powerd
Source-Version: 23-5
Done: Andreas Beckmann 

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

A summary of the changes between this 

Bug#1068224: marked as done (deepin-movie, dependencies unsatisfiable on 32-bit non-i386 architectures.)

2024-04-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Apr 2024 11:49:36 +
with message-id 
and subject line Bug#1068224: fixed in deepin-movie-reborn 5.10.8-2.1
has caused the Debian Bug report #1068224,
regarding deepin-movie, dependencies unsatisfiable on 32-bit non-i386 
architectures.
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.)


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

Package: deepin-movie
Version: 5.10.8-2
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t

After being rebuilt for the time64 transition, deepin-movie
still depends on libqt5concurrent5. As a
result it is uninstallable on architectures that are undergoing
the time64 transition (armel, armhf and some debian-ports
archictures).

Ubuntu seem to have fixed this by manually changing the
dependency.
--- End Message ---
--- Begin Message ---
Source: deepin-movie-reborn
Source-Version: 5.10.8-2.1
Done: Andreas Metzler 

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

Debian distribution maintenance software
pp.
Andreas Metzler  (supplier of updated deepin-movie-reborn 
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, 21 Apr 2024 13:23:59 +0200
Source: deepin-movie-reborn
Architecture: source
Version: 5.10.8-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Deepin Packaging Team 

Changed-By: Andreas Metzler 
Closes: 1068224
Changes:
 deepin-movie-reborn (5.10.8-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Change hardcoded dependency to libqt5concurrent5t64 instead of
 libqt5concurrent5. Closes: #1068224
Checksums-Sha1: 
 10707f255fdf4121066b83383d41ea922c969e30 2845 
deepin-movie-reborn_5.10.8-2.1.dsc
 9388148bc2eccd63cf90c36dd522f26c7a021dfb 7880 
deepin-movie-reborn_5.10.8-2.1.debian.tar.xz
Checksums-Sha256: 
 b91dc206ba7e7f17ab7c8627ac8e2c00633771b9bc95930f436a0534b1be5db5 2845 
deepin-movie-reborn_5.10.8-2.1.dsc
 2fc763cc3af124a6b75b15112c57c949b9cb21ce7265eea94f21c2a8a46a3660 7880 
deepin-movie-reborn_5.10.8-2.1.debian.tar.xz
Files: 
 6e692883e4a4ec7cce89df04cd734f68 2845 video optional 
deepin-movie-reborn_5.10.8-2.1.dsc
 e777c7206a2b05a7bb11a3d6cf433b17 7880 video optional 
deepin-movie-reborn_5.10.8-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmYk+U8ACgkQpU8BhUOC
FIQMlg/5AcALiJ4PwdV4rRCdgLC5LpeTme1/V03I6Xz3SGUCPthbr5m/GKh15BpE
EKdfz5sOi54TbCq1iorBDgKt5hzA4BQKaQR7kV5I4NgRbJZZGCtWzeB0tX6GCm4n
Y7zsN3poU3SrlR4aRZyK41xORRjXsWpPKLv4nv5M9SedxJkMCEyvRIMkFNy+Lokc
6pjJir68VuHqgaIsVMgjlJZpj2Gl9Ur968QVLl724tdGAmoPKnTRBn1WyZSPf6b7
ERGjDfKbuwWDLo5gm3SA6vLbTYxkhvS4o/w7XeSnp6KmuOLBNig9kWXWSAl8TBEM
EHvQFN8upYBj73KjFJBw0CRzZpG6KuxN+8T79wEI1FNcVr0Mx4hOSHECGyxI6xH1
1omYEN8MR0qbmHmdXnVB/9izdKLR5BhF32AXKGC0TUKe157sa3msmTvRkqlCMxml
2clqdt+7Tn26740Q96MTgf8YUUcaB1saHK1MH5GItvcjGafyG8CeF3CF3kVru5bi
NFTzkkGu3nb1viUgajlsJ2+Dq0IvjUL2lmLuJeJzZHY2jF0TBV73BHp6zmYWxcTl
6+4H4JUC5U5Bgeapa8KKnLKKJto//yr+qcDJjfr3k0xw2lKmTJCsCsr9cyf5eGK0
JBD0huTQyPRU9vkvwxQUoSlYrmJ91iz57fYAk9Vsfmduw8c2lPE=
=iqv3
-END PGP SIGNATURE-



pgpVI_3Nml6zx.pgp
Description: PGP signature
--- End Message ---


Processed: openssl breaks libcrypt-smime-perl autopkgtest: Crypt::SMIME#setPublicKeyStore: failed to store the public cert

2024-04-21 Thread Debian Bug Tracking System
Processing control commands:

> found -1 openssl/3.2.1-3
Bug #1069603 [src:openssl, src:libcrypt-smime-perl] openssl breaks 
libcrypt-smime-perl autopkgtest: Crypt::SMIME#setPublicKeyStore: failed to 
store the public cert
Marked as found in versions openssl/3.2.1-3.
> found -1 libcrypt-smime-perl/0.28-1
Bug #1069603 [src:openssl, src:libcrypt-smime-perl] openssl breaks 
libcrypt-smime-perl autopkgtest: Crypt::SMIME#setPublicKeyStore: failed to 
store the public cert
Marked as found in versions libcrypt-smime-perl/0.28-1.

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



Bug#1069603: openssl breaks libcrypt-smime-perl autopkgtest: Crypt::SMIME#setPublicKeyStore: failed to store the public cert

2024-04-21 Thread Paul Gevers

Source: openssl, libcrypt-smime-perl
Control: found -1 openssl/3.2.1-3
Control: found -1 libcrypt-smime-perl/0.28-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
opensslfrom testing3.2.1-3
libcrypt-smime-perlfrom testing0.28-1
all others from testingfrom testing

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

Currently this regression is blocking the migration of openssl to 
testing [1]. Due to the nature of this issue, I filed this bug report 
against both packages. Can you please investigate the situation and 
reassign the bug to the right package?


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/libc/libcrypt-smime-perl/45599656/log.gz


 50s not ok 14 - Load the default public key store
 50s=20
 50s #   Failed test 'Load the default public key store'
 50s #   at t/04-taint.t line 257.
 50s # died: Crypt::SMIME#setPublicKeyStore: failed to store the 
public cert at t/04-taint.t line 257.

 50s Failed 2/7 subtests=20


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1068738: marked as done (gfeeds: python failure at startup)

2024-04-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Apr 2024 11:34:55 +
with message-id 
and subject line Bug#1068738: fixed in gnome-feeds 2.2.0-3
has caused the Debian Bug report #1068738,
regarding gfeeds: python failure at startup
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.)


-- 
1068738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068738
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-feeds
Version: 2.2.0-2
Severity: grave

Hello, after a recent dist-upgrade to unstable, gfeeds crashes at
startup. This makes the package unusable.

-Ralf.

% gfeeds
Traceback (most recent call last):
  File "/usr/bin/gfeeds", line 75, in 
from gfeeds import __main__
  File "/usr/lib/python3/dist-packages/gfeeds/__main__.py", line 9, in 
from gfeeds.app_window import GFeedsAppWindow
  File "/usr/lib/python3/dist-packages/gfeeds/app_window.py", line 2, in 

from gfeeds.main_leaflet import MainLeaflet
  File "/usr/lib/python3/dist-packages/gfeeds/main_leaflet.py", line 11, in 

from gfeeds.webview import GFeedsWebView
  File "/usr/lib/python3/dist-packages/gfeeds/webview.py", line 4, in 
from gfeeds.util.build_reader_html import build_reader_html
  File "/usr/lib/python3/dist-packages/gfeeds/util/build_reader_html.py", line 
4, in 
from gfeeds.util.readability_wrapper import RDoc
  File "/usr/lib/python3/dist-packages/gfeeds/util/readability_wrapper.py", 
line 3, in 
from readability.readability import *
  File "/usr/lib/python3/dist-packages/readability/__init__.py", line 3, in 

from .readability import Document
  File "/usr/lib/python3/dist-packages/readability/readability.py", line 11, in 

from .cleaners import clean_attributes
  File "/usr/lib/python3/dist-packages/readability/cleaners.py", line 3, in 

from lxml.html.clean import Cleaner
  File "/usr/lib/python3/dist-packages/lxml/html/clean.py", line 18, in 
raise ImportError(
ImportError: lxml.html.clean module is now a separate project lxml_html_clean.
Install lxml[html_clean] or lxml_html_clean directly.


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

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

Versions of packages gnome-feeds depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4+b2
ii  gir1.2-adw-1 1.5.0-1
ii  gir1.2-webkit-6.02.44.1-1
ii  python3  3.11.8-1
ii  python3-arrow1.3.0-1
ii  python3-bs4  4.12.3-1
ii  python3-feedparser   6.0.10-1
ii  python3-gi   3.48.2-1
ii  python3-html5lib 1.1-6
ii  python3-humanize 4.9.0-1
ii  python3-listparser   0.18-3
ii  python3-lxml 5.2.1-1
ii  python3-magic2:0.4.27-3
ii  python3-pil  10.3.0-2
ii  python3-pygments 2.17.2+dfsg-1
ii  python3-readability  0.8.1+dfsg1-3
ii  python3-requests 2.31.0+dfsg-1
ii  python3-syndom   1.0-2
ii  python3-tz   2024.1-2
ii  xdg-utils1.1.3-4.1

gnome-feeds recommends no packages.

gnome-feeds suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gnome-feeds
Source-Version: 2.2.0-3
Done: Jeremy Bícha 

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

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated gnome-feeds 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 

  1   2   >