Bug#884430: marked as done (test_nothing_logged.py:7: AssertionError)
Your message dated Sun, 31 Dec 2017 09:46:14 +0100
with message-id <8705a28b-b2f2-cdae-294a-a8f076d6c...@debian.org>
and subject line pytest-catchlog: works now
has caused the Debian Bug report #884430,
regarding test_nothing_logged.py:7: AssertionError
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.)
--
884430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884430
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pytest-catchlog
Version: 1.2.2+git20170915-2
Severity: serious
Justification: fails to build from source
pytest-catchlog currently FTBFS:
I: pybuild base:184: python2.7 -m pytest -v -x
= test session starts ==
platform linux2 -- Python 2.7.14+, pytest-3.2.1, py-1.4.34, pluggy-0.4.0 --
/usr/bin/python2.7
cachedir: .cache
rootdir: /<>, inifile:
plugins: catchlog-1.2.2
collecting ... collected 14 items
test_pytest_catchlog.py::test_nothing_logged FAILED
=== FAILURES ===
_ test_nothing_logged __
testdir =
def test_nothing_logged(testdir):
testdir.makepyfile('''
import sys
import logging
def test_foo():
sys.stdout.write('text going to stdout')
sys.stderr.write('text going to stderr')
assert False
''')
result = testdir.runpytest()
assert result.ret == 1
result.stdout.fnmatch_lines(['*- Captured stdout call -*',
'text going to stdout'])
result.stdout.fnmatch_lines(['*- Captured stderr call -*',
'text going to stderr'])
py.test.raises(Exception, result.stdout.fnmatch_lines,
> ['*- Captured *log call -*'])
E Failed: nomatch: '*- Captured stdout call -*'
E and: u'= test session starts
=='
E and: u'platform linux2 -- Python 2.7.14+, pytest-3.2.1, py-1.4.34,
pluggy-0.4.0'
E and: u'rootdir:
/tmp/pytest-of-aham/pytest-0/testdir/test_nothing_logged0, inifile:'
E and: u'plugins: catchlog-1.2.2'
E and: u'collected 1 item'
E and: u''
E and: u'test_nothing_logged.py F'
E and: u''
E and: u'=== FAILURES
==='
E and: u'___ test_foo
___'
E and: u''
E and: u'def test_foo():'
E and: u"sys.stdout.write('text going to stdout')"
E and: u"sys.stderr.write('text going to stderr')"
E and: u'> assert False'
E and: u'E assert False'
E and: u''
E and: u'test_nothing_logged.py:7: AssertionError'
E fnmatch: '*- Captured stdout call -*'
E with: u'- Captured stdout call
-'
E exact match: 'text going to stdout'
E nomatch: '*- Captured stderr call -*'
E and: u'= test session starts
=='
E and: u'platform linux2 -- Python 2.7.14+, pytest-3.2.1, py-1.4.34,
pluggy-0.4.0'
E and: u'rootdir:
/tmp/pytest-of-aham/pytest-0/testdir/test_nothing_logged0, inifile:'
E and: u'plugins: catchlog-1.2.2'
E and: u'collected 1 item'
E and: u''
E and: u'test_nothing_logged.py F'
E and: u''
E and: u'=== FAILURES
==='
E and: u'___ test_foo
___'
E and: u''
E and: u'def test_foo():'
E and: u"sys.stdout.write('text going to stdout')"
E and: u"sys.stderr.write('text going to stderr')"
E and: u'> assert False'
E and: u'E assert False'
E and: u''
E and: u'test_nothing_logged.py:7: AssertionError'
E and: u'- Captured stdout call
-'
E and: u'text going to stdout'
E fnmatch: '*- Captured stderr call -*'
E with: u'- Captured stderr call
-'
E exact match: 'text going to stderr'
E nomatch:
Processed: notfound 884525 in 1.5.5
Processing commands for cont...@bugs.debian.org:
> notfound 884525 1.5.5
Bug #884525 {Done: Andreas Tille } [src:mobyle] mobyle:
Mobyle javascript includes Google analytics beacon
The source 'mobyle' and version '1.5.5' do not appear to match any binary
packages
No longer marked as found in versions mobyle/1.5.5.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
884525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884525
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#885785: marked as done (automatically created packages (-dbgsym) should not be rejected by lintian)
Your message dated Sun, 31 Dec 2017 10:30:58 +0100 with message-id and subject line Re: Bug#885785: automatically created packages (-dbgsym) should not be rejected by lintian has caused the Debian Bug report #885785, regarding automatically created packages (-dbgsym) should not be rejected by lintian 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.) -- 885785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885785 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debhelper,lintian Severity: serious Tags: sid buster The last gcc-8 upload was automatically rejected with E: libgomp-plugin-nvptx1-dbgsym: usr-share-doc-symlink-to-foreign-package libgomp-plugin-nvptx1 E: gcc-8-offload-nvptx-dbgsym: usr-share-doc-symlink-to-foreign-package gcc-8-offload-nvptx These are automatically generated packages by dehelper. I don't think that there should be automatic rejections for automatically generated packages at all. --- End Message --- --- Begin Message --- On 29.12.2017 21:54, Niels Thykier wrote: > Control: tags -1 moreinfo > > Matthias Klose: >> Package: debhelper,lintian >> Severity: serious >> Tags: sid buster >> >> The last gcc-8 upload was automatically rejected with >> >> E: libgomp-plugin-nvptx1-dbgsym: usr-share-doc-symlink-to-foreign-package >> libgomp-plugin-nvptx1 >> E: gcc-8-offload-nvptx-dbgsym: usr-share-doc-symlink-to-foreign-package >> gcc-8-offload-nvptx >> >> These are automatically generated packages by dehelper. I don't think that >> there >> should be automatic rejections for automatically generated packages at all. >> > > That lintian warning suggests that libgomp-plugin-nvptx1 + > gcc-8-offload-nvptx are not listed in the debian/control file of the > source package you uploaded. If that is the case, dak will/should > reject the package anyway in a later control check as the upload then > includes binaries not related to the source package. > > I am aware that the d/control of gcc-8 in subversion does list these, > but please confirm that the control file of the uploaded package lists > these two packages. it looks like that this was the case. The package is now in NEW.--- End Message ---
Bug#885914: "RuntimeError: dictionary changed size during iteration" in s3cmd put
Package: s3cmd Version: 2.0.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, s3cmd put is failing with: ! An unexpected error has occurred. Please try reproducing the error using the latest s3cmd code from the git master branch found at: https://github.com/s3tools/s3cmd and have a look at the known issues list: https://github.com/s3tools/s3cmd/wiki/Common-known-issues-and-their-solutions If the error persists, please report the following lines (removing any private info as necessary) to: s3tools-b...@lists.sourceforge.net ! Invoked as: /usr/bin/s3cmd --ssl --config=/tmp/tmp.akNQcIMsdc --acl-private put --cache-file=«path»/.s3cmd.cache --encrypt «files...» s3://«bucket»/ Problem: rc = main() File "/usr/bin/s3cmd", line 2989, in main rc = cmd_func(args) File "/usr/bin/s3cmd", line 364, in cmd_object_put local_list, single_file_local, exclude_list, total_size_local = fetch_local_list(args, is_src = True) File "/usr/lib/python3/dist-packages/S3/FileLists.py", line 353, in fetch_local_list _maintain_cache(cache, local_list) File "/usr/lib/python3/dist-packages/S3/FileLists.py", line 311, in _maintain_cache cache.purge() File "/usr/lib/python3/dist-packages/S3/HashCache.py", line 49, in purge for i in self.inodes[d].keys(): RuntimeError: dictionary changed size during iteration /tmp/tmp.akNQcIMsdc contains: [default] access_key = «access key» acl_public = False bucket_location = EU cloudfront_host = cloudfront.amazonaws.com cloudfront_resource = /2008-06-30/distribution default_mime_type = binary/octet-stream delete_removed = False dry_run = False encoding = UTF-8 encrypt = False force = False get_continue = False gpg_command = /usr/bin/gpg gpg_decrypt = %(gpg_command)s --homedir /usr/local/backups/gpghome -d --verbose --no-use-agent --batch --yes --passphrase-fd %(passphrase_fd)s -o %(output_file)s %(input_file)s gpg_encrypt = %(gpg_command)s --homedir /usr/local/backups/gpghome --cipher-algo AES256 -c --verbose --no-use-agent --batch --yes --passphrase-fd %(passphrase_fd)s -o %(output_file)s %(input_file)s gpg_passphrase = «passphrase» guess_mime_type = True host_base = s3.amazonaws.com host_bucket = %(bucket)s.s3.amazonaws.com human_readable_sizes = False list_md5 = False preserve_attrs = True progress_meter = True proxy_host = proxy_port = 0 recursive = False recv_chunk = 4096 secret_key = «secret key» send_chunk = 4096 simpledb_host = sdb.amazonaws.com skip_existing = False use_https = True verbosity = WARNING socket_timeout=60 Downgrading to 1.6.1-1 frm Stretch without changing any other packages works ok. Thanks, Ian. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf, armel, arm64 Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages s3cmd depends on: ii python3 3.6.4~rc1-2 ii python3-dateutil 2.6.1-1 ii python3-magic 1:5.32-1 s3cmd recommends no packages. s3cmd suggests no packages. -- no debconf information
Bug#885545: marked as done (hannah-foo2zjs: Don't depend on gksu)
Your message dated Sun, 31 Dec 2017 10:33:55 + with message-id and subject line Bug#885545: fixed in hannah-foo2zjs 1:3 has caused the Debian Bug report #885545, regarding hannah-foo2zjs: Don't depend on gksu 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.) -- 885545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885545 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: hannah-foo2zjs Severity: serious Tags: sid buster User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs gksu gksu has been deprecated for years. The intent of gksu is to allow running apps with elevated privileges but the way to do that is for the app developer to use PolicyKit to request elevated privileges for the specific actions that need done instead of for the whole app to run as root. For the next major stable release of Debian (codenamed Buster), the Debian GNOME team plans to default to GNOME on Wayland where gksu does not even work. Therefore, the Debian GNOME team intends to either remove gksu or replace it with a non-functional warning message. gksu is unmaintained (last upload 2014) and is a security vulnerability. On behalf of the Debian GNOME team, Jeremy Bicha --- End Message --- --- Begin Message --- Source: hannah-foo2zjs Source-Version: 1:3 We believe that the bug you reported is fixed in the latest version of hannah-foo2zjs, 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 885...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pino Toscano (supplier of updated hannah-foo2zjs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 31 Dec 2017 11:03:05 +0100 Source: hannah-foo2zjs Binary: hannah-foo2zjs Architecture: source Version: 1:3 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Pino Toscano Description: hannah-foo2zjs - Graphical firmware downloader for the foo2zjs package Closes: 772447 874903 885545 Changes: hannah-foo2zjs (1:3) unstable; urgency=medium . * QA upload. * Switch source format to "3.0 (native)". * Do not ship the generated hannah binary, and the Makefile, and make sure to remove them on clean. * Drop the menu file, since hannah-foo2zjs already provides a .desktop file. * Use an install file to install all the files, using dh-exec to rename the files: - add a new executable hannah-foo2zjs.install file - add the dh-exec build dependency * Rewrite rule to use the dh sequencer. * Bump the debhelper compatibility to 10: - bump compat to 10 - bump the debhelper build dependency to 10~ * Switch versioned conflict to versioned break. * Cleanup hannah.pro. * Build the application with Qt 5: (Closes: #874903) - set the QT modules in the .pro file - switch the libqt4-dev build dependency to qtbase5-dev - set QT_SELECT=5 in rules, to make sure to build even when Qt 4 is installed too * Various improvements to the application itself: - reindent code - forward-declare classes, including only what needed, and where needed - do not hardcode the font, use the default one - use better QMessageBox APIs - create & lay out widgets in the right order - add a checkbox -> firmware mapping, so there is not a separate list for the latter - turn the "Mark all" from a checkbox into a button, and add also a new "Unmark all" button - switch from QStatusBar to QLabel for the status messages - disable the download button while downloading - set the "printer" icon for the application - harden the build with extra defines, and fix the code accordingly (slot -> Q_SLOTS, QStringLiteral, etc) - group checkboxes & mark/unmark buttons in a group box, with the checkboxes laid in two columns - improve the text in the about dialog - add accelerators for buttons * Fix path of getweb to /usr/sbin/getweb. (Closes: #772447) * Use pkexec to run getweb, instead of su-to-root for the whole application: (LP: #1713311) - depend on policykit-1 - drop the gksu|kdebase-bin|kde-
Bug#867561: marked as done (hplip-gui: Depending on gksu is not good)
Your message dated Sun, 31 Dec 2017 11:04:45 + with message-id and subject line Bug#867561: fixed in hplip 3.17.10+repack0-2 has caused the Debian Bug report #867561, regarding hplip-gui: Depending on gksu is not good 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.) -- 867561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867561 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: hplip-gui Version: 3.16.11+repack0-3 Severity: important #867236 says it all. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867236 Regards, Brian. --- End Message --- --- Begin Message --- Source: hplip Source-Version: 3.17.10+repack0-2 We believe that the bug you reported is fixed in the latest version of hplip, 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 867...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Didier Raboud (supplier of updated hplip package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 31 Dec 2017 10:52:50 +0100 Source: hplip Binary: hplip hplip-data printer-driver-postscript-hp hplip-gui hplip-doc hpijs-ppds printer-driver-hpijs printer-driver-hpcups libhpmud0 libhpmud-dev libsane-hpaio Architecture: source Version: 3.17.10+repack0-2 Distribution: unstable Urgency: medium Maintainer: Debian Printing Team Changed-By: Didier Raboud Description: hpijs-ppds - HP Linux Printing and Imaging - HPIJS PPD files hplip - HP Linux Printing and Imaging System (HPLIP) hplip-data - HP Linux Printing and Imaging - data files hplip-doc - HP Linux Printing and Imaging - documentation hplip-gui - HP Linux Printing and Imaging - GUI utilities (Qt-based) libhpmud-dev - HP Multi-Point Transport Driver (hpmud) development libraries libhpmud0 - HP Multi-Point Transport Driver (hpmud) run-time libraries libsane-hpaio - HP SANE backend for multi-function peripherals printer-driver-hpcups - HP Linux Printing and Imaging - CUPS Raster driver (hpcups) printer-driver-hpijs - HP Linux Printing and Imaging - printer driver (hpijs) printer-driver-postscript-hp - HP Printers PostScript Descriptions Closes: 867561 Changes: hplip (3.17.10+repack0-2) unstable; urgency=medium . [ Pino Toscano ] * Remove not-needed-anymore gksu/kdesu/kdesudo/… dependencies (Closes: #867561) . [ Didier Raboud ] * Update Homepage field * Bump S-V to 4.1.3 without changes needed Checksums-Sha1: 5114e6734deb811f07a097a5541d3f4100c15baf 3104 hplip_3.17.10+repack0-2.dsc eebde93925d7fed021224e771e17bddbd3ad883c 101804 hplip_3.17.10+repack0-2.debian.tar.xz Checksums-Sha256: 8519d653c7ade3a5a9cf1a9d16ab169b3bee30255d610e46ea47f759689055d9 3104 hplip_3.17.10+repack0-2.dsc 3efadca429e6b7aba174248a3f2f199e07c535e47b157a1fdbc01493116d04d5 101804 hplip_3.17.10+repack0-2.debian.tar.xz Files: d218bf9cb1ea4bff5d6a1935ffcd0315 3104 utils optional hplip_3.17.10+repack0-2.dsc ac5deb83ee7f1e2659befa36e12ddaa7 101804 utils optional hplip_3.17.10+repack0-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQGzBAEBCgAdFiEEe+WPIRpjNw1/GSB7i8+nHsoWNFUFAlpIwL0ACgkQi8+nHsoW NFXIIQv/ar8t9LSHhKvFT9tAWXzNnxNySV7msZ/3RPoaTSpaKTPKZTKpTOigcdVZ u219wl7QfG72LgVZdWCQk+LSkkg753xMrzapm8UM+tNLY0Xw3fpwQKwCPxVoNhfn mZOqJDNb74cp2sGj9d2B5H9cwZwVGYHwU/AGSehJ8nggoxZfu2lQbia74ss4XGDP X/aTADp6WYoTCEnEb3qCvPYd+1fm/s727N3rm/YcDvB0umgUcf2EeS9AQNQPbF/A xjgTmpZZxS+ozCjQmzwq0eiV6e23U4K00JGoax84e2hgUIbl71CCbz2224yRio2y araoNkbrMzGlzb+N/jHxsLQOxrU16AjUQTeumiXWl1luPMxxc3R3bpzsx3tk6FRK hYQxnX366sZO3x3u2VGMYIzETzrG0BzMQ8XxJxJI3y/fDytLsG/gaD6HgVXJHgo7 e35Bd3BMTUQrl89AOD462Cf9Jp3twIZYXsjxyzBo+GmZb+sa19H0iSHU4XWQ+MoC Lm0UciOH =nZLX -END PGP SIGNATURE End Message ---
Bug#884849: librsvg: test failures on 32-bit no longer FTBFS
Control: severity 884849 normal Control: severity 884850 normal Control: retitle 884849 librsvg: test failure on any-i386: masking-path-04-b.svg: 213 pixels differ (with maximum difference of 19) from reference image Control: retitle 884850 librsvg: test failure on (32-bit && !any-i386): masking-mask-01-b.svg: 661 pixels differ (with maximum difference of 2) from reference image I've marked both these tests to be skipped during the build on 32-bit architectures. If autopkgtests are added at some point, they'll still be run there. The differences between the reference image and the actual output are still bugs, but don't seem release-critical. These tests were new in 2.40.19, so they've never passed on the affected architectures in Debian - this is probably a pre-existing bug being demonstrated by new test coverage, rather than a regression. smcv
Processed: Re: librsvg: test failures on 32-bit no longer FTBFS
Processing control commands: > severity 884849 normal Bug #884849 [src:librsvg] librsvg: FTBFS on any-i386: masking-path-04-b.svg: 213 pixels differ (with maximum difference of 19) from reference image Severity set to 'normal' from 'serious' > severity 884850 normal Bug #884850 [src:librsvg] librsvg: FTBFS on (32-bit && !any-i386): masking-mask-01-b.svg: 661 pixels differ (with maximum difference of 2) from reference image Severity set to 'normal' from 'serious' > retitle 884849 librsvg: test failure on any-i386: masking-path-04-b.svg: 213 > pixels differ (with maximum difference of 19) from reference image Bug #884849 [src:librsvg] librsvg: FTBFS on any-i386: masking-path-04-b.svg: 213 pixels differ (with maximum difference of 19) from reference image Changed Bug title to 'librsvg: test failure on any-i386: masking-path-04-b.svg: 213 pixels differ (with maximum difference of 19) from reference image' from 'librsvg: FTBFS on any-i386: masking-path-04-b.svg: 213 pixels differ (with maximum difference of 19) from reference image'. > retitle 884850 librsvg: test failure on (32-bit && !any-i386): > masking-mask-01-b.svg: 661 pixels differ (with maximum difference of 2) from > reference image Bug #884850 [src:librsvg] librsvg: FTBFS on (32-bit && !any-i386): masking-mask-01-b.svg: 661 pixels differ (with maximum difference of 2) from reference image Changed Bug title to 'librsvg: test failure on (32-bit && !any-i386): masking-mask-01-b.svg: 661 pixels differ (with maximum difference of 2) from reference image' from 'librsvg: FTBFS on (32-bit && !any-i386): masking-mask-01-b.svg: 661 pixels differ (with maximum difference of 2) from reference image'. -- 884849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884849 884850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884850 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#885920: [firefox] Firefox window doesn't show under wayland
Package: firefox Version: 57.0.3-1 Severity: grave --- Please enter the report below this line. --- When launching Firefox under Gnome shell/Wayland, nothing seems to happen: no window is shown. But doing a "ps ax" shows two processes with the name "firefox". Killing the second one (the one with the bigger PID) makes the window appear and everything seems to work fine. Using Gnome shell/X11 everything works fine. Tried it removing all Gnome shell extensions, and also all Firefox extensions. Same result. --- System information. --- Architecture: Kernel: Linux 4.14.0-2-amd64 Debian Release: buster/sid 500 unstable repo.skype.com 500 unstable ftp.debian.org 500 unstable dl.winehq.org 500 stable repo.skype.com 500 stable dl.google.com 500 any packagecloud.io --- Package information. --- Depends (Version) | Installed ==-+-== libatk1.0-0 (>= 1.12.4) | libc6 (>= 2.18) | libcairo-gobject2 (>= 1.10.0) | libcairo2 (>= 1.10.0) | libdbus-1-3 (>= 1.9.14) | libdbus-glib-1-2 (>= 0.78) | libevent-2.1-6 (>= 2.1.8-stable) | libffi6 (>= 3.0.4) | libfontconfig1 (>= 2.12) | libfreetype6 (>= 2.2.1) | libgcc1 (>= 1:4.2) | libgdk-pixbuf2.0-0 (>= 2.22.0) | libglib2.0-0 (>= 2.31.8) | libgtk-3-0 (>= 3.0.0) | libgtk2.0-0 (>= 2.10) | libhunspell-1.6-0 | libjsoncpp1 (>= 1.7.4) | libnspr4 (>= 2:4.10.9) | libnss3 (>= 2:3.33) | libpango-1.0-0 (>= 1.14.0) | libsqlite3-0 (>= 3.14.0) | libstartup-notification0 (>= 0.8) | libstdc++6 (>= 6) | libvpx4 (>= 1.6.0) | libx11-6 | libx11-xcb1 | libxcb-shm0 | libxcb1 | libxcomposite1 (>= 1:0.3-1) | libxdamage1 (>= 1:1.1) | libxext6 | libxfixes3 | libxrender1 | libxt6 | zlib1g (>= 1:1.2.3.4) | fontconfig | procps | debianutils (>= 1.16) | Package's Recommends field is empty. Suggests (Version) | Installed ===-+-=== fonts-stix | OR otf-stix | fonts-lmodern | mozplugger | libgssapi-krb5-2 | OR libkrb53 | libcanberra0 | --- Output from package bug script --- -- Addons package information
Processed: block 868410 with 885911
Processing commands for cont...@bugs.debian.org: > block 868410 with 885911 Bug #868410 [src:yarssr] yarssr: Please drop the (build-)dependency against gnome-vfs 868410 was not blocked by any bugs. 868410 was blocking: 868395 868398 Added blocking bug(s) of 868410: 885911 > thanks Stopping processing here. Please contact me if you need assistance. -- 868410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868410 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#868410: yarssr: Please drop the (build-)dependency against gnome-vfs
Hi, Joachim Breitner: > yarssr is dead upstream (for a decade or so) and I’d rather drop it > than patch it. So when it is time to RM gnome-vfs, feel free to RM > yarssr as well. Thanks! I've requested the removal today: #885911.
Bug#856085: marked as done (madplay: Please drop the (build-)dependency against esound)
Your message dated Sun, 31 Dec 2017 13:19:00 +
with message-id
and subject line Bug#856085: fixed in madplay 0.15.2b-8.2
has caused the Debian Bug report #856085,
regarding madplay: Please drop the (build-)dependency against esound
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.)
--
856085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856085
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: madplay
Version: 0.15.2b-8.1
Severity: wishlist
Tags: sid buster
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: esd-removal
Dear maintainer,
Your package is {build-}depending against esound which is deprecated
for quite some times now.
We are planning to remove esound for Buster if possible.
Could you please verify that this dependency is mandatory and if it's
not the case, could you please remove it?
Don't hesitate to contact me if you have any questions.
Kind regards,
Laurent Bigonville
--- End Message ---
--- Begin Message ---
Source: madplay
Source-Version: 0.15.2b-8.2
We believe that the bug you reported is fixed in the latest version of
madplay, 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 856...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Paul Gevers (supplier of updated madplay 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, 30 Dec 2017 07:58:33 +0100
Source: madplay
Binary: madplay
Architecture: source
Version: 0.15.2b-8.2
Distribution: unstable
Urgency: medium
Maintainer: Mad Maintainers
Changed-By: Paul Gevers
Description:
madplay- MPEG audio player in fixed point
Closes: 856085 865188 868709 885724
Changes:
madplay (0.15.2b-8.2) unstable; urgency=medium
.
* Non-maintainer upload (Closes: #885724)
* Drop build-dep on libesd0-dev as it was optional anyways and is now
deprecated (Closes: #856085)
* Replace build depends on automake1.11 with automake (Closes: #865188)
Thanks to Eric Dorland for the initial patch.
* Drop Clément Stenac from uploaders list (Closes: #868709)
* Add Homepage field to d/control
Checksums-Sha1:
f25136186f452d31df23cec38d6f2ee823a7468b 1590 madplay_0.15.2b-8.2.dsc
01cc9dff324cb806bcac98d3d8e607ebbb05a7b8 6903 madplay_0.15.2b-8.2.diff.gz
Checksums-Sha256:
800af690c720b70b9f2a42e37b9014b5e48354fec4f0fbea0d80fe8277055e5c 1590
madplay_0.15.2b-8.2.dsc
87ca78d3e5fffba66109a0ccbb9c0ac097c5b80c8717d6e62924d40eac1ce9cc 6903
madplay_0.15.2b-8.2.diff.gz
Files:
dadd9b2f8b62c33259278cd1bfe1ba2d 1590 sound optional madplay_0.15.2b-8.2.dsc
c04829a29e12242e600a13e167c59695 6903 sound optional
madplay_0.15.2b-8.2.diff.gz
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAlpIkWkACgkQnFyZ6wW9
dQrjXQf8CXrnMnLy5h6JiorsRKWUnZ35ca6nYJDyJomnkqwcikUhINXcstKANq3a
CuKrJuuI9AqI5omTtp5BIop3jm+M2SWgp2EWvkieQ5qu1GN6B04SQi38sMjqDsUY
O4u46gBvnqwyfnnvXjOMjuff4erXfQ4wEEY3F4/SeAwF5dA0lbFDEczrsUDJDZV+
h2m/5uanRqsvFWP3DFitd0s1HPmOegm7eKlYLH0VROb6YHdrXKhZYCy0VLnhYxja
+pbakI2vloyFO9C2YIkk4Mu0EWLGT0Waxt48ckEF+vsrPlYAN7W+jr1G4gm5oFWM
tQBTIWRZAQVa/p9zNVv1U2fOxmSDiw==
=q/T7
-END PGP SIGNATURE End Message ---
Bug#885927: xdemorse: file xdemorse.glade missing from package
Package: xdemorse Version: 3.4-1 Severity: grave Justification: renders package unusable Dear Maintainer, xdemorse fails to start. When running it from a terminal it prints the following messages: Xdemorse: failed to add objects to builder: Failed to open file “/home/daniele/.xdemorse/xdemorse.glade”: No such file or directory [...] in fact the glade file isn't available in the package, copying it from the upstream tarball makes the program start. thanks, Daniele -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.13.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8), LANGUAGE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xdemorse depends on: ii libasound2 1.1.3-5 ii libc6 2.25-5 ii libcairo2 1.15.8-3 ii libgdk-pixbuf2.0-0 2.36.11-1 ii libglib2.0-02.54.2-4 ii libgtk-3-0 3.22.26-2 xdemorse recommends no packages. xdemorse suggests no packages. -- no debconf information
Processed: severity of 885929 is grave
Processing commands for cont...@bugs.debian.org: > severity 885929 grave Bug #885929 [git-buildpackage] git-buildpackage: gbp pq import fails on non UTF-8 chars in patch Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 885929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885929 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#885935: python-pysodium depends on cruft package libsodium18
package: pysodium severity: serious libsodium18 has been replaced by libsodium23, python-pysodium and python3-pysodium still depends on libsodium18. I have not checked whether a simple no-change rebuild and upload is all that is needed or if further changes are required but either way since the package is arch all a sourceful upload is needed.
Bug#885934: python-libnacl depends on cruft package libsodium18
package: python-libnacl severity: serious libsodium18 has been replaced by libsodium23, python-libnacl still depends on libsodium18. I have not checked whether a simple no-change rebuild and upload is all that is needed or if further changes are required but either way since the package is arch all a sourceful upload is needed.
Bug#801849: marked as done (node-jquery does not register)
Your message dated Sun, 31 Dec 2017 15:06:18 + with message-id and subject line Bug#801849: fixed in node-jquery 2.2.4+dfsg-1 has caused the Debian Bug report #801849, regarding node-jquery does not register 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.) -- 801849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801849 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-jquery Version: 1.6.3-1 Severity: important Hi, The node-jquery package no longer works at all: module.js:460 return process.dlopen(module, path._makeLong(filename)); ^ Error: Module did not self-register. at Error (native) at Object.Module._extensions..node (module.js:460:18) at Module.load (module.js:356:32) at Function.Module._load (module.js:311:12) at Module.require (module.js:366:17) at require (module.js:385:17) at Object. (/usr/lib/nodejs/contextify/contextifyjs.js:1:77) at Module._compile (module.js:435:26) at Object.Module._extensions..js (module.js:442:10) at Module.load (module.js:356:32) -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: armhf Kernel: Linux 4.0.0-trunk-amd64 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages node-jquery depends on: ii node-jsdom 0.8.10+dfsg1-1 ii nodejs 4.2.1~dfsg-1 node-jquery recommends no packages. node-jquery suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: node-jquery Source-Version: 2.2.4+dfsg-1 We believe that the bug you reported is fixed in the latest version of node-jquery, 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 801...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pirate Praveen (supplier of updated node-jquery 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, 31 Dec 2017 18:30:30 +0530 Source: node-jquery Binary: node-jquery Architecture: source Version: 2.2.4+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Pirate Praveen Description: node-jquery - NodeJS wrapper for jQuery Closes: 801849 Changes: node-jquery (2.2.4+dfsg-1) unstable; urgency=medium . [ Pirate Praveen ] * New upstream release * Add myself to uploaders * Build using grunt * Install package.json (Closes: #801849) * Remove dependency on node-jsdom (no longer required) * Replace gzip-js with zlib * Update section, priority, bump standards * Use libjs-sizzle as a build dependency * Remove external dirctory from source tarball . [ Mathias Behrle ] * Add a debian/.gitignore file to avoid future errors with patches. . [ Jérémy Lal ] * Fix skip-gzip-js patch Checksums-Sha1: f14804fdab8ae354f1f794e379b06cc84683b811 2160 node-jquery_2.2.4+dfsg-1.dsc 320fd8aef4fc23da94639a272dc8c328cda0b3b8 253452 node-jquery_2.2.4+dfsg.orig.tar.xz c7203948f6e46def5d74dcb8e154f60143668c09 3312 node-jquery_2.2.4+dfsg-1.debian.tar.xz b12beb903c8f7e92656e8a0d14fa4c2c7e91d3af 13328 node-jquery_2.2.4+dfsg-1_source.buildinfo Checksums-Sha256: 1c0058214d139dc0c6b42acfb78223b91b2e210c523b2361e80540d47dfaa885 2160 node-jquery_2.2.4+dfsg-1.dsc 147e0ce686b462b64c9f9058c75e0323fa9ed0a4990c4e19f7f404d21855457e 253452 node-jquery_2.2.4+dfsg.orig.tar.xz 6acabac5583f55097003561e9f49b9b13a1896928e1497e9cb2e2713c2fed57d 3312 node-jquery_2.2.4+dfsg-1.debian.tar.xz 9458882e9d73e45f2d481e1ffd4b4480e3fc803b4a64116b91303de1719af7d7 13328 node-jquery_2.2.4+dfsg-1_source.buildinfo Files: bb92fbf1c8ddc7e20256b6edbf0aa702 2160 javascript optional node-jquery_2.2.4+dfsg-1.dsc 929d40e45ba976159776c6ff32201cea 253452 javascript optional node-jquery_2.2.4+dfsg.orig.tar.xz a04a3014e17219545fccf89ea7ffe5d3 3312 javascript optional node-jquery_2.2.4+dfsg-1.debian.tar.xz ad63e2a51be2fc2897eaab9cbce477b7
Bug#884214: marked as done (purify FTBFS with libspdlog-dev 1:0.14.0-1)
Your message dated Sun, 31 Dec 2017 15:07:31 + with message-id and subject line Bug#884214: fixed in purify 2.0.0-2 has caused the Debian Bug report #884214, regarding purify FTBFS with libspdlog-dev 1:0.14.0-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.) -- 884214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884214 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: purify Version: 2.0.0-1 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/purify.html ... In file included from /build/1st/purify-2.0.0/cpp/purify/logging.h:7:0, from /build/1st/purify-2.0.0/cpp/purify/utilities.cc:2: /build/1st/purify-2.0.0/cpp/purify/logging.enabled.h: In function 'std::shared_ptr purify::logging::initialize(const string&)': /build/1st/purify-2.0.0/cpp/purify/logging.enabled.h:15:92: error: too many arguments to function 'std::shared_ptr spdlog::stdout_logger_mt(const string&)' auto const result = spdlog::stdout_logger_mt(default_logger_name() + name, color_logger()); ^ In file included from /usr/include/spdlog/spdlog.h:189:0, from /build/1st/purify-2.0.0/cpp/purify/logging.enabled.h:6, from /build/1st/purify-2.0.0/cpp/purify/logging.h:7, from /build/1st/purify-2.0.0/cpp/purify/utilities.cc:2: /usr/include/spdlog/details/spdlog_impl.h:87:40: note: declared here inline std::shared_ptr spdlog::stdout_logger_mt(const std::string& logger_name) ^~ In file included from /usr/include/sopt/logging.h:7:0, from /usr/include/sopt/linear_transform.h:9, from /build/1st/purify-2.0.0/cpp/purify/MeasurementOperator.h:5, from /build/1st/purify-2.0.0/cpp/purify/MeasurementOperator.cc:2: /usr/include/sopt/logging.enabled.h: In function 'std::shared_ptr sopt::logging::initialize(const string&)': /usr/include/sopt/logging.enabled.h:16:92: error: too many arguments to function 'std::shared_ptr spdlog::stdout_logger_mt(const string&)' auto const result = spdlog::stdout_logger_mt(default_logger_name() + name, color_logger()); ^ In file included from /usr/include/spdlog/spdlog.h:189:0, from /usr/include/sopt/logging.enabled.h:5, from /usr/include/sopt/logging.h:7, from /usr/include/sopt/linear_transform.h:9, from /build/1st/purify-2.0.0/cpp/purify/MeasurementOperator.h:5, from /build/1st/purify-2.0.0/cpp/purify/MeasurementOperator.cc:2: /usr/include/spdlog/details/spdlog_impl.h:87:40: note: declared here inline std::shared_ptr spdlog::stdout_logger_mt(const std::string& logger_name) ^~ In file included from /usr/include/sopt/logging.h:7:0, from /usr/include/sopt/linear_transform.h:9, from /build/1st/purify-2.0.0/cpp/purify/MeasurementOperator.h:5, from /build/1st/purify-2.0.0/cpp/purify/clean.h:10, from /build/1st/purify-2.0.0/cpp/purify/clean.cc:2: /usr/include/sopt/logging.enabled.h: In function 'std::shared_ptr sopt::logging::initialize(const string&)': /usr/include/sopt/logging.enabled.h:16:92: error: too many arguments to function 'std::shared_ptr spdlog::stdout_logger_mt(const string&)' auto const result = spdlog::stdout_logger_mt(default_logger_name() + name, color_logger()); ^ In file included from /usr/include/spdlog/spdlog.h:189:0, from /usr/include/sopt/logging.enabled.h:5, from /usr/include/sopt/logging.h:7, from /usr/include/sopt/linear_transform.h:9, from /build/1st/purify-2.0.0/cpp/purify/MeasurementOperator.h:5, from /build/1st/purify-2.0.0/cpp/purify/clean.h:10, from /build/1st/purify-2.0.0/cpp/purify/clean.cc:2: /usr/include/spdlog/details/spdlog_impl.h:87:40: note: declared here inline std::shared_ptr spdlog::stdout_logger_mt(const std::string& logger_name) ^~ /build/1st/purify-2.0.0/cpp/purify/pfitsio.cc: In function 'purify::Image > purify::pfitsio::read2d(const string&)': /build/1st/purify-2.0.0/cpp/purify/pfitsio.cc:103:8: warning: 'te
Bug#864337: marked as done (python-blessed: Non-determistically FTBFS due to unreliable timing in tests)
Your message dated Sun, 31 Dec 2017 15:07:50 +
with message-id
and subject line Bug#864337: fixed in python-blessed 1.14.2-1
has caused the Debian Bug report #864337,
regarding python-blessed: Non-determistically FTBFS due to unreliable timing in
tests
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.)
--
864337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864337
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-blessed
Version: 1.14.1-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Dear Maintainer,
python-blessed's testsuite appears to use method timing/benchmarking in such
a way that it will non-deterministically FTBFS:
[…]
test_esc_delay_cbreak_timout_0
def test_esc_delay_cbreak_timout_0():
"""esc_delay still in effect with timeout of 0 ("nonblocking")."""
pid, master_fd = pty.fork()
if pid == 0: # child
cov = init_subproc_coverage('test_esc_delay_cbreak_timout_0')
term = TestTerminal()
os.write(sys.__stdout__.fileno(), SEMAPHORE)
with term.cbreak():
stime = time.time()
inp = term.inkey(timeout=0)
measured_time = (time.time() - stime) * 100
os.write(sys.__stdout__.fileno(), (
'%s %i' % (inp.name, measured_time,)).encode('ascii'))
sys.stdout.flush()
if cov is not None:
cov.stop()
cov.save()
os._exit(0)
with echo_off(master_fd):
os.write(master_fd, u'\x1b'.encode('ascii'))
read_until_semaphore(master_fd)
stime = time.time()
key_name, duration_ms = read_until_eof(master_fd).split()
pid, status = os.waitpid(pid, 0)
assert key_name == u'KEY_ESCAPE'
assert os.WEXITSTATUS(status) == 0
assert math.floor(time.time() - stime) == 0.0
> assert 34 <= int(duration_ms) <= 45, int(duration_ms)
E AssertionError: 71
E assert 71 <= 45
E+ where 71 = int('71')
blessed/tests/test_keyboard.py:528: AssertionError
1 failed, 305 passed in 75.27 seconds
=
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd
/build/1st/python-blessed-1.14.1/.pybuild/pythonX.Y_3.5/build; python3.5 -m
pytest
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.5 returned
exit code 13
debian/rules:7: recipe for target 'build' failed
make: *** [build] Error 25
dpkg-buildpackage: error: debian/rules build gave error exit status 2
I: copying local configuration
E: Failed autobuilding of package
[…]
The full build log is attached or can be viewed here:
https://tests.reproducible-builds.org/debian/logs/unstable/amd64/python-blessed_1.14.1-1.build1.log.gz
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
python-blessed.1.14.1-1.logs.unstable.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: python-blessed
Source-Version: 1.14.2-1
We believe that the bug you reported is fixed in the latest version of
python-blessed, 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.
Pierre-Elliott Bécue (supplier of updated python-blessed
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 31 Dec 2017 14:01:34 +0100
Source: python-blessed
Binary: python-blessed python3-blessed
Architecture: source
Version: 1.14.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team
Changed-By: Pierre-Elliott Bécue
Description:
python-blessed - Thin, practical wrapper around terminal capabilities in
Python2
python3-blessed - Thin, practical wrap
Bug#885934: python-libnacl depends on cruft package libsodium18
On Sun, Dec 31, 2017 at 02:36:06PM +, peter green wrote: > libsodium18 has been replaced by libsodium23, python-libnacl still > depends on libsodium18. > > I have not checked whether a simple no-change rebuild and upload is > all that is needed or if further changes are required but either way > since the package is arch all a sourceful upload is needed. Thanks for the heads-up. Upstream added the necessary support in 1.6.1, so it's just a simple rebuild; I'll sort that out. -- Colin Watson [cjwat...@debian.org]
Bug#885929: [git-buildpackage/master] patch_series: Don't fail on decoding errors when looking for DEP3 headers
tag 885929 pending thanks Date: Sun Dec 31 16:40:21 2017 +0100 Author: Guido Günther Commit ID: 0730a57db438b935bc7f16957650a6ef25589598 Commit URL: https://git.sigxcpu.org/cgit/git-buildpackage//commit/?id=0730a57db438b935bc7f16957650a6ef25589598 Patch URL: https://git.sigxcpu.org/cgit/git-buildpackage//patch/?id=0730a57db438b935bc7f16957650a6ef25589598 patch_series: Don't fail on decoding errors when looking for DEP3 headers Closes: #885929
Processed: [git-buildpackage/master] patch_series: Don't fail on decoding errors when looking for DEP3 headers
Processing commands for cont...@bugs.debian.org: > tag 885929 pending Bug #885929 [git-buildpackage] git-buildpackage: gbp pq import fails on non UTF-8 chars in patch Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 885929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885929 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#885934: marked as done (python-libnacl depends on cruft package libsodium18)
Your message dated Sun, 31 Dec 2017 15:49:20 + with message-id and subject line Bug#885934: fixed in python-libnacl 1.6.1-2 has caused the Debian Bug report #885934, regarding python-libnacl depends on cruft package libsodium18 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.) -- 885934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885934 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: python-libnacl severity: serious libsodium18 has been replaced by libsodium23, python-libnacl still depends on libsodium18. I have not checked whether a simple no-change rebuild and upload is all that is needed or if further changes are required but either way since the package is arch all a sourceful upload is needed. --- End Message --- --- Begin Message --- Source: python-libnacl Source-Version: 1.6.1-2 We believe that the bug you reported is fixed in the latest version of python-libnacl, 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 885...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Colin Watson (supplier of updated python-libnacl 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, 31 Dec 2017 15:30:10 + Source: python-libnacl Binary: python-libnacl python3-libnacl Architecture: source Version: 1.6.1-2 Distribution: unstable Urgency: medium Maintainer: Colin Watson Changed-By: Colin Watson Description: python-libnacl - Python 2 bindings for libsodium based on ctypes python3-libnacl - Python 3 bindings for libsodium based on ctypes Closes: 885934 Changes: python-libnacl (1.6.1-2) unstable; urgency=medium . * Rebuild against libsodium23 (closes: #885934). Checksums-Sha1: d078250e37b4e7d42d1a9037a4dd703c5fda4847 2154 python-libnacl_1.6.1-2.dsc bd0479d024f8feefa741f5356f6c4979be137b88 2260 python-libnacl_1.6.1-2.debian.tar.xz 6b6df53a9b974afc7a494851850dd8f0936d39ab 7254 python-libnacl_1.6.1-2_source.buildinfo Checksums-Sha256: 844f0ccfcae2c5268504e35bc082c249eb44761f302550b383f5651856e2e14f 2154 python-libnacl_1.6.1-2.dsc 0a717c5226d01d5d10277b8f806e33cd232686265c8b6d53bdf132d9a5a8f452 2260 python-libnacl_1.6.1-2.debian.tar.xz e03ca03ff05dbd5ea61cd4d9849378495d8bd73e2576142594206a0bc6c52dfc 7254 python-libnacl_1.6.1-2_source.buildinfo Files: 46e1497e0236e62d6e4b626db650c0ae 2154 python optional python-libnacl_1.6.1-2.dsc c2ab03b0330422d75cbc87e811880ca2 2260 python optional python-libnacl_1.6.1-2.debian.tar.xz a27ade54489b3cbfbbe4a2f9ef659dd1 7254 python optional python-libnacl_1.6.1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAlpJAscACgkQOTWH2X2G UAvcTQ/8D+RrvHWeXE1plyER7scfRpmgWRSuQARSYQ1EeX/mqzGA01VyIKyjxUbn Ja7K25ft/rOSAZHcHE+j/kO9meaSJg2NN95ngGG49K5KV+3ddQhdMsQxpHDnMG35 jfMoAysr+npH96FAc7uLYCWlG6mYIjnmEs8D547dg4Sz5W2KQCzEWMBHce7Jdvvc Zkpk6D7SiWr25aKS0/T0vYj4YtQJOPKkEQcIgMtVrUOpFOK0AFfLJ7cUW+HfmQU0 fa8jG0CRY/9oGBPrdCERDPLh4eBggFpcwDUQem1NoSiUx1sKAhkrP3nnof9KYcEU YGBJWxwD+ttlHBThdDWfezn7/Qz8EJkN6L/ZXj0fEfLUEjl9T4JGOL9RKZy6fs7B eeCSjQoNFrkzq80ZJksndQXHFyZTNRewNSkeveMfFD7IhMZYXki7aXUUUCbEwHNM 4xWHOvlrR6JezatRaKoA+OsPHISLGtPMCVJVTkq/dXIlGbiHFNvO1Nw0upZUH7+N jYciGKbM1b+vQ/VCXEyPr/PXe+U90APAiGwO0iVP4svh9j/VYIvLpROXQTHKIGVT K2K8x0u8T/gV5L89thB+N5C5UUYLy2QX0C5EBRMVSyuIpQ64ZCz5IIzIEKHIsuxQ awqj1+F2NgJCwFpTxgZanU1e8n/nDVFn/7OUWDbMDBXKxtFhOAo= =SMct -END PGP SIGNATURE End Message ---
Bug#885401: marked as done (openmw uninstallable)
Your message dated Sun, 31 Dec 2017 16:03:57 + with message-id and subject line Bug#885401: fixed in openmw 0.43.0-1 has caused the Debian Bug report #885401, regarding openmw uninstallable 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.) -- 885401: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885401 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Subject: openmw uninstallable Source: openmw Version: 0.41.0-1+b1 Severity: grave Justification: renders package unusable Dear Maintainer, Attempting to install openmw with apt fails. When I try to install: sudo apt install openmw Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: openmw : Depends: libopenscenegraph-3.4-130 but it is not going to be installed Recommends: openmw-launcher but it is not going to be installed E: Unable to correct problems, you have held broken packages. sudo apt install libopenscenegraph-3.4-130 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libopenscenegraph-3.4-130 : Depends: gdal-abi-2-2-1 but it is not installable E: Unable to correct problems, you have held broken packages. sudo apt install gdal-abi-2-2-1 Reading package lists... Done Building dependency tree Reading state information... Done Package gdal-abi-2-2-1 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source It appears that I have the necessary libs on my machine, and that the virtual package that libgdal20 provides is missing. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.14.0-1-amd64 (SMP w/4 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: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: openmw Source-Version: 0.43.0-1 We believe that the bug you reported is fixed in the latest version of openmw, 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 885...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bret Curtis (supplier of updated openmw 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, 30 Dec 2017 16:05:38 +0100 Source: openmw Binary: openmw openmw-cs openmw-data openmw-launcher Architecture: source Version: 0.43.0-1 Distribution: unstable Urgency: medium Maintainer: Bret Curtis Changed-By: Bret Curtis Description: openmw - Reimplementation of The Elder Scrolls III: Morrowind openmw-cs - Replacement of The Elder Scrolls Construction Set openmw-data - Resources for the OpenMW engine openmw-launcher - Launcher for OpenMW using the Qt-Gui-Toolkit Closes: 874599 875081 885401 Changes: openmw (0.43.0-1) unstable; urgency=medium . * New Upstream release: OpenMW-0.43.0. (Closes: #885401, #874599, #875081) * Declare compliance with Debian Policy 4.1.3. Checksums-Sha1: e16dd37c49ee5e03a3d0b1b8a41db180396cba2d 2633 openmw_0.43.0-1.dsc 7b25120b311b79ff3bb098f852754bc50aa97d6d 5023421 openmw_0.43.0.orig.tar.gz cf5f498e3a314ee04d7366b90c186be04a00c208 7484 openmw_0.43.0-1.debian.tar.xz 4f472cf5565c37c583adafd9b8682129744aa904 21516 openmw_0.43.0
Bug#864963: Uploading NMU to drop gdebi-kde package
Control: tags -1 +pending I am "fixing" this bug by not building the gdebi-kde package any more since this is the last package in Debian depending on pykde4. I have uploaded this to Debian's DELAYED/15 queue. Please let me know if I should speed up or delay the upload. Please see https://code.launchpad.net/~jbicha/gdebi/nmu-roundup/+merge/335608 I am also uploading changes to allow gdebi to work without gksu. See https://bugs.debian.org/822596 for more details. Thanks, Jeremy Bicha
Processed: Uploading NMU to port gdebi away from gksu
Processing control commands: > tags -1 +pending Bug #822596 [src:gdebi] gdebi: depends on gksu which is deprecated Added tag(s) pending. -- 822596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822596 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#822596: Uploading NMU to port gdebi away from gksu
Control: tags -1 +pending I am uploading the work done in Ubuntu to port gdebi away from gksu to Debian's DELAYED/15 queue. Please let me know if I should speed up or delay the upload. Note that gdebi still won't work in the default Debian GNOME Buster or Ubuntu 17.10 sessions (in other words, GNOME on Wayland) because it still tries to run the GUI as root after requesting elevated permissions. gdebi is now one of the last 2 packages to depend on gksu in Testing. The other is caja-gksu (which simply needs to be removed now that caja-admin exists) https://bugs.debian.org/822595 I am also removing gdebi-kde in this upload. See https://bugs.debian.org/864963 for more details. Please see https://code.launchpad.net/~jbicha/gdebi/nmu-roundup/+merge/335608 Thanks, Jeremy Bicha
Processed: Uploading NMU to drop gdebi-kde package
Processing control commands: > tags -1 +pending Bug #864963 [gdebi-kde] gdebi-kde: Depends on python3-pykde4 which is to be removed for Buster Added tag(s) pending. -- 864963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864963 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#822595: Raising severity to serious for packages depending on gksu
Processing control commands: > severity -1 serious Bug #822595 [src:caja-extensions] caja-extensions: depends on gksu which is deprecated Severity set to 'serious' from 'important' -- 822595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822595 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#885888: marked as done (lordsawar: Don't Build-Depend on libglademm2.4-dev)
Your message dated Sun, 31 Dec 2017 18:05:14 + with message-id and subject line Bug#885888: fixed in lordsawar 0.3.1-4 has caused the Debian Bug report #885888, regarding lordsawar: Don't Build-Depend on libglademm2.4-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.) -- 885888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885888 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lordsawar Version: 0.3.1-3 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs glademm Tags: sid buster patch lordsawar has an apparently unnecessary Build-Depends on libglademm2.4- dev. libglade is for gtk2 but lordsawar uses gtk3. Please drop this Build-Depends since libglademm2.4 will be removed from Debian soon. (No patch attached because this is a trivial fix.) On behalf of the Debian GNOME team, Jeremy Bicha --- End Message --- --- Begin Message --- Source: lordsawar Source-Version: 0.3.1-4 We believe that the bug you reported is fixed in the latest version of lordsawar, 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 885...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated lordsawar package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 31 Dec 2017 17:04:58 +0100 Source: lordsawar Binary: lordsawar lordsawar-data Architecture: source Version: 0.3.1-4 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Markus Koschany Description: lordsawar - Clone of the popular SSG game Warlords II lordsawar-data - Clone of the popular SSG game Warlords II - data files Closes: 885888 Changes: lordsawar (0.3.1-4) unstable; urgency=medium . * Drop libglademm-2.4-dev from Build-Depends. (Closes: #885888) * Declare compliance with Debian Policy 4.1.3. * Use dh_missing override. * Switch to compat level 11. Checksums-Sha1: 9271fec22dad2ad42f4ddd2e66fbe60f45a36a2a 2277 lordsawar_0.3.1-4.dsc 4ae15b1929f8315e90c760e9a2937f30b1e96ae3 6412 lordsawar_0.3.1-4.debian.tar.xz 09d594697246c20230281749f93c2b673cf94aa7 6452 lordsawar_0.3.1-4_source.buildinfo Checksums-Sha256: 16e2c2004e5d17a72036c267ece32bdeab2a267f34cac4b3b9a0c03eeed5ac65 2277 lordsawar_0.3.1-4.dsc d1a87534abe9c58b1eefbb3387b5928d77372937fa2b094e8a8008dbdfc630dc 6412 lordsawar_0.3.1-4.debian.tar.xz a82d3c7f09da884e463b16832fda269193e5e094a224091646d42c970207279a 6452 lordsawar_0.3.1-4_source.buildinfo Files: 33262c0da6aa189eb87530889cea1b98 2277 games optional lordsawar_0.3.1-4.dsc ef6d4fada9333c19fa4949bfd9c5e462 6412 games optional lordsawar_0.3.1-4.debian.tar.xz 450c90c573dcf09f98d46ee499e0f0e7 6452 games optional lordsawar_0.3.1-4_source.buildinfo -BEGIN PGP SIGNATURE- iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAlpJIgtfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp YW4ub3JnAAoJENmtFLlRO1HkICYQAMpaGcmI7VvPXSLE2DezHWa6e/xuUvUFVW3e pDS1rsYz8+nuFj6J3xWWgfqz7kU3tIBJVKSWQlKFH3mHwGoo7evF1b21qh++vmMc va8OyftxTgTzMB7+KI5ALRxbi552bP+ZexYuX0495SismuhrfnVfA9iBToXGW3nM U8gsDlcc9cwSqCanRsJObtURv0XxOG290WyQXlkf2xEY3KwcAEaF/99HHG/bpU0i 6ZxipS4CCLaClUnQT2wW3cSsGbdM3+60vxWtnLsIm5AJ2ByrzgozDLLpiw7FMyoX mhb8+HzvHGaC34p12VHpcjvadC2J+VRoi+7MXbw5vU+1u+7LqRN8S9A6ZI5x/AtT KCC0+4Yug5+tSOOqcKnrVRiLJENXOJo8u8UU59ru5GK7xTakaB7RPIV5LgbGYOZr 5kdBzwetTQNvRD/3Be9Iiqy8eJlEci7VXyHcQzfXFizGT3tdhMvIs1mtFifByxyw TqdN8vE64qDHoyjOvbGvgwtD4An54x1v/TQc/ULBrFtVP9lODD5mF4N+8OcSdXf6 hR2OS9PhIdZNod1RgDfzs8cuQETqAgmK5g50H/veo33XTeAqtVGOMrL4pBiNs7PM u73NocXR2QjGWDgCOBU1i0GN67KsTe+y92Kn6xRJxIviNwissnrVKzto/kc3owiC dpc6E1ld =y88b -END PGP SIGNATURE End Message ---
Bug#884476: derivations FTBFS with poppler 0.61.1
Thank you for the reminder. Poppler is always changing, isn't it?
NMUs are always okay with me, but I assume that you have better things to
do than to NMU an obscure package like my derivations. When I have some
time, I will look into the matter.
I need to update the package to the upstream version sometime, anyway.
On Thu, Dec 28, 2017 at 10:24 AM, Juhani Numminen wrote:
> Control: tags 884476 upstream
>
> On Fri, 15 Dec 2017 18:59:41 +0200 Adrian Bunk wrote:
> > Source: derivations
> > Version: 0.53.20120414-2
> > Severity: serious
> > Tags: buster sid
> >
> > https://tests.reproducible-builds.org/debian/rb-pkg/
> unstable/amd64/derivations.html
> >
> > ...
> > update_catalog.cc: In function 'int {anonymous}::copy_but(Dict*, Dict*,
> const set&)':
> > update_catalog.cc:39:33: error: no matching function for call to
> 'Dict::getValNF(int&, Object*)'
> >src ->getValNF( i , &obj );
> > ^
> > In file included from /usr/include/poppler/Object.h:342:0,
> > from /usr/include/poppler/XRef.h:42,
> > from /usr/include/poppler/PDFDoc.h:49,
> > from PDF_rep.h:6,
> > from update_catalog.cc:12:
> > /usr/include/poppler/Dict.h:85:10: note: candidate: Object
> Dict::getValNF(int) const
> >Object getValNF(int i) const;
> > ^~~~
>
> Dear Maintainer,
> CCing your derivations.org address since this seems like an "upstream"
> matter.
>
> Looks like there has been a major API change in poppler:
> https://cgit.freedesktop.org/poppler/poppler/commit/?id=9773c1534
>
> I superficially checked the latest derivations source and it isn't updated
> for
> the new API yet.
> http://www.derivations.org/derivations_0.55.20170703.orig.tar.xz
>
>
> Thanks,
> Juhani Numminen
>
Bug#885943: Fails to start: GLX version not found
Package: gr-osmosdr Version: 0.1.4-14 Severity: grave I installed gr-osmosdr and tried to run it only to get an error: wx._core.PyAssertionError: C++ assertion "ok" failed at ../src/unix/glx11.cpp(589) in GetGLXVersion(): GLX version not found The full output of the command is: linux; GNU C++ version 7.2.0; Boost_106200; UHD_003.010.002.000-0-unknown gr-osmosdr 0.1.4 (0.1.4) gnuradio 3.7.11 built-in source types: file osmosdr fcd rtl rtl_tcp uhd miri hackrf bladerf rfspace airspy airspyhf soapy redpitaya freesrp Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock Found Rafael Micro R820T tuner Using device #0 Generic RTL2832U SN: 153705700 Found Rafael Micro R820T tuner [R82XX] PLL not locked! Exact sample rate is: 25.000414 Hz [R82XX] PLL not locked! Traceback (most recent call last): File "/usr/bin/osmocom_fft", line 850, in main () File "/usr/bin/osmocom_fft", line 846, in main app = stdgui2.stdapp(app_top_block, "osmocom Spectrum Browser", nstatus=1) File "/usr/lib/python2.7/dist-packages/gnuradio/wxgui/stdgui2.py", line 46, in __init__ wx.App.__init__ (self, redirect=False) File "/usr/lib/python2.7/dist-packages/wx-3.0-gtk2/wx/_core.py", line 8628, in __init__ self._BootstrapApp() File "/usr/lib/python2.7/dist-packages/wx-3.0-gtk2/wx/_core.py", line 8196, in _BootstrapApp return _core_.PyApp__BootstrapApp(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/gnuradio/wxgui/stdgui2.py", line 49, in OnInit frame = stdframe (self.top_block_maker, self.title, self._nstatus) File "/usr/lib/python2.7/dist-packages/gnuradio/wxgui/stdgui2.py", line 76, in __init__ self.panel = stdpanel (self, self, top_block_maker) File "/usr/lib/python2.7/dist-packages/gnuradio/wxgui/stdgui2.py", line 98, in __init__ self.top_block = top_block_maker (frame, self, vbox, sys.argv) File "/usr/bin/osmocom_fft", line 255, in __init__ fft_rate=options.fft_rate) File "/usr/lib/python2.7/dist-packages/gnuradio/wxgui/fftsink_gl.py", line 126, in __init__ persist_alpha=persist_alpha, File "/usr/lib/python2.7/dist-packages/gnuradio/wxgui/fft_window.py", line 277, in __init__ self.plotter = plotter.channel_plotter(self) File "/usr/lib/python2.7/dist-packages/gnuradio/wxgui/plotter/channel_plotter.py", line 49, in __init__ grid_plotter_base.__init__(self, parent, MIN_PADDING) File "/usr/lib/python2.7/dist-packages/gnuradio/wxgui/plotter/grid_plotter_base.py", line 50, in __init__ plotter_base.__init__(self, parent) File "/usr/lib/python2.7/dist-packages/gnuradio/wxgui/plotter/plotter_base.py", line 94, in __init__ wx.glcanvas.GLCanvas.__init__(self, parent, wx.ID_ANY, attribList=attribList);# Specifically use the CTOR which does NOT create an implicit GL context File "/usr/lib/python2.7/dist-packages/wx-3.0-gtk2/wx/glcanvas.py", line 106, in __init__ _glcanvas.GLCanvas_swiginit(self,_glcanvas.new_GLCanvas(*args, **kwargs)) wx._core.PyAssertionError: C++ assertion "ok" failed at ../src/unix/glx11.cpp(589) in GetGLXVersion(): GLX version not found -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_IL.utf8, LC_CTYPE=en_IL.utf8 (charmap=UTF-8), LANGUAGE=en_IL:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gr-osmosdr depends on: ii libairspy01.0.9-1+b2 ii libairspyhf0 1.0-1 ii libbladerf1 0.2016.06-2 ii libboost-atomic1.62.0 1.62.0+dfsg-4+b2 ii libboost-chrono1.62.0 1.62.0+dfsg-4+b2 ii libboost-date-time1.62.0 1.62.0+dfsg-4+b2 ii libboost-system1.62.0 1.62.0+dfsg-4+b2 ii libboost-thread1.62.0 1.62.0+dfsg-4+b2 ii libc6 2.25-5 ii libfreesrp0 0.3.0-2 ii libgcc1 1:7.2.0-18 ii libgnuradio-blocks3.7.11 3.7.11-6 ii libgnuradio-fcd3.7.11 3.7.11-6 ii libgnuradio-fcdproplus3.7.11 3.7.25.4b6464b-5 ii libgnuradio-iqbalance3.7.11 0.37.2-11 ii libgnuradio-osmosdr0.1.4 0.1.4-14 ii libgnuradio-pmt3.7.11 3.7.11-6 ii libgnuradio-runtime3.7.11 3.7.11-6 ii libgnuradio-uhd3.7.11 3.7.11-6 ii libhackrf02017.02.1-1 ii liblog4cpp5v5 1.1.1-3 ii libmirisdr0 0.0.4.59ba37-5+b1 ii libosmosdr0 0.1.8.effcaa7-7+b1 ii libpython2.7 2.7.14-4 ii librtlsdr00.5.3-13 ii libsoapysdr0.60.6.1-1 ii libstdc++6
Processed: Re: verbiste: Please drop the (build-)dependency against gnome-vfs
Processing control commands: > severity -1 serious Bug #868409 [src:verbiste] verbiste: Please drop the (build-)dependency against gnome-vfs Severity set to 'serious' from 'important' -- 868409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868409 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: gallery-uploader: Uses deprecated python-gnomekeyring
Processing control commands: > severity -1 serious Bug #867959 [src:gallery-uploader] gallery-uploader: Uses deprecated python-gnomekeyring Severity set to 'serious' from 'important' > tags -1 +sid +buster Bug #867959 [src:gallery-uploader] gallery-uploader: Uses deprecated python-gnomekeyring Added tag(s) sid. Bug #867959 [src:gallery-uploader] gallery-uploader: Uses deprecated python-gnomekeyring Added tag(s) buster. -- 867959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867959 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#790589: gnome-specimen: depends on python-gnome2 which is deprecated
On Tue, Jun 30, 2015 at 4:18 PM, Kartik Mistry wrote: > It seems that we can remove this package. I will file request. Removal bug filed: https://bugs.debian.org/885949 Thanks, Jeremy Bicha
Bug#885570: More info
I also have reproduced this flicker which leads to a total freeze on my Lenovo T450 running Stretch with Intel HD Graphics 5500. It was immediately noticed when rebooting and using the linux-image-4.9.0-4-amd kernel. Once I booted back into the previous kernel (4.9.0-3-amd) the problem went away. I also have a dell laptop that has Intel Graphics HD 520 that I upgraded to the 4.9.0-4-amd kernel and the problem does not seem to affect it. Looks like it might be some incompatibility between the 4.9.0-4 kernel and the intel 5500 graphics? Thanks Dave
Bug#882955: marked as done (ufo-filters FTBFS with glibc 2.25)
Your message dated Sun, 31 Dec 2017 21:49:33 + with message-id and subject line Bug#882955: fixed in ufo-filters 0.14.1+dfsg1-1.1 has caused the Debian Bug report #882955, regarding ufo-filters FTBFS with glibc 2.25 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 882955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ufo-filters Version: 0.14.1+dfsg1-1 Severity: serious cd /build/1st/ufo-filters-0.14.1+dfsg1/obj-x86_64-linux-gnu/src && /usr/bin/cc -DG_LOG_DOMAIN=\"Ufo\" -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -Dufofilterread_EXPORTS -I/build/1st/ufo-filters-0.14.1+dfsg1/deps/oclfft -I/usr/include/x86_64-linux-gnu -I/usr/include/hdf5/serial -I/build/1st/ufo-filters-0.14.1+dfsg1/obj-x86_64-linux-gnu/src -I/build/1st/ufo-filters-0.14.1+dfsg1/src -I/usr/include/ufo-0 -I/usr/include/json-glib-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c99 -std=c99 -pedantic -Wall -Wextra -fPIC -Wno-unused-parameter -Wno-deprecated-declarations -fopenmp -fPIC -Wall -Wextra -fPIC -Wno-unused-parameter -o CMakeFiles/ufofilterread.dir/ufo-read-task.c.o -c /build/1st/ufo-filters-0.14.1+dfsg1/src/ufo-read-task.c ... /build/1st/ufo-filters-0.14.1+dfsg1/src/ufo-read-task.c: In function 'read_filenames': /build/1st/ufo-filters-0.14.1+dfsg1/src/ufo-read-task.c:159:32: error: 'GLOB_TILDE' undeclared (first use in this function); did you mean 'G_IS_FILE'? glob (pattern, GLOB_MARK | GLOB_TILDE, NULL, &filenames); ^~ G_IS_FILE /build/1st/ufo-filters-0.14.1+dfsg1/src/ufo-read-task.c:159:32: note: each undeclared identifier is reported only once for each function it appears in cd /build/1st/ufo-filters-0.14.1+dfsg1/obj-x86_64-linux-gnu/src && /usr/bin/cmake -E cmake_link_script CMakeFiles/ufofiltervolumerender.dir/link.txt --verbose=1 cd /build/1st/ufo-filters-0.14.1+dfsg1/obj-x86_64-linux-gnu/src && /usr/bin/cmake -E cmake_link_script CMakeFiles/ufofiltermedianfilter.dir/link.txt --verbose=1 make[3]: Leaving directory '/build/1st/ufo-filters-0.14.1+dfsg1/obj-x86_64-linux-gnu' src/CMakeFiles/ufofilterread.dir/build.make:65: recipe for target 'src/CMakeFiles/ufofilterread.dir/ufo-read-task.c.o' failed make[3]: *** [src/CMakeFiles/ufofilterread.dir/ufo-read-task.c.o] Error 1 GLOB_TILDE is a GNU extension, therefore it looks correct that it is (no longer) available with -std=c99. --- End Message --- --- Begin Message --- Source: ufo-filters Source-Version: 0.14.1+dfsg1-1.1 We believe that the bug you reported is fixed in the latest version of ufo-filters, 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 882...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated ufo-filters 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, 26 Dec 2017 23:03:53 +0200 Source: ufo-filters Binary: ufo-filters ufo-filters-doc ufo-filters-data Architecture: source Version: 0.14.1+dfsg1-1.1 Distribution: unstable Urgency: medium Maintainer: Picca Frédéric-Emmanuel Changed-By: Adrian Bunk Description: ufo-filters - Set of plugins for ufo-core - runtime ufo-filters-data - Library for high-performance, GPU-based computing - data ufo-filters-doc - Library for high-performance, GPU-based computing - documentation Closes: 882955 Changes: ufo-filters (0.14.1+dfsg1-1.1) unstable; urgency=medium . * Non-maintainer upload. * Add upstream fix for FTBFS with glibc 2.25. (Closes: #882955) Checksums-Sha1: 8d6235971b8629dbea1169952f8881d7dc530b54 2228 ufo-filters_0.14.1+dfsg1-1.1.dsc 6c3d6f515c77fa268077a71c0e73dccc5b526d5c 3544 ufo-filters_0.14.1+dfsg1-1.1.debian.tar.xz Checksums-Sha256: 33e47c78fa22927f935ab4f709e3f7ec29b5359108b4bccb5275e652e5dc6d85 2228 ufo-filters_0.14.1+dfsg1-1.1.dsc 480169121ac2eafc082a6dc85db8f7d8d90d4a759173c29bccb61611d71ed255 3544 ufo-filters_0.14.1+dfsg1-1.1.debian.tar.xz Files: 1ad25951f
Bug#867959: gallery-uploader: Uses deprecated python-gnomekeyring
Il giorno dom, 31/12/2017 alle 14.28 -0500, Jeremy Bicha ha scritto: > It is my understanding that it is Release > Critical for a package to recommend a removed library because it > keeps > the package from being a candidate for auto-removal when users > upgrade. Thanks Jeremy for opening this issue, given that gallery is dead upstream since 2014 ( http://galleryproject.org/time-to-hibernate ), I'm tempted to orphan this package (which I'm using no more). In fact, gallery-uploader (and its dependency python-galleryremote) never supported Gallery 3, and hence were officially obsolete since since way before. I'm going to send a message to the unofficial support group just to check if anybody complains. Pietro
Bug#867959: gallery-uploader: Uses deprecated python-gnomekeyring
On Sun, Dec 31, 2017 at 4:50 PM, Pietro Battiston wrote: > given that gallery is dead upstream since 2014 > ( http://galleryproject.org/time-to-hibernate ), I'm tempted to orphan > this package (which I'm using no more). > > In fact, gallery-uploader (and its dependency python-galleryremote) > never supported Gallery 3, and hence were officially obsolete since > since way before. In that case, could you consider requesting those two packages be removed instead of orphaning them? Thanks, Jeremy Bicha
Bug#883938:
Report
Bug#883938: Bug #883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51
On Mon, 11 Dec 2017 19:07:05 +0100 Karsten Heiken < hei...@luis.uni-hannover.de> wrote: > Bernhard Schmidt wrote: > >Can you check whether numa=off on the kernel command line fixes this as well? > > Indeed it does. Appending numa=off to the kernel command line fixes > the bug in my KVM virtual machines as well as my physical servers (at > least the ones I've tested so far). > > So this might be a viable workaround for the people that already > patched their systems. > > >
Processed: Raise severity of libgnome-keyring reverse depends bugs
Processing commands for cont...@bugs.debian.org: > severity 867939 serious Bug #867939 [src:smbnetfs] smbnetfs: Build-Depends on deprecated libgnome-keyring-dev Severity set to 'serious' from 'important' > End of message, stopping processing here. Please contact me if you need assistance. -- 867939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867939 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#853323: marked as done (atlas-cpp: ftbfs with GCC-7)
Your message dated Mon, 01 Jan 2018 00:18:53 + with message-id and subject line Bug#853323: fixed in atlas-cpp 0.6.3-4 has caused the Debian Bug report #853323, regarding atlas-cpp: ftbfs with GCC-7 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.) -- 853323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853323 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:atlas-cpp Version: 0.6.3-3 Severity: normal Tags: sid buster User: debian-...@lists.debian.org Usertags: ftbfs-gcc-7 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The severity of this report may be raised before the buster release. There is no need to fix this issue in time for the stretch release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc7-20170126/atlas-cpp_0.6.3-3_unstable_gcc7.log The last lines of the build log are at the end of this report. To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-7/porting_to.html [...] _ZNSt8_Rb_treeIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIS6_N5Atlas7Objects8SmartPtrINS9_8RootDataSt10_Select1stISD_ESt4lessIS6_ESaISD_EE24_M_get_insert_unique_posERS6_@Base 0.6.2 (optional=inline)_ZNSt8_Rb_treeIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIS6_N5Atlas7Objects8SmartPtrINS9_8RootDataSt10_Select1stISD_ESt4lessIS6_ESaISD_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorISD_ERS6_@Base 0.6.2 _ZNSt8_Rb_treeIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIS6_N5Atlas7Objects8SmartPtrINS9_8RootDataSt10_Select1stISD_ESt4lessIS6_ESaISD_EE8_M_eraseEPSt13_Rb_tree_nodeISD_E@Base 0.6.2 - (optional=templinst)_ZNSt8_Rb_treeIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIS6_S7_IPFN5Atlas7Objects8SmartPtrINS9_8RootDataEEERS6_iEiEESt10_Select1stISH_ESt4lessIS6_ESaISH_EE22_M_emplace_hint_uniqueIIRKSt21piecewise_construct_tSt5tupleIISD_EESS_IIESt17_Rb_tree_iteratorISH_ESt23_Rb_tree_const_iteratorISH_EDpOT_@Base 0.6.3 - (optional=templinst)_ZNSt8_Rb_treeIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIS6_S7_IPFN5Atlas7Objects8SmartPtrINS9_8RootDataEEERS6_iEiEESt10_Select1stISH_ESt4lessIS6_ESaISH_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJSD_EESS_IJESt17_Rb_tree_iteratorISH_ESt23_Rb_tree_const_iteratorISH_EDpOT_@Base 0.6.3 +#MISSING: 0.6.3-3# (optional=templinst)_ZNSt8_Rb_treeIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIS6_S7_IPFN5Atlas7Objects8SmartPtrINS9_8RootDataEEERS6_iEiEESt10_Select1stISH_ESt4lessIS6_ESaISH_EE22_M_emplace_hint_uniqueIIRKSt21piecewise_construct_tSt5tupleIISD_EESS_IIESt17_Rb_tree_iteratorISH_ESt23_Rb_tree_const_iteratorISH_EDpOT_@Base 0.6.3 +#MISSING: 0.6.3-3# (optional=templinst)_ZNSt8_Rb_treeIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIS6_S7_IPFN5Atlas7Objects8SmartPtrINS9_8RootDataEEERS6_iEiEESt10_Select1stISH_ESt4lessIS6_ESaISH_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJSD_EESS_IJESt17_Rb_tree_iteratorISH_ESt23_Rb_tree_const_iteratorISH_EDpOT_@Base 0.6.3 _ZNSt8_Rb_treeIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIS6_S7_IPFN5Atlas7Objects8SmartPtrINS9_8RootDataEEERS6_iEiEESt10_Select1stISH_ESt4lessIS6_ESaISH_EE24_M_get_insert_unique_posESD_@Base 0.6.2 (optional=inline)_ZNSt8_Rb_treeIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIS6_S7_IPFN5Atlas7Objects8SmartPtrINS9_8RootDataEEERS6_iEiEESt10_Select1stISH_ESt4lessIS6_ESaISH_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorISH_ESD_@Base 0.6.2 _ZNSt8_Rb_treeIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIS6_S7_IPFN5Atlas7Objects8SmartPtrINS9_8RootDataEEERS6_iEiEESt10_Select1stISH_ESt4lessIS6_ESaISH_EE4findESD_@Base 0.6.2 (optional=GCC6_added)_ZNSt8_Rb_treeIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIS
Bug#885965: FTBFS: Test: Run pylint on Python source code ... FAIL
Source: distro-info Version: 0.17 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi! I'm afraid your package fails to build with: Test: Run pylint on Python source code ... FAIL == FAIL: test_pylint (distro_info_test.test_pylint.PylintTestCase) Test: Run pylint on Python source code [...] (unused-variable)" is not false : pylint3 found errors: * Module distro_info_test.test_help W: 30, 0: Unused variable '__class__' (unused-variable) W: 30, 0: Unused variable '__class__' (unused-variable) * Module distro_info_test.test_pylint W: 26, 0: Unused variable '__class__' (unused-variable) * Module distro_info_test.test_flake8 W: 23, 0: Unused variable '__class__' (unused-variable) * Module distro_info_test.test_distro_info W: 25, 0: Unused variable '__class__' (unused-variable) W: 25, 0: Unused variable '__class__' (unused-variable) W: 25, 0: Unused variable '__class__' (unused-variable) Tested on armhf amd64. Log attached. Meow! -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: armhf (armv7l) Kernel: Linux 4.15.0-rc5-00024-g8358e4baaa66 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) distro-info_armhf.build Description: inode/symlink
Processed: tagging 884546
Processing commands for cont...@bugs.debian.org: > tags 884546 + pending Bug #884546 [src:sreview] sreview: FTBFS: missing B-D on perl modules Mojo::JSON Mojo::Pg Moose DBI Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 884546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884546 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#884546: marked as done (sreview: FTBFS: missing B-D on perl modules Mojo::JSON Mojo::Pg Moose DBI)
Your message dated Mon, 01 Jan 2018 03:04:02 + with message-id and subject line Bug#884546: fixed in sreview 0.2.3-1 has caused the Debian Bug report #884546, regarding sreview: FTBFS: missing B-D on perl modules Mojo::JSON Mojo::Pg Moose DBI 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.) -- 884546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884546 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sreview Version: 0.2.2-1 Severity: serious Justification: fails to build from source dh_auto_configure perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 -fdebug-prefix-map=/build/sreview-0.2.2=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" "LD=x86_64-linu x-gnu-gcc -g -O2 -fdebug-prefix-map=/build/sreview-0.2.2=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro" Warning: prerequisite Mojo::JSON 0 not found. Warning: prerequisite Mojo::Pg 0 not found. Warning: prerequisite Moose 0 not found. Checking if your kit is complete... Looks good Generating a Unix-style Makefile Writing Makefile for SReview Writing MYMETA.yml and MYMETA.json dh_auto_test make -j4 test TEST_VERBOSE=1 make[1]: Entering directory '/build/sreview-0.2.2' PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 'blib/arch')" t/*.t t/config.t . 1..9 ok 1 - use SReview::Config; ok 2 - loading nonexisting config produces a warning but succeeds ok 3 - An object of class 'SReview::Config' isa 'SReview::Config' ok 4 - loading an existing config file succeeds and prints no warning ok 5 - Config dump output is as expected ok 6 - Description of configuration value is as expected ok 7 - Trying to parse a syntactically invalid perl script produces an exception ok 8 - Trying to read a config variable that does not exist produces an exception ok 9 - Reading data that does not exist yet produces the default ok # Failed test 'use SReview::Video;' # at t/convert.t line 7. # Tried to use 'SReview::Video'. # Error: Can't locate Mojo/JSON.pm in @INC (you may need to install the Mojo::JSON module) (@INC contains: /build/sreview-0.2.2/blib/lib /build/sreview-0.2.2/blib/arch /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.26.1 /usr/local/share/perl/5.26.1 /usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at /build/sreview-0.2.2/blib/lib/SReview/Video.pm line 74. # BEGIN failed--compilation aborted at /build/sreview-0.2.2/blib/lib/SReview/Video.pm line 74. # Compilation failed in require at t/convert.t line 7. # BEGIN failed--compilation aborted at t/convert.t line 7. [...] and also Error: Can't locate Mojo/Pg.pm in @INC Error: Can't locate Moose.pm in @INC Can't locate DBI.pm in @INC Andreas sreview_0.2.2-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: sreview Source-Version: 0.2.3-1 We believe that the bug you reported is fixed in the latest version of sreview, 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 884...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Wouter Verhelst (supplier of updated sreview 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, 01 Jan 2018 03:16:05 +0100 Source: sreview Binary: sreview-master sreview-web sreview-encoder sreview-common sreview-detect Architecture: source all Version: 0.2.3-1 Distribution: experimental Urgency: medium Maintainer: Wouter Verhelst Changed-By: Wouter Verhelst Description: sreview-common - SReview -- common code sreview-detect - SReview input detection script sreview-encoder - SReview encoder code sreview-master - SReview components for master host sreview-web - SReview webinterface Closes: 884546 Changes: sreview (0.2.3-1) experimental; urgency=medium . * New upstream release (minor changes) * debian/control: add missing build-depends. Closes: #884546. Checksums-Sha1:
Bug#853391: marked as done (eris: ftbfs with GCC-7)
Your message dated Mon, 01 Jan 2018 03:49:02 + with message-id and subject line Bug#853391: fixed in eris 1.3.23-6 has caused the Debian Bug report #853391, regarding eris: ftbfs with GCC-7 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.) -- 853391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853391 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:eris Version: 1.3.23-5 Severity: normal Tags: sid buster User: debian-...@lists.debian.org Usertags: ftbfs-gcc-7 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The severity of this report may be raised before the buster release. There is no need to fix this issue in time for the stretch release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc7-20170126/eris_1.3.23-5_unstable_gcc7.log The last lines of the build log are at the end of this report. To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-7/porting_to.html [...] +#MISSING: 1.3.23-5# (optional=GCC6_removed)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6PersonEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE17_M_insert_unique_ISB_NSH_11_Alloc_nodeEEESt17_Rb_tree_iteratorISB_ESt23_Rb_tree_const_iteratorISB_EOT_RT0_@Base 1.3.23 +#MISSING: 1.3.23-5# (optional=GCC6_removed)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6PersonEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE22_M_emplace_hint_uniqueIIRKSt21piecewise_construct_tSt5tupleIIRS7_EESM_IIESt17_Rb_tree_iteratorISB_ESt23_Rb_tree_const_iteratorISB_EDpOT_@Base 1.3.23 +#MISSING: 1.3.23-5# (optional=GCC6_removed)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6PersonEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS7_EESM_IJESt17_Rb_tree_iteratorISB_ESt23_Rb_tree_const_iteratorISB_EDpOT_@Base 1.3.23 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6PersonEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE24_M_get_insert_unique_posERS7_@Base 1.3.23 (optional=certain_64b_arches)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6PersonEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorISB_ERS7_@Base 1.3.23 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6PersonEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE4findERS7_@Base 1.3.23 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6PersonEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE8_M_eraseEPSt13_Rb_tree_nodeISB_E@Base 1.3.23 (optional=certain_64b_arches)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6RouterEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE11equal_rangeERS7_@Base 1.3.23 - (optional=GCC6_removed)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6RouterEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE22_M_emplace_hint_uniqueIIRKSt21piecewise_construct_tSt5tupleIIRS7_EESM_IIESt17_Rb_tree_iteratorISB_ESt23_Rb_tree_const_iteratorISB_EDpOT_@Base 1.3.23 - (optional=GCC6_removed)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6RouterEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS7_EESM_IJESt17_Rb_tree_iteratorISB_ESt23_Rb_tree_const_iteratorISB_EDpOT_@Base 1.3.23 +#MISSING: 1.3.23-5# (optional=GCC6_removed)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6RouterEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE22_M_emplace_hint_uniqueIIRKSt21piecewise_construct_tSt5tupleIIRS7_EESM_IIESt17_Rb_tree_iteratorISB_ESt23_Rb_tree_const_iteratorISB_EDpOT_@Base 1.3.23 +#MISSING: 1.3.23
Processed: Fix typos in package assignments
Processing commands for cont...@bugs.debian.org: > reassign 885057 src:gnome-color-chooser 0.2.5-1.1 Bug #885057 [src:gnome-color-choser] gnome-color-chooser: Depends on old GNOME libraries Warning: Unknown package 'src:gnome-color-choser' Bug reassigned from package 'src:gnome-color-choser' to 'src:gnome-color-chooser'. No longer marked as found in versions gnome-color-choser/0.2.5-1.1. Ignoring request to alter fixed versions of bug #885057 to the same values previously set Bug #885057 [src:gnome-color-chooser] gnome-color-chooser: Depends on old GNOME libraries Marked as found in versions gnome-color-chooser/0.2.5-1.1. > reassign 885135 src:pygtk 2.24.0-5.1 Bug #885135 [src:pytgtk] pygtk: Unmaintained, use GObject Introspection instead Warning: Unknown package 'src:pytgtk' Bug reassigned from package 'src:pytgtk' to 'src:pygtk'. No longer marked as found in versions pytgtk/2.24.0-5.1. Ignoring request to alter fixed versions of bug #885135 to the same values previously set Bug #885135 [src:pygtk] pygtk: Unmaintained, use GObject Introspection instead Marked as found in versions pygtk/2.24.0-5.1. > reassign 885310 src:jumpnbump 1.60-2 Bug #885310 [src:gumpnbump] jumpnbump: Depends on unmaintained pygtk Warning: Unknown package 'src:gumpnbump' Bug reassigned from package 'src:gumpnbump' to 'src:jumpnbump'. No longer marked as found in versions gumpnbump/1.60-2. Ignoring request to alter fixed versions of bug #885310 to the same values previously set Bug #885310 [src:jumpnbump] jumpnbump: Depends on unmaintained pygtk Marked as found in versions jumpnbump/1.60-2. > reassign 885552 libgksu2-0 Bug #885552 [libgtksu2-0] libgksu: Don't release with buster Warning: Unknown package 'libgtksu2-0' Bug reassigned from package 'libgtksu2-0' to 'libgksu2-0'. Ignoring request to alter found versions of bug #885552 to the same values previously set Ignoring request to alter fixed versions of bug #885552 to the same values previously set > reassign 885637 src:stardict 3.0.1-9.3 Bug #885637 [src:startdict] stardict: Please drop Build-Depends on rarian-compat Warning: Unknown package 'src:startdict' Bug reassigned from package 'src:startdict' to 'src:stardict'. No longer marked as found in versions startdict/3.0.1-9.3. Ignoring request to alter fixed versions of bug #885637 to the same values previously set Bug #885637 [src:stardict] stardict: Please drop Build-Depends on rarian-compat Marked as found in versions stardict/3.0.1-9.3. > reassign 885815 fcitx-config-gtk2 0.4.9-1 Bug #885815 [fcitx-configtool-gtk2] fcitx-configtool-gtk2: Depends on libunique Warning: Unknown package 'fcitx-configtool-gtk2' Bug reassigned from package 'fcitx-configtool-gtk2' to 'fcitx-config-gtk2'. No longer marked as found in versions 0.4.9-1. Ignoring request to alter fixed versions of bug #885815 to the same values previously set Bug #885815 [fcitx-config-gtk2] fcitx-configtool-gtk2: Depends on libunique Marked as found in versions fcitx-configtool/0.4.9-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 885057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885057 885135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885135 885310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885310 885552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885552 885637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885637 885815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885815 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
