Bug#788512: cobbler: [INTL:ru] Russian debconf templates translation
Package: cobbler Version: 2.6.6+dfsg1-3 Severity: wishlist Tags: l10n patch 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 *** Russian debconf templates translation is attached. -- System Information: Debian Release: 8.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf, armel Kernel: Linux 3.16.0-4-amd64 (SMP w/8 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) ru.po.gz Description: application/gzip
Bug#788505: [Python-modules-team] Bug#788505: python-pypump: [PATCH] please make the build reproducible
(Cc'ing the reproducible builds mailing list instead of specific team members.) W. Martin Borgert: while I'm all in favour of reproducible builds, I'm not happy with messing up hundreds of packages debian/rules files. Why not change the defaults of sphinx or dh or whatever and just rebuild packages? It would need to be Sphinx. If you look at the patch for pypump you have replied to: - make -C docs html + make -C docs html SPHINXOPTS=$(SPHINXOPTS) As you can see, the current `debian/rules` already contains specific code to build the documentation. But if we can find solutions that would fix all these packages at once, that would be really awesome! :) Who needs or wants a last change date in the HTML anyway? Some people argue that you need it to determine how “fresh” the documentation is. In the case of documentation generated by Debian package, I think the package version string is a much more reliable information. The problem is that Sphinx is not only used to build Debian packages. So changing the default to the use the latter sounds tricky. We worked years to get the d/r files clean and short and now we add cruft to it again? Which is repeated redundantly in hundreds of files? Maybe dh_sphinxdoc could just do the right thing? `dh_sphinxdoc` should indeed be changed to do the right thing. But looking at the stream of patches written by Juan for this issue, I haven't seen any for packages using `dh_sphinxdoc`, and even if patches look alike, they are hardly identical. The only “cruft” I really see is: +LAST_CHANGE=$(shell dpkg-parsechangelog -S Date) +BUILD_DATE=$(shell LC_ALL=C date -u +%B %d, %Y -d $(LAST_CHANGE)) The problem is that every tool on Earth uses a different date format. They have been discussions on adding variables to `/usr/share/dpkg/pkg-info.mk` But that basically would mean replacing the two lines by: include /usr/share/dpkg/pkg-info.mk And then using something like (if we can agree to export the date in multiple format): SPHINXOPTS := -D today=\$(SOURCE_DATE_ENGLISH_SHORT)\ It doesn't feel like a huge win to me. (Remember that packages can be built without using `dpkg-buildpackage`, so the Makefile has to be self-contained.) -- Lunar.''`. lu...@debian.org: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature
Bug#787391: transition: evolution-data-server
On Thu, Jun 11, 2015 at 3:23 PM, Emilio Pozuelo Monfort po...@debian.org wrote: Hi Vincent, On 01/06/15 11:31, Vincent Cheng wrote: Hi Emilio, On Sun, May 31, 2015 at 6:07 PM, Emilio Pozuelo Monfort po...@debian.org wrote: These currently fail to build: eweouz sflphone bijiben I've gone ahead and uploaded bijiben/3.16.2-1 to experimental after verifying it builds against e-d-s in experimental. Please either ping me, or just go ahead and NMU bijiben to upload it to sid once the transition starts. I've uploaded e-d-s 3.16 to sid. If you can upload bijiben, that'd be great. Uploaded, thanks for the ping! Regards, Vincent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788516: mirror submission for mirrors-ca.muzzy.us
Package: mirrors Severity: wishlist Submission-Type: new Site: mirrors-ca.muzzy.us Aliases: mirrors.muzzy.us Type: leaf Archive-architecture: ALL amd64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc s390x sparc Archive-ftp: /debian/ Archive-http: /debian/ Archive-rsync: debian/ CDImage-ftp: /debiancd/ CDImage-http: /debiancd/ CDImage-rsync: debiancd/ IPv6: no Archive-upstream: debian.bhs.mirrors.ovh.net CDImage-upstream: mirror.its.dal.ca Updates: four Maintainer: Emiliano Muzzurru mirr...@muzzy.us Country: CA Canada -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788511: openssl: breaks ABI
Package: openssl Version: 1.0.2b-1 Severity: serious The HMAC_CTX structure added a new field at the end increasing it's size. This can break applications that allocate it on the stack. It looks like at least OpenSSH 4.7 through 6.5 on 32 bit platforms are affected. Kurt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788450: swift: [PATCH] Updated package to Swift 2.3.0 and container-reconciler
Hi Ondrej, Thanks a lot for your patch. This is very much appreciated. I'm about to upload Swift 2.3.0 in Sid, however, I need to fix #788451 first as you know. Since there's no reply from upstream, I guess I'll figure it out myself and cherry-pick the missing commits. Cheers, Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#787505: also affects browsers
Daniel Kahn Gillmor d...@fifthhorseman.net wrote: which web sites are you visiting that do FFDHE with weak groups? It is The authentication portal for my university intranet (!) a good thing that the browser does not treat these connections as secure connections. Indeed. But then there's no obvious way to access the site if really needed. Possible work-arounds: - downgrading to 3.19, - setting about:config security.ssl3.*.dhe* to false as suggested by Ben Caradoc-Davies above. Both do work. Maybe a word on the issue and possible work-arounds should appear in README.Debian. Also, it could be nice to display a warning about that when upgrading from 3.19 since it's probably not obvious for everybody to go look to libnss3 if the browser or mailer fails. (assuming that complies with the policy about displaying such warnings, which I don't know). -- Christophe Deleuze -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#787731: adds google nameserver without being asked to
Am 10.06.2015 um 11:37 schrieb Michael Biebl: Am 09.06.2015 um 13:14 schrieb Marc Haber: On Sat, Jun 06, 2015 at 09:42:37PM +0200, Michael Biebl wrote: This change is imho too invasive for being backported to the stable v215 in jessie. The first Debian version carrying that fix is 217-1, so I'm closing it for this version. How about shipping a /etc/systemd/resolved.conf with a not commented out DNS= line? Compiling with ---with-dns-servers= is better. It doesn't require us to patch the conf file, it also changes the builtin list, and the resulting resolved.conf will actually look pretty similar: [Resolve] #DNS= I committed this change now for the jessie branch: https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=jessieid=fc04df5fc3adedb990318a34d69a261521d4d57d So this change will be part of the next stable upload. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#788514: ruby-cssmin: FTBFS due to lack of build dependency on rake
Package: ruby-cssmin Version: 1.0.3-3 Severity: serious Tags: patch Justification: fails to build from source (but built successfully in the past) User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu wily ubuntu-patch Dear Maintainer, ruby-cssmin currently FTBFS in unstable because it uses rake without having a build dependency on it. In Ubuntu, the attached patch was applied to achieve the following: * Build-depend on rake to fix FTBFS. Thanks for considering the patch. Logan Rosen -- System Information: Debian Release: jessie/sid APT prefers wily-updates APT policy: (500, 'wily-updates'), (500, 'wily-security'), (500, 'wily'), (100, 'wily-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.19.0-20-generic (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) diff -Nru ruby-cssmin-1.0.3/debian/control ruby-cssmin-1.0.3/debian/control --- ruby-cssmin-1.0.3/debian/control 2015-05-24 04:35:48.0 -0700 +++ ruby-cssmin-1.0.3/debian/control 2015-06-12 01:03:04.0 -0700 @@ -3,7 +3,7 @@ Priority: optional Maintainer: Debian Ruby Extras Maintainers pkg-ruby-extras-maintain...@lists.alioth.debian.org Uploaders: Balasankar C balasank...@autistici.org -Build-Depends: debhelper (= 7.0.50~), gem2deb (= 0.7.5~) +Build-Depends: debhelper (= 7.0.50~), gem2deb (= 0.7.5~), rake Standards-Version: 3.9.6 Vcs-Git: git://anonscm.debian.org/pkg-ruby-extras/ruby-cssmin.git Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-ruby-extras/ruby-cssmin.git;a=summary
Bug#737058: CEGUI-0.8.4-1
Hi Yohann, Am Freitag, den 12.06.2015, 00:07 +0200 schrieb Yohann Ferreira: Hey, I just wanted to hint that Muammar uploaded a new package some days ago: https://ftp-master.debian.org/new/cegui-mk2_0.8.4-1.html Could you have a look at it, so we can close this bug and maybe a few others? Thanks and best regards, Yohann Yes, bug triaging is important and the Debian project appreciateas also any help on this here for sure appreciated Well, unfortuantly this bugs mixes two different things: - new upstream version - make dependencies optional As soon as the package is through NEW the first part is closed, but for the second part, Muammar needs to give directions how he wants to develop the project. So for this bug, after 0.8.4 is in the archives maybe this bug should be retitled... -- Tobi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#787686: pocl: FTBFS on arm64
Package: src:pocl Followup-For: Bug #787686 Hi, Thank you for your report. I'm preparing a package for the 0.11 version. For the arm64 arch, as for all other Debian arch, we need to tell llvm to use the minimum ABI garantee by the architecture (and not the architecture detected at build-time on the builder box) So, I will try 0.11 with LLVM_ARCH=cortex-a53 But I'm not an arm64 expert. So, do not hesitate to propose me a better arch target for arm64 llvm target CPU. Regards, Vincent -- System Information: Debian Release: stretch/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'oldstable-updates'), (500, 'oldoldstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armel, mipsel Kernel: Linux 4.0.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (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#787378: eweouz: FTBFS with evolution-data-server 3.16
Control: severity -1 serious On 31/05/15 23:13, Emilio Pozuelo Monfort wrote: Package: eweouz Version: 0.9 Severity: important Hi, On a rebuild of your package against evolution-data-server 3.16 (currently in experimental) it failed to build: .../../src/eweouz-write-addressbook.c:153:27: error: too few arguments to function 'e_book_client_connect_sync' client = E_BOOK_CLIENT(e_book_client_connect_sync(source, NULL, error)); ^ (and a few others). I'd like to upload e-d-s 3.16 to sid soon as it's needed for GNOME 3.16, so it'd be great if you could take a look at this. Upstream or other distros may already have a patch. e-d-s 3.16 is now in sid, so this is RC. Emilio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788505: [Python-modules-team] Bug#788505: python-pypump: [PATCH] please make the build reproducible
Dear Juan, (and H01ger, Lunar and team cc'ed), while I'm all in favour of reproducible builds, I'm not happy with messing up hundreds of packages debian/rules files. Why not change the defaults of sphinx or dh or whatever and just rebuild packages? Who needs or wants a last change date in the HTML anyway? We worked years to get the d/r files clean and short and now we add cruft to it again? Which is repeated redundantly in hundreds of files? Maybe dh_sphinxdoc could just do the right thing? Cheers On 2015-06-11 22:51, Juan Picca wrote: [1]: https://wiki.debian.org/ReproducibleBuilds diff -urNp python-pypump-0.6.old/debian/rules python-pypump-0.6/debian/rules --- python-pypump-0.6.old/debian/rules2015-05-13 14:48:10.0 -0300 +++ python-pypump-0.6/debian/rules2015-06-11 22:30:19.454056240 -0300 @@ -2,6 +2,10 @@ PYTHONS:=$(shell pyversions -vr) PYTHON3S:=$(shell py3versions -vr) +LAST_CHANGE = $(shell dpkg-parsechangelog -S Date) +BUILD_DATE = $(shell LC_ALL=C date -u +%B %d, %Y -d $(LAST_CHANGE)) +SPHINXOPTS := -D today=\$(BUILD_DATE)\ + %: dh $@ --buildsystem=python_distutils --with python2,python3,sphinxdoc @@ -12,7 +16,7 @@ override_dh_clean: override_dh_auto_build: dh_auto_build - make -C docs html + make -C docs html SPHINXOPTS=$(SPHINXOPTS) # # This version pypump-shell needs the path $HOME/.config/ # # to exist for it to build correctly, so I'm adding it -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#729649: cegui-mk2 - tagging pending bugs
Control: -1 tags pending A cegui-mk2 package fixing this is now in NEW https://ftp-master.debian.org/new/cegui-mk2_0.8.4-1.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788515: ruby-http-accept-language: FTBFS due to lack of build dependencies for tests
Package: ruby-http-accept-language Version: 2.0.5-2 Severity: serious Tags: patch Justification: fails to build from source (but built successfully in the past) User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu wily ubuntu-patch Dear Maintainer, ruby-http-accept-language currently FTBFS in unstable because it doesn't build-depend on certain packages that are required for the tests to run. In Ubuntu, the attached patch was applied to achieve the following: * Build-depend on ruby-i18n and ruby-activesupport to fix tests. Thanks for considering the patch. Logan Rosen -- System Information: Debian Release: jessie/sid APT prefers wily-updates APT policy: (500, 'wily-updates'), (500, 'wily-security'), (500, 'wily'), (100, 'wily-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.19.0-20-generic (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) diff -Nru ruby-http-accept-language-2.0.5/debian/control ruby-http-accept-language-2.0.5/debian/control --- ruby-http-accept-language-2.0.5/debian/control 2014-10-25 02:33:21.0 -0700 +++ ruby-http-accept-language-2.0.5/debian/control 2015-06-12 01:08:08.0 -0700 @@ -3,7 +3,7 @@ Priority: optional Maintainer: Debian Ruby Extras Maintainers pkg-ruby-extras-maintain...@lists.alioth.debian.org Uploaders: Anish A aneesh...@gmail.com -Build-Depends: debhelper (= 7.0.50~), gem2deb (= 0.10~), ruby-rspec-core, ruby-rack-test +Build-Depends: debhelper (= 7.0.50~), gem2deb (= 0.10~), ruby-rspec-core, ruby-rack-test, ruby-i18n, ruby-activesupport Standards-Version: 3.9.6 Vcs-Git: git://anonscm.debian.org/pkg-ruby-extras/ruby-http-accept-language.git Vcs-Browser: http://anonscm.debian.org/gitweb?p=pkg-ruby-extras/ruby-http-accept-language.git;a=summary
Bug#781789: I: [boinc_alpha] I: Bug#781789: boinc-manager: Boinc Manager seems to drop a configuration file into the home directory without hiding it
Control: reassign -1 wxwidgets Control: found -1 3.0.2-2 thanks Hi Wxwidgets maintainers, according to boinc/upstream this might be likely a wx issue, or a wx wrong usage :) cheers, G. Il Giovedì 11 Giugno 2015 10:21, David Anderson da...@ssl.berkeley.edu ha scritto: According to Rom, the file name is based on the app name supplied to WxWidgets, namely line 206 of BOINCGUIApp.cpp: SetAppName(wxT(BOINC Manager)); The functions for reading/writing config info (like window size and position) are members of the class WxConfigBase. Wx stores this info in a file on Unix; on Win, it uses the registry. -- David On 11-Jun-2015 1:02 AM, Gianfranco Costamagna wrote: Hi David, do you know where on the code the file is created? (I would like to reassign to wx, but I need prior to have a reduced testcase) thanks! Gianfranco Il Mercoledì 10 Giugno 2015 20:43, David Anderson da...@ssl.berkeley.edu ha scritto: This config file is create by WxWidgets, so its lack of leading . should be considered a WxWidgets bug. -- David On 03-Apr-2015 1:36 AM, Gianfranco Costamagna wrote: Hi Boinc developers, this bug seems to be an upstream one... can you please look at it? thanks Gianfranco Il Venerdì 3 Aprile 2015 6:33, kittyofthebox kittyofthe...@gmail.com ha scritto: Package: boinc-manager Version: 7.4.23+dfsg-1 Severity: minor Hi, It appears that Boinc Manager drops a configuration file into the home directory without hiding it: $ file /home/user/BOINC\ Manager-user /home/user/BOINC Manager-user: ASCII text, with no line terminators I think this file should begin with a dot to hide it from display in the home directory or be moved to a sub directory in a hidden directory in home. Kitty -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (750, 'testing'), (700, 'testing'), (650, 'stable'), (600, 'stable'), (450, 'oldstable'), (400, 'oldstable'), (300, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages boinc-manager depends on: ii boinc-client 7.4.23+dfsg-1 ii libboinc7 7.4.23+dfsg-1 ii libc6 2.19-17 ii libgcc11:4.9.2-10 ii libglib2.0-0 2.42.1-1 ii libgtk2.0-02.24.25-3 ii libnotify4 0.7.6-2 ii libsqlite3-0 3.8.7.1-1 ii libstdc++6 4.9.2-10 ii libwxbase3.0-0 3.0.2-1+b1 ii libwxgtk-webview3.0-0 3.0.2-1+b1 ii libwxgtk3.0-0 3.0.2-1+b1 boinc-manager recommends no packages. Versions of packages boinc-manager suggests: ii libgl1-mesa-glx 10.3.2-1 ii libxt6 1:1.1.4-1+b1 -- no debconf information ___ boinc_alpha mailing list boinc_al...@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha To unsubscribe, visit the above URL and (near bottom of page) enter your email address. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788510: ooniprobe: [INTL:ru] Russian debconf templates translation
Package: ooniprobe Version: 1.3.1-2 Severity: wishlist Tags: l10n patch 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 *** Russian debconf templates translation is attached. -- System Information: Debian Release: 8.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf, armel Kernel: Linux 3.16.0-4-amd64 (SMP w/8 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) ru.po.gz Description: application/gzip
Bug#781165: ITP: prospector -- Python code analysis tool
On 12.06.2015 07:43, Joseph Herlant wrote: Hi Daniel, FYI pylint-django and pylint-plugins-utils are now in unstable. Joseph GREAT! That's really great news! Thank you very much! Best, Daniel -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788509: remmina-plugin-rdp: Clipboard sync sometimes not working
Package: remmina-plugin-rdp Version: 1.1.1-2 Severity: normal Hi, I have honestly no idea where to start looking, so I'm filing this with the hope of someone having a great idea. In about 50% of the cases connecting to the very same server (using a preconfigured connection) the RDP clipboard sync just does not work. No content is synced. There is no visible error message. It is not consistent across server, network location, being the first or an additional session, being a fresh or resumed session. I could not make out any rule. The destination is usually Windows 2008R2. xfreerdp /... +clipboard works all the time on the affected servers. This is also happening with remmina from unstable (1.1.2-2+b1 at this time). Bernhard -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788034: aptdaemon: Uses obsolete vte3 which is going away
Source: aptdaemon Followup-For: Bug #788034 This is fixed in git upstream by commit http://bazaar.launchpad.net/~aptdaemon-developers/aptdaemon/main/revision/981 Regards, Rodolphe -- 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=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (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#788242: wheezy-pu: package rawtherapee/4.0.9-4
Control: tags -1 + pending On 2015-06-09 19:16, Adam D. Barratt wrote: Control: tags -1 + confirmed On Tue, 2015-06-09 at 19:53 +0200, Philip Rinn wrote: rawtherapee is affected by the security issue CVE-2015-3885. It's marked no-dsa that's why I want to coordinate the update with you. I attached the debdiff. +rawtherapee (4.0.9-4+deb7u1) wheezy-security; urgency=high + + * Add patch debian/patches/04-fix_CVE-2015-3885.patch: +- Fix dcraw imput sanitization errors (CVE-2015-3885) As with the jessie update, please drop -security from the distribution and go ahead. Uploaded and 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#788513: aufs-tools: FTBFS: linux/aufs_type.h: No such file or directory
Source: aufs-tools Version: 1:3.2+20130722-1.1 Severity: serious From my pbuilder build log: ... debian/rules build dh build dh_testdir dh_auto_configure dh_auto_build make -j1 make[1]: Entering directory '/tmp/buildd/aufs-tools-3.2+20130722' cc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -I./libau -O -Wall -D_FORTIFY_SOURCE=2 -DMOUNT_CMD_PATH=\\ -Wl,-z,relro ver.c -o ver ver.c:19:29: fatal error: linux/aufs_type.h: No such file or directory #include linux/aufs_type.h ^ compilation terminated. builtin: recipe for target 'ver' failed make[1]: *** [ver] Error 1 make[1]: Leaving directory '/tmp/buildd/aufs-tools-3.2+20130722' dh_auto_build: make -j1 returned exit code 2 debian/rules:4: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 -- Daniel Schepler -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788522: netsniff-ng: cannot update geoip-database
Package: netsniff-ng Version: 0.5.8-2 Severity: important Dear Maintainer, I've installed netsniff-ng to use astraceroute and I'm unable to do so. While trying to use it, I get: $ sudo astraceroute -i eth0 -N -S -H netsniff-ng.org Cannot open GeoIP4 city database, try --update! And hence I tried: $ sudo astraceroute -u Cannot get /GeoIP.dat.gz from mirrors! This does not happen with the version 5.9-1 in testing (it updates just fine). The reason is probably that 5.8 does not send Connection: close in its HTTP request (and 5.9 does). Cheers, Tomasz -- System Information: Debian Release: 8.1 APT prefers stable APT policy: (990, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-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/bash Init: systemd (via /run/systemd/system) Versions of packages netsniff-ng depends on: ii libc62.19-18 ii libcli1.91.9.7-1 ii libgeoip11.6.2-4 ii libncurses5 5.9+20140913-1+b1 ii libnet1 1.1.6+dfsg-3 ii libnetfilter-conntrack3 1.0.4-1 ii libnl-3-200 3.2.24-2 ii libnl-genl-3-200 3.2.24-2 ii libpcap0.8 1.6.2-2 ii libtinfo55.9+20140913-1+b1 ii liburcu2 0.8.5-1 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages netsniff-ng recommends: ii ntp 1:4.2.6.p5+dfsg-7 netsniff-ng 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#788498: udev: breaks the keyboard configuration
Control: severity -1 normal Control: tag -1 moreinfo Hello Vincent, Vincent Lefevre [2015-06-11 23:51 +0200]: Severity: grave Justification: renders package unusable This bug is highly hardware specific and specific to local configuration, so it does only affect very few people. It also does not render udev completely useless, it just affects a few keys. According to /lib/udev/hwdb.d/60-keyboard.hwdb, it seems that the format has changed (though nothing has been announced!). Right, keyboard: got changed to evdev: in https://github.com/systemd/systemd/commit/51c0c2869 As I saw lines starting with evdev:input:b0003 in this file for USB devices, I tried: evdev:input:b0003v05ACp0221* KEYBOARD_KEY_70035=102nd # Left to z: backslash bar KEYBOARD_KEY_70064=grave # Left to 1: grave notsign KEYBOARD_KEY_70068=insert # F13: Insert Matching on the hardcoded bus ID 0003 seems unnecessary and it might even be wrong. Please check lsusb/lspci if that keyboard is really on the bus 3; But as this doesn't seem important, just try evdev:input:b*v05ACp0221* instead? If that still does not work, can you please check cat /sys/class/input/event1/device/modalias for the actual modalias of that device? (Replace event1 with the actual keyboard) That's the one that the rule above needs to match. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788471: elasticsearch: CVE-2015-4165: unspecified arbitrary files modification vulnerability
Hi Hilko, On Fri, Jun 12, 2015 at 01:30:28PM +0200, Hilko Bengen wrote: Control: tags -1 moreinfo * Salvatore Bonaccorso: Source: elasticsearch Version: 1.0.3+dfsg-5 Severity: grave Tags: security upstream fixed-upstream Where exactly has it been fixed upstream? A git coommit id would be helpful. I haven't a specific commit. The only information I had so far is that upstream claims that affected versions are all 1.0.0 up to 1.5.2 and the issue is fixed in 1.6.0: See https://www.elastic.co/community/security/ Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788358: unattended-upgrades: Automatic-Reboot function is now broken
Ok, thanks. Will this fix be applied to my existing Jessie installation somehow via the usual apt-get upgrade? On 12 June 2015 at 12:09, Michael Vogt m...@debian.org wrote: This got fixed in version 0.83.4:
Bug#788525: git-remote-https segfault involving libgnutls
Package: libgnutls-deb0-28 Version: 3.3.15-5 Severity: grave Justification: breaks other package In my setup, a simple git ls-remote https://github.com/irmen/Pyro4.git; (or any https repo I had) would silently die, with only strace revealing git-remote-https segfaulting. gdb shows: Reading symbols from /usr/lib/git-core/git-remote-https...(no debugging symbols found)...done. [New LWP 26284] [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/i386-linux-gnu/i686/cmov/libthread_db.so.1. Core was generated by `git-remote-https origin https://github.com/irmen/Pyro4.git'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0xb73e2788 in nettle_yarrow256_update () from /usr/lib/i386-linux-gnu/libnettle.so.4 (gdb) bt #0 0xb73e2788 in nettle_yarrow256_update () from /usr/lib/i386-linux-gnu/libnettle.so.4 #1 0xb7356641 in do_device_source (init=optimized out, event=0xbfadc770, ctx=0xb73becc0 rnd_ctx) at rnd.c:147 #2 0xb7356804 in wrap_nettle_rnd_init (ctx=0xb73beedc gnutls_rnd_ctx) at rnd.c:241 #3 0xb72bf3e6 in _gnutls_rnd_init () at random.c:49 #4 0xb72b2d6d in gnutls_global_init () at gnutls_global.c:272 #5 0xb7293534 in lib_init () at gnutls_global.c:434 #6 0xb77d086e in call_init (l=optimized out, argc=argc@entry=3, argv=argv@entry=0xbfadc8e4, env=env@entry=0xbfadc8f4) at dl-init.c:78 #7 0xb77d0964 in call_init (env=0xbfadc8f4, argv=0xbfadc8e4, argc=3, l=optimized out) at dl-init.c:36 #8 _dl_init (main_map=0xb77e2930, argc=3, argv=0xbfadc8e4, env=0xbfadc8f4) at dl-init.c:126 #9 0xb77c2d3f in _dl_start_user () from /lib/ld-linux.so.2 (gdb) info threads Id Target Id Frame * 1Thread 0xb6e2c700 (LWP 26284) 0xb73e2788 in nettle_yarrow256_update () from /usr/lib/i386-linux-gnu/libnettle.so.4 (gdb) ... and when I downgrade to 3.3.8-6+deb8u1 from stable, the segfault does away. Anything to do with that nettle transition that should only affect unstable ? My testing install doesn't seem to have any stuff from unstable related to that... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788530: entr: New version 3.2 available
Package: entr Version: 3.2 Severity: wishlist Dear Maintainer, I noticed that http://entrproject.org/ shows the latest version of this package to be 3.2, but 2.6 is in testing. I normally wouldn't mention this, but 2.6 came out over a year ago and I'm surprised that the latest version has apparently either not been packaged or hasn't made it to testing yet. Would you please package the latest version? Perhaps the watch file needs to be updated. Thanks. -- System Information: Debian Release: jessie/sid APT prefers trusty-updates APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 'trusty'), (100, 'trusty-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-33-lowlatency (SMP w/8 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788531: jessie-pu: package postgresql-9.4/9.4.4-0+deb8u1
Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu Hi, postgresql minor releases are just being released. Here's the new package for jessie: postgresql-9.4 (9.4.4-0+deb8u1) jessie; urgency=medium * New upstream version. + Fix possible failure to recover from an inconsistent database state + Fix rare failure to invalidate relation cache init file -- Christoph Berg m...@debian.org Thu, 11 Jun 2015 20:35:19 +0200 Christoph -- c...@df7cb.de | http://www.df7cb.de/ signature.asc Description: Digital signature
Bug#788520: libobrender 3.6.0-1 is binary incompatible with previous versions but no ABI changed
Package: libobrender29 Version: 3.6.0-1 Severity: grave This is actually an upstream bug but it is a problem because it makes any of packages dependent on libobrender29 broken completely, any application compiled using libobrender29 version 3.5.x will crash using libobrender29 version 3.6.0-1. There are only two ways to deal with this problem: 1) patch upstream file configure.ac in openbox source package changing the values: RR_MICRO_VERSION=31 -RR_INTERFACE_AGE=2 -RR_BINARY_AGE=2 +RR_INTERFACE_AGE=0 +RR_BINARY_AGE=0 RR_VERSION=$RR_MAJOR_VERSION.$RR_MINOR_VERSION which will bump ABI to 31 (therefore libobrender29 becomes libobrender31) and make sure libobrender29 vesrion 3.6.0-1 never come into testing. 2) request a bump version from every dependent package where the package will set dependency on libobrender29 (= 3.6.0-1) and in libobrender29 set Breaks: the_package ( new_version) against each dependent package (or otherwise package manager would never upgrade any dependent package). I believe the second way is ugly and inacceptable one. I've mailed to upstream list about broken ABI and I hope they will release fixed version shortly, until then I suggest to fix the openbox source package instead. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788386: libprocps3-dev:amd64, libprocps3-dev:i386 not coinstallable
On Wed, Jun 10, 2015 at 11:50:42PM +0300, Sami Liedes wrote: libprocps3-dev cannot currently be installed for multiple architectures, causing inconvenience if one wishes to compile procps code for both 32-bit and 64-bit: I can see its due to libprocps3-dev conflicting with all other libprocps-devs and supplying it. I'm not sure what the answer is though. - Craig -- Craig Small (@smallsees) http://enc.com.au/ csmall at : enc.com.au Debian GNU/Linux http://www.debian.org/ csmall at : debian.org GPG fingerprint:5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#786834: fixed-upstream
Control: tags -1 + upstream fixed-upstream The fix is in master branch: https://git.gnome.org/browse/geocode-glib/commit/?id=e11087fcc85a0ce9bfe49cfd460ef97caceb00c1 This same commit for 3.16 branch (added after 3.16.2 release): https://git.gnome.org/browse/geocode-glib/commit/?h=gnome-3-16id=f7a24c1c90c6ac326403ad6e0a7ca28d304f7ee8 Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788447: argyll: FTBFS on mips64el
tags 788447 + pending thanks Hi James, thank you for spending your time helping to make Debian better with this bug report. Am Donnerstag, den 11.06.2015, 15:24 +0100 schrieb James Cowgill: [...] Hi, argyll FTBFS on mips64el because the relevant multiarch include / libs directory isn't checked as part of 15_jam.patch The multiarch paths for mips64el are: /usr/include/mips64el-linux-gnuabi64 /usr/lib/mips64el-linux-gnuabi64 Done in version 1.7.0+repack-3. However adding more stuff to this list for every architecture seems a bit fragile to me. Does JAM have any way of doing this for you? Is it possible to use something like pkg-config instead? No jam / ftjam does not have any multiarch support. :( Thanks, James CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old pgp Key: BE581B6E (revoked since 2014-12-31). Jörg Frings-Fürst D-54526 Niederkail Threema: SYR8SJXB IRC: j_...@freenode.net j_...@oftc.net My wish list: - Please send me a picture from the nature at your home. signature.asc Description: This is a digitally signed message part
Bug#788358: unattended-upgrades: Automatic-Reboot function is now broken
On Wed, Jun 10, 2015 at 04:12:39PM +0100, coder5 wrote:
Package: unattended-upgrades
Version: 0.83.3.1
Severity: normal
Thanks for your bugreport.
The update-notifier-common package has been removed from Jessie and as a
result, /var/run/reboot-required will never be created. Consequently, the
Automatic-Reboot option will never cause the system to reboot after an
upgrade which requires one.
Therefore unattended-upgrades needs some other way of determining if the
system needs a post-upgrade reboot.
This got fixed in version 0.83.4:
unattended-upgrades (0.83.4) unstable; urgency=medium
[ Alexandre Detiste ]
* fix sending dpkg log in mails (Closes: #776752)
[ Michael Vogt ]
* Document how the reboot-required file is generated (Closes: #776769)
* Add recommends to cron|cron-daemon|anacron (Closes: #776550),
thanks to Alexandre Detiste and christophe
* Ship /etc/kernel/postinst.d hook to ensure the
/var/run/reboot-required file is created (avoid the need to have
update-notifier-common installed) (Closes: #776769)
-- Michael Vogt m...@debian.org Tue, 10 Feb 2015 13:58:26 +0100
-- System Information:
Debian Release: 8.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages unattended-upgrades depends on:
ii apt1.0.9.8
ii apt-utils 1.0.9.8
ii debconf [debconf-2.0] 1.5.56
ii init-system-helpers1.22
ii lsb-base 4.1+Debian13+nmu1
ii lsb-release4.1+Debian13+nmu1
ii python33.4.2-2
ii python3-apt0.9.3.11
ii ucf3.0030
ii xz-utils 5.1.1alpha+20120614-2+b3
unattended-upgrades recommends no packages.
Versions of packages unattended-upgrades suggests:
ii bsd-mailx 8.1.2-0.20141216cvs-2
ii exim4-daemon-light [mail-transport-agent] 4.84-8
-- Configuration Files:
/etc/apt/apt.conf.d/50unattended-upgrades changed:
// Automatically upgrade packages from these (origin:archive) pairs
Unattended-Upgrade::Allowed-Origins {
${distro_id}:${distro_codename}-security;
${distro_id}:${distro_codename}-updates;
//${distro_id}:${distro_codename}-proposed;
//${distro_id}:${distro_codename}-backports;
};
// List of packages to not update (regexp are supported)
Unattended-Upgrade::Package-Blacklist {
//vim;
//libc6;
//libc6-dev;
//libc6-i686;
};
// This option allows you to control if on a unclean dpkg exit
// unattended-upgrades will automatically run
// dpkg --force-confold --configure -a
// The default is true, to ensure updates keep getting installed
//Unattended-Upgrade::AutoFixInterruptedDpkg false;
// Split the upgrade into the smallest possible chunks so that
// they can be interrupted with SIGUSR1. This makes the upgrade
// a bit slower but it has the benefit that shutdown while a upgrade
// is running is possible (with a small delay)
//Unattended-Upgrade::MinimalSteps true;
// Install all unattended-upgrades when the machine is shuting down
// instead of doing it in the background while the machine is running
// This will (obviously) make shutdown slower
//Unattended-Upgrade::InstallOnShutdown true;
// Send email to this address for problems or packages upgrades
// If empty or unset then no email is sent, make sure that you
// have a working mail setup on your system. A package that provides
// 'mailx' must be installed. E.g. u...@example.com
//Unattended-Upgrade::Mail root;
// Set this value to true to get emails only on errors. Default
// is to always send a mail if Unattended-Upgrade::Mail is set
//Unattended-Upgrade::MailOnlyOnError true;
// Do automatic removal of new unused dependencies after the upgrade
// (equivalent to apt-get autoremove)
//Unattended-Upgrade::Remove-Unused-Dependencies false;
Unattended-Upgrade::Remove-Unused-Dependencies true;
// Automatically reboot *WITHOUT CONFIRMATION*
// if the file /var/run/reboot-required is found after the upgrade
//Unattended-Upgrade::Automatic-Reboot false;
Unattended-Upgrade::Automatic-Reboot true;
// If automatic reboot is enabled and needed, reboot at the specific
// time instead of immediately
// Default: now
//Unattended-Upgrade::Automatic-Reboot-Time 02:00;
// Use apt bandwidth limit feature, this example limits the download
// speed to 70kb/sec
//Acquire::http::Dl-Limit 70;
-- debconf information:
* unattended-upgrades/enable_auto_updates: true
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788524: lxappearance-obconf depends on broken libobrender29
Package: lxappearance-obconf Version: 0.2.2-2 Severity: grave The latest package in sid is built against openbox library libobrender29 version 3.6.0-1 with broken ABI (see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788520) and therefore version 0.2.2-2 of lxappearance-obconf should never come to the testing distribution until mentioned problem is fixed. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788171: libvirt-daemon: segfault in libvirtd on qemu live migration
On Tue, Jun 09, 2015 at 03:05:51AM +0300, Vladimir Kudrya wrote: Package: libvirt-daemon Version: 1.2.9-9 Severity: important Dear Maintainer, I can confirm that the archived bug #773503 is not fixed. libvirtd still segfaults on live migration. Last message in #773503 may give some clue. Did you test the patch in this bug report successfully? -- Guido Thank you! -- System Information: Debian Release: 8.0 APT prefers stable APT policy: (900, 'stable'), (400, 'testing'), (300, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libvirt-daemon depends on: ii libapparmor12.9.0-3 ii libaudit1 1:2.4-1+b1 ii libavahi-client30.6.31-5 ii libavahi-common30.6.31-5 ii libblkid1 2.25.2-6 ii libc6 2.19-18 ii libcap-ng0 0.7.4-2 ii libdbus-1-3 1.8.16-1 ii libdevmapper1.02.1 2:1.02.90-2.2 ii libfuse22.9.3-15+deb8u1 ii libgnutls-deb0-28 3.3.8-6 ii libnetcf1 1:0.2.3-4.1 ii libnl-3-200 3.2.24-2 ii libnl-route-3-200 3.2.24-2 ii libnuma12.0.10-1 ii libparted2 3.2-7 ii libpcap0.8 1.6.2-2 ii libpciaccess0 0.13.2-3+b1 ii librados2 0.80.7-2 ii librbd1 0.80.7-2 ii libsasl2-2 2.1.26.dfsg1-13 ii libselinux1 2.3-2 ii libssh2-1 1.4.3-4.1 ii libsystemd0 215-17+deb8u1 ii libudev1215-17 ii libvirt01.2.9-9 ii libxen-4.4 4.4.1-9 ii libxenstore3.0 4.4.1-9 ii libxml2 2.9.1+dfsg1-5 ii libyajl22.1.0-2 Versions of packages libvirt-daemon recommends: pn libxml2-utils none ii netcat-openbsd 1.105-7 ii qemu-kvm1:2.1+dfsg-12 Versions of packages libvirt-daemon suggests: ii libvirt-daemon-system 1.2.9-9 -- 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#786652: fails to include TEMPLATE.kvm, preventing creation of domains with KVM under apparmor
On Sun, May 24, 2015 at 09:56:50AM +0200, Guido Günther wrote:
Hi,
Thanks for the report
On Sun, May 24, 2015 at 01:00:52AM +, Luke Faraone wrote:
Package: libvirt-daemon-system
Version: 1.2.9-9
Severity: normal
File: /etc/apparmor.d/libvirt/TEMPLATE.qemu
May 24 00:07:47 aqua libvirtd[1130]: internal error: Child process
(/usr/lib/libvirt/virt-aa-helper -p 0 -c -u libvirt-a8588abe-9d3b-4772-a95e-
0e312decc03a) unexpected exit status 1: virt-aa-helper.real: error: template
does not exist
This can be resolved by copying /etc/apparmor.d/libvirt/TEMPALTE.qemu to
/etc/apparmor.d/libvirt/TEMPALTE.kvm
Could you check if the attached patch fixes your problem as well?
Could you please check if the packages at:
http://honk.sigxcpu.org/projects/libvirt/snapshots/
make these copies superfluous. You should be able to remove the
TEMPLATE.kvm with these installed. Feedback would be appreciated so we
could squeeze this into a point release.
Cheers,
-- Guido
Cheers,
-- Guido
From 16d2bc8b98563f801f111795250515fcbd39ab46 Mon Sep 17 00:00:00 2001
Message-Id:
16d2bc8b98563f801f111795250515fcbd39ab46.1432454102.git@sigxcpu.org
From: =?UTF-8?q?C=C3=A9dric=20Bosdonnat?= cbosdon...@suse.com
Date: Tue, 28 Oct 2014 14:42:34 -0600
Subject: [PATCH] Teach virt-aa-helper to use TEMPLATE.qemu if the domain is
kvm or kqemu
To: libvir-l...@redhat.com
Status: RO
Content-Length: 1123
Lines: 37
---
src/security/virt-aa-helper.c | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/src/security/virt-aa-helper.c b/src/security/virt-aa-helper.c
index 9afc8db..1f299a0 100644
--- a/src/security/virt-aa-helper.c
+++ b/src/security/virt-aa-helper.c
@@ -341,15 +341,25 @@ create_profile(const char *profile, const char
*profile_name,
int tlen, plen;
int fd;
int rc = -1;
+const char *driver_name = NULL;
if (virFileExists(profile)) {
vah_error(NULL, 0, _(profile exists));
goto end;
}
+switch (virtType) {
+case VIR_DOMAIN_VIRT_QEMU:
+case VIR_DOMAIN_VIRT_KQEMU:
+case VIR_DOMAIN_VIRT_KVM:
+driver_name = qemu;
+break;
+default:
+driver_name = virDomainVirtTypeToString(virtType);
+}
if (virAsprintfQuiet(template, %s/TEMPLATE.%s, APPARMOR_DIR
/libvirt,
- virDomainVirtTypeToString(virtType)) 0) {
+ driver_name) 0) {
vah_error(NULL, 0, _(template name exceeds maximum length));
goto end;
}
--
2.1.4
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788526: udisks2: Unable to allow non-admin user to mount a volume
Package: udisks2
Version: 2.1.5-3
Severity: normal
Dear Maintainer,
I'm interested in letting a normal user mount certain type of LVM snapshot
(basically to allow free access to backups). As indicated by udisks'
documentation, a normal user is only allowed to mount non-system volumes (cf
http://udisks.freedesktop.org/docs/latest/udisks-polkit-actions.html).
So I added the following udev rule :
$ cat /etc/udev/rules.d/90-lvm.rules
ENV{DM_LV_NAME}==SNAP-?_TV_HOME, ENV{UDISKS_NAME}=SNAP_HOME-latest,
ENV{UDISKS_AUTO}=1, ENV{UDISKS_SYSTEM}=0
However this not working, udisks2 asks me for a administrative password, even
though the udev rule above did its work :
$ udisksctl dump
/org/freedesktop/UDisks2/block_devices/dm_2d11:
org.freedesktop.UDisks2.Block:
Configuration: []
CryptoBackingDevice:'/'
Device: /dev/dm-11
DeviceNumber: 65035
Drive: '/'
HintAuto: true
HintIconName:
HintIgnore: false
HintName: SNAP_HOME-latest
HintPartitionable: false
HintSymbolicIconName:
HintSystem: false
Id: by-id-dm-name-PC_VG1-SNAP--1_TV_HOME
IdLabel:TV_HOME
IdType: ext4
IdUUID: 13d69be4-520c-49d4-a71f-a1d4b7153ea5
IdUsage:filesystem
IdVersion: 1.0
MDRaid: '/'
MDRaidMember: '/'
PreferredDevice:/dev/PC_VG1/SNAP-1_TV_HOME
ReadOnly: false
Size: 21474836480
Symlinks: /dev/PC_VG1/SNAP-1_TV_HOME
/dev/disk/by-id/dm-name-PC_VG1-SNAP--1_TV_HOME
/dev/disk/by-id/dm-uuid-LVM-
A2qpzUNTI28ewKaGv3XCiiuZT9ud4hC0aH2brUjYgTTKsdk6flkGw3zXjvWT2RKW
/dev/disk/by-label/TV_HOME
/dev/disk/by-uuid/13d69be4-520c-49d4-a71f-
a1d4b7153ea5
/dev/mapper/PC_VG1-SNAP--1_TV_HOME
According to the polkit policy installed, a normal user should be allowed to
mount non-system volume.
My research on the web led me to a similar issue reported by Arch users :
https://bbs.archlinux.org/viewtopic.php?id=169220
Regards
H. Werner
-- System Information:
Debian Release: stretch/sid
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-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/dash
Init: systemd (via /run/systemd/system)
Versions of packages udisks2 depends on:
ii dbus 1.8.18-1
ii libacl12.2.52-2
ii libatasmart4 0.19-3
ii libc6 2.19-18
ii libglib2.0-0 2.44.1-1
ii libgudev-1.0-0 230-1
ii libpam-systemd 215-18
ii libpolkit-agent-1-00.105-8
ii libpolkit-gobject-1-0 0.105-8
ii libsystemd0215-18
ii libudisks2-0 2.1.5-3
ii parted 3.2-7
ii udev 215-18
Versions of packages udisks2 recommends:
ii dosfstools 3.0.28-1
ii eject2.1.5+deb1+cvs20081104-13.1
ii gdisk1.0.0-2
ii ntfs-3g 1:2014.2.15AR.3-3
ii policykit-1 0.105-8
Versions of packages udisks2 suggests:
pn btrfs-tools none
ii cryptsetup-bin 2:1.6.6-5
pn exfat-utils none
pn mdadm none
pn reiserfsprogs none
pn xfsprogsnone
-- 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#780093: libvirt: error: unsupported configuration: QEMU 2.1.2 is too new for help parsing
On Thu, Jun 11, 2015 at 03:00:29PM -0400, Elana Hashman wrote: Just wanted to chime in that I am encountering the same error on a `virsh define container.xml` But I also see ehashman@host:~$ virt-xml-validate container.xml container.xml validates This machine is running Debian jessie, libvirt-bin: 1.2.9-9 QEMU:2.1.2 (Debian 1:2.1+dfsg-12) Linux: 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1 (2015-05-24) x86_64 GNU/Linux I was able to successfully run the above command on another slightly out-of-date jessie machine with the following package versions: libvirt-bin: 1.2.7-10+b1 QEMU:2.1.0 (Debian 2.1+dfsg-2) Linux: 3.14-2-amd64 #1 SMP Debian 3.14.15-2 (2014-08-09) x86_64 GNU/Linux Unlike the above reporter, my VM is only using 1024MB RAM and no chroot. Because the machine having issues is a recent install, I can't downgrade my packages, so I don't have a solution to this problem. Please somebody who's seeing this problem apply the patch mentioned by Han and report the error message you see there. Without me being able to reproduce this is just not progressing anywhere. -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788528: nsd-control-setup stops initial key generating with openssl: not found
Source: nsd Version: 4.1.0-3 Severity: normal Dear Ondřej, after install of nsd under a new fresh Debian minimal installation i would like to start the inital key generation for nsd-control with nsd-control-setup. The key generation stops with the following error: ~# nsd-control-setup setup in directory /etc/nsd generating nsd_server.key /usr/sbin/nsd-control-setup: 98: /usr/sbin/nsd-control-setup: openssl: not found /usr/sbin/nsd-control-setup fatal error: could not genrsa I installed the missing package openssl with apt-get install openssl and start nsd-control-setup again without errors. # nsd-control-setup setup in directory /etc/nsd generating nsd_server.key Generating RSA private key, 1536 bit long modulus . e is 65537 (0x10001) generating nsd_control.key Generating RSA private key, 1536 bit long modulus ... e is 65537 (0x10001) create nsd_server.pem (self signed certificate) create nsd_control.pem (signed client certificate) Signature ok subject=/CN=nsd-control Getting CA Private Key Setup success. Certificates created. Can you add the openssl package as dependency for nsd to correct this problem? Regards Christian -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/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) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788521: please drop eperl from Build-Depends-Indep - not necessary anymore
Source: texlive-base Version: 2015.20150524-1 Severity: wishlist Tags: patch eperl is not necessary (and has not been for quite some time), nothing in the package even mentions it (except debian/changelog, debian/control and debian/tpm2deb.cfg). Please drop it, so that eperl can finally be put out to pasture (last upstream release was in 1998!). Note: This applies to texlive-lang and texlive-extra as well. Cheers, Roderich -- Package-specific info: IMPORTANT INFORMATION: We will only consider bug reports concerning the packaging of TeX Live as relevant. If you have problems with combination of packages in a LaTeX document, please consult your local TeX User Group, the comp.text.tex user group, the author of the original .sty file, or any other help resource. In particular, bugs that are related to up-upstream, i.e., neither Debian nor TeX Live (upstream), but the original package authors, will be closed immediately. *** The Debian TeX Team is *not* a LaTeX Help Desk *** If you report an error when running one of the TeX-related binaries (latex, pdftex, metafont,...), or if the bug is related to bad or wrong output, please include a MINIMAL example input file that produces the error in your report. Please run your example with (pdf)latex -recorder ... (or any other program that supports -recorder) and send us the generated file with the extension .fls, it lists all the files loaded during the run and can easily explain problems induced by outdated files in your home directory. Don't forget to also include minimal examples of other files that are needed, e.g. bibtex databases. Often it also helps to include the logfile. Please, never send included pictures! If your example file isn't short or produces more than one page of output (except when multiple pages are needed to show the problem), you can probably minimize it further. Instructions on how to do that can be found at http://www.minimalbeispiel.de/mini-en.html (english) or http://www.minimalbeispiel.de/mini.html (german) ## minimal input file ## other files ## List of ls-R files -rw-r--r-- 1 root root 3311 Jun 12 11:51 /var/lib/texmf/ls-R -rw-r--r-- 1 root staff 80 Apr 2 20:39 /usr/local/share/texmf/ls-R lrwxrwxrwx 1 root root 29 Jun 10 18:57 /usr/share/texmf/ls-R - /var/lib/texmf/ls-R-TEXMFMAIN lrwxrwxrwx 1 root root 31 Jun 10 21:27 /usr/share/texlive/texmf-dist/ls-R - /var/lib/texmf/ls-R-TEXLIVEDIST lrwxrwxrwx 1 root root 31 Jun 10 21:27 /usr/share/texlive/texmf-dist/ls-R - /var/lib/texmf/ls-R-TEXLIVEDIST ## Config files -rw-r--r-- 1 root root 1464 Jun 11 00:59 /etc/texmf/web2c/texmf.cnf -rw-r--r-- 1 root root 8665 Jun 10 19:18 /var/lib/texmf/web2c/fmtutil.cnf lrwxrwxrwx 1 root root 32 Jun 10 21:27 /usr/share/texmf/web2c/updmap.cfg - /var/lib/texmf/updmap.cfg-DEBIAN -rw-r--r-- 1 root root 4962 Jun 12 11:38 /var/lib/texmf/tex/generic/config/language.dat ## Files in /etc/texmf/web2c/ total 8 -rw-r--r-- 1 root root 283 Apr 16 2008 mktex.cnf -rw-r--r-- 1 root root 1464 Jun 11 00:59 texmf.cnf ## md5sums of texmf.d ca40c66f144b4bafc3e59a2dd32ecb9c /etc/texmf/texmf.d/00debian.cnf 3875bf0f4a53a29b7f247399dc9833e2 /etc/texmf/texmf.d/05TeXMF.cnf.dpkg-bak 6e82a3d4c00ae7e4f86aa8dcf9438cf3 /etc/texmf/texmf.d/15Plain.cnf.dpkg-bak c60a084820a0b73e3bfbf2e90bda437c /etc/texmf/texmf.d/45TeXinputs.cnf.dpkg-bak ea33127256c6a9f37145ae5b16fdb80c /etc/texmf/texmf.d/55Fonts.cnf.dpkg-bak afccf1d3f87057411166a77c58e00bd1 /etc/texmf/texmf.d/65BibTeX.cnf.dpkg-bak 9da7c1c7b1eaf06f941af91f48a23068 /etc/texmf/texmf.d/75DviPS.cnf.dpkg-bak 7ae52efac46feb97010986e57877d12e /etc/texmf/texmf.d/80DVIPDFMx.cnf.dpkg-bak 055e06548bac99958d8ab2dd1248f2b4 /etc/texmf/texmf.d/80tex4ht.cnf 37329819f1109e8a457e64b8b58fecdb /etc/texmf/texmf.d/85Misc.cnf.dpkg-bak a8952d594677235951d447665ec46e9c /etc/texmf/texmf.d/90TeXDoc.cnf.dpkg-bak 402d5adb3864c09ed3cd80c0f2131361 /etc/texmf/texmf.d/95NonPath.cnf.dpkg-bak 1df66bc319cec731e202eaf39f5d85e1 /etc/texmf/texmf.d/96JadeTeX.cnf -- System Information: Debian Release: stretch/sid APT prefers wily APT policy: (500, 'wily'), (500, 'buildd-unstable'), (500, 'unstable'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-rc7 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages tex-common depends on: ii dpkg 1.18.1 ii ucf 3.0030 Versions of packages tex-common suggests: ii debhelper 9.20150519+ddebs Versions of packages texlive-base is related to: ii tex-common6.00 ii texlive-binaries 2015.20150524.37493-1 -- debconf information: texlive-base/texconfig_ignorant:
Bug#787354: license is a documentation issue
severity 787354 normal thankyou The license which is one line in the file was overlooked and incorrect. The upstream authors have confirmed this[1] and for the next upstream release there is a fix is is removing the line[2]. [1] https://bugs.launchpad.net/mudlet/+bug/1404763 [2] https://github.com/Mudlet/Mudlet/pull/227 -- Craig Small (@smallsees) http://enc.com.au/ csmall at : enc.com.au Debian GNU/Linux http://www.debian.org/ csmall at : debian.org GPG fingerprint:5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788498: udev: breaks the keyboard configuration
On 2015-06-12 13:11:45 +0200, Martin Pitt wrote: Vincent Lefevre [2015-06-11 23:51 +0200]: Severity: grave Justification: renders package unusable This bug is highly hardware specific and specific to local configuration, so it does only affect very few people. It also does not render udev completely useless, it just affects a few keys. However, it might prevent the user from logging in if his password has characters that are affected, and since what is typed is not visible, this may be very confusing. I agree that this affects few people, but this can have very bad consequences. Something should be done to make sure that the user is aware of this change, early enough if possible. evdev:input:b0003v05ACp0221* KEYBOARD_KEY_70035=102nd # Left to z: backslash bar KEYBOARD_KEY_70064=grave # Left to 1: grave notsign KEYBOARD_KEY_70068=insert # F13: Insert Matching on the hardcoded bus ID 0003 seems unnecessary and it might even be wrong. Please check lsusb/lspci if that keyboard is really on the bus 3; If it is not on bus ID 0003, this seems to be a documentation bug, because /lib/udev/hwdb.d/60-keyboard.hwdb says: #This matches on the kernel modalias of the input-device, mainly: # is the bus-id (see /usr/include/linux/input.h BUS_*), , and and /usr/include/linux/input.h contains: #define BUS_PCI 0x01 #define BUS_ISAPNP 0x02 #define BUS_USB 0x03 #define BUS_HIL 0x04 #define BUS_BLUETOOTH 0x05 #define BUS_VIRTUAL 0x06 #define BUS_ISA 0x10 #define BUS_I8042 0x11 #define BUS_XTKBD 0x12 #define BUS_RS232 0x13 #define BUS_GAMEPORT0x14 #define BUS_PARPORT 0x15 #define BUS_AMIGA 0x16 #define BUS_ADB 0x17 #define BUS_I2C 0x18 #define BUS_HOST0x19 #define BUS_GSC 0x1A #define BUS_ATARI 0x1B #define BUS_SPI 0x1C BTW, what about all the b0003 in /lib/udev/hwdb.d/60-keyboard.hwdb? [The tests below are done with udev 215-18, as I had to revert.] lsusb gives for the keyboard: Bus 008 Device 003: ID 05ac:0221 Apple, Inc. Aluminum Keyboard (ISO) Does this mean that it is on bus ID 0008? But see below. But as this doesn't seem important, just try evdev:input:b*v05ACp0221* instead? I am not in front of the machine, but I'll try tonight. If this works, using a wildcard for b should be suggested by the documentation. If that still does not work, can you please check cat /sys/class/input/event1/device/modalias for the actual modalias of that device? (Replace event1 with the actual keyboard) That's the one that the rule above needs to match. xvii:~ cat /sys/class/input/event1/device/name Apple, Inc Apple Keyboard xvii:~ cat /sys/class/input/event1/device/modalias input:b0003v05ACp0221e0111-e0,1,4,11,14,k71,72,73,74,75,77,78,79,7A,7B,7C,7D,7E,7F,80,81,82,83,84,85,86,87,88,89,8A,8C,8E,96,98,9E,9F,A1,A3,A4,A5,A6,AD,B0,B1,B2,B3,B4,B8,B9,BA,BB,BC,BD,BE,BF,C0,C1,C2,CC,E0,E1,E3,E4,E5,E6,F0,1D0,ram4,l0,1,2,3,4,sfw So, it seems to be on bus ID 0003. -- 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#782831: libvorbis: use of non-initialized variable leads to SIGSEV in dhewm3
Hi Martin, Did you report this issue already upstream? Could not find it on their BTS... -- tobi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788517: Floating point exception on 0 eeprom size
Package: avrdude
Version: 6.1-2
Severity: important
Tags: patch
Avrdude is crashing on a zero eeprom size:
avrdude -pm128rfa1 -c arduino -P/dev/ttyUSB5 -b57600 -e -U \
flash:w:foo.hex:a -U \
eeprom:w:foo.eep:a
avrdude: AVR device initialized and ready to accept instructions
Reading | ## | 100% 0.00s
avrdude: Device signature = 0x1ea701
avrdude: erasing chip
avrdude: reading input file foo.hex
avrdude: input file foo.hex auto detected as Intel Hex
avrdude: writing flash (60774 bytes):
Writing | ## | 100% 14.50s
avrdude: 60774 bytes of flash written
avrdude: verifying flash memory against foo.hex:
avrdude: load data flash data from input file foo.hex:
avrdude: input file foo.hex auto detected as Intel Hex
avrdude: input file foo.hex contains 60774 bytes
avrdude: reading on-chip flash data:
Reading | ## | 100% 11.19s
avrdude: verifying ...
avrdude: 60774 bytes of flash verified
avrdude: reading input file foo.eep
avrdude: input file foo.eep auto detected as Intel Hex
avrdude: writing eeprom (0 bytes):
Writing | ## | 100% 0.00s
avrdude: 0 bytes of eeprom written
avrdude: verifying eeprom memory against foo.eep:
avrdude: load data eeprom data from input file foo.eep:
avrdude: input file foo.eep auto detected as Intel Hex
avrdude: input file foo.eep contains 0 bytes
avrdude: reading on-chip eeprom data:
Reading || 0%
0.00sMakefile:88: recipe for target 'flash' failed
make: *** [flash] Floating point exception (core dumped)
This is fixed by upstream revision 1340. Tested patch attached.
Cheers,
-- Guido
-- System Information:
Debian Release: 8.0
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'unstable'),
(500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-rc6 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages avrdude depends on:
ii libc6 2.19-18
ii libelf1 0.159-4.2
ii libftdi1 0.20-2
ii libncurses5 5.9+20140913-1+b1
ii libreadline6 6.3-8+b3
ii libtinfo5 5.9+20140913-1+b1
ii libusb-0.1-4 2:0.1.12-25
avrdude recommends no packages.
Versions of packages avrdude suggests:
pn avrdude-doc none
-- no debconf information
From 921d13272d55f8bc1baaf9f86b9fc2b6ee960ca9 Mon Sep 17 00:00:00 2001
Message-Id: 921d13272d55f8bc1baaf9f86b9fc2b6ee960ca9.1434100250.git@sigxcpu.org
From: =?UTF-8?q?Guido=20G=C3=BCnther?= a...@sigxcpu.org
Date: Fri, 12 Jun 2015 10:51:02 +0200
Subject: [PATCH] Avoid division by zero on empty size
---
.../Avoid-division-by-zero-on-empty-size.patch | 25 ++
debian/patches/series | 1 +
2 files changed, 26 insertions(+)
create mode 100644 debian/patches/Avoid-division-by-zero-on-empty-size.patch
diff --git a/debian/patches/Avoid-division-by-zero-on-empty-size.patch b/debian/patches/Avoid-division-by-zero-on-empty-size.patch
new file mode 100644
index 000..62e7992
--- /dev/null
+++ b/debian/patches/Avoid-division-by-zero-on-empty-size.patch
@@ -0,0 +1,25 @@
+From: =?utf-8?q?Guido_G=C3=BCnther?= a...@sigxcpu.org
+Date: Fri, 12 Jun 2015 10:49:52 +0200
+Subject: Avoid division by zero on empty size
+
+Basically a cherry-pick of revision 1340 in SVN fixing a
+floating point exception.
+
+Bug: http://savannah.nongnu.org/bugs/?40142
+---
+ avr.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/avr.c b/avr.c
+index 3b4c872..a04b2da 100644
+--- a/avr.c
b/avr.c
+@@ -1238,7 +1238,7 @@ void report_progress (int completed, int total, char *hdr)
+ {
+ static int last = 0;
+ static double start_time;
+- int percent = (completed * 100) / total;
++ int percent = (total 0) ? ((completed * 100) / total) : 100;
+ struct timeval tv;
+ double t;
+
diff --git a/debian/patches/series b/debian/patches/series
index 999888d..b742fde 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,3 +1,4 @@
0001-Fix-paths-in-the-man-page.patch
0002-FT245R-correct-reset-ftdi_syncbb.patch
0003-Fix-Linux-GPIO-pindefs-typo.patch
+Avoid-division-by-zero-on-empty-size.patch
--
2.1.4
Bug#756867: transition: gdal
On 06/12/2015 07:30 AM, Vincent Danjean wrote: Le 12/06/2015 01:06, Sebastiaan Couwenberg a écrit : On 06/12/2015 12:26 AM, Emilio Pozuelo Monfort wrote: So let's say gdal 1.11 changed the ABI for some C++ symbols. Since the packages currently in sid don't have strict dependencies on the old ABI, the new library will be installed with the old packages, causing breakage. Rebuilding all affected packages should take care of that. Isn't the point of a transition to coordinate the upload of the new library so that the old packages can be rebuilt with it soon after? The time between the upload of the new library and the rebuild of the old packages should be minimal, leaving only a short window in which the old packages may be broken. This is true only if the new version of gdal cannot be installed with old (jessie) version packages using it. I do not known anything about gdal. But remember you cannot assume that users will upgrade in one row from jessie to stretch/testing/unstable. I don't believe partial upgrades are supported, so this seems a mostly theoretical problem. Actual users of gdal and its rdeps will want to be able to use those rdeps so they will be motivated to not do a partial upgrade. GDAL 1.11 is the first version that allows tracking of the rdeps that use the C++ symbols, all earlier upgrades didn't care about that. Those relied on the symbols version only for upgrades. What do you think about that situation? Should we add the dependency magic to 1.10, rebuild everything, and only then update to 1.11? Or do you think that case isn't a problem? I don't think it's worth the effort to rebuild all rdepds twice, if we're going to rebuild them we should just do it for 1.11. Rebuilding rdeps twice wont do anything (but if you push the rebuild with old gdal to stable. I'm not sure release managers will accept) because jessie packages won't change. If I understand the problem correctly, the new version of gdal will probably need to have a versionned Breaks to all packages that must be upgraded with it. It is not enought that packages in sid are coherent, they must also work (or Conflict/Break) with packages in stable. I definitely don't understand your concern. What is your actual real world scenario, so I can better understand your point of view? To my best understanding, distribution upgrades from jessie to stretch will just work, with or without alternative dependency for packages using C++ symbols, as they did before. While I'm not entirely happy being unable to mark all affected packages as good in the tracker, I don't consider it a sufficient problem to add the alternative dependency to gdal 1.10.1 too. If there will be a GDAL 1.11.3 after we get 1.11.2 in unstable and before GDAL 2.0, we can limit the affected packages to those depending on libgdal.so.1-1.11.2. I'm becoming increasingly disillusioned about getting GDAL 1.11 into unstable and thereby gaining the spatialite_init_ex() support, the lack of which is currently causing segfaults because only the deprecated spatialite_init() method is used. The gdal 1.11.2 package is Ubuntu from some time already, and they didn't have these concerns. But that may be inherent to Ubuntu not being as strict as Debian about these kind of issues. I'd hate having to wait for GDAL 2.0 and the SONAME bump that should introduce before getting a newer gdal in unstable. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788519: libqtwebkit4: qtwebkit crash in javascript code on powerpc. quiterss, qupzilla and konqueror exposed
Package: libqtwebkit4 Version: 2.3.4.dfsg-3 Severity: normal Dear Maintainer, The qtwebkit4 crashes randomly in all three apps mainly in javascript code. Konqueror: Thread 1 (Thread 0xf7d332b0 (LWP 7238)): [KCrash Handler] #5 JSC::UnlinkedFunctionExecutable::codeBlockFor (this=0xf3255dc0, globalData=0x20, source=0x0, specializationKind=219145200, debuggerMode=604251176, profilerMode=147602808, error=0xf324) at /build /qtwebkit- d2Y274/qtwebkit-2.3.4.dfsg/Source/JavaScriptCore/heap/WeakSetInlines.h:39 #6 0x08e03e38 in JSC::FunctionExecutable::compileForCallInternal (this=0xf3273000, exec=not saved, scope=not saved, jitType=not saved, bytecodeIndex=unknown type) at /build/qtwebkit- d2Y274/qtwebkit-2.3.4.dfsg/Source/JavaScriptCore/runtime/Executable.cpp:500 #7 0x08d3bf24 in llint_slow_path_call (exec=0x0, pc=0xf1214488) at /build /qtwebkit- d2Y274/qtwebkit-2.3.4.dfsg/Source/JavaScriptCore/runtime/Executable.h:588 #8 0x08d43130 in JSC::LLInt::CLoop::execute (callFrame=0xf5200310, bootstrapOpcodeId=not saved, isInitializationPass=not saved) at generated/LLIntAssembly.h:5748 #9 0x08d27d7c in JSC::Interpreter::execute (this=0xf5fe77e0, program=0xf327ffc0, callFrame=0xf32ef7a8, thisObj=0xf571ffe0) at /build /qtwebkit- d2Y274/qtwebkit-2.3.4.dfsg/Source/JavaScriptCore/interpreter/Interpreter.cpp:980 #10 0x08de53d0 in JSC::evaluate (exec=0xf32ef7a8, source=0xffd02738, thisValue=..., returnedException=0xffd02620) at /build/qtwebkit- d2Y274/qtwebkit-2.3.4.dfsg/Source/JavaScriptCore/runtime/Completion.cpp:75 #11 0x075848ec in WebCore::ScriptController::evaluateInWorld (this=0xf5ff334c, sourceCode=0xffd02734, world=0xf32ef7a8) at /build/qtwebkit- d2Y274/qtwebkit-2.3.4.dfsg/Source/WebCore/bindings/js/JSMainThreadExecState.h:77 #12 0x07584ce8 in WebCore::ScriptController::evaluate (this=not saved, sourceCode=not saved) at /build/qtwebkit- d2Y274/qtwebkit-2.3.4.dfsg/Source/WebCore/bindings/js/ScriptController.cpp:159 #13 0x0781c180 in WebCore::ScriptElement::executeScript(WebCore::ScriptSourceCode const) () at /build/qtwebkit-d2Y274/qtwebkit-2.3.4.dfsg/Source/WTF/wtf/Atomics.cpp:75 #14 0x0781d344 in WebCore::ScriptElement::execute(WebCore::CachedScript*) () at /build/qtwebkit-d2Y274/qtwebkit-2.3.4.dfsg/Source/WTF/wtf/Atomics.cpp:75 #15 0x0782521c in WebCore::ScriptRunner::timerFired(WebCore::TimerWebCore::ScriptRunner*) () at /build/qtwebkit-d2Y274/qtwebkit-2.3.4.dfsg/Source/WTF/wtf/Atomics.cpp:75 #16 0x078246ac in WebCore::TimerWebCore::ScriptRunner::fired() () at /build /qtwebkit-d2Y274/qtwebkit-2.3.4.dfsg/Source/WTF/wtf/Atomics.cpp:75 #17 0x07e5a2c0 in WebCore::ThreadTimers::sharedTimerFiredInternal() [clone ..part.6] () at /build/qtwebkit- d2Y274/qtwebkit-2.3.4.dfsg/Source/WTF/wtf/Atomics.cpp:75 #18 0x0817d878 in WebCore::SharedTimerQt::timerEvent(QTimerEvent*) () at /build /qtwebkit-d2Y274/qtwebkit-2.3.4.dfsg/Source/WTF/wtf/Atomics.cpp:75 #19 0x0dfba584 in QObject::event(QEvent*) () from /usr/lib/powerpc-linux- gnu/libQtCore.so.4 #20 0x0e5f3218 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/powerpc-linux-gnu/libQtGui.so.4 #21 0x0e5fb40c in QApplication::notify(QObject*, QEvent*) () from /usr/lib /powerpc-linux-gnu/libQtGui.so.4 #22 0x0f2ffb88 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #23 0x0df99110 in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/powerpc-linux-gnu/libQtCore.so.4 #24 0x0dfda804 in ?? () from /usr/lib/powerpc-linux-gnu/libQtCore.so.4 #25 0x0dfd6310 in ?? () from /usr/lib/powerpc-linux-gnu/libQtCore.so.4 #26 0x0cfbea44 in g_main_context_dispatch () from /lib/powerpc-linux- gnu/libglib-2.0.so.0 #27 0x0cfbed18 in ?? () from /lib/powerpc-linux-gnu/libglib-2.0.so.0 #28 0x0cfbee20 in g_main_context_iteration () from /lib/powerpc-linux- gnu/libglib-2.0.so.0 #29 0x0dfd7008 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/powerpc-linux-gnu/libQtCore.so.4 #30 0x0e6c453c in ?? () from /usr/lib/powerpc-linux-gnu/libQtGui.so.4 #31 0x0df972d0 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/powerpc-linux-gnu/libQtCore.so.4 #32 0x0df97788 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/powerpc-linux-gnu/libQtCore.so.4 #33 0x0df9f120 in QCoreApplication::exec() () from /usr/lib/powerpc-linux- gnu/libQtCore.so.4 #34 0x0e5f0860 in QApplication::exec() () from /usr/lib/powerpc-linux- gnu/libQtGui.so.4 #35 0x0ffab678 in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_konqueror.so #36 0x0fd63274 in generic_start_main (main=0x14f0, argc=2, argv=0xffd031e4, auxvec=0xffd03284, init=optimized out, rtld_fini=optimized out, stack_end=optimized out, fini=optimized out) at ../csu/libc-start.c:287 #37 0x0fd63434 in __libc_start_main (argc=optimized out, argv=optimized out, ev=optimized out, auxvec=optimized out, rtld_fini=optimized out, stinfo=optimized out, stack_on_entry=optimized out) at
Bug#770470: ignore /var/lib/urandom/random-seed ?
Hi, do people have opinions whether piuparts should ignore /var/lib/urandom/random-seed ? cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#788100: 20141122 is not likely to fix the problem
Hi Tobias, Thanks for looking at the bug. FYI: When I first encountered it, I manually downloaded the last upstream version and tried it. This was not the debian version and I dunno what additional patches you may add but the problem was not fixed (few from memory). I will try your newer package version nevertheless and report. -- eric _ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766921: does this still happen?
tags 766921 + moreinfo thanks Hi, does this still happen in sid or jessie? #770109 (eatmydata should not depend on dpkg-dev) has been fixed in jessie, so assume this is mood. Or do we still need the patch outlined in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766921#35 ? cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#787736: apt-offline: wrong file extension for Packages/Sources files
I have added the bug report back so that your root cause doesn't get lost in our mail box. On Thursday 11 June 2015 06:27 PM, Peter Laird wrote: Another option for fixing bug#787736 is to change the line: AptInst = AptManip(Str_SetArg, Simulate=Bool_TestWindows, AptType=python-apt) to match version 1.6 ie. change to ...AptType=apt It will take me a few days to test this. Thank you for the root cause Peter. I guess this will be the rightest change and should also allow for migration into stable, easily. Upon receiving your test results, I will prepare the upload accordingly. -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention. signature.asc Description: OpenPGP digital signature
Bug#785442: DKMS build fails at linux-4.0.0
On 06/11/2015 03:22 PM, Txo wrote: Le 11/06/2015 13:28, Robert Ramięga a écrit : Try the nvidia-3.19.patch. Works on i686 should work on amd64 too. All is good with nvidia-3.19.patch. I believe that i need only patch 4.0 for kernel 4.nnn. I'm running 4.nn kernel from linux-image-4.0.0-2-686-pae_4.0.4-1_i386.deb and to get this to compile I've only used nvidia-3.19.patch Maybe that other patch was needed on earlier (pre, rc) 4.nnn kernels? Best regards, Robert -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788496: gbp dch should wrap lines
On Thu, Jun 11, 2015 at 11:23:33PM +0200, Guido Günther wrote: tags 788496 +moreinfo thanks On Thu, Jun 11, 2015 at 10:35:46PM +0200, Julian Andres Klode wrote: Package: git-buildpackage Version: 0.6.31 For the python-apt changelog starting from 0.9.4, gbp-dch will produce two long lines, which causes lintian to complain and me having to edit the changelog manually. This is an excerpt of the generated changelog. python-apt (0.9.5) UNRELEASED; urgency=medium [...] [ Michael Vogt ] * apt_pkg.rst: improve documentation for AcquireFile() hash and add sha512 to the documentation * rename md5 keyword argument in AcquireFile() to hash and add backward compatiblity * Fix apt.Package.installed_files for multi-arch packages (LP: #1313699) Nothing changed in this area since ages. You maybe want --customizations=customization-file to format your entries. If you're seeing a regression it would be good to see what regressed whan an how. Cheers, I don't know if it's a regression or not, I'm just saying gbp dch should wrap it lines around where lintian expects them to be wrapped around. Maybe I just did not have such long commit messages previously and thus never experienced the issue before. -- 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#781767: Makes it unusable for my buckets too
Hi Rodrigo and Matt, I tried to apply the upstream commit to 1.5.0~rc1-2 and it doesn't apply cleanly. I see two/three possible solutions: 1) upgrade to stretch (just almost jocking) or apt-pinning s3cmd from there 2) change the upstream commit to apply on top of 1.5.0~rc1 version 3) backport the 1.5.2 to jessie-backports. It is up to you, Rodrigo you can do 1, Matt you can do 2, and I can do 3. I would prefer a stable-release-update, but backporting the new 1.5.2, might be better because some new features have been added In the meanwhile you have your backport ready there http://debomatic-amd64.debian.net/distribution#jessie-backports/s3cmd/1.5.2-2~bpo8+1/buildlog :) cheers, G. Il Venerdì 12 Giugno 2015 1:36, Rodrigo Campos rodr...@sdfg.com.ar ha scritto: On Thu, Jun 11, 2015 at 04:42:15PM -0500, Matt Domsch wrote: The copy in jesse's repository is 1.5.0~rc1-2 which is not v1.5.2 where the fix was committed. I see the same failure if I simply apt-get install s3cmd on a new jesse install. v1.5.2 is in experimental and unstable or can be downloaded from https://github.com/s3tools/s3cmd. Exactly. And my point is to fix this in jessie, if possible. As I said in my first mail, it renders the package unusable to me (and all people who is using dots in the buckets name). I upgraded to jessie and because of this bug some scripts are now broken. Thanks a lot, Rodrigo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781767: Makes it unusable for my buckets too
My preference is the backport of 1.5.2. That picks up signature v4 support which allows Frankfurt and China regions too. On Jun 12, 2015 4:02 AM, Gianfranco Costamagna costamagnagianfra...@yahoo.it wrote: Hi Rodrigo and Matt, I tried to apply the upstream commit to 1.5.0~rc1-2 and it doesn't apply cleanly. I see two/three possible solutions: 1) upgrade to stretch (just almost jocking) or apt-pinning s3cmd from there 2) change the upstream commit to apply on top of 1.5.0~rc1 version 3) backport the 1.5.2 to jessie-backports. It is up to you, Rodrigo you can do 1, Matt you can do 2, and I can do 3. I would prefer a stable-release-update, but backporting the new 1.5.2, might be better because some new features have been added In the meanwhile you have your backport ready there http://debomatic-amd64.debian.net/distribution#jessie-backports/s3cmd/1.5.2-2~bpo8+1/buildlog :) cheers, G. Il Venerdì 12 Giugno 2015 1:36, Rodrigo Campos rodr...@sdfg.com.ar ha scritto: On Thu, Jun 11, 2015 at 04:42:15PM -0500, Matt Domsch wrote: The copy in jesse's repository is 1.5.0~rc1-2 which is not v1.5.2 where the fix was committed. I see the same failure if I simply apt-get install s3cmd on a new jesse install. v1.5.2 is in experimental and unstable or can be downloaded from https://github.com/s3tools/s3cmd. Exactly. And my point is to fix this in jessie, if possible. As I said in my first mail, it renders the package unusable to me (and all people who is using dots in the buckets name). I upgraded to jessie and because of this bug some scripts are now broken. Thanks a lot, Rodrigo
Bug#788523: slime: ASDF fails to compile
Package: slime Version: 2:2.13-1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? sbcl slime fails to load on emacs. Upon running slime on emacs, it fails to load, returning the following -- ; loading #P/usr/share/common-lisp/source/slime/swank-loader.lisp ; file: /usr/share/common-lisp/source/cl-asdf/build/asdf.lisp ; in: DEFUN GET-OPTIMIZATION-SETTINGS ; (ASSOC UIOP/LISP-BUILD::X SB-C::*POLICY*) ; ; caught WARNING: ; Derived type of (SYMBOL-VALUE 'SB-C::*POLICY*) is ; (VALUES SB-C:POLICY OPTIONAL), ; conflicting with its asserted type ; LIST. ; See also: ; The SBCL Manual, Node Handling of Types ; file: /usr/share/common-lisp/source/cl-asdf/build/asdf.lisp ; in: DEFUN GET-OPTIMIZATION-SETTINGS ; (ASSOC UIOP/LISP-BUILD::X SB-C::*POLICY*) ; ; note: deleting unreachable code ; (LIST UIOP/LISP-BUILD::X UIOP/LISP-BUILD::Y) ; == ; UIOP/LISP-BUILD::X ; ; note: deleting unreachable code ; (ASSOC UIOP/LISP-BUILD::X SB-C::*POLICY*) ; ; caught WARNING: ; Derived type of (SYMBOL-VALUE 'SB-C::*POLICY*) is ; (VALUES SB-C:POLICY OPTIONAL), ; conflicting with its asserted type ; LIST. ; See also: ; The SBCL Manual, Node Handling of Types ASDF could not load sb-bsd-sockets because COMPILE-FILE-ERROR while compiling #CL-SOURCE-FILE asdf build asdf. ; ; compilation unit aborted ; caught 3 fatal ERROR conditions ; caught 2 WARNING conditions ; printed 2 notes ;; ;; Error while compiling /usr/share/common-lisp/source/slime/swank/sbcl.lisp: ;; COMPILE-FILE-ERROR while compiling #CL-SOURCE-FILE asdf build asdf ;; Aborting. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) 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 slime depends on: ii emacsen-common 2.0.8 Versions of packages slime recommends: ii cl-swank2:2.13-1 ii emacs24 [info-browser] 24.4+1-5 ii info [info-browser] 5.2.0.dfsg.1-6 slime 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#787658: [Aptitude-devel] Bug#787658: aptitude ignores available updates for a while after downgrades
Hi, ydir...@free.fr wrote: Same here, it looks like only updating the package list again will bring those packages back into the Upgradable set. Explicitly marking the new version for upgrades also suffices, including future updates. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788527: pyro4: new upstream available
Source: pyro4 Version: 4.23-2 Severity: normal Dear Maintainer, The version in sid is quite old now, and the online docs describe very useful features... that are simply not available in that old version. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#787658: aptitude ignores available updates for a while after downgrades
Same here, it looks like only updating the package list again will bring those packages back into the Upgradable set. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788386: libprocps3-dev:amd64, libprocps3-dev:i386 not coinstallable
On Wed, Jun 10, 2015 at 11:50:42PM +0300, Sami Liedes wrote: libprocps3-dev cannot currently be installed for multiple architectures, causing inconvenience if one wishes to compile procps code for both 32-bit and 64-bit: Ah, no multiarch tags in the dev file. - Craig -- Craig Small (@smallsees) http://enc.com.au/ csmall at : enc.com.au Debian GNU/Linux http://www.debian.org/ csmall at : debian.org GPG fingerprint:5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788529: linux-image-3.16.0-4-686-pae: crash with modprobe i915 [drm:i9xx_set_fifo_underrun_reporting] *ERROR* pipe B underrun
Package: src:linux Version: 3.16.7-ckt11-1 Severity: normal When the i915 module loads, the display stops working and the kernel message log shows a bug has occurred. The only way to boot the system with a display is to blacklist the i915 module. Relevant lines from dmesg: [ 55.603051] [drm] Memory usable by graphics device = 256M [ 55.603059] [drm] Replacing VGA console driver [ 55.604726] Console: switching to colour dummy device 80x25 [ 55.608615] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 55.608624] [drm] Driver supports precise vblank timestamp query. [ 55.608730] [drm] applying pipe a force quirk [ 55.608758] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 55.637034] [drm:i9xx_set_fifo_underrun_reporting] *ERROR* pipe B underrun [ 55.638376] BUG: unable to handle kernel NULL pointer dereference at 0008 [ 55.638396] IP: [f82c3671] drm_mm_insert_node_in_range_generic+0x41/0x2d0 [drm] [ 55.638440] *pdpt = 33ae5001 *pde = [ 55.638457] Oops: [#1] SMP [ 55.638469] Modules linked in: i915(+) pcspkr psmouse drm_kms_helper evdev drm pcmcia serio_raw lpc_ich i2c_algo_bit i2c_core mfd_core shpchp rng_core toshiba_acpi snd_intel8x0m snd_intel8x0 yenta_socket sparse_keymap snd_ac97_codec rfkill snd_pcm wmi pcmcia_rsrc snd_timer pcmcia_core snd soundcore ac97_bus toshiba_bluetooth video ac battery button tpm_infineon tpm acpi_cpufreq processor fuse parport_pc ppdev lp parport autofs4 ext4 crc16 mbcache jbd2 xts gf128mul algif_skcipher af_alg dm_crypt usb_storage dm_mod sg sd_mod crc_t10dif crct10dif_generic crct10dif_common ata_generic ata_piix sdhci_pci sdhci mmc_core libata scsi_mod ehci_pci thermal thermal_sys uhci_hcd ehci_hcd sky2 usbcore usb_common [ 55.638719] CPU: 0 PID: 242 Comm: systemd-udevd Not tainted 3.16.0-4-686-pae #1 Debian 3.16.7-ckt11-1 [ 55.638740] Hardware name: TOSHIBA PORTEGE R200/Portable PC, BIOS Version 1.60 10/25/2005 [ 55.638761] task: f31ca010 ti: f44a4000 task.ti: f44a4000 [ 55.638777] EIP: 0060:[f82c3671] EFLAGS: 00010286 CPU: 0 [ 55.638810] EIP is at drm_mm_insert_node_in_range_generic+0x41/0x2d0 [drm] [ 55.638826] EAX: EBX: f3f7c084 ECX: 0012c000 EDX: [ 55.638841] ESI: fff8 EDI: EBP: f44a5930 ESP: f44a58f8 [ 55.638857] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 55.638871] CR0: 80050033 CR2: 0008 CR3: 37188000 CR4: 07f0 [ 55.638886] Stack: [ 55.638895] 0246 f3f15440 0060 80d0 0293 0012c000 f3f7c084 [ 55.638928] f3f0ff00 f44a5930 f848fc94 1000 0001 f3f0ff00 f44a5998 f84951c1 [ 55.638959] 0001 1000 f84ac17f 0012c000 [ 55.638991] Call Trace: [ 55.639108] [f848fc94] ? i915_gem_obj_lookup_or_create_vma+0x34/0x120 [i915] [ 55.639220] [f84951c1] ? i915_gem_object_pin+0x4c1/0x6f0 [i915] [ 55.639338] [f84ac17f] ? gen4_read32+0x3f/0xc0 [i915] [ 55.639445] [f84967bf] ? i915_gem_object_pin_to_display_plane+0x8f/0x190 [i915] [ 55.639570] [f84bbf94] ? intel_pin_and_fence_fb_obj+0x64/0x100 [i915] [ 55.639693] [f84c1721] ? __intel_set_mode+0x571/0x1400 [i915] [ 55.639733] [f82c53b8] ? drm_mode_object_get+0x58/0x70 [drm] [ 55.639768] [f82c5450] ? drm_framebuffer_init+0x80/0x90 [drm] [ 55.639893] [f84c4c13] ? intel_set_mode+0x23/0x40 [i915] [ 55.640014] [f84c4e0a] ? intel_get_load_detect_pipe+0x1da/0x450 [i915] [ 55.640140] [f84c68e1] ? intel_modeset_setup_hw_state+0x971/0xbb0 [i915] [ 55.640166] [c147a8c4] ? __ww_mutex_lock+0x14/0x77 [ 55.640277] [f84ac200] ? gen4_read32+0xc0/0xc0 [i915] [ 55.640399] [f84c723c] ? intel_modeset_init+0x71c/0x1210 [i915] [ 55.640508] [f84a0dcb] ? i915_enable_pipestat+0xab/0x120 [i915] [ 55.640617] [f84a13b4] ? i915_irq_postinstall+0x104/0x110 [i915] [ 55.640653] [f82bcb89] ? drm_irq_install+0xa9/0x170 [drm] [ 55.640791] [f84f0af5] ? i915_driver_load+0xb05/0xf00 [i915] [ 55.640926] [f84ede50] ? i915_switcheroo_set_state+0x90/0x90 [i915] [ 55.640949] [c1252b0a] ? kobject_uevent_env+0x15a/0x690 [ 55.640967] [c1252740] ? cleanup_uevent_env+0x10/0x10 [ 55.640989] [c133c664] ? get_device+0x14/0x30 [ 55.641008] [c1470fbb] ? klist_node_init+0x2b/0x40 [ 55.641012] [c1471026] ? klist_add_tail+0x16/0x30 [ 55.641012] [c133da36] ? device_add+0x1d6/0x5a0 [ 55.641012] [f82c28da] ? drm_sysfs_device_add+0xba/0x100 [drm] [ 55.641012] [f82bf5ae] ? drm_dev_register+0x8e/0xe0 [drm] [ 55.641012] [f82c1b79] ? drm_get_pci_dev+0x79/0x1c0 [drm] [ 55.641012] [c128605f] ? pci_device_probe+0x6f/0xc0 [ 55.641012] [c11cb765] ? sysfs_create_link+0x25/0x40 [ 55.641012] [c13404c3] ? driver_probe_device+0x93/0x3a0 [ 55.641012] [c11cb497] ? sysfs_create_dir_ns+0x37/0x80 [ 55.641012] [c1285fa1] ? pci_match_device+0xc1/0xe0 [ 55.641012] [c1340881] ? __driver_attach+0x71/0x80 [ 55.641012] [c1340810] ?
Bug#642552: Fix committed
tags 642552 pending thanks Hi, I think this commit should be enough: http://anonscm.debian.org/cgit/collab-maint/libmtp.git/commit/?id=d859fdc006abee20273af1353863a6032de5dd90 Cheers. -- Alessio Treglia | www.alessiotreglia.com Debian Developer | ales...@debian.org Ubuntu Core Developer| quadris...@ubuntu.com 0416 0004 A827 6E40 BB98 90FB E8A4 8AE5 311D 765A -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788498: udev: breaks the keyboard configuration
Hey Vincent, Vincent Lefevre [2015-06-12 14:14 +0200]: BTW, what about all the b0003 in /lib/udev/hwdb.d/60-keyboard.hwdb? These were confirmed to be USB devices. Anyway, you confirmed that too, so the b0003 seems correct. It's just not always the case that keyboards are wired through USB, so I wanted to check that. If this works, using a wildcard for b should be suggested by the documentation. Unlikely then. xvii:~ cat /sys/class/input/event1/device/name Apple, Inc Apple Keyboard xvii:~ cat /sys/class/input/event1/device/modalias input:b0003v05ACp0221e0111-e0,1,4,11,14,k71,72,73,74,75,77,78,79,7A,7B,7C,7D,7E,7F,80,81,82,83,84,85,86,87,88,89,8A,8C,8E,96,98,9E,9F,A1,A3,A4,A5,A6,AD,B0,B1,B2,B3,B4,B8,B9,BA,BB,BC,BD,BE,BF,C0,C1,C2,CC,E0,E1,E3,E4,E5,E6,F0,1D0,ram4,l0,1,2,3,4,sfw Hm, so this seems to match evdev:input:b0003v05ACp0221* perfectly well. So, let's assume that the evdev: is correct, and check the others: Where did you put your own config? You already ran udevadm hwdb --update, so that's not it. If you run udevadm hwdb -t evdev:input:b0003v05ACp0221e0111-e0,1,4 do you get your KEYBOARD_KEY_* entries? - If not: Something is wrong with your .hwdb file location or the --update - If so: Please check udevadm info /dev/input/eventX and check if this has the KEYBOARD_KEY* properties. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788568: debbindiff: leaves temporary files under /tmp
Package: debbindiff Version: 20 Severity: normal In jenkins.d.n i can see this: mattia@jenkins ~ % find /tmp -maxdepth 1 -name tmp*debbindiff | xargs ls -ld drwx-- 2 jenkins jenkins 4096 Jun 8 12:02 /tmp/tmp114lHtdebbindiff drwx-- 2 jenkins jenkins 4096 Jun 4 17:58 /tmp/tmp12TNVEdebbindiff drwx-- 2 jenkins jenkins 4096 Jun 2 19:58 /tmp/tmp1CdwrPdebbindiff drwx-- 2 jenkins jenkins 4096 Jun 12 15:37 /tmp/tmp1UjIWidebbindiff drwx-- 2 jenkins jenkins 4096 Jun 11 19:06 /tmp/tmp2Y1XlCdebbindiff drwx-- 3 jenkins jenkins 4096 Jun 3 00:02 /tmp/tmp3k5vUkdebbindiff drwx-- 2 jenkins jenkins 4096 Jun 10 14:40 /tmp/tmp3kCyiEdebbindiff drwx-- 2 jenkins jenkins 4096 Jun 3 17:04 /tmp/tmp3r5xTCdebbindiff drwx-- 2 jenkins jenkins 4096 Jun 7 13:10 /tmp/tmp3x8cYudebbindiff drwx-- 3 jenkins jenkins 4096 Jun 2 00:00 /tmp/tmp4rTe0kdebbindiff drwx-- 2 jenkins jenkins 4096 Jun 3 04:29 /tmp/tmp4SMf7Ndebbindiff drwx-- 2 jenkins jenkins 4096 Jun 5 11:45 /tmp/tmp4thL1edebbindiff drwx-- 3 jenkins jenkins 4096 Jun 12 15:41 /tmp/tmp5f8AWtdebbindiff drwx-- 2 jenkins jenkins 4096 Jun 5 23:01 /tmp/tmp5HF96Fdebbindiff drwx-- 2 jenkins jenkins 4096 Jun 12 08:24 /tmp/tmp5QgUUZdebbindiff drwx-- 2 jenkins jenkins 4096 Jun 3 11:37 /tmp/tmp6DgBRfdebbindiff drwx-- 2 jenkins jenkins 4096 Jun 11 13:37 /tmp/tmp6isMQMdebbindiff drwx-- 2 jenkins jenkins 4096 Jun 12 15:39 /tmp/tmp79pHrvdebbindiff drwx-- 2 jenkins jenkins 4096 Jun 5 11:45 /tmp/tmp7QhYqkdebbindiff drwx-- 2 jenkins jenkins 4096 Jun 3 00:02 /tmp/tmp8j4qNmdebbindiff drwx-- 2 jenkins jenkins 4096 Jun 9 16:49 /tmp/tmp8nRXGidebbindiff drwx-- 3 jenkins jenkins 4096 Jun 2 00:00 /tmp/tmp96Bflodebbindiff drwx-- 2 jenkins jenkins 4096 Jun 3 00:02 /tmp/tmp98Axipdebbindiff drwx-- 3 jenkins jenkins 4096 Jun 11 13:37 /tmp/tmp9ggOzmdebbindiff drwx-- 2 jenkins jenkins 4096 Jun 9 16:49 /tmp/tmp9NiEe7debbindiff drwx-- 2 jenkins jenkins 4096 Jun 3 17:04 /tmp/tmpAdkX73debbindiff drwx-- 2 jenkins jenkins 4096 Jun 7 13:10 /tmp/tmpBay8P7debbindiff drwx-- 2 jenkins jenkins 4096 Jun 5 23:01 /tmp/tmpBOMLKWdebbindiff drwx-- 3 jenkins jenkins 4096 Jun 3 17:04 /tmp/tmpc4ICUOdebbindiff drwx-- 2 jenkins jenkins 4096 Jun 2 19:58 /tmp/tmpcoGBbydebbindiff drwx-- 2 jenkins jenkins 4096 Jun 11 13:37 /tmp/tmpcQiGyadebbindiff drwx-- 2 jenkins jenkins 4096 Jun 3 17:04 /tmp/tmpcXl7NTdebbindiff drwx-- 2 jenkins jenkins 4096 Jun 10 02:38 /tmp/tmpdaf5L_debbindiff drwx-- 2 jenkins jenkins 4096 Jun 2 13:28 /tmp/tmpditBkHdebbindiff drwx-- 2 jenkins jenkins 4096 Jun 3 04:29 /tmp/tmpDKUd3Ddebbindiff drwx-- 2 jenkins jenkins 4096 Jun 5 11:45 /tmp/tmpdL4kFDdebbindiff drwx-- 2 jenkins jenkins 4096 Jun 8 12:02 /tmp/tmpdqPPFVdebbindiff drwx-- 2 jenkins jenkins 4096 Jun 3 00:02 /tmp/tmpDVpswydebbindiff drwx-- 3 jenkins jenkins 4096 Jun 3 00:02 /tmp/tmpe5HHxpdebbindiff drwx-- 2 jenkins jenkins 4096 Jun 11 10:32 /tmp/tmpEUbJg2debbindiff drwx-- 3 jenkins jenkins 4096 Jun 10 02:38 /tmp/tmpeufUvudebbindiff drwx-- 2 jenkins jenkins 4096 Jun 11 19:07 /tmp/tmpeUg8h9debbindiff drwx-- 2 jenkins jenkins 4096 Jun 3 11:37 /tmp/tmpeVs4Uddebbindiff drwx-- 2 jenkins jenkins 4096 Jun 12 08:24 /tmp/tmpewDCT6debbindiff drwx-- 3 jenkins jenkins 4096 Jun 6 17:03 /tmp/tmpf2hshYdebbindiff drwx-- 2 jenkins jenkins 4096 Jun 8 12:02 /tmp/tmpF6Nd82debbindiff drwx-- 3 jenkins jenkins 4096 Jun 4 17:58 /tmp/tmpF75xj0debbindiff drwx-- 2 jenkins jenkins 4096 Jun 2 00:00 /tmp/tmpF_cmTAdebbindiff drwx-- 2 jenkins jenkins 4096 Jun 11 10:32 /tmp/tmpfewwwVdebbindiff drwx-- 3 jenkins jenkins 4096 Jun 11 13:37 /tmp/tmpG1g8Q3debbindiff drwx-- 2 jenkins jenkins 4096 Jun 7 13:10 /tmp/tmpGIXMkfdebbindiff drwx-- 2 jenkins jenkins 4096 Jun 12 15:37 /tmp/tmpGqgkKKdebbindiff drwx-- 3 jenkins jenkins 4096 Jun 3 11:37 /tmp/tmphg_5p1debbindiff drwx-- 2 jenkins jenkins 4096 Jun 6 17:03 /tmp/tmphob_Xodebbindiff drwx-- 2 jenkins jenkins 4096 Jun 8 12:02 /tmp/tmphXu6Fddebbindiff drwx-- 2 jenkins jenkins 4096 Jun 8 12:02 /tmp/tmpibi0AHdebbindiff drwx-- 3 jenkins jenkins 4096 Jun 12 15:41 /tmp/tmpIDCVkCdebbindiff drwx-- 2 jenkins jenkins 4096 Jun 10 14:40 /tmp/tmpir455gdebbindiff drwx-- 2 jenkins jenkins 4096 Jun 2 00:00 /tmp/tmpIwn7sKdebbindiff drwx-- 2 jenkins jenkins 4096 Jun 10 14:40 /tmp/tmpjgdlCRdebbindiff drwx-- 2 jenkins jenkins 4096 Jun 2 00:00 /tmp/tmpjvhLWydebbindiff drwx-- 3 jenkins jenkins 4096 Jun 5 11:45 /tmp/tmpkDAeAGdebbindiff drwx-- 2 jenkins jenkins 4096 Jun 2 13:28 /tmp/tmpkI_uIydebbindiff drwx-- 2 jenkins jenkins 4096 Jun 11 10:32 /tmp/tmpkXfVT8debbindiff drwx-- 2 jenkins jenkins 4096 Jun 5 23:01 /tmp/tmpKxlky4debbindiff drwx-- 3 jenkins jenkins 4096 Jun 9 16:49 /tmp/tmpl056kkdebbindiff drwx-- 3 jenkins jenkins 4096 Jun 12 08:24 /tmp/tmpLcFWpAdebbindiff drwx-- 3
Bug#788348:
tags 788348 - help + moreinfo thanks If you still believe this is a bug, provide additional evidence supporting this claim. Otherwise, as this appears to be a misconfiguration, I intend to close the bug report next week. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788570: libsdl-perl: autopkgtest failure: Couldn't open test/data/sample.wav
Package: libsdl-perl Version: 2.546-1 User: debian-p...@lists.debian.org Usertags: autopkgtest This package failed its autopkgtest checks on ci.debian.net. From http://ci.debian.net/packages/libs/libsdl-perl/unstable/amd64/: t/core_audio.t .. 1..45 ok 1 - AUDIO_S16 should be imported [...] ok 32 - 'Created a new AudioSpec' isa 'SDL::AudioSpec' Error in SDL_LoadWAV: Couldn't open test/data/sample.wav at t/core_audio.t line 88. # Looks like you planned 45 tests but ran 32. # Looks like your test exited with 2 just after 32. Dubious, test returned 2 (wstat 512, 0x200) Failed 13/45 subtests -- 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#788567: [Pkg-openssl-devel] Bug#788567: libssl1.0.0: wpa_supplicant fails to authenticate
Please try 1.0.2c-1. Kurt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784942: autopkgtest: fails to read Files: from perfectly valid .changes file
-=| Damyan Ivanov, 12.06.2015 19:45:33 + |=- -=| Antonio Terceiro, 29.05.2015 08:01:50 -0300 |=- On Tue, May 26, 2015 at 06:31:15PM +0200, Martin Pitt wrote: Control: tag -1 unreproducible Hey Antonio, sorry for the late response. Antonio Terceiro [2015-05-10 19:45 -0300]: I am missing anything? $ adt-run --user debci --output-dir /tmp/adt-run ../build-area/ruby-defaults_2.1.5.0_amd64.changes --- schroot debci-unstable-amd64 adt-run: error: ../build-area/ruby-defaults_2.1.5.0_amd64.changes is invalid and does not contain Files: [20]$ cat ../build-area/ruby-defaults_2.1.5.0_amd64.changes I tried that .changes files, and it works correctly here. Maybe just pasting it into the email destroyed some subtle whitespace? Can you attach the file instead? I also got ruby-defaults 2.1.5.0 from the archive, sbuilt it, and ran adt-run on the binary unsigned .changes, which also worked. If you can still reproduce this, I can also send you some patch for enhancing debugging in runner/adt-run files_from_dsc() -- it seems the parse_rfc822() runs into a corner case? I can still reproduce it, yes: $ adt-run --user debci --output-dir /tmp/adt-run ruby-defaults_2.1.5.0_amd64.changes --- schroot debci-unstable-amd64 adt-run: error: ruby-defaults_2.1.5.0_amd64.changes is invalid and does not contain Files: [20]$ debsign ruby-defaults_2.1.5.0_amd64.changes [...] Successfully signed dsc and changes files $ adt-run --user debci --output-dir /tmp/adt-run ruby-defaults_2.1.5.0_amd64.changes --- schroot debci-unstable-amd64 adt-run [07:57:45]: version 3.14.2 adt-run [07:57:45]: command line: /usr/bin/adt-run --user debci --output-dir /tmp/adt-run ruby-defaults_2.1.5.0_amd64.changes --- schroot debci-unstable-amd64 adt-run [07:57:46]: testbed dpkg architecture: amd64 adt-run [07:57:46]: source ruby-defaults_2.1.5.0.dsc OK [...] adt-run [07:57:59]: test smoke-test: ---] adt-run [07:57:59]: test smoke-test: - - - - - - - - - - results - - - - - - - - - - smoke-test PASS The original ruby-defaults_2.1.5.0_amd64.changes, without the signature, is attached. I have another failing example (attached). Debsign-ing it works around the problem. Thanks to Niko Tyni, we may have a clue. Both .changes files seem to have what seems to be interpreted as a comment. Lines 186-189 of /usr/share/autopkgtest/python/testdesc.py seem to attempt to handle this, but after stripping the comment (not starting from the first character), the resulting test seems to confuse the parser, because the line now contains only whitespace. Perhaps the test on line 186 should also be triggered by lines starting with whitespace,followed by #? Maybe this gives some pointer. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788572: mplayer2: segmentation fault right after start
Package: mplayer2 Version: 2.0-728-g2c378c7-4+b1 Severity: important Dear Maintainer, after a dist-upgrade yesterday (11.06.2015) mplayer throws a seg fault. gdb output: (gdb) run Starting program: /usr/bin/mplayer [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/i386-linux-gnu/i686/cmov/libthread_db.so.1. Program received signal SIGSEGV, Segmentation fault. 0xb27d5788 in nettle_yarrow256_update () from /usr/lib/i386-linux-gnu/libnettle.so.4 (gdb) bt #0 0xb27d5788 in nettle_yarrow256_update () from /usr/lib/i386-linux-gnu/libnettle.so.4 #1 0xb4af3641 in ?? () from /usr/lib/i386-linux-gnu/libgnutls-deb0.so.28 #2 0xb4af3804 in ?? () from /usr/lib/i386-linux-gnu/libgnutls-deb0.so.28 #3 0xb4a5c3e6 in ?? () from /usr/lib/i386-linux-gnu/libgnutls-deb0.so.28 #4 0xb4a4fd6d in gnutls_global_init () from /usr/lib/i386-linux-gnu/libgnutls-deb0.so.28 #5 0xb4a30534 in ?? () from /usr/lib/i386-linux-gnu/libgnutls-deb0.so.28 #6 0xb7fed86e in call_init (l=optimized out, argc=argc@entry=1, argv=argv@entry=0xb614, env=env@entry=0xb61c) at dl-init.c:78 #7 0xb7fed964 in call_init (env=0xb61c, argv=0xb614, argc=1, l=optimized out) at dl-init.c:36 #8 _dl_init (main_map=0xb7fff930, argc=1, argv=0xb614, env=0xb61c) at dl-init.c:126 #9 0xb7fdfd3f in _dl_start_user () from /lib/ld-linux.so.2 Maybe it is something like this Gimp bug here? https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1328060.html On another machine with debian STABLE (and libgnutls 3.3.15-2) mplayer still works. -- System Information: Debian Release: stretch/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core) 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 mplayer2 depends on: ii liba52-0.7.4 0.7.4-18 ii libasound21.0.28-1 ii libass5 0.12.2-1 ii libavcodec56 6:11.4-2 ii libavformat56 6:11.4-2 ii libavresample26:11.4-2 ii libavutil54 6:11.4-2 ii libbluray11:0.8.1-1 ii libbs2b0 3.1.0+dfsg-2.1 ii libc6 2.19-18 ii libcaca0 0.99.beta19-2 ii libcdio-cdda1 0.83-4.2 ii libcdio-paranoia1 0.83-4.2 ii libcdio13 0.83-4.2 ii libdca0 0.0.5-dmo1 ii libdirectfb-1.2-9 1.2.10.0-5.1 ii libdv41.0.0-6 ii libdvdread4 5.0.0-1 ii libenca0 1.16-1 ii libfaad2 2.8.0~cvs20150510-1 ii libgif4 4.1.6-11 ii libgl1-mesa-glx [libgl1] 10.5.5-1 ii libjack-jackd2-0 [libjack-0.116] 1.9.10+20140719git3eb0ae6a~dfsg-2 ii libjpeg62-turbo 1:1.4.0-7 ii liblcms2-22.6-3+b3 ii liblircclient00.9.0~pre1-1.2 ii libmad0 0.15.1b-8 ii libmpg123-0 1.20.1-2 ii libogg0 1.3.2-1 ii libpng12-01.2.50-2+b2 ii libpostproc52 8:1.0.10-dmo1 ii libpulse0 6.0-2 ii libquvi7 0.4.1-3 ii libsdl1.2debian 1.2.15-11 ii libsmbclient 2:4.1.17+dfsg-4 ii libspeex1 1.2~rc1.2-1 ii libswscale3 6:11.4-2 ii libtheora01.1.1+dfsg.1-6 ii libtinfo5 5.9+20150516-2 ii libvdpau1 1.1-1 ii libvorbis0a 1.3.4-2 ii libx11-6 2:1.6.3-1 ii libxext6 2:1.3.3-1 ii libxinerama1 2:1.1.3-1+b1 ii libxss1 1:1.2.2-1 ii libxv12:1.0.10-1+b1 ii libxvidcore4 3:1.3.2-dmo1 ii libxxf86vm1 1:1.1.4-1 ii zlib1g1:1.2.8.dfsg-2+b1 mplayer2 recommends no packages. mplayer2 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#617665: (no subject)
The current version in the git repository contains a fix for fai-mirror, so that the reprepro config in mirrordir are not removed by fai-mirror. Now, only a conf/updates file has to be generated (from sources.list), to get the update feature. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#786650: virt-aa-helper: incomplete apparmor profile
Hi,
On Sun, 24 May 2015 16:51:27 + Luke Faraone lfara...@debian.org wrote:
On Sun, 2015-05-24 at 09:43 +0200, Guido Günther wrote:
Hi,
thanks for the patch.
On Sun, May 24, 2015 at 12:14:48AM +, Luke Faraone wrote:
[..snip..]
--- usr.lib.libvirt.virt-aa-helper2015-05-23 23:43:44.751750819
+
+++ /etc/apparmor.d/usr.lib.libvirt.virt-aa-helper2015-05-24
00:03:13.039766331 +
@@ -1,7 +1,7 @@
# Last Modified: Mon Apr 5 15:10:27 2010
#include tunables/global
-/usr/lib/libvirt/virt-aa-helper {
+/usr/lib/libvirt/virt-aa-helper flags=(complain) {
Is that one needed as well or is it rather a debugging leftover?
Oops, you're right, this was just for debugging. Sorry about that.
I think the problems you are seeing are entirely because of bug #786652.
These denials should be harmless therefore I propose the attached patch.
This is also aligned with what Ubuntu does in their virt-aa-helper profile.
Cheers,
Felix
--- libvirt-1.2.16.orig/examples/apparmor/usr.lib.libvirt.virt-aa-helper
+++ libvirt-1.2.16/examples/apparmor/usr.lib.libvirt.virt-aa-helper
@@ -16,9 +16,16 @@ profile virt-aa-helper /usr/{lib,lib64}/
owner @{PROC}/[0-9]*/status r,
@{PROC}/filesystems r,
+ /etc/libnl-3/classid r,
+
# for hostdev
/sys/devices/ r,
/sys/devices/** r,
+ deny /dev/sd* r,
+ deny /dev/vd* r,
+ deny /dev/dm-* r,
+ deny /dev/mapper/ r,
+ deny /dev/mapper/* r,
/usr/{lib,lib64}/libvirt/virt-aa-helper mr,
/sbin/apparmor_parser Ux,
Bug#788573: initscript doesn't preserve return code
Package: nginx Version: 1.9.1-1 Many actions offered by the initscript do not preserve or give the proper return code. One notable example is the configtest that always returns 0 even when problems are detected: echo invalid /etc/nging/nginx.conf service nginx configtest echo $? Should return 1 but returns 0 instead. The attached patch makes the initscript preserve the return code for all supported actions. Regards, Simon --- nginx-common.nginx.init.orig 2015-06-12 16:01:06.0 -0400 +++ nginx-common.nginx.init 2015-06-12 16:02:48.438224547 -0400 @@ -127,19 +127,19 @@ case $1 in start) - [ $VERBOSE != no ] log_daemon_msg Starting $DESC $NAME + log_daemon_msg Starting $DESC $NAME do_start case $? in - 0|1) [ $VERBOSE != no ] log_end_msg 0 ;; - 2) [ $VERBOSE != no ] log_end_msg 1 ;; + 0|1) log_end_msg 0 ;; + 2) log_end_msg 1 ;; esac ;; stop) - [ $VERBOSE != no ] log_daemon_msg Stopping $DESC $NAME + log_daemon_msg Stopping $DESC $NAME do_stop case $? in - 0|1) [ $VERBOSE != no ] log_end_msg 0 ;; - 2) [ $VERBOSE != no ] log_end_msg 1 ;; + 0|1) log_end_msg 0 ;; + 2) log_end_msg 1 ;; esac ;; restart) @@ -148,7 +148,7 @@ # Check configuration before stopping nginx if ! test_nginx_config; then log_end_msg 1 # Configuration error - exit 0 + exit $? fi do_stop @@ -178,7 +178,7 @@ # to the administrator. if ! test_nginx_config; then log_end_msg 1 # Configuration error - exit 0 + exit $? fi do_reload @@ -190,12 +190,12 @@ log_end_msg $? ;; status) - status_of_proc -p $PID $DAEMON $NAME exit 0 || exit $? + status_of_proc -p $PID $DAEMON $NAME ;; upgrade) log_daemon_msg Upgrading binary $NAME do_upgrade - log_end_msg 0 + log_end_msg $? ;; rotate) log_daemon_msg Re-opening $DESC log files $NAME @@ -207,5 +207,3 @@ exit 3 ;; esac - -:
Bug#737058: CEGUI-0.8.4-1
Hi Tobias, :) Yes, bug triaging is important and the Debian project appreciates also any help on this here for sure appreciated I'll happily review every bugs once the package is in, if you want me to. Two or three of them will be closed by Muammar's work, btw. As soon as the package is through NEW the first part is closed, but for the second part, Muammar needs to give directions how he wants to develop the project. Separating the deps is clearly a need along with adding python bindings for the future CEED package. Here, we can see how Fedora did it and it seems really done well. https://apps.fedoraproject.org/packages/cegui Then, is it possible for instance to retitle this bug with what's left to do in it, so it more clear for everyone? Or even close this one and start clean on a new one? Something like: -- CEGUI needs to separate its dependencies in different packages: -- (D) = Default - libcegui-dev - libcegui-dev-doc (Suggested by libcegui-dev) - libcegui (provides) - libcegui-imagecodec (provides) - (D) libcegui-freeimage-imagecodec - libcegui-DevIL-imagecodec - libcegui-xmlparser (provides) - (D) libcegui-tinyxml-xmlparser - libcegui-libxml-xmlparser - libcegui-xerces-xmlparse - libcegui-renderer (provides) - (D) libcegui-ogre-renderer - libcegui-irrlicht-renderer - libcegui-null-renderer - libcegui-python-bindings (optional, suggested by libcegui) Btw, I've got a noob question why is the cegui package named with the 'mk2' suffix? Feel free to correct me if you see something wrong here. :) Ah, and also please note that the copyright file of libcegui-mk2-0.8.4-dbg_0.8.4-1_amd64.deb is still the one from version 0.5. I hope Muammar will have some time for us so we can work on that. In any case, I'd like to see the following solved, even if I have to do the job myself: - Separate deps - Add python bindings - Add the CEED package which is really a powerful tool now, and very useful for gui makers. Best regards, Yohann Le 12/06/2015 10:10, Tobias Frost a écrit : Hi Yohann, Am Freitag, den 12.06.2015, 00:07 +0200 schrieb Yohann Ferreira: Hey, I just wanted to hint that Muammar uploaded a new package some days ago: https://ftp-master.debian.org/new/cegui-mk2_0.8.4-1.html Could you have a look at it, so we can close this bug and maybe a few others? Thanks and best regards, Yohann Yes, bug triaging is important and the Debian project appreciateas also any help on this here for sure appreciated Well, unfortuantly this bugs mixes two different things: - new upstream version - make dependencies optional As soon as the package is through NEW the first part is closed, but for the second part, Muammar needs to give directions how he wants to develop the project. So for this bug, after 0.8.4 is in the archives maybe this bug should be retitled... -- Tobi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788582: libkf5filemetadata-data: fails to upgrade from 'sid' - trying to overwrite /usr/share/locale/*/LC_MESSAGES/kfilemetadata.mo
Package: libkf5filemetadata-data Version: 5.6.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces The new package takes over files from (at least) these packages: kde-l10n-bg kde-l10n-bs kde-l10n-ca kde-l10n-cavalencia kde-l10n-cs kde-l10n-da kde-l10n-de kde-l10n-el kde-l10n-engb kde-l10n-es kde-l10n-fi kde-l10n-fr kde-l10n-gl kde-l10n-hu kde-l10n-ia kde-l10n-it kde-l10n-ja kde-l10n-ko kde-l10n-lt kde-l10n-nb kde-l10n-nds kde-l10n-nl kde-l10n-pa kde-l10n-pl kde-l10n-pt kde-l10n-ptbr kde-l10n-ru kde-l10n-sk kde-l10n-sl kde-l10n-sr kde-l10n-sv kde-l10n-uk kde-l10n-zhcn kde-l10n-zhtw From the attached log - just one example - (scroll to the bottom...): Selecting previously unselected package libkf5filemetadata-data. Preparing to unpack .../libkf5filemetadata-data_5.6.2-1_all.deb ... Unpacking libkf5filemetadata-data (5.6.2-1) ... dpkg: error processing archive /var/cache/apt/archives/libkf5filemetadata-data_5.6.2-1_all.deb (--unpack): trying to overwrite '/usr/share/locale/bg/LC_MESSAGES/kfilemetadata.mo', which is also in package kde-l10n-bg 4:4.14.0-1 cheers, Andreas kde-l10n-bg=4%4.14.0-1_libkf5filemetadata-data=5.6.2-1.log.gz Description: application/gzip
Bug#695127: O: blktool -- tune low-level block device parameters
Please see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788583 for corresponding RFS bug. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788584: Manpage still documents --disable-factory, which no longer works
Package: gnome-terminal Version: 3.16.2-1 Severity: normal File: /usr/share/man/man1/gnome-terminal.1.gz ~$ man gnome-terminal | grep disable-factory [--geometry=GEOMETRY] [--disable-factory] [-t, --title=TITLE] [--working-directory=DIRNAME] [--usage] [-?, --help] --disable-factory ~$ gnome-terminal --disable-factory Failed to parse arguments: Option --disable-factory is no longer supported in this version of gnome-terminal. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-terminal depends on: ii dconf-gsettings-backend [gsettings-backend] 0.24.0-2 ii gconf-service3.2.6-3 ii gnome-terminal-data 3.16.2-1 ii gsettings-desktop-schemas3.16.1-1 ii libatk1.0-0 2.16.0-2 ii libc62.19-18 ii libcairo-gobject21.14.2-2 ii libcairo21.14.2-2 ii libdconf10.24.0-2 ii libgconf-2-4 3.2.6-3 ii libgdk-pixbuf2.0-0 2.31.4-2 ii libglib2.0-0 2.44.1-1 ii libgtk-3-0 3.14.13-1 ii libnautilus-extension1a 3.14.2-1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libuuid1 2.26.2-6 ii libvte-2.91-00.40.2-1 ii libx11-6 2:1.6.3-1 Versions of packages gnome-terminal recommends: ii dbus-x11 1.8.18-1 ii gvfs 1.24.1-2+b1 ii yelp 3.16.1-1 gnome-terminal 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#788566: Push-Request from syncproxy.eu for debian.mirror.lrz.de
Package: mirrors Severity: normal Hi, we are running debian.mirror.lrz.de which is listed in the official mirror list. We are currently pushed by ftp.uni-kl.de and would like to switch over to syncproxy.eu.debian.org because ftp.uni-kl.de does not carry all architectures. We have added the ssh key to our authorized_keys already. We would be grateful if you could push mir...@debian.mirror.lrz.de in the future. Note that while the key has already been added, the sync will not be switched over until we have verified operations. Thanks, Bernhard -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#334505: Liste neuer Stellenausschreibungen für Sie.
Sehr geehrte/r 334505, die Arbeitsvermittlung stellt Ihnen folgende attraktive Arbeit in einem internationalen Team im Home Office Bereich vor, ohne Fahrzeit, ohne Anfahrt, ohne Verkehrsstress. Wir bieten qualitative und attraktive Jobs nicht nur in der Stadt, sondern auch auf dem Land in ganz EU und bieten gleichzeitig hochwertige Qualität für unsere Kunden. Ab sofort suchen wir: Angestellte (m/w) für den Support im Home-office im Bereich Office und Kommunikation Wir bieten Ihnen eine Stelle als Festangestellter oder als Selbständiger mit einem Stundenlohn von 20 € in der Stunde in selbständigen Arbeitsweise und einer effektiven Beschäftigungsform, sowie eine spannende Tätigkeit ohne Fahrzeit mit flexiblen Arbeitszeiten. Es werden keine besonderen Kenntnisse vorausgesetzt. Die Einarbeitung findet detailliert durch professionelle Kollegen statt. Die nötige technische Ausrüstung stellen wir Ihnen ohne zusätzlichen Kosten zur Verfügung. Die Arbeitsstelle kann gern nebenberuflich aufgenommen werden, sowie von Rentnern und Hausfrauen. Wir erwarten: - Sicherer Umgang mit E-mail, PC und Internet - Deutsch fließend, Fremdsprachen sind von Vorteil - Genauigkeit, Ehrlichkeit und Zielstrebigkeit Ihre Tätigkeitsschwerpunkte sind: - Dokumente empfangen, bearbeiten und weiterleiten - Unterlagen einscannen/kopieren - Emails bearbeiten - Aufgabe im Home-office in freier Zeiteinteilung - Umgang mit zur Verfügung gestellten Systemen Sie sind bereit für flexible Tätigkeit und die Arbeit im Homeoffice? Sollten Sie an diesen Arbeitsstellen Interesse haben, dann senden Sie uns ein Bewerbungsschreiben an: aleeld...@snakebite.com Wir freuen uns auf Ihre Antwort, Ihre persönlichen Daten behandeln wir selbstverständlich vertraulich. Mit freundlichen Grüßen Hartmann GmbH -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788581: cowbuilder can't build gpgme due to /dev/pts problems
Package: cowbuilder Version: 0.73 Control: affects -1 pbuilder gpgme1.0 When trying to build gpgme1.0 1.5.5-1 under cowbuilder, the tests fail with these error messages: echo x ./private-keys-v1.d/gpg-sample.stamp starting gpg-agent error starting gpg-agent PASS: initial.test t-encrypt.c:60: GPGME: Inappropriate ioctl for device FAIL: t-encrypt t-encrypt-sym.c:67: GPGME: Inappropriate ioctl for device FAIL: t-encrypt-sym t-encrypt-sign.c:116: GPGME: Inappropriate ioctl for device FAIL: t-encrypt-sign t-sign.c:124: GPGME: Inappropriate ioctl for device FAIL: t-sign t-signers.c:119: GPGME: Inappropriate ioctl for device FAIL: t-signers t-decrypt.c:65: GPGME: Inappropriate ioctl for device FAIL: t-decrypt t-verify.c:223: GPGME: Inappropriate ioctl for device FAIL: t-verify t-decrypt-verify.c:123: GPGME: Inappropriate ioctl for device FAIL: t-decrypt-verify t-sig-notation.c:149: GPGME: Inappropriate ioctl for device FAIL: t-sig-notation t-export.c:57: GPGME: Inappropriate ioctl for device FAIL: t-export t-import.c:229: GPGME: Inappropriate ioctl for device FAIL: t-import t-trustlist.c:50: GPGME: Inappropriate ioctl for device FAIL: t-trustlist t-edit.c:135: GPGME: Inappropriate ioctl for device FAIL: t-edit t-keylist.c:141: GPGME: Inappropriate ioctl for device FAIL: t-keylist t-keylist-sig.c:95: GPGME: Inappropriate ioctl for device FAIL: t-keylist-sig t-wait.c:59: GPGME: Inappropriate ioctl for device FAIL: t-wait t-encrypt-large.c:120: GPGME: Inappropriate ioctl for device FAIL: t-encrypt-large t-file-name.c:70: GPGME: Inappropriate ioctl for device FAIL: t-file-name PASS: t-gpgconf t-eventloop.c:201: GPGME: Inappropriate ioctl for device FAIL: t-eventloop t-thread1.c:124: GPGME: Inappropriate ioctl for device FAIL: t-thread1 gpg-agent not running PASS: final.test == 20 of 23 tests failed Please report to http://bugs.gnupg.org == Daiki Ueno points out that it may have something to do with /dev/pts: https://lists.gnupg.org/pipermail/gnupg-devel/2015-June/029998.html And it seems likely to be related, there are other odd error messages related to /dev/pts in the build process: At the beginning: I: mounting /dev/pts filesystem in the middle: Extracting templates from packages: 100% E: Can not write log (Is /dev/pts mounted?) - posix_openpt (2: No such file or directory) Selecting previously unselected package libpipeline1:amd64. and near the end: W: Could not unmount dev/pts: umount: /var/cache/pbuilder/build/cow.10684/dev/pts: not mounted W: Ignored error in unmount So maybe something is happening in the interaction between cowbuilder and pbuilder and mount? I don't know... Attached is the full buildlog, in case that's useful. it was made with: cowbuilder --build gpgme1.0_1.5.5-1.dsc Let me know if there are any other things you'd like me to try for debugging. --dkg - Copying COW directory forking: rm -rf /var/cache/pbuilder/build//cow.10684 forking: cp -al /var/cache/pbuilder/base.cow /var/cache/pbuilder/build//cow.10684 I: removed stale ilistfile /var/cache/pbuilder/build//cow.10684/.ilist forking: chroot /var/cache/pbuilder/build//cow.10684 cowdancer-ilistcreate /.ilist find . -xdev -path ./home -prune -o \( \( -type l -o -type f \) -a -links +1 -print0 \) | xargs -0 stat --format '%d %i ' - Invoking pbuilder forking: pbuilder build --buildplace /var/cache/pbuilder/build//cow.10684 --buildresult /var/cache/pbuilder/result/ --debbuildopts --no-targz --internal-chrootexec chroot /var/cache/pbuilder/build//cow.10684 cow-shell /root/src/gpgme/gpgme1.0_1.5.5-1.dsc W: /root/.pbuilderrc does not exist I: Running in no-targz mode I: using fakeroot in build. I: pbuilder: network access will be disabled during build I: Current time: Fri Jun 12 17:11:26 EDT 2015 I: pbuilder-time-stamp: 1434143487 I: copying local configuration I: mounting /proc filesystem I: mounting /run/shm filesystem I: mounting /dev/pts filesystem I: policy-rc.d already exists I: Obtaining the cached apt archive contents I: Installing the build-deps - Attempting to satisfy build-dependencies - Creating pbuilder-satisfydepends-dummy package Package: pbuilder-satisfydepends-dummy Version: 0.invalid.0 Architecture: amd64 Maintainer: Debian Pbuilder Team pbuilder-ma...@lists.alioth.debian.org Description: Dummy package to satisfy dependencies with aptitude - created by pbuilder This package was created automatically by pbuilder to satisfy the build-dependencies of the package being currently built. Depends: automake (= 1.14), debhelper ( 9~), dh-autoreconf, gnupg-agent, gnupg2, gpgsm, help2man, libassuan-dev ( 2.0.2), libgpg-error-dev ( 1.8), scdaemon, texinfo dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in '/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'. Selecting previously unselected package pbuilder-satisfydepends-dummy.
Bug#787249: clamav-daemon: clamdscan scans less than clamscan; worsened in latest release
Hi Sebastian, On 12.06.2015 22:07, Sebastian Andrzej Siewior wrote: On Fri, Jun 12, 2015 at 09:55:42PM +0200, Andreas Cadhalpun wrote: But before backporting this to the other branches, I think having it in unstable for a few days would be good. So what do you think about making an upload with the current changes? Sure thing. Unless Scott screams NOOO I will do it tomorrow. For Wheezy / Jessie I think we do it with next release upload. That's fine for me. There is nothing major that needs immediate attention. Correct? Deb6 is up to Scott. I think so. Best regards, Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788571: python-apt: unable to delete old directory '/usr/share/doc/python-apt/examples': Directory not empty
Package: python-apt Version: 1.0.0~beta1 I saw these warnings on upgrade: Unpacking python-apt-doc (1.0.0~beta1) over (0.9.4) ... dpkg: warning: unable to delete old directory '/usr/share/doc/python-apt/examples': Directory not empty dpkg: warning: unable to delete old directory '/usr/share/doc/python-apt/html/library': Directory not empty dpkg: warning: unable to delete old directory '/usr/share/doc/python-apt/html/tutorials': Directory not empty dpkg: warning: unable to delete old directory '/usr/share/doc/python-apt/html/c++': Directory not empty dpkg: warning: unable to delete old directory '/usr/share/doc/python-apt/html/_sources/library': Directory not empty dpkg: warning: unable to delete old directory '/usr/share/doc/python-apt/html/_sources/tutorials': Directory not empty dpkg: warning: unable to delete old directory '/usr/share/doc/python-apt/html/_sources/c++': Directory not empty dpkg: warning: unable to delete old directory '/usr/share/doc/python-apt/html/_sources/whatsnew': Directory not empty dpkg: warning: unable to delete old directory '/usr/share/doc/python-apt/html/_sources': Directory not empty dpkg: warning: unable to delete old directory '/usr/share/doc/python-apt/html/whatsnew': Directory not empty dpkg: warning: unable to delete old directory '/usr/share/doc/python-apt/html/_static': Directory not empty dpkg: warning: unable to delete old directory '/usr/share/doc/python-apt/html': Directory not empty And now I'm left with a bunch of files that don't belong to any package: $ find /usr/share/doc/python-apt/ -type f | xargs dpkg -S /dev/null dpkg-query: no path found matching pattern /usr/share/doc/python-apt/html/c++/api.html dpkg-query: no path found matching pattern /usr/share/doc/python-apt/html/c++/index.html dpkg-query: no path found matching pattern /usr/share/doc/python-apt/html/c++/embedding.html ... -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 4.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages python-apt depends on: ii libapt-inst1.5 1.0.9.10 ii libapt-pkg4.12 1.0.9.10 ii libc6 2.19-18 ii libgcc11:5.1.1-9 ii libstdc++6 5.1.1-9 ii python 2.7.9-1 ii python-apt-common 1.0.0~beta1 pn python:any none -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781767: Makes it unusable for my buckets too
Hi Matt, what do you mean by broke s3cmd? you mean the current jessie version is completely unusable? I honestly never tried it, my first release (used and packaged) as you know has been 1.5.2, and I'm using it since some months :) If the jessie version is completely broken I need to talk with release team, we might be able to make 1.5.2 go in jessie p-u (and eventually in the next point release) or drop it from the archive completely. I would have not released jessie with that package if I had been aware of its usefulness. (I would have updated it before if had the need of it, but I just didn't know about its existance before I had used it :) ) cheers! G. Il Venerdì 12 Giugno 2015 19:39, Matt Domsch m...@domsch.com ha scritto: By the time we knew Jesse's python SSL library change (actual cert validation) broke s3cmd it was too late to update the s3cmd package to a new enough version to fix it. And no I have not done a 1.5.0~rc1-X that is really just 1.5.2. But that is what is needed. On Jun 12, 2015 10:55 AM, Gianfranco Costamagna costamagnagianfra...@yahoo.it wrote: Control: tags -1 -patch thanks Not any particular problem, just that the jessie version seems totally useless... not for me :) this bug affects only part of people, not all of them ;) Anyway, the backport is still useful for people who want to try new features, and if you really want jessie to be fixed, you are encouraged to download the source and make the patch apply there I fully agree, but I do not have time to look at it right now :( I'll be happy to ask an spu and upload the package if a patch is provided! cheers, G. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788532: grub-efi-ia32-bin should be shipped on install DVD
Actually, that was the easy part. Except for a custom built grub-efi-i386 and some manual fiddling to find the install disc, I didn't need to do anything. Right, OK. Not exactly a common trail, then. :-) Well, brand new hardware that just works is relatively rare. I just happen to value Debian as a starting point for most of my Linux-related endeavours. Reduces configuration/customisation by much, and still manages to come without unnecessary bloat like certain other distributions. Also, I prefer apt over other package managers. Yup, I know - I wrote http://blog.einval.com/2015/04/23#ready_for_Jessie and the code described there. I've been hacking on Bay Trail systems for a ehile... :-) *Reading that article now* Right. If you'd just tried the multi-arch Debian CD netinst or DVD you'd probably have found that the installation just worked for you without having to fight with your own grub-efi-ia32 build etc.! What how where multiarch? Ok, it looks I completely missed that. Oops. And if I'm reading your blog correctly, the i386 images come with UEFI support, so that would be an option too. Except that I don't really like the idea of missing out on the advantages of amd64. But if it works... I'm *not* planning on adding the 32-bit grub binary packages to our amd64 CD images just yet. I'll want to add installer build code to get them booting easily in 32-bit first. Until then, please stick with the multi-arch images. OK? If that's the best way to get what I want, I'll give it a try. This seems pretty unique to Debian though? Ubuntu doesn't ship their i386 installers with EFI boot support, and they don't seem to have a multiarch installer either. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788569: libcpan-changes-perl: autopkgtest failure: t/self.t
Package: libcpan-changes-perl Version: 0.41-1 User: debian-p...@lists.debian.org Usertags: autopkgtest This package fails its autopkgtest checks on ci.debian.net. From http://ci.debian.net/packages/libc/libcpan-changes-perl/unstable/amd64/: t/self.t .. No such file or directory at /usr/share/perl5/CPAN/Changes.pm line 49. Dubious, test returned 2 (wstat 512, 0x200) No subtests run -- 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#786652: fails to include TEMPLATE.kvm, preventing creation of domains with KVM under apparmor
Hi Guido, On Fri, 12 Jun 2015 14:05:09 +0200 Guido =?iso-8859-1?Q?G=FCnther?= a...@sigxcpu.org wrote: On Sun, May 24, 2015 at 09:56:50AM +0200, Guido Günther wrote: Hi, Thanks for the report On Sun, May 24, 2015 at 01:00:52AM +, Luke Faraone wrote: Package: libvirt-daemon-system Version: 1.2.9-9 Severity: normal File: /etc/apparmor.d/libvirt/TEMPLATE.qemu May 24 00:07:47 aqua libvirtd[1130]: internal error: Child process (/usr/lib/libvirt/virt-aa-helper -p 0 -c -u libvirt-a8588abe-9d3b-4772-a95e- 0e312decc03a) unexpected exit status 1: virt-aa-helper.real: error: template does not exist This can be resolved by copying /etc/apparmor.d/libvirt/TEMPALTE.qemu to /etc/apparmor.d/libvirt/TEMPALTE.kvm Could you check if the attached patch fixes your problem as well? Could you please check if the packages at: http://honk.sigxcpu.org/projects/libvirt/snapshots/ make these copies superfluous. You should be able to remove the TEMPLATE.kvm with these installed. Feedback would be appreciated so we could squeeze this into a point release. Thanks for working on this. I can confirm that your test packages fix this bug. TEMPLATE.kvm isn't needed anymore. Cheers, Felix -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788575: liquidprompt seems to have been removed from unstable.
Package: liquidprompt Version: 1.9-1 After installing liquidprompt on its appearance in Debian unstable a day or two ago, I notice today that liquidprompt appears in the Obsolete and Locally Created Packages section in aptitude. I wrote to the maintainer, who asked me to open this bug report. I am using Debian unstable for amd64, updated daily. -- Thomas E. Vaughan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#377911: 377911 Arbeitsagentur Online Angebote für 2015
Guten Tag 377911, Vermittlungsagentur stellt Ihnen folgende interessante Tätigkeit in einem internationalen Team von zu Hause aus vor, ohne Fahrzeit, ohne Anfahrt, ohne Verkehrsstress. Wir haben qualitative und moderne Arbeitsplätze nicht nur in der Stadt, sondern auch in ländlichen Regionen europaweit und bieten gleichzeitig hervorragende Qualität für unsere Kunden Ab sofort sind nachfolgende Stellen frei: Mitarbeiter (m/w) für den Support im Home-office im Bereich Office und Kommunikation Wir bieten Ihnen einen Arbeitsplatz in Festanstellung oder als Freiberufler mit einem Stundenlohn von 20 € in der Stunde in selbständigen Arbeitsweise und einer modernen Beschäftigungsform, sowie eine spannende Tätigkeit ohne Arbeitsweg mit flexiblen Arbeitszeiten. Es werden keine Fachkenntnisse vorausgesetzt. Die Einarbeitung findet schrittweise durch professionelle Kollegen statt. Die nötige technische Ausrüstung stellen wir Ihnen ohne zusätzlichen Kosten zur Verfügung. Die Stelle kann gern nebenberuflich ausgeführt werden, sowie von Rentnern und Hausfrauen. Was von Ihnen erwartet wird: - Sicherer Umgang mit E-mail, PC und Internet - Deutsch fließend, Fremdsprachen wären von Vorteil - Genauigkeit, Ehrlichkeit und Zielstrebigkeit Ihre Tätigkeitsschwerpunkte sind: - Dokumente engegennehmen, bearbeiten und weitersenden - Unterlagen scannen/kopieren - E-Mails beantworten - Aufgabe im Home Office in freier Zeiteinteilung - Arbeit mit zur Verfügung gestellten Systemen Sie sind bereit für flexible Arbeitszeitmodelle und die Arbeit im Homeoffice? Wenn wir Ihr Interesse geweckt haben, senden Sie uns Ihre Bewerbung per E-Mail an: adafi1...@australiamail.com Wir freuen uns auf Ihre Bewerbung, Ihre persönlichen Unterlagen behandeln wir selbstverständlich vertraulich. Es grüßt Sie Ihre Reichert KG -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784942: autopkgtest: fails to read Files: from perfectly valid .changes file
-=| Antonio Terceiro, 29.05.2015 08:01:50 -0300 |=-
On Tue, May 26, 2015 at 06:31:15PM +0200, Martin Pitt wrote:
Control: tag -1 unreproducible
Hey Antonio,
sorry for the late response.
Antonio Terceiro [2015-05-10 19:45 -0300]:
I am missing anything?
$ adt-run --user debci --output-dir /tmp/adt-run
../build-area/ruby-defaults_2.1.5.0_amd64.changes --- schroot
debci-unstable-amd64
adt-run: error: ../build-area/ruby-defaults_2.1.5.0_amd64.changes is
invalid and does not contain Files:
[20]$ cat ../build-area/ruby-defaults_2.1.5.0_amd64.changes
I tried that .changes files, and it works correctly here. Maybe just
pasting it into the email destroyed some subtle whitespace? Can you
attach the file instead?
I also got ruby-defaults 2.1.5.0 from the archive, sbuilt it, and ran
adt-run on the binary unsigned .changes, which also worked.
If you can still reproduce this, I can also send you some patch for
enhancing debugging in runner/adt-run files_from_dsc() -- it seems the
parse_rfc822() runs into a corner case?
I can still reproduce it, yes:
$ adt-run --user debci --output-dir /tmp/adt-run
ruby-defaults_2.1.5.0_amd64.changes --- schroot debci-unstable-amd64
adt-run: error: ruby-defaults_2.1.5.0_amd64.changes is invalid and does not
contain Files:
[20]$ debsign ruby-defaults_2.1.5.0_amd64.changes
[...]
Successfully signed dsc and changes files
$ adt-run --user debci --output-dir /tmp/adt-run
ruby-defaults_2.1.5.0_amd64.changes --- schroot debci-unstable-amd64
adt-run [07:57:45]: version 3.14.2
adt-run [07:57:45]: command line: /usr/bin/adt-run --user debci --output-dir
/tmp/adt-run ruby-defaults_2.1.5.0_amd64.changes --- schroot
debci-unstable-amd64
adt-run [07:57:46]: testbed dpkg architecture: amd64
adt-run [07:57:46]: source ruby-defaults_2.1.5.0.dsc
OK
[...]
adt-run [07:57:59]: test smoke-test: ---]
adt-run [07:57:59]: test smoke-test: - - - - - - - - - - results - - - - - -
- - - -
smoke-test PASS
The original ruby-defaults_2.1.5.0_amd64.changes, without the signature,
is attached.
I have another failing example (attached). Debsign-ing it works around
the problem.
HTH,
dam
Format: 1.8
Date: Fri, 12 Jun 2015 17:52:22 +0200
Source: libwww-mechanize-shell-perl
Binary: libwww-mechanize-shell-perl
Architecture: source all
Version: 0.55-1
Distribution: UNRELEASED
Urgency: low
Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org
Changed-By: gregor herrmann gre...@debian.org
Description:
libwww-mechanize-shell-perl - interactive shell for WWW::Mechanize
Changes:
libwww-mechanize-shell-perl (0.55-1) UNRELEASED; urgency=low
.
IGNORE-VERSION: 0.53-1
# no code changes
.
[ Ansgar Burchardt ]
* debian/control: Convert Vcs-* fields to Git.
.
[ Angel Abad ]
* Email change: Angel Abad - an...@debian.org
.
[ gregor herrmann ]
* debian/control: update {versioned,alternative} (build) dependencies.
.
[ Salvatore Bonaccorso ]
* Change Vcs-Git to canonical URI (git://anonscm.debian.org)
* Change search.cpan.org based URIs to metacpan.org based URIs
.
[ Florian Schlichting ]
* Import Upstream version 0.53
* Bump Standards-Version to 3.9.4 (update to copyright-format 1.0)
* Bump dh compatibility to level 8 (no changes necessary)
.
[ gregor herrmann ]
* Strip trailing slash from metacpan URLs.
.
[ Salvatore Bonaccorso ]
* Update Vcs-Browser URL to cgit web frontend
.
[ gregor herrmann ]
* Add debian/upstream/metadata
* Import upstream version 0.55
Checksums-Sha1:
1329a48c84561a525779bc5e8bccf55356121da1 1767
libwww-mechanize-shell-perl_0.55-1.dsc
f584e573a117be957bcd6e0414b508652c2e8db2 52522
libwww-mechanize-shell-perl_0.55.orig.tar.gz
1b7c3e00e5b015d52cff9b0c6f767801639c2c87 4012
libwww-mechanize-shell-perl_0.55-1.debian.tar.xz
59ec8a273c93d18c086744ef280e9f085f59ef3a 36926
libwww-mechanize-shell-perl_0.55-1_all.deb
Checksums-Sha256:
2c09778aa11761d7fb93ab15fd391d61d35108e7e964470ece84478cbd40d709 1767
libwww-mechanize-shell-perl_0.55-1.dsc
b0231f7821dcd1d579723d4aea05cdeb023013434f2faf119dd03b4bd13efbde 52522
libwww-mechanize-shell-perl_0.55.orig.tar.gz
b52c39d08b353d3d00ddeaedd02132e6a3b93299ba965f6313a1aee3e27a12e5 4012
libwww-mechanize-shell-perl_0.55-1.debian.tar.xz
8f89e07cdf1a960156fe0c314297c1137f39331f3052afcf6ab0e6193d051d92 36926
libwww-mechanize-shell-perl_0.55-1_all.deb
Files:
d4364cd21926f43f1cc0efc41572b58f 1767 perl optional
libwww-mechanize-shell-perl_0.55-1.dsc
c18f81f8452301a2da58b00cc9970da5 52522 perl optional
libwww-mechanize-shell-perl_0.55.orig.tar.gz
b0b306988376c1ae103c9342d7ea4386 4012 perl optional
libwww-mechanize-shell-perl_0.55-1.debian.tar.xz
3aef16dae33fa71446b1fc07e0824763 36926 perl optional
libwww-mechanize-shell-perl_0.55-1_all.deb
Bug#768991: O: github-backup -- backs up data from GitHub
Control: owner -1 ! Control: retitle -1 ITA: github-backup -- backs up data from GitHub On Mon, Nov 10, 2014 at 12:27:45PM -0400, Joey Hess wrote: Package: wnpp Severity: normal I have orphaned the github-backup package. I will continue to develop the software upstream. I'll adopt it. Cheers, -- James GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy james...@debian.org signature.asc Description: Digital signature
Bug#787249: clamav-daemon: clamdscan scans less than clamscan; worsened in latest release
On Fri, Jun 12, 2015 at 09:55:42PM +0200, Andreas Cadhalpun wrote: Hi Sebastian, Hi Andreas, On 12.06.2015 21:46, Sebastian Andrzej Siewior wrote: On 2015-06-05 21:52:14 [+0200], Andreas Cadhalpun wrote: I've just pushed a commit implementing this. Since this again depends on a 'dpkg --compare-versions', we should backport it to all branches. Sure thing. Is there something you want me to do? Is there something I need to take care of while adding version in --compare-versions? The important thing is that the version one compares against is larger than all previous versions one could have installed, but smaller than the version adding the check. Okay. But before backporting this to the other branches, I think having it in unstable for a few days would be good. So what do you think about making an upload with the current changes? Sure thing. Unless Scott screams NOOO I will do it tomorrow. For Wheezy / Jessie I think we do it with next release upload. There is nothing major that needs immediate attention. Correct? Deb6 is up to Scott. Best regards, Andreas Sebastian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788574: Watch file doesn't work
Package: libjs-raphael Version: 2.1.0-1 Severity: minor Tags: patch Hi It looks like your d/watch file doesn't work anymore. Attached is an update. Ping me if you need a sponsor. Cheers -- System Information: Debian Release: 8.1 APT prefers stable APT policy: (990, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) libjs-raphael depends on no packages. libjs-raphael recommends no packages. Versions of packages libjs-raphael suggests: ii javascript-common 11 -- no debconf information version=3 opts=uversionmangle=s/\/(v|semver|0)// \ http://githubredir.debian.net/github/DmitryBaranovskiy/raphael (.*).tar.gz
Bug#8667: Liste neuer Stellenausschreibungen für Sie.
Sehr geehrte/r 8667, Vermittlungsagentur stellt Ihnen nachfolgend eine attraktive Arbeit in einem erfolgreichen Team im Home-office Bereich vor, ohne Fahrtkosten, ohne Anfahrtswege, ohne Verkehrsstress. Wir haben qualifizierte und attraktive Arbeitsplätze nicht nur in der Stadt, sondern auch in ländlichen Regionen landesweit und bieten dabei hervorragende Qualität für unsere Auftraggeber. Zur Erweiterung unseres Teams suchen wir ab sofort: Angestellte (m/w) für den Support im Home-office im Bereich Office und Kommunikation Wir bieten Ihnen einen Job in Festanstellung oder als Freiberufler mit einem Stundenlohn von 20 Euro pro Stunde in selbständigen Arbeitsweise und einer familienfreunflichen Beschäftigungsform, sowie eine abwechslungsreiche Tätigkeit ohne Fahrzeit mit flexiblen Arbeitszeiten. Es werden keine Fachkenntnisse vorausgesetzt. Die Einarbeitung findet detailliert durch professionelle Kollegen statt. Die nötige technische Ausstattung stellen wir Ihnen kostenlos zur Verfügung. Die Arbeit kann gern nebenberuflich ausgeführt werden, sowie von Rentnern und Hausfrauen. Wir erwarten: - Sicherer Umgang mit Email, PC und Internet - Deutsch fließend, Fremdsprachen sind vorteilhaft - Genauigkeit und Zielstrebigkeit Ihre Aufgaben sind: - Dokumente engegennehmen, überarbeiten und weitersenden - Dokumente einscannen/kopieren - E-Mails bearbeiten - Aufgabe im Home-office in freier Zeiteinteilung - Arbeit mit zur Verfügung gestellten Systemen Sie sind bereit für flexible Tätigkeit und die Arbeit im Home-office? Wenn wir Ihr Interesse geweckt haben, senden Sie uns Ihre Bewerbung per E-Mail an: aririo1...@gardener.com Wir freuen uns auf Ihre Bewerbung, Ihre persönlichen Daten behandeln wir selbstverständlich vertraulich. Mit freundlichen Grüßen Pfeiffer KG Alessandro Azzalin - Stars nati per animare Friend - seaclub Francorosso Akassia Swiss Resort Marsa Alam - Egypt Mobile 0039/3489014657 Mobile 0020/1014677396 alessandro.azza...@starswiss.cc www.starswiss.cc -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788576: ITP: pysal -- Python Spatial Analysis Library
Package: wnpp Owner: Johan Van de Wauw johan.vandew...@gmail.com Severity: wishlist X-Debbugs-CC: pkg-grass-de...@lists.debian.org * Package name: pysal Version : 1.9.1 Upstream Author : Serge Rey and contributors * URL : https://pysal.readthedocs.org/en/latest/ * License : BSD-3-Clause Programming Lang: python Description : Python Spatial Analysis Library PySAL is an open source library of spatial analysis functions written in Python intended to support the development of high level applications. It is important to underscore what PySAL is, and is not, designed to do. First and foremost, PySAL is a library in the fullest sense of the word. Developers looking for a suite of spatial analytical methods that they can incorporate into application development should feel at home using PySAL. Spatial analysts ho may be carrying out research projects requiring customized scripting, extensive simulation analysis, or those seeking to advance the state of the art in spatial analysis should also find PySAL to be a useful foundation for their work. . End users looking for a user friendly graphical user interface for spatial analysis should not turn to PySAL directly. Instead, we would direct them to projects like STARS and the GeoDaX suite of software products which wrap PySAL functionality in GUIs. At the same time, we expect that with developments such as the Python based plug-in architectures for QGIS, GRASS, and the toolbox extensions for ArcGIS, that end user access to PySAL functionality will be widening in the near future. signature.asc Description: OpenPGP digital signature
Bug#788578: docky: Graphics corruption after resume from sleep
Package: docky Version: 2.2.0-2 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? The steps to reproduce are as follows. 1) Put PC into sleep. 2) Resume from sleep. * What was the outcome of this action? I have docky set to autohide. After resuming from sleep, a vertical band of graphics corruption appears. The band fills the space between the edge of the dock, and the maximum width it expands to when mousing-over items. * What outcome did you expect instead? I didn't expect the vertical band of random pixels :). I'm not 100% confident this is a bug in docky per se, but I can close docky, restart it, and the problem goes away. I'm using the propriatary AMD fglrx driver from the repos, with an R9270X graphics card. All other software is from the repos. Short list of hardware: AMD FX8350 AMD R9 270X Asus Sabertooth R2 *** End of the template - remove these template lines *** -- System Information: Debian Release: 8.1 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/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages docky depends on: ii gconf2 3.2.6-3 ii libc6 2.19-18 ii libdbus-glib2.0-cil 0.6.0-1 ii libdbus2.0-cil 0.8.1-1 ii libgconf2.0-cil 2.24.2-3 ii libglib2.0-02.42.1-1 ii libglib2.0-cil 2.12.10-5.1 ii libgnome-keyring1.0-cil 1.0.0-4 ii libgnomedesktop2.20-cil 2.26.0-8 ii libgtk2.0-0 2.24.25-3 ii libgtk2.0-cil 2.12.10-5.1 ii libmono-addins0.2-cil 1.0+git20130406.adcd75b-3 ii libmono-cairo4.0-cil3.2.8+dfsg-10 ii libmono-corlib4.5-cil 3.2.8+dfsg-10 ii libmono-posix4.0-cil3.2.8+dfsg-10 ii libmono-sharpzip4.84-cil3.2.8+dfsg-10 ii libmono-system-core4.0-cil 3.2.8+dfsg-10 ii libmono-system-web4.0-cil 3.2.8+dfsg-10 ii libmono-system-xml-linq4.0-cil 3.2.8+dfsg-10 ii libmono-system-xml4.0-cil 3.2.8+dfsg-10 ii libmono-system4.0-cil 3.2.8+dfsg-10 ii libnotify0.4-cil0.4.0~r3032-7 ii librsvg2-2.18-cil 2.26.0-8 ii librsvg2-common 2.40.5-1 ii libwnck2.20-cil 2.26.0-8 ii libx11-62:1.6.2-3 ii mono-runtime3.2.8+dfsg-10 Versions of packages docky recommends: pn dockmanager none docky 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#788577: libseccomp: add some autopkgtests
Package: libseccomp Version: 2.2.1-1 Severity: wishlist Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu wily ubuntu-patch Dear Maintainer, In Ubuntu, the attached patch was applied to achieve the following: - add autopkgtests Thanks for considering the patch. -- System Information: Debian Release: jessie/sid APT prefers vivid-updates APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.19.0-20-generic (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) diff -Nru libseccomp-2.2.1/debian/changelog libseccomp-2.2.1/debian/changelog diff -Nru libseccomp-2.2.1/debian/control libseccomp-2.2.1/debian/control --- libseccomp-2.2.1/debian/control 2015-05-17 12:05:40.0 -0500 +++ libseccomp-2.2.1/debian/control 2015-06-12 15:59:10.0 -0500 @@ -5,6 +5,7 @@ Build-Depends: debhelper (= 9), dh-autoreconf, linux-libc-dev Standards-Version: 3.9.6 Homepage: https://sourceforge.net/projects/libseccomp/ +XS-Testsuite: autopkgtest Package: libseccomp-dev Section: libdevel diff -Nru libseccomp-2.2.1/debian/tests/control libseccomp-2.2.1/debian/tests/control --- libseccomp-2.2.1/debian/tests/control 1969-12-31 18:00:00.0 -0600 +++ libseccomp-2.2.1/debian/tests/control 2015-05-04 15:21:11.0 -0500 @@ -0,0 +1,3 @@ +Tests: test-filter test-scmp_sys_resolver +Restrictions: allow-stderr +Depends: @, build-essential, linux-libc-dev diff -Nru libseccomp-2.2.1/debian/tests/data/all-3.19.filter libseccomp-2.2.1/debian/tests/data/all-3.19.filter --- libseccomp-2.2.1/debian/tests/data/all-3.19.filter 1969-12-31 18:00:00.0 -0600 +++ libseccomp-2.2.1/debian/tests/data/all-3.19.filter 2015-05-01 13:04:43.0 -0500 @@ -0,0 +1,414 @@ +# all syscalls from 3.19 +syscalls: +accept +accept4 +access +acct +add_key +adjtimex +afs_syscall +alarm +arch_prctl +arm_fadvise64_64 +arm_sync_file_range +bdflush +bind +bpf +break +breakpoint +brk +cacheflush +capget +capset +chdir +chmod +chown +chown32 +chroot +clock_adjtime +clock_getres +clock_gettime +clock_nanosleep +clock_settime +clone +close +connect +creat +create_module +delete_module +dup +dup2 +dup3 +epoll_create +epoll_create1 +epoll_ctl +epoll_ctl_old +epoll_pwait +epoll_wait +epoll_wait_old +eventfd +eventfd2 +execve +execveat +exit +exit_group +faccessat +fadvise64 +fadvise64_64 +fallocate +fanotify_init +fanotify_mark +fchdir +fchmod +fchmodat +fchown +fchown32 +fchownat +fcntl +fcntl64 +fdatasync +fgetxattr +finit_module +flistxattr +flock +fork +fremovexattr +fsetxattr +fstat +fstat64 +fstatat64 +fstatfs +fstatfs64 +fsync +ftime +ftruncate +ftruncate64 +futex +futimesat +getcpu +getcwd +getdents +getdents64 +getegid +getegid32 +geteuid +geteuid32 +getgid +getgid32 +getgroups +getgroups32 +getitimer +get_kernel_syms +get_mempolicy +getpeername +getpgid +getpgrp +getpid +getpmsg +getppid +getpriority +getrandom +getresgid +getresgid32 +getresuid +getresuid32 +getrlimit +get_robust_list +getrusage +getsid +getsockname +getsockopt +get_thread_area +gettid +gettimeofday +getuid +getuid32 +getxattr +gtty +idle +init_module +inotify_add_watch +inotify_init +inotify_init1 +inotify_rm_watch +io_cancel +ioctl +io_destroy +io_getevents +ioperm +iopl +ioprio_get +ioprio_set +io_setup +io_submit +ipc +kcmp +kexec_file_load +kexec_load +keyctl +kill +lchown +lchown32 +lgetxattr +link +linkat +listen +listxattr +llistxattr +_llseek +lock +lookup_dcookie +lremovexattr +lseek +lsetxattr +lstat +lstat64 +madvise +mbind +memfd_create +migrate_pages +mincore +mkdir +mkdirat +mknod +mknodat +mlock +mlockall +mmap +mmap2 +modify_ldt +mount +move_pages +mprotect +mpx +mq_getsetattr +mq_notify +mq_open +mq_timedreceive +mq_timedsend +mq_unlink +mremap +msgctl +msgget +msgrcv +msgsnd +msync +multiplexer +munlock +munlockall +munmap +name_to_handle_at +nanosleep +newfstatat +_newselect +nfsservctl +nice +oldfstat +oldlstat +oldolduname +oldstat +olduname +open +openat +open_by_handle_at +pause +pciconfig_iobase +pciconfig_read +pciconfig_write +perf_event_open +personality +pipe +pipe2 +pivot_root +poll +ppoll +prctl +pread64 +preadv +prlimit64 +process_vm_readv +process_vm_writev +prof +profil +pselect6 +ptrace +putpmsg +pwrite64 +pwritev +query_module +quotactl +read +readahead +readdir +readlink +readlinkat +readv +reboot +recv +recvfrom +recvmmsg +recvmsg +remap_file_pages +removexattr +rename +renameat +renameat2 +request_key +restart_syscall +rmdir +rtas +rt_sigaction +rt_sigpending +rt_sigprocmask +rt_sigqueueinfo +rt_sigreturn +rt_sigsuspend +rt_sigtimedwait +rt_tgsigqueueinfo +sched_getaffinity +sched_getattr +sched_getparam +sched_get_priority_max +sched_get_priority_min +sched_getscheduler +sched_rr_get_interval +sched_setaffinity +sched_setattr +sched_setparam +sched_setscheduler +sched_yield +seccomp +security +select
Bug#788579: ITP: golang-yaml.v2 -- Go package for encoding and decoding YAML
Package: wnpp Severity: wishlist X-Debbugs-CC: pkg-go-maintain...@lists.alioth.debian.org * Package name: golang-yaml.v2 Version : 0.0~git20150611 Upstream Author : Gustavo Niemeyer gust...@niemeyer.net * URL : https://github.com/go-yaml/yaml/ * License : LGPLv3 Description : Go package for encoding and decoding YAML A library for the Go programming language, which allows programs using it to encode and decode YAML up to 1.2, with support also for anchors, tags and map merging. signature.asc Description: OpenPGP digital signature
Bug#787249: [Pkg-clamav-devel] Bug#787249: Bug#787249: clamav-daemon: clamdscan scans less than clamscan; worsened in latest release
On 2015-06-05 21:52:14 [+0200], Andreas Cadhalpun wrote: Hi Sebastian, Hi Andreas, I've just pushed a commit implementing this. Since this again depends on a 'dpkg --compare-versions', we should backport it to all branches. Sure thing. Is there something you want me to do? Is there something I need to take care of while adding version in --compare-versions? Best regards, Andreas Sebastian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#110015: Vermittlungsagentur bietet Jobs für Sie an 110015
Guten Tag 110015, die Arbeitsagentur stellt Ihnen nachfolgend eine interessante Arbeit in einem internationalen Team im Home Office Bereich vor, ohne Fahrzeit, ohne Anfahrt, ohne Verkehrsstress. Wir schaffen qualitative und attraktive Arbeitsplätze nicht nur in der Stadt, sondern auch auf dem Land landesweit und bieten gleichzeitig hervorragende Qualität für unsere Auftraggeber. Ab sofort sind folgenden Stellen zu besetzen: Mitarbeiter (m/w) für Home Office Tätigkeit im Bereich Telekommunikation und Büroarbeit Wir bieten Ihnen einen Job in Festanstellung oder als Freiberufler mit einem Stundenlohn von 20 € in der Stunde in eigenverantwortlichen Arbeitsweise und einer familienfreunflichen Beschäftigungsform, sowie eine spannende Tätigkeit ohne Fahrzeit mit flexiblen Arbeitszeiten. Es werden keine Fachkenntnisse vorausgesetzt. Die Einarbeitung findet schrittweise durch professionelle Mitarbeiter statt. Die benötigte technische Ausrüstung stellen wir Ihnen ohne zusätzlichen Kosten zur Verfügung. Die Stelle kann sogar nebenberuflich aufgenommen werden, sowie von Rentnern und Hausfrauen. Wir erwarten: - Unproblematischer Umgang mit E-mail, PC und Internet - Deutsch fließend, Fremdsprachen sind von Vorteil - Genauigkeit, Ehrlichkeit und Zielstrebigkeit Ihre Tätigkeitsschwerpunkte sind: - Dokumente empfangen, überarbeiten und weitersenden - Dokumente scannen/kopieren - Emails bearbeiten - Aufgabe im Home-office in freier Zeiteinteilung - Arbeit mit zur Verfügung gestellten Büroausstattungen Sie sind bereit für flexible Tätigkeit und die Arbeit im Homeoffice? Sollten Sie an diesen Arbeitsstellen Interesse haben, dann senden Sie uns ein Bewerbungsschreiben an: adafi1...@australiamail.com Wir freuen uns auf Ihre Antwort, Ihre persönlichen Daten behandeln wir selbstverständlich vertraulich. Hochachtungsvoll Maier Gbr. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781767: Makes it unusable for my buckets too
The breakage predates you Gianfranco. Not your fault. Python got updated in Jesse right before it released. That python added in https ssl certificate checking for all HTTPSConnection() usage, per the RFC regarding how to check the certificate. The RFC explicitly disallows bucket.with.dot.s3.amazonaws.com DNS names from matching *.s3.amazonaws.com wildcard certificates. But that's exactly what S3 uses. So we had to add a custom certificate checker into v1.5.2 to fix it correctly. We were past freeze for updating packages in jesse at that point, so we couldn't get the fix into the main release. (in Fedora, we can easily issue updates into an updates repo, so I didn't think much about it.; apparently that's harder in Debian to release updates). On Fri, Jun 12, 2015 at 4:05 PM, Gianfranco Costamagna costamagnagianfra...@yahoo.it wrote: Hi Matt, what do you mean by broke s3cmd? you mean the current jessie version is completely unusable? I honestly never tried it, my first release (used and packaged) as you know has been 1.5.2, and I'm using it since some months :) If the jessie version is completely broken I need to talk with release team, we might be able to make 1.5.2 go in jessie p-u (and eventually in the next point release) or drop it from the archive completely. I would have not released jessie with that package if I had been aware of its usefulness. (I would have updated it before if had the need of it, but I just didn't know about its existance before I had used it :) ) cheers! G. Il Venerdì 12 Giugno 2015 19:39, Matt Domsch m...@domsch.com ha scritto: By the time we knew Jesse's python SSL library change (actual cert validation) broke s3cmd it was too late to update the s3cmd package to a new enough version to fix it. And no I have not done a 1.5.0~rc1-X that is really just 1.5.2. But that is what is needed. On Jun 12, 2015 10:55 AM, Gianfranco Costamagna costamagnagianfra...@yahoo.it wrote: Control: tags -1 -patch thanks Not any particular problem, just that the jessie version seems totally useless... not for me :) this bug affects only part of people, not all of them ;) Anyway, the backport is still useful for people who want to try new features, and if you really want jessie to be fixed, you are encouraged to download the source and make the patch apply there I fully agree, but I do not have time to look at it right now :( I'll be happy to ask an spu and upload the package if a patch is provided! cheers, G.
Bug#788583: RFS: blktool -- tune low-level block device parameters [ITA]
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package blktool Package name: blktool Version : 4-7 Upstream Author : Jeff Garzik jgar...@pobox.com URL : http://sourceforge.net/projects/gkernel/files/blktool/ License : GPL v2 Section : admin It builds those binary packages: blktool- tune low-level block device parameters To access further information about this package, please visit the following URL: http://mentors.debian.net/package/blktool Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/b/blktool/blktool_4-7.dsc Changes since the last upload: * QA upload * New maintainer. (Closes: #695127). * Fix blktool readonly is broken (Closes: #641164). * bump debhelper version to 9 * fix changelog-should-mention-qa * fix ancient-standards-version 3.7.2.2 (current is 3.9.6) * fix vcs-field-not-canonical * fix xs-vcs-header-in-debian-control * add homepage Regards, Azat Khuzhin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
