Bug#909387: erlang-mode: fails to install with xemacs21
Followup-For: Bug #909387 Control: tag -1 pending Hi, I've backported the fix from sid to stretch and filed a stretch-pu request: https://bugs.debian.org/921811 Andreas
Bug#921725: libu2f-host: CVE-2018-20340
Hi Nicolas, On Fri, Feb 08, 2019 at 08:23:10PM +0100, Nicolas Braud-Santoni wrote: > On Fri, Feb 08, 2019 at 02:08:40PM +0100, Salvatore Bonaccorso wrote: > > Hi, > > > > The following vulnerability was published for libu2f-host. > > > > CVE-2018-20340[0]: > > buffer overflow > > > Hi Salvatore & Sébastien, > > Thanks a lot for the swift report(s). :) > > I just uploaded a fixed version to unstable. Thank you, tracker information is updated already. > I will see about backporting the fix to stretch. while the issue was not yet public, Sébastien did work on an update for stretch-security. Lets see if he would like to release his version of the upload. Regards, Salvatore
Bug#921738: chromium-widevine: Widevine does not work with Netflix
tags 921738 + wontfix
bye
This package is *not* widevine. It is the *support* for the legacy
widevine cdm. You still have to download the widevine cdm from
widevine.com/google. Google prohibits its distribution without a
license:
> "Google Inc. and its affiliates ("Google") own all legal right, title and
> interest in and to the content decryption module software ("Software") and
> related documentation, including any intellectual property rights in the
> Software. You may not use, modify, sell, or otherwise distribute the Software
> without a separate license agreement with Google. The Software is not open
> source software.
>
> If you are interested in licensing the Software, please contact
> widev...@google.com.
This package was removed from newer releases of the chromium package.
The new widevine cdm module (4.10.1196.0) will be loaded directly by
the browser from /usr/lib/chromium/libwidevinecdm.so when you have a
version installed which isn't affected by
https://bugs.debian.org/916058 - you still have to get
libwidevinecdm.so
If you are interested in automatically installing this plugin then
please use the approach by
https://tracker.debian.org/pkg/pepperflashplugin-nonfree and upload
the download helper to contrib/web.
As far as I know, Mozilla has a license to use widevine but not a
license to distribute it. Steam/Valve maybe has a license to
redistribute it (I could be wrong but I thought that it was in their
steam runtime) and the chrome team definitely has a license to
distribute it.
You have to contact netflix directly about their wrong help message
Bug#921822: iodine FTCBFS: uses the wrong pkg-config
Source: iodine
Version: 0.7.0-8
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
src/osflags hard codes the build architecture pkg-config. After making
it substitutable and substituting it (dh_auto_build only supplies it as
a make variable). iodine cross builds successfully. Please consider
applying the attached patch.
Helmut
diff --minimal -Nru iodine-0.7.0/debian/changelog iodine-0.7.0/debian/changelog
--- iodine-0.7.0/debian/changelog 2018-05-15 23:32:00.0 +0200
+++ iodine-0.7.0/debian/changelog 2019-02-09 07:33:00.0 +0100
@@ -1,3 +1,10 @@
+iodine (0.7.0-8.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix FTCBFS: Use a triplet-prefixed pkg-config. (Closes: #-1)
+
+ -- Helmut Grohne Sat, 09 Feb 2019 07:33:00 +0100
+
iodine (0.7.0-8) unstable; urgency=medium
* New version of iodine-client-start (1.0.6 + one commit) pulled from
diff --minimal -Nru iodine-0.7.0/debian/patches/cross.patch
iodine-0.7.0/debian/patches/cross.patch
--- iodine-0.7.0/debian/patches/cross.patch 1970-01-01 01:00:00.0
+0100
+++ iodine-0.7.0/debian/patches/cross.patch 2019-02-09 07:32:12.0
+0100
@@ -0,0 +1,29 @@
+--- iodine-0.7.0.orig/src/osflags
iodine-0.7.0/src/osflags
+@@ -1,5 +1,7 @@
+ #!/bin/sh
+
++: "${PKG_CONFIG:=pkg-config}"
++
+ case $2 in
+ link)
+
+@@ -19,7 +21,8 @@
+ Linux)
+ FLAGS="";
+ [ -e /usr/include/selinux/selinux.h ] && FLAGS="$FLAGS
-lselinux";
+- [ -e /usr/include/systemd/sd-daemon.h ] &&
FLAGS="$FLAGS $(pkg-config --libs libsystemd)";
++
++ "$PKG_CONFIG" --exists libsystemd && FLAGS="$FLAGS
$($PKG_CONFIG --libs libsystemd)"
+ echo $FLAGS;
+ ;;
+ esac
+@@ -35,7 +38,7 @@
+ Linux)
+ FLAGS="-D_GNU_SOURCE"
+ [ -e /usr/include/selinux/selinux.h ] && FLAGS="$FLAGS
-DHAVE_SETCON";
+- [ -e /usr/include/systemd/sd-daemon.h ] &&
FLAGS="$FLAGS -DHAVE_SYSTEMD";
++ "$PKG_CONFIG" --exists libsystemd && FLAGS="$FLAGS
-DHAVE_SYSTEMD";
+ echo $FLAGS;
+ ;;
+ GNU/kFreeBSD|GNU)
diff --minimal -Nru iodine-0.7.0/debian/patches/series
iodine-0.7.0/debian/patches/series
--- iodine-0.7.0/debian/patches/series 2018-05-15 23:32:00.0 +0200
+++ iodine-0.7.0/debian/patches/series 2019-02-09 07:30:44.0 +0100
@@ -2,3 +2,4 @@
verbose-build.patch
0001-osflags-use-pkg-config-for-systemd-support.patch
kfreebsd-hurd.patch
+cross.patch
diff --minimal -Nru iodine-0.7.0/debian/rules iodine-0.7.0/debian/rules
--- iodine-0.7.0/debian/rules 2018-05-15 23:32:00.0 +0200
+++ iodine-0.7.0/debian/rules 2019-02-09 07:32:46.0 +0100
@@ -4,6 +4,8 @@
TMP = $(CURDIR)/debian/$(PACKAGE)
export DEB_BUILD_MAINT_OPTIONS := hardening=+pie,+bindnow
+-include /usr/share/dpkg/buildtools.mk
+export PKG_CONFIG ?= pkg-config
%:
dh $@
Bug#921779: doxygen: FTBFS (LaTeX error)
Dear All, I think there is a major issue with doxygen: #921802 , #921776, #921789, and certainly other seem affected by a recent bug that affect doxygen. For #921776, I cannot compose the PDF in a Sid environment, but I can compose it on my Stretch box. Jerome -- Jerome BENOIT | calculus+at-rezozer^dot*net https://qa.debian.org/developer.php?login=calcu...@rezozer.net AE28 AE15 710D FF1D 87E5 A762 3F92 19A6 7F36 C68B signature.asc Description: OpenPGP digital signature
Bug#921821: exim4: fails to send mail, timeout reached or host closed connection
Package: exim4 Version: 4.92~RC5-1 Severity: important Dear Maintainer, I had fully working exim4, but after some update (I'm not sure which one, but the problem arose few days ago) I started to get Connection timed out error, say: 2019-02-09 10:59:18 1gsLfa-0006zu-QT <= dogs...@riseup.net U=dogsleg P=local S=3591 2019-02-09 11:04:19 1gsLfa-0006zu-QT H=mail.riseup.net [198.252.153.22]: SMTP timeout after initial connection: Connection timed out But still I can delete the message with `exim -Mrm 1gsLfa-0006zu-QT'. I've tried to update to 4.92~RC5-2 and now I'm getting waiting for a remote delivery subprocess to finish, which requires killing exim process even to remove messages from queue, say: 2019-02-09 11:06:23 Start queue run: pid=28694 2019-02-09 11:06:23 1gsLfa-0006zu-QT Spool file is locked (another process is handling this message) 2019-02-09 11:06:23 End queue run: pid=28694 After killing the exim4 process, removing the message and sending another one, I'm getting the following: 2019-02-09 11:09:07 1gsLp5-0007Z5-1Q <= dogs...@riseup.net U=dogsleg P=local S=3591 2019-02-09 11:14:08 1gsLp5-0007Z5-1Q H=mail.riseup.net [198.252.153.22]: Remote host closed connection in response to initial connection And I cannot delete the message: # exiwhat 29084 delivering 1gsLp5-0007Z5-1Q: waiting for a remote delivery subprocess to finish 29088 delivering 1gsLp5-0007Z5-1Q to mail.riseup.net [198.252.153.254]:465 (l.lambe...@gmail.com) # exim -Mrm 1gsLp5-0007Z5-1Q Message 1gsLp5-0007Z5-1Q is locked I still can telnet to mail.riseup.net:465 and even sending messages directly works properly. exim still handles local mail and everything which I'm getting with fetchmail properly. With regards, Lev Lamberov -- Package-specific info: Exim version 4.92-RC5 #5 built 31-Jan-2019 18:25:03 Copyright (c) University of Cambridge, 1995 - 2018 (c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2018 Berkeley DB: Berkeley DB 5.3.28: (September 9, 2013) Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages DANE DKIM DNSSEC Event OCSP PRDR SOCKS TCP_Fast_Open Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz dbmnz dnsdb dsearch nis nis0 passwd Authenticators: cram_md5 plaintext Routers: accept dnslookup ipliteral manualroute queryprogram redirect Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp Fixed never_users: 0 Configure owner: 0:0 Size of off_t: 8 Configuration file search path is /etc/exim4/exim4.conf:/var/lib/exim4/config.autogenerated Configuration file is /var/lib/exim4/config.autogenerated # /etc/exim4/update-exim4.conf.conf # # Edit this file and /etc/mailname by hand and execute update-exim4.conf # yourself or use 'dpkg-reconfigure exim4-config' # # Please note that this is _not_ a dpkg-conffile and that automatic changes # to this file might happen. The code handling this will honor your local # changes, so this is usually fine, but will break local schemes that mess # around with multiple versions of the file. # # update-exim4.conf uses this file to determine variable values to generate # exim configuration macros for the configuration file. # # Most settings found in here do have corresponding questions in the # Debconf configuration, but not all of them. # # This is a Debian specific file dc_eximconfig_configtype='smarthost' dc_other_hostnames='' dc_local_interfaces='127.0.0.1' dc_readhost='riseup.net' dc_relay_domains='' dc_minimaldns='true' dc_relay_nets='' dc_smarthost='mail.riseup.net::465' CFILEMODE='644' dc_use_split_config='true' dc_hide_mailname='false' dc_mailname_in_oh='true' dc_localdelivery='maildir_home' mailname:localhost # /etc/default/exim4 EX4DEF_VERSION='' # 'combined' - one daemon running queue and listening on SMTP port # 'no' - no daemon running the queue # 'separate' - two separate daemons # 'ppp' - only run queue with /etc/ppp/ip-up.d/exim4. # 'nodaemon' - no daemon is started at all. # 'queueonly' - only a queue running daemon is started, no SMTP listener. # setting this to 'no' will also disable queueruns from /etc/ppp/ip-up.d/exim4 QUEUERUNNER='combined' # how often should we run the queue QUEUEINTERVAL='30m' # options common to quez-runner and listening daemon COMMONOPTIONS='' # more options for the daemon/process running the queue (applies to the one # started in /etc/ppp/ip-up.d/exim4, too. QUEUERUNNEROPTIONS='' # special flags given to exim directly after the -q. See exim(8) QFLAGS='' # Options for the SMTP listener daemon. By default, it is listening on # port 25 only. To listen on more ports, it is recommended to use # -oX 25:587:10025 -oP /run/exim4/exim.pid SMTPLISTENEROPTIONS='' -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE,
Bug#921781: fis-gtm: FTBFS (dh_auto_configure fails)
Hi, that's caused by missing icu-config (#920900) On Sat, Feb 09, 2019 at 12:15:16AM +, Santiago Vila wrote: > -- Check for working C compiler: /usr/bin/cc > -- Check for working C compiler: /usr/bin/cc -- works > -- Detecting C compiler ABI info > > [... snipped ...] ... the relevant part was snipped here: -- Detecting C compiler ABI info - done -- Detecting C compile features -- Detecting C compile features - done --> OS = Linux / ARCH = x86_64 -- Bootstraping from pre-generated sources. CMake Error at CMakeLists.txt:756 (message): Unable to find 'icu-config'. Set ICUCONFIG in CMake cache. I need to check how to work around this. Its a bit ugly to drop something with "wontfix" in this release state ... Kind regards Andreas. -- http://fam-tille.de
Bug#810964: EDAC bug #810964 effects 4.8 too
I'm seeing bug #810964 occur in Xen 4.8 as well. Perhaps #810964 should be reassigned to xen-hypervisor-common or src:xen ? I don't know whether it effects Xen 4.11 yet... -- (\___(\___(\__ --=> 8-) EHM <=-- __/)___/)___/) \BS (| ehem+sig...@m5p.com PGP 87145445 |) / \_CS\ | _ -O #include O- _ | / _/ 8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445
Bug#915524: Acknowledgement (RFS: filemanager-actions/3.4-1 [ITP])
On Sat, Feb 9, 2019 at 1:07 AM Carlos Maddela wrote: > The reason I put it in the -dev package was that this documentation was> more > related to the API and not so much in end user's interests. Other > packages that have it this way are libnautilus-extension-dev and > network-manager-dev. Those aren't good examples since neither of those source packages ships a -doc package. :) Thanks, Jeremy Bicha
Bug#921820: fwupd: provide a network service file
Package: fwupd Version: 1.1.4-1 Severity: important In its current form, fwupd does not refresh its database on a periodic basis. Please provide a database update service file so that fwupd can periodically update its database. rrs@priyasi:/var/tmp/$ sudo fwupdmgr update No upgrades for XPS 13 9370 System Firmware, current is 0.1.5.1: 0.1.5.1=same, 0.1.4.0=older, 0.1.3.3=older, 0.1.2.1=older, 0.1.2.0=older 10:28 ♒♒♒ ☺ rrs@priyasi:/var/tmp/$ sudo fwupdmgr get-updates Firmware metadata has not been updated for 30 days and may not be up to date. Update now? (Requires internet connection) [y|N]: y Fetching metadata https://cdn.fwupd.org/downloads/firmware.xml.gz Downloading… [***] Less than one minute remaining… Fetching signature https://cdn.fwupd.org/downloads/firmware.xml.gz.asc XPS 13 9370 System Firmware has firmware updates: GUID:7ceaf7a8-0611-4480-9e30-64d8de420c7c GUID:43ea5588-d9a4-5031-8ad3-308045302d6b GUID:230c8b18-8d9b-53ec-838b-6cfc0383493a ID: com.dell.uefi7ceaf7a8.firmware Update Version: 0.1.6.3 Update Name: XPS 13 9370 System Update Update Summary: Firmware for the Dell XPS 13 9370 Update Remote ID:lvfs Update Checksum: SHA1(ce74ca63e86e2844a37748fefbdaf2eaaa36345a) Update Location: https://fwupd.org/downloads/af59a2314c4881ffc02e3a204327d765d0fd256b-Signed_1152921504627870090.cab Update Description: This stable release fixes the following issues: • Fixed the incorrect Windows operating system logon message that is displayed on the lock screen of Windows. • Fixed the issue where the characters fail to display on the screen while typing continuously. • Enabled support for Intel Turbo Boost Technology on I3-8310U processors that was disabled by default. • Optimized the battery diagnostics in Dell Enhanced Pre-boot System Assessment (ePSA). 13:18 ♒♒♒ ☺ rrs@priyasi:/var/tmp/$ sudo fwupdmgr update Downloading 0.1.6.3 for XPS 13 9370 System Firmware... Fetching firmware https://fwupd.org/downloads/af59a2314c4881ffc02e3a204327d765d0fd256b-Signed_1152921504627870090.cab Downloading… [***] Less than one minute remaining… Decompressing… [***] Authenticating…[***] failed to run update_prepare() on upower: Cannot install update when not on AC power unless forced 13:27 ♒♒♒☹ => 1 rrs@priyasi:/var/tmp/$ sudo fwupdmgr update Downloading 0.1.6.3 for XPS 13 9370 System Firmware... Decompressing… [***] Authenticating…[***] Updating XPS 13 9370 System Firmware… ] Scheduling…[***] An update requires a reboot to complete. Restart now? [Y|n]: -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (900, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_USER, TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fwupd depends on: ii libappstream-glib8 0.7.14-1 ii libarchive13 3.3.3-4 ii libc6 2.28-6 ii libefiboot137-1 ii libefivar1 37-1 ii libelf10.175-2 ii libfwupd2 1.1.4-1 ii libgcab-1.0-0 1.2-2 ii libglib2.0-0 2.58.2-4 ii libgnutls303.6.6-2 ii libgpg-error0 1.35-1 ii libgpgme11 1.12.0-6 ii libgudev-1.0-0 232-2 ii libgusb2 0.3.0-1 ii libjson-glib-1.0-0 1.4.4-2 ii libpolkit-gobject-1-0 0.105-25 ii libsmbios-c2 2.4.1-1 ii libsoup2.4-1 2.64.2-2 ii libsqlite3-0 3.26.0+fossilbc891ac6b-2 ii libuuid1 2.33.1-0.1 Versions of packages fwupd recommends: ii bolt 0.7-2 pn fwupd-signed ii python3 3.7.2-1 fwupd suggests no packages. -- no debconf information
Bug#915524: Acknowledgement (RFS: filemanager-actions/3.4-1 [ITP])
On 9/2/19 1:14 am, Jeremy Bicha wrote: > > 2. Why do you have gtk-doc stuff in your -dev package instead of in > your -doc package? > Hi, The reason I put it in the -dev package was that this documentation was more related to the API and not so much in end user's interests. Other packages that have it this way are libnautilus-extension-dev and network-manager-dev. Please let me know if you'd still like it moved to the -doc package. Cheers, Carlos Maddela
Bug#921819: Please consider dropping dependency on s6 / s6-setuidgid
Package: apt-listbugs Version: 0.1.28 Severity: normal Hi, I was rather suprised to have the whole suite of s6 supervision binaries installed on my system. Turns out the s6 package was installed by apt-listbugs via Recommends [1]. It looks to me, that all the functionality that you need is provided by either setpriv or runuser. Both those tools are shipped by util-linux and thus available on every system, as util-linux is marked as essential. Please consider dropping the dependency on s6 / s6-setuidgid an use either setpriv or runuser (it's not entirely clear if you want a PAM session or not in your case. If not, the former tool is what you want). Regards, Michael [1] https://salsa.debian.org/frx-guest/apt-listbugs/commit/60fe655dad963804290228a3886406016a3a82ee -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages apt-listbugs depends on: ii apt 1.8.0~rc2 ii ruby1:2.5.1 ii ruby-debian 0.3.9+b8 ii ruby-gettext3.2.9-1 ii ruby-soap4r 2.0.5-4 ii ruby-unicode0.4.4-2+b9 ii ruby-xmlparser 0.7.3-3+b2 Versions of packages apt-listbugs recommends: ii ruby-httpclient 2.8.3-1 ii s6 2.7.2.2-3 Versions of packages apt-listbugs suggests: ii epiphany-browser [www-browser] 3.30.3-1 ii firefox [www-browser] 65.0-1 ii google-chrome-stable [www-browser] 72.0.3626.96-1 ii lynx [www-browser] 2.8.9rel.1-3 ii reportbug 7.5.2 ii sensible-utils 0.0.12 ii w3m [www-browser] 0.5.3-37 ii xdg-utils 1.1.3-1 -- no debconf information
Bug#921473: [deb...@kitterman.com: Bug#921473: calibre: Invalid maintainer address]
Hi Scott, please let us know if you'd us to stop CCing you, I imagine you're very busy right now! Hi Norbert, On Fri, Feb 08, 2019 at 05:32:34PM +0900, Norbert Preining wrote: > Hi Nicholas, > > I just want to be sure that despite "interesting" decisions I can have > access to the repositories I maintain. Which is not the case on salsa. :-o Oh, now I see... You lost access to preining, and thus maintainer-level access to both the repository and messages. :-( > > It would have been nice to have received notification of the new > > project location...but at any rate, for the purposes of reintegrating > > Sorry, I posted a blog about it, but did not inform you personally. My > failure. P.S. No worries, we're resolving it now. P.S. I'm terrible about following even the blogs of close friends, but I've enjoyed several of your articles over the years! > > Would you like to work on the integration or shall I? No idea about > > I will cum grano salis take over the master/upstream/pristine-tar branch > from your work, because this is what is in Debian uploaded. > > For future work, I have added you to the collaborators of my > calibre-debian git, so you can pull/push directly to the github repo. > > But please wait until I have updated the gh to match salsa, thanks. Do you still have a copy of your branch? I'm interested in diffing between them to check if I missed something. > > Also, at the moment are you able to dput the next upload of Calibre, > > or will I need to? > > I can do that. I have DM rights for all my packages. I just couldn't > upload cssparser which I had packaged also already 2 months ago, but > wasn't able to upload since I am no DD. Oh my, more duplicated work :-p That's something you should have gotten credit for... > Thanks for your understanding and help! You're welcome :-) By the way, thank you for maintaining TeX for all these years...that package must have been a TONNE of work. Cheers, Nicholas signature.asc Description: PGP signature
Bug#921818: Please don't print "debug" output during installation
Package: libu2f-udev
Version: 1.1.7-1
Severity: normal
Hi,
when installing the package, I the the following on stdout:
libu2f-udev (1.1.7-1) wird eingerichtet ...
udevadm trigger -s hidraw -a ATTRS{idVendor}=="1050" -a
ATTRS{idProduct}=="0113|0114|0115|0116|0120|0200|0402|0403|0406|0407|0410" -v
udevadm trigger -s hidraw -a ATTRS{idVendor}=="2581" -a
ATTRS{idProduct}=="f1d0" -v
udevadm trigger -s hidraw -a ATTRS{idVendor}=="1e0d" -a
ATTRS{idProduct}=="f1d0|f1ae" -v
udevadm trigger -s hidraw -a ATTRS{idVendor}=="096e|2ccf" -a
ATTRS{idProduct}=="0880" -v
udevadm trigger -s hidraw -a ATTRS{idVendor}=="096e" -a
ATTRS{idProduct}=="0850|0852|0853|0854|0856|0858|085a|085b|085d" -v
udevadm trigger -s hidraw -a ATTRS{idVendor}=="24dc" -a
ATTRS{idProduct}=="0101" -v
udevadm trigger -s hidraw -a ATTRS{idVendor}=="10c4" -a
ATTRS{idProduct}=="8acf" -v
udevadm trigger -s hidraw -a ATTRS{idVendor}=="1a44" -a
ATTRS{idProduct}=="00bb" -v
udevadm trigger -s hidraw -a ATTRS{idVendor}=="2abe" -a
ATTRS{idProduct}=="1002" -v
udevadm trigger -s hidraw -a ATTRS{idVendor}=="1ea8" -a
ATTRS{idProduct}=="f025" -v
udevadm trigger -s hidraw -a ATTRS{idVendor}=="20a0" -a
ATTRS{idProduct}=="4287" -v
udevadm trigger -s hidraw -a ATTRS{idVendor}=="18d1" -a
ATTRS{idProduct}=="5026" -v
udevadm trigger -s hidraw -a ATTRS{idVendor}=="0483" -a
ATTRS{idProduct}=="cdab" -v
...
Please consider hiding this debug output. It's not really useful in the
common case. For a second I was confused and thought something was
broken. Less noise is better.
Regards,
Michael
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libu2f-udev depends on:
ii udev 240-5
libu2f-udev recommends no packages.
libu2f-udev suggests no packages.
-- no debconf information
Bug#921817: liblvm2cmd.so: undefined symbols: needs -ldevmapper-event
Package: liblvm2cmd2.03 Version: 2.03.02-2 Severity: minor File: /lib/x86_64-linux-gnu/liblvm2cmd.so.2.03 User: debian...@lists.debian.org Usertags: undefined-symbol adequate liblvm2cmd.so needs to link with -ldevmapper-event, see the output of adequate, symtree and objdump below. I detected this on amd64 but the Debian build log scanner also detected dpkg-buildpackage complaining about it and other underlinking in lvm2 on most architectures, see the w3m/getbuildlog output below. I filed this bug at severity minor since I'm not sure if there are any programs using the lvm2cmd lib or if they already use the libdevmapper- event symbols and link with the -ldevmapper-event flag or not. This bug report brought to you by adequate: http://bonedaddy.net/pabs3/log/2013/02/23/inadequate-software/ $ lib=/lib/x86_64-linux-gnu/liblvm2cmd.so.2.03 $ link=/lib/x86_64-linux-gnu/libdevmapper-event.so.1.02.1 $ pkg="$(dpkg-query --search "$lib" | sed s/:.*//)" $ src="$(grep-aptavail --no-field-names --show-field Source:Package --field Package --exact-match --pattern "$pkg")" $ first="$(printf '%s' "$src" | head --bytes 1)" $ adequate "$pkg" liblvm2cmd2.03:amd64: undefined-symbol /lib/x86_64-linux-gnu/liblvm2cmd.so.2.03 => dm_event_register_handler liblvm2cmd2.03:amd64: undefined-symbol /lib/x86_64-linux-gnu/liblvm2cmd.so.2.03 => dm_event_handler_get_dso liblvm2cmd2.03:amd64: undefined-symbol /lib/x86_64-linux-gnu/liblvm2cmd.so.2.03 => dm_event_handler_get_event_mask liblvm2cmd2.03:amd64: undefined-symbol /lib/x86_64-linux-gnu/liblvm2cmd.so.2.03 => dm_event_handler_set_dmeventd_path liblvm2cmd2.03:amd64: undefined-symbol /lib/x86_64-linux-gnu/liblvm2cmd.so.2.03 => dm_event_handler_set_dso liblvm2cmd2.03:amd64: undefined-symbol /lib/x86_64-linux-gnu/liblvm2cmd.so.2.03 => dm_event_get_registered_device liblvm2cmd2.03:amd64: undefined-symbol /lib/x86_64-linux-gnu/liblvm2cmd.so.2.03 => dm_event_handler_create liblvm2cmd2.03:amd64: undefined-symbol /lib/x86_64-linux-gnu/liblvm2cmd.so.2.03 => dm_event_handler_set_event_mask liblvm2cmd2.03:amd64: undefined-symbol /lib/x86_64-linux-gnu/liblvm2cmd.so.2.03 => dm_event_handler_set_timeout liblvm2cmd2.03:amd64: undefined-symbol /lib/x86_64-linux-gnu/liblvm2cmd.so.2.03 => dm_event_handler_set_uuid liblvm2cmd2.03:amd64: undefined-symbol /lib/x86_64-linux-gnu/liblvm2cmd.so.2.03 => dm_event_handler_destroy liblvm2cmd2.03:amd64: undefined-symbol /lib/x86_64-linux-gnu/liblvm2cmd.so.2.03 => dm_event_unregister_handler $ man adequate | grep -A4 undefined-symbol undefined-symbol The symbol has not been found in the libraries linked with the binary. Either the binary either needs to be linked with an additional shared library, or the dependency on the shared library package that provides this symbol is too weak. References: Debian Policy §3.5, §8.6, §10.2. $ lddtree "$lib" liblvm2cmd.so.2.03 => /lib/x86_64-linux-gnu/liblvm2cmd.so.2.03 (interpreter => none) libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 ld-linux-x86-64.so.2 => /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 libdevmapper.so.1.02.1 => /lib/x86_64-linux-gnu/libdevmapper.so.1.02.1 libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 libblkid.so.1 => /lib/x86_64-linux-gnu/libblkid.so.1 libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 libaio.so.1 => /lib/x86_64-linux-gnu/libaio.so.1 libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 $ symtree "$lib" /lib/x86_64-linux-gnu/liblvm2cmd.so.2.03 libsystemd.so.0 => sd_bus_flush_close_unref,sd_bus_error_free,sd_bus_message_unref,sd_bus_error_has_name,sd_bus_message_read,sd_bus_open_system,sd_bus_call_method libdevmapper.so.1.02.1 => !?! useless link !?! libselinux.so.1 => is_selinux_enabled,matchpathcon,freecon,lsetfilecon,setfscreatecon libudev.so.1 => udev_device_unref,udev_enumerate_unref,udev_new,udev_device_new_from_devnum,udev_enumerate_scan_devices,udev_queue_new,udev_list_entry_get_next,udev_device_get_devnode,udev_device_get_is_initialized,udev_unref,udev_enumerate_add_match_subsystem,udev_enumerate_new,udev_queue_unref,udev_enumerate_get_list_entry,udev_device_get_property_value,udev_device_get_sysattr_value,udev_list_entry_get_name,udev_device_get_devlinks_list_entry,udev_queue_get_udev_is_active,udev_device_new_from_syspath libblkid.so.1 =>
Bug#919659: live-build: building in docker fails with mounting /proc unmount /sys [UPDATE]
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921815 and https://salsa.debian.org/installer-team/debootstrap/merge_requests/26
Bug#921816: gvfs: CVE-2019-3827: Incorrect authorization in admin backend allows privileged users to read and modify arbitrary files without prompting for password
Source: gvfs Version: 1.38.1-2 Severity: important Tags: security upstream Forwarded: https://gitlab.gnome.org/GNOME/gvfs/issues/355 Control: found -1 1.30.4-1 Hi, The following vulnerability was published for gvfs. CVE-2019-3827[0]: |Incorrect authorization in admin backend allows privileged users to |read and modify arbitrary files without prompting for password If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-3827 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3827 [1] https://gitlab.gnome.org/GNOME/gvfs/issues/355 Regards, Salvatore
Bug#921815: debootstrap umount "host" /proc when running in a Docker container
Package: debootstrap Version: 1.0.110~bpo9+1 Hi When running debootstrap inside a Docker container, debootstrap umount both /proc and $TARGET/proc. This is due to a missing check at: https://salsa.debian.org/installer-team/debootstrap/blob/67a3c1c5f7ef44a6596f75b787289b3392c50759/scripts/debian-common#L104 Due to the missing check debootstrap umount "$TARGET/proc", which is a symlink to /proc [1]. I will open a MR shortly. [1] https://salsa.debian.org/installer-team/debootstrap/blob/67a3c1c5f7ef44a6596f75b787289b3392c50759/scripts/debian-common#L68 - Kristian Klausen
Bug#921814: lintian: spelling_exceptions() only considers binary packages
Package: lintian Version: 2.6.0 Severity: normal Hi, the function spelling_exceptions() only considers binary packages to add exceptions to the spell checking. This leads to situation where tags like spelling-error-in-patch-description are emitted depending on whether a binary package was added to the lintian call. An example is the src:alot package where we used to have an override for spelling-error-in-patch-description but then discovered that lintian will complain about an unused tag when we also add the binary package: $ lintian --pedantic --display-info --display-experimental alot_0.8-1.dsc alot_0.8-1_amd64.changes I: alot source: out-of-date-standards-version 4.2.1 (released 2018-08-25) (current is 4.3.0) I: alot source: testsuite-autopkgtest-missing X: alot source: upstream-metadata-file-is-missing I: alot source: unused-override spelling-error-in-patch-description debian/patches/0003-alot-UnicodeEncodeError-for-search-queries-with-non-.patch alot a lot N: 0 tags overridden; 1 unused override $ lintian --pedantic --display-info --display-experimental alot_0.8-1.dsc I: alot source: out-of-date-standards-version 4.2.1 (released 2018-08-25) (current is 4.3.0) I: alot source: testsuite-autopkgtest-missing X: alot source: upstream-metadata-file-is-missing N: 1 tag overridden (1 warning) I think what instead should happen is, that the function also considers the source package, specifically the Source and Binary fields. Thanks! cheers, josch
Bug#921751: python-rdflib-tools: Code injection from current working directory
Control: retitle -1 python-rdflib-tools: CVE-2019-7653: Code injection from
current working directory
Hi Gabriel!
On Fri, Feb 08, 2019 at 09:49:07PM +0100, Gabriel Corona wrote:
> Package: python-rdflib-tools
> Version: 4.2.2-1
> Severity: normal
> Tags: security
>
> The CLI tools in python-rdflib-tools can from load python modules
> found in the current directory. This happens because "python -m"
> appends the current directory in the python path.
>
> $ echo 'print("Something")' > cgi.py
> $ rdf2dot
> INFO:rdflib:RDFLib Version: 4.2.2
> Something
> Reading from stdin as None...
>
> The local cgi.py file is loaded instead of the system one.
>
> There are probably other instances of this in the Debian
> archive. Constructs such as:
>
> python -m "$some_module"
> python -c "$some_code"
> $some_command | python
>
> can lead to code injection from current working directory
MITRE has assigned CVE-2019-7653 for this issue.
For those following the bug, this likely does not affect the upstream
project itself and is Debian specifc, as the Debian packaging AFAICS
replaces the respective scripts/tools by wrappers invoking python -m
as described by Gabriel (please correct me if I'm wrong).
Regards,
Salvatore
Bug#921164: kubectx: FTBFS in sid
On Fri, Feb 08, 2019 at 05:31:02PM +0100, Santiago Vila wrote:
> Hi. The following patch may help, but I have not tested it
> (please double-check before uploading).
>
> Thanks.
>
> --- a/debian/rules
> +++ b/debian/rules
> @@ -1,5 +1,5 @@
> #!/usr/bin/make -f
> -#export DH_VERBOSE = 1
> +export TERM=dumb
>
> %:
> dh $@
This patch is okay in sbuild, thanks for the help. I will upload it
later.
--
ChangZhuo Chen (陳昌倬) czchen@{czchen,debconf,debian}.org
http://czchen.info/
Key fingerprint = BA04 346D C2E1 FE63 C790 8793 CC65 B0CD EC27 5D5B
signature.asc
Description: PGP signature
Bug#921813: netplan.io: After install of netplan.io, ifupdown keeps dhclient running
Package: netplan.io Version: 0.95-2 Severity: normal Dear Maintainer, I've noticed that when I install the package netplan.io, the package ifupdown is not removed automatically. Empty install of Debian Buster(a3), only selected 'system utilities' during setup (no 'Desktop', no 'print server'), updated/dist-upgraded. - install package netplan.io - configure a static IP in netplan config (renderer: networkd), set dhcp4 and dhcp6 to 'no', and run "netplan try" - after some time, the dhclient daemon still running in the background (from package ifupdown) reassigns the interface a dhcp address that may be different than the static IP set using netplan. Killing dhclient worked, until a reboot showd that dhclient was active again. 'apt-get remove ifupdown' fixed it for me, but I do not know of any side-effects of removing this package. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages netplan.io depends on: ii iproute2 4.20.0-2 ii libc6 2.28-6 ii libglib2.0-0 2.58.2-4 ii libuuid1 2.33.1-0.1 ii libyaml-0-20.2.1-1 ii python33.7.2-1 ii python3-netifaces 0.10.4-1+b1 ii python3-yaml 3.13-2 ii systemd240-5 netplan.io recommends no packages. Versions of packages netplan.io suggests: ii wpasupplicant 2:2.6-21 -- no debconf information
Bug#859122: about 500 DLAs missing from the website
Hello all Holger Levsen merged the generated DLAs and I've worked to create the /lts tree to show them separated from the DSA. I have moved to this new /lts folder the DLAs from years 2014, 2015 and 2016 that we had already, and remove them from the /security tree and removed references to DLAs in the Makefiles/indexes in /security. I think it's mostly done, I've closed all the related MR except one, but there are some small tasks left, that I hope we can solve together: * I have initially copied the content of /security/ to /lts/security, removed subfolders that I think are not needed (audit, key-rollover, oval, undated) and some other files that I think they were not needed too. Then I did a search and replace DSA -> DLA, dsa- -> dla- in the scripts, makefiles and indexes, and fixed the paths, and built locally (with "make) and I couldn't spot errors, but I don't trust every file that is currently in /lts/security is needed or has been used with my "make" command, so a review of the folder (comparing it with /security) done by an LTS or security team member, is welcome. * The README needs to be reviewed and adapted (I just did the search and replace dsa -> dla and DSA -> DLA). * I guess that parse-advisory.pl (and maybe others) can be removed, but I was not confident to do it without advice. * I didn't check the results of the generated RSS feeds. If anybody uses RSS readers, a review is welcome too. * The /lts/security//index.*.html files show the last advisory for the cases where there are several files with the same beginning (e.g. for DSA- and DSA--2, both html files are generated, but the index only points to the -2 file). If this is not the intended behaviour, changes in index.wml and Makefiles are needed. * Please review the content (text, links) of these files: /lts/index.wml /lts/security/index.wml I've tried to be short (for the case translators are fast and then you decide to heavy rewrite, to not to loose much work). * Translations have been handled, but I've left the *title* of these files unchanged: french/lts/security/*/dla*.wml russian/lts/security/*/dla*.wml danish/lts/security/*/dla*.wml japanese/lts/security/*/dla*.wml All those files have title "LTS Security Advisories from " (being the year: 2014, or 2015, or 2016). I guess translators can do a quick search and replace with the correct sentence and they don't need to update the commit hash, that's already done. I'll contact translators and point them to this message. * This new /lts section of the website is not referenced yet in other places of the Debian website. I'm not sure if it should be referenced in /security, in /releases/, or in both. There is also the temptation of creating a link in the homepage but there is also the suggestion of reducing the links in the homepage, so... For now, I'll try to add it to the sitemap and see how many references to the LTS wiki page we have currently, to see if any of them can be replaced with link to this section in the website. But I'll wait some days to do it because it's not clear for me if you want to populate the section to cover all the aspects of LTS, or keep it only/mainly for security stuff. * We still need the Apache redirects, so the people that try the old URLs (wether directly because they knew, or via the security tracker), find the files they need. What we need to do is send a patch to https://salsa.debian.org/dsa-team/mirror/dsa-puppet/blob/master/modules/roles/templates/apache-www.debian.org.erb that sets the redirect from https://www.debian.org/security/any_year/dla-whatever to https://www.debian.org/security/lts/any_year/dla-whatever * Adaptation in the security tracker so the new URL paths are used from now on is also needed. Thanks for reading so long! Kind regards El 8/2/19 a las 15:52, Holger Levsen escribió: > Hi Antoine, > > On Sun, Feb 03, 2019 at 02:08:06PM +0100, Salvatore Bonaccorso wrote: >> Thanks for working on this. > > indeed! > >> On Fri, Feb 01, 2019 at 01:44:10PM -0500, Antoine Beaupré wrote: >>> On 2018-12-19 18:05:36, Antoine Beaupré wrote: The DLAs are visible here: https://www-staging.debian.org/security/2018/dla-1580 > > that one is also visible on > https://www.debian.org/security/2018/dla-1580 now \o/ > One thing that's unclear is how the entries get added to the main list in: https://www-staging.debian.org/security/2018/ >> IMHO they should not be mixed into the same namespace as the DSAs. >> https://www.debian.org/security/ is very specific to the >> debian-security-announce list and contains items for e.g. contacting >> the Debian security team or referecing the respective FAQ. > > I agree. > > (Thus I think > https://salsa.debian.org/webmaster-team/webwml/merge_requests/50 should > be cloded and not merged.) > > OTOH I plan to review > https://salsa.debian.org/webmaster-team/webwml/merge_requests/53 once > more and then merge it.) > >> I think having a dedicated
Bug#921812: mldonkey-server: Add systemd service file for better security
Package: mldonkey-server Version: 3.1.6-1+b1 Severity: wishlist Tags: patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear Maintainer, It would nice to have a systemd service file for starting/stopping the daemon. It would avoid problems like #920466 and improve security due various restrictions that systemd can place. Attached is service file that we have tested for some simple operations. It lets the log get collected by journald on systems running systemd allowing for better log rotation too. Thanks, - -- Sunil - -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IN.UTF-8, LC_CTYPE=en_IN.UTF-8 (charmap=UTF-8), LANGUAGE=en_IN.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mldonkey-server depends on: ii adduser3.118 ii debconf [debconf-2.0] 1.5.70 ii libbz2-1.0 1.0.6-9 ii libc6 2.28-5 ii libgcc11:8.2.0-14 ii libgd3 2.2.5-5 ii libjpeg62-turbo1:1.5.2-2+b1 ii libpng16-161.6.36-2 ii libstdc++6 8.2.0-14 ii lsb-base 10.2018112800 ii mime-support 3.61 ii ucf3.0038+nmu1 ii zlib1g 1:1.2.11.dfsg-1 mldonkey-server recommends no packages. mldonkey-server suggests no packages. -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE5xPDY9ZyWnWupXSBQ+oc/wqnxfIFAlxeN80RHHN1bmlsQG1l ZGhhcy5vcmcACgkQQ+oc/wqnxfI/FQ//ehnR13Ji5Up0G/onwHyarHM+Fd5whjmn +clBJG28zX42ttgvFfbYokpEF6hoa0UeojNCKUayAlZIP+hK4opDv6u6dCABIr7H hJczQt+sVgumRmzwXtxEQIzgz1cz60CGxSo9QTJprFm5Lq+ZdoaTPczruaOUDMGA 5/6slk4QTiAD8mYwArH1ajGEj0qkea/A5YZjvMXjwpckXGqzwuaoiR6ApelNrZYm ZPscdPMHW+eLRUkhNXxbGB2KUCCAiRxRwYpbpdzvesYG7m1OCIw2M6X5rcR0uIcA cBYH2SKkqWo59hy6d5VZ21tGwhdsps4rRK4nFJXYRC64K8IMSOMfRcF6nkgzYugP QAsfLVrgy3PivkRKsoW572gR+ofEqTPX+Lo/+RBJFUCkSYf1JQBZSRPGBDm7veK7 8jyBNDqckXqhDpXbdEmBEvDfyiMpVfTa4Ec3VT0re75+q7Y2IFY2FEzmHoweAyCy LrcjahXZjdjM4QSBPpSnkoaPi+1yWHvlAh2thSFsD7ct2cNHn5dzTg/8qgrdMM0y xAajptd70Cg9j8Twi8U4F/bFV5xxbyjK0GvrDHaGPBeEFt4IClR3BAQRazwZ2mQo FgDomWH1KsSkkllMfg08pz1voDJWyBNdSAnwASTgQ3rI2UiIwz6HbRr/4psWIUuy MIQM+kyuXpU= =H4cX -END PGP SIGNATURE- [Unit] Description=MLDonkey: Multi-protocol, peer-to-peer file sharing server After=syslog.target network.target ConditionPathExists=/var/lib/mldonkey/downloads.ini Documentation=man:mlnet(1) http://mldonkey.sourceforge.net/Main_Page [Service] ExecStart=/usr/bin/mlnet Group=mldonkey LockPersonality=yes NoNewPrivileges=yes PrivateDevices=yes PrivateMounts=yes PrivateTmp=yes PrivateUsers=yes ProtectControlGroups=yes ProtectHome=yes ProtectKernelModules=yes ProtectKernelTunables=yes ProtectSystem=strict ReadWritePaths=/var/lib/mldonkey RestrictAddressFamilies=AF_UNIX AF_INET AF_INET6 RestrictRealtime=yes StateDirectory=mldonkey SystemCallArchitectures=native Type=simple User=mldonkey WorkingDirectory=/var/lib/mldonkey [Install] WantedBy=multi-user.target
Bug#921811: stretch-pu: package erlang/19.2.1+dfsg-2+deb9u2
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu
Hi,
the erlang-mode package cannot be installed along xemacs21 (#909387).
Backport the "fix" from unstable that removed xemacs21 from the list
of supported emacs versions. The package is already uploaded.
Andreas
diff -Nru erlang-19.2.1+dfsg/debian/changelog
erlang-19.2.1+dfsg/debian/changelog
--- erlang-19.2.1+dfsg/debian/changelog 2017-03-22 13:31:29.0 +0100
+++ erlang-19.2.1+dfsg/debian/changelog 2019-02-08 23:28:34.0 +0100
@@ -1,3 +1,15 @@
+erlang (1:19.2.1+dfsg-2+deb9u2) stretch; urgency=medium
+
+ [ Andreas Beckmann ]
+ * Non-maintainer upload.
+ * Backport removal of xemacs21 support from 1:21.2+dfsg-2.
+
+ [ Sergei Golovan ]
+ * Do not install Erlang mode for XEmacs since it isn't supposed to work
+with it (closes: #909387).
+
+ -- Andreas Beckmann Fri, 08 Feb 2019 23:28:34 +0100
+
erlang (1:19.2.1+dfsg-2+deb9u1) stretch-security; urgency=high
* Applied a patch from the upstream which fixes CVE-2017-1000385
diff -Nru erlang-19.2.1+dfsg/debian/erlang-mode.emacsen-install
erlang-19.2.1+dfsg/debian/erlang-mode.emacsen-install
--- erlang-19.2.1+dfsg/debian/erlang-mode.emacsen-install 2012-05-06
20:05:40.0 +0200
+++ erlang-19.2.1+dfsg/debian/erlang-mode.emacsen-install 2019-02-08
20:35:56.0 +0100
@@ -10,9 +10,13 @@
if [ ${FLAVOR} = emacs ]; then exit 0; fi
+FLAVORTEST=`echo $FLAVOR | cut -c-6`
+
+# Erlang mode doesn't work with XEmacs anymore (see bug #909387)
+if [ ${FLAVORTEST} = xemacs ]; then exit 0; fi
+
echo install/${PACKAGE}: Handling install for emacsen flavor ${FLAVOR}
-FLAVORTEST=`echo $FLAVOR | cut -c-6`
if [ ${FLAVORTEST} = xemacs ] ; then
SITEFLAG="-no-site-file"
else
Bug#921810: RM: crossfire-client-sounds -- ROM; Files included in crossfire-client by upstream
Package: ftp.debian.org Severity: normal crossfire-client version 1.73.0 release tarball included the sound files in it, superseding the need for a separate source package for the sounds.
Bug#921809: rustc: LLVM ERROR: Undefined temporary symbol (rust-wasm-bindgen-macro-support/ppc64el)
Package: rustc Version: 1.32.0+dfsg1-1 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu disco rust-wasm-bindgen-macro-support fails to build on ppc64el in both Debian and Ubuntu with the following error: [...] Compiling wasm-bindgen-macro-support v0.2.33 (/<>) Running `rustc --crate-name wasm_bindgen_macro_support src/lib.rs --color never --crate-type lib --emit=dep-info,link -C debuginfo=2 -C metadata=6a9909accf772696 -C extra-filename=-6a9909accf772696 --out-dir /<>/target/powerpc64le-unknown-linux-gnu/debug/deps --target powerpc64le-unknown-linux-gnu -C incremental=/<>/target/powerpc64le-unknown-linux-gnu/debug/incremental -L dependency=/<>/target/powerpc64le-unknown-linux-gnu/debug/deps -L dependency=/<>/target/debug/deps --extern proc_macro2=/<>/target/powerpc64le-unknown-linux-gnu/debug/deps/libproc_macro2-f042c85f95f84ab4.rlib --extern quote=/<>/target/powerpc64le-unknown-linux-gnu/debug/deps/libquote-2d04f78c87b252dc.rlib --extern syn=/<>/target/powerpc64le-unknown-linux-gnu/debug/deps/libsyn-c8c5acb28d4f9481.rlib --extern wasm_bindgen_backend=/<>/target/powerpc64le-unknown-linux-gnu/debug/deps/libwasm_bindgen_backend-a1b9fd8d5e269fc0.rlib --extern wasm_bindgen_shared=/<>/target/powerpc64le-unknown-linux-gnu/debug/deps/libwasm_bindgen_shared-b86d12bd4c252229.rlib -C debuginfo=2 --cap-lints warn -C linker=powerpc64le-linux-gnu-gcc -C link-arg=-Wl,-z,relro --remap-path-prefix /<>=/usr/share/cargo/registry/wasm-bindgen-macro-support-0.2.33` LLVM ERROR: Undefined temporary symbol error: Could not compile `wasm-bindgen-macro-support`. [...] (https://buildd.debian.org/status/fetch.php?pkg=rust-wasm-bindgen-macro-support=ppc64el=0.2.33-1=1549258418=0) There is no such error on other release architectures. This blocks bootstrap / installability of a substantial number of rust crates on this architecture. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature
Bug#910462: inspircd: New upstream release 2.0.26
This package is now three releases and fifteen months out of date. If you're not going to update it then please just remove it. We ship our own .deb packages now anyway. ~ Peter "SaberUK" Powell
Bug#921800: nvchecker: FTBFS (failing tests)
On February 8, 2019 7:59:10 PM EST, Santiago Vila wrote: >> It looks like a network access problem. The whole point of this >> package is to check online sources, so it's hard to test it without >> network access. I was able to build it just fine in my schroot, but I >> may have to disable the tests so the buildds can operate... > >If you have to do that, please do so. fair enough > Packages must not use the >network during the build, other than installing the build-dependencies. >This is actually written in Release Policy. > >Think about somebody building packages in a desert island and the >package failing because it can't connect to the outside world. > >However, I don't deliberately disable network access in my >autobuilders, so if just by looking at my build log you remembered >that your package was doing network access, that's a good thing anyway >:-) > >[ While we are at it, please try uploading in source-only form > (dpkg-buildpackage -S). It helps me a lot by preventing certain kind > of bugs to propagate to testing (where I usually do my test builds). > This also creates and keeps archived official build logs for the "all" > architecture ]. > I'm with you. I always do so whenever I can, but this was the first upload and needed to be a binary upload to go through NEW... regards Afif
Bug#921441: dsh: Suggested package "update-cluster" not available
> > I wanted to try dsh with the background to check (upgrade) all nodes on our > Ganeti cluster (see [1]). > > This is the first time I wanted to use dsh. > > Unfortunately, the suggested package "update-cluster" is not available on > Debian/buster AMD64. > > Is this a known issue? > If not, shall I open a bug report? > maybe we should remove suggestion to a removed package. update-cluster was a way to manage list of hosts. I doubt many people use NIS host groups these days, so how do people manage the list of hosts these days?
Bug#921800: nvchecker: FTBFS (failing tests)
Hi. Correction: I can't find the network issue in Release Policy right now but it's a Debian Policy violation anyway. (In other words: please don't do it :-) Thanks.
Bug#921800: nvchecker: FTBFS (failing tests)
> It looks like a network access problem. The whole point of this > package is to check online sources, so it's hard to test it without > network access. I was able to build it just fine in my schroot, but I > may have to disable the tests so the buildds can operate... If you have to do that, please do so. Packages must not use the network during the build, other than installing the build-dependencies. This is actually written in Release Policy. Think about somebody building packages in a desert island and the package failing because it can't connect to the outside world. However, I don't deliberately disable network access in my autobuilders, so if just by looking at my build log you remembered that your package was doing network access, that's a good thing anyway :-) [ While we are at it, please try uploading in source-only form (dpkg-buildpackage -S). It helps me a lot by preventing certain kind of bugs to propagate to testing (where I usually do my test builds). This also creates and keeps archived official build logs for the "all" architecture ]. Thanks.
Bug#917723: golang-github-mitchellh-mapstructure-dev: regression in 1.1.2 caused packer FTBFS
Package: golang-github-mitchellh-mapstructure-dev Version: 1.1.2-1 Followup-For: Bug #917723 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Control: severity -1 normal I just found one critical library[1][2] was already patched to depend on this bug behaviour. So I vendored the old mapstructure in packer, to ease the stress before buster freeze. [1] https://tracker.debian.org/pkg/golang-github-spf13-viper [2] https://github.com/spf13/viper/issues/579 -BEGIN PGP SIGNATURE- iQFEBAEBCgAuFiEE85F2DZP0aJKsSKyHONAPABi+PjUFAlxeJPkQHHpoc2pAZGVi aWFuLm9yZwAKCRA40A8AGL4+NTkTCACMBFOvl2b3Q9BLRmkQUSoFw7GbK0glRXd0 4W5FMZPbVk8Y4BO+F9tOcHipv6GZZrsptwAnkuTkhlfRmPGxgUu0RAInE9ce9+2v L064i7BLdqVIhMLLRIvazLSBtRUSTw5ZgaBaI1Zs9LQjLHI7CEwf3+U5e7nRfh3E t2ZYgRa3G8vvmOaWYPEFpuIje640WJjvPmhcNfX2Pqkgqckej/6IP+tDxQgT/abz +wRmaBbkVcsJK4sYHwTTQf34ZtP9vK2kNnYlqV18OIMc1J+b3sOQ/lFOojOgTeVo 07Qyy81xsub+PGwkRSZhvsQFtP3BSMGM+vCiUb/zxP9RnJIw7jPv =Uc6v -END PGP SIGNATURE-
Bug#921800: nvchecker: FTBFS (failing tests)
Hello, On February 8, 2019 7:15:55 PM EST, Santiago Vila wrote: >Package: src:nvchecker >Version: 1.3-1 >Severity: serious >Tags: ftbfs > >Dear maintainer: > >I tried to build this package in buster but it failed: > > [...] > >async with session.get(url) as res: >_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ >_ _ _ _ > >self = 0x7f4ba58c7c50> > >async def __aenter__(self): >> return await to_asyncio_future(client.fetch(self.req)) >E tornado.httpclient.HTTPClientError: HTTP 502: Proxy Error > >nvchecker/source/tornado_httpclient.py:62: HTTPClientError ... >The build was made in my autobuilder with "dpkg-buildpackage -A" >and it also fails here: > >https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/nvchecker.html > >where you can get a full build log if you need it. > >If this is really a bug in one of the build-depends, please use >reassign and affects, >so that this is still visible in the BTS web page for this package. > It looks like a network access problem. The whole point of this package is to check online sources, so it's hard to test it without network access. I was able to build it just fine in my schroot, but I may have to disable the tests so the buildds can operate... regards Afif
Bug#905697: kdepimlibs: don't depend on libical
What about porting it to libical3? That might be easier. I tried to build it
and it does need some changes, but I don't think keeping libical2 is feasible.
See the attached for the error.
Scott K
On Friday, February 08, 2019 10:46:21 PM Sandro Knauß wrote:
> Hey,
>
> for me it looks like we won't be able to get kdepimlibs without libical 2
> for buster.
> Keep in mind, that kdepimlibs is an old grufted lib set that we also would
> like to kill. But we also have other packages depending on it like:
> * basket
> * kopete (it has a QT5 version in experimental, but this is suitable as
> replacement yet).
> and other that may can be killed.
>
> extract libical 2 out of kdepimlibs is not that simple, as the whole
> interface will leak into akonadi-calendar, calcore, calutils,...
>
> In short I won't have the time to do the work and test it in the near
> future.
>
> I added pino to this bug report, as pino successfully extracted other parts
> of old kdelibs/kdepimlibs.
>
> hefee
>
> --
>
> On Donnerstag, 17. Januar 2019 12:11:46 CET Emilio Pozuelo Monfort wrote:
> > On 11/01/2019 13:37, Emilio Pozuelo Monfort wrote:
> > > On 08/08/2018 10:38, Emilio Pozuelo Monfort wrote:
> > >> Source: kdepimlibs
> > >> Version: 4:4.14.10-10
> > >> Severity: serious
> > >> Control: block 884128 with -1
> > >>
> > >> Hi,
> > >>
> > >> libical2 from src:libical is superseded by libical3 (src:libical3).
> > >>
> > >> Please either port kdepimlibs to libical3 or try to disable the
> > >> libical support, so that we can only ship src:libical3 in buster.
> > >
> > > Could someone who knows kdepimlibs take a look at this? Can we disable
> > > libical support in kdepimlibs for buster? This is the last blocker for
> > > the libical 2 removal.
> >
> > Hi Sandro,
> >
> > Lisandro said you may be able to help with this. Do you know if libical
> > support could be disabled in kdepimlibs, or if the newer version libical3
> > could be used?
> >
> > >From [1] it seems that libical is kind of optional, though I don't know
> > >if
> > >we
> >
> > can disable the bits to drop that or if those bits have rdeps. Since
> > kdepimlibs is the last rdep of the old libical version, fixing this would
> > allow us to drop that one from buster. Otherwise the RC bugs that it has
> > will need to be fixed and we'll have to ship with two versions of the
> > library.
> >
> > Thanks,
> > Emilio
> >
> > [1]
> > https://sources.debian.org/src/kdepimlibs/4:4.14.10-10/CMakeLists.txt/#L81
/home/kdepimlibs-4.14.10/kcalcore/icalformat_p.cpp: In static member function
'static icaltimetype KCalCore::ICalFormatImpl::writeICalDate(const QDate&)':
/home/kdepimlibs-4.14.10/kcalcore/icalformat_p.cpp:2304:7: error:
'icaltimetype' {aka 'struct icaltimetype'} has no member named 'is_utc'; did
you mean 'is_date'?
t.is_utc = 0;
^~
is_date
/home/kdepimlibs-4.14.10/kcalcore/icalformat_p.cpp: In static member function
'static icaltimetype KCalCore::ICalFormatImpl::writeICalDateTime(const
KDateTime&)':
/home/kdepimlibs-4.14.10/kcalcore/icalformat_p.cpp:2326:7: error:
'icaltimetype' {aka 'struct icaltimetype'} has no member named 'is_utc'; did
you mean 'is_date'?
t.is_utc = datetime.isUtc() ? 1 : 0;
^~
is_date
/home/kdepimlibs-4.14.10/kcalcore/icalformat_p.cpp: In static member function
'static icalproperty*
KCalCore::ICalFormatImpl::writeICalDateTimeProperty(icalproperty_kind, const
KDateTime&, KCalCore::ICalTimeZones*, KCalCore::ICalTimeZones*)':
/home/kdepimlibs-4.14.10/kcalcore/icalformat_p.cpp:2401:12: error:
'icaltimetype' {aka 'struct icaltimetype'} has no member named 'is_utc'; did
you mean 'is_date'?
if (!t.is_utc) {
^~
is_date
/home/kdepimlibs-4.14.10/kcalcore/icalformat_p.cpp: In static member function
'static KDateTime KCalCore::ICalFormatImpl::readICalDateTime(icalproperty*,
const icaltimetype&, KCalCore::ICalTimeZones*, bool)':
/home/kdepimlibs-4.14.10/kcalcore/icalformat_p.cpp:2434:11: error: 'const
icaltimetype' {aka 'const struct icaltimetype'} has no member named 'is_utc';
did you mean 'is_date'?
if (t.is_utc || t.zone == icaltimezone_get_utc_timezone()) {
^~
is_date
Bug#921808: grub-efi-amd64 / grub-pc-bin version 2.02+dfsg1-10 fail to boot from mdraid
Package: grub-efi-amd64
Version: 2.02+dfsg1-10
Severity: important
Dear Maintainer,
* What led up to the situation?
Installed Debian Buster on mdraid 1 (2 disks) system using debootstrap. Disks
are partitioned to allow both UEFI and legacy boot. Configured things in
chroot. Installed grub-efi-amd64 and grub-pc-bin package.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Ran "grub-install --target=i386-pc /dev/sda", "grub-install --target=i386-pc
/dev/sdb" to install grub in bios-grub partition, "grub-install
--target=x86_64-efi --no-nvram --removable" to install grub into efi partition,
done in chroot on laptop with disks attached via usb and mdraid started. Moved
disks to target system. Tried to boot up.
* What was the outcome of this action?
System does not boot, neither UEFI nor legacy mode. GRUB drops to shell.
* What outcome did you expect instead?
Expected to get to GRUB menu.
* Workaround
Downgraded all GRUB packages to current Debian Stretch versions. No other
changes. Ran "grub-install ..." in chroot as above. Moved disks to target
system. Result: System boots fine in both UEFI and legacy mode.
Upgraded GRUB to Buster versions on running target system, reinstalled GRUB
(both legacy and efi). After that, system does not boot any more, as above.
* Note
System information is not from affected server system, it's from the laptop
that's running reportbug.
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/mapper/aljanah_root / btrfs
rw,relatime,ssd,space_cache,subvolid=257,subvol=/root 0 0
/dev/loop0 /var/cache/openafs ext4 rw,relatime 0 0
/dev/mapper/aljanah_boot /boot btrfs
ro,relatime,ssd,space_cache,subvolid=256,subvol=/boot 0 0
/dev/sda3 /boot/grub ext4 ro,relatime 0 0
/dev/sda2 /boot/efi vfat
ro,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro
0 0
/dev/mapper/_dev_sda7 /home/rsenger btrfs
rw,relatime,ssd,space_cache,subvolid=257,subvol=/rsenger 0 0
*** END /proc/mounts
*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_gpt
insmod ext2
set root='hd0,gpt3'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3
--hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3
d9b51fef-c34d-4e4e-847b-813786f7cfeb
else
search --no-floppy --fs-uuid --set=root d9b51fef-c34d-4e4e-847b-813786f7cfeb
fi
font="/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=1024x768x32
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=de_DE
insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
set timeout=30
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=-1
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=-1
fi
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_gpt
insmod ext2
set root='hd0,gpt3'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3
--hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3
d9b51fef-c34d-4e4e-847b-813786f7cfeb
else
search --no-floppy --fs-uuid --set=root d9b51fef-c34d-4e4e-847b-813786f7cfeb
fi
insmod png
if background_image /.background_cache.png; then
set color_normal=white/black
set color_highlight=black/white
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_uefi-firmware ###
### END /etc/grub.d/30_uefi-firmware ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.
Bug#921793: mono-tools: FTBFS (error CS0618: Warning as Error)
Package: src:mono-tools
Version: 4.2-2.2
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --with autoreconf,xsp,cli
dh: Compatibility levels before 9 are deprecated (level 7 in use)
dh_update_autotools_config -i
dh_autoreconf -i
sh: 1: ACLOCAL_FLAGS: not found
aclocal: warning: autoconf input should be named 'configure.ac', not
'configure.in'
automake: warning: autoconf input should be named 'configure.ac', not
'configure.in'
automake: warning: autoconf input should be named 'configure.ac', not
'configure.in'
dh_auto_configure -i
dh_auto_configure: Compatibility levels before 9 are deprecated (level 7 in use)
./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-silent-rules --libexecdir=\${prefix}/lib/mono-tools
--disable-maintainer-mode --disable-dependency-tracking
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
[... snipped ...]
Member Added: public readonly Gendarme.Framework.Helpers.MethodSignature
Subscript;
Member Added: public readonly Gendarme.Framework.Helpers.MethodSignature Sort;
Member Added: public override void Initialize (Gendarme.Framework.IRunner
runner);
Member Added: public Gendarme.Framework.RuleResult CheckMethod
(Mono.Cecil.MethodDefinition method);
New Type: Gendarme.Rules.Performance.UseIsOperatorRule
Member Added: public UseIsOperatorRule ();
Member Added: public Gendarme.Framework.RuleResult CheckMethod
(Mono.Cecil.MethodDefinition method);
New Type: Gendarme.Rules.Performance.UseStringEmptyRule
Member Added: public UseStringEmptyRule ();
Member Added: public Gendarme.Framework.RuleResult CheckMethod
(Mono.Cecil.MethodDefinition method);
New Type: Gendarme.Rules.Performance.UseTypeEmptyTypesRule
Member Added: public UseTypeEmptyTypesRule ();
Member Added: public Gendarme.Framework.RuleResult CheckMethod
(Mono.Cecil.MethodDefinition method);
Members Added: 86, Members Deleted: 0
touch doc/generated/index.xml
mdoc assemble -f ecma -o doc/Gendarme.Rules.Performance doc/generated
echo -e "\n\n\t\n\t\n" >
doc/Gendarme.Rules.Performance.source
make[5]: Leaving directory
'/<>/gendarme/rules/Gendarme.Rules.Performance'
make[4]: Leaving directory
'/<>/gendarme/rules/Gendarme.Rules.Performance'
Making all in Gendarme.Rules.Portability
make[4]: Entering directory
'/<>/gendarme/rules/Gendarme.Rules.Portability'
Making all in Test
make[5]: Entering directory
'/<>/gendarme/rules/Gendarme.Rules.Portability/Test'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory
'/<>/gendarme/rules/Gendarme.Rules.Portability/Test'
make[5]: Entering directory
'/<>/gendarme/rules/Gendarme.Rules.Portability'
/usr/bin/mono-csc -target:library -debug+ -d:TRACE -optimize+ -nowarn:1591
-warn:4 -warnaserror+ -r:ICSharpCode.SharpZipLib.dll -r:System.Web.Services.dll
-nowarn:1591 -doc:../../bin/Gendarme.Rules.Portability.dll.doc \
-r:/usr/lib/mono-cecil/Mono.Cecil.dll
-r:/usr/lib/mono-cecil/Mono.Cecil.Mdb.dll
-r:/usr/lib/mono-cecil/Mono.Cecil.Pdb.dll
-r:/usr/lib/mono-cecil/Mono.Cecil.Rocks.dll -r:../../bin/Gendarme.Framework.dll
-out:../../bin/Gendarme.Rules.Portability.dll ./DoNotHardcodePathsRule.cs
./ExitCodeIsLimitedOnUnixRule.cs ./FeatureRequiresRootPrivilegeOnUnixRule.cs
./MoMAWebService.cs ./MonoCompatibilityReviewRule.cs ./NewLineLiteralRule.cs
../../AssemblyInfo.cs ./../../AssemblyStaticInfo.cs
./MonoCompatibilityReviewRule.cs(179,11): error CS0618: Warning as Error:
`ICSharpCode.SharpZipLib.Zip.ZipInputStream' is obsolete: `This assembly has
been deprecated. Please use https://www.nuget.org/packages/SharpZipLib/
instead.'
./MonoCompatibilityReviewRule.cs(179,35): error CS0618: Warning as Error:
`ICSharpCode.SharpZipLib.Zip.ZipInputStream' is obsolete: `This assembly has
been deprecated. Please use https://www.nuget.org/packages/SharpZipLib/
instead.'
./MonoCompatibilityReviewRule.cs(181,5): error CS0618: Warning as Error:
`ICSharpCode.SharpZipLib.Zip.ZipEntry' is obsolete: `This assembly has been
deprecated. Please use https://www.nuget.org/packages/SharpZipLib/ instead.'
Compilation failed: 3 error(s), 0 warnings
make[5]: *** [Makefile:795: ../../bin/Gendarme.Rules.Portability.dll] Error 1
make[5]: Leaving directory
'/<>/gendarme/rules/Gendarme.Rules.Portability'
make[4]: *** [Makefile:516: all-recursive] Error 1
make[4]: Leaving directory
'/<>/gendarme/rules/Gendarme.Rules.Portability'
make[3]: *** [Makefile:400: all-recursive] Error 1
make[3]: Leaving directory '/<>/gendarme/rules'
make[2]: *** [Makefile:487: all-recursive] Error 1
make[2]: Leaving directory '/<>/gendarme'
make[1]: *** [Makefile:408: all-recursive] Error 1
make[1]: Leaving directory '/<>'
Bug#921794: node-cross-spawn-async: FTBFS (failing tests)
Package: src:node-cross-spawn-async Version: 2.2.5-2 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep dh_update_autotools_config -i debian/rules override_dh_auto_test make[1]: Entering directory '/<>' nodejs test/prepare && mocha -C -R spec test/test Copied "prepare_()%!^&;, .sh" to "()%!^&;, " cross-spawn-async 1) should support shebang in executables with /usr/bin/env 2) should support shebang in executables without /usr/bin/env 3) should support shebang in executables with relative path â should support shebang in executables with relative path that starts with `..` (1538ms) 4) should support shebang in executables with extensions â should expand using PATHEXT properly â should handle commands with spaces â should handle commands with special shell chars â should handle arguments with quotes (1744ms) â should handle empty arguments (1244ms) â should handle non-string arguments (1236ms) â should handle arguments with spaces (1196ms) â should handle arguments with \" (1237ms) â should handle arguments that end with \ (1213ms) â should handle arguments that contain shell special chars (1202ms) â should handle special arguments when using echo â should handle optional args correctly (63ms) â should not mutate args nor options â should give correct exit code (1216ms) â should work with a relative command â should emit "error" and "close" if command does not exist (1024ms) â should NOT emit "error" if shebang command does not exist (1013ms) â should NOT emit "error" if the command actual exists but exited with 1 (1012ms) 19 passing (23s) 4 failing 1) cross-spawn-async should support shebang in executables with /usr/bin/env: Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19) 2) cross-spawn-async should support shebang in executables without /usr/bin/env: Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19) 3) cross-spawn-async should support shebang in executables with relative path: Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19) 4) cross-spawn-async should support shebang in executables with extensions: Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19) make[1]: *** [debian/rules:11: override_dh_auto_test] Error 4 make[1]: Leaving directory '/<>' make: *** [debian/rules:8: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant part) The build was made in my autobuilder with "dpkg-buildpackage -A" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-cross-spawn-async.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
Bug#921806: ruby-api-pagination: FTBFS (failing tests)
Package: src:ruby-api-pagination Version: 4.2.0-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --buildsystem=ruby --with ruby dh_update_autotools_config -i -O--buildsystem=ruby dh_auto_configure -i -O--buildsystem=ruby dh_ruby --configure dh_auto_build -i -O--buildsystem=ruby dh_ruby --build dh_ruby --build dh_auto_test -i -O--buildsystem=ruby dh_ruby --test fakeroot debian/rules binary-indep dh binary-indep --buildsystem=ruby --with ruby dh_testroot -i -O--buildsystem=ruby dh_prep -i -O--buildsystem=ruby [... snipped ...] ArgumentError: unknown keywords: count, page Shared Example Group: "an endpoint with a middle page" called from ./spec/rails_spec.rb:58 # ./spec/rails_spec.rb:56:in `block (5 levels) in ' Finished in 0.20069 seconds (files took 1.92 seconds to load) 56 examples, 27 failures Failed examples: rspec ./spec/rails_spec.rb:30 # NumbersController GET #index without enough items to give more than one page should list all numbers in the response body rspec ./spec/rails_spec.rb:26 # NumbersController GET #index without enough items to give more than one page should give a Per-Page header rspec ./spec/rails_spec.rb:22 # NumbersController GET #index without enough items to give more than one page should give a Total header rspec ./spec/rails_spec.rb:18 # NumbersController GET #index without enough items to give more than one page should not paginate rspec ./spec/rails_spec.rb:91 # NumbersController GET #index with custom response headers should give a X-Total-Count header rspec ./spec/rails_spec.rb:99 # NumbersController GET #index with custom response headers should give a X-Per-Page header rspec ./spec/rails_spec.rb:107 # NumbersController GET #index with custom response headers should give a X-Page header rspec ./spec/rails_spec.rb:118 # NumbersController GET #index configured not to include the total should not include a Total header rspec ./spec/rails_spec.rb:63 # NumbersController GET #index providing a block yields to the block instead of implicitly rendering rspec './spec/rails_spec.rb[1:1:2:1:3]' # NumbersController GET #index with existing Link headers behaves like an endpoint with existing Link headers should give a Total header rspec './spec/rails_spec.rb[1:1:2:1:1]' # NumbersController GET #index with existing Link headers behaves like an endpoint with existing Link headers should keep existing Links rspec './spec/rails_spec.rb[1:1:2:1:2]' # NumbersController GET #index with existing Link headers behaves like an endpoint with existing Link headers should contain pagination Links rspec './spec/rails_spec.rb[1:1:3:1:1:3]' # NumbersController GET #index with enough items to paginate when on the first page behaves like an endpoint with a first page should give a link with rel "last" rspec './spec/rails_spec.rb[1:1:3:1:1:6]' # NumbersController GET #index with enough items to paginate when on the first page behaves like an endpoint with a first page should list the first page of numbers in the response body rspec './spec/rails_spec.rb[1:1:3:1:1:4]' # NumbersController GET #index with enough items to paginate when on the first page behaves like an endpoint with a first page should give a link with rel "next" rspec './spec/rails_spec.rb[1:1:3:1:1:5]' # NumbersController GET #index with enough items to paginate when on the first page behaves like an endpoint with a first page should give a Total header rspec './spec/rails_spec.rb[1:1:3:1:1:1]' # NumbersController GET #index with enough items to paginate when on the first page behaves like an endpoint with a first page should not give a link with rel "first" rspec './spec/rails_spec.rb[1:1:3:1:1:2]' # NumbersController GET #index with enough items to paginate when on the first page behaves like an endpoint with a first page should not give a link with rel "prev" rspec './spec/rails_spec.rb[1:1:3:2:1:2]' # NumbersController GET #index with enough items to paginate when on the last page behaves like an endpoint with a last page should not give a link with rel "next" rspec './spec/rails_spec.rb[1:1:3:2:1:3]' # NumbersController GET #index with enough items to paginate when on the last page behaves like an endpoint with a last page should give a link with rel "first" rspec './spec/rails_spec.rb[1:1:3:2:1:6]' # NumbersController GET #index with enough items to paginate when on the last page behaves like an endpoint with a last page should list the last page of numbers in the response body rspec './spec/rails_spec.rb[1:1:3:2:1:5]' # NumbersController GET #index with enough items to paginate when on the last page behaves like an endpoint with a last page should give a Total header rspec './spec/rails_spec.rb[1:1:3:2:1:4]' # NumbersController GET #index
Bug#921795: node-flagged-respawn: FTBFS (failing tests)
Package: src:node-flagged-respawn Version: 1.0.0-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep dh_update_autotools_config -i dh_autoreconf -i debian/rules override_dh_auto_test make[1]: Entering directory '/<>' mocha -R spec flaggedRespawn isV8flags â should return true when flag is in v8flags â should ignore separator differences of "-" and "_" â should return false when flag is not in v8flags [... snipped ...] Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19) 7) flaggedRespawn force and forbid respawning always forbid respawning with inner --no-respawning: Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19) 8) flaggedRespawn force and forbid respawning should force respawning with node flags (array): Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19) 9) flaggedRespawn force and forbid respawning should force respawning with node flags (string): Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19) 10) flaggedRespawn force and forbid respawning should take priority to forbidding than forcing: Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19) 11) flaggedRespawn cli args which are passed to app should pass args except v8flags, forced node flags, --no-respawning when respawned: Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19) 12) flaggedRespawn cli args which are passed to app should pass args except v8flags, forced node flags, --no-respawning when not respawned: Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19) make[1]: *** [debian/rules:13: override_dh_auto_test] Error 12 make[1]: Leaving directory '/<>' make: *** [debian/rules:8: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant part) The build was made in my autobuilder with "dpkg-buildpackage -A" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-flagged-respawn.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
Bug#921803: python-scrapy: FTBFS (failing tests)
Package: src:python-scrapy
Version: 1.5.1-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --with python2,python3,bash_completion,sphinxdoc
--buildsystem=pybuild
dh_update_autotools_config -i -O--buildsystem=pybuild
dh_autoreconf -i -O--buildsystem=pybuild
dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config
running config
I: pybuild base:217: python3.7 setup.py config
running config
dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python setup.py build
running build
running build_py
creating /<>/.pybuild/cpython2_2.7_scrapy/build/scrapy
[... snipped ...]
/<>/.pybuild/cpython2_2.7_scrapy/build/tests/test_linkextractors.py:24:
ScrapyDeprecationWarning: SgmlLinkExtractor is deprecated and will be removed
in future releases. Please use scrapy.linkextractors.LinkExtractor
lx = self.extractor_cls()
.pybuild/cpython2_2.7_scrapy/build/tests/test_linkextractors_deprecated.py::SgmlLinkExtractorTestCase::test_xhtml
/<>/.pybuild/cpython2_2.7_scrapy/build/tests/test_linkextractors.py:421:
ScrapyDeprecationWarning: SgmlLinkExtractor is deprecated and will be removed
in future releases. Please use scrapy.linkextractors.LinkExtractor
lx = self.extractor_cls()
/<>/.pybuild/cpython2_2.7_scrapy/build/tests/test_linkextractors.py:432:
ScrapyDeprecationWarning: SgmlLinkExtractor is deprecated and will be removed
in future releases. Please use scrapy.linkextractors.LinkExtractor
lx = self.extractor_cls()
.pybuild/cpython2_2.7_scrapy/build/tests/test_linkextractors_deprecated.py::RegexLinkExtractorTestCase::test_html_base_href
/<>/.pybuild/cpython2_2.7_scrapy/build/tests/test_linkextractors_deprecated.py:228:
ScrapyDeprecationWarning: SgmlLinkExtractor is deprecated and will be removed
in future releases. Please use scrapy.linkextractors.LinkExtractor
lx = RegexLinkExtractor()
.pybuild/cpython2_2.7_scrapy/build/tests/test_linkextractors_deprecated.py::RegexLinkExtractorTestCase::test_link_wrong_href
/<>/.pybuild/cpython2_2.7_scrapy/build/tests/test_linkextractors_deprecated.py:210:
ScrapyDeprecationWarning: SgmlLinkExtractor is deprecated and will be removed
in future releases. Please use scrapy.linkextractors.LinkExtractor
lx = RegexLinkExtractor()
.pybuild/cpython2_2.7_scrapy/build/tests/test_spider.py::CrawlSpiderTest::test_follow_links_attribute_deprecated_population
/<>/.pybuild/cpython2_2.7_scrapy/build/scrapy/spiders/crawl.py:106:
ScrapyDeprecationWarning: set_crawler is deprecated, instantiate and bound the
spider to this crawler with from_crawler method instead.
super(CrawlSpider, self).set_crawler(crawler)
/<>/.pybuild/cpython2_2.7_scrapy/build/scrapy/spiders/crawl.py:106:
ScrapyDeprecationWarning: set_crawler is deprecated, instantiate and bound the
spider to this crawler with from_crawler method instead.
super(CrawlSpider, self).set_crawler(crawler)
.pybuild/cpython2_2.7_scrapy/build/tests/test_utils_deprecate.py::WarnWhenSubclassedTest::test_warning_on_instance
/<>/.pybuild/cpython2_2.7_scrapy/build/tests/test_utils_deprecate.py:115:
MyWarning: tests.test_utils_deprecate.UserClass inherits from deprecated class
tests.test_utils_deprecate.Deprecated, please inherit from
tests.test_utils_deprecate.NewName. (warning only on first subclass, there may
be others)
class UserClass(Deprecated):
.pybuild/cpython2_2.7_scrapy/build/tests/test_utils_python.py::UtilsPythonTestCase::test_stringify_dict
/<>/.pybuild/cpython2_2.7_scrapy/build/tests/test_utils_python.py:157:
ScrapyDeprecationWarning: Call to deprecated function stringify_dict.
d2 = stringify_dict(d, keys_only=False)
.pybuild/cpython2_2.7_scrapy/build/tests/test_utils_python.py::UtilsPythonTestCase::test_stringify_dict_keys_only
/<>/.pybuild/cpython2_2.7_scrapy/build/tests/test_utils_python.py:176:
ScrapyDeprecationWarning: Call to deprecated function stringify_dict.
d2 = stringify_dict(d)
.pybuild/cpython2_2.7_scrapy/build/tests/test_utils_python.py::UtilsPythonTestCase::test_stringify_dict_tuples
/<>/.pybuild/cpython2_2.7_scrapy/build/tests/test_utils_python.py:167:
ScrapyDeprecationWarning: Call to deprecated function stringify_dict.
d2 = stringify_dict(tuples, keys_only=False)
-- Docs: https://docs.pytest.org/en/latest/warnings.html
1 failed, 1648 passed, 13 skipped, 14 xfailed, 427 warnings in 373.86 seconds =
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd
/<>/.pybuild/cpython2_2.7_scrapy/build; python2.7 -m pytest tests
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned
exit code 13
make: *** [debian/rules:9: build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
Bug#921797: node-lru-cache: FTBFS (failing tests)
Package: src:node-lru-cache Version: 5.1.1-3 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep dh_update_autotools_config -i dh_autoreconf -i debian/rules override_dh_auto_test make[1]: Entering directory '/<>' tap -R spec test/*.js test/basic.js basic â should be equal â should be equal [... snipped ...] â should be equal â should be equal â should be equal â should be equal â should be equal â should be equal â should be equal â should be equal â should be equal â should be equal â should be equal dumpLru â type is Yallist 650 passing (14s) 1 failing 1) test/foreach.js expires should be equal: Error: should be equal + expected - actual -3 +5 at Timeout._onTimeout (test/foreach.js:125:7) make[1]: *** [debian/rules:12: override_dh_auto_test] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:8: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant part) The build was made in my autobuilder with "dpkg-buildpackage -A" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-lru-cache.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
Bug#921789: librostlab-blast: FTBFS (LaTeX error)
Package: src:librostlab-blast
Version: 1.0.1-9
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep
dh_update_autotools_config -i
dh_autoreconf -i
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:7: installing './compile'
configure.ac:5: installing './missing'
[... snipped ...]
LaTeX Warning: Reference `blast-parser-parser_8h' on page 7 undefined on input
line 5.
LaTeX Warning: Reference `blast-parser-position_8h' on page 7 undefined on inpu
t line 6.
LaTeX Warning: Reference `blast-parser-stack_8h' on page 7 undefined on input l
ine 7.
LaTeX Warning: Reference `blast-result_8h' on page 7 undefined on input line 8.
) [7] [8]
Chapter 5.
(./namespacerostlab.tex
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/ts1phv.fd)
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1pcr.fd)
LaTeX Font Warning: Font shape `T1/pcr/bc/n' undefined
(Font) using `T1/pcr/m/n' instead on input line 27.
[9]) (./namespacerostlab_1_1blast.tex [10] [11] [12] [13] [14]
! Missing } inserted.
}
l.253 \end{DoxyParams}
?
! Emergency stop.
}
l.253 \end{DoxyParams}
! ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
mv: cannot stat 'refman.pdf': No such file or directory
make[2]: *** [Makefile:902: ../doxygen-doc/librostlab-blast.pdf] Error 1
make[2]: Leaving directory '/<>/lib'
make[1]: *** [debian/rules:26: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:11: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/librostlab-blast.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
Bug#921798: node-mocha: FTBFS (Module not found: Error: Recursion in resolving)
Package: src:node-mocha Version: 4.1.0+ds3-3 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep dh_update_autotools_config -i dh_autoreconf -i dh_auto_configure -i debian/rules override_dh_auto_build make[1]: Entering directory '/<>/node-mocha-4.1.0+ds3' NODE_PATH='/usr/share/nodejs:/usr/lib/nodejs' webpack --verbose --config debian/webpack.config.js Hash: 87cc69c5bf02c862585f Version: webpack 3.5.6 Time: 2463ms AssetSize ChunksChunk Names mocha.js 458 kB 0 [emitted] [big] main Entrypoint main [big] = mocha.js [... snipped ...] raw-module: (/<>/node-mocha-4.1.0+ds3) buffer module: (/<>/node-mocha-4.1.0+ds3) buffer resolve: (/usr/share/nodejs) ./buffer new-resolve: (/usr/share/nodejs) ./buffer parsed-resolve: (/usr/share/nodejs) ./buffer described-resolve: (/usr/share/nodejs) ./buffer resolve: (/<>/node-mocha-4.1.0+ds3) buffer @ /usr/lib/nodejs/core-util-is/lib/util.js 1:0-79 @ /usr/lib/nodejs/readable-stream/lib/_stream_duplex.js @ /usr/lib/nodejs/readable-stream/readable-browser.js @ /usr/lib/nodejs/stream-browserify/index.js @ /usr/lib/nodejs/browser-stdout/index.js @ ./browser-entry.js ERROR in /usr/share/javascript/util/support/isBuffer.js Module not found: Error: Recursion in resolving Stack: resolve: (/usr/share/javascript/util/support) ./../../../../../<>/node-mocha-4.1.0+ds3/buffer new-resolve: (/usr/share/javascript/util/support) ./../../../../../<>/node-mocha-4.1.0+ds3/buffer parsed-resolve: (/usr/share/javascript/util/support) ./../../../../../<>/node-mocha-4.1.0+ds3/buffer described-resolve: (/usr/share/javascript/util/support) ./../../../../../<>/node-mocha-4.1.0+ds3/buffer relative: (/<>/node-mocha-4.1.0+ds3/buffer) described-relative: (/<>/node-mocha-4.1.0+ds3/buffer) raw-file: (/<>/node-mocha-4.1.0+ds3/buffer) file: (/<>/node-mocha-4.1.0+ds3/buffer) resolve: (/<>/node-mocha-4.1.0+ds3) buffer new-resolve: (/<>/node-mocha-4.1.0+ds3) buffer parsed-resolve: (/<>/node-mocha-4.1.0+ds3) buffer module described-resolve: (/<>/node-mocha-4.1.0+ds3) buffer module raw-module: (/<>/node-mocha-4.1.0+ds3) buffer module: (/<>/node-mocha-4.1.0+ds3) buffer resolve: (/usr/share/nodejs) ./buffer new-resolve: (/usr/share/nodejs) ./buffer parsed-resolve: (/usr/share/nodejs) ./buffer described-resolve: (/usr/share/nodejs) ./buffer resolve: (/<>/node-mocha-4.1.0+ds3) buffer @ /usr/share/javascript/util/support/isBuffer.js 1:0-79 @ /usr/share/javascript/util/util.js @ ./lib/utils.js @ ./lib/mocha.js @ ./browser-entry.js make[1]: *** [debian/rules:23: mocha.js] Error 2 make[1]: Leaving directory '/<>/node-mocha-4.1.0+ds3' make: *** [debian/rules:8: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant part) The build was made in my autobuilder with "dpkg-buildpackage -A" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-mocha.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
Bug#921799: node-serve-index: FTBFS (failing tests)
Package: src:node-serve-index Version: 1.4.0-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep dh: Compatibility levels before 9 are deprecated (level 8 in use) dh_update_autotools_config -i debian/rules override_dh_auto_test make[1]: Entering directory '/<>' mocha -C --reporter spec --bail --check-leaks test/ serveIndex(root) â should require root â should serve text/html without Accept header (139ms) â should serve a directory index â should work with HEAD requests â should work with OPTIONS requests â should deny POST requests â should deny path will NULL byte â should deny path outside root â should skip non-existent paths 1) should treat an ENAMETOOLONG as a 414 9 passing (329ms) 1 failing 1) serveIndex(root) should treat an ENAMETOOLONG as a 414: Error: expected 414 "URI Too Long", got 400 "Bad Request" at Test.assert (/usr/lib/nodejs/supertest/lib/test.js:205:15) at Server.assert (/usr/lib/nodejs/supertest/lib/test.js:132:12) at emitCloseNT (net.js:1616:8) at process._tickCallback (internal/process/next_tick.js:63:19) make[1]: *** [debian/rules:11: override_dh_auto_test] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:8: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant part) The build was made in my autobuilder with "dpkg-buildpackage -A" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-serve-index.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
Bug#921790: liquidsoap: FTBFS (ld: cannot find -lexif)
Package: src:liquidsoap
Version: 1.3.3-2
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --with elpa,ocaml
dh_update_autotools_config -i
debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
./bootstrap
make[1]: Leaving directory '/<>'
dh_ocamlinit -i
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure --
--with-default-font=/usr/share/fonts/truetype/liberation/LiberationMono-Regular.ttf
./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode
--disable-dependency-tracking
--with-default-font=/usr/share/fonts/truetype/liberation/LiberationMono-Regular.ttf
configure: WARNING: unrecognized options: --disable-silent-rules,
--disable-maintainer-mode, --disable-dependency-tracking
checking for a BSD-compatible install... /usr/bin/install -c
[... snipped ...]
OCAMLOPT -c decoder/image/ppm_decoder.ml
OCAMLOPT -c decoder/external_decoder.ml
OCAMLOPT -c decoder/raw_audio_decoder.ml
OCAMLOPT -c decoder/flac_decoder.ml
OCAMLOPT -c decoder/aac_decoder.ml
OCAMLOPT -c decoder/ogg_decoder.ml
OCAMLOPT -c decoder/mad_decoder.ml
OCAMLOPT -c decoder/vorbisduration.ml
OCAMLOPT -c decoder/flacduration.ml
OCAMLOPT -c decoder/ogg_flac_duration.ml
OCAMLOPT -c decoder/taglib_plug.ml
OCAMLOPT -c decoder/image/camlimages_decoder.ml
OCAMLOPT -c decoder/image/sdlimage_decoder.ml
OCAMLOPT -c decoder/gstreamer_decoder.ml
OCAMLOPT -c shebang.ml
OCAMLOPT -c lang/lang_builtins.ml
OCAMLOPT -c lang/builtins_json.ml
OCAMLOPT -c lang/builtins_harbor.ml
OCAMLOPT -c lang/builtins_dtools.ml
OCAMLOPT -c lang/builtins_time.ml
OCAMLOPT -c lang/builtins_callbacks.ml
OCAMLOPT -c lang/builtins_lo.mli
OCAMLOPT -c lang/builtins_lo.ml
OCAMLOPT -c lang/builtins_magic.ml
OCAMLOPT -c lang/builtins_cry.ml
OCAMLOPT -c lang/builtins_lastfm.ml
OCAMLOPT -c main.ml
OCAMLOPT -c runner.ml
CC -c tools/unix_c.c
CC -c io/oss_io_c.c
OCAMLOPT -o liquidsoap
/usr/bin/ld: cannot find -lexif
collect2: error: ld returned 1 exit status
File "caml_startup", line 1:
Error: Error during linking
make[4]: *** [../Makefile.rules:110: liquidsoap] Error 2
make[4]: Leaving directory '/<>/src'
make[3]: *** [../Makefile.rules:67: all-auto-ocaml-prog] Error 2
make[3]: Leaving directory '/<>/src'
make[2]: *** [Makefile.rules:27: all-subdirs] Error 2
make[2]: Leaving directory '/<>'
make[1]: *** [debian/rules:21: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:11: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/liquidsoap.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
Bug#921784: gromacs: FTBFS (ld returned 1 exit status)
Package: src:gromacs Version: 2019-2 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules binary-indep dh_testdir (mkdir -p build/basic; cd build/basic; cmake /<> -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_RULE_MESSAGES=OFF -DCMAKE_INSTALL_PREFIX="/usr" -DCMAKE_EXE_LINKER_FLAGS="-Wl,-z,relro -Wl,-z,now -Wl,--as-needed" -DGMX_EXTERNAL_ZLIB=ON -DGMX_SIMD=SSE2 -DGMX_MPI=OFF -DGMX_X11=ON -DBUILD_SHARED_LIBS=ON) -- The C compiler identification is GNU 8.2.0 -- The CXX compiler identification is GNU 8.2.0 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Detecting C compile features -- Detecting C compile features - done -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Detecting CXX compiler ABI info [... snipped ...] [ 84%] Built target testutils-mpi-test /usr/bin/make -f src/testutils/tests/CMakeFiles/testutils-test.dir/build.make src/testutils/tests/CMakeFiles/testutils-test.dir/depend make[4]: Entering directory '/<>/build/openmpi-dp' cd /<>/build/openmpi-dp && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> /<>/src/testutils/tests /<>/build/openmpi-dp /<>/build/openmpi-dp/src/testutils/tests /<>/build/openmpi-dp/src/testutils/tests/CMakeFiles/testutils-test.dir/DependInfo.cmake --color= Scanning dependencies of target testutils-test make[4]: Leaving directory '/<>/build/openmpi-dp' /usr/bin/make -f src/testutils/tests/CMakeFiles/testutils-test.dir/build.make src/testutils/tests/CMakeFiles/testutils-test.dir/build make[4]: Entering directory '/<>/build/openmpi-dp' cd /<>/build/openmpi-dp/src/testutils/tests && /usr/bin/mpicxx.openmpi -DGMX_DOUBLE=1 -DGTEST_HAS_PTHREAD=1 -DHAVE_CONFIG_H -DTEST_DATA_PATH=\"src/testutils/tests\" -DTEST_TEMP_PATH=\"/<>/build/openmpi-dp/src/testutils/tests/Testing/Temporary\" -I/<>/build/openmpi-dp/src -I/<>/src -isystem /<>/src/external/googletest/googletest/include -isystem /<>/src/external/googletest/googlemock/include -isystem /<>/src/testutils/../external/tinyxml2 -isystem /<>/src/external/thread_mpi/include -msse2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 -O3 -DNDEBUG -funroll-all-loops -fexcess-precision=fast -o CMakeFiles/testutils-test.dir/interactivetest.cpp.o -c /<>/src/testutils/tests/interactivetest.cpp cd /<>/build/openmpi-dp/src/testutils/tests && /usr/bin/mpicxx.openmpi -DGMX_DOUBLE=1 -DGTEST_HAS_PTHREAD=1 -DHAVE_CONFIG_H -DTEST_DATA_PATH=\"src/testutils/tests\" -DTEST_TEMP_PATH=\"/<>/build/openmpi-dp/src/testutils/tests/Testing/Temporary\" -I/<>/build/openmpi-dp/src -I/<>/src -isystem /<>/src/external/googletest/googletest/include -isystem /<>/src/external/googletest/googlemock/include -isystem /<>/src/testutils/../external/tinyxml2 -isystem /<>/src/external/thread_mpi/include -msse2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 -O3 -DNDEBUG -funroll-all-loops -fexcess-precision=fast -o CMakeFiles/testutils-test.dir/refdata_tests.cpp.o -c /<>/src/testutils/tests/refdata_tests.cpp cd /<>/build/openmpi-dp/src/testutils/tests && /usr/bin/mpicxx.openmpi -DGMX_DOUBLE=1 -DGTEST_HAS_PTHREAD=1 -DHAVE_CONFIG_H -DTEST_DATA_PATH=\"src/testutils/tests\" -DTEST_TEMP_PATH=\"/<>/build/openmpi-dp/src/testutils/tests/Testing/Temporary\" -I/<>/build/openmpi-dp/src -I/<>/src -isystem /<>/src/external/googletest/googletest/include -isystem /<>/src/external/googletest/googlemock/include -isystem /<>/src/testutils/../external/tinyxml2 -isystem /<>/src/external/thread_mpi/include -msse2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 -O3 -DNDEBUG -funroll-all-loops -fexcess-precision=fast -o CMakeFiles/testutils-test.dir/testasserts_tests.cpp.o -c /<>/src/testutils/tests/testasserts_tests.cpp cd /<>/build/openmpi-dp/src/testutils/tests && /usr/bin/mpicxx.openmpi -DGMX_DOUBLE=1 -DGTEST_HAS_PTHREAD=1 -DHAVE_CONFIG_H -DTEST_DATA_PATH=\"src/testutils/tests\" -DTEST_TEMP_PATH=\"/<>/build/openmpi-dp/src/testutils/tests/Testing/Temporary\" -I/<>/build/openmpi-dp/src -I/<>/src -isystem /<>/src/external/googletest/googletest/include -isystem /<>/src/external/googletest/googlemock/include -isystem /<>/src/testutils/../external/tinyxml2 -isystem /<>/src/external/thread_mpi/include -msse2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 -O3 -DNDEBUG -funroll-all-loops -fexcess-precision=fast -o
Bug#921778: deap: FTBFS (Could not import extension sphinx.ext.pngmath)
Package: src:deap Version: 1.0.2.post2-5 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --with python2,python3,sphinxdoc --buildsystem=pybuild dh_update_autotools_config -i -O--buildsystem=pybuild dh_autoreconf -i -O--buildsystem=pybuild dh_auto_configure -i -O--buildsystem=pybuild I: pybuild base:217: python2.7 setup.py config warning: pypandoc module not found, could not convert Markdown to RST running config I: pybuild base:217: python3.7 setup.py config warning: pypandoc module not found, could not convert Markdown to RST running config dh_auto_build -i -O--buildsystem=pybuild I: pybuild base:217: /usr/bin/python setup.py build warning: pypandoc module not found, could not convert Markdown to RST [... snipped ...] copying /<>/.pybuild/cpython3_3.7_deap/build/deap/__pycache__/gp.cpython-37.pyc -> /<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/__pycache__ copying /<>/.pybuild/cpython3_3.7_deap/build/deap/__pycache__/__init__.cpython-37.pyc -> /<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/__pycache__ copying /<>/.pybuild/cpython3_3.7_deap/build/deap/__pycache__/base.cpython-37.pyc -> /<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/__pycache__ copying /<>/.pybuild/cpython3_3.7_deap/build/deap/__pycache__/creator.cpython-37.pyc -> /<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/__pycache__ creating /<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/benchmarks copying /<>/.pybuild/cpython3_3.7_deap/build/deap/benchmarks/__init__.py -> /<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/benchmarks copying /<>/.pybuild/cpython3_3.7_deap/build/deap/benchmarks/movingpeaks.py -> /<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/benchmarks copying /<>/.pybuild/cpython3_3.7_deap/build/deap/benchmarks/binary.py -> /<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/benchmarks copying /<>/.pybuild/cpython3_3.7_deap/build/deap/benchmarks/tools.py -> /<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/benchmarks copying /<>/.pybuild/cpython3_3.7_deap/build/deap/benchmarks/gp.py -> /<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/benchmarks creating /<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/benchmarks/__pycache__ copying /<>/.pybuild/cpython3_3.7_deap/build/deap/benchmarks/__pycache__/__init__.cpython-37.pyc -> /<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/benchmarks/__pycache__ byte-compiling /<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/__init__.py to __init__.cpython-37.pyc byte-compiling /<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/tools/emo.py to emo.cpython-37.pyc byte-compiling /<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/tools/migration.py to migration.cpython-37.pyc byte-compiling /<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/tools/__init__.py to __init__.cpython-37.pyc byte-compiling /<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/tools/mutation.py to mutation.cpython-37.pyc byte-compiling /<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/tools/selection.py to selection.cpython-37.pyc byte-compiling /<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/tools/crossover.py to crossover.cpython-37.pyc byte-compiling /<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/tools/init.py to init.cpython-37.pyc byte-compiling /<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/tools/support.py to support.cpython-37.pyc byte-compiling /<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/base.py to base.cpython-37.pyc byte-compiling /<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/tests/__init__.py to __init__.cpython-37.pyc byte-compiling /<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/tests/test_logbook.py to test_logbook.cpython-37.pyc byte-compiling /<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/tests/test_pickle.py to test_pickle.cpython-37.pyc byte-compiling /<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/algorithms.py to algorithms.cpython-37.pyc byte-compiling /<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/cma.py to cma.cpython-37.pyc byte-compiling /<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/creator.py to creator.cpython-37.pyc byte-compiling /<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/gp.py to gp.cpython-37.pyc byte-compiling /<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/benchmarks/__init__.py to __init__.cpython-37.pyc byte-compiling /<>/debian/python3-deap/usr/lib/python3.7/dist-packages/deap/benchmarks/movingpeaks.py to movingpeaks.cpython-37.pyc byte-compiling
Bug#921788: libdc1394-22: FTBFS (LaTeX error)
Package: src:libdc1394-22
Version: 2.2.5-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --with autoreconf
dh_update_autotools_config -i
dh_autoreconf -i
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
configure.ac:29: installing './compile'
[... snipped ...]
[][][]
[30] [31]) (./control_8h.tex
Underfull \hbox (badness 1) in paragraph at lines 8--9
[32]
Underfull \hbox (badness 776) in paragraph at lines 67--69
[] \T1/phv/b/n/10 dc1394error[]_[]t dc1394[]_[]feature[]_[]set[]_[]value \T1/p
hv/m/n/10 ( \T1/phv/b/n/10 dc1394camera[]_[]t $\OMS/cmsy/m/n/10 ^^C$\T1/phv/m/n
/10 camera, \T1/phv/b/n/10 dc1394feature[]_[]t \T1/phv/m/n/10 fea-ture,
[33]
Underfull \hbox (badness 5893) in paragraph at lines 117--119
[] \T1/phv/b/n/10 dc1394error[]_[]t dc1394[]_[]external[]_[]trigger[]_[]get[]_
[]supported[]_[]sources \T1/phv/m/n/10 ( \T1/phv/b/n/10 dc1394camera[]_[]t $\OM
S/cmsy/m/n/10 ^^C$\T1/phv/m/n/10 camera,
Underfull \hbox (badness 1) detected at line 142
[][][]
[34] [35] [36] [37] [38] [39] [40] [41] [42]) (./conversions_8h.tex
Underfull \hbox (badness 1) in paragraph at lines 8--9
[43]
Underfull \hbox (badness 1) detected at line 42
[][][]
[44] [45]
! Missing } inserted.
}
l.123 \end{DoxyParams}
?
! Emergency stop.
}
l.123 \end{DoxyParams}
! ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
mv: cannot stat 'refman.pdf': No such file or directory
make[2]: *** [Makefile:1048: doc/libdc1394.pdf] Error 1
make[2]: Leaving directory '/<>'
dh_auto_build: make -j1 all doxygen-pdf returned exit code 2
make[1]: *** [debian/rules:10: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:4: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libdc1394-22.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
Bug#921805: rt-extension-nagios: FTBFS (you may need to install the Capture::Tiny module)
Package: src:rt-extension-nagios Version: 1.01-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep dh_update_autotools_config -i dh_auto_configure -i perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" "LD=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro" Cannot determine perl version info from lib/RT/Extension/Nagios.pm Can't locate Capture/Tiny.pm in @INC (you may need to install the Capture::Tiny module) (@INC contains: inc . /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 /usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at /usr/share/perl5/Module/Install/ReadmeFromPod.pm line 40. include /<>/inc/Module/Install.pm include inc/Module/Install/RTx.pm include inc/Module/Install/Base.pm include inc/Module/Install/Metadata.pm include inc/Module/Install/Makefile.pm include inc/Module/Install/ReadmeFromPod.pm dh_auto_configure: perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" "LD=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro" returned exit code 2 make: *** [debian/rules:6: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant part) The build was made in my autobuilder with "dpkg-buildpackage -A" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rt-extension-nagios.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
Bug#921807: sketch: FTBFS (LaTeX error)
Package: src:sketch Version: 1:0.3.7-10 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep dh_update_autotools_config -i dh_autoreconf -i debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' perl makever.pl not generating web page make[1]: Leaving directory '/<>' debian/rules override_dh_auto_build make[1]: Entering directory '/<>' dh_auto_build make -j1 make[2]: Entering directory '/<>' [... snipped ...] (/usr/share/texlive/texmf-dist/tex/generic/pst-node/pst-node.tex))) (/usr/share/texlive/texmf-dist/tex/latex/pst-text/pst-text.sty (/usr/share/texlive/texmf-dist/tex/generic/pst-text/pst-text.tex v1.01, 2018/12/22(tvz,hv))) (/usr/share/texlive/texmf-dist/tex/latex/pst-3d/pst-3d.sty (/usr/share/texlive/texmf-dist/tex/generic/pst-3d/pst-3d.tex)) (/usr/share/texlive/texmf-dist/tex/latex/pst-eps/pst-eps.sty (/usr/share/texlive/texmf-dist/tex/generic/pst-eps/pst-eps.tex v1.00, 2006/11/04)) (/usr/share/texlive/texmf-dist/tex/latex/pst-fill/pst-fill.sty (/usr/share/texlive/texmf-dist/tex/generic/pst-fill/pst-fill.tex `PST-Fill' v1.01, 2007/03/10 (tvz,dg,hv))) (/usr/share/texlive/texmf-dist/tex/latex/pstricks-add/pstricks-add.sty (/usr/share/texlive/texmf-dist/tex/latex/pst-math/pst-math.sty (/usr/share/texlive/texmf-dist/tex/latex/pst-calculate/pst-calculate.sty (/usr/share/texlive/texmf-dist/tex/latex/l3packages/xparse/xparse.sty (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3.sty (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3-code.tex) (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/l3dvips.def))) (/usr/share/texlive/texmf-dist/tex/latex/siunitx/siunitx.sty (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amstext.sty (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsgen.sty)) (/usr/share/texlive/texmf-dist/tex/latex/tools/array.sty) (/usr/share/texlive/texmf-dist/tex/latex/l3packages/l3keys2e/l3keys2e.sty) (/usr/share/texlive/texmf-dist/tex/latex/translator/translator.sty))) (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifluatex.sty) ! LaTeX Error: File `xstring.sty' not found. Type X to quit or to proceed, or enter new name. (Default extension: sty) Enter file name: ! Emergency stop. l.19 \input pst-math.tex^^M No pages of output. Transcript written on ex000-tmp.log. Inappropriate ioctl for device at make.pl line 34, line 1. make[1]: *** [debian/rules:28: override_dh_auto_build] Error 25 make[1]: Leaving directory '/<>' make: *** [debian/rules:21: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant part) The build was made in my autobuilder with "dpkg-buildpackage -A" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sketch.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
Bug#921800: nvchecker: FTBFS (failing tests)
Package: src:nvchecker
Version: 1.3-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --with python3 --buildsystem=pybuild
dh_update_autotools_config -i -O--buildsystem=pybuild
dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python3.7 setup.py config
running config
dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python3 setup.py build
running build
running build_py
creating /<>/.pybuild/cpython3_3.7/build/nvchecker
copying nvchecker/slogconf.py ->
/<>/.pybuild/cpython3_3.7/build/nvchecker
copying nvchecker/sortversion.py ->
/<>/.pybuild/cpython3_3.7/build/nvchecker
copying nvchecker/core.py ->
/<>/.pybuild/cpython3_3.7/build/nvchecker
[... snipped ...]
async with session.get(url) as res:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self =
async def __aenter__(self):
> return await to_asyncio_future(client.fetch(self.req))
E tornado.httpclient.HTTPClientError: HTTP 502: Proxy Error
nvchecker/source/tornado_httpclient.py:62: HTTPClientError
===Flaky Test Report===
test_archpkg passed 1 out of the required 1 times. Success!
test_archpkg_strip_release passed 1 out of the required 1 times. Success!
test_aur passed 1 out of the required 1 times. Success!
test_aur_strip_release passed 1 out of the required 1 times. Success!
test_aur_use_last_modified passed 1 out of the required 1 times. Success!
test_debianpkg passed 1 out of the required 1 times. Success!
test_debianpkg_strip_release passed 1 out of the required 1 times. Success!
test_debianpkg_suite passed 1 out of the required 1 times. Success!
test_ubuntupkg passed 1 out of the required 1 times. Success!
test_ubuntupkg_strip_release passed 1 out of the required 1 times. Success!
test_ubuntupkg_suite passed 1 out of the required 1 times. Success!
test_ubuntupkg_suite_with_paging passed 1 out of the required 1 times. Success!
===End Flaky Test Report===
=== warnings summary ===
tests/test_regex.py:12
/<>/.pybuild/cpython3_3.7/build/tests/test_regex.py:12:
DeprecationWarning: invalid escape sequence \w
"regex": '"User-Agent": "(\w+)"',
tests/test_regex.py:19
/<>/.pybuild/cpython3_3.7/build/tests/test_regex.py:19:
DeprecationWarning: invalid escape sequence \w
"regex": 'for (\w+) examples',
tests/test_substitute.py:20
/<>/.pybuild/cpython3_3.7/build/tests/test_substitute.py:20:
DeprecationWarning: invalid escape sequence \d
assert await get_version("example", {"manual": "r15", "prefix": "r",
"from_pattern": "r(\d+)", "to_pattern": "R\1"}) == "15"
-- Docs: https://docs.pytest.org/en/latest/warnings.html
= 1 failed, 40 passed, 18 skipped, 3 warnings in 13.15 seconds =
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd
/<>/.pybuild/cpython3_3.7/build; python3.7 -m pytest tests
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 returned
exit code 13
make: *** [debian/rules:6: build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/nvchecker.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
Bug#921804: rt-extension-jsgantt: FTBFS (mv: cannot stat 'Makefile': No such file or directory)
Package: src:rt-extension-jsgantt Version: 1.03-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep dh: Compatibility levels before 9 are deprecated (level 8 in use) dh_update_autotools_config -i debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' rm -rf inc/Module for ver in 4; do \ perl Makefile.PL INSTALLDIRS=vendor; \ mv Makefile Makefile$ver; \ done Cannot determine perl version info from lib/RT/Extension/JSGantt.pm Can't locate Capture/Tiny.pm in @INC (you may need to install the Capture::Tiny module) (@INC contains: inc /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 /usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/perl5/Module/Install/ReadmeFromPod.pm line 40. include /<>/inc/Module/Install.pm include inc/Module/Install/RTx.pm include inc/Module/Install/Base.pm include inc/Module/Install/Metadata.pm include inc/Module/Install/Makefile.pm include inc/Module/Install/ReadmeFromPod.pm mv: cannot stat 'Makefile': No such file or directory make[1]: *** [debian/rules:10: override_dh_auto_configure] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:6: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant part) The build was made in my autobuilder with "dpkg-buildpackage -A" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rt-extension-jsgantt.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
Bug#921796: node-libnpx: FTBFS (failing tests)
Package: src:node-libnpx Version: 10.2.0-2 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep dh_update_autotools_config -i dh_autoreconf -i dh_auto_configure -i debian/rules override_dh_auto_build make[1]: Entering directory '/<>' tail -n +2 README.md | marked-man --manual 'User Commands' --version libnpx@$(dpkg-parsechangelog -S version) > libnpx.1 make[1]: Leaving directory '/<>' debian/rules override_dh_auto_test make[1]: Entering directory '/<>' mkdir node_modules ln -s /usr/lib/nodejs/npm node_modules ln -s .. node_modules/libnpx [... snipped ...] 1..10 ok 15 - treats directory-type commands specially # time=39.876ms # Subtest: -n and --node-arg special parsing rules ok 1 - should match pattern provided ok 2 - should match pattern provided ok 3 - should match pattern provided ok 4 - should match pattern provided ok 5 - should match pattern provided ok 6 - should match pattern provided ok 7 - should match pattern provided ok 8 - should match pattern provided ok 9 - should match pattern provided ok 10 - should match pattern provided 1..10 ok 16 - -n and --node-arg special parsing rules # time=75.918ms 1..16 # time=708.137ms ok 5 - test/parse-args.js # time=2287.591ms # Subtest: test/util.js # Subtest: promisify with existing util.promisify ok 1 - used existing promisify fn 1..1 ok 1 - promisify with existing util.promisify # time=33.67ms # Subtest: promisify without existing util.promisify ok 1 - got a thenable ok 2 - value passed through successfully ok 3 - got the error! 1..3 ok 2 - promisify without existing util.promisify # time=22.968ms 1..2 # time=109.629ms ok 6 - test/util.js # time=1657.342ms 1..6 # failed 1 of 6 tests # time=49363.288ms make[1]: *** [debian/rules:27: override_dh_auto_test] Error 123 make[1]: Leaving directory '/<>' make: *** [debian/rules:9: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant part) The build was made in my autobuilder with "dpkg-buildpackage -A" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-libnpx.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
Bug#921802: primesieve: FTBFS (LaTeX error)
Package: src:primesieve
Version: 7.3+ds-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --builddirectory=_build
dh_update_autotools_config -i -O--builddirectory=_build
dh_autoreconf -i -O--builddirectory=_build
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/primesieve-7.3+ds'
dh_auto_configure -- \
-DBUILD_TESTS=ON \
-DBUILD_EXAMPLES=ON \
-DBUILD_DOC=ON
cd _build && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DBUILD_TESTS=ON
-DBUILD_EXAMPLES=ON -DBUILD_DOC=ON ..
-- The CXX compiler identification is GNU 8.2.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
[... snipped ...]
LaTeX Warning: Reference `iterator_8h' on page 9 undefined on input line 3.
LaTeX Warning: Reference `iterator_8hpp' on page 9 undefined on input line 4.
LaTeX Warning: Reference `primesieve_8h' on page 9 undefined on input line 5.
LaTeX Warning: Reference `primesieve_8hpp' on page 9 undefined on input line 6.
LaTeX Warning: Reference `primesieve__error_8hpp' on page 9 undefined on input
line 7.
) [9] [10]
Chapter 6.
(./namespaceprimesieve.tex [11]
Underfull \hbox (badness 1) detected at line 94
[][][]
[12] [13]
Underfull \hbox (badness 1) detected at line 156
[][][]
! Missing } inserted.
}
l.175 \end{DoxyParams}
?
! Emergency stop.
}
l.175 \end{DoxyParams}
! ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
make[3]: *** [Makefile:6: refman.pdf] Error 1
make[3]: Leaving directory
'/<>/primesieve-7.3+ds/_build/DEBIAN/doc/latex'
make[2]: *** [debian/adhoc/Makefile:15: doc] Error 2
make[2]: Leaving directory '/<>/primesieve-7.3+ds'
make[1]: *** [debian/rules:33: override_dh_auto_build-indep] Error 2
make[1]: Leaving directory '/<>/primesieve-7.3+ds'
make: *** [debian/rules:24: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/primesieve.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
Bug#921801: packaging-tutorial: FTBFS (LaTeX error)
Package: src:packaging-tutorial
Version: 0.21
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep
dh_update_autotools_config -i
dh_auto_configure -i
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
# version check
if [ 0.21 != 0.21 ]; then echo "Wrong version in .tex: 0.21 != 0.21"; exit 1; fi
#translate source files before building pdf
po4a po4a/po4a.cfg --verbose --keep 50
Updating po4a/po//packaging-tutorial.pot:
(628 entries)
Updating po4a/po//de.po:
... done.
[... snipped ...]
debiantutorial.zh_TW.sty is 100% translated (1 strings).
dh_auto_build
make -j1
make[2]: Entering directory '/<>'
make LU_REC_MASTER="packaging-tutorial.de" LU_REC_FLAVOR="PDF"
LU_REC_TARGET="packaging-tutorial.de.pdf" LU_WATCH_FILES_SAVE
make[3]: Entering directory '/<>'
make[3]: Nothing to be done for 'LU_WATCH_FILES_SAVE'.
make[3]: Leaving directory '/<>'
==> building packaging-tutorial.de.pdf <==
Running: 'pdflatex' '--interaction' 'errorstopmode' '--jobname'
'packaging-tutorial.de'
'\RequirePackage[extension=.pdf]{texdepends}\input{packaging-tutorial.de.tex}'
LaTeX Warning: You have requested package
`beamerthemedebian',*
Building packaging-tutorial.de.pdf fails
*
Here are the last lines of the log file
If this is not enought, try to
call 'make' with 'VERB=verbose' option
*
==> Last lines in packaging-tutorial.de.log <==
\beamer@dima=\dimen185
\beamer@dimb=\dimen186
)
(/usr/share/texlive/texmf-dist/tex/latex/beamer/beamerouterthemedefault.sty)))
(./beamerthemedebian.sty
LaTeX Warning: You have requested package `beamerthemedebian',
but the package provides `$'.
Package: $ 2019/01/05 v3.1 (3.1)
! LaTeX Error: Missing \begin{document}.
See the LaTeX manual or LaTeX Companion for explanation.
Type H for immediate help.
...
l.1 \ProvidesPackageRCS $H
eader: /cvsroot/latex-beamer/latex-beamer/themes/t...
make[2]: *** [LaTeX.mk:823: packaging-tutorial.de.pdf] Error 1
make[2]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
make[1]: *** [debian/rules:17: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:5: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/packaging-tutorial.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
Bug#921787: kombu: FTBFS (failing tests)
Package: src:kombu
Version: 4.2.1-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --with python2,python3,sphinxdoc --buildsystem=pybuild
dh_update_autotools_config -i -O--buildsystem=pybuild
dh_autoreconf -i -O--buildsystem=pybuild
dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config
running config
I: pybuild base:217: python3.7 setup.py config
running config
dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python setup.py build
running build
running build_py
creating /<>/.pybuild/cpython2_2.7_kombu/build/kombu
[... snipped ...]
t/unit/utils/test_div.py .. [ 91%]
t/unit/utils/test_encoding.py [ 92%]
t/unit/utils/test_functional.py .. [ 95%]
t/unit/utils/test_imports.py . [ 95%]
t/unit/utils/test_json.py ...[ 96%]
t/unit/utils/test_objects.py .. [ 97%]
t/unit/utils/test_scheduling.py ... [ 97%]
t/unit/utils/test_time.py [ 98%]
t/unit/utils/test_url.py .. [ 99%]
t/unit/utils/test_utils.py ..[ 99%]
t/unit/utils/test_uuid.py .. [100%]
=== FAILURES ===
_ test_Channel.test_basic_consume_registers_ack_status _
self =
def test_basic_consume_registers_ack_status(self):
self.channel.wait_returns = 'my-consumer-tag'
self.channel.basic_consume('foo', no_ack=True)
> assert 'my-consumer-tag' in self.channel.no_ack_consumers
E AssertionError: assert 'my-consumer-tag' in set(['m'])
E+ where set(['m']) = .no_ack_consumers
E+where = .channel
t/unit/transport/test_pyamqp.py:73: AssertionError
=== warnings summary ===
t/unit/test_serialization.py::test_Serialization::()::test_msgpack_loads
/<>/kombu/serialization.py:373: PendingDeprecationWarning:
encoding is deprecated, Use raw=False instead.
return unpackb(s, encoding='utf-8')
t/unit/test_serialization.py::test_Serialization::()::test_msgpack_dumps
/<>/kombu/serialization.py:373: PendingDeprecationWarning:
encoding is deprecated, Use raw=False instead.
return unpackb(s, encoding='utf-8')
/<>/kombu/serialization.py:373: PendingDeprecationWarning:
encoding is deprecated, Use raw=False instead.
return unpackb(s, encoding='utf-8')
-- Docs: https://docs.pytest.org/en/latest/warnings.html
=== 1 failed, 1005 passed, 130 skipped, 3 warnings in 22.79 seconds
E: pybuild pybuild:338: test: plugin custom failed with: exit code=1: python2.7
setup.py test
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7
--system=custom "--test-args={interpreter} setup.py test" returned exit code 13
make[1]: *** [debian/rules:16: override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/kombu.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
Bug#921776: bliss: FTBFS (LaTeX error)
Package: src:bliss
Version: 0.73-2
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --with autoreconf --builddirectory=_build --parallel
dh_update_autotools_config -i -O--builddirectory=_build -O--parallel
dh_autoreconf -i -O--builddirectory=_build -O--parallel
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: copying file 'build-aux/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:19: installing 'build-aux/compile'
configure.ac:16: installing 'build-aux/config.guess'
[... snipped ...]
Generating file member index...
Generating example index...
finalizing index lists...
writing tag file...
lookup cache used 185/65536 hits=1285 misses=221
finished...
cd /<>/_build/DEBIAN/doc/html && { \
rm -f *.md5 jquery.js ; \
rdfind -outputname /dev/null -makesymlinks true . ; \
symlinks -r -c -s -v . ; \
ln -sf /usr/share/javascript/jquery/jquery.js ; \
}
Now scanning ".", found 60 files.
Now have 60 files in total.
Removed 0 files due to nonunique device and inode.
Total size is 384954 bytes or 376 KiB
Removed 60 files due to unique sizes from list.0 files left.
Now eliminating candidates based on first bytes:removed 0 files from list.0
files left.
Now eliminating candidates based on last bytes:removed 0 files from list.0
files left.
Now eliminating candidates based on sha1 checksum:removed 0 files from list.0
files left.
It seems like you have 0 files that are not unique
Totally, 0 B can be reduced.
Now making results file /dev/null
Now making symbolic links. creating
Making 0 links.
cd /<>/_build/DEBIAN/doc/latex && { \
make && mv refman.pdf bliss_refman.pdf ; \
}
make[3]: Entering directory '/<>/_build/DEBIAN/doc/latex'
rm -f *.ps *.dvi *.aux *.toc *.idx *.ind *.ilg *.log *.out *.brf *.blg *.bbl
refman.pdf
pdflatex refman
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian)
(preloaded format=pdflatex)
restricted \write18 enabled.
entering extended mode
(./refman.tex
LaTeX2e <2018-12-01>
make[3]: *** [Makefile:6: refman.pdf] Error 1
make[3]: Leaving directory '/<>/_build/DEBIAN/doc/latex'
make[2]: *** [debian/adhoc/Makefile:30: doc] Error 2
make[2]: Leaving directory '/<>'
make[1]: *** [debian/rules:16: override_dh_auto_build-indep] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:13: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/bliss.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
Bug#921774: ask: FTBFS (LaTeX error)
Package: src:ask
Version: 1.1.1-2
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --with python2
dh_update_autotools_config -i
dh_auto_build -i
make -j1
make[1]: Entering directory '/<>'
make -C doc/
make[2]: Entering directory '/<>/doc'
pdflatex -shell-escape ask-manual.tex
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian)
(preloaded format=pdflatex)
\write18 enabled.
entering extended mode
(./ask-manual.tex
LaTeX2e <2018-12-01>
[... snipped ...]
(/usr/share/texlive/texmf-dist/tex/generic/xstring/xstring.sty
(/usr/share/texlive/texmf-dist/tex/generic/xstring/xstring.tex))
(/usr/share/texlive/texmf-dist/tex/latex/framed/framed.sty)
(/usr/share/texlive/texmf-dist/tex/latex/float/float.sty))
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/hyperref.sty
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-hyperref.sty
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-generic.sty))
(/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty)
(/usr/share/texlive/texmf-dist/tex/latex/oberdiek/auxhook.sty)
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/pd1enc.def)
(/usr/share/texlive/texmf-dist/tex/latex/latexconfig/hyperref.cfg)
(/usr/share/texlive/texmf-dist/tex/latex/url/url.sty))
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/hpdftex.def
(/usr/share/texlive/texmf-dist/tex/latex/oberdiek/rerunfilecheck.sty))
(/usr/share/texlive/texmf-dist/tex/latex/fancyhdr/fancyhdr.sty)
(/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty)
(/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/graphics.cfg)))system
returned with code 256
! Package minted Error: You must have `pygmentize' installed to use this packag
e.
See the minted package documentation for explanation.
Type H for immediate help.
...
l.17 \begin{document}
?
! Emergency stop.
...
l.17 \begin{document}
! ==> Fatal error occurred, no output PDF file produced!
Transcript written on ask-manual.log.
make[2]: *** [Makefile:22: ask-manual-1.1.1.pdf] Error 1
make[2]: Leaving directory '/<>/doc'
make[1]: *** [Makefile:18: doc] Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
make: *** [debian/rules:11: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ask.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
Bug#921791: litl: FTBFS (LaTeX error)
Package: src:litl
Version: 0.1.9-3
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --with autoreconf
dh_update_autotools_config -i
dh_autoreconf -i
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:12: installing './compile'
configure.ac:9: installing './missing'
[... snipped ...]
LaTeX Warning: Reference `litl__write_8h' on page 5 undefined on input line 18.
LaTeX Warning: Reference `utils_2litl__merge_8c' on page 5 undefined on input l
ine 19.
LaTeX Warning: Reference `litl__print_8c' on page 5 undefined on input line 20.
LaTeX Warning: Reference `utils_2litl__split_8c' on page 5 undefined on input l
ine 21.
) [5] [6]
Chapter 4.
(./group__litl__merge.tex
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/ts1phv.fd)
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1pcr.fd)
! Missing } inserted.
}
l.32 \end{DoxyParams}
?
! Emergency stop.
}
l.32 \end{DoxyParams}
! ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
make[3]: *** [Makefile:6: refman.pdf] Error 1
make[3]: Leaving directory '/<>/doc/latex'
make[2]: *** [Makefile:539: latex/refman.pdf] Error 2
make[2]: Leaving directory '/<>/doc'
make[1]: *** [Makefile:444: all-recursive] Error 1
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
make: *** [debian/rules:4: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/litl.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
Bug#921792: log4c: FTBFS (LaTeX error)
Package: src:log4c
Version: 1.2.1-3
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --list-missing
dh: Compatibility levels before 9 are deprecated (level 7 in use)
dh_update_autotools_config -i -O--list-missing
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
autoreconf --verbose --force --install --include=config
autoreconf: Entering directory `.'
autoreconf: configure.in: not using Gettext
autoreconf: running: aclocal -I config --force
aclocal: warning: autoconf input should be named 'configure.ac', not
'configure.in'
autoreconf: configure.in: tracing
autoreconf: running: libtoolize --copy --force
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'config'.
[... snipped ...]
LaTeX Warning: Reference `rollingpolicy__type__sizewin_8h' on page 6 undefined
on input line 23.
Underfull \vbox (badness 1308) has occurred while \output is active [6]
LaTeX Warning: Reference `version_8h' on page 7 undefined on input line 24.
) (./structlog4c__appender__type.tex) (./structlog4c__buffer__t.tex)
(./structlog4c__layout__type.tex [7]) (./structlog4c__location__info__t.tex)
(./structlog4c__logging__event__t.tex [8]) (./structlog4c__rc__t.tex
LaTeX Warning: Reference `init_8h_aaa454b3272145399cf10a897819c8a05' on page 9
undefined on input line 20.
[9]) (./structlog4c__rollingpolicy__type.tex) (./appender_8h.tex
Underfull \hbox (badness 1) in paragraph at lines 8--11
[10] [11]
! Missing } inserted.
}
l.87 \end{DoxyParams}
?
! Emergency stop.
}
l.87 \end{DoxyParams}
Output written on refman.dvi (12 pages, 31964 bytes).
Transcript written on refman.log.
make[4]: *** [Makefile:19: refman.dvi] Error 1
make[4]: Leaving directory '/<>/doc/latex'
make[3]: *** [Makefile:482: log4c.pdf] Error 2
make[3]: Leaving directory '/<>/doc'
make[2]: *** [Makefile:530: all-recursive] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [Makefile:394: all] Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
make: *** [debian/rules:9: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/log4c.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
Bug#921782: gmpc: FTBFS (error: Assigning delegate without required target)
Package: src:gmpc
Version: 11.8.16-14
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep
dh_update_autotools_config -i
dh_autoreconf -i
configure.ac:44: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in
body
../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2672: _AC_LINK_IFELSE is expanded from...
../../lib/autoconf/general.m4:2689: AC_LINK_IFELSE is expanded from...
m4/libtool.m4:1022: _LT_SYS_MODULE_PATH_AIX is expanded from...
m4/libtool.m4:4170: _LT_LINKER_SHLIBS is expanded from...
m4/libtool.m4:5253: _LT_LANG_C_CONFIG is expanded from...
m4/libtool.m4:138: _LT_SETUP is expanded from...
m4/libtool.m4:67: LT_INIT is expanded from...
configure.ac:44: the top level
[... snipped ...]
Widgets/GmpcVolume.vala:111.40-111.70: warning: use of possibly unassigned
parameter `requisition'
public override void size_request (out Gtk.Requisition requisition) {
^^^
Providers/music-tree.vala:212.8-212.32: warning: use of possibly unassigned
parameter `list'
list.append((owned)item);
^
Providers/music-tree.vala:176.3-176.30: warning: use of possibly unassigned
parameter `list'
out List list,
Providers/music-tree.vala:244.3-244.27: warning: use of possibly unassigned
parameter `list'
list.concat((owned)temp);
^
Providers/music-tree.vala:250.4-250.28: warning: use of possibly unassigned
parameter `list'
list.concat((owned)temp);
^
Providers/music-tree.vala:256.5-256.29: warning: use of possibly unassigned
parameter `list'
list.concat((owned)temp);
^
Providers/music-tree.vala:233.3-233.35: warning: use of possibly unassigned
parameter `list'
out List list,
^
Widgets/gmpc-widgets-qtable.vala:26.2-26.8: warning: attribute `compact' never
used
[compact]
^^^
Providers/HTBackdrops.vala:186.23-186.30: warning: copying delegates is not
supported
Providers/LyrDB.vala:240.17-240.24: warning: copying delegates is not supported
Providers/ChartLyrics.vala:109.23-109.30: warning: copying delegates is not
supported
vala/gmpc-easy-command.vala:213.6-213.79: error: Assigning delegate without
required target in scope
model.get(iter, 1, out name, 2, out
pattern, 3, out callback, 4, out data);
^^
vala/gmpc-url-fetching-gui.vala:88.26-88.39: warning: copying delegates is not
supported
vala/gmpc-url-fetching-gui.vala:89.29-89.45: warning: copying delegates is not
supported
Compilation failed: 1 error(s), 667 warning(s)
make[4]: *** [Makefile:2201: gmpc_vala.stamp] Error 1
make[4]: Leaving directory '/<>/src'
make[3]: *** [Makefile:849: all] Error 2
make[3]: Leaving directory '/<>/src'
make[2]: *** [Makefile:498: all-recursive] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [Makefile:426: all] Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
make: *** [debian/rules:6: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gmpc.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
Bug#921785: gtk-sharp3: FTBFS ('MONO_PROFILE_ENTER_LEAVE' undeclared)
Package: src:gtk-sharp3
Version: 2.99.3-2
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --with cli
dh_update_autotools_config -i
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- \
--libdir=/usr/lib \
--enable-debug \
CSC=/usr/bin/mono-csc
./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode
--disable-dependency-tracking --libdir=/usr/lib --enable-debug
CSC=/usr/bin/mono-csc
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
[... snipped ...]
libtool: link: ( cd ".libs" && rm -f "libgtksharpglue-3.la" && ln -s
"../libgtksharpglue-3.la" "libgtksharpglue-3.la" )
make[4]: Leaving directory '/<>/gtk/glue'
Making all in gui-thread-check
make[4]: Entering directory '/<>/gtk/gui-thread-check'
Making all in profiler
make[5]: Entering directory '/<>/gtk/gui-thread-check/profiler'
/bin/bash ../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
-I../../.. -D_REENTRANT -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include
-I/usr/lib/pkgconfig/../../include/mono-2.0 -Wall -Wdate-time
-D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -g -Wall -Wunused
-Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes
-Wmissing-prototypes -Wnested-externs -Wshadow -Wpointer-arith -Wno-cast-qual
-Wcast-align -Wwrite-strings -c -o gui-thread-check.lo gui-thread-check.c
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../.. -D_REENTRANT
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include
-I/usr/lib/pkgconfig/../../include/mono-2.0 -Wall -Wdate-time
-D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -g -Wall -Wunused
-Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes
-Wmissing-prototypes -Wnested-externs -Wshadow -Wpointer-arith -Wno-cast-qual
-Wcast-align -Wwrite-strings -c gui-thread-check.c -fPIC -DPIC -o
.libs/gui-thread-check.o
gui-thread-check.c:90:1: warning: no previous prototype for
'mono_profiler_startup' [-Wmissing-prototypes]
mono_profiler_startup (const char *desc)
^
gui-thread-check.c: In function 'mono_profiler_startup':
gui-thread-check.c:94:2: warning: implicit declaration of function
'mono_profiler_install'; did you mean 'mono_profiler_startup'?
[-Wimplicit-function-declaration]
mono_profiler_install (NULL, NULL);
^
mono_profiler_startup
gui-thread-check.c:94:2: warning: nested extern declaration of
'mono_profiler_install' [-Wnested-externs]
gui-thread-check.c:95:2: warning: implicit declaration of function
'mono_profiler_install_enter_leave'; did you mean
'mono_profiler_enable_coverage'? [-Wimplicit-function-declaration]
mono_profiler_install_enter_leave (simple_method_enter, NULL);
^
mono_profiler_enable_coverage
gui-thread-check.c:95:2: warning: nested extern declaration of
'mono_profiler_install_enter_leave' [-Wnested-externs]
gui-thread-check.c:96:2: warning: implicit declaration of function
'mono_profiler_set_events'; did you mean 'mono_profiler_startup'?
[-Wimplicit-function-declaration]
mono_profiler_set_events (MONO_PROFILE_ENTER_LEAVE);
^~~~
mono_profiler_startup
gui-thread-check.c:96:2: warning: nested extern declaration of
'mono_profiler_set_events' [-Wnested-externs]
gui-thread-check.c:96:28: error: 'MONO_PROFILE_ENTER_LEAVE' undeclared (first
use in this function); did you mean 'MONO_NATIVE_INTERFACE'?
mono_profiler_set_events (MONO_PROFILE_ENTER_LEAVE);
^~~~
MONO_NATIVE_INTERFACE
gui-thread-check.c:96:28: note: each undeclared identifier is reported only
once for each function it appears in
make[5]: *** [Makefile:454: gui-thread-check.lo] Error 1
make[5]: Leaving directory '/<>/gtk/gui-thread-check/profiler'
make[4]: *** [Makefile:377: all-recursive] Error 1
make[4]: Leaving directory '/<>/gtk/gui-thread-check'
make[3]: *** [Makefile:593: all-recursive] Error 1
make[3]: Leaving directory '/<>/gtk'
make[2]: *** [Makefile:438: all-recursive] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [Makefile:365: all] Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
make: *** [debian/rules:20:
Bug#921775: avr-libc: FTBFS (LaTeX error)
Package: src:avr-libc Version: 1:2.0.0+Atmel3.6.1-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep test -f debian/rules cd libc/avr-libc && ./bootstrap + rm -rf avr/lib + ./devtools/gen-avr-lib-tree.sh Generating source directories: avr/lib/avr2/ avr/lib/avr2/at90s1200 avr/lib/avr2/attiny11 avr/lib/avr2/attiny12 avr/lib/avr2/attiny15 avr/lib/avr2/attiny28 avr/lib/avr2/at90s4414 avr/lib/avr2/at90s4434 [... snipped ...] pnmtopng: 12 colors found Fixing transparency for open.png pnmtopng: 2 colors found Fixing transparency for releases.png pnmtopng: 2 colors found Fixing transparency for splitbar.png pnmtopng: 7 colors found Fixing transparency for sync_off.png pnmtopng: 54 colors found Fixing transparency for sync_on.png pnmtopng: 57 colors found Fixing transparency for tab_a.png pnmtopng: 27 colors found Fixing transparency for tab_b.png pnmtopng: 30 colors found Fixing transparency for tab_h.png pnmtopng: 32 colors found Fixing transparency for tab_s.png pnmtopng: 35 colors found echo timestamp > fix_png cd latex_src && make refman.pdf make[5]: Entering directory '/<>/avr-libc-2.0.0+Atmel3.6.1/libc/avr-libc/doc/api/latex_src' rm -f *.ps *.dvi *.aux *.toc *.idx *.ind *.ilg *.log *.out *.brf *.blg *.bbl refman.pdf pdflatex refman This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) (preloaded format=pdflatex) restricted \write18 enabled. entering extended mode (./refman.tex LaTeX2e <2018-12-01> make[5]: *** [Makefile:6: refman.pdf] Error 1 make[5]: Leaving directory '/<>/avr-libc-2.0.0+Atmel3.6.1/libc/avr-libc/doc/api/latex_src' make[4]: [Makefile:653: avr-libc-user-manual.pdf] Error 2 (ignored) cp latex_src/refman.pdf avr-libc-user-manual.pdf cp: cannot stat 'latex_src/refman.pdf': No such file or directory make[4]: *** [Makefile:654: avr-libc-user-manual.pdf] Error 1 make[4]: Leaving directory '/<>/avr-libc-2.0.0+Atmel3.6.1/libc/avr-libc/doc/api' make[3]: *** [Makefile:380: all-recursive] Error 1 make[3]: Leaving directory '/<>/avr-libc-2.0.0+Atmel3.6.1/libc/avr-libc/doc' make[2]: *** [Makefile:435: all-recursive] Error 1 make[2]: Leaving directory '/<>/avr-libc-2.0.0+Atmel3.6.1/libc/avr-libc' make[1]: *** [Makefile:374: all] Error 2 make[1]: Leaving directory '/<>/avr-libc-2.0.0+Atmel3.6.1/libc/avr-libc' make: *** [debian/rules:14: build-stamp] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant part) The build was made in my autobuilder with "dpkg-buildpackage -A" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/avr-libc.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
Bug#921781: fis-gtm: FTBFS (dh_auto_configure fails)
Package: src:fis-gtm Version: 6.3-005-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep dh_update_autotools_config -i dh_autoreconf -i debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' dh_auto_configure -- -DCMAKE_INSTALL_PREFIX:PATH=/usr -DGTM_INSTALL_DIR=lib/x86_64-linux-gnu/fis-gtm/V6.3-005_x86_64 -DCMAKE_BUILD_TYPE=Release cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DCMAKE_INSTALL_PREFIX:PATH=/usr -DGTM_INSTALL_DIR=lib/x86_64-linux-gnu/fis-gtm/V6.3-005_x86_64 -DCMAKE_BUILD_TYPE=Release .. -- The C compiler identification is GNU 8.2.0 -- The ASM compiler identification is GNU -- Found assembler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info [... snipped ...] Run Build Command:"/usr/bin/make" "cmTC_76390/fast" make[2]: Entering directory '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp' /usr/bin/make -f CMakeFiles/cmTC_76390.dir/build.make CMakeFiles/cmTC_76390.dir/build make[3]: Entering directory '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp' Building C object CMakeFiles/cmTC_76390.dir/feature_tests.c.o /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2-std=c99 -o CMakeFiles/cmTC_76390.dir/feature_tests.c.o -c /<>/obj-x86_64-linux-gnu/CMakeFiles/feature_tests.c Linking C executable cmTC_76390 /usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_76390.dir/link.txt --verbose=1 /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -rdynamic CMakeFiles/cmTC_76390.dir/feature_tests.c.o -o cmTC_76390 make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp' make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp' Feature record: C_FEATURE:1c_function_prototypes Feature record: C_FEATURE:1c_restrict Feature record: C_FEATURE:0c_static_assert Feature record: C_FEATURE:1c_variadic_macros Detecting C [-std=c90] compiler features compiled with the following output: Change Dir: /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp Run Build Command:"/usr/bin/make" "cmTC_da08a/fast" make[2]: Entering directory '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp' /usr/bin/make -f CMakeFiles/cmTC_da08a.dir/build.make CMakeFiles/cmTC_da08a.dir/build make[3]: Entering directory '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp' Building C object CMakeFiles/cmTC_da08a.dir/feature_tests.c.o /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2-std=c90 -o CMakeFiles/cmTC_da08a.dir/feature_tests.c.o -c /<>/obj-x86_64-linux-gnu/CMakeFiles/feature_tests.c Linking C executable cmTC_da08a /usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_da08a.dir/link.txt --verbose=1 /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -rdynamic CMakeFiles/cmTC_da08a.dir/feature_tests.c.o -o cmTC_da08a make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp' make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp' Feature record: C_FEATURE:1c_function_prototypes Feature record: C_FEATURE:0c_restrict Feature record: C_FEATURE:0c_static_assert Feature record: C_FEATURE:0c_variadic_macros dh_auto_configure: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DCMAKE_INSTALL_PREFIX:PATH=/usr -DGTM_INSTALL_DIR=lib/x86_64-linux-gnu/fis-gtm/V6.3-005_x86_64 -DCMAKE_BUILD_TYPE=Release .. returned exit code 1 make[1]: *** [debian/rules:24: override_dh_auto_configure] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:21: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant part) The
Bug#921783: graphite2: FTBFS (LaTeX error)
Package: src:graphite2
Version: 1.3.13-7
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --with python3 --buildsystem=cmake --builddirectory=build
dh_update_autotools_config -i -O--buildsystem=cmake -O--builddirectory=build
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- -DCMAKE_BUILD_TYPE:STRING=Release
-DGRAPHITE2_NTRACING:BOOL=ON -DLIB_SUFFIX=/x86_64-linux-gnu
-DPYTHON_EXECUTABLE=/usr/bin/python3
cd build && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles"
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu
-DCMAKE_BUILD_TYPE:STRING=Release -DGRAPHITE2_NTRACING:BOOL=ON
-DLIB_SUFFIX=/x86_64-linux-gnu -DPYTHON_EXECUTABLE=/usr/bin/python3 ..
-- Found PythonInterp: /usr/bin/python3 (found suitable version "3.7.2",
minimum required is "3.6")
-- The C compiler identification is GNU 8.2.0
-- The CXX compiler identification is GNU 8.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
[... snipped ...]
LaTeX Warning: Reference `Font_8h' on page 5 undefined on input line 3.
LaTeX Warning: Reference `Log_8h' on page 5 undefined on input line 4.
LaTeX Warning: Reference `Segment_8h' on page 5 undefined on input line 5.
LaTeX Warning: Reference `Types_8h' on page 5 undefined on input line 6.
) [5] [6]
Chapter 4.
(./structgr__face__ops.tex
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1pcr.fd)
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/ts1phv.fd) [7])
(./structgr__faceinfo.tex
! Missing } inserted.
}
l.84 \end{DoxyEnumFields}
?
! Emergency stop.
}
l.84 \end{DoxyEnumFields}
! ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
make[6]: *** [Makefile:6: refman.pdf] Error 1
make[6]: Leaving directory '/<>/build/doc/doxygen/latex'
make[5]: *** [doc/CMakeFiles/docs.dir/build.make:90:
doc/doxygen/latex/refman.pdf] Error 2
make[5]: Leaving directory '/<>/build'
make[4]: *** [CMakeFiles/Makefile2:1048: doc/CMakeFiles/docs.dir/all] Error 2
make[4]: Leaving directory '/<>/build'
make[3]: *** [CMakeFiles/Makefile2:1055: doc/CMakeFiles/docs.dir/rule] Error 2
make[3]: Leaving directory '/<>/build'
make[2]: *** [Makefile:412: docs] Error 2
make[2]: Leaving directory '/<>/build'
dh_auto_build: cd build && make -j1 docs returned exit code 2
make[1]: *** [debian/rules:14: override_dh_auto_build-indep] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/graphite2.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
Bug#921779: doxygen: FTBFS (LaTeX error)
Package: src:doxygen Version: 1.8.13-10 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh_testdir /usr/bin/make -C jquery install make[1]: Entering directory '/<>/jquery' java -jar /usr/share/yui-compressor/yui-compressor.jar jquery-1.7.1.js > jquery-1.7.1-min.js java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.ui-1.8.18.core.js > jquery.ui-1.8.18.core-min.js java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.ui-1.8.18.widget.js > jquery.ui-1.8.18.widget-min.js java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.ui-1.8.18.mouse.js > jquery.ui-1.8.18.mouse-min.js java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.ui-1.8.18.resizable.js > jquery.ui-1.8.18.resizable-min.js java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.ba-1.3-hashchange.js > jquery.ba-1.3-hashchange-min.js java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.scrollTo-1.4.2.js > jquery.scrollTo-1.4.2-min.js java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.powertip-1.2.0.js > jquery.powertip-1.2.0-min.js java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.ui-0.2.3.touch-punch.js > jquery.ui-0.2.3.touch-punch-min.js java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.smartmenus-1.0.0.js > jquery.smartmenus-1.0.0-min.js [... snipped ...] [100%] Generating trouble.doc cd /<>/build/doc && /usr/bin/cmake -E copy /<>/doc/trouble.doc /<>/build/doc/ [100%] Generating xmlcmds.doc cd /<>/build/doc && /usr/bin/cmake -E copy /<>/doc/xmlcmds.doc /<>/build/doc/ [100%] Generating Latex and HTML documentation. cd /<>/build/doc && /<>/build/bin/doxygen This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) (preloaded format=latex) restricted \write18 enabled. entering extended mode (./_formulas.tex LaTeX2e <2018-12-01> make[4]: Leaving directory '/<>/build' [100%] Built target run_doxygen /usr/bin/make -f doc/CMakeFiles/doxygen_pdf.dir/build.make doc/CMakeFiles/doxygen_pdf.dir/depend make[4]: Entering directory '/<>/build' cd /<>/build && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> /<>/doc /<>/build /<>/build/doc /<>/build/doc/CMakeFiles/doxygen_pdf.dir/DependInfo.cmake --color= Dependee "/<>/build/doc/CMakeFiles/doxygen_pdf.dir/DependInfo.cmake" is newer than depender "/<>/build/doc/CMakeFiles/doxygen_pdf.dir/depend.internal". Dependee "/<>/build/doc/CMakeFiles/CMakeDirectoryInformation.cmake" is newer than depender "/<>/build/doc/CMakeFiles/doxygen_pdf.dir/depend.internal". Scanning dependencies of target doxygen_pdf make[4]: Leaving directory '/<>/build' /usr/bin/make -f doc/CMakeFiles/doxygen_pdf.dir/build.make doc/CMakeFiles/doxygen_pdf.dir/build make[4]: Entering directory '/<>/build' [100%] Generating Doxygen Manual PDF. cd /<>/build/latex && /usr/bin/cmake -E remove refman.tex cd /<>/build/latex && /usr/bin/cmake -E copy /<>/build/doc/doxygen_manual.tex . cd /<>/build/latex && /usr/bin/cmake -E copy /<>/build/doc/manual.sty . cd /<>/build/latex && /usr/bin/epstopdf /<>/doc/doxygen_logo.eps --outfile=doxygen_logo.pdf cd /<>/build/latex && /usr/bin/pdflatex -shell-escape doxygen_manual.tex This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) (preloaded format=pdflatex) \write18 enabled. entering extended mode (./doxygen_manual.tex LaTeX2e <2018-12-01> make[4]: *** [doc/CMakeFiles/doxygen_pdf.dir/build.make:62: doc/CMakeFiles/doxygen_pdf] Error 1 make[4]: Leaving directory '/<>/build' make[3]: *** [CMakeFiles/Makefile2:445: doc/CMakeFiles/doxygen_pdf.dir/all] Error 2 make[3]: Leaving directory '/<>/build' make[2]: *** [CMakeFiles/Makefile2:484: doc/CMakeFiles/docs.dir/rule] Error 2 make[2]: Leaving directory '/<>/build' make[1]: *** [Makefile:301: docs] Error 2 make[1]: Leaving directory '/<>/build' make: *** [debian/rules:60: build-stamp] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant part) The build was made in my autobuilder with "dpkg-buildpackage -A" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/doxygen.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
Bug#921780: esajpip: FTBFS (LaTeX error)
Package: src:esajpip
Version: 0.1~bzr33-4
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep
dh_update_autotools_config -i
dh_auto_configure -i
debian/rules override_dh_auto_build-indep
make[1]: Entering directory '/<>'
/usr/bin/make documentation
make[2]: Entering directory '/<>'
make -C doc
make[3]: Entering directory '/<>/doc'
fig2dev -L pstex jpip_fig.fig > jpip_fig.eps
(fig2dev -L pstex_t -p jpip_fig jpip_fig.fig | sed
's/includegraphics{/includegraphics{..\//g') > jpip_fig.tex
epstopdf jpip_fig.eps
fig2dev -L pstex partition.fig > partition.eps
[... snipped ...]
LaTeX Warning: Reference `socket_8h' on page 10 undefined on input line 92.
LaTeX Warning: Reference `socket__stream_8cc' on page 10 undefined on input lin
e 93.
LaTeX Warning: Reference `socket__stream_8h' on page 10 undefined on input line
94.
) [10]
Chapter 5.
(./namespacedata.tex (/usr/share/texlive/texmf-dist/tex/latex/psnfss/ts1phv.fd)
[11]
Underfull \hbox (badness 1) detected at line 68
[][][]
Underfull \hbox (badness 1) detected at line 83
[][][]
) (./namespacehttp.tex [12]) (./namespaceipc.tex [13]
! Missing } inserted.
}
l.58 \end{DoxyEnumFields}
?
! Emergency stop.
}
l.58 \end{DoxyEnumFields}
! ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
make[4]: *** [Makefile:6: refman.pdf] Error 1
make[4]: Leaving directory '/<>/doc/latex'
make[3]: *** [Makefile:23: documentation] Error 2
rm codestream.eps partition.eps client_manager.eps architecture.eps jpip_fig.eps
make[3]: Leaving directory '/<>/doc'
make[2]: *** [Makefile:111: documentation] Error 2
make[2]: Leaving directory '/<>'
make[1]: *** [debian/rules:29: override_dh_auto_build-indep] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:5: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/esajpip.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
Bug#921786: kim-api: FTBFS (F90-F-0000-Internal compiler error. process_formal_arguments: Function argument with mismatched size that is neither integer nor floating-point)
Package: src:kim-api Version: 2.0~beta2.gita734d1-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep dh_update_autotools_config -i dh_autoreconf -i debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' mkdir -p /<>/debian/home dh_auto_configure -- -DKIM_API_BUILD_MODELS_AND_DRIVERS=ON cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DKIM_API_BUILD_MODELS_AND_DRIVERS=ON .. -- The CXX compiler identification is GNU 8.2.0 -- The C compiler identification is GNU 8.2.0 -- The Fortran compiler identification is Flang 99.99.1 -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works [... snipped ...] /usr/bin/cmake -E touch CMakeFiles/kim-api.dir/fortran/src/kim_length_unit_f.f90.o.provides.build [ 24%] Building Fortran object CMakeFiles/kim-api.dir/fortran/src/kim_log_f.f90.o /usr/bin/f95 -Dkim_api_EXPORTS -I"/<>/obj-x86_64-linux-gnu/Fortran_MODULES" -I"/<>/obj-x86_64-linux-gnu" -I"/<>/cpp/include" -I"/<>/c/include" -I"/<>/cpp/src" -I"/<>/fortran/include" -std=f2003 -Wall -Wextra -pedantic -ffree-line-length-none -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -JFortran_MODULES -fPIC -c "/<>/fortran/src/kim_log_f.f90" -o CMakeFiles/kim-api.dir/fortran/src/kim_log_f.f90.o flang: warning: argument unused during compilation: '-ffree-line-length-none' [-Wunused-command-line-argument] /usr/bin/cmake -E cmake_copy_f90_mod Fortran_MODULES/kim_log_f_module.mod CMakeFiles/kim-api.dir/kim_log_f_module.mod.stamp Flang /usr/bin/cmake -E touch CMakeFiles/kim-api.dir/fortran/src/kim_log_f.f90.o.provides.build [ 25%] Building Fortran object CMakeFiles/kim-api.dir/fortran/src/kim_log_verbosity_f.f90.o /usr/bin/f95 -Dkim_api_EXPORTS -I"/<>/obj-x86_64-linux-gnu/Fortran_MODULES" -I"/<>/obj-x86_64-linux-gnu" -I"/<>/cpp/include" -I"/<>/c/include" -I"/<>/cpp/src" -I"/<>/fortran/include" -std=f2003 -Wall -Wextra -pedantic -ffree-line-length-none -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -JFortran_MODULES -fPIC -c "/<>/fortran/src/kim_log_verbosity_f.f90" -o CMakeFiles/kim-api.dir/fortran/src/kim_log_verbosity_f.f90.o flang: warning: argument unused during compilation: '-ffree-line-length-none' [-Wunused-command-line-argument] /usr/bin/cmake -E cmake_copy_f90_mod Fortran_MODULES/kim_log_verbosity_f_module.mod CMakeFiles/kim-api.dir/kim_log_verbosity_f_module.mod.stamp Flang /usr/bin/cmake -E touch CMakeFiles/kim-api.dir/fortran/src/kim_log_verbosity_f.f90.o.provides.build [ 25%] Building Fortran object CMakeFiles/kim-api.dir/fortran/src/kim_model_compute_arguments_create_f.f90.o /usr/bin/f95 -Dkim_api_EXPORTS -I"/<>/obj-x86_64-linux-gnu/Fortran_MODULES" -I"/<>/obj-x86_64-linux-gnu" -I"/<>/cpp/include" -I"/<>/c/include" -I"/<>/cpp/src" -I"/<>/fortran/include" -std=f2003 -Wall -Wextra -pedantic -ffree-line-length-none -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -JFortran_MODULES -fPIC -c "/<>/fortran/src/kim_model_compute_arguments_create_f.f90" -o CMakeFiles/kim-api.dir/fortran/src/kim_model_compute_arguments_create_f.f90.o flang: warning: argument unused during compilation: '-ffree-line-length-none' [-Wunused-command-line-argument] /usr/bin/cmake -E cmake_copy_f90_mod Fortran_MODULES/kim_model_compute_arguments_create_f_module.mod CMakeFiles/kim-api.dir/kim_model_compute_arguments_create_f_module.mod.stamp Flang /usr/bin/cmake -E touch CMakeFiles/kim-api.dir/fortran/src/kim_model_compute_arguments_create_f.f90.o.provides.build [ 26%] Building Fortran object CMakeFiles/kim-api.dir/fortran/src/kim_model_compute_arguments_destroy_f.f90.o /usr/bin/f95 -Dkim_api_EXPORTS -I"/<>/obj-x86_64-linux-gnu/Fortran_MODULES" -I"/<>/obj-x86_64-linux-gnu" -I"/<>/cpp/include" -I"/<>/c/include" -I"/<>/cpp/src" -I"/<>/fortran/include" -std=f2003 -Wall -Wextra -pedantic -ffree-line-length-none -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -JFortran_MODULES -fPIC -c "/<>/fortran/src/kim_model_compute_arguments_destroy_f.f90" -o CMakeFiles/kim-api.dir/fortran/src/kim_model_compute_arguments_destroy_f.f90.o flang: warning: argument unused during compilation: '-ffree-line-length-none' [-Wunused-command-line-argument] /usr/bin/cmake -E cmake_copy_f90_mod Fortran_MODULES/kim_model_compute_arguments_destroy_f_module.mod CMakeFiles/kim-api.dir/kim_model_compute_arguments_destroy_f_module.mod.stamp Flang /usr/bin/cmake -E touch
Bug#921777: bugwarrior: FTBFS (failing tests)
Package: src:bugwarrior
Version: 1.6.0-2
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules binary-indep
dh binary-indep --with python3,sphinxdoc --buildsystem=pybuild
dh_update_autotools_config -i -O--buildsystem=pybuild
dh_autoreconf -i -O--buildsystem=pybuild
dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python3.7 setup.py config
running config
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
PYTHONPATH=. http_proxy='127.0.0.1:9' sphinx-build -N -bhtml bugwarrior/docs/
bugwarrior/docs/_build/html # HTML generator
Running Sphinx v1.7.9
making output directory...
loading pickled environment... not yet created
loading intersphinx inventory from http://docs.python.org/objects.inv...
[... snipped ...]
Traceback (most recent call last):
File "/<>/tests/test_db.py", line 78, in test_synchronize
db.synchronize(iter((issue,)), config, 'general')
File "/<>/bugwarrior/db.py", line 289, in synchronize
key_list = build_key_list(services)
File "/<>/bugwarrior/db.py", line 459, in build_key_list
keys[target] = get_service(target).ISSUE_CLASS.UNIQUE_KEY
File "/<>/bugwarrior/services/__init__.py", line 41, in
get_service
return epoint.load()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2345,
in load
self.require(*args, **kwargs)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2368,
in require
items = working_set.resolve(reqs, env, installer, extras=self.extras)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 789, in
resolve
raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.VersionConflict: (future 0.16.0 (/usr/lib/python3/dist-packages),
Requirement.parse('future!=0.16.0'))
==
ERROR: test_udas (tests.test_db.TestUDAs)
--
Traceback (most recent call last):
File "/<>/tests/test_db.py", line 146, in test_udas
udas = sorted(list(db.get_defined_udas_as_strings(config, 'general')))
File "/<>/bugwarrior/db.py", line 466, in
get_defined_udas_as_strings
uda_list = build_uda_config_overrides(services)
File "/<>/bugwarrior/db.py", line 507, in
build_uda_config_overrides
targets_udas.update(get_service(target).ISSUE_CLASS.UDAS)
File "/<>/bugwarrior/services/__init__.py", line 41, in
get_service
return epoint.load()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2345,
in load
self.require(*args, **kwargs)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2368,
in require
items = working_set.resolve(reqs, env, installer, extras=self.extras)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 789, in
resolve
raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.VersionConflict: (future 0.16.0 (/usr/lib/python3/dist-packages),
Requirement.parse('future!=0.16.0'))
--
Ran 117 tests in 0.666s
FAILED (SKIP=4, errors=2)
make[1]: *** [debian/rules:13: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:4: binary-indep] Error 2
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/bugwarrior.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
Bug#921772: CVE-2018-1000652
On Fri, 08 Feb 2019 23:37:20 +0100, Moritz Muehlenhoff wrote: > This was assigned CVE-2018-1000652: > https://github.com/JabRef/jabref/issues/4229 > https://github.com/JabRef/jabref/commit/89f855d76713b4cd25ac0830c719cd61c511851e Thanks Moritz. I've added a slightly adjusted and trimmed-down version of the of upstream commit to git. Which fails to build with /build/jabref-3.8.2+ds/src/main/java/net/sf/jabref/logic/importer/fileformat/MsBibImporter.java:16: error: package org.slf4j does not exist import org.slf4j.Logger; ^ /build/jabref-3.8.2+ds/src/main/java/net/sf/jabref/logic/importer/fileformat/MsBibImporter.java:17: error: package org.slf4j does not exist import org.slf4j.LoggerFactory; ^ /build/jabref-3.8.2+ds/src/main/java/net/sf/jabref/logic/importer/fileformat/MsBibImporter.java:29: error: cannot find symbol private static final Logger LOGGER = LoggerFactory.getLogger(MsBibImporter.class); ^ symbol: class Logger location: class MsBibImporter Seems like we either need a new build dependency, or remove the logging part, or rewrite it … I'd be grateful for help from Java experts :) Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- NP: Eagles signature.asc Description: Digital Signature
Bug#921773: i3lock: Failed attempts count wraps around after 2^32 wrong login attempts
Package: i3lock Version: 2.8-1 Severity: minor Dear Maintainer, i3lock can show the number of failed attempts using the -f flag. If the number of failed attempts is higher than 999, it shows “>999” – but the value shown was “1” again, after I manually incremented the value saved in i3lock memory to 2^32-1 and entered a wrong password again. I think one can duplicate this pretty easily using scanmem … To be clear, I expected the amount of failed attempts to be “>999”, without any wraparound behaviour. Note that the man page for i3lock does not contain a description of “>999” behaviour for the -f flag. I chose “Severity: minor” since it looks like a cosmetic bug to me. -- System Information: Debian Release: 9.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 4.9.0-7-686 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages i3lock depends on: ii libc6 2.24-11+deb9u3 ii libcairo2 1.14.8-1 ii libev4 1:4.22-1+b1 ii libpam0g1.1.8-3.6 ii libxcb-dpms01.12-1 ii libxcb-image0 0.4.0-1+b2 ii libxcb-shm0 1.12-1 ii libxcb-util00.3.8-3+b2 ii libxcb-xinerama01.12-1 ii libxcb-xkb1 1.12-1 ii libxcb1 1.12-1 ii libxkbcommon-x11-0 0.7.1-2~deb9u1 ii libxkbcommon0 0.7.1-2~deb9u1 i3lock recommends no packages. i3lock suggests no packages. -- no debconf information
Bug#895131: (linux-perf-4.16: Add libopencsd support to perf)
On Fri, 8 Feb 2019 04:04:13 + Wookey wrote: [...] > Hmm. Looks like there has been a revamp of the templates for > tools. Now the extra build-dep needs to go in > debian/templates/control.tools-versioned.in now. For some reason all > these build-deps seem to have lost their build-profile info (except > for asciidoc). I don't understand why that would be so. We don't want those > extra build-deps in stage1? [...] The single list of Build-Depends was getting hard to manage. So I changed debian/bin/gencontrol.py to extract Build-Depends from each binary package template, qualify them with the architectures and build- profiles specified for that binary package, and append them to Build- Depends-Arch or -Indep as appropriate. So in a binary package template you only need to specify architecture or profile qualifications for a build-dependency if the binary package should sometimes be built without it. Ben. -- Ben Hutchings Logic doesn't apply to the real world. - Marvin Minsky signature.asc Description: This is a digitally signed message part
Bug#921756: closed by Alf Gaida (Re: libfm-qt: FTBFS (dh_auto_configure fails))
To be more verbose - libfm-qt don't depend on libfm anymore (no part of LXQt does directly anymore) - so we removed the cmake find for from the build tools. Even if we would find libfm-dev it wouldn't build anymore because of some now deprecated things we don't allow anymore in the code. So waiting is the only chance. Alf
Bug#916277: closed by Johannes 'josch' Schauer (Bug#916277: fixed in alot 0.8-1)
Quoting Debian Bug Tracking System (2019-02-08 23:39:06) > #916277: alot: please package new upstream release 0.8 > > It has been closed by Johannes 'josch' Schauer . Great! Thanks alot¹, - Jonas ¹ Pun intended :-) -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#867671: closed by Stephen Kitt (Bug#867671: fixed in libratbag 0.9.904-3)
On 2019-02-08 21:27, Stephen Kitt wrote: > It was staring me in the face: you tested with 0.9.904-2 and marked the bug Damned race conditions ... I didn't realize that there were two uploads in a short timeframe. I first saw your closing message, then I found the bug showing up again in my latest test run (but your -3 upload hadn't reached my mirror, yet, even at the time I reopened the bug), so it was only -2 getting tested Running tests again, but the package itself looks good now in -3 :-) > as found in 0.9.904-3 (which is where the bug was fixed). copy+paste from the subject, since that obviously must have been the failing version :-( > There’s a few hours I won’t be getting back :-(. Sorry for that. Andreas
Bug#921772: CVE-2018-1000652
Package: jabref Severity: grave Tags: security This was assigned CVE-2018-1000652: https://github.com/JabRef/jabref/issues/4229 https://github.com/JabRef/jabref/commit/89f855d76713b4cd25ac0830c719cd61c511851e Cheers, Moritz
Bug#921756: closed by Alf Gaida (Re: libfm-qt: FTBFS (dh_auto_configure fails))
fixed 921756 0.14.0-3 thanks > thanks for filing this - i suggest to do nothing, just wait a bit, btw. > this would be the relevant lines of the build log: Oh, I see. Forgot to check the package in unstable, sorry. Nevertheless, I'm going to mark this as "fixed" in the unstable version. That way, anybody doing QA rebuilds of buster (not that there is a lot of people doing that, but who knows) will see that the problem is already solved. Thanks a lot.
Bug#921387: UI on HIDPI too small
Hi Rene, On Fri, Feb 08, 2019 at 07:41:58PM +0100, Rene Engelhard wrote: > screen #0: > dimensions:1920x1080 pixels (290x170 millimeters) > resolution:168x161 dots per inch > depths (7):24, 1, 4, 8, 15, 16, 32 > root window id:0x39c > depth of root window:24 planes > number of colormaps:minimum 1, maximum 1 > default colormap:0x23 > default number of colormap cells:256 > preallocated pixels:black 0, white 16777215 > options:backing-store WHEN MAPPED, save-unders NO > largest cursor:1920x1080 $ xrandr --verbose Screen 0: minimum 320 x 200, current 3840 x 2160, maximum 8192 x 8192 eDP-1 connected primary 3840x2160+0+0 (0x67) normal (normal left inverted right x axis y axis) 344mm x 194mm Identifier: 0x62 Timestamp: 90357 Subpixel: unknown Gamma: 1.0:1.3:1.7 Brightness: 0.55 Clones: CRTC: 0 CRTCs: 0 1 2 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: EDID: 00004d108d14 051c0104a52213780ead27a95335bc25 0c51540001010101010101010101 0101010101014dd000a0f0703e803020 350058c21018 00fe0046 4e564452804c513135364431 000241032801120b010a202000b6 scaling mode: Full aspect supported: Full, Center, Full aspect Broadcast RGB: Automatic supported: Automatic, Full, Limited 16:235 link-status: Good supported: Good, Bad CONNECTOR_ID: 71 supported: 71 non-desktop: 0 range: (0, 1) (I don't understand everything in there...) > Does export SAL_USE_VCLPLUGIN=gtk3 (install libreoffice-gtk3...) change it? > That would > use the "gtk3" plugin. (As done automatically when LO detects it runs under > GNOME) Yes, texts are now a little larger - but in the UI not very much. Cheers, Toni
Bug#921770: mutt: Openning attach - denied permission
Package: mutt
Version: 1.10.1-2
Severity: normal
Dear Maintainer,
When I try to open an attach, I got:
"File open Error home/marcelo/.mutt/temp/anydocument.pdf: permission denied."
This occur with .odt, .doc, docx, .pdf, .txt etc
Any file is not opened.
I make a video for that. Here is it. Please, could you see it here?
https://www.dropbox.com/s/61sb07hx4stvbcs/mutt-file-not-open.mp4?dl=0
Please, how can I bypass this problem?
Thanks
-- Package-specific info:
Mutt 1.10.1 (2018-07-13)
Copyright (C) 1996-2016 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for details.
System: Linux 4.19.0-2-amd64 (x86_64)
ncurses: ncurses 6.1.20181013 (compiled with 6.1)
libidn: 1.33 (compiled with 1.33)
hcache backend: tokyocabinet 1.4.48
Compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 8.2.0-3'
--with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr
--with-gcc-major-version-only --program-suffix=-8
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie
--with-system-zlib --with-target-system-zlib --enable-objc-gc=auto
--enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none --without-cuda-driver
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 8.2.0 (Debian 8.2.0-3)
Configure options: '--build=x86_64-linux-gnu' '--prefix=/usr'
'--includedir=\${prefix}/include' '--mandir=\${prefix}/share/man'
'--infodir=\${prefix}/share/info' '--sysconfdir=/etc' '--localstatedir=/var'
'--disable-silent-rules' '--libdir=\${prefix}/lib/x86_64-linux-gnu'
'--libexecdir=\${prefix}/lib/x86_64-linux-gnu' '--disable-maintainer-mode'
'--disable-dependency-tracking' '--with-mailpath=/var/mail'
'--enable-compressed' '--enable-debug' '--enable-fcntl' '--enable-hcache'
'--enable-gpgme' '--enable-imap' '--enable-smtp' '--enable-pop'
'--enable-sidebar' '--enable-nntp' '--enable-dotlock' '--disable-fmemopen'
'--with-curses' '--with-gnutls' '--with-gss' '--with-idn' '--with-mixmaster'
'--with-sasl' '--without-gdbm' '--without-bdb' '--without-qdbm'
'--with-tokyocabinet' 'build_alias=x86_64-linux-gnu' 'CFLAGS=-g -O2
-fdebug-prefix-map=/build/mutt-XxBiSz/mutt-1.10.1=. -fstack-protector-strong
-Wformat -Werror=format-security' 'LDFLAGS=-Wl,-z,relro -Wl,-z,now'
'CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2'
Compilation CFLAGS: -Wall -pedantic -Wno-long-long -g -O2
-fdebug-prefix-map=/build/mutt-XxBiSz/mutt-1.10.1=. -fstack-protector-strong
-Wformat -Werror=format-security
Compile options:
-DOMAIN
+DEBUG
-HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK
+USE_POP +USE_IMAP +USE_SMTP
-USE_SSL_OPENSSL +USE_SSL_GNUTLS +USE_SASL +USE_GSS +HAVE_GETADDRINFO
+HAVE_REGCOMP -USE_GNU_REGEX
+HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET
+HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +HAVE_FUTIMENS
+CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME +CRYPT_BACKEND_GPGME
-EXACT_ADDRESS -SUN_ATTACHMENT
+ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET
+HAVE_LANGINFO_YESEXPR
+HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN -HAVE_LIBIDN2 +HAVE_GETSID
+USE_HCACHE +USE_SIDEBAR +USE_COMPRESSED
-ISPELL
SENDMAIL="/usr/sbin/sendmail"
MAILPATH="/var/mail"
PKGDATADIR="/usr/share/mutt"
SYSCONFDIR="/etc"
EXECSHELL="/bin/sh"
MIXMASTER="mixmaster"
To contact the developers, please mail to .
To report a bug, please contact the Mutt maintainers via gitlab:
https://gitlab.com/muttmua/mutt/issues
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing'), (100, 'unstable'), (50, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8),
LANGUAGE=pt_BR:pt:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages mutt depends on:
ii libassuan02.5.2-1
ii libc6
Bug#868466: php-cas: CVE-2017-1000071
On Sat, Jul 15, 2017 at 09:06:41PM +0200, Salvatore Bonaccorso wrote: > Source: php-cas > Version: 1.3.3-1 > Severity: important > Tags: security upstream > Forwarded: https://github.com/Jasig/phpCAS/issues/228 > > Hi, > > the following vulnerability was published for php-cas. > > CVE-2017-171[0]: > | Jasig phpCAS version 1.3.4 is vulnerable to an authentication bypass > | in the validateCAS20 function when configured to authenticate against > | an old CAS server. > > If you fix the vulnerability please also make sure to include the > CVE (Common Vulnerabilities & Exposures) id in your changelog entry. Fixed in https://github.com/apereo/phpCAS/commit/c9ba00327fd0ac8faecc62ce150c1986022856cd Cheers, Moritz
Bug#921722: Please stop making libraries recommending qpdf
Definitely a bug. I have no idea why I did that. Probably a cut and paste error when I first create the package years ago. I will fix and upload a new version. Thanks for the report. On Fri, Feb 8, 2019 at 7:39 AM Laurent Bigonville wrote: > Source: qpdf > Version: 8.4.0-1 > Severity: normal > > Hi, > > Are there any reasons why the libqpdf Recommends qpdf? Does the library > use an executable contained in that package? > > Kind regards, > > Laurent Bigonville > > -- System Information: > Debian Release: buster/sid > APT prefers unstable-debug > APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, > 'experimental-debug'), (1, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) > Kernel taint flags: TAINT_WARN > Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), > LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy > > -- no debconf information > >
Bug#921550: Acknowledgement (nginx: Default nginx.conf leaves sites vulnerable to BREACH (and does not warn about it))
> A previous bug (#773332) was filed about this and was closed in 2015 > because a warning had been added in the configuration example. I do > not find this warning anymore. The warning *is* in fact present in /etc/nginx/sites-available/default, sorry. -- Gabriel
Bug#921768: gtg-trace: FTBFS (mv: cannot stat './latex/refman.pdf': No such file or directory)
Package: src:gtg-trace
Version: 0.2-2+dfsg-4
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-arch
dh build-arch --with autotools-dev,autoreconf
dh: The autotools-dev sequence is deprecated and replaced by dh in debhelper
(>= 9.20160115)
dh: This feature will be removed in compat 12.
dh_update_autotools_config -a
dh_autoreconf -a
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,
libtoolize: and rerunning libtoolize and aclocal.
libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
configure.ac:12: installing './compile'
configure.ac:9: installing './missing'
src/Makefile.am: installing './depcomp'
[... snipped ...]
LaTeX Warning: Reference `GTGPaje_8h' on page 7 undefined on input line 12.
LaTeX Warning: Reference `GTGPaje__Basic_8h' on page 7 undefined on input line
13.
LaTeX Warning: Reference `GTGReplay_8h' on page 7 undefined on input line 14.
LaTeX Warning: Reference `GTGStack_8h' on page 7 undefined on input line 15.
LaTeX Warning: Reference `GTGTypes_8h' on page 7 undefined on input line 16.
) [7] [8]
Chapter 5.
(./group__traceType.tex
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/ts1phv.fd)
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1pcr.fd)
! Missing } inserted.
}
l.56 \end{DoxyEnumFields}
?
! Emergency stop.
}
l.56 \end{DoxyEnumFields}
! ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
/<>/gtg-trace-0.2-2+dfsg/doc
mv: cannot stat './latex/refman.pdf': No such file or directory
make[3]: *** [Makefile:592: gtg_refmanual.pdf] Error 1
make[3]: Leaving directory '/<>/gtg-trace-0.2-2+dfsg/doc'
make[2]: *** [Makefile:476: install-am] Error 2
make[2]: Leaving directory '/<>/gtg-trace-0.2-2+dfsg/doc'
make[1]: *** [Makefile:447: install-recursive] Error 1
make[1]: Leaving directory '/<>/gtg-trace-0.2-2+dfsg'
dh_auto_install: make -j1 install
DESTDIR=/<>/gtg-trace-0.2-2\+dfsg/debian/tmp AM_UPDATE_INFO_DIR=no
returned exit code 2
make: *** [debian/rules:4: binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned
exit status 2
(The above is just how the build ends and not necessarily the most relevant
part)
The build was made in my autobuilder with "dpkg-buildpackage -B"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gtg-trace.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
Bug#905697: kdepimlibs: don't depend on libical
Hey, for me it looks like we won't be able to get kdepimlibs without libical 2 for buster. Keep in mind, that kdepimlibs is an old grufted lib set that we also would like to kill. But we also have other packages depending on it like: * basket * kopete (it has a QT5 version in experimental, but this is suitable as replacement yet). and other that may can be killed. extract libical 2 out of kdepimlibs is not that simple, as the whole interface will leak into akonadi-calendar, calcore, calutils,... In short I won't have the time to do the work and test it in the near future. I added pino to this bug report, as pino successfully extracted other parts of old kdelibs/kdepimlibs. hefee -- On Donnerstag, 17. Januar 2019 12:11:46 CET Emilio Pozuelo Monfort wrote: > On 11/01/2019 13:37, Emilio Pozuelo Monfort wrote: > > On 08/08/2018 10:38, Emilio Pozuelo Monfort wrote: > >> Source: kdepimlibs > >> Version: 4:4.14.10-10 > >> Severity: serious > >> Control: block 884128 with -1 > >> > >> Hi, > >> > >> libical2 from src:libical is superseded by libical3 (src:libical3). > >> > >> Please either port kdepimlibs to libical3 or try to disable the > >> libical support, so that we can only ship src:libical3 in buster. > > > > Could someone who knows kdepimlibs take a look at this? Can we disable > > libical support in kdepimlibs for buster? This is the last blocker for > > the libical 2 removal. > > Hi Sandro, > > Lisandro said you may be able to help with this. Do you know if libical > support could be disabled in kdepimlibs, or if the newer version libical3 > could be used? > >From [1] it seems that libical is kind of optional, though I don't know if > >we > can disable the bits to drop that or if those bits have rdeps. Since > kdepimlibs is the last rdep of the old libical version, fixing this would > allow us to drop that one from buster. Otherwise the RC bugs that it has > will need to be fixed and we'll have to ship with two versions of the > library. > > Thanks, > Emilio > > [1] > https://sources.debian.org/src/kdepimlibs/4:4.14.10-10/CMakeLists.txt/#L81 signature.asc Description: This is a digitally signed message part.
Bug#918058: aria2: CVE-2019-3500: Metadata and potential password leaks via --log=
On Wed, Jan 02, 2019 at 09:57:11PM +0100, Salvatore Bonaccorso wrote: > Source: aria2 > Version: 1.30.0-2 > Severity: normal > Tags: security upstream > Forwarded: https://github.com/aria2/aria2/issues/1329 > Control: found -1 1.34.0-3 > > Hi, > > The following vulnerability was published for aria2. > > CVE-2019-3500[0]: > | aria2c in aria2 1.33.1, when --log is used, can store an HTTP Basic > | Authentication username and password in a file, which might allow local > | users to obtain sensitive information by reading this file. > > The security impact is somehow disputable/limited, still reporting it > for tracking purpose with regard of the upstream issue. Once a fix > available it can land in Debian a well. Fixed in https://github.com/aria2/aria2/commit/37368130ca7de5491a75fd18a20c5c5cc641824a Can we get that in before buster? Cheers, Moritz
Bug#921769: moarvm: FTBFS (error: 'MP_GEN_RANDOM_MAX' undeclared)
Package: src:moarvm
Version: 2018.12+dfsg-2
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-arch
dh build-arch
dh_update_autotools_config -a
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/moarvm-2018.12+dfsg'
perl Configure.pl \
--prefix=/usr \
--libdir=/usr/lib/moar \
--debug \
--has-libtommath \
--has-libuv \
--has-libatomic_ops \
--has-libffi
Welcome to MoarVM!
[... snipped ...]
two_complement_bitop(ia, ib, ic, mp_##opname); \
^~~
src/math/bigintops.c:512:1: note: in expansion of macro 'MVM_BIGINT_BINARY_OP_2'
MVM_BIGINT_BINARY_OP_2(or , { sc = sa | sb; })
^~
src/math/bigintops.c:264:40: note: expected 'int (*)(mp_int *, mp_int *, mp_int
*)' {aka 'int (*)(struct *, struct *, struct
*)'} but argument is of type 'int (*)(const mp_int *, const mp_int
*, mp_int *)' {aka 'int (*)(const struct *, const struct
*, struct *)'}
int (*mp_bitop)(mp_int *, mp_int *, mp_int
*)) {
~~^~~
src/math/bigintops.c: In function 'MVM_bigint_xor':
src/math/bigintops.c:447:42: warning: passing argument 4 of
'two_complement_bitop' from incompatible pointer type
[-Wincompatible-pointer-types]
two_complement_bitop(ia, ib, ic, mp_##opname); \
^~~
src/math/bigintops.c:513:1: note: in expansion of macro 'MVM_BIGINT_BINARY_OP_2'
MVM_BIGINT_BINARY_OP_2(xor, { sc = sa ^ sb; })
^~
src/math/bigintops.c:264:40: note: expected 'int (*)(mp_int *, mp_int *, mp_int
*)' {aka 'int (*)(struct *, struct *, struct
*)'} but argument is of type 'int (*)(const mp_int *, const mp_int
*, mp_int *)' {aka 'int (*)(const struct *, const struct
*, struct *)'}
int (*mp_bitop)(mp_int *, mp_int *, mp_int
*)) {
~~^~~
src/math/bigintops.c: In function 'MVM_bigint_and':
src/math/bigintops.c:447:42: warning: passing argument 4 of
'two_complement_bitop' from incompatible pointer type
[-Wincompatible-pointer-types]
two_complement_bitop(ia, ib, ic, mp_##opname); \
^~~
src/math/bigintops.c:514:1: note: in expansion of macro 'MVM_BIGINT_BINARY_OP_2'
MVM_BIGINT_BINARY_OP_2(and, { sc = sa & sb; })
^~
src/math/bigintops.c:264:40: note: expected 'int (*)(mp_int *, mp_int *, mp_int
*)' {aka 'int (*)(struct *, struct *, struct
*)'} but argument is of type 'int (*)(const mp_int *, const mp_int
*, mp_int *)' {aka 'int (*)(const struct *, const struct
*, struct *)'}
int (*mp_bitop)(mp_int *, mp_int *, mp_int
*)) {
~~^~~
src/math/bigintops.c: In function 'MVM_bigint_rand':
src/math/bigintops.c:1166:13: error: 'MP_GEN_RANDOM_MAX' undeclared (first use
in this function); did you mean 'UV_ERRNO_MAX'?
if (MP_GEN_RANDOM_MAX >= abs(smallint_max)) {
^
UV_ERRNO_MAX
src/math/bigintops.c:1166:13: note: each undeclared identifier is reported only
once for each function it appears in
src/math/bigintops.c:1167:35: warning: implicit declaration of function
'MP_GEN_RANDOM'; did you mean 'UV_FS_O_RANDOM'?
[-Wimplicit-function-declaration]
mp_digit result_int = MP_GEN_RANDOM();
^
UV_FS_O_RANDOM
make[2]: *** [Makefile:621: src/math/bigintops.o] Error 1
make[2]: Leaving directory '/<>/moarvm-2018.12+dfsg'
dh_auto_build: make -j1 NOISY=1 returned exit code 2
make[1]: *** [debian/rules:51: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>/moarvm-2018.12+dfsg'
make: *** [debian/rules:37: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
The build was made in my autobuilder with "dpkg-buildpackage -B"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/moarvm.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
Bug#871617: CVE-2017-3224
On Sun, Oct 08, 2017 at 10:12:35PM +1100, Scott Leggett wrote: > On 2017-09-30.18:24, Moritz Muehlenhoff wrote: > > On Thu, Aug 10, 2017 at 01:10:46AM +0200, Moritz Muehlenhoff wrote: > > > Source: quagga > > > Severity: important > > > Tags: security > > > > > > Please see http://www.kb.cert.org/vuls/id/793496 > > > > What's the status, is that fixed upstream? > > Hi Moritz, > > Sorry I didn't respond earlier on this. > > No, this is not fixed in any version of quagga. > > I have discussed this CVE with upstream and they don't see it as a very > high impact bug. Has this been fixed in the mean time? Cheers, Moritz
Bug#921767: CVE-2018-12029
Source: passenger Severity: grave Tags: security This was assigned CVE-2018-12029: https://blog.phusion.nl/2018/06/12/passenger-5-3-2-various-security-fixes/ https://github.com/phusion/passenger/commit/207870f5b7f5cc240587ab0977d6046782ae1d86 Cheers, Moritz
Bug#889838: unzip: CVE-2018-1000035: Heap-based buffer overflow in password protected ZIP archives
On Fri, Feb 08, 2019 at 10:40:12PM +0100, Moritz Mühlenhoff wrote: > On Thu, Feb 08, 2018 at 01:29:07AM +0100, Santiago Vila wrote: > > forwarded 889838 http://www.info-zip.org/phpBB3/viewtopic.php?f=7=548 > > thanks > > > > Hello Salvatore. Thanks for the report. I've just forwarded it > > upstream as a first step. > > Was there any outcome/result? The phpBB forum in the forwarded line above disappeared from earth, so I have to contact them privately using an email address which they dislike very much to be shown in public. Maybe I offer to host a phpbb forum on my own if they can't, as there is currently no sane way to mark an issue as "forwarded". I'll take a look at the suse patch in your other email and will probably go ahead without upstream if the patch is clean enough. Thanks.
Bug#921766: starpu-contrib: FTBFS (mv: cannot stat 'latex/refman.pdf': No such file or directory)
Package: src:starpu-contrib Version: 1.2.6+dfsg-5 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-arch dh build-arch --parallel -Bbuild --with autoreconf dh_testdir -a -O--parallel -O-Bbuild dh_update_autotools_config -a -O--parallel -O-Bbuild dh_autoreconf -a -O--parallel -O-Bbuild libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'. libtoolize: copying file 'build-aux/ltmain.sh' libtoolize: putting macros in 'm4'. libtoolize: copying file 'm4/libtool.m4' libtoolize: copying file 'm4/ltoptions.m4' libtoolize: copying file 'm4/ltsugar.m4' libtoolize: copying file 'm4/ltversion.m4' libtoolize: copying file 'm4/lt~obsolete.m4' libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac, [... snipped ...] gcc-7 -DHAVE_CONFIG_H -I. -I../../tests -I../src/common -I../include -I../gcc-plugin/include/starpu-gcc -I../starpu-top -I../../include/ -I../src -I../../src/ -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_FORTIFY_SOURCE=1 -Wall -DSTARPU_OPENCL_DATADIR=/usr/share/starpu/opencl -DCL_USE_DEPRECATED_OPENCL_1_1_APIS -Wall -Werror=implicit -Werror=implicit-function-declaration -Wno-unused -O3 -g -O2 -fdebug-prefix-map=/<>/starpu-contrib-1.2.6+dfsg=. -fstack-protector-strong -Wformat -Werror=format-security -gdwarf-2 -g3 -g -c -o simple_cpu_gpu_sched.o `test -f 'sched_policies/simple_cpu_gpu_sched.c' || echo '../../tests/'`sched_policies/simple_cpu_gpu_sched.c :0:0: warning: "_FORTIFY_SOURCE" redefined :0:0: note: this is the location of the previous definition /bin/bash ../libtool --tag=CC --mode=link gcc-7 -Wall -DSTARPU_OPENCL_DATADIR=/usr/share/starpu/opencl -DCL_USE_DEPRECATED_OPENCL_1_1_APIS -Wall -Werror=implicit -Werror=implicit-function-declaration -Wno-unused -O3 -g -O2 -fdebug-prefix-map=/<>/starpu-contrib-1.2.6+dfsg=. -fstack-protector-strong -Wformat -Werror=format-security -gdwarf-2 -g3 -g -lOpenCL -lcudart -lcublas -lcudart -lstdc++-Wl,-z,relro -gdwarf-2 -g3 -g -o sched_policies/simple_cpu_gpu_sched simple_cpu_gpu_sched.o ../src/libstarpu-1.2.la -lhwloc -lrt -lcusparse -lrt -lm -lpthread libtool: link: gcc-7 -Wall -DSTARPU_OPENCL_DATADIR=/usr/share/starpu/opencl -DCL_USE_DEPRECATED_OPENCL_1_1_APIS -Wall -Werror=implicit -Werror=implicit-function-declaration -Wno-unused -O3 -g -O2 -fdebug-prefix-map=/<>/starpu-contrib-1.2.6+dfsg=. -fstack-protector-strong -Wformat -Werror=format-security -gdwarf-2 -g3 -g -Wl,-z -Wl,relro -gdwarf-2 -g3 -g -o sched_policies/.libs/simple_cpu_gpu_sched simple_cpu_gpu_sched.o -lOpenCL -lcublas -lcudart -lstdc++ ../src/.libs/libstarpu-1.2.so -lhwloc -lcusparse -lrt -lm -lpthread gfortran-7 -g -O2 -fdebug-prefix-map=/<>/starpu-contrib-1.2.6+dfsg=. -fstack-protector-strong -c -o starpu_mod.o '../../'include/starpu_mod.f90 gfortran-7 -g -O2 -fdebug-prefix-map=/<>/starpu-contrib-1.2.6+dfsg=. -fstack-protector-strong -c -o init_01.o `test -f 'fortran90/init_01.f90' || echo '../../tests/'`fortran90/init_01.f90 /bin/bash ../libtool --tag=FC --mode=link gfortran-7 -g -O2 -fdebug-prefix-map=/<>/starpu-contrib-1.2.6+dfsg=. -fstack-protector-strong -lOpenCL -lcudart -lcublas -lcudart -lstdc++ -Wl,-z,relro -gdwarf-2 -g3 -g -o fortran90/init_01 starpu_mod.o init_01.o ../src/libstarpu-1.2.la -lhwloc -lrt -lcusparse -lrt -lm -lpthread libtool: link: gfortran-7 -g -O2 -fdebug-prefix-map=/<>/starpu-contrib-1.2.6+dfsg=. -fstack-protector-strong -Wl,-z -Wl,relro -gdwarf-2 -g3 -g -o fortran90/.libs/init_01 starpu_mod.o init_01.o -lOpenCL -lcublas -lcudart -lstdc++ ../src/.libs/libstarpu-1.2.so -lhwloc -lcusparse -lrt -lm -lpthread make[4]: Leaving directory '/<>/starpu-contrib-1.2.6+dfsg/build/tests' make[3]: Leaving directory '/<>/starpu-contrib-1.2.6+dfsg/build/tests' make[2]: Leaving directory '/<>/starpu-contrib-1.2.6+dfsg/build/tests' Making all in doc make[2]: Entering directory '/<>/starpu-contrib-1.2.6+dfsg/build/doc' Making all in doxygen make[3]: Entering directory '/<>/starpu-contrib-1.2.6+dfsg/build/doc/doxygen' warning: Tag `SYMBOL_CACHE_SIZE' at line 370 of file `../../../doc/doxygen/doxygen.cfg' has become obsolete. To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u" warning: Tag `XML_SCHEMA' at line 1507 of file `../../../doc/doxygen/doxygen.cfg' has become obsolete. To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u" warning: Tag `XML_DTD' at line 1513 of file `../../../doc/doxygen/doxygen.cfg' has become obsolete. To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u" /<>/starpu-contrib-1.2.6+dfsg/doc/doxygen/chapters/api/codelet_and_tasks.doxy:673: warning: explicit link request to
Bug#895430: ITP: profanity-omemo -- OMEMO encryption for the Profanity XMPP client
Upstream gave up on this. Closing until somebody continues.
Bug#921276: status update
On 2019-02-03 17:45:32, Antoine Beaupré wrote: > Control: block 921276 by 921286 921285 921287 921288 > > The above estimate is incorrect: docopt is already packaged, for > example. > > I've filed more ITPs for the other (currently) known build-deps, but > that might grow a little more. I didn't notice an RFP for termui > (#890567) so we have a duplicate there (#921286). > > I also filed a bunch of bugs upstream so they issue proper releases. Unfortunately, with the freeze looming on feb 12, it is unlikely this will cross NEW any time soon. It might make it to bullseye eventually, hopefully, but I'll probably take a break from this one until the freeze is over and focus on RC bugfixing. This will give time for upstreams to get their stuff in order as well (specifically, in https://github.com/distatus/battery/issues/9)... A. -- Si les triangles avaient un Dieu, ils lui donneraient trois côtés. - Montesquieu, Lettres persanes
Bug#921496: ITP: swayidle -- Idle management daemon for Wayland
Hello Birger, On Wed 06 Feb 2019 at 07:48AM +01, Birger Schacht wrote: > * Package name: swayidle > Version : 1.2 > Upstream Author : Drew DeVault > * URL : https://github.com/swaywm/swayidle > * License : MIT > Programming Lang: C > Description : Idle management daemon for Wayland > > This is sway's idle management daemon, swayidle. It is compatible with > any Wayland compositor which implements the KDE idle protocol. See the > man page, swayidle(1), for instructions on configuring swayidle. d1cc9e94e01d9cc03e673b7ecf0951e231dc9e24 looks good to upload, but could you just confirm that only you have copyright on debian/, please? Did you do it from scratch, or copy parts from Nicolas' work on the old source package? If you did it all yourself, just confirm that and I will upload. -- Sean Whitton signature.asc Description: PGP signature
Bug#889838: unzip: CVE-2018-1000035: Heap-based buffer overflow in password protected ZIP archives
On Thu, Feb 08, 2018 at 01:29:07AM +0100, Santiago Vila wrote: > forwarded 889838 http://www.info-zip.org/phpBB3/viewtopic.php?f=7=548 > thanks > > Hello Salvatore. Thanks for the report. I've just forwarded it > upstream as a first step. SuSE fixed this with the patch linked from https://bugzilla.novell.com/show_bug.cgi?id=CVE-2018-135 Cheers, Moritz
Bug#889838: unzip: CVE-2018-1000035: Heap-based buffer overflow in password protected ZIP archives
On Thu, Feb 08, 2018 at 01:29:07AM +0100, Santiago Vila wrote: > forwarded 889838 http://www.info-zip.org/phpBB3/viewtopic.php?f=7=548 > thanks > > Hello Salvatore. Thanks for the report. I've just forwarded it > upstream as a first step. Was there any outcome/result? Cheers, Moritz
Bug#921765: workrave: occasionally runs into false activity detection
Package: workrave Version: 1.10.23-2 Severity: important Dear Maintainer, Workrave can work well for hours or even days, but sometimes it falls into unusable state. In that state, even when I don't touch input devices, it either just keeps blinking again and again, finally deciding that it's ignored and postponing a break, or enters a break but stucks after the first second. When I close it via tray icon, the terminal that I ran it from prints that it have exited with segmentation fault, which does not look normal. Moreover, restarting Workrave does not help: it keeps behaving the same. But this issue may evaporate during the session: when I recall about Workrave after a few days and start it again, it may start working well again for some time. Looks like this happens because of external factors, but I have no idea what exactly and how to debug it. -- System Information: Debian Release: buster/sid APT prefers oldoldstable-updates APT policy: (500, 'oldoldstable-updates'), (500, 'oldoldstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=ru_UA.UTF-8, LC_CTYPE=ru_UA.UTF-8 (charmap=UTF-8), LANGUAGE=ru_UA:ru (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages workrave depends on: ii libatk1.0-0 2.30.0-2 ii libatkmm-1.6-1v5 2.28.0-2 ii libc6 2.28-2 ii libcairo-gobject2 1.16.0-2 ii libcairo2 1.16.0-2 ii libcairomm-1.0-1v5 1.12.2-4 ii libdbusmenu-glib4 18.10.20180917~bzr490+repack1-1 ii libdbusmenu-gtk3-4 18.10.20180917~bzr490+repack1-1 ii libfontconfig1 2.13.1-2 ii libfreetype6 2.9.1-3 ii libgcc1 1:8.2.0-14 ii libgdk-pixbuf2.0-0 2.38.0+dfsg-7 ii libgdome2-0 0.8.1+debian-6 ii libglib2.0-0 2.58.2-3 ii libglibmm-2.4-1v5 2.58.0-2 ii libgstreamer1.0-0 1.14.4-1 ii libgtk-3-0 3.24.2-3 ii libgtk2.0-0 2.24.32-3 ii libgtkmm-3.0-1v5 3.24.0-2 ii libice6 2:1.0.9-2 ii libindicator3-7 0.5.0-4 ii libmate-panel-applet-4-1 1.20.3-1 ii libpanel-applet3 3.30.0-2 ii libpango-1.0-0 1.42.4-6 ii libpangocairo-1.0-0 1.42.4-6 ii libpangoft2-1.0-0 1.42.4-6 ii libpangomm-1.4-1v5 2.42.0-2 ii libpulse-mainloop-glib0 12.2-2 ii libpulse0 12.2-2 ii libsigc++-2.0-0v5 2.10.1-2 ii libsm6 2:1.2.2-1+b3 ii libstdc++6 8.2.0-14 ii libx11-6 2:1.6.7-1 ii libxfce4util7 4.12.1-3 ii libxml2 2.9.4+dfsg1-7+b3 ii libxss1 1:1.2.3-1 ii libxtst6 2:1.2.3-1 ii workrave-data 1.10.23-2 ii xfce4-panel 4.12.2-1 workrave recommends no packages. Versions of packages workrave suggests: pn gnome-panel ii gnome-shell 3.30.1-2 -- no debconf information
Bug#921497: ITP: swaylock -- Screen locker for Wayland
Hello Birger, On Wed 06 Feb 2019 at 07:54AM +01, Birger Schacht wrote: > * Package name: swaylock > Version : 1.3 > Upstream Author : Drew DeVault > * URL : https://github.com/swaywm/swaylock > * License : MIT > Programming Lang: C > Description : Screen locker for Wayland > > swaylock is a screen locking utility for Wayland compositors. It is > compatible with any Wayland compositor which implements the following > Wayland protocols: > * wlr-layer-shell > * wlr-input-inhibitor > * xdg-output > * xdg-shell Here is a review of 566c844e8e78c5eff3c5c638e8877efad16f99b0 in your repo on salsa. - The copyright years for upstream need to be 2016-2019, not 2016-2018. - Are you sure that Nicolas doesn't share copyright of debian/? Did you make debian/ from scratch, or copy parts of it from the old sway source package? - There is this Lintian warning; since we are uploading to unstable, ideally you'd add a patch to fix it, and forward that upstream: W: swaylock: manpage-has-errors-from-man usr/share/man/man1/swaylock.1.gz 70: warning: macro ':'' not defined - Be sure to `dch -r` when you've fixed these. Otherwise, we should be good to go. -- Sean Whitton signature.asc Description: PGP signature
Bug#921764: CVE-2019-3825
Source: gdm3 Severity: important This was assigned CVE-2019-3825: https://gitlab.gnome.org/GNOME/gdm/issues/460 Cheers, Moritz
Bug#914833: RFS: python-pyxs/0.4.1-1 [ITP] -- Pure Python XenStore client implementation
Hey nicoo, Awesome, thank you for taking the time! I agree with your edits and have pushed the updated changelog. Kind regards, Benjamin
