Bug#969756: marked as done (networkx breaks botch autopkgtest: KeyError: 'long')
Your message dated Tue, 29 Sep 2020 03:50:14 + with message-id and subject line Bug#969756: fixed in networkx 2.5+ds-2 has caused the Debian Bug report #969756, regarding networkx breaks botch autopkgtest: KeyError: '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.) -- 969756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969756 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: networkx, botch Control: found -1 networkx/2.5+ds-1 Control: found -1 botch/0.22-4 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 networkx the autopkgtest of botch fails in testing when that autopkgtest is run with the binary packages of networkx from unstable. It passes when run with only packages from testing. In tabular form: passfail networkx from testing2.5+ds-1 botch from testing0.22-4 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 networkx 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=networkx https://ci.debian.net/data/autopkgtest/testing/amd64/b/botch/6937981/log.gz checking acl_2.2.52-3_n20.xml + botch-graph-difference "tests/misc/tmp/acl_2.2.52-3_n20.xml" "/tmp/autopkgtest-lxc.hpqt4jni/downtmp/autopkgtest_tmp/tmp/acl_2.2.52-3_n20.xml" + echo + botch-graph-difference "tests/misc/tmp/acl_2.2.52-3_n20.xml" "/tmp/autopkgtest-lxc.hpqt4jni/downtmp/autopkgtest_tmp/tmp/acl_2.2.52-3_n20.xml" + : + botch-graph-difference tests/misc/tmp/acl_2.2.52-3_n20.xml /tmp/autopkgtest-lxc.hpqt4jni/downtmp/autopkgtest_tmp/tmp/acl_2.2.52-3_n20.xml Traceback (most recent call last): File "/usr/bin/botch-graph-difference", line 159, in args = parser.parse_args() File "/usr/lib/python3.8/argparse.py", line 1780, in parse_args args, argv = self.parse_known_args(args, namespace) File "/usr/lib/python3.8/argparse.py", line 1812, in parse_known_args namespace, args = self._parse_known_args(args, namespace) File "/usr/lib/python3.8/argparse.py", line 2021, in _parse_known_args stop_index = consume_positionals(start_index) File "/usr/lib/python3.8/argparse.py", line 1977, in consume_positionals take_action(action, args) File "/usr/lib/python3.8/argparse.py", line 1870, in take_action argument_values = self._get_values(action, argument_strings) File "/usr/lib/python3.8/argparse.py", line 2401, in _get_values value = self._get_value(action, arg_string) File "/usr/lib/python3.8/argparse.py", line 2434, in _get_value result = type_func(arg_string) File "/usr/share/botch/util.py", line 103, in read_graph g = nx.read_graphml(path) File "", line 2, in read_graphml File "/usr/lib/python3/dist-packages/networkx/utils/decorators.py", line 239, in _open_file result = func_to_be_decorated(*new_args, **kwargs) File "/usr/lib/python3/dist-packages/networkx/readwrite/graphml.py", line 258, in read_graphml glist = list(reader(path=path)) File "/usr/lib/python3/dist-packages/networkx/readwrite/graphml.py", line 775, in __call__ (keys, defaults) = self.find_graphml_keys(self.xml) File "/usr/lib/python3/dist-packages/networkx/readwrite/graphml.py", line 951, in find_graphml_keys "type": self.python_type[attr_type], KeyError: 'long' signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: networkx Source-Version: 2.5+ds-2 Done: Sandro Tosi We believe that the bug you reported is fixed in the latest version of networkx, 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 969...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated networkx package) (This message was generated automatically at their request; if you believe that there is a problem
Bug#971343: Problem changing wallpaper causes system to freeze
Package: gnome-control-center Version: 1:3.36.4-1 Severity: critical Tags: upstream When changing the wallpaper to the one that changes throughout the day in both sections xorg and wayland through the gnome control center the system freezes using nouveau and it is necessary to force the system shutdown. As the problem occurs in other distributions and I found out by doing tests I put the upstream tag. I haven't tested the current version 3.38 and I have no idea if it fixes this problem. I haven't found any reports on this and I'm looking through the git repository of gnome and bts. I chose to put this severity because it causes the system to freeze according to what it says in the documentation, which iscauses non-system-related software (or the whole system) to stop, or cause serious data loss, or introduce a security breach in the systems where you install the package. This report follows the documentation: https://www.debian.org/Bugs/Reporting -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.8.0-2-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR:pt:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -BEGIN PGP PUBLIC KEY BLOCK- mQINBF9maJUBEADs8Y/AQuM2cW0pKynIRkUj9qFvnn/HICLJ+MYjPk2/lzJGjepY YzQjkrNOpB5FlnDy0kfAI/ZAFIirytsH1JYx+4XEwBwlofGzS9hl9655u19n2iqp f4CPhXMkbjKQuQMSL+MC8Kn9rWibmcFri415yW0nhiqL//f+Z+9TRYXynKOLdGnE B4zi8l5TVh104rnP+vTChMHnnhBRRx1DNG6vaP+pkV6agHcaTVxcvIThu05+ngwR sPGBpdr/G3Rt9Ltf5O9uiksKa7aD6OX6no4xS+NO4O+Vr5487LYKEpiaEGNjh2/d eAdkqtjmH9lht16sUzqGTgq+Wdqtt0TX5ba5jClWvFcPMU3EVHZ5NsXuD9GQ5Vbx H+j+kNBSaaWZeILPM9DI3qUaQlHGZIL4SIQNBT533CMO9ceOyjG/MQAGvyvov7Li SasyQ65C89ExZhu1R/Z9M4vcWJX3QXf83CYgxoSANaU2eN+Pl9/tzIM+D/xy1O6A FuuaTQKi66kBJv9Ub3/BnEFzcYlbgAZXNly6Ft3T2LYLM9rYJ7cFVCZzSaEd9Hg8 PwiD5SGQN4iqi8AFbRA6IpCd2I35jU5BONyCwvzO4ifuXBZ8dkRYycJvEwS/Wfkx zRUnJx8GWRi6cdd9z4esw2AbzVoIR/cejOaY+DuQ5S2q46ImD56hwELWMwARAQAB tClMZWFuZHJvIEN1bmhhIDxsZWFuZHJvY3VuaGEwMTZAZ21haWwuY29tPokCTgQT AQoAOBYhBJzBewgVKcdfbNX/b2JhzmlCOdYYBQJfZmiVAhsDBQsJCAcCBhUKCQgL AgQWAgMBAh4BAheAAAoJEGJhzmlCOdYYLNcP/0YcO+abhoTXiU7r6yoeRGsI2x1q NBtpJZlaeF7KqDS0gyewQPpOGGMuFxfSvjUJp1MDig/+PyWToTw2uJZGOsDy7aqk Mas90k/UBeH50G7BMmmlOalYCCM/VMPpt0l4n6QxU6ONuQrieZCjIYPPcSBNPIKp I9WbNDSxbE/nb6n7Z2yYNYXXtHTjiPp4bs6Waoi9y5jxc7aTeKh8eI/Nz19w/3sB t3UOxFONVcZldwRiW6F6y32x938K7aBRH/9lB4vTLrejVXEkkAFfJdW+BO+PWKRS Ydnx9+UxtzPH2h2yT68bR4lL9WcEsqSz26s7a27hz4bqHBoLz5BohM8xDtv1eTSp XKCofNASSJ/lGyJ/yjB/hsSQgpt1X/GsyCd21NVKOGjFCW0DU6ZAcx2X0sBrIjDt iV8lUoTum7tW5HEtw1UJ5WY0Iik8wv32gXRaitRP+be1Kvcee4/Cqp0nHRBlO05R 4PG91g6kNOfSKHxH8FcZQ37F6e+dCHuK8Cx8XBegPVShQOFqWBGq7hQ/Uc2teUww B6xRoDIxJPQRTmh+zrHJhYd4r36TJxHQo9oEBJ086NiBW6QRJg7kfnR6p0/nekDs Wpw/lnivGToSDCJrZaOlMhnhZ+jWooH+fEPdnmcJDIByoOwh4hD+S5r9dy+kMlUp gfeT/anhKh/sW54muQINBF9maJUBEACzpPahcamBaALztTnXBnm9C+SNzIhgHvBN MDou32oVt1O42pKl4fa1JHsCS8+4TGPRvYvNqfB/vceEKjKvb5KXIltXR9B+cc4z SycM3srmwmSqGyiNG+oAfmGC0uKtci2vNOdM5J4lBJyn+aSbSLCIaS2hy1ATF4wt S4mnDJQlkWabiL6Nu8gLYup+rly8EwgH7EDIlRHHsZQGxVEXBrcXwqik29/CFZsy 6bA/sQAI9nreLNoexLucIJZGPEw+Wpk1y8vkdvxSZ3dxbQSK+sY4tINR4vp7hqiv NduCyYEoPUu3Vc1vqkxJncUqxjejXYdfS7rt2SqwqkXJeyQbNwlxtAgf3dNWwSCA fWwsL4Tw4ABXE9dy1SlZ1bbLaD4R8lLjY3iLArzDjTda0Lvwxr0+MIpryZevJD3w uikLWKgPqFzNov88jz+n0VSUbIO4Yqm0UnWM7maYx60r2boU9WebvvDoBOcEoNjl 2P/eCHGrExJQ51fVBxfMyHnFsY6r9vLTz1G2KjAjaTWE3DlKZmjib5p3xPJIPQcR V/4Lw8ILgUkGALbnoBQ2NWbRp3As1El5ANSJPWD52PdCEJ7leHIHNjSERvbpvXPM xV6/q5g2e3cSKMFmzyaFCMrsWAnMp5lfBb02u1LREnxBuzJtrtrBBbztMxt3G4r3 yApwqOzOywARAQABiQI2BBgBCgAgFiEEnMF7CBUpx19s1f9vYmHOaUI51hgFAl9m aJUCGwwACgkQYmHOaUI51hh55w//VhNmT8enopY+FW5seVLUf8nqHP3OtDIt5/RP hLnyqU+Vr/EXcYOuNleJr7DhbgWmVroQajow8kzEgJWbgUjuwDON4IjoAUHFqNRn 1qInbQ7hbL8ohL5z05RtCRjWfAE620bda7hWP8Y5EgqKXB5auT1RddJAKthRerrO u7gnehNW1X2CbZHEHTQOFUlXBnhL6Q6NtnT6Fi+t4sIQaRuXtqIBP/Hh88RdwxJk 1eYd0KSgDe7RG3DgQ5da+GRdAyqhNrKrsRjA1Re7poSFevSXyr5hYVvqGhmarpNp wfiTtKC0Wlubgyhzbz53ZFsRAMvOBc+kId+rb74Xs7SrJzr1+lXUuWte9ErIKaaD S/QHzShup9FOBY/WIU1tYAcSL83UkD6NFCzx+R48AG4Hfo25jg7/emj1vseNrfYB mPo/tnYteUXcXUs6wH0JSMmVVBJJtcURH+KgQI9aPtyNFvDlpxtpJFXCDZE7LYZt gUA8owrx1f/XuuLrgM+sS7beS7Z81JcEjBmBDGTNDxYFvO6/Lof9TyVScz4zLdLl MdvV4hIVReH1Cv9vDiQN9BbgMTWcT6RQM5QVArTMIICu5JmTYqVJi3nQOyuvJ2u/ UkqN1M3P724hldLD529LUcWOqeRCQTRRGZy4/l++xCj/KXbZJ4BI8MDkst8bpRBz XXnYczk= =ZmJB -END PGP PUBLIC KEY BLOCK-
Processed: reassign 971229 to symfony, fixed 971229 in 4.4.14+dfsg-1, fixed 970855 in 4.4.14+dfsg-1
Processing commands for cont...@bugs.debian.org:
> reassign 971229 symfony
Bug #971229 {Done: David Prévot } [synfony] symfony: FTBFS:
failed tests
Warning: Unknown package 'synfony'
Bug reassigned from package 'synfony' to 'symfony'.
Ignoring request to alter found versions of bug #971229 to the same values
previously set
Ignoring request to alter fixed versions of bug #971229 to the same values
previously set
> fixed 971229 4.4.14+dfsg-1
Bug #971229 {Done: David Prévot } [symfony] symfony: FTBFS:
failed tests
There is no source info for the package 'symfony' at version '4.4.14+dfsg-1'
with architecture ''
Unable to make a source version for version '4.4.14+dfsg-1'
Marked as fixed in versions 4.4.14+dfsg-1.
> fixed 970855 4.4.14+dfsg-1
Bug #970855 {Done: David Prévot } [symfony] php7.4 breaks
symfony autopkgtest: failed to open stream: Failed to parse address "0"
There is no source info for the package 'symfony' at version '4.4.14+dfsg-1'
with architecture ''
Unable to make a source version for version '4.4.14+dfsg-1'
Marked as fixed in versions 4.4.14+dfsg-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
970855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970855
971229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971229
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: reassign 971229 to synfony, reassign 970855 to symfony
Processing commands for cont...@bugs.debian.org:
> reassign 971229 synfony
Bug #971229 {Done: David Prévot } [src:php7.4,src:symfony]
symfony: FTBFS: failed tests
Bug reassigned from package 'src:php7.4,src:symfony' to 'synfony'.
Warning: Unknown package 'synfony'
Warning: Unknown package 'synfony'
Ignoring request to alter found versions of bug #971229 to the same values
previously set
Warning: Unknown package 'synfony'
Warning: Unknown package 'synfony'
No longer marked as fixed in versions php7.4/4.4.14+dfsg-1 and
symfony/4.4.14+dfsg-1.
Warning: Unknown package 'synfony'
> reassign 970855 symfony
Bug #970855 {Done: David Prévot } [src:php7.4, src:symfony]
php7.4 breaks symfony autopkgtest: failed to open stream: Failed to parse
address "0"
Bug reassigned from package 'src:php7.4, src:symfony' to 'symfony'.
No longer marked as found in versions php7.4/7.4.10-1.
No longer marked as fixed in versions php7.4/4.4.14+dfsg-1 and
symfony/4.4.14+dfsg-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
970855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970855
971229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971229
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#963201: flightgear: diff for building on s390x
Control: tags 963201 + patch Dear maintainer, I'd love to see flightgear get back into bullseye! I see that it's been blocked for a while because it doesn't build on the s390x. The HID bitfield extraction code assumes a little-endian machine, but the s390x is big-endian. Enclosed is a patch to fix that. I've written it as an NMU, but don't plan to actually upload it. I haven't looked for other places that make that assumption. I also haven't tried to verify that the HID code actually works right on an s390x. But at least it builds now. Regards. diff -Nru flightgear-2020.1.3+dfsg/debian/changelog flightgear-2020.1.3+dfsg/debian/changelog --- flightgear-2020.1.3+dfsg/debian/changelog 2020-07-13 01:50:46.0 -0700 +++ flightgear-2020.1.3+dfsg/debian/changelog 2020-09-28 14:32:08.0 -0700 @@ -1,3 +1,10 @@ +flightgear (1:2020.1.3+dfsg-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix HID extractBits for big-endian systems (Closes: #963201) + + -- Joel Ray Holveck Mon, 28 Sep 2020 14:32:08 -0700 + flightgear (1:2020.1.3+dfsg-1) unstable; urgency=medium * New upstream version 2020.1.3+dfsg diff -Nru flightgear-2020.1.3+dfsg/debian/patches/hid-bigendian.patch flightgear-2020.1.3+dfsg/debian/patches/hid-bigendian.patch --- flightgear-2020.1.3+dfsg/debian/patches/hid-bigendian.patch 1969-12-31 16:00:00.0 -0800 +++ flightgear-2020.1.3+dfsg/debian/patches/hid-bigendian.patch 2020-09-28 14:32:08.0 -0700 @@ -0,0 +1,22 @@ +Index: flightgear-2020.1.3+dfsg/src/Input/FGHIDEventInput.cxx +=== +--- flightgear-2020.1.3+dfsg.orig/src/Input/FGHIDEventInput.cxx flightgear-2020.1.3+dfsg/src/Input/FGHIDEventInput.cxx +@@ -27,6 +27,8 @@ + #include + #include + ++#include ++ + #include + #include + +@@ -865,6 +867,8 @@ int extractBits(uint8_t* bytes, size_t l + uint32_t v = 0; + // this goes from byte alignment to word alignment safely + memcpy((void*) , bytes + wholeBytesToSkip, bytesToCopy); ++// the memcpy arranges v in little-endian order, so swap if needed ++v = le32toh(v); + + // shift down so lowest bit is aligned + v = v >> offsetInByte; diff -Nru flightgear-2020.1.3+dfsg/debian/patches/series flightgear-2020.1.3+dfsg/debian/patches/series --- flightgear-2020.1.3+dfsg/debian/patches/series 2020-07-13 01:41:42.0 -0700 +++ flightgear-2020.1.3+dfsg/debian/patches/series 2020-09-28 14:32:08.0 -0700 @@ -6,3 +6,4 @@ disable_some_failing_tests.patch disable-check-for-windows.h.patch 0008-Disable-some-newly-failing-tests.patch +hid-bigendian.patch
Processed: flightgear: diff for building on s390x
Processing control commands: > tags 963201 + patch Bug #963201 [src:flightgear] flightgear: FTBFS on s390x: 10 - HIDInputUnitTests (Failed) Added tag(s) patch. -- 963201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963201 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: limit source to symfony, closing 971229, closing 970855
Processing commands for cont...@bugs.debian.org: > limit source symfony Limiting to bugs with field 'source' containing at least one of 'symfony' Limit currently set to 'source':'symfony' > close 971229 4.4.14+dfsg-1 Bug #971229 [src:php7.4,src:symfony] symfony: FTBFS: failed tests The source 'php7.4' and version '4.4.14+dfsg-1' do not appear to match any binary packages Marked as fixed in versions symfony/4.4.14+dfsg-1 and php7.4/4.4.14+dfsg-1. Bug #971229 [src:php7.4,src:symfony] symfony: FTBFS: failed tests Marked Bug as done > close 970855 4.4.14+dfsg-1 Bug #970855 [src:php7.4, src:symfony] php7.4 breaks symfony autopkgtest: failed to open stream: Failed to parse address "0" The source 'php7.4' and version '4.4.14+dfsg-1' do not appear to match any binary packages Marked as fixed in versions symfony/4.4.14+dfsg-1 and php7.4/4.4.14+dfsg-1. Bug #970855 [src:php7.4, src:symfony] php7.4 breaks symfony autopkgtest: failed to open stream: Failed to parse address "0" Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 970855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970855 971229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971229 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): reassign 971229 to src:php7.4, src:symfony, forcibly merging 970855 971229
Processing commands for cont...@bugs.debian.org: > reassign 971229 src:php7.4, src:symfony Bug #971229 [src:php7.4] symfony: FTBFS: failed tests Bug reassigned from package 'src:php7.4' to 'src:php7.4,src:symfony'. Ignoring request to alter found versions of bug #971229 to the same values previously set Ignoring request to alter fixed versions of bug #971229 to the same values previously set > forcemerge 970855 971229 Bug #970855 [src:php7.4, src:symfony] php7.4 breaks symfony autopkgtest: failed to open stream: Failed to parse address "0" Unable to merge bugs because: package of #971229 is 'src:php7.4,src:symfony' not 'src:php7.4, src:symfony' Failed to forcibly merge 970855: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 970855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970855 971229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971229 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957089: marked as done (cjs: ftbfs with GCC-10)
Your message dated Tue, 29 Sep 2020 11:16:53 +0900
with message-id <20200929021653.gb8...@bulldog.preining.info>
and subject line Re: Bug#957089: cjs: ftbfs with GCC-10
has caused the Debian Bug report #957089,
regarding cjs: ftbfs with GCC-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.)
--
957089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957089
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:cjs
Version: 4.4.0-4
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.
The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/cjs_4.4.0-4_unstable_gcc10.log
The last lines of the build log are at the end of this report.
To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html
[...]
+#MISSING: 4.4.0-4#
(subst)_ZN9GjsModule15evaluate_importEP9JSContextN2JS6HandleIP8JSObjectEEPKc{size_t}S8_i@Base
3.8.0
_ZN9GjsModule5klassE@Base 3.8.0
_ZN9GjsModule7resolveEP9JSContextN2JS6HandleIP8JSObjectEENS3_I4jsidEEPb@Base
3.8.0
_ZN9GjsModule8finalizeEP8JSFreeOpP8JSObject@Base 3.8.0
@@ -113,13 +128,17 @@
(optional=templinst)_ZNKSt5ctypeIcE8do_widenEc@Base 4.0.0
(optional=templinst|arch=!armel !armhf !hppa !i386 !m68k !mipsel !powerpc
!sh4)_ZNSt10_HashtableImSt4pairIKm11GjsAutoCharESaIS3_ENSt8__detail10_Select1stESt8equal_toImESt4hashImENS5_18_Mod_range_hashingENS5_20_Default_ranged_hashENS5_20_Prime_rehash_policyENS5_17_Hashtable_traitsILb0ELb0ELb19_M_rehashEmRS1_@Base
3.8.0
(optional=templinst|arch=armel armhf hppa i386 m68k mipsel powerpc
sh4)_ZNSt10_HashtableImSt4pairIKmSt6vectorISt10unique_ptrI11_GParamSpecPFvPS4_EESaIS8_EEESaISB_ENSt8__detail10_Select1stESt8equal_toImESt4hashImENSD_18_Mod_range_hashingENSD_20_Default_ranged_hashENSD_20_Prime_rehash_policyENSD_17_Hashtable_traitsILb0ELb0ELb121_M_insert_unique_nodeEjjPNSD_10_Hash_nodeISB_Lb0EEEj@Base
4.2.0
- (optional=templinst|arch=!armel !armhf !hppa !i386 !m68k
!sh4)_ZNSt10_HashtableImSt4pairIKmSt6vectorISt10unique_ptrI11_GParamSpecPFvPS4_EESaIS8_EEESaISB_ENSt8__detail10_Select1stESt8equal_toImESt4hashImENSD_18_Mod_range_hashingENSD_20_Default_ranged_hashENSD_20_Prime_rehash_policyENSD_17_Hashtable_traitsILb0ELb0ELb121_M_insert_unique_nodeEmmPNSD_10_Hash_nodeISB_Lb0EEEm@Base
4.0.0
+#MISSING: 4.4.0-4# (optional=templinst|arch=!armel !armhf !hppa !i386 !m68k
!sh4)_ZNSt10_HashtableImSt4pairIKmSt6vectorISt10unique_ptrI11_GParamSpecPFvPS4_EESaIS8_EEESaISB_ENSt8__detail10_Select1stESt8equal_toImESt4hashImENSD_18_Mod_range_hashingENSD_20_Default_ranged_hashENSD_20_Prime_rehash_policyENSD_17_Hashtable_traitsILb0ELb0ELb121_M_insert_unique_nodeEmmPNSD_10_Hash_nodeISB_Lb0EEEm@Base
4.0.0
+
_ZNSt10_HashtableImSt4pairIKmSt6vectorISt10unique_ptrI11_GParamSpecPFvPS4_EESaIS8_EEESaISB_ENSt8__detail10_Select1stESt8equal_toImESt4hashImENSD_18_Mod_range_hashingENSD_20_Default_ranged_hashENSD_20_Prime_rehash_policyENSD_17_Hashtable_traitsILb0ELb0ELb14findERS1_@Base
4.4.0-4
(optional=templinst)_ZNSt10_HashtableImSt4pairIKmSt6vectorISt10unique_ptrI11_GParamSpecPFvPS4_EESaIS8_EEESaISB_ENSt8__detail10_Select1stESt8equal_toImESt4hashImENSD_18_Mod_range_hashingENSD_20_Default_ranged_hashENSD_20_Prime_rehash_policyENSD_17_Hashtable_traitsILb0ELb0ELb15eraseENSD_20_Node_const_iteratorISB_Lb0ELb0EEE@Base
4.0.0
(optional=templinst|arch=armel armhf hppa i386 m68k mipsel powerpc
Bug#908234: marked as done (cjs: Please switch to mozjs78)
Your message dated Tue, 29 Sep 2020 01:33:31 + with message-id and subject line Bug#908234: fixed in cjs 4.6.0-3 has caused the Debian Bug report #908234, regarding cjs: Please switch to mozjs78 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.) -- 908234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908234 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cjs Version: 3.8.0-4 Severity: important Forwarded: https://github.com/linuxmint/cjs/issues/69 Firefox 52 ESR is no longer supported by Mozilla so neither is mozjs52. Ideally, cjs would switch to using mozjs60. I understand this will require coordination with the Cinnamon developers. mozjs60 is currently in the NEW queue. Thanks, Jeremy Bicha --- End Message --- --- Begin Message --- Source: cjs Source-Version: 4.6.0-3 Done: Norbert Preining We believe that the bug you reported is fixed in the latest version of cjs, 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 908...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Norbert Preining (supplier of updated cjs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 29 Sep 2020 10:16:13 +0900 Source: cjs Architecture: source Version: 4.6.0-3 Distribution: experimental Urgency: medium Maintainer: Debian Cinnamon Team Changed-By: Norbert Preining Closes: 908234 Changes: cjs (4.6.0-3) experimental; urgency=medium . [ Fabio Fantoni ] * Add missing libxml2-utils build-dep. . [ Norbert Preining ] * Switch to libmozjs-78 (see https://github.com/linuxmint/cjs/pull/84) (Closes: #908234) Checksums-Sha1: acf81aaa2c75213664b3a1acaaa680c8a7841089 2093 cjs_4.6.0-3.dsc 2c884f87cc0b9d0ec62f47c6efe8986618714d56 457292 cjs_4.6.0-3.debian.tar.xz 5649bab73f327aa2d466b77af5fc4363188dfb83 14528 cjs_4.6.0-3_source.buildinfo Checksums-Sha256: 62b633402d351d0dc750c4cffef189848b9c0c7c6afc7c59f32e73915621d941 2093 cjs_4.6.0-3.dsc ab268cc0e94400bfef8a63f714e41d853ca0907ca892b5cedb6eb1586926d17e 457292 cjs_4.6.0-3.debian.tar.xz 36d8e3cef6e5f53aa49ff2828e487d160232dbfee7e2a3771fffc0b0866e729c 14528 cjs_4.6.0-3_source.buildinfo Files: 4ed305d267bfb603b30944d857558a62 2093 interpreters optional cjs_4.6.0-3.dsc 46b31adb2282eafc322ac956232a52ef 457292 interpreters optional cjs_4.6.0-3.debian.tar.xz af88a7ced8cc527434701f8875129a76 14528 interpreters optional cjs_4.6.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEE68ws0vrA2voQX53I2A4JsIcUAGYFAl9yi9cACgkQ2A4JsIcU AGaYyAf/VuwLalUDVJpvOsD6s6Ku5Lij3qqkdbDftd7pjuZq7qhhpALnjqnq9+YI NCAd0ayJci9Ik7yH23hkWsRJBswk4IFAY1NmE9mnwGQldsTqiOsq4zqxAZDPreLd 65dXUnG0nr9I7G4iW8WsTl2i3nWWAeTT/WvZlc5GWqIpFeTkpudd6zFQwZfKroIa qo8GDt6Tvxq0soWpCroVeURfi3f3ZusMxeJIN8cxO3ldJt3sekv5sGbZa2/PX3P9 MUbaqO91csyAxbwOw6/vMtxayd38sZFvflci0656c4MAHR2EsJQ75tW+QDnN3HIl pIKqqD9yT2RG9IhrozumAK6HQZNc2Q== =AQEr -END PGP SIGNATURE End Message ---
Bug#970610: marked as done (src:cl-kmrcl: fails to migrate to testing for too long: maintainer built arch:all binairies)
Your message dated Mon, 28 Sep 2020 21:03:46 + with message-id and subject line Bug#970610: fixed in cl-kmrcl 1.111-1 has caused the Debian Bug report #970610, regarding src:cl-kmrcl: fails to migrate to testing for too long: maintainer built arch:all binairies 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.) -- 970610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970610 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cl-kmrcl Version: 1.109-1 Severity: serious Control: close -1 1.110-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:cl-kmrcl 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 arch:all 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=cl-kmrcl signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: cl-kmrcl Source-Version: 1.111-1 Done: k...@debian.org (Kevin M. Rosenberg) We believe that the bug you reported is fixed in the latest version of cl-kmrcl, 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 970...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kevin M. Rosenberg (supplier of updated cl-kmrcl 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, 28 Sep 2020 20:05:00 + Source: cl-kmrcl Binary: cl-kmrcl Architecture: source all Version: 1.111-1 Distribution: unstable Urgency: medium Maintainer: Kevin M. Rosenberg Changed-By: Kevin M. Rosenberg Description: cl-kmrcl - General Utilities for Common Lisp Programs Closes: 970610 Changes: cl-kmrcl (1.111-1) unstable; urgency=medium . * Upload source only package (closes: 970610) * New upstream Checksums-Sha1: 7324538802d09cf8752d333ea0af7d7f824ad983 1812 cl-kmrcl_1.111-1.dsc e0536679d8dae70e510230ec36a50d9efd1128ec 52043 cl-kmrcl_1.111.orig.tar.gz 4e99f4385afbfaea99dd614acf741f50de2f3f75 5460 cl-kmrcl_1.111-1.debian.tar.xz a7bb49bc03bb2b78b60febd7c5e8f68603963af5 46684 cl-kmrcl_1.111-1_all.deb 3dc9700e65abacfd87192966eb52cf9bea58cd5a 5537 cl-kmrcl_1.111-1_amd64.buildinfo Checksums-Sha256: 0a4b72815c9015bde680111846694b5a792be610d79d4da07600b814c4a55c25 1812 cl-kmrcl_1.111-1.dsc 0295ab3456dbe9c758aa1214676ede028f8428a16ea751bef46342914ebff6fb 52043 cl-kmrcl_1.111.orig.tar.gz 8540ba0ceab74cc4f80e501a80d2dfba2a69b402904e895e5b006986f5586c36 5460 cl-kmrcl_1.111-1.debian.tar.xz ea70750c96d76fc732fa8597c23806440ab463348a5b5c9486ce601289a5f050 46684 cl-kmrcl_1.111-1_all.deb 181c0a635b4fb2a4df9db43e1c7356d2659baafd1b0910e4c270a5c1eb71 5537
Bug#970609: marked as done (src:cl-sql: fails to migrate to testing for too long: maintainer built arch:all binaries)
Your message dated Mon, 28 Sep 2020 21:03:58 + with message-id and subject line Bug#970609: fixed in cl-sql 6.7.0.1-2 has caused the Debian Bug report #970609, regarding src:cl-sql: fails to migrate to testing for too long: maintainer built arch:all binaries 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.) -- 970609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970609 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cl-sql Version: 6.7.0-1.1 Severity: serious Control: close -1 6.7.0.1-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:cl-sql 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 arch:all 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=cl-sql signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: cl-sql Source-Version: 6.7.0.1-2 Done: k...@debian.org (Kevin M. Rosenberg) We believe that the bug you reported is fixed in the latest version of cl-sql, 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 970...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kevin M. Rosenberg (supplier of updated cl-sql 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, 28 Sep 2020 20:42:03 + Source: cl-sql Architecture: source Version: 6.7.0.1-2 Distribution: unstable Urgency: medium Maintainer: Kevin M. Rosenberg Changed-By: Kevin M. Rosenberg Closes: 970609 Changes: cl-sql (6.7.0.1-2) unstable; urgency=medium . * Source only package upload (closes: 970609) Checksums-Sha1: d1f85c54cc4f380637f5ca61f6193a89d520edda 2427 cl-sql_6.7.0.1-2.dsc e36f45ea218510131a31cf090ede6e0810e16318 11304 cl-sql_6.7.0.1-2.debian.tar.xz 2e3d9d1494ea2da99f6f47898509d41f7b8d43d5 9976 cl-sql_6.7.0.1-2_amd64.buildinfo Checksums-Sha256: ade3a3358cc52ed2fdb0dc0b5e49d1f0bec545922f3826748a58375e13b20686 2427 cl-sql_6.7.0.1-2.dsc dd6ae289e44dab3d29f68c6dece352056690e6d6b55ed3eafa027c129ac924e5 11304 cl-sql_6.7.0.1-2.debian.tar.xz 7e8e5efcd8607c971240a5b866f6cdad3b062ca3cad3d869d1a371593ebd57b6 9976 cl-sql_6.7.0.1-2_amd64.buildinfo Files: 1a176e2fb0ae950426b61ad2ac6a52a3 2427 lisp optional cl-sql_6.7.0.1-2.dsc 1e484d6a1d13e6ef85ed501a667599f9 11304 lisp optional cl-sql_6.7.0.1-2.debian.tar.xz 66f731a1c0e9f9c822d965c0bd51247f 9976 lisp optional cl-sql_6.7.0.1-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEtmAWDE14FMap/ipd56SId9aGxQUFAl9ySroACgkQ56SId9aG xQWi5w/+J2vuaPFqUDc8SqbamZ7ztihzKUX0vuz1yIG6uBCvqM3KZMCH87LJXmtD
Bug#970610: marked as done (src:cl-kmrcl: fails to migrate to testing for too long: maintainer built arch:all binairies)
Your message dated Mon, 28 Sep 2020 20:34:53 + with message-id and subject line Bug#970610: fixed in cl-cluck 0.1.3.1-1 has caused the Debian Bug report #970610, regarding src:cl-kmrcl: fails to migrate to testing for too long: maintainer built arch:all binairies 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.) -- 970610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970610 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cl-kmrcl Version: 1.109-1 Severity: serious Control: close -1 1.110-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:cl-kmrcl 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 arch:all 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=cl-kmrcl signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: cl-cluck Source-Version: 0.1.3.1-1 Done: k...@debian.org (Kevin M. Rosenberg) We believe that the bug you reported is fixed in the latest version of cl-cluck, 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 970...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kevin M. Rosenberg (supplier of updated cl-cluck 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, 28 Sep 2020 19:41:58 + Source: cl-cluck Architecture: source Version: 0.1.3.1-1 Distribution: unstable Urgency: low Maintainer: Kevin M. Rosenberg Changed-By: Kevin M. Rosenberg Closes: 970610 Changes: cl-cluck (0.1.3.1-1) unstable; urgency=low . * Claify purpose header in comments * Upload source only (closes: 970610) Checksums-Sha1: 8300cde76dbb684cfba09eef9a9d340ac85fc370 1823 cl-cluck_0.1.3.1-1.dsc 2150800485e5ba16e3fbecb6926a063df15d6368 4859 cl-cluck_0.1.3.1.orig.tar.gz bd4611b17fecaa15fd1fa3c4ea10e05543ffa862 2304 cl-cluck_0.1.3.1-1.debian.tar.xz d7d4c760b31130191f6732e5b90dacea9e15240b 5470 cl-cluck_0.1.3.1-1_amd64.buildinfo Checksums-Sha256: f9455f7f395617b851ab5602de7d910cd979a7a48269f7e29c7dddfff606c7f8 1823 cl-cluck_0.1.3.1-1.dsc e1a9b1302bdfa072f91f9e4ba6713070f1defd27e8c363ac8ba874a1f9ab998f 4859 cl-cluck_0.1.3.1.orig.tar.gz 4c318868e0c2ede555b30cbc41cf2c2d00c4b8a8b65a8898d45ccd71023f8d2e 2304 cl-cluck_0.1.3.1-1.debian.tar.xz 21c2e8e2736d6a85f0bdd61739a30aaa1c1b8738974d9d91ea0b7156d052 5470 cl-cluck_0.1.3.1-1_amd64.buildinfo Files: e8b57789f1ac524bb9a6d604736b7f75 1823 lisp optional cl-cluck_0.1.3.1-1.dsc 4c3cdbdf1d30048f05a4b02708f75ceb 4859 lisp optional cl-cluck_0.1.3.1.orig.tar.gz 75f9aa255e97737ed2aba497940c2861 2304 lisp optional
Processed: gcc-10: regression in 10.2.0-9 causes segmentation fault in vlc
Processing control commands: > reassign -1 gcc-10 10.2.0-9 Bug #971027 [vlc] vlc: segmentation fault with all video since update to 3.0.11.1-2 Bug reassigned from package 'vlc' to 'gcc-10'. No longer marked as found in versions vlc/3.0.11.1-2. Ignoring request to alter fixed versions of bug #971027 to the same values previously set Bug #971027 [gcc-10] vlc: segmentation fault with all video since update to 3.0.11.1-2 Marked as found in versions gcc-10/10.2.0-9. > retitle -1 gcc-10: regression in 10.2.0-9 causes segmentation fault in vlc Bug #971027 [gcc-10] vlc: segmentation fault with all video since update to 3.0.11.1-2 Changed Bug title to 'gcc-10: regression in 10.2.0-9 causes segmentation fault in vlc' from 'vlc: segmentation fault with all video since update to 3.0.11.1-2'. > affects -1 vlc Bug #971027 [gcc-10] gcc-10: regression in 10.2.0-9 causes segmentation fault in vlc Added indication that 971027 affects vlc > severity -1 serious Bug #971027 [gcc-10] gcc-10: regression in 10.2.0-9 causes segmentation fault in vlc Severity set to 'serious' from 'important' -- 971027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971027 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#971123: kxd: FTBFS: dh_auto_test: error: make -j4 test returned exit code 2
On Sun, Sep 27, 2020 at 08:45:30PM +0200, Lucas Nussbaum wrote: Source: kxd Version: 0.14-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200926 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is due to a change in x509 certificate handling in Go 1.15. It has been fixed in upstream release 0.15. In this repo you can find an updated Debian package for kxd 1.15; I don't have access to upload it to salsa directly, and it would need a DD to do a review and upload in any case: https://blitiri.com.ar/git/r/debian:kxd/ Thanks, Alberto
Bug#971203: dpkg-source cause gap-atlasrep to FTBFS for no reason
On Mon, Sep 28, 2020 at 05:19:33AM +0200, Guillem Jover wrote: > Hi! > > On Sun, 2020-09-27 at 22:53:13 +0200, Bill Allombert wrote: > > On Sun, Sep 27, 2020 at 08:58:00PM +0200, Lucas Nussbaum wrote: > > > During a rebuild of all packages in sid, your package failed to build > > > on amd64. > > > > > > > dpkg-source: error: pathname > > > > '/<>/debian/gaproot/pkg/AtlasRep' points outside source > > > > root (to '/<>') > > > $ apt-get source gap-atlasrep > > Fetched 1351 kB in 2s (722 kB/s) > > dpkg-source: info: extracting gap-atlasrep in gap-atlasrep-2.1.0 > > dpkg-source: info: unpacking gap-atlasrep_2.1.0.orig.tar.bz2 > > dpkg-source: info: unpacking gap-atlasrep_2.1.0-2.debian.tar.xz > > dpkg-source: info: using patch list from debian/patches/series > > dpkg-source: info: applying doc-makefile > > dpkg-source: info: applying default-dir > > dpkg-source: error: pathname > > 'gap-atlasrep-2.1.0/debian/gaproot/pkg/AtlasRep' points outside source > > root (to '/tmp/gap-atlasrep-2.1.0') > > E: Unpack command 'dpkg-source --no-check -x gap-atlasrep_2.1.0-2.dsc' > > failed. > > > > There is no rationale to reject such a symlink which does not point > > _outside_ the source root, but _to_ the source root. > > This leads to a spurious FTBFS. > > Right, this is due to a regex not matching when the basedir is the > same as the canonicalized symlink target. I've fixed this, but need to > adapt the new test case. > > > Also I am concerned that developers might need to unpack old packages > > with symlinks in them. There should be a way to do it, if only to fix > > the packaging. > > I guess it might make sense indeed to disable this when running under > --no-check. Another issue is that dpkg-source -b still allows to build such packages in the first place. So I am not completly sure about why you need to check symlinks. Cheers, -- Bill. Imagine a large red swirl here.
Processed: reassign 971072 to nvidia-modprobe, fixed 971072 in 455.23.04-1
Processing commands for cont...@bugs.debian.org:
> reassign 971072 nvidia-modprobe 450.66-1
Bug #971072 {Done: Luca Boccassi } [nvidia-kernel-support]
nvidia-kernel-support from experimental cannot be installed due to missing
nvidia-modprobe (>= 455)
Bug reassigned from package 'nvidia-kernel-support' to 'nvidia-modprobe'.
No longer marked as found in versions nvidia-graphics-drivers/455.23.04-1.
No longer marked as fixed in versions nvidia-modprobe/455.23.04-1.
Bug #971072 {Done: Luca Boccassi } [nvidia-modprobe]
nvidia-kernel-support from experimental cannot be installed due to missing
nvidia-modprobe (>= 455)
Marked as found in versions nvidia-modprobe/450.66-1.
> fixed 971072 455.23.04-1
Bug #971072 {Done: Luca Boccassi } [nvidia-modprobe]
nvidia-kernel-support from experimental cannot be installed due to missing
nvidia-modprobe (>= 455)
Marked as fixed in versions nvidia-modprobe/455.23.04-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
971072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971072
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 971072
Processing commands for cont...@bugs.debian.org:
> tags 971072 + experimental
Bug #971072 {Done: Luca Boccassi } [nvidia-modprobe]
nvidia-kernel-support from experimental cannot be installed due to missing
nvidia-modprobe (>= 455)
Added tag(s) experimental.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
971072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971072
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#969592: marked as done (sane-backends: FTBFS: +#MISSING: 1.0.27# sanei_pp_outb_epp@Base 1.0.25)
Your message dated Mon, 28 Sep 2020 18:49:33 + with message-id and subject line Bug#969592: fixed in sane-backends 1.0.31-2 has caused the Debian Bug report #969592, regarding sane-backends: FTBFS: +#MISSING: 1.0.27# sanei_pp_outb_epp@Base 1.0.25 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.) -- 969592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969592 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sane-backends Version: 1.0.27-3.2 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) sane-backends FTBFS on armel and armhf: | @@ -7204,7 +7151,7 @@ | sanei_pp_outb_addr@Base 1.0.25 | sanei_pp_outb_ctrl@Base 1.0.25 | sanei_pp_outb_data@Base 1.0.25 | - sanei_pp_outb_epp@Base 1.0.25 | +#MISSING: 1.0.27# sanei_pp_outb_epp@Base 1.0.25 | sanei_pp_release@Base 1.0.25 | sanei_pp_set_datadir@Base 1.0.25 | sanei_pp_setmode@Base 1.0.25 | dh_makeshlibs: error: failing due to earlier errors | make[1]: *** [debian/rules:139: override_dh_makeshlibs-arch] Error 25 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:25: binary-arch] Error 2 See https://buildd.debian.org/status/fetch.php?pkg=sane-backends=armel=1.0.27-3.2%2Bb2=1599315993=0 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: sane-backends Source-Version: 1.0.31-2 Done: =?utf-8?q?J=C3=B6rg_Frings-F=C3=BCrst?= We believe that the bug you reported is fixed in the latest version of sane-backends, 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 969...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jörg Frings-Fürst (supplier of updated sane-backends 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, 27 Sep 2020 13:38:48 +0200 Source: sane-backends Architecture: source Version: 1.0.31-2 Distribution: unstable Urgency: medium Maintainer: Jörg Frings-Fürst Changed-By: Jörg Frings-Fürst Closes: 969592 Changes: sane-backends (1.0.31-2) unstable; urgency=medium . * Upload into unstable (Closes: #969592). * New patch: - debian/patches/0170-return_empty_list_when_local_devices_requested.patch. * Remove not longer needed patches from debian/patches: - 0160-big_endian.patch - 0700-mk_reproducible_results.patch - 0715-20-sane.hwdb_multi-arch.patch * Fix typos in the Forwarded tag in the patch headers. * debian/upstream/metadata: - Change to gitlab. * Fix some trailing whitespaces / blank lines. Checksums-Sha1: 18f82f0ee4cb4cceb307e54029e60ae7e599b811 2466 sane-backends_1.0.31-2.dsc 148f65a8b50b45a945c2d723d784c1895a3d3592 78028 sane-backends_1.0.31-2.debian.tar.xz 0442793753d41403515cef3355e4287a22b39c9d 10456 sane-backends_1.0.31-2_source.buildinfo Checksums-Sha256: be4c6230368b5accb78e0ebe91cafd5c7b64b66b56fb32a22e52e047fa19998a 2466 sane-backends_1.0.31-2.dsc 3ca0bc5f8c857d38d9655296e65956b1c760fba500cf7c9905c7c11bddda822d 78028 sane-backends_1.0.31-2.debian.tar.xz 2dbbb99a6046e790e26566ed294741375b32f8784033fa700b0d78138dfc99da 10456 sane-backends_1.0.31-2_source.buildinfo Files: 9ae13155d00eb06d9153f50b9fae9d01 2466 graphics optional sane-backends_1.0.31-2.dsc e2ba9b7f348c940551a68c78354450ea 78028 graphics optional sane-backends_1.0.31-2.debian.tar.xz 8634698a574dfc7453fc3d053f8fbec4 10456 graphics optional sane-backends_1.0.31-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl9yKUMACgkQweDZLphv fH6sIxAAiSs1kClTw1lNK53i6I3ZGBmqGNIgdp28GvZTem5CvrvuIU7BmoHJyP29 dsY5DKRO/eHNuQwQLHYMQoCMsl3wv2Vq3wQBn+d0MLKIKYbvyDiiQN8sRsu09iAp ii3FI0K5jGS748fUNUO6uUGlIqP6NScD8Sp9yC+KCfEhNk8pCQehZOpOoovIOkCU 3L3ToslfvCPNmpF7OCDmYk4/Uga5VUNF+cYd2lhr8566OU3zVPutx+dr1Ve//d/r JjQFFpdY5lTPbtlAP/gkjGXyCCuQ2wiRUqBTDvsbZvNa0u/f2DWanWc/2tPbybvU 67+8uexKIdpZLEef85JtM5VcXk99aKTlZmqd9uSU7gNLizbFesUKXifGEysRoR5V 1YqfjPrSh+8f+83BxyIleqGFvO139cYFcTLonMgGT/4yJQ1ymMQ53LrU974aPjsj xxO9wHVrTgXsRNLiFUGUClCiEeqgwHIp4BduaK8OdCXDhD1tDWEfU1eSkjJ5nh7n
Bug#967137: marked as done (gmidimonitor: Unversioned Python removal in sid/bullseye)
Your message dated Mon, 28 Sep 2020 18:48:56 + with message-id and subject line Bug#967137: fixed in gmidimonitor 3.6+dfsg0-4 has caused the Debian Bug report #967137, regarding gmidimonitor: Unversioned Python 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.) -- 967137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967137 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gmidimonitor Version: 3.6+dfsg0-3 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned 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 We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. 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 --- Source: gmidimonitor Source-Version: 3.6+dfsg0-4 Done: Dmitry Baryshkov We believe that the bug you reported is fixed in the latest version of gmidimonitor, 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 967...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Baryshkov (supplier of updated gmidimonitor package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 28 Sep 2020 20:20:07 +0200 Source: gmidimonitor Architecture: source Version: 3.6+dfsg0-4 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Dmitry Baryshkov Closes: 943041 967137 967433 Changes: gmidimonitor (3.6+dfsg0-4) unstable; urgency=medium . * Team upload . [ Ondřej Nový ] * d/copyright: Use https protocol in Format field * d/control: Deprecating priority extra as per policy 4.0.1 * d/control: Set Vcs-* to salsa.debian.org . [ Felipe Sateler ] * Change maintainer address to debian-multime...@lists.debian.org . [ Ondřej Nový ] * d/rules: Remove trailing whitespaces * Use debhelper-compat instead of debian/compat . [ Olivier Humbert ] * Update gmidimonitor-alsa.desktop (add French Name & Comment) * Update gmidimonitor-jack.desktop (add French Name & Comment) * Update copyright (http -> https) * Update copyright (add myself) . [ Dmitry Baryshkov ] * d/patches: switch to Waf 2.0.20 * d/control, d/rules: use python3 for building (Closes: #967137, #943041) * d/patches, d/control: switch to using Gtk3 (Closes: #967433) Checksums-Sha1: ad96d2736fbebe70e69ab08c060d75b2aa4f5f80 2106 gmidimonitor_3.6+dfsg0-4.dsc a6e494ca5586af828f39eb1f30e8f7e70822a1b7 133952 gmidimonitor_3.6+dfsg0-4.debian.tar.xz Checksums-Sha256: 7396a3c4f919882661f85e8301d21bb0d497ff57be5b3b89fa23c28f7e1f6712 2106 gmidimonitor_3.6+dfsg0-4.dsc 956712c2ae631f2c2ef8db519fd475cdc89d4b7e5cd70860d5d09220268f44c7 133952 gmidimonitor_3.6+dfsg0-4.debian.tar.xz Files: eafda858171fe6a1db9bd47511d00ca1 2106 sound optional gmidimonitor_3.6+dfsg0-4.dsc ab2db8ef7c5204890d34ac20935fc6c5 133952 sound optional gmidimonitor_3.6+dfsg0-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl9yKlUACgkQafL8UW6n GZOpKw/6Aqvma0NQb1B2cRQePyccwcedliwn8sO/Nd0KMHK6ucAJ3xlIj9naEnYD p2NXNl32WlFDhX/hwnE6x+c+dyPilppS/i6OFr98yKxnnv8reQxhMzV+JHHj8X6l WII+jjDcB1fBcwI9dxRnyE6uYAWbftxhMOVrtYdtLr8rApbRm2T8hUwp17pjHoXe ld0kdOaNzmNO9mspNgBSdQjZOFG8MQ5lKk0KtRtswRQ9cgONu39q9zgOK7UAKgKU
Bug#971040: gnome-shell-extension-easyscreencast: please test with GNOME Shell 3.38 and update dependency
Hello SImon, > May I ask the release team to remove it from testing? I'd like to get > GNOME 3.38 into testing soon, so that we can get as much user testing > on it as possible before we freeze (this will be the version we ship > in bullseye, unless the planned freeze date slips by several months), > and that seems higher-priority to me than any of the Shell extensions. Please go ahead, and thanks for that, Regards, -- Samuel Henrique
Bug#971040: gnome-shell-extension-easyscreencast: please test with GNOME Shell 3.38 and update dependency
On Mon, 28 Sep 2020 at 18:25:04 +0100, Samuel Henrique wrote: > This package has only been alive with patches that I keep applying for > compatibility for some time now, if we don't manage to solve this, I'm > happy to let the package be removed from our repositories, especially > if it blocks gnome's transition. May I ask the release team to remove it from testing? I'd like to get GNOME 3.38 into testing soon, so that we can get as much user testing on it as possible before we freeze (this will be the version we ship in bullseye, unless the planned freeze date slips by several months), and that seems higher-priority to me than any of the Shell extensions. There's no need to remove it from unstable, unless it becomes clear that the necessary updates for 3.38 will never happen. smcv
Bug#971094: marked as done (distro-info: FTBFS: dh_auto_test: error: make -j4 test returned exit code 2)
Your message dated Mon, 28 Sep 2020 18:03:49 + with message-id and subject line Bug#971094: fixed in distro-info 0.24 has caused the Debian Bug report #971094, regarding distro-info: FTBFS: dh_auto_test: error: make -j4 test returned exit code 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 971094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971094 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: distro-info Version: 0.23 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200926 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 '/<>' > ./test-debian-distro-info > cd perl && ./test.pl > testAlias > testAll > testDevel > testOldstable > py3versions: no X-Python3-Version in control file, using supported versions > cd python && python3.8 setup.py test > testStable > 1..32 > testSupported > ok 1 - unique: Matching lists > ok 2 - symmetric_difference: Matching lists > ok 3 - unique: 1 Unique Item > ok 4 - unique: 1 Unique Item in the haystack > ok 5 - symmetric_difference: 1 Unique Item > ok 6 - Debian all > ok 7 - Debian devel > ok 8 - Debian oldstable > ok 9 - Debian stable > ok 10 - Debian testing > ok 11 - Debian valid > ok 12 - Debian valid > ok 13 - Debian invalid > ok 14 - Debian supported > ok 15 - Debian unsupported > ok 16 - Debian codename, invalid > ok 17 - Debian codename > ok 18 - Debian version, invalid > ok 19 - Debian version > ok 20 - Ubuntu all > ok 21 - Ubuntu version > ok 22 - Ubuntu LTS version > ok 23 - Ubuntu devel > ok 24 - Ubuntu LTS > ok 25 - Ubuntu stable > ok 26 - Ubuntu valid > ok 27 - Ubuntu invalid > ok 28 - Ubuntu is_lts > ok 29 - Ubuntu !is_lts > ok 30 - Ubuntu !is_lts > ok 31 - Ubuntu supported > ok 32 - Ubuntu unsupported > testUnsupported > testTesting > testFullname > testRelease > testSeries > testCombinedShortform > testReleaseDate > running test > WARNING: Testing via this command is deprecated and will be removed in a > future version. Users looking for a generic test entry point independent of > test runner are encouraged to use tox. > running egg_info > creating distro_info.egg-info > writing distro_info.egg-info/PKG-INFO > writing dependency_links to distro_info.egg-info/dependency_links.txt > writing top-level names to distro_info.egg-info/top_level.txt > writing manifest file 'distro_info.egg-info/SOURCES.txt' > reading manifest file 'distro_info.egg-info/SOURCES.txt' > writing manifest file 'distro_info.egg-info/SOURCES.txt' > running build_ext > test_pylint (distro_info_test.test_pylint.PylintTestCase) > Test: Run pylint on Python source code ... testHelp > testExactlyOne > testUnrecognizedOption > testUnrecognizedArguments > testMissingArgumentAlias > testMissingArgumentDate > testMissingArgumentSeries > testInvalidAlias > testInvalidDate > testInvalidSeries > testMultipleAlias > testMultipleDates > testMultipleSeries > testUnknownSeries > testDays > > Ran 28 tests. > > OK > ./test-ubuntu-distro-info > testAll > testDevel > testLatest > testLTS > testStable > testSupported > testUnsupported > testFullname > testRelease > testSeries > testCombinedShortform > testReleaseDate > testHelp > testExactlyOne > testUnrecognizedOption > testUnrecognizedArguments > testMissingArgumentDate > testMissingArgumentSeries > testDistributionDataOutdated > testInvalidDate > testInvalidSeries > testMultipleDates > testMultipleSeries > testUnknownSeries > testDays > > Ran 25 tests. > > OK > Running following command: > /usr/bin/python3.8 -m pylint > --rcfile=/<>/python/distro_info_test/pylint.conf -- > debian-distro-info ubuntu-distro-info distro_info_test distro_info.py setup.py > FAIL > test_all (distro_info_test.test_distro_info.DebianDistroInfoTestCase) > Test: List all known Debian distributions. ... ok > test_codename (distro_info_test.test_distro_info.DebianDistroInfoTestCase) > Test: Codename decoding ... ok > test_codename_result > (distro_info_test.test_distro_info.DebianDistroInfoTestCase) > Test: Check result set to codename. ... ok > test_devel (distro_info_test.test_distro_info.DebianDistroInfoTestCase) > Test: Get latest development Debian distribution. ... ok > test_fullname (distro_info_test.test_distro_info.DebianDistroInfoTestCase) > Test: Check result set to fullname. ... ok > test_old (distro_info_test.test_distro_info.DebianDistroInfoTestCase) > Test: Get old (stable) Debian distribution. ... ok > test_release
Processed: Bug#971094 marked as pending in distro-info
Processing control commands: > tag -1 pending Bug #971094 [src:distro-info] distro-info: FTBFS: dh_auto_test: error: make -j4 test returned exit code 2 Added tag(s) pending. -- 971094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971094 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#971094: marked as pending in distro-info
Control: tag -1 pending Hello, Bug #971094 in distro-info reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/distro-info/-/commit/9e22c0cf8a6581aa2219cdc69c37da57bb89015e Fix issues found by pylint 2.6.0 pylint 2.6.0 complains: ``` distro_info.py:51:8: R1725: Consider using Python 3 style super() without arguments (super-with-arguments) distro_info.py:182:8: R1725: Consider using Python 3 style super() without arguments (super-with-arguments) distro_info.py:248:8: R1725: Consider using Python 3 style super() without arguments (super-with-arguments) ``` Closes: #971094 Signed-off-by: Benjamin Drung (this message was generated automatically) -- Greetings https://bugs.debian.org/971094
Processed: mariadb bugs
Processing commands for cont...@bugs.debian.org: > tags 929707 moreinfo Bug #929707 [mariadb-client-10.1] mariadb-client-10.1: import of "mysqldump --all-databases" fails with "ERROR 1062 (23000): Duplicate entry" Added tag(s) moreinfo. > severity 970662 important Bug #970662 [src:mariadb-10.5] mariadb-10.5: FTBFS on x32: operand size mismatch for `crc32' Severity set to 'important' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 929707: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929707 970662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970662 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: gnome-shell-extension-easyscreencast: please test with GNOME Shell 3.38 and update dependency
Processing control commands: > tags -1 help upstream Bug #971040 [gnome-shell-extension-easyscreencast] gnome-shell-extension-easyscreencast: please test with GNOME Shell 3.38 and update dependency Added tag(s) help and upstream. -- 971040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971040 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#971040: gnome-shell-extension-easyscreencast: please test with GNOME Shell 3.38 and update dependency
Control: tags -1 help upstream Hello Simon, Thanks for the bugreport, I've bumped the requirements to make it work with 3.38 but the extension fails to load with: $ sudo journalctl /usr/bin/gnome-shell | grep screencast Sep 28 18:01:57 tnetennba gnome-shell[2373]: JS ERROR: Extension easyscreenc...@iacopodeenosee.gmail.com: ImportError: No JS module 'screencast' found in search path You mention a 1.2.0 release, but I don't think that ever happened, there is a commit bumping the version, and some non-critical changes, but no release was made, in any case, I don't think it will solve the issue. This package has only been alive with patches that I keep applying for compatibility for some time now, if we don't manage to solve this, I'm happy to let the package be removed from our repositories, especially if it blocks gnome's transition. Regards, -- Samuel Henrique
Processed: [bts-link] source package ruby-dalli
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package ruby-dalli > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #966384 (http://bugs.debian.org/966384) > # Bug title: ruby-dalli: ftbfs with rails 6 in experimental > # * https://github.com/petergoldstein/dalli/issues/752 > # * remote status changed: open -> closed > # * closed upstream > tags 966384 + fixed-upstream Bug #966384 [ruby-dalli] ruby-dalli: ftbfs with rails 6 in experimental Added tag(s) fixed-upstream. > usertags 966384 - status-open Usertags were: status-open. Usertags are now: . > usertags 966384 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 966384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966384 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package ruby-bootstrap-switch-rails
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package ruby-bootstrap-switch-rails > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #970782 (http://bugs.debian.org/970782) > # Bug title: ruby-bootstrap-switch-rails: 3.3.4 version is broken, downgrade > to 3.3.3 > # * https://github.com/Bttstrp/bootstrap-switch/issues/691 > # * remote status changed: (?) -> closed > # * closed upstream > tags 970782 + fixed-upstream Bug #970782 [ruby-bootstrap-switch-rails] ruby-bootstrap-switch-rails: 3.3.4 version is broken, downgrade to 3.3.3 Added tag(s) fixed-upstream. > usertags 970782 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 970782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970782 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 947547 is serious
Processing commands for cont...@bugs.debian.org: > severity 947547 serious Bug #947547 [src:osc] osc: Missing dependency on python3-m2crypto Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 947547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947547 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#855541: purple-matrix: Not ready for release yet
On Tue, Sep 22, 2020 at 09:51:14PM +0200, Alex ARNAUD wrote: > > I think this version shouldn't be shipped with the next > > release. Like the description says, it's "somewhat alpha". > > > > It works some times, but then stops working, it crashes, > > and so on. > > I've used the package purple-matrix on Debian 10 since at least 6 > months through Pidgin. It's not a perfect tool, have issues but in > my opinion it is usable. Sometimes purple-matrix is disconnected > or makes Pidgin to crash but it's quite rare. It's sufficient to > restart Pidgin to make it working again. > > I have two points why I think we should have it into next stable: > > * This is very difficult for a stable user to use purple-matrix. In my >case, I have had to rebuilt the package due to dependencies and it's >clearly something not easy for all. > * As a visual-impaired person, purple-matrix through Pidgin is the >most accessible Matrix client I've used. > > There are still reasons why we would like to keep it in unstable: > > * There are no commits in 2020 > * The project doesn't publish new release and "just" push commits Hi, I think that this project is essentially dead, there has never been a release and as you say there hasn't been changes in almost a year. I have stopped using it myself and the reason why I didn't ask for its removal from Debian is that it's a very small package with a very low manteinance burden (and because popcon shows that it has some users). But it seems that there are other alternatives nowadays. The official Matrix website no longer lists purple-matrix, but there are however other text-based clients such as weechat-matrix and gomuks. I cannot evaluate how accessible they are, though. Berto
Bug#971096: marked as done (ros-rviz: FTBFS: AttributeError: "pyqt_sip_dir" is not a valid configuration value or user option)
Your message dated Mon, 28 Sep 2020 16:49:25 +
with message-id
and subject line Bug#971096: fixed in ros-python-qt-binding 0.4.3-2
has caused the Debian Bug report #971096,
regarding ros-rviz: FTBFS: AttributeError: "pyqt_sip_dir" is not a valid
configuration value or user option
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.)
--
971096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971096
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ros-rviz
Version: 1.14.1+dfsg-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200926 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[3]: Entering directory '/<>/.pybuild/cpython3_3.8/build'
> cd /<>/.pybuild/cpython3_3.8/build && /usr/bin/cmake -E
> cmake_depends "Unix Makefiles" /<> /<>/src/rviz
> /<>/.pybuild/cpython3_3.8/build
> /<>/.pybuild/cpython3_3.8/build/src/rviz
> /<>/.pybuild/cpython3_3.8/build/src/rviz/CMakeFiles/executable.dir/DependInfo.cmake
> --color=
> Traceback (most recent call last):
> File "/usr/share/python_qt_binding/cmake/sip_configure.py", line 57, in
> get_sip_dir_flags
> sip_dir = config.pyqt_sip_dir
> File "/usr/lib/python3/dist-packages/sipconfig_nd8.py", line 193, in
> __getattr__
> raise AttributeError("\"%s\" is not a valid configuration value or user
> option" % name)
> AttributeError: "pyqt_sip_dir" is not a valid configuration value or user
> option
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
> File "/usr/share/python_qt_binding/cmake/sip_configure.py", line 92, in
>
> sip_dir, sip_flags = get_sip_dir_flags(config)
> File "/usr/share/python_qt_binding/cmake/sip_configure.py", line 72, in
> get_sip_dir_flags
> raise FileNotFoundError('The sip directory for PyQt5 could not be
> located. Please ensure' +
> FileNotFoundError: The sip directory for PyQt5 could not be located. Please
> ensure that PyQt5 is installed
> make[3]: Leaving directory '/<>/.pybuild/cpython3_3.8/build'
> make[3]: ***
> [src/python_bindings/sip/CMakeFiles/librviz_sip.dir/build.make:117:
> sip/rviz_sip/Makefile] Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/09/26/ros-rviz_1.14.1+dfsg-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
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: ros-python-qt-binding
Source-Version: 0.4.3-2
Done: Jochen Sprickerhof
We believe that the bug you reported is fixed in the latest version of
ros-python-qt-binding, 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 971...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jochen Sprickerhof (supplier of updated
ros-python-qt-binding package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 28 Sep 2020 18:28:05 +0200
Source: ros-python-qt-binding
Architecture: source
Version: 0.4.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Jochen Sprickerhof
Closes: 971096
Changes:
ros-python-qt-binding (0.4.3-2) unstable; urgency=medium
.
* Add patch for new sip dir (Closes: #971096)
Checksums-Sha1:
3fc1b17ef07c6b4650307eb17ceac452cde7cc59 2173 ros-python-qt-binding_0.4.3-2.dsc
b10f0953e2c43941b69e059dad566f166ccace7d 4224
ros-python-qt-binding_0.4.3-2.debian.tar.xz
e3da956d89c62ceb689e55bc7e16a151166064be 7695
ros-python-qt-binding_0.4.3-2_source.buildinfo
Checksums-Sha256:
13c3ceb549e46cc62384e0cea221c084ff886c564028ac7779c0ad3dc2cd7e72 2173
ros-python-qt-binding_0.4.3-2.dsc
5d8c79390c28365d2a58b61fb4964d26a15179ecb8798dc50af9d5135b4e85e1 4224
ros-python-qt-binding_0.4.3-2.debian.tar.xz
Bug#971206: marked as done (haskell-snap-templates: FTBFS: die', called at libraries/Cabal/Cabal/Distribution/Simple/Configure.hs:1022:20 in Cabal-3.0.1.0:Distribution.Simple.Configure)
Your message dated Mon, 28 Sep 2020 16:40:17 + with message-id and subject line Bug#971206: fixed in haskell-snap-templates 1.0.0.2-4 has caused the Debian Bug report #971206, regarding haskell-snap-templates: FTBFS: die', called at libraries/Cabal/Cabal/Distribution/Simple/Configure.hs:1022:20 in Cabal-3.0.1.0:Distribution.Simple.Configure 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.) -- 971206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971206 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-snap-templates Version: 1.0.0.2-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200926 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package haskell-snap-templates > dpkg-buildpackage: info: source version 1.0.0.2-3 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Gianfranco Costamagna > > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > test -x debian/rules > dh_clean > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > clean_recipe > Running rm -rf dist dist-ghc dist-ghcjs dist-hugs debian/hlibrary.setup > Setup.hi Setup.ho Setup.o .\*config\* > Running rm -f configure-ghc-stamp configure-ghcjs-stamp build-ghc-stamp > build-ghcjs-stamp build-hugs-stamp build-haddock-stamp > Running rm -rf debian/tmp-inst-ghc debian/tmp-inst-ghcjs > Running rm -f debian/extra-depends-ghc debian/extra-depends-ghcjs > Running rm -f debian/hlibrary.Makefile > Running rm -rf debian/dh_haskell_shlibdeps > Running rm -rf debian/tmp-db > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building haskell-snap-templates using existing > ./haskell-snap-templates_1.0.0.2.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: building haskell-snap-templates in > haskell-snap-templates_1.0.0.2-3.debian.tar.xz > dpkg-source: info: building haskell-snap-templates in > haskell-snap-templates_1.0.0.2-3.dsc > debian/rules binary > test -x debian/rules > dh_testroot > dh_prep > dh_installdirs -A > mkdir -p "." > CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85 > CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85 > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > make_setup_recipe > Running ghc --make Setup.hs -o debian/hlibrary.setup > [1 of 1] Compiling Main ( Setup.hs, Setup.o ) > Linking debian/hlibrary.setup ... > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > configure_recipe > Running debian/hlibrary.setup configure --ghc -v2 > --package-db=/var/lib/ghc/package.conf.d --prefix=/usr > --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib > --builddir=dist-ghc --ghc-option=-optl-Wl\,-z\,relro > --haddockdir=/usr/lib/ghc-doc/haddock/snap-templates-1.0.0.2/ > --datasubdir=snap-templates > --htmldir=/usr/share/doc/libghc-snap-templates-doc/html/ > Using Parsec parser > Configuring snap-templates-1.0.0.2... > CallStack (from HasCallStack): > die', called at > libraries/Cabal/Cabal/Distribution/Simple/Configure.hs:1022:20 in > Cabal-3.0.1.0:Distribution.Simple.Configure > configureFinalizedPackage, called at > libraries/Cabal/Cabal/Distribution/Simple/Configure.hs:475:12 in > Cabal-3.0.1.0:Distribution.Simple.Configure > configure, called at libraries/Cabal/Cabal/Distribution/Simple.hs:625:20 in > Cabal-3.0.1.0:Distribution.Simple > confHook, called at > libraries/Cabal/Cabal/Distribution/Simple/UserHooks.hs:65:5 in > Cabal-3.0.1.0:Distribution.Simple.UserHooks > configureAction, called at > libraries/Cabal/Cabal/Distribution/Simple.hs:180:19 in > Cabal-3.0.1.0:Distribution.Simple > defaultMainHelper, called at > libraries/Cabal/Cabal/Distribution/Simple.hs:116:27 in > Cabal-3.0.1.0:Distribution.Simple > defaultMain, called at Setup.hs:3:8 in main:Main > hlibrary.setup: Encountered missing or private dependencies: > hashable ==1.1.* || >=1.2.0.6 && <1.3, > template-haskell >=2.2 && <2.15 > > make: *** [/usr/share/cdbs/1/class/hlibrary.mk:142: configure-ghc-stamp] > Error 1 The full build log is available from: http://qa-logs.debian.net/2020/09/26/haskell-snap-templates_1.0.0.2-3_unstable.log A list of current common problems and possible solutions is
Bug#971274: webext-compactheader: not compatible with thunderbird 78
Package: webext-compactheader Version: 3.0.0~beta5-2 Severity: grave Control: forwarded -1 https://github.com/jmozmoz/compactheader/issues/42 After upgrading thunderbird from 68 to 78, it deactivated the CompactHeader extension as incompatible. Perhaps it should be replaced by https://addons.thunderbird.net/en-US/thunderbird/addon/compact-headers/ ? -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-rc7-nouveau (SMP w/2 CPU threads) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages webext-compactheader depends on: ii thunderbird 1:78.3.1-1 webext-compactheader recommends no packages. webext-compactheader suggests no packages. -- no debconf information
Processed: webext-compactheader: not compatible with thunderbird 78
Processing control commands: > forwarded -1 https://github.com/jmozmoz/compactheader/issues/42 Bug #971274 [webext-compactheader] webext-compactheader: not compatible with thunderbird 78 Set Bug forwarded-to-address to 'https://github.com/jmozmoz/compactheader/issues/42'. -- 971274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971274 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 971144 is forwarded to https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/620
Processing commands for cont...@bugs.debian.org: > forwarded 971144 > https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/620 Bug #971144 [src:network-manager] network-manager: FTBFS: Error: no ID for constraint linkend: "nmcli". Set Bug forwarded-to-address to 'https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/620'. > thanks Stopping processing here. Please contact me if you need assistance. -- 971144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971144 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#971244: marked as done (nqp-data: Missing Breaks/Replaces headers: trying to overwrite '/usr/share/nqp/lib/MASTNodes.moarvm', which is also in package nqp 2020.06+dfsg-1)
Your message dated Mon, 28 Sep 2020 15:49:25 + with message-id and subject line Bug#971244: fixed in nqp 2020.09+dfsg-2 has caused the Debian Bug report #971244, regarding nqp-data: Missing Breaks/Replaces headers: trying to overwrite '/usr/share/nqp/lib/MASTNodes.moarvm', which is also in package nqp 2020.06+dfsg-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.) -- 971244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971244 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nqp-data Version: 2020.09+dfsg-1 Severity: serious Hi, upgrading nqp and nqp-data from 2020.06 to 2020.09 fails for me as follows: [...] Unpacking nqp-data (2020.09+dfsg-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-lsZi6y/14-nqp-data_2020.09+dfsg-1_all.deb (--unpack): trying to overwrite '/usr/share/nqp/lib/MASTNodes.moarvm', which is also in package nqp 2020.06+dfsg-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../15-nqp_2020.09+dfsg-1_amd64.deb ... Unpacking nqp (2020.09+dfsg-1) over (2020.06+dfsg-1) ... [...] If I run the upgrade a second time, it works because nqp is already upgraded then. Nevertheless an RC bug due to the file conflict upon first upgrade. Looks as if Breaks and Replaces headers are missing in the nqp-data package and that it takes over files from the old nqp package. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages nqp-data depends on: ii libjs-angularjs 1.8.0-1 ii libjs-bootstrap 3.4.1+dfsg-1 ii moarvm 2020.09+dfsg-1 nqp-data recommends no packages. nqp-data suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: nqp Source-Version: 2020.09+dfsg-2 Done: Dominique Dumont We believe that the bug you reported is fixed in the latest version of nqp, 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 971...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dominique Dumont (supplier of updated nqp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 28 Sep 2020 12:00:39 +0200 Source: nqp Architecture: source Version: 2020.09+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Rakudo Maintainers Changed-By: Dominique Dumont Closes: 971244 Changes: nqp (2020.09+dfsg-2) unstable; urgency=medium . * control: add missing break/replace entries (Closes: 971244) * add missing nqp package split change in 2020.07 log Checksums-Sha1: a3c125674d4b091fc9d683448e04c43f4f6ac6f6 2430 nqp_2020.09+dfsg-2.dsc 30aa48e3560c3a1ae1295c99d43fb95c363966ed 15900 nqp_2020.09+dfsg-2.debian.tar.xz b5cc379787d31fcce1f29188f49fb7a30bdc89fb 5953 nqp_2020.09+dfsg-2_source.buildinfo Checksums-Sha256: 1ba25746ec6ac98eddbd3f6d5e897b43bb6a7c6b51c990b7f4aa60e5798fad5e 2430 nqp_2020.09+dfsg-2.dsc dfd912c6522629667dc2e3994c2b877fe8b0e235ec771ef1bdc22fe60762ea74 15900 nqp_2020.09+dfsg-2.debian.tar.xz f64ddba538b7829980370a21a7940b15d6ffabfda4a260a01fa6a3fb0c021ad3 5953 nqp_2020.09+dfsg-2_source.buildinfo Files: f26d222e51086ca198ac9de7043a4436 2430 interpreters optional nqp_2020.09+dfsg-2.dsc 9fd0c0a19b787399352d30106f307f7a 15900 interpreters optional nqp_2020.09+dfsg-2.debian.tar.xz 8a35d85b070fdd0be457a0aa6b65c8d5 5953 interpreters optional nqp_2020.09+dfsg-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn3I5/LZk8Qsz6dwDwx9P2UmrK2wFAl9yAHMACgkQwx9P2Umr K2ybXg/9HYKb8WyI94YaVO+Qib0y8t3gHedKHxrB5HhyzLQH3ZJBKeWFC9S6QBjb fPWaIxKHygCEYqR6SOQ90BFLpREnw1MvYI+cAoET8Ur/5Fm+d/8t8GubAAJE/uzG r6o3ADTedE2rNz3fqvdAq11TR2aS6pzm+jblFP5zn818Jf8TP+yJ3ndxyKJhyoi7
Processed (with 1 error): Re: [Pkg-utopia-maintainers] Bug#971144: network-manager: FTBFS: Error: no ID for constraint linkend: "nmcli".
Processing control commands: > tags -1 + fixed-upstream patch Bug #971144 [src:network-manager] network-manager: FTBFS: Error: no ID for constraint linkend: "nmcli". Added tag(s) patch and fixed-upstream. > forwarded -1 Unknown command or malformed arguments to command. -- 971144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971144 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#971144: [Pkg-utopia-maintainers] Bug#971144: network-manager: FTBFS: Error: no ID for constraint linkend: "nmcli".
Control: tags -1 + fixed-upstream patch Control: forwarded -1 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/620 Hi Lucas, thanks for your bug report. Am 27.09.20 um 20:45 schrieb Lucas Nussbaum: >> /usr/bin/xsltproc --output man/nmtui.1 --path man --xinclude --nonet >> --stringparam man.output.quietly 1 --stringparam funcsynopsis.style ansi >> --stringparam man.th.extra1.suppress 1 --stringparam >> man.authors.section.enabled 0 --stringparam man.copyright.section.enabled 0 >> --stringparam man.th.title.max.length 30 >> http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl >> man/nmtui.xml >> "/usr/bin/python3" ./tools/generate-docs-nm-settings-docs-merge.py >> man/nm-settings-docs-dbus.xml libnm/nm-property-infos-dbus.xml >> libnm/nm-settings-docs-gir.xml >> Traceback (most recent call last): >> File "./tools/generate-docs-nm-settings-docs-merge.py", line 127, in >> >> xml_roots = list([ET.parse(f).getroot() for f in gl_input_files]) >> File "./tools/generate-docs-nm-settings-docs-merge.py", line 127, in >> >> xml_roots = list([ET.parse(f).getroot() for f in gl_input_files]) >> File "/usr/lib/python3.8/xml/etree/ElementTree.py", line 1202, in parse >> tree.parse(source, parser) >> File "/usr/lib/python3.8/xml/etree/ElementTree.py", line 595, in parse >> self._root = parser._parse_whole(source) >> xml.etree.ElementTree.ParseError: not well-formed (invalid token): line 6, >> column 266 >> Error: no ID for constraint linkend: "nmcli". >> make[3]: *** [Makefile:20125: man/nm-settings-docs-dbus.xml] Error 1 This particular issue has been fixed upstream by https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/7d26773138dd4270c45e131761d4e6be58f64d12 and will be part of the next upstream release. signature.asc Description: OpenPGP digital signature
Bug#971183: marked as done (haskell-gi-atk: FTBFS: Unknown GIR element "docsection" when processing namespace "GLib", aborting.)
Your message dated Mon, 28 Sep 2020 15:35:03 + with message-id and subject line Bug#971183: fixed in haskell-haskell-gi 0.24.4-2 has caused the Debian Bug report #971183, regarding haskell-gi-atk: FTBFS: Unknown GIR element "docsection" when processing namespace "GLib", aborting. 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.) -- 971183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-gi-atk Version: 2.0.22-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200926 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package haskell-gi-atk > dpkg-buildpackage: info: source version 2.0.22-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Ilias Tsitsimpis > > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > test -x debian/rules > dh_clean > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > clean_recipe > Running rm -rf dist dist-ghc dist-ghcjs dist-hugs debian/hlibrary.setup > Setup.hi Setup.ho Setup.o .\*config\* > Running rm -f configure-ghc-stamp configure-ghcjs-stamp build-ghc-stamp > build-ghcjs-stamp build-hugs-stamp build-haddock-stamp > Running rm -rf debian/tmp-inst-ghc debian/tmp-inst-ghcjs > Running rm -f debian/extra-depends-ghc debian/extra-depends-ghcjs > Running rm -f debian/hlibrary.Makefile > Running rm -rf debian/dh_haskell_shlibdeps > Running rm -rf debian/tmp-db > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building haskell-gi-atk using existing > ./haskell-gi-atk_2.0.22.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: building haskell-gi-atk in > haskell-gi-atk_2.0.22-1.debian.tar.xz > dpkg-source: info: building haskell-gi-atk in haskell-gi-atk_2.0.22-1.dsc > debian/rules binary > test -x debian/rules > dh_testroot > dh_prep > dh_installdirs -A > mkdir -p "." > CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85 > CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85 > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > make_setup_recipe > Running ghc --make Setup.hs -o debian/hlibrary.setup > [1 of 1] Compiling Main ( Setup.hs, Setup.o ) > Linking debian/hlibrary.setup ... > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > configure_recipe > Running debian/hlibrary.setup configure --ghc -v2 > --package-db=/var/lib/ghc/package.conf.d --prefix=/usr > --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib > --builddir=dist-ghc --ghc-option=-optl-Wl\,-z\,relro > --haddockdir=/usr/lib/ghc-doc/haddock/gi-atk-2.0.22/ --datasubdir=gi-atk > --htmldir=/usr/share/doc/libghc-gi-atk-doc/html/ --enable-library-profiling > Using Parsec parser > Unknown GIR element "docsection" when processing namespace "GLib", aborting. > CallStack (from HasCallStack): > error, called at lib/Data/GI/CodeGen/API.hs:201:16 in > haskell-gi-0.24.4-GhfHY0VJtr89rHNQ5kPVxX:Data.GI.CodeGen.API > make: *** [/usr/share/cdbs/1/class/hlibrary.mk:142: configure-ghc-stamp] > Error 1 The full build log is available from: http://qa-logs.debian.net/2020/09/26/haskell-gi-atk_2.0.22-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: haskell-haskell-gi Source-Version: 0.24.4-2 Done: Ilias Tsitsimpis We believe that the bug you reported is fixed in the latest version of haskell-haskell-gi, 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 971...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ilias Tsitsimpis (supplier of updated haskell-haskell-gi package) (This message was generated
Bug#971175: marked as done (haskell-gi-gobject: FTBFS: Unknown GIR element "docsection" when processing namespace "GObject", aborting.)
Your message dated Mon, 28 Sep 2020 15:35:03 + with message-id and subject line Bug#971183: fixed in haskell-haskell-gi 0.24.4-2 has caused the Debian Bug report #971183, regarding haskell-gi-gobject: FTBFS: Unknown GIR element "docsection" when processing namespace "GObject", aborting. 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.) -- 971183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-gi-gobject Version: 2.0.24-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200926 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package haskell-gi-gobject > dpkg-buildpackage: info: source version 2.0.24-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Ilias Tsitsimpis > > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > test -x debian/rules > dh_clean > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > clean_recipe > Running rm -rf dist dist-ghc dist-ghcjs dist-hugs debian/hlibrary.setup > Setup.hi Setup.ho Setup.o .\*config\* > Running rm -f configure-ghc-stamp configure-ghcjs-stamp build-ghc-stamp > build-ghcjs-stamp build-hugs-stamp build-haddock-stamp > Running rm -rf debian/tmp-inst-ghc debian/tmp-inst-ghcjs > Running rm -f debian/extra-depends-ghc debian/extra-depends-ghcjs > Running rm -f debian/hlibrary.Makefile > Running rm -rf debian/dh_haskell_shlibdeps > Running rm -rf debian/tmp-db > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building haskell-gi-gobject using existing > ./haskell-gi-gobject_2.0.24.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: building haskell-gi-gobject in > haskell-gi-gobject_2.0.24-1.debian.tar.xz > dpkg-source: info: building haskell-gi-gobject in > haskell-gi-gobject_2.0.24-1.dsc > debian/rules binary > test -x debian/rules > dh_testroot > dh_prep > dh_installdirs -A > mkdir -p "." > CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85 > CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85 > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > make_setup_recipe > Running ghc --make Setup.hs -o debian/hlibrary.setup > [1 of 1] Compiling Main ( Setup.hs, Setup.o ) > Linking debian/hlibrary.setup ... > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > configure_recipe > Running debian/hlibrary.setup configure --ghc -v2 > --package-db=/var/lib/ghc/package.conf.d --prefix=/usr > --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib > --builddir=dist-ghc --ghc-option=-optl-Wl\,-z\,relro > --haddockdir=/usr/lib/ghc-doc/haddock/gi-gobject-2.0.24/ > --datasubdir=gi-gobject --htmldir=/usr/share/doc/libghc-gi-gobject-doc/html/ > --enable-library-profiling > Using Parsec parser > Unknown GIR element "docsection" when processing namespace "GObject", > aborting. > CallStack (from HasCallStack): > error, called at lib/Data/GI/CodeGen/API.hs:201:16 in > haskell-gi-0.24.4-GhfHY0VJtr89rHNQ5kPVxX:Data.GI.CodeGen.API > make: *** [/usr/share/cdbs/1/class/hlibrary.mk:142: configure-ghc-stamp] > Error 1 The full build log is available from: http://qa-logs.debian.net/2020/09/26/haskell-gi-gobject_2.0.24-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: haskell-haskell-gi Source-Version: 0.24.4-2 Done: Ilias Tsitsimpis We believe that the bug you reported is fixed in the latest version of haskell-haskell-gi, 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 971...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ilias Tsitsimpis (supplier
Bug#971186: marked as done (haskell-gi-pango: FTBFS: Unknown GIR element "docsection" when processing namespace "GLib", aborting.)
Your message dated Mon, 28 Sep 2020 15:35:03 + with message-id and subject line Bug#971183: fixed in haskell-haskell-gi 0.24.4-2 has caused the Debian Bug report #971183, regarding haskell-gi-pango: FTBFS: Unknown GIR element "docsection" when processing namespace "GLib", aborting. 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.) -- 971183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-gi-pango Version: 1.0.23-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200926 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package haskell-gi-pango > dpkg-buildpackage: info: source version 1.0.23-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Ilias Tsitsimpis > > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > test -x debian/rules > dh_clean > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > clean_recipe > Running rm -rf dist dist-ghc dist-ghcjs dist-hugs debian/hlibrary.setup > Setup.hi Setup.ho Setup.o .\*config\* > Running rm -f configure-ghc-stamp configure-ghcjs-stamp build-ghc-stamp > build-ghcjs-stamp build-hugs-stamp build-haddock-stamp > Running rm -rf debian/tmp-inst-ghc debian/tmp-inst-ghcjs > Running rm -f debian/extra-depends-ghc debian/extra-depends-ghcjs > Running rm -f debian/hlibrary.Makefile > Running rm -rf debian/dh_haskell_shlibdeps > Running rm -rf debian/tmp-db > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building haskell-gi-pango using existing > ./haskell-gi-pango_1.0.23.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: building haskell-gi-pango in > haskell-gi-pango_1.0.23-1.debian.tar.xz > dpkg-source: info: building haskell-gi-pango in haskell-gi-pango_1.0.23-1.dsc > debian/rules binary > test -x debian/rules > dh_testroot > dh_prep > dh_installdirs -A > mkdir -p "." > CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85 > CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85 > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > make_setup_recipe > Running ghc --make Setup.hs -o debian/hlibrary.setup > [1 of 1] Compiling Main ( Setup.hs, Setup.o ) > Linking debian/hlibrary.setup ... > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > configure_recipe > Running debian/hlibrary.setup configure --ghc -v2 > --package-db=/var/lib/ghc/package.conf.d --prefix=/usr > --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib > --builddir=dist-ghc --ghc-option=-optl-Wl\,-z\,relro > --haddockdir=/usr/lib/ghc-doc/haddock/gi-pango-1.0.23/ --datasubdir=gi-pango > --htmldir=/usr/share/doc/libghc-gi-pango-doc/html/ --enable-library-profiling > Using Parsec parser > Unknown GIR element "docsection" when processing namespace "GLib", aborting. > CallStack (from HasCallStack): > error, called at lib/Data/GI/CodeGen/API.hs:201:16 in > haskell-gi-0.24.4-GhfHY0VJtr89rHNQ5kPVxX:Data.GI.CodeGen.API > make: *** [/usr/share/cdbs/1/class/hlibrary.mk:142: configure-ghc-stamp] > Error 1 The full build log is available from: http://qa-logs.debian.net/2020/09/26/haskell-gi-pango_1.0.23-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: haskell-haskell-gi Source-Version: 0.24.4-2 Done: Ilias Tsitsimpis We believe that the bug you reported is fixed in the latest version of haskell-haskell-gi, 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 971...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ilias Tsitsimpis (supplier of updated haskell-haskell-gi package)
Bug#971190: marked as done (haskell-gi-gtk: FTBFS: Unknown GIR element "docsection" when processing namespace "GLib", aborting.)
Your message dated Mon, 28 Sep 2020 15:35:03 + with message-id and subject line Bug#971183: fixed in haskell-haskell-gi 0.24.4-2 has caused the Debian Bug report #971183, regarding haskell-gi-gtk: FTBFS: Unknown GIR element "docsection" when processing namespace "GLib", aborting. 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.) -- 971183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-gi-gtk Version: 3.0.36-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200926 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package haskell-gi-gtk > dpkg-buildpackage: info: source version 3.0.36-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Ilias Tsitsimpis > > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > test -x debian/rules > dh_clean > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > clean_recipe > Running rm -rf dist dist-ghc dist-ghcjs dist-hugs debian/hlibrary.setup > Setup.hi Setup.ho Setup.o .\*config\* > Running rm -f configure-ghc-stamp configure-ghcjs-stamp build-ghc-stamp > build-ghcjs-stamp build-hugs-stamp build-haddock-stamp > Running rm -rf debian/tmp-inst-ghc debian/tmp-inst-ghcjs > Running rm -f debian/extra-depends-ghc debian/extra-depends-ghcjs > Running rm -f debian/hlibrary.Makefile > Running rm -rf debian/dh_haskell_shlibdeps > Running rm -rf debian/tmp-db > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building haskell-gi-gtk using existing > ./haskell-gi-gtk_3.0.36.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: building haskell-gi-gtk in > haskell-gi-gtk_3.0.36-1.debian.tar.xz > dpkg-source: info: building haskell-gi-gtk in haskell-gi-gtk_3.0.36-1.dsc > debian/rules binary > test -x debian/rules > dh_testroot > dh_prep > dh_installdirs -A > mkdir -p "." > CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85 > CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85 > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > make_setup_recipe > Running ghc --make Setup.hs -o debian/hlibrary.setup > [1 of 1] Compiling Main ( Setup.hs, Setup.o ) > Linking debian/hlibrary.setup ... > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > configure_recipe > Running debian/hlibrary.setup configure --ghc -v2 > --package-db=/var/lib/ghc/package.conf.d --prefix=/usr > --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib > --builddir=dist-ghc --ghc-option=-optl-Wl\,-z\,relro > --haddockdir=/usr/lib/ghc-doc/haddock/gi-gtk-3.0.36/ --datasubdir=gi-gtk > --htmldir=/usr/share/doc/libghc-gi-gtk-doc/html/ --enable-library-profiling > Using Parsec parser > Unknown GIR element "docsection" when processing namespace "GLib", aborting. > CallStack (from HasCallStack): > error, called at lib/Data/GI/CodeGen/API.hs:201:16 in > haskell-gi-0.24.4-GhfHY0VJtr89rHNQ5kPVxX:Data.GI.CodeGen.API > make: *** [/usr/share/cdbs/1/class/hlibrary.mk:142: configure-ghc-stamp] > Error 1 The full build log is available from: http://qa-logs.debian.net/2020/09/26/haskell-gi-gtk_3.0.36-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: haskell-haskell-gi Source-Version: 0.24.4-2 Done: Ilias Tsitsimpis We believe that the bug you reported is fixed in the latest version of haskell-haskell-gi, 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 971...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ilias Tsitsimpis (supplier of updated haskell-haskell-gi package) (This message was generated
Bug#971191: marked as done (haskell-gi-dbusmenu: FTBFS: Unknown GIR element "docsection" when processing namespace "GLib", aborting.)
Your message dated Mon, 28 Sep 2020 15:35:03 + with message-id and subject line Bug#971183: fixed in haskell-haskell-gi 0.24.4-2 has caused the Debian Bug report #971183, regarding haskell-gi-dbusmenu: FTBFS: Unknown GIR element "docsection" when processing namespace "GLib", aborting. 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.) -- 971183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-gi-dbusmenu Version: 0.4.8-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200926 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package haskell-gi-dbusmenu > dpkg-buildpackage: info: source version 0.4.8-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Ilias Tsitsimpis > > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > test -x debian/rules > dh_clean > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > clean_recipe > Running rm -rf dist dist-ghc dist-ghcjs dist-hugs debian/hlibrary.setup > Setup.hi Setup.ho Setup.o .\*config\* > Running rm -f configure-ghc-stamp configure-ghcjs-stamp build-ghc-stamp > build-ghcjs-stamp build-hugs-stamp build-haddock-stamp > Running rm -rf debian/tmp-inst-ghc debian/tmp-inst-ghcjs > Running rm -f debian/extra-depends-ghc debian/extra-depends-ghcjs > Running rm -f debian/hlibrary.Makefile > Running rm -rf debian/dh_haskell_shlibdeps > Running rm -rf debian/tmp-db > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building haskell-gi-dbusmenu using existing > ./haskell-gi-dbusmenu_0.4.8.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: building haskell-gi-dbusmenu in > haskell-gi-dbusmenu_0.4.8-1.debian.tar.xz > dpkg-source: info: building haskell-gi-dbusmenu in > haskell-gi-dbusmenu_0.4.8-1.dsc > debian/rules binary > test -x debian/rules > dh_testroot > dh_prep > dh_installdirs -A > mkdir -p "." > CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85 > CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85 > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > make_setup_recipe > Running ghc --make Setup.hs -o debian/hlibrary.setup > [1 of 1] Compiling Main ( Setup.hs, Setup.o ) > Linking debian/hlibrary.setup ... > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > configure_recipe > Running debian/hlibrary.setup configure --ghc -v2 > --package-db=/var/lib/ghc/package.conf.d --prefix=/usr > --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib > --builddir=dist-ghc --ghc-option=-optl-Wl\,-z\,relro > --haddockdir=/usr/lib/ghc-doc/haddock/gi-dbusmenu-0.4.8/ > --datasubdir=gi-dbusmenu > --htmldir=/usr/share/doc/libghc-gi-dbusmenu-doc/html/ > --enable-library-profiling > Using Parsec parser > Unknown GIR element "docsection" when processing namespace "GLib", aborting. > CallStack (from HasCallStack): > error, called at lib/Data/GI/CodeGen/API.hs:201:16 in > haskell-gi-0.24.4-GhfHY0VJtr89rHNQ5kPVxX:Data.GI.CodeGen.API > make: *** [/usr/share/cdbs/1/class/hlibrary.mk:142: configure-ghc-stamp] > Error 1 The full build log is available from: http://qa-logs.debian.net/2020/09/26/haskell-gi-dbusmenu_0.4.8-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: haskell-haskell-gi Source-Version: 0.24.4-2 Done: Ilias Tsitsimpis We believe that the bug you reported is fixed in the latest version of haskell-haskell-gi, 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 971...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ilias Tsitsimpis (supplier
Bug#971230: marked as done (haskell-gi-gdk: FTBFS: Unknown GIR element "docsection" when processing namespace "GLib", aborting.)
Your message dated Mon, 28 Sep 2020 15:35:03 + with message-id and subject line Bug#971183: fixed in haskell-haskell-gi 0.24.4-2 has caused the Debian Bug report #971183, regarding haskell-gi-gdk: FTBFS: Unknown GIR element "docsection" when processing namespace "GLib", aborting. 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.) -- 971183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-gi-gdk Version: 3.0.23-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200926 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package haskell-gi-gdk > dpkg-buildpackage: info: source version 3.0.23-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Ilias Tsitsimpis > > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > test -x debian/rules > dh_clean > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > clean_recipe > Running rm -rf dist dist-ghc dist-ghcjs dist-hugs debian/hlibrary.setup > Setup.hi Setup.ho Setup.o .\*config\* > Running rm -f configure-ghc-stamp configure-ghcjs-stamp build-ghc-stamp > build-ghcjs-stamp build-hugs-stamp build-haddock-stamp > Running rm -rf debian/tmp-inst-ghc debian/tmp-inst-ghcjs > Running rm -f debian/extra-depends-ghc debian/extra-depends-ghcjs > Running rm -f debian/hlibrary.Makefile > Running rm -rf debian/dh_haskell_shlibdeps > Running rm -rf debian/tmp-db > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building haskell-gi-gdk using existing > ./haskell-gi-gdk_3.0.23.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: building haskell-gi-gdk in > haskell-gi-gdk_3.0.23-1.debian.tar.xz > dpkg-source: info: building haskell-gi-gdk in haskell-gi-gdk_3.0.23-1.dsc > debian/rules binary > test -x debian/rules > dh_testroot > dh_prep > dh_installdirs -A > mkdir -p "." > CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85 > CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85 > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > make_setup_recipe > Running ghc --make Setup.hs -o debian/hlibrary.setup > [1 of 1] Compiling Main ( Setup.hs, Setup.o ) > Linking debian/hlibrary.setup ... > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > configure_recipe > Running debian/hlibrary.setup configure --ghc -v2 > --package-db=/var/lib/ghc/package.conf.d --prefix=/usr > --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib > --builddir=dist-ghc --ghc-option=-optl-Wl\,-z\,relro > --haddockdir=/usr/lib/ghc-doc/haddock/gi-gdk-3.0.23/ --datasubdir=gi-gdk > --htmldir=/usr/share/doc/libghc-gi-gdk-doc/html/ --enable-library-profiling > Using Parsec parser > Unknown GIR element "docsection" when processing namespace "GLib", aborting. > CallStack (from HasCallStack): > error, called at lib/Data/GI/CodeGen/API.hs:201:16 in > haskell-gi-0.24.4-GhfHY0VJtr89rHNQ5kPVxX:Data.GI.CodeGen.API > make: *** [/usr/share/cdbs/1/class/hlibrary.mk:142: configure-ghc-stamp] > Error 1 The full build log is available from: http://qa-logs.debian.net/2020/09/26/haskell-gi-gdk_3.0.23-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: haskell-haskell-gi Source-Version: 0.24.4-2 Done: Ilias Tsitsimpis We believe that the bug you reported is fixed in the latest version of haskell-haskell-gi, 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 971...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ilias Tsitsimpis (supplier of updated haskell-haskell-gi package) (This message was generated
Bug#971189: marked as done (haskell-gi-gdkpixbuf: FTBFS: Unknown GIR element "docsection" when processing namespace "GLib", aborting.)
Your message dated Mon, 28 Sep 2020 15:35:03 + with message-id and subject line Bug#971183: fixed in haskell-haskell-gi 0.24.4-2 has caused the Debian Bug report #971183, regarding haskell-gi-gdkpixbuf: FTBFS: Unknown GIR element "docsection" when processing namespace "GLib", aborting. 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.) -- 971183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-gi-gdkpixbuf Version: 2.0.24-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200926 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package haskell-gi-gdkpixbuf > dpkg-buildpackage: info: source version 2.0.24-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Ilias Tsitsimpis > > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > test -x debian/rules > dh_clean > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > clean_recipe > Running rm -rf dist dist-ghc dist-ghcjs dist-hugs debian/hlibrary.setup > Setup.hi Setup.ho Setup.o .\*config\* > Running rm -f configure-ghc-stamp configure-ghcjs-stamp build-ghc-stamp > build-ghcjs-stamp build-hugs-stamp build-haddock-stamp > Running rm -rf debian/tmp-inst-ghc debian/tmp-inst-ghcjs > Running rm -f debian/extra-depends-ghc debian/extra-depends-ghcjs > Running rm -f debian/hlibrary.Makefile > Running rm -rf debian/dh_haskell_shlibdeps > Running rm -rf debian/tmp-db > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building haskell-gi-gdkpixbuf using existing > ./haskell-gi-gdkpixbuf_2.0.24.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: building haskell-gi-gdkpixbuf in > haskell-gi-gdkpixbuf_2.0.24-1.debian.tar.xz > dpkg-source: info: building haskell-gi-gdkpixbuf in > haskell-gi-gdkpixbuf_2.0.24-1.dsc > debian/rules binary > test -x debian/rules > dh_testroot > dh_prep > dh_installdirs -A > mkdir -p "." > CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85 > CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85 > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > make_setup_recipe > Running ghc --make Setup.hs -o debian/hlibrary.setup > [1 of 1] Compiling Main ( Setup.hs, Setup.o ) > Linking debian/hlibrary.setup ... > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > configure_recipe > Running debian/hlibrary.setup configure --ghc -v2 > --package-db=/var/lib/ghc/package.conf.d --prefix=/usr > --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib > --builddir=dist-ghc --ghc-option=-optl-Wl\,-z\,relro > --haddockdir=/usr/lib/ghc-doc/haddock/gi-gdkpixbuf-2.0.24/ > --datasubdir=gi-gdkpixbuf > --htmldir=/usr/share/doc/libghc-gi-gdkpixbuf-doc/html/ > --enable-library-profiling > Using Parsec parser > Unknown GIR element "docsection" when processing namespace "GLib", aborting. > CallStack (from HasCallStack): > error, called at lib/Data/GI/CodeGen/API.hs:201:16 in > haskell-gi-0.24.4-GhfHY0VJtr89rHNQ5kPVxX:Data.GI.CodeGen.API > make: *** [/usr/share/cdbs/1/class/hlibrary.mk:142: configure-ghc-stamp] > Error 1 The full build log is available from: http://qa-logs.debian.net/2020/09/26/haskell-gi-gdkpixbuf_2.0.24-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: haskell-haskell-gi Source-Version: 0.24.4-2 Done: Ilias Tsitsimpis We believe that the bug you reported is fixed in the latest version of haskell-haskell-gi, 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 971...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ilias
Bug#971181: marked as done (haskell-gi-glib: FTBFS: Unknown GIR element "docsection" when processing namespace "GLib", aborting.)
Your message dated Mon, 28 Sep 2020 15:35:03 + with message-id and subject line Bug#971183: fixed in haskell-haskell-gi 0.24.4-2 has caused the Debian Bug report #971183, regarding haskell-gi-glib: FTBFS: Unknown GIR element "docsection" when processing namespace "GLib", aborting. 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.) -- 971183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-gi-glib Version: 2.0.24-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200926 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package haskell-gi-glib > dpkg-buildpackage: info: source version 2.0.24-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Ilias Tsitsimpis > > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > test -x debian/rules > dh_clean > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > clean_recipe > Running rm -rf dist dist-ghc dist-ghcjs dist-hugs debian/hlibrary.setup > Setup.hi Setup.ho Setup.o .\*config\* > Running rm -f configure-ghc-stamp configure-ghcjs-stamp build-ghc-stamp > build-ghcjs-stamp build-hugs-stamp build-haddock-stamp > Running rm -rf debian/tmp-inst-ghc debian/tmp-inst-ghcjs > Running rm -f debian/extra-depends-ghc debian/extra-depends-ghcjs > Running rm -f debian/hlibrary.Makefile > Running rm -rf debian/dh_haskell_shlibdeps > Running rm -rf debian/tmp-db > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building haskell-gi-glib using existing > ./haskell-gi-glib_2.0.24.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: building haskell-gi-glib in > haskell-gi-glib_2.0.24-1.debian.tar.xz > dpkg-source: info: building haskell-gi-glib in haskell-gi-glib_2.0.24-1.dsc > debian/rules binary > test -x debian/rules > dh_testroot > dh_prep > dh_installdirs -A > mkdir -p "." > CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85 > CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85 > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > make_setup_recipe > Running ghc --make Setup.hs -o debian/hlibrary.setup > [1 of 1] Compiling Main ( Setup.hs, Setup.o ) > Linking debian/hlibrary.setup ... > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > configure_recipe > Running debian/hlibrary.setup configure --ghc -v2 > --package-db=/var/lib/ghc/package.conf.d --prefix=/usr > --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib > --builddir=dist-ghc --ghc-option=-optl-Wl\,-z\,relro > --haddockdir=/usr/lib/ghc-doc/haddock/gi-glib-2.0.24/ --datasubdir=gi-glib > --htmldir=/usr/share/doc/libghc-gi-glib-doc/html/ --enable-library-profiling > Using Parsec parser > Unknown GIR element "docsection" when processing namespace "GLib", aborting. > CallStack (from HasCallStack): > error, called at lib/Data/GI/CodeGen/API.hs:201:16 in > haskell-gi-0.24.4-GhfHY0VJtr89rHNQ5kPVxX:Data.GI.CodeGen.API > make: *** [/usr/share/cdbs/1/class/hlibrary.mk:142: configure-ghc-stamp] > Error 1 The full build log is available from: http://qa-logs.debian.net/2020/09/26/haskell-gi-glib_2.0.24-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: haskell-haskell-gi Source-Version: 0.24.4-2 Done: Ilias Tsitsimpis We believe that the bug you reported is fixed in the latest version of haskell-haskell-gi, 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 971...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ilias Tsitsimpis (supplier of updated haskell-haskell-gi package) (This message
Bug#971196: marked as done (haskell-gi-gio: FTBFS: Unknown GIR element "docsection" when processing namespace "Gio", aborting.)
Your message dated Mon, 28 Sep 2020 15:35:03 + with message-id and subject line Bug#971183: fixed in haskell-haskell-gi 0.24.4-2 has caused the Debian Bug report #971183, regarding haskell-gi-gio: FTBFS: Unknown GIR element "docsection" when processing namespace "Gio", aborting. 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.) -- 971183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-gi-gio Version: 2.0.27-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200926 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package haskell-gi-gio > dpkg-buildpackage: info: source version 2.0.27-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Ilias Tsitsimpis > > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > test -x debian/rules > dh_clean > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > clean_recipe > Running rm -rf dist dist-ghc dist-ghcjs dist-hugs debian/hlibrary.setup > Setup.hi Setup.ho Setup.o .\*config\* > Running rm -f configure-ghc-stamp configure-ghcjs-stamp build-ghc-stamp > build-ghcjs-stamp build-hugs-stamp build-haddock-stamp > Running rm -rf debian/tmp-inst-ghc debian/tmp-inst-ghcjs > Running rm -f debian/extra-depends-ghc debian/extra-depends-ghcjs > Running rm -f debian/hlibrary.Makefile > Running rm -rf debian/dh_haskell_shlibdeps > Running rm -rf debian/tmp-db > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building haskell-gi-gio using existing > ./haskell-gi-gio_2.0.27.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: building haskell-gi-gio in > haskell-gi-gio_2.0.27-1.debian.tar.xz > dpkg-source: info: building haskell-gi-gio in haskell-gi-gio_2.0.27-1.dsc > debian/rules binary > test -x debian/rules > dh_testroot > dh_prep > dh_installdirs -A > mkdir -p "." > CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85 > CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85 > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > make_setup_recipe > Running ghc --make Setup.hs -o debian/hlibrary.setup > [1 of 1] Compiling Main ( Setup.hs, Setup.o ) > Linking debian/hlibrary.setup ... > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > configure_recipe > Running debian/hlibrary.setup configure --ghc -v2 > --package-db=/var/lib/ghc/package.conf.d --prefix=/usr > --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib > --builddir=dist-ghc --ghc-option=-optl-Wl\,-z\,relro > --haddockdir=/usr/lib/ghc-doc/haddock/gi-gio-2.0.27/ --datasubdir=gi-gio > --htmldir=/usr/share/doc/libghc-gi-gio-doc/html/ --enable-library-profiling > Using Parsec parser > Unknown GIR element "docsection" when processing namespace "Gio", aborting. > CallStack (from HasCallStack): > error, called at lib/Data/GI/CodeGen/API.hs:201:16 in > haskell-gi-0.24.4-GhfHY0VJtr89rHNQ5kPVxX:Data.GI.CodeGen.API > make: *** [/usr/share/cdbs/1/class/hlibrary.mk:142: configure-ghc-stamp] > Error 1 The full build log is available from: http://qa-logs.debian.net/2020/09/26/haskell-gi-gio_2.0.27-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: haskell-haskell-gi Source-Version: 0.24.4-2 Done: Ilias Tsitsimpis We believe that the bug you reported is fixed in the latest version of haskell-haskell-gi, 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 971...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ilias Tsitsimpis (supplier of updated haskell-haskell-gi package) (This message was generated
Bug#971198: marked as done (haskell-gi-dbusmenugtk3: FTBFS: Unknown GIR element "docsection" when processing namespace "GLib", aborting.)
Your message dated Mon, 28 Sep 2020 15:35:03 + with message-id and subject line Bug#971183: fixed in haskell-haskell-gi 0.24.4-2 has caused the Debian Bug report #971183, regarding haskell-gi-dbusmenugtk3: FTBFS: Unknown GIR element "docsection" when processing namespace "GLib", aborting. 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.) -- 971183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-gi-dbusmenugtk3 Version: 0.4.9-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200926 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package haskell-gi-dbusmenugtk3 > dpkg-buildpackage: info: source version 0.4.9-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Ilias Tsitsimpis > > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > test -x debian/rules > dh_clean > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > clean_recipe > Running rm -rf dist dist-ghc dist-ghcjs dist-hugs debian/hlibrary.setup > Setup.hi Setup.ho Setup.o .\*config\* > Running rm -f configure-ghc-stamp configure-ghcjs-stamp build-ghc-stamp > build-ghcjs-stamp build-hugs-stamp build-haddock-stamp > Running rm -rf debian/tmp-inst-ghc debian/tmp-inst-ghcjs > Running rm -f debian/extra-depends-ghc debian/extra-depends-ghcjs > Running rm -f debian/hlibrary.Makefile > Running rm -rf debian/dh_haskell_shlibdeps > Running rm -rf debian/tmp-db > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building haskell-gi-dbusmenugtk3 using existing > ./haskell-gi-dbusmenugtk3_0.4.9.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: building haskell-gi-dbusmenugtk3 in > haskell-gi-dbusmenugtk3_0.4.9-1.debian.tar.xz > dpkg-source: info: building haskell-gi-dbusmenugtk3 in > haskell-gi-dbusmenugtk3_0.4.9-1.dsc > debian/rules binary > test -x debian/rules > dh_testroot > dh_prep > dh_installdirs -A > mkdir -p "." > CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85 > CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85 > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > make_setup_recipe > Running ghc --make Setup.hs -o debian/hlibrary.setup > [1 of 1] Compiling Main ( Setup.hs, Setup.o ) > Linking debian/hlibrary.setup ... > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > configure_recipe > Running debian/hlibrary.setup configure --ghc -v2 > --package-db=/var/lib/ghc/package.conf.d --prefix=/usr > --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib > --builddir=dist-ghc --ghc-option=-optl-Wl\,-z\,relro > --haddockdir=/usr/lib/ghc-doc/haddock/gi-dbusmenugtk3-0.4.9/ > --datasubdir=gi-dbusmenugtk3 > --htmldir=/usr/share/doc/libghc-gi-dbusmenugtk3-doc/html/ > --enable-library-profiling > Using Parsec parser > Unknown GIR element "docsection" when processing namespace "GLib", aborting. > CallStack (from HasCallStack): > error, called at lib/Data/GI/CodeGen/API.hs:201:16 in > haskell-gi-0.24.4-GhfHY0VJtr89rHNQ5kPVxX:Data.GI.CodeGen.API > make: *** [/usr/share/cdbs/1/class/hlibrary.mk:142: configure-ghc-stamp] > Error 1 The full build log is available from: http://qa-logs.debian.net/2020/09/26/haskell-gi-dbusmenugtk3_0.4.9-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: haskell-haskell-gi Source-Version: 0.24.4-2 Done: Ilias Tsitsimpis We believe that the bug you reported is fixed in the latest version of haskell-haskell-gi, 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 971...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution
Bug#971202: marked as done (haskell-gi-gdkx11: FTBFS: Unknown GIR element "docsection" when processing namespace "GLib", aborting.)
Your message dated Mon, 28 Sep 2020 15:35:03 + with message-id and subject line Bug#971183: fixed in haskell-haskell-gi 0.24.4-2 has caused the Debian Bug report #971183, regarding haskell-gi-gdkx11: FTBFS: Unknown GIR element "docsection" when processing namespace "GLib", aborting. 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.) -- 971183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-gi-gdkx11 Version: 3.0.10-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200926 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package haskell-gi-gdkx11 > dpkg-buildpackage: info: source version 3.0.10-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Ilias Tsitsimpis > > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > test -x debian/rules > dh_clean > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > clean_recipe > Running rm -rf dist dist-ghc dist-ghcjs dist-hugs debian/hlibrary.setup > Setup.hi Setup.ho Setup.o .\*config\* > Running rm -f configure-ghc-stamp configure-ghcjs-stamp build-ghc-stamp > build-ghcjs-stamp build-hugs-stamp build-haddock-stamp > Running rm -rf debian/tmp-inst-ghc debian/tmp-inst-ghcjs > Running rm -f debian/extra-depends-ghc debian/extra-depends-ghcjs > Running rm -f debian/hlibrary.Makefile > Running rm -rf debian/dh_haskell_shlibdeps > Running rm -rf debian/tmp-db > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building haskell-gi-gdkx11 using existing > ./haskell-gi-gdkx11_3.0.10.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: building haskell-gi-gdkx11 in > haskell-gi-gdkx11_3.0.10-1.debian.tar.xz > dpkg-source: info: building haskell-gi-gdkx11 in > haskell-gi-gdkx11_3.0.10-1.dsc > debian/rules binary > test -x debian/rules > dh_testroot > dh_prep > dh_installdirs -A > mkdir -p "." > CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85 > CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85 > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > make_setup_recipe > Running ghc --make Setup.hs -o debian/hlibrary.setup > [1 of 1] Compiling Main ( Setup.hs, Setup.o ) > Linking debian/hlibrary.setup ... > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > configure_recipe > Running debian/hlibrary.setup configure --ghc -v2 > --package-db=/var/lib/ghc/package.conf.d --prefix=/usr > --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib > --builddir=dist-ghc --ghc-option=-optl-Wl\,-z\,relro > --haddockdir=/usr/lib/ghc-doc/haddock/gi-gdkx11-3.0.10/ > --datasubdir=gi-gdkx11 --htmldir=/usr/share/doc/libghc-gi-gdkx11-doc/html/ > --enable-library-profiling > Using Parsec parser > Unknown GIR element "docsection" when processing namespace "GLib", aborting. > CallStack (from HasCallStack): > error, called at lib/Data/GI/CodeGen/API.hs:201:16 in > haskell-gi-0.24.4-GhfHY0VJtr89rHNQ5kPVxX:Data.GI.CodeGen.API > make: *** [/usr/share/cdbs/1/class/hlibrary.mk:142: configure-ghc-stamp] > Error 1 The full build log is available from: http://qa-logs.debian.net/2020/09/26/haskell-gi-gdkx11_3.0.10-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: haskell-haskell-gi Source-Version: 0.24.4-2 Done: Ilias Tsitsimpis We believe that the bug you reported is fixed in the latest version of haskell-haskell-gi, 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 971...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ilias Tsitsimpis (supplier of updated
Bug#971219: marked as done (haskell-gi-vte: FTBFS: Unknown GIR element "docsection" when processing namespace "GLib", aborting.)
Your message dated Mon, 28 Sep 2020 15:35:03 + with message-id and subject line Bug#971183: fixed in haskell-haskell-gi 0.24.4-2 has caused the Debian Bug report #971183, regarding haskell-gi-vte: FTBFS: Unknown GIR element "docsection" when processing namespace "GLib", aborting. 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.) -- 971183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-gi-vte Version: 2.91.27-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200926 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package haskell-gi-vte > dpkg-buildpackage: info: source version 2.91.27-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Ilias Tsitsimpis > > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > test -x debian/rules > dh_clean > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > clean_recipe > Running rm -rf dist dist-ghc dist-ghcjs dist-hugs debian/hlibrary.setup > Setup.hi Setup.ho Setup.o .\*config\* > Running rm -f configure-ghc-stamp configure-ghcjs-stamp build-ghc-stamp > build-ghcjs-stamp build-hugs-stamp build-haddock-stamp > Running rm -rf debian/tmp-inst-ghc debian/tmp-inst-ghcjs > Running rm -f debian/extra-depends-ghc debian/extra-depends-ghcjs > Running rm -f debian/hlibrary.Makefile > Running rm -rf debian/dh_haskell_shlibdeps > Running rm -rf debian/tmp-db > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building haskell-gi-vte using existing > ./haskell-gi-vte_2.91.27.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: building haskell-gi-vte in > haskell-gi-vte_2.91.27-1.debian.tar.xz > dpkg-source: info: building haskell-gi-vte in haskell-gi-vte_2.91.27-1.dsc > debian/rules binary > test -x debian/rules > dh_testroot > dh_prep > dh_installdirs -A > mkdir -p "." > CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85 > CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85 > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > make_setup_recipe > Running ghc --make Setup.hs -o debian/hlibrary.setup > [1 of 1] Compiling Main ( Setup.hs, Setup.o ) > Linking debian/hlibrary.setup ... > . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ > configure_recipe > Running debian/hlibrary.setup configure --ghc -v2 > --package-db=/var/lib/ghc/package.conf.d --prefix=/usr > --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib > --builddir=dist-ghc --ghc-option=-optl-Wl\,-z\,relro > --haddockdir=/usr/lib/ghc-doc/haddock/gi-vte-2.91.27/ --datasubdir=gi-vte > --htmldir=/usr/share/doc/libghc-gi-vte-doc/html/ --enable-library-profiling > Using Parsec parser > Unknown GIR element "docsection" when processing namespace "GLib", aborting. > CallStack (from HasCallStack): > error, called at lib/Data/GI/CodeGen/API.hs:201:16 in > haskell-gi-0.24.4-GhfHY0VJtr89rHNQ5kPVxX:Data.GI.CodeGen.API > make: *** [/usr/share/cdbs/1/class/hlibrary.mk:142: configure-ghc-stamp] > Error 1 The full build log is available from: http://qa-logs.debian.net/2020/09/26/haskell-gi-vte_2.91.27-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: haskell-haskell-gi Source-Version: 0.24.4-2 Done: Ilias Tsitsimpis We believe that the bug you reported is fixed in the latest version of haskell-haskell-gi, 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 971...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ilias Tsitsimpis (supplier of updated haskell-haskell-gi package) (This message was
Bug#971267: haskell-ncurses: Removal notice: broken and unmaintained
Source: haskell-ncurses Version: 0.2.16-4 Severity: grave Justification: renders package unusable This package seems to be unmaintained (last upstream upload in 2016). It does not build with newer ncurses (see Bug#971187), is not part of Stackage and has no rev dependencies. I intend to remove this package. -- Ilias
Bug#944169: open-ath9k-htc-firmware: non-standard gcc/g++ used for build (gcc-8)
Hello, It should be possible to build the package with patched gcc-10 now: https://github.com/qca/open-ath9k-htc-firmware/pull/164 Michel Le Bihan
Processed: reassign 971183 to haskell-haskell-gi, reassign 971191 to haskell-haskell-gi ..., affects 971183 ...
Processing commands for cont...@bugs.debian.org: > reassign 971183 haskell-haskell-gi 0.24.4-1 Bug #971183 [src:haskell-gi-atk] haskell-gi-atk: FTBFS: Unknown GIR element "docsection" when processing namespace "GLib", aborting. Bug reassigned from package 'src:haskell-gi-atk' to 'haskell-haskell-gi'. No longer marked as found in versions haskell-gi-atk/2.0.22-1. Ignoring request to alter fixed versions of bug #971183 to the same values previously set Bug #971183 [haskell-haskell-gi] haskell-gi-atk: FTBFS: Unknown GIR element "docsection" when processing namespace "GLib", aborting. There is no source info for the package 'haskell-haskell-gi' at version '0.24.4-1' with architecture '' Unable to make a source version for version '0.24.4-1' Marked as found in versions 0.24.4-1. > reassign 971191 haskell-haskell-gi 0.24.4-1 Bug #971191 [src:haskell-gi-dbusmenu] haskell-gi-dbusmenu: FTBFS: Unknown GIR element "docsection" when processing namespace "GLib", aborting. Bug reassigned from package 'src:haskell-gi-dbusmenu' to 'haskell-haskell-gi'. No longer marked as found in versions haskell-gi-dbusmenu/0.4.8-1. Ignoring request to alter fixed versions of bug #971191 to the same values previously set Bug #971191 [haskell-haskell-gi] haskell-gi-dbusmenu: FTBFS: Unknown GIR element "docsection" when processing namespace "GLib", aborting. There is no source info for the package 'haskell-haskell-gi' at version '0.24.4-1' with architecture '' Unable to make a source version for version '0.24.4-1' Marked as found in versions 0.24.4-1. > reassign 971198 haskell-haskell-gi 0.24.4-1 Bug #971198 [src:haskell-gi-dbusmenugtk3] haskell-gi-dbusmenugtk3: FTBFS: Unknown GIR element "docsection" when processing namespace "GLib", aborting. Bug reassigned from package 'src:haskell-gi-dbusmenugtk3' to 'haskell-haskell-gi'. No longer marked as found in versions haskell-gi-dbusmenugtk3/0.4.9-1. Ignoring request to alter fixed versions of bug #971198 to the same values previously set Bug #971198 [haskell-haskell-gi] haskell-gi-dbusmenugtk3: FTBFS: Unknown GIR element "docsection" when processing namespace "GLib", aborting. There is no source info for the package 'haskell-haskell-gi' at version '0.24.4-1' with architecture '' Unable to make a source version for version '0.24.4-1' Marked as found in versions 0.24.4-1. > reassign 971230 haskell-haskell-gi 0.24.4-1 Bug #971230 [src:haskell-gi-gdk] haskell-gi-gdk: FTBFS: Unknown GIR element "docsection" when processing namespace "GLib", aborting. Bug reassigned from package 'src:haskell-gi-gdk' to 'haskell-haskell-gi'. No longer marked as found in versions haskell-gi-gdk/3.0.23-1. Ignoring request to alter fixed versions of bug #971230 to the same values previously set Bug #971230 [haskell-haskell-gi] haskell-gi-gdk: FTBFS: Unknown GIR element "docsection" when processing namespace "GLib", aborting. There is no source info for the package 'haskell-haskell-gi' at version '0.24.4-1' with architecture '' Unable to make a source version for version '0.24.4-1' Marked as found in versions 0.24.4-1. > reassign 971189 haskell-haskell-gi 0.24.4-1 Bug #971189 [src:haskell-gi-gdkpixbuf] haskell-gi-gdkpixbuf: FTBFS: Unknown GIR element "docsection" when processing namespace "GLib", aborting. Bug reassigned from package 'src:haskell-gi-gdkpixbuf' to 'haskell-haskell-gi'. No longer marked as found in versions haskell-gi-gdkpixbuf/2.0.24-1. Ignoring request to alter fixed versions of bug #971189 to the same values previously set Bug #971189 [haskell-haskell-gi] haskell-gi-gdkpixbuf: FTBFS: Unknown GIR element "docsection" when processing namespace "GLib", aborting. There is no source info for the package 'haskell-haskell-gi' at version '0.24.4-1' with architecture '' Unable to make a source version for version '0.24.4-1' Marked as found in versions 0.24.4-1. > reassign 971202 haskell-haskell-gi 0.24.4-1 Bug #971202 [src:haskell-gi-gdkx11] haskell-gi-gdkx11: FTBFS: Unknown GIR element "docsection" when processing namespace "GLib", aborting. Bug reassigned from package 'src:haskell-gi-gdkx11' to 'haskell-haskell-gi'. No longer marked as found in versions haskell-gi-gdkx11/3.0.10-1. Ignoring request to alter fixed versions of bug #971202 to the same values previously set Bug #971202 [haskell-haskell-gi] haskell-gi-gdkx11: FTBFS: Unknown GIR element "docsection" when processing namespace "GLib", aborting. There is no source info for the package 'haskell-haskell-gi' at version '0.24.4-1' with architecture '' Unable to make a source version for version '0.24.4-1' Marked as found in versions 0.24.4-1. > reassign 971196 haskell-haskell-gi 0.24.4-1 Bug #971196 [src:haskell-gi-gio] haskell-gi-gio: FTBFS: Unknown GIR element "docsection" when processing namespace "Gio", aborting. Bug reassigned from package 'src:haskell-gi-gio' to 'haskell-haskell-gi'. No longer marked as found in versions haskell-gi-gio/2.0.27-1. Ignoring request to alter fixed versions of bug #971196 to the same values
Bug#971236: marked as done (src:r-cran-fs: fails to migrate to testing for too long: autopkgtest regression)
Your message dated Mon, 28 Sep 2020 15:05:02 + with message-id and subject line Bug#971236: fixed in r-cran-fs 1.5.0+dfsg-1 has caused the Debian Bug report #971236, regarding src:r-cran-fs: fails to migrate to testing for too long: autopkgtest regression 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.) -- 971236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971236 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: r-cran-fs Version: 1.4.1+dfsg-1 Severity: serious Control: close -1 1.4.2+dfsg-1 Tags: sid bullseye 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:r-cran-fs in its current version in unstable has been trying to migrate for 60 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. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=r-cran-fs signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: r-cran-fs Source-Version: 1.5.0+dfsg-1 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of r-cran-fs, 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 971...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated r-cran-fs 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, 28 Sep 2020 16:29:32 +0200 Source: r-cran-fs Architecture: source Version: 1.5.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian R Packages Maintainers Changed-By: Andreas Tille Closes: 971236 Changes: r-cran-fs (1.5.0+dfsg-1) unstable; urgency=medium . * New upstream version (exclude any version of libuv) * Test-Depends: r-cran-vctrs, r-cran-tibble, r-cran-pillar, r-cran-crayon, r-cran-knitr, r-cran-withr, r-cran-covr, r-cran-rmarkdown * Rewrite run-unit-test script Closes: #971236 Checksums-Sha1: 3e375796ee3d2cc31b9ef91337c397db76d56a6b 2204 r-cran-fs_1.5.0+dfsg-1.dsc 9657495ec05668d7ea8525c077fc5f1148c171a9 77176 r-cran-fs_1.5.0+dfsg.orig.tar.xz 0b632a55cb59b3de7ffaeff74c73a3dbafc483e7 3960 r-cran-fs_1.5.0+dfsg-1.debian.tar.xz 7a96fd293411e62a00d4136366cbdec1e38ba0b9 8816 r-cran-fs_1.5.0+dfsg-1_amd64.buildinfo Checksums-Sha256: 9aeeb429e8828c7993ae95ce5a8ad74cf37664247ab8735aa6b5ea37672447c0 2204 r-cran-fs_1.5.0+dfsg-1.dsc a0bb16fbea340b5d77d79abb02ce885b32837e548e56fc1a371a196b38744477 77176 r-cran-fs_1.5.0+dfsg.orig.tar.xz b5413aa00ae5ece836eee7f388f0da1c49c35c0bebd9a26ad4b0a9482850b6dd 3960 r-cran-fs_1.5.0+dfsg-1.debian.tar.xz be62c09baf97bbc5026762686f3ee5357f52f96724808fd6a01bd1a0780ea4b5 8816 r-cran-fs_1.5.0+dfsg-1_amd64.buildinfo Files: c3d01c7c6fc634b6eedf7b68d52f0d67 2204 gnu-r optional r-cran-fs_1.5.0+dfsg-1.dsc 3c4c39efd6699429b810729759dd1b64 77176 gnu-r optional r-cran-fs_1.5.0+dfsg.orig.tar.xz e79e81981f71b37d8e822f519dfa3ee9
Bug#969756: networkx breaks botch autopkgtest: KeyError: 'long'
Hi, On Mon, 07 Sep 2020 22:26:16 +0200 Johannes Schauer wrote: > I already have investigated the problem and filed a bug against networkx: > > https://github.com/networkx/networkx/issues/4188 > > As you can see I also already filed a pull request fixing the issue and > upstream accepted it in this commit: > > https://github.com/networkx/networkx/commit/2bfdee687d0db533555384f92ce3670d47c45aec > > So what has to happen next is either for the networkx 2.6 release to happen > (probably not any time soon) or that the networkx Debian maintainers > cherry-pick the commit into the Debian package. there has been no maintainer activity on this RC bug for three weeks. I can prepare an NMU for networkx with the patch from above commit if you like? Thanks! cheers, josch signature.asc Description: signature
Bug#970889: marked as done (lcl-units-2.0: missing Breaks+Replaces: lazarus-src-2.0 (<< 2.0.10+dfsg-3))
Your message dated Mon, 28 Sep 2020 14:42:58 + with message-id and subject line Bug#970889: fixed in lazarus 2.0.10+dfsg-4 has caused the Debian Bug report #970889, regarding lcl-units-2.0: missing Breaks+Replaces: lazarus-src-2.0 (<< 2.0.10+dfsg-3) 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.) -- 970889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970889 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lcl-units-2.0 Version: 2.0.10+dfsg-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../lcl-units-2.0_2.0.10+dfsg-3_amd64.deb ... Unpacking lcl-units-2.0 (2.0.10+dfsg-3) ... dpkg: error processing archive /var/cache/apt/archives/lcl-units-2.0_2.0.10+dfsg-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/lazarus/2.0.10/components/codetools/fpc.errore.msg', which is also in package lazarus-src-2.0 2.0.10+dfsg-2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/lcl-units-2.0_2.0.10+dfsg-3_amd64.deb cheers, Andreas lazarus-src-2.0=2.0.10+dfsg-2_lcl-units-2.0=2.0.10+dfsg-3.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: lazarus Source-Version: 2.0.10+dfsg-4 Done: Graham Inggs We believe that the bug you reported is fixed in the latest version of lazarus, 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 970...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Graham Inggs (supplier of updated lazarus package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 28 Sep 2020 14:07:21 + Source: lazarus Architecture: source Version: 2.0.10+dfsg-4 Distribution: unstable Urgency: medium Maintainer: Pascal Packaging Team Changed-By: Graham Inggs Closes: 970889 Changes: lazarus (2.0.10+dfsg-4) unstable; urgency=medium . * Team upload * Add Breaks and Replaces for moved file codetools/fpc.errore.msg (Closes: #970889) Checksums-Sha1: ca798b411ac567980ab1e9fa865274628173295f 3579 lazarus_2.0.10+dfsg-4.dsc 97857991e9130904382d3ac2fc63d0dd3d2d525b 72072 lazarus_2.0.10+dfsg-4.debian.tar.xz Checksums-Sha256: 8c1c4daa38cd0e94a0448a0489667b9324cc395121d7bcfc9babbae5f5d5e005 3579 lazarus_2.0.10+dfsg-4.dsc 450311d2b453c8ac8b07082ab48ebe561364afb5302b444c71c9ad250a6d529c 72072 lazarus_2.0.10+dfsg-4.debian.tar.xz Files: e6b24b57af605170d44c9b7116823021 3579 devel optional lazarus_2.0.10+dfsg-4.dsc ef130307437c1120a93368ca102cda11 72072 devel optional lazarus_2.0.10+dfsg-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAl9x79AACgkQr8/sjmac 4cIknhAAwiZoeh7M0Wkx5dSZxsZuW9DbPj9tE1IwL4ueMEXubLe1aoRl+pr3hIGy hjQocID3Yx5xKMLF+ZWLf8laf6atmpHTGsWfPvs2sEqA+iDoolDC9nY7xxPnV0du HWqxytWFWHaXntleaAxGK5hdc5qg4pWyGcZEIa/oJ28OcwhXj0ZZIOmYcvrbIK/H W8HwWbijUj8zXQmrbpp2FEkT3uzwg/nrbAYy9N92rXYMuL+puw4k8Ll59rq5eeFi qpQ7dHfJkVmuiNHoofb2FQronF0drGc6kspahBsov8ZA+74ycZWJeNJfPuThfh50 W1UMCmMhnKM0lzakavqU9wumLlNpyD6WgZjF+LzoVJUSZvOEhVdS+YM3LFUh3VGS mXx7pkbbpPtfCr7lgLszN2ajbcd0T++ZCDM22dzRFZo+ELtrGU//qQruPyoaMidK Jv8VtPHQVKAt7miFabLHPQbf/Lb7UZCdNlkd9DQo5K6Xm/34D7FFqfK+XXmF2ITD wHDmivfbBY/FFGJMHVoVzcmjZFTlpIllM3NJuKIYWFbnxrIiCZ21kw5UgOT9D492 OAf/4vcT6/mLz9fq0T7fnVHuO/luF5Er2c8BzHrDVtk7tjceXgsDH3mQu8jyzTQt WhFr/G9pCm7C1Fu0/soYkXxpLllkr5/D5S1R/ZQ+YVtwCRUsTCQ= =AP6g -END PGP SIGNATURE End Message ---
Bug#963640: Build fix for the new sphinx version
The attached patch fixes the issue
diff -Nru jansson-2.13.1/debian/changelog jansson-2.13.1/debian/changelog
--- jansson-2.13.1/debian/changelog 2020-06-28 14:46:50.0 +0200
+++ jansson-2.13.1/debian/changelog 2020-09-28 16:15:27.0 +0200
@@ -1,3 +1,11 @@
+jansson (2.13.1-2) unstable; urgency=medium
+
+ * debian/patches/git_new_sphinx.patch:
+- backport an upstream change to fix the build with sphinx3
+ (Closes: #963640)
+
+ -- Sebastien Bacher Mon, 28 Sep 2020 16:15:27 +0200
+
jansson (2.13.1-1) unstable; urgency=medium
* New upstream release (Closes: #963842)
diff -Nru jansson-2.13.1/debian/patches/git_new_sphinx.patch jansson-2.13.1/debian/patches/git_new_sphinx.patch
--- jansson-2.13.1/debian/patches/git_new_sphinx.patch 1970-01-01 01:00:00.0 +0100
+++ jansson-2.13.1/debian/patches/git_new_sphinx.patch 2020-09-28 13:15:48.0 +0200
@@ -0,0 +1,66 @@
+From 798d40c3f3e0700501de1588274b69e2b128ad7c Mon Sep 17 00:00:00 2001
+From: Pierce Lopez
+Date: Fri, 7 Aug 2020 01:54:45 -0400
+Subject: [PATCH] doc: convert refcounting directive to a class
+
+Directive functions are no longer supported in Sphinx-3.0
+but directive classes have been supported since early 1.x
+---
+ doc/ext/refcounting.py | 31 ---
+ 1 file changed, 20 insertions(+), 11 deletions(-)
+
+diff --git a/doc/ext/refcounting.py b/doc/ext/refcounting.py
+index bba26849..e72c481c 100644
+--- a/doc/ext/refcounting.py
b/doc/ext/refcounting.py
+@@ -24,8 +24,8 @@
+ """
+
+ from docutils import nodes
++from docutils.parsers.rst import Directive
+
+-class refcounting(nodes.emphasis): pass
+
+ def visit(self, node):
+ self.visit_emphasis(node)
+@@ -40,16 +40,25 @@ def html_depart(self, node):
+ self.body.append('')
+
+
+-def refcounting_directive(name, arguments, options, content, lineno,
+- content_offset, block_text, state, state_machine):
+-if arguments[0] == 'borrow':
+-text = 'Return value: Borrowed reference.'
+-elif arguments[0] == 'new':
+-text = 'Return value: New reference.'
+-else:
+-raise Error('Valid arguments: new, borrow')
++class refcounting(nodes.emphasis):
++pass
++
++class refcounting_directive(Directive):
++has_content = False
++required_arguments = 1
++optional_arguments = 0
++final_argument_whitespace = False
++
++def run(self):
++if self.arguments[0] == 'borrow':
++text = 'Return value: Borrowed reference.'
++elif self.arguments[0] == 'new':
++text = 'Return value: New reference.'
++else:
++raise Error('Valid arguments: new, borrow')
++
++return [refcounting(text, text)]
+
+-return [refcounting(text, text)]
+
+ def setup(app):
+ app.add_node(refcounting,
+@@ -57,4 +66,4 @@ def setup(app):
+ latex=(visit, depart),
+ text=(visit, depart),
+ man=(visit, depart))
+-app.add_directive('refcounting', refcounting_directive, 0, (1, 0, 0))
++app.add_directive('refcounting', refcounting_directive)
diff -Nru jansson-2.13.1/debian/patches/series jansson-2.13.1/debian/patches/series
--- jansson-2.13.1/debian/patches/series 1970-01-01 01:00:00.0 +0100
+++ jansson-2.13.1/debian/patches/series 2020-09-28 13:15:08.0 +0200
@@ -0,0 +1 @@
+git_new_sphinx.patch
Bug#970603: GeoIP database format
Control: severity -1 normal On Sat, Sep 19, 2020 at 07:33:39PM +0100, Dániel Fancsali wrote: > Confirmed: built from source with --enable-geoip=legacy and the issue is > gone. Yes, the legacy format is ... legacy. goacess in Debian is configured for the new format, on purpose. signature.asc Description: PGP signature
Processed: Re: Bug#970603: GeoIP database format
Processing control commands: > severity -1 normal Bug #970603 [goaccess] goaccess: Fails to read a completely fine GeoIP database Severity set to 'normal' from 'grave' -- 970603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970603 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 957045 ...
Processing commands for cont...@bugs.debian.org: > tags 957045 + patch Bug #957045 [src:bird] bird: ftbfs with GCC-10 Added tag(s) patch. > forwarded 957045 > https://bird.network.cz/pipermail/bird-users/2020-September/014891.html Bug #957045 [src:bird] bird: ftbfs with GCC-10 Set Bug forwarded-to-address to 'https://bird.network.cz/pipermail/bird-users/2020-September/014891.html'. > thanks Stopping processing here. Please contact me if you need assistance. -- 957045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957045 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#968023: marked as done (munin: Unversioned Python removal in sid/bullseye)
Your message dated Mon, 28 Sep 2020 12:49:05 + with message-id and subject line Bug#968023: fixed in munin 2.999.15-1 has caused the Debian Bug report #968023, regarding munin: Unversioned Python 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.) -- 968023: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968023 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: munin Version: 2.999.14-1 Severity: serious User: debian-pyt...@lists.debian.org Usertags: py2unversioned 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 We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. 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 --- Source: munin Source-Version: 2.999.15-1 Done: Holger Levsen We believe that the bug you reported is fixed in the latest version of munin, 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 968...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Holger Levsen (supplier of updated munin package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 28 Sep 2020 14:23:53 +0200 Source: munin Architecture: source Version: 2.999.15-1 Distribution: experimental Urgency: medium Maintainer: Munin Debian Maintainers Changed-By: Holger Levsen Closes: 968023 Changes: munin (2.999.15-1) experimental; urgency=medium . * New upstream release. - update debian/patches/disable-munin-limits.patch. - munin-node: add /usr/bin/munin-get, which is a simple tool for managing plugins from remote repositories. Not yet ship its manpage. - add build-dependency on libdevel-confess-perl and drop the python one. Closes: #968023 - munin-node and munin-run manpages have moved from section 1 to 8, adjust d/munin-node.manpages and d/munin-node.service accordingly. * Bump debhelper-compat to 13. Adjust d/rules override_dh_installdocs to use use --remaining-packages. * Bump standards version to 4.5.0, no changes needed. Checksums-Sha1: 4f038610e47b51e36d3faa6ab4ad1a905d9e519c 4774 munin_2.999.15-1.dsc de6039bc9b62999a66e79aff2c3b96d8d1446198 3196808 munin_2.999.15.orig.tar.gz 3be26edf62a95165633d83a21b71c3181efea0af 833 munin_2.999.15.orig.tar.gz.asc 4e375cb2e24a7db35cd6a12384127ba3f537916a 56640 munin_2.999.15-1.debian.tar.xz 6996443cdc24c292b629d2b5a727ff9b0e13780f 5390 munin_2.999.15-1_source.buildinfo Checksums-Sha256: d931b42ebe4d89812733200a63f9b8eb7e7bc6f99a948f170d11f50defeb037d 4774 munin_2.999.15-1.dsc 6c4c196b46c82a9b05903578b0cb3bdfa8d4ea8135cc85de8f89f3dda36c0bcf 3196808 munin_2.999.15.orig.tar.gz 9c02ba4a173e29d6874b4009e17b2c9a00d8a879cf361699cdd329e93dd6ed4e 833 munin_2.999.15.orig.tar.gz.asc ec14a715f47badfe22288834b068095fce58d314654654f5218014618c990706 56640 munin_2.999.15-1.debian.tar.xz 932947ad628c86382cb811cab02f79c92e9e83bd070df02efe92a21aff3ee300 5390 munin_2.999.15-1_source.buildinfo Files: 34cc24bb034ff1e28f26f3958170665f 4774 net optional munin_2.999.15-1.dsc 6b3ef05781e89df34192e6990609ce08 3196808 net optional munin_2.999.15.orig.tar.gz 1c5ec231895f854b12f401c11fed0feb 833 net optional munin_2.999.15.orig.tar.gz.asc f7d89d19a813befd02de1f9966a347a6 56640 net optional munin_2.999.15-1.debian.tar.xz 5c636fb14a0375d05ac76869fe14e557 5390 net optional
Bug#971264: mediawiki: ParseError after 1.27.7-1~deb9u4 upgrade (blame patch for User::pingLimiter)
tags 971264 + confirmed thanks On Mon, Sep 28, 2020 at 01:24:09PM +0100, carandraug wrote: > > Dear Maintainer, > > After the update to 1.27.7-1~deb9u4 (from 1.27.7-1~deb9u3), the mediawiki site > errors in all pages with: > > Exception encountered, of type "ParseError" > Thanks for the report. An update to fix this is being prepared and should be published later today. Regards, -Roberto -- Roberto C. Sánchez
Processed: Re: Bug#971264: mediawiki: ParseError after 1.27.7-1~deb9u4 upgrade (blame patch for User::pingLimiter)
Processing commands for cont...@bugs.debian.org: > tags 971264 + confirmed Bug #971264 [mediawiki] mediawiki: ParseError after 1.27.7-1~deb9u4 upgrade (blame patch for User::pingLimiter) Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 971264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971264 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#970356: assertion failed in vte_terminal_spawn_with_fds_async
Hello, is there a solution about this bug ? I can't downgrade libvte-2.91-0 0.60.3-1 Then, i'm very interested by a patch or new version. Thanks a lot for your help Pascal
Bug#971264: mediawiki: ParseError after 1.27.7-1~deb9u4 upgrade (blame patch for User::pingLimiter)
Package: mediawiki
Version: 1:1.27.7-1~deb9u4
Severity: grave
Justification: renders package unusable
Dear Maintainer,
After the update to 1.27.7-1~deb9u4 (from 1.27.7-1~deb9u3), the mediawiki site
errors in all pages with:
Exception encountered, of type "ParseError"
Enabling some debug messages, gives a bit more detail:
Exception encountered, of type "ParseError"
[a5b5213be767b7723077eae1] /w/ ParseError from line 1813 of
/usr/share/mediawiki/includes/user/User.php: syntax error, unexpected 'else'
(T_ELSE)
Backtrace:
#0 [internal function]: AutoLoader::autoload(string)
#1 /usr/share/mediawiki/includes/session/SessionBackend.php(125):
spl_autoload_call(string)
#2 /usr/share/mediawiki/includes/session/SessionManager.php(854):
MediaWiki\Session\SessionBackend->__construct(MediaWiki\Session\SessionId,
MediaWiki\Session\SessionInfo, CachedBagOStuff, MediaWiki\Logger\LegacyLogger,
integer)
#3 /usr/share/mediawiki/includes/session/SessionManager.php(301):
MediaWiki\Session\SessionManager->getSessionFromInfo(MediaWiki\Session\SessionInfo,
WebRequest)
#4 /usr/share/mediawiki/includes/session/SessionManager.php(235):
MediaWiki\Session\SessionManager->getEmptySessionInternal(WebRequest)
#5 /usr/share/mediawiki/includes/session/SessionManager.php(185):
MediaWiki\Session\SessionManager->getEmptySession(WebRequest)
#6 /usr/share/mediawiki/includes/WebRequest.php(700):
MediaWiki\Session\SessionManager->getSessionForRequest(WebRequest)
#7 /usr/share/mediawiki/includes/session/SessionManager.php(121):
WebRequest->getSession()
#8 /usr/share/mediawiki/includes/Setup.php(747):
MediaWiki\Session\SessionManager::getGlobalSession()
#9 /usr/share/mediawiki/includes/WebStart.php(137): require_once(string)
#10 /usr/share/mediawiki/index.php(40): require(string)
#11 {main}
Looking at User.php lines 1813, the whole thing looks odd. This comes from the
Debian patch "0009-User-pingLimiter-add-user-global-rate-limit-type.patch"
-- System Information:
Debian Release: 9.13
APT prefers oldstable
APT policy: (500, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-13-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages mediawiki depends on:
ii apache2 [httpd] 2.4.25-3+deb9u9
ii mediawiki-classes 1:1.27.7-1~deb9u4
ii mime-support3.60
ii php 1:7.0+49
ii php-common 1:49
ii php-mbstring1:7.0+49
ii php-mysql 1:7.0+49
ii php-xml 1:7.0+49
ii php7.0 [php]7.0.33-0+deb9u9
ii php7.0-mbstring [php-mbstring] 7.0.33-0+deb9u9
ii php7.0-mysql [php-mysqlnd] 7.0.33-0+deb9u9
ii php7.0-xml [php-xml]7.0.33-0+deb9u9
Versions of packages mediawiki recommends:
ii mariadb-server-10.1 [virtual-mysql-server] 10.1.45-0+deb9u1
ii php-curl1:7.0+49
ii php-intl1:7.0+49
ii php-wikidiff2 1.4.1-1
ii php7.0-cli [php-cli]7.0.33-0+deb9u9
ii php7.0-curl [php-curl] 7.0.33-0+deb9u9
ii php7.0-intl [php-intl] 7.0.33-0+deb9u9
ii python 2.7.13-2
Versions of packages mediawiki suggests:
pn clamav
pn hhvm
ii imagemagick 8:6.9.7.4+dfsg-11+deb9u10
ii imagemagick-6.q16 [imagemagick] 8:6.9.7.4+dfsg-11+deb9u10
ii memcached1.4.33-1+deb9u1
pn php-apcu
-- Configuration Files:
/etc/apache2/conf-available/mediawiki.conf changed [not included]
/etc/mediawiki/mediawiki.conf changed [not included]
-- no debconf information
Bug#971217: python-poppler-qt5: FTBFS: sip: Unable to find file "QtCore/QtCoremod.sip"
Hi Anthony! On Sun, Sep 27, 2020 at 09:11:13PM +0200, Lucas Nussbaum wrote: > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > Relevant part (hopefully): > > building 'popplerqt5' extension > > /usr/bin/sip -I /usr/share/sip -t POPPLER_V0_74_0 -c > > build/temp.linux-x86_64-3.8 -b build/temp.linux-x86_64-3.8/poppler-qt5.sbf > > -I /usr/share/sip/PyQt5 -n PyQt5.sip -t Qt_5_14_0 -t WS_X11 poppler-qt5.sip > > sip: Unable to find file "QtCore/QtCoremod.sip" I have ported this package to SIP 5 and committed my patch to git. Do you want to review and/or upload my changes, or I should go ahead with a team upload? -- Dmitry Shachnev signature.asc Description: PGP signature
Processed: Bug#971217 marked as pending in python-poppler-qt5
Processing control commands: > tag -1 pending Bug #971217 [src:python-poppler-qt5] python-poppler-qt5: FTBFS: sip: Unable to find file "QtCore/QtCoremod.sip" Added tag(s) pending. -- 971217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971217 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#971217: marked as pending in python-poppler-qt5
Control: tag -1 pending Hello, Bug #971217 in python-poppler-qt5 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-poppler-qt5/-/commit/c3a98980b72cfd77c9f3f13e08266d4440212b10 Build with sip5 instead of sip4. Closes: #964131, #971217. (this message was generated automatically) -- Greetings https://bugs.debian.org/971217
Processed: tagging 971134
Processing commands for cont...@bugs.debian.org: > tags 971134 + pending Bug #971134 [src:devscripts] devscripts: FTBFS: dh_auto_test: error: make -j4 test returned exit code 2 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 971134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971134 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 970580 is serious
Processing commands for cont...@bugs.debian.org: > severity 970580 serious Bug #970580 [licenseutils] licenseutils: Memory access error Severity set to 'serious' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 970580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970580 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#967137 marked as pending in gmidimonitor
Processing control commands: > tag -1 pending Bug #967137 [src:gmidimonitor] gmidimonitor: Unversioned Python removal in sid/bullseye Added tag(s) pending. -- 967137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967137 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#967137: marked as pending in gmidimonitor
Control: tag -1 pending Hello, Bug #967137 in gmidimonitor 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/multimedia-team/gmidimonitor/-/commit/b16abe24f947193117c1f99ad35652f41977df1f d/control, d/rules: use python3 for building (Closes: #967137, #943041) Signed-off-by: Dmitry Baryshkov (this message was generated automatically) -- Greetings https://bugs.debian.org/967137
Bug#970230: marked as done (freeipa FTBFS on non-nodejs architectures)
Your message dated Mon, 28 Sep 2020 10:33:38 + with message-id and subject line Bug#970230: fixed in freeipa 4.8.10-1 has caused the Debian Bug report #970230, regarding freeipa FTBFS on non-nodejs architectures 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.) -- 970230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970230 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: freeipa Version: 4.8.8-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=freeipa=sid ... dh_install -a dh_install: warning: Cannot find (any matches for) "etc/ipa/epn/expire_msg.template" (tried in ., debian/tmp) dh_install: warning: freeipa-client-epn missing files: etc/ipa/epn/expire_msg.template dh_install: warning: Cannot find (any matches for) "usr/lib/ipa/ipa-print-pac" (tried in ., debian/tmp) dh_install: warning: freeipa-client-epn missing files: usr/lib/ipa/ipa-print-pac dh_install: error: missing files, aborting make: *** [debian/rules:122: binary-arch] Error 25 --- End Message --- --- Begin Message --- Source: freeipa Source-Version: 4.8.10-1 Done: Timo Aaltonen We believe that the bug you reported is fixed in the latest version of freeipa, 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 970...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (supplier of updated freeipa package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 28 Sep 2020 13:12:26 +0300 Source: freeipa Architecture: source Version: 4.8.10-1 Distribution: unstable Urgency: medium Maintainer: Debian FreeIPA Team Changed-By: Timo Aaltonen Closes: 968428 970230 Launchpad-Bugs-Fixed: 1874568 Changes: freeipa (4.8.10-1) unstable; urgency=medium . * New upstream release. * control: Build freeipa-client-epn only where nodejs is available. (Closes: #970230) * install: ipa-print-pac belongs to the server instead of -client-epn. * control, pkcs11-openssl-for-bind.diff: Add support for bind 9.16. (LP: #1874568) * fix-chrony-service-name.diff: Map to correct chrony service name. (Closes: #968428) * freeipa-client-epn.install: Add epn.conf. Checksums-Sha1: 447886426871481644215968bbc1bdd165eadaab 3883 freeipa_4.8.10-1.dsc 3840fc003d4fd8dc9104b924d4346e3f41d35a3d 12688789 freeipa_4.8.10.orig.tar.gz fbf60ae2555db43ffd31cb385e6896c60dde8e81 287620 freeipa_4.8.10-1.debian.tar.xz b25f00d5dc21cdeff0be8b9c6dccfa1b4a79a75e 9222 freeipa_4.8.10-1_source.buildinfo Checksums-Sha256: 8983e564ac771a490259c8a5f54a5bd69afed470a15317ba9e2007c0f6a100a1 3883 freeipa_4.8.10-1.dsc 01e1d239e24c8841b1221c36d4fe50b7b4f165c022b888b8bdfb376fa55dc999 12688789 freeipa_4.8.10.orig.tar.gz 525a828e3e7881f48125921aafd7997e067ec0cba31920365d1bf3ec0fc8cf68 287620 freeipa_4.8.10-1.debian.tar.xz 02d6263edd340275bf6ef1b3be467b5ea4e3ef29f0635771a566dbaa45c7c523 9222 freeipa_4.8.10-1_source.buildinfo Files: 7f41f4d73dfd7e6a601e1c4804f9e7df 3883 net optional freeipa_4.8.10-1.dsc 4070a152b6560c02b439fdfe1afbd7e4 12688789 net optional freeipa_4.8.10.orig.tar.gz 40d523ba9e4af8563658c4d0d4f26cba 287620 net optional freeipa_4.8.10-1.debian.tar.xz ad9ad6cb79859e436f2a5be7f5b07409 9222 net optional freeipa_4.8.10-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAl9xtxgACgkQy3AxZaiJ hNxbvhAAqP6IIkEgWNJbH4V1rm5j/NfeyHWHj7aNWNAhZ/R0dzc898+AxtEiTqEJ zktnK4y6FgVJKWYoTQAtQCaTvLnBemPBgG4J8GVCc9SnPIKNs1396un/ns4rXdH6 LXfpuSeW4R9bzdh0OC+fXKzuX1H/RAopPf/vIslq9Mj+ZxOBMQbNqOYJaek0U93p 0r1hnyr9vKCvYCRnWr+9YrWZ26lJLovnc+p7XbOq64Fk3F7Xh64m1EktfNUuugHZ dX1z1hGZPDKQcjo6GZX6tkXqa/WA7X1/8HgAGzmb1KxZWpLDNT50OvvDucQZvf7f G8D5SnmJn6oW0v1R36RYo1CbB+FF9Ss2CEmSUxsNpDtiULCiWRxwpRQ0w221zxC+ XzA75GhWOQjcMMP0caFERdF5Opwyw07dJJ1DYb05cgEW2wNHx0sxxjzlwDVaqi0+ apOFWQdzWOsTNv6++j92yGASqDbxme2Ji4lHM6CyYt2QZqvXy2+QHCeG8yjB2D3s Vr65sdKPLcMe/SWVDog1iNu98qcXMDqzKYFWnh3vIKbsNlTbcOsCEkVwygZ233JW 2Z5sz3qM+1oxJ5eNbsrEg5ZGEnxzdSe/87RhhKZiBTvhtYDCqehfrtWkzAOK6T17 twnKa/huBcZdsZCW+R6kHafU8zWKk2tNCuED9qAyuuUvS+7QAxQ= =1Iul -END PGP SIGNATURE End Message ---
Bug#971138: marked as done (ionit: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.8 returned exit code 13)
Your message dated Mon, 28 Sep 2020 10:33:46 +
with message-id
and subject line Bug#971138: fixed in ionit 0.3.6-1
has caused the Debian Bug report #971138,
regarding ionit: FTBFS: dh_auto_test: error: pybuild --test -i python{version}
-p 3.8 returned exit code 13
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.)
--
971138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971138
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ionit
Version: 0.3.5-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200926 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 '/<>'
> dh_auto_build
> I: pybuild base:217: /usr/bin/python3 setup.py build
> running build
> running build_py
> copying ionit_plugin.py -> /<>/.pybuild/cpython3_3.8/build
> running build_scripts
> creating build
> creating build/scripts-3.8
> copying and adjusting ionit -> build/scripts-3.8
> changing mode of build/scripts-3.8/ionit from 644 to 755
> pandoc -s -t man ionit.1.md -o ionit.1
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:217: cd /<>/.pybuild/cpython3_3.8/build;
> python3.8 -m unittest discover -v -s /<>
> test_flake8 (tests.test_flake8.Flake8TestCase)
> Test: Run flake8 on Python source code ... Running following command:
> /usr/bin/python3.8 -m flake8 --max-line-length=99 /<>/ionit
> tests ionit_plugin.py /<>/setup.py
> ok
> test_collect_function (tests.test_ionit.TestCollectContext)
> Test: Run collect_context(["tests/config/function"]) ... ok
> test_collect_static_context (tests.test_ionit.TestCollectContext)
> Test: Run collect_context(["tests/config/static"]) ...
> /<>/ionit.py:128: YAMLLoadWarning: calling yaml.load() without
> Loader=... is deprecated, as the default Loader is unsafe. Please read
> https://msg.pyyaml.org/load for full details.
> file_context = yaml.load(config_file)
> ok
> test_configuration_file (tests.test_ionit.TestCollectContext)
> Test: Run collect_context(["tests/config/static/second.yaml"]) ... ok
> test_context_stacking (tests.test_ionit.TestCollectContext)
> Test: Run collect_context(["tests/config/stacking"]) ... ok
> test_empty_context (tests.test_ionit.TestCollectContext)
> Test: Run collect_context(["tests/config/empty-context"]) ... ok
> test_empty_python_file (tests.test_ionit.TestCollectContext)
> Test: Run collect_context(["tests/config/empty"]) ... ok
> test_ignoring_additional_files (tests.test_ionit.TestCollectContext)
> Test: Run collect_context(["tests/config/additional-file"]) ... ok
> test_invalid_json (tests.test_ionit.TestCollectContext)
> Test: Run collect_context(["tests/config/invalid-json"]) ... ok
> test_invalid_python (tests.test_ionit.TestCollectContext)
> Test: Run collect_context(["tests/config/invalid-python"]) ... ok
> test_invalid_yaml (tests.test_ionit.TestCollectContext)
> Test: Run collect_context(["tests/config/invalid-yaml"]) ... ok
> test_missing_directory (tests.test_ionit.TestCollectContext)
> Test: Non-existing context directory ... ok
> test_non_dict_context (tests.test_ionit.TestCollectContext)
> Test failure for collect_context(["tests/config/non-dict"]) ... ok
> test_python_module (tests.test_ionit.TestCollectContext)
> Test: Run collect_context(["tests/config/python"]) ... ok
> test_raise_exception (tests.test_ionit.TestCollectContext)
> Test failure for collect_context(["tests/config/exception"]) ... ok
> test_main_default_config (tests.test_ionit.TestMain)
> Test main() with default config ... 2020-09-27 11:27:41,520 ionit INFO:
> Loading Python module 'function' from
> '/<>/tests/config/function/function.py'...
> 2020-09-27 11:27:41,523 ionit INFO: Rendered
> '/<>/tests/template/function/Document.jinja' to
> '/<>/tests/template/function/Document'.
> ok
> test_main_static (tests.test_ionit.TestMain)
> Test main() with static context ... 2020-09-27 11:27:41,524 ionit INFO:
> Reading configuration file
> '/<>/tests/config/static/first.json'...
> 2020-09-27 11:27:41,524 ionit INFO: Reading configuration file
> '/<>/tests/config/static/second.yaml'...
> 2020-09-27 11:27:41,525 ionit INFO: Rendered
> '/<>/tests/template/static/counting.jinja' to
> '/<>/tests/template/static/counting'.
> ok
> test_attribution_error (tests.test_ionit.TestRendering)
> Test: Run render_templates("tests/template/attribution-error") ... ok
> test_missing_context (tests.test_ionit.TestRendering)
> Test: Missing context for
Processed: Re: Bug#971131: diffoscope: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13
Processing commands for cont...@bugs.debian.org:
> reassign 971131 black
Bug #971131 [src:diffoscope] diffoscope: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p 3.8 returned exit code 13
Bug reassigned from package 'src:diffoscope' to 'black'.
No longer marked as found in versions diffoscope/160.
Ignoring request to alter fixed versions of bug #971131 to the same values
previously set
> forcemerge 970901 971131
Bug #970901 [black] black: cannot run, "ModuleNotFoundError: No module named
'_black_version'"
Bug #971137 [black] grml2usb: FTBFS: ModuleNotFoundError: No module named
'_black_version'
Bug #971131 [black] diffoscope: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.8 returned exit code 13
Removed indication that 971131 affects diffoscope
Added indication that 971131 affects src:grml2usb
Marked as found in versions black/20.8b1-1.
Added tag(s) patch.
Bug #971137 [black] grml2usb: FTBFS: ModuleNotFoundError: No module named
'_black_version'
Merged 970901 971131 971137
> affects 971131 diffoscope
Bug #971131 [black] diffoscope: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.8 returned exit code 13
Bug #970901 [black] black: cannot run, "ModuleNotFoundError: No module named
'_black_version'"
Bug #971137 [black] grml2usb: FTBFS: ModuleNotFoundError: No module named
'_black_version'
Added indication that 971131 affects diffoscope
Added indication that 970901 affects diffoscope
Added indication that 971137 affects diffoscope
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
970901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970901
971131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971131
971137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971137
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#971131: diffoscope: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13
forcemerge 970901 971131 affects 971131 diffoscope thanks > Source: diffoscope > Version: 160 > Severity: serious > Justification: FTBFS on amd64 […] > > File "", line 219, in > > _call_with_frames_removed > > File "/usr/lib/python3/dist-packages/black/__init__.py", line 65, in > > > > from _black_version import version as __version__ > > ModuleNotFoundError: No module named '_black_version' This is #970901 in black. I actually provided a patch for this issue a few days ago, but no response from the maintainer yet. -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org chris-lamb.co.uk `-
Processed (with 1 error): Re: Bug#971131: diffoscope: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13
Processing commands for cont...@bugs.debian.org:
> forcemerge 970901 971131
Bug #970901 [black] black: cannot run, "ModuleNotFoundError: No module named
'_black_version'"
Bug #971137 [black] grml2usb: FTBFS: ModuleNotFoundError: No module named
'_black_version'
Unable to merge bugs because:
package of #971131 is 'src:diffoscope' not 'black'
Failed to forcibly merge 970901: Did not alter merged bugs.
> affects 971131 diffoscope
Bug #971131 [src:diffoscope] diffoscope: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p 3.8 returned exit code 13
Added indication that 971131 affects diffoscope
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
970901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970901
971131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971131
971137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971137
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#971225: marked as done (pyerfa: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13)
Your message dated Mon, 28 Sep 2020 10:04:26 +
with message-id
and subject line Bug#971225: fixed in pyerfa 1.7.0+ds-3
has caused the Debian Bug report #971225,
regarding pyerfa: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p 3.8 returned exit code 13
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.)
--
971225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971225
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyerfa
Version: 1.7.0+ds-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200926 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> === FAILURES
> ===
> ___ TestVersion.test_version
> ___
>
> self =
>
> def test_version(self):
> assert hasattr(erfa, '__version__')
> version = erfa.__version__
> assert version is erfa.version.version
> # Oops, we had the wrong version for quite a while...
> > assert (erfa.version.erfa_version == '1.6.0' and
> > version.startswith('1.7.0')
> or version.startswith(erfa.version.erfa_version))
> E AssertionError: assert (('1.7.1' == '1.6.0'
> E - 1.7.1
> E + 1.6.0) or False)
> E+ where False = 0x7fef2c703670>('1.7.1')
> E+where 0x7fef2c703670> = '1.7.0'.startswith
> E+and '1.7.1' = '/<>/.pybuild/cpython3_3.8_pyerfa/build/erfa/version.py'>.erfa_version
> E+ where '/<>/.pybuild/cpython3_3.8_pyerfa/build/erfa/version.py'> =
> erfa.version
>
> erfa/tests/test_erfa.py:42: AssertionError
> 1 failed, 24 passed, 1 skipped in 0.56 seconds
>
> E: pybuild pybuild:352: test: plugin distutils failed with: exit code=1: cd
> /<>/.pybuild/cpython3_3.8_pyerfa/build; python3.8 -m pytest
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8
> returned exit code 13
The full build log is available from:
http://qa-logs.debian.net/2020/09/26/pyerfa_1.7.0+ds-2_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: pyerfa
Source-Version: 1.7.0+ds-3
Done: Antonio Valentino
We believe that the bug you reported is fixed in the latest version of
pyerfa, 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 971...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Antonio Valentino (supplier of updated pyerfa
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 28 Sep 2020 06:57:46 +
Source: pyerfa
Architecture: source
Version: 1.7.0+ds-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Maintainers
Changed-By: Antonio Valentino
Closes: 971225
Changes:
pyerfa (1.7.0+ds-3) unstable; urgency=medium
.
* New 0002-Disable-tight-test-on-version.patch:
see also https://github.com/liberfa/pyerfa/issues/52.
Closes: #971225.
Checksums-Sha1:
b441cce5c2b45be9ce8c7d8bbd978d1b953dd400 2237 pyerfa_1.7.0+ds-3.dsc
8d143ffd34aec711c5a1e0d0ff70b575dac1419d 4856 pyerfa_1.7.0+ds-3.debian.tar.xz
Checksums-Sha256:
838e05bb4a7b0c98b459e5de422363dc7ac6a2e94a650a59ffdec25a59cdae29 2237
pyerfa_1.7.0+ds-3.dsc
bcc047c11d61dcfca38969b7622c545806c43bc6514a9510519a276a095608cd 4856
pyerfa_1.7.0+ds-3.debian.tar.xz
Files:
829d7667b6cc562209dc70938d9b330f 2237 python optional pyerfa_1.7.0+ds-3.dsc
c9217a47477f5a32f02b0c95586d4a2a 4856 python optional
pyerfa_1.7.0+ds-3.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAl9xr44ACgkQcRWv0HcQ
3PewsA/+PLJQX8aV/wYi3p+2QlWh2m6lV80D0JMZSiBQjg0h2OenibYerqBC8yTi
Bug#971244: nqp-data: Missing Breaks/Replaces headers: trying to overwrite '/usr/share/nqp/lib/MASTNodes.moarvm', which is also in package nqp 2020.06+dfsg-1
On Monday, 28 September 2020 03:44:46 CEST Axel Beckert wrote: > Looks as if Breaks and Replaces headers are missing in the nqp-data > package and that it takes over files from the old nqp package. Indeed. I'll fix this. Thanks for the heads-up. All the best Dod
Bug#966968: efp: FTBFS: efp.a65:line 89: 8000:Illegal segment error
Package: src:efp Followup-For: Bug #966968 asm_to_a65.pl translates efp.asm (DASM format) to efp.a65 (XA65 format). The related lines are: # "org FOO" ==> "*=FOO" s/\s*org\s+/*=/; and s/\s*SEG\.U\s+\w+/.zero/; s/\s*SEG\s+/./; They rewrite ; *** DATA SEGMENT SEG.U data org $ as ; *** DATA SEGMENT .zero *=$ The '.zero' line is rejected by xa65 2.3.11. There has probably been a change in the syntax described in http://www.floodgap.com/retrotech/xa/dists/xa-2.3.11.tar.gz /doc/fileformat.txt
Bug#963374: marked as done (node-regexpu-core: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1)
Your message dated Mon, 28 Sep 2020 08:48:24 +
with message-id
and subject line Bug#963374: fixed in node-regexpu-core 4.7.1-1
has caused the Debian Bug report #963374,
regarding node-regexpu-core: FTBFS: dh_auto_test: error: /bin/sh -ex
debian/tests/pkg-js/test 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.)
--
963374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963374
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-regexpu-core
Version: 4.7.0+ds-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mkdir data
> node scripts/iu-mappings.js
> Skipping 0x41 → 0x61 since /A/i.test('a') is already `true`.
> Skipping 0x42 → 0x62 since /B/i.test('b') is already `true`.
> Skipping 0x43 → 0x63 since /C/i.test('c') is already `true`.
> Skipping 0x44 → 0x64 since /D/i.test('d') is already `true`.
> Skipping 0x45 → 0x65 since /E/i.test('e') is already `true`.
> Skipping 0x46 → 0x66 since /F/i.test('f') is already `true`.
> Skipping 0x47 → 0x67 since /G/i.test('g') is already `true`.
> Skipping 0x48 → 0x68 since /H/i.test('h') is already `true`.
> Skipping 0x49 → 0x69 since /I/i.test('i') is already `true`.
> Skipping 0x4A → 0x6A since /J/i.test('j') is already `true`.
> Skipping 0x4B → 0x6B since /K/i.test('k') is already `true`.
> Skipping 0x4C → 0x6C since /L/i.test('l') is already `true`.
> Skipping 0x4D → 0x6D since /M/i.test('m') is already `true`.
> Skipping 0x4E → 0x6E since /N/i.test('n') is already `true`.
> Skipping 0x4F → 0x6F since /O/i.test('o') is already `true`.
> Skipping 0x50 → 0x70 since /P/i.test('p') is already `true`.
> Skipping 0x51 → 0x71 since /Q/i.test('q') is already `true`.
> Skipping 0x52 → 0x72 since /R/i.test('r') is already `true`.
> Skipping 0x53 → 0x73 since /S/i.test('s') is already `true`.
> Skipping 0x54 → 0x74 since /T/i.test('t') is already `true`.
> Skipping 0x55 → 0x75 since /U/i.test('u') is already `true`.
> Skipping 0x56 → 0x76 since /V/i.test('v') is already `true`.
> Skipping 0x57 → 0x77 since /W/i.test('w') is already `true`.
> Skipping 0x58 → 0x78 since /X/i.test('x') is already `true`.
> Skipping 0x59 → 0x79 since /Y/i.test('y') is already `true`.
> Skipping 0x5A → 0x7A since /Z/i.test('z') is already `true`.
> Skipping 0xB5 → 0x3BC since /\xB5/i.test('\u03BC') is already `true`.
> Skipping 0xC0 → 0xE0 since /\xC0/i.test('\xE0') is already `true`.
> Skipping 0xC1 → 0xE1 since /\xC1/i.test('\xE1') is already `true`.
> Skipping 0xC2 → 0xE2 since /\xC2/i.test('\xE2') is already `true`.
> Skipping 0xC3 → 0xE3 since /\xC3/i.test('\xE3') is already `true`.
> Skipping 0xC4 → 0xE4 since /\xC4/i.test('\xE4') is already `true`.
> Skipping 0xC5 → 0xE5 since /\xC5/i.test('\xE5') is already `true`.
> Skipping 0xC6 → 0xE6 since /\xC6/i.test('\xE6') is already `true`.
> Skipping 0xC7 → 0xE7 since /\xC7/i.test('\xE7') is already `true`.
> Skipping 0xC8 → 0xE8 since /\xC8/i.test('\xE8') is already `true`.
> Skipping 0xC9 → 0xE9 since /\xC9/i.test('\xE9') is already `true`.
> Skipping 0xCA → 0xEA since /\xCA/i.test('\xEA') is already `true`.
> Skipping 0xCB → 0xEB since /\xCB/i.test('\xEB') is already `true`.
> Skipping 0xCC → 0xEC since /\xCC/i.test('\xEC') is already `true`.
> Skipping 0xCD → 0xED since /\xCD/i.test('\xED') is already `true`.
> Skipping 0xCE → 0xEE since /\xCE/i.test('\xEE') is already `true`.
> Skipping 0xCF → 0xEF since /\xCF/i.test('\xEF') is already `true`.
> Skipping 0xD0 → 0xF0 since /\xD0/i.test('\xF0') is already `true`.
> Skipping 0xD1 → 0xF1 since /\xD1/i.test('\xF1') is already `true`.
> Skipping 0xD2 → 0xF2 since /\xD2/i.test('\xF2') is already `true`.
> Skipping 0xD3 → 0xF3 since /\xD3/i.test('\xF3') is already `true`.
> Skipping 0xD4 → 0xF4 since /\xD4/i.test('\xF4') is already `true`.
> Skipping 0xD5 → 0xF5 since /\xD5/i.test('\xF5') is already `true`.
> Skipping 0xD6 → 0xF6 since /\xD6/i.test('\xF6') is already `true`.
> Skipping 0xD8 → 0xF8 since /\xD8/i.test('\xF8') is already `true`.
> Skipping 0xD9 → 0xF9 since /\xD9/i.test('\xF9') is already `true`.
> Skipping 0xDA → 0xFA since /\xDA/i.test('\xFA') is already `true`.
> Skipping 0xDB → 0xFB since /\xDB/i.test('\xFB') is already `true`.
> Skipping 0xDC → 0xFC since /\xDC/i.test('\xFC') is already `true`.
> Skipping 0xDD → 0xFD since /\xDD/i.test('\xFD') is already `true`.
> Skipping 0xDE → 0xFE since /\xDE/i.test('\xFE') is
Bug#971258: snapper-gui: Cannot create configuration: DBusException: error.no_permissions
Package: snapper-gui Version: 0git.960a94834f-3 Severity: grave Justification: renders package unusable "Create configuration" gives a traceback on Debian Buster, so snapshots cannot be created and the program is of no use: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/snappergui/mainWindow.py", line 108, in on_create_config dialog.template) File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__ **keywords) File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: error.no_permissions: org.freedesktop.DBus.Error.Failed
Bug#963352: marked as done (ruby-redis: FTBFS: ERROR: Test "ruby2.7" failed.)
Your message dated Mon, 28 Sep 2020 08:34:38 + with message-id and subject line Bug#963352: fixed in ruby-redis 4.2.2-1 has caused the Debian Bug report #963352, regarding ruby-redis: FTBFS: ERROR: Test "ruby2.7" failed. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 963352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963352 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-redis Version: 4.1.2-4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200620 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ruby2.7 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Run tests for ruby2.7 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=. > GEM_PATH=/<>/debian/ruby-redis/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 > ruby2.7 -S rake -f debian/ruby-tests.rake > 20049:C 21 Jun 2020 07:34:15.426 # oO0OoO0OoO0Oo Redis is starting > oO0OoO0OoO0Oo > 20049:C 21 Jun 2020 07:34:15.426 # Redis version=6.0.5, bits=64, > commit=, modified=0, pid=20049, just started > 20049:C 21 Jun 2020 07:34:15.426 # Configuration loaded > 20051:C 21 Jun 2020 07:34:15.433 # oO0OoO0OoO0Oo Redis is starting > oO0OoO0OoO0Oo > 20051:C 21 Jun 2020 07:34:15.433 # Redis version=6.0.5, bits=64, > commit=, modified=0, pid=20051, just started > 20051:C 21 Jun 2020 07:34:15.433 # Configuration loaded > 20057:X 21 Jun 2020 07:34:15.440 # oO0OoO0OoO0Oo Redis is starting > oO0OoO0OoO0Oo > 20057:X 21 Jun 2020 07:34:15.440 # Redis version=6.0.5, bits=64, > commit=, modified=0, pid=20057, just started > 20057:X 21 Jun 2020 07:34:15.440 # Configuration loaded > 20064:X 21 Jun 2020 07:34:15.446 # oO0OoO0OoO0Oo Redis is starting > oO0OoO0OoO0Oo > 20064:X 21 Jun 2020 07:34:15.446 # Redis version=6.0.5, bits=64, > commit=, modified=0, pid=20064, just started > 20064:X 21 Jun 2020 07:34:15.446 # Configuration loaded > 20070:X 21 Jun 2020 07:34:15.453 # oO0OoO0OoO0Oo Redis is starting > oO0OoO0OoO0Oo > 20070:X 21 Jun 2020 07:34:15.453 # Redis version=6.0.5, bits=64, > commit=, modified=0, pid=20070, just started > 20070:X 21 Jun 2020 07:34:15.453 # Configuration loaded > 20076:C 21 Jun 2020 07:34:15.459 # oO0OoO0OoO0Oo Redis is starting > oO0OoO0OoO0Oo > 20076:C 21 Jun 2020 07:34:15.459 # Redis version=6.0.5, bits=64, > commit=, modified=0, pid=20076, just started > 20076:C 21 Jun 2020 07:34:15.459 # Configuration loaded > 20082:C 21 Jun 2020 07:34:15.465 # oO0OoO0OoO0Oo Redis is starting > oO0OoO0OoO0Oo > 20082:C 21 Jun 2020 07:34:15.465 # Redis version=6.0.5, bits=64, > commit=, modified=0, pid=20082, just started > 20082:C 21 Jun 2020 07:34:15.465 # Configuration loaded > 20088:C 21 Jun 2020 07:34:15.471 # oO0OoO0OoO0Oo Redis is starting > oO0OoO0OoO0Oo > 20088:C 21 Jun 2020 07:34:15.471 # Redis version=6.0.5, bits=64, > commit=, modified=0, pid=20088, just started > 20088:C 21 Jun 2020 07:34:15.472 # Configuration loaded > 20094:C 21 Jun 2020 07:34:15.478 # oO0OoO0OoO0Oo Redis is starting > oO0OoO0OoO0Oo > 20094:C 21 Jun 2020 07:34:15.478 # Redis version=6.0.5, bits=64, > commit=, modified=0, pid=20094, just started > 20094:C 21 Jun 2020 07:34:15.478 # Configuration loaded > 20100:C 21 Jun 2020 07:34:15.484 # oO0OoO0OoO0Oo Redis is starting > oO0OoO0OoO0Oo > 20100:C 21 Jun 2020 07:34:15.484 # Redis version=6.0.5, bits=64, > commit=, modified=0, pid=20100, just started > 20100:C 21 Jun 2020 07:34:15.484 # Configuration loaded > 20106:C 21 Jun 2020 07:34:15.490 # oO0OoO0OoO0Oo Redis is starting > oO0OoO0OoO0Oo > 20106:C 21 Jun 2020 07:34:15.490 # Redis version=6.0.5, bits=64, > commit=, modified=0, pid=20106, just started > 20106:C 21 Jun 2020 07:34:15.490 # Configuration loaded > /usr/bin/ruby2.7 -w -I"test" > "/usr/share/rubygems-integration/all/gems/rake-13.0.1/lib/rake/rake_test_loader.rb" > "test/bitpos_test.rb" "test/blocking_commands_test.rb" "test/client_test.rb" > "test/cluster_abnormal_state_test.rb" > "test/cluster_blocking_commands_test.rb" >
Bug#970662: Acknowledgement (mariadb-105: FTBFS on x32: operand size mismatch for `crc32')
After the upload of mariadb-10.5 1:10.5.5-1 the x32 build is still failing on this same error: /<>/storage/innobase/ut/ut0crc32.cc:167: Error: operand size mismatch for `crc32'
Bug#968893: marked as done (mariadb-10.3: FTBFS on alpha: relocation truncated to fit)
Your message dated Mon, 28 Sep 2020 10:32:29 +0300 with message-id and subject line Re: Bug#968893: Acknowledgement (mariadb-10.3: FTBFS on alpha: relocation truncated to fit) has caused the Debian Bug report #968893, regarding mariadb-10.3: FTBFS on alpha: relocation truncated to fit 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.) -- 968893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968893 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mariadb-10.3 Version: 1:10.3.13-1 Severity: serious Justification: fails to build from source User: debian-al...@lists.debian.org Usertags: alpha ftbfs The MariaDB Server package was building fine on alpha in version 1:10.3.12-2. However the next upload of 1:10.3.13-1 regressed it, and has been broken since. Before: https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.3=alpha=1%3A10.3.12-2=1548378207=0 After: https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.3=alpha=1%3A10.3.13-1=1551052198=0 Error: * [ 91%] Linking CXX executable mysql_embedded cd /<>/builddir/libmysqld/examples && /usr/bin/cmake -E cmake_link_script CMakeFiles/mysql_embedded.dir/link.txt --verbose=1 /usr/bin/alpha-linux-gnu-g++ -g -O2 -fdebug-prefix-map=/<>=. -specs=/usr/share/dpkg/pie-compile.specs -Wformat -Werror=format-security -pie -fPIC -Wl,-z,relro,-z,now -fstack-protector --param=ssp-buffer-size=4 -fno-rtti -O2 -g -static-libgcc -fno-omit-frame-pointer -fno-strict-aliasing -Wno-uninitialized -D_FORTIFY_SOURCE=2 -DDBUG_OFF -specs=/usr/share/dpkg/pie-link.specs -Wl,-z,relro -Wl,-z,now -Wl,--export-dynamic CMakeFiles/mysql_embedded.dir/__/__/client/completion_hash.cc.o CMakeFiles/mysql_embedded.dir/__/__/client/mysql.cc.o CMakeFiles/mysql_embedded.dir/__/__/client/readline.cc.o -o mysql_embedded -lpthread ../libmariadbd.a -lreadline -lcurses -lpthread -lz -lm -ldl -lpcre -lcrypt -laio -lsystemd /usr/bin/ld: ../libmariadbd.a(buf0buf.cc.o): in function `buf_resize_thread': ./builddir/storage/innobase/./storage/innobase/buf/buf0buf.cc:3171:(.text+0x124a0): relocation truncated to fit: ELF_LITERAL against `.text.unlikely' /usr/bin/ld: ../libmariadbd.a(buf0dblwr.cc.o): in function `buf_dblwr_check_block(buf_block_t const*) [clone .part.65]': ./builddir/storage/innobase/./storage/innobase/buf/buf0dblwr.cc:901:(.text+0x368): relocation truncated to fit: ELF_LITERAL against `.text.unlikely' /usr/bin/ld: ../libmariadbd.a(buf0flu.cc.o): in function `buf_flush_ready_for_replace(buf_page_t*)': ./builddir/storage/innobase/./storage/innobase/include/buf0buf.ic:379:(.text+0x1cd8): relocation truncated to fit: ELF_LITERAL against `.text.unlikely' /usr/bin/ld: ../libmariadbd.a(buf0flu.cc.o): in function `buf_flush_page_cleaner_coordinator': ./builddir/storage/innobase/./storage/innobase/buf/buf0flu.cc:3106:(.text+0xa630): relocation truncated to fit: ELF_LITERAL against `.text.unlikely' /usr/bin/ld: ./builddir/storage/innobase/./storage/innobase/buf/buf0flu.cc:3108:(.text+0xa65c): relocation truncated to fit: ELF_LITERAL against `.text.unlikely' /usr/bin/ld: ./builddir/storage/innobase/./storage/innobase/buf/buf0flu.cc:3098:(.text+0xa67c): relocation truncated to fit: ELF_LITERAL against `.text.unlikely' /usr/bin/ld: ./builddir/storage/innobase/./storage/innobase/buf/buf0flu.cc:3100:(.text+0xa6a8): relocation truncated to fit: ELF_LITERAL against `.text.unlikely' /usr/bin/ld: ./builddir/storage/innobase/./storage/innobase/buf/buf0flu.cc:3246:(.text+0xa9ec): relocation truncated to fit: ELF_LITERAL against `.text.unlikely' /usr/bin/ld: ./builddir/storage/innobase/./storage/innobase/buf/buf0flu.cc:3264:(.text+0xaa60): relocation truncated to fit: ELF_LITERAL against `.text.unlikely' /usr/bin/ld: ./builddir/storage/innobase/./storage/innobase/buf/buf0flu.cc:3340:(.text+0xab8c): relocation truncated to fit: ELF_LITERAL against `.text.unlikely' /usr/bin/ld: ./builddir/storage/innobase/./storage/innobase/buf/buf0flu.cc:3346:(.text+0xabc0): additional relocation overflows omitted from the output collect2: error: ld returned 1 exit status libmysqld/examples/CMakeFiles/mysqltest_embedded.dir/build.make:85: recipe for target 'libmysqld/examples/mysqltest_embedded' failed make[4]: *** [libmysqld/examples/mysqltest_embedded] Error 1 make[4]: Leaving directory '/<>/builddir' CMakeFiles/Makefile2:13043: recipe for target 'libmysqld/examples/CMakeFiles/mysqltest_embedded.dir/all' failed make[3]: *** [libmysqld/examples/CMakeFiles/mysqltest_embedded.dir/all] Error 2 * Something similar is also going on in mariadb-10.4 in
Bug#970663: marked as done (mariadb-10.5: FTBFS on ppc64: InnoDB: Trying to delete)
Your message dated Mon, 28 Sep 2020 10:26:45 +0300 with message-id and subject line Re: Bug#970663: Acknowledgement (mariadb-105: FTBFS on ppc64: InnoDB: Trying to delete tablespace 'test/bug21114_child' but there are 1 flushes and 0 pending i/o's on it) has caused the Debian Bug report #970663, regarding mariadb-10.5: FTBFS on ppc64: InnoDB: Trying to delete 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.) -- 970663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970663 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mariadb-10.3 Version: 1:10.5.5-1~exp1 Severity: serious Justification: fails to build from source User: debian-powe...@lists.debian.org Usertags: ppc64 After uploading the latest mariadb-10.5 I noticed it fails to build. However, mariadb-10.4 built just fine on ppc64. The failure is this test that fails: main.parser_bug21114_innodb 'innodb' w5 [ fail ] Found warnings/errors in server log file! Test ended at 2020-09-12 17:31:51 line 2020-09-12 17:31:19 8 [Warning] InnoDB: Trying to delete tablespace 'test/bug21114_child' but there are 1 flushes and 0 pending i/o's on it. ^ Found warnings in /<>/builddir/mysql-test/var/5/log/mysqld.1.err ok --- End Message --- --- Begin Message --- Version: 1:10.5.5-1 mariadb-10.5 built successfully in https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.5=ppc64=1%3A10.5.5-1=1601082702=0 so this seems to be fixed now.--- End Message ---
Processed: your mail
Processing commands for cont...@bugs.debian.org: > severity 971154 important Bug #971154 [golang-go] fever: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 github.com/DCSO/fever/cmd/fever github.com/DCSO/fever/cmd/fever/cmds github.com/DCSO/fever/db github.com/DCSO/fever/input github.com/DCSO/fever/processing github.com/DCSO/fever/stenosis/api github.com/DCSO/fever/stenosis/task github.com/DCSO/fever/types github.com/DCSO/fever/util returned exit code 2 Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 971154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971154 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#971132: marked as done (librasterlite2: FTBFS: ld: wmslite.o: undefined reference to symbol 'pthread_create@@GLIBC_2.2.5')
Your message dated Mon, 28 Sep 2020 07:03:33 + with message-id and subject line Bug#971132: fixed in librasterlite2 1.1.0~beta1-2 has caused the Debian Bug report #971132, regarding librasterlite2: FTBFS: ld: wmslite.o: undefined reference to symbol 'pthread_create@@GLIBC_2.2.5' 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.) -- 971132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971132 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: librasterlite2 Version: 1.1.0~beta1-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200926 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../libtool --tag=CC --mode=link gcc -I/usr/include/libpng16 > -I/usr/include/openjpeg-2.3 -I/usr/include/x86_64-linux-gnu > -I/usr/include/libxml2 -I/usr/include/uuid -I/usr/include/freetype2 > -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 > -I/usr/include/pixman-1 -I/usr/include/cairo -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 > -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -L../src -Wl,-z,relro -Wl,-z,now -o wmslite > wmslite.o -lpng16 -lz -lwebp -llzma -llz4 -lzstd -lopenjp2 -lcurl -lxml2 > -lfontconfig -lfreetype -lfreetype -lpixman-1 -lcairo -lspatialite > -lrasterlite2 -lminizip -lproj -lgeotiff -ltiff -lgif -ljpeg -lz -lsqlite3 > libtool: link: gcc -I/usr/include/libpng16 -I/usr/include/openjpeg-2.3 > -I/usr/include/x86_64-linux-gnu -I/usr/include/libxml2 -I/usr/include/uuid > -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 > -I/usr/include/libpng16 -I/usr/include/pixman-1 -I/usr/include/cairo > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 > -I/usr/include/libpng16 -g -O2 "-fdebug-prefix-map=/<>=." > -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z -Wl,relro > -Wl,-z -Wl,now -o .libs/wmslite wmslite.o -L../src -lpng16 -lwebp -llzma > -llz4 -lzstd -lopenjp2 -lcurl -lxml2 -lfontconfig -lfreetype -lpixman-1 > -lcairo -lspatialite /<>/src/.libs/librasterlite2.so -lminizip > /usr/lib/x86_64-linux-gnu/libproj.so -lgeotiff -ltiff -lgif -ljpeg -lz > /usr/lib/x86_64-linux-gnu/libsqlite3.so > /usr/bin/ld: wmslite.o: undefined reference to symbol > 'pthread_create@@GLIBC_2.2.5' > /usr/bin/ld: /lib/x86_64-linux-gnu/libpthread.so.0: error adding symbols: DSO > missing from command line > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/09/26/librasterlite2_1.1.0~beta1-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: librasterlite2 Source-Version: 1.1.0~beta1-2 Done: Bas Couwenberg We believe that the bug you reported is fixed in the latest version of librasterlite2, 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 971...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bas Couwenberg (supplier of updated librasterlite2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 28 Sep 2020 06:37:18 +0200 Source: librasterlite2 Architecture: source Version: 1.1.0~beta1-2 Distribution: unstable Urgency: medium Maintainer: Debian GIS Project Changed-By: Bas Couwenberg Closes: 971132 Changes: librasterlite2 (1.1.0~beta1-2) unstable; urgency=medium . * Add patch to use -pthread instead of -lpthread. (closes: #971132) * Update lintian overrides. Checksums-Sha1:
Bug#971145: marked as done (sfcgal: FTBFS: intersection_of_Polyhedra_3.h:1063:19: error: ‘Intersect_facets’ is not a member of ‘CGAL::internal’)
Your message dated Mon, 28 Sep 2020 06:48:40 + with message-id and subject line Bug#971145: fixed in sfcgal 1.3.8-1 has caused the Debian Bug report #971145, regarding sfcgal: FTBFS: intersection_of_Polyhedra_3.h:1063:19: error: ‘Intersect_facets’ is not a member of ‘CGAL::internal’ 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.) -- 971145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971145 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sfcgal Version: 1.3.7-4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200926 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ > -DBOOST_ALL_DYN_LINK -DBOOST_ALL_NO_LIB -DBOOST_ATOMIC_DYN_LINK > -DBOOST_CHRONO_DYN_LINK -DBOOST_FILESYSTEM_DYN_LINK > -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_SERIALIZATION_DYN_LINK > -DBOOST_SYSTEM_DYN_LINK -DBOOST_THREAD_DYN_LINK -DBOOST_TIMER_DYN_LINK > -DBOOST_UNIT_TEST_FRAMEWORK_DYN_LINK -DCGAL_USE_CORE=1 -DCGAL_USE_GMPXX=1 > -DSFCGAL_BUILD_SHARED -DSFCGAL_EXPORTS > -I/<>/obj-x86_64-linux-gnu/include > -I/<>/src/../CGAL_patches -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra > -Wno-long-long -pedantic -Wpointer-arith -Wcast-align -Wcast-qual > -Wno-overloaded-virtual -Wformat=2 -Winit-self -Wmissing-include-dirs > -Wwrite-strings -Wno-error=undef -O2 -g -DNDEBUG -fPIC -frounding-math > -std=gnu++14 -o CMakeFiles/SFCGAL.dir/algorithm/collect.cpp.o -c > /<>/src/algorithm/collect.cpp > In file included from > /<>/obj-x86_64-linux-gnu/include/SFCGAL/algorithm/area.h:24, > from /<>/src/algorithm/area.cpp:21: > /<>/obj-x86_64-linux-gnu/include/SFCGAL/Geometry.h:195:18: > warning: ‘template class std::auto_ptr’ is deprecated > [-Wdeprecated-declarations] > 195 | virtual std::auto_ptr< Geometry > boundary() const ; > | ^~~~ > In file included from /usr/include/c++/10/memory:83, > from /usr/include/boost/config/no_tr1/memory.hpp:21, > from /usr/include/boost/smart_ptr/shared_ptr.hpp:23, > from /usr/include/boost/shared_ptr.hpp:17, > from > /<>/obj-x86_64-linux-gnu/include/SFCGAL/Geometry.h:26, > from > /<>/obj-x86_64-linux-gnu/include/SFCGAL/algorithm/area.h:24, > from /<>/src/algorithm/area.cpp:21: > /usr/include/c++/10/bits/unique_ptr.h:57:28: note: declared here >57 | template class auto_ptr; > |^~~~ > In file included from > /<>/obj-x86_64-linux-gnu/include/SFCGAL/algorithm/collect.h:26, > from /<>/src/algorithm/collect.cpp:21: > /<>/obj-x86_64-linux-gnu/include/SFCGAL/Geometry.h:195:18: > warning: ‘template class std::auto_ptr’ is deprecated > [-Wdeprecated-declarations] > 195 | virtual std::auto_ptr< Geometry > boundary() const ; > | ^~~~ > In file included from /usr/include/c++/10/memory:83, > from /usr/include/boost/config/no_tr1/memory.hpp:21, > from /usr/include/boost/smart_ptr/shared_ptr.hpp:23, > from /usr/include/boost/shared_ptr.hpp:17, > from > /<>/obj-x86_64-linux-gnu/include/SFCGAL/Geometry.h:26, > from > /<>/obj-x86_64-linux-gnu/include/SFCGAL/algorithm/collect.h:26, > from /<>/src/algorithm/collect.cpp:21: > /usr/include/c++/10/bits/unique_ptr.h:57:28: note: declared here >57 | template class auto_ptr; > |^~~~ > In file included from /<>/src/algorithm/collect.cpp:21: > /<>/obj-x86_64-linux-gnu/include/SFCGAL/algorithm/collect.h:35:17: > warning: ‘template class std::auto_ptr’ is deprecated > [-Wdeprecated-declarations] >35 | SFCGAL_API std::auto_ptr collect( const Geometry& ga, const > Geometry& gb ); > | ^~~~ > In file included from /usr/include/c++/10/memory:83, > from /usr/include/boost/config/no_tr1/memory.hpp:21, > from /usr/include/boost/smart_ptr/shared_ptr.hpp:23, > from /usr/include/boost/shared_ptr.hpp:17, > from > /<>/obj-x86_64-linux-gnu/include/SFCGAL/Geometry.h:26, > from > /<>/obj-x86_64-linux-gnu/include/SFCGAL/algorithm/collect.h:26, > from
Processed: reopening 970901
Processing commands for cont...@bugs.debian.org:
> reopen 970901
Bug #970901 {Done: Michael Prokop } [black] black: cannot run,
"ModuleNotFoundError: No module named '_black_version'"
Bug #971137 {Done: Michael Prokop } [black] grml2usb: FTBFS:
ModuleNotFoundError: No module named '_black_version'
Bug reopened
Ignoring request to alter fixed versions of bug #970901 to the same values
previously set
Ignoring request to alter fixed versions of bug #971137 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
970901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970901
971137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971137
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#971137: marked as done (grml2usb: FTBFS: ModuleNotFoundError: No module named '_black_version')
Your message dated Mon, 28 Sep 2020 07:57:40 +0200
with message-id <2020-09-28t07-56...@devnull.michael-prokop.at>
and subject line Re: Bug#971137: grml2usb: FTBFS: ModuleNotFoundError: No
module named '_black_version'
has caused the Debian Bug report #971137,
regarding grml2usb: FTBFS: ModuleNotFoundError: No module named '_black_version'
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.)
--
971137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971137
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: grml2usb
Version: 0.18.3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200926 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> flake8 grml2usb
> isort --check-only grml2usb
> black --check grml2usb
> Traceback (most recent call last):
> File "/usr/lib/python3/dist-packages/black/__init__.py", line 63, in
>
> from black._black_version import version as __version__
> ModuleNotFoundError: No module named 'black._black_version'
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
> File "/usr/bin/black", line 33, in
> sys.exit(load_entry_point('black==20.8b1', 'console_scripts', 'black')())
> File "/usr/bin/black", line 25, in importlib_load_entry_point
> return next(matches).load()
> File "/usr/lib/python3.8/importlib/metadata.py", line 77, in load
> module = import_module(match.group('module'))
> File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> File "", line 1014, in _gcd_import
> File "", line 991, in _find_and_load
> File "", line 975, in _find_and_load_unlocked
> File "", line 671, in _load_unlocked
> File "", line 783, in exec_module
> File "", line 219, in _call_with_frames_removed
> File "/usr/lib/python3/dist-packages/black/__init__.py", line 65, in
>
> from _black_version import version as __version__
> ModuleNotFoundError: No module named '_black_version'
> make[2]: *** [Makefile:44: codecheck] Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/09/26/grml2usb_0.18.3_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 ---
Hi,
* Lucas Nussbaum [Sun Sep 27, 2020 at 08:45:00PM +0200]:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> Relevant part (hopefully):
[...]
> > black --check grml2usb
> > Traceback (most recent call last):
> > File "/usr/lib/python3/dist-packages/black/__init__.py", line 63, in
> >
> > from black._black_version import version as __version__
> > ModuleNotFoundError: No module named 'black._black_version'
[...]
Thanks for reporting, this is a bug in package black, see #970901.
I'm closing this one here for now (not being aware of a better
way how to handle this, tbh).
regards
-mika-
signature.asc
Description: Digital signature
--- End Message ---
Bug#970901: marked as done (black: cannot run, "ModuleNotFoundError: No module named '_black_version'")
Your message dated Mon, 28 Sep 2020 07:57:40 +0200
with message-id <2020-09-28t07-56...@devnull.michael-prokop.at>
and subject line Re: Bug#971137: grml2usb: FTBFS: ModuleNotFoundError: No
module named '_black_version'
has caused the Debian Bug report #971137,
regarding black: cannot run, "ModuleNotFoundError: No module named
'_black_version'"
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.)
--
971137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971137
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: black
Version: 20.8b1-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
The new black package version 20.8b1-1 seems to be missing some files:
% black
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/black/__init__.py", line 63, in
from black._black_version import version as __version__
ModuleNotFoundError: No module named 'black._black_version'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/bin/black", line 33, in
sys.exit(load_entry_point('black==20.8b1', 'console_scripts', 'black')())
File "/usr/bin/black", line 25, in importlib_load_entry_point
return next(matches).load()
File "/usr/lib/python3.8/importlib/metadata.py", line 77, in load
module = import_module(match.group('module'))
File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1014, in _gcd_import
File "", line 991, in _find_and_load
File "", line 975, in _find_and_load_unlocked
File "", line 671, in _load_unlocked
File "", line 783, in exec_module
File "", line 219, in _call_with_frames_removed
File "/usr/lib/python3/dist-packages/black/__init__.py", line 65, in
from _black_version import version as __version__
ModuleNotFoundError: No module named '_black_version'
Looking at the source, _black_version.py appears to be generated by the
setup.py:
https://github.com/psf/black/blob/master/setup.py#L50-L53
Regards,
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.8.0-2-amd64 (SMP w/8 CPU threads)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages black depends on:
ii python33.8.2-3
ii python3-appdirs1.4.4-1
ii python3-click 7.1.2-1
ii python3-mypy-extensions0.4.3-1
ii python3-pathspec 0.8.0-1
ii python3-pkg-resources 49.3.1-2
ii python3-regex 0.1.20200714-1
ii python3-toml 0.10.1-1
ii python3-typed-ast 1.4.1-1+b1
ii python3-typing-extensions 3.7.4.2-1
black recommends no packages.
Versions of packages black suggests:
pn python-black-doc
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,
* Lucas Nussbaum [Sun Sep 27, 2020 at 08:45:00PM +0200]:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> Relevant part (hopefully):
[...]
> > black --check grml2usb
> > Traceback (most recent call last):
> > File "/usr/lib/python3/dist-packages/black/__init__.py", line 63, in
> >
> > from black._black_version import version as __version__
> > ModuleNotFoundError: No module named 'black._black_version'
[...]
Thanks for reporting, this is a bug in package black, see #970901.
I'm closing this one here for now (not being aware of a better
way how to handle this, tbh).
regards
-mika-
signature.asc
Description: Digital signature
--- End Message ---
