Bug#784556: gem2deb: should generate Build-Depends and Depends with one item per line
On 11/05/15 at 19:16 -0300, Antonio Terceiro wrote: On Mon, May 11, 2015 at 11:06:32PM +0200, Lucas Nussbaum wrote: Could you please review the attached patch? I'm not sure if we should introduce an option to disable this. But I tend to agree with you (= I can't think of a reason to not want that, ever.) Let's always do it and see if anyone complains. ;-) OK, pushed with your proposed change. Thanks for the feedback! Lucas signature.asc Description: Digital signature
Bug#785074: sucrose-0.98: not installable in sid
Package: sucrose-0.98 Version: 0.98.8-2 Severity: serious User: trei...@debian.org Usertags: edos-uninstallable Hi, sucrose-0.98 is not installable in sid since 2015-04-04. It depends on gir1.2-maliit-1.0, which exists only in experimental. Cheers -Ralf. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785055: [Pkg-xfce-devel] Bug#785055: lightdm-gtk-greeter: white screen until I click a mouse button, with 2 screens
On mar., 2015-05-12 at 00:04 +0200, Vincent Lefevre wrote: On 2015-05-11 23:23:47 +0200, Vincent Lefevre wrote: Package: lightdm-gtk-greeter Version: 2.0.0-2 Severity: important Tags: upstream Forwarded: https://bugs.launchpad.net/ubuntu/+source/lightdm-gtk-greeter/+bug/1426664 or perhaps https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1410406 I also see a 100% CPU usage (but the screen is white, not black). Does setting active-monitor=0 fix your problem? -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#721227: audacious: Audacious opens for inode/directory
Package: audacious Version: 3.5-2 Followup-For: Bug #721227 This annoying bug still persist in 2015 and Debian 8 Jessie. I tried everything that I could but Audacious persist putting itself as main app for directories. Does anyone knows how exactly this could be stopped beside using different player? -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages audacious depends on: ii audacious-plugins3.5-1+b2 ii dbus 1.8.16-1 ii dbus-x11 1.8.16-1 ii gtk2-engines-pixbuf 2.24.25-3 ii libaudcore2 3.5-2 ii libc62.19-18 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libgtk-3-0 3.14.5-1 Versions of packages audacious recommends: ii unzip 6.0-16 audacious 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#785075: util-linux: /sbin/fstrim contains 2MiB of zero bytes
Package: util-linux Version: 2.26.2-2 Severity: minor Huge increase in the size of /sbin/fstrim on amd64. % dpkg -c util-linux_2.25.2-6_amd64.deb | grep -F /sbin/fstrim -rwxr-xr-x root/root 35432 2015-03-29 23:34 ./sbin/fstrim % dpkg -c util-linux_2.26.2-2_amd64.deb | grep -F /sbin/fstrim -rwxr-xr-x root/root 2132688 2015-05-03 23:30 ./sbin/fstrim There is a 2MiB block of zeros in the middle of the file. % hd /sbin/fstrim | grep -C2 '^\*' [...] 7db0 e0 e3 ff ff 1a 00 00 00 00 00 00 00 00 00 00 00 || 7dc0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || * 00207dc0 b0 26 40 00 00 00 00 00 90 26 40 00 00 00 00 00 |.@..@.| 00207dd0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || [...] Maybe another case of #750722? [1] If so, it will probably fix itself next time the package is rebuilt. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750722 -- http://rjy.org.uk/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785076: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
Package: x11-common Version: 1:7.7+9 Setting up x11-common (1:7.7+9) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769406: getty with systemd
There is a similar issue, especially systemd environment. The wheezy installer add serial console getty section in inittab, but jessie's systemd seems no care. I need to execute systemctl enable serial-getty@ttyS0.service manually to enable serial console login. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785077: w3m does not support single quoted meta refresh
Package: w3m Version: 0.5.3-8 Severity: normal To access https://www.google.com/accounts/ with w3m, it causes infinity refresh loop. It was already reported on Gentoo and NetBSD, and and also there is a patch. http://gnats.netbsd.org/42400 -- System Information: Debian Release: 7.8 APT prefers oldstable APT policy: (500, 'oldstable') Architecture: i386 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages w3m depends on: ii libc62.13-38+deb7u8 ii libgc1c2 1:7.1-9.1 ii libgpm2 1.20.4-6 ii libssl1.0.0 1.0.1e-2+deb7u16 ii libtinfo55.9-10 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages w3m recommends: ii ca-certificates 20130119+deb7u1 Versions of packages w3m suggests: ii man-db 2.6.2-1 ii menu2.1.46 ii migemo 20110227-7 ii migemo-el [migemo] 20110227-7 ii mime-support3.52-1+deb7u1 ii w3m-el 1.4.4-11 ii w3m-img 0.5.3-8 -- 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#785016: GnuTLS: received alert [70]: Error in protocol version
notfound 785016 1.16.3-2 tags 785016 + moreinfo thanks Hello Mathieu, please use reportbug to report your bugs because it includes more information about your system. The missing information is which Debian version you are using (stable, testing,...) and what versions of the dependencies are installed. I can guess but this might be wrong. thx. Am Montag, den 11.05.2015, 17:49 +0200 schrieb Mathieu Malaterre: Package: wget Version: 1.16-1 Severity: important I cannot download a zip file from https location: ... (documents.epfl.ch)|128.178.222.31|:443... connected. GnuTLS: A TLS fatal alert has been received. GnuTLS: received alert [70]: Error in protocol version Unable to establish SSL connection. It seems to be working from chromium -- Noël Köthe noel debian.org Debian GNU/Linux, www.debian.org signature.asc Description: This is a digitally signed message part
Bug#777113: invoke-rc.d, service under systemd: Avoid job dependency loops during boot/shutdown
Hello all, Martin Pitt [2015-02-15 16:43 +0100]: + * service, invoke-rc.d: Avoid deadlocks during bootup and shutdown from +units/hooks which call invoke-rc.d service reload and similar, since the +synchronous wait plus systemd's normal behaviour of transactionally +processing all dependencies first easily causes dependency loops. Thus +during boot/shutdown operate only on the unit and not on its dependencies, +just like SysV behaves. Can we please apply this patch now? It already missed jessie :-/ We do have some workarounds in systemd, but they can't cover all cases. Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#785055: [Pkg-xfce-devel] Bug#785055: lightdm-gtk-greeter: white screen until I click a mouse button, with 2 screens
On 2015-05-12 08:11:26 +0200, Yves-Alexis Perez wrote: On mar., 2015-05-12 at 00:04 +0200, Vincent Lefevre wrote: On 2015-05-11 23:23:47 +0200, Vincent Lefevre wrote: Package: lightdm-gtk-greeter Version: 2.0.0-2 Severity: important Tags: upstream Forwarded: https://bugs.launchpad.net/ubuntu/+source/lightdm-gtk-greeter/+bug/1426664 or perhaps https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1410406 I also see a 100% CPU usage (but the screen is white, not black). Does setting active-monitor=0 fix your problem? Yes, it does. -- Vincent Lefèvre vinc...@vinc17.net - Web: https://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: https://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780359: Options w.r.t. libcgal11 transition
On Tue, May 12, 2015 at 10:29 AM, Jonathan Wiltshire j...@debian.org wrote: On 2015-05-12 09:07, Johannes Ring wrote: On Mon, May 11, 2015 at 11:35 PM, Joachim Reichel joachim.reic...@gmx.de wrote: Hi, dolfin is now the only reverse dependency holding up the libcgal11 transition. What are the options? (1) Fix dolfin without causing another transition (2) Remove dolfin from testing (3) Upload 1.5.0-1 from experimental to unstable This will be the correct solution IMO. I will do that now. No, please do NOT do that now. It is the correct long-term solution, but it will entangle the cgal transition. Wait until britney has a chance to sort it out. ok! Johannes -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782364: linux-image-3.16.0-4-armmp: please configure drivers for both Cubox i4pro real time clocks
On May 6, 2015, at 3:35 AM, Rick Thomas rbtho...@pobox.com wrote: On May 6, 2015, at 3:27 AM, Ian Campbell i...@debian.org wrote: It would be preferable to test the thing in Sid before the upload to jessie-proposed-updates I’ll keep an eye out for it. But I don’t have one of the cubox models without the battery-backed RTC, so I won’t be able to test that case. Is there anyone out there in debian-arm land with an appropriate test box? Enjoy! Rick Am I looking in the wrong place? I would have expected to see something show up in sid by now. Is there a particular linux-image….deb I should download from somewhere to test this? Thanks for all your help! Rick -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785079: RM: wxwidgets2.8 -- ROM; Unmaintained upstream; newer release packaged
Package: ftp.debian.org Severity: normal Please remove wxwidgets2.8 from unstable. It's unmaintained upstream (last upstream release was 2.8.12 on 2011-03-28 - over 4 years ago), and a newer upstream release branch is packaged as wxwidgets3.0. It was already removed from testing (before the jessie freeze). There are a few lingering packages in unstable depending on it, but all have had bugs filed regarding updating to use wxwidgets3.0 for around a year now (the last filed was #751241 for amule on 2014-06-11): | olly@coccia:~$ dak rm -Rn wxwidgets2.8 | [...] | Checking reverse dependencies... | # Broken Depends: | amule: amule |amule-daemon |amule-utils |amule-utils-gui | codeblocks: codeblocks | codeblocks-contrib | libcodeblocks0 | libwxsmithlib0 | codelite: codelite [sparc] | codelite-plugins [sparc] | gspiceui: gspiceui | plplot: plplot11-driver-wxwidgets [sparc] | sitplus: sitplus [amd64 arm64 armel armhf i386 mips mipsel powerpc ppc64el s390x sparc] | tribler: tribler | usbprog: usbprog-gui [hurd-i386] | | # Broken Build-Depends: | amule: libwxgtk2.8-dev |wx2.8-i18n | codeblocks: libwxgtk2.8-dev | codelite: libwxgtk2.8-dev | gpac: libwxgtk2.8-dev | gspiceui: libwxbase2.8-dev | libwxgtk2.8-dev | matplotlib: python-wxgtk2.8 | plplot: libwxgtk2.8-dev | sitplus: libwxbase2.8-dev | libwxgtk2.8-dev | wx2.8-headers | usbprog: libwxgtk2.8-dev | | Dependency problem found. A quick analysis - these packages have actually been migrated away from wxwidgets2.8, but the newer package has failed to build on sparc or hurd-i386: codelite plplot usbprog gpac matplotlib These genuinely still depend on wxwidgets2.8: amule codeblocks gspiceui sitplus tribler Cheers, Olly signature.asc Description: Digital signature
Bug#785081: spamassassin: cronjob doesn't check if spamassasin is enabled before reloading
Package: spamassassin Version: 3.4.0-6 Severity: normal Tags: patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Maintainer, I'm running spamassasin through amavis therefore spamassasin is not running as a service. /etc/cron.daily/spamassassin tries to reload the service after updates have been found, resulting in an error mail as the service is not running and can therefore not be reloaded. I would suggest checking $ENABLED (as configured in /etc/default/spamassassin) before reloading the service, see attached patch. cu Alex - -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages spamassassin depends on: ii adduser 3.113+nmu3 ii init-system-helpers 1.22 pn libarchive-tar-perl none ii libhtml-parser-perl 3.71-1+b3 ii libnet-dns-perl 0.81-2 ii libnetaddr-ip-perl 4.075+dfsg-1+b1 ii libsocket6-perl 0.25-1+b1 ii libsys-hostname-long-perl 1.4-3 ii libwww-perl 6.08-1 ii perl5.20.2-3 ii perl-modules [libio-zlib-perl] 5.20.2-3 Versions of packages spamassassin recommends: ii gnupg 1.4.18-7 ii libio-socket-inet6-perl2.72-1 ii libmail-spf-perl 2.9.0-3 ii perl [libsys-syslog-perl] 5.20.2-3 pn sa-compile none ii spamc 3.4.0-6 Versions of packages spamassassin suggests: ii libdbi-perl 1.631-3+b1 ii libio-compress-perl [libcompress-zlib-perl] 2.066-1 ii libio-socket-ssl-perl2.002-2 ii libmail-dkim-perl0.40-1 ii perl [libcompress-zlib-perl] 5.20.2-3 pn pyzornone pn razornone - -- Configuration Files: /etc/default/spamassassin changed: ENABLED=0 OPTIONS=--create-prefs --max-children 5 --helper-home-dir PIDFILE=/var/run/spamd.pid CRON=1 - -- no debconf information -BEGIN PGP SIGNATURE- iEYEARECAAYFAlVRozkACgkQci0IS3Y4ncrf2gCghfc6OOHMgzCk+fYcKWxanXRm 1VYAoImCXThIyRSps56I6l/jL7cOE/dK =Gjct -END PGP SIGNATURE- --- /etc/cron.daily/spamassassin.orig 2015-05-12 08:41:58.431225651 +0200 +++ /etc/cron.daily/spamassassin 2015-05-12 08:40:43.603025384 +0200 @@ -48,10 +48,12 @@ # Tell a running spamd to reload its configs and rules. reload() { # Reload -if which invoke-rc.d /dev/null 21; then -invoke-rc.d spamassassin reload /dev/null -else -/etc/init.d/spamassassin reload /dev/null +if [ $ENABLED -ne 0 ]; then +if which invoke-rc.d /dev/null 21; then +invoke-rc.d spamassassin reload /dev/null +else +/etc/init.d/spamassassin reload /dev/null +fi fi if [ -d /etc/spamassassin/sa-update-hooks.d ]; then run-parts --lsbsysinit /etc/spamassassin/sa-update-hooks.d
Bug#784427: [Pkg-libvirt-maintainers] Bug#784427: virt-manager: unsupported configuration: spicevmc not supported in this QEMU binary)s
retitle On Sat, May 09, 2015 at 12:57:22PM +0200, David Ayers wrote: Traceback (most recent call last): File /usr/share/virt-manager/virtManager/create.py, line 1344, in page_changed self.populate_summary() File /usr/share/virt-manager/virtManager/create.py, line 931, in populate_summary self.netdev_changed(None) File /usr/share/virt-manager/virtManager/create.py, line 1088, in netdev_changed obj = self.conn.get_net(key) File /usr/share/virt-manager/virtManager/connection.py, line 685, in get_net return self.nets[uuid] KeyError: '1f05d411-9f8f-5ee4-4162-4616caa714de' ## Forward 5/5 So it's failing when building the summary. I'm not sure why it can't find net with that uuid. Can you do a grep -r 1f05d411-9f8f-5ee4-4162-4616caa714de /etc/libvirt/ on the affected host (assuming you're seeing the error when using qemu+ssh://ayers@myhost/system) Is the behaviour different if you use qemu:///system ? Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784245:
Control: severity -1 serious Hi Joachim, since this bug is already there in jessie, it doesn't appear as a regression, hence it doesn't prevent testing migration. If I'm correct, your intent is to let 7.8 migrate, and this isn't a blocker. In my opinion this still is an RC (for Stretch), hence I honestly think it should be Serious. However I'm not the maintainer, neither I want to start a severity ping/pong game, so feel free to change it back, I won't touch it anymore :) cheers, keep up the good work! :) Gianfranco Il Lunedì 11 Maggio 2015 22:21, Joachim Breitner nome...@debian.org ha scritto: Control: severity -1 normal On Mon, 4 May 2015 14:53:35 + (UTC) Gianfranco Costamagna costamagnagianfra...@yahoo.it wrote: As Joachim said in a mail where I requested the same thing: [1] (if correct) lists the compatibility matrix of ghc and llvm so 7.10 llvm 3.5 7.11 llvm 3.6 [1] http://smart-cactus.org/~ben/posts/2014-11-28-state-of-llvm-backend.html Quite right. So for 7.8 this is unavoidable, hence I’m downgrading this bug for now. Greetings, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784245:
Hi, Am Dienstag, den 12.05.2015, 06:52 + schrieb Gianfranco Costamagna: Hi Joachim, since this bug is already there in jessie, it doesn't appear as a regression, hence it doesn't prevent testing migration. If I'm correct, your intent is to let 7.8 migrate, and this isn't a blocker. Yes, that is my intend. But I’m worried about auto-removal of GHC on testing... Or is GHC already a key package, and hence immune to auto-removal? Not according to https://udd.debian.org/cgi-bin/key_packages.cgi. Oh well, we’ll see what happens. Greetings, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Bug#780359: Options w.r.t. libcgal11 transition
On 2015-05-11 22:35, Joachim Reichel wrote: Hi, dolfin is now the only reverse dependency holding up the libcgal11 transition. What are the options? (1) Fix dolfin without causing another transition (2) Remove dolfin from testing (3) Upload 1.5.0-1 from experimental to unstable (4) ...? dolfin has a rdep in testing, so removing it isn't (yet) an option. (Although its rdep fenics isn't going to migrate either because it depends on the version of dolfin in experimental since six weeks... what a mess.) I've asked ftp-masters to decruft gdal making dolfin in sid uninstallable. Britney may be able to smooth-update gdal, in which case the transition can take place and the dolfin maintainers can fix the bug at their leisure. -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 directhex i have six years of solaris sysadmin experience, from 8-10. i am well qualified to say it is made from bonghits layered on top of bonghits -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785080: update ruby-timers to latest upstream release
package: ruby-timers version: 1.1.0-2 timers ~ 4.0.0 is required for celluloid 0.16.0, which is in turn required for sidetiq 0.6.3 but when I tried updating, I got the following error /home/pravi/forge/debian/git/pkg-ruby-extras/ruby-timers/lib/timers/timer.rb:2:in `top (required)': Timers is not a module (TypeError) from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /home/pravi/forge/debian/git/pkg-ruby-extras/ruby-timers/lib/timers/group.rb:6:in `top (required)' from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /home/pravi/forge/debian/git/pkg-ruby-extras/ruby-timers/lib/timers.rb:4:in `top (required)' from /home/pravi/forge/debian/git/pkg-ruby-extras/ruby-timers/spec/spec_helper.rb:4:in `require_relative' from /home/pravi/forge/debian/git/pkg-ruby-extras/ruby-timers/spec/spec_helper.rb:4:in `top (required)' from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /home/pravi/forge/debian/git/pkg-ruby-extras/ruby-timers/spec/cancel_spec.rb:2:in `top (required)' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1226:in `load' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1226:in `block in load_spec_files' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1224:in `each' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1224:in `load_spec_files' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:98:in `setup' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:86:in `run' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:71:in `run' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:39:in `invoke' from /usr/bin/rspec:4:in `main' Loading simplecov-html failed, install ruby-simplecov-html [Coveralls] Set up the SimpleCov formatter. [Coveralls] Using SimpleCov's default settings. [Coveralls] Outside the Travis environment, not sending data. /usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb failed ERROR: Test ruby2.1 failed. Exiting. dh_auto_install: dh_ruby --install /home/pravi/forge/debian/git/pkg-ruby-extras/ruby-timers/debian/ruby-timers returned exit code 1 debian/rules:15: recipe for target 'binary' failed make: *** [binary] Error 1 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 debuild: fatal error at line 1376: dpkg-buildpackage -rfakeroot -D -us -uc -i -I failed gbp:error: 'debuild -i -I -k0x4512c22a' failed: it exited with 29 signature.asc Description: OpenPGP digital signature
Bug#785078: xserver-xorg-video-intel: Recent update triggers hung GPU, disabled acceleration
Hi Paul, On Mon, May 11, 2015 at 11:34 PM, Paul Millar paul.mil...@desy.de wrote: Package: xserver-xorg-video-intel Version: 2:2.99.917-1 Severity: important Dear Maintainer, I ran the usual apt-get update apt-get upgrade. This pulled in new packages for the intel X11 driver. After restarting, I noticed that the XV extension no longer worked when using mplayer. Subsequent investigation showed that the intel driver now reports it detected a hung GPU and has disabled acceleration as a consequence. Please file a bug report upstream against the intel DDX driver (following the instructions at [1]). Regards, Vincent [1] https://01.org/linuxgraphics/documentation/how-report-bugs -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768983: ITP: carbon-c-relay -- status?
hi Bernd, On Mon, May 11, 2015 at 03:33:41PM +0200, Bernd Zeimetz wrote: Hi Filippo, I was just wondering what the status of this ITP is? Do you plan to upload a package soon-ish? the package is at https://anonscm.debian.org/cgit/collab-maint/carbon-c-relay.git/ and upstream has released 0.40 yesterday, I think an upload might happen in the next two weeks! If you are interested though feel free to go ahead, I'll be fairly busy at work at least until end of May thanks! filippo -- http://esaurito.net - 0x99D49B6B00CAD1E5 - ⠠⠵ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785017: mate-power-manager: brightness is reset to maximum on every restart
Control: tags -1 patch Hi Flos, On Mo 11 Mai 2015 17:58:22 CEST, flos wrote: Package: mate-power-manager Version: 1.8.1+dfsg1-5 Severity: normal Dear MATE Maintainer, Currently the mate-power-manager could not save the brightness settings after changes. A workaround would be using the 'dconf-editor' or 'gsettings' tools to change the value of the key 'brightness-ac' of schema org.mate.power-manager. I modify the gpm-backlight.c a little so that we can save the brightness settings after every brightness adjustment when ac power supply is used. It seems to me that call back function 'brightness_changed_cb' was attached to 'backlight-priv-brightness' mistakenly. I think we should distinguish the backlight object from the brightness object. Please correct me and please review the patch in the attachment. Thank you very much! Best Regards, Flos I will make upstream aware of your patch and get back to you later once I got feedback from upstream. Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpxIYja02_l8.pgp Description: Digitale PGP-Signatur
Bug#785086: ITP: golang-bugsnag-panicwrap -- Go library for catching and handling panics in Go applications
Package: wnpp Severity: wishlist Owner: Tim Potter t...@hp.com * Package name: golang-bugsnag-panicwrap Version : 0.0~git2014 Upstream Author : Conrad Irwin, Mitchell Hashimoto * URL : https://github.com/bugsnag/panicwrap * License : MIT Programming Lang: Go Description : Go library for catching and handling panics in Go applications Go library for catching and handling panics in Go applications panicwrap is a Go library that re-executes a Go binary and monitors stderr output from the binary for a panic. When it find a panic, it executes a user-defined handler function. Stdout, stderr, stdin, signals, and exit codes continue to work as normal, making the existence of panicwrap mostly invisble to the end user until a panic actually occurs. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783899: fixed in liblog-any-perl 1.032-1
On Fri, 01 May 2015 19:35:00 + gregor herrmann gre...@debian.org wrote: liblog-any-perl (1.032-1) unstable; urgency=medium . * Team upload. . * Add Breaks/Replaces/Provides on liblog-any-adapter-perl. liblog-any-adapter-perl was merged into liblog-any-perl. (Closes: #783899) Sounds like you should file a RM bug against ftp.debian.org for liblog-any-adapter-perl. Emilio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785082: debdelta: service unavailable since months
Package: debdelta Version: 0.55 Severity: important Since months now, the debdelta servers have not been serving the delta packages. All I get is the followng error: rrs@ril:/var/tmp/linux-upstream_GIT (stable-40)$ sudo debdelta-upgrade Connection error (fatal): : debdeltas.debian.net Delta is not downloadable (timed out None):http://debdeltas.debian.net/debian-deltas/pool/main/b/bash-completion/bash-completion_1%3a2.1-4_1%3a2.1-4.1_all.debdelta Delta is not downloadable (None None):http://debdeltas.debian.net/debian-deltas/pool/main/a/atk1.0/gir1.2-atk-1.0_2.14.0-1_2.16.0-2_amd64.debdelta Delta is not downloadable (None None):http://debdeltas.debian.net/debian-deltas/pool/main/n/network-manager/gir1.2-networkmanager-1.0_1.0.0-5_1.0.2-2_amd64.debdelta Delta is not downloadable (None None):http://debdeltas.debian.net/debian-deltas/pool/main/n/network-manager-applet/gir1.2-nmgtk-1.0_1.0.0-3_1.0.2-1_amd64.debdelta Delta is not downloadable (None None):http://debdeltas.debian.net/debian-deltas/pool/main/r/rhythmbox/gir1.2-rb-3.0_3.1-1_3.2.1-1_amd64.debdelta Delta is not downloadable (None None):http://debdeltas.debian.net/debian-deltas/pool/main/g/git-buildpackage/git-buildpackage_0.6.26_0.6.27_all.debdelta Delta is not downloadable (None None):http://debdeltas.debian.net/debian-deltas/pool/main/g/gnupg/gnupg_1.4.18-7_1.4.19-2_amd64.debdelta Delta is not downloadable (None None):http://debdeltas.debian.net/debian-deltas/pool/main/g/gnupg/gpgv_1.4.18-7_1.4.19-2_amd64.debdelta Delta is not downloadable (None None):http://debdeltas.debian.net/debian-deltas/pool/main/liba/libassuan/libassuan0_2.1.2-2_2.2.0-2_amd64.debdelta Delta is not downloadable (None None):http://debdeltas.debian.net/debian-deltas/pool/main/a/atk1.0/libatk1.0-0_2.14.0-1_2.16.0-2_amd64.debdelta Delta is not downloadable (None None):http://debdeltas.debian.net/debian-deltas/pool/main/a/atk1.0/libatk1.0-data_2.14.0-1_2.16.0-2_all.debdelta Delta is not downloadable (None None):http://debdeltas.debian.net/debian-deltas/pool/main/liba/libav/libavcodec56_6%3a11.3-2_6%3a11.3-3+b1_amd64.debdelta Delta is not downloadable (None None):http://debdeltas.debian.net/debian-deltas/pool/main/liba/libav/libavdevice55_6%3a11.3-2_6%3a11.3-3+b1_amd64.debdelta Delta is not downloadable (None None):http://debdeltas.debian.net/debian-deltas/pool/main/liba/libav/libavformat56_6%3a11.3-2_6%3a11.3-3+b1_amd64.debdelta Delta is not downloadable (None None):http://debdeltas.debian.net/debian-deltas/pool/main/liba/libav/libavresample2_6%3a11.3-2_6%3a11.3-3+b1_amd64.debdelta Delta is not downloadable (None None):http://debdeltas.debian.net/debian-deltas/pool/main/liba/libav/libavutil54_6%3a11.3-2_6%3a11.3-3+b1_amd64.debdelta Delta is not downloadable (None None):http://debdeltas.debian.net/debian-deltas/pool/main/libc/libcap-ng/libcap-ng0_0.7.4-2_0.7.4-3_amd64.debdelta Delta is not downloadable (None None):http://debdeltas.debian.net/debian-deltas/pool/main/libc/libcpan-meta-perl/libcpan-meta-perl_2.142690-1_2.150001-1_all.debdelta Delta is not downloadable (None None):http://debdeltas.debian.net/debian-deltas/pool/main/d/djvulibre/libdjvulibre-text_3.5.25.4-4_3.5.27.1-1_all.debdelta Delta is not downloadable (None None):http://debdeltas.debian.net/debian-deltas/pool/main/d/djvulibre/libdjvulibre21_3.5.25.4-4+b1_3.5.27.1-1_amd64.debdelta Delta is not downloadable (None None):http://debdeltas.debian.net/debian-deltas/pool/main/libe/libestr/libestr0_0.1.9-1.1_0.1.10-1_amd64.debdelta Delta is not downloadable (None None):http://debdeltas.debian.net/debian-deltas/pool/main/g/glibmm2.4/libglibmm-2.4-1c2a_2.42.0-1_2.44.0-1_amd64.debdelta Delta is not downloadable (None None):http://debdeltas.debian.net/debian-deltas/pool/main/g/gnutls28/libgnutls-deb0-28_3.3.14-2_3.3.15-2_amd64.debdelta Delta is not downloadable (None None):http://debdeltas.debian.net/debian-deltas/pool/main/g/gnutls28/libgnutls-deb0-28_3.3.14-2_3.3.15-2_i386.debdelta Delta is not downloadable (None None):http://debdeltas.debian.net/debian-deltas/pool/main/g/gnutls28/libgnutls-openssl27_3.3.14-2_3.3.15-2_amd64.debdelta Delta is not downloadable (None None):http://debdeltas.debian.net/debian-deltas/pool/main/i/icu/libicu52_52.1-8_52.1-9_amd64.debdelta Delta is not downloadable (None None):http://debdeltas.debian.net/debian-deltas/pool/main/i/icu/libicu52_52.1-8_52.1-9_i386.debdelta
Bug#785084: lintian: backports-changes-missing obsolete, -v option no longer required
Package: lintian Version: 2.5.30+deb8u4 Severity: normal Dear Maintainer, The backports-changes-missing tag can now be considered obsolete, as the -v option is no longer required for a package to be accepted into backports (it's merely recommended now)[1][2]. Please either remove this tag, or downgrade the severity (wishlist/pedantic?). Regards, Vincent [1] https://lists.debian.org/debian-backports-announce/2015/04/msg0.html [2] http://backports.debian.org/Contribute/#index6h3 -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (700, 'testing'), (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.18-3-vclaptop-amd64 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages lintian depends on: ii binutils 2.25-7 ii bzip2 1.0.6-7+b3 ii diffstat 1.58-1 ii file 1:5.22+15-2 ii gettext0.19.3-2 ii hardening-includes 2.7 ii intltool-debian0.35.0+20060710.2 ii libapt-pkg-perl0.1.29+b2 ii libarchive-zip-perl1.39-1 ii libclass-accessor-perl 0.34-1 ii libclone-perl 0.37-1+b1 ii libdpkg-perl 1.17.25 ii libemail-valid-perl1.195-1 ii libfile-basedir-perl 0.03-1 ii libipc-run-perl0.92-1 ii liblist-moreutils-perl 0.410-1 ii libparse-debianchangelog-perl 1.2.0-1.1 ii libtext-levenshtein-perl 0.11-1 ii libtimedate-perl 2.3000-2 ii liburi-perl1.64-1 ii man-db 2.7.0.2-5 ii patchutils 0.3.3-1 ii perl [libdigest-sha-perl] 5.20.2-4 ii t1utils1.38-4 Versions of packages lintian recommends: ii libautodie-perl 2.25-1 ii libperlio-gzip-perl 0.18-3+b1 ii perl5.20.2-4 ii perl-modules [libautodie-perl] 5.20.2-4 Versions of packages lintian suggests: pn binutils-multiarch none ii dpkg-dev 1.17.25 ii libhtml-parser-perl3.71-1+b3 ii libtext-template-perl 1.46-1 ii libyaml-perl 1.13-1 ii xz-utils 5.1.1alpha+20120614-2+b3 -- 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#780359: Options w.r.t. libcgal11 transition
On Mon, May 11, 2015 at 11:35 PM, Joachim Reichel joachim.reic...@gmx.de wrote: Hi, dolfin is now the only reverse dependency holding up the libcgal11 transition. What are the options? (1) Fix dolfin without causing another transition (2) Remove dolfin from testing (3) Upload 1.5.0-1 from experimental to unstable This will be the correct solution IMO. I will do that now. Johannes (4) ...? (1) I don't know the details but it seems to me that this is not easy. (3) This causes another transition, but the only reverse dependencies of the binary packages of dolfin are python-viper (plus the meta packages fenics, science-mathematics and science-mathematics-dev). Rebuilding python-viper against dolfin 1.5.0-1 worked without problems. Maybe this additional transition isn't that bad (apart from the delay)? BTW does anyone understand why dolfin does not appear in the list of autoremovals? The bug is release-critical and not fixed in unstable/testing, only experimental. Joachim -- debian-science-maintainers mailing list debian-science-maintain...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780359: Options w.r.t. libcgal11 transition
On 2015-05-12 09:07, Johannes Ring wrote: On Mon, May 11, 2015 at 11:35 PM, Joachim Reichel joachim.reic...@gmx.de wrote: Hi, dolfin is now the only reverse dependency holding up the libcgal11 transition. What are the options? (1) Fix dolfin without causing another transition (2) Remove dolfin from testing (3) Upload 1.5.0-1 from experimental to unstable This will be the correct solution IMO. I will do that now. No, please do NOT do that now. It is the correct long-term solution, but it will entangle the cgal transition. Wait until britney has a chance to sort it out. -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 directhex i have six years of solaris sysadmin experience, from 8-10. i am well qualified to say it is made from bonghits layered on top of bonghits -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768983: ITP: carbon-c-relay -- status?
Hi Filippo, the package is at https://anonscm.debian.org/cgit/collab-maint/carbon-c-relay.git/ and upstream has released 0.40 yesterday, I think an upload might happen in the next two weeks! If you are interested though feel free to go ahead, I'll be fairly busy at work at least until end of May what I've done - and I hope you don't mind: - moved the carbon-c-relay config to /etc/carbon. Thats where the config lived from the inofficial packaging. - added a defaults file for the init script and the systemd service so you can easily pass options to the daemon - upgraded to 0.40 - fixed GIT_VERSION in Makefile I've added branches for wheezy and jessie backports. If thats all fine for you please let me know and I'll upload it to unstable. cheers, bernd -- Mit freundlichen Grüßen Bernd Zeimetz Systems Engineer Debian Developer conova communications GmbH Web| http://www.conova.com/ E-Mail | b.zeim...@conova.com Zentrale Salzburg Karolingerstraße 36A 5020 Salzburg Tel | +43 (0) 662 22 00 - 313 Fax | +43 (0) 662 22 00 - 209 Es gelten die Allgemeinen Geschäftsbedingungen der conova communications GmbH, http://www.conova.com/de/agb/ smime.p7s Description: S/MIME cryptographic signature
Bug#785088: gyrus: still build-depends on libgnet-dev
Package: gyrus Version: 0.3.10-1 Severity: important User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs gnet Your package stopped depending on libgnet, but it still build-depends on libgnet-dev. Please fix that. Emilio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784983: fatrace: some archs/kernels define O_LARGEFILE
On Tue, 12 May 2015, Martin Pitt wrote: Hello Cristian, Martin, Cristian Ionescu-Idbohrn [2015-05-11 20:10 +0200]: After compiling with 'CFLAGS += -save-temps' and looking at fatrace.i, I see this: $ grep O_LARGEFILE fatrace.i #define O_LARGEFILE 0x2000 #define KERNEL_O_LARGEFILE 0010 O_LARGEFILE set to 0x2000 (in /usr/include/bits/fcntl.h), but replaced with 0010. My patch makes it both build and run, and produce reasonable results. Ah, so I guess we might need something like if O_LARGEFILE is nonzero, use it, otherwise KERNEL_O_LARGEFILE? Yes, something like that. Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785016: GnuTLS: received alert [70]: Error in protocol version
On Tue, May 12, 2015 at 9:00 AM, Noël Köthe n...@debian.org wrote: please use reportbug to report your bugs because it includes more information about your system. The missing information is which Debian version you are using (stable, testing,...) and what versions of the dependencies are installed. I can guess but this might be wrong. jessie/stable on x86_64 (up-to-date). The wget version is accurate. Sorry for the missing information. Let me know if you need anything else to reproduce on your side, or a moore verbose output. Regards -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784934: Cannot edit same tag of two songs when it is only present in one
On 2015-05-11 12:37, Christoph Reiter wrote: You can click the write icon in the first column instead for now. Thanks for that hint. I always thought the icon is only display, not an action :~) I'll close this bug report then. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728676: ITP: ddrescueview -- Graphical viewer for GNU ddrescue log files
Package: wnpp Severity: wishlist * Package name: ddrescueview Version : 0.4 Upstream Author : Martin Bittermann martinbitterm...@gmx.de * URL : http://ddrescueview.sourceforge.net/ * License : GPL-3.0+ Programming Lang: Object Pascal / Lazarus Description : Graphical viewer for GNU ddrescue log files This small tool allows the user to graphically examine ddrescue's log files in a user friendly GUI application. The Main window displays a block grid with each block's color representing the block types it contains. Many people know this type of view from defragmentation programs. . GNU ddrescue [1] is a data recovery tool, already packaged in Debian as gddrescue [2]. . The ddrescueview package will be maintained by the Debian Pascal packaging team and a git repository has already been created on Alioth [3]. [1] http://www.gnu.org/software/ddrescue/ddrescue.html [2] https://packages.qa.debian.org/g/gddrescue.html [3] http://anonscm.debian.org/cgit/pkg-pascal/ddrescueview.git Regards Graham -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784397: devscripts: [debchange] Support un-finalised trailer line for UNRELEASED changelog entry
Control: retitle -1 devscripts: [debchange] Support un-finalised trailer line for UNRELEASED changelog entry On 06-May-2015, Ben Finney wrote: Instead, ‘debchange --release’ should recognise an unfinalised trailer line as valid for this action, and replace the line with a finalised trailer line for the release. On 11-May-2015, Barry Warsaw wrote: Note that the problem isn't only in debchange. dpkg-buildpackage also seems to suffer from unfinalized trailers: I think you're describing behaviour different from this report. ‘dpkg-buildpackage’ expects the changelog entry to be finalised. That's right and proper, and should not be changed for this bug report. ‘debchange --release’ should handle an unfinalised changelog entry, because the whole point of that action is to *alter* the changelog entry to finalise it for release. -- \ “A thing moderately good is not so good as it ought to be. | `\Moderation in temper is always a virtue; but moderation in | _o__) principle is always a vice.” —Thomas Paine | Ben Finney b...@benfinney.id.au signature.asc Description: Digital signature
Bug#785035: [Help] Re: Bug#785035: ugene: FTBFS on amd64
Hi folks, Ugine is in a quite bad state. We are lagging behind upstream and it has gathered some important errors now. I currently do not feel able to care for this one reported by Lisandro (thanks for reporting BTW). Is there anybody who might be able to spent some time into this - probably by taking the latest upstream and see what can be done about this error on the latest code base? Kind regards Andreas. On Mon, May 11, 2015 at 02:52:13PM -0300, Lisandro Damián Nicanor Pérez Meyer wrote: Source: ugene Version: 1.12.3+dfsg-1 Severity: serious Justification: FTBFS on amd64 Hi! While looking at #784382 I tried to compile ugene on a clean sid chroot using sbuild and it FTBFS. I'm attaching the build log. Kinds regards, Lisandro. -- System Information: Debian Release: 8.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) ___ Debian-med-packaging mailing list debian-med-packag...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780359: Options w.r.t. libcgal11 transition
On Tue, May 12, 2015 at 10:07 AM, Johannes Ring joha...@simula.no wrote: On Mon, May 11, 2015 at 11:35 PM, Joachim Reichel joachim.reic...@gmx.de wrote: Hi, dolfin is now the only reverse dependency holding up the libcgal11 transition. What are the options? (1) Fix dolfin without causing another transition (2) Remove dolfin from testing (3) Upload 1.5.0-1 from experimental to unstable This will be the correct solution IMO. I will do that now. Sorry for asking, but how should I upload to unstable when the package is already in experimental. I haven't done that before. Johannes Johannes (4) ...? (1) I don't know the details but it seems to me that this is not easy. (3) This causes another transition, but the only reverse dependencies of the binary packages of dolfin are python-viper (plus the meta packages fenics, science-mathematics and science-mathematics-dev). Rebuilding python-viper against dolfin 1.5.0-1 worked without problems. Maybe this additional transition isn't that bad (apart from the delay)? BTW does anyone understand why dolfin does not appear in the list of autoremovals? The bug is release-critical and not fixed in unstable/testing, only experimental. Joachim -- debian-science-maintainers mailing list debian-science-maintain...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785055: [Pkg-xfce-devel] Bug#785055: lightdm-gtk-greeter: white screen until I click a mouse button, with 2 screens
On mar., 2015-05-12 at 10:00 +0200, Vincent Lefevre wrote: On 2015-05-12 08:11:26 +0200, Yves-Alexis Perez wrote: On mar., 2015-05-12 at 00:04 +0200, Vincent Lefevre wrote: On 2015-05-11 23:23:47 +0200, Vincent Lefevre wrote: Package: lightdm-gtk-greeter Version: 2.0.0-2 Severity: important Tags: upstream Forwarded: https://bugs.launchpad.net/ubuntu/+source/lightdm-gtk-greeter/+bug/1426664 or perhaps https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1410406 I also see a 100% CPU usage (but the screen is white, not black). Does setting active-monitor=0 fix your problem? Yes, it does. Thanks for the confirmation, so at least you have a workaround for now (as a side note, I didn't experience that for now on multi-monitor setups I have). Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#783899: fixed in liblog-any-perl 1.032-1
On Tue, 12 May 2015 10:20:45 +0200, Emilio Pozuelo Monfort wrote: On Fri, 01 May 2015 19:35:00 + gregor herrmann gre...@debian.org wrote: liblog-any-perl (1.032-1) unstable; urgency=medium . * Team upload. . * Add Breaks/Replaces/Provides on liblog-any-adapter-perl. liblog-any-adapter-perl was merged into liblog-any-perl. (Closes: #783899) Sounds like you should file a RM bug against ftp.debian.org for liblog-any-adapter-perl. Thanks for the reminder, this somehow fell off of my TODO list :/ Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- BOFH excuse #18: excess surge protection -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784382: Patch attached
Hi Lisandro, thanks for your bugs against Ugene. I took this one over in SVN but we need to fix the FTBFS bug as well. I hope this can be done soon. BTW, Debian Med repository has set ACLs so any DD can commit directly. Kind regards Andreas. On Mon, May 11, 2015 at 02:41:25PM -0300, Lisandro Damián Nicanor Pérez Meyer wrote: tag 784382 + patch thanks Hi! I'm attaching a patch to solve this issue. -- Si vives cada día de tu vida como si fuera el último, algún día realmente tendrás razón. Steve Jobs Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ diff --git a/debian/changelog b/debian/changelog index 7a8bcae..fca5baa 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +ugene (1.12.3+dfsg-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Remove non necessary harcoded dependencies on transitional +packages (Closes: #784382). + + -- Lisandro Damián Nicanor Pérez Meyer lisan...@debian.org Mon, 11 May 2015 13:54:15 -0300 + ugene (1.12.3+dfsg-1) unstable; urgency=low [ Andreas Tille ] diff --git a/debian/control b/debian/control index e5bfa8b..deb2d53 100644 --- a/debian/control +++ b/debian/control @@ -24,8 +24,6 @@ Homepage: http://ugene.unipro.ru Package: ugene Architecture: any Depends: ${shlibs:Depends}, - libqt4-gui, - libqt4-core, ugene-data, ${misc:Depends} Description: integrated bioinformatics toolkit ___ Debian-med-packaging mailing list debian-med-packag...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785083: ITP: golang-loggo -- Alternative logging library for Go
Package: wnpp Severity: wishlist Owner: Tim Potter t...@hp.com * Package name: golang-loggo Version : 0.0~git20150330 Upstream Author : Tim Penhey * URL : https://github.com/juju/loggo * License : LGPL-3 Programming Lang: Go Description : Alternative logging library for Go Loggo is an alternative logging library for Go. It doesn't use the built-in Go log library, but instead offers a replacement. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785085: mksh: Misleading note in manpage about equality test
Package: mksh Version: 50d-5 Severity: minor Dear Maintainer, here is a note in manpage about [ $foo = bar ] equality test: $ MANWIDTH=78 LC_ALL=C man mksh 2/dev/null 2 | grep -A5 'A common mistake is to use' Note: A common mistake is to use ``if [ $foo = bar ]'' which fails if parameter ``foo'' is NULL or unset, if it has embedded spaces (i.e. IFS octets), or if it is a unary operator like '!' or '-n'. Use tests like ``if [ x$foo = xbar ]'' instead, or the double-bracket operator ``if [[ $foo = bar ]]'' or, to avoid pattern matching (see [[ above): ``if [[ $foo = $bar ]]'' the proposed [ x$foo = xbar ] is correct but with redundant x character; this x looks odd and attracts attention, while proper quotation is the point in order to make it clear it should be something like [ $foo = bar ] -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: armhf (armv7l) Foreign Architectures: armel Kernel: Linux 3.0.35-ygrex-fx6-6.3+ (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mksh depends on: ii libc6 2.19-18 mksh recommends no packages. Versions of packages mksh suggests: ii ed 1.10-2 -- 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#776512: function InsertData() is defined twice: installation is broken
Package: mantis Version: 1.2.18-1 Severity: grave Justification: Makes the package in question unusable for new installations. Followup-For: Bug #776512 Control: tags -1 +patch Dear Maintainer, I can confirm that the attached patch makes (at least) the install page showing up. Now continueing with configuration : Raising severity as this breaks the package for new installs. -- tobi -- System Information: Debian Release: jessie/sid APT prefers stable APT policy: (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mantis depends on: ii apache2-utils 2.4.10-9 ii cdebconf [debconf-2.0] 0.185 ii debconf [debconf-2.0] 1.5.52 ii libjs-prototype 1.7.1-3 ii libjs-scriptaculous 1.9.0-2 ii libnusoap-php 0.9.5-2 ii libphp-adodb5.15-1 ii libphp-phpmailer5.1-1 ii lighttpd [httpd]1.4.35-4.1 ii php5-cli5.6.5+dfsg-1 ii ucf 3.0027+nmu1 Versions of packages mantis recommends: ii mysql-client 5.5.43-0+deb7u1 ii mysql-client-5.5 [mysql-client] 5.5.43-0+deb7u1 ii php5-mysql 5.6.5+dfsg-1 Versions of packages mantis suggests: ii mysql-server 5.5.43-0+deb7u1 ii php5-cli 5.6.5+dfsg-1 -- debconf information excluded -- debsums errors found: debsums: changed file /usr/share/mantis/www/admin/install.php (from mantis package) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784854: RFS: gtk3-engines-unico/1.0.3+14.04.20140109+repack1-1 [ITA] [RC]
Control: tag -1 + moreinfo Hi James, On Sun, May 10, 2015 at 11:52 AM, James Lu glol...@hotmail.com wrote: Hi, Okay. Forget what I said about quilt, I don't think it'd fix this particular issue either. Right now, the problem is in the original source (aka the .orig.tar). The INSTALL file isn't even installed in the final binary, but just having a symlink in the original source is enough to make Lintian complain. Adding a debian/clean file only removes the INSTALL file from the extracted tree, but not the .orig.tar.gz. I could add a Lintian override if this is appropriate. Just from what you've said above, I'd ignore the lintian error entirely; if INSTALL is never used during the build process or installed into any of the binary packages produced by your source package, then source-contains-unsafe-symlink is quite harmless. It _is_ a valid lintian error though, since the orig tarball upstream presumably contains an INSTALL file symlinked above the root of the source package, and removing it via debian/clean doesn't change that. Where did you obtain this orig tarball? I can't seem to find a tarball versioned as 1.0.3+14.04.20140109 at [1]; if you actually are rolling your own tarball instead of using one provided upstream, then why not get rid of that symlink in your tarball? Also, this may seem to be a formality, but is this package actually orphaned? Neither the maintainer nor the MIA team filed #717044; a random user deciding to ITA the package out of the blue is more or less hijacking the package. Please follow the steps outlined in devref 5.9.4/5.9.5 [2] to properly orphan a package and adopt it. Regards, Vincent [1] https://launchpad.net/unico [2] https://www.debian.org/doc/manuals/developers-reference/pkgs.html#orphaning -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785087: ITP: golang-go-simplejson -- Go package to interact with arbitrary JSON
Package: wnpp Severity: wishlist Owner: Tim Potter t...@hp.com * Package name: golang-go-simplejson Version : 0.4.3~git20150401 Upstream Author : Matt Reiferson * URL : https://github.com/bitly/go-simplejson * License : MIT Programming Lang: Go Description : Go package to interact with arbitrary JSON go-simplejson is a Go package to read, write and assert facts about arbitrary JSON. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785065: vdso32 fails to built on ppc64el
On Tue, 2015-05-12 at 15:55 +0200, Matthias Klose wrote: that should be fixed on the kernel side by removing this code. there never was a powerpcle userland support. I agree we have no use for this code. Unfortunately it is currently non-optional. If this is not possible in the short term, then we can re-enable this for unstable for some time. Please do. Ben. -- Ben Hutchings For every action, there is an equal and opposite criticism. - Harrison signature.asc Description: This is a digitally signed message part
Bug#785118: coreutils: date : format %p %P do not work properly
Hi, [CC'ing Keld with whom this issue was discussed some years ago] On 2015-05-12 18:49, Pádraig Brady wrote: On 12/05/15 16:40, Pádraig Brady wrote: On 12/05/15 14:51, Michael Stone wrote: On Tue, May 12, 2015 at 03:36:17PM +0200, op...@mumm.ac.be wrote: I'm just upgrading my server from debian 7 (wheezy) to debian 8 (jessie) and several of my scripts are not working anymore. After some tests, it turns out that the problem likely comes from the fact the 'date' function does not work as expected. In wheezy, the command line date /bin/date +%Y%m%d.%p would have returned 20150512.PM In jessie, the same command line returns 20150512. omitting PM. As a consequence of this omission, my scripts are crashing. Have you got any idea why this is happening? I can't reproduce it: /bin/date +%Y%m%d.%p 20150512.AM If I had to guess, I'd say it's a locale issue. What does env LANG=C LC_ALL=C /bin/date +%Y%m%d.%p return? If that works, what does locale return when run by itself? %p is blank in many locales unfortunately. You can see the am_pm vary with these commands: $ LC_ALL=en_IE locale -k LC_TIME $ LC_TIME=C locale -k LC_TIME $ LC_ALL=zh_CN.utf8 date +%p 下午 $ LC_ALL=en_US.utf8 date +%p PM $ LC_ALL=en_US date +%p PM locales with blank am_pm should be fixed up to allow one to get an explicit 12 hour format like `date +%I:%m%p` for example. Note some locales (like en_GB for example) default to 24 hour (t_fmt=%T), and also provide an am_pm entry, which is the correct behavior in my opinion. I see that https://sourceware.org/glibc/wiki/Locales states: am_pm and t_fmt_ampm - should be empty if using 24 hour time Marko, that seems incorrect? At least am_pm should be populated to allow users to generate 12 hour time with strftime? I can't find references to the discussion I had with Keld earlier but the rationale for not populating it was along the lines: 1) am_pm should be populated only if AM/PM convention is used to signal applications they should not try to print them when using them is unwanted. Seems that only the locale(5) commit messages, not the page itself, spell this out: http://git.kernel.org/cgit/docs/man-pages/man-pages.git/commit/?id=b5d4168adfb426f45108ac2bf7c8b17b126b07a1 http://git.kernel.org/cgit/docs/man-pages/man-pages.git/commit/?id=0c2dbad182e40db2ca47128f229ca7dbd83e179f 2) what unwanted means is that in many cases 12 hour time with AM/PM notation is alien thus generating such time representation under those locales would be illogical (e.g. 5.34 ip. in Finnish context is completely unnatural). The same goes for various name_* keywords in LC_NAME, defining them for locales where they are not used would not allow signaling applications that under those locales their usage is unwanted. Thanks, -- Marko Myllynen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733678: inkscape: Provide a -dbg package with debugging symbols
I just noticed, I can import files (File - Import) without errors. So there's kind of a workaround... - Roland -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777084: open-iscsi-udeb: please build the udeb on x32
Control: tag -1 + moreinfo I just looked at this and am a bit confused w.r.t. x32: The udeb depends on iscsi-modules, which is built from the linux kernel source package. However, looking at a recent build log on x32 (and also current sid source for the linux package), it doesn't appear to be the case that ANY udeb is built from the kernel on x32. This in turn means that even if the open-iscsi udeb is built on x32, it will not be installable in the installer. (I added a comment to debian/control to make this clear for the future, will be part of the next upload.) I haven't followed the x32 port myself, and it seems really weird to me that NO module udebs are built at all for that architecture, so could you please clarify what's going on there? Thanks! Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785065: vdso32 fails to built on ppc64el
On Tue, 2015-05-12 at 17:21 +0100, Ben Hutchings wrote: On Tue, 2015-05-12 at 15:55 +0200, Matthias Klose wrote: that should be fixed on the kernel side by removing this code. there never was a powerpcle userland support. I agree we have no use for this code. Unfortunately it is currently non-optional. [...] I was able to hack out all the 32-bit vDOS along with all 32-bit userland compatibility, but that doesn't solve the problem: a 64-bit kernel apparently still boots in 32-bit mode. Ben. -- Ben Hutchings For every action, there is an equal and opposite criticism. - Harrison signature.asc Description: This is a digitally signed message part
Bug#777068: RFS: libtoxcore/0+git20150203-1
You have Vcs-* fields commented out in d/control. Uncomment them (creating the repos if they don't exist) or remove them. Is License: GPL-3 in d/copyright a typo? Looks like it should be GPL-3+. Why are build-time tests disabled? -- WBR, wRAR signature.asc Description: Digital signature
Bug#785143: rally: Screwed debconf templates
Source: rally Severity: normal Tags: patch The debconf template that includes an enumeration is completely messed up because no hard formatting is done. Patch attached. -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- rally.templates 2015-04-29 22:04:42.0 +0200 +++ rally.templates.new 2015-05-12 19:57:19.952945921 +0200 @@ -14,10 +14,10 @@ No database has been set up for rally to use. Before continuing, you should make sure you have the following information: . - * the type of database that you want to use; - * the database server hostname (that server must allow TCP connections from this - machine); - * a username and password to access the database. + * the type of database that you want to use; + * the database server hostname (that server must allow TCP +connections from this machine); + * a username and password to access the database. . If some of these requirements are missing, do not choose this option and run with regular SQLite support.
Bug#785071: pto2mk gone, breaks debian/tests/simple.pano.test
Control: tags -1 pending On 2015-05-12 Martin Pitt mp...@debian.org wrote: Package: hugin Version: 2015.0.0~beta1+dfsg-1 User: autopkgtest-de...@lists.alioth.debian.org Usertags: autopkgtest Hello, Version 2015.0.0~beta1+dfsg-1 apparently dropped the pto2mk tool. But debian/tests/simple.pano.test still tries to call it and thus hugin's autopkgtest now fails: http://ci.debian.net/data/packages/unstable/amd64/h/hugin/latest-autopkgtest/log.gz What's the replacement for pto2mk? Can you please adjust the test to the replacement? Hello, I have seen that (too late for beta2) and it is already fixed in GIT. Thanks for keeping an eye on these issues. cu Andreas http://anonscm.debian.org/cgit/pkg-phototools/hugin.git/commit/?id=477347385b6b59ccff6a645345846bdf39be68a5 -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#742723: Fwd: Re: CrashMail II doesn't work on debian jessie
-- Forwarded Message -- Subject: Re: CrashMail II doesn't work on debian jessie Date: Wednesday, May 06, 2015, 05:40:48 PM From: VS tvw...@yandex.ru To: j...@rocasa.us 06.05.2015 16:35, Robert James Clay пишет: On Monday, May 04, 2015 05:30:04 PM VS wrote: 04.05.2015 16:37, Robert James Clay пишет: CrashMail II doesn't work on debian jessie. Error: Failed to read message #1 in JAM messagebase /home/fido/areas/3bfe0095 So, this was with version 1.5? And was this the 64 bit version? I ask because I have seen or have heard of issues with the 64 bit version that do not seem to be in the 32 bit version. Yes, that is 64 bit Debian Jessie. $ crashmail version This is CrashMail II version 1.5 Note that there is already a bug open in Debian [1] and upstream [2] about issues with operations on a 64 bit system. I you have not already done so, I would appreciate it you check it's operation on an 32 bit system. I'm also setting up both 32 and 64 bit systems (hardware as all as LXCs.) but I would appreciate knowing how others are seeing it as as well. It's not easy for me. Sorry. I'll try to do it, but can't promise it will be soon. Also I can't switch on debug mode for logging. You mean, by setting the LogLevel to 6? Yes If so; what are you expecting that you are not seeing? I haven't noticed big difference between LogLevel 3 and LogLevel 6. That is why I've decided LogLevel 6 didn't work. Looking at the code again that LogLevel doesn't actually seem to be used much... (Only found one instance.) If you have suggestions about where such should be, please let me know. Or add a ticket about it at the upstream project. Note also that with 1.5-1 version of the package, there is also a package available with the debugging symbols for it, crashmail-dbg. By the way - I have my old JAM message base from 2002 year. It was made by crashecho (not crashmail). There weren't any errors when I worked with it in 2002. Was that on a 32 bit system? Yes But now, when I scan it by crashmail II and have this error for the each echo-conference in my JAM Base - Failed to read message #2 (#3,#4,#5...#11) in JAM messagebase /home/fido/areas/3bfe0095. Messages from #2 to #5 have this error but messages #1 and #11 ... #20 are OK. I've thought - my jam messagebase is broken. And simply have made one message by GoldedPlus and MSGED TE in a new JAM base. I got the same error - Failed to read message #1 in JAM messagebase /home/fido/areas/3bfe0095 That is why I think - that is problem of crashmail II. Rather than it being related to the Debian packaging? I think - that is the problem of original crashmail II, not deb package of it. Because I've compiled crashmail II by myself from the source and got the same error. Best regards, Vladislav - -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784665: Patch for unittest-cpp
I'd be happy to upload if you tell me to. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785118: coreutils: date : format %p %P do not work properly
On 12/05/15 17:55, Marko Myllynen wrote: Hi, [CC'ing Keld with whom this issue was discussed some years ago] On 2015-05-12 18:49, Pádraig Brady wrote: On 12/05/15 16:40, Pádraig Brady wrote: On 12/05/15 14:51, Michael Stone wrote: On Tue, May 12, 2015 at 03:36:17PM +0200, op...@mumm.ac.be wrote: I'm just upgrading my server from debian 7 (wheezy) to debian 8 (jessie) and several of my scripts are not working anymore. After some tests, it turns out that the problem likely comes from the fact the 'date' function does not work as expected. In wheezy, the command line date /bin/date +%Y%m%d.%p would have returned 20150512.PM In jessie, the same command line returns 20150512. omitting PM. As a consequence of this omission, my scripts are crashing. Have you got any idea why this is happening? I can't reproduce it: /bin/date +%Y%m%d.%p 20150512.AM If I had to guess, I'd say it's a locale issue. What does env LANG=C LC_ALL=C /bin/date +%Y%m%d.%p return? If that works, what does locale return when run by itself? %p is blank in many locales unfortunately. You can see the am_pm vary with these commands: $ LC_ALL=en_IE locale -k LC_TIME $ LC_TIME=C locale -k LC_TIME $ LC_ALL=zh_CN.utf8 date +%p 下午 $ LC_ALL=en_US.utf8 date +%p PM $ LC_ALL=en_US date +%p PM locales with blank am_pm should be fixed up to allow one to get an explicit 12 hour format like `date +%I:%m%p` for example. Note some locales (like en_GB for example) default to 24 hour (t_fmt=%T), and also provide an am_pm entry, which is the correct behavior in my opinion. I see that https://sourceware.org/glibc/wiki/Locales states: am_pm and t_fmt_ampm - should be empty if using 24 hour time Marko, that seems incorrect? At least am_pm should be populated to allow users to generate 12 hour time with strftime? I can't find references to the discussion I had with Keld earlier but the rationale for not populating it was along the lines: 1) am_pm should be populated only if AM/PM convention is used to signal applications they should not try to print them when using them is unwanted. Seems that only the locale(5) commit messages, not the page itself, spell this out: http://git.kernel.org/cgit/docs/man-pages/man-pages.git/commit/?id=b5d4168adfb426f45108ac2bf7c8b17b126b07a1 http://git.kernel.org/cgit/docs/man-pages/man-pages.git/commit/?id=0c2dbad182e40db2ca47128f229ca7dbd83e179f 2) what unwanted means is that in many cases 12 hour time with AM/PM notation is alien thus generating such time representation under those locales would be illogical (e.g. 5.34 ip. in Finnish context is completely unnatural). The same goes for various name_* keywords in LC_NAME, defining them for locales where they are not used would not allow signaling applications that under those locales their usage is unwanted. Thanks for the info. Generally apps would not need to know whether to select between 12 and 24? Can't they just use the higher level (and POSIX defined) %X to get the appropriate default? I propose the wiki at least should be reworded to state that am_pm should be omitted only when it doesn't make any sense, like in Finland for example? Also we'll need to fix up some locales that may have blindly followed the existing advice. The 12h format is not appropriate for Ireland at least: $ LC_TIME=en_IE date +'def: %X | 12h: %r | 24h: %T' def: 18:19:52 | 12h: 06:19:52 | 24h: 18:19:52 cheers, Pádraig. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785144: [okular] zoom not working in presentation mode
Package: okular Version: 4:4.14.2-2 Severity: normal --- Please enter the report below this line. --- When in presentation mode, zoom (e.g. using ctrl and the mouse wheel) is not working. This is quite annoying when wanting to highlight small details in graphics in presentations, since one has to leave presentation mode to show the details, and then go back to presentation mode again. --- System information. --- Architecture: amd64 Kernel: Linux 3.16.0-4-amd64 Debian Release: stretch/sid 500 unstableftp.de.debian.org 500 testing ftp.de.debian.org 1 experimentalftp.de.debian.org --- Package information. --- Depends (Version) | Installed ===-+-= libokularcore4 (= 4:4.13.3-1) | kde-runtime ( 4:4.10) | 4:4.14.2-2 libc6 (= 2.14) | libfreetype6 (= 2.2.1) | libjpeg8(= 8c) | libkactivities6 (= 4:4.11) | libkdecore5 (= 4:4.11) | libkdeui5 (= 4:4.11) | libkexiv2-11 (= 4:4.10.2) | libkio5 (= 4:4.11) | libkparts4 (= 4:4.11) | libkprintutils4 (= 4:4.11) | libkpty4(= 4:4.11) | libphonon4 (= 4:4.6.0really4.3.80) | libpoppler-qt4-4(= 0.22.1) | libqca2 (= 2.0.2) | libqimageblitz4(= 1:0.0.4) | libqmobipocket1 (= 4:4.11.80) | libqt4-dbus(= 4:4.6.1) | libqt4-declarative (= 4:4.7.0~rc1) | libqt4-svg (= 4:4.5.3) | libqt4-xml (= 4:4.5.3) | libqtcore4 (= 4:4.8.0) | libqtgui4 (= 4:4.8.0) | libsolid4 (= 4:4.11) | libspectre1 (= 0.2.3) | libstdc++6 (= 4.1.1) | phonon | zlib1g (= 1:1.1.4) | Package's Recommends field is empty. Suggests (Version) | Installed -+-=== ghostscript | 9.06~dfsg-2 jovie| okular-extra-backends (= 4:4.13.3-1) | poppler-data | 0.4.7-1 texlive-binaries | 2014.20140926.35254-6 unrar| -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759544: please fix in jessie
On Sun, 10 May 2015, Meik Hellmund wrote: Please provide a patched version of nslcd for jessie-updates. I just upgraded a larger installation of Debian servers and desktop clients to jessie and was bitten by this bug. Progress on getting this fixed in jessie can be tracked at https://bugs.debian.org/785053 Thanks, -- -- arthur - adej...@debian.org - http://people.debian.org/~adejong -- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785140: mate-power-manager: It doesn't respond to pressing the power button
Package: mate-power-manager Version: 1.8.1+dfsg1-5 Severity: normal Dear Maintainer, When current workspaces does not contain active application window and then open and close any application then mate-power-manager doesn't respond to pressing the power button. -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mate-power-manager depends on: ii dbus-x111.8.16-1 ii libatk1.0-0 2.14.0-1 ii libc6 2.19-18 ii libcairo2 1.14.0-2.1 ii libcanberra-gtk00.30-2.1 ii libcanberra00.30-2.1 ii libdbus-1-3 1.8.16-1 ii libdbus-glib-1-20.102-1 ii libfontconfig1 2.11.0-6.3 ii libfreetype62.5.2-3 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-02.42.1-1 ii libgnome-keyring0 3.12.0-1+b1 ii libgtk2.0-0 2.24.25-3 ii libmate-panel-applet-4-11.8.1+dfsg1-3 ii libnotify4 0.7.6-2 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpangoft2-1.0-0 1.36.8-3 ii libunique-1.0-0 1.1.6-5 ii libupower-glib3 0.99.1-3.2 ii libx11-62:1.6.2-3 ii libxext62:1.3.3-1 ii libxrandr2 2:1.4.2-1+b1 ii libxrender1 1:0.9.8-1+b1 ii mate-notification-daemon [notification-daemon] 1.8.1-3 ii mate-power-manager-common 1.8.1+dfsg1-5 ii notification-daemon 0.7.6-2 ii policykit-1 0.105-8 ii systemd 215-17 ii upower 0.99.1-3.2 Versions of packages mate-power-manager recommends: ii udisks 1.0.5-1+b1 Versions of packages mate-power-manager suggests: ii mate-polkit 1.8.0+dfsg1-4 -- no debconf information ailov
Bug#785141: inkscape crashes when opening any files
Package: inkscape Version: 0.91-4 Severity: important Dear Maintainer, Since a recent update, when I try to open any files, Inkscape crashes with the error message Inkscape encountered an internal error and will close now. [Close Button]. On the terminal, I see: 8 $ inkscape ~/tmp/drawing.svg terminate called after throwing an instance of 'Glib::ConvertError' Emergency save activated! Emergency save completed. Inkscape will close now. If you can reproduce this crash, please file a bug at www.inkscape.org with a detailed Description of the steps leading to the crash, so we can fix it. 8 The respective drawing.svg is attached for reference (saving SVGs in Inkscape works as usual), though I was able to reproduce this behaviour with every single PDF/SVG/PS/... file I tried. Here is a gdb backtrace: (by the way, it would be _really nice_ to see #733678 fixed ;-)) 8 $ gdb --args inkscape ~/tmp/drawing.svg Reading symbols from inkscape...(no debugging symbols found)...done. (gdb) r Starting program: /usr/bin/inkscape /home/rohieb/tmp/drawing.svg [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. terminate called after throwing an instance of 'Glib::ConvertError' [New Thread 0x7fffe1dc2700 (LWP 13989)] [New Thread 0x7fffe3cc9700 (LWP 13988)] [New Thread 0x7fffe4723700 (LWP 13987)] Program received signal SIGABRT, Aborted. 0x7fffee8d5107 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 0x7fffee8d5107 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x7fffee8d64e8 in __GI_abort () at abort.c:89 #2 0x7fffef3ddb3d in __gnu_cxx::__verbose_terminate_handler () at ../../../../src/libstdc++-v3/libsupc++/vterminate.cc:95 #3 0x7fffef3dbbb6 in __cxxabiv1::__terminate (handler=optimized out) at ../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:47 #4 0x7fffef3dbc01 in std::terminate () at ../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:57 #5 0x7fffef3dbe19 in __cxxabiv1::__cxa_throw (obj=0x401e8f0, tinfo=0xd542b0 typeinfo for Glib::ConvertError, dest=0x754ff820 Glib::ConvertError::~ConvertError()) at ../../../../src/libstdc++-v3/libsupc++/eh_throw.cc:87 #6 0x754ff6a7 in Glib::ConvertError::throw_func (gobject=0x40c48b0) at convert.cc:322 #7 0x75510977 in Glib::Error::throw_exception (gobject=0x40c48b0) at error.cc:167 #8 0x754ff41d in Glib::filename_from_uri (uri=...) at convert.cc:256 #9 0x0052b3f1 in ?? () #10 0x0052c786 in ?? () #11 0x004c7fe9 in ?? () #12 0x004753a3 in ?? () #13 0x7fffee8c1b45 in __libc_start_main (main=0x456ad0, argc=2, argv=0x7fffe038, init=optimized out, fini=optimized out, rtld_fini=optimized out, stack_end=0x7fffe028) at libc-start.c:287 #14 0x00471a7f in ?? () (gdb) q 8 Symbol mappings are attached, it seems that stack frames #12-#9 are from /usr/bin/inkscape, and #8-#6 are in /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1.3.0. I have installed libglibmm-2.4-dbg, but was not able to step through Glib::filename_from_uri() properly due to optimized-out symbols. Thanks for looking into this. - Roland -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (200, 'testing'), (170, 'unstable'), (150, 'testing-proposed-updates'), (150, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages inkscape depends on: ii gconf-service 3.2.6-3 ii libaspell150.60.7~20110707-3 ii libatk1.0-02.14.0-1 ii libatkmm-1.6-1 2.22.7-2.1 ii libc6 2.19-18 ii libcairo2 1.14.0-2.1 ii libcairomm-1.0-1 1.10.0-1.1 ii libcdr-0.1-1 0.1.1-2 ii libexif12 0.6.21-2 ii libfontconfig1 2.11.0-6.3 ii libfreetype6 2.5.2-4 ii libgc1c2 1:7.2d-6.4 ii libgcc11:4.9.2-10 ii libgconf-2-4 3.2.6-3 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libglibmm-2.4-1c2a 2.42.0-1 ii libgnomevfs2-0 1:2.24.4-6+b1 ii libgomp1 4.9.2-10 ii libgsl0ldbl1.16+dfsg-2 ii libgtk2.0-02.24.25-3 ii libgtkmm-2.4-1c2a 1:2.24.4-1.1 ii libgtkspell0 2.0.16-1.1 ii libjpeg62-turbo1:1.3.1-12 ii liblcms2-2 2.6-3+b3 ii libmagick++-6.q16-58:6.8.9.9-5 ii libmagickcore-6.q16-2 8:6.8.9.9-5 ii libmagickwand-6.q16-2 8:6.8.9.9-5 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0
Bug#773802: [Packaging] Bug#773802: new upstream (2.1.10)
Daniel Baumann daniel.baum...@progress-technologies.net writes: retitle 773802 new upstream (2.1.12) thanks 2.1.12 is out. Note: 2.1.x is the development series of munin. There are more than a few bits and pieces missing from 2.1.12 one would expect in a munin master. The new web interface is _much_ nicer, though. :) -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784939: wings3d: I can't open/save file because both dialogues crashed
Dear Maintainer, additional information. Open/close dialogs started to work when I change {current_directory} to //home in the preferences.txt. But I can't open any directory that contain the names in Cyrillic. -- Georg Mikhailov
Bug#775532: RFS: citeproc-py/0.3.0-1 [ITP] -- Python library for CSL based bibliography processing
I'm afraid the license for citeproc/data/schema/ is not DFSG-free: Permission to freely use, copy and distribute. -- WBR, wRAR signature.asc Description: Digital signature
Bug#785138: gparted: Upstream has a new version, v0.22
On 5/12/2015 12:17 PM, felipe wrote: Package: gparted Version: 0.19.0-2.1 Severity: wishlist Dear Maintainer, Gparted has a new version upstream (v0.22) which supports GPT partition tables. gparted has had support for GPT for ages, but yea, I suppose now that jessie has been released I can start upgrading again. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759277: gummiboot: function pointer typedefs using KnR-style(?) parameter declarations
On Tue, May 12, 2015 at 2:01 PM, Julian Andres Klode j...@debian.org wrote: Control: forwarded -1 k...@vrfy.org (Adding Kay Sievers Harald Hoyer from upstream) On Mon, Aug 25, 2014 at 09:10:48PM +0200, Michael Tautschnig wrote: Package: gummiboot Version: 45-2 Usertags: goto-cc Severity: wishlist Tags: upstream While trying to build gummiboot using our research compiler infrastructure the build stumbled upon the following declaration in src/efi/console.c (from line 29 onwards): typedef EFI_STATUS (EFIAPI *EFI_INPUT_RESET_EX)( struct _EFI_SIMPLE_TEXT_INPUT_EX_PROTOCOL *This; BOOLEAN ExtendedVerification; ); While even gcc -Wall -pedantic will emit warnings, clang entirely rejects this. To address this, the semicolons after the function parameters should be replaced by commas, and the last one should be omitted, like this: typedef EFI_STATUS (EFIAPI *EFI_INPUT_RESET_EX)( struct _EFI_SIMPLE_TEXT_INPUT_EX_PROTOCOL *This, BOOLEAN ExtendedVerification ); The same problem appears multiple times in that file. I'm not sure about the rationale for the chosen syntax and surely this is an upstream problem, but I couldn't figure out what their bugtracker was. I'm not sure either, I added the upstream authors to the list of recipients. Just a bug. Surprised that gcc even accepts that. Send a patch if you like it in the gummiboot repo, I'll fix the version in the systemd repo. Thanks, Kay -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785136: schroot: Merged overlayfs is called overlay now, needs an additional workdir
Package: schroot Version: 1.6.10-1+b1 Severity: normal Tags: upstream Control: forwarded -1 https://github.com/codelibre-net/schroot/issues/1 Now that we have kernel 4.0 with overlayfs, support should be fixed. Since overlayfs was merged it was renamed overlay, and now requires an additional workdir option. The work dir must be an empty directory located on the same file system as the upper dir. It is used for atomic file stuff. I have reported this at https://github.com/codelibre-net/schroot/issues/1 as well. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages schroot depends on: ii libboost-filesystem1.55.0 1.55.0+dfsg-3 ii libboost-iostreams1.55.01.55.0+dfsg-3 ii libboost-program-options1.55.0 1.55.0+dfsg-3 ii libboost-regex1.55.01.55.0+dfsg-3 ii libboost-system1.55.0 1.55.0+dfsg-3 ii libc6 2.19-18 ii libgcc1 1:5.1.1-4 ii libpam0g1.1.8-3.1 ii libstdc++6 5.1.1-4 ii libuuid12.25.2-6 ii schroot-common 1.6.10-1 schroot recommends no packages. Versions of packages schroot suggests: pn aufs-modules | unionfs-modules none pn btrfs-tools none ii debootstrap 1.0.67 pn lvm2none ii qemu-user-static1:2.1+dfsg-11 -- Configuration Files: /etc/schroot/default/fstab changed [not included] /etc/schroot/setup.d/10mount changed [not included] -- no debconf information -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. Be friendly, do not top-post, and follow RFC 1855 Netiquette. - If you don't I might ignore you. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784665:
Hi again, I really need the package, and it looks like unmaintained (also upstream, moved to github) since 2009, so I would like to help with the maintenance and upload the new one in a month or two if no answer at all. I really hope you can give me an ack, thanks :) cheers, Gianfranco -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785032: libhtml-strip-perl: autopkgtest failure: warns on usage
On Mon, May 11, 2015 at 11:50:32PM +0200, gregor herrmann wrote: Control: found -1 2.09-1 On Mon, 11 May 2015 20:31:24 +0300, Niko Tyni wrote: This package failed its autopkgtest checks on ci.debian.net. http://ci.debian.net/packages/libh/libhtml-strip-perl/unstable/amd64/ /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t .. 1..2 # Subroutine HTML::Strip::DESTROY redefined at /usr/lib/x86_64-linux-gnu/perl/5.20/DynaLoader.pm line 210. ok 1 - /usr/bin/perl -w -MHTML::Strip -e 1 21 exited successfully not ok 2 - /usr/bin/perl -w -MHTML::Strip -e 1 21 produced no output Still the same in the new upstream release. ISTR that we have the same output also in other XS modules ... It looks to me like this is a real bug in HTML::Strip that only recently started warning because the perl diagnostics improved. Both the XS (Strip.xs) and the Perl (Strip.pm) parts define a DESTROY function, and the former presumably overrides the latter. Apparently a perl change between wheezy (5.14) and jessie (5.20) introduced the warning. I have a small test case and will bisect the perl change at some point. -- Niko Tyni nt...@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#785142: smtube: Smtube doesnt work anymore because of youtube changes
Package: smtube Version: 14.8.0-1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? The search function started returning results except the one about device incompatibility. Reportedly Youtube changed its API to a newer one that isnt supported in smtube 14 * What exactly did you do (or not do) that was effective (or ineffective)? Nothing i could do * 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: stretch/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental'), (1, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages smtube depends on: ii gnome-mplayer 1.0.9-3 ii libc6 2.19-18 ii libgcc1 1:4.9.2-10 ii libqt4-network 4:4.8.6+git155-g716fbae+dfsg-2 ii libqt4-script 4:4.8.6+git155-g716fbae+dfsg-2 ii libqt4-xml 4:4.8.6+git155-g716fbae+dfsg-2 ii libqtcore4 4:4.8.6+git155-g716fbae+dfsg-2 ii libqtgui4 4:4.8.6+git155-g716fbae+dfsg-2 ii libstdc++6 4.9.2-10 ii mplayer2 [mplayer] 2.0-728-g2c378c7-4+b1 ii mpv 0.9.1-1 ii smplayer14.9.0-SVN-r6904 ii vlc [vlc] 3.0.0-git-1 smtube recommends no packages. smtube 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#781952: RFS:complexity/1.2-1 [ITP] -- tool for analyzing the complexity of C program functions
Control: tags -1 + moreinfo On Tue, May 12, 2015 at 12:51:48PM +, Dmitry Bogatov wrote: To access futher information about this package, please visit following URL: http://mentors.debian.net/package/complexity Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/c/complexity/complexity_1.2-1.dsc The package doesn't exist on mentors. -- WBR, wRAR signature.asc Description: Digital signature
Bug#784903: [Pkg-fglrx-devel] Bug#784903: fglrx-driver: broken depends on xorg-video-abi-18
Am 10.05.2015 um 14:18 schrieb Michael Tatge: Source: fglrx-driver Version: 1:14.9+ga14.201-2 Severity: grave Justification: renders package unusable Dear Maintainer, fglrx-driver depends on xorg-video-abi-18 but xserver-xorg-core provides xorg-video-abi-19 thus rendering the package uninstallable. I will check in the next days if the experimental 14.12 version is compatible with it, but I do not think so. -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ signature.asc Description: OpenPGP digital signature
Bug#785126:
Control: tags -1 fixed-upstream It has been fixed upstream using a sightly different patch: http://review.source.kitware.com/19771 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785137: ITP: fwupdate -- Tools to manage UEFI firmware updates
On Tue, 2015-05-12 at 10:58 -0500, Daniel Jared Dominguez wrote: Package: wnpp Severity: wishlist Owner: Daniel Jared Dominguez jared_doming...@dell.com * Package name: fwupdate Version : 0.2 Upstream Author : Peter Jones pjo...@redhat.com * URL : https://github.com/rhinstaller/fwupdate * License : GPL Programming Lang: C Description : Tools to manage UEFI firmware updates fwupdate provides a simple command line interface to the UEFI firmware updates. Shouldn't this have a more specific name, like uefi-fwupdate? Ben. -- Ben Hutchings For every action, there is an equal and opposite criticism. - Harrison signature.asc Description: This is a digitally signed message part
Bug#785138: gparted: Upstream has a new version, v0.22
Package: gparted Version: 0.19.0-2.1 Severity: wishlist Dear Maintainer, Gparted has a new version upstream (v0.22) which supports GPT partition tables. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (900, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gparted depends on: ii libatkmm-1.6-12.22.7-2.1 ii libc6 2.19-18 ii libgcc1 1:5.1.1-5 ii libglib2.0-0 2.44.0-2 ii libglibmm-2.4-1c2a2.44.0-1 ii libgtk2.0-0 2.24.25-3 ii libgtkmm-2.4-1c2a 1:2.24.4-1.1 ii libpangomm-1.4-1 2.36.0-1 ii libparted-fs-resize0 3.2-7 ii libparted23.2-7 ii libsigc++-2.0-0c2a2.4.1-1 ii libstdc++65.1.1-5 ii libuuid1 2.26.2-2 gparted recommends no packages. Versions of packages gparted suggests: pn dmraid none ii dmsetup2:1.02.90-2.2 ii dosfstools 3.0.27-1 pn gpart none pn jfsutils none pn kpartx none pn mtools none ii ntfs-3g1:2014.2.15AR.3-1 pn reiser4progs none pn reiserfsprogs none pn xfsprogs none pn yelp 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#785139: DEP8 tests fail
Package: src:tracker Version: 1.2.6-1 Severity: normal Tags: upstream patch Hi Michael, I noticed that the DEP8 tests of tracker fail (because they are blocking glib2.0 in Ubuntu). There are a few reasons, see the changelog of the attached diff: * debian/tests/unit-tests, debian/patches/000*: Fix the DEP8 tests - Make sure we always have LANG set - Run under dbus-run-session so that there's always a session bus available - Set HOME to our temporary dir so we can guarantee to be able to write to dconf friends - Tell the code that GInotifyFileWatcher is an inotify backend to avoid a warning and use the right number of max waters (bgo #749261) - Fix the collate order of some testsuite output (bgo #749262) - Make an en_US.utf8 locale which the testsuite expects to find. The 0001 patch is not only a testfix, but I hope you'll forgive me bundling it in this bug. You don't get a failure due to it in unstable, but it happens against glib from exp (≥ 2.45). See http://ci.debian.net/data/packages/unstable/amd64/t/tracker/20150501_094009.autopkgtest.log.gz for an example of a failure. Cheers, -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] diff -Nru tracker-1.2.6/debian/changelog tracker-1.2.6/debian/changelog --- tracker-1.2.6/debian/changelog 2015-05-01 04:37:49.0 +0100 +++ tracker-1.2.6/debian/changelog 2015-05-12 17:40:12.0 +0100 @@ -1,3 +1,18 @@ +tracker (1.2.6-1.1) UNRELEASED; urgency=medium + + * debian/tests/unit-tests, debian/patches/000*: Fix the DEP8 tests +- Make sure we always have LANG set +- Run under dbus-run-session so that there's always a session bus + available +- Set HOME to our temporary dir so we can guarantee to be able to write to + dconf friends +- Tell the code that GInotifyFileWatcher is an inotify backend to avoid a + warning and use the right number of max waters (bgo #749261) +- Fix the collate order of some testsuite output (bgo #749262) +- Make an en_US.utf8 locale which the testsuite expects to find. + + -- Iain Lane i...@orangesquash.org.uk Tue, 12 May 2015 11:16:40 +0100 + tracker (1.2.6-1) unstable; urgency=medium * New upstream release. diff -Nru tracker-1.2.6/debian/patches/0001-tracker-miner-Set-inotify-limits-for-GInotifyFileBac.patch tracker-1.2.6/debian/patches/0001-tracker-miner-Set-inotify-limits-for-GInotifyFileBac.patch --- tracker-1.2.6/debian/patches/0001-tracker-miner-Set-inotify-limits-for-GInotifyFileBac.patch 1970-01-01 01:00:00.0 +0100 +++ tracker-1.2.6/debian/patches/0001-tracker-miner-Set-inotify-limits-for-GInotifyFileBac.patch 2015-05-12 17:51:12.0 +0100 @@ -0,0 +1,30 @@ +From dc4785a0f256dc71e1c151da9b0b0c2927059906 Mon Sep 17 00:00:00 2001 +From: Iain Lane i...@orangesquash.org.uk +Date: Tue, 12 May 2015 14:48:32 +0100 +Subject: [PATCH 1/2] tracker-miner: Set inotify limits for + 'GInotifyFileBackend' too + +As of GLib 2.45.1, the inotify monitor backend is called this. + +http://bugzilla.gnome.org/749261 +--- + src/libtracker-miner/tracker-monitor.c | 3 ++- + 1 file changed, 2 insertions(+), 1 deletion(-) + +diff --git a/src/libtracker-miner/tracker-monitor.c b/src/libtracker-miner/tracker-monitor.c +index 327882f..dd7a798 100644 +--- a/src/libtracker-miner/tracker-monitor.c b/src/libtracker-miner/tracker-monitor.c +@@ -281,7 +281,8 @@ tracker_monitor_init (TrackerMonitor *object) + name = g_type_name (priv-monitor_backend); + + /* Set limits based on backend... */ +- if (strcmp (name, GInotifyDirectoryMonitor) == 0) { ++ if (strcmp(name, GInotifyDirectoryMonitor) == 0 || ++ strcmp (name, GInotifyFileMonitor) == 0) { + /* Using inotify */ + g_message (Monitor backend is Inotify); + +-- +2.1.4 + diff -Nru tracker-1.2.6/debian/patches/0002-functions-tracker-Fix-collate-order.patch tracker-1.2.6/debian/patches/0002-functions-tracker-Fix-collate-order.patch --- tracker-1.2.6/debian/patches/0002-functions-tracker-Fix-collate-order.patch 1970-01-01 01:00:00.0 +0100 +++ tracker-1.2.6/debian/patches/0002-functions-tracker-Fix-collate-order.patch 2015-05-12 17:51:41.0 +0100 @@ -0,0 +1,39 @@ +From 9f03dfb6ac77f4cf7f88563ff58a8196ae6be003 Mon Sep 17 00:00:00 2001 +From: Iain Lane i...@orangesquash.org.uk +Date: Tue, 12 May 2015 15:01:20 +0100 +Subject: [PATCH 2/2] functions-tracker: Fix collate order + +In at least en_GB.UTF-8 and C.UTF-8, these tests fail because the output is +actually in a different order. + +https://bugzilla.gnome.org/show_bug.cgi?id=749262 +--- + tests/libtracker-data/functions/functions-tracker-1.out | 2 +- + tests/libtracker-data/functions/functions-tracker-2.out | 2 +- + 2 files changed, 2 insertions(+), 2 deletions(-) + +diff --git a/tests/libtracker-data/functions/functions-tracker-1.out
Bug#785065: vdso32 fails to built on ppc64el
On Tue, 2015-05-12 at 18:32 +0100, Ben Hutchings wrote: On Tue, 2015-05-12 at 17:21 +0100, Ben Hutchings wrote: On Tue, 2015-05-12 at 15:55 +0200, Matthias Klose wrote: that should be fixed on the kernel side by removing this code. there never was a powerpcle userland support. I agree we have no use for this code. Unfortunately it is currently non-optional. [...] I was able to hack out all the 32-bit vDOS along with all 32-bit userland compatibility, but that doesn't solve the problem: a 64-bit kernel apparently still boots in 32-bit mode. If you can make gcc-4.9-powerpc-linux-gnu available on ppc64el we *might* be able to use that. I don't know whether it will be installable in a buildd though. Ben. -- Ben Hutchings For every action, there is an equal and opposite criticism. - Harrison signature.asc Description: This is a digitally signed message part
Bug#775812: HP EliteBook 840 G1 laptop fails to halt/poweroff after 15/12/2015 upgrade
Dear Tim, I have the same HP Elitebook and experienced the same issue when upgrading jessie a few months ago. At the time I solved the issue by booting into an older version of the kernel from GRUB. But then a few weeks ago that workaround stopped working. I thought that completely reinstalling my system (now stretch) would help, but alas it did not. Now I've discovered your bug report, but I'm still not sure what action I should take to get my laptop to power down. Do you have any advice for me? Thanks, Deepee
Bug#785135: msmtp stopped working due to TLS issues on jessie
Asumu, On Tue, May 12, 2015 at 11:36:26AM -0400, Asumu Takikawa wrote: [...] I have been using msmtp to send mail to a server using SMTP+STARTTLS on wheezy. On upgrading to jessie it stopped working and reports a TLS handshake failure. If this SMTP server is publicly reachable, could send me the hostname/IP privately? I will try to reproduce the bug. Regards, -- Emmanuel Bouthenot mail: kolter@{openics,debian}.orggpg: 4096R/0x929D42C3 xmpp: kol...@im.openics.org irc: kolter@{freenode,oftc} -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785118: coreutils: date : format %p %P do not work properly
Hi, On 2015-05-12 20:29, Pádraig Brady wrote: On 12/05/15 17:55, Marko Myllynen wrote: On 2015-05-12 18:49, Pádraig Brady wrote: On 12/05/15 16:40, Pádraig Brady wrote: On 12/05/15 14:51, Michael Stone wrote: On Tue, May 12, 2015 at 03:36:17PM +0200, op...@mumm.ac.be wrote: I'm just upgrading my server from debian 7 (wheezy) to debian 8 (jessie) and several of my scripts are not working anymore. After some tests, it turns out that the problem likely comes from the fact the 'date' function does not work as expected. In wheezy, the command line date /bin/date +%Y%m%d.%p would have returned 20150512.PM In jessie, the same command line returns 20150512. omitting PM. As a consequence of this omission, my scripts are crashing. Have you got any idea why this is happening? I can't reproduce it: /bin/date +%Y%m%d.%p 20150512.AM If I had to guess, I'd say it's a locale issue. What does env LANG=C LC_ALL=C /bin/date +%Y%m%d.%p return? If that works, what does locale return when run by itself? %p is blank in many locales unfortunately. You can see the am_pm vary with these commands: $ LC_ALL=en_IE locale -k LC_TIME $ LC_TIME=C locale -k LC_TIME $ LC_ALL=zh_CN.utf8 date +%p 下午 $ LC_ALL=en_US.utf8 date +%p PM $ LC_ALL=en_US date +%p PM locales with blank am_pm should be fixed up to allow one to get an explicit 12 hour format like `date +%I:%m%p` for example. Note some locales (like en_GB for example) default to 24 hour (t_fmt=%T), and also provide an am_pm entry, which is the correct behavior in my opinion. I see that https://sourceware.org/glibc/wiki/Locales states: am_pm and t_fmt_ampm - should be empty if using 24 hour time Marko, that seems incorrect? At least am_pm should be populated to allow users to generate 12 hour time with strftime? I can't find references to the discussion I had with Keld earlier but the rationale for not populating it was along the lines: 1) am_pm should be populated only if AM/PM convention is used to signal applications they should not try to print them when using them is unwanted. Seems that only the locale(5) commit messages, not the page itself, spell this out: http://git.kernel.org/cgit/docs/man-pages/man-pages.git/commit/?id=b5d4168adfb426f45108ac2bf7c8b17b126b07a1 http://git.kernel.org/cgit/docs/man-pages/man-pages.git/commit/?id=0c2dbad182e40db2ca47128f229ca7dbd83e179f 2) what unwanted means is that in many cases 12 hour time with AM/PM notation is alien thus generating such time representation under those locales would be illogical (e.g. 5.34 ip. in Finnish context is completely unnatural). The same goes for various name_* keywords in LC_NAME, defining them for locales where they are not used would not allow signaling applications that under those locales their usage is unwanted. Thanks for the info. Generally apps would not need to know whether to select between 12 and 24? Can't they just use the higher level (and POSIX defined) %X to get the appropriate default? I propose the wiki at least should be reworded to state that am_pm should be omitted only when it doesn't make any sense that might be a viable option but I think this should be discussed on libc-alpha/libc-locales lists first to allow people there to comment and see if we could even reach consensus. I don't know are there really applications using an empty am_pm to check whether to use 12 or 24 hour time (and if so, would that be a backward compatibility issue) but sounds like by using %X things might be more flexible and portable. Also we'll need to fix up some locales that may have blindly followed the existing advice. No, that's backwards - many/most glibc locales were contributed around '97/'98 or so by people who participated writing the related standards and code, the wiki page has been around only for a couple of years, it aims to document the existing situation and practices to make sure all the locales are consistent and also to make it easier to contribute new locales or validate existing ones. The 12h format is not appropriate for Ireland at least: If I'm not mistaken it has been this way since the locale was added in 1997. In general there's almost no activity at all on glibc locales front so finding issues like this in not totally unexpected. Related to this, it's unclear why the earlier mentioned script has started failing after a distribution upgrade since there certainly haven't been any efforts in upstream to actively remove am_pm or such from locales. Thanks, -- Marko Myllynen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784903: fglrx-driver: broken depends on xorg-video-abi-18
Package: fglrx-driver Version: 1:14.9+ga14.201-2 Followup-For: Bug #784903 Dear Maintainer, Same problem here -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785147: grub-installer bug link
The grub-installer bug report, with patch, is here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785149. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785155: wheezy-pu: package phpbb3/3.0.10-4+deb7u3
Package: release.debian.org Severity: normal Tags: wheezy User: release.debian@packages.debian.org Usertags: pu Hi, Please accept the fix for CVE-2015-3880 in Wheezy, tagged as no-dsa as agreed with the security team. The attached debdiff is pretty similar to the one for Jessie (phpbb3/3.0.12-5+deb8u1, #785154). Regards David diff --git a/changelog b/changelog index 0856a51..e4048ab 100644 --- a/changelog +++ b/changelog @@ -1,3 +1,11 @@ +phpbb3 (3.0.10-4+deb7u3) wheezy; urgency=medium + + * Fix possible redirection on Chrome: an insufficient check allowed users of +the Google Chrome browser to be redirected to external domains (e.g. on +login) [CVE-2015-3880] + + -- David Prévot taf...@debian.org Tue, 12 May 2015 16:02:09 -0400 + phpbb3 (3.0.10-4+deb7u2) wheezy; urgency=medium * Fix CSRF vulnerability [CVE-2015-1432] and CSS injection [CVE-2015-1431] diff --git a/patches/fix_CVE-2015-3880.patch b/patches/fix_CVE-2015-3880.patch new file mode 100644 index 000..bf789db --- /dev/null +++ b/patches/fix_CVE-2015-3880.patch @@ -0,0 +1,32 @@ +Description: Fix possible redirection on Chrome + An insufficient check allowed users of the Google Chrome browser to be + redirected to external domains (e.g. on login). + [CVE-2015-3880] +Author: Marc Alexander ad...@m-a-styles.de, Joas Schilling nickverges...@gmx.de +Origin: upstream, https://github.com/phpbb/phpbb/commit/1a3350619f428d9d69d196c52128727e27ef2f04 +Reviewed-by: Andreas Fischer ba...@phpbb.com +Last-Update: 2015-05-09 +--- a/includes/functions.php b/includes/functions.php +@@ -2426,7 +2426,7 @@ + // Attention: only able to redirect within the same domain if $disable_cd_check is false (yourdomain.com - www.yourdomain.com will not work) + if (!$disable_cd_check $url_parts['host'] !== $user-host) + { +- $url = generate_board_url(); ++ trigger_error('Tried to redirect to potentially insecure url.', E_USER_ERROR); + } + } + else if ($url[0] == '/') +@@ -2513,6 +2513,12 @@ + } + } + ++ // Make sure we don't redirect to external URLs ++ if (!$disable_cd_check strpos($url, generate_board_url(true) . '/') !== 0) ++ { ++ trigger_error('Tried to redirect to potentially insecure url.', E_USER_ERROR); ++ } ++ + // Make sure no linebreaks are there... to prevent http response splitting for PHP 4.4.2 + if (strpos(urldecode($url), \n) !== false || strpos(urldecode($url), \r) !== false || strpos($url, ';') !== false) + { diff --git a/patches/series b/patches/series index 42df55d..86f65b1 100644 --- a/patches/series +++ b/patches/series @@ -8,3 +8,4 @@ fix-php54.patch fix_chown.patch fix_CVE-2015-1431.patch fix_CVE-2015-1432.patch +fix_CVE-2015-3880.patch signature.asc Description: Digital signature
Bug#784732: RFS: liquidprompt/1.9-1 [ITP]
[I don't intend to sponsor this] You should put the Debian repo, not the upstream one into Vcs-* control fields. Recommending both screen and tmux looks strange. Recommending acpi which is useful only for laptops looks strange too. Suggesting zsh looks wrong. d/copyright misses a section for debian/* AGPL-3 should probably be AGPL-3+. I don't like the idea of multiple invocations of the liquidprompt_activate command may pollute ~/.bashrc and/or ~/.zshrc files even if it's mentioned in the manpage. I think a manpage in the section 1 is expected to correspond to an executable with the same name which is not the case here. Maybe I am wrong here. -- WBR, wRAR signature.asc Description: Digital signature
Bug#782450: ppp: Buffer overflow in radius plugin
On 12/04/15 13:20, Emanuele Rocca wrote: On systems with more than 65535 processes running, pppd aborts when sending a start accounting message to the RADIUS server because of a buffer overflow in rc_mksid. The process id is used in rc_mksid to generate a pseudo-unique string, assuming that the hex representation of the pid will be at most 4 characters (). __sprintf_chk(), used when compiling with optimization levels greater than 0 and FORTIFY_SOURCE, detects the buffer overflow and makes pppd crash. The following patch fixes the problem. --- ppp-2.4.6.orig/pppd/plugins/radius/util.c +++ ppp-2.4.6/pppd/plugins/radius/util.c @@ -77,7 +77,7 @@ rc_mksid (void) static unsigned short int cnt = 0; sprintf (buf, %08lX%04X%02hX, (unsigned long int) time (NULL), -(unsigned int) getpid (), +(unsigned int) getpid () % 65535, cnt 0xFF); cnt++; return buf; Hi Emanuele, Did you send your patch upstream? If not, would you mind if I did so? Would you be able to provide a Signed-off-by line as required by upstream? Thanks, Chris -- Chris Boot deb...@bootc.net GPG: 8467 53CB 1921 3142 C56D C918 F5C8 3C05 D9CE -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785154: jessie-pu: package phpbb3/3.0.12-5+deb8u1
Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu Hi, Please accept the fix for CVE-2015-3880 in Jessie, tagged as no-dsa as agreed with the security team. Attached debdiff, similar request for Wheezy follows. Regards David diff --git a/changelog b/changelog index f0fb324..c8b1f20 100644 --- a/changelog +++ b/changelog @@ -1,3 +1,11 @@ +phpbb3 (3.0.12-5+deb8u1) jessie; urgency=medium + + * Fix possible redirection on Chrome: an insufficient check allowed users of +the Google Chrome browser to be redirected to external domains (e.g. on +login) [CVE-2015-3880] + + -- David Prévot taf...@debian.org Tue, 12 May 2015 15:52:23 -0400 + phpbb3 (3.0.12-5) unstable; urgency=medium * Fix authentication setup: another PHP 5.6 compatibility issue, the diff --git a/patches/fix_CVE-2015-3880.patch b/patches/fix_CVE-2015-3880.patch new file mode 100644 index 000..320d589 --- /dev/null +++ b/patches/fix_CVE-2015-3880.patch @@ -0,0 +1,32 @@ +Description: Fix possible redirection on Chrome + An insufficient check allowed users of the Google Chrome browser to be + redirected to external domains (e.g. on login). + [CVE-2015-3880] +Author: Marc Alexander ad...@m-a-styles.de, Joas Schilling nickverges...@gmx.de +Origin: upstream, https://github.com/phpbb/phpbb/commit/1a3350619f428d9d69d196c52128727e27ef2f04 +Reviewed-by: Andreas Fischer ba...@phpbb.com +Last-Update: 2015-05-09 +--- a/includes/functions.php b/includes/functions.php +@@ -2492,7 +2492,7 @@ + // Attention: only able to redirect within the same domain if $disable_cd_check is false (yourdomain.com - www.yourdomain.com will not work) + if (!$disable_cd_check $url_parts['host'] !== $user-host) + { +- $url = generate_board_url(); ++ trigger_error('Tried to redirect to potentially insecure url.', E_USER_ERROR); + } + } + else if ($url[0] == '/') +@@ -2579,6 +2579,12 @@ + } + } + ++ // Make sure we don't redirect to external URLs ++ if (!$disable_cd_check strpos($url, generate_board_url(true) . '/') !== 0) ++ { ++ trigger_error('Tried to redirect to potentially insecure url.', E_USER_ERROR); ++ } ++ + // Make sure no linebreaks are there... to prevent http response splitting for PHP 4.4.2 + if (strpos(urldecode($url), \n) !== false || strpos(urldecode($url), \r) !== false || strpos($url, ';') !== false) + { diff --git a/patches/series b/patches/series index c79ff46..f3998ad 100644 --- a/patches/series +++ b/patches/series @@ -9,3 +9,4 @@ fix_CVE-2015-1431.patch fix_CVE-2015-1432.patch improve_php_5.6_compatibility.patch add_phpbb_prefix_to_ldap_escape.patch +fix_CVE-2015-3880.patch signature.asc Description: Digital signature
Bug#785137: ITP: fwupdate -- Tools to manage UEFI firmware updates
I agree that the name is awful. Even upstream thinks so, but fwupdate is the upstream name. I'm happy to use uefi-fwupdate for the Debian package if that's what people prefer. -Original Message- From: Ben Hutchings [b...@decadent.org.ukmailto:b...@decadent.org.uk] Sent: Tuesday, May 12, 2015 11:21 AM Central Standard Time To: Dominguez, Jared; 785...@bugs.debian.org Subject: Bug#785137: ITP: fwupdate -- Tools to manage UEFI firmware updates On Tue, 2015-05-12 at 10:58 -0500, Daniel Jared Dominguez wrote: Package: wnpp Severity: wishlist Owner: Daniel Jared Dominguez jared_doming...@dell.com * Package name : fwupdate Version : 0.2 Upstream Author : Peter Jones pjo...@redhat.com * URL : https://github.com/rhinstaller/fwupdate * License : GPL Programming Lang: C Description : Tools to manage UEFI firmware updates fwupdate provides a simple command line interface to the UEFI firmware updates. Shouldn't this have a more specific name, like uefi-fwupdate? Ben. -- Ben Hutchings For every action, there is an equal and opposite criticism. - Harrison
Bug#785149: grub-installer: NVMe boot drives not supported
Package: debian-installer Version: 20150422 Severity: critical Tags: d-i patch Justification: breaks the whole system Dear Maintainer, I used the Jessie DVD installer on a system with an NVMe SSD add-in-card (PCIe) that I wanted to make bootable, but there were two problems that halted the process: 1. In the install-the-base-system step, the initial ram disk creation step failed because it couldn't translate the nvme device name (nvme0n1p3) to the base name (nvme0n1). 2. In the boot loader installation step, the boot loader installation script again couldn't translate nvme0n1p3 to nvme0n1. I reported #1, with a patch, at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785147. When I modified grub-installer to work with my NVMe disk, I missed the fact that it wasn't installed on permanent media, so I lost those changes. The attached patch is my attempt at reconstructing what worked for me, so *please bear in mind that I have not tested it*. One additional note: since I use the Linux kernel, my patch does not change the hurd_convert function, and looking at it, I'm guessing it should be modified too. Steve Rowe -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.0.2 (SMP w/16 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- grub-installer-1.117/grub-installer 2015-01-12 23:01:14.0 -0500 +++ grub-installer-1.117/grub-installer.fixed 2015-05-12 15:13:49.002358498 -0400 @@ -134,7 +134,7 @@ # This should probably be rewritten using udevadm or similar. device_to_disk () { echo $1 | \ - sed 's:\(/dev/\(cciss\|ida\|rs\)/c[0-9]d[0-9][0-9]*\|/dev/mmcblk[0-9]\|/dev/\(ad\|ada\|da\)[0-9]\+\|/dev/[hs]d[0-9]\+\|/dev/[a-z]\+\).*:\1:' + sed 's:\(/dev/nvme[0-9]n[0-9]\|/dev/\(cciss\|ida\|rs\)/c[0-9]d[0-9][0-9]*\|/dev/mmcblk[0-9]\|/dev/\(ad\|ada\|da\)[0-9]\+\|/dev/[hs]d[0-9]\+\|/dev/[a-z]\+\).*:\1:' } # Run update-grub in $ROOT @@ -252,7 +252,7 @@ /dev/mapper) disc_offered_devfs=$bootfs ;; -/dev/[hsv]d[a-z0-9]|/dev/xvd[a-z]|/dev/cciss/c[0-9]d[0-9]*|/dev/ida/c[0-9]d[0-9]*|/dev/rs/c[0-9]d[0-9]*|/dev/mmcblk[0-9]|/dev/ad[0-9]*|/dev/da[0-9]*) +/dev/nvme[0-9]n[0-9]|/dev/[hsv]d[a-z0-9]|/dev/xvd[a-z]|/dev/cciss/c[0-9]d[0-9]*|/dev/ida/c[0-9]d[0-9]*|/dev/rs/c[0-9]d[0-9]*|/dev/mmcblk[0-9]|/dev/ad[0-9]*|/dev/da[0-9]*) disc_offered_devfs=$prefix ;; *) @@ -895,6 +895,10 @@ disk= part= case $1 in +/dev/nvme*n*p*) + disk=$(echo $1 | sed 's,\(/dev/nvme[0-9]n[0-9]\).*,\1,') + part=$(echo $1 | sed 's,/dev/nvme[0-9]n[0-9]\(.*\),\1,') + ;; /dev/[vhs]d[a-z]*) disk=$(echo $1 | sed 's,\(/dev/[a-z]\+\).*,\1,') part=$(echo $1 | sed 's,/dev/[a-z]\+\(.*\),\1,')
Bug#785151: fritzing: A new upstream version is available
Package: fritzing Version: 0.9.0b+dfsg-1 Severity: wishlist Dear Maintainer, at http://fritzing.org/download/, version 0.9.2b is available for download. Compared to 0.9.0b, it contains some new part definitions, and a few bug fixes. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784837: --cipher-suite-blacklist=0x5 doesn't
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Done, see https://code.google.com/p/chromium/issues/detail?id=487381 Regards Harri -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJVUlmPAAoJEAqeKp5m04HLS6EIAJFmN5Xj0VphFDEUKFy5zDDb BsryxLQAQP6lsxb+GUnBqSrY1BQsNsuS8qO0zsXncmdrujmDurVhXAf6Snm7C1C+ E5pcwnVLqDX/5SKElt/KIqP8HaL6dIV5I1gkFqc/8FYJ+FNlgLAtM7p8ggHkhY/m OZKEw5RgVlyVB/XNnD2bqt/ZbOncKCn7Efd/jCtV99ne3m1zkDwYFkNo/Pv1cGqk iBrHZ8pNpJyiaWiiWfPVPm+nU1rTzgnV6UE77a6vzhPA7IA4PFmuUOFCuPw4d4Hs l45pMqn54XSVFtDmDAuxJd3ilGnD1o3KKDwTwxLj8tKwhdm2Wp/YTirLarwsCZ0= =P9V9 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785149: grub-installer: NVMe boot drives not supported
Control: reassign -1 grub-installer Control: found -1 1.85 Control: severity important Hi Steve, Steve Rowe sar...@gmail.com (2015-05-12): Package: debian-installer Version: 20150422 Severity: critical Tags: d-i patch Justification: breaks the whole system Failing to install isn't breaking the whole system. ;) Dear Maintainer, I used the Jessie DVD installer on a system with an NVMe SSD add-in-card (PCIe) that I wanted to make bootable, but there were two problems that halted the process: 1. In the install-the-base-system step, the initial ram disk creation step failed because it couldn't translate the nvme device name (nvme0n1p3) to the base name (nvme0n1). I reported #1, with a patch, at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785147. ACK, thanks. 2. In the boot loader installation step, the boot loader installation script again couldn't translate nvme0n1p3 to nvme0n1. When I modified grub-installer to work with my NVMe disk, I missed the fact that it wasn't installed on permanent media, so I lost those changes. The attached patch is my attempt at reconstructing what worked for me, so *please bear in mind that I have not tested it*. One additional note: since I use the Linux kernel, my patch does not change the hurd_convert function, and looking at it, I'm guessing it should be modified too. I'll have a look shortly and push something. Provided the patch for #785147 is backported to jessie, we might do that as well. Mraw, KiBi. signature.asc Description: Digital signature
Bug#785153: [src:linux] Please enable support for DVBSky T9580
Package: src:linux Version: 4.0.2-1 Severity: wishlist --- Please enter the report below this line. --- Please set CONFIG_DVB_SMIPCIE=m to enable support for the DVBSky T9580 card. I did a test build with this option enabled on linux-image-3.19 and the card did work without problems. Regards, Maxi --- System information. --- Architecture: amd64 Kernel: Linux 4.0.0-1-amd64 Debian Release: stretch/sid 500 testing security.debian.org 500 testing httpredir.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. signature.asc Description: This is a digitally signed message part.
Bug#784964: jessie-pu: package mate-utils/1.8.1+dfsg1-2+deb8u1
Control: tags -1 + pending On Mon, 2015-05-11 at 10:36 +, Mike Gabriel wrote: Hi Adam, On Mo 11 Mai 2015 12:09:00 CEST, Adam D. Barratt wrote: Control: tags -1 + confirmed On 2015-05-11 9:14, Mike Gabriel wrote: [...] + * debian/patches: ++ Add 0002_fix-errmsg-text.patch. Show actual error message if loading of the + mate-screenshot UI fails. (Closes: #783162). This will fix a reported error message in mate-screenshot when the UI cannot be loaded. In the previous version, the reported error message was not exact and a wrong failure reason got reported. Please go ahead. Uploaded and accepted in stable-new. Flagged for acceptance. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784342: jessie-pu: package openstack-debian-images/1.3
Control: tags -1 + pending On Thu, 2015-05-07 at 22:45 +0100, Adam D. Barratt wrote: Control: tags -1 -moreinfo +confirmed On Thu, 2015-05-07 at 01:20 +0200, Thomas Goirand wrote: I have generated a new 1.3~deb8u1 version as suggested, and attached the debdiff to this bug. [...] In any case, please go ahead. Flagged for acceptance. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784430: [Lynx-dev] gnutls priority string disables any signature algorithms and ertificate types
* Andreas Metzler ametz...@bebt.de [2015-05-12 19:54 +0200]: On 2015-05-12 Thomas Dickey dic...@his.com wrote: On Mon, May 11, 2015 at 07:09:01PM +0200, Andreas Metzler wrote: As a hotfix +CTYPE-X.509:+SIGN-ALL could be added, however looking the string I wonder whether it would not be better if lynx simple used GnuTLS default settings with gnutls_set_default_priority() by default. Optionally a configuration option allowing a user to specify an alternate priority-string could be used. simpler settings sounds like an improvement... Hello, ;-) Great to see you agreeing. Attached q'n'd change[1] worked for me on a quick test. As gnutls_set_default_priority() was added in 2002 (GnuTLS 0.5.9) there is no need to add a autoconf test for it. I can confirm that this patch gets me back to access kernel.org via lynx. Thanks Andreas for your investigation. Elimar -- Numeric stability is probably not all that important when you're guessing;-) signature.asc Description: Digital signature
Bug#785150: fglrx-modules-dkms: the module fail to build with linux 4.0.0-1-amd64
Package: fglrx-modules-dkms Version: 1:14.9+ga14.201-2 Severity: grave When building the module for linux 4.0.0-1-amd64 dkms fail with: DKMS make.log for fglrx-14.12 for kernel 4.0.0-1-amd64 (x86_64) mardi 12 mai 2015, 21:50:46 (UTC+0200) make: Entering directory '/usr/src/linux-headers-4.0.0-1-amd64' LD /var/lib/dkms/fglrx/14.12/build/built-in.o CC [M] /var/lib/dkms/fglrx/14.12/build/firegl_public.o /var/lib/dkms/fglrx/14.12/build/firegl_public.c: In function ‘kcl_mem_pat_setup’: /var/lib/dkms/fglrx/14.12/build/firegl_public.c:4471:9: error: implicit declaration of function ‘read_cr4’ [-Werror=implicit-function-declaration] cr4 = read_cr4(); ^ /var/lib/dkms/fglrx/14.12/build/firegl_public.c:4472:9: error: implicit declaration of function ‘write_cr4’ [-Werror=implicit-function-declaration] write_cr4(cr4 ~X86_CR4_PGE); ^ /var/lib/dkms/fglrx/14.12/build/firegl_public.c: In function ‘kasSetExecutionLevel’: /var/lib/dkms/fglrx/14.12/build/firegl_public.c:4819:5: error: implicit declaration of function ‘__get_cpu_var’ [-Werror=implicit-function-declaration] orig_level = __get_cpu_var(kasExecutionLevel); ^ /var/lib/dkms/fglrx/14.12/build/firegl_public.c:4820:38: error: lvalue required as left operand of assignment __get_cpu_var(kasExecutionLevel) = level; ^ /var/lib/dkms/fglrx/14.12/build/firegl_public.c: At top level: /var/lib/dkms/fglrx/14.12/build/firegl_public.c:6396:12: warning: ‘KCL_fpu_save_init’ defined but not used [-Wunused-function] static int KCL_fpu_save_init(struct task_struct *tsk) ^ cc1: some warnings being treated as errors /usr/src/linux-headers-4.0.0-1-common/scripts/Makefile.build:263: recipe for target '/var/lib/dkms/fglrx/14.12/build/firegl_public.o' failed make[3]: *** [/var/lib/dkms/fglrx/14.12/build/firegl_public.o] Error 1 /usr/src/linux-headers-4.0.0-1-common/Makefile:1407: recipe for target '_module_/var/lib/dkms/fglrx/14.12/build' failed make[2]: *** [_module_/var/lib/dkms/fglrx/14.12/build] Error 2 Makefile:145: recipe for target 'sub-make' failed make[1]: *** [sub-make] Error 2 Makefile:8: recipe for target 'all' failed make: *** [all] Error 2 make: Leaving directory '/usr/src/linux-headers-4.0.0-1-amd64' DKMS make.log for fglrx-14.12 for kernel 4.0.0-1-amd64 (x86_64) mardi 12 mai 2015, 21:50:46 (UTC+0200) make: Entering directory '/usr/src/linux-headers-4.0.0-1-amd64' LD /var/lib/dkms/fglrx/14.12/build/built-in.o CC [M] /var/lib/dkms/fglrx/14.12/build/firegl_public.o /var/lib/dkms/fglrx/14.12/build/firegl_public.c: In function ‘kcl_mem_pat_setup’: /var/lib/dkms/fglrx/14.12/build/firegl_public.c:4471:9: error: implicit declaration of function ‘read_cr4’ [-Werror=implicit-function-declaration] cr4 = read_cr4(); ^ /var/lib/dkms/fglrx/14.12/build/firegl_public.c:4472:9: error: implicit declaration of function ‘write_cr4’ [-Werror=implicit-function-declaration] write_cr4(cr4 ~X86_CR4_PGE); ^ /var/lib/dkms/fglrx/14.12/build/firegl_public.c: In function ‘kasSetExecutionLevel’: /var/lib/dkms/fglrx/14.12/build/firegl_public.c:4819:5: error: implicit declaration of function ‘__get_cpu_var’ [-Werror=implicit-function-declaration] orig_level = __get_cpu_var(kasExecutionLevel); ^ /var/lib/dkms/fglrx/14.12/build/firegl_public.c:4820:38: error: lvalue required as left operand of assignment __get_cpu_var(kasExecutionLevel) = level; ^ /var/lib/dkms/fglrx/14.12/build/firegl_public.c: At top level: /var/lib/dkms/fglrx/14.12/build/firegl_public.c:6396:12: warning: ‘KCL_fpu_save_init’ defined but not used [-Wunused-function] static int KCL_fpu_save_init(struct task_struct *tsk) ^ cc1: some warnings being treated as errors /usr/src/linux-headers-4.0.0-1-common/scripts/Makefile.build:263: recipe for target '/var/lib/dkms/fglrx/14.12/build/firegl_public.o' failed make[3]: *** [/var/lib/dkms/fglrx/14.12/build/firegl_public.o] Error 1 /usr/src/linux-headers-4.0.0-1-common/Makefile:1407: recipe for target '_module_/var/lib/dkms/fglrx/14.12/build' failed make[2]: *** [_module_/var/lib/dkms/fglrx/14.12/build] Error 2 Makefile:145: recipe for target 'sub-make' failed make[1]: *** [sub-make] Error 2 Makefile:8: recipe for target 'all' failed make: *** [all] Error 2 make: Leaving directory '/usr/src/linux-headers-4.0.0-1-amd64' -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (150, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages fglrx-modules-dkms depends on: ii dkms 2.2.0.3-2 fglrx-modules-dkms recommends no packages. Versions of packages fglrx-modules-dkms
Bug#769844: linux: please make linux build reproducibly
On Wed, 2015-01-07 at 20:49 +0100, Jérémy Bobbio wrote: [...] With the attached patch, linux can be built reproducibly with the current experimental framework. The following changes have been introduced since the previous patch: * Files in the source tarball are added in a stable order. * kernel-doc is made deterministic when parsing `@foo()` in descriptions. * The last set of manpages when generating manpages from files referenced in multiple sections of the documentation is deterministic. Some `@foo()` constructs in the kernel should probably be fixed to be just `foo()`. It's unclear what should be used for functions passed as parameters. Hardly anyone seems to use the output of kernel-doc so the sources are of very variable quality. Function pointers aren't functions so I think they should be @foo. Moving on to your patch: Most of the added patches should go upstream and therefore belong under bugfix/all/ not debian/. Please can you also add a sign-off to these (after reading what Documentation/SubmittingPatches says about that). diff -Nru linux-3.16.7-ckt2/debian/patches/debian/generate-manpage-in-deterministic-order.patch linux-3.16.7-ckt2/debian/patches/debian/generate-manpage-in-deterministic-order.patch --- linux-3.16.7-ckt2/debian/patches/debian/generate-manpage-in-deterministic-order.patch 1970-01-01 01:00:00.0 +0100 +++ linux-3.16.7-ckt2/debian/patches/debian/generate-manpage-in-deterministic-order.patch 2015-01-07 16:34:00.0 +0100 @@ -0,0 +1,55 @@ +Description: generate manpages in deterministic order + When header files are referenced multiple times in different + documentation parts, manpages for the various functions will also + be generated multiple times. [...] I don't yet understand this, so I'll come back to it later. diff -Nru linux-3.16.7-ckt2/debian/patches/debian/make-highlights-deterministic-in-kernel-doc.patch linux-3.16.7-ckt2/debian/patches/debian/make-highlights-deterministic-in-kernel-doc.patch --- linux-3.16.7-ckt2/debian/patches/debian/make-highlights-deterministic-in-kernel-doc.patch 1970-01-01 01:00:00.0 +0100 +++ linux-3.16.7-ckt2/debian/patches/debian/make-highlights-deterministic-in-kernel-doc.patch 2015-01-07 16:43:31.0 +0100 @@ -0,0 +1,21 @@ +Description: parse kernel-doc deterministically + Regular expressions for highlights in kernel-doc are stored in a Perl + hash. These hashes are ordered differently for each Perl run. This will + prevent kernel-doc to behave deterministically when parsing + “@foo()” as in some runs it will be interpreted as a parameter and + in the others it will be interpreted as a function. + . + We now sort the %highlights hash to get the same behavior on every run. +Author: Jérémy Bobbio lu...@debian.org + +--- linux-3.16.7-ckt2.orig/scripts/kernel-doc linux-3.16.7-ckt2/scripts/kernel-doc +@@ -2586,7 +2586,7 @@ $kernelversion = get_kernel_version(); + + # generate a sequence of code that will splice in highlighting information + # using the s// operator. +-foreach my $pattern (keys %highlights) { ++foreach my $pattern (sort keys %highlights) { + # print STDERR scanning pattern:$pattern, highlight:($highlights{$pattern})\n; + $dohighlight .= \$contents =~ s:$pattern:$highlights{$pattern}:gs;\n; + } OK, applied. diff -Nru linux-3.16.7-ckt2/debian/patches/debian/parse-debian-build-timestamp.patch linux-3.16.7-ckt2/debian/patches/debian/parse-debian-build-timestamp.patch --- linux-3.16.7-ckt2/debian/patches/debian/parse-debian-build-timestamp.patch 1970-01-01 01:00:00.0 +0100 +++ linux-3.16.7-ckt2/debian/patches/debian/parse-debian-build-timestamp.patch 2015-01-05 14:50:58.0 +0100 @@ -0,0 +1,26 @@ +Description: parse Debian KBUILD_BUILD_TIMESTAMP in gen_initramfs_list.sh + gen_initramfs_list.sh assumes that KBUILD_BUILD_TIMESTAMP only contains a + date. In Debian, it's a longer string looking like: + “Debian 3.16.7-2 (2014-11-06)”. Here we adapt the script to parse Debian + format. + . + This change is necessary to have reproducible builds as the date will + then be used as mtime for files in initramfs archive instead of the + current time. +Author: Jérémy Bobbio lu...@debian.org +Bug-Debian: https://bugs.debian.org/769844 +Forwarded: not-needed + +--- linux-3.16.7-ckt2.orig/scripts/gen_initramfs_list.sh linux-3.16.7-ckt2/scripts/gen_initramfs_list.sh +@@ -301,7 +301,9 @@ if [ ! -z ${output_file} ]; then + if [ -z ${cpio_file} ]; then + timestamp= + if test -n $KBUILD_BUILD_TIMESTAMP; then +- timestamp=$(date -d$KBUILD_BUILD_TIMESTAMP +%s || :) ++ source_date=$(echo $KBUILD_BUILD_TIMESTAMP | ++ sed -e 's/.*(\([0-9-]\+\)).*/\1/') ++ timestamp=$(date -d$source_date +%s || :) +
Bug#781306: makehuman: Immediate segmentation fault at launch
Package: makehuman Version: 1.0.0~alpha6-5+b1 Followup-For: Bug #781306 Dear John, I have uploaded the new upstream version of makehuman to experimental. Could you please test it and tell me if you still have this bug, please?. Regards, -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages makehuman depends on: ii fontconfig2.11.0-6.3 ii libc6 2.19-18 ii libgl1-mesa-glx [libgl1] 10.5.5-1 ii libglew1.10 1.10.0-3 ii libglu1-mesa [libglu1]9.0.0-2 ii libpython2.7 2.7.10~rc1-1 ii libsdl-image1.2 1.2.12-5+b5 ii libsdl1.2debian 1.2.15-11 ii libx11-6 2:1.6.3-1 ii makehuman-data1.0.0~alpha6-5 pn python2.7:any none pn python:anynone Versions of packages makehuman recommends: ii aqsis 1.8.2-1 Versions of packages makehuman suggests: pn makehuman-doc none -- no debconf information -- Muammar El Khatib. http://muammar.me | http://proyectociencia.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696496:
This is definitely not an issue in the latest pithos upstream, version 1.1.0.
Bug#785147: initramfs-tools: NVMe boot drives not supported
Package: initramfs-tools Version: 0.120 Severity: critical Tags: d-i patch Justification: breaks the whole system Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** I used the Jessie DVD installer on a system with an NVMe SSD add-in-card (PCIe) that I wanted to make bootable, but there were two problems that halted the process: 1. In the install-the-base-system step, the initial ram disk creation step failed because it couldn't translate the nvme device name (nvme0n1p3) to the drive name (nvme0n1). This appears to be a new naming scheme, where p[0-9] refers the partition number. 2. In the boot loader installation step, the grub-installer script again couldn't translate nvme0n1p3 to nvme0n1. I'm making a separate bug for the grub-installer, so I'll only include the initramfs-tools patch here: - --- initramfs-tools/hook-functions 2015-03-01 16:44:34.0 -0500 +++ initramfs-tools/hook-functions.fixed2015-05-12 14:20:16.806315846 -0400 @@ -434,6 +434,10 @@ block=${dev_node#/dev/i2o/} block=${block%%[0-9]*} block='i2o!'$block + # nvme device + elif [ ${dev_node#/dev/nvme} != ${dev_node} ]; then + block=${dev_node#/dev/} + block=${block%p*} # classical block device else block=${dev_node#/dev/} - Thanks, Steve Rowe -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 3.6M May 8 01:52 /boot/initrd.img-3.16.0-4-amd64 -rw-r--r-- 1 root root 3.6M May 10 22:09 /boot/initrd.img-4.0.2 -- /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.0.2 root=UUID=9954878e-5783-4f4b-bca3-55d689f221da ro splash -- resume RESUME=UUID=ab2d298a-cc4d-46f9-b9a6-6452e4c3754f -- /proc/filesystems ext3 ext2 ext4 fuseblk vfat -- lsmod Module Size Used by iptable_filter 16384 0 ip_tables 28672 1 iptable_filter x_tables 28672 2 ip_tables,iptable_filter nf_nat 20480 0 nf_conntrack 90112 1 nf_nat bridge102400 0 stp16384 1 bridge llc16384 2 stp,bridge dm_thin_pool 61440 0 dm_persistent_data 53248 1 dm_thin_pool dm_bio_prison 16384 1 dm_thin_pool dm_bufio 24576 1 dm_persistent_data libcrc32c 16384 1 dm_persistent_data loop 28672 0 dm_mod 94208 3 dm_persistent_data,dm_bufio,dm_thin_pool joydev 20480 0 hid_microsoft 16384 0 hid_generic16384 0 usbhid 45056 0 hid 102400 3 hid_generic,hid_microsoft,usbhid usb_storage57344 0 cfg80211 446464 0 nfsd 278528 2 auth_rpcgss53248 1 nfsd oid_registry 16384 1 auth_rpcgss nfs_acl16384 1 nfsd nfs 204800 0 lockd 90112 2 nfs,nfsd grace 16384 2 nfsd,lockd fscache49152 1 nfs sunrpc270336 6 nfs,nfsd,auth_rpcgss,lockd,nfs_acl snd_hda_codec_hdmi 53248 1 sg 32768 0 sr_mod 24576 0 cdrom 49152 1 sr_mod sd_mod 40960 2 snd_hda_codec_realtek69632 1 snd_hda_codec_generic65536 1 snd_hda_codec_realtek x86_pkg_temp_thermal16384 0 intel_powerclamp 20480 0 intel_rapl 20480 0 iosf_mbi 16384 1 intel_rapl coretemp 16384 0 kvm 421888 0 nls_utf8 16384 1 nls_cp437 20480 1 crct10dif_pclmul 16384 0 crc32_pclmul 16384 0 eeepc_wmi 16384 0 crc32c_intel 24576 1 asus_wmi 24576 1 eeepc_wmi vfat 20480 1 sparse_keymap 16384 1 asus_wmi snd_hda_intel 28672 5 fat65536 1 vfat ahci 32768 1 rfkill 20480 2 cfg80211,asus_wmi ghash_clmulni_intel16384 0 snd_hda_controller 28672 1 snd_hda_intel libahci28672 1 ahci xhci_pci 16384 0 snd_hda_codec 110592 5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel,snd_hda_controller libata180224 2 ahci,libahci video 20480 1 asus_wmi radeon 1490944 2 ehci_pci 16384 0 iTCO_wdt 16384 0 aesni_intel 167936 0 iTCO_vendor_support16384 1 iTCO_wdt mxm_wmi16384 0 evdev