Bug#782249: Aborts with Alsa error
Package: liquidsoap Version: 1.1.1-7+b1 Severity: important Dear Maintainer, with some sound cards liquidsoap aborts with: Thread input.alsa_4944 aborts with exception Alsa error: Invalid argument! Thread 4 killed on uncaught exception Alsa.Invalid_argument Used card: VIA Technologies, Inc. VT8237A/VT8251 HDA Controller (rev 10) on hw0.0 -- System Information: Debian Release: 8 Kernel: Linux 3.16.0-4-686-pae Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778882: speedtest-cli: Failed to parse list of speedtest.net servers
Package: speedtest-cli
Version: 0.3.1-1
Followup-For: Bug #778882
Dear Maintainer,
I observe a behaviour [1] similar to that one described in the original
bug
report.
I would like to point out that in the new upstream version 0.3.2 this
problem
is not present. Please consider packaging it.
Thank you.
[1] This is what happens with speedtest 0.3.1-1:
$ speedtest
Retrieving speedtest.net configuration...
Retrieving speedtest.net server list...
Traceback (most recent call last):
File /usr/bin/speedtest, line 9, in module
load_entry_point('speedtest-cli==0.3.1', 'console_scripts',
'speedtest')()
File /usr/lib/python2.7/dist-packages/speedtest_cli.py, line 686,
in main
speedtest()
File /usr/lib/python2.7/dist-packages/speedtest_cli.py, line 536,
in
speedtest
servers = closestServers(config['client'])
File /usr/lib/python2.7/dist-packages/speedtest_cli.py, line 345,
in
closestServers
uh = urlopen('http://www.speedtest.net/speedtest-servers-static.php')
File /usr/lib/python2.7/urllib2.py, line 154, in urlopen
return opener.open(url, data, timeout)
File /usr/lib/python2.7/urllib2.py, line 437, in open
response = meth(req, response)
File /usr/lib/python2.7/urllib2.py, line 550, in http_response
'http', request, response, code, msg, hdrs)
File /usr/lib/python2.7/urllib2.py, line 469, in error
result = self._call_chain(*args)
File /usr/lib/python2.7/urllib2.py, line 409, in _call_chain
result = func(*args)
File /usr/lib/python2.7/urllib2.py, line 656, in http_error_302
return self.parent.open(new, timeout=req.timeout)
File /usr/lib/python2.7/urllib2.py, line 437, in open
response = meth(req, response)
File /usr/lib/python2.7/urllib2.py, line 550, in http_response
'http', request, response, code, msg, hdrs)
File /usr/lib/python2.7/urllib2.py, line 469, in error
result = self._call_chain(*args)
File /usr/lib/python2.7/urllib2.py, line 409, in _call_chain
result = func(*args)
File /usr/lib/python2.7/urllib2.py, line 656, in http_error_302
return self.parent.open(new, timeout=req.timeout)
File /usr/lib/python2.7/urllib2.py, line 437, in open
response = meth(req, response)
File /usr/lib/python2.7/urllib2.py, line 550, in http_response
'http', request, response, code, msg, hdrs)
File /usr/lib/python2.7/urllib2.py, line 469, in error
result = self._call_chain(*args)
File /usr/lib/python2.7/urllib2.py, line 409, in _call_chain
result = func(*args)
File /usr/lib/python2.7/urllib2.py, line 656, in http_error_302
return self.parent.open(new, timeout=req.timeout)
File /usr/lib/python2.7/urllib2.py, line 437, in open
response = meth(req, response)
File /usr/lib/python2.7/urllib2.py, line 550, in http_response
'http', request, response, code, msg, hdrs)
File /usr/lib/python2.7/urllib2.py, line 469, in error
result = self._call_chain(*args)
File /usr/lib/python2.7/urllib2.py, line 409, in _call_chain
result = func(*args)
File /usr/lib/python2.7/urllib2.py, line 656, in http_error_302
return self.parent.open(new, timeout=req.timeout)
File /usr/lib/python2.7/urllib2.py, line 437, in open
response = meth(req, response)
File /usr/lib/python2.7/urllib2.py, line 550, in http_response
'http', request, response, code, msg, hdrs)
File /usr/lib/python2.7/urllib2.py, line 469, in error
result = self._call_chain(*args)
File /usr/lib/python2.7/urllib2.py, line 409, in _call_chain
result = func(*args)
File /usr/lib/python2.7/urllib2.py, line 646, in http_error_302
self.inf_msg + msg, headers, fp)
urllib2.HTTPError: HTTP Error 302: The HTTP server returned a redirect
error
that would lead to an infinite loop.
The last 30x error message was:
Found
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages speedtest-cli depends on:
ii python2.7.9-1
ii python-pkg-resources 5.5.1-1
speedtest-cli recommends no packages.
speedtest-cli 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#782212: MDB backend
Hello,
The same problem does not seem to happen when using HDB. So it might be inside
MDB.
I built and installed slapd from upstream, (removed slapd package and used make
install).
I had to rm «/etc/ldap/slapd.d/cn\=config/cn\=module\{0\}.ldif» to be able to
run «/usr/local/libexec/slapd -F /etc/ldap/slapd.d», I don’t get why.
But then it gave the same result as the slapd from the package, the base that
should not be there is in the results.
signature.asc
Description: OpenPGP digital signature
Bug#782232: zpaq: please make the build reproducible
Source: zpaq
Version: 1.10-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org
Hi!
While working on Debian's “reproducible builds” effort [1], we have
noticed that zpaq doesn't build reproducibly.
It embeds the current date into the manpage.
The attached patch fixes this by using the last changelog date
as a timestamp that will be embedded.
Regards,
Reiner
[1]: https://wiki.debian.org/ReproducibleBuilds
diff --git a/debian/patches/reproducible_build.patch b/debian/patches/reproducible_build.patch
new file mode 100644
index 000..1709a04
--- /dev/null
+++ b/debian/patches/reproducible_build.patch
@@ -0,0 +1,16 @@
+Author: Reiner Herrmann rei...@reiner-h.de
+Description: Remove timestamp from binary to enable reproducible builds.
+
+Index: zpaq-1.10/zpaq.cpp
+===
+--- zpaq-1.10.orig/zpaq.cpp
zpaq-1.10/zpaq.cpp
+@@ -4556,7 +4556,7 @@ void run(int argc, char** argv) {
+ // Print help message and exit
+ void usage() {
+ printf(ZPAQ v1.10 archiver, (C) 2009, Ocarina Networks Inc.\n
+-Written by Matt Mahoney, __DATE__ .\n
++Written by Matt Mahoney.\n
+ This is free software under GPL v3, http://www.gnu.org/copyleft/gpl.html\n;
+ \n
+ To compress to new archive: zpaq [opnsitqv]c[F[,N...]] archive files...\n
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 000..b2026fe
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+reproducible_build.patch
diff --git a/debian/pod2man.mk b/debian/pod2man.mk
index 64bc797..f878a28 100644
--- a/debian/pod2man.mk
+++ b/debian/pod2man.mk
@@ -34,9 +34,10 @@ endif
PACKAGE ?= package
# Optional variables to set
+BUILD_DATE ?= $$(dpkg-parsechangelog -S Date -lchangelog)
MANSECT ?= 1
PODCENTER ?= User Commands
-PODDATE = $$(date +%Y-%m-%d)
+PODDATE = $$(date -u +%Y-%m-%d -d $(BUILD_DATE))
# Directories
MANSRC =
signature.asc
Description: OpenPGP digital signature
Bug#781696: [PATCH] apt-key del keyid is case sensitive
On 04/09/2015 06:34 AM, David Kalnischkies wrote: Beahviour changes two seconds before release are no good. I completely agree with this. Thank you for getting -qi into jessie. I can file a separate bug tonight, and I guess close this one. Note that the output from gnupg as well as from apt is uppercase, so its likely that lowercase is only encountered if people interactively type out the keyids, which is not a very common usecase – after all apt-key is supposed to be used mainly by -keyring packages and even those are supposed to get away from using it leaving next to nobody with a valid usecase to use it… There's a strong case that this was always wrong. At least a warning should be given, but changing that is too late for jessie. The interactive usecase is pretty common with third-party software that distributes a key for their repo but not a keyring package. Please split up your patches into meaningful self-containt entities. Ignoring case is independent from erroring on not found for example, so that should be two commits, not bundled up in one. Okay. Ignoring case is just one character of this patch (the i in -qi) but I see it should still be a separate commit. msgtest Try to remove a key which exists, but isn't in the 'forced keyring' testsuccess --nomsg aptkey --fakeroot --keyring rootdir/etc/apt/trusted.gpg del DBAC8DAE Shouldn't (at least) this testcase fail if you fail on not acting? In fact this test does fail. I didn't write it and it wasn't clearly related to me so I didn't touch it. Nathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709335: [Pkg-libvirt-maintainers] Bug#709335: libvirtd memory leakage
Hi Salvatore, No. You are right the leak is still there. The newer version in wheezy did fix another issue I had though. Any chance of applying the patching to the wheezy version? It's a really annoying bug. My apologies for the misdirection. Daniel On 09/04/15 18:58, Salvatore Bonaccorso wrote: Hi Daniel, On Thu, Apr 09, 2015 at 03:23:24PM +1200, Daniel Reurich wrote: On Tue, 24 Mar 2015 11:12:02 +0100 Horst Schirmeier ho...@schirmeier.com wrote: On Tue, 24 Mar 2015, Horst Schirmeier wrote: We're seeing this on x86-64 Wheezy with the libvirt backports version (currently 1.2.9-9~bpo70+1), too. A virt-manager client was attached several days, ramping up libvirtd memory usage (RES) to 8GB. The workaround (restarting libvirtd) helped. PS: https://bugs.launchpad.net/ubuntu/+source/netcf/+bug/1201938 may be related. There, the netcf package was identified as the culprit, and patched successfully. -- PGP-Key 0xD40E0E7A As per the launchpad bug, the leak is in the netcf package, and that bug has been fixed in netcf version 0.1.9-2 in Wheezy. Are you sure about this? The debian/changelog for 0.1.9-2 in wheezy reads as: netcf (0.1.9-2) unstable; urgency=low * Add debug package (Closes: #650817) * Link against libnl rather than libnl-3 (Closes: #651033) - debian/control - fix dependencies - Don't apply first two patches -- Serge Hallyn serge.hal...@ubuntu.com Mon, 05 Dec 2011 11:20:49 -0600 but the netcf-debian-memleak.patch patch was added separately in Ubuntu. It though should be present in a later version: netcf (1:0.2.3-4) unstable; urgency=low * netcf-debian-memleak.patch: prevent a memory leak when listing interfaces -- Serge Hallyn serge.hal...@ubuntu.com Tue, 13 Aug 2013 23:58:20 + AFAICS. Regards, Salvatore No it didn't. You are right the leak is still there. (I should have read the changelogs - The newer version in wheezy did fix another issue I had though.) My apologies for the misdirection. Daniel -- Daniel Reurich Centurion Computer Technology (2005) Ltd. 021 797 722 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779377: RFS: classified-ads/0.03-1 / ITP
Tobias Frost writes: Almost... you must regenerate the bitmap during the build. Manually is not enough. (Its ok do do it via d/rules, no need to patch your upstream buildsystem. Remember to clean the generated images, e.g using debian/clean. Ok, question: Initiating bitmap conversion seems very easy, just by adding into d/rules: override_dh_auto_configure: + cd graphics-highres ; make dh_auto_configure -- CONFIG+=nosilent the line marked with + and both debuild+dpkg-buildpackage seem both happy, as is lintian. The part that concerns me is that this addition overwrites files that are also included in .orig.tar.gz - is this considered bad thing? Having the generated png-files inside tarball is handy for doing build for windows+mac, but if necessary, this could be handled with git branching-tricks quite easily. Btw, I've agreed about identification+pgp-key signing with a DD living in Helsinki area, no date is set yet as I'm some 600km away but it will happen eventually.. -- Antti message.txt.asc Description: Message with signature
Bug#782250: ITP: python-future -- use a single, clean Python 3.x-compatible codebase to support both Python 2 and Python 3 with minimal overhead
Hello dacoex. Some time ago (on 2015-03-05) you asked aboyt python-future. Barry Warsaw is starting work on packaging it. Best regards. Dnia 2015-04-09, czw o godzinie 09:54 -0400, Barry Warsaw pisze: Package: wnpp Severity: wishlist Owner: Barry Warsaw ba...@debian.org * Package name: python-future Version : 0.14.3 Upstream Author : Ed Schofield * URL : https://python-future.org/ * License : MIT/X Programming Lang: Python Description : use a single, clean Python 3.x-compatible codebase to support both Python 2 and Python 3 with minimal overhead Easy, clean, reliable Python 2/3 compatibility, this is the missing compatibility layer between Python 2 and Python 3. This package will be maintained within the DPMT. -- Tomasz Rybak GPG/PGP key ID: 2AD5 9860 Fingerprint A481 824E 7DD3 9C0E C40A 488E C654 FB33 2AD5 9860 http://member.acm.org/~tomaszrybak signature.asc Description: This is a digitally signed message part
Bug#718807: Confirmed, reproducible, critical
I can reproduce this bug with package: bind9 1:9.8.4.dfsg.P1-6+nmu2+deb7u4 I have several internal networks and a PPPoE client running. The trigger is when the PPPoE link fails and the interface ppp0 goes away, along with its local address. I have discovered a second trigger that is when ppp0 re-appears, bind9 crashes in the same way. I have further refined this to if any interface is downed, bind will crash - eg: ifdown eth0.1002 The cause2trigger seems instant and 100% reproducible. The crash causes bind to syslog the following: Apr 9 12:45:10 shinybob named[12196]: received control channel command 'reconfig' Apr 9 12:45:10 shinybob named[12196]: loading configuration from '/etc/bind/named.conf' Apr 9 12:45:10 shinybob named[12196]: reading built-in trusted keys from file '/etc/bind/bind.keys' Apr 9 12:45:10 shinybob named[12196]: using default UDP/IPv4 port range: [1024, 65535] Apr 9 12:45:10 shinybob named[12196]: using default UDP/IPv6 port range: [1024, 65535] Apr 9 12:45:10 shinybob named[12196]: no IPv6 interfaces found Apr 9 12:45:10 shinybob named[12196]: no longer listening on 81.2.78.28#53 Apr 9 12:45:10 shinybob named[12196]: sizing zone task pool based on 46 zones Apr 9 12:45:10 shinybob named[12196]: view.c:467: REQUIRE(targetp != ((void *)0) *targetp == ((void *)0)) failed, back trace Apr 9 12:45:10 shinybob named[12196]: #0 0xb76ef724 in ?? Apr 9 12:45:10 shinybob named[12196]: #1 0xb72472b4 in ?? Apr 9 12:45:10 shinybob named[12196]: #2 0xb75e66a5 in ?? Apr 9 12:45:10 shinybob named[12196]: #3 0xb75e8700 in ?? Apr 9 12:45:10 shinybob named[12196]: #4 0xb76d2a09 in ?? Apr 9 12:45:10 shinybob named[12196]: #5 0xb7705805 in ?? Apr 9 12:45:10 shinybob named[12196]: #6 0xb77075a9 in ?? Apr 9 12:45:10 shinybob named[12196]: #7 0xb7707dbc in ?? Apr 9 12:45:10 shinybob named[12196]: #8 0xb76e82bc in ?? Apr 9 12:45:10 shinybob named[12196]: #9 0xb76eaf68 in ?? Apr 9 12:45:10 shinybob named[12196]: #10 0xb726a282 in ?? Apr 9 12:45:10 shinybob named[12196]: #11 0xb721ec39 in ?? Apr 9 12:45:10 shinybob named[12196]: #12 0xb7036c6e in ?? Apr 9 12:45:10 shinybob named[12196]: exiting (due to assertion failure) I think this needs to be raised to a higher priority. I have no elegant workaround - I have a kudgey workaround of running monit to watchdog bind9 and restart when needed. I have supply additional config on demand, but please be warned that my bind9 config is non trivial. It may be worth just trying the ifdown test on the same version of bind with any running config. Kind regards, Tim -- Tim Watts Personal Blog: http://squiddy.blog.dionic.net/ http://www.sensorly.com/ Crowd mapping of 2G/3G/4G mobile signal coverage -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782193: apngopt: please make the build reproducible
Source: apngopt Version: 1.2-1 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Hi! While working on Debian's “reproducible builds” effort [1], we have noticed that apngopt doesn't build reproducibly. It embeds the current date into the manpage. The attached patch fixes this by using the last changelog date as a timestamp that will be embedded. Regards, Reiner [1]: https://wiki.debian.org/ReproducibleBuilds diff --git a/debian/pod2man.mk b/debian/pod2man.mk index 450fa9a..e8c7d36 100644 --- a/debian/pod2man.mk +++ b/debian/pod2man.mk @@ -38,9 +38,10 @@ endif PACKAGE ?= package # Optional variables to set +BUILD_DATE ?= $$(dpkg-parsechangelog -S Date -lchangelog) MANSECT ?= 1 PODCENTER ?= User Commands -PODDATE ?= $$(date +%Y-%m-%d) +PODDATE ?= $$(date -u +%Y-%m-%d -d $(BUILD_DATE)) # Directories MANSRC ?= signature.asc Description: OpenPGP digital signature
Bug#769030: closed by Debian FTP Masters ftpmas...@ftp-master.debian.org (Bug#769030: fixed)
On 2015-04-09 22:30, Ansgar Burchardt wrote: was this the only change applied? Because there were more packages in the subject. No, I updated the other two packages as well. However dak override can only update one package at a time so I closed the bug report with the first of the changes. Thanks! Kind regards Philipp Kern -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779649: so no squid on new jessie installs?
On Thu, Apr 09, 2015 at 10:38:25AM +0200, Holger Levsen wrote: On Mittwoch, 8. April 2015, Wolfgang Schweer wrote: If upgrading from wheezy d-e would end up with squid kept installed and working but w/o any updates, I guess. and that (=no security upgrades) is a serious problem as it's a network facing service, putting the whole installation (and thus pupils and teachers data) at risk. the steps to migrate from squid to squid3 contained in the d-e jessie manual Upgrades chapter might go into a script called during the cfengine fifths pass run. In addition it would be needed to check in the script if squid3 is running to keep cfengine's actions idempotent. Unsure if this could be the way to go as I dont know enough about cfengin's passes (and to actually code it). Wolfgang signature.asc Description: Digital signature
Bug#782216: hpanel: please make the build reproducible
Source: hpanel Version: 0.3.2-4 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Hi! While working on Debian's “reproducible builds” effort [1], we have noticed that hpanel doesn't build reproducibly. It embeds the current date into the manpage. The attached patch fixes this by using the last changelog date as a timestamp that will be embedded. Regards, Reiner [1]: https://wiki.debian.org/ReproducibleBuilds diff --git a/debian/pod2man.mk b/debian/pod2man.mk index 64bc797..f878a28 100644 --- a/debian/pod2man.mk +++ b/debian/pod2man.mk @@ -34,9 +34,10 @@ endif PACKAGE ?= package # Optional variables to set +BUILD_DATE ?= $$(dpkg-parsechangelog -S Date -lchangelog) MANSECT ?= 1 PODCENTER ?= User Commands -PODDATE = $$(date +%Y-%m-%d) +PODDATE = $$(date -u +%Y-%m-%d -d $(BUILD_DATE)) # Directories MANSRC = signature.asc Description: OpenPGP digital signature
Bug#782266: nettle-dbg: directory vs. symlink conflict: /usr/share/doc/nettle-dbg - libnettle4
Package: nettle-dbg Version: 3.0-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package installs files over an existing symlink shipped or created by another package. This was observed during an sid-experimental upgrade. Installing something over existing symlinks is considered bad practice. See e.g. https://lists.debian.org/87ehlevcrf@windlord.stanford.edu It may break in subtle ways and dpkg cannot detect this as a problem. * Your package might silently overwrite files installed at the symlink destination by other packages. * If the package shipping the symlink decides to make the link point somewhere else (or turn it into a real directory), the files owned by your package will be lost somewhere in the filesystem. * Depending on installation order the problematic path will be created either as a symlink or a directory: the package installed first will win and all others have lost. Note that dpkg intentionally does not replace directories with symlinks and vice versa, see in particular the end of point 4 in https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase (Note: Adding Pre-Depends is *not* a solution.) From the attached log (usually somewhere in the middle...): 0m58.8s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/nettle-dbg/changelog.Debian.gz (nettle-dbg) != /usr/share/doc/libnettle4/changelog.Debian.gz (libnettle4:amd64) /usr/share/doc/nettle-dbg - libnettle4 /usr/share/doc/nettle-dbg/changelog.gz (nettle-dbg) != /usr/share/doc/libnettle4/changelog.gz (libnettle4:amd64) /usr/share/doc/nettle-dbg - libnettle4 /usr/share/doc/nettle-dbg/copyright (nettle-dbg) != /usr/share/doc/libnettle4/copyright (libnettle4:amd64) /usr/share/doc/nettle-dbg - libnettle4 0m59.4s ERROR: FAIL: debsums reports modifications inside the chroot: /usr/share/doc/libnettle4/changelog.Debian.gz /usr/share/doc/libnettle4/changelog.gz cheers, Andreas nettle-dbg_3.0-2.log.gz Description: application/gzip
Bug#782201: gif2apng: please make the build reproducible
Source: gif2apng Version: 1.7-3 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Hi! While working on Debian's “reproducible builds” effort [1], we have noticed that gif2apng doesn't build reproducibly. It embeds the current date into the manpage. The attached patch fixes this by using the last changelog date as a timestamp that will be embedded. Regards, Reiner [1]: https://wiki.debian.org/ReproducibleBuilds diff --git a/debian/pod2man.mk b/debian/pod2man.mk index 450fa9a..e8c7d36 100644 --- a/debian/pod2man.mk +++ b/debian/pod2man.mk @@ -38,9 +38,10 @@ endif PACKAGE ?= package # Optional variables to set +BUILD_DATE ?= $$(dpkg-parsechangelog -S Date -lchangelog) MANSECT ?= 1 PODCENTER ?= User Commands -PODDATE ?= $$(date +%Y-%m-%d) +PODDATE ?= $$(date -u +%Y-%m-%d -d $(BUILD_DATE)) # Directories MANSRC ?= signature.asc Description: OpenPGP digital signature
Bug#776739: assist cn=config users with schema updates
On Sat, 31 Jan 2015 16:00:16 -0800 Ryan Tandy r...@nardis.ca wrote: Package: slapd Version: 2.4.40-3 Severity: wishlist Files in /etc/ldap/schema are updated during upgrades, per the conffile rules, but currently we don't do anything about schemas imported into config databases. It would be nice if we notified users that their schemas were out of date, and even nicer if we offered assistane with upgrading them safely. (Concrete example: ppolicy.schema gained ordering rules in 2.4.40.) You may be interested by our tool fusiondirectory-insert-schema, it has a -i option to insert and -m option to update schema. (-m is for modify) https://forge.fusiondirectory.org/projects/fd/repository/revisions/master/entry/contrib/bin/fusiondirectory-insert-schema (It is also available in the fusiondirectory debian package but then you’ll have the whole web application you may not need at all) (Note: do not launch without option, it will try and install FD standard schemas. Use -h option for help) Côme signature.asc Description: OpenPGP digital signature
Bug#774643: [Pkg-puppet-devel] Bug#774643: fix introduces problems for Foreman
Hi Michael, On 23:54 Wed 08 Apr , Michael Moll wrote: Hi Apollon, On Wed, Apr 08, 2015 at 07:26:03PM +0300, Apollon Oikonomopoulos wrote: The mere presence of ruby-activerecord-deprecated-finders on the system should not impact foreman. What kind of problems did you encounter? The actual output: /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:251:in `block in require' /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:236:in `load_dependency' /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:251:in `require' /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/lazy_load_hooks.rb:36:in `instance_eval' /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/lazy_load_hooks.rb:36:in `execute_hook' /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/lazy_load_hooks.rb:26:in `block in on_load' /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/lazy_load_hooks.rb:25:in `each' /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/lazy_load_hooks.rb:25:in `on_load' /usr/share/foreman/vendor/ruby/2.1.0/gems/railties-3.2.21/lib/rails/initializable.rb:30:in `instance_exec' /usr/share/foreman/vendor/ruby/2.1.0/gems/railties-3.2.21/lib/rails/initializable.rb:30:in `run' /usr/share/foreman/vendor/ruby/2.1.0/gems/railties-3.2.21/lib/rails/initializable.rb:55:in `block in run_initializers' /usr/share/foreman/vendor/ruby/2.1.0/gems/railties-3.2.21/lib/rails/initializable.rb:54:in `each' /usr/share/foreman/vendor/ruby/2.1.0/gems/railties-3.2.21/lib/rails/initializable.rb:54:in `run_initializers' /usr/share/foreman/vendor/ruby/2.1.0/gems/railties-3.2.21/lib/rails/application.rb:136:in `initialize!' /usr/share/foreman/vendor/ruby/2.1.0/gems/railties-3.2.21/lib/rails/railtie/configurable.rb:30:in `method_missing' I didn't do further research and it might also have to do with our packages using vendored gems, however after removing the said package, it worked. Yes, your packages ship a vendorized version of rails 3.2 (which would also make it a bit difficult to get into the Debian archive). Since rails 3.2 is virtually EOL[1], foreman should eventually move to Rails 4, which will also make it easier to remove the bundled gems and use the Debian packages. [1] http://guides.rubyonrails.org/maintenance_policy.html: note that only severe security issues will be fixed for rails 3.2 at this point. Cheers, Apollon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782248: new upstream (2.23)
Package: calibre Severity: wishlist Hi, it would be nice if you could upgrade to 2.23. Regards, Daniel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774697: xmobar: Localized dates are disabled
Hi François, On 12:54 Tue 06 Jan , François Gannaz wrote: Package: xmobar Severity: wishlist Dear Maintainer, please compile xmobar with the parameter `with_datezone`. Unfortunately the timezone-olson and timezone-series packages required for this are missing in Debian. I'll try to get them packages once Jessie's freeze is over. Regards, Apollon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782268: RM: get-iplayer/2.87-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm The moving target that is iPlayer has moved again, and get-iplayer in Jessie can no longer retrieve programmes with a high enough success rate to be useful. Please remove it from Jessie and I will maintain through backports. Thanks, -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-proposed-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash 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#782205: game-data-packager: integrate lgogdownloader support
Package: game-data-packager Version: 40 Severity: wishlist Dear Maintainer, Please integrate support for lgogdownloader (GOG.com downloader) that is already in the archive. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782198: glibc: 2.21 FTBFS on mips
Source: glibc
Version: 2.21-0experimental0
Severity: important
Tags: patch
Hi,
I've attached a patch (to a patch) which fixes the FTBFS of 2.21 on
mips*. The bug is in the local-libgcc-compat-ports.diff patch. A warning
about __floatdisf not being defined had been appearing in the build logs
for years (since the patch was introduced?), but now it's an error it's
causing the build to fail.
Thanks,
James
diff -ur a/debian/patches/any/local-libgcc-compat-ports.diff b/debian/patches/any/local-libgcc-compat-ports.diff
--- a/debian/patches/any/local-libgcc-compat-ports.diff 2015-03-16 16:03:45.0 +
+++ b/debian/patches/any/local-libgcc-compat-ports.diff 2015-04-07 13:00:45.904337405 +0100
@@ -84,7 +84,7 @@
+symbol_version (__floatdidf_internal, __floatdidf, GLIBC_2.0);
+
+
-+extern float floatdisf (int64_t);
++extern float __floatdisf (int64_t);
+float __floatdisf_internal (int64_t u)
+{
+ return __floatdisf (u);
signature.asc
Description: This is a digitally signed message part
Bug#647441: xapian-bindings: python3-xapian
fyi, I built packages to test the python3 bindings at https://launchpad.net/~doko/+archive/ubuntu/toolchain no documentation, the amd64 build fails (builds fine locally for me), the tcl tests fail. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782273: sympa: wheezy-jessie upgrade fails to add prev_id_session column to session_table
On Thu, Apr 09, 2015 at 09:52:28PM +0200, Emmanuel Bouthenot wrote: I guess your using a postgres database. You should take a look at Yes, sorry, I meant to specify that. https://bugs.debian.org/769074, it's explained how to fix it. Hmm. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782041: yafc: Segfaults on specific path to shorten
On 2015-04-09 14:10:43, Celelibi wrote: 2015-04-09 11:05 UTC+02:00, Sebastian Ramacher sramac...@debian.org: xmalloc calls memset(..., 0, ...) on the the allocated memory block. I've removed the explicit assignment. I've seen this, but didn't know if that was just a fool-proof protection or actually part of the specification of the xmalloc function. The xmalloc in yafc does. + if (maxlen - start_len - 3 0) + copy_from = strchr(path + len - (maxlen - start_len - 3), '/'); This causes invalid reads if 0 = maxlen - start_len 3. Changing the condition to maxlen - start_len 3 fixes that. My math failed me. :) You're right, this is an unsigned expression. Although I agree with the mistake, I'd suggest writing the condition maxlen start_len + 3 to handle the following case: maxlen = 7, start_len = 8. maxlen - start_len 3 is true. maxlen - start_len - 3 == (unsigned)-4 thus making the memory access invalid. Thanks, fixed. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#781250: CVE-2015-1779 / CVE-2015-XXXX
Hi Michael, Mortiz, Small update for CVE-2015-1779: so the patches commited upstream are: http://git.qemu.org/?p=qemu.git;a=commit;h=a2bebfd6e09d http://git.qemu.org/?p=qemu.git;a=commit;h=2cdb5e142fb93 From: http://www.openwall.com/lists/oss-security/2015/04/09/6 Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782265: systemd always looks for plymouth even though it's not installed.
Hello shirish, shirish शिरीष [2015-04-09 21:37 +0530]: Apr 09 13:42:55 debian systemd[1]: Failed to load configuration for plymouth-start.service: No such file or directory Apr 09 13:42:55 debian systemd[1]: Failed to load configuration for plymouth-quit.service: No such file or directory Apr 09 13:42:55 debian systemd[1]: Failed to load configuration for plymouth-quit-wait.service: No such file or directory Not sure yet where these come from. Apr 09 13:42:55 debian systemd[1]: ConditionPathExists=!/run/plymouth/pid succeeded for systemd-ask-password-console.path. This and the three from above look like debug messages. Are you running with debug or systemd.log_level=debug? Apr 09 13:42:55 debian systemd-fsckd[159]: Couldn't connect to plymouth: Connection refused Apr 09 13:42:55 debian systemd-fsckd[159]: Couldn't send message to plymouth These are fixed in the experimental git already: http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=experimentalid=d7db462912c2c9 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#635752: ntp: Please include systemd service file
Package: ntp Version: 1:4.2.6.p5+dfsg-5 Followup-For: Bug #635752 Dear Maintainer, We are using saltstack to deploy our debian servers, during which we also have a formula that installs ntp on all systems, enables it and checks if it needs a restart due to changes in configuration files. As part of this, saltstack runs 'systemctrl is-enabled ntp.service' which on debian results in the error: Failed to get unit file state for ntp.service: No such file or directory expected output would be: enabled This is a rather minor, yet annoying issue. Given that Jessie introduces systemd as default, it would be nice if this could be resolved. Regards, Thomas -- 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/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ntp depends on: ii adduser 3.113+nmu3 ii dpkg 1.17.24 ii libc62.19-15 ii libcap2 1:2.24-7 ii libedit2 3.1-20140620-2 ii libopts251:5.18.4-3 ii libssl1.0.0 1.0.1k-1 ii lsb-base 4.1+Debian13+nmu1 ii netbase 5.3 Versions of packages ntp recommends: ii perl 5.20.2-2 Versions of packages ntp suggests: pn ntp-doc none -- Configuration Files: /etc/ntp.conf changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782161: rspec 3 does not have --pattern option
Control: reassign -1 gem2deb Control: found -1 0.12 On Thu, Apr 09, 2015 at 12:10:06AM +0530, Pirate Praveen wrote: package: gem2deb-test-runner version: 0.12 severity: critical After updating rspec to 3.2 from experimental, tests fail with /usr/bin/ruby2.1 -I/usr/lib/ruby/vendor_ruby /usr/bin/gem2deb-test-runner Running tests for ruby2.1 using debian/ruby-tests.rake ... /usr/bin/ruby2.1 -I /usr/lib/ruby/exe/rspec --pattern ./spec/\*\*/\*_spec.rb /usr/bin/ruby2.1: invalid option --pattern (-h will show valid options) (RuntimeError) /usr/bin/ruby2.1 -I /usr/lib/ruby/exe/rspec --pattern ./spec/\*\*/\*_spec.rb failed the gem tried was open_graph_reader the problem is actually in dh-make-ruby because the code that it generates in debian/ruby-tests.rb is not compatible with rspec3. But packages that already have it cannot be automatically fixed need and will need to be updated. -- Antonio Terceiro terce...@debian.org signature.asc Description: Digital signature
Bug#781696: [PATCH] apt-key del keyid is case sensitive
Control: tags -1 - jessie sid Control: found -1 0.9.10 # introduced by git commit 04937adc655ceda0b3367f540e76df10296cfba1 On Thu, Apr 09, 2015 at 01:30:19AM -0400, Nathan Kennedy wrote: Tagging this as a security issue since the effect is to allow installation of packages signed with keys that the administrator (or a an administrative script) specifically intended to remove, and this is a regression from wheezy. I think 'security' is a bit much here but well… The 'OK' was always the case, removed or not and changing this at this point in time is completely out of question as there might be maintainerscripts depending on this behavior (many -keyring packages remove 'old' keys or transition to fragment files and not all of them ignore the exitcode of apt-key in this case). Beahviour changes two seconds before release are no good. The regression on lower-case (aka the grep -i) is under consideration for jessie. A pre-approval unblock request with this (and other things) was filled yesterday (see #782131). Note that the output from gnupg as well as from apt is uppercase, so its likely that lowercase is only encountered if people interactively type out the keyids, which is not a very common usecase – after all apt-key is supposed to be used mainly by -keyring packages and even those are supposed to get away from using it leaving next to nobody with a valid usecase to use it… … expect apt itself in future. See the experimental branch which reworks apt-key to make what used to be considered the enemy (= the idea was to remove dependency on gnupg and ultimatively drop apt-key) our best friend (= future gnupg2 is going to enforce some new rules like only one keyring which work directly against e.g. trusted.gpg.d/ so we need gpg to do all sorts of clever magic instead of resorting to gpgv only :/ ). Pull request with fix to sid is attached. This doesn't fully restore previous behavior; before long keyids could be used as well, but it allows mixed case and fails if deletion fails (LP 1256565). Please split up your patches into meaningful self-containt entities. Ignoring case is independent from erroring on not found for example, so that should be two commits, not bundled up in one. As said, the later isn't going to be considered for jessie, but we could do e.g. a warning for stretch and error for buster. Please report a new bug for this – if you want to adapt your patch all the better (please against /experimental aka soon-to-be stretch). btw: /experimental also restores fingerprint (long keyid is supported). What it doesn't is all the various other things of matching a key gnupg supports – if those happen to work (or not) is undefined by the manpage (it says only keyid). +msgtest Try to remove a 'nonexistent keyid' +testfailure --nomsg aptkey --fakeroot --keyring rootdir/etc/apt/trusted.gpg del BOGUSKEY Such a test is probably better of using a valid keyid – otherwise you are testing if bogus ids trigger an error, not if a nonexistent id triggers an error. msgtest Try to remove a key which exists, but isn't in the 'forced keyring' testsuccess --nomsg aptkey --fakeroot --keyring rootdir/etc/apt/trusted.gpg del DBAC8DAE Shouldn't (at least) this testcase fail if you fail on not acting? Best regards David Kalnischkies signature.asc Description: Digital signature
Bug#782225: mksh: parameter expansion: string length ${#parameter} is incorrect on multibyte character
Package: mksh
Version: 50d-5
Severity: normal
In UTF-8 based locales:
$ mksh -c 'a=$(/usr/bin/printf \\u00e9); echo $a ${#a}'
é 2
while POSIX says[*]:
${#parameter}
String Length. The length in characters of the value of parameter
shall be substituted.
[*]
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_06_02
This the length in *characters*, not in bytes!
So, the output should be é 1 like with bash, ksh93 and zsh.
-- System Information:
Debian Release: 8.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages mksh depends on:
ii libc6 2.19-17
mksh recommends no packages.
Versions of packages mksh suggests:
ii ed 1.10-2
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781250: CVE-2015-1779 / CVE-2015-XXXX
On Thu, Apr 09, 2015 at 07:06:06PM +0300, Michael Tokarev wrote: 9 апреля 2015 г. 18:42:13 GMT+03:00, Salvatore Bonaccorso car...@debian.org пишет: Hi Michael, Mortiz, Small update for CVE-2015-1779: so the patches commited upstream are: Yes, thanks, I've seen the commits the other day, and I receive oss-sec as well. I hoped to see a fix for the second prob too Michael, I think we also need the patches from http://xenbits.xen.org/xsa/advisory-126.html ? Do you have it on radar or shall we file a bug? 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#782165: wheezy-pu: package debootstrap/1.0.48+deb7u3
Control: tags -1 + pending On Thu, 2015-04-09 at 00:37 +0200, Cyril Brulebois wrote: Adam D. Barratt a...@adam-barratt.org.uk (2015-04-08): Control: tags -1 + confirmed On Wed, 2015-04-08 at 21:51 +0200, Cyril Brulebois wrote: finally time to get some stable updates… Here's the bug report I'd like to address in wheezy: “debootstrap: host's /run/shm gets unmounted after debootstrap run” (https://bugs.debian.org/753442). I'll have to check it inside a VM soon-ish (because I don't seem to have any hosts running wheezy at the moment), but given the change that got backported and the fact we've had the fix in testing, and in backports for quite a while, I don't seem to have so many doubts about it. Please feel free to go ahead, thanks. Great, thanks. Local tests seem to confirm the nasty bug is fixed as desired, so I've just uploaded the package. Flagged for acceptance, thanks. Regards, Ada -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778265: [Pkg-puppet-devel] Bug#778265: CVE-2015-1426
On Wed, Feb 25, 2015 at 07:57:31PM +0100, Stig Sandbeck Mathisen wrote: Control: tags -1 + patch confirmed Moritz Muehlenhoff j...@inutil.org writes: Moritz Muehlenhoff wrote: Package: facter Severity: important Tags: security Please see http://puppetlabs.com/security/cve/cve-2015-1426 Patch attached. Lovely, thanks. :) The freeze is getting really close, could you please upload a fixed package so that it can still be unblocked in time? 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#782173: RFS: chrony/1.30-2 [RC] -- Set the computer clock from time servers on the Net
Control: owner -1 ! Control: tag -1 + moreinfo On Thu, 09 Apr 2015 01:00:12 +0200, Joachim Wiedorn wrote: I am looking for a sponsor for my package chrony [..] dget -x http://mentors.debian.net/debian/pool/main/c/chrony/chrony_1.30-2.dsc I'd be willing to sponsor this upload, I just saw one minor glitch: Changes since the last upload: * New upstream release. * It includes the following security fixes (Closes: #782160): - Fix CVE-2015-1853: Protect authenticated symmetric NTP associations against DoS attacks. - Fix CVE-2015-1821: Fix access configuration with subnet size indivisible by 4. - Fix CVE-2015-1822: Fix initialization of reply slots for authenticated commands. * debian/control: - Update e-mail address of myself. - Add Vincent Blut as co-maintainer. It seems that d/changlog is not really correct, in a slightly confusing way: This is no new upstream release but a backport of some fixes from the new upstream release to the current version. At least I guess so :) (And for and upload to unstable targetting jessie I'd probably also drop the changes in d/control to make the diff smaller for the release team; although it propbably doesn't matter for those technically trivial changes.) 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: Ostbahn-Kurti Die Chefpartie: Tequila Sunrise signature.asc Description: Digital Signature
Bug#778773: [PATCH] Likely fix for crash
Control: tag -1 jessie sid Cyril Brulebois k...@debian.org (2015-03-04): And your hypothesis seems totally plausible, let's look at d56c74f310b02af4f81e5f5a5ba65b55fdbdc34e[1]: | Adapt parted_server code to handle new GNU Parted swap filesystem handling. | | r59025 1. http://anonscm.debian.org/cgit/d-i/partman-base.git/commit/?id=d56c74f310b02af4f81e5f5a5ba65b55fdbdc34e I could imagine how tempting it would be to copy-paste between partition_info() and command_get_file_system(). The former deals with part-[…] stuff, while the latter deals with fstype. I'm very tempted to get the fix uploaded ASAP so that people can toy around, even if I don't do any testing myself. I don't see how it could possibly become worse than the current state of affairs. So in the end I've been able to reproduce this issue with the unpatched partman-base in testing at the time, and to see it go away with the patched one in sid; the updated package got therefore merged into jessie in time for D-I Jessie RC2 (even if I failed to mention this in the release announce, woops). In the meanwhile I haven't been able to reproduce this issue with wheezy even if the wrong code in partman-base was already there. Looking at the diff between parted 2.3 and 3.2, there have been some fstype vs. fs_type assignments getting changed so this likely explains why the partman-base isn't exposed there. I'm therefore adding the “if it ain’t broke, don’t fix it” tags accordingly. Mraw, KiBi. signature.asc Description: Digital signature
Bug#782066: linux-image-3.16.0-4-powerpc: Messed up colors with KMS disabled in PowerPC
Hi, I succeeded in loading radeonfb by removing it from /etc/modprobe.d/fbdev-bloacklist.conf, and I also had to turn off the open firmware framebuffer with the boot parameter video=offb:off. However, I'm now stuck in 8-bit colors. I tried adding the boot parameter that worked with the previous kernel, video=radeonfb:1024x768-32@60, but it had no effect. I also added radeonfb mode_option=1024x768-32@60 to /etc/modules and /etc/initramfs-tools/modules and ran # update-initramfs -u, but I'm still getting 8-bit colors. Is there anything else I can try? Is the bug regarding KMS on this system recorded on the upstream bug tracker (https://bugs.freedesktop.org)? No, I will do that. Regards, Dan My Xorg.0.log with the above settings: [34.660] X.Org X Server 1.16.4 Release Date: 2014-12-20 [34.668] X Protocol Version 11, Revision 0 [34.668] Build Operating System: Linux 3.2.0-4-powerpc64 ppc Debian [34.669] Current Operating System: Linux icebook 3.16.0-4-powerpc #1 Debian 3.16.7-ckt7-1 (2015-03-01) ppc [34.669] Kernel command line: root=UUID=60b9f356-e890-4f97-b7b6-be28c1f5a480 ro radeon.modeset=0 video=offb:off video=radeonfb:1024x768-32@60 [34.669] Build Date: 11 February 2015 01:13:01AM [34.669] xorg-server 2:1.16.4-1 (http://www.debian.org/support) [34.669] Current version of pixman: 0.32.6 [34.669]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [34.669] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [34.670] (==) Log file: /var/log/Xorg.0.log, Time: Thu Apr 9 01:00:34 2015 [34.779] (==) Using system config directory /usr/share/X11/xorg.conf.d [34.843] (==) No Layout section. Using the first Screen section. [34.844] (==) No screen section available. Using defaults. [34.844] (**) |--Screen Default Screen Section (0) [34.844] (**) | |--Monitor default monitor [34.845] (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. [34.845] (==) Automatically adding devices [34.845] (==) Automatically enabling devices [34.845] (==) Automatically adding GPU devices [34.906] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [34.906]Entry deleted from font path. [34.930] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [34.930] (==) ModulePath set to /usr/lib/xorg/modules [34.930] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [34.952] (II) Loader magic: 0x2037c698 [34.952] (II) Module ABI versions: [34.952]X.Org ANSI C Emulation: 0.4 [34.952]X.Org Video Driver: 18.0 [34.952]X.Org XInput driver : 21.0 [34.952]X.Org Server Extension : 8.0 [34.955] (--) PCI:*(0:0:16:0) 1002:4c59:1002:4c59 rev 0, Mem @ 0x9800/134217728, 0x9000/65536, I/O @ 0x0400/256, BIOS @ 0x/131072 [34.960] (II) LoadModule: glx [34.993] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [35.241] (II) Module glx: vendor=X.Org Foundation [35.241]compiled for 1.16.4, module version = 1.0.0 [35.241]ABI class: X.Org Server Extension, version 8.0 [35.241] (==) AIGLX enabled [35.243] (==) Matched ati as autoconfigured driver 0 [35.243] (==) Matched modesetting as autoconfigured driver 1 [35.243] (==) Matched fbdev as autoconfigured driver 2 [35.243] (==) Assigned the driver to the xf86ConfigLayout [35.243] (II) LoadModule: ati [35.244] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so [35.261] (II) Module ati: vendor=X.Org Foundation [35.261]compiled for 1.16.1, module version = 7.5.0 [35.261]Module class: X.Org Video Driver [35.261]ABI class: X.Org Video Driver, version 18.0 [35.262] (II) LoadModule: radeon [35.262] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so [35.338] (II) Module radeon: vendor=X.Org Foundation [35.338]compiled for 1.16.1, module version = 7.5.0 [35.338]Module class: X.Org Video Driver [35.338]ABI class: X.Org Video Driver, version 18.0 [35.338] (II) LoadModule: modesetting [35.339] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so [35.366] (II) Module modesetting: vendor=X.Org Foundation [35.366]compiled for 1.15.99.904, module version = 0.9.0 [35.367]Module class: X.Org Video Driver [35.367]ABI class: X.Org Video Driver, version 18.0 [35.367]
Bug#782058: Pegasos II: installer boots up to 'returning from prom_init'
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 04/09/2015 12:38 AM, Milan Kupcevic wrote: Well, yes. As you could see from the bug report you linked above, compiling radeonfb into the kernel broke X on basically all Radeon cards. It seems that radeonfb was compiled into the kernel since the dawn of time. On the powerpc Debian kernel, yes, on the other architectures, no. radeonfb has been deprecated long time ago and should no longer be used. The only reason it was compiled into the powerpc kernel without anyone complaining is the fact that the xf86-video-ati (= Radeon X.Org) driver in Wheezy was still old enough [1] to support userland mode-setting which was dropped upstream in version 7.0.0 almost three years ago [2]. This is no longer true in Jessie and therefore we have to use radeon, not radeonfb. Otherwise you won't get any X display. The reason is that the radeon KMS module does not work once radoenfb has been loaded once. Even if you unload radeonfb later, the radeon module will still refuse to work meaning X will not be usable. This is good to know. I did thorough testing for the bug report you linked above which is why I am a bit surprised you could convince Ben so easily to partly revert my change. I think I also explained in the other bug tracker that you have to use KMS these days as UMS is being phased out. Well, I think this can be answered straight-forward: radeonfb is the wrong solution as radeonfb does not support X which means you can use the text-based installer only. But I guess you never tested that as you stated in your bug report. The proper fix for your problem is not to revert my previous fix but to use the proper driver, thus reopening. There was no my previous fix, just reporting about the state of the things in RC1 and RC2. I'm trying to help as I have access to more than a few power and powerpc machines. Sure, but please ask people in the future before you are asking for changes which you don't understand. I also have tons of different hardware available here, including several powerpc machines and way beyond that (m68k, sh4, mips etc). I think you should at least discuss such changes with some more people before you ask for them to be integrated. For anyone who follows X.Org and kernel development, it is common knowledge that all the non-KMS drivers in the kernel are being deprecated and that you should no longer use them. This also applies to X.Org. It would be nice if you could CC me in the future if you are having issues with non-x86 hardware, especially anything that's powerpc, Macintosh, or - like in this case - Amiga-related hardware. Adrian - -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJVJjNyAAoJEHQmOzf1tfkTItwQAJid5vaSBdjsJBSROc7URnNp G7kc6AEF3oaEbX1lsqQ/wfvfKsFdKztN+ro4oAPW7xgo/QxQI7qWuDxNgTvbyOl2 9ApGjwliLKU5D4em479V58qTUnl0agcTqJxruWU88Kdb5NxUQrtAnRdqrmak6e5m pHPA+uMREu8KKM1TDOjw1ErJEKUXV8lnH+LVKIWRvWBoS9n63mHTZv69YDwSTZvh +V4zhVqwb++kcrVYX+GqPaeX+/N5hH1SaS2PAwqZCXXNXMm0x3XAHNVwk1GvvDek e+pZEiJi3pr7AtyJuzHsREQyIc3ivgDzw14DUvXIpSdrvkufj1jo/WbmkT+F9aik W0Tl5mu3zFW5pmXnGInL1umUv1JcE6yE79WorCYf+xDPHnfAZfkozy7nzPdjdZrO tV1PVdNg+tpPzJzD3JC8/x+YonvOolpvVCBRiJ43c5s80pV3yNglavPNEe/TEkFE ULwzvAbp72HyBirFX1S0aTlLbI85oRrxzcGfZrao0HTA6tm9nj9rsjPWpbaGjjsQ oWcX2b6xjBu7ng73Hpi8BIaLj6ECrt0hdMUGAvDf1OnMdYzNjSqX8gpJjjOJJpDs QQwfkSeZW8IVF1Nm5U6QTJ9Mgbcma19EDQyARyCiAKnscFMMp+iWDs0pBmKfXqZA zHWeVlv7eqivC+qDfMmU =mU0y -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#782133: gobby: wrongly archived as metapackage
On 2015-04-08 12:21, Jonas Smedegaard wrote: In the control file, gobby is declared a metapackage - likely missed after the transition form gobby-0.5. Missed is the wrong word: #769030. Also no clue if all of them were changed. Kind regards Philipp Kern -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781907: Need More Information
Can you provide some example files in which we can test this? I have an armhf server, but we need some more information, such as replication steps, example files and example configs under which you can replicate these problems, etc. Without that kind of information, Im not sure this is actually able to be replicated. -- Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782240: lsat: erroneously deduces that X is listening for tcp connections
Package: lsat Version: 0.9.7.1-2 Severity: normal Dear Maintainer, lsat seems to look for the '-nolisten tcp' option in the startx command file, but Debian uses /etc/X11/xinit/xserverrc for that. Best Regards, Manolo Díaz -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.19.3 (SMP w/2 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages lsat depends on: ii libc6 2.19-17 lsat recommends no packages. Versions of packages lsat suggests: pn iproute none ii lsof 4.86+dfsg-1 ii nmap 6.47-3+b1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782267: unblock: debian-installer-netboot-images/20150324
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock x-debbugs-cc: debian-b...@lists.debian.org, o...@debian.org, debian-...@lists.debian.org Hi, please unblock debian-installer-netboot-images/20150324 so we get the latest d-i images from testing in testing: debian-installer-netboot-images (20150324) unstable; urgency=medium * Update to 20150324 images. * Use ftp.debian.org as mirror -- Didier Raboud o...@debian.org Mon, 30 Mar 2015 11:25:16 +0200 It's been in unstable since 9 days. cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#782227: posh: parameter expansion: string length ${#parameter} is incorrect on multibyte character
Control: retitle -1 posh doesn't support multibyte characters in string handling Same problem with: posh -c 'case é in ?) echo OK;; esac' which doesn't print OK in UTF-8 locales. -- Vincent Lefèvre vinc...@vinc17.net - Web: https://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: https://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782194: marco does not apply workspace name changes
HI all, On Do 09 Apr 2015 11:39:15 CEST, Vlad Orlov wrote: Source: marco Version: 1.8.2+dfsg1-6 Severity: important Tags: jessie sid Due to a logic error, Marco does not apply workspace name changes when it receives the notifications for them. This happens with any version of GLib, it's not related to the known GLib 2.43 issue. The upstream pull request [1] fixes the problem. [1] https://github.com/mate-desktop/marco/pull/188 just talked to Niels from the RT. Fixing this bug is on our pu list (jessie-proposed-updates) for Debian 8.1. Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpicWLKOO2Lu.pgp Description: Digitale PGP-Signatur
Bug#779565: Proposal for maintaining bamf in debian
Control: retitle -1 ITA: bamf -- Window matching library Hi Didier, On Do 09 Apr 2015 12:47:15 CEST, Didier Roche wrote: Hey, After Rico Tzschichholz's contacted me (and as the package is orphaned https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779565), I'm happy to propose your team to maintain bamf in debian. Hope that you will find useful. :) Cheers, Didier happily we (Debian MATE packaging team) take over your previous work on that package. This will allow us to make plank a success in Debian, as well(, amongst other things). light+love, Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpp5YL2P9G2k.pgp Description: Digitale PGP-Signatur
Bug#782190: pre-approve: nginx/1.6.3-1
Package: release.debian.org Severity: normal Hello, I have prepared an upload for nginx (1.6.3-1) and I'd like to request a pre-approval for jessie. 1.6.3 is the latest upstream stable bugfix release including 6 bug fixes[0]. One of them fixes a tcp nodelay issue with spdy that effectively makes spdy unusuitable for production use. Upstream already maintains a stable branch and has proven that it does it well, backporting only what's absolutely needed. I believe it is better for debian and nginx maintainers to follow suit and package 1.6.3 for jessie. I am attaching a debdiff or the proposed upload. (I'll also file a bug report for packaging 1.6.3 and include it the changelog). Upstream changelog: *) Feature: now the tcp_nodelay directive works with SPDY connections. *) Bugfix: in error handling. Thanks to Yichun Zhang and Daniil Bondarev. *) Bugfix: alerts header already sent appeared in logs if the post_action directive was used; the bug had appeared in 1.5.4. *) Bugfix: alerts sem_post() failed might appear in logs. *) Bugfix: in hash table handling. Thanks to Chris West. *) Bugfix: in integer overflow handling. Thanks to Régis Leroy. [0] tcp_nodelay is marked as a feature, but it's actually an important bugfix diff -Nru nginx-1.6.2/auto/unix nginx-1.6.3/auto/unix --- nginx-1.6.2/auto/unix 2014-09-16 15:23:19.0 +0300 +++ nginx-1.6.3/auto/unix 2015-04-07 18:58:37.0 +0300 @@ -489,6 +489,7 @@ ngx_type=time_t; . auto/types/sizeof ngx_param=NGX_TIME_T_SIZE; ngx_value=$ngx_size; . auto/types/value ngx_param=NGX_TIME_T_LEN; ngx_value=$ngx_max_len; . auto/types/value +ngx_param=NGX_MAX_TIME_T_VALUE; ngx_value=$ngx_max_value; . auto/types/value # syscalls, libc calls and some features diff -Nru nginx-1.6.2/CHANGES nginx-1.6.3/CHANGES --- nginx-1.6.2/CHANGES 2014-09-16 15:23:24.0 +0300 +++ nginx-1.6.3/CHANGES 2015-04-07 18:58:53.0 +0300 @@ -1,4 +1,23 @@ +Changes with nginx 1.6.3 07 Apr 2015 + +*) Feature: now the tcp_nodelay directive works with SPDY connections. + +*) Bugfix: in error handling. + Thanks to Yichun Zhang and Daniil Bondarev. + +*) Bugfix: alerts header already sent appeared in logs if the + post_action directive was used; the bug had appeared in 1.5.4. + +*) Bugfix: alerts sem_post() failed might appear in logs. + +*) Bugfix: in hash table handling. + Thanks to Chris West. + +*) Bugfix: in integer overflow handling. + Thanks to Régis Leroy. + + Changes with nginx 1.6.2 16 Sep 2014 *) Security: it was possible to reuse SSL sessions in unrelated contexts diff -Nru nginx-1.6.2/CHANGES.ru nginx-1.6.3/CHANGES.ru --- nginx-1.6.2/CHANGES.ru 2014-09-16 15:23:22.0 +0300 +++ nginx-1.6.3/CHANGES.ru 2015-04-07 18:58:47.0 +0300 @@ -1,4 +1,24 @@ +Изменения в nginx 1.6.3 07.04.2015 + +*) Добавление: теперь директива tcp_nodelay работает для + SPDY-соединений. + +*) Исправление: в обработке ошибок. + Спасибо Yichun Zhang и Даниилу Бондареву. + +*) Исправление: при использовании директивы post_action в лог писались + сообщения header already sent; ошибка появилась в nginx 1.5.4. + +*) Исправление: в лог могли писаться сообщения sem_post() failed. + +*) Исправление: в обработке хэш-таблиц. + Спасибо Chris West. + +*) Исправление: в обработке целочисленных переполнений. + Спасибо Régis Leroy. + + Изменения в nginx 1.6.2 16.09.2014 *) Безопасность: при использовании общего для нескольких блоков server diff -Nru nginx-1.6.2/debian/changelog nginx-1.6.3/debian/changelog --- nginx-1.6.2/debian/changelog2014-12-01 13:12:00.0 +0200 +++ nginx-1.6.3/debian/changelog2015-04-09 11:00:03.0 +0300 @@ -1,3 +1,11 @@ +nginx (1.6.3-1) unstable; urgency=medium + + [ Christos Trochalakis ] + * New upstream release. +Fixes tcp nodelay issue in spdy module. + + -- Christos Trochalakis yati...@ideopolis.gr Thu, 09 Apr 2015 10:57:26 +0300 + nginx (1.6.2-5) unstable; urgency=medium [ Christos Trochalakis ] diff -Nru nginx-1.6.2/src/core/nginx.h nginx-1.6.3/src/core/nginx.h --- nginx-1.6.2/src/core/nginx.h2014-09-16 15:23:19.0 +0300 +++ nginx-1.6.3/src/core/nginx.h2015-04-07 18:58:38.0 +0300 @@ -9,8 +9,8 @@ #define _NGINX_H_INCLUDED_ -#define nginx_version 1006002 -#define NGINX_VERSION 1.6.2 +#define nginx_version 1006003 +#define NGINX_VERSION 1.6.3 #define NGINX_VER nginx/ NGINX_VERSION #define NGINX_VAR NGINX diff -Nru nginx-1.6.2/src/core/ngx_config.h nginx-1.6.3/src/core/ngx_config.h --- nginx-1.6.2/src/core/ngx_config.h 2014-09-16 15:23:19.0 +0300 +++ nginx-1.6.3/src/core/ngx_config.h 2015-04-07
Bug#647441: xapian-bindings: python3-xapian
On Thu, Apr 09, 2015 at 10:04:03PM +0200, Matthias Klose wrote: fyi, I built packages to test the python3 bindings at https://launchpad.net/~doko/+archive/ubuntu/toolchain Note that 1.3.x is a development series, so xapian-core may change API and ABI incompatibly between releases - it's not really suitable for packaging. no documentation, the amd64 build fails (builds fine locally for me), the tcl tests fail. I'm aware of the tcl test failure - it seems to pick a recently added C++ Query constructor instead of the one it is meant to. I've not worked out exactly why yet though. Cheers, Olly -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782226: rpcbind: -h ignored, still binds on all interfaces
Package: rpcbind Version: 0.2.1-6 Severity: normal Dear Maintainer, the manpage says that I can use -h address to make rpcbind only bind to this address (or several, if used multiple times), instead if IN_ADDR_ANY. Unfortunately, this is not true. Consider this: $ ps auwwx|grep rpc root 3862 0.0 0.0 37068 2396 ?Ss 12:39 0:00 /sbin/rpcbind -h 127.0.0.1 -h ::1 -l $ $ netstat -an |grep -F :111 tcp0 0 0.0.0.0:111 0.0.0.0:* LISTEN tcp6 0 0 :::111 :::*LISTEN udp0 0 127.0.0.1:111 0.0.0.0:* udp6 0 0 ::1:111 :::* $ # lsof -i udp@0.0.0.0:111 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME rpcbind 3862 root6u IPv4 39531536 0t0 UDP localhost:sunrpc # In other words, rpcbind still binds to IN_ADDR_ANY, despite the man page saying otherwise. Please also consider these related bugs: #621807, #737276 Kind regards, --Toni++ similar -- 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.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 rpcbind depends on: ii initscripts 2.88dsf-58 ii insserv 1.14.0-5 ii libc62.19-17 ii libtirpc10.2.5-1 ii libwrap0 7.6.q-25 ii lsb-base 4.1+Debian13+nmu1 rpcbind recommends no packages. rpcbind suggests no packages. -- no debconf information -- Mit freundlichen Gruessen / Kind regards / 祝好, Toni Mueller. Dipl.-Inf. Oeko.neT Mueller Brandt GbR fon +49 2241 1488440 http://www.oeko.net TM28-RIPEAS29394 Software Development in Python (Plone, Pyramid, Django), IT Security, Linux, OpenBSD, Hosting, Unix Systems Administration, Consulting GPG: 4096R/96563E79 B213:F65C:0C8D:B6F9:9434::E92B:9428:82D6:9656:3E79 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773171: epoll_ctl failed increasing number of open file descriptors
We are going to build our own packages directly from sources and thus not sure whether I will be able to test. On Thu, Apr 9, 2015 at 3:25 PM, Michael Biebl bi...@debian.org wrote: Hi Peter, Am 15.12.2014 um 11:05 schrieb Peter Viskup: Package: rsyslog Version: 5.8.11-3 Severity: Important Rsyslog doesn't release sockets causing the continuous increase of open file descriptors till the MaxOpenFiles reached (epoll_ctl failed message is an consequence of this behaviour). Looks like it's caused by the bug in GunTLS session handling. Review https://bugzilla.redhat.com/show_bug.cgi?id=848852 for reference. The patch has been implemented already, but causing some performance issues unfortunately. Would be good to review the code and include it in the updates. Can you confirm that this issue is fixed in jessie (8.4.2-1) or the version from wheezy-backports (7.6.3-2~bpo70+1)? Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
Bug#747663: mpv: hwdev=vaapi has bad quality output
Hi Kurt On 2014-05-10 22:55:09, Kurt Roeckx wrote: Package: mpv Version: 0.3.9-1 Hi, I've been using hwdec=vaapi for a while now and things looked good. Yesterday I upgraded from 0.3.8-1 to 0.3.9-1 and everything I look at now looks really bad. It seems that it starts good but then as it's updating the quality gets worse and worse like it's blurred. Sometimes you suddenly see that it improves a lot, and I guess that is when there is a new full frame or something. I've only looked at h264 content, and full screen. Commenting out the hwdec=vaapi from the config gives me back normal quality. Is this still an issue with libav 6:11.3-1? If so, could you please attach a verbose log from mpv? Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#782239: txt2html: New upstream version
Package: txt2html Version: 2.51-1 Severity: normal Tags: patch upstream Dear Maintainer, There is a new upstream version for txt2html (version 2.52). This patch will improve the debian/watch file: --- txt2html-2.51/debian/watch 2015-04-09 09:51:11.0 -0300 +++ txt2html-2.51-new/debian/watch 2015-04-09 09:52:27.505728513 -0300 @@ -1,2 +1,3 @@ version=3 http://sf.net/txt2html/ txt2html-(.*)\.tar\.gz debian debian/orig-tar.sh +http://search.cpan.org/~rubykat/txt2html-2.5201 /CPAN/authors/id/R/RU/RUBYKAT/txt2html-(\d\S+)\.tar\.(?:bz2|gz|xz) Have anice day! Regards, Eriberto -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages txt2html depends on: ii libgetopt-argvfile-perl 1.11-1 ii libyaml-syck-perl1.27-2+b2 ii perl 5.20.2-3 txt2html recommends no packages. Versions of packages txt2html suggests: pn perl-doc none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774816: wongfix it
Hi, Since it's useless to work on it (as oslo.messaging wont accept the password anyway), I have no choice but to wontfix this bug. Feel free to re-open if oslo.messaging gets fixed though. Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782238: duplicity: documentation to connect to European S3 bucket is wrong/misleading
Package: duplicity Version: 0.6.24-1 Severity: normal To connect to an S3 bucket in Frankfurt, if one reads the documentation, they get the impression they should be using --s3-use-new-style. Not only this doesn't work, but it prevents the (undocumented) workaround to work which is to export S3_USE_SIGV4=True. Either the documentation should be fixed, including the workaround, or (better?) duplicity should be able to select the correct authentication method for the s3-eu-central-1 endpoint. -- 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_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages duplicity depends on: ii libc62.19-17 ii librsync10.9.7-10 ii python 2.7.9-1 ii python-lockfile 1:0.8-2 Versions of packages duplicity recommends: ii python-oauthlib 0.6.3-1 ii python-paramiko 1.15.1-1 ii python-urllib3 1.9.1-3 ii rsync3.1.1-3 Versions of packages duplicity suggests: pn lftpnone ii ncftp 2:3.2.5-1.1 ii python-boto 2.34.0-2 pn python-cloudfiles none pn python-gdatanone pn python-swiftclient none pn tahoe-lafs none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782269: workaround for upgrade failures not working, bashisms is preinst
On 04/09/2015 10:38 PM, Olly Betts wrote: Control: tag -1 +pending On Thu, Apr 09, 2015 at 07:51:16PM +0200, Matthias Klose wrote: Preparing to unpack .../ruby-xapian_1.2.19-1_amd64.deb ... /var/lib/dpkg/tmp.ci/preinst: 6: [: missing ] /var/lib/dpkg/tmp.ci/preinst: 7: /var/lib/dpkg/tmp.ci/preinst: -x: not found Unpacking ruby-xapian (1.2.19-1) ... Setting up ruby-xapian (1.2.19-1) ... bashisms in the preinst: case $1 in install|upgrade) if [ -f /usr/share/doc-base/ruby-xapian-in -a -x /usr/sbin/install-docs ] ; then # Workaround for upgrade failure reported in #735418. It's not a bashism - it doesn't work under bash either! It looks to me to be just a missing line-continuation (\) - if I fix that this works under both bash and dash. Thanks for spotting this. I have pushed a fix to the git repo, and will upload shortly. -a is not available everywhere. can you make it [ ...] [ ... ]? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#620456: Please move /tmp/gpg-XXXXXX directories to $XDG_RUNTIME_DIR
Package: gnupg-agent Version: 2.0.26-6 Followup-For: Bug #620456 Apart from cluttering /tmp, placing the temporary directories there suffers from automatic /tmp cleaning. Since some time I lose the socket directories in /tmp in a week after I start my session. Perhaps this is some systemd-related task that swipes /tmp, but I haven't found it yet. Moving /tmp/gpg-XX directories to $XDG_RUNTIME_DIR would fix the above /tmp cleaning problem too. As a workaround, using --use-standard-socket option causes the sockets to be put in ~/.gnupg using fixed names, which solves both the problem I have above and the problem of cluttering the temporary directories location since no new directory is created with each session. Cheers, dam -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/3 CPU cores) Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnupg-agent depends on: ii libassuan0 2.1.2-2 ii libc6 2.19-17 ii libgcrypt20 1.6.3-2 ii libgpg-error0 1.17-3 ii libpth202.0.7-20 ii libreadline66.3-8+b3 ii pinentry-curses [pinentry] 0.8.3-2 ii pinentry-gtk2 [pinentry]0.8.3-2 Versions of packages gnupg-agent recommends: ii gnupg 1.4.18-7 ii gnupg2 2.0.26-6 ii gpgsm 2.0.26-6 gnupg-agent 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#769030: closed by Debian FTP Masters ftpmas...@ftp-master.debian.org (Bug#769030: fixed)
Hi, Philipp Kern pk...@debian.org writes: On 2015-04-09 12:39, ow...@bugs.debian.org wrote: #769030: override: gobby-infinote:oldlibs/extra, gobby-0.5:oldlibs/extra, gobby-0.5-dbg:oldlibs/extra, gobby:net/optional [...] We believe that the bug you reported is now fixed; the following changes were made to the overrides... Concerning package gobby-infinote... Operating on the unstable suite Changed priority from optional to extra Changed section from net to oldlibs was this the only change applied? Because there were more packages in the subject. No, I updated the other two packages as well. However dak override can only update one package at a time so I closed the bug report with the first of the changes. Ansgar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780862: [PATCH v2 0/7] New Lenovos 2015 touchpads: party time!
Control: tag -1 +patch I'm adding the Debian bug number on To: so it gets the information, and I'm dropping other recipients to limit the noise. On jeu., 2015-04-09 at 09:56 -0400, Benjamin Tissoires wrote: I've opened a Debian bug [1] to request the patch serie to be backported to the 3.16 kernel used by Debian and Ubuntu, but Ben Hutchings asked for more information than just the merge commit id. The merge contains the following commits: 09d042a2eb90ee2c86d80c48ad096ae3f5776cef Revert Input: synaptics - use dmax in input_mt_assign_slots 6067fe5e0bf29f525561c8281d01011cfc9ebbd4 Merge branch 'synaptics' into for-linus 8f004f3f4daf5dc98dc78f8e62497ad834053855 Input: synaptics - remove X250 from the topbuttonpad list 860e6f7fcbe5653ec4e394f9ee335f2032398beb Input: synaptics - remove X1 Carbon 3rd gen from the topbuttonpad list cdd9dc195916ef5644cfac079094c3c1d1616e4c Input: synaptics - re-route tracksticks buttons on the Lenovo 2015 series 3adde1f59195df2965f632e22b31f97fb371612f Input: synaptics - remove TOPBUTTONPAD property for Lenovos 2015 06aa374bc70468b517dd36b95c48c8f391c08a27 Input: synaptics - retrieve the extended capabilities in query $10 b57a7128be24062b5b5b26032b7cd58f1651547e Input: synaptics - do not retrieve the board id on old firmwares ebc80840b850db72f7ae84fbcf77630ae5409629 Input: synaptics - handle spurious release of trackstick buttons dc5465dc8a6d5cae8a0e1d8826bdcb2e4cb261ab Input: synaptics - fix middle button on Lenovo 2015 products 02e07492cdfae9c86e3bd21c0beec88dbcc1e9e8 Input: synaptics - skip quirks when post-2013 dimensions 5b3089ddb540401c1ad2e385a03d7e89ff954585 Input: synaptics - support min/max board id in min_max_pnpid_table b05f4d1c332a22f98c037fa64f249aa30877adaf Input: synaptics - remove obsolete min/max quirk for X240 ac097930f0730a9b37de2b51e0fc49d2be7a Input: synaptics - query min dimensions for fw v8.1 9aff65982d0f58a78a27769fba7e97bc937b2593 Input: synaptics - log queried and quirked dimension values 8b04baba10b007f8b6c245a50be73cf09cc3a414 Input: synaptics - split synaptics_resolution(), query first Are they all needed or is there a more minimal but still working list? 8b04baba...b57a7128 are marked as stable@ and will/should be backported in debian too. Ben, I'm not sure if you handle the 3.16.x-ckt branch as well and how your prefer handling this case (let upstream/CKT handle those or include 8b04baba...b57a7128 in the Debian build)? This leaves us the minimum patches to backport in addition to those 9: 06aa374bc70468b517dd36b95c48c8f391c08a27 Input: synaptics - retrieve the extended capabilities in query $10 3adde1f59195df2965f632e22b31f97fb371612f Input: synaptics - remove TOPBUTTONPAD property for Lenovos 2015 cdd9dc195916ef5644cfac079094c3c1d1616e4c Input: synaptics - re-route tracksticks buttons on the Lenovo 2015 series Ok. 09d042a2eb (Revert Input: synaptics - use dmax in input_mt_assign_slots) is only required if the reverted commit is already in the debian tree, which I doubt given that it was introduced in v3.19 or v4.0. Ok, I don't think it's needed then. Thank your for your help! Ben, is that ok for you or can I help further? Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#782250: (no subject)
See also this PPA for possibly a start on the packaging: https://launchpad.net/~nebc/+archive/ubuntu/bio-linux/+packages?field.name_filter=pythonfield.status_filter=publishedfield.series_filter= pgpuduXtvU52R.pgp Description: OpenPGP digital signature
Bug#782196: fusionforge-minimal: Removing fusionforge-minimal is dangerous
Package: fusionforge-minimal
Severity: grave
Justification: causes non-serious data loss
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
- I simply tried to remove package with sudo aptitude remove
fusionforge-minimal --purge
* What exactly did you do (or not do) that was effective (or
ineffective)?
- I wanted to remove the package after a failed installation with error
message:
No database found online on port 5432
* What was the outcome of this action?
The uninstall proccess tried to remove critial paths, I mean / or /etc/
:
samuel@ipc:~$ sudo aptitude remove fusionforge-minimal --purge
The following packages will be REMOVED:
fusionforge-minimal gforge-common{pu} gforge-db-postgresql{pu}
gforge-lists-mailman{pu} gforge-mta-exim4{pu} gforge-web-apache2{pu}
javascript-common{pu} libjs-jquery{pu} libjs-jquery-tipsy{pu}
libjs-jquery-ui{pu} libjs-jquery-ui-theme-overcast{pu}
libmail-sendmail-perl{pu} libnusoap-php{pu} libphp-simplepie{pu}
libsort-versions-perl{pu} libsys-hostname-long-perl{pu}
libtext-autoformat-perl{pu} libtext-reform-perl{pu} lockfile-progs{pu}
mailman{pu} php-htmlpurifier{pu} php-http{pu} php-http-webdav-server{pu}
php5-intl{pu} php5-pgsql{pu} postgresql{pu} python-dnspython{pu}
0 packages upgraded, 0 newly installed, 27 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 56.6 MB will be freed.
Do you want to continue? [Y/n/?]
(Reading database ... 156092 files and directories currently installed.)
Removing fusionforge-minimal (5.3.2+20141104-3) ...
(Reading database ... 156087 files and directories currently installed.)
Removing gforge-web-apache2 (5.3.2+20141104-3) ...
Purging configuration files for gforge-web-apache2 (5.3.2+20141104-3) ...
Removing gforge-lists-mailman (5.3.2+20141104-3) ...
Purging configuration files for gforge-lists-mailman (5.3.2+20141104-3) ...
rmdir: failed to remove ‘/etc’: Directory not empty
rmdir: failed to remove ‘/’: Device or resource busy
rmdir: failed to remove ‘/’: Device or resource busy
rmdir: failed to remove ‘/etc/exim4/conf.d/main’: Directory not empty
rmdir: failed to remove ‘/etc/exim4/conf.d’: Directory not empty
rmdir: failed to remove ‘/etc/exim4’: Directory not empty
rmdir: failed to remove ‘/etc/exim4’: Directory not empty
rmdir: failed to remove ‘/etc’: Directory not empty
rmdir: failed to remove ‘/’: Device or resource busy
rmdir: failed to remove ‘/etc/exim4/conf.d/router’: Directory not empty
rmdir: failed to remove ‘/etc/exim4/conf.d’: Directory not empty
rmdir: failed to remove ‘/etc/exim4’: Directory not empty
rmdir: failed to remove ‘/etc’: Directory not empty
rmdir: failed to remove ‘/’: Device or resource busy
rmdir: failed to remove ‘/’: Device or resource busy
rmdir: failed to remove ‘/etc/exim4/conf.d/main’: Directory not empty
rmdir: failed to remove ‘/etc/exim4/conf.d’: Directory not empty
rmdir: failed to remove ‘/etc/exim4’: Directory not empty
rmdir: failed to remove ‘/etc/exim4’: Directory not empty
rmdir: failed to remove ‘/etc’: Directory not empty
rmdir: failed to remove ‘/’: Device or resource busy
rmdir: failed to remove ‘/etc/exim4/conf.d/router’: Directory not empty
rmdir: failed to remove ‘/etc/exim4/conf.d’: Directory not empty
rmdir: failed to remove ‘/etc/exim4’: Directory not empty
rmdir: failed to remove ‘/etc’: Directory not empty
rmdir: failed to remove ‘/’: Device or resource busy
rmdir: failed to remove ‘/’: Device or resource busy
rmdir: failed to remove ‘/etc/exim4/conf.d/main’: Directory not empty
rmdir: failed to remove ‘/etc/exim4/conf.d’: Directory not empty
rmdir: failed to remove ‘/etc/exim4’: Directory not empty
rmdir: failed to remove ‘/etc/exim4’: Directory not empty
rmdir: failed to remove ‘/etc’: Directory not empty
rmdir: failed to remove ‘/’: Device or resource busy
rmdir: failed to remove ‘/etc/exim4/conf.d/router’: Directory not empty
rmdir: failed to remove ‘/etc/exim4/conf.d’: Directory not empty
rmdir: failed to remove ‘/etc/exim4’: Directory not empty
rmdir: failed to remove ‘/etc’: Directory not empty
rmdir: failed to remove ‘/’: Device or resource busy
rmdir: failed to remove ‘/’: Device or resource busy
rmdir: failed to remove ‘/etc/exim4/conf.d/main’: Directory not empty
rmdir: failed to remove ‘/etc/exim4/conf.d’: Directory not empty
rmdir: failed to remove ‘/etc/exim4’: Directory not empty
rmdir: failed to remove ‘/etc/exim4’: Directory not empty
rmdir: failed to remove ‘/etc’: Directory not empty
rmdir: failed to remove ‘/’: Device or resource busy
rmdir: failed to remove ‘/etc/exim4/conf.d/router’: Directory not empty
rmdir: failed to remove ‘/etc/exim4/conf.d’: Directory not empty
rmdir: failed to remove ‘/etc/exim4’: Directory not empty
rmdir: failed to remove ‘/etc’: Directory not empty
rmdir: failed to remove ‘/’: Device or resource busy
rmdir: failed to remove ‘/’: Device or resource busy
rmdir:
Bug#782058: Pegasos II: installer boots up to 'returning from prom_init'
On Thu, 2015-04-09 at 08:24 -0400, Milan Kupcevic wrote: [...] Your understanding of the consequences of your changes is trully stellar. [...] Well, I've asked, no one complained until you showed up. The resulting discussion spreads very interesting scent. [...] Let's try to keep this civil, please. Ben. -- Ben Hutchings I'm always amazed by the number of people who take up solipsism because they heard someone else explain it. - E*Borg on alt.fan.pratchett signature.asc Description: This is a digitally signed message part
Bug#686052: python-software-properties: add-apt-repository may add a wrong suite for PPAs
Package: software-properties-common Version: 0.92.25debian1 Followup-For: Bug #686052 simple thing to check PPA existence: wget -q --spider [PPA_URL]/dists/[DISTRO]/Release -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (510, 'unstable'), (510, 'testing'), (500, 'utopic'), (500, 'trusty'), (500, 'precise'), (500, 'stable'), (100, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.16.7-ckt4-empee584 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages software-properties-common depends on: ii ca-certificates 20141019 ii gir1.2-glib-2.0 1.42.0-2.2 ii python3 3.4.2-2 ii python3-dbus 1.2.0-2+b3 ii python3-gi 3.14.0-1 ii python3-software-properties 0.92.25debian1 software-properties-common recommends no packages. software-properties-common 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#779834: redmine with redmine_dmsf yields a locale error
Hi! [...] The interesting part here is that somehow /usr/lib/ruby/vendor_ruby/../locales/en.yml gets added to the list of translations to load; this path, of course, does not exist and the loading fails. [...] /usr/lib/ruby/vendor_ruby/../locales/en.yml, [...] Can you look for the guilty package in your system? I think this command should find something: $ grep -rl /__FILE__.*\.\.\/locales/ /usr/lib/ruby/vendor_ruby/ Thank you for helping me out! simple_enum (the legacy-1.x branch[1]) is the culprit: | # setup i18n load path... | I18n.load_path File.join(File.dirname(__FILE__), '..', 'locales', 'en.yml') Please close that bug report; I'll file a bug for simple_enum... Thanks and sorry for the noise! -- Adi [1] https://github.com/lwe/simple_enum/blob/legacy-1.x/lib/simple_enum.rb signature.asc Description: Digital signature
Bug#782209: dbar: please make the build reproducible
Source: dbar Version: 0.0.20100524-3 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Hi! While working on Debian's “reproducible builds” effort [1], we have noticed that dbar doesn't build reproducibly. It embeds the current date into the manpage. The attached patch fixes this by using the last changelog date as a timestamp that will be embedded. Regards, Reiner [1]: https://wiki.debian.org/ReproducibleBuilds diff --git a/debian/pod2man.mk b/debian/pod2man.mk index 64bc797..f878a28 100644 --- a/debian/pod2man.mk +++ b/debian/pod2man.mk @@ -34,9 +34,10 @@ endif PACKAGE ?= package # Optional variables to set +BUILD_DATE ?= $$(dpkg-parsechangelog -S Date -lchangelog) MANSECT ?= 1 PODCENTER ?= User Commands -PODDATE = $$(date +%Y-%m-%d) +PODDATE = $$(date -u +%Y-%m-%d -d $(BUILD_DATE)) # Directories MANSRC = signature.asc Description: OpenPGP digital signature
Bug#768618:
I'm not into the deadlines for jessie release but is there still a chance to get pacemaker back into the upcoming jessie release? This is quite a show stopper to ship debian 8 without a working cluster stack. Cheers, Stefan
Bug#712509: No Subject
Hey Ondřej.
I've just saw you closed #712509, which, AFAICS, has actually worked
before for quite a while.
Was this just catching up with already solved issues? Cause #712509
wasn't mentioned in the changelog for 5.5.0+dfsg-7.
Best wishes,
Chris.
On Thu, 2015-04-09 at 17:08 +0200, Ondřej Surý wrote:
Version: 5.5.0+dfsg-7
php5 (5.5.0+dfsg-7) unstable; urgency=low
[ Ondřej Surý ]
* This release introduces several major packaging changes:
+ php5{en,dis}mod now accepts -s SAPI argument to selectively
enable/disable module for specific SAPI; The -s also accepts ALL
as an argument (Closes: #505743)
+ php5{en,dis}mod now records a state for a module and has two
modi operandi: local administrator and maintainer script
This has been lousely modeled after apache2 packaging scripts.
Thanks Arno Töll for his work on dh_apache2, I have used some
parts of it.
+ Packages can now depend on dh_php5 (provided by php5-dev) which
provides: dh_php5, dh_phpize and dh_phpize_clean (also with dh
integration). See php-apcu for an example how to build an PHP 5
extension now. The scripts definitely needs some improvements
since I can't read nor write perl code without getting dizzy.
+ There's a new php5query script (again lousely modeled after
Apache 2 a2query script) which you can use to query status of
module (-m) and/or SAPI (-s) and also to list modules (-M) and
SAPIs (-S).
+ This still needs more documentation and less ducktape.
Contributions
are welcome and to be discussed in pkg-php-maint mailing list
first.
-- Ondřej Surý ond...@debian.org Tue, 09 Jul 2013 11:37:57 +0200
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782241: locales: On upgrade, generic locales as C.UTF-8 are lost in /etc/default/locale
Package: locales Version: 2.19-17 Severity: serious Tags: patch Justification: valid administator configuration is lost on upgrade Hi, The current debconf script for the 'locales' package does not allow to choose the C.UTF-8 locale. Moreover, if an administrator write this valid value for the LANG variable in /etc/default/locale, the value will be overwritten as soon as the 'locales' package is reconfigurated. If I correctly follow the logic of the config script, one goal is to ensure that the chosen value is correct (i.e. supported). So, the current value is not always put in the debconf proposed list. However, the C.UTF-8 value is valid (as are C and POSIX but I'm less sure of their value). So, either the C.UTF-8 value (and perhaps C and POSIX) should be proposed when selecting the default environment locale, or, at very least, the config script must allow to keep it when it has manually be put into /etc/default/locale by the administrator. If you want to always allow this value, the current patch is enough: === --- locales.config 2015-03-14 10:30:53.0 +0100 +++ /tmp/locales.config 2015-04-09 15:05:40.257852467 +0200 @@ -547,9 +547,12 @@ fi DEFAULT_LOCALES=$(echo $RET | sed -e 's/ [^ ]*,/,/g' -e 's/ [^ ]*$//') if [ -n $DEFAULT_LOCALES ]; then -db_subst locales/default_environment_locale locales $DEFAULT_LOCALES -db_input medium locales/default_environment_locale || true +DEFAULT_LOCALES=C, C.UTF-8, POSIX, $DEFAULT_LOCALES +else +DEFAULT_LOCALES=C, C.UTF-8, POSIX fi +db_subst locales/default_environment_locale locales $DEFAULT_LOCALES +db_input medium locales/default_environment_locale || true ;; *) break === Feel free to adjust the list of always supported locales (ie C and POSIX) If you want to only allow the C, C.UTF-8, and POSIX locales when they have been manually set up (so they do not show up on default install), I can provide an updated patch. Just tell me. Regards, Vincent -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armel, mipsel Kernel: Linux 3.19.0-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages locales depends on: ii debconf [debconf-2.0] 1.5.56 ii libc-bin 2.19-17 locales recommends no packages. locales suggests no packages. -- debconf information: locales/default_environment_locale: None locales/locales_to_be_generated: fr_FR.UTF-8 UTF-8 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782256: fail2ban: Removing package does not cleanup /etc/logrotate.d/fail2ban
Package: fail2ban Version: 0.8.13-1 Severity: normal Hi, It seems the file /etc/logrotate.d/fail2ban gets left behind after removing fail2ban. This causes cron to generate errors as fail2ban-client does not exist. Regards Wouter -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782255: icedove: does not mark all messages as forwarded
Package: icedove Version: 36.0~b1-1 Severity: minor -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 When forwarding multiple messages as attachments, only the first is marked as forwarded. - -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/lksh Init: systemd (via /run/systemd/system) Versions of packages icedove depends on: ii debianutils 4.4+b1 ii fontconfig2.11.0-6.3 ii libasound21.0.28-1 ii libatk1.0-0 2.14.0-1 ii libc6 2.19-16 ii libcairo2 1.14.0-2.1 ii libdbus-1-3 1.8.16-1 ii libdbus-glib-1-2 0.102-1 ii libevent-2.0-52.0.21-stable-2 ii libffi6 3.1-2+b2 ii libfontconfig12.11.0-6.3 ii libfreetype6 2.5.2-3 ii libgcc1 1:4.9.2-10 ii libgdk-pixbuf2.0-02.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libgtk2.0-0 2.24.25-3 ii libhunspell-1.3-0 1.3.3-3 ii libnspr4 2:4.10.7-1 ii libnss3 2:3.17.2-1.1 ii libpango-1.0-01.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpangoft2-1.0-0 1.36.8-3 ii libpixman-1-0 0.32.6-3 ii libsqlite3-0 3.8.7.4-1 ii libstartup-notification0 0.12-4 ii libstdc++64.9.2-10 ii libvpx1 1.3.0-3 ii libx11-6 2:1.6.2-3 ii libxcomposite11:0.4.4-1 ii libxdamage1 1:1.1.4-2+b1 ii libxext6 2:1.3.3-1 ii libxfixes31:5.0.1-2+b2 ii libxrender1 1:0.9.8-1+b1 ii libxt61:1.1.4-1+b1 ii psmisc22.21-2 ii zlib1g1:1.2.8.dfsg-2+b1 Versions of packages icedove recommends: ii hunspell-de-at [hunspell-dictionary] 20131206-5 ii hunspell-de-ch [hunspell-dictionary] 20131206-5 ii hunspell-de-de [hunspell-dictionary] 20131206-5 ii hunspell-en-us [hunspell-dictionary] 20070829-6 Versions of packages icedove suggests: ii fonts-lyx 2.1.3-1 ii libgssapi-krb5-2 1.12.1+dfsg-18 - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQJOBAEBCAA4BQJVJo5cMRpodHRwczovL3d3dy5kb21pbmlrLWdlb3JnZS5kZS9n cGctcG9saWN5LnR4dC5hc2MACgkQt5o8FqDE8pYgNBAAhNqWL5N7rnondy/Vs/2z R1bNySJwHJISTNXs5u0WFxnwkghyzxFjynCmEB4mzQ6m3prF+P+U55pR15YYUmQD BxWJckrt3qndf/Z3xBkzrWTu0keXRGJO8tTqt1qv6CfjtmawqFfbKFTIylLyFZ8Y Otr9bqkwS1GM3bQ10hM83GephMFRrpLROb8pKAFP5I0Pmq1aTAdvv+r0toKb3Zka qJkYqqKnd/jhK4LCLDhJPcPqX4uw+hGDtPjmk6WXg49TxLZeX9nlZVOWKlntCa0w dEgbRG0yO3CWc+ZcfCzH26zH89AzQP9vb7i8s12/OyCQj8/ZxJcAKaiujr6gPG48 Hy4IZk28hfL1oApm0wuj3Y07ru1/hFYa24359mT3MYfHz6xKQhHC75Lqs+B/PuKP r4cAmJoAIMUpfRcQhyTi7x3YKaXQ2HbBuAbuBgIODasyDJZ4ZDAWNW83uQUsOg/L 2WcwakYM/AnGQjpH5KWoPwVc+n4OO0NFerITR0EmR1PAFXolXm2Li5Abq+KzZmyj Y2fLvnD+UkHUUnvM9chqusbg2AWqJG2ryjiPj3ZZ3t7CMKpnSaIhUNXhnLEMi3fa x1GL3Nu95fDuT/99GPv0DDhS6Rsxby3FXh7QgOxWTaVzJv9zL6N6zJDK79wp2nLD hi4ykv77gErNq0tk7Aa5PV8= =hjVt -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#782242: O: xombrero -- minimalist web browser
Package: wnpp Severity: normal I intend to orphan the xombrero package. The main issues in Xombrero (xxxterm in the past): 1. Xombrero is an old software but has some bad behaviors, never solved by upstream. 2. Xombrero has lots of bugs. 3. The upstream is some times unresponsive. The package description is: xombrero is a minimalist web browser with sophisticated security features designed-in, rather than through an add-on after-the-fact. In particular, it provides both persistent and per-session controls for scripts and cookies, making it easy to thwart tracking and scripting attacks. . In addition to providing a familiar mouse-based interface like other web browsers, it offers a set of vi-like keyboard commands for users who prefer to keep their hands on their keyboard. . The default settings provide a secure environment. With simple keyboard commands, the user can whitelist specific sites, allowing cookies and scripts from those sites. . xombrero is light and has a very good performance when running over network connections, as SSH forwarded tunnels. . The major features are: - Tabbed browsing; - Written entirely in C; - Based on Webkit and GTK3, with GTK2 compatibility; - Built with security in mind; - Minimal on-screen layout; - Cookie, javascript and plugin toggles and whitelists; - Browsing session data auto-saves in case of crash; - Simple integration with Tor and other web proxies; - vi-like default keybindings; - Mouse-less browsing; - Basic MIME support; - Seamless upgrade process; - DNS and link prefetch disabled by default; - Colorful address bar indicates HTTPS certificate status; - Control over user_agent presented to sites; - Download manager; - Text-based config file; - Bookmarks, i.e. favorites; - Printing, including to PDF. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782197: apngdis: please make the build reproducible
Source: apngdis Version: 2.5-1 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Hi! While working on Debian's “reproducible builds” effort [1], we have noticed that apngdis doesn't build reproducibly. It embeds the current date into the manpage. The attached patch fixes this by using the last changelog date as a timestamp that will be embedded. Regards, Reiner [1]: https://wiki.debian.org/ReproducibleBuilds diff --git a/debian/pod2man.mk b/debian/pod2man.mk index 450fa9a..e8c7d36 100644 --- a/debian/pod2man.mk +++ b/debian/pod2man.mk @@ -38,9 +38,10 @@ endif PACKAGE ?= package # Optional variables to set +BUILD_DATE ?= $$(dpkg-parsechangelog -S Date -lchangelog) MANSECT ?= 1 PODCENTER ?= User Commands -PODDATE ?= $$(date +%Y-%m-%d) +PODDATE ?= $$(date -u +%Y-%m-%d -d $(BUILD_DATE)) # Directories MANSRC ?= signature.asc Description: OpenPGP digital signature
Bug#774044: Rake task incompatible with ruby-gettext 3.x
Hi Jan-Marek, Thanks for the bug report and the patch attached! Unfortunately, we were too slow on the treatment of this bug, so a new version of ruby-gettext-i18n-rails was now released. I just imported the new 1.2.3 version https://anonscm.debian.org/cgit/pkg-ruby-extras/ruby-gettext-i18n-rails.git/commit/?id=a52cd4330f64399bf93d239e3eeac9e58a383b2a Thanks! Seb -- Sebastien Badia signature.asc Description: Digital signature
Bug#659117: transmission-gtk: segfaults when torrent properties are opened/closed
Hi Sandro, The current transmission version in testing no longer crashes. It has been fixed. Thanks Simon Am 01.04.2015 um 22:47 schrieb Sandro Tosi: Hello Simon, sorry we didnt get back to you earlier. A lot of new versions have been uploaded to Debian, and I am unable to replicate this problem, are you? Regards, -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780865: any progress?
Any progress on patching up openafs? Thanks! C. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780352: initramfs-tools: Can't force fsck on remote systems
Control: tag -1 - moreinfo unreproducible Control: retitle -1 fsck log from initramfs is not documented On Thu, 2015-04-09 at 08:30 -0400, Jape Person wrote: On 04/08/2015 09:05 PM, Ben Hutchings wrote: Control: tag -1 unreproducible On Thu, 12 Mar 2015 10:25:34 -0400 jpw jap...@comcast.net wrote: Package: initramfs-tools Version: 0.119 Severity: important Dear Maintainer, A basic change in function for fsck at boot time has resulted following upgrade of this package from 0.116 to 0.119. Following deprecation of touch /forcefsck earlier this past year for forcing fsck at next reboot I started using a line in rc.local (tune2fs -c 0 /dev/sda1) to set maximum mount count so that in-depth file system checks would never occur unless I specified. I then issued tune2fs -c 1 /dev/sda1 from a root prompt on the remote systems to force the in-depth fsck on next reboot. The remote systems used to execute an in-depth fsck on the boot partition at next reboot when I followed this procedure. This function no longer works. [...] It works for me. However, the forced fsck is now done from the initramfs (for the root and /usr filesystems), not under systemd or initscripts. Is the real problem to do with logging the output of fsck? Ben. Hi! I was trying to force the type of fsck which results in a report of the % of discontiguous files on remote systems that I maintain. In the spirit of avoiding the use of the deprecated touch /forcefsck I was using a line (tune2fs -c 0 /dev/sda1) in rc.local to cause the check to never run unless I issued tune2fs -c 1 /dev/sda1 from a root prompt and then rebooted. So when you say that it works for you, do you mean that touch /forcefsck still gets the check for file system fragmentation, or that using the tune2fs trick works. Because, for me, touch /forcefsck still works (but I'm trying to avoid it), but using the tune2fs trick stopped working when initramfs-tools was upgraded from 0.116 to 0.119. I mean using 'tune2fs -c 1' before rebooting. By that, I mean that issuing systemctl status -l systemd-fsck-root.service stopped showing me % discontiguous following a reboot when I tried to run the full fsck check using the tune2fs command. [...] Right, so as I suspected you're talking about where the output is logged. Currently it's logged to /run/initramfs/fsck, but not documented. I'm intending to rename that to fsck.log (so it's obviously a log file) and to document it in the initramfs-tools(8) manual page. Ben. -- Ben Hutchings I'm always amazed by the number of people who take up solipsism because they heard someone else explain it. - E*Borg on alt.fan.pratchett signature.asc Description: This is a digitally signed message part
Bug#737276: bashism in proposed config file
Hi luka,
I appreciate your proposed config snippet, but unfortunately, it
contains a bashism and thus does not work. Here is a version that
does work with dash:
# /etc/init.d/rpcbind
OPTIONS=
# Cause rpcbind to do a warm start utilizing a state file (default)
# OPTIONS=-w
# Uncomment the following line to restrict rpcbind to localhost only for UDP
requests
OPTIONS=${OPTIONS} -h 127.0.0.1 -h ::1
# Uncomment the following line to enable libwrap TCP-Wrapper connection logging
OPTIONS=${OPTIONS} -l
Kind regards,
--Toni++
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782220: spamassassin-heatu: please make the build reproducible
Source: spamassassin-heatu Version: 3.02+20101108-2 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Hi! While working on Debian's “reproducible builds” effort [1], we have noticed that spamassassin-heatu doesn't build reproducibly. It embeds the current date into the manpage. The attached patch fixes this by using the last changelog date as a timestamp that will be embedded. Regards, Reiner [1]: https://wiki.debian.org/ReproducibleBuilds diff --git a/debian/pod2man.mk b/debian/pod2man.mk index 64bc797..f878a28 100644 --- a/debian/pod2man.mk +++ b/debian/pod2man.mk @@ -34,9 +34,10 @@ endif PACKAGE ?= package # Optional variables to set +BUILD_DATE ?= $$(dpkg-parsechangelog -S Date -lchangelog) MANSECT ?= 1 PODCENTER ?= User Commands -PODDATE = $$(date +%Y-%m-%d) +PODDATE = $$(date -u +%Y-%m-%d -d $(BUILD_DATE)) # Directories MANSRC = signature.asc Description: OpenPGP digital signature
Bug#782222: tabble: please make the build reproducible
Source: tabble Version: 0.43-2 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Hi! While working on Debian's “reproducible builds” effort [1], we have noticed that tabble doesn't build reproducibly. It embeds the current date into the manpage. The attached patch fixes this by using the last changelog date as a timestamp that will be embedded. Regards, Reiner [1]: https://wiki.debian.org/ReproducibleBuilds diff --git a/debian/pod2man.mk b/debian/pod2man.mk index 64bc797..f878a28 100644 --- a/debian/pod2man.mk +++ b/debian/pod2man.mk @@ -34,9 +34,10 @@ endif PACKAGE ?= package # Optional variables to set +BUILD_DATE ?= $$(dpkg-parsechangelog -S Date -lchangelog) MANSECT ?= 1 PODCENTER ?= User Commands -PODDATE = $$(date +%Y-%m-%d) +PODDATE = $$(date -u +%Y-%m-%d -d $(BUILD_DATE)) # Directories MANSRC = signature.asc Description: OpenPGP digital signature
Bug#782223: tinyirc: please make the build reproducible
Source: tinyirc Version: 1:1.1.dfsg.1-3 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Hi! While working on Debian's “reproducible builds” effort [1], we have noticed that tinyirc doesn't build reproducibly. It embeds the current date into the manpage. The attached patch fixes this by using the last changelog date as a timestamp that will be embedded. Regards, Reiner [1]: https://wiki.debian.org/ReproducibleBuilds diff --git a/debian/pod2man.mk b/debian/pod2man.mk index 3bbf697..ca56c1b 100644 --- a/debian/pod2man.mk +++ b/debian/pod2man.mk @@ -38,9 +38,10 @@ endif PACKAGE ?= package # Optional variables to set +BUILD_DATE ?= $$(dpkg-parsechangelog -S Date -lchangelog) MANSECT ?= 1 PODCENTER ?= User Commands -PODDATE ?= $$(date +%Y-%m-%d) +PODDATE ?= $$(date -u +%Y-%m-%d -d $(BUILD_DATE)) # Directories MANSRC ?= signature.asc Description: OpenPGP digital signature
Bug#782221: speedometer: please make the build reproducible
Source: speedometer Version: 2.8-1 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Hi! While working on Debian's “reproducible builds” effort [1], we have noticed that speedometer doesn't build reproducibly. It embeds the current date into the manpage. The attached patch fixes this by using the last changelog date as a timestamp that will be embedded. Regards, Reiner [1]: https://wiki.debian.org/ReproducibleBuilds diff --git a/debian/pod2man.mk b/debian/pod2man.mk index 64bc797..f878a28 100644 --- a/debian/pod2man.mk +++ b/debian/pod2man.mk @@ -34,9 +34,10 @@ endif PACKAGE ?= package # Optional variables to set +BUILD_DATE ?= $$(dpkg-parsechangelog -S Date -lchangelog) MANSECT ?= 1 PODCENTER ?= User Commands -PODDATE = $$(date +%Y-%m-%d) +PODDATE = $$(date -u +%Y-%m-%d -d $(BUILD_DATE)) # Directories MANSRC = signature.asc Description: OpenPGP digital signature
Bug#778876: linux-headers-3.19.0-trunk-amd64 is uninstallable.
Also adding myself to this bug report. I too would like to install a new Kernel, but linux-kbuild-3.19 is stopping me. So far I am also building the package myself using the Kernel sources and make deb-pkg. Greetings Bruno -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782245: tshark: Filtering regression when writing to file
Control: tags -1 wontfix upstream Control: severity -1 wishlist Control: forwarded -1 https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234 Dear Philipp, 2015-04-09 15:36 GMT+02:00 Ph. Marek philipp.ma...@linbit.com: Package: tshark Version: 1.12.1+g01b65bf-4 Severity: important Previously, a command like # tshark -w /tmp/bla portrange 22-23 or portrange 25-26 did work fine - I used something similar in some test scripts. With the current version, all that does is giving the usage output. Fine, let's specify the filter explicitly: # tshark -w /tmp/bla -R portrange 22-23 or portrange 25-26 tshark: -R without -2 is deprecated. For single-pass filtering use -Y. Grmbl. Okay, let's try this. # tshark -w /tmp/bla -R portrange 22-23 or portrange 25-26 -2 tshark: Live captures do not support two-pass analysis. Bah. Last resort: # tshark -w /tmp/bla -Y portrange 22-23 or portrange 25-26 tshark: Display filters aren't supported when capturing and saving the captured packets. Hmmm, maybe I'm using the wrong syntax? # tshark -w /tmp/bla -Y tcp.port == 22 or tcp.port == 25 tshark: Display filters aren't supported when capturing and saving the captured packets. Nope. So, how would I now capture to a file while using a filter? In short, you can't use a display filter this way. OTOH you can capture in a different process and pipe the result to tshark applying the display filter [1] or you can use _capture filters_ while capturing. For details please check tshark(1) (man tshark). Cheers, Balint [1] https://ask.wireshark.org/questions/25901/wireshark-capture-filter-syntax -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782269: workaround for upgrade failures not working, bashisms is preinst
Package: ruby-xapian Version: 1.2.19-1 Severity: serious Tags: sid jessie Preparing to unpack .../ruby-xapian_1.2.19-1_amd64.deb ... /var/lib/dpkg/tmp.ci/preinst: 6: [: missing ] /var/lib/dpkg/tmp.ci/preinst: 7: /var/lib/dpkg/tmp.ci/preinst: -x: not found Unpacking ruby-xapian (1.2.19-1) ... Setting up ruby-xapian (1.2.19-1) ... bashisms in the preinst: case $1 in install|upgrade) if [ -f /usr/share/doc-base/ruby-xapian-in -a -x /usr/sbin/install-docs ] ; then # Workaround for upgrade failure reported in #735418. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782203: apport: don't create .upload file is report is incomplete
Package: apport
Version: 2.16.2-2
Severity: important
The way apport works to determine if a crash has already been reported
or not, is by creating a .upload file for every successful report.
But, in its current form in Debian, even if the crash is incomplete, and
apport complains about its failure to send the report, it ends up
creating the .upload file, thus ignoring further crashes from it.
We need to intercept in between whether apport was able to determine the
completeness of the crash report, and then, accordingly, create a
.upload file, only when the report is submitted to the Debian BTS. In
case of Debian crashdb, that'd mean after the email is formatted and
submitted to the SMTP module.
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.19.3-bfq+ (SMP w/4 CPU cores)
Locale: LANG=en_IN.utf8, LC_CTYPE=en_IN.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages apport depends on:
ii gir1.2-glib-2.0 1.42.0-2.2
ii lsb-base 4.1+Debian13+nmu1
ii python3 3.4.2-2
ii python3-apport 2.16.2-2
ii python3-gi 3.14.0-1
pn python:any none
Versions of packages apport recommends:
ii policykit-1 0.105-8
Versions of packages apport suggests:
ii apport-gtk 2.16.2-2
-- Configuration Files:
/etc/apport/crashdb.conf changed:
default = 'debian-debug'
databases = {
'ubuntu': {
'impl': 'launchpad',
'bug_pattern_url':
'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
'dupdb_url':
'http://people.canonical.com/~ubuntu-archive/apport-duplicates',
'distro': 'ubuntu',
'escalation_tag': 'bugpattern-needed',
'escalated_tag': 'bugpattern-written',
},
'fedora': {
# NOTE this will change Fall '07 when RHT switches to bugzilla 3.x!
'impl': 'rhbugzilla',
'bug_pattern_url': 'http://qa.fedoraproject.org/apport/bugpatterns.xml',
'distro': 'fedora'
},
'debian': {
'impl': 'debian',
'distro': 'debian',
'smtphost': 'reportbug.debian.org',
'recipient': 'sub...@bugs.debian.org',
'sender': ''
},
'debian-debug': {
'impl': 'debian',
'distro': 'debian',
'smtphost': 'localhost',
'recipient': 'r...@debian.org',
'sender': 'r...@researchut.com'
},
'debug': {
# for debugging
'impl': 'memory',
'bug_pattern_url': '/tmp/bugpatterns.xml',
'distro': 'debug'
},
}
-- 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#762361: override: make-guile:devel/extra
Control: tag -1 + moreinfo d-i Hi, I'm going over the pending override changes and found another that affects the standard installation: #762361: make-guile: change priority from standard to extra There are no rdeps on make-guile, but it Provides: make; the make binary package itself has optional priority. Could the d-i team ack this change? Ansgar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762361: override: make-guile:devel/extra
Ansgar Burchardt ans...@debian.org (2015-04-09): Control: tag -1 + moreinfo d-i Hi, I'm going over the pending override changes and found another that affects the standard installation: #762361: make-guile: change priority from standard to extra There are no rdeps on make-guile, but it Provides: make; the make binary package itself has optional priority. Could the d-i team ack this change? Yep; can't see how that could blow up in our face. Mraw, KiBi. signature.asc Description: Digital signature
Bug#780352: initramfs-tools: Can't force fsck on remote systems
I am sure that a tune2fs -C -1 should suffice, as is normally the case to force an fsck. Robert On Mar 13, 2015 1:30 AM, jpw jap...@comcast.net wrote: Package: initramfs-tools Version: 0.119 Severity: important Dear Maintainer, A basic change in function for fsck at boot time has resulted following upgrade of this package from 0.116 to 0.119. Following deprecation of touch /forcefsck earlier this past year for forcing fsck at next reboot I started using a line in rc.local (tune2fs -c 0 /dev/sda1) to set maximum mount count so that in-depth file system checks would never occur unless I specified. I then issued tune2fs -c 1 /dev/sda1 from a root prompt on the remote systems to force the in-depth fsck on next reboot. The remote systems used to execute an in-depth fsck on the boot partition at next reboot when I followed this procedure. This function no longer works. So far, the only solution I have found would seem to be to make temporary changes in grub configuration on remote systems (via script or via manual editing) when I want to force a file system check at boot time. This seems inadvisable to me. Is there another solution, or can this functionality be restored by further changes to initramfs-tools? -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 15M Mar 11 10:03 /boot/initrd.img-3.16.0-4-amd64 -- /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=d6c0ac59-8f7c-438a-a87d-9f4f79ea58a1 ro initrd=/install/initrd.gz quiet -- resume RESUME=UUID=fad10f9d-8fa7-4f12-ab5c-a4d1e7a1a764 -- /proc/filesystems ext3 ext2 ext4 fuseblk -- lsmod Module Size Used by tun26385 0 binfmt_misc16949 1 asix 35194 0 usbnet 30844 1 asix libphy 32268 1 asix mii12675 2 asix,usbnet udl23117 0 drm_usb12469 1 udl udlfb 22180 0 nfsd 263032 2 auth_rpcgss51211 1 nfsd oid_registry 12419 1 auth_rpcgss nfs_acl12511 1 nfsd nfs 188136 0 lockd 83389 2 nfs,nfsd fscache45542 1 nfs sunrpc237402 6 nfs,nfsd,auth_rpcgss,lockd,nfs_acl joydev 17063 0 ip6t_REJECT12468 1 snd_usb_audio 135354 3 snd_usbmidi_lib23388 1 snd_usb_audio snd_rawmidi26806 1 snd_usbmidi_lib snd_seq_device 13132 1 snd_rawmidi x86_pkg_temp_thermal12951 0 intel_powerclamp 17159 0 arc4 12536 2 iwldvm135156 0 mac80211 474218 1 iwldvm intel_rapl 17356 0 coretemp 12820 0 kvm_intel 139116 0 kvm 388635 1 kvm_intel snd_hda_codec_hdmi 45118 1 xt_hl 12449 6 iTCO_wdt 12831 0 i915 837133 2 snd_hda_codec_conexant17841 1 snd_hda_codec_generic63107 1 snd_hda_codec_conexant ip6t_rt12456 3 iTCO_vendor_support12649 1 iTCO_wdt evdev 17445 33 nf_conntrack_ipv6 13605 7 iwlwifi96547 1 iwldvm snd_hda_intel 26327 4 crc32_pclmul 12915 0 cfg80211 405538 3 iwlwifi,mac80211,iwldvm psmouse98616 0 drm_kms_helper 49210 2 udl,i915 nf_defrag_ipv6 33358 1 nf_conntrack_ipv6 snd_hda_controller 26727 1 snd_hda_intel serio_raw 12849 0 ghash_clmulni_intel12978 0 mei_me 17941 0 thinkpad_acpi 69119 3 drm 249955 6 udl,i915,drm_usb,drm_kms_helper snd_hda_codec 104463 5 snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_hda_codec_generic,snd_hda_intel,snd_hda_controller ipt_REJECT 12465 1 nvram 13034 1 thinkpad_acpi lpc_ich20768 0 pcspkr 12595 0 mfd_core 12601 1 lpc_ich snd_hwdep 13148 2 snd_usb_audio,snd_hda_codec snd_pcm88662 5 snd_usb_audio,snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_controller mei74977 1 mei_me cryptd 14516 1 ghash_clmulni_intel snd_timer 26614 1 snd_pcm xt_LOG 17171 10 i2c_algo_bit 12751 1 i915 i2c_i801 16965 0 i2c_core 46012 5 drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit tpm_tis17182 0 wmi17339 0 snd65244 31 snd_usb_audio,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_pcm,snd_rawmidi,snd_hda_codec_generic,snd_usbmidi_lib,snd_hda_codec,snd_hda_intel,thinkpad_acpi,snd_seq_device shpchp 31121 0 tpm31511 1
Bug#781915: Patch (potential NMU) for multiple RC-grade issues in apt-zip
Thanks for having solved a lot of issues ;)
Only one problem remains in place: since I use the experimental
repository, the next upgrade shows many updates.
This happens because InRelease files are correctly in /var/lib/apt/lists
but the subsequent command:
[ -n $APTGETACTION ] apt-get ${APTGETEXTRAOPTS} ${APTGETACTION}
in /usr/sbin/apt-zip-inst removes them and creates .reverify files in
/var/lib/apt/lists/partial directory.
A little change to solve this:
...
if [ $APTGETACTION = update ]
then
APTGETEXTRAOPTS=-o Acquire::TryInRelease=0 ${APTGETEXTRAOPTS}
${APTGETCACHE}
else
APTGETEXTRAOPTS=${APTGETEXTRAOPTS} ${APTGETCACHE}
fi
[ -n $PACKAGES ] apt-get ${APTGETEXTRAOPTS} install $PACKAGES
[ -n $APTGETACTION ] apt-get ${APTGETEXTRAOPTS} ${APTGETACTION}
...
Thanks again for your work.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748618: syslinux-themes-debian: Fails to uninstall: extlinux-update: not found
tags 748618 patch
user ubuntu-de...@lists.ubuntu.com
usertag 748618 ubuntu-patch vivid
thanks
Patch below. I've applied this to Ubuntu. An identical patch also makes
sense for Debian.
diff -Nru syslinux-themes-debian-12/debian/changelog
syslinux-themes-debian-12/debian/changelog
--- syslinux-themes-debian-12/debian/changelog 2014-01-12 22:57:35.0
+
+++ syslinux-themes-debian-12/debian/changelog 2015-04-09 11:44:42.0
+0100
@@ -1,3 +1,10 @@
+syslinux-themes-debian (12-4) unstable; urgency=medium
+
+ * Check that extlinux-update exists before trying to run it in the postrm
+since it may already have been removed (Closes: #748618, LP: #1042511).
+
+ -- Robie Basak robie.ba...@ubuntu.com Thu, 09 Apr 2015 11:44:25 +0100
+
syslinux-themes-debian (12-3) unstable; urgency=low
* QA upload.
diff -Nru
syslinux-themes-debian-12/debian/syslinux-themes-debian-squeeze.postrm
syslinux-themes-debian-12/debian/syslinux-themes-debian-squeeze.postrm
--- syslinux-themes-debian-12/debian/syslinux-themes-debian-squeeze.postrm
2013-05-20 09:19:09.0 +0100
+++ syslinux-themes-debian-12/debian/syslinux-themes-debian-squeeze.postrm
2015-04-09 11:15:50.0 +0100
@@ -4,7 +4,7 @@
case ${1} in
remove)
- if [ -e /etc/default/extlinux ]
+ if [ -x /usr/sbin/extlinux-update -a -e /etc/default/extlinux ]
then
. /etc/default/extlinux
diff -Nru syslinux-themes-debian-12/debian/syslinux-themes-debian-wheezy.postrm
syslinux-themes-debian-12/debian/syslinux-themes-debian-wheezy.postrm
--- syslinux-themes-debian-12/debian/syslinux-themes-debian-wheezy.postrm
2013-05-20 09:19:09.0 +0100
+++ syslinux-themes-debian-12/debian/syslinux-themes-debian-wheezy.postrm
2015-04-09 11:16:09.0 +0100
@@ -4,7 +4,7 @@
case ${1} in
remove)
- if [ -e /etc/default/extlinux ]
+ if [ -x /usr/sbin/extlinux-update -a -e /etc/default/extlinux ]
then
. /etc/default/extlinux
diff -Nru syslinux-themes-debian-12/debian/syslinux-themes-debian.postrm
syslinux-themes-debian-12/debian/syslinux-themes-debian.postrm
--- syslinux-themes-debian-12/debian/syslinux-themes-debian.postrm
2013-05-20 09:19:09.0 +0100
+++ syslinux-themes-debian-12/debian/syslinux-themes-debian.postrm
2015-04-09 11:16:15.0 +0100
@@ -4,7 +4,7 @@
case ${1} in
remove)
- if [ -e /etc/default/extlinux ]
+ if [ -x /usr/sbin/extlinux-update -a -e /etc/default/extlinux ]
then
. /etc/default/extlinux
signature.asc
Description: Digital signature
Bug#782204: gdp: please support Arx Fatalis
Package: game-data-packager Version: 40 Severity: wishlist Tags: newcomer Dear Maintainer, Please add support for Arx Fatalis game, this game can be played with the arx-libertatis GPL'ed source port. This engine already search for files in the right place: /usr/share/games/arx . Upstream provides a 3200-lines shell script to unpack the data that uses: 7z, 7za, aterm, bsdtar, cabextract, curl, dcop, fetch, fuseiso, fusermount, gnome-terminal, greadlink, grealpath, gtkterm, gxmessage, innoextract, isoinfo, kdialog, konsole, md5, md5sum, mount, qdbus, realpath, rxvt, umount, unace, unrar, unshield, unzip, urxvt, wget, Xdialog, xmessage, xterm, x-terminal-emulator, zenity https://github.com/arx/ArxLibertatis/blob/master/scripts/arx-install-data http://wiki.arx-libertatis.org/Installing_the_game_data_under_Linux http://wiki.arx-libertatis.org/Linux_packages#Debian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782250: ITP: python-future -- use a single, clean Python 3.x-compatible codebase to support both Python 2 and Python 3 with minimal overhead
Package: wnpp Severity: wishlist Owner: Barry Warsaw ba...@debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 * Package name: python-future Version : 0.14.3 Upstream Author : Ed Schofield * URL : https://python-future.org/ * License : MIT/X Programming Lang: Python Description : use a single, clean Python 3.x-compatible codebase to support both Python 2 and Python 3 with minimal overhead Easy, clean, reliable Python 2/3 compatibility, this is the missing compatibility layer between Python 2 and Python 3. This package will be maintained within the DPMT. -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJVJoR7AAoJEBJutWOnSwa/R0cP/2omE2qkALBc0LMlWpc3P3ih Y1Zs4q/0ZyZ+/aa3sA9rfW18V9JY7APMh3FOXtxJNJKcGp3FygsTWtZOUNjtUAGf 45QU7e7NlJ8Y2iaqSeHiKjce+aoO2nB5KO/CYvtXNxMSUP/mGk2Bx81mLIziMEU+ V0QODuTQC64zSMplwvl+aT9VTrEAH/ChyzN43neWwZcfV9NbWQlDuaBqGtvNiJv4 FQKwIKfNI8G81QBqX8gTDnEsvYIu+5M+uoTqAaBGgC3NzkFcXeFPQrEZ4ub2Qu75 kUcpExKpaFN1dpvAY1J8SOgpxPVOKy4N/Tjo9UTH3wJG6Glutko7Jauy9+4H0cii hE3/qHSpxPncrRdvB2Pk34bGaOIOFpJtQYCQu7/oXxjiw6gjPBalYJQxrQIB6Gkz IULbKlfFRptpB4ZHlGLWMIks7SJcOiKZSBwf6s3pN2Mlee0WQBY4K409PfGF2xJC kR16QboIX8QoQs64anltTUuLf42dRZJrDj898CqPv8AzS8PI232QhTZzwDWfdzc+ uto/JFu56/ZZOfhGNlhiLYxjXeisUNgPAFGoXPZP9GqkQse8RxV3tw4sb6+iW+5a 9Jq6DJnfXKezl3wjy9AcVTRgLxy9thJRdaLXfVy9Kz4rig8fHeSmktTnki1HICd3 D1ii0n1UKmAhrQbzaxbt =njpk -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#620456: [Pkg-gnupg-maint] Bug#620456: Please move /tmp/gpg-XXXXXX directories to $XDG_RUNTIME_DIR
Version: 2.1.0-1 On Thu 2015-04-09 02:43:14 -0400, Damyan Ivanov wrote: Apart from cluttering /tmp, placing the temporary directories there suffers from automatic /tmp cleaning. Since some time I lose the socket directories in /tmp in a week after I start my session. Perhaps this is some systemd-related task that swipes /tmp, but I haven't found it yet. Moving /tmp/gpg-XX directories to $XDG_RUNTIME_DIR would fix the above /tmp cleaning problem too. agreed, this is suboptimal. As a workaround, using --use-standard-socket option causes the sockets to be put in ~/.gnupg using fixed names, which solves both the problem I have above and the problem of cluttering the temporary directories location since no new directory is created with each session. as of 2.1.0-1, gnupg2 always uses the standard socket option, so this problem is resolved there. the 2.1.x series is in experimental now, but i look forward to moving it to unstable after we release jessie. --dkg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772423: ITA: haskell-doc -- Assorted Haskell language documentation
retitle 772423 ITA: haskell-doc -- Assorted Haskell language documentation owner 772423! thanks Hello, I am interested in Haskell programming language and I am willing to take care of the package. Cheers, -- Alexandre Delanoë signature.asc Description: Digital signature
Bug#782212: [Pkg-openldap-devel] Bug#782212: MDB backend
Control: tag -1 fixed-upstream Control: forwarded -1 http://www.openldap.org/its/?findid=7975 On Thu, Apr 09, 2015 at 05:20:34PM +0200, Côme BERNIGAUD wrote: On 2015-04-09 17:18, Ryan Tandy wrote: The changelog for (not yet released) 2.4.41 has ITS#7975 which sounds similar: http://www.openldap.org/its/?findid=7975 Can you try applying the patch for that ITS? http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=patch;h=e6e073d31e89089a731870799b43de797480306d Indeed, this fixes the problem ! Great! Could this be applied for Jessie? It's the release team's decision. I will ask. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782229: Fix links to French TV icons
Package: vlc Version: 2.2.0~rc2-2 Tags: patch upstream Some links pointing to TV icons were broken. Attached patch fixes that. Typical output: [0x1e2ba18] access_http access error: error: HTTP/1.1 404 Not Found [0x1e2ba18] access_http access error: error: HTTP/1.1 404 Not Found [0x1e2ba18] access_mms access error: error: HTTP/1.1 403 Requested target domain not allowed. [0x1b3f7a8] main playlist error: no suitable access module for `http://upload.wikimedia.org/wikipedia/fr/4/4b/Logo_de_TMC.gif' [0x1e3fbc8] access_http access error: error: HTTP/1.1 404 Not Found [0x1e3fbc8] access_http access error: error: HTTP/1.1 404 Not Found [0x1e3fbc8] access_mms access error: error: HTTP/1.1 403 Requested target domain not allowed. [0x1b3f7a8] main playlist error: no suitable access module for `http://upload.wikimedia.org/wikipedia/fr/4/4b/Logo_de_TMC.gif' [0x4b52bc8] access_http access error: error: HTTP/1.1 404 Not Found [0x4b52bc8] access_http access error: error: HTTP/1.1 404 Not Found [0x4b52bc8] access_mms access error: error: HTTP/1.1 403 Requested target domain not allowed. [0x1b3f7a8] main playlist error: no suitable access module for `http://upload.wikimedia.org/wikipedia/fr/9/98/Public-Senat-LCP-An_logo_2010.png' [0x7fd8cc0133e8] access_http access error: error: HTTP/1.1 404 Not Found [0x7fd8cc0133e8] access_http access error: error: HTTP/1.1 404 Not Found [0x7fd8cc0133e8] access_mms access error: error: HTTP/1.1 403 Requested target domain not allowed. [0x1b3f7a8] main playlist error: no suitable access module for `http://upload.wikimedia.org/wikipedia/fr/9/98/Public-Senat-LCP-An_logo_2010.png' [0x3567038] access_http access error: error: HTTP/1.1 404 Not Found [0x3567038] access_http access error: error: HTTP/1.1 404 Not Found [0x3567038] access_mms access error: error: HTTP/1.1 403 Requested target domain not allowed. [0x1b3f7a8] main playlist error: no suitable access module for `http://upload.wikimedia.org/wikipedia/fr/3/30/Bfm_tv.jpg' [0x1ba7748] access_http access error: error: HTTP/1.1 404 Not Found [0x1ba7748] access_http access error: error: HTTP/1.1 404 Not Found [0x1ba7748] access_mms access error: error: HTTP/1.1 403 Requested target domain not allowed. [0x1b3f7a8] main playlist error: no suitable access module for `http://upload.wikimedia.org/wikipedia/fr/3/30/Bfm_tv.jpg' [0x1ba7748] access_http access error: error: HTTP/1.1 404 Not Found [0x1ba7748] access_http access error: error: HTTP/1.1 404 Not Found [0x1ba7748] access_mms access error: error: HTTP/1.1 403 Requested target domain not allowed. [0x1b3f7a8] main playlist error: no suitable access module for `http://upload.wikimedia.org/wikipedia/fr/3/30/Bfm_tv.jpg' [0x1ba7748] access_http access error: error: HTTP/1.1 404 Not Found [0x1ba7748] access_http access error: error: HTTP/1.1 404 Not Found [0x1ba7748] access_mms access error: error: HTTP/1.1 403 Requested target domain not allowed. [0x1b3f7a8] main playlist error: no suitable access module for `http://upload.wikimedia.org/wikipedia/fr/5/56/Logo_I_tele.png' Description: Fix broken links Author: Mathieu Malaterre ma...@debian.org Bug-Debian: https://bugs.debian.org/ --- vlc-2.2.0~rc2.orig/share/lua/meta/art/02_frenchtv.lua +++ vlc-2.2.0~rc2/share/lua/meta/art/02_frenchtv.lua @@ -38,11 +38,11 @@ function fetch_art() [W9] = http://cyril.bourreau.free.fr/Vectoriel/W9.png;, [Arte] = http://www.artepro.com/fr_fichiers/upload/10594.jpg;, -[TMC] = http://upload.wikimedia.org/wikipedia/fr/4/4b/Logo_de_TMC.gif;, -[i TELE] = http://upload.wikimedia.org/wikipedia/fr/5/56/Logo_I_tele.png;, -[BFM TV] = http://upload.wikimedia.org/wikipedia/fr/3/30/Bfm_tv.jpg;, +[TMC] = http://upload.wikimedia.org/wikipedia/fr/2/2e/TMC_new.svg;, +[i TELE] = http://upload.wikimedia.org/wikipedia/commons/a/a6/Logo_i_TELE_2013.png;, +[BFM TV] = http://upload.wikimedia.org/wikipedia/fr/c/c9/BFMTV_HD.png;, [Virgin 17] = http://upload.wikimedia.org/wikipedia/fr/3/39/Virgin17logo.png;, -[La Chaîne Parlementaire] = http://upload.wikimedia.org/wikipedia/fr/9/98/Public-Senat-LCP-An_logo_2010.png; +[La Chaîne Parlementaire] = http://upload.wikimedia.org/wikipedia/fr/1/1f/LCP-Public_Senat_logo.png; } local meta = vlc.item:metas(); local channel
Bug#720590: closed by Ansgar Burchardt ans...@debian.org (Re: dgit would like various information (also available anonymously))
Debian Bug Tracking System writes (Bug#720590 closed by Ansgar Burchardt ans...@debian.org (Re: dgit would like various information (also available anonymously))): api.ftp-master.debian.org now exists. If additional queries are needed, please open a new bug report for them. Indeed, all very helpful. Thank you. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773171: epoll_ctl failed increasing number of open file descriptors
Hi Peter, Am 15.12.2014 um 11:05 schrieb Peter Viskup: Package: rsyslog Version: 5.8.11-3 Severity: Important Rsyslog doesn't release sockets causing the continuous increase of open file descriptors till the MaxOpenFiles reached (epoll_ctl failed message is an consequence of this behaviour). Looks like it's caused by the bug in GunTLS session handling. Review https://bugzilla.redhat.com/show_bug.cgi?id=848852 for reference. The patch has been implemented already, but causing some performance issues unfortunately. Would be good to review the code and include it in the updates. Can you confirm that this issue is fixed in jessie (8.4.2-1) or the version from wheezy-backports (7.6.3-2~bpo70+1)? Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#782243: snmpd: systemctrl is-enabled snmpd.service fails with missing unit file
Package: snmpd Version: 5.7.2.1~dfsg-7 Severity: normal Dear Maintainer, We are using saltstack to deploy our debian servers, during which we also have a formula that installs snmpd on all systems, enables it and checks if it needs a restart due to changes in configuration files. As part of this, saltstack runs 'systemctrl is-enabled snmpd.service' which on debian results in the error: Failed to get unit file state for snmpd.service: No such file or directory expected output would be: enabled This is a rather minor, yet annoying issue. Given that Jessie introduces systemd as default, it would be nice if this could be resolved. Regards, Thomas -- 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/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages snmpd depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.56 ii libc6 2.19-15 ii libsnmp-base 5.7.2.1~dfsg-7 ii libsnmp30 5.7.2.1~dfsg-7 ii lsb-base 4.1+Debian13+nmu1 snmpd recommends no packages. Versions of packages snmpd suggests: pn snmptrapd none -- Configuration Files: /etc/default/snmpd changed [not included] /etc/snmp/snmpd.conf changed [not included] -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782058: Pegasos II: installer boots up to 'returning from prom_init'
On 04/09/2015 02:21 PM, Ben Hutchings wrote: It isn't reverted. All I've done is to add radeonfb.ko to the drivers that are included *in the installer*. Yes, I understand that. I still disagree with the change. Neither radeon.ko nor xserver-xorg-video-radeon are included in the installer, so how could they possibly be used? If you though those should be used in the installer, you should have told people that earlier. I didn't know they weren't included. I assumed that the graphics driver modules are important enough to be present in the installer image. As it is, I think that the installer should be able to work using radeonfb.ko and xserver-xorg-video-fbdev, though I'm not sure whether radeonfb.ko will be loaded automatically. As I have said before [1], radeonfb and xserver-xorg-video-fbdev aren't really working, the graphics are broken. Here's how it looks on a Powerbook G4 (with the same result on a Mac Mini G4) with radeonfb enabled: http://i.imgur.com/Miw5CR1.jpg http://i.imgur.com/AfpNdx3.jpg http://i.imgur.com/QBUPwRA.jpg On 04/09/2015 02:24 PM, Milan Kupcevic wrote: How is that X display in debian installer on PowerPC platform working for you? I never said it is. I said your suggested fix was wrong. Your understanding of the consequences of your changes is trully stellar. So you basically disagree about the graphical installer being broken on all PowerPC machines with Radeon graphics is not an important issue? OK. Well, I've asked, no one complained until you showed up. The resulting discussion spreads very interesting scent. I complained because I care about the end product. Are you sure you want to know about every non-x86 issue I face on daily basis? If it involves making such important changes to the kernel configuration, then yes. I am a porter for the m68k and sh4 architectures in Debian and also have large numbers of different hardware platforms available to test Debian on, ranging from a 22-year-old Amiga with 68030/50 MHz to an SGI UV-1000 supercomputer, so I can cover lots of use cases and I do lots of testing. On 04/09/2015 08:11 PM, Milan Kupcevic wrote: Sorry, my reaction to personal attacks was too harsh. Will stick to technical issues and ignore any personal slurs from now on. That wasn't a personal attack. I was criticizing you for requesting such a change without apparently reading the bug report where I elaborated why I said we should no longer use radeonfb. I have repeated several times that this driver produces broken graphics and I am starting to feel like an idiot having to repeat this over and over again. Cheers, Adrian [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748398#106 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782274: win32-loader: build-dependency not satisfied in jessie
Source: win32-loader Version: 0.7.8 Tags: jessie Severity: serious User: trei...@debian.org Usertags: edos-uninstallable Hello, win32-loader build-depends on nsis (= 2.46-10~). This is not satisfied in jessie, but is satisfied in sid: nsis | 2.46-9| jessie | source, amd64 nsis | 2.46-9+b1 | jessie | arm64, armel, armhf, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el nsis | 2.46-9+b2 | jessie | s390x nsis | 2.46-10 | sid | source, amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x, sparc To solve this bug one probably needs to let nsis migrate to jessie. When you reassign this bug accordingly please set an Affects: win32-loader. Sorry for filing this bug so late in the release process, I somehow was under the impression that the issue was known. Cheers -Ralf. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782244: nagios-nrpe-server: systemctl is-enabled nagios-nrpe-server fails with missing unit file
Package: nagios-nrpe-server Version: 2.15-1 Severity: normal Dear Maintainer, We are using saltstack to deploy our debian servers, during which we also have a formula that installs nagions-nrpe-server on all systems, enables it and checks if it needs a restart due to changes in configuration files. As part of this, saltstack runs 'systemctrl is-enabled nagios-nrpe-server' which on debian results in the error: Failed to get unit file state for nagios-nrpe-server.service: No such file or directory expected output would be: enabled This is a rather minor, yet annoying issue. Given that Jessie introduces systemd as default, it would be nice if this could be resolved. Regards, Thomas -- 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/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages nagios-nrpe-server depends on: ii adduser 3.113+nmu3 ii libc62.19-15 ii libssl1.0.0 1.0.1k-1 ii libwrap0 7.6.q-25 ii lsb-base 4.1+Debian13+nmu1 Versions of packages nagios-nrpe-server recommends: ii nagios-plugins-basic 2.1.1-1 nagios-nrpe-server suggests no packages. -- Configuration Files: /etc/nagios/nrpe.cfg changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
