Bug#756729: [DSE-Dev] Bug#756729: selinux-policy-default: Setting SELinux to enforce results in not configured network interface at boot time
Hello Mika, some more observations: I found a workaround: Changing 'allowed-hotplug eth0' to 'auto eth0' in /etc/network/interfaces fixes the problem for me. In the cases where this problem occurs, the /sys/class/net/eth0/operstate is 'down'. Therefore the hotplug function will not pick up the device. But why and how does (not) enforcing influence the setting of the device's operstate? Kind regards Andre -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#692249: sata boot+grub unknown filesystem without boot=on
Hello. Do you still remember this old bug from late-2012? Do you still have any issues outlined there? I weren't able to reproduce it meantime, and both qemu and seabios undergone several releases. Can we close this bugreport now maybe? :) Thanks, /mjt 31.12.2012 01:03, Michael Tokarev wrote: > 31.12.2012 00:43, Gianluigi Tiesi wrote: >> On 12/29/12 15:57, Michael Tokarev wrote: > [] vm -m 1024 -snapshot -device ahci,id=ahci0,bus=pci.0,addr=0x5 -drive file=/dev/sda,if=none,id=drive-sata0-0-0,format=raw,boot=on -device ide-hd,bus=ahci0.0,drive=drive-sata0-0-0,id=sata0-0-0 >>> >>> This is not scsi, this is ahci, FWIW. >> >> Yes true, but boot=on option was made for scsi, so why it makes work my ahci >> setup that instead would not work? I mean it should be unrelated but instead >> looks like related. > > Well. boot=on was made for general usage, it works (or worked) for > any bootable device, including scsi and ahci and network and other > stuff. It was a quick hack to allow booting from devices not > directly supported by seabios, and is not supported by upstream > anymore. > but if I run: kvm -m 1024 -snapshot -device ahci,id=ahci0,bus=pci.0,addr=0x5 -drive file=/dev/sda,if=none,id=drive-sata0-0-0,format=raw -device ide-hd,bus=ahci0.0,drive=drive-sata0-0-0,id=sata0-0-0 grub loads but it's unable to identify the filesystem >>> >>> Well. Which version of seabios is that? I'm asking because >>> this does not boot at all with current seabios+qemu-kvm from >>> wheezy: guest bios does not find any boot device. If in your >>> case guest bios finds the boot device and loads grub, it must >>> be some other version of either qemu-kvm or seabios. >> >> I'm on sid, and the just updated seabios 1.7.1-1 exposes same behavior >> qemu-kvm is 1.1.2+dfsg-3 > > Interesting. Okay. So I need some way to reproduce this. > Can you please tell us what do you use as the guest? What > is it, how it was setup, etc? Maybe it is enough to do a > fresh install of some distribution to expose this issue? > > [] >> Unfortunately bootindex options changes nothing > > Ok. > >> here grub2 without boot=on >> >> Booting from Hard Disk... >> GRUB loading. >> Welcome to GRUB! >> >> error: unknown filesystem. >> Entering rescue mode... >> grub rescue> ls >> (hd0) (hd0,msdos4) (hd0,msdos3) (hd0,msdos2) (hd0,msdos1) (fd0) >> grub rescue> ls (hd0,msdos4) >> error: unknown filesystem. > > Oh well. It looks like grub is unable to _read_ the drive. > > I need a way to reproduce this :) > > I'll try doing some installing/booting here when time permits. > Maybe you can provide some instructions or maybe a guest image > to speed things up... ;) > >> while it works fine with boot=on > > Ok. So it appears to be some grub+seabios issue with the > correct/modern way of booting things, while old/legacy boot > option works fine. > > Thank you! > > /mjt > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756729: [DSE-Dev] Bug#756729: selinux-policy-default: Setting SELinux to enforce results in not configured network interface at boot time
Hello Mika, looks that my yesterday's reply was lost - maybe because of the attachments. Attached to this mail you find the lost mail. The dhcp module was already loaded: root@debselinux01:~# sestatus SELinux status: enabled SELinuxfs mount:/sys/fs/selinux SELinux root directory: /etc/selinux Loaded policy name: default Current mode: enforcing Mode from config file: enforcing Policy MLS status: enabled Policy deny_unknown status: denied Max kernel policy version: 26 root@debselinux01:~# semodule -l apm 1.11.0 dbus1.15.0 devicekit 1.1.0 dhcp1.9.0 dmidecode 1.4.0 gpg 2.4.0 lvm 1.13.0 netutils1.11.0 ptchown 1.1.0 ssh 2.2.0 tcpd1.4.0 tzdata 1.4.0 unconfined 3.3.0 usbmodules 1.2.0 Trying to load it again does not change things - the problem still exists: root@debselinux01:~# semodule -i /usr/share/selinux/default/dhcp.pp root@debselinux01:~# semodule -l apm 1.11.0 dbus1.15.0 devicekit 1.1.0 dhcp1.9.0 dmidecode 1.4.0 gpg 2.4.0 lvm 1.13.0 netutils1.11.0 ptchown 1.1.0 ssh 2.2.0 tcpd1.4.0 tzdata 1.4.0 unconfined 3.3.0 usbmodules 1.2.0 Then I tried: root@debselinux01:~# cd /usr/share/selinux/default root@debselinux01:/usr/share/selinux/default# for f in *.pp; do echo "Loading $f" ; semodule -i $f; done Loading acct.pp Loading ada.pp Loading afs.pp [...] Some are failing because of unmet dependencies; therefore another round: root@debselinux01:/usr/share/selinux/default# for f in *.pp; do echo "Loading $f" ; semodule -u $f; done With the result that it now reliable fails :-) Every time after reboot eth0 is not available. The only AVC I found in the logging is the one about mounts and modules.dep. Also here: after disabling SELinux (setting it to permissive) the problem is not reproducible. (Tried 47 reboots). Kind regards Andre P.S.: I tried to reproduce this with Jessie: 428 reboots without any occurrence of the problem. - The lost mail - Hello Mika, very strange things happen: yesterday this bug happened (as I remember) every time I booted. Today this changed somehow: it only happens from time to time - but at least it happens Because the network interface is not working when the problem appears, I attached some console screenshots with the output of the commands you suggested. My idea then was that this might not be a problem of the selinux-policy package. Therefore I set SELINUX=permissive and wrote a small script which connects via network interface to the machine and reboots it. I stopped the test after 238 reboots - not one occurrence of the problem. I set SELINUX back to enforcing, and the problem occurs any some 1-4 boots. So there might be the possibility that is has something to do with the selinux-policy. I manage to create a minimal Debian 7 VM with SELinux set to enforced where this problem occurs (from time to time). If you want, I can provide the VM - and my reboot-test script. (The size of the compressed image is about 265MiByte.) Kind regards Andre -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756824: nvidia-driver: lost display the temperature of the GPU
On Fri, Aug 1, 2014 at 10:19 PM, YK wrote: > Package: nvidia-driver > Version: 340.24-2 > Severity: minor > > Hi, > Sorry my bad English. > > After upgrade to 340** lost display the temperature of the GPU. > Perhaps this is due, and there is no nvidia-settings. > Also on the card GF8400GS. I uploaded nvidia-settings over a week ago, but it's currently stuck in NEW, awaiting ftpmaster review. See #756240 for details. Regards, Vincent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756818: update-rc.d: error: insserv rejected the script header
02.08.2014 09:15, Michael Tokarev wrote: > Control: reassign -1 libvirt-bin > > 02.08.2014 05:17, 積丹尼 Dan Jacobson wrote: >> Package: qemu-system-x86 >> Version: 2.1+dfsg-1 >> Severity: grave >> >> Setting up qemu-system-x86 (2.1+dfsg-1) ... >> update-rc.d: warning: start and stop actions are no longer supported; >> falling back to defaults >> insserv: FATAL: service libvirt-bin has to exists for service libvirt-guests >> insserv: exiting now! >> update-rc.d: error: insserv rejected the script header >> dpkg: error processing package qemu-system-x86 (--configure): >> subprocess installed post-installation script returned error exit status 1 >> dpkg: dependency problems prevent configuration of qemu-kvm: >> qemu-kvm depends on qemu-system-x86 (>= 1.7.0+dfsg-2~); however: >> Package qemu-system-x86 is not configured yet. >> >> dpkg: error processing package qemu-kvm (--configure): >> dependency problems - leaving unconfigured Just to make it clear. I don't think it is a bug in libvirt (-bin or -guests) per se, to me it looks more like libvirt-bin service has been disabled manually (like, removing /etc/init.d/libvirt-bin) while other service (libvirt-guests) depends on it, hence insserv complains when installing an unrelated package, because current system-wide set of services can not be started due to a missing dependency. But this has obviously nothing to do with qemu, -- qemu tries to install its init.d script which fails because of other services. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756822: update-rc.d: warning: start and stop actions are no longer supported; falling back to default
Control: severity -1 minor Control: merge 751754 -1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756824: nvidia-driver: lost display the temperature of the GPU
Package: nvidia-driver Version: 340.24-2 Severity: minor Hi, Sorry my bad English. After upgrade to 340** lost display the temperature of the GPU. Perhaps this is due, and there is no nvidia-settings. Also on the card GF8400GS. Thanks for attention. -- Package-specific info: uname -a: Linux aspera 3.14-2-amd64 #1 SMP Debian 3.14.13-2 (2014-07-24) x86_64 GNU/Linux /proc/version: Linux version 3.14-2-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-5) ) #1 SMP Debian 3.14.13-2 (2014-07-24) /proc/driver/nvidia/version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.24 Wed Jul 2 14:24:20 PDT 2014 GCC version: gcc version 4.8.3 (Debian 4.8.3-6) lspci 'VGA compatible controller [0300]': 02:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83b8] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: nvidia dmesg: [0.00] No AGP bridge found [0.00] No AGP bridge found [0.00] Console: colour VGA+ 80x25 [0.425276] vgaarb: device added: PCI::02:00.0,decodes=io+mem,owns=io+mem,locks=none [0.425362] vgaarb: loaded [0.425423] vgaarb: bridge control possible :02:00.0 [1.308113] Linux agpgart interface v0.103 [ 12.733073] nvidia: module license 'NVIDIA' taints kernel. [ 12.750854] vgaarb: device changed decodes: PCI::02:00.0,olddecodes=io+mem,decodes=none:owns=none [ 12.751284] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 340.24 Wed Jul 2 14:24:20 PDT 2014 [ 19.977284] nvidia :02:00.0: irq 45 for MSI/MSI-X OpenGL and NVIDIA library files installed: lrwxrwxrwx 1 root root 15 Jul 31 01:35 /etc/alternatives/glx -> /usr/lib/nvidia lrwxrwxrwx 1 root root 43 Jul 31 01:35 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 43 Jul 31 01:35 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 51 Jul 31 01:35 /etc/alternatives/glx--libnvidia-cfg.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libnvidia-cfg.so.1 lrwxrwxrwx 1 root root 25 Jul 31 01:35 /etc/alternatives/glx--linux-libglx.so -> /usr/lib/nvidia/libglx.so lrwxrwxrwx 1 root root 42 Jul 31 01:35 /etc/alternatives/glx--nvidia-blacklists-nouveau.conf -> /etc/nvidia/nvidia-blacklists-nouveau.conf lrwxrwxrwx 1 root root 36 Jul 31 01:35 /etc/alternatives/glx--nvidia-bug-report.sh -> /usr/lib/nvidia/nvidia-bug-report.sh lrwxrwxrwx 1 root root 29 Jul 31 01:35 /etc/alternatives/glx--nvidia_drv.so -> /usr/lib/nvidia/nvidia_drv.so lrwxrwxrwx 1 root root 23 Jul 31 01:35 /etc/alternatives/nvidia -> /usr/lib/nvidia/current lrwxrwxrwx 1 root root 51 Jul 31 01:35 /etc/alternatives/nvidia--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/current/libGL.so.1 lrwxrwxrwx 1 root root 51 Jul 31 01:35 /etc/alternatives/nvidia--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/current/libGL.so.1 lrwxrwxrwx 1 root root 33 Jul 31 01:35 /etc/alternatives/nvidia--libglx.so -> /usr/lib/nvidia/current/libglx.so lrwxrwxrwx 1 root root 59 Jul 31 01:35 /etc/alternatives/nvidia--libnvidia-cfg.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/current/libnvidia-cfg.so.1 lrwxrwxrwx 1 root root 44 Jul 31 01:35 /etc/alternatives/nvidia--nvidia-bug-report.sh -> /usr/lib/nvidia/current/nvidia-bug-report.sh lrwxrwxrwx 1 root root 32 Jul 31 01:35 /etc/alternatives/nvidia--nvidia-modprobe.conf -> /etc/nvidia/nvidia-modprobe.conf lrwxrwxrwx 1 root root 37 Jul 31 01:35 /etc/alternatives/nvidia--nvidia_drv.so -> /usr/lib/nvidia/current/nvidia_drv.so lrwxrwxrwx 1 root root 50 Jul 31 01:35 /usr/lib/x86_64-linux-gnu/libGL.so.1 -> /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu lrwxrwxrwx 1 root root 58 Jul 31 01:35 /usr/lib/x86_64-linux-gnu/libnvidia-cfg.so.1 -> /etc/alternatives/glx--libnvidia-cfg.so.1-x86_64-linux-gnu -rw-r--r-- 1 root root 43998904 Jul 3 05:03 /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.340.24 lrwxrwxrwx 1 root root 17 Jul 20 15:31 /usr/lib/x86_64-linux-gnu/libnvidia-ml.so -> libnvidia-ml.so.1 lrwxrwxrwx 1 root root 22 Jul 20 15:31 /usr/lib/x86_64-linux-gnu/libnvidia-ml.so.1 -> libnvidia-ml.so.340.24 -rw-r--r-- 1 root root 879072 Jul 3 05:51 /usr/lib/x86_64-linux-gnu/libnvidia-ml.so.340.24 -rw-r--r-- 1 root root12696 Jul 3 05:07 /usr/lib/x86_64-linux-gnu/libnvidia-tls.so.340.24 -rw-r--r-- 1 root root 11523 Aug 1 19:50 /var/log/Xorg.0.log -rw-r--r-- 1 root root 13504 Aug 1 08:41 /var/log/Xorg.0.log.old -rw-r--r-- 1 root root 13969 Jun 26 02:16 /var
Bug#756822: update-rc.d: warning: start and stop actions are no longer supported; falling back to default
Control: severity -1 normal Control: merge 751754 -1 Stop doing this nonsense. Thank you. /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756818: update-rc.d: error: insserv rejected the script header
Control: reassign -1 libvirt-bin 02.08.2014 05:17, 積丹尼 Dan Jacobson wrote: > Package: qemu-system-x86 > Version: 2.1+dfsg-1 > Severity: grave > > Setting up qemu-system-x86 (2.1+dfsg-1) ... > update-rc.d: warning: start and stop actions are no longer supported; falling > back to defaults > insserv: FATAL: service libvirt-bin has to exists for service libvirt-guests > insserv: exiting now! > update-rc.d: error: insserv rejected the script header > dpkg: error processing package qemu-system-x86 (--configure): > subprocess installed post-installation script returned error exit status 1 > dpkg: dependency problems prevent configuration of qemu-kvm: > qemu-kvm depends on qemu-system-x86 (>= 1.7.0+dfsg-2~); however: > Package qemu-system-x86 is not configured yet. > > dpkg: error processing package qemu-kvm (--configure): > dependency problems - leaving unconfigured > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756822: update-rc.d: warning: start and stop actions are no longer supported; falling back to default
Package: qemu-system-x86 Version: 2.1+dfsg-2 update-rc.d: warning: start and stop actions are no longer supported; falling back to default -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756823: transmission-gtk: picking up dep on gconf*
Package: transmission-gtk Looking at remaining packages on my gnome install that dep on gconf, transmission appears to be the final piece. Looking at the configure script from upstream, it appears as though the use of gconf is completely a debianism, via: transmission-gtk.gconf-defaults Is it possible to consider splitting this to its own package? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756821: installation-reports: Successfull system install
Package: installation-reports Severity: normal Tags: d-i -- Package-specific info: Boot method: DVD Image version: Debian GNU/Linux 7.6.0 amd64 20140712-14:11 → http://cdimage.debian.org/debian-cd/7.6.0/amd64/bt-dvd/ Date: 2014-08-01 Machine: Toshiba Satellite L455-SP2903R Partitions: /boot - / - /home Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Clock/timezone setup: [O] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Install tasks: [O] Install boot loader:[E] Overall install:[O] Comments/Problems: After several tries, GRUB was not installed. However, LILO could be installed. -- == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="7 (wheezy) - installer build 20130613+deb7u2+b1" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux redstar 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] (rev 07) lspci -knn: Subsystem: Toshiba America Info Systems Device [1179:ff00] lspci -knn: Kernel driver in use: agpgart-intel lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) lspci -knn: Subsystem: Toshiba America Info Systems Device [1179:ff01] lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a43] (rev 07) lspci -knn: Subsystem: Toshiba America Info Systems Device [1179:ff01] lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 03) lspci -knn: Subsystem: Toshiba America Info Systems Device [1179:ff00] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1a.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 03) lspci -knn: Subsystem: Toshiba America Info Systems Device [1179:ff00] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1a.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 [8086:2939] (rev 03) lspci -knn: Subsystem: Toshiba America Info Systems Device [1179:ff00] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1a.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 [8086:293c] (rev 03) lspci -knn: Subsystem: Toshiba America Info Systems Device [1179:ff00] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 03) lspci -knn: Subsystem: Toshiba America Info Systems Device [1179:ff00] lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 [8086:2940] (rev 03) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 [8086:2944] (rev 03) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 [8086:2946] (rev 03) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.5 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 [8086:294a] (rev 03) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 [8086:2934] (rev 03) lspci -knn: Subsystem: Toshiba America Info Systems Device [1179:ff00] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 [8086:2935] (rev 03) lspci -knn: Subsystem: Toshiba America Info Systems Device [1179:ff00] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 [8086:2936] (rev 03) lspci -knn: Subsystem: Toshiba America Info Systems Device [1179:ff00] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 [8086:293a] (rev 03) lspci -knn: Subsystem: Toshiba America Info Systems Device [1179:ff00] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev 93) l
Bug#756820: one tap enough
Note that one tap of Fn Up Arrow or Fn Down Arrow is enough to 'wake up the brightness' from the depths. There are no need for several taps. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756820: keep hands off intel_backlight/brightness when switching to tty1-6
Package: src:linux Version: 3.14.13-2 On Lenovo (my other non-Lenovo are fine) G580, switching from X on tty7 to any of tty1...6 gives a very dim screen. So one must hit Fn Up Arrow (or Fn Down Arrow), after which one can read the screen again. Switching back to tty7 and then back again to tty1-6 recreates the problem. Running printf '%3d %3d %3d | %3d %3d %3d\n' $( cat \ /sys/class/backlight/intel_backlight/*brightness \ /sys/class/backlight/acpi_video0/*brightness ) before and after hitting a Fn Down Arrow shows 7 7 976 | 15 15 15 838 838 976 | 14 14 15 Therefore something is messing with /sys/class/backlight/intel_backlight/brightness , knocking it down to 7, when it should keep its hands off! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756778: RFS: charmap.app/0.3~rc1-2 [RC] -- Character map for GNUstep
tags 756778 moreinfo thanks Hi Yavor, Please, complete the Debian copyright years in d/copyright. You can get data at https://packages.qa.debian.org/c/charmap.app.html and from d/changelog. Be careful with each maintainer/team and years. The rest of the package is good. Regards, Eriberto -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756789: ITP: spork -- DRb (Distributed Ruby) server for testing frameworks
On Sat, Aug 02, 2014 at 02:00:09AM +0200, gregor herrmann wrote: > > Please note that there is a libspork-perl package which installs a > /usr/bin/spork binary. > Just in case the ruby spork tries to do the same, then we have to > find a solution :) Oops, it looks like I uploaded spork too soon then. The ruby spork install a /usr/bin/spork binary. I didn't check because I thought perl one was a library. -- 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#756247: Failed to start unit user@1000.service: Unknown unit: user@0000.service
Control: tags -1 moreinfo On Mon, Jul 28, 2014 at 01:17:51AM +0200, Michael Biebl wrote: > Package: systemd-shim > Version: 6-4 > Severity: normal > When running logind v205+ under systemd-shim 6-4 / cgmanager, I get this > error message: > Failed to start unit user@0.service: Unknown unit: user@0.service > Failed to start user service: Unknown unit: user@0.service > This is particularly visible on the console, where the error message is > shown on the users console upon login. > Ther user@.service provides a per user session which is started by the > pam_systemd module. [1] has a few more details. And what are you expecting systemd-shim to do to fix this? By definition, systemd-shim is used only when PID1 is not systemd; it is therefore meaningless to start a systemd unit, and certainly meaningless to start a systemd unit whose function is to spawn a systemd user session. Are you expecting libpam-systemd to now enforce the use of systemd user sessions? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Bug#756819: no support for xorg-xserver 1.16
Package: virtualbox-guest-x11 Version: 4.3.14-dfsg-1 Severity: grave I apologize, I'm not sure exactly which package this should be filed against, but I'm pretty sure this is the correct one. I am on a Windows 8.1 host running Debian jessie. I updated xorg-xserver etc. to the current version in testing, 1.16.0-1. However, I am no longer able to use the X11-related guest utilities. The relevant output from VBoxLinuxAdditions.run in the guest additions ISO: Installing the Window System drivers Warning: unknown version of the X Window System installed. Not installing X Window System drivers. Looking at the code, the issue is obvious. It is searching for /opt/VBoxGuestAdditions-4.3.14/lib/VBoxGuestAdditions/vboxvideo_drv_116.so, which does not exist. This support needs to be added. I'm sure that's easier said than done, and is probably an upstream problem. Meanwhile, however, this package needs to change its xorg-xserver-core dependency, adding (<< 1.16.0). -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages virtualbox-guest-x11 depends on: ii dpkg 1.17.10 ii libc6 2.19-7 ii libx11-6 2:1.6.2-2 ii libxcomposite1 1:0.4.4-1 ii libxdamage11:1.1.4-2 ii libxext6 2:1.3.2-1 ii libxfixes3 1:5.0.1-2 ii libxmu62:1.1.2-1 ii libxrandr2 2:1.4.2-1 ii libxt6 1:1.1.4-1 ii virtualbox-guest-utils 4.3.14-dfsg-1 ii xserver-xorg-core [xorg-video-abi-18] 2:1.16.0-1 virtualbox-guest-x11 recommends no packages. virtualbox-guest-x11 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#756818: update-rc.d: error: insserv rejected the script header
Package: qemu-system-x86 Version: 2.1+dfsg-1 Severity: grave Setting up qemu-system-x86 (2.1+dfsg-1) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults insserv: FATAL: service libvirt-bin has to exists for service libvirt-guests insserv: exiting now! update-rc.d: error: insserv rejected the script header dpkg: error processing package qemu-system-x86 (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of qemu-kvm: qemu-kvm depends on qemu-system-x86 (>= 1.7.0+dfsg-2~); however: Package qemu-system-x86 is not configured yet. dpkg: error processing package qemu-kvm (--configure): dependency problems - leaving unconfigured -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756791: Acknowledgement (xfig: Segfaults when editing points of an arc)
For what it is worth, I ran into more segfaults from seemingly innoculous events (clicking inside of dialog boxes?) with c-3. I downgraded xfig to 1:3.2.5.b-3 (stable) and it worked like a charm for a good 2 hours worth of heavy drawing. -- Keith Hellman #include khell...@mcprogramming.comfrom disclaimer import standard khell...@mines.edu -*- public key @ pgp.mit.edu 9FCF40FD Y!M: mcprogramming AIM/ICQ: 485403897 jabber: mrtu...@jabber.org irc: freenode.net as mrtuple -*- "... an elegant weapon for a more civilized age." -- Obi-Wan Kenobi signature.asc Description: Digital signature
Bug#756817: dpkg: warning: unable to delete old directory '/etc/apparmor...
Package: libvirt-bin Version: 1.2.7~rc2-1 .placeholder files cause: Unpacking libvirt-bin (1.2.7~rc2-1) over (1.2.4-3.2) ... dpkg: warning: unable to delete old directory '/etc/apparmor.d/abstractions': Directory not empty dpkg: warning: unable to delete old directory '/etc/apparmor.d/libvirt': Directory not empty dpkg: warning: unable to delete old directory '/etc/sasl2': Directory not empty dpkg: warning: unable to delete old directory '/etc/libvirt/qemu/networks': Directory not empty dpkg: warning: unable to delete old directory '/etc/libvirt/qemu': Directory not empty dpkg: warning: unable to delete old directory '/etc/libvirt/nwfilter': Directory not empty dpkg: warning: unable to delete old directory '/etc/libvirt': Directory not empty dpkg: warning: unable to delete old directory '/var/log/libvirt/lxc': Directory not empty dpkg: warning: unable to delete old directory '/var/log/libvirt/qemu': Directory not empty dpkg: warning: unable to delete old directory '/var/log/libvirt/uml': Directory not empty dpkg: warning: unable to delete old directory '/var/log/libvirt': Directory not empty dpkg: warning: unable to delete old directory '/var/lib/libvirt/qemu': Directory not empty dpkg: warning: unable to delete old directory '/var/lib/libvirt': Directory not empty dpkg: warning: unable to delete old directory '/var/cache/libvirt/qemu': Directory not empty dpkg: warning: unable to delete old directory '/var/cache/libvirt': Directory not empty Preparing to unpack .../libvirt0_1.2.7~rc2-1_i386.deb ... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756816: apt: "apt-get upgrade packagename" should not set packagename to manually installed
Package: apt Version: 1.1~exp2 Severity: normal Dear APT Developers, it seems that -- despite the documentation suggests otherwise -- you now can pass package names as parameter to "apt-get upgrade" and it does what you expect: Try to upgrade only that package. But it also seems to set the given package to "manually installed" for which there is no reason at all: # apt-get upgrade zsh Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... zsh is already the newest version. zsh set to manually installed. < This shouldn't happen! The following packages were automatically installed and are no longer required: […] -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (110, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.15-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages apt depends on: ii debian-archive-keyring 2012.4 ii gnupg 1.4.18-2 ii libapt-pkg4.13 1.1~exp2 ii libc6 2.19-7 ii libgcc1 1:4.9.1-4 ii libstdc++6 4.9.1-4 apt recommends no packages. Versions of packages apt suggests: ii apt-doc 1.0.6 ii aptitude0.6.11-1 ii dpkg-dev1.17.10 ii python-apt 0.9.3.8 ii synaptic0.81.2 ii wajig 2.14 -- 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#756789: ITP: spork -- DRb (Distributed Ruby) server for testing frameworks
On Fri, 01 Aug 2014 14:45:06 -0300, Miguel Landaeta wrote: > * Package name: spork > Version : 0.9.2 > Upstream Author : Tim Harper > * URL : https://github.com/sporkrb/spork > * License : MIT/X > Programming Lang: Ruby > Description : DRb (Distributed Ruby) server for testing frameworks > > Spork is a test server (similar to the script/spec_server that used to be > provided by rspec-rails), Please note that there is a libspork-perl package which installs a /usr/bin/spork binary. Just in case the ruby spork tries to do the same, then we have to find a solution :) Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- NP: STS: Wahnsinn signature.asc Description: Digital Signature
Bug#756815: ruby: missing man pages for testrb, rdoc, gem
Package: ruby Version: 1:2.1.0.1 Severity: normal Dear Maintainer, On jessie: $ man rdoc man: warning: /usr/share/man/man1/rdoc.1.gz is a dangling symlink No manual entry for rdoc etc. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ruby depends on: ii ruby2.1 2.1.2-2 ruby recommends no packages. Versions of packages ruby suggests: pn ri pn ruby-dev -- 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#756814: emdebian-grip: [INTL:pt] Portuguese translation
Package: emdebian-grip Version: 3.1.0 Tags: l10n, patch Severity: wishlist Updated Portuguese translation for emdebian-grip's UI's messages. Translator: Américo Monteiro Feel free to use it. For translation updates please contact 'Last Translator' or the Portuguese Translation Team . -- Melhores cumprimentos/Best regards, Américo Monteiro emdebian-grip_3.1.0_pt.po.gz Description: GNU Zip compressed data
Bug#756631: udev: hang during boot when using upstart with newer udev
reassign 756631 upstart thanks Am 31.07.2014 17:14, schrieb Juerg Haefliger: > Package: udev > Version: 208-6 > > Lately, booting never finishes when using upstart in combination with a > recent version of udev. This seems to be caused by the sysv init script > /etc/init.d/udev-finish, introduced by the following commit: > > commit c746e2ad194e222e423a60756a6a15e443ddd6b2 > Author: Marco d'Itri > Date: Sat Apr 26 20:25:25 2014 +0200 > > Copy the temporary rules from /run/ to /etc/ > > They are created by write_net_rules in early boot and need to be copied > to the root file system once it has been remounted read/write. > > > Disabling the init script (update-rc.d udev-finish disable) or disabling > makefile-style booting seems to 'fix' the problem. > > Attached is the boot log with verbose upstart and a strace'd starpart. > > To reproduce: Install a base sid system, install upstart, reboot. I'm going to re-assign this to the upstart maintainers since udev ships a native upstart job for udev-finish (/etc/init/udev-finish.conf) and you probably will get the best help/assitance there. Please follow up there. If the udev-finish.conf upstart job needs an update, please provide a tested patch and re-assign back to udev -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#709255: Your mail
On Tue, 03 Dec 2013 20:13:50 +0100 0 1 wrote: > Since this bug still seems open, the same happened to me, instead I > didn't have Gnash but the proprietary Flash plugin. > > Running: > update-alternatives --config flash-mozilla.so > And selecting Lightspark helped the situation and made it work inside > browser. > > However, it still isn't listed within iceweasel's browser plugins. Does it still happen with latest iceweasel versions? Alternatives system is supposed to activate one and only one flash plugin at a time. Plugin name is always "Shockwave Flash". Are you sure it's not there? -- G..e -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#750660: netfilter-persistent: error in systemd file
The stated fix works for me as well. Please implement it soon so debsums stops bugging me :) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#558628: Bug#753679: schroedinger: : use dh-autoreconf to fix ppc64el FTBFS
Control: tags -1 + pending
Hi,
The unability to compile this package is a problem for ports being
added recently (OpenRISC/or1k, ppc64el, ...) since they don't have
older versions to rely on, and many packages depend on them as
build-dependencies to compile, so this package (among many others) is
blocking a good portion of the archive to compile cleanly for these
ports.
I am preparing a NMU (diff attached) to fix the bugs above (see
headers), uploaded to DELAYED/5 as per guidelines in [1] -- since this
package is needed to compile many other packages, the bugs are open
for several weeks in one case and years in another and didn't receive
any update from the maintainers (and there are other bugs open for
years without any recent activity), and the changes should not affect
the behaviour of the package in the other architectures.
[1] http://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu
Please let me know if you want me to cancel the upload, or can assist
you in any way.
Cheers.
--
Manuel A. Fernandez Montecelo
diff -Nru schroedinger-1.0.11/debian/changelog
schroedinger-1.0.11/debian/changelog
--- schroedinger-1.0.11/debian/changelog2012-04-26 07:13:54.0
+0100
+++ schroedinger-1.0.11/debian/changelog2014-08-01 22:56:42.0
+0100
@@ -1,3 +1,12 @@
+schroedinger (1.0.11-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Run dh-autoreconf to update config.{sub,guess} and
+{libtool,aclocal}.m4, necessary for some new ports. Thanks
+Brahadambal Srinivasan. (Closes: #753679, #558628)
+
+ -- Manuel A. Fernandez Montecelo Fri, 01 Aug 2014 22:54:16
+0100
+
schroedinger (1.0.11-2) unstable; urgency=low
* Team upload.
diff -Nru schroedinger-1.0.11/debian/control schroedinger-1.0.11/debian/control
--- schroedinger-1.0.11/debian/control 2012-04-26 07:12:04.0 +0100
+++ schroedinger-1.0.11/debian/control 2014-08-01 22:57:36.0 +0100
@@ -5,6 +5,7 @@
Uploaders: Sebastian Dröge
Build-Depends: cdbs (>= 0.4.93~),
debhelper (>= 8.1.3~),
+ dh-autoreconf,
liborc-0.4-dev (>= 1:0.4.16),
pkg-config
Build-Depends-Indep: gtk-doc-tools (>= 1.0)
diff -Nru schroedinger-1.0.11/debian/rules schroedinger-1.0.11/debian/rules
--- schroedinger-1.0.11/debian/rules2012-04-26 07:03:26.0 +0100
+++ schroedinger-1.0.11/debian/rules2014-08-01 22:57:03.0 +0100
@@ -1,6 +1,7 @@
#!/usr/bin/make -f
include /usr/share/cdbs/1/rules/debhelper.mk
+include /usr/share/cdbs/1/rules/autoreconf.mk
include /usr/share/cdbs/1/class/gnome.mk
include /usr/share/cdbs/1/rules/utils.mk
Bug#756813: postgrey: Couldn't unlink "/var/run/postgrey.pid" [Permission denied]
Package: postgrey Version: 1.34-1.3 Severity: normal Dear Maintainer, * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? /etc/init.d postgrey stop * What was the outcome of this action? Log reports "Couldn't unlink "/var/run/postgrey.pid" [Permission denied]" * What outcome did you expect instead? No error. Most likely the pid file should be in a directory that the user postgrey can modify (such as /var/run/postgrey/postgrey.pid) rather than /var/run/postgrey.pid, since /var/run is not writable by postgrey. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13.7-x86_64-linode38 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages postgrey depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.52 ii libberkeleydb-perl 0.53-1+b1 ii libnet-dns-perl0.68-1.2 ii libnet-server-perl 2.007-3 ii perl 5.18.2-2+b1 ii ucf3.0027+nmu1 Versions of packages postgrey recommends: ii libnet-rblclient-perl 0.5-2 ii libparse-syslog-perl 1.10-2 ii postfix2.10.2-1 postgrey suggests no packages. -- debconf information: postgrey/1.32-3_changeport: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756812: nfs-common: rpc.gssd crashes while mounting an encrypted nfs4 filesystem
Control: reassign -1 libtirpc1
Control: found -1 0.2.4-1
On Fri, Aug 01, 2014 at 11:41:12PM +0200, Євгеній Мещеряков wrote:
> rpc.gssd started crashing again when mounting an encrypted nfs4
> filesystem.
> The dmesg contains:
> [ 391.284130] rpc.gssd[1756]: segfault at b5a ip 7f70bb3d772f sp
> 7fff5765a080 error 4 in libgssapi_krb5.so.2.2[7f70bb3c4000+45000]
> [ 391.284935] NFS: nfs4_discover_server_trunking unhandled error -32.
> Exiting with error EIO
This is a regression in libtirpc, which is no longer linked against gssglue
like it's supposed to be.
$ debdiff ftp/pool/main/libt/libtirpc/libtirpc1_0.2.{3-2,4-1}_i386.deb
File lists identical (after any substitutions)
Control files: lines which differ (wdiff format)
Depends: libc6 (>= 2.16), [-libgssglue1-] {+libcomerr2 (>= 1.01),
libgssapi-krb5-2 (>= 1.10+dfsg~), libk5crypto3 (>= 1.6.dfsg.2), libkrb5-3 (>=
1.6.dfsg.2)+}
Installed-Size: [-203-] {+251+}
Maintainer: [-Debian QA Group -] {+Anibal Monsalve
Salazar +}
Version: [-0.2.3-2-] {+0.2.4-1+}
$
Aníbal, I see that you have applied a patch in your most recent upload in
order to get the package to build against gssglue. This patch appears to be
incomplete, because regardless of the headers used at compile time, libtirpc
is clearly linking against MIT KRB5 directly. This is a bug; libtirpc and
nfs-utils need to be linking against the same provider of GSS, or segfaults
ensue. If there is a reason for switching the linkage away from gssglue,
then a coordinated transition would be needed.
libtirpc has two reverse dependencies in the archive, rpcbind and nfs-utils.
I would appreciate it if you would test both of them when making changes to
libtirpc.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: Digital signature
Bug#754793: RFS: mosquitto/1.2.1-2 RC
Hi Eriberto, Thanks for taking the time to start a review. > 1. Update the Standards-Version from 3.9.4 to 3.9.5. Done > 2. d/copyright: please, update the years (include 2014, because I > found it in your upstream code). Done. > 3. d/docs: The final user doesn't compiles codes. So, send compiling > instructions to user is unusual. Please, remove the compiling.txt. Yes, that makes complete sense. Removed. > 4. All readmes should be put in /usr/share/doc/mosquitto. Do you have > a reason to put them in /etc? These READMEs are simple explanations of empty directories, it doesn't make sense to put them in share/doc in my opinion. I'm following the example of packages such as sysv-rc, udev, sudo, grub, lighttpd, procps that all do this. > 5. The example must be put in /usr/share/doc/mosquitto/examples ($ man > dh_installexamples). I have fixed this. > 6. There is a .conf in /etc/init. What is this? This is an upstart config file as Cameron already mentioned. I've uploaded a new version (actually this is now upstream version 1.3.3) to mentors. Thanks again, Roger -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756760: systemd: stale session prevents hibernation of workstation
reassign 756760 systemd-shim thanks Am 01.08.2014 um 14:50 schrieb Martin Steigerwald: > Package: systemd > Version: 208-1 > Severity: important > > Dear Maintainer, > > I tried to hibernate but got same annoying authorization requester > *after* KDE locked its desktop as described in bug #747939. > > This time not due to a second KDE session but due to stale sessions: > > ms@mango:~> loginctl >SESSIONUID USER SEAT > 2 2012 ms seat0 > 84 0 root seat0 > 87 0 root seat0 > .. > systemd is still at 208-1 as I won't upgrade it at the cost of removing > sysvinit-core. If you are still using sysvinit-core, this means it's a bug in systemd-shim. Re-assigning accordingly. Most likely a duplicate of [1] [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756076 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#756726: [Pkg-chromium-maint] Bug#756726: chromium kills XFCE session
control: reassign -1 fglrx-driver control: forcemerge 739054 -1 On Fri, Aug 1, 2014 at 12:04 AM, Jerry Quinn wrote: > Starting up chromium kills my XFCE session. I've reported this to > upstream. Bug #384747. This is a known issue with fglrx-driver. Avoid that, and things will work fine. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756468: [DSE-Dev] Bug#756468: Please think about fixing this bug in stable
Hi, Andreas Florath wrote: > IMHO this bug should be fixed in stable, because it prevents > installing packages that use addgroup when SELinux is set to > enforcing. I haven't found time to investigate the issue, but if you have loaded the "unconfined" module and use normal "apt-get" (not se_apt-get etc.) commands as unconfined root, everything should work. You could at least use this as a workaround for the time being. Cheers, Mika -- signature.asc Description: PGP signature
Bug#756812: nfs-common: rpc.gssd crashes while mounting an encrypted nfs4 filesystem
Package: nfs-common Version: 1:1.2.8-6 Severity: serious Hello, rpc.gssd started crashing again when mounting an encrypted nfs4 filesystem. The dmesg contains: [ 391.284130] rpc.gssd[1756]: segfault at b5a ip 7f70bb3d772f sp 7fff5765a080 error 4 in libgssapi_krb5.so.2.2[7f70bb3c4000+45000] [ 391.284935] NFS: nfs4_discover_server_trunking unhandled error -32. Exiting with error EIO The output from the rpc.gssd and gdb follows: handling gssd upcall (/run/rpc_pipefs/nfs/clnte) handle_gssd_upcall: 'mech=krb5 uid=0 service=* enctypes=18,17,16,23,3,1,2 ' handling krb5 upcall (/run/rpc_pipefs/nfs/clnte) process_krb5_upcall: service is '*' Full hostname for 'thor.kazna.de' is 'thor.kazna.de' Full hostname for 'loki.local' is 'loki.local' No key table entry found for LOKI$@KAZNA.DE while getting keytab entry for 'LOKI$@KAZNA.DE' No key table entry found for root/loki.lo...@kazna.de while getting keytab entry for 'root/loki.lo...@kazna.de' No key table entry found for nfs/loki.lo...@kazna.de while getting keytab entry for 'nfs/loki.lo...@kazna.de' No key table entry found for host/loki.lo...@kazna.de while getting keytab entry for 'host/loki.lo...@kazna.de' Processing keytab entry for principal 'nfs/loki.kazna...@kazna.de' We will NOT use this entry (nfs/loki.kazna...@kazna.de) Processing keytab entry for principal 'nfs/loki.kazna...@kazna.de' We will NOT use this entry (nfs/loki.kazna...@kazna.de) Processing keytab entry for principal 'nfs/loki.kazna...@kazna.de' We will NOT use this entry (nfs/loki.kazna...@kazna.de) Processing keytab entry for principal 'nfs/loki.kazna...@kazna.de' We will NOT use this entry (nfs/loki.kazna...@kazna.de) Processing keytab entry for principal 'nfs/loki.kazna...@kazna.de' We WILL use this entry (nfs/loki.kazna...@kazna.de) Success getting keytab entry for nfs/*@KAZNA.DE Successfully obtained machine credentials for principal 'nfs/loki.kazna...@kazna.de' stored in ccache 'FILE:/tmp/krb5ccmachine_KAZNA.DE' INFO: Credentials in CC 'FILE:/tmp/krb5ccmachine_KAZNA.DE' are good until 1406965169 using FILE:/tmp/krb5ccmachine_KAZNA.DE as credentials cache for machine creds using environment variable to select krb5 ccache FILE:/tmp/krb5ccmachine_KAZNA.DE creating context using fsuid 0 (save_uid 0) creating tcp client for server thor.kazna.de DEBUG: port already set to 2049 creating context with server n...@thor.kazna.de Program received signal SIGSEGV, Segmentation fault. 0x76ac272f in ?? () from /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 (gdb) bt #0 0x76ac272f in ?? () from /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 #1 0x76ac33e2 in gss_init_sec_context () from /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 #2 0x77bcf863 in ?? () from /lib/x86_64-linux-gnu/libtirpc.so.1 #3 0x77bcfbf9 in authgss_create () from /lib/x86_64-linux-gnu/libtirpc.so.1 #4 0x77bcfcfc in authgss_create_default () from /lib/x86_64-linux-gnu/libtirpc.so.1 #5 0x00405126 in ?? () #6 0x00405bf2 in ?? () #7 0x0040685a in ?? () #8 0x00404aac in ?? () #9 0x00403941 in ?? () #10 0x76d18b45 in __libc_start_main (main=0x403690, argc=2, argv=0x7fffe0e8, init=, fini=, rtld_fini=, stack_end=0x7fffe0d8) at libc-start.c:287 #11 0x004039ae in ?? () -- Package-specific info: -- rpcinfo -- program vers proto port service 104 tcp111 portmapper 103 tcp111 portmapper 102 tcp111 portmapper 104 udp111 portmapper 103 udp111 portmapper 102 udp111 portmapper -- /etc/default/nfs-common -- NEED_STATD=no STATDOPTS= NEED_IDMAPD=yes NEED_GSSD=yes -- /etc/idmapd.conf -- [General] Verbosity = 0 Pipefs-Directory = /run/rpc_pipefs Domain = kazna.de [Mapping] Nobody-User = nobody Nobody-Group = nogroup -- /etc/fstab -- #thor.kazna.de:/ /srv/backups nfs sec=krb5p,rw,noatime,nodiratime,nodev,nosuid,noexec,proto=tcp,noauto,x-systemd.automount,x-systemd.device-timeout=60 0 0 -- /proc/mounts -- -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU cores) Locale: LANG=uk_UA.UTF-8, LC_CTYPE=uk_UA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nfs-common depends on: ii adduser 3.113+nmu3 ii initscripts 2.88dsf-53.2 ii libc6 2.19-7 ii libcap2 1:2.24-3 ii libcomerr2 1.42.11-2 ii libdevmapper1.02.1 2:1.02.85-2 ii libevent-2.0-5 2.0.21-stable-1 ii libgssglue1 0.4-2 ii libk5crypto31.12.1+dfsg-5 ii libkeyutils11.5.9-4 ii libkrb5-3 1.12.1+dfsg-5 ii libmount1 2.20.1-5.8 ii libnfsidmap20.25-5 ii libtirpc1 0.2.4-1 ii libwrap07.6.q-2
Bug#754796: RFP: puppetboard -- web interface to PuppetDB aiming to replace the reporting functionality of Puppet Dashboard.
On 13655 March 1977, Jonas Genannt wrote: >> > both packages are ready in git. Upstream need to add a correct >> > copyright statement, but he will do it next week. >> Very nice, thanks. >> Can/will you support a backport to wheezy? > I don't think. Mainly because I'm only a DM within the DD process and I need > to ask every > time for a sponsor. (saving sponsor requests for unstable uploads :)) DMs can upload to backports too, ... > But if you are willing to sponsor the packages, I can do it. ... but yes, need a sponsor initially. I can do that. Though from what I know you'll have fun with more than just puppetboard, I *think* it needs some pretty recent version of most of its dependencies, so the backports chain is probably a bit longer. Still, would love to have that, just have not enough time to do the actual work myself. Sponsoring is fine, but more is hard. -- bye, Joerg Ganneff seems to be quoting me a lot in his signature -- So. after movin my comuter, my usb keyboard anmous seems to be loosing events so some kys when typin fast is inored, and thmous kind ofmovingin large steps. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756729: [DSE-Dev] Bug#756729: selinux-policy-default: Setting SELinux to enforce results in not configured network interface at boot time
Hi Andre, most interesting is the output of semodule -l. SELinux refpolicy is modular, so that you only have to load the policy for the programs you actually use. Note that in your case you have loaded only some select modules, pretty much a minimal set of modules, which will provide only very basic functionality. Upon installation, the selinux-policy-default package in stable tries to guess which modules you could need and installs those. If you then install other software afterwards, you have to enable other modules yourself. To enable the dhcp module (which hopefully will fix your problem), use: # semodule -i /usr/share/selinux/default/dhcp.pp you will find all available modules in /usr/share/selinux/default/, just check which one sounds like you need it. You can also install all of them and then selectively disable some using # semodule -d dhcp (or equivalent for other module names, see semodule(8)), which is often easier. Note that having loaded "too many" modules usually only means selinux is not as effective in preventing acceses (if e.g. you don't have an ftp server installed, there is no need to allow ftp access), but it usually will not do much harm. We recognise that this situation (minimal set of default modules enable upon installation) is confusing for many users, which is why we changed this already in debian unstable, such that by default a much larger set (also including dhcp) of modules is installed. I hope this helps you to get up and running with selinux. Unfortunately, there is only very basic documentation about selinux on debian (the best I know is http://debian-handbook.info/browse/stable/sect.selinux.html from the debian administrator's handbook), but it is mostly analogous to how it works on RHEL and Fedora, so you can also read https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/SELinux_Users_and_Administrators_Guide/index.html Cheers, Mika -- signature.asc Description: PGP signature
Bug#747816: Review openalpr
Hallo Stefan, as promised some weeks ago, here's your review :) Here's an (unordered) list of thing I found during checking your package. Maybe you want to check them if they are valid and correct them? I just saw that the ITP is not owned by you. Did you coordinate with the one filing the ITP? (If so, you should document it there, if not you should ask Matt Hill if he intends to to the packaging or not... The bug's text is not clear here.) - Upstream released in the meantime 1.1.1 ... Can you update your package to the latest version? - The tarball does not match the upstream tarball. 7585916d11fef3ea88bba3249e839524 ../openalpr_1.1.0.orig.tar.gz d1446343788a52514e78afd33b73fe66 /home/tobi/Downloads/openalpr-1.1.0.tar.gz (Did you directly pull from the repository -- as there was a .git directory in it?) - d/README.source -- I think you don't need this file, let it go... :) - d/patches/* -- please add a dep3 header; does it make sense to send the patch upstream? - d/control -- as you are building a library I miss somehow a -dev package... Also the package description of the binary package openalpr needs to explain a little better what this package is for. Currently it only describes the libary, not the tool(s) you could find in the package. - d/copyright is incomplete and should be of the machine-readable debian/copyright file format (dep5) (licensecheck and /usr/lib/cdbs/licensecheck2dep5 can help you here, but you need anyway to check every file.. - any reason not to enable multiarch for the lib? - when building you should instruct cmake to be verbose (e.g show the complete gcc commandline... (I think you just need to "make VERBOSE=1") in d/rules) - the package does not build in a pdebuilder enviorment (chrpath not found; missing B-D?) Is chrpath really needed? - symbol files for c++ libraries are IMHO a little bit fragile and after installing chrpath it failed here. So you need to work on those or drop the symbol file for this moment) - you manually have a lots of manually added library dependencies on the binary packge --- are they needed? Shouldn't be shlibs:depends enough find the needed dependencies? nitpicks: - d/* -- I suggest to use wrap-and-sort to sort e.g the dependencies. - d/control -- there are some trailing white-spaces you should remove (wrap-and-sort will do it for you) - There are many "could avoid a useless dependency" warnings... Can you check if a --as-needed linker option would work? Ok, thats it for now. Thanks for working on the package, it's looks like a quite tricky package to do :) -- tobi signature.asc Description: This is a digitally signed message part
Bug#756811: src:nspr: add support for OpenRISC 1000 (or1k)
Package: src:nspr Version: 4.10.6-1 Severity: wishlist Tags: upstream patch Dear Maintainer, The attached patch adds support for the upcoming Debian architecture OpenRISC (or1k). -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- ./nspr/pr/include/md/_linux.cfg.orig 2014-08-01 22:11:46.763917524 +0200 +++ ./nspr/pr/include/md/_linux.cfg 2014-08-01 22:09:11.363033182 +0200 @@ -924,6 +924,51 @@ #define PR_BYTES_PER_WORD_LOG2 2 #define PR_BYTES_PER_DWORD_LOG2 3 +#elif defined(__or1k__) + +#undef IS_LITTLE_ENDIAN +#define IS_BIG_ENDIAN 1 + +#define PR_BYTES_PER_BYTE 1 +#define PR_BYTES_PER_SHORT 2 +#define PR_BYTES_PER_INT4 +#define PR_BYTES_PER_INT64 8 +#define PR_BYTES_PER_LONG 4 +#define PR_BYTES_PER_FLOAT 4 +#define PR_BYTES_PER_DOUBLE 8 +#define PR_BYTES_PER_WORD 4 +#define PR_BYTES_PER_DWORD 8 + +#define PR_BITS_PER_BYTE8 +#define PR_BITS_PER_SHORT 16 +#define PR_BITS_PER_INT 32 +#define PR_BITS_PER_INT64 64 +#define PR_BITS_PER_LONG32 +#define PR_BITS_PER_FLOAT 32 +#define PR_BITS_PER_DOUBLE 64 +#define PR_BITS_PER_WORD32 + +#define PR_BITS_PER_BYTE_LOG2 3 +#define PR_BITS_PER_SHORT_LOG2 4 +#define PR_BITS_PER_INT_LOG25 +#define PR_BITS_PER_INT64_LOG2 6 +#define PR_BITS_PER_LONG_LOG2 5 +#define PR_BITS_PER_FLOAT_LOG2 5 +#define PR_BITS_PER_DOUBLE_LOG2 6 +#define PR_BITS_PER_WORD_LOG2 5 + +#define PR_ALIGN_OF_SHORT 2 +#define PR_ALIGN_OF_INT 4 +#define PR_ALIGN_OF_LONG4 +#define PR_ALIGN_OF_INT64 4 +#define PR_ALIGN_OF_FLOAT 4 +#define PR_ALIGN_OF_DOUBLE 4 +#define PR_ALIGN_OF_POINTER 4 +#define PR_ALIGN_OF_WORD4 + +#define PR_BYTES_PER_WORD_LOG2 2 +#define PR_BYTES_PER_DWORD_LOG2 3 + #else #error "Unknown CPU architecture" --- ./nspr/pr/include/md/_linux.h.orig 2014-08-01 23:14:35.549052940 +0200 +++ ./nspr/pr/include/md/_linux.h 2014-08-01 23:09:27.011346747 +0200 @@ -55,6 +55,8 @@ #define _PR_SI_ARCHITECTURE "avr32" #elif defined(__m32r__) #define _PR_SI_ARCHITECTURE "m32r" +#elif defined(__or1k__) +#define _PR_SI_ARCHITECTURE "or1k" #else #error "Unknown CPU architecture" #endif @@ -123,6 +125,18 @@ #define _MD_ATOMIC_SET_PR_x86_64_AtomicSet #endif +#if defined(__or1k__) +#if defined(__GNUC__) +/* Use GCC built-in functions */ +#define _PR_HAVE_ATOMIC_OPS +#define _MD_INIT_ATOMIC() +#define _MD_ATOMIC_INCREMENT(ptr) __sync_add_and_fetch(ptr, 1) +#define _MD_ATOMIC_DECREMENT(ptr) __sync_sub_and_fetch(ptr, 1) +#define _MD_ATOMIC_ADD(ptr, i) __sync_add_and_fetch(ptr, i) +#define _MD_ATOMIC_SET(ptr, nv) __sync_lock_test_and_set(ptr, nv) +#endif +#endif + #if defined(__powerpc__) && !defined(__powerpc64__) #define _PR_HAVE_ATOMIC_OPS #define _MD_INIT_ATOMIC()
Bug#756769: icedove: Please upload the new upstream release (31)
Hello Sylvestre, On Fri, Aug 01, 2014 at 04:22:00PM +0200, Sylvestre Ledru wrote: > Version 31.0 has been released. Could you please upload the new upstream > release? you are right. :) Depended on lack of free time and the known FTBFS on kfreebsd* and armel Christoph hasen't uploaded the new version. I prepared in the between time the depended packages icedove-l10n and iceowl-l10n for the version 31 of icedove. Also I made some prework for Christoph in icedove and have locally running a current version 31 of icedove. But we need to get out of the FTBFS errors to get a transistion into testing with the current version so we want to fix this issues before we upload a next version. For kfreebsd it looks a little bit easier to do this than for armel. Mike had this is issue with a FTBFS on armel in the past too, but I don't have really understand how he has solved this error. As far as I can see it now the configure scripts a lacking support for less than armv7*. https://github.com/tijuca/icedove https://github.com/tijuca/icedove-l10n https://github.com/tijuca/iceowl-l10n 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#756810: linux-image-3.16-rc6-armmp: HDMI on wandboard/cubox-i no longer works
Package: src:linux Version: 3.16~rc6-1~exp1 Severity: normal With linux-image-3.15-trunk-armmp 3.15.5-1~exp1 which included patches applied from upstream, HDMI video output worked for me on both the Cubox i4pro and Wandboard Quad. The console framebuffer showed output, X with fbdev worked... Now with 3.16~rc6-1~exp1, which shold have the applied patches, there's no output. Perhaps other additional patches caused issues. I also tested with 3.16~rc5-1~exp1, no luck. hrm. Thanks for working on Debian kernel packaging! live well, vagrant -- Package-specific info: ** Version: Linux version 3.16-rc6-armmp (debian-ker...@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-5) ) #1 SMP Debian 3.16~rc6-1~exp1 (2014-07-21) ** Command line: console=ttymxc0,115200 ** Tainted: C (1024) * Module from drivers/staging has been loaded. ** Kernel log: [1.384242] mmc0: new high speed SDHC card at address 1234 [1.390289] mmcblk0: mmc0:1234 SA04G 3.63 GiB [1.398676] mmcblk0: p1 p2 p3 < p5 > [1.802878] PM: Starting manual resume from disk [1.807583] PM: Hibernation image partition 179:5 present [1.807592] PM: Looking for hibernation image. [1.809096] PM: Image not found (code -22) [1.809106] PM: Hibernation image not present or could not be loaded. [1.860617] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) [3.002967] systemd-udevd[260]: starting version 208 [3.354410] Registered IR keymap rc-empty [3.359051] input: gpio_ir_recv as /devices/soc0/ir-receiver/rc/rc0/input0 [3.366521] rc0: gpio_ir_recv as /devices/soc0/ir-receiver/rc/rc0 [3.374681] imx2-wdt 20bc000.wdog: timeout 60 sec (nowayout=0) [3.398170] i2c i2c-1: IMX I2C adapter registered [3.413338] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [3.453949] [drm] Initialized drm 1.1.0 20060810 [3.459654] SCSI subsystem initialized [3.484164] i2c i2c-2: IMX I2C adapter registered [3.511686] libata version 3.00 loaded. [3.542674] ahci-imx 220.sata: SSS flag set, parallel bus scan disabled [3.549529] imxdrm: module is from the staging directory, the quality is unknown, you have been warned. [3.549534] imxdrm: module is from the staging directory, the quality is unknown, you have been warned. [3.556139] IR Sony protocol handler initialized [3.556148] IR SANYO protocol handler initialized [3.562674] lirc_dev: IR Remote Control driver registered, major 243 [3.568302] rc rc0: lirc_dev: driver ir-lirc-codec (gpio-rc-recv) registered at minor = 0 [3.568306] IR LIRC bridge handler initialized [3.574839] IR NEC protocol handler initialized [3.579150] IR JVC protocol handler initialized [3.584020] input: MCE IR Keyboard/Mouse (gpio-rc-recv) as /devices/virtual/input/input1 [3.584623] IR MCE Keyboard/mouse protocol handler initialized [3.587476] imx_hdmi: module is from the staging directory, the quality is unknown, you have been warned. [3.592797] ci_hdrc ci_hdrc.0: ChipIdea HDRC found, lpm: 0; cap: f00c6100 op: f00c6140 [3.597022] ci_hdrc ci_hdrc.0: It is OTG capable controller [3.597522] ci_hdrc ci_hdrc.0: EHCI Host Controller [3.597781] ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 1 [3.606796] ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00 [3.607067] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [3.607074] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [3.607082] usb usb1: Product: EHCI Host Controller [3.607087] usb usb1: Manufacturer: Linux 3.16-rc6-armmp ehci_hcd [3.607092] usb usb1: SerialNumber: ci_hdrc.0 [3.607779] hub 1-0:1.0: USB hub found [3.607818] hub 1-0:1.0: 1 port detected [3.608715] ci_hdrc ci_hdrc.1: ChipIdea HDRC found, lpm: 0; cap: f00ee300 op: f00ee340 [3.611702] ci_hdrc ci_hdrc.1: doesn't support gadget [3.611712] ci_hdrc ci_hdrc.1: EHCI Host Controller [3.611956] ci_hdrc ci_hdrc.1: new USB bus registered, assigned bus number 2 [3.622801] ci_hdrc ci_hdrc.1: USB 2.0 started, EHCI 1.00 [3.623048] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 [3.623056] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [3.623062] usb usb2: Product: EHCI Host Controller [3.623069] usb usb2: Manufacturer: Linux 3.16-rc6-armmp ehci_hcd [3.623074] usb usb2: SerialNumber: ci_hdrc.1 [3.623758] hub 2-0:1.0: USB hub found [3.623801] hub 2-0:1.0: 1 port detected [3.651967] imx-spdif sound-spdif: ASoC: CPU DAI (null) not registered [3.651998] imx-spdif sound-spdif: snd_soc_register_card failed: -517 [3.652015] platform sound-spdif: Driver imx-spdif requests probe deferral [3.666015] imx-spdif sound-spdif: snd-soc-dummy-dai <-> 2004000.spdif mapping ok [3.770603] ahci-imx 220.sata: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode [3.771291] IR RC5(x) protocol handler initiali
Bug#756775: git tag does not tell one which chars are valid in tag names
Jonathan Nieder dixit: >and 'man 1 git check-ref-format' says Aah! >Any ideas for improving the wording in Documentation/git-tag.txt? Hm… will have to think about it. >E.g., should it have a note in the DESCRIPTION section, or should it >use the word "valid" to make searching within the file easier? I searched for that and “a-z”, yes, that would help, also maybe a regexp. bye, //mirabilos -- “ah that reminds me, thanks for the stellar entertainment that you and certain other people provide on the Debian mailing lists │ sole reason I subscribed to them (I'm not using Debian anywhere) is the entertainment factor │ Debian does not strike me as a place for good humour, much less German admin-style humour” -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#754463: RFS: pdf2htmlex/0.11+ds-1
* Johannes Schauer , 2014-07-30, 07:24: I do not understand why it fails for you but not for me. How did you run the tests? I ran sadt(1) in the freshly-unpacked source tree. I ran `adt-run -o /tmp/log --source pdf2htmlex_0.11+ds-1.dsc --- schroot sid-amd64-sbuild` This is what the adt-run manpage says about the --source option: "By default the package will also be built and the resulting binaries will be used to satisfy test dependencies" Presumably it also means that the built tree is used for running tests. (What I've been doing in my packages, as a defensive strategy against accidentally testing against not-installed code, is to copy all the bits necessary to run tests from the package directory to $ADTTMP, then chdir to $ADTTMP, and run tests from there.) Have you seen this thread on d-devel@? https://lists.debian.org/53ccf007.6020...@debian.org Yes, but how is it relevant to this? I'm a bit worried, because pdf2htmlex is built in C++11 mode, but it links to libraries built in C++98 mode. If I understand correctly, this is potentially a recipe for disaster. Now, it's probably not something that would stop me from uploading the package. Just wanted to make sure that you are aware of this problem. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756731: [DSE-Dev] Bug#756731: selinux-policy-default: Setting SELinux to enforce when using systemd some AVCs are logged during boot
Hello Mika, thank you very much for your detailed explanation. Looks that I miss some basics here. I'll try to reproduce the bugs I found with Jessie. (It might take some time, because I start vacation in the next days...) Thanks for your offer about the VMs - but I am able to setup a VM on my own ;-) Kind regards Andre -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#752178: [unetbootin] The resulting usb pendrive looping with menu.c32 error
Hi, have noticed the same today. Based on this Ubuntu bugreport: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752178 i have copied the following files: /usr/lib/syslinux/modules/bios/menu.c32 /usr/lib/syslinux/modules/bios/libutil.c32 to the root of the created USB stick to get the USB stick to work. P.S. As there is also no "menu32.c32" but a "menu.c32" in debian the title of this bugreport probably should be changed. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756790: tcpdump: FTBFS on kfreebsd-*
Hi, Yes, I already filed #756553 about this two days ago. If you care about kfreebsd you might want to get things moving on the kfreebsd-kernel-headers side. I have another RC bug which impacts libpcap open since June 7 with absolutely no action. If this holds up my testing migration I'll make tcpdump linux-any + hurd-i386 rather than have to wait for months for the kfreebsd maintainers to fix their RC bugs. Thanks, -- Romain Francoise http://people.debian.org/~rfrancoise/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756809: libvncserver: include ppc64el to acinclude.m4
Source: libvncserver
Severity: normal
Tags: patch
User: debian-powe...@lists.debian.org
Usertags: ppc64el
Dear Maintainer,
The package libvncserver fails to build from source on ppc64el.
The identification which is imported from acinclude.m4 to configure, does
not support ppc64el and the build breaks.
Since that piece of code is not generated by autoreconf, but comes from a
customized m4, I included the ppc64el part into it.
You can see the aforementioned modification in the patch attached.
Please let me know your comments.
Thanks!
Fernando
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: ppc64el (ppc64le)
Kernel: Linux 3.13-1-powerpc64le (SMP w/16 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru libvncserver-0.9.9+dfsg/debian/changelog libvncserver-0.9.9+dfsg/debian/changelog
--- libvncserver-0.9.9+dfsg/debian/changelog 2014-05-01 08:20:24.0 +
+++ libvncserver-0.9.9+dfsg/debian/changelog 2014-08-01 19:58:13.0 +
@@ -1,3 +1,10 @@
+libvncserver (0.9.9+dfsg-5ppc64el1) UNRELEASED; urgency=medium
+
+ * Added ppc64el to acinclude.m4, since the ABI identification is not being automatically
+generated with autoreconf in configure file.
+
+ -- Fernando Seiti Furusato Fri, 01 Aug 2014 19:57:05 +
+
libvncserver (0.9.9+dfsg-5) unstable; urgency=medium
* debian/patches/listenSock.patch:
diff -Nru libvncserver-0.9.9+dfsg/debian/patches/add-ppc64el.patch libvncserver-0.9.9+dfsg/debian/patches/add-ppc64el.patch
--- libvncserver-0.9.9+dfsg/debian/patches/add-ppc64el.patch 1970-01-01 00:00:00.0 +
+++ libvncserver-0.9.9+dfsg/debian/patches/add-ppc64el.patch 2014-08-01 19:58:42.0 +
@@ -0,0 +1,26 @@
+--- libvncserver-0.9.9+dfsg.orig/acinclude.m4
libvncserver-0.9.9+dfsg/acinclude.m4
+@@ -1137,7 +1137,10 @@ x86_64-*linux*|ppc*-*linux*|powerpc*-*li
+ x86_64-*linux*)
+ LD="${LD-ld} -m elf_i386"
+ ;;
+-ppc64-*linux*|powerpc64-*linux*)
++powerpc64le-*)
++ LD="${LD-ld} -m elf32lppclinux"
++ ;;
++powerpc64-*)
+ LD="${LD-ld} -m elf32ppclinux"
+ ;;
+ s390x-*linux*)
+@@ -1153,7 +1156,10 @@ x86_64-*linux*|ppc*-*linux*|powerpc*-*li
+ x86_64-*linux*)
+ LD="${LD-ld} -m elf_x86_64"
+ ;;
+-ppc*-*linux*|powerpc*-*linux*)
++powerpcle-*)
++ LD="${LD-ld} -m elf64lppc"
++ ;;
++powerpc-*)
+ LD="${LD-ld} -m elf64ppc"
+ ;;
+ s390*-*linux*)
diff -Nru libvncserver-0.9.9+dfsg/debian/patches/series libvncserver-0.9.9+dfsg/debian/patches/series
--- libvncserver-0.9.9+dfsg/debian/patches/series 2014-05-01 08:15:18.0 +
+++ libvncserver-0.9.9+dfsg/debian/patches/series 2014-08-01 19:58:37.0 +
@@ -3,3 +3,4 @@
format_string.patch
multiarch.patch
listenSock.patch
+add-ppc64el.patch
Bug#756468: Please think about fixing this bug in stable
Hello! I learned from a comment to another bug (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756731) that only bugs starting from 'important' will be fixed in stable. IMHO this bug should be fixed in stable, because it prevents installing packages that use addgroup when SELinux is set to enforcing. Please think about changing the severity to 'important' and fixing this bug. Kind regards Andre -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756808: open-vm-tools: vmtoolsd crashes with more than 16 network interfaces
Package: open-vm-tools Version: 2:8.8.0+2012.05.21-724730-1+nmu2 Severity: important Tags: upstream Dear Maintainer, We have a machine that has 19 interfaces (two physical, rest are vlans). This causes vmtoolsd to crash. This has been reported upstream here: http://sourceforge.net/p/open-vm-tools/tracker/158/ Let me know if you need any additional information, Thanks, -Nicholas Sielicki -- System Information: Debian Release: 7.6 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.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 Versions of packages open-vm-tools depends on: ii libc6 2.13-38+deb7u3 ii libdumbnet1 1.12-3.1 ii libfuse2 2.9.0-2+deb7u1 ii libgcc1 1:4.7.2-5 ii libglib2.0-0 2.33.12+really2.32.4-5 ii libicu48 4.8.1.1-12+deb7u1 ii libprocps01:3.3.3-3 ii libstdc++64.7.2-5 Versions of packages open-vm-tools recommends: ii ethtool 1:3.4.2-1 pn open-vm-dkms pn zerofree Versions of packages open-vm-tools suggests: ii open-vm-toolbox 2:8.8.0+2012.05.21-724730-1+nmu2 -- Configuration Files: /etc/vmware-tools/tools.conf changed [not included] -- 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#756807: apparmor: FTBFS with clang instead of gcc
Package: apparmor
Severity: minor
Tags: patch
User: pkg-llvm-t...@lists.alioth.debian.org
Usertags: clang-ftbfs
Hello,
Using the rebuild infrastructure, your package fails to build with clang
(instead of gcc).
Detected this kind of error:
http://clang.debian.net/status.php?version=3.4.2&key=UNDEF_REF
Full build log is available here:
http://clang.debian.net/logs/2014-06-16/apparmor_2.8.0-5.1_unstable_clang.log
Thanks,
Arthur
-- System Information:
Debian Release: jessie/sid (unstable)
Architecture: amd64 (x86_64)
Kernel: Linux 3.14-2-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE="en_US.UTF-8"
Shell: /bin/sh linked to /bin/dash
Compiler: Debian clang version 3.5.0-+rc1-2 (tags/RELEASE_35/rc1) (based on
LLVM 3.5.0)
diff -Naur apparmor.orig/apparmor-2.8.0/debian/changelog apparmor/apparmor-2.8.0/debian/changelog
--- apparmor.orig/apparmor-2.8.0/debian/changelog 2014-07-31 14:28:04.191226173 -0500
+++ apparmor/apparmor-2.8.0/debian/changelog 2014-08-01 15:01:01.007500846 -0500
@@ -1,3 +1,11 @@
+apparmor (2.8.0-5.2) unstable; urgency=low
+
+ * Fix FTBFS with clang
+- Fixed undefined reference error in
+ parser/parser_interface.c
+
+ -- Arthur Marble Fri, 01 Aug 2014 15:01:01 -0500
+
apparmor (2.8.0-5.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Naur apparmor.orig/apparmor-2.8.0/debian/patches/clang-ftbfs.diff apparmor/apparmor-2.8.0/debian/patches/clang-ftbfs.diff
--- apparmor.orig/apparmor-2.8.0/debian/patches/clang-ftbfs.diff 1969-12-31 18:00:00.0 -0600
+++ apparmor/apparmor-2.8.0/debian/patches/clang-ftbfs.diff 2014-08-01 14:58:42.863498440 -0500
@@ -0,0 +1,139 @@
+--- a/parser/parser_interface.c
b/parser/parser_interface.c
+@@ -255,13 +255,13 @@ static inline void sd_inc(sd_serialize *
+ }
+ }
+
+-inline long sd_serial_size(sd_serialize *p)
++static inline long sd_serial_size(sd_serialize *p)
+ {
+ return (p->pos - p->buffer);
+ }
+
+ /* routines for writing data to the serialization buffer */
+-inline int sd_prepare_write(sd_serialize *p, enum sd_code code, size_t size)
++static inline int sd_prepare_write(sd_serialize *p, enum sd_code code, size_t size)
+ {
+ int num = (size / BUFFERINC) + 1;
+ if (p->pos + SD_CODE_SIZE + size > p->extent) {
+@@ -284,7 +284,7 @@ inline int sd_prepare_write(sd_serialize
+ return 1;
+ }
+
+-inline int sd_write8(sd_serialize *p, u8 b)
++static inline int sd_write8(sd_serialize *p, u8 b)
+ {
+ u8 *c;
+ if (!sd_prepare_write(p, SD_U8, sizeof(b)))
+@@ -295,7 +295,7 @@ inline int sd_write8(sd_serialize *p, u8
+ return 1;
+ }
+
+-inline int sd_write16(sd_serialize *p, u16 b)
++static inline int sd_write16(sd_serialize *p, u16 b)
+ {
+ u16 tmp;
+ if (!sd_prepare_write(p, SD_U16, sizeof(b)))
+@@ -306,7 +306,7 @@ inline int sd_write16(sd_serialize *p, u
+ return 1;
+ }
+
+-inline int sd_write32(sd_serialize *p, u32 b)
++static inline int sd_write32(sd_serialize *p, u32 b)
+ {
+ u32 tmp;
+ if (!sd_prepare_write(p, SD_U32, sizeof(b)))
+@@ -317,7 +317,7 @@ inline int sd_write32(sd_serialize *p, u
+ return 1;
+ }
+
+-inline int sd_write64(sd_serialize *p, u64 b)
++static inline int sd_write64(sd_serialize *p, u64 b)
+ {
+ u64 tmp;
+ if (!sd_prepare_write(p, SD_U64, sizeof(b)))
+@@ -328,7 +328,7 @@ inline int sd_write64(sd_serialize *p, u
+ return 1;
+ }
+
+-inline int sd_write_name(sd_serialize *p, char *name)
++static inline int sd_write_name(sd_serialize *p, char *name)
+ {
+ long size = 0;
+ PDEBUG("Writing name '%s'\n", name);
+@@ -346,7 +346,7 @@ inline int sd_write_name(sd_serialize *p
+ return 1;
+ }
+
+-inline int sd_write_blob(sd_serialize *p, void *b, int buf_size, char *name)
++static inline int sd_write_blob(sd_serialize *p, void *b, int buf_size, char *name)
+ {
+ u32 tmp;
+ if (!sd_write_name(p, name))
+@@ -362,7 +362,7 @@ inline int sd_write_blob(sd_serialize *p
+ }
+
+ #define align64(X) (((size_t) (X) + (size_t) 7) & ~((size_t) 7))
+-inline int sd_write_aligned_blob(sd_serialize *p, void *b, int buf_size,
++static inline int sd_write_aligned_blob(sd_serialize *p, void *b, int buf_size,
+ char *name)
+ {
+ size_t pad;
+@@ -397,12 +397,12 @@ static int sd_write_strn(sd_serialize *p
+ return 1;
+ }
+
+-inline int sd_write_string(sd_serialize *p, char *b, char *name)
++static inline int sd_write_string(sd_serialize *p, char *b, char *name)
+ {
+ return sd_write_strn(p, b, strlen(b) + 1, name);
+ }
+
+-inline int sd_write_struct(sd_serialize *p, char *name)
++static inline int sd_write_struct(sd_serialize *p, char *name)
+ {
+ if (!sd_write_name(p, name))
+ return 0;
+@@ -411,14 +411,14 @@ inline int sd_write_struct(sd_serialize
+ return 1;
+ }
+
+-inline int sd_write_structend(sd_serialize *p)
++static inline int sd_write_structend(sd_serialize *p)
+ {
+ if (!sd_prepare_write(p, SD_STRUCTEND, 0))
+ return 0;
+ return 1;
+ }
+
+-inline int sd_write_array(sd_serialize *p, char *name, int size)
++static inline int sd_write_array(sd_serialize *p, char *name, int size)
+ {
+ u16 t
Bug#756477: devscripts: please lower debian-keyring to Suggests
2014-08-01 22:44 GMT+03:00 Jakub Wilk : > [IANA devscripts maintainer, and I'm not opposed to the downgrade you > proposed. Just wanted to bring forward some ideas.] > > * Martin-Éric Racine , 2014-07-30, 11:24: >> >> The Recommends on debian-keyring pulls a significantly huge tarball. This >> fills precious disk space without any immediate benefit since Debian's GPG >> does not include its content by default anyhow. > > > There *is* an immediate benefit: dscverify(1), who-uploads(1) and > who-permits-uploads(1) use the Debian keyrings by default. Noted. > Now, this is true that debian-keyring is huge. Moreover, the vast majority > of the space it takes are signatures, which aren't used by any on the > devscripts tools. > > One obvious optimization would be to have a debian-keyring-minimal package, > identical to debian-keyring, but with the non-essential signatures stripped > (--export-options export-minimal). I estimate that size of such a package > would be about 5MB (instead of 47MB). > > And who-uploads(1) and who-permits-uploads(1) don't even need a keyring. > They just need a mapping between key-ids and developers' names and emails. A > file with this information should take more than 200K compressed, even if it > included also data from removed-keys.gpg. Both of these options sound a lot more sensible than recommending this humongous 47MB package. :) Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/debian-bugs-dist
Bug#756806: linux-image-3.14-2-amd64: Strange connection resets
Package: src:linux Version: 3.14.13-2 Severity: normal Hi, since upgrading to a kernel from the 3.14-2 ABI series, I'm experiencing fairly reliable TCP connection resets on some connections, most notably ssh and outgoing SMTP on port 587. This appears to be somewhat dependent on the program opening the connection (openssh and icedove fail, netcat with exactly the same data works). The connection is always terminated with an incoming RST packet from the remote server, with correct sequence number and containing data(!), so my suspicion is that sometimes packets are somehow mangled, although I don't have the slightest idea what may be going on here. Booting into the last 3.14-1 kernel solves the problem. Network is via a Sierra Wireless LTE card. Simon -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: FUJITSU product_name: LIFEBOOK E782 product_version: 10601186020 chassis_vendor: FUJITSU chassis_version: LIFEBOOK E782 bios_vendor: FUJITSU // Phoenix Technologies Ltd. bios_version: Version 2.08 board_vendor: FUJITSU board_name: FJNB253 board_version: L3 ** Network interface configuration: auto lo iface lo inet loopback iface wwan0 inet dhcp pre-up qmicli -d /dev/cdc-wdm0 --dms-uim-verify-pin=PIN, pre-up qmi-network /dev/cdc-wdm0 start ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM Controller [8086:0154] (rev 09) Subsystem: Fujitsu Limited. Device [10cf:16bf] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Device [10cf:16c1] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- [disabled] Capabilities: Kernel driver in use: i915 00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04) (prog-if 30 [XHCI]) Subsystem: Fujitsu Limited. Device [10cf:16ee] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: xhci_hcd 00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 [8086:1e3a] (rev 04) Subsystem: Fujitsu Limited. Device [10cf:16ea] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: mei_me 00:16.3 Serial controller [0700]: Intel Corporation 7 Series/C210 Series Chipset Family KT Controller [8086:1e3d] (rev 04) (prog-if 02 [16550]) Subsystem: Fujitsu Limited. Device [10cf:16ed] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: serial 00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit Network Connection [8086:1502] (rev 04) Subsystem: Fujitsu Limited. Device [10cf:161b] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: e1000e 00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04) (prog-if 20 [EHCI]) Subsystem: Fujitsu Limited. Device [10cf:16e8] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: ehci-pci 00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller [8086:1e20] (rev 04) Subsystem: Fujitsu Limited. Device [10cf:1757] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snd_hda_intel 00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 [8086:1e10] (rev c4) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Bug#756805: alsa-tools: FTBFS with clang instead of gcc
Package: alsa-tools
Severity: minor
Tags: patch
User: pkg-llvm-t...@lists.alioth.debian.org
Usertags: clang-ftbfs
Hello,
Using the rebuild infrastructure, your package fails to build with clang
(instead of gcc).
Detected this kind of error:
http://clang.debian.net/status.php?version=3.4.2&key=UNDEF_REF
Full build log is available here:
http://clang.debian.net/logs/2014-06-16/alsa-tools_1.0.27-3_unstable_clang.log
Thanks,
Arthur
-- System Information:
Debian Release: jessie/sid (unstable)
Architecture: amd64 (x86_64)
Kernel: Linux 3.14-2-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE="en_US.UTF-8"
Shell: /bin/sh linked to /bin/dash
Compiler: Debian clang version 3.5.0-+rc1-2 (tags/RELEASE_35/rc1) (based on
LLVM 3.5.0)
diff -Naur alsa-tools.orig/alsa-tools-1.0.28/debian/changelog alsa-tools/alsa-tools-1.0.28/debian/changelog
--- alsa-tools.orig/alsa-tools-1.0.28/debian/changelog 2014-08-01 14:37:56.111476729 -0500
+++ alsa-tools/alsa-tools-1.0.28/debian/changelog 2014-08-01 14:41:21.059480298 -0500
@@ -1,3 +1,11 @@
+alsa-tools (1.0.28-2) unstable; urgency=low
+
+ * Fix FTBFS with clang
+- Fixed undefined undefined reference error in
+ as10k1/as10k1.c
+
+ -- Arthur Marble Fri, 01 Aug 2014 14:41:15 -0500
+
alsa-tools (1.0.28-1) unstable; urgency=medium
[ Luke Yelavich ]
diff -Naur alsa-tools.orig/alsa-tools-1.0.28/debian/patches/clang-ftbfs.diff alsa-tools/alsa-tools-1.0.28/debian/patches/clang-ftbfs.diff
--- alsa-tools.orig/alsa-tools-1.0.28/debian/patches/clang-ftbfs.diff 1969-12-31 18:00:00.0 -0600
+++ alsa-tools/alsa-tools-1.0.28/debian/patches/clang-ftbfs.diff 2014-08-01 14:39:03.443477901 -0500
@@ -0,0 +1,11 @@
+--- a/as10k1/as10k1.c
b/as10k1/as10k1.c
+@@ -366,7 +366,7 @@ void as_exit(const char *message)
+ exit(1);
+ }
+
+-inline void output_tram_line( struct list_head *line_head, int type){
++static inline void output_tram_line( struct list_head *line_head, int type){
+
+ struct tram *tram_sym;
+ struct list_head *entry;
diff -Naur alsa-tools.orig/alsa-tools-1.0.28/debian/patches/series alsa-tools/alsa-tools-1.0.28/debian/patches/series
--- alsa-tools.orig/alsa-tools-1.0.28/debian/patches/series 2014-08-01 14:37:56.111476729 -0500
+++ alsa-tools/alsa-tools-1.0.28/debian/patches/series 2014-08-01 14:38:41.307477516 -0500
@@ -1,3 +1,4 @@
usx2yloader_udev.patch
firmware_locations.patch
envy24control_config_dir.patch
+clang-ftbfs.diff
Bug#756477: devscripts: please lower debian-keyring to Suggests
[IANA devscripts maintainer, and I'm not opposed to the downgrade you proposed. Just wanted to bring forward some ideas.] * Martin-Éric Racine , 2014-07-30, 11:24: The Recommends on debian-keyring pulls a significantly huge tarball. This fills precious disk space without any immediate benefit since Debian's GPG does not include its content by default anyhow. There *is* an immediate benefit: dscverify(1), who-uploads(1) and who-permits-uploads(1) use the Debian keyrings by default. Now, this is true that debian-keyring is huge. Moreover, the vast majority of the space it takes are signatures, which aren't used by any on the devscripts tools. One obvious optimization would be to have a debian-keyring-minimal package, identical to debian-keyring, but with the non-essential signatures stripped (--export-options export-minimal). I estimate that size of such a package would be about 5MB (instead of 47MB). And who-uploads(1) and who-permits-uploads(1) don't even need a keyring. They just need a mapping between key-ids and developers' names and emails. A file with this information should take more than 200K compressed, even if it included also data from removed-keys.gpg. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756798: snappy: FTBFS almost everywhere
On Fri, Aug 01, 2014 at 08:21:28PM +0200, Sebastian Ramacher wrote: > snappy failed to build on almost every architecture with: > | configure.ac:42: error: possibly undefined macro: AC_DEFINE > | If this token and others are legitimate, please use m4_pattern_allow. > | See the Autoconf documentation. > | configure.ac:44: error: possibly undefined macro: AC_MSG_FAILURE > | autoreconf: /usr/bin/autoconf failed with exit status: 1 > | dh_autoreconf: autoreconf -f -i returned exit code 1 > | make: *** [build] Error 2 Thanks; I'll have a look. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756804: bash script fails with commands without path to command
Package: bash Version: 4.3-7 Severity: normal Dear Maintainer, Please disregard bug report. I found where I did a find and replace that changed path to PATH='', so it make sense. Tested with correction, and script works fine. Sorry, and thank you -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bash depends on: ii base-files 7.5 ii dash 0.5.7-4 ii debianutils 4.4 ii libc62.19-7 ii libtinfo55.9+20140712-2 Versions of packages bash recommends: ii bash-completion 1:2.1-4 Versions of packages bash suggests: pn bash-doc -- 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#756803: python3-spyderlib: typo in control file: Breakes/Breaks
Package: python3-spyderlib
Version: 2.3.0+dfsg-2
Severity: normal
Hi,
There is a typo in debian/control:
Breakes: ${python3:Breaks},
spyder3 (<< 2.3.0+dfsg-2)
It should be Breaks instead of Breakes.
Cheers,
Felix
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756801: [Pkg-haskell-maintainers] Bug#756801: haskell-bloomfilter: FTBFS almost everywhere
forwarded 756801 https://github.com/bos/bloomfilter/issues/7 quit Broken on 32-bit. On Fri, Aug 01, 2014 at 08:45:42PM +0200, Sebastian Ramacher wrote: > Source: haskell-bloomfilter > Version: 2.0.0.0-1 > Severity: serious > Justification: fails to build from source (but built successfully in the past) > > haskell-bloomfilter failed to build almost everywhere with: > | Running 1 test suites... > | Test suite tests: RUNNING... > | (): [Failed] > | *** Failed! Exception: 'Data.BloomFilter.Util.suggestSizing: capacity too > large to represent' (after 1 test): -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#748614: [pkg-kolab] Bug#748614: [libkolabxml1] looses information about birthdays
On Friday, August 01, 2014 08:49:17 Franz Schrober wrote: > Just tried it again with my system updated to 4.13.3 of kdepim and > kdepim-runtime. The problem still seems to be there. There's an upstream bug report https://issues.kolab.org/show_bug.cgi?id=2739 I told them about the debian bug. Diane -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756802: bash script fails with commands without path to command
Package: bash Version: 4.3-7 Severity: normal Dear Maintainer, I have a script in /usr/local/sbin using /bin/bash to create directories and files. In this script, I'm using the touch, chown, and chmod commands. They all fail with for example 'mkdir: No such file or directory'. All these commands work in a terminal, however. The only fix for this problem is to include the full path to the executable like /bin/touch, /bin/chmod, and /bin/chown. I've echo the value of $PATH at the beginning of my script, the value is '/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin'. Thank you -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bash depends on: ii base-files 7.5 ii dash 0.5.7-4 ii debianutils 4.4 ii libc62.19-7 ii libtinfo55.9+20140712-2 Versions of packages bash recommends: ii bash-completion 1:2.1-4 Versions of packages bash suggests: pn bash-doc -- 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#756801: haskell-bloomfilter: FTBFS almost everywhere
Source: haskell-bloomfilter
Version: 2.0.0.0-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
haskell-bloomfilter failed to build almost everywhere with:
| Running 1 test suites...
| Test suite tests: RUNNING...
| (): [Failed]
| *** Failed! Exception: 'Data.BloomFilter.Util.suggestSizing: capacity too
large to represent' (after 1 test):
| ()
| P {unP = 0.8033815424729676}
| (used seed 383316611)
| Bool: [Failed]
| *** Failed! Exception: 'Data.BloomFilter.Util.suggestSizing: capacity too
large to represent' (after 1 test and 1 shrink):
| False
| P {unP = 0.5711981786324355}
| (used seed 783244763)
| Ordering: [Failed]
| *** Failed! Exception: 'Data.BloomFilter.Util.suggestSizing: capacity too
large to represent' (after 1 test):
| EQ
| P {unP = 0.3816971869279409}
| (used seed 887643166)
| Char: [Failed]
| *** Failed! Exception: 'Data.BloomFilter.Util.suggestSizing: capacity too
large to represent' (after 1 test and 1 shrink):
| 'a'
| P {unP = 0.2906896187668971}
| (used seed -668750780)
| Int: [Failed]
| *** Failed! Exception: 'Data.BloomFilter.Util.suggestSizing: capacity too
large to represent' (after 1 test and 2 shrinks):
| 0
| P {unP = 0.353117130840947}
| (used seed 1631556714)
| Float: [Failed]
| *** Failed! Exception: 'Data.BloomFilter.Util.suggestSizing: capacity too
large to represent' (after 1 test):
| 0.0
| P {unP = 0.5315193196895125}
| (used seed 130888019)
| Double: [Failed]
| *** Failed! Exception: 'Data.BloomFilter.Util.suggestSizing: capacity too
large to represent' (after 1 test):
| 0.0
| P {unP = 0.17065813635035126}
| (used seed -1734145837)
| Int8: [Failed]
| *** Failed! Exception: 'Data.BloomFilter.Util.suggestSizing: capacity too
large to represent' (after 1 test and 2 shrinks):
| 0
| P {unP = 0.6128463004080046}
| (used seed 1402575473)
| Int16: [Failed]
| *** Failed! Exception: 'Data.BloomFilter.Util.suggestSizing: capacity too
large to represent' (after 1 test and 2 shrinks):
| 0
| P {unP = 0.7956180324066868}
| (used seed 1877254832)
| Int32: [Failed]
| *** Failed! Exception: 'Data.BloomFilter.Util.suggestSizing: capacity too
large to represent' (after 1 test):
| 0
| P {unP = 0.6046629350180126}
| (used seed 638412574)
| Int64: [Failed]
| *** Failed! Exception: 'Data.BloomFilter.Util.suggestSizing: capacity too
large to represent' (after 1 test and 1 shrink):
| 0
| P {unP = 0.5680359559591197}
| (used seed -1218189901)
| Word8: [Failed]
| *** Failed! Exception: 'Data.BloomFilter.Util.suggestSizing: capacity too
large to represent' (after 1 test and 1 shrink):
| 0
| P {unP = 0.5748927371270192}
| (used seed 133701633)
| Word16: [Failed]
| *** Failed! Exception: 'Data.BloomFilter.Util.suggestSizing: capacity too
large to represent' (after 1 test and 1 shrink):
| 0
| P {unP = 0.7590538015852916}
| (used seed -2085671915)
| Word32: [Failed]
| *** Failed! Exception: 'Data.BloomFilter.Util.suggestSizing: capacity too
large to represent' (after 1 test and 1 shrink):
| 0
| P {unP = 0.26456169709548605}
| (used seed -1534806952)
| Word64: [Failed]
| *** Failed! Exception: 'Data.BloomFilter.Util.suggestSizing: capacity too
large to represent' (after 1 test):
| 0
| P {unP = 0.8284759565226993}
| (used seed 611969002)
| String: [Failed]
| *** Failed! Exception: 'Data.BloomFilter.Util.suggestSizing: capacity too
large to represent' (after 1 test):
| ""
| P {unP = 0.6181214392832471}
| (used seed 707041186)
| LB.ByteString: [Failed]
| *** Failed! Exception: 'Data.BloomFilter.Util.suggestSizing: capacity too
large to represent' (after 1 test):
| ""
| P {unP = 0.9950431109280928}
| (used seed 915218596)
| prop_rechunked_eq: [OK, passed 100 tests]
|
| Properties Total
| Passed 11
| Failed 17 17
| Total 18 18
| Test suite tests: FAIL
| Test suite logged to: dist-ghc/test/bloomfilter-2.0.0.0-tests.log
| 0 of 1 test suites (0 of 1 test cases) passed.
| make: *** [check-ghc-stamp] Error 1
Full build logs are available from
https://buildd.debian.org/status/package.php?p=haskell-bloomfilter.
Please take a look.
Cheers
--
Sebastian Ramacher
signature.asc
Description: Digital signature
Bug#756658: owncloud: After migration from 6.0.4, database upgrade fail to find a table
Hi Mathias, Thanks for your interest in this package. On Thu, Jul 31, 2014 at 10:45:47PM +0200, Mathias BOCQUET wrote: > upgrade from owncloud 6.0.4+dfsg-1. Upgrade process (from browser) failed > while > searching for oc_oc_ldap_user_mapping* table.i Can you please provide the relevant log part (from /var/log/owncloud.log)? Do you rely on the LDAP user app, any other app? Regards David signature.asc Description: Digital signature
Bug#756800: libdshconfig: use dh-autoreconf to fix FTBFS on ppc64el
Package: libdshconfig
Version: 0.20.13
Severity: normal
Tags: patch
User: debian-powe...@lists.debian.org
Usertags: ppc64el
User: debian-de...@lists.debian.org
Usertags: autoreconf
Dear Maintainer,
The package libdshconfig fails to build on ppc64le, because of
changes required in config.{guess,sub}. This patch includes
dh-autoreconf to the build so that it builds correctly.
Thanks for considering the patch!
Thanks and regards,
Brahadambal
diff -ruN libdshconfig-0.20.13.orig/debian/control
libdshconfig-0.20.13/debian/control
--- libdshconfig-0.20.13.orig/debian/control2014-08-01 18:32:41.0
+
+++ libdshconfig-0.20.13/debian/control 2014-08-01 18:33:23.0 +
@@ -2,7 +2,7 @@
Section: libs
Priority: optional
Maintainer: Junichi Uekawa
-Build-Depends: debhelper (>> 4.0.0), libtool, d-shlibs (>= 0.4), doxygen
+Build-Depends: debhelper (>> 4.0.0), dh-autoreconf, libtool, d-shlibs (>=
0.4), doxygen
Standards-Version: 3.7.2
Package: libdshconfig1
diff -ruN libdshconfig-0.20.13.orig/debian/rules
libdshconfig-0.20.13/debian/rules
--- libdshconfig-0.20.13.orig/debian/rules 2014-08-01 18:32:52.0
+
+++ libdshconfig-0.20.13/debian/rules 2014-08-01 18:33:31.0 +
@@ -13,6 +13,7 @@
configure: configure-stamp
configure-stamp:
dh_testdir
+ dh_autoreconf
# Add here commands to configure the package.
./configure -prefix=/usr --with-versioned-symbol
touch configure-stamp
@@ -31,6 +32,7 @@
rm -f build-stamp configure-stamp
rm -rf $(DSH)
-$(MAKE) distclean
+ dh_autoreconf_clean
dh_clean
install: build
Bug#756619: apt-get update: SIGBUS when run out of disk space
* Julian Andres Klode , 2014-08-01, 19:57: # apt-get update Hit http://ftp.debian.org unstable InRelease Hit http://ftp.debian.org unstable/main amd64 Packages/DiffIndex Bus error (core dumped). 60% I just wonder how this happens. APT is writing to an mmap. That mmap has been allocated on the disk already, so it should not fail, unless the FS lied and has no space anymore, despite having promised it to APT, or am I wrong? How does apt allocate the space? In the DynamicMMap constructor I see: Fd->Seek(WorkSpace - 1); char C = 0; Fd->Write(&C,sizeof(C)); which would create just a sparse file. Maybe posix_fallocate(3) is needed instead? (But I'm not familiar with apt codebase, so maybe I'm looking at the completely wrong place.) -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756791: Acknowledgement (xfig: Segfaults when editing points of an arc)
Attached SAVE.fig that appears to reproduce the problem. Incidentally, I've been plowing through with XFig for the project, and there are *a lot* of seg faults :( You probably already knew that, and I'm sure you are working on it. Thanks for your efforts for Debian and Xfig. -- Keith Hellman #include khell...@mcprogramming.comfrom disclaimer import standard khell...@mines.edu -*- public key @ pgp.mit.edu 9FCF40FD Y!M: mcprogramming AIM/ICQ: 485403897 jabber: mrtu...@jabber.org irc: freenode.net as mrtuple -*- It's a small world. So you gotta use your elbows a lot. bug-report-SAVE.fig Description: application/xfig signature.asc Description: Digital signature
Bug#756396: Backport uploaded
On Fri, Aug 01, 2014 at 11:15:07AM -0400, micah wrote: > > Hello, > > I ran into this issue as well, I've backported ruby-mail and just > uploaded it to wheezy-backports. Thanks! > It has to get accepted before it will be available, but perhaps the > redmine backport could be re-uploaded with the Depends changed so that > this version will be properly pulled in. I am waiting for ruby-mime-types (and now ruby-mail) to be accepted before I upload redmine with the proper versioned dependencies, otherwise redmine will be uninstallable. -- Antonio Terceiro signature.asc Description: Digital signature
Bug#756799: gnome: Switch user causes system crash after updates
Package: gnome Version: 1:3.4+7+deb7u1 Severity: important Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? After allowing Software Updates to run on two different Debian 7.6 desktops they both crash when I try to switch users or logout a user. A black screen appears with no mouse pointer. Keyboard input has no effect, eg. Ctrl-Alt-Del. * What exactly did you do (or not do) that was effective (or ineffective)? The only way to recover is to force shutdown by holding the power button. Able to switch user only by restarting Debian or shutdown/startup. * What was the outcome of this action? Shutdown/restart brings Debian and Gnome Desktop back up, but does not fix the logout/switch user problem. * What outcome did you expect instead? Before most recent System Tools -> Software Updates (about 48 hours ago) I was able to switch users or log out as expected. Thank you. -- System Information: Debian Release: 7.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (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 Versions of packages gnome depends on: ii aisleriot1:3.4.1-1 ii alacarte 3.5.3-1 ii avahi-daemon 0.6.31-2 ii cheese 3.4.2-2 ii cups-pk-helper 0.2.3-3 ii desktop-base 7.0.3 ii evolution3.4.4-3 ii evolution-plugins3.4.4-3 ii file-roller 3.4.2-1 ii gedit3.4.2-1 ii gedit-plugins3.4.0-1 ii gimp 2.8.2-2+deb7u1 ii gnome-applets3.4.1-3 ii gnome-color-manager 3.4.2-1 ii gnome-core 1:3.4+7+deb7u1 ii gnome-documents 0.4.2-2 ii gnome-games 1:3.4.2-3 ii gnome-media 3.4.0-1 ii gnome-nettool3.2.0-1 ii gnome-orca 3.4.2-2 ii gnome-shell-extensions 3.4.0-2 ii gnome-tweak-tool 3.4.0.1-2 ii gstreamer0.10-ffmpeg 0.10.13-5 ii gstreamer0.10-plugins-ugly 0.10.19-2+b2 ii hamster-applet 2.91.3+git20120514.b9fec3e1-1 ii inkscape 0.48.3.1-1.3 ii libgtk2-perl 2:1.244-1 ii libreoffice-calc 1:3.5.4+dfsg2-0+deb7u2 ii libreoffice-gnome1:3.5.4+dfsg2-0+deb7u2 ii libreoffice-impress 1:3.5.4+dfsg2-0+deb7u2 ii libreoffice-writer 1:3.5.4+dfsg2-0+deb7u2 ii nautilus-sendto 3.0.3-2+b1 ii network-manager-gnome0.9.4.1-5 ii rhythmbox2.97-2.1 ii rhythmbox-plugin-cdrecorder 2.97-2.1 ii rhythmbox-plugins2.97-2.1 ii rygel-playbin0.14.3-2+deb7u1 ii rygel-preferences0.14.3-2+deb7u1 ii rygel-tracker0.14.3-2+deb7u1 ii seahorse 3.4.1-2 ii shotwell 0.12.3-2+deb7u1 ii simple-scan 3.4.2-1 ii sound-juicer 3.4.0-3 ii telepathy-gabble 0.16.7-0+deb7u1 ii telepathy-rakia 0.7.4-1 ii telepathy-salut 0.8.1-1 ii tomboy 1.10.0-2 ii totem3.0.1-8 ii totem-plugins3.0.1-8 ii tracker-gui 0.14.1-3 ii transmission-gtk 2.52-3+nmu2 ii vinagre 3.4.2-2 ii xdg-user-dirs-gtk0.9-1 Versions of packages gnome recommends: ii browser-plugin-gnash 0.8.11~git20120629-1+deb7u1 ii gdebi0.8.7 ii gnome-games-extra-data 3.2.0-4 ii nautilus-sendto-empathy 3.4.2.3-2+deb7u1 ii telepathy-idle 0.1.11-2+deb7u1 Versions of packages gnome suggests: pn dia-gnome pn gnome-boxes pn gnucash pn iceweasel-l10n-all ii libreoffice-evolution 1:3.5.4+dfsg2-0+deb7u2 pn planner pn xul-ext-adblock-plus pn xul-ext-gnome-keyring Versions of packages gnome-core depends on: ii at-spi2-core2.5.3-2 ii baobab 3.4.1-1 ii brasero 3.4.1-4 ii caribou 0.4.4-1 ii caribou-antler 0.4.4-1 ii dconf-gsettings-backend 0.12.1-3 ii dconf-tools 0.12.1-3 ii empathy 3.4.2.3-2+deb7u1 ii eog 3.4.2-1+build1 ii evince 3.4.0-3.1 ii evolution-data-server 3.4.4-3 ii fonts-cantarell 0.0.9-1 ii gcalctool 6.4.2.1-3 ii gconf2 3.2.5-1+build1 ii gdm33.4.1-8 ii gkbd-capplet3.4.0.2-1 ii glib-networking 2.32.3-1 ii gnome-backgrounds 3.4.2-1 ii gnome-b
Bug#756724: cups-browsed: Can't see remote printers in print dialogs
Control: severity -1 important Control: tags -1 +upstream Hi Peter, and thanks for your bugreport, Le vendredi, 1 août 2014 12.58:48, vous avez écrit : > Since updating to 1.0.55-1 I no longer see remote printers in print > dialogs. > > cups-browsed --debug reports > > cups-browsed: browsed queue name is vrl-lvl1-p1 > cups-browsed: Found CUPS queue: vrl-lvl1-p1 on host PRINT_SERVER_IP > cups-browsed: Remote CUPS queue vrl-lvl1-p1 on host PRITN_SERVER_IP is > raw, ignored. > > If I downgrade to Jessie's cups-browsed (1.0.54-3.b1) everything works > as expected. > > The print server is running cups version 1.4.4 This behaviour change was intentionally introduced in 1.0.55 on the upstream side: - cups-browsed: Do not create a local queue pointing to a remote raw queue (Ubuntu bug #1335211). Till: this change introduces a regression for valid use cases. How should we fix this and/or how should Peter access his remote raw queue then? Cheers, OdyX signature.asc Description: This is a digitally signed message part.
Bug#756798: snappy: FTBFS almost everywhere
Source: snappy Version: 1.1.2-2 Severity: serious Justification: fails to build from source (but built successfully in the past) snappy failed to build on almost every architecture with: | dh_autoreconf | libtoolize: putting auxiliary files in `.'. | libtoolize: copying file `./ltmain.sh' | libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'. | libtoolize: copying file `m4/libtool.m4' | libtoolize: copying file `m4/ltoptions.m4' | libtoolize: copying file `m4/ltsugar.m4' | libtoolize: copying file `m4/ltversion.m4' | libtoolize: copying file `m4/lt~obsolete.m4' | configure.ac:42: error: possibly undefined macro: AC_DEFINE | If this token and others are legitimate, please use m4_pattern_allow. | See the Autoconf documentation. | configure.ac:44: error: possibly undefined macro: AC_MSG_FAILURE | autoreconf: /usr/bin/autoconf failed with exit status: 1 | dh_autoreconf: autoreconf -f -i returned exit code 1 | make: *** [build] Error 2 Full build logs are available from https://buildd.debian.org/status/package.php?p=snappy. Please take a look. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#570423: Movement on bug report
Is there anything needed from the community to get movement on this feature request? Is a new patch needed?
Bug#756797: emdebian-crush: [INTL:pt] Updated Portuguese translation of manpage
Package: emdebian-crush Version: 2.2.20 Tags: l10n, patch Severity: wishlist Updated Portuguese translation for emdebian-crush's manpage. Translator: Américo Monteiro Feel free to use it. For translation updates please contact 'Last Translator' or the Portuguese Translation Team . -- Melhores cumprimentos/Best regards, Américo Monteiro emdebian-crush_2.2.20_pt.po.gz Description: GNU Zip compressed data
Bug#756796: espresso: FTBFS on s390x
Source: espresso Version: 5.1+dfsg-1 Severity: serious Justification: fails to build from source (but built successfully in the past) espresso failed to build on s390x with: | mpif90 -g -pthread -o pw.x \ |pwscf.o libpw.a ../../Modules/libqemod.a ../../flib/ptools.a ../../flib/flib.a ../../clib/clib.a ../../iotk/src/libiotk.a -lscalapack-mpich2 -lblacs-mpich2 -lblacsF77init-mpich2 -llapack -lblas -lfftw3 -lblas | /usr/bin/ld: cannot find -lscalapack-mpich2 | /usr/bin/ld: cannot find -lblacs-mpich2 | /usr/bin/ld: cannot find -lblacsF77init-mpich2 | collect2: error: ld returned 1 exit status | make[4]: *** [pw.x] Error 1 Full build logs are available from https://buildd.debian.org/status/fetch.php?pkg=espresso&arch=s390x&ver=5.1+dfsg-1&stamp=1406242584. Please take a look. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#756795: espresso: FTBFS on armel
Source: espresso Version: 5.1+dfsg-1 Severity: serious Justification: fails to build from source (but built successfully in the past) espresso failed to build on armel with: | Checking dft1...passed | Checking dft10...passed | Checking dft11...passed | Checking dft2...passed | Checking dft3...passed | Checking dft4...passed | Checking dft5...passed | Checking dft6...passed | Checking dft7...passed | Checking dft8...discrepancy in total energy detected | Reference: -15.653555, You got: -15.653554 | Checking dft9...passed | Checking dipole...passed | E: Caught signal ‘Terminated’: terminating immediately | make: *** wait: No child processes. Stop. Full build log is available from https://buildd.debian.org/status/fetch.php?pkg=espresso&arch=armel&ver=5.1+dfsg-1&stamp=1406271521. Please take a look Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#756794: vsftpd: FTBFS on kfreebsd-*
Source: vsftpd Version: 3.0.2-15 Severity: serious Justification: fails to build from source (but built successfully in the past) vsftpd failed to build on kfreebsd-* with: | gcc -c sysdeputil.c -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -idirafter dummyinc | sysdeputil.c: In function 'do_checkcap': | sysdeputil.c:622:3: error: unknown type name 'cap_t' |cap_t current_caps = cap_get_proc(); |^ | sysdeputil.c:624:20: warning: comparison between pointer and integer |if (current_caps != NULL) | ^ | sysdeputil.c: In function 'vsf_sysdep_adopt_capabilities': | sysdeputil.c:635:3: error: unknown type name 'cap_value_t' |cap_value_t cap_value; |^ | sysdeputil.c:636:3: error: unknown type name 'cap_t' |cap_t adopt_caps = cap_init(); |^ | sysdeputil.c:639:17: error: 'CAP_CHOWN' undeclared (first use in this function) | cap_value = CAP_CHOWN; | ^ | sysdeputil.c:639:17: note: each undeclared identifier is reported only once for each function it appears in | sysdeputil.c:640:30: error: 'CAP_EFFECTIVE' undeclared (first use in this function) | cap_set_flag(adopt_caps, CAP_EFFECTIVE, 1, &cap_value, CAP_SET); | ^ | sysdeputil.c:640:60: error: 'CAP_SET' undeclared (first use in this function) | cap_set_flag(adopt_caps, CAP_EFFECTIVE, 1, &cap_value, CAP_SET); | ^ | sysdeputil.c:641:30: error: 'CAP_PERMITTED' undeclared (first use in this function) | cap_set_flag(adopt_caps, CAP_PERMITTED, 1, &cap_value, CAP_SET); | ^ | sysdeputil.c:645:17: error: 'CAP_NET_BIND_SERVICE' undeclared (first use in this function) | cap_value = CAP_NET_BIND_SERVICE; | ^ | make[2]: *** [sysdeputil.o] Error 1 Build logs are available from https://buildd.debian.org/status/package.php?p=vsftpd. Please take a look. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#756793: axiom: FTBFS on mips
Source: axiom Version: 20120501-18 Severity: serious Justification: fails to build from source (but built successfully in the past) axiom failed to build on mips with: | 2 building gcl-2.6.8pre7 | echo '(compiler::link (list (compile-file "/«PKGBUILDDIR»/books/tangle.lisp")) "/«PKGBUILDDIR»/obj/linux/bin/lisp" (format nil "(progn (let ((*load-path* (cons ~S *load-path*))(si::*load-types* ~S)) (compiler::emit-fn t))(when (fboundp (quote si::sgc-on)) (si::sgc-on t))#-native-reloc(setq compiler::*default-system-p* t))" si::*system-directory* (quote (list #+native-reloc".o" ".lsp"))) "/«PKGBUILDDIR»/obj/linux/lib/cfuns-c.o /«PKGBUILDDIR»/obj/linux/lib/sockio-c.o /«PKGBUILDDIR»/obj/linux/lib/libspad.a")' | gcl | | Error: Caught fatal error [memory may be damaged] | Fast links are on: do (si::use-fast-links nil) for debugging | Error signalled by an anonymous function. | | Error: 3 is an illegal ihs index. | Fast links are on: do (si::use-fast-links nil) for debugging | Error signalled by an anonymous function. | Broken at NIL. | Bus error | make[3]: *** [gcldir] Error 138 The full build log is available at https://buildd.debian.org/status/fetch.php?pkg=axiom&arch=mips&ver=20120501-18&stamp=1406871957. Please take a look. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#756792: "help" command should provide help for "done", "then", "else", "elif", "fi", "esac"
Package: bash Version: 4.3-7 Severity: wishlist The keywords "done", "then", "else", "elif", "fi", and "esac" all produce "no help topics match" errors rather than pointing to useful help. help could instead open the help for "if" or "case" as appropriate; for "done" it could show the help for "for", "while", and "until". - Josh Triplett -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bash depends on: ii base-files 7.5 ii dash 0.5.7-4 ii debianutils 4.4 ii libc62.19-7 ii libtinfo55.9+20140712-2 Versions of packages bash recommends: ii bash-completion 1:2.1-4 Versions of packages bash suggests: pn bash-doc -- 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#754793: RFS: mosquitto/1.2.1-2 RC
Thanks Cameron! Upstart isn't familiar to me yet. Regards, Eriberto 2014-08-01 14:39 GMT-03:00 Cameron Norman : > El vie, 1 de ago 2014 a las 10:32 , Eriberto Mota > escribió: > > 6. There is a .conf in /etc/init. What is this? > > > That would be an Upstart job. > > Best, > -- > Cameron Norman -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756619: apt-get update: SIGBUS when run out of disk space
On Thu, Jul 31, 2014 at 1:52 PM, Jakub Wilk wrote: > Package: apt > Version: 1.0.6 > > "apt-get update" dies with SIGBUS when there's very little free space on > disk: > > # rm -f /var/cache/apt/*.* > > # df -h /var > Filesystem Size Used Avail > Use% Mounted on > /dev/disk/by-uuid/0fbbe877-619a-4769-9583-1f6ca4084685 2.0G 1.9G 25M > 99% / > > # apt-get update > Hit http://ftp.debian.org unstable InRelease > Hit http://ftp.debian.org unstable/main amd64 Packages/DiffIndex > Bus error (core dumped). 60% > I just wonder how this happens. APT is writing to an mmap. That mmap has been allocated on the disk already, so it should not fail, unless the FS lied and has no space anymore, despite having promised it to APT, or am I wrong? -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756791: xfig: Segfaults when editing points of an arc
Package: xfig Version: 1:3.2.5.c-3 Severity: important Dear Maintainer, * What led up to the situation? I was beginning a floor plan diagram and drawing in the typical door-and-swing graphic. * What exactly did you do (or not do) that was effective (or ineffective)? I was attempting to edit-point of an arc to even it up with the horizontal location of a straight line segment in the same (opened) group. * What was the outcome of this action? SEGFAULT. The group was saved to SAVE.fig. Trying to perform the same editing on SAVE.fig (re?)produces a SEGFAULT as well. * What outcome did you expect instead? :) Not to segfault. -- System Information: Debian Release: testing/unstable APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-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 Versions of packages xfig depends on: ii libc6 2.18-7 ii libjpeg88d-2 ii libpng12-0 1.2.50-1 ii libx11-62:1.6.2-2 ii libxpm4 1:3.5.10-1 ii libxt6 1:1.1.4-1 ii xaw3dg 1.5+E-18.2 Versions of packages xfig recommends: ii transfig 1:3.2.5.e-3 ii xfig-libs 1:3.2.5.c-3 Versions of packages xfig suggests: ii cups-bsd [lpr] 1.7.2-3 ii cups-client 1.7.2-3 ii ghostscript 9.05~dfsg-8.1 ii gimp2.8.10-1 ii gsfonts-x11 0.22 ii netpbm 2:10.0-15+b2 pn spell pn xfig-doc -- 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#756790: tcpdump: FTBFS on kfreebsd-*
Source: tcpdump Version: 4.6.1-1 Severity: serious Justification: fails to build from source (but built successfully in the past) tcpdump failed to build on kfreebsd-* with: | gcc -ffloat-store -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FILE_OFFSET_BITS=64 -DHAVE_CONFIG_H -D_FORTIFY_SOURCE=2 -D_U_="__attribute__((unused))" -I. -I/usr/include -DINET6 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FILE_OFFSET_BITS=64 -o strlcat.o -c ./missing/strlcat.c | ./print-pflog.c:34:26: fatal error: net/if_pflog.h: No such file or directory | #include | ^ | compilation terminated. Full build logs are available from https://buildd.debian.org/status/package.php?p=tcpdump. Please take a look. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#756163: Reducing the severity
severity 756163 minor thanks Anton -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#750590: Closing the bug
Closing the bug Anton -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#751441: Closing the bug
Bug is closed. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756734: ITP: python-xstatic-jquery -- jquery XStatic support
Great! Sorry, I hadn't spotted any of the other xstatic packages you'd repackaged and uploaded yet so I didn't realize they were going to omit the Javascript libraries themselves and just provide the xstatic installation wrapper. In that case I don't suppose there's any risk of having them rejected, but it still may be worth a quick discussion with the Horizon devs to confirm this is at all necessary, so you don't waste your already limited available time (assuming this hasn't already been discussed with them). I'll do some asking around as well... on its face, at least, it seems dubious that you should actually need a Debian wrapper around a Python wrapper around a Javascript library which is itself already packaged in Debian. -- Jeremy Stanley -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756789: ITP: spork -- DRb (Distributed Ruby) server for testing frameworks
Package: wnpp Severity: wishlist Owner: Miguel Landaeta * Package name: spork Version : 0.9.2 Upstream Author : Tim Harper * URL : https://github.com/sporkrb/spork * License : MIT/X Programming Lang: Ruby Description : DRb (Distributed Ruby) server for testing frameworks Spork is a test server (similar to the script/spec_server that used to be provided by rspec-rails), except rather than using the Rails constant unloading to reload your files, it forks a copy of the server each time you run your tests. . It supports the following testing frameworks: * Rspec * Cucumber * Test::Unit -- 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#754793: RFS: mosquitto/1.2.1-2 RC
El vie, 1 de ago 2014 a las 10:32 , Eriberto Mota escribió: 6. There is a .conf in /etc/init. What is this? That would be an Upstart job. Best, -- Cameron Norman
Bug#754793: RFS: mosquitto/1.2.1-2 RC
tags 754793 moreinfo thanks Hi Roger, how are you? I will try help you. Please: 1. Update the Standards-Version from 3.9.4 to 3.9.5. 2. d/copyright: please, update the years (include 2014, because I found it in your upstream code). 3. d/docs: The final user doesn't compiles codes. So, send compiling instructions to user is unusual. Please, remove the compiling.txt. 4. All readmes should be put in /usr/share/doc/mosquitto. Do you have a reason to put them in /etc? 5. The example must be put in /usr/share/doc/mosquitto/examples ($ man dh_installexamples). 6. There is a .conf in /etc/init. What is this? I need to stop now. But, if you reply me, I will resume my efforts. Thanks for your work. Regards, Eriberto -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756787: stress-ng: FTBFS on kfreebsd-*
Source: stress-ng
Version: 0.01.28-1
Severity: serious
Justification: fails to build from source
stress-ng failed to build on kfreebsd-* with:
| cc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat
-Werror=format-security -Wall -Wextra -DVERSION='"0.01.28"' -O2
-D_FORTIFY_SOURCE=2 -c -o stress-ng.o stress-ng.c
| stress-ng.c: In function 'stress_sigq':
| stress-ng.c:2023:12: error: 'siginfo_t' has no member named 'si_int'
| if (info.si_int)
| ^
| stress-ng.c: At top level:
| stress-ng.c:2226:18: error: 'OPT_SIGQUEUE' undeclared here (not in a function)
| { "sigq", 1, 0, OPT_SIGQUEUE },
| ^
| stress-ng.c:2226:2: warning: missing initializer for field 'val' of 'const
struct option' [-Wmissing-field-initializers]
| { "sigq", 1, 0, OPT_SIGQUEUE },
| ^
| In file included from stress-ng.c:38:0:
| /usr/include/getopt.h:111:7: note: 'val' declared here
|int val;
|^
| stress-ng.c:2227:22: error: 'OPT_SIGQUEUE_OPS' undeclared here (not in a
function)
| { "sigq-ops", 1, 0, OPT_SIGQUEUE_OPS },
| ^
| stress-ng.c:2227:2: warning: missing initializer for field 'val' of 'const
struct option' [-Wmissing-field-initializers]
| { "sigq-ops", 1, 0, OPT_SIGQUEUE_OPS },
| ^
| In file included from stress-ng.c:38:0:
| /usr/include/getopt.h:111:7: note: 'val' declared here
|int val;
|^
| make[1]: *** [stress-ng.o] Error
Full build logs are available from
https://buildd.debian.org/status/package.php?p=stress-ng. Please take a
look.
Cheers
--
Sebastian Ramacher
signature.asc
Description: Digital signature
Bug#756734: ITP: python-xstatic-jquery -- jquery XStatic support
On 08/01/2014 08:16 PM, Jeremy Stanley wrote: > On 2014-08-01 15:37:02 +0800 (+0800), Thomas Goirand wrote: > [...] >> This package provides jQuery support. > > More than that, it provides jQuery itself... I suspect you're > repackaging this for Debian as one of the many xstatic dependencies > recently added to OpenStack Horizon, but those are really more of a > Python Cheeseshop implementation detail to allow people who are > installing via pip to get the necessary Javascript libraries. For > Debian this is probably just going to be seen (correctly in my > opinion) as yet another embedded copy of jQuery, and I have doubts > this will make it through new/ftpmaster unless its goal is to become > *the* jQuery package for Debian. > > To reiterate, my understanding is that Horizon added xstatic package > dependencies specifically for the benefit of people who *weren't* > getting those Javascript libraries from their respective > distributions, so at least in most cases distro packagers shouldn't > need to worry about them unless the equivalent JS libs aren't > already in their distros. Hi Jeremy, Thanks for this message. You are mistaking in what I've been doing. The python-xstatic-jquery package will *not* embed/provide a copy of jquery. I have *removed* jquery itself from the python-xstatic-jquery source. Instead, I have edited xstatic/pkg/jquery/__init__.py, fixed the version number so that it matches what's available in Debian (eg: 1.7.2), and fixed the BASE_DIR= directive to point at /usr/share/javascript/jquery. The resulting package then Depends: libjs-jquery (>= 1.7.2), libjs-jquery (<< 1.7.3), to make sure that xstatic isn't lying. In fact, all this is what xstatic has been created for, and what the author of xstatic recommends doing. If you think that I should have another approach, and just have Horizon depend on libjs-jquery directly, please let me know, but my understanding is that the wrapper in xstatic/pkg/jquery/__init__.py is really needed for Horizon. Also, using the code review system, I made sure that new stuff in the OpenStack global-requirements.txt matches the version of javascript libraries we have in Debian, including that one for jQuery (eg: libjs-jquery). Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#740701: multipath-tools: mkfs fails "Add. Sense: Incompatible medium installed"
--On Thursday, July 31, 2014 10:13:15 PM +0200 Hans van Kranenburg wrote: If Bill (OP) agrees, I'll close it as soon as I found a solution for the problem, documenting it, whatever that is. That is fine by me. Thanks for your work on this. Bill -- Bill MacAllister System Programmer, Stanford University -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756788: libwebp: FTBFS on mips*
Source: libwebp Version: 0.4.1-1 Severity: serious Justification: fails to build from source (but built successfully in the past) libwebp failed to build on mips* with: | libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../src/webp -D_FORTIFY_SOURCE=2 -Wall -Wdeclaration-after-statement -Wextra -Wmissing-declarations -Wmissing-prototypes -Wold-style-definition -Wshadow -Wunused-but-set-variable -Wunused -Wvla -g -O2 -Wformat -Werror=format-security -pthread -c upsampling.c -fPIC -DPIC -o .libs/libwebpdsp_la-upsampling.o | /tmp/cc3MeNhe.s: Assembler messages: | /tmp/cc3MeNhe.s:52: Error: opcode not supported on this processor: mips2 (mips2) `madd $6,$5' | /tmp/cc3MeNhe.s:53: Error: opcode not supported on this processor: mips2 (mips2) `madd $6,$4' | /tmp/cc3MeNhe.s:140: Error: opcode not supported on this processor: mips2 (mips2) `madd $9,$3' | /tmp/cc3MeNhe.s:141: Error: opcode not supported on this processor: mips2 (mips2) `madd $9,$7' | /tmp/cc3MeNhe.s:1262: Error: opcode not supported on this processor: mips2 (mips2) `clz $6,$4' | /tmp/cc3MeNhe.s:1479: Error: opcode not supported on this processor: mips2 (mips2) `clz $6,$4' | make[3]: *** [libwebpdsp_la-lossless_mips32.lo] Error 1 | make[3]: *** Waiting for unfinished jobs | Makefile:613: recipe for target 'libwebpdsp_la-lossless_mips32.lo' failed | /tmp/cc4m73Vp.s: Assembler messages: | /tmp/cc4m73Vp.s:218: Error: opcode not supported on this processor: mips2 (mips2) `movz $7,$12,$22' | /tmp/cc4m73Vp.s:227: Error: opcode not supported on this processor: mips2 (mips2) `movz $22,$12,$7' | /tmp/cc4m73Vp.s:236: Error: opcode not supported on this processor: mips2 (mips2) `movz $7,$12,$22' | /tmp/cc4m73Vp.s:245: Error: opcode not supported on this processor: mips2 (mips2) `movz $22,$12,$7' | /tmp/cc4m73Vp.s:260: Error: opcode not supported on this processor: mips2 (mips2) `movz $11,$12,$7' | /tmp/cc4m73Vp.s:266: Error: opcode not supported on this processor: mips2 (mips2) `movz $14,$12,$7' | /tmp/cc4m73Vp.s:274: Error: opcode not supported on this processor: mips2 (mips2) `movz $25,$12,$7' | /tmp/cc4m73Vp.s:278: Error: opcode not supported on this processor: mips2 (mips2) `movz $20,$12,$19' | /tmp/cc4m73Vp.s:302: Error: opcode not supported on this processor: mips2 (mips2) `movz $11,$12,$7' | /tmp/cc4m73Vp.s:306: Error: opcode not supported on this processor: mips2 (mips2) `movz $14,$12,$19' | /tmp/cc4m73Vp.s:310: Error: opcode not supported on this processor: mips2 (mips2) `movz $25,$12,$24' | /tmp/cc4m73Vp.s:314: Error: opcode not supported on this processor: mips2 (mips2) `movz $20,$12,$9' | /tmp/cc4m73Vp.s:338: Error: opcode not supported on this processor: mips2 (mips2) `movz $11,$12,$7' | /tmp/cc4m73Vp.s:342: Error: opcode not supported on this processor: mips2 (mips2) `movz $14,$12,$19' | /tmp/cc4m73Vp.s:346: Error: opcode not supported on this processor: mips2 (mips2) `movz $25,$12,$24' | /tmp/cc4m73Vp.s:350: Error: opcode not supported on this processor: mips2 (mips2) `movz $20,$12,$9' | make[3]: *** [libwebpdsp_la-dec_mips32.lo] Error 1 | Makefile:592: recipe for target 'libwebpdsp_la-dec_mips32.lo' failed Full build logs are available from https://buildd.debian.org/status/package.php?p=libwebp. Please take a look. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#756786: ntp: FTBFS on kfreebsd-*
Source: ntp Version: 1:4.2.6.p5+dfsg-3.1 Severity: serious Justification: fails to build from source (but built successfully in the past) ntp failed to build on kfreebsd-* with: | # move the administrator programs from /usr/bin to /usr/sbin | for file in ntpdate ntp-wait ntpd ntptime ntp-keygen; do \ | mv debian/ntp/usr/bin/$file debian/ntp/usr/sbin/$file || exit; \ | done | mv: cannot stat 'debian/ntp/usr/bin/ntptime': No such file or directory | make: *** [install] Error 1 I think the interesting parts in the diff of the build logs of 1:4.2.6.p5+dfsg-3 and 1:4.2.6.p5+dfsg-3.1 is @@ -802,8 +964,8 @@ checking struct clockinfo for hz... no checking struct clockinfo for tickadj... (cached) no checking for struct timespec... yes -checking for struct ntptimeval... yes -checking for struct ntptimeval.time.tv_nsec... yes +checking for struct ntptimeval... no +checking for struct ntptimeval.time.tv_nsec... no checking for inline... inline checking whether char is unsigned... no checking size of signed char... 1 and @@ -991,7 +1153,7 @@ checking half-heartedly for 'noprintf' in the kernel... _noprintf checking for a default value for 'tick'... 100L/hz checking for a default value for 'tickadj'... 500/hz -checking if we want and can make the ntptime utility... yes +checking if we want and can make the ntptime utility... no checking if we want and can make the tickadj utility... yes checking if we want and can make the timetrim utility... no checking if we want to build the NTPD simulator... no For the full build logs, please see https://buildd.debian.org/status/package.php?p=ntp&suite=unstable. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#756784: visp: FTBFS on powerpc
On 2014-08-01 18:53:06, Fabien Spindler wrote: > I was able to deploy a Debian powerpc arch where I tried to reproduce > without success the error reported during ViSP build. > > The test doesn't fail any more. I suspect that a 3rd party was updated. Is > it possible to restart the build of the package. You can ask on debian-wb-t...@lists.debian.org for a give back. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#756677: libvigraimpex: [hdf5 transition] please support hdf5 1.8.13 new packaging layout
On 2014-08-01 Gilles Filippini wrote: > Source: libvigraimpex > Version: 1.9.0+dfsg-8 > Severity: important > Tags: patch > User: p...@debian.org > Usertags: HDF5-transition > Hi, > The hdf5 1.8.13 package in experimental features a new layout for > headers and libraries, so that all the binary packages are now > co-installable. > Please find attached a patch proposal to support both the current > and the new layouts. > Because this bug is in the way of the hdf5 transition I intend to NMU > in a few days. I apologize for the urge, and I hope this approach won't > offend you. Please tell me otherwise. [...] Hello, please be aware that libvigraimpex is orphaned/QA maintained. And it is also somewhat broken. * 1.9.0 nowadays FTBFS with a testsuite error in ix86 * 1.10 (experimental) FTBFS on mips (I could not reproduce the amd64 error there.) cu Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756784: visp: FTBFS on powerpc
I was able to deploy a Debian powerpc arch where I tried to reproduce without success the error reported during ViSP build. The test doesn't fail any more. I suspect that a 3rd party was updated. Is it possible to restart the build of the package. Thanks Fabien Le 01/08/14 18:41, Sebastian Ramacher a écrit : Source: visp Version: 2.9.0-3 Severity: serious Justification: fails to build from source viisp failed to build on powerpc with: | Start 90: videoReader | 90/135 Test #90: videoReader ...***Exception: SegFault 0.34 sec ... | 99% tests passed, 1 tests failed out of 135 | | Total Test time (real) = 137.03 sec | | The following tests FAILED: |90 - videoReader (SEGFAULT) | Errors while running CTest | make[2]: *** [test] Error 8 | Makefile:116: recipe for target 'test' failed The full log is available at https://buildd.debian.org/status/fetch.php?pkg=visp&arch=powerpc&ver=2.9.0-3&stamp=1405961889. Please take a look. Cheers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756785: scitkit-learn: FTBFS on armel
Source: scikit-learn Version: 0.15.0-1 Severity: serious Justification: fails to build from source (but built successfully in the past) scikit-learn failed to build on armel with: | == | FAIL: sklearn.feature_extraction.tests.test_text.test_tfidf_no_smoothing | -- | Traceback (most recent call last): | File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest | self.test(*self.arg) | File "/«PKGBUILDDIR»/debian/python-sklearn/usr/lib/python2.7/dist-packages/sklearn/feature_extraction/tests/test_text.py", line 357, in test_tfidf_no_smoothing | tr.fit_transform, X).toarray() | File "/«PKGBUILDDIR»/debian/python-sklearn/usr/lib/python2.7/dist-packages/sklearn/utils/testing.py", line 186, in assert_warns_message | % func.__name__) | AssertionError: No warning raised when calling fit_transform | | == | FAIL: sklearn.metrics.tests.test_metrics.test_precision_recall_curve_toydata | -- | Traceback (most recent call last): | File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest | self.test(*self.arg) | File "/«PKGBUILDDIR»/debian/python-sklearn/usr/lib/python2.7/dist-packages/sklearn/metrics/tests/test_metrics.py", line 1224, in test_precision_recall_curve_toydata | assert_raises(Exception, precision_recall_curve, y_true, y_score) | AssertionError: Exception not raised | | -- | Ran 2676 tests in 1542.680s | | FAILED (SKIP=16, failures=2) | make[1]: *** [python-test2.7] Error 1 The full build log is available at https://buildd.debian.org/status/fetch.php?pkg=scikit-learn&arch=armel&ver=0.15.0-1&stamp=1405822256. Please take a look. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#756747: nmu: zanshin_0.2.1-1
On 2014-08-01 13:43, Emilio Pozuelo Monfort wrote: > [...] >> Also, the ben file of the auto transition seems broken, as >> libkontactinterface4 >> will match libkontactinterface4a, so, maybe it should be replaced with >> /\b(libkontactinterface4)\b/ > > I see. Another option may be "libkontactinterface4", but IIRC exact matches > perform worse than regexes in ben. Niels, what do you think? > > Cheers, > Emilio > Optimially we would use exact package name, but yes, Ben had a horrible performance with those. I tried to create the same in regex, but I never got it right, so I gave up in the end. The particular suggestion works for the particular example, but fails with dashes: $ echo a-b | perl -ne 'print "MATCH\n" if m/\ba\b/' MATCH So, if you had libkontactinterface4 and libkontactinterface4-a, then the regex would still be broken even with your suggestion. ~Niels -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756784: visp: FTBFS on powerpc
Source: visp Version: 2.9.0-3 Severity: serious Justification: fails to build from source viisp failed to build on powerpc with: | Start 90: videoReader | 90/135 Test #90: videoReader ...***Exception: SegFault 0.34 sec ... | 99% tests passed, 1 tests failed out of 135 | | Total Test time (real) = 137.03 sec | | The following tests FAILED: |90 - videoReader (SEGFAULT) | Errors while running CTest | make[2]: *** [test] Error 8 | Makefile:116: recipe for target 'test' failed The full log is available at https://buildd.debian.org/status/fetch.php?pkg=visp&arch=powerpc&ver=2.9.0-3&stamp=1405961889. Please take a look. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#741147: mutt: Mutt generated smime signatures fail verification in icedove/thunderbird
Hi, apparently caused by openssl defaulting to SHA256 digest bacause of #694738. Workaround: in /etc/Muttrc.d/smime.rc change the line set smime_sign_command="openssl smime -sign -signer %c -inkey %k -passin stdin -in %f -certfile %i -outform DER" to set smime_sign_command="openssl smime -sign -md SHA1 -signer %c -inkey %k -passin stdin -in %f -certfile %i -outform DER" Regards, Raoul -- - Raoul Gunnar Borenius Phone : +49 711 63314-206 DFN-Verein, Geschäftsstelle Stuttgart Fax: +49 711 63314-133 Lindenspürstr.32 E-Mail : boren...@dfn.de D-70176 Stuttgart WWW: http://www.dfn.de - - Deutsches Forschungsnetz -- - Germany's National Research and Education Network - - smime.p7s Description: S/MIME cryptographic signature
