Bug#778558: lintian: Cannot process ganeti - intltool-extract issues
Package: lintian Version: 2.5.30+deb8u3 Severity: normal From lintian.d.o's logs: N: Processing source package ganeti (version 2.12.0-3, arch source) ... print() on closed filehandle OUT at /usr/share/intltool-debian/intltool-extract line 942. print() on closed filehandle OUT at /usr/share/intltool-debian/intltool-extract line 942. print() on closed filehandle OUT at /usr/share/intltool-debian/intltool-extract line 942. print() on closed filehandle OUT at /usr/share/intltool-debian/intltool-extract line 942. /usr/bin/xgettext: error while opening ../templates/versioned.templates.h for reading: No such file or directory ERROR: xgettext failed to generate PO template file. Please consult error message above if there is any. command failed with error code 1 at /srv/lintian.debian.org/root/checks/po-debconf.pm line 182 internal error: cannot run po-debconf check on package source:ganeti/2.12.0-3 warning: skipping check of source:ganeti/2.12.0-3 N: ~Niels -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778562: lldb-3.5: lldb fails on x86_64 binaries
Package: lldb-3.5 Version: 1:3.5-9 Severity: important Dear Maintainer, Install package lldb (lldb-3.5) on Debian Jessie x86_64. Trying to run lldb was ineffective. Ex: ~$ lldb /bin/ls error: '/bin/ls' doesn't contain the architecture x86_64 (lldb) quit This makes it so that I'm unable to use lldb at all. I found this bug upstream: http://llvm.org/bugs/show_bug.cgi?id=20400 This comment in particular seems to contain relevant information: http://llvm.org/bugs/show_bug.cgi?id=20400#c8 I'm not sure if this is a problem upstream or the packaging itself. Regardless, it looks like lldb disagrees about what the host triplet should be, and it causes it to be unusable on Jessie. Some other things I've tried: Explicitly building my own binaries with clang, and attempting to use lldb on them. lldb-3.4 also appears to work successfully. -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.18.5 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages lldb-3.5 depends on: ii libc62.19-13 ii libedit2 3.1-20140620-2 ii libffi6 3.1-2+b2 ii libgcc1 1:4.9.1-19 ii liblldb-3.5 1:3.5-9 ii libllvm3.5 1:3.5-9 ii libstdc++6 4.9.1-19 ii libtinfo55.9+20140913-1+b1 ii llvm-3.5-dev 1:3.5-9 ii python 2.7.8-3 ii python-lldb-3.5 1:3.5-9 ii zlib1g 1:1.2.8.dfsg-2+b1 lldb-3.5 recommends no packages. lldb-3.5 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#778487: s3ql: Needs python-dugong = 3.4
So please tighten the dependencies of s3ql 2.13 to require python3-dugong = 3.4 At least according to https://packages.debian.org/source/unstable/s3ql, this is exactly what the dependency is. Where did you get the package from? Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.« -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755722: systemd must sync systemclock to RTC on shutdown
Hello all, For jessie+1/experimental onward, we'll fix this properly by enabling timesyncd by default. It won't start if ntp or similar are installed. This will make sure that the hw clock will be updated often enough, and we won't poke false data into it: http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=experimentalid=929bece5326 This is a new feature though, and as such most probably not appropriate for jessie at this point. For master (i. e. testing/jessie), I prepared and tested the attached patch. I'm still kind of hesitant to apply it as it's solving the problem in a rather questionable, insufficient, and conceptually wrong way. However, with that it would stay bug compatible with sysvinit in jessie. Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) From 74563299c38608afac0ab79e6926d74d9e26e853 Mon Sep 17 00:00:00 2001 From: Martin Pitt martin.p...@ubuntu.com Date: Mon, 16 Feb 2015 16:14:23 +0100 Subject: [PATCH] Add hwclock.service to sync the system clock to the hardware clock on shutdown This provides monotonic time for reboots. Thanks to Stefan Fritsch for the initial unit. Note: this is a hack for jessie; the next Debian release will enable timesyncd by default. Closes: #755722 --- debian/changelog | 9 + debian/extra/hwclock.service | 14 ++ debian/rules | 2 +- debian/systemd.links | 3 ++- debian/systemd.postinst | 4 5 files changed, 30 insertions(+), 2 deletions(-) create mode 100644 debian/extra/hwclock.service diff --git a/debian/changelog b/debian/changelog index 6d81277..4ebc8af 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,12 @@ +systemd (215-13) UNRELEASED; urgency=medium + + * Add hwclock.service to sync the system clock to the hardware clock on +shutdown, to provide monotonic time for reboots. (Note: this is a hack for +jessie; the next Debian release will enable timesyncd by default). +(Closes: #755722) + + -- Martin Pitt mp...@debian.org Mon, 16 Feb 2015 16:11:12 +0100 + systemd (215-12) unstable; urgency=medium [ Martin Pitt ] diff --git a/debian/extra/hwclock.service b/debian/extra/hwclock.service new file mode 100644 index 000..1e0f99a --- /dev/null +++ b/debian/extra/hwclock.service @@ -0,0 +1,14 @@ +[Unit] +Description=Synchronise Hardware Clock to System Clock +DefaultDependencies=no +Before=shutdown.target +ConditionFileIsExecutable=!/usr/sbin/ntpd +ConditionFileIsExecutable=!/usr/sbin/openntpd +ConditionFileIsExecutable=!/usr/sbin/chrony + +[Service] +Type=oneshot +ExecStart=/sbin/hwclock -D --systohc + +[Install] +WantedBy=reboot.target halt.target poweroff.target diff --git a/debian/rules b/debian/rules index 4f79678..5d69e86 100755 --- a/debian/rules +++ b/debian/rules @@ -183,7 +183,7 @@ override_dh_install: debian/systemd/lib/lsb/init-functions.d/40-systemd install --mode=644 debian/tmpfiles.d/debian.conf \ debian/systemd/usr/lib/tmpfiles.d/ - install --mode=644 debian/debian-fixup.service debian/ifup@.service debian/extra/getty-static.service \ + install --mode=644 debian/debian-fixup.service debian/ifup@.service debian/extra/getty-static.service debian/extra/hwclock.service \ debian/systemd/lib/systemd/system/ install -D --mode=644 debian/extra/network-pre.conf \ debian/systemd/lib/systemd/system/networking.service.d/network-pre.conf diff --git a/debian/systemd.links b/debian/systemd.links index 74ab5a7..1c29732 100644 --- a/debian/systemd.links +++ b/debian/systemd.links @@ -31,7 +31,8 @@ # systemd sets the hwclock internally # http://cgit.freedesktop.org/systemd/systemd/commit/?id=7948c4dfbea73ac21250b588089039aa17a90386 -/dev/null /lib/systemd/system/hwclock.service +# we ship a replacement hwclock.service for shutdown, but disable the other one +# from util-linux /dev/null /lib/systemd/system/hwclockfirst.service # We use native mount support so mask those services diff --git a/debian/systemd.postinst b/debian/systemd.postinst index 488df32..f5c9913 100644 --- a/debian/systemd.postinst +++ b/debian/systemd.postinst @@ -131,6 +131,10 @@ if dpkg --compare-versions $2 lt 214-1; then systemctl enable remote-fs.target || true fi +if dpkg --compare-versions $2 lt 215-12; then +systemctl enable hwclock.service || true +fi + # Re-run systemctl enable for any service that was enabled when preinst was run. if dpkg --compare-versions $2 ge 204; then while read UNIT ; do -- 2.1.4 signature.asc Description: Digital signature
Bug#778348: release-notes: document security status for libv8/nodejs in jessie
Hi, I see your mail wrong, so here is a forward with the correct mail. ~Niels Forwarded Message Subject: Re: Bug#778348: release-notes: document security status for libv8/nodejs in jessie Date: Mon, 16 Feb 2015 09:11:33 +0100 From: Niels Thykier ni...@thykier.net To: Michael Gilbert mgilb...@debian.org, 778...@bugs.debian.org, sb...@mailbox.org CC: pkg-javascript-de...@lists.debian.org Control: tags -1 pending On 2015-02-13 22:35, Michael Gilbert wrote: package: release-notes severity: important tags: security x-debbugs-cc: pkg-javascript-de...@lists.debian.org Information was added about this problem to the libv8 package [0], but it would be useful to state something in the release notes also. Please see draft attached. Best wishes, Mike [0] http://bugs.debian.org/775715 Hi, I have attached Michael's patch (with Stephan's typo fixes) and included a few minor changes on top of this. The result is attached as 0001-en-issues-Document-lack-of-security-support-for-Node.patch. Review/remarks welcome. Thanks, ~Niels From b4a2d1c275bf871705d53b4861c1dd26f568f2c8 Mon Sep 17 00:00:00 2001 From: nthykier nthykier@313b444b-1b9f-4f58-a734-7bb04f332e8d Date: Mon, 16 Feb 2015 08:07:01 + Subject: [PATCH 1/2] en/issues: Document lack of security support for Node.js Includes typo fixes, mark-up changes and minor word changes from Stephan Beck sb...@mailbox.org and nthykier. Closes: #778348 Written-by: Michael Gilbert mgilb...@debian.org Signed-off-by: Niels Thykier ni...@thykier.net git-svn-id: svn+ssh://svn.debian.org/svn/ddp/manuals/trunk/release-notes@10634 313b444b-1b9f-4f58-a734-7bb04f332e8d --- en/issues.dbk | 22 ++ 1 file changed, 22 insertions(+) diff --git a/en/issues.dbk b/en/issues.dbk index 51a144f..8b232f5 100644 --- a/en/issues.dbk +++ b/en/issues.dbk @@ -45,6 +45,28 @@ role=packagedebian-security-support/systemitem, introduced in packages./para /section +section id=libv8 +titleLack of security support for the ecosystem around libv8 and Node.js/title +para + The Node.js platform is built on top of libv8, which receives a + high volume of security issues but there are currently no + volunteers within the project or the security team sufficiently + interested and willing to spend the large amount of time required + to stem those incoming issues. +/para +para + Unfortunately, this means that systemitem + role=packagelibv8/systemitem, systemitem + role=packagenodejs/systemitem, and the associated node-* + package ecosystem should not currently be used with untrusted + content, for example unsanitized data from the internet. +/para +para + In addition, these packages will not receive any security updates + during the lifetime of the jessie release. +/para +/section + section id=openssh titleOpenSSH server defaults to PermitRootLogin without-password/title !-- Wheezy to Jessie -- -- 2.1.4
Bug#778555: icewm: fails to upgrade from 'sid' - trying to overwrite /usr/share/xsessions/icewm-session.desktop
Package: icewm Version: 1.3.8+githubmod+20150214+d373d98-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 From the attached log (scroll to the bottom...): Preparing to unpack .../icewm_1.3.8+githubmod+20150214+d373d98-1_amd64.deb ... Unpacking icewm (1.3.8+githubmod+20150214+d373d98-1) over (1.3.8-2) ... dpkg: error processing archive /var/cache/apt/archives/icewm_1.3.8+githubmod+20150214+d373d98-1_amd64.deb (--unpack): trying to overwrite '/usr/share/xsessions/icewm-session.desktop', which is also in package icewm-common 1.3.8-2 Preparing to unpack .../icewm-common_1.3.8+githubmod+20150214+d373d98-1_amd64.deb ... Unpacking icewm-common (1.3.8+githubmod+20150214+d373d98-1) over (1.3.8-2) ... Errors were encountered while processing: /var/cache/apt/archives/icewm_1.3.8+githubmod+20150214+d373d98-1_amd64.deb cheers, Andreas icewm_1.3.8+githubmod+20150214+d373d98-1.log.gz Description: application/gzip
Bug#778556: lintian: Cannot process ctwn: debian/patches is not a directory or a symlink
Package: lintian Version: 2.5.30+deb8u3 Severity: normal From lintian.d.o's logs: N: Processing source package ctwm (version 3.7-3.3, arch source) ... W: ctwm source (3.7-3.3) [source]: dh_installmanpages-is-obsolete line 69 W: ctwm source (3.7-3.3) [source]: debhelper-but-no-misc-depends ctwm W: ctwm source (3.7-3.3) [source]: debhelper-compat-file-is-missing W: ctwm source (3.7-3.3) [source]: package-uses-deprecated-debhelper-compat-version 4 Path debian/patches is not a directory or a symlink at /srv/lintian.debian.org/root/checks/patch-systems.pm line 55 internal error: cannot run patch-systems check on package source:ctwm/3.7-3.3 warning: skipping check of source:ctwm/3.7-3.3 ~Niels -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778527: ITP: libfile-mktemp-perl -- Make temporary filename from template
On Mon, 16 Feb 2015 11:30:24 +0100, Raoul Gunnar Borenius wrote: * Package name: libfile-mktemp-perl Version : 1.0.6 Upstream Author : Travis Gummels tra...@gummels.com * URL : https://metacpan.org/release/File-MkTemp/ * License : public-domain Programming Lang: Perl Description : Make temporary filename from template File::MkTemp and File::MkTempO provides functions to create unique strings for use as file/directory names based on an user specified template. The package would be very useful for Nagios/Icinga-Installations using the optional Kerberos-Check-Plugin from http://exchange.nagios.org/directory/Plugins/Security/check_krb5/details This plugin is implemented in Perl and needs File::MkTemp which is not in Debian yet. I'm wondering if adding a probably trivial 2-lines patch to this nagios plugin in order to make it use File::Temp (in perl core) instead of File::MkTemp (last release: 2000) would be a better way forward? Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Rupie Edwards: Ire Feelings (Leggo Skanga) signature.asc Description: Digital Signature
Bug#778561: python3-dvdvideo: backport to Debian Wheezy
Package: python3-dvdvideo Version: 0.20140413 Severity: wishlist Dear Maintainer, I find this package useful and wrote a small patch to backport it to Debian Wheezy. I attach it here, so other people might profit from it. Would it be much of a nuisance to upload the patched package to Debian Backports? Thanks a lot for the good work, Antonio -- System Information: Debian Release: 7.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-0.bpo.4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python3-dvdvideo depends on: ii python3 3.2.3-6 python3-dvdvideo recommends no packages. python3-dvdvideo suggests no packages. -- no debconf information Fixes Python3 import error on Debian Wheezy --- a/dvdvideo/media.py +++ b/dvdvideo/media.py @@ -14,14 +14,17 @@ # You should have received a copy of the GNU General Public License # along with this program. If not, see http://www.gnu.org/licenses/. -import collections.abc +try: +from collections.abc import Mapping +except ImportError: +from collections import Mapping import os import stat from .volume import VmgUdf, VtsUdf -class MediaUdf(collections.abc.Mapping): +class MediaUdf(Mapping): class File: def __init__(self, filename): f = open(filename, 'rb')
Bug#778557: lintian: Errors processing libelmersolver-dbg/6.1.0.svn.5396.dfsg2-4+b1
Package: lintian Version: 2.5.30+deb8u3 Severity: normal From lintian.d.o's logs: N: Processing binary package libelmersolver-dbg (version 6.1.0.svn.5396.dfsg2-4+b1, arch amd64) ... Use of uninitialized value in pattern match (m//) at /srv/lintian.debian.org/root/checks/binaries.pm line 129. Use of uninitialized value in pattern match (m//) at /srv/lintian.debian.org/root/checks/binaries.pm line 129. Use of uninitialized value in pattern match (m//) at /srv/lintian.debian.org/root/checks/binaries.pm line 129. E: libelmersolver-dbg binary (6.1.0.svn.5396.dfsg2-4+b1) [amd64]: binary-with-bad-dynamic-table usr/lib/dreadelf: Error: the dynamic segment offset + size exceeds the size of the file W: libelmersolver-dbg binary (6.1.0.svn.5396.dfsg2-4+b1) [amd64]: debug-file-with-no-debug-symbols usr/lib/debug/usr/lib/elmersolver-6.1/AdvectionDiffusion.so W: libelmersolver-dbg binary (6.1.0.svn.5396.dfsg2-4+b1) [amd64]: debug-file-with-no-debug-symbols usr/lib/debug/usr/lib/elmersolver-6.1/AdvectionReaction.so W: libelmersolver-dbg binary (6.1.0.svn.5396.dfsg2-4+b1) [amd64]: debug-file-with-no-debug-symbols usr/lib/debug/usr/lib/elmersolver-6.1/ArteryOutlet.so W: libelmersolver-dbg binary (6.1.0.svn.5396.dfsg2-4+b1) [amd64]: debug-file-with-no-debug-symbols usr/lib/debug/usr/lib/elmersolver-6.1/ArtificialCompressibility.so W: libelmersolver-dbg binary (6.1.0.svn.5396.dfsg2-4+b1) [amd64]: debug-file-with-no-debug-symbols usr/lib/debug/usr/lib/elmersolver-6.1/DCRComplexSolve.so W: libelmersolver-dbg binary (6.1.0.svn.5396.dfsg2-4+b1) [amd64]: debug-file-with-no-debug-symbols usr/lib/debug/usr/lib/elmersolver-6.1/DFTSolver.so W: libelmersolver-dbg binary (6.1.0.svn.5396.dfsg2-4+b1) [amd64]: debug-file-with-no-debug-symbols usr/lib/debug/usr/lib/elmersolver-6.1/DistanceSolve.so W: libelmersolver-dbg binary (6.1.0.svn.5396.dfsg2-4+b1) [amd64]: debug-file-with-no-debug-symbols usr/lib/debug/usr/lib/elmersolver-6.1/DivergenceSolver.so W: libelmersolver-dbg binary (6.1.0.svn.5396.dfsg2-4+b1) [amd64]: debug-file-with-no-debug-symbols usr/lib/debug/usr/lib/elmersolver-6.1/ElasticSolve.so W: libelmersolver-dbg binary (6.1.0.svn.5396.dfsg2-4+b1) [amd64]: debug-file-with-no-debug-symbols usr/lib/debug/usr/lib/elmersolver-6.1/ElectricForce.so W: libelmersolver-dbg binary (6.1.0.svn.5396.dfsg2-4+b1) [amd64]: debug-file-with-no-debug-symbols usr/lib/debug/usr/lib/elmersolver-6.1/Electrokinetics.so W: libelmersolver-dbg binary (6.1.0.svn.5396.dfsg2-4+b1) [amd64]: debug-file-with-no-debug-symbols usr/lib/debug/usr/lib/elmersolver-6.1/EliminateDirichlet.so W: libelmersolver-dbg binary (6.1.0.svn.5396.dfsg2-4+b1) [amd64]: debug-file-with-no-debug-symbols usr/lib/debug/usr/lib/elmersolver-6.1/EliminatePeriodic.so W: libelmersolver-dbg binary (6.1.0.svn.5396.dfsg2-4+b1) [amd64]: debug-file-with-no-debug-symbols usr/lib/debug/usr/lib/elmersolver-6.1/EnergyRelease.so W: libelmersolver-dbg binary (6.1.0.svn.5396.dfsg2-4+b1) [amd64]: debug-file-with-no-debug-symbols usr/lib/debug/usr/lib/elmersolver-6.1/FDiffusion.so W: libelmersolver-dbg binary (6.1.0.svn.5396.dfsg2-4+b1) [amd64]: debug-file-with-no-debug-symbols usr/lib/debug/usr/lib/elmersolver-6.1/FDiffusion3D.so W: libelmersolver-dbg binary (6.1.0.svn.5396.dfsg2-4+b1) [amd64]: debug-file-with-no-debug-symbols usr/lib/debug/usr/lib/elmersolver-6.1/FilterTimeSeries.so W: libelmersolver-dbg binary (6.1.0.svn.5396.dfsg2-4+b1) [amd64]: debug-file-with-no-debug-symbols usr/lib/debug/usr/lib/elmersolver-6.1/FindOptimum.so W: libelmersolver-dbg binary (6.1.0.svn.5396.dfsg2-4+b1) [amd64]: debug-file-with-no-debug-symbols usr/lib/debug/usr/lib/elmersolver-6.1/FlowSolve.so W: libelmersolver-dbg binary (6.1.0.svn.5396.dfsg2-4+b1) [amd64]: debug-file-with-no-debug-symbols usr/lib/debug/usr/lib/elmersolver-6.1/FluidicForce.so Can't use an undefined value as an ARRAY reference at /srv/lintian.debian.org/root/checks/binaries.pm line 427. internal error: cannot run binaries check on package binary:libelmersolver-dbg/6.1.0.svn.5396.dfsg2-4+b1/amd64 warning: skipping check of binary:libelmersolver-dbg/6.1.0.svn.5396.dfsg2-4+b1/amd64 N: ~Niels -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#718765: apel: (emacs-snapshot)Eager macro-expansion failure: (wrong-type-argument sequencep 769).
Package: apel Version: 10.8-2 Followup-For: Bug #718765 This problem also occurs with wheezy's apel and Emacs 24.4 from backports, and seems to interfere with e.g. debian-bug.el from debian-el for some reason. -- System Information: Debian Release: 7.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages apel depends on: ii emacs23-lucid [emacsen] 23.4+1-4 ih emacs24-lucid [emacsen] 24.4+1-4.1~bpo70+1 apel recommends no packages. apel 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#778269: ITP: python-mkdocs -- Static site generator geared towards building project documentation
On Mon, 16 Feb 2015 09:33:59 +1100, Brian May wrote: Thinking about this, I will call the source python-mkdocs, but the binary package just mkdocs. As I think the names python-mkdocs and python3-mkdocs imply some sort of public and stable python API. That is absolutely right. -- Dmitry Shachnev signature.asc Description: OpenPGP digital signature
Bug#778553: Authentication setup panel broken. Cannot redeclare ldap_escape()
Package: phpbb3 Version: 3.0.12-4 Severity: important Justification: Cannot setup authentication, package becomes unusable in some cases. After a Fresh install of phpbb3 on Jessie, when logged in the administration control panel, when you click on Authentication on the left, you get an empty page. /var/log/apache/error.log says: [Mon Feb 16 16:35:23.885642 2015] [:error] [pid 2720] [client ::1:48216] PHP Fatal error: Cannot redeclare ldap_escape() in /usr/share/phpbb3/www/includes/auth/auth_ldap.php on line 300, referer: http://localhost/phpbb/adm/index.php?sid=b4ad54b7602b01ed8556c8cefa50e92ei=usersmode=overview So it is now impossible to ask phpbb to use apache or ldap authentication backends: Only the default builtin authentication scheme is available. I really need these functions, and it will prevent me to upgrade to Jessie without patching that package, hence the severity. ldap_escape [1] is part of php built in functions since 5.6.0. [1] http://php.net/manual/en/function.ldap-escape.php -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 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) Versions of packages phpbb3 depends on: ii apache2 [httpd]2.4.10-9 ii dbconfig-common1.8.47+nmu3 ii debconf [debconf-2.0] 1.5.55 ii libapache2-mod-php55.6.5+dfsg-1 ii php5 5.6.5+dfsg-1 ii php5-cli 5.6.5+dfsg-1 ii php5-gd5.6.5+dfsg-1 ii php5-mysql 5.6.5+dfsg-1 ii php5-pgsql 5.6.5+dfsg-1 ii postgresql-client-9.4 [postgresql-client] 9.4.1-1 ii sqlite 2.8.17-12 ii ucf3.0030 Versions of packages phpbb3 recommends: ii exim4 4.84-7 ii exim4-daemon-light [mail-transport-agent] 4.84-7 ii php5-imagick 3.2.0~rc1-1 Versions of packages phpbb3 suggests: pn phpbb3-l10n none ii postgresql 9.4+165 -- debconf information: phpbb3/purge: false * phpbb3/httpd: apache2 * phpbb3/pgsql/authmethod-user: password phpbb3/admin-pass-generated: * phpbb3/pgsql/admin-user: postgres phpbb3/mysql/admin-user: root phpbb3/upgrade-error: abort phpbb3/remote/port: phpbb3/admin-pass-mismatch: phpbb3/internal/skip-preseed: false phpbb3/install-error: retry phpbb3/dbconfig-upgrade: true phpbb3/db/basepath: phpbb3/dbconfig-remove: * phpbb3/pgsql/authmethod-admin: ident * phpbb3/pgsql/method: unix socket phpbb3/pgsql/no-empty-passwords: phpbb3/admin-pass-ask: phpbb3/missing-db-package-error: abort phpbb3/passwords-do-not-match: phpbb3/remove-error: abort phpbb3/dbconfig-reinstall: false * phpbb3/db/app-user: phpbb3 phpbb3/admin-pass-requirements: phpbb3/internal/reconfiguring: false phpbb3/remote/host: phpbb3/pgsql/manualconf: phpbb3/database-type: pgsql phpbb3/upgrade-backup: true phpbb3/mysql/method: unix socket * phpbb3/dbconfig-install: true phpbb3/pgsql/changeconf: false * phpbb3/db/dbname: phpbb3 phpbb3/remote/newhost: signature.asc Description: OpenPGP digital signature
Bug#778559: gdm3: Login temporarily unavailable if the previous user failed login
Package: gdm3 Version: 3.14.1-3 Severity: important Dear Maintainer, * What led up to the situation? I was implementing restrictions on login times for my users using pam_time.so First, I enabled the pam_time.so by appending the following to /etc/pam.d/gdm-password account required pam_time.so Second, I added the following line to /etc/security/time.conf *;*;demo;Su1130-2130 * What was the outcome of this action? The user 'demo' can login during the time specified, but during the times not specified, login fails almost instantly, with the message: Sorry, that didn't work. Please try again. This is the expected outcome. However, at this point, I then clicked on Cancel to bring me back to the user list. This worked as expected and I clicked on my user to login, but it just brought me to a blank screen as if the login widget were still loading. After about 10 to 30 seconds, I saw the login widget appear for brief moment with a message under the password box. I was unable to read the message because it disappeared too quickly. I was then taken back to the user list where I clicked on 'laverne' again and was able to log in normally. * What outcome did you expect instead? I expected that, after failure, I would be able to choose any user and log in normally. * Reproducibility It seems like I can reproduce the bug with the following steps. 1) Chose any user from the GDM user list 2) Make the login fail (by using an incorrect password) 3) Click Cancel or use the ESC key to return to the user list. 4) Chose any user. (Including the one that just failed) -Laverne -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 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 gdm3 depends on: ii accountsservice 0.6.37-3+b1 ii adduser 3.113+nmu3 ii dconf-cli 0.22.0-1 ii dconf-gsettings-backend 0.22.0-1 ii debconf [debconf-2.0] 1.5.55 ii gir1.2-gdm3 3.14.1-3 ii gnome-session [x-session-manager] 3.14.0-2 ii gnome-session-bin 3.14.0-2 ii gnome-settings-daemon 3.14.2-2 ii gnome-shell 3.14.2-3+b1 ii gnome-terminal [x-terminal-emulator] 3.14.1-1 ii gsettings-desktop-schemas 3.14.1-1 ii libaccountsservice0 0.6.37-3+b1 ii libaudit1 1:2.4-1+b1 ii libc6 2.19-15 ii libcanberra-gtk3-00.30-2.1 ii libcanberra0 0.30-2.1 ii libgdk-pixbuf2.0-02.31.1-2+b1 ii libgdm1 3.14.1-3 ii libglib2.0-0 2.42.1-1 ii libglib2.0-bin2.42.1-1 ii libgtk-3-03.14.5-1 ii libpam-modules1.1.8-3.1 ii libpam-runtime1.1.8-3.1 ii libpam-systemd215-12 ii libpam0g 1.1.8-3.1 ii librsvg2-common 2.40.5-1 ii libselinux1 2.3-2 ii libsystemd0 215-12 ii libwrap0 7.6.q-25 ii libx11-6 2:1.6.2-3 ii libxau6 1:1.0.8-1 ii libxdmcp6 1:1.1.1-1+b1 ii libxrandr22:1.4.2-1+b1 ii lsb-base 4.1+Debian13+nmu1 ii metacity [x-window-manager] 1:3.14.3-1 ii mutter [x-window-manager] 3.14.2-1 ii policykit-1 0.105-8 ii ucf 3.0030 ii x11-common1:7.7+7 ii x11-xserver-utils 7.7+3+b1 ii xterm [x-terminal-emulator] 312-1 Versions of packages gdm3 recommends: ii at-spi2-core 2.14.0-1 ii desktop-base 8.0.2 ii gnome-icon-theme 3.12.0-1 ii gnome-icon-theme-symbolic 3.12.0-1 ii x11-xkb-utils 7.7+1 ii xserver-xephyr 2:1.16.4-1 ii xserver-xorg 1:7.7+7 ii zenity 3.14.0-1 Versions of packages gdm3 suggests: ii gnome-orca3.14.0-3 ii libpam-gnome-keyring 3.14.0-1+b1 -- Configuration Files: /etc/gdm3/PreSession/Default changed: PATH=/usr/bin:$PATH synclient RTCornerButton=2 /etc/gdm3/daemon.conf changed: [daemon] [security] [xdmcp] [greeter] IncludeAll = true [chooser] [debug] /etc/pam.d/gdm-password changed: authrequisite pam_nologin.so authrequired
Bug#755722: systemd must sync systemclock to RTC on shutdown
Martin Pitt [2015-02-16 16:41 +0100]: For master (i. e. testing/jessie), I prepared and tested the attached patch. Slightly refined version 2 of the patch: renamed to hwclock-save.service to not get mingled with util-linux' hwclock.service. Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) From a32678de07b3a89028e54d5bceff5479ad1169c3 Mon Sep 17 00:00:00 2001 From: Martin Pitt martin.p...@ubuntu.com Date: Mon, 16 Feb 2015 16:14:23 +0100 Subject: [PATCH] Add hwclock-save.service to sync the system clock to the hardware clock on shutdown This provides monotonic time for reboots. Thanks to Stefan Fritsch for the initial unit. Note: this is a hack for jessie; the next Debian release will enable timesyncd by default. Closes: #755722 --- debian/changelog | 9 + debian/extra/hwclock-save.service | 14 ++ debian/rules | 2 +- debian/systemd.postinst | 4 4 files changed, 28 insertions(+), 1 deletion(-) create mode 100644 debian/extra/hwclock-save.service diff --git a/debian/changelog b/debian/changelog index 6d81277..1493538 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,12 @@ +systemd (215-13) UNRELEASED; urgency=medium + + * Add hwclock-save.service to sync the system clock to the hardware clock on +shutdown, to provide monotonic time for reboots. (Note: this is a hack for +jessie; the next Debian release will enable timesyncd by default). +(Closes: #755722) + + -- Martin Pitt mp...@debian.org Mon, 16 Feb 2015 16:11:12 +0100 + systemd (215-12) unstable; urgency=medium [ Martin Pitt ] diff --git a/debian/extra/hwclock-save.service b/debian/extra/hwclock-save.service new file mode 100644 index 000..1e0f99a --- /dev/null +++ b/debian/extra/hwclock-save.service @@ -0,0 +1,14 @@ +[Unit] +Description=Synchronise Hardware Clock to System Clock +DefaultDependencies=no +Before=shutdown.target +ConditionFileIsExecutable=!/usr/sbin/ntpd +ConditionFileIsExecutable=!/usr/sbin/openntpd +ConditionFileIsExecutable=!/usr/sbin/chrony + +[Service] +Type=oneshot +ExecStart=/sbin/hwclock -D --systohc + +[Install] +WantedBy=reboot.target halt.target poweroff.target diff --git a/debian/rules b/debian/rules index 4f79678..92bd007 100755 --- a/debian/rules +++ b/debian/rules @@ -183,7 +183,7 @@ override_dh_install: debian/systemd/lib/lsb/init-functions.d/40-systemd install --mode=644 debian/tmpfiles.d/debian.conf \ debian/systemd/usr/lib/tmpfiles.d/ - install --mode=644 debian/debian-fixup.service debian/ifup@.service debian/extra/getty-static.service \ + install --mode=644 debian/debian-fixup.service debian/ifup@.service debian/extra/getty-static.service debian/extra/hwclock-save.service \ debian/systemd/lib/systemd/system/ install -D --mode=644 debian/extra/network-pre.conf \ debian/systemd/lib/systemd/system/networking.service.d/network-pre.conf diff --git a/debian/systemd.postinst b/debian/systemd.postinst index 488df32..de92c57 100644 --- a/debian/systemd.postinst +++ b/debian/systemd.postinst @@ -131,6 +131,10 @@ if dpkg --compare-versions $2 lt 214-1; then systemctl enable remote-fs.target || true fi +if dpkg --compare-versions $2 lt 215-13; then +systemctl enable hwclock-save.service || true +fi + # Re-run systemctl enable for any service that was enabled when preinst was run. if dpkg --compare-versions $2 ge 204; then while read UNIT ; do -- 2.1.4 signature.asc Description: Digital signature
Bug#778554: unblock: systemd/215-12
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock systemd 215-12 hit unstable three days ago with some RC/important/safe So far there have been no regression reports. At the time of this writing there are now no RC bugs left \o/ I attach the full debdiff between 215-11 and -12, but as usual I also link to the individual commits on anonscm. Unfortunately the latter are a bit noisy, as the implementation of the fixes was discussed several times and changed a bit. Note that there are zero changes for udev and hence the udebs (for d-i). Annotated changelog: | systemd (215-12) unstable; urgency=medium | | [ Martin Pitt ] | * debian/udev.README.Debian: Trim the parts which are obsolete, wrong, or | described in manpages. Only keep the Debian specific bits. | (Part of #776546) http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=a76b454 | * Actually install udev's README.Debian when building for Debian. | (Closes: #776546) http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=d26405c8 Documentation cleanup. Note that this was requested/pre-approved by Niels. | * Only start logind if dbus is installed. This fixes the noisy startup | failure in environments without dbus such as LXC containers or servers. | (part of #772700) http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=a7d7679 http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=0d601f8 (update/cleanup) | * Add getty-static.service unit which starts getty@.service on tty 2 to 6 if | dbus is not installed, and hence logind cannot auto-start them on demand. | (Closes: #772700) http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=c4b5782f0 http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=965ef72 (cleanup of the previous two commits) RC bug (with 3 duplicates). This restores VT functionality on systems without dbus (i. e. mainly servers) as it is under sysvinit, and quiesces logind failures there. | * Add unit-config autopkgtest to check systemd unit/sysv init enabling and | disabling via systemctl. This avoids bugs like #777613 (did not affect | unstable). http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=ec551e56 I used this to verify that 215 was not affected. I'd like to keep this in master, just to have it available for post-release bug fixes/verification. | * cgroup: Don't trim cgroup trees created by someone else, just the ones | that systemd itself created. This avoids cleaning up empty cgroups from | e.g. LXC. (Closes: #777601) http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=255ae60 http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=59d9202 (followup fix due to git pilot error on my side, sorry) RC bug. This looks fairly intrusive (not at all in patch size, that's just a two-liner; but in effect), but as long as there is more than just systemd writing to /sys/fs/cgroups this errs on the safe side: now systemd will never cleanup empty cgroups that it didn't create by itself (realized_mask); before it cleaned up all controllers which are supported by the kernel (cgroup_supported). | * boot-and-services autopkgtest: Add CgroupsTest to check cgroup | creation/cleanup behaviour. This reproduces #777601 and verifies the fix | for it. http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=f1a42bae tests == ♥ :-) | * rules: Fix by-path of mmc RPMB partitions and don't blkid them. Avoids | kernel buffer I/O errors and timeouts. (LP: #1333140) http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=21c55fb This is https://launchpad.net/bugs/1333140 . Not quite RC, but a trivial patch which just blacklists mmcblk*-rpmb devices from getting touched by udev rules; they are rather mimosic and can't really opened or detected with blkid and other tools. | * Document systemctl --failed option. (Closes: #767267) http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=8b3d324 Documentation (manpage) only, and an useful option. | [ Michael Biebl ] | * core: Don't fail to run services in --user instances if $HOME is missing. | (Closes: #759320) http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=e0b3ce3b Not release critical, but causes annoyingly long delays during shutdown, and quite a simple fix. | [ Didier Roche ] | * default-display-manager-generator: Avoid unnecessary /dev/null symlink and | warning if there is no display-manager.service unit. http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=496110f3a This fixes a corner case to avoid a useless warning, and this is a simple patch. This whole logic is tested by debian/tests/display-managers which which covers all scenarios we ran into so far, and it's still passing fine. Thanks for considering! Please let
Bug#778553: Authentication setup panel broken. Cannot redeclare ldap_escape()
Control: tags -1 + fixed-upstream Control: forwarded -1 https://github.com/phpbb/phpbb/pull/2989 Upstream patch is available here: https://github.com/phpbb/phpbb/pull/2989/files signature.asc Description: OpenPGP digital signature
Bug#778404: Henry Spencer regular expressions (regex) library contains a heap overflow vulnerability
On 16/02/15 17:19, Moritz Muehlenhoff wrote: severity 778404 minor thanks On Sat, Feb 14, 2015 at 03:39:19PM +0100, Luciano Bello wrote: Package: ptlib Severity: important Tags: security patch The security team received a report from the CERT Coordination Center that the Henry Spencer regular expressions (regex) library contains a heap overflow vulnerability. It looks like this package includes the affected code at that's the reason of this bug report. The configure script picks the glibc regex code, so this doesn't affect the Debian binary packages. Thank you for the analysis. It would still be useful to report this upstream, so that they update the local regex code (it could be that the local one is used when building with a libc other than glibc) I will do it, I have commit access. -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777170: [pkg-wpa-devel] Bug#777170: wpasupplicant: lots of CTRL-EVENT-SIGNAL-CHANGE messages in syslog and couldn't connect to wireless network
On Thu, Feb 12, 2015 at 10:36:35PM +, Julian Gilbey wrote: I've just found out that there were general problems with the wireless in the building which may be part of the cause of this problem, so I will check next week to see if things have improved (they've replaced the wireless network hardware). [...] So clearly something is amiss, but it might be network-related. I'll update next week when I'm able to check again with the new network setup. Well, I tried today, and it seems that it is almost certainly system-related: when I rebooted the machine into Mac OSX (Yosemite), it worked perfectly, yet in Linux, it is giving these messages repeatedly and dropping the connection. Hmmm. Julian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778560: ITP: python-kmip -- Key Management Interoperability Protocol
Package: wnpp Severity: wishlist Owner: Thomas Goirand z...@debian.org * Package name: python-kmip Version : 0.2.0 Upstream Author : Peter Hamilton peter.hamil...@jhuapl.edu * URL : https://github.com/OpenKMIP/PyKMIP * License : Apache-2.0 Programming Lang: Python Description : Key Management Interoperability Protocol PyKMIP is a Python implementation of the Key Management Interoperability Protocol (KMIP) specification, supporting version 1.1 of the KMIP standard. The KMIP standard is governed by the Organization for the Advancement of Structured Information Standards (OASIS) and specifies a client/server-based protocol to perform key, certificate, and secret object management, including storage and maintenance operations. . The PyKMIP library currently provides a KMIP client and server supporting the following operations for the KMIP SymmetricKey managed object: * Create * Register * Get * Destroy . Note that KMIP specifies profiles that tailor the standard to specific use cases. The KMIP Profile Support section includes several profiles that need to be developed for PyKMIP to fully support symmetric key storage and generation capabilities. A list of operations necessary for these profiles is included. . The PyKMIP software-based KMIP server is intended for use only in testing and demonstration environments. Note that the PyKMIP server is NOT intended to be a substitute for secured, hardware-based KMIP appliances. The PyKMIP client should be used for operational purposes only with a hardware-based KMIP server. The development of the PyKMIP client and server should take place in parallel to facilitate testing of each operation as it is developed. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#606138: Allow use of tomcat7-user package with solr-tomcat
tags 606138 + fixed pending signature.asc Description: OpenPGP digital signature
Bug#778404: Henry Spencer regular expressions (regex) library contains a heap overflow vulnerability
severity 778404 minor thanks On Sat, Feb 14, 2015 at 03:39:19PM +0100, Luciano Bello wrote: Package: ptlib Severity: important Tags: security patch The security team received a report from the CERT Coordination Center that the Henry Spencer regular expressions (regex) library contains a heap overflow vulnerability. It looks like this package includes the affected code at that's the reason of this bug report. The configure script picks the glibc regex code, so this doesn't affect the Debian binary packages. It would still be useful to report this upstream, so that they update the local regex code (it could be that the local one is used when building with a libc other than glibc) Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778336: pastebinit: fails in the default configuration
This could be fixed by fixing #760341 so that pastebinit defaults to paste.debian.net The root cause of that is lsb-release doesn't support Python 3, breaking the distro detection. The attached patch works around that by using platform to detect the distribution instead. Thanks, -- Andrew Starr-Bochicchio Ubuntu Developer https://launchpad.net/~andrewsomething Debian Developer http://qa.debian.org/developer.php?login=asb PGP/GPG Key ID: D53FDCB1 From c8d33415abf8d07b3b2bcb41bb088a03b882a7cb Mon Sep 17 00:00:00 2001 From: Andrew Starr-Bochicchio a...@debian.org Date: Mon, 16 Feb 2015 12:45:05 -0500 Subject: [PATCH] detect_distro_with_python3.patch: Use platform instead of lsb_release to detect the distro as lsb_release is not available under Python 3 (Closes: #760341). pastebinit will now default to using paste.debian.net on Debian (Closes: #778336). --- debian/changelog| 11 +++ debian/patches/detect_distro_with_python3.patch | 15 +++ debian/patches/series | 1 + 3 files changed, 27 insertions(+) create mode 100644 debian/patches/detect_distro_with_python3.patch diff --git a/debian/changelog b/debian/changelog index 7de6407..c2d3758 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,14 @@ +pastebinit (1.4-3.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * detect_distro_with_python3.patch: Use platform instead of +lsb_release to detect the distro as lsb_release is not +available under Python 3 (Closes: #760341). pastebinit +will now default to using paste.debian.net on Debian +(Closes: #778336). + + -- Andrew Starr-Bochicchio a...@debian.org Mon, 16 Feb 2015 12:40:55 -0500 + pastebinit (1.4-3) unstable; urgency=low * bump debhelper to version 9 diff --git a/debian/patches/detect_distro_with_python3.patch b/debian/patches/detect_distro_with_python3.patch new file mode 100644 index 000..e0737c3 --- /dev/null +++ b/debian/patches/detect_distro_with_python3.patch @@ -0,0 +1,15 @@ +Index: pastebinit/pastebinit +=== +--- pastebinit.orig/pastebinit 2015-02-16 12:37:04.434846203 -0500 pastebinit/pastebinit 2015-02-16 12:39:22.709104460 -0500 +@@ -37,8 +37,8 @@ + + # Now try to override it with a distributor pastebin + try: +-import lsb_release +-release = lsb_release.get_distro_information()['ID'].lower() ++import platform ++release = platform.linux_distribution()[0].lower() + if release == 'debian': + defaultPB = http://paste.debian.net; + elif release == 'fedora': diff --git a/debian/patches/series b/debian/patches/series index 986704d..b17e68f 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -1,2 +1,3 @@ upstream-r205_r201.patch increase_timeout.patch +detect_distro_with_python3.patch -- 2.1.0
Bug#776172: vlc: crash (segmentation fault) on a webm file
On 2015-02-15 00:46:46, Vincent Lefevre wrote: On 2015-02-14 16:20:39 +0100, Sebastian Ramacher wrote: I can't reproduce it. I've tried to play the URL directly with vlc, downloaded it with youtube-dl and downloaded the webm. It never crashed on normal speed or higher speed. I could reproduce it by setting the speed to 3x and the start time position to 00:00:06, but it doesn't always crash. It seems that the VLC behavior is not deterministic! I could also reproduce the crash by resetting to position to 00:00:00 (or clicking on stop/play), still at speed 3x. The crash often occurs near 1:15. But it also occurred just after I clicked on stop/play (i.e. just at the beginning of the file). Another test: I start vlc Nosferatu*.webm, then select the 3x speed via a click on the speed area at the bottom, then do a sequence of stop/play until a crash. The first 3 times, VLC crashed immediately after a play in the first 5 iterations. The 4th time, I did a sequence of several dozens of stop/play, but couldn't make it crash. The 5th time, VLC crashed at the 7th iteration. The 6th time, VLC crashed at the 6th iteration. Nope, cannot get it to crash. So without a minimal sample that causes the clash, Can VLC can extract a sample that caused the crash? I am not aware of such a feature. the traceback with -dbg packages installed and a verbose vlc log, there is not much we can do. Here's the full backtrace with the debugging symbols. The crash always occurs in the same function. Please also include the output of vlc -vvv. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#778565: 215-12 does not set correct rights for hidraw devices (and others) anymore
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package: udev Version: 215-12 Severity: important After updating from 215-11 to 215-12, usb hidraw devices stopped to be accessable by plugdev group after reboot. I only checked that rights as this ist the most important for me but had also some other error messages after the reboot. So the system is only partial working after that update. - -- Package-specific info: - -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (800, 'unstable'), (110, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.18.6 (SMP w/8 CPU cores) Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) (ignored: LC_ALL set to de_DE) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages udev depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.55 ii libacl12.2.52-2 ii libblkid1 2.25.2-5 ii libc6 2.19-15 ii libkmod2 18-3 ii libselinux12.3-2 ii libudev1 215-12 ii lsb-base 4.1+Debian13+nmu1 ii procps 2:3.3.9-8 ii util-linux 2.25.2-5 udev recommends no packages. udev suggests no packages. - -- debconf information: udev/new_kernel_needed: false udev/title/upgrade: udev/sysfs_deprecated_incompatibility: udev/reboot_needed: - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen kl...@ethgen.de Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQGcBAEBCgAGBQJU4jwEAAoJEKZ8CrGAGfasgygL/1ROlK85k13ZlZZzeME1KRTK YwGlbEhZB1svyoSjoGLHXg6mRKSW01Ogomen/ozFIfZrTsoXsoMUfI3Dvm2vef2g DyWkzwwq3fPtQFBaL7EgHKTqYSk/IjEPRN1hTIvqBoAknkDijrNIrqtqEgaNe70l oR2RyZhYT4mjG9r0RFhqpfBgwQF3z+RpPofAj7XcBX1LNs0tGO06ACz4+tpN+yOX 6RrSAVUpj4bMN+WUqWM1b37rDX6Wtq0q3nplDZ1r4Y85tb/tqqe5+BmQbwd1p2wl JCy5nGXRXGtXlhullR+ZquQefkbLBRJJjkEOSUAPUCbJai2ZRWcaGgmT9aeYLBmC bdgW7X19aPpZ8Iyga5xtiq4V1f0weiD4Z8jvZgKWGTduyeIE0cqPnTVqbjARwKU8 ijquB2YVr//70QgVJ9LobUYOxfrfyqJoZQuyjCSuJIVR6dk81UTQ9llfmt0BJYCz 42khGJByYFOPp7v+TEDKBwDGkQ2GvwLrr9Rf8mgvIw== =ktTJ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778487: s3ql: Needs python-dugong = 3.4
Hi Nikolaus,
Am Mon, 16 Feb 2015 09:42:57 -0800
schrieb Nikolaus Rath nikol...@rath.org:
So please tighten the dependencies of s3ql 2.13 to require
python3-dugong = 3.4
At least according to
https://packages.debian.org/source/unstable/s3ql, this is exactly
what the dependency is.
That shows the dependencies of the s3ql source package (I guess that's
build dependencies, but I'm not sure about that). The dependencies of
the s3ql binary packages are found at
https://packages.debian.org/sid/s3ql
and as you can see, there is no version specified for python3-dugong. I
think the ${python3:Depends} does not expand to versioned dependencies
by default. The dh_python3 man page says:
If the pydist file contains PEP386 flag or set of (uscan like) rules,
dh_python3 will make the depedency versioned (version requirements are
ignored by default).
So I guess dh_python3 needs a pydist file or a py3dist-overrides file.
Adding debian/s3ql.pydist with the contents
dugong python3-dugong; PEP386
did not do the trick for me, maybe I'm reading the manpage wrong.
However; I couldn't test building in a clean environment because
building s3ql failed for me (with and without the pydist file) in an
unstable pbuilder. I still think a proper pydist file should work.
Cheers,
Mika
--
pgpjah7f9TaT9.pgp
Description: Digitale Signatur von OpenPGP
Bug#778557: lintian: Errors processing libelmersolver-dbg/6.1.0.svn.5396.dfsg2-4+b1
On 2015-02-16 17:32, Niels Thykier wrote:
Package: lintian
Version: 2.5.30+deb8u3
Severity: normal
From lintian.d.o's logs:
N: Processing binary package libelmersolver-dbg (version
6.1.0.svn.5396.dfsg2-4+b1, arch amd64) ...
Use of uninitialized value in pattern match (m//) at
/srv/lintian.debian.org/root/checks/binaries.pm line 129.
Use of uninitialized value in pattern match (m//) at
/srv/lintian.debian.org/root/checks/binaries.pm line 129.
Use of uninitialized value in pattern match (m//) at
/srv/lintian.debian.org/root/checks/binaries.pm line 129.
E: libelmersolver-dbg binary (6.1.0.svn.5396.dfsg2-4+b1) [amd64]:
binary-with-bad-dynamic-table usr/lib/dreadelf: Error: the dynamic segment
offset + size exceeds the size of the file
[...]
Can't use an undefined value as an ARRAY reference at
/srv/lintian.debian.org/root/checks/binaries.pm line 427.
internal error: cannot run binaries check on package
binary:libelmersolver-dbg/6.1.0.svn.5396.dfsg2-4+b1/amd64
warning: skipping check of
binary:libelmersolver-dbg/6.1.0.svn.5396.dfsg2-4+b1/amd64
N:
~Niels
More info:
* Only reproducible on a stable system - but it is reproducible every
time.
* It seems to be caused by readelf truncating its own output with a
message from stderr.
I managed to extract the following extra message:
/usr/bin/head: cannot open
`usr/lib/debug/usr/lib/elmersolver-6.1/FluxSolver.readelf: Error: the
dynamic segment offset + size exceeds the size of the file' for reading:
No such file or directory
/usr/bin/head: cannot open `usr/lib/dreadelf: Error: the dynamic segment
offset + size exceeds the size of the file' for reading: No such file or
directory
/usr/bin/head: cannot open `usr/lib/debug/usr/lreadelf: Error: the
dynamic segment offset + size exceeds the size of the file' for reading:
No such file or directory
Which seems to suggest that helpers/coll/objdump-info-helper believes
that the package contains 3 files *literally* ending with:
part-of-name.readelf: Error: the dynamic segment offset + size
exceeds the size of the file
Note that part-of-name is truncated, so we cannot just strip off the
error message. The code triggering the above is:
while (my $line = $readelf) {
chomp $line;
if ($line =~ m/^File: (.+)$/) {
my $file = $1;
finish_file();
$bin = $file;
print Filename: $bin\n;
if (
spawn(
undef, ['head', $bin],
'|', ['grep', '-q', 'packed.*with.*UPX'])
) {
print UPX: yes\n;
}
[...]
Which is why I suspect readelf for truncating its own output.
Thanks,
~Niels
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778568: unblock: node-findit2/2.2.3-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package node-findit2 The package build-depends on node-tap, a buggy package. However, this dependency is strictly optional and is only used to run upstream tests. Further, there are many examples of Debian JavaScript packages which have tests disabled. diff -Nru node-findit2-2.2.3/debian/changelog node-findit2-2.2.3/debian/changelog --- node-findit2-2.2.3/debian/changelog 2014-10-20 00:05:27.0 + +++ node-findit2-2.2.3/debian/changelog 2015-02-16 19:25:16.0 + @@ -1,3 +1,9 @@ +node-findit2 (2.2.3-2) unstable; urgency=medium + + * remove build dependency on buggy dependency: node-tap + + -- Andrew Kelley superjo...@gmail.com Mon, 16 Feb 2015 19:25:08 + + node-findit2 (2.2.3-1) unstable; urgency=medium * Initial release (Closes: #765772) diff -Nru node-findit2-2.2.3/debian/control node-findit2-2.2.3/debian/control --- node-findit2-2.2.3/debian/control 2014-10-20 00:03:35.0 + +++ node-findit2-2.2.3/debian/control 2015-02-16 19:23:44.0 + @@ -6,7 +6,6 @@ Build-Depends: debhelper (= 8) , dh-buildinfo - , node-tap , nodejs Standards-Version: 3.9.6 Homepage: https://github.com/andrewrk/node-findit diff -Nru node-findit2-2.2.3/debian/rules node-findit2-2.2.3/debian/rules --- node-findit2-2.2.3/debian/rules 2014-10-20 00:03:21.0 + +++ node-findit2-2.2.3/debian/rules 2015-02-16 19:24:00.0 + @@ -9,8 +9,6 @@ #override_dh_auto_build: -override_dh_auto_test: - tap test/*.js unblock node-findit2/2.2.3-1 -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16-2-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#212814: Kiemelt akció
2 felnőtt + 4 év alatti gyermek részére 2 éjszakára félpanzióval, római ízvilággal, sok finomsággal vár benneteket a Kék Duna Wellness Hotel! Kék Duna Wellness Hotel - Ráckeve Eredeti ár: 61.700 Ft Akciós ár: 41.500 Ft Foglaláshoz fizetendő: 5.600 Ft 33% kedvezmény Kupon Tartalma: 3 nap/2 éjszaka szállás 2 felnőtt és egy 4 év alatti gyermek részére Kis-Dunára néző standard kétágyas szobában a Kék Duna Wellness Hotelben antik Római wellness részlegünk használata szauna programok – képzett szauna mesterünkkel, mely a test és a lélek harmonizálására szolgál aerobic és vízi torna azoknak, akik fittebbnek és egészségesebbnek szeretnék magukat érezni Római ízvilág bemutató és kóstoló az ókori római konyha ízvilágában Dráva Hotel - Harkány (3 nap / 2 éjszaka - 2 fő) Eredeti ár: 66.360 Ft Akciós ár: 49.900 Ft Foglaláskor fizetendő: 7.485 Ft 25% NAIH-79431/2014. Ha nem Te adtad meg az emailcímedet, vagy nem szeretnél a jövőben értesülni a legjobb ajánlatokról, ide kattinva leiratkozhatsz, vagy írj levelet az i...@wellness7.eu címre
Bug#777540: The libhtp SONAME mismatch *is* a policy violation.
On Fri, Feb 13, 2015 at 22:13:21 +0100, Hilko Bengen wrote: control: severity -1 grave control: block 772551 by -1 control: tag -1 patch In the current state of the libhtp source package, every new upstream release of changes the SONAME and thus requires that reverse dependencies (currently only suricata) are rebuilt. As long as the name of the binary package stays the same, eventual breakage is guaranteed, see #772551. The current state defeats the purpose of shared libraries and violates section 8.1 (Run-time shared libraries) of the Debian Policy Manual. I see three possible solutions: 1. Override upstream's decision to change the SONAME with every release. I am not entirelysure how stable libhtp's API/ABI should be considered -- looking at changes and deciding on compatibility issues making those decisions would certainly put a burden on the maintainer in the future (although the .symbols mechanism helps for obvious cases such as removed APIs.) I am attaching a patch to drop the -release parameter from the libtool call, libhtp.so.1.0.0 (instead of libhtp-0.5.15.so.1.0.0) is generated. The .symbols file would need to be updated to reflect that change, too, of course. 2. Since suricata is the only reverse dependency of libhtp and contains a copy of libhtp within its source tarball, so we could drop the libhtp package altogether and use that embedded copy instead, at least for the jessie release. 3. Change the binary package name to reflect the SONAME -- for instance libhtp-0.5.15. I believe that we are too late in the freeze to be adding new binary package names. For jessie, 2 sounds like the best way to go IMO. Cheers, Julien signature.asc Description: Digital signature
Bug#778570: sbuild: ignore .buildinfo files in .changes
Package: sbuild
Version: 0.65.0-1
Severity: wishlist
Tags: patch
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Thanks for maintaining sbuild!
When using dpkg from the reproducible builds toolchain, it generates a
.buildinfo file in the .changes file:
https://wiki.debian.org/ReproducibleBuilds/ExperimentalToolchain#dpkg
When .buildinfo files are present in the .changes, sbuild treats it as
an attempted build, rather than a successful build; it appears to be
treating the .buildinfo file as a .deb and tries to unpack it:
ltsp_5.5.4-4~20150213~1_amd64.buildinfo
───
dpkg-deb: error:
`/«CHROOT»/«BUILDDIR»/ltsp_5.5.4-4~20150213~1_amd64.buildinfo' is not a debian
format archive
dpkg-deb: error:
`/«CHROOT»/«BUILDDIR»/ltsp_5.5.4-4~20150213~1_amd64.buildinfo' is not a debian
format archive
The following patch should fix/workaround this:
From 8468411099b8ec28641df015742784b63b98b573 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian vagr...@debian.org
Date: Fri, 13 Feb 2015 23:51:11 -0800
Subject: [PATCH 2/2] Ignore .buildinfo files produced by reproducible builds.
---
lib/Sbuild/Build.pm | 2 ++
1 file changed, 2 insertions(+)
diff --git a/lib/Sbuild/Build.pm b/lib/Sbuild/Build.pm
index 5149a8a..f15e94a 100644
--- a/lib/Sbuild/Build.pm
+++ b/lib/Sbuild/Build.pm
@@ -1768,6 +1768,8 @@ sub build {
foreach (@debcfiles) {
my $deb = $build_dir/$_;
next if $deb !~ /(\Q$host_arch\E|all)\.[\w\d.-]*$/;
+ # ignore .buildinfo files produced by reproducible builds.
+ next if $deb =~ /\.*buildinfo$/;
$self-log_subsubsection($_);
if (!open( PIPE, dpkg --info $deb 21 | )) {
--
2.1.4
live well,
vagrant
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (500, 'testing'), (120, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages sbuild depends on:
ii adduser 3.113+nmu3
ii apt-utils 1.0.9.6
ii libsbuild-perl 0.65.0-1
ii perl5.20.1-5
ii perl-modules5.20.1-5
Versions of packages sbuild recommends:
ii debootstrap 1.0.66
ii fakeroot 1.20.2-1
Versions of packages sbuild suggests:
pn deborphan none
ii wget 1.16-1
-- no debconf information
signature.asc
Description: PGP signature
Bug#777694: ITA: icu -- Development utilities for International Components for Unicode
On Mon, Feb 16, 2015 at 12:12:02AM +0100, László Böszörményi (GCS) wrote: Hi all, On Thu, Feb 12, 2015 at 4:50 PM, j...@debian.org wrote: It would be great if you (or any co-maintainer) would initially take care of the open icu security issues in jessie/sid (with a minimal upload to sid + unblock request to the release team): https://security-tracker.debian.org/tracker/CVE-2014-9654 https://security-tracker.debian.org/tracker/CVE-2014-7940 https://security-tracker.debian.org/tracker/CVE-2014-7926 https://security-tracker.debian.org/tracker/CVE-2014-7923 https://security-tracker.debian.org/tracker/CVE-2014-6585 I'm ready with the first iteration[1]. I've backported all security fixes. Anyone would like to, please test it. If someone has exploits, I'm looking for reports how those work on this Debian package version. I noticed that Mike has been working on a NMU as well, adding him to CC. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778406: Henry Spencer regular expressions (regex) library contains a heap overflow vulnerability
Control: tags -1 fixed-upstream Hi, On 16.02.2015 13:30, Sebastian Andrzej Siewior wrote: Good. I will wait what upstream says. Maybe they drop usage of the library since they check for PCRE since two releases or so. The patch got applied upstream so this bug will be fixed with the next upstream version 0.98.7. 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#778507: clamav: aptitude error: /var/lib/dpkg/info/clamav-daemon.postinst: cannot create : Directory nonexistent
Control: tags -1 pending Hi Andy, On 16.02.2015 01:07, Andy Dorman wrote: Testing install of clamav reports the subject error with the postinst script. The problem is really simple, line 626 of clamav-daemon.postinst has a typo: [ -n $PidFile ] echo PidFile $PidFile $DEBCONFILE should actually be [ -n $PidFile ] echo PidFile $PidFile $DEBCONFFILE Thanks for this patch, which I just applied. (It was actually a copy and paste error, because clamav-freshclam.postinst uses/used DEBCONFILE...) Thank you for your excellent work on packaging ClamAV. You're welcome. 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#768352: gsasl: Does not support GSSAPI.
Any way I can help move this along? -- Morgan Hamill -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778388: ccache: scanner confused by comment signs in strings
Yes, a reduced testcase would be much appreciated. I don't have access to https://codereview.qt-project.org/105039 and I wouldn't know what to do anyway. :-) (BTW: You did clear the cache before you compiled the changed source code, right? Otherwise a cache hit is expected from the previous experiments, of course. Just checking.) -- Joel On 16 February 2015 at 20:37, Oswald Buddenhagen oswald.buddenha...@gmx.de wrote: this is pretty incredible ... i can't reproduce it with your testcase, either. but when i run the actual build with CCACHE_LOGFILE=/dev/stdout, it totally confirms that the issue is real: [2015-02-16T20:25:26.035076 20314] === CCACHE STARTED = [2015-02-16T20:25:26.035222 20314] Command line: /usr/bin/ccache /usr/bin/g++ -c -pipe -g -Wall -W -D_REENTRANT -fPIE -DQT_NO_MTDEV -DQT_NO_TSLIB -DQT_NO_LIBINPUT -DQT_NO_XKB -DPROPARSER_DEBUG -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_TESTLIB_LIB -DQT_CORE_LIB -DQT_NAMESPACE=TestSpace -DQT_TESTCASE_BUILDDIR=/home/obuddenh/depot/qt5_build/qtbase/tests/auto/tools/qmakelib -I/home/obuddenh/depot/qt5/qtbase/tests/auto/tools/qmakelib -I. -I/home/obuddenh/depot/qt5/qtbase/qmake/library -I../../../../include -I../../../../include/QtTest -I../../../../include/QtCore -I.moc -I/home/obuddenh/depot/qt5/qtbase/mkspecs/linux-g++ -o .obj/qmakeparser.o /home/obuddenh/depot/qt5/qtbase/qmake/library/qmakeparser.cpp [2015-02-16T20:25:26.035255 20314] Hostname: troll08 [2015-02-16T20:25:26.035295 20314] Working directory: /home/obuddenh/depot/qt5_build/qtbase/tests/auto/tools/qmakelib [2015-02-16T20:25:26.035379 20314] Source file: /home/obuddenh/depot/qt5/qtbase/qmake/library/qmakeparser.cpp [2015-02-16T20:25:26.035393 20314] Object file: .obj/qmakeparser.o [2015-02-16T20:25:26.035412 20314] Trying direct lookup [2015-02-16T20:25:26.035865 20314] Looking for object file hash in /home/obuddenh/.ccache/1/8/3571b3286295ea842e4d0e4b5d8614-51629.manifest [2015-02-16T20:25:26.055382 20314] Got object file hash from manifest [2015-02-16T20:25:26.055444 20314] Unlink .obj/qmakeparser.o via .obj/qmakeparser.o.tmp.rm.troll08.20314 [2015-02-16T20:25:26.055697 20314] Copying /home/obuddenh/.ccache/6/1/77b6a1a9b40804c3fde51f0bc6c051-1584683.o to .obj/qmakeparser.o via .obj/qmakeparser.o.troll08.20314.XX (uncompressed) [2015-02-16T20:25:26.056724 20314] Created .obj/qmakeparser.o from /home/obuddenh/.ccache/6/1/77b6a1a9b40804c3fde51f0bc6c051-1584683.o [2015-02-16T20:25:26.056755 20314] Succeeded getting cached result [2015-02-16T20:25:26.056793 20314] Acquired lock /home/obuddenh/.ccache/6/stats.lock [2015-02-16T20:25:26.056988 20314] Releasing lock /home/obuddenh/.ccache/6/stats.lock [2015-02-16T20:25:26.057008 20314] Unlink /home/obuddenh/.ccache/6/stats.lock (as-tmp) [2015-02-16T20:25:26.057033 20314] Result: cache hit (direct) to reproduce it, you only need: qtbase/dev (@1d2efe1f27bedcbaa157ef4e82b8eda33dda46ad). this pending change: https://codereview.qt-project.org/105039 (PS3) including dependencies. this hunk on top: --- a/qmake/library/qmakeparser.cpp +++ b/qmake/library/qmakeparser.cpp @@ -1340,6 +1374,7 @@ static bool getBlock(const ushort *tokens, int limit, int offset, QString *outS return false; } *outStr += fL1S( H() + fL1S(tokNames[maskedTok]); +*outStr += fL1S( /* \\u) + QString::number(maskedTok, 16) + fL1S( */); if (tok TokNewStr) *outStr += fL1S( | TokNewStr); if (tok TokQuoted) ... and a lot of time, heh. i thought i might have some env variables set (CCACHE_UNIFY), but this doesn't appear to be the case, either. i can try to extract a smaller testcase if you don't beat me to it.
Bug#778571: sbuild: predictible build location for reproducible builds
Package: sbuild
Version: 0.65.0-1
Severity: wishlist
Tags: patch
Thanks for maintaining sbuild!
In order to use sbuild for reproducible builds, the build dir needs to
be consistent across rebuilds, but sbuild currenty generates a
randomly named build dir.
The following proof-of-concept patch does this by setting the build
dir to /build/PACKAGE-VERSION rather than /build/PACKAGE-XX:
From 15b77405a67faaea7bc3974a4e7a3862620d0b42 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian vagr...@debian.org
Date: Fri, 13 Feb 2015 23:18:23 -0800
Subject: [PATCH 1/2] Make predictible build dir location based on the package
version.
---
lib/Sbuild/Build.pm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lib/Sbuild/Build.pm b/lib/Sbuild/Build.pm
index 155e4fc..5149a8a 100644
--- a/lib/Sbuild/Build.pm
+++ b/lib/Sbuild/Build.pm
@@ -396,8 +396,8 @@ sub run_chroot_session {
# TODO: Don't hack the build location in; add a means to customise
# the chroot directly. i.e. allow changing of /build location.
$self-set('Chroot Build Dir',
- tempdir($self-get('Package') . '-XX',
- DIR = $session-get('Location') . /build));
+ $session-get('Location') . /build/ .
$self-get('Package') . - . $self-get('Version'));
+ mkdir $self-get('Chroot Build Dir');
$self-set('Build Dir', $session-strip_chroot_path($self-get('Chroot
Build Dir')));
--
2.1.4
This patch is really only a small step forward, making the build dir
consistent only when building with sbuild. Ideally, the build dir
should be set to /usr/src/debian/PACKAGE-VERSION (or some other widely
agreed upon dir) so that builds would be reproducible if built with
other tools such as pbuilder using the same build dir.
Making the build dir configurable might also help...
live well,
vagrant
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (500, 'testing'), (120, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages sbuild depends on:
ii adduser 3.113+nmu3
ii apt-utils 1.0.9.6
ii libsbuild-perl 0.65.0-1
ii perl5.20.1-5
ii perl-modules5.20.1-5
Versions of packages sbuild recommends:
ii debootstrap 1.0.66
ii fakeroot 1.20.2-1
Versions of packages sbuild suggests:
pn deborphan none
ii wget 1.16-1
-- no debconf information
signature.asc
Description: PGP signature
Bug#778412: Henry Spencer regular expressions (regex) library contains a heap overflow vulnerability
On Sat, Feb 14, 2015 at 03:41:21PM +0100, Luciano Bello wrote: Package: nvi Severity: important Tags: security patch The security team received a report from the CERT Coordination Center that the Henry Spencer regular expressions (regex) library contains a heap overflow vulnerability. It looks like this package includes the affected code at that's the reason of this bug report. The patch is available here: http://gitweb.dragonflybsd.org/dragonfly.git/blobdiff/4d133046c59a851141519d03553a70e903b3eefc..2841837793bd095a82f477e9c370cfe6cfb3862c:/lib/libc/regex/regcomp.c Building with --disable-re should fix this. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774700: Cryptsetup tools are not included by update-initramfs command
Hello Jonas! We run into this bug, too. There is mkinitramfs_debug.log you requested at message #25. Installation was performed from debian testing amd64 netinst ISO image built on unknown date, and apt-get dist-upgraded to jessie. cryptsetup version is 2:1.6.6-5. Thanks in advance! + PREREQ= + prereqs + echo + exit 0 + PREREQ= + . /usr/share/initramfs-tools/hook-functions + setup=no + rootdevs= + usrdevs= + resumedevs= + [ -n ] + [ -r /etc/crypttab ] + get_fs_devices / + local device mount type options dump pass + local wantmount=/ + [ ! -r /etc/fstab ] + read device mount type options dump pass + grep -s ^[^#] /etc/fstab + [ / = / ] + local devices + [ ext4 = btrfs ] + canonical_device UUID=9feb0db8-5828-48eb-b43f-63cbd141122d + local dev altdev original + dev=UUID=9feb0db8-5828-48eb-b43f-63cbd141122d + opt= + altdev=UUID=9feb0db8-5828-48eb-b43f-63cbd141122d + [ UUID=9feb0db8-5828-48eb-b43f-63cbd141122d != UUID=9feb0db8-5828-48eb-b43f-63cbd141122d ] + altdev=9feb0db8-5828-48eb-b43f-63cbd141122d + [ 9feb0db8-5828-48eb-b43f-63cbd141122d != UUID=9feb0db8-5828-48eb-b43f-63cbd141122d ] + dev=/dev/disk/by-uuid/9feb0db8-5828-48eb-b43f-63cbd141122d + original=/dev/disk/by-uuid/9feb0db8-5828-48eb-b43f-63cbd141122d + [ -h /dev/disk/by-uuid/9feb0db8-5828-48eb-b43f-63cbd141122d ] + readlink -e /dev/disk/by-uuid/9feb0db8-5828-48eb-b43f-63cbd141122d + dev=/dev/sda1 + [ = --no-simplify ] + [ x/dev/sda1 = x ] + altdev=/dev/sda1 + [ /dev/sda1 != /dev/sda1 ] + [ x = x ] + echo 9feb0db8-5828-48eb-b43f-63cbd141122d + return 0 + devices=9feb0db8-5828-48eb-b43f-63cbd141122d + echo 9feb0db8-5828-48eb-b43f-63cbd141122d + return + rootdevs=9feb0db8-5828-48eb-b43f-63cbd141122d + [ -z 9feb0db8-5828-48eb-b43f-63cbd141122d ] + get_fs_devices /usr + local device mount type options dump pass + local wantmount=/usr + [ ! -r /etc/fstab ] + read device mount type options dump pass + grep -s ^[^#] /etc/fstab + [ / = /usr ] + read device mount type options dump pass + usrdevs= + get_resume_devices + local device opt count dupe candidates devices derived + candidates= + [ -e /etc/uswsusp.conf ] + [ -e /etc/suspend.conf ] + cat /proc/cmdline + [ -e /etc/initramfs-tools/conf.d/resume ] + devices= + count=0 + [ 0 -gt 1 ] + [ 0 -gt 0 ] + return 0 + resumedevs= + get_initramfs_devices + local device opt count dupe target source key options candidates devices derived + read target source key options + grep -s ^[^#] /etc/crypttab + candidates= + devices= + count=0 + [ 0 -gt 0 ] + return 0 + initramfsdevs= + add_device 9feb0db8-5828-48eb-b43f-63cbd141122d + local node nodes opts lastopts i count + nodes=9feb0db8-5828-48eb-b43f-63cbd141122d + opts= + lastopts= + [ -z 9feb0db8-5828-48eb-b43f-63cbd141122d ] + grep -q \b9feb0db8-5828-48eb-b43f-63cbd141122d\b + echo 9feb0db8-5828-48eb-b43f-63cbd141122d + [ -z ] + opts=rootdev + node_is_in_crypttab 9feb0db8-5828-48eb-b43f-63cbd141122d + local node + node=9feb0db8-5828-48eb-b43f-63cbd141122d + grep -q ^9feb0db8-5828-48eb-b43f-63cbd141122d\b /etc/crypttab + return 1 + get_lvm_deps 9feb0db8-5828-48eb-b43f-63cbd141122d + local node deps maj min depnode + node=9feb0db8-5828-48eb-b43f-63cbd141122d + [ -z 9feb0db8-5828-48eb-b43f-63cbd141122d ] + cut -d: -f1 + dmsetup --noheadings splitname 9feb0db8-5828-48eb-b43f-63cbd141122d + vgs --noheadings -o pv_name 9feb0db8 + deps= + return 0 + lvmnodes= + [ -z ] + return 0 + modules= + [ -n ] + [ no = no ] + continue + [ most != dep ] + [ no = yes ] + [ no = yes ] + exit 0
Bug#764275: chromium: Segfaults on Startup
Package: chromium Version: 37.0.2062.120 Built on Debian 7.6, running on Debian 7.8 (281580) (64-bit) when I start chromium from command line, I get following error: ERROR:sandbox_linux.cc(308)] InitializeSandbox() called with multiple threads in process gpu-process while googling, I found bug 764275, where the OP has similar error. Unlike the OP, I don't get segmentation fault/crash. But the error seems worrying nevertheless. I have therefore requested this bug to be unarchived. I will be happy to provide more information, if needed Regards, Martin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778559: gdm3: Login temporarily unavailable if the previous user failed login
Package: gdm3
Version: 3.14.1-3
Followup-For: Bug #778559
Dear Maintainer,
The bug also exists on my other machine running Jessie. Here is the
system information for that machine. If you need any other information
about either system, please let me know.
-Laverne
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.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 gdm3 depends on:
ii accountsservice 0.6.37-3+b1
ii adduser 3.113+nmu3
ii dconf-cli 0.22.0-1
ii dconf-gsettings-backend 0.22.0-1
ii debconf [debconf-2.0] 1.5.55
ii gir1.2-gdm3 3.14.1-3
ii gnome-session [x-session-manager] 3.14.0-2
ii gnome-session-bin 3.14.0-2
ii gnome-settings-daemon 3.14.2-2
ii gnome-shell 3.14.2-3+b1
ii gnome-terminal [x-terminal-emulator] 3.14.1-1
ii gsettings-desktop-schemas 3.14.1-1
ii libaccountsservice0 0.6.37-3+b1
ii libaudit1 1:2.4-1+b1
ii libc6 2.19-13
ii libcanberra-gtk3-00.30-2.1
ii libcanberra0 0.30-2.1
ii libgdk-pixbuf2.0-02.31.1-2+b1
ii libgdm1 3.14.1-3
ii libglib2.0-0 2.42.1-1
ii libglib2.0-bin2.42.1-1
ii libgtk-3-03.14.5-1
ii libpam-modules1.1.8-3.1
ii libpam-runtime1.1.8-3.1
ii libpam-systemd215-11
ii libpam0g 1.1.8-3.1
ii librsvg2-common 2.40.5-1
ii libselinux1 2.3-2
ii libsystemd0 215-11
ii libwrap0 7.6.q-25
ii libx11-6 2:1.6.2-3
ii libxau6 1:1.0.8-1
ii libxdmcp6 1:1.1.1-1+b1
ii libxrandr22:1.4.2-1+b1
ii lsb-base 4.1+Debian13+nmu1
ii mutter [x-window-manager] 3.14.2-1
ii policykit-1 0.105-8
ii ucf 3.0030
ii x11-common1:7.7+7
ii x11-xserver-utils 7.7+3+b1
ii xterm [x-terminal-emulator] 312-1
Versions of packages gdm3 recommends:
ii at-spi2-core 2.14.0-1
ii desktop-base 8.0.2
ii gnome-icon-theme 3.12.0-1
ii gnome-icon-theme-symbolic 3.12.0-1
ii x11-xkb-utils 7.7+1
ii xserver-xephyr 2:1.16.2.901-1
ii xserver-xorg 1:7.7+7
ii zenity 3.14.0-1
Versions of packages gdm3 suggests:
pn gnome-orcanone
ii libpam-gnome-keyring 3.14.0-1+b1
-- Configuration Files:
/etc/gdm3/Init/Default changed:
PATH=/usr/bin:$PATH
OLD_IFS=$IFS
gdmwhich () {
COMMAND=$1
OUTPUT=
IFS=:
for dir in $PATH
do
if test -x $dir/$COMMAND ; then
if test x$OUTPUT = x ; then
OUTPUT=$dir/$COMMAND
fi
fi
done
IFS=$OLD_IFS
echo $OUTPUT
}
sysresources=/etc/X11/Xresources
if [ -f $sysresources ]; then
xrdb -merge $sysresources
fi
sysmodmap=/etc/X11/Xmodmap
XMODMAP=`gdmwhich xmodmap`
if [ x$XMODMAP != x ] ; then
if [ x$GDM_PARENT_DISPLAY = x ]; then
if [ -f $sysmodmap ]; then
$XMODMAP $sysmodmap
fi
else
( DISPLAY=$GDM_PARENT_DISPLAY XAUTHORITY=$GDM_PARENT_XAUTHORITY
$XMODMAP -pke ) | $XMODMAP -
fi
#
# Switch Sun's Alt and Meta mod mappings
#
UNAME=`gdmwhich uname`
PROCESSOR=`$UNAME -p`
if [ x$PROCESSOR = xsparc ]; then
if $XMODMAP | grep mod4 | grep Alt /dev/null 2/dev/null
then
$XMODMAP -e clear Mod1 \
-e clear Mod4 \
-e add Mod1 = Alt_L \
-e add Mod1 = Alt_R \
-e add Mod4 = Meta_L \
-e add Mod4 = Meta_R
fi
fi
fi
SETXKBMAP=`gdmwhich setxkbmap`
if [ x$SETXKBMAP != x ] ; then
# FIXME: is this all right? Is this completely on crack?
# What this does is move the xkb configuration from the
GDM_PARENT_DISPLAY
# FIXME: This should be done in code. Or there must be an easier
way ...
if [ -n $GDM_PARENT_DISPLAY ]; then
XKBSETUP=`( DISPLAY=$GDM_PARENT_DISPLAY XAUTHORITY=
$GDM_PARENT_XAUTHORITY $SETXKBMAP -v )`
if [ -n $XKBSETUP ]; then
XKBKEYMAP=`echo $XKBSETUP | grep '^keymap' | awk '{ print $2 }'`
XKBTYPES=`echo $XKBSETUP | grep '^types' | awk '{ print $2 }'`
XKBCOMPAT=`echo $XKBSETUP | grep '^compat' | awk '{ print $2 }'`
Bug#774033: debian-lan-config: diskless clients do not work: workaround
Hi, On Sat, 27 Dec 2014 20:35:52 +0100 Andreas B. Mundt andi.mu...@web.de wrote: currently diskless machines seem not to work. On login, the user is authenticated successfully, but the machine kind of deadlocks immediately (perhaps on mounting the home directory?) and no prompt is shown. To work around the issue, switch back to serving the diskless' root file system with nfs3. Add the line: /opt/live 10.0.0.0/16(ro,no_subtree_check,no_root_squash) to '/etc/fstab' on the mainserver and run 'exportfs -ra'. Then modify the pxe boot file for the corresponding machines in '/srv/tftp/fai/pxelinux.cfg/'. Comment the original 'append'-line and add the second line: #append initrd=initrd.img ip=dhcp root=nfs4:/live aufs append initrd=initrd.img ip=dhcp root=/dev/nfs nfsroot=/opt/live aufs (To do that for all diskless machines, modify line 104 in '/usr/local/sbin/debian-lan-chroots' and run the script again.) Do the same in '/etc/di-netboot-assistant/pxelinux.HEAD' (line 38) and recreate the pxe-menu: 'di-netboot-assistant rebuild-menu'. After that, diskless machines should work again. (#759544 is another problem that happens at least with my VMs). Best regards, Andi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778566: unblock: node-serve-static/1.6.4-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package node-serve-static
The package had a security vulnerability which was the bug that caused
node-serve-static and its reverse dependencies to be marked as
autoremove. This debdiff fixes that vulnerability without touching any
other code.
diff -Nru node-serve-static-1.6.4/debian/changelog
node-serve-static-1.6.4/debian/changelog
--- node-serve-static-1.6.4/debian/changelog2014-10-15 15:52:21.0
+
+++ node-serve-static-1.6.4/debian/changelog2015-02-16 19:05:08.0
+
@@ -1,3 +1,9 @@
+node-serve-static (1.6.4-2) UNRELEASED; urgency=medium
+
+ * Upstream patch fixing CVE-2015-1164 (Closes: #775843).
+
+ -- Jérémy Lal kapo...@melix.org Sat, 31 Jan 2015 12:10:55 +0100
+
node-serve-static (1.6.4-1) unstable; urgency=medium
[ Leo Iannacone ]
diff -Nru node-serve-static-1.6.4/debian/patches/CVE-2015-1164.patch
node-serve-static-1.6.4/debian/patches/CVE-2015-1164.patch
--- node-serve-static-1.6.4/debian/patches/CVE-2015-1164.patch 1970-01-01
00:00:00.0 +
+++ node-serve-static-1.6.4/debian/patches/CVE-2015-1164.patch 2015-02-16
19:05:08.0 +
@@ -0,0 +1,71 @@
+Description: Fix open redirect when mounted at root
+Origin: https://github.com/expressjs/serve-static/commit/0399e399.patch
+Bug-Upstream: https://github.com/expressjs/serve-static/issues/26
+From: Douglas Christopher Wilson d...@somethingdoug.com
+Last-Update: 2015-01-31
+Reviewed-by: Jérémy Lal kapo...@melix.org
+Applied-Upstream: 1.7.2
+
+fixes #26
+--- a/index.js
b/index.js
+@@ -79,10 +79,13 @@
+ return next()
+ }
+
+-originalUrl.pathname += '/'
++// append trailing slash
++originalUrl.pathname = collapseLeadingSlashes(originalUrl.pathname +
'/')
+
++// reformat the URL
+ var target = url.format(originalUrl)
+
++// send redirect response
+ res.statusCode = 303
+ res.setHeader('Content-Type', 'text/html; charset=utf-8')
+ res.setHeader('Location', target)
+@@ -116,3 +119,19 @@
+ */
+
+ exports.mime = send.mime
++
++/**
++ * Collapse all leading slashes into a single slash
++ * @private
++ */
++function collapseLeadingSlashes(str) {
++ for (var i = 0; i str.length; i++) {
++if (str[i] !== '/') {
++ break
++}
++ }
++
++ return i 1
++? '/' + str.substr(i)
++: str
++}
+--- a/test/test.js
b/test/test.js
+@@ -259,6 +259,13 @@
+ .expect(303, done)
+ })
+
++it('should not redirect to protocol-relative locations', function (done) {
++ request(server)
++ .get('//users')
++ .expect('Location', '/users/')
++ .expect(303, done)
++})
++
+ it('should not redirect incorrectly', function (done) {
+ request(server)
+ .get('/')
+@@ -532,7 +539,7 @@
+ it('should not choke on auth-looking URL', function(done){
+ request(server)
+ .get('//todo@txt')
+- .expect('Location', '//todo@txt/')
++ .expect('Location', '/todo@txt/')
+ .expect(303, done);
+ });
+ });
diff -Nru node-serve-static-1.6.4/debian/patches/series
node-serve-static-1.6.4/debian/patches/series
--- node-serve-static-1.6.4/debian/patches/series 1970-01-01
00:00:00.0 +
+++ node-serve-static-1.6.4/debian/patches/series 2015-02-16
19:05:08.0 +
@@ -0,0 +1 @@
+CVE-2015-1164.patch
unblock node-serve-static/1.6.4-1
-- System Information:
Debian Release: 8.0
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16-2-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#778554: unblock: systemd/215-12
Control: tags -1 moreinfo On 2015-02-16 17:16, Martin Pitt wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock systemd 215-12 hit unstable three days ago with some RC/important/safe So far there have been no regression reports. At the time of this writing there are now no RC bugs left \o/ [...] Hi Martin, I have not had time to review this fully. However, I noticed #778565, which suggests a regression in this version of udev. I am putting this unblock request on hold until you have had a time to review #778565. While you are at it, would you mind having a look at #755722? I'd be interested in your opinion whether for jessie we should (1) ignore the problem, (2) apply the sysv behaviour compatible hwclock.service, or (3) boldly go and enable timesyncd. Thanks, Martin unblock systemd/215-12 Personally, I am leaning towards (2) in the absence of a patch/diff for (3). Though, as I understood the link to the upstream date, part of the reason for not sync'ing the time was to make it easier on live-CDs. Is this the sort of change that will break live-CDs? If so, what will it take to not break live-CDs with (2) (or possibly (3)). Thanks, ~Niels -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778569: gnome-session-flashback: switching between different keyboard layouts does not work
Package: gnome-session-flashback Version: 3.8.1-7 Severity: important Dear Maintainer, On clean Jessie installation in GNOME flashback session I setup two keyboard layouts (ru and us). But layout switching does not work neither with default shortcut (Alt-Shift, Super-Space) nor with others (Menu, Ctrl-Shift). I've not checked all possible keyboard shortcuts settings. Layout switching is broken only in flashback session in normal gnome session layout can be switched as expected. As a temporary solution I installed gxneur and created script, that is started automatically as user logs in. #!/bin/sh setxkbmap -option grp:switch,grp:alt_shift_toggle,grp_led:scroll us,ru gxneur -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-session-flashback depends on: ii gnome-flashback 3.10.0-3 ii gnome-panel 3.8.1-7+b1 ii gnome-screensaver 3.6.1-4 ii gnome-session-bin 3.14.0-2 ii gnome-session-common3.14.0-2 ii gnome-settings-daemon 3.14.2-2 ii mate-notification-daemon [notification-daemon] 1.8.1-2 ii mate-polkit [policykit-1-gnome] 1.8.0+dfsg1-4 ii metacity1:3.14.3-1 ii nautilus3.14.1-2 ii notification-daemon 0.7.6-2 ii policykit-1-gnome 0.105-2 Versions of packages gnome-session-flashback recommends: ii gnome-power-manager 3.14.1-1 Versions of packages gnome-session-flashback suggests: ii desktop-base 8.0.2 ii gnome-keyring 3.14.0-1+b1 ii gnome-user-guide 3.14.1-1 -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778388: ccache: scanner confused by comment signs in strings
this is pretty incredible ... i can't reproduce it with your testcase, either. but when i run the actual build with CCACHE_LOGFILE=/dev/stdout, it totally confirms that the issue is real: [2015-02-16T20:25:26.035076 20314] === CCACHE STARTED = [2015-02-16T20:25:26.035222 20314] Command line: /usr/bin/ccache /usr/bin/g++ -c -pipe -g -Wall -W -D_REENTRANT -fPIE -DQT_NO_MTDEV -DQT_NO_TSLIB -DQT_NO_LIBINPUT -DQT_NO_XKB -DPROPARSER_DEBUG -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_TESTLIB_LIB -DQT_CORE_LIB -DQT_NAMESPACE=TestSpace -DQT_TESTCASE_BUILDDIR=/home/obuddenh/depot/qt5_build/qtbase/tests/auto/tools/qmakelib -I/home/obuddenh/depot/qt5/qtbase/tests/auto/tools/qmakelib -I. -I/home/obuddenh/depot/qt5/qtbase/qmake/library -I../../../../include -I../../../../include/QtTest -I../../../../include/QtCore -I.moc -I/home/obuddenh/depot/qt5/qtbase/mkspecs/linux-g++ -o .obj/qmakeparser.o /home/obuddenh/depot/qt5/qtbase/qmake/library/qmakeparser.cpp [2015-02-16T20:25:26.035255 20314] Hostname: troll08 [2015-02-16T20:25:26.035295 20314] Working directory: /home/obuddenh/depot/qt5_build/qtbase/tests/auto/tools/qmakelib [2015-02-16T20:25:26.035379 20314] Source file: /home/obuddenh/depot/qt5/qtbase/qmake/library/qmakeparser.cpp [2015-02-16T20:25:26.035393 20314] Object file: .obj/qmakeparser.o [2015-02-16T20:25:26.035412 20314] Trying direct lookup [2015-02-16T20:25:26.035865 20314] Looking for object file hash in /home/obuddenh/.ccache/1/8/3571b3286295ea842e4d0e4b5d8614-51629.manifest [2015-02-16T20:25:26.055382 20314] Got object file hash from manifest [2015-02-16T20:25:26.055444 20314] Unlink .obj/qmakeparser.o via .obj/qmakeparser.o.tmp.rm.troll08.20314 [2015-02-16T20:25:26.055697 20314] Copying /home/obuddenh/.ccache/6/1/77b6a1a9b40804c3fde51f0bc6c051-1584683.o to .obj/qmakeparser.o via .obj/qmakeparser.o.troll08.20314.XX (uncompressed) [2015-02-16T20:25:26.056724 20314] Created .obj/qmakeparser.o from /home/obuddenh/.ccache/6/1/77b6a1a9b40804c3fde51f0bc6c051-1584683.o [2015-02-16T20:25:26.056755 20314] Succeeded getting cached result [2015-02-16T20:25:26.056793 20314] Acquired lock /home/obuddenh/.ccache/6/stats.lock [2015-02-16T20:25:26.056988 20314] Releasing lock /home/obuddenh/.ccache/6/stats.lock [2015-02-16T20:25:26.057008 20314] Unlink /home/obuddenh/.ccache/6/stats.lock (as-tmp) [2015-02-16T20:25:26.057033 20314] Result: cache hit (direct) to reproduce it, you only need: qtbase/dev (@1d2efe1f27bedcbaa157ef4e82b8eda33dda46ad). this pending change: https://codereview.qt-project.org/105039 (PS3) including dependencies. this hunk on top: --- a/qmake/library/qmakeparser.cpp +++ b/qmake/library/qmakeparser.cpp @@ -1340,6 +1374,7 @@ static bool getBlock(const ushort *tokens, int limit, int offset, QString *outS return false; } *outStr += fL1S( H() + fL1S(tokNames[maskedTok]); +*outStr += fL1S( /* \\u) + QString::number(maskedTok, 16) + fL1S( */); if (tok TokNewStr) *outStr += fL1S( | TokNewStr); if (tok TokQuoted) ... and a lot of time, heh. i thought i might have some env variables set (CCACHE_UNIFY), but this doesn't appear to be the case, either. i can try to extract a smaller testcase if you don't beat me to it. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778532: apt-cacher-ng fails with Acquire::http to http.debian.net
tags 778532 +moreinfo thanks Hallo, * Mathias Behrle [Mon, Feb 16 2015, 12:45:40PM]: Package: apt-cacher-ng Version: 0.8.0-3 Severity: normal Ign http://http.debian.net jessie-updates Release Err http://http.debian.net jessie/main amd64 Packages 404 Not Found [IP: 192.168.99.13 ] Err http://http.debian.net jessie-updates/main amd64 Packages Please send me the apt-cacher-ng logs and configuration files from your server. Regards, Eduard. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776264: icu security upload
Michael Gilbert mgilb...@debian.org wrote: I uploaded an nmu to delayed/5 fixing all of the known security issues. Please let me know if I should delay longer. From my perspective, this is fine. I think this provides a good opportunity for the next maintainer (presumably László though I've seen some discussion in the ITA about collaborative maintenance) to grab the repo, incorporate the fixes, and do a new upload that completes the adoption process of the package. I won't plan on taking any action, so if the new maintainer doesn't act within the number of days, the NMU will go through. Thanks for taking care of it. I can do a quick review if desired, but I would only be reviewing mechanics, not correctness of the patches, as I haven't and won't have time to look into the details of the problems or their solutions. -- Jay Berkenbilt q...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778564: [pkg-ntp-maintainers] Bug#778564: Should be possible to preseed ntp server
On Mon, Feb 16, 2015 at 06:10:32PM +, Ian Jackson wrote: Package: ntp Version: 1:4.2.6.p5+dfsg-2+deb7u1 I did a preseeded installation of wheezy with d-i clock-setup/ntp-server string ntp.uk.xensource.com As far as I know that is for the clock-setup package, not anything related to ntp. I think it currently only sets the clock correct once and doesn't put that value in any config file we could use. I'm not sure where exactly this should be fixed. ntp.conf is a dpkg-handled conffile in ntp in wheezy so I think at the very least ntp needs to change. An alternative is to send the ntp servers using DHCP. In that case we generate a new config file (with other name) and replace the servers in it. This currently seems to be broken when using netwerk-manager though. Kurt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775834: closed by Michael Gilbert mgilb...@debian.org (Bug#775834: fixed in isc-dhcp 4.3.1-6)
reopen 775834 thanks I'm not convinced that a change to isc-dhcp fixes this issue - did you perhaps make a typo? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778437: palo: please make the build reproducible
Hello Chris, On 16.02.2015 00:08, Chris Lamb wrote: With that in mind we can not use debian-specific tools like dpkg-parsechangelog... Of course. The patch was 50% to highlight/demonstrate the issue in a concise way and 50% assuming that it would be a Debian-specific modification. I've pushed two changes upstream which will make the build reproducible: http://git.kernel.org/cgit/linux/kernel/git/deller/palo.git/commit/?id=db563d9c49054409959f9befbcb05d28a6d68c20 http://git.kernel.org/cgit/linux/kernel/git/deller/palo.git/commit/ Thanks, Helge -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777607: puppet-module-puppetlabs-postgresql: Module tries to install postgresql-9.3 on jessie and fails
Hi,
I can confirm that the upstream commit resolves the issue. The
attached patch backports it.
Thanks,
-- Andrew Starr-Bochicchio
Ubuntu Developer https://launchpad.net/~andrewsomething
Debian Developer http://qa.debian.org/developer.php?login=asb
PGP/GPG Key ID: D53FDCB1
From 5a16c4afd05617763b584e79de21bb137978da7c Mon Sep 17 00:00:00 2001
From: Andrew Starr-Bochicchio a...@debian.org
Date: Mon, 16 Feb 2015 13:09:55 -0500
Subject: [PATCH] use_postgresql-9.4_on_jessie.patch: Backport upstream commit
to correctly use postgresql 9.4 on Jessie (Closes: #777607).
---
debian/changelog | 8 ++
debian/patches/series | 1 +
debian/patches/use_postgresql-9.4_on_jessie.patch | 31 +++
3 files changed, 40 insertions(+)
create mode 100644 debian/patches/series
create mode 100644 debian/patches/use_postgresql-9.4_on_jessie.patch
diff --git a/debian/changelog b/debian/changelog
index 2e35323..5be8118 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+puppet-module-puppetlabs-postgresql (4.0.0-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * use_postgresql-9.4_on_jessie.patch: Backport upstream commit
+to correctly use postgresql 9.4 on Jessie (Closes: #777607).
+
+ -- Andrew Starr-Bochicchio a...@debian.org Mon, 16 Feb 2015 13:07:26 -0500
+
puppet-module-puppetlabs-postgresql (4.0.0-1) unstable; urgency=medium
* Imported upstream relase 4.0.0
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 000..479d051
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+use_postgresql-9.4_on_jessie.patch
diff --git a/debian/patches/use_postgresql-9.4_on_jessie.patch b/debian/patches/use_postgresql-9.4_on_jessie.patch
new file mode 100644
index 000..1325c5c
--- /dev/null
+++ b/debian/patches/use_postgresql-9.4_on_jessie.patch
@@ -0,0 +1,31 @@
+From 9bb1c5e491463fe64beff663be156d6724b4e06e Mon Sep 17 00:00:00 2001
+From: Armin ranjbar z...@zoup.org
+Date: Fri, 21 Nov 2014 22:26:18 +0330
+Subject: [PATCH] Fixing autodetected version for Debian Jessie, which uses
+ postgresql 9.4
+
+---
+ manifests/globals.pp | 3 ++-
+ 1 file changed, 2 insertions(+), 1 deletion(-)
+
+Index: puppet-module-puppetlabs-postgresql/manifests/globals.pp
+===
+--- puppet-module-puppetlabs-postgresql.orig/manifests/globals.pp 2015-02-16 13:06:53.515483692 -0500
puppet-module-puppetlabs-postgresql/manifests/globals.pp 2015-02-16 13:06:53.511483620 -0500
+@@ -67,7 +67,7 @@
+ 'Debian' = $::operatingsystemrelease ? {
+ /^6\./ = '8.4',
+ /^(wheezy|7\.)/ = '9.1',
+-/^(jessie|8\.)/ = '9.3',
++/^(jessie|8\.)/ = '9.4',
+ default = undef,
+ },
+ 'Ubuntu' = $::operatingsystemrelease ? {
+@@ -102,6 +102,7 @@
+ '91'= '1.5',
+ '9.2' = '2.0',
+ '9.3' = '2.1',
++'9.4' = '2.1',
+ default = undef,
+ }
+ $globals_postgis_version = pick($postgis_version, $default_postgis_version)
--
2.1.0
Bug#778563: differing header files
Source: witty Version: 3.3.3+dfsg-4.1 User: reproducible-bui...@lists.alioth.debian.org Hi! While working on Debian's “reproducible builds” effort [1], we have noticed that witty doesn't build reproducibly [2]. There is a difference in the header file /usr/include/Wt/WConfig.h. Depending on the build, some macros are defined or not: On one build it had the following content: #define WT_STATIC #define WTDBO_STATIC #define WTDBOPOSTGRES_STATIC #define WTDBOSQLITE3_STATIC #define WTDBOFIREBIRD_STATIC #define WTDBOMYSQL_STATIC #define WTHTTP_STATIC #define WT_EXT_STATIC #define WT_EXT_STATIC While on another build it contained the following lines: /* #undef WT_STATIC */ /* #undef WTDBO_STATIC */ /* #undef WTDBOPOSTGRES_STATIC */ /* #undef WTDBOSQLITE3_STATIC */ /* #undef WTDBOFIREBIRD_STATIC */ /* #undef WTDBOMYSQL_STATIC */ /* #undef WTHTTP_STATIC */ /* #undef WT_EXT_STATIC */ /* #undef WT_EXT_STATIC */ The build environments differed in user/group, hostname, time, locale, but the toolchain was the same. The generated header should always be identical with the same toolchain. Regards, Reiner [1]: https://wiki.debian.org/ReproducibleBuilds [2]: https://reproducible.debian.net/witty signature.asc Description: OpenPGP digital signature
Bug#778564: Should be possible to preseed ntp server
Package: ntp Version: 1:4.2.6.p5+dfsg-2+deb7u1 I did a preseeded installation of wheezy with d-i clock-setup/ntp-server string ntp.uk.xensource.com This was honoured during installation, but after installation the real system has *.debian.pool.ntp.org in its ntp.conf. This is obviously not desirable. This bug against clock-setup in Ubuntu seems to be the same complaint: https://bugs.launchpad.net/ubuntu/+source/clock-setup/+bug/388343 I'm not sure where exactly this should be fixed. ntp.conf is a dpkg-handled conffile in ntp in wheezy so I think at the very least ntp needs to change. Thanks, Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777694: ITA: icu -- Development utilities for International Components for Unicode
On Mon, Feb 16, 2015 at 7:29 PM, Moritz Mühlenhoff j...@inutil.org wrote: On Mon, Feb 16, 2015 at 12:12:02AM +0100, László Böszörményi (GCS) wrote: I'm ready with the first iteration[1]. I've backported all security fixes. Anyone would like to, please test it. If someone has exploits, I'm looking for reports how those work on this Debian package version. I noticed that Mike has been working on a NMU as well, adding him to CC. Ouch. Mike, can I check the contents of your NMU, download that package version? Laszlo/GCS -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738897: Looking to adopt
I believe I found a sponsor and this package looks to be one that fits my skill-sets and interests Is this package still actually orphaned? I see some regular updates have taken place on the tracker site... Sorry do not wish to jump the gun or anything - please let me know, thanks! *Richard B. Winters*
Bug#778244: tomboy: Please add evolution add on
Now that Evolution uses Gsettings, the evolution addin no longer works (it crashes all of tomboy). The tomboy package will build it in if evolution is installed, which should probably be fixed. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778567: qt5-default: wrongly in section libs
Package: qt5-default Version: 5.3.2+dfsg-4+b1 Severity: normal Dear Maintainer, Please consider moving qt5-default to the libdevel section since: - this package provides development facilities - qt4-default is already in the libdevel section - it makes deborphan list the package in its standard configuration (without ' --libdevel' option) Regards -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (990, 'unstable'), (980, 'stable-updates'), (980, 'testing'), (970, 'stable'), (90, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages qt5-default depends on: ii qtbase5-dev 5.3.2+dfsg-4+b1 ii qtchooser47-gd2b7997-2 qt5-default recommends no packages. Versions of packages qt5-default suggests: ii qt5-qmake 5.3.2+dfsg-4+b1 ii qtbase5-dev-tools 5.3.2+dfsg-4+b1 -- 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#755722: systemd must sync systemclock to RTC on shutdown
On Monday 16 February 2015 16:00:36, Michael Biebl wrote: There is also natural drift between the system clock and the RTC. Who is supposed to account for that? On a system with an uptime of several months, the drift may be large enough to cause the time to go backwards at a reboot. Running hwclock --systohc on shutdown does not solve the time skew problem. It does not magically make the RTC run accurately. But it solves the problem of spurious fscks at reboot, doesn't it? You could use hwclocks drift calculation and call hwclock --adjust e.g. via a cron job. That is ugly though and it get's easily confused in multi-boot environments. A better alternative is NTP. Incidentally, systemd ships systemd-timesyncd, a SNTP client, which can easily be enabled via systemctl enable systemd-timesyncd.service and we are discussing about shipping it enabled by default. I am not opposed to enabling timesyncd by default post-jessie. For jessie, I agree with the simpler fix posted by Martin. I don't know what timesyncd does if no NTP server is reachable. It's possible that this case will need to be discussed again, but probably that discussion should happen in upstream's bug tracker. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732209: unable to create file '/run/user/1000/dconf/user': Permission denied
Package: libpam-systemd Version: 215-11 Followup-For: Bug #732209 Hi Vlad, Yes, I am still able to reproduce this bug in my GNOME session in my latest Jessie, indeed. After opening the root terminal window and in focus, I can use three ways to trigger: 1. In a standar user terminal open a shell and run gksu gedit. 2. Type Super key and search dconf-Editor and run it. 3. Type Super key and search for Files file manager and run it. I do not use MATE so I don't know how that works. My system otherwise is working fine. I don't have access to unstable or experimental distro, so I cannot test it. My system is a healthy Debian Jessie 8 with systemd-sysv: root@localhost:~# systemctl status sysinit.target ● sysinit.target - System Initialization Loaded: loaded (/lib/systemd/system/sysinit.target; static) Active: active since Sun 2015-02-15 18:57:11 CET; 1 day 1h ago Docs: man:systemd.special(7) root@localhost:~# date Mon Feb 16 20:31:46 CET 2015 root@localhost:~# cat /etc/debian_version 8.0 gnome-session: 3.14.0-2 libpam-systemd: 215-11 gnome-shell:3.14.2-3+b1 Package gnome-desktop-environment is *not* installed. Regards, -- Miklos -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (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: systemd (via /run/systemd/system) Versions of packages libpam-systemd depends on: ii dbus 1.8.12-3 ii libc6 2.19-13 ii libcap21:2.24-6 ii libpam-runtime 1.1.8-3.1 ii libpam0g 1.1.8-3.1 ii multiarch-support 2.19-13 ii systemd215-11 ii systemd-sysv 215-11 libpam-systemd recommends no packages. libpam-systemd 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#770492: [RFC PATCH RESEND] vfs: Move security_inode_killpriv() after permission checks
On Sat, Jan 17, 2015 at 6:26 PM, Ben Hutchings b...@decadent.org.uk wrote: chown() and write() should clear all privilege attributes on a file - setuid, setgid, setcap and any other extended privilege attributes. However, any attributes beyond setuid and setgid are managed by the LSM and not directly by the filesystem, so they cannot be set along with the other attributes. Currently we call security_inode_killpriv() in notify_change(), but in case of a chown() this is too early - we have not called inode_change_ok() or made any filesystem-specific permission/sanity checks. Add a new function setattr_killpriv() which calls security_inode_killpriv() if necessary, and change the setattr() implementation to call this in each filesystem that supports xattrs. This assumes that extended privilege attributes are always stored in xattrs. Compile-tested only. XXX This is a silent change to the VFS API, but we should probably change something so OOT filesystems fail to compile if they aren't updated to call setattr_killpriv(). Reported-by: Ben Harris bj...@cam.ac.uk References: https://bugs.debian.org/770492 This seems to have stalled. I don't see it in linux-next or anywhere else I can find. The issue has a shiny CVE now, so it makes people that follow those nervous. Is there any further feedback or follow-up here? josh --- drivers/staging/lustre/lustre/llite/llite_lib.c | 4 fs/9p/vfs_inode.c | 4 fs/9p/vfs_inode_dotl.c | 4 fs/attr.c | 32 + fs/btrfs/inode.c| 4 fs/ceph/inode.c | 4 fs/cifs/inode.c | 11 - fs/ext2/inode.c | 4 fs/ext3/inode.c | 4 fs/ext4/inode.c | 4 fs/f2fs/file.c | 4 fs/fuse/dir.c | 15 +++- fs/fuse/file.c | 3 ++- fs/fuse/fuse_i.h| 2 +- fs/gfs2/inode.c | 3 +++ fs/hfs/inode.c | 4 fs/hfsplus/inode.c | 4 fs/jffs2/fs.c | 4 fs/jfs/file.c | 4 fs/kernfs/inode.c | 17 + fs/libfs.c | 3 +++ fs/nfs/inode.c | 11 +++-- fs/ocfs2/file.c | 6 - fs/reiserfs/inode.c | 4 fs/ubifs/file.c | 4 fs/xfs/xfs_acl.c| 3 ++- fs/xfs/xfs_file.c | 2 +- fs/xfs/xfs_ioctl.c | 2 +- fs/xfs/xfs_iops.c | 16 ++--- fs/xfs/xfs_iops.h | 10 ++-- include/linux/fs.h | 1 + mm/shmem.c | 4 32 files changed, 176 insertions(+), 25 deletions(-) diff --git a/drivers/staging/lustre/lustre/llite/llite_lib.c b/drivers/staging/lustre/lustre/llite/llite_lib.c index a8bcc51..2a714b2 100644 --- a/drivers/staging/lustre/lustre/llite/llite_lib.c +++ b/drivers/staging/lustre/lustre/llite/llite_lib.c @@ -1434,6 +1434,10 @@ int ll_setattr_raw(struct dentry *dentry, struct iattr *attr, bool hsm_import) spin_unlock(lli-lli_lock); } + rc = setattr_killpriv(dentry, attr); + if (rc) + return rc; + /* We always do an MDS RPC, even if we're only changing the size; * only the MDS knows whether truncate() should fail with -ETXTBUSY */ diff --git a/fs/9p/vfs_inode.c b/fs/9p/vfs_inode.c index 296482f..735cbf84 100644 --- a/fs/9p/vfs_inode.c +++ b/fs/9p/vfs_inode.c @@ -1130,6 +1130,10 @@ static int v9fs_vfs_setattr(struct dentry *dentry, struct iattr *iattr) if (S_ISREG(dentry-d_inode-i_mode)) filemap_write_and_wait(dentry-d_inode-i_mapping); + retval = setattr_killpriv(dentry, iattr); + if (retval) + return retval; + retval = p9_client_wstat(fid, wstat); if (retval 0) return retval; diff --git a/fs/9p/vfs_inode_dotl.c b/fs/9p/vfs_inode_dotl.c index 02b64f4..f3ca76d 100644 --- a/fs/9p/vfs_inode_dotl.c +++ b/fs/9p/vfs_inode_dotl.c @@ -583,6 +583,10 @@ int v9fs_vfs_setattr_dotl(struct dentry *dentry, struct iattr *iattr) if (S_ISREG(inode-i_mode)) filemap_write_and_wait(inode-i_mapping); + retval =
Bug#778446: python-argh: Please provide Python 3 package
Il 16/02/15 10:36, Marco Nenciarini ha scritto: Hi Brian, Il 15/02/15 23:26, Brian May ha scritto: Attached is a patch to fix this. I have not attempted to update the standards version. I also have not attempted to update the git repository, if you want I can redo the change using git as a reference, and commit the changes to git also. I plan to upload this tomorrow as a NMU. It will get stuck in new for a while, so you can raise any objections if I have done anything wrong. thanks for the patch. I will upload this today unless I found issues. I've found two issues with unit tests included in version 0.26.1 which I was pushing at the same time. Python 2.7 tests fail with - prompt = '\u043f\u0440\u0438\u0432\u0435\u0442? (y/n)' def safe_input(prompt): Prompts user for input. Correctly handles prompt message encoding. if sys.version_info (3,0): if isinstance(prompt, compat.text_type): # Python 2.x: unicode â bytes encoding = locale.getpreferredencoding() or 'utf-8' prompt = prompt.encode(encoding) E UnicodeEncodeError: 'ascii' codec can't encode characters in position 0-5: ordinal not in range(128) - and python 3.4 tests fail because they depends from py.test filename (which is py.test-3.4 in this case) I'll try to fix them this evening, but if I fail doing that I'll upload a 0.25.0-2 tomorrow. Regards, Marco -- - |Marco Nenciarini| Debian/GNU Linux Developer - Plug Member | | mnen...@prato.linux.it | http://www.prato.linux.it/~mnencia | - Key fingerprint = 7C23 B804 3E65 D298 0A21 B6E2 589F 03F0 1BA5 5038 signature.asc Description: OpenPGP digital signature
Bug#776847: gsasl 1.8.0-6 does not support GSSAPI
It seems clear that the #745332 fix was incorrect. You can see in the build logs GSSAPI is not enabled since krb5-config isn't found: https://buildd.debian.org/status/fetch.php?pkg=gsaslarch=amd64ver=1.8.0-6stamp=1412611018 On considering solutions, I don't like the unpredictability in depending on libkrb5-dev|libheimdal-dev. The GSSAPI library used by the binary libgsasl package in Debian will depend on whether the buildds have Heimdal or MIT installed when you built the package. Coping with different GSS libraries on different architecture sounds like a recipe for disaster. For Jessie, gsasl should be built against the same Kerberos library on all architectures, unless there is a reason not to -- and I don't know of a reason. MIT is picked arbitrarily here. Cc'ing Jelmer (who reported 745332) and Andreas (who uploaded it) -- any comments? Jelmer, what prompted your initial report? The way I see it, it is important (for us) that you buildds don't have multiple Kerberos development packages installed when they build gsasl. So the old way was the preferred way, causing heimdal-dev to be removed and libkrb5-dev to be pulled in. People with other preferences who build their own packages can surely modify the gsasl package to their liking. I've pushed a fix in git and attmpted to upload to experimental, so you can test the new packages. /Simon pgpTXn8nmJV3r.pgp Description: OpenPGP digital signatur
Bug#776847: gsasl 1.8.0-6 does not support GSSAPI
Hi, Jelmer 17.02.2015 0:51, Jelmer Vernooij пишет: On 16/02/15 22:13, Simon Josefsson wrote: It seems clear that the #745332 fix was incorrect. You can see in the build logs GSSAPI is not enabled since krb5-config isn't found: https://buildd.debian.org/status/fetch.php?pkg=gsaslarch=amd64ver=1.8.0-6stamp=1412611018 [skip] With the patch, the intent was to gsasl still build against MIT kerberos - e.g. no change in the binary packages. It merely changed the dependency from libkrb5-dev to libkrb5-multidev, the latter of which doesn't prevent heimdal-dev from being installed. With Your patch gsasl configure can't find krb5-config. From buildd logs above: configure: checking for GSS implementation (mit) configure: WARNING: MIT Kerberos krb5-config not found, disabling GSSAPI Without patch (1.8.0-4): configure: checking for GSS implementation (mit) configure: trying MIT checking for krb5-config... /usr/bin/krb5-config So binary files are differ: 1.8.0-4 support GSSAPI and 1.6.0-6 - does not support. -- With best wishes Max -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778566: unblock: node-serve-static/1.6.4-2
Tags: + confirmed Le 2015-02-16 20:14, Andrew Kelley a écrit : The package had a security vulnerability which was the bug that caused node-serve-static and its reverse dependencies to be marked as autoremove. This debdiff fixes that vulnerability without touching any other code. diff -Nru node-serve-static-1.6.4/debian/changelog node-serve-static-1.6.4/debian/changelog --- node-serve-static-1.6.4/debian/changelog 2014-10-15 15:52:21.0 + +++ node-serve-static-1.6.4/debian/changelog 2015-02-16 19:05:08.0 + @@ -1,3 +1,9 @@ +node-serve-static (1.6.4-2) UNRELEASED; urgency=medium ^^ Assuming you will replace UNRELEASED with a more sensible string, please go ahead and upload it to Unstable. Regards, -- Mehdi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778575: libparse-recdescent-perl: please enable reproducible builds
Source: libparse-recdescent-perl
Version: 1.967009+dfsg-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: toolchain randomness
Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=102160
Hi!
While working on Debian's “reproducible builds” effort [1], we have
noticed that libparse-recdescent-perl produces grammar files with
elements in random order, which results in other packages being
unreproducible.
The attached patch, which I have already forwarded upstream,
fixes this.
Regards,
Reiner
[1]: https://wiki.debian.org/ReproducibleBuilds
diff --git a/debian/patches/reproducible_grammar.patch b/debian/patches/reproducible_grammar.patch
new file mode 100644
index 000..3404321
--- /dev/null
+++ b/debian/patches/reproducible_grammar.patch
@@ -0,0 +1,25 @@
+Author: Reiner Herrmann rei...@reiner-h.de
+Description: produce reproducible grammar files
+Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=102160
+
+Index: libparse-recdescent-perl-1.967009+dfsg/lib/Parse/RecDescent.pm
+===
+--- libparse-recdescent-perl-1.967009+dfsg.orig/lib/Parse/RecDescent.pm
libparse-recdescent-perl-1.967009+dfsg/lib/Parse/RecDescent.pm
+@@ -144,6 +144,7 @@ sub Precompile
+ print OUT my ;
+
+ require Data::Dumper;
++$Data::Dumper::Sortkeys = 1;
+ $code = Data::Dumper-Dump([$self], [qw(self)]);
+ if ($opt{-standalone}) {
+ $code =~ s/Parse::RecDescent/$runtime_package/gs;
+@@ -3082,7 +3083,7 @@ local \$SIG{__WARN__} = sub {0};
+ $self-{startcode} = '';
+
+ my $rule;
+-foreach $rule ( values %{$self-{rules}} )
++foreach $rule ( sort { $a-{name} cmp $b-{name} } values %{$self-{rules}} )
+ {
+ if ($rule-{changed})
+ {
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 000..d2c4421
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+reproducible_grammar.patch
signature.asc
Description: OpenPGP digital signature
Bug#777042: unblock: suricata/2.0.6-1
On Wed, Feb 4, 2015 at 12:16:59 +0100, Arturo Borrero Gonzalez wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Dear release team, please unblock package suricata We were contacted privately regarding this release of libhtp/suricata which include important security updates (no CVE asigned though). We considered backporting just the important patches, but the changelog is rather small and we decided to package the new version directly. Before we upload 2.0.6-1 to unstable we would like to make sure that this is OK for you. Similar unblock exists for libhtp (#777040). The the debdiff, generated with this cmdline: debdiff suricata_2.0.4-1.dsc suricata_2.0.6-1.dsc | filterdiff -i '*.[ch] Note that the resulting debdiff was hand-modified to delete the libhtp code, which is included in upstream tarball but it has his own source package. It's large enough that I got bored midway through, but meh, if it breaks you keep both pieces; feel free to upload. Cheers, Julien signature.asc Description: Digital signature
Bug#778487: s3ql: Needs python-dugong = 3.4
On Feb 16 2015, Mika Pflüger deb...@mikapflueger.de wrote: Hi Nikolaus, Am Mon, 16 Feb 2015 09:42:57 -0800 schrieb Nikolaus Rath nikol...@rath.org: So please tighten the dependencies of s3ql 2.13 to require python3-dugong = 3.4 At least according to https://packages.debian.org/source/unstable/s3ql, this is exactly what the dependency is. That shows the dependencies of the s3ql source package (I guess that's [...] So I guess dh_python3 needs a pydist file or a py3dist-overrides file. Adding debian/s3ql.pydist with the contents dugong python3-dugong; PEP386 Gotcha. Thanks for doing all the debugging for me. It'll be fixed in the next release (I'd upload a fixed version right away if I could, but I don't want to bother my sponsor with too many minor uploads). Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.« signature.asc Description: PGP signature
Bug#778565: 215-12 does not set correct rights for hidraw devices (and others) anymore
Am 16.02.2015 um 23:02 schrieb Klaus Ethgen: Am Mo den 16. Feb 2015 um 21:46 schrieb Michael Biebl: Am 16.02.2015 um 19:50 schrieb Klaus Ethgen: Package: udev Version: 215-12 Severity: important After updating from 215-11 to 215-12, usb hidraw devices stopped to be accessable by plugdev group after reboot. I only checked that rights as this ist the most important for me but had also some other error messages after the reboot. So the system is only partial working after that update. The udev rules shipped by the udev package do not use the plugdev group *at all*. I fail to see why an update of udev should have changed anything in that regard. Well, it is in fact. Installing version 215-11 fixes the bug. And aside from that, the only udev related change in 215-12 was [1], which isn't relevant regarding hidraw devices. Well, then I suspect that there got something else into that package under the radar. Please run git bisect to find the commit then. -- 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#778388: ccache: scanner confused by comment signs in strings
Thanks. After seeing more of the code, I have been able to reproduce the problem. It's not only related to the code you added but also to the usage of '' further up in the code. See attachment for a reproduction script. The bug is not present in ccache 3.2 due to a rewrite of the relevant code. -- Joel On 16 February 2015 at 21:41, Oswald Buddenhagen oswald.buddenha...@gmx.de wrote: On Mon, Feb 16, 2015 at 09:26:02PM +0100, Joel Rosdahl wrote: Yes, a reduced testcase would be much appreciated. I don't have access to https://codereview.qt-project.org/105039 and I wouldn't know what to do anyway. :-) oh, right, it was a draft, invite only. fixed now. i think you'll figure it out easily. anyway, cloning the whole thing seems like overkill, indeed. you can just get the patched version of the file from the diff view. from there it is extracting the code into a minimal qt/qmake project. i expect this to be a somewhat time-consuming iterative process, so i'm not exactly in a hurry ... (BTW: You did clear the cache before you compiled the changed source code, right? Otherwise a cache hit is expected from the previous experiments, of course. Just checking.) i retried with multiple string and number variants i didn't use before, so this is of no concern. debian-bug-778388.sh Description: Bourne shell script
Bug#607543: Interested
Is this package still in need of a maintainer? I believe I have a sponsor and I am looking for a way to get my foot in the door to progress in Debian development/contribution. RapidSVN interests me and I have other interests with Node.js with regards to creating a web front end alternative to apache webdav. I would explore the RapidSVN API but it doesn't necessarily mean I will use it for said idea. My purpose for inquiry is that I'm interested in getting started in contributing to Debian. Please advise - *Rik*
Bug#776847: gsasl 1.8.0-6 does not support GSSAPI
Den Mon, 16 Feb 2015 22:51:26 +0100 skrev Re: Bug#776847: gsasl 1.8.0-6 does not support GSSAPI: On 16/02/15 22:13, Simon Josefsson wrote: It seems clear that the #745332 fix was incorrect. You can see in the build logs GSSAPI is not enabled since krb5-config isn't found: https://buildd.debian.org/status/fetch.php?pkg=gsaslarch=amd64ver=1.8.0-6stamp=1412611018 On considering solutions, I don't like the unpredictability in depending on libkrb5-dev|libheimdal-dev. The GSSAPI library used by the binary libgsasl package in Debian will depend on whether the buildds have Heimdal or MIT installed when you built the package. Coping with different GSS libraries on different architecture sounds like a recipe for disaster. For Jessie, gsasl should be built against the same Kerberos library on all architectures, unless there is a reason not to -- and I don't know of a reason. MIT is picked arbitrarily here. Cc'ing Jelmer (who reported 745332) and Andreas (who uploaded it) -- any comments? Jelmer, what prompted your initial report? The way I see it, it is important (for us) that you buildds don't have multiple Kerberos development packages installed when they build gsasl. So the old way was the preferred way, causing heimdal-dev to be removed and libkrb5-dev to be pulled in. People with other preferences who build their own packages can surely modify the gsasl package to their liking. I've pushed a fix in git and attmpted to upload to experimental, so you can test the new packages. The main reason for proposing this change was just to make it easier to have heimdal-dev installed while working on other parts of the system. At the moment, building gsasl requires uninstalling a number of packages for me, that indirectly depend on heimdal-dev. With the patch, the intent was to gsasl still build against MIT kerberos - e.g. no change in the binary packages. It merely changed the dependency from libkrb5-dev to libkrb5-multidev, the latter of which doesn't prevent heimdal-dev from being installed. Right -- but the patch also had the consequence of completely disabling GSSAPI in gsasl. Reverting the patch makes GSSAPI work again. Anyway, as you say, I can manually patch gsasl if I need to, and at the moment I don't work on any packages that depend on libgsasl-dev. I still think it would be nice to not have gsasl conflict with heimdal-dev, but it's not the end of the world if it doesn't. Maybe libkrb5-dev|heimdal-dev is a better build-dep -- but I don't know what holds for Debian buildds: are they allowed to have some packages pre-installed? If they can never have heimdal-dev installed (or for some other reason prefer heimdal-dev over libkrb5-dev), I don't see a problem using libkrb5-dev|heimdal-dev instead of libkrb5-dev. But if there are no guarantees, I prefer hard-coding libkrb5-dev to avoid linking with different Kerberos libraries depending on Debian architecture. Does anyone know? Btw, packages have hit experimental, if someone wants to test them. We can look at build logs to see if it enables GSSAPI or not. /Simon Cheers, Jelmer pgpSbqZz2UQGk.pgp Description: OpenPGP digital signatur
Bug#778568: unblock: node-findit2/2.2.3-2
Control: retitle -1 pre-approval: node-findit2/2.2.3-2 Le 2015-02-16 20:33, Andrew Kelley a écrit : Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package node-findit2 The package build-depends on node-tap, a buggy package. However, this dependency is strictly optional and is only used to run upstream tests. Further, there are many examples of Debian JavaScript packages which have tests disabled. Can you please elaborate on the node-tap is a buggy package part? I see that there is an RC-bug reported against it and its maintainer seems to think that it should be easy to fix. Are there any other issues? Did you try to contact node-tap's maintainer to see if/when he is willing to fix that RC-bug? Regards, -- Mehdi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777714: Acknowledgement (man-db crashes during post-install)
This bug can be closed, because it does not directly concern the man-db. Hangs during packages installation are caused by another problem, possibly related to VirtualBox. [720.119857] ca-certificates D c1657c44 0 5246 5244 0x [720.119862] f4903d94 0082 f5054ab0 c1657c44 0001 c170e280 c170e280 [720.119866] 007b f75de280 f5054ab0 c16571c0 c1254011 c1657540 [720.119871] f5fa1620 0001 bfede000 8000 bfedf000 f6980cf0 f4903d7c c10524ec [720.119876] Call Trace: [720.119882] [c1254011] ? radix_tree_lookup_slot+0x11/0x30 [720.119885] [c10524ec] ? __kunmap_atomic+0x5c/0x80 [720.119889] [c113b0bb] ? unmap_single_vma+0x44b/0x760 [720.119892] [c147a075] ? rwsem_down_write_failed+0x165/0x260 [720.119895] [c125acf2] ? call_rwsem_down_write_failed+0x6/0x8 [720.119898] [c1479ac5] ? down_write+0x25/0x40 [720.119901] [c1146f5b] ? unlink_anon_vmas+0x5b/0x160 [720.119904] [c113a971] ? free_pgtables+0x81/0xf0 [720.119906] [c1143862] ? exit_mmap+0x82/0x120 [720.119910] [c1054327] ? mmput+0x57/0xf0 [720.119913] [c1171a74] ? flush_old_exec+0x364/0x6d0 [720.119916] [c11afc6a] ? load_elf_binary+0x23a/0x11c0 [720.119919] [c1139141] ? kmap_high+0x21/0x1f0 [720.119922] [c1138daa] ? page_address+0xba/0xd0 [720.119925] [c1138ddf] ? kunmap_high+0x1f/0xb0 [720.119928] [c117120d] ? copy_strings+0x1fd/0x250 [720.119931] [c117138d] ? search_binary_handler+0x7d/0x1a0 [720.119934] [c117240e] ? do_execve_common+0x3fe/0x540 [720.119937] [c1172721] ? SyS_execve+0x21/0x30 [720.119940] [c147ae5f] ? sysenter_do_call+0x12/0x12 -- Best regards Lukasz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738897: Update
After looking through I see that 2.0 is released and actively maintained. Unless there is some reason to keep this package maintained I suppose I should retract my claim of interest. Sorry, looking for a package to adopt - or somewhere I can be helpful is quite an involved process it seems - so I've been jumping on things that seem promising - I apologize if I was too hasty. *Rik*
Bug#776701: ssd-test 1g file size too small
On 02/04/2015 02:10 AM, Martin Steigerwald wrote: Hello Daniel, hi Jens, Am Samstag, 31. Januar 2015, 14:23:34 schrieb Daniel Pocock: Package: fio Version: 2.1.11-2 Severity: important In the ssd-test sample config: https://sources.debian.net/src/fio/2.1.11-2/examples/ssd-test.fio/ The test size is 1GB, this line: size=1g There are SSDs that have 1g caches and this leads to unhelpful results. One user I discussed this with had to use a 10g test file to get consistent and meaningful results. Maybe bump the example to 10g or add a comment in front of that line. As the examples are taken from the upstream tarball, I suggest taking this upstream. I put upstream in Cc, Jens, what do you think about this? Sure, that sounds fine to me. 1G is tiny by todays standards, 10G would be a lot more reasonable. I'll commit that change. -- Jens Axboe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778565: 215-12 does not set correct rights for hidraw devices (and others) anymore
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Mo den 16. Feb 2015 um 21:46 schrieb Michael Biebl: Am 16.02.2015 um 19:50 schrieb Klaus Ethgen: Package: udev Version: 215-12 Severity: important After updating from 215-11 to 215-12, usb hidraw devices stopped to be accessable by plugdev group after reboot. I only checked that rights as this ist the most important for me but had also some other error messages after the reboot. So the system is only partial working after that update. The udev rules shipped by the udev package do not use the plugdev group *at all*. I fail to see why an update of udev should have changed anything in that regard. Well, it is in fact. Installing version 215-11 fixes the bug. And aside from that, the only udev related change in 215-12 was [1], which isn't relevant regarding hidraw devices. Well, then I suspect that there got something else into that package under the radar. I suspect that the problem you have lies elsewhere, but with the given information it's hard to tell. Then please tell me why the problem is gone when I go back to 215-11 without changing anything else? I believe that it is not that easy to find. But it is clearly udev update that triggered the issue. The point where I seen that directly is using solaar to look/configure my logitech mouse. There is a special rule that comes with it, /lib/udev/rules.d/60-solaar.rules, that is not working after the update. And even more. There was many desktop notifications about late detected devices. It was too many to see all of them. I believe that there is something really strange happen with this update. Regards Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen kl...@ethgen.de Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQGcBAEBCgAGBQJU4mkJAAoJEKZ8CrGAGfasSKEL/1ZFBd/IEWyVHWN6D+KHvByU BG3sQwe32gwzFSiynN5kLg31gL8CcWh6+T4La9xOOIGb7xl1cn9P7mJsjxaaMVS0 YG5KRZw8rT1314pSaf2c3UkQti0ezLHXS9+3Rq2VFaZIfC51xgTVd94v7wEYziqf nHKjdQ/f+P/7u3NvOsKFdpj49NNOxy1slxLDwCg7FY9Xby7jxSHSrAO4+gzHq4En fOnLQnfhAGSILUrSNU9rKWBYypi/TMpQjKJ4DhAS2dlnS5IvGMwZ6w7Ib8hNU/zl 1jcdfHTpFWsJpldZfMCrtTMeMbL9PqLbAg3rBXq8+x84oQAHPuOh3ttvWrcsVpd0 o142LLDekAGSpjQSG3fP4ya2okEY/lTnLgKWRHX7t0jujreQpzpD8Hg260fg55dd siWETB3qi1LF6LYLklx6PjZtqm4KjE6tHR4awv5ir8yUbodpP/fAUx2iLHIBMKew WAuWSdQc9+FTR/7gDEeHDwWSwYwVCs/0wilsnrkavA== =v3EC -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769155: kde-workspace-bin: laptop does not go to sleep when critical battery level is reached
Package: kde-workspace-bin Version: 4:4.11.13-2 Followup-For: Bug #769155 Dear Maintainer, Confirming this bug with version 4.11.13-2. I tested booting with linux-image-3.2.0-4-amd64 (3.2.65-1+deb7u1) and the laptop has gone to hibernate when passing the critical level, so I think is related with kernel behaviour. Thank you. Felipe Sologuren -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (600, 'testing'), (500, 'testing-updates'), (500, 'stable-updates'), (500, 'stable'), (100, 'unstable'), (40, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=es_CL.UTF-8, LC_CTYPE=es_CL.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to es_CL.UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages kde-workspace-bin depends on: ii iso-codes 3.57-1 ii kde-runtime 4:4.14.2-2 ii kde-style-oxygen 4:4.11.13-2 ii kde-workspace-data4:4.11.13-2 ii kde-workspace-kgreet-plugins 4:4.11.13-2 ii kscreen 1.0.2.1-1 ii libc6 2.19-13 ii libcln6 1.3.4-1 ii libdbusmenu-qt2 0.9.2-1 ii libfontconfig12.11.0-6.3 ii libfreetype6 2.5.2-2 ii libgcc1 1:4.9.1-19 ii libgl1-mesa-glx [libgl1] 10.3.2-1 ii libice6 2:1.0.9-1+b1 ii libjpeg62-turbo 1:1.3.1-11 ii libkactivities6 4:4.13.3-1 ii libkcmutils4 4:4.14.2-5 ii libkdeclarative5 4:4.14.2-5 ii libkdecore5 4:4.14.2-5 ii libkdesu5 4:4.14.2-5 ii libkdeui5 4:4.14.2-5 ii libkfile4 4:4.14.2-5 ii libkidletime4 4:4.14.2-5 ii libkio5 4:4.14.2-5 ii libknewstuff3-4 4:4.14.2-5 ii libknotifyconfig4 4:4.14.2-5 ii libkparts44:4.14.2-5 ii libkpty4 4:4.14.2-5 ii libkscreensaver5 4:4.11.13-2 ii libkworkspace4abi24:4.11.13-2 ii libnepomukcore4 4:4.14.0-1+b2 ii libpam0g 1.1.8-3.1 ii libphonon44:4.8.0-4 ii libplasma34:4.14.2-5 ii libplasmagenericshell44:4.11.13-2 ii libpng12-01.2.50-2+b2 ii libprocesscore4abi1 4:4.11.13-2 ii libprocessui4a4:4.11.13-2 ii libqalculate5 0.9.7-9 ii libqimageblitz4 1:0.0.6-4 ii libqjson0 0.8.1-3 ii libqt4-dbus 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-declarative4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-sql4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-xml4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libsm62:1.2.2-1+b1 ii libsolid4 4:4.14.2-5 ii libsoprano4 2.9.4+dfsg-1.1 ii libstdc++64.9.1-19 ii libstreamanalyzer00.7.8-1.2+b2 ii libudev1 215-11 ii libusb-0.1-4 2:0.1.12-25 ii libx11-6 2:1.6.2-3 ii libxcursor1 1:1.1.14-1+b1 ii libxext6 2:1.3.3-1 ii libxfixes31:5.0.1-2+b2 ii libxft2 2.3.2-1 ii libxi62:1.7.4-1+b2 ii libxinerama1 2:1.1.3-1+b1 ii libxkbfile1 1:1.0.8-1 ii libxrandr22:1.4.2-1+b1 ii libxrender1 1:0.9.8-1+b1 ii libxtst6 2:1.2.2-1+b1 ii phonon4:4.8.0-4 ii plasma-desktop4:4.11.13-2 ii qdbus 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii x11-utils 7.7+2 ii x11-xserver-utils 7.7+3+b1 Versions of packages kde-workspace-bin recommends: ii plasma-scriptengines 4:4.11.13-2 ii policykit-1-gnome 0.105-2 ii polkit-kde-1 0.99.1-1 ii upower0.99.1-3.1 Versions of packages kde-workspace-bin suggests: ii x11-xkb-utils 7.7+1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778574: planetfilter: Log output to /var/log/planetfilter.log
Package: planetfilter Version: 0.2.0-1 Severity: wishlist Because we swallow all non-error cron output using chronic, there should be a (log-rotated) logfile that admins can take a look at if they want to see more info about what the package is doing. We could modify the cronjob to make use of the ts command (part of moreutils) to timestamp each message coming out of the main binary. The tricky part here is that we want: - the cronjob to hide all output when planetfilter zero exit code - the cronjob to show all output in case of a non-zero exit code - the log file to have all output, regardless of the exit code We may not be able to use chronic anymore. If anybody has ideas on how to do the above, please chime in. Francois -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776847: gsasl 1.8.0-6 does not support GSSAPI
On 16/02/15 22:13, Simon Josefsson wrote: It seems clear that the #745332 fix was incorrect. You can see in the build logs GSSAPI is not enabled since krb5-config isn't found: https://buildd.debian.org/status/fetch.php?pkg=gsaslarch=amd64ver=1.8.0-6stamp=1412611018 On considering solutions, I don't like the unpredictability in depending on libkrb5-dev|libheimdal-dev. The GSSAPI library used by the binary libgsasl package in Debian will depend on whether the buildds have Heimdal or MIT installed when you built the package. Coping with different GSS libraries on different architecture sounds like a recipe for disaster. For Jessie, gsasl should be built against the same Kerberos library on all architectures, unless there is a reason not to -- and I don't know of a reason. MIT is picked arbitrarily here. Cc'ing Jelmer (who reported 745332) and Andreas (who uploaded it) -- any comments? Jelmer, what prompted your initial report? The way I see it, it is important (for us) that you buildds don't have multiple Kerberos development packages installed when they build gsasl. So the old way was the preferred way, causing heimdal-dev to be removed and libkrb5-dev to be pulled in. People with other preferences who build their own packages can surely modify the gsasl package to their liking. I've pushed a fix in git and attmpted to upload to experimental, so you can test the new packages. The main reason for proposing this change was just to make it easier to have heimdal-dev installed while working on other parts of the system. At the moment, building gsasl requires uninstalling a number of packages for me, that indirectly depend on heimdal-dev. With the patch, the intent was to gsasl still build against MIT kerberos - e.g. no change in the binary packages. It merely changed the dependency from libkrb5-dev to libkrb5-multidev, the latter of which doesn't prevent heimdal-dev from being installed. Anyway, as you say, I can manually patch gsasl if I need to, and at the moment I don't work on any packages that depend on libgsasl-dev. I still think it would be nice to not have gsasl conflict with heimdal-dev, but it's not the end of the world if it doesn't. Cheers, Jelmer signature.asc Description: OpenPGP digital signature
Bug#778190: fixed-upstream
tags 778190 +fixed-upstream thanks https://github.com/yade/trunk/commit/459085df5e3bdab39aae879d65a6e8198249ebf4 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778190: fixed-upstream
tags 778190 +pending thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778576: unblock: node-tap/0.4.13-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package node-tap
The bug that caused this package to be scheduled for autoremoval is
fixed with this small patch which disables a single test.
This does not affect the behavior of the package itself in any way.
diff -Nru node-tap-0.4.13/debian/changelog node-tap-0.4.13/debian/changelog
--- node-tap-0.4.13/debian/changelog2014-10-20 00:01:44.0 +
+++ node-tap-0.4.13/debian/changelog2015-02-16 22:53:56.0 +
@@ -1,3 +1,9 @@
+node-tap (0.4.13-2) unstable; urgency=medium
+
+ * Patch fixing failing test FTBFS (Closes: #775627)
+
+ -- Jérémy Lal kapo...@melix.org Mon, 16 Feb 2015 23:52:37 +0100
+
node-tap (0.4.13-1) unstable; urgency=low
* Initial release (Closes: #765988)
diff -Nru node-tap-0.4.13/debian/patches/mitigate_test_segv.patch
node-tap-0.4.13/debian/patches/mitigate_test_segv.patch
--- node-tap-0.4.13/debian/patches/mitigate_test_segv.patch 1970-01-01
00:00:00.0 +
+++ node-tap-0.4.13/debian/patches/mitigate_test_segv.patch 2015-02-16
22:53:00.0 +
@@ -0,0 +1,30 @@
+Description: exit code of segv test depend on platform - do not check it
+ For reasons yet to be discovered, the assumption in segv test is wrong on
+ the platform used for https://bugs.debian.org/775627.
+Last-Update: 2015-02-16
+Author: Jérémy Lal kapo...@melix.org
+Forwarded: no, need more info
+--- a/test/segv.js
b/test/segv.js
+@@ -37,9 +37,7 @@
+ , { 'id': 1,
+ 'ok': false,
+ 'name': ' ././segv',
+- 'exit': null,
+ 'timedOut': true,
+- 'signal': process.platform === 'linux' ? 'SIGSEGV' : 'SIGTERM',
+ 'command': './segv' }
+ , 'tests 1'
+ , 'fail 1' ]
+@@ -47,11 +45,6 @@
+ tc.on('data', function (d) {
+ var e = expect.shift()
+
+-// specific signal can be either term or bus
+-if (d.signal e.signal)
+- e.signal = d.signal === SIGTERM || d.signal === SIGBUS ?
+-d.signal : e.signal
+-
+ t.same(d, e)
+ })
+ tc.on('end', function () {
diff -Nru node-tap-0.4.13/debian/patches/series
node-tap-0.4.13/debian/patches/series
--- node-tap-0.4.13/debian/patches/series 2014-10-20 00:01:40.0
+
+++ node-tap-0.4.13/debian/patches/series 2015-02-16 22:53:00.0
+
@@ -1,3 +1,4 @@
nodejs_rename.patch
use_available_modules.patch
sbuild_disable_tests.patch
+mitigate_test_segv.patch
unblock node-tap/0.4.13-2
-- System Information:
Debian Release: 8.0
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=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#778546: RFS: miceamaze/4.2-1 -- video game with mice in a maze
Control: tags -1 + moreinfo
On Mon, Feb 16, 2015 at 10:38 PM, Raphaël Champeimont wrote:
miceamaze - video game with mice in a maze
There is one issue that need to be fixed before I will upload the package:
The debian/copyright file needs to be updated for the new copyright
year. It also needs updating for the new files that are under
different licenses or have different copyright holders (data/music/
and data/mazes/maze13.txt). Please note that a full copy of the CC-BY
3.0 license needs to be added to debian/copyright, so offline users
can read the license.
Other thoughts:
On a system with two screens (laptop + external screen), full-screen
mode crosses the two screens which makes the menu hard to read and
cuts part of it off.
In chromium-bsu I was able to get nice anti-aliased text by passing
GLC_TEXTURE to glcRenderStyle, but for some reason that only produces
white squares in miceamaze.
You might want to mention the Standards-Version in debian/changelog.
If you have gone through the upgrading checklist and there aren't any
changes that apply to miceamaze, you can say just Bump
Standards-Version, no changes needed.
http://www.debian.org/doc/debian-policy/upgrading-checklist
You might want to mention the reason for the Priority change in
debian/changelog.
I would have indented the second debian/changelog item like this:
* New upstram release 4.2 (Closes: #766820)
- Removed creation timestamp in PNG generation (Closes: #778491)
ttf-dejavu-core is a transitional dummy package, you could depend on
fonts-dejavu-core | ttf-dejavu-core instead.
You may want to work on porting the code to SDL2. chromium-bsu is an
example of a game that supports SDL and SDL2 (in upstream git only).
The debian/patches directory is empty and could be removed.
There are two spelling errors:
$ codespell --quiet-level=3
./src/Functions.h:149: occured == occurred
./src/AIVertex.h:33: colum == column
The include-what-you-use tool (from the iwyu Debian package) suggests
a lot of files that are missing headers for the variables and
functions that they use. I ran this command:
$ find -type f \( -iname '*.c' -o -iname '*.cc' -o -iname '*.cxx' -o
-iname '*.cpp' -o -iname '*.h' -o -iname '*.hh' -o -iname '*.hxx' -o
-iname '*.hpp' \) -exec include-what-you-use {} \;
I would suggest renaming the upstream README.txt file to INSTALL.txt.
The upstream LICENSE.txt still contains details about the
Bitstream/DejaVu license even though that was removed from the source
tarball.
The upstream LICENSE.txt is missing copyright/license info for
maze13.txt, which appears to have been contributed by someone else?
This is a better URL for the Ogg file from ccmixter, I found it in the
metadata of the Ogg file:
http://ccmixter.org/files/George_Ellinas/14073-
The upstream ChangeLog.txt is missing information about versions from
2.1 to 4.2.
You've changed the mouse image and introduced 2 modified copies of it.
This could be problematic if you want to tweak the mouse image or use
different modifications in the future. Personally I would have done it
like this: mouse.png containing the normal mouse image, helmet.png
containing the mouse helmet and sickness.png containing the sickness
pattern. Then at build time you would use imagemagick to overlay the
helmet on the mouse image to create drill_mouse.png and similarly to
create sick_mouse.png. Using SVG for the mouse image would give you
more options for modifying the mouse too.
The Ogg files aren't very modifiable, for example you could not easily
change the drums to different drum or to a sample of someone hitting
two rocks together.
lintian complaints:
P: miceamaze source: debian-watch-may-check-gpg-signature
I: miceamaze: arch-dep-package-has-big-usr-share 12285kB 98%
For the first one, refer to these URLs:
https://lintian.debian.org/tags/debian-watch-may-check-gpg-signature.html
https://wiki.debian.org/debian/watch#Cryptographic_signature_verification
https://help.riseup.net/security/message-security/openpgp/best-practices
For the second one, refer to these URLs:
https://lintian.debian.org/tags/arch-dep-package-has-big-usr-share.html
As you are upstream for a game, you may want to look at these:
https://wiki.debian.org/UpstreamGuide
http://www.freedesktop.org/wiki/Games/Upstream/
--
bye,
pabs
https://wiki.debian.org/PaulWise
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755722: systemd must sync systemclock to RTC on shutdown
On Tue, Feb 17, 2015 at 06:44:28AM +0100, Martin Pitt wrote: Josh Triplett [2015-02-16 17:37 -0800]: Seems like systemd could take a lesson from Debian packaging metadata here. Every mail transport agent, rather than conflicting with every other, has a Provides: mail-transport-agent and Conflicts: mail-transport-agent, specifically because they all want to provide /usr/sbin/sendmail and (usually) listen on port 25. Note that openntpd and chrony both have a Provides: time-daemon, but ntp doesn't. Interesting. Any idea why? Unit files could do something similar, if systemd had an appropriate virtual service mechanism. It does, it's called Alias= (man systemd.unit). Can Alias work together with Conflicts on that alias, such that each of several services all Alias a given virtual service and Conflicts with other providers of that service? If so, what about using that for systemd-timesyncd and all of the other time services, at least once they all have native service files? We use it for display-manager already (kind of, as we also have to support the old /etc/X11/default-display-manager config file). Also, post-jessie, do you have any plans to do a one-time migration away from that display manager configuration file, similar to the various one-time migrations away from sysvinit-specific config files like /etc/default/rcS? - Josh Triplett -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#80123: Interested
Hello, I'm a newbie to debian development, looking to find a spot to settle and start contributing. The requested feature I believe I can do with some investigation of the code and time to get familiar - so not sure if I should go ahead and try or if I might want to stay away from this particular request? However, I'm also very interested in the plugin API you have stated would be a good idea. I'd be interested to help with that - especially if you guys would consider a more modern and universal approach (such as JS rather than LUA). Please let me know - I have experience with v8 more specifically ...also with LUA and with building LUA plug-in systems (though mostly for games). Please keep in mind all of my extravagant ranting above is pre-looking-at-any-code. I'm just basing my input on the *.cc reference above. Best, *Richard B. Winters*
Bug#755722: systemd must sync systemclock to RTC on shutdown
Josh Triplett [2015-02-16 21:49 -0800]: Note that openntpd and chrony both have a Provides: time-daemon, but ntp doesn't. Interesting. Any idea why? No, I don't; probably just an omission. openntpd and chrony both have an explicit Conflicts: ntp, though. It does, it's called Alias= (man systemd.unit). Can Alias work together with Conflicts on that alias, such that each of several services all Alias a given virtual service and Conflicts with other providers of that service? If so, what about using that for systemd-timesyncd and all of the other time services, at least once they all have native service files? That's certainly the idea, yes. The Alias= mechanism works a bit differently than Provides: on a packaging level; e. g. it must be possible to have several of them installed in parallel. So AFAIK packages which use this schema need to either systemctl disable aliasname first (if they want to set itself as the selected alternative) or not enable itself at all (if they are not the selected alternative). We use it for display-manager already (kind of, as we also have to support the old /etc/X11/default-display-manager config file). Also, post-jessie, do you have any plans to do a one-time migration away from that display manager configuration file, similar to the various one-time migrations away from sysvinit-specific config files like /etc/default/rcS? I wish we could. But don't forget that we still have to support at least SysVinit and perpaps even more (openrc? upstart?). As long as we have those, we probably have to keep these uber-complex mechanisms like systemd-default-display-manager-generator which sync these config files with the systemd unit enablement. 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#755722: systemd must sync systemclock to RTC on shutdown
On Tue, Feb 17, 2015 at 06:59:15AM +0100, Martin Pitt wrote: Josh Triplett [2015-02-16 21:49 -0800]: It does, it's called Alias= (man systemd.unit). Can Alias work together with Conflicts on that alias, such that each of several services all Alias a given virtual service and Conflicts with other providers of that service? If so, what about using that for systemd-timesyncd and all of the other time services, at least once they all have native service files? That's certainly the idea, yes. The Alias= mechanism works a bit differently than Provides: on a packaging level; e. g. it must be possible to have several of them installed in parallel. So AFAIK packages which use this schema need to either systemctl disable aliasname first (if they want to set itself as the selected alternative) or not enable itself at all (if they are not the selected alternative). With a bit of machinery tied into the alternatives mechanism, perhaps which of several concurrently installed units are enabled could be more easily admin-controllable? We use it for display-manager already (kind of, as we also have to support the old /etc/X11/default-display-manager config file). Also, post-jessie, do you have any plans to do a one-time migration away from that display manager configuration file, similar to the various one-time migrations away from sysvinit-specific config files like /etc/default/rcS? I wish we could. But don't forget that we still have to support at least SysVinit and perpaps even more (openrc? upstart?). As long as we have those, we probably have to keep these uber-complex mechanisms like systemd-default-display-manager-generator which sync these config files with the systemd unit enablement. Just because we support other init systems, and migrate user configuration from those init systems, doesn't necessarily mean the configuration files have to remain the *same*. It'd be easy enough to do a one-time migration of the current value in /etc/X11/default-display-manager to the set of enabled .service files for display managers, and let the user know that future changes to that file will not have any further effect. Similarly, the current setting in /etc/default/tmpfs for whether to mount a tmpfs on /tmp gets migrated to /etc/systemd/system/local-fs.target.wants/tmp.mount , but future changes to /etc/default/tmpfs have no effect, and that file will one day go away when systemd no longer depends on initscripts. (I also have hopes that one day, the sysvinit unit generator can live in a separate package that systemd just Suggests but does not Depends on.) - Josh Triplett -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778593: [PATCH] bootcd: Update Burning the image Section in FAQ
Source: bootcd Source-Version: 4.05 Tags: patch Dear Maintainer, it looks like the Burning the image section in FAQ.bootcd is outdated. In the example I have replaced the tool cdrecord by wodim. Kind regards, Kai Harries --- Index: bootcd-4.05/FAQ.bootcd === --- bootcd-4.05/FAQ.bootcd +++ bootcd-4.05/FAQ.bootcd @@ -164,15 +164,10 @@ 3. Burning the image or creating a liveusbstick 3.1 Q: How can I burn the image ? -A: For cdrom install cdrecord and see man cdrecord(1). Example - cdrecord -scanbus - cdrecord dev=0,2,0 -v -eject blank=fast - cdrecord dev=0,2,0 -v -eject /var/spool/bootcd/cdimage.iso - For dvd install package dvd+rw-tools and see man growisofs(1m). Example: - dvd+rw-format /dev/dvd - growisofs -dvd-compat -Z /dev/dvd=/var/spool/bootcd/cdimage.iso +A: Install wodim and see man wodim(1). Example + wodim -v -eject /var/spool/bootcd/cdimage.iso 3.2 Q: How can I create a floppy ? A: If you need to boot from floppy and to save changes made in ram you can -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777647: partman-efi always complains when installing from usb
On Wed, Feb 11, 2015 at 01:10:02PM -0500, Phillip Susi wrote: On 02/11/2015 11:47 AM, Steve McIntyre wrote: Quite, that's exactly how it's meant to work and it's what I've seen in my development and testing. Silly question - is ubiquity trying to run some of the d-i bits in parallel, or something? That's what I was wondering. I'm looking at /var/log/partman now and it appears that visual.d/35name runs and then I see /bin/perform_recipie issue a NEW_PARTITION command to make the ext2 partition ( which will later be formatted as fat32 for the esp ), and then the ext4 partition for the root and then swap. Later init.d/50efi runs and sees the partition that the earlier script created even though it has not actually been committed to disk yet ( i.e. blkid still sees a blank disk ). Did we change the ordering in ubuntu or something so that the problem is that visual.d has priority 35 but init.d/efi has priority 50 when they should run the other order? I would think that all of the init.d scripts would be run before any visual.d scripts though, and the priorities just order them within their group. If that's not the case then I guess they simply have the wrong priority. Hi Phillip! [ technically I'm on VAC, but my wife's not watching... *grin* ] Any futher clues on this at all? I have next to no knowledge about how the Ubuntu installer code uses the d-i packages, which makes it difficult for me to comment much more. -- Steve McIntyre, Cambridge, UK.st...@einval.com I've only once written 'SQL is my bitch' in a comment. But that code is in use on a military site... -- Simon Booth -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768352: gsasl: Does not support GSSAPI.
Hi. Thanks for the report. It seems related to this report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776847 /Simon pgp4mL89Z9DCa.pgp Description: OpenPGP digital signatur
Bug#778573: xorg: Xorg shows blank black screen at startup instead of a Display Manager.
Package: xorg Version: 1:7.7+3~deb7u1 Dear Maintainer, * What led up to the situation? A system update which included an update for xorg * What exactly did you do (or not do) that was effective (or ineffective)? I attempted to switch to a different Display Manager. * What was the outcome of this action? Nothing changed. * What outcome did you expect instead? I hoped that the problem was with gdm3. -- System Information: Debian Release: 7.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xorg depends on: ii gnome-terminal [x-terminal-emulator] 3.4.1.1-2 ii konsole [x-terminal-emulator] 4:4.8.4-2 ii libgl1-mesa-dri 8.0.5-4+deb7u2 ii libgl1-mesa-glx [libgl1] 8.0.5-4+deb7u2 ii libglu1-mesa 8.0.5-4+deb7u2 ii lxterminal [x-terminal-emulator] 0.1.11-4 pn x11-apps none pn x11-session-utils none ii x11-utils 7.7~1 pn x11-xfs-utils none ii x11-xkb-utils 7.7~1 ii x11-xserver-utils 7.7~3 ii xauth 1:1.0.7-1 ii xfonts-100dpi 1:1.0.3 ii xfonts-75dpi 1:1.0.3 ii xfonts-base 1:1.0.3 ii xfonts-scalable 1:1.0.3-1 ii xfonts-utils 1:7.7~1 pn xinit none ii xkb-data 2.5.1-3 ii xorg-docs-core1:1.6-1 ii xserver-xorg 1:7.7+3~deb7u1 ii xterm [x-terminal-emulator] 278-4 xorg recommends no packages. Versions of packages xorg suggests: pn xorg-docs none Versions of packages xserver-xorg depends on: ii libc6 2.13-38+deb7u7 ii x11-xkb-utils 7.7~1 ii xkb-data 2.5.1-3 ii xserver-xorg-core 2:1.12.4-6+deb7u6 ii xserver-xorg-input-all1:7.7+3~deb7u1 ii xserver-xorg-input-evdev [xorg-driver-input] 1:2.7.0-1+b1 ii xserver-xorg-input-mouse [xorg-driver-input] 1:1.7.2-3 ii xserver-xorg-input-synaptics [xorg-driver-input] 1.6.2-2 ii xserver-xorg-input-vmmouse [xorg-driver-input]1:12.9.0-1 ii xserver-xorg-input-wacom [xorg-driver-input] 0.15.0+20120515-2 ii xserver-xorg-video-all1:7.7+3~deb7u1 ii xserver-xorg-video-apm [xorg-driver-video]1:1.2.3-3 ii xserver-xorg-video-ark [xorg-driver-video]1:0.7.4-1+b1 ii xserver-xorg-video-ati [xorg-driver-video]1:6.14.4-8 ii xserver-xorg-video-chips [xorg-driver-video] 1:1.2.4-2 ii xserver-xorg-video-cirrus [xorg-driver-video] 1:1.4.0-2 ii xserver-xorg-video-fbdev [xorg-driver-video] 1:0.4.2-4+b3 ii xserver-xorg-video-i128 [xorg-driver-video] 1:1.3.5-1+b1 ii xserver-xorg-video-intel [xorg-driver-video] 2:2.19.0-6 ii xserver-xorg-video-mach64 [xorg-driver-video] 6.9.1-2 ii xserver-xorg-video-mga [xorg-driver-video]1:1.5.0-3 ii xserver-xorg-video-neomagic [xorg-driver-video] 1:1.2.6-1 ii xserver-xorg-video-nouveau [xorg-driver-video]1:1.0.1-5 ii xserver-xorg-video-openchrome [xorg-driver-video] 1:0.2.906-2+deb7u1 ii xserver-xorg-video-r128 [xorg-driver-video] 6.8.2-1 ii xserver-xorg-video-radeon [xorg-driver-video] 1:6.14.4-8 ii xserver-xorg-video-rendition [xorg-driver-video] 1:4.2.4-3 ii xserver-xorg-video-s3 [xorg-driver-video] 1:0.6.3-5 ii xserver-xorg-video-s3virge [xorg-driver-video]1:1.10.4-5 ii xserver-xorg-video-savage [xorg-driver-video] 1:2.3.4-1 ii xserver-xorg-video-siliconmotion [xorg-driver-video] 1:1.7.6-1 ii xserver-xorg-video-sis [xorg-driver-video]1:0.10.4-1 ii xserver-xorg-video-sisusb [xorg-driver-video] 1:0.9.4-3 ii xserver-xorg-video-tdfx [xorg-driver-video] 1:1.4.4-1 ii xserver-xorg-video-trident [xorg-driver-video]1:1.3.5-1 ii xserver-xorg-video-tseng [xorg-driver-video] 1:1.2.4-3 ii xserver-xorg-video-vesa [xorg-driver-video] 1:2.3.1-1+b1 ii xserver-xorg-video-vmware [xorg-driver-video] 1:12.0.2-1+b1 ii xserver-xorg-video-voodoo [xorg-driver-video] 1:1.2.4-2+b3 Versions of packages xserver-xorg recommends: ii libgl1-mesa-dri 8.0.5-4+deb7u2
Bug#549551:
Hello, looks like the xscreensaver violates UNIX philosophy : do one thing and do it well. There is dozen of other applicasions taking care of powermanagement, not just DPMS: display brightness, HDD spindown... It seems that perfection is attained not when there is nothing more to add, but when there is nothing more to remove. please kill the DPMS handling, or at least allow us to disable it. -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Fucking windows! Bring Bill Gates! (Southpark the movie) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777540: The libhtp SONAME mismatch *is* a policy violation.
* Julien Cristau: 1. Override upstream's decision to change the SONAME with every release. I am not entirelysure how stable libhtp's API/ABI should be considered -- looking at changes and deciding on compatibility issues making those decisions would certainly put a burden on the maintainer in the future (although the .symbols mechanism helps for obvious cases such as removed APIs.) I am attaching a patch to drop the -release parameter from the libtool call, libhtp.so.1.0.0 (instead of libhtp-0.5.15.so.1.0.0) is generated. The .symbols file would need to be updated to reflect that change, too, of course. 2. Since suricata is the only reverse dependency of libhtp and contains a copy of libhtp within its source tarball, so we could drop the libhtp package altogether and use that embedded copy instead, at least for the jessie release. 3. Change the binary package name to reflect the SONAME -- for instance libhtp-0.5.15. I believe that we are too late in the freeze to be adding new binary package names. For jessie, 2 sounds like the best way to go IMO. Thank you. Could somebody please decide about #777042 (unblock: suricata/2.0.6-1)? A positive answer, together with the decision to use the copy of the libhtp sources shipped as part of suricata for jessie, would also take care of #777040 (unblock: libhtp/0.5.16-1), as well as security issues #774897, #777522, and #777523. Cheers, -Hilko -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778445: My mistake on MilterSocketMode
Great, thanks a lot for the quick work! :) My bad on MilterSocketMode, I must have been going back and forth for testing, so the error slipped in on my side. Best regards -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776839: unblock: libgit2/0.21.3-1.1
Tags: + confirmed On Thu, Feb 12, 2015 at 09:49:34PM +1100, Russell Sim russell@gmail.com wrote: On 11 February 2015 at 23:24, Russell Sim russell@gmail.com wrote: On 9 February 2015 at 09:36, Mehdi Dogguy me...@dogguy.org wrote: I'm afraid we cannot accept 0.21.3-1.1 in Jessie because the changes are quite large. Can you please prepare an upload targetting jessie based on 0.21.1-2.1? Thanks for looking at this. I have created a patch that backport the relevant changes to the 0.21.1-2.1 I have reduced the patch removing any Win32 parts. Thanks for your work and sorry for not getting back to you sooner. The patch looks okay. Please go ahead and upload 0.21.1-3 to Jessie and notify us as soon as it gets accepted. Cheers. -- Mehdi Dogguy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778596: php5-gd: imageantialias is still missing
Package: php5-gd
Version: 5.6.5+dfsg-1
Severity: normal
Dear Maintainer,
Quite some time ago bug #321237 was posted, noting that php5-gd used by Debian
has missing some funtions.
There is a comment (#71) stating that There is also an ongoing work,
and since Jessie is comming, I have checked if previosly missing
imageantialias() is maybe already implemented, but sadly:
$ php -r var_dump(function_exists('imageantialias'));
bool(false)
I have asked about imageantialias() progress in libgd bug tracker:
https://bitbucket.org/libgd/gd-libgd/issue/115/backports-php-internal-functions-to-libgd#comment-13551981
but with no response.
Is there any hope, any possibility to encourage, motivate libgd developers to
have it fixed since Jessie is out? Or it is already too late (because of freeze)
and we will have to recompile php with bundeled libgd for another 2-3 years..?
-- Package-specific info:
Additional PHP 5 information
PHP 5 SAPI (php5query -S):
apache2
cli
PHP 5 Extensions (php5query -M -v):
readline (Enabled for apache2 by maintainer script)
readline (Enabled for cli by maintainer script)
json (Enabled for apache2 by maintainer script)
json (Enabled for cli by maintainer script)
opcache (Enabled for apache2 by maintainer script)
opcache (Enabled for cli by maintainer script)
gd (Enabled for apache2 by maintainer script)
gd (Enabled for cli by maintainer script)
pdo (Enabled for apache2 by maintainer script)
pdo (Enabled for cli by maintainer script)
Configuration files:
/etc/php5/mods-available/gd.ini
extension=gd.so
-- System Information:
Debian Release: 8.0
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=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 php5-gd depends on:
ii libc6 2.19-13
ii libfreetype6 2.5.2-2
ii libgd3 2.1.0-5
ii libjpeg62-turbo1:1.3.1-11
ii libpng12-0 1.2.50-2+b2
ii libvpx11.3.0-3
ii libx11-6 2:1.6.2-3
ii libxpm41:3.5.11-1+b1
ii php5-common [phpapi-20131226] 5.6.5+dfsg-1
ii ucf3.0030
ii zlib1g 1:1.2.8.dfsg-2+b1
php5-gd recommends no packages.
php5-gd suggests no packages.
Versions of packages php5-common depends on:
ii libc6 2.19-13
ii lsof4.86+dfsg-1
ii psmisc 22.21-2
ii sed 4.2.2-4+b1
ii ucf 3.0030
Versions of packages php5-common suggests:
pn php5-user-cache none
Versions of packages php5-cli depends on:
ii libbz2-1.01.0.6-7+b2
ii libc6 2.19-13
ii libcomerr21.42.12-1
ii libdb5.3 5.3.28-7~deb8u1
ii libedit2 3.1-20140620-2
ii libgssapi-krb5-2 1.12.1+dfsg-17
ii libk5crypto3 1.12.1+dfsg-17
ii libkrb5-3 1.12.1+dfsg-17
ii libmagic1 1:5.20-2
ii libonig2 5.9.5-3.2
ii libpcre3 2:8.35-3.3
ii libqdbm14 1.8.78-5+b1
ii libssl1.0.0 1.0.1k-1
ii libxml2 2.9.1+dfsg1-4
ii mime-support 3.58
ii php5-common 5.6.5+dfsg-1
ii php5-json 1.3.6-1
ii tzdata2015a-1
ii ucf 3.0030
ii zlib1g1:1.2.8.dfsg-2+b1
Versions of packages php5-cli recommends:
ii php5-readline 5.6.5+dfsg-1
Versions of packages php5-cli suggests:
pn php-pear none
Versions of packages libapache2-mod-php5 depends on:
ii apache2 2.4.10-9
ii apache2-bin [apache2-api-20120211] 2.4.10-9
ii libbz2-1.0 1.0.6-7+b2
ii libc6 2.19-13
ii libcomerr2 1.42.12-1
ii libdb5.35.3.28-7~deb8u1
ii libgssapi-krb5-21.12.1+dfsg-17
ii libk5crypto31.12.1+dfsg-17
ii libkrb5-3 1.12.1+dfsg-17
ii libmagic1 1:5.20-2
ii libonig25.9.5-3.2
ii libpcre32:8.35-3.3
ii libqdbm14 1.8.78-5+b1
ii libssl1.0.0 1.0.1k-1
ii libstdc++6 4.9.1-19
ii libxml2 2.9.1+dfsg1-4
ii mime-support3.58
ii php5-cli5.6.5+dfsg-1
ii php5-common 5.6.5+dfsg-1
ii php5-json 1.3.6-1
ii tzdata 2015a-1
ii ucf 3.0030
ii zlib1g 1:1.2.8.dfsg-2+b1
Versions of
Bug#778597: [PATCH] bootcd: Update LiveUsbBootStick Section in FAQ
Source: bootcd
Source-Version: 4.05
Tags: patch
Dear Maintainer,
I believe the LiveUsbBootStick section in the FAQ contains an error.
At least I was not able to make it work without a few modifications.
Therefore I have updated the FAQ.bootcd.
Kind regards,
Kai Harries
---
Index: bootcd-4.05/FAQ.bootcd
===
--- bootcd-4.05/FAQ.bootcd
+++ bootcd-4.05/FAQ.bootcd
@@ -195,9 +195,9 @@
sgdisk -n 2:0:+100M -c 2:partition for iso -t 2:8300 /dev/sdx
sgdisk -N 3 -c 3:unused partition-t 3:8300 /dev/sdx
# Format partition for iso and mount it
- mkfs.ext3 /dev/sdx2
+ mkfs.ext2 /dev/sdx2
mkdir -p /mnt/stick
mount /dev/sdx2 /mnt/stick
# install Grub
@@ -211,10 +211,12 @@
set default=0
set timeout=5
menuentry 'bootcd 1' {
+insmod part_gpt
+insmod ext2
search --file --set root --no-floppy /cdimage_1.iso
-loopback loop /cdimage.iso
+loopback loop /cdimage_1.iso
linux (loop)/isolinux/vmlinuz root=iso:auto:/cdimage_1.iso
bootcd=standard
initrd (loop)/isolinux/initrd
}
END
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776701: ssd-test 1g file size too small
Am Montag, 16. Februar 2015, 15:04:03 schrieb Jens Axboe: On 02/04/2015 02:10 AM, Martin Steigerwald wrote: Hello Daniel, hi Jens, Am Samstag, 31. Januar 2015, 14:23:34 schrieb Daniel Pocock: Package: fio Version: 2.1.11-2 Severity: important In the ssd-test sample config: https://sources.debian.net/src/fio/2.1.11-2/examples/ssd-test.fio/ The test size is 1GB, this line: size=1g There are SSDs that have 1g caches and this leads to unhelpful results. One user I discussed this with had to use a 10g test file to get consistent and meaningful results. Maybe bump the example to 10g or add a comment in front of that line. As the examples are taken from the upstream tarball, I suggest taking this upstream. I put upstream in Cc, Jens, what do you think about this? Sure, that sounds fine to me. 1G is tiny by todays standards, 10G would be a lot more reasonable. I'll commit that change. Great. I think I will look into packaging latest fio upstream one of the next weeks. (sorry for long sig, can´t disable it) -- Martin Steigerwald | Consultant / Trainer teamix GmbH Südwestpark 43 90449 Nürnberg Tel.: +49 911 30999 55 | Fax: +49 911 30999 99 mail: martin.steigerw...@teamix.de | web: http://www.teamix.de | blog: http://blog.teamix.de Amtsgericht Nürnberg, HRB 18320 | Geschäftsführer: Oliver Kügow, Richard Müller ***Nicht verpassen: TechDemo Hochverfügbare Storage-Infrastruktur*** Nürnberg 25.02.15 | München 26.02.15 | Jetzt anmelden unter: www.teamix.de/techdemo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772963: release-notes: cellphone friendly CSS
On 2015-02-17 01:04, Stéphane Blondon wrote: I didn't find the arrows icons in the repository in Niels's master branch. Do you have directly updated /usr/share/xml/docbook/stylesheet/nwalsh? Hi, I do not quite have the capacity for tracking this thread right now. Feel free to continue this one without me and I will catch up when I can. By all means, please do make a clone/branch on git.debian.org or github if that will facilitate your work, so you do not stall on me. Thanks, ~Niels -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
