Bug#891618: DistributionNotFound: The 'pyqt5' distribution was not found
Package: spyder3
Version: 3.2.6+dfsg1-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
The latest update of src:spyder now explicitly requires pyqt5. Despite
being pulled transitively by python{,3}-qtpy, detection by pkg_resources
is failing. Launching spyder3 yields a DistributionNotFound error with
the following traceback:
Traceback (most recent call last):
File "/usr/bin/spyder3", line 6, in
from pkg_resources import load_entry_point
File
"/home/ghislain/.local/lib/python3.6/site-packages/pkg_resources/__init__.py",
line 3147, in
@_call_aside
File
"/home/ghislain/.local/lib/python3.6/site-packages/pkg_resources/__init__.py",
line 3131, in _call_aside
f(*args, **kwargs)
File
"/home/ghislain/.local/lib/python3.6/site-packages/pkg_resources/__init__.py",
line 3160, in _initialize_master_working_set
working_set = WorkingSet._build_master()
File
"/home/ghislain/.local/lib/python3.6/site-packages/pkg_resources/__init__.py",
line 666, in _build_master
ws.require(__requires__)
File
"/home/ghislain/.local/lib/python3.6/site-packages/pkg_resources/__init__.py",
line 984, in require
needed = self.resolve(parse_requirements(requirements))
File
"/home/ghislain/.local/lib/python3.6/site-packages/pkg_resources/__init__.py",
line 870, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'pyqt5' distribution was not found and
is required by spyder
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (900, 'testing'), (90, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.14.0-3-amd64 (SMP w/8 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 /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages spyder3 depends on:
ii python3 3.6.4-1
ii python3-spyder 3.2.6+dfsg1-1
ii python3.6 3.6.4-4
spyder3 recommends no packages.
spyder3 suggests no packages.
Versions of packages python3-spyder depends on:
ii libjs-jquery 3.2.1-1
ii libjs-mathjax2.7.2+dfsg-1
ii pylint3 1.8.1-1
ii python3 3.6.4-1
ii python3-chardet 3.0.4-1
ii python3-cloudpickle 0.5.2-2
ii python3-jedi 0.11.1-1
ii python3-nbconvert5.3.1-1
ii python3-numpydoc 0.7.0-1
ii python3-pickleshare 0.7.4-2
ii python3-psutil 5.4.2-1
ii python3-pycodestyle 2.3.1-2
ii python3-pyflakes 1.6.0-1
ii python3-pygments 2.2.0+dfsg-1
ii python3-qtawesome0.4.4+ds1-1
ii python3-qtconsole4.3.1-1
ii python3-qtpy 1.3.1-1
ii python3-rope 0.10.5-2
ii python3-sphinx 1.6.7-1
ii python3-zmq 16.0.2-2+b1
ii spyder-common3.2.6+dfsg1-1
Versions of packages python3-spyder suggests:
ii cython3 0.26.1-0.4
pn python3-matplotlib
pn python3-numpy
pn python3-pandas
ii python3-pil 4.3.0-2
pn python3-scipy
pn python3-sympy
pn spyder-doc
Versions of packages python3-pyqt5 depends on:
ii libc62.26-6
ii libgcc1 1:8-20180218-1
ii libpython3.6 3.6.4-4
ii libqt5core5a [qtbase-abi-5-9-2] 5.9.2+dfsg-12
ii libqt5dbus5 5.9.2+dfsg-12
ii libqt5designer5 5.9.2-6
ii libqt5gui5 5.9.2+dfsg-12
ii libqt5help5 5.9.2-6
ii libqt5network5 5.9.2+dfsg-12
ii libqt5printsupport5 5.9.2+dfsg-12
ii libqt5test5 5.9.2+dfsg-12
ii libqt5widgets5 5.9.2+dfsg-12
ii libqt5xml5 5.9.2+dfsg-12
ii libstdc++6 8-20180218-1
ii python3 3.6.4-1
ii python3-sip [sip-py3api-12.3]4.19.7+dfsg-1
Versions of packages python3-pyqt5 suggests:
pn python3-pyqt5-dbg
-- no debconf information
Bug#891617: DistributionNotFound: The 'pyopengl' distribution was not found
Package: spyder Version: 3.2.6+dfsg1-1 Severity: grave Justification: renders package unusable The latest update of src:spyder now requires pyopengl, which is currently missing from Depends. Launching spyder yields a DistributionNotFound error with the following traceback: Traceback (most recent call last): File "/usr/bin/spyder", line 6, in from pkg_resources import load_entry_point File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3147, in @_call_aside File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3131, in _call_aside f(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3160, in _initialize_master_working_set working_set = WorkingSet._build_master() File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 666, in _build_master ws.require(__requires__) File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 984, in require needed = self.resolve(parse_requirements(requirements)) File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 870, in resolve raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'pyopengl' distribution was not found and is required by spyder -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (900, 'testing'), (90, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/8 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 /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages spyder depends on: ii python 2.7.14-4 ii python-spyder 3.2.6+dfsg1-1 ii python2.7 2.7.14-6 spyder recommends no packages. spyder suggests no packages. Versions of packages python-spyder depends on: ii libjs-jquery3.2.1-1 ii libjs-mathjax 2.7.2+dfsg-1 ii pylint 1.8.1-1 ii python 2.7.14-4 ii python-chardet 3.0.4-1 ii python-cloudpickle 0.5.2-2 ii python-jedi 0.11.1-1 ii python-nbconvert5.3.1-1 ii python-numpydoc 0.7.0-1 ii python-pickleshare 0.7.4-2 ii python-psutil 5.4.2-1 ii python-pycodestyle 2.3.1-2 ii python-pyflakes 1.6.0-1 ii python-pygments 2.2.0+dfsg-1 ii python-qtawesome0.4.4+ds1-1 ii python-qtconsole4.3.1-1 ii python-qtpy 1.3.1-1 ii python-rope 0.10.5-2 ii python-sphinx 1.6.7-1 ii python-zmq 16.0.2-2+b1 ii spyder-common 3.2.6+dfsg1-1 Versions of packages python-spyder suggests: pn cython pn python-matplotlib ii python-numpy 1:1.13.3-2 pn python-pandas ii python-pil 4.3.0-2 pn python-scipy pn python-sympy pn spyder-doc Versions of packages python-pyqt5 depends on: ii libc62.26-6 ii libqt5core5a [qtbase-abi-5-9-2] 5.9.2+dfsg-12 ii libqt5dbus5 5.9.2+dfsg-12 ii libqt5designer5 5.9.2-6 ii libqt5gui5 5.9.2+dfsg-12 ii libqt5help5 5.9.2-6 ii libqt5network5 5.9.2+dfsg-12 ii libqt5printsupport5 5.9.2+dfsg-12 ii libqt5test5 5.9.2+dfsg-12 ii libqt5widgets5 5.9.2+dfsg-12 ii libqt5xml5 5.9.2+dfsg-12 ii libstdc++6 8-20180218-1 ii python 2.7.14-4 ii python-sip [sip-api-12.3]4.19.7+dfsg-1 Versions of packages python-pyqt5 suggests: pn python-pyqt5-dbg -- no debconf information
Bug#875637: stretch update for iipimage-server
On Mon, Feb 26, 2018 at 9:02 PM, Adrian Bunk wrote: > On Wed, Nov 22, 2017 at 09:21:10PM +, Debian Bug Tracking System wrote: >>... >> iipimage (1.0-3) unstable; urgency=medium >> . >>* Really fix apache configuration. Closes: #875637 >>... > > Thanks a lot for fixing this bug for unstable. > > It is still present in stretch, could you also fix it there? > Alternatively, I can fix it for stretch if you don't object. Please do :) Thanks for your help!
Processed: Marking the bugs as fixed upstream and pending a release
Processing commands for cont...@bugs.debian.org: > # The dependency on libgnome2 has been removed > tags 890465 + pending Bug #890465 [pioneers] pioneers: Depends on libgnome Added tag(s) pending. > # The dependency on scrollkeeper has been removed > tags 885613 + pending Bug #885613 [src:pioneers] pioneers: Please drop Build-Depends on scrollkeeper Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 885613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885613 890465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890465 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#891460: marked as done (ring: Should depend on libqt5sql5-sqlite)
Your message dated Tue, 27 Feb 2018 07:06:41 +
with message-id
and subject line Bug#891460: fixed in ring 20180222.1.7bffde2~ds2-2
has caused the Debian Bug report #891460,
regarding ring: Should depend on libqt5sql5-sqlite
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.)
--
891460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891460
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ring
Version: 20180119.1.9e06f94~ds1-3
Severity: grave
Justification: renders package unusable
Dear Maintainer,
After installing ring, I was unable to start it.
Issuing gnome-ring yielded the following error:
--
$ gnome-ring
** Message: Ring GNOME client version: 1.0.0
** Message: git ref: unknown
(gnome-ring:4245): Gtk-WARNING **: Theme file for default has no name
(gnome-ring:4245): Gtk-WARNING **: Theme file for default has no directories
Updating all accounts
Loading "..."
Loading vcf from: QDir( "/home/luis.oliveira/.local/share/gnome-ring/profiles"
, nameFilters = { "*" }, QDir::SortFlags( Name | IgnoreCase ) , QDir::Filters(
Dirs|Files|Drives|AllEntries ) )
CM already has text recording ContactMethod(..., name = "...")
terminate called after throwing an instance of 'std::runtime_error'
what(): QSQLITE not supported
Aborted
--
I found out that installing the 'libqt5sql5-sqlite' package makes ring start
correctly.
Can you please include that as a dependency for this package?
Thanks and best regards,
Luís Picciochi Oliveira
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages ring depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.26.1-3
ii libappindicator3-1 0.4.92-5
ii libatk1.0-0 2.26.1-3
ii libc62.26-6
ii libcairo-gobject21.15.10-1
ii libcairo21.15.10-1
ii libcanberra-gtk3-0 0.30-6
ii libcanberra0 0.30-6
ii libclutter-1.0-0 1.26.2+dfsg-4
ii libclutter-gtk-1.0-0 1.8.4-3
ii libcogl-pango20 1.22.2-3
ii libcogl-path20 1.22.2-3
ii libcogl201.22.2-3
ii libdbusmenu-glib416.04.1+17.04.20170109.1-5
ii libdrm2 2.4.89-1
ii libebackend-1.2-10 3.26.5-1
ii libebook-1.2-19 3.26.5-1
ii libebook-contacts-1.2-2 3.26.5-1
ii libedata-book-1.2-25 3.26.5-1
ii libedataserver-1.2-223.26.5-1
ii libegl1 1.0.0-2
ii libgbm1 17.3.3-1
ii libgcc1 1:8-20180207-2
ii libgdk-pixbuf2.0-0 2.36.11-1
ii libglib2.0-0 2.54.3-2
ii libgtk-3-0 3.22.28-1
ii libjavascriptcoregtk-4.0-18 2.18.6-1
ii libjson-glib-1.0-0 1.4.2-3
ii libnm0 1.10.4-1+b1
ii libnotify4 0.7.7-3
ii libpango-1.0-0 1.40.14-1
ii libpangocairo-1.0-0 1.40.14-1
ii libqrencode3 3.4.4-1+b2
ii libqt5core5a 5.9.2+dfsg-12
ii libqt5dbus5 5.9.2+dfsg-12
ii libqt5sql5 5.9.2+dfsg-12
ii libsecret-1-00.18.5-6
ii libsoup2.4-1 2.60.3-1
ii libstdc++6 8-20180207-2
ii libwayland-client0 1.14.0-1+b1
ii libwayland-cursor0 1.14.0-1+b1
ii libwayland-egl1-mesa [libwayland-egl1] 17.3.3-1
ii libwayland-server0 1.14.0-1+b1
ii
Bug#891614: jackson-databind: CVE-2018-7489: incomplete fix for CVE-2017-7525 permits unsafe serialization via c3p0 libraries
Source: jackson-databind Version: 2.9.4-1 Severity: grave Tags: patch security upstream Justification: user security hole Forwarded: https://github.com/FasterXML/jackson-databind/issues/1931 Hi, the following vulnerability was published for jackson-databind. CVE-2018-7489[0]: | FasterXML jackson-databind before 2.8.11.1 and 2.9.x before 2.9.5 | allows unauthenticated remote code execution because of an incomplete | fix for the CVE-2017-7525 deserialization flaw. This is exploitable by | sending maliciously crafted JSON input to the readValue method of the | ObjectMapper, bypassing a blacklist that is ineffective if the c3p0 | libraries are available in the classpath. 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-2018-7489 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-7489 [1] https://github.com/FasterXML/jackson-databind/issues/1931 [2] https://github.com/FasterXML/jackson-databind/commit/6799f8f10cc78e9af6d443ed6982d00a13f2e7d2 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#884417: python-trezor v0.9.0 tagged - next steps?
> I'll try to take care of it this week. Fantastic, thanks Tristan!
Processed: user debian...@lists.debian.org, found 891454 in 2.17.2-1 ..., affects 840151, usertagging 857792 ...
Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > found 891454 2.17.2-1 Bug #891454 [apport-kde] apport-kde: unsatisfiable Depends: python-kde4 Marked as found in versions apport/2.17.2-1. > found 876608 ruby-compass-import-once/1.0.5~dfsg-5 Bug #876608 [ruby-compass] ruby-compass (build) depends on ruby-sass (< 3.5), but 3.5.1-2 is in unstable The source ruby-compass-import-once and version 1.0.5~dfsg-5 do not appear to match any binary packages Marked as found in versions ruby-compass-import-once/1.0.5~dfsg-5. > affects 840151 + libswiften3 Bug #840151 [swift-im] swift-im: FTBFS on i386: Qt wants this to be built with -fPIC Added indication that 840151 affects libswiften3 > usertags 857792 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 866471 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 866429 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 866436 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 866440 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 866443 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 866445 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 866453 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 866459 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 866470 piuparts There were no usertags set. Usertags are now: piuparts. > affects 886802 + python-uniconvertor-dbg Bug #886802 [python-uniconvertor] python-uniconvertor: cannot be installed Added indication that 886802 affects python-uniconvertor-dbg > usertags 866486 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 866497 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 866499 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 889581 piuparts There were no usertags set. Usertags are now: piuparts. > affects 889581 + syslog-ng-mod-basicfuncs-plus syslog-ng-mod-grok > syslog-ng-mod-perl syslog-ng-mod-kafka syslog-ng-mod-rss syslog-ng-mod-trigger Bug #889581 [src:syslog-ng-incubator] syslog-ng-incubator: FTBFS with syslog-ng 3.13.2 Added indication that 889581 affects syslog-ng-mod-basicfuncs-plus, syslog-ng-mod-grok, syslog-ng-mod-perl, syslog-ng-mod-kafka, syslog-ng-mod-rss, and syslog-ng-mod-trigger > thanks Stopping processing here. Please contact me if you need assistance. -- 840151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840151 876608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876608 886802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886802 889581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889581 891454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891454 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#891612: thumbor: uninstallable after python-imaging removal
Package: thumbor Version: 6.3.2-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package is no longer installable in sid: The following packages have unmet dependencies: thumbor : Depends: python-imaging but it is not installable Cheers, Andreas
Bug#891020: Bug#891413: fixed in ppp 2.4.7-2+2
Thanks, this fixed my problem as well. -Chris Dow
Bug#889719: marked as done (python-yowsup-common: Missing Breaks+Replaces on python-yowsup (<< 2.5.7-1~))
Your message dated Tue, 27 Feb 2018 02:55:56 + with message-id and subject line Bug#889719: fixed in yowsup 2.5.7-3 has caused the Debian Bug report #889719, regarding python-yowsup-common: Missing Breaks+Replaces on python-yowsup (<< 2.5.7-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.) -- 889719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889719 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-yowsup-common Version: 2.5.7-2 Severity: serious Unpacking python-yowsup-common (2.5.7-2) ... dpkg: error processing archive /tmp/apt-dpkg-install-SUZNpz/32-python-yowsup-common_2.5.7-2_all.deb (--unpack): trying to overwrite '/usr/share/yowsup/common/mime.types/mime.types', which is also in package python-yowsup 2.5.0~git20160904.d69c1ff-1 --- End Message --- --- Begin Message --- Source: yowsup Source-Version: 2.5.7-3 We believe that the bug you reported is fixed in the latest version of yowsup, 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 889...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Josue Ortega (supplier of updated yowsup 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, 26 Feb 2018 20:04:16 -0600 Source: yowsup Binary: python-yowsup python3-yowsup python-yowsup-common yowsup-cli Architecture: source all Version: 2.5.7-3 Distribution: unstable Urgency: medium Maintainer: Josue Ortega Changed-By: Josue Ortega Description: python-yowsup - library to implement a WhatsApp client python-yowsup-common - library to implement a WhatsApp client (common files) python3-yowsup - Python 3 library to implement a WhatsApp client yowsup-cli - command line tool that acts as WhatsApp client Closes: 889719 Changes: yowsup (2.5.7-3) unstable; urgency=medium . * Adds missing Breaks+Replaces package relationship with python-yowsup (<< 2.5.7-1~), (Closes: #889719). Checksums-Sha1: fbfd5375006d1be72a177fb741bdd7ff4c30feb2 2209 yowsup_2.5.7-3.dsc e20c836acca453f78c476ed9dc3555c66a4072b7 10688 yowsup_2.5.7-3.debian.tar.xz 4dcaf69622cf5060d589d8fc0baa5986e3c98b92 6156 python-yowsup-common_2.5.7-3_all.deb 95cabc6389b830778ae7349adbfede86c1dbb2a8 98744 python-yowsup_2.5.7-3_all.deb ba03699227945ccc1165180ba51e13356d0fa033 96956 python3-yowsup_2.5.7-3_all.deb be48a68253217e2c57559e0b9a9a790c660c79d5 14264 yowsup-cli_2.5.7-3_all.deb 9ef79e6851dedd851661a55ae38ac0ca0dda2ca1 7733 yowsup_2.5.7-3_amd64.buildinfo Checksums-Sha256: d96575b7be710cc291ac5d526e7c40624d9e92e639f70c2198b0ab311a1bcbf4 2209 yowsup_2.5.7-3.dsc 3dae645521df0c6ff69484287e86c74a133a7b715b7e7d17626427bea31fc87d 10688 yowsup_2.5.7-3.debian.tar.xz 96bd3f3e3c5991b83af2aa5770f9ba4b639528262a84cb613391acdc0853a12c 6156 python-yowsup-common_2.5.7-3_all.deb c1336482f6fce0696a4d8ffac146b0a9b7912b709a4934e970501e003a55d654 98744 python-yowsup_2.5.7-3_all.deb 293ea323143fc834f9cf9f46ee710c883f0ed4bedb562d02e7ea9ffb48a7a5e3 96956 python3-yowsup_2.5.7-3_all.deb 437bd6d87937e0f35511ea5913ceaa23fc2338463575fb0feae7fa31af31fdd6 14264 yowsup-cli_2.5.7-3_all.deb 0782d4714892ed9f3510c3144be41a281e229cdb8ab9d11be8c4d67e3eea0cce 7733 yowsup_2.5.7-3_amd64.buildinfo Files: 186b1228f851f354f4eda5d532ad8ce9 2209 python optional yowsup_2.5.7-3.dsc 959b38d8169fbaa36ef74c4666b51562 10688 python optional yowsup_2.5.7-3.debian.tar.xz 8089fd50fb4155016a4f5c92c2d52fcb 6156 python optional python-yowsup-common_2.5.7-3_all.deb c7677f1007ad4fcfecfba90927b3eed2 98744 python optional python-yowsup_2.5.7-3_all.deb c64eed443a3dc9274bf0db8abad1084e 96956 python optional python3-yowsup_2.5.7-3_all.deb 930730d8a42517463cea80cda662f6a5 14264 net optional yowsup-cli_2.5.7-3_all.deb d066483a8dd37c4029cd20f5a6f0c237 7733 python optional yowsup_2.5.7-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEdzOzKNJ5X1viMlrdAVCdXKtK/T8FAlqUv9ERHGpvc3VlQGRl Ymlhbi5vcmcACgkQAVCdXKtK/T9ATA//YopfOgdpECF/CEah6lJUiZFJAgzWBkk/ kI+z9JOAKjc1vNamBZAAgJNC3O2ZJsGYGLQCCOAmbJcQHpNe2tMH5OWn4WtL9xsB JWj88gut4SrM/MdQFSyDVZRLBGu2jLQRvj5vEA+3DbCherIjka1OGrXnUzpwKvoV gGK/T7PNolzqqcwtw5+wjTmz7/rBl3sTwf1GwuRuJG9gURcTqFMiAJ
Processed: tagging 891523
Processing commands for cont...@bugs.debian.org: > tags 891523 + buster sid Bug #891523 [src:tcpxtract] tcpxtract FTBFS with flex 2.6.4-6 Added tag(s) buster and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 891523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891523 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 884772
Processing commands for cont...@bugs.debian.org:
> tags 884772 + buster sid
Bug #884772 {Done: Sean Whitton } [src:projectile]
projectile: FTBFS with new version of mkdocs
Added tag(s) buster and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
884772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884772
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 885963
Processing commands for cont...@bugs.debian.org:
> tags 885963 + buster sid
Bug #885963 {Done: Adam Borowski } [src:libopenraw] FTBFS:
failed to open /etc/hosts
Added tag(s) sid and buster.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
885963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885963
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 866172
Processing commands for cont...@bugs.debian.org:
> tags 866172 + buster sid
Bug #866172 {Done: Michael Stapelberg }
[src:golang-github-minio-minio-go] golang-github-minio-minio-go FTBFS: FAIL:
TestGetEndpointURL
Added tag(s) sid and buster.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
866172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866172
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 866175
Processing commands for cont...@bugs.debian.org:
> tags 866175 + buster sid
Bug #866175 {Done: Alexandre Viau }
[src:golang-github-d4l3k-messagediff] golang-github-d4l3k-messagediff FTBFS:
FAIL: TestPrettyDiff
Added tag(s) sid and buster.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
866175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866175
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 881036
Processing commands for cont...@bugs.debian.org:
> tags 881036 + buster sid
Bug #881036 {Done: Jonas Smedegaard } [src:debian-parl]
debian-parl build depends on boxer-data (< 10.6) but 10.6.0 is to be installed
Added tag(s) sid and buster.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
881036: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881036
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 881037
Processing commands for cont...@bugs.debian.org:
> tags 881037 + buster sid
Bug #881037 {Done: Jonas Smedegaard } [src:debian-design]
debian-design build depends on boxer-data (< 10.6) but 10.6.0 is to be installed
Added tag(s) buster and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
881037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881037
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 888818
Processing commands for cont...@bugs.debian.org:
> tags 18 + buster sid
Bug #18 {Done: Sergei Golovan } [tk8.6-blt2.5] [blt]
Binary (probably) incompatible with new Tcl/Tk versions (8.6)
Added tag(s) buster and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
18: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=18
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#891570: SSL connect attempt failed error:141A90B5:SSL routines:ssl_cipher_list_to_bytes:no ciphers available
WWW::Mechanize: 500 Can't connect to mbasic.facebook.com:443...
Processed: tagging 865704
Processing commands for cont...@bugs.debian.org:
> tags 865704 + buster sid
Bug #865704 {Done: Manolo Díaz } [quiterss] quiterss:
Segfault at start
Added tag(s) sid and buster.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
865704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865704
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#880554: [Pkg-xen-devel] Bug#880554: xen domu freezes with kernel linux-image-4.9.0-4-amd64
On 02/26/2018 07:35 PM, Hans van Kranenburg wrote:
> On 02/26/2018 03:52 PM, Ian Jackson wrote:
>> Christian Schwamborn writes ("Re: Bug#880554: xen domu freezes with
kernel linux-image-4.9.0-4-amd64"):
>>> I can try, but the only system I can really test this is a productive
>>> system, as this 'reliable' shows this issue (and I don't want to crash
>>> it on purpose on a regular basis). Since I set gnttab_max_frame to a
>>> higher value it runs smooth. If you're confident this will work I can
>>> try this in the eventing, when all users logged off.
>>
>> Thanks. I understand your reluctance. I don't want to mislead you.
>> I think the odds of it working are probably ~75%.
>>
>> Unless you want to tolerate that risk, it might be better for us to
>> try to come up with a better way to test it.
>
> I can try this.
>
> I can run a dom0 with Xen 4.8 and 4.9 domU, I already have the xen-diag
> for it (so confirmed the patch in this bug report builds ok, we should
> include it for stretch, it's really useful).
>
> I think it's mainly trying to get a domU running with various
> combinations of domU kernel, number of disks and vcpus, and then look at
> the output of xen-diag.
Ok, I spent some time trying things.
Xen: 4.8.3+comet2+shim4.10.0+comet3-1+deb9u4.1
dom0 kernel 4.9.65-3+deb9u2
domU (PV) kernel 4.9.82-1+deb9u2
Observation so far: nr_frames increases as soon as a combination of
disk+vcpu has actually been doing disk activity, and then never decreases.
I ended up with a 64-vcpu domU with additional 10 1GiB disks (xvdc,
xvdd, etc).
I created ext4 fs on the disks and mounted them.
I used fio to throw some IO at the disk, trying to hit as many
combinations of vcpu and disk.
[things]
rw=randwrite
rwmixread=75
size=8M
directory=/mnt/xvdBLAH
ioengine=libaio
direct=1
iodepth=16
numjobs=64
with BLAH replaced by c, d, e, f etc...
-# rm */things*; for i in c d e f g h i j k l; do fio fio-xvd$i; done
-# while true; do /usr/lib/xen-4.8/bin/xen-diag gnttab_query_size 2;
sleep 10; done
domid=2: nr_frames=6, max_nr_frames=128
domid=2: nr_frames=7, max_nr_frames=128
domid=2: nr_frames=7, max_nr_frames=128
domid=2: nr_frames=10, max_nr_frames=128
domid=2: nr_frames=10, max_nr_frames=128
domid=2: nr_frames=11, max_nr_frames=128
domid=2: nr_frames=13, max_nr_frames=128
domid=2: nr_frames=14, max_nr_frames=128
domid=2: nr_frames=15, max_nr_frames=128
domid=2: nr_frames=16, max_nr_frames=128
domid=2: nr_frames=18, max_nr_frames=128
domid=2: nr_frames=18, max_nr_frames=128
domid=2: nr_frames=19, max_nr_frames=128
domid=2: nr_frames=21, max_nr_frames=128
domid=2: nr_frames=21, max_nr_frames=128
domid=2: nr_frames=23, max_nr_frames=128
domid=2: nr_frames=24, max_nr_frames=128
domid=2: nr_frames=24, max_nr_frames=128
domid=2: nr_frames=24, max_nr_frames=128
domid=2: nr_frames=24, max_nr_frames=128
So I can push it up to about 24 when doing this.
-# grep . /sys/module/xen_blkback/parameters/*
/sys/module/xen_blkback/parameters/log_stats:0
/sys/module/xen_blkback/parameters/max_buffer_pages:1024
/sys/module/xen_blkback/parameters/max_persistent_grants:1056
/sys/module/xen_blkback/parameters/max_queues:4
/sys/module/xen_blkback/parameters/max_ring_page_order:4
Now, I rebooted my test domo and put the modprobe file in place.
(Note: the filename has to end in .conf)!!
-# grep . /sys/module/xen_blkback/parameters/*
/sys/module/xen_blkback/parameters/log_stats:0
/sys/module/xen_blkback/parameters/max_buffer_pages:1024
/sys/module/xen_blkback/parameters/max_persistent_grants:1056
/sys/module/xen_blkback/parameters/max_queues:1
/sys/module/xen_blkback/parameters/max_ring_page_order:0
After doing the same tests, the result ends up being exactly 24 again.
So, the modprobe settings don't seem to do anything.
-# tree /sys/block/xvda/mq
/sys/block/xvda/mq
└── 0
├── active
├── cpu0
│ ├── completed
│ ├── dispatched
│ ├── merged
│ └── rq_list
├── cpu1
│ ├── completed
│ ├── dispatched
│ ├── merged
│ └── rq_list
[...]
├── cpu63
│ ├── completed
│ ├── dispatched
│ ├── merged
│ └── rq_list
[...]
├── cpu_list
├── dispatched
├── io_poll
├── pending
├── queued
├── run
└── tags
65 directories, 264 files
Mwooop mwooop mwoop mwo (failure trombone).
It obviously didn't involve network traffic yet. And, all is stretch
kernels etc, which are reported to already be problematic.
But, the main thing I wanted to test is if the change would result in a
much lower total amount of grants, which is not the case.
So, anyone a better idea, or should we just add some clear documentation
for the max frames setting in the grub config example?
Hans
Processed: tagging 888893
Processing commands for cont...@bugs.debian.org:
> tags 93 + buster sid
Bug #93 {Done: alexandre.j.raym...@gmail.com (Alexandre J. Raymond)}
[password-gorilla] password-gorilla: After upgrade, password-gorilla refuses to
start with "Couldn't find the package Itcl" message
Added tag(s) sid and buster.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
93: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=93
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#891006: marked as done (libeiskaltdcpp2.4: fails to upgrade from 'sid' - trying to overwrite /usr/share/locale/be/LC_MESSAGES/libeiskaltdcpp.mo)
Your message dated Mon, 26 Feb 2018 22:49:36 + with message-id and subject line Bug#891006: fixed in eiskaltdcpp 2.2.10+186+g1c0173ec-2 has caused the Debian Bug report #891006, regarding libeiskaltdcpp2.4: fails to upgrade from 'sid' - trying to overwrite /usr/share/locale/be/LC_MESSAGES/libeiskaltdcpp.mo 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.) -- 891006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891006 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libeiskaltdcpp2.4 Version: 2.2.10+186+g1c0173ec-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' 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/#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package libeiskaltdcpp2.4. Preparing to unpack .../libeiskaltdcpp2.4_2.2.10+186+g1c0173ec-1_amd64.deb ... Unpacking libeiskaltdcpp2.4 (2.2.10+186+g1c0173ec-1) ... dpkg: error processing archive /var/cache/apt/archives/libeiskaltdcpp2.4_2.2.10+186+g1c0173ec-1_amd64.deb (--unpack): trying to overwrite '/usr/share/locale/be/LC_MESSAGES/libeiskaltdcpp.mo', which is also in package libeiskaltdcpp2.2 2.2.9-7 Errors were encountered while processing: /var/cache/apt/archives/libeiskaltdcpp2.4_2.2.10+186+g1c0173ec-1_amd64.deb cheers, Andreas libeiskaltdcpp2.2=2.2.9-7_libeiskaltdcpp2.4=2.2.10+186+g1c0173ec-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: eiskaltdcpp Source-Version: 2.2.10+186+g1c0173ec-2 We believe that the bug you reported is fixed in the latest version of eiskaltdcpp, 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 891...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boris Pek (supplier of updated eiskaltdcpp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 27 Feb 2018 01:34:29 +0300 Source: eiskaltdcpp Binary: eiskaltdcpp eiskaltdcpp-common eiskaltdcpp-emoticons eiskaltdcpp-scripts eiskaltdcpp-sounds libeiskaltdcpp2.4 libeiskaltdcpp-dev eiskaltdcpp-qt eiskaltdcpp-qt-data eiskaltdcpp-gtk eiskaltdcpp-gtk-data eiskaltdcpp-daemon eiskaltdcpp-cli Architecture: source Version: 2.2.10+186+g1c0173ec-2 Distribution: unstable Urgency: medium Maintainer: Boris Pek Changed-By: Boris Pek Description: eiskaltdcpp - EiskaltDC++ metapackage eiskaltdcpp-cli - EiskaltDC++ command-line interface eiskaltdcpp-common - common files for EiskaltDC++ eiskaltdcpp-daemon - EiskaltDC++ daemon eiskaltdcpp-emoticons - emoticons for EiskaltDC++ eiskaltdcpp-gtk - EiskaltDC++ GUI based on GTK+ eiskaltdcpp-gtk-data - data files for EiskaltDC++ Gtk eiskaltdcpp-qt - EiskaltDC++ GUI based on Qt eiskaltdcpp-qt-data - data files for EiskaltDC++ Qt eiskaltdcpp-scripts - scripts examples for EiskaltDC++ eiskaltdcpp-sounds - sound files for EiskaltDC++ libeiskaltdcpp-dev - DC++ kernel from EiskaltDC++ (development files) libeiskaltdcpp2.4 - DC++ kernel library from EiskaltDC++ Closes: 891006 Changes: eiskaltdcpp (2.2.10+186+g1c0173ec-2) unstable; urgency=medium . * Move to unstable: no changes required. * Package libeiskaltdcpp2.4 now Breaks and Replaces package libeiskaltdcpp2.2. (Closes: #891006) Checksums-Sha1: b032a6536087a6d183034849563f5756acca90a5 3144 eiskaltdcpp_2.2.10+186+g1c0173ec-2.dsc 2e470880be93abd7532333a8d81345d46979e368 2380356 eiskaltdcpp_2.2.10+186+g1c0173ec.orig.tar.xz d7a973dc639ca3cd86a16a2661dee3e22f98d04f 10888 eiskaltdcpp_2.2.10+186+g1c0173ec-2.debian.tar.xz Checksums-Sha256: 55781cd2a2657f0305ddd18bf7f3eb91e390a43d9fb34a69da1172cbee6fa2e9 3144 eiskaltdcpp_2.2.10+186+g1c0173ec-2.dsc 6d82ebd05fc59e6bf23bc60ff966451081945bc8cca8d58d5a862c74ca274517 2380356 eiskaltdcpp_2.2.10+186+g1c0173ec.orig.tar.xz 20d8058bb87b3198a1d6bd2364a1264486fd0a88
Bug#887530: marked as done (cen64-qt FTBFS with libquazip5-headers 0.7.3-3)
Your message dated Mon, 26 Feb 2018 22:49:28 + with message-id and subject line Bug#887530: fixed in cen64-qt 20180125-alpha-1 has caused the Debian Bug report #887530, regarding cen64-qt FTBFS with libquazip5-headers 0.7.3-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.) -- 887530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887530 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cen64-qt Version: 20160829-alpha-1 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/cen64-qt.html ... g++ -c -pipe -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -W -D_REENTRANT -fPIC -DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_XML_LIB -DQT_SQL_LIB -DQT_CORE_LIB -I. -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem /usr/include/x86_64-linux-gnu/qt5/QtSql -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -I. -isystem /usr/include/libdrm -I. -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o common.o src/common.cpp src/common.cpp:43:10: fatal error: quazip/quazip.h: No such file or directory #include ^ compilation terminated. Makefile:554: recipe for target 'common.o' failed make[1]: *** [common.o] Error 1 --- End Message --- --- Begin Message --- Source: cen64-qt Source-Version: 20180125-alpha-1 We believe that the bug you reported is fixed in the latest version of cen64-qt, 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 887...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dan Hasting (supplier of updated cen64-qt 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: Thu, 15 Feb 2018 00:05:29 -0500 Source: cen64-qt Binary: cen64-qt Architecture: source Version: 20180125-alpha-1 Distribution: sid Urgency: medium Maintainer: John Paul Adrian Glaubitz Changed-By: Dan Hasting Description: cen64-qt - Cross-platform graphical frontend for the CEN64 emulator Closes: 887530 Changes: cen64-qt (20180125-alpha-1) unstable; urgency=medium . * New upstream release. - Fix FTBFS with libquazip5-headers. (Closes: #887530) * New maintainer. - Set myself as maintainer in debian/control. * Depend on libqt5sql5-sqlite. * Add manpage for cen64-qt. * Use compat level 11. * Declare compliance with Debian Policy 4.1.3. - Use https for Vcs-Git location. * Remove comments from rules. * Override rc-version-greater-than-expected-version warning. * Update Vcs-Git location. Checksums-Sha1: bdd06285535bf20374cdb255117dbbd0ecefa805 1934 cen64-qt_20180125-alpha-1.dsc 33d57f3d168ab600d56ba8f13c7aa8a6bcadf9fb 457365 cen64-qt_20180125-alpha.orig.tar.gz 3f0d76f876a6f4ae16932a177a73fb9baceb9356 3284 cen64-qt_20180125-alpha-1.debian.tar.xz 9a7f8d6b0f9cf65c31aa0ee7b61a4c9f1183ef1c 10341 cen64-qt_20180125-alpha-1_amd64.buildinfo Checksums-Sha256: cd82cf4805f8232c90ef2dcecf514fdfa35c963153acb11dd9d1504d706fb590 1934 cen64-qt_20180125-alpha-1.dsc e8a4e3692f6590a51c2fafaa2fc1e86f8ff454900268afde4aeb248344090b4c 457365 cen64-qt_20180125-alpha.orig.tar.gz e4541cea7b1f8d6c6fc2bf5eee0b3792a83251a34e62b71860f2718da8061911 3284 cen64-qt_20180125-alpha-1.debian.tar.xz 9f919f60db5a46c8a21206782d62cf05e8915e175b6e7c84763ed838e6a28ff7 10341 cen64-qt_20180125-alpha-1_amd64.buildinfo Files: de026edcf08b1a98dad302052a286a1d 1934 otherosfs optional cen64-qt_20180125-alpha-1.dsc c6c74460b76bcf366956c0dfce598f82 457365 otherosfs optional cen64-qt_20180125-alpha.orig.tar.gz 279a79b831bb744405994423b9655ae9 3284 otherosfs optional cen64-qt_20180125-alpha-1.debian.tar.xz 2d7a2b6323051afcb5d942212b6a16c6 10341 otherosfs optional cen64-qt_20180125-alpha-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEYv+KdYTgKVaVRgAGdCY7N/W1+RMFAlqUi6kACgkQdCY7N/W1 +RNK5A/+Nu5ES10rM+lcV0Xq5ayv9XLIOuEWvss7IzMzEgPSXggMDe8aqtCXZze0 fcdzD+/Elv
Bug#891266: marked as done (libtest-postgresql-perl: Incomplete debian/copyright?)
Your message dated Mon, 26 Feb 2018 22:00:13 + with message-id and subject line Bug#891266: fixed in libtest-postgresql-perl 1.23-2 has caused the Debian Bug report #891266, regarding libtest-postgresql-perl: Incomplete debian/copyright? 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.) -- 891266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891266 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libtest-postgresql-perl Version: 1.23-1 Severity: serious Justication: Policy 12.5 X-Debbugs-CC: Don Armstrong Hi, I just ACCEPTed libtest-postgresql-perl from NEW but noticed it was missing attribution in debian/copyright for at least Junio Hamano. :) (This is not exhaustive so please check over the entire package carefully and address these on your next upload.) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- --- End Message --- --- Begin Message --- Source: libtest-postgresql-perl Source-Version: 1.23-2 We believe that the bug you reported is fixed in the latest version of libtest-postgresql-perl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 891...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Don Armstrong (supplier of updated libtest-postgresql-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 24 Feb 2018 17:54:02 -0800 Source: libtest-postgresql-perl Binary: libtest-postgresql-perl Architecture: source all Version: 1.23-2 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: Don Armstrong Description: libtest-postgresql-perl - sets up and destroys temporary PostgreSQL instances for testing Closes: 890540 891266 Changes: libtest-postgresql-perl (1.23-2) unstable; urgency=medium . * Document the rest of the authors in debian/changelog; apparently Kazuho Oku did 0.09 as a work for hire for Cybozu Labs. (Closes: #891266) . libtest-postgresql-perl (1.23-1) unstable; urgency=medium . * Initial Release (Closes: #890540) Checksums-Sha1: 8695cb6af2ff226bc50725acb017d9078d533767 2344 libtest-postgresql-perl_1.23-2.dsc 2f65c5829b1c82fb9c03edb215267884122945dc 27111 libtest-postgresql-perl_1.23.orig.tar.gz 5fcde8b7c2d74deef113822726fce067dbf7d372 5452 libtest-postgresql-perl_1.23-2.debian.tar.xz 00adf362d26c68bc34d3b7284c7954a506397959 14928 libtest-postgresql-perl_1.23-2_all.deb a74dcc60ba4bba8b98dde97ccc475016626e4e0d 7511 libtest-postgresql-perl_1.23-2_amd64.buildinfo Checksums-Sha256: b7126a8b824cb12d7c87c3feecf5e89699d06723f1330cc7d587330ea10d508b 2344 libtest-postgresql-perl_1.23-2.dsc 43c3ffcf414ae5fad69da19b246d394800b1c08a75607eb98dc298412e42b6fb 27111 libtest-postgresql-perl_1.23.orig.tar.gz d01bb5e61d700cc0e2e323de3d25436d58f836e1c7cf53d6c1f8e138b939064a 5452 libtest-postgresql-perl_1.23-2.debian.tar.xz 0fc52d3fa3359b4279f53f6f24e485ae91f4b6fb45c7b03a181bf1aa1a5e0819 14928 libtest-postgresql-perl_1.23-2_all.deb aec67ec29cb588c413e70f3a5cf788e63be349a4c4e8073ab130bb0ad374add4 7511 libtest-postgresql-perl_1.23-2_amd64.buildinfo Files: 34611f051e96e43aafebba771558cafa 2344 perl optional libtest-postgresql-perl_1.23-2.dsc 1a25b915d481e67b88fd15854984c70f 27111 perl optional libtest-postgresql-perl_1.23.orig.tar.gz a06f5d30eb01c9398fd59a397fc250d7 5452 perl optional libtest-postgresql-perl_1.23-2.debian.tar.xz 0e38e0c4656378c1d09a9911f513930c 14928 perl optional libtest-postgresql-perl_1.23-2_all.deb 658ab8b32b7c0612bfdbc49a4ba5a9ac 7511 perl optional libtest-postgresql-perl_1.23-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEKthluiYED2f5zDZgotEwAdmMD7oFAlqTmPgACgkQotEwAdmM D7p5GhAAhxFzDz+CG63T19AtZnhXsRo3WBwIX8lXVYGvDnmWwgjXUI55DVq+Slgp h/Q/Lvy29jo4sgpp83/ejRxW5W1iqsQUMnoPGw4iI2RH16k58ftBWYlBF2pCTa+J F4RkaxHO/CSQJHpbpMT0mxwUgTEfqHh83cHpoSiELpJ3M5MKqoveCqiAvr1I76t+ ogMkaXvsScYNyNvAMNniZ7hqY8lxuvgP5DTlZbhYVgDT90QlQ5N5Cv+swu7RkrvF QQlp5NRjmvHc65lEwJkC2GjJbCUvTxOs8iDzxxZfYaE0b4qg2wgvLfkdlYo/Ur3E fsQa6BX9RbQ/Wh/7pfqLs87rf2hwYEXmhRZ/NccaLwuG/dDRsSEeg9Y43CwAM5bE lS5rUGyV92YZ2i3qCWOzbTguUOKIZNavflusZJhbNy
Processed: tagging 866512
Processing commands for cont...@bugs.debian.org:
> tags 866512 + buster sid
Bug #866512 {Done: se...@debian.org (Steinar H. Gunderson)} [nageru] SIGFPE
when encoding H.264 video
Added tag(s) sid and buster.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
866512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866512
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#891597: tomboy FTBFS: No rule to make target '.config.in', needed by '../bin/Tomboy.exe.config'.
Source: tomboy Version: 1.14.1-4 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/tomboy.html ... make[4]: *** No rule to make target '.config.in', needed by '../bin/Tomboy.exe.config'. Stop. make[4]: Leaving directory '/build/1st/tomboy-1.14.1/Tomboy' make[3]: *** [Makefile:694: all-recursive] Error 1
Bug#891596: CVE-2018-7409
Source: unixodbc Version: 2.3.4-1.1 Severity: grave Tags: security Hi, the following vulnerability was published for unixodbc. CVE-2018-7409[0]: | In unixODBC before 2.3.5, there is a buffer overflow in the | unicode_to_ansi_copy() function in DriverManager/__info.c. 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-2018-7409 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-7409 Please adjust the affected versions in the BTS as needed. signature.asc Description: PGP signature
Bug#871506: stretch update for hdf5
On 02/26/2018 10:23 PM, Adrian Bunk wrote: > On Sun, Aug 13, 2017 at 05:51:08PM +, Debian Bug Tracking System wrote: >> ... >> hdf5 (1.10.0-patch1+docs-4) unstable; urgency=medium >> . >>* debian/rules: fix javahelper invocation (closes: #871506) >> ... > > Thanks a lot for fixing this bug for unstable. > > It is still present in stretch, could you also fix it there? > Alternatively, I can fix it for stretch if you don't object. The stretch-pu was requested in #872642 and given a go-ahead. It's just a matter of uploading or am I missing something? Kind Regards, Bas
Processed: found 867128 in 15
Processing commands for cont...@bugs.debian.org:
> found 867128 15
Bug #867128 {Done: Alf Gaida } [lxqt] cmst |
network-manager-gnome is to hard
Marked as found in versions lxqt-metapackages/15.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
867128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867128
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: fixed 889873 in 2.0.2+dfsg-2
Processing commands for cont...@bugs.debian.org: > fixed 889873 2.0.2+dfsg-2 Bug #889873 [vagrant] vagrant: unable to download images (moved from atlas.hashicorp.com to app.vagrantup.com) Marked as fixed in versions vagrant/2.0.2+dfsg-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 889873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889873 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 891575 is important
Processing commands for cont...@bugs.debian.org: > severity 891575 important Bug #891575 [elinks] elinks: CVE-2012-6709 Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 891575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891575 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#871506: stretch update for hdf5
On Sun, Aug 13, 2017 at 05:51:08PM +, Debian Bug Tracking System wrote: >... > hdf5 (1.10.0-patch1+docs-4) unstable; urgency=medium > . >* debian/rules: fix javahelper invocation (closes: #871506) >... Thanks a lot for fixing this bug for unstable. It is still present in stretch, could you also fix it there? Alternatively, I can fix it for stretch if you don't object. Thanks Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Processed: tag #891215: qmmp FTBFS: AutoMoc error pending
Processing commands for cont...@bugs.debian.org: > tag 891215 pending Bug #891215 [src:qmmp] qmmp FTBFS: AutoMoc error Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. -- 891215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891215 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 866791
Processing commands for cont...@bugs.debian.org:
> tags 866791 + buster sid
Bug #866791 {Done: Jonas Smedegaard } [libdata-messagepack-perl]
libdata-messagepack-perl: FTBFS against msgpack-c 2.x
Added tag(s) buster and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
866791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866791
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#890715: marked as done (designate: Incomplete debian/copyright?)
Your message dated Mon, 26 Feb 2018 21:00:12 + with message-id and subject line Bug#890715: fixed in designate 1:6.0.0~rc1-1 has caused the Debian Bug report #890715, regarding designate: Incomplete debian/copyright? 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.) -- 890715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890715 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: designate Version: 1:5.0.1-1 Severity: serious Justication: Policy 12.5 X-Debbugs-CC: Thomas Goirand Hi, I just ACCEPTed designate from NEW but noticed it was missing attribution in debian/copyright for at least Rackspace, eBay, "Managed I.T." etc. (This is not exhaustive so please check over the entire package carefully and address these on your next upload.) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- --- End Message --- --- Begin Message --- Source: designate Source-Version: 1:6.0.0~rc1-1 We believe that the bug you reported is fixed in the latest version of designate, 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 890...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated designate package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 24 Feb 2018 22:21:45 + Source: designate Binary: designate designate-agent designate-api designate-central designate-common designate-doc designate-mdns designate-pool-manager designate-producer designate-sink designate-worker designate-zone-manager python3-designate Architecture: source all Version: 1:6.0.0~rc1-1 Distribution: experimental Urgency: medium Maintainer: Debian OpenStack Changed-By: Thomas Goirand Description: designate - OpenStack DNS as a Service - metapackage designate-agent - OpenStack DNS as a Service - agent designate-api - OpenStack DNS as a Service - API server designate-central - OpenStack DNS as a Service - central daemon designate-common - OpenStack DNS as a Service - common files designate-doc - OpenStack DNS as a Service - doc designate-mdns - OpenStack DNS as a Service - mdns designate-pool-manager - OpenStack DNS as a Service - pool manager designate-producer - OpenStack DNS as a Service - producer designate-sink - OpenStack DNS as a Service - sink designate-worker - OpenStack DNS as a Service - worker designate-zone-manager - OpenStack DNS as a Service - zone manager python3-designate - OpenStack DNS as a Service - Python libs Closes: 890715 Changes: designate (1:6.0.0~rc1-1) experimental; urgency=medium . [ David Rabel ] * Fix d/copyright (Closes: #890715). . [ Thomas Goirand ] * New upstream release. * Fixed (build-)depends for this release. * Remove make-designate.conf-build-reproducibly.patch applied upstream. * Install other config files correctly. * Switch package to Python 3. * Add fixes-sphinx-doc-with-python3.patch. Checksums-Sha1: 40b56e5c19445c0b231658b525538a09901ac449 4578 designate_6.0.0~rc1-1.dsc f341f48248560eaf6972f6791d76e738d92dc42a 554544 designate_6.0.0~rc1.orig.tar.xz ee564fe59a974e3da2f6a3e3de6d0a3607f08d4e 18072 designate_6.0.0~rc1-1.debian.tar.xz a12329f37f1c7bba28d52fea064a9ca7e621b72f 9088 designate-agent_6.0.0~rc1-1_all.deb 0d1357cff66ce525b9533bfa35b1c22c06cf5946 19856 designate-api_6.0.0~rc1-1_all.deb 3893d837e6d9a18f58cddbb85c8a1969d6e4650b 9104 designate-central_6.0.0~rc1-1_all.deb f32caeb0cd9525d5e4570dc2f5f288fdd6b377ae 39340 designate-common_6.0.0~rc1-1_all.deb d55257599891b1a766e11f43b279054e5443ac38 1133904 designate-doc_6.0.0~rc1-1_all.deb 36c996db83cf6a07d3e6bc72ee7fe78d733c3cb3 9088 designate-mdns_6.0.0~rc1-1_all.deb eb3def0514bec2e141b9ce49c1be76163d6ff2f1 9108 designate-pool-manager_6.0.0~rc1-1_all.deb 645084dcec4f83f7beb3174869cf378139efc622 9092 designate-producer_6.0.0~rc1-1_all.deb 4b4e65bdddb88230dd66b15e7ac8897abe15076d 9068 designate-sink_6.0.0~rc1-1_all.deb aa785fdaee2fabc846a9247a79e9c496a41101aa 9068 designate-worker_6.0.0~rc1-1_all.deb d75bae5dc1644048ea1ed11a14ca864567a28d9c 9108 designate-zone-manager
Bug#891296: marked as done (x2goserver binary-all FTBFS: chmod: cannot access 'debian/x2goserver/usr/lib/x2go/*': No such file or directory)
Your message dated Mon, 26 Feb 2018 21:00:39 + with message-id and subject line Bug#891296: fixed in x2goserver 4.1.0.0-3 has caused the Debian Bug report #891296, regarding x2goserver binary-all FTBFS: chmod: cannot access 'debian/x2goserver/usr/lib/x2go/*': No such file or directory 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.) -- 891296: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891296 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: x2goserver Version: 4.1.0.0-2 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=x2goserver&arch=all&ver=4.1.0.0-2&stamp=1519444735&raw=0 ... dh_install # FIXME: upstream has some X2Go scripts in their tarball that are not executable chmod a+x debian/x2goserver/usr/lib/x2go/* chmod: cannot access 'debian/x2goserver/usr/lib/x2go/*': No such file or directory make[1]: *** [debian/rules:31: override_dh_install] Error 1 --- End Message --- --- Begin Message --- Source: x2goserver Source-Version: 4.1.0.0-3 We believe that the bug you reported is fixed in the latest version of x2goserver, 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 891...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel (supplier of updated x2goserver 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, 25 Feb 2018 14:41:16 +0100 Source: x2goserver Binary: x2goserver libx2go-log-perl libx2go-server-db-perl libx2go-server-perl x2goserver-common x2goserver-extensions x2goserver-fmbindings x2goserver-printing x2goserver-x2goagent x2goserver-xsession Architecture: source all amd64 Version: 4.1.0.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Remote Maintainers Changed-By: Mike Gabriel Description: libx2go-log-perl - Perl X2Go::Log package libx2go-server-db-perl - Perl X2Go::Server:DB package libx2go-server-perl - Perl X2Go::Server package x2goserver - X2Go server x2goserver-common - X2Go Server (common files) x2goserver-extensions - X2Go server (extension support) x2goserver-fmbindings - X2Go Server (file manager bindings) x2goserver-printing - X2Go server (printing support) x2goserver-x2goagent - X2Go Server's X2Go Agent x2goserver-xsession - X2Go server (Xsession runner) Closes: 891296 Changes: x2goserver (4.1.0.0-3) unstable; urgency=medium . * debian/rules: + Ignore chmod failures when adapting x-bits in /usr/lib/x2go/*. Fixes FTBFS for binary-all build target. (Closes: #891296). Checksums-Sha1: 18261df92b7817debab52de387036e24782438e6 2932 x2goserver_4.1.0.0-3.dsc 96c2c10a24dacc8a4ccc3aa880158af792cd45a2 25408 x2goserver_4.1.0.0-3.debian.tar.xz d0d2adb7b00ef5f20a07bca8661dca7cf3741b37 40424 libx2go-log-perl_4.1.0.0-3_all.deb 356552fe884975fbbd3c97651f6ab555e48c83f5 3156 libx2go-server-db-perl-dbgsym_4.1.0.0-3_amd64.deb a6ebddc2ff6b642128d4e3174c2a96d9797ec602 51796 libx2go-server-db-perl_4.1.0.0-3_amd64.deb f74d9e87f75463ed22735f5524a59966b1a24922 49760 libx2go-server-perl_4.1.0.0-3_all.deb 108cc72fbffc27bc3845a07485a9cbf42da98ae1 42692 x2goserver-common_4.1.0.0-3_amd64.deb 8a4152f2faa4f5582978d5b1a60ef0d1dad19cf0 44020 x2goserver-extensions_4.1.0.0-3_all.deb fe1730d09d7e5000852a69343510d3778e5bd8c1 40620 x2goserver-fmbindings_4.1.0.0-3_all.deb 81de4c87963746e82f6b777eb774cf62ae0c371e 44860 x2goserver-printing_4.1.0.0-3_all.deb 72a2d6047a88721b802e8b49816ac97b139a79ff 42784 x2goserver-x2goagent_4.1.0.0-3_amd64.deb a87617fe27d480fe715d3fd66195b0f66242bf64 42860 x2goserver-xsession_4.1.0.0-3_all.deb 2732b9608c13c0e0a9665d173cab8abf31b0d125 8466 x2goserver_4.1.0.0-3_amd64.buildinfo 87be75c9fb82d8191a687e9a51f29b0c4ea43184 106500 x2goserver_4.1.0.0-3_amd64.deb Checksums-Sha256: cfc0ae039072139dfbe9aa0c2f1e2a767d66e447b312b3945b391a6ef1b47284 2932 x2goserver_4.1.0.0-3.dsc b1a36c26528c8b501b61691e4aa4dca11e26d5c130f5a3232339cb82701cbc6d 25408 x2goserver_4.1.0.0-3.debian.tar.xz 6d0d539b0d41b8d003b06a9f050f0fb91a5bb12dff0ce4aa8c05008620084d59 40424 libx2go-log-perl_4.1.0.0-3_all.deb 6956890a4706953fba4f6cec2ef9b667b6fe9ed7c7cbf11a9812fbb6a542af3f 3156 libx2go-server-db-per
Bug#889210: stretch update for libdap
On Sat, Feb 03, 2018 at 01:51:18PM +, Debian Bug Tracking System wrote: >... > libdap (3.19.1-2) unstable; urgency=medium >... >* Add libdap-doc.docs to install docs. Closes: #889210 >... Thanks a lot for fixing this bug for unstable. It is still present in stretch, could you also fix it there? Alternatively, I can fix it for stretch if you don't object. Thanks Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#887673: marked as done (graphviz: Drop dependency on libgnomeui)
Your message dated Mon, 26 Feb 2018 21:00:32 + with message-id and subject line Bug#887673: fixed in graphviz 2.40.1-1 has caused the Debian Bug report #887673, regarding graphviz: Drop dependency on libgnomeui 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.) -- 887673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887673 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: graphviz Version: 2.38.0-18 Severity: normal X-Debbugs-Cc: 885767-submit...@bugs.debian.org According to #885767 , libgnomeui is slated for removal from sid and buster. So, it would be great to have src:libgnomeui drop the Build-Depends on libgnomeui-dev (and the corresponding dependencies of binary packages, if any - though I didn't notice any of the src:graphviz packages showing up in my quick scan of the output of "apt-cache showpkg libgnomeui-0"). -- Daniel Schepler --- End Message --- --- Begin Message --- Source: graphviz Source-Version: 2.40.1-1 We believe that the bug you reported is fixed in the latest version of graphviz, 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 887...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laszlo Boszormenyi (GCS) (supplier of updated graphviz 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, 25 Feb 2018 14:26:18 + Source: graphviz Binary: graphviz libgv-guile libgv-lua libgv-perl libgv-php7 python-gv python3-gv libgv-ruby libgv-tcl libcgraph6 libcdt5 libpathplan4 libgvc6 libgvc6-plugins-gtk libgvpr2 libxdot4 liblab-gamut1 libgraphviz-dev graphviz-doc Architecture: source amd64 all Version: 2.40.1-1 Distribution: experimental Urgency: medium Maintainer: Laszlo Boszormenyi (GCS) Changed-By: Laszlo Boszormenyi (GCS) Description: graphviz - rich set of graph drawing tools graphviz-doc - additional documentation for graphviz libcdt5- rich set of graph drawing tools - cdt library libcgraph6 - rich set of graph drawing tools - cgraph library libgraphviz-dev - graphviz libs and headers against which to build applications libgv-guile - Guile bindings for graphviz libgv-lua - Lua bindings for graphviz libgv-perl - Perl bindings for graphviz libgv-php7 - PHP7 bindings for graphviz libgv-ruby - Ruby bindings for graphviz libgv-tcl - Tcl bindings for graphviz libgvc6- rich set of graph drawing tools - gvc library libgvc6-plugins-gtk - rich set of graph drawing tools - gtk plugins libgvpr2 - rich set of graph drawing tools - gvpr library liblab-gamut1 - rich set of graph drawing tools - liblab_gamut library libpathplan4 - rich set of graph drawing tools - pathplan library libxdot4 - rich set of graph drawing tools - xdot library python-gv - Python bindings for graphviz python3-gv - Python3 bindings for graphviz Closes: 691023 884479 887673 Changes: graphviz (2.40.1-1) experimental; urgency=medium . * New major upstream release (closes: #884479). * Use short debhelper rules format. * Drop libgnomeui-dev build dependency (closes: #887673). * Switch back to Guile 2.0 build dependency. * Rename libgv-python to python-gv package. * Add liblab-gamut1 package. * Drop graphviz-dev old transitional package. * Update Standards-Version to 4.1.3 . * Update debhelper level to 11: - remove dh-autoreconf build dependency, - remove autotools-dev build dependency. . [ Matthias Klose ] * Build new libgv-php7 . * Build a python3-gv package (closes: #691023). Checksums-Sha1: 7d556d75d447ada54472552a18a72090f1f8a835 3322 graphviz_2.40.1-1.dsc 8a44d19bcdb50df1bd8e649de472ebf86846 25633455 graphviz_2.40.1.orig.tar.gz 5f730a50724b2ee42507dafb2e5de908810dd41b 42668 graphviz_2.40.1-1.debian.tar.xz 4f12cbb662488389a471c0b725e136168a932bed 1706696 graphviz-dbgsym_2.40.1-1_amd64.deb 522c9a7ceab62036225e4c7729e41cb9f475eab1 3894880 graphviz-doc_2.40.1-1_all.deb 20efd93e3a139d34498726b248e08f8d35f37c73 23905 graphviz_2.40.1-1_amd64.buildinfo 1ab02ffdf7232b5a2cfd0d455c9984dac65ab93c 633796 graphviz_2.40.1-1_amd64.deb 0247a88a91abe256699ac33b315e6d18752b4cc3 21628 libcdt5-dbgsym_2.40.1-1_amd64.deb d3
Processed: found 889873 in 1.9.1+dfsg-1, notfound 889873 in 2.0.2+dfsg-2
Processing commands for cont...@bugs.debian.org: > found 889873 1.9.1+dfsg-1 Bug #889873 [vagrant] vagrant: unable to download images (moved from atlas.hashicorp.com to app.vagrantup.com) Ignoring request to alter found versions of bug #889873 to the same values previously set > notfound 889873 2.0.2+dfsg-2 Bug #889873 [vagrant] vagrant: unable to download images (moved from atlas.hashicorp.com to app.vagrantup.com) Ignoring request to alter found versions of bug #889873 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 889873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889873 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 875627
Processing commands for cont...@bugs.debian.org:
> tags 875627 + buster sid
Bug #875627 {Done: Xavier Guimard } [libauthen-captcha-perl]
libauthen-captcha-perl: Random failure due to bad images
Added tag(s) sid and buster.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
875627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875627
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: reassign 891567 to vagrant-libvirt, reassign 891568 to vagrant-libvirt ...
Processing commands for cont...@bugs.debian.org:
> reassign 891567 vagrant-libvirt
Bug #891567 [vagrant] vagrant: Unable to resolve dependency: 'vagrant-libvirt
(> 0)' requires 'fog-core (~> 1.44.0)'
Bug reassigned from package 'vagrant' to 'vagrant-libvirt'.
No longer marked as found in versions vagrant/2.0.2+dfsg-2.
Ignoring request to alter fixed versions of bug #891567 to the same values
previously set
> reassign 891568 vagrant-libvirt
Bug #891568 [vagrant] vagrant: Unable to resolve dependency: 'vagrant-libvirt
(> 0)' requires 'fog-core (~> 1.44.0)'
Bug reassigned from package 'vagrant' to 'vagrant-libvirt'.
No longer marked as found in versions vagrant/2.0.2+dfsg-2.
Ignoring request to alter fixed versions of bug #891568 to the same values
previously set
> forcemerge 891498 891567 891568
Bug #891498 {Done: Antonio Terceiro } [vagrant-libvirt]
Needs fog-core (~> 1.44.0), but ruby-fog-core is now 1.45.0
Bug #891567 [vagrant-libvirt] vagrant: Unable to resolve dependency:
'vagrant-libvirt (> 0)' requires 'fog-core (~> 1.44.0)'
Severity set to 'serious' from 'important'
Marked Bug as done
The source vagrant-libvirt and version 0.0.43-2 do not appear to match any
binary packages
Marked as fixed in versions vagrant-libvirt/0.0.43-2.
Marked as found in versions vagrant-libvirt/0.0.43-1.
Bug #891568 [vagrant-libvirt] vagrant: Unable to resolve dependency:
'vagrant-libvirt (> 0)' requires 'fog-core (~> 1.44.0)'
Severity set to 'serious' from 'important'
Marked Bug as done
The source vagrant-libvirt and version 0.0.43-2 do not appear to match any
binary packages
Marked as fixed in versions vagrant-libvirt/0.0.43-2.
Marked as found in versions vagrant-libvirt/0.0.43-1.
Merged 891498 891567 891568
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
891498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891498
891567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891567
891568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891568
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 881598
Processing commands for cont...@bugs.debian.org:
> tags 881598 + buster sid
Bug #881598 {Done: Thomas Goirand } [ironic-inspector]
ironic-inspector: fails to install: ValueError: invalid literal for int() with
base 10: 'ironic_inspector.sqlite'
Added tag(s) sid and buster.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
881598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881598
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#891586: tomboy-latex: Build-Depends on tomboy
Source: tomboy-latex Version: 0.5-5 Severity: serious Tags: buster sid As part of an effort to remove unmaintained GNOME2 libraries from Debian, tomboy will likely be removed from Testing soon. When this happens, tomboy-latex will need to be removed from Testing too since it Build-Depends and Depends on tomboy. You may want to look into whether gnote can satisfy these dependencies. There is also a rewrite (in Pascal!) of Tomboy that has not been packaged in Debian yet: https://github.com/tomboy-notes/tomboy-ng I am filing an explicit bug here because tomboy is not eligible for auto-removal because its popcon is still too high (it used to be part of the 'gnome' metapackage.). References -- https://lists.debian.org/debian-devel/2018/02/msg00169.html https://bugs.debian.org/885804 Tomboy depends on gconf via gnome-sharp2 https://bugs.debian.org/877259 Tomboy FTBFS Thanks, Jeremy Bicha
Bug#884033: scilab-celestlab
Hello,
Indeed the changes from Scilab 5 to 6 include non-heterogeneous strings and
quotes around the save(...) input parameters; so simply replacing
execstr(sprintf('save(pathmacros+filesep()+''%s.bin'',%s)',vars(i),vars(i)));
by
execstr(sprintf('save(pathmacros+filesep()+''%s.bin’’,'’%s'')',vars(i),vars(i)));
should do it.
Regards,
Paul
> On 24 Feb 2018, at 17:22, Sylvestre Ledru wrote:
>
> Context:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884033
>
> + some upstream folks
>
> Le 19/12/2017 à 19:06, Julien Puydt a écrit :
>> Hi,
>>
>> again, a number of heterogeneous strings, then I get a prompt after
>> warnings, and quitting (several times) leads to a success.
>>
>> I haven't reproduced the segfault in this bug report, but I have found
>> problems which indicate that the three listed packages do not support
>> the most recent scilab version.
>>
>> What can we do to push things forward?
>>
>> Snark on #debian-science
>>
Processed: nmu: intercal_30:0.30-1
Processing control commands:
> block 879789 by -1
Bug #879789 {Done: Mark Brown } [intercal] intercal: Link
error when compiling Intercal programs
879789 was not blocked by any bugs.
879789 was not blocking any bugs.
Added blocking bug(s) of 879789: 891585
--
879789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879789
891585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891585
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#891582: Dependency missing in vulkan-utils
Package: vulkan Version: 1.0.65.2+dfsg1-1 Severity: serious Justification: 1 The utility "vulkan-smoketest" in the vulkan-utils package depends on layers in the libvulkan-dev package, but there is no dependency. This can be easily verified by running it with the "--validate" option: $ vulkan-smoketest --validate terminate called after throwing an instance of 'std::runtime_error' what(): instance layer VK_LAYER_LUNARG_standard_validation is missing Aborted The easiest way to fix this is simply add a dependency, but it raises the question of why the vulkan-utils package exists. Both vulkaninfo and smoketest could reasonably just be part of libvulkan-dev, as both are really vulkan developer utilities, rather than general purpose utilities.
Bug#875637: stretch update for iipimage-server
On Wed, Nov 22, 2017 at 09:21:10PM +, Debian Bug Tracking System wrote: >... > iipimage (1.0-3) unstable; urgency=medium > . >* Really fix apache configuration. Closes: #875637 >... Thanks a lot for fixing this bug for unstable. It is still present in stretch, could you also fix it there? Alternatively, I can fix it for stretch if you don't object. Thanks Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#890589: stretch-pu update for chaosreader
2018-02-26 14:27 GMT-03:00 Adrian Bunk : > On Fri, Feb 16, 2018 at 01:21:03PM +, Debian Bug Tracking System wrote: >>... >> chaosreader (0.96-3) unstable; urgency=medium >>... >>- Added libnet-dns-perl to Depends field. (Closes: #890589) >>... > > Thanks a lot for fixing this bug for unstable. > > It is still present in stretch, could you also fix it there? > Alternatively, I can fix it for stretch if you don't object. > Hi! In this month, my time is a bit compromissed. So, go ahead! Thanks in advance. Regards, Eriberto
Bug#891498: marked as done (Needs fog-core (~> 1.44.0), but ruby-fog-core is now 1.45.0)
Your message dated Mon, 26 Feb 2018 19:40:14 + with message-id and subject line Bug#891498: fixed in vagrant-libvirt 0.0.43-2 has caused the Debian Bug report #891498, regarding Needs fog-core (~> 1.44.0), but ruby-fog-core is now 1.45.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 891498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891498 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: vagrant-libvirt Version: 0.0.43-1 Severity: serious Upon Debian Sid upgrade, vagrant (with vagrant-libvirt) became unuseable with this error: > Vagrant failed to initialize at a very early stage: > > The plugins failed to initialize correctly. This may be due to manual > modifications made within the Vagrant home directory. Vagrant can > attempt to automatically correct this issue by running: > > vagrant plugin repair > > If Vagrant was recently updated, this error may be due to incompatible > versions of dependencies. To fix this problem please remove and re-install > all plugins. Vagrant can attempt to do this automatically by running: > > vagrant plugin expunge --reinstall > > Or you may want to try updating the installed plugins to their latest > versions: > > vagrant plugin update > > Error message given during initialization: Unable to resolve dependency: > 'vagrant-libvirt (> 0)' requires 'fog-core (~> 1.44.0) That's because ruby-fog-core was recently upgraded to 1.45.0 in Debian Sid. It seems that the .gemspec's dependencies need to be relaxed again. In any case, the Depends in vagrant-libvirt should really have an upper-version limit. --- End Message --- --- Begin Message --- Source: vagrant-libvirt Source-Version: 0.0.43-2 We believe that the bug you reported is fixed in the latest version of vagrant-libvirt, 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 891...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Antonio Terceiro (supplier of updated vagrant-libvirt 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, 26 Feb 2018 16:14:07 -0300 Source: vagrant-libvirt Binary: vagrant-libvirt Architecture: source Version: 0.0.43-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Antonio Terceiro Description: vagrant-libvirt - Vagrant plugin that adds an Libvirt provider to Vagrant Closes: 891498 Changes: vagrant-libvirt (0.0.43-2) unstable; urgency=medium . * 0001-gemspec-relax-dependencies.patch: make dependency on fog-core use >= instead of ~> (Closes: #891498) Checksums-Sha1: 1924e93ad18887e2e5e50d777337f45e437118ac 2310 vagrant-libvirt_0.0.43-2.dsc fd83e0a48f2aa3661a10051cb47950248bfcf173 4048 vagrant-libvirt_0.0.43-2.debian.tar.xz 015075b3940c8ee57fdfe6fa2fbc65fe79848658 9330 vagrant-libvirt_0.0.43-2_source.buildinfo Checksums-Sha256: 51b8fb23d923484a6a56c7f52fc8947068f699afc376b33d31b5baf932628d9f 2310 vagrant-libvirt_0.0.43-2.dsc 8590690edab1892e22e76e22c74f1a49e337da7de198c23997b369db42769a47 4048 vagrant-libvirt_0.0.43-2.debian.tar.xz a55dda886668aa4226e286fc30f613cfcb6cda887cf32f27d0c5a4572523a4c0 9330 vagrant-libvirt_0.0.43-2_source.buildinfo Files: ca992db6eb9e5e48a9f511322a99bd57 2310 ruby optional vagrant-libvirt_0.0.43-2.dsc 63684d5b8880174127612c1ca1856842 4048 ruby optional vagrant-libvirt_0.0.43-2.debian.tar.xz c69be71d1ee1142a12ac0be3546673a5 9330 ruby optional vagrant-libvirt_0.0.43-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAlqUXRYACgkQ/A2xu81G C962jA/+OaMgL1aC+XemzerFXEGSd9fAatAGR+wO9GMXl6W5y2h89XC6iEV0Rf1a 4Zf9r7stdOKnqzqbdXMDfpILe328PSJhiN/r7tVmxjMHw2QhE6hwy5i4wLIKBCBO X7fiWZF477DdksSRR8EZLLs2mQ2lCNAOUDUW4cDxTmAtUmX3J3oPtYggdXzUULHv WlsLFGavPWGY6w8nXFyrjJfvztg19vaJaJW0DHz5B6bX84eQOnEXKz1k4tPX74Xm ag+m28iomWbzGgwvVKc3Fkn4k2HXxEx0qwU+lceQjlbnH+3adP23ucpxfd3D4bxp A/wYfzLuzO25YjNCqrzuGa23FBqy8vwB7A9B/bRWZC958NHlN12si9Ik7zvdv+ut i0aRtAXjo32jmS5tq4nGOf6C73iLeZyEnslYhtYuJ7vvqBj1Qke339xAse9WQaPu c+wEN0YPTR4ywtZsPLlcPeq/M4vMjnYwhjuKpoCm1nV4PHaUK4nd9WM89zDVioB6 5yjwqkhdzXPt4aMSgHH3gTSgtMUyHCIolvVT60KuwmQ6MGkzCf1V73CSWRW6
Bug#884417: python-trezor v0.9.0 tagged - next steps?
On Mon, 26 Feb 2018 at 21:20 Andreas Beckmann wrote:
> This is what I understood from reading debian/{changelog,control} and
> the upload notifications on the qa page [1]: the package was split with
> the 0.7.16-1 upload, but lacks proper Breaks+Replaces for the files
> being moved around.
>
Yes, this is a relatively straightforward fix, sorry for the delay in
implementing it! I'll try to take care of it this week. It's just an issue
with the Debian packaging, not the upstream portion.
Bug#891498: Bug #891498 in vagrant-libvirt marked as pending
Control: tag -1 pending Hello, Bug #891498 in vagrant-libvirt reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/vagrant-libvirt/commit/b9b36d04d55caaa1b82caa4d240f34f25627c2a4 make dependency on fog-core use >= instead of ~> Closes: #891498 (this message was generated automatically) -- Greetings
Bug#884417: python-trezor v0.9.0 tagged - next steps?
[ adding the bug back into the loop, please keep it Cc:ed ]
On 2018-02-26 19:23, Jonathan Cross wrote:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884417
>
> What would be the next steps in getting past this?
>
> How can we indicate that '/usr/bin/trezorctl' should be replaced?
In debian/control, in the 'Package: trezor' stanza, add
Breaks: python-trezor (<< 0.7.16)
Replaces: python-trezor (<< 0.7.16)
Disclaimer: completely untested!
This is what I understood from reading debian/{changelog,control} and
the upload notifications on the qa page [1]: the package was split with
the 0.7.16-1 upload, but lacks proper Breaks+Replaces for the files
being moved around.
[1] https://packages.qa.debian.org/p/python-trezor.html
Andreas
Processed: Bug #891498 in vagrant-libvirt marked as pending
Processing control commands: > tag -1 pending Bug #891498 [vagrant-libvirt] Needs fog-core (~> 1.44.0), but ruby-fog-core is now 1.45.0 Added tag(s) pending. -- 891498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891498 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#891570: SSL connect attempt failed error:141A90B5:SSL routines:ssl_cipher_list_to_bytes:no ciphers available
On 2018-02-27 02:37:38 [+0800], 積丹尼 Dan Jacobson wrote: > Package: libssl1.1 > Version: 1.1.1~~pre1-1 > Severity: grave > > SSL connect attempt failed error:141A90B5:SSL > routines:ssl_cipher_list_to_bytes:no ciphers available Can you give more information how to reproduce this? My first guess is that you have TLS1.3 enabled on the client side but the cipher list does not permit any TLS1.3 cipher. Sebastian
Processed (with 1 error): forcibly merging 891498 891567 891568
Processing commands for cont...@bugs.debian.org: > forcemerge 891498 891567 891568 Bug #891498 [vagrant-libvirt] Needs fog-core (~> 1.44.0), but ruby-fog-core is now 1.45.0 Unable to merge bugs because: package of #891568 is 'vagrant' not 'vagrant-libvirt' package of #891567 is 'vagrant' not 'vagrant-libvirt' Failed to forcibly merge 891498: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 891498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891498 891567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891567 891568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891568 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): merging 891498 891567 891568
Processing commands for cont...@bugs.debian.org: > merge 891498 891567 891568 Bug #891498 [vagrant-libvirt] Needs fog-core (~> 1.44.0), but ruby-fog-core is now 1.45.0 Unable to merge bugs because: severity of #891567 is 'important' not 'serious' package of #891567 is 'vagrant' not 'vagrant-libvirt' severity of #891568 is 'important' not 'serious' package of #891568 is 'vagrant' not 'vagrant-libvirt' Failed to merge 891498: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 891498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891498 891567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891567 891568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891568 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#888172: marked as done (ruby-rspec-its: FTBFS on ruby2.5: Fixnum/Integer)
Your message dated Mon, 26 Feb 2018 19:06:31 + with message-id and subject line Bug#888172: fixed in ruby-rspec-its 1.2.0-3 has caused the Debian Bug report #888172, regarding ruby-rspec-its: FTBFS on ruby2.5: Fixnum/Integer 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.) -- 888172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888172 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-rspec-its Version: 1.2.0-2 Severity: important User: debian-r...@lists.debian.org Usertags: ruby2.5 Dear Maintainer, This package fails to build against ruby2.5. Soon, there will be a transition to ruby2.5, and this package will FTBFS in sid. There may be some details on the wiki about common problems: https://wiki.debian.org/Teams/Ruby/Ruby25Transition Build log excerpt: Failures: 1) RSpec::Its#its with explicit subject when it responds to #[] [:b, "c", 4] should eq "Symbol: b; String: c; Fixnum: 4" Failure/Error: RSpec::Expectations::PositiveExpectationHandler.handle_matcher(__its_subject, matcher, message) expected: "Symbol: b; String: c; Fixnum: 4" got: "Symbol: b; String: c; Integer: 4" (compared using ==) # ./spec/rspec/its_spec.rb:89:in `block (5 levels) in ' Finished in 0.02877 seconds (files took 0.09433 seconds to load) 34 examples, 1 failure Failed examples: rspec ./spec/rspec/its_spec.rb:89 # RSpec::Its#its with explicit subject when it responds to #[] [:b, "c", 4] should eq "Symbol: b; String: c; Fixnum: 4" Randomized with seed 35708 /usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb failed ERROR: Test "ruby2.5" failed. Exiting. dh_auto_install: dh_ruby --install /build/ruby-rspec-its-1.2.0/debian/ruby-rspec-its returned exit code 1 debian/rules:15: recipe for target 'binary' failed make: *** [binary] Error 1 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Full build log: https://rbuild.fau.xxx/2018-01-23/ruby-rspec-its.log Please fix it! Cheers, Chris. --- End Message --- --- Begin Message --- Source: ruby-rspec-its Source-Version: 1.2.0-3 We believe that the bug you reported is fixed in the latest version of ruby-rspec-its, 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 888...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Balasankar C (supplier of updated ruby-rspec-its package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 27 Feb 2018 00:04:47 +0530 Source: ruby-rspec-its Binary: ruby-rspec-its Architecture: source Version: 1.2.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Balasankar C Description: ruby-rspec-its - attribute matching extension for the RSpec BDD framework Closes: 888172 Changes: ruby-rspec-its (1.2.0-3) unstable; urgency=medium . * Team upload. * Add patch to make tests run with Ruby 2.5 (Closes: #888172) * Bump debhelper compatibility to 11 * Bump Standards-Version to 4.1.3 (No changes) Checksums-Sha1: d737e68ac7f03d3258fed5c168331fa8996e275d 2131 ruby-rspec-its_1.2.0-3.dsc 4ff89beeab525ea2ee820062cf201822a71dd632 2904 ruby-rspec-its_1.2.0-3.debian.tar.xz b6d9428886167663618a5c3de9269adb3a8c1da3 7314 ruby-rspec-its_1.2.0-3_source.buildinfo Checksums-Sha256: 59fed0b4d6689d8f4e361d9966b97154ab974a3dd5f934b67c7757014225a49f 2131 ruby-rspec-its_1.2.0-3.dsc 9929a7596ac7fb387ad97bdb7b8ec57ac201e9f400e977cee7a14a1322415ddb 2904 ruby-rspec-its_1.2.0-3.debian.tar.xz 2905a17af1981a8f22f3c92e25a52817712a400dff8f6aa25accd8c5dca7d34a 7314 ruby-rspec-its_1.2.0-3_source.buildinfo Files: c70fee9f231bd4fc4a976571a3e418af 2131 ruby optional ruby-rspec-its_1.2.0-3.dsc f03d2b18fda325edd235bdac918a6223 2904 ruby optional ruby-rspec-its_1.2.0-3.debian.tar.xz 8bd25a89177a77d64f823e68c91fdbba 7314 ruby optional ruby-rspec-its_1.2.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJLBAEBCgA1FiEE3fK4OxY1M+BbaW1bt30uLiNzVCcFAlqUV9YXHGJhbGFzYW5r YXJjQGRlYmlhbi5vcmcACgkQt30uLiNzVCdHeg/+N8sHHS12vurxh0fUxWAzEiKs 1h0QVNtijOkAJw6R8qsadewrtAG0WO9rk1Oydq4rYO2j5wfvf+UUIY1ybUx6MY36 LH62qsHYB+WeCcDlCqBT0o
Bug#891575: elinks: CVE-2012-6709
Package: elinks Version: 0.12~pre5-9 X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, the following vulnerability was published for elinks. CVE-2012-6709[0]: | ELinks 0.12 and Twibright Links 2.3 have Missing SSL Certificate | Validation. 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-2012-6709 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-6709 Please adjust the affected versions in the BTS as needed. -- signature.asc Description: PGP signature
Bug#877645: marked as done (source-highlight: libsource-highlight-dev depends on libboost-dev instead of libboost-regex-dev)
Your message dated Mon, 26 Feb 2018 19:07:08 + with message-id and subject line Bug#877645: fixed in source-highlight 3.1.8-1.2 has caused the Debian Bug report #877645, regarding source-highlight: libsource-highlight-dev depends on libboost-dev instead of libboost-regex-dev 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.) -- 877645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877645 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libsource-highlight-dev Version: 3.1.8-1.1 Severity: serious Tags: patch source-highligt uses the regex module from boost, and therefore has a libboost-regex-dev build-dependency, and the pkgconfig has -lboost_regex, etc, etc. Now, the libsource-highlight-dev package has a dependency on libboost-dev though, but libboost-dev doesn't pull in libboost-regex-dev (by design), therfore packages trying to build against libsource-highlight-dev fails to link due to this missing dependency. Please fix the dependency (I'm not providing a patch, as it would take longer to download the package than to whoever is going to fix it to do the change himself). -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: source-highlight Source-Version: 3.1.8-1.2 We believe that the bug you reported is fixed in the latest version of source-highlight, 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 877...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated source-highlight package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 24 Feb 2018 20:36:52 +0200 Source: source-highlight Binary: source-highlight libsource-highlight-dev libsource-highlight4v5 libsource-highlight-common Architecture: source Version: 3.1.8-1.2 Distribution: unstable Urgency: medium Maintainer: Peter Eisentraut Changed-By: Adrian Bunk Description: libsource-highlight-common - architecture-independent files for source highlighting library libsource-highlight-dev - development files for source highlighting library libsource-highlight4v5 - source highlighting library source-highlight - convert source code to syntax highlighted document Closes: 877645 Changes: source-highlight (3.1.8-1.2) unstable; urgency=medium . * Non-maintainer upload. * libsource-highlight-dev: Fix the dependency from libboost-dev to libboost-regex-dev. (Closes: #877645) Checksums-Sha1: 4de1fd7de34373461a1a7f6c6ab241a53c3a43ea 2140 source-highlight_3.1.8-1.2.dsc eb2704cadb856791165a32a6a55665753963d56c 5220 source-highlight_3.1.8-1.2.debian.tar.xz Checksums-Sha256: decda9f7b05ced26064bd41b43711d0b6f8af0c6c257feee5dbc17ee9fda74fc 2140 source-highlight_3.1.8-1.2.dsc c2a93630d82219ad9fc6c5e4b2cfaf5fe6472f898d5b7afd643a82187e360176 5220 source-highlight_3.1.8-1.2.debian.tar.xz Files: 5ab48bb4b0a7f7118a6a836ca6840fc7 2140 devel optional source-highlight_3.1.8-1.2.dsc fbce96f48df3331017a3c9ed83ff7c73 5220 devel optional source-highlight_3.1.8-1.2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlqRsmwACgkQiNJCh6LY mLF7FA/9GseFlHgw3QQ/C6+g/hiU+kHl6zZSmjtLr9y3OF7QZ/v/P+pOzlZTtUNV lYs5WKcWqZN2AQ+yAgH75h6t1KMLTkQ00V5IL9AGsZkc2fxpRJRxWrPtr/qtdt+I VZV+IFEJ3vUyGn9SX3VyuHAXgbhC5J6rKtnesbhoKcRbHIVkp8UHdvX1ZibqHEqO TQUq9b+6GNfzE72gfHtYkOOVxZd/C3yvtc5+H6G1uFmQSxQ+p5sPn+Hdnyunl5/W maxeKRYqpNzKkrTJbjnqvbmkNMVTQBWptOt+ZDkJKFiHKzJhlQjegvbzzGCKHkQw IvohPK1HcStRhZTeNWKS2QMICCvjUhdGkLH93BaR77XXF2M2I4Rb31ee56nQeKY6 n4Z2H73l4g8Oh8NyViHICtFW2IXVM7CiKfbpzQPFB/pozJ3NuUovbD3W0Z9cMGUi du7f4hlT2YsbXhYubfFhRHgzNf/Q7nAmin7Gg8fQKEK4pcHXPKeYX4xqcKRnqXa0 h6k/15G5MFMmlEMDLY7ReYlnk91usfbABS/mU29wSRJjY4iWABpvjteQ4VwSTF2M HdLGUsKX5tZdPPQeGMvpwunb9hF3fsFSEXYraEDwqMoGMmkaH0F0pulwzLZiTpQI nEHvsWEDkogwdrAipzSHy
Bug#891573: openjdk-10: builds with unlimited 'make -j'
Source: openjdk-10 Version: 10~32-1 Severity: serious Justification: make build machine unusable while building Hi, I just stumbled upon load 425 while rebuilding openjdk-10 in experimental ... the build runs with DEB_BUILD_OPTIONS=parallel=4 There seem to be some unlimited 'make -j' calls ... Unfortunately no such commands were logged in the build logfile, the only evidence I have left is a screen full of 'ps aux | grep make | grep -- -j' output: 1234 3767 0.0 0.0 8892 1660 pts/40 SN+ 18:34 0:00 /usr/bin/make -r -R -I /build/openjdk-10-10~32/make/common SPEC=/build/openjdk-10-10~32/build/spec.gmk MAKE_LOG_FLAGS= LOG_LEVEL=debug LOG_NOFILE= L OG_CMDLINES= LOG_PROFILE_TIMES_LOG= LOG_PROFILE_TIMES_FILE= -Onone -j 4 -f make/Main.gmk bootcycle-images 1234 3768 0.0 0.0 9668 1736 pts/40 S+ 18:34 0:00 /bin/bash -o pipefail -e -c ( cd /build/openjdk-10-10~32 && \ /usr/bin/nice /usr/bin/make -r -R -I /build/openjdk-10-10~32/make/common SPEC =/build/openjdk-10-10~32/build/spec.gmk MAKE_LOG_FLAGS="" LOG_LEVEL=debug LOG_NOFILE= LOG_CMDLINES= LOG_PROFILE_TIMES_LOG= LOG_PROFILE_TIMES_FILE= -Onone \ -j 4 -f make/Main.gmk \ bootcycle-images > >(/usr/bin/tee -a /build/openjdk-10-10~32/build/build.log) 2> >(/usr/bin/tee -a /build/openjdk-10-10~32/build/build.log >&2) && wait || \ ( exitcode=$? && \ /usr/bin/printf "\nERROR: Build failed for target 'bootcycle-images' in configuration '/build/openjdk-10-10~32/build' (exit code $exitcode) \n" \ > >(/usr/bin/tee -a /build/openjdk-10-10~32/build/build.log) 2> >(/usr/bin/tee -a /build/openjdk-10-10~32/build/build.log >&2) && wait && \ cd /build/openjdk-10-10~32 && /usr/bin/make -r -R -I /build/openjdk-10-10~32/make/common SPEC=/build/openjdk-10-10~32/build/spec.gmk MAKE_LOG_FLAGS="" LOG_LEVEL=debug LOG_NOFILE= LOG_CMDLINES= LOG_PROFILE_TIMES_LOG= LOG_PROFILE_TIMES_FILE= -j 1 -f make/Init.gmk \ HAS_SPEC=true on-failure ; \ exit $exitcode ) ) 1234 3769 0.0 0.0 9668 1692 pts/40 S+ 18:34 0:00 /bin/bash -o pipefail -e -c ( cd /build/openjdk-10-10~32 && \ /usr/bin/nice /usr/bin/make -r -R -I /build/openjdk-10-10~32/make/common SPEC=/build/openjdk-10-10~32/build/spec.gmk MAKE_LOG_FLAGS="" LOG_LEVEL=debug LOG_NOFILE= LOG_CMDLINES= LOG_PROFILE_TIMES_LOG= LOG_PROFILE_TIMES_FILE= -Onone \ -j 4 -f make/Main.gmk \ bootcycle-images > >(/usr/bin/tee -a /build/openjdk-10-10~32/build/build.log) 2> >(/usr/bin/tee -a /build/openjdk-10-10~32/build/build.log >&2) && wait || \ ( exitcode=$? && \ /usr/bin/printf "\nERROR: Build failed for target 'bootcycle-images' in configuration '/build/openjdk-10-10~32/build' (exit code $exitcode) \n" \ > >(/usr/bin/tee -a /build/openjdk-10-10~32/build/build.log) 2> >(/usr/bin/tee -a /build/openjdk-10-10~32/build/build.log >&2) && wait && \ cd /build/openjdk-10-10~32 && /usr/bin/make -r -R -I /build/openjdk-10-10~32/make/common SPEC=/build/openjdk-10-10~32/build/spec.gmk MAKE_LOG_FLAGS="" LOG_LEVEL=debug LOG_NOFILE= LOG_CMDLINES= LOG_PROFILE_TIMES_LOG= LOG_PROFILE_TIMES_FILE= -j 1 -f make/Init.gmk \ HAS_SPEC=true on-failure ; \ exit $exitcode ) ) 1234 22671 0.0 0.0 9660 2428 pts/40 SN+ 19:16 0:00 /bin/bash -o pipefail -e -c ( cd /build/openjdk-10-10~32 && \ /usr/bin/nice /usr/bin/make -r -R -I /build/openjdk-10-10~32/make/common SPEC=/build/openjdk-10-10~32/build/bootcycle-spec.gmk MAKE_LOG_FLAGS="" LOG_LEVEL=debug LOG_NOFILE= LOG_CMDLINES= LOG_PROFILE_TIMES_LOG= LOG_PROFILE_TIMES_FILE= -Onone \ -j -f make/Main.gmk \ product-images > >(/usr/bin/tee -a /build/openjdk-10-10~32/build/bootcycle-build/build.log) 2> >(/usr/bin/tee -a /build/openjdk-10-10~32/build/bootcycle-build/build.log >&2) && wait || \ ( exitcode=$? && \ /usr/bin/printf "\nERROR: Build failed for target 'product-images' in configuration '/build/openjdk-10-10~32/build' (exit code $exitcode) \n" \ > >(/usr/bin/tee -a /build/openjdk-10-10~32/build/bootcycle-build/build.log) 2> >(/usr/bin/tee -a /build/openjdk-10-10~32/build/bootcycle-build/build.log >&2) && wait && \ cd /build/openjdk-10-10~32 && /usr/bin/make -r -R -I /build/openjdk-10-10~32/make/common SPEC=/build/openjdk-10-10~32/build/bootcycle-spec.gmk MAKE_LOG_FLAGS="" LOG_LEVEL=debug LOG_NOFILE= LOG_CMDLINES= LOG_PROFILE_TIMES_LOG= LOG_PROFILE_TIMES_FILE= -j 1 -f make/Init.gmk \ HAS_SPEC=true on-failure ; \ exit $exitcode ) ) 1234 22672 0.0 0.0 9668 2040 pts/40 SN+ 19:16 0:00 /bin/bash -o pipefail -e -c ( cd /build/openjdk-10-10~32 && \ /usr/bin/nice /usr/bin/make -r -R -I /build/openjdk-10-10~32/make/common SPEC=/build/openjdk-10-10~32/build/bootcycle-spec.gmk MAKE_LOG_
Processed: tagging 889688
Processing commands for cont...@bugs.debian.org:
> tags 889688 + buster sid
Bug #889688 {Done: Stephen Kitt } [gweled] gweled crashes
when rsvg reports an error
Added tag(s) sid and buster.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
889688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#880554: xen domu freezes with kernel linux-image-4.9.0-4-amd64
On 02/26/2018 03:52 PM, Ian Jackson wrote:
> Christian Schwamborn writes ("Re: Bug#880554: xen domu freezes with kernel
> linux-image-4.9.0-4-amd64"):
>> I can try, but the only system I can really test this is a productive
>> system, as this 'reliable' shows this issue (and I don't want to crash
>> it on purpose on a regular basis). Since I set gnttab_max_frame to a
>> higher value it runs smooth. If you're confident this will work I can
>> try this in the eventing, when all users logged off.
>
> Thanks. I understand your reluctance. I don't want to mislead you.
> I think the odds of it working are probably ~75%.
>
> Unless you want to tolerate that risk, it might be better for us to
> try to come up with a better way to test it.
I can try this.
I can run a dom0 with Xen 4.8 and 4.9 domU, I already have the xen-diag
for it (so confirmed the patch in this bug report builds ok, we should
include it for stretch, it's really useful).
I think it's mainly trying to get a domU running with various
combinations of domU kernel, number of disks and vcpus, and then look at
the output of xen-diag.
Hans
Bug#891570: SSL connect attempt failed error:141A90B5:SSL routines:ssl_cipher_list_to_bytes:no ciphers available
Package: libssl1.1 Version: 1.1.1~~pre1-1 Severity: grave SSL connect attempt failed error:141A90B5:SSL routines:ssl_cipher_list_to_bytes:no ciphers available
Bug#887525: poppler FTBFS with gtk-doc-tools 1.27-1
Source: poppler Followup-For: Bug #887525 This appears to be fixed upstream: https://cgit.freedesktop.org/poppler/poppler/commit/gtkdoc.py?id=791e024656212c65d798cb69a134cdd3e30cc79e -- System Information: Debian Release: buster/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: ia64 Kernel: Linux 3.14-0.bpo.2-mckinley (SMP w/2 CPU cores) 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: sysvinit (via /sbin/init)
Processed: found 870843 in 1.0.2-1
Processing commands for cont...@bugs.debian.org:
> found 870843 1.0.2-1
Bug #870843 {Done: Martín Ferrari }
[golang-github-sirupsen-logrus-dev] golang-github-armon-go-metrics-dev:
unhandled symlink to directory conversion:
/usr/share/gocode/src/github.com/sirupsen/logrus -> ../Sirupsen/logrus
Marked as found in versions golang-logrus/1.0.2-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
870843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870843
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#864620: marked as done (camo: missing dependency on openssl)
Your message dated Mon, 26 Feb 2018 18:04:47 + with message-id and subject line Bug#864620: fixed in camo 2.3.0+dfsg-1.1 has caused the Debian Bug report #864620, regarding camo: missing dependency on openssl 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.) -- 864620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864620 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: camo Version: 2.3.0+dfsg-1 This happened when installing camo: Setting up camo (2.3.0+dfsg-1) ... /var/lib/dpkg/info/camo.postinst: 1: /var/lib/dpkg/info/camo.postinst: openssl: not found The installation didn't fail, but I ended up with this: $ grep KEY /etc/default/camo CAMO_KEY= -- Jakub Wilk --- End Message --- --- Begin Message --- Source: camo Source-Version: 2.3.0+dfsg-1.1 We believe that the bug you reported is fixed in the latest version of camo, 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 864...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated camo package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 24 Feb 2018 19:23:54 +0200 Source: camo Binary: camo Architecture: source Version: 2.3.0+dfsg-1.1 Distribution: unstable Urgency: high Maintainer: Zulip Debian Packaging Team Changed-By: Adrian Bunk Description: camo - SSL/TLS image proxy to prevent mixed-content warnings Closes: 864620 Changes: camo (2.3.0+dfsg-1.1) unstable; urgency=high . * Non-maintainer upload. * Add the missing dependency on openssl. (Closes: #864620) Checksums-Sha1: 0e0e8cb6964b9453bc4809a29962906fa8785660 1974 camo_2.3.0+dfsg-1.1.dsc 4758697292299c75ef2041ac96cc84e0b11b9cce 5080 camo_2.3.0+dfsg-1.1.debian.tar.xz Checksums-Sha256: f2fd396488913efdebbb753e6cb940e1244fe27f72c4c06a906be143ea2dcaf2 1974 camo_2.3.0+dfsg-1.1.dsc d37c1dc5ff64485a28fbbc37c3b6d9b3999d76e1728c677c6505b8a3625edfc4 5080 camo_2.3.0+dfsg-1.1.debian.tar.xz Files: 184dc240c00cc8712a75001d862b870c 1974 web extra camo_2.3.0+dfsg-1.1.dsc 2e003b682525c031a1ab48b6febfbf8a 5080 web extra camo_2.3.0+dfsg-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlqRooIACgkQiNJCh6LY mLEhDBAAqUYm1CbqOpErE1RZ+KIDZJElIS+qgLkQuIYwFkl4Fb0+yk+FPfEJ/Vn7 IIatYUeufj3kLjznexxZOna3s0HIkcJjg53RdvRIWqug4q/M6SIm2UOGuPOuYXTP ZPjrCqdcyfjHdzjvu+oqozLeSIeSizmK9ETJ64WpR3sNhr2Gpq9OwRK2nbZfRtpo sWy8H8dJEBAqq9BCrqG7tThjCHXvG+Cyd95F+7GpagzOVpHqDm+ZBEj75QVsG75l gW3PR3VNCFB6iwHzm9qdcyaCE7D6oujuPi/J9o9TLq9hMUnG5DhK5EbPuEvApMOL MdAQky6ycJ9vLLuMLg5lKrhfvwIbhWios+hVQRA4aRcrucPCc74DEbbFB4fmtp4o DuieZZaSJdgMkrnchuOLyNrawyPeRWTrDPNc6R9OicirOio+km1hre554mIdLH9H oy0rigaJ7qK9+dcwZZJcz8eFOK2qRlc3dEkqEBLGMe/5kTczrRqN3NddfZsqzoA6 TfUKNVPak2UvYydaSCnaCUjF1vS396EvaH11Mefgb0VXI1ZOrGAbR9JT+3lr3kGr xxUq+e9oBxJ0c2fxJ+HoUevR2qwES49YrioyJ1Xw0SdD7FZqp1WBA0hswfzms7MD dQABT0lgpBIiHHzqtk2qF2zLHmTF9rzkz+WPemfrkWiA4jIbHyk= =Wjef -END PGP SIGNATURE End Message ---
Processed: tagging 868473
Processing commands for cont...@bugs.debian.org:
> tags 868473 + buster sid
Bug #868473 {Done: Gianfranco Costamagna } [dh-acc]
dh-acc: Incorrect usage of doit (Dh_Lib)
Added tag(s) buster and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
868473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868473
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#870359: stretch update for clustershell
On Tue, Aug 22, 2017 at 03:09:09PM +, Debian Bug Tracking System wrote: >... > clustershell (1.7.3-2) unstable; urgency=medium > . >* Add dependency python-pkg-resources (closes: Bug#870359) >... Thanks a lot for fixing this bug for unstable. It is still present in stretch, could you also fix it there? Alternatively, I can fix it for stretch if you don't object. Thanks Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Processed: Re: Bug#884436: xdg-open: wrongly handled file/URL in LXQt
Processing control commands: > severity -1 grave Bug #884436 [xdg-utils] xdg-open: wrongly handled file/URL in LXQt Bug #887027 [xdg-utils] xdg-open: "Open destination folder" doesn't work with PCManFM Severity set to 'grave' from 'normal' Severity set to 'grave' from 'normal' -- 884436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884436 887027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887027 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#890589: stretch-pu update for chaosreader
On Fri, Feb 16, 2018 at 01:21:03PM +, Debian Bug Tracking System wrote: >... > chaosreader (0.96-3) unstable; urgency=medium >... >- Added libnet-dns-perl to Depends field. (Closes: #890589) >... Thanks a lot for fixing this bug for unstable. It is still present in stretch, could you also fix it there? Alternatively, I can fix it for stretch if you don't object. Thanks Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#878322: stretch-pu update for ax25-tools
On Tue, Oct 31, 2017 at 12:21:07AM +, Debian Bug Tracking System wrote: >... > ax25-tools (0.0.10-rc4-2) unstable; urgency=medium > . >* Add patch 02-ptsname-prototype.patch to fix segfault at runtime > - Closes: #878322 >... Thanks a lot for fixing this bug for unstable. It is still present in stretch, could you also fix it there? Alternatively, I can fix it for stretch if you don't object. Thanks Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Processed: [bts-link] source package glade
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package glade > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). > # remote status report for #890774 (http://bugs.debian.org/890774) > # Bug title: glade 3.20.2-1 has same filename for all images > # * http://bugzilla.gnome.org/show_bug.cgi?id=772485 > # * remote status changed: NEW -> RESOLVED > # * remote resolution changed: (?) -> FIXED > # * closed upstream > forwarded 890774 https://bugzilla.gnome.org/show_bug.cgi?id=793576, > merged-upstream: http://bugzilla.gnome.org/show_bug.cgi?id=772485 Bug #890774 [glade] glade 3.20.2-1 has same filename for all images Changed Bug forwarded-to-address to 'https://bugzilla.gnome.org/show_bug.cgi?id=793576, merged-upstream: http://bugzilla.gnome.org/show_bug.cgi?id=772485' from 'https://bugzilla.gnome.org/show_bug.cgi?id=793576'. > tags 890774 + fixed-upstream Bug #890774 [glade] glade 3.20.2-1 has same filename for all images Added tag(s) fixed-upstream. > usertags 890774 - status-NEW Usertags were: status-NEW. Usertags are now: . > usertags 890774 + status-RESOLVED resolution-FIXED There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. > thanks Stopping processing here. Please contact me if you need assistance. -- 890774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890774 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#891371: marked as done (goobook: Missing dependency: python-setuptools)
Your message dated Mon, 26 Feb 2018 17:19:32 +
with message-id
and subject line Bug#891371: fixed in goobook 1.9-3
has caused the Debian Bug report #891371,
regarding goobook: Missing dependency: python-setuptools
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.)
--
891371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891371
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: goobook
Version: 1.9-2
Severity: serious
Justification: Policy 7.2
Dear Maintainer,
the package is missing an dependency: python-setuptools
Without it just crashes when running:
Traceback (most recent call last):
File "/usr/bin/goobook", line 6, in
from pkg_resources import load_entry_point
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3147,
in
@_call_aside
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3131,
in _call_aside
f(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3160,
in _initialize_master_working_set
working_set = WorkingSet._build_master()
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 666,
in _build_master
ws.require(__requires__)
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 984,
in require
needed = self.resolve(parse_requirements(requirements))
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 870,
in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'setuptools>=0.7' distribution was not
found and is required by goobook
After installing it everything is fine.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (1001, 'testing'), (500, 'stable-updates'), (500, 'stable'),
(500, 'oldstable'), (300, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages goobook depends on:
ii python2.7.14-4
ii python-gdata 2.0.18+dfsg1-2
ii python-httplib2 0.9.2+dfsg-1
ii python-oauth2client 4.1.2-2
ii python-pkg-resources 38.4.0-1
ii python-simplejson 3.13.2-1
goobook recommends no packages.
Versions of packages goobook suggests:
pn python-keyring
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: goobook
Source-Version: 1.9-3
We believe that the bug you reported is fixed in the latest version of
goobook, 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 891...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ilias Tsitsimpis (supplier of updated goobook 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, 26 Feb 2018 18:54:52 +0200
Source: goobook
Binary: goobook
Architecture: source
Version: 1.9-3
Distribution: unstable
Urgency: medium
Maintainer: Ilias Tsitsimpis
Changed-By: Ilias Tsitsimpis
Description:
goobook- command-line interface to Google contacts
Closes: 891371
Changes:
goobook (1.9-3) unstable; urgency=medium
.
* Add missing dependency on python-setuptools (Closes: #891371)
* Modify d/watch and d/copyright to use HTTPS
* Bump Standards-Version to 4.1.3, no changes needed
* Use salsa.debian.org URLs in Vcs-{Browser,Git} fields
* Update d/copyright file (bump Copyright years)
Checksums-Sha1:
c2adc2d63a6cb65d531689e18a094b9d0fb676fd 1861 goobook_1.9-3.dsc
855becce7340d1ad67fdbce2685a62f6ff904faa 4132 goobook_1.9-3.debian.tar.xz
facfd7ed3aaeeb7499f7be322f6aa62e417ec6f2 6232 goobook_1.9-3_amd64.buildinfo
Checksums-Sha256:
0bf3abc5f65311561f6f24a71a55d61887adfc1c7fbce723242bfc2cf24688bf 1861
goobook_1.9-3.dsc
1c910ec2cc7941224874dcceb9a09ebcaae3b955b562ee1cb1becf1360e5 4132
goobook_1.9-3.debian.tar.xz
938b35499f1609bf212295153785abc373c5f9ab0a7ad991b4f8b81fd60e585f 6232
goobook_1.9-3_amd64.buildinfo
Files:
85d78e89184512019ef52abb7b0c01db 1861 mail op
Bug#891557: gocryptfs FTBFS: src/github.com/jacobsa/crypto/cmac/hash.go:97:3: undefined: xorBlock
Source: gocryptfs Version: 1.4.3-5 Severity: serious https://buildd.debian.org/status/package.php?p=gocryptfs&suite=sid ... github.com/rfjakob/gocryptfs/internal/stupidgcm # github.com/jacobsa/crypto/cmac src/github.com/jacobsa/crypto/cmac/hash.go:97:3: undefined: xorBlock golang.org/x/crypto/hkdf golang.org/x/crypto/ssh/terminal github.com/rfjakob/gocryptfs/internal/exitcodes golang.org/x/crypto/pbkdf2 golang.org/x/crypto/scrypt github.com/rfjakob/gocryptfs/internal/tlog github.com/rfjakob/gocryptfs/internal/nametransform/dirivcache github.com/rfjakob/gocryptfs/internal/openfiletable github.com/rfjakob/gocryptfs/internal/ctlsock github.com/rfjakob/gocryptfs/internal/serialize_reads golang.org/x/sync/syncmap github.com/rfjakob/gocryptfs/internal/readpassword github.com/hanwen/go-fuse/fuse github.com/rfjakob/gocryptfs/internal/syscallcompat github.com/hanwen/go-fuse/fuse/nodefs github.com/hanwen/go-fuse/fuse/pathfs github.com/rfjakob/gocryptfs/internal/prefer_openssl dh_auto_build: cd obj-x86_64-linux-gnu && go install -gcflags=\"-trimpath=/<>/obj-x86_64-linux-gnu/src\" -asmflags=\"-trimpath=/<>/obj-x86_64-linux-gnu/src\" -v -p 4 -ldflags "-X main.GitVersion=1.4.3 -X main.GitVersionFuse=0.0~git20171124.0.14c3015 -X main.BuildDate=2018-02-24" github.com/rfjakob/gocryptfs github.com/rfjakob/gocryptfs/gocryptfs-xray github.com/rfjakob/gocryptfs/internal/configfile github.com/rfjakob/gocryptfs/internal/contentenc github.com/rfjakob/gocryptfs/internal/cryptocore github.com/rfjakob/gocryptfs/internal/ctlsock github.com/rfjakob/gocryptfs/internal/exitcodes github.com/rfjakob/gocryptfs/internal/fusefrontend github.com/rfjakob/gocryptfs/internal/fusefrontend_reverse github.com/rfjakob/gocryptfs/internal/nametransform github.com/rfjakob/gocryptfs/internal/nametransform/dirivcache github.com/rfjakob/gocryptfs/internal/openfiletable github.com/rfjakob/gocryptfs/internal/pathiv github.com/rfjakob/gocryptfs/internal/prefer_openssl git hub.com/rfjakob/gocryptfs/internal/readpassword github.com/rfjakob/gocryptfs/internal/serialize_reads github.com/rfjakob/gocryptfs/internal/siv_aead github.com/rfjakob/gocryptfs/internal/speed github.com/rfjakob/gocryptfs/internal/stupidgcm github.com/rfjakob/gocryptfs/internal/syscallcompat github.com/rfjakob/gocryptfs/internal/tlog returned exit code 2 make[1]: *** [debian/rules:28: override_dh_auto_build] Error 2
Bug#891533: marked as done (chemeq FTBFS with flex 2.6.4-6)
Your message dated Mon, 26 Feb 2018 16:34:45 +
with message-id
and subject line Bug#891533: fixed in chemeq 2.12-3
has caused the Debian Bug report #891533,
regarding chemeq FTBFS with flex 2.6.4-6
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.)
--
891533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891533
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: chemeq
Version: 2.12-2
Severity: serious
Tags: patch buster sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/chemeq.html
...
g++ -g -O1 -o chemeq chemeq.o chemparser.o mendeleiev.o -lfl
/usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/libfl.so: undefined
reference to `yylex'
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:6: chemeq] Error 1
Fix attached.
Description: With shared libfl unnecessary -lfl causes FTBFS
Due to libfl requiring yylex.
Author: Adrian Bunk
--- chemeq-2.12.orig/src/Makefile
+++ chemeq-2.12/src/Makefile
@@ -3,7 +3,7 @@ CXX = g++
CXXFLAGS= -g -O1
chemeq : chemeq.o chemparser.o mendeleiev.o
- ${CXX} $(CXXFLAGS) -o chemeq chemeq.o chemparser.o mendeleiev.o -lfl
+ ${CXX} $(CXXFLAGS) -o chemeq chemeq.o chemparser.o mendeleiev.o
chemeq.h: chemeq.h.in
--- End Message ---
--- Begin Message ---
Source: chemeq
Source-Version: 2.12-3
We believe that the bug you reported is fixed in the latest version of
chemeq, 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 891...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Georges Khaznadar (supplier of updated chemeq 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, 26 Feb 2018 16:49:29 +0100
Source: chemeq
Binary: chemeq
Architecture: source amd64
Version: 2.12-3
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar
Changed-By: Georges Khaznadar
Description:
chemeq - Parser for chemical formula and equilibria
Closes: 891533
Changes:
chemeq (2.12-3) unstable; urgency=medium
.
* applied Adrian Bunk's patch. Closes: #891533
* upgraded Standards-Version to 4.1.3, and dh level to 10
* added Vcs repositories
Checksums-Sha1:
61cb28effd6b0f6ecc218749ebfdfdbe140b252d 1798 chemeq_2.12-3.dsc
72b20e5743ed0ce52edd3360cada0a4ac496c5a9 7468 chemeq_2.12-3.debian.tar.xz
6a1272566e2f1d61c7339071f73e1e556c739295 178892 chemeq-dbgsym_2.12-3_amd64.deb
606e4a6e03e219a0014fe507ceb8483fb3f067d6 5673 chemeq_2.12-3_amd64.buildinfo
ce3f64d0e5b5511ae76faa4580c67205138ade68 47076 chemeq_2.12-3_amd64.deb
Checksums-Sha256:
556d67fe4c27c2052d98ceb0f275de81d041b329c964dcbe9215fc742acca33a 1798
chemeq_2.12-3.dsc
4617cf1b24dc8e2d4614354f907baad182a65b7105af7b8a10cc16c941f944c4 7468
chemeq_2.12-3.debian.tar.xz
43eb007769102d8be856e2156f675fbbb82cdede649825965b0378eaa6f37fa3 178892
chemeq-dbgsym_2.12-3_amd64.deb
4cf39a513ff18f97f05d9861be095baa1af0c558375a7d2b2b768e574db7ce88 5673
chemeq_2.12-3_amd64.buildinfo
67a56e3d35d70aee6780200fb161e5cc9085a51d160b47d345b8abbd43dad06c 47076
chemeq_2.12-3_amd64.deb
Files:
f55e33bc4999eb34bff58f927a432f2a 1798 tex optional chemeq_2.12-3.dsc
effa5499507087490eef97dcd90bafca 7468 tex optional chemeq_2.12-3.debian.tar.xz
09797fc22c9215debbe577677b0bd2e4 178892 debug optional
chemeq-dbgsym_2.12-3_amd64.deb
62417d404a6bc6b39709510fca14475f 5673 tex optional
chemeq_2.12-3_amd64.buildinfo
fddba8e74e47fe88e470636ad91fd1db 47076 tex optional chemeq_2.12-3_amd64.deb
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAlqUMZ4ACgkQHCgWkHE2
rjltpA/+Mxy6XLIZw9ul+caCLVU0zkPtxFxQG5rRvrYDIDBkdLenUb/vDn45+jQo
LfmgYoMgKHvAIuaPvxvyVzvuIFvUvdVO/V8m2PXo7gywIY3OnZFcOGVXzJ0HlWgC
aeJwrBxCawAzYcbjeF1MtBeAgXuVEZeKo+1AIjbfWoDdw9KpoQIJPjgMWy8Ys8Yt
QUOmWg3wTU4Qq27c4UlfCMoLaHPj1Rk/NMCM8U5+9+1fTaHp9Gyn4uAudSuFjHSJ
i7nMaG7BQa0OkDUoZUi0L9x1E/yRyOUCFNazKXv9pzzzLTBUYLVS4c81KoLAy8Eb
paYD0A3Z2l+ryq+nsydRWNrKbR8SdxJqB0+VuQGjThNnrtMSSV34vtommQBiSjis
SgGOxZcqqa0jGHwVi7Ve4SFi80+WPHjoJzNnsvEZyoBseFxK0r3KMBtmOTFLlIxY
vNRB61JvWFDPOSD+ZC4dqmOHCMvC87Pcsvk6K43uuvbuhF/G2qKmramTLfgCvxvT
73Tx9o4OE7fSChlSnJGK3X6eOv9jRC1N2Pj7v533Pnt6f4YdXghimbddWBYtEVJ7
66SZV8Sn7XBAWU
Processed: android-framework-23 FTBFS with make 4.2.1-1: execvp: /bin/sh: Argument list too long
Processing control commands: > affects -1 make Bug #891548 [src:android-framework-23] android-framework-23 FTBFS with make 4.2.1-1: execvp: /bin/sh: Argument list too long Added indication that 891548 affects make -- 891548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891548 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#891548: android-framework-23 FTBFS with make 4.2.1-1: execvp: /bin/sh: Argument list too long
Source: android-framework-23 Version: 6.0.1+r72-3 Severity: serious Tags: buster sid Control: affects -1 make https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/android-framework-23.html ... debian/rules override_dh_auto_build make[1]: Entering directory '/build/1st/android-framework-23-6.0.1+r72' make -f debian/aidl.mk make[2]: Entering directory '/build/1st/android-framework-23-6.0.1+r72' make[2]: execvp: /bin/sh: Argument list too long make[2]: *** [debian/aidl.mk:392: build] Error 127 Works after downgrading make to 4.1-9.1.
Bug#891547: cairo: test runs into buildd timeout without fpu
Source: cairo Version: 1.15.10-2 Severity: serious https://buildd.debian.org/status/package.php?p=cairo&suite=sid On the fpu-less armel port the build ran into the 150 minute timeout during the tests. With an fpu-less buildd the mips build ran into the 360 minute timeout during the tests. These timeouts are time without anything output during the build. On the abel porterbox (that is the same hardware as the armel/armhf buildds) I got a successful armel build after 4h 18m. This is three times the durtion of the successful armhf build, which wouldn't be surprising if plenty of fp code is run. The ia64 failure is likely a real problem somewhere, Jason is currently debugging that. Possible solutions: 1. get some output during the tests (disable the output redirection), or 2. don't run the tests on the armel and mips architectures (mipsel and mips64el are fine)
Bug#890747: marked as done (clang-defaults: needs to provide a generic clang-tools package)
Your message dated Mon, 26 Feb 2018 15:37:46 + with message-id and subject line Bug#890747: fixed in llvm-defaults 0.41~exp3 has caused the Debian Bug report #890747, regarding clang-defaults: needs to provide a generic clang-tools 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.) -- 890747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890747 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: clang-4.0 Version: 1:4.0.1-10 Severity: serious Control: affects -1 src:httping https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/httping.html ... scan-build make make[1]: scan-build: Command not found make[1]: *** [Makefile:155: check] Error 127 The root cause is that the following symlinks are dangling due to the binaries missing in clang-4.0: /usr/bin/scan-build -> scan-build-4.0 /usr/bin/scan-view -> scan-view-4.0 --- End Message --- --- Begin Message --- Source: llvm-defaults Source-Version: 0.41~exp3 We believe that the bug you reported is fixed in the latest version of llvm-defaults, 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 890...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sylvestre Ledru (supplier of updated llvm-defaults 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, 26 Feb 2018 16:16:02 +0100 Source: llvm-defaults Binary: llvm llvm-runtime llvm-dev clang clang-tools clang-tidy clang-format libclang1 libclang-dev lldb lld Architecture: source Version: 0.41~exp3 Distribution: experimental Urgency: medium Maintainer: LLVM Packaging Team Changed-By: Sylvestre Ledru Description: clang - C, C++ and Objective-C compiler (LLVM based) clang-format - Tool to format C/C++/Obj-C code clang-tidy - clang-based C++ linter tool clang-tools - clang-based tools libclang-dev - clang library - Development package libclang1 - C, C++ and Objective-C compiler (LLVM based) lld- LLVM-based linker lldb - Next generation, high-performance debugger llvm - Low-Level Virtual Machine (LLVM) llvm-dev - Low-Level Virtual Machine (LLVM), libraries and headers llvm-runtime - Low-Level Virtual Machine (LLVM), bytecode interpreter Closes: 890747 Changes: llvm-defaults (0.41~exp3) experimental; urgency=medium . * clang-tools: Pull the right package (clang-tools-X) (Closes: #890747) * Move the VCS to git. Many thanks to James Clarke for doing the conversion Checksums-Sha1: 8a103c896a1916c9e8b7b32f5c7a9c9fbf80ccbd 2314 llvm-defaults_0.41~exp3.dsc cb711c90d955a8844edbf35fbe2a937613ed2767 9520 llvm-defaults_0.41~exp3.tar.xz 839c16baaa6fc16df09db62579ddb05d0ee2e5a7 8424 llvm-defaults_0.41~exp3_amd64.buildinfo Checksums-Sha256: 53801169a18409a27a185db4257cca7e6276b29ff0ee57fd25893f8cd6e7f19c 2314 llvm-defaults_0.41~exp3.dsc 576030d45c1055f75c430d5817a594b850a4b5c60483959d8b4241a34ecc53f7 9520 llvm-defaults_0.41~exp3.tar.xz 2c954a7df5528a120887c0c82bedce26166ace697b2dcb3a28f19b9c46607ea8 8424 llvm-defaults_0.41~exp3_amd64.buildinfo Files: 297b35bb211e2cdc7d79506c6f1945a0 2314 devel optional llvm-defaults_0.41~exp3.dsc a14da35dfeb679ee7a8229434de84a62 9520 devel optional llvm-defaults_0.41~exp3.tar.xz 57e3995a6496129993919758fcfc1f14 8424 devel optional llvm-defaults_0.41~exp3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAlqUJRAACgkQfmUo2nUv G+EsDxAAjoh3TPQHuNv1VUKNDcaUwD42EOs5rWYUCSo/b6UdwoK8aIPV2qr40kBr pZBlYgA7pUtC+V9+2a8gnH3NWEjZRYE0wQVUQ6w3mi7vb+1yTn4Yun82gEsOobUJ uSANmtCixJ9zphuBQ+ZZiiFboD3Z3eQfBTVO+QyJ7DPPDtqpu/Dj0IykqM2V3WcF GnCuSW1CwMXe6yi05lkjB4hNsIwRhtRgn0YMZX+I0Mtk+0zmGBV9iDKLcABFNOur EwHRO8RIDpGleaRwvFzYGtpvhj7HEl3F3u/9+Sf5cEVaQZtvLQALUrgRWwxYtexb yMDUpKG2Vaf91bncAbwKL58JNeoDRWpgm2cM/ixDC4Elk/qzYR/zRnJ9o3lAxUCD 7wc/QtLZPSwC4ZTv8SBqylfckeKsvMLsqmxuJmGIbvk983UJN7TpI9lzV2pTdcVh ayJG24Dd/Ek3looRaI/oBgeM6P9iehZLJHPjlNrJt2zDXgdpbBkJYQt5D2TEVhKg Sto3Lqxp2q72951VyiOF5/xC9miPFJGt4G45Z9ZtX7/J1yDnL+TSIlabkzGzdNiz 3BOl9NerlfskthNSX1q5hjgy2fQy48jpUNY11GsdT9/O6ETj+GdcOiXJiOxXQuyp vkYTH0Hx/JwAKuClXAjKAIyRFnlza5lvR9Jvc1OKId3Py21Y4X0= =CuZA -END PGP SIGN
Processed: Move to the package where the bug was
Processing commands for cont...@bugs.debian.org:
> reassign 891217 libmaven3-core-java 3.5.2-1
Bug #891217 {Done: Mattias Ellert }
[src:voms-api-java] voms-api-java FTBFS: java.lang.NoClassDefFoundError
Bug reassigned from package 'src:voms-api-java' to 'libmaven3-core-java'.
No longer marked as found in versions libmaven3-core-java/3.5.2-1.
No longer marked as fixed in versions libmaven3-core-java/3.5.2-2.
Bug #891217 {Done: Mattias Ellert }
[libmaven3-core-java] voms-api-java FTBFS: java.lang.NoClassDefFoundError
Marked as found in versions maven/3.5.2-1.
> fixed 891217 3.5.2-2
Bug #891217 {Done: Mattias Ellert }
[libmaven3-core-java] voms-api-java FTBFS: java.lang.NoClassDefFoundError
Marked as fixed in versions maven/3.5.2-2.
> affects 891217 src:voms-api-java
Bug #891217 {Done: Mattias Ellert }
[libmaven3-core-java] voms-api-java FTBFS: java.lang.NoClassDefFoundError
Added indication that 891217 affects src:voms-api-java
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
891217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891217
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#891249: linux: unstable kernel/data corruption on ppc64el
Hi again, it looks that there was missing bit in some earlier patch included in 4.9 stable kernel : https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-4.9.y&id=3146a32b39cd78722869bca6e839b3c59155e012 I tested with this single patch on top of 4.9.82-1+deb9u2 and I could do some heavy linux compilation without issue. The latest upstream 4.9.84 has that fix. F. On Mon, 26 Feb 2018 12:33:56 +0100, Frédéric Bonnard wrote: > Hi, > I got this as well, not immediatly though but adding some > parallelization to the build helped. I'll look into this as well. > > F. > > On Fri, 23 Feb 2018 19:52:35 +0100, Aurelien Jarno wrote: > > Source: linux > > Version: 4.9.82-1+deb9u2 > > Severity: critical > > Justification: causes serious data corruption > > > > DSA has installed the latest security kernel (4.9.82-1+deb9u2) on the > > Debian POWER8 machines running ppc64el. While they boot correctly, then > > programs segfault randomly (apt, sbuild, systemd, etc...). Passing > > no_rfi_flush to the command line does not change anything. Looking more > > in details, things looks scarying as some code actually get wrongly > > executed. Here are some build logs examples: > > - > > https://buildd.debian.org/status/fetch.php?pkg=python-msgpack&arch=ppc64el&ver=0.5.1-1&stamp=1519399908&raw=0 > > - > > https://buildd.debian.org/status/fetch.php?pkg=python-msgpack&arch=ppc64el&ver=0.5.1-1&stamp=1519396907&raw=0 > > - > > https://buildd.debian.org/status/fetch.php?pkg=tk8.5&arch=ppc64el&ver=8.5.19-3&stamp=1519362938&raw=0 > > > > While in the above case the packages fail to build from source, I guess > > there are also some cases of undetected corruptions. > > > > I'll try to run the 4.9.80-2 kernel at some point to narrow down the > > issue. > > > > pgpl53nDOZ6N2.pgp Description: PGP signature
Bug#891280: marked as done (python{,3}-cmor: fails to install: SyntaxError)
Your message dated Mon, 26 Feb 2018 15:07:15 +
with message-id
and subject line Bug#891280: fixed in cmor 3.3.1-2
has caused the Debian Bug report #891280,
regarding python{,3}-cmor: fails to install: SyntaxError
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.)
--
891280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891280
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-cmor,python3-cmor
Version: 3.3.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
>From the attached log (scroll to the bottom...):
Selecting previously unselected package python-cmor.
(Reading database ...
(Reading database ... 5934 files and directories currently installed.)
Preparing to unpack .../python-cmor_3.3.1-1_amd64.deb ...
Unpacking python-cmor (3.3.1-1) ...
Setting up python-cmor (3.3.1-1) ...
File "/usr/lib/python2.7/dist-packages/cmip6_cv/PrePARE/PrePARE.py", line
506
print
"="
^
SyntaxError: invalid syntax
dpkg: error processing package python-cmor (--configure):
installed python-cmor package post-installation script subprocess returned
error exit status 101
Errors were encountered while processing:
python-cmor
Selecting previously unselected package python3-cmor.
(Reading database ...
(Reading database ... 6101 files and directories currently installed.)
Preparing to unpack .../python3-cmor_3.3.1-1_amd64.deb ...
Unpacking python3-cmor (3.3.1-1) ...
Setting up python3-cmor (3.3.1-1) ...
File "/usr/lib/python3/dist-packages/cmip6_cv/PrePARE/PrePARE.py", line 506
print
"="
^
SyntaxError: Missing parentheses in call to 'print'. Did you mean
print("=")?
dpkg: error processing package python3-cmor (--configure):
installed python3-cmor package post-installation script subprocess returned
error exit status 1
Errors were encountered while processing:
python3-cmor
cheers,
Andreas
python-cmor_3.3.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: cmor
Source-Version: 3.3.1-2
We believe that the bug you reported is fixed in the latest version of
cmor, 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 891...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Alastair McKinstry (supplier of updated cmor 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, 26 Feb 2018 14:39:44 +
Source: cmor
Binary: libcmor2 libcmor-dev python-cmor python3-cmor
Architecture: source amd64
Version: 3.3.1-2
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry
Changed-By: Alastair McKinstry
Description:
libcmor-dev - Development files for Climate Model Output Rewriter
libcmor2 - Climate Model Output Rewriter library
python-cmor - Python interface to CMOR
python3-cmor - Python3 interface to CMOR
Closes: 883985 891280
Changes:
cmor (3.3.1-2) unstable; urgency=medium
.
* Fixes to PrePARE.py python3 patch. Closes: #891280
* Add build-dep on heimdal-multidev
* Add kfreebsd/hurd patch for fortran detection. Closes: #883985
Checksums-Sha1:
2579e2ef359a52ff0c1b06e9baf4273fc16cfa40 2284 cmor_3.3.1-2.dsc
6347b4d9778e1101793b4bb0191a2f5453181825 29408 cmor_3.3.1-2.debian.tar.xz
c4dfe95ac940d882700982d53d4cf7996713928a 10507 cmor_3.3.1-2_amd64.buildinfo
fd971d2e5c770936a29ea89317c9032aaf4156fd 3144556 libcmor-dev_3.3.1-2_amd64.deb
6d78199b0271b650b573640572bc6429a9583ace 187680
libcmor2-dbgsym_3.3.1-2_amd64.deb
75de0cadfc8190b4
Processed: Re: clang-defaults: needs to provide a generic clang-tools package
Processing control commands:
> reopen -1
Bug #890747 {Done: Andreas Beckmann } [clang] clang-defaults:
needs to provide a generic clang-tools package
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.41~exp2.
> block 891407 with -1
Bug #891407 [src:httping] httping: needs B-D: clang-tools
891407 was not blocked by any bugs.
891407 was not blocking any bugs.
Added blocking bug(s) of 891407: 890747
--
890747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890747
891407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891407
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#890747: clang-defaults: needs to provide a generic clang-tools package
Followup-For: Bug #890747 Control: reopen -1 Control: block 891407 with -1 The generic clang-tools package pulls in clang instead of clang-tools-5.0, making it rather useless. Also causes lots of broken manpage symlinks. Andreas
Bug#880554: xen domu freezes with kernel linux-image-4.9.0-4-amd64
Christian Schwamborn writes ("Re: Bug#880554: xen domu freezes with kernel
linux-image-4.9.0-4-amd64"):
> I can try, but the only system I can really test this is a productive
> system, as this 'reliable' shows this issue (and I don't want to crash
> it on purpose on a regular basis). Since I set gnttab_max_frame to a
> higher value it runs smooth. If you're confident this will work I can
> try this in the eventing, when all users logged off.
Thanks. I understand your reluctance. I don't want to mislead you.
I think the odds of it working are probably ~75%.
Unless you want to tolerate that risk, it might be better for us to
try to come up with a better way to test it.
Ian.
Bug#890866: mesa: regression vs mesa 17.3.3-1: crash on i915 triggered by running emacs
Hello, I can confirm it appears to fix things here too, with 17.3 I could trigger the crash just by making emacs scroll a larger-than-screen buffer or make scid resize its internal windows, now it doesn't crash anymore. Regards, -- Lucas
Processed: Re: Bug#891249: linux: unstable kernel/data corruption on ppc64el
Processing commands for cont...@bugs.debian.org: > tag 891249 + fixed-upstream Bug #891249 [src:linux] linux: unstable kernel/data corruption on ppc64el Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 891249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891249 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#891249: linux: unstable kernel/data corruption on ppc64el
tag 891249 + fixed-upstream thanks On 2018-02-26 11:01, Breno Leitao wrote: > Hi, > > On 02/23/2018 03:52 PM, Aurelien Jarno wrote: > > > DSA has installed the latest security kernel (4.9.82-1+deb9u2) on the > > Debian POWER8 machines running ppc64el. While they boot correctly, then > > programs segfault randomly (apt, sbuild, systemd, etc...). Passing > > no_rfi_flush to the command line does not change anything. Looking more > > in details, things looks scarying as some code actually get wrongly > > executed. Here are some build logs examples: > > - > > https://buildd.debian.org/status/fetch.php?pkg=python-msgpack&arch=ppc64el&ver=0.5.1-1&stamp=1519399908&raw=0 > > - > > https://buildd.debian.org/status/fetch.php?pkg=python-msgpack&arch=ppc64el&ver=0.5.1-1&stamp=1519396907&raw=0 > > - > > https://buildd.debian.org/status/fetch.php?pkg=tk8.5&arch=ppc64el&ver=8.5.19-3&stamp=1519362938&raw=0 > > > > While in the above case the packages fail to build from source, I guess > > there are also some cases of undetected corruptions. > > > > I'll try to run the 4.9.80-2 kernel at some point to narrow down the > > issue. > > I talked to the powerpc maintainer about this problem, and in fact this is a > knew > problem, since the 4.4 patches were 'backported' to 4.9 without success. > > This is already fixed and in the stable tree already: > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/log/arch/powerpc?h=linux-4.9.y > > I understand that the commit ids are: > * 3146a32b39cd78722869bca6e839b3c59155e012 > * efe8bc07c47fff196bbc0822e249a27ae0574d24 > * ec0084d082137b73460303b39f4089970a213ad7 > > But I suppose that Debian will do a full merge with the stable tree, then, I > expect > that the next release will just work. Thanks for the quick answer. I confirm that these commit are indeed in the 4.9.84 stable release, which has been released yesterday. I guess 3146a32b39cd78722869bca6e839b3c59155e012 is the one which fixes the data corruption. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Bug#891539: python-murano-pkg-check FTBFS: test failures
Source: python-murano-pkg-check
Version: 0.3.0-2
Severity: serious
Some recent change in unstable makes python-murano-pkg-check FTBFS:
https://tests.reproducible-builds.org/debian/history/python-murano-pkg-check.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-murano-pkg-check.html
...
==
FAIL:
muranopkgcheck.tests.test_code_structure_checker.CodeStructureTest.test_bad_assigment_case2
muranopkgcheck.tests.test_code_structure_checker.CodeStructureTest.test_bad_assigment_case2
--
_StringException: Traceback (most recent call last):
File "muranopkgcheck/tests/test_code_structure_checker.py", line 72, in
test_bad_assigment_case2
self.assertIn('"res" is not valid variable name', p.message)
File "/usr/lib/python2.7/unittest/case.py", line 804, in assertIn
self.fail(self._formatMessage(msg, standardMsg))
File "/usr/lib/python2.7/unittest/case.py", line 410, in fail
raise self.failureException(msg)
AssertionError: '"res" is not valid variable name' not found in '"$.deploy()"
is not valid yaql expression'
==
FAIL:
muranopkgcheck.tests.test_code_structure_checker.CodeStructureTest.test_bad_assigment_case2
muranopkgcheck.tests.test_code_structure_checker.CodeStructureTest.test_bad_assigment_case2
--
_StringException: Traceback (most recent call last):
File "muranopkgcheck/tests/test_validator_helpers.py", line 27, in tearDown
self.assertEqual(len(problems), 0)
File "/usr/lib/python2.7/unittest/case.py", line 513, in assertEqual
assertion_func(first, second, msg=msg)
File "/usr/lib/python2.7/unittest/case.py", line 506, in _baseAssertEqual
raise self.failureException(msg)
AssertionError: 2 != 0
==
FAIL:
muranopkgcheck.tests.test_code_structure_checker.CodeStructureTest.test_multiline
muranopkgcheck.tests.test_code_structure_checker.CodeStructureTest.test_multiline
--
_StringException: Traceback (most recent call last):
File "muranopkgcheck/tests/test_validator_helpers.py", line 27, in tearDown
self.assertEqual(len(problems), 0)
File "/usr/lib/python2.7/unittest/case.py", line 513, in assertEqual
assertion_func(first, second, msg=msg)
File "/usr/lib/python2.7/unittest/case.py", line 506, in _baseAssertEqual
raise self.failureException(msg)
AssertionError: 2 != 0
==
FAIL:
muranopkgcheck.tests.test_code_structure_checker.CodeStructureTest.test_simple
muranopkgcheck.tests.test_code_structure_checker.CodeStructureTest.test_simple
--
_StringException: Traceback (most recent call last):
File "muranopkgcheck/tests/test_validator_helpers.py", line 27, in tearDown
self.assertEqual(len(problems), 0)
File "/usr/lib/python2.7/unittest/case.py", line 513, in assertEqual
assertion_func(first, second, msg=msg)
File "/usr/lib/python2.7/unittest/case.py", line 506, in _baseAssertEqual
raise self.failureException(msg)
AssertionError: 1 != 0
==
FAIL:
muranopkgcheck.tests.test_code_structure_checker.CodeStructureTest.test_not_empty
muranopkgcheck.tests.test_code_structure_checker.CodeStructureTest.test_not_empty
--
_StringException: Traceback (most recent call last):
File "muranopkgcheck/tests/test_code_structure_checker.py", line 173, in
test_not_empty
next(self.g).message)
File "/usr/lib/python2.7/unittest/case.py", line 804, in assertIn
self.fail(self._formatMessage(msg, standardMsg))
File "/usr/lib/python2.7/unittest/case.py", line 410, in fail
raise self.failureException(msg)
AssertionError: 'Statement should be empty, not a "a"' not found in
'"$.deploy()" is not valid yaql expression'
==
FAIL:
muranopkgcheck.tests.test_code_structure_checker.CodeStructureTest.test_not_empty
muranopkgcheck.tests.test_code_structure_checker.CodeStructureTest.test_not_empty
--
_StringException: Traceback (most recent call last):
File "muranopkgcheck/tests/test_validator_helpers.py", line 27, in tearDown
self.assertEqual(len(problems), 0)
File "/usr/lib/python2.7/unittest/case.py", line 513, in assertEqual
assertion_func(first, second, msg=msg)
File "/usr/lib/python2.7/unittest/case.py", line 506, in _baseAssertEqual
raise self.failureException(msg)
AssertionError: 2 != 0
=
Processed: affects 891359
Processing commands for cont...@bugs.debian.org:
> affects 891359 src:pk4 src:rawdns
Bug #891359 {Done: Michael Stapelberg } [dh-golang] pk4
FTBFS with golang-1.10-go
Bug #891358 {Done: Michael Stapelberg } [dh-golang]
rawdns FTBFS with golang-1.10-go
Added indication that 891359 affects src:pk4 and src:rawdns
Added indication that 891358 affects src:pk4 and src:rawdns
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
891358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891358
891359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891359
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#891249: linux: unstable kernel/data corruption on ppc64el
Hi, On 02/23/2018 03:52 PM, Aurelien Jarno wrote: > DSA has installed the latest security kernel (4.9.82-1+deb9u2) on the > Debian POWER8 machines running ppc64el. While they boot correctly, then > programs segfault randomly (apt, sbuild, systemd, etc...). Passing > no_rfi_flush to the command line does not change anything. Looking more > in details, things looks scarying as some code actually get wrongly > executed. Here are some build logs examples: > - > https://buildd.debian.org/status/fetch.php?pkg=python-msgpack&arch=ppc64el&ver=0.5.1-1&stamp=1519399908&raw=0 > - > https://buildd.debian.org/status/fetch.php?pkg=python-msgpack&arch=ppc64el&ver=0.5.1-1&stamp=1519396907&raw=0 > - > https://buildd.debian.org/status/fetch.php?pkg=tk8.5&arch=ppc64el&ver=8.5.19-3&stamp=1519362938&raw=0 > > While in the above case the packages fail to build from source, I guess > there are also some cases of undetected corruptions. > > I'll try to run the 4.9.80-2 kernel at some point to narrow down the > issue. I talked to the powerpc maintainer about this problem, and in fact this is a knew problem, since the 4.4 patches were 'backported' to 4.9 without success. This is already fixed and in the stable tree already: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/log/arch/powerpc?h=linux-4.9.y I understand that the commit ids are: * 3146a32b39cd78722869bca6e839b3c59155e012 * efe8bc07c47fff196bbc0822e249a27ae0574d24 * ec0084d082137b73460303b39f4089970a213ad7 But I suppose that Debian will do a full merge with the stable tree, then, I expect that the next release will just work.
Processed: Merge duplicates and more to the package where it was fixed
Processing commands for cont...@bugs.debian.org:
> reassign 891359 dh-golang
Bug #891359 {Done: Michael Stapelberg } [src:pk4] pk4
FTBFS with golang-1.10-go
Bug reassigned from package 'src:pk4' to 'dh-golang'.
No longer marked as found in versions pk4/5.
No longer marked as fixed in versions dh-golang/1.34.
> reassign 891358 dh-golang
Bug #891358 [src:rawdns] rawdns FTBFS with golang-1.10-go
Bug reassigned from package 'src:rawdns' to 'dh-golang'.
No longer marked as found in versions rawdns/1.6~ds1-1.
Ignoring request to alter fixed versions of bug #891358 to the same values
previously set
> forcemerge 891359 891358
Bug #891359 {Done: Michael Stapelberg } [dh-golang] pk4
FTBFS with golang-1.10-go
Bug #891358 [dh-golang] rawdns FTBFS with golang-1.10-go
Marked Bug as done
Bug #891359 {Done: Michael Stapelberg } [dh-golang] pk4
FTBFS with golang-1.10-go
Added tag(s) sid and buster.
Merged 891358 891359
> tags 891359 buster sid
Bug #891359 {Done: Michael Stapelberg } [dh-golang] pk4
FTBFS with golang-1.10-go
Bug #891358 {Done: Michael Stapelberg } [dh-golang]
rawdns FTBFS with golang-1.10-go
Ignoring request to alter tags of bug #891359 to the same tags previously set
Ignoring request to alter tags of bug #891358 to the same tags previously set
> fixed 891359 1.34
Bug #891359 {Done: Michael Stapelberg } [dh-golang] pk4
FTBFS with golang-1.10-go
Bug #891358 {Done: Michael Stapelberg } [dh-golang]
rawdns FTBFS with golang-1.10-go
Marked as fixed in versions dh-golang/1.34.
Marked as fixed in versions dh-golang/1.34.
> affects 891359 pk4 rawdns
Bug #891359 {Done: Michael Stapelberg } [dh-golang] pk4
FTBFS with golang-1.10-go
Bug #891358 {Done: Michael Stapelberg } [dh-golang]
rawdns FTBFS with golang-1.10-go
Added indication that 891359 affects pk4 and rawdns
Added indication that 891358 affects pk4 and rawdns
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
891358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891358
891359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891359
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#891356: marked as done (golang-google-cloud FTBFS: FAIL google.golang.org/cloud/spanner)
Your message dated Mon, 26 Feb 2018 13:49:59 + with message-id and subject line Bug#891356: fixed in golang-google-cloud 0.9.0-5 has caused the Debian Bug report #891356, regarding golang-google-cloud FTBFS: FAIL google.golang.org/cloud/spanner 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.) -- 891356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-google-cloud Version: 0.9.0-4 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=golang-google-cloud&arch=all&ver=0.9.0-4&stamp=1519472771&raw=0 ... === RUN TestRsdNonblockingStates FATAL: 2018/02/24 11:45:48 grpc: Server.RegisterService after Server.Serve for "google.spanner.v1.Spanner" FAILgoogle.golang.org/cloud/spanner 0.039s --- End Message --- --- Begin Message --- Source: golang-google-cloud Source-Version: 0.9.0-5 We believe that the bug you reported is fixed in the latest version of golang-google-cloud, 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 891...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martín Ferrari (supplier of updated golang-google-cloud 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, 26 Feb 2018 13:30:54 + Source: golang-google-cloud Binary: golang-google-cloud-dev golang-google-cloud-compute-metadata-dev Architecture: source Version: 0.9.0-5 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Martín Ferrari Description: golang-google-cloud-compute-metadata-dev - Google Cloud Platform APIs (only cloud/compute/metadata) golang-google-cloud-dev - Google Cloud Platform APIs Closes: 891356 Changes: golang-google-cloud (0.9.0-5) unstable; urgency=medium . * debian/patches: Fix typo. * Fix racy spanner test. Closes: #891356 Checksums-Sha1: 6fe1216fc79855fcc09eed537525b33d7e538b7b 2709 golang-google-cloud_0.9.0-5.dsc 3f9007091021a3c6436ae2c661cab50ee47d4d09 7104 golang-google-cloud_0.9.0-5.debian.tar.xz 0b0f31f4339037ef26a0c81a64a110d17974e6a6 7025 golang-google-cloud_0.9.0-5_amd64.buildinfo Checksums-Sha256: 959ac87853f3f42c24b15046f3e5dc6d72286a69f4f6ea8733606a21f140ee5f 2709 golang-google-cloud_0.9.0-5.dsc de5155c8aacf65b6d19f08b3023a9fb83159422c54c7867e4724c2995923c230 7104 golang-google-cloud_0.9.0-5.debian.tar.xz ee3f138869c4db110204e0d0ce8fe81627c1425166a466235cf529b9ae0016d7 7025 golang-google-cloud_0.9.0-5_amd64.buildinfo Files: 117914e219fc6747002a1d988e26c8e5 2709 devel optional golang-google-cloud_0.9.0-5.dsc f3d742edc9f45a084e61b42c39a28dad 7104 devel optional golang-google-cloud_0.9.0-5.debian.tar.xz 57302eee2092a76fe5073734c0b47b1e 7025 devel optional golang-google-cloud_0.9.0-5_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEETe94h3mvRsa9AoOeXdjgv5Gj09oFAlqUDMUACgkQXdjgv5Gj 09rR0w//Z9eRRnOZT5+pFTuLBBMXJ1PyhGw11HUuwzSt4W37S1zYFAb4fNqqYISO NuJN7rNoQKxU7YnKYF3SWQbZkzJ4DIlg8g2yIuB3/fQ8t4KbEVVbATuMIxZlhdan /Pnp4dUU5TUoOgSoFnBpOEkn6/Ab6FOg4kHVKlklRngSHaWNpLimW3brbr21Y79T 9lKSRP0H1P4PKf9wkTVwLJx0sZdKenSJ1zv9AdxPQIfzkBgV5mb4Zyf6YQ4rWWL1 xTBgstJpdlZ931iOqCyx3kWYO35MyLeLgJlSxvR3udE45cic02ook4nti2A4+MNX 0NfCP0TGdN43Irr0CU71NoK5RLemG6+wA8wZTjXigtVrvDv8yNmtRT8b9rVBdaCN rXrxYRc76O3M7JaRnxaNjch37AMQoXbTipJIv9WL04b+6MBVvVLBWsO34d1rnAnr 9OTT0E0KEnXBqIgWi+WNj2R5EGaqDxMH8crN5RRcCvoHOja3tDS+CeoRXFc6ulPl F145Ra01UoGTGwAxoIBgqevhmHT4Op8hGcXWdQMDM52P4FqFKVRv7wwc+LOmZemh Ksm7q3FoU9huuBXql3BOt3mQIJgRr2rJbXSp8M36sFwdUEpvqdKw8kopD7On+4cI yLumHCXLBa+XReEvst6wJvYjlBWaRNwclmp4vA5dsVrG/piD6Aw= =ipVB -END PGP SIGNATURE End Message ---
Bug#891533: chemeq FTBFS with flex 2.6.4-6
Source: chemeq
Version: 2.12-2
Severity: serious
Tags: patch buster sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/chemeq.html
...
g++ -g -O1 -o chemeq chemeq.o chemparser.o mendeleiev.o -lfl
/usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/libfl.so: undefined
reference to `yylex'
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:6: chemeq] Error 1
Fix attached.
Description: With shared libfl unnecessary -lfl causes FTBFS
Due to libfl requiring yylex.
Author: Adrian Bunk
--- chemeq-2.12.orig/src/Makefile
+++ chemeq-2.12/src/Makefile
@@ -3,7 +3,7 @@ CXX = g++
CXXFLAGS= -g -O1
chemeq : chemeq.o chemparser.o mendeleiev.o
- ${CXX} $(CXXFLAGS) -o chemeq chemeq.o chemparser.o mendeleiev.o -lfl
+ ${CXX} $(CXXFLAGS) -o chemeq chemeq.o chemparser.o mendeleiev.o
chemeq.h: chemeq.h.in
Processed: tagging 891532
Processing commands for cont...@bugs.debian.org: > tags 891532 + patch Bug #891532 [src:captagent] captagent FTBFS with shared libfl Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 891532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891532 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#891356: [pkg-go] Bug#891356: golang-google-cloud FTBFS: FAIL google.golang.org/cloud/spanner
On 24/02/18 21:14, Adrian Bunk wrote: > Source: golang-google-cloud > Version: 0.9.0-4 > Severity: serious Another flaky test. Actually, I think it only worked by chance (because goroutines will take a while to start), but it still required a busy CPU, 19 niceness, and a while loop to reproduce.. I have a fix and it seems I can't reproduce the problem any more. -- Martín Ferrari (Tincho)
Bug#891356: Pending fixes for bugs in the golang-google-cloud package
tag 891356 + pending thanks Some bugs in the golang-google-cloud package are closed in revision ab9eb22e3ef390307c5b9fc7e79460aac06762e4 in branch 'master' by Martín Ferrari The full diff can be seen at https://anonscm.debian.org/cgit/pkg-go/packages/golang-google-cloud.git/commit/?id=ab9eb22 Commit message: Fix racy spanner test. Closes: #891356
Processed: Pending fixes for bugs in the golang-google-cloud package
Processing commands for cont...@bugs.debian.org: > tag 891356 + pending Bug #891356 [src:golang-google-cloud] golang-google-cloud FTBFS: FAIL google.golang.org/cloud/spanner Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 891356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
