Processed: found 909554 in 1:13.14.1~dfsg-1
Processing commands for cont...@bugs.debian.org: > found 909554 1:13.14.1~dfsg-1 Bug #909554 [src:asterisk] asterisk: CVE-2018-17281: Remote crash vulnerability in HTTP websocket upgrade Marked as found in versions asterisk/1:13.14.1~dfsg-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 909554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909554 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909554: asterisk: CVE-2018-17281: Remote crash vulnerability in HTTP websocket upgrade
Source: asterisk Version: 1:13.22.0~dfsg-2 Severity: grave Tags: security upstream Hi, The following vulnerability was published for asterisk. CVE-2018-17281[0]: | There is a stack consumption vulnerability in the | res_http_websocket.so module of Asterisk through 13.23.0, 14.7.x | through 14.7.7, and 15.x through 15.6.0 and Certified Asterisk through | 13.21-cert2. It allows an attacker to crash Asterisk via a specially | crafted HTTP request to upgrade the connection to a websocket. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2018-17281 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-17281 [1] http://downloads.asterisk.org/pub/security/AST-2018-009.html [2] https://issues.asterisk.org/jira/browse/ASTERISK-28013 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Processed: bug 909549 is forwarded to https://github.com/p1otr/pypi2deb/pull/19
Processing commands for cont...@bugs.debian.org: > forwarded 909549 https://github.com/p1otr/pypi2deb/pull/19 Bug #909549 [pypi2deb] cannot download... None details from PyPI: ContentTypeError Set Bug forwarded-to-address to 'https://github.com/p1otr/pypi2deb/pull/19'. > thanks Stopping processing here. Please contact me if you need assistance. -- 909549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909549 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909551: qdirstat: Segfault immediately after choosing scan directory
Package: qdirstat Version: 1.4-2 Severity: grave Tags: a11y Justification: renders package unusable Dear Maintainer, * What led up to the situation? I installed qdirstat and launched it. It gave me a GTK(3?) prompt for choosing the directory I wish to scan. After choosing the directory and clicking "Open", it crashes. The message given when run from the terminal is "Segmentation fault". This happens when running with/without root privileges. Here is the log: 2018-09-24 22:36:10.956 [5046] Logger.cpp:143 openLogFile(): -- Log Start -- 2018-09-24 22:36:10.956 [5046] main.cpp:44 logVersion(): QDirStat-1.4 built with Qt 5.7.1 2018-09-24 22:36:11.070 [5046]DirTreeModel.cpp:549 sort(): Sorting by NameCol ascending 2018-09-24 22:36:11.070 [5046]TreemapView.cpp:124 setSelectionModel(): 2018-09-24 22:36:11.071 [5046] Cleanup.cpp:415 desktopSpecificApps(): Detected desktop "XFCE" 2018-09-24 22:36:11.071 [5046] Cleanup.cpp:468 desktopSpecificApps(): %filemanager => "thunar" 2018-09-24 22:36:11.071 [5046] Cleanup.cpp:468 desktopSpecificApps(): %terminal => "xfce4-terminal &" 2018-09-24 22:36:11.071 [5046]DebugHelpers.cpp:133 dumpExcludeRules(): 2018-09-24 22:36:11.071 [5046] MainWindow.cpp:818 toggleVerboseSelection(): Verbose selection is now off. Change this with Shift-F7. 2018-09-24 22:36:12.818 [5046] DirTree.cpp:95 startReading(): url: "/home/yankee" 2018-09-24 22:36:12.818 [5046] DirTree.cpp:98 startReading(): device: /dev/sda5 2018-09-24 22:36:12.818 [5046]DirReadJob.cpp:349 stat(): url: "/home/yankee" 2018-09-24 22:36:12.818 [5046]MainWindow.cpp:589 expandTreeToLevel(): Expanding tree to level 1 2018-09-24 22:36:12.835 [5046]DirReadJob.cpp:248 startReading(): Found cache file .qdirstat.cache.gz 2018-09-24 22:36:12.836 [5046]DirReadJob.cpp:260 startReading(): Using cache file /home/yankee/.qdirstat.cache.gz for /home/yankee 2018-09-24 22:36:12.836 [5046]DirReadJob.cpp:544 killAll(): NOT killing read job 2018-09-24 22:36:12.836 [5046]DirReadJob.cpp:278 startReading(): Deleting subtree /home/yankee 2018-09-24 22:36:12.836 [5046]DirTree.cpp:237 deletingChildNotify(): Deleting child /home/yankee 2018-09-24 22:36:12.836 [5046]DirTreeModel.cpp:918 deletingChild(): Deleting child /home/yankee 2018-09-24 22:36:12.836 [5046]DirTreeModel.cpp:926 deletingChild(): beginRemoveRows for /home/yankee row 0 2018-09-24 22:36:12.836 [5046]DirTreeModel.cpp:984 invalidatePersistent(): Invalidating * What exactly did you do (or not do) that was effective (or ineffective)? I attempted to start and use qdirstat, but it crashed when selecting a directory to scan. * What was the outcome of this action? It crashed. * What outcome did you expect instead? It should not crash. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (1000, 'testing'), (1000, 'stable'), (750, 'stable'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.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) LSM: AppArmor: enabled Versions of packages qdirstat depends on: ii libc62.27-6 ii libgcc1 1:8.2.0-7 ii libgl1 1.1.0-1 ii libgl1-mesa-glx 18.1.7-1 ii libqt5core5a 5.11.1+dfsg-8 ii libqt5gui5 5.11.1+dfsg-8 ii libqt5widgets5 5.11.1+dfsg-8 ii libstdc++6 8.2.0-7 ii liburi-perl 1.74-1 ii perl 5.26.2-7 ii zlib1g 1:1.2.11.dfsg-1 qdirstat recommends no packages. qdirstat suggests no packages. -- no debconf information
Bug#909549: cannot download... None details from PyPI: ContentTypeError
Control: tag -1 +patch +pending +upstream Workaround: PYPI_JSON_URL=https://pypi.org/pypi PYPI_XMLRPC_URL=https://pypi.org/pypi py2dsp internetarchive ... which confirms this is probably fixed upstream. A. -- C'est avec les pierres de la loi qu'on a bâti les prisons, et avec les briques de la religion, les bordels. - William Blake
Processed: Re: cannot download... None details from PyPI: ContentTypeError
Processing control commands: > tag -1 +patch +pending +upstream Bug #909549 [pypi2deb] cannot download... None details from PyPI: ContentTypeError Added tag(s) patch. Bug #909549 [pypi2deb] cannot download... None details from PyPI: ContentTypeError Added tag(s) pending. Bug #909549 [pypi2deb] cannot download... None details from PyPI: ContentTypeError Added tag(s) upstream. -- 909549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909549 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909549: cannot download... None details from PyPI: ContentTypeError
Package: pypi2deb
Version: 2.20180318
Severity: grave
File: /usr/share/pypi2deb/py2dsp
Running py2dsp on Debian buster completely fails in my tests right
now:
$ py2dsp internetarchive
W: py2dsp pypi:54: cannot download internetarchive None details from PyPI:
ContentTypeError("0, message='Attempt to decode JSON with unexpected mimetype:
text/html; charset=utf-8'",)
E: py2dsp py2dsp:57: invalid name: internetarchive
$ py2dsp jinja2
W: py2dsp pypi:54: cannot download jinja2 None details from PyPI:
ContentTypeError("0, message='Attempt to decode JSON with unexpected mimetype:
text/html; charset=utf-8'",)
E: py2dsp py2dsp:57: invalid name: jinja2
The justification for the severity is the "unusable by most or all
users".
I suspect this is because of changes on PyPI's side. In fact, I
believe this might be fixed upstream: the GitHub repo has a newer
version but it is not in Debian right now.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing'), (1, 'experimental'), (1, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages pypi2deb depends on:
ii build-essential 12.5
ii devscripts 2.18.4
ii dh-python3.20180723
ii python3 3.6.5-3
ii python3-aiohttp 3.1.3-1
ii python3-debian 0.1.33
ii python3-jinja2 2.10-1
ii python3-redis2.10.6-4
Versions of packages pypi2deb recommends:
ii python3-msgpack 0.5.6-1+b1
Versions of packages pypi2deb suggests:
pn cython
ii cython3 0.28.4-1
ii pypy6.0.0+dfsg-1
ii python-all-dev 2.7.15-3
pn python-nose
ii python-pytest 3.6.4-1
ii python-setuptools 40.2.0-1
pn python3-all-dev
pn python3-nose
ii python3-pytest 3.6.4-1
ii python3-setuptools 40.2.0-1
ii python3-sphinx 1.7.9-1
-- no debconf information
Bug#907764: marked as done (golang-github-hashicorp-raft: FTBFS in buster/sid (failing tests))
Your message dated Tue, 25 Sep 2018 02:37:11 + with message-id and subject line Bug#907764: fixed in golang-github-hashicorp-raft 1.0.0+git20180118.077966db-2 has caused the Debian Bug report #907764, regarding golang-github-hashicorp-raft: FTBFS in buster/sid (failing 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.) -- 907764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907764 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:golang-github-hashicorp-raft Version: 1.0.0+git20180118.077966db-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --buildsystem=golang --with=golang dh_update_autotools_config -i -O--buildsystem=golang dh_auto_configure -i -O--buildsystem=golang dh_auto_build -i -O--buildsystem=golang cd obj-x86_64-linux-gnu && go install -gcflags=\"-trimpath=/<>/golang-github-hashicorp-raft-1.0.0\+git20180118.077966db/obj-x86_64-linux-gnu/src\" -asmflags=\"-trimpath=/<>/golang-github-hashicorp-raft-1.0.0\+git20180118.077966db/obj-x86_64-linux-gnu/src\" -v -p 1 github.com/hashicorp/raft github.com/hashicorp/raft/bench github.com/hashicorp/golang-lru/simplelru github.com/hashicorp/go-immutable-radix github.com/armon/go-metrics github.com/hashicorp/go-msgpack/codec github.com/hashicorp/raft github.com/hashicorp/raft/bench dh_auto_test -i -O--buildsystem=golang cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 github.com/hashicorp/raft github.com/hashicorp/raft/bench === RUN TestCommitment_setVoters --- PASS: TestCommitment_setVoters (0.00s) === RUN TestCommitment_match_max --- PASS: TestCommitment_match_max (0.00s) === RUN TestCommitment_match_nonVoting --- PASS: TestCommitment_match_nonVoting (0.00s) === RUN TestCommitment_recalculate --- PASS: TestCommitment_recalculate (0.00s) === RUN TestCommitment_recalculate_startIndex --- PASS: TestCommitment_recalculate_startIndex (0.00s) === RUN TestCommitment_noVoterSanity --- PASS: TestCommitment_noVoterSanity (0.00s) === RUN TestCommitment_singleVoter --- PASS: TestCommitment_singleVoter (0.00s) === RUN TestConfiguration_Configuration_Clone --- PASS: TestConfiguration_Configuration_Clone (0.00s) === RUN TestConfiguration_configurations_Clone --- PASS: TestConfiguration_configurations_Clone (0.00s) === RUN TestConfiguration_hasVote --- PASS: TestConfiguration_hasVote (0.00s) === RUN TestConfiguration_checkConfiguration --- PASS: TestConfiguration_checkConfiguration (0.00s) === RUN TestConfiguration_nextConfiguration_table --- PASS: TestConfiguration_nextConfiguration_table (0.00s) === RUN TestConfiguration_nextConfiguration_prevIndex --- PASS: TestConfiguration_nextConfiguration_prevIndex (0.00s) === RUN TestConfiguration_nextConfiguration_checkConfiguration --- PASS: TestConfiguration_nextConfiguration_checkConfiguration (0.00s) === RUN TestConfiguration_encodeDecodePeers --- PASS: TestConfiguration_encodeDecodePeers (0.00s) === RUN TestConfiguration_encodeDecodeConfiguration --- PASS: TestConfiguration_encodeDecodeConfiguration (0.00s) === RUN TestDiscardSnapshotStoreImpl --- PASS: TestDiscardSnapshotStoreImpl (0.00s) === RUN TestDiscardSnapshotSinkImpl --- PASS: TestDiscardSnapshotSinkImpl (0.00s) === RUN TestFileSnapshotStoreImpl --- PASS: TestFileSnapshotStoreImpl (0.00s) === RUN TestFileSnapshotSinkImpl --- PASS: TestFileSnapshotSinkImpl (0.00s) === RUN TestFileSS_CreateSnapshotMissingParentDir --- PASS: TestFileSS_CreateSnapshotMissingParentDir (0.14s) raft_test.go:101: 21:34:33.261773 [INFO] snapshot: Creating new snapshot at /tmp/raft068757217/raft335529164/snapshots/3-10-1533504873261.tmp === RUN TestFileSS_CreateSnapshot --- PASS: TestFileSS_CreateSnapshot (0.50s) raft_test.go:101: 21:34:33.401289 [INFO] snapshot: Creating new snapshot at /tmp/raft997309883/snapshots/3-10-1533504873401.tmp raft_test.go:101: 21:34:33.534238 [WARN] snapshot: Found temporary snapshot: 3-10-1533504873401.tmp === RUN TestFileSS_CancelSnapshot --- PASS: TestFileSS_CancelSnapshot (0.13s) raft_test.go:101: 21:34:33.899206 [INFO] snapshot: Creating new snapshot at /tmp/raft437327838/snapshots/3-10-1533504873899.tmp === RUN TestFileSS_Retention --- PASS: TestFileSS_Retention (2.67s) raft_test.go:101: 21:34:34.032449 [INFO] snapshot: Creating new snapshot at /tmp/raft011354021/snapshots/3-10-1533504874032.tmp
Processed: Re: [Pkg-rust-maintainers] Bug#909482: rustc: FTBFS on mips64el on buildds: timeout
Processing control commands: > reassign -1 src:rustc Bug #909482 [rustc] rustc: FTBFS on mips64el on buildds: timeout Bug reassigned from package 'rustc' to 'src:rustc'. No longer marked as found in versions rustc/1.28.0+dfsg1-2. Ignoring request to alter fixed versions of bug #909482 to the same values previously set > forcemerge 881845 -1 Bug #881845 [src:rustc] rustc: FTBFS on mips*: test failures Bug #909482 [src:rustc] rustc: FTBFS on mips64el on buildds: timeout Set Bug forwarded-to-address to 'https://bugs.llvm.org/show_bug.cgi?id=32020'. Severity set to 'important' from 'serious' Marked as found in versions rustc/1.21.0+dfsg1-3. Added tag(s) confirmed and upstream. Bug #881845 [src:rustc] rustc: FTBFS on mips*: test failures Added tag(s) ftbfs. Merged 881845 909482 -- 881845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881845 909482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909482 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909482: [Pkg-rust-maintainers] Bug#909482: rustc: FTBFS on mips64el on buildds: timeout
Control: reassign -1 src:rustc Control: forcemerge 881845 -1 Ximin Luo: > Control: forcemerge 881845 -1 > > Yes, we're aware, see the discussion in #881845. The issue is some mips CPUs > are (allegedly) buggy and so a porter with access to the allegedly non-buggy > ones have been doing manual builds. > > I let this situation continue but would also be happy to just RM rustc > mips64el for the time being, to avoid blocking migration to Debian Testing to > the other bugs. > > If nobody builds mips64el in the next few days I will go ahead and request RM > by FTP masters. > > X > > Ivo De Decker: >> package: rustc >> version: 1.28.0+dfsg1-2 >> severity: serious >> tags: ftbfs >> >> Hi, >> >> The builds of rustc in sid on mips64el consistently fail on the buildds: >> >> https://buildd.debian.org/status/logs.php?pkg=rustc=mips64el >> >> Most of the fail with >> >> "Build killed with signal TERM after 150 minutes of inactivity" >> >> If the build is actually still going at that point, it should produce output >> to avoid being killed. >> >> The builds that are in the archive seem to be manual builds that were >> uploaded. >> >> Cheers, >> >> Ivo >> -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git
Processed: summary 907764 Disabled unreliable test
Processing commands for cont...@bugs.debian.org: > summary 907764 Disabled unreliable test Summary recorded from message bug 907764 message > thanks Stopping processing here. Please contact me if you need assistance. -- 907764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907764 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907764: Bug #907764 in golang-github-hashicorp-raft marked as pending
Control: tag -1 pending Hello, Bug #907764 in golang-github-hashicorp-raft reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at: https://salsa.debian.org/go-team/packages/golang-github-hashicorp-raft/commit/fed8268eb0447defaebb69b1c52a304ed75dfbac New patch to disable unreliable test (Closes: #907764). (this message was generated automatically) -- Greetings https://bugs.debian.org/907764
Processed: Bug #907764 in golang-github-hashicorp-raft marked as pending
Processing control commands: > tag -1 pending Bug #907764 [src:golang-github-hashicorp-raft] golang-github-hashicorp-raft: FTBFS in buster/sid (failing tests) Added tag(s) pending. -- 907764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907764 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#905977: kea-ctrl-agent: missing dependency on python3
Thanks Adrian, I have made the changes to fix this, but I am running into issues building the package. The odd part is the errors seem unrelated to the changes. I just wanted to let you know I am working on it. On Sun, Aug 12, 2018 at 1:58 PM, Adrian Bunk wrote: > Package: kea-ctrl-agent > Version: 1.4.0.P1-3 > Severity: serious > > kea-ctrl-agent lacks a python3 dependency > for /usr/sbin/kea-shell > > This can be fixed by adding dh-python to the build dependencies > plus python3 to the "dh $@ --with" in debian/rules. >
Processed: tagging 908487
Processing commands for cont...@bugs.debian.org: > tags 908487 = ftbfs fixed-upstream pending Bug #908487 [src:mozjs60] mozjs60: FTBFS on mips: error: static assertion failed: atomics supported up to pointer size only Warning: Unknown package 'src:mozjs60' Added tag(s) pending; removed tag(s) help. Warning: Unknown package 'src:mozjs60' > thanks Stopping processing here. Please contact me if you need assistance. -- 908487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908487 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909542: opam: FTBFS when built with dpkg-buildpackage -A
Package: src:opam
Version: 2.0.0-4
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules binary-indep
dh binary-indep --with ocaml
dh_testdir -i
dh_update_autotools_config -i
dh_autoreconf -i
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*'
-o -path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a -type f -exec
md5sum {} + -o -type l -printf "symlink %p
" > debian/autoreconf.before
grep -q ^XDT_ configure.ac
autoreconf -f -i
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*'
-o -path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a -type f -exec
md5sum {} + -o -type l -printf "symlink %p
" > debian/autoreconf.after
dh_ocamlinit -i
touch ocamlinit-stamp
debian/rules override_dh_auto_configure
[... snipped ...]
dh_perl -i
dh_usrlocal -i
dh_link -i
dh_installwm -i
dh_installxfonts -i
dh_strip_nondeterminism -i
rm -f debian/opam-docs.debhelper.log
debian/rules override_dh_compress
make[1]: Entering directory '/<>'
dh_compress -X.pdf
cd debian/opam-docs
chmod a-x usr/share/doc/opam-docs/README.md
usr/share/doc/opam-docs/changelog usr/share/doc/opam-docs/changelog.Debian
usr/share/man/man1/opam-admin-cache.1 usr/share/man/man1/opam-admin-filter.1
usr/share/man/man1/opam-admin-index.1 usr/share/man/man1/opam-admin-lint.1
usr/share/man/man1/opam-admin-list.1 usr/share/man/man1/opam-admin-upgrade.1
usr/share/man/man1/opam-admin.1 usr/share/man/man1/opam-clean.1
usr/share/man/man1/opam-config.1 usr/share/man/man1/opam-env.1
usr/share/man/man1/opam-exec.1 usr/share/man/man1/opam-help.1
usr/share/man/man1/opam-info.1 usr/share/man/man1/opam-init.1
usr/share/man/man1/opam-install.1 usr/share/man/man1/opam-lint.1
usr/share/man/man1/opam-list.1 usr/share/man/man1/opam-pin.1
usr/share/man/man1/opam-reinstall.1 usr/share/man/man1/opam-remote.1
usr/share/man/man1/opam-remove.1 usr/share/man/man1/opam-repository.1
usr/share/man/man1/opam-search.1 usr/share/man/man1/opam-show.1
usr/share/man/man1/opam-source.1 usr/share/man/man1/opam-switch.1 usr
/share/man/man1/opam-uninstall.1 usr/share/man/man1/opam-unpin.1
usr/share/man/man1/opam-update.1 usr/share/man/man1/opam-upgrade.1
usr/share/man/man1/opam-var.1 usr/share/man/man1/opam.1
gzip -9nf usr/share/doc/opam-docs/README.md
usr/share/doc/opam-docs/changelog usr/share/doc/opam-docs/changelog.Debian
usr/share/man/man1/opam-admin-cache.1 usr/share/man/man1/opam-admin-filter.1
usr/share/man/man1/opam-admin-index.1 usr/share/man/man1/opam-admin-lint.1
usr/share/man/man1/opam-admin-list.1 usr/share/man/man1/opam-admin-upgrade.1
usr/share/man/man1/opam-admin.1 usr/share/man/man1/opam-clean.1
usr/share/man/man1/opam-config.1 usr/share/man/man1/opam-env.1
usr/share/man/man1/opam-exec.1 usr/share/man/man1/opam-help.1
usr/share/man/man1/opam-info.1 usr/share/man/man1/opam-init.1
usr/share/man/man1/opam-install.1 usr/share/man/man1/opam-lint.1
usr/share/man/man1/opam-list.1 usr/share/man/man1/opam-pin.1
usr/share/man/man1/opam-reinstall.1 usr/share/man/man1/opam-remote.1
usr/share/man/man1/opam-remove.1 usr/share/man/man1/opam-repository.1
usr/share/man/man1/opam-search.1 usr/share/man/man1/opam-show.1
usr/share/man/man1/opam-source.1 usr/share/man/man1/opam-switch.1 usr
/share/man/man1/opam-uninstall.1 usr/share/man/man1/opam-unpin.1
usr/share/man/man1/opam-update.1 usr/share/man/man1/opam-upgrade.1
usr/share/man/man1/opam-var.1 usr/share/man/man1/opam.1
cd '/<>'
make[1]: Leaving directory '/<>'
dh_fixperms -i
find debian/opam-docs ! -type l -a -true -a -true -print0 2>/dev/null |
xargs -0r chmod go=rX,u+rw,a-s
find debian/opam-docs/usr/share/doc -type f -a -true -a ! -regex
'debian/opam-docs/usr/share/doc/[^/]*/examples/.*' -print0 2>/dev/null | xargs
-0r chmod 0644
find debian/opam-docs/usr/share/doc -type d -a -true -a -true -print0
2>/dev/null | xargs -0r chmod 0755
find debian/opam-docs/usr/share/man -type f -a -true -a -true -print0
2>/dev/null | xargs -0r chmod 0644
find debian/opam-docs -type f \( -name '*.so.*' -o -name '*.so' -o
-name '*.la' -o -name '*.a' -o -name '*.js' -o -name '*.css' -o -name '*.scss'
-o -name '*.sass' -o -name '*.jpeg' -o -name '*.jpg' -o -name '*.png' -o -name
'*.gif' -o -name '*.cmxs' \) -a -true -a -true -print0 2>/dev/null | xargs -0r
chmod 0644
rm -f debian/opam-docs.debhelper.log
debian/rules override_dh_missing
make[1]: Entering directory '/<>'
dh_missing --fail-missing
dh_missing: usr/doc/opam-installer/CHANGES exists in debian/tmp but is not
installed to anywhere
dh_missing: usr/doc/opam-installer/README.md exists in debian/tmp but is not
installed to anywhere
dh_missing: usr/doc/opam-installer/LICENSE exists in
Bug#840569: [Pkg-mozext-maintainers] Bug#840569: xul-ext-nosquint is dead, long live nosquint
On Wed, Oct 12, 2016 at 11:23:32AM -1000, David Prévot wrote: > Control: severity -1 serious > > Le 12/10/2016 à 10:35, shirish शिरीष a écrit : > > Source: nosquint > > Version: 2.1.9-4 > > Severity: important > > > > Dear Maintainer, > > > > Nosquint is dead, please remove it > > Then let’s use a proper RC-severity so it gets removed from Stretch. If > someone wants to follow up and package something equivalent instead, > please step up before the freeze (i.e., soon). Noone followed up and packaged nosquint-plus for almost two years, let's go ahead with removing it? Cheers, Moritz
Bug#906887: xul-ext-automatic-save-folder no longer works with firefox-esr 60
On Tue, Aug 21, 2018 at 11:02:49PM +0300, Adrian Bunk wrote: > Package: xul-ext-automatic-save-folder > Version: 1.0.5~20140831-4 > Severity: serious > > XUL addons are no longer supported. Per http://asf.mangaheart.org/closed.php the project is dead and won't get fixed for Firefox > 57, so let's remove it from the archive. Cheers, Moritz
Bug#907997: emacs-lucid: trying to overwrite '/usr/share/emacs/25.2/etc/DOC', which is also in package emacs25 25.2+1-6+b2
Package: emacs-common Followup-For: Bug #907997 FYI Preparing to unpack .../emacs-common_1%3a25.2+1-11_all.deb ... Unpacking emacs-common (1:25.2+1-11) ... dpkg: error processing archive /var/cache/apt/archives/emacs-common_1%3a25.2+1-11_all.deb (--unpack): trying to overwrite '/usr/share/emacs/25.2/etc/AUTHORS', which is also in package emacs25-common 25.2+1-6 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Selecting previously unselected package emacs-bin-common. Preparing to unpack .../emacs-bin-common_1%3a25.2+1-11_amd64.deb ... Unpacking emacs-bin-common (1:25.2+1-11) ... dpkg: error processing archive /var/cache/apt/archives/emacs-bin-common_1%3a25.2+1-11_amd64.deb (--unpack): trying to overwrite '/usr/lib/emacs/25.2/x86_64-linux-gnu/hexl', which is also in package emacs25-bin-common 25.2+1-6+b2 Selecting previously unselected package libmagickwand-6.q16-6:amd64. Preparing to unpack .../libmagickwand-6.q16-6_8%3a6.9.10.8+dfsg-1_amd64.deb ... Unpacking libmagickwand-6.q16-6:amd64 (8:6.9.10.8+dfsg-1) ... Selecting previously unselected package emacs-gtk. Preparing to unpack .../emacs-gtk_1%3a25.2+1-11_amd64.deb ... Unpacking emacs-gtk (1:25.2+1-11) ... dpkg: error processing archive /var/cache/apt/archives/emacs-gtk_1%3a25.2+1-11_amd64.deb (--unpack): trying to overwrite '/usr/share/emacs/25.2/etc/DOC', which is also in package emacs25 25.2+1-6+b2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../emacs23_1%3a25.2+1-11_all.deb ... Remove latex-cjk-thai for emacs23 remove/latex-cjk-thai: purging byte-compiled files for emacs23 Remove latex-cjk-common for emacs23 remove/latex-cjk-common: purging byte-compiled files for emacs23 Remove systemtap-common for emacs23 remove/systemtap-common: Purging byte-compiled files for emacs23 Remove emacsen-common for emacs23 emacsen-common: Handling removal of emacsen flavor emacs23 Unpacking emacs23 (1:25.2+1-11) over (23.4+1-4.1+b1) ... Errors were encountered while processing: /var/cache/apt/archives/emacs-common_1%3a25.2+1-11_all.deb /var/cache/apt/archives/emacs-bin-common_1%3a25.2+1-11_amd64.deb /var/cache/apt/archives/emacs-gtk_1%3a25.2+1-11_amd64.deb [ Rootkit Hunter version 1.4.6 ] File updated: searched for 182 files, found 158 E: Sub-process /usr/bin/dpkg returned an error code (1) -- 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.16.0-2-amd64 (SMP w/12 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages emacs-common depends on: ii emacsen-common 2.0.8 it install-info6.5.0.dfsg.1-4 Versions of packages emacs-common recommends: pn emacs-el Versions of packages emacs-common suggests: pn emacs-common-non-dfsg iu ncurses-term 6.1+20180714-1
Bug#909076: ghostscript: ps2ascii crashes: Error: /typecheck in --.bind--
Hi FTR, I tried to bisect the issue, by using commits between 9.20 and 9.21 upstream and applying on top each fb713b3818b52d8a6cf62c951eba2e1795ff9624 . Due to a possibly unrelated bug, some of the commits cause "empty" outputs, so I had to skip those all. The resulting git bisect is git bisect start '--term-old' 'broken' '--term-new' 'fixed' # broken: [937efa62c23c2c79c7487895421041896e8c14b7] Fix previous JPEG commit. git bisect broken 937efa62c23c2c79c7487895421041896e8c14b7 # fixed: [f80288c8a4b9c9abfc0fa3ccce3b6d169baa59ff] Dates for 9.21 release git bisect fixed f80288c8a4b9c9abfc0fa3ccce3b6d169baa59ff # fixed: [4d07b45685976bd38e5cec8062b3a61d2ada5575] Hide more JPEG entries. git bisect fixed 4d07b45685976bd38e5cec8062b3a61d2ada5575 # fixed: [8894abf2985a58900e778957f93151b6cec1c17a] Address a segfault and error introduced in 4b3be09 git bisect fixed 8894abf2985a58900e778957f93151b6cec1c17a # skip: [513d6fd7ddfc5a59fbf8bf6ce72eda6c97fea9f8] remove a bunch of now unused variables from the earlier shading code commit. git bisect skip 513d6fd7ddfc5a59fbf8bf6ce72eda6c97fea9f8 # skip: [336c69b8be32c7193909a7f25b1a073b0ac2d92f] PDF Interpreter - have warning messages respect QUIET git bisect skip 336c69b8be32c7193909a7f25b1a073b0ac2d92f # skip: [c9f7be4f4de8e98df9d34ff8e4a7f781c0a33899] Bring master up to date with 9.20 release branch git bisect skip c9f7be4f4de8e98df9d34ff8e4a7f781c0a33899 # skip: [f42898997f249062f5da8fcf9c3a46cd6443fb39] PDF interpreter - skip 'R' operator in invalid context git bisect skip f42898997f249062f5da8fcf9c3a46cd6443fb39 # skip: [2f6ddae95676585717159445001fda2ebb00db8d] Squash compiler warning. git bisect skip 2f6ddae95676585717159445001fda2ebb00db8d # skip: [b7ea690782c306241ed94fa3bdaf296f6bcc455f] Bug 697366 git bisect skip b7ea690782c306241ed94fa3bdaf296f6bcc455f # skip: [0e2523b9dae517f91bd7da78323e5207d099a10e] Fix expat build on Windows git bisect skip 0e2523b9dae517f91bd7da78323e5207d099a10e # skip: [2f3679b53632c5b7b9e9a416311ae82f36645fc9] Bug 697220(2): Fix returning execstackoverflow git bisect skip 2f3679b53632c5b7b9e9a416311ae82f36645fc9 # skip: [d4d8b7d51f79b47d21d3c82fe652a79e1f890df5] Fix bug 697323, Segfault after pattern with transparency. git bisect skip d4d8b7d51f79b47d21d3c82fe652a79e1f890df5 # skip: [cb8022f3e15b761adf4bbc78621cf0699f69e21c] Fix SEGV caused by previous commit. git bisect skip cb8022f3e15b761adf4bbc78621cf0699f69e21c # skip: [0f6067d2531298060392d0e25fa759d320e03021] ps2write - don't try to alter /pagesave when modifying media size git bisect skip 0f6067d2531298060392d0e25fa759d320e03021 # skip: [6655712ee1d0bf2a7818044613bbed226b7abddd] Update freetype to 2.7.0 git bisect skip 6655712ee1d0bf2a7818044613bbed226b7abddd # skip: [8cefc79359e14fdb8b967697bba33b754e83bcad] pdfwrite - fix calculation of a bounding box git bisect skip 8cefc79359e14fdb8b967697bba33b754e83bcad # skip: [45268652fcddf2031f5edb592bc61e53d9ac4f5b] Set GX_DOWNSCALER_PARAMS_DEFAULTS in jpeg git bisect skip 45268652fcddf2031f5edb592bc61e53d9ac4f5b # skip: [8a26fa67398970f357e1292310ef20556a8e5d96] Fix 'corner' radial gradient case. git bisect skip 8a26fa67398970f357e1292310ef20556a8e5d96 # skip: [99c6a18eb430a9091c79369b2bdd2952d481c7d5] Document use of string for subsituted CIDFont name git bisect skip 99c6a18eb430a9091c79369b2bdd2952d481c7d5 # skip: [90b7603c1afb3ad79a6a0dfee97560b1c3565379] PCL - fix pdfmark parsing for PUTFILE git bisect skip 90b7603c1afb3ad79a6a0dfee97560b1c3565379 # skip: [23dc144b3c3d3dbafd83dca7b9c09e6977b774d6] Update lcms2 to 2.8 git bisect skip 23dc144b3c3d3dbafd83dca7b9c09e6977b774d6 # skip: [a46245139253b2ec607fcd06c549a6293d05a3a8] Fix a bug in device subclassing git bisect skip a46245139253b2ec607fcd06c549a6293d05a3a8 # skip: [0726780b28920045ee6f344a34bc5e8565bc4ed5] "cups" output device: When creating PWG Raster output, always output the bitmap of the full page, ignoring any unprintable margins suggested by the PPD file. git bisect skip 0726780b28920045ee6f344a34bc5e8565bc4ed5 # skip: [21b582ca561214aa9c5b9c8987a1c0cdce43ace6] Add expat endian settings. git bisect skip 21b582ca561214aa9c5b9c8987a1c0cdce43ace6 # skip: [71629c04758788b238d6ff3537d9708f430a4db7] Tweak to clip device nesting. git bisect skip 71629c04758788b238d6ff3537d9708f430a4db7 # skip: [99e9ca317adbd28b5faf3e9eda4c63d636478f43] Bug 697045: Skip over broken tile data rather than aborting. git bisect skip 99e9ca317adbd28b5faf3e9eda4c63d636478f43 # skip: [1eebbfa373d295bdd2bad88aaef1edc368450568] Bug 697231: Introduce caching to use of clipping paths. git bisect skip 1eebbfa373d295bdd2bad88aaef1edc368450568 # broken: [ed425fcd620837bf63a18a3ee2a2202fa91b1207] Add -sPostRenderICCProfile support to tiffsep git bisect broken ed425fcd620837bf63a18a3ee2a2202fa91b1207 # skip: [8dcec8cc076a0cf8350ca7a6ec1d3136812e2a24] Bug 697186: Workaround JPEG lib bug. git bisect skip 8dcec8cc076a0cf8350ca7a6ec1d3136812e2a24 # fixed:
Bug#906841: xul-ext-firebug no longer works with firefox-esr 60
On Sat, Sep 08, 2018 at 03:14:50PM +0800, Paul Wise wrote: > On Tue, 21 Aug 2018 20:01:17 +0300 Adrian Bunk wrote: > > > Package: xul-ext-firebug > > > > XUL addons are no longer supported. > > The native Firefox developer tools were written to replace Firebug > so I think this package can just be removed from Debian. > > https://getfirebug.com/ > https://developer.mozilla.org/en-US/docs/Tools/Migrating_from_Firebug I've filed a removal bug. Cheers, Moritz
Bug#908495: marked as done (entangle FTBFS with gobject-introspection 1.58.0-1)
Your message dated Mon, 24 Sep 2018 20:43:38 + with message-id and subject line Bug#908495: fixed in entangle 1.0-1 has caused the Debian Bug report #908495, regarding entangle FTBFS with gobject-introspection 1.58.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.) -- 908495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908495 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: entangle Version: 0.7.2-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/entangle.html ... /usr/bin/g-ir-scanner -v --warn-all \ --namespace Entangle \ --nsversion 0.1 \ --include GObject-2.0 \ --include Gtk-3.0 \ --include Peas-1.0 \ --include Gst-1.0 \ --include GstBase-1.0 \ --include GExiv2-0.10 \ --program=./entangle \ --add-include-path=. \ --add-include-path=. \ --output Entangle-0.1.gir \ -I./backend \ -I./frontend \ -I./backend \ -I./frontend \ --verbose \ --pkg=glib-2.0 \ --pkg=gthread-2.0 \ --pkg=gdk-pixbuf-2.0 \ --pkg=gobject-2.0 \ --pkg=gtk+-3.0 \ --pkg=libgphoto2 \ --pkg=libpeas-1.0 \ --pkg=gexiv2 \ --pkg=gstreamer-1.0 \ ./backend/entangle-media.h ./backend/entangle-media.c ./backend/entangle-image.h ./backend/entangle-image.c ./backend/entangle-video.h ./backend/entangle-video.c ./backend/entangle-session.h ./backend/entangle-session.c ./backend/entangle-camera.h ./backend/entangle-camera.c ./backend/entangle-camera-automata.h ./backend/entangle-camera-automata.c ./backend/entangle-camera-file.h ./backend/entangle-camera-file.c ./backend/entangle-camera-list.h ./backend/entangle-camera-list.c ./backend/entangle-colour-profile.h ./backend/entangle-colour-profile.c ./backend/entangle-control.h ./backend/entangle-control.c ./backend/entangle-control-button.h ./backend/entangle-control-button.c ./backend/entangle-control-choice.h ./backend/entangle-control-choice.c ./backend/entangle-control-date.h ./backend/entangle-control-date.c ./backend/entangle-control-group.h ./backend/entangle-control-group.c ./backend/entangle-control-range.h ./backend/entangle-control-range.c ./backend/entangle-control-text.h ./backend/entangle-control-text.c ./backend/entangle-control-toggle.h ./backend/entangle-control-toggle.c ./backend/entangle-debug.h ./backend/entangle-debug.c ./backend/entangle-device-manager.h ./backend/entangle-device-manager.c ./backend/entangle-pixbuf.h ./backend/entangle-pixbuf.c ./backend/entangle-image-loader.h ./backend/entangle-image-loader.c ./backend/entangle-pixbuf-loader.h ./backend/entangle-pixbuf-loader.c ./backend/entangle-progress.h ./backend/entangle-progress.c ./backend/entangle-thumbnail-loader.h ./backend/entangle-thumbnail-loader.c \ ./backend/entangle-camera-enums.h ./backend/entangle-camera-enums.c ./backend/entangle-colour-profile-enums.h ./backend/entangle-colour-profile-enums.c \ ./frontend/entangle-window.h ./frontend/entangle-window.c ./frontend/entangle-application.h ./frontend/entangle-application.c ./frontend/entangle-camera-support.h ./frontend/entangle-camera-support.c ./frontend/entangle-camera-manager.h ./frontend/entangle-camera-manager.c ./frontend/entangle-camera-picker.h ./frontend/entangle-camera-picker.c ./frontend/entangle-camera-preferences.h ./frontend/entangle-camera-preferences.c ./frontend/entangle-control-panel.h ./frontend/entangle-control-panel.c ./frontend/entangle-dpms.h ./frontend/entangle-dpms.c ./frontend/entangle-help-about.h ./frontend/entangle-help-about.c ./frontend/entangle-image-display.h ./frontend/entangle-image-display.c ./frontend/entangle-image-histogram.h ./frontend/entangle-image-histogram.c ./frontend/entangle-media-popup.h ./frontend/entangle-media-popup.c ./frontend/entangle-media-statusbar.h ./frontend/entangle-media-statusbar.c ./frontend/entangle-preferences.h ./frontend/entangle-preferences.c ./frontend/entangle-preferences-display.h ./frontend/entangle-preferences-display.c ./frontend/entangle-script.h ./frontend/entangle-script.c ./frontend/entangle-script-simple.h ./frontend/entangle-script-simple.c ./frontend/entangle-script-config.h ./frontend/entangle-script-config.c ./frontend/entangle-session-browser.h
Bug#909536: mozjs60: FTBFS on s390x: around 80% of tests crash
Source: mozjs60 Version: 60.2.1-1 Severity: serious Tags: ftbfs help X-Debbugs-Cc: debian-s...@lists.debian.org User: debian-s...@lists.debian.org Usertags: s390x Most of the test cases provided with mozjs60 crash: grep '^TEST-' s390x.log | cut -d' ' -f1 | sort | uniq -c 1714 TEST-KNOWN-FAIL 6923 TEST-PASS 28635 TEST-UNEXPECTED-FAIL See https://buildd.debian.org/status/fetch.php?pkg=mozjs60=s390x=60.2.1-1=1537442189=0 for a full log. You'll see that the result of many tests is "rc = -11" (I think that's signal 11, or SIGSEGV). After reproducing this on the porterbox zelenka, a backtrace from one such crash is below. The js interpreter seems to be crashing during a garbage collection pass triggered during process shutdown. This is a regression since mozjs52, in which only a few tests failed (#878286). I'm willing to ignore a few isolated test failures, but when 80% of the tests fail, I don't think we can be confident that mozjs60 is at all usable on s390x. We can't upgrade gjs to a version that uses mozjs60 until either this is fixed somehow, or gjs and its dependencies (notably GNOME Shell) are removed from s390x. The architecture-specific removal seems a more likely short term solution; if this is done I'll downgrade this bug to important. Thanks, smcv % gdb /home/smcv/mozjs60/debian/build/dist/bin/js js/src/tests/core Core was generated by `/home/smcv/mozjs60/debian/build/dist/bin/js -f shell.js -f test262/shell.js -f'. Program terminated with signal SIGSEGV, Segmentation fault. #0 ContextToPC (context=0x3fff7e7d740) at ./js/src/wasm/WasmSignalHandlers.cpp:452 452 MOZ_CRASH(); [Current thread is 1 (Thread 0x3ffad574750 (LWP 63693))] Loading JavaScript value pretty-printers; see js/src/gdb/README. If they cause trouble, type: disable pretty-printer .* SpiderMonkey SpiderMonkey unwinder is disabled by default, to enable it type: enable unwinder .* SpiderMonkey (gdb) bt #0 0x000112a11e96 in ContextToPC (context=0x3fff7e7d740) at ./js/src/wasm/WasmSignalHandlers.cpp:452 #1 0x000112a11e96 in HandleFault (info=0x3fff7e7d6c0, ctx=0x3fff7e7d740, signum=) at ./js/src/wasm/WasmSignalHandlers.cpp:1399 #2 0x000112a11e96 in WasmFaultHandler(int, siginfo_t*, void*) (signum=, info=0x3fff7e7d6c0, context=0x3fff7e7d740) at ./js/src/wasm/WasmSignalHandlers.cpp:1477 #3 0x03fff7e7d6b8 in () #4 0x000112aa6f04 in js::ProtectedData, unsigned int>::operator++(int) (this=0x7b0) at ./js/src/threading/ProtectedData.h:95 #5 0x000112aa6f04 in js::TenuringTracer::moveToTenured(JSString*) (this=0x3fff7e7dde8, src=Python Exception 'ascii' codec can't encode characters in position 3-4: ordinal not in range(128): ) at ./js/src/gc/Marking.cpp:3226 #6 0x000112aa70d2 in js::TenuringTracer::traverse(JSString**) (this=this@entry=0x3fff7e7dde8, strp=0x11a89d598) at ./js/src/gc/Marking.cpp:2743 #7 0x000112ab2d68 in js::gc::StoreBuffer::CellPtrEdge::trace(js::TenuringTracer&) const (this=this@entry=0x11a608e58, mover=...) at ./js/src/gc/Marking.cpp:2919 #8 0x000112ab2da8 in js::gc::StoreBuffer::MonoTypeBuffer::trace(js::gc::StoreBuffer*, js::TenuringTracer&) (this=this@entry=0x11a608e40, owner=, mover=...) at ./js/src/gc/StoreBuffer.h:236 #9 0x000112ac8c00 in js::gc::StoreBuffer::traceCells(js::TenuringTracer&) (mover=..., this=) at ./js/src/gc/StoreBuffer.h:440 #10 0x000112ac8c00 in js::Nursery::doCollection(JS::gcreason::Reason, js::gc::TenureCountCache&) (this=this@entry=0x11a608af8, reason=reason@entry=315707392, tenureCounts=...) at ./js/src/gc/Nursery.cpp:858 #11 0x000112ac9ffa in js::Nursery::collect(JS::gcreason::Reason) (this=this@entry=0x11a608af8, reason=reason@entry=JS::gcreason::DESTROY_RUNTIME) at ./js/src/gc/Nursery.cpp:724 #12 0x000112a79f76 in js::gc::GCRuntime::minorGC(JS::gcreason::Reason, js::gcstats::PhaseKind) (this=this@entry=0x11a6069a8, reason=reason@entry=JS::gcreason::DESTROY_RUNTIME, phase=phase@entry=js::gcstats::PhaseKind::EVICT_NURSERY_FOR_MAJOR_GC) at ./js/src/threading/ProtectedData.h:98 #13 0x000112a9f340 in js::gc::GCRuntime::minorGC(JS::gcreason::Reason, js::gcstats::PhaseKind) (phase=js::gcstats::PhaseKind::EVICT_NURSERY_FOR_MAJOR_GC, reason=JS::gcreason::DESTROY_RUNTIME, this=0x11a6069a8) at ./debian/build/dist/include/mozilla/ThreadLocal.h:223 #14 0x000112a9f340 in js::gc::GCRuntime::gcCycle(bool, js::SliceBudget&, JS::gcreason::Reason) (this=this@entry=0x11a6069a8, nonincrementalByAPI=nonincrementalByAPI@entry=true, budget=..., reason=reason@entry=JS::gcreason::DESTROY_RUNTIME) at ./js/src/gc/GC.cpp:7365 #15 0x000112a9f73e in js::gc::GCRuntime::collect(bool, js::SliceBudget, JS::gcreason::Reason) (this=this@entry=0x11a6069a8, nonincrementalByAPI=nonincrementalByAPI@entry=true, budget=..., reason=reason@entry=JS::gcreason::DESTROY_RUNTIME) at ./js/src/gc/GC.cpp:7556 #16 0x000112a9f8ac in js::gc::GCRuntime::gc(JSGCInvocationKind,
Bug#884352: virtualenvwrapper: Python interpreter inside virtualenv breaks after system python upgrade
On Mon, Sep 24, 2018 at 03:46:09PM -0400, Nicholas D Steeves wrote: > > > after upgrading system-wide Python installation (in my case from 3.5.3 to > > > 3.5.4), > > > virtualenvs may break due to the outdated interpreter > > > (somevirtualenv/bin/python3) inside the venv, trying to work with a newer > > > stdlib. > > This is in no way specific to virtualenvwrapper which is just a wrapper. > > Hi Andrey! If this is the case would you please reassign this bug to > virtualenv? I don't see any real value in reassigning this bug and I don't want to find out the correct binary package name. > > > The problem is that mkvirtualenv copies rather than symlinks the python > > > interpreter binary, but symlinks the modules from standard library (e.g. > > > /usr/lib/python3.5). > > This is done by virtualenv, not mkvirtualenv, and it was always that way, > > and it's quite well known that the breakages happen and how to fix them > > (by running virtualenv again). It is done because otherwise Python would > > not find some files using relative paths. > > > > See also https://github.com/pypa/virtualenv/pull/1171 and note "only for > > Python 3.3 and higher". > > As a beginner to Python it seems to me that the current behaviour > (copied interpreter and symlinked modules) is incorrect and that there > are three correct solutions: > > 1) As proposed in that PR, symlink the interpreter. This will fix itself when the PR is merged, not sooner. > 2) Copy the libraries instead of symlinking them. Can't comment on this. > 3) Downgrade the severity of this bug to non-RC, because this is a > known and expected issue when using virtualenvs. Sure, but this is up to the maintainer. > I imagine that the current behaviour is useful because more > vulnerabilities are found in libraries than in interpreters, and so it > is beneficial for them to automatically follow system-wide security > updates. Of course apt isn't aware of all possible locations of > venvs, so [2] would be bad, unless there was NEWS on each security > update to "update all your virtualenvs". In terms of annoyance > factor, the [2] option (plus running virtualenv again) seems more > annoying (but more secure) than using pip install --upgrade inside the > venv. Can't comment on this. -- WBR, wRAR signature.asc Description: PGP signature
Bug#831148: marked as done (toulbar2: FTBFS with GCC 6: tb2wcsp.cpp:873:14: error: no match for 'operator!=' (operand types are 'std::istream {aka std::basic_istream}' and 'long int'))
Your message dated Mon, 24 Sep 2018 16:04:03 -0400
with message-id
and subject line Re: toulbar2 packaging
has caused the Debian Bug report #831148,
regarding toulbar2: FTBFS with GCC 6: tb2wcsp.cpp:873:14: error: no match for
'operator!=' (operand types are 'std::istream {aka std::basic_istream}'
and 'long int')
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.)
--
831148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831148
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: toulbar2
Version: 0.9.8-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64
Hi,
During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html
Relevant part (hopefully):
> /usr/bin/c++ -DBOOST -DLINUX -DLONGDOUBLE_PROB -DLONGLONG_COST -DNARYCHAR
> -DWCSPFORMATONLY -DWIDE_STRING -I/«PKGBUILDDIR»/src -Wall -O3 -DNDEBUG -o
> CMakeFiles/toulbar2.dir/src/tb2wcsp.cpp.o -c /«PKGBUILDDIR»/src/tb2wcsp.cpp
> /«PKGBUILDDIR»/src/tb2wcsp.cpp: In member function 'virtual int
> WCSP::postGlobalConstraint(int*, int, std::__cxx11::string&, std::istream&,
> int*)':
> /«PKGBUILDDIR»/src/tb2wcsp.cpp:873:14: error: no match for 'operator!='
> (operand types are 'std::istream {aka std::basic_istream}' and 'long
> int')
> if (file != NULL) gc->read(file);
> ^
> /«PKGBUILDDIR»/src/tb2wcsp.cpp:873:14: note: candidate: operator!=(int, long
> int)
> /«PKGBUILDDIR»/src/tb2wcsp.cpp:873:14: note: no known conversion for
> argument 1 from 'std::istream {aka std::basic_istream}' to 'int'
> In file included from /usr/include/c++/6/bits/stl_algobase.h:64:0,
> from /usr/include/c++/6/bits/char_traits.h:39,
> from /usr/include/c++/6/string:40,
> from /«PKGBUILDDIR»/src/tb2utils.hpp:20,
> from /«PKGBUILDDIR»/src/tb2types.hpp:33,
> from /«PKGBUILDDIR»/src/toulbar2lib.hpp:56,
> from /«PKGBUILDDIR»/src/tb2wcsp.hpp:9,
> from /«PKGBUILDDIR»/src/tb2wcsp.cpp:7:
> /usr/include/c++/6/bits/stl_pair.h:376:5: note: candidate: template _T1, class _T2> constexpr bool std::operator!=(const std::pair<_T1, _T2>&,
> const std::pair<_T1, _T2>&)
> operator!=(const pair<_T1, _T2>& __x, const pair<_T1, _T2>& __y)
> ^~~~
> /usr/include/c++/6/bits/stl_pair.h:376:5: note: template argument
> deduction/substitution failed:
> In file included from /usr/include/unistd.h:229:0,
> from /usr/include/boost/config/stdlib/libstdcpp3.hpp:78,
> from /usr/include/boost/config.hpp:48,
> from /usr/include/boost/type_index.hpp:17,
> from /«PKGBUILDDIR»/src/tb2store.hpp:32,
> from /«PKGBUILDDIR»/src/tb2btlist.hpp:17,
> from /«PKGBUILDDIR»/src/tb2variable.hpp:9,
> from /«PKGBUILDDIR»/src/tb2wcsp.hpp:10,
> from /«PKGBUILDDIR»/src/tb2wcsp.cpp:7:
> /«PKGBUILDDIR»/src/tb2wcsp.cpp:873:17: note: 'std::istream {aka
> std::basic_istream}' is not derived from 'const std::pair<_T1, _T2>'
> if (file != NULL) gc->read(file);
> ^
> In file included from /usr/include/c++/6/bits/stl_algobase.h:67:0,
> from /usr/include/c++/6/bits/char_traits.h:39,
> from /usr/include/c++/6/string:40,
> from /«PKGBUILDDIR»/src/tb2utils.hpp:20,
> from /«PKGBUILDDIR»/src/tb2types.hpp:33,
> from /«PKGBUILDDIR»/src/toulbar2lib.hpp:56,
> from /«PKGBUILDDIR»/src/tb2wcsp.hpp:9,
> from /«PKGBUILDDIR»/src/tb2wcsp.cpp:7:
> /usr/include/c++/6/bits/stl_iterator.h:304:5: note: candidate: template _Iterator> bool std::operator!=(const std::reverse_iterator<_Iterator>&,
> const std::reverse_iterator<_Iterator>&)
> operator!=(const reverse_iterator<_Iterator>& __x,
> ^~~~
> /usr/include/c++/6/bits/stl_iterator.h:304:5: note: template argument
> deduction/substitution failed:
> In file included from /usr/include/unistd.h:229:0,
> from /usr/include/boost/config/stdlib/libstdcpp3.hpp:78,
> from /usr/include/boost/config.hpp:48,
> from /usr/include/boost/type_index.hpp:17,
Bug#909455: Info received (systemd FTBFS: meson_options.txt:49:0: ERROR: Option name debug is reserved.)
Never mind, found out that this is a backport from upstream (commit 8f6b442a78d0b485f044742ad90b2e8271b4e68e) -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
Processed: bug 908487 is forwarded to https://bugzilla.mozilla.org/show_bug.cgi?id=1492897, tagging 908487
Processing commands for cont...@bugs.debian.org: > forwarded 908487 https://bugzilla.mozilla.org/show_bug.cgi?id=1492897 Bug #908487 [src:mozjs60] mozjs60: FTBFS on mips: error: static assertion failed: atomics supported up to pointer size only Warning: Unknown package 'src:mozjs60' Set Bug forwarded-to-address to 'https://bugzilla.mozilla.org/show_bug.cgi?id=1492897'. Warning: Unknown package 'src:mozjs60' > tags 908487 + fixed-upstream Bug #908487 [src:mozjs60] mozjs60: FTBFS on mips: error: static assertion failed: atomics supported up to pointer size only Warning: Unknown package 'src:mozjs60' Added tag(s) fixed-upstream. Warning: Unknown package 'src:mozjs60' > thanks Stopping processing here. Please contact me if you need assistance. -- 908487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908487 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#884352: virtualenvwrapper: Python interpreter inside virtualenv breaks after system python upgrade
Hello, This bug came to my attention because elpy -> pyvenv-el -> virtualenvwrapper. On Sat, Sep 22, 2018 at 12:18:33PM +0500, Andrey Rahmatullin wrote: > On Thu, Dec 14, 2017 at 01:33:18PM +0100, Krzysztof Słychań wrote: > > after upgrading system-wide Python installation (in my case from 3.5.3 to > > 3.5.4), > > virtualenvs may break due to the outdated interpreter > > (somevirtualenv/bin/python3) inside the venv, trying to work with a newer > > stdlib. > This is in no way specific to virtualenvwrapper which is just a wrapper. Hi Andrey! If this is the case would you please reassign this bug to virtualenv? > > The problem is that mkvirtualenv copies rather than symlinks the python > > interpreter binary, but symlinks the modules from standard library (e.g. > > /usr/lib/python3.5). > This is done by virtualenv, not mkvirtualenv, and it was always that way, > and it's quite well known that the breakages happen and how to fix them > (by running virtualenv again). It is done because otherwise Python would > not find some files using relative paths. > > See also https://github.com/pypa/virtualenv/pull/1171 and note "only for > Python 3.3 and higher". As a beginner to Python it seems to me that the current behaviour (copied interpreter and symlinked modules) is incorrect and that there are three correct solutions: 1) As proposed in that PR, symlink the interpreter. 2) Copy the libraries instead of symlinking them. 3) Downgrade the severity of this bug to non-RC, because this is a known and expected issue when using virtualenvs. I imagine that the current behaviour is useful because more vulnerabilities are found in libraries than in interpreters, and so it is beneficial for them to automatically follow system-wide security updates. Of course apt isn't aware of all possible locations of venvs, so [2] would be bad, unless there was NEWS on each security update to "update all your virtualenvs". In terms of annoyance factor, the [2] option (plus running virtualenv again) seems more annoying (but more secure) than using pip install --upgrade inside the venv. Cheers, Nicholas signature.asc Description: PGP signature
Bug#909455: systemd FTBFS: meson_options.txt:49:0: ERROR: Option name debug is reserved.
Has this issue been reported upstream? Or a PR sent to fix the issue? I'm guessing this is caused by a change in meson in version 0.48 -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
Processed: found 863631 in 6.1.23~dfsg-2+deb8u3
Processing commands for cont...@bugs.debian.org:
> found 863631 6.1.23~dfsg-2+deb8u3
Bug #863631 {Done: Emmanuel Bouthenot } [sympa] sympa:
trashes configuration on update without asking
There is no source info for the package 'sympa' at version
'6.1.23~dfsg-2+deb8u3' with architecture ''
Unable to make a source version for version '6.1.23~dfsg-2+deb8u3'
Marked as found in versions 6.1.23~dfsg-2+deb8u3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
863631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863631
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#863631: conf file reset to default
also in sympa 6.1.23~dfsg-2+deb8u3
Bug#909529: python3-alembic and python3-astroid: file conflict on /usr/lib/python3/dist-packages/.pytest_cache/v/cache/nodeids
Package: python3-alembic,python3-astroid Severity: serious When installing python3-alembic and python3-astroid in a fresh sid chroot, this is what I get: | ... | Unpacking python3-sqlalchemy (1.2.8+ds1-1) ... | Selecting previously unselected package python3-alembic. | Preparing to unpack .../11-python3-alembic_1.0.0-1_all.deb ... | Unpacking python3-alembic (1.0.0-1) ... | Selecting previously unselected package python3-lazy-object-proxy. | Preparing to unpack .../12-python3-lazy-object-proxy_1.3.1-1+b1_amd64.deb ... | Unpacking python3-lazy-object-proxy (1.3.1-1+b1) ... | Selecting previously unselected package python3-wrapt. | Preparing to unpack .../13-python3-wrapt_1.10.11-1_amd64.deb ... | Unpacking python3-wrapt (1.10.11-1) ... | Selecting previously unselected package python3-setuptools. | Preparing to unpack .../14-python3-setuptools_40.2.0-1_all.deb ... | Unpacking python3-setuptools (40.2.0-1) ... | Selecting previously unselected package python3-astroid. | Preparing to unpack .../15-python3-astroid_2.0.4-1_all.deb ... | Unpacking python3-astroid (2.0.4-1) ... | dpkg: error processing archive /tmp/apt-dpkg-install-PRg25B/15-python3-astroid_2.0.4-1_all.deb (--unpack): | trying to overwrite '/usr/lib/python3/dist-packages/.pytest_cache/v/cache/nodeids', which is also in package python3-alembic 1.0.0-1 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Errors were encountered while processing: | /tmp/apt-dpkg-install-PRg25B/15-python3-astroid_2.0.4-1_all.deb | E: Sub-process /usr/bin/dpkg returned an error code (1) Helmut
Bug#906349: doublecmd: FTBFS in buster/sid (tries to write in /usr)
Hi Abou On 23 September 2018 at 22:44, Abou Al Montacir wrote: > I've reverted this in b9ccece9. However this means that Bug#898310 needs to > be reopen. Thanks, I have a reassigned #906349 so it can be closed when lazarus is uploaded. Shall I go ahead with an upload, or do you wish to make more changes? Regards Graham
Processed: [bts-link] source package src:todoman
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:todoman > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #908686 (http://bugs.debian.org/908686) > # Bug title: todoman FTBFS with python-click 6.7+git20180829-1 > # * https://github.com/pimutils/todoman/issues/324 > # * remote status changed: (?) -> closed > # * closed upstream > tags 908686 + fixed-upstream Bug #908686 [src:todoman] todoman FTBFS with python-click 6.7+git20180829-1 Added tag(s) fixed-upstream. > usertags 908686 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 908686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908686 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Add fixed in version ruby-minitest-around/0.4.1-1
Processing commands for cont...@bugs.debian.org:
> fixed 906654 ruby-minitest-around/0.4.1-1
Bug #906654 {Done: Sruthi Chandran }
[src:ruby-minitest-around] ruby-default-value-for: FTBFS in buster/sid (failing
tests)
Bug #906655 {Done: Sruthi Chandran }
[src:ruby-minitest-around] ruby-minitest-around: FTBFS in buster/sid (failing
tests)
The source ruby-minitest-around and version 0.4.1-1 do not appear to match any
binary packages
Marked as fixed in versions ruby-minitest-around/0.4.1-1.
Marked as fixed in versions ruby-minitest-around/0.4.1-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
906654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906654
906655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Reassign #906654 and close #906655
Processing commands for cont...@bugs.debian.org:
> reassign 906654 src:ruby-minitest-around
Bug #906654 {Done: Sruthi Chandran } [ruby-minitest-around]
ruby-default-value-for: FTBFS in buster/sid (failing tests)
Bug reassigned from package 'ruby-minitest-around' to
'src:ruby-minitest-around'.
Ignoring request to alter found versions of bug #906654 to the same values
previously set
Ignoring request to alter fixed versions of bug #906654 to the same values
previously set
> forcemerge 906654 906655
Bug #906654 {Done: Sruthi Chandran }
[src:ruby-minitest-around] ruby-default-value-for: FTBFS in buster/sid (failing
tests)
Bug #906655 [src:ruby-minitest-around] ruby-minitest-around: FTBFS in
buster/sid (failing tests)
Marked Bug as done
Added indication that 906655 affects ruby-default-value-for
Bug #906654 {Done: Sruthi Chandran }
[src:ruby-minitest-around] ruby-default-value-for: FTBFS in buster/sid (failing
tests)
Marked as found in versions ruby-minitest-around/0.3.2-1.
Merged 906654 906655
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
906654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906654
906655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed (with 1 error): Reassign #906654 and close #906655
Processing commands for cont...@bugs.debian.org:
> reassign 906654 ruby-minitest-around
Bug #906654 {Done: Sruthi Chandran }
[src:ruby-default-value-for] ruby-default-value-for: FTBFS in buster/sid
(failing tests)
Bug reassigned from package 'src:ruby-default-value-for' to
'ruby-minitest-around'.
No longer marked as found in versions ruby-default-value-for/3.0.1-1.
No longer marked as fixed in versions ruby-minitest-around/0.4.1-1.
> affects 906654 ruby-default-value-for
Bug #906654 {Done: Sruthi Chandran } [ruby-minitest-around]
ruby-default-value-for: FTBFS in buster/sid (failing tests)
Added indication that 906654 affects ruby-default-value-for
> forcemerge 906654 906655
Bug #906654 {Done: Sruthi Chandran } [ruby-minitest-around]
ruby-default-value-for: FTBFS in buster/sid (failing tests)
Unable to merge bugs because:
package of #906655 is 'src:ruby-minitest-around' not 'ruby-minitest-around'
Failed to forcibly merge 906654: Did not alter merged bugs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
906654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906654
906655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#906654: marked as done (ruby-default-value-for: FTBFS in buster/sid (failing tests))
Your message dated Mon, 24 Sep 2018 17:07:27 + with message-id and subject line Bug#906654: fixed in ruby-minitest-around 0.4.1-1 has caused the Debian Bug report #906654, regarding ruby-default-value-for: FTBFS in buster/sid (failing 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.) -- 906654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906654 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:ruby-default-value-for Version: 3.0.1-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --buildsystem=ruby --with ruby dh: Compatibility levels before 9 are deprecated (level 7 in use) dh_update_autotools_config -i -O--buildsystem=ruby dh_auto_configure -i -O--buildsystem=ruby dh_auto_configure: Compatibility levels before 9 are deprecated (level 7 in use) dh_ruby --configure dh_auto_build -i -O--buildsystem=ruby dh_auto_build: Compatibility levels before 9 are deprecated (level 7 in use) dh_ruby --build dh_ruby --build dh_auto_test -i -O--buildsystem=ruby dh_auto_test: Compatibility levels before 9 are deprecated (level 7 in use) dh_ruby --test [... snipped ...] install -d /<>/debian/ruby-default-value-for/usr/lib/ruby/vendor_ruby install -D -m644 /<>/lib/default_value_for/railtie.rb /<>/debian/ruby-default-value-for/usr/lib/ruby/vendor_ruby/default_value_for/railtie.rb install -D -m644 /<>/lib/default_value_for.rb /<>/debian/ruby-default-value-for/usr/lib/ruby/vendor_ruby/default_value_for.rb ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ â Install Rubygems integration metadata â ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ generating gemspec at /<>/debian/ruby-default-value-for/usr/share/rubygems-integration/all/specifications/default_value_for-3.0.1.gemspec /usr/bin/ruby2.5 /usr/bin/gem2deb-test-runner ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ â Run tests for ruby2.5 from debian/ruby-tests.rake â ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ RUBYLIB=/<>/debian/ruby-default-value-for/usr/lib/ruby/vendor_ruby:. GEM_PATH=debian/ruby-default-value-for/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all ruby2.5 -S rake -f debian/ruby-tests.rake /usr/bin/ruby2.5 test.rb /usr/lib/ruby/vendor_ruby/minitest.rb:961:in `run_one_method': DefaultValuePluginTest#run _must_ return a Result (RuntimeError) from /usr/lib/ruby/vendor_ruby/minitest.rb:334:in `run_one_method' from /usr/lib/ruby/vendor_ruby/minitest.rb:321:in `block (2 levels) in run' from /usr/lib/ruby/vendor_ruby/minitest.rb:320:in `each' from /usr/lib/ruby/vendor_ruby/minitest.rb:320:in `block in run' from /usr/lib/ruby/vendor_ruby/minitest.rb:360:in `on_signal' from /usr/lib/ruby/vendor_ruby/minitest.rb:347:in `with_info_handler' from /usr/lib/ruby/vendor_ruby/minitest.rb:319:in `run' from /usr/lib/ruby/vendor_ruby/minitest.rb:159:in `block in __run' from /usr/lib/ruby/vendor_ruby/minitest.rb:159:in `map' from /usr/lib/ruby/vendor_ruby/minitest.rb:159:in `__run' from /usr/lib/ruby/vendor_ruby/minitest.rb:136:in `run' from /usr/lib/ruby/vendor_ruby/minitest.rb:63:in `block in autorun' Testing with Active Record version 4.2.10 Run options: --seed 61094 # Running: rake aborted! Command failed with status (1): [/usr/bin/ruby2.5 test.rb...] /<>/debian/ruby-tests.rake:5:in `block in ' Tasks: TOP => default => test (See
Bug#870683: marked as done (ghc: DFSG incompatible file included in src)
Your message dated Mon, 24 Sep 2018 17:07:13 + with message-id and subject line Bug#870683: fixed in ghc 8.4.3+dfsg1-1 has caused the Debian Bug report #870683, regarding ghc: DFSG incompatible file included in src 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.) -- 870683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870683 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ghc Severity: serious Justification: Policy 2.1 Dear Maintainer, I find your package contains the following file, http://sources.debian.net/src/ghc/8.0.2-5/libraries/bytestring/tests/data/ which is licensed under The Project Gutenberg License. I have a package that meets the same problem, and I asked at debian-legal. Someone suggests this license fails the DFSG[1]. Please consider to remove this file from source. [1] https://lists.debian.org/debian-legal/2017/08/msg1.html Thanks, Shengjing Zhu signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: ghc Source-Version: 8.4.3+dfsg1-1 We believe that the bug you reported is fixed in the latest version of ghc, 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 870...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ilias Tsitsimpis (supplier of updated ghc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 21 Sep 2018 23:05:59 +0300 Source: ghc Binary: ghc ghc-prof ghc-doc Architecture: source Version: 8.4.3+dfsg1-1 Distribution: experimental Urgency: medium Maintainer: Debian Haskell Group Changed-By: Ilias Tsitsimpis Description: ghc- The Glasgow Haskell Compilation system ghc-doc- Documentation for the Glasgow Haskell Compilation system ghc-prof - Profiling libraries for the Glasgow Haskell Compilation system Closes: 870683 Changes: ghc (8.4.3+dfsg1-1) experimental; urgency=medium . * Backport upstream commit 18cb44dfae3f. This fixes upstream bug #15213 (32 bit Haddock runs out of memory compiling 32 bit GHC). * Remove DFSG incompatible file (Closes: #870683). Checksums-Sha1: 73d795f3bcb15a0baf2dbf834546897d69d63a22 2400 ghc_8.4.3+dfsg1-1.dsc b6042084be8d0b429c74dfe3bd065be22a9055df 11234976 ghc_8.4.3+dfsg1.orig.tar.xz 2d41dc1549edf2147d56871e73f97b275d2e7bd7 56124 ghc_8.4.3+dfsg1-1.debian.tar.xz 8b4bb4b7743a2a4c150cb1364bea75ca591c7e93 6201 ghc_8.4.3+dfsg1-1_source.buildinfo Checksums-Sha256: 2904c32ba35923ab59c883730a17d7426e6688b63c85c3db6b413a8d846180cf 2400 ghc_8.4.3+dfsg1-1.dsc 7e55be5fa6d390ba83285ffd3673fab009d99ee438dcbe7493be8f01c7ad1ac6 11234976 ghc_8.4.3+dfsg1.orig.tar.xz eb8ba0fb1e9d19eea95566e5318f413d19dc23612daa7c64f95379777b47d065 56124 ghc_8.4.3+dfsg1-1.debian.tar.xz 411c6a4f2e6700546ce6424cac03370e04ed2f01280bfe4cad7fb99dc5a704d3 6201 ghc_8.4.3+dfsg1-1_source.buildinfo Files: 714a6b042bfa3639de84c8d67caa0c47 2400 haskell optional ghc_8.4.3+dfsg1-1.dsc f5b6595fd11b75657c59291f67e9347b 11234976 haskell optional ghc_8.4.3+dfsg1.orig.tar.xz d6e20686df843b32ceb95fe0b8950c61 56124 haskell optional ghc_8.4.3+dfsg1-1.debian.tar.xz 8ccebb6b69352971a93d211b8b2c66ff 6201 haskell optional ghc_8.4.3+dfsg1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAlupFVAUHGlsaWFzdHNp QGRlYmlhbi5vcmcACgkQ16hngMxkQDzDiQ/7ByGjHcpr1YmdKxlNx4lQKuHAGbmr N55ahEeT15+BZx9th3sA5vz26KA9DVI+vWi+vJb23OZMLnElWPQDXdJuAKj4U2Pq nbmKM3+2ciiYwlfpcNSAfRdOVTNGURzYC/uhaZA/UE/dMqTbEaIsojL3W4hAdSFp opakLWwDvgGhSV0KWnfED1mte3g7zRp7jTSzk9qTQckaAhmpU8Gsr4NNhhhKWRzL 4jhK2ulwpAxe/at23nYMa0LcaLXhJP9AcCTV5SM35++23W8/QK88b/DhsBSfuvFr vXeu7F9flsLfcCvkk0Gy+Wk19BQSQF1q54cgHXFMUosw/CjpCjtQ1X//Iaewfzpw 0PL14b+ccjdTW4pN0ilrSu3iTajYgwIrJ1BnEBGNeFu+A6Htxgxqhnc2tH11Mc9K jhD2qD4U/ZE0s29vHzDa/nl12jYDesjN4Mo5C+anTwu1DNm1/7WOJwXUbRYpOd4C 8iBaieBBBeKCyfSxRDllm2CINUG+P38M+yLEHfe5/t7HjHTCHZ//wTQ73dlAxj4W etlUgxaxfCrIlWCr3kQKs2pk9CDax7pbw3wmQUJPvhyuP4wvZKXqpBhsGUyuiMXl 7I+bS1h9QJFmA9+171VNRCggg0lII3R5lI4rbCam/cfc/cGwr3cBQk89fNz9Hbt/ Jm9UYrRFJXkY2PI= =IiVb -END PGP SIGNATURE End Message ---
Bug#882287: fixed in mozilla-noscript 10.1.9.6-1
Hello On 9/24/18 11:00 AM, Ximin Luo wrote: Source: mozilla-noscript Source-Version: 10.1.9.6-1 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 22 Sep 2018 23:25:18 -0700 Source: mozilla-noscript Binary: webext-noscript xul-ext-noscript Architecture: source all Version: 10.1.9.6-1 Distribution: unstable Urgency: medium Maintainer: Debian Mozilla Extension Maintainers Changed-By: Ximin Luo Description: webext-noscript - permissions manager for Firefox xul-ext-noscript - Show browser tabs like a tree - transitional package Show browser tabs like a tree? I don't think so. Please correct that. Regards Jiri Palecek
Bug#909512: python-argon2: Incomplete debian/copyright?
Source: python-argon2 Version: 18.1.0-1 Severity: serious Justication: Policy 12.5 X-Debbugs-CC: Nicolas Dandrimont , ftpmas...@debian.org Hi, I just ACCEPTed python-argon2 from NEW but noticed it was missing some attribution in debian/copyright for the "original Argon2 repo". It would be great if you could ensure this is more explicitly mention in debian/copyright, perhaps in the Comment field or similar. (This is in no way exhaustive so please check over the entire package carefully and address this or anything else on your next upload.) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#906472: horst: FTBFS in buster/sid (unable to open 'stdarg.h')
On Fri, Sep 14, 2018 at 09:45:44PM +0200, Uwe Kleine-König wrote: > Hello, > > [Cc += sparse mailing list] Sorry for the late answer. > > > Santiago Vila wrote... > > > > > > > make -j1 check > > > > make[1]: Entering directory '/<>' > > > > sparse -g -O2 -fdebug-prefix-map=/<>=. > > > > -fstack-protector-strong -Wformat -Werror=format-security -std=gnu99 > > > > -Wall -Wextra -g -I. -DDO_DEBUG -I/usr/include/libnl3 *.[ch] > > > > /usr/include/err.h:25:11: error: unable to open 'stdarg.h' > > > > > > To reproduce this it's important to remove gcc-7 from the build chroot > > > (apt purge libgcc-7-dev ; apt --purge autoremove). > > > > > > Problem is, sparse appearently uses hardcoded paths and looks for > > > stdarg.h in (among other places) Well, sparse needs to know where it can find the system header files. There is an option for this: -gcc-base-dir (and -multiarch-dir). Usually you will want to use either some that are installed by your distro or the one that match the exact GCC version you're using. By *default*, if no -gcc-base-dir is used, sparse use the same dir as the one used by the GCC used to compile sparse itself. It's only this default that is hardcoded. > > > Solution is to rebuild sparse, building horst was successful then. > > > If this is true (please check!), the interesting question is why this > > > wasn't a problem in earlier gcc version bumps. > > I think this is a known limitation of sparse and there are three > ways to fix this (in my order of preference): > > a) let horst use cgcc -no-compile instead of sparse; or > b) let sparse depend on libgcc-7-dev (or whatever provides the > necessary files); or > c) use autodetection which gcc is used and pick its files. > > I'm not sure if a) fixes the problem. It fixed another problem we had > with horst's usage of sparse in the past though[1]. > > The downside of c) is that running this autodetection on every call to > sparse is probably slowing down sparse a bit which isn't nice. In case the default can't be used, like here, I think the best is to add in your Makefile something like: GCC_BASE_DIR=$(shell $(CC) -print-file-name=) SPARSE_FLAGS= -gcc-base-dir $(GCC_BASE_DIR) ... sparse $(SPARSE_FLAGS) ... This doesn't need to be done at each invocation of sparse (but will be done at each top-level make invocation). Regards, -- Luc
Processed: forcibly merging 909464 909039
Processing commands for cont...@bugs.debian.org: > forcemerge 909464 909039 Bug #909464 [thunderbird] thunderbird: Thunderbird crash : Fontconfig error: failed reading config file Bug #909039 [thunderbird] thunderbird: Crash when starting Thunderbird after latest security update to 1:60.0-3~deb9u1 Unset Bug forwarded-to-address Bug #909464 [thunderbird] thunderbird: Thunderbird crash : Fontconfig error: failed reading config file Added tag(s) upstream. Merged 909039 909464 > thanks Stopping processing here. Please contact me if you need assistance. -- 909039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909039 909464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909464 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909506: inetutils-telnetd: calls update-inetd with wrong arguments
Package: inetutils-telnetd Version: 2:1.9.4-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to remove. >From the attached log (scroll to the bottom...): Removing inetutils-telnetd (2:1.9.4-3+b1) ... update-inetd: error: --group is only relevant with --add dpkg: error processing package inetutils-telnetd (--remove): installed inetutils-telnetd package post-removal script subprocess returned error exit status 255 update-inetd got more strict recently and rejects superfluous usage of --group cheers, Andreas inetutils-telnetd_2:1.9.4-3+b1.log.gz Description: application/gzip
Bug#908166: marked as done (swt4-gtk: compilation with openjdk-10 results in empty jar)
Your message dated Mon, 24 Sep 2018 16:09:41 + with message-id and subject line Bug#908166: fixed in swt4-gtk 4.6.3-3 has caused the Debian Bug report #908166, regarding swt4-gtk: compilation with openjdk-10 results in empty jar 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.) -- 908166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908166 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: swt4-gtk Severity: normal Hi, I tried to rebuild this as part of fixing #907990 but only got an empty jar. It compiles fine with openjdk-8, though. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.17.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: swt4-gtk Source-Version: 4.6.3-3 We believe that the bug you reported is fixed in the latest version of swt4-gtk, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 908...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg (supplier of updated swt4-gtk package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 24 Sep 2018 17:45:21 +0200 Source: swt4-gtk Binary: libswt-gtk-4-java libswt-gtk-4-jni libswt-gtk2-4-jni libswt-cairo-gtk-4-jni libswt-glx-gtk-4-jni libswt-webkit-gtk-4-jni Architecture: source Version: 4.6.3-3 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Emmanuel Bourg Description: libswt-cairo-gtk-4-jni - Standard Widget Toolkit for GTK+ Cairo JNI library libswt-glx-gtk-4-jni - Standard Widget Toolkit for GTK+ GLX JNI library libswt-gtk-4-java - Standard Widget Toolkit for GTK+ Java library libswt-gtk-4-jni - Standard Widget Toolkit for GTK+ JNI library libswt-gtk2-4-jni - Standard Widget Toolkit for GTK+ 2.0 JNI library libswt-webkit-gtk-4-jni - Standard Widget Toolkit for GTK+ WebKit JNI library Closes: 908166 908281 Changes: swt4-gtk (4.6.3-3) unstable; urgency=medium . * Team upload. . [ Jochen Sprickerhof ] * Set javac release to 7 for JDK 10 compatibility (Closes: #908166) * Add patch for missing swt-gnome-gtk (Closes: #908281) . [ Emmanuel Bourg ] * Standards-Version updated to 4.2.1 * Use salsa.debian.org Vcs-* URLs Checksums-Sha1: 325e96f151208b2336ac30e89766ee29f1ffb4bb 2521 swt4-gtk_4.6.3-3.dsc 5c01c562b540a60f41ba9e27b8b58f04cbe9efea 26900 swt4-gtk_4.6.3-3.debian.tar.xz 9da556f575c9fba8a69848ce80084957d95cbbdd 15202 swt4-gtk_4.6.3-3_source.buildinfo Checksums-Sha256: f860ab96c66c1c5deb993b02e987e3c14e079d78d17c376a3a5b78aacfa4d59f 2521 swt4-gtk_4.6.3-3.dsc e128ed2807585a3efbfd19eb92778d5673e10e6242e333851adee5375047f940 26900 swt4-gtk_4.6.3-3.debian.tar.xz 97c2095a235579c1283608b60e15ba838edcbedc9e56904f57859b6ad2dad217 15202 swt4-gtk_4.6.3-3_source.buildinfo Files: a0bef3489b7b4be77a537063630f2871 2521 java optional swt4-gtk_4.6.3-3.dsc 6b9a483fa5d4a3a95e4b128d9806c28d 26900 java optional swt4-gtk_4.6.3-3.debian.tar.xz 661ea8229af9ffc18b22dff2f8c23749 15202 java optional swt4-gtk_4.6.3-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlupBvMSHGVib3VyZ0Bh cGFjaGUub3JnAAoJEPUTxBnkudCsn68P/0UGM9+i4n33Em5N/yPLsrnv7QsKb6tv xo+GV0Ksqan96Gfl+SlYP68Unv4SXenFmMjnuGU82+V+J1ih5JWRdssAack3gjMR cabRX0il3lJNyCcqIGFwI9yPuyOlipYxd4eo5I++mmuNZAQbenjDSdY7NjVk8lJ6 lIN7yyGe20ReFPDcUFU7d3OnEWzb7fGkh0BEqBcc5reInhusYO2sTwyjBn46ishy MFsToxVV97Attmoo1LMgqgwaxH/mkBllxytXiCRWxlnDl4dRe7emLI8Wu79uiVR9 sDz6rP5ApSKoIL4Gg9GO9vBkSXGrW+KLm7MpwQPx2uM9FhFrWcMdmUbwXNfZEoOi Ocuv6oJW+MGz/dR8gJtvoh5hPhv4tOSjUp9oKDBpWHlCiYihFZ3jxhCxewWd8wu3 coFtYOpMdxS8iPIkkwMpgNbY5vPhVyK1Yex9S8EJ1YAiIbDYi6AtxWy1rb0YlvT7 VH42k6gRYLpxSTd3rbLKH2/GEnaOLFn5z24ESZ8STQ8ZuwHU6vnQW7MD/LjVXWig ZK3teR90JP62/8dvkzTlR+eEKh6RbJW7pQJD1zdQrU6z2lAgy7tcEBpOMsvoXM/S nKBOjDb4f6l4mDifab8BD8Sh6+wAg4kP5EZiolR5LvPC1McB6Q9XZe7Uqvz+YcTZ
Bug#909464: Also afected me
Just for the record, and to help anyone who may have the problem, hopefully this will be referenced in search engines. This happened to me as well. I had in my folder: ~/.thunderbird/-hash-.default/Mail/Local Folders/Éléments envoyés "Éléments envoyés" in French matches the sent folder. I didn't care about it, so I just renamed the folder, and thunderbird just worked. The folders and files like this were encoded with some weirdo encoding, and even ls or mc wouldn't display it correctly. Cheers, Thomas Goirand (zigo)
Bug#908166: Bug #908166 in swt-gtk marked as pending
Control: tag -1 pending Hello, Bug #908166 in swt-gtk reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at: https://salsa.debian.org/java-team/swt-gtk/commit/86679ce2b105be643584d39a3e7d92ccabf30bd9 Add patch for Java 10 Closes: #908166 (this message was generated automatically) -- Greetings https://bugs.debian.org/908166
Processed: Bug #908166 in swt-gtk marked as pending
Processing control commands: > tag -1 pending Bug #908166 [src:swt4-gtk] swt4-gtk: compilation with openjdk-10 results in empty jar Added tag(s) pending. -- 908166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908166 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): Re: [Pkg-rust-maintainers] Bug#909482: rustc: FTBFS on mips64el on buildds: timeout
Processing control commands: > forcemerge 881845 -1 Bug #881845 [src:rustc] rustc: FTBFS on mips*: test failures Unable to merge bugs because: package of #909482 is 'rustc' not 'src:rustc' Failed to forcibly merge 881845: Did not alter merged bugs. -- 881845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881845 909482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909482 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909482: [Pkg-rust-maintainers] Bug#909482: rustc: FTBFS on mips64el on buildds: timeout
Control: forcemerge 881845 -1 Yes, we're aware, see the discussion in #881845. The issue is some mips CPUs are (allegedly) buggy and so a porter with access to the allegedly non-buggy ones have been doing manual builds. I let this situation continue but would also be happy to just RM rustc mips64el for the time being, to avoid blocking migration to Debian Testing to the other bugs. If nobody builds mips64el in the next few days I will go ahead and request RM by FTP masters. X Ivo De Decker: > package: rustc > version: 1.28.0+dfsg1-2 > severity: serious > tags: ftbfs > > Hi, > > The builds of rustc in sid on mips64el consistently fail on the buildds: > > https://buildd.debian.org/status/logs.php?pkg=rustc=mips64el > > Most of the fail with > > "Build killed with signal TERM after 150 minutes of inactivity" > > If the build is actually still going at that point, it should produce output > to avoid being killed. > > The builds that are in the archive seem to be manual builds that were > uploaded. > > Cheers, > > Ivo > > ___ > Pkg-rust-maintainers mailing list > pkg-rust-maintain...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-rust-maintainers > -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git
Bug#909505: bidentd: calls update-inetd with wrong arguments
Package: bidentd Version: 1.1.4-1.1 Severity: serious Tags: sid buster User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Selecting previously unselected package bidentd. (Reading database ... (Reading database ... 8336 files and directories currently installed.) Preparing to unpack .../bidentd_1.1.4-1.1+b2_i386.deb ... Unpacking bidentd (1.1.4-1.1+b2) ... Setting up bidentd (1.1.4-1.1+b2) ... update-inetd: error: --pattern is not relevant with --add dpkg: error processing package bidentd (--configure): installed bidentd package post-installation script subprocess returned error exit status 255 Errors were encountered while processing: bidentd update-inetd got more strict recently and rejects superfluous usage of --group cheers, Andreas bidentd_1.1.4-1.1+b2.log.gz Description: application/gzip
Processed: Tags
Processing commands for cont...@bugs.debian.org: > forwarded 909480 https://github.com/stash/Feersum/issues/31 Bug #909480 [src:feersum] feersum: FTBFS randomly (failing tests) Warning: Unknown package 'src:feersum' Set Bug forwarded-to-address to 'https://github.com/stash/Feersum/issues/31'. Warning: Unknown package 'src:feersum' > End of message, stopping processing here. Please contact me if you need assistance. -- 909480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909480 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909502: libbio-tools-run-alignment-tcoffee-perl: FTBFS (test failures) with t-coffee 11.00.8cbe486-7
Source: libbio-tools-run-alignment-tcoffee-perl Version: 1.7.4-1 Severity: serious Tags: sid buster Justification: fails to build from source -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 As first seen on ci.debian.net, the upgrade of t-coffee from 11.00.8cbe486-6 to 11.00.8cbe486-7 breaks libbio-tools-run-alignment-tcoffee-perl's test suite: debian/rules override_dh_auto_test make[1]: Entering directory '/build/libbio-tools-run-alignment-tcoffee-perl-1.7.4' mkdir -p /build/libbio-tools-run-alignment-tcoffee-perl-1.7.4/debian/build HOME=/build/libbio-tools-run-alignment-tcoffee-perl-1.7.4/debian/build dh_auto_test make -j4 test TEST_VERBOSE=1 make[2]: Entering directory '/build/libbio-tools-run-alignment-tcoffee-perl-1.7.4' 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/00-compile.t ... 1..1 ok 1 - Bio/Tools/Run/Alignment/TCoffee.pm loaded ok ok t/author-eol.t ... skipped: these tests are for testing by the author t/author-mojibake.t .. skipped: these tests are for testing by the author t/author-no-tabs.t ... skipped: these tests are for testing by the author t/author-pod-coverage.t .. skipped: these tests are for testing by the author t/author-pod-syntax.t skipped: these tests are for testing by the author * *FULL TRACE BACK PID: 2227 2243 -- ERROR: COREDUMP: T-COFFEE Version_11.00.8cbe486 (2014-08-12 22:05:29 - Revision 8cbe486 - Build 477) * ** * Abnormal Termination * Job NOT Completed:[T-COFFEE, Version_11.00.8cbe486] * Please CHECK: * -1 The format of your Input Files * -2 The parameters * -3 The use of special characters in sequence names: *(@, |, %...) * -4 The Online Doc (http://www.tcoffee.org) * -5 re-run your CL (see below) with tze -debug option. This will produce a debug file you can send us. * * NO * to: * cedric.notred...@gmail.com * If you run T-Coffee over the WEB: * Windows Cut and Paste is sometimes erratic and * it can loose carriage returns. If you suspect this, * try to cut and paste through an intermediate application * (word pad) and inspect the results * CONFIDENTIALITY: * The File NO may contain your personal DATA * Remove ALL confidential DATA from this file BEFORE sending it ** # Command Line: /usr/bin/t_coffee -profile otOrqlTVt8 -seq g5USs5RIgV -matrix blosum -method lalign_id_pair clustalw_pair -ktuple 3 -outfile /tmp/McVdzikYRh/smBiz31aXb -output clustalw -quiet [PROGRAM:T-COFFEE] # TERMINATION STATUS: FAILURE [PROGRAM: T-COFFEE pid 2227 ppid 2133 #CL: /usr/bin/t_coffee -profile otOrqlTVt8 -seq g5USs5RIgV -matrix blosum -method lalign_id_pair clustalw_pair -ktuple 3 -outfile /tmp/McVdzikYRh/smBiz31aXb -output clustalw -quiet # Failed test at t/TCoffee.t line 74. # died: # - EXCEPTION - # MSG: TCoffee call crashed: 256 [command /usr/bin/t_coffee -profile=otOrqlTVt8 -seq=g5USs5RIgV -matrix=blosum -method=lalign_id_pair,clustalw_pair -ktuple=3 -outfile=/tmp/McVdzikYRh/smBiz31aXb -output=clustalw -quiet] # # STACK Bio::Root::RootI::warn /usr/share/perl5/Bio/Root/RootI.pm:150 # STACK Bio::Tools::Run::Alignment::TCoffee::_run /build/libbio-tools-run-alignment-tcoffee-perl-1.7.4/blib/lib/Bio/Tools/Run/Alignment/TCoffee.pm:272 # STACK Bio::Tools::Run::Alignment::TCoffee::profile_align /build/libbio-tools-run-alignment-tcoffee-perl-1.7.4/blib/lib/Bio/Tools/Run/Alignment/TCoffee.pm:198 # STACK Test::Exception::lives_ok t/TCoffee.t:74 # STACK toplevel t/TCoffee.t:74 # - # Failed test 'no T-COFFEE errors' # at t/TCoffee.t line 76. * *FULL TRACE BACK PID: 2285 2300 -- ERROR: COREDUMP: T-COFFEE Version_11.00.8cbe486 (2014-08-12 22:05:29 - Revision 8cbe486 - Build 477) * ** * Abnormal Termination * Job NOT Completed:[T-COFFEE,
Bug#909503: micro-httpd: calls update-inetd with wrong arguments
Package: micro-httpd Version: 20051212-15.1 Severity: serious Tags: sid buster User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to remove. >From the attached log (scroll to the bottom...): Removing micro-httpd (20051212-15.1) ... /var/lib/dpkg/info/micro-httpd.prerm: removing /etc/inetd.conf entry update-inetd: error: --group is only relevant with --add dpkg: error processing package micro-httpd (--remove): installed micro-httpd package pre-removal script subprocess returned error exit status 255 update-inetd got more strict recently and rejects superfluous usage of --group cheers, Andreas micro-httpd_20051212-15.1.log.gz Description: application/gzip
Bug#907806: How to disable tests for Python2 only?
On Mon, 24 Sep 2018, Andreas Tille wrote: > Probably due to racing condition since I migrated the repository before > your pushes. > > > either needed to be imported as quilt patches or alternatively you can > > > use git mode in d/watch which creates a new tarball for you > > > incorporating the latest state of upstream Git (I doubt that would be a > > > sensible solution in the current case). > > if we are to stay with my non conventional setup of sitting straight on > > top of the upstream git repo, then we would just need to merge > > debian-0.20 branch into debian branch (might be a fast-forward) whenever > > we are ready to upload that beast. > I confirm that there are cases where this workflow makes sense. We need > to outweight pros and cons. To say the truth, I am no longer sure since it is possible to still have regular upstream repo as a remote and dedicated branches for them in the same git repo (locally), so I could still cherry pick etc. Pretty much what I do eg for cython etc. That is why I am agreeing to go "standard" so to make life easier for others as well. My only concern with the "standard" workflow ATM is that pristine-tar is not as reliable as needed to be. # of open issues manifests to that https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=pristine-tar;dist=unstable and Joey himself moved from using it to dgit AFAIK. But anyways it is unrelated to this discussion, sorry for bringing it up ;( > > ... > > If we are to convert to the more conventional gbp workflow (I am ok with > > that now ;)) , I guess the best would be to just reimport from the > > snapshots entire history of the package and proceed from there. Then > > commits in debian-0.20 would need to be rebased (or cherry picked or > > your suggested format-patch+am) to stay on top of the "master" > > branch > I hope I will find the time tomorrow or the day after tomorrow. thanks > > and picking any needed changes, would be appreciated. I will adjust ;) > I'll check what might be the easier solution and will come back once I > did so. Hopefully you will have solved the ssh issue meanwhile. I will try again later today, and when home (different network/provider) -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik
Bug#907806: How to disable tests for Python2 only?
Hi Yaroslav, On Mon, Sep 24, 2018 at 11:03:16AM -0400, Yaroslav Halchenko wrote: > > > You asked me to clone http://github.com/yarikoptic/scikit-learn to > > https://salsa.debian.org/science-team/scikit-learn which I did. In > > cool :-) > > *your* packaging repository is no branch 0.20rc1 those commits would be > > indeed salsa clone is missing the > https://github.com/yarikoptic/scikit-learn/tree/debian-0.20 branch which > sits on top of debian branch and the 0.20rc1 upstream tag (pushed > now to my fork on github) Probably due to racing condition since I migrated the repository before your pushes. > > either needed to be imported as quilt patches or alternatively you can > > use git mode in d/watch which creates a new tarball for you > > incorporating the latest state of upstream Git (I doubt that would be a > > sensible solution in the current case). > > if we are to stay with my non conventional setup of sitting straight on > top of the upstream git repo, then we would just need to merge > debian-0.20 branch into debian branch (might be a fast-forward) whenever > we are ready to upload that beast. I confirm that there are cases where this workflow makes sense. We need to outweight pros and cons. My main argument against it is *currently* that the workflow is not described in our team policy and I previous had always trouble with workflows not described there because there are always some details some other team member can not guess. Below you agree to use the traditional workflow so I'd like to stick to this. > > like using git mode in debian/watch and try to extract your commits to > > debian/ dir via `git format-patch` and import these into Debian Science > > repository via `git am`. However, I do not see this as very promising > > If we are to convert to the more conventional gbp workflow (I am ok with > that now ;)) , I guess the best would be to just reimport from the > snapshots entire history of the package and proceed from there. Then > commits in debian-0.20 would need to be rebased (or cherry picked or > your suggested format-patch+am) to stay on top of the "master" > branch I hope I will find the time tomorrow or the day after tomorrow. > > since I'm not sure whether you are really in favour to migrate to Debian > > Science or rather stick to your workflow. > > I am ok with either way now, as long as the package stays easy to > backport (so cythonize in debian/rules etc stays) I do not plan to fiddle with d/rules since I do not really understand what's happening there - at least as long as it works. :-) > > So before I start spending > > time into this it would be helpful if you confirm that you can > > >gbp clone g...@salsa.debian.org:science-team/scikit-learn.git > > as I said, smth is finicky with ssh for me for salsa: > > $>gbp clone g...@salsa.debian.org:science-team/scikit-learn.git > gbp:info: Cloning from 'g...@salsa.debian.org:science-team/scikit-learn.git' > gbp:error: Git command failed: Error running git clone: ssh: connect to host > salsa.debian.org port 22: Network is unreachable > fatal: Could not read from remote repository. > > Please make sure you have the correct access rights > and the repository exists. > > $> sudo tcptraceroute salsa.debian.org 22 > Running: > traceroute -T -O info -p 22 salsa.debian.org > traceroute to salsa.debian.org (209.87.16.44), 30 hops max, 60 byte packets > 1 _gateway (10.31.176.1) 1.733 ms 2.085 ms 2.620 ms > 2 berry1-crt.border1-rt.dartmouth.edu (129.170.1.42) 2.598 ms 2.074 ms > 2.060 ms > 3 i2-cleveland.border1-rt.dartmouth.edu (129.170.9.241) 6.170 ms 6.151 ms > 6.155 ms > 4 et-3-1-0.4079.rtsw.clev.net.internet2.edu (162.252.70.93) 15.175 ms > 15.531 ms 15.542 ms > 5 ae-1.4079.rtsw.eqch.net.internet2.edu (162.252.70.131) 25.121 ms 25.082 > ms 24.325 ms > 6 et-7-0-0.4079.rtsw.minn.net.internet2.edu (162.252.70.107) 31.915 ms > 32.184 ms 31.981 ms > 7 et-7-0-0.4079.rtsw.miss2.net.internet2.edu (162.252.70.59) 55.142 ms > 57.452 ms 55.346 ms > 8 et-4-1-0.4079.rtsw.seat.net.internet2.edu (162.252.70.1) 65.376 ms > 65.717 ms 65.842 ms > 9 * * * > 10 * * * > 11 * * * > 12 * * * > 13 * * * > 14 * * * > 15 * * * > 16 * * * > > > I can clone though via https:// (just can't push changes via ssh) Is this true for all repositories on Salsa? May be something with your ssh-key? > > and we both agree about the method how we want to inject the upstream > > source there. Debian Science policy says this is done via > > >gbp import-orig --pristine-tar > > > while the upstream tarball is obtained via uscan or some get-orig-source > > script in exceptional cases. What do you think about this? > > If you could migrate to the team standard using > > gbp import-dscs --debsnap > > and picking any needed changes, would be appreciated. I will adjust ;) I'll check what might be the easier solution and will come back once I did so.
Bug#907806: How to disable tests for Python2 only?
On Mon, 24 Sep 2018, Andreas Tille wrote: > > > When you talked about new upstream version: Do you want to give 0.20rc1 > > I did give it a try... > > From the now empty list of > > https://github.com/scikit-learn/scikit-learn/issues/created_by/yarikoptic it > > might be that all of the ones I've filed are addressed by now, BUT I do not > > see > > them in > > $> git lg 0.20rc1..origin/0.20.X > > * c196ec405 - (origin/0.20.X) Remove OPTICS from 0.20 (#12053) (7 days ago) > > [Joel Nothman] > > * 17f8016c5 - Bugfix release of joblib that also restores PyPy support > > (#12012) (3 weeks ago) [Olivier Grisel] > > * c40726e91 - CI handle sparse checkout with new branch (4 weeks ago) [Joel > > Nothman] > > * 96a3e21fb - CI Verbosity in push_doc (4 weeks ago) [Joel Nothman] > > * 9c3ecb2c4 - CI use correct scikit-learn.github.io branch (4 weeks ago) > > [Joel Nothman] > > * 061343e9f - CI Only try to remove docs dir if present (4 weeks ago) [Joel > > Nothman] > > so might have been fixed in master, and not backported yet, which indeed > > might be the case: > > https://github.com/scikit-learn/scikit-learn/issues/12016#issuecomment-419079493 > You asked me to clone http://github.com/yarikoptic/scikit-learn to > https://salsa.debian.org/science-team/scikit-learn which I did. In cool > *your* packaging repository is no branch 0.20rc1 those commits would be indeed salsa clone is missing the https://github.com/yarikoptic/scikit-learn/tree/debian-0.20 branch which sits on top of debian branch and the 0.20rc1 upstream tag (pushed now to my fork on github) > either needed to be imported as quilt patches or alternatively you can > use git mode in d/watch which creates a new tarball for you > incorporating the latest state of upstream Git (I doubt that would be a > sensible solution in the current case). if we are to stay with my non conventional setup of sitting straight on top of the upstream git repo, then we would just need to merge debian-0.20 branch into debian branch (might be a fast-forward) whenever we are ready to upload that beast. > I have no trouble with accessing the repository on Salsa. > > Meanwhile, debian-0.20 branch is on > > http://github.com/yarikoptic/scikit-learn > I admit I'm not sure what you want me to do next. It somehow smells > like using git mode in debian/watch and try to extract your commits to > debian/ dir via `git format-patch` and import these into Debian Science > repository via `git am`. However, I do not see this as very promising If we are to convert to the more conventional gbp workflow (I am ok with that now ;)) , I guess the best would be to just reimport from the snapshots entire history of the package and proceed from there. Then commits in debian-0.20 would need to be rebased (or cherry picked or your suggested format-patch+am) to stay on top of the "master" branch > since I'm not sure whether you are really in favour to migrate to Debian > Science or rather stick to your workflow. I am ok with either way now, as long as the package stays easy to backport (so cythonize in debian/rules etc stays) > So before I start spending > time into this it would be helpful if you confirm that you can >gbp clone g...@salsa.debian.org:science-team/scikit-learn.git as I said, smth is finicky with ssh for me for salsa: $>gbp clone g...@salsa.debian.org:science-team/scikit-learn.git gbp:info: Cloning from 'g...@salsa.debian.org:science-team/scikit-learn.git' gbp:error: Git command failed: Error running git clone: ssh: connect to host salsa.debian.org port 22: Network is unreachable fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. $> sudo tcptraceroute salsa.debian.org 22 Running: traceroute -T -O info -p 22 salsa.debian.org traceroute to salsa.debian.org (209.87.16.44), 30 hops max, 60 byte packets 1 _gateway (10.31.176.1) 1.733 ms 2.085 ms 2.620 ms 2 berry1-crt.border1-rt.dartmouth.edu (129.170.1.42) 2.598 ms 2.074 ms 2.060 ms 3 i2-cleveland.border1-rt.dartmouth.edu (129.170.9.241) 6.170 ms 6.151 ms 6.155 ms 4 et-3-1-0.4079.rtsw.clev.net.internet2.edu (162.252.70.93) 15.175 ms 15.531 ms 15.542 ms 5 ae-1.4079.rtsw.eqch.net.internet2.edu (162.252.70.131) 25.121 ms 25.082 ms 24.325 ms 6 et-7-0-0.4079.rtsw.minn.net.internet2.edu (162.252.70.107) 31.915 ms 32.184 ms 31.981 ms 7 et-7-0-0.4079.rtsw.miss2.net.internet2.edu (162.252.70.59) 55.142 ms 57.452 ms 55.346 ms 8 et-4-1-0.4079.rtsw.seat.net.internet2.edu (162.252.70.1) 65.376 ms 65.717 ms 65.842 ms 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * I can clone though via https:// (just can't push changes via ssh) > and we both agree about the method how we want to inject the upstream > source there. Debian Science policy says this is done via >gbp import-orig --pristine-tar > while the upstream tarball is obtained via
Bug#909460: Trouble with the sqlite3 upgrade path
Hi, I found the source. Upstream commit ac391519c8e4125db0662dea92e7550d95bd9a16 "Permit catalog to contain negative FileIndexes", added shortly before the 9.2.1 release. This makes me wonder about how these schema updates would reach people that are already on db version 16. For us, we can fix that by adding yet more manual snippets for dbconfig... Sven Hartge wrote: > Looking at the code, it seems we have to create a temp table with the > new schema and then select everything from the old table into it, then > removing the old table and finally renaming the temp table. > > Just like it was done with basefiles_temp. Yes, when I read your mail I remembered having done that before... I'll take care of this, but probably after fixing latex2html and bacula-docs. - Carsten
Bug#907255: marked as done (Missing dependencies (python-monotonic and python-requests))
Your message dated Mon, 24 Sep 2018 15:03:30 + with message-id and subject line Bug#907255: fixed in oz 0.16.0-2 has caused the Debian Bug report #907255, regarding Missing dependencies (python-monotonic and python-requests) 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.) -- 907255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907255 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: oz Version: 0.16.0-1 Severity: normal Dear Maintainer, Looks like the oz binary package is missing a couple of dependencies. Attempting to run the binaries result in error messages like this: $ oz-install Traceback (most recent call last): File "/usr/bin/oz-install", line 25, in import oz.TDL File "/usr/lib/python2.7/dist-packages/oz/TDL.py", line 37, in import oz.ozutil File "/usr/lib/python2.7/dist-packages/oz/ozutil.py", line 45, in import requests ImportError: No module named requests sudo apt install python-monotonic python-requests resolves the issue, so I suppose they should be added as dependencies. Originally reported in Ubuntu as https://bugs.launchpad.net/ubuntu/+source/oz/+bug/1773310 -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-3-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages oz depends on: ii genisoimage 9:1.1.11-3+b2 ii libvirt-dev 4.6.0-2 ii mtools 4.0.18-2.1 ii openssh-client 1:7.7p1-4 ii python 2.7.15-3 ii python-guestfs 1:1.38.4-1 ii python-libvirt 4.6.0-1 ii python-lxml 4.2.4-1 ii python-m2crypto 0.27.0-6 ii python-pycurl7.43.0.1-0.2+b1 oz recommends no packages. oz suggests no packages. -- no debconf information -- mvh / best regards Hans Joachim Desserud http://desserud.org --- End Message --- --- Begin Message --- Source: oz Source-Version: 0.16.0-2 We believe that the bug you reported is fixed in the latest version of oz, 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 907...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon Josefsson (supplier of updated oz 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, 24 Sep 2018 15:17:57 +0200 Source: oz Binary: oz Architecture: source all Version: 0.16.0-2 Distribution: unstable Urgency: low Maintainer: Simon Josefsson Changed-By: Simon Josefsson Description: oz - install virtual machine guest OSs with minimal input the user Closes: 907255 Changes: oz (0.16.0-2) unstable; urgency=low . * Update Standards-Version from 4.0.0 to 4.2.1. * Change debhelper/compat from 9 to 11. * Packaging moved to Salsa, update Vcs-Browser and Vcs-Git. * Use https copyright/Homepage URL. * Put tools in Section: admin. * Drop unnecessary X-Python-Version: >= 2.6. * Re-add python-monotonic and python-requests deps. Closes: #907255. Checksums-Sha1: 71f22ae332dc3b397aa275fed7334983c07e5565 1467 oz_0.16.0-2.dsc 7bdbec59abffc16bd4e52d30c45a3c16dd80d01f 3004 oz_0.16.0-2.debian.tar.xz 748cdfad6284b1875db4aa3001549979f097bcdf 88532 oz_0.16.0-2_all.deb 221528e83511a2316c467a6f97987ea2b4eee10d 5630 oz_0.16.0-2_amd64.buildinfo Checksums-Sha256: ae2e2f54391a287da5b8d808acf385a238e623b73e49102e27f3dd3085dd14e2 1467 oz_0.16.0-2.dsc f88755743faf9d953334c1ac65c9186429effe33722eb30e691fa8d0fe3b0e6b 3004 oz_0.16.0-2.debian.tar.xz b73404197b53c6427431ad1ba34f839cd90fcd2f339f0572fb3cd82dfb49b2c4 88532 oz_0.16.0-2_all.deb d9d090cefe279aaeeeafb0fb404356f9f55bb0ce07cc946f7902b88eb3be4b09 5630 oz_0.16.0-2_amd64.buildinfo Files: a10442a294e5b46800a6faad38c15820 1467 python optional oz_0.16.0-2.dsc 00ddd2973529ab6222b117af760d28c5 3004 python optional oz_0.16.0-2.debian.tar.xz fb3e679ce96f8610019a71021b997ed9 88532 admin optional oz_0.16.0-2_all.deb be7b86b4f8344a84e183dafc07348d89 5630 python optional oz_0.16.0-2_amd64.buildinfo
Bug#909343: marked as done (libcatalyst-perl: fails to build with libmoosex-getopt-perl 0.73-1)
Your message dated Mon, 24 Sep 2018 14:55:34 + with message-id and subject line Bug#909343: fixed in libcatalyst-perl 5.90119-1 has caused the Debian Bug report #909343, regarding libcatalyst-perl: fails to build with libmoosex-getopt-perl 0.73-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.) -- 909343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909343 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libcatalyst-perl Version: 5.90118-1 Severity: serious Tags: upstream sid buster Justification: fails to build from source Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=127050 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 As first noticed by ci.debian.net, one test in libcatalyst-perl fails with the new libmoosex-getopt-perl 0.73-1. t/aggregate/unit_core_script_help.t ... No subtests run … Test Summary Report - --- t/aggregate/unit_core_script_help.t (Wstat: 0 Tests: 0 Failed: 0) Parse errors: No plan found in TAP output The upstream report at https://rt.cpan.org/Public/Bug/Display.html?id=127050 is undecided if the problem is in Catalyst-Runtime or in MooseX-Getopt, there's also https://rt.cpan.org/Ticket/Display.html?id=127096 Cheers, gregor -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlulr4FfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgbYCA//c9H7i6yDCv1RCgKhxvO4uLY1BJEdYAw+uidNV2aLXXyUfCueJorewdHN ccZirNKbRwxkkIQtSZYCB0qvlhM0RRdk8//aXR+FM+hSiVeEXp/HRXNrAKji19jT 6JJJkRSoTNEkvc0OIgdi/ljRgKS27r+DLBfFjKV18IiTAdfO45Dbz1zso/7QGkUa tRGTaP9B3jOVTYT9sCB0UFfvtpDuQ9Svl+aWFY4VIGPDbF/1j4Y5QWf/BdXqsyuN 9Gukw2Zy2RxGYTZ4diHR8Dwh9WGzvX9FBZUkkT39EbtqYPazSF0X4QryTXt4KKQ/ 0QDTLQV4EAaXp3GP472LCPNvmZxBUg75QEeczC++gAQCFnnTYjW90PvntNEIy3uV BaIXbkXEdai8A1vDn3ay8gqOPukcASIDwnqYp7GCmpheru4RofBWzxPnxPfB0k+T 2yo4fkPIjXbttrCUmQ2Wlki8ZMuyfhfJN9SFuGxsoOEg+xRSDgum34Hd7Isr99Gi 0hWTpxZYepyUGDx+mJm3m7SpzWZeeH1xj6cJUgzS23UzEkaHyB4ZmVaLFOFvkMhB YDFDrJjZkBV+53oNNiahJ434GMZWdrqcvko+FxFtYvGpusEaF6YVwQpJe+oeSx3P 913F96sBqq/cfNEcEjQJF4shi6yrWInGGzZxTefVJsG2EdQsboM= =632F -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: libcatalyst-perl Source-Version: 5.90119-1 We believe that the bug you reported is fixed in the latest version of libcatalyst-perl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 909...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated libcatalyst-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 24 Sep 2018 16:28:12 +0200 Source: libcatalyst-perl Binary: libcatalyst-perl Architecture: source Version: 5.90119-1 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: gregor herrmann Closes: 909343 Description: libcatalyst-perl - elegant Model-View-Controller Web Application Framework Changes: libcatalyst-perl (5.90119-1) unstable; urgency=medium . * Import upstream version 5.90119. Fixes "fails to build with libmoosex-getopt-perl 0.73-1" (Closes: #909343) * Declare compliance with Debian Policy 4.2.1. Checksums-Sha1: 8ceedf24dba5e9f45da3eced91ec73a1afb6b910 4006 libcatalyst-perl_5.90119-1.dsc 42139cd50dc689e392851e1b4485b31aa82530f2 374755 libcatalyst-perl_5.90119.orig.tar.gz 96f2aca2138f8a4c29ae9c91bf98d12cc21b9d7b 11752 libcatalyst-perl_5.90119-1.debian.tar.xz Checksums-Sha256: 58fc56fcb1337693dbfea9f8315f22da363ba89cac6f99791970d606ccbc0c09 4006 libcatalyst-perl_5.90119-1.dsc 19fff77c70a4fc8df2909db82629fda7f25d3e5d01f0152a145f8f8973ea87c7 374755 libcatalyst-perl_5.90119.orig.tar.gz 78b3d2141120b02f7533aab8a5606a87b0c2f0e5ee13f4b3404a1749ad790244 11752 libcatalyst-perl_5.90119-1.debian.tar.xz Files: 86c8e5b40f7a26015a677de1797aa8d4 4006 perl optional libcatalyst-perl_5.90119-1.dsc cf048e4adefa99b9e43b221caeffc188 374755 perl optional libcatalyst-perl_5.90119.orig.tar.gz 9f6788d0488e6657d4ba812004ce7d54 11752 perl optional
Bug#905114: marked as done (gnome-shell-extension-multi-monitors: global.screen is not available in GNOME Shell 3.29)
Your message dated Mon, 24 Sep 2018 14:55:12 + with message-id and subject line Bug#905114: fixed in gnome-shell-extension-multi-monitors 0.00~git20180920.1.0ca053f-1 has caused the Debian Bug report #905114, regarding gnome-shell-extension-multi-monitors: global.screen is not available in GNOME Shell 3.29 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.) -- 905114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905114 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-shell-extension-multi-monitors Version: 0.00~git20171014.1.df5d6e4-1 Severity: important Tags: upstream experimental User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: shell-3.30 According to codesearch.debian.net, this extension uses the MetaScreen via global.screen. MetaScreen no longer exists in GNOME 3.29, which is starting to become available in experimental. This extension will need code changes to use the MetaDisplay (global.display), MetaWorkspaceManager (global.workspace_manager), MetaMonitorManager (Meta.MonitorManager.get()) or MetaX11Display (global.display.get_x11_display()). Because GNOME 3.29/3.30 is not a stable release yet and is not in Debian unstable yet, you'll probably need to condition on the GNOME Shell version. smcv --- End Message --- --- Begin Message --- Source: gnome-shell-extension-multi-monitors Source-Version: 0.00~git20180920.1.0ca053f-1 We believe that the bug you reported is fixed in the latest version of gnome-shell-extension-multi-monitors, 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 905...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonathan Carter (supplier of updated gnome-shell-extension-multi-monitors package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 24 Sep 2018 15:21:25 +0200 Source: gnome-shell-extension-multi-monitors Binary: gnome-shell-extension-multi-monitors Architecture: source all Version: 0.00~git20180920.1.0ca053f-1 Distribution: unstable Urgency: medium Maintainer: Jonathan Carter Changed-By: Jonathan Carter Description: gnome-shell-extension-multi-monitors - Better support for additional monitors in GNOME shell Closes: 905114 Changes: gnome-shell-extension-multi-monitors (0.00~git20180920.1.0ca053f-1) unstable; urgency=medium . * New upstream snapshot (Closes: #905114) * debian/control: - Update standards version to 4.2.1 - Update compat to level 11 - Depend on minimum gnome-shell version 3.24 - Move git repository to salsa.debian.org service - Add Debian GNOME Maintainers to uploaders * debian/changelog: Update copyright years Checksums-Sha1: 3038dad260aa5d3d8c50f462b4be36493667ac5a 2452 gnome-shell-extension-multi-monitors_0.00~git20180920.1.0ca053f-1.dsc 17d74816d8518214261ce7a0d15d01b783a9f498 39117 gnome-shell-extension-multi-monitors_0.00~git20180920.1.0ca053f.orig.tar.gz 975460361ea23d9c7e25252a02fea63af0d72335 2796 gnome-shell-extension-multi-monitors_0.00~git20180920.1.0ca053f-1.debian.tar.xz 79d1512efcc7a16740e48d4fdede1295b683d474 29200 gnome-shell-extension-multi-monitors_0.00~git20180920.1.0ca053f-1_all.deb 493db32ab65760ea52123d0325d3c63d1c33f76a 5844 gnome-shell-extension-multi-monitors_0.00~git20180920.1.0ca053f-1_amd64.buildinfo Checksums-Sha256: 4d602893ec1e1645c8f53a8766c93bc5d6d828038348d285a1ddecb259a618ac 2452 gnome-shell-extension-multi-monitors_0.00~git20180920.1.0ca053f-1.dsc aa8375689acf50cfcd90442598cb3916a5995d8a1becef8f00d8b7bd43cbf970 39117 gnome-shell-extension-multi-monitors_0.00~git20180920.1.0ca053f.orig.tar.gz a6dfe37a5949f1c7ddc8c029dc0b14c19ac6ccd409a6f26ee1811674ad177049 2796 gnome-shell-extension-multi-monitors_0.00~git20180920.1.0ca053f-1.debian.tar.xz 34792178fa6db32d75adb540e51c4ffe7f25cbb6bb55f63815718712fa405df5 29200 gnome-shell-extension-multi-monitors_0.00~git20180920.1.0ca053f-1_all.deb 281121f655b35305c647bbb780ee1706678e743412755203bf84ea0b7a4dea74 5844 gnome-shell-extension-multi-monitors_0.00~git20180920.1.0ca053f-1_amd64.buildinfo Files: c1e748e7b96a926f01994a5db6c41913 2452 gnome optional
Bug#902817: marked as done (fail2ban: SyntaxError when run with python3.7)
Your message dated Mon, 24 Sep 2018 14:54:20 +
with message-id
and subject line Bug#902817: fixed in fail2ban 0.10.2-2.1
has caused the Debian Bug report #902817,
regarding fail2ban: SyntaxError when run with python3.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.)
--
902817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902817
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fail2ban
Version: 0.10.2-2
Severity: important
fail2ban uses 'async' as a parameter/variable name. But it's a
reserved keyword in python3.7.
I found the problem in this CI build:
https://salsa.debian.org/freedombox-team/plinth/-/jobs/28625
Setting up fail2ban (0.10.2-2) ...
File "/usr/lib/python3/dist-packages/fail2ban/client/fail2banclient.py", line
231
def configureServer(self, async=True, phase=None):
^
SyntaxError: invalid syntax
File "/usr/lib/python3/dist-packages/fail2ban/client/fail2banserver.py", line
173
async = self._conf.get("async", False)
^
SyntaxError: invalid syntax
dpkg: error processing package fail2ban (--configure):
installed fail2ban package post-installation script subprocess returned error
exit status 1
--- End Message ---
--- Begin Message ---
Source: fail2ban
Source-Version: 0.10.2-2.1
We believe that the bug you reported is fixed in the latest version of
fail2ban, 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 902...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mattia Rizzolo (supplier of updated fail2ban 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, 23 Sep 2018 20:14:23 +0200
Source: fail2ban
Binary: fail2ban
Architecture: source
Version: 0.10.2-2.1
Distribution: unstable
Urgency: medium
Maintainer: Yaroslav Halchenko
Changed-By: Mattia Rizzolo
Description:
fail2ban - ban hosts that cause multiple authentication errors
Closes: 902817
Changes:
fail2ban (0.10.2-2.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Add patch from upstream to fix SyntaxError with Python 3.7. Closes: #902817
Checksums-Sha1:
fa719c45b76046892f656e2ffef3c443e096f763 1936 fail2ban_0.10.2-2.1.dsc
4e6b594a26bef65085aec770a8e178628b81630c 30680
fail2ban_0.10.2-2.1.debian.tar.xz
747b6a06e6180fe8ddbb666998b2671340c1db96 6042
fail2ban_0.10.2-2.1_amd64.buildinfo
Checksums-Sha256:
118a9d679cdb3512bd5e4be68251a21c72535d724d99a142177735274154d386 1936
fail2ban_0.10.2-2.1.dsc
980f216b5402bc9c9314b7f0f5ad17b953e0652f47227e199c2f2a65319b0e04 30680
fail2ban_0.10.2-2.1.debian.tar.xz
e1e4fa21b33021796e175899b643623043a4b65cac71bd0b2b864cdfe63a3d42 6042
fail2ban_0.10.2-2.1_amd64.buildinfo
Files:
a4f9849b81537642e14c50e3a32e 1936 net optional fail2ban_0.10.2-2.1.dsc
9e75956fde9743a6b1f371e96e20d224 30680 net optional
fail2ban_0.10.2-2.1.debian.tar.xz
aa9b45a95e5a9cbe9f91faa17bf01660 6042 net optional
fail2ban_0.10.2-2.1_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAlun2dwACgkQCBa54Yx2
K624AQ//edVsIrnNh4rdl7HyBeBUDczTinJ4oSIdg0jFKuoLAEnhZsWpLNz8aoMi
alrONKM1mgPZ4VX+OuK5qCh7y2t27SSzWdXC/4vnvi9eayZUv6zPfUl9fwmUz5Ui
KEoYqegmufrL8USE5iA0VCNm0p9XUTnR/KT+vfwBevwmZNAaruvc+YY4+c/AyiHf
QHx+asZ+ibfOh5YHSyYlvRrjLIes6iYnNw42h8e5ogc7K1Wz/mq2nupUaJnC/wgX
NCqaCZirafKqvf6D5MSHS0a9IxIFF8T/eEddynqzrJtSR8hoIfWXPvNWb5QpRLg3
69NZCKcVEU000maoKBaJVX3yK1QrIlRSewU4uZLyTw6OABUOkrd/HE7DuZpQ53tY
VNxD7f/Zlr+zchDuCgkbX3MlU4tgRyTLgP+N60mqsHoWHgYHmJssa9tZBueBdAyd
Fij5iWES1hc/UidYum5Cm02LuZDD67v4jAyYsYWCuSgCH/tixRHb12H16bsRY6zY
mNyWFX3Nz7TbEM28pzHJdAgDWFSuHyXw2DOt2BiCKGYhs0xvLEXvZMDzoYs3vS3z
nFxMEdbQmqxPOmGIb/ZUMnIZR0dT4Hd70jzGK+Z6nzF2KAPR9X7lTLA1k7PC7XaD
P95z87EWYHzutmSzHMMA9HFb/OoIOhKt82z4a67RArJoK+ukOx0=
=7IGE
-END PGP SIGNATURE End Message ---
Processed: found 771085 in 3.30.0-1, found 858954 in 0.7.4.0+nmu1, found 668393 in 0.5.17-1.2 ...
Processing commands for cont...@bugs.debian.org:
> found 771085 3.30.0-1
Bug #771085 [gdm3] gdm3: unowned symlink after purge (policy 6.8, 10.8):
/etc/systemd/system/display-manager.service
Marked as found in versions gdm3/3.30.0-1.
> found 858954 0.7.4.0+nmu1
Bug #858954 [diaspora-common] diaspora-common: unowned directories after purge:
/var/cache/diaspora/, /var/lib/diaspora-common/, /var/log/diaspora/
Marked as found in versions diaspora-installer/0.7.4.0+nmu1.
> found 668393 0.5.17-1.2
Bug #668393 [dtc-xen] dtc-xen: unowned directory after purge: /etc/xen/auto/
Marked as found in versions dtc-xen/0.5.17-1.2.
> found 782156 2.02+dfsg1-6
Bug #782156 [grub-xen] grub-xen: unowned files after purge (policy 6.8, 10.8):
/boot/grub/{locale, x86_64-xen}/* and some more
Marked as found in versions grub2/2.02+dfsg1-6.
> unarchive 668751
Bug #668751 {Done: Mattia Rizzolo } [liquidsoap] liquidsoap:
unowned directory after purge: /usr/share/liquidsoap
Unarchived Bug 668751
> found 668751 1.3.3-2
Bug #668751 {Done: Mattia Rizzolo } [liquidsoap] liquidsoap:
unowned directory after purge: /usr/share/liquidsoap
Marked as found in versions liquidsoap/1.3.3-2 and reopened.
> found 905513 0.77.1-1
Bug #905513 [sbuild-debian-developer-setup] sbuild-debian-developer-setup:
unowned files after purge (policy 6.8, 10.8): /var/log/sbuild-update-all.log
Marked as found in versions sbuild/0.77.1-1.
> severity 909030 serious
Bug #909030 [libnewt0.52] libnewt0.52: preinst removes conffile shipped in the
package
Severity set to 'serious' from 'normal'
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 909030 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 829255 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 907848 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 907848 + libgtk2.0-common libgtk2.0-bin
Bug #907848 [libgtk2.0-0] libgtk2.0-0: Broken symlink:
/usr/share/doc/libgtk2.0-0/changelog.gz
Added indication that 907848 affects libgtk2.0-common and libgtk2.0-bin
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
668393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668393
668751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668751
771085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771085
782156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782156
858954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858954
905513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905513
907848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907848
909030: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909030
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#909440: meson: missing dependency on python3-pkg-resources
On Sun, Sep 23, 2018 at 11:21 PM Jeremy Bicha wrote: > On Sun, Sep 23, 2018 at 10:53 PM Jussi Pakkanen wrote: > > On Sun, Sep 23, 2018 at 10:03 AM Jeremy Bicha wrote: > > > > > I tried building a package (gnome-games-app) using meson but the build > > > fails now. I guess meson needs to depend on python3-pkg-resources . > > > > No. We are not permitted to depend on anything outside of Python > > standard library. Thought looking at the package info that package is > > provided by setuptools which is a bit of an edge case because > > distutils is a bit neglected AFAICT. > > This issue means that everything using meson in Debian fails to build > right now. Specifically, this is blocking us from being able to do the > GNOME 3.30.1 updates this week. > > So I think a temporary fix now would be appropriate and then you can > take more time to figure out a different solution if you like. You might want to look at https://github.com/mesonbuild/meson/pull/4004 if you're still wondering how this change happened. May I do an NMU to add the dependency to unbreak things? Thanks, Jeremy Bicha
Bug#907491: closed by Paul Gevers (Re: goobook fails to authenticate)
Hi Ilias,
Nope. It's not python-httplib2. Can't find what can it be:
root@izta:~# pip uninstall python-httplib2
Cannot uninstall requirement python-httplib2, not installed
root@izta:~# dpkg -l python-httplib2
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==---==
ii python-httplib 0.11.3-1 all comprehensive HTTP client library
root@izta:~# ls -l /usr/lib/python2.7/dist-packages/httplib2/
total 180
-rw-r--r-- 1 root root 73431 Sep 5 01:45 __init__.py
-rw-r--r-- 1 root root 59427 Sep 9 13:05 __init__.pyc
-rw-r--r-- 1 root root 3828 Mar 29 20:28 iri2uri.py
-rw-r--r-- 1 root root 3786 Sep 9 13:05 iri2uri.pyc
-rw-r--r-- 1 root root 18999 Mar 29 20:28 socks.py
-rw-r--r-- 1 root root 17500 Sep 9 13:05 socks.pyc
Cheers,
Sergio.
--
Sergio Mendoza
Instituto de Astronomia, UNAM
http://www.mendozza.org/sergio
On Sat, Sep 22, 2018 at 02:36:45PM +0300, Ilias Tsitsimpis wrote:
> Hi again,
>
> On Fri, Sep 21, 2018 at 01:46PM, Sergio Mendoza wrote:
> > Unfortunately, no matter how hard I look for to spot the problem, I have
> > not find the culprit package. I tried and tried, but couldn't. This is
> > the reason I reported the bug to goobook. Sorry for not being more
> > helpful.
> >
> > > > sergio@izta:~$ goobook query sergio
> > > > Traceback (most recent call last):
> > > > File "/usr/bin/goobook", line 11, in
> > > > load_entry_point('goobook==1.9', 'console_scripts', 'goobook')()
> > > > File "/usr/share/goobook/goobook/application.py", line 94, in main
> > > > args.func(config, args)
> > > > File "/usr/share/goobook/goobook/application.py", line 125, in
> > > > do_query
> > > > goobk = GooBook(config)
> > > > File "/usr/share/goobook/goobook/goobook.py", line 59, in __init__
> > > > self.cache.load()
> > > > File "/usr/share/goobook/goobook/goobook.py", line 257, in load
> > > > self.update()
> > > > File "/usr/share/goobook/goobook/goobook.py", line 264, in update
> > > > self.contacts = list(self._parse_contacts(gc.fetch_contacts()))
> > > > File "/usr/share/goobook/goobook/goobook.py", line 395, in
> > > > fetch_contacts
> > > > res = self._get(query)
> > > > File "/usr/share/goobook/goobook/goobook.py", line 371, in _get
> > > > connection_type=httplib2.HTTPSConnectionWithTimeout)
> > > > File "/usr/local/lib/python2.7/dist-packages/oauth2client/client.py",
> > > > line 562, in new_request
> > > > redirections, connection_type)
> > > > File "/usr/local/lib/python2.7/dist-packages/httplib2/__init__.py",
> > > > line 1608, in request
> > > > (response, content) = self._request(conn, authority, uri,
> > > > request_uri, method, body, headers, redirections, cachekey)
> > > > File "/usr/local/lib/python2.7/dist-packages/httplib2/__init__.py",
> > > > line 1350, in _request
> > > > (response, content) = self._conn_request(conn, request_uri, method,
> > > > body, headers)
> > > > File "/usr/local/lib/python2.7/dist-packages/httplib2/__init__.py",
> > > > line 1272, in _conn_request
> > > > conn.connect()
> > > > File "/usr/local/lib/python2.7/dist-packages/httplib2/__init__.py",
> > > > line 1059, in connect
> > > > raise SSLHandshakeError(e)
> > > > httplib2.SSLHandshakeError: [SSL: CERTIFICATE_VERIFY_FAILED]
> > > > certificate verify failed (_ssl.c:726)
> > >
> > > The above traceback mentions
> > > "/usr/local/lib/python2.7/dist-packages/httplib2/__init__.py".
> > > This is not the canonical location where Debian Python packages get
> > > installed. I believe you have installed a different version of the
> > > httplib2 module using pip. Could you please test using the Python module
> > > provided by the python-httplib2 package?
>
> Please take a look at the comment above. It looks like you are not using
> the official Debian package for python-httplib2, which is installed
> under /usr/lib/python2.7/dist-packages/httplib2/ [1]. My guess is that
> you have `pip install`-ed that package, so I would start by uninstalling
> it and revert back to the Debian one.
>
> [1] https://packages.debian.org/sid/all/python-httplib2/filelist
>
> Cheers,
>
> --
> Ilias
Bug#907806: How to disable tests for Python2 only?
Hi Yaroslav, On Mon, Sep 24, 2018 at 09:40:49AM -0400, Yaroslav Halchenko wrote: > > On Mon, 24 Sep 2018, Andreas Tille wrote: > > > When you talked about new upstream version: Do you want to give 0.20rc1 > > I did give it a try... > > From the now empty list of > https://github.com/scikit-learn/scikit-learn/issues/created_by/yarikoptic it > might be that all of the ones I've filed are addressed by now, BUT I do not > see > them in > > $> git lg 0.20rc1..origin/0.20.X > * c196ec405 - (origin/0.20.X) Remove OPTICS from 0.20 (#12053) (7 days ago) > [Joel Nothman] > * 17f8016c5 - Bugfix release of joblib that also restores PyPy support > (#12012) (3 weeks ago) [Olivier Grisel] > * c40726e91 - CI handle sparse checkout with new branch (4 weeks ago) [Joel > Nothman] > * 96a3e21fb - CI Verbosity in push_doc (4 weeks ago) [Joel Nothman] > * 9c3ecb2c4 - CI use correct scikit-learn.github.io branch (4 weeks ago) > [Joel Nothman] > * 061343e9f - CI Only try to remove docs dir if present (4 weeks ago) [Joel > Nothman] > > so might have been fixed in master, and not backported yet, which indeed > might be the case: > https://github.com/scikit-learn/scikit-learn/issues/12016#issuecomment-419079493 You asked me to clone http://github.com/yarikoptic/scikit-learn to https://salsa.debian.org/science-team/scikit-learn which I did. In *your* packaging repository is no branch 0.20rc1 those commits would be either needed to be imported as quilt patches or alternatively you can use git mode in d/watch which creates a new tarball for you incorporating the latest state of upstream Git (I doubt that would be a sensible solution in the current case). > > a try or do you want to wait for 0.20? > > regarding push to salsa: > > something is funky with salsa or with my network? > > (git)hopa:~deb/scikit-learn[debian-0.20] > $> git remote add salsa g...@salsa.debian.org:science-team/scikit-learn.git > > $> git fetch salsa > ssh: connect to host salsa.debian.org port 22: Network is unreachable > fatal: Could not read from remote repository. > > Please make sure you have the correct access rights > and the repository exists. I have no trouble with accessing the repository on Salsa. > Meanwhile, debian-0.20 branch is on > http://github.com/yarikoptic/scikit-learn I admit I'm not sure what you want me to do next. It somehow smells like using git mode in debian/watch and try to extract your commits to debian/ dir via `git format-patch` and import these into Debian Science repository via `git am`. However, I do not see this as very promising since I'm not sure whether you are really in favour to migrate to Debian Science or rather stick to your workflow. So before I start spending time into this it would be helpful if you confirm that you can gbp clone g...@salsa.debian.org:science-team/scikit-learn.git and we both agree about the method how we want to inject the upstream source there. Debian Science policy says this is done via gbp import-orig --pristine-tar while the upstream tarball is obtained via uscan or some get-orig-source script in exceptional cases. What do you think about this? Kind regards Andreas. -- http://fam-tille.de
Bug#902817: fail2ban: diff for NMU version 0.10.2-2.1
On Sun, 23 Sep 2018, Mattia Rizzolo wrote: > Control: tags 902817 + patch > Control: tags 902817 + pending > Dear maintainer, > I've prepared an NMU for fail2ban (versioned as 0.10.2-2.1) and > uploaded it to DELAYED/2. Please feel free to tell me if I > should delay it longer. I guess if tests pass, should be ok and no need to delay Thank you! > Regards. -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik signature.asc Description: PGP signature
Bug#907806: How to disable tests for Python2 only?
On Mon, 24 Sep 2018, Andreas Tille wrote: > When you talked about new upstream version: Do you want to give 0.20rc1 I did give it a try... From the now empty list of https://github.com/scikit-learn/scikit-learn/issues/created_by/yarikoptic it might be that all of the ones I've filed are addressed by now, BUT I do not see them in $> git lg 0.20rc1..origin/0.20.X * c196ec405 - (origin/0.20.X) Remove OPTICS from 0.20 (#12053) (7 days ago) [Joel Nothman] * 17f8016c5 - Bugfix release of joblib that also restores PyPy support (#12012) (3 weeks ago) [Olivier Grisel] * c40726e91 - CI handle sparse checkout with new branch (4 weeks ago) [Joel Nothman] * 96a3e21fb - CI Verbosity in push_doc (4 weeks ago) [Joel Nothman] * 9c3ecb2c4 - CI use correct scikit-learn.github.io branch (4 weeks ago) [Joel Nothman] * 061343e9f - CI Only try to remove docs dir if present (4 weeks ago) [Joel Nothman] so might have been fixed in master, and not backported yet, which indeed might be the case: https://github.com/scikit-learn/scikit-learn/issues/12016#issuecomment-419079493 > a try or do you want to wait for 0.20? regarding push to salsa: something is funky with salsa or with my network? (git)hopa:~deb/scikit-learn[debian-0.20] $> git remote add salsa g...@salsa.debian.org:science-team/scikit-learn.git $> git fetch salsa ssh: connect to host salsa.debian.org port 22: Network is unreachable fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. Meanwhile, debian-0.20 branch is on http://github.com/yarikoptic/scikit-learn -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik
Bug#903432: downgrading severity
Control: severity -1 important We are close fixing the issues in the autopkg tests and the syntax errors. Downgrading this report to get proper britney resuilts.
Processed: downgrading severity
Processing control commands: > severity -1 important Bug #903432 [python3-minimal] Block testing migration of python3-defaults until #902788 is fixed Severity set to 'important' from 'serious' -- 903432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903432 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909492: calamares-settings-debian: removes files that were installed by another package: /usr/share/applications/calamares.desktop.orig
Package: calamares-settings-debian
Version: 10.0.10-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package removes files that
were installed by another package.
The removed files were already present before the package was installed,
they may have been shipped or created by a dependency.
This could be a violation of policy 10.7.4 ("Sharing configuration
files"), see
https://www.debian.org/doc/debian-policy/ch-files.html#sharing-configuration-files
or policy chapter 6 ("Package maintainer scripts..."), see
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html
or policy 7.6 ("Overwriting files..."), see
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
If a directory is used by several packages, all should ship it as part
of the package (possibly empty, using $package.dirs to create it), and
no package should mkdir/rmdir it in the maintainer scripts as dpkg will
take care of this.
>From the attached log (scroll to the bottom...):
1m11.7s ERROR: FAIL: debsums reports modifications inside the chroot:
debsums: missing file /usr/share/applications/calamares.desktop.orig (from
calamares package)
cheers,
Andreas
calamares-settings-debian_10.0.10-1.log.gz
Description: application/gzip
Bug#909490: pylint: doesn't support Python 3.7
Source: pylint Version: 1.9.2-1 Severity: serious pylint needs the same care astroid received yesterday, being split into a package version 1.9.2 building the py2 variant, and another version 2.1.1 building the py3 variant. Possibly sooner rather than later, things have been stalled for months already. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Processed: Re: Bug#903989: vcr.py: autopkgtest needs update for python3.7 in supported versions
Processing control commands: > severity -1 serious Bug #903989 [src:vcr.py] vcr.py: autopkgtest needs update for python3.7 in supported versions Severity set to 'serious' from 'normal' -- 903989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903989 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#893645: marked as done (os-autoinst: FTBFS: FAIL: 02-test_ocr.t)
Your message dated Mon, 24 Sep 2018 13:07:16 +
with message-id
and subject line Bug#893645: fixed in os-autoinst 4.5.1527308405.8b586d5-1
has caused the Debian Bug report #893645,
regarding os-autoinst: FTBFS: FAIL: 02-test_ocr.t
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.)
--
893645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893645
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: os-autoinst
Version: 4.4.1508936943.39adc5eb-2
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic
In addition to bug #880791, os-autoinst now fails to build with a second
test failure:
[...]
FAIL: 02-test_ocr.t
===
Use of uninitialized value in index at ../needle.pm line 44.
Use of uninitialized value $bmwqemu::vars{"PRJDIR"} in addition (+) at
../needle.pm line 45.
20:27:15.8564 433 MATCH(bootmenu-ocr.ref:1.00)
Tesseract Open Source OCR Engine v4.00.00alpha with Leptonica
Warning. Invalid resolution 0 dpi. Using 70 instead.
Estimating resolution as 132
Tesseract Open Source OCR Engine v4.00.00alpha with Leptonica
Warning. Invalid resolution 0 dpi. Using 70 instead.
Estimating resolution as 138
ok 1 - ocr match 1
Tesseract Open Source OCR Engine v4.00.00alpha with Leptonica
Warning. Invalid resolution 0 dpi. Using 70 instead.
Estimating resolution as 132
Tesseract Open Source OCR Engine v4.00.00alpha with Leptonica
Warning. Invalid resolution 0 dpi. Using 70 instead.
Estimating resolution as 138
not ok 2 - multiple OCR regions
# Failed test 'multiple OCR regions'
# at ./02-test_ocr.t line 42.
1..2
# Looks like you failed 1 test of 2.
FAIL 02-test_ocr.t (exit status: 1)
[...]
First seen in Ubuntu at
,
this failure is also reproducible in unstable.
Perhaps this is a regression in, or incompatibility with, tesseract-ocr
4.00. (The last successful builds of os-autoinst in Debian used
tesseract-ocr 3.04.01-6.)
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: os-autoinst
Source-Version: 4.5.1527308405.8b586d5-1
We believe that the bug you reported is fixed in the latest version of
os-autoinst, 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 893...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Hideki Yamane (supplier of updated os-autoinst package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 24 Sep 2018 20:48:29 +0900
Source: os-autoinst
Binary: os-autoinst
Architecture: source
Version: 4.5.1527308405.8b586d5-1
Distribution: unstable
Urgency: medium
Maintainer: Hideki Yamane
Changed-By: Hideki Yamane
Description:
os-autoinst - automated testing of Operating Systems
Closes: 880791 893645
Changes:
os-autoinst (4.5.1527308405.8b586d5-1) unstable; urgency=medium
.
* New upstream release
* debian/patches
- refresh patch
- add 0003-adjust-to-avoid-ocr-test-failure.patch (Closes: #893645)
- add 0004-avoid-make-check-doc-failure.patch
- add 0005-set-perl-path.patch to avoid lintian error
* debian/control
- add Build-Depends: libsocket-msghdr-perl, spell for test
- move Vcs-* to salsa.debian.org
* debian/rules
- set --no-parallel for dh_auto_test to avoid random test failure
(Closes: #880791)
Checksums-Sha1:
b696bc921ad82766e2ed3c43d0f26b7b7088e331 2782
os-autoinst_4.5.1527308405.8b586d5-1.dsc
b4030943fcf5c983dd6bb762ea7da9d8d57be986 20456277
os-autoinst_4.5.1527308405.8b586d5.orig.tar.gz
1ee2cf7273440fe4ebb0640fe8b988b44fbfc59e 4644
os-autoinst_4.5.1527308405.8b586d5-1.debian.tar.xz
abd54b9cb1db4b05ce9157c1217b097f5c0a90ad 21825
os-autoinst_4.5.1527308405.8b586d5-1_amd64.buildinfo
Checksums-Sha256:
Bug#880791: marked as done (os-autoinst FTBFS frequently: FAIL 99-full-stack.t)
Your message dated Mon, 24 Sep 2018 13:07:16 + with message-id and subject line Bug#880791: fixed in os-autoinst 4.5.1527308405.8b586d5-1 has caused the Debian Bug report #880791, regarding os-autoinst FTBFS frequently: FAIL 99-full-stack.t 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.) -- 880791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880791 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: os-autoinst Version: 4.4.1508936943.39adc5eb-1 Severity: serious https://buildd.debian.org/status/package.php?p=os-autoinst=sid ... ok 1 - test executed fine ok 2 - Snapshots are enabled ok 3 - Wait idle waits for a second. ok 4 - test type string and do not wait ok 5 - test type string and wait for 5 seconds ok 6 - test type string and wait for 10 seconds ok 7 - test type string and wait for 20 seconds not ok 8 - Result in testresults/result-boot.json is ok # Failed test 'Result in testresults/result-boot.json is ok' # at ./99-full-stack.t line 69. # got: 'fail' # expected: 'ok' Bail out! testresults/result-boot.json failed FAIL 99-full-stack.t (exit status: 255) Testsuite summary for os-autoinst 1.1.0 # TOTAL: 17 # PASS: 16 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See t/test-suite.log Please report to https://github.com/os-autoinst/os-autoinst Makefile:526: recipe for target 'test-suite.log' failed make[4]: *** [test-suite.log] Error 1 --- End Message --- --- Begin Message --- Source: os-autoinst Source-Version: 4.5.1527308405.8b586d5-1 We believe that the bug you reported is fixed in the latest version of os-autoinst, 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 880...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hideki Yamane (supplier of updated os-autoinst package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 24 Sep 2018 20:48:29 +0900 Source: os-autoinst Binary: os-autoinst Architecture: source Version: 4.5.1527308405.8b586d5-1 Distribution: unstable Urgency: medium Maintainer: Hideki Yamane Changed-By: Hideki Yamane Description: os-autoinst - automated testing of Operating Systems Closes: 880791 893645 Changes: os-autoinst (4.5.1527308405.8b586d5-1) unstable; urgency=medium . * New upstream release * debian/patches - refresh patch - add 0003-adjust-to-avoid-ocr-test-failure.patch (Closes: #893645) - add 0004-avoid-make-check-doc-failure.patch - add 0005-set-perl-path.patch to avoid lintian error * debian/control - add Build-Depends: libsocket-msghdr-perl, spell for test - move Vcs-* to salsa.debian.org * debian/rules - set --no-parallel for dh_auto_test to avoid random test failure (Closes: #880791) Checksums-Sha1: b696bc921ad82766e2ed3c43d0f26b7b7088e331 2782 os-autoinst_4.5.1527308405.8b586d5-1.dsc b4030943fcf5c983dd6bb762ea7da9d8d57be986 20456277 os-autoinst_4.5.1527308405.8b586d5.orig.tar.gz 1ee2cf7273440fe4ebb0640fe8b988b44fbfc59e 4644 os-autoinst_4.5.1527308405.8b586d5-1.debian.tar.xz abd54b9cb1db4b05ce9157c1217b097f5c0a90ad 21825 os-autoinst_4.5.1527308405.8b586d5-1_amd64.buildinfo Checksums-Sha256: 05335604a69def90d95fdb7ea9ac425c7ed552e64bcc420de51c343cb9ef111e 2782 os-autoinst_4.5.1527308405.8b586d5-1.dsc 6b08eb766a8241d255e5956ad3af671aae1ace59ad85e6951acdda02d98b92c0 20456277 os-autoinst_4.5.1527308405.8b586d5.orig.tar.gz 5721b7330303c888b28a760d076aabc14a68e3d75b40fa055b75b71f9283244e 4644 os-autoinst_4.5.1527308405.8b586d5-1.debian.tar.xz 1195caa9c4dca5b8205ce044d4f75e8d0b57a142aebc03134e900d5b518ddb13 21825 os-autoinst_4.5.1527308405.8b586d5-1_amd64.buildinfo Files: ac5e0188adcf51949c2355ba5ad122a5 2782 devel optional os-autoinst_4.5.1527308405.8b586d5-1.dsc 8b9b82092023ec260d37d65beee70049 20456277 devel optional
Bug#904646: marked as done (python-hypothesis fails imports with Python 3.7)
Your message dated Mon, 24 Sep 2018 13:08:07 + with message-id and subject line Bug#904646: fixed in python-hypothesis 3.71.11-1 has caused the Debian Bug report #904646, regarding python-hypothesis fails imports with Python 3.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.) -- 904646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904646 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-hypothesis Version: 3.44.1-2 Severity: serious Tags: sid buster typing.GenericMeta doesn't exist anymore in 3.7 = test session starts == platform linux -- Python 3.7.0+, pytest-3.6.2, py-1.5.3, pluggy-0.6.0 rootdir: /tmp/autopkgtest-lxc.ow4u414h/downtmp/build.PPF/src/tests, inifile: /dev/null plugins: hypothesis-3.44.1, flaky-3.3.0 collected 2070 items / 1 errors ERRORS _ ERROR collecting py3/test_lookup.py __ tests/py3/test_lookup.py:38: in if isinstance(t, typing.GenericMeta)), key=str) tests/py3/test_lookup.py:38: in if isinstance(t, typing.GenericMeta)), key=str) E AttributeError: module 'typing' has no attribute 'GenericMeta' ===Flaky Test Report=== ===End Flaky Test Report=== --- End Message --- --- Begin Message --- Source: python-hypothesis Source-Version: 3.71.11-1 We believe that the bug you reported is fixed in the latest version of python-hypothesis, 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 904...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mattia Rizzolo (supplier of updated python-hypothesis package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 24 Sep 2018 13:47:07 +0200 Source: python-hypothesis Binary: python-hypothesis python3-hypothesis pypy-hypothesis python-hypothesis-doc Architecture: source Version: 3.71.11-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Mattia Rizzolo Description: pypy-hypothesis - advanced Quickcheck style testing library for PyPy python-hypothesis - advanced Quickcheck style testing library for Python 2 python-hypothesis-doc - advanced Quickcheck style testing library (documentation) python3-hypothesis - advanced Quickcheck style testing library for Python 3 Closes: 904646 904647 Changes: python-hypothesis (3.71.11-1) unstable; urgency=medium . * Team upload. . [ Ondřej Nový ] * Convert git repository from git-dpm to gbp layout * Use 'python3 -m sphinx' instead of sphinx-build for building docs . [ Mattia Rizzolo ] * New upstream version 3.71.11. + Compatibility with Python 3.7. Closes: #904646 * Update watch file to the new tarball names. Closes: #904647 * Fix paths after upstream shuffled files around. * d/rules: Drop unneeded override_dh_python3. * d/rules: Add a comment on why the tests are skipped. * Add new dependency on python(3)-dateutil. * Fix autopkgtest to fit the new version. Checksums-Sha1: 2858510d3858229a65e29289766673859b169b49 2749 python-hypothesis_3.71.11-1.dsc 2eda1233c62fc0fc82c9f6f04a530f5974d10592 550579 python-hypothesis_3.71.11.orig.tar.gz 2cf5b943cb106bea4c0c7883ca2370f9ccac3954 9512 python-hypothesis_3.71.11-1.debian.tar.xz 6b2ee7f6c15920dbf1ae7d997a853942cc6355d2 8896 python-hypothesis_3.71.11-1_amd64.buildinfo Checksums-Sha256: ef124ee36e5cb4bea9166ff280ab8162245382f09004e7adcbc0cc2d77c04cab 2749 python-hypothesis_3.71.11-1.dsc 45f291c4ef8861892d9e5695da209145c6bda6e81e1540791be49f2b94c79c7b 550579 python-hypothesis_3.71.11.orig.tar.gz 64002d7b1e3b7fae4a3071c7322b1eb0fbe8702415aa92d7834f4b71a73ff0f2 9512 python-hypothesis_3.71.11-1.debian.tar.xz c02ce404e2ceb6217652f42b914828a63d16255e5ce10315d90dbfc645ffd2c5 8896 python-hypothesis_3.71.11-1_amd64.buildinfo Files: 479877800c1af20fe9345e115badd3af 2749 python optional python-hypothesis_3.71.11-1.dsc 6c38a30da23616b43b95a69d87cc9498 550579 python optional python-hypothesis_3.71.11.orig.tar.gz f7e739ae864b85ef0d8c2f80fa6ad78d 9512 python optional
Bug#909120: camitk FTBFS: tests segfault (Bug #909120)
On Mon, Sep 24, 2018 at 02:49:37PM +0200, Emmanuel Promayon wrote: > - if there is no (easy) way to go back to vtk6 in gdcm (or to support both > vtk6 and vtk7), does this means that we (upstream) need to update CamiTK to > be based on VTK7 in order to fix this bug? Disclaimer: I have no idea about VTK and all its dependencies. I have read that upstream is joining Debian Science to package recent upstream version VTK8. I expect that VTK6 will be removed from Debian soon. So yes, I'd strongly recommend to follow the stable release cycle of VTK upstream, which means that porting camitk to VTK7 is necessary for including camitk into Debian and it is sensible to do some checks with VTK8 since at some point in time this will be used in Debian. We will not be able to support more than two VTK versions in Debian (most probably only one). So far for a short note - more details from VTK maintainers ... Kind regards Andreas. -- http://fam-tille.de
Bug#909120: camitk FTBFS: tests segfault (Bug #909120)
Hello all Thanks again to Andreas and Bernhard. You are right: the problem comes from gdcm 2.8.7-2. I tried to build the package with the previous version of vtkgdcm. With version 2.8.7-1 all the tests pass and the packages are built normally (and autopkgtest does not fail either). If I understood well (let me know otherwise), the history of this bug goes like this: - the gdcm package was updated to support python3 - in the process, the dependency of gdcm was updated from vtk6 to vtk7 (see this commit [1], which took effect in gdcm 2.8.7-2) - one extension (i.e., plugin) of CamiTK requires gdcm to read DICOM images. During the first build after gdcm 2.8.7-2 was available on sid, vtk6 was used to build CamiTK core library and gdcm 2.8.7-2 (using vtk7) was used to build the dicom extension of CamiTK. - In the test where the dicom extension is loaded (this is not all the CamiTK test, hence the specific test failures), the class RendererWidget of CamiTK was confused with both vtk share library loaded in memory (as Berhnard message pointed out). - This bug was born - Berhnard (bravely!) decided to update the dependency of CamiTK from vtk6 to vtk7, which resulted in other problem (probably due to the use of VTK class QVTKWidget2 in the CamiTK class RendererWidget) My questions to all: - is there any other package using vtk6 and gdcm 2.8.7-2 that are affected by this? - should the gdcm package not add (some kind of) conflict flag with vtk6 (so that this problem can be more easily detected in the future)? - if there is no (easy) way to go back to vtk6 in gdcm (or to support both vtk6 and vtk7), does this means that we (upstream) need to update CamiTK to be based on VTK7 in order to fix this bug? And two bonus subsidiary questions to Gert , Steve and Sébastien : - About VTK8 : is there any plan to add a vtk8 package in debian? I don't really know what is the release policy of VTK, but it seems they went from 7.0 to 7.1 to directly 8.0 and then 8.1, and I saw VTK 9 mentioned (if you have more information or pointer about the release policy or the roadmap, I will be very thankful!). I found an article on the Kitware blog saying that they have their own apt repository for sid providing nightly builds of VTK [2]. Do you know any more about that? What is your "vision" about vtk8 in debian? - (more technical and may be not in the proper context) about VTK Qt and OpenGL: VTK8 seems to have introduced a different class to manage VTK renderer inside Qt widget (QVTKOpenGLWidget instead of QVTKWidget). This is an area where we add a lot of problem with Qt5+VTK6 (especially on linux+intel integrated video cards and windows virtual machines). So it seems that transition to VTK8 brings more hope. Do you have any experience of migrating QVTKWidget from VTK6 to VTK7 or VTK8? Thanks again to Andreas and Bernhard and in advance to Gert, Steve and Sébastien! Hopefully this bug can be solved soon... Best regards, Emmanuel PS : and of course the double delete discovered by Bernhard [3] should be solved upstream as well! [1] https://salsa.debian.org/med-team/gdcm/commit/dd4f5d00b99730388512f512743e0be48ce56ae2 [2] https://blog.kitware.com/rethinking-debian-packaging-for-vtk-and-other-cmake-projects-part-1/ [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909120#10
Bug#909464: thunderbird: Thunderbird crash : Fontconfig error: failed reading config file
Le 24/09/2018 à 13:43, Carsten Schoenert a écrit : > Hello, > > Am 24.09.18 um 11:11 schrieb Frederic MASSOT: >> Dear Maintainer, >> >> After upgrading Thunderbird from version 1:52.9.1-1 to version >> 1:60.0-3~deb9u1, Thunderbird crash at startup with error message: >> >> $ thunderbird --verbose >> INFO -> [[ ... using verbose mode ... ]] >> DEBUG -> Found folder /home/toto/.icedove, found a symlink >> /home/toto/.thunderbird pointing to /home/toto/.icedove >> DEBUG -> call '/usr/lib/thunderbird/thunderbird ' >> Fontconfig error: failed reading config file >> alloc factor 0,90 0,90 >> alloc factor 0,90 0,90 >> ExceptionHandler::GenerateDump cloned child 4962 >> ExceptionHandler::SendContinueSignalToChild sent continue signal to child >> ExceptionHandler::WaitForContinueSignal waiting for continue signal... > > you have seen #909039 and have checked your bug is a different behavior? > > I don't think the message about some Fontconfig error is related to this > crash (we never have seen this before). You would need to wrap the start > of Thunderbird within a strace call, or run this all through the debugger. > > You also have installed AppArmor, the profile for Thunderbird is disabled? > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909039 Hi, Yes, the message on Fontconfig has nothing to do with the crash. This is the same problem as bug report #909039. I had folders in Thunderbird with accents in the name. I renamed these files by replacing the letter accented by the same letter without accent. In 2018 a bug related to the use of non-ASCII characters, crazy! :o) Thank you. Regards. -- == | FRÉDÉRIC MASSOT | | http://www.juliana-multimedia.com | | mailto:frede...@juliana-multimedia.com | | +33.(0)2.97.54.77.94 +33.(0)6.67.19.95.69 | ===Debian=GNU/Linux===
Bug#909482: rustc: FTBFS on mips64el on buildds: timeout
package: rustc version: 1.28.0+dfsg1-2 severity: serious tags: ftbfs Hi, The builds of rustc in sid on mips64el consistently fail on the buildds: https://buildd.debian.org/status/logs.php?pkg=rustc=mips64el Most of the fail with "Build killed with signal TERM after 150 minutes of inactivity" If the build is actually still going at that point, it should produce output to avoid being killed. The builds that are in the archive seem to be manual builds that were uploaded. Cheers, Ivo
Bug#909481: tinyproxy: fails to install: chmod: cannot access '/var/log/tinyproxy/*': No such file or directory
Package: tinyproxy Version: 1.10.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Selecting previously unselected package tinyproxy. (Reading database ... (Reading database ... 4919 files and directories currently installed.) Preparing to unpack .../tinyproxy_1.10.0-1_all.deb ... Unpacking tinyproxy (1.10.0-1) ... Setting up tinyproxy (1.10.0-1) ... chmod: cannot access '/var/log/tinyproxy/*': No such file or directory dpkg: error processing package tinyproxy (--configure): installed tinyproxy package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: tinyproxy cheers, Andreas tinyproxy_1.10.0-1.log.gz Description: application/gzip
Bug#909480: feersum: FTBFS randomly (failing tests)
Package: src:feersum Version: 1.406-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package but it failed: [...] debian/rules build-arch dh build-arch dh_update_autotools_config -a dh_autoreconf -a dh_auto_configure -a perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" "LD=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now" Checking if your kit is complete... Looks good Generating a Unix-style Makefile Writing Makefile for Feersum Writing MYMETA.yml and MYMETA.json dh_auto_build -a make -j1 make[1]: Entering directory '/<>' cp lib/Feersum/Connection/Handle.pm blib/lib/Feersum/Connection/Handle.pm cp lib/Feersum/Connection.pm blib/lib/Feersum/Connection.pm cp lib/Feersum.pm blib/lib/Feersum.pm cp lib/Plack/Handler/Feersum.pm blib/lib/Plack/Handler/Feersum.pm cp lib/Feersum/Runner.pm blib/lib/Feersum/Runner.pm Running Mkbootstrap for Feersum () chmod 644 "Feersum.bs" "/usr/bin/perl" -MExtUtils::Command::MM -e 'cp_nonempty' -- Feersum.bs blib/arch/auto/Feersum/Feersum.bs 644 "/usr/bin/perl" "/usr/share/perl/5.26/ExtUtils/xsubpp" -typemap '/usr/share/perl/5.26/ExtUtils/typemap' -typemap '/<>/typemap' Feersum.xs > Feersum.xsc mv Feersum.xsc Feersum.c x86_64-linux-gnu-gcc -c -I. -I/usr/lib/x86_64-linux-gnu/perl5/5.26/EV -I/usr/lib/x86_64-linux-gnu/perl5/5.26 -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DVERSION=\"1.406\" -DXS_VERSION=\"1.406\" -fPIC "-I/usr/lib/x86_64-linux-gnu/perl/5.26/CORE" Feersum.c In file included from /usr/include/string.h:494, from /usr/lib/x86_64-linux-gnu/perl/5.26/CORE/perl.h:941, from /usr/lib/x86_64-linux-gnu/perl5/5.26/EV/EVAPI.h:5, from Feersum.xs:1: In function 'memcpy', inlined from 'feersum_env.isra.23' at Feersum.xs:1566:9: /usr/include/x86_64-linux-gnu/bits/string_fortified.h:34:10: warning: '__builtin_memcpy' reading 8 bytes from a region of size 5 [-Wstringop-overflow=] return __builtin___memcpy_chk (__dest, __src, __len, __bos0 (__dest)); ^~ rm -f blib/arch/auto/Feersum/Feersum.so x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now -shared -L/usr/local/lib -fstack-protector-strong Feersum.o -o blib/arch/auto/Feersum/Feersum.so \ \ chmod 755 blib/arch/auto/Feersum/Feersum.so cp bin/feersum blib/script/feersum "/usr/bin/perl" -MExtUtils::MY -e 'MY->fixin(shift)' -- blib/script/feersum Manifying 1 pod document Manifying 5 pod documents make[1]: Leaving directory '/<>' dh_auto_test -a make -j1 test TEST_VERBOSE=1 make[1]: Entering directory '/<>' "/usr/bin/perl" -MExtUtils::Command::MM -e 'cp_nonempty' -- Feersum.bs blib/arch/auto/Feersum/Feersum.bs 644 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 'blib/arch')" t/*.t t/01-simple.t . 1..31 ok 1 - use Feersum; ok 2 - made listen socket ok 3 - has a fileno ok 4 - assigned socket ok 5 - can assign code block ok 6 - after undef cb ok 7 - cv recycled ok 8 - can assign another code block ok 9 - unicode connected ok 10 - ascii connected ok 11 - called back! ok 12 - 'got an object!' isa 'Feersum::Connection' ok 13 - got env ok 14 - got a ua! ok 15 - done request handler ok 16 - called back! ok 17 - 'got an object!' isa 'Feersum::Connection' ok 18 - got env ok 19 - got a ua! ok 20 - done request handler ok 21 - client 2 got 200 ok 22 - got a custom x-client header ok 23 - content-length was overwritten by the engine ok 24 ok 25 - unicode body! ok 26 - client 1 got 200 ok 27 - got a custom x-client header ok 28 - content-length was overwritten by the engine ok 29 ok 30 - plain old body ok 31 - all done ok t/02-array-body.t . 1..12 ok 1 - use Feersum; ok 2 - made listen socket ok 3 - has a fileno ok 4 - assigned socket ok 5 - simple_client connected ok 6 - 'got an object!' isa 'Feersum::Connection' ok 7 - sent response ok 8 - client got 200 ok 9 ok 10 - content-length was calculated correctly ok 11 - body was concatenated together ok 12 - all done ok t/03-env-hash.t ... 1..143 ok 1 - use Feersum; ok 2 - made listen socket ok 3 - has a fileno ok 4 - assigned socket ok 5 - simple_client connected ok 6 - simple_client connected ok 7 - simple_client connected ok 8 - simple_client connected ok 9 - simple_client connected ok 10 -
Bug#896627: marked as done (FTBFS with sphinx 1.7.2: exception: cannot import name 'Directive')
Your message dated Mon, 24 Sep 2018 12:13:04 + with message-id and subject line Bug#896627: fixed in pygments 2.2.0+dfsg-2 has caused the Debian Bug report #896627, regarding FTBFS with sphinx 1.7.2: exception: cannot import name 'Directive' 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.) -- 896627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896627 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sphinx Version: 1.7.2-1 Severity: serious Control: affects -1 src:alembic src:bcfg2 src:bottleneck src:dipy src:heat src:julia src:mako src:prospector src:pyevolve src:pymvpa2 src:python-cryptography src:python-expyriment src:python-numpy src:python-scipy https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/alembic.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/bcfg2.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/bottleneck.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dipy.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/heat.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/julia.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mako.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/prospector.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pyevolve.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pymvpa2.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/python-cryptography.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-expyriment.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-numpy.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-scipy.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/sqlalchemy.html Example (from alembic): ... debian/rules override_dh_sphinxdoc make[1]: Entering directory '/build/1st/alembic-0.9.7' sphinx-build -b html docs/build /build/1st/alembic-0.9.7/debian/alembic/usr/share/doc/alembic/html Running Sphinx v1.7.2 Extension error: Could not import extension changelog (exception: cannot import name 'Directive') make[1]: *** [debian/rules:13: override_dh_sphinxdoc] Error 2 --- End Message --- --- Begin Message --- Source: pygments Source-Version: 2.2.0+dfsg-2 We believe that the bug you reported is fixed in the latest version of pygments, 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 896...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mattia Rizzolo (supplier of updated pygments package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 24 Sep 2018 13:17:46 +0200 Source: pygments Binary: python-pygments python3-pygments python-pygments-doc Architecture: source Version: 2.2.0+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Piotr Ożarowski Changed-By: Mattia Rizzolo Description: python-pygments - syntax highlighting package written in Python python-pygments-doc - documentation for the Pygments python3-pygments - syntax highlighting package written in Python 3 Closes: 892948 896627 902690 904325 Changes: pygments (2.2.0+dfsg-2) unstable; urgency=medium . * Team upload. . [ Ondřej Nový ] * d/control: Set Vcs-* to salsa.debian.org. * d/control: Deprecating priority extra as per policy 4.0.1. * d/control: Remove XS-Testsuite field, not needed anymore. * d/tests: Use AUTOPKGTEST_TMP instead of ADTTMP. * d/control: Remove ancient X-Python-Version field. * Convert git repository from git-dpm to gbp layout. . [ Helmut Grohne ] * Mark all packages Multi-Arch: foreign. Closes: #892948 . [ Mattia Rizzolo ] * Suggests python-pygments-doc from the library packages. Closes: #902690 * Add patch from Dmitry Shachnev to fix FTBFS with Sphinx 1.7. Closes: 896627 * Add patch to fix compatibility with Python 3.7. Closes: #904325 Checksums-Sha1: 64ca350dd0d9c19bc121508fe9a2e0f7663b9a36 2359 pygments_2.2.0+dfsg-2.dsc
Bug#909477: python3-octavia-dashboard: typo in Depends: pytnon3-django
Package: python3-octavia-dashboard Version: 2.0.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package is no longer installable in sid: v Depends: pytnon3-django (< 2:2) but it is not installable ^ Cheers, Andreas
Bug#909464: thunderbird: Thunderbird crash : Fontconfig error: failed reading config file
Hello, Am 24.09.18 um 11:11 schrieb Frederic MASSOT: > Dear Maintainer, > > After upgrading Thunderbird from version 1:52.9.1-1 to version > 1:60.0-3~deb9u1, Thunderbird crash at startup with error message: > > $ thunderbird --verbose > INFO -> [[ ... using verbose mode ... ]] > DEBUG -> Found folder /home/toto/.icedove, found a symlink > /home/toto/.thunderbird pointing to /home/toto/.icedove > DEBUG -> call '/usr/lib/thunderbird/thunderbird ' > Fontconfig error: failed reading config file > alloc factor 0,90 0,90 > alloc factor 0,90 0,90 > ExceptionHandler::GenerateDump cloned child 4962 > ExceptionHandler::SendContinueSignalToChild sent continue signal to child > ExceptionHandler::WaitForContinueSignal waiting for continue signal... you have seen #909039 and have checked your bug is a different behavior? I don't think the message about some Fontconfig error is related to this crash (we never have seen this before). You would need to wrap the start of Thunderbird within a strace call, or run this all through the debugger. You also have installed AppArmor, the profile for Thunderbird is disabled? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909039 -- Regards Carsten Schoenert
Bug#896627: Bug #896627 in pygments marked as pending
Control: tag -1 pending Hello, Bug #896627 in pygments reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at: https://salsa.debian.org/python-team/modules/pygments/commit/d48ee34e4f68f6f9812c14075cc5a66b4fc14cf3 Add patch from Dmitry Shachnev to fix FTBFS with Sphinx 1.7 Closes: #896627 Signed-off-by: Mattia Rizzolo (this message was generated automatically) -- Greetings https://bugs.debian.org/896627
Processed: Bug #896627 in pygments marked as pending
Processing control commands: > tag -1 pending Bug #896627 [src:pygments] FTBFS with sphinx 1.7.2: exception: cannot import name 'Directive' Ignoring request to alter tags of bug #896627 to the same tags previously set -- 896627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896627 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 903761 in 1:9.13.3-1, tagging 893498, tagging 893499, tagging 895795 ...
Processing commands for cont...@bugs.debian.org:
> found 903761 1:9.13.3-1
Bug #903761 [bind] bind: fails to install: rndc-confgen: The -r option has been
deprecated.
Marked as found in versions bind/1:9.13.3-1.
> tags 893498 + experimental
Bug #893498 {Done: Adrian Bunk } [src:openhft-chronicle-wire]
openhft-chronicle-wire FTBFS with openjdk-9
Added tag(s) experimental.
> tags 893499 + experimental
Bug #893499 {Done: Adrian Bunk } [src:openhft-chronicle-core]
openhft-chronicle-core FTBFS with openjdk-9
Added tag(s) experimental.
> tags 895795 + experimental
Bug #895795 {Done: Adrian Bunk } [src:openhft-chronicle-bytes]
openhft-chronicle-bytes FTBFS with openjdk-9
Added tag(s) experimental.
> found 904459 1.10.0+dfsg-3
Bug #904459 [netdata] modifies conffiles (health_alarm_notify.conf)
Marked as found in versions netdata/1.10.0+dfsg-3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
893498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893498
893499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893499
895795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895795
903761: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903761
904459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#906971: apper: diff for NMU version 1.0.0-1.1
Am Sa., 22. Sep. 2018 um 21:45 Uhr schrieb Adrian Bunk : > > Control: tags 906971 + pending > Dear maintainer, > > I've prepared an NMU for apper (versioned as 1.0.0-1.1) and uploaded > it to DELAYED/15. Please feel free to tell me if I should cancel it. It's fine, sorry for not acting on the bug as of yet, I am moving to a new place and that is causing a few (internet related) difficulties. I might make a new upload including your change before the delayed upload is applied, but if I don't manage to do that in time, the delayed upload is more than justified. Thank you for helping out! Cheers, Matthias -- I welcome VSRE emails. See http://vsre.info/
Bug#900997: Different message asking for password?
On 9/24/18 6:45 AM, Steven De Herdt wrote: > Hello folks > > At the moment, this bug prevents a freshly installed buster with KDE as > desktop to have its printers configured. If the message asking for > authentication is clarified, would that be enough to at least lower the > severity of this bug below RC? > > Kind regards > -Steven > I think this bug is properly resolved when the server address (IP and/or DNS name), port, protocol, and certificate are available for inspection (like in a web browser). A stop-gap message that gives the first three would make this a wishlist bug, in my opinion. That should be relatively easy, right? Antonio
Bug#900997: Different message asking for password?
Hello folks At the moment, this bug prevents a freshly installed buster with KDE as desktop to have its printers configured. If the message asking for authentication is clarified, would that be enough to at least lower the severity of this bug below RC? Kind regards -Steven
Bug#906375: marked as done (libitext5-java: FTBFS in buster/sid (method marshal in class org.apache.jcp.xml.dsig.internal.dom.DOMXMLSignature cannot be applied to given types))
Your message dated Mon, 24 Sep 2018 10:38:08 + with message-id and subject line Bug#906375: fixed in libxml-security-java 2.0.10-2 has caused the Debian Bug report #906375, regarding libitext5-java: FTBFS in buster/sid (method marshal in class org.apache.jcp.xml.dsig.internal.dom.DOMXMLSignature cannot be applied to given types) 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.) -- 906375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906375 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libitext5-java Version: 5.5.6-4 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --buildsystem=maven dh_update_autotools_config -i -O--buildsystem=maven dh_autoreconf -i -O--buildsystem=maven dh_auto_configure -i -O--buildsystem=maven mh_patchpoms -plibitext5-java --debian-build --keep-pom-version --maven-repo=/<>/debian/maven-repo dh_auto_build -i -O--buildsystem=maven /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/<> -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/<>/debian/maven.properties org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by com.google.inject.internal.cglib.core.$ReflectUtils$1 (file:/usr/share/maven/lib/guice.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) WARNING: Please consider reporting this to the maintainers of com.google.inject.internal.cglib.core.$ReflectUtils$1 WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release [INFO] Scanning for projects... [... snipped ...] [INFO] [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ itextpdf --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 24 resources [INFO] [INFO] --- maven-compiler-plugin:3.8.0:compile (default-compile) @ itextpdf --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 622 source files to /<>/target/classes [INFO] /<>/src/main/java/com/itextpdf/text/pdf/PdfPublicKeySecurityHandler.java: Some input files use or override a deprecated API. [INFO] /<>/src/main/java/com/itextpdf/text/pdf/PdfPublicKeySecurityHandler.java: Recompile with -Xlint:deprecation for details. [INFO] /<>/src/main/java/com/itextpdf/text/pdf/TtfUnicodeWriter.java: Some input files use unchecked or unsafe operations. [INFO] /<>/src/main/java/com/itextpdf/text/pdf/TtfUnicodeWriter.java: Recompile with -Xlint:unchecked for details. [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] /<>/src/main/java/com/itextpdf/text/pdf/security/MakeXmlSignature.java:[443,22] method marshal in class org.apache.jcp.xml.dsig.internal.dom.DOMXMLSignature cannot be applied to given types; required: org.apache.jcp.xml.dsig.internal.dom.XmlWriter,java.lang.String,javax.xml.crypto.XMLCryptoContext found: org.w3c.dom.Node,org.w3c.dom.Node,java.lang.String,javax.xml.crypto.dsig.dom.DOMSignContext reason: actual and formal argument lists differ in length [INFO] 1 error [INFO] - [INFO] [INFO] [INFO] Skipping iText, a Free Java-PDF library [INFO] This project has been banned from the build due to previous failures. [INFO] [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 12.567 s [INFO] Finished at: 2018-08-10T03:56:01Z [INFO] [ERROR] Failed to execute goal
Processed: Bug #906375 in libxml-security-java marked as pending
Processing control commands: > tag -1 pending Bug #906375 [src:libxml-security-java] libitext5-java: FTBFS in buster/sid (method marshal in class org.apache.jcp.xml.dsig.internal.dom.DOMXMLSignature cannot be applied to given types) Added tag(s) pending. -- 906375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906375 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909470: r-cran-shinythemes: needs to be rebuilt for r-api-3.5
Source: r-cran-shinythemes Version: 1.1.1+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package is no longer installable in sid: r-cran-shinythemes/amd64 unsatisfiable Depends: r-api-3.4 r-cran-shinythemes/i386 unsatisfiable Depends: r-api-3.4 r-cran-shinythemes/arm64 unsatisfiable Depends: r-api-3.4 r-cran-shinythemes/armel unsatisfiable Depends: r-api-3.4 r-cran-shinythemes/armhf unsatisfiable Depends: r-api-3.4 r-cran-shinythemes/mips unsatisfiable Depends: r-api-3.4 r-cran-shinythemes/mips64el unsatisfiable Depends: r-api-3.4 r-cran-shinythemes/mipsel unsatisfiable Depends: r-api-3.4 r-cran-shinythemes/ppc64el unsatisfiable Depends: r-api-3.4 r-cran-shinythemes/s390x unsatisfiable Depends: r-api-3.4 Cheers, Andreas
Bug#906375: Bug #906375 in libxml-security-java marked as pending
Control: tag -1 pending Hello, Bug #906375 in libxml-security-java reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at: https://salsa.debian.org/java-team/libxml-security-java/commit/5c42ca8379d99b4ed59a2210dd5a2cc0b65813bc Add patch for old API used by libitext5-java Closes: #906375 (this message was generated automatically) -- Greetings https://bugs.debian.org/906375
Processed: Re: libitext5-java: FTBFS in buster/sid (method marshal in class org.apache.jcp.xml.dsig.internal.dom.DOMXMLSignature cannot be applied to given types)
Processing commands for cont...@bugs.debian.org: > reassign 906375 src:libxml-security-java Bug #906375 [src:libitext5-java] libitext5-java: FTBFS in buster/sid (method marshal in class org.apache.jcp.xml.dsig.internal.dom.DOMXMLSignature cannot be applied to given types) Bug reassigned from package 'src:libitext5-java' to 'src:libxml-security-java'. No longer marked as found in versions libitext5-java/5.5.6-4. Ignoring request to alter fixed versions of bug #906375 to the same values previously set > affects 906375 src:libitext5-java Bug #906375 [src:libxml-security-java] libitext5-java: FTBFS in buster/sid (method marshal in class org.apache.jcp.xml.dsig.internal.dom.DOMXMLSignature cannot be applied to given types) Added indication that 906375 affects src:libitext5-java > End of message, stopping processing here. Please contact me if you need assistance. -- 906375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906375 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#903336: marked as done (node-babel-plugin-add-module-exports: FTBFS in buster/sid (dh_installdocs: Cannot find "README.md"))
Your message dated Mon, 24 Sep 2018 10:05:39 + with message-id and subject line Bug#903336: fixed in node-babel-plugin-add-module-exports 0.2.1-3 has caused the Debian Bug report #903336, regarding node-babel-plugin-add-module-exports: FTBFS in buster/sid (dh_installdocs: Cannot find "README.md") 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.) -- 903336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903336 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:node-babel-plugin-add-module-exports Version: 0.2.1-2 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep dh_update_autotools_config -i fakeroot debian/rules binary-indep dh binary-indep dh_testroot -i dh_prep -i dh_install -i dh_installdocs -i dh_installdocs: Cannot find (any matches for) "README.md" (tried in .) debian/rules:8: recipe for target 'binary-indep' failed make: *** [binary-indep] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess returned exit status 2 The build was made with "dpkg-buildpackage -A" in my autobuilder. Most probably, it also fails here in reproducible builds: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-babel-plugin-add-module-exports.html [ Note: There has been a recent change in debhelper behaviour, the current behaviour is the intended one. See Bug #903133 for details ]. Thanks. --- End Message --- --- Begin Message --- Source: node-babel-plugin-add-module-exports Source-Version: 0.2.1-3 We believe that the bug you reported is fixed in the latest version of node-babel-plugin-add-module-exports, 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 903...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pirate Praveen (supplier of updated node-babel-plugin-add-module-exports 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, 24 Sep 2018 15:17:23 +0530 Source: node-babel-plugin-add-module-exports Binary: node-babel-plugin-add-module-exports Architecture: source Version: 0.2.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Pirate Praveen Description: node-babel-plugin-add-module-exports - Babel plugin for default module.exports like babel version 5 Closes: 903336 Changes: node-babel-plugin-add-module-exports (0.2.1-3) unstable; urgency=medium . * Stop trying to install a not shipped README.md. (Closes: #903336) (Thanks to Adrian Bunk) * Use salsa.debian.org in Vcs-* fields * Bump debhelper compatibility level to 11 * Bump Standards-Version to 4.2.1 (no changes needed) Checksums-Sha1: 0eff0230233ef7bfcc2588009d550ac1964ed46d 2277 node-babel-plugin-add-module-exports_0.2.1-3.dsc be3cb72fcf574580f867732bd89a9064368b5587 2452 node-babel-plugin-add-module-exports_0.2.1-3.debian.tar.xz b71b73b534c31741b699adc3e160d69a751f96fe 6171 node-babel-plugin-add-module-exports_0.2.1-3_source.buildinfo Checksums-Sha256: 17235238dce4e3419ce0a6c9a205c046dce3f03a8af8116e52001c178bfdab35 2277 node-babel-plugin-add-module-exports_0.2.1-3.dsc bde264adb2d479c4ffe0daa95901ec2700b2a9ffa30ccac20b96819e8d916dbb 2452 node-babel-plugin-add-module-exports_0.2.1-3.debian.tar.xz 320ec7481260ae35c9a4201f9de762ca4a0ca8c28c2ffb2a49c3e39455133402 6171 node-babel-plugin-add-module-exports_0.2.1-3_source.buildinfo Files: 67034960b6b3be4372a372b6052b94cf 2277 javascript optional node-babel-plugin-add-module-exports_0.2.1-3.dsc 99783f1e4e520dc2f0bec287978bc7b8 2452 javascript optional node-babel-plugin-add-module-exports_0.2.1-3.debian.tar.xz bff61cd94a5eab866989c1c26e68f111 6171 javascript optional node-babel-plugin-add-module-exports_0.2.1-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEKnl0ri/BUtd4Z9pKzh+cZ0USwioFAluotGIACgkQzh+cZ0US
Bug#909468: python-openstack-doc-tools: fails to install: update-alternatives: error: alternative path /usr/bin/python2-doc-tools-update-cli-reference doesn't exist
Package: python-openstack-doc-tools,python3-openstack-doc-tools Version: 1.8.0-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Selecting previously unselected package python-openstack-doc-tools. (Reading database ... (Reading database ... 16142 files and directories currently installed.) Preparing to unpack .../python-openstack-doc-tools_1.8.0-2_all.deb ... Unpacking python-openstack-doc-tools (1.8.0-2) ... Setting up python-openstack-doc-tools (1.8.0-2) ... update-alternatives: using /usr/bin/python2-doc-tools-check-languages to provide /usr/bin/doc-tools-check-languages (doc-tools-check-languages) in auto mode update-alternatives: error: alternative path /usr/bin/python2-doc-tools-update-cli-reference doesn't exist dpkg: error processing package python-openstack-doc-tools (--configure): installed python-openstack-doc-tools package post-installation script subprocess returned error exit status 2 Errors were encountered while processing: python-openstack-doc-tools Selecting previously unselected package python3-openstack-doc-tools. (Reading database ... (Reading database ... 15205 files and directories currently installed.) Preparing to unpack .../python3-openstack-doc-tools_1.8.0-2_all.deb ... Unpacking python3-openstack-doc-tools (1.8.0-2) ... Setting up python3-openstack-doc-tools (1.8.0-2) ... update-alternatives: using /usr/bin/python3-doc-tools-check-languages to provide /usr/bin/doc-tools-check-languages (doc-tools-check-languages) in auto mode update-alternatives: error: alternative path /usr/bin/python3-doc-tools-update-cli-reference doesn't exist dpkg: error processing package python3-openstack-doc-tools (--configure): installed python3-openstack-doc-tools package post-installation script subprocess returned error exit status 2 Errors were encountered while processing: python3-openstack-doc-tools cheers, Andreas python-openstack-doc-tools_1.8.0-2.log.gz Description: application/gzip
Bug#909466: radicale: fails to remove: post-removal script subprocess returned error exit status 1
Package: radicale Version: 1.1.6-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to remove. >From the attached log (scroll to the bottom...): Removing radicale (1.1.6-2) ... invoke-rc.d: could not determine current runlevel invoke-rc.d: policy-rc.d denied execution of stop. -sh: 1: radicale: not found ERROR: Export for Radicale failed (maybe source contains alien content?) chown: cannot access '/var/backups/radicale-2018-09-23T23:11:59.hR8mUg/root.tar.gz': No such file or directory dpkg: error processing package radicale (--remove): installed radicale package post-removal script subprocess returned error exit status 1 cheers, Andreas radicale_1.1.6-2.log.gz Description: application/gzip
Bug#909464: thunderbird: Thunderbird crash : Fontconfig error: failed reading config file
Package: thunderbird Version: 1:60.0-3~deb9u1 Severity: grave Justification: renders package unusable Dear Maintainer, After upgrading Thunderbird from version 1:52.9.1-1 to version 1:60.0-3~deb9u1, Thunderbird crash at startup with error message: $ thunderbird --verbose INFO -> [[ ... using verbose mode ... ]] DEBUG -> Found folder /home/toto/.icedove, found a symlink /home/toto/.thunderbird pointing to /home/toto/.icedove DEBUG -> call '/usr/lib/thunderbird/thunderbird ' Fontconfig error: failed reading config file alloc factor 0,90 0,90 alloc factor 0,90 0,90 ExceptionHandler::GenerateDump cloned child 4962 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... Regards. -- System Information: Debian Release: buster/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 4.18.0-1-686-pae (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages thunderbird depends on: ii debianutils 4.8.6 ii fontconfig2.13.0-5 ii libatk1.0-0 2.30.0-1 ii libc6 2.27-6 ii libcairo-gobject2 1.15.12-1 ii libcairo2 1.15.12-1 ii libdbus-1-3 1.12.10-1 ii libdbus-glib-1-2 0.110-3 ii libevent-2.0-52.0.21-stable-3 ii libffi6 3.2.1-8 ii libfontconfig12.13.0-5 ii libfreetype6 2.8.1-2 ii libgcc1 1:8.2.0-7 ii libgdk-pixbuf2.0-02.38.0+dfsg-6 ii libglib2.0-0 2.58.1-2 ii libgtk-3-03.24.0-3 ii libgtk2.0-0 2.24.32-3 ii libjsoncpp1 1.7.4-3 ii libpango-1.0-01.42.4-3 ii libpangocairo-1.0-0 1.42.4-3 ii libpangoft2-1.0-0 1.42.4-3 ii libstartup-notification0 0.12-5 ii libstdc++68.2.0-7 ii libvpx4 1.6.1-3+deb9u1 ii libx11-6 2:1.6.6-1 ii libx11-xcb1 2:1.6.6-1 ii libxcb-shm0 1.13-3 ii libxcb1 1.13-3 ii libxext6 2:1.3.3-1+b2 ii libxrender1 1:0.9.10-1 ii libxt61:1.1.5-1 ii psmisc23.1-1+b1 ii x11-utils 7.7+4 ii zlib1g1:1.2.11.dfsg-1 Versions of packages thunderbird recommends: ii hunspell-en-gb [hunspell-dictionary] 1:6.1.0~rc2-3 ii hunspell-en-us [hunspell-dictionary] 1:2018.04.16-1 ii hunspell-fr-classical [hunspell-dictionary] 1:6.3-1 ii lightning1:60.0-3~deb9u1 Versions of packages thunderbird suggests: ii apparmor 2.13-8 ii fonts-lyx 2.3.1-2-1 ii libgssapi-krb5-2 1.16-2 -- no debconf information
