Bug#776637: pulseaudio: resets the volume to 100% everytime I connect my bluetooth speakers
Am Donnerstag, den 12.02.2015, 10:30 -0300 schrieb Felipe Sateler: Does this problem occur after disconnecting and reconnecting the speakers? If so, please provide a verbose log of pulseaudio[1] where you connect the bluetooth speakers. This problem occurs every time I connect my speakers. I'll attach a pulseaudio log file I already posted with report #776632. I started pulseaudio, entered GNOME bluetooth settings, connected to my bluetooth speakers and then entered GNOME audio settings. In this case I was not affected by bug #776632, so the speakers were addded as audio output device. Thanks for this log. I'm currrently a bit busy to investigate this, but in the meantime please check this askubuntu post to see if anything applies to you: http://askubuntu.com/questions/396841/how-can-i-save-my-bluetooth-headset-volume-settings Thanks for your speedy answer and the link! I didn't edit my /etc/pulse/default.pa but I'll attach this file anyway. I'll also attach the output of 'pacmd list-modules'. Modules module-device-restore and module-card-restore are both loaded. I deleted ~/.config/pulse/ which contains the database with device volumes several times before and tried it again now – but without any luck. Since it is mentioned that applications can override the default settings I didn't use Rhythmbox this time but tried out Totem, VLC and Iceweasel after connecting the speakers instead – also without any luck. I had these speakers for some months now and connected them several times every day. Every single time I connected them volume was set to 100%. Please tell me if I can provide any more useful information. #!/usr/bin/pulseaudio -nF # # This file is part of PulseAudio. # # PulseAudio is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version. # # PulseAudio is distributed in the hope that it will be useful, but # WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU # General Public License for more details. # # You should have received a copy of the GNU Lesser General Public License # along with PulseAudio; if not, write to the Free Software Foundation, # Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA. # This startup script is used only if PulseAudio is started per-user # (i.e. not in system mode) .nofail ### Load something into the sample cache #load-sample-lazy x11-bell /usr/share/sounds/gtk-events/activate.wav #load-sample-lazy pulse-hotplug /usr/share/sounds/startup3.wav #load-sample-lazy pulse-coldplug /usr/share/sounds/startup3.wav #load-sample-lazy pulse-access /usr/share/sounds/generic.wav .fail ### Automatically restore the volume of streams and devices load-module module-device-restore load-module module-stream-restore load-module module-card-restore ### Automatically augment property information from .desktop files ### stored in /usr/share/application load-module module-augment-properties ### Should be after module-*-restore but before module-*-detect load-module module-switch-on-port-available ### Load audio drivers statically ### (it's probably better to not load these drivers manually, but instead ### use module-udev-detect -- see below -- for doing this automatically) #load-module module-alsa-sink #load-module module-alsa-source device=hw:1,0 #load-module module-oss device=/dev/dsp sink_name=output source_name=input #load-module module-oss-mmap device=/dev/dsp sink_name=output source_name=input #load-module module-null-sink #load-module module-pipe-sink ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif ### Automatically connect sink and source if JACK server is present .ifexists module-jackdbus-detect.so .nofail load-module module-jackdbus-detect channels=2 .fail .endif ### Automatically load driver modules for Bluetooth hardware .ifexists module-bluetooth-policy.so load-module module-bluetooth-policy .endif .ifexists module-bluetooth-discover.so load-module module-bluetooth-discover .endif ### Load several protocols .ifexists module-esound-protocol-unix.so load-module module-esound-protocol-unix .endif load-module module-native-protocol-unix ### Network access (may be configured with paprefs, so leave this commented ### here if you plan to use paprefs) #load-module module-esound-protocol-tcp #load-module module-native-protocol-tcp #load-module module-zeroconf-publish ### Load the RTP receiver module (also configured via paprefs, see above) #load-module module-rtp-recv ### Load the RTP sender module (also configured via paprefs, see above) #load-module module-null-sink
Bug#778235: [Pkg-libvirt-maintainers] Bug#778235: libvirt0: Migration drops elements from XML
On Thu, Feb 12, 2015 at 04:34:35PM +0100, Martin Sofaru wrote: On 12/02/15 16:02, Guido Günther wrote: On Thu, Feb 12, 2015 at 02:54:20PM +0100, Martin Sofaru wrote: Package: libvirt0 Version: 1.2.9-9 Severity: important Tags: patch Dear Maintainer, when migrating a VM the actual XML virsh dumpxml vm is copied to the target host. This drops important elements like portgroups out of a network configuration. You don't provide much information. Which elemnts are wrong for you (e.g. provide a diff and the original configuration). The origin XML (--inactive) looks like this: interface type='network' mac address='52:54:00:12:34:56'/ source network='ovs' portgroup='foo'/ target dev='bar'/ model type='virtio'/ driver name='vhost'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /interface After migration the origin XML (--inactive) becomes the same as the actual XML (without --inactive): interface type='bridge' mac address='52:54:00:12:34:56'/ source bridge='br0'/ virtualport type='openvswitch' parameters interfaceid='60cd8a2e-c182-44d1-b613-32a8a042bf9e'/ /virtualport target dev='bar'/ model type='virtio'/ driver name='vhost'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /interface The information about the portgroup is lost after migration! Did you check that the patch fixes your problem? No. I originally reported the issue to libvirt upstream and was told the issue was fixed with that commit. I am trying to verify if this single commit is enough to fix the issue. You can also try the version from experimental and see if it helps. If so we can try to isolate the fix for jessie (I'm currently lacking the time for any serious libvirt or Debian work though). Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777664: [Pkg-salt-team] Bug#777664: salt-minion: Make log file readable by adm group
Am Mittwoch, den 11.02.2015, 23:28 +1100 schrieb Joe Healy: On Wed, Feb 11, 2015 at 8:43 PM, Benjamin Drung benjamin.dr...@profitbricks.com wrote: A patch against your master branch is attached. debian/patches/make-log-file-group-readable.patch is a backport of the patch that was accepted upstream (in their develop branch). Should this also be done in the salt-master? Yes, maybe. The master log was created with mode 644. So I assume that chmod is not run on that files. = # ls /var/log/salt/ -al total 0 drwxr-s--- 2 root adm 60 Feb 12 18:10 . drwxr-xr-x 1 root root 120 Feb 12 18:10 .. -rw-r--r-- 1 root adm0 Feb 12 18:10 master = -- Benjamin Drung System Developer ProfitBricks GmbH - The IaaS-Company Greifswalder Str. 207 D - 10405 Berlin Mail: benjamin.dr...@profitbricks.com Fax: +49 30 577 008 598 URL: http://www.profitbricks.com Sitz der Gesellschaft: Berlin. Registergericht: Amtsgericht Charlottenburg, HRB 125506 B. Geschäftsführer: Andreas Gauger, Achim Weiss. signature.asc Description: This is a digitally signed message part
Bug#778253: libarchive13: archive_read_disk_entry_from_file() and archive_write_disk_set_acls() don't preserv ACL.
Package: libarchive13
Version: 3.1.2-11ghigo
Severity: normal
Tags: patch
libarchive in linux doesn't support properly the ACL. This is a bug alredy
solved in upstream [1][2].
The problem is that the code which handles ACLs depend by the definition
of the macro ACL_TYPE_NFS4. However in linux this macro is not defined.
During the packaging build, dpkg-shlibdeps warns abou the fact the the acl
library is unused:
---
dpkg-shlibdeps: warning: package could avoid a useless dependency if
debian/libarchive13/usr/lib/x86_64-linux-gnu/libarchive.so.13.1.2 was not
linked against libacl.so.1 (it uses none of the library's symbols)
---
In upstream the problem is solved by the patch [2]. Fedora
solved this issue cherry-picking the same patch [4].
I made a new version the libarchive package: I put the commit [2] in
debian/patches/, I update debian/patches/series adding the new patch,
and finally I updated the debian/changelog file. The package compiled and
now my tests showed ACL seems supported.
BR
G.Baroncelli
[1] https://code.google.com/p/libarchive/issues/detail?id=329
[2] See commit b45c3ae1825c8cedc7cde2972a04974f73b08315
[3] https://bugzilla.redhat.com/show_bug.cgi?id=993048
[4]
http://pkgs.fedoraproject.org/cgit/libarchive.git/commit/?id=da58d4e8afce6acca54475be528f6b948aa2951a
-- System Information:
Debian Release: 8.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf
Kernel: Linux 3.18.5 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages libarchive13 depends on:
ii libacl12.2.52-2
ii libattr1 1:2.4.47-2
ii libbz2-1.0 1.0.6-7+b2
ii libc6 2.19-15
ii liblzma5 5.1.1alpha+20120614-2+b3
ii liblzo2-2 2.08-1.2
ii libnettle4 2.7.1-5
ii libxml22.9.2+dfsg1-3
ii multiarch-support 2.19-15
ii zlib1g 1:1.2.8.dfsg-2+b1
libarchive13 recommends no packages.
Versions of packages libarchive13 suggests:
pn lrzip none
-- no debconf information
commit b45c3ae1825c8cedc7cde2972a04974f73b08315
Author: Tim Kientzle kient...@acm.org
Date: Sat Jan 4 21:46:57 2014 -0800
Issue #329: https://code.google.com/p/libarchive/issues/detail?id=329
Fix POSIX.1e draft ACL handling on Linux systems that lack NFSv4 ACL libraries.
diff --git a/libarchive/archive_read_disk_entry_from_file.c b/libarchive/archive_read_disk_entry_from_file.c
index e984aaa..e81cbec 100644
--- a/libarchive/archive_read_disk_entry_from_file.c
+++ b/libarchive/archive_read_disk_entry_from_file.c
@@ -399,7 +399,7 @@ setup_mac_metadata(struct archive_read_disk *a,
#endif
-#if defined(HAVE_POSIX_ACL) defined(ACL_TYPE_NFS4)
+#ifdef HAVE_POSIX_ACL
static int translate_acl(struct archive_read_disk *a,
struct archive_entry *entry, acl_t acl, int archive_entry_acl_type);
@@ -419,6 +419,7 @@ setup_acls(struct archive_read_disk *a,
archive_entry_acl_clear(entry);
+#ifdef ACL_TYPE_NFS4
/* Try NFS4 ACL first. */
if (*fd = 0)
acl = acl_get_fd(*fd);
@@ -447,6 +448,7 @@ setup_acls(struct archive_read_disk *a,
acl_free(acl);
return (ARCHIVE_OK);
}
+#endif
/* Retrieve access ACL from file. */
if (*fd = 0)
@@ -492,6 +494,7 @@ static struct {
{ARCHIVE_ENTRY_ACL_EXECUTE, ACL_EXECUTE},
{ARCHIVE_ENTRY_ACL_WRITE, ACL_WRITE},
{ARCHIVE_ENTRY_ACL_READ, ACL_READ},
+#ifdef ACL_TYPE_NFS4
{ARCHIVE_ENTRY_ACL_READ_DATA, ACL_READ_DATA},
{ARCHIVE_ENTRY_ACL_LIST_DIRECTORY, ACL_LIST_DIRECTORY},
{ARCHIVE_ENTRY_ACL_WRITE_DATA, ACL_WRITE_DATA},
@@ -508,8 +511,10 @@ static struct {
{ARCHIVE_ENTRY_ACL_WRITE_ACL, ACL_WRITE_ACL},
{ARCHIVE_ENTRY_ACL_WRITE_OWNER, ACL_WRITE_OWNER},
{ARCHIVE_ENTRY_ACL_SYNCHRONIZE, ACL_SYNCHRONIZE}
+#endif
};
+#ifdef ACL_TYPE_NFS4
static struct {
int archive_inherit;
int platform_inherit;
@@ -519,21 +524,25 @@ static struct {
{ARCHIVE_ENTRY_ACL_ENTRY_NO_PROPAGATE_INHERIT, ACL_ENTRY_NO_PROPAGATE_INHERIT},
{ARCHIVE_ENTRY_ACL_ENTRY_INHERIT_ONLY, ACL_ENTRY_INHERIT_ONLY}
};
-
+#endif
static int
translate_acl(struct archive_read_disk *a,
struct archive_entry *entry, acl_t acl, int default_entry_acl_type)
{
acl_tag_t acl_tag;
+#ifdef ACL_TYPE_NFS4
acl_entry_type_t acl_type;
acl_flagset_t acl_flagset;
+ int brand, r;
+#endif
acl_entry_t acl_entry;
acl_permset_t acl_permset;
- int brand, i, r, entry_acl_type;
+ int i, entry_acl_type;
int s, ae_id, ae_tag, ae_perm;
const char *ae_name;
+#ifdef ACL_TYPE_NFS4
// FreeBSD brands ACLs as POSIX.1e or NFSv4
// Make sure the brand on this ACL is consistent
// with the default_entry_acl_type bits provided.
@@ -560,6 +569,7 @@ translate_acl(struct archive_read_disk *a,
return ARCHIVE_FAILED;
break;
}
+#endif
s = acl_get_entry(acl,
Bug#778247: Please create debconf-in...@list.debian.org
Package: lists.debian.org Severity: wishlist X-Debbugs-Cc: debconf-t...@lists.debconf.org Name: debconf-in...@lists.debian.org Rationale: The DebConf infrastructure team has requested a new pseudo-package in the BTS for tracking issues related to summit.debconf.org, our conference management system. See bug #776982. As discussed there this list will serve as the maintainer address required to receive BTS mail. It will also be useful for team discussions that aren't appropriate for the debconf-team or debconf-video lists. Short Description: DebConf Infrastructure team. Long Description: DebConf Infrastructure team discussions and bug report handling. Category: DebConf Subscription Policy: Open Post Policy: Open Web Archive: Yes Thank you, Eric Rzewnicki (on behalf of DebConf Infrastructure team) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778248: libnewlib-dev: newlib-nano has a different newlib.h
Package: libnewlib-dev
Version: 2.1.0+git20141201.db59ff3-1
Severity: normal
Tags: patch
Dear Maintainer,
Code built against newlib-nano needs to use newlib-nano's version of
newlib.h, because things like the size and layout of struct _reent
are different.
There are two patches attached:
- The first copies newlib.h from the -nano build to
/usr/include/newlib/nano/newlib.h in the installed package, so that
it's available for use.
- The second adjusts the nano.specs file to add the appropriate
include path, so that #include newlib.h pulls in the
correct file for both cases (with/without -specs=nano.specs).
This is so that the user does not need to manually specify
the include path in their build.
I'm not very familiar with specs files, so there may be a better
way to handle that second case that avoids having to hardcode the
path.
The first patch is more important and only affects the debian/ dir,
the other might be better coordinated with upstream?
Jim
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (250, 'testing'), (200, 'stable'), (50, 'unstable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
libnewlib-dev depends on no packages.
libnewlib-dev recommends no packages.
Versions of packages libnewlib-dev suggests:
ii gcc-arm-none-eabi4.8.3-9+11
ii libnewlib-arm-none-eabi 2.1.0+git20141201.db59ff3-1
-- no debconf information
From 235fd4040650b5a3cdca018b089f63f5e34a87f5 Mon Sep 17 00:00:00 2001
From: Jim Paris j...@jtan.com
Date: Thu, 12 Feb 2015 12:30:44 -0500
Subject: [PATCH 1/2] Ship nano/newlib.h
---
debian/rules | 5 +
1 file changed, 5 insertions(+)
diff --git a/debian/rules b/debian/rules
index b234fe72be86..a0f2330ee4e3 100755
--- a/debian/rules
+++ b/debian/rules
@@ -100,6 +100,11 @@ override_dh_auto_install:
find $(TMP_NANO_DIR) -regex .*/lib\(c\|g\|rdimon\)\.a \
-exec rename 's@$(TMP_NANO_DIR)/(.*).a@$(TMP_DIR)/$$1_nano.a@' \{\} \+
#
+ # Move nano's version of newlib.h to nano/newlib.h
+ mkdir -p $(TMP_DIR)/usr/lib/$(TARGET)/include/nano
+ mv $(TMP_NANO_DIR)/usr/lib/$(TARGET)/include/newlib.h \
+ $(TMP_DIR)/usr/lib/$(TARGET)/include/nano/newlib.h
+ #
# Build newlib-source package
mkdir -p $(P_SRC)/usr/src/newlib
cp ../newlib_$(UVERSION).orig.tar.xz $(P_SRC)/usr/src/newlib/newlib-$(UVERSION).tar.xz
--
2.1.3
From bd495d655003eb97f143bb7bb19d05333046b7fb Mon Sep 17 00:00:00 2001
From: Jim Paris j...@jtan.com
Date: Thu, 12 Feb 2015 12:54:40 -0500
Subject: [PATCH 2/2] Add /usr/include/newlib/nano to search path in nano.specs
---
libgloss/arm/elf-nano.specs | 3 +++
1 file changed, 3 insertions(+)
diff --git a/libgloss/arm/elf-nano.specs b/libgloss/arm/elf-nano.specs
index 60dc407c678b..c96c57aee50b 100644
--- a/libgloss/arm/elf-nano.specs
+++ b/libgloss/arm/elf-nano.specs
@@ -1,5 +1,6 @@
%rename linknano_link
%rename link_gcc_c_sequencenano_link_gcc_c_sequence
+%rename cpp nano_cpp
*nano_libc:
-lc_nano
@@ -16,3 +17,5 @@
*lib:
%{!shared:%{g*:-lg_nano} %{!p:%{!pg:-lc_nano}}%{p:-lc_p}%{pg:-lc_p}}
+*cpp:
+-I/usr/include/newlib/nano %(nano_cpp)
--
2.1.3
Bug#778249: linux-tools-3.16: Please include the x86_energy_perf_policy and turbostat tool on x86
Package: linux-tools-3.16 Version: 3.16-3 Severity: wishlist Hi, Would it be possible to include the x86_energy_perf_policy and turbostat tool on x86 builds of linux-tools? It allows you to set the x86 performance policy of the CPU, and a tool to monitor the CPU states of recent intel processors. Regards, Rik -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-tools-3.16 depends on: ii libaudit1 1:2.4-1+b1 ii libc6 2.19-13 ii libdw10.159-4 ii libelf1 0.159-4 ii libnuma1 2.0.10-1 ii libperl5.20 5.20.1-5 ii libpython2.7 2.7.8-11 ii libslang2 2.3.0-2 ii libunwind81.1-3.2 ii perl 5.20.1-5 pn python:anynone Versions of packages linux-tools-3.16 recommends: ii linux-base 3.5 Versions of packages linux-tools-3.16 suggests: pn linux-doc-3.16 none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778251: linux-image-3.16.0-4-amd64: x86_energy_perf_policy of cpu0 switches to performance after suspend to ram
Package: src:linux Version: 3.16.7-ckt4-3 Severity: normal Hi, I was playing with the x86_energy_perf_policy tool to change the energy performance policy of the CPU. When the system boots, it indicates it has switched the CPU to the 'normal' perf_policy (from 'performance'). [0.011281] ENERGY_PERF_BIAS: Set to 'normal', was 'performance' ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8) When checked with the x86_energy_perf_policy tools, this looks OK: rik@earth:~/bin$ sudo ./x86_energy_perf_policy -v -r CPUID.06H.ECX: 0x9 cpu0: 0x0006 cpu1: 0x0006 cpu2: 0x0006 cpu3: 0x0006 6 seems to indicate 'normal' on my CPU. To check the values, I configured the CPU to enter 'normal': rik@earth:~/bin$ sudo ./x86_energy_perf_policy -v normal CPUID.06H.ECX: 0x9 cpu0 msr0x1b0 0x0006 - 0x0006 cpu1 msr0x1b0 0x0006 - 0x0006 cpu2 msr0x1b0 0x0006 - 0x0006 cpu3 msr0x1b0 0x0006 - 0x0006 For 'performance', the tool sets the msr to 0 at the end: rik@earth:~/bin$ sudo ./x86_energy_perf_policy -v performance CPUID.06H.ECX: 0x9 cpu0 msr0x1b0 0x0006 - 0x cpu1 msr0x1b0 0x0006 - 0x cpu2 msr0x1b0 0x0006 - 0x cpu3 msr0x1b0 0x0006 - 0x Now, when the system boots, all cpu's are correctly set to 'normal'. But when I suspend to RAM and wake the system again, cpu0's perf_policy is set to performance again. The other cpu's remain at the normal policy: rik@earth:~/bin$ sudo ./x86_energy_perf_policy -v -r CPUID.06H.ECX: 0x9 cpu0: 0x cpu1: 0x0006 cpu2: 0x0006 cpu3: 0x0006 It seems the perf_policy is not restored on resume for cpu0. My system has the following cpu: rik@earth:~/bin$ lscpu Architecture: x86_64 CPU op-mode(s):32-bit, 64-bit Byte Order:Little Endian CPU(s):4 On-line CPU(s) list: 0-3 Thread(s) per core:2 Core(s) per socket:2 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family:6 Model: 58 Model name:Intel(R) Core(TM) i5-3360M CPU @ 2.80GHz Stepping: 9 CPU MHz: 3433.390 CPU max MHz: 3500. CPU min MHz: 1200. BogoMIPS: 5581.57 Virtualization:VT-x L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 3072K NUMA node0 CPU(s): 0-3 Regards, Rik -- 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-ckt4-3 (2015-02-03) ** Command line: BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 root=/dev/mapper/vg_earth-root ro elevator=deadline quiet systemd.show_status=1 splash ** Not tainted ** Kernel log: [ 401.220242] pci :00:1f.3: using default PCI settings [ 401.220384] i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment [ 401.220402] ivb_uncore :00:00.0: no hotplug settings from platform [ 401.220407] ivb_uncore :00:00.0: using default PCI settings [ 401.220422] i915 :00:02.0: no hotplug settings from platform [ 401.220427] i915 :00:02.0: using default PCI settings [ 401.220442] xhci_hcd :00:14.0: no hotplug settings from platform [ 401.220447] xhci_hcd :00:14.0: using default PCI settings [ 401.220467] mei_me :00:16.0: no hotplug settings from platform [ 401.220472] mei_me :00:16.0: using default PCI settings [ 401.220489] e1000e :00:19.0: no hotplug settings from platform [ 401.220494] e1000e :00:19.0: using default PCI settings [ 401.220513] ehci-pci :00:1a.0: no hotplug settings from platform [ 401.220518] ehci-pci :00:1a.0: using default PCI settings [ 401.220537] snd_hda_intel :00:1b.0: no hotplug settings from platform [ 401.220548] pcieport :00:1c.0: no hotplug settings from platform [ 401.220559] pcieport :00:1c.1: no hotplug settings from platform [ 401.220600] pcieport :00:1c.2: no hotplug settings from platform [ 401.220610] pcieport :00:1c.3: no hotplug settings from platform [ 401.220620] pcieport :00:1c.5: no hotplug settings from platform [ 401.220668] ehci-pci :00:1d.0: no hotplug settings from platform [ 401.220673] ehci-pci :00:1d.0: using default PCI settings [ 401.220693] lpc_ich :00:1f.0: no hotplug settings from platform [ 401.220698] lpc_ich :00:1f.0: using default PCI settings [ 401.220717] ahci :00:1f.2: no hotplug settings from platform [ 401.220723] ahci :00:1f.2: using default PCI settings [ 401.220740] pci :00:1f.3: no hotplug settings from platform [ 401.220745] pci :00:1f.3: using default PCI settings [ 401.220790] i915 :00:02.0: BAR 6: [???
Bug#778252: RFS: pyoperators/0.13.5-1 -- Operators and solvers for high-performance computing.
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package pyoperators: * Package name: pyoperators Version : 0.13.5-1 Upstream Author : Pierre Chanial * URL :http://pchanial.github.io/pyoperators/ * License : CeCILL-B Programming Lang: Python Description : Operators and solvers for high-performance computing. It builds the following binary packages: python-pyoperators -- Python 2 version of the module python3-pyoperators -- Python 3 version of the module Changes since last upload: * New upstream release * d/copyright: cme fixed * d/control: cme fixed This package is currently maintained by the Debian Science Team and will be sponsored via the Sponsorship of Blends initiative [1]. The source package can be checked out at [2]. Cheers, Ghislain [1] https://wiki.debian.org/DebianPureBlends/SoB [2] https://anonscm.debian.org/cgit/debian-science/packages/pyoperators.git -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778254: release.debian.org: jessie's new kernel breaks openafs-modules-dkms
Package: release.debian.org Severity: normal Bug #778196 was filed against openafs-modules-dkms to note that the latest kernel to hit jessie (which was the unblock request in #776899) causes the DKMS module to fail to build. The new kernel introduced a KPI change for accesses to the d_alias field of struct dentry, which must now be made through the d_u union. I updated openafs in sid to include upstream's patches for new linux support (including the d_u change) when the new kernel hit sid, but that update also included a new translation and several bugfixes of various severity. Additionally, openafs in sid has a newer upstream version than openafs in jessie, due to excessive optimism on my part in the lead up to freeze. (It is also the case that nearly every upstream update for openafs includes support for new linux versions, since the KPI is a moving target, so I am used to having to pull in new upstream versions regularly.) The version in jessie also does not have native systemd support, and it remains unclear whether the systemd sysv compat is causing problems for jessie users that native unit files could resolve (#760063) -- for at least some users, the issue seems to have mysteriously gone away but there is no openafs or systemd change which obviously should have resolved things. The question is, how should we resolve the situation for jessie? It seems like the most likely answer is a minimal patch uploaded to testing-proposed-updates, but I wanted to ask the release team whether there were other options, such as unblocking the openafs currently in sid (even though it is a new upstream version). It is probably worth noting that openafs is a leaf package. -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777866: gcl: ftbfs with GCC-5
Is there a way to install gcc-5 into an experimental schroot on a porterbox? Take care, Matthias Klose d...@debian.org writes: Package: src:gcl Version: 2.6.12-1 Severity: normal Tags: sid stretch User: debian-...@lists.debian.org Usertags: ftbfs-gcc-5 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The severity of this report may be raised before the stretch release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc5-20150205/gcl_2.6.12-1_unstable_gcc5.log The last lines of the build log are at the end of this report. To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ Common build failures are C11 as the default C mode, new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html [...] num_sfun.c:(.text+0x9ffd): undefined reference to `number_fix_iexpt' num_sfun.c:(.text+0xa0c1): undefined reference to `number_ui_expt' num_sfun.c:(.text+0xa0d1): undefined reference to `number_ui_expt' num_sfun.c:(.text+0xa1ae): undefined reference to `number_fix_iexpt' num_sfun.c:(.text+0xa237): undefined reference to `number_ui_expt' num_sfun.c:(.text+0xa247): undefined reference to `number_ui_expt' num_sfun.c:(.text+0xab17): undefined reference to `number_zero_expt' num_sfun.c:(.text+0xab8e): undefined reference to `number_zero_expt' num_sfun.c:(.text+0xad19): undefined reference to `number_zero_expt' num_sfun.c:(.text+0xb399): undefined reference to `number_zero_expt' num_sfun.c:(.text+0xb461): undefined reference to `number_zero_expt' ./libpre_gcl.a(num_sfun.o):num_sfun.c:(.text+0xb52a): more undefined references to `number_zero_expt' follow ./libpre_gcl.a(gbc.o): In function `sgc_start': gbc.c:(.text+0x7583): undefined reference to `add_page_to_freelist' gbc.c:(.text+0x7650): undefined reference to `set_tm_maxpage' gbc.c:(.text+0x780e): undefined reference to `add_pages' gbc.c:(.text+0x8393): undefined reference to `set_tm_maxpage' ./libpre_gcl.a(gbc.o): In function `GBC': gbc.c:(.text+0x9ad5): undefined reference to `opt_maxpage' ./libpre_gcl.a(alloc.o): In function `alloc_object': alloc.c:(.text+0x8074): undefined reference to `alloc_after_turning_off_sgc' alloc.c:(.text+0x8f7c): undefined reference to `maybe_reallocate_page' alloc.c:(.text+0x94d0): undefined reference to `maybe_reallocate_page' alloc.c:(.text+0x99f9): undefined reference to `maybe_reallocate_page' ./libpre_gcl.a(alloc.o): In function `alloc_contblock': alloc.c:(.text+0xb93e): undefined reference to `alloc_after_turning_off_sgc' alloc.c:(.text+0xc162): undefined reference to `maybe_reallocate_page' alloc.c:(.text+0xcbcf): undefined reference to `maybe_reallocate_page' alloc.c:(.text+0xd79c): undefined reference to `maybe_reallocate_page' ./libpre_gcl.a(alloc.o): In function `alloc_relblock': alloc.c:(.text+0xefce): undefined reference to `alloc_after_turning_off_sgc' alloc.c:(.text+0xf7f2): undefined reference to `maybe_reallocate_page' alloc.c:(.text+0x1025f): undefined reference to `maybe_reallocate_page' alloc.c:(.text+0x10e2c): undefined reference to `maybe_reallocate_page' ./libpre_gcl.a(alloc.o): In function `make_cons': alloc.c:(.text+0x124c4): undefined reference to `alloc_after_turning_off_sgc' alloc.c:(.text+0x12c3d): undefined reference to `maybe_reallocate_page' alloc.c:(.text+0x14089): undefined reference to `maybe_reallocate_page' alloc.c:(.text+0x145b3): undefined reference to `maybe_reallocate_page' collect2: error: ld returned 1 exit status make[2]: *** [raw_pre_gcl_map] Error 1 makefile:171: recipe for target 'raw_pre_gcl_map' failed make[2]: Leaving directory '/«PKGBUILDDIR»/unixport' make[1]: *** [unixport/saved_pre_gcl] Error 2 makefile:71: recipe for target 'unixport/saved_pre_gcl' failed rm h/mcompdefs.h make[1]: Leaving directory '/«PKGBUILDDIR»' make: *** [build-gprof-stamp] Error 2 debian/rules:109: recipe for target 'build-gprof-stamp' failed dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 -- Camm Maguirec...@maguirefamily.org == The earth is but one country, and mankind its citizens. -- Baha'u'llah -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact
Bug#778253: Library version
I noticed only now that the library version reported is the 3.1.2-11ghigo. This is a my mistake. 3.1.2-11ghigo is the library which I rebuild with the patch. The problem is related to the 3.1.2-10. BR G.Baroncelli -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777743: ITP: wallpaperd -- X wallpaper changing daemon
* Gunnar Wolf gw...@gwolf.org [2015-02-12 12:23:29-0600] Dmitry Bogatov dijo [Thu, Feb 12, 2015 at 10:43:17AM +0300]: - why is this package useful/relevant? It follows unix way and manages wallpapers without connection to your DE, WM or anything. (...) if there are other packages providing similar functionality, how does it compare? Such functionality exists in GNOME and KDE, at least. But I know nothing similar for bare WM. I guess I do this the ugliest possible way, but my .xsession has: BGDIR=/home/gwolf/.backgrounds while /bin/true do feh --bg-max $BGDIR/$(xscreensaver-getimage-file $BGDIR) sleep 60 done Yes, it is more. Like per-workspace wallpapers and random change every X seconds. -- Best regards, Dmitry Bogatov kact...@gnu.org, Free Software supporter, esperantisto and netiquette guardian. GPG: 54B7F00D pgpgfjS0XnwdJ.pgp Description: PGP signature
Bug#776636: pulseaudio: uses bluetooth speakers for audio output immediately after connection - but I can't control the volume
I found a workaround for this bug: When I load the pulseaudio module module-switch-on-connect by adding this entry to /etc/pulse/default.pa load-module module-switch-on-connect I can control the volume of my bluetooth speakers immediately when they are connected. I don't understand why the speakers are even used for audio output when this module is not loaded… But there's no entry for example about module-switch-on-port-available in the PulseAudio documentation [1]. [1] http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Modules/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778255: clang-3.6: Error message in man pages
Package: clang-3.6 Version: 1:3.6~+rc2-2 Severity: normal The man page for clang-tblgen-3.6 starts with an error message: NAME clang-tblgen - manual page for clang-tblgen 3.6 DESCRIPTION ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.USAGE: clang-tblgen [options] input file Several other manpages from this package have the same problem. -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.18.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages clang-3.6 depends on: ii binutils 2.25-4 ii libc62.19-14 ii libc6-dev2.19-14 ii libclang-common-3.6-dev 1:3.6~+rc2-2 ii libclang1-3.61:3.6~+rc2-2 ii libedit2 3.1-20140620-2 ii libffi6 3.1-2+b2 ii libgcc-4.9-dev 4.9.2-10 ii libgcc1 1:4.9.2-10 ii libllvm3.6 1:3.6~+rc2-2 ii libobjc-4.9-dev 4.9.2-10 ii libstdc++-4.9-dev4.9.2-10 ii libstdc++6 4.9.2-10 ii libtinfo55.9+20140913-1+b1 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages clang-3.6 recommends: pn llvm-3.6-dev none ii python2.7.8-3 Versions of packages clang-3.6 suggests: pn clang-3.6-doc none pn gnustepnone pn gnustep-devel none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778070: [Pkg-postgresql-public] Bug#778070: postgresql-9.1: ftbfs with GCC-5
Control: tag -1 +confirmed -stretch Re: Matthias Klose 2015-02-12 e1ylr7f-0001iz...@paradis.debian.org Package: src:postgresql-9.1 Version: 9.1.15-0+deb8u1 Severity: normal Tags: sid stretch User: debian-...@lists.debian.org Usertags: ftbfs-gcc-5 The package fails to build in a test rebuild on at least amd64 with gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The severity of this report may be raised before the stretch release. Hi, thanks for the report, confirmed here. Looks like initdb is filling up the disk until it panics because there's no space left. It affects PostgreSQL 9.5devel as well. Fwiw, postgresql-9.1 won't be part of stretch, it is a perl- compatibility package for upgrades from wheezy to jessie and will be removed as soon as jessie is released. Christoph -- c...@df7cb.de | http://www.df7cb.de/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755437: leocad suggests ldraw-parts since 0.80.3-1
Nicolas, the leocad package suggests ldraw-parts since 0.80.3-1 which should fix the issue about the minimal parts set (apt-get install leocad --install-suggests). Concerning the parts not being visible, I cannot reproduce that error. Is it still a problem? Best regards Nicolas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778246: ITP: prokka -- rapid annotation of prokaryotic genomes
Package: wnpp Severity: wishlist Owner: Debian Med team debian-...@lists.debian.org X-Debbugs-Cc: debian-de...@lists.debian.org, debian-...@lists.debian.org * Package name: prokka Version : 1.10 Upstream Author : Torsten Seemann torsten.seem...@monash.edu * URL : http://www.vicbioinformatics.com/software.prokka.shtml * License : GPL-3+, CC0-1, CC-BY-ND-3 Programming Lang: Perl Description : rapid annotation of prokaryotic genomes A typical 4 Mbp genome can be fully annotated in less than 10 minutes on a quad-core computer, and scales well to 32 core SMP systems. It produces GFF3, GBK and SQN files that are ready for editing in Sequin and ultimately submitted to Genbank/DDJB/ENA. Prokka is a popular bioinformatics program. It will be team maintained by the Debian Med team.
Bug#777743: ITP: wallpaperd -- X wallpaper changing daemon
Dmitry Bogatov dijo [Thu, Feb 12, 2015 at 10:43:17AM +0300]: - why is this package useful/relevant? It follows unix way and manages wallpapers without connection to your DE, WM or anything. (...) if there are other packages providing similar functionality, how does it compare? Such functionality exists in GNOME and KDE, at least. But I know nothing similar for bare WM. I guess I do this the ugliest possible way, but my .xsession has: BGDIR=/home/gwolf/.backgrounds while /bin/true do feh --bg-max $BGDIR/$(xscreensaver-getimage-file $BGDIR) sleep 60 done I guess there's more to wallpaperd than this, right? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777694: ITA: icu -- Development utilities for International Components for Unicode
On Thu, Feb 12, 2015 at 4:50 PM, j...@debian.org wrote: It would be great if you (or any co-maintainer) would initially take care of the open icu security issues in jessie/sid (with a minimal upload to sid + unblock request to the release team): That's what I'd like to do. The problem is that upstream doesn't support the version in Jessie anymore and thus I'll have to backport all those security fixes. Regards, Laszlo/GCS -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777080: crashed when trying to load plugins
Package: gwenview Version: 4:4.8.4-2 Severity: normal Dear Maintainer, I tried various different permutations of packages installed. Gwenview still crashes as before, but only on the one computer, which is a Time computer. Gwenview works on an old Packard Bell EasyNote. I have obtained a backtrace from my Time computer. I attach a copy. The following system information applies to the latest run. with best regards from Richard Betham -- System Information: Debian Release: 7.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i586) Kernel: Linux 3.2.0-4-486 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gwenview depends on: ii kde-runtime4:4.8.4-2 ii libc6 2.13-38+deb7u7 ii libexiv2-120.23-1 ii libgcc11:4.7.2-5 ii libjpeg8 8d-1+deb7u1 ii libkdecore54:4.8.4-4+deb7u1 ii libkdeui5 4:4.8.4-4+deb7u1 ii libkfile4 4:4.8.4-4+deb7u1 ii libkio54:4.8.4-4+deb7u1 ii libkipi8 4:4.8.4-1 ii libkonq5abi1 4:4.8.4-2 ii libkparts4 4:4.8.4-4+deb7u1 ii libnepomuk44:4.8.4-4+deb7u1 ii libphonon4 4:4.6.0.0-3 ii libqt4-opengl 4:4.8.2+dfsg-11 ii libqt4-svg 4:4.8.2+dfsg-11 ii libqtcore4 4:4.8.2+dfsg-11 ii libqtgui4 4:4.8.2+dfsg-11 ii libstdc++6 4.7.2-5 ii phonon 4:4.6.0.0-3 Versions of packages gwenview recommends: ii kamera 4:4.8.4-2 Versions of packages gwenview suggests: pn svgpart none -- no debconf information Versions of packages kipi-plugins depends on: ii digikam 4:2.6.0-1+deb7u1 ii kde-runtime 4:4.8.4-2 ii kipi-plugins-common 4:2.6.0-1+deb7u1 ii libc6 2.13-38+deb7u7 ii libexpat1 2.1.0-1+deb7u1 ii libgcc1 1:4.7.2-5 ii libgl1-mesa-glx [libgl1] 8.0.5-4+deb7u2 ii libglib2.0-0 2.33.12+really2.32.4-5 ii libgomp1 4.7.2-5 ii libgpod4-nogtk0.8.2-7 ii libjpeg8 8d-1+deb7u1 ii libkcalcore4 4:4.8.4-2 ii libkdcraw20 4:4.8.4-1 ii libkdecore5 4:4.8.4-4+deb7u1 ii libkdeui5 4:4.8.4-4+deb7u1 ii libkexiv2-10 4:4.8.4-1 ii libkio5 4:4.8.4-4+deb7u1 ii libkipi8 4:4.8.4-1 ii libksane0 4:4.8.4-1 ii libopencv-core2.3 2.3.1-11 ii libopencv-highgui2.3 2.3.1-11 ii libopencv-imgproc2.3 2.3.1-11 ii libopencv-legacy2.3 2.3.1-11 ii libopencv-objdetect2.32.3.1-11 ii libphonon44:4.6.0.0-3 ii libpng12-01.2.49-1 ii libqca2 2.0.3-4 ii libqjson0 0.7.1-7 ii libqt4-dbus 4:4.8.2+dfsg-11 ii libqt4-network4:4.8.2+dfsg-11 ii libqt4-opengl 4:4.8.2+dfsg-11 ii libqt4-svg4:4.8.2+dfsg-11 ii libqt4-xml4:4.8.2+dfsg-11 ii libqt4-xmlpatterns4:4.8.2+dfsg-11 ii libqtcore44:4.8.2+dfsg-11 ii libqtgui4 4:4.8.2+dfsg-11 ii libsolid4 4:4.8.4-4+deb7u1 ii libstdc++64.7.2-5 ii libthreadweaver4 4:4.8.4-4+deb7u1 ii libtiff4 3.9.6-11 ii libxml2 2.8.0+dfsg1-7+wheezy3 ii libxrandr22:1.3.2-2+deb7u1 ii libxslt1.11.1.26-14.1 ii phonon4:4.6.0.0-3 Versions of packages kipi-plugins recommends: ii enblend 4.0+dfsg-4+b3 ii enfuse 4.0+dfsg-4+b3 ii hugin2011.4.0+dfsg-5 ii imagemagick 8:6.7.7.10-5+deb7u3 ii konqueror4:4.8.4-2 Versions of packages kipi-plugins suggests: pn gallery none pn gimp none ii kmail 4:4.4.11.1+l10n-3+b1 pn vorbis-tools none -- no debconf information On Thursday 05 February 2015 12:39:22 Debian Bug Tracking System wrote: Thank you for the additional information you have supplied regarding this Bug report. Application: Gwenview (gwenview), signal: Illegal instruction Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0xb4463720 (LWP 6341))] Thread 3 (Thread 0xb1f14b70 (LWP 6343)): #0 0xb5108edf in pthread_mutex_lock () from /lib/i386-linux-gnu/libpthread.so.0 #1 0xb5b7ec76 in pthread_mutex_lock () from /lib/i386-linux-gnu/libc.so.6 #2 0xb507f940 in g_mutex_lock () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb503f8c5 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb503fb51 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0xb71ab84f in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #6 0xb717801c in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #7 0xb7178311 in
Bug#778250: powerline: leaks environment into build (makes unreproducible and possible privacy breach)
Source: powerline Version: 1.2-2 Severity: normal User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps fileordering Hello, While working on the “reproducible builds” effort [1], we have noticed that powerline could not be built reproducibly and it leaks the users environment into the resulting binary package when building. The environment appears in the file ../usr/share/doc/python-powerline-doc/html/develop/extensions.html which is generated from powerline/renderer.py line 47. Since the environment is different between different users this makes the package unreproducible. It might also leak sensitive data the user happens to have in their environment into the package build. Maybe the environment dump should be filtered? What is the reason for it being stored in segment_info in the first place? What is the purpose of storing the value of $HOME during the package build in the member 'home'? If these values are important for the operation of the package then they have to be kept but they should not be included with their values during the package build in the sphinx documentation. Cheers, akira [1]: https://wiki.debian.org/ReproducibleBuilds -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778196: Fails to built with current Jessie's kernel
Package: openafs-modules-dkms Version: 1.6.9-2 Severity: critical Dear maintainers, openafs-modules-dkms can not compile with linux-headers-3.16.0-4-amd64 version 3.16.7-ckt4-3. With the previous Jessies's kernel (version 3.16.7-ckt2-1) there was no problem. Here is the message when trying to dpkg-reconfigure openafs-modules-dkms: Uninstall Beginning Module: openafs Version: 1.6.9 Kernel: 3.16.0-4-amd64 (x86_64) - Status: Before uninstall, this module version was ACTIVE on this kernel. openafs.ko: - Uninstallation - Deleting from: /lib/modules/3.16.0-4-amd64/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. depmod DKMS: uninstall completed. -- Deleting module version: 1.6.9 completely from the DKMS tree. -- Done. Loading new openafs-1.6.9 DKMS files... Building only for 3.16.0-4-amd64 Building initial module for 3.16.0-4-amd64 Error! Bad return status for module build on kernel: 3.16.0-4-amd64 (x86_64) Consult /var/lib/dkms/openafs/1.6.9/build/make.log for more information. The make.log file mentionned above is attached. Thanks for your time and work, Yvan Masson DKMS make.log for openafs-1.6.9 for kernel 3.16.0-4-amd64 (x86_64) jeudi 12 février 2015, 12:47:46 (UTC+0100) checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes /var/lib/dkms/openafs/1.6.9/build/build-tools/missing: Unknown `--is-lightweight' option Try `/var/lib/dkms/openafs/1.6.9/build/build-tools/missing --help' for more information configure: WARNING: 'missing' script is too old or missing checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking whether gcc understands -c and -o together... yes checking for style of include used by make... GNU checking dependency style of gcc... none checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for flex... no checking for lex... no checking for pkg-config... no checking for libxslt... no checking for saxon... no checking for xalan-j... no checking for xsltproc... no checking for docbook2pdf... no checking for dblatex... no checking for library containing strerror... none required checking for pid_t... yes checking for size_t... yes checking whether ln -s works... yes checking for ranlib... ranlib checking for bison... no checking for byacc... no checking if lex is flex... no checking whether byte order is known at compile time... yes checking whether byte ordering is bigendian... no checking whether printf understands the %z length modifier... yes checking your OS... linux checking if gcc accepts -march=pentium... no checking if gcc needs -fno-strength-reduce... yes checking if gcc needs -fno-strict-aliasing... yes checking if gcc supports -fno-common... yes checking if gcc supports -pipe... yes checking if linux kbuild requires EXTRA_CFLAGS... yes checking for linux kernel module build works... yes checking for linux/config.h... no checking for linux/completion.h... yes checking for linux/exportfs.h... yes checking for linux/freezer.h... yes checking for linux/key-type.h... yes checking for linux/semaphore.h... yes checking for linux/seq_file.h... yes checking for struct vfs_path... no checking for kuid_t... yes checking for write_begin in struct address_space_operations... yes checking for name in struct backing_dev_info... yes checking for session_keyring in struct cred... yes checking for ctl_name in struct ctl_table... no checking for d_automount in struct dentry_operations... yes checking for i_alloc_sem in struct inode... no checking for i_blkbits in struct inode... yes checking for i_blksize in struct inode... no checking for i_mutex in struct inode... yes checking for i_security in struct inode... yes checking for flock in struct file_operations...
Bug#778200: netmaze: please make the build reproducible
Source: netmaze Version: 0.81+jpg0.82-14.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 netmaze could not be built reproducibly. The attached patch removes timestamps from the build system. Once applied, netmaze can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff -urNad netmaze.orig/netmaze-0.81+jpg0.82/debian/rules netmaze/netmaze-0.81+jpg0.82/debian/rules --- netmaze.orig/netmaze-0.81+jpg0.82/debian/rules 2015-02-12 02:54:29.816460710 + +++ netmaze/netmaze-0.81+jpg0.82/debian/rules 2015-02-12 02:56:20.640435910 + @@ -53,7 +53,7 @@ cp debian/changelog debian/tmp/usr/share/doc/$(PACKAGENAME)/changelog.Debian cp README.Debian CREDITS README TODO debian/tmp/usr/share/doc/$(PACKAGENAME) cp CHANGES debian/tmp/usr/share/doc/$(PACKAGENAME)/changelog - gzip -9vr debian/tmp/usr/share/doc/$(PACKAGENAME) + gzip -9nvr debian/tmp/usr/share/doc/$(PACKAGENAME) cp debian/copyright debian/tmp/usr/share/doc/$(PACKAGENAME)/copyright cp debian/menu debian/tmp/usr/lib/menu/netmaze dpkg-shlibdeps debian/tmp/usr/games/netmaze \
Bug#778201: netris: please make the build reproducible
Source: netris Version: 0.52-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 netris could not be built reproducibly. The attached patch removes timestamps from the build system. Once applied, netris can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff -urNad netris.orig/netris-0.52/debian/rules netris/netris-0.52/debian/rules --- netris.orig/netris-0.52/debian/rules2015-02-12 02:55:23.618388633 + +++ netris/netris-0.52/debian/rules 2015-02-12 02:56:02.971801113 + @@ -64,7 +64,7 @@ $(INSTALL_FILE) debian/netris*.6 $(TMP)/usr/share/man/man6 $(INSTALL_FILE) FAQ robot_desc $(TMP)/usr/share/doc/$(PKG) $(INSTALL_FILE) sr.c $(TMP)/usr/share/doc/$(PKG)/examples - gzip -9 $(TMP)/usr/share/man/man6/netris*.6 \ + gzip -9n $(TMP)/usr/share/man/man6/netris*.6 \ $(TMP)/usr/share/doc/$(PKG)/FAQ \ $(TMP)/usr/share/doc/$(PKG)/robot_desc \ $(TMP)/usr/share/doc/$(PKG)/examples/sr.c @@ -86,7 +86,7 @@ $(TMP)/usr/share/doc/$(PKG) $(INSTALL_FILE) debian/changelog \ $(TMP)/usr/share/doc/$(PKG)/changelog.Debian - gzip -9 $(TMP)/usr/share/doc/$(PKG)/changelog.Debian + gzip -9n $(TMP)/usr/share/doc/$(PKG)/changelog.Debian $(INSTALL_SCRIPT) debian/postinst debian/postrm \ $(TMP)/DEBIAN dpkg-shlibdeps -Tdebian/substvars -dDepends \
Bug#778203: original-awk: please make the build reproducible
Source: original-awk Version: 2012-12-20-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 original-awk could not be built reproducibly. The attached patch removes timestamps from the build system. Once applied, original-awk can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff -urNad original-awk.orig/original-awk-2012-12-20/debian/rules original-awk/original-awk-2012-12-20/debian/rules --- original-awk.orig/original-awk-2012-12-20/debian/rules 2015-02-12 02:56:59.945849458 + +++ original-awk/original-awk-2012-12-20/debian/rules 2015-02-12 02:57:44.335448148 + @@ -36,10 +36,10 @@ install -m 644 debian/changelog $(docdir)/changelog.Debian install -m 644 awk.1 debian/tmp/usr/share/man/man1/$(package).1 cp -p README FIXES debian/copyright $(docdir) - cd $(docdir) gzip -9 FIXES changelog.Debian + cd $(docdir) gzip -9n FIXES changelog.Debian ln -s FIXES.gz $(docdir)/changelog.gz $(STRIP) debian/tmp/usr/bin/* - gzip -r9 debian/tmp/usr/share/man/man1 + gzip -r9n debian/tmp/usr/share/man/man1 dpkg-shlibdeps debian/tmp/usr/bin/* dpkg-gencontrol cd debian/tmp \
Bug#778199: mod-authn-webid: please make the build reproducible
Source: mod-authn-webid Version: 0~20110301-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 mod-authn-webid could not be built reproducibly. The attached patch removes timestamps from the build system. Once applied, mod-authn-webid can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff -urNad mod-authn-webid.orig/mod-authn-webid-0~20110301/debian/rules mod-authn-webid/mod-authn-webid-0~20110301/debian/rules --- mod-authn-webid.orig/mod-authn-webid-0~20110301/debian/rules 2015-02-12 02:49:24.413588457 + +++ mod-authn-webid/mod-authn-webid-0~20110301/debian/rules 2015-02-12 02:50:16.011416583 + @@ -29,7 +29,7 @@ $(INSTALL_FILE) debian/authn_webid.load $(CURDIR)/debian/$(package)/etc/apache2/mods-available $(INSTALL_FILE) debian/copyright debian/$(package)/usr/share/doc/$(package)/copyright $(INSTALL_FILE) debian/changelog debian/$(package)/usr/share/doc/$(package)/changelog.Debian - gzip -9f `find debian/$(package)/usr/share/man -type f` `find debian/$(package)/usr/share/doc -type f ! -name copyright` + gzip -9nf `find debian/$(package)/usr/share/man -type f` `find debian/$(package)/usr/share/doc -type f ! -name copyright` ifeq (,$(findstring nostrip,$(DEB_BUILD_OPTIONS))) strip --remove-section=.comment --remove-section=.note \ --strip-unneeded debian/$(package)/usr/lib/apache2/modules/*.so
Bug#778202: newmail: please make the build reproducible
Source: newmail Version: 0.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 newmail could not be built reproducibly. The attached patch removes timestamps from the build system. Once applied, newmail can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff -urNad newmail.orig/newmail-0.5/debian/rules newmail/newmail-0.5/debian/rules --- newmail.orig/newmail-0.5/debian/rules 2015-02-12 02:55:35.226805079 + +++ newmail/newmail-0.5/debian/rules2015-02-12 02:56:38.089063184 + @@ -60,7 +60,7 @@ $(installbin) -d debian/tmp/usr/share/doc/$(package) $(installdoc) debian/changelog debian/tmp/usr/share/doc/$(package)/changelog.Debian $(installdoc) debian/copyright debian/tmp/usr/share/doc/$(package) - gzip -9f debian/tmp/usr/share/doc/$(package)/changelog.Debian + gzip -9nf debian/tmp/usr/share/doc/$(package)/changelog.Debian # $(installdoc) AUTHORS debian/tmp/usr/share/doc/$(package) $(installdoc) README debian/tmp/usr/share/doc/$(package) @@ -70,7 +70,7 @@ $(MAKE) prefix=debian/tmp/usr install $(installbin) $(STRIP) newmail debian/tmp/usr/bin # - gzip -9f debian/tmp/usr/share/man/man1/newmail.1 + gzip -9nf debian/tmp/usr/share/man/man1/newmail.1 # dpkg-shlibdeps debian/tmp/usr/bin/newmail dpkg-gencontrol -isp
Bug#774928: ITP: libcoap -- library for the CoAP protocol written in C
On Fri, Jan 09, 2015 at 09:33:10AM +0100, Carsten Schoenert wrote: Currently the upstream source is lacking some minor tweaks like versioning of the library and also symbol versioning. The build environment is improvable. I'm in contact with Olaf Bergmann to improve the situation here. The current state on the rework of the build environment can be found on my Github page within a local copy of the upstream tree in the branch '4upstream'. https://github.com/tijuca/libcoap/tree/4upstream But note, I'm offen rebasing this branch because I work from various PCs on the projects and using the Github service to interchange my work! If you have some critisim and/or you are willing to help please contact me! Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777751: efi-reader: x32 port
Package: efi-reader
Version: 0.14
Severity: wishlist
Tags: d-i patch
Hi!
Please apply the attached patch. It adds support for the x32 architecture.
The patch is trivial -- all that needed to be done is adding x32 to
debian/control. The patch can be applied directly to the d-i/efi-reader git
repository.
If you want to test, as the patch-set for x32 in d-i involves around twenty
packages, you'll want ready packages from the repository at debian-x32.org.
Complete d-i isos are available at http://debian-x32.org/#debian-installer
while debs/udebs/modified sources at http://ftp.debian-x32.org/debian/
-- System Information:
Debian Release: 8.0
APT prefers unstable
APT policy: (600, 'unstable'), (500, 'unreleased'), (50, 'experimental')
Architecture: x32 (x86_64)
Kernel: Linux 3.19.0-x32 (SMP w/6 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
From bb723d009d35a5a3048c13129d88a688825c6b70 Mon Sep 17 00:00:00 2001
From: Adam Borowski kilob...@angband.pl
Date: Thu, 12 Feb 2015 07:29:01 +0100
Subject: [PATCH] Add x32 to the list of architectures.
---
debian/control | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/debian/control b/debian/control
index 2396049..42926e7 100644
--- a/debian/control
+++ b/debian/control
@@ -8,7 +8,7 @@ Vcs-Browser: http://anonscm.debian.org/gitweb/?p=d-i/efi-reader.git
Vcs-Git: git://anonscm.debian.org/d-i/efi-reader.git
Package: efi-reader
-Architecture: ia64 amd64 i386 arm64 armhf
+Architecture: ia64 amd64 i386 arm64 armhf x32
Depends: ${shlibs:Depends}
Description: Select default values from EFI configuration.
Package-Type: udeb
--
2.1.4
Bug#777757: unblock: wss4j/1.6.15-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package wss4j, the version 1.6.15-2 fixes two security issues
(#41).
Thank you
unblock wss4j/1.6.15-2
dpkg-source: warning: extracting unsigned source package
(/home/ebourg/packaging/wss4j_1.6.15-2.dsc)
diff -Nru wss4j-1.6.15/debian/changelog wss4j-1.6.15/debian/changelog
--- wss4j-1.6.15/debian/changelog 2014-04-07 06:52:38.0 +0200
+++ wss4j-1.6.15/debian/changelog 2015-02-12 09:55:30.0 +0100
@@ -1,3 +1,14 @@
+wss4j (1.6.15-2) unstable; urgency=medium
+
+ * Fixed security issues (Closes: #41):
+ - CVE-2015-0227: WSS4J is still vulnerable to Bleichenbacher's attack
+ (incomplete fix for CVE-2011-2487)
+ - CVE-2015-0226: WSS4J doesn't correctly enforce the
+ requireSignedEncryptedDataElements property
+ * Standards-Version updated to 3.9.6 (no changes)
+
+ -- Emmanuel Bourg ebo...@apache.org Thu, 12 Feb 2015 09:11:29 +0100
+
wss4j (1.6.15-1) unstable; urgency=medium
* New upstream release
diff -Nru wss4j-1.6.15/debian/control wss4j-1.6.15/debian/control
--- wss4j-1.6.15/debian/control 2014-02-26 10:08:52.0 +0100
+++ wss4j-1.6.15/debian/control 2015-02-12 09:12:08.0 +0100
@@ -12,9 +12,9 @@
libxalan2-java,
libxml-security-java
Build-Depends: ant, cdbs (= 0.4.5.3), debhelper (= 9), maven-debian-helper
-Standards-Version: 3.9.5
+Standards-Version: 3.9.6
Vcs-Git: git://anonscm.debian.org/pkg-java/wss4j.git
-Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-java/wss4j.git
+Vcs-Browser: http://anonscm.debian.org/cgit/pkg-java/wss4j.git
Homepage: http://ws.apache.org/wss4j/
Package: libwss4j-java
diff -Nru wss4j-1.6.15/debian/patches/02-CVE-2015-0227.patch
wss4j-1.6.15/debian/patches/02-CVE-2015-0227.patch
--- wss4j-1.6.15/debian/patches/02-CVE-2015-0227.patch 1970-01-01
01:00:00.0 +0100
+++ wss4j-1.6.15/debian/patches/02-CVE-2015-0227.patch 2015-02-12
09:38:54.0 +0100
@@ -0,0 +1,137 @@
+Description: Fix CVE-2015-0227: WSS4J is still vulnerable to Bleichenbacher's
attack (incomplete fix for CVE-2011-2487)
+Origin: backport, http://svn.apache.org/r1619359
+Bug-Debian: http://bugs.debian.org/41
+---
a/src/main/java/org/apache/ws/security/processor/EncryptedDataProcessor.java
b/src/main/java/org/apache/ws/security/processor/EncryptedDataProcessor.java
+@@ -91,7 +91,7 @@
+ );
+
+ if (elem != null request.isRequireSignedEncryptedDataElements()) {
+-WSSecurityUtil.verifySignedElement(elem, elem.getOwnerDocument(),
wsDocInfo.getSecurityHeader());
++WSSecurityUtil.verifySignedElement(elem, wsDocInfo);
+ }
+
+ SecretKey key = null;
+--- a/src/main/java/org/apache/ws/security/processor/EncryptedKeyProcessor.java
b/src/main/java/org/apache/ws/security/processor/EncryptedKeyProcessor.java
+@@ -403,7 +403,7 @@
+ Element encryptedDataElement =
+ ReferenceListProcessor.findEncryptedDataElement(doc, docInfo,
dataRefURI);
+ if (encryptedDataElement != null
data.isRequireSignedEncryptedDataElements()) {
+-WSSecurityUtil.verifySignedElement(encryptedDataElement, doc,
docInfo.getSecurityHeader());
++WSSecurityUtil.verifySignedElement(encryptedDataElement, docInfo);
+ }
+ //
+ // Prepare the SecretKey object to decrypt EncryptedData
+---
a/src/main/java/org/apache/ws/security/processor/ReferenceListProcessor.java
b/src/main/java/org/apache/ws/security/processor/ReferenceListProcessor.java
+@@ -132,7 +132,7 @@
+ Element encryptedDataElement = findEncryptedDataElement(doc,
wsDocInfo, dataRefURI);
+
+ if (encryptedDataElement != null asymBinding
data.isRequireSignedEncryptedDataElements()) {
+-WSSecurityUtil.verifySignedElement(encryptedDataElement, doc,
wsDocInfo.getSecurityHeader());
++WSSecurityUtil.verifySignedElement(encryptedDataElement,
wsDocInfo);
+ }
+ //
+ // Prepare the SecretKey object to decrypt EncryptedData
+--- a/src/main/java/org/apache/ws/security/util/WSSecurityUtil.java
b/src/main/java/org/apache/ws/security/util/WSSecurityUtil.java
+@@ -24,6 +24,7 @@
+ import org.apache.ws.security.SOAPConstants;
+ import org.apache.ws.security.WSConstants;
+ import org.apache.ws.security.WSDataRef;
++import org.apache.ws.security.WSDocInfo;
+ import org.apache.ws.security.WSEncryptionPart;
+ import org.apache.ws.security.WSSecurityEngineResult;
+ import org.apache.ws.security.WSSecurityException;
+@@ -50,10 +51,8 @@
+ import java.security.SecureRandom;
+ import java.util.ArrayList;
+ import java.util.Collections;
+-import java.util.HashSet;
+ import java.util.Iterator;
+ import java.util.List;
+-import java.util.Set;
+
+ /**
+ * WS-Security Utility methods. p/
+@@ -1350,56 +1349,39 @@
+ }
+ }
+
+-
Bug#777759: linux-image-3.16.0-4-amd64: When I use bluetooth speakers for audio output Wi-Fi stops working
Package: src:linux Version: 3.16.7-ckt4-3 Severity: normal Dear Maintainer, often when I use my bluetooth speakers for audio output, my Wi-Fi connection becomes unusable slow. When I stop the playback and wait a few seconds I can use Wi-Fi again. The Wi-Fi connection never breaks completely, I stay connected but I can't even send or receive e-mails. I'm affected by this bug on an HP Folio 13-2000 notebook with an Intel Corporation Centrino Wireless-N 1030 [Rainbow Peak] [8086:008b] adapter. Since I can't reproduce it with another notebook using the same WLAN and the same bluetooth speakers I guess it's hardware related. -- 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-ckt4-3 (2015-02-03) ** Command line: BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 root=/dev/mapper/rosa-root ro quiet splash ** Not tainted ** Kernel log: [ 154.133125] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 154.755897] wlan0: authenticate with 70:72:3c:20:76:08 [ 154.766082] wlan0: send auth to 70:72:3c:20:76:08 (try 1/3) [ 154.768436] wlan0: authenticated [ 154.769119] wlan0: associate with 70:72:3c:20:76:08 (try 1/3) [ 154.773148] wlan0: RX AssocResp from 70:72:3c:20:76:08 (capab=0x431 status=0 aid=2) [ 154.782186] wlan0: associated [ 154.782236] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 154.782302] cfg80211: Calling CRDA for country: CA [ 154.785394] cfg80211: Regulatory domain changed to country: CA [ 154.785399] cfg80211: DFS Master region: FCC [ 154.785402] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 154.785406] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 3000 mBm), (N/A) [ 154.785410] cfg80211: (517 KHz - 525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 1700 mBm), (N/A) [ 154.785415] cfg80211: (525 KHz - 533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2400 mBm), (0 s) [ 154.785419] cfg80211: (549 KHz - 573 KHz @ 16 KHz), (N/A, 2400 mBm), (0 s) [ 154.785422] cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 3000 mBm), (N/A) [ 161.990013] usb 1-1.2: new full-speed USB device number 6 using ehci-pci [ 162.182647] usb 1-1.2: New USB device found, idVendor=8086, idProduct=0189 [ 162.182651] usb 1-1.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 172.073227] input: 00:02:3C:49:93:08 as /devices/virtual/input/input17 [ 662.130063] tun: Universal TUN/TAP device driver, 1.6 [ 662.130068] tun: (C) 1999-2004 Max Krasnyansky m...@qualcomm.com [ 1727.831947] usb 2-2: new high-speed USB device number 2 using xhci_hcd [ 1727.961783] usb 2-2: New USB device found, idVendor=1058, idProduct=1100 [ 1727.961792] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1727.961797] usb 2-2: Product: My Book [ 1727.961801] usb 2-2: Manufacturer: Western Digital [ 1727.961806] usb 2-2: SerialNumber: 57442D574341563530313235303133 [ 1727.979956] usb-storage 2-2:1.0: USB Mass Storage device detected [ 1727.980136] scsi6 : usb-storage 2-2:1.0 [ 1727.980368] usbcore: registered new interface driver usb-storage [ 1728.980093] scsi 6:0:0:0: Direct-Access WD 10EADS External 1.75 PQ: 0 ANSI: 4 [ 1728.980932] sd 6:0:0:0: Attached scsi generic sg1 type 0 [ 1728.981261] sd 6:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [ 1728.981599] sd 6:0:0:0: [sdb] Write Protect is off [ 1728.981605] sd 6:0:0:0: [sdb] Mode Sense: 23 00 00 00 [ 1728.982050] sd 6:0:0:0: [sdb] No Caching mode page found [ 1728.982057] sd 6:0:0:0: [sdb] Assuming drive cache: write through [ 1729.003049] sdb: sdb1 [ 1729.005054] sd 6:0:0:0: [sdb] Attached SCSI disk [ 1729.861553] sha256_ssse3: Using AVX optimized SHA-256 implementation [ 1730.112760] EXT4-fs (dm-4): warning: maximal mount count reached, running e2fsck is recommended [ 1730.121083] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null) [ 2192.334964] usb 2-2: USB disconnect, device number 2 [ 2192.603577] usb 2-2: new high-speed USB device number 3 using xhci_hcd [ 2192.733304] usb 2-2: New USB device found, idVendor=1058, idProduct=1100 [ 2192.733314] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2192.733319] usb 2-2: Product: My Book [ 2192.733323] usb 2-2: Manufacturer: Western Digital [ 2192.733327] usb 2-2: SerialNumber: 57442D574341563530313235303133 [ 2192.734329] usb-storage 2-2:1.0: USB Mass Storage device detected [ 2192.734651] scsi7 : usb-storage 2-2:1.0 [ 2193.364260] usb 2-2: USB disconnect, device number 3 [ 3213.427171] input: 00:02:3C:49:93:08 as /devices/virtual/input/input18 [ 3375.406780] Loading kernel module for a network device with CAP_SYS_MODULE (deprecated). Use CAP_NET_ADMIN and alias netdev- instead. [ 4851.734371] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [
Bug#778194: partman-auto: x32 port
Package: partman-auto Version: 124 Severity: wishlist Tags: d-i patch User: debian-...@lists.debian.org Usertags: port-x32 di-x32 Hi! Please apply the attached git patch (via git am). It adds support for the x32 architecture, by linking recipes-x32-efi to recipes-amd64-efi. The patch can be applied directly to the d-i/partman-auto git repository. If you want to test, as the patch-set for x32 in d-i involves around twenty packages, you'll want ready packages from the repository at debian-x32.org. Complete d-i isos are available at http://debian-x32.org/#debian-installer while debs/udebs/modified sources at http://ftp.debian-x32.org/debian/ -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (600, 'unstable'), (500, 'unreleased'), (50, 'experimental') Architecture: x32 (x86_64) Kernel: Linux 3.19.0-x32 (SMP w/6 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776839: unblock: libgit2/0.21.3-1.1
On 11 February 2015 at 23:24, Russell Sim russell@gmail.com wrote: On 9 February 2015 at 09:36, Mehdi Dogguy me...@dogguy.org wrote: I'm afraid we cannot accept 0.21.3-1.1 in Jessie because the changes are quite large. Can you please prepare an upload targetting jessie based on 0.21.1-2.1? Thanks for looking at this. I have created a patch that backport the relevant changes to the 0.21.1-2.1 I have reduced the patch removing any Win32 parts. -- Cheers, Russell Sim diff -Nru libgit2-0.21.1/debian/changelog libgit2-0.21.1/debian/changelog --- libgit2-0.21.1/debian/changelog 2015-01-09 09:51:34.0 +1100 +++ libgit2-0.21.1/debian/changelog 2015-02-12 20:06:00.0 +1100 @@ -1,3 +1,10 @@ +libgit2 (0.21.1-3) jessie; urgency=medium + + * Backported fix for case insensitive filesystems (CVE-2014-9390). +(Closes: #774048) + + -- Russell Sim russell@gmail.com Tue, 10 Feb 2015 20:29:05 +1100 + libgit2 (0.21.1-2.1) jessie; urgency=medium * Non-maintainer upload. diff -Nru libgit2-0.21.1/debian/patches/CVE-2014-9390.patch libgit2-0.21.1/debian/patches/CVE-2014-9390.patch --- libgit2-0.21.1/debian/patches/CVE-2014-9390.patch 1970-01-01 10:00:00.0 +1000 +++ libgit2-0.21.1/debian/patches/CVE-2014-9390.patch 2015-02-12 20:06:00.0 +1100 @@ -0,0 +1,1479 @@ +commit a86d224d78a3ac0f8a1901b0e9e2aee1e15d6f73 +Author: Edward Thomson ethom...@microsoft.com +Date: Thu Dec 18 12:41:59 2014 -0600 + +index tests: test capitalization before mkdir + +commit 86b9eb3bf5dba342d0a5d805e6fe35c3e9c861cc +Author: Carlos Martín Nieto c...@dwim.me +Date: Thu Dec 18 02:11:06 2014 +0100 + +Plug leaks + +commit 07164371d10109ba564835947a62fcedf288dce9 +Author: Carlos Martín Nieto c...@dwim.me +Date: Thu Dec 18 02:07:36 2014 +0100 + +Create miscapitialised dirs for case-sensitive filesystems + +We need these directories to exist so cl_git_mkfile() can create the +files we ask it to. + +commit 5d5d6136aaeea22903ed5d30a858f8d106876771 +Author: Edward Thomson ethom...@microsoft.com +Date: Tue Dec 16 18:53:55 2014 -0600 + +Introduce core.protectHFS and core.protectNTFS + +Validate HFS ignored char .git paths when `core.protectHFS` is +specified. Validate NTFS invalid .git paths when `core.protectNTFS` +is specified. + +commit 2698e209d895856df9900899948269e2e490abd3 +Author: Vicent Marti tan...@gmail.com +Date: Tue Dec 16 13:03:02 2014 +0100 + +path: Use UTF8 iteration for HFS chars + +commit d7026dc574b79723008bba72989f74a801f4dfb5 +Author: Edward Thomson ethom...@microsoft.com +Date: Wed Dec 10 19:12:16 2014 -0500 + +checkout: disallow bad paths on HFS + +HFS filesystems ignore some characters like U+200C. When these +characters are included in a path, they will be ignored for the +purposes of comparison with other paths. Thus, if you have a .git +folder, a folder of .gitU+200C will also match. Protect our +.git folder by ensuring that .gitU+200C and friends do not match it. + +commit 37221f8cb02554297710f703047711a61e1169bb +Author: Edward Thomson ethom...@microsoft.com +Date: Tue Nov 25 18:13:00 2014 -0500 + +checkout: disallow bad paths on win32 + +Disallow: + 1. paths with trailing dot + 2. paths with trailing space + 3. paths with trailing colon + 4. paths that are 8.3 short names of .git folders (GIT~1) + 5. paths that are reserved path names (COM1, LPT1, etc). + 6. paths with reserved DOS characters (colons, asterisks, etc) + +These paths would (without \\?\ syntax) be elided to other paths - for +example, .git. would be written as .git. As a result, writing these +paths literally (using \\?\ syntax) makes them hard to operate with from +the shell, Windows Explorer or other tools. Disallow these. + +commit cb6a309d8667310d3323f5b601a2f2fa893c37d0 +Author: Vicent Marti tan...@gmail.com +Date: Tue Nov 25 00:58:03 2014 +0100 + +index: Check for valid paths before creating an index entry + +commit 928a41d189f068010a32c6dea4bf921baa81d21c +Author: Vicent Marti tan...@gmail.com +Date: Tue Nov 25 00:14:52 2014 +0100 + +tree: Check for `.git` with case insensitivy + +commit f45baf7a94a75cfb1855c9a750f38bbcfa22b199 +Author: Edward Thomson ethom...@microsoft.com +Date: Mon Dec 1 13:09:58 2014 -0500 + +win32: use NT-prefixed \\?\ paths + +When turning UTF-8 paths into UCS-2 paths for Windows, always use +the \\?\-prefixed paths. Because this bypasses the system's +path canonicalization, handle the canonicalization functions ourselves. + +We must: + 1. always use a backslash as a directory separator + 2. only use a single backslash between directories + 3. not rely on the system to translate . and .. in paths + 4. remove trailing backslashes, except at the drive root (C:\) + +commit 2e37e214e3d85da2a68476c7ae54051d525b05eb +Author: Edward Thomson ethom...@microsoft.com
Bug#601178: gpointing-device-settings: forgets setting within minutes
Package: gpointing-device-settings Version: 1.5.1-6 Followup-For: Bug #601178 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I have the same bug in jessie using MATE desktop. I want to turn off the touchpad and only use the ThinkPad trackpoint. The touchpad is re-enabled after some time, which is bad because Lenovo's modern touchpads really suck. Is there any movement in this bug, or any other way to configure the touchpad? - -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gpointing-device-settings depends on: ii gconf2 3.2.6-3 ii libatk1.0-0 2.14.0-1 ii libc6 2.19-15 ii libcairo2 1.14.0-2.1 ii libdbus-1-3 1.8.16-1 ii libdbus-glib-1-20.102-1 ii libfontconfig1 2.11.0-6.3 ii libfreetype62.5.2-2 ii libgconf2-4 3.2.6-3 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-02.42.1-1 ii libgpds01.5.1-6 ii libgtk2.0-0 2.24.25-1 ii libpango1.0-0 1.36.8-3 ii libxi6 2:1.7.4-1+b2 gpointing-device-settings recommends no packages. gpointing-device-settings suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQJOBAEBCAA4BQJU3IRdMRpodHRwczovL3d3dy5kb21pbmlrLWdlb3JnZS5kZS9n cGctcG9saWN5LnR4dC5hc2MACgkQt5o8FqDE8pbT1A/+ORjdUWAdIKVvzyaligKk fogaD32ODNT+nLHBJlgbePBzuhOhCKDMrOYQ1wczeW3HPpsi21Mqt9R8BMaUtOAM CwQ7f6ATXROGW9evsiPE5vQl3buYd5lr3cPZb/nwK+kNvQ1dW4kGKaHRMC6P29kX TWGVExzM9oxVD+ez1cZOB8jpD1UIORqChwog8FrvRzvb9Ouq+hfUcgcHV3IauGU6 UVvx70imHUx/DYzez7Zu0EyZsm5humGxW/55UmPb/XlRWYuZva7S+EyO1FHq+i89 ZG360NkVz/F5oNZQGb78WlhiXZ1wboOULIceLZz0VGVTAFzb7zoI161xz8IxyYqG 598H3a9X/O5/9De/NimT7WAa0NrCVJEc7yhNHWIx1P8vd5ireHwqUALO34Pfngcc qIGJJccA/wZFjDLVVI1ZyiZ6+xsumzrAU+weTg6FBCJGuSvktmh4W9Bc8l4Fq3Vi Mud/KTfAfu7Qbepnw23ciLl8DxzDGFl3tA4HFPM8Zlexf0PqlZfGj7pjJb+M8uFb FldsaXDbhZiRjJHUen4GSTNmEvvPzdkJC1d2+NMGVseQwyk3IbkUA800x+GJm41V ibt+BlkRqd1omBe53S0mt1oJAlZ8VNOEjfn6HCLWtqX1xaF0BgJzHEhAR1ScaDj3 REWqoDQjjYhYdTeh0TB5zkk= =A4j+ -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#777760: apt: fails to satisfy dependencies of the form package:arch with arch being the native architecture
Package: apt Version: 1.0.9.6 Severity: normal Hi, apt in unstable/jessie fails to satisfy binary dependencies of the form package:arch if arch happens to be the native architecture. steps to reproduce: $ sudo debootstrap --variant=minbase sid debian-sid http://127.0.0.1:3142/http.debian.net/debian $ sudo mkdir debian-sid/repository $ cat END | sudo tee debian-sid/repository/Packages /dev/null Package: foo Version: 1.0 Architecture: amd64 Depends: blub:amd64 Package: blub Version: 1.0 Architecture: amd64 END $ echo deb file:/repository ./ | sudo tee -a debian-sid/etc/apt/sources.list /dev/null $ sudo chroot debian-sid apt-get update $ sudo chroot debian-sid apt-get install -o Debug::pkgProblemResolver=true -o Debug::pkgDepCache::Marker=1 -o Debug::pkgDepCache::AutoInstall=1 foo Reading package lists... Done Building dependency tree... Done foo:amd64 Depends on blub:amd64 [ amd64 ] none ( none ) can't be satisfied! Starting pkgProblemResolver with broken count: 1 Starting 2 pkgProblemResolver with broken count: 1 Investigating (0) foo [ amd64 ] none - 1.0 ( unknown ) Broken foo:amd64 Depends on blub:amd64 [ amd64 ] none ( none ) Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: foo : Depends: blub:amd64 but it is not installable E: Unable to correct problems, you have held broken packages. On the other hand it works with foreign architectures (at least as far as the resolver seems to be concerned - it only fails on the missing Filename: field): $ sudo chroot debian-sid dpkg --add-architecture i386 $ cat END | sudo tee debian-sid/repository/Packages /dev/null Package: foo Version: 1.0 Architecture: amd64 Depends: blub:i386 Package: blub Version: 1.0 Architecture: i386 END $ sudo chroot debian-sid apt-get update $ sudo chroot debian-sid apt-get install -o Debug::pkgProblemResolver=true -o Debug::pkgDepCache::Marker=1 -o Debug::pkgDepCache::AutoInstall=1 foo Reading package lists... Done Building dependency tree... Done MarkInstall foo [ amd64 ] none - 1.0 ( unknown ) FU=1 Installing blub as Depends of foo MarkInstall blub [ i386 ] none - 1.0 ( unknown ) FU=0 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done The following extra packages will be installed: blub:i386 The following NEW packages will be installed: blub:i386 foo 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. E: The package index files are corrupted. No Filename: field for package blub. Lets try experimental apt: $ echo deb http://127.0.0.1:3142/http.debian.net/debian experimental main | sudo tee -a debian-sid/etc/apt/sources.list /dev/null $ sudo chroot debian-sid apt-get update $ sudo chroot debian-sid apt-get install -t experimental apt $ cat END | sudo tee debian-sid/repository/Packages /dev/null Package: foo Version: 1.0 Architecture: amd64 Depends: blub:amd64 Package: blub Version: 1.0 Architecture: amd64 END $ sudo chroot debian-sid apt-get update $ sudo chroot debian-sid apt-get install -o Debug::pkgProblemResolver=true -o Debug::pkgDepCache::Marker=1 -o Debug::pkgDepCache::AutoInstall=1 foo Reading package lists... Done Building dependency tree Reading state information... Done MarkInstall foo [ amd64 ] none - 1.0 ( unknown ) FU=1 Installing blub as Depends of foo MarkInstall blub [ amd64 ] none - 1.0 ( unknown ) FU=0 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done The following extra packages will be installed: blub The following NEW packages will be installed: blub foo 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. E: The package index files are corrupted. No Filename: field for package blub. So gladly this is only a problem with apt unstable/jessie but not in experimental. cheers, josch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact
Bug#778015: mpd: ftbfs with GCC-5
On 2015/02/12 11:34, Matthias Klose d...@debian.org wrote: src/output/plugins/ShoutOutputPlugin.cxx: In member function 'bool ShoutOutput::Configure(const config_param, Error)': src/output/plugins/ShoutOutputPlugin.cxx:112:10: error: converting to 'bool' from 'std::nullptr_t' requires direct-initialization [-fpermissive] This problem has been fixed in upstream 0.19.9. Please consider including the latest bug-fix release in the upcoming Debian stable. It fixes a lot of bugs compared to 0.19.1, including a few nasty crash bugs. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778197: lpe: please make the build reproducible
Source: lpe
Version: 1.2.7-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 lpe could not be built reproducibly.
The attached patch removes timestamps from the build system. Once
applied, lpe can be built reproducibly in our current experimental
framework.
[1]: https://wiki.debian.org/ReproducibleBuilds
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
diff -urNad lpe.orig/lpe-1.2.7/debian/rules lpe/lpe-1.2.7/debian/rules
--- lpe.orig/lpe-1.2.7/debian/rules 2015-02-12 02:53:51.891103929 +
+++ lpe/lpe-1.2.7/debian/rules 2015-02-12 02:55:49.251308432 +
@@ -73,8 +73,8 @@
strip --remove-section=.comment --remove-section=.note $(find-binaries)
endif
# compress stuff
- find ${PKGDIR}/usr/share/man/ -type f | xargs gzip -9f
- gzip -9f ${PKGDIR}/usr/share/doc/${PACKAGE}/changelog \
+ find ${PKGDIR}/usr/share/man/ -type f | xargs gzip -9nf
+ gzip -9nf ${PKGDIR}/usr/share/doc/${PACKAGE}/changelog \
${PKGDIR}/usr/share/doc/${PACKAGE}/changelog.Debian \
${PKGDIR}/usr/share/doc/${PACKAGE}/BUGS \
${PKGDIR}/usr/share/doc/${PACKAGE}/CUSTOMIZE \
Bug#778206: xblast-tnt-images: please make the build reproducible
Source: xblast-tnt-images Version: 20050106-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 xblast-tnt-images could not be built reproducibly. The attached patch removes timestamps from the build system. Once applied, xblast-tnt-images can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff -urNad xblast-tnt-images.orig/xblast-tnt-images-20050106/debian/rules xblast-tnt-images/xblast-tnt-images-20050106/debian/rules --- xblast-tnt-images.orig/xblast-tnt-images-20050106/debian/rules 2015-02-12 05:37:07.252417316 + +++ xblast-tnt-images/xblast-tnt-images-20050106/debian/rules 2015-02-12 05:37:59.806447398 + @@ -55,7 +55,7 @@ $(TMP)/usr/share/doc/$(PKG)/changelog.Debian $(INSTALL_FILE) debian/copyright \ $(TMP)/usr/share/doc/$(PKG) - gzip -9 $(TMP)/usr/share/doc/$(PKG)/changelog.Debian + gzip -9n $(TMP)/usr/share/doc/$(PKG)/changelog.Debian dpkg-gencontrol -isp -p$(PKG) -P$(TMP) cd $(TMP) find * -type f ! -regex '^DEBIAN/.*' -print0 | \ xargs -r0 md5sum DEBIAN/md5sums
Bug#778208: xblast-tnt-models: please make the build reproducible
Source: xblast-tnt-models Version: 20050106-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 xblast-tnt-models could not be built reproducibly. The attached patch removes timestamps from the build system. Once applied, xblast-tnt-models can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff -urNad xblast-tnt-models.orig/xblast-tnt-models-20050106/debian/rules xblast-tnt-models/xblast-tnt-models-20050106/debian/rules --- xblast-tnt-models.orig/xblast-tnt-models-20050106/debian/rules 2015-02-12 05:37:30.517315811 + +++ xblast-tnt-models/xblast-tnt-models-20050106/debian/rules 2015-02-12 05:38:25.843453751 + @@ -45,7 +45,7 @@ $(TMP)/usr/share/doc/$(PKG)/changelog.Debian $(INSTALL_FILE) debian/copyright \ $(TMP)/usr/share/doc/$(PKG) - gzip -9 $(TMP)/usr/share/doc/$(PKG)/changelog.Debian + gzip -9n $(TMP)/usr/share/doc/$(PKG)/changelog.Debian dpkg-gencontrol -isp -p$(PKG) -P$(TMP) cd $(TMP) find * -type f ! -regex '^DEBIAN/.*' -print0 | \ xargs -r0 md5sum DEBIAN/md5sums
Bug#778205: rockdodger: please make the build reproducible
Source: rockdodger Version: 1.0.0-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 rockdodger could not be built reproducibly. The attached patch removes timestamps from the build system. Once applied, rockdodger can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff -urNad rockdodger.orig/rockdodger-1.0.0/debian/patches/make.diff rockdodger/rockdodger-1.0.0/debian/patches/make.diff --- rockdodger.orig/rockdodger-1.0.0/debian/patches/make.diff 2015-02-12 02:58:43.001564667 + +++ rockdodger/rockdodger-1.0.0/debian/patches/make.diff2015-02-12 03:01:21.571305918 + @@ -23,7 +23,7 @@ chmod g+rw $(gamesdir)/rockdodger.scores mkdir -p $(mandir)/man6 - gzip $(MANPAGE) $(mandir)/man6/$(MANPAGE).gz -+ gzip -9 $(MANPAGE) $(mandir)/man6/$(MANPAGE).gz ++ gzip -9n $(MANPAGE) $(mandir)/man6/$(MANPAGE).gz uninstall: rm -f $(gamesdir)/rockdodger.scores diff -urNad rockdodger.orig/rockdodger-1.0.0/debian/rules rockdodger/rockdodger-1.0.0/debian/rules --- rockdodger.orig/rockdodger-1.0.0/debian/rules 2015-02-12 02:58:43.001564667 + +++ rockdodger/rockdodger-1.0.0/debian/rules2015-02-12 02:59:35.219452014 + @@ -46,7 +46,7 @@ install -D -p -m 0644 rockdodger.desktop debian/tmp/usr/share/applications/rockdodger.desktop install -D -p -m 0644 debian/changelog debian/tmp/usr/share/doc/rockdodger/changelog.Debian - gzip -9 debian/tmp/usr/share/doc/rockdodger/changelog.Debian + gzip -9n debian/tmp/usr/share/doc/rockdodger/changelog.Debian install -p -m 0644 debian/copyright debian/tmp/usr/share/doc/rockdodger install -d -m 0755 debian/tmp/DEBIAN diff -urNad rockdodger.orig/rockdodger-1.0.0/Makefile rockdodger/rockdodger-1.0.0/Makefile --- rockdodger.orig/rockdodger-1.0.0/Makefile 2015-02-12 02:58:43.013565094 + +++ rockdodger/rockdodger-1.0.0/Makefile2015-02-12 03:01:24.055396094 + @@ -107,7 +107,7 @@ -chgrp games $(gamesdir)/rockdodger.scores chmod g+rw $(gamesdir)/rockdodger.scores mkdir -p $(mandir)/man6 - gzip -9 $(MANPAGE) $(mandir)/man6/$(MANPAGE).gz + gzip -9n $(MANPAGE) $(mandir)/man6/$(MANPAGE).gz uninstall: rm -f $(gamesdir)/rockdodger.scores
Bug#778204: ratfor: please make the build reproducible
Source: ratfor Version: 1.0-15 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 ratfor could not be built reproducibly. The attached patch removes timestamps from the build system. Once applied, ratfor can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff -urNad ratfor.orig/ratfor-1.0/debian/rules ratfor/ratfor-1.0/debian/rules --- ratfor.orig/ratfor-1.0/debian/rules 2015-02-12 02:57:31.102971326 + +++ ratfor/ratfor-1.0/debian/rules 2015-02-12 02:58:10.088376731 + @@ -55,7 +55,7 @@ install -d -o root -g root -m 755 debian/tmp/usr/share/man/man1 install -o root -g root -m 644 ratfor.1 debian/tmp/usr/share/man/man1 - gzip -9f debian/tmp/usr/share/man/man1/ratfor.1 + gzip -9nf debian/tmp/usr/share/man/man1/ratfor.1 install -d -o root -g root -m 755 debian/tmp/usr/share/doc/$(package) install -o root -g root -m 644 BUGS\ debian/tmp/usr/share/doc/$(package) @@ -66,12 +66,12 @@ install -d -o root -g root -m 755 debian/tmp/usr/share/doc/$(package)/examples install -o root -g root -m 644 *.r \ debian/tmp/usr/share/doc/$(package)/examples - gzip -9f debian/tmp/usr/share/doc/$(package)/examples/*.r + gzip -9nf debian/tmp/usr/share/doc/$(package)/examples/*.r install -d -o root -g root -m 755 debian/tmp/DEBIAN install -c -m 0644 debian/changelog \ debian/tmp/usr/share/doc/$(package)/changelog.Debian - gzip -9 debian/tmp/usr/share/doc/$(package)/changelog.Debian + gzip -9n debian/tmp/usr/share/doc/$(package)/changelog.Debian dpkg-shlibdeps ./ratfor dpkg-gencontrol -isp dh_md5sums --tmpdir=debian/tmp
Bug#778210: xblast-tnt-sounds: please make the build reproducible
Source: xblast-tnt-sounds Version: 20040429-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 xblast-tnt-sounds could not be built reproducibly. The attached patch removes timestamps from the build system. Once applied, xblast-tnt-sounds can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff -urNad xblast-tnt-sounds.orig/xblast-tnt-sounds-20040429/debian/rules xblast-tnt-sounds/xblast-tnt-sounds-20040429/debian/rules --- xblast-tnt-sounds.orig/xblast-tnt-sounds-20040429/debian/rules 2015-02-12 05:37:47.809983863 + +++ xblast-tnt-sounds/xblast-tnt-sounds-20040429/debian/rules 2015-02-12 05:38:39.879996437 + @@ -45,7 +45,7 @@ $(TMP)/usr/share/doc/$(PKG)/changelog.Debian $(INSTALL_FILE) debian/copyright \ $(TMP)/usr/share/doc/$(PKG) - gzip -9 $(TMP)/usr/share/doc/$(PKG)/changelog.Debian + gzip -9n $(TMP)/usr/share/doc/$(PKG)/changelog.Debian dpkg-gencontrol -isp -p$(PKG) -P$(TMP) cd $(TMP) find * -type f ! -regex '^DEBIAN/.*' -print0 | \ xargs -r0 md5sum DEBIAN/md5sums
Bug#778207: xblast-tnt-levels: please make the build reproducible
Source: xblast-tnt-levels Version: 20050106-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 xblast-tnt-levels could not be built reproducibly. The attached patch removes timestamps from the build system. Once applied, xblast-tnt-levels can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff -urNad xblast-tnt-levels.orig/xblast-tnt-levels-20050106/debian/rules xblast-tnt-levels/xblast-tnt-levels-20050106/debian/rules --- xblast-tnt-levels.orig/xblast-tnt-levels-20050106/debian/rules 2015-02-12 05:37:15.276727181 + +++ xblast-tnt-levels/xblast-tnt-levels-20050106/debian/rules 2015-02-12 05:38:10.694868208 + @@ -47,7 +47,7 @@ $(TMP)/usr/share/doc/$(PKG)/changelog.Debian $(INSTALL_FILE) debian/copyright \ $(TMP)/usr/share/doc/$(PKG) - gzip -9 $(TMP)/usr/share/doc/$(PKG)/changelog.Debian + gzip -9n $(TMP)/usr/share/doc/$(PKG)/changelog.Debian dpkg-gencontrol -isp -p$(PKG) -P$(TMP) cd $(TMP) find * -type f ! -regex '^DEBIAN/.*' -print0 | \ xargs -r0 md5sum DEBIAN/md5sums
Bug#777762: wiki.debian.org: path separator must be /, not . in sysfs.conf
Package: wiki.debian.org Severity: normal In https://wiki.debian.org/SSDOptimization: echo block.sdX.queue.scheduler = deadline /etc/sysfs.conf is wrong. This results Setting sysfs variables...unknown attribute block.sda.queue.scheduler ... failed! in syslog. Must be: echo block/sdX/queue/scheduler = deadline /etc/sysfs.conf -- -- Name: SATOH Fumiyasu @ OSS Technology Corp. (fumiyas @ osstech co jp) -- Business Home: http://www.OSSTech.co.jp/ -- GitHub Home: https://GitHub.com/fumiyas/ -- PGP Fingerprint: BBE1 A1C9 525A 292E 6729 CDEC ADC2 9DCA 5E1C CBCA -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777761: RFP: ruby-trocla -- Create and store (random) passwords on a central server which can be retrieved by other applications.
Package: wnpp Severity: wishlist * Package name: ruby-trocla Version : 0.0.12 Upstream Author : Marcel Haerry mh+tro...@immerda.ch * URL : https://github.com/duritong/trocla * License : GPL Programming Lang: Ruby Description : Create and store (random) passwords on a central server which can be retrieved by other applications. Trocla provides you a simple way to create and store (random) passwords on a central server, which can be retrieved by other applications. An example for such an application is puppet and trocla can help you to not store any plaintext or hashed passwords in your manifests by keeping these passwords only on your puppetmaster. Furthermore it provides you a simple cli that helps you to modify the password storage from the cli. In concert with its puppet module it provides a very elegant way to generate random but from then on fixed passwords for use on possibly multiple puppet clients on the fly and store them in a reasonably secure way on the server. I hope that since trocla is available as a gem, packaging effort will be minimal by using gem2deb. I can help in packaging and maintaining via the Debian Ruby team if desired. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778195: debian-installer: x32 port
Package: debian-installer Version: 20150108 Severity: wishlist Tags: d-i patch User: debian-...@lists.debian.org Usertags: port-x32 di-x32 Hi! Here's the main part for x32 support in d-i. This patch is rather big, but as it doesn't touch non-x32 parts (save for a single comment), it should be safe to apply. It's in the form of a git am patch, to ease patching. If you want to test, as the patch-set for x32 in d-i involves around twenty packages, you'll want ready packages from the repository at debian-x32.org. Complete d-i isos are available at http://debian-x32.org/#debian-installer while debs/udebs/modified sources at http://ftp.debian-x32.org/debian/ By the way, if you'd want to apply all patches to the d-i/ repository in one go, daughter bug reports are: #48 grub-installer #49 lilo-installer #51 efi-reader #52 partman-efi #58 partman-partitioning #777905 base-installer #778194 partman-auto As for d-i related bugs in other sources, the usertag is: https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-...@lists.debian.org;tag=di-x32 -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (600, 'unstable'), (500, 'unreleased'), (50, 'experimental') Architecture: x32 (x86_64) Kernel: Linux 3.19.0-x32 (SMP w/6 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) From d9ace554fa6716e8ecb5647475ced4475ea741aa Mon Sep 17 00:00:00 2001 From: Adam Borowski kilob...@angband.pl Date: Thu, 12 Feb 2015 08:10:53 +0100 Subject: [PATCH] Add x32 support. --- build/config/x32.cfg | 25 ++ build/config/x32/cdrom-xen.cfg | 14 ++ build/config/x32/cdrom.cfg | 7 + build/config/x32/cdrom/el-torito.cfg | 7 + build/config/x32/cdrom/gtk.cfg | 17 build/config/x32/cdrom/isolinux.cfg| 14 ++ build/config/x32/hd-media.cfg | 22 build/config/x32/hd-media/gtk.cfg | 16 build/config/x32/monolithic.cfg| 9 +++ build/config/x32/netboot-gtk.cfg | 23 build/config/x32/netboot-xen.cfg | 16 build/config/x32/netboot.cfg | 12 + build/config/x86.cfg | 2 +- build/pkg-lists/cdrom/isolinux/gtk/x32.cfg | 8 ++ build/pkg-lists/cdrom/isolinux/x32.cfg | 12 + build/pkg-lists/cdrom/x32.cfg | 25 ++ build/pkg-lists/hd-media/gtk/x32.cfg | 10 +++ build/pkg-lists/hd-media/x32.cfg | 32 +++ build/pkg-lists/netboot/gtk/x32.cfg| 10 +++ build/pkg-lists/netboot/x32.cfg| 42 ++ debian/control | 30 ++--- 21 files changed, 337 insertions(+), 16 deletions(-) create mode 100644 build/config/x32.cfg create mode 100644 build/config/x32/cdrom-xen.cfg create mode 100644 build/config/x32/cdrom.cfg create mode 100644 build/config/x32/cdrom/el-torito.cfg create mode 100644 build/config/x32/cdrom/gtk.cfg create mode 100644 build/config/x32/cdrom/isolinux.cfg create mode 100644 build/config/x32/hd-media.cfg create mode 100644 build/config/x32/hd-media/gtk.cfg create mode 100644 build/config/x32/monolithic.cfg create mode 100644 build/config/x32/netboot-gtk.cfg create mode 100644 build/config/x32/netboot-xen.cfg create mode 100644 build/config/x32/netboot.cfg create mode 100644 build/pkg-lists/cdrom/isolinux/gtk/x32.cfg create mode 100644 build/pkg-lists/cdrom/isolinux/x32.cfg create mode 100644 build/pkg-lists/cdrom/x32.cfg create mode 100644 build/pkg-lists/hd-media/gtk/x32.cfg create mode 100644 build/pkg-lists/hd-media/x32.cfg create mode 100644 build/pkg-lists/netboot/gtk/x32.cfg create mode 100644 build/pkg-lists/netboot/x32.cfg diff --git a/build/config/x32.cfg b/build/config/x32.cfg new file mode 100644 index 000..62df865 --- /dev/null +++ b/build/config/x32.cfg @@ -0,0 +1,25 @@ +MEDIUM_SUPPORTED = cdrom cdrom-xen netboot netboot-gtk netboot-xen hd-media +MEDIUM_SUPPORTED_EXTRA = monolithic + +# The version of the kernel to use. +KERNELVERSION = $(LINUX_KERNEL_ABI)-amd64 +KERNELMAJOR = 2.6 +KERNELNAME = vmlinuz + +# Not used for amd64. +#UPX=upx-ucl-beta + +# Default syslinux configuration +SYSLINUX_CFG=standard + +# The default video modes +# These should be kept in sync with win32-loader's preseed line as +# defined in graphics.nsi around line 58 +VIDEO_MODE=vga=788 +VIDEO_MODE_GTK=vga=788 + +GRUB_EFI=y +GRUB_PLATFORM=x86_64-efi +GRUB_EFI_NAME=x64 + +include config/x86.cfg diff --git a/build/config/x32/cdrom-xen.cfg b/build/config/x32/cdrom-xen.cfg new file mode 100644 index 000..2b4fd1b --- /dev/null +++ b/build/config/x32/cdrom-xen.cfg @@ -0,0 +1,14 @@ +TYPE=cdrom/gtk + +EXTRANAME=cdrom/xen/ + +MANIFEST-KERNEL =
Bug#773942: O: lynx-cur -- Text-mode WWW Browser with NLS support (development version)
Hi again, Denis Briand wrote: On Thu, Feb 12, 2015 at 02:04:26AM +0100, Axel Beckert wrote: Shall we open an Alioth project to get a team mailing list? Or will collab-maint plus bug tracking system already suffice the team's needs? IMHO I think a team mailing list will be better to coordinate our work. Ok. I've created an alioth project named pkg-lynx and ordered a mailing list: | A mailing list will be created on Alioth in 6-24 hours | and you are the list administrator. | | This list is: pkg-lynx-ma...@lists.alioth.debian.org . | | Your mailing list info is at: | https://lists.alioth.debian.org/mailman/listinfo/pkg-lynx-maint . So for now we just have to wait a little bit. I've added Denis and Andreas to the project, but for now this has no real effect. (I also gave Andreas administrative access to the project so we have another DD who can administrate the project in case I'm unavailable.) Maybe Axel could open a collab-maint git repository on alioth to work together ? Done: https://anonscm.debian.org/cgit/collab-maint/lynx-cur.git/ I wonder if we should move that to https://anonscm.debian.org/cgit/pkg-lynx/lynx-cur.git/ now that we have an alioth project. That way it would make it easier to give freshly involved people like Andy commit access. (Collab-maint rather eases access for already involved people...) If nobody opposes, I'd move the git repo from collab-maint to pkg-lynx and give all team members commit access. In any case, Andy should create an alioth account at https://alioth.debian.org/account/register.php (at least I didn't find one with his name) -- Further steps to get commit access will depend on our decision about the final git repo location (collab-maint vs pkg-lynx). Andy Valencia wrote: I went sorta quiet. Some local dev work picked up, but also it takes a B-I-G gulp of document reading to have even the first idea of all that Debian packaging goop. Maybe starting with small pieces of hands-on experience will make that easier. :-) I'm perfectly well skilled at C and git and all that stuff. That's good! Because C is not one of my strengths. :-) I saw you're doing ham radio, radio shows and gopher, too. I like that. (I recently broadcasted two radio shows about amateur radio for http://www.hackerfunk.ch/ -- in Swiss-German, second one not yet online. :-) But there are so many layers of Debian package tooling, and even after grinding through all the documentation sets Axel pointed me at I still don't have a clear idea of what gets built where, for which release, and where one goes to find out what got built/packaged, or if it had a problem, where's the log? Tons of details. I can understand that. For being able to work with the git repository with already having Git knowledge, I'd say that having a look at some of the tools included in the git-buildpackage package (meta command is gbp) would be a good start. If you want to help importing and merging new upstream releases, I recommend having a look at the git-import-orig or gbp import-orig command (they're both the same, the latter being the newer, preferred variant) especially. It works fine together the following two commands: * pristine-tar (of the package of the same name) * origtargz (of the package devscripts) To make git-import-orig to always use pristine-tar, create a ~/.gbp.conf file with this contents: ---8--- [DEFAULT] pristine-tar = true ---8--- pristine-tar isn't easy to understand as its value only shows up in some specific situations, especially in team-maintenance or if package development is done on multiple machines. I'll try to show a common one to explain how the tools work together: Team Maintenance: * Person A wants to import a new upstream release. git-import-orig does the main work of untarring and adding files. It pushes all branches to the central repository. But the tar ball contains more details than git can store (permissions, etc.) pristine-tar saves all those git can't store in a binary delta file in a separate pristine-tar branch. Together with the contents from the upstream branch and the small binary delta, the whole .orig.tar.gz can be recreated from the git repository. * Person B wants to work on the package. gbp pull gets the current state. But since a new upstream version was imported, running dpkg-buildpackage bails out because no .orig.tar.gz tar ball was found, but is required. B calls origtargz which sees that there is a pristine-tar branch containing all necessary information to recreate the tar ball bit-wise identically. To do that, origtargz calls pristine-tar with the according options to recreate the newest tar ball. B can build the package and can be sure to have an identical upstream source tar ball without having to download it a second time via HTTP. (origtargz will try to do that to some extend if pristine-tar is not used. But unless the upstream release already had been uploaded to
Bug#212814: Kiemelt akció
Téli pihenés a 4 csillagos Hotel Aurum Familyben, Hajdúszoboszlón! 3 nap/2 éjszaka/2 felnőttnek + egy 3 éven aluli gyermeknek félpanzióval, wellness használattal és strand belépővel csak 34.900 Ft Hotel Aurum Family - Hajdúszoboszló Eredeti ár: 69.800 Ft Akciós ár: 34.900 Ft Foglaláshoz fizetendő: 6.980 Ft 50% kedvezmény Kupon Tartalma: 3 nap/2 éjszaka 2 felnőtt és egy 3 éven aluli gyermek részére a Hotel Aurum Familyben fogadó ital félpanziós ellátás: svédasztalos reggeli és vacsora Hotel Aurum Family szállodában szauna és gőzkabin használható térítésmentesen, valamint a Park Hotel Ambrózia*** wellness-részlege is ingyenesen áll a vendégek rendelkezésére. városi strand belépő köntös bekészítés ingyenes Wi-Fi a szálloda egész területén Laroba Hotel - Alsóörs (3 nap / 2 éjszaka - 2 fő) Eredeti ár: 85.600 Ft Akciós ár: 41.990 Ft Foglaláskor fizetendő: 5.335 Ft 51% NAIH-79431/2014. Ha nem Te adtad meg az emailcímedet, vagy nem szeretnél a jövőben értesülni a legjobb ajánlatokról, ide kattinva leiratkozhatsz, vagy írj levelet az i...@wellness7.hu címre
Bug#773942: O: lynx-cur -- Text-mode WWW Browser with NLS support (development version)
On Thu, Feb 12, 2015 at 12:33:05PM +0100, Axel Beckert wrote: I wonder if we should move that to https://anonscm.debian.org/cgit/pkg-lynx/lynx-cur.git/ now that we have an alioth project. That way it would make it easier to give freshly involved people like Andy commit access. (Collab-maint rather eases access for already involved people...) If nobody opposes, I'd move the git repo from collab-maint to pkg-lynx and give all team members commit access. I agree with that regards Denis signature.asc Description: Digital signature
Bug#777906: ITP: puppet-module-duritong-trocla -- Use trocla password generator and storage from puppet.
Package: wnpp Severity: wishlist Owner: Michael Weiser michael.wei...@gmx.de * Package name: puppet-module-duritong-trocla Version : 0.0.4 Upstream Author : Marcel Haerry mh+tro...@immerda.ch * URL : https://forge.puppetlabs.com/duritong/trocla * License : GPL Programming Lang: Puppet Description : Use trocla password generator and storage from puppet. This is the puppet module to manage a trocla installation on the puppet master. It also, provides the necessary function to query trocla from puppet. Trocla provides you a simple way to create and store (random) passwords on a central server, which can be retrieved by other applications. An example for such an application is puppet and trocla can help you to not store any plaintext or hashed passwords in your manifests by keeping these passwords only on your puppetmaster. For more information see https://github.com/duritong/trocla. trocla provides an elegant way to generate and store random but afterwards fixed passwords for use on possibly multiple clients. Passwords are stored on the Puppet master and only available to clients they're assigned to via the manifests. I'd like to create a Debian package via the Puppet packaging team and can help in maintenance. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777904: FTBFS on arm64
Package: ming Version: 0.4.5-1.2 Severity: normal Tags: patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Fix FTBFS on arm64 by dh_autoreconf. -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJU3II+AAoJEHXZCwEKhFERtN4QAJSDpXOSw6FA8sWRKzrgQQfB fvtijLioVW/nfr2TefQ51PA1pH9cxnmQEwMs1r0MIMyQqjoWTYTUqVtjW98q7rzB lyUPLsBZnI0G99AIs5XHRBYrauSLmV4ddMTS1OFh71tF6HY0Fhd7MzSvZzfuVIkF SMjViq9zklOu0QqXHMRoa4CkS8PGdXahwcPFfIxMnHXWH/4Gx/KZ4YoH7KWLjw/g kzy9y0TGuH024oeNgKvPo0m6RzUviTdfNw21qgLiZ0Wy95uOP9CIBzZPZUnsLCUp BgzdsjJ5m8t0e+q5HHt//DAso97KQfvasdYLHBY39LFzNheM8B/UZDYX1BDWtCTf uevMKIDGtDsISlm2ngjtxydcNB9pN77Q/2fDzyXgyMtgcerI/7z1ASbYkJLR8nmb 0UbsS9FRS3CQ1tA1aFvZYSv1JqyWQFhifAaY4vm/k+Omdybyqjqc5Vu/3pUHHBp3 lL04qKWRl6dkSVR7rO2nXnzyTCsSsQz5HmC3QiWw18D0AX6d8nC6aHdx03sdDenD TtHIwHIhAUGOD/aCIv/m4FIpH3S8NLhQ4+O8SrmUlFqi453ajIm6FURsr5YtUWUI TiDJ82tcf4t0tD3IzH2M+icnonWcdrbsGmDxYFAQBmYnaL+KAn2OMiyb25OIIZzr ilUh58y37ArBIDNUpTBp =fUyC -END PGP SIGNATURE- diff -Nru ming-0.4.5/debian/changelog ming-0.4.5/debian/changelog --- ming-0.4.5/debian/changelog 2015-02-12 10:32:51.0 + +++ ming-0.4.5/debian/changelog 2015-02-12 10:32:52.0 + @@ -1,3 +1,10 @@ +ming (1:0.4.5-1.3) unstable; urgency=medium + + * Non-maintainer upload. + * Fix FTBFS on arm64. + + -- Chen Baozi baoz...@debian.org Thu, 12 Feb 2015 10:25:16 + + ming (1:0.4.5-1.2) unstable; urgency=medium * Non-maintainer upload with team member's permission. diff -Nru ming-0.4.5/debian/control ming-0.4.5/debian/control --- ming-0.4.5/debian/control 2015-02-12 10:32:51.0 + +++ ming-0.4.5/debian/control 2015-02-12 10:32:52.0 + @@ -2,7 +2,7 @@ Section: libs Priority: optional Maintainer: Stuart R. Anderson ander...@netsweng.com -Build-Depends: debhelper (= 5.0.37.2), docbook-to-man, swig, python-all-dev (= 2.7.3), libgif-dev, libpng-dev, libz-dev, perl (= 5.10.0), autotools-dev, flex, bison, libfreetype6-dev, ttf-dejavu, ttf-opensymbol, php5-dev, php5-cli, automake, autoconf2.59, quilt, chrpath +Build-Depends: debhelper (= 5.0.37.2), docbook-to-man, swig, python-all-dev (= 2.7.3), libgif-dev, libpng-dev, libz-dev, perl (= 5.10.0), autotools-dev, flex, bison, libfreetype6-dev, ttf-dejavu, ttf-opensymbol, php5-dev, php5-cli, automake, autoconf2.59, quilt, chrpath, dh-autoreconf Standards-Version: 3.9.3 Homepage: http://www.libming.net/ diff -Nru ming-0.4.5/debian/rules ming-0.4.5/debian/rules --- ming-0.4.5/debian/rules 2015-02-12 10:32:51.0 + +++ ming-0.4.5/debian/rules 2015-02-12 10:32:52.0 + @@ -36,14 +36,7 @@ $(MAKE) -f /usr/share/quilt/quilt.make patch -ifneq $(wildcard /usr/share/misc/config.sub) - cp -f /usr/share/misc/config.sub config.sub -endif -ifneq $(wildcard /usr/share/misc/config.guess) - cp -f /usr/share/misc/config.guess config.guess -endif - ./autogen.sh - + dh_autoreconf CFLAGS=$(CFLAGS) ./configure \ --host=$(DEB_HOST_GNU_TYPE) \ --build=$(DEB_BUILD_GNU_TYPE) \ @@ -97,6 +90,7 @@ clean: dh_testdir dh_testroot + dh_autoreconf_clean if [ -f Makefile ] ;\ then \
Bug#761249: icedtea-7-plugin: Plugin does not remember permission option
Dear Package Maintainers! As I did not receive any kind of confirmation for this bug I ask you to have a look at it again. Please consider fixing this Bug before Jessie release to stable as it makes IcedTea a major pain to use (having to confirm running Java applets every time, even frequently used ones as it is not possible to save the confirm option). Best Regards, Juergen Fuchsberger From: Juergen Fuchsberger juergen.fuchsber...@uni-graz.at To: Debian Bug Tracking System sub...@bugs.debian.org Subject: icedtea-7-plugin: Plugin does not remember permission option Date: Fri, 12 Sep 2014 08:53:21 +0200 Package: icedtea-7-plugin Version: 1.5-2 Severity: normal Dear all, When opening a java applet in Iceweasel, the icedtea plugin does not remember the permission to run the applet. Testing with https://www.java.com/en/download/installed.jsp?detect=jre the applet is asking for permission to run the application. Even if I select Remember this option, the option is not remembered. The next time the applet is loaded, the dialog appears again. This behaviour is also described here: http://askubuntu.com/questions/463196/iced-tea-plugin-keeps-asking-for-permission-to-run-java-applets Best regards, Juergen -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages icedtea-7-plugin depends on: ii icedtea-netx 1.5-2 ii libc6 2.19-10 ii libgcc11:4.9.1-12 ii libglib2.0-0 2.40.0-5 ii libstdc++6 4.9.1-12 ii openjdk-7-jre 7u65-2.5.2-2 icedtea-7-plugin recommends no packages. icedtea-7-plugin suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777905: base-installer: x32 port
Package: base-installer Version: 1.152 Severity: wishlist Tags: d-i patch User: debian-...@lists.debian.org Usertags: port-x32 di-x32 Hi! Please apply the attached patch. It defines kernel selectors for the x32 architecture. As x32 is a new ABI atop the amd64 kernel, this patch symlinks kernel/amd64.sh to kernel/x32.sh, to keep them in sync in the future. The patch can be applied directly to the d-i/base-installer git repository. If you want to test, as the patch-set for x32 in d-i involves around twenty packages, you'll want ready packages from the repository at debian-x32.org. Complete d-i isos are available at http://debian-x32.org/#debian-installer while debs/udebs/modified sources at http://ftp.debian-x32.org/debian/ -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (600, 'unstable'), (500, 'unreleased'), (50, 'experimental') Architecture: x32 (x86_64) Kernel: Linux 3.19.0-x32 (SMP w/6 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) From 60dd1261da6c21033b13ed7670d245f7f09640cf Mon Sep 17 00:00:00 2001 From: Adam Borowski kilob...@angband.pl Date: Thu, 12 Feb 2015 07:39:01 +0100 Subject: [PATCH] Link x32 kernel selectors to amd64. --- kernel/x32.sh | 1 + 1 file changed, 1 insertion(+) create mode 12 kernel/x32.sh diff --git a/kernel/x32.sh b/kernel/x32.sh new file mode 12 index 000..85c8502 --- /dev/null +++ b/kernel/x32.sh @@ -0,0 +1 @@ +kernel/amd64.sh \ No newline at end of file -- 2.1.4
Bug#777753: gcc: LTO produces unreproducible debug information
affects 53 + apt-cacher-ng affects 53 + avian affects 53 + batctl affects 53 + batmand affects 53 + cloop affects 53 + encfs affects 53 + exactimage affects 53 + kwalletcli affects 53 + makefs affects 53 + mupen64plus-audio-sdl affects 53 + mupen64plus-core affects 53 + mupen64plus-input-sdl affects 53 + mupen64plus-rsp-hle affects 53 + mupen64plus-rsp-z64 affects 53 + mupen64plus-ui-console affects 53 + mupen64plus-video-arachnoid affects 53 + mupen64plus-video-glide64 affects 53 + mupen64plus-video-rice affects 53 + mupen64plus-video-z64 affects 53 + pax affects 53 + py3cairo affects 53 + rna-star affects 53 + rs affects 53 + simgrid affects 53 + systemd thanks I just tried to extract the visible -flto parameters from the reproducible build [1] logs and got this list of packages. There might be even more packages which are affected. [1] https://reproducible.debian.net/reproducible.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#656233: libapache2-mod-wsgi-py3: libapache2-mod-python-py3 should conflict with libapache2-mod-python
Jessie version shows a better error message, which is a real improvement: [wsgi:crit] [pid 17100] mod_wsgi (pid=17100): The mod_python module can not be used on conjunction with mod_wsgi 4.0+. Remove the mod_python module from the Apache configuration. However, a Conflicts: libapache2-mod-python seems a good idea to me. -- Nirgal signature.asc Description: OpenPGP digital signature
Bug#777823: Setting bugs to forwarded
Control: tag -1 upstream Control: forwarded -1 PIPE-5756 The bug was forwarded to upstream and is registered under the mentioned Id. Since the bug database is not public, an URL is not given. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645467: ITP: autodeb -- automated debianization tool
owner 645467 ! retitle 645467 ITP: autodeb -- automated debianization tool thanks Hi I'm stealing this RFP (inactive since 2011) to make a reservation for the 'autodeb' name for my own attempt at an automated debianization tool. Currently it's vaporware. We will see. Lucas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778211: xblast-tnt: please make the build reproducible
Source: xblast-tnt Version: 2.10.4-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 xblast-tnt could not be built reproducibly. The attached patch removes timestamps from the build system. Once applied, xblast-tnt can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff -urNad xblast-tnt.orig/xblast-tnt-2.10.4/debian/rules xblast-tnt/xblast-tnt-2.10.4/debian/rules --- xblast-tnt.orig/xblast-tnt-2.10.4/debian/rules 2015-02-12 05:36:44.071522369 + +++ xblast-tnt/xblast-tnt-2.10.4/debian/rules 2015-02-12 06:07:21.361990287 + @@ -85,7 +85,7 @@ $(INSTALL_FILE) README NEWS features.html $(TMP1)/usr/share/doc/$(PKG1) $(INSTALL_FILE) ChangeLog $(TMP1)/usr/share/doc/$(PKG1)/changelog $(INSTALL_FILE) xblast.man $(TMP1)/usr/share/man/man6/xblast-tnt.6x - gzip -9 $(TMP1)/usr/share/doc/$(PKG1)/changelog \ + gzip -9n $(TMP1)/usr/share/doc/$(PKG1)/changelog \ $(TMP1)/usr/share/man/man6/xblast-tnt.6x cd $(TMP1)/usr/share/man/man6 ln -s xblast-tnt.6x.gz \ xblast-tnt-mini.6x.gz @@ -115,7 +115,7 @@ $(INSTALL_FILE) debian/changelog \ $(TMP1)/usr/share/doc/$(PKG1)/changelog.Debian $(INSTALL_FILE) debian/copyright $(TMP1)/usr/share/doc/$(PKG1) - gzip -9 $(TMP1)/usr/share/doc/$(PKG1)/changelog.Debian + gzip -9n $(TMP1)/usr/share/doc/$(PKG1)/changelog.Debian $(INSTALL_SCRIPT) debian/postinst debian/postrm \ $(TMP1)/DEBIAN $(INSTALL_FILE) debian/overrides \
Bug#778209: xblast-tnt-musics: please make the build reproducible
Source: xblast-tnt-musics Version: 20050106-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 xblast-tnt-musics could not be built reproducibly. The attached patch removes timestamps from the build system. Once applied, xblast-tnt-musics can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff -urNad xblast-tnt-musics.orig/xblast-tnt-musics-20050106/debian/rules xblast-tnt-musics/xblast-tnt-musics-20050106/debian/rules --- xblast-tnt-musics.orig/xblast-tnt-musics-20050106/debian/rules 2015-02-12 05:37:40.449699492 + +++ xblast-tnt-musics/xblast-tnt-musics-20050106/debian/rules 2015-02-12 05:39:09.185129800 + @@ -45,7 +45,7 @@ $(TMP)/usr/share/doc/$(PKG)/changelog.Debian $(INSTALL_FILE) debian/copyright \ $(TMP)/usr/share/doc/$(PKG) - gzip -9 $(TMP)/usr/share/doc/$(PKG)/changelog.Debian + gzip -9n $(TMP)/usr/share/doc/$(PKG)/changelog.Debian dpkg-gencontrol -isp -p$(PKG) -P$(TMP) cd $(TMP) find * -type f ! -regex '^DEBIAN/.*' -print0 | \ xargs -r0 md5sum DEBIAN/md5sums
Bug#778256: clang: fail to use the wrong gnu libstdc++ include directory this directory is one digit only (here 5)
Package: clang Version: 1:3.5-26 Severity: normal Dear Maintainer, I tried to compile a c++ with clang (3.5, 3.7) which worked before I installed libstdc++ libstdc++-5-dev:amd64 5-20150205-1 libstdc++6:amd645-20150205-1 from experimental (thus the normal severity as the tool the package ship is broken, higher would be expected when 5 enters unstable). The verbose output of clang++ (3.5 here) follows. What helper me was: ignoring nonexistent directory /usr/bin/../lib/gcc/x86_64-linux-gnu/5.0.0/../../../../include/x86_64-linux-gnu/c++/5.0.0 that is there is an /usr/include/x86_64-linux-gnu/c++/5 but no /usr/include/x86_64-linux-gnu/c++/5.0.0 which is fine and was same scheme with 4.X serie. But the initial guess is wrong: Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5.0.0 as with 4.9 , 4.9 is sorted before 4.9.2 thus include/c++/4.9 is used instead of non existent include/c++/4.9.2 ... but 5.0.0 is sorted before 5 , or 5 is bypassed altogether ! My guess is this is the root of bug. Debian clang version 3.5.0-9 (tags/RELEASE_350/final) (based on LLVM 3.5.0) Target: x86_64-pc-linux-gnu Thread model: posix Found candidate GCC installation: /usr/bin/../lib/gcc/i586-linux-gnu/4.9 Found candidate GCC installation: /usr/bin/../lib/gcc/i586-linux-gnu/4.9.2 Found candidate GCC installation: /usr/bin/../lib/gcc/i586-linux-gnu/5.0.0 Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/4.7 Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/4.7.4 Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/4.8 Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/4.8.4 Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/4.9 Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/4.9.2 Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/5.0.0 Found candidate GCC installation: /usr/lib/gcc/i586-linux-gnu/4.9 Found candidate GCC installation: /usr/lib/gcc/i586-linux-gnu/4.9.2 Found candidate GCC installation: /usr/lib/gcc/i586-linux-gnu/5.0.0 Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.7 Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.7.4 Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.8 Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.8.4 Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.9 Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.9.2 Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5.0.0 Selected GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/5.0.0 Candidate multilib: .;@m64 Candidate multilib: 32;@m32 Candidate multilib: x32;@mx32 Selected multilib: .;@m64 /usr/lib/llvm-3.5/bin/clang -cc1 -triple x86_64-pc-linux-gnu -emit-obj -mrelax-all -disable-free -disable-llvm-verifier -main-file-name main.cpp -mrelocation-model static -mdisable-fp-elim -fmath-errno -masm-verbose -mconstructor-aliases -munwind-tables -fuse-init-array -target-cpu x86-64 -target-linker-version 2.24.90 -v -dwarf-column-info -coverage-file /home/prahal/SandBoxes/uva.onlinejudge.org/429_wordtransformation-build2/CMakeFiles/429_wordtransformation.dir/main.cpp.o -resource-dir /usr/lib/llvm-3.5/bin/../lib/clang/3.5.0 -internal-isystem /usr/bin/../lib/gcc/x86_64-linux-gnu/5.0.0/../../../../include/c++/5.0.0 -internal-isystem /usr/bin/../lib/gcc/x86_64-linux-gnu/5.0.0/../../../../include/x86_64-linux-gnu/c++/5.0.0 -internal-isystem /usr/bin/../lib/gcc/x86_64-linux-gnu/5.0.0/../../../../include/x86_64-linux-gnu/c++/5.0.0 -internal-isystem /usr/bin/../lib/gcc/x86_64-linux-gnu/5.0.0/../../../../include/c++/5.0.0/backward -internal-isystem /usr/include/clang/3.5.0/include/ - internal-isystem /usr/local/include -internal-isystem /usr/lib/llvm-3.5/bin/../lib/clang/3.5.0/include -internal-externc-isystem /usr/bin/../lib/gcc/x86_64-linux-gnu/5.0.0/include -internal-externc-isystem /usr/include/x86_64-linux-gnu -internal-externc-isystem /include -internal-externc-isystem /usr/include -std=c++11 -fdeprecated-macro -fdebug-compilation-dir /home/prahal/SandBoxes/uva.onlinejudge.org/429_wordtransformation-build2 -ferror-limit 19 -fmessage-length 212 -mstackrealign -fobjc-runtime=gcc -fcxx-exceptions -fexceptions -fdiagnostics-show-option -fcolor-diagnostics -o CMakeFiles/429_wordtransformation.dir/main.cpp.o -x c++ /home/prahal/SandBoxes/uva.onlinejudge.org/429_wordtransformation/main.cpp clang -cc1 version 3.5.0 based upon LLVM 3.5.0 default target x86_64-pc-linux-gnu ignoring nonexistent directory /usr/bin/../lib/gcc/x86_64-linux-gnu/5.0.0/../../../../include/x86_64-linux-gnu/c++/5.0.0 ignoring nonexistent directory /usr/bin/../lib/gcc/x86_64-linux-gnu/5.0.0/../../../../include/x86_64-linux-gnu/c++/5.0.0 ignoring nonexistent directory /include ignoring duplicate directory
Bug#778212: closed by Ben Hutchings b...@decadent.org.uk
On Thu, Feb 12, 2015 at 05:21:14PM +, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the src:linux package: #778212: linux: please build the kernel and udebs on x32 It has been closed by Ben Hutchings b...@decadent.org.uk. No, you need to make the installer use the amd64 packages for this. 1. d-i cannot currently use packages from a foreign architecture (same applies for example to i386 on non-ancient hardware) 2. neither can it use udebs (needed to boot d-i itself) 3. amd64 kernels currently have x32 syscalls disabled unless a special argument is passed on the command line. This is fragile, especially if fancy combinations of bootloader with preseeding are involved. I'm not going to force reopen this, as you know more about Debian kernel packaging than me (duh), but at least in my unofficial x32 release I'm going to use kernel+udebs with this patch, unless you can enlighten me. Would you please elaborate a bit about what do I understand wrong? And what the plans for foreign kernels in d-i are? -- // If you believe in so-called intellectual property, please immediately // cease using counterfeit alphabets. Instead, contact the nearest temple // of Amon, whose priests will provide you with scribal services for all // your writing needs, for Reasonable and Non-Discriminatory prices. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764799: update to the bug
After some analysis the issues turned out to be related to missing ed25519 host key. Once it was created the sshd had no issues with running. My custom sshd_config has only specific HostKeys defined and for some reason not having there ed25519 cause this crash. Running: ssh-keygen -A and adding to /etc/ssh/sshd_config line: HostKey /etc/ssh/ssh_host_ed25519_key solved this. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#689083: libgphoto2-2-dev is not Multi-Arch compatible
Package: libgphoto2-dev
Version: 2.5.4-1.1+b2
Followup-For: Bug #689083
Dear Maintainer,
Here is a proposed patch to make it possible to make libgphoto2-dev as
Multi-Arch: same.
The trick is that on Debian it's not necessary to use -L to link with libraries
that
are in /usr/lib/triplet. This means it should be ok to remove this option
from the
xxx-config scripts which in turn solves the conflict for libgphoto2-dev.
Is that approach ok?
diff -ur a/debian/control b/debian/control
--- a/debian/control2014-08-25 21:47:22.0 +0200
+++ b/debian/control2015-02-12 23:10:00.414367888 +0100
@@ -30,6 +30,7 @@
Package: libgphoto2-dev
Section: libdevel
Architecture: any
+Multi-Arch: same
Depends:
libgphoto2-6 (= ${binary:Version})
, libexif-dev
diff -ur a/debian/patches/series b/debian/patches/series
--- a/debian/patches/series 2014-01-06 01:37:00.0 +0100
+++ b/debian/patches/series 2015-02-12 23:23:08.251291406 +0100
@@ -1,3 +1,4 @@
#10_disable_cache
#11_hurd_no_path_max_bsdsource
+30_multiarch.patch
kFreeBSD-ENODATA.patch
--- /dev/null 2015-01-27 12:27:17.181130653 +0100
+++ b/debian/patches/30_multiarch.patch 2015-02-12 23:22:24.959450232 +0100
@@ -0,0 +1,40 @@
+--- a/gphoto2-config.in
b/gphoto2-config.in
+@@ -2,7 +2,7 @@
+
+ # leave these definitions here
+ # they are required for correct interpolation of
+-# @libdir@ and @includedir@ later on
++# libdir and includedir later on
+ prefix=@prefix@
+ exec_prefix=@exec_prefix@
+
+@@ -59,7 +59,7 @@
+ ;;
+
+ --libs)
+-echo -L@libdir@ -lgphoto2 -lgphoto2_port -lm
++echo -lgphoto2 -lgphoto2_port -lm
+ ;;
+
+ *)
+--- a/libgphoto2_port/gphoto2-port-config.in
b/libgphoto2_port/gphoto2-port-config.in
+@@ -2,7 +2,7 @@
+
+ # leave these definitions here
+ # they are required for correct interpolation of
+-# @libdir@ and @includedir@ later on
++# libdir and includedir later on
+ prefix=@prefix@
+ exec_prefix=@exec_prefix@
+
+@@ -59,7 +59,7 @@
+ ;;
+
+ --libs)
+- echo -L@libdir@ -lgphoto2_port
++ echo -lgphoto2_port
+ ;;
+
+ *)
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages libgphoto2-dev depends on:
ii libexif-dev 0.6.21-2
ii libgphoto2-6 2.5.4-1.1+b2
ii pkg-config0.28-1
libgphoto2-dev recommends no packages.
libgphoto2-dev suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775527: live-images: upgrade splash to Jessie theme
On 12/02/2015 04:27, Daniel Baumann wrote: On 02/11/15 20:19, jnqnfe wrote: Why are we now using the simple black syslinux theme instead of the official install disc theme? it's the one Juliette provided in her tarball. Right, but Juliette is only going by the stated requirements at [1] to determine what images to create and supply in her archive. These requirements simply list, under the boot screen heading: - GRUB 2: 640x480, 24bit, file PNG. - Isolinux: 640x300px, 4bit color depth (means: 16 colors). View Make Sys Image. - Syslinux: 640x300px, 16bit color depth (means: 65,536 colors), in PNG format. - Plymouth: a SVG file (or at the very least a collection of PNGs for the different elements of scene and background). There is no implication anywhere that Juliette means for any of the images she has produced for the above to be used for install/live boot menus, nor by the Debian artwork proposal outlines that any of these would be used for that, and no-one so far has properly communicated to her than an image for such use is needed. If we look at the Wheezy 'joy' theme archive [2] this also only contains boot images per the above requirements. It does not contain a copy of the image actually used by the debian d-i/cd teams as a boot menu splash for the official install media. I would assume that they took the base theme assets and produced that image themselves. Furthermore at [3] and [4] you'll see that again with Jessie they are doing the very same thing. I am supportive of a notion that this image should actually be being produced by the theme artist as part of the artwork proposal, thus allowing correct and proper copyright attribution (perhaps we can have the requirements amended to list it). I am against use of the syslinux image currently selected for live-images though, I think it's completely the wrong one to be using. If the issue with the image I supplied myself was down to copyright attribution, I am perfectly happy to give up any claim of ownership/copyright I may have on it to Juliette, and for Juliette to adopt it as her own, or equally happy for her to produce her own copy. I had no intention of wanting any credit/claim over this, after all, all I did was take her individual asset components and place them on top of each other in a particular layout, then add the text 'GNU/Linux', hardly something I can or would want to claim as mine. :) I'm writing a separate email to Juliette at the same time as this to explain things. [1] https://wiki.debian.org/DebianDesktop/Artwork/Requirements [2] https://wiki.debian.org/DebianArt/Themes/Joy [3] http://anonscm.debian.org/cgit/d-i/debian-installer.git/tree/build/boot/x86/pics/ [4] http://ftp.debian.org/debian/dists/sid/main/installer-amd64/current/images/cdrom/debian-cd_info.tar.gz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777583: Incorrect debian/copyright for smartmontools
retitle -1 debian/copyright for smartmontools is too restrictive severity -1 wishlist On Tue, Feb 10, 2015 at 01:30:33AM -0500, Mark H Weaver wrote: Package: smartmontools debian/copyright claims that smartmontools is distributed under GPLv2, but the copyright notices in its source files include the or (at your option) any later version language. In that case, the Debian package “just” claims a more restrictive term of use than it actually is, but it is not wrong either (GPL-2 is included in GPL-2+, it’s as if the maintainer decided on the option). Regards David signature.asc Description: Digital signature
Bug#778264: mailfilter: please make the build reproducible
Source: mailfilter Version: 0.8.3-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 mailfilter could not be built reproducibly. The attached patch removes timestamps from the build system. Once applied, mailfilter can be built reproducibly in our current reproducible toolchain. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff -urNad mailfilter.orig/mailfilter-0.8.3/debian/rules mailfilter/mailfilter-0.8.3/debian/rules --- mailfilter.orig/mailfilter-0.8.3/debian/rules 2015-02-12 22:05:39.709241365 + +++ mailfilter/mailfilter-0.8.3/debian/rules2015-02-12 22:19:23.497813728 + @@ -1,11 +1,13 @@ #!/usr/bin/make -f +BUILD_DATE := $(shell dpkg-parsechangelog --show-field Date) + %: dh $@ --with autotools_dev override_dh_auto_install: dh_auto_install - tar -czf ./debian/mailfilter/usr/share/doc/mailfilter/contrib.tar.gz ./contrib + GZIP=-9n tar -czf ./debian/mailfilter/usr/share/doc/mailfilter/contrib.tar.gz --mtime=$(BUILD_DATE) ./contrib override_dh_auto_clean: dh_auto_clean
Bug#778267: irsim: please make the build reproducible
Source: irsim
Version: 9.7.87-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 irsim could not be built reproducibly.
The attached patch removes timestamps from the build system. Once
applied, irsim can be built reproducibly in our current reproducible
toolchain.
[1]: https://wiki.debian.org/ReproducibleBuilds
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
diff -urNad irsim.orig/irsim-9.7.87/debian/patches/05-reproducible-build.patch
irsim/irsim-9.7.87/debian/patches/05-reproducible-build.patch
--- irsim.orig/irsim-9.7.87/debian/patches/05-reproducible-build.patch
1970-01-01 01:00:00.0 +0100
+++ irsim/irsim-9.7.87/debian/patches/05-reproducible-build.patch
2015-02-12 22:28:33.474293551 +
@@ -0,0 +1,11 @@
+--- irsim-9.7.87.orig/irsim/Makefile
irsim-9.7.87/irsim/Makefile
+@@ -8,7 +8,7 @@ EXTRA_LIBS = ${IRSIMDIR}/analyzer/libana
+${IRSIMDIR}/base/libbase.o \
+${MAIN_EXTRA_LIBS}
+
+-DFLAGS += -DIRSIM_DATE=\`date`\
++DFLAGS += -DIRSIM_DATE=\`dpkg-parsechangelog -l../debian/changelog
--show-field Date`\
+
+ CFLAGS += -I${IRSIMDIR}/base
+ LIBS += ${GR_LIBS} -lm
diff -urNad irsim.orig/irsim-9.7.87/debian/patches/series
irsim/irsim-9.7.87/debian/patches/series
--- irsim.orig/irsim-9.7.87/debian/patches/series 2015-02-12
22:22:00.272787116 +
+++ irsim/irsim-9.7.87/debian/patches/series2015-02-12 22:31:18.457645814
+
@@ -2,3 +2,4 @@
02-manpages.patch
03-fhs-images.patch
04-makefile-fix-hardening-ldflags.patch
+05-reproducible-build.patch
Bug#777694: icu maintenance
László, I would be in strong support of your taking over icu. Feel free to do it in conjunction with uploading security fixes that are pending. Right now, last time I looked, there were not yet public patches for all the issues, but I may be wrong. A general tip for ICU security patches: Red Hat has to do them too. I have generally tried to make sure that the version of ICU in a debian release corresponds with a version present in at least one Red Hat release, but I hadn't planned for the 52 to be in jessie; I just didn't have a way to get it updated. But you can often grab security patches from other distributions. Also, upstream has generally been pretty helpful with backporting patches when necessary. Mostly I have found the patches backport pretty easily. Regardless, we will also get stuck in a situation where upstream doesn't support some version we have in a security supported version, which is one of the main challenges of maintaining icu. -- Jay Berkenbilt q...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#689097: libgtk2.0-dev is not Multi-Arch compatible
Package: libgtk2.0-dev
Version: 2.24.25-1
Tags: patch
Followup-For: Bug #689097
Dear Maintainer,
I'm attaching a patch to make some gtk+ packages multiarch-compatible and get
closer to
being able to make libgtk2.0-dev itself Multi-Arch: same.
* Mark the gtk2.0-examples package as Multi-Arch: foreign.
* Now that the GObject introspection files can be put in
/usr/lib/triplet/girepository-1.0, do so in the gir1.2-gtk-2.0 package and
mark it
as Multi-Arch: same.
What will be left then is:
* In libgtk2.0-devi: /usr/bin/dh_gtkmodules contains some /usr/lib/triplet
paths.
* In libgtk2.0-0-dbg: /usr/lib/debug/usr/bin/gtk-demo contains the debug
information for
this binary of the gtk2.0-examples package.
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages libgtk2.0-dev depends on:
ii gir1.2-gtk-2.02.24.25-1
ii libatk1.0-dev 2.14.0-1
ii libcairo2-dev 1.14.0-2.1
ii libgdk-pixbuf2.0-dev 2.31.1-2+b1
ii libglib2.0-dev2.42.1-1
ii libgtk2.0-0 2.24.25-1
ii libgtk2.0-common 2.24.25-1
ii libpango1.0-dev 1.36.8-3
ii libx11-dev2:1.6.2-3
ii libxcomposite-dev 1:0.4.4-1
ii libxcursor-dev1:1.1.14-1+b1
ii libxdamage-dev1:1.1.4-2+b1
ii libxext-dev 2:1.3.3-1
ii libxfixes-dev 1:5.0.1-2+b2
ii libxi-dev 2:1.7.4-1+b2
ii libxinerama-dev 2:1.1.3-1+b1
ii libxml2-utils 2.9.1+dfsg1-4
ii libxrandr-dev 2:1.4.2-1+b1
ii pkg-config0.28-1
Versions of packages libgtk2.0-dev recommends:
ii debhelper 9.20141022
ii python 2.7.8-3
Versions of packages libgtk2.0-dev suggests:
pn libgtk2.0-doc none
-- no debconf information
diff -ur gtk+-2.24.25.orig/debian/control.in gtk+-2.24.25/debian/control.in
--- gtk+-2.24.25.orig/debian/control.in 2015-02-12 16:05:57.0 +0100
+++ gtk+-2.24.25/debian/control.in 2015-02-12 19:30:24.018571814 +0100
@@ -49,6 +49,8 @@
Package: @SHARED_PKG@
Architecture: any
+Multi-Arch: same
+Pre-Depends: ${misc:Pre-Depends}
Depends: @COMMON_PKG@,
${misc:Depends},
${shlibs:Depends},
@@ -58,8 +60,6 @@
@BIN_PKG@
Suggests: librsvg2-common,
gvfs
-Multi-Arch: same
-Pre-Depends: ${misc:Pre-Depends}
Description: GTK+ graphical user interface library
GTK+ is a multi-platform toolkit for creating graphical user
interfaces. Offering a complete set of widgets, GTK+ is suitable
@@ -90,11 +90,11 @@
Package: @COMMON_PKG@
Section: misc
Architecture: all
+Multi-Arch: foreign
Depends: ${misc:Depends}
Recommends: @SHARED_PKG@
Replaces: @SHARED_PKG@ ( 2.24.8-2)
Breaks: @SHARED_PKG@ ( 2.24.8-2)
-Multi-Arch: foreign
Description: common files for the GTK+ graphical user interface library
GTK+ is a multi-platform toolkit for creating graphical user
interfaces. Offering a complete set of widgets, GTK+ is suitable
@@ -106,10 +106,10 @@
Package: @BIN_PKG@
Section: misc
Architecture: any
+Multi-Arch: foreign
Depends: ${misc:Depends},
@SHARED_PKG@ (= ${binary:Version}),
@COMMON_PKG@
-Multi-Arch: foreign
Description: programs for the GTK+ graphical user interface library
GTK+ is a multi-platform toolkit for creating graphical user
interfaces. Offering a complete set of widgets, GTK+ is suitable
@@ -176,12 +176,12 @@
Package: @DOC_PKG@
Section: doc
Architecture: all
+Multi-Arch: foreign
Depends: ${misc:Depends}
Recommends: libglib2.0-doc,
libatk1.0-doc,
libpango1.0-doc
Suggests: devhelp
-Multi-Arch: foreign
Description: documentation for the GTK+ graphical user interface library
GTK+ is a multi-platform toolkit for creating graphical user
interfaces. Offering a complete set of widgets, GTK+ is suitable
@@ -195,6 +195,7 @@
Section: x11
Priority: extra
Architecture: any
+Multi-Arch: foreign
Depends: ${shlibs:Depends},
${misc:Depends},
@SHARED_PKG@ (= ${binary:Version})
@@ -226,6 +227,7 @@
Package: gir1.2-gtk-2.0
Section: introspection
Architecture: any
+Multi-Arch: same
Depends: @COMMON_PKG@,
${misc:Depends},
${shlibs:Depends},
@@ -244,11 +246,11 @@
Package: libgail18
Architecture: any
+Multi-Arch: same
+Pre-Depends: ${misc:Pre-Depends}
Depends: ${misc:Depends},
${shlibs:Depends},
@SHARED_PKG@ (= ${binary:Version})
-Multi-Arch: same
-Pre-Depends: ${misc:Pre-Depends}
Description: GNOME Accessibility Implementation Library -- shared libraries
Gail implements ATK interfaces for GTK+ widgets which are dynamically
loadable at runtime by a GTK+ application. Once loaded, those parts of
@@ -259,11 +261,11 @@
Package: libgail-common
Bug#778266: Directory traversal
Source: libarchive Severity: grave Tags: security Hi, please see http://www.openwall.com/lists/oss-security/2015/01/16/7 for details. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778261: Buffer overflow in GIF encoder
Package: byzanz Severity: important Tags: security Hi, this was reported by Red Hat: https://bugzilla.redhat.com/show_bug.cgi?id=852481 I'm afraid there are no further details, but maybe you can get in touch with upstream; I suppose Red Hat had contacted them and it might already be fixed by now? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776995: snd-usb-audio: micrphone Unlikely big volume range
Please close this bug, I found a workaround. It is just because the webcam's microphone was not set to default in pulseaudio configuration. Executing: pactl set-default-source alsa_input.usb-046d_09a4_F89C6650-02-U0x46d0x9a4.analog-mono resolves the issue. Can be made persistent in /etc/pulse/default.pa. (Command not documented in 'man pactl') The message Unlikely big volume range in syslog is just cosmetic. Ingo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777170: [pkg-wpa-devel] Bug#777170: wpasupplicant: lots of CTRL-EVENT-SIGNAL-CHANGE messages in syslog and couldn't connect to wireless network
On Thu, Feb 05, 2015 at 11:04:30PM +0100, Stefan Lippers-Hollmann wrote: tags -1 moreinfo Hi Hiya! On 2015-02-05, Julian Gilbey wrote: Package: wpasupplicant Version: 2.3-1 Severity: normal I was trying to connect to a wireless network from my MacBook Pro running testing today, and it connected only intermittently. I'm using network-manager, if that makes any difference. It may be the network involved, as I can connect to my home network with no difficulties. What wireless card are you using in your system/ which kernel driver is in use? Overcrowded and noisy environments can certainly make the situation worse, especially when you're almost out of reach of your AP and may even hop between different, equally bad APs. I guess this part of the issue is more of kernel issue though. I've just found out that there were general problems with the wireless in the building which may be part of the cause of this problem, so I will check next week to see if things have improved (they've replaced the wireless network hardware). In the meantime, for the record, here is the wireless card info from hwinfo: 31: PCI 200.0: 0282 WLAN controller [Created at pci.328] Unique ID: y9sn._jDsMEPhrB9 Parent ID: qTvu.mgUbsEukkq3 SysFS ID: /devices/pci:00/:00:1c.1/:02:00.0 SysFS BusID: :02:00.0 Hardware Class: network Model: Broadcom BCM4331 802.11a/b/g/n Vendor: pci 0x14e4 Broadcom Device: pci 0x4331 BCM4331 802.11a/b/g/n SubVendor: pci 0x106b Apple Inc. SubDevice: pci 0x00f5 Revision: 0x02 Driver: bcma-pci-bridge Driver Modules: bcma Device File: wlan0 Features: WLAN Memory Range: 0xa060-0xa0603fff (rw,non-prefetchable) IRQ: 17 (329374 events) HW Address: a8:86:dd:98:d7:12 Link detected: yes WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472 2.484 WLAN encryption modes: WEP40 WEP104 TKIP CCMP WLAN authentication modes: open sharedkey wpa-psk wpa-eap Module Alias: pci:v14E4d4331sv106Bsd00F5bc02sc80i00 Driver Info #0: Driver Status: bcma is active Driver Activation Cmd: modprobe bcma Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #23 (PCI bridge) The log file was filled with thousands of lines of the form: Feb 5 16:54:18 redfield wpa_supplicant[2925]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=0 noise=0 txrate=48000 which were appearing at the rate of about 10 per second. CTRL-EVENT-SIGNAL-CHANGE is emitted at the MSG_INFO (default) logging level - you can tune wpa_supplicant's logging level to reduce (and subsequently hide) these messages. If you start wpa_supplicant by hand, the parameters are -d, -dd, ... (to increase the logging level) or -q, -qq, ... (to reduce the logging level. ifupdown's wpa_supplicant integration allows you to set a debugging level via wpa-debug-level %d (where %d stands for positive or negative numbers, e.g. -3, ..., 0, ..., 3). I do not know how (or if) networkmanager exposes access to these settings. As long as your kernel driver/ module is working fine, you're usually not supposed to get bothered by this event - it may be emitted occassionally, but rarely enough not to be noticed. So clearly something is amiss, but it might be network-related. I'll update next week when I'm able to check again with the new network setup. Many thanks! Julian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778268: 'Alias=saned' line causes problematic running of saned@.service
Package: sane-utils Version: 1.0.24-8 Severity: important Dear Maintainer, After upgrading my Pi 2 Debian install from wheezy to jessie, I was running into systemd chewing up as much CPU power as it could get its hands on. Running 'journalctl -f' showed it printing Looping too fast. Throttling execution a little. approximately every 2 seconds for quite a while after system boot. Although this stopped after some uptime, the high CPU usage remained. Running systemctl --failed showed that saned.service had failed. This causes other issues, such as a lack of any VTs and an inability to normally reboot (although a shutdown can be forced by killing PID 1, but that's hardly ideal!). A quick trip to the #debian-systemd channel on OFTC seems to have established that this is because of the Alias=saned line at the end of the /lib/systemd/system/saned@.service file, which is packaged with sane-utils. Apparently, when /etc/init.d/sane goes up, systemd hits up saned@.service, which it should not because saned@.service should only go up with saned.socket. Two people on the channel recommended dropping the Alias=saned line, and one also suggested that a /dev/null symlink should be packaged for /lib/systemd/system/saned.service. In theory, any program attempting to access a scanner will just be poking [::]6566 anyways, which then will prompt systemd to run saned@.service. Although I think I understand that, I won't claim to be sure; what I am sure of is that removing the Alias=saned line does indeed solve the problem for me. (Apologies if anything is incomplete or mistaken in this bug report, after many years using Debian and derivatives this is actually my first time directly submitting a bug here. Cheers!) -- System Information: Distributor ID: Raspbian Description:Raspbian GNU/Linux 8.0 (jessie) Release: 8.0 Codename: jessie Architecture: armv7l Kernel: Linux 3.18.5-v7+ (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages sane-utils depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.55 ii init-system-helpers1.22 ii libavahi-client3 0.6.31-4 ii libavahi-common3 0.6.31-4 ii libc6 2.19-13 ii libieee1284-3 0.2.11-12 ii libsane1.0.24-8 ii libsystemd0215-11 ii libusb-1.0-0 2:1.0.19-1 ii update-inetd 4.43 sane-utils recommends no packages. Versions of packages sane-utils suggests: pn avahi-daemon none pn unpaper none -- debconf information: sane-utils/saned_run: false sane-utils/saned_scanner_group: true -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778265: CVE-2015-1426
Package: facter Severity: important Tags: security Please see http://puppetlabs.com/security/cve/cve-2015-1426 Fix: https://github.com/puppetlabs/facter/commit/e546bc546e7fb23ad6b68fcf2059452df4d320dd Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#611505: icewm does not unblock signals for reboot and shutdown command
Hallo, * Jörg Sommer [Sat, Jan 29 2011, 11:40:26PM]: Package: icewm Version: 1.3.7~pre2-1 Severity: normal Icewm does not unblock the signals, especially SIGCHLD, for the reboot and shutdown command, what confuses some of these commands. And it seams icewm also does not unblock the signals for itself on restart. % grep \^SigBlk /proc/1862/status SigBlk: After restart (menu, logout, restart) of icewm: % grep \^SigBlk /proc/1862/status SigBlk: 00014007 Please elaborate, I don't see a practical problem as outcome of this behaviour yet. Regards, Eduard. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778271: debian-maintainers: Annual ping for Hugo Lefeuvre (DM)
Package: debian-maintainers Severity: normal Hi, Here is my annual ping (sorry, a bit late maybe...). I'm still interested in maintaining my packages. Best regards, Hugo -- Hugo Lefeuvre (hugo6390)|www.hugo6390.org 4096/ ACB7 B67F 197F 9B32 1533 431C AC90 AC3E C524 065E signature.asc Description: Digital signature
Bug#777038: gnome-icon-theme-symbolic: description's URL broken (404) debdiff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 diff -Nru gnome-icon-theme-symbolic-3.12.0/debian/changelog gnome-icon-theme-symbolic-3.12.0/debian/changelog - --- gnome-icon-theme-symbolic-3.12.0/debian/changelog 2014-03-25 22:20:54.0 +1300 +++ gnome-icon-theme-symbolic-3.12.0/debian/changelog 2015-02-13 05:26:44.0 +1300 @@ -1,3 +1,9 @@ +gnome-icon-theme-symbolic (3.12.0-2) unstable; urgency=medium + + * Fix broken link in package description + + -- John Billings jbilli...@catalyst.net.nz Fri, 13 Feb 2015 04:59:07 +1300 + gnome-icon-theme-symbolic (3.12.0-1) unstable; urgency=medium [ Jackson Doak ] diff -Nru gnome-icon-theme-symbolic-3.12.0/debian/control gnome-icon-theme-symbolic-3.12.0/debian/control - --- gnome-icon-theme-symbolic-3.12.0/debian/control 2014-03-25 22:27:08.0 +1300 +++ gnome-icon-theme-symbolic-3.12.0/debian/control 2015-02-13 05:32:42.0 +1300 @@ -2,12 +2,11 @@ # # Modifications should be made to debian/control.in instead. # This file is regenerated automatically in the clean target. - - Source: gnome-icon-theme-symbolic Section: gnome Priority: optional Maintainer: Debian GNOME Maintainers pkg-gnome-maintain...@lists.alioth.debian.org - -Uploaders: Andreas Henriksson andr...@fatal.se, Michael Biebl bi...@debian.org, Simon McVittie s...@debian.org, Sjoerd Simons sjo...@debian.org +Uploaders: Andreas Henriksson andr...@fatal.se, John Billings jbilli...@catalyst.net.nz, Michael Biebl bi...@debian.org, Simon McVittie s...@debian.org, Sjoerd Simons sjo...@debian.org Build-Depends: debhelper (= 9), dh-autoreconf, gnome-pkg-tools (= 0.10) @@ -16,7 +15,7 @@ pkg-config, libgtk2.0-bin, icon-naming-utils (= 0.8.7) - -Standards-Version: 3.9.5 +Standards-Version: 3.9.6 Vcs-Browser: http://anonscm.debian.org/viewvc/pkg-gnome/desktop/unstable/gnome-icon-theme-symbolic Vcs-Svn: svn://anonscm.debian.org/pkg-gnome/desktop/unstable/gnome-icon-theme-symbolic @@ -37,4 +36,4 @@ directories, and devices. . These stylised icons are symbolic variations on the standard - - theme (see http://www.freedesktop.org/wiki/SymbolicIcons). + theme (see https://wiki.gnome.org/Design/OS/SymbolicIcons). diff -Nru gnome-icon-theme-symbolic-3.12.0/debian/control.in gnome-icon-theme-symbolic-3.12.0/debian/control.in - --- gnome-icon-theme-symbolic-3.12.0/debian/control.in2014-03-08 14:58:23.0 +1300 +++ gnome-icon-theme-symbolic-3.12.0/debian/control.in 2015-02-13 05:31:58.0 +1300 @@ -11,7 +11,7 @@ pkg-config, libgtk2.0-bin, icon-naming-utils (= 0.8.7) - -Standards-Version: 3.9.5 +Standards-Version: 3.9.6 Vcs-Browser: http://anonscm.debian.org/viewvc/pkg-gnome/desktop/unstable/gnome-icon-theme-symbolic Vcs-Svn: svn://anonscm.debian.org/pkg-gnome/desktop/unstable/gnome-icon-theme-symbolic @@ -32,4 +32,4 @@ directories, and devices. . These stylised icons are symbolic variations on the standard - - theme (see http://www.freedesktop.org/wiki/SymbolicIcons). + theme (see https://wiki.gnome.org/Design/OS/SymbolicIcons). -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJU3TPvAAoJEIh2j3pq1+LIT/cP/AlMZGbbg1oz7wVg4LlPQdLq RHe2CEH77I+/iGVemQf0MNrSuZW7FgvzxiXiyM+fpeyoB5QxQyOEpT919H/J6l/T CWao9NvAfYebTYBzabv075Qzfj+CGdJ9O9s12ju6++epDhuaCYefAByIAF0Znjl1 f/F/zm5zGhf7pxCFTlkRhdz9zOl7LVReVv5YHxmWQGg05JWm/Zu4ABwXEzk3OHF4 zNVRi0iOzwCMMa1nJt7cIzE8YTH7VfT38BxSCgbRMGlGPj+pXgsAW+qEAnIfvjY/ NfhQC6IefEoYVfN/n7i8YQY4XFua4uD0dOrrDF3DFoTXYBLnKZJ55HmhyBJNmk6x Q86FqfzR/xhNST+OqiyyKOxdmksSs9dmrKfj9wLoUfVoMqKMFc43Jlt/NGXf4vux T0JdHvLd9sd3JjOe4hpFcW7usry2Xu2qagmU8aloKcjaC1pphVja87pjENwuFlW1 ZqpZMbmnrEXwNxGXzjidjpFg4ZyG4rFMwbSZTuor3c7Jb2y5qoZXIFqu2dekoKnv 0sZbBe4Njd+I088bhiJou324k4iChnVt3d+TX5gA3SmPHPCB+ojxH1LFRKZECTUJ RkNMQESlxB7Oc7uNaNQCdo6xB8j0YQn+sqb+/+e98XLyDbQOAEujH1n3x1mzb5Fp 94/6XX4NqeOAot2PEF+R =PZah -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#778275: miro: please make the build reproducible
Source: miro
Version: 6.0-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 miro could not be built reproducibly.
The attached patch removes timestamps from the build system. Once
applied, miro can be built reproducibly in our current reproducible
toolchain.
[1]: https://wiki.debian.org/ReproducibleBuilds
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
diff -urNad miro.orig/miro-6.0/debian/patches/180_reproducible_build
miro/miro-6.0/debian/patches/180_reproducible_build
--- miro.orig/miro-6.0/debian/patches/180_reproducible_build1970-01-01
01:00:00.0 +0100
+++ miro/miro-6.0/debian/patches/180_reproducible_build 2015-02-12
23:59:27.917458326 +
@@ -0,0 +1,37 @@
+--- miro-6.0.orig/linux/setup.py
miro-6.0/linux/setup.py
+@@ -62,6 +62,7 @@ import platform
+ import pwd
+ import subprocess
+ import time
++import email.utils
+ import shutil
+
+ from Pyrex.Distutils import build_ext
+@@ -360,7 +361,7 @@ data_files += [
+ # of things that have file-related side-effects
+ if not clean in sys.argv:
+ # gzip the man page
+-os.system(gzip -9 %s %s % (
++os.system(gzip -9n %s %s % (
+ os.path.join(platform_dir, 'miro.1'),
+ os.path.join(platform_dir, 'miro.1.gz')))
+ # copy miro.1.gz to miro.real.1.gz so that lintian complains less
+@@ -403,13 +404,16 @@ class miro_install_data(install_data):
+ # We don't use the dist utils copy_file() because it only copies
+ # the file if the timestamp is newer
+ shutil.copyfile(source, dest)
++changelog = subprocess.check_output(('dpkg-parsechangelog',
++ '--show-field', 'Date'))
++buildtime = str(time.mktime(email.utils.parsedate(changelog)))
+ expand_file_contents(dest, APP_REVISION=revision,
+ APP_REVISION_NUM=revisionnum,
+ APP_REVISION_URL=revisionurl,
+ APP_PLATFORM='linux',
+ BUILD_MACHINE=%s@%s % (getlogin(),
+ os.uname()[1]),
+- BUILD_TIME=str(time.time()),
++ BUILD_TIME=buildtime,
+ MOZILLA_LIB_PATH=)
+ self.outfiles.append(dest)
+
diff -urNad miro.orig/miro-6.0/debian/patches/series
miro/miro-6.0/debian/patches/series
--- miro.orig/miro-6.0/debian/patches/series2015-02-12 22:30:21.383101937
+
+++ miro/miro-6.0/debian/patches/series 2015-02-12 23:58:15.154246077 +
@@ -5,3 +5,4 @@
150_codec_id.patch
160_fixyoutubedl.patch
170_no_enfmp.patch
+180_reproducible_build
Bug#778269: ITP: python-mkdocs -- Static site generator geared towards building project documentation
Package: wnpp Severity: wishlist Owner: Brian May b...@debian.org * Package name: python-mkdocs Version : 0.11.1 Upstream Author : Tom Christie * URL : http://www.mkdocs.org/ * License : BSD Programming Lang: Python Description : Static site generator geared towards building project documentation MkDocs is a fast, simple and downright gorgeous static site generator that's geared towards building project documentation. Documentation source files are written in Markdown, and configured with a single YAML configuration file. This package is required to build the documentation in the latest upstream version of python-djangorestframework. I plan to maintain this as part of the python modules team. The intention appears to be that mkdocs is used as a standalone application, although it supplies a mkdocs python package which could in theory be called directly. Given the above paragraph, is it still appropriate to build both a python-mkdocs and a python3-mkdocs package? Unless I hear otherwise, this will be my plan. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778270: libterm-size-perl-perl: please make the build reproducible
Source: libterm-size-perl-perl
Version: 0.029-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 libterm-size-perl-perl could not be built reproducibly.
The attached patch removes timestamps from the build system. Once
applied, libterm-size-perl-perl can be built reproducibly in our current
reproducible
toolchain.
[1]: https://wiki.debian.org/ReproducibleBuilds
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
diff -urNad
libterm-size-perl-perl.orig/libterm-size-perl-perl-0.029/debian/patches/reproducible_build.patch
libterm-size-perl-perl/libterm-size-perl-perl-0.029/debian/patches/reproducible_build.patch
---
libterm-size-perl-perl.orig/libterm-size-perl-perl-0.029/debian/patches/reproducible_build.patch
1970-01-01 01:00:00.0 +0100
+++
libterm-size-perl-perl/libterm-size-perl-perl-0.029/debian/patches/reproducible_build.patch
2015-02-12 22:54:21.273756396 +
@@ -0,0 +1,11 @@
+--- libterm-size-perl-perl-0.029.orig/inc/Probe.pm
libterm-size-perl-perl-0.029/inc/Probe.pm
+@@ -105,7 +105,7 @@ my $PARAMS_TEMPLATE = PARAMS;
+
+ package Term::Size::Perl::Params;
+
+-# created @{[scalar localtime]}
++# created @{[`dpkg-parsechangelog --show-field Date`]}
+
+ use vars qw(\$VERSION);
+ \$VERSION = @{[MM-parse_version('Perl.pm')]};
diff -urNad
libterm-size-perl-perl.orig/libterm-size-perl-perl-0.029/debian/patches/series
libterm-size-perl-perl/libterm-size-perl-perl-0.029/debian/patches/series
---
libterm-size-perl-perl.orig/libterm-size-perl-perl-0.029/debian/patches/series
2015-02-12 22:28:55.667282334 +
+++ libterm-size-perl-perl/libterm-size-perl-perl-0.029/debian/patches/series
2015-02-12 23:01:04.627351493 +
@@ -1,2 +1,3 @@
fix_spelling.patch
manpage_has_bad_whatis_entry.patch
+reproducible_build.patch
Bug#775812: base: HP EliteBook 840 G1 laptop fails to halt/poweroff after 15/12/2015 upgrade
On Tue, 20 Jan 2015 12:42:05 +0100 Miguel miguel.ortiz-lombar...@igs.cnrs-mrs.fr wrote: I'm running Debian testing (jessie) on an HP EliteBook 840 G1 laptop. Everything goes reasonably well, even very well, except that after running apt-get update/upgrade on Monday (15 December) I cannot halt (poweroff) the computer. When I try to switch it off it just reboots. I manage to get it in sleep mode by pressing the the physical start button and this is what I'm doing since then. No previous problems in this sense before that upgrade. I have 'intel-microcode' and 'firmware-linux-free' installed from the beginning. I can confirm this problem on exactly the same notebook and with 'intel-microcode' installed as well. After that report I was able to sometimes halt the computer correctly either from the gnome interface or from the console. I would like to add that I also didn't succeed in halting the notebook by using the GRUB command 'halt', it just rebooted after entering this command. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776599: python-watchdog: please provide Python3 package
Hello, I require python3-watchdog, because it is required by python-mkdocs, which is required by the latest version of djangorestframework. I am about to upload your python-pathtools_0.1.2-2.dsc to unstable; I imagine it will get stuck in new for a while. If you provide me an updated version of python-watchdog, I will upload that for you too. Thanks. -- Brian May br...@microcomaustralia.com.au
Bug#778274: mauve: please make the build reproducible
Source: mauve Version: 20140821-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 mauve could not be built reproducibly. The attached patch removes timestamps from the build system. Once applied, mauve can be built reproducibly in our current reproducible toolchain. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff -urNad mauve.orig/mauve-20140821/debian/rules mauve/mauve-20140821/debian/rules --- mauve.orig/mauve-20140821/debian/rules 2015-02-12 23:49:53.696111641 + +++ mauve/mauve-20140821/debian/rules 2015-02-12 23:54:10.779458633 + @@ -4,6 +4,7 @@ # Uncomment this to turn on verbose mode. #export DH_VERBOSE=1 +BUILD_DATE := $(shell dpkg-parsechangelog --show-field Date) build: build-stamp build-arch: build-stamp @@ -29,8 +30,8 @@ mkdir -p debian/mauve/usr/src/mauve cp -a $(filter-out debian, $(wildcard .??* *)) \ debian/mauve/usr/src/mauve/ - tar -c --gzip -f $(CURDIR)/debian/mauve/usr/src/mauve.tar.gz \ - -C debian/mauve/usr/src mauve + GZIP=-9n tar -c --gzip -f $(CURDIR)/debian/mauve/usr/src/mauve.tar.gz \ + -C debian/mauve/usr/src --mtime=$(BUILD_DATE) mauve rm -rf debian/mauve/usr/src/mauve # Build architecture-independent files here.
Bug#743310: rsnapshot: Program calls with arguments containing quotations mark don't work anymore
Le lundi 09 février 2015 à 23:07 +, Christoph Egger a écrit : Package: rsnapshot Version: 1.3.1-4 Followup-For: Bug #743310 Hi! Hi, Guess it has something to do with additional quoting. Makes rsnapshot mostly useless for me. I'm sorry to have introduced such a problem by cherry-picked the upstream patch; the last known author is about to abandon the maintenance of rsnapshot (due to inactivity) to other users to fix some old code base of the software (https://github.com/bebehei/rsnapshot/issues/1). I've missed the freeze deadline by trying to update rsnapshot to the last upstream git repo (there was lots of changes and improvements i wanted to be done and the project start to be inactive) and it is too late for this important fix. I'll try to look further on the take over to see what happen. /etc/rsnapshot.conf # ssh has no args passed by default, but you can specify some here. # ssh_args-i /root/.ssh/id_rsa_backup /bin/cp -al /srv/rsnapshot/daily.0 /srv/rsnapshot/daily.1 /usr/bin/rsync -ax --delete --numeric-ids --relative --delete-excluded \ --rsh=/usr/bin/ssh -i /root/.ssh/id_rsa_backup \ user@host:path \ /srv/rsnapshot/daily.0/entry/ rsync: Failed to exec /usr/bin/ssh -i /root/.ssh/id_rsa_backup: No such file or directory (2) rsync error: error in IPC code (code 14) at pipe.c(85) [Receiver=3.1.1] rsync: connection unexpectedly closed (0 bytes received so far) [Receiver] rsync error: error in IPC code (code 14) at io.c(226) [Receiver=3.1.1] -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages rsnapshot depends on: ii liblchown-perl 1.01-2+b1 ii logrotate 3.8.7-1+b1 ii perl5.20.1-5 ii rsync 3.1.1-2+b1 Versions of packages rsnapshot recommends: ii openssh-client [ssh-client] 1:6.7p1-3 rsnapshot suggests no packages. -- Configuration Files: /etc/cron.d/rsnapshot changed [not included] /etc/rsnapshot.conf changed [not included] -- no debconf information signature.asc Description: This is a digitally signed message part
Bug#778272: magic: please make the build reproducible
Source: magic
Version: 7.5.241-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 magic could not be built reproducibly.
The attached patch removes timestamps from the build system. Once
applied, magic can be built reproducibly in our current reproducible
toolchain.
[1]: https://wiki.debian.org/ReproducibleBuilds
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
diff -urNad magic.orig/magic-7.5.241/debian/patches/07-reproducible-build.patch
magic/magic-7.5.241/debian/patches/07-reproducible-build.patch
--- magic.orig/magic-7.5.241/debian/patches/07-reproducible-build.patch
1970-01-01 01:00:00.0 +0100
+++ magic/magic-7.5.241/debian/patches/07-reproducible-build.patch
2015-02-12 23:12:09.332451746 +
@@ -0,0 +1,11 @@
+--- magic-7.5.241.orig/tcltk/Makefile
magic-7.5.241/tcltk/Makefile
+@@ -8,7 +8,7 @@ SRCS = tclmagic.c
+
+ include ${MAGICDIR}/defs.mak
+
+-DFLAGS += -DMAGIC_DATE=\`date`\
++DFLAGS += -DMAGIC_DATE=\`dpkg-parsechangelog -l../debian/changelog
--show-field Date`\
+ CLEANS += magic.sh magic.tcl magicexec magicdnull
+
+ TCL_FILES = \
diff -urNad magic.orig/magic-7.5.241/debian/patches/series
magic/magic-7.5.241/debian/patches/series
--- magic.orig/magic-7.5.241/debian/patches/series 2015-02-12
22:30:06.606443393 +
+++ magic/magic-7.5.241/debian/patches/series 2015-02-12 23:12:06.200314190
+
@@ -4,3 +4,4 @@
04-fhs-images.patch
05-readline-reference-removal.patch
06-script-adjustments.patch
+07-reproducible-build.patch
Bug#777635: [Python-modules-team] Bug#777635: python-odf: please make the build reproducible
On 2015-02-12 17:44, Chris Lamb wrote: How about changing doxygen to default to HTML_TIMESTAMP=NO in Debian? Whilst this would benefit the reproducible project, I worry this would be a little too invasive and unexpected as a general default. I don't think so, but let us ask the maintainer: Matthias, to make builds reproducible, we need to eliminate timestamps and such stuff from build results. Do you think, not having timestamps in HTML generated by doxygen would be a useful default? Maybe even acceptable by upstream? Otherwise, all Debian packages that use doxygen need to be changed to use HTML_TIMESTAMP=NO. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778253: Library version
Control: notfound -1 3.1.2-11ghigo Control: found -1 3.1.2-10 On Thu, Feb 12, 2015 at 09:04:44PM +0100, Goffredo Baroncelli wrote: I noticed only now that the library version reported is the 3.1.2-11ghigo. This is a my mistake. 3.1.2-11ghigo is the library which I rebuild with the patch. The problem is related to the 3.1.2-10. BR G.Baroncelli Adding the above control messages updates the version number tracked in the bug tracking system. Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777706: A couple of patches
I've attached here two debdiffs for a couple of options which may be helpful. It looks like the underlying bug has been fixed between versions 1.1 and 1.2 of NUT-Monitor, as the configuration directory is now being created with a sensible mode (0700). The attached patch `fix-permissions-on-start.debdiff' causes NUT-Monitor to detect and correct unsafe permissions on ~/.nut-monitor automatically when it is started. It also includes a NEWS item explaining this. The second patch, `just-warn.debdiff' merely includes a NEWS item explaining the problem and suggesting a fix. Hopefully one of these approaches may be sufficient. -- Michael Fincham Catalyst fix-permissions-on-start.debdiff Description: Binary data just-warn.debdiff Description: Binary data pgpKU9VLZRsEZ.pgp Description: PGP signature
Bug#737750: debian-installer: Netboot initrd does not download ata-modules or sata-modules udebs
I would like to mention that I've just hit this bug. I've got a handful of dell laptops here that will install perfectly via DVD, but the netboot image fails to load the drivers for the sata controller. I've confirmed that the network is functional, and watched a tcpdump of the installer downloading the installer components from three different mirrors. The netboot images are completely missing a handful of drivers according to this link: http://stackoverflow.com/questions/26524888/debian-missing-firmware-with-pxe-installation And it appears that the drivers are not being downloaded from the mirror for some reason. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778212: closed by Ben Hutchings b...@decadent.org.uk
On Thu, 2015-02-12 at 22:08 +0100, Adam Borowski wrote: On Thu, Feb 12, 2015 at 05:21:14PM +, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the src:linux package: #778212: linux: please build the kernel and udebs on x32 It has been closed by Ben Hutchings b...@decadent.org.uk. No, you need to make the installer use the amd64 packages for this. 1. d-i cannot currently use packages from a foreign architecture (same applies for example to i386 on non-ancient hardware) 2. neither can it use udebs (needed to boot d-i itself) We have multiarch now and I have no intention of adding more fake-architecture packages as a workaround for non-multiarch-aware tools (in fact I'd like to remove those that we have now, wherever the real architecture is a release architecture). 3. amd64 kernels currently have x32 syscalls disabled unless a special argument is passed on the command line. This is fragile, especially if fancy combinations of bootloader with preseeding are involved. Right, so you'll want to add that parameter to the initial configuration in grub-installer. I'm not going to force reopen this, as you know more about Debian kernel packaging than me (duh), but at least in my unofficial x32 release I'm going to use kernel+udebs with this patch, unless you can enlighten me. Would you please elaborate a bit about what do I understand wrong? And what the plans for foreign kernels in d-i are? My plan is that you implement this since you're adding the first architecture that needs it. Ben. -- Ben Hutchings Make three consecutive correct guesses and you will be considered an expert. signature.asc Description: This is a digitally signed message part
Bug#755722: systemd must sync systemclock to RTC on shutdown
You really should CC the the submitter when responing. On Tuesday 10 February 2015 09:56:28, Martin Pitt wrote: Control: severity -1 normal Stefan Fritsch [2015-01-31 10:19 +0100]: severity 755722 serious retitle 755722 systemd must sync systemclock to RTC on shutdown This is severity inflation according to https://www.debian.org/Bugs/Developer#severities ; adjusting back to original severity. No. It breaks other software, like fsck and make. I would call make an unrelated package which would make severity critical appropriate. I also disagree with the retitling, FTR. Systemd must make sure that the system clock does not go backwards, which causes all kinds of problems, with file systems and with other software. To achieve that, systemd has to sync the system time to RTC on shutdown. I disagree. As the discussion showed, it is in no way clear why the system time should be more accurate than the hardware clock; on most hardware it will be the other way around. I don't deny that. But monotonic time is more important than accurate time. You have not commented on that in any way. On long running systems, even if nothing modifies the system clock the normal drift between system time and RTC can cause the system time to go backwards when the system is rebooted. Therefore the system time must be synced to the RTC on shutdown. IMHO the only proper time to write the hardware clock is when we know the system time is correct, i. e. after an NTP sync or when the user sets it manually. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778261: Buffer overflow in GIF encoder
Control: tags -1 moreinfo On Thu, 12. Feb 23:13 Moritz Muehlenhoff j...@debian.org wrote: Package: byzanz Severity: important Tags: security Hi, this was reported by Red Hat: https://bugzilla.redhat.com/show_bug.cgi?id=852481 I'm afraid there are no further details, but maybe you can get in touch with upstream; I suppose Red Hat had contacted them and it might already be fixed by now? Hi Moritz, I have been trying to find out more about this security issue but so far without having any luck. Apparently the bug was reported 2,5 years ago but there are no hints at redhat's bug tracker which could help us or would at least point us to the affected code in question. Why did they escalate this to seclists.org just now? http://seclists.org/oss-sec/2015/q1/447 I checked upstream's git repository but I could not find any commits related to some kind of security issue with the GIF encoder or the playback tool. https://git.gnome.org/browse/byzanz/ However I know for sure, if upstream released a fix it would be included in Debian. The package is up to date and only some minor language updates from November 2014 are currently missing. I couldn't find anything useful at Fedora either. http://pkgs.fedoraproject.org/cgit/byzanz.git/ I will keep an eye on this Red Hat bug report but at the moment I just have not enough information to work on something. Regards, Markus signature.asc Description: Digital signature
Bug#778273: simplepie: please make the build reproducible
Source: simplepie
Version: 1.3.1+dfsg-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 simplepie could not be built reproducibly.
The attached patch removes timestamps from the build system. Once
applied, simplepie can be built reproducibly in our current reproducible
toolchain.
[1]: https://wiki.debian.org/ReproducibleBuilds
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
diff -urNad
simplepie.orig/simplepie-1.3.1+dfsg/debian/patches/reproducible_build.patch
simplepie/simplepie-1.3.1+dfsg/debian/patches/reproducible_build.patch
--- simplepie.orig/simplepie-1.3.1+dfsg/debian/patches/reproducible_build.patch
1970-01-01 01:00:00.0 +0100
+++ simplepie/simplepie-1.3.1+dfsg/debian/patches/reproducible_build.patch
2015-02-12 23:36:57.665902167 +
@@ -0,0 +1,11 @@
+--- simplepie-1.3.1+dfsg.orig/build/compile.php
simplepie-1.3.1+dfsg/build/compile.php
+@@ -67,7 +67,7 @@ $compiled = preg_replace(#\n\n\n+#, \
+ // Hardcode the build
+ $compiled = str_replace(
+ define('SIMPLEPIE_BUILD', gmdate('YmdHis',
SimplePie_Misc::get_build())),
+- define('SIMPLEPIE_BUILD', ' . gmdate('YmdHis', time()) . '),
++ define('SIMPLEPIE_BUILD', ' . gmdate('YmdHis',
strtotime(`dpkg-parsechangelog --show-field Date`)) . '),
+ $compiled
+ );
+
diff -urNad simplepie.orig/simplepie-1.3.1+dfsg/debian/patches/series
simplepie/simplepie-1.3.1+dfsg/debian/patches/series
--- simplepie.orig/simplepie-1.3.1+dfsg/debian/patches/series 2015-02-12
23:35:00.124727344 +
+++ simplepie/simplepie-1.3.1+dfsg/debian/patches/series2015-02-12
23:36:54.613767783 +
@@ -1,3 +1,4 @@
include_idn.patch
cache_directory.patch
fix_compile_file.patch
+reproducible_build.patch
Bug#778276: jnr-posix: Please update it to 3.0.9 or a more recent release
Package: src:jnr-posix Version: 1.1.8-2 Severity: wishlist As title says. -- System Information: Debian Release: 7.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.13-0.bpo.1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#778277: wget memory problem in mirror mode, possible memory leak
Package: wget Version: 1.13.4-3+deb7u2 Severity: important hi, i have tryed to use wgets mirror mode to mirror a webserver with a lot of content. it seams to work grate at first, downloaded robots.txt at first and done its job. some time later i realised that my box started to swap, nothing unusual... After that i got some serius performace problems and i realiced that ram and swap were full. That was the last thing i could do after my system frezzed entirely... After some time my box became usable again and the dmesg reported a lot of problems related to a high system load. At last there was a statement about that the kernel killed wget because of to much memory consumtion. here is extract: [269277.634832] Out of memory: Kill process 4049 (wget) score 780 or sacrifice child [269277.634843] Killed process 4049 (wget) total-vm:5596716kB, anon-rss:4111532kB, file-rss:56kB i have just a command lige this: $ wget -a wgetlog -m http://domain.tld/path/ and let it run and this is the resould please fix that. After my system recovered from that odd situation i discovered another odd bug which occoured with my mate desktop enviorment. mate-settings-daemon got 99% cpu load and the numlock led on my keyboard was switching on and of rapidly. ill report that bug next. thanks in advance and keep up the good work greetings treaki -- System Information: Debian Release: 7.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages wget depends on: ii dpkg 1.16.15 ii install-info 4.13a.dfsg.1-10 ii libc6 2.13-38+deb7u6 ii libgcrypt111.5.0-5+deb7u2 ii libgnutls262.12.20-8+deb7u2 ii libgpg-error0 1.10-3.1 ii libidn11 1.25-2 ii zlib1g 1:1.2.7.dfsg-13 wget recommends no packages. wget suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#737750: debian-installer: Netboot initrd does not download ata-modules or sata-modules udebs
Greg Bell greg.b...@artemech.com (2015-02-12): I would like to mention that I've just hit this bug. I've got a handful of dell laptops here that will install perfectly via DVD, but the netboot image fails to load the drivers for the sata controller. I've confirmed that the network is functional, and watched a tcpdump of the installer downloading the installer components from three different mirrors. Great, please attach /var/log/syslog from both a DVD-based install and from a netboot-based install. Please mention the netboot files you're serving as well (even if the relevant information should be in syslog already, that wouldn't hurt). Mraw, KiBi. signature.asc Description: Digital signature
Bug#777752: partman-efi: x32 port
Package: partman-efi
Version: 60
Severity: wishlist
Tags: d-i patch
User: debian-...@lists.debian.org
Usertags: port-x32 di-x32
Hi!
Please apply the attached patch. It adds support for the x32 architecture.
The patch follows in every case amd64 code paths, as x32 is a new ABI atop
the amd64 kernel. The patch can be applied directly to the d-i/partman-efi
git repository.
If you want to test, as the patch-set for x32 in d-i involves around twenty
packages, you'll want ready packages from the repository at debian-x32.org.
Complete d-i isos are available at http://debian-x32.org/#debian-installer
while debs/udebs/modified sources at http://ftp.debian-x32.org/debian/
-- System Information:
Debian Release: 8.0
APT prefers unstable
APT policy: (600, 'unstable'), (500, 'unreleased'), (50, 'experimental')
Architecture: x32 (x86_64)
Kernel: Linux 3.19.0-x32 (SMP w/6 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
From 4ae9c282d11f364a6b1b92207807a76a08d1bedd Mon Sep 17 00:00:00 2001
From: Adam Borowski kilob...@angband.pl
Date: Thu, 12 Feb 2015 07:33:04 +0100
Subject: [PATCH] Add support for x32.
---
commit.d/format_efi | 2 +-
debian/control | 2 +-
fstab.d/efi | 2 +-
init.d/efi | 4 ++--
4 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/commit.d/format_efi b/commit.d/format_efi
index a78444a..223ebae 100755
--- a/commit.d/format_efi
+++ b/commit.d/format_efi
@@ -4,7 +4,7 @@
ARCH=$(archdetect)
case $ARCH in
-i386/*|amd64/*)
+i386/*|amd64/*|x32/*)
new_efi_fs=fat32
;;
*)
diff --git a/debian/control b/debian/control
index a91db3b..e83c29f 100644
--- a/debian/control
+++ b/debian/control
@@ -9,6 +9,6 @@ Vcs-Git: git://anonscm.debian.org/d-i/partman-efi.git
Package: partman-efi
Package-Type: udeb
-Architecture: i386 ia64 amd64 arm64
+Architecture: i386 ia64 amd64 arm64 x32
Depends: partman-base (= 114), efi-modules, dosfstools-udeb, ${misc:Depends}
Description: Add to partman support for EFI System Partitions
diff --git a/fstab.d/efi b/fstab.d/efi
index 14b6696..42b0c6f 100755
--- a/fstab.d/efi
+++ b/fstab.d/efi
@@ -4,7 +4,7 @@
ARCH=$(archdetect)
case $ARCH in
-i386/mac|amd64/mac)
+i386/mac|amd64/mac|x32/mac)
# Not yet sure what to do on Intel Macs. Mounting the EFI System
# Partition on /boot/efi will change the behaviour of grub-install,
# so it seems best to avoid it for the moment.
diff --git a/init.d/efi b/init.d/efi
index 7b71990..cc9ad61 100755
--- a/init.d/efi
+++ b/init.d/efi
@@ -12,7 +12,7 @@ if [ -d /proc/efi ] || [ -d /sys/firmware/efi ]; then
/var/lib/partman/efi
else
case $ARCH in
- i386/mac|amd64/mac)
+ i386/mac|amd64/mac|x32/mac)
# Intel Macs have an EFI partition, regardless of
# whether we're currently booted using BIOS
# compatibility or not (if we are, we won't be able to
@@ -88,7 +88,7 @@ log Found $NUM_ESP ESPs, $NUM_NO non-ESPs
if [ $NUM_ESP = 0 ] [ $NUM_NO -gt 0 ]; then
case $ARCH in
- i386/*|amd64/*)
+ i386/*|amd64/*|x32/*)
db_input critical partman-efi/non_efi_system || true
db_go || exit 1
db_fset partman-efi/non_efi_system seen true
--
2.1.4
Bug#777753: gcc: LTO produces unreproducible debug information
Source: gcc-4.9 Version: 4.9.2-10 Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: randomness toolchain X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Forwarded: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65015 The GCC produced binaries seem to be only reproducible when not using link time optimization. This was discussed on the mailing list [1]. Both Jérémy Bobbio and Richard Biener pointed me in the direction of debug information which contained artifacts from the randomly generated temporary files of the LTO builds. The last test [2] showed that these really seemed to be the culprit of the problem. In the meantime, Richard Biener proposed patches which can solve this problem. I've compiled my own version of gcc-4.9 using the attached patch and can confirm that the LTO builds are now working perfectly fine and no changes to the affected packages are necessary anymore. Other versions of gcc might also have this problem but this is right now only for the default gcc version used by the build infrastructure. A small testcase is attached to the upstream bug. [1] http://lists.alioth.debian.org/pipermail/reproducible-builds/Week-of-Mon-20150209/000933.html [2] http://lists.alioth.debian.org/pipermail/reproducible-builds/Week-of-Mon-20150209/000942.htmldiff -u gcc-4.9-4.9.2/debian/rules.patch gcc-4.9-4.9.2/debian/rules.patch --- gcc-4.9-4.9.2/debian/rules.patch +++ gcc-4.9-4.9.2/debian/rules.patch @@ -232,6 +232,7 @@ sys-auxv-header \ libcilkrts-targets \ go-use-gold \ + drop_opt \ ifeq ($(with_softfloat),yes) debian_patches += arm-multilib-soft-float only in patch2: unchanged: --- gcc-4.9-4.9.2.orig/debian/patches/drop_opt.diff +++ gcc-4.9-4.9.2/debian/patches/drop_opt.diff @@ -0,0 +1,28 @@ +Bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65015 + +--- a/src/gcc/dwarf2out.c b/src/gcc/dwarf2out.c +@@ -19196,6 +19196,9 @@ gen_producer_string (void) + case OPT__sysroot_: + case OPT_nostdinc: + case OPT_nostdinc__: ++ case OPT_fpreprocessed: ++ case OPT_fltrans_output_list_: ++ case OPT_fresolution_: + /* Ignore these. */ + continue; + default: +@@ -23984,8 +23987,11 @@ dwarf2out_finish (const char *filename) + gen_remaining_tmpl_value_param_die_attribute (); + + /* Add the name for the main input file now. We delayed this from +- dwarf2out_init to avoid complications with PCH. */ +- add_name_attribute (comp_unit_die (), remap_debug_filename (filename)); ++ dwarf2out_init to avoid complications with PCH. ++ Avoid doing this for LTO produced units as it adds random ++ tempfile names. */ ++ if (!in_lto_p) ++add_name_attribute (comp_unit_die (), remap_debug_filename (filename)); + if (!IS_ABSOLUTE_PATH (filename) || targetm.force_at_comp_dir) + add_comp_dir_attribute (comp_unit_die ()); + else if (get_AT (comp_unit_die (), DW_AT_comp_dir) == NULL)
