Bug#987113: ruby-librarian: autopkgtest failure: times out everywhere
Source: ruby-librarian Version: 0.6.4-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always timeout Dear maintainers, Your package has an autopkgtest, great. However it fails. Worse, since 0.6.4-2 it times out on the ci.d.n infrastructure after 2:47 hours. I copied some of the output at the bottom of this report. These kind of timeouts are bad for our infrastructure. I'll add your package to our ignore-list. Paul https://ci.debian.net/packages/r/ruby-librarian/testing/amd64/ https://ci.debian.net/packages/r/ruby-librarian/testing/arm64/ https://ci.debian.net/packages/r/ruby-librarian/testing/armhf/ https://ci.debian.net/packages/r/ruby-librarian/testing/i386/ https://ci.debian.net/packages/r/ruby-librarian/testing/ppc64el/ https://ci.debian.net/packages/r/ruby-librarian/testing/s390x/ https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-librarian/11723045/log.gz autopkgtest [01:43:42]: test gem2deb-test-runner: gem2deb-test-runner --autopkgtest --check-dependencies 2>&1 autopkgtest [01:43:42]: test gem2deb-test-runner: [--- ┌──┐ │ Checking Rubygems dependency resolution on ruby2.7 │ └──┘ GEM_PATH= ruby2.7 -e gem\ \"librarianp\" ┌──┐ │ Run tests for ruby2.7 from debian/ruby-tests.rake │ └──┘ mv lib .gem2deb.lib mv Gemfile.lock .gem2deb.Gemfile.lock RUBYLIB=. GEM_PATH= ruby2.7 -S rake -f debian/ruby-tests.rake /usr/bin/ruby2.7 -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec --pattern ./spec/\*\*/\*_spec.rb --format documentation Librarian::Mock::Cli version autopkgtest [04:30:22]: ERROR: timed out on command "su -s /bin/bash debci -c set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 || true; . ~/.profile >/dev/null 2>&1 || true; buildtree="/tmp/autopkgtest-lxc.4s6pt3u1/downtmp/build.PF3/src"; mkdir -p -m 1777 -- "/tmp/autopkgtest-lxc.4s6pt3u1/downtmp/gem2deb-test-runner-artifacts"; export AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.4s6pt3u1/downtmp/gem2deb-test-runner-artifacts"; export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755 "/tmp/autopkgtest-lxc.4s6pt3u1/downtmp/autopkgtest_tmp"; export AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.4s6pt3u1/downtmp/autopkgtest_tmp"; export ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive; export LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=48; unset LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT LC_IDENTIFICATION LC_ALL;rm -f /tmp/autopkgtest_script_pid; set -C; echo $$ > /tmp/autopkgtest_script_pid; set +C; trap "rm -f /tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd "$buildtree"; touch /tmp/autopkgtest-lxc.4s6pt3u1/downtmp/gem2deb-test-runner-stdout /tmp/autopkgtest-lxc.4s6pt3u1/downtmp/gem2deb-test-runner-stderr; bash -ec 'gem2deb-test-runner --autopkgtest --check-dependencies 2>&1' 2> >(tee -a /tmp/autopkgtest-lxc.4s6pt3u1/downtmp/gem2deb-test-runner-stderr >&2) > >(tee -a /tmp/autopkgtest-lxc.4s6pt3u1/downtmp/gem2deb-test-runner-stdout);" (kind: test) autopkgtest [04:30:22]: test gem2deb-test-runner: ---] OpenPGP_signature Description: OpenPGP digital signature
Bug#986637: fixed in speedtest-cli 2.1.3-1
Hi, On Mon, 12 Apr 2021 13:08:04 + Debian FTP Masters wrote: >* Upgrade to debhelper-compat (=13) With this reverted [1], it can be unblocked. Paul [1] https://release.debian.org/bullseye/FAQ.html section "I bumped the debhelper compat level, why is it rejected?" OpenPGP_signature Description: OpenPGP digital signature
Bug#950761: marked as done (ipmitool: CVE-2020-5208)
Your message dated Sat, 17 Apr 2021 19:17:08 + with message-id and subject line Bug#950761: fixed in ipmitool 1.8.18-6+deb10u1 has caused the Debian Bug report #950761, regarding ipmitool: CVE-2020-5208 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.) -- 950761: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950761 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ipmitool Version: 1.8.18-8 Severity: important Tags: security upstream Control: found -1 1.8.18-6 Control: found -1 1.8.18-3 Hi, The following vulnerability was published for ipmitool. CVE-2020-5208[0]: | It's been found that multiple functions in ipmitool before 1.8.19 | neglect proper checking of the data received from a remote LAN party, | which may lead to buffer overflows and potentially to remote code | execution on the ipmitool side. This is especially dangerous if | ipmitool is run as a privileged user. This problem is fixed in version | 1.8.19. 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-5208 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-5208 [1] https://github.com/ipmitool/ipmitool/security/advisories/GHSA-g659-9qxw-p7cp [2] https://github.com/ipmitool/ipmitool/commit/e824c23316ae50beb7f7488f2055ac65e8b341f2 Regards, Salvatore --- End Message --- --- Begin Message --- Source: ipmitool Source-Version: 1.8.18-6+deb10u1 Done: Thomas Goirand We believe that the bug you reported is fixed in the latest version of ipmitool, 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 950...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated ipmitool 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, 19 Feb 2021 11:30:06 +0100 Source: ipmitool Architecture: source Version: 1.8.18-6+deb10u1 Distribution: buster Urgency: medium Maintainer: Jörg Frings-Fürst Changed-By: Thomas Goirand Closes: 950761 Changes: ipmitool (1.8.18-6+deb10u1) buster; urgency=medium . * Non-maintainer upload. * CVE-2020-5208: buffer overflows and potentially to remote code execution. Applied upstream patches: - CVE-2020-5208_1_Fix_buffer_overflow_vulnerabilities.patch - CVE-2020-5208_2-fru-Fix-buffer-overflow-in-ipmi_spd_print_fru.patch - CVE-2020-5208_3-session-Fix-buffer-overflow-in-ipmi_get_session_info.patch - CVE-2020-5208_4-channel-Fix-buffer-overflow.patch - CVE-2020-5208_5_lanp-Fix-buffer-overflows-in-get_lan_param_select.patch - CVE-2020-5208_6-fru-sdr-Fix-id_string-buffer-overflows.patch (Closes: #950761). Checksums-Sha1: 1e03a023cd27c1c0ae3d7e9538a1c2ca03d0a769 1930 ipmitool_1.8.18-6+deb10u1.dsc 4268254534c9cb0abfa5a25164931b74ff989eb7 25288 ipmitool_1.8.18-6+deb10u1.debian.tar.xz be8c255c850a896e7ad366393dbd9a19529e7761 6085 ipmitool_1.8.18-6+deb10u1_amd64.buildinfo Checksums-Sha256: b068185100ced6e7e06c2fdb674edbdbf71eec64367d9c9fb84798b45dcfc58b 1930 ipmitool_1.8.18-6+deb10u1.dsc ce84ca43243974f8a98127f3ba094989e8a945ba3b00ae815b8433c55848b92b 25288 ipmitool_1.8.18-6+deb10u1.debian.tar.xz 9fc8577b40ce23ef4e1c8d96ae461664f71b1a85bc21fcf1007353f9d53c12f7 6085 ipmitool_1.8.18-6+deb10u1_amd64.buildinfo Files: fa99fdd82a1d37d1c65cc6b7fb1db9b7 1930 utils optional ipmitool_1.8.18-6+deb10u1.dsc 44b889cde529d8550e2d0642cf2529a9 25288 utils optional ipmitool_1.8.18-6+deb10u1.debian.tar.xz fc636d477e8d16be2243e817b8800e29 6085 utils optional ipmitool_1.8.18-6+deb10u1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmBfzqcACgkQ1BatFaxr Q/69pw/8D26WGi/NM3QORYlO9OUZfm+gUHSDVV+eh8/HtrAz/JHcEP/onJhzZmBr D15TvY+FUM4VXm3VQ58UIkKl0Ktsg6IlQJ7Q21dxkpThdX+PVJoqmShAcr4PoE2n FMaw+3DYB+QPFCzfOFHKmvj1P+2h3DiIXeLcZ+ieaVjrp3z9FzNHKvPoHw3c3l3e EPMjOxFfmFgG6WV40/uhp0EmrVi8VvcI0wUR/p4mbEDztZgttShOW9/S+04Zzu9O 3pfBH6NgOlsrOjslo+PlvcLFeoyLes4arRcmqew82uwo0ZdRLXXZ/Lgs1yAI3hb1 z40vRZoJJJ8ZfUC7+2DS8h5XyLJtmTpclERp1a3Zr6jK/4+y09dYY/3zoQnWWk
Processed: tagging 986814
Processing commands for cont...@bugs.debian.org:
> tags 986814 + unreproducible
Bug #986814 {Done: Lucas Nussbaum } [cloud.debian.org] Latest
vagrant Buster libvirt image not found
Added tag(s) unreproducible.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
986814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986814
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#986814: Latest vagrant Buster libvirt image not found
Le 12/04/2021 à 13:14, Christopher Huhn a écrit : > Package: cloud.debian.org > Severity: serious > > The latest Buster libvirt image for vagrant gives me a 404, `vagrant box > update` fails. > > λ > curl > https://app.vagrantup.com/debian/boxes/buster64/versions/10.20210409.1/providers/libvirt.box Hi Thanks for your interest for the Debian Vagrant boxes. when I'm doing vagrant box update the box is downloaded from https://vagrantcloud.com/debian/boxes/buster64/versions/10.20210409./providers/libvirt.box and is properly found vagrant box update ==> default: Checking for updates to 'debian/buster64' default: Latest installed version: 10.4.0 default: Version constraints: default: Provider: libvirt ==> default: Updating 'debian/buster64' with provider 'libvirt' from version ==> default: '10.4.0' to '10.20210409.1'... ==> default: Loading metadata for box 'https://vagrantcloud.com/debian/buster64' ==> default: Adding box 'debian/buster64' (v10.20210409.1) for provider: libvirt default: Downloading: https://vagrantcloud.com/debian/boxes/buster64/versions/10.20210409.1/providers/libvirt.box Download redirected to host: vagrantcloud-files-production.s3-accelerate.amazonaws.com ==> default: Successfully added box 'debian/buster64' (v10.20210409.1) for 'libvirt'! when creating a fresh environment with export VAGRANT_DEFAULT_PROVIDER=libvirt vagrant init debian/buster64` vagrant up is the box properly downloaded on your side ? -- You know an upstream is nice when they even accept m68k patches. - John Paul Adrian Glaubitz, Debian OpenJDK maintainer
Processed: bug 987095 is forwarded to https://github.com/graphviz-perl/Graph/issues/20, tagging 987095
Processing commands for cont...@bugs.debian.org: > forwarded 987095 https://github.com/graphviz-perl/Graph/issues/20 Bug #987095 [libgraph-perl] transitive_closure corrupted results, after vertex deleted Set Bug forwarded-to-address to 'https://github.com/graphviz-perl/Graph/issues/20'. > tags 987095 + upstream Bug #987095 [libgraph-perl] transitive_closure corrupted results, after vertex deleted Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 987095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987095 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#986806: CVE-2021-28965
On Sat, Apr 17, 2021 at 10:16 pm, Utkarsh Gupta wrote: Makes sense. Probably the time to RM ruby-rexml from the archive is *now*? Requested removal from archive in #987101
Processed: RM: ruby-rexml -- ROM; duplicate package, included in libruby2.7
Processing control commands:
> block 986806 by -1
Bug #986806 {Done: Pirate Praveen } [ruby-rexml]
CVE-2021-28965
986806 was not blocked by any bugs.
986806 was not blocking any bugs.
Added blocking bug(s) of 986806: 987101
--
986806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986806
987101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987101
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#986806: CVE-2021-28965
Hi Praveen, On Fri, Apr 16, 2021 at 3:24 PM Pirate Praveen wrote: > I think the separate package was introduced by mistake without seeing > the copy embedded in ruby. I think the right way is to fix this in ruby > and remove this separate package. But I'd like someone from ruby team > to confirm this. Makes sense. Probably the time to RM ruby-rexml from the archive is *now*? As for fixing this in src:ruby2.7, see #986742. TL;DR: ruby2.7 2.7.3-1 was uploaded to fix this earlier today. - u
Bug#986701: marked as done (mosquitto: CVE-2021-28166)
Your message dated Sat, 17 Apr 2021 16:27:13 + with message-id and subject line Bug#986701: fixed in mosquitto 2.0.10-1 has caused the Debian Bug report #986701, regarding mosquitto: CVE-2021-28166 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.) -- 986701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986701 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mosquitto Version: 2.0.9-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for mosquitto. CVE-2021-28166[0]: | In Eclipse Mosquitto version 2.0.0 to 2.0.9, if an authenticated | client that had connected with MQTT v5 sent a crafted CONNACK message | to the broker, a NULL pointer dereference would occur. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2021-28166 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-28166 [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=572608 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: mosquitto Source-Version: 2.0.10-1 Done: Roger A. Light We believe that the bug you reported is fixed in the latest version of mosquitto, 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 986...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Roger A. Light (supplier of updated mosquitto package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 10 Apr 2021 00:41:35 +0100 Source: mosquitto Architecture: source Version: 2.0.10-1 Distribution: unstable Urgency: high Maintainer: Roger A. Light Changed-By: Roger A. Light Closes: 986701 Changes: mosquitto (2.0.10-1) unstable; urgency=high . * SECURITY UPDATE: In Eclipse Mosquitto version 2.0.0 to 2.0.9, if an authenticated client that had connected with MQTT v5 sent a crafted CONNACK message to the broker, a NULL pointer dereference would occur. (Closes: #986701) - CVE-2021-28166 * New upstream release. Checksums-Sha1: d9b54f2b9a5682260f05caa254adfc464dd14f34 2440 mosquitto_2.0.10-1.dsc 7a7fd91f1619c194e0f9b2e3db0f4eadb9e9da75 759106 mosquitto_2.0.10.orig.tar.gz 7eb4b1e4bc89df5621331dab8f1529e69c13c19b 19812 mosquitto_2.0.10-1.debian.tar.xz d2479ae8a5f4de9f394a9c3c8e6ed174a52291bf 9380 mosquitto_2.0.10-1_source.buildinfo Checksums-Sha256: 8ed25a9d446c20f30364199aee2fc7933cf63718428585a777ca9fd71dfbc890 2440 mosquitto_2.0.10-1.dsc 0188f7b21b91d6d80e992b8d6116ba851468b3bd154030e8a003ed28fb6f4a44 759106 mosquitto_2.0.10.orig.tar.gz a1137210d94c1a450afa0ad67645a8883a9a84299f80eb4fc80cd09d3cbd3bd2 19812 mosquitto_2.0.10-1.debian.tar.xz 220ad5a610414a705c500c1e11bf76ebb6e6c1e2bc1f6e8cf010e4ccd8841a1b 9380 mosquitto_2.0.10-1_source.buildinfo Files: 15587b9281cc35c213b2afa88eed0a74 2440 net optional mosquitto_2.0.10-1.dsc 3d1c327d8c5881f56983bee1e3c8f068 759106 net optional mosquitto_2.0.10.orig.tar.gz fc517159caf4195d43fad415e3435252 19812 net optional mosquitto_2.0.10-1.debian.tar.xz a043f7bf5908062062906e527c5ce5ce 9380 net optional mosquitto_2.0.10-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAmB7B8IACgkQ808JdE6f XdkNjw/+M5x1saOdh0XVDJe8ZYrrHKrgwfqX7saPpgPUTVc+MghCOQu781KCkVPi xUxV9YI//VW3iJDA3Of0mhZDH1wB0sxkK9nFHqjv0yS1vKsHZ1pdFzrRoC1kIFZc brXLDaIsCUSHJSfUOfTr1LafvCSTghsykErrwee3yS5H5y1fSvzvmf8z8qfNpUx0 DUpaveOqq0yGYr7NlyHBv56ZS5fzLG0i79gj27ynCY5AuJj6EMfkw+Xey7BBNnFc hh3RKlbhnV8Mk7nNgTcpsKXBfvWIgyinJMZiuqDbGU44oVfi7GQUcmn4LX9HbYpG o+E/iGCWfSKO2GFyeoGF9ecJVtP1/nFTmhG/mHox+0o60ZGvKsLx/tm7xOm8O1Su +4BY98AY3kGrzmFAr37o8z5Esxwyxc859Na2aUvNeXRwK/coPNfoNEc2/l7MAfK1 qFoH5m+/Keyx+zte8ac40oVKvwEY4B+cx1iah5kuOF/r87Cmst51GdUmlSbIqmya XDxihoMARtkK6n7aTn0Nbyo5j1m6u/9pms86yErPX7mcxbZu4uxZlLtBpaCiZ2bf cCikzTYEqRP8hSLgCJeh0+MaO9LDXhaz6/mW80Qda4Ww28Vil07kWfvaXvu5fO6+ kfBwOtgb9jflA9nXYNOj4oerHCrcRbmyZ2YJWEQQy9D
Bug#986518: marked as done (starjava-topcat: FTBFS: [javadoc] javadoc: error - invalid flag: -Xdoclint:none)
Your message dated Sat, 17 Apr 2021 14:18:05 + with message-id and subject line Bug#986518: fixed in ant 1.10.9-4 has caused the Debian Bug report #986518, regarding starjava-topcat: FTBFS: [javadoc] javadoc: error - invalid flag: -Xdoclint:none 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.) -- 986518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986518 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: starjava-topcat Version: 4.8-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210406 ftbfs-bullseye Hi, During a rebuild of all packages in bullseye, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > ant jars > Buildfile: /<>/build.xml > > prepare: >[tstamp] Honouring environment variable SOURCE_DATE_EPOCH which has been > set to 1612474211 > > check_packages: > > build: > [mkdir] Created dir: /<>/build/classes > [javac] Compiling 419 source files to /<>/build/classes > [javac] > /<>/src/main/uk/ac/starlink/topcat/TopcatModel.java:193: > warning: [deprecation] Long(long) in Long has been deprecated > [javac] subsetCounts_.put( RowSubset.NONE, new Long( 0 ) ); > [javac]^ > [javac] > /<>/src/main/uk/ac/starlink/topcat/TopcatModel.java:194: > warning: [deprecation] Long(long) in Long has been deprecated > [javac] subsetCounts_.put( RowSubset.ALL, new Long( > startab.getRowCount() ) ); > [javac] ^ > [javac] > /<>/src/main/uk/ac/starlink/topcat/TopcatModel.java:516: > warning: [deprecation] Long(long) in Long has been deprecated > [javac] fireModelChanged( TopcatEvent.ROW, new Long( lrow ) ); > [javac]^ > [javac] > /<>/src/main/uk/ac/starlink/topcat/TopcatModel.java:1266: > warning: [deprecation] Long(long) in Long has been deprecated > [javac] subsetCounts_.put( rset, new Long( > viewModel_.getRowCount() ) ); > [javac] ^ > [javac] > /<>/src/main/uk/ac/starlink/topcat/ViewerTableModel.java:129: > warning: [deprecation] Long(long) in Long has been deprecated > [javac] return new Long( ++lx_ ); > [javac]^ > [javac] > /<>/src/main/uk/ac/starlink/topcat/ViewerTableModel.java:144: > warning: [deprecation] Long(long) in Long has been deprecated > [javac] return new Long( rowMap[ ++kx_ ] ); > [javac]^ > [javac] > /<>/src/main/uk/ac/starlink/topcat/activate/ActivationWindow.java:661: > warning: [deprecation] Long(long) in Long has been deprecated > [javac] tcModel_.fireModelChanged( TopcatEvent.ROW, new Long( > lrow ) ); > [javac] ^ > [javac] > /<>/src/main/uk/ac/starlink/topcat/activate/ActivationWindow.java:1406: > warning: [deprecation] newInstance() in Class has been deprecated > [javac] (ActivationType) Class.forName( clazzName > ).newInstance(); > [javac]^ > [javac] where T is a type-variable: > [javac] T extends Object declared in class Class > [javac] > /<>/src/main/uk/ac/starlink/topcat/ControlWindow.java:534: > warning: [deprecation] ALT_MASK in InputEvent has been deprecated > [javac] > InputEvent.ALT_MASK ), > [javac] ^ > [javac] > /<>/src/main/uk/ac/starlink/topcat/ControlWindow.java:539: > warning: [deprecation] ALT_MASK in InputEvent has been deprecated > [javac] > InputEvent.ALT_MASK ), > [javac] ^ > [javac] > /<>/src/main/uk/ac/starlink/topcat/ControlWindow.java:2001: > warning: [deprecation] newInstance() in Class has been deprecated > [javac] tld0 = tldClazz.newInstance(); > [javac]^ > [javac] where T is a type-variable: > [javac] T extends Object declared in class Class > [javac] > /<>/src/main/uk/ac/starlink/topcat/TopcatJELRowReader.java:153: > warning: [deprecation] Short(short) in Short has been deprecated > [javac] return new Short( isub ); > [jav
Bug#986521: marked as done (starjava-ttools: FTBFS: [javadoc] javadoc: error - invalid flag: -Xdoclint:none)
Your message dated Sat, 17 Apr 2021 14:18:05 +
with message-id
and subject line Bug#986518: fixed in ant 1.10.9-4
has caused the Debian Bug report #986518,
regarding starjava-ttools: FTBFS: [javadoc] javadoc: error - invalid flag:
-Xdoclint:none
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.)
--
986518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986518
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: starjava-ttools
Version: 3.4-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye
Hi,
During a rebuild of all packages in bullseye, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> ant jars
> Buildfile: /<>/build.xml
>
> prepare:
>[tstamp] Honouring environment variable SOURCE_DATE_EPOCH which has been
> set to 1612473971
>
> check_packages:
>
> build:
> [mkdir] Created dir: /<>/build/classes
> [javac] Compiling 916 source files to /<>/build/classes
> [javac]
> /<>/src/main/uk/ac/starlink/ttools/plot2/paper/PaperTypeSelector.java:132:
> warning: [deprecation] Integer(int) in Integer has been deprecated
> [javac] rgbSet.add( new Integer( color.getRGB() & 0x00ff
> ) );
> [javac] ^
> [javac]
> /<>/src/main/uk/ac/starlink/ttools/plot2/layer/ShapeMode.java:317:
> warning: [deprecation] Double(double) in Double has been deprecated
> [javac] report.put( key, new Double( pixSize ) );
> [javac] ^
> [javac]
> /<>/src/main/uk/ac/starlink/ttools/plot2/geom/CubeSurface.java:499:
> warning: [deprecation] Double(double) in Double has been deprecated
> [javac] config.put( CubeSurfaceFactory.ZOOM_KEY, new Double(
> zoom_ ) );
> [javac] ^
> [javac]
> /<>/src/main/uk/ac/starlink/ttools/plot2/geom/CubeSurface.java:500:
> warning: [deprecation] Double(double) in Double has been deprecated
> [javac] config.put( CubeSurfaceFactory.XOFF_KEY, new Double(
> xoff_ ) );
> [javac] ^
> [javac]
> /<>/src/main/uk/ac/starlink/ttools/plot2/geom/CubeSurface.java:501:
> warning: [deprecation] Double(double) in Double has been deprecated
> [javac] config.put( CubeSurfaceFactory.YOFF_KEY, new Double(
> yoff_ ) );
> [javac] ^
> [javac]
> /<>/src/main/uk/ac/starlink/ttools/build/BashComplete.java:31:
> warning: [rawtypes] found raw type: Parameter
> [javac] Parameter[] params = task.getParameters();
> [javac] ^
> [javac] missing type arguments for generic class Parameter
> [javac] where T is a type-variable:
> [javac] T extends Object declared in class Parameter
> [javac]
> /<>/src/main/uk/ac/starlink/ttools/build/BashComplete.java:33:
> warning: [rawtypes] found raw type: List
> [javac] List outputFormats = env.getTableOutput().getKnownFormats();
> [javac] ^
> [javac] missing type arguments for generic class List
> [javac] where E is a type-variable:
> [javac] E extends Object declared in interface List
> [javac]
> /<>/src/main/uk/ac/starlink/ttools/build/BashComplete.java:34:
> warning: [rawtypes] found raw type: List
> [javac] List inputFormats = env.getTableFactory().getKnownFormats();
> [javac] ^
> [javac] missing type arguments for generic class List
> [javac] where E is a type-variable:
> [javac] E extends Object declared in interface List
> [javac]
> /<>/src/main/uk/ac/starlink/ttools/build/BashComplete.java:35:
> warning: [rawtypes] found raw type: Collection
> [javac] Collection charsets = Charset.availableCharsets().keySet();
> [javac] ^
> [javac] missing type arguments for generic class Collection
> [javac] where E is a type-variable:
> [javac] E extends Object declared in interface Collection
> [javac]
> /<>/src/main/uk/ac/starlink/ttools/build/BashComplete.java:105:
> warning: [rawtypes] found raw type: Collection
> [javac] public static String completionCase(String name, Collection
> pattern) {
> [javac] ^
> [javac] missing type arguments for generic class Collection
> [javac] where E is a type-variable:
> [javac] E extends Object declared in interface Collection
> [javac]
> /<>/src/main/uk/ac/starli
Bug#978674: python3-build: Fails to work unless pip is installed
On Fri, Mar 26, 2021 at 07:32:47PM -0400, Sergio Durigan Junior wrote: > Control: severity -1 serious > Control: tags -1 + help > > On Sunday, January 17 2021, Martina Ferrari wrote: > > > On 17/01/2021 01:06, Sergio Durigan Junior wrote: > > > >> Thanks for the bug report, Martina. > >> Yeah, this is strange. I don't think it should require pip, and > >> after > >> installing python3-pip here and re-running /usr/bin/pyproject-build I > >> noticed that it (obviously) invokes pip and downloads several things, > >> which IMO is a no-no. > > > > Yeah, that's bad. > > > >> The reason I packaged python3-build is because check-manifest started > >> depending on it. I'm thinking about removing the > >> /usr/bin/pyproject-build program and just shipping the library. Do you > >> think it could work? (Sorry, I'm not a PEP-517 expert). > > > > Honestly, I don't know much about it either.. I'd suggest discussing > > it with the python-modules team? I guess somebody there would know > > what to do. > > I'm marking this bug as serious because I don't think we want a clearly > broken package in bullseye. > > I don't have much time to work on it right now, so I'm tagging this bug > as "help" and would appreciate if someone could take another look and > check if it's possible to fix it, or if it even makes sense having this > package in Debian, given that python-build seems to depend on > downloading things via pip and all... > > The only reverse-dependency of python3-build is check-manifest, which is > another package I've uploaded, and nothing really depends on it, so I'm > fine if nobody steps up to fix this bug and both packages are excluded > from bullseye. Hm. I may be a bit off-base here, but I needed to look at the "build" tool a while ago as part of $REAL_JOB, and, hm... ...is this not how python3-build is supposed to operate? From what I know (which may not be completely correct), it has two basic operating modes: - isolated (the default one): create a virtual environment, make sure that the specified build system's dependencies are satisfied in there, then run the specified build system's PEP 517 hook for creating wheel packages - non-isolated (the -n command-line option): do not create a virtual environment, assume that the build system itself and all its dependencies are already installed in the environment of the Python interpreter that "build" is being run with, so just invoke the build system's PEP 517 hook for creating wheel packages So if one invokes `python3 -m build --wheel` (which is the default target if none are specified), "build" will create a virtual environment, then look at the pyproject.toml file and figure out what packages need to be installed within the newly-created environment. After that, it will use pip to install them. The way to avoid that is to use build's non-isolated mode by specifying the -n option on the command line. Of course, this brings along all the perils of a non-isolated build, e.g. not noticing forgotten build dependencies that are accidentally present in the current environment. So... I think that this is the way the "build" tool is supposed to operate. If somebody needs to use it with assuredly nothing downloaded from external sites, e.g. during a Debian package build, then I think a non-isolated build is the way to go. I hope this was useful in some way - I thought I'd make things a bit clearer for people who are not familiar with the tool itself. If somebody still decides that the "build" tool's default mode of operation makes it unsuitable for Debian, well, I guess that would be a valid viewpoint, but IMHO that would also apply to many, many other Debian packages related to various language ecosystems that have "download stuff from a central repository" as their main purpose :) Thanks, everyone, for your work on Debian! G'luck, Peter -- Peter Pentchev r...@ringlet.net r...@debian.org p...@storpool.com PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 signature.asc Description: PGP signature
Processed: Bug#986518 marked as pending in ant
Processing control commands: > tag -1 pending Bug #986518 [ant] starjava-topcat: FTBFS: [javadoc] javadoc: error - invalid flag: -Xdoclint:none Bug #986521 [ant] starjava-ttools: FTBFS: [javadoc] javadoc: error - invalid flag: -Xdoclint:none Added tag(s) pending. Added tag(s) pending. -- 986518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986518 986521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986521 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#986518: marked as pending in ant
Control: tag -1 pending Hello, Bug #986518 in ant 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/java-team/ant/-/commit/2bb010ec62b3f93a093fad405db13fa60c9aee22 Disable doclint only with the default doclet (Closes: #986518) (this message was generated automatically) -- Greetings https://bugs.debian.org/986518
Bug#986806: CVE-2021-28965
On Fri, Apr 16, 2021 at 03:22:24PM +0530, Pirate Praveen wrote: > On Mon, 12 Apr 2021 12:05:29 +0200 Moritz Muehlenhoff > wrote: > > https://www.ruby-lang.org/en/news/2021/04/05/xml-round-trip-vulnerability-in-rexml-cve-2021-28965/ > > > > Why is there a separate package duplicating rexml from src:ruby2.7 in > bullseye? > > I think the separate package was introduced by mistake without seeing the > copy embedded in ruby. I think the right way is to fix this in ruby and > remove this separate package. But I'd like someone from ruby team to confirm > this. agreed. signature.asc Description: PGP signature
Bug#987095: transitive_closure corrupted results, after vertex deleted
I've created a bug upstream: https://github.com/graphviz-perl/Graph/issues/20 All the best
Bug#987095: transitive_closure corrupted results, after vertex deleted
Hi On Sat, 17 Apr 2021 12:59:40 +0100 Ian Jackson <> The correct output, as seen on buster: > > input: A-NOTA,B-A,B-NOTA > output: A-A,A-NOTA,B-A,B-B,B-NOTA,NOTA-NOTA > output: A-NOTA,B-A,B-NOTA,NOTA-NOTA I've bisected this regression to: 3ded9c7a25bf190fda5add1a13ed4f9b54082db7 is the first bad commit commit 3ded9c7a25bf190fda5add1a13ed4f9b54082db7 Author: Ed J Date: Mon Dec 14 13:34:32 2020 + all AdjacencyMap store _i as array-refs lib/Graph/AdjacencyMap.pm| 6 +- lib/Graph/AdjacencyMap/Heavy.pm | 10 -- lib/Graph/AdjacencyMap/Light.pm | 9 ++--- lib/Graph/AdjacencyMap/Vertex.pm | 8 ++-- lib/Graph/AdjacencyMatrix.pm | 17 ++-- lib/Graph/BitMatrix.pm | 42 + +-- 6 files changed, 34 insertions(+), 58 deletions(-) All the best
Bug#987095: transitive_closure corrupted results, after vertex deleted
Package: libgraph-perl
Version: 1:0.9716-1
Severity: grave
The attached script, which tests the transitive closure function,
prints this output on testing:
input: A-NOTA,B-A,B-NOTA
Use of uninitialized value $_ in exists at /usr/share/perl5/Graph.pm line 362.
Use of uninitialized value $_ in exists at /usr/share/perl5/Graph.pm line 362.
output: A-A,A-B,B-B,NOTA-NOTA
output: A-B,NOTA-NOTA
The correct output, as seen on buster:
input: A-NOTA,B-A,B-NOTA
output: A-A,A-NOTA,B-A,B-B,B-NOTA,NOTA-NOTA
output: A-NOTA,B-A,B-NOTA,NOTA-NOTA
Empirically, the delete_vertex call is necessary for the repro.
I think this is certainly release critical. I chose "grave" rather
than "serious" since this can produce corrupted output in data
processing situations, where the corrupted output might not be
detected.
In my Debian tally sheet processing program
https://www.chiark.greenend.org.uk/ucgi/~ian/git?p=appendix-a6.git
(`compute`, there), this can produce totally wrong answers for the
winner of votes.
Ian.
#!/usr/bin/perl -w
use strict;
use Graph::Directed;
my $input = Graph::Directed->new;
foreach my $e (qw(
A-C
A-NOTA
B-A
B-C
B-NOTA
)) {
my ($x,$y) = split /-/, $e;
$input->add_edge($x,$y);
}
$input->delete_vertex('C');
print "input: $input\n";
my $output = $input->transitive_closure();
print "output: $output\n";
foreach my $x (qw(A B C N)) {
$output->delete_edge($x,$x);
}
print "output: $output\n";
--
Ian JacksonThese opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
Bug#987065: wordpress: CVE-2021-29450: Authenticated disclosure of password-protected posts and pages
Hi, On Sat, Apr 17, 2021 at 09:22:09PM +1000, Craig Small wrote: > Yeah I realised there wasn't PHP 8 in Debian anywhere yet but referencing > it is worthwhile otherwise months later someone might ask me about it and > I'll go, hmm I think we fixed that. Ack. > Buster will have a debdiff to review very soon. Bullseye I have asked for > the version in Sid to be unblocked in #987084 which I think is the best > outcome for future maintenance. Thanks, best just to the team alias for the security-team so we can distribute review workload. Regards, Salvatore
Processed: unarchiving 980428, found 980428 in 1:1.10.6+submodules+notgz-1.1+deb10u1 ...
Processing commands for cont...@bugs.debian.org:
> unarchive 980428
Bug #980428 {Done: Ondřej Surý } [php-pear] Disallow
symlinks to out-of-path filenames (CVE-2020-36193)
Unarchived Bug 980428
> found 980428 1:1.10.6+submodules+notgz-1.1+deb10u1
Bug #980428 {Done: Ondřej Surý } [php-pear] Disallow
symlinks to out-of-path filenames (CVE-2020-36193)
Marked as found in versions php-pear/1:1.10.6+submodules+notgz-1.1+deb10u1.
> found 980428 1:1.10.6+submodules+notgz-1
Bug #980428 {Done: Ondřej Surý } [php-pear] Disallow
symlinks to out-of-path filenames (CVE-2020-36193)
Marked as found in versions php-pear/1:1.10.6+submodules+notgz-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
980428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980428
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#987065: wordpress: CVE-2021-29450: Authenticated disclosure of password-protected posts and pages
Yeah I realised there wasn't PHP 8 in Debian anywhere yet but referencing it is worthwhile otherwise months later someone might ask me about it and I'll go, hmm I think we fixed that. Buster will have a debdiff to review very soon. Bullseye I have asked for the version in Sid to be unblocked in #987084 which I think is the best outcome for future maintenance. - Craig On Sat, 17 Apr 2021 at 16:37, Salvatore Bonaccorso wrote: > Hi Craig, > > On Sat, Apr 17, 2021 at 08:32:35AM +1000, Craig Small wrote: > > Should CVE-2021-29447 [1] be also listed against this bug? I'll be > putting > > it in the changelog. > > I choosed to explicitly cover only CVE-2021-29450 with this bug > because CVE-2021-29447 while fixed as well with 5.7.1, is only a > problem with PHP8, which is not the default version for bullseye/sid. > > But clearly if you fix the issues by updating to 5.7.1 then by all > means yes list as well CVE-2021-29447 in the changelog entry. > > Thanks for your work! > > Salvatore >
Bug#986854: marked as done (elpa-helm: does not ship helm-global-bindings.el)
Your message dated Sat, 17 Apr 2021 10:48:21 + with message-id and subject line Bug#986854: fixed in helm 3.7.0-2 has caused the Debian Bug report #986854, regarding elpa-helm: does not ship helm-global-bindings.el 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.) -- 986854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986854 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: elpa-helm Version: 3.7.0-1 Severity: grave Justification: renders package unusable Dear Maintainer, The elpa-helm package does not ship the file helm-global-bindings.el, which is essential for its function: it contains all global keybindings for helm. These keybindings were previously in helm-config.el. As a result, upon upgrading to bullseye, helm stops working. Please include the file helm-global-bindings.el (which is present in the source) in either elpa-helm or elpa-helm-core binary package. Best wishes, Todor -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-5-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages elpa-helm depends on: ii dh-elpa-helper 2.0.8 ii elpa-async 1.9.4-2 ii elpa-helm-core 3.7.0-1 ii elpa-popup 0.5.8-1 ii emacsen-common 3.0.4 Versions of packages elpa-helm recommends: ii emacs 1:27.1+1-3.1 ii emacs-gtk [emacs] 1:27.1+1-3.1 Versions of packages elpa-helm suggests: pn elpa-helm-org --- End Message --- --- Begin Message --- Source: helm Source-Version: 3.7.0-2 Done: David Bremner We believe that the bug you reported is fixed in the latest version of helm, 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 986...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Bremner (supplier of updated helm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 17 Apr 2021 07:31:15 -0300 Source: helm Architecture: source Version: 3.7.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Emacsen team Changed-By: David Bremner Closes: 986854 Changes: helm (3.7.0-2) unstable; urgency=medium . * Team upload * ship helm-global-bindings.el in elpa-helm (Closes: #986854). Checksums-Sha1: 3e598779f3e7c80cf515c4b6bd9ff690f9a4d61d 2058 helm_3.7.0-2.dsc f4b2f3b28a09b6a756c5decb6ea66a218bf9f399 6456 helm_3.7.0-2.debian.tar.xz Checksums-Sha256: 093a9caa3e51883d3736b60ab533c31eada3892fcce7ab3cd444ea360939ed75 2058 helm_3.7.0-2.dsc b3e6fb6604046102143c2f43bcb94f5540185cad1235ec087a274ce53144ec89 6456 helm_3.7.0-2.debian.tar.xz Files: de937b69911b21842b195c2f5aa2ed5a 2058 lisp optional helm_3.7.0-2.dsc f185f92491b876b05f22325454fae442 6456 lisp optional helm_3.7.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmB6uqgACgkQA0U5G1Wq FSEJHhAAq9xrTUp8eQ4AFB6d3jzbhGoSuZerYiHi94qqF9tG3sWMSd1tnkR94IK3 L9UNc7wK3VDYdzrzWrDG1yZE5mEfqKY7RSEi9M8KDDssxxkmnCewhcnGMophsOWc tuVGZ9sNg9cm1TkmqWAAQesebr9vJgwLx5SjkhVK+6hiR/YxZSTcURojXe2J59Jg cki+E/ANDW4UI0Wp7IaIzXJZovT0o3wUbFw0sC9ujeQG6p4w5TJ/SvMbWowh2aXL 7nNIpihqMRbleA7YD7XD2K3neR9KmgTd/d60CZrXRIy8rHKMM8ECvGOw3K1eW7oN wfIKPuBeGtnmGiHSitKNYbN5y2qk9cFh61/kRvdSCMyRLvJI3+z/TfSE00RYBNca 0Gmt8DLsf3eYoiwPbgfFRC6xKfy9xfcoYW+Njqb+n+PqRhZV0lxCZVon11nttedi uA/8bfjtMSnOzMGA/wNSM7clB5hgnCktMqu8WUOAdeC/yT1rNFO3yUsB2uO9q1gw gCYl94zGxKryEi4F2I03pkqdHg5ZRJQGDl+8eFidYuLvhNY2vIZZEx5pvHWGqXpw 8wx1rcxoL+k4jQQIHHcFO9rNeRgHkVUZdQy1Ta78teR6BW6EGjeQzdn7xbacun6Q AF0igqgPg/Nkl8+Z6z9Mw9HOqFiko12wSQaQ1hE3KczqFbilzO0= =hzpb -END PGP SIGNATURE End Message ---
Bug#985517: marked as done (lxpanel-dev: broken symlink: /usr/lib/x86_64-linux-gnu/lxpanel/liblxpanel.so -> liblxpanel.so.0.0.0)
Your message dated Sat, 17 Apr 2021 10:48:27 + with message-id and subject line Bug#985517: fixed in lxpanel 0.10.1-2 has caused the Debian Bug report #985517, regarding lxpanel-dev: broken symlink: /usr/lib/x86_64-linux-gnu/lxpanel/liblxpanel.so -> liblxpanel.so.0.0.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 985517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985517 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lxpanel-dev Version: 0.10.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 2m9.7s ERROR: FAIL: Broken symlinks: /usr/lib/x86_64-linux-gnu/lxpanel/liblxpanel.so -> liblxpanel.so.0.0.0 (lxpanel-dev:amd64) This looks like a missing dependency on lxpanel. cheers, Andreas lxpanel-dev_0.10.1-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: lxpanel Source-Version: 0.10.1-2 Done: Andriy Grytsenko We believe that the bug you reported is fixed in the latest version of lxpanel, 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 985...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andriy Grytsenko (supplier of updated lxpanel package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 17 Apr 2021 13:22:04 +0300 Source: lxpanel Architecture: source Version: 0.10.1-2 Distribution: unstable Urgency: medium Maintainer: Debian LXDE Maintainers Changed-By: Andriy Grytsenko Closes: 985517 Changes: lxpanel (0.10.1-2) unstable; urgency=medium . * Making lxpanel-dev package Multi-Arch: no (Closes: #985517). Checksums-Sha1: 5ad25c3ed0ffd78fcc0d274a3f7ed2113e778631 2305 lxpanel_0.10.1-2.dsc 9241bb2ae89308bf7eeda044d4fd58b4d4f6ef6b 14872 lxpanel_0.10.1-2.debian.tar.xz 79aa54b584e0babba7995da5d3b9758ec18fb09c 12692 lxpanel_0.10.1-2_amd64.buildinfo Checksums-Sha256: 53bc1f900f488387492fa790943cad72da3fc41120b94eab6acf0d676d981dc3 2305 lxpanel_0.10.1-2.dsc d508b2c92fc74bb89d21657f443229253840398042354bcaef3bf15a57566403 14872 lxpanel_0.10.1-2.debian.tar.xz 72d76a3dfbfb514a0994ef03cbe20961e91efc733f46b3ad2d064f9357be5808 12692 lxpanel_0.10.1-2_amd64.buildinfo Files: bfaeedf0ca1c8dbc8fd90d5678d12097 2305 x11 optional lxpanel_0.10.1-2.dsc 82e882a435d124438af3a32ecb313c6e 14872 x11 optional lxpanel_0.10.1-2.debian.tar.xz f1a88eddc4b47d1d1277671a54339bb8 12692 x11 optional lxpanel_0.10.1-2_amd64.buildinfo -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJgerl0AAoJEAV2MC/hidTSQ6wP/AphEd++GrwoQMSCS4PPE1C6 LH5QnY2Lfin0jY9CkDaXgvLRashZcBJ6MG/ynM2S/anUlfWIOAk9RVeVb3Bx51oU iQ10Y19PQCFvzFLQH4DVcj8OFCozGjCYG+crWJjjvbWEFvDS8Vo1uWK4rZoQNsPj J0OQd31eOWwfw7Y8hteMTVi/rGEZsmBGIpCQhOvL0DL1YZieUDBtHH5GfIvWnHNe 5nSmOU3lAxZy2b4ZBGVmbwUZKy15AdzQ11chhqdYFVbUrJdJ9K4/GEJxhhxaG17n +Mzs+npoXqaSpRxpzuv3v5fJ/i5BkR15hqw3JT4y7sKBH0uhgeP670nnNi5sp1uc kXhMF4aGoW16lfqlFJOzi4wGHdHBQmPzlB6wJSHRBUtssa7OSTe+EzLL/gvhR8Al dbRaDq98K5+SupjNvUM/CgP2FYCpAjW2XSiGtOOe6KZre6pCgDL05OK8wO2hSfHo vPUCzBj/Za34pa/wDhJdE+rgj1US8X5WpvHeRtj4hgpcaxnXTrrJlQwrF3ijUBdy LOccFNoiCm3ioGR10g799D09rtTopMMg9VOgMtWVJos32yaWaYaxaUiFaoXUfFx4 T0qJtGwUmvDQKtBW+Bt7rZiO/AiQkSBcZoYLOy8J7s+zrB/u4S/6FuJbiOEp/f1I /tSLZsR1G2KcGC69Mkju =OdpW -END PGP SIGNATURE End Message ---
Bug#986726: marked as done (boxer-data: autopkgtest regressionin testing)
Your message dated Sat, 17 Apr 2021 09:03:22 + with message-id and subject line Bug#986726: fixed in boxer-data 10.8.22 has caused the Debian Bug report #986726, regarding boxer-data: autopkgtest regressionin testing to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 986726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986726 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: boxer-data Version: 10.8.20 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: regression Hi Maintainer The autopkgtest of boxer-data fails in testing where it succeeded in the past [1]. The current failure seems to be due to the removal of citadel-mta from testing: E: Unable to locate package citadel-mta This regression also prevents boxer-data/10.8.21 from migrating to testing. Regards Graham [1] https://ci.debian.net/packages/b/boxer-data/testing/amd64/ --- End Message --- --- Begin Message --- Source: boxer-data Source-Version: 10.8.22 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of boxer-data, 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 986...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated boxer-data package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 17 Apr 2021 10:47:12 +0200 Source: boxer-data Architecture: source Version: 10.8.22 Distribution: unstable Urgency: medium Maintainer: Boxer developers Changed-By: Jonas Smedegaard Closes: 986726 Changes: boxer-data (10.8.22) unstable; urgency=medium . * fix class Service.mail.avoid: stop avoid citadel-mta unavailable since bullseye; closes: bug#986726, thanks to Graham Inggs Checksums-Sha1: 70fa5a0a7617f7713bd763173e1290bbfa22fbf0 1717 boxer-data_10.8.22.dsc f5b854d7b91157f822d2f15627f18bbeb8073db1 96540 boxer-data_10.8.22.tar.xz 927c1562d5d1c273947bf7a65982fba7c1557876 7862 boxer-data_10.8.22_amd64.buildinfo Checksums-Sha256: f1d4599f1dce0f501df2cd032fadb53aedba31230a6380ed55370d0a0c4f8f17 1717 boxer-data_10.8.22.dsc 0976795bb5d9eb320bc43896302d05d9411b6f747aa8954acfeb7f04305d7309 96540 boxer-data_10.8.22.tar.xz ccb922a0d5cf29a9a227a119c8368ec0cba05b16bf85bbbcc387ffbff18075b2 7862 boxer-data_10.8.22_amd64.buildinfo Files: 96de56526ead8106b08dacfdf059253c 1717 misc optional boxer-data_10.8.22.dsc 346530c80e44402dc74d7b704f1f76ea 96540 misc optional boxer-data_10.8.22.tar.xz c7eabe21f420b6ce8cd9d5bf7e22027f 7862 misc optional boxer-data_10.8.22_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmB6oXgACgkQLHwxRsGg ASGVIw//XbUq2GnLFpjrQE7zDihX1P1979sm/JaQoHXtYFl7XmpBGyhs0iF7HcgS qYqkFbW+oiBYAmCYlqMeJ9rWylbxnI8GLW1HuBE2fHewfRq7y9fagLEXf4woOEcV ie1NZ1IdgaTV48V5pPa4gyOkSN1cNd7atAJbinhSmCPMgHKrlIhfekZqi3NtFOjN NbcD2dyNr1BoEFscLuMJczQJPGhJNXDXqb7SnUQurBvzw3PgsvrwgWBrX+DoTT28 pfs81P1UfzoFaJIlROMAISkRfPJTJivH0Ydn1Ns3rl9s6p5i5aY7K7UVwiQ1sYMk KsGujdnlAa0xI/BZajvW1JBl9JJeIp/VhSgHSWXVvc0i53OhOxQkWeNISrE9Er+a csTvzRmRAjd8FNsZivu82nFW+jNciBPx95+1G4QmKAds/EpptIlOnTR3C4pjCxSh dkZoguRVTE0spn4R1APWa6Hdc0u3/JxjKAhMpk74syRpcW8lJ6T033OpA0xgAZkF pmsQLs2fi8Yegq1jW1IbMsA8p3ldOriEes3K1OctEacBZGhB9nvNQchVTLwBqO8W c2HKx2V6H3X7+0oBi6apABdbSIsm+K9tYgtdFOgkbvWAybUlT8Ghpiue9EaUrod3 Kqk5BB6P5G8suNsw/7bXp8nTUcWjnGXMwfPJmDYMOXjgSFIGo0Y= =e7YB -END PGP SIGNATURE End Message ---
Bug#983653: marked as done (task-japanese-gnome-desktop: no Japanese input method available out of the box)
Your message dated Sat, 17 Apr 2021 08:10:17 +
with message-id
and subject line Bug#983653: fixed in tasksel 3.66
has caused the Debian Bug report #983653,
regarding task-japanese-gnome-desktop: no Japanese input method available out
of the box
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.)
--
983653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983653
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: task-japanese-gnome-desktop
Version: 3.64
Severity: grave
Tags: bullseye l10n patch
Justification: renders package unusable
X-Debbugs-Cc: debian-japan...@lists.debian.org
Dear Maintainer,
On a fresh bullseye installation of Japanese GNOME desktop,
its user cannot type Japanese text out of the box.
A fresh buster installation of Japanese GNOME desktop
dist-upgraded to bullseye is also affected.
Note that a fresh buster installation of Japanese GNOME desktop itself
is not affected.
This is caused by the change in the gnome-shell package (Bug#815050) to add
"Recommends: ibus", which breaks any non-ibus input method framework
(Bug#941624),
especially uim (mainly used by Japanese users) and fcitx (mainly used
by Chinese users),
while reverting the change is perhaps not feasible to western language
users for emoji support.
Adding some Japanese input method to the ibus framework should work
around the problem
for Japanese users. Specifically, adding Recommends: ibus-mozc (or ibus-anthy on
architectures where mozc is not available) to this package should work
around the problem.
The attached patch should apply the work-around.
Thanks in advance,
--
YOSHINO Yoshihito
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-3-amd64 (SMP w/1 CPU thread)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages task-japanese-gnome-desktop depends on:
ii tasksel 3.64
Versions of packages task-japanese-gnome-desktop recommends:
ii thunderbird 1:78.7.1-1
ii thunderbird-l10n-ja 1:78.7.1-1
task-japanese-gnome-desktop suggests no packages.
-- no debconf information
--- tasksel-3.64/debian/control 2021-02-15 02:01:51.0 +0900
+++ tasksel-3.64/debian/control 2021-02-28 13:04:16.335684227 +0900
@@ -1423,6 +1423,7 @@
This task localises the GNOME desktop in Japanese.
Depends: ${misc:Depends},
Recommends:
+ ibus-mozc | ibus-anthy,
# evolution has a problem for Japanese, for example it uses always UTF-8
# subject instead of iso-2022-jp used Japanese de-facto. I recommend
# thunderbird as default mailer for Japanese desktop users.
--- End Message ---
--- Begin Message ---
Source: tasksel
Source-Version: 3.66
Done: Holger Wansing
We believe that the bug you reported is fixed in the latest version of
tasksel, 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 983...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Holger Wansing (supplier of updated tasksel 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, 20 Mar 2021 16:22:17 +0800
Source: tasksel
Binary: task-albanian-desktop task-amharic task-amharic-desktop
task-amharic-gnome-desktop task-amharic-kde-desktop task-arabic
task-arabic-desktop task-arabic-kde-desktop task-asturian task-asturian-desktop
task-basque task-basque-desktop task-basque-kde-desktop task-belarusian
task-belarusian-desktop task-belarusian-kde-desktop task-bengali
task-bengali-desktop task-bengali-kde-desktop task-bosnian task-bosnian-desktop
task-bosnian-kde-desktop task-brazilian-portuguese
task-brazilian-portuguese-desktop task-brazilian-portuguese-kde-desktop
task-british-desktop task-british-kde-desktop task-bulgarian
task-bulgarian-desktop task-bulgarian-kde-desktop task-catalan
task-catalan-desktop task-catalan-kde-desktop task-chinese-s
task-chinese-s-desktop task-chinese-s-gnome-desktop task-chinese-s-kde-desktop
task-chinese-t task-chinese-t-desktop task-chinese-t-gnome-desktop
Bug#941624: marked as done (Recommending ibus breaks fcitx)
Your message dated Sat, 17 Apr 2021 08:10:17 + with message-id and subject line Bug#941624: fixed in tasksel 3.66 has caused the Debian Bug report #941624, regarding Recommending ibus breaks fcitx 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.) -- 941624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941624 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-shell Version: 3.34.0-2 Severity: important I've been using fcitx as the default Chinese input method for decades. Recommending ibus simply breaks everything for me. Oct 03 01:23:57 Macadamia fcitx.desktop[2905]: (ERROR-10874 ime.c:432) fcitx-keyboard-in-kan-kagapa already exists Oct 03 01:23:57 Macadamia fcitx.desktop[2905]: (ERROR-10874 ime.c:432) fcitx-keyboard-in-tel-kagapa already exists Oct 03 01:23:57 Macadamia fcitx.desktop[2905]: (ERROR-10874 ime.c:432) fcitx-keyboard-cm-mmuock already exists Oct 03 01:23:57 Macadamia fcitx.desktop[2905]: (ERROR-10874 xim.c:239) Start XIM error. Another XIM daemon named ibus is running? Oct 03 01:23:57 Macadamia fcitx.desktop[2905]: (ERROR-10874 instance.c:443) Exiting. ^ ibus (which I never use) was already running, so fcitx won't start. Please revert 220 * debian/control.in: Recommends ibus, gnome-shell tried to start for years 221 now, ibus is required to input emoji these days. (Closes: #815050) Or find a better solution, e.g. Recommends: ibus | fcitx | --- End Message --- --- Begin Message --- Source: tasksel Source-Version: 3.66 Done: Holger Wansing We believe that the bug you reported is fixed in the latest version of tasksel, 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 941...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Holger Wansing (supplier of updated tasksel 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, 20 Mar 2021 16:22:17 +0800 Source: tasksel Binary: task-albanian-desktop task-amharic task-amharic-desktop task-amharic-gnome-desktop task-amharic-kde-desktop task-arabic task-arabic-desktop task-arabic-kde-desktop task-asturian task-asturian-desktop task-basque task-basque-desktop task-basque-kde-desktop task-belarusian task-belarusian-desktop task-belarusian-kde-desktop task-bengali task-bengali-desktop task-bengali-kde-desktop task-bosnian task-bosnian-desktop task-bosnian-kde-desktop task-brazilian-portuguese task-brazilian-portuguese-desktop task-brazilian-portuguese-kde-desktop task-british-desktop task-british-kde-desktop task-bulgarian task-bulgarian-desktop task-bulgarian-kde-desktop task-catalan task-catalan-desktop task-catalan-kde-desktop task-chinese-s task-chinese-s-desktop task-chinese-s-gnome-desktop task-chinese-s-kde-desktop task-chinese-t task-chinese-t-desktop task-chinese-t-gnome-desktop task-chinese-t-kde-desktop task-cinnamon-desktop task-croatian task-croatian-desktop task-croatian-kde-desktop task-cyrillic task-cyrillic-desktop task-cyrillic-kde-desktop task-czech task-czech-desktop task-czech-kde-desktop task-danish task-danish-desktop task-danish-kde-desktop task-desktop task-dutch task-dutch-desktop task-dutch-kde-desktop task-dzongkha-desktop task-dzongkha-kde-desktop task-english task-esperanto task-esperanto-desktop task-esperanto-kde-desktop task-estonian task-estonian-desktop task-estonian-kde-desktop task-finnish task-finnish-desktop task-finnish-kde-desktop task-french task-french-desktop task-french-kde-desktop task-galician task-galician-desktop task-galician-kde-desktop task-georgian-desktop task-german task-german-desktop task-german-kde-desktop task-gnome-desktop task-gnome-flashback-desktop task-greek task-greek-desktop task-greek-kde-desktop task-gujarati task-gujarati-desktop task-gujarati-kde-desktop task-hebrew task-hebrew-desktop task-hebrew-gnome-desktop task-hebrew-kde-desktop task-hindi task-hindi-desktop task-hindi-kde-desktop task-hungarian task-hungarian-desktop task-hungarian-kde-desktop task-icelandic task-icelandic-desktop task-icelandic-kde-desktop task-indonesian-desktop task-indonesian-kde-desktop task-irish task-irish-desktop task-irish-kde
