Bug#1000932: doxygen: diff for NMU version 1.9.1-2.1
Il 15/07/22 00:23, Sebastian Ramacher ha scritto: On 2022-07-14 16:23:16 +0200, Paolo Greppi wrote: ... ACK, I've canceled the NMU. Please consider that doxygen is a key package and thus effectively keeping llvm-toolchain-11 in testing. A timely fix for this issue would be much appreciated. Cheers Many thanks. I have prepared the new version with a fix for your issue (https://salsa.debian.org/debian/doxygen) and started a "fast" ratt job (https://salsa.debian.org/debian/doxygen/-/wikis/ratt_doxygen_1.9.1-1_amd64%20partial). This will take a few days to compete, so far we're at 22% of the progress and 8% of packages fail on the first pass, but all are probably false positives. If all goes well I should be able to upload by Friday. Paolo
Processed: bug 1015088 is forwarded to https://github.com/golang/go/issues/53852
Processing commands for cont...@bugs.debian.org: > forwarded 1015088 https://github.com/golang/go/issues/53852 Bug #1015088 [src:golang-1.18] icingadb: FTBFS: ../pkg/com/bulker.go:30:16: internal compiler error: assertion failed Changed Bug forwarded-to-address to 'https://github.com/golang/go/issues/53852' from 'https://github.com/golang/go/issues/53916'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1015088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015088 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org:
> reassign 1015111 libgd-dev
Bug #1015111 [src:sagemath] sagemath: FTBFS:
pkgconfig.pkgconfig.PackageNotFoundError: gdlib not found
Bug reassigned from package 'src:sagemath' to 'libgd-dev'.
No longer marked as found in versions sagemath/9.5-4.
Ignoring request to alter fixed versions of bug #1015111 to the same values
previously set
> forcemerge 1014759 1015111
Bug #1014759 {Done: Ondřej Surý } [libgd-dev] libgd-dev:
Missing dependency on libwebp-dev?
Bug #1015111 [libgd-dev] sagemath: FTBFS:
pkgconfig.pkgconfig.PackageNotFoundError: gdlib not found
Marked Bug as done
Added indication that 1015111 affects src:sagemath
Marked as fixed in versions libgd2/2.3.3-6.
Marked as found in versions libgd2/2.3.3-3.
Bug #1014759 {Done: Ondřej Surý } [libgd-dev] libgd-dev:
Missing dependency on libwebp-dev?
Added tag(s) bookworm and sid.
Merged 1014759 1015111
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1014759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014759
1015111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015111
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: reassign 1014633 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 1014633 src:linux 5.19~rc4-1~exp1 Bug #1014633 [linux-headers-5.19.0-rc4-common] linux-headers-5.19.0-rc4-common: file check-local-export does not exist Bug reassigned from package 'linux-headers-5.19.0-rc4-common' to 'src:linux'. No longer marked as found in versions linux/5.19~rc4-1~exp1. Ignoring request to alter fixed versions of bug #1014633 to the same values previously set Bug #1014633 [src:linux] linux-headers-5.19.0-rc4-common: file check-local-export does not exist Marked as found in versions linux/5.19~rc4-1~exp1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1014633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014633 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997509: marked as done (direnv: FTBFS: dh_auto_test: error: make -j1 test returned exit code 2)
Your message dated Sun, 17 Jul 2022 23:34:37 +
with message-id
and subject line Bug#997509: fixed in direnv 2.32.1-1
has caused the Debian Bug report #997509,
regarding direnv: FTBFS: dh_auto_test: error: make -j1 test 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.)
--
997509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997509
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: direnv
Version: 2.25.2-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> shellcheck stdlib.sh
>
> In stdlib.sh line 999:
> source "${rvm_scripts_path}/rvm"
>^---^ SC1091: Not following: ./rvm was not
> specified as input (see shellcheck -x).
>
>
> In stdlib.sh line 1002:
> source "${rvm_path}/scripts/rvm"
>^---^ SC1091: Not following: ./scripts/rvm was
> not specified as input (see shellcheck -x).
>
>
> In stdlib.sh line 1005:
> source "$HOME/.rvm/scripts/rvm"
>^--^ SC1091: Not following: ./.rvm/scripts/rvm
> was not specified as input (see shellcheck -x).
>
>
> In stdlib.sh line 1208:
> source "$direnv_config_dir/direnvrc" >&2
>^---^ SC1091: Not following: ./direnvrc
> was not specified as input (see shellcheck -x).
>
>
> In stdlib.sh line 1211:
> source "$HOME/.direnvrc" >&2
>^---^ SC1091: Not following: ./.direnvrc was not
> specified as input (see shellcheck -x).
>
> For more information:
> https://www.shellcheck.net/wiki/SC1091 -- Not following: ./.direnvrc was
> no...
> make[2]: *** [GNUmakefile:124: test-shellcheck] Error 1
> make[2]: Leaving directory '/<>'
> dh_auto_test: error: make -j1 test returned exit code 2
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/direnv_2.25.2-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 ---
Source: direnv
Source-Version: 2.32.1-1
Done: Punit Agrawal
We believe that the bug you reported is fixed in the latest version of
direnv, 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 997...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Punit Agrawal (supplier of updated direnv 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, 18 Jul 2022 00:09:09 +0100
Source: direnv
Architecture: source
Version: 2.32.1-1
Distribution: unstable
Urgency: medium
Maintainer: Punit Agrawal
Changed-By: Punit Agrawal
Closes: 997509
Changes:
direnv (2.32.1-1) unstable; urgency=medium
.
* debian/watch: Fix the matching regular expression
* Update standards version to 4.6.0
* debian: Update list of manpages to install
* debian/control: Annotate test dependencies with nocheck profile
* debian/control: Bump debhelper-compat to 13
* debian/rules: Migrate to using dh-golang
* New upstream version 2.32.1 (Closes: #997509)
* debian/patches: Refresh patches for new upstream version 2.32.1
* debian: manpages: Drop direnv-toml manpage
* debian/control: Add build dependencies due to devendoring
* debian/rules: Make artifacts available during build
* debian/rules: Re-enable tests
* debian/control: Drop go-md2man dependency
Checksums-Sha1:
b7392da042c3c2297f084c91f6a647337def631c 2101 direnv_2.32.1-1.dsc
415c6028e2ed0c338e39b753393e62bd4395c060 86219 direnv_2.32.1.orig.tar.gz
5946f574717f2327f57662e2918bd4007c4c2a65 4384
Bug#1015081: marked as done (matplotlib: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)
Your message dated Sun, 17 Jul 2022 23:06:00 +
with message-id
and subject line Bug#1015081: fixed in matplotlib 3.5.2-2
has caused the Debian Bug report #1015081,
regarding matplotlib: FTBFS: dpkg-buildpackage: error: dpkg-source -b .
subprocess returned exit status 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.)
--
1015081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015081
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: matplotlib
Version: 3.5.2-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220716 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> py3versions: no X-Python3-Version in control file, using supported versions
> :1: DeprecationWarning: The distutils package is deprecated and
> slated for removal in Python 3.12. Use setuptools or check PEP 632 for
> potential alternatives
> dh_testdir
> dpkg-buildflags: warning: invalid flag in DEB_BUILD_OPTIONS: --no-parallel
> dpkg-buildflags: warning: invalid flag in DEB_BUILD_OPTIONS: --no-parallel
> dpkg-buildflags: warning: invalid flag in DEB_BUILD_OPTIONS: --no-parallel
> dpkg-buildflags: warning: invalid flag in DEB_BUILD_OPTIONS: --no-parallel
> dpkg-buildflags: warning: invalid flag in DEB_BUILD_OPTIONS: --no-parallel
> dpkg-buildflags: warning: invalid flag in DEB_BUILD_OPTIONS: --no-parallel
> dpkg-buildflags: warning: invalid flag in DEB_BUILD_OPTIONS: --no-parallel
> dpkg-buildflags: warning: invalid flag in DEB_BUILD_OPTIONS: --no-parallel
> dpkg-buildflags: warning: invalid flag in DEB_BUILD_OPTIONS: --no-parallel
> dpkg-buildflags: warning: invalid flag in DEB_BUILD_OPTIONS: --no-parallel
> dpkg-buildflags: warning: invalid flag in DEB_BUILD_OPTIONS: --no-parallel
> dh_testroot
> for i in 3.9 3.10; do \
> python$i ./setup.py clean --all; \
> done
> running clean
> 'build/lib.linux-x86_64-3.9' does not exist -- can't clean it
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.9' does not exist -- can't clean it
> running clean
> 'build/lib.linux-x86_64-3.10' does not exist -- can't clean it
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.10' does not exist -- can't clean it
> # clean the doc
> # workaround for cleaning the doc ("doc/make.py clean" only runs useless
> svn-clean)
> rm -f doc/api/_as_gen/*
> #rm -rf doc/build doc/examples
> #rm -f doc/mpl_examples/api/*.png
> #rm -f doc/mpl_examples/pylab_examples/*.png
> #rm -f doc/mpl_examples/pylab_examples/*.pdf
> #rm -f doc/mpl_examples/units/*.png
> #rm -f doc/pyplots/tex_demo.png
> #rm -f doc/_static/matplotlibrc
> #rm -f doc/_templates/gallery.html
> find . -name '*.pyc' -exec rm {} \;
> #dh_clean lib/matplotlib/mpl-data/matplotlib.conf \
> # lib/matplotlib/mpl-data/matplotlibrc setup.cfg
> rm -rf build
> rm -rf lib/matplotlib.egg-info
> # restore "pristine" doc/matplotlibrc
> sed -i '/^examples\./d' /<>/doc/matplotlibrc
> ## remove doc symlinks to examples directory
> #rm -rf doc/mpl_examples
> #rm -rf doc/mpl_toolkits/axes_grid/examples
> # build twice in a row
> rm -rf doc/tex.cache/ fontList.py3k.cache result_images/ test_cache/
> tex.cache/ examples/pylab_examples/test.xls
> rm -rf doc/finance.cache/ doc/fontList.cache fontList.cache
> # remove embedded CXX to prevent it to be picked up
> rm -rf extern/CXX/
> dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building matplotlib using existing
> ./matplotlib_3.5.2.orig.tar.xz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: local changes detected, the modified files are:
> matplotlib-3.5.2/lib/matplotlib/_version.py
> dpkg-source: error: aborting due to unexpected upstream changes, see
> /tmp/matplotlib_3.5.2-1.diff.xdCjx7
> dpkg-source: info: Hint: make sure the version in debian/changelog matches
> the unpacked source tree
> dpkg-source: info: you can integrate the local changes with dpkg-source
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
>
> Build finished at 2022-07-16T05:46:57Z
The full build log is available from:
http://qa-logs.debian.net/2022/07/16/matplotlib_3.5.2-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org
or:
Bug#1015081: marked as pending in matplotlib
Control: tag -1 pending Hello, Bug #1015081 in matplotlib reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/matplotlib/-/commit/e669ce52afe675918dc22eeab67a4342bbe81560 remove lib/matplotlib/_version.py in the clean target instead of trying to mess with it; Closes: #1015081 (this message was generated automatically) -- Greetings https://bugs.debian.org/1015081
Processed: Bug#1015081 marked as pending in matplotlib
Processing control commands: > tag -1 pending Bug #1015081 [src:matplotlib] matplotlib: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 Added tag(s) pending. -- 1015081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015081 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015224: Illegal instruction (SIGILL) on arm64
Package: librocksdb6.11 Version: 6.11.4-3 Severity: grave Tags: bullseye, patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I got just hit by https://github.com/facebook/rocksdb/pull/7233 on my RPI 400 running Debian Bullseye. I rebuilt the librocksdb6.11 package with the patch from https://github.com/facebook/rocksdb/commit/29f7bbef995bdf83098963799c66af742e95373f and I can confirm that this patch fixes the SIGILL issue. Is there any chance to push that fix into Bullseye? Without it, librocksdb is not working for me on my Raspberry PI. Regards, Daniel - -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages librocksdb6.11 depends on: ii libbz2-1.01.0.8-5 ii libc6 2.33-8 ii libgcc-s1 12.1.0-5 pn libgflags2.2 ii liblz4-1 1.9.3-2 ii libsnappy1v5 1.1.9-2 ii libstdc++612.1.0-5 ii libzstd1 1.5.2+dfsg-1 ii zlib1g1:1.2.11.dfsg-4 librocksdb6.11 recommends no packages. librocksdb6.11 suggests no packages. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEIB9kcJqmmF4VguFXclr8JZgo7DMFAmLUhqkACgkQclr8JZgo 7DPsPRAAtqU9d0WaXdqYIfrjyMNnJkvcCzGTM211mRIq5tFk9PqiyRAWZqjhCwn3 7QNA4uYQbECXgd6Bgc+hP+GDoPlbwPYRe6VeNIzPc87LpAVh2BR2jG2D4tzCtG1/ hHqolpGbDsMmTyr1hSQwfZWwCZJ5uIsIk60Of3O1TD/PM2dFpSqwFb/dwKJ2B/v+ oqqaZDLOxeh87vqEmFmCxubstk9giNWtID9tMXfE8c5ot9naAViNBlHzRyj9L2PC xJ7dPSmS4qqWouZUSOM/PaIYjmK2oFB2OVJ/w1isao0SNkQIePRMg43R8x5TGKI+ x3pUvPyBe5lekq2yVD/wigOSFF2fLh+FhM/5+Noq+c6aEIRAU16pa0iMA5SF/w9C 5l0tapF/T0RYM8zaAfZe95hqCgq4OtUwHry1OEEL/r0ngEPnLkjUwHaOVPr0PGNh ZZhmBrpg23NR17m+4H4OksyGB3D8w8I5X2EiljKBiIXZzOVUO5ATGedZOM2nWXH7 EYCZqhbjVWCYuGZtNBuzlFaeK5bGA0UWTj+LG1LQcaAXIWLnWJQ7vKeXDiDeJ+m/ hposcBS9yR3ndCX0Wp418EvgQVYgnmCABbeH/o2PJ1JgvpFDLajUHeWOhSSU7iGu yAvryTvY/Hc/4uXRr7V0F+YKoBCbNOVKrnS/ypZbxBHSt/p9Yu4= =GH1z -END PGP SIGNATURE-
Processed: bug 1015094 is forwarded to https://github.com/pmem/libpmemobj-cpp/issues/1262
Processing commands for cont...@bugs.debian.org: > forwarded 1015094 https://github.com/pmem/libpmemobj-cpp/issues/1262 Bug #1015094 [src:libpmemobj-cpp] libpmemobj-cpp: FTBFS: make[1]: *** [debian/rules:26: override_dh_auto_test] Error 8 Set Bug forwarded-to-address to 'https://github.com/pmem/libpmemobj-cpp/issues/1262'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1015094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015094 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015011: marked as done (autopkgtest fail with python3-jsonschema 4.6.0)
Your message dated Sun, 17 Jul 2022 20:38:03 + with message-id and subject line Bug#1015011: fixed in bmtk 1.0.5+ds-2 has caused the Debian Bug report #1015011, regarding autopkgtest fail with python3-jsonschema 4.6.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.) -- 1015011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015011 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bmtk Version: 1.0.5+ds-1 Severity: important Dear maintainer, I intend to quickly upload python3-jsonschema >= 4, because other package maintainer need that new version for their packages. I uploaded version 4.6.0 to Experimental, and the pseudo-excuses page shows failures in the autopkgtest of your package. Please see this page: https://release.debian.org/britney/pseudo-excuses-experimental.html#python-jsonschema This bug is using severity important, when python3-jsonschema >= 4 will reach unstable, severity of this bug will be set to serious (ie: RC bug), which can later trigger AUTORM if not addressed. Cheers, Thomas Goirand (zigo) --- End Message --- --- Begin Message --- Source: bmtk Source-Version: 1.0.5+ds-2 Done: Étienne Mollier We believe that the bug you reported is fixed in the latest version of bmtk, 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. Étienne Mollier (supplier of updated bmtk 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, 17 Jul 2022 21:48:30 +0200 Source: bmtk Architecture: source Version: 1.0.5+ds-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Étienne Mollier Closes: 1015011 Changes: bmtk (1.0.5+ds-2) unstable; urgency=medium . * Add jsonschema4.patch. (Closes: #1015011) * d/control: add myself to uploaders. * Set upstream metadata fields: Repository. * Apply multi-arch hints. + python3-bmtk-doc: Add Multi-Arch: foreign. Checksums-Sha1: f6f9947ce20bd6ceab582f24e2978d3d815bc0db 2793 bmtk_1.0.5+ds-2.dsc 44a83d57f68079509500174df34aab726929e72c 7920 bmtk_1.0.5+ds-2.debian.tar.xz Checksums-Sha256: b81ccf083d9321b15688ae9750bd9a98fbd0ade603b6ca28471a98a86fea9a92 2793 bmtk_1.0.5+ds-2.dsc d835a0bb0d0cbf8df790cef3bf7da47d82e862d0754562a0e5864f366a4014c4 7920 bmtk_1.0.5+ds-2.debian.tar.xz Files: 4d7a824812bb2a6bffbf5d942ec3a28b 2793 science optional bmtk_1.0.5+ds-2.dsc 64b36274084320f7a6fa651ce8df2392 7920 science optional bmtk_1.0.5+ds-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmLUbp8UHGVtb2xsaWVy QGRlYmlhbi5vcmcACgkQeTz2fo8NEdoXXRAAtdDoXOYJDyXCbqe4TId5t6siS6g+ 0fdqFnI2Z9hrgZPIUJcmhbF34Goq67q++ulTZbmDF37gtdUHrr5DtV5NIBL7xBwP pjLDPNGDf/ZWSAnmlVBTv5G5wVKG0SNhnwfBYu7i+1BXug+chugp3oMeLJxSI/1h sHHIKv9NEmZHVQh2LKsfAHQhiUuEfa87eZnP1qvERNPv+AEF9/fkfPlTDIxoRwR4 tGdZiIrhqobvjp14HADFXF/AzNYtaLBRit2Ka/8YtybQL6q7nukX557iL6qdJslg lNzW+p4Tm6uPzqVl/SaWCmLQG2RAGuZPTqG/97EF4YM/Y9PVHRO73q+jThOhMPbu ztNGScvJbmaKAoFGY+qaMKE3jEEmP2ME9KURJZlXu2yZxkbBMA1V7j/2wwX1gzD7 9JZqRxkh0sf50M3gjiKNDfe/B+mKoTy250Zp33bRPeTKkJUJZUlEa/uH2UBw1V/m SkTnZMGseYaGQqOb9ySe/UetvCq5tb+qo5BqveaPCc3Eo/bwTPRLTaQreYUoW05i 7ZF1yVtxgiYW8JgPUcJB+TyurThHk2c1vpR8ZY9PTwK2yiu5DgTBaLXUCXqMWKG5 8COxo9MUMy3h5YLCzniu5MVV+vFRSpfJCqNXpuLlepiRSBDjrg4siK9Zk1xR2Jd2 o7T3sWxhYqlqNuw= =sepl -END PGP SIGNATURE End Message ---
Bug#1015218: consul: CVE-2021-37219 CVE-2021-38698 CVE-2022-29153
Source: consul X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for consul. CVE-2021-37219[0]: | HashiCorp Consul and Consul Enterprise 1.10.1 Raft RPC layer allows | non-server agents with a valid certificate signed by the same CA to | access server-only functionality, enabling privilege escalation. Fixed | in 1.8.15, 1.9.9 and 1.10.2. https://discuss.hashicorp.com/t/hcsec-2021-22-consul-raft-rpc-privilege-escalation/29024 CVE-2021-38698[1]: | HashiCorp Consul and Consul Enterprise 1.10.1 Txn.Apply endpoint | allowed services to register proxies for other services, enabling | access to service traffic. Fixed in 1.8.15, 1.9.9 and 1.10.2. https://discuss.hashicorp.com/t/hcsec-2021-24-consul-missing-authorization-check-on-txn-apply-endpoint/29026 https://github.com/hashicorp/consul/commit/747844bad6410091f2c6e961216c0c5fc285a44d (v1.8.15) CVE-2022-29153[2]: | HashiCorp Consul and Consul Enterprise through 2022-04-12 allow SSRF. https://discuss.hashicorp.com/t/hcsec-2022-10-consul-s-http-health-check-may-allow-server-side-request-forgery/38393 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-2021-37219 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-37219 [1] https://security-tracker.debian.org/tracker/CVE-2021-38698 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-38698 [2] https://security-tracker.debian.org/tracker/CVE-2022-29153 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29153 Please adjust the affected versions in the BTS as needed.
Bug#992645: marked as done (ncftp: stores wrong path to tar if built on merged-/usr system)
Your message dated Sun, 17 Jul 2022 19:48:59 +
with message-id
and subject line Bug#992645: fixed in ncftp 2:3.2.6-1
has caused the Debian Bug report #992645,
regarding ncftp: stores wrong path to tar if built on merged-/usr system
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.)
--
992645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992645
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ncftp
Version: 2:3.2.5-2.2
Severity: important
Tags: patch bookworm sid
User: reproducible-bui...@lists.alioth.debian.org
Usertags: usrmerge
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
If ncftp is built on a merged-/usr system (as created by new installations
of Debian >= 10, debootstrap --merged-usr, or installing the usrmerge
package into an existing installation), the path to tar is recorded in the
binary as /usr/bin/tar.
This can be seen on the reproducible-builds.org infra:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/ncftp.html
(search for "/bin/tar" to see the difference I'm concerned about).
If you have sbuild available, an easy way to reproduce this is to build
ncftp twice, once with --add-depends-arch=usrmerge and once without.
The problematic situation is if pkgconf is *built* on a merged-/usr
system, but *used* on a non-merged-/usr system. In this situation,
/usr/bin/tar exists on the build system but not on the system where
ncftp will be used, resulting in the feature that uses tar not being
available.
Technical Committee resolution #978636 mandates heading towards a
transition to merged-/usr, and this will become a non-issue at the end of
that transition; but variation between merged-/usr and non-merged-/usr
builds is a problem while that transition is taking place, because it
can lead to partial upgrades behaving incorrectly. It is likely that
this class of bugs will become release-critical later in the bookworm
development cycle.
Some Debian developers advocate that instead of merged-/usr, we should
use a different strategy where /bin becomes a "symlink farm" with
individual symlinks such as /bin/tar -> /usr/bin/tar. If that route is
taken instead of merged-/usr, then resolving bugs like this one will be
equally important as part of that transition, because it shares the
property that both /bin/tar and /usr/bin/tar exist after the transition,
but only /bin/tar exists on untransitioned systems.
The attached patch resolves this: with it applied, the package builds
identically with and without --add-depends-arch=usrmerge.
A side benefit of fixing this is that this change might be sufficient
to make the package reproducible (as recommended by Policy §4.15).
smcv
>From 252c7fdcee3fa2548bc8246849aa3dc280169992 Mon Sep 17 00:00:00 2001
From: Simon McVittie
Date: Sat, 21 Aug 2021 16:50:49 +0100
Subject: [PATCH] d/rules: Specify canonical path to tar
If ncftp is built on a merged-/usr system, then tar is available at
both /usr/bin/tar and /bin/tar, but if it is subsequently used on a
non-merged-/usr system, only /bin/tar will work. Force the canonical
path /bin/tar so that the layout of the build system does not matter.
Signed-off-by: Simon McVittie
---
debian/rules | 1 +
1 file changed, 1 insertion(+)
diff --git a/debian/rules b/debian/rules
index 5b12238..a0410b4 100755
--- a/debian/rules
+++ b/debian/rules
@@ -21,6 +21,7 @@ config.status:
dh_testdir
cp /usr/share/misc/config.guess /usr/share/misc/config.sub .
# Add here commands to configure the package.
+ TAR=/bin/tar \
CFLAGS="$(CFLAGS)" CPPFLAGS="$(CPPFLAGS)" LDFLAGS="$(LDFLAGS)" ./configure \
--prefix=/usr \
--mandir=\$${prefix}/share/man \
--
2.33.0
--- End Message ---
--- Begin Message ---
Source: ncftp
Source-Version: 2:3.2.6-1
Done: Noël Köthe
We believe that the bug you reported is fixed in the latest version of
ncftp, 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 992...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Noël Köthe (supplier of updated ncftp 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, 17 Jul 2022 20:24:42
Bug#1015214: node-canvas-confetti: FTBFS dh_auto_test SyntaxError: Cannot use import statement outside a module
Source: node-canvas-confetti Version: 1.5.1-1 Severity: serious Tags: ftbfs Justification: fails to build from source In debian/unstable, Here's the log dh binary dh_update_autotools_config dh_autoreconf dh_auto_configure --buildsystem=nodejs dh_auto_build --buildsystem=nodejs Found debian/nodejs/./build cd ./. && sh -ex debian/nodejs/./build + node build/build.js dh_auto_test --buildsystem=nodejs mkdir -p node_modules ln -s ../. node_modules/canvas-confetti /bin/sh -ex debian/tests/pkg-js/test + cd test + ava --verbose --serial Uncaught exception in test/index.test.js SyntaxError: Cannot use import statement outside a module ✖ test/index.test.js exited with a non-zero exit code: 1 Uncaught exception in test/ssr.test.js SyntaxError: Cannot use import statement outside a module ✖ test/ssr.test.js exited with a non-zero exit code: 1 ─ 2 uncaught exceptions dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 make: *** [debian/rules:8: binary] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1015095: libzeep: FTBFS: make[3]: *** [CMakeFiles/doc.dir/build.make:76: ../doc/html/index.html] Error 1
On 16/07/22 at 19:28 +0200, Maarten L. Hekkelman wrote: > Hi, > > Problem here is that during the generation of the documentation, the > xslt-processor chokes on a line in the file > /usr/share/boostbook/xsl/annotation.xsl which comes from libboost-tools-dev. > My guess is that the boost file did not change but the xslt-processor now no > longer accepts it as input. But I may be wrong. > > Anyway, I don't know how to reassign a bug. Hope someone else can do that > for me? Hi, Here is an example: Control: reassign -1 golang-github-getkin-kin-openapi Control: found -1 golang-github-getkin-kin-openapi/0.97.0-1 Control: affects -1 perl6-readline raku-getopt-long raku-tap-harness Lucas
Processed: Re: [Debian-med-packaging] Bug#1015011: Upgrading to severity serious
Processing control commands: > forwarded -1 https://github.com/AllenInstitute/bmtk/issues/241 Bug #1015011 [src:bmtk] autopkgtest fail with python3-jsonschema 4.6.0 Set Bug forwarded-to-address to 'https://github.com/AllenInstitute/bmtk/issues/241'. > tags -1 confirmed patch pending upstream Bug #1015011 [src:bmtk] autopkgtest fail with python3-jsonschema 4.6.0 Added tag(s) confirmed, patch, pending, and upstream. -- 1015011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015011 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: golang-gopkg-goose.v1: FTBFS
Processing control commands: > tags -1 +moreinfo +unreproducible Bug #1015070 [src:golang-gopkg-goose.v1] golang-gopkg-goose.v1: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 gopkg.in/goose.v1 gopkg.in/goose.v1/cinder gopkg.in/goose.v1/client gopkg.in/goose.v1/errors gopkg.in/goose.v1/glance gopkg.in/goose.v1/http gopkg.in/goose.v1/identity gopkg.in/goose.v1/logging gopkg.in/goose.v1/neutron gopkg.in/goose.v1/nova gopkg.in/goose.v1/swift gopkg.in/goose.v1/sync gopkg.in/goose.v1/testing/envsuite gopkg.in/goose.v1/testing/httpsuite gopkg.in/goose.v1/testservices gopkg.in/goose.v1/testservices/hook gopkg.in/goose.v1/testservices/identityservice gopkg.in/goose.v1/testservices/neutronmodel gopkg.in/goose.v1/testservices/neutronservice gopkg.in/goose.v1/testservices/novaservice gopkg.in/goose.v1/testservices/openstackservice gopkg.in/goose.v1/testservices/swiftservice returned exit code 1 Added tag(s) moreinfo. Bug #1015070 [src:golang-gopkg-goose.v1] golang-gopkg-goose.v1: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 gopkg.in/goose.v1 gopkg.in/goose.v1/cinder gopkg.in/goose.v1/client gopkg.in/goose.v1/errors gopkg.in/goose.v1/glance gopkg.in/goose.v1/http gopkg.in/goose.v1/identity gopkg.in/goose.v1/logging gopkg.in/goose.v1/neutron gopkg.in/goose.v1/nova gopkg.in/goose.v1/swift gopkg.in/goose.v1/sync gopkg.in/goose.v1/testing/envsuite gopkg.in/goose.v1/testing/httpsuite gopkg.in/goose.v1/testservices gopkg.in/goose.v1/testservices/hook gopkg.in/goose.v1/testservices/identityservice gopkg.in/goose.v1/testservices/neutronmodel gopkg.in/goose.v1/testservices/neutronservice gopkg.in/goose.v1/testservices/novaservice gopkg.in/goose.v1/testservices/openstackservice gopkg.in/goose.v1/testservices/swiftservice returned exit code 1 Added tag(s) unreproducible. > severity -1 important Bug #1015070 [src:golang-gopkg-goose.v1] golang-gopkg-goose.v1: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 gopkg.in/goose.v1 gopkg.in/goose.v1/cinder gopkg.in/goose.v1/client gopkg.in/goose.v1/errors gopkg.in/goose.v1/glance gopkg.in/goose.v1/http gopkg.in/goose.v1/identity gopkg.in/goose.v1/logging gopkg.in/goose.v1/neutron gopkg.in/goose.v1/nova gopkg.in/goose.v1/swift gopkg.in/goose.v1/sync gopkg.in/goose.v1/testing/envsuite gopkg.in/goose.v1/testing/httpsuite gopkg.in/goose.v1/testservices gopkg.in/goose.v1/testservices/hook gopkg.in/goose.v1/testservices/identityservice gopkg.in/goose.v1/testservices/neutronmodel gopkg.in/goose.v1/testservices/neutronservice gopkg.in/goose.v1/testservices/novaservice gopkg.in/goose.v1/testservices/openstackservice gopkg.in/goose.v1/testservices/swiftservice returned exit code 1 Severity set to 'important' from 'serious' -- 1015070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015070 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015070: golang-gopkg-goose.v1: FTBFS
Control: tags -1 +moreinfo +unreproducible Control: severity -1 important On Sat, 16 Jul 2022 15:43:55 +0200 Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. Thanks for the report. However, locally I haven't been able to reproduce this FTBFS in my sid schroot. I've attached the complete log from a successful build I performed this afternoon. Are you able to reproduce this build failure locally? Is so, I'd be interested to see if we can figure out what the delta is between our setups that's triggering the test failure. Thanks, Mathias binUZFtXdFxwu.bin Description: application/gzip signature.asc Description: This is a digitally signed message part
Bug#1011970: nrepl-clojure: autopkgtest regression on armhf and i386
retitle 1011970 src:nrpepl-clojure: FTBFS on i386 (and maybe on armhf?) tags 1011970 ftbfs thanks So I tried building on i386 and I get the same error as the autopkgtest (who's running the upstream testsuite). So this is FTBFS and not just an autopkgtest regression. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄
Processed: Re: nrepl-clojure: autopkgtest regression on armhf and i386
Processing commands for cont...@bugs.debian.org: > retitle 1011970 src:nrpepl-clojure: FTBFS on i386 (and maybe on armhf?) Bug #1011970 [src:nrepl-clojure] nrepl-clojure: autopkgtest regression on armhf and i386 Changed Bug title to 'src:nrpepl-clojure: FTBFS on i386 (and maybe on armhf?)' from 'nrepl-clojure: autopkgtest regression on armhf and i386'. > tags 1011970 ftbfs Bug #1011970 [src:nrepl-clojure] src:nrpepl-clojure: FTBFS on i386 (and maybe on armhf?) Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1011970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011970 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1011970: Fwd: src:nrepl-clojure: fails to migrate to testing for too long: autopkgtest regression
So the arches that the autopkgtest fails on are all 32 bits (i386, armhf), which looked suspicious to me. I (finally) got around to test upstream's 0.9.0 tag fetching libraries from Maven using `lein test` in an i386 chroot, and all tests pass fine :( I guess this means it's not an upstream issue and is created by something we're doing in Debian. More debug needed! NB: the "java.io.FileNotFoundException: Could not locate unknown_middleware__init.class" is expected, the actual testsuite failure is "FAIL in (hotloading-common-classloader-test) (core_test.clj:1182)" -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄
Bug#1015026: marked as done (fortunes-debian-hints: FTBFS: po4a::chooser: Module loading error: Can't locate Syntax/Keyword/Try.pm in @INC)
Your message dated Sun, 17 Jul 2022 20:27:24 +0200 with message-id and subject line Re: Bug#1015026: fortunes-debian-hints: FTBFS: po4a::chooser: Module loading error: Can't locate Syntax/Keyword/Try.pm in @INC has caused the Debian Bug report #1015026, regarding fortunes-debian-hints: FTBFS: po4a::chooser: Module loading error: Can't locate Syntax/Keyword/Try.pm in @INC 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.) -- 1015026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015026 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fortunes-debian-hints Version: 2.01.4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > strfile hints > "hints.dat" created > There were 44 strings > Longest string: 397 bytes > Shortest string: 58 bytes > po4a --msgid-bugs-address "Kartik Mistry " --previous > po4a.cfg > Unknown format type: text. > po4a::chooser: Module loading error: Can't locate Syntax/Keyword/Try.pm in > @INC > BEGIN failed--compilation aborted at /usr/share/perl5/Locale/Po4a/Text.pm > line 61. > Compilation failed in require at (eval 37) line 1. > BEGIN failed--compilation aborted at (eval 37) line 1. > > List of valid formats: > - asciidoc: AsciiDoc format. > - dia: uncompressed Dia diagrams. > - docbook: DocBook XML. > - guide: Gentoo Linux's XML documentation format. > - ini: INI format. > - kernelhelp: Help messages of each kernel compilation option. > - latex: LaTeX format. > - man: Good old manual page format. > - pod: Perl Online Documentation format. > - rubydoc: Ruby Documentation (RD) format. > - sgml: either DebianDoc or DocBook DTD. > - texinfo: The info page format. > - tex: generic TeX documents (see also latex). > - text: simple text document. > - wml: WML documents. > - xhtml: XHTML documents. > - xml: generic XML documents (see also docbook). > - yaml: YAML documents. > make[1]: *** [debian/rules:18: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/07/16/fortunes-debian-hints_2.01.4_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220716=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 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 17/07/22 at 17:23 +0530, Kartik Mistry wrote: > On Sat, Jul 16, 2022 at 7:30 PM Lucas Nussbaum wrote: > > During a rebuild of all packages in sid, your package failed to build > > on amd64. > > Thanks for all this tedious work! > > > 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. > > I can't reproduce this locally or via Salsa CI. See: > https://salsa.debian.org/debian/fortunes-debian-hints/-/jobs/3002295 > > Is this sufficient? A diff would be difficult to generate in both build cases. There was a po4a regression which was fixed in the next po4a upload. I suspect this is what hit this package, so closing. Lucas--- End Message ---
Bug#1014100: marked as done (qiime: autopkgtest needs update for new version of python-decorator)
Your message dated Sun, 17 Jul 2022 19:57:20 +0200
with message-id
and subject line qiime - 2022.2.1 builds again
has caused the Debian Bug report #1014100,
regarding qiime: autopkgtest needs update for new version of python-decorator
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.)
--
1014100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014100
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qiime
Version: 2021.8.0-2
Severity: serious
X-Debbugs-CC: python-decora...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:python-decorator
Dear maintainer(s),
With a recent upload of python-decorator the autopkgtest of qiime fails
in testing when that autopkgtest is run with the binary packages of
python-decorator from unstable. It passes when run with only packages
from testing. In tabular form:
passfail
python-decorator from testing5.1.1-2
qiime from testing2021.8.0-2
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 python-decorator
to testing [1]. Of course, python-decorator shouldn't just break your
autopkgtest (or even worse, your package), but it seems to me that the
change in python-decorator was intended and your package needs to update
to the new situation. To me it looks like the references need updating
for the new version but I might be wrong.
If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from python-decorator should
really add a versioned Breaks on the unfixed version of (one of your)
package(s). Note: the Breaks is nice even if the issue is only in the
autopkgtest as it helps the migration software to figure out the right
versions to combine in the tests.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=python-decorator
https://ci.debian.net/data/autopkgtest/testing/amd64/q/qiime/23173367/log.gz
FF.FFF..
==
FAIL: test_callable_and_async_signature_with_artifacts_and_parameters
(qiime2.sdk.tests.test_method.TestMethod)
--
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.t_q3d0jx/downtmp/autopkgtest_tmp/qiime2/sdk/tests/test_method.py",
line 223, in test_callable_and_async_signature_with_artifacts_and_parameters
self.assertEqual(parameters, exp_parameters)
AssertionError: Lists differ: [('in[20 chars]ts1: list">), ('ints2',
)] != [('in[20 chars]ts1:
IntSequence1 | IntSequence2">), ('ints2',[147 chars]t">)]
First differing element 0:
('ints1', )
('ints1', )
Diff is 735 characters long. Set self.maxDiff to None to see it.
==
FAIL: test_callable_and_async_signature_with_no_parameters
(qiime2.sdk.tests.test_method.TestMethod)
--
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.t_q3d0jx/downtmp/autopkgtest_tmp/qiime2/sdk/tests/test_method.py",
line 242, in test_callable_and_async_signature_with_no_parameters
self.assertEqual(parameters, exp_parameters)
AssertionError: Lists differ: [('ma[26 chars]ng1: dict">), ('mapping2',
)] != [('ma[26 chars]ng1: Mapping">),
Bug#1014918: src:nrepl-clojure: fails to migrate to testing for too long: autopkgtest regression
So the arches that the autopkgtest fails on are all 32 bits (i386, armhf), which looked suspicious to me. I (finally) got around to test upstream's 0.9.0 tag fetching libraries from Maven using `lein test` in an i386 chroot, and all tests pass fine :( I guess this means it's not an upstream issue and is created by something we're doing in Debian. More debug needed! NB: the "java.io.FileNotFoundException: Could not locate unknown_middleware__init.class" is expected, the actual testsuite failure is "FAIL in (hotloading-common-classloader-test) (core_test.clj:1182)" -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄
Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel")
https://developers.slashdot.org/story/22/07/17/0110250/gcc-rust-approved-by-steering-committee-beta-likely-next-april and now it becomes Unlawful for Debian to distribute gcc with patches, as well [without the explicit consent of the Mozilla Foundation, an action which is in direct violation of DFSG] l.
Bug#1004769: Video not handled anymore for now
On Sunday, July 17, 2022 4:09:20 A.M. CDT you wrote: > Le 16/07/2022 à 18:50, Steven Robbins a écrit : > > I would say that there may well be others in your situation so if you do > > find a method please report back to this bug. > >For my personnal use, until upstream provides a correct fix, I recompile > digikam 7.7.0-1 (-2 was not pushed in the git ;-) ) Now pushed, thanks! -Steve signature.asc Description: This is a digitally signed message part.
Bug#1015079: marked as done (dh-raku: FTBS others package with test failure when perl5 prove is used)
Your message dated Sun, 17 Jul 2022 15:50:01 + with message-id and subject line Bug#1015079: fixed in dh-raku 0.11 has caused the Debian Bug report #1015079, regarding dh-raku: FTBS others package with test failure when perl5 prove is used to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1015079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015079 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: perl6-readline Version: 0.1.5-5 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_raku_build > Pre-compiling perl6-readline > HOME=/<>/debian/tmp/home/ RAKUDO_LOG_PRECOMP=1 > RAKUDO_RERESOLVE_DEPENDENCIES=0 raku /usr/share/perl6/tools/install-dist.p6 > --for=vendor --from=. --to=debian/tmp/pre-compiled > Precompiling EBC1B2DDA59A9D91D483BD81DAA416714D2D1276 (Readline) >dh_raku_test > HOME=/<>/debian/tmp/home/ /usr/bin/prove --exec raku -l -v > [31m===[0mSORRY![31m===[0m Error while compiling > /<>/t/01-load.t > Could not find Readline in: > /<>/debian/tmp/home/.raku > /usr/lib/perl6/site > /usr/lib/perl6/vendor > /usr/lib/perl6/core > CompUnit::Repository::AbsolutePath<94194822864720> > CompUnit::Repository::NQP<94194809017072> > CompUnit::Repository::Perl5<94194809017112> > at /<>/t/01-load.t:7 > t/01-load.t .. > Dubious, test returned 1 (wstat 256, 0x100) > No subtests run > [31m===[0mSORRY![31m===[0m Error while compiling > /<>/t/02-base.t > Could not find Readline in: > /<>/debian/tmp/home/.raku > /usr/lib/perl6/site > /usr/lib/perl6/vendor > /usr/lib/perl6/core > CompUnit::Repository::AbsolutePath<94365082360768> > CompUnit::Repository::NQP<94365072513504> > CompUnit::Repository::Perl5<94365072513544> > at /<>/t/02-base.t:3 > t/02-base.t .. > Dubious, test returned 1 (wstat 256, 0x100) > No subtests run > > Test Summary Report > --- > t/01-load.t (Wstat: 256 Tests: 0 Failed: 0) > Non-zero exit status: 1 > Parse errors: No plan found in TAP output > t/02-base.t (Wstat: 256 Tests: 0 Failed: 0) > Non-zero exit status: 1 > Parse errors: No plan found in TAP output > Files=2, Tests=0, 1 wallclock secs ( 0.03 usr 0.00 sys + 1.19 cusr 0.28 > csys = 1.50 CPU) > Result: FAIL > dh_raku_test: error: HOME=/<>/debian/tmp/home/ /usr/bin/prove > --exec raku -l -v returned exit code 1 > make: *** [debian/rules:4: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2022/07/16/perl6-readline_0.1.5-5_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220716=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 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 --- Source: dh-raku Source-Version: 0.11 Done: Dominique Dumont We believe that the bug you reported is fixed in the latest version of dh-raku, 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. Dominique Dumont (supplier of updated dh-raku 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, 17 Jul 2022 17:16:20 +0200 Source: dh-raku Architecture: source Version: 0.11 Distribution: unstable Urgency: medium Maintainer: Debian Rakudo Maintainers Changed-By: Dominique
Bug#1014689: marked as done (leiningen-clojure breaks cljx-clojure autopkgtest: artifact nrepl:nrepl:jar:0.9.0 has not been downloaded)
Your message dated Sun, 17 Jul 2022 17:25:34 +0200
with message-id <487f5772-6d90-c63a-6a77-4e77a756b...@debian.org>
and subject line close leiningen-not-migrating-because-of-cljx
has caused the Debian Bug report #1014689,
regarding leiningen-clojure breaks cljx-clojure autopkgtest: artifact
nrepl:nrepl:jar:0.9.0 has not been downloaded
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.)
--
1014689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014689
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: leiningen-clojure, cljx-clojure
Control: found -1 leiningen-clojure/2.9.1-6
Control: found -1 cljx-clojure/0.6.0-3
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of leiningen-clojure the autopkgtest of
cljx-clojure fails in testing when that autopkgtest is run with the
binary packages of leiningen-clojure from unstable. It passes when run
with only packages from testing. In tabular form:
passfail
leiningen-clojure from testing2.9.1-6
cljx-clojure from testing0.6.0-3
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of leiningen-clojure
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=leiningen-clojure
https://ci.debian.net/data/autopkgtest/testing/amd64/c/cljx-clojure/23492153/log.gz
Rewriting test to target/test-output (clj) with features #{clj} and 0
transformations.
Rewriting test to target/test-output (cljs) with features #{cljs} and 1
transformations.
Cannot access central (https://repo1.maven.org/maven2/) in offline mode
and the artifact nrepl:nrepl:jar:0.9.0 has not been downloaded from it
before.
Cannot access clojars (https://repo.clojars.org/) in offline mode and
the artifact nrepl:nrepl:jar:0.9.0 has not been downloaded from it before.
This could be due to a typo in :dependencies, file system permissions,
or network issues.
If you are behind a proxy, try setting the 'http_proxy' environment
variable.
autopkgtest [19:11:54]: test unittests
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
This issue was fixed when I uploaded leiningen 2.9.1-8.
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau
⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org
⠈⠳⣄--- End Message ---
Processed (with 1 error): reassign 1015110 to dh-raku, reassign 1015034 to dh-raku, merging 1015079 1015110 1015034
Processing commands for cont...@bugs.debian.org: > reassign 1015110 dh-raku Bug #1015110 [src:raku-getopt-long] raku-getopt-long: FTBFS: Failed to create directory '/usr/lib/perl6/site/short' with mode '0o777': Failed to mkdir: Permission denied Bug reassigned from package 'src:raku-getopt-long' to 'dh-raku'. No longer marked as found in versions raku-getopt-long/0.3.3-2. Ignoring request to alter fixed versions of bug #1015110 to the same values previously set > reassign 1015034 dh-raku Bug #1015034 [src:raku-tap-harness] raku-tap-harness: FTBFS: Failed to create directory '/usr/lib/perl6/site/short' with mode '0o777': Failed to mkdir: Permission denied Bug reassigned from package 'src:raku-tap-harness' to 'dh-raku'. No longer marked as found in versions raku-tap-harness/0.3.5-2. Ignoring request to alter fixed versions of bug #1015034 to the same values previously set > merge 1015079 1015110 1015034 Bug #1015079 [dh-raku] dh-raku: FTBS others package with test failure when perl5 prove is used Unable to merge bugs because: affects of #1015110 is '' not 'perl6-readline,raku-tap-harness,raku-getopt-long' affects of #1015034 is '' not 'perl6-readline,raku-tap-harness,raku-getopt-long' Failed to merge 1015079: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1015034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015034 1015079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015079 1015110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015110 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): merging 1015079 1015110 1015034
Processing commands for cont...@bugs.debian.org: > merge 1015079 1015110 1015034 Bug #1015079 [dh-raku] dh-raku: FTBS others package with test failure when perl5 prove is used Unable to merge bugs because: affects of #1015034 is '' not 'perl6-readline,raku-tap-harness,raku-getopt-long' package of #1015034 is 'src:raku-tap-harness' not 'dh-raku' affects of #1015110 is '' not 'perl6-readline,raku-tap-harness,raku-getopt-long' package of #1015110 is 'src:raku-getopt-long' not 'dh-raku' Failed to merge 1015079: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1015034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015034 1015079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015079 1015110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015110 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1015079 to dh-raku ..., affects 1015079
Processing commands for cont...@bugs.debian.org: > reassign 1015079 dh-raku Bug #1015079 [src:perl6-readline] perl6-readline: FTBFS: make: *** [debian/rules:4: binary] Error 25 Bug reassigned from package 'src:perl6-readline' to 'dh-raku'. No longer marked as found in versions perl6-readline/0.1.5-5. Ignoring request to alter fixed versions of bug #1015079 to the same values previously set > retitle 1015079 dh-raku: FTBS others package with test failure when perl5 > prove is used Bug #1015079 [dh-raku] perl6-readline: FTBFS: make: *** [debian/rules:4: binary] Error 25 Changed Bug title to 'dh-raku: FTBS others package with test failure when perl5 prove is used' from 'perl6-readline: FTBFS: make: *** [debian/rules:4: binary] Error 25'. > affects 1015079 perl6-readline raku-getopt-long raku-tap-harness Bug #1015079 [dh-raku] dh-raku: FTBS others package with test failure when perl5 prove is used Added indication that 1015079 affects perl6-readline, raku-getopt-long, and raku-tap-harness > thanks Stopping processing here. Please contact me if you need assistance. -- 1015079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015079 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#915850: marked as done (rsnapshot: reproducible build (usrmerge): embeds path of tool found via PATH)
Your message dated Sun, 17 Jul 2022 15:06:31 + with message-id and subject line Bug#915850: fixed in rsnapshot 1.4.4-3 has caused the Debian Bug report #915850, regarding rsnapshot: reproducible build (usrmerge): embeds path of tool found via PATH 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.) -- 915850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915850 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rsnapshot Version: 1.4.2-1 Severity: normal Tags: unreproducible patch User: m...@linux.it Usertags: usrmerge Dear maintainer. The package rsnapshot currently fails to build reproducibly on merged-usr vs non-merged systems. Please see attached patch fixing this issue. Regards, Andreas Henriksson diff -Nru rsnapshot-1.4.2/debian/changelog rsnapshot-1.4.2/debian/changelog --- rsnapshot-1.4.2/debian/changelog2016-03-26 18:51:17.0 +0100 +++ rsnapshot-1.4.2/debian/changelog2018-12-06 21:25:55.0 +0100 @@ -1,3 +1,11 @@ +rsnapshot (1.4.2-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Explicitly pass paths to configure instead of looking up tools +- fixes reproducible build on merged-usr vs non-merged + + -- Andreas Henriksson Thu, 06 Dec 2018 21:25:55 +0100 + rsnapshot (1.4.2-1) unstable; urgency=medium * New upstream release (Closes: #817071), refresh patches diff -Nru rsnapshot-1.4.2/debian/rules rsnapshot-1.4.2/debian/rules --- rsnapshot-1.4.2/debian/rules2016-03-26 18:21:15.0 +0100 +++ rsnapshot-1.4.2/debian/rules2018-12-06 21:25:53.0 +0100 @@ -19,6 +19,12 @@ cp -f $(var) $(var).bak;) dh_autoreconf +override_dh_auto_configure: + dh_auto_configure -- \ + CP=/bin/cp RM=/bin/rm \ + LVCREATE=/sbin/lvcreate LVREMOVE=/sbin/lvremove \ + MOUNT=/bin/mount UMOUNT=/bin/umount + override_dh_install: dh_install # rename default configfile --- End Message --- --- Begin Message --- Source: rsnapshot Source-Version: 1.4.4-3 Done: Mark Hindley We believe that the bug you reported is fixed in the latest version of rsnapshot, 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 915...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mark Hindley (supplier of updated rsnapshot 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, 17 Jul 2022 15:16:36 +0100 Source: rsnapshot Architecture: source Version: 1.4.4-3 Distribution: unstable Urgency: medium Maintainer: Mark Hindley Changed-By: Mark Hindley Closes: 915850 Changes: rsnapshot (1.4.4-3) unstable; urgency=medium . * d/rules: specify paths so merged usr build is reproducible (Closes: #915850). Checksums-Sha1: 6793391e0e9319c21d8e95153a81b0571ca0e42e 1918 rsnapshot_1.4.4-3.dsc d78bf43b16772a389a6a8951f53c8be45726229a 15740 rsnapshot_1.4.4-3.debian.tar.xz 909e522cdf3d64ee1799982e636914a41ecea366 7181 rsnapshot_1.4.4-3_amd64.buildinfo Checksums-Sha256: b9d966d7d6cdb1eed9252cfb790e2927cb783eee2aecc38921d413669a9c4309 1918 rsnapshot_1.4.4-3.dsc 09754e80d245814fba43a922196b3568a38ac58e697f316eec2c60c79e938807 15740 rsnapshot_1.4.4-3.debian.tar.xz a11c726fad5c2430805b02c3e4709deb57f753ce9e5c1790da27f6f9acfc8823 7181 rsnapshot_1.4.4-3_amd64.buildinfo Files: 9968e908b3caf8050d67f7e3ee832f4c 1918 utils optional rsnapshot_1.4.4-3.dsc 7a9518cf9aefeecdd41e7efe3aea62bc 15740 utils optional rsnapshot_1.4.4-3.debian.tar.xz 7e3dbfd6771a46c45b85c3559e9f8728 7181 utils optional rsnapshot_1.4.4-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEUGwVpCsK9aCoVCPu0opFvzKH1kkFAmLUG+gACgkQ0opFvzKH 1klUxA//SabkSolK/ObO2xzoA190ctEbswddmptl4lxmbiDRRT6nU5tt1JSWKr1z p5/AJ4p5qsnumjtfOHrksg5JJEoav1l6mTq1Bld4XXwnOR/WLpW7hWW/HVdAUfNh Pq+pt7EgRB1a5sQP1ZHTkxa93tOcxEP/JDh8r1ELIEHtVQ1jO04GhB+m8S9szgKZ FhfvDsO3VMEw2SYHSXU4kU9J35IZpfwmFMuG/wLQPminIsl3wYL+smjrwbRNxKyQ kg84zJa4R8+BSqTVJelD/9IU+DTQqdDnmssVSUx+56D7uZvrj2D40Uv0p1AA7AqZ nK08Fwv4W0eMQVNs3xW32zOMOkvvdCR5ljT9EAdsKACG4ZbiVx3ajSDrONpgwKG/ NSjPF107J38rUmxIDQrAaOlY/Kpxx67uM/mjKC0pzmroirdk0ATU/oKVRv5vCGxK
Bug#1015008: marked as done (gnome-tweaks: gir1.2-notify-0.7 breaks startup of gnome-tweaks)
Your message dated Sun, 17 Jul 2022 15:04:31 + with message-id and subject line Bug#1015008: fixed in libnotify 0.8.1-1 has caused the Debian Bug report #1015008, regarding gnome-tweaks: gir1.2-notify-0.7 breaks startup of gnome-tweaks 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.) -- 1015008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015008 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-tweaks Version: 42~beta-1 Severity: important Tags: d-i X-Debbugs-Cc: compte.perso.de-al...@bbox.fr alain@sid:~$ apt-cache madison gir1.2-notify-0.7 gir1.2-notify-0.7 |0.8.0-1 | http://deb.debian.org/debian unstable/main amd64 Packages gir1.2-notify-0.7 | 0.7.12-1 | http://deb.debian.org/debian bookworm/main amd64 Packages gir1.2-notify-0.7 | 0.7.12-1 | http://deb.debian.org/debian testing/main amd64 Packages libnotify | 0.7.12-1 | http://deb.debian.org/debian bookworm/main Sources the 0.8.0-1 version of gir1.2-notify-0.7 (sid) breaks the startup of gnome tweaks. to solve this problem, i had to downgrade this package. alain@sid:~$ dpkg -l gnome-tweaks gir1.2-notify-0.7 Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder | État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi- installé/W=attend-traitement-déclenchements |/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais) ||/ Nom Version Architecture Description +++-===---== hi gir1.2-notify-0.7:amd64 0.7.12-1 amd64sends desktop notifications to a notification daemon (Introspection files) ii gnome-tweaks42~beta-1all tool to adjust advanced configuration settings for GNOME also i made an apt-mark hold on this package to prevent upgrade. friendly, respectfully, alain. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (100, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-2-amd64 (SMP w/24 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-tweaks depends on: ii dconf-gsettings-backend [gsettings-backend] 0.40.0-3 ii gir1.2-glib-2.0 1.72.0-1+b1 ii gir1.2-gnomedesktop-3.0 42.3-1 ii gir1.2-gtk-3.0 3.24.34-1 ii gir1.2-handy-1 1.6.2-1 hi gir1.2-notify-0.70.7.12-1 ii gir1.2-pango-1.0 1.50.7+ds-1 ii gir1.2-soup-2.4 2.74.2-3 ii gnome-settings-daemon42.2-1 ii gnome-shell-common 42.2-1 ii gnome-shell-extension-prefs 42.2-1 ii gsettings-desktop-schemas42.0-1 ii mutter-common42.2-1 ii python3 3.10.4-1+b1 ii python3-gi 3.42.1-1 gnome-tweaks recommends no packages. gnome-tweaks suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: libnotify Source-Version: 0.8.1-1 Done: Jeremy Bicha We believe that the bug you reported is fixed in the latest version of libnotify, 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. Jeremy Bicha (supplier of updated libnotify 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, 17 Jul 2022 16:52:02 +0200 Source: libnotify Built-For-Profiles: noudeb Architecture: source Version: 0.8.1-1 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Jeremy Bicha Closes: 1015006 1015008 Changes: libnotify (0.8.1-1)
Bug#1015006: marked as done (gir1.2-notify-0.7: Upgrade to version 0.8.0-1 breaks at least two packages that use Python)
Your message dated Sun, 17 Jul 2022 15:04:31 +
with message-id
and subject line Bug#1015006: fixed in libnotify 0.8.1-1
has caused the Debian Bug report #1015006,
regarding gir1.2-notify-0.7: Upgrade to version 0.8.0-1 breaks at least two
packages that use Python
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.)
--
1015006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015006
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gir1.2-notify-0.7
Version: 0.8.0-1
Severity: important
X-Debbugs-Cc: edo...@gmail.com
Hi, I have two packages (guake and mate-tweak) which uses Python and after
upgrading gir1.2-notify-0.7 from version 0.7.12-1 to 0.8.0-1 breaks those
packages. Downgrading gir1.2-notife-0.7 and libnotify4 to the previous version
solves the problem.
Both application fails with the Python error message:
guake:
Traceback (most recent call last):
File "/usr/bin/guake", line 33, in
sys.exit(load_entry_point('guake==3.9.0', 'console_scripts', 'guake')())
File "/usr/lib/python3/dist-packages/guake/main.py", line 648, in exec_main
if not main():
File "/usr/lib/python3/dist-packages/guake/main.py", line 487, in main
from guake.guake_app import Guake
File "/usr/lib/python3/dist-packages/guake/guake_app.py", line 49, in
from guake import notifier
File "/usr/lib/python3/dist-packages/guake/notifier.py", line 23, in
gi.require_version("Notify", "0.7")
File "/usr/lib/python3/dist-packages/gi/__init__.py", line 129, in
require_version
raise ValueError('Namespace %s not available for version %s' %
ValueError: Namespace Notify not available for version 0.7
mate-tweak:
Traceback (most recent call last):
File "/usr/bin/mate-tweak", line 56, in
gi.require_version('Notify', '0.7')
File "/usr/lib/python3/dist-packages/gi/__init__.py", line 129, in
require_version
raise ValueError('Namespace %s not available for version %s' %
ValueError: Namespace Notify not available for version 0.7
Greets
Ernesto
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.18.0-2-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 gir1.2-notify-0.7 depends on:
ii gir1.2-gdkpixbuf-2.0 2.42.8+dfsg-1
ii gir1.2-glib-2.0 1.72.0-1+b1
ii libnotify40.8.0-1
gir1.2-notify-0.7 recommends no packages.
gir1.2-notify-0.7 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libnotify
Source-Version: 0.8.1-1
Done: Jeremy Bicha
We believe that the bug you reported is fixed in the latest version of
libnotify, 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.
Jeremy Bicha (supplier of updated libnotify 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, 17 Jul 2022 16:52:02 +0200
Source: libnotify
Built-For-Profiles: noudeb
Architecture: source
Version: 0.8.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers
Changed-By: Jeremy Bicha
Closes: 1015006 1015008
Changes:
libnotify (0.8.1-1) unstable; urgency=medium
.
* New upstream release (Closes: #1015006, #1015008)
Checksums-Sha1:
7b766a833204606b6f0071b379f98958b865ba25 2606 libnotify_0.8.1-1.dsc
fe72d5a2184aa30f79fe31e6124ed5c2d83b87b6 105368 libnotify_0.8.1.orig.tar.xz
0d14e95d731c654e42ffef6324558be5336b537f 9900 libnotify_0.8.1-1.debian.tar.xz
0b36b1ce912dc31437067b014cf839f6fe4ffcd9 16353
libnotify_0.8.1-1_source.buildinfo
Checksums-Sha256:
53f1cd144c9be3ce3b64fa0073100f0857b64739399cbf21d2cf3cbd57bea7da 2606
libnotify_0.8.1-1.dsc
d033e6d4d6ccbf46a436c31628a4b661b36dca1f5d4174fe0173e274f4e62557 105368
libnotify_0.8.1.orig.tar.xz
0178ec7e19553fc5ac0cd829e1c6e75f8354b1708fd7966ad0798467499bf65a 9900
libnotify_0.8.1-1.debian.tar.xz
Bug#1015011: Upgrading to severity serious
Hi, I did a mistake and uploaded to Unstable instead of Experimental. The result is that this bug becomes a serious one. bmtk is, with Sahara, the only package that still has issues with the new version. Please get it fixed ASAP. FYI, I'm also looking at the issue, but didn't find a fix yet. If you do, please ping me, as your issue looks the same as the one in Sahara. Cheers, Thomas Goirand (zigo)
Processed: Bug#1015008 marked as pending in libnotify
Processing control commands: > tag -1 pending Bug #1015008 [src:libnotify] gnome-tweaks: gir1.2-notify-0.7 breaks startup of gnome-tweaks Added tag(s) pending. -- 1015008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015008 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015008: marked as pending in libnotify
Control: tag -1 pending Hello, Bug #1015008 in libnotify 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/libnotify/-/commit/7c3d7b89600be1b1c4e0755a7736c21689a8ff5d New upstream release Closes: #1015008 (this message was generated automatically) -- Greetings https://bugs.debian.org/1015008
Processed: severity 1015011 serious
Processing commands for cont...@bugs.debian.org: > severity 1015011 serious Bug #1015011 [src:bmtk] autopkgtest fail with python3-jsonschema 4.6.0 Severity set to 'serious' from 'important' > End of message, stopping processing here. Please contact me if you need assistance. -- 1015011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015011 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#914935: enca: diff for NMU version 1.19-1.1
Control: tags 914935 + pending
Dear maintainer,
I've prepared an NMU for enca (versioned as 1.19-1.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru enca-1.19/debian/changelog enca-1.19/debian/changelog
--- enca-1.19/debian/changelog 2016-09-05 16:23:32.0 +0200
+++ enca-1.19/debian/changelog 2022-07-17 16:35:46.0 +0200
@@ -1,3 +1,14 @@
+enca (1.19-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+
+ [ Andreas Henriksson ]
+ * Pass MKTEMP_PROG=/bin/mktemp to configure instead of finding in PATH
+- this fixes reproducible build issue on merged-usr vs non-merged.
+(Closes: #914935)
+
+ -- Ansgar Sun, 17 Jul 2022 16:35:46 +0200
+
enca (1.19-1) unstable; urgency=medium
* New upstream release.
diff -Nru enca-1.19/debian/rules enca-1.19/debian/rules
--- enca-1.19/debian/rules 2016-01-07 09:27:18.0 +0100
+++ enca-1.19/debian/rules 2022-07-17 16:35:40.0 +0200
@@ -5,7 +5,8 @@
--libexecdir=\$${prefix}/lib \
--with-librecode \
--with-libiconv \
- --disable-rpath
+ --disable-rpath \
+ MKTEMP_PROG=/bin/mktemp
override_dh_strip:
dh_strip --dbg-package=libenca-dbg
Processed: enca: diff for NMU version 1.19-1.1
Processing control commands: > tags 914935 + pending Bug #914935 [enca] enca: reproducible build (usrmerge): Embeds full path to mktemp found via PATH Added tag(s) pending. -- 914935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015008: gnome-tweaks: gir1.2-notify-0.7 breaks startup of gnome-tweaks
Thanks for the quick fix on the weekend. I believe the only thing we need to do on the Debian side is package the new version so I'll do that now. Jeremy On Sun, Jul 17, 2022 at 3:08 PM Marco Trevisan wrote: > > Ok, > > That's fixed in 0.8.1 now, please can you handle the debian side? > > Thanks
Processed: Re: Bug#915850: rsnapshot: reproducible build (usrmerge): embeds path of tool found via PATH
Processing control commands: > tags -1 pending Bug #915850 [rsnapshot] rsnapshot: reproducible build (usrmerge): embeds path of tool found via PATH Added tag(s) pending. -- 915850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915850 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#915850: rsnapshot: reproducible build (usrmerge): embeds path of tool found via PATH
Control: tags -1 pending Simon, Thanks for this. On Sun, Jul 17, 2022 at 01:15:42PM +0100, Simon McVittie wrote: > Control: reopen -1 > Control: severity -1 serious > > On Fri, 24 Jun 2022 at 13:12:07 +, Debian Bug Tracking System forwarded: > > * d/rules: specify PATH for build so unmerged usr paths are discovered > > first (Closes: #915850). > > Sorry, this does not solve the problem. More precisely, it solves the > problem as originally reported (for cp, rm, lvcreate, etc.), but also > causes the opposite problem for tools that are canonically in /usr/bin > (rsync, ssh, logger, du, perl). Yes, I had realised this and have already queued the patch that was originally suggested. Mark
Bug#1015193: kata-containers: FTBFS: kata-containers/src/runtime/virtcontainers/pkg/agent/protocols/client/client.go:362:26: not enough arguments in call to vsock.Dial
Source: kata-containers Version: 2.4.0~alpha0+ds1-1 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, kata-containers recently started to FTBFS after some (transitive) build-dependency got upgraded. ... github.com/opencontainers/runc/libcontainer/cgroups/fs github.com/kata-containers/kata-containers/src/runtime/virtcontainers/pkg/agent/protocols/client # github.com/kata-containers/kata-containers/src/runtime/virtcontainers/pkg/agent/protocols/client src/github.com/kata-containers/kata-containers/src/runtime/virtcontainers/pkg/agent/protocols/client/client.go:362:26: not enough arguments in call to vsock.Dial have (uint32, uint32) want (uint32, uint32, *vsock.Config) github.com/cilium/ebpf/internal/unix golang.org/x/net/context/ctxhttp ... Andreas kata-containers_2.4.0~alpha0+ds1-1.log.gz Description: application/gzip
Bug#1015008: gnome-tweaks: gir1.2-notify-0.7 breaks startup of gnome-tweaks
Ok, That's fixed in 0.8.1 now, please can you handle the debian side? Thanks On lug 17 2022, at 2:51 pm, Jeremy Bicha wrote: > On Sun, Jul 17, 2022 at 2:49 PM Marco Trevisan > wrote: >> Mmh, there are no ABI/API breaks afaik, so there was no need to change >> package name > > Marco, see the comments at > https://gitlab.gnome.org/GNOME/libnotify/-/issues/27 > > Thank you, > Jeremy Bicha >
Bug#1008450: marked as done (snapd: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 1 -pkgdir=/<>/_build/std -buildmode=pie -tags nosecboot github.com/snapcore/snapd/... g
Your message dated Sun, 17 Jul 2022 13:05:56 + with message-id and subject line Bug#1008450: fixed in snapd 2.54.3-1.1 has caused the Debian Bug report #1008450, regarding snapd: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 1 -pkgdir=/<>/_build/std -buildmode=pie -tags nosecboot github.com/snapcore/snapd/... github.com/snapcore/snapd/advisor github.com/snapcore/snapd/arch github.com/snapcore/snapd/asserts [...] github.com/snapcore/snapd/usersession/userd/ui github.com/snapcore/snapd/usersession/xdgopenproxy github.com/snapcore/snapd/wrappers github.com/snapcore/snapd/x11 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.) -- 1008450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008450 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: snapd Version: 2.54.3-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > GO111MODULE=off dh_auto_test -- -pkgdir=/<>/_build/std > -buildmode=pie -tags "nosecboot" github.com/snapcore/snapd/... > dh_auto_test: warning: Compatibility levels before 10 are deprecated (level 9 > in use) > cd _build && go test -vet=off -v -p 1 > -pkgdir=/<>/_build/std -buildmode=pie -tags nosecboot > github.com/snapcore/snapd/... github.com/snapcore/snapd/advisor > github.com/snapcore/snapd/arch github.com/snapcore/snapd/asserts > github.com/snapcore/snapd/asserts/assertstest > github.com/snapcore/snapd/asserts/internal > github.com/snapcore/snapd/asserts/signtool > github.com/snapcore/snapd/asserts/snapasserts > github.com/snapcore/snapd/asserts/sysdb > github.com/snapcore/snapd/asserts/systestkeys github.com/snapcore/snapd/boot > github.com/snapcore/snapd/boot/boottest github.com/snapcore/snapd/bootloader > github.com/snapcore/snapd/bootloader/androidbootenv > github.com/snapcore/snapd/bootloader/assets > github.com/snapcore/snapd/bootloader/assets/genasset > github.com/snapcore/snapd/bootloader/bootloadertest > github.com/snapcore/snapd/bootloader/efi > github.com/snapcore/snapd/bootloader/grubenv > github.com/snapcore/snapd/bootloader/lkenv > github.com/snapcore/snapd/bootloader/ubootenv > github.com/snapcore/snapd/client github.com/snapcore/snapd/client/clientutil > github.com/snapcore/snapd/cmd/snap github.com/snapcore/snapd/cmd/snap-exec > github.com/snapcore/snapd/cmd/snap-failure > github.com/snapcore/snapd/cmd/snap-preseed > github.com/snapcore/snapd/cmd/snap-recovery-chooser > github.com/snapcore/snapd/cmd/snap-repair > github.com/snapcore/snapd/cmd/snap-seccomp > github.com/snapcore/snapd/cmd/snap-seccomp/syscalls > github.com/snapcore/snapd/cmd/snap-update-ns > github.com/snapcore/snapd/cmd/snapctl github.com/snapcore/snapd/cmd/snapd > github.com/snapcore/snapd/cmd/snaplock > github.com/snapcore/snapd/cmd/snaplock/runinhibit > github.com/snapcore/snapd/daemon github.com/snapcore/snapd/dbusutil > github.com/snapcore/snapd/dbusutil/dbustest > github.com/snapcore/snapd/dbusutil/netplantest > github.com/snapcore/snapd/desktop/notification > github.com/snapcore/snapd/desktop/notification/notificationtest > github.com/snapcore/snapd/desktop/portal github.com/snapcore/snapd/dirs > github.com/snapcore/snapd/docs github.com/snapcore/snapd/errtracker > github.com/snapcore/snapd/features github.com/snapcore/snapd/gadget > github.com/snapcore/snapd/gadget/edition > github.com/snapcore/snapd/gadget/gadgettest > github.com/snapcore/snapd/gadget/install > github.com/snapcore/snapd/gadget/quantity github.com/snapcore/snapd/httputil > github.com/snapcore/snapd/i18n github.com/snapcore/snapd/i18n/xgettext-go > github.com/snapcore/snapd/image github.com/snapcore/snapd/interfaces > github.com/snapcore/snapd/interfaces/apparmor > github.com/snapcore/snapd/interfaces/backends > github.com/snapcore/snapd/interfaces/builtin > github.com/snapcore/snapd/interfaces/dbus > github.com/snapcore/snapd/interfaces/hotplug > github.com/snapcore/snapd/interfaces/ifacetest > github.com/snapcore/snapd/interfaces/kmod > github.com/snapcore/snapd/interfaces/mount > github.com/snapcore/snapd/interfaces/policy > github.com/snapcore/snapd/interfaces/polkit > github.com/snapcore/snapd/interfaces/seccomp > github.com/snapcore/snapd/interfaces/systemd > github.com/snapcore/snapd/interfaces/udev > github.com/snapcore/snapd/interfaces/utils
Bug#1015008: gnome-tweaks: gir1.2-notify-0.7 breaks startup of gnome-tweaks
On Sun, Jul 17, 2022 at 2:49 PM Marco Trevisan wrote: > Mmh, there are no ABI/API breaks afaik, so there was no need to change > package name Marco, see the comments at https://gitlab.gnome.org/GNOME/libnotify/-/issues/27 Thank you, Jeremy Bicha
Bug#1015008: gnome-tweaks: gir1.2-notify-0.7 breaks startup of gnome-tweaks
Mmh, there are no ABI/API breaks afaik, so there was no need to change package name On lug 16 2022, at 11:11 am, Jeremy Bicha wrote: Control: reassign -1 src:libnotify Control: severity -1 serious Control: affects -1 src:gnome-tweaks src:comfy src:gnome-gmail src:isenkram On Sat, Jul 16, 2022 at 9:09 AM alain wrote: > > Package: gnome-tweaks > Version: 42~beta-1 > Severity: important > Tags: d-i > X-Debbugs-Cc: compte.perso.de-al...@bbox.fr > > alain@sid:~$ apt-cache madison gir1.2-notify-0.7 > gir1.2-notify-0.7 | 0.8.0-1 | http://deb.debian.org/debian unstable/main > amd64 Packages > gir1.2-notify-0.7 | 0.7.12-1 | http://deb.debian.org/debian bookworm/main > amd64 Packages > gir1.2-notify-0.7 | 0.7.12-1 | http://deb.debian.org/debian testing/main > amd64 Packages > libnotify | 0.7.12-1 | http://deb.debian.org/debian bookworm/main Sources > > the 0.8.0-1 version of gir1.2-notify-0.7 (sid) breaks the startup of gnome > tweaks. > to solve this problem, i had to downgrade this package. > > alain@sid:~$ dpkg -l gnome-tweaks gir1.2-notify-0.7 > Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder > | État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi- > installé/W=attend-traitement-déclenchements > |/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais) > ||/ Nom Version Architecture Description > +++-===---== > hi gir1.2-notify-0.7:amd64 0.7.12-1 amd64 sends desktop > notifications to a notification daemon (Introspection files) > ii gnome-tweaks 42~beta-1 all tool to adjust advanced > configuration settings for GNOME > > also i made an apt-mark hold on this package to prevent upgrade. > > friendly, > respectfully, > alain. > > > > > -- System Information: > Debian Release: bookworm/sid > APT prefers unstable > APT policy: (500, 'unstable'), (100, 'testing'), (1, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 5.18.0-2-amd64 (SMP w/24 CPU threads; PREEMPT) > Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), > LANGUAGE not set > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages gnome-tweaks depends on: > ii dconf-gsettings-backend [gsettings-backend] 0.40.0-3 > ii gir1.2-glib-2.0 1.72.0-1+b1 > ii gir1.2-gnomedesktop-3.0 42.3-1 > ii gir1.2-gtk-3.0 3.24.34-1 > ii gir1.2-handy-1 1.6.2-1 > hi gir1.2-notify-0.7 0.7.12-1 > ii gir1.2-pango-1.0 1.50.7+ds-1 > ii gir1.2-soup-2.4 2.74.2-3 > ii gnome-settings-daemon 42.2-1 > ii gnome-shell-common 42.2-1 > ii gnome-shell-extension-prefs 42.2-1 > ii gsettings-desktop-schemas 42.0-1 > ii mutter-common 42.2-1 > ii python3 3.10.4-1+b1 > ii python3-gi 3.42.1-1 Thank you for taking the time to report this bug. I am going to check with the libnotify maintainer to see if the version number change was intentional. I think we would need to rename gir1.2-notify-0.7 if this change is kept. Thank you, Jeremy Bicha On lug 16 2022, at 11:11 am, Jeremy Bicha wrote: > Control: reassign -1 src:libnotify > Control: severity -1 serious > Control: affects -1 src:gnome-tweaks src:comfy src:gnome-gmail src:isenkram > > On Sat, Jul 16, 2022 at 9:09 AM alain wrote: >> >> Package: gnome-tweaks >> Version: 42~beta-1 >> Severity: important >> Tags: d-i >> X-Debbugs-Cc: compte.perso.de-al...@bbox.fr >> >> alain@sid:~$ apt-cache madison gir1.2-notify-0.7 >> gir1.2-notify-0.7 |0.8.0-1 | http://deb.debian.org/debian unstable/main >> amd64 Packages >> gir1.2-notify-0.7 | 0.7.12-1 | http://deb.debian.org/debian bookworm/main >> amd64 Packages >> gir1.2-notify-0.7 | 0.7.12-1 | http://deb.debian.org/debian testing/main >> amd64 Packages >> libnotify | 0.7.12-1 | http://deb.debian.org/debian bookworm/main Sources >> >> the 0.8.0-1 version of gir1.2-notify-0.7 (sid) breaks the startup of gnome >> tweaks. >> to solve this problem, i had to downgrade this package. >> >> alain@sid:~$ dpkg -l gnome-tweaks gir1.2-notify-0.7 >> Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder >> | État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi- >> installé/W=attend-traitement-déclenchements >> |/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais) >> ||/ Nom Version Architecture Description >> +++-===---== >> hi gir1.2-notify-0.7:amd64 0.7.12-1 amd64sends desktop >> notifications to a notification daemon (Introspection files) >> ii gnome-tweaks42~beta-1all tool to adjust advanced >> configuration settings for GNOME >> >> also i made an apt-mark hold on this package to prevent upgrade. >> >> friendly, >> respectfully, >> alain. >> >> >> >> >> --
Processed: Re: Bug#983303: imagemagick: reproducible builds: Embeds different paths on usrmerge system
Processing control commands: > severity -1 serious Bug #983303 [src:imagemagick] imagemagick: reproducible builds: Embeds different paths on usrmerge system Severity set to 'serious' from 'normal' -- 983303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983303 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015191: vice: FTBFS against ffmpeg 5
Package: vice Version: 3.6.1+dfsg-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, vice FTBFS against ffmpeg 5: cc -DHAVE_CONFIG_H -I. -I../../src -I../../src/systemheaderoverride -DNDEBUG -I../../src/arch/shared -I../../src -I../../src -I../../src/sounddrv -I/usr/include/x86_64-linux-gnu -I/usr/include/x86_64-linux-gnu -I../../src/arch/gtk3 -I../../src/arch -Wdate-ti me -D_FORTIFY_SOURCE=2 -g -O3 -W -Wall -Wextra -Wformat -Wformat-signedness -Wshadow -Wpointer-arith -Wmissing-prototypes -Wstrict-prototypes -Wuninitialized -Wunreachable-code -Werror=implicit-function-declaration -Wfatal-errors -Wdiscarded-qualifiers -Wno-s ign-compare -Wno-missing-field-initializers -Wno-ignored-qualifiers -Wno-unused-parameter -fopenmp -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -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/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz -I/usr/include/atk-1.0 -I/usr/include/cairo -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/libmount -I/usr/include/blkid -I/usr/include /glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -g -O2 -ffile-prefix-map=/build/vice-3.6.1+dfsg=. -fstack-protector-strong -Wformat -Werror=format-security -MT ffmpeglib.o -MD -MP -MF .deps/ffmpeglib.Tpo -c -o ffmpeglib.o ffmpeglib.c In file included from ffmpegdrv.c:42: ffmpeglib.h:89:31: error: unknown type name 'AVCodecContext'; did you mean 'AVIODirContext'? 89 | typedef int(*avcodec_open2_t)(AVCodecContext*, AVCodec*, AVDictionary **); | ^~ | AVIODirContext compilation terminated due to -Wfatal-errors. make[4]: *** [Makefile:544: ffmpegdrv.o] Error 1 Andreas vice_3.6.1+dfsg-2.log.gz Description: application/gzip
Processed: Re: Bug#915955: vm: may embed undesired paths when built in local environment
Processing control commands: > severity -1 serious Bug #915955 [vm] vm: may embed undesired paths when built in local environment Severity set to 'serious' from 'normal' -- 915955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#992651: sharutils: stores wrong path to bash if built on merged-/usr system
Processing control commands: > severity -1 serious Bug #992651 [src:sharutils] sharutils: stores wrong path to bash if built on merged-/usr system Severity set to 'serious' from 'important' -- 992651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992651 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#915850: rsnapshot: reproducible build (usrmerge): embeds path of tool found via PATH
Processing control commands:
> reopen -1
Bug #915850 {Done: Mark Hindley } [rsnapshot] rsnapshot:
reproducible build (usrmerge): embeds path of tool found via PATH
'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 rsnapshot/1.4.4-2.
> severity -1 serious
Bug #915850 [rsnapshot] rsnapshot: reproducible build (usrmerge): embeds path
of tool found via PATH
Severity set to 'serious' from 'normal'
--
915850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915850
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1015089: psmisc: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
On Sun, 17 Jul 2022 at 21:12, Craig Small wrote: > Why, after 10 years, has the mass-rebuild triggered it? > Because after even more years of printing a useless warning Dejagnu now makes it an error[1]. - Craig 1: https://git.savannah.gnu.org/gitweb/?p=dejagnu.git;a=commit;h=660af948c8fce93ad2781ab8e0527a5b8e216f14
Bug#1015089: marked as done (psmisc: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2)
Your message dated Sun, 17 Jul 2022 12:04:17 + with message-id and subject line Bug#1015089: fixed in psmisc 23.5-2 has caused the Debian Bug report #1015089, regarding psmisc: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" 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.) -- 1015089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015089 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: psmisc Version: 23.5-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 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 '/<>/testsuite' > Making a new site.exp file ... > srcdir='.'; export srcdir; \ > EXPECT=expect; export EXPECT; \ > if /bin/bash -c "runtest --version" > /dev/null 2>&1; then \ > exit_status=0; l='killall pslog fuser'; for tool in $l; do \ > if runtest --tool $tool --srcdir $srcdir ; \ > then :; else exit_status=1; fi; \ > done; \ > else echo "WARNING: could not find 'runtest'" 1>&2; :;\ > fi; \ > exit $exit_status > ERROR: global config file ../testsuite/global-conf.exp not found. > ERROR: global config file ../testsuite/global-conf.exp not found. > ERROR: global config file ../testsuite/global-conf.exp not found. > make[4]: *** [Makefile:314: check-DEJAGNU] Error 1 > make[4]: Leaving directory '/<>/testsuite' > make[3]: *** [Makefile:388: check-am] Error 2 > make[3]: Leaving directory '/<>/testsuite' > make[2]: *** [Makefile:657: check-recursive] Error 1 > make[2]: Leaving directory '/<>' > make[1]: *** [Makefile:957: check] Error 2 > make[1]: Leaving directory '/<>' > dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 > returned exit code 2 The full build log is available from: http://qa-logs.debian.net/2022/07/16/psmisc_23.5-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220716=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 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 --- Source: psmisc Source-Version: 23.5-2 Done: Craig Small We believe that the bug you reported is fixed in the latest version of psmisc, 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. Craig Small (supplier of updated psmisc 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, 17 Jul 2022 21:48:01 +1000 Source: psmisc Architecture: source Version: 23.5-2 Distribution: unstable Urgency: medium Maintainer: Craig Small Changed-By: Craig Small Closes: 1015089 Changes: psmisc (23.5-2) unstable; urgency=medium . * Fix DEJAGNU workaround Closes: #1015089 Checksums-Sha1: bee97502bb227bad130ba608c83ac09d0d976600 1864 psmisc_23.5-2.dsc 4183e4b15bc48436d640f44d4b5fd2ffe0150e23 7984 psmisc_23.5-2.debian.tar.xz 7bc4c3fb8d05970826beaead7bd2bd500575e3be 6503 psmisc_23.5-2_amd64.buildinfo Checksums-Sha256: 41950ae2fbaf9841c549a9fd2db26cccf7ac67f809b8292e5bdc0ce7695d6245 1864 psmisc_23.5-2.dsc 70dfed8e60b0b6a51a65d444ab7d08c6e06a8eae1a2f0fffb68d17a8bcc5e3b3 7984 psmisc_23.5-2.debian.tar.xz 2959f9c4fb1ad0f64ed299da651eb0c7969f5c64297d365532f86d515d0c4179 6503 psmisc_23.5-2_amd64.buildinfo Files: 393454e4073699ff8e18bd23dd1ff34f 1864 admin optional psmisc_23.5-2.dsc 34a1b83b1134fbcb75441dc3038bf135 7984 admin optional psmisc_23.5-2.debian.tar.xz cbe0b23a086625dc7e822671136cd589 6503
Processed: Re: Bug#979021: lirc: reproducible builds: Embeds different paths to "modinfo" and "sh"
Processing control commands: > severity -1 serious Bug #979021 [src:lirc] lirc: reproducible builds: Embeds different paths to "modinfo" and "sh" Severity set to 'serious' from 'normal' -- 979021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979021 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015026: fortunes-debian-hints: FTBFS: po4a::chooser: Module loading error: Can't locate Syntax/Keyword/Try.pm in @INC
On Sat, Jul 16, 2022 at 7:30 PM Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. Thanks for all this tedious work! > 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. I can't reproduce this locally or via Salsa CI. See: https://salsa.debian.org/debian/fortunes-debian-hints/-/jobs/3002295 Is this sufficient? A diff would be difficult to generate in both build cases. -- Kartik Mistry | કાર્તિક મિસ્ત્રી kartikm.wordpress.com
Processed: Re: Bug#1003495: gcc-xtensa-lx106: reproducible builds: embeds path to various binaries
Processing control commands: > severity -1 serious Bug #1003495 [src:gcc-xtensa-lx106] gcc-xtensa-lx106: reproducible builds: embeds path to various binaries Severity set to 'serious' from 'normal' -- 1003495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003495 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1000946: gcc-riscv64-unknown-elf: reproducible builds: embeds path to various binaries
Processing control commands: > severity -1 serious Bug #1000946 [src:gcc-riscv64-unknown-elf] gcc-riscv64-unknown-elf: reproducible builds: embeds path to various binaries Severity set to 'serious' from 'normal' -- 1000946: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000946 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#914935: enca: reproducible build (usrmerge): Embeds full path to mktemp found via PATH
Processing control commands: > severity -1 serious Bug #914935 [enca] enca: reproducible build (usrmerge): Embeds full path to mktemp found via PATH Severity set to 'serious' from 'normal' -- 914935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1015089 marked as pending in psmisc
Processing control commands: > tag -1 pending Bug #1015089 [src:psmisc] psmisc: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2 Added tag(s) pending. -- 1015089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015089 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015089: marked as pending in psmisc
Control: tag -1 pending Hello, Bug #1015089 in psmisc 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/psmisc/-/commit/89a786ed3def6fd9eae66db45ba89e0907bff88b Fix DEJAGNU workaround Closes: #1015089 (this message was generated automatically) -- Greetings https://bugs.debian.org/1015089
Processed: Re: Bug#992662: cfengine3: stores wrong path to chpasswd, etc. if built on merged-/usr system
Processing control commands: > severity -1 serious Bug #992662 [src:cfengine3] cfengine3: stores wrong path to chpasswd, etc. if built on merged-/usr system Severity set to 'serious' from 'important' -- 992662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992662 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: php8.1: records wrong path to sed when built on a system with /usr/bin/sed
Processing control commands: > block 1001648 by -1 Bug #1001648 [php8.1] php8.1: please make the build (mostly) reproducible 1001648 was not blocked by any bugs. 1001648 was not blocking any bugs. Added blocking bug(s) of 1001648: 1015188 -- 1001648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001648 1015188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015188 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015188: php8.1: records wrong path to sed when built on a system with /usr/bin/sed
Source: php8.1 Version: 8.1.7-1 Severity: serious Justification: TC resolution #994388 Control: block 1001648 by -1 User: reproducible-bui...@lists.alioth.debian.org Usertags: usrmerge When php8.1 is built on a system where /usr/bin/sed exists (such as a system that has undergone the /usr merge), it records SED="/usr/bin/sed" in the php8.1-config and phpize8.1 scripts. The resulting binary package will not work on an unmerged-/usr system, because on such systems, only /bin/sed exists. Technical Committee resolution https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994388#110 recommends that this class of bug is treated as release-critical. I suspect that building php8.1 on a system with a /usr/local/bin/sed would have a similar problem. This is basically the same problem as #913620 in php7.3, and passing SED=/bin/sed as an argument to the configure command is likely to be a correct solution. smcv
Bug#1015089: psmisc: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
On Sun, 17 Jul 2022 at 00:03, Lucas Nussbaum wrote: > > ERROR: global config file ../testsuite/global-conf.exp not found. > > ERROR: global config file ../testsuite/global-conf.exp not found. > > ERROR: global config file ../testsuite/global-conf.exp not found. > This bug is curious for a few reasons. Why, after 10 years, has the mass-rebuild triggered it? I first thought there was something wrong with the rebuilder; surely something that has built fine since it was put in 2012 can't be at fault? I can't say why this particular build triggered it, but there is a bug in psmisc. I was comparing the psmisc and procps build systems to see why one is fine, and one is not; which brought to my attention a commit in procps in 2013[1], which removed global-conf.exp from the distribution and replaced it with /dev/null. This showed me that you either need to a) distribute the referenced file or b) use something always there, such as /dev/null. psmisc does neither of these as the configure.ac references global-conf.exp[2] It's a pretty simple change, don't use global-conf.exp but use /dev/null instead. I've got that for upstream[3] so next is the Debian package. - Craig 1: https://gitlab.com/procps-ng/procps/-/commit/f0b7271810bc7ad7c7cb15cd590d954907c8c4f4 2: https://gitlab.com/psmisc/psmisc/-/blob/c51c6fafeb01a95d1e01e5c3a3369ee8063b7384/configure.ac#L207 3: https://gitlab.com/psmisc/psmisc/-/commit/3fac667430341bdcec733da6eacd88b03813467a
Bug#997541: marked as done (oldsys-preseed: FTBFS: Running test misc/hostname... ./do-test: line 17: tempfile: command not found)
Your message dated Sun, 17 Jul 2022 11:18:49 + with message-id and subject line Bug#997541: fixed in oldsys-preseed 3.23 has caused the Debian Bug report #997541, regarding oldsys-preseed: FTBFS: Running test misc/hostname... ./do-test: line 17: tempfile: command not found to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 997541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997541 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: oldsys-preseed Version: 3.22 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > cd tests && ./runtests > Running test arm/dns323-dhcp... ./do-test: line 17: tempfile: command not > found > diff: missing operand after 'arm/dns323-dhcp.preseed' > diff: Try 'diff --help' for more information. > ./runtests: line 10: d-i: command not found > not ok > Running test arm/dns323-static... ./do-test: line 17: tempfile: command not > found > diff: missing operand after 'arm/dns323-static.preseed' > diff: Try 'diff --help' for more information. > ./runtests: line 10: d-i: command not found > not ok > Running test arm/kuroboxpro_dhcp... ./do-test: line 17: tempfile: command not > found > diff: missing operand after 'arm/kuroboxpro_dhcp.preseed' > diff: Try 'diff --help' for more information. > ./runtests: line 10: d-i: command not found > not ok > Running test arm/kuroboxpro_static... ./do-test: line 17: tempfile: command > not found > diff: missing operand after 'arm/kuroboxpro_static.preseed' > diff: Try 'diff --help' for more information. > ./runtests: line 10: d-i: command not found > not ok > Running test arm/lspro_dhcp... ./do-test: line 17: tempfile: command not found > diff: missing operand after 'arm/lspro_dhcp.preseed' > diff: Try 'diff --help' for more information. > ./runtests: line 10: d-i: command not found > not ok > Running test arm/lspro_static... ./do-test: line 17: tempfile: command not > found > diff: missing operand after 'arm/lspro_static.preseed' > diff: Try 'diff --help' for more information. > ./runtests: line 10: d-i: command not found > not ok > Running test arm/mv2120_dhcp... ./do-test: line 17: tempfile: command not > found > diff: missing operand after 'arm/mv2120_dhcp.preseed' > diff: Try 'diff --help' for more information. > ./runtests: line 10: d-i: command not found > not ok > Running test arm/mv2120_static... ./do-test: line 17: tempfile: command not > found > diff: missing operand after 'arm/mv2120_static.preseed' > diff: Try 'diff --help' for more information. > ./runtests: line 10: d-i: command not found > not ok > Running test arm/nslu2... ./do-test: line 17: tempfile: command not found > diff: missing operand after 'arm/nslu2.preseed' > diff: Try 'diff --help' for more information. > ./runtests: line 10: d-i: command not found > not ok > Running test arm/nslu2_invalid_hostname... ./do-test: line 17: tempfile: > command not found > diff: missing operand after 'arm/nslu2_invalid_hostname.preseed' > diff: Try 'diff --help' for more information. > ./runtests: line 10: d-i: command not found > not ok > Running test arm/nslu2_static... ./do-test: line 17: tempfile: command not > found > diff: missing operand after 'arm/nslu2_static.preseed' > diff: Try 'diff --help' for more information. > ./runtests: line 10: d-i: command not found > not ok > Running test arm/nslu2_static_no_dns... ./do-test: line 17: tempfile: command > not found > diff: missing operand after 'arm/nslu2_static_no_dns.preseed' > diff: Try 'diff --help' for more information. > ./runtests: line 10: d-i: command not found > not ok > Running test arm/nslu2_static_no_gw... ./do-test: line 17: tempfile: command > not found > diff: missing operand after 'arm/nslu2_static_no_gw.preseed' > diff: Try 'diff --help' for more information. > ./runtests: line 10: d-i: command not found > not ok > Running test arm/nslu2_static_no_ip... ./do-test: line 17: tempfile: command > not found > diff: missing operand after 'arm/nslu2_static_no_ip.preseed' > diff: Try 'diff --help' for more information. > ./runtests: line 10: d-i: command not found > not ok > Running test arm/nslu2_uninitialized... ./do-test: line 17: tempfile: command > not found > diff: missing operand after 'arm/nslu2_uninitialized.preseed' > diff: Try 'diff --help' for more information. > ./runtests: line 10: d-i: command not found > not ok > Running test arm/qnap_dhcp...
Bug#1015127: marked as done (pytest-arraydiff: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)
Your message dated Sun, 17 Jul 2022 11:18:54 + with message-id and subject line Bug#1015127: fixed in pytest-arraydiff 0.5.0-2 has caused the Debian Bug report #1015127, regarding pytest-arraydiff: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 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.) -- 1015127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015127 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pytest-arraydiff Version: 0.5.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > fakeroot debian/rules clean > dh clean --with python3 --buildsystem=pybuild >dh_auto_clean -O--buildsystem=pybuild > I: pybuild base:239: python3.9 setup.py clean > running clean > removing '/<>/.pybuild/cpython3_3.9/build' (and everything under > it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.9' does not exist -- can't clean it > I: pybuild base:239: python3.10 setup.py clean > running clean > removing '/<>/.pybuild/cpython3_3.10/build' (and everything > under it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.10' does not exist -- can't clean it >dh_autoreconf_clean -O--buildsystem=pybuild >dh_clean -O--buildsystem=pybuild > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building pytest-arraydiff using existing > ./pytest-arraydiff_0.5.0.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: local changes detected, the modified files are: > pytest-arraydiff-0.5.0/pytest_arraydiff/version.py > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/pytest-arraydiff_0.5.0-1.diff.2jIgaq > dpkg-source: info: Hint: make sure the version in debian/changelog matches > the unpacked source tree > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 > > Build finished at 2022-07-16T06:06:07Z The full build log is available from: http://qa-logs.debian.net/2022/07/16/pytest-arraydiff_0.5.0-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220716=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 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 --- Source: pytest-arraydiff Source-Version: 0.5.0-2 Done: Ole Streicher We believe that the bug you reported is fixed in the latest version of pytest-arraydiff, 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. Ole Streicher (supplier of updated pytest-arraydiff 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, 17 Jul 2022 12:57:03 +0200 Source: pytest-arraydiff Architecture: source Version: 0.5.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Ole Streicher Closes: 1015127 Changes: pytest-arraydiff (0.5.0-2) unstable; urgency=medium . * Add version.py to d/clean (Closes: #1015127) * Push Standards-Version to 4.6.1. No changes needed Checksums-Sha1: 7ae7d18753645ca8e3af086682babb9116b21a77 2183 pytest-arraydiff_0.5.0-2.dsc
Bug#1015115: marked as done (parfive: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)
Your message dated Sun, 17 Jul 2022 11:04:13 + with message-id and subject line Bug#1015115: fixed in parfive 1.5.1-2 has caused the Debian Bug report #1015115, regarding parfive: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 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.) -- 1015115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015115 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: parfive Version: 1.5.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules clean > dh clean --with python3,sphinxdoc --buildsystem=pybuild >dh_auto_clean -O--buildsystem=pybuild > I: pybuild base:239: python3.9 setup.py clean > running clean > removing '/<>/.pybuild/cpython3_3.9_parfive/build' (and > everything under it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.9' does not exist -- can't clean it > I: pybuild base:239: python3.10 setup.py clean > running clean > removing '/<>/.pybuild/cpython3_3.10_parfive/build' (and > everything under it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.10' does not exist -- can't clean it >dh_autoreconf_clean -O--buildsystem=pybuild >dh_clean -O--buildsystem=pybuild > dpkg-source -b . > dpkg-source: info: using options from parfive-1.5.1/debian/source/options: > --extend-diff-ignore=^[^/]+.egg-info/ > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building parfive using existing ./parfive_1.5.1.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: local changes detected, the modified files are: > parfive-1.5.1/parfive/_version.py > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/parfive_1.5.1-1.diff.pQcU51 > dpkg-source: info: Hint: make sure the version in debian/changelog matches > the unpacked source tree > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 > > Build finished at 2022-07-16T06:02:51Z The full build log is available from: http://qa-logs.debian.net/2022/07/16/parfive_1.5.1-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220716=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 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 --- Source: parfive Source-Version: 1.5.1-2 Done: Ole Streicher We believe that the bug you reported is fixed in the latest version of parfive, 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. Ole Streicher (supplier of updated parfive 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, 17 Jul 2022 12:46:56 +0200 Source: parfive Architecture: source Version: 1.5.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Ole Streicher Closes: 1015115 Changes: parfive (1.5.1-2) unstable; urgency=medium . * Add version.py to d/clean (Closes: #1015115) * Push Standards-Version to 4.6.1. No changes needed Checksums-Sha1: 605310f13f8cc6149475a7e3d7c71133e7a9dc21 2317 parfive_1.5.1-2.dsc
Processed: Re: Bug#1006471: ruby3.0: reproducible builds: embeds path to various binaries
Processing control commands: > severity -1 serious Bug #1006471 [src:ruby3.0] ruby3.0: reproducible builds: embeds path to various binaries Severity set to 'serious' from 'normal' -- 1006471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006471 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015127: marked as pending in pytest-arraydiff
Control: tag -1 pending Hello, Bug #1015127 in pytest-arraydiff reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/pytest-arraydiff/-/commit/05fbbb107ea742b0f5896842a92c20c3c6bf598d Add version.py to d/clean Closes: #1015127 (this message was generated automatically) -- Greetings https://bugs.debian.org/1015127
Processed: Bug#1015127 marked as pending in pytest-arraydiff
Processing control commands: > tag -1 pending Bug #1015127 [src:pytest-arraydiff] pytest-arraydiff: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 Added tag(s) pending. -- 1015127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015127 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#977684: mahimahi: reproducible builds: Embeds paths to iptables and ip in binaries
Processing control commands: > severity -1 serious Bug #977684 [src:mahimahi] mahimahi: reproducible builds: Embeds paths to iptables and ip in binaries Severity set to 'serious' from 'normal' -- 977684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977684 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1015115 marked as pending in parfive
Processing control commands: > tag -1 pending Bug #1015115 [src:parfive] parfive: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 Added tag(s) pending. -- 1015115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015115 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015115: marked as pending in parfive
Control: tag -1 pending Hello, Bug #1015115 in parfive reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/parfive/-/commit/d0aa67418798eb1b56bd2d9a66a7c5d01881a2fc Add version.py to d/clean Closes: #1015115 (this message was generated automatically) -- Greetings https://bugs.debian.org/1015115
Bug#1015131: marked as done (asdf-wcs-schemas: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)
Your message dated Sun, 17 Jul 2022 10:49:05 + with message-id and subject line Bug#1015131: fixed in asdf-wcs-schemas 0.1.1-3 has caused the Debian Bug report #1015131, regarding asdf-wcs-schemas: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 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.) -- 1015131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015131 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: asdf-wcs-schemas Version: 0.1.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules clean > dh clean --with python3 --buildsystem=pybuild >dh_auto_clean -O--buildsystem=pybuild > I: pybuild base:239: python3.9 setup.py clean > running clean > removing '/<>/.pybuild/cpython3_3.9/build' (and everything under > it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.9' does not exist -- can't clean it > I: pybuild base:239: python3.10 setup.py clean > running clean > removing '/<>/.pybuild/cpython3_3.10/build' (and everything > under it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.10' does not exist -- can't clean it >dh_autoreconf_clean -O--buildsystem=pybuild >dh_clean -O--buildsystem=pybuild > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building asdf-wcs-schemas using existing > ./asdf-wcs-schemas_0.1.1.orig.tar.gz > dpkg-source: info: local changes detected, the modified files are: > asdf-wcs-schemas-0.1.1/src/asdf_wcs_schemas/_version.py > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/asdf-wcs-schemas_0.1.1-2.diff.46AjU6 > dpkg-source: info: Hint: make sure the version in debian/changelog matches > the unpacked source tree > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 > > Build finished at 2022-07-16T06:05:58Z The full build log is available from: http://qa-logs.debian.net/2022/07/16/asdf-wcs-schemas_0.1.1-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220716=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 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 --- Source: asdf-wcs-schemas Source-Version: 0.1.1-3 Done: Ole Streicher We believe that the bug you reported is fixed in the latest version of asdf-wcs-schemas, 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. Ole Streicher (supplier of updated asdf-wcs-schemas 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, 17 Jul 2022 12:32:40 +0200 Source: asdf-wcs-schemas Architecture: source Version: 0.1.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Astronomy Team Changed-By: Ole Streicher Closes: 1015131 Changes: asdf-wcs-schemas (0.1.1-3) unstable; urgency=medium . * Add version.py to d/clean (Closes: #1015131) * Push Standards-Version to 4.6.1. No changes needed Checksums-Sha1: 4dbb275fb8e1fba1355fbc09f2c2a5e6253cbe7b 2203 asdf-wcs-schemas_0.1.1-3.dsc 1da2709d7bce6ab6f78429124caa120b3d21d8d4 2540 asdf-wcs-schemas_0.1.1-3.debian.tar.xz
Bug#1015116: marked as done (asdf-standard: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)
Your message dated Sun, 17 Jul 2022 10:48:59 + with message-id and subject line Bug#1015116: fixed in asdf-standard 1.0.2-2 has caused the Debian Bug report #1015116, regarding asdf-standard: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 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.) -- 1015116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015116 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: asdf-standard Version: 1.0.2-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules clean > dh clean --with python3 --buildsystem=pybuild >dh_auto_clean -O--buildsystem=pybuild > I: pybuild base:239: python3.9 setup.py clean > running clean > removing '/<>/.pybuild/cpython3_3.9/build' (and everything under > it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.9' does not exist -- can't clean it > I: pybuild base:239: python3.10 setup.py clean > running clean > removing '/<>/.pybuild/cpython3_3.10/build' (and everything > under it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.10' does not exist -- can't clean it >dh_autoreconf_clean -O--buildsystem=pybuild >dh_clean -O--buildsystem=pybuild > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building asdf-standard using existing > ./asdf-standard_1.0.2.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: local changes detected, the modified files are: > asdf-standard-1.0.2/src/asdf_standard/_version.py > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/asdf-standard_1.0.2-1.diff.gNWR83 > dpkg-source: info: Hint: make sure the version in debian/changelog matches > the unpacked source tree > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 > > Build finished at 2022-07-16T06:05:26Z The full build log is available from: http://qa-logs.debian.net/2022/07/16/asdf-standard_1.0.2-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220716=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 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 --- Source: asdf-standard Source-Version: 1.0.2-2 Done: Ole Streicher We believe that the bug you reported is fixed in the latest version of asdf-standard, 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. Ole Streicher (supplier of updated asdf-standard 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, 17 Jul 2022 12:21:25 +0200 Source: asdf-standard Architecture: source Version: 1.0.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Astronomy Team Changed-By: Ole Streicher Closes: 1015116 Changes: asdf-standard (1.0.2-2) unstable; urgency=medium . [ Debian Janitor ] * debian/copyright: Replace commas with whitespace to separate items . [ Ole Streicher ] * Add version.py to d/clean (Closes: #1015116) * Push Standards-Version to 4.6.1. No changes needed Checksums-Sha1:
Bug#1015082: marked as done (python3-stdlib-extensions: FTBFS: ImportError: cannot import name '_is_python_source_dir' from 'sysconfig' (/usr/lib/python3.11/sysconfig.py))
Your message dated Sun, 17 Jul 2022 10:49:29 +
with message-id
and subject line Bug#1015082: fixed in python3-stdlib-extensions 3.10.5-2
has caused the Debian Bug report #1015082,
regarding python3-stdlib-extensions: FTBFS: ImportError: cannot import name
'_is_python_source_dir' from 'sysconfig' (/usr/lib/python3.11/sysconfig.py)
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.)
--
1015082: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015082
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python3-stdlib-extensions
Version: 3.10.5-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220716 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh_testdir
> ln -sf /usr/lib/libBLT.2.4.so.8.6 3.9/libBLT86.so
> ln -sf /usr/lib/libBLT.2.4.so.8.6 3.9/libBLT86.so.8.6
> cd 3.9 && PYTHONPATH=/<>/3.9/Lib python3.9 setup.py build
> /<>/3.9/setup.py:4: DeprecationWarning: the imp module is
> deprecated in favour of importlib; see the module's documentation for
> alternative uses
> import sys, os, imp, re, optparse
> /<>/3.9/setup.py:787: DeprecationWarning: SO is deprecated, use
> EXT_SUFFIX
> so_ext = sysconfig.get_config_var("SO")
> running build
> running build_ext
> building '_gdbm' extension
> creating build/temp.linux-x86_64-3.9/Modules
> x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g
> -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat
> -Werror=format-security -g -fwrapv -O2 -g -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I.
> -I/usr/include/x86_64-linux-gnu -I/usr/include/python3.9 -c
> Modules/_gdbmmodule.c -o build/temp.linux-x86_64-3.9/Modules/_gdbmmodule.o
> creating build/lib.linux-x86_64-3.9
> x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -g
> -fwrapv -O2 -g -fwrapv -O2 -g -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2
> build/temp.linux-x86_64-3.9/Modules/_gdbmmodule.o -lgdbm -o
> build/lib.linux-x86_64-3.9/_gdbm.cpython-39-x86_64-linux-gnu.so
> building '_tkinter' extension
> x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g
> -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat
> -Werror=format-security -g -fwrapv -O2 -g -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -DWITH_APPINIT=1 -DWITH_BLT=1 -I/usr/include/tcl8.6 -I/usr/X11/include -I.
> -I/usr/include/x86_64-linux-gnu -I/usr/include/python3.9 -c
> Modules/_tkinter.c -o build/temp.linux-x86_64-3.9/Modules/_tkinter.o
> x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g
> -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat
> -Werror=format-security -g -fwrapv -O2 -g -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -DWITH_APPINIT=1 -DWITH_BLT=1 -I/usr/include/tcl8.6 -I/usr/X11/include -I.
> -I/usr/include/x86_64-linux-gnu -I/usr/include/python3.9 -c
> Modules/tkappinit.c -o build/temp.linux-x86_64-3.9/Modules/tkappinit.o
> x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -g
> -fwrapv -O2 -g -fwrapv -O2 -g -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2
> build/temp.linux-x86_64-3.9/Modules/_tkinter.o
> build/temp.linux-x86_64-3.9/Modules/tkappinit.o -L/usr/X11/lib -lBLT -ltk8.6
> -ltcl8.6 -lX11 -o
> build/lib.linux-x86_64-3.9/_tkinter.cpython-39-x86_64-linux-gnu.so
> touch build-stamp-py3.9
> dh_testdir
> ln -sf /usr/lib/libBLT.2.4.so.8.6 3.10/libBLT86.so
> ln -sf /usr/lib/libBLT.2.4.so.8.6 3.10/libBLT86.so.8.6
> cd 3.10 && PYTHONPATH=/<>/3.10/Lib python3.10 setup.py build
> /<>/3.10/setup.py:4: DeprecationWarning: the imp module is
> deprecated in favour of importlib and slated for removal in Python 3.12; see
> the module's documentation for alternative uses
> import sys, os, imp, re, optparse
> /<>/3.10/setup.py:8: DeprecationWarning: The distutils package
> is deprecated and slated for removal in Python 3.12. Use setuptools or check
> PEP 632 for potential alternatives
> from distutils import log
> /<>/3.10/setup.py:850: DeprecationWarning: SO is deprecated, use
> EXT_SUFFIX
> so_ext = sysconfig.get_config_var("SO")
> running build
> running build_ext
> building '_gdbm' extension
> creating build/temp.linux-x86_64-3.10/Modules
>
Bug#1015086: marked as done (asdf-coordinates-schemas: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)
Your message dated Sun, 17 Jul 2022 10:48:54 + with message-id and subject line Bug#1015086: fixed in asdf-coordinates-schemas 0.1.0-3 has caused the Debian Bug report #1015086, regarding asdf-coordinates-schemas: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 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.) -- 1015086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015086 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: asdf-coordinates-schemas Version: 0.1.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules clean > dh clean --with python3 --buildsystem=pybuild >dh_auto_clean -O--buildsystem=pybuild > I: pybuild base:239: python3.9 setup.py clean > running clean > removing '/<>/.pybuild/cpython3_3.9/build' (and everything under > it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.9' does not exist -- can't clean it > I: pybuild base:239: python3.10 setup.py clean > running clean > removing '/<>/.pybuild/cpython3_3.10/build' (and everything > under it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.10' does not exist -- can't clean it >dh_autoreconf_clean -O--buildsystem=pybuild >dh_clean -O--buildsystem=pybuild > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building asdf-coordinates-schemas using existing > ./asdf-coordinates-schemas_0.1.0.orig.tar.gz > dpkg-source: info: local changes detected, the modified files are: > asdf-coordinates-schemas-0.1.0/src/asdf_coordinates_schemas/_version.py > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/asdf-coordinates-schemas_0.1.0-2.diff.sx3TIH > dpkg-source: info: Hint: make sure the version in debian/changelog matches > the unpacked source tree > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 > > Build finished at 2022-07-16T06:05:59Z The full build log is available from: http://qa-logs.debian.net/2022/07/16/asdf-coordinates-schemas_0.1.0-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220716=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 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 --- Source: asdf-coordinates-schemas Source-Version: 0.1.0-3 Done: Ole Streicher We believe that the bug you reported is fixed in the latest version of asdf-coordinates-schemas, 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. Ole Streicher (supplier of updated asdf-coordinates-schemas 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, 17 Jul 2022 12:26:52 +0200 Source: asdf-coordinates-schemas Architecture: source Version: 0.1.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Astronomy Team Changed-By: Ole Streicher Closes: 1015086 Changes: asdf-coordinates-schemas (0.1.0-3) unstable; urgency=medium . * Add version.py to d/clean (Closes: #1015086) * Push Standards-Version to 4.6.1. No changes needed Checksums-Sha1: d786175e4d09c925c1e8338d2ebd1842ddd7f900 2299
Processed: Re: Bug#992645: ncftp: stores wrong path to tar if built on merged-/usr system
Processing control commands: > severity -1 serious Bug #992645 [src:ncftp] ncftp: stores wrong path to tar if built on merged-/usr system Severity set to 'serious' from 'important' -- 992645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992645 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015088: [Pkg-nagios-devel] Bug#1015088: icingadb: FTBFS: ../pkg/com/bulker.go:30:16: internal compiler error: assertion failed
On Sun, Jul 17, 2022 at 06:44:08PM +0800, Shengjing Zhu wrote: > On Sun, Jul 17, 2022 at 6:09 PM Nilesh Patra wrote: > > > > Anthony, Shengjing, > > > > Could you consider taking a look if you have some b/w available? > > > > The issue has already been forwarded to > https://github.com/golang/go/issues/53916 Thanks! -- Regards, Nilesh signature.asc Description: PGP signature
Bug#1015088: [Pkg-nagios-devel] Bug#1015088: icingadb: FTBFS: ../pkg/com/bulker.go:30:16: internal compiler error: assertion failed
On Sun, Jul 17, 2022 at 6:09 PM Nilesh Patra wrote: > > Anthony, Shengjing, > > Could you consider taking a look if you have some b/w available? > The issue has already been forwarded to https://github.com/golang/go/issues/53916 And Sebastiaan already has some progress on the upstream bug. Please just be patient for upstream after the weekend. -- Shengjing Zhu
Bug#1015071: marked as done (pytest-astropy-header: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)
Your message dated Sun, 17 Jul 2022 10:34:30 + with message-id and subject line Bug#1015071: fixed in pytest-astropy-header 0.2.1-2 has caused the Debian Bug report #1015071, regarding pytest-astropy-header: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 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.) -- 1015071: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015071 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pytest-astropy-header Version: 0.2.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > fakeroot debian/rules clean > dh clean --with python3 --buildsystem=pybuild >dh_auto_clean -O--buildsystem=pybuild > I: pybuild base:239: python3.9 setup.py clean > running clean > removing '/<>/.pybuild/cpython3_3.9/build' (and everything under > it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.9' does not exist -- can't clean it > I: pybuild base:239: python3.10 setup.py clean > running clean > removing '/<>/.pybuild/cpython3_3.10/build' (and everything > under it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.10' does not exist -- can't clean it >dh_autoreconf_clean -O--buildsystem=pybuild >dh_clean -O--buildsystem=pybuild > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building pytest-astropy-header using existing > ./pytest-astropy-header_0.2.1.orig.tar.gz > dpkg-source: info: local changes detected, the modified files are: > pytest-astropy-header-0.2.1/pytest_astropy_header/version.py > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/pytest-astropy-header_0.2.1-1.diff.AnCOPH > dpkg-source: info: Hint: make sure the version in debian/changelog matches > the unpacked source tree > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 > > Build finished at 2022-07-16T06:06:19Z The full build log is available from: http://qa-logs.debian.net/2022/07/16/pytest-astropy-header_0.2.1-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220716=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 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 --- Source: pytest-astropy-header Source-Version: 0.2.1-2 Done: Ole Streicher We believe that the bug you reported is fixed in the latest version of pytest-astropy-header, 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. Ole Streicher (supplier of updated pytest-astropy-header 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, 17 Jul 2022 12:10:08 +0200 Source: pytest-astropy-header Architecture: source Version: 0.2.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Astro Team Changed-By: Ole Streicher Closes: 1015071 Changes: pytest-astropy-header (0.2.1-2) unstable; urgency=medium . * Add version.py to d/clean (Closes: #1015071) * Push Standards-Version to 4.6.1. No changes needed Checksums-Sha1: fbf293ad06f0aa0cbf895324e38231acce05e01d 2254 pytest-astropy-header_0.2.1-2.dsc
Bug#1015066: marked as done (asdf-astropy: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)
Your message dated Sun, 17 Jul 2022 10:33:55 + with message-id and subject line Bug#1015066: fixed in asdf-astropy 0.2.1-3 has caused the Debian Bug report #1015066, regarding asdf-astropy: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 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.) -- 1015066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015066 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: asdf-astropy Version: 0.2.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules clean > dh clean --with python3 --buildsystem=pybuild >dh_auto_clean -O--buildsystem=pybuild > I: pybuild base:239: python3.9 setup.py clean > running clean > removing '/<>/.pybuild/cpython3_3.9/build' (and everything under > it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.9' does not exist -- can't clean it > I: pybuild base:239: python3.10 setup.py clean > running clean > removing '/<>/.pybuild/cpython3_3.10/build' (and everything > under it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.10' does not exist -- can't clean it >dh_autoreconf_clean -O--buildsystem=pybuild >dh_clean -O--buildsystem=pybuild > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building asdf-astropy using existing > ./asdf-astropy_0.2.1.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: warning: ignoring deletion of directory asdf_astropy.egg-info > dpkg-source: warning: ignoring deletion of file > asdf_astropy.egg-info/zip-safe, use --include-removal to override > dpkg-source: warning: ignoring deletion of file > asdf_astropy.egg-info/dependency_links.txt, use --include-removal to override > dpkg-source: warning: ignoring deletion of file > asdf_astropy.egg-info/top_level.txt, use --include-removal to override > dpkg-source: warning: ignoring deletion of file > asdf_astropy.egg-info/SOURCES.txt, use --include-removal to override > dpkg-source: warning: ignoring deletion of file > asdf_astropy.egg-info/PKG-INFO, use --include-removal to override > dpkg-source: warning: ignoring deletion of file > asdf_astropy.egg-info/requires.txt, use --include-removal to override > dpkg-source: warning: ignoring deletion of file > asdf_astropy.egg-info/entry_points.txt, use --include-removal to override > dpkg-source: info: local changes detected, the modified files are: > asdf-astropy-0.2.1/asdf_astropy/_version.py > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/asdf-astropy_0.2.1-2.diff.IFSX63 > dpkg-source: info: Hint: make sure the version in debian/changelog matches > the unpacked source tree > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 > > Build finished at 2022-07-16T06:05:01Z The full build log is available from: http://qa-logs.debian.net/2022/07/16/asdf-astropy_0.2.1-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220716=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 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 --- Source: asdf-astropy Source-Version: 0.2.1-3 Done: Ole Streicher We believe that the bug you reported is fixed in the latest version of asdf-astropy, 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
Bug#1015122: marked as done (pytest-astropy: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)
Your message dated Sun, 17 Jul 2022 10:19:09 + with message-id and subject line Bug#1015122: fixed in pytest-astropy 0.10.0-2 has caused the Debian Bug report #1015122, regarding pytest-astropy: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 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.) -- 1015122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015122 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pytest-astropy Version: 0.10.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > fakeroot debian/rules clean > dh clean --with python3 --buildsystem=pybuild >dh_auto_clean -O--buildsystem=pybuild > I: pybuild base:239: python3.9 setup.py clean > running clean > removing '/<>/.pybuild/cpython3_3.9/build' (and everything under > it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.9' does not exist -- can't clean it > I: pybuild base:239: python3.10 setup.py clean > running clean > removing '/<>/.pybuild/cpython3_3.10/build' (and everything > under it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.10' does not exist -- can't clean it >dh_autoreconf_clean -O--buildsystem=pybuild >dh_clean -O--buildsystem=pybuild > dpkg-source -b . > dpkg-source: warning: upstream signing key but no upstream tarball signature > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building pytest-astropy using existing > ./pytest-astropy_0.10.0.orig.tar.gz > dpkg-source: info: local changes detected, the modified files are: > pytest-astropy-0.10.0/pytest_astropy/version.py > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/pytest-astropy_0.10.0-1.diff.Wsetp6 > dpkg-source: info: Hint: make sure the version in debian/changelog matches > the unpacked source tree > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 > > Build finished at 2022-07-16T06:06:05Z The full build log is available from: http://qa-logs.debian.net/2022/07/16/pytest-astropy_0.10.0-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220716=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 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 --- Source: pytest-astropy Source-Version: 0.10.0-2 Done: Ole Streicher We believe that the bug you reported is fixed in the latest version of pytest-astropy, 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. Ole Streicher (supplier of updated pytest-astropy 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, 17 Jul 2022 12:04:44 +0200 Source: pytest-astropy Architecture: source Version: 0.10.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Astro Team Changed-By: Ole Streicher Closes: 1015122 Changes: pytest-astropy (0.10.0-2) unstable; urgency=medium . * Add gitlab ci file * Add version.py to d/clean (Closes: #1015122) * Push Standards-Version to 4.6.1. No changes needed Checksums-Sha1: 62af0b291506fc3cffc36cc463a0d5ba29a881e6 2426 pytest-astropy_0.10.0-2.dsc
Bug#1015072: marked as done (pytest-doctestplus: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)
Your message dated Sun, 17 Jul 2022 10:19:13 + with message-id and subject line Bug#1015072: fixed in pytest-doctestplus 0.12.0-2 has caused the Debian Bug report #1015072, regarding pytest-doctestplus: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 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.) -- 1015072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015072 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pytest-doctestplus Version: 0.12.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules clean > dh clean --with python3 --buildsystem=pybuild >dh_auto_clean -O--buildsystem=pybuild > I: pybuild base:239: python3.9 setup.py clean > running clean > removing '/<>/.pybuild/cpython3_3.9/build' (and everything under > it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.9' does not exist -- can't clean it > I: pybuild base:239: python3.10 setup.py clean > running clean > removing '/<>/.pybuild/cpython3_3.10/build' (and everything > under it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.10' does not exist -- can't clean it >dh_autoreconf_clean -O--buildsystem=pybuild >dh_clean -O--buildsystem=pybuild > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building pytest-doctestplus using existing > ./pytest-doctestplus_0.12.0.orig.tar.gz > dpkg-source: info: local changes detected, the modified files are: > pytest-doctestplus-0.12.0/pytest_doctestplus/version.py > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/pytest-doctestplus_0.12.0-1.diff.A7u40R > dpkg-source: info: Hint: make sure the version in debian/changelog matches > the unpacked source tree > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 > > Build finished at 2022-07-16T06:06:05Z The full build log is available from: http://qa-logs.debian.net/2022/07/16/pytest-doctestplus_0.12.0-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220716=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 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 --- Source: pytest-doctestplus Source-Version: 0.12.0-2 Done: Ole Streicher We believe that the bug you reported is fixed in the latest version of pytest-doctestplus, 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. Ole Streicher (supplier of updated pytest-doctestplus 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, 17 Jul 2022 11:57:46 +0200 Source: pytest-doctestplus Architecture: source Version: 0.12.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Ole Streicher Closes: 1015072 Changes: pytest-doctestplus (0.12.0-2) unstable; urgency=medium . * Add version.py to d/clean (Closes: #1015072) * Push Standards-Version to 4.6.1. No changes needed Checksums-Sha1: 32a647be3fecf020bece5ce2291ed3da6d27093c 2274 pytest-doctestplus_0.12.0-2.dsc 5889b3abe84b47efed2bafb32766c7e00bd437da 3332
Bug#1015083: marked as done (pytest-remotedata: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)
Your message dated Sun, 17 Jul 2022 10:19:18 + with message-id and subject line Bug#1015083: fixed in pytest-remotedata 0.3.3-2 has caused the Debian Bug report #1015083, regarding pytest-remotedata: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 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.) -- 1015083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015083 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pytest-remotedata Version: 0.3.3-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > fakeroot debian/rules clean > dh clean --with python3 --buildsystem=pybuild >dh_auto_clean -O--buildsystem=pybuild > I: pybuild base:239: python3.9 setup.py clean > running clean > removing '/<>/.pybuild/cpython3_3.9/build' (and everything under > it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.9' does not exist -- can't clean it > I: pybuild base:239: python3.10 setup.py clean > running clean > removing '/<>/.pybuild/cpython3_3.10/build' (and everything > under it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.10' does not exist -- can't clean it >dh_autoreconf_clean -O--buildsystem=pybuild >dh_clean -O--buildsystem=pybuild > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building pytest-remotedata using existing > ./pytest-remotedata_0.3.3.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: local changes detected, the modified files are: > pytest-remotedata-0.3.3/pytest_remotedata/version.py > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/pytest-remotedata_0.3.3-1.diff.JW4H3o > dpkg-source: info: Hint: make sure the version in debian/changelog matches > the unpacked source tree > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 > > Build finished at 2022-07-16T06:06:32Z The full build log is available from: http://qa-logs.debian.net/2022/07/16/pytest-remotedata_0.3.3-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220716=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 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 --- Source: pytest-remotedata Source-Version: 0.3.3-2 Done: Ole Streicher We believe that the bug you reported is fixed in the latest version of pytest-remotedata, 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. Ole Streicher (supplier of updated pytest-remotedata 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, 17 Jul 2022 11:53:09 +0200 Source: pytest-remotedata Architecture: source Version: 0.3.3-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Ole Streicher Closes: 1015083 Changes: pytest-remotedata (0.3.3-2) unstable; urgency=medium . * Add version.py to d/clean (Closes: #1015083) * Push Standards-Version to 4.6.1. No changes needed Checksums-Sha1: cbd4d0be4cf8e3f5ef6961ce1f3cfdbec193da4f 2144 pytest-remotedata_0.3.3-2.dsc
Bug#1015088: [Pkg-nagios-devel] Bug#1015088: icingadb: FTBFS: ../pkg/com/bulker.go:30:16: internal compiler error: assertion failed
Anthony, Shengjing, Could you consider taking a look if you have some b/w available? On Sat, 16 Jul 2022 16:16:44 +0200 Sebastiaan Couwenberg wrote: > reassign 1015088 src:golang-1.18 > found 1015088 golang-1.18/1.18.4-1 > affects 1015088 src:icingadb > thanks > > On 7/16/22 15:21, Lucas Nussbaum wrote: > >> dh_auto_build > >>cd _build && go version > >> go version go1.18.4 linux/amd64 > >>cd _build && go env > >> GO111MODULE="on" > >> GOARCH="amd64" > >> GOBIN="" > >> GOCACHE="/<>/_build/go-build" > >> GOENV="/sbuild-nonexistent/.config/go/env" > >> GOEXE="" > >> GOEXPERIMENT="" > >> GOFLAGS="" > >> GOHOSTARCH="amd64" > >> GOHOSTOS="linux" > >> GOINSECURE="" > >> GOMODCACHE="/<>/_build/pkg/mod" > >> GONOPROXY="" > >> GONOSUMDB="" > >> GOOS="linux" > >> GOPATH="/<>/_build" > >> GOPRIVATE="" > >> GOPROXY="off" > >> GOROOT="/usr/lib/go-1.18" > >> GOSUMDB="sum.golang.org" > >> GOTMPDIR="" > >> GOTOOLDIR="/usr/lib/go-1.18/pkg/tool/linux_amd64" > >> GOVCS="" > >> GOVERSION="go1.18.4" > >> GCCGO="gccgo" > >> GOAMD64="v1" > >> AR="ar" > >> CC="gcc" > >> CXX="g++" > >> CGO_ENABLED="1" > >> GOMOD="/<>/go.mod" > >> GOWORK="" > >> CGO_CFLAGS="-g -O2 -ffile-prefix-map=/<>=. > >> -fstack-protector-strong -Wformat -Werror=format-security" > >> CGO_CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" > >> CGO_CXXFLAGS="-g -O2 -ffile-prefix-map=/<>=. > >> -fstack-protector-strong -Wformat -Werror=format-security" > >> CGO_FFLAGS="-g -O2 -ffile-prefix-map=/<>=. > >> -fstack-protector-strong" > >> CGO_LDFLAGS="-Wl,-z,relro" > >> PKG_CONFIG="pkg-config" > >> GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 > >> -fdebug-prefix-map=/tmp/go-build898317925=/tmp/go-build > >> -gno-record-gcc-switches" > >>cd _build && go install -trimpath -v -p 8 > >> github.com/icinga/icingadb/cmd/icingadb > >> [...] > >> github.com/icinga/icingadb/pkg/com > >> os/user > >> # github.com/icinga/icingadb/pkg/com > >> ../pkg/com/bulker.go:30:16: internal compiler error: assertion failed > >> > >> Please file a bug report including a short program that triggers the error. > >> https://go.dev/issue/new > > This issue is introduced in golang-1.18 (1.18.4-1), icingadb built -- Regards, Nilesh signature.asc Description: PGP signature
Bug#1014741: libgd-perl: GD and GD2 image formats are disabled in libgd3 package
On Mon, 11 Jul 2022 23:05:32 +0200, gregor herrmann wrote: > > I also note that the tests (which use the samples (which call the > > export_format > > function (which has line 515 of Graph.pm))) also fail by now: > > > > # Failed test at t/samples.t line 21. > > # died: gdImageGdPtr error at > > /build/libgd-graph-perl-1.54~ds/blib/lib/GD/Graph.pm line 515. > > # Compilation failed in require at t/samples.t line 17. > > With this change > > #v+ > % cat debian/patches/disable-old-formats.patch > --- a/Graph.pm > +++ b/Graph.pm > @@ -514,7 +514,7 @@ > $g->colorAllocate(0,0,0); > $g->$_() > }; > -} qw(gif png jpeg xbm xpm gd gd2); > +} qw(gif png jpeg xbm xpm); > wantarray ? @f : $f[0]; > } > > #v- > > the tests indeed pass. > But I don't have enough knowledge about this stuff that I would feel > confident to blindly upload. Out of curiosity, I tried again today to build the package _without_ this patch. -- And: all tests pass. That's with libgd3_2.3.3-6 and libgd-perl_2.76-3. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Processed: Bug#1015072 marked as pending in pytest-doctestplus
Processing control commands: > tag -1 pending Bug #1015072 [src:pytest-doctestplus] pytest-doctestplus: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 Added tag(s) pending. -- 1015072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015072 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015072: marked as pending in pytest-doctestplus
Control: tag -1 pending Hello, Bug #1015072 in pytest-doctestplus reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/pytest-doctestplus/-/commit/8cb7209dfff9f4919be15943fc86298927913c7b Add version.py to d/clean Closes: #1015072 (this message was generated automatically) -- Greetings https://bugs.debian.org/1015072
Bug#1014506: slurm-wlm: flaky autopkgtest: sbatch fails without
Control: affects 1014506 src:libyaml On Thu, Jul 07, 2022 at 11:22:44AM +0200, Paul Gevers wrote: > [...] > I looked at the results of the autopkgtest of you package on armhf because > it was showing up as a regression for the upload of perl. I noticed that the > test regularly fails and I saw failures on other architectures too. > > 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. JFTR, this now also affects the unstable-to-testing migration of libyaml, cf. https://tracker.debian.org/pkg/libyaml. Thus marking this issue here as such. Cheers, Flo signature.asc Description: PGP signature
Processed: Bug#1015083 marked as pending in pytest-remotedata
Processing control commands: > tag -1 pending Bug #1015083 [src:pytest-remotedata] pytest-remotedata: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 Added tag(s) pending. -- 1015083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015083 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015083: marked as pending in pytest-remotedata
Control: tag -1 pending Hello, Bug #1015083 in pytest-remotedata reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/pytest-remotedata/-/commit/d2c8743018fb474bcebe5d946ad7020f875e Add version.py to d/clean Closes: #1015083 (this message was generated automatically) -- Greetings https://bugs.debian.org/1015083
Processed: Re: Bug#1014506: slurm-wlm: flaky autopkgtest: sbatch fails without
Processing control commands: > affects 1014506 src:libyaml Bug #1014506 [src:slurm-wlm] slurm-wlm: flaky autopkgtest: sbatch fails without Added indication that 1014506 affects src:libyaml -- 1014506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014506 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1007138: libgnutls30: fails on Let's Encrypt chains due to blacklisted expired root certificate
Processing control commands: > severity -1 serious Bug #1007138 [libgnutls30] libgnutls30: fails to validate when there is junk in the cert chain, including duplicated server certs Severity set to 'serious' from 'important' -- 1007138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007138 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015174: lvm2-udeb: uninstallable, depends on non-udeb libsystemd0
I presume this is also the cause of this failure when installing Debian-EDU: https://openqa.debian.net/tests/64605#step/grub/3 If one looks at the associated syslog, here: https://openqa.debian.net/tests/64605#step/grub/31 one can see various symptoms of libsystemd0's absence: ... Jul 16 14:43:44 anna[2159]: DEBUG: resolver (libsystemd0): package doesn't exist (ignored) ... Jul 16 14:43:58 main-menu[423]: (process:4065): pvs: error while loading shared libraries: libsystemd.so.0: cannot open shared object file: No such file or directory ... resulting in the failure to create the volume group, seen in the initial screenshot above. Cheers, Phil. -- |)| Philip Hands [+44 (0)20 8530 9560] HANDS.COM Ltd. |-| http://www.hands.com/http://ftp.uk.debian.org/ |(| Hugo-Klemm-Strasse 34, 21075 Hamburg,GERMANY
Processed: Bug#1015129 marked as pending in sphinx-automodapi
Processing control commands: > tag -1 pending Bug #1015129 [src:sphinx-automodapi] sphinx-automodapi: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 Added tag(s) pending. -- 1015129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015129 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015129: marked as pending in sphinx-automodapi
Control: tag -1 pending Hello, Bug #1015129 in sphinx-automodapi reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/sphinx-automodapi/-/commit/113b691302eba41c5b9b4d99a95e648de12a7a10 Add version.py to d/clean Closes: #1015129 (this message was generated automatically) -- Greetings https://bugs.debian.org/1015129
Bug#1015112: marked as done (radio-beam: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)
Your message dated Sun, 17 Jul 2022 09:20:22 + with message-id and subject line Bug#1015112: fixed in radio-beam 0.3.3-3 has caused the Debian Bug report #1015112, regarding radio-beam: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 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.) -- 1015112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015112 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: radio-beam Version: 0.3.3-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules clean > py3versions: no X-Python3-Version in control file, using supported versions > dh clean --with python3 --buildsystem=pybuild >dh_auto_clean -O--buildsystem=pybuild > I: pybuild base:239: python3.9 setup.py clean > running clean > removing '/<>/.pybuild/cpython3_3.9_radio_beam/build' (and > everything under it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.9' does not exist -- can't clean it > I: pybuild base:239: python3.10 setup.py clean > running clean > removing '/<>/.pybuild/cpython3_3.10_radio_beam/build' (and > everything under it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.10' does not exist -- can't clean it >dh_autoreconf_clean -O--buildsystem=pybuild >dh_clean -O--buildsystem=pybuild > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building radio-beam using existing > ./radio-beam_0.3.3.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: local changes detected, the modified files are: > radio-beam-0.3.3/radio_beam/version.py > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/radio-beam_0.3.3-2.diff.bBsxR3 > dpkg-source: info: Hint: make sure the version in debian/changelog matches > the unpacked source tree > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 > > Build finished at 2022-07-16T05:57:32Z The full build log is available from: http://qa-logs.debian.net/2022/07/16/radio-beam_0.3.3-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220716=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 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 --- Source: radio-beam Source-Version: 0.3.3-3 Done: Ole Streicher We believe that the bug you reported is fixed in the latest version of radio-beam, 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. Ole Streicher (supplier of updated radio-beam 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, 17 Jul 2022 11:00:05 +0200 Source: radio-beam Architecture: source Version: 0.3.3-3 Distribution: unstable Urgency: medium Maintainer: Debian Astronomy Team Changed-By: Ole Streicher Closes: 1015112 Changes: radio-beam (0.3.3-3) unstable; urgency=medium . * Add version.py to d/clean (Closes: #1015112) Checksums-Sha1: 68f5110c5c7dd563b6c68ffc2fb4335413a8db6b 2210 radio-beam_0.3.3-3.dsc cf6235d96c162a940f46fd769514336c391101e1 3640 radio-beam_0.3.3-3.debian.tar.xz
