Bug#913137: closing 913137
close 913137 5.2.22-dfsg-1 thanks
Processed: closing 913137
Processing commands for cont...@bugs.debian.org:
> close 913137 5.2.22-dfsg-1
Bug #913137 {Done: Gianfranco Costamagna }
[src:virtualbox] virtualbox: VirtualBox E1000 Guest-to-Host Escape
Marked as fixed in versions virtualbox/5.2.22-dfsg-1.
Bug #913137 {Done: Gianfranco Costamagna }
[src:virtualbox] virtualbox: VirtualBox E1000 Guest-to-Host Escape
Bug 913137 is already marked as done; not doing anything.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
913137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913137
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#905367: marked as done (cccolutils: FTBFS in sid)
Your message dated Sun, 11 Nov 2018 07:18:51 +
with message-id
and subject line Bug#905367: fixed in cccolutils 1.4-2
has caused the Debian Bug report #905367,
regarding cccolutils: FTBFS in sid
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.)
--
905367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905367
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:cccolutils
Version: 1.4-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in sid but it failed:
[...]
debian/rules build-arch
dh build-arch --with python3 --buildsystem=pybuild
dh_update_autotools_config -a -O--buildsystem=pybuild
dh_autoreconf -a -O--buildsystem=pybuild
dh_auto_configure -a -O--buildsystem=pybuild
I: pybuild base:217: python3.7 setup.py config
running config
I: pybuild base:217: python3.6 setup.py config
running config
dh_auto_build -a -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python3.7 setup.py build
running build
running build_ext
building 'cccolutils' extension
creating build
creating build/temp.linux-amd64-3.7
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
-I/usr/include/python3.7m -c cccolutils.c -o
build/temp.linux-amd64-3.7/cccolutils.o
cccolutils.c:17:10: fatal error: Python.h: No such file or directory
#include
^~
compilation terminated.
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
E: pybuild pybuild:338: build: plugin distutils failed with: exit code=1:
/usr/bin/python3.7 setup.py build
dh_auto_build: pybuild --build -i python{version} -p "3.7 3.6" returned exit
code 13
make: *** [debian/rules:8: build-arch] Error 25
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit
status 2
The build was made with "dpkg-buildpackage -B" in my autobuilder,
but it also fails here:
https://buildd.debian.org/status/package.php?p=cccolutils
Seems like a missing build-depends somewhere.
Thanks.
--- End Message ---
--- Begin Message ---
Source: cccolutils
Source-Version: 1.4-2
We believe that the bug you reported is fixed in the latest version of
cccolutils, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 905...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sergio Durigan Junior (supplier of updated cccolutils
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 11 Nov 2018 01:50:28 -0500
Source: cccolutils
Binary: python3-cccolutils
Architecture: source
Version: 1.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team
Changed-By: Sergio Durigan Junior
Description:
python3-cccolutils - Python Kerberos Credential Cache Collection Utilities
(Python 3)
Closes: 905367
Changes:
cccolutils (1.4-2) unstable; urgency=medium
.
[ Ondřej Nový ]
* d/control: Fix wrong Vcs-*
.
[ Sergio Durigan Junior ]
* List "python3-all-dev" on B-D instead of "python3-dev", which fixes a
FTBFS when there are multiple Python 3 versions supported.
(Closes: #905367)
* Bump Standards-Version to 4.2.1.
Checksums-Sha1:
c7658b6c57bb22313860baf0bf7db2fc672853dd 2086 cccolutils_1.4-2.dsc
2f9ffcd306ff7b0e2517766376dda8183cd00e7a 1980 cccolutils_1.4-2.debian.tar.xz
b64954549e3a64be9255b43af6807fc631dbc2dd 7048 cccolutils_1.4-2_amd64.buildinfo
Checksums-Sha256:
01c68f3c2206373aa43c5b0847d086593be263590a4c46ddfd74ea58c6509d32 2086
cccolutils_1.4-2.dsc
c2ffdd2d592e16180a8f6eea7168a8143ae188c595d0421afc15f661be3f69e7 1980
cccolutils_1.4-2.debian.tar.xz
d2581696724d3f470a9a1198d88ff17d4a07820ffd7b2ae718c15602c6d0f874 7048
cccolutils_1.4-2_amd64.buildinfo
Files:
552c0bed4a2890e17317c002ba9c7b90 2086 python optional cccolutils_1.4-2.dsc
5f7c10f260f0d772f5798fee8cb20608 1980 python optional
cccolutils_1.4-2.debian.tar.xz
6efb7fb29e66336b2b6fccffe1cf6746 7048
Bug#913452: vtk-dicom has a hard-coded dependency on python (< 3.7)
Package: src:vtk-dicom Version: 0.8.7-2 Severity: serious Tags: sid buster vtk-dicom has a hard-coded dependency on python (< 3.7), which will make the package RC with the move to Python 3.7. Please update the package.
Bug#893861: marked as done (thawab: Intent to remove from Debian)
Your message dated Sun, 11 Nov 2018 04:16:10 + with message-id <5be7ad0a99351_3642af9ab8050dc2...@godard.mail> and subject line Bug #893861 in thawab fixed has caused the Debian Bug report #893861, regarding thawab: Intent to remove from Debian 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.) -- 893861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893861 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: thawab Version: 3.2.0-1.2 Severity: serious Tags: buster sid X-Debbugs-CC: aelmahmo...@users.sourceforge.net thawab's last maintainer upload was 3 years ago. It was removed from Debian Testing 8 months ago because it depends on the old webkitgtk. It is now one of the last few apps preventing the complete removal of the old webkitgtk from Debian. Are you ok with me filing a removal bug now? If this issue is fixed, thawab could be reintroduced to Debian. (I think you can ask the ftpmasters for expedited processing since it was already in Debian.) I contacted أحمد المحمودي (Ahmed El-Mahmoudy) in late December about this issue but didn't receive a reply yet. Thanks, Jeremy Bicha --- End Message --- --- Begin Message --- Hello, Bug #893861 in thawab reported by you has been fixed in the Git repository. You can see the commit message below, and you can check the diff of the fix at: https://salsa.debian.org/islamic-team/thawab/commit/8d9eae628868faa7533e083d3383eff8ac62943a Add webkit2.diff patch to port to Webkit2 Closes: #893861 (this message was generated automatically) -- Greetings https://bugs.debian.org/893861--- End Message ---
Processed: Bug #893861 in thawab marked as pending
Processing control commands:
> tag -1 pending
Bug #893861 {Done: أحمد المحمودي }
[src:thawab] thawab: Intent to remove from Debian
Added tag(s) pending.
--
893861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893861
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#893861: Bug #893861 in thawab marked as pending
Control: tag -1 pending Hello, Bug #893861 in thawab 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/islamic-team/thawab/commit/8d9eae628868faa7533e083d3383eff8ac62943a Add webkit2.diff patch to port to Webkit2 Closes: #893861 (this message was generated automatically) -- Greetings https://bugs.debian.org/893861
Processed: Re: gnome-commander: Please drop the (build-)dependency against gnome-vfs
Processing commands for cont...@bugs.debian.org: > forwarded 868417 https://gitlab.gnome.org/GNOME/gnome-commander/issues/33 Bug #868417 [src:gnome-commander] gnome-commander: Please drop the (build-)dependency against gnome-vfs Changed Bug forwarded-to-address to 'https://gitlab.gnome.org/GNOME/gnome-commander/issues/33' from 'https://bugzilla.gnome.org/show_bug.cgi?id=589069'. > tags 868417 -fixed-upstream Bug #868417 [src:gnome-commander] gnome-commander: Please drop the (build-)dependency against gnome-vfs Removed tag(s) fixed-upstream. > End of message, stopping processing here. Please contact me if you need assistance. -- 868417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868417 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#893861: thawab: Intent to remove from Debian
On Sat, Nov 10, 2018 at 9:27 AM أحمد المحمودي wrote: > There is an upstream patch. > Please delay for one more week. Sure. I can wait until the end of November. Thanks, Jeremy Bicha
Bug#913271: [Pkg-rust-maintainers] Bug#913271: segfault - broken rust compiling
Ximin Luo: > [..] > Thread 1 "rustc" received signal SIGSEGV, Segmentation fault. > 0x71e273bc in llvm::StringMapImpl::LookupBucketFor(llvm::StringRef) > () from /usr/lib/x86_64-linux-gnu/libLLVM-7.so.1 > (gdb) bt > #0 0x71e273bc in > llvm::StringMapImpl::LookupBucketFor(llvm::StringRef) () from > /usr/lib/x86_64-linux-gnu/libLLVM-7.so.1 > #1 0x71f654c9 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-7.so.1 > #2 0x71f65491 in llvm::MDString::get(llvm::LLVMContext&, > llvm::StringRef) () from /usr/lib/x86_64-linux-gnu/libLLVM-7.so.1 > #3 0x71ee69cd in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-7.so.1 Hopefully the stack trace is informative even though some stuff is missing. They are missing because the debug symbols are missing for this version of LLVM: $ dpkg -S /usr/lib/x86_64-linux-gnu/libLLVM-7.so.1 libllvm7:amd64: /usr/lib/x86_64-linux-gnu/libLLVM-7.so.1 $ apt-cache policy libllvm7 libllvm7: Installed: 1:7.0.1~+rc2-2 Candidate: 1:7.0.1~+rc2-2 Version table: *** 1:7.0.1~+rc2-2 500 500 http://deb.debian.org/debian unstable/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy libllvm7-dbgsym libllvm7-dbgsym: Installed: (none) Candidate: 1:7-8 Version table: 1:7-8 500 500 http://deb.debian.org/debian-debug unstable-debug/main amd64 Packages Would you be able to re-enable them Sylvestre? X -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git
Processed: Bug #911183 in logback marked as pending
Processing control commands: > tag -1 pending Bug #911183 [src:logback] logback: FTBFS with Java 11 due to sun.reflect.Reflection removal Added tag(s) pending. -- 911183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#913271: segfault - broken rust compiling
The segfault is triggered by the presence of debuginfo=N where N != 0. You can
avoid it by setting RUSTFLAGS or running "cargo rustc -- -C debuginfo=0"
instead of "cargo build".
Together with the workaround for #913414, this means a temporary workaround for
users could be to set RUSTFLAGS="-C debuginfo=0 -C relocation-model=default" in
their environment. This works in some cases, unfortunately it doesn't work for
packages that have a custom build.rs and use cc in it. (Perhaps the workaround
can be extended to cover these cases too but I couldn't figure out how.)
Here is a backtrace of the segfault, would be good if someone else more
familiar with LLVM than me could take a look:
hello_world$ gdb -q rustc
Reading symbols from rustc...Reading symbols from
/usr/lib/debug/.build-id/e9/0dc62b102986d644f980ffeab6adab6f53625d.debug...done.
done.
warning: Missing auto-load script at offset 0 in section .debug_gdb_scripts
of file /usr/bin/rustc.
Use `info auto-load python-scripts [REGEXP]' to list them.
(gdb) run src/main.rs -C debuginfo=2
Starting program: /usr/bin/rustc src/main.rs -C debuginfo=2
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffee0ed700 (LWP 10750)]
[New Thread 0x7fffedeec700 (LWP 10751)]
[New Thread 0x7fffedceb700 (LWP 10752)]
[New Thread 0x7fffedae8700 (LWP 10753)]
[Thread 0x7fffedae8700 (LWP 10753) exited]
[Thread 0x7fffedceb700 (LWP 10752) exited]
Thread 1 "rustc" received signal SIGSEGV, Segmentation fault.
0x71e273bc in llvm::StringMapImpl::LookupBucketFor(llvm::StringRef) ()
from /usr/lib/x86_64-linux-gnu/libLLVM-7.so.1
(gdb) bt
#0 0x71e273bc in llvm::StringMapImpl::LookupBucketFor(llvm::StringRef)
() from /usr/lib/x86_64-linux-gnu/libLLVM-7.so.1
#1 0x71f654c9 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-7.so.1
#2 0x71f65491 in llvm::MDString::get(llvm::LLVMContext&,
llvm::StringRef) () from /usr/lib/x86_64-linux-gnu/libLLVM-7.so.1
#3 0x71ee69cd in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-7.so.1
#4 0x71ee2d12 in llvm::DIBuilder::createFile(llvm::StringRef,
llvm::StringRef, llvm::Optional >,
llvm::Optional) () from
/usr/lib/x86_64-linux-gnu/libLLVM-7.so.1
#5 0x750a01f2 in LLVMRustDIBuilderCreateFile (Builder=0x555d4180,
Filename=0x7ffeedd8 "src/main.rs", Directory=0x55b3dd10
"$HOME/hello_world")
at /usr/lib/llvm-7/include/llvm/ADT/StringRef.h:85
#6 0x7501d39e in
rustc_codegen_llvm::debuginfo::metadata::compile_unit_metadata (tcx=...,
codegen_unit_name=..., debug_context=0x7ffeeeb0) at
librustc_codegen_llvm/debuginfo/metadata.rs:859
#7 0x74f75946 in rustc_codegen_llvm::context::CodegenCx::new (tcx=...,
codegen_unit=..., llvm_module=) at
librustc_codegen_llvm/context.rs:272
#8 0x74ffad3e in
rustc_codegen_llvm::base::compile_codegen_unit::module_codegen (tcx=...,
cgu_name=...) at librustc_codegen_llvm/base.rs:1225
#9 0x7503e642 in rustc::dep_graph::graph::DepGraph::with_task_impl
(self=0x7fff15d8, arg=..., no_tcx=false, task=0x800e8150, key=...,
cx=..., create_task=,
finish_task_and_alloc_depnode=) at
librustc/dep_graph/graph.rs:342
#10 rustc::dep_graph::graph::DepGraph::with_task (self=0x7fff15d8, key=...,
cx=..., arg=..., task=0x74ffac40
) at
librustc/dep_graph/graph.rs:208
#11 0x74ff8b8f in rustc_codegen_llvm::base::compile_codegen_unit
(tcx=..., cgu_name=...) at librustc_codegen_llvm/base.rs:1199
#12 rustc_codegen_llvm::base::codegen_crate (tcx=..., rx=...) at
librustc_codegen_llvm/base.rs:905
#13 0x7502df70 in ::codegen_crate
(self=, tcx=..., rx=...) at librustc_codegen_llvm/lib.rs:215
#14 0x77deb832 in rustc_driver::driver::phase_4_codegen::{{closure}} ()
at librustc_driver/driver.rs:1369
#15 rustc::util::common::time_ext (do_it=, what=...,
sess=, f=...) at librustc/util/common.rs:163
#16 rustc::util::common::time (sess=, what=..., f=...) at
librustc/util/common.rs:157
#17 0x77e104ae in rustc_driver::driver::phase_4_codegen
(codegen_backend=..., tcx=..., rx=...) at librustc_driver/driver.rs:1369
#18 0x77ebd614 in rustc_driver::driver::compile_input::{{closure}}
(tcx=..., analysis=..., rx=..., result=...) at librustc_driver/driver.rs:328
#19 0x77eb7446 in
rustc_driver::driver::phase_3_run_analysis_passes::{{closure}} (tcx=...) at
librustc_driver/driver.rs:1352
#20 rustc::ty::context::tls::enter_global::{{closure}}::{{closure}} () at
librustc/ty/context.rs:1986
#21 rustc::ty::context::tls::enter_context::{{closure}} () at
librustc/ty/context.rs:1954
#22 rustc::ty::context::tls::set_tlv (value=, f=...) at
librustc/ty/context.rs:1893
#23 rustc::ty::context::tls::enter_context (context=, f=...) at
librustc/ty/context.rs:1953
#24 0x77e6e1cb in rustc::ty::context::tls::enter_global::{{closure}} ()
at librustc/ty/context.rs:1985
#25
Bug#911183: Bug #911183 in logback marked as pending
Control: tag -1 pending Hello, Bug #911183 in logback reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at: https://salsa.debian.org/java-team/logback/commit/83b545532cb397c8a872c295a56f445c35a4e068 Fixed the build failure with Java 11 (Closes: #911183) (this message was generated automatically) -- Greetings https://bugs.debian.org/911183
Bug#913447: Fwd: Bug#913447: libgap-sage: Depends on nbs version of gap
Hello, I guess that we have to remove libgal-sage-4 sooner or later: please let me know when we can remove it. Thanks, Jerome Forwarded Message Subject: Bug#913447: libgap-sage: Depends on nbs version of gap Resent-Date: Sat, 10 Nov 2018 23:39:01 + Resent-From: Jeremy Bicha Resent-To: debian-bugs-d...@lists.debian.org Resent-CC: calcu...@rezozer.net, Debian Science Maintainers Date: Sat, 10 Nov 2018 18:36:55 -0500 From: Jeremy Bicha Reply-To: Jeremy Bicha , 913...@bugs.debian.org To: submit Source: libgap-sage Version: 4.8.8+6+20181010g0581647+dsx-1 Severity: serious X-Debbugs-CC: calcu...@rezozer.net libgap-sage-4 has this dependency: Depends: gap (>= 4r8p8), gap (<< 4r8p9) But the version of gap in unstable is 4r9p3-3. I've filing this as serious since version 4r8p8 is no longer built from source (NBS) in unstable. Thanks, Jeremy Bicha signature.asc Description: OpenPGP digital signature
Bug#913447: libgap-sage: Depends on nbs version of gap
Source: libgap-sage Version: 4.8.8+6+20181010g0581647+dsx-1 Severity: serious X-Debbugs-CC: calcu...@rezozer.net libgap-sage-4 has this dependency: Depends: gap (>= 4r8p8), gap (<< 4r8p9) But the version of gap in unstable is 4r9p3-3. I've filing this as serious since version 4r8p8 is no longer built from source (NBS) in unstable. Thanks, Jeremy Bicha
Bug#912297: ansible: CVE-2018-16837
Quick follow-up: I don't have a patch for CVE-2018-10875. However, the patch in question I have is for CVE-2018-10855, which is already checked in on the stretch branch of the packaging repo. For some reason the security tracker has this CVE marked as "not affected", although I could reproduce the issue on stretch. On 08/11/2018 11:51, Lee Garrett wrote: > Hi, > > sorry for the late response. CVE-2018-16837 should be fairly straight-forward > to fix in stretch and jessie. > > For CVE-2018-10875 I have a patch in my work dir that should fix it. I'll push > it to the git stretch branch tomorrow (not on my work machine right now). > > For CVE-2018-10874, it's not clear if it affects stable. The inventory module > was completely rewritten in (IIRC) ansible 2.5, so it won't be a > straight-forward patch. > > Regards, > Lee > > On 07/11/2018 22:55, Moritz Mühlenhoff wrote: >> On Tue, Oct 30, 2018 at 12:35:05AM -0400, Chris Lamb wrote: >>> Hi Ivo, >>> From the upstream changelog for 2.7.1+dfsg-1 (already in unstable): >>> [..] - user module - do not pass ssh_key_passphrase on cmdline (CVE-2018-16837) >>> >>> Thanks for providing this and no problem that this wasn't in the >>> changelog. >>> >>> Security team: This still affects stretch and jessie as I unless >>> I'm missing something - would you like me to prepare an upload for >>> stable? I'm happy to take the LTS side of things. >> >> We can fix that one in a DSA, but should also fix CVE-2018-10875 >> and CVE-2018-10874, then. >> >> Cheers, >> Moritz >> >
Bug#913408: Bug#901827: dpkg: Support two-sided version constraint ranges, required to properly translate Cargo dependencies
Control: severity 901827 important Control: block 913408 by 901827 Ximin Luo: > Guillem Jover: >> [..] >> >> So you could have package slab-X.Y and then depend on just that, or if >> for some reason you need to have coinstallability down to the minor >> version, then slab-X.Y.Z, in which case that package would provide >> slab-X.Y (= X.Y.Z). In addition, all of these would also provide >> slab-X (= X.Y.Z) and slab (= X.Y.Z) and probably also slab, so that >> you can represent all the range types. >> >> Cargo deps (A) dpkg deps (A-X.Y || A-X.Y.Z) >> A A >> A (>= 6) A (>= 6) >> A (>= 6.1) A (>= 6.1) >> A (>= 6.1.3) A (>= 6.1.3) >> A (>= 6, << 7) A-6 >> A (>= 6.1, << 6.2) A-6.1 >> A (= 6)A-6 >> A (= 6.1) A-6.1 >> > > Thanks for being specific here. After thinking after it for a bit, I think > this might work. The key is to only generate a single item within in the > comma-separated list of AND-clauses in the dpkg dependency, where the item > itself is a "|"-separated OR-clause. It would be pretty ugly in some > circumstances: > > Cargo deps dpkg deps > A (>= 6.1, << 9.5) >A-6 (>= 6.1) | A-7 | A-8 | A-9 (<< 9.5) > > but I think I have a decently-simple way of achieving this in debcargo. > This translation scheme works for Depends and Build-Depends, however it does not work for Replaces and Breaks, please see #913408 for an example of the problem. In the abstract example above, since A-5 (= 5.1.1) replaces files from a previously-uploaded A (= 5.1.1), it must declare Replaces+Breaks: A (= 5). But in reality, there may be multiple Debian uploads of 5.1.1 including security uploads and backports. So we really need to declare: Breaks: A (>= 5.1.1~~, << 5.1.2~~) Replaces: A (>= 5.1.1~~, << 5.1.2~~) but this is not possible in Debian today. Note that this: Breaks: A (>= 5.1.1~~), A (<< 5.1.2~~) Replaces: A (>= 5.1.1~~), A (<< 5.1.2~~) won't work as it is equivalent to Breaks: A, Replaces: A which is not what we want. X -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git
Processed: Re: Bug#901827: dpkg: Support two-sided version constraint ranges, required to properly translate Cargo dependencies
Processing control commands: > severity 901827 important Bug #901827 [dpkg] dpkg: Support two-sided version constraint ranges, required to properly translate Cargo dependencies Severity set to 'important' from 'wishlist' > block 913408 by 901827 Bug #913408 [librust-crossbeam-epoch-0.5-dev] librust-crossbeam-epoch-0.5-dev: missing Breaks+Replaces: librust-crossbeam-epoch-dev (<< 0.6) 913408 was not blocked by any bugs. 913408 was not blocking any bugs. Added blocking bug(s) of 913408: 901827 -- 901827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901827 913408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#901827: dpkg: Support two-sided version constraint ranges, required to properly translate Cargo dependencies
Processing control commands: > severity 901827 important Bug #901827 [dpkg] dpkg: Support two-sided version constraint ranges, required to properly translate Cargo dependencies Ignoring request to change severity of Bug 901827 to the same value. > block 913408 by 901827 Bug #913408 [librust-crossbeam-epoch-0.5-dev] librust-crossbeam-epoch-0.5-dev: missing Breaks+Replaces: librust-crossbeam-epoch-dev (<< 0.6) 913408 was blocked by: 901827 913408 was not blocking any bugs. Ignoring request to alter blocking bugs of bug #913408 to the same blocks previously set -- 901827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901827 913408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#913445: Broken with Thunderbird 60
Source: imap-acl-extension Severity: grave When installing the plugin on Thunderbird 60, it's disabled and only prints "IMAP-ACL-Extension is incompatible with Thunderbird 60.3" on stretch and sid. TB 60 was uploaded to stretch two months ago (and three months ago to sid), given that noone filed a bug so far, it makes me wonder whether this package is used at all... Cheers, Moritz
Bug#913443: Broken with Thunderbird 60
Package: xul-ext-tbdialout Version: 1.7.2-2 Severity: grave The plugin is broken with Thunderbird 60 in stretch and sid, after installation it's disabled and only prints "TBDialOut is incompatible with Thunderbird 60.3". TB 60 was uploaded to stretch two months ago (and three months ago to sid), given that noone filed a bug so far, it makes me wonder whether this package is used at all... Cheers, Moritz
Bug#906863: xul-ext-personasplus no longer works with firefox-esr 60
On Tue, Aug 21, 2018 at 09:17:28PM +0300, Adrian Bunk wrote: > Package: xul-ext-personasplus > Version: 1.7.8-1 > Severity: serious > > XUL addons are no longer supported. > > If it is confirmed that this package works with thunderbird 60, > it might be an option to change the dependency to only thunderbird. It'a also broken on Thunderbird. When installing it, the addon is disabled with the message "Personas Plus is incompatible with Thunderbird 60.3" on stretch and sid. Cheers, Moritz
Bug#912377: marked as done (libxstream-java: FTBFS with Java 11 due to javax.activation removal)
Your message dated Sat, 10 Nov 2018 22:19:55 + with message-id and subject line Bug#912377: fixed in libxstream-java 1.4.11-1 has caused the Debian Bug report #912377, regarding libxstream-java: FTBFS with Java 11 due to javax.activation removal 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.) -- 912377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912377 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libxstream-java Version: 1.4.10-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libxstream-java.html ... [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 5.633 s [INFO] Finished at: 2018-10-30T08:20:31-12:00 [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) on project xstream: Compilation failure: Compilation failure: [ERROR] /build/1st/libxstream-java-1.4.10/xstream/src/java/com/thoughtworks/xstream/converters/extended/ActivationDataFlavorConverter.java:[13,24] package javax.activation does not exist [ERROR] /build/1st/libxstream-java-1.4.10/xstream/src/java/com/thoughtworks/xstream/converters/extended/ActivationDataFlavorConverter.java:[32,24] cannot find symbol [ERROR] symbol: class ActivationDataFlavor [ERROR] location: class com.thoughtworks.xstream.converters.extended.ActivationDataFlavorConverter [ERROR] /build/1st/libxstream-java-1.4.10/xstream/src/java/com/thoughtworks/xstream/converters/extended/ActivationDataFlavorConverter.java:[36,15] cannot find symbol [ERROR] symbol: class ActivationDataFlavor [ERROR] location: class com.thoughtworks.xstream.converters.extended.ActivationDataFlavorConverter [ERROR] /build/1st/libxstream-java-1.4.10/xstream/src/java/com/thoughtworks/xstream/converters/extended/ActivationDataFlavorConverter.java:[36,50] cannot find symbol [ERROR] symbol: class ActivationDataFlavor [ERROR] location: class com.thoughtworks.xstream.converters.extended.ActivationDataFlavorConverter [ERROR] /build/1st/libxstream-java-1.4.10/xstream/src/java/com/thoughtworks/xstream/converters/extended/ActivationDataFlavorConverter.java:[78,9] cannot find symbol [ERROR] symbol: class ActivationDataFlavor [ERROR] location: class com.thoughtworks.xstream.converters.extended.ActivationDataFlavorConverter [ERROR] /build/1st/libxstream-java-1.4.10/xstream/src/java/com/thoughtworks/xstream/converters/extended/ActivationDataFlavorConverter.java:[81,34] cannot find symbol [ERROR] symbol: class ActivationDataFlavor [ERROR] location: class com.thoughtworks.xstream.converters.extended.ActivationDataFlavorConverter [ERROR] /build/1st/libxstream-java-1.4.10/xstream/src/java/com/thoughtworks/xstream/converters/extended/ActivationDataFlavorConverter.java:[83,34] cannot find symbol [ERROR] symbol: class ActivationDataFlavor [ERROR] location: class com.thoughtworks.xstream.converters.extended.ActivationDataFlavorConverter [ERROR] /build/1st/libxstream-java-1.4.10/xstream/src/java/com/thoughtworks/xstream/converters/extended/ActivationDataFlavorConverter.java:[85,34] cannot find symbol [ERROR] symbol: class ActivationDataFlavor [ERROR] location: class com.thoughtworks.xstream.converters.extended.ActivationDataFlavorConverter [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn -rf :xstream dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/build/1st/libxstream-java-1.4.10 -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/build/1st/libxstream-java-1.4.10/debian/maven.properties org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/build/1st/libxstream-java-1.4.10/debian -Dmaven.repo.local=/build/1st/libxstream-java-1.4.10/debian/maven-repo
Bug#892336: marked as done (otf2bdf: Please use 'pkg-config' to find FreeType 2)
Your message dated Sat, 10 Nov 2018 21:49:52 + with message-id and subject line Bug#892336: fixed in otf2bdf 3.1-4.1 has caused the Debian Bug report #892336, regarding otf2bdf: Please use 'pkg-config' to find FreeType 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 892336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892336 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: otf2bdf Severity: important Dear Maintainer, The next release of libfreetype6-dev will *not* ship `freetype-config', as the script has now been deprecated in favour of `pkg-config'. This is an upstream change: "Use of the `freetype-config' script to get compilation and linking options is deprecated since it doesn't support cross-compiling, among other deficiencies. Instead, you should use the `pkg-config' interface." [1] Please use `pkg-config' to detect the FreeType 2 headers and libraries in otf2bdf. If this bug is not resolved prior to the release of FreeType 2.9.1, your package may FTBFS. Thank you [1] http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=b0 a93839b52818abbfe9b4c8755b4aa0f5232063 --- End Message --- --- Begin Message --- Source: otf2bdf Source-Version: 3.1-4.1 We believe that the bug you reported is fixed in the latest version of otf2bdf, 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 892...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilko Bengen (supplier of updated otf2bdf package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 26 Oct 2018 22:55:05 +0200 Source: otf2bdf Binary: otf2bdf Architecture: source Version: 3.1-4.1 Distribution: unstable Urgency: medium Maintainer: Miriam Ruiz Changed-By: Hilko Bengen Description: otf2bdf- generate BDF bitmap fonts from OpenType outline fonts Closes: 892336 Changes: otf2bdf (3.1-4.1) unstable; urgency=medium . * Non-maintainer upload * Detect freetype2 via pkg-config, modernize package (Closes: #892336) Checksums-Sha1: 55224891df09990615adcc18bc3784812d66df4e 1798 otf2bdf_3.1-4.1.dsc 592d7b784192c57cae73ec8d9a6d426aeb90351b 4048 otf2bdf_3.1-4.1.debian.tar.bz2 aa8b7b79511cc83998d3c25ee66172eeda99df83 6251 otf2bdf_3.1-4.1_source.buildinfo Checksums-Sha256: 91aa7892f826452b87fdc2e2ca3e85d21146f30a0c5f50819b01ba5e30851a26 1798 otf2bdf_3.1-4.1.dsc 77a0e1d618bc3bd8d88480bac17baece5b272510f24b34baa0d290776a220584 4048 otf2bdf_3.1-4.1.debian.tar.bz2 c1b863990487a61d650b4fd985c3f37477a07566ff25933f559df44637692673 6251 otf2bdf_3.1-4.1_source.buildinfo Files: 92c72fc0c283bcf661a359a848109295 1798 utils optional otf2bdf_3.1-4.1.dsc ea908c642695a1f07ea90df5d52495ba 4048 utils optional otf2bdf_3.1-4.1.debian.tar.bz2 0adb12f5aa45cfcdabfb135e6d7eb17d 6251 utils optional otf2bdf_3.1-4.1_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCAAwFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAlvTgOMSHGJlbmdlbkBk ZWJpYW4ub3JnAAoJEHW3EGNcITp+xKQP/0V5gfROlT6bZp9IOAd/28Z2AIbFoQ3H xdlTgMTgnr9EK2yIda/5l8lxsB1Gfktzb8iYakGxCF14FO7AS8xKyqFegWPCQf1Z 2B7RQ2/X42CKwGb3MksyBIsIBfrBFuGHGHgV3C+aFQmDNQE83Al4Y4yXsLutExH0 FSweOwjmJxhiuqX7vc4DsgVUKazN6Uf6rJNyaRM/J1KuQDjDUjRm4AQMPU4Saodp qO2VZVcJueE1FRx1upYfqdJHMdbWD4jAHF2jXkJvDW84QzSG/xa/RnE+MaCh3Hza H7m9GYWl6Q0CCnzegG2eywww5n6WcFMVIlUQHJnmiuXZTiYtp+N7tR0A9WeEwoMN 7XRSbo4bmsRmDrHYC533Y5c9zT9Tm/WSnEcBFu0hZD/0eK4KE1b9h4Q0wy7nyeID Glz1Nj8F04gFArF4Jxk9QeZLcb2Xr3lOVt+UV2dPJ4XczuofPiyYaYJ1u4qV3Uro 4G8FQqfvduItCecKEcVMgmaWGfaE4FeulEdht4lo9jmGtz+k9dYgkj0u7joHek67 +c7hRNYANCEIWty4yKFo/t6cprQDcTmgNBkOy/W3WNBQqEElsW1DrcJ4y48sVhGH Gr+3NkRblX+OW2eHB70rEVtQSPTqw+M4ZR7pDXaeYIlMFTwVH+3goQFCd07P/7DV HLqcjXcNqV8V =u4PI -END PGP SIGNATURE End Message ---
Bug#913137: marked as done (virtualbox: VirtualBox E1000 Guest-to-Host Escape)
Your message dated Sat, 10 Nov 2018 21:42:07 + (UTC) with message-id <715204243.487615.1541886127...@mail.yahoo.com> and subject line Re: Bug#913137: closed by Gianfranco Costamagna (Bug#913137: fixed in virtualbox 5.2.22-dfsg-1) has caused the Debian Bug report #913137, regarding virtualbox: VirtualBox E1000 Guest-to-Host Escape 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.) -- 913137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913137 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: virtualbox Version: 5.2.20-dfsg-3 Severity: grave Tags: security upstream Justification: user security hole Hi See https://github.com/MorteNoir1/virtualbox_e1000_0day for the respective report. Regards, Salvatore --- End Message --- --- Begin Message --- https://github.com/MorteNoir1/virtualbox_e1000_0day/issues/12fixed according to the first reporter. G. Il venerdì 9 novembre 2018, 22:54:08 CET, Salvatore Bonaccorso ha scritto: Hi Gianfranco Let's keep this open until it is confirmed that the changes 5.2.20 -> 5.2.22 are actually enough. Did you got any confirmation on your query to upstream? Regards, Salvatore --- End Message ---
Bug#913058: marked as done (libc++1-7,libc++1-8: both ship libc++.so.1{,.0})
Your message dated Sat, 10 Nov 2018 21:21:51 +
with message-id
and subject line Bug#913058: fixed in llvm-toolchain-snapshot
1:8~svn346586-1~exp1
has caused the Debian Bug report #913058,
regarding libc++1-7,libc++1-8: both ship libc++.so.1{,.0}
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
913058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913058
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc++1-7,libc++1-8
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
>From the attached log (scroll to the bottom...):
Selecting previously unselected package libc++abi1-8:amd64.
Preparing to unpack .../libc++abi1-8_1%3a8~svn343154-1_amd64.deb ...
Unpacking libc++abi1-8:amd64 (1:8~svn343154-1) ...
dpkg: error processing archive
/var/cache/apt/archives/libc++abi1-8_1%3a8~svn343154-1_amd64.deb (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libc++abi.so.1', which is
also in package libc++abi1-7:amd64 1:7-8
Selecting previously unselected package libc++1-8:amd64.
Preparing to unpack .../libc++1-8_1%3a8~svn343154-1_amd64.deb ...
Unpacking libc++1-8:amd64 (1:8~svn343154-1) ...
dpkg: error processing archive
/var/cache/apt/archives/libc++1-8_1%3a8~svn343154-1_amd64.deb (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libc++.so.1', which is also
in package libc++1-7:amd64 1:7-8
Errors were encountered while processing:
/var/cache/apt/archives/libc++abi1-8_1%3a8~svn343154-1_amd64.deb
/var/cache/apt/archives/libc++1-8_1%3a8~svn343154-1_amd64.deb
You probably want to use C/R/B on a virtual package similar to what is
done in python-clang-7:
Conflicts+Replaces+Provides: libc++1-x.y
The following files are shipped by both packages:
usr/lib/x86_64-linux-gnu/libc++.so.1
usr/lib/x86_64-linux-gnu/libc++.so.1.0
Similar problems exist between these package pairs:
libc++abi1-7/libc++abi1-8
libomp5-7/libomp5-8
The corresponding clashes in the -dev packages should automatically
be solved once the library packages are no longer co-installable.
cheers,
Andreas
libc++1-7=1%7-8_libc++1-8=1%8~svn343154-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-snapshot
Source-Version: 1:8~svn346586-1~exp1
We believe that the bug you reported is fixed in the latest version of
llvm-toolchain-snapshot, 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 913...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sylvestre Ledru (supplier of updated
llvm-toolchain-snapshot package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 10 Nov 2018 15:14:15 +0100
Source: llvm-toolchain-snapshot
Binary: clang-8 clang-tools-8 clang-format-8 clang-tidy-8 clang-8-doc
libclang1-8 libclang-8-dev libclang-common-8-dev libfuzzer-8-dev python-clang-8
clang-8-examples libllvm8 llvm-8 llvm-8-runtime llvm-8-dev llvm-8-tools
libllvm-8-ocaml-dev llvm-8-doc llvm-8-examples lld-8 liblld-8 liblld-8-dev
lldb-8 liblldb-8 python-lldb-8 liblldb-8-dev libomp-8-dev libomp5-8
libomp-8-doc libc++1-8 libc++-8-dev libc++abi1-8 libc++abi-8-dev
Architecture: source
Version: 1:8~svn346586-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: LLVM Packaging Team
Changed-By: Sylvestre Ledru
Description:
clang-8- C, C++ and Objective-C compiler
clang-8-doc - C, C++ and Objective-C compiler - Documentation
clang-8-examples - Clang examples
clang-format-8 - Tool to format C/C++/Obj-C code
clang-tidy-8 - clang-based C++ linter tool
clang-tools-8 - clang-based tools for C/C++ developments
libc++-8-dev - LLVM C++ Standard library (development files)
libc++1-8 - LLVM C++ Standard library
libc++abi-8-dev - LLVM low level support for a standard C++ library
(development fi
libc++abi1-8 - LLVM
Bug#913271: segfault - broken rust compiling
Le 10/11/2018 à 21:12, Santiago Vila a écrit : > On Thu, 8 Nov 2018, Sylvestre Ledru wrote: > >> Le 08/11/2018 à 21:30, jnq...@gmail.com a écrit : >>> Package: llvm-7 >>> Version: 1:7.0.1~+rc2-1 >>> Severity: grave >>> >>> I've just updated my Sid install and found that building Rust crates >>> with Cargo now fails with a seg fault. >>> >>> Initially I fired a bug report at cargo to kick things off, but I've >>> now discovered that it relates to the llvm-7 update, as switching llvm7 >>> packages back to testing versions fixes the problem. >> Do you have more info than "it segfaults"? > I believe the reported problem is the same that makes all these > recently uploaded rust packages to FTBFS: > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rust-arc-swap.html > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rust-encoding.html > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rust-encode-unicode.html > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rust-crossbeam-epoch-0.5.html > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rust-gobject-sys.html > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rust-grep-regex.html > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rust-heck.html > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rust-iso8601.html > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rust-mio-uds.html > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rust-rustc-version.html > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rust-term.html > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rust-stringprep.html > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rust-string-cache-codegen.html Yeah, this is related to the move of llvm toolchain to be compiled using clang (stage2). Reverting llvm to the previous version works. If someone could help debugging the segfault, this would be great :) Thanks S
Bug#913271: segfault - broken rust compiling
Le 10/11/2018 à 20:04, brian m. carlson a écrit : > On Thu, Nov 08, 2018 at 09:29:43PM +0100, Sylvestre Ledru wrote: >> Do you have more info than "it segfaults"? > I can provide some reproduction steps, if that's helpful. > > 1. Install rustc and cargo. > 2. git clone https://github.com/rust-lang-nursery/rust-clippy.git > 3. cd rust-clippy > 4. git checkout v0.0.212 > 5. cargo build --verbose > 6. Notice build failures due to SIGSEGV. Easier: $ cargo new hello_world --bin $ cargo build --verbose $ rustc --crate-name hello_world src/main.rs --color always --crate-type bin --emit=dep-info,link -C debuginfo=2 -C metadata=923fd6da5ef0e38e -C extra-filename=-923fd6da5ef0e38e --out-dir /tmp/hello_world/target/debug/deps -C incremental=/tmp/hello_world/target/debug/incremental -L dependency=/tmp/hello_world/target/debug/deps [1] 7942 segmentation fault rustc --crate-name hello_world src/main.rs --color always --crate-type bin - S signature.asc Description: OpenPGP digital signature
Bug#911944: neovim FTBFS: tests fail
On Sat, Nov 10, 2018 at 04:09:55PM +0100, Helmut Grohne wrote: > On Sat, Nov 10, 2018 at 09:29:42AM -0500, James McCoy wrote: > > On Fri, Oct 26, 2018 at 03:30:54PM +0200, Helmut Grohne wrote: > > > Looking to reproducible builds, the failure pattern looks quite random: > > > > > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/neovim.html > > > The armhf & ppc64el buildd failures I can't reproduce on the > > porterboxes, although the latter is likely another flaky test. > > armhf likely needs to be retried as the build timed out. It should't have timed out, though. A single test shouldn't take >150 minutes. :) It got stuck, and I would need to investigate that live. > > > However, in local builds for unstable/amd64 in sbuild, I didn't get a > > > single successful build. > > > > If it's not any of the mentioned failures, then some more information > > would be useful, as I have quite the opposite behavior locally. > > What information are you interested in? First off would be the actual failure, but it seems you were hitting the one I reported to upstream. > I also tried in pbuilder and there I only got the utf_char2bytes > failure, not the ones with check_cores. This hints that something about > my build environment is fishy. If I understand correctly, my user's > resource limits "leak" through sbuild while they don't pass through > pbuilder. Would limiting the number of processes or virtual memory be a > plausible explanation for the failures? Possibly. I can more reliably hit the utf_char2bytes failure when I have other builds running in parallel. It seems to correlate with resource contention. > So it might be useful to reduce the scope of this bug to the > utf_char2bytes failure and the armhf/ppc64el buildd failures. Sounds reasonable. Any help triaging/narrowing down ways to reproduce the failures would be helpful. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#913424: trio does not have a stable API
Source: python-trio Version: 0.9.0-1 Severity: serious Forwarded: https://github.com/python-trio/trio/issues/1 Trio upstream do not yet consider the API stable, so in my opinion this package is not yet ready for a stable Debian release. Please use this bug for discussion if you think this status should change. signature.asc Description: PGP signature
Bug#913271: segfault - broken rust compiling
On Thu, 8 Nov 2018, Sylvestre Ledru wrote: > Le 08/11/2018 à 21:30, jnq...@gmail.com a écrit : > > Package: llvm-7 > > Version: 1:7.0.1~+rc2-1 > > Severity: grave > > > > I've just updated my Sid install and found that building Rust crates > > with Cargo now fails with a seg fault. > > > > Initially I fired a bug report at cargo to kick things off, but I've > > now discovered that it relates to the llvm-7 update, as switching llvm7 > > packages back to testing versions fixes the problem. > > Do you have more info than "it segfaults"? I believe the reported problem is the same that makes all these recently uploaded rust packages to FTBFS: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rust-arc-swap.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rust-encoding.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rust-encode-unicode.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rust-crossbeam-epoch-0.5.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rust-gobject-sys.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rust-grep-regex.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rust-heck.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rust-iso8601.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rust-mio-uds.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rust-rustc-version.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rust-term.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rust-stringprep.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rust-string-cache-codegen.html Thanks.
Bug#904111: clamav-daemon causing deadlocks/blocking I/O
On 2018-11-08 15:15:57 [-0800], Adam Lambert wrote: > What do you need me to do to provide debug info on this? I would like to reproduce this. I would need the clamd.conf, kernel command line if something non-standard and what it is you do. If I can reproduce this on my Stretch VM then I try to forward this upstream or look myself. > Thanks, Sebastian
Bug#913143: Bug #913143 in samba marked as pending
Control: tag -1 pending Hello, Bug #913143 in samba 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/samba-team/samba/commit/8c1bd98589587e22e28c2195d7eca2c08c1c2b82 d/rules: Replace override_dh_perl by override_dh_perl-arch (Closes: #913143) (this message was generated automatically) -- Greetings https://bugs.debian.org/913143
Processed: Bug #913143 in samba marked as pending
Processing control commands: > tag -1 pending Bug #913143 [src:samba] samba: FTBFS when built with dpkg-buildpackage -A Added tag(s) pending. -- 913143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913143 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#912393: marked as done (scala FTBFS with OpenJDK 11)
Your message dated Sat, 10 Nov 2018 19:34:13 + with message-id and subject line Bug#912393: fixed in scala 2.11.12-3 has caused the Debian Bug report #912393, regarding scala FTBFS with OpenJDK 11 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.) -- 912393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912393 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: scala Version: 2.11.12-2 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/scala.html ... locker.reflect: [mkdir] Created dir: /build/1st/scala-2.11.12/build/locker/classes/reflect [javac] Using javac -source 1.5 is no longer supported, switching to 6 [locker.reflect] Compiling 158 files to /build/1st/scala-2.11.12/build/locker/classes/reflect [locker.reflect] /build/1st/scala-2.11.12/src/reflect/scala/reflect/internal/util/StringOps.scala:48: error: missing argument list for method trimTrailingSpace in trait StringOps [locker.reflect] Unapplied methods are only converted to functions when a function type is expected. [locker.reflect] You can make this conversion explicit by writing `trimTrailingSpace _` or `trimTrailingSpace(_)` instead of `trimTrailingSpace`. [locker.reflect] def trimAllTrailingSpace(s: String): String = s.lines map trimTrailingSpace mkString EOL [locker.reflect] ^ [locker.reflect] one error found --- End Message --- --- Begin Message --- Source: scala Source-Version: 2.11.12-3 We believe that the bug you reported is fixed in the latest version of scala, 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 912...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated scala package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 10 Nov 2018 16:14:38 +0100 Source: scala Binary: scala scala-library scala-doc Architecture: source Version: 2.11.12-3 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Markus Koschany Description: scala - Scala programming language scala-doc - Scala API documentation scala-library - Scala standard library Closes: 912393 Changes: scala (2.11.12-3) unstable; urgency=medium . * Team upload. . [ Markus Koschany ] * Add 0017-bug912393.patch and fix several compilation errors. (Closes: #912393) * Declare compliance with Debian Policy 4.2.1. . [ Emmanuel Bourg ] * Depend on scala (>= 2.11.12) to build with Java 9 Checksums-Sha1: bf15359d76155c0b1d1eb540a043844f3f718df4 2445 scala_2.11.12-3.dsc c31ea3a52463d527f4dd306dd7cb627fb5e1ee70 27184 scala_2.11.12-3.debian.tar.xz 2c5d839c0f8346a8073240dc11a72b1f012e2fd3 13231 scala_2.11.12-3_source.buildinfo Checksums-Sha256: dd22355ee7055ed4d8712a7a477c77ffece4f154031336dcd1832b28203c0b3b 2445 scala_2.11.12-3.dsc a62192f00b747adc008ef387b8e0c7d12883a359e8b2fff86be96a624d9ca5c8 27184 scala_2.11.12-3.debian.tar.xz c4ddb7906c009f2081662d7dd6d3f2997a5bede637360651d970769fb27f2fe5 13231 scala_2.11.12-3_source.buildinfo Files: ce8f6e5b4fd7af0167c02f5ac0aa06cd 2445 devel optional scala_2.11.12-3.dsc 0b8e984c9ceb2fa92141d3ec409cbf5f 27184 devel optional scala_2.11.12-3.debian.tar.xz 2db5f947b9f4a399a54c768ab484b899 13231 devel optional scala_2.11.12-3_source.buildinfo -BEGIN PGP SIGNATURE- iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAlvnLUpfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp YW4ub3JnAAoJENmtFLlRO1HkjSgQAK30w7U7CVSy6pmpX3SQ6YNQ82tVMXR7JOjv QB6v/2jkIw7TpS4hgqzk0im73iYWOWPnPKyx9LVLlJ1408TUuf1w9y2ySLvisiQQ FBDSKQnJSgW8atcBy3BeEX/pfE52uH9cf7EMSkQnj2+aEJ53PEG+yUY/ZYmRfFAx rVEU1Z6wGaWQg47Mh9jLOKh1U6a61fAzY2270uwe1mYVJf+qr+3V3KH94IneVawZ yw4sb6Q2TCSa3YjldDUp853tqBB001i+QDD9a1saA+jVR1J4oJz6O98jh/EEp9ec 458s/XB0RwCx3y/zNaS3Diwaly2DsdixXKvrIvoEdmyU52YSfldHu+np/XcpDU6Q IrIYk8GHiqP01cb+2kNISbboy/qfWnGrhiQJAmtA225o/4t0yq3ywDQsfhJzVAdU +ofLjXUiium1Z+UvryDTkzGKB/VLEI33rQDxFKDTe3O8nFWVzYL2EIym6M8B8l/F
Processed: Bug #912393 in scala marked as pending
Processing control commands: > tag -1 pending Bug #912393 [src:scala] scala FTBFS with OpenJDK 11 Added tag(s) pending. -- 912393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912393 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#913271: segfault - broken rust compiling
On Thu, Nov 08, 2018 at 09:29:43PM +0100, Sylvestre Ledru wrote: > Do you have more info than "it segfaults"? I can provide some reproduction steps, if that's helpful. 1. Install rustc and cargo. 2. git clone https://github.com/rust-lang-nursery/rust-clippy.git 3. cd rust-clippy 4. git checkout v0.0.212 5. cargo build --verbose 6. Notice build failures due to SIGSEGV. Note that if instead you compile with "cargo build --verbose --release" in step 5, you get #913414. rustc did work as recently as November 3, since a project of mine that exhibits the same behavior has that as its most recent commit. -- brian m. carlson: Houston, Texas, US OpenPGP: https://keybase.io/bk2204 signature.asc Description: PGP signature
Bug#912393: Bug #912393 in scala marked as pending
Control: tag -1 pending Hello, Bug #912393 in scala reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at: https://salsa.debian.org/java-team/scala/commit/c5097346ea5ded7175e6c37e7a898f61db18908d Add 0017-trimTrailingSpace.patch and fix the FTBFS in StringOps.scala. Closes: #912393 (this message was generated automatically) -- Greetings https://bugs.debian.org/912393
Processed: Re: Bug#913409: libasound2: plugging in RME ADI2-DAC causes pulseaudio to crash in libasound2
Processing control commands: > reassign -1 libasound2-plugins 1.1.7-2 Bug #913409 [libasound2] libasound2: plugging in RME ADI2-DAC causes pulseaudio to crash in libasound2 Bug reassigned from package 'libasound2' to 'libasound2-plugins'. No longer marked as found in versions alsa-lib/1.1.7-1. Ignoring request to alter fixed versions of bug #913409 to the same values previously set Bug #913409 [libasound2-plugins] libasound2: plugging in RME ADI2-DAC causes pulseaudio to crash in libasound2 Marked as found in versions alsa-plugins/1.1.7-2. > forcemerge 912921 -1 Bug #912921 [libasound2-plugins] libasound2-plugins: Crashes pulseaudio Bug #913071 [libasound2-plugins] libasound2: pulseaudio segfault when plugging USB card Bug #913409 [libasound2-plugins] libasound2: plugging in RME ADI2-DAC causes pulseaudio to crash in libasound2 Severity set to 'important' from 'grave' Marked as fixed in versions alsa-plugins/1.1.6-1. Added tag(s) pending. Bug #913071 [libasound2-plugins] libasound2: pulseaudio segfault when plugging USB card Merged 912921 913071 913409 -- 912921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912921 913071: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913071 913409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913409 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#913409: libasound2: plugging in RME ADI2-DAC causes pulseaudio to crash in libasound2
Control: reassign -1 libasound2-plugins 1.1.7-2 Control: forcemerge 912921 -1 * Florin Iucha [2018-11-10 12:12 -0500]: > Package: libasound2 > Version: 1.1.7-1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > >* What led up to the situation? > >Purchased a new USB DAC. It worked fine last night, then this morning >it is crashing pulseaudio every time it is attached / turned on. > >* What exactly did you do (or not do) that was effective (or > ineffective)? > >Plug the USB DAC. > >* What was the outcome of this action? > >Nov 10 12:03:07 herakles kernel: do_general_protection: 10 callbacks > suppressed >Nov 10 12:03:07 herakles kernel: traps: pulseaudio[6311] general > protection ip:7f8f3e557532 sp:7fff1aa8bb20 error:0 in > libasound.so.2.0.0[7f8f3e51e000+8f000] > >* What outcome did you expect instead? > >Music coming out from the headphones. Please check https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912921 Elimar -- On the keyboard of life you have always to keep a finger at the escape key;-) signature.asc Description: PGP signature
Bug#908678: Testing the filter-branch scripts
Antoine,
thank you very much for your filter-branch scripts.
I tested each:
1) the golang version:
It completes after 3h36min:
# git filter-branch --tree-filter '/split-by-year' HEAD
Rewrite a09118bf0a33f3721c0b8f6880c4cbb1e407a39d (68282/68286) (12994 seconds
passed, remaining 0 predicted)
Ref 'refs/heads/master' was rewritten
But it doesn't Close() the os.OpenFile handles so ...
all data/CVE/list. files are 0 bytes long. Sic!
I can reproduce that just running the golang executable
against a current checkout of data/CVE/list.
# go version
go version go1.10.3 linux/amd64
(Stretch backport golang-go 2:1.10~5~bpo9+1)
2.1) the Python version
You claim #!/usr/bin/python3 in the shebang, so I tried that first:
# git filter-branch --tree-filter '/usr/bin/python3
/__pycache__/split-by-year.cpython-35.pyc' HEAD
Rewrite 990d3c4bbb49308fb3de1e0e91b9ba5600386f8a (1220/68293) (41 seconds
passed, remaining 2254 predicted)
Traceback (most recent call last):
File "split-by-year.py", line 13, in
File "/usr/lib/python3.5/codecs.py", line 321, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xf6 in position 5463:
invalid start byte
tree filter failed: /usr/bin/python3 /__pycache__/split-by-year.cpython-35.pyc
The offending commit is:
* 990d3c4bbb - Rename sarge-checks data to something not specific to sarge,
since we're working on etch now.
Sorry for the probable annoyance, but it had to be done. (13 years ago) [Joey
Hess]
There will be many more like this, so for Python3
this needs needs to be made unicode-agnostic.
Notice I compiled the .py to .pyc which makes it
much faster and thus well usable.
2.2) Python, when a string was a string .. Python2
Your code is actually Python2, so why not give that a try:
# git filter-branch --tree-filter '/usr/bin/python2 /split-by-year.pyc' HEAD
Rewrite b59da20b82011ffcfa6c4a453de9df58ee036b2c (2516/68293) (113 seconds
passed, remaining 2954 predicted)
Traceback (most recent call last):
File "split-by-year.py", line 18, in
yearly = 'data/CVE/list.{:d}'.format(year)
NameError: name 'year' is not defined
tree filter failed: /usr/bin/python2 /split-by-year.pyc
The offending commit is:
* b59da20b82 - claim (13 years ago) [Moritz Muehlenhoff]
| diff --git a/data/CVE/list b/data/CVE/list
| index 7b5d1d21d6..cdf0b74dd0 100644
| --- a/data/CVE/list
| +++ b/data/CVE/list
| @@ -1,3 +1,4 @@
| +begin claimed by jmm
| CVE-2005-3276 (The sys_get_thread_area function in process.c in Linux 2.6
before ...)
| TODO: check
| CVE-2005-3275 (The NAT code (1) ip_nat_proto_tcp.c and (2)
ip_nat_proto_udp.c in ...)
| @@ -34,6 +35,7 @@ CVE-2005-3260 (Multiple cross-site scripting (XSS)
vulnerabilities in ...)
| TODO: check
| CVE-2005-3259 (Multiple SQL injection vulnerabilities in
versatileBulletinBoard (vBB) ...)
| TODO: check
| +end claimed by jmm
| CVE-2005- [Insecure caching of user id in mantis]
| - mantis (bug #330682; unknown)
| CVE-2005- [Filter information disclosure in mantis]
As you see the line "+begin claimed by jmm" breaks the too simplistic parser
logic.
Unfortunately dry-running against a current version of data/CVE/list such
errors do not show up.
The "violations" of the file format are transient and buried in history.
Best,
Daniel
Bug#912181: Fixed setup.py
Dear Piotr,
I maintain the package "turing", which build-depends on python-jedi.
I found the reason why python-jedi FTBFS: setup.py tries to find out
the package's version by parsing jedi/__init__.py, but the parse tree
was interpreted in two different ways, depending on python's version.
I checked that the right expressions to access the package's version is
always `tree.body[1].value.s` and never `tree.body[0].value.s`, so I
simplified the source code.
Please find attached the patch used by quilt to fix this bug.
In case you have no time to publish a new version of your package, I am
pushing it as a NMU into DELAYED+15.
Best regards, Georges.
--
Georges KHAZNADAR et Jocelyne FOURNIER
22 rue des mouettes, 59240 Dunkerque France.
Téléphone +33 (0)3 28 29 17 70
Cleaned out an alternative to assign the variable 'version' for
the package, which was not accessed in the same way, depending on
Python language's version.
It looked like a non-documented workaround to compensate some weird
behavior of an older version of the module ast.
Index: python-jedi-0.12.0/setup.py
===
--- python-jedi-0.12.0.orig/setup.py
+++ python-jedi-0.12.0/setup.py
@@ -11,10 +11,7 @@ __AUTHOR_EMAIL__ = 'davidhalter88@gmail.
# Get the version from within jedi. It's defined in exactly one place now.
with open('jedi/__init__.py') as f:
tree = ast.parse(f.read())
-if sys.version_info > (3, 7):
-version = tree.body[0].value.s
-else:
-version = tree.body[1].value.s
+version = tree.body[1].value.s
readme = open('README.rst').read() + '\n\n' + open('CHANGELOG.rst').read()
with open('requirements.txt') as f:
signature.asc
Description: PGP signature
Bug#913411: python3-libiio: Fails to build from source: hardcodes py3 versions
Package: python3-libiio Version: 0.15-3 Severity: serious libiio Build-Depends on python3-dev but debian/python3-libiio.install specifies python3.6. On Ubuntu 19.04 "Alpha", the default python3 is now python3.7. That change will be made in Debian very soon so that's why I'm filing this as serious now. I think the usual procedure to fix this is to use a wildcard like python3* instead of a specific version number in the install rules. Also, I think it is preferred for libraries to Build-Depend on python3-all-dev instead of python3-dev so that the package is built for all supported Python3 versions. I believe there is usually only one version, but currently Ubuntu 19.04 supports both 3.6 and 3.7 since the 3.7-only transition hasn't completed yet. The build log showing the build failure can be found at https://launchpad.net/ubuntu/+source/libiio/0.15-4/+build/15640565 Thanks, Jeremy Bicha
Bug#913412: rfkill: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/share/bash-completion/completions/rfkill
Package: rfkill Version: 2.32.1-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 'stable'. It installed fine in 'stable', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces This test intentionally skipped 'testing' to find file overwrite problems before packages migrate from 'unstable' to 'testing'. >From the attached log (scroll to the bottom...): Preparing to unpack .../rfkill_2.32.1-0.2_amd64.deb ... Unpacking rfkill (2.32.1-0.2) ... dpkg: error processing archive /var/cache/apt/archives/rfkill_2.32.1-0.2_amd64.deb (--unpack): trying to overwrite '/usr/share/bash-completion/completions/rfkill', which is also in package bash-completion 1:2.1-4.3 Errors were encountered while processing: /var/cache/apt/archives/rfkill_2.32.1-0.2_amd64.deb cheers, Andreas bash-completion=1%2.1-4.3_rfkill=2.32.1-0.2.log.gz Description: application/gzip
Processed: bug 913406 is forwarded to https://github.com/dtschump/gmic/issues/89
Processing commands for cont...@bugs.debian.org: > forwarded 913406 https://github.com/dtschump/gmic/issues/89 Bug #913406 [cimg-dev,libgmic-dev] cimg-dev,libgmic-dev: both ship /usr/include/CImg.h Set Bug forwarded-to-address to 'https://github.com/dtschump/gmic/issues/89'. > thanks Stopping processing here. Please contact me if you need assistance. -- 913406: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913406 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#913410: texlive-fonts-extra-links: needs version bump in Breaks+Replaces: texlive-fonts-extra
Package: texlive-fonts-extra-links Version: 2018.20181106-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../texlive-fonts-extra-links_2018.20181106-1_all.deb ... Unpacking texlive-fonts-extra-links (2018.20181106-1) ... dpkg: error processing archive /var/cache/apt/archives/texlive-fonts-extra-links_2018.20181106-1_all.deb (--unpack): trying to overwrite '/usr/share/texlive/texmf-dist/fonts/opentype/impallari/cabin/Cabin-Italic.otf', which is also in package texlive-fonts-extra 2018.20181009-1 Errors were encountered while processing: /var/cache/apt/archives/texlive-fonts-extra-links_2018.20181106-1_all.deb cheers, Andreas texlive-fonts-extra=2018.20181009-1_texlive-fonts-extra-links=2018.20181106-1.log.gz Description: application/gzip
Bug#901214: marked as done (libvtkdicom0.8: fails to upgrade from 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/cmake/DICOMConfig.cmake)
Your message dated Sat, 10 Nov 2018 17:24:22 + with message-id and subject line Bug#901214: fixed in vtk-dicom 0.8.7-2 has caused the Debian Bug report #901214, regarding libvtkdicom0.8: fails to upgrade from 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/cmake/DICOMConfig.cmake 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.) -- 901214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901214 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libvtkdicom0.8 Version: 0.8.7-1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package libvtkdicom0.8:amd64. Preparing to unpack .../09-libvtkdicom0.8_0.8.7-1~exp1_amd64.deb ... Unpacking libvtkdicom0.8:amd64 (0.8.7-1~exp1) ... dpkg: error processing archive /tmp/apt-dpkg-install-IbQBLb/09-libvtkdicom0.8_0.8.7-1~exp1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/cmake/DICOMConfig.cmake', which is also in package libvtkdicom0.7:amd64 0.7.10-1+b3 Shouldn't that file rather go into the -dev package? cheers, Andreas libvtkdicom0.7=0.7.10-1+b3_libvtkdicom0.8=0.8.7-1~exp1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: vtk-dicom Source-Version: 0.8.7-2 We believe that the bug you reported is fixed in the latest version of vtk-dicom, 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 901...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gert Wollny (supplier of updated vtk-dicom package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 10 Nov 2018 13:56:45 +0100 Source: vtk-dicom Binary: libvtk-dicom-dev libvtkdicom0.8 vtk-dicom-tools python3-vtk-dicom Architecture: source Version: 0.8.7-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Gert Wollny Description: libvtk-dicom-dev - DICOM for VTK - dev libvtkdicom0.8 - DICOM for VTK - lib python3-vtk-dicom - DICOM for VTK - Python vtk-dicom-tools - DICOM for VTK - tools Closes: 901214 Changes: vtk-dicom (0.8.7-2) unstable; urgency=medium . * d/control: Add break/replace lib package, Closes: #901214 Checksums-Sha1: 7da379df01425834d2142540f6e5919543a562c6 2239 vtk-dicom_0.8.7-2.dsc e8bd9fa0fe2a9d412f0c0b09ad5a46cf297e540b 5748 vtk-dicom_0.8.7-2.debian.tar.xz 07816200bb5c2f630f2dfe415ae9113fdd97ff37 22605 vtk-dicom_0.8.7-2_source.buildinfo Checksums-Sha256: 20efb4208c02b0dfd414b67a1bc98769fb8b031d4216ad96c65573bfc614b10b 2239 vtk-dicom_0.8.7-2.dsc 3c29d4a231e933f870d4940c8174a1540f2d3fbdc7305b03a3601776beef20b0 5748 vtk-dicom_0.8.7-2.debian.tar.xz da07389546998b6889d2855ce6462e7968c57ba70400dca6552a518b99bae602 22605 vtk-dicom_0.8.7-2_source.buildinfo Files: 0d194aa78968574f51af7439386bea01 2239 graphics optional vtk-dicom_0.8.7-2.dsc 9c1f9d7a9b4276fd44b1277f03aa11cf 5748 graphics optional vtk-dicom_0.8.7-2.debian.tar.xz c2ba1aaec1a19e399e89db4041d49c7e 22605 graphics optional vtk-dicom_0.8.7-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEELtRZww6NuKjZPKd6l/LU/KCfME4FAlvnBwsACgkQl/LU/KCf ME5h3Q/+M6SA3I8ur11yMtipKIn80V8NU2KuUM+3Xi6zyNaGGo5xQ17hu1M4PYwT Q7IIqSrDSXHNWHG8aRQviHsDTC6y+uQ+++NmfBVH7j75YcVPro3js3G7mZ8wwvHA CEXVjBAmAA4L8yS3KzZ7sUL6kgm1EQSdVk6/F6v0pVoL9netNo/WnIpsovHzo2C+ 9J5mrhKoffi344hwX8LThiiJOh+Ho/udBivou4j+/UFn2OjJZMv6t9mDe9C1b/Gd iWy9CiF/aBjONtnB3KLisrTF9ONwr+BFgq9u1bwpqTGbI1ydZkffqy6DmPnB+twL btmRFPHknBJ8vfIm+LWkm0zKJk300/sYlSuC1IxjUsChP1dtVShdu95k1VnrAzHk hRf37dTGOo+H2PfR7GVakhUP+1bL+S/xWlgWoiqsPGrbPxfCpT0GX7TpSNLgbXFX wG/N/nWwDk9CCGs1K0f7HGvP1BOL45s5hPdn7i2dPP7w6h7pEuCIuroqfywOUxSA
Bug#913379: marked as done (zurl FTBFS with curl 7.62.0)
Your message dated Sat, 10 Nov 2018 17:24:36 + with message-id and subject line Bug#913379: fixed in zurl 1.9.1-5 has caused the Debian Bug report #913379, regarding zurl FTBFS with curl 7.62.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 913379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913379 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zurl Version: 1.9.1-4 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/zurl.html ... ../httprequest_curl.cpp: In member function 'void HttpRequest::Private::conn_updated()': ../httprequest_curl.cpp:1288:5: error: duplicate case value case CURLE_PEER_FAILED_VERIFICATION: ^~~~ ../httprequest_curl.cpp:1287:5: note: previously used here case CURLE_SSL_CACERT: ^~~~ make[2]: *** [Makefile:750: _obj/httprequest_curl.o] Error 1 For background see https://github.com/curl/curl/commit/3f3b26d6feb0667714902e836af608094235fca2 --- End Message --- --- Begin Message --- Source: zurl Source-Version: 1.9.1-5 We believe that the bug you reported is fixed in the latest version of zurl, 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 913...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jan Niehusmann (supplier of updated zurl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 10 Nov 2018 16:45:16 +0100 Source: zurl Binary: zurl Architecture: source Version: 1.9.1-5 Distribution: unstable Urgency: medium Maintainer: Jan Niehusmann Changed-By: Jan Niehusmann Description: zurl - HTTP client worker with ZeroMQ interface Closes: 913379 Changes: zurl (1.9.1-5) unstable; urgency=medium . * Fix build with libcurl >= 7.62 (Closes: Bug#913379) Checksums-Sha1: 67865a5d71267aaba384ae166a4079df3f90bfc0 1741 zurl_1.9.1-5.dsc 35eda27162e62b7d50aa3eea6e43392eb37fa28d 8744 zurl_1.9.1-5.debian.tar.xz 820afa453a92f1c33720542a5f989979afe4b290 10962 zurl_1.9.1-5_amd64.buildinfo Checksums-Sha256: 97745f4ea79673e0f5d8946ca3c02495194a1eed42a9d93dd92814bd74caf5c5 1741 zurl_1.9.1-5.dsc 8d89d2772f90cf0440c5eae9a6c409b8133430a37aca77b9ae49bc4ba590eea8 8744 zurl_1.9.1-5.debian.tar.xz be2a6c866d8d6b116c4223041261e1b168db21c63fc1271b9478b48dc831abfb 10962 zurl_1.9.1-5_amd64.buildinfo Files: 21ca01b7b22deec0d005a1f9e346a04f 1741 net optional zurl_1.9.1-5.dsc 5be151d7646b889889c349a21a22d0ec 8744 net optional zurl_1.9.1-5.debian.tar.xz eeaac2b9ab0edb2f4367d93e327c6808 10962 net optional zurl_1.9.1-5_amd64.buildinfo -BEGIN PGP SIGNATURE- iQHDBAEBCgAtFiEE+20yASySVog94MmzwkDOmV0CaxEFAlvm/o8PHGphbkBkZWJp YW4ub3JnAAoJEMJAzpldAmsRzIgL/0Vhia4zdwf664FJuOF+V9Vfo+vdcV50rPkY yQjDRU4ODWV4bsfl2N6XsW4PSA43jZm3eoDCGLL9vFOQIDhTXu/tVNuAX1XpSzZQ JRMVEapU96k528uo8o0Lh7oZezPPxvZwP0sFVChu6D0Kpx6B4Y8RxMcEVIzMMYkv ruGpV70MhUEc2/F0NcVS2+zesov4m6u+rKYxWrvljH931OO4n1qP27N5QdCrvfWx pTQ5qmE/oaS23C300QMpx0miIfAobNRBmf9k7O6Y35CHzphKpX45slQiciSrqOUM 6Ld7POt0O6r5qX4HZoO8ufFx+uCYjjYpZu293465p49grytgZNLX8yN+8MiBJDlZ DkCm0l01CNNRk9GjtofAxf0MxSjdDzt+TLkrXVFuKy1mV6cKBdnlwR3+d1uVvZiz 0L4Bw4pc6M5PAlvdOFIl1l7VXdYrmDh1ytujemSybXXDKl4/QjrvNt325bDNtvPe 4KtTYQDgTTCVlF0VmZDOFiZTEIf4Xg== =dTYO -END PGP SIGNATURE End Message ---
Bug#913409: libasound2: plugging in RME ADI2-DAC causes pulseaudio to crash in libasound2
Package: libasound2 Version: 1.1.7-1 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? Purchased a new USB DAC. It worked fine last night, then this morning it is crashing pulseaudio every time it is attached / turned on. * What exactly did you do (or not do) that was effective (or ineffective)? Plug the USB DAC. * What was the outcome of this action? Nov 10 12:03:07 herakles kernel: do_general_protection: 10 callbacks suppressed Nov 10 12:03:07 herakles kernel: traps: pulseaudio[6311] general protection ip:7f8f3e557532 sp:7fff1aa8bb20 error:0 in libasound.so.2.0.0[7f8f3e51e000+8f000] * What outcome did you expect instead? Music coming out from the headphones. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libasound2 depends on: ii libasound2-data 1.1.7-1 ii libc62.27-8 libasound2 recommends no packages. Versions of packages libasound2 suggests: ii libasound2-plugins 1.1.7-2 -- no debconf information
Bug#913408: librust-crossbeam-epoch-0.5-dev: missing Breaks+Replaces: librust-crossbeam-epoch-dev (<< 0.6)
Package: librust-crossbeam-epoch-0.5-dev Version: 0.5.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../librust-crossbeam-epoch-0.5-dev_0.5.2-1_amd64.deb ... Unpacking librust-crossbeam-epoch-0.5-dev:amd64 (0.5.2-1) ... dpkg: error processing archive /var/cache/apt/archives/librust-crossbeam-epoch-0.5-dev_0.5.2-1_amd64.deb (--unpack): trying to overwrite '/usr/share/cargo/registry/crossbeam-epoch-0.5.2/.cargo-checksum.json', which is also in package librust-crossbeam-epoch-dev:amd64 0.5.2-1 Errors were encountered while processing: /var/cache/apt/archives/librust-crossbeam-epoch-0.5-dev_0.5.2-1_amd64.deb cheers, Andreas librust-crossbeam-epoch-dev=0.5.2-1_librust-crossbeam-epoch-0.5-dev=0.5.2-1.log.gz Description: application/gzip
Processed: tagging 912445, found 912916 in 5.1.45-1, tagging 912142
Processing commands for cont...@bugs.debian.org:
> tags 912445 + experimental
Bug #912445 {Done: Adrian Bunk }
[src:openhft-chronicle-threads] openhft-chronicle-threads: FTBFS with Java 11
due to JAXWS removal
Added tag(s) experimental.
> found 912916 5.1.45-1
Bug #912916 [mysql-connector-java] mysql-connector-java: removal from Debian
There is no source info for the package 'mysql-connector-java' at version
'5.1.45-1' with architecture ''
Unable to make a source version for version '5.1.45-1'
Marked as found in versions 5.1.45-1.
> tags 912142 + sid buster
Bug #912142 [src:ruby-capybara-screenshot] ruby-capybara-screenshot FTBFS: test
failure
Added tag(s) sid and buster.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
912142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912142
912445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912445
912916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912916
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#913407: libsword-1.8.1: missing Breaks+Replaces: libsword11v5 (>= 1.8)
Package: libsword-1.8.1 Version: 1.8.1+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libsword-1.8.1_1.8.1+dfsg-1_amd64.deb ... Unpacking libsword-1.8.1:amd64 (1.8.1+dfsg-1) ... dpkg: error processing archive /var/cache/apt/archives/libsword-1.8.1_1.8.1+dfsg-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libsword-1.8.1.so', which is also in package libsword11v5:amd64 1.8.1-3 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libsword-1.8.1_1.8.1+dfsg-1_amd64.deb Yes, I really mean (greater-or-equal 1.8), since the package is co-installable with libsword11v5 (1.7.3+dfsg-9+b2) in stable. cheers, Andreas libsword11v5=1.8.1-3_libsword-1.8.1=1.8.1+dfsg-1.log.gz Description: application/gzip
Processed: cimg-dev,libgmic-dev: both ship /usr/include/CImg.h
Processing control commands: > found -1 2.4.1-2 Bug #913406 [cimg-dev,libgmic-dev] cimg-dev,libgmic-dev: both ship /usr/include/CImg.h There is no source info for the package 'cimg-dev' at version '2.4.1-2' with architecture '' Marked as found in versions gmic/2.4.1-2. > found -1 2.3.6+dfsg-1 Bug #913406 [cimg-dev,libgmic-dev] cimg-dev,libgmic-dev: both ship /usr/include/CImg.h There is no source info for the package 'libgmic-dev' at version '2.3.6+dfsg-1' with architecture '' Marked as found in versions cimg/2.3.6+dfsg-1. -- 913406: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913406 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#913406: cimg-dev,libgmic-dev: both ship /usr/include/CImg.h
Package: cimg-dev,libgmic-dev Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: found -1 2.4.1-2 Control: found -1 2.3.6+dfsg-1 Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Selecting previously unselected package libgmic-dev. Preparing to unpack .../5-libgmic-dev_2.4.1-2_amd64.deb ... Unpacking libgmic-dev (2.4.1-2) ... dpkg: error processing archive /tmp/apt-dpkg-install-gHJoKE/5-libgmic-dev_2.4.1-2_amd64.deb (--unpack): trying to overwrite '/usr/include/CImg.h', which is also in package cimg-dev 2.3.6+dfsg-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /tmp/apt-dpkg-install-gHJoKE/5-libgmic-dev_2.4.1-2_amd64.deb Adding Breaks/Replaces/Conflicts is probably not the correct solution in this case. cheers, Andreas cimg-dev=2.3.6+dfsg-1_libgmic-dev=2.4.1-2.log.gz Description: application/gzip
Bug#911944: neovim FTBFS: tests fail
Hi James, On Sat, Nov 10, 2018 at 09:29:42AM -0500, James McCoy wrote: > On Fri, Oct 26, 2018 at 03:30:54PM +0200, Helmut Grohne wrote: > > neovim fails to build from source in unstable. > > > > | [ ERROR ] 6 errors, listed below: > > | [ ERROR ] test/functional/helpers.lua @ 743: after_each > > | test/helpers.lua:289: crash detected (see above) > > | > > | stack traceback: > > | test/helpers.lua:289: in function 'check_cores' > > | test/functional/helpers.lua:748: in function > > > > I haven't seen these on the buidds or locally. The only issue I've been > seeing, aside from some flaky tests, I've filed upstream[0]: > > [ RUN ] mbyte utf_char2bytes: FAIL > test/unit/helpers.lua:731: (string) ' > not enough memory' > > stack traceback: > test/unit/helpers.lua:747: in function 'itp_parent' > test/unit/helpers.lua:774: in function > > [0]: https://github.com/neovim/neovim/issues/9212 Thank you for looking into this. I've no clue what the error is supposed to mean either. In any case, I just retried and I can still reliably reproduce the failure. > > Looking to reproducible builds, the failure pattern looks quite random: > > > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/neovim.html > > I'm not actually sure what's happening in the most recent builds there. > I don't see any explicit error output, just the testing stopping earlier > than it should. That looks quite different now. Earlier, I've seen the same errors there. > The armhf & ppc64el buildd failures I can't reproduce on the > porterboxes, although the latter is likely another flaky test. armhf likely needs to be retried as the build timed out. > > However, in local builds for unstable/amd64 in sbuild, I didn't get a > > single successful build. > > If it's not any of the mentioned failures, then some more information > would be useful, as I have quite the opposite behavior locally. What information are you interested in? I also tried in pbuilder and there I only got the utf_char2bytes failure, not the ones with check_cores. This hints that something about my build environment is fishy. If I understand correctly, my user's resource limits "leak" through sbuild while they don't pass through pbuilder. Would limiting the number of processes or virtual memory be a plausible explanation for the failures? So it might be useful to reduce the scope of this bug to the utf_char2bytes failure and the armhf/ppc64el buildd failures. Helmut
Bug#901214: Bug #901214 in vtk-dicom marked as pending
Control: tag -1 pending Hello, Bug #901214 in vtk-dicom 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/med-team/vtk-dicom/commit/0bdaa3eb4f19f0bdc8d8382eb3954f18cbf8dfc5 d/control: Add break/replace lib package, Closes: #901214 (this message was generated automatically) -- Greetings https://bugs.debian.org/901214
Processed: Bug #901214 in vtk-dicom marked as pending
Processing control commands: > tag -1 pending Bug #901214 [libvtkdicom0.8] libvtkdicom0.8: fails to upgrade from 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/cmake/DICOMConfig.cmake Added tag(s) pending. -- 901214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901214 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#911754: undefined symbol: _D7gobject7ObjectGQi5dorefMFZCQBcQxQz
On Sat, Nov 10, 2018 at 16:02:51 +0100, Matthias Klumpp wrote: > If a dependency gets rebuilt, but the reverse dependency didn't (like > with libglibd and appstream-generator here), this issue can happen. > Because of that, the new LDC releases have their newer standard > library package conflict with the previous version now, so people > won't install an uninstallable configuration. > Since the first rebuild here failed though due to an unrelated bug in > Meson, LDC got more releases in the meantime, dropping this Conflicts > safeguard, which caused this issue. > > Not great, but dealing with unstable ABIs unfortunately leads to these > issues (unless you go the Go route and recompile everything, or go the > Haskell route and make a more complicated system of dependencies). > The good news is that this issue shouldn't happen again (or would be > rather rare, as it requires a package to FTBFS due to a dependency > that is unrelated to the LDC ABI transition). > That sounds like it'll break partial upgrades. If ABIs are unstable then that needs to be reflected in package dependencies. Cheers, Julien
Bug#913366: [Pkg-privacy-maintainers] Bug#913366: torbrowser-launcher: more apparmor fixes needed, otherwise fails to launch
control: severity -1 important control: tags -1 +pending On Sat, Nov 10, 2018 at 9:54 AM Diederik de Haas wrote: > > Package: torbrowser-launcher > Version: 0.3.1-1 > Severity: grave > Tags: upstream patch > Justification: renders package unusable Thanks for your report! However this is not grave level, IMHO. I think important should be proper. > I had applied the patch before, but I guess it got overwritten with a > new version (which I thought wasn't supposed to happen without asking). > Applied the patch again and then torbrowser started again. > > For completeness sake, this is the patch intrigeri submitted upstream, > but the upstream pull request is now already waiting more then a month > for approval/merge, so it's probably good to apply this patch to the > Debian package in the meantime. It'd be included in next upload. Thanks! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Processed: Re: [Pkg-privacy-maintainers] Bug#913366: torbrowser-launcher: more apparmor fixes needed, otherwise fails to launch
Processing control commands: > severity -1 important Bug #913366 [torbrowser-launcher] torbrowser-launcher: more apparmor fixes needed, otherwise fails to launch Severity set to 'important' from 'grave' > tags -1 +pending Bug #913366 [torbrowser-launcher] torbrowser-launcher: more apparmor fixes needed, otherwise fails to launch Added tag(s) pending. -- 913366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913366 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: [Piuparts-devel] Bug#913400: piuparts: dirname part contains a symlink
Processing control commands: > severity -1 serious Bug #913400 [src:piuparts] piuparts: dirname part contains a symlink Severity set to 'serious' from 'normal' > reassign -1 libc++-7-dev,libc++-8-dev Bug #913400 [src:piuparts] piuparts: dirname part contains a symlink Bug reassigned from package 'src:piuparts' to 'libc++-7-dev,libc++-8-dev'. Ignoring request to alter found versions of bug #913400 to the same values previously set Ignoring request to alter fixed versions of bug #913400 to the same values previously set -- 913400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913400 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#858938: fixed in kopete 4:18.04.1-1
On Sat, Nov 10, 2018 at 03:48:37PM +0100, Pino Toscano wrote: > In data sabato 10 novembre 2018 13:30:19 CET, Kurt Roeckx ha scritto: > > On Sun, Oct 28, 2018 at 11:29:43PM +0100, Sebastian Andrzej Siewior wrote: > > > On 2018-10-21 12:31:45 [+0200], Kurt Roeckx wrote: > > > > On Tue, Sep 25, 2018 at 11:29:28PM +0200, Sebastian Andrzej Siewior > > > > wrote: > > > > > On 2018-08-25 10:33:54 [+0200], Kurt Roeckx wrote: > > > > > > On Fri, Jun 01, 2018 at 11:22:09AM +, Sandro Knauß wrote: > > > > > > > Source: kopete > > > > > > > Source-Version: 4:18.04.1-1 > > > > > > > > > > > > > > We believe that the bug you reported is fixed in the latest > > > > > > > version of > > > > > > > kopete, which is due to be installed in the Debian FTP archive. > > > > > > > > > > > > Any plans to upload this to unstable? > > > > > > > > > > There are just two packages left in testing which use openssl1.0. The > > > > > last kopete upload was in mid June. Is there anything blocking an > > > > > upload > > > > > to unstable? > > > > > > > > The other one just got fixed in unstable, so this will soon be the > > > > only package in testing still depending on libssl1.0.2. > > > > > > kopete is the only package in testing still using libssl1.0.2. Could > > > someone please comment on this? > > > > This is in experimental for more than 5 months now. > > > > If nobody replies to this, I will upload an NMU to unstable. > > NMU *what*? Because if you upload the version in experimental to > unstable, then you are effectively taking its maintainership. > The version in experimental is *NOT* ready for unstable/testing, > otherwise I would have uploaded it long ago. And you could have answered this months ago that it was not ready, or that you prefer to fix this the version in unstable instead, or whatever. > > OTOH, this kind of non-helping attitude for you openssl guys (for > example not helping fixing these porting bugs, constant useless poking, > breakage of openssl 1.1 in unstable) certainly does not help. > If you want cooperation, then be ccoperative yourself, instead of just > expecting others to follow whatever you do. > If you need help with something, please ask. Just as you, we're busy with various things, submitting patches for various packages. This bug got closed, so as far as we know you don't need help. Kurt
Bug#913163: (Security) bugs in pdns in stretch
Hi everyone, thanks for reporting bugs against pdns in stretch. I intend to upload a new version to stretch to fix those bugs, but I cannot test all involved components personally. Please give this version a shot: https://people.debian.org/~zeha/pdns/source/ For your convenience, amd64 binaries are here: https://people.debian.org/~zeha/pdns/amd64/ Security team: if you want to do a separate DSA for stretch for CVE-2018-10851 please say so :-) Thanks, Chris
Processed: Re: Bug#911708: scikit-learn breaks astroml autopkgtest: ImportError: cannot import name 'GMM'
Processing control commands: > found -1 0.3-7 Bug #911708 [src:astroml] scikit-learn breaks astroml autopkgtest: ImportError: cannot import name 'GMM' Marked as found in versions astroml/0.3-7. > tags -1 ftbfs Bug #911708 [src:astroml] scikit-learn breaks astroml autopkgtest: ImportError: cannot import name 'GMM' Added tag(s) ftbfs. > severity -1 serious Bug #911708 [src:astroml] scikit-learn breaks astroml autopkgtest: ImportError: cannot import name 'GMM' Severity set to 'serious' from 'normal' -- 911708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911708 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#913405: seafile-gui: Undefined symbol error in seafile-applet
Package: seafile-gui Version: 6.1.8-1 Severity: grave Justification: renders package unusable Dear Maintainer, When I run seafile-applet, instead of launching successfully, I get the following error: seafile-applet: symbol lookup error: seafile-applet: undefined symbol: seafile_checkout_task_get_type If you need any more information, please let me know. Regards, Tom Mason -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-2-amd64 (SMP w/6 CPU cores) Locale: LANG=en_IE.utf8, LC_CTYPE=en_IE.utf8 (charmap=UTF-8), LANGUAGE=en_IE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages seafile-gui depends on: ii ccnet 6.1.8-1 ii libc6 2.27-8 ii libccnet0 6.1.8-1 ii libevent-2.1-6 2.1.8-stable-4 ii libgcc1 1:8.2.0-9 ii libglib2.0-02.58.1-2 ii libjansson4 2.11-1 ii libqt5core5a5.11.2+dfsg-4 ii libqt5dbus5 5.11.2+dfsg-4 ii libqt5gui5 5.11.2+dfsg-4 ii libqt5network5 5.11.2+dfsg-4 ii libqt5webkit5 5.212.0~alpha2-17 ii libqt5widgets5 5.11.2+dfsg-4 ii libquazip5-10.7.6-1 ii libseafile0 6.2.5-2 ii libsearpc1 3.1.0-1 ii libsqlite3-03.25.2-1 ii libssl1.1 1.1.1-2 ii libstdc++6 8.2.0-9 ii seafile-daemon 6.2.5-2 seafile-gui recommends no packages. Versions of packages seafile-gui suggests: pn seafile-cli -- no debconf information
Processed: closing 909957
Processing commands for cont...@bugs.debian.org: > close 909957 9.25~dfsg-0+deb9u1 Bug #909957 [ghostscript] Regression in ghostscript when using pstoedit (/undefined in --setpagedevice--) There is no source info for the package 'ghostscript' at version '9.25~dfsg-0+deb9u1' with architecture '' Unable to make a source version for version '9.25~dfsg-0+deb9u1' Marked as fixed in versions 9.25~dfsg-0+deb9u1. Bug #909957 [ghostscript] Regression in ghostscript when using pstoedit (/undefined in --setpagedevice--) Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 909957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909957 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#913404: ruby-curb FTBFS with curl 7.62.0
Source: ruby-curb Version: 0.9.6-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-curb.html ... curb_errors.c: In function 'rb_curl_easy_error': curb_errors.c:337:5: error: duplicate case value case CURLE_SSL_CACERT: /* 60 - problem with the CA cert (path?) */ ^~~~ curb_errors.c:310:5: note: previously used here case CURLE_SSL_PEER_CERTIFICATE:/* 51 - peer's certificate wasn't ok */ ^~~~ make[1]: *** [Makefile:243: curb_errors.o] Error 1 For background see https://github.com/curl/curl/commit/3f3b26d6feb0667714902e836af608094235fca2
Bug#913403: sssd FTBFS with curl 7.62.0
Source: sssd Version: 1.16.3-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=sssd=sid ... ../src/util/tev_curl.c: In function 'curl_code2errno': ../src/util/tev_curl.c:113:5: error: duplicate case value case CURLE_PEER_FAILED_VERIFICATION: ^~~~ ../src/util/tev_curl.c:100:5: note: previously used here case CURLE_SSL_CACERT: ^~~~ make[3]: *** [Makefile:32438: src/util/tcurl_test_tool-tev_curl.o] Error 1 For background see https://github.com/curl/curl/commit/3f3b26d6feb0667714902e836af608094235fca2
Processed: severity of 913359 is serious
Processing commands for cont...@bugs.debian.org: > severity 913359 serious Bug #913359 [x11-xkb-utils] xkbcomp.pc requires libxkbfile-dev as dependency Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 913359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 913371
Processing commands for cont...@bugs.debian.org: > tags 913371 + ftbfs Bug #913371 [src:gnat-gps] gnat-gps fails to build on 32-bit kernels, address space exhaustion. Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 913371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913371 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 913371 is serious
Processing commands for cont...@bugs.debian.org: > severity 913371 serious Bug #913371 [src:gnat-gps] gnat-gps fails to build on 32-bit kernels, address space exhaustion. Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 913371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913371 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#911754: undefined symbol: _D7gobject7ObjectGQi5dorefMFZCQBcQxQz
Am Sa., 10. Nov. 2018 um 15:25 Uhr schrieb Julien Cristau : > > On Wed, Oct 24, 2018 at 12:50:28 +0200, Matthias Klumpp wrote: > > > Am Mi., 24. Okt. 2018 um 12:45 Uhr schrieb Andrey Rahmatullin > > : > > > > > > Package: appstream-generator > > > Version: 0.7.4-1 > > > Severity: grave > > > > > > I've just installed appstream-generator and ran it: > > > > > > $ appstream-generator > > > appstream-generator: symbol lookup error: appstream-generator: undefined > > > symbol: _D7gobject7ObjectGQi5dorefMFZCQBcQxQz > > > > > > So it's either underlinked or some dependency dropped that symbol without > > > bumping the soname, in which case please reassign the bug accordingly. > > > > This is because the package wasn't properly rebuilt with the latest > > LDC release in the last LDC transition. > > A simple package rebuild should fix this issue. > > > > There is another LDC transition pending, which starts when LDC clears > > NEW, I'll merge this issue with the transition bug then. > > > Package dependencies should prevent silent breakage like this, though? If a dependency gets rebuilt, but the reverse dependency didn't (like with libglibd and appstream-generator here), this issue can happen. Because of that, the new LDC releases have their newer standard library package conflict with the previous version now, so people won't install an uninstallable configuration. Since the first rebuild here failed though due to an unrelated bug in Meson, LDC got more releases in the meantime, dropping this Conflicts safeguard, which caused this issue. Not great, but dealing with unstable ABIs unfortunately leads to these issues (unless you go the Go route and recompile everything, or go the Haskell route and make a more complicated system of dependencies). The good news is that this issue shouldn't happen again (or would be rather rare, as it requires a package to FTBFS due to a dependency that is unrelated to the LDC ABI transition). Cheers, Matthias -- I welcome VSRE emails. See http://vsre.info/
Bug#913402: tomcat8 FTBFS: error: incompatible types: Object cannot be converted
Source: tomcat8 Version: 8.5.34-1 Severity: serious Tags: ftbfs Some recent change in unstable makes tomcat8 FTBFS: https://tests.reproducible-builds.org/debian/history/tomcat8.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/tomcat8.html https://buildd.debian.org/status/fetch.php?pkg=tomcat8=all=8.5.35-1=1541722000=0 ... test-compile: [mkdir] Created dir: /<>/output/testclasses [javac] Compiling 499 source files to /<>/output/testclasses [javac] Ignoring source, target and bootclasspath as release has been set [javac] /<>/test/org/apache/catalina/valves/TestCrawlerSessionManagerValve.java:43: error: incompatible types: Object cannot be converted to Valve [javac] valve.setNext(EasyMock.createMock(Valve.class)); [javac] ^ [javac] /<>/test/org/apache/catalina/valves/TestCrawlerSessionManagerValve.java:49: error: incompatible types: Object cannot be converted to Response [javac] valve.invoke(request, EasyMock.createMock(Response.class)); [javac] ^ [javac] /<>/test/org/apache/catalina/valves/TestCrawlerSessionManagerValve.java:59: error: incompatible types: Object cannot be converted to Valve [javac] valve.setNext(EasyMock.createMock(Valve.class)); [javac] ^ [javac] /<>/test/org/apache/catalina/valves/TestCrawlerSessionManagerValve.java:65: error: incompatible types: Object cannot be converted to Response [javac] valve.invoke(request, EasyMock.createMock(Response.class)); [javac] ^ [javac] /<>/test/org/apache/catalina/valves/TestCrawlerSessionManagerValve.java:76: error: incompatible types: Object cannot be converted to Valve [javac] valve.setNext(EasyMock.createMock(Valve.class)); [javac] ^ [javac] /<>/test/org/apache/catalina/valves/TestCrawlerSessionManagerValve.java:90: error: incompatible types: Object cannot be converted to Response [javac] valve.invoke(request, EasyMock.createMock(Response.class)); [javac] ^ [javac] /<>/test/org/apache/catalina/valves/TestSSLValve.java:39: error: incompatible types: Object cannot be converted to Connector [javac] setConnector(EasyMock.createMock(Connector.class)); [javac] ^ [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. [javac] Note: Some messages have been simplified; recompile with -Xdiags:verbose to get full output [javac] 7 errors BUILD FAILED /<>/build.xml:1350: Compile failed; see the compiler error output for details. Total time: 9 seconds make[1]: *** [debian/rules:36: override_dh_auto_test] Error 1
Bug#858938: fixed in kopete 4:18.04.1-1
In data sabato 10 novembre 2018 13:30:19 CET, Kurt Roeckx ha scritto: > On Sun, Oct 28, 2018 at 11:29:43PM +0100, Sebastian Andrzej Siewior wrote: > > On 2018-10-21 12:31:45 [+0200], Kurt Roeckx wrote: > > > On Tue, Sep 25, 2018 at 11:29:28PM +0200, Sebastian Andrzej Siewior wrote: > > > > On 2018-08-25 10:33:54 [+0200], Kurt Roeckx wrote: > > > > > On Fri, Jun 01, 2018 at 11:22:09AM +, Sandro Knauß wrote: > > > > > > Source: kopete > > > > > > Source-Version: 4:18.04.1-1 > > > > > > > > > > > > We believe that the bug you reported is fixed in the latest version > > > > > > of > > > > > > kopete, which is due to be installed in the Debian FTP archive. > > > > > > > > > > Any plans to upload this to unstable? > > > > > > > > There are just two packages left in testing which use openssl1.0. The > > > > last kopete upload was in mid June. Is there anything blocking an upload > > > > to unstable? > > > > > > The other one just got fixed in unstable, so this will soon be the > > > only package in testing still depending on libssl1.0.2. > > > > kopete is the only package in testing still using libssl1.0.2. Could > > someone please comment on this? > > This is in experimental for more than 5 months now. > > If nobody replies to this, I will upload an NMU to unstable. NMU *what*? Because if you upload the version in experimental to unstable, then you are effectively taking its maintainership. The version in experimental is *NOT* ready for unstable/testing, otherwise I would have uploaded it long ago. I cannot work on it today, maybe tomorrow. OTOH, this kind of non-helping attitude for you openssl guys (for example not helping fixing these porting bugs, constant useless poking, breakage of openssl 1.1 in unstable) certainly does not help. If you want cooperation, then be ccoperative yourself, instead of just expecting others to follow whatever you do. -- Pino Toscano signature.asc Description: This is a digitally signed message part.
Bug#893861: thawab: Intent to remove from Debian
There is an upstream patch. Please delay for one more week. On Sun, Nov 04, 2018 at 06:50:22AM -0500, Jeremy Bicha wrote: > There has been a lot of progress recently on packaging a newer eclipse > that won't require the old webkitgtk. > > I'm going to convert this bug into a thawab removal bug in a week > unless I hear otherwise from you. > > I'm sorry for the inconvenience, but I think it's a bit more polite to > start the removal now rather than waiting until the freezes start when > release team policy won't generally allow "new" packages in to > Testing. > > I did ping upstream again at https://github.com/ojuba-org/thawab/issues/14 > > Thanks, > Jeremy Bicha > ---end quoted text--- -- أحمد المحمودي (Ahmed El-Mahmoudy) Digital design engineer GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7 GPG Fingerprints: 6E2E E4BB 72E2 F417 D066 6ABF 7B30 B496 A7EF 5761 8206 A196 2084 7E6D 0DF8 B176 BC19 6A94 EDDD A1B7 signature.asc Description: PGP signature
Bug#911944: neovim FTBFS: tests fail
On Fri, Oct 26, 2018 at 03:30:54PM +0200, Helmut Grohne wrote: > neovim fails to build from source in unstable. > > | [ ERROR ] 6 errors, listed below: > | [ ERROR ] test/functional/helpers.lua @ 743: after_each > | test/helpers.lua:289: crash detected (see above) > | > | stack traceback: > | test/helpers.lua:289: in function 'check_cores' > | test/functional/helpers.lua:748: in function > I haven't seen these on the buidds or locally. The only issue I've been seeing, aside from some flaky tests, I've filed upstream[0]: [ RUN ] mbyte utf_char2bytes: FAIL test/unit/helpers.lua:731: (string) ' not enough memory' stack traceback: test/unit/helpers.lua:747: in function 'itp_parent' test/unit/helpers.lua:774: in function [0]: https://github.com/neovim/neovim/issues/9212 > Looking to reproducible builds, the failure pattern looks quite random: > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/neovim.html I'm not actually sure what's happening in the most recent builds there. I don't see any explicit error output, just the testing stopping earlier than it should. The armhf & ppc64el buildd failures I can't reproduce on the porterboxes, although the latter is likely another flaky test. > However, in local builds for unstable/amd64 in sbuild, I didn't get a > single successful build. If it's not any of the mentioned failures, then some more information would be useful, as I have quite the opposite behavior locally. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#911754: undefined symbol: _D7gobject7ObjectGQi5dorefMFZCQBcQxQz
On Wed, Oct 24, 2018 at 12:50:28 +0200, Matthias Klumpp wrote: > Am Mi., 24. Okt. 2018 um 12:45 Uhr schrieb Andrey Rahmatullin > : > > > > Package: appstream-generator > > Version: 0.7.4-1 > > Severity: grave > > > > I've just installed appstream-generator and ran it: > > > > $ appstream-generator > > appstream-generator: symbol lookup error: appstream-generator: undefined > > symbol: _D7gobject7ObjectGQi5dorefMFZCQBcQxQz > > > > So it's either underlinked or some dependency dropped that symbol without > > bumping the soname, in which case please reassign the bug accordingly. > > This is because the package wasn't properly rebuilt with the latest > LDC release in the last LDC transition. > A simple package rebuild should fix this issue. > > There is another LDC transition pending, which starts when LDC clears > NEW, I'll merge this issue with the transition bug then. > Package dependencies should prevent silent breakage like this, though? Cheers, Julien
Bug#911754: marked as done (undefined symbol: _D7gobject7ObjectGQi5dorefMFZCQBcQxQz)
Your message dated Sat, 10 Nov 2018 15:19:16 +0100 with message-id and subject line Re: Bug#911754: undefined symbol: _D7gobject7ObjectGQi5dorefMFZCQBcQxQz has caused the Debian Bug report #911754, regarding undefined symbol: _D7gobject7ObjectGQi5dorefMFZCQBcQxQz 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.) -- 911754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911754 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: appstream-generator Version: 0.7.4-1 Severity: grave I've just installed appstream-generator and ran it: $ appstream-generator appstream-generator: symbol lookup error: appstream-generator: undefined symbol: _D7gobject7ObjectGQi5dorefMFZCQBcQxQz So it's either underlinked or some dependency dropped that symbol without bumping the soname, in which case please reassign the bug accordingly. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages appstream-generator depends on: ii libappstream40.12.3-1 ii libarchive13 3.2.2-5 ii libc62.27-6 ii libcairo21.16.0-1 ii libcurl3-gnutls 7.61.0-1 ii libdcontainers0 0.8.0~alpha.9-1 ii libfontconfig1 2.13.1-1 ii libfreetype6 2.8.1-2 ii libgdk-pixbuf2.0-0 2.38.0+dfsg-6 ii libglib2.0-0 2.58.1-2 ii libglibd-2.0-0 2.0.0-1+b1 ii libjs-highlight.js 9.12.0+dfsg1-4 ii libjs-jquery-flot0.8.3+dfsg-1 ii liblmdb0 0.9.22-1 ii libmustache-d0 0.1.3-3+b1 ii libpango-1.0-0 1.42.4-3 ii libphobos2-ldc-shared78 1:1.8.0-3 ii librsvg2-2 2.40.20-3 ii libstdx-allocator0 2.77.2-1 Versions of packages appstream-generator recommends: ii optipng 0.7.6-1.1 appstream-generator suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Hi! The appstream-generator package has finally been rebuilt, so this issue can be closed. Cheers, Matthias--- End Message ---
Bug#911754: undefined symbol: _D7gobject7ObjectGQi5dorefMFZCQBcQxQz
Hi! The appstream-generator package has finally been rebuilt, so this issue can be closed. Cheers, Matthias
Bug#880047: postgrey: Regression - Postgrey doesn't start after installing new stable proposed-update
On 08/11/18 19:34, Adrian Bunk wrote: Tanks a lot for trying stretch-proposed-updates and reproting bugs you find! This is a regression that is also in 1.36-5 in unstable. The proposed 1.36-3+deb9u1 update has now been dropped from the upcoming stretch point release. Thank you for your work on this package. I think the reason my system was badly affected by the new release is because I had used the example unix socket location given in /usr/share/doc/postgrey/README.exim, which conflicted with the new directory created in the init script (although to be fair, the README does warn that the socket location might need to be changed). Regards, Roger
Bug#895513: confirming 895513
Hi, FTR, the issue seems present as well with current sid version for ghoscript (which is on 9.25). Regards, Salvatore
Bug#913397: ucommon FTBFS: new symbols
Source: ucommon Version: 7.0.0-14 Severity: serious Tags: ftbfs Some recent change in unstable makes ucommon FTBFS: https://tests.reproducible-builds.org/debian/history/ucommon.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ucommon.html ... debian/rules override_dh_strip make[1]: Entering directory '/build/1st/ucommon-7.0.0' dh_strip --dbgsym-migration='libucommon8-dbg (<< 7.0.0-7~)' make[1]: Leaving directory '/build/1st/ucommon-7.0.0' dh_makeshlibs dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libucommon8/DEBIAN/symbols doesn't match completely debian/libucommon8.symbols --- debian/libucommon8.symbols (libucommon8_7.0.0-14_amd64) +++ dpkg-gensymbolsLvPJvE 2019-12-13 07:43:27.773789987 -1200 @@ -14,6 +14,8 @@ (c++)"VTT for ost::TTYStream@Base" 7.0.0 (c++)"VTT for ost::ThreadQueue@Base" 7.0.0 (c++)"VTT for ost::ttystream@Base" 7.0.0 + _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_N3ost4Slog5LevelEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE14_M_insert_nodeEPSt18_Rb_tree_node_baseSJ_PSt13_Rb_tree_nodeISB_E@Base 7.0.0-14 + _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_N3ost4Slog5LevelEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE17_M_emplace_uniqueIJS6_IS5_SA_S6_ISt17_Rb_tree_iteratorISB_EbEDpOT_@Base 7.0.0-14 (c++)"non-virtual thunk to ost::AppLog::~AppLog()@Base" 7.0.0 (c++)"non-virtual thunk to ost::SerialService::~SerialService()@Base" 7.0.0 (c++)"non-virtual thunk to ost::SharedMemPager::~SharedMemPager()@Base" 7.0.0 @@ -717,7 +719,7 @@ (c++|optional=templinst)"std::_Rb_tree, std::allocator >, std::pair, std::allocator > const, ost::Slog::Level>, std::_Select1st, std::allocator > const, ost::Slog::Level> >, std::less, std::allocator > >, std::allocator, std::allocator > const, ost::Slog::Level> > >::_M_get_insert_hint_unique_pos(std::_Rb_tree_const_iterator, std::allocator > const, ost::Slog::Level> >, std::__cxx11::basic_string, std::allocator > const&)@Base" 7.0.0 (c++|optional=templinst)"std::_Rb_tree, std::allocator >, std::pair, std::allocator > const, ost::Slog::Level>, std::_Select1st, std::allocator > const, ost::Slog::Level> >, std::less, std::allocator > >, std::allocator, std::allocator > const, ost::Slog::Level> > >::_M_get_insert_unique_pos(std::__cxx11::basic_string, std::allocator > const&)@Base" 7.0.0 (c++|optional=templinst)"std::_Rb_tree, std::allocator >, std::pair, std::allocator > const, ost::Slog::Level>, std::_Select1st, std::allocator > const, ost::Slog::Level> >, std::less, std::allocator > >, std::allocator, std::allocator > const, ost::Slog::Level> > >::find(std::__cxx11::basic_string, std::allocator > const&)@Base" 7.0.0 - (c++|optional)"std::_Rb_tree_iterator > std::_Rb_tree, std::_Select1st >, std::less, std::allocator > >::_M_emplace_hint_unique, std::tuple<> >(std::_Rb_tree_const_iterator >, std::piecewise_construct_t const&, std::tuple&&, std::tuple<>&&)@Base" 7.0.0 +#MISSING: 7.0.0-14# (c++|optional)"std::_Rb_tree_iterator > std::_Rb_tree, std::_Select1st >, std::less, std::allocator > >::_M_emplace_hint_unique, std::tuple<> >(std::_Rb_tree_const_iterator >, std::piecewise_construct_t const&, std::tuple&&, std::tuple<>&&)@Base" 7.0.0 (c++|optional)"std::_Rb_tree_iterator, std::allocator > const, ost::Slog::Level> > std::_Rb_tree, std::allocator >, std::pair, std::allocator > const, ost::Slog::Level>, std::_Select1st, std::allocator > const, ost::Slog::Level> >, std::less, std::allocator > >, std::allocator, std::allocator > const, ost::Slog::Level> > >::_M_emplace_hint_unique, std::allocator > const&>, std::tuple<> >(std::_Rb_tree_const_iterator, std::allocator > const, ost::Slog::Level> >, std::piecewise_construct_t const&, std::tuple, std::allocator > const&>&&, std::tuple<>&&)@Base" 7.0.0 (c++|optional=templinst)"std::__cxx11::basic_stringbuf, std::allocator >::~basic_stringbuf()@Base" 7.0.0 (c++|optional=templinst)"std::ctype::do_widen(char) const@Base" 7.0.0 dh_makeshlibs: failing due to earlier errors make: *** [debian/rules:11: binary] Error 2
Bug#913391: [Parl-devel] Bug#913391: parl-desktop-world: depends on cruft package icedove-bidiui
Control: tags -1 pending Quoting Andreas Beckmann (2018-11-10 13:12:47) > please switch to thunderbird-bidiui, icedove-bidiui is no longer built. Thanks! Preparing that now. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Processed: Re: [Parl-devel] Bug#913391: parl-desktop-world: depends on cruft package icedove-bidiui
Processing control commands: > tags -1 pending Bug #913391 [parl-desktop-world] parl-desktop-world: depends on cruft package icedove-bidiui Added tag(s) pending. -- 913391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913391 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#897658: marked as done (m2crypto: FTBFS against openssl 1.1.1)
Your message dated Sat, 10 Nov 2018 13:17:30 +0100
with message-id <4c08e2fa-9c1f-6118-b583-c99916da7...@danielstender.com>
and subject line m2crypto: FTBFS against openssl 1.1.1
has caused the Debian Bug report #897658,
regarding m2crypto: FTBFS against openssl 1.1.1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
897658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897658
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: m2crypto
Version: 0.27.0-5
Severity: important
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1.1
The new openssl 1.1.1 is currently in experimental [0]. This package
failed to build against this new package [1] while it built fine against
the openssl version currently in unstable [2].
Could you please have a look? It seems not to like the new version
string:
|I: pybuild base:217: python2.7 setup.py clean
|Traceback (most recent call last):
| File "setup.py", line 256, in
|if openssl_version('1.1.0', required=True):
| File "setup.py", line 84, in openssl_version
|return StrictVersion(ver_str) >= StrictVersion(req_ver)
| File "/usr/lib/python2.7/distutils/version.py", line 40, in __init__
|self.parse(vstring)
| File "/usr/lib/python2.7/distutils/version.py", line 107, in parse
|raise ValueError, "invalid version number '%s'" % vstring
|ValueError: invalid version number '1.1.1-pre6'
|E: pybuild pybuild:336: clean: plugin distutils failed with: exit code=1:
python2.7 setup.py clean
|dh_auto_clean: pybuild --clean --test-pytest -i python{version} -p 2.7
returned exit code 13
|make: *** [debian/rules:15: clean] Error 25
this is probably temporary until the `-preX' suffix vanishes in the
final release but it would nice to handle it in the meantime.
[0] https://lists.debian.org/msgid-search/20180501211400.ga21...@roeckx.be
[1]
https://breakpoint.cc/openssl-rebuild/2018-05-03-rebuild-openssl1.1.1-pre6/attempted/m2crypto_0.27.0-5_amd64-2018-05-02T20%3A11%3A27Z
[2]
https://breakpoint.cc/openssl-rebuild/2018-05-03-rebuild-openssl1.1.1-pre6/successful/m2crypto_0.27.0-5_amd64-2018-05-02T18%3A45%3A27Z
Sebastian
--- End Message ---
--- Begin Message ---
Version: 0.30.1+git20181013.1576f1e-1
Thanks,
DS
--
4096R/DF5182C8 (sten...@debian.org)
http://www.danielstender.com/--- End Message ---
Bug#858938: fixed in kopete 4:18.04.1-1
On Sun, Oct 28, 2018 at 11:29:43PM +0100, Sebastian Andrzej Siewior wrote: > On 2018-10-21 12:31:45 [+0200], Kurt Roeckx wrote: > > On Tue, Sep 25, 2018 at 11:29:28PM +0200, Sebastian Andrzej Siewior wrote: > > > On 2018-08-25 10:33:54 [+0200], Kurt Roeckx wrote: > > > > On Fri, Jun 01, 2018 at 11:22:09AM +, Sandro Knauß wrote: > > > > > Source: kopete > > > > > Source-Version: 4:18.04.1-1 > > > > > > > > > > We believe that the bug you reported is fixed in the latest version of > > > > > kopete, which is due to be installed in the Debian FTP archive. > > > > > > > > Any plans to upload this to unstable? > > > > > > There are just two packages left in testing which use openssl1.0. The > > > last kopete upload was in mid June. Is there anything blocking an upload > > > to unstable? > > > > The other one just got fixed in unstable, so this will soon be the > > only package in testing still depending on libssl1.0.2. > > kopete is the only package in testing still using libssl1.0.2. Could > someone please comment on this? This is in experimental for more than 5 months now. If nobody replies to this, I will upload an NMU to unstable. Kurt
Bug#913392: yapps2: missing dependency on python3-pkg-resources
Source: yapps2 Version: 2.2.1-2 Severity: serious Justification: policy 3.5 An attempt to build keymapper with current yapps2 produced: yapps2 x11.g Traceback (most recent call last): File "/usr/bin/yapps2", line 6, in from pkg_resources import load_entry_point ModuleNotFoundError: No module named 'pkg_resources' yapps2 needs to depend on python3-pkg-resources. Thanks, -- Colin Watson [cjwat...@debian.org]
Bug#913391: parl-desktop-world: depends on cruft package icedove-bidiui
Package: parl-desktop-world Version: 1.9.13 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, please switch to thunderbird-bidiui, icedove-bidiui is no longer built. Andreas
Processed: severity of 913346 is normal
Processing commands for cont...@bugs.debian.org: > severity 913346 normal Bug #913346 [libsane1] libsane1: Cannot update libsane1 Severity set to 'normal' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 913346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913346 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#913346: Subject: Re: libsane1: Cannot update libsane1
Control: -1 severity normal Hi, libsane1 has been renamed to libsane. apt install libsane will remove libsane1 and install libsane which should resolve your issue. Cheers, Amy
Bug#913192: qtwebengine5-examples: Instructions on how to compile the examples must be provided
Control: tags -1 moreinfo Hi Salvo! On Wed, Nov 07, 2018 at 11:37:42PM +0100, Salvo Tomaselli wrote: > Dear Maintainer, > this packages provides source examples, and a binary that supposedly is > compiled from them. > > However, there is no README, the usual qmake . && make won't work. The usual qmake && make works fine here: $ cp -r /usr/lib/x86_64-linux-gnu/qt5/examples/webenginewidgets/simplebrowser/ /tmp/ $ cd /tmp/simplebrowser/ $ qmake -qt5 Info: creating stash file /tmp/simplebrowser/.qmake.stash $ make [compiles] $ ./simplebrowser [opens the simple browser] What error are you getting? -- Dmitry Shachnev signature.asc Description: PGP signature
Processed: Re: Bug#913192: qtwebengine5-examples: Instructions on how to compile the examples must be provided
Processing control commands: > tags -1 moreinfo Bug #913192 [qtwebengine5-examples] qtwebengine5-examples: Instructions on how to compile the examples must be provided Added tag(s) moreinfo. -- 913192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913192 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907219: marked as done (m2crypto: autopkgtest needs update for new version of openssl)
Your message dated Sat, 10 Nov 2018 11:20:17 +
with message-id
and subject line Bug#907219: fixed in m2crypto 0.31.0-1
has caused the Debian Bug report #907219,
regarding m2crypto: autopkgtest needs update for new version of openssl
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
907219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907219
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: m2crypto
Version: 0.27.0-6
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:openssl
Control: block 907015 by -1
Dear maintainers,
With a recent upload of openssl the autopkgtest of m2crypto started to
fail in testing. I copied some of the output below.
Of course, openssl shouldn't just break your autopkgtest (or even worse,
your package), but the change in openssl was intended and your package
needs to update to the new situation. If needed, please change the bug's
severity.
If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from openssl should really add
a versioned Breaks on the unfixed version of (one of your) package(s),
hence I added a blocking relation on the openssl bug that tracks that.
Note: the Breaks is nice even if the issue is only in the autopkgtest as
it helps the migration software to figure out the right versions to
combine in the tests.
A quote from the openssl maintainer about the openssl update:
"
This is probably the result of the default openssl.cfg now having:
[system_default_sect]
MinProtocol = TLSv1.2
CipherString = DEFAULT@SECLEVEL=2
Where the SECLEVEL 2 requires a 112 / 2048 bit security level.
"
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=openssl
https://ci.debian.net/data/autopkgtest/testing/amd64/m/m2crypto/874888/log.gz
/usr/lib/python2.7/dist-packages/M2Crypto/httpslib.py:88: error
_ TwistedSSLClientTestCase.test_makefile_timeout_fires
_
self =
def test_makefile_timeout_fires(self):
# This is convoluted because (openssl s_server -www) starts
# writing the response as soon as it receives the first line of
# the request, so it's possible for it to send the response
# before the request is sent and there would be no timeout. So,
# let the server spend time reading from an empty pipe
FIFO_NAME = 'test_makefile_timeout_fires_fifo' # noqa
os.mkfifo('tests/' + FIFO_NAME)
pipe_pid = os.fork()
try:
if pipe_pid == 0:
try:
with open('tests/' + FIFO_NAME, 'w') as f:
time.sleep(sleepTime + 1)
f.write('Content\n')
finally:
os._exit(0)
self.args[self.args.index('-www')] = '-WWW'
pid = self.start_server(self.args)
try:
c = httpslib.HTTPSConnection(srv_host, self.srv_port)
c.putrequest('GET', '/' + FIFO_NAME)
c.putheader('Accept', 'text/html')
c.putheader('Accept', 'text/plain')
> c.endheaders()
tests/test_ssl.py:988:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
/usr/lib/python2.7/httplib.py:1038: in endheaders
self._send_output(message_body)
/usr/lib/python2.7/httplib.py:882: in _send_output
self.send(msg)
/usr/lib/python2.7/httplib.py:844: in send
self.connect()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
self =
def connect(self):
# type: () -> None
error = None
# We ignore the returned sockaddr because SSL.Connection.connect
needs
# a host name.
for (family, _, _, _, _) in \
socket.getaddrinfo(self.host, self.port, 0,
socket.SOCK_STREAM):
sock = None
try:
sock = SSL.Connection(self.ssl_ctx, family=family)
# set SNI server name since we know it at this point
sock.set_tlsext_host_name(self.host)
if self.session is not None:
sock.set_session(self.session)
sock.connect((self.host, self.port))
self.sock = sock
sock = None
return
except socket.error as e:
# Other
Bug#912611: marked as done (icecast2: CVE-2018-18820)
Your message dated Sat, 10 Nov 2018 11:17:07 + with message-id and subject line Bug#912611: fixed in icecast2 2.4.2-1+deb9u1 has caused the Debian Bug report #912611, regarding icecast2: CVE-2018-18820 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.) -- 912611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912611 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: icecast2 Version: 2.4.3-3 Severity: grave Tags: patch security upstream Justification: user security hole Forwarded: https://gitlab.xiph.org/xiph/icecast-server/issues/2342 Control: found -1 2.4.2-1 Hi, The following vulnerability was published for icecast2. CVE-2018-18820[0]: buffer overflow in url-auth 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-18820 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-18820 Please adjust the affected versions in the BTS as needed. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: icecast2 Source-Version: 2.4.2-1+deb9u1 We believe that the bug you reported is fixed in the latest version of icecast2, 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 912...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Unit 193 (supplier of updated icecast2 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, 31 Oct 2018 01:26:56 -0400 Source: icecast2 Binary: icecast2 Architecture: source amd64 Version: 2.4.2-1+deb9u1 Distribution: stretch-security Urgency: high Maintainer: Debian Multimedia Maintainers Changed-By: Unit 193 Description: icecast2 - streaming media server Closes: 912611 Changes: icecast2 (2.4.2-1+deb9u1) stretch-security; urgency=high . * d/p/CVE-2018-18820.patch: - Cherry-pick upstream commits fixing buffer overflow in URL authentication - Closes: #912611, CVE-2018-18820 Checksums-Sha1: e83d04d09254541b123f94de759941e1a85cc2d9 2351 icecast2_2.4.2-1+deb9u1.dsc 57a092302ab8aa4993fa280f299c099d25e875a5 2388381 icecast2_2.4.2.orig.tar.gz 8a27d083c07f667d168a46e897f067decc3b2721 34880 icecast2_2.4.2-1+deb9u1.debian.tar.xz 0848675c90b1878f4731fa6ff278a2561df4ba6a 353612 icecast2-dbgsym_2.4.2-1+deb9u1_amd64.deb 8a33ac175d212e01215ee58001ced85b0810f331 8383 icecast2_2.4.2-1+deb9u1_amd64.buildinfo 52b3f9418ffbffe6ebfc8318de790d67a0d23838 1541780 icecast2_2.4.2-1+deb9u1_amd64.deb Checksums-Sha256: 9e452a038f0cc0b8507c1ec410d5596d9fcc9e41be393276ba76f8eb94fc2caf 2351 icecast2_2.4.2-1+deb9u1.dsc aa1ae2fa364454ccec61a9247949d19959cb0ce1b044a79151bf8657fd673f4f 2388381 icecast2_2.4.2.orig.tar.gz 5dc93b6265545dd7d5479a321131cdc409c9c5bcc3619360091141e4bcb732c8 34880 icecast2_2.4.2-1+deb9u1.debian.tar.xz 99f8761083d313a984bf6ae457fd1b43cd5ddc10a4a87264e4714aa92b036f5e 353612 icecast2-dbgsym_2.4.2-1+deb9u1_amd64.deb b3484d9d1328c904d3b4ec418a5626a31bbe5497fdd2d7c640d0c03d79e281e4 8383 icecast2_2.4.2-1+deb9u1_amd64.buildinfo 59a1f09c76c63ab3b64fc87917e167d2a8df3426fbb655499df1590b52aaec2a 1541780 icecast2_2.4.2-1+deb9u1_amd64.deb Files: f754a9b188085e511c369157a7728621 2351 sound optional icecast2_2.4.2-1+deb9u1.dsc 55947c83d31dfcbbede58c9521c676f4 2388381 sound optional icecast2_2.4.2.orig.tar.gz 902a5675ff489d5af8826cbbda99778f 34880 sound optional icecast2_2.4.2-1+deb9u1.debian.tar.xz 5702dd5ac8b9244c820f7feb96192a45 353612 debug extra icecast2-dbgsym_2.4.2-1+deb9u1_amd64.deb 8ee841e92ded6ce4e730ffa6a7298e41 8383 sound optional icecast2_2.4.2-1+deb9u1_amd64.buildinfo ebd357884a35e8f3f68607e740e3e11e 1541780 sound optional icecast2_2.4.2-1+deb9u1_amd64.deb
Bug#913090: marked as done (nginx: CVE-2018-16843 CVE-2018-16844 CVE-2018-16845)
Your message dated Sat, 10 Nov 2018 11:17:21 + with message-id and subject line Bug#913090: fixed in nginx 1.10.3-1+deb9u2 has caused the Debian Bug report #913090, regarding nginx: CVE-2018-16843 CVE-2018-16844 CVE-2018-16845 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.) -- 913090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913090 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nginx Version: 1.10.3-1 Severity: important Tags: security upstream Control: found -1 1.10.3-1+deb9u1 Control: found -1 1.14.0-1 Hi, The following vulnerabilities were published for nginx. CVE-2018-16843[0]: Excessive memory usage in HTTP/2 CVE-2018-16844[1]: Excessive CPU usage in HTTP/2 CVE-2018-16845[2]: Memory disclosure in the ngx_http_mp4_module If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2018-16843 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16843 [1] https://security-tracker.debian.org/tracker/CVE-2018-16844 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16844 [2] https://security-tracker.debian.org/tracker/CVE-2018-16845 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16845 Regards, Salvatore --- End Message --- --- Begin Message --- Source: nginx Source-Version: 1.10.3-1+deb9u2 We believe that the bug you reported is fixed in the latest version of nginx, 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 913...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christos Trochalakis (supplier of updated nginx 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, 07 Nov 2018 07:40:42 +0200 Source: nginx Binary: nginx nginx-doc nginx-common nginx-full nginx-light nginx-extras libnginx-mod-http-geoip libnginx-mod-http-image-filter libnginx-mod-http-xslt-filter libnginx-mod-mail libnginx-mod-stream libnginx-mod-http-perl libnginx-mod-http-auth-pam libnginx-mod-http-lua libnginx-mod-http-ndk libnginx-mod-nchan libnginx-mod-http-echo libnginx-mod-http-upstream-fair libnginx-mod-http-headers-more-filter libnginx-mod-http-cache-purge libnginx-mod-http-fancyindex libnginx-mod-http-uploadprogress libnginx-mod-http-subs-filter libnginx-mod-http-dav-ext Architecture: source Version: 1.10.3-1+deb9u2 Distribution: stretch-security Urgency: high Maintainer: Debian Nginx Maintainers Changed-By: Christos Trochalakis Description: libnginx-mod-http-auth-pam - PAM authentication module for Nginx libnginx-mod-http-cache-purge - Purge content from Nginx caches libnginx-mod-http-dav-ext - WebDAV missing commands support for Nginx libnginx-mod-http-echo - Bring echo and more shell style goodies to Nginx libnginx-mod-http-fancyindex - Fancy indexes module for the Nginx libnginx-mod-http-geoip - GeoIP HTTP module for Nginx libnginx-mod-http-headers-more-filter - Set and clear input and output headers for Nginx libnginx-mod-http-image-filter - HTTP image filter module for Nginx libnginx-mod-http-lua - Lua module for Nginx libnginx-mod-http-ndk - Nginx Development Kit module libnginx-mod-http-perl - Perl module for Nginx libnginx-mod-http-subs-filter - Substitution filter module for Nginx libnginx-mod-http-uploadprogress - Upload progress system for Nginx libnginx-mod-http-upstream-fair - Nginx Upstream Fair Proxy Load Balancer libnginx-mod-http-xslt-filter - XSLT Transformation module for Nginx libnginx-mod-mail - Mail module for Nginx libnginx-mod-nchan - Fast, flexible pub/sub server for Nginx libnginx-mod-stream - Stream module for Nginx nginx - small, powerful, scalable web/proxy server nginx-common - small, powerful, scalable web/proxy server - common files nginx-doc - small, powerful, scalable web/proxy server - documentation nginx-extras - nginx web/proxy server (extended version) nginx-full - nginx web/proxy server (standard version) nginx-light - nginx web/proxy server (basic version) Closes: 913090 Changes: nginx (1.10.3-1+deb9u2)
Bug#913383: libetpan FTBFS with curl 7.62.0
Source: libetpan Version: 1.9.1-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libetpan.html ... newsfeed.c: In function 'curl_error_convert': newsfeed.c:538:3: error: duplicate case value case CURLE_SSL_CACERT: ^~~~ newsfeed.c:533:3: note: previously used here case CURLE_SSL_PEER_CERTIFICATE: ^~~~ make[9]: *** [Makefile:579: newsfeed.lo] Error 1 For background see https://github.com/curl/curl/commit/3f3b26d6feb0667714902e836af608094235fca2
Bug#913382: fbreader FTBFS with curl 7.62.0
Source: fbreader Version: 0.12.10dfsg2-2 Severity: serious Tags: ftbfs buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/fbreader.html ... ZLCurlNetworkManager.cpp: In member function 'virtual std::__cxx11::string ZLCurlNetworkManager::perform(const Vector&) const': ZLCurlNetworkManager.cpp:287:5: error: duplicate case value case CURLE_SSL_CACERT: ^~~~ ZLCurlNetworkManager.cpp:281:5: note: previously used here case CURLE_PEER_FAILED_VERIFICATION: ^~~~ make[3]: *** [/build/1st/fbreader-0.12.10dfsg2/zlibrary/core/../../makefiles/subdir.mk:14: ZLCurlNetworkManager.o] Error 1 For background see https://github.com/curl/curl/commit/3f3b26d6feb0667714902e836af608094235fca2
Bug#913381: simgear FTBFS with curl 7.62.0
Source: simgear Version: 1:2018.2.2+dfsg-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/simgear.html ... Start 4: http 4/35 Test #4: http .***Failed 14.02 sec testing chunked transfer encoding sending error 404 for /not-found content: done 404 test done1 channel close dtor test server channel done2 channel close dtor test server channel done3 testing abrupt close CURL Result:6 Couldn't resolve host name HTTP request: set failure:6 reason Couldn't resolve host name channel close dtor test server channel testing proxy close CURL Result:52 Server returned nothing (no headers, no data) HTTP request: set failure:52 reason Server returned nothing (no headers, no data) testing HTTP 1.1 pipelining dtor test server channel http 1.0 multiple requests channel close dtor test server channel channel close dtor test server channel channel close dtor test server channel testing POST testing PUT sending PUT response testing PUT create sending create response zero-length-content-response cancel request dtor test server channel HTTP request: set failure:-1 reason my reason 1 HTTP request: set failure:-1 reason my reason 2 cancel middle request dtor test server channel HTTP request: set failure:-1 reason middle request get-during-response-send channel close dtor test server channel timed out failed: (tr->bodyData) == (string(BODY3)) got 'Cras ut neque nulla. Duis ut velit neque, sit amet pharetra risus. In est ligula, lacinia vitae cong' and 'Cras ut neque nulla. Duis ut velit neque, sit amet pharetra risus. In est ligula, lacinia vitae congue in, sollicitudin at libero. Mauris pharetra pretium elit, nec placerat dui semper et. Maecenas magna magna, placerat sed luctus ac, commodo et ligula. Mauris at purus et nisl molestie auctor placerat at quam. Donec sapien magna, venenatis sed iaculis id, fringilla vel arcu. Duis sed neque nisi. Cras a arcu sit amet risus ultrices varius. Integer sagittis euismod dui id varius. Cras vel justo gravida metus.' at ./simgear/io/test_HTTP.cxx:771 ... 97% tests passed, 1 tests failed out of 35 Total Test time (real) = 45.97 sec The following tests FAILED: 4 - http (Failed) Errors while running CTest make[2]: *** [Makefile:144: test] Error 8
Bug#913380: tarantool FTBFS with curl 7.62.0
Source: tarantool Version: 1.9.1.26.g63eb81e3c-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/tarantool.html ... cd /build/1st/tarantool-1.9.1.26.g63eb81e3c/obj-x86_64-linux-gnu/src && /usr/bin/cc -DCORO_ASM -DLUAJIT_SMART_STRINGS=1 -DNDEBUG -DNVALGRIND -DNVALGRIND=1 -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS=1 -D__STDC_FORMAT_MACROS=1 -D__STDC_LIMIT_MACROS=1 -I/build/1st/tarantool-1.9.1.26.g63eb81e3c/src -I/build/1st/tarantool-1.9.1.26.g63eb81e3c/obj-x86_64-linux-gnu/src -I/build/1st/tarantool-1.9.1.26.g63eb81e3c/src/lib -I/build/1st/tarantool-1.9.1.26.g63eb81e3c/src/lib/small -I/build/1st/tarantool-1.9.1.26.g63eb81e3c/src/lib/small/third_party -I/build/1st/tarantool-1.9.1.26.g63eb81e3c -I/build/1st/tarantool-1.9.1.26.g63eb81e3c/third_party/zstd/lib -I/build/1st/tarantool-1.9.1.26.g63eb81e3c/third_party/zstd/lib/common -I/build/1st/tarantool-1.9.1.26.g63eb81e3c/obj-x86_64-linux-gnu/third_party -I/build/1st/tarantool-1.9.1.26.g63eb81e3c/third_party -I/build/1st/tarantool-1.9.1.26.g63eb81e3c/third_party/coro -I/build/1st/tarantool-1.9.1.26.g63eb81e3c/third_party/luajit/src -I/build/1st/tarantool-1.9.1.26.g63eb81e3c/src/lib/msgpuck -I/usr/include/x86_64-linux-gnu -I/build/1st/tarantool-1.9.1.26.g63eb81e3c/third_party/libutil_freebsd -g -O2 -ffile-prefix-map=/build/1st/tarantool-1.9.1.26.g63eb81e3c=. -specs=/usr/share/dpkg/no-pie-compile.specs -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fexceptions -funwind-tables -fno-omit-frame-pointer -fno-stack-protector -fno-common -fopenmp -msse2 -std=c11 -Wall -Wextra -Wno-strict-aliasing -Wno-char-subscripts -Wno-format-truncation -fno-gnu89-inline -O2 -g -DNDEBUG -ggdb -O2 -o CMakeFiles/server.dir/httpc.c.o -c /build/1st/tarantool-1.9.1.26.g63eb81e3c/src/httpc.c /build/1st/tarantool-1.9.1.26.g63eb81e3c/src/httpc.c: In function 'httpc_execute': /build/1st/tarantool-1.9.1.26.g63eb81e3c/src/httpc.c:336:2: error: duplicate case value case CURLE_PEER_FAILED_VERIFICATION: ^~~~ /build/1st/tarantool-1.9.1.26.g63eb81e3c/src/httpc.c:335:2: note: previously used here case CURLE_SSL_CACERT: ^~~~ make[3]: *** [src/CMakeFiles/server.dir/build.make:425: src/CMakeFiles/server.dir/httpc.c.o] Error 1 For background see https://github.com/curl/curl/commit/3f3b26d6feb0667714902e836af608094235fca2
Bug#913379: zurl FTBFS with curl 7.62.0
Source: zurl Version: 1.9.1-4 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/zurl.html ... ../httprequest_curl.cpp: In member function 'void HttpRequest::Private::conn_updated()': ../httprequest_curl.cpp:1288:5: error: duplicate case value case CURLE_PEER_FAILED_VERIFICATION: ^~~~ ../httprequest_curl.cpp:1287:5: note: previously used here case CURLE_SSL_CACERT: ^~~~ make[2]: *** [Makefile:750: _obj/httprequest_curl.o] Error 1 For background see https://github.com/curl/curl/commit/3f3b26d6feb0667714902e836af608094235fca2
