Bug#792745: [Pkg-xfce-devel] Bug#792745: lightdm: session refuses to start when theres no space left without informing the user
On lun., 2015-07-20 at 01:25 +0200, alberto fuentes wrote: Basically what i am asking with this bug is, should this error be reported to the user by the DM or not at all and let the user put this puzzle together by themselves as any aceptable and responsible grown up should be able to do anyway?? Yes. There's so many things which won't work if you can't write to the disk that it's not possible to handle them soundly. -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#791869: Output of 'systemctl status' in broken state and just after un-breaking it...
In case it helps, here’s systemctl status as logged during emergency shell. Rick Jul 19 22:43:49 stretch fixup[687]: + systemctl status Jul 19 22:43:49 stretch fixup[687]: * stretch Jul 19 22:43:49 stretch fixup[687]: State: maintenance Jul 19 22:43:49 stretch fixup[687]: Jobs: 0 queued Jul 19 22:43:49 stretch fixup[687]:Failed: 0 units Jul 19 22:43:49 stretch fixup[687]: Since: Sun 2015-07-19 22:41:41 PDT; 2min 7s ago Jul 19 22:43:49 stretch fixup[687]:CGroup: / Jul 19 22:43:49 stretch fixup[687]:|-1 /sbin/init Jul 19 22:43:49 stretch fixup[687]:`-system.slice Jul 19 22:43:49 stretch fixup[687]: |-lvm2-lvmetad.service Jul 19 22:43:49 stretch fixup[687]: | `-287 /sbin/lvmetad -f Jul 19 22:43:49 stretch fixup[687]: |-nfs-common.service Jul 19 22:43:49 stretch fixup[687]: | |-654 /sbin/rpc.statd Jul 19 22:43:49 stretch fixup[687]: | `-677 /usr/sbin/rpc.idmapd Jul 19 22:43:49 stretch fixup[687]: |-emergency.service Jul 19 22:43:49 stretch fixup[687]: | |-682 /bin/sh -c /sbin/sulogin; /bin/systemctl --job-mode=fail --no-block default Jul 19 22:43:49 stretch fixup[687]: | |-684 bash Jul 19 22:43:49 stretch fixup[687]: | |-686 bash -x bin/fixup Jul 19 22:43:49 stretch fixup[687]: | |-687 logger -s -t fixup Jul 19 22:43:49 stretch fixup[687]: | `-701 systemctl status Jul 19 22:43:49 stretch fixup[687]: |-systemd-journald.service Jul 19 22:43:49 stretch fixup[687]: | `-293 /lib/systemd/systemd-journald Jul 19 22:43:49 stretch fixup[687]: |-systemd-timesyncd.service Jul 19 22:43:49 stretch fixup[687]: | `-449 /lib/systemd/systemd-timesyncd Jul 19 22:43:49 stretch fixup[687]: |-systemd-udevd.service Jul 19 22:43:49 stretch fixup[687]: | `-295 /lib/systemd/systemd-udevd Jul 19 22:43:49 stretch fixup[687]: |-rpcbind.service Jul 19 22:43:49 stretch fixup[687]: | `-645 /sbin/rpcbind -w Jul 19 22:43:49 stretch fixup[687]: `-system-ifup.slice Jul 19 22:43:49 stretch fixup[687]:`-ifup@eth0.service Jul 19 22:43:49 stretch fixup[687]: `-605 dhclient -v -pf /run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases eth0 Jul 19 22:43:49 stretch fixup[687]: + vgchange -a ay Jul 19 22:43:49 stretch systemd[1]: Found device /dev/disk/by-uuid/46fac389-6646-4166-af3a-d03e9f885a41. Jul 19 22:43:49 stretch fixup[687]: 3 logical volume(s) in volume group stretch now active Jul 19 22:43:49 stretch systemd[1]: Found device /dev/disk/by-label/HOME. Jul 19 22:43:49 stretch systemd[1]: Found device /dev/disk/by-id/dm-uuid-LVM-04rFhEmC9zV7NuS8clm8ymGQYGH3TifIaxFBoTV3Na3deugGPex3cERrD1rRYvzE. Jul 19 22:43:49 stretch systemd[1]: Found device /dev/disk/by-id/dm-name-stretch-home. Jul 19 22:43:49 stretch fixup[687]: + sleep 5 Jul 19 22:43:49 stretch systemd[1]: Found device /dev/dm-2. Jul 19 22:43:49 stretch systemd[1]: Found device /sys/devices/virtual/block/dm-2. Jul 19 22:43:49 stretch systemd[1]: Starting File System Check on /dev/mapper/stretch-home... Jul 19 22:43:49 stretch systemd[1]: Started File System Check Daemon to report status. Jul 19 22:43:49 stretch systemd[1]: Starting File System Check Daemon to report status... Jul 19 22:43:49 stretch systemd-fsck[712]: HOME: clean, 30/157760 files, 27366/630784 blocks Jul 19 22:43:49 stretch systemd[1]: Started File System Check on /dev/mapper/stretch-home. Jul 19 22:43:49 stretch systemd[1]: Mounting /home... Jul 19 22:43:49 stretch systemd[1]: Mounted /home. Jul 19 22:43:49 stretch kernel: EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null) Jul 19 22:43:53 stretch systemd-timesyncd[449]: Timed out waiting for reply from [2001:418:8405:4002::2]:123 (2.debian.pool.ntp.org). Jul 19 22:43:54 stretch fixup[687]: + systemctl status Jul 19 22:43:54 stretch fixup[687]: * stretch Jul 19 22:43:54 stretch fixup[687]: State: maintenance Jul 19 22:43:54 stretch fixup[687]: Jobs: 0 queued Jul 19 22:43:54 stretch fixup[687]:Failed: 0 units Jul 19 22:43:54 stretch fixup[687]: Since: Sun 2015-07-19 22:41:41 PDT; 2min 12s ago Jul 19 22:43:54 stretch fixup[687]:CGroup: / Jul 19 22:43:54 stretch fixup[687]:|-1 /sbin/init Jul 19 22:43:54 stretch fixup[687]:`-system.slice Jul 19 22:43:54 stretch fixup[687]: |-lvm2-lvmetad.service Jul 19 22:43:54 stretch fixup[687]: | `-287 /sbin/lvmetad -f Jul 19 22:43:54 stretch fixup[687]: |-nfs-common.service Jul 19 22:43:54 stretch fixup[687]: | |-654 /sbin/rpc.statd Jul 19 22:43:54 stretch fixup[687]: | `-677 /usr/sbin/rpc.idmapd Jul 19 22:43:54 stretch fixup[687]: |-emergency.service Jul 19 22:43:54 stretch fixup[687]: | |-682 /bin/sh -c /sbin/sulogin;
Bug#792919: ITP: pytest-tornado -- py.test plugin for testing Tornado applications
Package: wnpp
Severity: wishlist
Owner: Daniel Stender deb...@danielstender.com
* Package name: pytest-tornado
Version : 0.4.4
Upstream Author : Eugeniy Kalinin bur...@gmail.com
* URL : https://github.com/eugeniy/pytest-tornado
* License : Apache-2.0
Programming Lang: Python
Description : py.test plugin for testing Tornado applications
py.test plugin providing fixtures and markers for testing Tornado
applications (asynchronous networking library). It's needed to get
the testsuite of vcp.py running w/o any disabled tests [1], but it would
be great to have some more py.test plugins available in Debian, anyway.
The binaries are going to be python{,3}-pytest-tornado.
[1] https://bugs.debian.org/792700
ITP: vcr.py -- mock your HTTP interactions to simplify and speed up testing
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792831: ejabberd: issues with passwords with special characters
Hi, this is quite an important bug you have found here, thank you for reporting it! Debugging the postinst by adding a set -x to /var/lib/dpkg/info/ejabberd.postinst revealed, that the bug is not in the debconf part, but in ejabberdctl. What you have seen is ejabberdctl's reaction to ejabberdctl register $USER $HOST $PASSWD when $PASSWD contains special characters as in your examples. E.g.: ~# ejabberdctl register admin localhost 'Cbfy=6Yi?mepNOw3!:mBYJmBr7BL[' sh: 1: cannot open Ow3!:: No such file Enabling -x in ejabberdctl shows: + su ejabberd -c /usr/bin/erl -sname ctl-ejabberd -noinput -hidden -pa /usr/lib/x86_64-linux-gnu/ejabberd/ebin -s ejabberd_ctl -extra ejabberd register admin localhost Cbfy=6Yi?mepNOw3!:mBYJmBr7BL[ sh: 1: cannot open Ow3!:: No such file So the problem is somewhere in ctlexec() or later. Regards, -- .''`. Philipp Huebner debala...@debian.org : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#792924: dhclient -r overflows buffer every time
Package: isc-dhcp-client Version: 4.3.2-1 File: /sbin/dhclient # dhclient -v -r *** buffer overflow detected ***: dhclient terminated === Backtrace: = /lib/i386-linux-gnu/i686/cmov/libc.so.6(+0x69409)[0xb73b0409] /lib/i386-linux-gnu/i686/cmov/libc.so.6(__fortify_fail+0x37)[0xb743f7c7] /lib/i386-linux-gnu/i686/cmov/libc.so.6(+0xf69ca)[0xb743d9ca] /lib/i386-linux-gnu/i686/cmov/libc.so.6(__strcpy_chk+0x37)[0xb743cf27] dhclient(+0x23923)[0xb7721923] dhclient(main+0x613)[0xb7704703] /lib/i386-linux-gnu/i686/cmov/libc.so.6(__libc_start_main+0xde)[0xb735f71e] dhclient(+0x74de)[0xb77054de] === Memory map: b6f07000-b6f23000 r-xp 08:07 655540 /lib/i386-linux-gnu/libgcc_s.so.1 b6f23000-b6f24000 rw-p 0001b000 08:07 655540 /lib/i386-linux-gnu/libgcc_s.so.1 b6f33000-b6f3f000 r-xp 08:07 660558 /lib/i386-linux-gnu/i686/cmov/libnss_files-2.21.so b6f3f000-b6f4 r--p b000 08:07 660558 /lib/i386-linux-gnu/i686/cmov/libnss_files-2.21.so b6f4-b6f41000 rw-p c000 08:07 660558 /lib/i386-linux-gnu/i686/cmov/libnss_files-2.21.so b6f41000-b7333000 rw-p 00:00 0 b7333000-b733f000 r-xp 08:07 657484 /lib/i386-linux-gnu/libisccfg-export.so.90.1.0 b733f000-b734 r--p b000 08:07 657484 /lib/i386-linux-gnu/libisccfg-export.so.90.1.0 b734-b7341000 rw-p c000 08:07 657484 /lib/i386-linux-gnu/libisccfg-export.so.90.1.0 b7341000-b7342000 rw-p 00:00 0 b7342000-b7345000 r-xp 08:07 660552 /lib/i386-linux-gnu/i686/cmov/libdl-2.21.so b7345000-b7346000 r--p 2000 08:07 660552 /lib/i386-linux-gnu/i686/cmov/libdl-2.21.so b7346000-b7347000 rw-p 3000 08:07 660552 /lib/i386-linux-gnu/i686/cmov/libdl-2.21.so b7347000-b74f8000 r-xp 08:07 660549 /lib/i386-linux-gnu/i686/cmov/libc-2.21.so b74f8000-b74fb000 r--p 001b 08:07 660549 /lib/i386-linux-gnu/i686/cmov/libc-2.21.so b74fb000-b74fd000 rw-p 001b3000 08:07 660549 /lib/i386-linux-gnu/i686/cmov/libc-2.21.so b74fd000-b74ff000 rw-p 00:00 0 b74ff000-b7556000 r-xp 08:07 655884 /lib/i386-linux-gnu/libisc-export.so.95.5.0 b7556000-b7557000 r--p 00057000 08:07 655884 /lib/i386-linux-gnu/libisc-export.so.95.5.0 b7557000-b7558000 rw-p 00058000 08:07 655884 /lib/i386-linux-gnu/libisc-export.so.95.5.0 b7558000-b7559000 rw-p 00:00 0 b7559000-b76b8000 r-xp 08:07 655890 /lib/i386-linux-gnu/libdns-export.so.100.2.2 b76b8000-b76ba000 r--p 0015e000 08:07 655890 /lib/i386-linux-gnu/libdns-export.so.100.2.2 b76ba000-b76bc000 rw-p 0016 08:07 655890 /lib/i386-linux-gnu/libdns-export.so.100.2.2 b76bc000-b76c5000 r-xp 08:07 655448 /lib/i386-linux-gnu/libirs-export.so.91.0.0 b76c5000-b76c6000 r--p 9000 08:07 655448 /lib/i386-linux-gnu/libirs-export.so.91.0.0 b76c6000-b76c7000 rw-p a000 08:07 655448 /lib/i386-linux-gnu/libirs-export.so.91.0.0 b76d4000-b76d8000 rw-p 00:00 0 b76d8000-b76da000 r--p 00:00 0 [vvar] b76da000-b76db000 r-xp 00:00 0 [vdso] b76db000-b76fc000 r-xp 08:07 655416 /lib/i386-linux-gnu/ld-2.21.so b76fc000-b76fd000 r--p 0002 08:07 655416 /lib/i386-linux-gnu/ld-2.21.so b76fd000-b76fe000 rw-p 00021000 08:07 655416 /lib/i386-linux-gnu/ld-2.21.so b76fe000-b778b000 r-xp 08:07 277596 /sbin/dhclient b778b000-b778c000 r--p 0008c000 08:07 277596 /sbin/dhclient b778c000-b778e000 rw-p 0008d000 08:07 277596 /sbin/dhclient b778e000-b7798000 rw-p 00:00 0 b9722000-b97bf000 rw-p 00:00 0 [heap] bfd75000-bfd96000 rw-p 00:00 0 [stack] 13472 Aborted dhclient -v -r -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792473: cups: After updating to 2.0.3-6 in testing cups interface no longer works
On 19/07/15 22:13, Brian Potkin wrote: On Sun 19 Jul 2015 at 21:41:39 +0100, John Talbut wrote: $ iceweasel (process:1687): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed console.error: [CustomizableUI] Custom widget with id loop-button does not return a valid node console.error: [CustomizableUI] Custom widget with id loop-button does not return a valid node These don't mean that much to me and are probably nothing to do with what we are investigating. They are likely harmless. I thought the output might show a complaint that the program could not connect to localhost:631. root@johnwtnc110:/home/john# netstat -tulpan | grep cups root@johnwtnc110:/home/john# netstat -tulpan Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp0 0 0.0.0.0:17500 0.0.0.0:* LISTEN 1042/dropbox tcp0 0 127.0.0.1:17600 0.0.0.0:* LISTEN 1042/dropbox tcp0 0 127.0.0.1:17603 0.0.0.0:* LISTEN 1042/dropbox tcp0 0 0.0.0.0:111 0.0.0.0:* LISTEN 662/rpcbind tcp0 0 0.0.0.0:37809 0.0.0.0:* LISTEN 702/rpc.statd tcp0 0 0.0.0.0:22 0.0.0.0:* LISTEN This is the worrying bit. You have shown you have cups running but there is no sign here that it is listening for any connection on 127.0.0.1, which is localhost. We need to see your /etc/cups/cupsd.conf. Please would you post it. Send the contents of /etc/hosts too. Hope this helps It does. Cheers, Brian. /etc/cups/cupsd.conf: # # # Sample configuration file for the CUPS scheduler. See man cupsd.conf for a # complete description of this file. # # Log general information in error_log - change warn to debug # for troubleshooting... LogLevel warn # Deactivate CUPS' internal logrotating, as we provide a better one, especially # LogLevel debug2 gets usable now MaxLogSize 0 # Only listen for connections from the local machine. Listen Servername:631 Listen /var/run/cups/cups.sock # Show shared printers on the local network. Browsing On BrowseLocalProtocols dnssd # Default authentication type, when authentication is required... DefaultAuthType Basic # Web interface setting... WebInterface Yes # Restrict access to the server... Location / Order allow,deny /Location # Restrict access to the admin pages... Location /admin Order allow,deny /Location # Restrict access to configuration files... Location /admin/conf AuthType Default Require user @SYSTEM Order allow,deny /Location # Set the default printer/job policies... Policy default # Job/subscription privacy... JobPrivateAccess default JobPrivateValues default SubscriptionPrivateAccess default SubscriptionPrivateValues default # Job-related operations must be done by the owner or an administrator... Limit Create-Job Print-Job Print-URI Validate-Job Order deny,allow /Limit Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job Cancel-My-Jobs Close-Job CUPS-Move-Job CUPS-Get-Document Require user @OWNER @SYSTEM Order deny,allow /Limit # All administration operations require an administrator to authenticate... Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default CUPS-Get-Devices AuthType Default Require user @SYSTEM Order deny,allow /Limit # All printer operations require a printer operator to authenticate... Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After Cancel-Jobs CUPS-Accept-Jobs CUPS-Reject-Jobs AuthType Default Require user @SYSTEM Order deny,allow /Limit # Only the owner or an administrator can cancel or authenticate a job... Limit Cancel-Job CUPS-Authenticate-Job Require user @OWNER @SYSTEM Order deny,allow /Limit Limit All Order deny,allow /Limit /Policy # Set the authenticated printer/job policies... Policy authenticated # Job/subscription privacy... JobPrivateAccess default JobPrivateValues default SubscriptionPrivateAccess default SubscriptionPrivateValues default # Job-related operations must be done by the owner or an administrator... Limit Create-Job Print-Job Print-URI Validate-Job AuthType Default Order deny,allow /Limit Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job Cancel-My-Jobs
Bug#787800: RFS: iperf3/3.0.11-1
Hi Vincent, On Fri, Jul 17, 2015 at 04:08:25PM -0700, Vincent Cheng wrote: Hi Raoul, On Fri, Jul 17, 2015 at 2:05 AM, Raoul Borenius boren...@dfn.de wrote: Hallo Vincent, Thanks for taking the time to check my package! On Sat, Jul 04, 2015 at 03:21:43PM -0700, Vincent Cheng wrote: Control: tag -1 + moreinfo Control: owner -1 ! Hi Raoul, On Fri, Jun 5, 2015 at 12:59 AM, Raoul Borenius boren...@dfn.de wrote: perf3 (3.0.11-1) unstable; urgency=medium * new upstream version * bumped standards version to 3.9.6 Your changes look ok, but I've noticed that src:iperf3 builds library packages that are installed into multiarch paths (because you're using dh compat level 9), but your packages are not actually multiarch-ified. Please implement multiarch support in your package [1]. Thanks for pointing that out! I've followed the multiarch guide and rebuilt the iperf package: https://mentors.debian.net/package/iperf3 Your -dev package should be declared as MA: same as well. Adding Ah, ok. I misread the recipe because it just talked about adding MA: same to the library package. Thanks! multiarch support to your package is also worth mentioning in d/changelog. Ok, added that! Would you mind checking once more? https://mentors.debian.net/package/iperf3 Thanks a lot! Raoul smime.p7s Description: S/MIME cryptographic signature
Bug#791869: Info received (Output of 'systemctl status' in broken state and just after un-breaking it...)
On a hunch, I made the following change # diff /SAVE/etc/lvm/lvm.conf /etc/lvm/lvm.conf 823c823 use_lvmetad = 1 --- use_lvmetad = 0 and ran # update-initramfs -u Then rebooted. The problem went away… As I understand it, this makes LVM always check the actual physical volumes to see which PVs are present, rather than relying on the cached information kept by lvmetad. Since lvmetad is not present in the initramfs (and wouldn’t be useful, even if it was) this allows the PVs to be scanned in the initramfs phase, at the cost of having to re-scan them after switching to real-root… Maybe getting lvmetad into the initramfs, so it can be used there, then doing a strategically placed ‘pvscan —cache’ when switching to real-root, might do the trick? Hope that helps! Rick -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792731: cups: incorrect MIME type on cups.css
Control: tags -1 +patch -unreproducible Le dimanche, 19 juillet 2015, 15.29:28 Stephen Kitt a écrit : On Sun, 19 Jul 2015 12:39:36 +0200, OdyX wrote: Okay. Do you happen to have mime.types or mime.convs files in /etc/cups or /usr/share/cups ? Indeed, I have rather old copies in /etc/cups: % ls -l /etc/cups/mime.* -rw-r--r-- 1 root root 4424 Jul 11 2009 /etc/cups/mime.convs -rw-r--r-- 1 root root 6184 Aug 20 2007 /etc/cups/mime.types Ah, there! Can you confirm that deleting these two configuration files restores the correct behaviour of the webinterface? These files were removed from these paths in CUPS 1.4.0~svn8773-1, in 2009, and weren't cleaned up back then. Let's fix that now! (I can at least confirm that adding those from CUPS 1.3.11 (from snapshot.d.o) indeed breaks the treatment of the cups.css file.) Cheers, OdyXFrom 2e69c25ff31fe3ea38f140198d8582d7b2b7ec4a Mon Sep 17 00:00:00 2001 From: Didier Raboud o...@debian.org Date: Mon, 20 Jul 2015 08:23:50 +0200 Subject: [PATCH] Add maintscript stanzas to properly remove the mime.convs and mime.types conffiles in /etc/cups that are not shipped in this path since 1.4.0~svn8773-1~ Closes: #792731 LP: #1475683 STR: #4593 --- debian/cups.maintscript | 2 ++ 1 file changed, 2 insertions(+) diff --git a/debian/cups.maintscript b/debian/cups.maintscript index 1640bc0..67a6e70 100644 --- a/debian/cups.maintscript +++ b/debian/cups.maintscript @@ -1,3 +1,5 @@ +rm_conffile /etc/cups/mime.convs 1.4.0~svn8773-1~ +rm_conffile /etc/cups/mime.types 1.4.0~svn8773-1~ rm_conffile /etc/cups/acroread.conf 1.6.2-9~ rm_conffile /etc/cups/pdftops.conf 1.6.2-9~ rm_conffile /etc/modprobe.d/blacklist-cups-usblp.conf 1.5.3-2.1~ -- 2.1.4
Bug#790060: jessie-pu: nbd update?
On Sun, Jul 19, 2015 at 04:29:30PM +0200, Julien Cristau wrote:
On Sun, Jul 19, 2015 at 14:37:57 +0200, Wouter Verhelst wrote:
On Sat, Jul 18, 2015 at 02:59:08PM +0100, Adam D. Barratt wrote:
On Sat, 2015-07-18 at 15:33 +0200, Wouter Verhelst wrote:
On Sat, Jul 18, 2015 at 12:07:13PM +0100, Adam D. Barratt wrote:
That's much bigger than I was expecting given your description, and
I'm
not sure all of the changes were intended to be included.
Crap. I fucked up again. Can you reject that, or is it too late?
No problem. There's a gateway policy queue (slightly incorrectly
referred to as stable-new) in front of proposed-updates which we have
to accept or reject packages from before they hit p-u.
I've flagged the upload for rejection but unfortunately just missed the
start of the 13:52 dinstall, so it will need to wait until after that
for dak to notice.
Thanks.
If you don't want me to immediately upload, what do you want me to do
instead?
Send us the proposed (source) debdiff.
Attached.
--
It is easy to love a country that is famous for chocolate and beer
-- Barack Obama, speaking in Brussels, Belgium, 2014-03-26
diff -u nbd-3.8/debian/changelog nbd-3.8/debian/changelog
--- nbd-3.8/debian/changelog
+++ nbd-3.8/debian/changelog
@@ -1,3 +1,10 @@
+nbd (1:3.8-4+deb8u2) jessie; urgency=low
+
+ * Cherry-pick two commits from 3.10 to fix authfile parsing.
+Closes: #785727.
+
+ -- Wouter Verhelst wou...@debian.org Fri, 17 Jul 2015 21:52:40 +0200
+
nbd (1:3.8-4+deb8u1) jessie-security; urgency=medium
* Add fix for CVE-2015-0847. Closes: #784657.
only in patch2:
unchanged:
--- nbd-3.8.orig/nbdsrv.c
+++ nbd-3.8/nbdsrv.c
@@ -21,14 +21,14 @@
#include cliserv.h
-bool address_matches(const char* mask, const void* addr, int af, GError** err)
{
+bool address_matches(const char* mask, const struct sockaddr* addr, GError**
err) {
struct addrinfo *res, *aitmp, hints;
char *masksep;
char privmask[strlen(mask)+1];
int masklen;
- int addrlen = af == AF_INET ? 4 : 16;
+ int addrlen = addr-sa_family == AF_INET ? 4 : 16;
- assert(af == AF_INET || af == AF_INET6);
+ assert(addr-sa_family == AF_INET || addr-sa_family == AF_INET6);
strcpy(privmask, mask);
@@ -50,18 +50,20 @@
}
aitmp = res;
while(res) {
- const uint8_t* byte_s = addr;
+ const uint8_t* byte_s;
uint8_t* byte_t;
uint8_t mask = 0;
int len_left = masklen;
- if(res-ai_family != af) {
+ if(res-ai_family != addr-sa_family) {
goto next;
}
- switch(af) {
+ switch(addr-sa_family) {
case AF_INET:
+ byte_s = (const uint8_t*)struct
sockaddr_in*)addr)-sin_addr));
byte_t = (uint8_t*)struct
sockaddr_in*)(res-ai_addr))-sin_addr));
break;
case AF_INET6:
+ byte_s = (const uint8_t*)struct
sockaddr_in6*)addr)-sin6_addr));
byte_t = (uint8_t*)struct
sockaddr_in6*)(res-ai_addr))-sin6_addr));
break;
}
@@ -129,8 +131,7 @@
if(!(*pos)) {
continue;
}
- struct sockaddr* sa = (struct sockaddr*)opts-clientaddr;
- if(address_matches(line, sa-sa_data, sa-sa_family, NULL)) {
+ if(address_matches(line, (struct sockaddr*)opts-clientaddr,
NULL)) {
fclose(f);
return 1;
}
only in patch2:
unchanged:
--- nbd-3.8.orig/nbdsrv.h
+++ nbd-3.8/nbdsrv.h
@@ -123,14 +123,13 @@
* Check whether a given address matches a given netmask.
*
* @param mask the address or netmask to check against, in ASCII
representation
- * @param addr the address to check, in network byte order
- * @param af the address family of the passed address (AF_INET or AF_INET6)
+ * @param addr the address to check
*
* @return true if the address matches the mask, false otherwise; in case of
* failure to parse netmask, returns false with err set appropriately.
* @todo decide what to do with v6-mapped IPv4 addresses.
*/
-bool address_matches(const char* mask, const void* addr, int af, GError** err);
+bool address_matches(const char* mask, const struct sockaddr* addr, GError**
err);
/**
* Gets a byte to allow for address masking.
only in patch2:
unchanged:
--- nbd-3.8.orig/tests/code/clientacl.c
+++ nbd-3.8/tests/code/clientacl.c
@@ -31,7 +31,7 @@
(((struct
sockaddr_in*)res-ai_addr)-sin_addr),
buf,
Bug#786649: goldendict: Home page package reported by debian package don't exist
tags 786649 patch thanks The attached patch replaces the deprecated Berlios URL with the new URL http://goldendict.org. Cheers, Felix From b9a5c454902b46bf58340bf210799ea613a8c20a Mon Sep 17 00:00:00 2001 From: Felix Gruber fel...@gmx.de Date: Mon, 20 Jul 2015 08:55:33 +0200 Subject: [PATCH] replace deprecated homepage URL --- debian/control | 2 +- debian/copyright | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/debian/control b/debian/control index fb735a4..b9087a9 100644 --- a/debian/control +++ b/debian/control @@ -21,7 +21,7 @@ Build-Depends: cdbs, debhelper (= 7), qt4-qmake, x11proto-record-dev, zlib1g-dev -Homepage: http://goldendict.berlios.de/ +Homepage: http://goldendict.org/ VCS-Browser: http://git.debian.org/?p=collab-maint/goldendict.git;a=summary VCS-Git: git://git.debian.org/collab-maint/goldendict.git diff --git a/debian/copyright b/debian/copyright index 10846c4..4c7428a 100644 --- a/debian/copyright +++ b/debian/copyright @@ -2,7 +2,7 @@ This package was debianized by Dmitry E. Oboukhov di...@avanto.org on Thu Jun 4 00:08:48 MSD 2009. It was downloaded from: - http://goldendict.berlios.de + http://goldendict.org Upstream Author: Konstantin Isakov i...@users.berlios.de -- 2.1.4
Bug#792903: ITP: hdump -- Hexadecimal and ASCII dumper for binary files
On 20/07/15 00:04, Paulo Kretcheu wrote: Description : Hexadecimal and ASCII dumper for binary files Does this have significant advantages over these tools that are already in the archive and likely to be near-ubiquitous on GNU systems? * od -t x1 (part of coreutils, and a subset of its functionality is standardized in POSIX) * hd, aka hexdump (part of bsdmainutils) * xxd (part of vim-common) I personally prefer xxd, because it gives reasonable output (hex + ASCII) without requiring special command-line options, and can also be used in reverse to patch or create binaries from hex input. - Number of columns adjustable by constant in the source. That's not much of an advantage in a binary distribution like Debian. xxd can adjust this at runtime with the -c/-cols command-line option. S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792473: cups: After updating to 2.0.3-6 in testing cups interface no longer works
On Mon 20 Jul 2015 at 07:12:12 +0100, John Talbut wrote: # # Sample configuration file for the CUPS scheduler. See man cupsd.conf for a # complete description of this file. # The web interface has not been used to alter the defaults because the comments are still in the file. # Only listen for connections from the local machine. Listen Servername:631 This second line is not part of the default cupsd.conf. Replace it with Listen localhost:631 and restart cups. How's that now? systemctl cups restart /etc/hosts: 127.0.0.1 localhost 192.168.0.7 johnwtwind.dpetsjohnwtwind 192.168.0.5 johnwtnc110.luton johnwtnc110 # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback ff02::1 ip6-allnodes ff02::2 ip6-allrouters The default /etc/hosts has a line beginning '127.0.1.1'. Mine is 127.0.1.1 jessie.lan jessie It is not a problem for this situation but some software will not work properly if it missing. Regards, Brian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686908: Wrong indexterm sorting order for Norwegian Bokmål (nb)
Control: found -1 1.78.1+dfsg-1 [Petter Reinholdtsen] I tried, and it did not work. I tried the attached patch, and got the (more correct) 'Register' string shown verifying that the correct file was edited, but 'åndsverklov' is still sorted as 'A' and not 'Å'. :) Hi. The index sorting order problem still exist in version 1.78.1+dfsg-1, and I am not sure how to try to fix it. Did I test the wrong thing? -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#420716: Offer Diodes SM5819 SUF4007 SM4937 SM4007 GL1M
img{ border:0; } Dearnbsp;Engineer, Purchaser Nice day! Could you please
check below our data for some diodes? From these data, you will see we are
supplying good quality. If you need any diodes, capacitors from Topdiode or UF
Capacitors factory, please send me inquiry, or please do tell me the contact
person. We have fast responded sales, high quality and reasonable prices. We
are eager to cooperate with you! Part Number Package/Size Chips/Wafer
IF(AV) VF VB IR IFSM TRR nbsp; nbsp; nbsp;SM5817 / B120 /
LL5817 DO-213AB SKY 1A lt;0.45V 20V 0.5uA 25A N/A nbsp;
SM5819 / B140 / LL5819 DO-213AB SKY 1A lt;0.6V 40V 0.5uA 25A
N/A nbsp; nbsp;HSM101 / SUF4001
DO-213AB HER GPP 1A lt;1.0V 50V 5uA 30A lt;50nS nbsp;
HSM108 / SUF4007 DO-213AB HER GPP 1A lt;1.7V 1000V 5uA 30A
lt;75nS nbsp; nbsp;SM4933
DO-213AB FR GPP 1A lt;1.3V 50V 5uA 30A lt;200nS nbsp;
SM4937 DO-213AB FR GPP 1A lt;1.3V 600V 5uA 30A lt;200nS
nbsp; nbsp;SM4007/LL4007 DO-213AB
STD GPP 1A lt;1.1V 1000V 5uA 30A N/A nbsp;
nbsp;GL341A DO-213AA STD GPP 1A lt;1.1V 50V
5uA 10A N/A nbsp;GL341M/GL1M DO-213AA STD GPP 1A lt;1.1V
1000V 5uA 10A N/A nbsp;nbsp; Ms. Win Tang -- Sales Manager Skype:
topdiode Tel.: +86-(0)769 8252 3211 Topdiode Group amp; UF Capacitors Factory
Website ISO 9001: 2008, Military Qualification: GJB90018:2009 for tantalum cap
RoHS, Reach, Halogen free, Metal Conflict Free Manufacturer for: Capacitors,
MOVs, Diodes, Bridge, Transistorsnbsp;
Ifnbsp;younbsp;wishnbsp;tonbsp;benbsp;removednbsp;plsnbsp;advise,nbsp;thennbsp;wenbsp;willnbsp;removenbsp;you,nbsp;andnbsp;wenbsp;apologize.nbsp;nbsp;
nbsp; nbsp;
Bug#792923: After an update, the translation of KDE in french becomes very incomplete
Package: kde-l10n-fr Version: 4:4.14.0-2 Hi, After an update of french Localization of KDE files, the translation becomes very incomplete. For many menus and submenus, before this update, the translation was good. But after this same update, many menus switch from french to english, although french language is chosen in kde settings. The problems occurs for both testing and unstable versions. I wait for a solution to solve the problem. Kind regards, Etienne.
Bug#778159: uswsusp: diff for NMU version 1.0+20120915-6.1
gregor herrmann gre...@debian.org escribió: Control: tags 778159 + pending Dear maintainer, I've prepared an NMU for uswsusp (versioned as 1.0+20120915-6.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. Dear Gregor, thanks a lot for your upload. My gpg key expired and I am waiting the new key upload to the ring (probably the next week). Your upload is fine. Best regards, Rodolfo. -- .''`. : :' : Rodolfo García Peñas (kix) k...@debian.org `. `'` Proud Debian Developer `- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778171: wmmon: diff for NMU version 1.1+20131205-1.1
gregor herrmann gre...@debian.org escribió: Control: tags 778171 + pending Dear maintainer, I've prepared an NMU for wmmon (versioned as 1.1+20131205-1.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. Dear Gregor, as I said for the bug #778159, thanks a lot for your upload. My gpg key expired and I am waiting the new key upload to the ring (probably the next week). Your upload is fine. Best regards, Rodolfo. -- .''`. : :' : Rodolfo García Peñas (kix) k...@debian.org `. `'` Proud Debian Developer `- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792922: Addendum: localy connected printers via parallel interface are working
I have forgetten to mention a detail. The locally connected printers via parallel interface are working after system start with systemd. The printers connected via ethernet don't. All printers are working after system start with sysvinit. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#702201: Patch
Hi. Any reason not to integrate this patch ? I can't tell about the 'smbcontrol nmbd reload-config' part but the 'delaycompress' seems worth adding and is a no-risk change. Thanks. -- Jérôme -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792925: webalizer: Webalizer stopped parsing squid logs (after 1 may 2015) saying Invlid Date Format
Package: webalizer Version: 2.23.05-1 Severity: grave Justification: renders package unusable Dear Maintainer, I've just noticed that my webalizer installation does no more parse my squid log files saying Invalid Date Format to each log record. I've seen that this strange behaviour started last May 1 2015. The package was working with no problem for years, analyzing my squid logs in standard squid format. What can be wrong? Thanks for your collaboration Luca Here what I get if I try to manually invoke the cron.daily start script (I've removed the Quiet Option - Locale is Italian) 10:01:06-root@andromeda:/etc/cron.daily$ ./webalizer 21|less [new_unode] Attenzione: La stringa e' di dimensione eccessiva (517) [new_unode] Attenzione: La stringa e' di dimensione eccessiva (516) [new_unode] Attenzione: La stringa e' di dimensione eccessiva (515) [new_unode] Attenzione: La stringa e' di dimensione eccessiva (514) [new_unode] Attenzione: La stringa e' di dimensione eccessiva (513) [new_unode] Attenzione: La stringa e' di dimensione eccessiva (512) Errore: Tralascio il record (data errata): [19/lug/2015:07:36:00 -] [1] Errore: Tralascio il record (data errata): [19/lug/2015:07:36:51 -] [2] Errore: Tralascio il record (data errata): [19/lug/2015:07:37:11 -] [3] Errore: Tralascio il record (data errata): [19/lug/2015:07:37:41 -] [4] Errore: Tralascio il record (data errata): [19/lug/2015:07:38:32 -] [5] Errore: Tralascio il record (data errata): [19/lug/2015:07:38:42 -] [6] Errore: Tralascio il record (data errata): [19/lug/2015:07:39:17 -] [7] Errore: Tralascio il record (data errata): [19/lug/2015:07:39:32 -] [8] Errore: Tralascio il record (data errata): [19/lug/2015:07:40:23 -] [9] Errore: Tralascio il record (data errata): [19/lug/2015:07:40:59 -] [10] Errore: Tralascio il record (data errata): [19/lug/2015:07:41:35 -] [11] ... ... ... Here an excerpt of the parsed log file 09:41:43-root@andromeda:/var/log/squid3$ cat access.log.1 |tail -n 10 1437369923.693275 pegaso.local TCP_MISS/200 2763 GET http://query.yahooapis.com/v1/public/yql? - DIRECT/98.137.200.255 application/json 1437369982.845 240362 luskinnexus TCP_MISS/200 5376 CONNECT history.google.com:443 - DIRECT/173.194.67.138 - 1437369984.652 242757 luskinnexus TCP_MISS/200 1959 CONNECT android.clients.google.com:443 - DIRECT/173.194.116.4 - 1437369984.872 240145 luskinnexus TCP_MISS/200 4649 CONNECT www.googleapis.com:443 - DIRECT/216.58.212.74 - 1437369986.550 240434 luskinnexus TCP_MISS/200 4754 CONNECT www.google.com:443 - DIRECT/173.194.116.19 - 1437369986.634 240519 luskinnexus TCP_MISS/200 5404 CONNECT android.googleapis.com:443 - DIRECT/216.58.212.74 - 1437369986.781 240665 luskinnexus TCP_MISS/200 5153 CONNECT history.google.com:443 - DIRECT/173.194.67.138 - 1437369986.848 240351 luskinnexus TCP_MISS/200 6575 CONNECT www.google.it:443 - DIRECT/173.194.116.23 - 1437370223.766346 pegaso.local TCP_MISS/200 2763 GET http://query.yahooapis.com/v1/public/yql? - DIRECT/98.137.200.255 application/json 1437370523.711316 pegaso.local TCP_MISS/200 2763 GET http://query.yahooapis.com/v1/public/yql? - DIRECT/98.137.200.255 application/json And here an excerpt of a old log (really i see no diffrence at all..) 09:40:00-root@andromeda:/var/log/squid3$ lesspipe access.log.132.gz |tail -n 10 1416118582.790314 192.168.1.2 TCP_MISS/200 2784 GET http://query.yahooapis.com/v1/public/yql? - DIRECT/98.137.200.255 application/json 1416118882.774315 192.168.1.2 TCP_MISS/200 2784 GET http://query.yahooapis.com/v1/public/yql? - DIRECT/98.137.200.255 application/json 1416119050.629183 192.168.1.5 TCP_MISS/200 398 POST http://streamback.ff.avast.com/V1/MD/004A1E6C5208F6A80149CB640ED233353463613336640148A6E4C750/1416119052470 - DIRECT/77.234.45.95 application/octet-stream 1416119050.652235 192.168.1.5 TCP_MISS/200 543 POST http://streamback.ff.avast.com/V1/MD/004C38145208F6A80149C980B82435363961373731340148F8FE21D1/1416119052413 - DIRECT/77.234.45.95 application/octet-stream 1416119182.707317 192.168.1.2 TCP_MISS/200 2784 GET http://query.yahooapis.com/v1/public/yql? - DIRECT/98.137.200.255 application/json 1416119361.898 240990 192.168.1.5 TCP_MISS/200 793 CONNECT android.clients.google.com:443 - DIRECT/173.194.40.8 - 1416119362.732 240470 192.168.1.5 TCP_MISS/200 757 CONNECT www.googleapis.com:443 - DIRECT/173.194.78.95 - 1416119465.789 10548 192.168.1.5 TCP_MISS/200 747 CONNECT mobile-collector.newrelic.com:443 - DIRECT/23.235.43.143 - 1416119482.922433 192.168.1.2 TCP_MISS/200 2784 GET http://query.yahooapis.com/v1/public/yql? - DIRECT/98.137.200.255 application/json 1416119782.776307 192.168.1.2 TCP_MISS/200 2784 GET http://query.yahooapis.com/v1/public/yql? - DIRECT/98.137.200.255 application/json --- -- System Information:
Bug#777169: FTBFS on sparc64: symbol errors
On 06/18/2015 11:29 PM, Matthias Klose wrote: this doesn't look correct. You simply allow the libstdc++ build without these symbols. Please could you address this upstream, and ask to create a baseline symbols file, and then see if the build is supposed to be done without these symbols? Just for documentation purposes, this issue seems to have the same cause as #792204 in the gcc-5 package. The bug report there now shows a possible solution, see [1]. Adrian [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792204#35 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792761: UX issue, handling of endless shutdown loops
Hallo, * Felipe Sateler [Sun, Jul 19 2015, 03:14:11PM]: Control: tags -1 moreinfo Hi Eduard, On 18 July 2015 at 05:24, Eduard Bloch e...@gmx.de wrote: Package: systemd Version: 222-1 Severity: normal Hello systemd maintainers, foreword for systemd hatters: I want this problem to be fixed IN systemd and not by removing systemd. Move along, those are not the droids you are looking for. There is a thing in systemd that bothers me (and has for a while) and it looks like upstream is not moving to fix this. I say BUG and FIX because this is not cosmetics (i.e. a minor user experience issue), the UX might affect how the user acts in order to solve the problem and eventually loose/damage his data because of this problem. What happens is, sometimes systemd gets into an endless loop at the shutdown. Right when the devices are unmounted, in the most vulnerable moment. And then this BS happens, see https://www.unix-ag.uni-kl.de/~bloch/part2.m4v . Obvious questions and events so far (and during/after the video): - what does it wait for? - why don't you let me see any useful detail of that running tasks? - why do I have to wait for 90s and then it tells me: HA HA, now you wait another two minutes. - And when I waited another two minutes, again, HA HA, wait until 4:36... - or maybe until no limit which is blinking again and again? Waiting forever? Are you kidding me? - ok, I was pissed now and pressed Ctrl-Alt-Del, expecting it to do something useful. Now it showed me some Stopped... messages and then immediately three Starting... messages. And huh... Starting? Starting something? I am trying to shutdown, why do you restart some sh.. instead? - Now I have enough of that sh... and use Magic-SysRQ sequence to sync and reboot. I see some room for improvement: - give the user usable information in this case! - AND/OR tell the user how to retrieve more information. Maybe there is some secret shortcut to dump information (I haven't checked the docs yet but I expect upstream to be sane enough to have implemented a such thing) but that infomration needs to be revealed NOW. Having it in some wiki on the internet does not help. - give the user a way to interrupt this. I guess it's either a systemd bug (closed depedency loop?) or one of the outstanding tasks is blocked for some reason (might be a kernel driver issue with devmapper) but in any case, I want to be able to investigate and apply the most harmless fix (kill or ignore the hanging task). Right now I just feel stupid and it's not my fault. So, we have 2 issues: 1. Your system is not shutting down 2. Systemd is not telling you enough to discover what is wrong. I'm afraid 2 is really an upstream issue and not an integration issue. Could you please file that bug upstream? Maybe... I will give it a try tonight. However I am sceptical regarding productive communication with upstream. We can try to help debug number 1, though, and there may be a real integration bug. Please see the shutdown section in the upstream wiki[1]; in particular, starting the debug shell before shutting down The thing is, the issue is not reproducible. It might happen once a month, and then not appear for many months. And you don't want to enable all the debug machinery all the just in case. The thing needed is the minimum control mechanism in place just when the problem occurs. And when it happens for the first time, it's too late to active the debug shell. and switching to it when the shutdown hangs should let you query the journal to find out issues. Note that if you enabled persistent journal logging you can maybe still get the info from the journal: journalctl -b -number of boots since the last hang Says that it cannot find an id. Checked: $ sudo journalctl --list-boots -1 39f59f8ebdd644f39aeb46b67eef9bff Sa 2015-07-18 09:12:05 CEST—Mo 2015-07-20 08 0 39f59f8ebdd644f39aeb46b67eef9bff Mo 2015-07-20 08:39:43 CEST—Mo 2015-07-20 08 No idea what happened to the logs. Regards, Eduard. [1] http://freedesktop.org/wiki/Software/systemd/Debugging/ -- Saludos, Felipe Sateler -- Die letzte Stimme, die man hört, bevor die Welt explodiert, wird die Stimme eines Experten sein, der sagt: 'Das ist technisch unmöglich!' -- Sir Peter Ustinov -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792921: [sparc64] linking against libx264 crashes runtime linker
Package: x264,libc6
Version: x264/2:0.142.2431+gita5831aa-1
Version: libc6/2.19-19
Severity: important
X-Debbugs-Cc: debian-sp...@lists.debian.org
Dear Maintainers,
The x264 package on sparc64 is unusable, because linking against
the libx264 library causes the runtime linker to crash:
$ cat main.c
int main () {
return 0;
}
$ rm ./main
rm: cannot remove './main': No such file or directory
$ cc -g -lx264 main.c -o main
$ ./main; echo $?
138
$ gdb --batch -ex r -ex bt -ex q --args ./main
[tcsetpgrp failed in terminal_inferior: Inappropriate ioctl for device]
[tcsetpgrp failed in terminal_inferior: Inappropriate ioctl for device]
[tcsetpgrp failed in terminal_inferior: Inappropriate ioctl for device]
Program received signal SIGBUS, Bus error.
0xf801cda4 in elf_dynamic_do_Rela (skip_ifunc=optimized out, lazy=0,
nrelative=optimized out, relsize=optimized out, reladdr=optimized out,
map=0xf80100023570) at do-rel.h:111
111 do-rel.h: No such file or directory.
#0 0xf801cda4 in elf_dynamic_do_Rela (skip_ifunc=optimized out,
lazy=0, nrelative=optimized out, relsize=optimized out, reladdr=optimized
out, map=0xf80100023570) at do-rel.h:111
#1 _dl_relocate_object (scope=optimized out, reloc_mode=optimized out,
consider_profiling=optimized out, consider_profiling@entry=0) at
dl-reloc.c:264
#2 0xf8013f2c in dl_main (phdr=optimized out, phnum=optimized out,
user_entry=optimized out, auxv=optimized out) at rtld.c:2205
#3 0xf80100018be4 in _dl_sysdep_start
(start_argptr=start_argptr@entry=0x7fefdc0, dl_main=0xf8011e00
dl_main) at ../elf/dl-sysdep.c:249
#4 0xf8015630 in _dl_start_final (arg=0x7fefdc0) at rtld.c:331
#5 _dl_start (arg=0x7fefdc0) at rtld.c:557
#6 0xf80116ec in _start () from /lib64/ld-linux.so.2
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
I'm not sure what the cause for this crash is, so I'm filing this bug
against both packages. Please reassign as appropriate.
Best regards,
Andreas
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792914: Package: xarchiver
Control: severity -1 important Control: tags -1 moreinfo On Sun, 19. Jul 21:51 Richard Jasmin frazzledj...@gmail.com wrote: Package: xarchiver Version: 1:0.5.4-1 Severity: Grave Xarchiver has a SERIOUS data LOSS issue.One can attempt to zip up some home folders from /home.The problem when doing so is that data gets corrupted on add. This does not happen when using zip from the commandline.When attempting to unzip these archives, unzip complains that there is invalid compressed data to inflate and skips over the bad crc marked files.This has resulted in about less than 25GB of a 300GB archive to be recovered on restore.I have lost my backup set due to this. Hello, Xarchiver is merely a frontend for various compression formats and not much has changed in regard to zip compression since squeeze. Please try to describe how it is possible to reproduce your issue by attaching a simple test case to this bug report. Thanks Markus signature.asc Description: Digital signature
Bug#674671: [icedove] Subject and message use different languages with spell checking
This issue is not gone. Steps to reproduce: 1. Create a new message. 2. Click on subject line text box. 3. Open context menu and select some spell checker language. 4. Click on message text area. 5. Open context menu and select a different spell checker language. 6. Click on subject line again. Now, both the subject and the message text are checked using the language selected in step 3, not step 5. This is the problem. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792920: uqm: FTBFS due to missing -lm
Source: uqm Version: 0.6.2.dfsg-9 Severity: serious Tags: jessie sid stretch Justification: fails to build from source (but built successfully in the past) Hi, starting with jessie, uqm FTBFS due to missing -lm: CC obj/release/src/sc2code/netplay/proto/ready.c.o CC obj/release/src/sc2code/netplay/proto/reset.c.o CC obj/release/src/getopt/getopt.c.o CC obj/release/src/getopt/getopt1.c.o LINK uqm /usr/bin/ld: obj/release/src/sc2code/planets/plangen.c.o: undefined reference to symbol 'exp@@GLIBC_2.2.5' //lib/x86_64-linux-gnu/libm.so.6: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status Makefile.build:84: recipe for target 'uqm' failed make[1]: *** [uqm] Error 1 make[1]: Leaving directory '/tmp/buildd/uqm-0.6.2.dfsg/sc2' debian/rules:13: recipe for target 'build-stamp' failed make: *** [build-stamp] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 Please enable verbose build, too. I.e. the individual command lines need to be shown s.t. it is easier to analyze such bugs from the buildlog and run automated checks like blhc. Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792902: laptop-mode-tools: Naive install results in USB keyboard/mouse problems
Control: severity -1 wishlist Control: tag -1 pending On Monday 20 July 2015 04:00 AM, Joel Roth wrote: To help others avoid the lengthy period of unresolved difficulties, doubts about hardware integrity, and ergonomic awkwardness I experienced, I suggest that laptop-mode-tools ought to go further to avoid the loss of mouse/keyboard functionality, and/or to warn potentially naive installers of this package that possible breakage could occur and user study and customization may be necessary to avoid the issues. The catch is that not every driver/device is a broken one. But yes, documenting it should be done. I just checked and realized that we do not ship a README.Debian file. Perhaps that should be a good start. Perhaps the installer script could display the lsusb output and prompt the user to select the keyboard and mouse IDs from the lsusb output and configure the BLACKLIST entries accordingly. That is debhelper specific. And not all users may see that. Also just showing the device ID may not help. Will the user be able to build the relation on which ID belongs to which specific device? I recently had to blacklist one ill behaving device, and it took me some looking around to figure it out. Perhaps driver type designations can or could allow users to blacklist all keyboard and mouse devices by default. This is already there. Just not enabled by default, for the reasons that I explained above. Let's start with README.Debian and see how it goes. I've added the necessary content. Will be part of next upload. rrs@learner:~/devel/Laptop-Mode-Tools/laptop-mode-tools (master)$ cat debian/README.Debian Some common problems and fixing them My USB Mouse / Keyboard stops working after seconds of inactivity - Many devices advertise power savings but misbehave when power savings is triggered. Laptop Mode Tools, by default, enabled power savings for all devices. If you have devices, that mis-behave when running on battery, you can blacklist them. For details on blacklisting the device, please refer to the configuration details in /etc/laptop-mode/conf.d/runtime-pm.conf -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System signature.asc Description: OpenPGP digital signature
Bug#792913: Package: linux-image-4.0.0-2-amd64
Same here in PowerPC G5 Quad Core with ATI Radeon HD4670 and NVidia 6600. The first is not loading Xorg, the latter is not going to work at all. More Dmesg output and Xorg logs ASAP. On Mon, Jul 20, 2015 at 4:30 AM, Richard Jasmin frazzledj...@gmail.com wrote: Package: linux-image-4.0.0-2-amd64 Version: 4.0.8-1 Severity: Major ATI opensource drivers are broken once more and cause X11 to fail to start when stretch is installed. Hardware used is a A8-4500M QUAD core AMD Radeon APU. This doesnt happen in Jessie. Flgrx is not installed during this time. Installing said package may fix the issue but was untested because wifi was not configured. Suggest porting Fedora 22's latest ATI drivers. They are open source and work without issue.They have a version list available online so you can see what version of packages you are using to compare it to fedora's. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1437359444.30318.11.ca...@gmail.com -- Ciao e buona giornata. GP! In mezzo al campo stai proprio schifoso! Coach M.Russo
Bug#791823: [Reproducible-builds] Bug#791823: debhelper: set SOURCE_DATE_EPOCH env var for reproducible builds
On 12/07/15 12:03, Jérémy Bobbio wrote: Hi! Dhole: Also, in order to help reproducible builds, a fixed timezone is exported (TZ=UTC). I am not convinced this change is a good idea. While reviewing new uploads to the Debian archive, I have at least spotted these lines in exim4/4.86~RC4-1 changelog [1]: * unexport/undefine TZ in debian/rules for reproducible build. It would be used as default value for TIMEZONE_DEFAULT. The `TZ` environment variable is not usually set in a build environment. It is a reproducibility problem if a package produce different binaries when it is, but that's all. I am afraid that some packages, like exim4, would silently start behaving differently if we set `TZ` in debhelper. If we don't set the variable in debhelper, we can use the reproducibility tests to spot packages who are building differently depending on the timezone or the value of TZ and propose fixes to maintainers. This enables them to review their impact. It is indeed more work, but it's less likely to unknowingly introduce any weird behavior. [1]: https://tracker.debian.org/news/694090 I also had some reservations about setting TZ in this way, but wasn't quite sure how to express it. But here's a more general, abstract version of the scenario Lunar pointed out. - Imagine that upstream thinks it's reasonable to e.g. generate certain locale data based on the TZ variable at build time. - Setting TZ=UTC would make the build appear reproducible, and the package maintainer may not even realise that there's something missing, especially if this locales thing is buried deep in the build scripts. - The correct solution would be for upstream to generate such data for all TZs. For sure, setting TZ=UTC would not interfere with this fix, but it makes such issues harder to detect. I suggest we drop this particular aspect from this patch and just focus on SOURCE_DATE_EPOCH instead. X -- GPG: 4096R/1318EFAC5FBBDBCE git://github.com/infinity0/pubkeys.git signature.asc Description: OpenPGP digital signature
Bug#792915: Logwatch fails to parse log statements
Hi, --archives is the default, which solves most of the problems you describe. The only known problem that remains is support for alternative compression methods (gz and bzip2 are supported, but xz is not supported). If you report bugs, please use reportbug, as the upstream version only makes it hard to know whether we talk about the same package version. Bye Willi Am 2015-07-20 um 05:29 schrieb Jane D: Package: logwatch Version: 7.4.1 SYMPTOM Log statements for the first hours of yesterday are ignored and not processed by logwatch. CAUSE The configuration for syslog uses files /var/log/syslog and /var/log/syslog.1. Because log rotation does not occur exactly at midnight, the first portion of yesterday's log statements are in syslog.2, and logwatch does not process this file. GET-AROUND FOR SYSLOG ONLY sudo mkdir --parents /etc/logwatch/conf/logfiles; sudo echo LogFile = syslog.2 | sudo tee /etc/logwatch/conf/logfiles/syslog.conf /dev/null BIGGER PROBLEM 1 The way of locating logs does not take in account the logrotate rotate directive or the period of which logs are rotated. logwatch would need to scan every log until a too old modification date is found. Since logs can be rotated when reaching a certain size, which can be hundreds of times daily. Therefore, every index number up to logrotate's rotate setting must be scanned. Say a log has rotate 100 and is rotated every hour dues ot its size or configuration. Logwatch would then need to examine file indexes up to 48 (2 x 24 hours), ie. put 48 LogFile= … statements in the log configuration file. The logwatch architecture is lacking. BIGGER PROBLEM 2 The compressed extension is assumed to be .gz. Today, it is more likely to be .xz but can be anything, really. Logwatch should examine any file by stemming the original log filename, eg. look for syslog* and test the result against common file compress methods. BIGGER PROBLEM 3 If logrotate delaycompress is used, syslog.2 will be compressed and logwatch will not look in it. ie. every run would need the --archives option, and this is not the default. DATA When are logs rotated? maybe 6:25 am grep /etc/cron.daily /etc/crontab 25 6 * * * root test -x /usr/sbin/anacron || ( cd / run-parts --report /etc/cron.daily ) Add a service that echoes all processed syslog lines sudo mkdir --parents /etc/logwatch/conf/services /etc/logwatch/scripts/services; echo -e Title = \All syslog\\nLogFile = syslog | sudo tee /etc/logwatch/conf/services/allsyslog.conf /dev/null; Y=!; echo -e #$Y/bin/bash -eu\ncat | sudo tee /etc/logwatch/scripts/services/allsyslog /dev/null logwatch --service allsyslog | less delete the service sudo rm /etc/logwatch/conf/services/allsyslog.conf /etc/logwatch/scripts/services/allsyslog -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#791929: [t...@hp.com: Please support ARM64 (No rule to make target 'aarch64')]
Hi Vince, I am forwarding this bug to you. Please preserve the CC field when responding. -- Dariusz Dwornikowski, Institute of Computing Science, Poznań University of Technology www.cs.put.poznan.pl/ddwornikowski/ room 1.6.2 BTiCW | tel. +48 61 665 23 71 ---BeginMessage--- Package: linuxlogo Version: 5.11-7 Severity: wishlist User: debian-...@lists.debian.org Usertags: arm64 port This package fails to build on arm64, but a quick looks suggests this package might be useful on arm64. Do you know if upstream or someone else is working on arm64 support (aarch64) already? If not, I might be able to get somone to work on this. sbuild (Debian sbuild) 0.64.1 (13 Oct 2013) on m400-c4n1.hlinux.usa.hp.com ... make[3]: Entering directory '/«PKGBUILDDIR»/libsysinfo-0.2.2/Linux' make[3]: *** No rule to make target 'aarch64', needed by 'cpuinfo.o'. Stop. make[3]: Leaving directory '/«PKGBUILDDIR»/libsysinfo-0.2.2/Linux' -- Martin Michlmayr Linux for HP Helion, Hewlett-Packard ---End Message--- signature.asc Description: Digital signature
Bug#792473: cups: After updating to 2.0.3-6 in testing cups interface no longer works
Hi, we also confirm the bug after updating to 2.0.3-6 and the temporary workaround manually running cupsd. We have some clients running Testing and comparing the cups* running processes we found that every client has /usr/sbin/cups-browsed /usr/sbin/cupsd -l /usr/lib/cups/notifier/dbus dbus:// but only the workarounded manually running cupsd has cupsd -C /etc/cups/cupsd.conf -s /etc/cups/cups-files.conf so discovering the network printers ... Regards! Guido On Sun, 19 Jul 2015 13:01:52 +0200 Didier 'OdyX' Raboud o...@debian.org wrote: Le dimanche, 19 juillet 2015, 11.54:02 Brad Rogers a écrit : Brian, for comparison, this is what I get; (â¦) This is after running cupsd as root. Sorry to say it so bluntly, but running cups as root is the wrong solution: if the launch by the init system doesn't work, it needs to be fixed; having to manually run cupsd by hand can only be a temporary workaround. Cheers, OdyX -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#791929: Please support ARM64 (No rule to make target 'aarch64')
This package fails to build on arm64, but a quick looks suggests this package might be useful on arm64. Do you know if upstream or someone else is working on arm64 support (aarch64) already? If not, I might be able to get somone to work on this. sbuild (Debian sbuild) 0.64.1 (13 Oct 2013) on m400-c4n1.hlinux.usa.hp.com ... make[3]: Entering directory '/«PKGBUILDDIR»/libsysinfo-0.2.2/Linux' make[3]: *** No rule to make target 'aarch64', needed by 'cpuinfo.o'. Stop. make[3]: Leaving directory '/«PKGBUILDDIR»/libsysinfo-0.2.2/Linux' -- Thank You for reporting this, I will forward the bug to upstream but afaik their development is kept in github [1] so you can push your changes there. I do not think upstream is working on aarch64, linuxlogo is pretty dormant (not dead though). [1] https://github.com/deater/linux_logo -- Dariusz Dwornikowski, Institute of Computing Science, Poznań University of Technology www.cs.put.poznan.pl/ddwornikowski/ room 1.6.2 BTiCW | tel. +48 61 665 23 71 signature.asc Description: Digital signature
Bug#776473: ITP: luacheck -- static analyzer and a linter for the Lua language
0.11.0 released initial? work http://blog.torreviejawireless.org/debian/lua-check/ signature.asc Description: OpenPGP digital signature
Bug#792936: cpl-plugin-hawki: please make the build reproducible
Source: cpl-plugin-hawki Version: 1.8.18+dfsg-3 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: randomness X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, While working on the reproducible builds effort [1], we have noticed that cpl-plugin-hawki could not be built reproducibly. The attached patch removes randomness from the build system. Once applied, cpl-plugin-hawki can be built reproducibly in our reproducible toolchain. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff --git a/debian/create_sphinx.py b/debian/create_sphinx.py index cf72d4e..bb0f300 100644 --- a/debian/create_sphinx.py +++ b/debian/create_sphinx.py @@ -146,7 +146,7 @@ index = [ oca.find(recipe.__name__) for recipe in recipes_oca ] recipes_oca = [r for (i, r) in sorted(zip(index, recipes_oca))] recipes_x = [recipe for recipe in recipes if not recipe.__name__ in oca] -recipes_x.sort() +recipes_x.sort(lambda x: x.__name__) def par(recipe, template, delimiter = , count = None): return delimiter.join(template.format(
Bug#792935: cpl-plugin-giraf: please make the build reproducible
Source: cpl-plugin-giraf Version: 2.14+dfsg-3 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: randomness X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, While working on the reproducible builds effort [1], we have noticed that cpl-plugin-giraf could not be built reproducibly. The attached patch removes randomness from the build system. Once applied, cpl-plugin-giraf can be built reproducibly in our reproducible toolchain. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff --git a/debian/create_sphinx.py b/debian/create_sphinx.py index 3c283da..0336111 100644 --- a/debian/create_sphinx.py +++ b/debian/create_sphinx.py @@ -146,7 +146,7 @@ index = [ oca.find(recipe.__name__) for recipe in recipes_oca ] recipes_oca = [r for (i, r) in sorted(zip(index, recipes_oca))] recipes_x = [recipe for recipe in recipes if not recipe.__name__ in oca] -recipes_x.sort() +recipes_x.sort(lambda x: x.__name__) def par(recipe, template, delimiter = , count = None): return delimiter.join(template.format(
Bug#792934: libebook-tools-perl: install_driver(SQLite) failed: Can't locate DBD/SQLite.pm in @INC
Package: libebook-tools-perl Version: 0.5.4-1 Severity: serious Justification: Policy §3.5 $ perl -e 'use EBook::Tools' install_driver(SQLite) failed: Can't locate DBD/SQLite.pm in @INC (you may need to install the DBD::SQLite module) (@INC contains: /etc/perl /usr/local/lib/i386-linux-gnu/perl/5.20.2 /usr/local/share/perl/5.20.2 /usr/lib/i386-linux-gnu/perl5/5.20 /usr/share/perl5 /usr/lib/i386-linux-gnu/perl/5.20 /usr/share/perl/5.20 /usr/local/lib/site_perl .) at (eval 30) line 3. Perhaps the DBD::SQLite perl module hasn't been fully installed, or perhaps the capitalisation of 'SQLite' isn't right. Available drivers: DBM, ExampleP, File, Gofer, Proxy, Sponge. at /usr/share/perl5/EBook/Tools/BISG.pm line 326. Compilation failed in require at -e line 1. BEGIN failed--compilation aborted at -e line 1. If you install libdbd-sqlite3-perl, the error goes away. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 4.0.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages libebook-tools-perl depends on: ii libarchive-zip-perl1.48-1 ii libbit-vector-perl 7.4-1 ii libconfig-inifiles-perl2.83-3 ii libdate-manip-perl 6.50-1 ii libdbi-perl1.633-1 ii libencode-detect-perl 1.01-4 ii libfile-mimeinfo-perl 0.27-1 ii libfile-slurp-perl .19-4 ii libfile-which-perl 1.18-1 ii libhtml-parser-perl3.71-2 ii libimage-size-perl 3.300-1 ii liblingua-en-nameparse-perl1.32-1 ii liblist-moreutils-perl 0.413-1 ii libmojolicious-perl5.54+dfsg-1 ii libossp-uuid-perl 1.6.2-1.5+b1 ii libpalm-perl 1:1.013-1 ii libstring-crc32-perl 1.5-1+b1 ii libtie-ixhash-perl 1.23-2 ii libwww-perl6.13-1 ii libxml-twig-perl 1:3.48-1 ii perl 5.20.2-6 ii perl-modules [libtime-local-perl] 5.20.2-6 ii txt2html 2.51-1 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792942: cpl-plugin-visir: please make the build reproducible
Source: cpl-plugin-visir Version: 3.5.1+dfsg-2 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: randomness X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, While working on the reproducible builds effort [1], we have noticed that cpl-plugin-visir could not be built reproducibly. The attached patch removes randomness from the build system. Once applied, cpl-plugin-visir can be built reproducibly in our reproducible toolchain. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff --git a/debian/create_sphinx.py b/debian/create_sphinx.py index a694f8a..f132ea8 100644 --- a/debian/create_sphinx.py +++ b/debian/create_sphinx.py @@ -146,7 +146,7 @@ index = [ oca.find(recipe.__name__) for recipe in recipes_oca ] recipes_oca = [r for (i, r) in sorted(zip(index, recipes_oca))] recipes_x = [recipe for recipe in recipes if not recipe.__name__ in oca] -recipes_x.sort() +recipes_x.sort(lambda x: x.__name__) def par(recipe, template, delimiter = , count = None): return delimiter.join(template.format(
Bug#792938: cpl-plugin-muse: please make the build reproducible
Source: cpl-plugin-muse Version: 1.0.4+dfsg-3 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: randomness X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, While working on the reproducible builds effort [1], we have noticed that cpl-plugin-muse could not be built reproducibly. The attached patch removes randomness from the build system. Once applied, cpl-plugin-muse can be built reproducibly in our reproducible toolchain. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff --git a/debian/create_sphinx.py b/debian/create_sphinx.py index 03a56b0..a94cf81 100644 --- a/debian/create_sphinx.py +++ b/debian/create_sphinx.py @@ -150,7 +150,7 @@ index = [ oca.find(recipe.__name__) for recipe in recipes_oca ] recipes_oca = [r for (i, r) in sorted(zip(index, recipes_oca))] recipes_x = [recipe for recipe in recipes if not recipe.__name__ in oca] -recipes_x.sort() +recipes_x.sort(lambda x: x.__name__) def par(recipe, template, delimiter = , count = None): return delimiter.join(template.format(
Bug#792473: cups: After updating to 2.0.3-6 in testing cups interface no longer works
On Mon, 20 Jul 2015 11:04:21 +0200
MAG4 Piemonte m...@aruba.it wrote:
Hello,
We have some clients running Testing and comparing the cups* running
processes we found that every client has
/usr/sbin/cups-browsed
That isn't installed here.
{time passes}
After installing the package cups-browsed and rebooting, my printer is
now detected. I no longer have to run cupsd manually.
--
Regards _
/ ) The blindingly obvious is
/ _)radnever immediately apparent
Just stop and take a second
U Ur Hand - P!nk
pgptvNiuf19YJ.pgp
Description: OpenPGP digital signature
Bug#792937: cpl-plugin-kmos: please make the build reproducible
Source: cpl-plugin-kmos Version: 1.3.12+dfsg-3 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: randomness X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, While working on the reproducible builds effort [1], we have noticed that cpl-plugin-kmos could not be built reproducibly. The attached patch removes randomness from the build system. Once applied, cpl-plugin-kmos can be built reproducibly in our reproducible toolchain. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff --git a/debian/create_sphinx.py b/debian/create_sphinx.py index 9107b16..e7bf499 100644 --- a/debian/create_sphinx.py +++ b/debian/create_sphinx.py @@ -146,7 +146,7 @@ index = [ oca.find(recipe.__name__) for recipe in recipes_oca ] recipes_oca = [r for (i, r) in sorted(zip(index, recipes_oca))] recipes_x = [recipe for recipe in recipes if not recipe.__name__ in oca] -recipes_x.sort() +recipes_x.sort(lambda x: x.__name__) def par(recipe, template, delimiter = , count = None): return delimiter.join(template.format(
Bug#792939: cpl-plugin-sinfo: please make the build reproducible
Source: cpl-plugin-sinfo Version: 2.6.0+dfsg-3 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: randomness X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, While working on the reproducible builds effort [1], we have noticed that cpl-plugin-sinfo could not be built reproducibly. The attached patch removes randomness from the build system. Once applied, cpl-plugin-sinfo can be built reproducibly in our reproducible toolchain. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff --git a/debian/create_sphinx.py b/debian/create_sphinx.py index 170b470..96d7a04 100644 --- a/debian/create_sphinx.py +++ b/debian/create_sphinx.py @@ -146,7 +146,7 @@ index = [ oca.find(recipe.__name__) for recipe in recipes_oca ] recipes_oca = [r for (i, r) in sorted(zip(index, recipes_oca))] recipes_x = [recipe for recipe in recipes if not recipe.__name__ in oca] -recipes_x.sort() +recipes_x.sort(lambda x: x.__name__) def par(recipe, template, delimiter = , count = None): return delimiter.join(template.format(
Bug#787473: systemd: Segfault while adding a new job
Ths system was running for two weeks now with no issues. I almost gathered some hope, that it's finally stable now. :( Next crash.. This time sshd crashed in the first place and the stack of the coredump seems broken. Both very strange, that never happened before. As usual, all other services remained working until i rebooted. Jul 19 22:06:22 Storage-Blue systemd[1]: systemd-journald.service: Got notification message from PID 224 (WATCHDOG=1) Jul 19 22:07:01 Storage-Blue systemd[1]: systemd-journald.service: Got notification message from PID 224 (WATCHDOG=1) Jul 19 22:07:01 Storage-Blue systemd[1]: Received SIGCHLD from PID 941 (sshd). Jul 19 22:07:01 Storage-Blue systemd[1]: Child 941 (sshd) died (code=killed, status=11/SEGV) Jul 19 22:07:01 Storage-Blue systemd[1]: ssh.service: Child 941 belongs to ssh.service Jul 19 22:07:01 Storage-Blue systemd[1]: ssh.service: Main process exited, code=killed, status=11/SEGV Jul 19 22:07:01 Storage-Blue systemd[1]: ssh.service: Changed running - failed Jul 19 22:07:01 Storage-Blue systemd[1]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=5342 reply_cookie=0 error=n/a Jul 19 22:07:01 Storage-Blue systemd[1]: ssh.service: Unit entered failed state. Jul 19 22:07:01 Storage-Blue systemd[1]: ssh.service: Failed with result 'signal'. Jul 19 22:07:01 Storage-Blue systemd[1]: ssh.service: Changed failed - auto-restart Jul 19 22:07:01 Storage-Blue systemd[1]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=5343 reply_cookie=0 error=n/a Jul 19 22:07:01 Storage-Blue systemd[1]: ssh.service: cgroup is empty Jul 19 22:07:01 Storage-Blue systemd[1]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1/unit/ssh_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=5344 reply_cookie=0 error=n/a Jul 19 22:07:01 Storage-Blue systemd[1]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1/unit/ssh_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=5345 reply_cookie=0 error=n/a Jul 19 22:07:01 Storage-Blue systemd[1]: systemd-logind.service: Got notification message from PID 948 (WATCHDOG=1) Jul 19 22:07:01 Storage-Blue systemd[1]: Failed to determine peer security context: Protocol not available Jul 19 22:07:01 Storage-Blue systemd[1]: Accepted new private connection. Jul 19 22:07:01 Storage-Blue systemd[1]: Got message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1/agent interface=org.freedesktop.systemd1.Agent member=Released cookie=1 reply_cookie=0 error=n/a Jul 19 22:07:01 Storage-Blue systemd[1]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1/agent interface=org.freedesktop.systemd1.Agent member=Released cookie=1 reply_cookie=0 error=n/a Jul 19 22:07:01 Storage-Blue systemd[1]: Got disconnect on private connection. Jul 19 22:07:01 Storage-Blue systemd[1]: ssh.service: Service hold-off time over, scheduling restart. Jul 19 22:07:01 Storage-Blue systemd[1]: ssh.service: Trying to enqueue job ssh.service/restart/fail Jul 19 22:07:01 Storage-Blue systemd[1]: Caught SEGV, dumped core as pid 21119. Jul 19 22:07:01 Storage-Blue systemd[1]: Freezing execution. $ ls -la /core -rw--- 1 root root 18395136 Jul 19 22:07 /core $ sudo gdb /lib/systemd/systemd /core GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1 [...] Reading symbols from /lib/systemd/systemd...Reading symbols from /usr/lib/debug/.build-id/f7/4b60d31f6367ce58af04291f69c2f46d6a67a2.debug...done. done. [New LWP 21119] Core was generated by `/sbin/init'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0xb6b45d2c in ?? () (gdb) bt #0 0xb6b45d2c in ?? () #1 0xb6eac740 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) $ dpkg -l | grep openssh-server ii openssh-server 1:6.7p1-5armel secure shell (SSH) server, for secure access from remote machines $ dpkg -l | grep systemd ii libsystemd0:armel 221-1+deb9u2 armel systemd utility library ii systemd221-1+deb9u2 armel system and service manager ii systemd-dbg221-1+deb9u2 armel system and service manager (debug symbols) ii systemd-sysv 221-1armel system and service manager - SysV links signature.asc Description: OpenPGP digital signature
Bug#792941: cpl-plugin-vimos: please make the build reproducible
Source: cpl-plugin-vimos Version: 2.9.15+dfsg-4 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: randomness X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, While working on the reproducible builds effort [1], we have noticed that cpl-plugin-vimos could not be built reproducibly. The attached patch removes randomness from the build system. Once applied, cpl-plugin-vimos can be built reproducibly in our reproducible toolchain. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff --git a/debian/create_sphinx.py b/debian/create_sphinx.py index 3a9492a..fd87529 100644 --- a/debian/create_sphinx.py +++ b/debian/create_sphinx.py @@ -145,7 +145,7 @@ recipes_oca = [name for name in recipes if name in oca] index = [ oca.find(name) for name in recipes_oca ] recipes_oca = [r for (i, r) in sorted(zip(index, recipes_oca))] recipes_x = [name for name in recipes if not name in oca] -recipes_x.sort() +recipes_x.sort(lambda x: x.__name__) def par(recipe, template, delimiter = , count = None): return delimiter.join(template.format(
Bug#792824: libmagics++-dev: arch-dependent files in Multi-Arch: same package
More ing timestamps! Thanks, will remove. Alastair On 18/07/2015 21:54, Jakub Wilk wrote: Package: libmagics++-dev Version: 2.24.7-1 Severity: important User: multiarch-de...@lists.alioth.debian.org Usertags: multiarch libmagics++-dev is marked as Multi-Arch: same, but the following files are architecture-dependent: /usr/include/magics/BaseDriverAttributes.h /usr/include/magics/BinningObjectAttributes.h /usr/include/magics/ContinuousLegendMethodAttributes.h /usr/include/magics/DateGribLoopStepAttributes.h /usr/include/magics/FixedTableModeAttributes.h /usr/include/magics/FortranRootSceneNodeAttributes.h /usr/include/magics/GeoRectangularProjectionAttributes.h /usr/include/magics/GribDecoderAttributes.h /usr/include/magics/GribLoopAttributes.h /usr/include/magics/HistogramLegendMethodAttributes.h /usr/include/magics/ImagePlottingAttributes.h /usr/include/magics/LegendVisitorAttributes.h /usr/include/magics/LookupTableModeAttributes.h /usr/include/magics/OutputHandlerAttributes.h /usr/include/magics/QtDriverAttributes.h /usr/include/magics/WrepRootNodeAttributes.h /usr/include/magics/XmlBasicNodeAttributes.h /usr/include/magics/XmlRootNodeAttributes.h An example diff between i386 and amd64 is attached. -- Alastair McKinstry, alast...@sceal.ie, mckins...@debian.org, https://diaspora.sceal.ie/u/amckinstry Misentropy: doubting that the Universe is becoming more disordered. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792930: linux-image-4.0.0-2-586: [Geode LX] fails to load via GRUB 2
Package: src:linux Version: 4.0.8-1 Severity: important Kernel 4 completely fails to launch on this Geode LX host. GRUB displays the usual messages about loading the kernel and the initrd image, then the cursor freezes. No further message is displayed. Kernel 3.2 (oldstable) and 3.16 (stable) boot normaly on the exact same host. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information not available ** Network interface configuration: auto lo iface lo inet loopback ** PCI devices: 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] CS5536 [Geode companion] Host Bridge [1022:2080] (rev 31) Subsystem: FIRST INTERNATIONAL Computer Inc Device [1509:801b] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 248, Cache Line Size: 32 bytes Region 0: I/O ports at ac1c [size=4] Region 1: I/O ports at 9e00 [size=8] 00:01.1 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD] Geode LX Video [1022:2081] (prog-if 00 [VGA controller]) Subsystem: FIRST INTERNATIONAL Computer Inc Device [1509:801b] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 10 Region 0: Memory at d000 (32-bit, non-prefetchable) [size=256M] Region 1: Memory at efff (32-bit, non-prefetchable) [size=16K] Region 2: Memory at effec000 (32-bit, non-prefetchable) [size=16K] Region 3: Memory at effe8000 (32-bit, non-prefetchable) [size=16K] Region 4: Memory at efff8000 (32-bit, non-prefetchable) [size=16K] Expansion ROM at unassigned [disabled] 00:01.2 Entertainment encryption device [1010]: Advanced Micro Devices, Inc. [AMD] Geode LX AES Security Block [1022:2082] Subsystem: FIRST INTERNATIONAL Computer Inc Device [1509:801b] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 10 Region 0: Memory at efff4000 (32-bit, non-prefetchable) [size=16K] Kernel driver in use: Geode LX AES 00:0d.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter [10ec:8139] (rev 10) Subsystem: FIRST INTERNATIONAL Computer Inc Device [1509:801b] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR+ INTx- Latency: 32 (8000ns min, 16000ns max) Interrupt: pin A routed to IRQ 11 Region 0: I/O ports at fc00 [size=256] Region 1: Memory at e000 (32-bit, non-prefetchable) [size=256] Capabilities: access denied Kernel driver in use: 8139too 00:0f.0 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] CS5536 [Geode companion] ISA [1022:2090] (rev 03) Subsystem: FIRST INTERNATIONAL Computer Inc Device [1509:801b] Control: I/O+ Mem- BusMaster- SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Region 0: I/O ports at 6000 [size=8] Region 1: I/O ports at 6100 [size=256] Region 2: I/O ports at 6200 [size=64] Region 3: I/O ports at 1000 [size=32] Region 4: I/O ports at 9d00 [size=128] Region 5: I/O ports at 9c00 [size=64] 00:0f.2 IDE interface [0101]: Advanced Micro Devices, Inc. [AMD] CS5536 [Geode companion] IDE [1022:209a] (rev 01) (prog-if 80 [Master]) Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 248, Cache Line Size: 32 bytes Region 0: [virtual] Memory at 01f0 (32-bit, non-prefetchable) [size=8] Region 1: [virtual] Memory at 03f0 (type 3, non-prefetchable) Region 2: [virtual] Memory at 0170 (32-bit, non-prefetchable) [size=8] Region 3: [virtual] Memory at 0370 (type 3, non-prefetchable) Region 4: I/O ports at ff00 [size=16] Kernel driver in use: pata_cs5536 00:0f.3 Multimedia audio controller [0401]: Advanced Micro Devices, Inc. [AMD] CS5536 [Geode companion] Audio [1022:2093] (rev 01) Subsystem: FIRST
Bug#792931: ITP: libsigscan -- library for binary signature scanning
Control: block 792350 by -1 Package: wnpp Owner: Hilko Bengen ben...@debian.org Severity: wishlist * Package name: libsigscan Version : 20150714 Upstream Author : Joachim Metz * URL or Web page : https://github.com/libyal/libsigscan * License : LGPL-3.0+ Description : library for binary signature scanning libsigscan is a dependency for dfvfs which in turn is a dependency for Plaso. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792932: cpl-plugin-amber: please make the build reproducible
Source: cpl-plugin-amber Version: 4.3.3+dfsg-3 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: randomness X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, While working on the reproducible builds effort [1], we have noticed that cpl-plugin-amber could not be built reproducibly. The attached patch removes randomness from the build system. Once applied, cpl-plugin-amber can be built reproducibly in our reproducible toolchain. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff --git a/debian/create_sphinx.py b/debian/create_sphinx.py index d9ece20..65bb6ff 100644 --- a/debian/create_sphinx.py +++ b/debian/create_sphinx.py @@ -146,7 +146,7 @@ index = [ oca.find(recipe.__name__) for recipe in recipes_oca ] recipes_oca = [r for (i, r) in sorted(zip(index, recipes_oca))] recipes_x = [recipe for recipe in recipes if not recipe.__name__ in oca] -recipes_x.sort() +recipes_x.sort(lambda x: x.__name__) def par(recipe, template, delimiter = , count = None): return delimiter.join(template.format(
Bug#792518: Manual page for the docker-compose executable is missing
forwarded 792518 https://github.com/docker/compose/issues/1727 thanks Awesome job! Thanks Dariusz! I just opened an upstream bug report in order to get it included upstream. Regards, -- Carl Chenet Blog : https://carlchenet.com https://identi.ca/carlchenet | https://twitter.com/carl_chenet FOSS contributions : https://www.ohloh.net/accounts/chaica -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792943: argus-client: please make the build reproducible
Source: argus-client Version: 2.0.6.fixes.1-3 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps Hi! While working on the “reproducible builds” effort [1], we have noticed that argus-client could not be built reproducibly. The attached patch sets the mtimes of all files which are modified during the built to the date of the last changelog entry in order to produce files with reproducible metadata. Cheers, akira [1]: https://wiki.debian.org/ReproducibleBuilds diff -u argus-client-2.0.6.fixes.1/debian/rules argus-client-2.0.6.fixes.1/debian/rules --- argus-client-2.0.6.fixes.1/debian/rules +++ argus-client-2.0.6.fixes.1/debian/rules @@ -16,6 +16,8 @@ OLDSUB=./config/config.sub OLDGUESS=./config/config.guess +BUILD_DATE := $(shell dpkg-parsechangelog --show-field Date) + ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS))) CFLAGS += -O0 else @@ -185,6 +187,8 @@ dpkg-shlibdeps $(tmp)/$(bindir)/* dpkg-gencontrol -ips -p$(PACKAGE) -P$(tmp) + find $(tmp) -newermt '$(BUILD_DATE)' -print0 | \ + xargs -0r touch --no-dereference --date='$(BUILD_DATE)' dpkg --build $(tmp) .. diff -u argus-client-2.0.6.fixes.1/debian/changelog argus-client-2.0.6.fixes.1/debian/changelog --- argus-client-2.0.6.fixes.1/debian/changelog +++ argus-client-2.0.6.fixes.1/debian/changelog @@ -1,3 +1,10 @@ +argus-client (2.0.6.fixes.1-3.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix mtimes before building binary packages to produce reproducible output + + -- akira marival...@gmail.com Wed, 15 Jul 2015 23:26:49 +0200 + argus-client (2.0.6.fixes.1-3) unstable; urgency=low * Applied patch from Xavier Renaut to make ragraph generate PNG graphs
Bug#792933: cpl-plugin-fors: please make the build reproducible
Source: cpl-plugin-fors Version: 5.0.11+dfsg-3 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: randomness X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, While working on the reproducible builds effort [1], we have noticed that cpl-plugin-fors could not be built reproducibly. The attached patch removes randomness from the build system. Once applied, cpl-plugin-fors can be built reproducibly in our reproducible toolchain. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff --git a/debian/create_sphinx.py b/debian/create_sphinx.py index b9f9096..9272342 100644 --- a/debian/create_sphinx.py +++ b/debian/create_sphinx.py @@ -146,7 +146,7 @@ index = [ oca.find(recipe.__name__) for recipe in recipes_oca ] recipes_oca = [r for (i, r) in sorted(zip(index, recipes_oca))] recipes_x = [recipe for recipe in recipes if not recipe.__name__ in oca] -recipes_x.sort() +recipes_x.sort(lambda x: x.__name__) def par(recipe, template, delimiter = , count = None): return delimiter.join(template.format(
Bug#792940: cpl-plugin-uves: please make the build reproducible
Source: cpl-plugin-uves Version: 5.5.2+dfsg-3 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: randomness X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, While working on the reproducible builds effort [1], we have noticed that cpl-plugin-uves could not be built reproducibly. The attached patch removes randomness from the build system. Once applied, cpl-plugin-uves can be built reproducibly in our reproducible toolchain. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff --git a/debian/create_sphinx.py b/debian/create_sphinx.py index 558a57c..a04e821 100644 --- a/debian/create_sphinx.py +++ b/debian/create_sphinx.py @@ -146,7 +146,7 @@ index = [ oca.find(recipe.__name__) for recipe in recipes_oca ] recipes_oca = [r for (i, r) in sorted(zip(index, recipes_oca))] recipes_x = [recipe for recipe in recipes if not recipe.__name__ in oca] -recipes_x.sort() +recipes_x.sort(lambda x: x.__name__) def par(recipe, template, delimiter = , count = None): return delimiter.join(template.format(
Bug#792204: Setting default CPU to ultrasparc for -m32 on sparc64 does not work
On 07/20/2015 01:37 AM, Michael Karcher wrote: Hello, the problem (ATOMIC_INT_LOCK_FREE == 1) applies for the 32-bit build of libstdc++, and is caused by gcc assuming a too old 32-bit sparc processor, as can be seen by: (unstable-sparc64-sbuild)mkarcher@ravirin:~$ COLUMNS=140 dpkg -l gcc-4.9 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version ArchitectureDescription +++-=-===-===-=== ii gcc-4.9 4.9.2-21+sparc64 sparc64 GNU C compiler (this is a custom build of the official debian gcc source with the symbol verification quieted by using fudged expected symbols lists) (unstable-sparc64-sbuild)mkarcher@ravirin:~$ g++-4.9 -std=c++11 -dM -E -m32 -x c++ /dev/null | grep INT_LOCK #define __GCC_ATOMIC_INT_LOCK_FREE 1 (unstable-sparc64-sbuild)mkarcher@ravirin:~$ g++-4.9 -std=c++11 -dM -E -m32 -mcpu=ultrasparc -x c++ /dev/null | grep INT_LOCK #define __GCC_ATOMIC_INT_LOCK_FREE 2 The changelog messages for gcc seem to indicate that the default CPU for -m32 is intended to be ultrasparc: gcc-4.9 (4.9.0-10) unstable; urgency=medium * Update to SVN 20140704 (r212295) from the gcc-4_9-branch. * Explicitly set cpu_32 to ultrasparc for sparc64 builds. [...] gcc-4.9 (4.9.0-9) unstable; urgency=medium * Update to SVN 20140701 (r212192) from the gcc-4_9-branch. * Update libstdc++ symbols files for ARM. * Configure --with-cpu-32=ultrasparc on sparc64. This seems to not have the intended effect of defaulting to require the ultrasparc architecture providing lock-free atomics. Regards, Michael Karcher see sparc-force-cpu.diff, which currently disables this for sparc64 biarch. So maybe somebody should just enable it and see if it works as intended, or make it working. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792929: linux-image-3.16.0-4-amd64: Sporadic hv_storvsc in dmesg and FS remounted read-only, when running as an Hyper-V guest
Package: src:linux Version: 3.16.7-ckt11-1 Severity: normal Tags: patch upstream Dear Maintainer, * What led up to the situation? Running as an Hyper-V guest, I see sporadic messages like the ones you can see at the end of this dmesg output. This doesn't appear to be related to what happens on the machine, it may be related to the underlying storage taking backup snapshots, but I am not sure since I don't have access to it. In one occasione dmesg said: [1710593.904046] sd 2:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. [1710593.904061] end_request: I/O error, dev sda, sector 531976632 [1710593.905535] Aborting journal on device sda5-8. [1710593.912586] EXT4-fs error (device sda5): ext4_journal_check_start:56: Detected aborted journal [1710593.913975] EXT4-fs (sda5): Remounting filesystem read-only [1797034.976074] EXT4-fs (sda5): error count since last fsck: 2 [1797034.976116] EXT4-fs (sda5): initial error at time 1436081211: ext4_journal_check_start:56 [1797034.976133] EXT4-fs (sda5): last error at time 1436081211: ext4_journal_check_start:56 The FS was read-only, we had to reboot and manually run fsck. This appears to be the bug in the Hyper-V virtualized storage driver described in: https://social.technet.microsoft.com/Forums/windowsserver/en-US/8807f61c-565e-45bc-abc4-af09abf59de2/ubuntu-14042-lts-generation-2-scsi-errors-on-vss-based-backups That bug lead to the patch: http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?id=dc45708ca9988656d706940df5fd102672c5de92 * What exactly did you do (or not do) that was effective (or ineffective)? Most of this messages are harmless, when it remounted RO we rebooted. * What was the outcome of this action? fsck had to be run manually * What outcome did you expect instead? I expect the FS not to be remounted read-only. -- Package-specific info: ** Version: Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt11-1 (2015-05-24) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=c52e963f-ad44-49b5-b657-65ffae35a135 ro quiet ** Not tainted ** Kernel log: [1.307341] cdrom: Uniform CD-ROM driver Revision: 3.20 [1.307713] sr 1:0:0:0: Attached scsi CD-ROM sr0 [1.310584] sd 2:0:0:0: Attached scsi generic sg0 type 0 [1.310821] sr 1:0:0:0: Attached scsi generic sg1 type 5 [1.800087] tsc: Refined TSC clocksource calibration: 1999.998 MHz [2.013645] hv_netvsc vmbus_0_13: Send section size: 6144, Section count:170 [2.013955] hv_netvsc vmbus_0_13: Device MAC 00:15:5d:00:87:1f link state up [2.273864] PM: Starting manual resume from disk [2.273873] PM: Hibernation image partition 8:1 present [2.273875] PM: Looking for hibernation image. [2.274221] PM: Image not found (code -22) [2.274224] PM: Hibernation image not present or could not be loaded. [2.453629] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null) [3.533926] random: nonblocking pool is initialized [ 11.807712] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. [ 15.117107] systemd-udevd[197]: starting version 215 [ 19.098448] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 [ 19.098457] ACPI: Power Button [PWRF] [ 19.444133] input: PC Speaker as /devices/platform/pcspkr/input/input4 [ 19.779940] hv_vmbus: registering driver hyperv_fb [ 19.780832] hyperv_fb: Screen resolution: 1152x864, Color depth: 32 [ 19.785620] Console: switching to colour frame buffer device 144x54 [ 19.968763] psmouse serio1: alps: Unknown ALPS touchpad: E7=12 00 64, EC=12 00 64 [ 20.013638] piix4_smbus :00:07.3: SMBus base address uninitialized - upgrade BIOS or use force_addr=0xaddr [ 20.172074] psmouse serio1: trackpoint: failed to get extended button data [ 20.201985] AVX version of gcm_enc/dec engaged. [ 20.206808] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni) [ 20.323755] hv_vmbus: registering driver hyperv_keyboard [ 20.356807] hv_utils: Registering HyperV Utility Driver [ 20.356812] hv_vmbus: registering driver hv_util [ 20.399659] alg: No test for crc32 (crc32-pclmul) [ 20.880089] Adding 7811068k swap on /dev/sda1. Priority:-1 extents:1 across:7811068k FS [ 22.641247] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro [ 22.649268] systemd-journald[192]: Received request to flush runtime journal from PID 1 [ 24.172149] psmouse serio1: trackpoint: IBM TrackPoint firmware: 0x01, buttons: 0/0 [ 24.173335] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/input/input5 [ 24.174317] input: AT Translated Set 2 keyboard as
Bug#792732: sosreport: generating report with --all-logs option results in 0 byte logs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Heather, Thank you for reporting this bug on the debian package. The issue that you are seeing is an upstream bug that has been reported here : https://github.com/sosreport/sos/issues/586 While sosreport is actively kept bilingual (i.e. py2 and py3), it is by no mean exempt from bugs and some of them may be specific to python3. This situation is currently being actively investigated and, given the recent activity in the upstream bug, I will try to help out to reproduce and eventually identify a fix for the problem. Once the bug is fixed upstream, I will backport the patch to the current Debian version. Kind regards, ...Louis - -- Louis Bouchard Software engineer, Ubuntu GPG : 429D 7A3B DD05 B6F8 AF63 B9C4 8B3D 867C 823E 7A61 -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJVrLRMAAoJEIs9hnyCPnphLywP/ArLVrKXWjkfe63+mhrYi6TR URo1IIIgyfwvxPy8ZcljXT/mAldfWNFGOJ6DSQM4uBhtCddUj01Opxzglmk6l83t nuzW5NcQquYHRxXyFhs9Q7TAKSe4ugVmZjWkA2cjBIlfHs1c1pTWnR7OBSSySxpC eOV+plBj1oXTRbJNhbcL09MVnI0AAvPo8QqFawO3XevfY/TZKWoejz6jXrE9vwgc 5Ch4kwgnSZY0OicxJ36ttKh6AWLLbKuPl5vhmuCeXnUtEbqzoM2fjjAJa2tHnCT2 YZi3LTZ+JBPecVUBixNgTVCS2ohccuh0cEkv7ozBtAcOsPrMmQmPr8Fns4umbGjc +kCpiqsgqOIDvzDObBc3C7ERcoIMT0kKc9wVzIbJlHqJ9ittq4Ee2ZgHHldbA+J0 qAjVNqMW3tnA8D+lsEUNohEV9BIFqEUoi2fB4Z35UjNqqnm1A65BIk49/rCSH7vq mzcBh69pamkX7qsDKpOsPHuNlp5aHHjdoezEv2fzsIPsMnZDIjFhPbD+dZcT4n1V LLYVTtbQOLaKze3RlDSpi0Xk1AGqqgmxL83MorWdRM7wlTJaUF7UZ2L/RQjChD0q zKjilGyJtV9z/vYBXSrsG6JijOPeN7l2WeQuBzJB9goTr1FvXbllEvLTJ5i6llPS LIOmtNUU/9Qmczj+3Lk4 =tV0u -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#787486: ppl: FTBFS with swi-prolog 7.x
Control: retitle -1 ppl: FTBFS with swi-prolog 7.x Since it built in 'stretch/testing' successfully I looked at the difference in installed packages after satisfying the build dependencies ... the only interesting package with a newer upstream version in sid seemed to be swi-prolog ... and then rebuilt it again in 'sid/unstable' but with swi-prolog 6.x from 'testing', which worked well. Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792388:
I noticed the commit, thx Ian! I only own a beaglebone black, so not all drivers are of interest there, but unless there's a reason not to: please enable. Hah, I also own a couple of other devices unrelated to sunxi, but what I really meant is my cubieboard 2 :P -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792927: Python ownet library cannot access sensor's attribute
Package: python-ownet
Version: 2.8p15-1
Severity: grave
The ownet python module does not work properly. This script should open a
connection to the owserver on localhost, display the information for sensor
10.67C6697351FF and then print the value of its temperature attribute:
#!/bin/python
import ownet
r = ownet.Sensor('/10.67C6697351FF', 'localhost', 4304)
print r
print r.temperature
The connection works and the sensor information is shown, but the attribute
cannot be read because a library method is not found:
walter@walter-VirtualBox:~$ python test.py
localhost:4304/10.67C6697351FF - DS18S20
Traceback (most recent call last):
File test.py, line 5, in module
print r.temperature
File /usr/lib/python2.7/dist-packages/ownet/__init__.py, line 252, in
__getattr__
attr = object._connection.read(object.__getattribute__(self,
'_attrs')[name])
AttributeError: type object 'object' has no attribute '_connection'
This error can be fixed easily by editing line 252 in file
/usr/lib/python2.7/dist-packages/ownet/__init__.py:
-- attr = object._connection.read(object.__getattribute__(self,
'_attrs')[name])
++ attr = self._connection.read(self.__getattribute__('_attrs')[name])
I have reproduced and fixed this bug on 2 machines:
* Raspbian on a Raspberry PI B with python 2.7.3-4+deb7u1
Linux smarthome 4.0.8+ #804 PREEMPT Tue Jul 14 12:57:44 BST 2015 armv6l
GNU/Linux
* Ubuntu 14.4 LTS with python 2.7.5-5ubuntu3
Linux walter-VirtualBox 3.13.0-57-generic #95-Ubuntu SMP Fri Jun 19
09:27:48 UTC 2015 i686 i686 i686 GNU/Linux
Bug#792926: Package: grub2
Package: grub2 Version: 2.02~beta2-22 This ones a DUZY for AMD 990FX boards. Previous distriutions of Amd64 did not seem to be affected by this bug.This bug affects multiple linux distributions.ASUS support is unwilling to solve thier end of the problem.Solution in part is to ban all 990FX boards until this is fixed.The bios is 64 bit capable. GRUB2 wants to setup UEFI.It supposedly does this in a manner that creates a NON-BOOTABLE installation.The bios wants partition 4 to boot from, not the first partition where the EFI boot files reside.You can only create a bootable Linux setup if you use msdos partition type, forcing partition 4 to be bootable.This is only possible from jessie live media. Writing the efi boot file to a USB stick does not work either, but should according to intel x64 specifications. Will test further on my AMD APU-based laptop.I have jessie, wheezy and squeeze all on bdrom.This in itself is supposedly a bug; distributions before jessie supposedly have no bdrom support. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792928: please set --enable-log-pid in configure
Package: isc-dhcp-server Version: 4.3.2-1 Severity: wishlist Hi, when multiple instances of dhcpd are running, it would be helpful to have the logging processes pid in the syslog to distinguish which instance of the dhcpd instances created a given log entry. This is a common case when IPv4 and IPv6 instances run. Unfortunately, this can only be set at compile time by using the --enable-log-pid option to configure. Please consider enabling this option in a future version of the package. Greetings Marc -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792945: authbind : please make the build reproducible
Source: authbind Version: 3.0.3.5 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi! While working on the “reproducible builds” effort [1], we have noticed that authbind could not be built reproducibly. The attached patch sets the mtimes of all files which are modified during the built to the date of the last changelog entry in order to produce files with reproducible metadata. Cheers, akira [1]: https://wiki.debian.org/ReproducibleBuilds diff -Nru authbind-2.1.1/debian/changelog authbind-2.1.1+nmu1/debian/changelog --- authbind-2.1.1/debian/changelog 2012-06-11 00:17:19.0 +0200 +++ authbind-2.1.1+nmu1/debian/changelog2015-07-15 23:42:10.0 +0200 @@ -1,3 +1,10 @@ +authbind (2.1.1+nmu1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix mtimes before building binary packages to produce reproducible output + + -- akira marival...@gmail.com Wed, 15 Jul 2015 23:40:51 +0200 + authbind (2.1.1) unstable; urgency=low * Manpage has an example of which files will be checked and read diff -Nru authbind-2.1.1/debian/rules authbind-2.1.1+nmu1/debian/rules --- authbind-2.1.1/debian/rules 2012-06-03 02:45:04.0 +0200 +++ authbind-2.1.1+nmu1/debian/rules2015-07-15 23:37:33.0 +0200 @@ -29,6 +29,8 @@ arch = $(shell dpkg --print-architecture) +BUILD_DATE := $(shell dpkg-parsechangelog --show-field Date) + INSTALL = install INSTALL_FILE= $(INSTALL) -p-o root -g root -m 644 INSTALL_PROGRAM = $(INSTALL) -p-o root -g root -m 755 @@ -90,6 +92,8 @@ dpkg-gencontrol -isp chown -R root.root debian/tmp chmod -R g-ws debian/tmp + find debian/tmp -newermt '$(BUILD_DATE)' -print0 | \ + xargs -0r touch --no-dereference --date='$(BUILD_DATE)' dpkg --build debian/tmp .. binary: binary-indep binary-arch
Bug#792944: authbind : please make the build reproducible
Source: authbind Version: 3.0.3.5 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi! While working on the “reproducible builds” effort [1], we have noticed that authbind could not be built reproducibly. The attached patch sets the mtimes of all files which are modified during the built to the date of the last changelog entry in order to produce files with reproducible metadata. Cheers, akira [1]: https://wiki.debian.org/ReproducibleBuilds diff -Nru authbind-2.1.1/debian/changelog authbind-2.1.1+nmu1/debian/changelog --- authbind-2.1.1/debian/changelog 2012-06-11 00:17:19.0 +0200 +++ authbind-2.1.1+nmu1/debian/changelog2015-07-15 23:42:10.0 +0200 @@ -1,3 +1,10 @@ +authbind (2.1.1+nmu1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix mtimes before building binary packages to produce reproducible output + + -- akira marival...@gmail.com Wed, 15 Jul 2015 23:40:51 +0200 + authbind (2.1.1) unstable; urgency=low * Manpage has an example of which files will be checked and read diff -Nru authbind-2.1.1/debian/rules authbind-2.1.1+nmu1/debian/rules --- authbind-2.1.1/debian/rules 2012-06-03 02:45:04.0 +0200 +++ authbind-2.1.1+nmu1/debian/rules2015-07-15 23:37:33.0 +0200 @@ -29,6 +29,8 @@ arch = $(shell dpkg --print-architecture) +BUILD_DATE := $(shell dpkg-parsechangelog --show-field Date) + INSTALL = install INSTALL_FILE= $(INSTALL) -p-o root -g root -m 644 INSTALL_PROGRAM = $(INSTALL) -p-o root -g root -m 755 @@ -90,6 +92,8 @@ dpkg-gencontrol -isp chown -R root.root debian/tmp chmod -R g-ws debian/tmp + find debian/tmp -newermt '$(BUILD_DATE)' -print0 | \ + xargs -0r touch --no-dereference --date='$(BUILD_DATE)' dpkg --build debian/tmp .. binary: binary-indep binary-arch
Bug#785542: viewnior: Behavior setting doesn't work corectly
after upgrading viewnior from 1.4-2+b1 to 1.5-1 , I noticed that basically all options that can be set via the behavior tab simply don't work as expected. You can set, for instance, on mouse wheel to navigate images, but you get zoom image instead, etc. On the previous version everything works just fine I can't seem to reproduce this problem on my two computers. Is it still occurring ? -- Dariusz Dwornikowski, Institute of Computing Science, Poznań University of Technology www.cs.put.poznan.pl/ddwornikowski/ room 1.6.2 BTiCW | tel. +48 61 665 23 71 signature.asc Description: Digital signature
Bug#790988: bullet: library transition may be needed when GCC 5 is the default
Control: user release.debian@packages.debian.org Control: usertag -1 + transition Control: block -1 by 790756 Control: reassign -1 release.debian.org Control: severity -1 normal Control: tags -1 patch Hello release team, I would like to request a transition for bullet due to a SONAME bump in the latest version 2.83.5 as soon as GCC 5 is the new default. The upload to unstable happened before I became aware of #790988 and the package could pass the NEW queue. Openmw was the only reverse-dependency in contrib/experimental back then. None of the current reverse-dependencies is in testing at the moment. I have rebuilt all of them and with the exception of gazebo, they all can be built from source with Bullet 2.83.5. List of r-deps (source packages): openmw gazebo hkl cyphesis-cpp Ben file: Good: .depends ~ /libbullet2\.83\-dbg|libbulletcollision2\.83|libbulletdynamics2\.83|libbulletfileloader2\.83|libbulletsoftbody2\.83|libbulletworldimporter2\.83|libbulletxmlworldimporter2\.83|libconvexdecomposition2\.83|libgimpactutils2\.83|libhacd2\.83|liblinearmath2\.83/ Bad: .depends ~ /libbullet2\.82\-dbg|libbulletcollision2\.82|libbulletdynamics2\.82|libbulletfileloader2\.82|libbulletsoftbody2\.82|libbulletworldimporter2\.82|libbulletxmlworldimporter2\.82|libconvexdecomposition2\.82|libgimpactutils2\.82|libhacd2\.82|liblinearmath2\.82/ Regards, Markus signature.asc Description: OpenPGP digital signature
Bug#792983: gerstensaft: please make the build reproducible
Source: gerstensaft Version: 0.3-4 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi! While working on the “reproducible builds” effort [1], we have noticed that gerstensaft could not be built reproducibly. The attached patch sets the mtimes of all files which are modified during the built to the date of the last changelog entry in order to produce files with reproducible metadata. Cheers, akira [1]: https://wiki.debian.org/ReproducibleBuilds diff -u gerstensaft-0.3/debian/rules gerstensaft-0.3/debian/rules --- gerstensaft-0.3/debian/rules +++ gerstensaft-0.3/debian/rules @@ -17,6 +17,8 @@ # SHELL=/bin/bash +BUILD_DATE := $(shell dpkg-parsechangelog --show-field Date) + # The name and version of the source # source = $(shell grep ^Source: debian/control|head -1|sed 's/Source: \(.*\)/\1/g') @@ -85,6 +87,8 @@ # dpkg-shlibdeps debian/tmp/usr/bin/beer dpkg-gencontrol -isp + find debian/tmp -newermt '$(BUILD_DATE)' -print0 | \ + xargs -0r touch --no-dereference --date='$(BUILD_DATE)' dpkg --build debian/tmp .. binary: binary-indep binary-arch diff -u gerstensaft-0.3/debian/changelog gerstensaft-0.3/debian/changelog --- gerstensaft-0.3/debian/changelog +++ gerstensaft-0.3/debian/changelog @@ -1,3 +1,10 @@ +gerstensaft (0.3-4.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix mtimes before building binary packages to produce reproducible output + + -- akira marival...@gmail.com Sun, 19 Jul 2015 13:59:51 +0200 + gerstensaft (0.3-4) unstable; urgency=low * Properly separate homepage
Bug#792984: integrit: please make the build reproducible
Source: integrit Version: 4.1-1 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi! While working on the “reproducible builds” effort [1], we have noticed that integrit could not be built reproducibly. The attached patch sets the mtimes of all files which are modified during the built to the date of the last changelog entry in order to produce files with reproducible metadata. Cheers, akira [1]: https://wiki.debian.org/ReproducibleBuilds diff -u integrit-4.1/debian/changelog integrit-4.1/debian/changelog --- integrit-4.1/debian/changelog +++ integrit-4.1/debian/changelog @@ -1,3 +1,10 @@ +integrit (4.1-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix mtimes before building binary packages to produce reproducible output + + -- akira marival...@gmail.com Sun, 19 Jul 2015 14:26:24 +0200 + integrit (4.1-1) unstable; urgency=low * new upstream release. diff -u integrit-4.1/debian/rules integrit-4.1/debian/rules --- integrit-4.1/debian/rules +++ integrit-4.1/debian/rules @@ -7,6 +7,7 @@ DEB_HOST_GNU_TYPE ?=$(shell dpkg-architecture -qDEB_HOST_GNU_TYPE) DEB_BUILD_GNU_TYPE ?=$(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE) DEB_HOST_ARCH ?=$(shell dpkg-architecture -qDEB_HOST_ARCH) +BUILD_DATE := $(shell dpkg-parsechangelog --show-field Date) DIET_ARCHS =alpha amd64 arm hppa i386 ia64 mips mipsel powerpc ppc64 s390 sparc ifeq (,$(findstring $(DEB_HOST_ARCH),$(DIET_ARCHS))) @@ -101,6 +102,8 @@ binary-arch: deb-checkdir deb-checkuid install integrit.deb dpkg-gencontrol -isp -pintegrit -P'$(DIR)' + find '$(DIR)' -newermt '$(BUILD_DATE)' -print0 | \ +xargs -0r touch --no-dereference --date='$(BUILD_DATE)' dpkg -b '$(DIR)' .. binary: binary-indep binary-arch
Bug#792986: uruk: please make the build reproducible
Source: uruk Version:20150401-1 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi! While working on the “reproducible builds” effort [1], we have noticed that uruk could not be built reproducibly. The attached patch sets the mtimes of all files which are modified during the built to the date of the last changelog entry in order to produce files with reproducible metadata. Once applied, uruk can be built reproducibly in our current experimental framework. Cheers, akira [1]: https://wiki.debian.org/ReproducibleBuilds diff -Nru uruk-20150401/debian/changelog uruk-20150401/debian/changelog --- uruk-20150401/debian/changelog 2015-05-12 21:21:41.0 +0200 +++ uruk-20150401/debian/changelog 2015-07-14 15:07:03.0 +0200 @@ -1,3 +1,10 @@ +uruk (20150401-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix mtimes before building binary packages to produce reproducible output + + -- akira marival...@gmail.com Tue, 14 Jul 2015 15:06:27 +0200 + uruk (20150401-1) unstable; urgency=low * New upstream release: The Gorp en Roovert Release (missed: uruk version diff -Nru uruk-20150401/debian/rules uruk-20150401/debian/rules --- uruk-20150401/debian/rules 2015-05-12 21:21:41.0 +0200 +++ uruk-20150401/debian/rules 2015-07-14 15:03:38.0 +0200 @@ -17,6 +17,8 @@ package=uruk docdir = debian/$(package)/usr/share/doc/$(package) +BUILD_DATE := $(shell dpkg-parsechangelog --show-field Date) + define checkdir test -f debian/rules endef @@ -89,6 +91,8 @@ done chown -R root.root debian/$(package) chmod -R go=rX debian/$(package) + find debian/$(package) -newermt '$(BUILD_DATE)' -print0 | \ + xargs -0r touch --no-dereference --date='$(BUILD_DATE)' dpkg --build debian/$(package) .. binary-arch: checkroot build
Bug#792988: xbs: please make the build reproducible
Source: xbs Version: 0-9 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi! While working on the “reproducible builds” effort [1], we have noticed that xbs could not be built reproducibly. The attached patch sets the mtimes of all files which are modified during the built to the date of the last changelog entry in order to produce files with reproducible metadata. Once applied, xbs can be built reproducibly in our current experimental framework. Cheers, akira [1]: https://wiki.debian.org/ReproducibleBuilds diff -Nru xbs-0/debian/changelog xbs-0/debian/changelog --- xbs-0/debian/changelog 2015-03-07 23:59:59.0 +0100 +++ xbs-0/debian/changelog 2015-07-14 15:14:23.0 +0200 @@ -1,3 +1,10 @@ +xbs (0-9.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix mtimes before building binary packages + + -- akira marival...@gmail.com Tue, 14 Jul 2015 15:13:30 +0200 + xbs (0-9) unstable; urgency=low * patch from Sylvestre Ledru sylves...@debian.org to make this build diff -Nru xbs-0/debian/rules xbs-0/debian/rules --- xbs-0/debian/rules 2015-03-07 23:58:40.0 +0100 +++ xbs-0/debian/rules 2015-07-14 15:13:21.0 +0200 @@ -7,6 +7,8 @@ ddir=`pwd`/debian/tmp +BUILD_DATE := $(shell dpkg-parsechangelog --show-field Date) + build: $(checkdir) make @@ -70,6 +72,8 @@ # clean permissions and build chown -R root:root debian/tmp chmod -R go=rX debian/tmp + find debian/tmp -newermt '$(BUILD_DATE)' -print0 | \ + xargs -0r touch --no-dereference --date='$(BUILD_DATE)' dpkg --build debian/tmp .. define checkdir
Bug#792977: luakit: please make the build reproducible
Source: luakit Version: 2012.09.13-r1-4 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi! While working on the “reproducible builds” effort [1], we have noticed that luakit could not be built reproducibly. The attached patch sets the mtimes of all files which are modified during the built to the date of the last changelog entry in order to produce files with reproducible metadata. Cheers, akira [1]: https://wiki.debian.org/ReproducibleBuilds diff -Nru luakit-2012.09.13-r1/debian/changelog luakit-2012.09.13-r1/debian/changelog --- luakit-2012.09.13-r1/debian/changelog 2015-05-26 03:46:14.0 +0200 +++ luakit-2012.09.13-r1/debian/changelog 2015-07-14 21:45:24.0 +0200 @@ -1,3 +1,9 @@ +luakit (2012.09.13-r1-5) UNRELEASED; urgency=medium + + * Fix mtimes before building binary packages to produce reproducible output + + -- akira marival...@gmail.com Tue, 14 Jul 2015 21:45:01 +0200 + luakit (2012.09.13-r1-4) unstable; urgency=medium * Patch from Chris Lamb to make the build reproducible. diff -Nru luakit-2012.09.13-r1/debian/rules luakit-2012.09.13-r1/debian/rules --- luakit-2012.09.13-r1/debian/rules 2015-05-26 03:45:48.0 +0200 +++ luakit-2012.09.13-r1/debian/rules 2015-07-14 21:43:50.0 +0200 @@ -13,6 +13,8 @@ DEB_BUILD_GNU_TYPE = $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE) DEB_HOST_GNU_TYPE = $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE) +BUILD_DATE := $(shell dpkg-parsechangelog --show-field Date) + STRIP=strip ifneq ($(DEB_BUILD_GNU_TYPE),$(DEB_HOST_GNU_TYPE)) @@ -81,6 +83,8 @@ chmod a-x debian/$(package)/usr/share/luakit/lib/lousy/*.lua chown -R root:root debian/$(package) chmod -R go=rX debian/$(package) + find debian/luakit -newermt '$(BUILD_DATE)' -print0 | \ + xargs -0r touch --no-dereference --date='$(BUILD_DATE)' dpkg --build debian/$(package) ..
Bug#792974: liblockfile: please make the build reproducible
Source: liblockfile Version: 1.09-6 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi! While working on the “reproducible builds” effort [1], we have noticed that liblockfile could not be built reproducibly. The attached patch sets the mtimes of all files which are modified during the built to the date of the last changelog entry in order to produce files with reproducible metadata. Cheers, akira [1]: https://wiki.debian.org/ReproducibleBuilds diff -Nru liblockfile-1.09/debian/changelog liblockfile-1.09/debian/changelog --- liblockfile-1.09/debian/changelog 2013-06-02 11:46:21.0 +0200 +++ liblockfile-1.09/debian/changelog 2015-07-14 17:12:57.0 +0200 @@ -1,3 +1,10 @@ +liblockfile (1.09-6.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix mtimes before building binary packages to produce reproducible output + + -- akira marival...@gmail.com Tue, 14 Jul 2015 17:12:23 +0200 + liblockfile (1.09-6) unstable; urgency=low * Merge 1.09-5ubuntu1 diff -Nru liblockfile-1.09/debian/rules liblockfile-1.09/debian/rules --- liblockfile-1.09/debian/rules 2012-06-13 13:26:39.0 +0200 +++ liblockfile-1.09/debian/rules 2015-07-14 17:12:20.0 +0200 @@ -20,6 +20,8 @@ DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH) +BUILD_DATE := $(shell dpkg-parsechangelog --show-field Date) + build-arch:config.status $(checkdir) make @@ -68,6 +70,8 @@ $(do_md5sums) dpkg-shlibdeps liblockfile.so dpkg-gencontrol -pliblockfile1 -P$(tmp) -isp + find $(tmp) -newermt '$(BUILD_DATE)' -print0 | \ + xargs -0r touch --no-dereference --date='$(BUILD_DATE)' dpkg --build $(tmp) .. # # Build liblockfile-bin @@ -97,6 +101,8 @@ $(do_md5sums) dpkg-shlibdeps dotlockfile dpkg-gencontrol -pliblockfile-bin -P$(tmp) -isp + find $(tmp) -newermt '$(BUILD_DATE)' -print0 | \ + xargs -0r touch --no-dereference --date='$(BUILD_DATE)' dpkg --build $(tmp) .. # # Build liblockfile-dev @@ -132,6 +138,8 @@ $(tmp)/usr/share/doc/liblockfile-dev/copyright $(do_md5sums) dpkg-gencontrol -pliblockfile-dev -P$(tmp) -isp + find $(tmp) -newermt '$(BUILD_DATE)' -print0 | \ + xargs -0r touch --no-dereference --date='$(BUILD_DATE)' dpkg --build $(tmp) ..
Bug#792970: fortunes-bg: please make the build reproducible
Source: fortunes-bg Version: 1.1 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi! While working on the “reproducible builds” effort [1], we have noticed that fortunes-bg could not be built reproducibly. The attached patch sets the mtimes of all files which are modified during the built to the date of the last changelog entry in order to produce files with reproducible metadata. Cheers, akira [1]: https://wiki.debian.org/ReproducibleBuilds diff -Nru fortunes-bg-1.1/changelog fortunes-bg-1.1+nmu1/changelog --- fortunes-bg-1.1/changelog 2004-11-30 04:56:58.0 +0100 +++ fortunes-bg-1.1+nmu1/changelog 2015-07-17 22:23:40.0 +0200 @@ -1,3 +1,10 @@ +fortunes-bg (1.1+nmu1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix mtimes before building binary packages to produce reproducible output + + -- akira marival...@gmail.com Fri, 17 Jul 2015 22:23:29 +0200 + fortunes-bg (1.1) unstable; urgency=low * The text of GPL (ver. 1) included directly in the copyright file. diff -Nru fortunes-bg-1.1/Makefile fortunes-bg-1.1+nmu1/Makefile --- fortunes-bg-1.1/Makefile2004-11-09 02:40:45.0 +0100 +++ fortunes-bg-1.1+nmu1/Makefile 2015-07-17 22:23:26.0 +0200 @@ -10,6 +10,8 @@ FORTUNEROOT=/usr/share/games/fortunes +BUILD_DATE := $(shell dpkg-parsechangelog --show-field Date) + build: $(compiled) $(u8) rm -r bg/ mkdir bg @@ -42,6 +44,8 @@ dpkg-gencontrol -isp chown -R root.root tmp chmod -R go=rX,u=rwX tmp + find debian/tmp -newermt '$(BUILD_DATE)' -print0 | \ + xargs -0r touch --no-dereference --date='$(BUILD_DATE)' dpkg --build tmp .. binary-arch: checkroot build diff -Nru fortunes-bg-1.1/rules fortunes-bg-1.1+nmu1/rules --- fortunes-bg-1.1/rules 2004-11-09 02:40:45.0 +0100 +++ fortunes-bg-1.1+nmu1/rules 2015-07-17 22:23:26.0 +0200 @@ -10,6 +10,8 @@ FORTUNEROOT=/usr/share/games/fortunes +BUILD_DATE := $(shell dpkg-parsechangelog --show-field Date) + build: $(compiled) $(u8) rm -r bg/ mkdir bg @@ -42,6 +44,8 @@ dpkg-gencontrol -isp chown -R root.root tmp chmod -R go=rX,u=rwX tmp + find debian/tmp -newermt '$(BUILD_DATE)' -print0 | \ + xargs -0r touch --no-dereference --date='$(BUILD_DATE)' dpkg --build tmp .. binary-arch: checkroot build
Bug#792962: Correct spelling of ${shlibs:Depends}
Package: snappy1.0.3-java
Version: 1.0.3-rc3~dfsg-4
Tags: patch
Patch attached.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
diff --git a/debian/control b/debian/control
index 786bb2a..b703241 100644
--- a/debian/control
+++ b/debian/control
@@ -21,7 +21,7 @@ Package: libsnappy1.0.3-java
Architecture: all
Depends: ${misc:Depends},
${maven:Depends},
- ${shlib:Depends},
+ ${shlibs::Depends},
libsnappy1
Recommends: ${maven:OptionalDepends}
Description: Snappy v1.0.3 for Java, a fast compressor/decompresser
Bug#792868: transition: libsidplayfp
On 19/07/15 15:55, László Böszörményi (GCS) wrote: Both build fine with the new API as it was only extended. Why was the soversion bumped then? Emilio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792961: enemies-of-carlotta: please make the build reproducible
Source: enemies-of-carlotta Version: 1.2.6-4 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi! While working on the “reproducible builds” effort [1], we have noticed that enemies-of-carlotta could not be built reproducibly. The attached patch sets the mtimes of all files which are modified during the built to the date of the last changelog entry in order to produce files with reproducible metadata. Cheers, akira [1]: https://wiki.debian.org/ReproducibleBuilds diff -u enemies-of-carlotta-1.2.6/debian/rules enemies-of-carlotta-1.2.6/debian/rules --- enemies-of-carlotta-1.2.6/debian/rules +++ enemies-of-carlotta-1.2.6/debian/rules @@ -2,6 +2,8 @@ package=enemies-of-carlotta +BUILD_DATE := $(shell dpkg-parsechangelog --show-field Date) + build: $(MAKE) check @@ -41,6 +43,8 @@ dpkg-gencontrol -isp chown -R root.root debian/tmp chmod -R o-s,go=u,go-ws debian/tmp + find debian/tmp -newermt '$(BUILD_DATE)' -print0 | \ + xargs -0r touch --no-dereference --date='$(BUILD_DATE)' dpkg --build debian/tmp .. binary-arch: diff -u enemies-of-carlotta-1.2.6/debian/changelog enemies-of-carlotta-1.2.6/debian/changelog --- enemies-of-carlotta-1.2.6/debian/changelog +++ enemies-of-carlotta-1.2.6/debian/changelog @@ -1,3 +1,10 @@ +enemies-of-carlotta (1.2.6-4.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix mtimes before building binary packages to produce reproducible output + + -- akira marival...@gmail.com Fri, 17 Jul 2015 18:02:51 +0200 + enemies-of-carlotta (1.2.6-4) unstable; urgency=high * Switched from deprecated md5 to hashlib (closes: #596623)
Bug#792969: flowscan: please make the build reproducible
Source: flowscan Version: 1.006-13.2 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi! While working on the “reproducible builds” effort [1], we have noticed that flowscan could not be built reproducibly. The attached patch sets the mtimes of all files which are modified during the built to the date of the last changelog entry in order to produce files with reproducible metadata. Cheers, akira [1]: https://wiki.debian.org/ReproducibleBuilds diff -u flowscan-1.006/debian/rules flowscan-1.006/debian/rules --- flowscan-1.006/debian/rules +++ flowscan-1.006/debian/rules @@ -9,6 +9,8 @@ binary: binary-arch binary-indep +BUILD_DATE := $(shell dpkg-parsechangelog --show-field Date) + binary-arch: binary-indep: build @@ -59,6 +61,8 @@ dpkg-shlibdeps debian/tmp/usr/bin/* dpkg-gencontrol -isp + find debian/tmp -newermt '$(BUILD_DATE)' -print0 | \ + xargs -0r touch --no-dereference --date='$(BUILD_DATE)' dpkg --build debian/tmp .. build: diff -u flowscan-1.006/debian/changelog flowscan-1.006/debian/changelog --- flowscan-1.006/debian/changelog +++ flowscan-1.006/debian/changelog @@ -1,3 +1,10 @@ +flowscan (1.006-13.3) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix mtimes before building binary packages to produce reproducible output + + -- akira marival...@gmail.com Fri, 17 Jul 2015 22:20:28 +0200 + flowscan (1.006-13.2) unstable; urgency=low * Non-maintainer upload.
Bug#792958: dtaus: please make the build reproducible
Source: dtaus Version: 0.9-1 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi! While working on the “reproducible builds” effort [1], we have noticed that dtaus could not be built reproducibly. The attached patch sets the mtimes of all files which are modified during the built to the date of the last changelog entry in order to produce files with reproducible metadata. Cheers, akira [1]: https://wiki.debian.org/ReproducibleBuilds diff -u dtaus-0.9/debian/rules dtaus-0.9/debian/rules --- dtaus-0.9/debian/rules +++ dtaus-0.9/debian/rules @@ -24,6 +24,8 @@ version = $(shell grep ^$(source) debian/changelog|head -1 |sed 's/.*(\(.*\)\-[^\-]*).*/\1/g') revision = $(shell grep ^$(source) debian/changelog|head -1 |sed 's/.*([^\-]*\-\(.*\)).*/\1/g') +BUILD_DATE := $(shell dpkg-parsechangelog --show-field Date) + installbin = install -g root -o root -m 755 installdoc = install -g root -o root -m 644 @@ -80,6 +82,8 @@ # dpkg-shlibdeps debian/tmp/usr/bin/dtaus dpkg-gencontrol -isp + find debian/tmp -newermt '$(BUILD_DATE)' -print0 | \ + xargs -0r touch --no-dereference --date='$(BUILD_DATE)' dpkg --build debian/tmp .. binary: binary-indep binary-arch diff -u dtaus-0.9/debian/changelog dtaus-0.9/debian/changelog --- dtaus-0.9/debian/changelog +++ dtaus-0.9/debian/changelog @@ -1,3 +1,10 @@ +dtaus (0.9-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix mtimes before building binary packages to produce reproducible output + + -- akira marival...@gmail.com Fri, 17 Jul 2015 17:54:58 +0200 + dtaus (0.9-1) unstable; urgency=low * New upstream version
Bug#792162: DontBlameSendmail option: GroupReadableDefaultAuthInfoFile unrecognized
Hi Harry, On 2015-07-12 12:41, Harald Dunkel wrote: Since version 8.14.9-3 sendmail doesn't start, but complains /etc/mail/sendmail.cf: line 107: readcf: DontBlameSendmail option: GroupReadableDefaultAuthInfoFile unrecognized I doubt the typo correction is the cause for this ... but rather the reordering of masquerading options and mailer definitions in sendmail.mc which allows to create a sendmail.cf out of the box. (I posted a diff of the generated default sendmail.cf in these 2 versions to the bug previously, but you probably didn't get a copy of this) My sendmail.mc doesn't set such an option. Rebuilding sendmail.cf doesn't help. Moving back to version 8.14.9-2 fixes the problem. Could you apply the typo correction manually on 8.14.9-2: sed -i s/GroupReadableaDefaultAuthInfoFile/GroupReadableDefaultAuthInfoFile/ /usr/share/sendmail/cf/domain/debian-mta.m4 and see if rebuilding sendmail.cf causes the same problem? How does the diff between the two sendmail.cf file versions look like? Anyway, this should be working fine in experimental where sendmail actually knows about GroupReadableDefaultAuthInfoFile Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792945: authbind : please make the build reproducible
Maria Valentina Marin writes (Bug#792945: authbind : please make the build reproducible): Source: authbind Version: 3.0.3.5 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org ... The attached patch sets the mtimes of all files which are modified during the built to the date of the last changelog entry in order to produce files with reproducible metadata. Glrgk. I had forgotten that this package has such an ad-hoc build system. I apologise. +authbind (2.1.1+nmu1) UNRELEASED; urgency=medium + * Non-maintainer upload. FAOD I did not understand your covering note to say that you were actually doing an NMU. But, such an NMU would be welcome. If you don't do an NMU I will fold this patch in at some point, but maybe not particularly soon. I may rewrite the build system instead. + find debian/tmp -newermt '$(BUILD_DATE)' -print0 | \ + xargs -0r touch --no-dereference --date='$(BUILD_DATE)' Again, I'm sorry to preside over a situation where this kind of thing is the best answer. Thanks for your contribution. Regards, Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792946: bwidget: FSL failes to run due to bwidget
Package: bwidget Version: 1.9.8-1 Severity: important Tags: upstream Dear Maintainer, please have a look at 792758: http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=792758 _uninstalling_ bwidget solves the startup problem, leading me to believe that - the call to bwidget from FSL is wrong - something has changed in bwidget and FSL is not aware of the new call - some error creeped into bwidget in the new version in Debian Jessie. Thank you for considering this bug, regards, Vincent -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/64 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages bwidget depends on: ii tk 8.6.0+8 bwidget recommends no packages. bwidget suggests no packages. -- De informatie opgenomen in dit bericht kan vertrouwelijk zijn en is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht onterecht ontvangt, wordt u verzocht de inhoud niet te gebruiken en de afzender direct te informeren door het bericht te retourneren. Het Universitair Medisch Centrum Utrecht is een publiekrechtelijke rechtspersoon in de zin van de W.H.W. (Wet Hoger Onderwijs en Wetenschappelijk Onderzoek) en staat geregistreerd bij de Kamer van Koophandel voor Midden-Nederland onder nr. 30244197. Denk s.v.p aan het milieu voor u deze e-mail afdrukt. -- This message may contain confidential information and is intended exclusively for the addressee. If you receive this message unintentionally, please do not use the contents but notify the sender immediately by return e-mail. University Medical Center Utrecht is a legal person by public law and is registered at the Chamber of Commerce for Midden-Nederland under no. 30244197. Please consider the environment before printing this e-mail. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792952: dhcpdump : please make the build reproducible
Source: dhcpdump Version: 1.8-2 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi! While working on the “reproducible builds” effort [1], we have noticed that dhcpdump could not be built reproducibly. The attached patch sets the mtimes of all files which are modified during the built to the date of the last changelog entry in order to produce files with reproducible metadata. Cheers, akira [1]: https://wiki.debian.org/ReproducibleBuilds diff -u dhcpdump-1.8/debian/rules dhcpdump-1.8/debian/rules --- dhcpdump-1.8/debian/rules +++ dhcpdump-1.8/debian/rules @@ -24,6 +24,8 @@ version = $(shell grep ^$(source) debian/changelog|head -1 |sed 's/.*(\(.*\)\-[^\-]*).*/\1/g') revision = $(shell grep ^$(source) debian/changelog|head -1 |sed 's/.*([^\-]*\-\(.*\)).*/\1/g') +BUILD_DATE := $(shell dpkg-parsechangelog --show-field Date) + installbin = install -g root -o root -m 755 installdoc = install -g root -o root -m 644 @@ -74,6 +76,8 @@ # dpkg-shlibdeps debian/tmp/usr/sbin/dhcpdump dpkg-gencontrol -isp + find debian/tmp -newermt '$(BUILD_DATE)' -print0 | \ + xargs -0r touch --no-dereference --date='$(BUILD_DATE)' dpkg --build debian/tmp .. binary: binary-indep binary-arch diff -u dhcpdump-1.8/debian/changelog dhcpdump-1.8/debian/changelog --- dhcpdump-1.8/debian/changelog +++ dhcpdump-1.8/debian/changelog @@ -1,3 +1,10 @@ +dhcpdump (1.8-2.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix mtimes before building binary packages to produce reproducible output + + -- akira marival...@gmail.com Fri, 17 Jul 2015 17:18:14 +0200 + dhcpdump (1.8-2) unstable; urgency=low * Bump standards-version
Bug#792953: dhcping: please make the build reproducible
Source: dhcping Version: 1.2-4.1 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi! While working on the “reproducible builds” effort [1], we have noticed that dhcping could not be built reproducibly. The attached patch sets the mtimes of all files which are modified during the built to the date of the last changelog entry in order to produce files with reproducible metadata. Cheers, akira [1]: https://wiki.debian.org/ReproducibleBuilds diff -u dhcping-1.2/debian/changelog dhcping-1.2/debian/changelog --- dhcping-1.2/debian/changelog +++ dhcping-1.2/debian/changelog @@ -1,3 +1,10 @@ +dhcping (1.2-4.2) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix mtimes before building binary packages to produce reproducible output + + -- akira marival...@gmail.com Fri, 17 Jul 2015 17:22:57 +0200 + dhcping (1.2-4.1) unstable; urgency=low * Non-maintainer upload. diff -u dhcping-1.2/debian/rules dhcping-1.2/debian/rules --- dhcping-1.2/debian/rules +++ dhcping-1.2/debian/rules @@ -24,6 +24,8 @@ version = $(shell grep ^$(source) debian/changelog|head -1 |sed 's/.*(\(.*\)\-[^\-]*).*/\1/g') revision = $(shell grep ^$(source) debian/changelog|head -1 |sed 's/.*([^\-]*\-\(.*\)).*/\1/g') +BUILD_DATE := $(shell dpkg-parsechangelog --show-field Date) + installbin = install -g root -o root -m 755 installdoc = install -g root -o root -m 644 @@ -76,6 +78,8 @@ # dpkg-shlibdeps debian/tmp/usr/sbin/dhcping dpkg-gencontrol -isp + find debian/tmp -newermt '$(BUILD_DATE)' -print0 | \ + xargs -0r touch --no-dereference --date='$(BUILD_DATE)' dpkg --build debian/tmp .. binary: binary-indep binary-arch
Bug#792979: runit: please make the build reproducible
Source: runit Version: 2.1.2-3 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi! While working on the “reproducible builds” effort [1], we have noticed that runit could not be built reproducibly. The attached patch sets the mtimes of all files which are modified during the built to the date of the last changelog entry in order to produce files with reproducible metadata. Cheers, akira [1]: https://wiki.debian.org/ReproducibleBuilds diff -u runit-2.1.2/debian/changelog runit-2.1.2/debian/changelog --- runit-2.1.2/debian/changelog +++ runit-2.1.2/debian/changelog @@ -1,3 +1,10 @@ +runit (2.1.2-3.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix mtimes before building binary packages to produce reproducible output + + -- akira marival...@gmail.com Wed, 15 Jul 2015 17:10:54 +0200 + runit (2.1.2-3) unstable; urgency=medium * workaround #766187 by copying from sysvinit-2.88dsf: diff -u runit-2.1.2/debian/rules runit-2.1.2/debian/rules --- runit-2.1.2/debian/rules +++ runit-2.1.2/debian/rules @@ -12,6 +12,8 @@ CPPFLAGS =$(shell DEB_BUILD_MAINT_OPTIONS=$(DEB_BUILD_MAINT_OPTIONS) \ dpkg-buildflags --get CPPFLAGS) +BUILD_DATE := $(shell dpkg-parsechangelog --show-field Date) + DEB_HOST_GNU_TYPE =$(shell dpkg-architecture -qDEB_HOST_GNU_TYPE) DEB_BUILD_GNU_TYPE =$(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE) ifneq ($(DEB_HOST_GNU_TYPE),$(DEB_BUILD_GNU_TYPE)) @@ -144,6 +146,8 @@ test '$(CC)' != 'gcc' || \ dpkg-shlibdeps '$(DIR)'/usr/sbin/* '$(DIR)'/usr/bin/* dpkg-gencontrol -isp -prunit -P'$(DIR)' + find '$(DIR)' -newermt '$(BUILD_DATE)' -print0 | \ + xargs -0r touch --no-dereference --date='$(BUILD_DATE)' dpkg -b '$(DIR)' .. binary: binary-indep binary-arch
Bug#792980: tworld: please make the build reproducible
Source: tworld Version: 1.3.0-6 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi! While working on the “reproducible builds” effort [1], we have noticed that tworld could not be built reproducibly. The attached patch sets the mtimes of all files which are modified during the built to the date of the last changelog entry in order to produce files with reproducible metadata. Cheers, akira [1]: https://wiki.debian.org/ReproducibleBuilds diff -u tworld-1.3.0/debian/rules tworld-1.3.0/debian/rules --- tworld-1.3.0/debian/rules +++ tworld-1.3.0/debian/rules @@ -18,6 +18,7 @@ DEB_HOST_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE) DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE) +BUILD_DATE := $(shell dpkg-parsechangelog --show-field Date) CFLAGS = -Wall -W -fomit-frame-pointer -DNDEBUG LDFLAGS = -Wall -W @@ -114,6 +115,8 @@ -p$(PKG1) -P$(TMP1) cd $(TMP1) find * -type f ! -regex '^DEBIAN/.*' -print0 | \ xargs -r0 md5sum DEBIAN/md5sums + find $(TMP1) -newermt '$(BUILD_DATE)' -print0 | \ + xargs -0r touch --no-dereference --date='$(BUILD_DATE)' dpkg --build $(TMP1) .. $(INSTALL_FILE) debian/copyright debian/README.Debian \ @@ -125,6 +128,8 @@ -p$(PKG2) -P$(TMP2) cd $(TMP2) find * -type f ! -regex '^DEBIAN/.*' -print0 | \ xargs -r0 md5sum DEBIAN/md5sums + find $(TMP2) -newermt '$(BUILD_DATE)' -print0 | \ + xargs -0r touch --no-dereference --date='$(BUILD_DATE)' dpkg --build $(TMP2) .. binary: binary-indep binary-arch diff -u tworld-1.3.0/debian/changelog tworld-1.3.0/debian/changelog --- tworld-1.3.0/debian/changelog +++ tworld-1.3.0/debian/changelog @@ -1,3 +1,10 @@ +tworld (1.3.0-6.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix mtimes before building binary packages to produce reproducible output + + -- akira marival...@gmail.com Wed, 15 Jul 2015 19:14:15 +0200 + tworld (1.3.0-6) unstable; urgency=low [ Peter Pentchev ]
Bug#792981: wmweather: please make the build reproducible
Source: wmweather Version: 2.4.5-2 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi! While working on the “reproducible builds” effort [1], we have noticed that wmweather could not be built reproducibly. The attached patch sets the mtimes of all files which are modified during the built to the date of the last changelog entry in order to produce files with reproducible metadata. Cheers, akira [1]: https://wiki.debian.org/ReproducibleBuilds diff -Nru wmweather-2.4.5/debian/changelog wmweather-2.4.5/debian/changelog --- wmweather-2.4.5/debian/changelog2013-12-30 16:28:13.0 +0100 +++ wmweather-2.4.5/debian/changelog2015-07-15 19:36:09.0 +0200 @@ -1,3 +1,10 @@ +wmweather (2.4.5-2.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix mtimes before building binary packages to produce reproducible output + + -- akira marival...@gmail.com Wed, 15 Jul 2015 19:35:49 +0200 + wmweather (2.4.5-2) unstable; urgency=low * Updated build system. diff -Nru wmweather-2.4.5/debian/rules wmweather-2.4.5/debian/rules --- wmweather-2.4.5/debian/rules2013-12-30 16:15:09.0 +0100 +++ wmweather-2.4.5/debian/rules2015-07-15 19:35:47.0 +0200 @@ -17,6 +17,8 @@ export CFLAGS export LDFLAGS +BUILD_DATE := $(shell dpkg-parsechangelog --show-field Date) + clean: $(testdir) rm -f build-stamp debian/files debian/substvars @@ -66,6 +68,8 @@ dpkg-shlibdeps debian/wmweather/usr/bin/wmweather dpkg-gencontrol -isp -pwmweather -Pdebian/wmweather chmod -R u+w,go=u-w debian/wmweather + find debian/wmweather -newermt '$(BUILD_DATE)' -print0 | \ + xargs -0r touch --no-dereference --date='$(BUILD_DATE)' dpkg --build debian/wmweather .. binary-indep:
Bug#792989: freecdb: please make the build reproducible
Source: freecdb Version: 0.75 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi! While working on the “reproducible builds” effort [1], we have noticed that freecdb could not be built reproducibly. The attached patch sets the mtimes of all files which are modified during the built to the date of the last changelog entry in order to produce files with reproducible metadata. Cheers, akira [1]: https://wiki.debian.org/ReproducibleBuilds diff -Nru freecdb-0.75/debian/changelog freecdb-0.75+nmu1/debian/changelog --- freecdb-0.75/debian/changelog 2006-01-13 22:12:00.0 +0100 +++ freecdb-0.75+nmu1/debian/changelog 2015-07-19 13:45:25.0 +0200 @@ -1,3 +1,10 @@ +freecdb (0.75+nmu1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix mtimes before building binary packages to produce reproducible output + + -- akira marival...@gmail.com Sun, 19 Jul 2015 13:45:01 +0200 + freecdb (0.75) unstable; urgency=low * take over upstream (closes: #272127). diff -Nru freecdb-0.75/debian/rules freecdb-0.75+nmu1/debian/rules --- freecdb-0.75/debian/rules 2006-01-13 22:12:00.0 +0100 +++ freecdb-0.75+nmu1/debian/rules 2015-07-19 13:44:58.0 +0200 @@ -12,6 +12,8 @@ DIR =$(shell pwd)/debian/freecdb +BUILD_DATE := $(shell dpkg-parsechangelog --show-field Date) + build: deb-checkdir build-stamp build-stamp: $(MAKE) CC='$(CC)' @@ -40,6 +42,8 @@ binary-arch: install freecdb.deb test '$(CC)' != 'gcc' || dpkg-shlibdeps '$(DIR)'/usr/bin/* dpkg-gencontrol -isp -pfreecdb -P'$(DIR)' + find '$(DIR)' -newermt '$(BUILD_DATE)' -print0 | \ + xargs -0r touch --no-dereference --date='$(BUILD_DATE)' dpkg -b '$(DIR)' .. binary: binary-indep binary-arch
Bug#792985: ipsvd: please make the build reproducible
Source: ipsvd Version: 1.0.0-3 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi! While working on the “reproducible builds” effort [1], we have noticed that ipsvd could not be built reproducibly. The attached patch sets the mtimes of all files which are modified during the built to the date of the last changelog entry in order to produce files with reproducible metadata. Cheers, akira [1]: https://wiki.debian.org/ReproducibleBuilds diff -u ipsvd-1.0.0/debian/changelog ipsvd-1.0.0/debian/changelog --- ipsvd-1.0.0/debian/changelog +++ ipsvd-1.0.0/debian/changelog @@ -1,3 +1,10 @@ +ipsvd (1.0.0-3.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix mtimes before building binary packages to produce reproducible output + + -- akira marival...@gmail.com Sun, 19 Jul 2015 14:42:34 +0200 + ipsvd (1.0.0-3) unstable; urgency=low * debian/rules: no longer install the sslsvd, sslio programs and man diff -u ipsvd-1.0.0/debian/rules ipsvd-1.0.0/debian/rules --- ipsvd-1.0.0/debian/rules +++ ipsvd-1.0.0/debian/rules @@ -14,6 +14,8 @@ DIR =$(shell pwd)/debian/ipsvd +BUILD_DATE := $(shell dpkg-parsechangelog --show-field Date) + patch: deb-checkdir patch-stamp patch-stamp: for i in `ls -1 debian/diff/*.diff || :`; do \ @@ -68,6 +70,8 @@ binary-arch: install ipsvd.deb test '$(CC)' != 'gcc' || dpkg-shlibdeps '$(DIR)'/usr/bin/* dpkg-gencontrol -isp -pipsvd -P'$(DIR)' + find '$(DIR)' -newermt '$(BUILD_DATE)' -print0 | \ + xargs -0r touch --no-dereference --date='$(BUILD_DATE)' dpkg -b '$(DIR)' .. binary: binary-indep binary-arch
Bug#792592: poppler: ftbfs with GCC-5 and Qt 5.4
On Thu, Jul 16, 2015 at 04:54:25PM +0200, Matthias Klose wrote: Package: src:poppler Version: 0.71-5 Severity: important Tags: sid stretch patch User: debian-...@lists.debian.org Usertags: ftbfs-gcc-5 patch / work around at https://launchpadlibrarian.net/211805046/poppler_0.33.0-0ubuntu2~gcc5.1_0.33.0-0ubuntu2.diff.gz + cd qt5/src + g++ -DHAVE_CONFIG_H -I. -I../.. -I../../poppler -I../.. -I../../poppler -I/usr/include/x86_64-linux-gnu/qt5/QtXml -I/usr/include/x86_64-linux-gnu/qt5 -I/usr/include/x86_64-linux-gnu/qt5/QtWidgets -I/usr/include/x86_64-linux-gnu/qt5 -I/usr/include/x86_64-linux-gnu/qt5/QtGui -I/usr/include/x86_64-linux-gnu/qt5 -I/usr/include/x86_64-linux-gnu/qt5/QtCore -I/usr/include/x86_64-linux-gnu/qt5 -D_FORTIFY_SOURCE=2 -fvisibility=hidden -fvisibility-inlines-hidden -Dpoppler_qt5_EXPORTS -fPIC -fPIC -Wall -Woverloaded-virtual -Wnon-virtual-dtor -Wcast-align -fno-exceptions -fno-check-new -fno-common -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c poppler-document.cc -fPIE -o libpoppler_qt5_la-poppler-document.o In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qchar.h:37:0, from /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:37, from /usr/include/x86_64-linux-gnu/qt5/QtCore/qdatetime.h:37, from /usr/include/x86_64-linux-gnu/qt5/QtCore/QDateTime:1, from poppler-annotation.h:31, from poppler-qt5.h:37, from poppler-document.cc:27: /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:1052:4: error: #error You must build your code with position independent code if Qt was built with -reduce-relocations. Compile your code with -fPIC (-fPIE is not enough). # error You must build your code with position independent code if Qt was built with -reduce-relocations. \ Try hardening=+all,-pie to turn off fPIE. Ideally you'd do this for just Qt5, I guess. -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] signature.asc Description: Digital signature
Bug#792987: jargon: please make the build reproducible
Source: jargon Version: 4.0.0-5.1 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi! While working on the “reproducible builds” effort [1], we have noticed that jargon could not be built reproducibly. The attached patch sets the mtimes of all files which are modified during the built to the date of the last changelog entry in order to produce files with reproducible metadata. Cheers, akira [1]: https://wiki.debian.org/ReproducibleBuilds diff -u jargon-4.0.0/debian/changelog jargon-4.0.0/debian/changelog --- jargon-4.0.0/debian/changelog +++ jargon-4.0.0/debian/changelog @@ -1,3 +1,10 @@ +jargon (4.0.0-5.2) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix mtimes before building binary packages to produce reproducible output + + -- akira marival...@gmail.com Sun, 19 Jul 2015 14:50:54 +0200 + jargon (4.0.0-5.1) unstable; urgency=medium * Non-maintainer upload. diff -u jargon-4.0.0/debian/rules jargon-4.0.0/debian/rules --- jargon-4.0.0/debian/rules +++ jargon-4.0.0/debian/rules @@ -11,6 +11,8 @@ MANDIR=$(DESTDIR)/usr/share/man INFODIR=$(DESTDIR)/usr/share/info +BUILD_DATE := $(shell dpkg-parsechangelog --show-field Date) + build: $(checkdir) touch build @@ -52,6 +54,8 @@ dpkg-gencontrol -isp chown -R root.root debian/tmp chmod -R go=rX debian/tmp + find debian/tmp -newermt '$(BUILD_DATE)' -print0 | \ + xargs -0r touch --no-dereference --date='$(BUILD_DATE)' dpkg --build debian/tmp .. binary-arch: checkroot build
Bug#792162: DontBlameSendmail option: GroupReadableDefaultAuthInfoFile unrecognized
Followup-For: Bug #792162 attached is a filtered diff of /etc/mail between installations of -2 and -3 in a pbuilder chroot Andreas diff -ur /tmp/pbuilder/build/17461/etc/mail/sendmail.cf /tmp/pbuilder/build/7573/etc/mail/sendmail.cf --- /tmp/pbuilder/build/17461/etc/mail/sendmail.cf 2015-07-20 12:39:51.875344086 +0200 +++ /tmp/pbuilder/build/7573/etc/mail/sendmail.cf 2015-07-20 12:40:23.679394196 +0200 @@ -21,7 +21,7 @@ # # SENDMAIL CONFIGURATION FILE # -# built by root@myhost on Mon Jul 20 10:32:11 UTC 2015 +# built by root@myhost on Mon Jul 20 10:31:56 UTC 2015 # in / # using /usr/share/sendmail/cf/ as configuration include directory # @@ -87,7 +87,7 @@ # override file safeties - setting this option compromises system security, # addressing the actual file configuration problem is preferred # need to set this before any file actions are encountered in the cf file -O DontBlameSendmail= ,AssumeSafeChown,ForwardFileInGroupWritableDirPath,GroupWritableForwardFileSafe,GroupWritableIncludeFileSafe,IncludeFileInGroupWritableDirPath,DontWarnForwardFileInUnsafeDirPath,TrustStickyBit,NonRootSafeAddr,GroupWritableIncludeFile,GroupReadableaDefaultAuthInfoFile +O DontBlameSendmail= ,AssumeSafeChown,ForwardFileInGroupWritableDirPath,GroupWritableForwardFileSafe,GroupWritableIncludeFileSafe,IncludeFileInGroupWritableDirPath,DontWarnForwardFileInUnsafeDirPath,TrustStickyBit,NonRootSafeAddr,GroupWritableIncludeFile,GroupReadableDefaultAuthInfoFile # default LDAP map specification # need to set this now before any LDAP maps are defined @@ -168,7 +168,7 @@ Kaccess hash -TTMPF /etc/mail/access # Configuration version number -DZ8.14.9/Debian-2 +DZ8.14.9/Debian-3 ### @@ -1780,12 +1780,15 @@ # SHdrToL R$+ $: $AddDomain $1 add local domain if needed -R$* @ *LOCAL* $* $: $1 @ $j . $2 +R$* $: $MasqHdr $1 do all-masquerading # # Common code to add local domain name (only if always-add-domain) # SAddDomain +R$* @ $* $* $@ $1 @ $2 $3 already fully qualified + +R$+ $@ $1 @ *LOCAL* add local qualification Mlocal, P=/usr/sbin/sensible-mda, F=lsDFMAw5:/|@qPn9S, S=EnvFromL/HdrFromL, R=EnvToL/HdrToL, T=DNS/RFC822/X-Unix, @@ -1870,19 +1873,19 @@ R$+ $: $MasqSMTP $1 R$+ $: $MasqHdr $1 -Msmtp, P=[IPC], F=mDFMuX, S=EnvFromSMTP/HdrFromSMTP, R=EnvToSMTP, E=\r\n, L=990, +Msmtp, P=[IPC], F=mDFMuX, S=EnvFromSMTP/HdrFromSMTP, R=EnvToSMTP/HdrFromSMTP, E=\r\n, L=990, T=DNS/RFC822/SMTP, A=TCP $h -Mesmtp, P=[IPC], F=mDFMuXa, S=EnvFromSMTP/HdrFromSMTP, R=EnvToSMTP, E=\r\n, L=990, +Mesmtp, P=[IPC], F=mDFMuXa, S=EnvFromSMTP/HdrFromSMTP, R=EnvToSMTP/HdrFromSMTP, E=\r\n, L=990, T=DNS/RFC822/SMTP, A=TCP $h -Msmtp8, P=[IPC], F=mDFMuX8, S=EnvFromSMTP/HdrFromSMTP, R=EnvToSMTP, E=\r\n, L=990, +Msmtp8, P=[IPC], F=mDFMuX8, S=EnvFromSMTP/HdrFromSMTP, R=EnvToSMTP/HdrFromSMTP, E=\r\n, L=990, T=DNS/RFC822/SMTP, A=TCP $h -Mdsmtp, P=[IPC], F=mDFMuXa%, S=EnvFromSMTP/HdrFromSMTP, R=EnvToSMTP, E=\r\n, L=990, +Mdsmtp, P=[IPC], F=mDFMuXa%, S=EnvFromSMTP/HdrFromSMTP, R=EnvToSMTP/HdrFromSMTP, E=\r\n, L=990, T=DNS/RFC822/SMTP, A=TCP $h -Mrelay, P=[IPC], F=mDFMuXa8, S=EnvFromSMTP/HdrFromSMTP, R=MasqSMTP, E=\r\n, L=2040, +Mrelay, P=[IPC], F=mDFMuXa8, S=EnvFromSMTP/HdrFromSMTP, R=MasqSMTP/MasqRelay, E=\r\n, L=2040, T=DNS/RFC822/SMTP, A=TCP $h @@ -1987,13 +1990,14 @@ # include(`/etc/mail/m4/dialup.m4')dnl # include(`/etc/mail/m4/provider.m4')dnl # dnl # -# dnl # Default Mailer setup -# MAILER_DEFINITIONS -# MAILER(`local')dnl -# MAILER(`smtp')dnl -# # dnl # Masquerading options # FEATURE(`always_add_domain')dnl # MASQUERADE_AS(`myhost.domain.example.com')dnl # FEATURE(`allmasquerade')dnl # FEATURE(`masquerade_envelope')dnl +# dnl # +# dnl # Default Mailer setup +# MAILER_DEFINITIONS +# MAILER(`local')dnl +# MAILER(`smtp')dnl +# Only in /tmp/pbuilder/build/17461/etc/mail: sendmail.cf.errors diff -ur /tmp/pbuilder/build/17461/etc/mail/sendmail.mc /tmp/pbuilder/build/7573/etc/mail/sendmail.mc --- /tmp/pbuilder/build/17461/etc/mail/sendmail.mc 2015-07-20 12:39:51.871344080 +0200 +++ /tmp/pbuilder/build/7573/etc/mail/sendmail.mc 2015-07-20 12:40:23.675394190 +0200 @@ -97,13 +97,14 @@ include(`/etc/mail/m4/dialup.m4')dnl include(`/etc/mail/m4/provider.m4')dnl dnl # -dnl # Default Mailer setup -MAILER_DEFINITIONS -MAILER(`local')dnl -MAILER(`smtp')dnl - dnl # Masquerading options FEATURE(`always_add_domain')dnl MASQUERADE_AS(`myhost.domain.example.com')dnl FEATURE(`allmasquerade')dnl FEATURE(`masquerade_envelope')dnl +dnl # +dnl # Default Mailer setup +MAILER_DEFINITIONS +MAILER(`local')dnl +MAILER(`smtp')dnl +
Bug#792204: Setting default CPU to ultrasparc for -m32 on sparc64 does not work
On 07/20/2015 12:31 PM, Matthias Klose wrote: On 07/20/2015 01:37 AM, Michael Karcher wrote: Hello, the problem (ATOMIC_INT_LOCK_FREE == 1) applies for the 32-bit build of libstdc++, and is caused by gcc assuming a too old 32-bit sparc processor, as can be seen by: (unstable-sparc64-sbuild)mkarcher@ravirin:~$ COLUMNS=140 dpkg -l gcc-4.9 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version ArchitectureDescription +++-=-===-===-=== ii gcc-4.9 4.9.2-21+sparc64 sparc64 GNU C compiler (this is a custom build of the official debian gcc source with the symbol verification quieted by using fudged expected symbols lists) (unstable-sparc64-sbuild)mkarcher@ravirin:~$ g++-4.9 -std=c++11 -dM -E -m32 -x c++ /dev/null | grep INT_LOCK #define __GCC_ATOMIC_INT_LOCK_FREE 1 (unstable-sparc64-sbuild)mkarcher@ravirin:~$ g++-4.9 -std=c++11 -dM -E -m32 -mcpu=ultrasparc -x c++ /dev/null | grep INT_LOCK #define __GCC_ATOMIC_INT_LOCK_FREE 2 The changelog messages for gcc seem to indicate that the default CPU for -m32 is intended to be ultrasparc: gcc-4.9 (4.9.0-10) unstable; urgency=medium * Update to SVN 20140704 (r212295) from the gcc-4_9-branch. * Explicitly set cpu_32 to ultrasparc for sparc64 builds. [...] gcc-4.9 (4.9.0-9) unstable; urgency=medium * Update to SVN 20140701 (r212192) from the gcc-4_9-branch. * Update libstdc++ symbols files for ARM. * Configure --with-cpu-32=ultrasparc on sparc64. This seems to not have the intended effect of defaulting to require the ultrasparc architecture providing lock-free atomics. Regards, Michael Karcher see sparc-force-cpu.diff, which currently disables this for sparc64 biarch. So maybe somebody should just enable it and see if it works as intended, or make it working. ahh, and r7502 disabled it again, so probably somebody should have a look how to set the default for the 32bit build. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792948: ITP: stringtemplate4 -- StringTemplate templating engine for Java
Package: wnpp Severity: wishlist Owner: Emmanuel Bourg ebo...@apache.org * Package name: stringtemplate4 Version : 4.0.6 Upstream Author : Terence Parr * URL : http://www.stringtemplate.org * License : BSD-3-clause Programming Lang: Java Description : StringTemplate templating engine for Java StringTemplate is a Java template engine for generating source code, web pages, emails, or any other formatted text output. StringTemplate is particularly good at multi-targeted code generators, multiple site skins, and internationalization/localization. Its distinguishing characteristic is that unlike other engines, it strictly enforces model-view separation. Strict separation makes websites and code generators more flexible and maintainable; it also provides an excellent defense against malicious template authors. This package is an update of the existing stringtemplate package. The version 4 is incompatible with the version 3 (different package name and Maven coordinates) and thus requires a different package. stringtemplate4 is required to upgrade antlr3 to the latest version. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792947: cvs-mailcommit: please make the build reproducible
Source: cvs-mailcommit Version: 1.19-2 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi! While working on the “reproducible builds” effort [1], we have noticed that cvs-mailcommit could not be built reproducibly. The attached patch sets the mtimes of all files which are modified during the built to the date of the last changelog entry in order to produce files with reproducible metadata. Cheers, akira [1]: https://wiki.debian.org/ReproducibleBuilds diff -u cvs-mailcommit-1.19/debian/changelog cvs-mailcommit-1.19/debian/changelog --- cvs-mailcommit-1.19/debian/changelog +++ cvs-mailcommit-1.19/debian/changelog @@ -1,3 +1,10 @@ +cvs-mailcommit (1.19-2.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix mtimes before building binary packages to produce reproducible output + + -- akira marival...@gmail.com Fri, 17 Jul 2015 16:35:27 +0200 + cvs-mailcommit (1.19-2) unstable; urgency=medium * Added the missing dependency to RCS *sigh* diff -u cvs-mailcommit-1.19/debian/rules cvs-mailcommit-1.19/debian/rules --- cvs-mailcommit-1.19/debian/rules +++ cvs-mailcommit-1.19/debian/rules @@ -24,6 +24,8 @@ version = $(shell grep ^$(source) debian/changelog|head -n 1 |sed 's/.*(\(.*\)\-[^\-]*).*/\1/g') revision = $(shell grep ^$(source) debian/changelog|head -n 1 |sed 's/.*([^\-]*\-\(.*\)).*/\1/g') +BUILD_DATE := $(shell dpkg-parsechangelog --show-field Date) + installbin = install -g root -o root -m 755 installdoc = install -g root -o root -m 644 @@ -67,6 +69,8 @@ # dpkg-shlibdeps debian/tmp/usr/bin/* dpkg-gencontrol -isp chown root.root debian/tmp/DEBIAN/control + find debian/tmp -newermt '$(BUILD_DATE)' -print0 | \ + xargs -0r touch --no-dereference --date='$(BUILD_DATE)' dpkg --build debian/tmp .. binary: binary-indep binary-arch
Bug#792951: dbview: please make the build reproducible
Source: dbview Version: 1.0.4-1 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi! While working on the “reproducible builds” effort [1], we have noticed that dbview could not be built reproducibly. The attached patch sets the mtimes of all files which are modified during the built to the date of the last changelog entry in order to produce files with reproducible metadata. Cheers, akira [1]: https://wiki.debian.org/ReproducibleBuilds diff -u dbview-1.0.4/debian/changelog dbview-1.0.4/debian/changelog --- dbview-1.0.4/debian/changelog +++ dbview-1.0.4/debian/changelog @@ -1,3 +1,10 @@ +dbview (1.0.4-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix mtimes before building binary packages to produce reproducible output + + -- akira marival...@gmail.com Fri, 17 Jul 2015 17:09:05 +0200 + dbview (1.0.4-1) unstable; urgency=low * Fixed typo in NMU-Disclaimer, thanks to Petter Reinholdtsen (See: diff -u dbview-1.0.4/debian/rules dbview-1.0.4/debian/rules --- dbview-1.0.4/debian/rules +++ dbview-1.0.4/debian/rules @@ -24,6 +24,8 @@ version = $(shell grep ^$(package) debian/changelog|head -1 |sed 's/.*(\(.*\)\-[^\-]*).*/\1/g') revision = $(shell grep ^$(package) debian/changelog|head -1 |sed 's/.*([^\-]*\-\(.*\)).*/\1/g') +BUILD_DATE := $(shell dpkg-parsechangelog --show-field Date) + installbin = install -o root -g root -m 755 installdoc = install -o root -g root -m 644 @@ -74,6 +76,8 @@ # dpkg-shlibdeps debian/tmp/usr/bin/dbview dpkg-gencontrol -isp + find debian/tmp -newermt '$(BUILD_DATE)' -print0 | \ + xargs -0r touch --no-dereference --date='$(BUILD_DATE)' dpkg --build debian/tmp .. binary: binary-indep binary-arch
Bug#792949: chimera2: please make the build reproducible
Source: chimera2 Version: 2.0a19-8 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi! While working on the “reproducible builds” effort [1], we have noticed that chimera2 could not be built reproducibly. The attached patch sets the mtimes of all files which are modified during the built to the date of the last changelog entry in order to produce files with reproducible metadata. Cheers, akira [1]: https://wiki.debian.org/ReproducibleBuilds diff -u chimera2-2.0a19/debian/rules chimera2-2.0a19/debian/rules --- chimera2-2.0a19/debian/rules +++ chimera2-2.0a19/debian/rules @@ -9,6 +9,8 @@ package=chimera2 +BUILD_DATE := $(shell dpkg-parsechangelog --show-field Date) + ifneq (,$(findstring nostrip,$(DEB_BUILD_OPTIONS))) INSTALLOPT= else @@ -63,6 +65,8 @@ dpkg-gencontrol -isp chown -R root.root debian/tmp chmod -R g-ws debian/tmp + find debian/tmp -newermt '$(BUILD_DATE)' -print0 | \ + xargs -0r touch --no-dereference --date='$(BUILD_DATE)' dpkg --build debian/tmp .. define checkdir diff -u chimera2-2.0a19/debian/changelog chimera2-2.0a19/debian/changelog --- chimera2-2.0a19/debian/changelog +++ chimera2-2.0a19/debian/changelog @@ -1,3 +1,10 @@ +chimera2 (2.0a19-8.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix mtimes before building binary packages to produce reproducible output + + -- akira marival...@gmail.com Fri, 17 Jul 2015 16:05:52 +0200 + chimera2 (2.0a19-8) unstable; urgency=low * Fix segfault with font handling - Thanks to Flos Lonicera for patch
Bug#792950: ccze: please make the build reproducible
Source: ccze
Version: 0.2.1-2
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Hi!
While working on the “reproducible builds” effort [1], we have noticed
that ccze could not be built reproducibly.
The attached patch sets the mtimes of all files which are modified
during the built to the date of the last changelog entry in order to
produce files with reproducible metadata.
Cheers,
akira
[1]: https://wiki.debian.org/ReproducibleBuilds
diff -u ccze-0.2.1/debian/changelog ccze-0.2.1/debian/changelog
--- ccze-0.2.1/debian/changelog
+++ ccze-0.2.1/debian/changelog
@@ -1,3 +1,10 @@
+ccze (0.2.1-2.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix mtimes before building binary packages to produce reproducible output
+
+ -- akira marival...@gmail.com Thu, 16 Jul 2015 23:52:43 +0200
+
ccze (0.2.1-2) unstable; urgency=low
* Add myself as Maintainer, as Gergely seems to be MIA
diff -u ccze-0.2.1/debian/rules ccze-0.2.1/debian/rules
--- ccze-0.2.1/debian/rules
+++ ccze-0.2.1/debian/rules
@@ -8,6 +8,7 @@
CFLAGS ?= -g
BGT:= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
HGT:= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
+BUILD_DATE := $(shell dpkg-parsechangelog --show-field Date)
ifneq (,$(findstring noopt,${DEB_BUILD_OPTIONS}))
CFLAGS += -O0
@@ -81,6 +82,9 @@
## Generate DEBIAN/control
dpkg-gencontrol -isp -p${PACKAGE} -Tdebian/${PACKAGE}.substvars \
-P${PKGDIR}
+## Fix mtimes before building binary packages
+ find ${PKGDIR} -newermt '$(BUILD_DATE)' -print0 | \
+ xargs -0r touch --no-dereference --date='$(BUILD_DATE)'
## Build the binary package
dpkg --build ${PKGDIR} ..
Bug#792993: cgoban: please make the build reproducible
Source: cgoban Version: 1.9.14-17 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi! While working on the “reproducible builds” effort [1], we have noticed that cgoban could not be built reproducibly. The attached patch sets the mtimes of all files which are modified during the built to the date of the last changelog entry in order to produce files with reproducible metadata. Once applied, cgoban can be built reproducibly in our current experimental framework. Cheers, akira [1]: https://wiki.debian.org/ReproducibleBuilds diff -Nru cgoban-1.9.14/debian/changelog cgoban-1.9.14/debian/changelog --- cgoban-1.9.14/debian/changelog 2012-05-06 20:31:51.0 +0200 +++ cgoban-1.9.14/debian/changelog 2015-07-14 11:33:04.0 +0200 @@ -1,3 +1,11 @@ +cgoban (1.9.14-17.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix mtimes before building binary packages to produce reproducible +output + + -- akira marival...@gmail.com Tue, 14 Jul 2015 11:32:08 +0200 + cgoban (1.9.14-17) unstable; urgency=low * Fixed crash on maximization, closes: #387209. diff -Nru cgoban-1.9.14/debian/rules cgoban-1.9.14/debian/rules --- cgoban-1.9.14/debian/rules 2012-05-06 20:31:30.0 +0200 +++ cgoban-1.9.14/debian/rules 2015-07-14 14:34:19.0 +0200 @@ -3,6 +3,8 @@ testdir = test -f src/goBoard.c test -f debian/rules testroot = test x`whoami` = xroot +BUILD_DATE := $(shell dpkg-parsechangelog --show-field Date) + # FOR AUTOCONF 2.52 AND NEWER ONLY ifeq ($(DEB_BUILD_GNU_TYPE), $(DEB_HOST_GNU_TYPE)) CONFFLAGS += --build $(DEB_HOST_GNU_TYPE) @@ -72,6 +74,8 @@ dpkg-shlibdeps debian/cgoban/usr/games/cgoban dpkg-gencontrol -isp -pcgoban -Pdebian/cgoban chmod -R u+w,go=u-w debian/cgoban + find debian/cgoban -newermt '$(BUILD_DATE)' -print0 | \ + xargs -0r touch --no-dereference --date='$(BUILD_DATE)' dpkg --build debian/cgoban .. .PHONY: clean binary binary-arch binary-indep
Bug#792990: skalibs: please make the build reproducible
Source: skalibs Version: 0.47-1 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi! While working on the “reproducible builds” effort [1], we have noticed that skalibs could not be built reproducibly. The attached patch sets the mtimes of all files which are modified during the built to the date of the last changelog entry in order to produce files with reproducible metadata. Cheers, akira [1]: https://wiki.debian.org/ReproducibleBuilds diff -u skalibs-0.47/debian/changelog skalibs-0.47/debian/changelog --- skalibs-0.47/debian/changelog +++ skalibs-0.47/debian/changelog @@ -1,3 +1,10 @@ +skalibs (0.47-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix mtimes before building binary packages to produce reproducible output + + -- akira marival...@gmail.com Wed, 15 Jul 2015 18:15:29 +0200 + skalibs (0.47-1) unstable; urgency=low * new upstream version. diff -u skalibs-0.47/debian/rules skalibs-0.47/debian/rules --- skalibs-0.47/debian/rules +++ skalibs-0.47/debian/rules @@ -14,6 +14,8 @@ DIR =$(shell pwd)/debian/skalibs +BUILD_DATE := $(shell dpkg-parsechangelog --show-field Date) + configure: deb-checkdir configure-stamp configure-stamp: ln -s skalibs-0.47 skalibs @@ -81,10 +83,14 @@ binary-indep: install-indep skalibs-doc.deb dpkg-gencontrol -isp -pskalibs-doc -P'$(DIR)'-doc + find '$(DIR)'-doc -newermt '$(BUILD_DATE)' -print0 | \ + xargs -0r touch --no-dereference --date='$(BUILD_DATE)' dpkg -b '$(DIR)'-doc .. binary-arch: install-arch skalibs-dev.deb dpkg-gencontrol -isp -pskalibs-dev -P'$(DIR)'-dev + find '$(DIR)'-dev -newermt '$(BUILD_DATE)' -print0 | \ + xargs -0r touch --no-dereference --date='$(BUILD_DATE)' dpkg -b '$(DIR)'-dev .. binary: binary-indep binary-arch
Bug#792991: gpsmanshp: please make the build reproducible
Source: gpsmanshp Version: 1.2.3-4 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi! While working on the “reproducible builds” effort [1], we have noticed that gpsmanshp could not be built reproducibly. The attached patch sets the mtimes of all files which are modified during the built to the date of the last changelog entry in order to produce files with reproducible metadata. Cheers, akira [1]: https://wiki.debian.org/ReproducibleBuilds diff -Nru gpsmanshp-1.2.3/debian/changelog gpsmanshp-1.2.3/debian/changelog --- gpsmanshp-1.2.3/debian/changelog2013-10-11 09:06:04.0 +0200 +++ gpsmanshp-1.2.3/debian/changelog2015-07-19 14:06:26.0 +0200 @@ -1,3 +1,10 @@ +gpsmanshp (1.2.3-4.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix mtimes before building binary packages to produce reproducible output + + -- akira marival...@gmail.com Sun, 19 Jul 2015 14:06:15 +0200 + gpsmanshp (1.2.3-4) unstable; urgency=low * Fixed permissions of some control files diff -Nru gpsmanshp-1.2.3/debian/rules gpsmanshp-1.2.3/debian/rules --- gpsmanshp-1.2.3/debian/rules2013-10-11 09:18:35.0 +0200 +++ gpsmanshp-1.2.3/debian/rules2015-07-19 14:06:12.0 +0200 @@ -10,6 +10,8 @@ LDFLAGS:=$(shell dpkg-buildflags --get LDFLAGS) +BUILD_DATE := $(shell dpkg-parsechangelog --show-field Date) + build: $(MAKE) -f Makefile TCLVERSION=$(TCLVERSION) LDFLAGS=$(LDFLAGS) @@ -53,6 +55,8 @@ dpkg-shlibdeps $(INSTALLDIR)/gpsmanshp.so dpkg-gencontrol -isp (cd $(TMPROOT) ; md5sum usr/lib/tcl$(TCLVERSION)/gpsmanshp.so DEBIAN/md5sums ; md5sum usr/share/doc/gpsmanshp/* DEBIAN/md5sums ; md5sum usr/share/doc/gpsmanshp/html/*DEBIAN/md5sums ; chmod 644 DEBIAN/md5sums) + find debian/tmp -newermt '$(BUILD_DATE)' -print0 | \ +xargs -0r touch --no-dereference --date='$(BUILD_DATE)' dpkg-deb --build $(TMPROOT) .. binary: binary-arch
Bug#792473: cups: After updating to 2.0.3-6 in testing cups interface no longer works
Le lundi, 20 juillet 2015, 11.04:21 MAG4 Piemonte a écrit : Hi, we also confirm the bug after updating to 2.0.3-6 and the temporary workaround manually running cupsd. We have some clients running Testing and comparing the cups* running processes we found that every client has /usr/sbin/cups-browsed /usr/sbin/cupsd -l /usr/lib/cups/notifier/dbus dbus:// The presence of /usr/sbin/cupsd -l indicates that it got started correctly by systemd. but only the workarounded manually running cupsd has cupsd -C /etc/cups/cupsd.conf -s /etc/cups/cups-files.conf There should be no difference between letting systemd launch cupsd -l or launching the above command manually. This points to a weird behaviour when launched by systemd. What do the following commands output when the manual workaround has not been used (aka, cupsd launched by systemd, but apparently inactive) (please launch them as root): # grep -E 'WebInterface|Listen' /etc/cups/cupsd.conf # systemdctl status cups cups.socket cups.path # journalctl -u cups /tmp/cups.journal Please attach cups.journal Cheers, OdyX -- OdyX -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
