Bug#1006289: marisa's autopkgtest regressed since rebuild for ruby3.0 as default
X-Debbugs-CC: kanash...@debian.org terce...@debian.org gunna...@debian.org
Hi all,
(see bottom)
在 2022-02-22星期二的 22:05 +0100，Paul Gevers写道：
> Source: marisa
> Version: 0.2.6-8
> Severity: serious
> X-Debbugs-Cc: kanash...@debian.org, terce...@debian.org
>
> Dear maintainer,
>
> As part of the ongoing transition from ruby2.7 as default ruby to
> ruby3.0 as default, your package got rebuild. In that rebuild it
> correctly picked up a dependency on libruby3.0, but as it also depends
> on ruby (unversioned) it seems to not be able to work in testing, as
> seen by the autopkgtest regression.
>
> I don't know what the best way forward is, but I think the right
> version of ruby needs to be detected during build and included in
> ${misc:Depends} or something similar. I have included two ruby
> maintainers in the X-Debbugs-CC for advice.
>
> Paul
>
> https://ci.debian.net/data/autopkgtest/testing/amd64/m/marisa/19472910/log.gz
>
> [...]
>
> Setting up libruby3.0:amd64 (3.0.2-7) ...
> Setting up libruby2.7:amd64 (2.7.4-1+b1) ...
> Setting up ruby2.7 (2.7.4-1+b1) ...
> Setting up ruby (1:2.7.6) ...
>
> [...]
>
> autopkgtest [20:54:51]: test ruby: [---
> === ruby ===
> /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in
> `require': cannot load such file -- marisa (LoadError)
> from
> /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in
> `require'
> from bindings/ruby/sample.rb:1:in `'
> autopkgtest [20:54:51]: test ruby: ---]
Compared to
https://salsa.debian.org/input-method-team/marisa/-/merge_requests/1 ,
I am more into a more generic solution to avoid version hardcoding:
diff --git a/debian/control b/debian/control
index 39c36da..dec2dc7 100644
--- a/debian/control
+++ b/debian/control
@@ -95,7 +95,7 @@ Architecture: any
Multi-Arch: foreign
Depends:
libmarisa0 (= ${binary:Version}),
- ruby,
+ ruby (>= ${ruby:Build-Version}),
${misc:Depends},
${shlibs:Depends},
Description: Ruby bindings for MARISA
diff --git a/debian/rules b/debian/rules
index 20a945c..9acebb2 100755
--- a/debian/rules
+++ b/debian/rules
@@ -79,3 +79,9 @@ override_dh_auto_install:
rm $(CURDIR)/debian/libmarisa-perl$(PERL_VENDOR_ARCH)/sample.pl
# install ruby modules
cd bindings/ruby; make install DESTDIR=$(CURDIR)/debian/ruby-marisa
+
+# record minimum ruby version requirement
+# see https://bugs.debian.org/1006289
+override_dh_gencontrol:
+ dh_gencontrol -- \
+ -V"ruby:Build-Version=$$(dpkg-query -f='$${Version}' -W ruby)"
I will make an upload with this solution to see how things works. The testing
migration will unfortunately be blocked till ruby3.0 migrates, but that should
be the expected behavior. I really don't want to hack into marisa's (custom)
ruby building chain to support multiple ruby versions.
BTW: it would be great if Ruby could provide some similar substvar (or via
${ruby:Depends}), though it is not possible for now since ${ruby:Depends} is
currently from gem2deb and not for non-gem packages.
Thank you all for caring marisa package!
Best,
Boyuan Yang
signature.asc
Description: This is a digitally signed message part
Bug#1000336: Upgrading tbb
On Wed, 2022-02-23 at 00:31 -0500, M. Zhou wrote: > Hello guys. Finally it's all green on our release architectures > https://buildd.debian.org/status/package.php?p=onetbb=experimental > > I shall request the slot for transition once finished the rebuild > of its reverse dependencies and filed FTBFS bugs if any. Wonderful! That is great news. Thank you! Diane
Bug#1006308: seatd-launch: CVE-2022-25643
Source: seatd Version: 0.6.3-2 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for seatd. CVE-2022-25643[0]: | seatd-launch in seatd 0.6.x before 0.6.4 allows removing files with | escalated privileges when installed setuid root. The attack vector is | a user-supplied socket pathname. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-25643 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-25643 [1] https://lists.sr.ht/~kennylevinsen/seatd-announce/%3CETEO7R.QG8B1KGD531R1%40kl.wtf%3E Regards, Salvatore
Processed: correctly mark tags
Processing commands for cont...@bugs.debian.org: > tags 1006306 -sid Bug #1006306 [apper] apper: apper_installer functionality broken? Removed tag(s) sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 1006306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006306 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1006306: apper: apper_installer functionality broken?
Package: apper Severity: grave Version: 1.0.0-3 Tags: sid X-Debbugs-CC: m...@debian.org Hi, I received a user report that they cannot use Apper to install deb packages on Debian Unstable. I reproduced this issue in the following way: * Right-click on a deb package (in any file manager app of your choice), and select "Apper Installer" to open it. * Nothing happens. In system journal, the following error occurs: = 2月 23 01:40:46 hosiet-vm-home dbus-daemon[2238]: [session uid=1000 pid=2238] Activating service name='org.freedesktop.PackageKit' requested by ':1.108' (uid=1000 pid=5894 comm="apper /dev/shm/flameshot_11.0.0-2_amd64.deb ") 2月 23 01:40:46 hosiet-vm-home dbus-daemon[5901]: writing oom_score_adj error: Permission denied 2月 23 01:40:46 hosiet-vm-home dbus-daemon[2238]: [session uid=1000 pid=2238] Activated service 'org.freedesktop.PackageKit' failed: Failed to execute program org.freedesktop.PackageKit: No such file or directory The same error will also take place when I manually execute "apper /path/to/name.deb". This functionality seems to be provided by /usr/share/applications/org.kde.apper_installer.desktop . I have no idea why service org.freedesktop.PackageKit is looking for nonexistant executable "org.freedesktop.PackageKit". Contents of /usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service already points to the correct executable. My Debian Sid environment already has PackageKit installed. Could you please take a look into it? -- Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1004556: marked as done (libmpich-dev: The simplest MPI program compiled with mpich crashes)
Your message dated Wed, 23 Feb 2022 06:03:41 +
with message-id
and subject line Bug#1004556: fixed in mpich 4.0-3
has caused the Debian Bug report #1004556,
regarding libmpich-dev: The simplest MPI program compiled with mpich crashes
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.)
--
1004556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmpich-dev
Version: 4.0-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: jul...@julien-bigot.fr
Dear Maintainer,
When running the simplest MPI program,
```
#include
int main(int argc, char* argv[])
{
MPI_Init(, );
MPI_Finalize();
return 0;
}
```
it crashes with output:
```
Abort(874106383): Fatal error in internal_Init: Other MPI error, error stack:
internal_Init(59): MPI_Init(argc=0x7ffc82ed999c, argv=0x7ffc82ed9990) failed
MPII_Init_thread(209):
MPID_Init(359)...:
MPIR_pmi_init(151)...: PMIX_Init returned -25
```
See attached reproduction log for full details
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'stable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.15.0-3-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libmpich-dev depends on:
ii g++4:11.2.0-2
ii gfortran [gfortran-mod-15] 4:11.2.0-2
ii gfortran-10 [gfortran-mod-15] 10.3.0-14
ii gfortran-11 [gfortran-mod-15] 11.2.0-14
ii gfortran-9 [gfortran-mod-15] 9.4.0-4+b1
ii libmpich12 4.0-1
ii mpich 4.0-1
libmpich-dev recommends no packages.
libmpich-dev suggests no packages.
-- no debconf information
docker run --rm -ti debian:sid
[14:10]
Unable to find image 'debian:sid' locally
sid: Pulling from library/debian
48c02bc8c594: Pull complete
Digest: sha256:0e6e082a988ec6f880c76864c68705f47e4af4a319e0a56d5a1817282767336c
Status: Downloaded newer image for debian:sid
root@23bd1ec5a8ce:/# apt update
Get:1 http://deb.debian.org/debian sid InRelease [165 kB]
Get:2 http://deb.debian.org/debian sid/main amd64 Packages [8898 kB]
Fetched 9063 kB in 1s (8372 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
13 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@23bd1ec5a8ce:/# apt upgrade
Reading package lists... Done
Building dependency tree... 50%
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
bsdutils libblkid1 libc-bin libc6 libgnutls30 libmount1 libsmartcols1
libsystemd0 libudev1 libuuid1 mawk mount util-linux
13 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 7946 kB of archives.
After this operation, 1207 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian sid/main amd64 bsdutils amd64 1:2.37.3-1+b1
[149 kB]
Get:2 http://deb.debian.org/debian sid/main amd64 util-linux amd64 2.37.3-1+b1
[1200 kB]
Get:3 http://deb.debian.org/debian sid/main amd64 libc6 amd64 2.33-5 [2831 kB]
Get:4 http://deb.debian.org/debian sid/main amd64 libc-bin amd64 2.33-5 [834 kB]
Get:5 http://deb.debian.org/debian sid/main amd64 libsystemd0 amd64 250.3-2
[404 kB]
Get:6 http://deb.debian.org/debian sid/main amd64 mount amd64 2.37.3-1+b1 [191
kB]
Get:7 http://deb.debian.org/debian sid/main amd64 libblkid1 amd64 2.37.3-1+b1
[202 kB]
Get:8 http://deb.debian.org/debian sid/main amd64 libgnutls30 amd64 3.7.3-4+b1
[1377 kB]
Get:9 http://deb.debian.org/debian sid/main amd64 libmount1 amd64 2.37.3-1+b1
[220 kB]
Get:10 http://deb.debian.org/debian sid/main amd64 libsmartcols1 amd64
2.37.3-1+b1 [162 kB]
Get:11 http://deb.debian.org/debian sid/main amd64 libudev1 amd64 250.3-2 [178
kB]
Get:12 http://deb.debian.org/debian sid/main amd64 libuuid1 amd64 2.37.3-1+b1
[85.4 kB]
Get:13 http://deb.debian.org/debian sid/main amd64 mawk amd64
1.3.4.20200120-3+b1 [113 kB]
Fetched 7946 kB in 0s (73.9 MB/s)
debconf: delaying package configuration, since apt-utils is not
Bug#1004556: libmpich-dev: The simplest MPI program compiled with mpich crashes
I can disable pmix support in mpich. Pmix is working fine in openmpi, so it’s an mpich/pmix issue of some sort (or maybe ch4) Regards Alastair On 22/02/2022, 14:57, "debian-science-maintainers on behalf of Drew Parsons" wrote: Package: mpich Followup-For: Bug #1004556 My guess is that this bug is ongoing in 4.0-2 because of pmix support. 4.0-2 is still configured --with-pmix=/usr/lib/x86_64-linux-gnu/pmix2 and still Depends: libpmix2 (>= 4.1.2) pmix support was added in 4.0~b1-2 along with ucx. I gather ucx was deactivated in 4.0-2 but pmix was not. Looks like pmix also needs to go (unless the problem is ch4, which was also added in 4.0~b1-2). But the error message references PMIX. Ironically, I find that an executable compiled against mpich 4.0-1 fails with mpiexec.mpich (as raised in this bug) but actually passes when run with mpiexec.openmpi. Awkward. -- debian-science-maintainers mailing list debian-science-maintain...@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1000336: Upgrading tbb
Am Wed, Feb 23, 2022 at 12:31:07AM -0500 schrieb M. Zhou: > Hello guys. Finally it's all green on our release architectures > https://buildd.debian.org/status/package.php?p=onetbb=experimental > > I shall request the slot for transition once finished the rebuild > of its reverse dependencies and filed FTBFS bugs if any. Sounds good - thanks a lot for your work on this Andreas. -- http://fam-tille.de
Bug#1005438: pygame: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" --system=custom --test-args "/usr/bin/xvfb-run {interpreter} -m pygame.tests.__main__ --exclude opengl"
Hi Stefano, Am Wed, Feb 23, 2022 at 01:56:11AM + schrieb Stefano Rivera: > Hi Andreas (2022.02.22_07:57:25_+) > > I've put all developers mentioned as Uploader in CC. Given that the > > last non-team upload was two years ago which might have lead to the > > situation that following upstream changes is stalled it would be great > > if you confirm that you intend to continue working on this package. > > I think it's high time to get pygame 2 into Debian. There's probably > some transition required, and maybe some rev-deps will need to be > removed, but pygame 1.9 isn't supportable forever. Missing myself the slightest insight into pygame I'd say we should start rather sooner than later. > I've done some of the recent uploads, kicking the can down the road, but > they're getting harder and harder. Definitely. And thanks for keeping it alife so far. Kind regards Andreas. -- http://fam-tille.de
Bug#1000336: Upgrading tbb
Hello guys. Finally it's all green on our release architectures https://buildd.debian.org/status/package.php?p=onetbb=experimental I shall request the slot for transition once finished the rebuild of its reverse dependencies and filed FTBFS bugs if any. On Tue, 2022-02-08 at 17:59 -0500, M. Zhou wrote: > Hi Diane, > > Thank you. I have added that patch in the git repository. > > On Tue, 2022-02-08 at 13:49 -0800, Diane Trout wrote: > > Hi, > > > > After Andreas pointed it out I looked through some of the build > > failures for onetbb and talked to upstream about the i386 failure. > > https://github.com/oneapi-src/oneTBB/issues/370#issuecomment-1030387116 > > > > They have a patch. > > https://github.com/oneapi-src/oneTBB/commit/542a27fa1cfafaf76772e793549d9f4d288d03a9 > > > > I've tested it against a checkout of the 2021.5.0-1 version of onetbb > > on i386 and it does build with it applied. Once there was a test > > failure, and once all tests ran successfully > > > > I see that you've made some more progress for the memory alignment > > bugs > > so I didn't commit "Detect 32 bit x86 systems while adding -mwaitpkg > > option" i386 patch but could if you want. > > > > Diane > > > > >
Bug#1002445: About shortuuid (was: FTBFS: AssertionError...)
Dear Martin. I'm sorry. Please go ahead. -- Kouhei Maeda KeyID 4096R/B8F286F62206360F7D4108172E8162547E37CE41 2022年1月30日(日) 18:51 Martin : > Dear Kouhei Maeda, > > one of my packages, libervia-backend resp. salutatoi, depends on > shortuuid and due to bug #1002445 of 2021-12-22 in shortuuid it will be > removed from testing soon. > > If you don't have the time to fix the bug right now, I could make an NMU > (non-maintainer upload), but I wonder, if it would be better to move the > package to the "Debian Python Team"? That would allow many people to > make changes, whenever necessary. You would remain in charge of the > package, of course. > > Please, if you don't mind, just send me a short note "go ahead", and I > would move the package to the team, fix the bug and update it! > > Many thanks in advance! > > Cheers, Martin >
Bug#1005438: pygame: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" --system=custom --test-args "/usr/bin/xvfb-run {interpreter} -m pygame.tests.__main__ --exclude opengl"
Hi Andreas (2022.02.22_07:57:25_+) > I've put all developers mentioned as Uploader in CC. Given that the > last non-team upload was two years ago which might have lead to the > situation that following upstream changes is stalled it would be great > if you confirm that you intend to continue working on this package. I think it's high time to get pygame 2 into Debian. There's probably some transition required, and maybe some rev-deps will need to be removed, but pygame 1.9 isn't supportable forever. I've done some of the recent uploads, kicking the can down the road, but they're getting harder and harder. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Bug#979931: marked as done (jquery-at.js: node-uglify is deprecated in favor of uglifyjs)
Your message dated Wed, 23 Feb 2022 01:49:01 + with message-id and subject line Bug#979931: fixed in jquery-at.js 1.5.4+dfsg.1-3 has caused the Debian Bug report #979931, regarding jquery-at.js: node-uglify is deprecated in favor of uglifyjs 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.) -- 979931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979931 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: jquery-at.js Severity: important jquery-at.js build depends on node-uglify which is deprecated and will be removed from bullseye (#958117), please update your (build) dependency in favor of uglifyjs or uglifyjs.terser https://bugs.debian.org/958117 (sent using mass-bug) --- End Message --- --- Begin Message --- Source: jquery-at.js Source-Version: 1.5.4+dfsg.1-3 Done: Ben Finney We believe that the bug you reported is fixed in the latest version of jquery-at.js, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Finney (supplier of updated jquery-at.js package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 23 Feb 2022 12:19:27 +1100 Source: jquery-at.js Architecture: source Version: 1.5.4+dfsg.1-3 Distribution: unstable Urgency: medium Maintainer: Ben Finney Changed-By: Ben Finney Closes: 863293 954680 979931 Changes: jquery-at.js (1.5.4+dfsg.1-3) unstable; urgency=medium . * The “Glenn Randers-Pehrson” release. * Update publication years for Debian packaging in copyright notices. * Specify settings for EditorConfig in this project. * Rename default Git branch in official repository, to ‘main’. * Declare conformance to “Standards-Version: 4.6.0”. * Remove ‘get-orig-source’ and ‘get-packaged-orig-source’ targets. These are no longer mentioned in Debian Policy 4.1.4 and later. * Declare Debhelper compatibility level 13. * debian/compat: * Remove obsolete configuration file. * Update package source documentation for standard packaging tools. * Refine the exclusion set, to preserve the upstream source files. * Use UScan features to better specify upstream source URLs. * Specify the package build system does not require root privilege. * Add simple AutoPkgTest smoke test of installed library files. * Build-Depends on command-line tool (not library) UglifyJS package. Closes: bug#979931. Thanks to Jonas Smedegaard for the explanation. * debian/patches/gulp-signal-task-completion.patch: * Patch Gulp tasks for new asynchronous task runner. Closes: bug#954680. Thanks to Lucas Nussbaum for the report. * Install the NodeJS package definition. * Symlink the library files to the NodeJS search path. * Declare the installed package “Provides: node-jquery.caret”. Closes: bug#863293. Thanks to Pirate Praveen for the report. * Record upstream metadata in DEP-12 document. * Override a Lintian check for upstream example documents. The documents breach user privacy, which should not be installed. Checksums-Sha1: bbbfff446120c5a8dc93ce41161d93d9594ccfe0 2091 jquery-at.js_1.5.4+dfsg.1-3.dsc 387f6826361760433161a685fcde1cda1c45b72e 8104 jquery-at.js_1.5.4+dfsg.1-3.debian.tar.xz e174c1c8a56624806dad3762fb48eea89f287af9 14428 jquery-at.js_1.5.4+dfsg.1-3_amd64.buildinfo Checksums-Sha256: 908c91ce21edbf46249ba55f9dae6d7bd8ecdfda89c8fefbaabb5d6a919cfbf3 2091 jquery-at.js_1.5.4+dfsg.1-3.dsc ac498309a4143b103f25a965f3c33ece390c00857da6df535cdd2d45e36629ac 8104 jquery-at.js_1.5.4+dfsg.1-3.debian.tar.xz 6493a5fcc194f950501d1f6453c571468b1652859fa18c07465b5df651cffd5c 14428 jquery-at.js_1.5.4+dfsg.1-3_amd64.buildinfo Files: ba255cd3d73b3b066d51b759a6c288ff 2091 javascript optional jquery-at.js_1.5.4+dfsg.1-3.dsc f9323f38c2a0dcb56ba1b56293a71ffa 8104 javascript optional jquery-at.js_1.5.4+dfsg.1-3.debian.tar.xz 779c759fc31a1b2023de872a27e14bed 14428 javascript optional jquery-at.js_1.5.4+dfsg.1-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEdN8hqSSdpNPGgGg3kgn6QYDP/G8FAmIVjqkACgkQkgn6QYDP
Bug#954680: marked as done (jquery-at.js: FTBFS: The following tasks did not complete: coffee)
Your message dated Wed, 23 Feb 2022 01:49:01 + with message-id and subject line Bug#954680: fixed in jquery-at.js 1.5.4+dfsg.1-3 has caused the Debian Bug report #954680, regarding jquery-at.js: FTBFS: The following tasks did not complete: coffee 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.) -- 954680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954680 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jquery-at.js Version: 1.5.4+dfsg.1-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200322 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > mkdir --parents /<>/build/js > gulp coffee > [08:50:25] Local modules not found in /<> > [08:50:25] Try running: npm install > [08:50:25] Using globally installed gulp > [08:50:25] Using gulpfile /<>/gulpfile.js > [08:50:25] Starting 'coffee'... > [08:50:26] The following tasks did not complete: coffee > [08:50:26] Did you forget to signal async completion? > make[1]: *** [debian/rules:105: /<>/build/js/default.js] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/03/22/jquery-at.js_1.5.4+dfsg.1-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! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: jquery-at.js Source-Version: 1.5.4+dfsg.1-3 Done: Ben Finney We believe that the bug you reported is fixed in the latest version of jquery-at.js, 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 954...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Finney (supplier of updated jquery-at.js package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 23 Feb 2022 12:19:27 +1100 Source: jquery-at.js Architecture: source Version: 1.5.4+dfsg.1-3 Distribution: unstable Urgency: medium Maintainer: Ben Finney Changed-By: Ben Finney Closes: 863293 954680 979931 Changes: jquery-at.js (1.5.4+dfsg.1-3) unstable; urgency=medium . * The “Glenn Randers-Pehrson” release. * Update publication years for Debian packaging in copyright notices. * Specify settings for EditorConfig in this project. * Rename default Git branch in official repository, to ‘main’. * Declare conformance to “Standards-Version: 4.6.0”. * Remove ‘get-orig-source’ and ‘get-packaged-orig-source’ targets. These are no longer mentioned in Debian Policy 4.1.4 and later. * Declare Debhelper compatibility level 13. * debian/compat: * Remove obsolete configuration file. * Update package source documentation for standard packaging tools. * Refine the exclusion set, to preserve the upstream source files. * Use UScan features to better specify upstream source URLs. * Specify the package build system does not require root privilege. * Add simple AutoPkgTest smoke test of installed library files. * Build-Depends on command-line tool (not library) UglifyJS package. Closes: bug#979931. Thanks to Jonas Smedegaard for the explanation. * debian/patches/gulp-signal-task-completion.patch: * Patch Gulp tasks for new asynchronous task runner. Closes: bug#954680. Thanks to Lucas Nussbaum for the report. * Install the NodeJS package definition. * Symlink the library files to the NodeJS search path. * Declare the installed package “Provides: node-jquery.caret”. Closes: bug#863293. Thanks to Pirate Praveen for the report. * Record upstream metadata in DEP-12 document. * Override a Lintian check for upstream example documents. The documents breach user privacy, which should not be installed. Checksums-Sha1: bbbfff446120c5a8dc93ce41161d93d9594ccfe0 2091 jquery-at.js_1.5.4+dfsg.1-3.dsc 387f6826361760433161a685fcde1cda1c45b72e
Bug#1006289: marisa's autopkgtest regressed since rebuild for ruby3.0 as default
X-Debbugs-Cc: kanash...@debian.org, terce...@debian.org Hi Paul, I submitted this MR: https://salsa.debian.org/input-method-team/marisa/-/merge_requests/1 Can someone confirm that it would help? One reason why I hesitate is that it would make ruby-marisa uninstallable in testing ATM. -- Cheers, Gunnar Hjalmarsson
Bug#1005653: (no subject)
On Mon, 21 Feb 2022 09:14:22 -0800, ZenWalker said: > maybe > https://github.com/Nheko-Reborn/nheko/commit/b439e1fa41b26db5f1d0d16bd1da664338b435e7 > fixes the bug, which is included in version 0.9.1 > There is plans to package nheko 0.9.1 ? Yes, I should be able to upload it in the next few days. -- Hubert Chathi -- https://www.uhoreg.ca/ Jabber: hub...@uhoreg.ca -- Matrix: @uhoreg:matrix.org PGP/GnuPG key: 4096R/F24C F749 6C73 DDB8 DCB8 72DE B2DE 88D3 113A 1368
Bug#1005187: collectd build-depends on package that is not in testing.
On Tue, 2022-02-22 at 22:37 +, Peter Green wrote: > > To the best of my knowledge there is no mechanism to automatically remove > packages with broken build-dependencies from testing. I certainly > don't recall collectd being listed for autoremoval at the time I filed the > bug. No idea, but things work as expected, got this mail on january 9th: collectd 5.12.0-7 is marked for autoremoval from testing on 2022-02-04 It (build-)depends on packages with these RC bugs: 997189: liboping: FTBFS: oping.c:1159:25: error: format not a string literal and no format arguments [-Werror=format-security] https://bugs.debian.org/997189 > > The auto-removals system does take account of reverse build-dependencies when > deciding what extra removals to trigger, but unfortunately the same does not > apply to manual removals by the release team. > Not sure, but in the next mail the removal date changed, I'd assume as the removal from testing was used as base date for the autoremoval, not the filed bug: (mail from january 31st) collectd 5.12.0-8 is marked for autoremoval from testing on 2022-02-28 It (build-)depends on packages with these RC bugs: 1002985: ruby-redis, src:ruby-fakeredis: ruby-redis breaks ruby-fakeredis autopkgtest https://bugs.debian.org/1002985 997189: liboping: FTBFS: oping.c:1159:25: error: format not a string literal and no format arguments [-Werror=format-security] https://bugs.debian.org/997189 > In particular the following scenario can happen. > > Package a build-depends (but does not depend) on package b. > Package b is rc buggy. > The autoremovals system sends out mails notifying maintainers that if the > situation doesn't change, it will remove packages b and a > Package b gets manually removed by the release team. > The package with the rc bug is no longer in testing, so it drops off the > autoremoval system's list of issues. > Package a does not actually get autoremoved despite the earlier mail from the > autoremovals system. > > I suspect that may well be what happened here (liboping was manually > removed from testing as it was blocking the perl transition). > > > > Don't think so, at least thats how I interpret the mails I've got. > > It basically adds the extra work of tracking and closing this bug manually. > > I understand that and that is why I am selective about when I file such bugs. > If I see indications that the underlying issue is likely to be fixed on > a reasonable timescale, I generally will hold-off filing bugs on the reverse > dependencies. > > In this case I saw no such indications. The bug report was over a month > old with no maintainer response, and the package had not seen a maintainer > upload in over a year. > The maintainer is busy with real life, if I'd have known that it blocks the perl transition, I'd have fixed oping earlier. > > > > If you want to add such bugs, please link them properly to the bugs that > > caused the issue and make sure that it is closed automatically as soon as > > the > > issue is fixed. > > If the bts had a system to automatically close bugs when another package > migrates > to testing I would use it but afaict it doesn't. > > I am not going to build custom automation for such a small volume of bugs. > Ah thought that it would be automatically generated. > It certainly makes sense to link to the underlying bug though, I'll try and > remember > that next time. > That would be appreciated. > I guess I could also set "blocks", but i'm not entirely convinced it's > appropriate, > it's the maintainers call not mine as to whether to fix the issue by fixing > the > unmaintained package they build-depend on or by eliminating the > build-dependency > on it. True. But I still think that these things shouldn't need manual investigation and bugs at all, if autoremovals doesn't handle manual removals (I guess it does, but add a delay), that should be fixed. Manually filing bugs also needs time. Cheers, Bernd -- Bernd ZeimetzDebian GNU/Linux Developer http://bzed.dehttp://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F
Bug#1005968: marked as done (vdirsyncer: flaky autopkgtest blocks migration of reverse deps)
Your message dated Tue, 22 Feb 2022 22:49:50 + with message-id and subject line Bug#1005968: fixed in vdirsyncer 0.18.0-6 has caused the Debian Bug report #1005968, regarding vdirsyncer: flaky autopkgtest blocks migration of reverse deps 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.) -- 1005968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005968 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vdirsyncer Version: 0.18.0-5 Severity: grave Justification: blocks testing migration of reverse dependencies A flaky unit test (test_fuzzing) sometimes fail, causing unrelated reverse dependencies to be blocked from migrating from unstable to testing. Please either fix or skip this test. Eg: https://ci.debian.net/data/autopkgtest/testing/ppc64el/v/vdirsyncer/19319438/log.gz === FAILURES === _ test_fuzzing _ tests/unit/cli/test_fetchparams.py:60: in test_fuzzing def test_fuzzing(s, t): /usr/lib/python3/dist-packages/hypothesis/core.py:886: in __flaky raise Flaky(message) E hypothesis.errors.Flaky: Hypothesis test_fuzzing(s='', t='74') produces unreliable results: Falsified on the first call but did not on a subsequent one - Captured stdout call - debug: Fetching value for .fetch with mystrategy strategy. debug: Fetching value for 0.fetch with mystrategy strategy. debug: Fetching value for 0.fetch with mystrategy strategy. debug: Fetching value for .fetch with mystrategy strategy. debug: Fetching value for 0.fetch with mystrategy strategy. debug: Fetching value for 0.fetch with mystrategy strategy. debug: Fetching value for 0.fetch with mystrategy strategy. debug: Fetching value for 0.fetch with mystrategy strategy. debug: Fetching value for .fetch with mystrategy strategy. debug: Fetching value for .fetch with mystrategy strategy. debug: Fetching value for .fetch with mystrategy strategy. debug: Fetching value for L.fetch with mystrategy strategy. debug: Fetching value for ᔽ<×ꁺK~.fetch with mystrategy strategy. debug: Fetching value for º.fetch with mystrategy strategy. debug: Fetching value for .fetch with mystrategy strategy. debug: Fetching value for IáðÙ=7ܷ.fetch with mystrategy strategy. debug: Fetching value for I.fetch with mystrategy strategy. debug: Fetching value for ఁÉ줊(.fetch with mystrategy strategy. debug: Fetching value for ꊈD)"Æ.fetch with mystrategy strategy. debug: Fetching value for "ᛞ.fetch with mystrategy strategy. debug: Fetching value for "ᛞ.fetch with mystrategy strategy. debug: Fetching value for .fetch with mystrategy strategy. debug: Fetching value for .fetch with mystrategy strategy. debug: Fetching value for .fetch with mystrategy strategy. debug: Fetching value for .fetch with mystrategy strategy. debug: Fetching value for ï㭰.fetch with mystrategy strategy. debug: Fetching value for 㭰㭰.fetch with mystrategy strategy. debug: Fetching value for .fetch with mystrategy strategy. debug: Fetching value for 젩 ¿憊<ꑕAÞ.fetch with mystrategy strategy. debug: Fetching value for .fetch with mystrategy strategy. debug: Fetching value for .fetch with mystrategy strategy. debug: Fetching value for .fetch with mystrategy strategy. debug: Fetching value for .fetch with mystrategy strategy. debug: Fetching value for .fetch with mystrategy strategy. debug: Fetching value for .fetch with mystrategy strategy. debug: Fetching value for .fetch with mystrategy strategy. debug: Fetching value for .fetch with mystrategy strategy. debug: Fetching value for .fetch with mystrategy strategy. debug: Fetching value for .fetch with mystrategy strategy. debug: Fetching value for ì.fetch with mystrategy strategy. debug: Fetching value for ì.fetch with mystrategy strategy. debug: Fetching value for 1.fetch with mystrategy strategy. debug: Fetching value for 1Ȁg.fetch with mystrategy strategy. debug: Fetching value for .fetch with mystrategy strategy. debug: Fetching value for .fetch with mystrategy strategy. debug: Fetching value for ༁4.fetch with mystrategy strategy. debug: Fetching value for .fetch with mystrategy strategy. debug: Fetching value for .fetch with mystrategy strategy. debug: Fetching value for .fetch with mystrategy strategy. debug: Fetching value for §2.fetch with mystrategy strategy. debug: Fetching value for .fetch with mystrategy strategy. debug: Fetching value for .fetch with mystrategy strategy. debug: Fetching value for ΆΆ.fetch with mystrategy strategy.
Bug#1005968: marked as pending in vdirsyncer
Control: tag -1 pending Hello, Bug #1005968 in vdirsyncer 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/vdirsyncer/-/commit/3f1224f15fd688ce0b9c1961c1c81028913c87cf avoid checking flaky test test_fuzzing; closes: bug#1005968, thanks to Luca Boccassi (this message was generated automatically) -- Greetings https://bugs.debian.org/1005968
Processed: Bug#1005968 marked as pending in vdirsyncer
Processing control commands: > tag -1 pending Bug #1005968 [src:vdirsyncer] vdirsyncer: flaky autopkgtest blocks migration of reverse deps Added tag(s) pending. -- 1005968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005968 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1005187: collectd build-depends on package that is not in testing.
On 22/02/2022 12:57, Bernd Zeimetz wrote: Hi, I fail to understand why you are opening this bug at all. rc bugs are how we track packages in testing that are not living up to the standards Debian sets and ultimately trigger their removal. "packages must be buildable within the same release" has been part of the rc policy for as long as I can remember. collectd would have been removed from testing automatically anyway, people are notified about that. To the best of my knowledge there is no mechanism to automatically remove packages with broken build-dependencies from testing. I certainly don't recall collectd being listed for autoremoval at the time I filed the bug. The auto-removals system does take account of reverse build-dependencies when deciding what extra removals to trigger, but unfortunately the same does not apply to manual removals by the release team. In particular the following scenario can happen. Package a build-depends (but does not depend) on package b. Package b is rc buggy. The autoremovals system sends out mails notifying maintainers that if the situation doesn't change, it will remove packages b and a Package b gets manually removed by the release team. The package with the rc bug is no longer in testing, so it drops off the autoremoval system's list of issues. Package a does not actually get autoremoved despite the earlier mail from the autoremovals system. I suspect that may well be what happened here (liboping was manually removed from testing as it was blocking the perl transition). It basically adds the extra work of tracking and closing this bug manually. I understand that and that is why I am selective about when I file such bugs. If I see indications that the underlying issue is likely to be fixed on a reasonable timescale, I generally will hold-off filing bugs on the reverse dependencies. In this case I saw no such indications. The bug report was over a month old with no maintainer response, and the package had not seen a maintainer upload in over a year. If you want to add such bugs, please link them properly to the bugs that caused the issue and make sure that it is closed automatically as soon as the issue is fixed. If the bts had a system to automatically close bugs when another package migrates to testing I would use it but afaict it doesn't. I am not going to build custom automation for such a small volume of bugs. It certainly makes sense to link to the underlying bug though, I'll try and remember that next time. I guess I could also set "blocks", but i'm not entirely convinced it's appropriate, it's the maintainers call not mine as to whether to fix the issue by fixing the unmaintained package they build-depend on or by eliminating the build-dependency on it.
Processed: retitle 1006290 to kvmtool: CVE-2021-45464: hypervisor escape and host code execution
Processing commands for cont...@bugs.debian.org: > retitle 1006290 kvmtool: CVE-2021-45464: hypervisor escape and host code > execution Bug #1006290 [src:kvmtool] kvmtoo: CVE-2021-45464: hypervisor escape and host code execution Changed Bug title to 'kvmtool: CVE-2021-45464: hypervisor escape and host code execution' from 'kvmtoo: CVE-2021-45464: hypervisor escape and host code execution'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1006290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006290 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1006131: marked as done (rus-ispell: please stop build-depending on myspell-tools)
Your message dated Tue, 22 Feb 2022 21:07:47 + with message-id and subject line Bug#1006131: fixed in rus-ispell 0.99g5-28 has caused the Debian Bug report #1006131, regarding rus-ispell: please stop build-depending on myspell-tools 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.) -- 1006131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006131 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rus-ispell Version: 0.99g5-27 Severity: serious Dear maintainer, we plan to remove src:myspell really soon, and together with it also the package "myspell-tools". Your package still depends on it. Please see whether you can move whatever the package is doing to hunspell-tools, or otherwise please tell us src:hunspell maintainers how that is not possible for you. Thank you for maintaining rus-ispell. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: rus-ispell Source-Version: 0.99g5-28 Done: Agustin Martin Domingo We believe that the bug you reported is fixed in the latest version of rus-ispell, 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 1006...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Agustin Martin Domingo (supplier of updated rus-ispell package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 22 Feb 2022 21:30:04 +0100 Source: rus-ispell Architecture: source Version: 0.99g5-28 Distribution: unstable Urgency: medium Maintainer: Mikhail Gusarov Changed-By: Agustin Martin Domingo Closes: 1006131 Changes: rus-ispell (0.99g5-28) unstable; urgency=medium . * Drop myspell-tools build-dep. Use hunspell-tools ispellaff2myspell to generate aspell affix file (Closes: #1006131). * debian/copyright: Make DEP5. Checksums-Sha1: 3b14e6bdaf2d34fec26f5366cd1c9dcea090626a 2095 rus-ispell_0.99g5-28.dsc c16677872d6a13972cc1db5b4294c0f874d03326 9516 rus-ispell_0.99g5-28.debian.tar.xz c15590b5cf0b762152685021af5f118a577200ad 6589 rus-ispell_0.99g5-28_amd64.buildinfo Checksums-Sha256: 5b2e326c2353a8da4870b5ffa432639009a45c1916bd16c1b84eb31da5c10d3e 2095 rus-ispell_0.99g5-28.dsc 21f073577e2c85229b66c3f18ee4adcecb9a69ad989ac6de6b4d9e9aacaad1bb 9516 rus-ispell_0.99g5-28.debian.tar.xz 02468ac959d8faf5fd31b5d33b3a7b5c315c94d3bbae0a8689be8bcbed83d0a4 6589 rus-ispell_0.99g5-28_amd64.buildinfo Files: 623d7997810931150a17b6723c7166fc 2095 text optional rus-ispell_0.99g5-28.dsc 0de85ec8467273e4b7bd551d08fb295b 9516 text optional rus-ispell_0.99g5-28.debian.tar.xz 84eaa1d0799bb3e574e5e2195bd7fc83 6589 text optional rus-ispell_0.99g5-28_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEEehey7p+gYd346SEFJrCLeiggvwFAmIVSCsACgkQFJrCLeig gvyL2hAAlVdFOdYavEJc1EPU5RsQ1luczIZkG/PAM7JWTb4t1LbCRAtstcujNCA2 oyjLJiSeoSc7bk1Cu3frX7etz/2vuFXFBbXqcGzkt9tfG/E7XfcYRvUY+05mi6iv LYTZQ4bXnbZANvzXN1H2AC6F85qZeY9U5njmQKlXh4rDBRzaRjf8Lp7aJ9h9BMrK Jzjcql5qxwkKrMr35cREXCtBrWpoqE7UHk07twsZckmsmxfqwwFl9O8Zmtnt+WfC i9w+wfR1/bg7PLFF6Ll+YMzL7HeBY1qzvOuX/gLfqFpY4DY2XaJehgGgMnIXUIMs /3K2o+iZ6mOPsFJv9hFtasbGOxv8xn/zsrXI4tjib+9faVhzxGW53f2/inFWUovC Q0gOPySzqvdn4i6ger+jR5rTaUZTLkoJrWmBJAefz57K1/VFVjAWNaxwZ6WCGHjD s62JrjFXkKunQ1JFkd37+AoYSynp4tSfpYrct0kUP3O0ysOLVJ2evH2nBbCKGlPO dDGg7wW5E1zJHfFnOukmzH02WcyRJIG+UMgJ4/Ht7z3K2hmW5x4xRHINpEQengCW H6ydUdfoevhqonCp/zY6qxx1IIad5WSye5MuKQbPrCQGuPikLxzFGmMlgxeKBJrq PjWDG49gYKfT/pbdksbnp/fs44UoYkCwk2c+ns15wSxBcgfRqEo= =FgXg -END PGP SIGNATURE End Message ---
Bug#1006289: marisa's autopkgtest regressed since rebuild for ruby3.0 as default
Source: marisa
Version: 0.2.6-8
Severity: serious
X-Debbugs-Cc: kanash...@debian.org, terce...@debian.org
Dear maintainer,
As part of the ongoing transition from ruby2.7 as default ruby to
ruby3.0 as default, your package got rebuild. In that rebuild it
correctly picked up a dependency on libruby3.0, but as it also depends
on ruby (unversioned) it seems to not be able to work in testing, as
seen by the autopkgtest regression.
I don't know what the best way forward is, but I think the right
version of ruby needs to be detected during build and included in
${misc:Depends} or something similar. I have included two ruby
maintainers in the X-Debbugs-CC for advice.
Paul
https://ci.debian.net/data/autopkgtest/testing/amd64/m/marisa/19472910/log.gz
[...]
Setting up libruby3.0:amd64 (3.0.2-7) ...
Setting up libruby2.7:amd64 (2.7.4-1+b1) ...
Setting up ruby2.7 (2.7.4-1+b1) ...
Setting up ruby (1:2.7.6) ...
[...]
autopkgtest [20:54:51]: test ruby: [---
=== ruby ===
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require':
cannot load such file -- marisa (LoadError)
from
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
from bindings/ruby/sample.rb:1:in `'
autopkgtest [20:54:51]: test ruby: ---]
Bug#1006290: kvmtoo: CVE-2021-45464: hypervisor escape and host code execution
Source: kvmtool Version: 0.20170904-1.1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for kvmtool. CVE-2021-45464[0]: | hypervisor escape and host code execution If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2021-45464 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45464 [1] https://www.kalmarunionen.dk/writeups/2021/hxp-2021/lkvm/ Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#1006219: new expat causes regressions in the python autopkg tests
Hi Matthias On Mon, Feb 21, 2022 at 09:35:06PM +0100, Matthias Klose wrote: > On 2/21/22 21:31, Salvatore Bonaccorso wrote: > > Control: forwarded -1 https://bugs.python.org/issue46811 > > Control: affects -1 + src:expat > > Control: clone -1 -2 -3 > > Control: reassign -1 src:python3.10 3.10.2-1 > > Control: reassign -2 src:python3.9 3.9.10-1 > > Control: reassign -3 src:python2.7 2.7.18-12 > > > > Hi László, hi Matthias, > > > > On Mon, Feb 21, 2022 at 08:44:26PM +0100, Salvatore Bonaccorso wrote: > >> Hi, > >> > >> On Mon, Feb 21, 2022 at 05:10:02PM +0100, László Böszörményi wrote: > >>> Control: tags -1 +confirmed > >>> > >>> Hi Matthias, > >>> > >>> On Mon, Feb 21, 2022 at 2:57 PM Matthias Klose wrote: > The new expat causes regressions in the python autopkg tests. I also see > there > is a new upstream 2.4.6. Didn't check that yet. > >>> Basically 2.4.5-2 and 2.4.6 should be identical. I can package the > >>> latter for you if you want. > >>> Will contact upstream about this and see what he finds. > >> > >> It looks this is actually an issue in python's testsuite. Upstream > >> report is at https://bugs.python.org/issue46811 and > >> https://github.com/python/cpython/pull/31453 . > > > > So given the above, I'm trying to reassign it now to the relevant > > python packages accordingly, bear with me that I have not done > > mistkaes with the control commands. > > thanks for looking at these. I'll prepare uploads soonish. many thanks! Regards, Salvatore
Bug#1005889: dbus: flaky autopkgtest on ppc64el: dbus/integration/transient-services.sh.test
Hi, On 21-02-2022 20:03, Paul Gevers wrote: I have a possible patch which I'll upload soon. Would you be able to schedule several consecutive runs on the affected hardware to make sure it's really fixed? 10 runs should be enough for a reasonable level of confidence. Sure, but anybody (with Salsa credentials) can schedule those jobs. Just hitting the retry button will do. Results should be fast too as they are scheduled with higher prio. 11 runs happened. None of them failed. Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: hivex: wrongly detects ruby versions during build
Processing control commands: > block 1004915 by -1 Bug #1004915 [release.debian.org] transition: ruby2.7-rm 1004915 was blocked by: 1005947 1001217 1001022 1006119 1005448 1005426 998499 1004915 was not blocking any bugs. Added blocking bug(s) of 1004915: 1006286 -- 1004915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004915 1006286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006286 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: ruby3.0
Processing commands for cont...@bugs.debian.org: > # no longer in testing > unblock 1004915 by 1001022 Bug #1004915 [release.debian.org] transition: ruby2.7-rm 1004915 was blocked by: 1001217 1005426 1001022 1006286 1005448 1006119 998499 1005947 1004915 was not blocking any bugs. Removed blocking bug(s) of 1004915: 1001022 > unblock 1004915 by 998499 Bug #1004915 [release.debian.org] transition: ruby2.7-rm 1004915 was blocked by: 1001217 1006119 1006286 1005448 998499 1005947 1005426 1004915 was not blocking any bugs. Removed blocking bug(s) of 1004915: 998499 > thanks Stopping processing here. Please contact me if you need assistance. -- 1004915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004915 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1006286: hivex: wrongly detects ruby versions during build
Source: hivex Version: 1.3.21-1 Severity: serious Tags: patch Justification: FTBFS Control: block 1004915 by -1 Dear maintainer, >From https://salsa.debian.org/libvirt-team/hivex/-/merge_requests/1 ''' It fixes a FTBFS against ruby3.0 (ongoing transition). This is the same patch proposed here to libguestfs: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998636 ''' This isn't totally true as it doesn't FTBFS (yet), but if fails to pick up a dependency on ruby3.0, which is now the default ruby, causing the transition to delay. Paul
Bug#981878: ruby-gitlab-pg-query downloads from the internet during the build
Hi Pirate, On Sun, 07 Mar 2021 00:47:46 +0530 Pirate Praveen wrote: Once ruby-pg-query is accepted and its reverse dependencies switch to the new package, I will request removal of this package. What's the status on this? Paul PS: please CC, I'm not subscribed OpenPGP_signature Description: OpenPGP digital signature
Bug#1006239: closing 1006239
close 1006239 3.9.10-2 thanks
Processed: cloning 1006219, reassign -1 to src:python3.7, found 1006239 in 3.9.2-1, found 1006240 in 2.7.18-8 ...
Processing commands for cont...@bugs.debian.org:
> clone 1006219 -1
Bug #1006219 {Done: Matthias Klose } [src:python3.10] new
expat causes regressions in the python autopkg tests
Bug 1006219 cloned as bug 1006285
> # for oldstable as we need to fix it in a point release
> reassign -1 src:python3.7 3.7.3-2+deb10u3
Bug #1006285 {Done: Matthias Klose } [src:python3.10] new
expat causes regressions in the python autopkg tests
Bug reassigned from package 'src:python3.10' to 'src:python3.7'.
No longer marked as found in versions python3.10/3.10.2-1.
No longer marked as fixed in versions python3.10/3.10.2-2.
Bug #1006285 {Done: Matthias Klose } [src:python3.7] new expat
causes regressions in the python autopkg tests
Marked as found in versions python3.7/3.7.3-2+deb10u3.
> found 1006239 3.9.2-1
Bug #1006239 [src:python3.9] new expat causes regressions in the python autopkg
tests
Marked as found in versions python3.9/3.9.2-1.
> found 1006240 2.7.18-8
Bug #1006240 {Done: Matthias Klose } [src:python2.7] new expat
causes regressions in the python autopkg tests
Marked as found in versions python2.7/2.7.18-8.
> found 1006240 2.7.16-2+deb10u1
Bug #1006240 {Done: Matthias Klose } [src:python2.7] new expat
causes regressions in the python autopkg tests
Marked as found in versions python2.7/2.7.16-2+deb10u1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1006219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006219
1006239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006239
1006240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006240
1006285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006285
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: closing 1006239
Processing commands for cont...@bugs.debian.org: > close 1006239 3.9.10-2 Bug #1006239 [src:python3.9] new expat causes regressions in the python autopkg tests Marked as fixed in versions python3.9/3.9.10-2. Bug #1006239 [src:python3.9] new expat causes regressions in the python autopkg tests Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1006239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006239 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1005537: marked as done (tilix: FTBFS: ../data/meson.build:13:0: ERROR: Function does not take positional arguments.)
Your message dated Tue, 22 Feb 2022 19:35:20 + with message-id and subject line Bug#1005537: fixed in tilix 1.9.5-1 has caused the Debian Bug report #1005537, regarding tilix: FTBFS: ../data/meson.build:13:0: ERROR: Function does not take positional arguments. 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.) -- 1005537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005537 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tilix Version: 1.9.4-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220212 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 build --with gnome --buildsystem=meson >dh_update_autotools_config -O--buildsystem=meson >dh_autoreconf -O--buildsystem=meson >dh_auto_configure -O--buildsystem=meson > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu > The Meson build system > Version: 0.61.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: Tilix > Project version: 1.9.4 > D compiler for the host machine: ldc2 (llvm 1.28.0 "LDC - the LLVM D compiler > (1.28.0):") > D linker for the host machine: ldc2 ld.gold 2.38 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Found pkg-config: /usr/bin/pkg-config (0.29.2) > Run-time dependency gtkd-3 found: YES 3.10.0 > Run-time dependency vted-3 found: YES 3.10.0 > Run-time dependency x11 found: YES 1.7.2 > Run-time dependency libunwind found: YES 1.3.2 > Run-time dependency libsecret-1 found: YES 0.20.4 > > ../data/meson.build:13:0: ERROR: Function does not take positional arguments. > > A full log can be found at > /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt > cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt > ==> meson-logs/meson-log.txt <== > Build started at 2022-02-12T22:38:44.794742 > Main binary: /usr/bin/python3 > Build Options: -Dprefix=/usr -Dlibdir=lib/x86_64-linux-gnu > -Dlocalstatedir=/var -Dsysconfdir=/etc -Dbuildtype=plain > -Dwrap_mode=nodownload > Python system: Linux > The Meson build system > Version: 0.61.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: Tilix > Project version: 1.9.4 > D compiler for the host machine: ldc2 (llvm 1.28.0 "LDC - the LLVM D compiler > (1.28.0):") > D linker for the host machine: ldc2 ld.gold 2.38 > D compiler for the build machine: ldc2 (llvm 1.28.0 "LDC - the LLVM D > compiler (1.28.0):") > D linker for the build machine: ldc2 ld.gold 2.38 > Build machine cpu family: x86_64 > Build machine cpu: x86_64 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Target machine cpu family: x86_64 > Target machine cpu: x86_64 > Pkg-config binary for 1 is not cached. > Pkg-config binary missing from cross or native file, or env var undefined. > Trying a default Pkg-config fallback at pkg-config > Found pkg-config: /usr/bin/pkg-config (0.29.2) > Determining dependency 'gtkd-3' with pkg-config executable > '/usr/bin/pkg-config' > env[PKG_CONFIG_PATH]: > Called `/usr/bin/pkg-config --modversion gtkd-3` -> 0 > 3.10.0 > env[PKG_CONFIG_PATH]: > Called `/usr/bin/pkg-config --cflags gtkd-3` -> 0 > -pthread -I/usr/include/d/gtkd-3/ -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/atk-1.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/librsvg-2.0 > -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 > -I/usr/include/x86_64-linux-gnu -I/usr/include/cairo -I/usr/include/pixman-1 > -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 > -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 > env[PKG_CONFIG_ALLOW_SYSTEM_LIBS]: 1 > env[PKG_CONFIG_PATH]: > Called `/usr/bin/pkg-config --libs gtkd-3` -> 0 > -L-L/usr/lib/x86_64-linux-gnu/ -L-lgtkd-3 -L-ldl -L/usr/lib/x86_64-linux-gnu > -lgtk-3 -lgdk-3 -latk-1.0 -lcairo-gobject -lpangocairo-1.0 -lpango-1.0 > -lharfbuzz -lrsvg-2 -lm -lgdk_pixbuf-2.0 -lcairo -lgio-2.0 -lgobject-2.0 >
Bug#1005658: marked as done (unison-2.51+4.11.1: FTBFS: detects changes in debian/control)
Your message dated Tue, 22 Feb 2022 19:11:33 +
with message-id
and subject line Bug#1006259: Removed package(s) from unstable
has caused the Debian Bug report #1005658,
regarding unison-2.51+4.11.1: FTBFS: detects changes in debian/control
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.)
--
1005658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005658
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: unison-2.51+4.11.1
Version: 2.51.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220212 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 '/<>'
> sed -e "s/@UnisonVersion@/2.51/g" -e "s/@UnisonABI@/2.51+4.13.1/g"
> debian/control.in > debian/control.new
> diff -u debian/control debian/control.new
> --- debian/control2020-10-15 11:46:52.0 +
> +++ debian/control.new2022-02-12 22:42:04.954069034 +
> @@ -1,4 +1,4 @@
> -Source: unison-2.51+4.11.1
> +Source: unison-2.51+4.13.1
> Section: utils
> Priority: optional
> Maintainer: Debian OCaml Maintainers
> @@ -17,7 +17,7 @@
> Vcs-Browser: https://salsa.debian.org/ocaml-team/unison/-/tree/2.51/debian
> Homepage: http://www.cis.upenn.edu/~bcpierce/unison/
>
> -Package: unison-2.51+4.11.1
> +Package: unison-2.51+4.13.1
> Architecture: any
> Depends: ${shlibs:Depends}, ${ocaml:Depends}, ${misc:Depends}
> Recommends: ssh-client | openssh-client
> @@ -43,9 +43,9 @@
> specification, and is resilient to failure due to its careful
> handling of the replicas and its private structures.
>
> -Package: unison-2.51+4.11.1-gtk
> +Package: unison-2.51+4.13.1-gtk
> Architecture: any
> -Depends: unison-2.51+4.11.1, ${shlibs:Depends}, ${ocaml:Depends},
> ${misc:Depends}
> +Depends: unison-2.51+4.13.1, ${shlibs:Depends}, ${ocaml:Depends},
> ${misc:Depends}
> Recommends: ssh-askpass, ssh-client | openssh-client
> Breaks: unison-gtk (<< 2.48.4-5~)
> Replaces: unison-gtk (<< 2.48.4-5~)
> make[1]: *** [debian/rules:34: override_dh_auto_configure] Error 1
The full build log is available from:
http://qa-logs.debian.net/2022/02/12/unison-2.51+4.11.1_2.51.3-1_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 ---
Version: 2.51.3-1+rm
Dear submitter,
as the package unison-2.51+4.11.1 has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1006259
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1006046: marked as done (ignition-tools: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2)
Your message dated Tue, 22 Feb 2022 18:18:27 +0100 with message-id and subject line Re: Bug#1006046: ignition-tools: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2 has caused the Debian Bug report #1006046, regarding ignition-tools: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 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.) -- 1006046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006046 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ignition-tools Version: 1.4.1+dfsg-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>/obj-x86_64-linux-gnu' > Running tests... > /usr/bin/ctest --force-new-ctest-process --verbose -j8 > UpdateCTestConfiguration from > :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl > Parse Config file:/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl > UpdateCTestConfiguration from > :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl > Parse Config file:/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl > Test project /<>/obj-x86_64-linux-gnu > Constructing a list of tests > Done constructing a list of tests > Updating test list for fixtures > Added 0 tests to meet fixture requirements > Checking test dependency graph... > Checking test dependency graph end > test 1 > Start 1: UNIT_ign_TEST > > 1: Test command: /usr/bin/cmake "-DTEST_NAME=UNIT_ign_TEST" > "-DIGN_SCRIPT=/<>/obj-x86_64-linux-gnu/None/test/bin/ign" "-P" > "/<>/cmake/run_test.cmake" > 1: Environment variables: > 1: IGN_CONFIG_PATH=/<>/obj-x86_64-linux-gnu/test/conf/None > 1: Test timeout computed to be: 1500 > 1: CMake Error at /<>/cmake/run_test.cmake:24 (message): > 1: Failed test. > 1: > 1: Output: > 1: Error: > 1: > 1: > 1/1 Test #1: UNIT_ign_TEST ***Failed0.02 sec > CMake Error at /<>/cmake/run_test.cmake:24 (message): > Failed test. > > Output: > Error: > > > > > 0% tests passed, 1 tests failed out of 1 > > Total Test time (real) = 0.03 sec > > The following tests FAILED: > 1 - UNIT_ign_TEST (Failed) > Errors while running CTest > make[1]: *** [Makefile:94: test] Error 8 > make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu' > dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test > ARGS\+=--verbose ARGS\+=-j8 returned exit code 2 The full build log is available from: http://qa-logs.debian.net/2022/02/18/ignition-tools_1.4.1+dfsg-1_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 --- fixed in 1.4.1+dfsg-2 On Sat, Feb 19, 2022 at 7:46 AM Lucas Nussbaum wrote: > Source: ignition-tools > Version: 1.4.1+dfsg-1 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): > > make[1]: Entering directory '/<>/obj-x86_64-linux-gnu' > > Running tests... > > /usr/bin/ctest --force-new-ctest-process --verbose -j8 > > UpdateCTestConfiguration from > :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl > > Parse Config > file:/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl > > UpdateCTestConfiguration from > :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl > > Parse Config > file:/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl > > Test project /<>/obj-x86_64-linux-gnu > > Constructing a list of tests > > Done constructing a list of tests > > Updating test list for fixtures > > Added 0 tests to meet fixture requirements > > Checking test dependency graph... > > Checking test dependency graph end > > test 1 > > Start 1: UNIT_ign_TEST > > > > 1: Test command: /usr/bin/cmake "-DTEST_NAME=UNIT_ign_TEST" > "-DIGN_SCRIPT=/<>/obj-x86_64-linux-gnu/None/test/bin/ign" "-P" > "/<>/cmake/run_test.cmake" > > 1: Environment variables: > > 1: IGN_CONFIG_PATH=/<>/obj-x86_64-linux-gnu/test/conf/None > > 1: Test timeout computed to be: 1500 > > 1: CMake
Processed: reassign 1004990 to golang-github-containers-dnsname, forcibly merging 985549 1004990
Processing commands for cont...@bugs.debian.org:
> reassign 1004990 golang-github-containers-dnsname 1.1.1+ds1-4
Bug #1004990 [golang-github-containernetworking-plugin-dnsname]
golang-github-containernetworking-plugin-dnsname: podman does not use the
dnsname plugin because the executable is in wrong directory
Bug reassigned from package 'golang-github-containernetworking-plugin-dnsname'
to 'golang-github-containers-dnsname'.
No longer marked as found in versions
golang-github-containers-dnsname/1.1.1+ds1-4.
Ignoring request to alter fixed versions of bug #1004990 to the same values
previously set
Bug #1004990 [golang-github-containers-dnsname]
golang-github-containernetworking-plugin-dnsname: podman does not use the
dnsname plugin because the executable is in wrong directory
There is no source info for the package 'golang-github-containers-dnsname' at
version '1.1.1+ds1-4' with architecture ''
Unable to make a source version for version '1.1.1+ds1-4'
Marked as found in versions 1.1.1+ds1-4.
> forcemerge 985549 1004990
Bug #985549 {Done: Leo Antunes }
[golang-github-containers-dnsname] golang-github-containers-dnsname: Incorrect
installation path for dnsname binary
Bug #1004990 [golang-github-containers-dnsname]
golang-github-containernetworking-plugin-dnsname: podman does not use the
dnsname plugin because the executable is in wrong directory
Severity set to 'normal' from 'grave'
Marked Bug as done
Marked as fixed in versions golang-github-containers-dnsname/1.3.1+ds1-1.
Merged 985549 1004990
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1004990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004990
985549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985549
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1004556: libmpich-dev: The simplest MPI program compiled with mpich crashes
Package: mpich Followup-For: Bug #1004556 My guess is that this bug is ongoing in 4.0-2 because of pmix support. 4.0-2 is still configured --with-pmix=/usr/lib/x86_64-linux-gnu/pmix2 and still Depends: libpmix2 (>= 4.1.2) pmix support was added in 4.0~b1-2 along with ucx. I gather ucx was deactivated in 4.0-2 but pmix was not. Looks like pmix also needs to go (unless the problem is ch4, which was also added in 4.0~b1-2). But the error message references PMIX. Ironically, I find that an executable compiled against mpich 4.0-1 fails with mpiexec.mpich (as raised in this bug) but actually passes when run with mpiexec.openmpi. Awkward.
Processed (with 2 errors): reassign 1004990 to golang-github-containers-dnsname/1.1.1+ds1-4, forcibly merging 985549 1004990
Processing commands for cont...@bugs.debian.org:
> reassign 1004990 golang-github-containers-dnsname/1.1.1+ds1-4
Unknown command or malformed arguments to command.
> forcemerge 985549 1004990
Bug #985549 {Done: Leo Antunes }
[golang-github-containers-dnsname] golang-github-containers-dnsname: Incorrect
installation path for dnsname binary
Unable to merge bugs because:
package of #1004990 is 'golang-github-containernetworking-plugin-dnsname' not
'golang-github-containers-dnsname'
Failed to forcibly merge 985549: Did not alter merged bugs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1004990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004990
985549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985549
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed (with 1 error): unarchiving 985549, forcibly merging 985549 1004990
Processing commands for cont...@bugs.debian.org:
> unarchive 985549
Bug #985549 {Done: Leo Antunes }
[golang-github-containers-dnsname] golang-github-containers-dnsname: Incorrect
installation path for dnsname binary
Unarchived Bug 985549
> forcemerge 985549 1004990
Bug #985549 {Done: Leo Antunes }
[golang-github-containers-dnsname] golang-github-containers-dnsname: Incorrect
installation path for dnsname binary
Unable to merge bugs because:
package of #1004990 is 'golang-github-containernetworking-plugin-dnsname' not
'golang-github-containers-dnsname'
Failed to forcibly merge 985549: Did not alter merged bugs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1004990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004990
985549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985549
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1005446: marked as done (ruby-clockwork: FTBFS: ERROR: Test "ruby2.7" failed.)
Your message dated Tue, 22 Feb 2022 16:33:55 + with message-id and subject line Bug#1005446: fixed in ruby-clockwork 2.0.4-2 has caused the Debian Bug report #1005446, regarding ruby-clockwork: FTBFS: ERROR: Test "ruby2.7" failed. 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.) -- 1005446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005446 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-clockwork Version: 2.0.4-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220212 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ruby2.7 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby2.7 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-clockwork/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 > ruby2.7 -e gem\ \"clockwork\" > > ┌──┐ > │ Run tests for ruby2.7 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=/<>/debian/ruby-clockwork/usr/lib/ruby/vendor_ruby:. > GEM_PATH=/<>/debian/ruby-clockwork/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 > ruby2.7 -S rake -f debian/ruby-tests.rake > /usr/bin/ruby2.7 -w -I"test" > /usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb > "test/at_test.rb" "test/clockwork_test.rb" > "test/database_events/event_store_test.rb" > "test/database_events/synchronizer_test.rb" "test/event_test.rb" > "test/manager_test.rb" "test/samples/signal_test.rb" > "test/database_events/test_helpers.rb" -v > /<>/test/database_events/support/active_record_fake.rb:32: > warning: `*' interpreted as argument prefix > /<>/test/database_events/test_helpers.rb:41: warning: method > redefined; discarding old name > /<>/test/database_events/test_helpers.rb:50: warning: method > redefined; discarding old name > /<>/test/database_events/test_helpers.rb:64: warning: method > redefined; discarding old name > Run options: -v --seed 258 > > # Running: > > Clockwork::Manager:::at option#test_0002_twice a day at 16:20 and 18:10 = > 0.00 s = . > Clockwork::Manager:::at option#test_0001_once a day at 16:20 = 0.00 s = . > Clockwork::Event::#thread?::manager config thread option set to > true#test_0001_is true = 0.00 s = . > Clockwork::Event::#thread?::manager config thread option set to > true#test_0002_is false when event thread option set = 0.00 s = . > Clockwork::At#test_0005_16:** = 0.00 s = . > Clockwork::At#test_0009_invalid time 32:00 = 0.00 s = . > Clockwork::At#test_0001_16:20 = 0.00 s = . > Clockwork::At#test_0003_**:20 with two stars = 0.00 s = . > Clockwork::At#test_0013_invalid multi-line with 12:** = 0.00 s = . > Clockwork::At#test_0010_invalid multi-line with Sat 12:00 = 0.00 s = . > Clockwork::At#test_0007_Saturday 12:00 = 0.00 s = . > Clockwork::At#test_0012_invalid multi-line with *:10 = 0.00 s = . > Clockwork::At#test_0008_sat 12:00 = 0.00 s = . > Clockwork::At#test_0011_invalid multi-line with 8:30 = 0.00 s = . > Clockwork::At#test_0002_8:20 = 0.00 s = . > Clockwork::At#test_0004_*:20 with one star = 0.00 s = . > Clockwork::At#test_0006_8:** = 0.00 s = . > Clockwork::Event::#run_now?::event skip_first_run option set to > true#test_0001_returns false on first attempt = 0.00 s = . > Clockwork::Event::#run_now?::event skip_first_run option set to > true#test_0002_returns true on subsequent attempts = 0.00 s = . > Clockwork::Manager::error_handler#test_0001_registered error_handler handles > error from event = 0.00 s = . > Clockwork::Manager::error_handler#test_0002_error is notified to logger and > handler = 0.00 s = . > Clockwork::Manager::error_handler#test_0003_error in handler will NOT be > suppressed = 0.00 s = . >
Bug#1006219: marked as done (new expat causes regressions in the python autopkg tests)
Your message dated Tue, 22 Feb 2022 14:43:05 + with message-id and subject line Bug#1006219: fixed in python3.10 3.10.2-2 has caused the Debian Bug report #1006219, regarding new expat causes regressions in the python autopkg tests 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.) -- 1006219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006219 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:expat Version: 2.4.5-2 Severity: serious Tags: sid bookworm The new expat causes regressions in the python autopkg tests. I also see there is a new upstream 2.4.6. Didn't check that yet. See https://tracker.debian.org/pkg/expat --- End Message --- --- Begin Message --- Source: python3.10 Source-Version: 3.10.2-2 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of python3.10, 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 1006...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated python3.10 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 22 Feb 2022 14:57:42 +0100 Source: python3.10 Architecture: source Version: 3.10.2-2 Distribution: unstable Urgency: medium Maintainer: Matthias Klose Changed-By: Matthias Klose Closes: 1004558 1005761 1006219 Changes: python3.10 (3.10.2-2) unstable; urgency=medium . * Make test suite support Expat >=2.4.5. Closes: #1006219. * Build again using readline instead of libedit. Closes: #1005761. * Serialize frozenset elements deterministically, taken from the trunk. Closes: #1004558. Checksums-Sha1: 16965d4aecc7b3b3996fb2e4516f534212847772 3500 python3.10_3.10.2-2.dsc f314fdac6d5d1973bc262d04adddcb05e9fba695 213904 python3.10_3.10.2-2.debian.tar.xz ea1f7154367be0608a0c9f6467c2b239c66c9b1b 9694 python3.10_3.10.2-2_source.buildinfo Checksums-Sha256: c73c292188e620a18666019b764076c8303190be0ca4721530fa0167eb66e696 3500 python3.10_3.10.2-2.dsc 2a57f709175ee19e31ed26ab1bef4ff213320e8654f4e7129588524d43bf6a62 213904 python3.10_3.10.2-2.debian.tar.xz 49ec4aebab69cac5c0fd4ab64e0b6b8327ab28b1895ea037d9700ea2cd2ef2b7 9694 python3.10_3.10.2-2_source.buildinfo Files: 5fb2ac914f24149c34804c9366a6e122 3500 python optional python3.10_3.10.2-2.dsc e2863f1cb9f1485ca17b584b66deb166 213904 python optional python3.10_3.10.2-2.debian.tar.xz e5bb4d2e03457bbea69c304e22e5d8cf 9694 python optional python3.10_3.10.2-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmIU7sYQHGRva29AZGVi aWFuLm9yZwAKCRC9fqpgd4+m9bYVEACRwaLV+6dkBXtZMDmRxsW861N2Oo7Fzu9X Ne5IPdCafWVstZuM5NRreV3eiLjaIjS0JBJjpG7/u+bpEKABl9qUjANjcTMIYkJ+ a6lPtmTc3OKKthxatOVVVtnu70qB75Hg5h4J5j5gQWHdYkkDtSQ62v/jOk/76EaQ x7bRW+3GjajM8Lhu4tpikSlVMC13F6d4E5wbF+3paSpvGxKpO+0GmEb2DRr+nMC1 lznqA18hiHaFhPBQg2m0FJJUTpx+m3j1GXYmtWopOG8yYv1sLRCorSohrHxMm/vB yXKlzEH6ppboL3iajoCcPFe36r7S9P4GLRJrtLE10QPFM9bIxIn/rmRnGUARxO8t o7vFf0v97D41a1qfjBXFYQu+4fcKHGaET8CSJoBDbZ6Ux4GhoTFAQH9hR0J40oKZ iOHuR5CZo8BDNVFI7t6ggRXqPIsclE2jcOLWEZ2eB095BAmSwdSznnRoawLGvV+I HdCbcNWmRSImO/YlPlUtgL7y98u78NeUGT2XO0DJNRX0Jnp7uOmKnYJXAaB2lKG2 98yyj2DCZKIGqSvnWMHqej9MsLNA14LTruzVwqc5Ak0IQsKxm6bhz4E8zMtBuP5b Lr5BBGDDyS0PTXFpSmg10l9i/1v/6xzpZOkY+YmHw7mAz7oPmqJcqNvZVDAvEXLs vyhKpWwuTA== =GCVU -END PGP SIGNATURE End Message ---
Bug#954443: marked as done (jp: name conflict of /usr/bin/jp with sat-xmpp-jp)
Your message dated Tue, 22 Feb 2022 14:06:24 + with message-id <87ley30yu2@fama.lan> and subject line jp: name conflict of /usr/bin/jp with sat-xmpp-jp has caused the Debian Bug report #904742, regarding jp: name conflict of /usr/bin/jp with sat-xmpp-jp 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.) -- 904742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904742 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: jp Version: 0.1.3-1+b10 jp includes /usr/bin/jp, which is already "taken" since ~2013 by something completely different, sat-xmpp-jp. Given that jp has not yet been part of Debian release, it is probably easy to just rename the binary, e.g. jp-cli, jp-jmespath, or jmespath. Thanks! --- End Message --- --- Begin Message --- The program jp (package sat-xmpp-jp) has been renamed to libervia-cli (package libervia-cli). Problem solved.--- End Message ---
Bug#904742: marked as done (jp: name conflict of /usr/bin/jp with sat-xmpp-jp)
Your message dated Tue, 22 Feb 2022 14:06:24 + with message-id <87ley30yu2@fama.lan> and subject line jp: name conflict of /usr/bin/jp with sat-xmpp-jp has caused the Debian Bug report #904742, regarding jp: name conflict of /usr/bin/jp with sat-xmpp-jp 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.) -- 904742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904742 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: jp Version: 0.1.3-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. The new package should probably rename its binary, unless you come to an agreement with the existing user of that path. Breaks/Conflicts/Replaces are *NOT* a soution in this case. >From the attached log (scroll to the bottom...): Selecting previously unselected package jp. Preparing to unpack .../archives/jp_0.1.3-1_amd64.deb ... Unpacking jp (0.1.3-1) ... dpkg: error processing archive /var/cache/apt/archives/jp_0.1.3-1_amd64.deb (--unpack): trying to overwrite '/usr/bin/jp', which is also in package sat-xmpp-jp 0.6.1.1+hg20180228-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/jp_0.1.3-1_amd64.deb cheers, Andreas sat-xmpp-jp=0.6.1.1+hg20180228-1_jp=0.1.3-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- The program jp (package sat-xmpp-jp) has been renamed to libervia-cli (package libervia-cli). Problem solved.--- End Message ---
Bug#904742: jp: name conflict of /usr/bin/jp with sat-xmpp-jp
The program jp (package sat-xmpp-jp) has been renamed to libervia-cli (package libervia-cli). Problem solved.
Bug#1005920: marked as done (coq-doc: FTBFS: Error: Library "zarith" not found.)
Your message dated Tue, 22 Feb 2022 13:33:54 + with message-id and subject line Bug#1005920: fixed in coq-doc 8.15.0-3 has caused the Debian Bug report #1005920, regarding coq-doc: FTBFS: Error: Library "zarith" 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.) -- 1005920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005920 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: coq-doc Version: 8.15.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, I cannot rebuild coq-doc in sid (minimal pbuilder chroot), it fails with [...] dh binary --with sphinxdoc dh_update_autotools_config dh_autoreconf debian/rules override_dh_auto_build make[1]: Entering directory '/build/coq-doc-8.15.0' dune build @refman-html @refman-pdf --display=verbose Workspace root: /build/coq-doc-8.15.0 Running[0]: /usr/bin/nproc > /tmp/dune0e9ce7.output 2> /dev/null Auto-detected concurrency: 16 disable binary cache Running[1]: /usr/bin/ocamlc.opt -config > /tmp/duneedc787.output [...] Running[1244]: (cd _build/default && tools/configure/configure.exe -no-ask -native-compiler no -bin-annot) [...] Command [1244] exited with code 1: $ (cd _build/default && tools/configure/configure.exe -no-ask -native-compiler no -bin-annot) ocamlfind: Package `zarith' not found Error while running '/usr/bin/ocamlfind query zarith -format %v' (exit code 2) Configuration script failed! File "interp/dune", line 6, characters 12-18: 6 | (libraries zarith pretyping)) ^^ Error: Library "zarith" not found. Hint: try: dune external-lib-deps --missing --display verbose @refman-html @refman-pdf make[1]: *** [debian/rules:9: override_dh_auto_build] Error 1 [...] Andreas coq-doc_8.15.0-1_sid.build.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: coq-doc Source-Version: 8.15.0-3 Done: Julien Puydt We believe that the bug you reported is fixed in the latest version of coq-doc, 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 1005...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Puydt (supplier of updated coq-doc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 22 Feb 2022 14:02:25 +0100 Source: coq-doc Binary: coq-doc coq-doc-html coq-doc-pdf Architecture: source all Version: 8.15.0-3 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Julien Puydt Description: coq-doc- documentation for Coq coq-doc-html - documentation for Coq in html format coq-doc-pdf - documentation for Coq in pdf format Closes: 1005920 Changes: coq-doc (8.15.0-3) unstable; urgency=medium . * Fix b-deps again (Closes: #1005920). Checksums-Sha1: 9a4863315a8588f3dc42308f6861794fc1640b66 2554 coq-doc_8.15.0-3.dsc c988c5eab24607a2193eb56b16c7b515002e6e1b 7600 coq-doc_8.15.0-3.debian.tar.xz deb82347022764be625cf88532db3ff83a3b9082 1419864 coq-doc-html_8.15.0-3_all.deb b5a6a9067bca7917cd677f1ed64c210697a3c76f 4065372 coq-doc-pdf_8.15.0-3_all.deb 122b53266462daac288102a04f909b8e046370b0 6484 coq-doc_8.15.0-3_all.deb 508194bda0f821298477ce33cc0e97aef73fd299 13368 coq-doc_8.15.0-3_amd64.buildinfo Checksums-Sha256: 738df330b2eeb0b1cba3e8c7852253cfab2ca595b8376e4e420578df9afd43b7 2554 coq-doc_8.15.0-3.dsc 215ec135c804ec5fe7788c56efca77378fbfc92cee61f8ea9e68f58576472fb9 7600 coq-doc_8.15.0-3.debian.tar.xz 9b5f7e65f4b0aa0f633e1dbe3350db4eb49640123be9d75534a760fd5f1e216e 1419864 coq-doc-html_8.15.0-3_all.deb e342d7620a4b1f6545c7ba1b8a2684ce0f1dd7d5b38bbde11913b12598a51554 4065372 coq-doc-pdf_8.15.0-3_all.deb e7ef103d650e7637a7ddca9dd1da2d777d237f6346f9cb9c75d8834c91387034 6484 coq-doc_8.15.0-3_all.deb 22cddc8a128520b93dcb2615c3839599c8c31cb58d10bee45d7d3a52c315fa16 13368 coq-doc_8.15.0-3_amd64.buildinfo Files: 0186ed69112aafb5ec43f2c4e144ded0 2554 non-free/doc optional coq-doc_8.15.0-3.dsc ecbbf32e0a19e11ddbf511c83022f00a 7600 non-free/doc optional coq-doc_8.15.0-3.debian.tar.xz 56470b77a3d65025fb9e555f8bdbb1bf 1419864 non-free/doc optional coq-doc-html_8.15.0-3_all.deb
Processed: block 1006098 with 1005640
Processing commands for cont...@bugs.debian.org: > block 1006098 with 1005640 Bug #1006098 [src:fonts-jetbrains-mono] fonts-jetbrains-mono: FTBFS: pkg_resources.DistributionNotFound: The 'unicodedata2>=14.0.0' distribution was not found and is required by fonttools 1006098 was not blocked by any bugs. 1006098 was not blocking any bugs. Added blocking bug(s) of 1006098: 1005640 > thanks Stopping processing here. Please contact me if you need assistance. -- 1006098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006098 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1006240: marked as done (new expat causes regressions in the python autopkg tests)
Your message dated Tue, 22 Feb 2022 13:20:45 + with message-id and subject line Bug#1006240: fixed in python2.7 2.7.18-13 has caused the Debian Bug report #1006240, regarding new expat causes regressions in the python autopkg tests 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.) -- 1006240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006240 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:expat Version: 2.4.5-2 Severity: serious Tags: sid bookworm The new expat causes regressions in the python autopkg tests. I also see there is a new upstream 2.4.6. Didn't check that yet. See https://tracker.debian.org/pkg/expat --- End Message --- --- Begin Message --- Source: python2.7 Source-Version: 2.7.18-13 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of python2.7, 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 1006...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated python2.7 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 22 Feb 2022 12:45:08 +0100 Source: python2.7 Architecture: source Version: 2.7.18-13 Distribution: unstable Urgency: medium Maintainer: Matthias Klose Changed-By: Matthias Klose Closes: 1006240 Changes: python2.7 (2.7.18-13) unstable; urgency=medium . * Skip tests requiring TLS 1.2 under OpenSSL 3. * Test suite adjustments for Expat >=2.4.5. Closes: #1006240. Checksums-Sha1: 7522b198103403b4b82f9e80b8d7b669f41f7540 3332 python2.7_2.7.18-13.dsc ba596cfc144c719a4d0f7d80fd8c8a9b4f5e68b3 376678 python2.7_2.7.18-13.diff.gz ecbf14f89dc87103be8a5e5da32716e10479be68 9695 python2.7_2.7.18-13_source.buildinfo Checksums-Sha256: 88458e50108cf5893990c0aedaf8c101f983ed916e2038927b467cd45ac3d707 3332 python2.7_2.7.18-13.dsc 80d08c8293cbd06fb955ec25dd3327d75571579fa290474e80e66343f06b2aa4 376678 python2.7_2.7.18-13.diff.gz 7855d831e17ab85e88bc268b74e87eb7191c8cf7640eae19c6cae6d942678084 9695 python2.7_2.7.18-13_source.buildinfo Files: af4e40cf953968d51739d1876b2f13f9 3332 python optional python2.7_2.7.18-13.dsc e2638ed629c31954a12587c79f94cd20 376678 python optional python2.7_2.7.18-13.diff.gz 91815918e2d09af3df68eac264f22a5f 9695 python optional python2.7_2.7.18-13_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmIU4JkQHGRva29AZGVi aWFuLm9yZwAKCRC9fqpgd4+m9Vl5EACsmCRVsjOHgAdDsyCt7tj7njSq9cGRY9GI hwtf97FOfd/Z+s3RCJ4OfStO0XGFsshOljZtYjvkyYANhIqiDaFvcbKB7NBZyw+v J2eBtwEvI916alg/f9D/2hTmHpFnnLprmizq0ivUM6A5TZJWa1IDsdFRzpZMIgZk jfjBNc2qZh6NQ0Wq/1LM6gjuQdKLX+pnlCzTcoVAn0QGmcX4oq1+Rwz7nNpBVzUh Fj5lZafMpTLIW8sdSyUk9CXP1WBZ53O3MZH3lIGv4o3C4gVKcA+P3hRECcc52QF/ xIBpWgU0vbyRKLtgN5btgFLqcDmCyK5JMZ8Err5FdjOgLD6H7th5347vE+enm7ek rbDXZ7yZFb1NB/Eovltd1nBKhr14UAxlNV4uJ5256VI4HuR1Ly8bHxR3erMBfe3U K/caWL/3bHxRlX58RhGWkDRP0pnelrBz91Z/KFXNFFMqPjO3cP6n7JUMMBV920ux jc79vvDtGMz/mBeG8gVoVPp/yLwHc6lf5G/oyKjpkETzyr5J4CBd5zSfuzGbuj6l QSnONus87q3QkP6j14GMeXj/3gklopV1Ut5681le73SvnWjSbswzzFjZSUictF38 Ubl79X4UiG70O23MJY1zOJ2zw50zS7Rwuww8Qfh8Ka1nlnkLXCmX8HaotqzYb6q3 SsJEckKgqw== =6d74 -END PGP SIGNATURE End Message ---
Bug#1005440: marked as done (ruby-liquid-c: FTBFS: ERROR: Test "ruby2.7" failed: /<>/test/liquid_test.rb:8:in `': uninitialized constant FileList (NameError))
Your message dated Tue, 22 Feb 2022 13:20:53 + with message-id and subject line Bug#1005440: fixed in ruby-liquid-c 4.0.0-2 has caused the Debian Bug report #1005440, regarding ruby-liquid-c: FTBFS: ERROR: Test "ruby2.7" failed: /<>/test/liquid_test.rb:8:in `': uninitialized constant FileList (NameError) 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.) -- 1005440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005440 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-liquid-c Version: 4.0.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220212 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /<>/test/liquid_test.rb:8:in `': uninitialized > constant FileList (NameError) > Did you mean? FileTest > from > /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' > from > /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' > from > /usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:21:in > `block in ' > from > /usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in > `select' > from > /usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in > `' > rake aborted! > Command failed with status (1): [ruby -w -I"test" > /usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb > "test/liquid_test.rb" "test/unit/tokenizer_test.rb" > "test/unit/variable_test.rb" "test/test_helper.rb" -v] > /usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in ` (required)>' > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby2.7" failed: The full build log is available from: http://qa-logs.debian.net/2022/02/12/ruby-liquid-c_4.0.0-1_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: ruby-liquid-c Source-Version: 4.0.0-2 Done: Cédric Boutillier We believe that the bug you reported is fixed in the latest version of ruby-liquid-c, 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 1005...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cédric Boutillier (supplier of updated ruby-liquid-c package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 22 Feb 2022 13:53:23 +0100 Source: ruby-liquid-c Architecture: source Version: 4.0.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Cédric Boutillier Closes: 1005440 Changes: ruby-liquid-c (4.0.0-2) unstable; urgency=medium . * Team upload . [ Jenkins ] * Remove constraints unnecessary since buster . [ Cédric Boutillier ] * run tests in a way closer to upstream * Require rake in test/liquid_test to define FileList (Closes: #1005440) Checksums-Sha1: 8383671145171b98c357aec67b4f828bf77e37ee 1468 ruby-liquid-c_4.0.0-2.dsc 9c9f0764c1a31aa79fd805ffa6a2d91d0ce617fc 3304 ruby-liquid-c_4.0.0-2.debian.tar.xz 9bfe81f28b5072fbf4bde8c7b5f19e63a3cd5221 8989 ruby-liquid-c_4.0.0-2_amd64.buildinfo Checksums-Sha256: 21dd94d0e5d04e062aade211cae585174f0726b23861055b910aaff78d9d2eda 1468 ruby-liquid-c_4.0.0-2.dsc b07d36df3d1083a740be5f41bf84947000ecf50d85e71b0c0cfb6099e4ca58af 3304 ruby-liquid-c_4.0.0-2.debian.tar.xz 99963cd8f6518b58735757a9e505b9f7c4c3eba3cb29ee5436ff7a5233b069ce 8989 ruby-liquid-c_4.0.0-2_amd64.buildinfo Files: 888188e3bbf35a4acb427dfa3250c73e 1468 ruby optional ruby-liquid-c_4.0.0-2.dsc 80baa7af78428cf129a890d1fa4538a6 3304 ruby
Processed: Bug#1005920 marked as pending in coq-doc
Processing control commands: > tag -1 pending Bug #1005920 [src:coq-doc] coq-doc: FTBFS: Error: Library "zarith" not found. Added tag(s) pending. -- 1005920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005920 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1005920: marked as pending in coq-doc
Control: tag -1 pending Hello, Bug #1005920 in coq-doc reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ocaml-team/coq-doc/-/commit/3008fb4bc49395c2ec746e6432b6198a46d9e48e Fix b-deps again (Closes: #1005920) (this message was generated automatically) -- Greetings https://bugs.debian.org/1005920
Bug#1005187: marked as done (collectd build-depends on package that is not in testing.)
Your message dated Tue, 22 Feb 2022 13:57:55 +0100 with message-id <2fb8cfa3634443ffdc7256b6f06048d284beb37e.ca...@bzed.de> and subject line Re: Bug#1005187: collectd build-depends on package that is not in testing. has caused the Debian Bug report #1005187, regarding collectd build-depends on package that is not in testing. 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.) -- 1005187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005187 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: collectd Version: 5.12.0-8 Severity: serious Justification: rc policy: "packages must be buildable within the same release" collectd build-depends on liboping-dev, which is rc buggy and was removed from testing recently in an attempt to finish off the perl transition. This makes collectd rc buggy in testing. Potential soloutions (in descending order of preference) 1. Fix liboping, it seems there is a patch available but there has been no maintainer response for months and I won't NMU myself because I have no idea how to test it. 2. Disable liboping support in collectd (the fact that the runtime relationship is only a reccomends makes me suspect that this relates to optional functionality). --- End Message --- --- Begin Message --- Hi, I fail to understand why you are opening this bug at all. collectd would have been removed from testing automatically anyway, people are notified about that. It basically adds the extra work of tracking and closing this bug manually. If you want to add such bugs, please link them properly to the bugs that caused the issue and make sure that it is closed automatically as soon as the issue is fixed. Best would be not to open bugs at all, its just a waste of ressources. Bernd On Tue, 2022-02-08 at 17:33 +, peter green wrote: > Package: collectd > Version: 5.12.0-8 > Severity: serious > Justification: rc policy: "packages must be buildable within the same release" > > collectd build-depends on liboping-dev, which is rc buggy and was removed from > testing recently in an attempt to finish off the perl transition. This makes > collectd rc buggy in testing. > > Potential soloutions (in descending order of preference) > > 1. Fix liboping, it seems there is a patch available but there has been no > maintainer response for months and I won't NMU myself because I have no > idea how to test it. > 2. Disable liboping support in collectd (the fact that the runtime > relationship is only a reccomends makes me suspect that this relates > to optional functionality). > -- Bernd ZeimetzDebian GNU/Linux Developer http://bzed.dehttp://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F--- End Message ---
Bug#1005440: marked as pending in ruby-liquid-c
Control: tag -1 pending Hello, Bug #1005440 in ruby-liquid-c 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/ruby-team/ruby-liquid-c/-/commit/51a75101b4b574a7be17bea2a91150b12de084d4 Require rake in test/liquid_test to define FileList (Closes: #1005440) (this message was generated automatically) -- Greetings https://bugs.debian.org/1005440
Processed: Bug#1005440 marked as pending in ruby-liquid-c
Processing control commands: > tag -1 pending Bug #1005440 [src:ruby-liquid-c] ruby-liquid-c: FTBFS: ERROR: Test "ruby2.7" failed: /<>/test/liquid_test.rb:8:in `': uninitialized constant FileList (NameError) Added tag(s) pending. -- 1005440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005440 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995402: libclass-dbi-sweet-perl: FTBFS: test failure
Related Ubuntu bug https://bugs.launchpad.net/debiantesting/+bug/1961751 Suggested solution: drop package as upstream is not maintained anymore
Bug#1006035: marked as done (ruby-heapy: FTBFS: ERROR: Error installing /tmp/d20220218-169793-6cuult/heapy-0.1.4.gem: heapy-0.1.4 requires Ruby version ~> 2.3. The current ruby version is 3.0.2.107.)
Your message dated Tue, 22 Feb 2022 11:19:41 + with message-id and subject line Bug#1006035: fixed in ruby-heapy 0.2.0-1 has caused the Debian Bug report #1006035, regarding ruby-heapy: FTBFS: ERROR: Error installing /tmp/d20220218-169793-6cuult/heapy-0.1.4.gem: heapy-0.1.4 requires Ruby version ~> 2.3. The current ruby version is 3.0.2.107. 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.) -- 1006035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006035 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-heapy Version: 0.1.4-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --buildsystem=ruby --with ruby >dh_update_autotools_config -O--buildsystem=ruby >dh_autoreconf -O--buildsystem=ruby >dh_auto_configure -O--buildsystem=ruby > dh_ruby --configure >dh_auto_build -O--buildsystem=ruby > dh_ruby --build >dh_ruby --build >dh_auto_test -O--buildsystem=ruby > dh_ruby --test >create-stamp debian/debhelper-build-stamp >dh_testroot -O--buildsystem=ruby >dh_prep -O--buildsystem=ruby >dh_auto_install --destdir=debian/ruby-heapy/ -O--buildsystem=ruby > dh_ruby --install /<>/debian/ruby-heapy >dh_ruby --install > /usr/bin/ruby3.0 -S gem build --config-file /dev/null --verbose > /tmp/d20220218-169793-6cuult/gemspec > Failed to load /dev/null because it doesn't contain valid YAML hash > WARNING: open-ended dependency on rspec (>= 0, development) is not > recommended > use a bounded requirement, such as '~> x.y' > WARNING: See https://guides.rubygems.org/specification-reference/ for help > Successfully built RubyGem > Name: heapy > Version: 0.1.4 > File: heapy-0.1.4.gem > /usr/bin/ruby3.0 -S gem install --config-file /dev/null --verbose --local > --verbose --no-document --ignore-dependencies --install-dir > debian/ruby-heapy/usr/share/rubygems-integration/all > /tmp/d20220218-169793-6cuult/heapy-0.1.4.gem > Failed to load /dev/null because it doesn't contain valid YAML hash > ERROR: Error installing /tmp/d20220218-169793-6cuult/heapy-0.1.4.gem: > heapy-0.1.4 requires Ruby version ~> 2.3. The current ruby version is > 3.0.2.107. > /usr/lib/ruby/vendor_ruby/gem2deb.rb:54:in `run': /usr/bin/ruby3.0 -S gem > install --config-file /dev/null --verbose --local --verbose --no-document > --ignore-dependencies --install-dir > debian/ruby-heapy/usr/share/rubygems-integration/all > /tmp/d20220218-169793-6cuult/heapy-0.1.4.gem (Gem2Deb::CommandFailed) > from /usr/lib/ruby/vendor_ruby/gem2deb/gem_installer.rb:212:in `run_gem' > from /usr/lib/ruby/vendor_ruby/gem2deb/gem_installer.rb:120:in `block > in install_files_and_build_extensions' > from /usr/lib/ruby/vendor_ruby/gem2deb/gem_installer.rb:68:in `each' > from /usr/lib/ruby/vendor_ruby/gem2deb/gem_installer.rb:68:in > `install_files_and_build_extensions' > from /usr/lib/ruby/vendor_ruby/gem2deb/installer.rb:28:in `install' > from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:86:in `block in > install' > from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:84:in `each' > from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:84:in `install' > from /usr/bin/dh_ruby:89:in `' > dh_auto_install: error: dh_ruby --install /<>/debian/ruby-heapy > returned exit code 1 > make: *** [debian/rules:7: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2022/02/18/ruby-heapy_0.1.4-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: ruby-heapy Source-Version: 0.2.0-1 Done: Cédric Boutillier We believe that the bug you reported is fixed in the latest version of ruby-heapy, 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 1006...@bugs.debian.org, and the maintainer will
Bug#1006009: qtimageformats-opensource-src: FTBFS on mipsel: test failure
Control: tags -1 patch
On 2022-02-21 22:05:53, Sebastian Ramacher wrote:
> On 2022-02-20 18:33:22, Dmitry Shachnev wrote:
> > Control: reassign -1 libwebp7 1.2.1-7
> > Control: affects -1 src:qtimageformats-opensource-src
> >
> > Hi Sebastian and libwebp maintainers!
> >
> > On Fri, Feb 18, 2022 at 10:39:23PM +0100, Sebastian Ramacher wrote:
> > > Source: qtimageformats-opensource-src
> > > Version: 5.15.2-2
> > > Severity: serious
> > > Tags: ftbfs
> > > Justification: fails to build from source (but built successfully in the
> > > past)
> > > X-Debbugs-Cc: sramac...@debian.org
> > >
> > > qtimageformats-opensource-src FTBFS on mipsel:
> > >
> > > TIFFReadDirectory: Warning, Sum of Photometric type-related color
> > > channels and ExtraSamples doesn't match SamplesPerPixel. Defining
> > > non-color channels as ExtraSamples..
> > > TIFFReadDirectory: Warning, Sum of Photometric type-related color
> > > channels and ExtraSamples doesn't match SamplesPerPixel. Defining
> > > non-color channels as ExtraSamples..
> > > PASS : tst_qtiff::tiffGrayscale()
> > > FAIL! : tst_qwebp::writeImage(kollada_noalpha-100) '!reread.isNull()'
> > > returned FALSE. ()
> > >Loc: [tst_qwebp.cpp(174)]
> > > PASS : tst_qwebp::cleanupTestCase()
> > > Totals: 10 passed, 1 failed, 0 skipped, 0 blacklisted, 632ms
> > > * Finished testing of tst_qwebp *
> > >
> > > See
> > > https://buildd.debian.org/status/fetch.php?pkg=qtimageformats-opensource-src=mipsel=5.15.2-2%2Bb1=1645209225=0
> >
> > It looks to me like a bug in new libwebp version: encoder generates broken
> > webp files on mipsel.
> >
> > I can reproduce it without any Qt code by encoding the attached PNG file and
> > then trying to decode it back:
> >
> > (sid_mipsel-dchroot)mitya57@eller:~$ cwebp kollada_noalpha.png -lossless -o
> > kollada_noalpha.webp
> > Saving file 'kollada_noalpha.webp'
> > File: kollada_noalpha.png
> > Dimension: 436 x 160
> > Output:37004 bytes (4.24 bpp)
> > Lossless-ARGB compressed size: 37004 bytes
> > * Header size: 636 bytes, image data size: 36342
> > * Precision Bits: histogram=3 transform=3 cache=1
> > (sid_mipsel-dchroot)mitya57@eller:~$ dwebp kollada_noalpha.webp
> > Decoding of kollada_noalpha.webp failed.
> > Status: 3(BITSTREAM_ERROR)
> >
> > I am also attaching the generated broken WEBP file.
>
> A git bisect run suggests that this issue was introduced upstream in
> dea3e89983f299b3325898fa5b9474be258553b2 and is not yet fixed.
Disabling the mips specific optimizations works around this issue. See
the attached patch for a temporary fix until this issue is properly
fixed upstream.
Cheers
--
Sebastian Ramacher
diff --git a/src/dsp/dsp.h b/src/dsp/dsp.h
index fafc2d05..d466893c 100644
--- a/src/dsp/dsp.h
+++ b/src/dsp/dsp.h
@@ -97,17 +97,17 @@ extern "C" {
#if defined(__mips__) && !defined(__mips64) && \
defined(__mips_isa_rev) && (__mips_isa_rev >= 1) && (__mips_isa_rev < 6)
-#define WEBP_USE_MIPS32
+/* #define WEBP_USE_MIPS32 */
#if (__mips_isa_rev >= 2)
-#define WEBP_USE_MIPS32_R2
+/* #define WEBP_USE_MIPS32_R2 */
#if defined(__mips_dspr2) || (defined(__mips_dsp_rev) && __mips_dsp_rev >= 2)
-#define WEBP_USE_MIPS_DSP_R2
+/* #define WEBP_USE_MIPS_DSP_R2 */
#endif
#endif
#endif
#if defined(__mips_msa) && defined(__mips_isa_rev) && (__mips_isa_rev >= 5)
-#define WEBP_USE_MSA
+/* #define WEBP_USE_MSA */
#endif
#endif /* EMSCRIPTEN */
Processed: Re: Bug#1006009: qtimageformats-opensource-src: FTBFS on mipsel: test failure
Processing control commands: > tags -1 patch Bug #1006009 [libwebp7] qtimageformats-opensource-src: FTBFS on mipsel: test failure Added tag(s) patch. -- 1006009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006009 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1005671: marked as done (libvirt-python: FTBFS: ERROR: failed virDomainSetLaunchSecurityState)
Your message dated Tue, 22 Feb 2022 10:35:00 +
with message-id
and subject line Bug#1005671: fixed in libvirt-python 8.0.0-1
has caused the Debian Bug report #1005671,
regarding libvirt-python: FTBFS: ERROR: failed virDomainSetLaunchSecurityState
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.)
--
1005671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005671
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libvirt-python
Version: 7.9.0-0.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220212 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 build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:237: python3.10 setup.py config
> /<>/setup.py:3: 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.core import setup, Extension, Command
> running config
> I: pybuild base:237: python3.9 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:237: /usr/bin/python3.10 setup.py build
> /<>/setup.py:3: 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.core import setup, Extension, Command
> running build
> /usr/bin/pkg-config --print-errors --atleast-version=0.9.11 libvirt
> /usr/bin/python3.10 generator.py libvirt
> /usr/share/libvirt/api/libvirt-api.xml
> Found 493 functions in /usr/share/libvirt/api/libvirt-api.xml
> Found 0 functions in libvirt-override-api.xml
> Generated 403 wrapper functions
> Missing type converters:
> virTypedParameterPtr:1
> ERROR: failed virDomainSetLaunchSecurityState
> error: command '/usr/bin/python3.10' failed with exit code 1
> E: pybuild pybuild:367: build: plugin distutils failed with: exit code=1:
> /usr/bin/python3.10 setup.py build
> I: pybuild base:237: /usr/bin/python3 setup.py build
> running build
> /usr/bin/pkg-config --print-errors --atleast-version=0.9.11 libvirt
> /usr/bin/python3 generator.py libvirt /usr/share/libvirt/api/libvirt-api.xml
> Found 493 functions in /usr/share/libvirt/api/libvirt-api.xml
> Found 0 functions in libvirt-override-api.xml
> Generated 403 wrapper functions
> Missing type converters:
> virTypedParameterPtr:1
> ERROR: failed virDomainSetLaunchSecurityState
> error: command '/usr/bin/python3' failed with exit code 1
> E: pybuild pybuild:367: build: plugin distutils failed with: exit code=1:
> /usr/bin/python3 setup.py build
> dh_auto_build: error: pybuild --build -i python{version} -p "3.10 3.9"
> returned exit code 13
> make: *** [debian/rules:12: build] Error 25
The full build log is available from:
http://qa-logs.debian.net/2022/02/12/libvirt-python_7.9.0-0.1_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: libvirt-python
Source-Version: 8.0.0-1
Done: Guido Günther
We believe that the bug you reported is fixed in the latest version of
libvirt-python, 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 1005...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Guido Günther (supplier of updated libvirt-python package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 22 Feb 2022 10:59:53 +0100
Source: libvirt-python
Architecture: source
Version: 8.0.0-1
Processed: Re: Bug#1006131: rus-ispell: please stop build-depending on myspell-tools
Processing control commands: > tags -1 +pending Bug #1006131 [src:rus-ispell] rus-ispell: please stop build-depending on myspell-tools Added tag(s) pending. -- 1006131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006131 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1006131: rus-ispell: please stop build-depending on myspell-tools
Control: tags -1 +pending El mar, 22 feb 2022 a las 8:05, Mikhail Gusarov () escribió: > > Hello Agustin, > > On 21 Feb 2022, at 23:46, Agustin Martin wrote: > > >> Could you show me the difference? > > > Find attached diff. SInce flags are sorted differently by i2myspell > > and ispellaff2myspell , I made some magic for easier check of result, > > actually diffing sorted affix files. This is what leads to that file > > Thanks. Looks fine for me. > Actually, new file has the Cyrillic letters sorted in the right order :) Thanks a lot, -- Agustin
Bug#1005671: libvirt-python: FTBFS: ERROR: failed virDomainSetLaunchSecurityState
Hi Fabio, On Tue, Feb 22, 2022 at 10:15:22AM +0100, Fabio Fantoni wrote: > Hi, is there someone working on this? if yes let me know please otherwise > I'll try to do it when I have time Thanks for the reminder. I just uploaded a new version. Cheers, -- Guido
Bug#997189: marked as done (liboping: FTBFS: oping.c:1159:25: error: format not a string literal and no format arguments [-Werror=format-security])
Your message dated Tue, 22 Feb 2022 09:19:05 +
with message-id
and subject line Bug#997189: fixed in liboping 1.10.0-5
has caused the Debian Bug report #997189,
regarding liboping: FTBFS: oping.c:1159:25: error: format not a string literal
and no format arguments [-Werror=format-security]
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.)
--
997189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997189
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: liboping
Version: 1.10.0-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -DUSE_NCURSES=1 -D_DEFAULT_SOURCE
> -D_XOPEN_SOURCE=600 -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Werror -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -c -o noping-oping.o `test -f 'oping.c' || echo
> './'`oping.c
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2
> -Wall -Werror -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -c liboping.c
> -fPIC -DPIC -o .libs/liboping_la-liboping.o
> oping.c: In function ‘update_graph_prettyping’:
> oping.c:1159:25: error: format not a string literal and no format arguments
> [-Werror=format-security]
> 1159 | mvwprintw (ctx->window, /* y = */ y_max, /* x
> = */ x + 2, symbol);
> | ^
> oping.c: In function ‘update_graph_histogram’:
> oping.c:1265:41: error: format not a string literal and no format arguments
> [-Werror=format-security]
> 1265 | hist_symbols_utf8[index]);
> | ^
> oping.c: In function ‘update_host_hook’:
> oping.c:1640:38: error: too many arguments for format
> [-Werror=format-extra-args]
> 1640 | HOST_PRINTF ("%zu bytes from %s (%s):
> icmp_seq=%u ttl=%i ",
> |
> ^
> oping.c:1617:45: note: in definition of macro ‘HOST_PRINTF’
> 1617 | # define HOST_PRINTF(...) wprintw(main_win, __VA_ARGS__)
> | ^~~
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2
> -Wall -Werror -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -c liboping.c -o
> liboping_la-liboping.o >/dev/null 2>&1
> cc1: all warnings being treated as errors
> make[4]: *** [Makefile:598: noping-oping.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/liboping_1.10.0-4_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: liboping
Source-Version: 1.10.0-5
Done: Bernd Zeimetz
We believe that the bug you reported is fixed in the latest version of
liboping, 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.
Bernd Zeimetz (supplier of updated liboping package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 22 Feb 2022 09:53:24 +0100
Source: liboping
Architecture: source
Version: 1.10.0-5
Distribution: unstable
Urgency: medium
Maintainer: Sebastian Harl
Changed-By: Bernd Zeimetz
Closes: 997189
Changes:
liboping (1.10.0-5) unstable; urgency=medium
.
* [d4b6a3a] Fix build with -Werror=format-security (Closes: #997189)
* [2f3779d] Add a gitlab ci config
* [df697b1] Update debian/.gitlab-ci.yml file
* [fa5cded] Better name for
Bug#1005671: libvirt-python: FTBFS: ERROR: failed virDomainSetLaunchSecurityState
Hi, is there someone working on this? if yes let me know please otherwise I'll try to do it when I have time OpenPGP_signature Description: OpenPGP digital signature
Bug#1006039: pytest-xdist: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13
On 21/02/22 at 19:52 -0500, Scott Talbert wrote: > I'm not able to reproduce this, at least locally in sbuild. Possibly some > transient error in unstable? Can you re-try? Hi Scott, I can reproduce it, but this looks like a random failure. Building in a loop, I get: log.1:Status: attempted log.2:Status: successful log.3:Status: successful log.4:Status: successful log.5:Status: attempted Lucas
Processed: Re: fwupd : segfault of service
Processing control commands:
> reassign 1005820 libgusb2
Bug #1005820 [fwupd] fwupd : segfault of service
Bug reassigned from package 'fwupd' to 'libgusb2'.
No longer marked as found in versions fwupd/1.7.4-2.
Ignoring request to alter fixed versions of bug #1005820 to the same values
previously set
> forcemerge 1005416 1005820
Bug #1005416 {Done: Paul Wise } [libgusb2] libgusb: causes
crashes in fwupd with libusb-1.0 2:1.0.25-1
Bug #1005820 [libgusb2] fwupd : segfault of service
Set Bug forwarded-to-address to
'https://github.com/hughsie/libgusb/commit/24934619a2ad3467b98142dfab2039985afc970d
https://github.com/fwupd/fwupd/issues/4285'.
Severity set to 'important' from 'grave'
1005820 was not blocked by any bugs.
1005820 was not blocking any bugs.
Added blocking bug(s) of 1005820: 1005780
Marked Bug as done
Marked as fixed in versions libgusb/0.3.10-1.
Merged 1005416 1005820
--
1005416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005416
1005820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005820
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1005820: fwupd : segfault of service
Control: reassign 1005820 libgusb2 Control: forcemerge 1005416 1005820 On Fri, 18 Feb 2022 20:14:16 + Mario Limonciello wrote: > It was fixed by an upgrade to libgusb. This can be closed. Doing that in this message I think. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Processed: mailavenger: fixed in salsa 'gcc_10' branch
Processing control commands: > tags -1 patch Bug #957514 [src:mailavenger] mailavenger: ftbfs with GCC-10 Added tag(s) patch. -- 957514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957514 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957514: mailavenger: fixed in salsa 'gcc_10' branch
Source: mailavenger Followup-For: Bug #957514 Control: tags -1 patch Hi Dererk, The reason for this FTBFS is that gcc 10 now defaults to -fno-common, which then throws errors because there are some tentative definitions in .h files, and some definitions of an int `garbage` in several .c files. Here's a branch that fixes that: https://salsa.debian.org/debian/mailavenger/-/commits/gcc_10 by adding `__attribute__((__common__))` to those variables. I separated the patches, because the `garbage` definitions seem a little different in character. Cheers, Phil. P.S. my C programming experience is from the previous millenium, so I could easily have got this wrong. I will not be upset if you point this out :-)
Processed: Re: pygame: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" --system=custom --test-args "/usr/bin/xvfb-run {interpreter} -m pygame.tests.__main__ --exclude openg
Processing control commands:
> tags -1 confirmed
Bug #1005438 [src:pygame] pygame: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p "3.10 3.9" --system=custom --test-args "/usr/bin/xvfb-run
{interpreter} -m pygame.tests.__main__ --exclude opengl" returned exit code 13
Added tag(s) confirmed.
--
1005438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005438
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1005438: pygame: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" --system=custom --test-args "/usr/bin/xvfb-run {interpreter} -m pygame.tests.__main__ --exclude opengl"
Control: tags -1 confirmed Hi, I had a look into this issue since a Debian Med package received a testing removal warning. I can confirm the build fails with Segmentation fault in the build time test suite. I realised that this package is lagging quite a bit behind upstream and my personal approach would be to do an upgrade to latest upstream. However, the package has a number of dependencies which I have no idea about and thus I'm hesitating to go on with this idea which takes probably some time to review all the patches. So for the moment I've just commited the changes of lintian-brush (= made myself Debian Janitor ;-) ) I've put all developers mentioned as Uploader in CC. Given that the last non-team upload was two years ago which might have lead to the situation that following upstream changes is stalled it would be great if you confirm that you intend to continue working on this package. Kind regards Andreas. -- http://fam-tille.de
