Bug#943924: pandas2?
Matthias disagrees: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942106#73 It should be technically straightforward to make a pandas2 package (start from the debian-v023 branch and drop the python2 part), but you'd have to upload it because DMs can't upload NEW packages. (Only pandas would need to be split - our current statsmodels version still can support Python 2.)
Bug#940902: doesn't read the data
On Sun, Nov 10, 2019 at 05:32:48PM +0100, Ana Guerrero Lopez wrote: > > > > Welcome to the team, Andreas. > > Thanks! > Good news, I've tested and it works fine. I'm doing a team upload right now. > > I think we shouldn't give up in getting this ported to python3, but I think a > re-write keeping the possibility to read the all data is the best way to go. Thanks a lot for caring Andreas. -- http://fam-tille.de
Processed: retitle 944473 to build-dependency not satisfiable in sid
Processing commands for cont...@bugs.debian.org: > retitle 944473 build-dependency not satisfiable in sid Bug #944473 [src:botch] botch: build-dependency not satisfiable in sio Changed Bug title to 'build-dependency not satisfiable in sid' from 'botch: build-dependency not satisfiable in sio'. > thanks Stopping processing here. Please contact me if you need assistance. -- 944473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944473 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#941535: marked as done (libforms: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended)
Your message dated Mon, 11 Nov 2019 03:04:46 + with message-id and subject line Bug#941535: fixed in libforms 1.2.3-1.4 has caused the Debian Bug report #941535, regarding libforms: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 941535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941535 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libforms Version: 1.2.3-1.3 Severity: serious Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu eoan ubuntu-patch Hi Peter, The texlive-generic-recommended transitional package has been dropped from texlive-base in sid. Please update your build-dependency to texlive-plain-generic instead. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org diff -Nru libforms-1.2.3/debian/control libforms-1.2.3/debian/control --- libforms-1.2.3/debian/control 2016-08-23 22:30:18.0 -0700 +++ libforms-1.2.3/debian/control 2019-10-01 14:11:04.0 -0700 @@ -3,7 +3,7 @@ Priority: optional Maintainer: Peter S Galbraith Build-Depends: debhelper (>= 8.9.7~), dpkg (>= 1.15.4) | install-info, libxpm-dev, libjpeg-dev, libtiff-dev, libgl1-mesa-dev, libxext-dev, texinfo, dh-autoreconf -Build-Depends-Indep: texi2html, texlive-generic-recommended, texlive-latex-base, gsfonts +Build-Depends-Indep: texi2html, texlive-plain-generic, texlive-latex-base, gsfonts Standards-Version: 3.8.4 Homepage: http://savannah.nongnu.org/projects/xforms/ --- End Message --- --- Begin Message --- Source: libforms Source-Version: 1.2.3-1.4 We believe that the bug you reported is fixed in the latest version of libforms, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 941...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Wise (supplier of updated libforms 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, 11 Nov 2019 10:33:39 +0800 Source: libforms Architecture: source Version: 1.2.3-1.4 Distribution: unstable Urgency: medium Maintainer: Peter S Galbraith Changed-By: Paul Wise Closes: 941535 Changes: libforms (1.2.3-1.4) unstable; urgency=medium . * Non-maintainer upload. * Switch from texlive-generic-recommended to texlive-plain-generic (Closes: #941535) Checksums-Sha1: 3d02fddd8a38dd5c21e190f33c43f249b47aef78 2231 libforms_1.2.3-1.4.dsc e3dae6f8099f1a756af327a3b5f2b2afd5e0b728 5988 libforms_1.2.3-1.4.debian.tar.xz Checksums-Sha256: b97c32a50364e794468185c804edc8e03ac2b8cfde2c6a0346cc578da02c0dcf 2231 libforms_1.2.3-1.4.dsc 296b2fc1ab022f29ce3b93eccf74de607c6c21453f63e498d1d30148da01d119 5988 libforms_1.2.3-1.4.debian.tar.xz Files: a8545f23c6f06ebfd9d4d8cca8a0e803 2231 libs optional libforms_1.2.3-1.4.dsc 2734b803be614f5f30ab36707235192a 5988 libs optional libforms_1.2.3-1.4.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEYQsotVz8/kXqG1Y7MRa6Xp/6aaMFAl3IyYYACgkQMRa6Xp/6 aaPzKQ//QDKiPiqbUkofVB0dV5ySwGOloDv9wBee1/VDYyUaLuxYXS4NzZNFRJpg 0YuFMCChGWCLdn7+t4g3aHu28IMcPA17OV3IJM12iPqC1vMkqyWugijetfpQMdBM lHp2ENIr6yTTK5xC93O3ty06Gz5Xx2bdCmBmXcDYQb7dYgRJuCiIkq7Of8WO6mls KNk7eatErm7uGxacyj/1gDdckpsvu6SLE/lgPfghBW21ptKXo7tbU1uRWf/uAzlg NhTV+GPvM2pJ4cDEb3JMKyiErwr0MbPgX2E8S2RmdmjGj2vPFRq3xQBla6WfzAfQ iPoyMBH4J74h/D3k+WR4M0iW4lWNAtVgbXNa6wnUlVNZbzYr4a1dyhG/BYFmBTlA Pni3f6291tvSOoq6hTWfEMz/njhd04yZbEt+pvKqDFpCJTUQHqhh7NjDA7XLRXkl GuJJ1a3efdMiF6uTdTfILfFCK9xS92bxieKBMkRYSYkCpCKVxoHCEHMnUVToR43k MfWLUmriL9zqmaJo+6B37wLjxbbJ1Z7LdAZ1ynoYrkmrh7fYDiJ7CFlsIodvPXwW lN6Xa7GACvMrnIhsECjp2W9li7PsSL2adrfImpnyZsoPIQu/BYPfieEtqQ89jP+e 5N4tRoGWOWf2zRlGMyVDLpt3cabIgmEAO+wqYqbu0HNgHbsVdtQ= =kaSA -END PGP SIGNATURE End Message ---
Processed: limit source to libforms, tagging 941535
Processing commands for cont...@bugs.debian.org: > limit source libforms Limiting to bugs with field 'source' containing at least one of 'libforms' Limit currently set to 'source':'libforms' > tags 941535 + pending Bug #941535 [libforms] libforms: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 941535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941535 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 943410
Processing commands for cont...@bugs.debian.org: > tags 943410 + pending Bug #943410 [src:xapian-bindings] autopkg test calls python instead of python2 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 943410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943410 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#944505: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity
Source: fonts-beteckna Version: 0.5-2 Severity: serious Tags: ftbfs Justification: fails to build from source Hi! I'm afraid that fonts-beteckna fails to build: ** (process:53089): WARNING **: 22:56:10.699: GlyfData.vala:407: Point on point in TTF. Index 50 Path: 1 in 9 E: Build killed with signal TERM after 150 minutes of inactivity Same happens both on a fat amd64 and a low-end arm64. Full log attached. Meow! -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-rc6-00053-g729694c1a413 (SMP w/64 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) sbuild (Debian sbuild) 0.78.1 (09 February 2019) on valinor.angband.pl +==+ | fonts-beteckna (amd64) Sun, 10 Nov 2019 22:55:49 + | +==+ Package: fonts-beteckna Distribution: unstable Machine Architecture: amd64 Host Architecture: amd64 Build Architecture: amd64 Build Type: binary I: NOTICE: Log filtering will replace 'var/run/schroot/mount/unstable-amd64-sbuild-e7a44aad-019d-4522-ab69-da5957dbc7b3' with '<>' I: NOTICE: Log filtering will replace 'build/fonts-beteckna-5CJmIK/resolver-UgUo7l' with '<>' +--+ | Update chroot| +--+ Hit:1 http://apt-rosy.angband.pl:3142/debian unstable InRelease Reading package lists... Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. +--+ | Fetch source files | +--+ Check APT - Checking available source versions... Download source files with APT -- Reading package lists... Need to get 2125 kB of source archives. Get:1 http://apt-rosy.angband.pl:3142/debian unstable/main fonts-beteckna 0.5-2 (dsc) [1884 B] Get:2 http://apt-rosy.angband.pl:3142/debian unstable/main fonts-beteckna 0.5-2 (tar) [2119 kB] Get:3 http://apt-rosy.angband.pl:3142/debian unstable/main fonts-beteckna 0.5-2 (diff) [3432 B] Fetched 2125 kB in 0s (109 MB/s) Download complete and in download only mode I: NOTICE: Log filtering will replace 'build/fonts-beteckna-5CJmIK/fonts-beteckna-0.5' with '<>' I: NOTICE: Log filtering will replace 'build/fonts-beteckna-5CJmIK' with '<>' +--+ | Install package build dependencies | +--+ Setup apt archive - Merged Build-Depends: debhelper (>= 11), birdfont, build-essential, fakeroot Filtered Build-Depends: debhelper (>= 11), birdfont, build-essential, fakeroot dpkg-deb: building package 'sbuild-build-depends-main-dummy' in '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. Ign:1 copy:/<>/apt_archive ./ InRelease Get:2 copy:/<>/apt_archive ./ Release [957 B] Ign:3 copy:/<>/apt_archive ./ Release.gpg Get:4 copy:/<>/apt_archive ./ Sources [373 B] Get:5 copy:/<>/apt_archive ./ Packages [456 B] Fetched 1786 B in 0s (161 kB/s) Reading package lists... Reading package lists... Install main build dependencies (apt-based resolver) Installing build dependencies Reading package lists... Building dependency tree... Reading state information... The following additional packages will be installed: adwaita-icon-theme birdfont bubblewrap dbus dbus-user-session dconf-gsettings-backend dconf-service dictionaries-common dmsetup emacsen-common fontconfig fontconfig-config fonts-dejavu-core fonts-roboto-unhinted glib-networking glib-networking-common glib-networking-services gsettings-desktop-schemas gtk-update-icon-cache hicolor-icon-theme hunspell-en-us iso-codes libapparmor1 libargon2-1 libaspell15 libatk-bridge2.0-0 libatk1.0-0 libatk1.0-data libatspi2.0-0 libavahi-client3 libavahi-common-data libavahi-common3 libbrotli1 libcairo-gobject2 libcairo2 libcap2 libcap2-bin libcolord2 libcryptsetup12 libcups2 libdatrie1 libdbus-1-3 libdconf1 libdevmapper1.02.1 libdrm-amdgpu1 libdrm-common libdrm-intel1 libdrm-nouveau2 libdrm-radeon1 libdrm2 libedit2 libegl-mesa0 libegl1
Bug#915470: marked as done (phpmyadmin build depends on and recommends php-tcpdf that might be removed from buster)
Your message dated Mon, 11 Nov 2019 03:03:44 +0300 with message-id <1573430624.996089...@f432.i.mail.ru> and subject line has caused the Debian Bug report #915470, regarding phpmyadmin build depends on and recommends php-tcpdf that might be removed from buster 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.) -- 915470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915470 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: phpmyadmin Version: 4:4.6.6-5 Severity: serious Control: block -1 by 908866 915286 phpmyadmin build depends on and recommends php-tcpdf that might be removed from buster. --- End Message --- --- Begin Message --- Version: phpmyadmin/4:4.9.1+dfsg1-2 --- End Message ---
Bug#916310: marked as done (4.6 should not be shipped in a stable release)
Your message dated Mon, 11 Nov 2019 03:04:57 +0300 with message-id <1573430697.881124...@f159.i.mail.ru> and subject line has caused the Debian Bug report #916310, regarding 4.6 should not be shipped in a stable release 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.) -- 916310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916310 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: phpmyadmin Severity: serious phpmyadmin hasn't seen an upload since almost 1.5 years and the current 4.6.x packafe isn't covered by upstream support (only 4.8). This isn't an acceptable state for inclusion in buster. (This isn't resolved by a one time upload rebasing to 4.8.x, whoever picks up the maintenance should also be available for updating it in buster when it's a stable release) Cheers, Moritz --- End Message --- --- Begin Message --- Version: phpmyadmin/4:4.9.1+dfsg1-2 4.9 will be shipped into next release--- End Message ---
Bug#942353: marked as done (python-evtx: ImportError: No module named hexdump)
Your message dated Sun, 10 Nov 2019 23:35:09 + with message-id and subject line Bug#942353: fixed in python-evtx 0.6.1-2 has caused the Debian Bug report #942353, regarding python-evtx: ImportError: No module named hexdump 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.) -- 942353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-evtx Version: 0.6.1-1 Severity: serious Justification: missing dependency $ evtx_dump.py Traceback (most recent call last): File "/usr/bin/evtx_dump.py", line 20, in import Evtx.Evtx as evtx File "/usr/local/buildtools/current/sitecustomize/sitecustomize.py", line 152, in SetupPathsAndImport return real_import(name, globals, locals, fromlist, level) File "/usr/lib/python2.7/dist-packages/Evtx/Evtx.py", line 28, in import Evtx.Views as e_views File "/usr/lib/python2.7/dist-packages/Evtx/Views.py", line 25, in import Evtx.Nodes as e_nodes File "/usr/lib/python2.7/dist-packages/Evtx/Nodes.py", line 25, in import hexdump ImportError: No module named hexdump Looks similar to https://bugs.debian.org/851056. The fix there doesn't seem to help here: there is a /usr/lib/python2.7/dist-packages/Evtx/hexdump.py file, but "import hexdump" doesn't import it (should it be "import Evtx.hexdump" instead?). Thanks for packaging the evtx package! --- End Message --- --- Begin Message --- Source: python-evtx Source-Version: 0.6.1-2 We believe that the bug you reported is fixed in the latest version of python-evtx, 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 942...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilko Bengen (supplier of updated python-evtx 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, 11 Nov 2019 00:03:40 +0100 Source: python-evtx Architecture: source Version: 0.6.1-2 Distribution: unstable Urgency: medium Maintainer: Hilko Bengen Changed-By: Hilko Bengen Closes: 942353 Changes: python-evtx (0.6.1-2) unstable; urgency=medium . [ Ondřej Nový ] * d/copyright: Use https protocol in Format field * d/control: Set Vcs-* to salsa.debian.org . [ Hilko Bengen ] * Fix hexdump import (Closes: #942353) Checksums-Sha1: 1d0d133150554c45cce4a98b10a44d9134398125 1916 python-evtx_0.6.1-2.dsc e3a9d0f79d60ae07e97f6e33f53f1e7b5dbb8bcf 7528 python-evtx_0.6.1-2.debian.tar.xz c6c9edfba1778c01a5d18b3a1248c4693a054a85 6452 python-evtx_0.6.1-2_source.buildinfo Checksums-Sha256: 85bdd3b9efc11859c9174ee017e7d4ced78a96d6846866c2beee2295a6925a75 1916 python-evtx_0.6.1-2.dsc e56286f07a9b89d72f38f559516a8729e04fdfbd0928c7d65cb0e7d1ca2f0f8b 7528 python-evtx_0.6.1-2.debian.tar.xz 198608faf3c73dd157cf27801fa905f50b349ca15fadfa547bf149bf37bc4fb7 6452 python-evtx_0.6.1-2_source.buildinfo Files: 79eee021b886908676840237dc6c6e31 1916 python optional python-evtx_0.6.1-2.dsc 69e9db1c07fdc84b7ea4fdb59b2f92b1 7528 python optional python-evtx_0.6.1-2.debian.tar.xz 50a2a9c24b6ffbdbba06cd92436467c6 6452 python optional python-evtx_0.6.1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAl3ImQgACgkQdbcQY1wh On48RRAAk/md8whsnNhoLSoJH9uomSDgQO99T4DPT9tBobq+yjwb/Fbc4mJnozSM 8hNj6g7fMEa5nxd71bK9WcHVZeiS7YBFya487q/BqfGwP5cnhv1PURygBlwP9fMz F2DdacJOcQjJJMtLfNjxPvfnQtsN3ybCPYNQv8UvN5jt3LfSO+4VFApVWLHEEPxs 0yy3JKsWDH9CJ/0gv5ELzBX66iXOM+XnWNpqAlKtTyJJQoxZUIksXrTfZj9S8Fkn yhijh5E4M3GXJvrnyz/2VELcdWqGHNMdGtGjGIkGaqfADD0zg2JeCp95nh+tHCco 9cvtuQjIFqcapI0tjwMZqg70Mu7pfM0Oov2M+0RTc95tJbg3I5RANr+6zu87+jl1 KAqFijPqdblOpbglyH4W9FiEevlpMbk3FAz3zV0KcqUMEmNdHahI2+oKOoig2g4e zeQc49K61tjk81CkoyMOUgXitgMtHU0M8idVm1UgkWc9oeSy3tiwQGUPbVieGcNx e8MS4ceXhAxluvIE/vpFKCOqCJCzqAmQK8Ubsc+O/UG4uRM0bYg0nSLxAyYE9ffC zxIPw78RHc8juuIy1mRM25OAnJ2PxNs+jetVGyjPqAb3dzMx0iAUQXSdwgQE1HyA 2+sMWgbsodUKu331Fo1rHGxTtk9Qjw3y2le3XRpwU8iyq4LHmV0= =1kHb -END PGP SIGNATURE End Message ---
Bug#938444: pymvpa2: Python2 removal in sid/bullseye
On 10.11.19 14:55, Rebecca N. Palmer wrote: On 10/11/2019 13:45, Matthias Klose wrote: I'm preparing a NMU for scikit-learn, based on the new subminor upstream release 0.20.3 I don't know why Ubuntu has 0.20.3 and Debian only .2, but it doesn't look related to either python3.8 or py2removal: https://scikit-learn.org/0.20/whats_new.html#version-0-20-3 there's also a bug report requesting the update to 0.21. The Ubuntu fix I was referring to is the explicit "Drop python2 support" i.e. https://launchpadlibrarian.net/438042402/scikit-learn_0.20.3+dfsg-0ubuntu1_0.20.3+dfsg-0ubuntu2.diff.gz (Probably the python-sklearn*.install files should have been removed as well?) yes, that's what I had done for the NMU.
Bug#943924: Processed: it no longer exists Re: please stop build-depending on python-pandas
Rebecca, please revert this. pandas has still 9 rdeps http://sandrotosi.me/debian/py2removal/python-pandas_1.svg and it's not appropriate to drop it like this. if you need to support py2 and py3 and upstream already dropped py2 support, you need to split it into 2 sources packages. On Sun, Nov 10, 2019 at 5:15 PM Debian Bug Tracking System wrote: > > Processing control commands: > > > severity -1 serious > Bug #943924 [python-matplotlib] matplotlib2: please stop build-depending on > python-pandas > Severity set to 'serious' from 'important' > > -- > 943924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943924 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Bug#944499: FTBFS: IndexError: list index out of range
Source: fonts-alegreya-sans
Version: 2.008-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi!
I'm afraid your package fails to build from source:
.
INFO:fontmake.font_project:Generating instance UFO for "Alegreya Sans Light"
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/fontmake/instantiator.py", line 314, in
generate_instance
glyph_instance = glyph_mutator.instance_at(location_normalized)
[...]
File "/usr/lib/python3/dist-packages/fontMath/mathGlyph.py", line 499, in
_processMathOneContours
points2 = contours2[index]["points"]
IndexError: list index out of range
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/bin/fontmake", line 11, in
load_entry_point('fontmake==2.0.4', 'console_scripts', 'fontmake')()
[...]
File "/usr/lib/python3/dist-packages/fontmake/instantiator.py", line 329, in
generate_instance
) from e
fontmake.instantiator.InstantiatorError: Failed to generate instance of glyph
'colonsign.BRACKET.75'.
`
On another run (full log attached) the glyph was 'longs.l' instead.
Meow!
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.4.0-rc6-00053-g729694c1a413 (SMP w/64 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
sbuild (Debian sbuild) 0.78.1 (09 February 2019) on valinor.angband.pl
+==+
| fonts-alegreya-sans 2.008-1 (amd64) Sun, 10 Nov 2019 18:31:25 + |
+==+
Package: fonts-alegreya-sans
Version: 2.008-1
Source Version: 2.008-1
Distribution: unstable
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: binary
I: NOTICE: Log filtering will replace
'var/run/schroot/mount/unstable-amd64-sbuild-6868024d-89bd-4b78-9d21-4c3a4471c7a0'
with '<>'
I: NOTICE: Log filtering will replace
'build/fonts-alegreya-sans-LiDCKh/resolver-b4Dc2K' with '<>'
+--+
| Fetch source files |
+--+
Local sources
-
/mnt/optane/f/fonts-alegreya-sans_2.008-1.dsc exists in /mnt/optane/f; copying
to chroot
I: NOTICE: Log filtering will replace
'build/fonts-alegreya-sans-LiDCKh/fonts-alegreya-sans-2.008' with
'<>'
I: NOTICE: Log filtering will replace 'build/fonts-alegreya-sans-LiDCKh' with
'<>'
+--+
| Install package build dependencies |
+--+
Setup apt archive
-
Merged Build-Depends: debhelper (>= 11), fontmake (>= 1.8.0), sfnt2woff-zopfli,
woff2, build-essential, fakeroot
Filtered Build-Depends: debhelper (>= 11), fontmake (>= 1.8.0),
sfnt2woff-zopfli, woff2, build-essential, fakeroot
dpkg-deb: building package 'sbuild-build-depends-main-dummy' in
'/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
Ign:1 copy:/<>/apt_archive ./ InRelease
Get:2 copy:/<>/apt_archive ./ Release [957 B]
Ign:3 copy:/<>/apt_archive ./ Release.gpg
Get:4 copy:/<>/apt_archive ./ Sources [394 B]
Get:5 copy:/<>/apt_archive ./ Packages [475 B]
Fetched 1826 B in 0s (21.3 kB/s)
Reading package lists...
Reading package lists...
Install main build dependencies (apt-based resolver)
Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
fontconfig fontconfig-config fontmake fonts-dejavu-core glyphsinfo libblas3
libbrotli1 libdbus-1-3 libdouble-conversion3 libdrm-amdgpu1 libdrm-common
libdrm-intel1 libdrm-nouveau2 libdrm-radeon1 libdrm2 libedit2 libegl-mesa0
libegl1 libevdev2 libexpat1 libfontconfig1 libfreetype6 libgbm1 libgfortran5
libgl1 libgl1-mesa-dri libglapi-mesa libglvnd0 libglx-mesa0 libglx0
libgraphite2-3 libgudev-1.0-0 libharfbuzz0b libice6 libinput-bin libinput10
libjpeg62-turbo liblapack3 liblbfgsb0 libllvm9 libmpdec2 libmtdev1
libpciaccess0 libpcre2-16-0 libpng16-16 libpython3-stdlib
libpython3.7-minimal libpython3.7-stdlib libqt5core5a libqt5dbus5 libqt5gui5
libqt5network5 libqt5widgets5 libreadline8 libsensors-config libsensors5
libsm6 libsqlite3-0 libssl1.1 libttfautohint1 libwacom-common libwacom2
libwayland-client0 libwayland-server0
Processed: it no longer exists Re: please stop build-depending on python-pandas
Processing control commands: > severity -1 serious Bug #943923 [python-apptools] python-apptools: please stop build-depending on python-pandas Severity set to 'serious' from 'important' -- 943923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943923 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: it no longer exists Re: please stop build-depending on python-pandas
Processing control commands: > severity -1 serious Bug #943924 [python-matplotlib] matplotlib2: please stop build-depending on python-pandas Severity set to 'serious' from 'important' -- 943924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943924 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#874853: [cmtk] Future Qt4 removal from Buster
On Thu, Oct 31, 2019 at 08:11:31PM -0700, Torsten Rohlfing wrote: > > There hasn't been any followup on this bug since two years and we're now > > moving > > forward with the Qt4 removal, are the immediate plans to port cmtk to Qt5 > > or > > should we remove it from the archive? > > > No plans for Qt5 whatsoever. > > The only thing to note here is that Qt is actually optional for the vast > majority of CMTK's tools. The package config could probably be changed to > build without GUI support, which would remove the dependency on Qt. I'm attaching a patch which disables the GUI tools in the package build. Cheers, Moritz diff -aur cmtk-3.3.1p1+dfsg.orig/debian/control cmtk-3.3.1p1+dfsg/debian/control --- cmtk-3.3.1p1+dfsg.orig/debian/control 2019-01-25 09:24:56.0 +0100 +++ cmtk-3.3.1p1+dfsg/debian/control 2019-11-10 22:43:57.518788563 +0100 @@ -13,8 +13,6 @@ libbz2-dev, libfftw3-dev, liblzma-dev, - libqt4-dev, - qt4-qmake, libpng-dev, libtiff-dev | libtiff4-dev, libwrap0-dev, diff -aur cmtk-3.3.1p1+dfsg.orig/debian/rules cmtk-3.3.1p1+dfsg/debian/rules --- cmtk-3.3.1p1+dfsg.orig/debian/rules 2019-01-25 09:24:56.0 +0100 +++ cmtk-3.3.1p1+dfsg/debian/rules 2019-11-10 22:48:57.444774239 +0100 @@ -38,7 +38,7 @@ -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON \ -DBUILD_APPS:BOOL=ON \ -DBUILD_DOCUMENTATION:BOOL=OFF \ - -DBUILD_GUI:BOOL=ON \ + -DBUILD_GUI:BOOL=OFF \ -DBUILD_SHARED_LIBS:BOOL=ON \ -DBUILD_TESTING:BOOL=$(TESTING) \ -DCMTK_BUILD_DCMTK:BOOL=OFF \ @@ -49,7 +49,7 @@ -DCMTK_ROOT_PATH_SRI24:PATH=/usr/share/data/sri24-atlas \ -DCMTK_USE_DCMTK:BOOL=ON \ -DCMTK_USE_FFTW:BOOL=ON \ - -DCMTK_USE_QT:BOOL=ON \ + -DCMTK_USE_QT:BOOL=OFF \ -DCMTK_USE_SMP:BOOL=ON \ -DCMTK_USE_SQLITE:BOOL=ON \ -DDART_TESTING_TIMEOUT:STRING=15000 \
Bug#933581: marked as done (BD on texlive-generic-extra which isn't build anymore and isn't in bullseye)
Your message dated Sun, 10 Nov 2019 22:06:52 + with message-id and subject line Bug#933581: fixed in python-networkx 2.2-5 has caused the Debian Bug report #933581, regarding BD on texlive-generic-extra which isn't build anymore and isn't in 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.) -- 933581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933581 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: breathe Version: 4.11.1-1 Severity: serious Tags: ftbfs sid bullseye Recently the texlive-base package has stopped building the transitional package texlive-generic-extra. This is an issue for your package as it build-depends on it. Please update the building of your package to use texlive-plain-generic instead. Unfortunately the migration software doesn't detected this kind of situation yet, so your package also FTBFS in bullseye since 2019-07-16. Paul signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: python-networkx Source-Version: 2.2-5 We believe that the bug you reported is fixed in the latest version of python-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 933...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated python-networkx package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 10 Nov 2019 16:53:36 -0500 Source: python-networkx Architecture: source Version: 2.2-5 Distribution: unstable Urgency: medium Maintainer: Sandro Tosi Changed-By: Sandro Tosi Closes: 933581 935195 Changes: python-networkx (2.2-5) unstable; urgency=medium . * Drop python3 and -doc packages, taken over by src:networkx; this removes quite some b-d and all the patches; Closes: #935195, #933581 Checksums-Sha1: 1659df528fcf82f20b11a33138b26038427f3d94 2140 python-networkx_2.2-5.dsc d4a54563b88b8d0e41f8e97851e3697ecf84ad88 11884 python-networkx_2.2-5.debian.tar.xz 78f0b1769b8d7038e46568495b109a74cd335efd 6458 python-networkx_2.2-5_source.buildinfo Checksums-Sha256: 02aeb5098fe01b23833b890d070441bd88690de2d04d94fdcfa2a1007928089a 2140 python-networkx_2.2-5.dsc 5318981979d8105c4029c01d62ebde274c09bcfbd8a1db2e2a21955e1a5dcdcc 11884 python-networkx_2.2-5.debian.tar.xz bc393fe2094b0e9a42c68fc7a2d5578988b87a716f12743eb81994b6b01ea1ec 6458 python-networkx_2.2-5_source.buildinfo Files: b7cc38e90634c04308490be54c1de899 2140 python optional python-networkx_2.2-5.dsc f035c0112add611dfac0c3730ca4cdd6 11884 python optional python-networkx_2.2-5.debian.tar.xz aa37a60ec0737480a815831fbd7bffbb 6458 python optional python-networkx_2.2-5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl3IhyUACgkQh588mTgB qU8IKA//YX6uq8UdRNe3tRLphJmVKo7c6hrvfYkdINHxKc8MrexkZJLFDhkDpqBh MScwGM13PZ23K3TCbv/iuhY8gV3gl1E2rkIGqoN4kzPW+8UitqXmYHH1y/4Cb+2g vCRKn82YrRGdvpDGGP0T5AxOi87gqVDF6uJLifPdFagx70jnqgON7pw2vwRSJ7ZK 3SLJ817zzFG6BNzWczJi3Fq67Zxpt1kLUZwNw6tY1EXcMtZ2FtpyMlqR8t8OUwvN ms1SDZ7pKpMeMQDYj6amWnYJ4CKMC5ToBTdPF2ZAg2yXR+TX4qDljrEYGMrbZlVz Rmt/pcHF4C/Fdgf4GMxRHNPfHxLjYUTRFdaR9RLQKOdu/feL41P9jCLaE4FGqXwI bxr7cWuYOOsgvuNlJW9u5SeVD0ro5PSxx+wzxukxPc2Oy+/y28OgSBdoXJFENs6k 3agI5H/JTwZQetrhw6UmezzVUqJUcdFVK4YYohBs+66bagStJSeX/jVr14i6R2mS wuwvG9W6zPRB06QEbb8ielewIniCUKWY4+dPORYlfUSisWlAEYL6aFYsYQFAJgg7 Q1EP64XeKplQEeQo/3DJV+7wz8hzkWdsEsm5jP55V2R4uOORwxB2eX91cr7FxyuH OVQRHY3qGSsSqXc0TuwnAMe9dy6YjUrYNoLK7SnukqP+DvkDRSQ= =D0Iq -END PGP SIGNATURE End Message ---
Bug#900787: nvidia-graphics-drivers-legacy-304xx: does not support Xorg Xserver 1.20
Package: xserver-xorg-video-nvidia-legacy-304xx Version: 304.137-7 Followup-For: Bug #900787 Dear Maintainer, I use a Dell Inspiron 9400 Laptop with a nvidia 7900 Go graphics adapter which is not changegable to a newer gpu card. This 64 bit laptop is for the trash bin if I cannot use it any more like with freecad which supports also nouveau driver, but is not really working with all needed hw acceleration. So also freecad as an example is not really usuable with nouveau on this laptop and other accelerations looks like not further usuable like video decoding via gpu. Please add support for the legacy driver for my card (which is still only available by 304xx). It looks like the installation could be only possible by using stretch and not buster? And what is if the support for stretch ends? So downgrade to stretch is also not the optimal option. Is it not really possible to use xserver version 1.20 for this driver or must I downgrade xserver to 1.19? Save the world from electronic trash by eol supported software. Cheers, PS: I installed only the 304xx from unstable. All the rest is still from stable. -- System Information: Debian Release: 10.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-6-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xserver-xorg-video-nvidia-legacy-304xx depends on: ii libc6 2.28-10 ii libnvidia-legacy-304xx-glcore 304.137-7 ii nvidia-installer-cleanup 20151021+9 ii nvidia-legacy-304xx-alternative 304.137-7 ii nvidia-support 20151021+9 pn xorg-video-abi-23 | xorg-video-abi-20 | xorg-video-abi-19 | xor ii xserver-xorg-core 2:1.20.4-1 ii xserver-xorg-legacy 2:1.20.4-1 Versions of packages xserver-xorg-video-nvidia-legacy-304xx recommends: pn nvidia-legacy-304xx-driver ii nvidia-legacy-304xx-kernel-dkms [nvidia-legacy-304xx-kernel-304. 304.137-7 ii nvidia-legacy-304xx-vdpau-driver 304.137-7 ii nvidia-settings-legacy-304xx 304.137-2
Bug#944496: FTBFS: Assigning non-zero to $[ is no longer possible at tools/hex2bdf
Source: xfonts-efont-unicode Version: 0.4.2-11 Severity: serious Tags: ftbfs Justification: fails to build from source Hi! I'm afraid that the package fails to build, with a bunch of: Assigning non-zero to $[ is no longer possible at tools/hex2bdf line 17, <> line 7446. Additionally, there's some binary spew to the terminal. Full log attached. Meow! -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-rc6-00053-g729694c1a413 (SMP w/64 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) xfonts-efont-unicode_amd64.build Description: Binary data
Bug#926528: marked as done (libgps changed API of gps_read)
Your message dated Sun, 10 Nov 2019 21:49:42 + with message-id and subject line Bug#926528: fixed in collectd 5.9.2-1 has caused the Debian Bug report #926528, regarding libgps changed API of gps_read 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.) -- 926528: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926528 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: collectd Version: 5.8.1-1.2 Hi, libgps changed the gps_read implementation in [0]. To be clear the change in gpsd is currently only in experimental. This is a heads up for the post buster transition that will come sooner or later. Upstream collectd already implemented the change necessary in [1]. So far collectd has had no release that includes this, but due to being dependent on the GPSD_API_MAJOR_VERSION this can be applied at any time and will make it (re)build correctly once the new gpsd version will start the transition. Therefore I'd appreciate if you could include this change in when-/whatever the next upload to collectd will happen. I'll let the gpsd maintainer know about the bug, so that we can consider it when kicking off the transition. [0]: https://git.savannah.gnu.org/cgit/gpsd.git/commit/?id=6bba8b329 [1]: https://github.com/collectd/collectd/commit/991a6d3fd38c2435d94de3853fda36b3330cf6ab -- Christian Ehrhardt Software Engineer, Ubuntu Server Canonical Ltd --- End Message --- --- Begin Message --- Source: collectd Source-Version: 5.9.2-1 We believe that the bug you reported is fixed in the latest version of collectd, 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 926...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bernd Zeimetz (supplier of updated collectd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 10 Nov 2019 22:29:36 +0100 Source: collectd Architecture: source Version: 5.9.2-1 Distribution: unstable Urgency: medium Maintainer: Collectd Packaging Team Changed-By: Bernd Zeimetz Closes: 926528 Changes: collectd (5.9.2-1) unstable; urgency=medium . * [e2bc528] Stay with the common debian/version tag. * [989ce6e] Collect and review changes from @zebity https://github.com/zebity/pkg-debian * [6119616] Configure gitlab-ci * [4f34b97] Update upstream source from tag 'upstream/5.9.2' Update to upstream version '5.9.2' with Debian dir af7c66a8817dcb447a93e60e87aff32a05a0b4c3 This fixes build issues with recent libgps-dev. Closes: #926528 * [ccc5baf] snapshot changelog * [ad672e1] fake commit for CI * [65f9d1b] Make deps for collectd automatic * [07a98ce] Set CXXFLAGS from dpkg-buildflags * [918a39f] Updating git urls * [41e284a] Use a tracker.d.o team as maintainer. Adding myself as uploader. Checksums-Sha1: 08352e03ef9682f4f2132f1f7e43acd2020ca3b9 4215 collectd_5.9.2-1.dsc 74d3abd097367a01284efc42861854e17751723c 1572628 collectd_5.9.2.orig.tar.xz c8f447bcf7728c6ac987fbd5095537d927e1b59b 76736 collectd_5.9.2-1.debian.tar.xz b5841186c40ad7ab1581eaa4d198821506fe51fb 16764 collectd_5.9.2-1_source.buildinfo Checksums-Sha256: f6e2ecdf3be30a9b65922945004be8e8526401f5ccd61c7d114f025faa737784 4215 collectd_5.9.2-1.dsc dfcb2a2fa7de0ab02c9e6c1457bee2069957d4ffc9b428851661e9c5e5fc35b7 1572628 collectd_5.9.2.orig.tar.xz 82710eb166abfd95db4ac51ba95097111e45b19f25f0c85b8e1de982d4ad01d3 76736 collectd_5.9.2-1.debian.tar.xz 0dd1ddb7c29d2826a973ddaf1e9d097d979e94bb851eda7e3e551f28e22e1ab5 16764 collectd_5.9.2-1_source.buildinfo Files: 56e0b3532cb870ebe363b59ea6e1407f 4215 utils optional collectd_5.9.2-1.dsc 4ec308f256a3d3575f6c8a2be4338966 1572628 utils optional collectd_5.9.2.orig.tar.xz 39bfccef64ba7a02498b08d66fa46d5b 76736 utils optional collectd_5.9.2-1.debian.tar.xz 96d694a81ec6d6538c81e9726feba4e0 16764 utils optional collectd_5.9.2-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE7KHj8o4RJDLUhd2V6zYXGm/5Q18FAl3IgYoACgkQ6zYXGm/5 Q1/3jBAAgc9q/rFKFBE7WHAOUdWKu5WP50ePMZHDrFqPb3VDjaTRztomqsFdJ6zp Wd4LHGZTYzeFzuVXQLVE0OhzBoolYDen7BTWBHDIvnSbvxkYtFmH4wB3jAe2ZMNL
Bug#875250: Bug#875258: [scim] Future Qt4 removal from Buster
On Sun, Sep 08, 2019 at 03:31:29AM +0800, Tz-Huan Huang wrote: > On Fri, Aug 30, 2019 at 4:39 AM Moritz Mühlenhoff wrote: > > > On Sat, Sep 09, 2017 at 11:09:36PM +0200, Lisandro Damián Nicanor Pérez > > Meyer wrote: > > > Source: scim > > > > > > Hi! As you might know we the Qt/KDE team are preparing to remove Qt4 > > > as [announced] in: > > > > > > [announced] < > > https://lists.debian.org/debian-devel-announce/2017/08/msg6.html> > > > > > > Currently Qt4 has been dead upstream and we are starting to have problems > > > maintaining it, like for example in the [OpenSSL 1.1 support] case. > > > > > > [OpenSSL 1.1 support] < > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828522> > > > > > > In order to make this move, all packages directly or indirectly > > depending on > > > the Qt4 libraries have to either get ported to Qt5 or eventually get > > > removed from the Debian repositories. > > > > > > Therefore, please take the time and: > > > - contact your upstream (if existing) and ask about the state of a Qt5 > > > port of your application > > > - if there are no activities regarding porting, investigate whether > > there are > > > suitable alternatives for your users > > > - if there is a Qt5 port that is not yet packaged, consider packaging it > > > - if both the Qt4 and the Qt5 versions already coexist in the Debian > > > archives, consider removing the Qt4 version > > > > Given upstream's comments on https://github.com/scim-im/scim/issues/21, > > let's > > move forward by dropping the scim-qt-immodule binary package? It can still > > be re-added if a Qt5 port appears at a later time. > > > > Sure. I have made the update and been waiting for maintainer's review. > > https://github.com/leggewie-DM/scim/pull/1 Hi Rolf, could you have a look/do an upload? Once the qscintilla migration is complete, scim will be the last remaining key package blocking the removal of Qt4 from testing. Cheers, Moritz
Bug#925833: marked as done (snoopy: ftbfs with GCC-9)
Your message dated Sun, 10 Nov 2019 21:23:28 + with message-id and subject line Bug#925833: fixed in snoopy 2.4.6-6 has caused the Debian Bug report #925833, regarding snoopy: ftbfs with GCC-9 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.) -- 925833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925833 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:snoopy Version: 2.4.6-5 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-9 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-9/g++-9, but succeeds to build with gcc-8/g++-8. 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/gcc9-20190321/snoopy_2.4.6-5_unstable_gcc9.log The last lines of the build log are at the end of this report. To build with GCC 9, either set CC=gcc-9 CXX=g++-9 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-9/porting_to.html GCC 9 also passes the linker option --as-needed by default; typical build issues are passing libraries before object files to the linker, or underlinking of convenience libraries built from the same source. [...] config.status: creating lib/Makefile config.status: creating lib/inih/Makefile config.status: creating lib/inih/src/Makefile config.status: creating src/Makefile config.status: creating src/datasource/Makefile config.status: creating src/eventsource/Makefile config.status: creating src/filter/Makefile config.status: creating src/output/Makefile config.status: creating util/Makefile config.status: creating tests/Makefile config.status: creating tests/bin/Makefile config.status: creating tests/combined/Makefile config.status: creating tests/configfile/Makefile config.status: creating tests/datasource/Makefile config.status: creating tests/filter/Makefile config.status: creating tests/message/Makefile config.status: creating tests/output/Makefile config.status: creating tests/threads/Makefile config.status: creating util/snoopy-disable config.status: creating util/snoopy-enable config.status: creating config.h config.status: executing depfiles commands config.status: executing libtool commands configure: WARNING: unrecognized options: --disable-maintainer-mode make[1]: Leaving directory '/<>' dh_auto_build -a make -j4 make[1]: Entering directory '/<>' make all-recursive make[2]: Entering directory '/<>' Making all in etc make[3]: Entering directory '/<>/etc' make[3]: Nothing to be done for 'all'. make[3]: Leaving directory '/<>/etc' Making all in lib make[3]: Entering directory '/<>/lib' Making all in inih make[4]: Entering directory '/<>/lib/inih' Making all in src make[5]: Entering directory '/<>/lib/inih/src' /bin/bash ../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Werror -Wextra -Wno-unused-parameter -std=c99 -pedantic -I../../.. -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o ini.lo ini.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Werror -Wextra -Wno-unused-parameter -std=c99 -pedantic -I../../.. -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c ini.c -fPIC -DPIC -o .libs/ini.o In file included from /usr/include/string.h:494, from ini.c:16: In function 'strncpy', inlined from 'strncpy0' at ini.c:67:5, inlined from 'ini_parse_stream' at ini.c:164:17: /usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: error: '__builtin_strncpy' specified bound 50 equals destination size [-Werror=stringop-truncation] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~ In function 'strncpy', inlined from 'strncpy0' at
Bug#943911: marked as done (squid: needs a source-only upload.)
Your message dated Sun, 10 Nov 2019 21:23:42 + with message-id and subject line Bug#943911: fixed in squid 4.9-1 has caused the Debian Bug report #943911, regarding squid: needs a source-only upload. 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.) -- 943911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943911 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: squid Version: 4.8-1 Severity: serious The release team have decreed that non-buildd binaries can no longer migrate to testing. Please make a source-only upload so your package can migrate. --- End Message --- --- Begin Message --- Source: squid Source-Version: 4.9-1 We believe that the bug you reported is fixed in the latest version of squid, 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 943...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luigi Gangitano (supplier of updated squid 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, 10 Nov 2019 20:28:15 +0100 Source: squid Architecture: source Version: 4.9-1 Distribution: unstable Urgency: high Maintainer: Luigi Gangitano Changed-By: Luigi Gangitano Closes: 911325 933295 943692 943911 Changes: squid (4.9-1) unstable; urgency=high . * Urgency high due to security fixes . [ Amos Jeffries ] * New Upstream Release (Closes: #943692) - Fixes security issue SQUID-2019:7 (CVE-2019-12526) - Fixes security issue SQUID-2019:8 (CVE-2019-18676) (CVE-2019-12523) - Fixes security issue SQUID-2019:9 (CVE-2019-18677) - Fixes security issue SQUID-2019:10 (CVE-2019-18678) - Fixes security issue SQUID-2019:11 (CVE-2019-18679) - Updates fix for security issue SQUID-2019:6 (CVE-2019-13345) . * debian/control - Bumped Standards-Version to 4.4.1, no change needed . * debian/tests/test-squid.py - Disable Apparmor tests . [ Luigi Gangitano ] * Source only upload (Closes: #943911) . * debian/squid.resolvconf - Avoid reload before squid.pid is available (Closes: #911325) thanks to Michael Biebl and Wolfgang Schweer . * debian/squid.rc - Make squid.rc wait for directory creation (Closes: #933295), thanks to Daniel Reichelt Checksums-Sha1: f3effc89fcc01e932da199c3680cc3d48bba29da 2655 squid_4.9-1.dsc 6f4b6dcb8225953dccf94b9afb3f6677ebf17478 5181543 squid_4.9.orig.tar.gz 040e88cd49b191a59edf88a73ef379a870a5505d 38116 squid_4.9-1.debian.tar.xz b94bbf184f63299728ec9b114a94dc0b3b0a0f95 9672 squid_4.9-1_amd64.buildinfo Checksums-Sha256: 9a6454ab921cc5f0435a45a3084cc3f82a28fab2e6496270a374b98864b52ba0 2655 squid_4.9-1.dsc 7a3157da55d91eac7ea54b1d3145f18563a98dcaf5132bf5bf16b4eafa69459a 5181543 squid_4.9.orig.tar.gz 543adde95874a5a1edf53fa83fb8f77c72209cb426d93ee29c0430b6625ebc72 38116 squid_4.9-1.debian.tar.xz dd3a6e02070f1b7690fcb041bd6a211a6a9d0a1721096e6f20878ae8a43a6b31 9672 squid_4.9-1_amd64.buildinfo Files: 2cef70454feead49d6b545b5602cb212 2655 web optional squid_4.9-1.dsc 9cf23fc2d53761390b1f9f0ec3859d8f 5181543 web optional squid_4.9.orig.tar.gz ec7ed1ec9b28d848811130104eb56301 38116 web optional squid_4.9-1.debian.tar.xz a52336ba5940169191f773348457c981 9672 web optional squid_4.9-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEjUhaNf8ebreQ5Q9tAoTyDCupfO0FAl3IeQcACgkQAoTyDCup fO3L+Q//VAY14odYPOOiec/ozklHeG5bw6qfgXvXH4W6blK1qGNxaBRa0WDBAF7G Eta5I0oJ/3/BZasSCzCBHFzBy5vmIIVXxPsNo4y+rDPj+w+/3NMbD3EKmXgWkG/u /H+6gYSIrtg2pRZ6q/UWfxInNpsNHzmiHsqu0gcVW563lFbO3M0nfoUg47laWbj/ X1/YagzD1r+Am0IzctruAAmeVbn2cS5NldxJUVCIrMVTXtXvDP3LpYPy863BNRl9 6AtAKDcmyWZ3fXHgRFS2TLzXzOezlAWf8JHbZedYADShlxT/6t858OyFxZYxLplF gYIpCbEaof0LZCaC29AQYJa3HMh0xYkQPbc12xjEIhzC10/5AP6r8YqBMznwdvXj 4iWOqQeAMwXyCQZWYDWX3dfFqfIKZenm18W+MQvb0T2YSalqPnGW4jJkeFRf/KKU cjuiQny3GSGm8lEut4Nnf2rRRLqzM2Mkr51k0Rg6wQPRZfGk0OZnSGTT6GsIzf1p beBK8/xy0v8zI97hum+WqvzuzYq5iuOT5ZxHSEA2W7DvJ+eDLuApeDA4RmJLs3JE tpSjwN5PkLLRRUygssbhN2mlAiyT3FRp0LkqlETvGIm0pi8Fqi/qzpbKz4aDW1gq /OJ2LcnhCDWdCsM2p6FOD5y8dzhRzze6wS62kBhHxA85uCIkiKE= =Dw70 -END PGP SIGNATURE End Message ---
Processed: liquidsoap unblock
Processing commands for cont...@bugs.debian.org: > unblock 939580 by 941907 944404 Bug #939580 [src:liquidsoap] liquidsoap: FTBFS with new ffmpeg ocaml library 939580 was blocked by: 941907 944404 939580 was not blocking any bugs. Removed blocking bug(s) of 939580: 941907 and 944404 > thanks Stopping processing here. Please contact me if you need assistance. -- 939580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939580 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#943653: thrift: fails to clean after build: cannot find java
Hi Andreas, On Sun, Oct 27, 2019 at 3:45 PM Andreas Beckmann wrote: > thrift/experimental fails to clean after a successful build (I haven't > checked whether the version in sid has the same problem). > The build succeeds, but a subsequent 'make distclean' fails. (This does > not happen during the first build, since the tree is unconfigured and > 'make distclean' does not get called.) Please point me where's in the policy that a package must be buildable several times from the same source tree and that experimental is a supported branch (target for filing RC bugs). Thanks, Laszlo/GCS
Processed: severity of 944491 is important
Processing commands for cont...@bugs.debian.org: > severity 944491 important Bug #944491 [firmware-iwlwifi] firmware-iwlwifi: firmware does not load with error -110 with Intel 7260 Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 944491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944491 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#941540: marked as done (moon-buggy: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended)
Your message dated Sun, 10 Nov 2019 19:20:34 + with message-id and subject line Bug#941540: fixed in moon-buggy 1:1.0.51-13 has caused the Debian Bug report #941540, regarding moon-buggy: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 941540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941540 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: moon-buggy Version: 1:1.0.51-12 Severity: serious Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu eoan ubuntu-patch Hi Christian, The texlive-generic-recommended transitional package has been dropped from texlive-base in sid. Please update your build-dependency to texlive-plain-generic instead. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org diff -Nru moon-buggy-1.0.51/debian/control moon-buggy-1.0.51/debian/control --- moon-buggy-1.0.51/debian/control2018-05-07 13:20:01.0 -0700 +++ moon-buggy-1.0.51/debian/control2019-10-01 14:24:07.0 -0700 @@ -11,7 +11,7 @@ po-debconf, texinfo, texlive, - texlive-generic-recommended + texlive-plain-generic Standards-Version: 4.1.4.1 Homepage: http://seehuhn.de/pages/moon-buggy Vcs-Browser: https://salsa.debian.org/debian/moon-buggy --- End Message --- --- Begin Message --- Source: moon-buggy Source-Version: 1:1.0.51-13 We believe that the bug you reported is fixed in the latest version of moon-buggy, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 941...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian T. Steigies (supplier of updated moon-buggy 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: Wed, 02 Oct 2019 19:58:13 +0200 Source: moon-buggy Architecture: source Version: 1:1.0.51-13 Distribution: unstable Urgency: medium Maintainer: Christian T. Steigies Changed-By: Christian T. Steigies Closes: 941540 Changes: moon-buggy (1:1.0.51-13) unstable; urgency=medium . [ Ondřej Nový ] * d/changelog: Remove trailing whitespaces * d/rules: Remove trailing whitespaces . [ Christian T. Steigies ] * b-d on texlive-plain-generic, not obsolete texlive-generic-recommended (closes: #941540) * drop deprecated --with autotools_dev * mention pause patch in d/patches/series Checksums-Sha1: fe1eea9dc187c2401e06d3bb144569d684d85a57 2000 moon-buggy_1.0.51-13.dsc ace911585569352b7be86eda76d438adf43b01bb 18436 moon-buggy_1.0.51-13.debian.tar.xz 15b87067af90c1a30a2863dd1929c91776a47317 13661 moon-buggy_1.0.51-13_amd64.buildinfo Checksums-Sha256: 165f2204ba2deaa60a1387b605570ae162696db43b0a1b08da2e7d8cba81e077 2000 moon-buggy_1.0.51-13.dsc 843722330a735933c5c26c93a11897e203574bdfd801c7aecc6f5f8c3c459380 18436 moon-buggy_1.0.51-13.debian.tar.xz 28c61b5cb52d3de00047b5e19e1c32589877ca527a085329a1783955915dc9e0 13661 moon-buggy_1.0.51-13_amd64.buildinfo Files: 5146e769fd603bd2fe54ee13b18b11ca 2000 games optional moon-buggy_1.0.51-13.dsc 5a26e9da3b66174a8f495b31eb8faabd 18436 games optional moon-buggy_1.0.51-13.debian.tar.xz 3fea6828cac81ccc39219ee4e215898b 13661 games optional moon-buggy_1.0.51-13_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCgAtFiEEMuHemUY/GC4Wej4EcA1WeHGyg0IFAl3IXkAPHGN0c0BkZWJp YW4ub3JnAAoJEHANVnhxsoNCUIIP+wZk91xicZU+t+QtmnekummKTcXEdbx/+Ujc u9zadWONHMTb355tYKZ050laKUigW6dvpbZTKaEEHTh7aAUgNnWFe1x3OkWF2Jpj pAoXUk7e8N8vBr3+7dPVjoWkyz+3dnYx0iaRxOxWXcUst3z0CfPvClPckFZ8pDVT NlTl/+lIuNMoLPfqCvxRexxjNenhYlwJjdveYcQiM6kKBn4ExMHJiVjoDpKwsHDh dlQp8lwXlq2DJUKhLTQsA+pCGXzk6X2mvCJN0Y0319Syaijcfu3k0fM8++rOpHbh 8mzJaRr2KFnp354j+SWmWkJ/xYmw4WrQSe63AfZ/zOjW9ZtkJbARLURz16dUUqnV ZEQZwgidB00CqUZhhWbX1hsADVP4nhKTuc+858QSfXrmTV3AgC8FiHz5rSIbjAUf
Processed: Re: nosexcover: Python2 removal in sid/bullseye, python3-nosexcover shouldn't depend on python-nose and python-coverage
Processing control commands: > tags -1 pending Bug #937159 [src:nosexcover] nosexcover: Python2 removal in sid/bullseye Added tag(s) pending. -- 937159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937159 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: nosexcover: Python2 removal in sid/bullseye, python3-nosexcover shouldn't depend on python-nose and python-coverage
Processing control commands: > tags -1 pending Bug #906083 [python3-nosexcover] python3-nosexcover shouldn't depend on python-nose and python-coverage Added tag(s) pending. -- 906083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906083 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#906083: nosexcover: Python2 removal in sid/bullseye, python3-nosexcover shouldn't depend on python-nose and python-coverage
Control: tags -1 pending
Hi,
I have uploaded the attached fix to DELAYED/5.
Cheers,
Balint
diff -Nru nosexcover-1.0.11/debian/changelog nosexcover-1.0.11/debian/changelog
--- nosexcover-1.0.11/debian/changelog 2018-05-02 09:21:57.0 +0200
+++ nosexcover-1.0.11/debian/changelog 2019-11-10 18:07:13.0 +0100
@@ -1,3 +1,11 @@
+nosexcover (1.0.11-1.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop Python 2 dependencies, build-dependencies and binary package
+(Closes: #937159, #906083)
+
+ -- Balint Reczey Sun, 10 Nov 2019 18:07:13 +0100
+
nosexcover (1.0.11-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru nosexcover-1.0.11/debian/control nosexcover-1.0.11/debian/control
--- nosexcover-1.0.11/debian/control 2018-05-02 09:21:57.0 +0200
+++ nosexcover-1.0.11/debian/control 2019-11-10 18:07:13.0 +0100
@@ -4,32 +4,16 @@
Maintainer: Guido Günther
Build-Depends: debhelper (>= 10.0.0~),
dh-python,
- python-all,
- python3,
- python-nose,
+ python3-all,
python3-nose,
- python-setuptools,
python3-setuptools,
Standards-Version: 4.1.1
Homepage: http://pypi.python.org/pypi/nosexcover
-Package: python-nosexcover
-Architecture: all
-Depends: ${misc:Depends},
- ${python:Depends}, python-nose, python-coverage (>= 3.4)
-Description: Add Cobertura-style XML coverage report to nose (Python2 version)
- A companion to the built-in nose.plugins.cover, this plugin will write
- out an XML coverage report to a file named coverage.xml.
- .
- It will honor all the options you pass to the Nose coverage plugin,
- especially --cover-package.
- .
- This package contains the Python 2 version of the module.
-
Package: python3-nosexcover
Architecture: all
Depends: ${misc:Depends},
- ${python3:Depends}, python-nose, python-coverage (>= 3.4)
+ ${python3:Depends}, python3-nose, python3-coverage (>= 3.4)
Description: Add Cobertura-style XML coverage report to nose (Python3 version)
A companion to the built-in nose.plugins.cover, this plugin will write
out an XML coverage report to a file named coverage.xml.
diff -Nru nosexcover-1.0.11/debian/python3-nosexcover.install nosexcover-1.0.11/debian/python3-nosexcover.install
--- nosexcover-1.0.11/debian/python3-nosexcover.install 2015-02-19 13:02:36.0 +0100
+++ nosexcover-1.0.11/debian/python3-nosexcover.install 1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-usr/lib/python3.?
diff -Nru nosexcover-1.0.11/debian/python-nosexcover.install nosexcover-1.0.11/debian/python-nosexcover.install
--- nosexcover-1.0.11/debian/python-nosexcover.install 2015-02-19 13:02:32.0 +0100
+++ nosexcover-1.0.11/debian/python-nosexcover.install 1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-usr/lib/python2.?
diff -Nru nosexcover-1.0.11/debian/rules nosexcover-1.0.11/debian/rules
--- nosexcover-1.0.11/debian/rules 2015-02-19 13:37:49.0 +0100
+++ nosexcover-1.0.11/debian/rules 2019-11-10 18:07:13.0 +0100
@@ -1,4 +1,4 @@
#!/usr/bin/make -f
%:
- dh $@ --with python2,python3 --buildsystem=pybuild
+ dh $@ --with python3 --buildsystem=pybuild
Processed: severity of 906083 is serious
Processing commands for cont...@bugs.debian.org: > severity 906083 serious Bug #906083 [python3-nosexcover] python3-nosexcover shouldn't depend on python-nose and python-coverage Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 906083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906083 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#944258: lintian 2.32.0~bpo9+1 in stretch-backports depends on coreutils (>= 8.30), but stretch has only 8.26-3
tags 944258 + pending thanks Felix, > Was this not resolved by the following? I didn't see this commit; I likely assumed you would followup to the bug explicitly and the lack of automatic "pending" is likely due to "(Closes #944258)" vs. "(Closes: #944258)" with the colon. No matter, doing it manually above - these things happen. > Or, do I need to backport the patch to that specific version? If you mean backport it to that particular branch... then no; we just need to do a regular backport upload. I do that after its migrated to testing to follow the rules, so we are a few days off this landing in stretch alas. (As in; I need to do an unstable upload first that includes this commit and let that migrate...) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org chris-lamb.co.uk `-
Processed: Re: Bug#944258: lintian 2.32.0~bpo9+1 in stretch-backports depends on coreutils (>= 8.30), but stretch has only 8.26-3
Processing commands for cont...@bugs.debian.org: > tags 944258 + pending Bug #944258 [lintian] lintian 2.32.0~bpo9+1 in stretch-backports depends on coreutils (>= 8.30), but stretch has only 8.26-3 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 944258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944258 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#944491: firmware-iwlwifi: firmware does not load with error -110 with Intel 7260
Package: firmware-iwlwifi Version: 20190717-2 Severity: grave Dear Maintainer, After upgrading to the 5.2.0-3 kernel, module iwlwifi cannot be loaded as there is an error in the microcode. Here are the related kernel.log messages: [ 12.689939] iwlwifi :3d:00.0: Failed to load firmware chunk! [ 12.690990] iwlwifi :3d:00.0: iwlwifi transaction failed, dumping registers [ 12.692217] iwlwifi :3d:00.0: iwlwifi device config registers: [ 12.693323] iwlwifi :3d:00.0: : 08b18086 00100406 0280006b 0010 d014 [ 12.695108] iwlwifi :3d:00.0: 0020: c0608086 00c8 0100 [ 12.696916] iwlwifi :3d:00.0: iwlwifi device memory mapped registers: [ 12.698169] iwlwifi :3d:00.0: : 40489204 8040 2000 0800 [ 12.699981] iwlwifi :3d:00.0: 0020: 0009 080003c5 0144 8000 803a 80008040 00080046 [ 12.701777] iwlwifi :3d:00.0: iwlwifi device AER capability structure: [ 12.703006] iwlwifi :3d:00.0: : 14010001 4000 00462031 2000 2000 000e [ 12.703861] iwlwifi :3d:00.0: 0020: [ 12.704382] iwlwifi :3d:00.0: iwlwifi parent port (:3c:01.0) config registers: [ 12.704921] iwlwifi :3c:01.0: : 240412d8 00180407 06040005 00010010 003d3d3c 01f1 [ 12.705580] iwlwifi :3c:01.0: 0020: d010d010 0001fff1 0040 0002010a [ 12.706300] iwlwifi :3d:00.0: Could not load the [0] uCode section [ 12.706786] iwlwifi :3d:00.0: Failed to start INIT ucode: -110 [ 12.707189] iwlwifi :3d:00.0: Collecting data: trigger 16 fired. [ 12.954147] iwlwifi :3d:00.0: Not valid error log pointer 0x for Init uCode [ 12.954692] iwlwifi :3d:00.0: Fseq Registers: [ 12.954710] iwlwifi :3d:00.0: Hardware error detected. Restarting. [ 12.955004] iwlwifi :3d:00.0: 0x | FSEQ_ERROR_CODE [ 12.955813] iwlwifi :3d:00.0: 0x | FSEQ_TOP_INIT_VERSION [ 12.956215] iwlwifi :3d:00.0: 0x | FSEQ_CNVIO_INIT_VERSION [ 12.956627] iwlwifi :3d:00.0: 0x | FSEQ_OTP_VERSION [ 12.957002] iwlwifi :3d:00.0: 0x | FSEQ_TOP_CONTENT_VERSION [ 12.957420] iwlwifi :3d:00.0: 0x | FSEQ_ALIVE_TOKEN [ 12.957795] iwlwifi :3d:00.0: 0x | FSEQ_CNVI_ID [ 12.958208] iwlwifi :3d:00.0: 0x | FSEQ_CNVR_ID [ 12.958569] iwlwifi :3d:00.0: 0x | CNVI_AUX_MISC_CHIP [ 12.958964] iwlwifi :3d:00.0: 0x | CNVR_AUX_MISC_CHIP [ 12.959359] iwlwifi :3d:00.0: 0x | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM [ 12.959865] iwlwifi :3d:00.0: 0x | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR [ 12.960407] iwlwifi :3d:00.0: Firmware not running - cannot dump error [ 12.979731] iwlwifi :3d:00.0: Failed to run INIT ucode: -110 The firmware works perfectly with a 4.19 kernel. Notice that this is surely related to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939262, but as I have an unreported error (Failed to run INIT ucode: -110), I have submitted a new bug report. Notice also that manually installing 20190815 version does not solve the problem. Best, Christophe -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (986, 'testing'), (984, 'stable'), (982, 'stable'), (98, 'unstable'), (96, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux -5.2.0-3-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled firmware-iwlwifi depends on no packages. firmware-iwlwifi recommends no packages. Versions of packages firmware-iwlwifi suggests: ii initramfs-tools 0.135 -- no debconf information
Bug#944258: lintian 2.32.0~bpo9+1 in stretch-backports depends on coreutils (>= 8.30), but stretch has only 8.26-3
Hi Chris, On Sun, Nov 10, 2019 at 10:06 AM Chris Lamb wrote: > > Felix, can you do the "honours" here? Was this not resolved by the following? https://salsa.debian.org/lintian/lintian/commit/33bd1434f0c160770a26bea55328e5bf7545322f As you can see, I marked the bug as closed. The BTS never switched to pending, presumably due to the version restriction via 'found'. Or, do I need to backport the patch to that specific version? Kind regards, Felix Lechner
Bug#943938: marked as done (tpm2-tss FTBFS: Makefile:15030: *** missing separator. Stop.)
Your message dated Sun, 10 Nov 2019 18:21:12 + with message-id and subject line Bug#943938: fixed in tpm2-tss 2.3.1-1 has caused the Debian Bug report #943938, regarding tpm2-tss FTBFS: Makefile:15030: *** missing separator. Stop. 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.) -- 943938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943938 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tpm2-tss Version: 2.1.0-4 Severity: serious Tags: ftbfs tpm2-tss fails to build from source: https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/tpm2-tss_2.1.0-4.rbuild.log.gz | dh_auto_build | make -j15 | make[2]: Entering directory '/build/1st/tpm2-tss-2.1.0' | Makefile:15030: *** missing separator. Stop. | make[2]: Leaving directory '/build/1st/tpm2-tss-2.1.0' | dh_auto_build: make -j15 returned exit code 2 | make[1]: *** [debian/rules:22: override_dh_auto_build] Error 255 | make[1]: Leaving directory '/build/1st/tpm2-tss-2.1.0' | make: *** [debian/rules:7: build] Error 2 | dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 This is also reproduced by crossqa: http://crossqa.debian.net/build/tpm2-tss_2.1.0-4_ppc64el_20190906172018.log Line 15030 of the Makefile contains "@CODE_COVERAGE_RULES@". Very likely, this line should have been substituted from Makefile.in, but the generate configure does not contain any substitutions for it. Hope this helps with diagnosing the issue Helmut --- End Message --- --- Begin Message --- Source: tpm2-tss Source-Version: 2.3.1-1 We believe that the bug you reported is fixed in the latest version of tpm2-tss, 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 943...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ying-Chun Liu (PaulLiu) (supplier of updated tpm2-tss 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, 10 Nov 2019 20:45:08 +0800 Source: tpm2-tss Binary: libtss2-dev libtss2-esys0 libtss2-esys0-dbgsym Architecture: source amd64 Version: 2.3.1-1 Distribution: unstable Urgency: low Maintainer: Mathieu Trudel-Lapierre Changed-By: Ying-Chun Liu (PaulLiu) Description: libtss2-dev - TPM2 Software stack library - development files libtss2-esys0 - TPM2 Software stack library - TSS and TCTI libraries Closes: 918973 940642 940643 941146 943938 Changes: tpm2-tss (2.3.1-1) unstable; urgency=low . * New upstream release - Can be build now. (Closes: #943938) - Drop 0001-test-fix-tpm2b-unit-tests-failing-on-big-endian.patch. Already upstreamed. * Depends on tpm-udev now. (Closes: #918973) - All the following are implemented in tpm-udev package instead. - mark libtss2-udev Multi-Arch: foreign (Closes: #941146) - call udevadm trigger after installing libtss2-udev (Closes: #940642) - /var/lib/tpm/ not owned by tss user/group (Closes: #940643) Checksums-Sha1: a49455337d49f2ce3a2fe29d07b58c33ab2bef67 2050 tpm2-tss_2.3.1-1.dsc 092125bb3b1a263600f599798b74910460db37b3 546196 tpm2-tss_2.3.1.orig.tar.gz 46f597e7a19012f043898c57e78efff5b16e3508 7992 tpm2-tss_2.3.1-1.debian.tar.xz 3fa34c1c5a00d9075dfc4146c08bd4a488f4f056 59428 libtss2-dev_2.3.1-1_amd64.deb d4c1cb770681dc6b4cd5f209d0ad7fe40700f852 852304 libtss2-esys0-dbgsym_2.3.1-1_amd64.deb 9fc2af4f56066ba9a92e747150ad485c3bd0ad30 236972 libtss2-esys0_2.3.1-1_amd64.deb 44420e621da491b940fff52ab154dd56eacf2097 6569 tpm2-tss_2.3.1-1_amd64.buildinfo Checksums-Sha256: 667e0d6df03df9ba7070a9e70953ed937d504d8f6f00614fcabea055d0b05321 2050 tpm2-tss_2.3.1-1.dsc da818b8cb82630f561ed088ef3204b243a8f1de680623a09d775deb6014c4c99 546196 tpm2-tss_2.3.1.orig.tar.gz 80fd385b8afd2b7aecbc78108af861cf7b2c8969b7b386acc1cc0f0be4e39a89 7992 tpm2-tss_2.3.1-1.debian.tar.xz af8f0fd8ba624332cb79b025b30dcb0cf89eab5ce47deea0a4855a4a5649892a 59428 libtss2-dev_2.3.1-1_amd64.deb 390be1a0064618565bff0af197befeb6e8c042424852a480b2bcc7cb3da7b02f 852304 libtss2-esys0-dbgsym_2.3.1-1_amd64.deb 31233affdbc293a84a7bc9b5d551a95a24ff0be102f6e415fb309f1fc255ab55 236972 libtss2-esys0_2.3.1-1_amd64.deb
Bug#918973: marked as done (udev rules and created user conflict with the one shipped in trousers package)
Your message dated Sun, 10 Nov 2019 18:21:11 + with message-id and subject line Bug#918973: fixed in tpm2-tss 2.3.1-1 has caused the Debian Bug report #918973, regarding udev rules and created user conflict with the one shipped in trousers package to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 918973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918973 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libtss2-udev Version: 2.1.0-3 Severity: serious Hello, The trousers package also contains udev rules for the tpm* devices (45-trousers.rules): KERNEL=="tpm[0-9]*", MODE="0600", OWNER="tss", GROUP="tss" This conflicts with the one shipped by libtss2-udev (60-libtss2-udev.rules): KERNEL=="tpm[0-9]*", MODE="0660", OWNER="tss" KERNEL=="tpmrm[0-9]*", MODE="0660", OWNER="tss", GROUP="tss" Also, the trousers package is creating the tss user with the following command: adduser --system --quiet --home /var/lib/tpm --shell /bin/false --no-create-home --group tss While libtss2-udev creates it with: adduser --system --ingroup tss --home /var/lib/libtss2-udev/tss --no-create-home --gecos "TPM2 software stack" tss Wouldn't it be better to create these at an higher level? Create a package being pulled by both the tpm(1) and tpm2 daemons? Kind regards, Laurent Bigonville -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy Versions of packages libtss2-udev depends on: ii adduser 3.118 libtss2-udev recommends no packages. libtss2-udev suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: tpm2-tss Source-Version: 2.3.1-1 We believe that the bug you reported is fixed in the latest version of tpm2-tss, 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 918...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ying-Chun Liu (PaulLiu) (supplier of updated tpm2-tss 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, 10 Nov 2019 20:45:08 +0800 Source: tpm2-tss Binary: libtss2-dev libtss2-esys0 libtss2-esys0-dbgsym Architecture: source amd64 Version: 2.3.1-1 Distribution: unstable Urgency: low Maintainer: Mathieu Trudel-Lapierre Changed-By: Ying-Chun Liu (PaulLiu) Description: libtss2-dev - TPM2 Software stack library - development files libtss2-esys0 - TPM2 Software stack library - TSS and TCTI libraries Closes: 918973 940642 940643 941146 943938 Changes: tpm2-tss (2.3.1-1) unstable; urgency=low . * New upstream release - Can be build now. (Closes: #943938) - Drop 0001-test-fix-tpm2b-unit-tests-failing-on-big-endian.patch. Already upstreamed. * Depends on tpm-udev now. (Closes: #918973) - All the following are implemented in tpm-udev package instead. - mark libtss2-udev Multi-Arch: foreign (Closes: #941146) - call udevadm trigger after installing libtss2-udev (Closes: #940642) - /var/lib/tpm/ not owned by tss user/group (Closes: #940643) Checksums-Sha1: a49455337d49f2ce3a2fe29d07b58c33ab2bef67 2050 tpm2-tss_2.3.1-1.dsc 092125bb3b1a263600f599798b74910460db37b3 546196 tpm2-tss_2.3.1.orig.tar.gz 46f597e7a19012f043898c57e78efff5b16e3508 7992 tpm2-tss_2.3.1-1.debian.tar.xz 3fa34c1c5a00d9075dfc4146c08bd4a488f4f056 59428 libtss2-dev_2.3.1-1_amd64.deb d4c1cb770681dc6b4cd5f209d0ad7fe40700f852 852304 libtss2-esys0-dbgsym_2.3.1-1_amd64.deb 9fc2af4f56066ba9a92e747150ad485c3bd0ad30 236972 libtss2-esys0_2.3.1-1_amd64.deb 44420e621da491b940fff52ab154dd56eacf2097 6569 tpm2-tss_2.3.1-1_amd64.buildinfo Checksums-Sha256: 667e0d6df03df9ba7070a9e70953ed937d504d8f6f00614fcabea055d0b05321 2050 tpm2-tss_2.3.1-1.dsc
Bug#944258: lintian 2.32.0~bpo9+1 in stretch-backports depends on coreutils (>= 8.30), but stretch has only 8.26-3
Hi, > lintian 2.32.0~bpo9+1 in stretch-backports depends on coreutils > (>= 8.30), but stretch has only 8.26-3 I'd like to resolve this issue and as a new upload of coreutils seems to be neither warranted, 100% essential and (practically-speaking) forthcoming, I would request that we do whatever we need to do to weaken this dependency. Felix, can you do the "honours" here? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#944486: libtrilinos-belos-dev: missing Breaks+Replaces: libtrilinos-muelu-dev (<< 12.14)
Package: libtrilinos-belos-dev Version: 12.14.1-1 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 .../libtrilinos-belos-dev_12.14.1-1_amd64.deb ... Unpacking libtrilinos-belos-dev:amd64 (12.14.1-1) ... dpkg: error processing archive /var/cache/apt/archives/libtrilinos-belos-dev_12.14.1-1_amd64.deb (--unpack): trying to overwrite '/usr/include/trilinos/BelosOperatorT.hpp', which is also in package libtrilinos-muelu-dev:amd64 12.12.1-8 Errors were encountered while processing: dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) /var/cache/apt/archives/libtrilinos-belos-dev_12.14.1-1_amd64.deb cheers, Andreas libtrilinos-muelu-dev=12.12.1-8_libtrilinos-belos-dev=12.14.1-1.log.gz Description: application/gzip
Bug#944484: siril-common: missing Breaks+Replaces: siril (<< 0.9.12)
Package: siril-common Version: 0.9.12-1 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 .../siril-common_0.9.12-1_all.deb ... Unpacking siril-common (0.9.12-1) ... dpkg: error processing archive /var/cache/apt/archives/siril-common_0.9.12-1_all.deb (--unpack): trying to overwrite '/usr/share/doc/siril/AUTHORS', which is also in package siril 0.9.11-1+b3 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/siril-common_0.9.12-1_all.deb cheers, Andreas siril=0.9.11-1+b3_siril-common=0.9.12-1.log.gz Description: application/gzip
Bug#930018: marked as done (phpmyadmin: should phpmyadmin removed from unstable?)
Your message dated Sun, 10 Nov 2019 18:20:26 +0100 with message-id <7663845e-077a-37e4-a7e2-84fe09d95...@wdes.fr> and subject line has caused the Debian Bug report #930018, regarding phpmyadmin: should phpmyadmin removed from unstable? 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.) -- 930018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930018 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: phpmyadmin Severity: serious Justification: unfit for a stable release Hi In meanwhile phpmyadmin could be removed from unstable without disturbing reverse dependencies. Should phpmyadmin be removed from the archive? Regards, Salvatore --- End Message --- --- Begin Message --- Version: 4:4.9.1+dfsg1-2--- End Message ---
Bug#944481: exim4: [Dummy bug] Enforce longer testing period for new upstream
Source: exim4 Version: 4.93~RC2-1 Severity: serious One of 4.93's changes | | JH/32 Introduce a general tainting mechanism for values read from the | input channel, and values derived from them. Refuse to expand any | tainted values, to catch one form of exploit. | has a relatively high potential for breaking stuff. Let's give this version some additional time for testing sid and delay migration to testing. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#933923: src:valinor: Incompatible with safe load changes in new pyyaml
Control: retitle -1 valinor: FTBFS and autopkgtest failure due to new version of pyyaml thanks
Processed: Re: src:valinor: Incompatible with safe load changes in new pyyaml
Processing control commands:
> retitle -1 valinor: FTBFS and autopkgtest failure due to new version of pyyaml
Bug #933923 {Done: Scott Kitterman } [src:valinor]
valinor: FTBFS and autopkgtest failure due to new
Changed Bug title to 'valinor: FTBFS and autopkgtest failure due to new version
of pyyaml' from 'valinor: FTBFS and autopkgtest failure due to new'.
--
933923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933923
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#940902: marked as done (doesn't read the data)
Your message dated Sun, 10 Nov 2019 16:49:38 + with message-id and subject line Bug#940902: fixed in cycle 0.3.1-17 has caused the Debian Bug report #940902, regarding doesn't read the data 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.) -- 940902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940902 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cycle Version: 0.3.1-16 Severity: grave Hi, This new version of cycle, ported to python3, doesn't read the data file ( under .cycle) and prompts to create a new user. Not creating a new user and downgrading to the version in buster (-14), allows to continue using the application with the previous data. Cheers, Ana --- End Message --- --- Begin Message --- Source: cycle Source-Version: 0.3.1-17 We believe that the bug you reported is fixed in the latest version of cycle, 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 940...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated cycle 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, 23 Sep 2019 09:31:51 +0200 Source: cycle Architecture: source Version: 0.3.1-17 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 940902 Changes: cycle (0.3.1-17) unstable; urgency=medium . * Team upload * Revert port to Python3 Closes: #940902 * Warn about future removal at login screen and in NEWS.Debian Checksums-Sha1: 31998391ffbdadba23c944057724bdb2eb15ad19 1945 cycle_0.3.1-17.dsc 040050c00c5c918134e668b37a89ff2064cf5b73 37952 cycle_0.3.1-17.debian.tar.xz bb9d60968df1fa197464278215ce86f9820c4cb3 5254 cycle_0.3.1-17_source.buildinfo Checksums-Sha256: 78639f4defc6d3f58801833a076e32ab54c3eca9595a82e8213d093c02ecf3d5 1945 cycle_0.3.1-17.dsc 502682a572afb94ef122f3570ae8ce6ba21516c50858f3f621f45179f741cb03 37952 cycle_0.3.1-17.debian.tar.xz 3782570c3a702d184615c4990e2ed0fba4a0eb5db08bb508de812750c2a649b7 5254 cycle_0.3.1-17_source.buildinfo Files: f2eca55bbc944139f56cfcb8faae0e3f 1945 utils optional cycle_0.3.1-17.dsc 2bda76c9d854fc5303f623055a56ca1f 37952 utils optional cycle_0.3.1-17.debian.tar.xz 2fa8e6b019d8f69af27d41a643788499 5254 utils optional cycle_0.3.1-17_source.buildinfo -BEGIN PGP SIGNATURE- Comment: Signed by Ana Guerrero iQIzBAEBCAAdFiEEejPsqhiLlvJ8kXKIs0ZPiWqhWUgFAl3IPI4ACgkQs0ZPiWqh WUgaeA//faI9++ME9aNAmNGvzu+jF/OKB0c9Il4uJZuB3Nk9o5cVAiGmHvR/tcpb Ya7BxHNuyz4k5H8xBgbo1W7xUqgWNHp4yT5Pvv5tWcvgR44mrKGBso92dsK22/pC lhoPBL/WNdk253pjQcz3Vc1IdIr60pHwdsF6usCSj1L/kWEhYQ2FDQnM5oswbnoX RwXOM51CKdjAIanLWh+CG8AXacvFn10+Fke5xRYdIirFJJT4seJosm8bBGFwvRJt WGOEPyyIb54snKZijNryMXYwLBQfw1KCj46gTj+NUKNHeXkcKYk6liirY3FxUh+K OAWw5xQhNjJemGpc4HVpDEowlYmlDk1b7i+96N+u4ggRReSYgJVrNiCe97x3mHVF gn95wsVUlNcB4TJsL2vKjwuiYcPCRSnUAyQxbh24vCxPEq6wdJ0lPOy2eDHQ5QEB zTFVDZjJ06jlveDoUj+toEh1+OGrzersox+vY2lDFYf7jDkJDyFjRzD0GHa2jAzv nTTxuSZb1OCxHrKihl2gDgA1g4ki1eP7QPC79xXy7qP7to7gp/jcpg0vXyyR6NoF Uxc5fTBwkfzuLNPwRduLjnvCdf3lSc1GC9W+EXXh+L2c0/OaIAuReNPkw4WJyYF/ /CaISpvLlpFI/GF5fSSgTml2qQcEJrY6TAsrtM8/nbwwBe2ytdA= =PkiT -END PGP SIGNATURE End Message ---
Bug#940902: doesn't read the data
On Tue, Oct 01, 2019 at 06:12:56AM +0200, Andreas Tille wrote: > On Mon, Sep 30, 2019 at 11:47:14PM +0200, Ana Guerrero Lopez wrote: > > > Thanks to you. I'd be happy if you could check master[1] and confirm > > > that it is OK. I can even give you commit permissions so you can change > > > anything you feel sensible and do the team upload yourself. > > > > Please, add me to the group, I'll take care of the testing and upload. > > Welcome to the team, Andreas. Thanks! Good news, I've tested and it works fine. I'm doing a team upload right now. I think we shouldn't give up in getting this ported to python3, but I think a re-write keeping the possibility to read the all data is the best way to go. Cheers, Ana
Bug#933923: src:valinor: Incompatible with safe load changes in new pyyaml
Control: retitle -1 valinor: FTBFS and autopkgtest failure due to new version of pyyaml thanks
Processed: Re: src:valinor: Incompatible with safe load changes in new pyyaml
Processing control commands:
> retitle -1 valinor: FTBFS and autopkgtest failure due to new
Bug #933923 {Done: Scott Kitterman } [src:valinor]
src:valinor: Incompatible with safe load changes in new pyyaml
Changed Bug title to 'valinor: FTBFS and autopkgtest failure due to new' from
'src:valinor: Incompatible with safe load changes in new pyyaml'.
--
933923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933923
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#944474: autopkg tests fail on 32bit architectures
Package: src:openblas Version: 0.3.7+ds-3 Severity: serious Tags: sid bullseye patch The autopkg tests fail on 32bit architectures, because the 64bit packages are not available. Feel free to extend the list of 32bit archs to other architectures. http://launchpadlibrarian.net/450747895/openblas_0.3.7+ds-3_0.3.7+ds-3ubuntu1.diff.gz
Bug#944473: botch: build-dependency not satisfiable in sio
Source: botch Version: 0.21-8 Tags: ftbfs Severity: serious User: trei...@debian.org Usertags: edos-uninstallable Hi, botch build-depends on libcdt5 << 2.40.1.0~ but the current version of libcdt5 in sid is 2.42.2-3. -Ralf.
Bug#933923: src:valinor: Incompatible with safe load changes in new pyyaml
retitle -1 valinor: FTBFS and autopkgtest failure due to new version of pyyaml thanks
Bug#932777: marked as done (scotch: 6.0.8 FTBFS: segfault in test_scotch_graph_order bump_b1.grf)
Your message dated Sun, 10 Nov 2019 15:40:14 + with message-id and subject line Bug#932777: fixed in scotch 6.0.9-1 has caused the Debian Bug report #932777, regarding scotch: 6.0.8 FTBFS: segfault in test_scotch_graph_order bump_b1.grf 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.) -- 932777: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932777 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: scotch Version: 6.0.7-1 Severity: normal Forwarded: https://gforge.inria.fr/tracker/index.php?func=detail=21768_id=248=1079 Scotch 6.0.7 FTBFS on most arches, see https://buildd.debian.org/status/package.php?p=scotch=experimental The error message looks like: mpicc -g -O2 -fdebug-prefix-map=/<>/src/check=. -fstack-protector-strong -Wformat -Werror=format-security -O3 -fPIC -I. -I/usr/include/mpi -Drestrict=__restrict -DCOMMON_FILE_COMPRESS_GZ -DCOMMON_FILE_COMPRESS_BZ2 -DCOMMON_FILE_COMPRESS_LZMA -DCOMMON_PTHREAD -DSCOTCH_PTHREAD_NUMBER=2 -DCOMMON_RANDOM_FIXED_SEED -DSCOTCH_RENAME -DSCOTCH_RENAME_PARSER -DCOMMON_PTHREAD_AFFINITY_LINUX -DINTSIZE64 -I../../include -L../../lib test_libmetis.c -o test_libmetis -lscotchmetis -lscotch -lscotcherr -Wl,-z,relro -pthread -lz -lbz2 -llzma -lm -lrt ./test_libmetis data/bump.grf ./test_libmetis data/bump_b1.grf munmap_chunk(): invalid pointer make[3]: *** [Makefile:206: check_libmetis] Aborted test_libmetis is new in 6.0.7 but the test failure seems to be localised in the sense that only bump_b1.grf fails. test_libmetis succeeds on bump.grf and bump_imbal_32.grf. bump_b1.grf passes on ppc64el, hppa and m68k. Debian patch skip_failing_tests.patch has been prepared to skip test_libmetis bump_b1.grf. But waiting to hear back from upstrea https://gforge.inria.fr/tracker/index.php?func=detail=21768_id=248=1079 to hear whether the failure indicates a bigger problem in 6.0.7, meaning we should keep 6.0.6 for the time being. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages scotch depends on: ii libbz2-1.0 1.0.6-9.2 ii libc6 2.28-10 ii liblzma5 5.2.4-1 ii libopenmpi33.1.3-11 ii libscotch-6.0 6.0.6-2 ii zlib1g 1:1.2.11.dfsg-1 scotch recommends no packages. scotch suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: scotch Source-Version: 6.0.9-1 We believe that the bug you reported is fixed in the latest version of scotch, 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 932...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Drew Parsons (supplier of updated scotch package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 10 Nov 2019 23:57:57 +0900 Source: scotch Architecture: source Version: 6.0.9-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Drew Parsons Closes: 932777 940176 Changes: scotch (6.0.9-1) unstable; urgency=medium . * Team upload. * New upstream release. - fixes bump_b1.grf tests. Closes: #932777. Drop debian patch skip_failing_tests.patch. * skip build-time tests if nocheck is set in DEB_BUILD_OPTIONS * drop VERSION,RELEASE,PATCHLEVEL from debian Makefile.inc files (VERSION is defined in src/Makefile) - update debian patch build-fixes.patch to build metis and esmumps component libraries with soname VERSION. Closes: #940176. * drop -I/usr/include/mpi from CFLAGS_COMMON in debian/rules (defunct non-multiarch path, and MPI path is now provided by mpicc) * ignore missing OpenFabrics transports in debian/tests (set MCA btl_base_warn_component_unused to 0) * Standards-Version:
Bug#920822: marked as done (phpmyadmin: CVE-2019-6798: PMASA-2019-2)
Your message dated Sun, 10 Nov 2019 15:38:18 + with message-id and subject line Bug#920822: fixed in phpmyadmin 4:4.9.1+dfsg1-2 has caused the Debian Bug report #920822, regarding phpmyadmin: CVE-2019-6798: PMASA-2019-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.) -- 920822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920822 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: phpmyadmin Version: 4:4.6.6-5 Severity: grave Tags: security upstream Control: found -1 4:4.6.6-4 Hi, The following vulnerability was published for phpmyadmin. CVE-2019-6798[0]: | An issue was discovered in phpMyAdmin before 4.8.5. A vulnerability was | reported where a specially crafted username can be used to trigger a | SQL injection attack through the designer feature. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-6798 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6798 [1] https://www.phpmyadmin.net/security/PMASA-2019-2/ Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: phpmyadmin Source-Version: 4:4.9.1+dfsg1-2 We believe that the bug you reported is fixed in the latest version of phpmyadmin, 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 920...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Blümel (supplier of updated phpmyadmin package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 01 Nov 2019 19:33:40 +0100 Source: phpmyadmin Architecture: source Version: 4:4.9.1+dfsg1-2 Distribution: unstable Urgency: medium Maintainer: phpMyAdmin Packaging Team Changed-By: Matthias Blümel Closes: 772741 883417 884827 890595 893539 896490 914673 917755 920822 920823 930017 930048 943209 Changes: phpmyadmin (4:4.9.1+dfsg1-2) unstable; urgency=medium . * Adjust open_basedir setting for ubuntu eoan . phpmyadmin (4:4.9.1+dfsg1-1) unstable; urgency=medium . * New upstream version 4.9.1. * Remove webbased setup (Closes: #772741) * Check for weak blowfish key and regenerate if necessary during update * fix avahi service-installation (Closes: #914673, LP: #1293558) * fix bug in sql-script for non-default tablename (Closes: #884827) . phpmyadmin (4:4.9.0.1+dfsg1-1) unstable; urgency=medium . [ Matthias Blümel ] * New upstream version 4.9.0.1. * Update Package for new composer-oriented structure in upstream * Update Traslations - Catalan - Ukrainian - Chinese (Traditional) * New Translations - Romanian - Indonesian * New upstream release, fixing several security issues: - Warings when running under php 7.2 (Closes: #890595) - FTBFS with phpunit 6.4.4-2 (Closes: #883417, Closes: #917755) - Bypass $cfg['Servers'][$i]['AllowNoPassword'] (PMASA-2017-8, CVE-2017-18264) - XSRF/CSRF vulnerability in phpMyAdmin (PMASA-2017-9, CVE-2017-1000499) - Self XSS in central columns feature (PMASA-2018-1, CVE-2018-7260, Closes: #893539) - CSRF vulnerability allowing arbitrary SQL execution (PMASA-2018-2, CVE-2018-10188, Closes: #896490) - XSS in Designer feature (PMASA-2018-3, CVE-2018-12581) - Bug that can be used for XSS when importing files - Local file inclusion (PMASA-2018-6, CVE-2018-19968) - XSRF/CSRF vulnerabilities allowing a to perform harmful operations (PMASA-2018-7, CVE-2018-19969) - an XSS vulnerability in the navigation tree (PMASA-2018-8, CVE-2018-19970) - Arbitrary file read vulnerability (PMASA-2019-1, CVE-2019-6799, Closes: #920823) - SQL injection in the Designer interface (PMASA-2019-2, CVE-2019-6798, Closes: #920822) - SQL injection in Designer feature (PMASA-2019-3, CVE-2019-11768, Closes: #930048)) - CSRF vulnerability in login form (PMASA-2019-4, CVE-2019-12616, Closes: #930017) * patch to
Bug#930017: marked as done (phpmyadmin: CVE-2019-12616: PMASA-2019-4)
Your message dated Sun, 10 Nov 2019 15:38:18 + with message-id and subject line Bug#930017: fixed in phpmyadmin 4:4.9.1+dfsg1-2 has caused the Debian Bug report #930017, regarding phpmyadmin: CVE-2019-12616: PMASA-2019-4 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.) -- 930017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930017 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: phpmyadmin Version: 4:4.6.6-4 Severity: grave Tags: security upstream Justification: user security hole Control: found -1 4:4.6.6-5 Hi, The following vulnerability was published for phpmyadmin. CVE-2019-12616[0]: | An issue was discovered in phpMyAdmin before 4.9.0. A vulnerability | was found that allows an attacker to trigger a CSRF attack against a | phpMyAdmin user. The attacker can trick the user, for instance through | a broken img tag pointing at the victim's phpMyAdmin database, | and the attacker can potentially deliver a payload (such as a specific | INSERT or DELETE statement) to the victim. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-12616 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12616 [1] https://www.phpmyadmin.net/security/PMASA-2019-4/ Regards, Salvatore --- End Message --- --- Begin Message --- Source: phpmyadmin Source-Version: 4:4.9.1+dfsg1-2 We believe that the bug you reported is fixed in the latest version of phpmyadmin, 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 930...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Blümel (supplier of updated phpmyadmin package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 01 Nov 2019 19:33:40 +0100 Source: phpmyadmin Architecture: source Version: 4:4.9.1+dfsg1-2 Distribution: unstable Urgency: medium Maintainer: phpMyAdmin Packaging Team Changed-By: Matthias Blümel Closes: 772741 883417 884827 890595 893539 896490 914673 917755 920822 920823 930017 930048 943209 Changes: phpmyadmin (4:4.9.1+dfsg1-2) unstable; urgency=medium . * Adjust open_basedir setting for ubuntu eoan . phpmyadmin (4:4.9.1+dfsg1-1) unstable; urgency=medium . * New upstream version 4.9.1. * Remove webbased setup (Closes: #772741) * Check for weak blowfish key and regenerate if necessary during update * fix avahi service-installation (Closes: #914673, LP: #1293558) * fix bug in sql-script for non-default tablename (Closes: #884827) . phpmyadmin (4:4.9.0.1+dfsg1-1) unstable; urgency=medium . [ Matthias Blümel ] * New upstream version 4.9.0.1. * Update Package for new composer-oriented structure in upstream * Update Traslations - Catalan - Ukrainian - Chinese (Traditional) * New Translations - Romanian - Indonesian * New upstream release, fixing several security issues: - Warings when running under php 7.2 (Closes: #890595) - FTBFS with phpunit 6.4.4-2 (Closes: #883417, Closes: #917755) - Bypass $cfg['Servers'][$i]['AllowNoPassword'] (PMASA-2017-8, CVE-2017-18264) - XSRF/CSRF vulnerability in phpMyAdmin (PMASA-2017-9, CVE-2017-1000499) - Self XSS in central columns feature (PMASA-2018-1, CVE-2018-7260, Closes: #893539) - CSRF vulnerability allowing arbitrary SQL execution (PMASA-2018-2, CVE-2018-10188, Closes: #896490) - XSS in Designer feature (PMASA-2018-3, CVE-2018-12581) - Bug that can be used for XSS when importing files - Local file inclusion (PMASA-2018-6, CVE-2018-19968) - XSRF/CSRF vulnerabilities allowing a to perform harmful operations (PMASA-2018-7, CVE-2018-19969) - an XSS vulnerability in the navigation tree (PMASA-2018-8, CVE-2018-19970) - Arbitrary file read vulnerability (PMASA-2019-1, CVE-2019-6799, Closes: #920823) - SQL injection in the Designer interface (PMASA-2019-2, CVE-2019-6798, Closes: #920822) - SQL injection in
Bug#917755: marked as done (phpmyadmin: FTBFS: PHP Fatal error: Uncaught Error: Class 'PHPUnit_Framework_TestCase' not found in /<>/test/PMATestCase.php:14)
Your message dated Sun, 10 Nov 2019 15:38:18 +
with message-id
and subject line Bug#917755: fixed in phpmyadmin 4:4.9.1+dfsg1-2
has caused the Debian Bug report #917755,
regarding phpmyadmin: FTBFS: PHP Fatal error: Uncaught Error: Class
'PHPUnit_Framework_TestCase' not found in
/<>/test/PMATestCase.php:14
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.)
--
917755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917755
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: phpmyadmin
Version: 4:4.6.6-5
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # We exclude:
> # - selenium tests as the setup would be too complex
> # - some network based tests
> LC_ALL=en_US.UTF-8 phpunit --config phpunit.xml.nocoverage --exclude-group
> selenium --exclude-group network
> No headers testing.
> Please install runkit and enable runkit.internal_override!
> PHP Fatal error: Uncaught Error: Class 'PHPUnit_Framework_TestCase' not
> found in /<>/test/PMATestCase.php:14
> Stack trace:
> #0 /<>/test/classes/AdvisorTest.php(13): require_once()
> #1 /usr/share/php/PHPUnit/Util/FileLoader.php(57):
> include_once('/build/phpmyadm...')
> #2 /usr/share/php/PHPUnit/Util/FileLoader.php(45):
> PHPUnit\Util\FileLoader::load('/build/phpmyadm...')
> #3 /usr/share/php/PHPUnit/Framework/TestSuite.php(540):
> PHPUnit\Util\FileLoader::checkAndLoad('/build/phpmyadm...')
> #4 /usr/share/php/PHPUnit/Framework/TestSuite.php(618):
> PHPUnit\Framework\TestSuite->addTestFile('/build/phpmyadm...')
> #5 /usr/share/php/PHPUnit/Util/Configuration.php(1137):
> PHPUnit\Framework\TestSuite->addTestFiles(Array)
> #6 /usr/share/php/PHPUnit/Util/Configuration.php(1003):
> PHPUnit\Util\Configuration->getTestSuite(Object(DOMElement), Array)
> #7 /usr/share/php/PHPUnit/TextUI/Command.php(902):
> PHPUnit\Util\Configuration->getTestSuiteConfiguration('')
> #8 /usr/share/php/PHPUnit in /<>/test/PMATestCase.php on line 14
> make[1]: *** [debian/rules:14: override_dh_auto_test] Error 255
The full build log is available from:
http://aws-logs.debian.net/2018/12/29/phpmyadmin_4.6.6-5_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: phpmyadmin
Source-Version: 4:4.9.1+dfsg1-2
We believe that the bug you reported is fixed in the latest version of
phpmyadmin, 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 917...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Matthias Blümel (supplier of updated phpmyadmin package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 01 Nov 2019 19:33:40 +0100
Source: phpmyadmin
Architecture: source
Version: 4:4.9.1+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: phpMyAdmin Packaging Team
Changed-By: Matthias Blümel
Closes: 772741 883417 884827 890595 893539 896490 914673 917755 920822 920823
930017 930048 943209
Changes:
phpmyadmin (4:4.9.1+dfsg1-2) unstable; urgency=medium
.
* Adjust open_basedir setting for ubuntu eoan
.
phpmyadmin (4:4.9.1+dfsg1-1) unstable; urgency=medium
.
* New upstream version 4.9.1.
* Remove webbased setup (Closes: #772741)
* Check for weak blowfish key and regenerate if necessary during update
* fix avahi service-installation (Closes: #914673, LP: #1293558)
* fix bug in sql-script for non-default tablename (Closes: #884827)
.
phpmyadmin (4:4.9.0.1+dfsg1-1) unstable; urgency=medium
.
[ Matthias Blümel ]
* New upstream version 4.9.0.1.
* Update Package for new composer-oriented structure in upstream
* Update Traslations
- Catalan
- Ukrainian
- Chinese
Bug#930048: marked as done (phpmyadmin: CVE-2019-11768: PMASA-2019-3)
Your message dated Sun, 10 Nov 2019 15:38:18 + with message-id and subject line Bug#930048: fixed in phpmyadmin 4:4.9.1+dfsg1-2 has caused the Debian Bug report #930048, regarding phpmyadmin: CVE-2019-11768: PMASA-2019-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.) -- 930048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930048 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: phpmyadmin Version: 4:4.6.6-4 Severity: grave Tags: security upstream Justification: user security hole Control: found -1 4:4.6.6-3 Hi, The following vulnerability was published for phpmyadmin. CVE-2019-11768[0]: | An issue was discovered in phpMyAdmin before 4.9.0.1. A vulnerability | was reported where a specially crafted database name can be used to | trigger an SQL injection attack through the designer feature. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-11768 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11768 [1] https://www.phpmyadmin.net/security/PMASA-2019-3/ Regards, Salvatore --- End Message --- --- Begin Message --- Source: phpmyadmin Source-Version: 4:4.9.1+dfsg1-2 We believe that the bug you reported is fixed in the latest version of phpmyadmin, 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 930...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Blümel (supplier of updated phpmyadmin package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 01 Nov 2019 19:33:40 +0100 Source: phpmyadmin Architecture: source Version: 4:4.9.1+dfsg1-2 Distribution: unstable Urgency: medium Maintainer: phpMyAdmin Packaging Team Changed-By: Matthias Blümel Closes: 772741 883417 884827 890595 893539 896490 914673 917755 920822 920823 930017 930048 943209 Changes: phpmyadmin (4:4.9.1+dfsg1-2) unstable; urgency=medium . * Adjust open_basedir setting for ubuntu eoan . phpmyadmin (4:4.9.1+dfsg1-1) unstable; urgency=medium . * New upstream version 4.9.1. * Remove webbased setup (Closes: #772741) * Check for weak blowfish key and regenerate if necessary during update * fix avahi service-installation (Closes: #914673, LP: #1293558) * fix bug in sql-script for non-default tablename (Closes: #884827) . phpmyadmin (4:4.9.0.1+dfsg1-1) unstable; urgency=medium . [ Matthias Blümel ] * New upstream version 4.9.0.1. * Update Package for new composer-oriented structure in upstream * Update Traslations - Catalan - Ukrainian - Chinese (Traditional) * New Translations - Romanian - Indonesian * New upstream release, fixing several security issues: - Warings when running under php 7.2 (Closes: #890595) - FTBFS with phpunit 6.4.4-2 (Closes: #883417, Closes: #917755) - Bypass $cfg['Servers'][$i]['AllowNoPassword'] (PMASA-2017-8, CVE-2017-18264) - XSRF/CSRF vulnerability in phpMyAdmin (PMASA-2017-9, CVE-2017-1000499) - Self XSS in central columns feature (PMASA-2018-1, CVE-2018-7260, Closes: #893539) - CSRF vulnerability allowing arbitrary SQL execution (PMASA-2018-2, CVE-2018-10188, Closes: #896490) - XSS in Designer feature (PMASA-2018-3, CVE-2018-12581) - Bug that can be used for XSS when importing files - Local file inclusion (PMASA-2018-6, CVE-2018-19968) - XSRF/CSRF vulnerabilities allowing a to perform harmful operations (PMASA-2018-7, CVE-2018-19969) - an XSS vulnerability in the navigation tree (PMASA-2018-8, CVE-2018-19970) - Arbitrary file read vulnerability (PMASA-2019-1, CVE-2019-6799, Closes: #920823) - SQL injection in the Designer interface (PMASA-2019-2, CVE-2019-6798, Closes: #920822) - SQL injection in Designer feature (PMASA-2019-3, CVE-2019-11768, Closes: #930048)) - CSRF vulnerability in login form (PMASA-2019-4, CVE-2019-12616, Closes: #930017) * patch to allow twig in
Bug#920823: marked as done (phpmyadmin: CVE-2019-6799: PMASA-2019-1)
Your message dated Sun, 10 Nov 2019 15:38:18 + with message-id and subject line Bug#920823: fixed in phpmyadmin 4:4.9.1+dfsg1-2 has caused the Debian Bug report #920823, regarding phpmyadmin: CVE-2019-6799: PMASA-2019-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.) -- 920823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920823 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: phpmyadmin Version: 4:4.6.6-5 Severity: grave Tags: security upstream Control: found -1 4:4.6.6-4 Hi, The following vulnerability was published for phpmyadmin. CVE-2019-6799[0]: | An issue was discovered in phpMyAdmin before 4.8.5. When the | AllowArbitraryServer configuration setting is set to true, with the use | of a rogue MySQL server, an attacker can read any file on the server | that the web server's user can access. This is related to the | mysql.allow_local_infile PHP configuration, and the inadvertent | ignoring of "options(MYSQLI_OPT_LOCAL_INFILE" calls. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-6799 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6799 [1] https://www.phpmyadmin.net/security/PMASA-2019-1/ Regards, Salvatore --- End Message --- --- Begin Message --- Source: phpmyadmin Source-Version: 4:4.9.1+dfsg1-2 We believe that the bug you reported is fixed in the latest version of phpmyadmin, 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 920...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Blümel (supplier of updated phpmyadmin package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 01 Nov 2019 19:33:40 +0100 Source: phpmyadmin Architecture: source Version: 4:4.9.1+dfsg1-2 Distribution: unstable Urgency: medium Maintainer: phpMyAdmin Packaging Team Changed-By: Matthias Blümel Closes: 772741 883417 884827 890595 893539 896490 914673 917755 920822 920823 930017 930048 943209 Changes: phpmyadmin (4:4.9.1+dfsg1-2) unstable; urgency=medium . * Adjust open_basedir setting for ubuntu eoan . phpmyadmin (4:4.9.1+dfsg1-1) unstable; urgency=medium . * New upstream version 4.9.1. * Remove webbased setup (Closes: #772741) * Check for weak blowfish key and regenerate if necessary during update * fix avahi service-installation (Closes: #914673, LP: #1293558) * fix bug in sql-script for non-default tablename (Closes: #884827) . phpmyadmin (4:4.9.0.1+dfsg1-1) unstable; urgency=medium . [ Matthias Blümel ] * New upstream version 4.9.0.1. * Update Package for new composer-oriented structure in upstream * Update Traslations - Catalan - Ukrainian - Chinese (Traditional) * New Translations - Romanian - Indonesian * New upstream release, fixing several security issues: - Warings when running under php 7.2 (Closes: #890595) - FTBFS with phpunit 6.4.4-2 (Closes: #883417, Closes: #917755) - Bypass $cfg['Servers'][$i]['AllowNoPassword'] (PMASA-2017-8, CVE-2017-18264) - XSRF/CSRF vulnerability in phpMyAdmin (PMASA-2017-9, CVE-2017-1000499) - Self XSS in central columns feature (PMASA-2018-1, CVE-2018-7260, Closes: #893539) - CSRF vulnerability allowing arbitrary SQL execution (PMASA-2018-2, CVE-2018-10188, Closes: #896490) - XSS in Designer feature (PMASA-2018-3, CVE-2018-12581) - Bug that can be used for XSS when importing files - Local file inclusion (PMASA-2018-6, CVE-2018-19968) - XSRF/CSRF vulnerabilities allowing a to perform harmful operations (PMASA-2018-7, CVE-2018-19969) - an XSS vulnerability in the navigation tree (PMASA-2018-8, CVE-2018-19970) - Arbitrary file read vulnerability (PMASA-2019-1, CVE-2019-6799, Closes: #920823) - SQL injection in the Designer interface (PMASA-2019-2, CVE-2019-6798, Closes: #920822) - SQL injection in Designer feature (PMASA-2019-3,
Bug#890595: marked as done (phpmyadmin: warnings when running under php 7.2, apparently fixed by new upstream series 4.7.x)
Your message dated Sun, 10 Nov 2019 15:38:18 + with message-id and subject line Bug#890595: fixed in phpmyadmin 4:4.9.1+dfsg1-2 has caused the Debian Bug report #890595, regarding phpmyadmin: warnings when running under php 7.2, apparently fixed by new upstream series 4.7.x 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.) -- 890595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890595 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: phpmyadmin Version: 4:4.6.6-5 Severity: important Hi, Now that php 7.2 is default, phpmyadmin is printing some warnings like this: Warning in ./libraries/sql.lib.php#613 count(): Parameter must be an array or an object that implements Countable According to upstream these are fixed in the 4.7 series[1][2] [1]https://www.phpmyadmin.net/news/2017/8/24/phpmyadmin-474-released/ [2]https://www.phpmyadmin.net/news/2017/12/23/phpmyadmin-477-released/ It would be great to have phpmyadmin updated to the latest upsteam so we have php 7.2 compat. Thanks! -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages phpmyadmin depends on: ii dbconfig-common 2.0.9 ii dbconfig-mysql 2.0.9 ii debconf [debconf-2.0] 1.5.65 ii libjs-sphinxdoc 1.6.7-1 ii perl5.26.1-4+b1 ii php 1:7.2+60 ii php-mbstring1:7.2+60 ii php-mysql 1:7.2+60 ii php-php-gettext 1.0.12-0.1 ii php-phpseclib 2.0.9-1 ii php-xml 1:7.2+60 ii php7.0-cli [php-cli]7.0.27-1 ii php7.0-json [php-json] 7.0.27-1 ii php7.0-mbstring [php-mbstring] 7.0.27-1 ii php7.0-mysql [php-mysqli] 7.0.27-1 ii php7.0-xml [php-xml]7.0.27-1 ii php7.2 [php]7.2.2-1 ii php7.2-cli [php-cli]7.2.2-1 ii php7.2-json [php-json] 7.2.2-1 ii php7.2-mbstring [php-mbstring] 7.2.2-1 ii php7.2-mysql [php-mysqli] 7.2.2-1 ii php7.2-xml [php-xml]7.2.2-1 ii ucf 3.0036 Versions of packages phpmyadmin recommends: ii apache2 [httpd] 2.4.29-2 ii php-bz2 1:7.2+60 ii php-curl1:7.2+60 ii php-gd 1:7.2+60 ii php-tcpdf 6.2.13+dfsg-1 ii php-zip 1:7.2+60 ii php7.0-bz2 [php-bz2]7.0.27-1 ii php7.0-curl [php-curl] 7.0.27-1 ii php7.0-gd [php-gd] 7.0.27-1 ii php7.0-zip [php-zip]7.0.27-1 ii php7.2-bz2 [php-bz2]7.2.2-1 ii php7.2-curl [php-curl] 7.2.2-1 ii php7.2-gd [php-gd] 7.2.2-1 ii php7.2-zip [php-zip]7.2.2-1 Versions of packages phpmyadmin suggests: ii firefox-esr [www-browser]52.6.0esr-2 ii google-chrome-stable [www-browser] 64.0.3282.167-1 ii mysql-server-5.7 [virtual-mysql-server] 5.7.21-1 -- debconf information: phpmyadmin/dbconfig-remove: true phpmyadmin/remote/newhost: phpmyadmin/db/app-user: phpmyadmin@localhost phpmyadmin/remove-error: abort phpmyadmin/dbconfig-reinstall: false * phpmyadmin/mysql/admin-user: debian-sys-maint phpmyadmin/missing-db-package-error: abort phpmyadmin/db/dbname: phpmyadmin phpmyadmin/setup-username: admin phpmyadmin/dbconfig-upgrade: true phpmyadmin/remote/port: phpmyadmin/purge: false * phpmyadmin/dbconfig-install: true phpmyadmin/upgrade-backup: true phpmyadmin/passwords-do-not-match: phpmyadmin/mysql/method: Unix socket phpmyadmin/internal/skip-preseed: false phpmyadmin/database-type: mysql phpmyadmin/install-error: abort phpmyadmin/remote/host: localhost phpmyadmin/upgrade-error: abort phpmyadmin/internal/reconfiguring: false * phpmyadmin/reconfigure-webserver: apache2 --- End Message --- --- Begin Message --- Source: phpmyadmin Source-Version: 4:4.9.1+dfsg1-2 We believe that the bug you reported is fixed in the latest version of phpmyadmin, 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
Bug#883417: marked as done (phpmyadmin FTBFS with phpunit 6.4.4-2)
Your message dated Sun, 10 Nov 2019 15:38:18 + with message-id and subject line Bug#883417: fixed in phpmyadmin 4:4.9.1+dfsg1-2 has caused the Debian Bug report #883417, regarding phpmyadmin FTBFS with phpunit 6.4.4-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.) -- 883417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883417 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: phpmyadmin Version: 4:4.6.6-5 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/phpmyadmin.html ... debian/rules override_dh_auto_test make[1]: Entering directory '/build/1st/phpmyadmin-4.6.6' # We exclude: # - selenium tests as the setup would be too complex # - some network based tests LC_ALL=en_US.UTF-8 phpunit --config phpunit.xml.nocoverage --exclude-group selenium --exclude-group network No headers testing. Please install runkit and enable runkit.internal_override! PHP Fatal error: Class 'PHPUnit_Framework_TestCase' not found in /build/1st/phpmyadmin-4.6.6/test/PMATestCase.php on line 14 debian/rules:11: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 255 --- End Message --- --- Begin Message --- Source: phpmyadmin Source-Version: 4:4.9.1+dfsg1-2 We believe that the bug you reported is fixed in the latest version of phpmyadmin, 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 883...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Blümel (supplier of updated phpmyadmin package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 01 Nov 2019 19:33:40 +0100 Source: phpmyadmin Architecture: source Version: 4:4.9.1+dfsg1-2 Distribution: unstable Urgency: medium Maintainer: phpMyAdmin Packaging Team Changed-By: Matthias Blümel Closes: 772741 883417 884827 890595 893539 896490 914673 917755 920822 920823 930017 930048 943209 Changes: phpmyadmin (4:4.9.1+dfsg1-2) unstable; urgency=medium . * Adjust open_basedir setting for ubuntu eoan . phpmyadmin (4:4.9.1+dfsg1-1) unstable; urgency=medium . * New upstream version 4.9.1. * Remove webbased setup (Closes: #772741) * Check for weak blowfish key and regenerate if necessary during update * fix avahi service-installation (Closes: #914673, LP: #1293558) * fix bug in sql-script for non-default tablename (Closes: #884827) . phpmyadmin (4:4.9.0.1+dfsg1-1) unstable; urgency=medium . [ Matthias Blümel ] * New upstream version 4.9.0.1. * Update Package for new composer-oriented structure in upstream * Update Traslations - Catalan - Ukrainian - Chinese (Traditional) * New Translations - Romanian - Indonesian * New upstream release, fixing several security issues: - Warings when running under php 7.2 (Closes: #890595) - FTBFS with phpunit 6.4.4-2 (Closes: #883417, Closes: #917755) - Bypass $cfg['Servers'][$i]['AllowNoPassword'] (PMASA-2017-8, CVE-2017-18264) - XSRF/CSRF vulnerability in phpMyAdmin (PMASA-2017-9, CVE-2017-1000499) - Self XSS in central columns feature (PMASA-2018-1, CVE-2018-7260, Closes: #893539) - CSRF vulnerability allowing arbitrary SQL execution (PMASA-2018-2, CVE-2018-10188, Closes: #896490) - XSS in Designer feature (PMASA-2018-3, CVE-2018-12581) - Bug that can be used for XSS when importing files - Local file inclusion (PMASA-2018-6, CVE-2018-19968) - XSRF/CSRF vulnerabilities allowing a to perform harmful operations (PMASA-2018-7, CVE-2018-19969) - an XSS vulnerability in the navigation tree (PMASA-2018-8, CVE-2018-19970) - Arbitrary file read vulnerability (PMASA-2019-1, CVE-2019-6799, Closes: #920823) - SQL injection in the Designer interface (PMASA-2019-2, CVE-2019-6798, Closes: #920822) - SQL injection in Designer feature (PMASA-2019-3, CVE-2019-11768, Closes: #930048)) - CSRF vulnerability in login form (PMASA-2019-4, CVE-2019-12616, Closes: #930017) * patch to allow twig in version 2 * adjust autoload path
Bug#939961: marked as done (FTBFS with OCaml 4.08.0 (safe strings))
Your message dated Sun, 10 Nov 2019 14:53:49 + with message-id and subject line Bug#939961: fixed in haxe 1:4.0.1-1 has caused the Debian Bug report #939961, regarding FTBFS with OCaml 4.08.0 (safe strings) 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.) -- 939961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939961 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:haxe Version: 1:3.4.7-1 Severity: important User: debian-ocaml-ma...@lists.debian.org Usertags: ocaml-4.08-transition Dear Maintainer, You package haxe FTBFS with OCaml 4.08.0 because -safe-string is now the default. Full log: https://ocaml.debian.net/transitions/ocaml-4.08.0/pool/haxe.log Please fix your package so that it compiles with -safe-string. This is possible with the version of OCaml currently in unstable (4.05.0). You can also check that your package builds fine with the repository available at: https://ocaml.debian.net/transitions/ocaml-4.08.0/ Cheers, -- Stéphane -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: haxe Source-Version: 1:4.0.1-1 We believe that the bug you reported is fixed in the latest version of haxe, 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 939...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andy Li (supplier of updated haxe 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, 10 Nov 2019 21:25:41 +0800 Source: haxe Architecture: source Version: 1:4.0.1-1 Distribution: unstable Urgency: medium Maintainer: Andy Li Changed-By: Andy Li Closes: 939961 Changes: haxe (1:4.0.1-1) unstable; urgency=medium . * New upstream version. + Safe-strings compatible (Closes: #939961). * Remove camlp5.diff, which is no longer needed. * Bump Standards-Version to 4.4.1 (no changes). Checksums-Sha1: e8e7b5292357f15022f493e99dfa9f71ada4e262 2015 haxe_4.0.1-1.dsc 454f7e57f144e4e0f3e842048ca8c4fa8dd60711 8749076 haxe_4.0.1.orig.tar.gz d668d217027d93db717f88aaf549147537e6d8fd 14356 haxe_4.0.1-1.debian.tar.xz 4aaf2195c79abe6cceb8e7b328b3c0183ab4e06a 8663 haxe_4.0.1-1_source.buildinfo Checksums-Sha256: 9ac367c943c9a8ba1fcfb107af2796dbf05deccb6bc53d7b303426ab45ebdccb 2015 haxe_4.0.1-1.dsc 9a1281cfbad0f5f1ce56068569415c3cd3d6ed14f011fcd2508257c00981aca5 8749076 haxe_4.0.1.orig.tar.gz 9c1f62208665542c2369c350ab0167c00f779769f77c77f948e9ce5b055d7c05 14356 haxe_4.0.1-1.debian.tar.xz 4b551430cbd8dc212033a5d84b18fc8c235d672befa7216dd077e1347fbe621a 8663 haxe_4.0.1-1_source.buildinfo Files: 9b1966b9eb2d8a55a77a98d2ba0c5b09 2015 devel optional haxe_4.0.1-1.dsc 01c20faa46e16b4147eafefcd662e015 8749076 devel optional haxe_4.0.1.orig.tar.gz c18e1687c3c8a5211858a86039687734 14356 devel optional haxe_4.0.1-1.debian.tar.xz 7949920d448d3b8a59fdc40c8e41cf9c 8663 devel optional haxe_4.0.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE3wGpIpcm0PpC91cGbaw8RIdzOBoFAl3IFvQACgkQbaw8RIdz OBq6nA//Wck2aGKI6YPOlSfsT73XNanKC3Nq2s9xWGSFROKQxSQvsK389xVZqHDW dpNAwqPjVYP+6SIkd5YnpStVEA2xbKTPBeLvCg+4P02T/W2sIrHfAn4HVu5gHeRE mgen2wkHSUd5dxcab79CN2KDwktNtHI5BSZOFEg2P9quSRJ0QZxQf4M1/HV2AnkT VoEgU1P+uxyCxWbVbjC0E+GRQWDKJaxs+GlOQbQSIdK57MQg4NtMLavhcpiJr8wg F4l9fwyL8yMi6DJCMTgfjp/6NCn+/bf298CNJpV4WfOsvHSHGWxEXHM/8Pak0pNn weMtzE+yYZ7YeGhUzLfVt3ODdGY1fZByY2KmM9YBYeoY4AfHQYR4JKDZrmCEulUO vqfOj7Tnx2T7gKtNkiR21BkB9KTbSPCJQdbV44xIYAGmEYeauCsDxFak15rZiMcP 40JJWJy1XP5wI2YN23di0RQNIVp7jxG6awkAhxwNR7CufWKxdeSZWfBy5BW3SuMj VO4rZ3zIfPt0AbHiRkkq71QeJdODMaW2E0vH15UaJlQbhEoP3w4Bo3JqC3STcijA M3zA/o3f+3Uy8V+cRI7PdfGaF7KjTAHtqB99nvUilFkgjwtkebejwfIJ0YMR42ZA 8k5mODhDdhO1656pN5N5a2oowuIivsdh7XxQsUHEOALgY1YoPME= =d2mj -END PGP SIGNATURE End Message ---
Bug#944468: autopkg tests fail on 32bit architectures
Package: src:lapack Version: 3.8.0-8 Severity: serious Tags: sid bullseye patch The autopkg tests fail on 32bit architectures, because the 64bit packages are not available. Feel free to extend the list of 32bit archs to other architectures. http://launchpadlibrarian.net/450724497/lapack_3.8.0-8_3.8.0-8ubuntu1.diff.gz
Bug#939733: lsb-release: lsb_release does not show point release on Debian 10.1
[2019-11-10 02:31] Santiago Vila
> > I am losing context. We have at least following three files (oh, why all
> > this madness?):
> >
> > * /usr/lib/os-release
> > * /etc/os-release
> > * /etc/debian_version
> >
> > So, in case of conflicts, what should override what?
>
> Please note that /usr/lib/os-release and /etc/os-release are the same file.
Thank you for your patience.
> AFAIK, lsb-release is already ignoring /etc/debian_version in buster,
> which is the reason we have this problem.
Not exactly. We have following code, where get_os_release() reads
"/usr/lib/os-release", and guess_debian_release() uses several other
files, including "/etc/debian_version".
lsbinfo = get_os_release()
# OS is only used inside guess_debian_release anyway
for key in ('ID', 'RELEASE', 'CODENAME', 'DESCRIPTION',):
if key not in lsbinfo:
distinfo = guess_debian_release()
distinfo.update(lsbinfo)
return distinfo
else:
return lsbinfo
So /etc/os-release overrides /etc/debian_version. Probably, we could
drop guess_debian_release() code though, since base-files are essential.
> b) As it has been suggested by you, fixing the problem in base-files
> by including the minor version in /etc/os-release "somewhere".
>
> I am ok with doing the change in base-files, because I believe it's
> the best option in the long term.
>
> I also believe that it would suffice to change VERSION_ID, but I need
> confirmation for that.
> [..]
>
> So: Is this ok for you?
Yes, that is fine. As I just checked, `lsb_release -d` (as is in
Archives) will happily output anything I put into VERSION_ID variable of
/etc/os_release.
--
Note, that I send and fetch email in batch, once in a few days.
Please, mention in body of your reply when you add or remove recepients.
Processed: Re: tnseq-transit: Python2 removal in sid/bullseye
Processing control commands: > severity -1 serious Bug #938674 [src:tnseq-transit] tnseq-transit: Python2 removal in sid/bullseye Severity set to 'serious' from 'important' -- 938674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938674 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918973:
Looks that ftp-master accepted tpm-udev now. Can you update tpm2-tss to use it too?
Bug#938444: pymvpa2: Python2 removal in sid/bullseye
On 10/11/2019 13:45, Matthias Klose wrote: I'm preparing a NMU for scikit-learn, based on the new subminor upstream release 0.20.3 I don't know why Ubuntu has 0.20.3 and Debian only .2, but it doesn't look related to either python3.8 or py2removal: https://scikit-learn.org/0.20/whats_new.html#version-0-20-3 The Ubuntu fix I was referring to is the explicit "Drop python2 support" i.e. https://launchpadlibrarian.net/438042402/scikit-learn_0.20.3+dfsg-0ubuntu1_0.20.3+dfsg-0ubuntu2.diff.gz (Probably the python-sklearn*.install files should have been removed as well?)
Bug#943555: wireguard-dkms: Kernel modules don't build with kernel 5.3.0-1-arm64 on Raspberry Pi3
Control: tags 943555 + help moreinfo Control: severity 943555 important Control: affects 943555 + linux-headers-5.3.0-1-arm64 gcc-9 Hi Chris-- Thanks for the report! On Sat 2019-10-26 12:51:47 +, Chris. wrote: > on Raspberry Pi3 kernel module stops building since updating to kernel > 5.3.0.1. > > Output of /var/lib/dkms/wireguard/0.0.20191012/build/make.log > DKMS make.log for wireguard-0.0.20191012 for kernel 5.3.0-1-arm64 (aarch64) > Sat Oct 26 12:37:31 UTC 2019 > make: Entering directory '/usr/src/linux-headers-5.3.0-1-arm64' > arch/arm64/Makefile:58: *** arm-linux-gnueabihf-gcc not found, check > CROSS_COMPILE_COMPAT. Stop. > make: *** [/usr/src/linux-headers-5.3.0-1-common/Makefile:179: sub-make] > Error 2 > make: Leaving directory '/usr/src/linux-headers-5.3.0-1-arm64' I'm not sure this is a wireguard-specific issue... This looks to me like you don't have the arm64-specific compiler installed, which ought to have been installed correctly by linux-headers-5.3.0-1-arm64. I note that the arm64 flavor of the linux-headers-* packages just depends directly on gcc-9, and not on any specific variant of it. compare with the x86_64 variant or the armmp variant, which explicitly point toward an arch-specific metapackages for gcc: https://packages.debian.org/sid/linux-headers-5.3.0-1-arm64 vs: https://packages.debian.org/sid/linux-headers-5.3.0-1-amd64 https://packages.debian.org/sid/linux-headers-5.3.0-1-armmp Is it possible that you have some other architecture's gcc-9 installed, or something like that? Regards, --dkg signature.asc Description: PGP signature
Processed: Re: Bug#943555: wireguard-dkms: Kernel modules don't build with kernel 5.3.0-1-arm64 on Raspberry Pi3
Processing control commands: > tags 943555 + help moreinfo Bug #943555 [wireguard-dkms] wireguard-dkms: Kernel modules don't build with kernel 5.3.0-1-arm64 on Raspberry Pi3 Added tag(s) help and moreinfo. > severity 943555 important Bug #943555 [wireguard-dkms] wireguard-dkms: Kernel modules don't build with kernel 5.3.0-1-arm64 on Raspberry Pi3 Severity set to 'important' from 'grave' > affects 943555 + linux-headers-5.3.0-1-arm64 gcc-9 Bug #943555 [wireguard-dkms] wireguard-dkms: Kernel modules don't build with kernel 5.3.0-1-arm64 on Raspberry Pi3 Added indication that 943555 affects linux-headers-5.3.0-1-arm64 and gcc-9 -- 943555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943555 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: pymvpa2: Python2 removal in sid/bullseye
Processing control commands: > severity -1 serious Bug #937485 [src:pymvpa2] pymvpa2: Python2 removal in sid/bullseye Severity set to 'serious' from 'important' -- 937485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937485 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: pymvpa2: Python2 removal in sid/bullseye
Processing control commands: > severity -1 serious Bug #936999 [src:mdp] mdp: Python2 removal in sid/bullseye Severity set to 'serious' from 'important' -- 936999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936999 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: pymvpa2: Python2 removal in sid/bullseye
Processing control commands: > severity -1 serious Bug #938444 [src:scikit-learn] scikit-learn: Python2 removal in sid/bullseye Severity set to 'serious' from 'important' -- 938444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938444 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#942896: marked as done (tellico test rely on the network)
Your message dated Sun, 10 Nov 2019 11:19:58 + with message-id and subject line Bug#942896: fixed in tellico 3.2.2-1 has caused the Debian Bug report #942896, regarding tellico test rely on the network 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.) -- 942896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942896 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:tellico Version: 3.2.1-2 Severity: serious Tags: sid bullseye patch tellico access the network during the build. please don't do this. http://launchpadlibrarian.net/374519251/tellico_3.1.2-2ubuntu4_3.1.2-2ubuntu5.diff.gz --- End Message --- --- Begin Message --- Source: tellico Source-Version: 3.2.2-1 We believe that the bug you reported is fixed in the latest version of tellico, 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 942...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pino Toscano (supplier of updated tellico 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, 10 Nov 2019 11:54:15 +0100 Source: tellico Architecture: source Version: 3.2.2-1 Distribution: unstable Urgency: medium Maintainer: Debian KDE Extras Team Changed-By: Pino Toscano Closes: 901527 942896 Changes: tellico (3.2.2-1) unstable; urgency=medium . * New upstream release. * Update the patches: - upstream_Fix-build-with-Qt-5.13.patch: drop, backported from upstream - upstream_Fix-apparent-build-problem-on-Jenkins.patch: drop, backported from upstream - fix-version.diff: drop, no more needed (the version string is correct) * Bump Standards-Version to 4.4.1, no changes required. * Add the configuration for the CI on salsa. * tellico-project.org supports https now, so use it for Homepage, and in the watch file. * Remove the extra copyright notices files, i.e. /usr/share/tellico/pics/README.*. * Bump the debhelper compatibility to 12: - switch the debhelper build dependency to debhelper-compat 12 - remove debian/compat * Extend tests-no-network.diff to always consider the network unavailable in imagejobtest. (Closes: #901527, #942896) * Use a temporary directory in $TMPDIR (or /tmp) for the home directory when running the tests: using a subdirectory of the source directory may be a too long path for local unix sockets. Checksums-Sha1: 072f64fcbca292c6fe88d9bb43dde59a6e227bdf 2760 tellico_3.2.2-1.dsc dd297d1bd16e4a720bbe74104d1ab7d5d193b9d0 5589296 tellico_3.2.2.orig.tar.xz e266565a079bda877093ec873c8dc5e9bd10a9dc 13444 tellico_3.2.2-1.debian.tar.xz ec986ed1c9aec0c15939b51666100b341ea8881d 21843 tellico_3.2.2-1_source.buildinfo Checksums-Sha256: 9b1216cdf8b0f2ec4cc364ac469b2b830b23681a8e8d6c1c461cdcd2c7f56b87 2760 tellico_3.2.2-1.dsc ec0595a421011596b39b51e0e88558da2716073f066862e9707571be9de77a9a 5589296 tellico_3.2.2.orig.tar.xz 20e0ab411e944d4fec51c241dda40761842fcbe1e2394430f0ed39c7d56ceb08 13444 tellico_3.2.2-1.debian.tar.xz 28e936c42e2e9a8333e652ac8b06e47bcbe906156d76fbccbd038e761bc22f82 21843 tellico_3.2.2-1_source.buildinfo Files: f4932e6f175668f7e458183f687e30f4 2760 kde optional tellico_3.2.2-1.dsc e57a3c93d7d5e2edc3834bcffe910df7 5589296 kde optional tellico_3.2.2.orig.tar.xz 90e6c0a0472dd6ed0349457cbaa6e412 13444 kde optional tellico_3.2.2-1.debian.tar.xz e52baf711bfbd0be5fc5f86fa45d0aff 21843 kde optional tellico_3.2.2-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAl3H7JcACgkQLRkciEOx P03CcxAAqowGW0Cdy0Crm0k0PBOoNVrP/+SAFeqL0Ctaz7m/8W6n+YcZ4j0sFcho 46rvoVzPXQTOQnmP38locJUSQmge3xG9ZwoqJKo7dm2ecOKyPfV+FXyC3czGn+o1 du84kwKAo88gmHJdPva7mjKCbrtgfXH1Zvk5cmAnABFO4NHQRuFzXHwirafnlzyN Re+rc/wHalIzEzLCInES71J/40runs5qY2I17dlANG/hj7N/sL7MZkejXlmrf9/U ReQ2YYyI90/zVNKFPJaJCwjhnDsNL9zbfrnLJ2nIyURAHHsEvbC0kuJLqf/VBzd9 xnAWAHq/xr869md/u/5fXc3nFPnuvmbF3hO4kHeVq4tdzdvRevdhgFy3DrXf7LOL lk832M+ANvFEIkZl1Rj08z/xbZStYe/0Si8CeppvonjidLiU9pwUvnOb8OwxJEVI 9wmpFCpieAA4JUNZVT71Rp3rknVRYEhbXUv7nmeV73sUZnaW7/ZEdjIaSUaXrmsl WOxLdsGGoTCIl/u6pEMORsKLxdBSXnkOR1DUMU/mASkcNnXOQMnK3qC7ZkauIGRR
Bug#944455: pgcli: missing dependency on python3-pkg-resources
Package: pgcli Version: 1.9.1-3 Severity: serious pgcli does not run out-of-the-box after installing it in a minimal sid (or buster) chroot: # pgcli Traceback (most recent call last): File "/usr/bin/pgcli", line 6, in from pkg_resources import load_entry_point ModuleNotFoundError: No module named 'pkg_resources' Andreas
Processed: tagging 944425, tagging 944397, tagging 944401
Processing commands for cont...@bugs.debian.org:
> tags 944425 + sid bullseye
Bug #944425 [sat-xmpp-primitivus] sat-xmpp-primitivus depends on
python-urwid-satext which has been dropped
Added tag(s) bullseye and sid.
> tags 944397 + sid bullseye
Bug #944397 {Done: Hilko Bengen } [src:libldm] libldm FTBFS:
error: G_ADD_PRIVATE [-Werror]
Added tag(s) bullseye and sid.
> tags 944401 + sid bullseye
Bug #944401 [pgcli] pgcli: does not start due to unmet psycopg2 requirement
Added tag(s) bullseye and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
944397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944397
944401: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944401
944425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944425
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 901527, tagging 942896
Processing commands for cont...@bugs.debian.org: > tags 901527 + pending Bug #901527 [src:tellico] disable more network related tests Added tag(s) pending. > tags 942896 + pending Bug #942896 [src:tellico] tellico test rely on the network Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 901527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901527 942896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942896 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#944327: marked as done (fribidi: CVE-2019-18397)
Your message dated Sun, 10 Nov 2019 09:15:46 + with message-id and subject line Bug#944327: fixed in fribidi 1.0.7-1.1 has caused the Debian Bug report #944327, regarding fribidi: CVE-2019-18397 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.) -- 944327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944327 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fribidi Version: 1.0.7-1 Severity: grave Tags: security upstream Justification: user security hole Control: found -1 1.0.5-3.1 Control: fixed -1 1.0.5-3.1+deb10u1 Hi, The following vulnerability was published for fribidi. CVE-2019-18397[0]: | stack buffer overflow in the fribidi_get_par_embedding_levels_ex() | function in lib/fribidi-bidi.c The update for buster is already pending for release. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-18397 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-18397 [1] https://github.com/fribidi/fribidi/commit/034c6e9a1d296286305f4cfd1e0072b879f52568 Regards, Salvatore --- End Message --- --- Begin Message --- Source: fribidi Source-Version: 1.0.7-1.1 We believe that the bug you reported is fixed in the latest version of fribidi, 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 944...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated fribidi 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: Fri, 08 Nov 2019 13:36:50 +0100 Source: fribidi Architecture: source Version: 1.0.7-1.1 Distribution: unstable Urgency: high Maintainer: Debian Hebrew Packaging Team Changed-By: Salvatore Bonaccorso Closes: 944327 Changes: fribidi (1.0.7-1.1) unstable; urgency=high . * Non-maintainer upload. * Truncate isolate_level to FRIBIDI_BIDI_MAX_EXPLICIT_LEVEL (CVE-2019-18397) (Closes: #944327) Checksums-Sha1: f1600a09a120794ed6c0cc9aea073d725779512d 2444 fribidi_1.0.7-1.1.dsc 0b1483fcd3036f619c0edd464dc3ff0aa0897f52 8908 fribidi_1.0.7-1.1.debian.tar.xz Checksums-Sha256: 716cfa7b98103104c2dec36d90427d91185a7dfb96cf7ae0854713a830e5da87 2444 fribidi_1.0.7-1.1.dsc bef9430be691d1790754431c7fe2f0b33235e406fce3956c9a67e1c1268390ef 8908 fribidi_1.0.7-1.1.debian.tar.xz Files: a40ac0861d62522dd496be7c25f73fda 2444 libs optional fribidi_1.0.7-1.1.dsc 9aea7c2a9fec1074daf9e51d7a99a28d 8908 libs optional fribidi_1.0.7-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAl3FYqhfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EQiMP/ioiD0NHor/4qOMcd3OV115dN2MaJhCu drBgpHZ5nY60cZOVonS9G2Jlm4dxCabYcFiNH4w1UmrqqCUDUuAy1VNDK7yJyGDq yPMz3j+jAs1F4zY1JK2amG9fCgFNjQUKh/DFfObvxHEWB5408yxCTLv99a9KEQmZ BaYtRtYEZpgG0em0sCPtkzoaP7BKsATad5a50PWMUiTQIBJ4TFmpOuPbxQry56Ae 75MgKb11l6hZBeOs8470ddO8YEtAJXogG0/XeB2XX46lJf7tghWVwyL1flYLwkHB QNNQjO8WbnkMYspmTLdy+awsBQwZ6Mhq5jK/MW7ZS86F6F7M4PDgvtYJ+XYs1qWd Ht4h+p7XBgeSbuD3mTxwifeHlUyZLneXu8IcAtc8oukZeRqyRfzoXzJhv1P3ua4/ AKHIBfJEf/sFUsVOlhZRgV4wAsogrClLvC85m1TrJume/1oBqbbtubaxcTPX5nzL 4X6NVHxbHggtYuiQfCX958HH8B5VMzhfeUSHPsW3F1QJKYSaUosUUK2TpM9rFmBO /fYb5vuZed4LWS9c7MO4a30pbROUkhlYhN+ObOMcPnaq0uWUsogQpqJYllztjijJ lrq9Ilz2/AhxSQ3Wy1yxCxpKK/qq2gflQWD8YFzY3cqQEq5lxvRs7RXamPmZs8f4 x2++ZYOOORsj =pydT -END PGP SIGNATURE End Message ---
Bug#897756: Testing migration blocked
Theses bugs (#897756, #897775, #906230) are preventing testing migration of insighttoolkit4 (4.13.2-dfsg1-1) because the fixed version is not included in its changelog history. If these bugs are also fixed in 4.13.2-dfsg1-1 the BTS fixed versions need to be updated to reflect that. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#944327: fribidi: diff for NMU version 1.0.7-1.1
Hi! On Sun, Nov 10, 2019 at 08:32:22AM +0200, Lior Kaplan wrote: > Hi Salvatore, > > As you already prepared a package, you can just upload it with no delay. > > Thanks for the patch & help. > > If you prefer we'd do the upload -let me know. Thanks for feedback, I rescheduled it from the delayed/5 now so it can enter the archive earlier. Regards, Salvatore
