Bug#959157: fix for CVE-2020-1749 in linux-image-4.19.0-9 breaks wireguard
Package: wireguard-dkms Version: 1.0.20200429-1~bpo10+1 Followup-For: Bug #959157 Dear Maintainer, look like problem is still here: $ sudo aptitude -f install The following partially installed packages will be configured: wireguard wireguard-dkms No packages will be installed, upgraded, or removed. 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B of archives. After unpacking 0 B will be used. Setting up wireguard-dkms (1.0.20200429-1~bpo10+1) ... Removing old wireguard-1.0.20200429 DKMS files... -- Deleting module version: 1.0.20200429 completely from the DKMS tree. -- Done. Loading new wireguard-1.0.20200429 DKMS files... Building for 4.19.0-9-amd64 Building initial module for 4.19.0-9-amd64 Error! Bad return status for module build on kernel: 4.19.0-9-amd64 (x86_64) Consult /var/lib/dkms/wireguard/1.0.20200429/build/make.log for more information. dpkg: error processing package wireguard-dkms (--configure): installed wireguard-dkms package post-installation script subprocess returned error exit status 10 dpkg: dependency problems prevent configuration of wireguard: wireguard depends on wireguard-dkms (>= 0.0.20200121-2) | wireguard-modules (>= 0.0.20191219); however: Package wireguard-dkms is not configured yet. Package wireguard-modules is not installed. dpkg: error processing package wireguard (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: wireguard-dkms wireguard E: Sub-process /usr/bin/dpkg returned an error code (1) Setting up wireguard-dkms (1.0.20200429-1~bpo10+1) ... Removing old wireguard-1.0.20200429 DKMS files... -- Deleting module version: 1.0.20200429 completely from the DKMS tree. -- Done. Loading new wireguard-1.0.20200429 DKMS files... Building for 4.19.0-9-amd64 Building initial module for 4.19.0-9-amd64 Error! Bad return status for module build on kernel: 4.19.0-9-amd64 (x86_64) Consult /var/lib/dkms/wireguard/1.0.20200429/build/make.log for more information. dpkg: error processing package wireguard-dkms (--configure): installed wireguard-dkms package post-installation script subprocess returned error exit status 10 dpkg: dependency problems prevent configuration of wireguard: wireguard depends on wireguard-dkms (>= 0.0.20200121-2) | wireguard-modules (>= 0.0.20191219); however: Package wireguard-dkms is not configured yet. Package wireguard-modules is not installed. dpkg: error processing package wireguard (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: wireguard-dkms wireguard $ cat /var/lib/dkms/wireguard/1.0.20200429/build/make.log DKMS make.log for wireguard-1.0.20200429 for kernel 4.19.0-9-amd64 (x86_64) Sat May 2 16:31:27 +10 2020 make: Entering directory '/usr/src/linux-headers-4.19.0-9-amd64' CC [M] /var/lib/dkms/wireguard/1.0.20200429/build/main.o CC [M] /var/lib/dkms/wireguard/1.0.20200429/build/noise.o CC [M] /var/lib/dkms/wireguard/1.0.20200429/build/device.o CC [M] /var/lib/dkms/wireguard/1.0.20200429/build/peer.o CC [M] /var/lib/dkms/wireguard/1.0.20200429/build/timers.o CC [M] /var/lib/dkms/wireguard/1.0.20200429/build/queueing.o CC [M] /var/lib/dkms/wireguard/1.0.20200429/build/send.o CC [M] /var/lib/dkms/wireguard/1.0.20200429/build/receive.o CC [M] /var/lib/dkms/wireguard/1.0.20200429/build/socket.o CC [M] /var/lib/dkms/wireguard/1.0.20200429/build/peerlookup.o CC [M] /var/lib/dkms/wireguard/1.0.20200429/build/allowedips.o CC [M] /var/lib/dkms/wireguard/1.0.20200429/build/ratelimiter.o In file included from : /var/lib/dkms/wireguard/1.0.20200429/build/socket.c: In function 'send6': /var/lib/dkms/wireguard/1.0.20200429/build/compat/compat.h:102:42: error: 'const struct ipv6_stub' has no member named 'ipv6_dst_lookup'; did you mean 'ipv6_dst_lookup_flow'? #define ipv6_dst_lookup_flow(a, b, c, d) ipv6_dst_lookup(a, b, &dst, c) + (void *)0 ?: dst ^~~ /var/lib/dkms/wireguard/1.0.20200429/build/socket.c:145:20: note: in expansion of macro 'ipv6_dst_lookup_flow' dst = ipv6_stub->ipv6_dst_lookup_flow(sock_net(sock), sock, &fl, ^~~~ make[3]: *** [/usr/src/linux-headers-4.19.0-9-common/scripts/Makefile.build:308: /var/lib/dkms/wireguard/1.0.20200429/build/socket.o] Error 1 make[3]: *** Waiting for unfinished jobs make[2]: *** [/usr/src/linux-headers-4.19.0-9-common/Makefile:1537: _module_/var/lib/dkms/wireguard/1.0.20200429/build] Error 2 make[1]: *** [Makefile:146: sub-make] Error 2 make: *** [Makefile:8: all] Error 2 make: Leaving directory '/usr/src/linux-headers-4.19.0-9-amd64' $ uname -a Linux hostname 4.19.0-9-amd64 #1 SMP Debian 4.19.118-2 (2020-04-29) x86_64 GNU/Linux -- System Information: Debian Release: 10.3 APT prefers stable-updates
Bug#959157: patch does not address issue
On Fri, 1 May 2020 15:30:40 + Luca Filipozzi wrote: > The changes made do not address the bug, I'm afraid. wireguard-dkms > fails to install because kernel-image 4.19.0-9 includes a backported > change that is not caught by the pragmas in compat.h. This backport > might be a Debian-ism that perhaps should not need to be handled in > upstream, I'll admit, but wireguard-dkms (and upstream > wireguard-linux-compat, of course), fail to build with 4.19.0-9. How about this: https://git.zx2c4.com/wireguard-linux-compat/commit/?id=88640eddadaed11668d7d38190d9f6158ea3ff60
Bug#959157: fix for CVE-2020-1749 in linux-image-4.19.0-9 breaks wireguard
Package: wireguard-dkms Followup-For: Bug #959157 Dear Maintainer, wireguard-dkms 1.0.20200429-2 (from unstable) compile module successfully so this set fixed the problem for me $ dpkg -l | grep wireguard ii wireguard 1.0.20200319-1~bpo10+1 all ii wireguard-dkms 1.0.20200429-2 all ii wireguard-tools1.0.20200319-1~bpo10+1 amd64 -- System Information: Debian Release: 10.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-9-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages wireguard-dkms depends on: ii bc1.07.1-2+b1 ii dkms 2.6.1-4 ii perl 5.28.1-6 Versions of packages wireguard-dkms recommends: ii wireguard1.0.20200319-1~bpo10+1 ii wireguard-tools 1.0.20200319-1~bpo10+1 wireguard-dkms suggests no packages. -- no debconf information
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> fixed 958419 swi-prolog/8.1.29+dfsg-2
Bug #958419 {Done: Jonas Smedegaard } [src:swi-prolog, src:eye]
swi-prolog breaks eye autopkgtest: Failed 7/15 subtests
Marked as fixed in versions swi-prolog/8.1.29+dfsg-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
958419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958419
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 954259
Processing commands for cont...@bugs.debian.org: > tags 954259 + pending Bug #954259 [src:innoextract] src:innoextract: fails to migrate to testing for too long Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 954259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954259 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959421: debhelper 13 complains about source files missing in the binary of ebumeter
Package: debhelper Version: 13 Severity: serious Tags: upstream ftbfs Justification: fails to build from source Dear Maintainer, when upgrading to dh 13 with ebumeter, dh complains about source files from ebumeter/source missing in the binary. https://salsa.debian.org/multimedia-team/ebumeter Best regards, Dennis -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 5.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages debhelper depends on: ii autotools-dev20180224.1 ii dh-autoreconf19 ii dh-strip-nondeterminism 1.8.0-1 ii dpkg 1.19.7 ii dpkg-dev 1.19.7 ii dwz 0.13-5 ii file 1:5.38-4 ii libdebhelper-perl13 ii libdpkg-perl 1.19.7 ii man-db 2.9.1-1 ii perl 5.30.0-10 ii po-debconf 1.0.21 debhelper recommends no packages. Versions of packages debhelper suggests: ii dh-make 2.202001 -- no debconf information
Bug#959391: wordpress: CVE-2020-11025 CVE-2020-11026 CVE-2020-11027 CVE-2020-11028 CVE-2020-11029 CVE-2020-11030
Hi Craig, On Sat, May 02, 2020 at 10:31:24AM +1000, Craig Small wrote: > This is the analysis of the latest WordPress security bugs. > Is it awesome upstream already has CVE IDs and (almost) clear patches of > the fixes? Yes, it is! > > Sid: 5.4 > All vulnerabilities, use upstream 5.4.1 > > Bullseye: 5.3.2 > https://github.com/WordPress/wordpress-develop/commit/42cbfc76f87add1853996730c587ea66aa8fdc28 > SVN references: 47633 47634 47635 47636 47637 47638 > https://core.trac.wordpress.org/changeset/47633 Customizer - CVE-2020-11025 > https://core.trac.wordpress.org/changeset/47634 password update - > CVE-2020-11027 > https://core.trac.wordpress.org/changeset/47635 single post on query - > CVE-2020-11028 > https://core.trac.wordpress.org/changeset/47636 block editor escape - > CVE-2020-11030 > https://core.trac.wordpress.org/changeset/47637 escaping around stats - > CVE-2020-11029 > https://core.trac.wordpress.org/changeset/47638 sanitize file name - > CVE-2020-11026 > All vulnerable, use aggregated GH commit Thanks for this btw, and I have synced the security-tracker information with it now (plus trying to add respective isolated commits from the git hub repository a swell). For a respective update in the other branches it makes obviously sense as you say to use the aggregted commit from GH. Regards, Salvatore
Processed: Re: Bug#959421: debhelper 13 complains about source files missing in the binary of ebumeter
Processing commands for cont...@bugs.debian.org: > tags 959421 upstream Bug #959421 [debhelper] debhelper 13 complains about source files missing in the binary of ebumeter Ignoring request to alter tags of bug #959421 to the same tags previously set > End of message, stopping processing here. Please contact me if you need assistance. -- 959421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959421 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#959421: debhelper 13 complains about source files missing in the binary of ebumeter
Processing control commands: > severity -1 normal Bug #959421 [debhelper] debhelper 13 complains about source files missing in the binary of ebumeter Severity set to 'normal' from 'serious' > tags -1 moreinfo Bug #959421 [debhelper] debhelper 13 complains about source files missing in the binary of ebumeter Added tag(s) moreinfo. -- 959421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959421 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959421: debhelper 13 complains about source files missing in the binary of ebumeter
Control: severity -1 normal Control: tags -1 moreinfo Dennis Braun: > Package: debhelper > Version: 13 > Severity: serious > Tags: upstream ftbfs > Justification: fails to build from source > > Dear Maintainer, > > when upgrading to dh 13 with ebumeter, dh complains about source files from > ebumeter/source missing in the binary. > > https://salsa.debian.org/multimedia-team/ebumeter > > Best regards, > Dennis > > > [...] Hi Dennis, This bug report leaves me with very mixed feelings. The report has no details of what you did other than a vague "Upgrading to dh" which is ambiguous (did you upgrade to debhelper 13 or bump compat level to 13? There is a major difference between the two). There are no details of what you did to understand the problem nor any mention of unclear documentation from debhelper's documentation. This leaves me with the feeling that you bumped the compat level without reading the relevant documentation and when it broke you shoved the broken pieces to me with an implicit "Please fix this for me!". This is hopefully not what you intended to do. In the future, I would recommend you provide a bit more details on what you have tried to do or/and which part of the documentation that you do not feel match the reality you see. This would leave me with less guess work and also less likely to come to the above assumption that cannot be part of a fruitful discussion on how we fix the issue you experience. *Moving on* Pushing that aside, lets move on to ebumeter. I presume what you were experiencing was that dh_missing terminated when an error as it now defaults to --fail-missing instead of --list-missing. This is documented in "man 7 debhelper" under "Supported compatibility levels" (see the "v13" / "Changes from v12" entry). Related, dh_missing emits the same warnings already under compat 12, which is an early warning and would have enabled you to fix this problem ahead of time. I can recommend checking the build logs for warnings before bumping compat levels. At this point, we might be tempted to just neuter the dh_missing issue (instructions are in "man 7 debhelper") and move on. However, I recommend that you fix the root cause, which in this case involves the --sourcedir parameter to dh and some follow up fixes. *The root cause for ebumeter* The "--sourcedir" parameter is accepted by dh_install AND the dh_auto_* commands. But in ebumeter, it *seem* to be used to make sure dh_auto_* pick up the upstream source files directly. This can be done by using the longer form "--sourcedirectory", which only dh_auto_* responds to[1]. This will trigger some errors from the .install and .manpages files because the "../" hack does not work any longer. That said, it is unneeded and simply removing "../" will work because the relevant dh_install* helpers will fall back to the source root when they do not get the --sourcedir parameter. These changes should also work in compat 12, so you can try them out without bumping to compat 13 and see all the dh_missing warnings disappear. Note: I have made no attempts to check if the package work after these changes and include every thing as you would expect. I leave that to you. *In summary* I do not see a bug in debhelper, only a failed attempt to migrate to compat 13 (which I have provided suggestions on how to fix). Should you find that the documentation for bumping compat levels is unclear or have suggestions to improve it, please let me know and I will look at fixing it. ~Niels [1] Yes, it is confusing that --sourcedir is picked up by both dh_install + dh_auto_*.
Processed: gajim in Debian stretch does not start anymore
Processing commands for cont...@bugs.debian.org: > retitle 930991 gajim in Debian stretch does not start anymore Bug #930991 [gajim] gajim in Debian Stable does not start anymore Changed Bug title to 'gajim in Debian stretch does not start anymore' from 'gajim in Debian Stable does not start anymore'. > notfound 930991 1.1.2-2~bpo9+1 Bug #930991 [gajim] gajim in Debian stretch does not start anymore Ignoring request to alter found versions of bug #930991 to the same values previously set > notfound 930991 1.1.2-2 Bug #930991 [gajim] gajim in Debian stretch does not start anymore Ignoring request to alter found versions of bug #930991 to the same values previously set > notfound 930991 1.1.3-2 Bug #930991 [gajim] gajim in Debian stretch does not start anymore Ignoring request to alter found versions of bug #930991 to the same values previously set > notfound 930991 1.1.99~20200429.65506e31-1 Bug #930991 [gajim] gajim in Debian stretch does not start anymore Ignoring request to alter found versions of bug #930991 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 930991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930991 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#954691: marked as done (stunnel4: FTBFS: A fatalerror occurred writing to the 127.0.0.1:48164 connection: Connection reset by peer)
Your message dated Sat, 02 May 2020 11:18:50 + with message-id and subject line Bug#954691: fixed in stunnel4 3:5.56+dfsg-1 has caused the Debian Bug report #954691, regarding stunnel4: FTBFS: A fatalerror occurred writing to the 127.0.0.1:48164 connection: Connection reset by peer 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.) -- 954691: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954691 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: stunnel4 Version: 3:5.56-1 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 '/<>' > env TEST_STUNNEL=/<>/src/stunnel debian/tests/runtime > Found the certificate at debian/tests/certs/certificate.pem and the private > key at debian/tests/certs/key.pem > Using the /tmp/p4obeQVBIN temporary directory > About to get the stunnel version information > Got stunnel version 5.56 > Listening for cleartext connections on 127.0.0.1:6502 > Connected to 127.0.0.1:6502, local 127.0.0.1:48160 > Accepted a connection from 127.0.0.1:48160 > Got a local connection id 127.0.0.1:48160 > Waiting for the server to acknowledge a completed client connection > Got an eof from 127.0.0.1:48160, all seems well > Waiting for the client connection itself to report completion > Looks like we are done with the test cleartext connection! > Got listening port 8086 for the stunnel server > Let us hope this was enough to get stunnel to listen there... > Created the stunnel config file /tmp/p4obeQVBIN/stunnel.conf: > == > pid = /tmp/p4obeQVBIN/stunnel.pid > foreground = yes > output = /tmp/p4obeQVBIN/stunnel.log > > cert = debian/tests/certs/certificate.pem > key = debian/tests/certs/key.pem > > [test] > accept = 127.0.0.1:8086 > connect = 127.0.0.1:6502 > == > 2020.03.22 08:45:58 LOG5[ui]: stunnel 5.56 on x86_64-pc-linux-gnu platform > 2020.03.22 08:45:58 LOG5[ui]: Compiled/running with OpenSSL 1.1.1e 17 Mar > 2020 > 2020.03.22 08:45:58 LOG5[ui]: Threading:PTHREAD Sockets:POLL,IPv6,SYSTEMD > TLS:ENGINE,FIPS,OCSP,PSK,SNI Auth:LIBWRAP > 2020.03.22 08:45:58 LOG5[ui]: Reading configuration from file > /tmp/p4obeQVBIN/stunnel.conf > 2020.03.22 08:45:58 LOG5[ui]: UTF-8 byte order mark not detected > 2020.03.22 08:45:58 LOG5[ui]: FIPS mode disabled > 2020.03.22 08:45:58 LOG4[ui]: Insecure file permissions on > debian/tests/certs/key.pem > 2020.03.22 08:45:58 LOG5[ui]: Configuration successful > 2020.03.22 08:45:59 LOG5[0]: Service [test] accepted connection from > 127.0.0.1:51458 > 2020.03.22 08:45:59 LOG5[0]: s_connect: connected 127.0.0.1:6502 > 2020.03.22 08:45:59 LOG5[0]: Service [test] connected remote server from > 127.0.0.1:48164 > 2020.03.22 08:45:59 LOG3[0]: SSL_read: ../ssl/record/rec_layer_s3.c:302: > error:14095126:SSL routines:ssl3_read_n:unexpected eof while reading > 2020.03.22 08:45:59 LOG5[0]: Connection reset: 18 byte(s) sent to TLS, 0 > byte(s) sent to socket > A fatalerror occurred writing to the 127.0.0.1:48164 connection: Connection > reset by peer > The listener's close message timed out > __DIE__ handler invoked: The listener did not acknowledge the connection > The listener did not acknowledge the connection > Started the stunnel server, pid 22952 > Trying a connection through stunnel, iteration 1 > Trying to connect to the stunnel server at 127.0.0.1:8086 > ...connected! > Registered a client connection as 127.0.0.1:51458 > Waiting for the cleartext listener to receive this connection > Accepted a connection from 127.0.0.1:48164 > Oof, let us see if there are any children left > Pffth, sending a SIGKILL to 22952 > Some children remaining, laying low for a second... > - waiting for 22952 (stunnel server (127.0.0.1:8086)) > - OK, 22952 done > make[1]: *** [debian/rules:33: override_dh_auto_test] Error 10 The full build log is available from: http://qa-logs.debian.net/2020/03/22/stunnel4_5.56-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! 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: stunnel4 Source-Version: 3:5.56+dfsg-1 Done: Peter Pentchev We believe that the bug you reported is fixed in the latest ve
Processed: Downgrading severity
Processing commands for cont...@bugs.debian.org: > severity 956735 normal Bug #956735 [qv4l2] qv4l2: No sound when capture a video VHS. Severity set to 'normal' from 'grave' > stop Stopping processing here. Please contact me if you need assistance. -- 956735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956735 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#959393 marked as pending in ruby
Processing control commands: > tag -1 pending Bug #959393 [ruby2.7] ruby2.7 breaks diaspora-installer autopkgtest: sh: 1: bundle: not found Added tag(s) pending. -- 959393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959393 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959393: marked as pending in ruby
Control: tag -1 pending Hello, Bug #959393 in ruby 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/-/commit/969df5fe2fae4176f8061d333e20c9de652a7907 libruby: do not provide ruby-bundler Closes: #959393 (this message was generated automatically) -- Greetings https://bugs.debian.org/959393
Bug#959393: [DRE-maint] Bug#959393: ruby2.7 breaks diaspora-installer autopkgtest: sh: 1: bundle: not found
Am Freitag, den 01.05.2020, 21:20 -0300 schrieb Antonio Terceiro: > Control: reassign -1 libruby2.7 > Control: found -1 2.7.0-6 > > On Fri, May 01, 2020 at 09:12:57PM -0300, Antonio Terceiro wrote: > > Control: reassign -1 ruby2.7 > > Control: found -1 2.7.0-6 > > > > On Fri, May 01, 2020 at 10:23:56PM +0200, Paul Gevers wrote: > > > Using system bundler... > > > Installing gems with rubygems ... > > > sh: 1: bundle: not found > > > > libruby2.7 now has some Provides: for libraries builtin to the standard > > library, including ruby-bundler. But since ruby-bundler also provides a > > `bundle` binary, which libruby2.7 does not, then this Provides: is not > > really correct. > > > > Instead, libruby2.7 should depend on ruby-bundler, like it already does on > > rake, ruby-test-unit and others, and not provide it. > > It's on libruby2.7, not ruby2.7 The binary is in ruby2.7. IMHO our approach should be: - ship a symlink /usr/bin/bundle -> /usr/bin/bundle2.7 with ruby(-defaults), - handle the symlink via dpkg-divert if ruby-bundler gets installed, and - keep the provides in libruby2.7. Regards, Daniel ___ > Pkg-ruby-extras-maintainers mailing list > pkg-ruby-extras-maintain...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 If you like my work consider sponsoring me via https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part
Bug#959444: openexr: CVE-2020-11758 CVE-2020-11759 CVE-2020-11760 CVE-2020-11761 CVE-2020-11762 CVE-2020-11763 CVE-2020-11764 CVE-2020-11765
Package: openexr Version: 2.3.0-6 Severity: grave Tags: security upstream Justification: user security hole Hi, The following vulnerabilities were published for openexr, all are fixed in 2.4.1. CVE-2020-11758[0]: | An issue was discovered in OpenEXR before 2.4.1. There is an out-of- | bounds read in ImfOptimizedPixelReading.h. CVE-2020-11759[1]: | An issue was discovered in OpenEXR before 2.4.1. Because of integer | overflows in CompositeDeepScanLine::Data::handleDeepFrameBuffer and | readSampleCountForLineBlock, an attacker can write to an out-of-bounds | pointer. CVE-2020-11760[2]: | An issue was discovered in OpenEXR before 2.4.1. There is an out-of- | bounds read during RLE uncompression in rleUncompress in ImfRle.cpp. CVE-2020-11761[3]: | An issue was discovered in OpenEXR before 2.4.1. There is an out-of- | bounds read during Huffman uncompression, as demonstrated by | FastHufDecoder::refill in ImfFastHuf.cpp. CVE-2020-11762[4]: | An issue was discovered in OpenEXR before 2.4.1. There is an out-of- | bounds read and write in DwaCompressor::uncompress in | ImfDwaCompressor.cpp when handling the UNKNOWN compression case. CVE-2020-11763[5]: | An issue was discovered in OpenEXR before 2.4.1. There is an | std::vector out-of-bounds read and write, as demonstrated by | ImfTileOffsets.cpp. CVE-2020-11764[6]: | An issue was discovered in OpenEXR before 2.4.1. There is an out-of- | bounds write in copyIntoFrameBuffer in ImfMisc.cpp. CVE-2020-11765[7]: | An issue was discovered in OpenEXR before 2.4.1. There is an off-by- | one error in use of the ImfXdr.h read function by | DwaCompressor::Classifier::Classifier, leading to an out-of-bounds | read. If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-11758 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11758 [1] https://security-tracker.debian.org/tracker/CVE-2020-11759 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11759 [2] https://security-tracker.debian.org/tracker/CVE-2020-11760 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11760 [3] https://security-tracker.debian.org/tracker/CVE-2020-11761 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11761 [4] https://security-tracker.debian.org/tracker/CVE-2020-11762 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11762 [5] https://security-tracker.debian.org/tracker/CVE-2020-11763 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11763 [6] https://security-tracker.debian.org/tracker/CVE-2020-11764 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11764 [7] https://security-tracker.debian.org/tracker/CVE-2020-11765 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11765 [8] https://bugs.chromium.org/p/project-zero/issues/detail?id=1987 Regards, Salvatore
Bug#959117: Unable to mount with fuse3 (fusermount: unknown option 'nonempty')
Package: s3ql Version: 3.3.2+dfsg-2+b1 Followup-For: Bug #959117 Dear Maintainer, This seems to be solved by upstream's commit 752da96c1b0c71e666ac0263eaa46b1620f32e92, which is preset in release-3.4.0 It's also worth updating the "Homepage:" field, as the project has moved to https://github.com/s3ql/s3ql -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (520, 'testing'), (510, 'stable'), (150, 'unstable'), (120, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.5.0-2-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages s3ql depends on: ii fuse3 [fuse] 3.9.0-2 ii libc6 2.30-4 ii libjs-sphinxdoc2.4.3-2 ii libsqlite3-0 3.31.1-5 ii procps 2:3.3.16-4 ii psmisc 23.3-1 ii python33.8.2-3 ii python3-apsw 3.30.1-r1-1.1+b1 ii python3-cryptography 2.8-4 ii python3-defusedxml 0.6.0-2 ii python3-dugong 3.7.4+dfsg-2 ii python3-google-auth1.5.1-2 ii python3-llfuse 1.3.6+dfsg-2+b2 ii python3-pkg-resources 46.1.3-1 ii python3-requests 2.23.0+dfsg-2 Versions of packages s3ql recommends: ii python3-systemd 234-3+b2 s3ql suggests no packages. -- no debconf information
Bug#959393: [DRE-maint] Bug#959393: ruby2.7 breaks diaspora-installer autopkgtest: sh: 1: bundle: not found
On Sat, May 02, 2020 at 02:59:36PM +0200, Daniel Leidert wrote: > Am Freitag, den 01.05.2020, 21:20 -0300 schrieb Antonio Terceiro: > > Control: reassign -1 libruby2.7 > > Control: found -1 2.7.0-6 > > > > On Fri, May 01, 2020 at 09:12:57PM -0300, Antonio Terceiro wrote: > > > Control: reassign -1 ruby2.7 > > > Control: found -1 2.7.0-6 > > > > > > On Fri, May 01, 2020 at 10:23:56PM +0200, Paul Gevers wrote: > > > > Using system bundler... > > > > Installing gems with rubygems ... > > > > sh: 1: bundle: not found > > > > > > libruby2.7 now has some Provides: for libraries builtin to the standard > > > library, including ruby-bundler. But since ruby-bundler also provides a > > > `bundle` binary, which libruby2.7 does not, then this Provides: is not > > > really correct. > > > > > > Instead, libruby2.7 should depend on ruby-bundler, like it already does on > > > rake, ruby-test-unit and others, and not provide it. > > > > It's on libruby2.7, not ruby2.7 > > The binary is in ruby2.7. IMHO our approach should be: > > - ship a symlink /usr/bin/bundle -> /usr/bin/bundle2.7 with ruby(-defaults), > - handle the symlink via dpkg-divert if ruby-bundler gets installed, and > - keep the provides in libruby2.7. the problem with this is that the binaries would be provided by ruby(-defaults), and the actual Provides: would be in libruby2.7. Although it would work, because there is a circular dependency between libruby2.7 and ruby, it's not entirely correct. FWIW, racc is in a similar situation: libruby2.7 Provides: ruby-racc, but not the racc binary (provided by the racc package). There is no real ruby-racc package though. For now, I have commited a change to ruby to drop ruby-bundler from Provides:, but we can revisit this later with a solution that is consistent for bundler, racc, and any other package that ruby might absorb that also contains a binary. signature.asc Description: PGP signature
Bug#959451: am-utils: Build-Depends on obsolete package linux-kernel-headers
Package: src:am-utils Version: 6.2+rc20110530-3.2 Severity: serious linux-kernel-headers was removed from unstable in 2007 (I think). It is now effectively a virtual package provided by linux-libc-dev, but it's not a documented virtual package name and I would like to stop providing it. Please change the dependency to linux-libc-dev. Ben. -- Ben Hutchings The first rule of tautology club is the first rule of tautology club. signature.asc Description: This is a digitally signed message part
Bug#959452: array-info: Build-Depends on obsolete package linux-kernel-headers
Package: src:array-info Version: 0.16-4 Severity: serious linux-kernel-headers was removed from unstable in 2007 (I think). It is now effectively a virtual package provided by linux-libc-dev, but it's not a documented virtual package name and I would like to stop providing it. Please change the dependency to linux-libc-dev. Ben. -- Ben Hutchings The first rule of tautology club is the first rule of tautology club. signature.asc Description: This is a digitally signed message part
Bug#959454: dvbtune: Build-Depends on obsolete package linux-kernel-headers
Package: src:dvbtune Version: 0.5.ds-1.1 Severity: serious linux-kernel-headers was removed from unstable in 2007 (I think). It is now effectively a virtual package provided by linux-libc-dev, but it's not a documented virtual package name and I would like to stop providing it. Please change the dependency to linux-libc-dev. Ben. -- Ben Hutchings The first rule of tautology club is the first rule of tautology club. signature.asc Description: This is a digitally signed message part
Bug#959453: dvbstream: Build-Depends on obsolete package linux-kernel-headers
Package: src:dvbstream Version: 0.6+cvs20090621-2 Severity: serious linux-kernel-headers was removed from unstable in 2007 (I think). It is now effectively a virtual package provided by linux-libc-dev, but it's not a documented virtual package name and I would like to stop providing it. Please change the dependency to linux-libc-dev. Ben. -- Ben Hutchings The first rule of tautology club is the first rule of tautology club. signature.asc Description: This is a digitally signed message part
Bug#959456: inotify-tools: Build-Depends on obsolete package linux-kernel-headers
Package: src:inotify-tools Version: 3.14-8 Severity: serious linux-kernel-headers was removed from unstable in 2007 (I think). It is now effectively a virtual package provided by linux-libc-dev, but it's not a documented virtual package name and I would like to stop providing it. linux-libc-dev is (transitively) build-essential, so you do not need to Build-Depend on it at all. Ben. -- Ben Hutchings The first rule of tautology club is the first rule of tautology club. signature.asc Description: This is a digitally signed message part
Bug#959457: isakmpd: Build-Depends on obsolete package linux-kernel-headers
Package: src:isakmpd Version: 20041012-8 Severity: serious linux-kernel-headers was removed from unstable in 2007 (I think). It is now effectively a virtual package provided by linux-libc-dev, but it's not a documented virtual package name and I would like to stop providing it. linux-libc-dev is (transitively) build-essential, so you do not need to Build-Depend on it at all. Ben. -- Ben Hutchings The first rule of tautology club is the first rule of tautology club. signature.asc Description: This is a digitally signed message part
Bug#959455: fakeroot-ng: Build-Depends on obsolete package linux-kernel-headers
Package: src:fakeroot-ng Version: 0.18-4 Severity: serious linux-kernel-headers was removed from unstable in 2007 (I think). It is now effectively a virtual package provided by linux-libc-dev, but it's not a documented virtual package name and I would like to stop providing it. linux-libc-dev is (transitively) build-essential, so you do not need to Build-Depend on it at all. Ben. -- Ben Hutchings The first rule of tautology club is the first rule of tautology club. signature.asc Description: This is a digitally signed message part
Bug#959225: libcap-ng FTBFS: Build-Depends: linux-kernel-headers is no longer provided
On Fri, 1 May 2020 09:18:20 +0200 Helmut Grohne wrote: > Source: libcap-ng > Version: 0.7.9-2.1 > Severity: serious > Tags: ftbfs patch > User: helm...@debian.org > Usertags: rebootstrap > > libcap-ng fails to build from source, because linux-libc-dev no longer > provides linux-kernel-headers, which is what libcap-ng Build-Depends on. > Please transition your dependency to linux-libc-dev: > > sed -i -e 's/linux-kernel-headers/linux-libc-dev/' debian/control I will restore this Provides temporarily as I had failed to see that there were still build-dependencies on it. But please do remove linux- kernel-headers, as it's not a documented virtual package. linux-libc-dev is (transitively) build-essential, so there is no need to explicitly Build-Depend on it. Ben. -- Ben Hutchings The first rule of tautology club is the first rule of tautology club. signature.asc Description: This is a digitally signed message part
Bug#959458: matchbox-panel: Build-Depends on obsolete package linux-kernel-headers
Package: src:matchbox-panel Version: 0.9.3-10 Severity: serious linux-kernel-headers was removed from unstable in 2007 (I think). It is now effectively a virtual package provided by linux-libc-dev, but it's not a documented virtual package name and I would like to stop providing it. linux-libc-dev is (transitively) build-essential, so you do not need to Build-Depend on it at all. Ben. -- Ben Hutchings The first rule of tautology club is the first rule of tautology club. signature.asc Description: This is a digitally signed message part
Bug#959459: netsend: Build-Depends on obsolete package linux-kernel-headers
Package: src:netsend Version: 0.0~svnr250-1.3 Severity: serious linux-kernel-headers was removed from unstable in 2007 (I think). It is now effectively a virtual package provided by linux-libc-dev, but it's not a documented virtual package name and I would like to stop providing it. linux-libc-dev is (transitively) build-essential, so you do not need to Build-Depend on it at all. Ben. -- Ben Hutchings The first rule of tautology club is the first rule of tautology club. signature.asc Description: This is a digitally signed message part
Bug#959460: paxtest: Build-Depends on obsolete package linux-kernel-headers
Package: src:paxtest Version: 1:0.9.15-1 Severity: serious linux-kernel-headers was removed from unstable in 2007 (I think). It is now effectively a virtual package provided by linux-libc-dev, but it's not a documented virtual package name and I would like to stop providing it. linux-libc-dev is (transitively) build-essential, so you do not need to Build-Depend on it at all. Ben. -- Ben Hutchings The first rule of tautology club is the first rule of tautology club. signature.asc Description: This is a digitally signed message part
Bug#959461: raidutils: Build-Depends on obsolete package linux-kernel-headers
Package: src:raidutils Version: 0.0.6-22 Severity: serious linux-kernel-headers was removed from unstable in 2007 (I think). It is now effectively a virtual package provided by linux-libc-dev, but it's not a documented virtual package name and I would like to stop providing it. linux-libc-dev is (transitively) build-essential, so you do not need to Build-Depend on it at all. Ben. -- Ben Hutchings The first rule of tautology club is the first rule of tautology club. signature.asc Description: This is a digitally signed message part
Bug#959452: Acknowledgement (array-info: Build-Depends on obsolete package linux-kernel-headers)
Actually, since linux-libc-dev is (transitively) build-essential, you do not need to Build-Depend on it at all. Ben. -- Ben Hutchings The first rule of tautology club is the first rule of tautology club. signature.asc Description: This is a digitally signed message part
Bug#959453: Acknowledgement (dvbstream: Build-Depends on obsolete package linux-kernel-headers)
Actually, since linux-libc-dev is (transitively) build-essential, you do not need to Build-Depend on it at all. Ben. -- Ben Hutchings The first rule of tautology club is the first rule of tautology club. signature.asc Description: This is a digitally signed message part
Bug#959454: Acknowledgement (dvbtune: Build-Depends on obsolete package linux-kernel-headers)
Actually, since linux-libc-dev is (transitively) build-essential, you do not need to Build-Depend on it at all. Ben. -- Ben Hutchings The first rule of tautology club is the first rule of tautology club. signature.asc Description: This is a digitally signed message part
Bug#959451: Acknowledgement (am-utils: Build-Depends on obsolete package linux-kernel-headers)
Actually, since linux-libc-dev is (transitively) build-essential, you do not need to Build-Depend on it at all. Ben. -- Ben Hutchings The first rule of tautology club is the first rule of tautology club. signature.asc Description: This is a digitally signed message part
Processed: block 959462 with 959225 959451 959452 959453 959454 959455 959456 959457 959458 959459 959460 959461
Processing commands for cont...@bugs.debian.org: > block 959462 with 959225 959451 959452 959453 959454 959455 959456 959457 > 959458 959459 959460 959461 Bug #959462 [linux-libc-dev] Provides undocumented virtual package linux-kernel-headers 959462 was not blocked by any bugs. 959462 was not blocking any bugs. Added blocking bug(s) of 959462: 959451, 959456, 959453, 959461, 959457, 959455, 959459, 959225, 959458, 959460, 959454, and 959452 > thanks Stopping processing here. Please contact me if you need assistance. -- 959462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959462 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959452:
Processed: tagging 955689
Processing commands for cont...@bugs.debian.org: > tags 955689 + fixed-upstream Bug #955689 [src:libcatmandu-filestore-perl] libcatmandu-filestore-perl: FTBFS: dh_auto_test: error: perl Build test --verbose 1 returned exit code 255 Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 955689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955689 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959223: marked as done (fcitx won't start anymore)
Your message dated Sat, 02 May 2020 17:04:01 + with message-id and subject line Bug#959223: fixed in librime 1.5.3+dfsg1-5 has caused the Debian Bug report #959223, regarding fcitx won't start anymore 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.) -- 959223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959223 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fcitx Version: 4.2.9.7-3 Severity: serious Dear Maintainer, I don't think I've done anything fcitx- or input-method-related, but fcitx just won't start after a normal reboot. I tried issuing fcitx command in a terminal but fcitx didn't show up either. Here is the output from fcitx-diagnose:https://cfp.vim-cn.com/cbhQ3 --- End Message --- --- Begin Message --- Source: librime Source-Version: 1.5.3+dfsg1-5 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of librime, 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 959...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated librime package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 02 May 2020 10:26:39 -0400 Source: librime Architecture: source Version: 1.5.3+dfsg1-5 Distribution: unstable Urgency: medium Maintainer: Debian Input Method Team Changed-By: Boyuan Yang Closes: 959223 Changes: librime (1.5.3+dfsg1-5) unstable; urgency=medium . * debian/control: + Bump debhelper compat to v13. + Force rebuild with opencc 1.0.6+. (Closes: #959223) * debian/librime1.shlibs: Bump minimal library version to 1.5.3+dfsg1-5~ to avoid potential ABI incompatibility cased by the rebuild. * debian/rules: Drop as-needed linker flag, not longer needed. Checksums-Sha1: 39d18d9299a5d2a1263f28100cc2efb5db9c69c4 2511 librime_1.5.3+dfsg1-5.dsc 4a6560e26e28aa7b32535ee59bf766361d579d2f 15432 librime_1.5.3+dfsg1-5.debian.tar.xz e3e24435a39c593a0931b9d68eaa364816e0b331 9323 librime_1.5.3+dfsg1-5_amd64.buildinfo Checksums-Sha256: 5ff4a63e0e105dacf8d85274308122a26feae373c3128c5dcb1caec6e62ba3ac 2511 librime_1.5.3+dfsg1-5.dsc 5ed12ae198dfc76bc12113d12746696e3d1ebcca970c15fa50cba314a4dbc662 15432 librime_1.5.3+dfsg1-5.debian.tar.xz d349a578d589f103a569538af00754d4f65b20273394460768af0879259a5a6b 9323 librime_1.5.3+dfsg1-5_amd64.buildinfo Files: 9c68ff85c71b027478be823fbf09fb59 2511 libs optional librime_1.5.3+dfsg1-5.dsc 673ed994f8288fd0b8dda84661e30ed5 15432 libs optional librime_1.5.3+dfsg1-5.debian.tar.xz 18e5720cc5c189bbad8c2387f6fe9132 9323 libs optional librime_1.5.3+dfsg1-5_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl6tpSIACgkQwpPntGGC Ws5iKBAAo7vLRxoyjDKDyJkdr3Yi8DHQmWXrKUt/aAkhr5I6MONPTj7dS/3vlWYQ esY85/NXr196si0Bq2oWKody/l3sTvN+jxdlOZyHmsPLCp0UNujuTeEP6jo6zMAN m1cRPqaKtaQdEz6ecjDguuIztfuIiHajss1F6u7FOICc9LPQj8Em3S2ogMjfz1/K KtCu8iqIWMlCGOmUn201ly8usZvZV1J2o4wB76idQKn90TohcH3ViS7kDMWbDcts hreSadmUOrSvvAO1kWVx1wTAdtIW7coTEZ6kNDBykqbEZD7XeKtwU+qXljKJmu5Q 3DDa1XixELDCtBJBccx+UURWpmXViThwq1XJSUm3CXrXRr/x85RLWpafahm4VqDm Yx1MDGladZGJ1lSR7Qb5xeboSLk75zC/lzdreESJVOqkcRE3i746yRbunvYWfV9+ e16wVxQ+VyWKH5q522oBFQmpZgSZK6hKUDauYlIDECX7FzqVEH96GFPGDQqLytAD VwSGl5a/Tj29+LBcqivjY2iRlKjyzHYZiq/+7af5XLMb25vD0RsAahLarp1dLEBO eTimzri2j8TBRKe0gTlvl8mMh9LVMLEkDaH0lZqpJeBVpXMUyVOmeN6rKO+KaAJ8 GkAP0L6Znjdgf7AqniZisEnLe/yZS+wzpe3X4b9/97+f2M0dTNw= =BdGL -END PGP SIGNATURE End Message ---
Bug#959378: marked as done (gap-guava-bin: please update for new GAP ABI)
Your message dated Sat, 02 May 2020 17:18:38 +
with message-id
and subject line Bug#959378: fixed in gap-guava 3.15+ds-2
has caused the Debian Bug report #959378,
regarding gap-guava-bin: please update for new GAP ABI
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.)
--
959378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959378
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gap-guava-bin
Version: 3.15+ds-1
Severity: serious
Dear Debian Science Maintainers,
Please update gap-guava for the new GAP ABI.
1) GAP 4.11.0 includes libgap7, libgap-dev as a normal Debian
shared library package.
2) There is now an officially supported ABI for the GAP kernel.
the current kernel ABI version is 7
In the file /usr/lib/gap/sysinfo.gap
GAParch=x86_64-pc-linux-gnu-default64-kv7
GAP_KERNEL_MAJOR_VERSION=7
kv7 mean kernel version 7.
If your package is built against the GAP 4.11.0 kernel, please make it
depends on gap-kernel-7.
Cheers,
--
Bill.
Imagine a large red swirl here.
--- End Message ---
--- Begin Message ---
Source: gap-guava
Source-Version: 3.15+ds-2
Done: Jerome Benoit
We believe that the bug you reported is fixed in the latest version of
gap-guava, 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 959...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jerome Benoit (supplier of updated gap-guava package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 02 May 2020 17:01:53 +
Source: gap-guava
Architecture: source
Version: 3.15+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Jerome Benoit
Closes: 959378
Changes:
gap-guava (3.15+ds-2) unstable; urgency=medium
.
* Debianization:
- debian/copyright:
- copyright year tuple, update;
- debian/control:
- Maintainer address, update;
- Rules-Requires-Root, introduce and set to no;
- Depends field:
- gap, bump to 4.11.0 ;
- Standards Version, bump to 4.5.0 (no change);
- debian/tests:
- d/t/makecheck.tst, harden (Closes: #959378);
- debian/{rules,gap-guava-bin.install,patches/debianization.patch}, put
internal binary executable inside the /usr/libexec hierarchy
(executable-in-usr-lib fix).
Checksums-Sha1:
e1a3958e4af7d46005b7c56a788c3aef9d6f1a1e 2896 gap-guava_3.15+ds-2.dsc
aded78c4aa4d226ec7c162f0af7c22dfa981af2a 7184 gap-guava_3.15+ds-2.debian.tar.xz
9379ac290da5a1a9e656a1bdbdf47e90b0ef48cb 8623
gap-guava_3.15+ds-2_source.buildinfo
Checksums-Sha256:
97f25d40172b3c94f47617ce687f6c9b013d7ffbbd5e8b13ae2c76fa1a6e637c 2896
gap-guava_3.15+ds-2.dsc
a3a4430b3b2bf3e45013ed24486dfaa9b71d5636fe3c96aa35fae4b55cf2a1d6 7184
gap-guava_3.15+ds-2.debian.tar.xz
84c23572bf8afe8eb2f903407fd8319fada4081a37451e0fbe3973c7a05fd2e3 8623
gap-guava_3.15+ds-2_source.buildinfo
Files:
7a4f6ed14c2cf9d02c620abb8c7d9c6d 2896 math optional gap-guava_3.15+ds-2.dsc
d498f0e007042e54fb69bfea00eaa420 7184 math optional
gap-guava_3.15+ds-2.debian.tar.xz
5b89d24637b13ad3b8fb79a79071da75 8623 math optional
gap-guava_3.15+ds-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQRJBAEBCgAzFiEEriiuFXEN/x2H5adiP5IZpn82xosFAl6tqNMVHGNhbGN1bHVz
QHJlem96ZXIubmV0AAoJED+SGaZ/NsaLO/cf/2CkL122A2pEa+ZWF6CDFOopH5lX
Zo68oR9w4O5+73DvU4Dj/Cu5bGDwOyRcqBqJihuSxY5sKMPxNQj4jwaPojwOq1DB
eDJksJ4+/s8X0jO5ama8FhO3MlmcRLcphJUda2eIMEVneFtI3iWzzFcEFb0MwKCo
Lu/reLsAcFlgOsdRTS7JLuTEGjcKobJ+5r0mgd4PVhqQ+L1xmWE7kmOQFJgdrTH3
Vi3VY8/GNPNd12k4D88BULA92CD3YWhSFBA/CDr6WT5r0mVbw6kRyWUiOvPqGOsb
hlj6IV/Jx8EudCvM+CXq2chc8Ijwwy2NfWXl6iwRjyD6Qc/ujtoS3X4tT0uMGB1y
Uf6JClMbkznPsxBHhBCHJuZRqX+mKnJRLTURTddp60sYpLJMEnyntgL+0nxlLUOf
4pgG7+5ZNcwZGRfnJsDy1qAMvBTe77hU/+UO1oDQ0ZWKcihzMZ6ChRQUE9y539g5
gMgUVJsA8qZBL0Lgy/IngLAVrfQAMNXFXacMCJdJpw0uChLx5Jd/RnS3/FZvWu+U
eJWhbDI88VXjsB6QyMsO62gIVQayd2AMr4SMeY/QHpjvRSZ3dfg4h5saTDADvLnf
m1PBK3XH6DRqFJ56v7Misc3nuFXsWWvmgj1LQZjiX82d07Och7MM0s4+hkqXDWuT
Fy4k6HpNeKkQhtoyVX8tuJLmk5YIQTFr+K6r+9gzcSX4GGwLu8HG8804ZJUjIks6
/bqkM9fk+Rmg0ny6w5Hq/RYxvqWL2AJOPndre9+qarLXpxC7sH85xMsNr9GOYXVq
IzHc7iX0X+JFN20c+F5uv7WdXjpU4NVrEN25l0s5EJTq732ywql9gHTItG
Processed: birdfont: diff for NMU version 2.28.0-1.1
Processing control commands: > tags 955680 + patch Bug #955680 [src:birdfont] birdfont: FTBFS: ld: build/bin//libbirdfont.so: undefined reference to `cairo_gobject_surface_get_type' Added tag(s) patch. > tags 955680 + pending Bug #955680 [src:birdfont] birdfont: FTBFS: ld: build/bin//libbirdfont.so: undefined reference to `cairo_gobject_surface_get_type' Added tag(s) pending. -- 955680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955680 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#955680: birdfont: diff for NMU version 2.28.0-1.1
Control: tags 955680 + patch
Control: tags 955680 + pending
Dear maintainer,
I've prepared an NMU for birdfont (versioned as 2.28.0-1.1) and uploaded
it to DELAYED/14. Please feel free to tell me if I should cancel it.
cu
Adrian
diff -Nru birdfont-2.28.0/debian/changelog birdfont-2.28.0/debian/changelog
--- birdfont-2.28.0/debian/changelog 2019-10-11 18:42:17.0 +0300
+++ birdfont-2.28.0/debian/changelog 2020-05-02 20:40:39.0 +0300
@@ -1,3 +1,10 @@
+birdfont (2.28.0-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Link with libcairo-gobject. (Closes: #955680)
+
+ -- Adrian Bunk Sat, 02 May 2020 20:40:39 +0300
+
birdfont (2.28.0-1) unstable; urgency=medium
* New upstream release
diff -Nru birdfont-2.28.0/debian/patches/cairo-gobject.patch birdfont-2.28.0/debian/patches/cairo-gobject.patch
--- birdfont-2.28.0/debian/patches/cairo-gobject.patch 1970-01-01 02:00:00.0 +0200
+++ birdfont-2.28.0/debian/patches/cairo-gobject.patch 2020-05-02 20:40:39.0 +0300
@@ -0,0 +1,14 @@
+Description: Link with libcairo-gobject.
+Author: Adrian Bunk
+Bug-Debian: https://bugs.debian.org/955680
+
+--- birdfont-2.28.0.orig/dodo.py
birdfont-2.28.0/dodo.py
+@@ -335,6 +335,7 @@ def make_libbirdfont(target_binary, deps
+ $({pkg-config} --libs gio-2.0) \
+ $({pkg-config} --libs fontconfig) \
+ $({pkg-config} --libs cairo) \
++$({pkg-config} --libs cairo-gobject) \
+ $({pkg-config} --libs glib-2.0) \
+ $({pkg-config} --libs xmlbird) \
+ -L./build -L./build/bin -l birdgems \
diff -Nru birdfont-2.28.0/debian/patches/series birdfont-2.28.0/debian/patches/series
--- birdfont-2.28.0/debian/patches/series 2019-10-11 18:42:17.0 +0300
+++ birdfont-2.28.0/debian/patches/series 2020-05-02 20:40:39.0 +0300
@@ -1 +1,2 @@
0001-Don-t-install-Roboto-Regular.ttf.patch
+cairo-gobject.patch
Bug#959473: orthanc-dicomweb build-dependencies unsatisfiable on armel
Package: orthanc-dicomweb Version: 1.1+dfsg-1 Severity: serious x-debbugs-cc: node-axios My self-contained buildability check script detected that armel binaries for orthanc-dicomweb were present in testing, but the build-dependencies for orthanc-dicomweb could not be satisified on armel. Specifically orthanc-dicomweb depends on the arch-all package node-axios which in turn depends on nodejs which is not available on armel. What took me a while to figure out is how exactly things had got to this state. It seems that orthanc-dicomweb gained the build-dependency on node-axios in version 1.0+dfsg-1 which got stuck in unstable for a while. A while later 1.0+dfsg-2 was uploaded, a request was made to the ftpmasters to remove the old packages ( https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944732 ). The removal request was actioned and orthanc-dicomweb migrated to testing without armel support. 1.1+dfsg-1 was also uploaded and migrated to testing, initially without armel support. Then a month or so later a buggy version of node-pegjs was uploaded that contained "Provides: libjs-pegjs, node-peg, nodejs, pegjs". The bug was fixed a week or so later, but not before it had allowed the buildds to build armel packages for orthanc-dicomweb 1.1+dfsg-1. The release teams build-dependency checks are not sophisticated enough to detect this either and so the armel binaries made it into testing (even though the package that had enabled them to build never did). Since it seems that the orthanc-dicomweb build does not actually need nodejs (the armel build succeeded after-all) that would seem to leave two ways to get back to a consistent state. 1. Request again removal of the armel binaries. This is probablly the easiest option, but it's not really in keeping with "packages must be built on as many architectures as reasonably possible". 2. Restructure the "node-axios" package and it's dependencies to provide a "libjs-axios" package that can be installed without nodejs. I am ccing the node-axios maintainers on this bug report so they can comment on the feasibility of providing a libjs-axios package that can be installed on architectures where nodejs is not available.
Processed: block 944018 with 950611
Processing commands for cont...@bugs.debian.org: > block 944018 with 950611 Bug #944018 [ocsinventory-reports] ocsinventory-reports: depends on no longer available libjs-select2.js 944018 was not blocked by any bugs. 944018 was not blocking any bugs. Added blocking bug(s) of 944018: 950611 > thanks Stopping processing here. Please contact me if you need assistance. -- 944018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944018 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 920261 is serious
Processing commands for cont...@bugs.debian.org: > severity 920261 serious Bug #920261 [ocsinventory-reports] ocsinventory-reports doesn't depend on php-zip Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 920261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920261 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959461: marked as done (raidutils: Build-Depends on obsolete package linux-kernel-headers)
Your message dated Sat, 02 May 2020 18:48:49 + with message-id and subject line Bug#959461: fixed in raidutils 0.0.6-23 has caused the Debian Bug report #959461, regarding raidutils: Build-Depends on obsolete package linux-kernel-headers 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.) -- 959461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959461 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:raidutils Version: 0.0.6-22 Severity: serious linux-kernel-headers was removed from unstable in 2007 (I think). It is now effectively a virtual package provided by linux-libc-dev, but it's not a documented virtual package name and I would like to stop providing it. linux-libc-dev is (transitively) build-essential, so you do not need to Build-Depend on it at all. Ben. -- Ben Hutchings The first rule of tautology club is the first rule of tautology club. signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: raidutils Source-Version: 0.0.6-23 Done: b...@debian.org (Barak A. Pearlmutter) We believe that the bug you reported is fixed in the latest version of raidutils, 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 959...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Barak A. Pearlmutter (supplier of updated raidutils package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 02 May 2020 17:03:40 +0100 Source: raidutils Architecture: source Version: 0.0.6-23 Distribution: unstable Urgency: medium Maintainer: Barak A. Pearlmutter Changed-By: Barak A. Pearlmutter Closes: 959461 Changes: raidutils (0.0.6-23) unstable; urgency=medium . [ Ondřej Nový ] * d/changelog: Remove trailing whitespaces . [ Barak A. Pearlmutter ] * Bump debhelper from old 10 to 12. * Set debhelper-compat version in Build-Depends. * Bump policy * remove obsolete build dependency (closes: #959461) * Rules-Requires-Root: no Checksums-Sha1: a3a915b7faf776e5bf308d6bf6679d435d30768d 1966 raidutils_0.0.6-23.dsc 1c571c89a168485460e5f4acfa9564fe32c548f9 24716 raidutils_0.0.6-23.debian.tar.xz fe8446af04c629b7f10cf532c0d0b549a52614d4 5995 raidutils_0.0.6-23_source.buildinfo Checksums-Sha256: b55b51e1148e9c2fd9e90a248710131f727de82b0031404cd96c2723fb5434c2 1966 raidutils_0.0.6-23.dsc 60846bf46251e87c5c6c250e0819668b3381a4181153d659f02b4199948c4a9c 24716 raidutils_0.0.6-23.debian.tar.xz 745de9b4f64fadfad38b78a06445e75d29541cf934774b22a38164a0f654435e 5995 raidutils_0.0.6-23_source.buildinfo Files: 1e8277376055e065a29b1aed16983e64 1966 admin optional raidutils_0.0.6-23.dsc 1667842a2d3f4541dd3f2883d73affd1 24716 admin optional raidutils_0.0.6-23.debian.tar.xz 8f11bf83a0aed601de8e81eeb8c37a82 5995 admin optional raidutils_0.0.6-23_source.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCgAtFiEEZPQp426hHMLZZlRvEltXR14ZDRgFAl6tvSsPHGJhcEBkZWJp YW4ub3JnAAoJEBJbV0deGQ0YdpEQAK3K9pY3CoWRgiNtBhSoKjB5z07gNjW/FxpH 9sCJgLIbK9ON1SQiCmU7Jd9PZ+E2eL6ZthlZOwkP7itA1sPQpBYT/4aUGjBY0wxd eqQIZVmWe3yWVCRz4Mw9IRmNMbeDTyDCAgzVI7l+stZWyILOEih5PireEm2RR7dA l6napcdoiaP0T4RCtsYXOyT7aJqg5DzoUcgAuU1aXdcF3MZiUfmeejvmydo6lhFF SoOkN6q+JyzuwtD3CGnLiJq1nwQKbLfjNEww5tb+ih2AYWGDMeBh/0dBlsXdb0GV 8jDgMrfEQHXRPKIeUzlWaVvliSYlNGh+u9onB+OATL5gdu4dQmsU/boXOVgkQKD5 2beXadQzZ/W2o0ZncQsWdkTIs16eddXXEpbXKJYEubVP+gFV3tDcI9Iu7sgWTb97 nRvtXpVDmDFf5V6nxOoPX3UZPkVUBnLGe85J3Od3eGsKX7TpAABLIwQN6H7pS/79 MRr5Gs+F0s1vjVECFQ3Golr9KdWDODW0lurMU3q67OWqdMr22BQ8cd37R9z/J8QK avU5Xg3LFg+oVogfeR+RAg7HQpHIAXSzJeHzQXDbijQgJzwo39bBxHJUrUlo9DzL Zh5opQhYHcoRGjm+UtAmRloK3DSjB7z9AgOsicuWqeHbCWMHos8zLbWFEtoM6Z0d EjVhx5B7 =JcTP -END PGP SIGNATURE End Message ---
Bug#959475: screenkey: doesn't respect settings
Package: screenkey Version: 0.10-1 Severity: grave Justification: renders package unusable The python3 version seems almost entirely broken on my Debian testing system. Almost all settings are ignored, regardless of whether I change them using command-line switches or the settings GUI. Backspace shows as [⁰⁰₀₈] instead of ⌫. No matter what font I choose, it uses some fixed one that apparently lacks the symbol for backspace and many other keys. No matter what setting I choose for --bak-mode, it shows the same broken backspace unicode replacement instead of erasing the last char. --key-mode is ignored as well. When changing settings through the setting GUI, the following exception is printed: File "/usr/lib/python3/dist-packages/Screenkey/screenkey.py", line 340, in on_cbox_modes_changed self.options.key_mode = KEY_MODES.keys()[index] TypeError: 'dict_keys' object is not subscriptable Downgrading to 0.9-2 from stable fixes all of this. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (990, 'stable'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-debug'), (500, 'unstable'), (500, 'stable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8), LANGUAGE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- Tomáš Janoušek, a.k.a. Pivník, a.k.a. Liskni_si, http://work.lisk.in/
Bug#954259: innoextract: diff for NMU version 1.8-1.1
Control: tags 954259 + patch Dear maintainer, I've prepared an NMU for innoextract (versioned as 1.8-1.1) and uploaded it to DELAYED/14. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru innoextract-1.8/debian/changelog innoextract-1.8/debian/changelog --- innoextract-1.8/debian/changelog 2020-01-15 17:30:07.0 +0200 +++ innoextract-1.8/debian/changelog 2020-05-02 21:00:51.0 +0300 @@ -1,3 +1,11 @@ +innoextract (1.8-1.1) unstable; urgency=low + + * Non-maintainer upload. + * Go back to debhelper-compat 11 to work around dwz issues on +mipsel and mips64el. (see #956954) (Closes: #954259) + + -- Adrian Bunk Sat, 02 May 2020 21:00:51 +0300 + innoextract (1.8-1) unstable; urgency=medium * Move to new upstream version. Deprecating the last patch diff -Nru innoextract-1.8/debian/control innoextract-1.8/debian/control --- innoextract-1.8/debian/control 2020-01-15 17:30:07.0 +0200 +++ innoextract-1.8/debian/control 2020-05-02 21:00:35.0 +0300 @@ -8,8 +8,7 @@ Vcs-git: https://salsa.debian.org/lhw-guest/innoextract.git Homepage: http://constexpr.org/innoextract/ Build-Depends: cmake, - debhelper (>= 12), - debhelper-compat(= 12), + debhelper-compat(= 11), dpkg-dev (>= 1.16.1~), libboost-iostreams-dev, libboost-filesystem-dev,
Processed: innoextract: diff for NMU version 1.8-1.1
Processing control commands: > tags 954259 + patch Bug #954259 [src:innoextract] src:innoextract: fails to migrate to testing for too long Added tag(s) patch. -- 954259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954259 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#937431: marked as done (pyepl: Python2 removal in sid/bullseye)
Your message dated Sat, 02 May 2020 20:55:09 + with message-id and subject line Bug#959213: Removed package(s) from unstable has caused the Debian Bug report #937431, regarding pyepl: Python2 removal in sid/bullseye 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.) -- 937431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937431 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pyepl Version: 1.1.0+git12-g365f8e3-3 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:pyepl If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 1.1.0+git12-g365f8e3-3+rm Dear submitter, as the package pyepl 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/959213 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#935413: marked as done (ruby2.5: flaky autopkgtest: base dir expected vs actual mismatch)
Your message dated Sat, 02 May 2020 20:54:04 + with message-id and subject line Bug#959203: Removed package(s) from unstable has caused the Debian Bug report #935413, regarding ruby2.5: flaky autopkgtest: base dir expected vs actual mismatch 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.) -- 935413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935413 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby2.5 Version: 2.5.5-3 Severity: serious Tags: sid bullseye buster X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: flaky Dear maintainers, With a recent upload of ncurses the autopkgtest of ruby2.5 fails in stable when that autopkgtest is run with the binary packages of ncurses from stable-proposed-updates. The same happened in testing. However, when the test was retried, the test passed. I looked into the history of your autopkgtest and it fails once in a while with the same error every time (as far as I checked). Because the unstable-to-testing migration software now blocks on regressions in testing, flaky tests, i.e. tests that flip between passing and failing without changes to the list of installed packages, are wasting peoples time. In this case, it also wasted time of the stable release managers due to the failure in stable. Please either fix the test to be more robust, or use the "flaky" restriction for the offending test. I copied some of the output at the bottom of this report. I'll have the migration software ignore the results of your autopkgtest until this bug is fixed. Paul https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby2.5/2332519/log.gz 1) Failure: TestGemSpecification#test_base_dir_default [/tmp/autopkgtest-lxc.a80kp91c/downtmp/autopkgtest_tmp/test/rubygems/test_gem_specification.rb:1947]: --- expected +++ actual @@ -1 +1 @@ -"/var/lib/gems/2.5.0" +"/tmp/test_rubygems_17185/default" signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Version: 2.5.7-1+rm Dear submitter, as the package ruby2.5 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/959203 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#956862: marked as done (ho22bus: Consider removing this package)
Your message dated Sat, 02 May 2020 20:55:29 + with message-id and subject line Bug#959216: Removed package(s) from unstable has caused the Debian Bug report #956862, regarding ho22bus: Consider removing this package 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.) -- 956862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956862 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ho22bus Version: 0.9.1-2 Severity: serious X-Debbugs-CC: cheny...@gmail.com Dear Debian ho22bus maintainer, After reviewing the ho22bus package [1] in Debian, I found that this package saw no upload in the past 8 years. Currently its upstream project is also defunct (previously hosted on Google Code).As a result, I think this package should be suitable for removal from Debian archive. I will submit a removal request 15 days later (after Apr. 30, 2020). If you have any thoughts, please feel free to let me know. [1] https://tracker.debian.org/pkg/ho22bus -- Best Regards, Boyuan Yang --- End Message --- --- Begin Message --- Version: 0.9.1-2+rm Dear submitter, as the package ho22bus 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/959216 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#955792: marked as done (python-imaging-doc-handbook: Please remove this package)
Your message dated Sat, 02 May 2020 20:55:56 + with message-id and subject line Bug#959217: Removed package(s) from unstable has caused the Debian Bug report #955792, regarding python-imaging-doc-handbook: Please remove this package 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.) -- 955792: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955792 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-imaging-doc-handbook Version: 1.1.2-1.2 Severity: serious Tags: sid bullseye X-Debbugs-CC: s...@debian.org Dear Debian python-imaging-doc-handbook maintainer, Since the Python Imaging Library is no longer part of Debian (it has long been replaced by Pillow) and that PIL upstream has been dead for 11 years, it doesn't make sense for this package to be still left in the Debian archive. Please consider removing it. I will consider filing a Removal bug 28 days later (after May 02, 2020) myself if there's no response. If you have any thoughts, please let me know ASAP. -- Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Version: 1.1.2-1.2+rm Dear submitter, as the package python-imaging-doc-handbook 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/959217 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#937484: marked as done (pymtp: Python2 removal in sid/bullseye)
Your message dated Sat, 02 May 2020 20:52:52 + with message-id and subject line Bug#959200: Removed package(s) from unstable has caused the Debian Bug report #937484, regarding pymtp: Python2 removal in sid/bullseye 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.) -- 937484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937484 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pymtp Version: 0.0.6-1.1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:pymtp If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 0.0.6-1.1+rm Dear submitter, as the package pymtp 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/959200 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#941539: marked as done (mh-e: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended)
Your message dated Sat, 02 May 2020 20:58:54 + with message-id and subject line Bug#959370: Removed package(s) from unstable has caused the Debian Bug report #941539, regarding mh-e: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended 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.) -- 941539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941539 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mh-e Version: 8.5-2.1 Severity: serious Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu eoan ubuntu-patch Hi Peter, The texlive-generic-recommended transitional package has been dropped from texlive-base in sid. Please update your build-dependency to texlive-plain-generic instead. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org diff -Nru mh-e-8.5/debian/control mh-e-8.5/debian/control --- mh-e-8.5/debian/control 2017-01-08 10:58:39.0 -0800 +++ mh-e-8.5/debian/control 2019-10-01 14:21:47.0 -0700 @@ -2,7 +2,7 @@ Section: mail Priority: extra Maintainer: Peter S Galbraith -Build-Depends: debhelper (>> 4.0.0), texinfo, emacs25-nox | emacs25 | emacs24, texlive-latex-base, texlive-generic-recommended +Build-Depends: debhelper (>> 4.0.0), texinfo, emacs25-nox | emacs25 | emacs24, texlive-latex-base, texlive-plain-generic Standards-Version: 3.9.2 Homepage: http://mh-e.sourceforge.net/ --- End Message --- --- Begin Message --- Version: 8.5-2.1+rm Dear submitter, as the package mh-e 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/959370 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#934993: marked as done (mh-e: FTBFS because transitional emacs25 et al. doesn't exist anymore)
Your message dated Sat, 02 May 2020 20:58:54 + with message-id and subject line Bug#959370: Removed package(s) from unstable has caused the Debian Bug report #934993, regarding mh-e: FTBFS because transitional emacs25 et al. doesn't exist anymore 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.) -- 934993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934993 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mh-e Version: 8.5-2.1 Severity: serious Justification: FTBFS Tags: ftbfs Hi, The emacs source package has been providing transitional packages for the buster release, but apparently decided to drop them. Because you (build) depend on them, you package now can't be build. In bug #934977 I read you could (build) depend on emacs-gtk instead. Paul -- System Information: Debian Release: 10.0 APT prefers stable-debug APT policy: (500, 'stable-debug'), (500, 'stable'), (200, 'stable'), (100, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mh-e depends on: ii dpkg1.19.7 ii emacs 1:26.1+1-3.2 ii emacs-gtk [emacs] 1:26.1+1-3.2 ii install-info6.5.0.dfsg.1-4+b1 pn nmh | mailutils-mh Versions of packages mh-e recommends: pn compface Versions of packages mh-e suggests: ii imagemagick 8:6.9.10.23+dfsg-2.1 ii imagemagick-6.q16 [imagemagick] 8:6.9.10.23+dfsg-2.1 pn mailcrypt pn picon-domains pn swish++ pn w3m-el ii wget 1.20.1-1.1 signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Version: 8.5-2.1+rm Dear submitter, as the package mh-e 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/959370 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#918241: marked as done (frown FTBFS: Fails to build docs - missing font, plue more problems)
Your message dated Sat, 02 May 2020 20:57:15 + with message-id and subject line Bug#959368: Removed package(s) from unstable has caused the Debian Bug report #918241, regarding frown FTBFS: Fails to build docs - missing font, plue more problems 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.) -- 918241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918241 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:frown Version: 0.6.2.3-6 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi! I've been doing a full rebuild of the Debian archive, building all source packages targeting armel and armhf using arm64 hardware. We are planning in future to move all of our 32-bit armel/armhf builds to using arm64 machines, so this rebuild is to identify packages that might have problems with this configuration. I've found that frown fails to build from source for armhf on aem64, but the problem is generic. I can see that it also FTBFS in sid at the moment for amd64: ... kpathsea: Running mktextfm cmbtt10 mkdir: cannot create directory '././homedoesnotexistatbuildtime': Permission denied mktextfm: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input cmbtt10 This is METAFONT, Version 2.7182818 (TeX Live 2019/dev/Debian) (preloaded base=mf) kpathsea: Running mktexmf cmbtt10 ! I can't find file `cmbtt10'. <*> ...=ljfour; mag:=1; nonstopmode; input cmbtt10 Please type another input file name ! Emergency stop. ... Installing texlive-fonts-extra (new build-dep needed, I guess?) to get the cmbtt10 font gets past this particular problem, but then the build fails further down: ... [1 <./Pics/Frown.ps>] [2<./Pics/Frown.ps>] [3<./auto.1>] [4<./Pics/tuberling.ps>] mkdir -p html mv index.html Manual.html Manual.css Manual[0-9]*.html Manual[0-9]*.png *motif.gif html mv: cannot stat '*motif.gif': No such file or directory make[1]: *** [Makefile:112: html] Error 1 make[1]: Leaving directory '/work/stemci01/debian/build/frown/frown-0.6.2.3/Manual' make: *** [debian/rules:20: build/frown-doc] Error 2 At this point, I stopped looking further. -- System Information: Debian Release: 9.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Version: 0.6.2.3-6+rm Dear submitter, as the package frown 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/959368 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#932951: marked as done (pspp build-depends on cruft package.)
Your message dated Sat, 02 May 2020 20:58:18 + with message-id and subject line Bug#959371: Removed package(s) from unstable has caused the Debian Bug report #932951, regarding pspp build-depends on cruft package. 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.) -- 932951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932951 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pspp Version: 3.5.2-1 Tags: bullseye, sid, patch Severity: serious pspp build-depends on texlive-generic-reccomended which is no longer built by the texlive-base source package. Please build-depend on texlive-plain-generic instead. --- End Message --- --- Begin Message --- Version: 1.2.0-3+rm Dear submitter, as the package pspp 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/959371 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#932949: marked as done (gri build-depends on cruft package.)
Your message dated Sat, 02 May 2020 20:57:43 + with message-id and subject line Bug#959369: Removed package(s) from unstable has caused the Debian Bug report #932949, regarding gri build-depends on cruft package. 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.) -- 932949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932949 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gri Version: 3.5.2-1 Tags: bullseye, sid, patch Severity: serious gri build-depends on texlive-generic-reccomended which is no longer built by the texlive-base source package. Please build-depend on texlive-plain-generic instead. --- End Message --- --- Begin Message --- Version: 2.12.26-1+rm Dear submitter, as the package gri 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/959369 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#956472: marked as done (atitvout: Consider removing this package)
Your message dated Sat, 02 May 2020 20:56:54 + with message-id and subject line Bug#959218: Removed package(s) from unstable has caused the Debian Bug report #956472, regarding atitvout: Consider removing this package 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.) -- 956472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956472 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: atitvout Version: 0.4-13 Severity: serious Tags: sid bullseye X-Debbugs-CC: r...@gna.org Dear Debian atitvout maintainer, The upstream of atitvout was not active since 2003 (!). Besides, this package saw no upload in Debian since 2009. It is also an i386-only package currently. As a result, I believe we should have it removed before Buster release. I will submit the removal bug 15 days later (on Apr. 26, 2020) if I receive no reply. If you have any doubts, please let me know *immediately*. -- Best Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Version: 0.4-13+rm Dear submitter, as the package atitvout 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/959218 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#941513: marked as done (c-graph: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended)
Your message dated Sat, 02 May 2020 20:59:31 + with message-id and subject line Bug#959372: Removed package(s) from unstable has caused the Debian Bug report #941513, regarding c-graph: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended 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.) -- 941513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941513 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: c-graph Version: 2.0.1-3.1 Severity: serious Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu eoan ubuntu-patch Hi Adrienne, The texlive-generic-recommended transitional package has been dropped from texlive-base in sid. Please update your build-dependency to texlive-plain-generic instead. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org diff -Nru c-graph-2.0.1/debian/control c-graph-2.0.1/debian/control --- c-graph-2.0.1/debian/control2019-02-21 21:41:49.0 -0800 +++ c-graph-2.0.1/debian/control2019-10-01 11:38:10.0 -0700 @@ -2,7 +2,7 @@ Maintainer: Adrienne Gaye Thompson Section: math Priority: optional -Build-Depends: debhelper (>= 11), gfortran, texlive, texlive-generic-recommended, texinfo +Build-Depends: debhelper (>= 11), gfortran, texlive, texlive-plain-generic, texinfo Standards-Version: 4.3.0 Homepage: https://www.gnu.org/software/c-graph/ --- End Message --- --- Begin Message --- Version: 2.0.1-3.1+rm Dear submitter, as the package c-graph 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/959372 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#895376: marked as done (frown FTBFS: Encountered missing dependencies: base <4.10)
Your message dated Sat, 02 May 2020 20:57:15 + with message-id and subject line Bug#959368: Removed package(s) from unstable has caused the Debian Bug report #895376, regarding frown FTBFS: Encountered missing dependencies: base <4.10 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.) -- 895376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895376 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: frown Version: 0.6.2.3-5 Severity: serious https://buildd.debian.org/status/package.php?p=frown&suite=sid ... Configuring frown-0.6.2.3... CallStack (from HasCallStack): die', called at libraries/Cabal/Cabal/Distribution/Simple/Configure.hs:948:20 in Cabal-2.0.1.0:Distribution.Simple.Configure configureFinalizedPackage, called at libraries/Cabal/Cabal/Distribution/Simple/Configure.hs:470:12 in Cabal-2.0.1.0:Distribution.Simple.Configure configure, called at libraries/Cabal/Cabal/Distribution/Simple.hs:570:20 in Cabal-2.0.1.0:Distribution.Simple confHook, called at libraries/Cabal/Cabal/Distribution/Simple/UserHooks.hs:67:5 in Cabal-2.0.1.0:Distribution.Simple.UserHooks configureAction, called at libraries/Cabal/Cabal/Distribution/Simple.hs:174:19 in Cabal-2.0.1.0:Distribution.Simple defaultMainHelper, called at libraries/Cabal/Cabal/Distribution/Simple.hs:119:27 in Cabal-2.0.1.0:Distribution.Simple defaultMain, called at Setup.hs:11:8 in main:Main hlibrary.setup: Encountered missing dependencies: base <4.10 make: *** [/usr/share/cdbs/1/class/hlibrary.mk:142: configure-ghc-stamp] Error 1 --- End Message --- --- Begin Message --- Version: 0.6.2.3-6+rm Dear submitter, as the package frown 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/959368 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#949150: marked as done (gri: texi file need @documentencoding)
Your message dated Sat, 02 May 2020 20:57:43 + with message-id and subject line Bug#959369: Removed package(s) from unstable has caused the Debian Bug report #941557, regarding gri: texi file need @documentencoding 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.) -- 941557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941557 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gri Version: 2.12.26-1 Severity: serious Tags: ftbfs Justification: makes the package in question unusable or mostly so Dear Maintainer, In preparation of the netcdf transition as test rebuild of your package was done which FTBFS: makeinfo -I. gri.texi utf8 "\xF3" does not map to Unicode at /usr/share/texinfo/Texinfo/ParserNonXS.pm line 1796, line 19280. Malformed UTF-8 character: \xf3\x70\x65\x7a (unexpected non-continuation byte 0x70, immediately after start byte 0xf3; need 4 bytes, got 1) in pattern match (m//) at /usr/share/texinfo/Texinfo/ParserNonXS.pm line 3364. Malformed UTF-8 character (fatal) at /usr/share/texinfo/Texinfo/ParserNonXS.pm line 3364. make[1]: *** [Makefile:975: html] Error 25 Kind Regards, Bas --- End Message --- --- Begin Message --- Version: 2.12.26-1+rm Dear submitter, as the package gri 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/959369 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#935041: marked as done (mh-e: unbuildable in testing due to missing B-D)
Your message dated Sat, 02 May 2020 20:58:54 + with message-id and subject line Bug#959370: Removed package(s) from unstable has caused the Debian Bug report #935041, regarding mh-e: unbuildable in testing due to missing B-D to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 935041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935041 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mh-e Version: 8.5-2.1 Severity: serious Currently mh-e build-depends on emacs25-nox | emacs25 | emacs24 but none of these packages exist in testing. This makes mh-e unbuildable. Please build-depend on emacs-nox | emacs-gtk instead. --- End Message --- --- Begin Message --- Version: 8.5-2.1+rm Dear submitter, as the package mh-e 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/959370 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#941557: marked as done (gri: texi file need @documentencoding)
Your message dated Sat, 02 May 2020 20:57:43 + with message-id and subject line Bug#959369: Removed package(s) from unstable has caused the Debian Bug report #941557, regarding gri: texi file need @documentencoding 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.) -- 941557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941557 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gri Version: 2.12.26-1 Severity: serious Justification: FTBFS User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu eoan Hi Peter, The gri package appears to fail to build from source in unstable: [...] cd tst_suite ; make make[2]: Entering directory '/tmp/gri-2.12.26/doc/tst_suite' perl ./../gri2html tst_IO.gri tst_IO.html perl ./../gri2html tst_control.gri tst_control.html perl ./../gri2html tst_rpn.gri tst_rpn.html perl ./../gri2html tst_var_syn.gri tst_var_syn.html make[2]: Leaving directory '/tmp/gri-2.12.26/doc/tst_suite' makeinfo -I. gri.texi utf8 "\xF3" does not map to Unicode at /usr/share/texinfo/Texinfo/ParserNonXS.pm line 1796, line 19280. Malformed UTF-8 character: \xf3\x70\x65\x7a (unexpected non-continuation byte 0x70, immediately after start byte 0xf3; need 4 bytes, got 1) in pattern match (m//) at /usr/share/texinfo/Texinfo/ParserNonXS.pm line 3364. Malformed UTF-8 character (fatal) at /usr/share/texinfo/Texinfo/ParserNonXS.pm line 3364. make[1]: *** [Makefile:975: html] Error 25 make[1]: Leaving directory '/tmp/gri-2.12.26/doc' make: *** [debian/rules:83: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 debuild: fatal error at line 1182: dpkg-buildpackage -us -uc -ui -b failed [...] -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Version: 2.12.26-1+rm Dear submitter, as the package gri 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/959369 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#953376: marked as done (src:mailman: Depends/Build-Depends on cruft package python-dnspython)
Your message dated Sat, 02 May 2020 21:01:59 + with message-id and subject line Bug#959435: Removed package(s) from unstable has caused the Debian Bug report #953376, regarding src:mailman: Depends/Build-Depends on cruft package python-dnspython 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.) -- 953376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953376 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:mailman Version: 1:2.1.29-1 Severity: serious Justification: Policy 2.2.1 This package Depends/Build-Depends on python-dnspython which is an NBS cruft package. Please update your package to use python3-dnspython, which is still provided (if the package will be ported to python3). Scott K --- End Message --- --- Begin Message --- Version: 1:2.1.29-1+rm Dear submitter, as the package mailman 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/959435 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#958930: marked as done (mailman: CVE-2020-12137)
Your message dated Sat, 02 May 2020 21:01:59 + with message-id and subject line Bug#959435: Removed package(s) from unstable has caused the Debian Bug report #958930, regarding mailman: CVE-2020-12137 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.) -- 958930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958930 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mailman Version: 1:2.1.29-1 Severity: grave Tags: security upstream Control: found -1 1:2.1.23-1+deb9u4 Control: found -1 1:2.1.23-1 Control: fixed -1 1:2.1.23-1+deb9u5 Control: fixed -1 1:2.1.29-1+deb10u1 Hi, Note filling this mainly for tracking and for the "regression" from stable. Given that, if no upload happens at point release time it might just prop-up from stable to unstable and so include the fix as well for bullseye. The following vulnerability was published for mailman. CVE-2020-12137[0]: | GNU Mailman 2.x before 2.1.30 uses the .obj extension for scrubbed | application/octet-stream MIME parts. This behavior may contribute to | XSS attacks against list-archive visitors, because an HTTP reply from | an archive web server may lack a MIME type, and a web browser may | perform MIME sniffing, conclude that the MIME type should have been | text/html, and execute JavaScript code. 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-2020-12137 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-12137 Regards, Salvatore --- End Message --- --- Begin Message --- Version: 1:2.1.29-1+rm Dear submitter, as the package mailman 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/959435 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#956359: marked as done (netgen: FTBFS with new opencascade 7.4 (library transistion))
Your message dated Sat, 02 May 2020 21:04:17 + with message-id and subject line Bug#956359: fixed in netgen 6.2.1804+dfsg1-3.1 has caused the Debian Bug report #956359, regarding netgen: FTBFS with new opencascade 7.4 (library transistion) 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.) -- 956359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:netgen Version: 6.2.1804+dfsg1-3 Severity: important Control: tags -1 +fixed-upstream +patch Control: block 956351 by -1 Hi Kurt, Adam, Dear Science Team, I'm currently preparing for the opencascade 7.4 transistion [1] and netgen FTBFS with the new version, available in experimental. [1] https://release.debian.org/transitions/html/auto-opencascade.html It seems so that upstream has a fix already [2], I can confirm that it also fix the FTBFS for the current version available in Debian: [2] https://github.com/NGSolve/netgen/commit/18070c9f03072cadffe7baed4ba4045dd9ea680e#diff-3ee1c88f2a71a62145e31da1ef21ea3f Attached is the build log and the patch I used to make it compile. (Note: I did NOT check if netgen also compiles with the patch and the current opencascade 7.3) I did also NOT test the new package, please speak up if you have concerns. Cheers, -- tobi -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: netgen Source-Version: 6.2.1804+dfsg1-3.1 Done: Tobias Frost We believe that the bug you reported is fixed in the latest version of netgen, 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 956...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tobias Frost (supplier of updated netgen package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 27 Apr 2020 22:01:24 +0200 Source: netgen Architecture: source Version: 6.2.1804+dfsg1-3.1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Tobias Frost Closes: 956359 Changes: netgen (6.2.1804+dfsg1-3.1) unstable; urgency=medium . * Non-maintainer upload. * Patch to fix FTBFS against opencascade 7.4. (Closes: #956359) Checksums-Sha1: 6745e4ebb0cde9bf1e8174a41838a0530241b344 2623 netgen_6.2.1804+dfsg1-3.1.dsc 43d5139900d7a4e4cd1e46b5440562ad3c50e844 11196 netgen_6.2.1804+dfsg1-3.1.debian.tar.xz 30975616c51506acc47a9bc84e9571273dc54d7d 8808 netgen_6.2.1804+dfsg1-3.1_source.buildinfo Checksums-Sha256: 05eea0b0a053b1cdc2fce7b384321348bc12339ac730da3590f0a5031d607673 2623 netgen_6.2.1804+dfsg1-3.1.dsc fa305e931c5730bb16d6b0b0f4cbcca0b5ac0803521c07a745c3ebd55b430642 11196 netgen_6.2.1804+dfsg1-3.1.debian.tar.xz 8355218435bf5cab641dc35693971d40b13e3928cf82a413d1871178c094a466 8808 netgen_6.2.1804+dfsg1-3.1_source.buildinfo Files: 31eb1c021902db3a8765f53d60346be5 2623 math optional netgen_6.2.1804+dfsg1-3.1.dsc 8f9763556e7aaec58f7eeb6c65c65991 11196 math optional netgen_6.2.1804+dfsg1-3.1.debian.tar.xz 5d67e2b17133275891e9d3db053e340c 8808 math optional netgen_6.2.1804+dfsg1-3.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAl6nOscACgkQkWT6HRe9 XTbs2g//QOgpeY3d5JMWmdABeeZZt5n5xCRTa8haBtD4Pdxn6L5TIAkLMIaM/gPK LK1/KzGMcb+iFVzhZUSH7V8wgdDU79J5fR9nNWuOSPX+1PyQdfrdLQ/swWhti0X+ ju+YVwKR41t3X5pTijkJgFDlOtGf71GHxFNJFNYh0QebWi7K7ccXzqYSYP54J4Um fvKpj4VZrIWjxgTUox6q/QeO2qgsoDmldhtunXuprCbi+5TAaXKYR0eDQznVSIsf wsBOlK41OUxMO7zG7rkRlnZH6UwwsTEQYSJdGtjvsBL+Cojt0oENg1b0ob5jGRTk +uwsAOKlDrZJt894ej4CucRYavSC8vqdnHdN2uAH2kaYI5oW7fK/aYGWXBK9v/xM SAKMxVAkA91UiPs3HBJ5TQ6M2zNG3bZc5N+lr9eHu9yGJFtfPsh/V7jd
Processed: found 953369 in 3.8.3~rc1-1
Processing commands for cont...@bugs.debian.org: > found 953369 3.8.3~rc1-1 Bug #953369 [libpython3.8-minimal] RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used Bug #953125 [libpython3.8-minimal] libpython3.8-minimal: /usr/lib/python3.8/subprocess.py:838: RuntimeWarning Marked as found in versions python3.8/3.8.3~rc1-1. Marked as found in versions python3.8/3.8.3~rc1-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 953125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953125 953369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953369 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#958051: marked as done (src:homebank: fails to migrate to testing for too long)
Your message dated Sat, 02 May 2020 21:22:15 + with message-id and subject line Bug#958051: fixed in homebank 5.3.2-1.1 has caused the Debian Bug report #958051, regarding src:homebank: fails to migrate to testing for too long 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.) -- 958051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958051 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: homebank Version: 5.2.2-1 Severity: serious Control: close -1 5.3.2-1 Tags: sid bullseye pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:homebank in its current version in unstable has been trying to migrate for 61 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. Your package is only blocked because the binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=homebank signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: homebank Source-Version: 5.3.2-1.1 Done: Paul Gevers We believe that the bug you reported is fixed in the latest version of homebank, 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 958...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Gevers (supplier of updated homebank 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: Fri, 17 Apr 2020 22:16:09 +0200 Source: homebank Architecture: source Version: 5.3.2-1.1 Distribution: unstable Urgency: medium Maintainer: Francesco Namuri Changed-By: Paul Gevers Closes: 958051 Changes: homebank (5.3.2-1.1) unstable; urgency=medium . * Non-maintainer upload. * source only upload to enable migration (Closes: #958051) Checksums-Sha1: a8521605b04bef5f70860973838c4ac0b958e378 1769 homebank_5.3.2-1.1.dsc e20610b38cd96efbbda232591dfaa25464c51822 8524 homebank_5.3.2-1.1.debian.tar.xz Checksums-Sha256: 0a5750672ed70c80d7d20954247f4daa3b2ebc26fce195b0bbd5d3accb8b 1769 homebank_5.3.2-1.1.dsc 0cbc17ef1f398c2832f702c774b7d5cdce84a210a51cd7791a83bc27aa26 8524 homebank_5.3.2-1.1.debian.tar.xz Files: 3939c41f4548631cbb786499154699b8 1769 gnome optional homebank_5.3.2-1.1.dsc 685c8b9580dcbe4f350978e165df1280 8524 gnome optional homebank_5.3.2-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQEyBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl6aDr4ACgkQnFyZ6wW9 dQrgeAf3da7QXXhjdfjBCVfuIjDq07y4/w15gW9Ytsl83Ny3glz1xhF4L7czVeWa HS8McFxnkWoSs1lnTixcpuJEdg05F7+h6IKWTm23IH7bjTJcrt8cCQFJX7tB3VQ9 x+Zq7pvlf1BDuqjCJGNd3Kh7chtn12W3LqKct1Nqwvc5hK3qZGrH8JsvRn1TRqBr 6ttDAyt1lF0SKSWgWvNb+dMpx3auvOxhar8BawG08F5oHGjGo5ZpPIN+1RRK9xA0 /yT6LXvxTPQxcqgUArKNJioJ8ztf1uy8QjWTFnJWNRmykfCliIny7TD310lPp0c7 5fmyGYAacAITXZsZ8RV0CgVsJR8l =HoVL -END PGP SIGNATURE End
Processed: tagging 959453, tagging 959455, tagging 959457, tagging 959458, tagging 959454, tagging 959452 ...
Processing commands for cont...@bugs.debian.org:
> tags 959453 + sid bullseye
Bug #959453 [src:dvbstream] dvbstream: Build-Depends on obsolete package
linux-kernel-headers
Added tag(s) bullseye and sid.
> tags 959455 + sid bullseye
Bug #959455 [src:fakeroot-ng] fakeroot-ng: Build-Depends on obsolete package
linux-kernel-headers
Added tag(s) sid and bullseye.
> tags 959457 + sid bullseye
Bug #959457 [src:isakmpd] isakmpd: Build-Depends on obsolete package
linux-kernel-headers
Added tag(s) bullseye and sid.
> tags 959458 + sid bullseye
Bug #959458 [src:matchbox-panel] matchbox-panel: Build-Depends on obsolete
package linux-kernel-headers
Added tag(s) sid and bullseye.
> tags 959454 + sid bullseye
Bug #959454 [src:dvbtune] dvbtune: Build-Depends on obsolete package
linux-kernel-headers
Added tag(s) bullseye and sid.
> tags 959452 + sid bullseye
Bug #959452 [src:array-info] array-info: Build-Depends on obsolete package
linux-kernel-headers
Added tag(s) bullseye and sid.
> tags 959461 + sid bullseye
Bug #959461 {Done: b...@debian.org (Barak A. Pearlmutter)} [src:raidutils]
raidutils: Build-Depends on obsolete package linux-kernel-headers
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
959452: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959452
959453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959453
959454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959454
959455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959455
959457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959457
959458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959458
959461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959461
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#954624: marked as done (deltachat-core: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc
Your message dated Sat, 02 May 2020 21:48:27 + with message-id and subject line Bug#952619: fixed in deltachat-core 0.45.0+ds-1 has caused the Debian Bug report #952619, regarding deltachat-core: FTBFS: dh_auto_configure: error: 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 returned exit code 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 952619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952619 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: deltachat-core Version: 0.39.0+ds-0.1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200321 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build >dh_update_autotools_config >dh_autoreconf >dh_auto_configure > 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.53.2 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: deltachat-core > Project version: 0.0.0 > Appending CFLAGS from environment: '-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' > Appending LDFLAGS from environment: ['-Wl,-z,relro'] > Appending CPPFLAGS from environment: '-Wdate-time -D_FORTIFY_SOURCE=2' > Appending CFLAGS from environment: '-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' > Appending LDFLAGS from environment: ['-Wl,-z,relro'] > Appending CPPFLAGS from environment: '-Wdate-time -D_FORTIFY_SOURCE=2' > C compiler for the host machine: cc (gcc 9.3.0 "cc (Debian 9.3.0-5) 9.3.0") > C linker for the host machine: cc ld.bfd 2.34 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Program git found: YES (/usr/bin/git) > meson.build:32: WARNING: Git version not found, using (dummy) project version > Run-time dependency threads found: YES > Library m found: YES > Found pkg-config: /usr/bin/pkg-config (0.29) > Run-time dependency zlib found: YES 1.2.11 > Run-time dependency openssl found: YES 1.1.1e > Run-time dependency libsasl2 found: YES 2.1.27 > Run-time dependency sqlite3 found: YES 3.31.1 > Program libetpan-config found: NO > Message: Using libetpan fallback... > > meson.build:103:2: ERROR: Subproject directory not found and libetpan.wrap > file not found > > 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 2020-03-22T03:20:11.090735 > 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.53.2 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: deltachat-core > Project version: 0.0.0 > Appending CFLAGS from environment: '-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' > Appending LDFLAGS from environment: ['-Wl,-z,relro'] > Appending CPPFLAGS from environment: '-Wdate-time -D_FORTIFY_SOURCE=2' > Sanity testing C compiler: cc > Is cross compiler: False. > Sanity check compiler command line: cc > /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.c -o > /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.exe -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pipe > -D_FILE_OFFSET_BITS=64 -Wl,-z,relro > Sanity check compile stdout: > > - > Sanity check compile stderr: > > - > Running test binary command: > /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.exe > C compiler for the build machine: cc (gcc 9.3.0 "cc (Debian 9.3.0-5) 9.3.0") > C linker for the build machine: cc ld.bfd 2.34 > Appending CFLAGS from environment: '-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' > Appending LDFLAGS from environment: ['-Wl,-z,relro'] > Appending CPPFLAGS from environment: '-Wdate-time -D_FORTIFY_SOURCE=2' > Sanity testing C compiler: cc > Is cross compiler: False. > Sanity chec
Bug#952619: marked as done (deltachat-core: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc
Your message dated Sat, 02 May 2020 21:48:27 + with message-id and subject line Bug#952619: fixed in deltachat-core 0.45.0+ds-1 has caused the Debian Bug report #952619, regarding deltachat-core: FTBFS: dh_auto_configure: error: 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 returned exit code 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 952619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952619 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: deltachat-core Version: 0.39.0+ds-0.1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200225 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules). Relevant part (hopefully): > debian/rules build > dh build >dh_update_autotools_config >dh_autoreconf >dh_auto_configure > 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.53.2 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: deltachat-core > Project version: 0.0.0 > Appending CFLAGS from environment: '-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' > Appending LDFLAGS from environment: ['-Wl,-z,relro'] > Appending CPPFLAGS from environment: '-Wdate-time -D_FORTIFY_SOURCE=2' > Appending CFLAGS from environment: '-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' > Appending LDFLAGS from environment: ['-Wl,-z,relro'] > Appending CPPFLAGS from environment: '-Wdate-time -D_FORTIFY_SOURCE=2' > C compiler for the host machine: cc (gcc 9.2.1 "cc (Debian 9.2.1-30) 9.2.1 > 20200224") > C linker for the host machine: cc ld.bfd 2.34 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Program git found: YES (/usr/bin/git) > meson.build:32: WARNING: Git version not found, using (dummy) project version > Run-time dependency threads found: YES > Library m found: YES > Found pkg-config: /usr/bin/pkg-config (0.29) > Run-time dependency zlib found: YES 1.2.11 > Run-time dependency openssl found: YES 1.1.1d > Run-time dependency libsasl2 found: YES 2.1.27 > Run-time dependency sqlite3 found: YES 3.31.1 > Program libetpan-config found: NO > Message: Using libetpan fallback... > > meson.build:103:2: ERROR: Subproject directory not found and libetpan.wrap > file not found > > 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 2020-02-26T12:46:27.625192 > 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.53.2 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: deltachat-core > Project version: 0.0.0 > Appending CFLAGS from environment: '-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' > Appending LDFLAGS from environment: ['-Wl,-z,relro'] > Appending CPPFLAGS from environment: '-Wdate-time -D_FORTIFY_SOURCE=2' > Sanity testing C compiler: cc > Is cross compiler: False. > Sanity check compiler command line: cc > /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.c -o > /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.exe -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pipe > -D_FILE_OFFSET_BITS=64 -Wl,-z,relro > Sanity check compile stdout: > > - > Sanity check compile stderr: > > - > Running test binary command: > /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.exe > C compiler for the build machine: cc (gcc 9.2.1 "cc (Debian 9.2.1-30) 9.2.1 > 20200224") > C linker for the build machine: cc ld.bfd 2.34 > Appending CFLAGS from environment: '-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' > Appending LDFLAGS from environment: ['-Wl,-z,relro'] > Appendi
Processed: Re: caml-crush, build-dependencies unsatisfiable on armel
Processing control commands: > found -1 1.0.8-1 Bug #929450 [caml-crush] caml-crush, build-dependencies unsatisfiable on armel There is no source info for the package 'caml-crush' at version '1.0.8-1' with architecture '' Unable to make a source version for version '1.0.8-1' Marked as found in versions 1.0.8-1. > tag -1 = sid Bug #929450 [caml-crush] caml-crush, build-dependencies unsatisfiable on armel Added tag(s) sid; removed tag(s) buster. > close -1 Bug #929450 [caml-crush] caml-crush, build-dependencies unsatisfiable on armel Marked Bug as done -- 929450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929450 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#929450: caml-crush, build-dependencies unsatisfiable on armel
Control: found -1 1.0.8-1 Control: tag -1 = sid Control: close -1 On Tue, 09 Jul 2019 13:56:40 +0200 Andreas Beckmann wrote: > The armel binaries have been removed from sid. and buster, too. Andreas
Processed: Bug#958789 marked as pending in libmodule-manifest-skip-perl
Processing control commands: > tag -1 pending Bug #958789 [src:libmodule-manifest-skip-perl] libmodule-manifest-skip-perl: FTBFS and unusable: Can't locate object method "_install_subs" Added tag(s) pending. -- 958789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958789 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#958789: marked as pending in libmodule-manifest-skip-perl
Control: tag -1 pending Hello, Bug #958789 in libmodule-manifest-skip-perl 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/perl-team/modules/packages/libmodule-manifest-skip-perl/-/commit/465057adc57b27fd0b7c6d3732494ce9eeac381d Add patch from upstream pull request to adapt to Moo 2.004000. Closes: #958789 (this message was generated automatically) -- Greetings https://bugs.debian.org/958789
Bug#958789: marked as done (libmodule-manifest-skip-perl: FTBFS and unusable: Can't locate object method "_install_subs")
Your message dated Sat, 02 May 2020 23:49:00 +
with message-id
and subject line Bug#958789: fixed in libmodule-manifest-skip-perl 0.23-2
has caused the Debian Bug report #958789,
regarding libmodule-manifest-skip-perl: FTBFS and unusable: Can't locate object
method "_install_subs"
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.)
--
958789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958789
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libmodule-manifest-skip-perl
Version: 0.23-1
Severity: grave
Tags: bullseye sid ftbfs
This package fails to build from source on current sid/amd64.
The whole module seems to be unusable.
Looking at the test build history at
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libmodule-manifest-skip-perl.html
this probably regressed between 2020-04-11 and 2020-04-15,
which coincides with the upload of libmoo-perl_2.004000-1.
Even rudimentary autopkgtest checks would have caught this and prevented
libmoo-perl from transitioning to testing if it caused the regression.
Please consider adding some, preferably by making the autopkgtest-pkg-perl
checks work.
PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness"
"-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 'blib/arch')"
t/*.t
Can't locate object method "_install_subs" via package
"Module::Manifest::Skip" at /usr/share/perl5/Moo.pm line 47.
BEGIN failed--compilation aborted at t/TestModuleManifestSkip.pm line 6.
Compilation failed in require at t/create.t line 3.
BEGIN failed--compilation aborted at t/create.t line 3.
t/create.t ..
Dubious, test returned 255 (wstat 65280, 0xff00)
No subtests run
Can't locate object method "_install_subs" via package
"Module::Manifest::Skip" at /usr/share/perl5/Moo.pm line 47.
[...]
Test Summary Report
---
t/create.t(Wstat: 65280 Tests: 0 Failed: 0)
Non-zero exit status: 255
Parse errors: No plan found in TAP output
t/recreate.t (Wstat: 65280 Tests: 0 Failed: 0)
Non-zero exit status: 255
Parse errors: No plan found in TAP output
t/skip1.t (Wstat: 65280 Tests: 0 Failed: 0)
Non-zero exit status: 255
Parse errors: No plan found in TAP output
t/update.t(Wstat: 65280 Tests: 0 Failed: 0)
Non-zero exit status: 255
Parse errors: No plan found in TAP output
Files=5, Tests=0, 0 wallclock secs ( 0.02 usr 0.00 sys + 0.09 cusr 0.02
csys = 0.13 CPU)
Result: FAIL
--
Niko Tyni nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: libmodule-manifest-skip-perl
Source-Version: 0.23-2
Done: gregor herrmann
We believe that the bug you reported is fixed in the latest version of
libmodule-manifest-skip-perl, 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 958...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
gregor herrmann (supplier of updated
libmodule-manifest-skip-perl package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 03 May 2020 01:29:06 +0200
Source: libmodule-manifest-skip-perl
Architecture: source
Version: 0.23-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group
Changed-By: gregor herrmann
Closes: 958789
Changes:
libmodule-manifest-skip-perl (0.23-2) unstable; urgency=medium
.
* Team upload.
.
[ Salvatore Bonaccorso ]
* Update Vcs-* headers for switch to salsa.debian.org
.
[ gregor herrmann ]
* debian/*: update URLs from {search,www}.cpan.org to MetaCPAN.
* debian/*: update GitHub URLs to use HTTPS.
.
[ Debian Janitor ]
* Use secure copyright file specification URI.
* Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
Repository-Browse.
.
[ gregor herrmann ]
* Add patch from upstream pull request to adapt to Moo 2.004000.
(Closes: #958789)
* Mark package as autopkgtest-able.
* Add buildtime and runtime dependency on libfile-sharedir-perl.
Thanks to autopkgtest.
Checksums-Sha1:
a297abe90cefe89a1f0344f4092370100a627267 2545
libmodule-manifest-s
Processed: Re: mozjs52: No longer maintained upstream
Processing commands for cont...@bugs.debian.org: > severity 912941 serious Bug #912941 [src:mozjs52] mozjs52: No longer maintained upstream Severity set to 'serious' from 'important' > severity 908234 serious Bug #908234 [src:cjs] cjs: Please switch to mozjs60 Severity set to 'serious' from 'important' > End of message, stopping processing here. Please contact me if you need assistance. -- 908234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908234 912941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912941 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: notfound 958841 in erlang/1:22.3+dfsg-1
Processing commands for cont...@bugs.debian.org:
> notfound 958841 erlang/1:22.3+dfsg-1
Bug #958841 {Done: Sergei Golovan } [src:erlang,
src:elixir-lang] erlang breaks elixir-lang autopkgtest: killed
Ignoring request to alter found versions of bug #958841 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
958841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958841
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#959503: salmon breaks trinityrnaseq autopkgtest: /usr/bin/ParaFly -c recursive_trinity.cmds -CPU 2 -v -shuffle died with ret 256
Source: salmon, trinityrnaseq
Control: found -1 salmon/1.2.1+ds1-1
Control: found -1 trinityrnaseq/2.6.6+dfsg-6
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of salmon the autopkgtest of trinityrnaseq fails in
testing when that autopkgtest is run with the binary packages of salmon
from unstable. It passes when run with only packages from testing. In
tabular form:
passfail
salmon from testing1.2.1+ds1-1
trinityrnaseq from testing2.6.6+dfsg-6
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of salmon to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=salmon
https://ci.debian.net/data/autopkgtest/testing/amd64/t/trinityrnaseq/5248098/log.gz
We are sorry, commands in file: [FailedCommands] failed. :-(
Error, cmd: /usr/bin/ParaFly -c recursive_trinity.cmds -CPU 2 -v
-shuffle died with ret 256 at ../../Trinity line 2589.
main::process_cmd("/usr/bin/ParaFly -c recursive_trinity.cmds -CPU 2 -v
-shuffle ") called at ../../Trinity line 3226
main::run_partitioned_cmds("recursive_trinity.cmds") called at
../../Trinity line 2247
main::run_recursive_trinity("/tmp/autopkgtest-lxc.v050vbja/downtmp/autopkgtest_tmp/trinity"...)
called at ../../Trinity line 2009
main::run_chrysalis("/tmp/autopkgtest-lxc.v050vbja/downtmp/autopkgtest_tmp/trinity"...,
"/tmp/autopkgtest-lxc.v050vbja/downtmp/autopkgtest_tmp/trinity"..., 200, 500,
"RF", "/tmp/autopkgtest-lxc.v050vbja/downtmp/autopkgtest_tmp/trinity"...,
"/tmp/autopkgtest-lxc.v050vbja/downtmp/autopkgtest_tmp/trinity"...) called at
../../Trinity line 1672
main::run_Trinity() called at ../../Trinity line 1325
eval {...} called at ../../Trinity line 1324
Trinity run failed. Must investigate error above.
make[1]: *** [Makefile:7: test_all] Error 2
make[1]: Leaving directory
'/tmp/autopkgtest-lxc.v050vbja/downtmp/autopkgtest_tmp/trinityrnaseq/sample_data/test_Trinity_Assembly'
make: *** [Makefile:6: test_trin_assembly] Error 2
signature.asc
Description: OpenPGP digital signature
Processed: salmon breaks trinityrnaseq autopkgtest: /usr/bin/ParaFly -c recursive_trinity.cmds -CPU 2 -v -shuffle died with ret 256
Processing control commands: > found -1 salmon/1.2.1+ds1-1 Bug #959503 [src:salmon, src:trinityrnaseq] salmon breaks trinityrnaseq autopkgtest: /usr/bin/ParaFly -c recursive_trinity.cmds -CPU 2 -v -shuffle died with ret 256 Marked as found in versions salmon/1.2.1+ds1-1. > found -1 trinityrnaseq/2.6.6+dfsg-6 Bug #959503 [src:salmon, src:trinityrnaseq] salmon breaks trinityrnaseq autopkgtest: /usr/bin/ParaFly -c recursive_trinity.cmds -CPU 2 -v -shuffle died with ret 256 Marked as found in versions trinityrnaseq/2.6.6+dfsg-6. -- 959503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959503 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
