Bug#754670: ibus: FTBFS: if python-gi-dev is installed
Hi,
I can reproduce this FTBFS bug. (libpcrc3 and related packages are at
hold with testing version)
| dh_install --fail-missing -X.la
| dh_install: usr/lib/python2.7/dist-packages/gi/overrides/IBus.py exists in
debian/tmp but is not installed to anywhere
| dh_install: usr/lib/python2.7/dist-packages/gi/overrides/IBus.pyo exists in
debian/tmp but is not installed to anywhere
| dh_install: usr/lib/python2.7/dist-packages/gi/overrides/IBus.pyc exists in
debian/tmp but is not installed to anywhere
| dh_install: usr/lib/python3/dist-packages/gi/overrides/IBus.py exists in
debian/tmp but is not installed to anywhere
| dh_install:
usr/lib/python3/dist-packages/gi/overrides/__pycache__/IBus.cpython-34.pyc
exists in debian/tmp but is not installed to anywhere
| dh_install:
usr/lib/python3/dist-packages/gi/overrides/__pycache__/IBus.cpython-34.pyo
exists in debian/tmp but is not installed to anywhere
Removing --fail-missing maybe a short term fix but what are these files
in gi/overrides directories are for. IBus.py has:
| from gi.repository import GObject
|
| from ..overrides import override
|
| # for newer pygobject: https://bugzilla.gnome.org/show_bug.cgi?id=686828
| # from ..module import get_introspection_module
| # IBus = get_introspection_module('IBus')
| from ..importer import modules
| IBus = modules['IBus']._introspection_module
|
As I see SPEC file of FEDORA, when this is generated, it makes some
extra package to store the result:
| %if %with_python2_override_pkg
| %package py2override
| Summary:IBus python2 override library
| Group: System Environment/Libraries
| Requires: %{name}-libs%{?_isa} = %{version}-%{release}
| # Owner of %%python2_sitearch/gi/overrides
| Requires: pygobject3-base
|
| %description py2override
| This is a python2 override library for IBus. The python files override
| some functions in gobject-introspection.
| %endif
...
In debian speak, this is something like ibus-py2override package.
I have no idea if this is required by some packages on Debian. So far,
I have not seen one. Does any one have idea?
Also, overrides under python3 side are not packaged.
Changwoo, do you have any use for installing thise files?
Regards,
Osamu
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725593: FTBFS: automake: error: global options already processed
Hi, I build the package on mips64el and 386, also have the same issue. This problem maybe in all ports.
Bug#693669: Lower wine dependency to a recommendation
Dear maintainer, playonlinux depends on wine | wine-unstable but those package do not have to be installed on amd64 to have operational wine. For example on amd64 I'm getting the following error when I'm trying to install playonlinux while I have wine-unstable:i386 installed: Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: playonlinux : Depends: wine but it is not going to be installed or wine-unstable but it is not going to be installed E: Unable to correct problems, you have held broken packages. Needless to say that such hard dependency make playonlinux unnecessary difficult to install. Please consider to demote wine | wine-unstable to Recommends. Furthermore wine-unstable no longer provides `wine` executable (it provides `wine-unstable`) hence dialog PlayOnLinux cannot find wine (from Wine) You should install it to use PlayOnLinux still appears and probably needs patching. IMHO the very presence of this dialog destroys the argument for keeping wine | wine-unstable in Depends. Thanks for consideration. -- Regards, Dmitry Smirnov GPG key : 4096R/53968D1B --- All that is necessary for the triumph of evil is that good men do nothing. signature.asc Description: This is a digitally signed message part.
Bug#755021: Found Workaround
Dear Support Team FYI I've reinstalled Jessie today from an iso file and Wifi was working again, even with all upgrades. Mousepad was still very slow... Following steps solved the issue (thanks reinob from forums.debian.net): Created /etc/X11/xorg.conf.d/synaptics.conf following content synaptics.conf worked fine for me Section InputClass Identifier touchpad Driver synaptics MatchIsTouchpad on Option MinSpeed 1 Option MaxSpeed 2 Option AccelFactor 0.5 EndSection Reference: http://forums.debian.net/viewtopic.php?f=6t=115925 Best Regards reto -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754828: fixed in nvidia-graphics-drivers 340.24-1
I'm afraid the problem isn't fixed for multi-arch systems: the Unstable nvidia isn't installable because libgl1-nvidia-glx:i386 has no v340.24-1. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754828: fixed in nvidia-graphics-drivers 340.24-1
On Sun, Jul 20, 2014 at 12:06 AM, Tsu Jan tsujan2...@gmail.com wrote: I'm afraid the problem isn't fixed for multi-arch systems: the Unstable nvidia isn't installable because libgl1-nvidia-glx:i386 has no v340.24-1. It's fixed; the i386 packages are currently being built by the Debian buildds [1] and awaiting upload to the mirror network, whereas the amd64 packages are already being mirrored. As with most packages, there's always going to be a slight delay between the maintainer uploading a package to ftpmaster, and the package on any specific architecture being made available to users (depending on a number of factors, including buildd delays, outdated mirrors, etc.). Regards, Vincent [1] https://buildd.debian.org/status/package.php?p=nvidia-graphics-drivers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754828: fixed in nvidia-graphics-drivers 340.24-1
OK! Thank you for your fast reply! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754532: Conflicting build-depencies: libgnomevfs2-dev/libgnutls-dev
Hi! On 2014-07-12 at 07:23 (CEST), Andreas Metzler wrote: Hello, camorama's b-d cannot be installed since libgnomevfs2-dev has been upgraded to use libgnutls28-dev instead of libgnutls-dev. Afaict the build-dependency on libgnutls-dev can simply be dropped: Attached, you will find a patch fixing the issue reported above. Hope that helps. -- Matteo F. Vescovi | Debian Maintainer GnuPG KeyID: 4096R/0x8062398983B2CF7A Description: Fix FTBFS due to conflicting build-deps libgnomevfs2-dev/libgnutls-dev Author: Matteo F. Vescovi mfvesc...@gmail.com Origin: Debian Bug-Debian: https://bugs.debian.org/754532 Last-Update: 2014-07-20 --- a/debian/control +++ b/debian/control @@ -2,7 +2,7 @@ Section: gnome Priority: optional Maintainer: Leo Costela cost...@debian.org -Build-Depends: libgconf2-dev, file, gettext, libgtk2.0-dev (= 2.10), libglib2.0-dev, pkg-config, libgnutls-dev, cdbs, libgnomevfs2-dev, debhelper (= 5), libpng12-dev, libgnome2-dev, libgnomeui-dev, libglade2-dev, libx11-dev, libxml-parser-perl, libv4l-dev +Build-Depends: libgconf2-dev, file, gettext, libgtk2.0-dev (= 2.10), libglib2.0-dev, pkg-config, cdbs, libgnomevfs2-dev, debhelper (= 5), libpng12-dev, libgnome2-dev, libgnomeui-dev, libglade2-dev, libx11-dev, libxml-parser-perl, libv4l-dev Homepage: http://camorama.fixedgear.org Standards-Version: 3.7.2 signature.asc Description: Digital signature
Bug#746358: systemd: system boot hangs if /etc/fstab contains an NFS mount: how about wheezy-backports?
Control: reopen -1 I'm not sure what to do with this really. Yesterday I upgraded my wheezy system and come to this very issue there. Because I had systemd installed from wheezy-backports, and now this bug reappeared in a backported version, ofcourse initscripts in wheezy is not patched. At least, either systemd should have a Breaks: initscripts fixed-version, or the same fix should be provided in wheezy initscripts. 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#755381: src:totalopenstation: Missing manpages
Package: src:totalopenstation Version: 0.3-3 Severity: normal Tags: patch Dear Maintainer, CLI scripts are actually missing the manual pages. Upstream is trying to find a way to provide them directly from documentation, but had no luck for now. Attached, you'll find a couple of manual pages solving the issue for: * totalopenstation-cli-connector * totalopenstation-cli-parser 'totalopenstation-gui' script is used to simply launch the graphical interface for the other commands. So probably won't ever have a manual page. Hope that helps. Cheers. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- Matteo F. Vescovi | Debian Maintainer GnuPG KeyID: 4096R/0x8062398983B2CF7A .\ DO NOT MODIFY THIS FILE! It was generated by help2man 1.45.1. .TH TOTALOPENSTATION-CLI-CONNECTOR 1 July 2014 totalopenstation-cli-connector 0.3 User Commands .SH NAME totalopenstation-cli-connector \- test manual page .SH SYNOPSIS .B totalopenstation-cli-connector [\fI\,option\/\fR] \fI\,arg1 \/\fR[\fI\,option\/\fR] \fI\,arg2 \/\fR... .SH OPTIONS .TP \fB\-h\fR, \fB\-\-help\fR show this help message and exit .TP \fB\-m\fR MODEL, \fB\-\-model\fR=\fI\,MODEL\/\fR select input MODEL .TP \fB\-p\fR PORT, \fB\-\-port\fR=\fI\,PORT\/\fR select input SERIAL PORT .TP \fB\-o\fR FILE, \fB\-\-outfile\fR=\fI\,FILE\/\fR select output FILE (do not specify for stdout) .SH SEE ALSO The full documentation for .B totalopenstation-cli-connector is maintained as a Texinfo manual. If the .B info and .B totalopenstation-cli-connector programs are properly installed at your site, the command .IP .B info totalopenstation-cli-connector .PP should give you access to the complete manual. .\ DO NOT MODIFY THIS FILE! It was generated by help2man 1.45.1. .TH TOTALOPENSTATION-CLI-PARSER 1 July 2014 totalopenstation-cli-parser 0.3 User Commands .SH NAME totalopenstation-cli-parser \- test manual page .SH SYNOPSIS .B totalopenstation-cli-parser [\fI\,option\/\fR] \fI\,arg1 \/\fR[\fI\,option\/\fR] \fI\,arg2 \/\fR... .SH OPTIONS .TP \fB\-h\fR, \fB\-\-help\fR show this help message and exit .TP \fB\-i\fR FILE, \fB\-\-infile\fR=\fI\,FILE\/\fR select input FILE (do not specify for stdin) .TP \fB\-o\fR FILE, \fB\-\-outfile\fR=\fI\,FILE\/\fR select output FILE (do not specify for stdout) .TP \fB\-f\fR FORMAT, \fB\-\-input\-format\fR=\fI\,FORMAT\/\fR select input FORMAT .TP \fB\-t\fR FORMAT, \fB\-\-output\-format\fR=\fI\,FORMAT\/\fR select input FORMAT .TP \fB\-\-overwrite\fR overwrite existing output file .TP \fB\-\-list\fR list the available input and output formats .SH SEE ALSO The full documentation for .B totalopenstation-cli-parser is maintained as a Texinfo manual. If the .B info and .B totalopenstation-cli-parser programs are properly installed at your site, the command .IP .B info totalopenstation-cli-parser .PP should give you access to the complete manual. signature.asc Description: Digital signature
Bug#755382: ITP: fonts-adobe-sourcehansans-cn -- “Source Han Sans CN” A sans-serif Pan-CJK font family (CN subset) that is offered in seven weights
Package: wnpp Severity: wishlist Owner: LIU Dongyuan liu.dongy...@gmail.com * Package name: fonts-adobe-sourcehansans-cn Version : 1.000 Upstream Author : Ken Lunde lu...@adobe.com * URL : http://sourceforge.net/projects/source-han-sans.adobe/ * License : Apache 2.0 Description : “Source Han Sans CN” A sans-serif Pan-CJK font family (CN subset) that is offered in seven weights Source Han Sans is a sans serif Pan-CJK font family that is offered in seven weights—ExtraLight, Light, Normal, Regular, Medium, Bold, and Heavy—and in several OpenType/CFF-based deployment configurations to accommodate various system requirements or limitations. As the name suggests, Pan-CJK fonts are intended to support the characters necessary to render or display text in Simplified Chinese, Traditional Chinese, Japanese, and Korean. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755383: ITP: fonts-adobe-sourcehansans-twhk -- “Source Han Sans TWHK” A sans-serif Pan-CJK font family (TWHK subset) that is offered in seven weights
Package: wnpp Severity: wishlist Owner: LIU Dongyuan liu.dongy...@gmail.com * Package name: fonts-adobe-sourcehansans-twhk Version : 1.000 Upstream Author : Ken Lunde lu...@adobe.com * URL : http://sourceforge.net/projects/source-han-sans.adobe/ * License : Apache 2.0 Description : “Source Han Sans TWHK” A sans-serif Pan-CJK font family (TWHK subset) that is offered in seven weights Source Han Sans is a sans serif Pan-CJK font family that is offered in seven weights—ExtraLight, Light, Normal, Regular, Medium, Bold, and Heavy—and in several OpenType/CFF-based deployment configurations to accommodate various system requirements or limitations. As the name suggests, Pan-CJK fonts are intended to support the characters necessary to render or display text in Simplified Chinese, Traditional Chinese, Japanese, and Korean. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755202: network-manager: keeps creating and using new connection eth0 that does not work
severity: important thanks Dear network-manager maintainers, On Fri, Jul 18, 2014 at 09:35:52PM +0200, Felix C. Stegerman wrote: NetworkManager has started creating a new wired connection eth0 after/during boot; this connection has ipv4 (and ipv6) disabled, and thus provides no connectivity. I can manually select my original wired connection (standard dhcp) in gnome3 (or using nmcli), but it keeps creating the eth0 interface and using it after restarting. I'm seeing this as well. Furthermore, it seems to get in the way of other interfaces such as wifi, meaning that if you're regularly using a wifi, every time a new eth0 interface kicks in you lose connectivity. To give in idea, currently my laptop has 9 bogus eth0 interfaces, in addition to the right one (i.e., ifupdown (eth0) and another static one I've configured). I haven't yet understood when exactly network-manager adds a new one, but at each resume for suspend I lose connectivity, but not only. For instance, since the last resume (~1 hour ago) I had to manually disable a bogus eth0 interface at least 3 times. As you can imagine, this is really getting in the way of using my computer productively --- hence my severity tweaking. If you've ideas on how I can help you debug the problem, let me know. Cheers. -- Stefano Zacchiroli . . . . . . . z...@upsilon.cc . . . . o . . . o . o Maître de conférences . . . . . http://upsilon.cc/zack . . . o . . . o o Former Debian Project Leader . . @zack on identi.ca . . o o o . . . o . « the first rule of tautology club is the first rule of tautology club » signature.asc Description: Digital signature
Bug#748867: [Pkg-chromium-maint] Bug#748867: Missing API keys, some features of chromium are disabled
❦ 7 juillet 2014 00:35 -0400, Michael Gilbert mgilb...@debian.org : But I didn´t found anything on the net to tell Chromium to just shut up with the warning. Is there a way? I am already considering to grep the source for the warning, disable it and build my own package. If you do find a solution to silence the warning, please post it here. Hi Mike! Does this mean that the API key won't be back when Chromium 36 will be uploaded to unstable? -- /* * Hash table gook.. */ 2.4.0-test2 /usr/src/linux/fs/buffer.c signature.asc Description: PGP signature
Bug#755384: mplayer2: enable support for joystick device at compile time
Package: mplayer2 Version: 2.0-728-g2c378c7-2+b1 Severity: wishlist Dear Maintainer, could you please enable support for joystick device for linux targets? AFAICS you'd need to add --enable-joystick explicitly when calling the configure script. Thanks, Antonio -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (900, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-rc2-ao2 (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/bash Versions of packages mplayer2 depends on: ii liba52-0.7.4 0.7.4-17 ii libasound21.0.28-1 ii libass5 0.10.2-3 ii libavcodec55 6:10.2-1 ii libavformat55 6:10.2-1 ii libavresample16:10.2-1 ii libavutil53 6:10.2-1 ii libbluray11:0.6.0+dfsg-2 ii libbs2b0 3.1.0+dfsg-2 ii libc6 2.19-7 ii libcaca0 0.99.beta19-2 ii libcdio-cdda1 0.83-4.1 ii libcdio-paranoia1 0.83-4.1 ii libcdio13 0.83-4.1 ii libdca0 0.0.5-6 ii libdirectfb-1.2-9 1.2.10.0-5 ii libdv41.0.0-6 ii libdvdread4 4.2.1-2 ii libenca0 1.15-2 ii libfaad2 2.7-8 ii libgif4 4.1.6-11 ii libgl1-mesa-glx [libgl1] 10.2.3-1 ii libjack0 [libjack-0.116] 1:0.124.1+20140122git5013bed0-3 ii libjpeg8 8d1-1 ii liblcms2-22.6-3 ii liblircclient00.9.0~pre1-1 ii libmad0 0.15.1b-8 ii libmng1 1.0.10-3 ii libmpg123-0 1.20.0-1 ii libncurses5 5.9+20140712-2 ii libogg0 1.3.2-1 ii libpng12-01.2.50-1 ii libpostproc52 6:0.git20120821-4 ii libpulse0 5.0-2 ii libquvi7 0.4.1-2.1 ii libsdl1.2debian 1.2.15-10 ii libsmbclient 2:4.1.9+dfsg-1 ii libspeex1 1.2~rc1.1-1 ii libswscale2 6:10.2-1 ii libtheora01.1.1+dfsg.1-3.2 ii libtinfo5 5.9+20140712-2 ii libvdpau1 0.7-2 ii libvorbis0a 1.3.2-1.4 ii libx11-6 2:1.6.2-2 ii libxext6 2:1.3.2-1 ii libxinerama1 2:1.1.3-1 ii libxss1 1:1.2.2-1 ii libxv12:1.0.10-1 ii libxvidcore4 2:1.3.3-1 ii libxxf86vm1 1:1.1.3-1 ii zlib1g1:1.2.8.dfsg-1 mplayer2 recommends no packages. mplayer2 suggests no packages. -- no debconf information -- Antonio Ospite http://ao2.it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755385: ITP: fonts-adobe-sourcehansans-jp -- “Source Han Sans JP” A sans-serif Pan-CJK font family (JP subset) that is offered in seven weights
Package: wnpp Severity: wishlist Owner: LIU Dongyuan liu.dongy...@gmail.com * Package name: fonts-adobe-sourcehansans-jp Version : 1.000 Upstream Author : Ken Lunde lu...@adobe.com * URL : http://sourceforge.net/projects/source-han-sans.adobe/ * License : Apache 2.0 Description : “Source Han Sans JP” A sans-serif Pan-CJK font family (JP subset) that is offered in seven weights Source Han Sans is a sans serif Pan-CJK font family that is offered in seven weights—ExtraLight, Light, Normal, Regular, Medium, Bold, and Heavy—and in several OpenType/CFF-based deployment configurations to accommodate various system requirements or limitations. As the name suggests, Pan-CJK fonts are intended to support the characters necessary to render or display text in Simplified Chinese, Traditional Chinese, Japanese, and Korean. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755386: ITP: fonts-adobe-sourcehansans-kr -- “Source Han Sans KR” A sans-serif Pan-CJK font family (KR subset) that is offered in seven weights
Package: wnpp Severity: wishlist Owner: LIU Dongyuan liu.dongy...@gmail.com * Package name: fonts-adobe-sourcehansans-kr Version : 1.000 Upstream Author : Ken Lunde lu...@adobe.com * URL : http://sourceforge.net/projects/source-han-sans.adobe/ * License : Apache 2.0 Description : “Source Han Sans KR” A sans-serif Pan-CJK font family (KR subset) that is offered in seven weights Source Han Sans is a sans serif Pan-CJK font family that is offered in seven weights—ExtraLight, Light, Normal, Regular, Medium, Bold, and Heavy—and in several OpenType/CFF-based deployment configurations to accommodate various system requirements or limitations. As the name suggests, Pan-CJK fonts are intended to support the characters necessary to render or display text in Simplified Chinese, Traditional Chinese, Japanese, and Korean. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755387: libvirt-bin: Wheezy guest doesn't ACPI power button events
Package: libvirt-bin Version: 1.2.4-3 Severity: normal I have a Wheezy guest I can't shutdown cleanly from libvirt (i.e. without logging into VM and shutting down VM from within VM) because the guest is failing to get ACPI events. The guest didn't have issues before jessie (i.e. while on Wheezy) and does have acpid and I've even tried adding acpi-support to no avail. acpi is enabled as a feature in the XML. The strange thing is a Windows 8.1 guest is not having issues with this (it was created around the same time as the wheezy guest, while host was on wheezy). The command line generated by libvirt is: LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -name name -S -machine pc-1.1,accel=kvm,usb=off -m 256 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid uuid -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/name.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot order=cd,menu=on,strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=image,if=none,id=drive-virtio-disk0,format=raw -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0 -netdev tap,fd=25,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=mac,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-seria l,chardev=charserial0,id=serial0 -device usb-tablet,id=input0 -vnc 127.0.0.1:1 -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 Neither libvirt nor the guest produce any logs as result of issuing the shutdown command from virt-manageer or virsh. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libvirt-bin depends on: ii adduser 3.113+nmu3 ii gettext-base 0.18.3.2-3 ii init-system-helpers 1.19 ii libapparmor1 2.8.0-5.1+b1 ii libaudit11:2.3.7-1 ii libavahi-client3 0.6.31-4 ii libavahi-common3 0.6.31-4 ii libblkid12.20.1-5.8 ii libc62.19-7 ii libcap-ng0 0.7.3-1.1 ii libdbus-1-3 1.8.6-1 ii libdevmapper1.02.1 2:1.02.85-2 ii libfuse2 2.9.3-12 ii libgcrypt11 1.5.3-4 ii libgnutls26 2.12.23-17 ii libnetcf11:0.2.3-4 ii libnl-3-200 3.2.24-2 ii libnl-route-3-2003.2.24-2 ii libnuma1 2.0.9-1 ii libparted0debian12.3-20 ii libpcap0.8 1.5.3-4 ii libpciaccess00.13.2-3 ii librados20.80.1-2 ii librbd1 0.80.1-2 ii libreadline6 6.3-6 ii libsasl2-2 2.1.26.dfsg1-11 ii libselinux1 2.3-1 ii libssh2-11.4.3-3 ii libsystemd-daemon0 204-14 ii libudev1 204-14 ii libvirt0 1.2.4-3 ii libxen-4.3 4.3.0-3+b1 ii libxenstore3.0 4.3.0-3+b1 ii libxml2 2.9.1+dfsg1-4 ii libyajl2 2.1.0-1 ii logrotate3.8.7-1 Versions of packages libvirt-bin recommends: ii bridge-utils1.5-9 ii dmidecode 2.12-3 ii dnsmasq-base2.71-1 ii ebtables2.0.10.4-3 ii iproute 1:3.15.0-2 ii iptables1.4.21-2 ii libxml2-utils 2.9.1+dfsg1-4 ii netcat-openbsd 1.105-7 ii parted 2.3-20 ii pm-utils1.4.1-15 ii qemu2.0.0+dfsg-6+b1 ii qemu-kvm2.0.0+dfsg-6+b1 Versions of packages libvirt-bin suggests: pn apparmor none pn auditd none ii policykit-1 0.105-6 pn radvdnone ii systemd 204-14 pn systemtapnone -- Configuration Files: /etc/default/libvirt-guests changed [not included] /etc/libvirt/qemu.conf [Errno 13] Permission denied: u'/etc/libvirt/qemu.conf' -- 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#754988: transition: libjpeg-turbo
Hi Emilio, On Sat, Jul 19, 2014, at 00:11, Emilio Pozuelo Monfort wrote: Hi Ondřej, thanks for this report. On 16/07/14 17:47, Ondřej Surý wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition As voted by tech-ctte in #717076, we are going to prepare the transition from IIJ jpeg to libjpeg-turbo implementation. The transition plan as asked in the resolution: 1. Since nothing depends on libjpeg8 API we will bump back to libjpeg.so.62 with extra decode from memory buffer interface (jpeg_mem_src/jpeg_mem_dest). NOTES: * Fedora/OpenSUSE has also settled down on libjpeg.so.62, so that would make us cross-distro compatible. * Ubuntu has already transitioned to libjpeg-turbo8, so it will be up to them if they bump back to libjpeg62. 2. The proposed libjpeg-turbo packages implementing libjpeg62 will be uploaded to experimental before end of July 2014. We will announce that to debian-devel and leave a reasonable period of time for people to test their packages to recompile against libjpeg-turbo. I propose we provide libjpeg-dev dummy (not virtual) package in experimental, so there's no clash between libjpeg8-dev and libjpeg-turbo-dev. 3. The updated libjpeg-turbo packages implementing libjpeg62 and libjpeg-turbo-dev (providing libjpeg-dev virtual package) will be uploaded to unstable at the end of August 2014. This upload will be synchronized with libjpeg8 maintainer (or NMUed) to remove virtual libjpeg-dev from libjpeg8-dev at the same time (or very close to it). Cheers, Ondrej Ben file: title = libjpeg-turbo; is_affected = .depends ~ libjpeg8 | .depends ~ libjpeg62; is_good = .depends ~ libjpeg62; is_bad = .depends ~ libjpeg8; There already is a libjpeg62 package, built from src:libjpeg6b. What's the plan here? Drop src:libjpeg6b? Take over the libjpeg62 name and rename current libjpeg62 to libjpeg62-ijg, and make it Provide and Conflict libjpeg62? Something else? Somehow I didn't realize that we still have libjpeg6b in the archive. Dropping/Replacing src:libjpeg6b makes most sense to me and I can probably do that from src:libjpeg-turbo (epoch would need to be introduced anyway to replace IIJ JPEG packages). dak also shows that it should not be a problem: Checking reverse dependencies... # Broken Depends: ecere-sdk: libecere0 [amd64 armel armhf i386 mips mipsel powerpc] emacs23: emacs23 [hurd-i386] emacs23-lucid [hurd-i386] lsb: lsb-desktop # Broken Build-Depends: eagle/non-free: libjpeg62-dev ecere-sdk: libjpeg62-dev emacs23: libjpeg62-dev Those looks more like relicts than real depends. I'm especially interested in knowing whether libjpeg-turbo will be able to migrate before anything else does (i.e whether it will be a smooth transition) but until I fully understand what packages there will be, and what conflicts, I can't know that. I do think so. I will prepare update libjpeg-turbo packages in experimental during next week and let you know to review the changes. Ondrej -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#718601: updated fet package ready
On Sat, Jul 12, 2014 at 11:56:30PM +0200, Mattia Rizzolo wrote: I prepared an updated package for fet, upstream versin 5.22.0. Uploading to DELAYED/15, thanks. -- Andrea Colangelo | http://andreacolangelo.com Debian Developer war...@debian.org | Ubuntu Developer war...@ubuntu.com signature.asc Description: Digital signature
Bug#755362: sysdig: FTBFS on kfreebsd-*: scap.c:1015: undefined reference to `scap_readbuf'
control: forwarded -1 https://github.com/draios/sysdig/pull/212 control: tags -1 + fixed-upstream patch Mraw! On Sat, Jul 19, 2014 at 11:27:37PM +0200, Cyril Brulebois wrote: your package no longer builds on kfreebsd-*: Yepp, I fixed that upstream [1], but was not motivated enough to reupload just because of this. Upstream is usually quick with new releases, so maybe they will just release a fixed version. :) Greets Evgeni [1] https://github.com/draios/sysdig/commit/257b75ffdf99137dde5a73ae7f57a419ff5996a7 -- Bruce Schneier can read and understand Perl programs. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754670: ibus: FTBFS: if python-gi-dev is installed
2014-07-20 (일), 15:18 +0900, Osamu Aoki: ... In debian speak, this is something like ibus-py2override package. I have no idea if this is required by some packages on Debian. So far, I have not seen one. Does any one have idea? Also, overrides under python3 side are not packaged. Changwoo, do you have any use for installing thise files? In general, those g-i overrides provide additional or modified APIs when automatically generated g-i bindings are not enough. For example when automatic bindings don't look good in Python. And they are transparent; you don't have to specify explicitly to use the overridden code. So when the ibus g-i overrides are installed, the ibus programs in Python transparently use them. But interestingly, all ibus Python programs in Debian seem to work without the overrides. I still think the overrides should be installed, because they are the officially provided ibus Python APIs anyway. In Debian, the g-i overrides are packaged in python-* packages or sometimes in gir* packages. I have no idea which one is better. $ apt-file search /gi/overrides/ gedit: /usr/lib/python3/dist-packages/gi/overrides/Gedit.py gir1.2-dee-1.0: /usr/lib/python2.7/dist-packages/gi/overrides/Dee.py gir1.2-dee-1.0: /usr/share/pyshared/gi/overrides/Dee.py gir1.2-gexiv2-0.10: /usr/lib/python2.7/dist-packages/gi/overrides/GExiv2.py gir1.2-gexiv2-0.10: /usr/lib/python3/dist-packages/gi/overrides/GExiv2.py gir1.2-grip: /usr/lib/python2.7/dist-packages/gi/overrides/Grip.py gir1.2-grip: /usr/lib/python3/dist-packages/gi/overrides/Grip.py python-gi: /usr/lib/python2.7/dist-packages/gi/overrides/GIMarshallingTests.py python-gi: /usr/lib/python2.7/dist-packages/gi/overrides/GLib.py python-gi: /usr/lib/python2.7/dist-packages/gi/overrides/GObject.py python-gi: /usr/lib/python2.7/dist-packages/gi/overrides/Gdk.py python-gi: /usr/lib/python2.7/dist-packages/gi/overrides/Gio.py python-gi: /usr/lib/python2.7/dist-packages/gi/overrides/Gtk.py python-gi: /usr/lib/python2.7/dist-packages/gi/overrides/Pango.py python-gi: /usr/lib/python2.7/dist-packages/gi/overrides/__init__.py python-gi: /usr/lib/python2.7/dist-packages/gi/overrides/keysyms.py python-gst-1.0: /usr/lib/python2.7/dist-packages/gi/overrides/Gst.py python-gst-1.0: /usr/lib/python2.7/dist-packages/gi/overrides/GstPbutils.py python-gst-1.0: /usr/lib/python2.7/dist-packages/gi/overrides/_gi_gst.so python-gst-1.0-dbg: /usr/lib/python2.7/dist-packages/gi/overrides/_gi_gst_d.so python-v-sim: /usr/lib/python2.7/dist-packages/gi/overrides/v_sim.py python-v-sim: /usr/share/pyshared/gi/overrides/v_sim.py python3-gi: /usr/lib/python3/dist-packages/gi/overrides/GIMarshallingTests.py python3-gi: /usr/lib/python3/dist-packages/gi/overrides/GLib.py python3-gi: /usr/lib/python3/dist-packages/gi/overrides/GObject.py python3-gi: /usr/lib/python3/dist-packages/gi/overrides/Gdk.py python3-gi: /usr/lib/python3/dist-packages/gi/overrides/Gio.py python3-gi: /usr/lib/python3/dist-packages/gi/overrides/Gtk.py python3-gi: /usr/lib/python3/dist-packages/gi/overrides/Pango.py python3-gi: /usr/lib/python3/dist-packages/gi/overrides/__init__.py python3-gi: /usr/lib/python3/dist-packages/gi/overrides/keysyms.py python3-gst-1.0: /usr/lib/python3/dist-packages/gi/overrides/Gst.py python3-gst-1.0: /usr/lib/python3/dist-packages/gi/overrides/GstPbutils.py python3-gst-1.0: /usr/lib/python3/dist-packages/gi/overrides/_gi_gst.cpython-34m-x86_64-linux-gnu.so python3-gst-1.0-dbg: /usr/lib/python3/dist-packages/gi/overrides/_gi_gst.cpython-34dm-x86_64-linux-gnu.so $ Regards Changwoo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755094: transition: harfbuzz
On Sat, Jul 19, 2014 at 10:34:19AM +0200, Emilio Pozuelo Monfort wrote: I see the package in NEW is 0.9.30 but upstream has just released 0.9.32. Can you check if there are any other breaks in 0.9.32, and if so update to it? ---end quoted text--- No other breaks there. Anyways, the new package is in git now. -- أحمد المحمودي (Ahmed El-Mahmoudy) Digital design engineer GPG KeyID: 0xEDDDA1B7 GPG Fingerprint: 8206 A196 2084 7E6D 0DF8 B176 BC19 6A94 EDDD A1B7 signature.asc Description: Digital signature
Bug#748867: [Pkg-chromium-maint] Bug#748867: Bug#748867: Missing API keys, some features of chromium are disabled
Hi, Il 20/07/2014 10:08, Vincent Bernat ha scritto: Does this mean that the API key won't be back when Chromium 36 will be uploaded to unstable? I just activated Google+ Api for the chromium Debian package, please let me know if this fixed the issue. Cheers, Giuseppe signature.asc Description: OpenPGP digital signature
Bug#755388: [kmail] Kmail mail directory messages keep returning
Package: kmail Version: 4:4.12.4-1 Severity: normal --- Please enter the report below this line. --- If I delete new messages from any subfolder to the kmail mail directory, next time I click on that subfolder, update or check mail, those messages will return to their former subfolders. This is so even if trash folders were cleared. Only way to permanently get rid of them is to expire the subfolder, for example, one day back. Does not effect inbox placed in this folder-tree. Inbox in local-mail does have this problem, however. could be corollary to other bugs I submitted or be relevant to akonadi. --- System information. --- Architecture: amd64 Kernel: Linux 3.2.0-4-amd64 Debian Release: jessie/sid 500 unstableftp.us.debian.org 500 testing ftp.us.debian.org 500 sid linux.dropbox.com --- Package information. --- Depends (Version) | Installed ===-+-=== perl| 5.18.2-7 kde-runtime ( 4:4.10) | 4:4.13.1-1 kdepim-runtime(= 4:4.10.2) | 4:4.12.4-2 kdepimlibs-kio-plugins | 4:4.12.4-1 libakonadi-calendar4 (= 4:4.11.1) | 4:4.12.4-1 libakonadi-contact4 (= 4:4.12.2) | 4:4.12.4-1 libakonadi-kde4 (= 4:4.12.2) | 4:4.12.4-1 libakonadi-kmime4 (= 4:4.12.2) | 4:4.12.4-1 libakonadiprotocolinternals1 (= 1.5.1) | 1.12.1-1+b1 libc6 (= 2.14) | 2.19-7 libcalendarsupport4 (= 4:4.12.4-1) | 4:4.12.4-1 libfolderarchive4(= 4:4.12.4-1) | 4:4.12.4-1 libgcc1(= 1:4.1.1) | 1:4.9.1-1 libgpgme++2 (= 4:4.12.2) | 4:4.12.4-1 libgrantlee-core0(= 0.3.0) | 0.3.0-5 libincidenceeditorsng4 (= 4:4.12.4-1) | 4:4.12.4-1 libkabc4 (= 4:4.12.2) | 4:4.12.4-1 libkalarmcal2 (= 4:4.8.1) | 4:4.12.4-1 libkcalcore4 (= 4:4.5.86) | 4:4.12.4-1 libkcalutils4 (= 4:4.5.86) | 4:4.12.4-1 libkcmutils4 (= 4:4.5.86) | 4:4.13.3-1 libkdecore5 (= 4:4.4.95) | 4:4.13.3-1 libkdepim4 (= 4:4.12.4-1) | 4:4.12.4-1 libkdeui5 (= 4:4.10.0) | 4:4.13.3-1 libkio5 (= 4:4.5.85) | 4:4.13.3-1 libkleo4 (= 4:4.12.4-1) | 4:4.12.4-1 libkmime4 (= 4:4.12.2) | 4:4.12.4-1 libknewstuff3-4 (= 4:4.5.85) | 4:4.13.3-1 libknotifyconfig4 (= 4:4.3.4) | 4:4.13.3-1 libkontactinterface4 (= 4:4.12.2) | 4:4.12.4-1 libkparts4(= 4:4.5.85) | 4:4.13.3-1 libkpgp4 (= 4:4.12.4-1) | 4:4.12.4-1 libkpimidentities4(= 4:4.12.2) | 4:4.12.4-1 libkpimtextedit4 (= 4:4.12.2) | 4:4.12.4-1 libkpimutils4 (= 4:4.12.2) | 4:4.12.4-1 libkprintutils4 (= 4:4.4.95) | 4:4.13.3-1 libksieveui4 (= 4:4.12.4-1) | 4:4.12.4-1 libktnef4 (= 4:4.12.2) | 4:4.12.4-1 libmailcommon4 (= 4:4.12.4-1) | 4:4.12.4-1 libmailimporter4 (= 4:4.12.4-1) | 4:4.12.4-1 libmailtransport4 (= 4:4.12.2) | 4:4.12.4-1 libmessagecomposer4 (= 4:4.12.4-1) | 4:4.12.4-1 libmessagecore4 (= 4:4.12.4-1) | 4:4.12.4-1 libmessagelist4 (= 4:4.12.4-1) | 4:4.12.4-1 libmessageviewer4(= 4:4.12.4-1) | 4:4.12.4-1 libnepomukcore4(= 4:4.9.3) | 4:4.12.4-1+b1 libpimcommon4(= 4:4.12.4-1) | 4:4.12.4-1 libqt4-dbus(= 4:4.5.3) | 4:4.8.6+dfsg-2 libqt4-network (= 4:4.5.3) | 4:4.8.6+dfsg-2 libqt4-xml (= 4:4.5.3) | 4:4.8.6+dfsg-2 libqtcore4 (= 4:4.7.0~beta1) | 4:4.8.6+dfsg-2 libqtgui4 (= 4:4.8.0) | 4:4.8.6+dfsg-2 libqtwebkit4 (= 2.2.0) | 2.2.1-7 libsendlater4(= 4:4.12.4-1) | 4:4.12.4-1 libsolid4 (= 4:4.3.4) | 4:4.13.3-1 libsoprano4 (= 2.9.0) | 2.9.4+dfsg-1.1 libstdc++6 (= 4.1.1) | 4.9.1-1 libtemplateparser4 (= 4:4.12.4-1) | 4:4.12.4-1 Recommends(Version) | Installed ===-+-=== gnupg-agent | 2.0.25-1 gnupg2 | 2.0.25-1 pinentry-qt4| OR pinentry-x11| Suggests
Bug#748867: [Pkg-chromium-maint] Bug#748867: Bug#748867: Missing API keys, some features of chromium are disabled
Hi! Am Sonntag, 20. Juli 2014, 10:48:45 schrieb Giuseppe Iuculano: Il 20/07/2014 10:08, Vincent Bernat ha scritto: Does this mean that the API key won't be back when Chromium 36 will be uploaded to unstable? I just activated Google+ Api for the chromium Debian package, please let me know if this fixed the issue. I don´t get a API key message on Chromium startup any more with 36.0.1985.125-0. So thems to be fixed here. Ciao, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 signature.asc Description: This is a digitally signed message part.
Bug#699141: get-orig-source
On Wed, 2 Jul 2014 11:48:12 Gianfranco Costamagna wrote: so now you can run ./debian/rules get-orig-source or directly uscan, with exactly the same behaviour. I think this is the best way, compliant with policy and not breaking the existing update procedure. I hope you agree, I committed it here http://anonscm.debian.org/gitweb/?p=pkg-virtualbox/virtualbox.git;a=commitdi ff;h=cb88c2a13a0fe8336831b3d63082fda348c02c4b I'm sorry to be a pest but this solution is incomplete. When `uscan` can be called with usual parameters you may need no get-orig-source target in first place. I sometimes introduce it in order to help remembering `uscan` arguments which I had troubles to recall for a while. If you decide to use get-orig-source then please make sure it is policy compliant: it should work when called from any directory, not just from current one (e.g. `/path/to/package/debian/rules get-orig-source`); it should fetch ceurrent version by default etc. You can find the simplest sample of properly working get-orig-source here: https://wiki.debian.org/onlyjob/get-orig-source Note $(PKD) variable and how it is passed to `uscan`. Thank you. -- Best wishes, Dmitry Smirnov. signature.asc Description: This is a digitally signed message part.
Bug#755389: synaptic: List remaining files for package Not installed (residual config)
Package: synaptic Version: 0.81.2 Severity: wishlist Tags: upstream Dear Maintainer, After un-installing some packages, they end up in the Not installed (residual config) state. In general case, this is ok as is and we can mark them for complete removal, but in some case it would be interresting first to be able to check the files that remains, so we can cross-check them before removal (my current use case being the package sysvinit-core for which I would like to be sure it is not linked to some customised stuff that I need to port to systemd's config). Would it be thinkable to list these files in the package - Property - Installed Files tab, or something similar? Best regards, Christophe -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages synaptic depends on: ii hicolor-icon-theme 0.13-1 ii libapt-inst1.5 1.0.6 ii libapt-pkg4.12 1.0.6 ii libatk1.0-0 2.12.0-1 ii libc62.19-7 ii libcairo-gobject21.12.14-4 ii libcairo21.12.14-4 ii libept1.4.12 1.0.12 ii libgcc1 1:4.9.0-7 ii libgdk-pixbuf2.0-0 2.30.7-1 ii libglib2.0-0 2.40.0-3 ii libgtk-3-0 3.8.6-1 ii libpango-1.0-0 1.36.3-1 ii libpangocairo-1.0-0 1.36.3-1 ii libstdc++6 4.9.0-7 ii libvte-2.90-91:0.36.3-1 ii libx11-6 2:1.6.2-2 ii libxapian22 1.2.18-1 ii libxext6 2:1.3.2-1 ii zlib1g 1:1.2.8.dfsg-1 Versions of packages synaptic recommends: ii gksu 2.0.2-6 ii libgtk2-perl 2:1.2491-4 ii policykit-10.105-6 ii rarian-compat 0.8.1-5 Versions of packages synaptic suggests: ii apt-xapian-index 0.46 ii deborphan1.7.28.8 pn dwww none ii menu 2.1.47 pn software-properties-gtk none pn tasksel none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748867: [Pkg-chromium-maint] Bug#748867: Bug#748867: Missing API keys, some features of chromium are disabled
❦ 20 juillet 2014 11:19 +0200, Martin Steigerwald mar...@lichtvoll.de : Does this mean that the API key won't be back when Chromium 36 will be uploaded to unstable? I just activated Google+ Api for the chromium Debian package, please let me know if this fixed the issue. I don´t get a API key message on Chromium startup any more with 36.0.1985.125-0. So thems to be fixed here. Mike disabled the message in this version but didn't add the API keys. The version that Giuseppe is talking about did not hit the mirrors yet. -- /* Binary compatibility is good American knowhow fuckin' up. */ 2.2.16 /usr/src/linux/arch/sparc/kernel/sunos_ioctl.c signature.asc Description: PGP signature
Bug#754078: crypt devices not brought online (backed by iscsi)
On Mon, 07 Jul 2014, Peter Palfrader wrote: } weasel@valiant:~$ cat /etc/crypttab } sda3_crypt UUID=81402c7d-3819-4860-b71f-ff0f808f599e none luks } sda6_crypt UUID=4385f6be-9584-4fd9-a3b8-92a2826311a5 /etc/luks/sda6.key luks } } aux1 /dev/disk/by-path/ip-172.22.118.11\:3260-iscsi-iqn.1992-04.com.emc\:storage.storcenter.sbg.palfrader.org.aux1-lun-0 /etc/luks/aux1.key luks,noearly } mailbak /dev/disk/by-path/ip-172.22.118.11\:3260-iscsi-iqn.1992-04.com.emc\:storage.storcenter.sbg.palfrader.org.mailbak-lun-0 /etc/luks/mailbak.key luks,noearly It seems systemd does not handle those backslashes that were previously required to escape the colon correctly. If I remove those, systemd brings up the interfaces. It's still very slow (because it tries to get them before iscsi is up). So, - it should correctly handle backslashes, - it should probably not block/timeout on bringing up noearly interfaces. -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal http://www.palfrader.org/ | `. `' Operating System | `-http://www.debian.org/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755390: libphobos-4.9-dev: does not build on armel/armhf anymore but did so in the past
Package: libphobos-4.9-dev Version: 4.9.0-7 Severity: normal Hi, libphobos built successfully with gdc 4.8 on armel/armhf in the past. However libphobos-4.9-dev is not available for these architectures anymore. All programs written in the programming language D FTBFS on armel/armhf at the moment. See https://bugs.debian.org/754665 for an example bug report filed against tatan. If this behaviour is intended please feel free to downgrade this bug report to wishlist. However I could not find any mention in the changelog. It would be nice if libphobos was supported on armel/armhf again. I will then request the removal of Tatan and all D based games maintained by the Games Team for ARM from the archive. Otherwise please raise the severity and tell me if I should reassign #754665 to libphobos-4.9-dev. Regards, Markus -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libphobos-4.9-dev depends on: ii gcc-4.9-base 4.9.0-7 ii zlib1g-dev1:1.2.8.dfsg-1 libphobos-4.9-dev recommends no packages. libphobos-4.9-dev suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755255: Acknowledgement (clang-3.5 segfault when compiling libsofia in freeswitch source tree)
I cannot reproduce the bug with clang 3.4.2-4 or, as you said, with more recent version of clang 3.5 (3.5~svn213400-1~exp1 in my case) Sylvestre PS: FYI, you code can be reduced much more. There is plenty of useless defines. On 20/07/2014 01:16, William King wrote: This crash appears fixed in clang-3.5 version: 1:3.5~svn213451-1~exp1 Attached is as minimal of a test file as delta can create(73 lines). For future reference I've also attached the small shell script that delta was using to minimize the file. I was using the follow to run delta: ./delta-2006.08.03/delta -test=./nua_client_test.sh -suffix=.c -cp_minimal=nua_client_minimal.c ./nua_client_preprocess.c Delta took about 9 hours to drop the ~70k lines preprocess file down to about 3k lines. Then running delta again on the latest file ~20 times was able to reduce it down to the 73 line file attached. Not yet sure why delta wasn't able to get to the final product directly. William King Senior Engineer Quentus Technologies, INC 1037 NE 65th St Suite 273 Seattle, WA 98115 Main: (877) 211-9337 Office: (206) 388-4772 Cell: (253) 686-5518 william.k...@quentustech.com On 07/19/2014 09:49 AM, Sylvestre Ledru wrote: tags 755255 + moreinfo thanks 2.2M files are not a reduce test case. See: http://www.gnu.org/software/gcc/bugs/ Thanks for providing it. Otherwise, probably nothing will happen on this bug. Sylvestre On 19/07/2014 18:29, William King wrote: The segfault can be replicated with the following two files. William King Senior Engineer Quentus Technologies, INC 1037 NE 65th St Suite 273 Seattle, WA 98115 Main: (877) 211-9337 Office: (206) 388-4772 Cell: (253) 686-5518 william.k...@quentustech.com On 07/19/2014 02:09 AM, Debian Bug Tracking System wrote: Thank you for filing a new Bug report with Debian. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): LLVM Packaging Team pkg-llvm-t...@lists.alioth.debian.org If you wish to submit further information on this problem, please send it to 755...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. ___ Pkg-llvm-team mailing list pkg-llvm-t...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-llvm-team -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755392: [reportbug-ng] Smart handling for bugs against general psedo package
Package: reportbug-ng Version: 1.31 Severity: wishlist In order to reduce the number of bugs reported against the general pseudo package that are more a support request rather than real bugs, the reportbug-ng shall perform some pre-filtering. The following list provide some idea about what can be done, but is not exclusive. 1) Display a warning message that this package is meant for experienced users only and can not use reportbug-ng to fill bugs against this package. 2) Ensure that call to reportbug launches reportbug-ng whenever DISPLAY environment variable is set by diverting /usr/bin/reportbug. Cheers, Abou Al Montacir signature.asc Description: This is a digitally signed message part
Bug#754441: GMastermind Relicensing
Hi Riley, thanks for inquirying. I am not the original author of GMastermind, thus I cannot relicense it, if you need that explicit statement, you need to ask Marko Riedel. I see you put it in CC, I do not know if that email address is current though. We just got permissions to incorporate GMastermind in GAP. I think the original author licensed it under GPLv2+. The README file is misleading and probably written in haste. Not only the header files explicitely say or later, but also the COPYING is the full GPL v2 or later statement. The README file says to refer to gpl.txt, this is probably inaccurate and COPYING was intended. I would say that the original intentions are pretty clear. Just in the case, I corrected the README file and also updated COPYING to the current GPL v2+ file from fsf, it had even the old FSF address. Perhaps that statement should be removed totally and just COPYING should be included. Riccardo Riley Baird wrote: Hi, I'm currently packaging GMastermind for Debian. In the process, it has been discovered that, according to a technical reading of the README, GMastermind is licensed under GPL-2 only (i.e. without or, at your option, any later version). However, according to the headers on the source files, it would appear that the intention was to license under GPL-2 or any later version. If you are fine with releasing your contributions under GPL-2+, please copy the following statement, fill in your name and send it to the email addresses below. (If not, then please send a message anyway so we know.) - I, YOUR NAME, irrevocably give permission to use, redistribute, modify and to distribute modified copies of any and all of my contributions to the program GMastermind under the terms of the GNU General Public License as published by the Free Software Foundation, either version 2 of the License, or (should anyone choose to do so) any later version. No warranty, not even the implied warranties of merchantability or fitness for a particular purpose, is given by this license grant. --- Please send this statement to the following email addresses: bm-2cvqnduybau5do2dfjtrn7zbaj246s4...@bitmessage.ch 754...@bugs.debian.org pkg-gnustep-maintain...@lists.alioth.debian.org gap-dev-disc...@nongnu.org NOTE: If you don't want to be bothered by licensing issues again, send the following statement in instead. I, YOUR NAME, release my contributions to the program GMastermind into the public domain. This applies worldwide. In some countries, this may not be legally possible; if so: I grant anyone the right to use this my contributions to the program GMastermind for any purpose, without any conditions, unless such conditions are required by law. - Thanks in advance, Riley Baird -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755393: appstream transition yields conflicting versioned Recommends
Source: appstream Version: 0.7.0-1 Severity: normal The libappstream0 and libappstream1 packages are co-installable, but have conflicting Recommends: For libappstream0: Version: 0.6.2-1 Recommends: appstream-index (= 0.6.2-1) For libappstream1: Version: 0.7.0-1 Recommends: appstream-index (= 0.7.0-1) meaning that either these Recommends dependencies are abusive or one of the packages could have problems due to unsatisfied Recommends. It's too late for libappstream0, but the libappstream1 one could yield future problems with a libappstream2. Moreover a versioned dependency on a library can affect upgrades: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755391 (though I regard this also as a bug in aptitude). -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/2 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751847: [pkg-fgfs-crew] Bug#751847: flightgear: Seneca II interior lighting
Control: reassing -1 flightgear-data Hello Ludovic, On 07/12/2014 08:57 PM, Ludovic Brenta wrote: Here is version 3 of my patch (this replaces and includes version 3). Changes relative to version 2: Thanks for working on this. (And kudos for using monotone for that. Did you import the entire fgdata? Or just that aircraft?) I must admit that I didn't test your changes, but I can confirm it still applies upstream (on 3.2.0 and master). I think it would be nice if this patch were included upstream in the upcoming FlightGear 3.2. I've just forwarded the patch to the fgfs-devel mailing list with you CC'ed. Regards Markus Wanner signature.asc Description: OpenPGP digital signature
Bug#755202: [Pkg-utopia-maintainers] Processed: severity of 755202 is important
Are you using managed=true mode in /etc/NetworkManager/NetworkManager.conf? A debug log might be helpful, run service network-manager stop NetworkManager --no-daemon --debug --log-level=debug Are those duplicated interfaces happening whenever networkmanager is restarted? -- 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#755394: base-files: move of os-release to /usr/lib breaks dracut initrd
Package: base-files Version: 7.4 Severity: critical Justification: breaks the whole system Using a dracut initrd the move of os-release to /usr/lib breaks the boot, as systemd can't find the os-release file, as it is located under /sysroot/usr/lib/os-release, but the symlink points to /usr/lib/os-release. The error message is: Specified switch root path /sysroot does not seem to be an OS tree. /etc/os-release is missing. Replacing the absolute symlink with a relative symlink /etc/os-release - ../usr/lib/os-release fixes the boot here. -- Daniel -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (103, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-rc5-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages base-files depends on: ii gawk [awk] 1:4.1.1+dfsg-1 ii mawk [awk] 1.3.3-17 base-files recommends no packages. base-files 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#755395: linux-image-3.14-0.bpo.1-amd64: Some filesystem modules fail to load with error Unknown symbol __test_set_page_writeback (err 0)
Package: src:linux Version: 3.14.12-1~bpo70+1 Severity: important Dear Maintainer, After upgrading to version 3.14.12-1~bpo70+1, some filesystem modules fail to load. Tried reinstalling the package, but the problem persists. Using modprobe on any of the modules ext4, reiserfs, jfs, ntfs or btrfs gives the error Unknown symbol in module, or unknown parameter (see dmesg) From dmesg: Unknown symbol __test_set_page_writeback (err 0) -- Package-specific info: ** Version: Linux version 3.14-0.bpo.1-amd64 (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.14.7-1~bpo70+1 (2014-06-21) ** Command line: BOOT_IMAGE=/vmlinuz-3.14-0.bpo.1-amd64 root=/dev/mapper/sysvg-root ** Not tainted ** Kernel log: [42052.778834] ext4: Unknown symbol __test_set_page_writeback (err 0) [162982.752350] reiserfs: Unknown symbol __test_set_page_writeback (err 0) [162982.756538] jfs: Unknown symbol __test_set_page_writeback (err 0) [162982.761808] ntfs: Unknown symbol __test_set_page_writeback (err 0) [162982.771709] btrfs: Unknown symbol __test_set_page_writeback (err 0) [162982.775307] fuse: Unknown symbol __test_set_page_writeback (err 0) ** Model information sys_vendor: System manufacturer product_name: P5E-VM DO product_version: System Version chassis_vendor: Chassis Manufacture chassis_version: Chassis Version bios_vendor: American Megatrends Inc. bios_version: 0902 board_vendor: ASUSTeK Computer INC. board_name: P5E-VM DO board_version: Rev 1.xx ** Loaded modules: nfsv3 rpcsec_gss_krb5 nfsv4 dns_resolver raid6_pq xor ufs qnx4 hfsplus hfs minix vfat msdos fat crc16 mbcache jbd2 vhost_net vhost macvtap macvlan tun xt_tcpudp xt_length xt_mark cls_u32 cls_fw sch_sfq sch_htb iptable_mangle ip_tables x_tables nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache sunrpc bridge stp llc ip_vs_wrr ip_vs_wlc ip_vs_sh ip_vs_sed ip_vs_rr ip_vs_nq ip_vs_lc ip_vs_lblcr ip_vs_lblc ip_vs_ftp nf_nat ip_vs_dh ip_vs nf_conntrack hwmon_vid vga16fb vgastate loop hid_generic usbhid hid iTCO_wdt iTCO_vendor_support ppdev coretemp kvm_intel kvm evdev serio_raw pcspkr firewire_ohci firewire_core crc_itu_t i2c_i801 i915 video tpm_infineon tpm_tis drm_kms_helper drm e1000 e1000e lpc_ich tpm i2c_algo_bit i2c_core mfd_core sg asus_atk0110 ata_generic pata_jmicron parport_pc parport ehci_pci ptp button pps_core uhci_hcd ehci_hcd shpchp usbcore usb_common processor thermal_sys raid10 dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio dm_mod xfs crc32c libcrc32c raid1 md_mod sd_mod crc_t10dif crct10dif_common ahci libahci libata scsi_mod ** Network interface configuration: auto lo eth3 eth3:1 iface lo inet loopback iface eth3 inet static address 10.0.0.100 netmask 255.255.255.0 gateway 10.0.0.1 iface eth3:1 inet static address 10.0.0.199 netmask 255.255.255.0 gateway 10.0.0.1 auto br0 iface br0 inet dhcp bridge_ports eth2 bridge_stp on bridge_fd 0 ** Network status: *** IP interfaces and addresses: 1: lo: LOOPBACK,UP,LOWER_UP mtu 65536 qdisc noqueue state UNKNOWN group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth3: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc htb state UP group default qlen 1000 link/ether 00:23:54:6d:85:59 brd ff:ff:ff:ff:ff:ff inet 10.0.0.100/24 brd 10.0.0.255 scope global eth3 valid_lft forever preferred_lft forever inet 10.0.0.199/24 brd 10.0.0.255 scope global secondary eth3:1 valid_lft forever preferred_lft forever inet6 fe80::223:54ff:fe6d:8559/64 scope link valid_lft forever preferred_lft forever 3: eth2: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast master br0 state UP group default qlen 1000 link/ether 00:0e:0c:da:6c:41 brd ff:ff:ff:ff:ff:ff 4: br0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state UP group default link/ether 00:0e:0c:da:6c:41 brd ff:ff:ff:ff:ff:ff inet6 fe80::20e:cff:feda:6c41/64 scope link valid_lft forever preferred_lft forever 8: vnet0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast master br0 state UNKNOWN group default qlen 500 link/ether fe:0c:29:b5:38:65 brd ff:ff:ff:ff:ff:ff inet6 fe80::fc0c:29ff:feb5:3865/64 scope link valid_lft forever preferred_lft forever 9: vnet1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast master br0 state UNKNOWN group default qlen 500 link/ether fe:54:00:99:75:76 brd ff:ff:ff:ff:ff:ff inet6 fe80::fc54:ff:fe99:7576/64 scope link valid_lft forever preferred_lft forever 10: vnet2: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast master br0 state UNKNOWN group default qlen 500 link/ether fe:0c:29:a9:7c:c7 brd ff:ff:ff:ff:ff:ff inet6 fe80::fc0c:29ff:fea9:7cc7/64 scope link valid_lft forever preferred_lft forever ***
Bug#755364: [Pkg-utopia-maintainers] Bug#755364: network-manager: Creates one additional bluetooth connection per resume
Am 19.07.2014 23:39, schrieb Julian Andres Klode: Package: network-manager Version: 0.9.10.0-1 Severity: normal After each resume an additional network connection for my Bluetooth PAN is created. Might be related to https://bugzilla.gnome.org/show_bug.cgi?id=732998 -- 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#748867: [Pkg-chromium-maint] Bug#748867: Bug#748867: Missing API keys, some features of chromium are disabled
Il 20/07/2014 11:32, Vincent Bernat ha scritto: Mike disabled the message in this version but didn't add the API keys. The version that Giuseppe is talking about did not hit the mirrors yet. I've not uploaded a new version (I'm still waiting Michael pushes his changes on git...) but I enabled The Google+ Api for the Chromium project and that message should disappear also in the version in sid. P.S. Michael, please, again, I wrote you the first email on May and I'm really upset by this... Please, PUSH YOUR CHANGES ON GIT! You are blocking me and other people to work on chromium. Cheers, Giuseppe. signature.asc Description: OpenPGP digital signature
Bug#755396: qtwebkit: New version is avalible
Source: qtwebkit Severity: normal Dear Maintainer, Please, consider packaging of newer version. Such old version causes problems with, for example, qupzilla - favicons are not displaying there. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754984: libpam-systemd 208-6 conflicts with sysvinit-core
* Michael Biebl bi...@debian.org [2014-07-17 17:25 +0200]: Am 17.07.2014 16:20, schrieb Elimar Riesebieter: [...] I don't see the intention? You should read the changelog then. Not understanding the intentions is not a justification for reopening a bug report which has been closed by its maintainer. It seems that the intention is to push systemd as the only init system. Why did you upload 208-6 _before_ systemd-shim was adjusted? sysvinit is broken by that injudicious action! Elimar -- Learned men are the cisterns of knowledge, not the fountainheads ;-) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755148: [Pkg-utopia-maintainers] Bug#755148: if inet6 is set to manual, then IPv4 is ignored, too
Am 18.07.2014 11:28, schrieb Harald Dunkel: Package: network-manager Version: 0.9.10.0-1 If I set auto eth0 iface eth0 inet6 manual # EOF in /etc/network/interfaces, then network-manager seems to ignore IPv4 on eth0, too. This is fatal. I would suggest to keep IPv4 and IPv6 seperate, and to introduce explicit network_manager methods for IPv4 and IPv6 in the interfaces file. Are you using managed=true mode in /etc/NetworkManager/NetworkManager.conf? -- 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#755039: [Pkg-utopia-maintainers] Bug#755039: network-manager: Wrong harcoded path to arping
forwarded 755039 https://bugzilla.gnome.org/show_bug.cgi?id=732997 thanks Am 18.07.2014 02:26, schrieb Stanley Schade Hi, I just downgraded to check that this does not happen with version 0.9.8.10-4. Also, note that arping is an optional package. So, I guess it should be listed in the dependencies... FWIW I attached a patch that sets the hardcoded path of arping correctly. Thanks for the patch, but unfortunately, there is not really a correct path for the arping binary. Instead of hardcoding it for Debian, I think it should be configurable and filed a corresponding bug upstream. Also keep in mind, that we do have two arping implementations in Debian: iputils-arping (/usr/bin/arping) and iputils (/usr/sbin/arping). I'm leaning to support the former, i.e. set the path to /usr/bin/arping and add a suggests on iputils-arping. -- 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#755284: libjbig0 priority should be at least optional
I'd be happy to have a co-maintainer; my workload has been much heavier over the last year, and so I haven't sat down to do tasks that I really should do - after all, I use it on my own systems, so I should be willing to contribute too. Cheers, Michael On 20 Jul 2014 01:52, Didier Raboud o...@debian.org wrote: Source: libjbig0 Version: 2.0-2.1 Severity: important Hi, according to https://ftp-master.debian.org/override-disparity.gz , libjbig0 is depended upon by 11 packages of priority 'optional'. It should therefore be at least of priority 'optional'. Markus, by the way, do you need assistance with the maintenance of libjbigkit? A new upstream version should be uploaded since April and Ubuntu has prepared many fixes which should really be included in the Debian package. I'd be happy to help with the maintenance either as co-maintainer (that just needs your agreement) or single maintainer (you'd need to properly orphan the package, see [0]). Thanks in advance, OdyX [0] https://www.debian.org/doc/manuals/developers-reference/pkgs.html#orphaning -- System Information: Debian Release: jessie/sid APT prefers testing-proposed-updates APT policy: (500, 'testing-proposed-updates'), (500, 'proposed-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.15-rc8-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash
Bug#755286: Bug#755285: marked as done (general: Black screen on resume after suspend)
On 07/19/2014 08:49 PM, Abou Al Montacir wrote: Control: reopen -1 On Sat, 2014-07-19 at 17:03 +, Debian Bug Tracking System wrote: ... Missing information, dupe. Kind regards, Andrei Hi Andrei, I don't think that missing information is enough argument to close a bug. Hi AL Nik, Can you please provide more information about your issue. As the screen is dead I understand that you may have issue to provide the required information depending on your computer skills. Please find below some hints, and maybe Andrei can provide more hints instead of closing this bug again ;) If you have access to another computer, please consider logging into the first one after resume (you need to have sshd installed or any other deamon for remote access) then gain root access and provide output of dmesg and other log files in /var/log like /var/log/pm-powersave.log. I'm not a specialist of such issues, but don't like to have user's request closed abruptly. Cheers, Abou Al Montacir Hi Abou Al Montacir, I tried this experiment: Installed sshd and connected from another computer - it works. But after the lid closed and opened, I cannot connect. The system must be dead, although the fans blows and the power led is on. Further after restart I found that nothing was written in neither dmesg nor pm-powersave.log after the lid is closed and then opened. Best, Aleksandar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748867: [Pkg-chromium-maint] Bug#748867: Bug#748867: Missing API keys, some features of chromium are disabled
❦ 20 juillet 2014 11:56 +0200, Giuseppe Iuculano giuse...@iuculano.it : Mike disabled the message in this version but didn't add the API keys. The version that Giuseppe is talking about did not hit the mirrors yet. I've not uploaded a new version (I'm still waiting Michael pushes his changes on git...) but I enabled The Google+ Api for the Chromium project and that message should disappear also in the version in sid. I was mostly concerned by the ability to use Google Sync. I have no problem with Chromium 35 but from reading this bug report, I thought that it wouldn't work anymore with Chromium 36 (and another bug report suggests that it is not possible to reinstall Chromium 35 after that, so I didn't test with Chromium 36 from experimental). But maybe I am worried for nothing? I can also just backup my profile (just ~/.config/chromium?) and test Chromium 36. -- Make sure input cannot violate the limits of the program. - The Elements of Programming Style (Kernighan Plauger) signature.asc Description: PGP signature
Bug#755106: same error with pypy
Hello, i see the same error when i try to create a virtualenv with pypy: $ virtualenv -p /usr/bin/pypy pypyvenv Running virtualenv with interpreter /usr/bin/pypy New pypy executable in pypyvenv/bin/pypy Installing setuptools, pip... Complete output from command /home/rm/src/pypyvenv/bin/pypy -c import sys, pip; sys...d\] + sys.argv[1:])) setuptools pip: Traceback (most recent call last): File app_main.py, line 75, in run_toplevel File app_main.py, line 581, in run_it File string, line 1, in module ZipImportError: cannot import name 'CertificateError' ...Installing setuptools, pip...done. Traceback (most recent call last): File app_main.py, line 75, in run_toplevel File /usr/lib/python3/dist-packages/virtualenv.py, line 2378, in module main() File /usr/lib/python3/dist-packages/virtualenv.py, line 830, in main symlink=options.symlink) File /usr/lib/python3/dist-packages/virtualenv.py, line 1032, in create_environment install_wheel(to_install, py_executable, search_dirs) File /usr/lib/python3/dist-packages/virtualenv.py, line 975, in install_wheel 'PIP_NO_INDEX': '1' File /usr/lib/python3/dist-packages/virtualenv.py, line 917, in call_subprocess % (cmd_desc, proc.returncode)) OSError: Command /home/rm/src/pypyvenv/bin/pypy -c import sys, pip; sys...d\] + sys.argv[1:])) setuptools pip failed with error code 1 thanks, riccardo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755397: glibc FTBFS on alpha: tst-eintr3 sometimes fails.
Source: glibc
Version: 2.19-7
Severity: important
User: debian-al...@lists.debian.org
Usertags: alpha
Justification: Fails to build from source but built in the past.
The test tst-eintr3 sometimes fails in the build of glibc on alpha
and has done so twice in a row in attempting to build 2.19-7.
It's an intermittant fault that appears to only occur on a
multiprocessor SMP system (which the buildd imago is). Running the
test manually 40 or so times never failed when running a UP kernel.
To make testing faster I have used upstream glibc source on the 2.19
branch configuring with --enable-hardcoded-path-in-tests and running
tst-eintr3 with the --direct option. It occasionally segfaults.
Getting a core dump and analysing with gdb gives the following:
Core was generated by `/home/mjc/toolchain/glibc-build/nptl/tst-eintr3
--direct'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 start_thread (arg=0x2000121f1f0) at pthread_create.c:243
243 __resp = pd-res;
(gdb) bt full
#0 start_thread (arg=0x2000121f1f0) at pthread_create.c:243
pd = 0x2000121f1f0
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0 repeats 17 times},
mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x203da00
start_thread,
0x2000121f1f0}, data = {prev = 0x0, cleanup = 0x0, canceltype =
252416}}}
not_first_call = optimized out
robust = optimized out
pagesize_m1 = optimized out
sp = optimized out
freesize = optimized out
__PRETTY_FUNCTION__ = start_thread
#1 0x02177d24 in thread_start ()
at ../ports/sysdeps/unix/sysv/linux/alpha/clone.S:111
No locals.
(gdb) disass /m
Dump of assembler code for function start_thread:
232 {
0x0203da00 +0: ldahgp,3(t12)
0x0203da04 +4: lda gp,-14800(gp)
0x0203da08 +8: lda sp,-240(sp)
0x0203da14 +20:stq fp,40(sp)
0x0203da18 +24:mov sp,fp
0x0203da24 +36:stq s0,8(sp)
0x0203da28 +40:stq ra,0(sp)
0x0203da30 +48:stq s1,16(sp)
0x0203da38 +56:stq s2,24(sp)
0x0203da3c +60:stq s3,32(sp)
0x0203da40 +64:stq a0,224(fp)
233 struct pthread *pd = (struct pthread *) arg;
234
235 #if HP_TIMING_AVAIL
236 /* Remember the time when the thread was started. */
237 hp_timing_t now;
238 HP_TIMING_NOW (now);
239 THREAD_SETMEM (pd, cpuclock_offset, now);
240 #endif
241
242 /* Initialize resolver state pointer. */
243 __resp = pd-res;
0x0203da0c +12:rduniq
0x0203da10 +16:ldq t0,-32656(gp)
0x0203da20 +32:addqv0,t0,t0
0x0203da2c +44:lda t1,1208(a0)
0x0203da34 +52:mov v0,s0
= 0x0203da44 +68:stq t1,0(t0)
The __resp variable appears to be a thread local variable being
accessed (well, written) by the initial exec TLS model. The rduniq
PALcall should put the thread pointer (from the PCB) into register
v0. Now let's check the address being written to at the point of
the segfault.
(gdb) print /x $t0
$1 = 0x18
That's definitely not a valid memory location since the first page of
memory starting at location 0 should be inaccessible. Checking the
thread pointer:
(gdb) print /x $v0
$2 = 0x0
Ouch! That looks like the thread pointer in the PCB has not been
initialised.
Running tst-eintr3 under gdb and setting a break point on line 243
reveals that, in general, the rduniq PALcall does return a valid
memory address (and presumably correctly the thread pointer), but,
occassionaly on an SMP system, it can return 0.
This is as far as I have got with debugging. Presumably there is a
wruniq PALcode call somewhere that sets up the thread pointer in the
PCB and that might be the next place to investigate what is going
on.
Cheers
Michael.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755398: [INTL:da] Danish translation of linuxinfo
Package: linuxinfo Severity: wishlist Tags: l10n patch Please include the attached Danish linuxinfo translation. joe@pc:~/over/debianp/linuxinfo$ msgfmt --statistics -c -v -o /dev/null da.po da.po: 21 oversatte tekster. bye Joe da.po.tar.gz Description: application/gzip
Bug#755399: libpcre3: i386 needs update to match amd64
Source: libpcre3 Version: 1:8.35-2 Severity: normal Dear Maintainer, I'm blocked from updating my Sid install because of the following: libpcre3:i386 breaks libpcre3 (!= 1:8.31-5) As is probably common on 64-bit systems, I have some packages that need 32-bit. The problem is libpcre3:amd64 wants to update to 1:8.35-2, but only version 1.8.31-5 is available for i386. I'd rather not have to untangle this if i386 can be easily updated and will be soon. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755400: [INTL:da] Danish translation of linux
Package: linux Severity: wishlist Tags: l10n patch Please include the attached Danish linux translation. joe@pc:~/over/debianp/linux$ msgfmt --statistics -c -v -o /dev/null da.po da.po: 11 oversatte tekster. bye Joe da.po.tar.gz Description: application/gzip
Bug#755022: [claws-mail-spam-report] likely useless to report to Debian because of the use of http instead of https
Control: tags -1 fixed-upstream wheezy jessie sid Hi Manolo, On Wed, Jul 16, 2014 at 11:58:48PM +0200, Manolo Díaz wrote: Package: claws-mail-spam-report Version: 3.10.1-2 Severity: important Dear Developer/Maintainer, Judging by the trace I think that the spam report fails. Yep, I've comitted a patch upstream¹, but will take some time to have it fixed on all releases. Thanks for reporting, ¹http://git.claws-mail.org/?p=claws.git;a=commit;h=d0ad5f6a -- Ricardo Mones ~ bash: ./signature: No such file or directory /bin/bash signature.asc Description: Digital signature
Bug#755402: network-manager: All ppp connections (dsl or gsm) fail
Package: network-manager Version: 0.9.10.0-1 Severity: important Dear Maintainer, I noticed the problem after last update, previous version of NM was not affected ineffective)? For dsl connection I received failed message when using the plasma plugin in kde, when the connection is invoked via pon (configured with pppoeconfig) it works regularly and create a connection to ppp0 (a new connection is created at every pon due to parameters change). I tried with nmcli, for example: $ LANG=C nmcli con NAME UUID TYPE DEVICE N900 d8281e2e-6754-4aef-a5cd-4982653d24a7 802-3-ethernet -- Wind - Non-business c1635f50-887d-444b-9b61-8b77d8839292 gsm -- PuruPuru Network 8891490a-e907-47f8-b2c3-915bf4443010 bluetooth -- Alice6202b767-f969-45e8-9f8c-46c3773fe502 pppoe -- ppp0 b0d72434-e4c7-4d69-aa1a-1f48a7bdc154 generic ppp0 Alice IPv6 6441fa55-ca59-47b5-a28b-0fc2e6ac232a pppoe -- Modembd214c10-059a-42e2-8e70-c0bd414ef338 802-3-ethernet eth1 ppp0 889de5b2-defd-4a90-af94-b25958dfb07f generic -- $ LANG=C nmcli con up 6441fa55-ca59-47b5-a28b-0fc2e6ac232a Error: Connection activation failed. For dsl the message is a generic activation failed, I think you'll need more debugging. For gsm connection it seems NM can't handle the modem, even if it's correctly seen: $ LANG=C nmcli dev DEVICE TYPE STATECONNECTION eth1 ethernet connectedModem ppp0 unknown connectedppp0 usb0 ethernet unavailable -- ttyACM0 gsm unavailable -- eth0 ethernet unmanaged-- lo loopback unmanaged-- usbpn0 unknown unmanaged-- I thought it was a modem manager fault, indeed it seems to work correctly: $ mmcli -L Found 1 modems: /org/freedesktop/ModemManager1/Modem/1 [Nokia] Nokia N900 $ mmcli -m /org/freedesktop/ModemManager1/Modem/0 --3gpp-scan Found 1 networks: 22288 - I WIND (umts, current) In nmcli the device seems to be unavailable, but it works when using wvdial, when trying to connect I receive: $ LANG=C nmcli con up c1635f50-887d-444b-9b61-8b77d8839292 Error: Connection activation failed: Connection 'Wind - Non-business' is not available on the device ttyACM0 at this time. If needed I can give more details -- System Information: Debian Release: jessie/sid Architecture: i386 (i686) Kernel: Linux 3.14-1-686-pae (SMP w/1 CPU core) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages network-manager depends on: ii adduser3.113+nmu3 ii dbus 1.8.6-1 ii init-system-helpers1.19 ii isc-dhcp-client4.3.0+dfsg-1 ii libc6 2.19-7 ii libdbus-1-31.8.6-1 ii libdbus-glib-1-2 0.102-1 ii libgcrypt111.5.3-4 ii libglib2.0-0 2.40.0-3 ii libgnutls-deb0-28 3.2.15-3 ii libgudev-1.0-0 204-14 ii libmm-glib01.2.0-1 ii libndp01.3-1 ii libnewt0.520.52.17-1 ii libnl-3-2003.2.24-2 ii libnl-genl-3-200 3.2.24-2 ii libnl-route-3-200 3.2.24-2 ii libnm-glib40.9.10.0-1 ii libnm-util20.9.10.0-1 ii libpam-systemd 204-14 ii libpolkit-gobject-1-0 0.105-6 ii libreadline6 6.3-6 ii libsoup2.4-1 2.46.0-2 ii libsystemd-daemon0 204-14 ii libsystemd-login0 204-14 ii libuuid1 2.20.1-5.8 ii lsb-base 4.1+Debian13 ii policykit-10.105-6 ii udev 204-14 ii wpasupplicant 1.1-1 Versions of packages network-manager recommends: ii crda 1.1.2-1 ii dnsmasq-base 2.71-1 ii iptables 1.4.21-2 ii modemmanager 1.2.0-1 ii ppp 2.4.6-2 Versions of packages network-manager suggests: pn avahi-autoipd none -- Configuration Files: /etc/NetworkManager/NetworkManager.conf changed: [main] plugins=ifupdown,keyfile no-auto-default=00:11:2f:3f:eb:d2,62:03:B1:BD:67:9F,62:71:D0:AF:1F:7C,F6:71:A4:36:63:03,EA:A9:30:B3:08:D3, [ifupdown] managed=false -- 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#755401: update man page and add --help
Package: chromium Version: 36.0.1985.103-1 man chromium says NAME chromium-browser - the web browser from Google SYNOPSIS chromium-browser [OPTION] [PATH|URL] those two lines are now wrong. It is not chromium-browser anymore. DESCRIPTION See the Google Chrome help center for help on using the browser. http://www.google.com/support/chrome/ This manpage only describes invocation, environment, and arguments. standard input:113: warning [p 2, 7.8i]: cannot adjust line We note this error. However doing $ chromium --help reveals this not seen at all on the man page: chromium [-h|--help] [-g|--debug] [--temp-profile] [options] [URL] -g or --debug Start within /usr/bin/gdb -h or --helpThis help screen --temp-profile Start with a new and temporary profile -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755403: ITA: libiksemel -- C library for the Jabber IM platform
Source: libiksemel Severity: normal I'm going to take over this unmaintained package and bring it to shape. -- Regards, Dmitry Smirnov GPG key : 4096R/53968D1B signature.asc Description: This is a digitally signed message part.
Bug#754299: dnsmasq: Reloading dnsmasq with systctl results in stop
I work on up-to-date Testing. Just wanted to recheck just in case, and here it goes again! dnsmasq.service - A lightweight DHCP and caching DNS server Loaded: loaded (/lib/systemd/system/dnsmasq.service; disabled) Drop-In: /run/systemd/generator/dnsmasq.service.d └─50-dnsmasq-$named.conf, 50-insserv.conf-$named.conf Active: inactive (dead) since Sun 2014-07-20 15:21:58 MSK; 3s ago Process: 1771 ExecStop=/etc/init.d/dnsmasq systemd-stop-resolvconf (code=exited, status=0/SUCCESS) Process: 1768 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS) Main PID: 1644 (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/dnsmasq.service июля 20 10:14:35 hostname dnsmasq-dhcp[1644]: DHCPREQUEST(lan0) 10.42.1.75 8c:3a:e3:5d:af:f3 июля 20 10:14:35 hostname dnsmasq-dhcp[1644]: DHCPACK(lan0) 10.42.1.75 8c:3a:e3:5d:af:f3 android-89ce4...7fbf июля 20 13:49:33 hostname dnsmasq-dhcp[1644]: DHCPDISCOVER(lan0) 10.42.1.66 30:85:a9:18:52:06 июля 20 13:49:33 hostname dnsmasq-dhcp[1644]: DHCPOFFER(lan0) 10.42.1.66 30:85:a9:18:52:06 июля 20 13:49:33 hostname dnsmasq-dhcp[1644]: DHCPREQUEST(lan0) 10.42.1.66 30:85:a9:18:52:06 июля 20 13:49:33 hostname dnsmasq-dhcp[1644]: DHCPACK(lan0) 10.42.1.66 30:85:a9:18:52:06 mindflash4 июля 20 15:21:58 hostname systemd[1]: Reloading A lightweight DHCP and caching DNS server. июля 20 15:21:58 hostname dnsmasq[1644]: read /etc/dnsmasq-custom.hosts - 3 addresses июля 20 15:21:58 hostname dnsmasq[1644]: exiting on receipt of SIGTERM июля 20 15:21:58 hostname systemd[1]: Reloaded A lightweight DHCP and caching DNS server. I've checked reloading dnsmasq after some time of operation and upgrades to the system: The following NEW packages will be installed: libupower-glib2 The following packages will be upgraded: acpid alsa-base alsa-utils cups cups-bsd cups-client cups-common cups-core-drivers cups-daemon cups-ppdc cups-server-common e2fslibs e2fsprogs isc-dhcp-client isc-dhcp-common kmod libaqbanking34 libaqbanking34-plugins libaqebics0 libaqhbci22 libaqofxconnect7 libatk-bridge2.0-0 libcomerr2 libcups2 libcupscgi1 libcupsimage2 libcupsmime1 libcupsppdc1 libdate-manip-perl libegl1-mesa libegl1-mesa-drivers libeot0 libgbm1 libgc1c2 libgdbm3 libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa libgnutls-deb0-28 libgnutls-openssl27 libgssdp-1.0-3 libhunspell-1.3-0 libhyphen0 libice6 libjavascriptcoregtk-1.0-0 libjavascriptcoregtk-3.0-0 libjson-glib-1.0-0 libjson-glib-1.0-common libkmod2 libmpg123-0 libnss3 libnss3-1d libopenvg1-mesa libpciaccess0 libpixman-1-0 libprocps3 libpython-stdlib libquvi-scripts librtmp1 libsasl2-2 libsasl2-modules libsasl2-modules-db libsm6 libss2 liburi-perl libwayland-egl1-mesa libwebkitgtk-1.0-0 libwebkitgtk-1.0-common libwebkitgtk-3.0-0 libwebkitgtk-3.0-common libx264-142 libxatracker2 libxaw7 libxfont1 libxft2 libxml-parser-perl libxml2 libxmlsec1 libxmlsec1-gcrypt libxmlsec1-gnutls libxpm4 module-init-tools mpv openjdk-6-jre openjdk-6-jre-headless openjdk-6-jre-lib printer-driver-all procps python python-minimal upower x11-apps x11-utils x11-xserver-utils xauth xbacklight xcursor-themes xfonts-utils It seems nothing is relevant except isc-dhcp packages. I will try to just send HUP directly after some time to see what happens if I exclude systemd from the reload process. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755404: goplay: do not start
Package: goplay Version: 0.5-1.1 Severity: serious Goplay do not start, the following error is printed: goplay: error while loading shared libraries: libept.so.1.0.5.4.12: cannot open shared object file: No such file or directory --- System information. --- Architecture: amd64 Kernel: Linux 3.14-1-amd64 -- Best wishes, Dmitry Smirnov GPG key : 4096R/53968D1B signature.asc Description: This is a digitally signed message part.
Bug#755405: [lintian] Please add statistic about speed of lintian on lintian.debian.org
Package: lintian Version: 2.5.25 Severity: important Could be possible to track day to day change of Rescheduled groups: 19455 (-53), both absolute and relative change ? It will help to see long term speed variation of lintian. Could be possible to get statistic of lintian run publically available ? Bastien -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755022: [claws-mail-spam-report] likely useless to report to Debian because of the use of http instead of https
On Sunday, Jul 20 2014 at 13:22 (UTC+2), Ricardo Mones wrote: Control: tags -1 fixed-upstream wheezy jessie sid Hi Manolo, On Wed, Jul 16, 2014 at 11:58:48PM +0200, Manolo Díaz wrote: Package: claws-mail-spam-report Version: 3.10.1-2 Severity: important Dear Developer/Maintainer, Judging by the trace I think that the spam report fails. Yep, I've comitted a patch upstream¹, but will take some time to have it fixed on all releases. Thanks for reporting, ¹http://git.claws-mail.org/?p=claws.git;a=commit;h=d0ad5f6a Nothing to worry about. Meanwhile I'm using the Claws-mail actions tool for that and works perfectly. Best Regards, -- Manolo Díaz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755332: libdevel-nytprof-perl: FTBFS: Tests failures
On Sat, 19 Jul 2014 20:44:08 +0200, David Suárez wrote: Source: libdevel-nytprof-perl Version: 5.06+dfsg-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140718 qa-ftbfs Justification: FTBFS on amd64 During a rebuild of all packages in sid, your package failed to build on amd64. Additionally to https://github.com/timbunce/devel-nytprof/issues/34 there's also https://rt.cpan.org/Public/Bug/Display.html?id=50524 (Sub::Name). 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: The Beatles: Ob-La-Di Ob-La-Da signature.asc Description: Digital Signature
Bug#755399: libpcre3: i386 needs update to match amd64
Control: reassign -1 pcre3 Control: severity -1 serious Control: merge 751828 -1 On Sun, Jul 20, 2014 at 06:35:15AM -0400, Jeff Nowakowski wrote: Source: libpcre3 Version: 1:8.35-2 Severity: normal Dear Maintainer, I'm blocked from updating my Sid install because of the following: libpcre3:i386 breaks libpcre3 (!= 1:8.31-5) As is probably common on 64-bit systems, I have some packages that need 32-bit. The problem is libpcre3:amd64 wants to update to 1:8.35-2, but only version 1.8.31-5 is available for i386. I'd rather not have to untangle this if i386 can be easily updated and will be soon. This class of problem is more or less unavoidable in unstable from time to time; testing will largely prevent multiarch skew of this nature, so if this is a frequent problem for you then you should consider using testing instead. (Fixing this systemically in unstable would essentially entail turning it into testing.) That said, in this case, builds on all systems other than the maintainer's own amd64 upload failed, according to https://buildd.debian.org/status/package.php?p=pcre3suite=sid. This appears to be #751828, so merging. Cheers, -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754769: closed by Michael Gilbert mgilb...@debian.org (Re: [Pkg-chromium-maint] Bug#754769: don't trash your profile by upgrading to Debian chromium 36 yet!)
Well even with --temp-profile there's no way to sync profiles anymore without API keys. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732698: gemdropx: Fails to start (Failure loading sampleinfo)
Hello again all. I'm not quite sure what changed, but I no longer get the error message when starting gemdropx. Since gemdropx hasn't been upgraded I wonder whether it could be libsdl-mixer1.2 version 1.2.12-11+b1 which has resolved this in some way. Could someone check whether they are still able to reproduce this one? So the game is running again. (Though it is running awfully fast, I don't know if this is intentional or another bug) Hi, (Please keep me in CC if you want more input from me). 2014/1/5 Christian T. Steigies c...@debian.org: Manuel, maybe you as the new sdl-mixer maintainer have an idea sdl-mixer1.2 can not play xm audio files anymore? Perhaps this is an SDL bug? Or is it a feature and XM files should be converted? Christian I added modplug support about a year ago. This was motivated by this change upstream for 2.0.0 version: 2.0.0: Sam Lantinga - Sun Jun 9 14:45:30 PDT 2013 * Made libmodplug the default MOD player as it is now in the public domain The same support existed in 1.2 since 2009 although disabled, so I thought that it would be useful to have modplug enabled in 1.2 if it was the preferred lib for SDL2_mixer: 1.2.12: [...] Jon Atkins - Sat Nov 14 13:00:18 PST 2009 * Added support for libmodplug (disabled by default) Also because modplug seems more popular by a far margin: http://qa.debian.org/popcon-graph.php?packages=libmikmod2+libmodplug1show_installed=onwant_legend=onwant_ticks=onfrom_date=to_date=hlght_date=date_fmt=%25Y-%25mbeenhere=1 So I think that this failure might be because the XM files are now interpreted by modplug which cannot read the file. It would be useful if you install mikmod and modplug-tools and try to verify if they both can play the file, or have some problem, etc. If this is the case, I think that it would be useful to either fix the XM files (if it's a problem with the format of the file itself, if the most popular interpreter has problems) or report the bug to ModPlug (maybe it's more popular but the support for XM is incomplete). Other changes might have caused this, e.g. overflow protection now enabled for sdl-mixer1.2 getting in the way. On Sun, Dec 22, 2013 at 02:09:31PM -0800, Bill Kendrick wrote: Sadly, I do not. We may need to convert or replace the XM file. I just tried on my Kubuntu 13.10 and got the same error. -bill! On Sat, Dec 21, 2013 at 05:54:13PM +0100, Christian T. Steigies wrote: Hi, thanks for the report. On Fri, Dec 20, 2013 at 02:00:16PM +0100, Hans Joachim Desserud wrote: Package: gemdropx Version: 0.9-6 Severity: important Dear Maintainer, When I attempt to start gemdropx, I only get the following error message: $ gemdropx Couldn't load /usr/share/games/gemdropx/sounds/2force.xm: Failure loading sampleinfo Just in case, I double-checked with the frozen-bubble package which also use libsdl-mixer1.2 for sound and that works fine. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.11-2-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 gemdropx depends on: ii libc62.17-97 ii libsdl-mixer1.2 1.2.12-9 ii libsdl1.2debian 1.2.15-8 gemdropx recommends no packages. gemdropx suggests no packages. -- no debconf information -- mvh / best regards Hans Joachim http://desserud.org Strange, I am pretty sure that gemdropx was working when I uploaded the package, two years ago... I get the same message now, I can play the file with timidity, but gemdropx can not play it, even after rebuilding it for unstable. Since gemdropx has not changed, I suspect the problem is with sdl-mixer. Bill, do you have an idea what could be wrong? Christian Cheers. -- Manuel A. Fernandez Montecelo manuel.montez...@gmail.com -- mvh / best regards Hans Joachim http://desserud.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755406: RFP: screencloud -- easy to use screenshot tool
Package: wnpp Severity: wishlist * Package name: screencloud Version : 1.1.6 Upstream Author : Olav Sortland Thoresen olav.s...@gmail.com * URL : http://www.screencloud.net (online service) http://www.github.com/olav-st/screencloud (source) * License : GPL2 or any later version Programming Lang: C++ / Qt Description : easy to use screenshot tool Screencloud allows taking a screenshot of the full screen, a window or a manually selected screen region. It offers various advanced settings like adding a delay before taking the screenshot, hotkeys, and optionally sharing the screenshot through (S)FTP, the screencloud online service or similar services. Relevant information (similar packages, reason for RFP etc.): Shutter offers the same features and quite a bit more. I'm a little concerned about the future of shutter though, as it still depends on Gtk2 and other gnome2 libraries and there's not much activity in the usptream bzr repository. At the same time, screencloud still depends on Qt4. There's some activity in the upstream git repo though, and I imagine porting from Qt4 to Qt5 is easier than porting from Gtk2 to Gtk3 and libgnome2-* to whatever the new libraries are called. While screencloud is less feature-rich than shutter, it has a nicer user interface and is less overwhelming for the average user. I prefer it over shutter and would therefore love to see it in Debian. Caveats: - Screencloud apparently downloads a list of sharing plugins and offers them for installation on first start. This is almost certainly not ideal for packaging in Debian, it probably has security implications as well. This functionality should probably be patched out of the eventual Debian package and desired plugins should be included with the package. - Likewise, there's a check for updates in the preferences dialog and an automatic update check. It should probably be patched out of the package, too. - Since the tool was created by the owner of the screencloud online service, it advertises creating an account there to share screenshots. While this seems to be completely optional and the tool is open source and very useful even without having an account, it may or may not conflict with some Debian policies. - There might be more caveats related to the proprietary open source nature of this software. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755407: current error messages seen upon a startup of pristine installation of chromium
Package: chromium Version: 36.0.1985.103-1 Here are the current error messages seen upon a startup of pristine installation of chromium: # su - nobody -c 'HOME=/tmp/p chromium' ATTENTION: default value of option force_s3tc_enable overridden by environment. [19221:19221:0720/201152:ERROR:command_buffer_proxy_impl.cc(152)] Could not send GpuCommandBufferMsg_Initialize. [19221:19221:0720/201152:ERROR:webgraphicscontext3d_command_buffer_impl.cc(386)] CommandBufferProxy::Initialize failed. [19221:19221:0720/201152:ERROR:webgraphicscontext3d_command_buffer_impl.cc(405)] Failed to initialize command buffer. ATTENTION: default value of option force_s3tc_enable overridden by environment. [19221:19221:0720/201152:ERROR:command_buffer_proxy_impl.cc(152)] Could not send GpuCommandBufferMsg_Initialize. [19221:19221:0720/201152:ERROR:webgraphicscontext3d_command_buffer_impl.cc(386)] CommandBufferProxy::Initialize failed. [19221:19221:0720/201152:ERROR:webgraphicscontext3d_command_buffer_impl.cc(405)] Failed to initialize command buffer. [26:33:0720/201152:ERROR:command_buffer_proxy_impl.cc(152)] Could not send GpuCommandBufferMsg_Initialize. [24:30:0720/201152:ERROR:command_buffer_proxy_impl.cc(152)] Could not send GpuCommandBufferMsg_Initialize. [26:33:0720/201152:ERROR:webgraphicscontext3d_command_buffer_impl.cc(386)] CommandBufferProxy::Initialize failed. [24:30:0720/201152:ERROR:webgraphicscontext3d_command_buffer_impl.cc(386)] CommandBufferProxy::Initialize failed. [26:33:0720/201152:ERROR:webgraphicscontext3d_command_buffer_impl.cc(405)] Failed to initialize command buffer. [24:30:0720/201152:ERROR:webgraphicscontext3d_command_buffer_impl.cc(405)] Failed to initialize command buffer. ATTENTION: default value of option force_s3tc_enable overridden by environment. [19221:19221:0720/201152:ERROR:command_buffer_proxy_impl.cc(152)] Could not send GpuCommandBufferMsg_Initialize. [19221:19221:0720/201152:ERROR:webgraphicscontext3d_command_buffer_impl.cc(386)] CommandBufferProxy::Initialize failed. [19221:19221:0720/201152:ERROR:webgraphicscontext3d_command_buffer_impl.cc(405)] Failed to initialize command buffer. [24:30:0720/201152:ERROR:command_buffer_proxy_impl.cc(152)] Could not send GpuCommandBufferMsg_Initialize. [24:30:0720/201152:ERROR:webgraphicscontext3d_command_buffer_impl.cc(386)] CommandBufferProxy::Initialize failed. [24:30:0720/201152:ERROR:webgraphicscontext3d_command_buffer_impl.cc(405)] Failed to initialize command buffer. [26:33:0720/201152:ERROR:webgraphicscontext3d_command_buffer_impl.cc(446)] Failed to initialize GLES2Implementation. [19221:19251:0720/201205:ERROR:raw_channel_posix.cc(139)] recvmsg: Connection reset by peer [19221:19251:0720/201205:ERROR:channel.cc(297)] RawChannel fatal error (type 1) [19221:19251:0720/201205:ERROR:raw_channel_posix.cc(139)] recvmsg: Connection reset by peer [19221:19251:0720/201205:ERROR:channel.cc(297)] RawChannel fatal error (type 1) [19221:19251:0720/201207:ERROR:raw_channel_posix.cc(139)] recvmsg: Connection reset by peer [19221:19251:0720/201207:ERROR:channel.cc(297)] RawChannel fatal error (type 1) [19221:19251:0720/201210:ERROR:raw_channel_posix.cc(139)] recvmsg: Connection reset by peer [19221:19251:0720/201210:ERROR:channel.cc(297)] RawChannel fatal error (type 1) [19221:19251:0720/201212:ERROR:raw_channel_posix.cc(139)] recvmsg: Connection reset by peer [19221:19251:0720/201212:ERROR:channel.cc(297)] RawChannel fatal error (type 1) [19221:19251:0720/201213:ERROR:raw_channel_posix.cc(139)] recvmsg: Connection reset by peer [19221:19251:0720/201213:ERROR:channel.cc(297)] RawChannel fatal error (type 1) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627954: debdelta does not apply deltas on files on which localepurge has been used.
Hi Shirish, hi Andrea, shirish शिरीष wrote in 2011: Debdelta does not work on packages on which localepurge has already been applied. For instance see :- Error: applying of delta for binutils failed: : localepurge removed 85 files. (non retriable) Error: applying of delta for cups failed: : localepurge removed 26 files. (non retriable) I'd also be very happy to see that feature being implemented. However as far as I can see, this is probably impossible, since debdelta aims to produce bitwise identical .debs (i.e. with same checksum). This is impossible if data which the diff is against is missing. I suspect that debdelta already does the following: If the .deb is still around in /var/cache/apt/archives/, use that instead of gathering stuff from the installed files. If not, that probably would be a way to mitigate this issue. P.S. to Andrea: Thanks a lot for debdelta. It's quite slow, but it's worth real money if you are travelling and only have volume based prepaid internet access. So please keep up that good service and thanks again! Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#582126: #582126 - nautilus: Using xrandr, desktop background is tiled on external display
Hey Emmanuel, this is an old bug. Could you please still reproduce this issue with newer nautilus version like 3.4.2-1+build1 or 3.8.2-3 ? thanks regards Pedro
Bug#755328: libgraph-writer-graphviz-perl: FTBFS: Tests failures
Control: tag -1 + confirmed
On Sat, 19 Jul 2014 20:44:20 +0200, David Suárez wrote:
Source: libgraph-writer-graphviz-perl
Version: 0.11-1nmu1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140718 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
make[1]: Entering directory '/«PKGBUILDDIR»'
PERL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -e
test_harness(0, 'inc', 'blib/lib', 'blib/arch') t/*.t
t/0.use.t . ok
# Failed test at t/1.simple.t line 23.
# Looks like you failed 1 test of 1.
t/1.simple.t ..
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/1 subtests
This is similar to #711446, except that the output has changed again:
#v+
t/1.simple.t .. $VAR1 = 'digraph test {
graph [ratio=fill];
node [label=\\N, color=black];
edge [color=black];
graph [bb=0,0,290,52];
Bob [label=Bob, pos=27,26, width=0.75, height=0.50];
Dr [label=Dr, pos=99,26, width=0.75, height=0.50];
Alice [label=Alice, pos=174,26, width=0.83, height=0.50];
Crude [label=Crude, pos=256,26, width=0.94, height=0.50];
}
';
$VAR2 = 'digraph test {
graph [bb=0,0,312.65,36,
ratio=fill
];
node [color=black,
label=\\N
];
edge [color=black];
Crude[height=0.5,
label=Crude,
pos=39.646,18,
width=1.1013];
Bob [height=0.5,
label=Bob,
pos=125.65,18,
width=0.79437];
Alice[height=0.5,
label=Alice,
pos=206.65,18,
width=0.95686];
Dr [height=0.5,
label=Dr,
pos=285.65,18,
width=0.75];
}
';
$VAR1 = 'digraphAlice [label=Alice, pos=0,0, width=0.0, height=0.0];
Bob [label=Bob, pos=0,0, width=0.0, height=0.0];
Crude [label=Crude, pos=0,0, width=0.0, height=0.0];
Dr [label=Dr, pos=0,0, width=0.0, height=0.0];
edge [color=black];
graph [bb=0,0,0,0];
graph [ratio=fill];
node [label=\\N, color=black];
test {}
';
$VAR2 = 'digraphlabel=\\N
label=Alice,
label=Bob,
label=Crude,
label=Dr,
pos=0.0,0,
pos=0.0,0,
pos=0.0,0,
pos=0.0,0,
ratio=fill
width=0.0];
width=0.0];
width=0.0];
width=0.0];
Alice[height=0.0,
Bob [height=0.0,
Crude[height=0.0,
Dr [height=0.0,
];
];
edge [color=black];
graph [bb=0,0,0.0,0,
node [color=black,
test {}
';
#v-
where $VAR1 is $g1 and $VAR2 = $g1, once before and once after the
laundering which was introduced as a patch for #711446.
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: Ludwig Hirsch: 1928
signature.asc
Description: Digital Signature
Bug#664761: apache2/conf.d migration: what should webapp packagers do?
Hi Jonathan, On 14.07.2014 23:12, Jonathan Nieder wrote: https://wiki.debian.org/Apache/PackagingFor24 is helpful (thanks!), but I'm still stuck --- I really just don't know how to package gitweb in the new setup. See also http://bugs.debian.org/669292#28: * It's not clear when to run apache2_invoke enconf gitweb for a package like gitweb that does not have a Depends against apache 2.4. If I run it conditionally based on the Apache version, then gitweb will still be broken when the user upgrades apache, unless gitweb happens to be upgraded later in the same upgrade run. web applications aren't supposed to depend on Apache anyway. We suggest packagers of web applications to recommend on Apache so that other web servers can be used, too if people wish. On that matter I do not think gitweb would be different to other packages, or is it? Therefore, we recommend that you check if Apache 2.4 is installed at time you execute the maintainer scripts. There is not much you or we could do, if it isn't. We do both agree that gitweb should rather not depend on Apache, therefore we need conditionals in maintainer scripts. For Apache 2.4 this works like this: if [ -e /usr/share/apache2/apache2-maintscript-helper ] ; then . /usr/share/apache2/apache2-maintscript-helper apache2_invoke enconf gitweb.conf || exit $? fi This ensures that your configuration is enabled when Apache is installed, and it will not fail if it is not. You do not need to worry in what context to execute this, as our apache2-maintscript-helper takes care to figure out the right thing in the right context (e.g. postinst configure). * It's not clear when to run apache2_invoke disconf gitweb. At remove and purge time doesn't seem to be enough. Likewise as for the enable part. Just call if [ -e /usr/share/apache2/apache2-maintscript-helper ] ; then . /usr/share/apache2/apache2-maintscript-helper apache2_invoke disconf gitweb.conf || exit $? fi ... and apache2-maintscript-helper tries to figure out when to do what. In particular we disable the module in postrm purge, postrm remove and prerm remove. When else do you think it would be necessary? For the archives: apache2-maintscript-helper is reading the maintainer script state out of $@ supplied to your script. If you wish to call it from a function, you must ensure the context is preserved. If you wish, you can set APACHE2_MAINTSCRIPT_DEBUG (e.g. in /etc/apache2/envvars) and get debug output of the apache2-maintscript-helper at runtime to see what it does in various use cases. And https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=23;filename=update-apache-packaging.patch;att=1;bug=669292: - prerm deconfigure does not clean up as much as it should - needs triggers to reconfigure when apache is updated? Not sure what you ask me about here? Basically, I am stuck on understanding the state machine: (1) What is the intended update order between webapps, apache-common, and apache itself? What Depends, Pre-Depends, or triggers should be used to make sure everything works okay regardless of the update order? Please read http://anonscm.debian.org/gitweb/?p=pkg-apache/apache2.git;a=blob;f=debian/PACKAGING;h=0bbb06c48d628cd7c3b6037a0118574a722f2184;hb=HEAD#l157. Does this answer your questions? It does not talk about triggers, because there are none (though we planned to do at some stage) ;-) In particular, the conditional enconf and disconf invocations seem to make it easy to get into a non-working state and never get out of it. Well, we need to deal with that. This is not different than before. If Apache2 wasn't installed, you putting a conf to conf.d is not going to work out either. If you meant to address situations when you install your conf to conf-available and install Apache at a later stage, it is our business (i.e. Apache maintainer's) to ensure those get enabled then. That's a good point actually, and I need to think if we can and should do something in that case. (2) What is the intended uninstallation procedure? https://wiki.debian.org/Apache/PackagingFor24 tells me I should enconf in postinst and disconf in postrm. That's confusing because: * Usually in packaging, postinst is a mirror image of prerm so when the package is in a given dpkg state, the state of configuration matches that. Why here is postinst's mirror image in postrm instead? * Dependencies are not guaranteed to be present during postrm, so the disconf is not guaranteed to happen. It is actually preferred that disconf is called in prerm. This is also what dh-apache2 would do if you let it. Or in both scripts. I am not sure why this is isn't written more explicit in the wiki but I will fix that in a minute. -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D signature.asc
Bug#755317: libnet-bonjour-perl: FTBFS: Tests failures
Control: tag -1 + confirmed On Sat, 19 Jul 2014 20:44:36 +0200, David Suárez wrote: Source: libnet-bonjour-perl Version: 0.96-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140718 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[1]: Entering directory '/«PKGBUILDDIR»' PERL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -e test_harness(0, 'blib/lib', 'blib/arch') t/*.t t/1-use.t . ok Use of uninitialized value in uc at /«PKGBUILDDIR»/blib/lib/Net/Bonjour/Entry.pm line 272. Use of uninitialized value $_[4] in join or string at /usr/lib/perl5/Net/DNS/RR.pm line 69. Use of uninitialized value $argument in concatenation (.) or string at /usr/lib/perl5/Net/DNS/RR/.pm line 75. in new Net::DNS::RR( type ttl 3600 address name server.local ... ) at /«PKGBUILDDIR»/blib/lib/Net/Bonjour/Entry.pm line 327. # Looks like you planned 18 tests but ran 15. # Looks like your test exited with 255 just after 15. t/2-entry.t ... Dubious, test returned 255 (wstat 65280, 0xff00) Failed 3/18 subtests Breakage by recent Net::DNS? 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: Wir sind Helden: Der Krieg kommt schneller zurück als du denkst signature.asc Description: Digital Signature
Bug#755408: printer-driver-escpr: Cups Epson-WF-7610: not possible to select 'Rear Paper Feed Slot'
Package: printer-driver-escpr Version: 1.4.0-1 Severity: normal Dear Maintainer, I'm using a Epson WF-7610 Printer. Nearly everthing works as expected but it is not possible to select the 'Rear Paper Feed Slot'. If I do so the setting is ignored and the Printer still uses the paper cassette. I'm not sure if this bug is really related to the ppd (I've tried the upstream version of the PPDs with the same result -- not really a surprive as they are identical). -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages printer-driver-escpr depends on: ii libc6 2.19-7 ii libcups2 1.7.4-1 ii libcupsimage2 1.7.4-1 ii python33.4.1-1 ii xz-utils 5.1.1alpha+20120614-2 Versions of packages printer-driver-escpr recommends: ii cups-ppdc 1.7.4-1 Versions of packages printer-driver-escpr suggests: ii psutils 1.17.dfsg-1 -- 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#755324: Pending fixes for bugs in the pinto package
tag 755324 + pending thanks Some bugs in the pinto package are closed in revision bf78f275c1ec82485dd6f546ad3cb210d69bfe9a in branch 'master' by gregor herrmann The full diff can be seen at http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/pinto.git;a=commitdiff;h=bf78f27 Commit message: Add patch to use URI::file before using it. Thanks: David Suárez for the bug report. Closes: #755324 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755364: [Pkg-utopia-maintainers] Bug#755364: network-manager: Creates one additional bluetooth connection per resume
Am 20.07.2014 11:55, schrieb Michael Biebl: Am 19.07.2014 23:39, schrieb Julian Andres Klode: Package: network-manager Version: 0.9.10.0-1 Severity: normal After each resume an additional network connection for my Bluetooth PAN is created. Might be related to https://bugzilla.gnome.org/show_bug.cgi?id=732998 And https://bugzilla.gnome.org/show_bug.cgi?id=731937 -- 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#755282: nss-pam-ldap: [INTL:it] updated Italian translation of debconf messages
Control: tags -1 + pending On Sat, 2014-07-19 at 19:49 +0300, Andrei POPESCU wrote: Control: reassign -1 nss-pam-ldapd Thanks Andrei for re-assigning. On Sb, 19 iul 14, 17:22:02, Beatrice Torracca wrote: Please find attached the updated Italian translation of nss-pam-ldap debconf messages proofread by the Italian localization team. Thanks Beatrice for the updated translation, it will be included in the next upload. Thanks, -- -- arthur - adej...@debian.org - http://people.debian.org/~adejong -- signature.asc Description: This is a digitally signed message part
Bug#732025: kanla: fills harddisk with seems to be working messages
Michael wrote on 2013-12-14: The package cannot know which things to monitor and where to send alerts to. There just is no way to have it in “normal working condition” unless you configure it. The apache2 package also cannot know which content to serve, so serves virtually nothing by default - but ready for adding content, not (as with kanla) spewing debug hints filling up the disk. I would find it more appropriate to include the fail plugin but have it commented out by default - same as you've done with a sample use of the http plugin. For a better user experience, you could add debconf handling of where to send alerts to, but that is unneeded for the issue of this bugreport. If one wants debugging output, onewould enable optional features for that, not expect it to be enabled by default. I disagree. It is tempting and likely that without this message, people would configure kanla, say “this looks about right” and never get any alerts. Having a sightly annoying default configuration to err on the side of caution is the right thing, IMO. If you consider it unsuitable for kanla to be provided in a state that works out-of-the-box (i.e. working very little as nothing is being monitored, but also no debugging is enabled), then have the daemon turned *off* initially. I strongly recommend *against* that, however, as then _other_ users who _do_ understand what silence means cannot automatically install a working kanla (e.g. by providing add-on monitoring snippets by another package). - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#754078: crypt devices not brought online (backed by iscsi)
Hi, Am 20.07.2014 11:28, schrieb Peter Palfrader: On Mon, 07 Jul 2014, Peter Palfrader wrote: } weasel@valiant:~$ cat /etc/crypttab } sda3_crypt UUID=81402c7d-3819-4860-b71f-ff0f808f599e none luks } sda6_crypt UUID=4385f6be-9584-4fd9-a3b8-92a2826311a5 /etc/luks/sda6.key luks } } aux1 /dev/disk/by-path/ip-172.22.118.11\:3260-iscsi-iqn.1992-04.com.emc\:storage.storcenter.sbg.palfrader.org.aux1-lun-0 /etc/luks/aux1.key luks,noearly } mailbak /dev/disk/by-path/ip-172.22.118.11\:3260-iscsi-iqn.1992-04.com.emc\:storage.storcenter.sbg.palfrader.org.mailbak-lun-0 /etc/luks/mailbak.key luks,noearly It seems systemd does not handle those backslashes that were previously required to escape the colon correctly. If I remove those, systemd brings up the interfaces. It's still very slow (because it tries to get them before iscsi is up). So, - it should correctly handle backslashes, - it should probably not block/timeout on bringing up noearly interfaces. What exactly is the effect of noearly in general and in context of iscsi (under sysvinit)? -- 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#755409: Package should not be part of jessie
Source: net6,obby,gobby-0.4 Severity: serious I'd like to drop gobby 0.4 (not 0.4.9x aka 0.5) from Jessie. This means that net6, obby, and gobby-0.4 should be removed from testing. Further development focus will be on the 0.5 series. signature.asc Description: Digital signature
Bug#755410: RFS: python-xmp-toolkit/2.0.1-1 [ITA] -- Python library for XMP
Package: sponsorship-requests Severity: normal Hi, I'm looking for a sponsor of my package of the Python-xmp-toolkit: https://packages.qa.debian.org/p/python-xmp-toolkit.html The Debian patch is community maintained: http://anonscm.debian.org/viewvc/python-modules/packages/python-xmp-toolkit/trunk/ Plus, I've uploaded the my package to mentors: http://mentors.debian.net/package/python-xmp-toolkit http://mentors.debian.net/debian/pool/main/p/python-xmp-toolkit/python-xmp-toolkit_2.0.1-1.dsc My buildlog: http://www.danielstender.com/buildlogs/python-xmp-toolkit_2.0.1-1_amd64.build Changelog: * New upstream release: updated hardcode-library-name.diff, removed fix-deprecated-unittest-methods.diff (applied upstream). * Changed to build with setuptools: + Removed patches/no-setuptools.diff, added b-ds on python(3)-setuptools. * deb/control: + Change of maintainer (Closes: #708545). + Bumped debhelper level to 9 (also in debian/compat). + B-ds: dropped python-support, added python3-all, python(3)-mock, python(3)-tz (needed by test suite), and dh-python. + Bumped standards to 3.9.5 (no changes needed). + Changed Homepage URL (Google Code became obsolete). + Added X-Python(3)-Versions. + Added description for Python3 bindings package. * deb/copyright: + Updated Format URI [Jakub Wilk]. + Straightened, removed trailing commas, updated. * deb/rules: + Added DH_VERBOSE, DEB_BUILD_OPTIONS and PYBUILD_NAME export lines. + Reduced to build with dh sequencer. * deb/watch: changed from Google Code (obsolete) to Pypi. * Upstream ships with Sphinx documentation: + Removed deb/get-orig.source.sh (not needed anymore to create dfsg). + deb/control: added b-d for python-sphinx. + deb/rules: overrides for building docs and removal of docs/_build. + deb/rules: generation of symbolic links for jquery.js and underscore.js. + Added deb/python(3)-libxmp.docs and deb/python(3)-libxmp.doc-base. * deb/source: added extend-diff-ignore for \.egg-info. * Wrapped and sorted. Thank you very much, Daniel Stender -- http://www.danielstender.com/blog/ PGP key: 2048R/E41BD2D0 C879 5E41 1ED7 EE80 0F2E 7D0C DBDD 4D96 E41B D2D0 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696617: unetbootin: please document available command line options
Package: unetbootin Version: 603-1 Followup-For: Bug #696617 Dear Maintainer, the info at http://sourceforge.net/p/unetbootin/wiki/commands/ is very useful indeed. I was having troubles using unetbootin with a device containing a NTFS partition in order to create a bootable Windows drive, many guides suggested to use an old version of unetbootin but this was not strictly necessary, it was enough to pass the desired targetdrive option to unetbootin. The command line I had to use was: unetbootin installtype=USB targetdrive=/dev/sdf1 but finding out the appropriate options was hard, there was no mention of them in the man page or in the --help output, I was lucky to find the hint in a _comment_ to a blog post, and only after that I looked up targetdrive and landed on the official documentation on sf.net. Please mention the upstream documentation or list the command line options in the manual page. If you need help just say so and I will prepare a patch. Thanks, Antonio -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (900, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-rc2-ao2 (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/bash Versions of packages unetbootin depends on: ii gksu 2.0.2-6 ii libc62.19-7 ii libgcc1 1:4.9.0-10 ii libqt4-network 4:4.8.6+dfsg-2 ii libqtcore4 4:4.8.6+dfsg-2 ii libqtgui44:4.8.6+dfsg-2 ii libstdc++6 4.9.0-10 ii mtools 4.0.18-1 ii p7zip-full 9.20.1~dfsg.1-4.1 ii syslinux 3:6.03~pre18+dfsg-1 ii syslinux-common 3:6.03~pre18+dfsg-1 ii udev 208-6 Versions of packages unetbootin recommends: ii extlinux 3:6.03~pre18+dfsg-1 ii unetbootin-translations 603-1 unetbootin suggests no packages. -- no debconf information -- Antonio Ospite http://ao2.it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755411: build transitional package gobby
Package: gobby-0.5 Version: 0.4.94-6 Severity: normal Take over the gobby transitional package from gobby 0.4 and depend on 0.5 only. Put it into oldlibs as a proper transitional package. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755286: Bug#755285: marked as done (general: Black screen on resume after suspend)
On Sun, 2014-07-20 at 13:10 +0300, Aleksandar Nikolov wrote: I tried this experiment: Installed sshd and connected from another computer - it works. But after the lid closed and opened, I cannot connect. The system must be dead, although the fans blows and the power led is on. This means that your system hanged either during going into sleep mode or when exiting the sleep mode. This is then not a screen issue but a system issue. The fact that fans are on may indicate that the issue happened when exiting suspend mode. But we definitely need more information. Further after restart I found that nothing was written in neither dmesg dmesg does not remember messages from old boot, you need to relay on logs nor pm-powersave.log after the lid is closed and then opened. yes this is normal as you rebooted. Then this file will be filled for the next time but you won't be able to recover it. Normally you should find a /var/log/pm-*.log.1, these files are the ones you need to provide. Also it could be better if you try using the official Debian kernel, at least while we are investigating the issue. I assume you have good reason to use an other kernel, but we do not support such combinations, so please ensure investigating this bug with: (jessie)root@karim:~# aptitude show linux-image-amd64 Package: linux-image-amd64 State: not installed Version: 3.14+58 Priority: optional Section: kernel Maintainer: Debian Kernel Team debian-ker...@lists.debian.org Architecture: i386 Uncompressed Size: 38.9 k Depends: linux-image-3.14-1-amd64 Provides: linux-latest-modules-3.14-1-amd64 Description: Linux for 64-bit PCs (meta-package) This package depends on the latest Linux kernel and modules for use on PCs with AMD64, Intel 64 or VIA Nano processors. This kernel also runs on a Xen hypervisor. It supports both privileged (dom0) and unprivileged (domU) operation. Cheers, Abou Al Montacir signature.asc Description: This is a digitally signed message part
Bug#594798: #594798 - [nautilus] cannot remount usb devices
found 594798 3.12.2-1 I confirm this issue with nautilus-3.12.2-1. thanks regards Pedro
Bug#755249: IPv6 link non-functional after suspend
Hi! Ben Hutchings b...@decadent.org.uk writes: On Sat, 2014-07-19 at 08:39 +0200, Christoph Egger wrote: Package: src:linux Version: 3.14.12-1 Severity: important After suspend/resume the computer is unable to perform any IPv6 connection (no ping to fixed IP, no nc, no anything). tcpdump was unfortunately not helpfull in figuring out where exactly it breaks because, as soon as I start tcpdump, things work again. If I stop tcpdump after resume I can still reach all routed IPv6 addresses but only the local ones I have contacted while tcpdump running. Removing the interface and adding it again helps as well. [...] IPv6 addresses are dropped when the interface is taken down. Do you have a script that does that on suspend? I'm using pm-suspend for suspending: | % cat /var/log/pm-suspend.log | | % ls /etc/pm/* | /etc/pm/config.d: | unload_module | | /etc/pm/power.d: | | /etc/pm/sleep.d: | | % cat /etc/pm/config.d/unload_module | SUSPEND_MODULES=xhci_hcd anywhere else to look? I haven't done anything manually. Also what's the current-good way to do suspend without any magic for debugging purposes? The interface seems up after suspend (IPv4 works, even the autoconf address works after I remove the manually set IPv6 address). The problem either appeared with booting into the 3.13 kernel or with adding the br0.65 vlan interface -- I can try and see if removing the vlan interface changes anything as soon as I'm back home. Christoph pgphUq2RkvN1d.pgp Description: PGP signature
Bug#747599: ITP: lxqt-common -- Common files for LXQt
On Ma, 08 iul 14, 11:41:28, Gerhard A. Dittes wrote: Hi Andrew, great, that you intent to package LXQt! Have you any timeline in mind for doing that? I can hardly wait to use/test it on my Debian system. Me too, even if from experimental. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Bug#755412: debhelper: dh_install does not find file because dh_auto_install did not place them where expected
Package: debhelper
Version: 9.20140613
Severity: normal
Tags: upstream
Dear Maintainer,
I am trying to build from source the package 'konq-plugins' with a few hacks.
To do this, I am using 'apt-get source ...' (ok), then some hacks, then
'buildpackage -rfakeroot -uc -b' as found there:
http://www.debian.org/doc/manuals/apt-howto/ch-sourcehandling.en.html
The creation of the package fails at dh_install step:
make[2]: Leaving directory '[...]/kde-baseapps-4.12.4/obj-x86_64-linux-gnu'
dh_install
cp: cannot stat ‘debian/tmp/usr/lib/kde4/autorefresh.so’: No such file or
directory
dh_install: cp -a debian/tmp/usr/lib/kde4/autorefresh.so
debian/konq-plugins-curis//usr/lib/kde4/ returned exit code 1
/usr/share/pkg-kde-tools/qt-kde-team/2/dhmk.mk:97: recipe for target
'pre_install_dh_install' failed
make[1]: *** [pre_install_dh_install] Error 2
Apparently, there is no directory 'tmp' and the file is already at the 'final'
place because 'dh_auto_install' seems to have already got it installed in
'konq-plugins-curis':
make[1]: Entering directory '/home/curis/Programming/kde-baseapps-4.12.4'
dh_testroot
dh_prep
dh_installdirs
dh_auto_install '--buildsystem=kde' --parallel
make[2]: Entering directory '[...]/kde-baseapps-4.12.4/obj-x86_64-linux-gnu'
[...]
-- Installing:
[...]/kde-baseapps-4.12.4/debian/konq-plugins-curis/usr/lib/kde4/autorefresh.so
From my (small) investigation, it seems in line with what the code does,
because amongst my hacks the control file now defines only one package
(instead of many), and in 'dh_auto_install' there is:
my @allpackages=getpackages();
if (@allpackages 1) {
$destdir=debian/tmp;
} else {
$destdir=tmpdir($dh{MAINPACKAGE});
}
but it seems that 'dh_install' is not ready for this optimisation?
Best regards,
Christophe.
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages debhelper depends on:
ii binutils2.24.51.20140617-1
ii dpkg1.17.10
ii dpkg-dev1.17.10
ii file1:5.19-1
ii man-db 2.6.7.1-1
ii perl5.18.2-6
ii po-debconf 1.0.16+nmu3
debhelper recommends no packages.
Versions of packages debhelper suggests:
pn dh-make none
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#597027: #597027 - nautilus-connect-server misses options in dropdown menu
Hey Jonas, I think we have to know in advanced what protocol types are supported: https://help.gnome.org/users/gnome-help/stable/nautilus-connect.html.en nautilus-connect-server 3.12.2-1 only has custom location and one example. thanks regards Pedro
Bug#755383: ITP: fonts-adobe-sourcehansans-twhk -- “Source Han Sans TWHK” A sans-serif Pan-CJK font family (TWHK subset) that is offered in seven weights
On Sun, 2014-07-20 at 01:08 -0700, LIU Dongyuan wrote: Package: wnpp Severity: wishlist Owner: LIU Dongyuan liu.dongy...@gmail.com * Package name: fonts-adobe-sourcehansans-twhk Version : 1.000 Upstream Author : Ken Lunde lu...@adobe.com * URL : http://sourceforge.net/projects/source-han-sans.adobe/ * License : Apache 2.0 Description : “Source Han Sans TWHK” A sans-serif Pan-CJK font family (TWHK subset) that is offered in seven weights Source Han Sans is a sans serif Pan-CJK font family that is offered in seven weights—ExtraLight, Light, Normal, Regular, Medium, Bold, and Heavy—and in several OpenType/CFF-based deployment configurations to accommodate various system requirements or limitations. As the name suggests, Pan-CJK fonts are intended to support the characters necessary to render or display text in Simplified Chinese, Traditional Chinese, Japanese, and Korean. Does it make sense to use separate source packages for each of the languages covered by Source Han? Are they likely to be updated separately? Ben. -- Ben Hutchings Kids! Bringing about Armageddon can be dangerous. Do not attempt it in your own home. - Terry Pratchett and Neil Gaiman, `Good Omens' signature.asc Description: This is a digitally signed message part
Bug#754078: crypt devices not brought online (backed by iscsi)
On Sun, 20 Jul 2014, Michael Biebl wrote: Hi, Am 20.07.2014 11:28, schrieb Peter Palfrader: On Mon, 07 Jul 2014, Peter Palfrader wrote: } weasel@valiant:~$ cat /etc/crypttab } sda3_crypt UUID=81402c7d-3819-4860-b71f-ff0f808f599e none luks } sda6_crypt UUID=4385f6be-9584-4fd9-a3b8-92a2826311a5 /etc/luks/sda6.key luks } } aux1 /dev/disk/by-path/ip-172.22.118.11\:3260-iscsi-iqn.1992-04.com.emc\:storage.storcenter.sbg.palfrader.org.aux1-lun-0 /etc/luks/aux1.key luks,noearly } mailbak /dev/disk/by-path/ip-172.22.118.11\:3260-iscsi-iqn.1992-04.com.emc\:storage.storcenter.sbg.palfrader.org.mailbak-lun-0 /etc/luks/mailbak.key luks,noearly It seems systemd does not handle those backslashes that were previously required to escape the colon correctly. If I remove those, systemd brings up the interfaces. It's still very slow (because it tries to get them before iscsi is up). So, - it should correctly handle backslashes, - it should probably not block/timeout on bringing up noearly interfaces. What exactly is the effect of noearly in general and in context of iscsi (under sysvinit)? man crypttab(5) has this to say: | noearly | The cryptsetup init scripts are invoked twice during the boot | process - once before lvm, evms, raid, etc. are started and once | again after that. Sometimes you need to start your encrypted | disks in a special order. With this option the device is ignored | during the first invokation of the cryptsetup init scripts. So, previously on my system, cryptdisk-early would run and bring up the local cryptdevices that were backed by partitions. Then, after network and iscsi was up, it'd run again and bring up the remaining devices. Currently, with systemd, it gets to where it'd like to bring up the crypt devices. As network and open-iscsi aren't up yet, it wastes a lot of time waiting for block devices that will never appear (at least not without further action later in the boot process). Cheers, -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal http://www.palfrader.org/ | `. `' Operating System | `-http://www.debian.org/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755249: IPv6 link non-functional after suspend
On Sun, 2014-07-20 at 15:39 +0200, Christoph Egger wrote: Hi! Ben Hutchings b...@decadent.org.uk writes: On Sat, 2014-07-19 at 08:39 +0200, Christoph Egger wrote: Package: src:linux Version: 3.14.12-1 Severity: important After suspend/resume the computer is unable to perform any IPv6 connection (no ping to fixed IP, no nc, no anything). tcpdump was unfortunately not helpfull in figuring out where exactly it breaks because, as soon as I start tcpdump, things work again. If I stop tcpdump after resume I can still reach all routed IPv6 addresses but only the local ones I have contacted while tcpdump running. Removing the interface and adding it again helps as well. [...] IPv6 addresses are dropped when the interface is taken down. Do you have a script that does that on suspend? I'm using pm-suspend for suspending: | % cat /var/log/pm-suspend.log | | % ls /etc/pm/* | /etc/pm/config.d: | unload_module | | /etc/pm/power.d: | | /etc/pm/sleep.d: | | % cat /etc/pm/config.d/unload_module | SUSPEND_MODULES=xhci_hcd anywhere else to look? I haven't done anything manually. Also what's the current-good way to do suspend without any magic for debugging purposes? echo mem /sys/power/state The interface seems up after suspend (IPv4 works, even the autoconf address works after I remove the manually set IPv6 address). It sounds a little bit like multicast RX is broken after resume (IPv6 uses multicast for neighbour discovery). But, looking at the driver code (r8169) it certainly appears to reprogram the hardware multicast filter on resume. Please send the output of 'ethtool -d eth0' before and after suspend/resume. The problem either appeared with booting into the 3.13 kernel or with adding the br0.65 vlan interface -- I can try and see if removing the vlan interface changes anything as soon as I'm back home. I don't see any changes to r8169 between 3.12 and 3.13 that could explain this. Ben. -- Ben Hutchings Kids! Bringing about Armageddon can be dangerous. Do not attempt it in your own home. - Terry Pratchett and Neil Gaiman, `Good Omens' signature.asc Description: This is a digitally signed message part
Bug#755390: libphobos-4.9-dev: does not build on armel/armhf anymore but did so in the past
Control: tags -1 + pending Am 20.07.2014 11:32, schrieb Markus Koschany: Package: libphobos-4.9-dev Version: 4.9.0-7 Severity: normal Hi, libphobos built successfully with gdc 4.8 on armel/armhf in the past. However libphobos-4.9-dev is not available for these architectures anymore. All programs written in the programming language D FTBFS on armel/armhf at the moment. See scheduled for the next upload. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754078: crypt devices not brought online (backed by iscsi)
Am 20.07.2014 15:42, schrieb Peter Palfrader: On Sun, 20 Jul 2014, Michael Biebl wrote: Hi, Am 20.07.2014 11:28, schrieb Peter Palfrader: On Mon, 07 Jul 2014, Peter Palfrader wrote: } weasel@valiant:~$ cat /etc/crypttab } sda3_crypt UUID=81402c7d-3819-4860-b71f-ff0f808f599e none luks } sda6_crypt UUID=4385f6be-9584-4fd9-a3b8-92a2826311a5 /etc/luks/sda6.key luks } } aux1 /dev/disk/by-path/ip-172.22.118.11\:3260-iscsi-iqn.1992-04.com.emc\:storage.storcenter.sbg.palfrader.org.aux1-lun-0 /etc/luks/aux1.key luks,noearly } mailbak /dev/disk/by-path/ip-172.22.118.11\:3260-iscsi-iqn.1992-04.com.emc\:storage.storcenter.sbg.palfrader.org.mailbak-lun-0 /etc/luks/mailbak.key luks,noearly It seems systemd does not handle those backslashes that were previously required to escape the colon correctly. If I remove those, systemd brings up the interfaces. It's still very slow (because it tries to get them before iscsi is up). So, - it should correctly handle backslashes, - it should probably not block/timeout on bringing up noearly interfaces. What exactly is the effect of noearly in general and in context of iscsi (under sysvinit)? man crypttab(5) has this to say: | noearly | The cryptsetup init scripts are invoked twice during the boot | process - once before lvm, evms, raid, etc. are started and once | again after that. Sometimes you need to start your encrypted | disks in a special order. With this option the device is ignored | during the first invokation of the cryptsetup init scripts. So, previously on my system, cryptdisk-early would run and bring up the local cryptdevices that were backed by partitions. Then, after network and iscsi was up, it'd run again and bring up the remaining devices. Currently, with systemd, it gets to where it'd like to bring up the crypt devices. As network and open-iscsi aren't up yet, it wastes a lot of time waiting for block devices that will never appear (at least not without further action later in the boot process). Hm, k. So I guess we'd need something like a cryptsetup-pre.target, where certain units can hook into (via Wants/Before), network.target being one of them. And devices flagged noearly would get a dependency on this target and be ordered after it. Lennart, do you have a different/better idea how we could handle such setups which have more complex requirements, like cryptsetup devices being backed by iscsi which in turn requires network access? Michael -- 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#755393: appstream transition yields conflicting versioned Recommends
Hi! 2014-07-20 11:50 GMT+02:00 Vincent Lefevre vinc...@vinc17.net: Source: appstream Version: 0.7.0-1 Severity: normal The libappstream0 and libappstream1 packages are co-installable, but have conflicting Recommends: For libappstream0: Version: 0.6.2-1 Recommends: appstream-index (= 0.6.2-1) For libappstream1: Version: 0.7.0-1 Recommends: appstream-index (= 0.7.0-1) meaning that either these Recommends dependencies are abusive or one of the packages could have problems due to unsatisfied Recommends. It's too late for libappstream0, but the libappstream1 one could yield future problems with a libappstream2. Yes, I already recognized that and changed the dependency to =, but didn't think that would justify an upload at time. Originally, the strict dependency was there to ensure the database matches the schema which the current libappstream library can read. But since the databases are backwards-compatible now, this is no longer necessary. This bug will be fixed with the next upload of this package. Thanks for reporting it! Cheers, Matthias -- Debian Developer | Freedesktop-Developer I welcome VSRE emails. See http://vsre.info/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754575: New upstream version available
Please package 2.27 for inclusion in Unstable
Bug#754665: Removal of D based games from armel/armhf (Tatan #754665)
On 20.07.2014 00:02, Peter De Wachter wrote: Has anybody asked the gcc/gdc maintainers about this? The changelog says nothing about dropping phobos on arm, so I think this might simply be a packaging bug. As far as I know, gdc 4.9 on arm is supported upstream. Seems you're right. I filed https://bugs.debian.org/755390 and the gcc/gdc maintainer confirmed your suspicion. Upload is pending. I will request a give-back for Tatan as soon as libphobos-4.9-dev is available on armel/armhf again. Regards, Markus signature.asc Description: OpenPGP digital signature
Bug#754984: libpam-systemd 208-6 conflicts with sysvinit-core
2014-07-20 12:00 GMT+02:00 Elimar Riesebieter riese...@lxtec.de: * Michael Biebl bi...@debian.org [2014-07-17 17:25 +0200]: Am 17.07.2014 16:20, schrieb Elimar Riesebieter: [...] I don't see the intention? You should read the changelog then. Not understanding the intentions is not a justification for reopening a bug report which has been closed by its maintainer. It seems that the intention is to push systemd as the only init system. Why did you upload 208-6 _before_ systemd-shim was adjusted? sysvinit is broken by that injudicious action! Systemd 208 brings a lot of fixes and has been out for a year. The systemd-shim people knew about the issues with systemd = 205 and have been notified that a new systemd will be uploaded to Debian in 4months last November or December, if I remember correctly. A bug was filed against the shim, and the systemd maintainers waited a huge extra-time to see if the shim will get ready. But since this is not the case, systemd 208 improves a lot of things and all necessary actions have been taken to get the shim ready in time (which didn't happen), the upload was absolutely justified. I recommend helping https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752939 to make the shim available again. Cheers, Matthias -- I welcome VSRE emails. See http://vsre.info/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#598491: #598491 - Timeout waiting for mount to appear in nautilus when mounting a nfs4-share
Hey, this is an old bug. Could you please still reproduce this issue with newer nautilus version like 3.4.2-1+build1 or 3.8.2-3 ? thanks regards Pedro
Bug#755219: [php-maint] Bug#755219: php5: Roundcube fails after upgrading to 5.6.0~rc2+dfsg-3
Hi,
On 19.07.2014 01:00, Ondřej Surý wrote:
Only thing that's broken right now is getallheaders() in php5-fpm,
so there's a remote possibility that roundcube is using that...
Anyway RC3 should be out soon and I'll fix getallheaders there, so
it might help...
I think that is indeed the case. getallheaders() is used if it exists.
public static function request_header($name)
{
if (function_exists('getallheaders')) {
$hdrs = array_change_key_case(getallheaders(), CASE_UPPER);
$key = strtoupper($name);
}
else {
$key = 'HTTP_' . strtoupper(strtr($name, '-', '_'));
$hdrs = array_change_key_case($_SERVER, CASE_UPPER);
}
return $hdrs[$key];
}
Best Regards,
Bernhard
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755413: gucharmap: please add search on pronunciation
Package: gucharmap Version: 1:3.12.1-1 Severity: wishlist Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? trying to search for a kana glyph with the same pronunciation as the currently selected glyph * What exactly did you do (or not do) that was effective (or ineffective)? tried searching for the pronunciation string to match descriptions and none was found. * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-rc5+ (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages gucharmap depends on: ii dconf-gsettings-backend [gsettings-backend] 0.20.0-2 ii libatk1.0-0 2.12.0-1 ii libc62.19-7 ii libcairo21.12.16-2 ii libglib2.0-0 2.41.0-1 ii libgtk-3-0 3.12.2-1+b1 ii libgucharmap-2-90-7 1:3.12.1-1 ii libpango-1.0-0 1.36.3-1 ii libpangocairo-1.0-0 1.36.3-1 Versions of packages gucharmap recommends: ii yelp 3.12.0-1 gucharmap 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
