Bug#883448: bind9: FTBFS with -A (arch:all)
Source: bind9 Version: 1:9.11.2+dfsg-2 Severity: serious Justification: FTBFS Hi, Your package FTBFS when performing the arch:all build: | make[1]: Entering directory '/<>/bind9-9.11.2+dfsg' | # TODO: move this to bind9.install | install -c -o bin -g bin -m 444 debian/db.0 /<>/bind9-9.11.2+dfsg/debian/bind9/etc/bind/db.0 | install: cannot create regular file '/<>/bind9-9.11.2+dfsg/debian/bind9/etc/bind/db.0': No such file or directory | debian/rules:129: recipe for target 'override_dh_install' failed | make[1]: *** [override_dh_install] Error 1 | make[1]: Leaving directory '/<>/bind9-9.11.2+dfsg' | debian/rules:47: recipe for target 'binary-indep' failed | make: *** [binary-indep] Error 2 Full build log: https://buildd.debian.org/status/fetch.php?pkg=bind9&arch=all&ver=1%3A9.11.2%2Bdfsg-2&stamp=1512340742&raw=0 KiBi.
Bug#849122: unmerging 849122, bug 849122 is forwarded to https://github.com/lwfinger/rtl8188eu/issues/237
unmerge 849122 forwarded 849122 https://github.com/lwfinger/rtl8188eu/issues/237 severity 849122 normal thanks Hi, I'm unmerging 849122 as should be a separate bug. It should have been worked around since I uploaded an NM snippet to blacklist it for MAC address randomisation, so I'm downgrading the severity. lwfinger's repository seems to be the upstream, so I have reported the bug there. Please let me know if this is still an issue with the latest wpasupplicant upload. -- Cheers, Andrew
Processed: unmerging 849122, bug 849122 is forwarded to https://github.com/lwfinger/rtl8188eu/issues/237
Processing commands for cont...@bugs.debian.org: > unmerge 849122 Bug #849122 [wpasupplicant] With 2.6-2 i dont have the wifi adapter in the (network-manager) list available. Ignoring request to unmerge a bug which is not merged with any others. > forwarded 849122 https://github.com/lwfinger/rtl8188eu/issues/237 Bug #849122 [wpasupplicant] With 2.6-2 i dont have the wifi adapter in the (network-manager) list available. Set Bug forwarded-to-address to 'https://github.com/lwfinger/rtl8188eu/issues/237'. > severity 849122 normal Bug #849122 [wpasupplicant] With 2.6-2 i dont have the wifi adapter in the (network-manager) list available. Severity set to 'normal' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 849122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849122 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#883449: bind9: uninstallable udebs
Source: bind9 Version: 1:9.11.2+dfsg-2 Severity: serious Tags: d-i Justification: uninstallable packages [ Please keep debian-boot@ in copy of your replies. ] Hi, There seems to be new issues with the udebs: libdns-export169-udeb and libisccc-export160-udeb depend on non-udeb: libisc-export166 libirs-export160-udeb and libisccfg-export160-udeb depend on non-udeb: libdns-export169 KiBi.
Processed: merging 849077 849875, retitle 849077 to broadcom fails with wpa 2.5+
Processing commands for cont...@bugs.debian.org: > merge 849077 849875 Bug #849077 [wpasupplicant] wpasupplicant: [Regression] Updating wpasupplicant makes not possible to connect to encrypted WiFi Bug #849875 [wpasupplicant] broadcom-sta-dkms: Wifi association took too long, failing activation Merged 849077 849875 > retitle 849077 broadcom fails with wpa 2.5+ Bug #849077 [wpasupplicant] wpasupplicant: [Regression] Updating wpasupplicant makes not possible to connect to encrypted WiFi Bug #849875 [wpasupplicant] broadcom-sta-dkms: Wifi association took too long, failing activation Changed Bug title to 'broadcom fails with wpa 2.5+' from 'wpasupplicant: [Regression] Updating wpasupplicant makes not possible to connect to encrypted WiFi'. Changed Bug title to 'broadcom fails with wpa 2.5+' from 'broadcom-sta-dkms: Wifi association took too long, failing activation'. > thanks Stopping processing here. Please contact me if you need assistance. -- 849077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849077 849875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849875 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#883450: omniorb-dfsg: FTBFS with openssl-1.1
Source: omniorb-dfsg
Version: 4.1.6-2.2
Severity: serious
Justification: blocks ongoing transition?
Control: block 827061 by -1
omniorb-dfsg build-depends on openssl 1.0, which is to be removed.
With openssl-1.1, omniorb-dfsg fails to build from source. This is
blocking the removal of openssl-1.0.
There was a big round of bug raising for this before, I don't know
how this package has slipped through the gaps. I've raised this as
serious as all the other bugs in this category are, but maybe more
time should be given.
Build log:
g++ -c -O2 -Wall [..] ./../../../../../src/lib/omniORB/orbcore/ssl/sslContext.cc
../../../../../../src/lib/omniORB/orbcore/ssl/sslContext.cc: In member function
‘virtual void sslContext::set_DH()’:
../../../../../../src/lib/omniORB/orbcore/ssl/sslContext.cc:380:5: error:
invalid use of incomplete type ‘DH {aka struct dh_st}’
dh->p = BN_bin2bn(dh512_p, sizeof(dh512_p), 0);
^~
In file included from /usr/include/openssl/crypto.h:31:0,
from /usr/include/openssl/comp.h:16,
from /usr/include/openssl/ssl.h:47,
from ../../../../../../include/omniORB4/sslContext.h:86,
from
../../../../../../src/lib/omniORB/orbcore/ssl/sslContext.cc:104:
/usr/include/openssl/ossl_typ.h:104:16: note: forward declaration of ‘DH {aka
struct dh_st}’
typedef struct dh_st DH;
^
This is classic "using the old openssl API with direct access to
structs, instead of using getters".
Chris.
Processed (with 1 error): merging 849077 833507
Processing commands for cont...@bugs.debian.org: > merge 849077 833507 Bug #849077 [wpasupplicant] broadcom fails with wpa 2.5+ Bug #849875 [wpasupplicant] broadcom fails with wpa 2.5+ Unable to merge bugs because: severity of #833507 is 'important' not 'serious' Failed to merge 849077: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 833507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833507 849077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849077 849875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849875 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): forcibly merging 849077 838096
Processing commands for cont...@bugs.debian.org: > forcemerge 849077 838096 Bug #849077 [wpasupplicant] broadcom fails with wpa 2.5+ Bug #849875 [wpasupplicant] broadcom fails with wpa 2.5+ Unable to merge bugs because: package of #838096 is 'network-manager' not 'wpasupplicant' Failed to forcibly merge 849077: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 838096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838096 849077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849077 849875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849875 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#853443: hidrd: ftbfs with GCC-7
Hi, Upstream has committed some GCC-7-related fixes. https://github.com/DIGImend/hidrd/commit/7e94881 https://github.com/DIGImend/hidrd/commit/e126127 Thanks, Juhani
Processed: forcibly merging 849077 833507
Processing commands for cont...@bugs.debian.org: > forcemerge 849077 833507 Bug #849077 [wpasupplicant] broadcom fails with wpa 2.5+ Bug #849875 [wpasupplicant] broadcom fails with wpa 2.5+ Bug #833507 [wpasupplicant] wpasupplicant: Unable to connect WLAN (wlan0: CTRL-EVENT-SCAN-FAILED ret=-22) Severity set to 'serious' from 'important' Marked as fixed in versions wpa/2:2.4-1. Marked as found in versions wpa/2:2.6-4 and wpa/2.6-2. Bug #849875 [wpasupplicant] broadcom fails with wpa 2.5+ Marked as found in versions wpa/2.5-2. Marked as found in versions wpa/2.5-2. Merged 833507 849077 849875 > thanks Stopping processing here. Please contact me if you need assistance. -- 833507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833507 849077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849077 849875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849875 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: balsa: FTBFS for me, and the buildds
Processing control commands: > severity -1 serious Bug #828245 [src:balsa] balsa: Stop using deprecated openssl functions Severity set to 'serious' from 'wishlist' > retitle -1 balsa: FTBFS with openssl 1.1.0 Bug #828245 [src:balsa] balsa: Stop using deprecated openssl functions Changed Bug title to 'balsa: FTBFS with openssl 1.1.0' from 'balsa: Stop using deprecated openssl functions'. -- 828245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828245 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#853521: lldpad: ftbfs with GCC-7
Hello, On Tue, 31 Jan 2017 09:33:25 + Matthias Klose wrote: cc1: all warnings being treated as errors Fedora packagers have simply disabled -Werror. http://pkgs.fedoraproject.org/cgit/rpms/lldpad.git/commit/?id=b09c517b There isn't much upstream activity. http://open-lldp.org/git/?p=open-lldp.git Cheers, Juhani
Bug#876299: pcre3: ftbfs on s390x, test failures
Hello, >I thought I'd modified the build script to have the same effect (up >ulimit before running tests), would you care to tell me what I did >wrong, please? it seems to work now, not sure what happened, but my wild guess is that we can't ulimit from rules file (not enough permissions), and probably zelenka has an higer ulimit stack I don't honestly know why your last upload worked :) G.
Bug#882349: marked as done (sra-sdk FTBFS with glibc 2.25)
Your message dated Mon, 04 Dec 2017 09:43:31 + with message-id and subject line Bug#882349: fixed in sra-sdk 2.8.2-3+dfsg-1 has caused the Debian Bug report #882349, regarding sra-sdk FTBFS with glibc 2.25 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 882349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882349 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sra-sdk Version: 2.8.1-2+dfsg-2 Severity: serious Tags: buster sid Forwarded: https://github.com/ncbi/sra-tools/issues/67 https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sra-sdk.html ... /build/1st/sra-sdk-2.8.1-2+dfsg/tools/bam-loader/bam.c:3998:17: error: conflicting types for 'canonicalize' static unsigned canonicalize(uint32_t cigar[], unsigned n) ^~~~ In file included from /usr/include/features.h:406:0, from /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, from /usr/include/stdint.h:26, from /usr/lib/gcc/x86_64-linux-gnu/7/include/stdint.h:9, from /usr/include/ncbi-vdb/kfc/defs.h:34, from /usr/include/ncbi-vdb/klib/defs.h:31, from /build/1st/sra-sdk-2.8.1-2+dfsg/tools/bam-loader/bam.c:27: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:435:1: note: previous declaration of 'canonicalize' was here __MATHDECL_1 (int, canonicalize,, (_Mdouble_ *__cx, const _Mdouble_ *__x)); ^ /build/1st/sra-sdk-2.8.1-2+dfsg/tools/bam-loader/bam.c:2990:17: warning: 'SequenceLengthFromCIGAR' defined but not used [-Wunused-function] static unsigned SequenceLengthFromCIGAR(const BAM_Alignment *self) ^~~ /build/1st/sra-sdk-2.8.1-2+dfsg/build/Makefile.rules:31: recipe for target 'bam.o' failed make[5]: *** [bam.o] Error 1 --- End Message --- --- Begin Message --- Source: sra-sdk Source-Version: 2.8.2-3+dfsg-1 We believe that the bug you reported is fixed in the latest version of sra-sdk, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 882...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated sra-sdk package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 04 Dec 2017 08:29:02 +0100 Source: sra-sdk Binary: sra-toolkit Architecture: source Version: 2.8.2-3+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: sra-toolkit - utilities for the NCBI Sequence Read Archive Closes: 882349 Changes: sra-sdk (2.8.2-3+dfsg-1) unstable; urgency=medium . [ Steffen Moeller ] * debian/upstream/metadata: - added references to registries - yamllint cleanliness . [ Andreas Tille ] * New upstream version * cme fix dpkg-control * Standards-Version: 4.1.1 * debhelper 10 * renamed function to resolve name clash with gnutards to avoid FTBFS with glibc 2.25 Closes: #882349 * Drop test that should not run as root Checksums-Sha1: d587197f032bb3703fa891a71ac6e3dff95e323e 2121 sra-sdk_2.8.2-3+dfsg-1.dsc fa85e5a0aadb3383f6423d28ac07249805b5f16f 2990120 sra-sdk_2.8.2-3+dfsg.orig.tar.xz 9c46bbd60386302a662e0385cbced8f3c80ac1a5 13820 sra-sdk_2.8.2-3+dfsg-1.debian.tar.xz 796a783c126e9740d10f13320dd119f42fae523a 14263 sra-sdk_2.8.2-3+dfsg-1_source.buildinfo Checksums-Sha256: df99d863e91454e2cff5a08e54d85d15164dff9c91dcaa2478c1dd1f9b719da3 2121 sra-sdk_2.8.2-3+dfsg-1.dsc f0fd1dd6eced90a276f3800cef6baf502c85a7fb90531da5da47401e6a793403 2990120 sra-sdk_2.8.2-3+dfsg.orig.tar.xz 3cd133582604605e49e619077c5900f37125dcad2084b7d690e8f97f312ce859 13820 sra-sdk_2.8.2-3+dfsg-1.debian.tar.xz 9ce66239eb9267309e2286697779a4787c7f4667fe8737d0a383f92b560d9af3 14263 sra-sdk_2.8.2-3+dfsg-1_source.buildinfo Files: c2f8f001f29372f8405b2dbd129cf1f3 2121 science optional sra-sdk_2.8.2-3+dfsg-1.dsc d8b967d3d13e025302da5b22fa1cde52 2990120 science optional sra-sdk_2.8.2-3+dfsg.orig.tar.xz 38742042996fc2b06ec3be0fe93b9fde 13820 science optional sra-sdk_2.8.2-3+dfsg-1.debian.tar.xz 5303a68af26721d286e94b37d7bd257c 14263 science opti
Processed: Re: Bug#880387: aufs-dkms: the module is not built for Linux 4.14
Processing control commands: > severity -1 serious Bug #880387 [aufs-dkms] aufs-dkms: the module is not built for Linux 4.14 Ignoring request to change severity of Bug 880387 to the same value. -- 880387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880387 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#880387: aufs-dkms: the module is not built for Linux 4.14
Processing control commands: > severity -1 serious Bug #880387 [aufs-dkms] aufs-dkms: the module is not built for Linux 4.14 Severity set to 'serious' from 'normal' -- 880387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880387 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#880387: aufs-dkms: the module is not built for Linux 4.14
Control: severity -1 serious > Linux 4.14-rc7 was uploaded to experimental; we're getting close to > the 4.14 final release and its upload to sid. How about uploading > a version of aufs-dkms that's compatible with Linux 4.14 (to sid, or > to experimental if that's impractical or not feasible) so that we're > ready when 4.14 reaches sid? Linux 4.14 is now in sid so I think this makes this bug RC. Cheers, -- intrigeri
Bug#882769: Cannot upgrade from Stretch: cp: target '/lib/live/mount/medium/live/vmlinuz.new' is not a directory
Hi, Thomas Goirand: > After booting a Stretch live image, I tried to upgrade it to Sid, and > it fails with this error: Upgrading a *Live* system from one version of Debian to the other is arguably a corner case and this bug does not affect the usability of live-boot in the vast majority of cases. Besides, I would feel wrong to see live-boot automatically removed from testing merely because of this bug. So perhaps this could be demoted to severity:important? Cheers, -- intrigeri
Bug#880387: [Filesystems-devel] Bug#880387: aufs-dkms: the module is not built for Linux 4.14
Hey, I have already prepared an upload but there was a seg fault on my test system I want to investigate before uploading. Best regards, Jan Am 04.12.2017 um 10:44 schrieb intrigeri: > Control: severity -1 serious > >> Linux 4.14-rc7 was uploaded to experimental; we're getting close to >> the 4.14 final release and its upload to sid. How about uploading >> a version of aufs-dkms that's compatible with Linux 4.14 (to sid, or >> to experimental if that's impractical or not feasible) so that we're >> ready when 4.14 reaches sid? > > Linux 4.14 is now in sid so I think this makes this bug RC. > > Cheers, >
Bug#853708: wxhexeditor: ftbfs with GCC-7
Control: tags -1 patch fixed-upstream
Juhani Numminen kirjoitti 04.12.2017 klo 00:12:
This is probably fixed upstream.
https://github.com/EUA/wxHexEditor/commit/581fdbf36e818803f1adffe2c62fb797482b2bca
A suitable patch made from that commit is attached. I tested the package
build (amd64, with cowbuilder) and the resulting application at least
starts up without crashing.
Thanks,
Juhani
Description: Disambiguate abs() overload to use for uint64_t.
At least with MSVC, call to abs() with uint64_t argument is ambiguous, select
the overload taking int64_t explicitly by casting the argument to it.
Author: Vadim Zeitlin
Origin: https://github.com/EUA/wxHexEditor/commit/581fdbf36e818803f1adffe2c62fb797482b2bca
Bug-Debian: https://bugs.debian.org/853708
Last-Update: 2017-12-04
--- a/src/HexEditorCtrl/HexEditorCtrl.h
+++ b/src/HexEditorCtrl/HexEditorCtrl.h
@@ -60,7 +60,7 @@
evth = evth_;
}
uint64_t GetSize( void ){
- return abs( EndOffset - StartOffset)+1;}; //for select byte 13 start=13, end=13
+ return abs(static_cast(EndOffset - StartOffset))+1;}; //for select byte 13 start=13, end=13
void SetState( bool new_state ){
state = new_state;
Processed: Re: wxhexeditor: ftbfs with GCC-7
Processing control commands: > tags -1 patch fixed-upstream Bug #853708 [src:wxhexeditor] wxhexeditor: ftbfs with GCC-7 Added tag(s) fixed-upstream and patch. -- 853708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853708 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#828245: balsa: FTBFS for me, and the buildds
Processing control commands: > forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=789135 Bug #828245 [src:balsa] balsa: FTBFS with openssl 1.1.0 Set Bug forwarded-to-address to 'https://bugzilla.gnome.org/show_bug.cgi?id=789135'. -- 828245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828245 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#828245: balsa: FTBFS for me, and the buildds
Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=789135 On 04/12/17 09:37, Chris West wrote: > Control: severity -1 serious > Control: retitle -1 balsa: FTBFS with openssl 1.1.0 > > This is failing to build for me still on sid (with libssl-dev): > > auth-cram.c: In function ‘hmac_md5’: > auth-cram.c:134:14: error: storage size of ‘ctx’ isn’t known >EVP_MD_CTX ctx; > ^~~ > Makefile:515: recipe for target 'auth-cram.o' failed > > And on the buildds for the transition: > https://release.debian.org/transitions/html/openssl1.0-rm.html > > This is a typical error for this openssl version migration: > the structs have become opaque and you must use pointers everywhere. > > Going back to "serious" because that's what the other transition > bugs are today, but they were raised with much more notice; maybe > more time can be taken to fix this. This is already fixed upstream, we just need a new upstream release or to backport the patch (like Fedora did), see https://bugzilla.gnome.org/show_bug.cgi?id=789135 Emilio
Processed: Not a problem in stretch
Processing commands for cont...@bugs.debian.org: > tags 828245 buster sid Bug #828245 [src:balsa] balsa: FTBFS with openssl 1.1.0 Added tag(s) sid and buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 828245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828245 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#881328: mininet requires missing ovs-controller
El 03/12/17 a las 14:38, Tomasz Buchert escribió: > On 30/11/17 09:26, Santiago R.R. wrote: > > Control: tags -1 + patch fixed-upstream > > > > On Fri, 10 Nov 2017 12:15:39 +0100 "Santiago R.R." > > wrote: > > > > It seems I am wrong about this. > > The bug was only happening if you would have > openvswitch-testcontroller installed. The reason is that mininet fails > to detect the path of the test controller. The patch you provided fixes > the issue. Just for the record: If you are talking about package names, it happened in unstable if you had openvswith-common installed: dpkg -S /usr/bin/ovs-testcontroller openvswitch-common: /usr/bin/ovs-testcontroller LANG=C.UTF-8 dpkg -l openvswitch-common ii openvswitch-common 2.8.1+dfsg1-3 amd64 Open vSwitch common components ... > > P.S. Question for openvswitch maintainers: does it make sense to include > > back /usr/bin/ovs-testcontroller in the -testcontroller package? > > Thanks, I've added the patch and will upload the package later today. Thanks for uploading it! Cheers, -- Santiago
Bug#880308: marked as done (tigervnc: FTBFS: dh_install: missing files, aborting)
Your message dated Mon, 04 Dec 2017 10:43:14 + with message-id and subject line Bug#880308: fixed in tigervnc 1.7.0+dfsg-8 has caused the Debian Bug report #880308, regarding tigervnc: FTBFS: dh_install: missing files, aborting 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.) -- 880308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880308 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tigervnc Version: 1.7.0+dfsg-7 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20171030 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory > '/<>/tigervnc-1.7.0+dfsg/obj-x86_64-linux-gnu/unix/xserver/hw/vnc' > /bin/mkdir -p '/<>/tigervnc-1.7.0+dfsg/debian/tmp//usr/bin' > /bin/bash ../../libtool --mode=install /usr/bin/install -c Xvnc > '/<>/tigervnc-1.7.0+dfsg/debian/tmp//usr/bin' > libtool: install: /usr/bin/install -c Xvnc > /<>/tigervnc-1.7.0+dfsg/debian/tmp//usr/bin/Xvnc > /bin/mkdir -p > '/<>/tigervnc-1.7.0+dfsg/debian/tmp//lib/xorg/modules/extensions' > /bin/bash ../../libtool --mode=install /usr/bin/install -c libvnc.la > '/<>/tigervnc-1.7.0+dfsg/debian/tmp//lib/xorg/modules/extensions' > libtool: install: /usr/bin/install -c .libs/libvnc.so > /<>/tigervnc-1.7.0+dfsg/debian/tmp//lib/xorg/modules/extensions/libvnc.so > libtool: install: /usr/bin/install -c .libs/libvnc.lai > /<>/tigervnc-1.7.0+dfsg/debian/tmp//lib/xorg/modules/extensions/libvnc.la > libtool: warning: remember to run 'libtool --finish > /lib/xorg/modules/extensions' > /bin/mkdir -p > '/<>/tigervnc-1.7.0+dfsg/debian/tmp//usr/share/man/man1' > /usr/bin/install -c -m 644 > '/<>/tigervnc-1.7.0+dfsg/./unix/xserver/hw/vnc/Xvnc.man' > '/<>/tigervnc-1.7.0+dfsg/debian/tmp//usr/share/man/man1/Xvnc.1' > make[2]: Leaving directory > '/<>/tigervnc-1.7.0+dfsg/obj-x86_64-linux-gnu/unix/xserver/hw/vnc' > make[1]: Leaving directory > '/<>/tigervnc-1.7.0+dfsg/obj-x86_64-linux-gnu/unix/xserver/hw/vnc' > Adding cdbs dependencies to debian/tigervnc-viewer.substvars > dh_installdirs -ptigervnc-viewer \ > > mv /<>/tigervnc-1.7.0+dfsg/debian/tmp//usr/bin/vncviewer \ > /<>/tigervnc-1.7.0+dfsg/debian/tmp//usr/bin/xvncviewer > mv > /<>/tigervnc-1.7.0+dfsg/debian/tmp//usr/share/man/man1/vncviewer.1 \ > > /<>/tigervnc-1.7.0+dfsg/debian/tmp//usr/share/man/man1/xvncviewer.1 > cd /<>/tigervnc-1.7.0+dfsg/debian/tmp/ && find usr/bin > usr/share/man -name "*vnc*" | while read line; do \ > mv "$line" `echo "$line" | sed -e 's/vnc/tigervnc/g'`; \ > done > cp -pr debian/helpers/* \ > debian/tmp > find debian/tmp/usr/share/man -type f | while read line; do \ > sed -e 's/\/xtigervncviewer/g' \ > -e 's/\/tigervncpasswd/g' \ > -e 's/\/tigervncconfig/g' \ > -e 's/\/tigervncserver/g' \ > -e 's/\/x0tigervncserver/g' \ > -e 's/\/Xtigervnc/g' \ > -e 's/\/Xvnc-session/g' \ > $line | \ > gzip -9 > $line.gz; \ > rm -f $line; \ > done > touch debian/tmp/common-binary-impl.stamp > dh_installdocs -ptigervnc-common > dh_installexamples -ptigervnc-common > dh_installman -ptigervnc-common > dh_installinfo -ptigervnc-common > dh_installmenu -ptigervnc-common > dh_installcron -ptigervnc-common > dh_systemd_enable -ptigervnc-common > dh_installinit -ptigervnc-common > dh_installdebconf -ptigervnc-common > dh_installemacsen -ptigervnc-common > dh_installcatalogs -ptigervnc-common > dh_installpam -ptigervnc-common > dh_installlogrotate -ptigervnc-common > dh_installlogcheck -ptigervnc-common > dh_installchangelogs -ptigervnc-common > dh_installudev -ptigervnc-common > dh_lintian -ptigervnc-common > dh_bugfiles -ptigervnc-common > dh_install -ptigervnc-common > dh_systemd_start -ptigervnc-common > dh_link -ptigervnc-common > dh_installmime -ptigervnc-common > dh_installgsettings -ptigervnc-common > dh_installdocs -ptigervnc-scraping-server > dh_installexamples -ptigervnc-scraping-server > dh_installman -ptigervnc-scraping-server > dh_installinfo -ptigervnc-scraping-server > dh_installmenu -ptigervnc-scraping-server > dh_installcron -ptigervnc-scraping-server > dh_systemd_enable -ptigervnc-scraping-server > dh_installinit -ptigervnc-scraping-server > dh_installdebconf -ptigervnc-scraping-server > dh_installemacsen -ptigervnc-scraping-server > dh_installcatalogs -ptigervnc-scraping-server > dh_installpam -ptigervnc-scraping-server > dh_installlogrotate -ptigervnc-scraping-server > dh_ins
Bug#883457: python-numpy: don't build depend on python3.5
Package: python-numpy Version: 1:1.13.3-1 Severity: serious Control: block 866335 with -1 Hi, python-numpy 1:1.12.1-3.1 added explict build-depends on python3.5-dev and python3.6-dev to get versions without the fpectl module. However python3.5 is being removed now (already dropped from the list of supported python3 versions) so it is unused during the build. Thus, please drop it from build-depends. It should be possible to drop python3.6-dev as well, as the version without fpectl is in all supported suites (sid and testing). Severity serious as this blocks the removal of python3.5. Thanks, Emilio -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.14.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python-numpy depends on: ii libblas3 [libblas.so.3] 3.7.1-4 ii libc62.25-3 ii liblapack3 [liblapack.so.3] 3.7.1-4 ii python 2.7.14-1 ii python2.72.7.14-2 python-numpy recommends no packages. Versions of packages python-numpy suggests: ii gcc 4:7.2.0-1d1 pn gfortran pn python-dev pn python-nose pn python-numpy-dbg pn python-numpy-doc -- no debconf information
Processed: python-numpy: don't build depend on python3.5
Processing control commands: > block 866335 with -1 Bug #866335 [release.debian.org] transition: python3-defaults 866335 was blocked by: 800709 867010 866575 862431 866504 799635 883403 813083 882778 867028 882789 882790 866555 866700 872052 866335 was not blocking any bugs. Added blocking bug(s) of 866335: 883457 -- 866335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866335 883457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883457 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: hidrd: ftbfs with GCC-7
Processing control commands: > tags -1 patch fixed-upstream Bug #853443 [src:hidrd] hidrd: ftbfs with GCC-7 Added tag(s) fixed-upstream and patch. -- 853443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853443 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#853443: hidrd: ftbfs with GCC-7
Control: tags -1 patch fixed-upstream
On Mon, 4 Dec 2017 10:23:34 +0200 Juhani Numminen
wrote:
Upstream has committed some GCC-7-related fixes.
https://github.com/DIGImend/hidrd/commit/7e94881
https://github.com/DIGImend/hidrd/commit/e126127
I had a successful amd64 build with the two attached patches.
Cheers,
Juhani
Origin: https://github.com/DIGImend/hidrd/commit/e126127ce16aff2b5b8f7dff262bb06180c3ecca
Bug-Debian: https://bugs.debian.org/853443
Last-Update: 2017-12-04
From: Jason Gerecke
Date: Wed, 2 Aug 2017 08:01:41 -0700
Subject: [PATCH] Fix implicit-fallthrough warning/error in GCC 7
GCC 7 now warns about implicit fallthrough, causing the build to fail
(due to -Werror) when compiling lib/fmt/xml/snk/element.c.
element.c: In function âxml_snk_element_addpvâ:
element.c:229:17: error: this statement may fall through [-Werror=implicit-fallthrough=]
(void)va_arg(*pap, const char *);
^
element.c:230:13: note: here
case XML_SNK_ELEMENT_NT_COMMENT:
^~~~
---
lib/fmt/xml/snk/element.c | 1 +
1 file changed, 1 insertion(+)
--- a/lib/fmt/xml/snk/element.c
+++ b/lib/fmt/xml/snk/element.c
@@ -229,6 +229,7 @@
case XML_SNK_ELEMENT_NT_ATTR:
/* Retrieve name */
(void)va_arg(*pap, const char *);
+/* FALLTHROUGH */
case XML_SNK_ELEMENT_NT_COMMENT:
case XML_SNK_ELEMENT_NT_CONTENT:
fmt = va_arg(*pap, hidrd_fmt_type);
Origin: https://github.com/DIGImend/hidrd/commit/7e94881a6059a824efaed41301c4a89a384d86a2
Bug-Debian: https://bugs.debian.org/853443
Last-Update: 2017-12-04
From: Jason Gerecke
Date: Wed, 2 Aug 2017 10:10:43 -0700
Subject: [PATCH] Fix truncation warning/error in GCC 7
GCC 7 now warns about potential truncation in printf statements, causing
the build to fail (due to -Werror). Expand the size of our temporary
buffer to make GCC happy.
element_bitmap.c: In function âparse_bitmap_element.isra.0â:
element_bitmap.c:96:59: error: â%zuâ directive output may be truncated writing between 1 and 20 bytes into a region of size 3 [-Werror=format-truncation=]
snprintf(i_name + 3, sizeof(i_name) - 3, "%zu", i);
^~~
element_bitmap.c:96:58: note: directive argument in the range [0, 18446744073709551614]
snprintf(i_name + 3, sizeof(i_name) - 3, "%zu", i);
^
element_bitmap.c:96:17: note: âsnprintfâ output between 2 and 21 bytes into a destination of size 3
snprintf(i_name + 3, sizeof(i_name) - 3, "%zu", i);
^~
---
lib/fmt/xml/src/element_bitmap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/lib/fmt/xml/src/element_bitmap.c
+++ b/lib/fmt/xml/src/element_bitmap.c
@@ -66,7 +66,7 @@
booldata;
boolmatched;
size_t i;
-chari_name[6] = "bit";
+chari_name[24] = "bit";
for (i = 0, e = e->children; e != NULL; e = e->next)
{
Bug#883403: marked as done (python-astropy: sourceful upload needed for the python3.6 transition)
Your message dated Mon, 4 Dec 2017 11:56:07 +0100 with message-id <48162229-fb63-cd25-e1dd-76aba49a7...@debian.org> and subject line Uploaded. has caused the Debian Bug report #883403, regarding python-astropy: sourceful upload needed for the python3.6 transition 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.) -- 883403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883403 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: astropy-utils Version: 2.0.2-1 Severity: serious Control: block 866335 with -1 Hi, A sourceful upload of astropy-utils is needed for the python3.6 transition. There are no changes needed to the packaging for this transition (rebuilding in an up-to-date sid environment will automatically generate updated dependencies), but since astropy-utils is an arch-indep package depending on pythonX.Y, it cannot be binNMUed. A source-only upload (without any maintainer-built .debs) is preferred. Emilio -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages astropy-utils depends on: ii python33.6.3-2 pn python3-astropy ii python3-pkg-resources 36.7.1-1 pn python3.5 astropy-utils recommends no packages. astropy-utils suggests no packages. --- End Message --- --- Begin Message --- Source: python-astropy-helpers Source-Version: 2.0.2-3 I just uploaded the package (and forgot to close the bug in d/changelog). Cheers Ole--- End Message ---
Bug#882769: Cannot upgrade from Stretch: cp: target '/lib/live/mount/medium/live/vmlinuz.new' is not a directory
On Mon, Dec 04, 2017 at 10:50:53AM +0100, intrigeri wrote: >Hi, > >Thomas Goirand: >> After booting a Stretch live image, I tried to upgrade it to Sid, and >> it fails with this error: > >Upgrading a *Live* system from one version of Debian to the other is >arguably a corner case and this bug does not affect the usability of >live-boot in the vast majority of cases. Besides, I would feel wrong >to see live-boot automatically removed from testing merely because of >this bug. So perhaps this could be demoted to severity:important? At best, yes. -- Steve McIntyre, Cambridge, UK.st...@einval.com There's no sensation to compare with this Suspended animation, A state of bliss
Bug#883466: singularity-container: FTBFS on mips*
Source: singularity-container
Version: 2.4-1
Severity: serious
Tags: sid buster patch
Hi,
singularity-container FTBFS on mips* with the error:
> In file included from mnt.c:41:0:
> ../../../../../src/util/setns.h:46:4: error: #error Please determine the
> syscall number for setns on your architecture
> # error Please determine the syscall number for setns on your architecture
> ^
This error happens because the setns.h header requires a __NR_setns
define for each architecture. However, this define is never used in the
case where glibc provides a setns function (as is the case for all
architectures in buster).
The attached "setns-syscall-nr.patch" patch fixes this by moving the
__NR_setns ifdefs into setns.c so it is only used in the case where
setns is not provided by libc.
After doing this, the package FTBFS again in a different way:
> util/signal.c:39:5: error: 'SIGSTKFLT' undeclared here (not in a function);
> did you mean 'SIGSTKSZ'?
> SIGSTKFLT,
> ^
> SIGSTKSZ
The SIGSTKFLT signal is not defined on mips (and a few other
architectures). This is fixed by the "maybe-sigstkflt.patch" patch which
only adds this signal to the all_signals list if it is defined.
Thanks,
James
--- a/src/util/signal.c
+++ b/src/util/signal.c
@@ -36,7 +36,9 @@ static const int all_signals[] = {
SIGPIPE,
SIGALRM,
SIGTERM,
+#ifdef SIGSTKFLT
SIGSTKFLT,
+#endif
SIGCHLD,
SIGCONT,
SIGTSTP,
--- a/src/util/setns.c
+++ b/src/util/setns.c
@@ -21,7 +21,29 @@
#if defined (NO_SETNS) && defined (SETNS_SYSCALL)
-#include "util/setns.h"
+#ifndef __NR_setns
+# if defined (__x86_64__)
+#define __NR_setns 308
+# elif defined (__i386__)
+#define __NR_setns 346
+# elif defined (__alpha__)
+#define __NR_setns 501
+# elif defined (__arm__)
+#define __NR_setns 375
+# elif defined (__aarch64__)
+#define __NR_setns 375
+# elif defined (__ia64__)
+#define __NR_setns 1330
+# elif defined (__sparc__)
+#define __NR_setns 337
+# elif defined (__powerpc__)
+#define __NR_setns 350
+# elif defined (__s390__)
+#define __NR_setns 339
+# else
+#error Please determine the syscall number for setns on your architecture
+# endif
+#endif
int setns(int fd, int nstype) {
return syscall(__NR_setns, fd, nstype);
--- a/src/util/setns.h
+++ b/src/util/setns.h
@@ -16,34 +16,6 @@
#ifndef __SETNS_H_
#define __SETNS_H_
-#ifndef __NR_setns
-# if defined (__x86_64__)
-#define __NR_setns 308
-# elif defined (__i386__)
-#define __NR_setns 346
-# elif defined (__alpha__)
-#define __NR_setns 501
-# elif defined (__arm__)
-#define __NR_setns 375
-# elif defined (__aarch64__)
-#define __NR_setns 375
-# elif defined (__ia64__)
-#define __NR_setns 1330
-# elif defined (__sparc__)
-#define __NR_setns 337
-# elif defined (__powerpc__)
-#define __NR_setns 350
-# elif defined (__s390__)
-#define __NR_setns 339
-# endif
-#endif
-
-#ifdef __NR_setns
-
extern int setns(int fd, int nstype);
-#else /* !__NR_setns */
-# error Please determine the syscall number for setns on your architecture
-#endif
-
#endif /* __SETNS_H_ */
signature.asc
Description: OpenPGP digital signature
Processed: Re: oclgrind: Please update to llvm-toolchain 4.0 or, better, 5.0
Processing control commands: > severity -1 serious Bug #873422 [src:oclgrind] oclgrind: Please update to llvm-toolchain 4.0 or, better, 5.0 Severity set to 'serious' from 'normal' -- 873422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873422 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Resolved upstream ticket for bug#882540
Processing commands for cont...@bugs.debian.org: > forwarded 882540 https://github.com/sahlberg/libnfs/issues/202 Bug #882540 [src:libnfs] libnfs FTBFS with glibc 2.25 Set Bug forwarded-to-address to 'https://github.com/sahlberg/libnfs/issues/202'. > tags 882540 fixed-upstream Bug #882540 [src:libnfs] libnfs FTBFS with glibc 2.25 Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 882540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882540 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#883469: mercurial-git: needs to be updated to work with mercurial 4.4.1
Package: mercurial-git Version: 0.8.9-1 Severity: grave Justification: renders package unusable With the new mercurial 4.4.1 in sid mercurial-git cannot work anymore. A sample error is: $ hg log abort: cannot import name peerrepository! Mercurial don't work anymore even if the upstream repository is mercurial and not git. So, basically, you cannot use mercurial anymore without disabling the extension in hgrc or updating to the latest upstream version which is already fixed. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (800, 'unstable'), (50, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.13.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to it_IT.UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to it_IT.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mercurial-git depends on: ii mercurial 4.4.1-1 ii python 2.7.14-1 ii python-dulwich 0.18.5-1 mercurial-git recommends no packages. mercurial-git suggests no packages. -- no debconf information
Bug#882769: Cannot upgrade from Stretch: cp: target '/lib/live/mount/medium/live/vmlinuz.new' is not a directory
On 12/04/2017 10:50 AM, intrigeri wrote: > Hi, > > Thomas Goirand: >> After booting a Stretch live image, I tried to upgrade it to Sid, and >> it fails with this error: > > Upgrading a *Live* system from one version of Debian to the other is > arguably a corner case and this bug does not affect the usability of > live-boot in the vast majority of cases. My use case is to use live for the OpenStack CI, when I want to test with Sid and not stable. Probably not a lot of people do that, but it's still a use case. Do you know if it's possible to generate a Sid live system? > Besides, I would feel wrong > to see live-boot automatically removed from testing merely because of > this bug. So perhaps this could be demoted to severity:important? I don't mind much the severity, but I'd very much prefer if we found out how to fix! Currently, I still don't understand which script is the problem. Do you have any idea? Cheers, Thomas Goirand (zigo)
Bug#883449: marked as done (bind9: uninstallable udebs)
Your message dated Mon, 04 Dec 2017 11:48:57 + with message-id and subject line Bug#883449: fixed in bind9 1:9.11.2+dfsg-3 has caused the Debian Bug report #883449, regarding bind9: uninstallable udebs 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.) -- 883449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883449 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bind9 Version: 1:9.11.2+dfsg-2 Severity: serious Tags: d-i Justification: uninstallable packages [ Please keep debian-boot@ in copy of your replies. ] Hi, There seems to be new issues with the udebs: libdns-export169-udeb and libisccc-export160-udeb depend on non-udeb: libisc-export166 libirs-export160-udeb and libisccfg-export160-udeb depend on non-udeb: libdns-export169 KiBi. --- End Message --- --- Begin Message --- Source: bind9 Source-Version: 1:9.11.2+dfsg-3 We believe that the bug you reported is fixed in the latest version of bind9, 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 883...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bernhard Schmidt (supplier of updated bind9 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 04 Dec 2017 10:56:58 +0100 Source: bind9 Binary: bind9 bind9utils bind9-doc bind9-host libbind-dev libbind9-160 libdns169 libirs160 libisc166 liblwres160 libisccc160 libisccfg160 dnsutils libbind-export-dev libdns-export169 libdns-export169-udeb libirs-export160 libirs-export160-udeb libisc-export166 libisc-export166-udeb libisccc-export160 libisccc-export160-udeb libisccfg-export160 libisccfg-export160-udeb Architecture: source Version: 1:9.11.2+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian DNS Packaging Changed-By: Bernhard Schmidt Description: bind9 - Internet Domain Name Server bind9-doc - Documentation for BIND bind9-host - Version of 'host' bundled with BIND 9.X bind9utils - Utilities for BIND dnsutils - Clients provided with BIND libbind-dev - Static Libraries and Headers used by BIND libbind-export-dev - Development files for the exported BIND libraries libbind9-160 - BIND9 Shared Library used by BIND libdns-export169 - Exported DNS Shared Library libdns-export169-udeb - Exported DNS library for debian-installer (udeb) libdns169 - DNS Shared Library used by BIND libirs-export160 - Exported IRS Shared Library libirs-export160-udeb - Exported IRS library for debian-installer (udeb) libirs160 - DNS Shared Library used by BIND libisc-export166 - Exported ISC Shared Library libisc-export166-udeb - Exported ISC library for debian-installer (udeb) libisc166 - ISC Shared Library used by BIND libisccc-export160 - Command Channel Library used by BIND libisccc-export160-udeb - Command Channel Library used by BIND (udeb) libisccc160 - Command Channel Library used by BIND libisccfg-export160 - Exported ISC CFG Shared Library libisccfg-export160-udeb - Exported ISC CFG library for debian-installer (udeb) libisccfg160 - Config File Handling Library used by BIND liblwres160 - Lightweight Resolver Library used by BIND Closes: 883448 883449 Changes: bind9 (1:9.11.2+dfsg-3) unstable; urgency=medium . * Team upload. * Only install files into bind9:any on arch-any builds (Closes: #883448) * Adjust dependencies for udeb packages (Closes: #883449) Checksums-Sha1: e5288d52f7575e7a5f0c6300fdd78670d9d8e405 3767 bind9_9.11.2+dfsg-3.dsc c2c0fcbc37c57c7350b58f0e4d72d854f9c2ec28 77744 bind9_9.11.2+dfsg-3.debian.tar.xz 6f1a9bcbf706066765d74784c12cfbe3721a0194 18639 bind9_9.11.2+dfsg-3_amd64.buildinfo Checksums-Sha256: 8e4c18f76fae876173bc94db49926f5ee721f9435d21f95782c0ef1679fb58f0 3767 bind9_9.11.2+dfsg-3.dsc ec3acd322dfd045d92485ad5122050ac4ad834ebd0efe7635748f7c62e4e1435 77744 bind9_9.11.2+dfsg-3.debian.tar.xz 101711d67b50d9b4628af158effc25eaeab69dd4a93eae0a572a061ca39cbbf4 18639 bind9_9.11.2+dfsg-3_amd64.buildinfo Files: afa74c589f9c35ba4267b7d9409046f9 3767 net optional bind9_9.11.2+dfsg-3.dsc c508d9821c984afa6f8037002e106043 77744 net optional bind9_9.11.2+dfsg-3.debian.tar.xz 8c6c0528c8f076a438efc0606cd36e9d 1
Bug#883448: marked as done (bind9: FTBFS with -A (arch:all))
Your message dated Mon, 04 Dec 2017 11:48:56 + with message-id and subject line Bug#883448: fixed in bind9 1:9.11.2+dfsg-3 has caused the Debian Bug report #883448, regarding bind9: FTBFS with -A (arch:all) 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.) -- 883448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883448 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bind9 Version: 1:9.11.2+dfsg-2 Severity: serious Justification: FTBFS Hi, Your package FTBFS when performing the arch:all build: | make[1]: Entering directory '/<>/bind9-9.11.2+dfsg' | # TODO: move this to bind9.install | install -c -o bin -g bin -m 444 debian/db.0 /<>/bind9-9.11.2+dfsg/debian/bind9/etc/bind/db.0 | install: cannot create regular file '/<>/bind9-9.11.2+dfsg/debian/bind9/etc/bind/db.0': No such file or directory | debian/rules:129: recipe for target 'override_dh_install' failed | make[1]: *** [override_dh_install] Error 1 | make[1]: Leaving directory '/<>/bind9-9.11.2+dfsg' | debian/rules:47: recipe for target 'binary-indep' failed | make: *** [binary-indep] Error 2 Full build log: https://buildd.debian.org/status/fetch.php?pkg=bind9&arch=all&ver=1%3A9.11.2%2Bdfsg-2&stamp=1512340742&raw=0 KiBi. --- End Message --- --- Begin Message --- Source: bind9 Source-Version: 1:9.11.2+dfsg-3 We believe that the bug you reported is fixed in the latest version of bind9, 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 883...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bernhard Schmidt (supplier of updated bind9 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 04 Dec 2017 10:56:58 +0100 Source: bind9 Binary: bind9 bind9utils bind9-doc bind9-host libbind-dev libbind9-160 libdns169 libirs160 libisc166 liblwres160 libisccc160 libisccfg160 dnsutils libbind-export-dev libdns-export169 libdns-export169-udeb libirs-export160 libirs-export160-udeb libisc-export166 libisc-export166-udeb libisccc-export160 libisccc-export160-udeb libisccfg-export160 libisccfg-export160-udeb Architecture: source Version: 1:9.11.2+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian DNS Packaging Changed-By: Bernhard Schmidt Description: bind9 - Internet Domain Name Server bind9-doc - Documentation for BIND bind9-host - Version of 'host' bundled with BIND 9.X bind9utils - Utilities for BIND dnsutils - Clients provided with BIND libbind-dev - Static Libraries and Headers used by BIND libbind-export-dev - Development files for the exported BIND libraries libbind9-160 - BIND9 Shared Library used by BIND libdns-export169 - Exported DNS Shared Library libdns-export169-udeb - Exported DNS library for debian-installer (udeb) libdns169 - DNS Shared Library used by BIND libirs-export160 - Exported IRS Shared Library libirs-export160-udeb - Exported IRS library for debian-installer (udeb) libirs160 - DNS Shared Library used by BIND libisc-export166 - Exported ISC Shared Library libisc-export166-udeb - Exported ISC library for debian-installer (udeb) libisc166 - ISC Shared Library used by BIND libisccc-export160 - Command Channel Library used by BIND libisccc-export160-udeb - Command Channel Library used by BIND (udeb) libisccc160 - Command Channel Library used by BIND libisccfg-export160 - Exported ISC CFG Shared Library libisccfg-export160-udeb - Exported ISC CFG library for debian-installer (udeb) libisccfg160 - Config File Handling Library used by BIND liblwres160 - Lightweight Resolver Library used by BIND Closes: 883448 883449 Changes: bind9 (1:9.11.2+dfsg-3) unstable; urgency=medium . * Team upload. * Only install files into bind9:any on arch-any builds (Closes: #883448) * Adjust dependencies for udeb packages (Closes: #883449) Checksums-Sha1: e5288d52f7575e7a5f0c6300fdd78670d9d8e405 3767 bind9_9.11.2+dfsg-3.dsc c2c0fcbc37c57c7350b58f0e4d72d854f9c2ec28 77744 bind9_9.11.2+dfsg-3.debian.tar.xz 6f1a9bcbf706066765d74784c12cfbe3721a0194 18639 bind9_9.11.2+dfsg-3_amd64.buildinfo Checksums-Sha256: 8e4c18f76fae876173bc94db49926f5ee721f9435d21f95782c0ef1679fb58f0 3767 b
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> fixed 879974 0.39
Bug #879974 {Done: Stéphane Glondu } [src:llvm-defaults]
llvm-defaults: drop libllvm-ocaml-dev (temporarily)
Marked as fixed in versions llvm-defaults/0.39.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
879974: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879974
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Not a problem in stretch
Processing commands for cont...@bugs.debian.org: > tags 873422 buster sid Bug #873422 [src:oclgrind] oclgrind: Please update to llvm-toolchain 4.0 or, better, 5.0 Added tag(s) buster and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 873422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873422 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: No point in keeping the Qt4 libkmahjongg without kajongg
Processing control commands: > severity -1 serious Bug #875017 [src:libkmahjongg] [libkmahjongg] Future Qt4 removal from Buster Severity set to 'serious' from 'wishlist' -- 875017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875017 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#872028: marked as done (scikit-learn FTBFS on big endian: FAIL: sklearn.feature_extraction.tests.test_feature_hasher.test_hasher_alternate_sign)
Your message dated Mon, 4 Dec 2017 13:30:25 +0100 with message-id and subject line Bug seems to be fixed has caused the Debian Bug report #872028, regarding scikit-learn FTBFS on big endian: FAIL: sklearn.feature_extraction.tests.test_feature_hasher.test_hasher_alternate_sign 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.) -- 872028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872028 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: scikit-learn Version: 0.19.0-1 Severity: serious https://buildd.debian.org/status/package.php?p=scikit-learn&suite=sid ... == FAIL: sklearn.feature_extraction.tests.test_feature_hasher.test_hasher_alternate_sign -- Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/sklearn/utils/testing.py", line 291, in wrapper return fn(*args, **kwargs) File "/«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/sklearn/feature_extraction/tests/test_feature_hasher.py", line 122, in test_hasher_alternate_sign assert_true(len(Xt.data) < len(X[0])) AssertionError: False is not true -- Ran 7994 tests in 367.585s FAILED (SKIP=74, failures=1) debian/rules:88: recipe for target 'python-test2.7' failed make[1]: *** [python-test2.7] Error 1 make[1]: Leaving directory '/«PKGBUILDDIR»' debian/rules:41: recipe for target 'binary-arch' failed make: *** [binary-arch] Error 2 --- End Message --- --- Begin Message --- Source: scikit-learn Source-Version: 0.19.1-1 >From the build logs https://buildd.debian.org/status/logs.php?pkg=scikit-learn&ver=0.19.1-1 there are no longer failures specific to big endian archs: mips is big endian and nop longer fails. Specifically this bug is gone. best regards Ole--- End Message ---
Bug#883473: scikit-learn: FTBFS on several architectures
Package: src:scikit-learn Version: 0.19.1-1 Severity: serious scikit-learn fails to build from source on a number of platforms due to the following failing test: == FAIL: sklearn.neighbors.tests.test_approximate.test_radius_neighbors -- Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/<>/debian/tmp/usr/lib/python2.7/dist-packages/sklearn/neighbors/tests/test_approximate.py", line 229, in test_radius_neighbors sorted_dists_approx))) AssertionError: False is not true -- Ran 8008 tests in 929.227s FAILED (SKIP=62, failures=1) The platforms where this happens are: * arm64 * ppc64el * s390x * powerpc (non-release arch) * ppc64 (non-release arch) This did not happen with the previous version. Best regards Ole
Bug#867391: marked as done (src:scikit-learn: FTBFS on mips64el due to test failures)
Your message dated Mon, 4 Dec 2017 13:49:27 +0100 with message-id <08a2b131-4e94-6b50-dbd5-a268cbad7...@debian.org> and subject line Bug seems to be fixed has caused the Debian Bug report #867391, regarding src:scikit-learn: FTBFS on mips64el due to test failures 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.) -- 867391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867391 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:scikit-learn Version: 0.18-5 Severity: serious Justification: fails to build from source (but built successfully in the past) Although this failure happened when the package was binNMUed to add support for python3.6, it is unrelated. The test failures are for tests run with python2.7. Below is an extract from the build log [1]: == FAIL: /<>/debian/tmp/usr/lib/python2.7/dist-packages/sklearn/tests/test_common.py.test_non_meta_estimators:check_transformer_data_not_an_array(LocallyLinearEmbedding) -- Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/<>/debian/tmp/usr/lib/python2.7/dist-packages/sklearn/utils/testing.py", line 826, in __call__ return self.check(*args, **kwargs) File "/<>/debian/tmp/usr/lib/python2.7/dist-packages/sklearn/utils/testing.py", line 348, in wrapper return fn(*args, **kwargs) File "/<>/debian/tmp/usr/lib/python2.7/dist-packages/sklearn/utils/estimator_checks.py", line 537, in check_transformer_data_not_an_array _check_transformer(name, Transformer, this_X, this_y) File "/<>/debian/tmp/usr/lib/python2.7/dist-packages/sklearn/utils/estimator_checks.py", line 605, in _check_transformer % Transformer) File "/usr/lib/python2.7/dist-packages/numpy/testing/utils.py", line 979, in assert_array_almost_equal precision=decimal) File "/usr/lib/python2.7/dist-packages/numpy/testing/utils.py", line 796, in assert_array_compare raise AssertionError(msg) AssertionError: Arrays are not almost equal to 2 decimals fit_transform and transform outcomes not consistent in (mismatch 75.0%) x: array([[ 1.45e-01, -2.98e-01], [ 2.14e-01, 1.60e-12], [ 2.14e-01, -6.13e-12],... y: array([[ -2.56e-01, 2.98e-01], [ -2.97e-02, -8.49e-13], [ -2.97e-02, 3.37e-12],... == FAIL: /<>/debian/tmp/usr/lib/python2.7/dist-packages/sklearn/tests/test_common.py.test_non_meta_estimators:check_transformer_general(LocallyLinearEmbedding) -- Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/<>/debian/tmp/usr/lib/python2.7/dist-packages/sklearn/utils/testing.py", line 826, in __call__ return self.check(*args, **kwargs) File "/<>/debian/tmp/usr/lib/python2.7/dist-packages/sklearn/utils/testing.py", line 348, in wrapper return fn(*args, **kwargs) File "/<>/debian/tmp/usr/lib/python2.7/dist-packages/sklearn/utils/estimator_checks.py", line 523, in check_transformer_general _check_transformer(name, Transformer, X, y) File "/<>/debian/tmp/usr/lib/python2.7/dist-packages/sklearn/utils/estimator_checks.py", line 605, in _check_transformer % Transformer) File "/usr/lib/python2.7/dist-packages/numpy/testing/utils.py", line 979, in assert_array_almost_equal precision=decimal) File "/usr/lib/python2.7/dist-packages/numpy/testing/utils.py", line 796, in assert_array_compare raise AssertionError(msg) AssertionError: Arrays are not almost equal to 2 decimals fit_transform and transform outcomes not consistent in (mismatch 75.0%) x: array([[ -1.49e-01, -2.98e-01], [ -2.11e-01, 2.92e-12], [ -2.11e-01, 9.62e-12],... y: array([[ -3.56e-02, 2.98e-01], [ -2.56e-01, -4.06e-12], [ -2.56e-01, -9.95e-12],... -- Ran 6891 tests in 3731.118s FAILED (SKIP=17, failures=2) debian/rules:88: recipe for target 'python-test2.7' failed Scott K [1] https://buildd.debian.org/status/fetch.php?pkg=scikit-learn&arch=mips64el&ver=0.18-5%2Bb1&stamp=1499282634&raw=0 --- End Message --- --- Begin Message --- Source: scikit-learn Source-Version: 0.19.1-1 mips64el build successfully now: https://buildd.debian.org/status/fe
Processed: Set bug forwarded
Processing commands for cont...@bugs.debian.org: > forwarded 883473 https://github.com/scikit-learn/scikit-learn/issues/10244 Bug #883473 [src:scikit-learn] scikit-learn: FTBFS on several architectures Set Bug forwarded-to-address to 'https://github.com/scikit-learn/scikit-learn/issues/10244'. > thanks Stopping processing here. Please contact me if you need assistance. -- 883473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883473 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#882778: python-cymruwhois: diff for NMU version 1.6-2.1
Hi Mattia, Many thanks for this, it looks great! Ana On Sun, Dec 3, 2017, at 04:55 PM, Mattia Rizzolo wrote: > Control: tags 882778 + patch > Control: tags 882778 + pending > > Dear maintainer, > > I've prepared an NMU for python-cymruwhois (versioned as 1.6-2.1) and > uploaded it to DELAYED/2. Please feel free to tell me if I > should delay it longer. > > Regards. > > -- > regards, > Mattia Rizzolo > > GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. > more about me: https://mapreri.org : :' : > Launchpad user: https://launchpad.net/~mapreri `. `'` > Debian QA page: https://qa.debian.org/developer.php?login=mattia `- > Email had 2 attachments: > + python-cymruwhois-1.6-2.1-nmu.diff > 4k (text/x-diff) > + signature.asc > 1k (application/pgp-signature)
Processed (with 2 errors): bump llvm-3.8 removal bugs
Processing commands for cont...@bugs.debian.org: > forcemerge 873416 873428 Bug #873416 [src:starpu-contrib] starpu-contrib: Please update to llvm-toolchain 4.0 or, better, 5.0 Bug #873428 [src:starpu-contrib] nvidia-cuda-toolkit: Please update to llvm-toolchain 4.0, or, better, 5.0 873407 was blocked by: 873428 873427 873407 was blocking: 873331 Removed blocking bug(s) of 873407: 873428 873416 was blocked by: 873428 873427 873416 was blocking: 873331 Removed blocking bug(s) of 873416: 873428 Failed to forcibly merge 873416: It is nonsensical for a bug to block itself (or a merged partner): 873428. > severity 873416 serious Failed to set severity of Bug 873416 to serious: failed to get lock on /org/bugs.debian.org/spool/lock/873416 -- Unable to lock /org/bugs.debian.org/spool/lock/873416 Resource temporarily unavailable. Unable to lock /org/bugs.debian.org/spool/lock/873416 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664. Unable to lock /org/bugs.debian.org/spool/lock/873416 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664. Unable to lock /org/bugs.debian.org/spool/lock/873416 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664. Unable to lock /org/bugs.debian.org/spool/lock/873416 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664. Unable to lock /org/bugs.debian.org/spool/lock/873416 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664. Unable to lock /org/bugs.debian.org/spool/lock/873416 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664. Unable to lock /org/bugs.debian.org/spool/lock/873416 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664. Unable to lock /org/bugs.debian.org/spool/lock/873416 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664. Unable to lock /org/bugs.debian.org/spool/lock/873416 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664. at /usr/local/lib/site_perl/Debbugs/Common.pm line 622. > severity 873468 serious Bug #873468 [nvidia-cuda-toolkit] cuda: moving away from clang-3.8 to gcc-6 ? Severity set to 'serious' from 'important' > retitle 873468 nvidia-cuda-toolkit: move away from clang-3.8 Bug #873468 [nvidia-cuda-toolkit] cuda: moving away from clang-3.8 to gcc-6 ? Changed Bug title to 'nvidia-cuda-toolkit: move away from clang-3.8' from 'cuda: moving away from clang-3.8 to gcc-6 ?'. > severity 873407 serious Bug #873407 [src:eztrace-contrib] eztrace-contrib: Please update to llvm-toolchain 4.0 or, better, 5.0 Severity set to 'serious' from 'normal' > -- Stopping processing here. Please contact me if you need assistance. -- 873407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873407 873416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873416 873428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873428 873468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873468 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: llvm-defaults: please drop lld from architectures where lld is not built
Processing control commands: > block 869752 by -1 Bug #869752 [release.debian.org] transition: llvm-defaults to llvm 4.0 869752 was blocked by: 853715 880257 882157 882160 879976 869752 was blocking: 869602 Added blocking bug(s) of 869752: 883477 -- 869752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869752 883477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883477 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#883477: llvm-defaults: please drop lld from architectures where lld is not built
Source: llvm-defaults Version: 0.38 Severity: serious Control: block 869752 by -1 llvm-toolchain-4.0 builds lld-4.0 only for |Architecture: amd64 armel armhf i386 kfreebsd-amd64 kfreebsd-i386 s390 sparc alpha hppa m68k powerpcspe ppc64 sh4 sparc64 x32 mips mipsel But llvm-defaults ships lld for |Architecture: any That causes lld to be uninstallable on e.g. arm64, therefore blocking testing migration. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Processed: bump llvm-3.8 removal bugs - take 2
Processing commands for cont...@bugs.debian.org: > retitle 873428 starpu-contrib: Please update to llvm-toolchain 4.0 or, > better, 5.0 Bug #873428 [src:starpu-contrib] nvidia-cuda-toolkit: Please update to llvm-toolchain 4.0, or, better, 5.0 Changed Bug title to 'starpu-contrib: Please update to llvm-toolchain 4.0 or, better, 5.0' from 'nvidia-cuda-toolkit: Please update to llvm-toolchain 4.0, or, better, 5.0'. > forcemerge 873416 873428 Bug #873416 [src:starpu-contrib] starpu-contrib: Please update to llvm-toolchain 4.0 or, better, 5.0 Bug #873428 [src:starpu-contrib] starpu-contrib: Please update to llvm-toolchain 4.0 or, better, 5.0 Merged 873416 873428 > severity 873416 serious Bug #873416 [src:starpu-contrib] starpu-contrib: Please update to llvm-toolchain 4.0 or, better, 5.0 Bug #873428 [src:starpu-contrib] starpu-contrib: Please update to llvm-toolchain 4.0 or, better, 5.0 Severity set to 'serious' from 'normal' Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 873416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873416 873428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873428 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 873468
Processing commands for cont...@bugs.debian.org: > # cuda 9.0 is in experiental/NEW > tags 873468 + pending Bug #873468 [nvidia-cuda-toolkit] nvidia-cuda-toolkit: move away from clang-3.8 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 873468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873468 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: notfixed 811860 in 201409.0-1
Processing commands for cont...@bugs.debian.org:
> # unconfuse the bts - found+fixed in the same version
> notfixed 811860 201409.0-1
Bug #811860 {Done: Juhani Numminen } [mcrl2] mcrl2:
FTBFS with GCC 6: no matching function for call to
No longer marked as fixed in versions mcrl2/201409.0-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
811860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811860
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: severity of 881663 is serious
Processing commands for cont...@bugs.debian.org: > severity 881663 serious Bug #881663 [llvm-toolchain-5.0] Missing build/Build-Attempted on mips64el and mipsel Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 881663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881663 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 882769 is important
Processing commands for cont...@bugs.debian.org: > severity 882769 important Bug #882769 [live-boot-initramfs-tools] Cannot upgrade from Stretch: cp: target '/lib/live/mount/medium/live/vmlinuz.new' is not a directory Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 882769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882769 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 856545 is serious
Processing commands for cont...@bugs.debian.org: > severity 856545 serious Bug #856545 [liblld-5.0-dev] liblld-5.0-dev: Doesn't depend on liblld-5.0 Severity set to 'serious' from 'minor' > thanks Stopping processing here. Please contact me if you need assistance. -- 856545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856545 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 2 errors): un-mess llvm-3.8 removal bugs - take 3
Processing commands for cont...@bugs.debian.org: > retitle 873427 starpu-contrib: Please update to llvm-toolchain 4.0 or, > better, 5.0 Bug #873427 [src:starpu-contrib] nvidia-cuda-toolkit: Please update to llvm-toolchain 4.0, or, better, 5.0 Changed Bug title to 'starpu-contrib: Please update to llvm-toolchain 4.0 or, better, 5.0' from 'nvidia-cuda-toolkit: Please update to llvm-toolchain 4.0, or, better, 5.0'. > forcemerge 873416 873427 Bug #873416 [src:starpu-contrib] starpu-contrib: Please update to llvm-toolchain 4.0 or, better, 5.0 Bug #873428 [src:starpu-contrib] starpu-contrib: Please update to llvm-toolchain 4.0 or, better, 5.0 Bug #873427 [src:starpu-contrib] starpu-contrib: Please update to llvm-toolchain 4.0 or, better, 5.0 Severity set to 'serious' from 'normal' 873407 was blocked by: 873427 873407 was blocking: 873331 Removed blocking bug(s) of 873407: 873427 873416 was blocked by: 873427 873416 was blocking: 873331 Removed blocking bug(s) of 873416: 873427 873428 was blocked by: 873427 873428 was blocking: 873331 Removed blocking bug(s) of 873428: 873427 Failed to forcibly merge 873416: It is nonsensical for a bug to block itself (or a merged partner): 873427. > block 873416 by 873468 Failed to set blocking bugs of 873416: failed to get lock on /org/bugs.debian.org/spool/lock/merge -- Unable to lock /org/bugs.debian.org/spool/lock/merge Resource temporarily unavailable. Unable to lock /org/bugs.debian.org/spool/lock/merge Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664. Unable to lock /org/bugs.debian.org/spool/lock/merge Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664. Unable to lock /org/bugs.debian.org/spool/lock/merge Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664. Unable to lock /org/bugs.debian.org/spool/lock/merge Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664. Unable to lock /org/bugs.debian.org/spool/lock/merge Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664. Unable to lock /org/bugs.debian.org/spool/lock/merge Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664. Unable to lock /org/bugs.debian.org/spool/lock/merge Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664. Unable to lock /org/bugs.debian.org/spool/lock/merge Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664. Unable to lock /org/bugs.debian.org/spool/lock/merge Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664. at /usr/local/lib/site_perl/Debbugs/Common.pm line 622. > -- Stopping processing here. Please contact me if you need assistance. -- 873407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873407 873416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873416 873427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873427 873428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873428 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: un-mess llvm-3.8 removal bugs - take 4
Processing commands for cont...@bugs.debian.org: > forcemerge 873416 873427 Bug #873416 [src:starpu-contrib] starpu-contrib: Please update to llvm-toolchain 4.0 or, better, 5.0 Bug #873428 [src:starpu-contrib] starpu-contrib: Please update to llvm-toolchain 4.0 or, better, 5.0 Bug #873427 [src:starpu-contrib] starpu-contrib: Please update to llvm-toolchain 4.0 or, better, 5.0 Bug #873428 [src:starpu-contrib] starpu-contrib: Please update to llvm-toolchain 4.0 or, better, 5.0 Merged 873416 873427 873428 > block 873416 by 873468 Bug #873416 [src:starpu-contrib] starpu-contrib: Please update to llvm-toolchain 4.0 or, better, 5.0 Bug #873427 [src:starpu-contrib] starpu-contrib: Please update to llvm-toolchain 4.0 or, better, 5.0 Bug #873428 [src:starpu-contrib] starpu-contrib: Please update to llvm-toolchain 4.0 or, better, 5.0 873416 was not blocked by any bugs. 873416 was blocking: 873331 Added blocking bug(s) of 873416: 873468 873427 was not blocked by any bugs. 873427 was blocking: 873331 Added blocking bug(s) of 873427: 873468 873428 was not blocked by any bugs. 873428 was blocking: 873331 Added blocking bug(s) of 873428: 873468 > thanks Stopping processing here. Please contact me if you need assistance. -- 873416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873416 873427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873427 873428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873428 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#882247: can't even close it
yes, it can be closed with ctrl+q, atleast in my setup. No errors or anything else in the logs if started from the command line. I also tried to start it with safe mode, and then I get a window with Here's a pic that might help: https://img1.picload.org/image/driolrli/selection_099.png On Wed, 29 Nov 2017 04:45:06 +0800 =?utf-8?B?56mN5Li55bC8?= Dan Jacobson wrote: > Maintainer: can you even close it with CTRL+Q or CTRL+W? > >
Bug#883477: marked as done (llvm-defaults: please drop lld from architectures where lld is not built)
Your message dated Mon, 04 Dec 2017 13:53:56 + with message-id and subject line Bug#883477: fixed in llvm-defaults 0.40 has caused the Debian Bug report #883477, regarding llvm-defaults: please drop lld from architectures where lld is not built 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.) -- 883477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883477 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: llvm-defaults Version: 0.38 Severity: serious Control: block 869752 by -1 llvm-toolchain-4.0 builds lld-4.0 only for |Architecture: amd64 armel armhf i386 kfreebsd-amd64 kfreebsd-i386 s390 sparc alpha hppa m68k powerpcspe ppc64 sh4 sparc64 x32 mips mipsel But llvm-defaults ships lld for |Architecture: any That causes lld to be uninstallable on e.g. arm64, therefore blocking testing migration. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: llvm-defaults Source-Version: 0.40 We believe that the bug you reported is fixed in the latest version of llvm-defaults, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 883...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sylvestre Ledru (supplier of updated llvm-defaults package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 04 Dec 2017 14:34:27 +0100 Source: llvm-defaults Binary: llvm llvm-runtime llvm-dev clang clang-tidy clang-format libclang1 libclang-dev lldb lld Architecture: source amd64 Version: 0.40 Distribution: unstable Urgency: medium Maintainer: LLVM Packaging Team Changed-By: Sylvestre Ledru Description: clang - C, C++ and Objective-C compiler (LLVM based) clang-format - Tool to format C/C++/Obj-C code clang-tidy - clang-based C++ linter tool libclang-dev - clang library - Development package libclang1 - C, C++ and Objective-C compiler (LLVM based) lld- LLVM-based linker lldb - Next generation, high-performance debugger llvm - Low-Level Virtual Machine (LLVM) llvm-dev - Low-Level Virtual Machine (LLVM), libraries and headers llvm-runtime - Low-Level Virtual Machine (LLVM), bytecode interpreter Closes: 883477 Changes: llvm-defaults (0.40) unstable; urgency=medium . * Drop lld from architectures where lld is not built (Closes: #883477) Checksums-Sha1: 5ba033a9a529a3d9e0725ef2309d506f7c74346f 2244 llvm-defaults_0.40.dsc c567b61ed4a46acfb2ae03c452cc1a4f4c6d48b8 9308 llvm-defaults_0.40.tar.xz 9b2b02b0416795e740aa220d50bb4b8586f59753 6336 clang-format_4.0-40_amd64.deb 7f3bba73a93149f780bf797a2bc88cc5a6a80862 6180 clang-tidy_4.0-40_amd64.deb 065f9d0440bc3f5e8693887696dc719881a830ac 6636 clang_4.0-40_amd64.deb 2bfbb6ab27eec4627d5e289f1d520fbcde80bc35 6032 libclang-dev_4.0-40_amd64.deb 9abccb0360396b42ed4bed7dbb1e95af8d463ba2 6196 libclang1_4.0-40_amd64.deb 2250dd9d390573bf6db792b9c69659a9b20ab2bd 6004 lld_4.0-40_amd64.deb e404eb8d4e0eeb84f169dfacc48f55b0eb3b85b0 6120 lldb_4.0-40_amd64.deb a998b0c75f717f609749ed46ca65fd1009ff06c8 7913 llvm-defaults_0.40_amd64.buildinfo 3d6fcd8eb4cd041df0b17c56980c2b64b6f62eec 6336 llvm-dev_4.0-40_amd64.deb 298fd1d83571b2f46f38b08c2e88e104f8d127cc 6072 llvm-runtime_4.0-40_amd64.deb eb81d14aa810e8a8fc19d14ccb615bcd0504dfd5 7912 llvm_4.0-40_amd64.deb Checksums-Sha256: c301f27c8452e786dea33fa231526cc74f5db0863bdc51c25a865165033e81f7 2244 llvm-defaults_0.40.dsc d27185fdc436a95ce5587ef0a5457839a830dbe61e76fccea084d63cc422cca2 9308 llvm-defaults_0.40.tar.xz b02dbe821503880d2c145cb6828323d10ef40ab47d6e4140373d4eb4d07a7de2 6336 clang-format_4.0-40_amd64.deb b0ed7146cfa61015c4c61f9aec2da4a6f0d07148ccd6e5fe08fa1b2bcdf22fd2 6180 clang-tidy_4.0-40_amd64.deb 62c56bdcf6fd922e85f68b7dc52cbe907b1c9b7837af4299908c5e4efea51771 6636 clang_4.0-40_amd64.deb 42dd8574391
Bug#877344: [Debian-med-packaging] Bug#877344: python-mne FTBFS: ERROR: Test ICA on raw and epochs
Hi Andreas, I don't have the bandwidth to address this sorry. Also mne 0.13 is now 2 versions behind where we are now. Nobody found the time to do the debian packaging for 0.14 and 0.15 so far. Really sorry about this. Best, Alex On Sun, Dec 3, 2017 at 6:45 PM, Andreas Tille wrote: > Hi, > > could please somebody care for this bug. I admit I do not like the > pattern that RC bugs in python-mne remain unanswered by any of the > uploaders until you get a ping. I would really love if you make sure > to subscribe the package and answer this kind of bugs in a timely > manner. > > Thank you > > Andreas. > > -- > http://fam-tille.de > > ___ > Debian-med-packaging mailing list > debian-med-packag...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/ > debian-med-packaging >
Processed: Bug#882608 marked as pending
Processing commands for cont...@bugs.debian.org: > tag 882608 pending Bug #882608 [src:ruby-mechanize] ruby-mechanize: FTBFS and Debci failure with ruby 2.3.5 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 882608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882608 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#882608: marked as pending
tag 882608 pending thanks Hello, Bug #882608 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/pkg-ruby-extras/ruby-mechanize.git/commit/?id=3a659cb --- commit 3a659cb96d681ffccbbfdda9ad7b250af3f05c2d Author: HIGUCHI Daisuke (VDR dai) Date: Mon Dec 4 23:25:23 2017 +0900 releasing ruby-mechanize version 2.7.5-2 diff --git a/debian/changelog b/debian/changelog index 988c47f..81df816 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,19 @@ +ruby-mechanize (2.7.5-2) unstable; urgency=medium + + * Team upload. + + [ HIGUCHI Daisuke (VDR dai) ] + * fix FTBFS and Debci failure with ruby 2.3.5 (Closes: #882608) + - d/p/clean_up_tests_for_minitest_5_deprecations.patch: new patch. + - d/p/fixes_the_current_test_failures_on_master.patch: new patch. + * remove Ryan Niebur from Uploaders (Closes: #856378) +thanks for previous works. + * support autopkgtest-pkg-ruby. + * eliminate lintian warning: debian-watch-uses-insecure-uri + * bump Standards-Version to 4.1.1 (no changes needed) + + -- HIGUCHI Daisuke (VDR dai) Mon, 04 Dec 2017 23:24:52 +0900 + ruby-mechanize (2.7.5-1) unstable; urgency=medium * Team upload.
Bug#882608: marked as done (ruby-mechanize: FTBFS and Debci failure with ruby 2.3.5)
Your message dated Mon, 04 Dec 2017 15:32:58 +
with message-id
and subject line Bug#882608: fixed in ruby-mechanize 2.7.5-2
has caused the Debian Bug report #882608,
regarding ruby-mechanize: FTBFS and Debci failure with ruby 2.3.5
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.)
--
882608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-mechanize
Version: 2.7.5-1
Severity: serious
Tags: buster sid
https://ci.debian.net/packages/r/ruby-mechanize/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-mechanize.html
...
┌──┐
│ Run tests for ruby2.3 from debian/ruby-test-files.yaml │
└──┘
RUBYLIB=/build/1st/ruby-mechanize-2.7.5/debian/ruby-mechanize/usr/lib/ruby/vendor_ruby:.
GEM_PATH=debian/ruby-mechanize/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
ruby2.3 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\ \{\
\|f\|\ require\ f\ \}
Run options: --seed 47730
# Running:
...DEPRECATED: Use assert_nil if
expecting nil from
/build/1st/ruby-mechanize-2.7.5/test/test_mechanize_page_meta_refresh.rb:115.
This will fail in Minitest 6.
...E..DEPRECATED: assert_send. From
/build/1st/ruby-mechanize-2.7.5/test/test_mechanize.rb:984
.F..E...EDEPRECATED:
assert_send. From /build/1st/ruby-mechanize-2.7.5/test/test_mechanize.rb:946
..DEPRECATED: assert_send. From
/build/1st/ruby-mechanize-2.7.5/test/test_mechanize.rb:965
.DEPRECATED: Use assert_nil if
expecting nil from
/build/1st/ruby-mechanize-2.7.5/test/test_mechanize_cookie.rb:461. This will
fail in Minitest 6.
...DEPRECATED: Use assert_nil if expecting nil from
/build/1st/ruby-mechanize-2.7.5/test/test_mechanize_util.rb:30. This will fail
in Minitest 6.
.DEPRECATED: Use assert_nil if expecting nil from
/build/1st/ruby-mechanize-2.7.5/test/test_mechanize_form_encoding.rb:70. This
will fail in Minitest 6.
.DEPRECATED:
Use assert_nil if expecting nil from
/build/1st/ruby-mechanize-2.7.5/test/test_mechanize_page_link.rb:342. This will
fail in Minitest 6.
..DEPRECATED: Use assert_nil if expecting nil from
/build/1st/ruby-mechanize-2.7.5/test/test_mechanize_page_link.rb:75. This will
fail in Minitest 6.
..
Finished in 1.713436s, 384.0237 runs/s, 1220.9387 assertions/s.
1) Error:
TestMechanize#test_get_http_refresh_disabled:
ArgumentError: header field value cannnot include CR/LF
/usr/lib/ruby/2.3.0/net/http/header.rb:76:in `set_field'
/usr/lib/ruby/2.3.0/net/http/header.rb:41:in `[]='
/build/1st/ruby-mechanize-2.7.5/debian/ruby-mechanize/usr/lib/ruby/vendor_ruby/mechanize/test_case/http_refresh_servlet.rb:6:in
`do_GET'
/build/1st/ruby-mechanize-2.7.5/debian/ruby-mechanize/usr/lib/ruby/vendor_ruby/mechanize/test_case.rb:234:in
`request'
/usr/lib/ruby/vendor_ruby/net/http/persistent.rb:999:in `request'
/build/1st/ruby-mechanize-2.7.5/debian/ruby-mechanize/usr/lib/ruby/vendor_ruby/mechanize/http/agent.rb:274:in
`fetch'
/build/1st/ruby-mechanize-2.7.5/debian/ruby-mechanize/usr/lib/ruby/vendor_ruby/mechanize.rb:464:in
`get'
/build/1st/ruby-mechanize-2.7.5/test/test_mechanize.rb:614:in
`test_get_http_refresh_disabled'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:107:in `block (3 levels) in run'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:204:in `capture_exceptions'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:104:in `block (2 levels) in run'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:255:in `time_it'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:103:in `block in run'
/usr/lib/ruby/vendor_ruby/minitest.rb:350:in `on_signal'
/usr/lib/
Bug#877344: [Debian-med-packaging] Bug#877344: python-mne FTBFS: ERROR: Test ICA on raw and epochs
I will look into updating it in upcoming days On December 4, 2017 8:54:28 AM EST, Alexandre Gramfort wrote: >Hi Andreas, > >I don't have the bandwidth to address this sorry. > >Also mne 0.13 is now 2 versions behind where we are now. >Nobody found the time to do the debian packaging for 0.14 >and 0.15 so far. > >Really sorry about this. > >Best, >Alex > > >On Sun, Dec 3, 2017 at 6:45 PM, Andreas Tille wrote: > >> Hi, >> >> could please somebody care for this bug. I admit I do not like the >> pattern that RC bugs in python-mne remain unanswered by any of the >> uploaders until you get a ping. I would really love if you make sure >> to subscribe the package and answer this kind of bugs in a timely >> manner. >> >> Thank you >> >> Andreas. >> >> -- >> http://fam-tille.de >> >> ___ >> Debian-med-packaging mailing list >> debian-med-packag...@lists.alioth.debian.org >> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/ >> debian-med-packaging >>
Processed: Not a problem in stretch
Processing commands for cont...@bugs.debian.org: > tags 873468 buster sid Bug #873468 [nvidia-cuda-toolkit] nvidia-cuda-toolkit: move away from clang-3.8 Added tag(s) buster and sid. > tags 873407 buster sid Bug #873407 [src:eztrace-contrib] eztrace-contrib: Please update to llvm-toolchain 4.0 or, better, 5.0 Added tag(s) sid and buster. > tags 873416 buster sid Bug #873416 [src:starpu-contrib] starpu-contrib: Please update to llvm-toolchain 4.0 or, better, 5.0 Bug #873427 [src:starpu-contrib] starpu-contrib: Please update to llvm-toolchain 4.0 or, better, 5.0 Bug #873428 [src:starpu-contrib] starpu-contrib: Please update to llvm-toolchain 4.0 or, better, 5.0 Added tag(s) sid and buster. Added tag(s) buster and sid. Added tag(s) buster and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 873407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873407 873416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873416 873427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873427 873428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873428 873468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873468 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:ufo-filters
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:ufo-filters > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). > # remote status report for #882955 (http://bugs.debian.org/882955) > # Bug title: ufo-filters FTBFS with glibc 2.25 > # * https://github.com/ufo-kit/ufo-filters/issues/146 > # * remote status changed: (?) -> closed > # * closed upstream > tags 882955 + fixed-upstream Bug #882955 [src:ufo-filters] ufo-filters FTBFS with glibc 2.25 Added tag(s) fixed-upstream. > usertags 882955 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 882955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#882778: marked as done (python-cymruwhois: sourceful upload needed for the python3.6 transition)
Your message dated Mon, 04 Dec 2017 17:41:34 + with message-id and subject line Bug#882778: fixed in python-cymruwhois 1.6-2.1 has caused the Debian Bug report #882778, regarding python-cymruwhois: sourceful upload needed for the python3.6 transition 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.) -- 882778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882778 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-cymruwhois Version: 1.6-2 Severity: serious Tags: sid bustr Control: block 866335 with -1 Hi, a sourceful upload of python-cymruwhois is needed for the python3.6 transition. Since the python3-cymruwhois is arch:all, it cannot be binNMUed. There are no changes needed to the packaging. Andreas --- End Message --- --- Begin Message --- Source: python-cymruwhois Source-Version: 1.6-2.1 We believe that the bug you reported is fixed in the latest version of python-cymruwhois, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 882...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mattia Rizzolo (supplier of updated python-cymruwhois 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, 03 Dec 2017 17:52:47 +0100 Source: python-cymruwhois Binary: python-cymruwhois python3-cymruwhois python-cymruwhois-doc Architecture: source Version: 1.6-2.1 Distribution: unstable Urgency: medium Maintainer: Ana Custura Changed-By: Mattia Rizzolo Description: python-cymruwhois - Python library for interfacing with the whois.cymru.com service ( python-cymruwhois-doc - python-cymruwhois common documentation python3-cymruwhois - Python library for interfacing with the whois.cymru.com service ( Closes: 882778 Changes: python-cymruwhois (1.6-2.1) unstable; urgency=medium . * Non-maintainer upload. * Mark python-cymruwhois-doc as Multi-Arch: foreign. * Remove a bunch of trailing whitespaces. * Rebuild for Python 3.6. Closes: #882778 Checksums-Sha1: df872e3ba5cfb321dd91500b8794de42b2d78b1e 2404 python-cymruwhois_1.6-2.1.dsc a5a5441141e750b0183f4f639c0451ffd6b534bb 3576 python-cymruwhois_1.6-2.1.debian.tar.xz 678341d4c614fae9d367edbd0141fb4930c269ce 8183 python-cymruwhois_1.6-2.1_amd64.buildinfo Checksums-Sha256: b8e5441955447360d6736c52f4283aa065998b81aec6085b49ade15bb8a6ad81 2404 python-cymruwhois_1.6-2.1.dsc 09c21ec9e2912f0515f83e178085b0f1427e7f4bf4715c0161b17dabed3a8665 3576 python-cymruwhois_1.6-2.1.debian.tar.xz 9edea66803fe05b68deaf4d3d44863cacf1d4a00dd007ec14391419f44034e01 8183 python-cymruwhois_1.6-2.1_amd64.buildinfo Files: f0db269938b49bd0611f49d9ede1fe0f 2404 python optional python-cymruwhois_1.6-2.1.dsc d10b3983720b3f2fadb9321bc9211082 3576 python optional python-cymruwhois_1.6-2.1.debian.tar.xz c77315dc242e05af79ed7e3b2bd18214 8183 python optional python-cymruwhois_1.6-2.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAlokLFkSHG1hdHRpYUBk ZWJpYW4ub3JnAAoJEAgWueGMdiut3zoQAK51MIgS3yR7rlrXL2mMInlWNQ5HzQXI KDY+OuzA0Jy/3zaO9LsStEOavWYJIUSmiWIIB70o9tvWX+HO6pergc7bGA4G4oPj BGJIlDOQYvTD2BeRxRocVtjOUYO/D4E27bxecJS4zGzpVFIT2htjTJL0iYVuHs0k fZD4/o16GMhFGSe2z8Rw936MWT2IevkSj97rwcR7HEOfdro5lqq6rWsqrT8bYIq6 COIC1OHH7GFV/MIxacKNH/Em01hzpfYR1IRTOOti9XQjYMQmTbIoqVw7/zCxSFYY hmatLO0FAcWuBqoRWj4uT13mZiEshsBibQkPxo2TQUVonz8jEkfhxePPC/+dnqJZ JAwoVH4uZSZd+LGgJJGvqzUa8iyX5Yi5j9BMY5DK//QdgPs0h8JzAfsIh/JjmANM gG8UYN8PQuA7VSSM6D/XZTSmX3ukROTeAz3jsOksb33x0PryXXxfspuGyVIvxaji NYBGw+wHD7juHIHbUsjOiibS5k1iRJKHtyNhUQUWjHoW1U8xOFo8iset0Ufuq6sG YAC3JpDpPHdZhLvJpFnAxS3FyC+NIgJiA+vRTWMmoa6bm64eYxehw3NFsnkvW99j T+pAC/Yza3aRXVWIvMjOVTMPP8fddiDnAl4j0E5DBO77wKkR6XDk6cKKa0ILTOJT wVB8Ka5bOV5f =T2Ue -END PGP SIGNATURE End Message ---
Bug#883499: kfilemetadata: depends on libpoppler-qt4 which is about to be removed
Source: kfilemetadata Severity: serious Tags: sid stretch User: pkg-freedesktop-maintain...@lists.alioth.debian.org Usertags: oldlibs poppler-qt4 Control: block 875096 with -1 Hi, kfilemetadata (build-)depends on Poppler Qt4 bindings, which have been removed upstream in Poppler 0.62.0. They will be gone from Debian soon, once we update to that version. kfilemetadata should switch to the Qt5 bindings, or disable Poppler support if the former is not possible. If you have any question don't hesitate to ask. Cheers, Emilio
Bug#883498: kbibtex: depends on libpoppler-qt4 which is about to be removed
Source: kbibtex Severity: serious Tags: sid stretch User: pkg-freedesktop-maintain...@lists.alioth.debian.org Usertags: oldlibs poppler-qt4 Control: block 875096 with -1 Hi, kbibtex (build-)depends on Poppler Qt4 bindings, which have been removed upstream in Poppler 0.62.0. They will be gone from Debian soon, once we update to that version. kbibtex should switch to the Qt5 bindings, or disable Poppler support if the former is not possible. If you have any question don't hesitate to ask. Cheers, Emilio
Bug#883503: prerex: depends on libpoppler-qt4 which is about to be removed
Source: prerex Severity: serious Tags: sid stretch User: pkg-freedesktop-maintain...@lists.alioth.debian.org Usertags: oldlibs poppler-qt4 Control: block 875096 with -1 Hi, prerex (build-)depends on Poppler Qt4 bindings, which have been removed upstream in Poppler 0.62.0. They will be gone from Debian soon, once we update to that version. prerex should switch to the Qt5 bindings, or disable Poppler support if the former is not possible. If you have any question don't hesitate to ask. Cheers, Emilio
Bug#883501: ktikz: depends on libpoppler-qt4 which is about to be removed
Source: ktikz Severity: serious Tags: sid stretch User: pkg-freedesktop-maintain...@lists.alioth.debian.org Usertags: oldlibs poppler-qt4 Control: block 875096 with -1 Hi, ktikz (build-)depends on Poppler Qt4 bindings, which have been removed upstream in Poppler 0.62.0. They will be gone from Debian soon, once we update to that version. ktikz should switch to the Qt5 bindings, or disable Poppler support if the former is not possible. If you have any question don't hesitate to ask. Cheers, Emilio
Bug#883497: okular: depends on libpoppler-qt4 which is about to be removed
Source: okular Severity: serious Tags: sid stretch User: pkg-freedesktop-maintain...@lists.alioth.debian.org Usertags: oldlibs poppler-qt4 Control: block 875096 with -1 Hi, okular (build-)depends on Poppler Qt4 bindings, which have been removed upstream in Poppler 0.62.0. They will be gone from Debian soon, once we update to that version. okular should switch to the Qt5 bindings, or disable Poppler support if the former is not possible. If you have any question don't hesitate to ask. Cheers, Emilio
Bug#883496: comparepdf: depends on libpoppler-qt4 which is about to be removed
Source: comparepdf Severity: serious Tags: sid stretch User: pkg-freedesktop-maintain...@lists.alioth.debian.org Usertags: oldlibs poppler-qt4 Control: block 875096 with -1 Hi, comparepdf (build-)depends on Poppler Qt4 bindings, which have been removed upstream in Poppler 0.62.0. They will be gone from Debian soon, once we update to that version. comparepdf should switch to the Qt5 bindings, or disable Poppler support if the former is not possible. If you have any question don't hesitate to ask. Cheers, Emilio
Bug#883500: calligra: depends on libpoppler-qt4 which is about to be removed
Source: calligra Severity: serious Tags: sid stretch User: pkg-freedesktop-maintain...@lists.alioth.debian.org Usertags: oldlibs poppler-qt4 Control: block 875096 with -1 Hi, calligra (build-)depends on Poppler Qt4 bindings, which have been removed upstream in Poppler 0.62.0. They will be gone from Debian soon, once we update to that version. calligra should switch to the Qt5 bindings, or disable Poppler support if the former is not possible. If you have any question don't hesitate to ask. Cheers, Emilio
Bug#883502: diffpdf: depends on libpoppler-qt4 which is about to be removed
Source: diffpdf Severity: serious Tags: sid stretch User: pkg-freedesktop-maintain...@lists.alioth.debian.org Usertags: oldlibs poppler-qt4 Control: block 875096 with -1 Hi, diffpdf (build-)depends on Poppler Qt4 bindings, which have been removed upstream in Poppler 0.62.0. They will be gone from Debian soon, once we update to that version. diffpdf should switch to the Qt5 bindings, or disable Poppler support if the former is not possible. If you have any question don't hesitate to ask. Cheers, Emilio
Processed: The next release is buster not stretch, and actually add the blocker
Processing commands for cont...@bugs.debian.org: > tags 883497 - stretch Bug #883497 [src:okular] okular: depends on libpoppler-qt4 which is about to be removed Removed tag(s) stretch. > tags 883497 buster Bug #883497 [src:okular] okular: depends on libpoppler-qt4 which is about to be removed Added tag(s) buster. > tags 883498 - stretch Bug #883498 [src:kbibtex] kbibtex: depends on libpoppler-qt4 which is about to be removed Removed tag(s) stretch. > tags 883498 buster Bug #883498 [src:kbibtex] kbibtex: depends on libpoppler-qt4 which is about to be removed Added tag(s) buster. > tags 883499 - stretch Bug #883499 [src:kfilemetadata] kfilemetadata: depends on libpoppler-qt4 which is about to be removed Removed tag(s) stretch. > tags 883499 buster Bug #883499 [src:kfilemetadata] kfilemetadata: depends on libpoppler-qt4 which is about to be removed Added tag(s) buster. > tags 883500 - stretch Bug #883500 [src:calligra] calligra: depends on libpoppler-qt4 which is about to be removed Removed tag(s) stretch. > tags 883500 buster Bug #883500 [src:calligra] calligra: depends on libpoppler-qt4 which is about to be removed Added tag(s) buster. > tags 883501 - stretch Bug #883501 [src:ktikz] ktikz: depends on libpoppler-qt4 which is about to be removed Removed tag(s) stretch. > tags 883501 buster Bug #883501 [src:ktikz] ktikz: depends on libpoppler-qt4 which is about to be removed Added tag(s) buster. > tags 883502 - stretch Bug #883502 [src:diffpdf] diffpdf: depends on libpoppler-qt4 which is about to be removed Removed tag(s) stretch. > tags 883502 buster Bug #883502 [src:diffpdf] diffpdf: depends on libpoppler-qt4 which is about to be removed Added tag(s) buster. > tags 883503 - stretch Bug #883503 [src:prerex] prerex: depends on libpoppler-qt4 which is about to be removed Removed tag(s) stretch. > tags 883503 buster Bug #883503 [src:prerex] prerex: depends on libpoppler-qt4 which is about to be removed Added tag(s) buster. > block 875096 by 883497 883498 883499 883500 883501 883502 883503 Bug #875096 [src:poppler] [poppler] Future Qt4 removal from Buster 875096 was blocked by: 877653 875096 was not blocking any bugs. Added blocking bug(s) of 875096: 883499, 883498, 883503, 883501, 883500, 883497, and 883502 > thanks Stopping processing here. Please contact me if you need assistance. -- 875096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875096 883497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883497 883498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883498 883499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883499 883500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883500 883501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883501 883502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883502 883503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883503 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > block 875096 with 883496 Bug #875096 [src:poppler] [poppler] Future Qt4 removal from Buster 875096 was blocked by: 883497 877653 883503 883498 883499 883502 883500 883501 875096 was not blocking any bugs. Added blocking bug(s) of 875096: 883496 > block 875096 with 883497 Bug #875096 [src:poppler] [poppler] Future Qt4 removal from Buster 875096 was blocked by: 877653 883496 883499 883502 883501 883497 883498 883503 883500 875096 was not blocking any bugs. Ignoring request to alter blocking bugs of bug #875096 to the same blocks previously set > block 875096 with 883498 Bug #875096 [src:poppler] [poppler] Future Qt4 removal from Buster 875096 was blocked by: 877653 883496 883499 883502 883501 883497 883498 883503 883500 875096 was not blocking any bugs. Ignoring request to alter blocking bugs of bug #875096 to the same blocks previously set > block 875096 with 883499 Bug #875096 [src:poppler] [poppler] Future Qt4 removal from Buster 875096 was blocked by: 877653 883496 883499 883502 883501 883497 883498 883503 883500 875096 was not blocking any bugs. Ignoring request to alter blocking bugs of bug #875096 to the same blocks previously set > block 875096 with 883500 Bug #875096 [src:poppler] [poppler] Future Qt4 removal from Buster 875096 was blocked by: 877653 883496 883499 883502 883501 883497 883498 883503 883500 875096 was not blocking any bugs. Ignoring request to alter blocking bugs of bug #875096 to the same blocks previously set > block 875096 with 883501 Bug #875096 [src:poppler] [poppler] Future Qt4 removal from Buster 875096 was blocked by: 877653 883496 883499 883502 883501 883497 883498 883503 883500 875096 was not blocking any bugs. Ignoring request to alter blocking bugs of bug #875096 to the same blocks previously set > block 875096 with 883502 Bug #875096 [src:poppler] [poppler] Future Qt4 removal from Buster 875096 was blocked by: 877653 883496 883499 883502 883501 883497 883498 883503 883500 875096 was not blocking any bugs. Ignoring request to alter blocking bugs of bug #875096 to the same blocks previously set > block 875096 with 883503 Bug #875096 [src:poppler] [poppler] Future Qt4 removal from Buster 875096 was blocked by: 877653 883496 883499 883502 883501 883497 883498 883503 883500 875096 was not blocking any bugs. Ignoring request to alter blocking bugs of bug #875096 to the same blocks previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 875096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875096 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#871068: cbmc: FTBFS: wmm/abstract_event.h:23:7: error: '.abstract_eventt::operation' may be used uninitialized in this function [-Werror=maybe-uninitialized]
Control: tags -1 patch fixed-upstream
Hi,
I've attached a patch to fix this FTBFS. It's based on this upstream commit:
https://github.com/diffblue/cbmc/commit/a057ef562
Thanks,
Juhani
Subject: ensure initialization of PODs
From: Daniel Kroening
Origin:
https://github.com/diffblue/cbmc/commit/a057ef562c232c6aacc71648b7aaa0ea5346b246
Bug-Debian: https://bugs.debian.org/871068
Last-Update: 2017-12-04
--- a/src/goto-instrument/wmm/abstract_event.h
+++ b/src/goto-instrument/wmm/abstract_event.h
@@ -46,7 +46,18 @@
bool RWcumul;
bool RRcumul;
- abstract_eventt()
+ abstract_eventt():
+operation(operationt::Write),
+thread(0),
+id(0),
+local(false),
+WRfence(false),
+WWfence(false),
+RRfence(false),
+RWfence(false),
+WWcumul(false),
+RWcumul(false),
+RRcumul(false)
{
}
Processed: Re: cbmc: FTBFS: wmm/abstract_event.h:23:7: error: '.abstract_eventt::operation' may be used uninitialized in this function [-Werror=maybe-uninitialized]
Processing control commands: > tags -1 patch fixed-upstream Bug #871068 [src:cbmc] cbmc: FTBFS: wmm/abstract_event.h:23:7: error: '.abstract_eventt::operation' may be used uninitialized in this function [-Werror=maybe-uninitialized] Added tag(s) fixed-upstream and patch. -- 871068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871068 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: The next release is buster not stretch, and actually add the blocker
Processing commands for cont...@bugs.debian.org: > tags 883496 - stretch Bug #883496 [src:comparepdf] comparepdf: depends on libpoppler-qt4 which is about to be removed Removed tag(s) stretch. > tags 883496 buster Bug #883496 [src:comparepdf] comparepdf: depends on libpoppler-qt4 which is about to be removed Added tag(s) buster. > block 875096 by 883496 Bug #875096 [src:poppler] [poppler] Future Qt4 removal from Buster 875096 was blocked by: 877653 883496 883499 883502 883501 883497 883498 883503 883500 875096 was not blocking any bugs. Ignoring request to alter blocking bugs of bug #875096 to the same blocks previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 875096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875096 883496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883496 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#883497: marked as done (okular: depends on libpoppler-qt4 which is about to be removed)
Your message dated Mon, 4 Dec 2017 20:21:23 +0200 with message-id <20171204182123.GT18367@localhost> and subject line Already fixed in experimental has caused the Debian Bug report #883497, regarding okular: depends on libpoppler-qt4 which is about to be removed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 883497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883497 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: okular Severity: serious Tags: sid stretch User: pkg-freedesktop-maintain...@lists.alioth.debian.org Usertags: oldlibs poppler-qt4 Control: block 875096 with -1 Hi, okular (build-)depends on Poppler Qt4 bindings, which have been removed upstream in Poppler 0.62.0. They will be gone from Debian soon, once we update to that version. okular should switch to the Qt5 bindings, or disable Poppler support if the former is not possible. If you have any question don't hesitate to ask. Cheers, Emilio --- End Message --- --- Begin Message --- Version: 4:17.08.1-1 Version 4:17.08.1-1 in experimental already switched to Qt5. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed--- End Message ---
Bug#833507: same thing
I got this bug after upgrading wpasupplicant from version 2:2.4-1.1 to version 2:2.6-11. None of my attempts to bring wifi back wasn't successful, until I rolled back wpasupplicant to 2.4. I use Broadcom Limited BCM4352 802.11ac Wireless Network Adapter (rev 03) (14e4:43b1) with broadcom-sta-dkms driver (wl.ko).
Bug#883526: geeqie build does not trap errors from make
Source: geeqie Version: 1:1.3-1 Severity: serious Justification: policy 4.6 User: helm...@debian.org Usertags: rebootstrap The upstream build system of geeqie does not trap all errors from programs executed by make. In src/Makefile.am in the ui_icons.h target, $(GDK_PIXBUF_CSOURCE) is chained with a semicolon. Thus a potential failure is suppressed and a misbuild can result. This is why such behaviour is prohibited by the Debian policy section 4.6. Indeed, cross builds do exhibit exactly that behaviour. Inserting a "set -e;" into the subshell is an easy fix. Helmut
Bug#883500: marked as done (calligra: depends on libpoppler-qt4 which is about to be removed)
Your message dated Mon, 4 Dec 2017 20:46:34 +0200 with message-id <20171204184634.GU18367@localhost> and subject line Closing bugs already fixed in testing has caused the Debian Bug report #883500, regarding calligra: depends on libpoppler-qt4 which is about to be removed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 883500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883500 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: calligra Severity: serious Tags: sid stretch User: pkg-freedesktop-maintain...@lists.alioth.debian.org Usertags: oldlibs poppler-qt4 Control: block 875096 with -1 Hi, calligra (build-)depends on Poppler Qt4 bindings, which have been removed upstream in Poppler 0.62.0. They will be gone from Debian soon, once we update to that version. calligra should switch to the Qt5 bindings, or disable Poppler support if the former is not possible. If you have any question don't hesitate to ask. Cheers, Emilio --- End Message --- --- Begin Message --- These were spurious bugs caused by entries for older versions that are kept in Sources for non-release architectures. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed--- End Message ---
Bug#883498: marked as done (kbibtex: depends on libpoppler-qt4 which is about to be removed)
Your message dated Mon, 4 Dec 2017 20:46:34 +0200 with message-id <20171204184634.GU18367@localhost> and subject line Closing bugs already fixed in testing has caused the Debian Bug report #883498, regarding kbibtex: depends on libpoppler-qt4 which is about to be removed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 883498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883498 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kbibtex Severity: serious Tags: sid stretch User: pkg-freedesktop-maintain...@lists.alioth.debian.org Usertags: oldlibs poppler-qt4 Control: block 875096 with -1 Hi, kbibtex (build-)depends on Poppler Qt4 bindings, which have been removed upstream in Poppler 0.62.0. They will be gone from Debian soon, once we update to that version. kbibtex should switch to the Qt5 bindings, or disable Poppler support if the former is not possible. If you have any question don't hesitate to ask. Cheers, Emilio --- End Message --- --- Begin Message --- These were spurious bugs caused by entries for older versions that are kept in Sources for non-release architectures. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed--- End Message ---
Processed: Re: yp-tools: ftbfs with GCC-7
Processing control commands: > tags -1 patch fixed-upstream Bug #853714 [src:yp-tools] yp-tools: ftbfs with GCC-7 Added tag(s) patch and fixed-upstream. -- 853714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853714 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#853714: yp-tools: ftbfs with GCC-7
Control: tags -1 patch fixed-upstream Hello, Here's a patch to fix this ftbfs (tested on amd64), based on an upstream commit but shortened to get the minimal diff relevant to the build failure. https://github.com/thkukuk/yp-tools/commit/6188e75cc Thanks, Juhani Description: Fix Wrong pointer usage From: Thorsten Kukuk Origin: https://github.com/thkukuk/yp-tools/commit/6188e75cc89c47a786799b73df55a71b777aeb0e Bug-Debian: https://bugs.debian.org/853714 Last-Update: 2017-12-04 --- a/lib/yp_all_host.c +++ b/lib/yp_all_host.c @@ -106,7 +106,7 @@ if (hostname == NULL || hostname[0] == '\0' || indomain == NULL || indomain[0] == '\0' || - inmap == NULL || inmap == '\0') + inmap == NULL || inmap[0] == '\0') return YPERR_BADARGS; res = YPERR_YPERR;
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org:
> forcemerge 859367 883450
Bug #859367 {Done: Matthias Klose } [src:omniorb-dfsg]
omniorb-dfsg: Please migrate to openssl1.1 in buster
Bug #883450 [src:omniorb-dfsg] omniorb-dfsg: FTBFS with openssl-1.1
871056 was blocked by: 859224 859053 859367 859230 858828 858435 828503 828475
859853 859834 858939 859226 859829 828483 871939 850897 851094 859222 828441
859852 859851 859720 859232 858929 859544 858938 853778 870778 859784 851077
851424 850895 851084 859050 828420 844303 882615 867140 859552 873647 851085
858928 859669 851091 854583 859840 828481 859717 858857 859841 859557 859540
828451 859548 882562 859297 851054 858386 859555 859554 859719 850898 859054
851090 859826 851087 835801 870779 828522 859715 858931 859228 858991 872885
851081 853782 858930 859718 858927 859556 858936 859550 858990 851086 859786
828557 851093 859790 828477 851076 859671 847611 882549 828329 859831 858992
859838 827076 873574 882561 859750 859721 859052 851069 828429 875349 859740
859542 859229 859783 859553 859146 858935 858989 859791 859416 858993 859673
850888 859055 851073 828471 859551 863568 859145 851070 859546 859543 859558
859674 828449 828572 828520 851074 874699 859742 858436 859782 859716 859844
858398 828413 848680 859785 851078 850890 851079 870775 859675 859545 859225
850886 858937 851080 859789
871056 was not blocking any bugs.
Added blocking bug(s) of 871056: 883450
Marked Bug as done
The source omniorb-dfsg and version 4.2.2-0.1 do not appear to match any binary
packages
Marked as fixed in versions omniorb-dfsg/4.2.2-0.1.
Marked as found in versions omniorb-dfsg/4.1.6-2.
Added tag(s) experimental, sid, and buster.
Bug #859367 {Done: Matthias Klose } [src:omniorb-dfsg]
omniorb-dfsg: Please migrate to openssl1.1 in buster
Marked as found in versions omniorb-dfsg/4.1.6-2.2.
Merged 859367 883450
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
859367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859367
871056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871056
883450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883450
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: RM: libplexus-containers1.5-java -- RoQA; manual cruft removal needed
Processing control commands:
> block 880829 by -1
Bug #880829 {Done: Emmanuel Bourg } [src:plexus-containers]
plexus-containers FTBFS: ComponentDescriptor.java:[192,44] incompatible types:
java.lang.Class cannot be converted to java.lang.Class
880829 was not blocked by any bugs.
880829 was not blocking any bugs.
Added blocking bug(s) of 880829: 883531
--
880829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880829
883531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883531
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#833507: wpasupplicant: workaround wifi.scan-rand-mac-address=no
Package: wpasupplicant Version: 2:2.6-11 Followup-For: Bug #833507 Dear Maintainer, with one of the sid updates last week my wireless stop working again with the wpa_supplicant[737]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 I remember a workaround for this problem from the past to add into /etc/NetworkManager/NetworkManager.conf the following: [device] wifi.scan-rand-mac-address=no which fixed it again for me. ... network-manager (1.4.0-4) unstable; urgency=medium ... * Fix MAC address randomization. Cherry-pick a couple of upstream commits which work around driver bugs when MAC address randomization is used. (Closes: #835822, #835553) ... Because the last network-manager was from 2017-11-10 and my wlan problem started last week I'm a bit unsure where the root cause is. Maybe the workaround helps someone. Regards Noël -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages wpasupplicant depends on: ii adduser 3.116 ii libc6 2.25-3 ii libdbus-1-3 1.12.2-1 ii libnl-3-200 3.2.27-2 ii libnl-genl-3-200 3.2.27-2 ii libpcsclite1 1.8.22-1 ii libreadline7 7.0-3 ii libssl1.1 1.1.0g-2 ii lsb-base 9.20170808 wpasupplicant recommends no packages. Versions of packages wpasupplicant suggests: pn libengine-pkcs11-openssl pn wpagui -- no debconf information
Bug#877344: [Debian-med-packaging] Bug#877344: python-mne FTBFS: ERROR: Test ICA on raw and epochs
On Mon, 04 Dec 2017, Alexandre Gramfort wrote: >Hi Andreas, >I don't have the bandwidth to address this sorry. >Also mne 0.13 is now 2 versions behind where we are now. >Nobody found the time to do the debian packaging for 0.14 >and 0.15 so far. >Really sorry about this. if only life was easy and fair ;) ... /usr/lib/python2.7/dist-packages/mayavi/core/source.py:209: DeprecationWarning: use "HasTraits.trait_set" instead obj.set(scene=self.scene, parent=self) /usr/lib/python2.7/dist-packages/mayavi/core/module_manager.py:260: DeprecationWarning: use "HasTraits.trait_set" instead obj.set(module_manager=self, scene=self.scene, parent=self) /usr/lib/python2.7/dist-packages/mayavi/tools/pipe_base.py:157: DeprecationWarning: use "HasTraits.trait_get" instead traits = self.get(self.class_trait_names()) /usr/lib/python2.7/dist-packages/mayavi/tools/pipe_base.py:171: DeprecationWarning: use "HasTraits.trait_set" instead **traits) /usr/lib/python2.7/dist-packages/traitsui/qt4/ui_panel.py:833: DeprecationWarning: use "HasTraits.trait_set" instead ).set(item = item, object_name = item.object ) /usr/lib/python2.7/dist-packages/traitsui/qt4/ui_panel.py:809: DeprecationWarning: use "HasTraits.trait_set" instead editor_factory = trait.get_editor().set(**item.editor_args) /usr/lib/python2.7/dist-packages/traitsui/qt4/ui_panel.py:833: DeprecationWarning: use "HasTraits.trait_set" instead ).set(item = item, object_name = item.object ) /usr/lib/python2.7/dist-packages/traitsui/group.py:793: DeprecationWarning: use "HasTraits.trait_set" instead orientation = self.orientation ) ) /usr/lib/python2.7/dist-packages/traitsui/qt4/ui_panel.py:809: DeprecationWarning: use "HasTraits.trait_set" instead editor_factory = trait.get_editor().set(**item.editor_args) /usr/lib/python2.7/dist-packages/traitsui/qt4/ui_panel.py:833: DeprecationWarning: use "HasTraits.trait_set" instead ).set(item = item, object_name = item.object ) Segmentation fault (core dumped) debian/rules:25: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 139 ;) -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik
Processed: dietlibc-dev: linux-libc-dev 4.14.2-1 linux/fs.h does not compile with dietlibc-dev linux/types.h
Processing control commands: > affects -1 src:util-vserver linux-libc-dev Bug #883534 [dietlibc-dev] dietlibc-dev: linux-libc-dev 4.14.2-1 linux/fs.h does not compile with dietlibc-dev linux/types.h Added indication that 883534 affects src:util-vserver and linux-libc-dev -- 883534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883534 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#883534: dietlibc-dev: linux-libc-dev 4.14.2-1 linux/fs.h does not compile with dietlibc-dev linux/types.h
Package: dietlibc-dev Version: 0.34~cvs20160606-7 Severity: serious Control: affects -1 src:util-vserver linux-libc-dev linux-libc-dev 4.13.13-1 -> 4.14.2-1 makes util-vserver FTBFS: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/util-vserver.html ... diet -Os gcc -DHAVE_CONFIG_H -I. -I ./lib -I ./ensc_wrappers -D_GNU_SOURCE -D_REENTRANT -DNDEBUG -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -std=c99 -Wall -pedantic -W -funit-at-a-time -MT lib_internal/lib_internal_libinternal_diet_a-util-cleanupmount.o -MD -MP -MF lib_internal/.deps/lib_internal_libinternal_diet_a-util-cleanupmount.Tpo -c -o lib_internal/lib_internal_libinternal_diet_a-util-cleanupmount.o `test -f 'lib_internal/util-cleanupmount.c' || echo './'`lib_internal/util-cleanupmount.c In file included from lib_internal/util-cleanupmount.c:25:0: /usr/include/linux/fs.h:366:23: error: expected '=', ',', ';', 'asm' or '__attribute__' before '__kernel_rwf_t' typedef int __bitwise __kernel_rwf_t; ^~ Makefile:7565: recipe for target 'lib_internal/lib_internal_libinternal_diet_a-util-cleanupmount.o' failed make[3]: *** [lib_internal/lib_internal_libinternal_diet_a-util-cleanupmount.o] Error 1 The root cause is: /usr/lib/x86_64-linux-gnu/diet/include/linux/fs.h does not exist but /usr/include/linux/fs.h does exist. /usr/lib/x86_64-linux-gnu/diet/include/linux/types.h does exist. The result is a combination of the linux-libc-dev linux/fs.h and the dietlibc-dev linux/types.h. __bitwise is defined in /usr/include/linux/types.h but not in /usr/lib/x86_64-linux-gnu/diet/include/linux/types.h, and /usr/include/linux/fs.h just started using it.
Processed: Re: reportbug locks terminal, refuses echo, requires "reset" after viewing followup
Processing control commands:
> forcemerge 695887 849763 882983
Bug #695887 [reportbug] reportbug locks terminal, refuses echo, requires
"reset" after viewing followup
Bug #849763 [reportbug] reportbug: aborts if you attempt to read "Common issues
with reportbug:"
Marked as found in versions reportbug/7.1.7 and reportbug/6.4.3.
Bug #695887 [reportbug] reportbug locks terminal, refuses echo, requires
"reset" after viewing followup
Marked as found in versions reportbug/7.1.7 and reportbug/7.1.1.
Bug #882983 {Done: Sandro Tosi } [reportbug] Doesn't ask for
description anymore and break afterwards
Severity set to 'normal' from 'grave'
Bug reopened
Ignoring request to alter fixed versions of bug #882983 to the same values
previously set
Marked as found in versions reportbug/6.4.3 and reportbug/7.1.1.
Merged 695887 849763 882983
> tags -1 patch
Bug #695887 [reportbug] reportbug locks terminal, refuses echo, requires
"reset" after viewing followup
Bug #849763 [reportbug] reportbug: aborts if you attempt to read "Common issues
with reportbug:"
Bug #882983 [reportbug] Doesn't ask for description anymore and break afterwards
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
--
695887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695887
849763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849763
882983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882983
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#883536: isc-dhcp FTBFS with libbind-export-dev 1:9.11.2+dfsg-2
Source: isc-dhcp Version: 4.3.5-3 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/isc-dhcp.html ... gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -I/usr/include/bind-export -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_PATH_DHCPD_CONF='"/etc/dhcp/dhcpd.conf"' -D_PATH_DHCPD_DB='"/var/lib/dhcp/dhcpd.leases"' -D_PATH_DHCPD6_DB='"/var/lib/dhcp/dhcpd6.leases"' -D_PATH_DHCLIENT_SCRIPT='"/sbin/dhclient-script"' -D_PATH_DHCLIENT_CONF='"/etc/dhcp/dhclient.conf"' -D_PATH_DHCLIENT_DB='"/var/lib/dhcp/dhclient.leases"' -D_PATH_DHCLIENT6_DB='"/var/lib/dhcp/dhclient6.leases"' -DNSUPDATE -I../includes -I../bind/include -lirs-export -Wl,-z,relro -Wl,-z,now -o svtest test.o libomapi.a -lirs-export -ldns-export -lisc-export /usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/libirs-export.a(dnsconf.o): In function `configure_dnsseckeys.constprop.0': (.text+0x49): undefined reference to `cfg_map_get' (.text+0x5c): undefined reference to `cfg_list_first' (.text+0x89): undefined reference to `cfg_listelt_value' (.text+0x91): undefined reference to `cfg_list_first' (.text+0xbb): undefined reference to `cfg_listelt_value' (.text+0xcd): undefined reference to `cfg_tuple_get' (.text+0xd5): undefined reference to `cfg_obj_asuint32' (.text+0xe7): undefined reference to `cfg_tuple_get' (.text+0xef): undefined reference to `cfg_obj_asuint32' (.text+0x101): undefined reference to `cfg_tuple_get' (.text+0x109): undefined reference to `cfg_obj_asuint32' (.text+0x11c): undefined reference to `cfg_tuple_get' (.text+0x124): undefined reference to `cfg_obj_asstring' (.text+0x1cb): undefined reference to `cfg_tuple_get' (.text+0x1d3): undefined reference to `cfg_obj_asstring' (.text+0x393): undefined reference to `cfg_list_next' (.text+0x3a9): undefined reference to `cfg_list_next' /usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/libirs-export.a(dnsconf.o): In function `irs_dnsconf_load': (.text+0x765): undefined reference to `cfg_obj_destroy' (.text+0x76d): undefined reference to `cfg_parser_destroy' (.text+0x7de): undefined reference to `cfg_parser_create' (.text+0x813): undefined reference to `cfg_type_dnsconf' (.text+0x825): undefined reference to `cfg_parse_file' /usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/libdns-export.a(openssl_link.o): In function `dst__openssl_init': (.text+0x1d4): undefined reference to `CRYPTO_set_mem_functions' (.text+0x23a): undefined reference to `OPENSSL_load_builtin_modules' (.text+0x23f): undefined reference to `ENGINE_load_builtin_engines' (.text+0x244): undefined reference to `ERR_clear_error' (.text+0x252): undefined reference to `CONF_modules_load_file' (.text+0x269): undefined reference to `ENGINE_by_id' (.text+0x286): undefined reference to `ENGINE_set_default' (.text+0x2a0): undefined reference to `ENGINE_free' (.text+0x2e1): undefined reference to `ENGINE_get_default_RAND' (.text+0x2f0): undefined reference to `ENGINE_finish' (.text+0x311): undefined reference to `ENGINE_new' (.text+0x333): undefined reference to `ENGINE_set_RAND' (.text+0x33b): undefined reference to `ENGINE_set_default_RAND' (.text+0x343): undefined reference to `ENGINE_free' /usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/libdns-export.a(openssl_link.o): In function `dst__openssl_destroy': (.text+0x355): undefined reference to `OPENSSL_cleanup' /usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/libdns-export.a(openssl_link.o): In function `dst__openssl_toresult': (.text+0x394): undefined reference to `ERR_get_error' (.text+0x3a9): undefined reference to `ERR_clear_error' /usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/libdns-export.a(openssl_link.o): In function `dst__openssl_toresult3': (.text+0x3f2): undefined reference to `ERR_get_error' (.text+0x48c): undefined reference to `ERR_error_string_n' (.text+0x4ea): undefined reference to `ERR_get_error_line_data' (.text+0x4f4): undefined reference to `ERR_clear_error' /usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/libdns-export.a(openssl_link.o): In function `dst__openssl_getengine': (.text+0x5b6): undefined reference to `ENGINE_get_id' /usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/libdns-export.a(openssldh_link.o): In function `openssldh_cleanup': (.text+0xc): undefined reference to `BN_free' (.text+0x18): undefined reference to `BN_free' (.text+0x24): undefined reference to `BN_free' /usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/libdns-export.a(openssldh_link.o): In function `openssldh_isprivate': (.text+0x6a): undefined reference to `DH_get0_key' /usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/libdns-export.a(openssldh_link.o): In function `openssldh_tofile': (.text+0x124): undefined reference to `DH_get0_key' (.text+0x13d): undefined reference to `DH_get0_pqg' (.text+0x155): undefined reference to `BN_num_bits' (.text+0x1a0): undefined reference to `BN_
Bug#883499: marked as done (kfilemetadata: depends on libpoppler-qt4 which is about to be removed)
Your message dated Mon, 04 Dec 2017 20:51:13 + with message-id and subject line Bug#883499: fixed in kfilemetadata 4:4.14.3-2 has caused the Debian Bug report #883499, regarding kfilemetadata: depends on libpoppler-qt4 which is about to be removed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 883499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kfilemetadata Severity: serious Tags: sid stretch User: pkg-freedesktop-maintain...@lists.alioth.debian.org Usertags: oldlibs poppler-qt4 Control: block 875096 with -1 Hi, kfilemetadata (build-)depends on Poppler Qt4 bindings, which have been removed upstream in Poppler 0.62.0. They will be gone from Debian soon, once we update to that version. kfilemetadata should switch to the Qt5 bindings, or disable Poppler support if the former is not possible. If you have any question don't hesitate to ask. Cheers, Emilio --- End Message --- --- Begin Message --- Source: kfilemetadata Source-Version: 4:4.14.3-2 We believe that the bug you reported is fixed in the latest version of kfilemetadata, 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 883...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pino Toscano (supplier of updated kfilemetadata package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 04 Dec 2017 21:09:54 +0100 Source: kfilemetadata Binary: libkfilemetadata-dev libkfilemetadata4 Architecture: source Version: 4:4.14.3-2 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Pino Toscano Description: libkfilemetadata-dev - library for extracting file metadata -- development files libkfilemetadata4 - library for extracting file metadata Closes: 883499 Changes: kfilemetadata (4:4.14.3-2) unstable; urgency=medium . * Team upload. * Remove PDF support, since poppler-qt4 is dropped upstream (Closes: #883499) - remove the libpoppler-qt4-dev build dependency * Remove Mobipocket support, since libqmobipocket is ported to Qt5 - remove the libqmobipocket-dev build dependency * Bump Standards-Version to 4.1.1, no changes required. * Remove not needed Testsuite header. * Simplify watch file, and switch it to https. Checksums-Sha1: eccfd4b4e563a8e836bcb32959d72e0ca94d9160 2329 kfilemetadata_4.14.3-2.dsc d45153764394e15954a8a95146041ce42e150ffd 3992 kfilemetadata_4.14.3-2.debian.tar.xz 3e9695b74af603cea5087f30aab01bf458b14f8d 20226 kfilemetadata_4.14.3-2_source.buildinfo Checksums-Sha256: c5b2c6d82557e9d5af63a2a0472ffcedef5b8b89d3063a1a96236f14f1423e6b 2329 kfilemetadata_4.14.3-2.dsc 1e770ba99c010734c8b1d9eab05c94d69953f8124fc02f58c4a1b183388a8088 3992 kfilemetadata_4.14.3-2.debian.tar.xz f44cc6ef7a330d0e7fd2887293a4a32182921a49425dd67189efe84ebfb28625 20226 kfilemetadata_4.14.3-2_source.buildinfo Files: f7e320589e610df31a383a666c464361 2329 libs optional kfilemetadata_4.14.3-2.dsc 1cc8f3eece4bdfb8935ac739e0a9410a 3992 libs optional kfilemetadata_4.14.3-2.debian.tar.xz e12c32a66168240384a5975b01ed8cb4 20226 libs optional kfilemetadata_4.14.3-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAlolq8oACgkQLRkciEOx P0049A/+IGNh3o3Xn7Rp2ZWu7l7sFNASXyDT4ZzPBP3LZtV1rDSG61MD3r153X4b tCFf/1dzuVVBniPf030rH94NCCgtXEq/ph+5W6PRFL8cgyrKK4rdgK3YjODZ8sjd gvcUExj+Ed2HtnIdBBXZlhkNxallO7ZRBfMDtp9Fe3w67Ni+MO6Jtt/8xtfow8GE kQKaFb5umXKh2g53HqxzpoUYEJWROQMMwSuV9DVZrYaxXz4d8kf/63TSq6EhbKP2 7gZqdmCgmma2aVPLSlp2HxUG8Pn+GwnPLf1ycT485t/ZXKrNfR311Ze8vmcvqYcr OFvcsMD4hSWSqHKORj5krFtXQMJTiLL1G+V5Wd7eD/ANjj7lyAjxHwzqqrljjpQo vSYi3SGYGHDSwfCppFtmpv9AqJUQOrdh8j8Ouvx8F6mH0yq/OCii3En7mvB3/QDR eM1JzUKWbqwL6N6h3hp31+M5TJQ7xLLxArnaZBzcRTOg5mnVnLM7ZTNPjBAW6T1W zrjiyBbf7u2Rb3IQiW65EMso/+09BbNKM80AdyaIcJCg4y1wX2v2gKGC/gtFYd21 4iztvKe3+KorbzGJTVkA8s1v8Wi0IQP29eb4itNzJkG+w8B/rvJTTo5SvujhEnL/ Dp67ND8gP+G0HIk+kl7aGYYaVhCoB7aK0ZKamUll52MiL7s5XSY= =tVEk -END PGP SIGNATURE End Message ---
Bug#878498: snakemake FTBFS with Python 3.6 as default
On Sun, Dec 03, 2017 at 06:47:48PM +0100, Andreas Tille wrote: > Ping? sorry, I thought I had already done that: my latest WIP state is now pushed; it includes a patch that disables rate limiting for sake of being able to work on the main issue, but I haven't made any progress there yet. signature.asc Description: PGP signature
Bug#851077: marked as done (gnupg-pkcs11-scd: Please migrate to openssl1.1 in buster)
Your message dated Mon, 04 Dec 2017 21:33:53 + with message-id and subject line Bug#851077: fixed in gnupg-pkcs11-scd 0.7.3-4 has caused the Debian Bug report #851077, regarding gnupg-pkcs11-scd: Please migrate to openssl1.1 in buster 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.) -- 851077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851077 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnupg-pkcs11-scd Version: 0.7.3-1 Severity: important Control: block 827061 by -1 Hi, OpenSSL 1.1.0 is about to released. During a rebuild of all packages using OpenSSL this package fail to build. A log of that build can be found at: https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/gnupg-pkcs11-scd_0.7.3-1_amd64-20160529-1423 On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the reasons why it might fail. There are also updated man pages at https://www.openssl.org/docs/manmaster/ that should contain useful information. There is a libssl-dev package available in experimental that contains a recent snapshot, I suggest you try building against that to see if everything works. If you have problems making things work, feel free to contact us. Kurt --- End Message --- --- Begin Message --- Source: gnupg-pkcs11-scd Source-Version: 0.7.3-4 We believe that the bug you reported is fixed in the latest version of gnupg-pkcs11-scd, 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 851...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Alteholz (supplier of updated gnupg-pkcs11-scd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 04 Dec 2017 19:07:31 +0100 Source: gnupg-pkcs11-scd Binary: gnupg-pkcs11-scd Architecture: source amd64 Version: 0.7.3-4 Distribution: sid Urgency: medium Maintainer: Thorsten Alteholz Changed-By: Thorsten Alteholz Description: gnupg-pkcs11-scd - GnuPG smart-card daemon with PKCS#11 support Closes: 851077 864106 Changes: gnupg-pkcs11-scd (0.7.3-4) unstable; urgency=medium . * debian/control: Recompile against libssl-dev. (Closes: #851077) * debian/control: depend on libgcrypt20-dev (Closes: #864106) * debian/control: bump standard to 4.1.1 (no changes) * debian/control: use dh10 * debian/control: remove gnupg-pkcs11-scd-dbg Checksums-Sha1: a950aa9cb149fb42d40356eeb34567d8e41c3ef9 2211 gnupg-pkcs11-scd_0.7.3-4.dsc 2d7e35254df96b295eb2d970021c18f3470ea78a 150358 gnupg-pkcs11-scd_0.7.3.orig.tar.gz 2a52bcdef329dc9f2f94d852eb62958f2e73b4a9 3992 gnupg-pkcs11-scd_0.7.3-4.debian.tar.xz ffb06681945a3ac4437f3d874b80ef1ba4988f5b 52808 gnupg-pkcs11-scd-dbgsym_0.7.3-4_amd64.deb ca82da34793990416e43829f4105c7fa83e9bd5a 6186 gnupg-pkcs11-scd_0.7.3-4_amd64.buildinfo 7316f908c986e9c26291ae7453a8cfab92044c87 26500 gnupg-pkcs11-scd_0.7.3-4_amd64.deb Checksums-Sha256: deeb0afcc5e60f9b353e7af084e70b426b778aba7c719f195d27f4d53a63a0d8 2211 gnupg-pkcs11-scd_0.7.3-4.dsc 04bd11d07b89b0cae40df14e698d35eb5c7067b6c62823dc75fc2ca3b196e338 150358 gnupg-pkcs11-scd_0.7.3.orig.tar.gz 93fca43e7217ea6f5081459ba1821d2265c0869f56b0f9a3c209e86354f8269d 3992 gnupg-pkcs11-scd_0.7.3-4.debian.tar.xz d18b1a11faa4e57a80f66b507e72d10c2010045275ca2cf7b61d0c4674974058 52808 gnupg-pkcs11-scd-dbgsym_0.7.3-4_amd64.deb 64493ef48e2ade884f38180d460c6e1b439b3d0ca90c6cf985e5749086ff856c 6186 gnupg-pkcs11-scd_0.7.3-4_amd64.buildinfo 9f4ebf3ce415409637b28affb9a9a079a4dae678861c9a02a8cd5688c8a4b0c8 26500 gnupg-pkcs11-scd_0.7.3-4_amd64.deb Files: 3850b7db399852b8558bf34b258349d3 2211 utils optional gnupg-pkcs11-scd_0.7.3-4.dsc a91680d73f814bd3a16fa4a72e0ee998 150358 utils optional gnupg-pkcs11-scd_0.7.3.orig.tar.gz 8bbe793a21cf42b52c39e4b433f96f48 3992 utils optional gnupg-pkcs11-scd_0.7.3-4.debian.tar.xz 009652efee6ab2a19e0f7fd33a7668d2 52808 debug optional gnupg-pkcs11-scd-dbgsym_0.7.3-4_amd64.deb 136efc23554e1e71c5a2034cb0b49ce1 6186 utils optional gnupg-pkcs11-scd_0.7.3-4_amd64.buildinfo 93e98ec5909dcad49949c35890810048 26500 utils optional gnupg-pkcs11-scd_0.7.3-4_amd64.deb -BEGIN PGP SIGNATURE- iQKnBAEBCg
Processed: GCC 7 fixes by upstreams
Processing commands for cont...@bugs.debian.org: > forwarded 853713 https://github.com/geommer/yabar/issues/154 Bug #853713 [src:yabar] yabar: ftbfs with GCC-7 Set Bug forwarded-to-address to 'https://github.com/geommer/yabar/issues/154'. > # https://sourceforge.net/p/auber/code/12497/ > tags 853688 + patch fixed-upstream Bug #853688 [src:tulip] tulip: ftbfs with GCC-7 Added tag(s) fixed-upstream and patch. > forwarded 853651 https://sourceforge.net/p/sarg/bugs/171/ Bug #853651 [src:sarg] sarg: ftbfs with GCC-7 Set Bug forwarded-to-address to 'https://sourceforge.net/p/sarg/bugs/171/'. > tags 853651 + fixed-upstream Bug #853651 [src:sarg] sarg: ftbfs with GCC-7 Added tag(s) fixed-upstream. > forwarded 853640 https://github.com/nelhage/reptyr/issues/81 Bug #853640 [src:reptyr] reptyr: ftbfs with GCC-7 Set Bug forwarded-to-address to 'https://github.com/nelhage/reptyr/issues/81'. > tags 853640 + fixed-upstream Bug #853640 [src:reptyr] reptyr: ftbfs with GCC-7 Added tag(s) fixed-upstream. > forwarded 853595 https://github.com/OpenMS/OpenMS/issues/2372 Bug #853595 [src:openms] openms: ftbfs with GCC-7 Set Bug forwarded-to-address to 'https://github.com/OpenMS/OpenMS/issues/2372'. > tags 853595 + fixed-upstream Bug #853595 [src:openms] openms: ftbfs with GCC-7 Added tag(s) fixed-upstream. > # https://github.com/OpenMAMA/OpenMAMA/commit/46345f6d78 > tags 853594 + fixed-upstream Bug #853594 [src:openmama] openmama: ftbfs with GCC-7 Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 853594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853594 853595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853595 853640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853640 853651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853651 853688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853688 853713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853713 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
