Bug#895699: marked as done (peruse: Incomplete debian/copyright?)
Your message dated Thu, 19 Apr 2018 05:34:27 +
with message-id
and subject line Bug#895699: fixed in peruse 1.2+dfsg-2
has caused the Debian Bug report #895699,
regarding peruse: Incomplete debian/copyright?
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
895699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895699
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: peruse
Version: 1.2+dfsg-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: tsimo...@ubuntu.com
Hi,
I just ACCEPTed peruse from NEW but noticed it was missing
attribution in debian/copyright for at least Vishesh Handa.
This is in no way exhaustive (!) so please check over the
entire package carefully and address these on your next upload.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
--- End Message ---
--- Begin Message ---
Source: peruse
Source-Version: 1.2+dfsg-2
We believe that the bug you reported is fixed in the latest version of
peruse, 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 895...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Pino Toscano (supplier of updated peruse 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: Thu, 19 Apr 2018 07:17:36 +0200
Source: peruse
Binary: peruse peruse-common
Architecture: source
Version: 1.2+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian KDE Extras Team
Changed-By: Pino Toscano
Description:
peruse - comic book reader for KDE
peruse-common - common files for peruse
Closes: 895699
Changes:
peruse (1.2+dfsg-2) unstable; urgency=medium
.
* Team upload.
.
[ Simon Quigley ]
* Remove unneeded runtime dependency, qml-module-org-kde-kirigami.
* Add a missing line to debian/copyright (Closes: #895699). Thanks to
Chris Lamb for the pointer!
* Mark peruse-common as Multi-Arch: foreign, as recommended by the
Multiarch Hinter.
* Change maintainer to KDE Extras to be more specific.
* Fix appstream-metadata-in-legacy-location by grabbing a patch from
upstream.
.
[ Pino Toscano ]
* Move the appdata, and desktop files from peruse-common to peruse: they
need to stay together with the executable they refer to, otherwise the
installation with AppStream is broken, and just installing peruse-common
creates broken menu entries
- add proper breaks/replaces for this
* Do not include debian-qt-kde.mk in rules, since the dh sequencer is used
directly.
* Remove unused build dependencies: kdoctools-dev, libkf5newstuff-dev, and
libkf5plasma-dev.
* Remove the unused ${shlibs:Depends} substvar in peruse-common.
* Tighten the peruse-common dependency in peruse.
* Update the short descriptions to not start with a capital letter.
Checksums-Sha1:
1e3748b501cc27d08138aa323fb7d34b2aa19325 2369 peruse_1.2+dfsg-2.dsc
1da80f52388d2ce409d94a854380e5505dba9b69 4792 peruse_1.2+dfsg-2.debian.tar.xz
c556c2b5d6f0aaafe35befebce2c9b52af028390 19730
peruse_1.2+dfsg-2_source.buildinfo
Checksums-Sha256:
3f9a52d6ff5239468ab609700fef73d0adfaba58648e067689a296ea8040a8f9 2369
peruse_1.2+dfsg-2.dsc
05c44569895e63341556720b5b6b78d09b3b5d80a7d7a39a017fb72f56ffca9b 4792
peruse_1.2+dfsg-2.debian.tar.xz
aa33c23cac3db31f5d357330975fca6332148ba2c1c301b91be9bf5081014ada 19730
peruse_1.2+dfsg-2_source.buildinfo
Files:
b2c2b5093a9b5d91fcf899aea4159eef 2369 kde optional peruse_1.2+dfsg-2.dsc
81c1f90a364b77dec0dc39359df3f40b 4792 kde optional
peruse_1.2+dfsg-2.debian.tar.xz
62dfca99c77001e00a7a4dc87f9abcaf 19730 kde optional
peruse_1.2+dfsg-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAlrYJqgACgkQLRkciEOx
P00XPQ//clLi6bI2r3vFlaK3Lp0i9yTG90U3C43lTEm4gURwDShN/rhWAWrOYwJd
uMgRQ/wxesNock7TKiYVZ/Qm6jL7e273H1lLCsyYmAGvJcxzlAPBLsKi61E7vDa3
U0fIpVsEqqwISaYZ75q55/DFqVlWzWB98l29rmPjF6WWU2/fGYS8v20g6OxzbY9W
JQruyf/yQOOyFdaowLKXwHTYb7dfvpr+OYuDtwTI7grh435Tw7EpJTGc++FEQV1K
QAdqecxsGtsdCGXQsYptGeTXOD06NeGxwkKDXBYes5DZ5X6eA8/Tmv+GWpQpxvZ+
voCVfNganMRrHfQ25cvE3bUwvYyrnbsyXaWB5EjYoeDHctrbzzi
Bug#895980: zathura: symbol lookup error: zathura: undefined symbol: synctex_next_result
Hi thanks for the report > Control: retitle -1 libsynctex1: drops public symbols without SONAME bump Indeed, what a pity. I opened an issue on the github page: https://github.com/jlaurens/synctex/issues/23 > including a SONAME bump. FWIW, synctex_result_next was a public symbol in I guess you mean synctex_next_result. Yes, indeed synctex_parser_readme.md mentions this :-( * rename `synctex_next_result` to `synctex_scanner_next_result` > Additionally, synctex-version.h seems to be missing from the -dev package: That is strange and unintended, I will fix it. Thanks for the report. Best Norbert -- PREINING Norbert http://www.preining.info Accelia Inc. +JAIST +TeX Live +Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Processed: gcc-7: doesn't look for "as" in dir specified by -B
Processing control commands: > block 895618 with -1 Bug #895618 [src:afl] FTBFS: the instrumentation does not seem to be behaving correctly 895618 was not blocked by any bugs. 895618 was not blocking any bugs. Added blocking bug(s) of 895618: 896057 -- 895618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895618 896057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896057 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#893380: marked as done (ognl FTBFS with openjdk-9)
Your message dated Wed, 18 Apr 2018 20:58:18 +
with message-id
and subject line Bug#893380: fixed in ognl 2.7.3-7
has caused the Debian Bug report #893380,
regarding ognl FTBFS with openjdk-9
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
893380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893380
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ognl
Version: 2.7.3-6
Severity: serious
Tags: buster sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ognl.html
...
compile:
[mkdir] Created dir: /build/1st/ognl-2.7.3/build/classes
[javac] /build/1st/ognl-2.7.3/osbuild.xml:60: warning: 'includeantruntime'
was not set, defaulting to build.sysclasspath=last; set to false for repeatable
builds
[javac] Using javac -source 1.5 is no longer supported, switching to 1.6
[javac] Using javac -target 1.5 is no longer supported, switching to 1.6
[javac] Compiling 121 source files to /build/1st/ognl-2.7.3/build/classes
[javac] warning: [options] bootstrap class path not set in conjunction with
-source 1.6
[javac] warning: [options] source value 1.6 is obsolete and will be removed
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use
-Xlint:-options.
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 4 warnings
[copy] Copying 2 files to /build/1st/ognl-2.7.3/build/classes
[javac] /build/1st/ognl-2.7.3/osbuild.xml:70: warning: 'includeantruntime'
was not set, defaulting to build.sysclasspath=last; set to false for repeatable
builds
[javac] Using javac -source 1.5 is no longer supported, switching to 1.6
[javac] Using javac -target 1.5 is no longer supported, switching to 1.6
[javac] Compiling 124 source files to /build/1st/ognl-2.7.3/build/classes
[javac] warning: [options] bootstrap class path not set in conjunction with
-source 1.6
[javac] warning: [options] source value 1.6 is obsolete and will be removed
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use
-Xlint:-options.
[javac]
/build/1st/ognl-2.7.3/src/test/java/org/ognl/test/QuotingTest.java:44: error:
unmappable character (0xE5) for encoding US-ASCII
[javac] { null, "'???MM???dd???'", "???MM???dd???"}
[javac] ^
[javac]
/build/1st/ognl-2.7.3/src/test/java/org/ognl/test/QuotingTest.java:44: error:
unmappable character (0xB9) for encoding US-ASCII
[javac] { null, "'???MM???dd???'", "???MM???dd???"}
[javac]^
[javac]
/build/1st/ognl-2.7.3/src/test/java/org/ognl/test/QuotingTest.java:44: error:
unmappable character (0xB4) for encoding US-ASCII
[javac] { null, "'???MM???dd???'", "???MM???dd???"}
[javac] ^
[javac]
/build/1st/ognl-2.7.3/src/test/java/org/ognl/test/QuotingTest.java:44: error:
unmappable character (0xE6) for encoding US-ASCII
[javac] { null, "'???MM???dd???'", "???MM???dd???"}
[javac]^
[javac]
/build/1st/ognl-2.7.3/src/test/java/org/ognl/test/QuotingTest.java:44: error:
unmappable character (0x9C) for encoding US-ASCII
[javac] { null, "'???MM???dd???'", "???MM???dd???"}
[javac] ^
[javac]
/build/1st/ognl-2.7.3/src/test/java/org/ognl/test/QuotingTest.java:44: error:
unmappable character (0x88) for encoding US-ASCII
[javac] { null, "'???MM???dd???'", "???MM???dd???"}
[javac] ^
[javac]
/build/1st/ognl-2.7.3/src/test/java/org/ognl/test/QuotingTest.java:44: error:
unmappable character (0xE6) for encoding US-ASCII
[javac] { null, "'???MM???dd???'", "???MM???dd???"}
[javac] ^
[javac]
/build/1st/ognl-2.7.3/src/test/java/org/ognl/test/QuotingTest.java:44: error:
unmappable character (0x97) for encoding US-ASCII
[javac] { null, "'???MM???dd???'", "???MM???dd?
Bug#896025: python-mne FTBFS with python-matplotlib 2.2.2-1
Source: python-mne Version: 0.15.2+dfsg-2 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-mne.html ... === FAILURES === ___ [doctest] mne.viz.misc.plot_ideal_filter ___ 840 .. versionadded:: 0.14 841 842 Examples 843 844 Plot a simple ideal band-pass filter:: 845 846 >>> from mne.viz import plot_ideal_filter 847 >>> freq = [0, 1, 40, 50] 848 >>> gain = [0, 1, 1, 0] 849 >>> plot_ideal_filter(freq, gain, flim=(0.1, 100)) #doctest: +ELLIPSIS Expected: Got: /build/1st/python-mne-0.15.2+dfsg/mne/viz/misc.py:849: DocTestFailure test_plot_connectivity_circle _ def test_plot_connectivity_circle(): """Test plotting connectivity circle """ import matplotlib.pyplot as plt node_order = ['frontalpole-lh', 'parsorbitalis-lh', 'lateralorbitofrontal-lh', 'rostralmiddlefrontal-lh', 'medialorbitofrontal-lh', 'parstriangularis-lh', 'rostralanteriorcingulate-lh', 'temporalpole-lh', 'parsopercularis-lh', 'caudalanteriorcingulate-lh', 'entorhinal-lh', 'superiorfrontal-lh', 'insula-lh', 'caudalmiddlefrontal-lh', 'superiortemporal-lh', 'parahippocampal-lh', 'middletemporal-lh', 'inferiortemporal-lh', 'precentral-lh', 'transversetemporal-lh', 'posteriorcingulate-lh', 'fusiform-lh', 'postcentral-lh', 'bankssts-lh', 'supramarginal-lh', 'isthmuscingulate-lh', 'paracentral-lh', 'lingual-lh', 'precuneus-lh', 'inferiorparietal-lh', 'superiorparietal-lh', 'pericalcarine-lh', 'lateraloccipital-lh', 'cuneus-lh', 'cuneus-rh', 'lateraloccipital-rh', 'pericalcarine-rh', 'superiorparietal-rh', 'inferiorparietal-rh', 'precuneus-rh', 'lingual-rh', 'paracentral-rh', 'isthmuscingulate-rh', 'supramarginal-rh', 'bankssts-rh', 'postcentral-rh', 'fusiform-rh', 'posteriorcingulate-rh', 'transversetemporal-rh', 'precentral-rh', 'inferiortemporal-rh', 'middletemporal-rh', 'parahippocampal-rh', 'superiortemporal-rh', 'caudalmiddlefrontal-rh', 'insula-rh', 'superiorfrontal-rh', 'entorhinal-rh', 'caudalanteriorcingulate-rh', 'parsopercularis-rh', 'temporalpole-rh', 'rostralanteriorcingulate-rh', 'parstriangularis-rh', 'medialorbitofrontal-rh', 'rostralmiddlefrontal-rh', 'lateralorbitofrontal-rh', 'parsorbitalis-rh', 'frontalpole-rh'] label_names = ['bankssts-lh', 'bankssts-rh', 'caudalanteriorcingulate-lh', 'caudalanteriorcingulate-rh', 'caudalmiddlefrontal-lh', 'caudalmiddlefrontal-rh', 'cuneus-lh', 'cuneus-rh', 'entorhinal-lh', 'entorhinal-rh', 'frontalpole-lh', 'frontalpole-rh', 'fusiform-lh', 'fusiform-rh', 'inferiorparietal-lh', 'inferiorparietal-rh', 'inferiortemporal-lh', 'inferiortemporal-rh', 'insula-lh', 'insula-rh', 'isthmuscingulate-lh', 'isthmuscingulate-rh', 'lateraloccipital-lh', 'lateraloccipital-rh', 'lateralorbitofrontal-lh', 'lateralorbitofrontal-rh', 'lingual-lh', 'lingual-rh', 'medialorbitofrontal-lh', 'medialorbitofrontal-rh', 'middletemporal-lh', 'middletemporal-rh', 'paracentral-lh', 'paracentral-rh', 'parahippocampal-lh', 'parahippocampal-rh', 'parsopercularis-lh', 'parsopercularis-rh', 'parsorbitalis-lh', 'parsorbitalis-rh', 'parstriangularis-lh', 'parstriangularis-rh', 'pericalcarine-lh', 'pericalcarine-rh', 'postcentral-lh', 'postcentral-rh', 'posteriorcingulate-lh', 'posteriorcingulate-rh', 'precentral-lh', 'precentral-rh', 'precuneus-lh', 'precuneus-rh', 'rostralanteriorcingulate-lh', 'rostralanteriorcingulate-rh', 'rostralmiddlefrontal-lh', 'rostralmiddlefrontal-rh', 'superiorfrontal-lh', 'superiorfrontal-rh', 'superiorparietal-lh', 'superiorparietal-rh', 'superiortemporal-lh', 'superiortemporal-rh', 'supr
Bug#896021: mruby: CVE-2018-10199: Use after free in File#initilialize_copy
Source: mruby Version: 1.4.0-1 Severity: grave Tags: patch security upstream Forwarded: https://github.com/mruby/mruby/issues/4001 Hi, The following vulnerability was published for mruby. CVE-2018-10199[0]: | In versions of mruby up to and including 1.4.0, a use-after-free | vulnerability exists in src/io.c::File#initilialize_copy(). An attacker | that can cause Ruby code to be run can possibly use this to execute | arbitrary code. 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-10199 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10199 [1] https://github.com/mruby/mruby/issues/4001 [2] https://github.com/mruby/mruby/commit/b51b21fc63c9805862322551387d9036f2b63433 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#896019: libglib2.0-0: undefined symbol g_date_copy breaking many programs
Am 18.04.2018 um 20:43 schrieb rektide de la faye: > Package: libglib2.0-0 > Version: 2.56.1-2 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > I recently updated a number of packages on my Debian/testing laptop, via > aptitude > and included in that upgrade to satisfy dependencies was libglib-2.0-0. > > Since installing, many many programs on my system refuse to start. Trying > to run nmcli, for example, returns: > > nmcli: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0: > undefined symbol: g_date_copy > > I also see like errors trying to run lightdm, urxvt, vi. > This file appears to be a symlink, pointing at > /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.5600.1. > > There is a .4200.0 in that directory. I tried symlinking to that, but got a > different set of undefined > symbol errors keeping me from running things- g_option_group_unref. > Where is that .4200.0 file coming from? This looks pretty much like a duplicate of #894763 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#896020: mruby: CVE-2018-10191: Use after free caused by integer overflow in environment stack
Source: mruby Version: 1.0.0+20141015+gitb4cc962c-1 Severity: grave Tags: patch security upstream Forwarded: https://github.com/mruby/mruby/issues/3995 Hi, The following vulnerability was published for mruby. CVE-2018-10191[0]: | In versions of mruby up to and including 1.4.0, an integer overflow | exists in src/vm.c::mrb_vm_exec() when handling OP_GETUPVAR in the | presence of deep scope nesting, resulting in a use-after-free. An | attacker that can cause Ruby code to be run can use this to possibly | execute arbitrary code. Demostrable/verifiable with an ASAN build of mruby: dummy@sid:~$ ./mruby-1.4.0/bin/mruby ./use_after_free.rb = ==3180==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x62514100 at pc 0x004a77c3 bp 0x7ffef79d70d0 sp 0x7ffef79d70c8 READ of size 16 at 0x62514100 thread T0 #0 0x4a77c2 in mrb_vm_exec src/vm.c:1196 #1 0x4ac408 in mrb_vm_run src/vm.c:935 #2 0x52df53 in mrb_load_exec mrbgems/mruby-compiler/core/parse.y:5840 #3 0x404036 in main mrbgems/mruby-bin-mruby/tools/mruby/mruby.c:227 #4 0x7ffb5b242a86 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21a86) #5 0x405b89 in _start (/home/dummy/mruby-1.4.0/bin/mruby+0x405b89) Address 0x62514100 is a wild pointer. SUMMARY: AddressSanitizer: heap-buffer-overflow src/vm.c:1196 in mrb_vm_exec Shadow bytes around the buggy address: 0x0c4a7fffa7d0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c4a7fffa7e0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c4a7fffa7f0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c4a7fffa800: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c4a7fffa810: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa =>0x0c4a7fffa820:[fa]fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c4a7fffa830: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c4a7fffa840: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c4a7fffa850: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c4a7fffa860: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c4a7fffa870: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa Shadow byte legend (one shadow byte represents 8 application bytes): Addressable: 00 Partially addressable: 01 02 03 04 05 06 07 Heap left redzone: fa Freed heap region: fd Stack left redzone: f1 Stack mid redzone: f2 Stack right redzone: f3 Stack after return: f5 Stack use after scope: f8 Global redzone: f9 Global init order: f6 Poisoned by user:f7 Container overflow: fc Array cookie:ac Intra object redzone:bb ASan internal: fe Left alloca redzone: ca Right alloca redzone:cb ==3180==ABORTING dummy@sid:~$ dummy@sid:~$ ./mruby-1.4.0/bin/mruby ./null_ptr_deref.rb /root/mruby-1.4.0/src/class.c:94:11: runtime error: member access within null pointer of type 'struct RClass' ASAN:DEADLYSIGNAL = ==3189==ERROR: AddressSanitizer: SEGV on unknown address 0x (pc 0x004b03b3 bp 0x7ffe636d25b0 sp 0x7ffe636d2560 T0) ==3189==The signal is caused by a READ memory access. ==3189==Hint: address points to the zero page. #0 0x4b03b2 in prepare_singleton_class src/class.c:94 #1 0x4c18da in mrb_singleton_class src/class.c:1320 #2 0x4858fa in mrb_vm_exec src/vm.c:2895 #3 0x4ac408 in mrb_vm_run src/vm.c:935 #4 0x52df53 in mrb_load_exec mrbgems/mruby-compiler/core/parse.y:5840 #5 0x404036 in main mrbgems/mruby-bin-mruby/tools/mruby/mruby.c:227 #6 0x7fe21ffe5a86 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21a86) #7 0x405b89 in _start (/home/dummy/mruby-1.4.0/bin/mruby+0x405b89) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV src/class.c:94 in prepare_singleton_class ==3189==ABORTING dummy@sid:~$ 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-10191 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10191 [1] https://github.com/mruby/mruby/issues/3995 Regards, Salvatore
Bug#862883: Port from libnm-glib/libnm-util to libnm
Am 18.04.2018 um 19:55 schrieb Pino Toscano: > In data mercoledì 18 aprile 2018 19:35:01 CEST, Michael Biebl ha scritto: >> Control: tags -1 + patch >> >> I made some more minor tweaks to v2: >> >> - Update debian/changelog >> - Drop debian/patches/add_glib_for_nm, no longer necessary >> >> v3 of the debdiff is attached. I was told that it's probably not worth >> forwarding this upstream, as KDE4 development is pretty much dormant. > > While the KDE 4 development is basically stopped, the code here was > basically copied into the compatibility framework kdelibs4support; > hence I'd prefer to see the resolution of #862877 (or at least upstream > feedback on the patch for it), so the same fix can be backported here > too. So, we have upstream feedback now, but I'm not sure what to make of it. It seems the preference is to simply drop NM support in networkstatus, given that NM support in kdelibs4support was never actually enabled and kde-runtime is basically on its way out anyway. I have no preference either way. Can you please let me know how you intend to proceed? Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#896019: libglib2.0-0: undefined symbol g_date_copy breaking many programs
Package: libglib2.0-0 Version: 2.56.1-2 Severity: grave Justification: renders package unusable Dear Maintainer, I recently updated a number of packages on my Debian/testing laptop, via aptitude and included in that upgrade to satisfy dependencies was libglib-2.0-0. Since installing, many many programs on my system refuse to start. Trying to run nmcli, for example, returns: nmcli: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0: undefined symbol: g_date_copy I also see like errors trying to run lightdm, urxvt, vi. This file appears to be a symlink, pointing at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.5600.1. There is a .4200.0 in that directory. I tried symlinking to that, but got a different set of undefined symbol errors keeping me from running things- g_option_group_unref. This does appear to gravely reduce the functionality of my workstation. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (250, 'unstable'), (600, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.4.1 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/zsh Versions of packages libglib2.0-0 depends on: ii libc62.27-3 ii libffi6 3.2.1-4 ii libmount12.30.2-0.1 ii libpcre3 8.39-9 ii libselinux1 2.6-3+b1 ii zlib1g 2.8.dfsg-2+b1 Versions of packages libglib2.0-0 recommends: ii libglib2.0-data 2.56.1-2 ii shared-mime-info 1.7-1 ii xdg-user-dirs 0.15-2 libglib2.0-0 suggests no packages. -- no debconf information
Bug#862877: Port from libnm-glib/libnm-util to libnm
Hi Pino Am 18.04.2018 um 19:50 schrieb Pino Toscano: > In data mercoledì 18 aprile 2018 19:01:53 CEST, Michael Biebl ha scritto: >> Control: tags -1 + patch >> >> Attached is a debdiff which is based on lubo's patch. >> >> Changes to the initial patch >> - Use Q_SLOTS instead of slots, instead of simply commenting it out >> - Use nm-dbus-interface.h include instead of NetworkManager.h, so we >> don't pull in any glib/gio related headers >> - Drop NM_CHECK_VERSION define, no longer needed. >> >> I've submitted the same patch upstream. > > Do you have the link to the upstream submission? Note that these days > upstream uses phabricator [1] for patch reviews. The bug report has been tagged accordingly already, but for completeness sake, the upstream bug report is https://bugs.kde.org/show_bug.cgi?id=393255 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#862883: Port from libnm-glib/libnm-util to libnm
In data mercoledì 18 aprile 2018 19:35:01 CEST, Michael Biebl ha scritto: > Control: tags -1 + patch > > I made some more minor tweaks to v2: > > - Update debian/changelog > - Drop debian/patches/add_glib_for_nm, no longer necessary > > v3 of the debdiff is attached. I was told that it's probably not worth > forwarding this upstream, as KDE4 development is pretty much dormant. While the KDE 4 development is basically stopped, the code here was basically copied into the compatibility framework kdelibs4support; hence I'd prefer to see the resolution of #862877 (or at least upstream feedback on the patch for it), so the same fix can be backported here too. > I plan to NMU kde-runtime in a week or so and upload to DELAYED/10 > unless I hear back from you. Please holler, if you have any objections. See above. Also, there are local changes in the packaging git, and possibly I should land one/two more (although I have not worked on them yet). -- Pino Toscano signature.asc Description: This is a digitally signed message part.
Bug#862877: Port from libnm-glib/libnm-util to libnm
In data mercoledì 18 aprile 2018 19:01:53 CEST, Michael Biebl ha scritto: > Control: tags -1 + patch > > Attached is a debdiff which is based on lubo's patch. > > Changes to the initial patch > - Use Q_SLOTS instead of slots, instead of simply commenting it out > - Use nm-dbus-interface.h include instead of NetworkManager.h, so we > don't pull in any glib/gio related headers > - Drop NM_CHECK_VERSION define, no longer needed. > > I've submitted the same patch upstream. Do you have the link to the upstream submission? Note that these days upstream uses phabricator [1] for patch reviews. [1] https://phabricator.kde.org/ > I plan to NMU in a week or so and upload to DELAYED/10 unless I hear > back from you. I'd rather prefer to get first the feedback from upstream, so we can possibly even just backport the upstream commit. -- Pino Toscano signature.asc Description: This is a digitally signed message part.
Bug#862678: Switch from network-manager-dev to libnm-dev
Hi Ari, did you find some time to look into this? Anything I can help you with? Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Processed: Re: Port from libnm-glib/libnm-util to libnm
Processing control commands: > tags -1 + patch Bug #862883 [src:kde-runtime] Port from libnm-glib/libnm-util to libnm Added tag(s) patch. -- 862883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862883 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#862883: Port from libnm-glib/libnm-util to libnm
Control: tags -1 + patch
I made some more minor tweaks to v2:
- Update debian/changelog
- Drop debian/patches/add_glib_for_nm, no longer necessary
v3 of the debdiff is attached. I was told that it's probably not worth
forwarding this upstream, as KDE4 development is pretty much dormant.
I plan to NMU kde-runtime in a week or so and upload to DELAYED/10
unless I hear back from you. Please holler, if you have any objections.
Regards,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
diff -Nru kde-runtime-17.08.3/debian/changelog
kde-runtime-17.08.3/debian/changelog
--- kde-runtime-17.08.3/debian/changelog2018-01-11 09:22:25.0
+0100
+++ kde-runtime-17.08.3/debian/changelog2018-04-14 15:02:04.0
+0200
@@ -1,3 +1,12 @@
+kde-runtime (4:17.08.3-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Update solid-networkstatus to use libnm. (Closes: #862883)
+ * Drop debian/patches/add_glib_for_nm, no longer necessary with the above
+changes.
+
+ -- Michael Biebl Sat, 14 Apr 2018 13:02:04 +
+
kde-runtime (4:17.08.3-1) unstable; urgency=medium
* Team upload.
diff -Nru kde-runtime-17.08.3/debian/control kde-runtime-17.08.3/debian/control
--- kde-runtime-17.08.3/debian/control 2018-01-06 11:49:18.0 +0100
+++ kde-runtime-17.08.3/debian/control 2018-04-14 15:02:04.0 +0200
@@ -24,7 +24,7 @@
libjpeg-dev,
libkactivities-dev,
liblzma-dev,
- libnm-util-dev (>= 0.7) [linux-any],
+ libnm-dev (>= 1.0.0) [linux-any],
libntrack-qt4-dev [linux-any],
libopenexr-dev,
libphonon-dev (>= 4:4.6.0really4.4.3),
@@ -35,7 +35,6 @@
libwebp-dev,
libx11-dev,
libxcursor-dev,
- network-manager-dev (>= 0.7.0) [linux-any],
pkg-config,
pkg-kde-tools (>= 0.12),
shared-mime-info,
diff -Nru kde-runtime-17.08.3/debian/patches/add_glib_for_nm
kde-runtime-17.08.3/debian/patches/add_glib_for_nm
--- kde-runtime-17.08.3/debian/patches/add_glib_for_nm 2017-05-22
19:34:05.0 +0200
+++ kde-runtime-17.08.3/debian/patches/add_glib_for_nm 1970-01-01
01:00:00.0 +0100
@@ -1,25 +0,0 @@
-From: Debian/Kubuntu Qt/KDE Maintainers
-Date: Sat, 18 Jun 2016 16:24:29 +0200
-Subject: add_glib_for_nm
-
- solid-networkstatus/kded/CMakeLists.txt | 6 ++
- 1 file changed, 6 insertions(+)
-
-diff --git a/solid-networkstatus/kded/CMakeLists.txt
b/solid-networkstatus/kded/CMakeLists.txt
-index 633c7f1394..5dfcbf4f8d 100644
a/solid-networkstatus/kded/CMakeLists.txt
-+++ b/solid-networkstatus/kded/CMakeLists.txt
-@@ -16,6 +16,12 @@ set_package_properties(NetworkManager PROPERTIES
DESCRIPTION "The NetworkManager
- )
-
- if(NETWORKMANAGER_FOUND)
-+find_package(PkgConfig REQUIRED)
-+pkg_check_modules(GLIB_PKG glib-2.0)
-+
-+if (GLIB_PKG_FOUND)
-+ include_directories(${GLIB_PKG_INCLUDE_DIRS})
-+endif()
- macro_ensure_version("0.7.0" ${NETWORKMANAGER_VERSION} NM_0_7)
- if(NM_0_7)
- MESSAGE(STATUS "Adding in-process NetworkManager service-wart to kded
module")
diff -Nru
kde-runtime-17.08.3/debian/patches/cmake-add-NetworkManager-module.patch
kde-runtime-17.08.3/debian/patches/cmake-add-NetworkManager-module.patch
--- kde-runtime-17.08.3/debian/patches/cmake-add-NetworkManager-module.patch
1970-01-01 01:00:00.0 +0100
+++ kde-runtime-17.08.3/debian/patches/cmake-add-NetworkManager-module.patch
2018-04-14 15:02:04.0 +0200
@@ -0,0 +1,56 @@
+From 5711ab8b4b053e5d2f4f0b5831ff2a1d37cdf9fa Mon Sep 17 00:00:00 2001
+From: Lubomir Rintel
+Date: Tue, 19 Dec 2017 19:45:23 +0100
+Subject: [PATCH] cmake: add NetworkManager module
+
+This one looks for libnm as opposed to the deprecated libnm-glib.
+---
+ cmake/modules/FindNetworkManager.cmake | 40 ++
+ 1 file changed, 40 insertions(+)
+ create mode 100644 cmake/modules/FindNetworkManager.cmake
+
+Index: kde-runtime-17.08.3/cmake/modules/FindNetworkManager.cmake
+===
+--- /dev/null
kde-runtime-17.08.3/cmake/modules/FindNetworkManager.cmake
+@@ -0,0 +1,40 @@
++# - Try to find NetworkManager
++# Once done this will define
++#
++# NETWORKMANAGER_FOUND - system has NetworkManager
++# NETWORKMANAGER_INCLUDE_DIRS - the NetworkManager include directories
++# NETWORKMANAGER_LIBRARIES - the libraries needed to use NetworkManager
++# NETWORKMANAGER_CFLAGS - Compiler switches required for using NetworkManager
++# NETWORKMANAGER_VERSION - version number of NetworkManager
++
++# Copyright (c) 2006, Alexander Neundorf,
++# Copyright (c) 2007, Will Stephenson,
++#
++# Redistribution and use is allowed according to the terms of the BSD license.
++# For detail
Processed: Re: suricata: new version fails to start if eth0 not present
Processing control commands:
> reopen -1
Bug #895342 {Done: Arturo Borrero Gonzalez } [suricata]
suricata: new version fails to start if eth0 not present
Bug reopened
Ignoring request to alter fixed versions of bug #895342 to the same values
previously set
--
895342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895342
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#895342: suricata: new version fails to start if eth0 not present
Control: reopen -1 Hi Arturo, On Wed, Apr 18, 2018 at 11:07:32AM +0200, Arturo Borrero Gonzalez wrote: > If you check debian/tests/systemd-service-test.sh [0], the interface > in use by the config file is decided at runtime. This code runs only for one of the tests. It doesn't change the fact that the suricata service as a whole is broken on install when eth0 is not present, and all commands which try to talk to the daemon prior to that point in the tests will fail. You could fix the autopkgtests to not depend on eth0 if you moved the systemd-service-test.sh to run before all other tests. But I don't think that would fix this bug, because I think the behavior of the package itself is still wrong. > What autopkgtest tests are you running? The ones shipped in your package. > This seem like an ubuntu specific issue. All tests in debian are going > fine, both in unstable and in testing [1]. The tests work fine in Debian because the testbed HAPPENS TO HAVE AN eth0 INTERFACE, as I said in the original bug report. I know the difference between Debian and Ubuntu and am not in the habit of gratuitously overinflating the severity of bugs filed in Debian for Ubuntu-specific issues. > This Debian bug may result in the package being removed from Debian > testing for no actual reason. I wrote the reason in my original bug report: I'm filing this as serious because it seems to me that neither of these behaviors - either starting up and being ineffective because it's running on the wrong interface, or failing to start up because the interface is hard-coded and not present - is a reasonable default behavior for an IDS. I think the interface should either be autodetected or prompted for at install time. I also wrote: Feel free to downgrade if you disagree. It's not clear to me that you disagree. It's not clear to me that you even read my bug report. So, reopening at original severity. > Closing this bug now as it seems totally bogus. There is at least one bug here in the package, which is that the autopkgtests make a brittle assumption that eth0 will be available in the test bed. eth0 is a legacy interface name in the kernel, and despite the fact that eth0 is currently present on the ci.debian.net testbeds, this is not a robust assumption. If you want to reorder the tests so that the config file setup is done first, then that would address the bug in the autopkgtests. I still also think it's a bug that the package installs successfully but the daemon fails to start if there is no eth0 interface. I think best practice is that a package ensures its daemons can be started before the package is configured, because it's better to surface a failure to the admin than to consider a package "configured" without providing core functionality to reverse-dependencies. This was in my view the issue that warranted a 'serious' severity, but you are free to disagree and downgrade the bug. > [0] > https://salsa.debian.org/pkg-suricata-team/pkg-suricata/blob/master/debian/tests/systemd-service-test.sh > [1] https://ci.debian.net/packages/s/suricata/ -- 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
Processed: Re: Port from libnm-glib/libnm-util to libnm
Processing control commands: > tags -1 + patch Bug #862877 [src:kdelibs4support] Port from libnm-glib/libnm-util to libnm Added tag(s) patch. -- 862877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862877 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#862877: Port from libnm-glib/libnm-util to libnm
Control: tags -1 + patch
Attached is a debdiff which is based on lubo's patch.
Changes to the initial patch
- Use Q_SLOTS instead of slots, instead of simply commenting it out
- Use nm-dbus-interface.h include instead of NetworkManager.h, so we
don't pull in any glib/gio related headers
- Drop NM_CHECK_VERSION define, no longer needed.
I've submitted the same patch upstream.
I plan to NMU in a week or so and upload to DELAYED/10 unless I hear
back from you.
Regards,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
diff -Nru kdelibs4support-5.44.0/debian/changelog
kdelibs4support-5.44.0/debian/changelog
--- kdelibs4support-5.44.0/debian/changelog 2018-03-23 08:19:17.0
+0100
+++ kdelibs4support-5.44.0/debian/changelog 2018-04-18 18:35:20.0
+0200
@@ -1,3 +1,10 @@
+kdelibs4support (5.44.0-2.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Port networkmanagerstatus to libnm. (Closes: #862877)
+
+ -- Michael Biebl Wed, 18 Apr 2018 18:35:20 +0200
+
kdelibs4support (5.44.0-2) sid; urgency=medium
* New revision
diff -Nru kdelibs4support-5.44.0/debian/control
kdelibs4support-5.44.0/debian/control
--- kdelibs4support-5.44.0/debian/control 2018-03-23 08:19:17.0
+0100
+++ kdelibs4support-5.44.0/debian/control 2018-04-18 18:35:19.0
+0200
@@ -36,7 +36,7 @@
libssl1.0-dev,
liburi-perl,
libx11-dev,
- network-manager-dev (>= 0.7.0~) [linux-any],
+ libnm-dev (>= 1.0.0) [linux-any],
pkg-config,
pkg-kde-tools (>= 0.15.15ubuntu1~),
qtbase5-dev (>= 5.7.0~),
diff -Nru
kdelibs4support-5.44.0/debian/patches/networkmanagerstatus-port-to-libnm.patch
kdelibs4support-5.44.0/debian/patches/networkmanagerstatus-port-to-libnm.patch
---
kdelibs4support-5.44.0/debian/patches/networkmanagerstatus-port-to-libnm.patch
1970-01-01 01:00:00.0 +0100
+++
kdelibs4support-5.44.0/debian/patches/networkmanagerstatus-port-to-libnm.patch
2018-04-18 18:35:20.0 +0200
@@ -0,0 +1,146 @@
+From 8a9345633319cfd97d42a6e7ef4bbd0d89c561a2 Mon Sep 17 00:00:00 2001
+From: Lubomir Rintel
+Date: Tue, 19 Dec 2017 18:58:14 +0100
+Subject: [PATCH] networkmanagerstatus: port to libnm
+
+libnm-util has been deprecated for three years and is eventually going
+to disappear.
+As libnm has been introduced in NetworkManager 1.0.0, the version checks
+are no longer necessary, so drop them.
+---
+ cmake/modules/FindNetworkManager.cmake| 20 +--
+ src/solid-networkstatus/kded/CMakeLists.txt | 12 +--
+ .../kded/networkmanagerstatus.cpp | 12 +--
+ .../kded/networkmanagerstatus.h | 2 +-
+ 4 files changed, 16 insertions(+), 30 deletions(-)
+
+diff --git a/cmake/modules/FindNetworkManager.cmake
b/cmake/modules/FindNetworkManager.cmake
+index ced2017c..269bef6b 100644
+--- a/cmake/modules/FindNetworkManager.cmake
b/cmake/modules/FindNetworkManager.cmake
+@@ -14,29 +14,27 @@
+ # For details see the accompanying COPYING-CMAKE-SCRIPTS file.
+
+
+-IF (NETWORKMANAGER_INCLUDE_DIRS AND NM-UTIL_INCLUDE_DIRS)
++IF (NETWORKMANAGER_INCLUDE_DIRS)
+# in cache already
+SET(NetworkManager_FIND_QUIETLY TRUE)
+-ENDIF (NETWORKMANAGER_INCLUDE_DIRS AND NM-UTIL_INCLUDE_DIRS)
++ENDIF (NETWORKMANAGER_INCLUDE_DIRS)
+
+ IF (NOT WIN32)
+# use pkg-config to get the directories and then use these values
+# in the FIND_PATH() and FIND_LIBRARY() calls
+find_package(PkgConfig)
+- PKG_SEARCH_MODULE( NETWORKMANAGER NetworkManager )
+- PKG_SEARCH_MODULE( NM-UTIL libnm-util )
++ PKG_SEARCH_MODULE( NETWORKMANAGER libnm )
+ ENDIF (NOT WIN32)
+
+-IF (NETWORKMANAGER_FOUND AND NM-UTIL_FOUND)
++IF (NETWORKMANAGER_FOUND)
+IF (NOT NetworkManager_FIND_QUIETLY)
+- MESSAGE(STATUS "Found NetworkManager ${NETWORKMANAGER_VERSION}:
${NETWORKMANAGER_LIBRARY_DIRS}")
+- MESSAGE(STATUS "Found libnm-util: ${NM-UTIL_LIBRARY_DIRS}")
++ MESSAGE(STATUS "Found libnm ${NETWORKMANAGER_VERSION}:
${NETWORKMANAGER_LIBRARY_DIRS}")
+ENDIF (NOT NetworkManager_FIND_QUIETLY)
+-ELSE (NETWORKMANAGER_FOUND AND NM-UTIL_FOUND)
++ELSE (NETWORKMANAGER_FOUND)
+IF (NetworkManager_FIND_REQUIRED)
+- MESSAGE(FATAL_ERROR "Could NOT find NetworkManager or libnm-util, check
FindPkgConfig output above!")
++ MESSAGE(FATAL_ERROR "Could NOT find libnm, check FindPkgConfig output
above!")
+ENDIF (NetworkManager_FIND_REQUIRED)
+-ENDIF (NETWORKMANAGER_FOUND AND NM-UTIL_FOUND)
++ENDIF (NETWORKMANAGER_FOUND)
+
+-MARK_AS_ADVANCED(NETWORKMANAGER_INCLUDE_DIRS NM-UTIL_INCLUDE_DIRS)
++MARK_AS_ADVANCED(NETWORKMANAGER_INCLUDE_DIRS)
+
+diff --git a/src/solid-networkstatus/kded/CMakeLists.txt
b/src/solid-networkstatus/kded/CMakeLists.txt
+index 9fa30651..604209fa 100644
+--- a/src/solid-networkstatus/kded/CMakeLists.txt
b/src
Bug#894619: sdcc: diff for NMU version 3.5.0+dfsg-2.1
Control: tags 894619 + pending
Dear maintainer,
I've prepared an NMU for sdcc (versioned as 3.5.0+dfsg-2.1) and uploaded
it to DELAYED/15. Please feel free to tell me if I should cancel it.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
diff -Nru sdcc-3.5.0+dfsg/debian/changelog sdcc-3.5.0+dfsg/debian/changelog
--- sdcc-3.5.0+dfsg/debian/changelog 2016-03-19 20:31:19.0 +0200
+++ sdcc-3.5.0+dfsg/debian/changelog 2018-04-18 19:34:21.0 +0300
@@ -1,3 +1,11 @@
+sdcc (3.5.0+dfsg-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add patch from Dr. Tobias Quathamer to fix FTBFS with lyx 2.3.
+(Closes: #894619)
+
+ -- Adrian Bunk Wed, 18 Apr 2018 19:34:21 +0300
+
sdcc (3.5.0+dfsg-2) unstable; urgency=medium
* Add dependency on gsfonts (Closes: #818447)
diff -Nru sdcc-3.5.0+dfsg/debian/patches/04_fix_ftbfs_with_lyx_2.3.patch sdcc-3.5.0+dfsg/debian/patches/04_fix_ftbfs_with_lyx_2.3.patch
--- sdcc-3.5.0+dfsg/debian/patches/04_fix_ftbfs_with_lyx_2.3.patch 1970-01-01 02:00:00.0 +0200
+++ sdcc-3.5.0+dfsg/debian/patches/04_fix_ftbfs_with_lyx_2.3.patch 2018-04-18 19:34:06.0 +0300
@@ -0,0 +1,39 @@
+--- a/doc/sdccman.lyx
b/doc/sdccman.lyx
+@@ -13,14 +13,6 @@
+ \mbox{\ifx\def@pt\pas@pt\cite@rig{#2}\else\cite@rig[#1]{#2}\fi}}
+ \renewcommand{\underbar}[1]{{\let\cite\b@xcite\uline{#1}}}
+ \pdfoptionpdfminorversion=3
+-\usepackage[
+- pdftitle={SDCC Compiler User Guide},
+- pdfauthor={SDCC development team},
+- pdfsubject={installation, user manual},
+- pdfkeywords={68hc08 8032 8051 ansi iso c compiler assembler CPU DS390 embedded development free Floating Point Arithmetic Freescale GPL HC08 S08 inline Intel ISO/IEC 9899:1990 Linux MAC OS X manual Maxim mcs51 Microchip microcontroller open source PIC Unix Windows Z80 Z180 Zilog Rabbit},
+- pdfpagemode=UseOutlines,
+- colorlinks=true,
+- linkcolor=blue] {hyperref}
+ %
+ \sloppy
+ \tolerance=500
+@@ -51,7 +43,20 @@
+ \index_command default
+ \paperfontsize default
+ \spacing single
+-\use_hyperref false
++\use_hyperref true
++\pdf_title "SDCC Compiler User Guide"
++\pdf_author "SDCC development team"
++\pdf_subject "installation, user manual"
++\pdf_keywords "68hc08 8032 8051 ansi iso c compiler assembler CPU DS390 embedded development free Floating Point Arithmetic Freescale GPL HC08 S08 inline Intel ISO/IEC 9899:1990 Linux MAC OS X manual Maxim mcs51 Microchip microcontroller open source PIC Unix Windows Z80 Z180 Zilog Rabbit"
++\pdf_bookmarks true
++\pdf_bookmarksnumbered false
++\pdf_bookmarksopen false
++\pdf_bookmarksopenlevel 1
++\pdf_breaklinks false
++\pdf_pdfborder false
++\pdf_colorlinks true
++\pdf_backref false
++\pdf_pdfusetitle true
+ \papersize letterpaper
+ \use_geometry true
+ \use_package amsmath 1
diff -Nru sdcc-3.5.0+dfsg/debian/patches/series sdcc-3.5.0+dfsg/debian/patches/series
--- sdcc-3.5.0+dfsg/debian/patches/series 2016-03-19 20:24:24.0 +0200
+++ sdcc-3.5.0+dfsg/debian/patches/series 2018-04-18 19:34:20.0 +0300
@@ -1,3 +1,4 @@
01_enable_huge_model.patch
02_enable_ppc64.patch
03_spelling.patch
+04_fix_ftbfs_with_lyx_2.3.patch
Processed: sdcc: diff for NMU version 3.5.0+dfsg-2.1
Processing control commands: > tags 894619 + pending Bug #894619 [src:sdcc] sdcc FTBFS with lyx 2.3.0-2 Added tag(s) pending. -- 894619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894619 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#891547: marked as done (cairo: test runs into buildd timeout on armel)
Your message dated Wed, 18 Apr 2018 16:35:21 + with message-id and subject line Bug#891547: fixed in cairo 1.15.10-3 has caused the Debian Bug report #891547, regarding cairo: test runs into buildd timeout on armel 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.) -- 891547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891547 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cairo Version: 1.15.10-2 Severity: serious https://buildd.debian.org/status/package.php?p=cairo&suite=sid On the fpu-less armel port the build ran into the 150 minute timeout during the tests. With an fpu-less buildd the mips build ran into the 360 minute timeout during the tests. These timeouts are time without anything output during the build. On the abel porterbox (that is the same hardware as the armel/armhf buildds) I got a successful armel build after 4h 18m. This is three times the durtion of the successful armhf build, which wouldn't be surprising if plenty of fp code is run. The ia64 failure is likely a real problem somewhere, Jason is currently debugging that. Possible solutions: 1. get some output during the tests (disable the output redirection), or 2. don't run the tests on the armel and mips architectures (mipsel and mips64el are fine) --- End Message --- --- Begin Message --- Source: cairo Source-Version: 1.15.10-3 We believe that the bug you reported is fixed in the latest version of cairo, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 891...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emilio Pozuelo Monfort (supplier of updated cairo 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: Wed, 18 Apr 2018 18:07:55 +0200 Source: cairo Binary: libcairo2 libcairo2-dev libcairo2-doc libcairo-script-interpreter2 libcairo-gobject2 cairo-perf-utils libcairo2-udeb Architecture: source Version: 1.15.10-3 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Emilio Pozuelo Monfort Description: cairo-perf-utils - Cairo 2D vector graphics library performance utilities libcairo-gobject2 - Cairo 2D vector graphics library (GObject library) libcairo-script-interpreter2 - Cairo 2D vector graphics library (script interpreter) libcairo2 - Cairo 2D vector graphics library libcairo2-dev - Development files for the Cairo 2D graphics library libcairo2-doc - Documentation for the Cairo Multi-platform 2D graphics library libcairo2-udeb - Cairo 2D vector graphics library (udeb) Closes: 891547 Changes: cairo (1.15.10-3) unstable; urgency=medium . * Disable the test suite (enabled in 1.15.10-2). The test results were ignored anyway, and the test suite is quite broken at the moment so we won't be able to make the results fatal anytime soon. Furthermore, there's only one mega-test that runs all the smaller tests, and this causes automake to emit no output until the one test is done, making the build fail on builders with no FPU due to inactivity. Closes: #891547. Checksums-Sha1: 309918844c2d1c9200085feed8ea4cdbd94506a6 2877 cairo_1.15.10-3.dsc de180498ac563249b93ee5e17ba9aa26f90644b3 41881364 cairo_1.15.10.orig.tar.xz 9e69e221524270c6133a03bd5916b60f99682cd2 30060 cairo_1.15.10-3.debian.tar.xz 383e62856b29de87bf5738714db57b10997cd41a 7221 cairo_1.15.10-3_source.buildinfo Checksums-Sha256: c2397e1f83177e22c358b57f5706e114cb1d149108311afaeb8a57482c6d49a9 2877 cairo_1.15.10-3.dsc 62ca226134cf2f1fd114bea06f8b374eb37f35d8e22487eaa54d5e9428958392 41881364 cairo_1.15.10.orig.tar.xz 5315c7c4400d1245a7d335afdaf25be580fe2782e9f47a0f4cb1bc7758a63068 30060 cairo_1.15.10-3.debian.tar.xz 4d2d3e8acce6be3dad2f4be037f17db88b707884f901765acba857de8143bb40 7221 cairo_1.15.10-3_source.buildinfo Files: 418205827a328325ffa10239d416de03 2877 libs optional cairo_1.15.10-3.dsc f060381576d67c855fad03e327fc9a69 41881364 libs optional cairo_1.15.10.orig.tar.xz 2a9685694f8e7ef9f914a2d67b41c9cc 30060 libs optional cairo_1.15.10-3.debian.tar.xz 6899616a3789f3a75905dec630d91433 7221 libs optional cairo_1.15.10-3_source.buildinfo -BEGIN PGP
Bug#896007: openjdk-9: EOL; do not ship with buster
Source: openjdk-9 Severity: serious Hi, OpenJDK 9 already is end of life, see [1]. We should thus change the default OpenJDK version to 10 (and later 11 before the buster release) and remove openjdk-9. Cheers, Emilio [1] http://www.oracle.com/technetwork/java/eol-135779.html -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#896006: eclipse: FTBFS on buster, unmappable character encoding errors
Source: eclipse Version: 3.8.1-11 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** Subject: eclipse: FTBFS on buster, unmappable character encoding error Source: eclipse Version: 3.8.1-11 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, I'm unable to rebuild eclipse from source on Debian Buster. Reproducer: debootstrap buster buster systemd-nspawn -D buster # add deb-src line to /etc/apt/sources.list apt-get update apt-get build-dep eclipse apt-get source eclipse cd eclipse-* dpkg-buildpackage -us -uc . It fails with these messages: @dot: [mkdir] Created dir: /root/eclipse-3.8.1/build/eclipse-3.8.1-src/plugins/org.eclipse.osgi/@dot [javac] Using javac -source 1.5 is no longer supported, switching to 1.7 [javac] Using javac -target 1.5 is no longer supported, switching to 1.7 [javac] Compiling 449 source files to /root/eclipse-3.8.1/build/eclipse-3.8.1-src/plugins/org.eclipse.osgi/@dot [javac] warning: [options] bootstrap class path not set in conjunction with -source 1.7 [javac] /root/eclipse-3.8.1/build/eclipse-3.8.1-src/plugins/org.eclipse.osgi/osgi/src/org/osgi/framework/FrameworkUtil.java:120: error: unmappable character (0xC3) for encoding US-ASCII [javac] * street = 9C\, Avenue St. Dr??z??ry, o=ACME, c=US [javac] ^ [javac] /root/eclipse-3.8.1/build/eclipse-3.8.1-src/plugins/org.eclipse.osgi/osgi/src/org/osgi/framework/FrameworkUtil.java:120: error: unmappable character (0xA9) for encoding US-ASCII [javac] * street = 9C\, Avenue St. Dr??z??ry, o=ACME, c=US [javac]^ [javac] /root/eclipse-3.8.1/build/eclipse-3.8.1-src/plugins/org.eclipse.osgi/osgi/src/org/osgi/framework/FrameworkUtil.java:120: error: unmappable character (0xC3) for encoding US-ASCII [javac] * street = 9C\, Avenue St. Dr??z??ry, o=ACME, c=US [javac] ^ [javac] /root/eclipse-3.8.1/build/eclipse-3.8.1-src/plugins/org.eclipse.osgi/osgi/src/org/osgi/framework/FrameworkUtil.java:120: error: unmappable character (0xA9) for encoding US-ASCII [javac] * street = 9C\, Avenue St. Dr??z??ry, o=ACME, c=US [javac] ^ [javac] /root/eclipse-3.8.1/build/eclipse-3.8.1-src/plugins/org.eclipse.osgi/osgi/src/org/osgi/framework/FrameworkUtil.java:128: error: unmappable character (0xC3) for encoding US-ASCII [javac] * street = 9C\, Avenue St. Dr??z??ry, o=ACME, c=FR [javac] ^ [javac] /root/eclipse-3.8.1/build/eclipse-3.8.1-src/plugins/org.eclipse.osgi/osgi/src/org/osgi/framework/FrameworkUtil.java:128: error: unmappable character (0xA9) for encoding US-ASCII [javac] * street = 9C\, Avenue St. Dr??z??ry, o=ACME, c=FR [javac]^ [javac] /root/eclipse-3.8.1/build/eclipse-3.8.1-src/plugins/org.eclipse.osgi/osgi/src/org/osgi/framework/FrameworkUtil.java:128: error: unmappable character (0xC3) for encoding US-ASCII [javac] * street = 9C\, Avenue St. Dr??z??ry, o=ACME, c=FR [javac] ^ [javac] /root/eclipse-3.8.1/build/eclipse-3.8.1-src/plugins/org.eclipse.osgi/osgi/src/org/osgi/framework/FrameworkUtil.java:128: error: unmappable character (0xA9) for encoding US-ASCII [javac] * street = 9C\, Avenue St. Dr??z??ry, o=ACME, c=FR [javac] ^ [javac] 8 errors [javac] 1 warning BUILD FAILED /root/eclipse-3.8.1/build.xml:139: The following error occurred while executing this line: /root/eclipse-3.8.1/pdebuild.xml:208: The following error occurred while executing this line: /root/eclipse-3.8.1/build/eclipse-3.8.1-src/plugins/org.eclipse.osgi/build.xml:228: The following error occurred while executing this line: /root/eclipse-3.8.1/build/eclipse-3.8.1-src/plugins/org.eclipse.osgi/build.xml:90: Compile failed; see the compiler error output for details. Full log: https://gist.github.com/dsd/bae6116da6c69778cc7809383ce982ae This is with default locale settings: LANG= LANGUAGE= LC_ALL= I have also tried with LC_ALL values: C, C.UTF-8, en_US, en_US.UTF-8. None of them succeed although changing the value does mean that it ends up failing on different strings in different files. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.13.0-38
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org:
> reassign 893783 python3-tornado
Bug #893783 [spyder3] spyder3: does not start even after --reset
Bug reassigned from package 'spyder3' to 'python3-tornado'.
No longer marked as found in versions spyder/3.2.6+dfsg1-2.
Ignoring request to alter fixed versions of bug #893783 to the same values
previously set
> forcemerge 893360 893783
Bug #893360 {Done: Julian Taylor }
[python3-tornado] python3-tornado 5.0.0 breaks python3-zmq
Bug #893385 {Done: Julian Taylor }
[python3-tornado] ipykernel FTBFS: test failures
Bug #893474 {Done: Julian Taylor }
[python3-tornado] jupyter-core: AttributeError on launch since last update of
python 3.6 in Sid
Bug #894033 {Done: Julian Taylor }
[python3-tornado] jupyter-notebook: jupyter notebook: IOLoop has no attribute
initialized
Bug #893783 [python3-tornado] spyder3: does not start even after --reset
Severity set to 'serious' from 'grave'
Marked Bug as done
Added indication that 893783 affects
src:ipykernel,jupyter-notebook,src:jupyter-notebook,jupyter-nbconvert,python3-ipykernel,src:jupyter-client
Marked as fixed in versions pyzmq/17.0.0-1 and python-tornado/5.0.0-2.
Marked as found in versions python-tornado/5.0.0-1.
Bug #893385 {Done: Julian Taylor }
[python3-tornado] ipykernel FTBFS: test failures
Bug #893474 {Done: Julian Taylor }
[python3-tornado] jupyter-core: AttributeError on launch since last update of
python 3.6 in Sid
Bug #894033 {Done: Julian Taylor }
[python3-tornado] jupyter-notebook: jupyter notebook: IOLoop has no attribute
initialized
Merged 893360 893385 893474 893783 894033
> affects 893360 spyder3
Bug #893360 {Done: Julian Taylor }
[python3-tornado] python3-tornado 5.0.0 breaks python3-zmq
Bug #893385 {Done: Julian Taylor }
[python3-tornado] ipykernel FTBFS: test failures
Bug #893474 {Done: Julian Taylor }
[python3-tornado] jupyter-core: AttributeError on launch since last update of
python 3.6 in Sid
Bug #893783 {Done: Julian Taylor }
[python3-tornado] spyder3: does not start even after --reset
Bug #894033 {Done: Julian Taylor }
[python3-tornado] jupyter-notebook: jupyter notebook: IOLoop has no attribute
initialized
Added indication that 893360 affects spyder3
Added indication that 893385 affects spyder3
Added indication that 893474 affects spyder3
Added indication that 893783 affects spyder3
Added indication that 894033 affects spyder3
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
893360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893360
893385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893385
893474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893474
893783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893783
894033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894033
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#894580: knot-resolver: diff for NMU version 2.2.0-1.1
Control: tags 894580 + pending Dear maintainer, I've prepared an NMU for knot-resolver (versioned as 2.2.0-1.1) and uploaded it to DELAYED/14. Please feel free to tell me if I should cancel it. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed diff -Nru knot-resolver-2.2.0/debian/changelog knot-resolver-2.2.0/debian/changelog --- knot-resolver-2.2.0/debian/changelog 2018-04-09 06:46:47.0 +0300 +++ knot-resolver-2.2.0/debian/changelog 2018-04-18 18:43:53.0 +0300 @@ -1,3 +1,11 @@ +knot-resolver (2.2.0-1.1) unstable; urgency=high + + * Non-maintainer upload. + * Fix typo that prevented creation of the knot-resolver user, +thanks to Marco d'Itri for the bug report. (Closes: #894580) + + -- Adrian Bunk Wed, 18 Apr 2018 18:43:53 +0300 + knot-resolver (2.2.0-1) unstable; urgency=medium * new upstream release diff -Nru knot-resolver-2.2.0/debian/knot-resolver.postinst knot-resolver-2.2.0/debian/knot-resolver.postinst --- knot-resolver-2.2.0/debian/knot-resolver.postinst 2018-02-26 03:46:20.0 +0200 +++ knot-resolver-2.2.0/debian/knot-resolver.postinst 2018-04-18 18:43:53.0 +0300 @@ -1,7 +1,7 @@ #!/bin/sh set -e -if [ "$1" = "$configure" ]; then +if [ "$1" = "configure" ]; then adduser --quiet --system --group --no-create-home --home /var/cache/knot-resolver knot-resolver fi
Processed: knot-resolver: diff for NMU version 2.2.0-1.1
Processing control commands: > tags 894580 + pending Bug #894580 [knot-resolver] postinst does not create the knot-resolver user Added tag(s) pending. -- 894580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894580 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#896003: seaborn FTBFS with python-matplotlib 2.2.2-1
Source: seaborn
Version: 0.8.0-1
Severity: serious
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/seaborn.html
...
==
ERROR: seaborn.tests.test_palettes.TestColorPalettes.test_get_color_cycle
--
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
File
"/build/1st/seaborn-0.8.0/.pybuild/cpython2_2.7_seaborn/build/seaborn/tests/test_palettes.py",
line 297, in test_get_color_cycle
expected = mpl.rcParams['axes.color_cycle']
File "/usr/lib/python2.7/dist-packages/matplotlib/__init__.py", line 951, in
__getitem__
val = dict.__getitem__(self, key)
KeyError: 'axes.color_cycle'
--
Ran 421 tests in 173.467s
FAILED (SKIP=5, errors=1)
E: pybuild pybuild:336: test: plugin custom failed with: exit code=1: nosetests
-s -v /build/1st/seaborn-0.8.0/.pybuild/cpython2_2.7_seaborn/build/
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
make[1]: *** [debian/rules:28: override_dh_auto_test] Error 25
Bug#893704: marked as done (please remove dependency pdftk (will be removed when GCJ is removed))
Your message dated Wed, 18 Apr 2018 15:01:51 + with message-id and subject line Bug#893704: fixed in impressive 0.12.0-2 has caused the Debian Bug report #893704, regarding please remove dependency pdftk (will be removed when GCJ is removed) 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.) -- 893704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893704 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:impressive Version: 0.12.0-1 Severity: serious Tags: sid buster patch please remove the dependency on pdftk (will be removed when GCJ is removed). patch to build without pdftk: http://launchpadlibrarian.net/361431082/impressive_0.12.0-1_0.12.0-1ubuntu1.diff.gz --- End Message --- --- Begin Message --- Source: impressive Source-Version: 0.12.0-2 We believe that the bug you reported is fixed in the latest version of impressive, 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. Yaroslav Halchenko (supplier of updated impressive 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: Wed, 18 Apr 2018 10:28:56 -0400 Source: impressive Binary: impressive Architecture: source all Version: 0.12.0-2 Distribution: unstable Urgency: medium Maintainer: Yaroslav Halchenko Changed-By: Yaroslav Halchenko Description: impressive - PDF presentation tool with eye candies Closes: 893704 Changes: impressive (0.12.0-2) unstable; urgency=medium . * Remove hard dependency on pdftk, keep it only in Suggests since impressive could still make use of it at times (Closes: #893704) Checksums-Sha1: 7e07e66a967e4a5364761f474b287b13373a115b 2152 impressive_0.12.0-2.dsc a36ceed465159cf01a5923c527877026cd77fa02 9876 impressive_0.12.0-2.debian.tar.xz abb757cb0fa0ed2ee2b1ce23476812fbb527ed84 200320 impressive_0.12.0-2_all.deb 02d50fe222957263fed99d3230c7fbc0f8273e2c 12915 impressive_0.12.0-2_amd64.buildinfo Checksums-Sha256: c9c6d9eacd0d44097f68144589437f7842265aaa889a685965246af8fe2eb8b7 2152 impressive_0.12.0-2.dsc 2859bcf5e9856b02ec84b1d5cb1bca4895cfd38f98de0baefb3ee7a217a812d8 9876 impressive_0.12.0-2.debian.tar.xz c5321e56cb7eb1217e8c76e7e6aed78f11da39fd6500e017d707a8d0acaede72 200320 impressive_0.12.0-2_all.deb 71036d92c7e668303425f9e1bb46c3ed0dc0a1cf6d8d3070045c46005ed5b430 12915 impressive_0.12.0-2_amd64.buildinfo Files: a0084651cdd5cd46e295e27b7d0e12eb 2152 x11 optional impressive_0.12.0-2.dsc 5edf31db5e23ff162c785c8a8a34be8b 9876 x11 optional impressive_0.12.0-2.debian.tar.xz bb55465b8af1072990224db7ba48edc2 200320 x11 optional impressive_0.12.0-2_all.deb fe3289def43617ccd0ca5b25537d4893 12915 x11 optional impressive_0.12.0-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEExbkF8OjZ/ZZo/zZvot4jUGLaM/oFAlrXWN4ACgkQot4jUGLa M/oBQQ/8CWzUI5BRlyNiFnt0iP49zqpeqEDtNNa/dwgtiWmIoy7na5L1lUAPTFss vNjwi88CQ5Vq3IxG9GnQ02t0vC9cMulDZ6m+MUajUB5+9Iq8jXexY6KvXAZBaikM 4Stdrikaen3XtriU3lRnXoA3d6z9lQHDRz6vt4WVjInAgwkNUJlETn2GOE0//gvS X1KsAQnIDTZAbMognPdx2zC6lJeIcJLXFlxnPRNj9j2jH522kTmxQSopUNvhFdLz Mdr33lweCy7wv5B29218AZOk+pviWgknbpX3JsMwTCrW581O6C23m/QcC109g6fH XbEfMOnlkbhlPQWpYUSnW49LP1dhX4evHuin5eNXlnN44CjJFyAweKQCzIThX74m ZUbeveUCoTNMPDmghFMbb5DoF1FPfPzIdNtQFppAJUf0QXZom0kOHTcahICL+3++ 1zPXvlBEt5fHqS4unblc2TPte/xn8ud+Dn5rEv1xxvsPuLhwSi3I38OUvXHZdNPg nceXqzXVOrOSmhVxyg5s0ntx2ixuYYGpTFJSUeW8SDDrltObkdoNc2E2wzmfA53s uwfBwqyj+NXfqztjp5WPLqqkQgTzR3vWulsYD3CClzO1UGaN0wz/bL0FWKwgzkLS 0ogx47FjJS0OCSzhEN6JriAao7rjBDroHdAKRD8YN7UdVuOvBmY= =2eXg -END PGP SIGNATURE End Message ---
Bug#862883: Port from libnm-glib/libnm-util to libnm
On Sat, 14 Apr 2018 21:32:30 +0200 Michael Biebl wrote: > Am 14.04.2018 um 15:21 schrieb Michael Biebl: > > > I tried updating solid-networkstartus to use QT_NO_KEYWORDS and the Q_ > > macros, but ran into a problem. The QNtrack headers use the slots > > keyword, so if I set -DQT_NO_KEYWORDS, > > solid-networkstatus/kded/ntracknetworkstate.cpp fails to compile. > > > > So while I could get the networkmanager backend compile successfully > > with the attached patch, I had to disable QNtrack support. > > I found a way to avoid that situation. > As networkmanagerstatus.cpp only uses the D-Bus interface, using > #include > instead of > #include > was sufficient and it avoids that gio related headers are included, so > -DQT_NO_KEYWORDS is not necessary. > > Lubo, as NM upstream, wdyt about using nm-dbus-interface.h directly > instead of the include-all NetworkManager.h? > > v2 of the patch is attached. Thomas Haller just confirmed on IRC that using nm-dbus-interface.h directly is fine and it was actually designed that way that it can be used from Qt without dragging in any gio dependencies. I guess that means v2 of my patch is the better approach, as it avoids having to rewrite the code to accomodate the use of -DQT_NO_KEYWORDS. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Processed: bug 862877 is forwarded to https://bugs.kde.org/show_bug.cgi?id=393255
Processing commands for cont...@bugs.debian.org: > forwarded 862877 https://bugs.kde.org/show_bug.cgi?id=393255 Bug #862877 [src:kdelibs4support] Port from libnm-glib/libnm-util to libnm Set Bug forwarded-to-address to 'https://bugs.kde.org/show_bug.cgi?id=393255'. > thanks Stopping processing here. Please contact me if you need assistance. -- 862877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862877 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#895882: sphinx: version 1.7.2-1 causes regression in sphinxcontrib-bibtex (Unknown node: bibliography)
Control: reassign -1 python3-sphinxcontrib.bibtex 0.3.6-2 Control: forwarded -1 https://github.com/mcmtroffaes/sphinxcontrib-bibtex/pull/136 Control: affects -1 - src:sphinxcontrib-bibtex On Tue, Apr 17, 2018 at 09:56:49AM +0200, Paul Gevers wrote: > Since the upload of sphinx version 1.7.2-1, the autopkgtest of > sphinxcontrib-bibtex¹ fails with the errors copied below. > > As all the failures (25 failures/28 tests) really come from the same > issue (NotImplementedError: Unknown node: bibliography), the ratio > between passes and failures is so high, and the missing node name > suggests core functionality for sphinxcontrib-bibtex I file this bug > with severity *serious* against sphinx. If you believe this was > exaggerated or the issue is really in sphinxcontrib-bibtex, please don't > hesitate to lower it accordingly and/or reassign to sphinxcontrib-bibtex. Yes, it is a bug in sphinxcontrib-bibtex, it no longer applies its transform for all tests except the first one. I have submitted a pull request upstream which has a fix for this issue. -- Dmitry Shachnev signature.asc Description: PGP signature
Processed: Re: Bug#895882: sphinx: version 1.7.2-1 causes regression in sphinxcontrib-bibtex (Unknown node: bibliography)
Processing control commands: > reassign -1 python3-sphinxcontrib.bibtex 0.3.6-2 Bug #895882 [src:sphinx] sphinx: version 1.7.2-1 causes regression in sphinxcontrib-bibtex (Unknown node: bibliography) Bug reassigned from package 'src:sphinx' to 'python3-sphinxcontrib.bibtex'. No longer marked as found in versions sphinx/1.7.2-1. Ignoring request to alter fixed versions of bug #895882 to the same values previously set Bug #895882 [python3-sphinxcontrib.bibtex] sphinx: version 1.7.2-1 causes regression in sphinxcontrib-bibtex (Unknown node: bibliography) Marked as found in versions sphinxcontrib-bibtex/0.3.6-2. > forwarded -1 https://github.com/mcmtroffaes/sphinxcontrib-bibtex/pull/136 Bug #895882 [python3-sphinxcontrib.bibtex] sphinx: version 1.7.2-1 causes regression in sphinxcontrib-bibtex (Unknown node: bibliography) Set Bug forwarded-to-address to 'https://github.com/mcmtroffaes/sphinxcontrib-bibtex/pull/136'. > affects -1 - src:sphinxcontrib-bibtex Bug #895882 [python3-sphinxcontrib.bibtex] sphinx: version 1.7.2-1 causes regression in sphinxcontrib-bibtex (Unknown node: bibliography) Removed indication that 895882 affects src:sphinxcontrib-bibtex -- 895882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895882 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#895980: zathura: symbol lookup error: zathura: undefined symbol: synctex_next_result
On 2018-04-18 12:45:02, Sebastian Ramacher wrote: > Control: reassign -1 libsynctex1 2018.20180416.47457-1 > Control: severity -1 serious > Control: retitle -1 libsynctex1: drops public symbols without SONAME bump > Control: affects -1 zathura > > On 2018-04-18 10:18:12, Giuseppe Bilotta wrote: > > Package: zathura > > Version: 0.3.9-1 > > Severity: normal > > > > This error has appeared after an upgrade of the texlive system, which > > includes > > a new libsynctex1. Probably zathura needs to be rebuilt against the latest > > libsynctex > > No, libsynctex1 broke its API and ABI and needs to perform a proper transition > including a SONAME bump. FWIW, synctex_result_next was a public symbol in > 2017.20170613.44572, but was removed in 2018.20180416.47457. Many other > symbols > also affected by this change. Additionally, synctex-version.h seems to be missing from the -dev package: /usr/include/synctex/synctex_parser.h:53:10: fatal error: synctex_version.h: No such file or directory #include "synctex_version.h" ^~~ compilation terminated. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#895998: galleta does not trap compilation errors
Source: galleta Version: 1.0+20040505-8 Severity: serious Justification: policy 4.6 Tags: upstream User: helm...@debian.org Usertags: rebootstrap galleta's upstream build system does not trap errors from gcc as it chains multiple commands with ";". Doing so is required by policy section 4.6 to avoid producing misbuilds. The typical solutions include: * Chaining commands with && rather than ; * Adding set -e Helmut
Bug#895997: mysql-5.7: Security fixes from the April 2018 CPU
Source: mysql-5.7 Version: 5.7.21-1 Severity: grave Tags: security upstream Hi Detail at http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html#AppendixMSQL Regards, Salvatore
Bug#893690: marked as done (dogtag-pki: CVE-2018-1080: Mishandled ACL configuration in AAclAuthz.java reverses rules that allow and deny access)
Your message dated Wed, 18 Apr 2018 12:19:41 + with message-id and subject line Bug#893690: fixed in dogtag-pki 10.6.0-2 has caused the Debian Bug report #893690, regarding dogtag-pki: CVE-2018-1080: Mishandled ACL configuration in AAclAuthz.java reverses rules that allow and deny access 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.) -- 893690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893690 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dogtag-pki Version: 10.5.5-1 Severity: grave Tags: security upstream Forwarded: https://pagure.io/freeipa/issue/7453 Hi, the following vulnerability was published for dogtag-pki. CVE-2018-1080[0]: Mishandled ACL configuration in AAclAuthz.java reverses rules that allow and deny access 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-1080 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1080 [1] https://pagure.io/freeipa/issue/7453 [2] https://review.gerrithub.io/#/c/404435/ Regards, Salvatore --- End Message --- --- Begin Message --- Source: dogtag-pki Source-Version: 10.6.0-2 We believe that the bug you reported is fixed in the latest version of dogtag-pki, 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. Timo Aaltonen (supplier of updated dogtag-pki package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 18 Apr 2018 15:07:20 +0300 Source: dogtag-pki Binary: dogtag-pki pki-base pki-base-java python3-pki-base pki-tools pki-server pki-ca dogtag-pki-console-theme dogtag-pki-server-theme pki-console pki-kra pki-ocsp pki-tks pki-tps pki-tps-client pki-javadoc libsymkey-java libsymkey-jni Architecture: source Version: 10.6.0-2 Distribution: experimental Urgency: medium Maintainer: Debian FreeIPA Team Changed-By: Timo Aaltonen Description: dogtag-pki - Dogtag Public Key Infrastructure (PKI) Suite dogtag-pki-console-theme - Certificate System - PKI Console User Interface dogtag-pki-server-theme - Certificate System - PKI Server User Interface libsymkey-java - Symmetric Key Java library libsymkey-jni - Symmetric Key JNI Library pki-base - Certificate System - PKI Framework pki-base-java - Certificate System - PKI Framework -- java client support pki-ca - Certificate System - Certificate Authority pki-console - Certificate System - PKI Console pki-javadoc - Certificate System - PKI Framework Javadocs pki-kra- Certificate System - Data Recovery Manager pki-ocsp - Certificate System - Online Certificate Status Protocol Manager pki-server - Certificate System - PKI Server Framework pki-tks- Certificate System - Token Key Service pki-tools - Certificate System - PKI Tools pki-tps- Certificate System - Token Processing System pki-tps-client - Certificate System - Token Processing System client python3-pki-base - Certificate System - PKI Framework -- python3 client support Closes: 893690 Changes: dogtag-pki (10.6.0-2) experimental; urgency=medium . * rules: Build everything in one pass. * Fix ACL evaluation in allow,deny mode. (Closes: #893690) - CVE-2018-1080 Checksums-Sha1: 6ccbb5d35c52f92a2a9910c2c0705f02492447b3 3709 dogtag-pki_10.6.0-2.dsc a211a46e56ae28d3e9cf407c694ace203c4c6feb 32584 dogtag-pki_10.6.0-2.debian.tar.xz 3688da8ee57f57ebbb09eec3eb323f94d869f09a 17932 dogtag-pki_10.6.0-2_source.buildinfo Checksums-Sha256: 6bd3401e9afaebc8369e2c50dc3ade4c7c060f2a22134730d9230abd559b7f0e 3709 dogtag-pki_10.6.0-2.dsc 54fe3534494dd22c7dd23ede490a49515a4d3ce0a238d71cc24ac424e3e30083 32584 dogtag-pki_10.6.0-2.debian.tar.xz d7e902752d2944fdda262051999618090c347af8bf699028b6ffce4fba53325c 17932 dogtag-pki_10.6.0-2_source.buildinfo Files: 09597b27529fd80763ad92966a99ca1f 3709 java optional dogtag-pki_10.6.0-2.dsc 3f193ab6d0ea88446943370304e03efc 32584 java optional dogtag-pki_10.6.0-2.debian.tar.xz aa9dcf4900bcd484ab8a76b2ff4ab310 17932 java optional
Bug#895990: gdm3: memory leak (known upstream)
Package: gdm3 Version: 3.22.3-3+deb9u1 Severity: critical Tags: upstream Justification: breaks the whole system Dear Maintainer, the gdm3 process has a memory leak which continuously consumes more and more memory until the OOM killer renders the system unusable. Therefore, this bug was tagged as critical. Up to 10 GB memory usage of gdm3 were observered until we killed the process to prevent further problems. From our 59 identical systems, 3 suffered from this leak in the past days. This bug is known upstream, see https://bugs.launchpad.net/gnome-shell/+bug/1672297 Comment 66 of the above bug report includes fixes for the upstream packages. Please backport them to Debian stable. Kind regards Dennis Grunert -- System Information: Debian Release: 9.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-6-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gdm3 depends on: ii accountsservice 0.6.43-1 ii adduser 3.115 ii cinnamon [x-window-manager] 3.2.7-4 ii cinnamon-session [x-session-manager] 3.2.0-4 ii dconf-cli 0.26.0-2+b1 ii dconf-gsettings-backend 0.26.0-2+b1 ii debconf [debconf-2.0] 1.5.61 ii gir1.2-gdm-1.03.22.3-3+deb9u1 ii gnome-session [x-session-manager] 3.22.3-1 ii gnome-session-bin 3.22.3-1 ii gnome-settings-daemon 3.22.2-2+deb9u2 ii gnome-shell 3.22.3-3 ii gnome-terminal [x-terminal-emulator] 3.22.2-1 ii gsettings-desktop-schemas 3.22.0-1 ii i3-wm [x-window-manager] 4.13-1 ii konsole [x-terminal-emulator] 4:16.12.0-4 ii kwin-x11 [x-window-manager] 4:5.8.6-1 ii libaccountsservice0 0.6.43-1 ii libaudit1 1:2.6.7-2 ii libc6 2.24-11+deb9u3 ii libcanberra-gtk3-00.30-3 ii libcanberra0 0.30-3 ii libgdk-pixbuf2.0-02.36.5-2+deb9u2 ii libgdm1 3.22.3-3+deb9u1 ii libglib2.0-0 2.50.3-2 ii libglib2.0-bin2.50.3-2 ii libgtk-3-03.22.11-1 ii libkeyutils1 1.5.9-9 ii libpam-modules1.1.8-3.6 ii libpam-runtime1.1.8-3.6 ii libpam-systemd232-25+deb9u3 ii libpam0g 1.1.8-3.6 ii librsvg2-common 2.40.16-1+b1 ii libselinux1 2.6-3+b3 ii libsystemd0 232-25+deb9u3 ii libwrap0 7.6.q-26 ii libx11-6 2:1.6.4-3 ii libxau6 1:1.0.8-1 ii libxcb1 1.12-1 ii libxdmcp6 1:1.1.2-3 ii lsb-base 9.20161125 ii lxsession [x-session-manager] 0.5.3-2 ii lxterminal [x-terminal-emulator] 0.3.0-2 ii muffin [x-window-manager] 3.2.1-2 ii mutter [x-window-manager] 3.22.3-2 ii openbox [x-window-manager]3.6.1-4 ii openbox-lxde-session [x-session-manager] 0.99.2-3 ii plasma-workspace [x-session-manager] 4:5.8.6-2.1+deb9u1 ii policykit-1 0.105-18 ii ucf 3.0036 ii x11-common1:7.7+19 ii x11-xserver-utils 7.7+7+b1 ii xfce4-session [x-session-manager] 4.12.1-5 ii xfce4-terminal [x-terminal-emulator] 0.8.3-1 ii xfwm4 [x-window-manager] 4.12.4-1 ii xterm [x-terminal-emulator] 327-2 Versions of packages gdm3 recommends: ii at-spi2-core2.22.0-6+deb9u1 ii desktop-base9.0.2+deb9u1 ii x11-xkb-utils 7.7+3+b1 pn xserver-xephyr ii xserver-xorg1:7.7+19 ii zenity 3.22.0-1+b1 Versions of packages gdm3 suggests: pn gnome-orca ii libpam-gnome-keyring 3.20.0-3 -- debconf-show failed
Bug#895371: ejabberd: conffile edited using ucf
Excerpts from Philipp Huebner's message of april 16, 2018 9:38 am:
On Tue, 10 Apr 2018 19:39:14 +0200 Jonas Smedegaard
wrote:
The file /etc/default/ejabberd is registered as a conffile, but is
also manipulated using ucf in postinst script. That is illegal,
according to Policy § 10.7.3
thanks for pointing this out!
However, this is rather unfortunate, the current setup has been well
tested and in use for ages.
Do you have an idea on how to achieve this in a policy-conform way?
Not touching ejabberd.yml would mean to remove the debconf templates
for configuring ejabberd, not declaring ejabberd.yml a conffile would
mean putting in some extra effort for handling changes. Are
non-conffiles even allowed in /etc ?
Debian Policy distinguishes between "configuration file" and "conffile"
and describes, particular at §10.7.3, how to handle either. I believe
the first step is to *not* ship the configuration file below /etc if it
should not be a conffile ("man dh_installdeb" documents how any file
below /etc shipped with a package is registered as a conffile).
"man ucf" contains some documentation on transitioning from conffile to
non-conffile. I believe that involves collecting md5sums of most
possible previous pristine states (i.e. configfile as shipped unedited
with the package) as possible.
Hope that helps,
- Jonas
--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
pgpuO1dAJFvFL.pgp
Description: PGP signature
Bug#893664: marked as done (sambamba: Fails to build on i386)
Your message dated Wed, 18 Apr 2018 10:52:13 + with message-id and subject line Bug#893664: fixed in sambamba 0.6.7-2 has caused the Debian Bug report #893664, regarding sambamba: Fails to build on i386 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.) -- 893664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893664 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sambamba Version: 0.6.7-1 Severity: serious sambamba fails to build from source on i386: https://buildd.debian.org/status/package.php?p=sambamba Thanks, Jeremy Bicha --- End Message --- --- Begin Message --- Source: sambamba Source-Version: 0.6.7-2 We believe that the bug you reported is fixed in the latest version of sambamba, 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. Gianfranco Costamagna (supplier of updated sambamba 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: Wed, 18 Apr 2018 12:10:12 +0200 Source: sambamba Binary: sambamba Architecture: source Version: 0.6.7-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Gianfranco Costamagna Description: sambamba - tools for working with SAM/BAM data Closes: 893664 Changes: sambamba (0.6.7-2) unstable; urgency=medium . * Team upload. * Disable assert on i386, this is a new assert, but the current package is already broken on i386. Upstream is working on a proper fix, in the meantime we can let the package migrate without removing i386 or making things worse for this architecture. Closes: #893664 See: https://github.com/biod/sambamba/issues/344 (and issue 300) . [ Steffen Möller ] * Update upstream metadata file . [ Matthias Klumpp ] * Fail on missing files * Do not force disable of neon on armhf in rules file, already handled by dh-dlang Checksums-Sha1: e7e7dc18769b4daffd0dff328f445accea282ce6 2036 sambamba_0.6.7-2.dsc 31e66b56ce5abce680ac7e519958bda78b8927ba 3772 sambamba_0.6.7-2.debian.tar.xz dbf71dc5731ad4474d53664ad9558105317074a5 5837 sambamba_0.6.7-2_source.buildinfo Checksums-Sha256: 6b930e61c3f400edd2fb2d26fc87cbd9c8544a4fb1656ca58cefe88d62443db8 2036 sambamba_0.6.7-2.dsc 4827785096a93a4afe72d4c4c6000c221f2d8ef8fe4254899fe8da7489711b0a 3772 sambamba_0.6.7-2.debian.tar.xz 3b254a41144add3763cf4e9cc1a291aeda148ea499aeea2ded04da656e3dfa40 5837 sambamba_0.6.7-2_source.buildinfo Files: 5b7ae02f6ebe2991f688680045d582d4 2036 science optional sambamba_0.6.7-2.dsc 0edee3385ceef1714669f87e7dc5cb7b 3772 science optional sambamba_0.6.7-2.debian.tar.xz 000b64283560c7dfadc67d78f13d0c50 5837 science optional sambamba_0.6.7-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJa1yCUAAoJEPNPCXROn13ZzJQP/1ua94sblhheoAcL0cANwU/4 98IzKWEALFPNluOyF4Sk8c+XoWgY39pdDp7aJBLBlDS7jZOV+vr1cecLTCeUL5jL Z4IICiAvy7aHiVyoq+gar4Yixy+vT9rAgIpwpgZaueLNNzUDvnDubWqOAxM93nTQ vgXXOJRa2QKvdxvny/72m253dxoVg9o2a5rSNKwPhvdIDK0d5GZTqaE2GAsn8Dn9 2eXCRvmGDhBfp88B3QmLfvDIhDu4ja5MYtuiIFPkNXHFyb/3P0j2A+izHtXxb0xp cR7f7fLZeNnnq+UYApL8MmZiSbB2UkWlKyldORSjz6hj1WI/eMp0krtQyG5/0eFK I+7DeXd+W9l7RJ4R68CtvmP8aeUlq++J1vQ7d+c+Z+KhwAnV7+8KrAZczNdTyWso SeGOS6FTxt8LmCy5/0MsBFb1eGozjAqimniJZ6EgxntCXNLx6tfTyfpYr+WLMC9z cNhlZjIX1u1wc01CuR2ZUFi7Vg+8vP5qVKqqw3EAKvlAi58+7KLRTrw7qfiI0M+v ATDswFm192br97Alg3mrM46h+l0ypeNZXq99sEb2H1x3+Mb8P80FNsKS/qNe3Xya Lset+J/9w6qlgQfxb4dFxYgzVD4e9zS1hVS1wV50N274DTx7d2xJbVpcsGD88Fif aqj1Qk5WLBupApM54z2i =VC0I -END PGP SIGNATURE End Message ---
Processed: Re: Bug#895980: zathura: symbol lookup error: zathura: undefined symbol: synctex_next_result
Processing control commands: > reassign -1 libsynctex1 2018.20180416.47457-1 Bug #895980 [zathura] zathura: symbol lookup error: zathura: undefined symbol: synctex_next_result Bug reassigned from package 'zathura' to 'libsynctex1'. No longer marked as found in versions zathura/0.3.9-1. Ignoring request to alter fixed versions of bug #895980 to the same values previously set Bug #895980 [libsynctex1] zathura: symbol lookup error: zathura: undefined symbol: synctex_next_result Marked as found in versions texlive-bin/2018.20180416.47457-1. > severity -1 serious Bug #895980 [libsynctex1] zathura: symbol lookup error: zathura: undefined symbol: synctex_next_result Severity set to 'serious' from 'normal' > retitle -1 libsynctex1: drops public symbols without SONAME bump Bug #895980 [libsynctex1] zathura: symbol lookup error: zathura: undefined symbol: synctex_next_result Changed Bug title to 'libsynctex1: drops public symbols without SONAME bump' from 'zathura: symbol lookup error: zathura: undefined symbol: synctex_next_result'. > affects -1 zathura Bug #895980 [libsynctex1] libsynctex1: drops public symbols without SONAME bump Added indication that 895980 affects zathura -- 895980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895980 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#895986: sbt-test-interface: FTBFS with java 9: object java.lang.Object in compiler mirror not found
Source: sbt-test-interface Version: 1.0-1 Severity: serious Justification: fails to build from source Hi, sbt-test-interface FTBFS since the default jdk was switched to openjdk-9: debian/rules build dh build --with javahelper --with maven_repo_helper dh_update_autotools_config jh_linkjars debian/rules override_dh_auto_build make[1]: Entering directory '/build/sbt-test-interface-1.0' mkdir -p /build/sbt-test-interface-1.0/debian/sbt_home/.ivy2/cache cp -fr /build/sbt-test-interface-1.0/bootstrapdeps/* /build/sbt-test-interface-1.0/debian/sbt_home/.ivy2/cache/ mkdir /build/sbt-test-interface-1.0/debian/sbt_home/.sbt echo "[repositories]" > /build/sbt-test-interface-1.0/debian/sbt_home/.sbt/repositories echo "local" >> /build/sbt-test-interface-1.0/debian/sbt_home/.sbt/repositories /build/sbt-test-interface-1.0/bootstrapsbt/bin/sbt -verbose -debug -sbt-dir /build/sbt-test-interface-1.0/debian/sbt_home/.sbt -ivy /build/sbt-test-interface-1.0/debian/sbt_home/.ivy2 'set offline := true' -Dsbt.o verride.build.repos=true packageBin make-pom [residual] arg = '-sbt-dir' [residual] arg = '/build/sbt-test-interface-1.0/debian/sbt_home/.sbt' [addJava] arg = '-Dsbt.ivy.home=/build/sbt-test-interface-1.0/debian/sbt_home/.ivy2' [residual] arg = 'set offline := true' [addJava] arg = '-Dsbt.override.build.repos=true' [residual] arg = 'packageBin' [residual] arg = 'make-pom' [addJava] arg = '-Dsbt.global.base=/build/sbt-test-interface-1.0/debian/sbt_home/.sbt' [residual] arg = 'set offline := true' [residual] arg = 'packageBin' [residual] arg = 'make-pom' [process_args] java_version = '9.0.4' # Executing command line: java -Xms1024m -Xmx1024m -XX:ReservedCodeCacheSize=128m -XX:MaxMetaspaceSize=256m -Dsbt.ivy.home=/build/sbt-test-interface-1.0/debian/sbt_home/.ivy2 -Dsbt.override.build.repos=true -Dsbt.global.base=/build/sbt-test-interface-1.0/debian/sbt_home/.sbt -jar /build/sbt-test-interface-1.0/bootstrapsbt/bin/sbt-launch.jar "set offline := true" packageBin make-pom Getting org.scala-sbt sbt 0.13.12 ... :: retrieving :: org.scala-sbt#boot-app confs: [default] 49 artifacts copied, 0 already retrieved (17462kB/111ms) Getting Scala 2.10.6 (for sbt)... :: retrieving :: org.scala-sbt#boot-scala confs: [default] 5 artifacts copied, 0 already retrieved (24494kB/42ms) error: error while loading package, Missing dependency 'object java.lang.Object in compiler mirror', required by /build/sbt-test-interface-1.0/debian/sbt_home/.sbt/boot/scala-2.10.6/lib/scala-library.jar(scala/package.class) error: error while loading package, Missing dependency 'object java.lang.Object in compiler mirror', required by /build/sbt-test-interface-1.0/debian/sbt_home/.sbt/boot/scala-2.10.6/lib/scala-library.jar(scala/runtime/package.class) scala.reflect.internal.MissingRequirementError: object java.lang.Object in compiler mirror not found. at scala.reflect.internal.MissingRequirementError$.signal(MissingRequirementError.scala:16) at scala.reflect.internal.MissingRequirementError$.notFound(MissingRequirementError.scala:17) at scala.reflect.internal.Mirrors$RootsBase.getModuleOrClass(Mirrors.scala:48) at scala.reflect.internal.Mirrors$RootsBase.getModuleOrClass(Mirrors.scala:40) at scala.reflect.internal.Mirrors$RootsBase.getModuleOrClass(Mirrors.scala:40) at scala.reflect.internal.Mirrors$RootsBase.getModuleOrClass(Mirrors.scala:61) at scala.reflect.internal.Mirrors$RootsBase.getClassByName(Mirrors.scala:99) at scala.reflect.internal.Mirrors$RootsBase.getRequiredClass(Mirrors.scala:102) at scala.reflect.internal.Definitions$DefinitionsClass.ObjectClass$lzycompute(Definitions.scala:264) at scala.reflect.internal.Definitions$DefinitionsClass.ObjectClass(Definitions.scala:264) at scala.reflect.internal.Definitions$DefinitionsClass.AnyRefClass$lzycompute(Definitions.scala:263) at scala.reflect.internal.Definitions$DefinitionsClass.AnyRefClass(Definitions.scala:263) at scala.reflect.internal.Definitions$DefinitionsClass.specialPolyClass(Definitions.scala:1120) at scala.reflect.internal.Definitions$DefinitionsClass.RepeatedParamClass$lzycompute(Definitions.scala:407) at scala.reflect.internal.Definitions$DefinitionsClass.RepeatedParamClass(Definitions.scala:407) at scala.reflect.internal.Definitions$DefinitionsClass.syntheticCoreClasses$lzycompute(Definitions.scala:1154) at scala.reflect.internal.Definitions$DefinitionsClass.syntheticCoreClasses(Definitions.scala:1152) at scala.reflect.internal.Definitions$DefinitionsClass.symbolsNotPresentInBytecode$lzycompute(Definitions.scala:1196) at scala.reflect.internal.Definitions$DefinitionsClass.symbolsNotPresentInBytecode(Definitions.scala:1196) at scala.reflect.internal.Definitions$DefinitionsClass.init(Definitions.scala:1261) at scala.tools.nsc.Global$Run.(Global.scala:1
Bug#895718: marked as done (python-pyqt5: import PyQt5.QtCore fails)
Your message dated Wed, 18 Apr 2018 12:48:27 +0300 with message-id <20180418094827.ga10...@mitya57.me> and subject line Re: Bug#895718: python-pyqt5: import PyQt5.QtCore fails has caused the Debian Bug report #895718, regarding python-pyqt5: import PyQt5.QtCore fails 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.) -- 895718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895718 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-pyqt5 Version: 5.9.2+dfsg-1 Severity: grave Justification: renders package unusable Tried this on sid with both pyqt5 5.9.2 and 5.10.1: Unpacking python-pyqt5 (5.10.1+dfsg-1) over (5.9.2+dfsg-1+b1) ... Setting up python-pyqt5 (5.10.1+dfsg-1) ... # python Python 2.7.14+ (default, Apr 2 2018, 04:16:25) [GCC 7.3.0] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import PyQt5.QtCore Traceback (most recent call last): File "", line 1, in ImportError: libQt5Core.so.5: cannot open shared object file: No such file or directory >>> I checked and libQt5Core.so.5 is installed at the expected location: # ls -l /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 lrwxrwxrwx 1 root root 20 Apr 7 19:35 /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 -> libQt5Core.so.5.10.1 # ls -l /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.1 -rw-r--r-- 1 root root 5224752 Apr 7 19:35 /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.1 The same thing happenson python3 too: Python 3.6.5 (default, Apr 1 2018, 05:46:30) [GCC 7.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import PyQt5.QtCore Traceback (most recent call last): File "", line 1, in ImportError: libQt5Core.so.5: cannot open shared object file: No such file or directory Scott K --- End Message --- --- Begin Message --- On Sun, Apr 15, 2018 at 01:26:50PM +0300, Dmitry Shachnev wrote: > Works for me in a clean sid chroot. The CI tests for pyqt5 are also passing [1], so I am closing this bug. [1]: https://ci.debian.net/packages/p/pyqt5/unstable/amd64/ -- Dmitry Shachnev signature.asc Description: PGP signature --- End Message ---
Bug#889530: acm FTBFS with gdbm 1.14.1-2
On Wed, 18 Apr 2018, Markus Koschany wrote: I've uploaded a new revision of acm versioned as 5.0-29.2 to fix Debian bug #889530. […] Thank you, Markus. That's much appreciated. Cheers, Phil.
Bug#895971: marked as done (virtualbox-ext-pack: Unroutable maintainer address)
Your message dated Wed, 18 Apr 2018 09:35:29 + with message-id and subject line Bug#895971: fixed in virtualbox-ext-pack 5.2.10-2 has caused the Debian Bug report #895971, regarding virtualbox-ext-pack: Unroutable maintainer address 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.) -- 895971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: virtualbox-ext-pack Version: 5.2.10-1 Severity: serious Justification: Policy 3.3 Dear Maintainer, After a recent upload, the FTP team received this error: This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: pkg-virtualbox-de...@lists.alioth.debian.org host alioth-lists-mx.debian.net [2001:ba8:0:2c77:0:4:0:1] SMTP error from remote mail server after RCPT TO:: 550 Unrouteable address Policy 3.3 requires a working email address for the package maintainer. This may be an issue with the recent migration of alioth lists to a new host. Scott K --- End Message --- --- Begin Message --- Source: virtualbox-ext-pack Source-Version: 5.2.10-2 We believe that the bug you reported is fixed in the latest version of virtualbox-ext-pack, 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 895...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gianfranco Costamagna (supplier of updated virtualbox-ext-pack 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: Wed, 18 Apr 2018 11:16:47 +0200 Source: virtualbox-ext-pack Binary: virtualbox-ext-pack Architecture: source Version: 5.2.10-2 Distribution: unstable Urgency: medium Maintainer: Debian Virtualbox Team Changed-By: Gianfranco Costamagna Description: virtualbox-ext-pack - extra capabilities for VirtualBox, downloader. Closes: 895971 Changes: virtualbox-ext-pack (5.2.10-2) unstable; urgency=medium . * Update maintainer field to the new dispatcher (Closes: #895971) Checksums-Sha1: a50a7060869282e548444061caaba8df535f07ed 2092 virtualbox-ext-pack_5.2.10-2.dsc 2d14839e1e3772d75b478453ba0bd43da2f8923f 12948 virtualbox-ext-pack_5.2.10-2.debian.tar.xz f8e5e396ea6077c4ceecde91010215c8ce51697e 5988 virtualbox-ext-pack_5.2.10-2_source.buildinfo Checksums-Sha256: fd2118cf917de90fd1bb6ef49b4e34726d1dd8f2e6f8cf723cdac633ed28c27f 2092 virtualbox-ext-pack_5.2.10-2.dsc 56cea77e5aa001cc467f3b30bfa120e462fccd2622214039fc9d10d52587aae0 12948 virtualbox-ext-pack_5.2.10-2.debian.tar.xz fd1abeccb9c538cd76b516fe235172dd89432287e098327b9f6e42740439d0c3 5988 virtualbox-ext-pack_5.2.10-2_source.buildinfo Files: 3c2da60830e43f72cc00d8be2524fe34 2092 contrib/misc optional virtualbox-ext-pack_5.2.10-2.dsc 41de6ae1fcf78c30d55efdc71eed0ec8 12948 contrib/misc optional virtualbox-ext-pack_5.2.10-2.debian.tar.xz ed45e6a9fbc521092b24fdcba3c93791 5988 contrib/misc optional virtualbox-ext-pack_5.2.10-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJa1w07AAoJEPNPCXROn13Zs7kP/RQq7f6qiFzVQfosuuU2R2UE 6vO97p79EzQ+OejxD2JpHo5bsKV7LeR61NrSIfWY6/ioU8ndRpJFsE+6LpMa0MDY fTG4Es+ktDjJQwme6o2tPpoQyydp0dxwEbyzp4ZnKJn9Wusoo5yvkzvcoRrx50Am qB8iW5ce/hah/W4dz7FPPkpHCIxA4rg6QztoBlOl5TbNul5ortTyhg4aT29pRb8r jQwK2Ze4R9bybNWUDlgmNy3eSkJiE3mAKlfrrFmm0T7hcRRWnZL/XJZuIQU7gDnY 7mSZLghXZnjwZJVKC47aotFZWYhydg9NF+l2Nm3kKpUzocba2wVgSHnbBi2pd1l2 BZMkbX4VZOk/thT3CxRw1nxrA+HpoW+sXsWtn3ayoIKBaYo5gYxb+GXlvdzAcuE4 +njRhciaxEmn4T6J2AtCIDI8gmhF7oz8+Rq3NoFZZYpzgjkNAalf/Rs0Dc8e/uIT Eqf1g/2Ut6uJq3OQyWMZrhdpkrlUVFpBfF17kwpd9qj5ESVVId07KVgvdDtuhg0r 2Ef2jMmFBqKCgYP569gzeFD/MZkZCb7BSzc8W3KUVCrMJojUEvWipElQTkRkt2M2 AeMIPuwW6fDTVf/1dLaT719rF02wEGRw4zLLfC+kRZcfJABy0B3mRjRYIUuR3ILb xqKOGOQVsDgwsIjIM15h =2BY0 -END PGP SIGNATURE End Message ---
Bug#895970: marked as done (virtualbox: Unroutable maintainer address)
Your message dated Wed, 18 Apr 2018 09:20:01 + with message-id and subject line Bug#895970: fixed in virtualbox 5.2.10-dfsg-2 has caused the Debian Bug report #895970, regarding virtualbox: Unroutable maintainer address 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.) -- 895970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895970 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: virtualbox Version: 5.2.10-dfsg-1 Severity: serious Justification: Policy 3.3 Dear Maintainer, After a recent upload, the FTP team received this error: This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: pkg-virtualbox-de...@lists.alioth.debian.org host alioth-lists-mx.debian.net [2001:ba8:0:2c77:0:4:0:1] SMTP error from remote mail server after RCPT TO:: 550 Unrouteable address Policy 3.3 requires a working email address for the package maintainer. This may be an issue with the recent migration of alioth lists to a new host. Scott K --- End Message --- --- Begin Message --- Source: virtualbox Source-Version: 5.2.10-dfsg-2 We believe that the bug you reported is fixed in the latest version of virtualbox, 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 895...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gianfranco Costamagna (supplier of updated virtualbox 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: Wed, 18 Apr 2018 11:02:56 +0200 Source: virtualbox Binary: virtualbox-qt virtualbox virtualbox-dkms virtualbox-source virtualbox-guest-dkms virtualbox-guest-source virtualbox-guest-x11 virtualbox-guest-utils Architecture: source Version: 5.2.10-dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Virtualbox Team Changed-By: Gianfranco Costamagna Description: virtualbox - x86 virtualization solution - base binaries virtualbox-dkms - x86 virtualization solution - kernel module sources for dkms virtualbox-guest-dkms - x86 virtualization solution - guest addition module source for dk virtualbox-guest-source - x86 virtualization solution - guest addition module source virtualbox-guest-utils - x86 virtualization solution - non-X11 guest utilities virtualbox-guest-x11 - x86 virtualization solution - X11 guest utilities virtualbox-qt - x86 virtualization solution - Qt based user interface virtualbox-source - x86 virtualization solution - kernel module source Closes: 895970 Changes: virtualbox (5.2.10-dfsg-2) unstable; urgency=medium . * Alioth list is dead, move to new list. (Closes: #895970) Checksums-Sha1: e8e36cb192c570f3e5aa54704cdadeeef945a164 3591 virtualbox_5.2.10-dfsg-2.dsc 5e79630c5ee8dae32ff19e2fdb7b4640cabcc2b6 84092 virtualbox_5.2.10-dfsg-2.debian.tar.xz f752878c7dd33668a87c630807c717ffceb8a5a1 24325 virtualbox_5.2.10-dfsg-2_source.buildinfo Checksums-Sha256: 51e6459289b8770edb7db2e65c8e6bdaaa17a838de87403884c7ef42178af7b5 3591 virtualbox_5.2.10-dfsg-2.dsc bb8cf541277caa1eef876e92cbffdf530fc3c990fe90b5bd4ec290566604b5e8 84092 virtualbox_5.2.10-dfsg-2.debian.tar.xz 395be1d2caf9661bbd5e46274b6fab912054979be7736cf2bb81715a2d762476 24325 virtualbox_5.2.10-dfsg-2_source.buildinfo Files: ec38f33736e943b1d990cc6cce72d916 3591 contrib/misc optional virtualbox_5.2.10-dfsg-2.dsc cad1ae438749296ddcbfbd0e42891c6b 84092 contrib/misc optional virtualbox_5.2.10-dfsg-2.debian.tar.xz 3a0c5d2482c5a60adc6efd9e32de0a93 24325 contrib/misc optional virtualbox_5.2.10-dfsg-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJa1wvnAAoJEPNPCXROn13ZanwQANZZMoxtcKco11OqCKqxr+GK brq7E42gvJCt+71OI7mUr8sMEEATbfnv9fhPXMoCQn2h5uN8gQUgd1UrveTVmujq mnwjc3DVAQlCLJZEvIHOZf4JvFzfAYrZzQ7E7qV0/yGtX/XwlgiE0N0FyVKaT+QH mmpCYvo3VxPCWzw+FWQoVItGndMorTSETI84NU5QXVjjS5njB6Z6bhhlYuqLoZke gyCbDM8GBrbXJC6s/j4gzaTeSRom4eswSOUrELNNI77M+TdKkuTyBt98xlKpZKEV fX/FRedLf7PHTUXuk4zvFnVrW/y7TO9Ic7qVMN1pu0U8qE4wADVPDdn92t64tR7r cIbgi9qwVsznj4smAl+ztUuS3PLHNYp/LRn+dD1N2mm5yMD69dGh7YatyYeBLUJQ zy6LSbg4AZUZsVzNBwPyh0e7lHnK
Bug#895342: marked as done (suricata: new version fails to start if eth0 not present)
Your message dated Wed, 18 Apr 2018 11:07:32 +0200 with message-id and subject line suricata: new version fails to start if eth0 not present has caused the Debian Bug report #895342, regarding suricata: new version fails to start if eth0 not present 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.) -- 895342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895342 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: suricata Version: 1:4.0.4-1 Severity: serious User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu bionic autopkgtest Dear maintainers, The latest version of suricata is failing its autopkgtests in Ubuntu because the suricata daemon does not start in the test environment. This appears to be due to the fact that the default suricata config assumes eth0 as an interface name, but the testbed has ens2 as its default interface: # /usr/bin/suricata --af-packet -c /etc/suricata/suricata.yaml --pidfile /var/run/suricata.pid 10/4/2018 -- 05:31:56 - - This is Suricata version 4.0.4 RELEASE 10/4/2018 -- 05:31:56 - - [ERRCODE: SC_ERR_SYSCALL(50)] - Failure when trying to get MTU via ioctl for 'eth0': No such device (19) 10/4/2018 -- 05:31:56 - - [ERRCODE: SC_ERR_SYSCALL(50)] - Failure when trying to get MTU via ioctl for 'eth0': No such device (19) 10/4/2018 -- 05:31:56 - - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule files match the pattern /etc/suricata/rules/botcc.rules 10/4/2018 -- 05:31:56 - - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule files match the pattern /etc/suricata/rules/ciarmy.rules 10/4/2018 -- 05:31:56 - - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule files match the pattern /etc/suricata/rules/compromised.rules 10/4/2018 -- 05:31:56 - - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule files match the pattern /etc/suricata/rules/drop.rules 10/4/2018 -- 05:31:56 - - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule files match the pattern /etc/suricata/rules/dshield.rules 10/4/2018 -- 05:31:56 - - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule files match the pattern /etc/suricata/rules/emerging-attack_response.rules 10/4/2018 -- 05:31:56 - - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule files match the pattern /etc/suricata/rules/emerging-chat.rules 10/4/2018 -- 05:31:56 - - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule files match the pattern /etc/suricata/rules/emerging-current_events.rules 10/4/2018 -- 05:31:56 - - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule files match the pattern /etc/suricata/rules/emerging-dns.rules 10/4/2018 -- 05:31:56 - - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule files match the pattern /etc/suricata/rules/emerging-dos.rules 10/4/2018 -- 05:31:56 - - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule files match the pattern /etc/suricata/rules/emerging-exploit.rules 10/4/2018 -- 05:31:56 - - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule files match the pattern /etc/suricata/rules/emerging-ftp.rules 10/4/2018 -- 05:31:56 - - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule files match the pattern /etc/suricata/rules/emerging-imap.rules 10/4/2018 -- 05:31:56 - - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule files match the pattern /etc/suricata/rules/emerging-malware.rules 10/4/2018 -- 05:31:56 - - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule files match the pattern /etc/suricata/rules/emerging-misc.rules 10/4/2018 -- 05:31:56 - - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule files match the pattern /etc/suricata/rules/emerging-mobile_malware.rules 10/4/2018 -- 05:31:56 - - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule files match the pattern /etc/suricata/rules/emerging-netbios.rules 10/4/2018 -- 05:31:56 - - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule files match the pattern /etc/suricata/rules/emerging-p2p.rules 10/4/2018 -- 05:31:56 - - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule files match the pattern /etc/suricata/rules/emerging-policy.rules 10/4/2018 -- 05:31:56 - - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule files match the pattern /etc/suricata/rules/emerging-pop3.rules 10/4/2018 -- 05:31:56 - - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule files match the pattern /etc/suricata/rules/emerging-rpc.rules 10/4/2018 -- 05:31:56 - - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule files match the pattern /etc/suricata/rules/emerging-scan.rules 10/4/2018 -- 05:31:56 - - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule files match the pattern /etc/suricata/rules/emerging-smtp.rules 10/4/2018 -- 05:31:56 - - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule files match the pattern /etc/suricata/rules/emerging-snmp.rules 10/4/2018 -- 05:31:56 - - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule files match the
Bug#895342: suricata: new version fails to start if eth0 not present
If you check debian/tests/systemd-service-test.sh [0], the interface in use by the config file is decided at runtime. What autopkgtest tests are you running? This seem like an ubuntu specific issue. All tests in debian are going fine, both in unstable and in testing [1]. This Debian bug may result in the package being removed from Debian testing for no actual reason. Closing this bug now as it seems totally bogus. [0] https://salsa.debian.org/pkg-suricata-team/pkg-suricata/blob/master/debian/tests/systemd-service-test.sh [1] https://ci.debian.net/packages/s/suricata/
Bug#891025: marked as done (python-flask-login-doc: missing Breaks+Replaces: python3-flask-login-doc)
Your message dated Wed, 18 Apr 2018 08:50:40 + with message-id and subject line Bug#891025: fixed in flask-login 0.4.1-2 has caused the Debian Bug report #891025, regarding python-flask-login-doc: missing Breaks+Replaces: python3-flask-login-doc 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.) -- 891025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891025 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-flask-login-doc Version: 0.4.0-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package python-flask-login-doc. Preparing to unpack .../python-flask-login-doc_0.4.0-2_all.deb ... Unpacking python-flask-login-doc (0.4.0-2) ... dpkg: error processing archive /var/cache/apt/archives/python-flask-login-doc_0.4.0-2_all.deb (--unpack): trying to overwrite '/usr/share/doc-base/flask-login', which is also in package python3-flask-login-doc 0.4.0-1 Errors were encountered while processing: /var/cache/apt/archives/python-flask-login-doc_0.4.0-2_all.deb cheers, Andreas python3-flask-login-doc=0.4.0-1_python-flask-login-doc=0.4.0-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: flask-login Source-Version: 0.4.1-2 We believe that the bug you reported is fixed in the latest version of flask-login, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 891...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Berg (supplier of updated flask-login 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: Wed, 18 Apr 2018 09:35:46 +0200 Source: flask-login Binary: python3-flask-login python-flask-login-doc Architecture: source Version: 0.4.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Christoph Berg Description: python-flask-login-doc - user session management for Flask -- documentation python3-flask-login - user session management for Flask -- Python 3 module Closes: 891025 Changes: flask-login (0.4.1-2) unstable; urgency=medium . * Team upload. * Fix Breaks/Replaces of python3-flask-login-doc. Spotted by Andreas Beckmann, thanks! (Closes: #891025 again) * The doc package Enhances the module package instead of Suggests. Checksums-Sha1: b66905b3c763b01190095a6f67be6de7b6829450 2272 flask-login_0.4.1-2.dsc b3783f7ee0a41c120a180fcaaed9224dc3509349 5380 flask-login_0.4.1-2.debian.tar.xz 878acc36f3dd26c3d209e93591188d7cce863cba 6879 flask-login_0.4.1-2_source.buildinfo Checksums-Sha256: 947ad22393354713375139c9c1161265f012cb047a8cf6f23a84f50f4f4e0b44 2272 flask-login_0.4.1-2.dsc 6ee492a89b1e0a5f955f65dc3de9e713cbb2544b0075b251cc2703651dd4bcc3 5380 flask-login_0.4.1-2.debian.tar.xz abfec14086dd7cb796d7950426195aad7478d518e8aa456d3dd123ae45aa7fb7 6879 flask-login_0.4.1-2_source.buildinfo Files: 9d7d83196f67570516d2ee04eef09021 2272 python optional flask-login_0.4.1-2.dsc 8c8d0142ac3692c39cc35fb2bfca1102 5380 python optional flask-login_0.4.1-2.debian.tar.xz 1c02d28608d13a11d500c4d9ef0bf307 6879 python optional flask-login_0.4.1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAlrW9tsACgkQTFprqxLS p66Ung//Vl5VlQVUms3mCwiEuOdCyFwfotViWh9cigd+JL6Y4GkCR2VwGAG8SV3v HgXQz7ekLcu/k1LxHKhAIIhlVumNR2BSEJ8ktDbEy7RMKUEucqWc+P1muMdSSgGn Ano8CVq8qrqbvgm6Ian15QHE/7N0tUP6c2Cduk9+Z2hOo/Glz85U51rJo1xOO2th hePzqAArG4T2fm9uVNrsj+oXzs8j9Eb+rehvG1LaemJo+LpSTrvgSFf+kx5+dTcZ yBA3kIMcg0D/ZCleGySeUEGI4zgjCVZTMbGlT/pS/FrMFwA3ebNZTMDfjhxEYKWg l4dxoqDxQmS34ZEegfvs1ujmiRgytz2scN+3dP4Cilf/gjEuEE1LPmdFKTVkeVfT 7WPAypriH52bW5MEwwz/VU/NKTR6AL5t+XBfvIzjJxFz+KqHk7m/CqGWJ2jassc1 oZx1s4/Lq
Bug#875585: marked as done (FTBFS with Java 9: AWT api changes)
Your message dated Wed, 18 Apr 2018 08:51:35 + with message-id and subject line Bug#875585: fixed in jmol 14.6.4+2016.11.05+dfsg1-3.1 has caused the Debian Bug report #875585, regarding FTBFS with Java 9: AWT api changes 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.) -- 875585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875585 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jmol Version: 14.6.4+2016.11.05+dfsg1 Severity: normal User: debian-j...@lists.debian.org Usertags: default-java9 This package fails to build with default-jdk pointing to openjdk-9-jdk. Please fix it, so that we can start the transition to Java 9. The wiki has some common problems and their solutions: https://wiki.debian.org/Java/Java9Pitfalls Build log: cd JSpecView && ant -Dnetscape.jar.path=/usr/share/icedtea-web/plugin.jar -DPrivate.propertyFile=none make-application-jar javadoc Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8 Buildfile: /build/jmol-14.6.4+2016.11.05+dfsg1/JSpecView/build.xml [input] skipping input as property Private.propertyFile has already been set. build: [echo] copying files from ../Jmol/src/org/jmol [copy] Copying 5 files to /build/jmol-14.6.4+2016.11.05+dfsg1/JSpecView/src/org/jmol [echo] getting application icons and resources [mkdir] Created dir: /build/jmol-14.6.4+2016.11.05+dfsg1/JSpecView/bin [javac] Compiling 86 source files to /build/jmol-14.6.4+2016.11.05+dfsg1/JSpecView/bin [javac] /build/jmol-14.6.4+2016.11.05+dfsg1/JSpecView/src/jspecview/application/AwtTreeNode.java:9: error: AwtTreeNode is not abstract and does not override abstract method children() in JSVTreeNode [javac] public class AwtTreeNode extends [javac]^ [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. [javac] 1 error BUILD FAILED /build/jmol-14.6.4+2016.11.05+dfsg1/JSpecView/build.xml:115: Compile failed; see the compiler error output for details. Cheers, Chris. --- End Message --- --- Begin Message --- Source: jmol Source-Version: 14.6.4+2016.11.05+dfsg1-3.1 We believe that the bug you reported is fixed in the latest version of jmol, 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 875...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tobias Hansen (supplier of updated jmol 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: Tue, 17 Apr 2018 23:18:40 +0200 Source: jmol Binary: jmol libjmol-java jmol-applet libjmol-java-doc Architecture: source Version: 14.6.4+2016.11.05+dfsg1-3.1 Distribution: unstable Urgency: medium Maintainer: Debichem Team Changed-By: Tobias Hansen Description: jmol - Molecular Viewer jmol-applet - Jmol Java applet libjmol-java - Java library for molecular structures libjmol-java-doc - API documentation for libjmol-java Closes: 875585 Changes: jmol (14.6.4+2016.11.05+dfsg1-3.1) unstable; urgency=medium . * Non-maintainer upload. * Apply java9-compatibility.patch by Emmanuel Bourg. (Closes: #875585) * Update Vcs-* fields to salsa. Checksums-Sha1: 0b67d61c46c7f588a4308b2d12bc0e15dad574b4 2425 jmol_14.6.4+2016.11.05+dfsg1-3.1.dsc 70f27d2e1e5a920262a16459082eb5135776e78f 29812 jmol_14.6.4+2016.11.05+dfsg1-3.1.debian.tar.xz 05f06fe1fffe3829d1c9b55aa32c0a4d6f4d7be7 11647 jmol_14.6.4+2016.11.05+dfsg1-3.1_source.buildinfo Checksums-Sha256: d3822021c98f676ed8dbc3f761efcab9541ef8c750e729a0d410857805a7ce24 2425 jmol_14.6.4+2016.11.05+dfsg1-3.1.dsc 9a5ff5d4938a5351dc5a821f88aab6bc07b603d74e8b1727ee62bbb9107f4262 29812 jmol_14.6.4+2016.11.05+dfsg1-3.1.debian.tar.xz 099beaa79c0a4d8a79a7dea7a91ccac2496b67a51422ae60388e581a3e49bd58 11647 jmol_14.6.4+2016.11.05+dfsg1-3.1_source.buildinfo Files: b8eac90d7382d3e5d3c6b10f84e12a6d 2425 science optional jmol_14.6.4+2016.11.05+dfsg1-3.1.dsc 79c05567f04c8bf4e401bdab6ccd8d73 29812 science optional jmol_14.6.4+2016.11.05+dfsg1-3.1.debian.tar.xz 3d9ef74671f4a7e8f9a6a74a730fcacc 11647 science optional jmol_14.6.4+2016.11.05+dfsg1-3.1_source.buildinfo -BEGIN PGP
Processed: Re: Bug#895978: FSHS violation: systemd-timesyncd installed in /lib
Processing control commands: > tag -1 moreinfo Bug #895978 [systemd] FSHS violation: systemd-timesyncd installed in /lib Added tag(s) moreinfo. -- 895978: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895978 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#895978: FSHS violation: systemd-timesyncd installed in /lib
Control: tag -1 moreinfo
Hello Thomas,
Thomas Goirand [2018-04-18 9:36 +0200]:
> Package: systemd
> Version: 232-25+deb9u2
> Severity: serious
What is the rationale for this being release-critical?
> Doing my everyday $work, I found that a machine had systemd-timesyncd
> installed. To the contrary of a lot of people, I don't really mind it,
> if it does the job. Though it got installed in
> /lib/systemd/systemd-timesyncd. This makes no sense for a daemon, that
> must be installed in /bin (if needed at boot time) or in /usr/bin
> (more likely).
This isn't a program which you are supposed to run on the command line, so
putting it into $PATH makes no sense. This is a typical example of a program
that should be in LIBEXECDIR, which is {,/usr}/lib/ in Debian.
So it can certainly be argued that this (and a lot of similar programs) should
move to /usr/lib/systemd/systemd-timesyncd instead of /lib, but that doesn't
seem to be release critical to me. I can't find a Debian Policy requirement
that would mandate this, but maybe I'm overlooking something.
Martin
Processed: Re: Bug#893538: [src:kbibtex]
Processing control commands: > block 893538 by 894969 Bug #893538 [src:kbibtex] kbibtex FTBFS: delegate-failed rsvg-convert 893538 was blocked by: 894969 893538 was not blocking any bugs. Ignoring request to alter blocking bugs of bug #893538 to the same blocks previously set -- 893538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893538 894969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894969 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#893538: [src:kbibtex]
Control: block 893538 by 894969 On Mon, Apr 02, 2018 at 05:22:30PM -0400, Antonio Russo wrote: > In the process of fixing another bug [1], I had no problem > building from source. Could you try to reproduce with the > patch I've included with that bug? It should change the svg > importer to not try to use rsvg (though, I don't understand > why it would try and fail). >... The problem is that the build dependency on libmagickcore-6.q16-3-extra can pull in the wrong package. This can be fixed properly after #894969 got fixed in imagemagick. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Processed: Re: Bug#893538: [src:kbibtex]
Processing control commands: > block 893538 by 894969 Bug #893538 [src:kbibtex] kbibtex FTBFS: delegate-failed rsvg-convert 893538 was not blocked by any bugs. 893538 was not blocking any bugs. Added blocking bug(s) of 893538: 894969 -- 893538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893538 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 895970 in 5.2.8-dfsg-5
Processing commands for cont...@bugs.debian.org: > found 895970 5.2.8-dfsg-5 Bug #895970 [virtualbox] virtualbox: Unroutable maintainer address Marked as found in versions virtualbox/5.2.8-dfsg-5. > thanks Stopping processing here. Please contact me if you need assistance. -- 895970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895970 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 895971 in 5.2.8-1
Processing commands for cont...@bugs.debian.org: > found 895971 5.2.8-1 Bug #895971 [virtualbox-ext-pack] virtualbox-ext-pack: Unroutable maintainer address Marked as found in versions virtualbox-ext-pack/5.2.8-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 895971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#891025: Bug #891025 in flask-login marked as pending
Control: tag -1 pending Hello, Bug #891025 in flask-login 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/flask-login/commit/a7d6a5aeb689c4eb962a2cce75655eeb7e3e7466 Fix Breaks/Replaces of python3-flask-login-doc. * Team upload. * Fix Breaks/Replaces of python3-flask-login-doc. Spotted by Andreas Beckmann, thanks! (Closes: #891025 again) * The doc package Enhances the module package instead of Suggests. (this message was generated automatically) -- Greetings https://bugs.debian.org/891025
Processed: Bug #891025 in flask-login marked as pending
Processing control commands: > tag -1 pending Bug #891025 [python-flask-login-doc] python-flask-login-doc: missing Breaks+Replaces: python3-flask-login-doc Added tag(s) pending. -- 891025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891025 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#895978: FSHS violation: systemd-timesyncd installed in /lib
Package: systemd Version: 232-25+deb9u2 Severity: serious Hi, Doing my everyday $work, I found that a machine had systemd-timesyncd installed. To the contrary of a lot of people, I don't really mind it, if it does the job. Though it got installed in /lib/systemd/systemd-timesyncd. This makes no sense for a daemon, that must be installed in /bin (if needed at boot time) or in /usr/bin (more likely). Please ping upstream and ask for sensible respect of the FSHS. Cheers, Thomas Goirand (zigo)
Bug#886968: btrfs-progs-udeb: depends on non-udeb: libzstd1
On 18/04/18 01:30, Cyril Brulebois wrote: > That's another perfect example why udeb additions should get reviewed: > we would have noticed another buggy package, and its bugginess might not > have been copied over to another package. I'm sure people don't request those reviews because they don't know or because they forget. A lintian warning could help, or ftp-masters enforcing an ack. Though I'd prefer the former as I wouldn't like NEW to have another bottleneck. > If someone wants to drive an effort to make -V a must for udebs in > policy, that's probably fine. It doesn't strike me as ultimately needed > (we've lived without it for quite some time because maintainers tend to > just do the right thing), but if people have spare time, go for it. It's not in policy (but I don't think it has to be), but following the conversation on #-ftp yesterday I opened: #895949 lintian: warn about packages with udebs but no udeb line in shlibs #895953 lintian: check that shlibs-version >= higher-version-symbols-file The latter wouldn't enforce -V, but would check that we at least get a high enough version in shlibs as compared to the .symbols file (and would have solved the zstd problem). Cheers, Emilio
