Bug#1017626: marked as done (r-cran-glmmtmb: autopkgtest regression on i386: times out)

[Debian Bug Tracking System]

Your message dated Sun, 18 Sep 2022 05:20:35 +
with message-id 
and subject line Bug#1017626: fixed in r-cran-glmmtmb 1.1.4+dfsg-3
has caused the Debian Bug report #1017626,
regarding r-cran-glmmtmb: autopkgtest regression on i386: times out
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.)


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

Source: r-cran-glmmtmb
Version: 1.1.4+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: timeout

Dear maintainer(s),

I looked at the results of the autopkgtest of your package because it 
was showing up on our page for long running tests on i386. I noticed 
that your package regressed on armhf around Mid July 2022, as it started 
to time out on the run-unit-test test after 2:47 hours while it passed 
in several minutes before.


Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

https://ci.debian.net/packages/r/r-cran-glmmtmb/testing/i386/

https://ci.debian.net/data/autopkgtest/testing/i386/r/r-cran-glmmtmb/24014022/log.gz

methods: 
S

simulate consistency with glm/lm: ...
Ranef etc.: ...S...
misc: .
offset: S
predict: .SSS
Predict two-column response case: SS.S....S...S..
reml:
REML: ...autopkgtest [21:13:54]: ERROR: timed out on command "su -s 
/bin/bash debci -c set -e; export USER=`id -nu`; . /etc/profile 
>/dev/null 2>&1 || true;  . ~/.profile >/dev/null 2>&1 || true; 
buildtree="/tmp/autopkgtest-lxc.gn26h5iq/downtmp/build.QTo/src"; mkdir 
-p -m 1777 -- 
"/tmp/autopkgtest-lxc.gn26h5iq/downtmp/run-unit-test-artifacts"; export 
AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.gn26h5iq/downtmp/run-unit-test-artifacts"; 
export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755 
"/tmp/autopkgtest-lxc.gn26h5iq/downtmp/autopkgtest_tmp"; export 
AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.gn26h5iq/downtmp/autopkgtest_tmp"; 
export ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive; 
export LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=2; unset LANGUAGE 
LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE   LC_MONETARY LC_MESSAGES 
LC_PAPER LC_NAME LC_ADDRESS   LC_TELEPHONE LC_MEASUREMENT 
LC_IDENTIFICATION LC_ALL;rm -f /tmp/autopkgtest_script_pid; set -C; echo 
$$ > /tmp/autopkgtest_script_pid; set +C; trap "rm -f 
/tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd "$buildtree"; chmod 
+x 
/tmp/autopkgtest-lxc.gn26h5iq/downtmp/build.QTo/src/debian/tests/run-unit-test; 
touch /tmp/autopkgtest-lxc.gn26h5iq/downtmp/run-unit-test-stdout 
/tmp/autopkgtest-lxc.gn26h5iq/downtmp/run-unit-test-stderr; 
/tmp/autopkgtest-lxc.gn26h5iq/downtmp/build.QTo/src/debian/tests/run-unit-test 
2> >(tee -a /tmp/autopkgtest-lxc.gn26h5iq/downtmp/run-unit-test-stderr 
>&2) > >(tee -a 
/tmp/autopkgtest-lxc.gn26h5iq/downtmp/run-unit-test-stdout);" (kind: test)

autopkgtest [21:13:54]: test run-unit-test: ---]
run-unit-testFAIL timed out


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: r-cran-glmmtmb
Source-Version: 1.1.4+dfsg-3
Done: Nilesh Patra 

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

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated r-cran-glmmtmb 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, 18 Sep 2022 10:04:45 +0530
Source: r-cran-glmmtmb
Architecture: source
Version: 1.1.4+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Nilesh Patra 
Closes: 1017626
Changes:
 r-cran-glmmtmb (1.1.4+dfsg-3) unstable; urgency=medium
 .
   * Team Upload.
   * Skip a few tests on i386 (Closes: #1017626)
   * Add versioned deps to ease transition
Checksums-Sha1:
 2267adea8d1750b2d4a729752b3b648cd056023a 2255 r-cran-glmmtmb_1.1.4+dfsg-3.dsc
 

Bug#1019936: marked as done (r-cran-tmb must depend on the exact upstream version of r-cran-matrix it was built with or drop the warning)

[Debian Bug Tracking System]

Your message dated Sun, 18 Sep 2022 09:58:33 +0530
with message-id <20220918042833.eufooiobdw4sv...@nileshpatra.info>
and subject line Re: r-cran-tmb must depend on the exact upstream version of 
r-cran-matrix it was built with or drop the warning
has caused the Debian Bug report #1019936,
regarding r-cran-tmb must depend on the exact upstream version of r-cran-matrix 
it was built with or drop the warning
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.)


-- 
1019936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019936
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: r-cran-tmb
Version: 1.9.1-1
Severity: serious
Control: affects -1 r-cran-glmmtmb src:r-cran-glmmtmb
Control: block 1017626 by -1

> library(TMB)
Warning message:
In checkMatrixPackageVersion() : Package version inconsistency detected.
TMB was built with Matrix version 1.4.1
Current Matrix version is 1.5.1
Please re-install 'TMB' from source using install.packages('TMB', type = 
'source') or ask CRAN for a binary version of 'TMB' matching CRAN's 'Matrix' 
package
>

This is also causing autopkgtest failures:
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-tmb/26168759/log.gz
--- End Message ---
--- Begin Message ---
Version: 1.9.1-2

Fixed with new upload, thanks!

On Fri, 16 Sep 2022 18:58:38 +0300 Adrian Bunk  wrote:
> Package: r-cran-tmb
> Version: 1.9.1-1
> Severity: serious
> Control: affects -1 r-cran-glmmtmb src:r-cran-glmmtmb
> Control: block 1017626 by -1
> 
> > library(TMB)
> Warning message:
> In checkMatrixPackageVersion() : Package version inconsistency detected.
> TMB was built with Matrix version 1.4.1
> Current Matrix version is 1.5.1
> Please re-install 'TMB' from source using install.packages('TMB', type = 
> 'source') or ask CRAN for a binary version of 'TMB' matching CRAN's 'Matrix' 
> package
> >
> 
> This is also causing autopkgtest failures:
> https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-tmb/26168759/log.gz
> 
> 

-- 
Best,
Nilesh


signature.asc
Description: PGP signature
--- End Message ---

Processed: Bug#1017944 marked as pending in grub2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1017944 [grub-xen-host] grub-xen-host: 2.06-3 crashes PV guests in early 
boot
Added tag(s) pending.

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

Bug#1017944: marked as pending in grub2

[Steve McIntyre]

Control: tag -1 pending

Hello,

Bug #1017944 in grub2 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/grub-team/grub/-/commit/aeac09767fd915304102f72d2deb21848fdd8bea


Don't strip Xen binaries so they work again.

Closes: #1017944. Thanks to Valentin Kleibel for the patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1017944

Bug#1019981: subversion: "svn propedit" loses changes in case of a network failure / remote attack

[Vincent Lefevre]

Package: subversion
Version: 1.14.2-3+b1
Severity: critical
Tags: security upstream
Justification: causes serious data loss
X-Debbugs-Cc: Debian Security Team 
Forwarded: https://lists.apache.org/thread/54hk6wbqsjnyl3h6p88tno2gpmgr4otd

(The "critical" severity is in part because the data loss was
triggered by a remote attack, though the data loss may occur
with any kind of network failure.)

I wanted to edit a log message with

  svn pe --revprop svn:log -r 151946

(not just a minor change, I was replacing text by a much longer text),
but got an immediate error from SSH after quitting the editor:

kex_exchange_identification: read: Connection reset by peer
Connection reset by 155.133.131.76 port 22
svn: E170013: Unable to connect to a repository at URL 'svn+ssh://mysvn'
svn: E210002: To better debug SSH connection problems, remove the -q option 
from 'ssh' in the [tunnels] section of your Subversion configuration file.
svn: E210002: Network connection closed unexpectedly

Subversion apparently does not keep a copy of the text (contrary to
the case of a commit, which leaves a svn-commit.tmp file), so the
whole new text was lost!!!

I noticed a bit later that the cause of the failure was a remote attack
from a single IP, which lead to "beginning MaxStartups throttling" by
sshd. There is protection by fail2ban on my server, but it takes a few
seconds to react. This is quite a short time, but this was sufficient
to make a SSH failure on my side and lose data.

(There are a bit more details in my upstream bug report, see Forwarded.)

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
merged-usr: no
Architecture: amd64 (x86_64)

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

Versions of packages subversion depends on:
ii  libapr1  1.7.0-8
ii  libaprutil1  1.6.1-5+b2
ii  libc62.34-8
ii  libsvn1  1.14.2-3+b1

subversion recommends no packages.

Versions of packages subversion suggests:
pn  db5.3-util  
pn  libapache2-mod-svn  
ii  patch   2.7.6-7
ii  subversion-tools1.14.2-3+b1

-- no debconf information

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

Processed: mixed bugnumber with ruby bug

[Debian Bug Tracking System]

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

> fixed 1002548 2.0-2
Bug #1002548 {Done: Thorsten Alteholz } [libfli2,indi-fli] 
libfli2,indi-fli: both ship /lib/udev/rules.d/99-fli.rules
There is no source info for the package 'indi-fli' at version '2.0-2' with 
architecture ''
Marked as fixed in versions libfli/2.0-2.
>
End of message, stopping processing here.

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

Bug#1013043: marked as done (stressapptest: ftbfs with GCC-12)

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2022 23:19:26 +
with message-id 
and subject line Bug#1013043: fixed in stressapptest 1.0.6-2.1
has caused the Debian Bug report #1013043,
regarding stressapptest: ftbfs with GCC-12
to be marked as done.

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

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


-- 
1013043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013043
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:stressapptest
Version: 1.0.6-2
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-12

[This bug is targeted to the upcoming bookworm release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. The
severity of this report will be raised before the bookworm release.

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/stressapptest_1.0.6-2_unstable_gcc12.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating src/stressapptest_config.h
config.status: executing depfiles commands
   dh_auto_build
dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 9 
in use)
make -j1
make[1]: Entering directory '/<>'
Making all in src
make[2]: Entering directory '/<>/src'
make  all-am
make[3]: Entering directory '/<>/src'
g++ -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DCHECKOPTS -Wreturn-type -Wunused -Wuninitialized 
-Wall -Wno-psabi -O3 -funroll-all-loops  -funroll-loops -DNDEBUG -c -o main.o 
main.cc
g++ -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DCHECKOPTS -Wreturn-type -Wunused -Wuninitialized 
-Wall -Wno-psabi -O3 -funroll-all-loops  -funroll-loops -DNDEBUG -c -o os.o 
os.cc
os.cc: In member function ‘virtual bool OsLayer::AllocateTestMem(int64, 
uint64)’:
os.cc:509:36: warning: passing NULL to non-pointer argument 3 of ‘void* 
shmat(int, const void*, int)’ [-Wconversion-null]
  509 |   shmaddr = shmat(shmid, NULL, NULL);
  |^~~~
In file included from os.cc:36:
/usr/include/x86_64-linux-gnu/sys/shm.h:55:61: note:   declared here
   55 | extern void *shmat (int __shmid, const void *__shmaddr, int __shmflg)
  | ^~~~
os.cc:566:38: warning: passing NULL to non-pointer argument 6 of ‘void* 
mmap64(void*, size_t, int, int, int, __off64_t)’ [-Wconversion-null]
  566 |  shm_object, NULL);
  |  ^~~~
In file included from os.cc:30:
/usr/include/x86_64-linux-gnu/sys/mman.h:71:55: note:   declared here
   71 |  int __flags, int __fd, __off64_t __offset) __THROW;
  | ~~^~~~
os.cc: In member function ‘virtual PCIDevices OsLayer::GetPCIDevices()’:
os.cc:888:19: warning: ‘int readdir_r(DIR*, dirent*, dirent**)’ is deprecated 
[-Wdeprecated-declarations]
  888 |   while (readdir_r(dir, buf, ) == 0 && entry) {
  |  ~^~
In file included from os.h:19,
 from os.cc:21:
/usr/include/dirent.h:183:12: note: declared here
  183 | extern int readdir_r (DIR *__restrict __dirp,
  |^
os.cc:899:11: warning: ‘void free(void*)’ called on pointer returned 

Bug#1016927: marked as done (gtk4: Ctrl+Shift shortcuts executed with Ctrl only (X11))

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2022 22:49:55 +
with message-id 
and subject line Bug#1016927: fixed in gtk4 4.8.1+ds-1
has caused the Debian Bug report #1016927,
regarding gtk4: Ctrl+Shift shortcuts executed with Ctrl only (X11)
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.)


-- 
1016927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016927
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-console
Version: 43~beta-1
Severity: important
X-Debbugs-Cc: hackedbell...@gmail.com

After upgrading to the current gnome-console version in Debian Sid (43~beta-1),
all shortcuts are being executed even without pressing shift.

For example, ctrl+c is executing a copy (together with a SIGINT) just as if I
pressed ctrl+shift+c
ctrl+v is pasting without requiring shift being hold
ctrl+w is closing the current tab
etc

I reported this upstream (https://gitlab.gnome.org/GNOME/console/-/issues/176)
but the maintainers there said that could not reproduce this and thus it should
probably be an issue in Debian itself.


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

Kernel: Linux 5.18.0-3-amd64 (SMP w/6 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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-console depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-3
ii  gsettings-desktop-schemas42.0-1
ii  libadwaita-1-0   1.2~beta-1
ii  libc62.34-3
ii  libglib2.0-0 2.72.3-1+b1
ii  libgtk-4-1   4.6.6+ds-2
ii  libgtop-2.0-11   2.40.0-2
ii  libpango-1.0-0   1.50.7+ds-1
ii  libvte-2.91-gtk4-0   0.69.92-1

gnome-console recommends no packages.

gnome-console suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gtk4
Source-Version: 4.8.1+ds-1
Done: Simon McVittie 

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated gtk4 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 17 Sep 2022 22:23:08 +0100
Source: gtk4
Architecture: source
Version: 4.8.1+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 1016927
Changes:
 gtk4 (4.8.1+ds-1) unstable; urgency=medium
 .
   * New upstream release
   * debian/libgtk-4-1.symbols.in: Add a new symbol
   * d/control.in: Replace transitional libfontconfig1-dev with
 libfontconfig-dev
   * d/missing-sources: Update for upstream updates to Compose data
   * d/p/gdkevents-Don-t-ignore-modifiers-that-are-not-currently-a.patch:
 Add proposed patch to fix keyboard shortcuts with X11 backend
 (Closes: #1016927)
   * d/p/build-Use-more-conservative-GResource-embedding-on-non-x8.patch:
 Update patch for GResource embedding based on upstream feedback
Checksums-Sha1:
 4fc34fa9ed9b5663ed85c5d0669493004f878fcb 5536 gtk4_4.8.1+ds-1.dsc
 aa8767a20ff9f4f92946b4164901d77fce724fd9 12329152 gtk4_4.8.1+ds.orig.tar.xz
 d7adb5cabb027f68033e918045dd14cbdf9b2322 2960280 gtk4_4.8.1+ds-1.debian.tar.xz
 87a068b21915162ca4251307732636d4ff228bf6 24649 gtk4_4.8.1+ds-1_source.buildinfo
Checksums-Sha256:
 4b31b13c6d493e4981ab605dfe66c56ce5b9e7a25b7392cd2e1161ce4ba2b112 5536 
gtk4_4.8.1+ds-1.dsc
 f5fd6f54f35ad59bc480c090dce7d9abaf40eb1e61bc99c9ce3776215f853918 12329152 
gtk4_4.8.1+ds.orig.tar.xz
 e644d78b0de3da9bd5fbf47db7648c02cdd3548ca8c4f6fad9e8dbeed4b9aba5 2960280 

Bug#1016927: marked as pending in gtk4

[Simon McVittie]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/gnome-team/gtk4/-/commit/2139a8c4eb0eadf4ce527cb6936a0d763970ad2e


Add proposed patch to fix keyboard shortcuts with X11 backend

Closes: #1016927


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1016927

Processed: Bug#1016927 marked as pending in gtk4

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1016927 [src:gtk4] gtk4: Ctrl+Shift shortcuts executed with Ctrl only (X11)
Added tag(s) pending.

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

Bug#1002779: cdbs: diff for NMU version 0.4.163+nmu1

[Paul Gevers]

Hi

On 17-09-2022 22:29, Paul Gevers wrote:

I've prepared an NMU for cdbs (versioned as 0.4.163+nmu1) and I'll
shortly upload it to DELAYED/14. Please feel free to tell me if I
should delay it longer.


Maybe I should have noted somewhere that the reason that the test fails 
is that debhelper compat 5 is no longer supported so it's a bad default 
for cdbs.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1018773: marked as done (libgnuradio-funcube3.10.0: Missing Breaks and Replaces headers: trying to overwrite '/usr/lib/x86_64-linux-gnu/libgnuradio-funcube.so.3.10.0.0', which is also in package l

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2022 20:45:00 +
with message-id 
and subject line Bug#1018773: fixed in gr-funcube 3.10.0~rc3-1
has caused the Debian Bug report #1018773,
regarding libgnuradio-funcube3.10.0: Missing Breaks and Replaces headers: 
trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libgnuradio-funcube.so.3.10.0.0', which is also in 
package libgnuradio-funcube1.0.0 3.10.0~rc2-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.)


-- 
1018773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018773
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gr-funcube
Severity: serious
Version: 3.10.0~rc2-3

Hi,

libgnuradio-funcube3.10.0 fails to install as follows due to missing
Breaks and Replaces headers against libgnuradio-funcube1.0.0:

Preparing to unpack .../libgnuradio-funcube3.10.0_3.10.0~rc2-3_amd64.deb ...
Unpacking libgnuradio-funcube3.10.0 (3.10.0~rc2-3) ...
dpkg: error processing archive 
/var/cache/apt/archives/libgnuradio-funcube3.10.0_3.10.0~rc2-3_amd64.deb 
(--unpack):
 trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libgnuradio-funcube.so.3.10.0.0', which is also in 
package libgnuradio-funcube1.0.0 3.10.0~rc2-1
Errors were encountered while processing:
 /var/cache/apt/archives/libgnuradio-funcube3.10.0_3.10.0~rc2-3_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

-- System Information:
Debian Release: bookworm/sid
[Bug report written on a different system than the issue showed up.]
--- End Message ---
--- Begin Message ---
Source: gr-funcube
Source-Version: 3.10.0~rc3-1
Done: A. Maitland Bottoms 

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

Debian distribution maintenance software
pp.
A. Maitland Bottoms  (supplier of updated gr-funcube 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 17 Sep 2022 11:18:25 -0400
Source: gr-funcube
Binary: gr-funcube libgnuradio-funcube3.10.0 libgnuradio-funcube3.10.0-dbgsym
Architecture: source amd64
Version: 3.10.0~rc3-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Hamradio Maintainers 
Changed-By: A. Maitland Bottoms 
Description:
 gr-funcube - Funcube Dongle controller for GNU Radio
 libgnuradio-funcube3.10.0 - Funcube Dongle controller for GNU Radio (runtime)
Closes: 1018773
Changes:
 gr-funcube (3.10.0~rc3-1) experimental; urgency=medium
 .
   * New upstream release
   * Go ahead and update library name with soversion
 for clean upgrade path (Closes: #1018773).
   * Register gr-funcube HTML documentation with doc-base
   * patch to ensure CMake library helpers get installed with gnuradio
   * update Standards-Version to 4.6.1
   * upload to experimental for ABI bump
Checksums-Sha1:
 88f3bd52b05925bea985215a541e2441dcd297eb 2478 gr-funcube_3.10.0~rc3-1.dsc
 2a1547687f1a1aa25e0dd7c24859857bc01ea0ca 112595 
gr-funcube_3.10.0~rc3.orig.tar.gz
 8735e1e838c6323d712dc6322c6a20e665f9b338 5172 
gr-funcube_3.10.0~rc3-1.debian.tar.xz
 de90be6f01ade162703bc4a86e385dd34facf4d8 19929 
gr-funcube_3.10.0~rc3-1_amd64.buildinfo
 fadf57c06a34cd2b8b1b7a634dd33b6d81bf49f9 199836 
gr-funcube_3.10.0~rc3-1_amd64.deb
 aab749350171b48109172f7df0f4486c9d0ac37f 1796476 
libgnuradio-funcube3.10.0-dbgsym_3.10.0~rc3-1_amd64.deb
 cddbffe9f13466d1574c7d4a6e2c972ecf3cab13 81876 
libgnuradio-funcube3.10.0_3.10.0~rc3-1_amd64.deb
Checksums-Sha256:
 4580bca2c7ab7d9493039274c1c014609669e9aad45589be57aea9d9b584d587 2478 
gr-funcube_3.10.0~rc3-1.dsc
 0e93f799acdc7dae0627ecb3eaea607565f8a71bfe615b80ef6ca057298593aa 112595 
gr-funcube_3.10.0~rc3.orig.tar.gz
 7049997da8ab2a7ecad02e348188bb311fa2136ce8e4ae9684e3ab20a6a7c769 5172 
gr-funcube_3.10.0~rc3-1.debian.tar.xz
 34cfc4db2f129bf92b73cb92fd80b7551df8ebf06c87d9257d43e3bc825c0080 19929 
gr-funcube_3.10.0~rc3-1_amd64.buildinfo
 abe77532f18b03f6b7e20078166a7b5d6e4bdb157c411d1bfaf57a7389353599 199836 
gr-funcube_3.10.0~rc3-1_amd64.deb
 3687037b3f7a86bcfdee1e75bc184f34aab7b7d5eebe7a904884d0b01db38b93 1796476 
libgnuradio-funcube3.10.0-dbgsym_3.10.0~rc3-1_amd64.deb
 

Bug#1002779: cdbs: diff for NMU version 0.4.163+nmu1

[Paul Gevers]

Control: pending

Dear maintainer,

I've prepared an NMU for cdbs (versioned as 0.4.163+nmu1) and I'll
shortly upload it to DELAYED/14. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru cdbs-0.4.163/debian/changelog cdbs-0.4.163+nmu1/debian/changelog
--- cdbs-0.4.163/debian/changelog   2020-12-27 06:31:25.0 +0100
+++ cdbs-0.4.163+nmu1/debian/changelog  2022-09-17 22:20:04.0 +0200
@@ -1,3 +1,11 @@
+cdbs (0.4.163+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Don't fail the build on the test; instead show the log (Closes: 
#1002779)

+  * Drop !nocheck Build-Depends-Indep on pypy-dev (Closes: #1019975)
+
+ -- Paul Gevers   Sat, 17 Sep 2022 22:20:04 +0200
+
 cdbs (0.4.163) unstable; urgency=medium

   * remove myself as uploader
diff -Nru cdbs-0.4.163/debian/control cdbs-0.4.163+nmu1/debian/control
--- cdbs-0.4.163/debian/control 2020-12-27 06:30:38.0 +0100
+++ cdbs-0.4.163+nmu1/debian/control2022-09-17 22:20:04.0 +0200
@@ -7,7 +7,6 @@
  autoconf,
  fakeroot ,
  python3-all-dev ,
- pypy-dev ,
  dh-python ,
  ant ,
  default-jdk-headless  | default-jdk ,
diff -Nru cdbs-0.4.163/debian/rules cdbs-0.4.163+nmu1/debian/rules
--- cdbs-0.4.163/debian/rules   2019-02-27 12:24:43.0 +0100
+++ cdbs-0.4.163+nmu1/debian/rules  2022-09-17 22:20:04.0 +0200
@@ -25,7 +25,7 @@
 # emit testsuite errors, and don't fail on experimental builds
 DEB_SUITE_EXP = $(filter experimental% UNRELEASED,$(DEB_SUITE))
 DEB_MAKE_CHECK_TARGET = check \
- || { cat test/test-suite.log; $(if $(DEB_SUITE_EXP),,false;) }
+ || { cat tests/testsuite.log; }

 # Unset these variables so config.guess/config.sub in the test suite are
 # not replaced (because the test suite is supposed to test the replacing




OpenPGP_signature
Description: OpenPGP digital signature

Processed: asn1crypto: pypy removal: please drop pypy-asn1crypto and stop Build Depending on pypy related packages

[Debian Bug Tracking System]

Processing control commands:

> block 1011926 by -1
Bug #1011926 [pypy] pypy shouldn't be shipped in bookworm
1011926 was blocked by: 932820 983470 937510 938168 1019975 1018738
1011926 was not blocking any bugs.
Added blocking bug(s) of 1011926: 1019976

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

Bug#1019976: asn1crypto: pypy removal: please drop pypy-asn1crypto and stop Build Depending on pypy related packages

[Paul Gevers]

Source: asn1crypto
Version: 1.5.1-1
Severity: serious
Control: block 1011926 by -1

Dear maintainer(s),

We're trying to remove the last remnants of python2 from bookworm. One
of the involved source packages is pypy. Your package has a
Build-Depends on pypy and some related packages. I assume because this
source buils pypy-asn1crypto. I suggest to drop that latter package in order to 
drop the Build-Depends related to pypy.

Paul

Processed: cdbs: pypy removal; please drop Build-Dependency on pypy-dev

[Debian Bug Tracking System]

Processing control commands:

> block 1011926 by -1
Bug #1011926 [pypy] pypy shouldn't be shipped in bookworm
1011926 was blocked by: 1018738 938168 937510 983470 932820
1011926 was not blocking any bugs.
Added blocking bug(s) of 1011926: 1019975

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

Bug#1019975: cdbs: pypy removal; please drop Build-Dependency on pypy-dev

[Paul Gevers]

Source: cdbs
Version: 0.4.163
Severity: serious
Control: block 1011926 by -1

Dear maintainer,

We're trying to remove the last remnants of python2 from bookworm. One
of the involved source packages is pypy. Your package has a (nocheck
build-profiled) Build-Depends on pyp-dev. Can you please drop that?

Paul

Bug#1019865: Debian Bug report logs - #1019865

[Andy Mann]

Package: Evolution
*Hangs and goes to 100% CPU usage on compose*

I confirm this bug. I too am running bookworm, with Evolution 3.45.3-2, and
have exactly the same issue when trying to compose with new>mail message.
This started happening a couple of days ago (15 Sept 2022). I apt update
daily. (I've had to use a web browser to send this email.)

I can confirm this also happens from the command line with evolution mailto:
- CPU goes to 100% and compose does not start. There are no command line
errors - I have to terminate with CTRL-C.

Regards,

Andy, Birmingham, UK

Bug#1019972: gnuradio: FTBFS on mips*, ppc64el, s390x

[Sebastian Ramacher]

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

https://buildd.debian.org/status/fetch.php?pkg=gnuradio=mips64el=3.10.4.0-1=1663413658=0

-- Python checking for Thrift - found
CMake Error at 
/usr/share/cmake-3.24/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
  Could NOT find THRIFT (missing: THRIFT_LIBRARIES THRIFT_INCLUDE_DIRS
  THRIFT_FOUND) (Required is at least version "0.13")
Call Stack (most recent call first):
  /usr/share/cmake-3.24/Modules/FindPackageHandleStandardArgs.cmake:594 
(_FPHSA_FAILURE_MESSAGE)
  cmake/Modules/FindTHRIFT.cmake:89 (find_package_handle_standard_args)
  gnuradio-runtime/CMakeLists.txt:100 (find_package)


-- Configuring incomplete, errors occurred!

Cheers
-- 
Sebastian Ramacher

Bug#1019953: marked as done (flamerobin: FTBFS on arm, i386, mips)

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2022 15:33:46 +
with message-id 
and subject line Bug#1019953: fixed in flamerobin 0.9.3.12-2
has caused the Debian Bug report #1019953,
regarding flamerobin: FTBFS on arm, i386, mips
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.)


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

flamerobin 0.9.3.12-1 FTBFS on serveral arches (arm*, i386, mips*).

Relevant log snippets:

cd /<>/obj-aarch64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<> 
/<>/obj-aarch64-linux-gnu /<>/obj-aarch64-linux-gnu 
/<>/obj-aarch64-linux-gnu/CMakeFiles/IBPP.dir/DependInfo.cmake 
--color=
make[3]: Leaving directory '/<>/obj-aarch64-linux-gnu'
make  -f CMakeFiles/IBPP.dir/build.make CMakeFiles/IBPP.dir/build
make[3]: Entering directory '/<>/obj-aarch64-linux-gnu'
[  0%] Building CXX object CMakeFiles/IBPP.dir/src/ibpp/_dpb.cpp.o
[  1%] Building CXX object CMakeFiles/IBPP.dir/src/ibpp/_ibpp.cpp.o
/usr/bin/c++ -DFR_INSTALL_PREFIX=\"/usr\" -DIBPP_LINUX -DWXUSINGDLL 
-D_FILE_OFFSET_BITS=64 -D__WXGTK__ -I/<>/res 
-I/<>/src/ibpp -I/<>/src -isystem 
/usr/lib/aarch64-linux-gnu/wx/include/gtk3-unicode-3.2 -isystem 
/usr/include/wx-3.2 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -pthread -std=gnu++14 -MD -MT 
CMakeFiles/IBPP.dir/src/ibpp/_ibpp.cpp.o -MF 
CMakeFiles/IBPP.dir/src/ibpp/_ibpp.cpp.o.d -o 
CMakeFiles/IBPP.dir/src/ibpp/_ibpp.cpp.o -c /<>/src/ibpp/_ibpp.cpp
[  2%] Building CXX object CMakeFiles/IBPP.dir/src/ibpp/_ibs.cpp.o
[  3%] Building CXX object CMakeFiles/IBPP.dir/src/ibpp/_rb.cpp.o
/usr/bin/c++ -DFR_INSTALL_PREFIX=\"/usr\" -DIBPP_LINUX -DWXUSINGDLL 
-D_FILE_OFFSET_BITS=64 -D__WXGTK__ -I/<>/res 
-I/<>/src/ibpp -I/<>/src -isystem 
/usr/lib/aarch64-linux-gnu/wx/include/gtk3-unicode-3.2 -isystem 
/usr/include/wx-3.2 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -pthread -std=gnu++14 -MD -MT 
CMakeFiles/IBPP.dir/src/ibpp/_rb.cpp.o -MF 
CMakeFiles/IBPP.dir/src/ibpp/_rb.cpp.o.d -o 
CMakeFiles/IBPP.dir/src/ibpp/_rb.cpp.o -c /<>/src/ibpp/_rb.cpp
/usr/bin/c++ -DFR_INSTALL_PREFIX=\"/usr\" -DIBPP_LINUX -DWXUSINGDLL 
-D_FILE_OFFSET_BITS=64 -D__WXGTK__ -I/<>/res 
-I/<>/src/ibpp -I/<>/src -isystem 
/usr/lib/aarch64-linux-gnu/wx/include/gtk3-unicode-3.2 -isystem 
/usr/include/wx-3.2 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -pthread -std=gnu++14 -MD -MT 
CMakeFiles/IBPP.dir/src/ibpp/_dpb.cpp.o -MF 
CMakeFiles/IBPP.dir/src/ibpp/_dpb.cpp.o.d -o 
CMakeFiles/IBPP.dir/src/ibpp/_dpb.cpp.o -c /<>/src/ibpp/_dpb.cpp
/usr/bin/c++ -DFR_INSTALL_PREFIX=\"/usr\" -DIBPP_LINUX -DWXUSINGDLL 
-D_FILE_OFFSET_BITS=64 -D__WXGTK__ -I/<>/res 
-I/<>/src/ibpp -I/<>/src -isystem 
/usr/lib/aarch64-linux-gnu/wx/include/gtk3-unicode-3.2 -isystem 
/usr/include/wx-3.2 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -pthread -std=gnu++14 -MD -MT 
CMakeFiles/IBPP.dir/src/ibpp/_ibs.cpp.o -MF 
CMakeFiles/IBPP.dir/src/ibpp/_ibs.cpp.o.d -o 
CMakeFiles/IBPP.dir/src/ibpp/_ibs.cpp.o -c /<>/src/ibpp/_ibs.cpp
In file included from /<>/src/ibpp/ibpp.h:71,
 from /<>/src/ibpp/_ibpp.h:23,
 from /<>/src/ibpp/_rb.cpp:26:
/usr/include/c++/12/decimal/decimal:39:2: error: #error This file requires 
compiler and library support for ISO/IEC TR 24733 that is currently not 
available.
   39 | #error This file requires compiler and library support for ISO/IEC TR 
24733 \
  |  ^
/usr/include/c++/12/decimal/decimal:233:5: error: decimal floating-point not 
supported for this target
  233 | decimal32() : __val(0.e-101DF) {}
  | ^
/usr/include/c++/12/decimal/decimal:319:5: error: decimal floating-point not 
supported for this target
  319 | decimal64() : __val(0.e-398dd) {}
  | ^
/usr/include/c++/12/decimal/decimal:405:5: error: decimal floating-point not 
supported for this target
  405 | decimal128(): __val(0.e-6176DL) {}
  | ^~
In file included from /usr/include/c++/12/decimal/decimal:492:

Bug#1012124: pipenv: change in collections with python 3.10

[Jochen Becker]

Package: pipenv
Version: 11.9.0-1.1
Followup-For: Bug #1012124
X-Debbugs-Cc: deb...@beckerjochen.de

Dear Maintainer,

python 3.10 has a change in the import for MutableMapping

till 3.9 it is "from collections import MutableMapping"
since 3.10 is "from collections.abc import MutableMapping"

Greatings
Jochen


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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


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

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

Versions of packages pipenv depends on:
ii  python3   3.10.6-1
ii  python3-certifi   2022.6.15-2
ii  python3-pip   22.2+dfsg-1
ii  python3-pkg-resources 59.6.0-1.2
ii  python3-virtualenv20.16.3+ds-1
ii  python3-virtualenv-clone  0.3.0-2

pipenv recommends no packages.

pipenv suggests no packages.

-- no debconf information

Bug#1015309: marked as done (ruby-bson: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: actual = YAML.load(regexp.to_yaml))

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2022 13:19:58 +
with message-id 
and subject line Bug#1015309: fixed in ruby-bson 4.15.0-1
has caused the Debian Bug report #1015309,
regarding ruby-bson: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: actual 
= YAML.load(regexp.to_yaml)
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.)


-- 
1015309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015309
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-bson
Version: 4.10.0-2+rebuild1658137615
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1

Hi,

We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-bson with ruby3.1 enabled, the build failed.

Relevant part of the build log (hopefully):
>  Failure/Error: actual = YAML.load(regexp.to_yaml)
>  
>  Psych::DisallowedClass:
>Tried to load unspecified class: BSON::Regexp::Raw
>  # ./spec/bson/raw_spec.rb:588:in `block (3 levels) in '
> 
> Finished in 4.66 seconds (files took 2.66 seconds to load)
> 6802 examples, 5 failures, 8 pending
> 
> Failed examples:
> 
> rspec './spec/bson/document_spec.rb[1:19:3:1]' # BSON::Document#each when the 
> document has been serialized iterates over each of the keys
> rspec './spec/bson/document_spec.rb[1:19:3:2]' # BSON::Document#each when the 
> document has been serialized iterates over each of the vals
> rspec './spec/bson/document_spec.rb[1:20:3:1]' # BSON::Document#each_pair 
> when the document has been serialized iterates over each of the keys
> rspec './spec/bson/document_spec.rb[1:20:3:2]' # BSON::Document#each_pair 
> when the document has been serialized iterates over each of the vals
> rspec ./spec/bson/raw_spec.rb:587 # BSON::Regexp::Raw yaml loading round-trips
> 
> /usr/bin/ruby3.1 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.1" failed: 


The full build log is available from:
https://people.debian.org/~terceiro/ruby3.1/ruby-bson_4.10.0-2+rebuild1658137615_amd64.log

To reproduce this, you need to install ruby-all-dev >= 1:3.0+2 (in 
experimental).
If you fail to reproduce, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

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 marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-bson
Source-Version: 4.15.0-1
Done: Antonio Terceiro 

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

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated ruby-bson package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 17 Sep 2022 09:47:53 -0300
Source: ruby-bson
Architecture: source
Version: 4.15.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Antonio Terceiro 
Closes: 1015309
Changes:
 ruby-bson (4.15.0-1) unstable; urgency=medium
 .
   * Team upload
 .
   [ Debian Janitor ]
   * Update standards version to 4.5.1, no changes needed.
 .
   [ Antonio Terceiro ]
   * New upstream version 4.15.0
 - Tests fine against ruby3.1 (Closes: #1015309)
   * Bump Standards-Version to 4.6.1; no changes needed
   * Drop patch, already applied upstream
   * Copy external file needed to run the test suite
Checksums-Sha1:
 8baf3ab1b844ed54bc758c9b135fa69c30682066 2138 ruby-bson_4.15.0-1.dsc
 b9136029b5359083f0e4ff26354649af451d05bd 169374 ruby-bson_4.15.0.orig.tar.gz
 935c3931b26aee7d20276586a70b0f7790775801 

Processed: Re: Bug#1017018: Removal notice: obsolete

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #1017018 [src:haskell-bytestring-handle] Removal notice: obsolete
Bug 1017018 cloned as bug 1019964
> reassign -2 ftp.debian.org
Bug #1019964 [src:haskell-bytestring-handle] Removal notice: obsolete
Bug reassigned from package 'src:haskell-bytestring-handle' to 'ftp.debian.org'.
No longer marked as found in versions haskell-bytestring-handle/0.1.0.6-5.
Ignoring request to alter fixed versions of bug #1019964 to the same values 
previously set
> retitle -2 RM: haskell-bytestring-handle -- RoQA; unmaintained upstream, no 
> reverse dependencies
Bug #1019964 [ftp.debian.org] Removal notice: obsolete
Changed Bug title to 'RM: haskell-bytestring-handle -- RoQA; unmaintained 
upstream, no reverse dependencies' from 'Removal notice: obsolete'.
> severity -2 normal
Bug #1019964 [ftp.debian.org] RM: haskell-bytestring-handle -- RoQA; 
unmaintained upstream, no reverse dependencies
Severity set to 'normal' from 'serious'
> tags -1 sid bookworm
Bug #1017018 [src:haskell-bytestring-handle] Removal notice: obsolete
Added tag(s) bookworm and sid.

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

Bug#1017018: Removal notice: obsolete

[Sebastian Ramacher]

Control: clone -1 -2
Control: reassign -2 ftp.debian.org
Control: retitle -2 RM: haskell-bytestring-handle -- RoQA; unmaintained 
upstream, no reverse dependencies
Control: severity -2 normal
Control: tags -1 sid bookworm

On 2022-08-11 16:39:34 +0300, Ilias Tsitsimpis wrote:
> Source: haskell-bytestring-handle
> Version: 0.1.0.6-5
> Severity: serious
> 
> I intend to remove this package:
> 
>   * It has no rev dependencies
>   * The current version FTBFS
>   * Seems unmaintained; Last upload more than 5 years ago
>   * It's not part of the latest Stackage LTS
> 
> If you believe we should keep this package in Debian, please close this
> bug report.

So let's get this removed.

Dear FTP masters, please remove haskell-bytestring-handle from unstable.

Cheers
-- 
Sebastian Ramacher

Bug#1011682: marked as done (ruby-json-jwt: FTBFS: ERROR: Test "ruby3.0" failed: Failure/Error: key.set_key n, e, d)

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2022 11:35:48 +
with message-id 
and subject line Bug#1011682: fixed in ruby-json-jwt 1.14.0-2
has caused the Debian Bug report #1011682,
regarding ruby-json-jwt: FTBFS: ERROR: Test "ruby3.0" failed: Failure/Error: 
key.set_key n, e, d
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.)


-- 
1011682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011682
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-json-jwt
Version: 1.13.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>Failure/Error: key.set_key n, e, d
> 
>OpenSSL::PKey::PKeyError:
>  rsa#set_key= is incompatible with OpenSSL 3.0
># ./lib/json/jwk.rb:106:in `set_key'
># ./lib/json/jwk.rb:106:in `to_rsa_key'
># ./lib/json/jwk.rb:43:in `to_key'
># ./lib/json/jose.rb:27:in `with_jwk_support'
># ./lib/json/jws.rb:100:in `sign'
># ./lib/json/jws.rb:17:in `sign!'
># ./lib/json/jwt.rb:35:in `sign'
># ./spec/json/jwt_spec.rb:130:in `block (4 levels) in '
> 
> Finished in 0.7193 seconds (files took 0.45001 seconds to load)
> 380 examples, 117 failures, 6 pending
> 
> Failed examples:
> 
> rspec ./spec/interop/with_jsrsasign_spec.rb:41 # interop with jsrsasign JWS 
> verify should succeed
> rspec ./spec/json/jwk_spec.rb:105 # JSON::JWK when RSA public key given 
> #to_key 
> rspec ./spec/json/jwk_spec.rb:139 # JSON::JWK when EC public key given 
> unknown curve 
> rspec ./spec/json/jwk_spec.rb:160 # JSON::JWK when EC public key given 
> #to_key 
> rspec ./spec/json/jwk_spec.rb:187 # JSON::JWK unknown key type 
> rspec './spec/json/jws_spec.rb[1:4:4:2:1:1]' # JSON::JWS#sign! RS256 when 
> JSON::JWK key given behaves like jwt_with_alg 
> rspec './spec/json/jws_spec.rb[1:4:4:2:1:2:1]' # JSON::JWS#sign! RS256 when 
> JSON::JWK key given behaves like jwt_with_alg header 
> rspec './spec/json/jws_spec.rb[1:4:4:2:2:1]' # JSON::JWS#sign! RS256 when 
> JSON::JWK key given behaves like generate_expected_signature 
> rspec './spec/json/jws_spec.rb[1:4:4:2:2:2:1]' # JSON::JWS#sign! RS256 when 
> JSON::JWK key given behaves like generate_expected_signature with blank 
> payload 
> rspec './spec/json/jws_spec.rb[1:4:5:2:1:1]' # JSON::JWS#sign! RS384 when 
> JSON::JWK key given behaves like jwt_with_alg 
> rspec './spec/json/jws_spec.rb[1:4:5:2:1:2:1]' # JSON::JWS#sign! RS384 when 
> JSON::JWK key given behaves like jwt_with_alg header 
> rspec './spec/json/jws_spec.rb[1:4:5:2:2:1]' # JSON::JWS#sign! RS384 when 
> JSON::JWK key given behaves like generate_expected_signature 
> rspec './spec/json/jws_spec.rb[1:4:5:2:2:2:1]' # JSON::JWS#sign! RS384 when 
> JSON::JWK key given behaves like generate_expected_signature with blank 
> payload 
> rspec './spec/json/jws_spec.rb[1:4:6:2:1:1]' # JSON::JWS#sign! RS512 when 
> JSON::JWK key given behaves like jwt_with_alg 
> rspec './spec/json/jws_spec.rb[1:4:6:2:1:2:1]' # JSON::JWS#sign! RS512 when 
> JSON::JWK key given behaves like jwt_with_alg header 
> rspec './spec/json/jws_spec.rb[1:4:6:2:2:1]' # JSON::JWS#sign! RS512 when 
> JSON::JWK key given behaves like generate_expected_signature 
> rspec './spec/json/jws_spec.rb[1:4:6:2:2:2:1]' # JSON::JWS#sign! RS512 when 
> JSON::JWK key given behaves like generate_expected_signature with blank 
> payload 
> rspec './spec/json/jws_spec.rb[1:4:7:1:1:1]' # JSON::JWS#sign! ES256 when 
> OpenSSL::PKey::EC key given behaves like jwt_with_alg 
> rspec './spec/json/jws_spec.rb[1:4:7:1:1:2:1]' # JSON::JWS#sign! ES256 when 
> OpenSSL::PKey::EC key given behaves like jwt_with_alg header 
> rspec './spec/json/jws_spec.rb[1:4:7:1:2:1]' # JSON::JWS#sign! ES256 when 
> OpenSSL::PKey::EC key given behaves like self_verifiable should be 
> self-verifiable
> rspec './spec/json/jws_spec.rb[1:4:7:2:1:1]' # JSON::JWS#sign! ES256 when 
> JSON::JWK key given behaves like jwt_with_alg 
> rspec './spec/json/jws_spec.rb[1:4:7:2:1:2:1]' # JSON::JWS#sign! ES256 when 
> JSON::JWK key given behaves like jwt_with_alg header 
> rspec './spec/json/jws_spec.rb[1:4:7:2:2:1]' # JSON::JWS#sign! ES256 when 
> JSON::JWK key given behaves like self_verifiable should be self-verifiable
> rspec './spec/json/jws_spec.rb[1:4:8:1:1:1]' # JSON::JWS#sign! ES384 when 
> OpenSSL::PKey::EC key given behaves like jwt_with_alg 
> rspec './spec/json/jws_spec.rb[1:4:8:1:1:2:1]' # JSON::JWS#sign! 

Bug#1019962: marked as done (evolution-ews: FTBFS: /<>/src/EWS/evolution/e-ews-comp-editor-extension.c:60:16: error: implicit declaration of function ‘e_comp_editor_get_property_part’; di

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2022 11:03:48 +
with message-id 
and subject line Bug#1019962: fixed in evolution-ews 3.46.0-2
has caused the Debian Bug report #1019962,
regarding evolution-ews: FTBFS: 
/<>/src/EWS/evolution/e-ews-comp-editor-extension.c:60:16: error: 
implicit declaration of function ‘e_comp_editor_get_property_part’; did you 
mean ‘e_comp_editor_page_add_property_part’? 
[-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.)


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

https://buildd.debian.org/status/fetch.php?pkg=evolution-ews=amd64=3.46.0-1=1663387153=0

[ 94%] Building C object 
src/EWS/evolution/CMakeFiles/module-ews-configuration.dir/e-ews-config-lookup.c.o
cd /<>/obj-x86_64-linux-gnu/src/EWS/evolution && /usr/bin/cc 
-DEXCHANGE_EWS_LOCALEDIR=\"/usr/share/locale\" 
-DGDK_VERSION_MAX_ALLOWED=GDK_VERSION_3_10 
-DGDK_VERSION_MIN_REQUIRED=GDK_VERSION_3_10 
-DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_68 
-DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_68 
-DG_LOG_DOMAIN=\"module-ews-configuration\" 
-DSOUP_VERSION_MAX_ALLOWED=SOUP_VERSION_3_0 
-DSOUP_VERSION_MIN_REQUIRED=SOUP_VERSION_3_0 -Dmodule_ews_configuration_EXPORTS 
-I/<>/obj-x86_64-linux-gnu -I/<> 
-I/usr/include/evolution-data-server -I/usr/include/libsecret-1 
-I/usr/include/gio-unix-2.0 -I/usr/include/libxml2 -I/usr/include/libsoup-3.0 
-I/usr/include/sysprof-4 -I/usr/include/json-glib-1.0 -I/usr/include/libmount 
-I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/evolution 
-I/usr/include/gnome-desktop-3.0 -I/usr/include/webkitgtk-4.1 
-I/usr/include/gtk-3.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 
-I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz 
-I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng16 -I/usr/include/gsettings-desktop-schemas 
-I/<>/obj-x86_64-linux-gnu/src/EWS -I/<>/src/EWS 
-I/<>/obj-x86_64-linux-gnu/src/EWS/common 
-I/<>/src/EWS/common 
-I/<>/obj-x86_64-linux-gnu/src/EWS/camel 
-I/<>/src/EWS/camel -Wnested-externs -Wno-unused-parameter 
-Wno-sign-compare -Wno-missing-field-initializers -Wdeclaration-after-statement 
-Werror-implicit-function-declaration -Wno-missing-include-dirs 
-Wno-deprecated-declarations -fno-strict-aliasing -Wl,--no-undefined 
-Wno-cast-function-type -Wwrite-strings -Wundef -Wredundant-decls 
-Wpointer-arith -Wmissing-noreturn -Wmissing-declarations -Winit-self 
-Wformat-security -Wformat -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -pthread -I/usr/include/evolution-data-server 
-I/usr/include/libsecret-1 -I/usr/include/gio-unix-2.0 -I/usr/include/libxml2 
-I/usr/include/libsoup-3.0 -I/usr/include/sysprof-4 
-I/usr/include/json-glib-1.0 -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/evolution -I/usr/include/gnome-desktop-3.0 
-I/usr/include/webkitgtk-4.1 -I/usr/include/gtk-3.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 
-I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz 
-I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng16 -I/usr/include/x86_64-linux-gnu 
-I/usr/include/gsettings-desktop-schemas -MD -MT 
src/EWS/evolution/CMakeFiles/module-ews-configuration.dir/e-ews-config-lookup.c.o
 -MF CMakeFiles/module-ews-configuration.dir/e-ews-config-lookup.c.o.d -o 
CMakeFiles/module-ews-configuration.dir/e-ews-config-lookup.c.o -c 
/<>/src/EWS/evolution/e-ews-config-lookup.c
/<>/src/EWS/evolution/e-ews-comp-editor-extension.c: In function 
‘e_ews_comp_editor_extension_target_client_changed_cb’:
/<>/src/EWS/evolution/e-ews-comp-editor-extension.c:60:16: error: 
implicit declaration of function ‘e_comp_editor_get_property_part’; did you 
mean ‘e_comp_editor_page_add_property_part’? 
[-Werror=implicit-function-declaration]
   60 | 

Processed: Re: Bug#1017016: Removal notice: obsolete

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #1017016 [src:haskell-bitarray] Removal notice: obsolete
Bug 1017016 cloned as bug 1019963
> reassign -2 ftp.debian.org
Bug #1019963 [src:haskell-bitarray] Removal notice: obsolete
Bug reassigned from package 'src:haskell-bitarray' to 'ftp.debian.org'.
No longer marked as found in versions haskell-bitarray/0.0.1.1-6.
Ignoring request to alter fixed versions of bug #1019963 to the same values 
previously set
> retitle -2 RM: haskell-bitarray -- RoQA; unmaintained, no reverse dependencies
Bug #1019963 [ftp.debian.org] Removal notice: obsolete
Changed Bug title to 'RM: haskell-bitarray -- RoQA; unmaintained, no reverse 
dependencies' from 'Removal notice: obsolete'.
> severity -2 normal
Bug #1019963 [ftp.debian.org] RM: haskell-bitarray -- RoQA; unmaintained, no 
reverse dependencies
Severity set to 'normal' from 'serious'
> tags -1 sid bookworm
Bug #1017016 [src:haskell-bitarray] Removal notice: obsolete
Added tag(s) bookworm and sid.

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

Bug#1017016: Removal notice: obsolete

[Sebastian Ramacher]

Control: clone -1 -2
Control: reassign -2 ftp.debian.org
Control: retitle -2 RM: haskell-bitarray -- RoQA; unmaintained, no reverse 
dependencies
Control: severity -2 normal
Control: tags -1 sid bookworm

On 2022-08-11 16:21:23 +0300, Ilias Tsitsimpis wrote:
> Source: haskell-bitarray
> Version: 0.0.1.1-6
> Severity: serious
> 
> I intend to remove this package:
> 
>   * It has no rev dependencies
>   * Seems unmaintained; Home page doesn't work
>   * Seems unmaintained; Last upload more than 5 years ago
> 
> If you believe we should keep this package in Debian, please close this
> bug report.

So let's get this removed.

Dear FTP masters, please remove haskell-bitarray from unstable.

Cheers
-- 
Sebastian Ramacher

Bug#1019121: marked as done (libpqtypes: flaky autopkgtest on arm64: table "libpq_array" does not exist)

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2022 11:38:42 +0200
with message-id 
and subject line Re: Bug#1019121: libpqtypes: flaky autopkgtest on arm64: table 
"libpq_array" does not exist
has caused the Debian Bug report #1019121,
regarding libpqtypes: flaky autopkgtest on arm64: table "libpq_array" 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.)


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

Source: libpqtypes
Version: 1.5.1-7
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of your package. I noticed 
that it regularly fails on arm64.


Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

Ran 125 tests - 1 failed
*** /tmp/pg_virtualenv.QzsWeE/log/postgresql-14-regress.log (last 100 
lines) ***
2022-09-02 13:57:21.320 CST [7664] LOG:  starting PostgreSQL 14.5 
(Debian 14.5-1) on aarch64-unknown-linux-gnu, compiled by gcc (Debian 
12.1.0-8) 12.1.0, 64-bit
2022-09-02 13:57:21.321 CST [7664] LOG:  listening on IPv6 address 
"::1", port 5433
2022-09-02 13:57:21.321 CST [7664] LOG:  listening on IPv4 address 
"127.0.0.1", port 5433
2022-09-02 13:57:21.321 CST [7664] LOG:  listening on Unix socket 
"/tmp/.s.PGSQL.5433"
2022-09-02 13:57:21.322 CST [7665] LOG:  database system was shut down 
at 2022-09-02 13:57:21 CST
2022-09-02 13:57:21.327 CST [7664] LOG:  database system is ready to 
accept connections
2022-09-02 13:57:23.522 CST [7685] debci@postgres ERROR:  table 
"libpq_array" does not exist
2022-09-02 13:57:23.522 CST [7685] debci@postgres STATEMENT:  DROP TABLE 
libpq_array
2022-09-02 13:57:23.525 CST [7685] debci@postgres ERROR:  type 
"public.complex" does not exist
2022-09-02 13:57:23.525 CST [7685] debci@postgres STATEMENT:  DROP TYPE 
public.complex
2022-09-02 13:57:23.525 CST [7685] debci@postgres ERROR:  type 
"public.simple" does not exist
2022-09-02 13:57:23.525 CST [7685] debci@postgres STATEMENT:  DROP TYPE 
public.simple


https://ci.debian.net/data/autopkgtest/testing/arm64/libp/libpqtypes/25613424/log.gz
https://ci.debian.net/data/autopkgtest/testing/arm64/libp/libpqtypes/24974038/log.gz
https://ci.debian.net/data/autopkgtest/testing/arm64/libp/libpqtypes/24648942/log.gz
https://ci.debian.net/data/autopkgtest/testing/arm64/libp/libpqtypes/24021115/log.gz
https://ci.debian.net/data/autopkgtest/testing/arm64/libp/libpqtypes/23016446/log.gz


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 1.5.1-8

Re: Paul Gevers
> I looked at the results of the autopkgtest of your package. I noticed that
> it regularly fails on arm64.

Hi Paul,

I think I found the problem - it's not flaky, but it was failing when
the system timezone wasn't UTC. Some of the arm64 workers are set to
CDT.

The tests are pinned to run with UTC now, and
https://ci.debian.net/packages/libp/libpqtypes/testing/arm64/
seems happy.

Thanks for the report,
Christoph--- End Message ---

Processed: closing 1017249

[Debian Bug Tracking System]

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

> close 1017249
Bug #1017249 [src:rheolef] rheolef: FTBFS: 
../../include/rheolef/communicator.h:112:25: error: expected initializer before 
‘size’
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1002239: marked as done (google-authenticator: FTBFS: dh_auto_test: error: make -j4 test VERBOSE=1 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2022 11:00:27 +0200
with message-id 
and subject line Re: google-authenticator: FTBFS: dh_auto_test: error: make -j4 
test VERBOSE=1 returned exit code 2
has caused the Debian Bug report #1002239,
regarding google-authenticator: FTBFS: dh_auto_test: error: make -j4 test 
VERBOSE=1 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.)


-- 
1002239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002239
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: google-authenticator
Version: 20191231-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<>'
> FAIL: tests/pam_google_authenticator_unittest
> PASS: tests/base32_test.sh
> =
>google-authenticator 1.08: ./test-suite.log
> =
> 
> # TOTAL: 2
> # PASS:  1
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> .. contents:: :depth: 2
> 
> FAIL: tests/pam_google_authenticator_unittest
> =
> 
> pam_google_authenticator_unittest: 
> tests/pam_google_authenticator_unittest.c:389: main: Assertion 
> `pam_sm_authenticate(NULL, 0, targc, targv) == PAM_SUCCESS' failed.
> Invalid verification code for root
> FAIL tests/pam_google_authenticator_unittest (exit status: 1)
> 
> 
> Testsuite summary for google-authenticator 1.08
> 
> # TOTAL: 2
> # PASS:  1
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> See ./test-suite.log
> Please report to hab...@google.com
> 
> make[4]: *** [Makefile:1361: test-suite.log] Error 1
> make[4]: Leaving directory '/<>'
> make[3]: *** [Makefile:1469: check-TESTS] Error 2
> make[3]: Leaving directory '/<>'
> make[2]: *** [Makefile:1688: check-am] Error 2
> make[2]: Leaving directory '/<>'
> dh_auto_test: error: make -j4 test VERBOSE=1 returned exit code 2


The full build log is available from:
http://qa-logs.debian.net/2021/12/20/google-authenticator_20191231-2_unstable.log

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 marking 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 ---
Hi,

On 05/09/22 at 11:30 +0100, Robie Basak wrote:
> Hi,
> 
> On Tue, Dec 21, 2021 at 05:33:17PM +0100, Lucas Nussbaum wrote:
> > Source: google-authenticator
> > Version: 20191231-2
> > Severity: serious
> > Justification: FTBFS
> > Tags: bookworm sid ftbfs
> > User: lu...@debian.org
> > Usertags: ftbfs-20211220 ftbfs-bookworm
> > 
> > Hi,
> > 
> > During a rebuild of all packages in sid, your package failed to build
> > on amd64.
> 
> I'm not the maintainer but noticed that google-authenticator is being
> held out of testing due to this bug.
> 
> But this package seems to rebuild successfully for me locally, and
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/google-authenticator.html
> seems to concur.
> 
> Can this bug be closed, please?

I confirm that it builds fine now. Closing.

Lucas


signature.asc
Description: PGP signature
--- End Message ---

Bug#1016953: marked as done (intel-media-driver: FTBFS on i386: error: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘uint64_t’)

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2022 08:34:49 +
with message-id 
and subject line Bug#1016953: fixed in intel-media-driver 
22.5.1+dfsg1+really22.4.3-1
has caused the Debian Bug report #1016953,
regarding intel-media-driver: FTBFS on i386: error: format ‘%lu’ expects 
argument of type ‘long unsigned int’, but argument 3 has type ‘uint64_t’
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.)


-- 
1016953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016953
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: intel-media-driver
Version: 22.5.1+dfsg1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

intel-media-driver failed to build on i386, breaking multiarch
co-installation of amd64 and i386 driver libraries.

https://buildd.debian.org/status/fetch.php?pkg=intel-media-driver=i386=22.5.1%2Bdfsg1-1=1659479611=0

/<>/media_softlet/linux/common/os/osservice/mos_utilities_specific.cpp:
 In static member function ‘static MOS_STATUS 
MosUtilitiesSpecificNext::UserFeatureDumpDataToFile(const char*, 
MOS_PUF_KEYLIST)’:
/<>/media_softlet/linux/common/os/osservice/mos_utilities_specific.cpp:1023:44:
 error: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 
3 has type ‘uint64_t’ {aka ‘long long unsigned int’} [-Werror=format=]
 1023 | fprintf(File, "\t\t\t%lu\n",
  |  ~~^
  ||
  |long unsigned int
  |  %llu
 1024 | 
*(uint64_t*)(pKeyTmp->pElem->pValueArray[j].ulValueBuf));
  | 
~~~
  | |
  | uint64_t {aka long long unsigned int}

The solution might be as simple as including  or ,
and using "%" PRIu64 instead of "%lu". I'm testing that now.

smcv
--- End Message ---
--- Begin Message ---
Source: intel-media-driver
Source-Version: 22.5.1+dfsg1+really22.4.3-1
Done: Sebastian Ramacher 

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated 
intel-media-driver package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 17 Sep 2022 10:17:13 +0200
Source: intel-media-driver
Architecture: source
Version: 22.5.1+dfsg1+really22.4.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Sebastian Ramacher 
Closes: 1016953
Changes:
 intel-media-driver (22.5.1+dfsg1+really22.4.3-1) unstable; urgency=medium
 .
   * Revert to upstream version 22.4.3 (Closes: #1016953)
Checksums-Sha1:
 a903d197a7a85492850c90d8dcc3377186cc268b 2463 
intel-media-driver_22.5.1+dfsg1+really22.4.3-1.dsc
 e54bc39354e3e80bbb8be546baa137b9c3f4681f 7595344 
intel-media-driver_22.5.1+dfsg1+really22.4.3.orig.tar.xz
 c75644988c036081c16d4eda957f131a940e3654 7200 
intel-media-driver_22.5.1+dfsg1+really22.4.3-1.debian.tar.xz
Checksums-Sha256:
 f55c339f267e56478834872cfb6bff7dc9dd500a5e03f12f7340f176a4b2e29d 2463 
intel-media-driver_22.5.1+dfsg1+really22.4.3-1.dsc
 3f2ff26b9c3ae37a94f38da9869f4d5f99e2326c7d1793e5fdea9b825a76322b 7595344 
intel-media-driver_22.5.1+dfsg1+really22.4.3.orig.tar.xz
 866a2c4b5ef03b3dfa34156b09a1538d019d10c14eca2a74191af594e66f8ace 7200 
intel-media-driver_22.5.1+dfsg1+really22.4.3-1.debian.tar.xz
Files:
 996667e50190dad7eaf5af772302f6aa 2463 video optional 
intel-media-driver_22.5.1+dfsg1+really22.4.3-1.dsc
 663371c315a88c78d76ababe5354c22b 7595344 video optional 
intel-media-driver_22.5.1+dfsg1+really22.4.3.orig.tar.xz
 04a39d1b4f014cdf93b7d1d89668348f 7200 video optional 
intel-media-driver_22.5.1+dfsg1+really22.4.3-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAmMlhV0ACgkQafL8UW6n

Bug#1019962: evolution-ews: FTBFS: /<>/src/EWS/evolution/e-ews-comp-editor-extension.c:60:16: error: implicit declaration of function ‘e_comp_editor_get_property_part’; did you mean ‘e_co

[Sebastian Ramacher]

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

https://buildd.debian.org/status/fetch.php?pkg=evolution-ews=amd64=3.46.0-1=1663387153=0

[ 94%] Building C object 
src/EWS/evolution/CMakeFiles/module-ews-configuration.dir/e-ews-config-lookup.c.o
cd /<>/obj-x86_64-linux-gnu/src/EWS/evolution && /usr/bin/cc 
-DEXCHANGE_EWS_LOCALEDIR=\"/usr/share/locale\" 
-DGDK_VERSION_MAX_ALLOWED=GDK_VERSION_3_10 
-DGDK_VERSION_MIN_REQUIRED=GDK_VERSION_3_10 
-DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_68 
-DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_68 
-DG_LOG_DOMAIN=\"module-ews-configuration\" 
-DSOUP_VERSION_MAX_ALLOWED=SOUP_VERSION_3_0 
-DSOUP_VERSION_MIN_REQUIRED=SOUP_VERSION_3_0 -Dmodule_ews_configuration_EXPORTS 
-I/<>/obj-x86_64-linux-gnu -I/<> 
-I/usr/include/evolution-data-server -I/usr/include/libsecret-1 
-I/usr/include/gio-unix-2.0 -I/usr/include/libxml2 -I/usr/include/libsoup-3.0 
-I/usr/include/sysprof-4 -I/usr/include/json-glib-1.0 -I/usr/include/libmount 
-I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/evolution 
-I/usr/include/gnome-desktop-3.0 -I/usr/include/webkitgtk-4.1 
-I/usr/include/gtk-3.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 
-I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz 
-I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng16 -I/usr/include/gsettings-desktop-schemas 
-I/<>/obj-x86_64-linux-gnu/src/EWS -I/<>/src/EWS 
-I/<>/obj-x86_64-linux-gnu/src/EWS/common 
-I/<>/src/EWS/common 
-I/<>/obj-x86_64-linux-gnu/src/EWS/camel 
-I/<>/src/EWS/camel -Wnested-externs -Wno-unused-parameter 
-Wno-sign-compare -Wno-missing-field-initializers -Wdeclaration-after-statement 
-Werror-implicit-function-declaration -Wno-missing-include-dirs 
-Wno-deprecated-declarations -fno-strict-aliasing -Wl,--no-undefined 
-Wno-cast-function-type -Wwrite-strings -Wundef -Wredundant-decls 
-Wpointer-arith -Wmissing-noreturn -Wmissing-declarations -Winit-self 
-Wformat-security -Wformat -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -pthread -I/usr/include/evolution-data-server 
-I/usr/include/libsecret-1 -I/usr/include/gio-unix-2.0 -I/usr/include/libxml2 
-I/usr/include/libsoup-3.0 -I/usr/include/sysprof-4 
-I/usr/include/json-glib-1.0 -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/evolution -I/usr/include/gnome-desktop-3.0 
-I/usr/include/webkitgtk-4.1 -I/usr/include/gtk-3.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 
-I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz 
-I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng16 -I/usr/include/x86_64-linux-gnu 
-I/usr/include/gsettings-desktop-schemas -MD -MT 
src/EWS/evolution/CMakeFiles/module-ews-configuration.dir/e-ews-config-lookup.c.o
 -MF CMakeFiles/module-ews-configuration.dir/e-ews-config-lookup.c.o.d -o 
CMakeFiles/module-ews-configuration.dir/e-ews-config-lookup.c.o -c 
/<>/src/EWS/evolution/e-ews-config-lookup.c
/<>/src/EWS/evolution/e-ews-comp-editor-extension.c: In function 
‘e_ews_comp_editor_extension_target_client_changed_cb’:
/<>/src/EWS/evolution/e-ews-comp-editor-extension.c:60:16: error: 
implicit declaration of function ‘e_comp_editor_get_property_part’; did you 
mean ‘e_comp_editor_page_add_property_part’? 
[-Werror=implicit-function-declaration]
   60 | part = e_comp_editor_get_property_part (comp_editor, 
I_CAL_SUMMARY_PROPERTY);
  |^~~
  |e_comp_editor_page_add_property_part
/<>/src/EWS/evolution/e-ews-comp-editor-extension.c:60:16: 
warning: nested extern declaration of ‘e_comp_editor_get_property_part’ 
[-Wnested-externs]
/<>/src/EWS/evolution/e-ews-comp-editor-extension.c:60:14: 
warning: assignment to ‘ECompEditorPropertyPart *’ {aka ‘struct 
_ECompEditorPropertyPart *’} from ‘int’ makes pointer from integer without a 
cast [-Wint-conversion]
   60 | part = e_comp_editor_get_property_part (comp_editor, 
I_CAL_SUMMARY_PROPERTY);
  |  ^
/<>/src/EWS/evolution/e-ews-comp-editor-extension.c:69:14: 
warning: assignment to ‘ECompEditorPropertyPart *’ {aka ‘struct 
_ECompEditorPropertyPart *’} from ‘int’ makes pointer from integer without a 
cast [-Wint-conversion]
   69 | part = e_comp_editor_get_property_part (comp_editor, 
I_CAL_LOCATION_PROPERTY);
  |   

Processed: fixed 1016898 in 2019.2.0~git20220407.d29e24d-8

[Debian Bug Tracking System]

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

> fixed 1016898 2019.2.0~git20220407.d29e24d-8
Bug #1016898 {Done: Aurelien Jarno } [src:dolfin] dolfin 
needs a rebuild against glibc 2.34
Marked as fixed in versions dolfin/2019.2.0~git20220407.d29e24d-8.
> thanks
Stopping processing here.

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

Processed: fixed 1005165 in 1:1.2+3

[Debian Bug Tracking System]

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

> fixed 1005165 1:1.2+3
Bug #1005165 [fwupd-amd64-signed] fwupd-amd64-signed uninstallable for a few 
weeks now
Marked as fixed in versions fwupd-amd64-signed/1:1.2+3.
> thanks
Stopping processing here.

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