Bug#769941: iceweasel crash
control: tag -1 unreproducible, moreinfo On Mon, Jan 12, 2015 at 3:22 AM, webmbackslash wrote: I've found that all my problems with iceweasel and chrome crash was due to a Ram module fault. I was thinking about glib and others stuff, but all was solved after removing the module that fail the memtest :) Thanks all folks This turned out to be faulty ram for the other person experiencing this. Submitter, can you see if memtest says anything meaningful, and possibly reseating, removing, or replacing ram? Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#769941: iceweasel crash
Processing control commands: tag -1 unreproducible, moreinfo Bug #769941 [libgstreamer-plugins-base1.0-0] libgstreamer-plugins-base1.0-0: Iceweasel crashes with gst_app_src_set_size: assertion 'GST_IS_APP_SRC (appsrc)' failed Added tag(s) unreproducible and moreinfo. -- 769941: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769941 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774791: xine-ui: Creates dpkg trigger cycle via libxine2-ffmpeg, libxine2-misc-plugins or libxine2-x
control: tag -1 patch On Wed, Jan 7, 2015 at 12:30 PM, Niels Thykier wrote: The libxine2-ffmpeg, libxine2-misc-plugins and libxine2-x packages have a trigger cycle via the xine-ui package. This was detected by a script on jenkins.debian.net[1]. Hi, I reviewed xine's trigger usage, and it looks correct to me to use interest-noawait since the trigger is used just for updating xine's .desktop file. Best wishes, Mike diff -Nru xine-ui-0.99.9/debian/changelog xine-ui-0.99.9/debian/changelog --- xine-ui-0.99.9/debian/changelog 2014-10-06 11:12:05.0 + +++ xine-ui-0.99.9/debian/changelog 2015-01-14 04:08:07.0 + @@ -1,3 +1,10 @@ +xine-ui (0.99.9-1.2) unstable; urgency=medium + + * Non-maintainer upload. + * Use interest-noawait trigger (closes: #774791). + + -- Michael Gilbert mgilb...@debian.org Wed, 14 Jan 2015 04:07:45 + + xine-ui (0.99.9-1.1) unstable; urgency=medium * Non-maintainer upload diff -Nru xine-ui-0.99.9/debian/xine-ui.triggers xine-ui-0.99.9/debian/xine-ui.triggers --- xine-ui-0.99.9/debian/xine-ui.triggers 2014-10-06 11:12:05.0 + +++ xine-ui-0.99.9/debian/xine-ui.triggers 2015-01-14 04:09:32.0 + @@ -1 +1 @@ -interest /usr/lib/xine/plugins +interest-noawait /usr/lib/xine/plugins
Processed: Re: Bug#774791: xine-ui: Creates dpkg trigger cycle via libxine2-ffmpeg, libxine2-misc-plugins or libxine2-x
Processing control commands: tag -1 patch Bug #774791 [src:xine-ui] xine-ui: Creates dpkg trigger cycle via libxine2-ffmpeg, libxine2-misc-plugins or libxine2-x Added tag(s) patch. -- 774791: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774791 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770008: calendar-google-provider: Can no longer connect to Google calendars
On Sat, Nov 22, 2014 at 10:36 AM, Christian Kastner wrote: For the sake of completeness, here is the note from the addon page: | NOTE FOR 0.31 AND 0.25 USERS | After a previous announcement, Google has shut down the v1 API today | (November 17th) that version 0.32 and 0.25 has been using. This means | those versions will no longer work and you MUST upgrade to 1.0.x to | continue using the Provider for Google Calendar. Here is a possibly unusual suggestion. What about shipping an empty package, with just a README, for now? A future ESR icedove version supporting the new API will eventually be shipped in -security, so trying to come up with a solution in time for the initial jessie release is possibly not entirely needed. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#769941: iceweasel crash
Processing control commands: tag -1 unreproducible, moreinfo Bug #769941 [libgstreamer-plugins-base1.0-0] libgstreamer-plugins-base1.0-0: Iceweasel crashes with gst_app_src_set_size: assertion 'GST_IS_APP_SRC (appsrc)' failed Ignoring request to alter tags of bug #769941 to the same tags previously set -- 769941: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769941 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 774726
Processing commands for cont...@bugs.debian.org: tags 774726 + pending Bug #774726 [libmspack0] libmspack: CHM decompression: pointer arithmetic overflow Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 774726: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774726 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 774725
Processing commands for cont...@bugs.debian.org: tags 774725 + pending Bug #774725 [libmspack0] libmspack: CHM decompression: division by zero Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 774725: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774725 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: forcibly merging 774436 775178
Processing commands for cont...@bugs.debian.org: forcemerge 774436 775178 Bug #774436 [src:linux] linux-image-3.2.0-4-amd64: suspend to ram regression in 3.2.65-1 Bug #774461 [src:linux] linux-image-3.2.0-4-amd64: suspend triggers reboot Bug #774526 [src:linux] linux-image-3.2.0-4-amd64: system crash with sudden reboot when hotplugging a CPU - suspend functionality broken Bug #775059 [src:linux] linux-image-3.2.0-4-amd64: kernel update broke suspend to ram - system crashes instead Bug #775123 [src:linux] (no subject) Bug #775154 [src:linux] linux-image-3.2.0-4-amd64: Wake/suspend-to-ram loop in 3.2.65-1 Bug #775157 [src:linux] base: Crash on resume after suspend-to-ram Bug #775246 [src:linux] general: Debian does wake from suspend. It either hard reboots or remains unresponsive. Bug #775178 [src:linux] linux-image-3.2.0-4-amd64: linux-image-3.2.0-4-amd64: regression: suspend/resume not working after update (again) Severity set to 'serious' from 'normal' Added indication that 775178 affects release.debian.org Added tag(s) confirmed and patch. Bug #774461 [src:linux] linux-image-3.2.0-4-amd64: suspend triggers reboot Bug #774526 [src:linux] linux-image-3.2.0-4-amd64: system crash with sudden reboot when hotplugging a CPU - suspend functionality broken Bug #775059 [src:linux] linux-image-3.2.0-4-amd64: kernel update broke suspend to ram - system crashes instead Bug #775123 [src:linux] (no subject) Bug #775154 [src:linux] linux-image-3.2.0-4-amd64: Wake/suspend-to-ram loop in 3.2.65-1 Bug #775157 [src:linux] base: Crash on resume after suspend-to-ram Bug #775246 [src:linux] general: Debian does wake from suspend. It either hard reboots or remains unresponsive. Merged 774436 774461 774526 775059 775123 775154 775157 775178 775246 thanks Stopping processing here. Please contact me if you need assistance. -- 774436: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774436 774461: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774461 774526: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774526 775059: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775059 775123: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775123 775154: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775154 775157: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775157 775178: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775178 775246: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775246 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775259: marked as done (code-saturne: fails to upgrade from 'wheezy' - trying to overwrite /usr/lib/python2.7/dist-packages/code_saturne/cs_config.py)
Your message dated Wed, 14 Jan 2015 07:47:29 +0100 with message-id 54b61101.8080...@thykier.net and subject line Re: code-saturne: fails to upgrade from 'wheezy' - trying to overwrite /usr/lib/python2.7/dist-packages/code_saturne/cs_config.py has caused the Debian Bug report #775259, regarding code-saturne: fails to upgrade from 'wheezy' - trying to overwrite /usr/lib/python2.7/dist-packages/code_saturne/cs_config.py to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 775259: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775259 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: code-saturne Version: 3.3.2-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'wheezy'. It installed fine in 'wheezy', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Preparing to replace code-saturne 2.1.7-1 (using .../code-saturne_3.3.2-3_amd64.deb) ... Unpacking replacement code-saturne ... Preparing to replace code-saturne-include 2.1.7-1 (using .../code-saturne-include_3.3.2-3_amd64.deb) ... Unpacking replacement code-saturne-include ... dpkg: error processing /var/cache/apt/archives/code-saturne-include_3.3.2-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python2.7/dist-packages/code_saturne/cs_config.py', which is also in package code-saturne-data 2.1.7-1 Preparing to replace libhdf5-openmpi-dev 1.8.8-9+b1 (using .../libhdf5-openmpi-dev_1.8.13+docs-15_amd64.deb) ... Unpacking replacement libhdf5-openmpi-dev ... Preparing to replace code-saturne-bin 2.1.7-1 (using .../code-saturne-bin_3.3.2-3_amd64.deb) ... Unpacking replacement code-saturne-bin ... Errors were encountered while processing: /var/cache/apt/archives/code-saturne-include_3.3.2-3_amd64.deb cheers, Andreas code-saturne_3.3.2-3.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Version: 3.3.2-4 On Tue, 13 Jan 2015 11:25:01 +0100 Andreas Beckmann a...@debian.org wrote: Package: code-saturne Version: 3.3.2-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'wheezy'. It installed fine in 'wheezy', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): [...] cheers, Andreas Seems like the 3.3.2-4 would fix this (based on the changes). ~Niels---End Message---
Bug#774889: Patch for gdm conflict with gdm3 in Jessie
Attached is the Patch for fixing the gdm3 upgrade issue from Squeeze - Wheezy - Jessie. The Wheezy gdm3 package properly addresses the conflict between the gdm and gdm3 .,but it is not done in gdm3. This patch will fix up that issue and does seamless upgrades. -- Regards., Prema S Index: debian/control === --- debian/control (revision 44082) +++ debian/control (working copy) @@ -91,6 +91,7 @@ Suggests: libpam-gnome-keyring, gnome-orca Provides: x-display-manager +Conflicts: gdm Breaks: gnome-panel ( 3.0), gnome-screensaver ( 2.17.7), gnome-orca ( 2.30.0-2), Index: debian/control.in === --- debian/control.in (revision 44082) +++ debian/control.in (working copy) @@ -87,6 +87,7 @@ Suggests: libpam-gnome-keyring, gnome-orca Provides: x-display-manager +Conflicts: gdm Breaks: gnome-panel ( 3.0), gnome-screensaver ( 2.17.7), gnome-orca ( 2.30.0-2),
Processed: notfound 775250 in 1.7.2.4-4
Processing commands for cont...@bugs.debian.org:
notfound 775250 1.7.2.4-4
Bug #775250 {Done: Axel Beckert a...@debian.org} [src:wicd] wicd: modifies
isc-dhcp conffile
No longer marked as found in versions wicd/1.7.2.4-4.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
775250: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775250
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: found 775276 in 8.2.3~dfsg.1-5
Processing commands for cont...@bugs.debian.org: found 775276 8.2.3~dfsg.1-5 Bug #775276 [condor] condor: CVE-2014-8126 Marked as found in versions condor/8.2.3~dfsg.1-5. thanks Stopping processing here. Please contact me if you need assistance. -- 775276: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775276 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: found 775276 in 7.8.2~dfsg.1-1
Processing commands for cont...@bugs.debian.org: found 775276 7.8.2~dfsg.1-1 Bug #775276 [condor] condor: CVE-2014-8126 Marked as found in versions condor/7.8.2~dfsg.1-1. thanks Stopping processing here. Please contact me if you need assistance. -- 775276: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775276 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: bug 775276 is forwarded to https://htcondor-wiki.cs.wisc.edu/index.cgi/tktview?tn=4764
Processing commands for cont...@bugs.debian.org: forwarded 775276 https://htcondor-wiki.cs.wisc.edu/index.cgi/tktview?tn=4764 Bug #775276 [condor] condor: CVE-2014-8126 Set Bug forwarded-to-address to 'https://htcondor-wiki.cs.wisc.edu/index.cgi/tktview?tn=4764'. thanks Stopping processing here. Please contact me if you need assistance. -- 775276: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775276 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773749: Resolvconf vs wicd
Hi there and thanks for the report. First I need some info. 1. When (if ever) does wicd modify dhclient.conf? 2. When the malfunction occurs are the contents /run/resolvconf/resolv.conf correct (i.e., what one would expect to find in resolv.conf)? So that the problem is that /etc/resolv.conf is not a symbolic link to /run/resolvconf/resolv.conf? -- Thomas Hood resolvconf maintainers -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735261: mutiple upstream bugs
control: severity -1 important It may sound cynical, but my advice would be that if you're hit with this, change mail clients :/ In the context of freeze/release, I'd suggest to tag this jessie-ignore, or even forever-ignore. This is a usability problem, so it doesn't really qualify as release critical. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#735261: mutiple upstream bugs
Processing control commands: severity -1 important Bug #735261 [kmail] kmail2 randomly marks read messages as unread Severity set to 'important' from 'grave' -- 735261: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735261 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775255: [pkg-fetchmail-maint] Bug#775255: fetchmail: Fails to start when libssl has SSLv3 disabled
Yes, it works with the version of libssl from unstable since SSLv3 is not
disabled in that version. The main problem is that currently, fetchmail does
not work with more secure versions of libssl (which have SSLv3 disabled
completely). I just provided one solution (completely disable SSLv3 in
fetchmail), but if another one (such as automatically detecting that libssl
does not provide SSLv3 and therefore not even attempting to load the SSLv3
symbols) works better, that's fine too.
Currently, the version of fetchmail in experimental is the same as the version
of fetchmail in unstable. If necessary, you could release a different version
of fetchmail for experimental which drops SSLv3 support entirely (if updating
the one in unstable seems like a bad idea currently), since SSLv3 support
*should* be dropped at some point due to the POODLE bug.
This is not an issue of fetchmail negotiating SSLv3 by default, this is an
issue of fetchmail looking for symbols in libssl *which don't exist*. The first
would only surface if, for example, libssl provided an empty implementation of
SSLv3 but still exported the symbols. What's happening right now is that the
symbols don't even exist, which leads to the program not working at all. This
is regardless of whether or not I actually utilize SSLv3 as my protocol (which
I never specifically requested).
- Chiraag
--
Chiraag M Nataraj
Senior at the California Institute of Technology
Email: chiraag.nata...@gmail.com
Phone: 610-350-6329
Website: http://chiraag.nataraj.us
On Wed, Jan 14, 2015 at 12:38:54AM +0100, Nico Golde wrote:
Hi,
* Chiraag Nataraj chiraag.nata...@gmail.com [2015-01-13 12:22]:
Package: fetchmail
Version: 6.3.26-1+b1
Severity: grave
Justification: renders package unusable
You filed a bug against a version that works absolutely fine with the openssl
version it is supposed to work with. Hence, I'm inclined to close that bug or
downgrade it to wishlist in favor of removing/disabling sslv3 support in
fetchmail.
When the latest version of libssl1.0.0 is installed from experimental
(which has SSLv3 disabled), Fetchmail exits with the following error:
fetchmail: relocation error: fetchmail: symbol SSLv3_client_method, version
OPENSSL_1.0.0 not defined in file libssl.so.1.0.0 with link time reference
See above
Fetchmail should be rebuilt to not require SSLv3.
The patch you included simply removes this feature entirely:
--- fetchmail-6.3.26/socket.c 2013-04-23 22:00:45.0 +0200
+++ socket.c2015-01-14 00:29:53.412608735 +0100
@@ -913,8 +913,6 @@
report(stderr, GT_(Your operating system does not
support SSLv2.\n));
return -1;
#endif
- } else if(!strcasecmp(ssl3,myproto)) {
- _ctx[sock] = SSL_CTX_new(SSLv3_client_method());
} else if(!strcasecmp(tls1,myproto)) {
_ctx[sock] = SSL_CTX_new(TLSv1_client_method());
} else if (!strcasecmp(ssl23,myproto)) {
In the current git version of fetchmail, sslv3 is not negotiated by default,
unless a user explicitly requests to do so. As such I'm not sure how useful
this patch is as well.
Matthias, do you mind weighing in on this?
Thanks
Nico
--
Nico Golde - XMPP: n...@jabber.ccc.de - GPG: 0xA0A0
signature.asc
Description: Digital signature
Bug#773749: Resolvconf vs wicd
On 2015-01-13 20:47:56 +0100, Thomas Hood wrote:
Hi there and thanks for the report.
First I need some info.
1. When (if ever) does wicd modify dhclient.conf?
In the past, wicd was creating its own dhclient.conf and was
invoking dhclient with this config file:
2011/12/17 03:16:46 :: /sbin/dhclient -v -cf /var/lib/wicd/dhclient.conf wlan0
Though this is still the way it should work according to the
documentation, this is no longer the case; wicd just executes:
/sbin/dhclient -v wlan0
so that /etc/dhcp/dhclient.conf is used by dhclient (but it has not
been modified by wicd). Well, this is what happens on my machine.
BTW, this was the first confusing point concerning this bug.
2. When the malfunction occurs are the contents
/run/resolvconf/resolv.conf correct (i.e., what one would expect to
find in resolv.conf)?
Yes, it appears to be correct.
So that the problem is that /etc/resolv.conf is not a symbolic link
to /run/resolvconf/resolv.conf?
More or less. The problem is actually a lack of consistency: only
/run/resolvconf/resolv.conf is modified *but* it is not used.
IMHO, there would be two possible correct behaviors concerning
the /etc/dhcp/dhclient-enter-hooks.d/resolvconf hook script:
1. The hook script assumes that resolvconf should be used, so that
a) it should disable the default behavior;
b) it should modify /run/resolvconf/resolv.conf;
c) it should make sure that /etc/resolv.conf is a symlink to
/etc/resolvconf/run/resolv.conf (e.g. by removing the old
file if there is one and adding the symlink).
Currently, the hook script does (a)[*] and (b), but not (c).
[*] make_resolv_conf() { : ; }
2. The hook script assumes that the symlink is not there because
the user didn't want to use resolvconf (without having to remove
the resolvconf package), e.g. temporarily, so that
a) it should test whether /etc/resolv.conf is a symlink to
/etc/resolvconf/run/resolv.conf;
b) if it isn't, terminate;
c) otherwise the script should disable the default behavior
and modify /run/resolvconf/resolv.conf (this is what it
currently does).
Here, what is missing is the test (a). I suppose that changing
the line
if [ -x /sbin/resolvconf ] ; then
to
if [ -x /sbin/resolvconf ] \
[ $(readlink /etc/resolv.conf) = /etc/resolvconf/run/resolv.conf ] ; then
would be sufficient.
On 2015-01-13 22:45:45 +0100, Axel Beckert wrote:
[wicd]
But it doesn't use /etc/dhcp/dhclient.conf for that (probably because
it should also work when using static IPs) but (without having
resolvconf installed) modifies /etc/resolv.conf directly as it seems.
On my machine, it doesn't. In the wicd-daemon source, the only parts
related to /etc/resolv.conf are:
def main(argv):
The main daemon program.
Keyword arguments:
argv -- The arguments passed to the script.
# back up resolv.conf before we do anything else
try:
backup_location = wpath.varlib + 'resolv.conf.orig'
# don't back up if .orig exists, probably there cause
# wicd exploded
if not os.path.exists(backup_location):
if os.path.islink('/etc/resolv.conf'):
dest = os.readlink('/etc/resolv.conf')
os.symlink(dest, backup_location)
else:
shutil.copy2('/etc/resolv.conf', backup_location)
os.chmod(backup_location, 0644)
except IOError:
print 'error backing up resolv.conf'
and
if kill:
try:
f = open(wpath.pidfile)
except:
#print sys.stderr, No wicd instance active, aborting.
sys.exit(1)
# restore resolv.conf on quit
try:
backup_location = wpath.varlib + 'resolv.conf.orig'
if os.path.islink(backup_location):
dest = os.readlink(backup_location)
os.remove('/etc/resolv.conf')
os.symlink(dest, '/etc/resolv.conf')
else:
shutil.move(backup_location, '/etc/resolv.conf')
os.chmod('/etc/resolv.conf', 0644)
except IOError:
print 'error restoring resolv.conf'
and indeed, there is a backup file:
-rw-r--r-- 1 root root 21 2010-05-24 20:28:15 /var/lib/wicd/resolv.conf.orig
However it is completely obsolete. The above method is obviously
broken: if ever wicd-daemon or the system crashes, or the machine
switches off due to a power supply problem, then one ends up with
an obsolete backup file, and the backup no longer works at all
until this file is removed by the user (who probably doesn't know
anything about this problem).
At least for a short moment the message Modifying /etc/resolv.conf
or similar was shown in wicd-curses' status line.
Are you sure that this comes from wicd? The wicd source doesn't
contain the word Modifying.
--
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 -
Bug#773749: Resolvconf vs wicd
On 2015-01-13 23:32:45 +0100, Axel Beckert wrote: Yes, the patch has been removed with the 1.6.0-1 upload with the following changelog entry: * debian/patches/: - 01-fix_desktop_file.patch, 07-add_resolvconf_support.patch removed, fixed upstream Anyway I haven't provided any DNS settings in the wicd configuration (I don't use static DNS). So, in my case, it is dhclient that should set up the DNS (unless some hook script overrides the default behavior). -- 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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: tag 740998 -patch Bug #740998 [rdnssd] NetworkManager and rdnssd do not play well together Removed tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 740998: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740998 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reassign 775246 to src:linux and merge
Processing commands for cont...@bugs.debian.org: reassign 775246 src:linux 3.2.65-1 Bug #775246 [general] general: Debian does wake from suspend. It either hard reboots or remains unresponsive. Bug reassigned from package 'general' to 'src:linux'. Ignoring request to alter found versions of bug #775246 to the same values previously set Ignoring request to alter fixed versions of bug #775246 to the same values previously set Bug #775246 [src:linux] general: Debian does wake from suspend. It either hard reboots or remains unresponsive. Marked as found in versions linux/3.2.65-1. severity 775246 serious Bug #775246 [src:linux] general: Debian does wake from suspend. It either hard reboots or remains unresponsive. Severity set to 'serious' from 'important' forcemerge 774436 775246 Bug #774436 [src:linux] linux-image-3.2.0-4-amd64: suspend to ram regression in 3.2.65-1 Bug #774461 [src:linux] linux-image-3.2.0-4-amd64: suspend triggers reboot Bug #774526 [src:linux] linux-image-3.2.0-4-amd64: system crash with sudden reboot when hotplugging a CPU - suspend functionality broken Bug #775059 [src:linux] linux-image-3.2.0-4-amd64: kernel update broke suspend to ram - system crashes instead Bug #775123 [src:linux] (no subject) Bug #775154 [src:linux] linux-image-3.2.0-4-amd64: Wake/suspend-to-ram loop in 3.2.65-1 Bug #775157 [src:linux] base: Crash on resume after suspend-to-ram Bug #775246 [src:linux] general: Debian does wake from suspend. It either hard reboots or remains unresponsive. Added indication that 775246 affects release.debian.org Added tag(s) confirmed and patch. Bug #774461 [src:linux] linux-image-3.2.0-4-amd64: suspend triggers reboot Bug #774526 [src:linux] linux-image-3.2.0-4-amd64: system crash with sudden reboot when hotplugging a CPU - suspend functionality broken Bug #775059 [src:linux] linux-image-3.2.0-4-amd64: kernel update broke suspend to ram - system crashes instead Bug #775123 [src:linux] (no subject) Bug #775154 [src:linux] linux-image-3.2.0-4-amd64: Wake/suspend-to-ram loop in 3.2.65-1 Bug #775157 [src:linux] base: Crash on resume after suspend-to-ram Merged 774436 774461 774526 775059 775123 775154 775157 775246 thanks Stopping processing here. Please contact me if you need assistance. -- 774436: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774436 774461: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774461 774526: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774526 775059: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775059 775123: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775123 775154: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775154 775157: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775157 775246: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775246 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#773749: [pkg-dhcp-devel] Bug#773749: Bug#773749: isc-dhcp-client: no longer updates /etc/resolv.conf
Processing control commands: reassign -1 resolvconf Bug #773749 [wicd-daemon] isc-dhcp-client: no longer updates /etc/resolv.conf Bug reassigned from package 'wicd-daemon' to 'resolvconf'. Ignoring request to alter found versions of bug #773749 to the same values previously set Ignoring request to alter fixed versions of bug #773749 to the same values previously set retitle -1 resolvconf prevents dhclient-script from updating /etc/resolv.conf Bug #773749 [resolvconf] isc-dhcp-client: no longer updates /etc/resolv.conf Changed Bug title to 'resolvconf prevents dhclient-script from updating /etc/resolv.conf' from 'isc-dhcp-client: no longer updates /etc/resolv.conf' -- 773749: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773749 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773749: [pkg-dhcp-devel] Bug#773749: Bug#773749: isc-dhcp-client: no longer updates /etc/resolv.conf
Control: reassign -1 resolvconf Control: retitle -1 resolvconf prevents dhclient-script from updating /etc/resolv.conf On 2015-01-13 09:20:12 +0100, Vincent Lefevre wrote: On 2015-01-13 02:18:37 -0500, Michael Gilbert wrote: There are other programs that circumvent isc-dhcp to update /etc/resolv.conf like resolvconf and network manager. According to your setup, it sounds like wicd also has a corner case that also does that. No, that could be true only if /etc/resolv.conf were updated. But it wasn't. This means that wicd (or some other package) prevents dhclient from updating /etc/resolv.conf. Actually it seems that it is resolvconf that prevents dhclient from updating /etc/resolv.conf. According to the dhclient-script(8) man page, there may be hooks to change the default behavior by defining the shell function make_resolv_conf. And this is what resolvconf appears to do *unconditionally*. So, either resolvconf should make sure that /etc/resolv.conf is a symlink to /etc/resolvconf/run/resolv.conf, or it shouldn't modify the default behavior. -- 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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775252: icinga-web-config-icinga2-ido-mysql, icinga-web-config-icinga2-ido-pgsql: fails to install: icinga2-enable-feature: command not found
Package: icinga-web-config-icinga2-ido-mysql,icinga-web-config-icinga2-ido-pgsql Version: 1.11.2+dfsg1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package icinga-web-config-icinga2-ido-mysql. (Reading database ... 19829 files and directories currently installed.) Preparing to unpack .../icinga-web-config-icinga2-ido-mysql_1.11.2+dfsg1-1_all.deb ... Unpacking icinga-web-config-icinga2-ido-mysql (1.11.2+dfsg1-1) ... Setting up icinga-web-config-icinga2-ido-mysql (1.11.2+dfsg1-1) ... Configuration IDO database for the MySQL IDO of Icinga 2... Creating config file /etc/icinga-web/conf.d/database-ido.xml with new version database config successful: /etc/icinga-web/conf.d/database-ido.xml enabling icinga2 features for classicui /var/lib/dpkg/info/icinga-web-config-icinga2-ido-mysql.postinst: line 33: icinga2-enable-feature: command not found dpkg: error processing package icinga-web-config-icinga2-ido-mysql (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: icinga-web-config-icinga2-ido-mysql Selecting previously unselected package icinga-web-config-icinga2-ido-pgsql. (Reading database ... 20687 files and directories currently installed.) Preparing to unpack .../icinga-web-config-icinga2-ido-pgsql_1.11.2+dfsg1-1_all.deb ... Unpacking icinga-web-config-icinga2-ido-pgsql (1.11.2+dfsg1-1) ... Setting up icinga-web-config-icinga2-ido-pgsql (1.11.2+dfsg1-1) ... Configuration IDO database for the PostgreSQL IDO of Icinga 2... Creating config file /etc/icinga-web/conf.d/database-ido.xml with new version database config successful: /etc/icinga-web/conf.d/database-ido.xml enabling icinga2 features for classicui /var/lib/dpkg/info/icinga-web-config-icinga2-ido-pgsql.postinst: line 33: icinga2-enable-feature: command not found dpkg: error processing package icinga-web-config-icinga2-ido-pgsql (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: icinga-web-config-icinga2-ido-pgsql cheers, Andreas icinga-web-config-icinga2-ido-mysql_1.11.2+dfsg1-1.log.gz Description: application/gzip
Processed: Re: Bug#773749: [pkg-dhcp-devel] Bug#773749: Bug#773749: isc-dhcp-client: no longer updates /etc/resolv.conf
Processing control commands: severity -1 grave Bug #773749 [wicd-daemon] isc-dhcp-client: no longer updates /etc/resolv.conf Severity set to 'grave' from 'normal' -- 773749: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773749 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773749: [pkg-dhcp-devel] Bug#773749: Bug#773749: isc-dhcp-client: no longer updates /etc/resolv.conf
Control: tag -1 - moreinfo unreproducible Hi Vincent, Vincent Lefevre wrote: Actually it seems that it is resolvconf that prevents dhclient from updating /etc/resolv.conf. Thanks, that explains well why neither Michael nor me were able to reproduce the issue. I'm hence removing the according tags. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#773749: [pkg-dhcp-devel] Bug#773749: Bug#773749: isc-dhcp-client: no longer updates /etc/resolv.conf
Processing control commands: tag -1 - moreinfo unreproducible Bug #773749 [resolvconf] resolvconf prevents dhclient-script from updating /etc/resolv.conf Removed tag(s) unreproducible and moreinfo. -- 773749: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773749 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698375: gfs2-utils: fails to upgrade from wheezy: insserv: script gfs2-utils: service gfs2 already provided!
Hi Andreas, On Sat, Jan 10, 2015 at 12:37:55PM +0100, Andreas Beckmann wrote: Followup-For: Bug #698375 Hi, adjusted Salvatore's patch to also run dpkg-maintscript-helper rm_conffile on initial package install. Verified that the upgrade path works. NMU uploaded to DELAYED/2. Thanks for your work on this issue. Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775225: work around : the crash seems to caused by the AMD fglrx driver and /usr/lib/libamdocl64.so
the crash seems to be caused by the AMD fglrx driver and /usr/lib/libamdocl64.so apt-get purge amd-opencl-icd solves the problem for code-aster I didn't check to see if anything else needed amd-opencl-icd is there anyway to force code aster and associated libraries to not use amd-opencl-icd ?
Bug#768245: opendnssec-enforcer-{sqlite3, mysql}: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
JFTR, my testing looks good: # ls -ld /usr/share/doc/opendnssec* drwxr-xr-x 2 root root 4096 Jan 13 13:41 /usr/share/doc/opendnssec drwxr-xr-x 2 root root 4096 Jan 13 13:41 /usr/share/doc/opendnssec-common drwxr-xr-x 5 root root 4096 Jan 13 13:36 /usr/share/doc/opendnssec-doc drwxr-xr-x 2 root root 4096 Jan 13 13:41 /usr/share/doc/opendnssec-enforcer drwxr-xr-x 2 root root 4096 Jan 13 13:41 /usr/share/doc/opendnssec-enforcer-sqlite3 drwxr-xr-x 2 root root 4096 Jan 13 13:41 /usr/share/doc/opendnssec-signer O. On Tue, Jan 13, 2015, at 14:52, Ondřej Surý wrote: 1:1.4.6-6 was uploaded right now. Please retest when you have a time and I will fill an unblock request. O. On Tue, Jan 13, 2015, at 14:49, Ondřej Surý wrote: Hi Andreas, oh my... Somehow I with the dh_installdoc --link-doc= was never introduced :). Building fixed package right now. I have tidied the others as well and bumped required dpkg to 1.17.14. O. On Tue, Jan 13, 2015, at 13:47, Andreas Beckmann wrote: Followup-For: Bug #768245 Control: found -1 1:1.4.6-5 Hi Ondrey, are you up for another iteration? The packages in wheezy-backports have yet another symlink - pointing to opendnssec-common (which was already once in your maintscripts, but we replaced it by another target). I think the approach of listing them all in the .maintscript should work here, too. (Don't forget the version bump to -6~ for the newly added ones). After an upgrade wheezy - wheezy-backports - jessie I get: 1m7.8s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/opendnssec-enforcer-sqlite3/NEWS.Debian.gz (opendnssec-enforcer-sqlite3) != /usr/share/doc/opendnssec-common/NEWS.Debian.gz (opendnssec-common) /usr/share/doc/opendnssec-enforcer-sqlite3 - opendnssec-common /usr/share/doc/opendnssec-enforcer-sqlite3/changelog.Debian.gz (opendnssec-enforcer-sqlite3) != /usr/share/doc/opendnssec-common/changelog.Debian.gz (opendnssec-common) /usr/share/doc/opendnssec-enforcer-sqlite3 - opendnssec-common /usr/share/doc/opendnssec-enforcer-sqlite3/changelog.gz (opendnssec-enforcer-sqlite3) != /usr/share/doc/opendnssec-common/changelog.gz (opendnssec-common) /usr/share/doc/opendnssec-enforcer-sqlite3 - opendnssec-common /usr/share/doc/opendnssec-enforcer-sqlite3/copyright (opendnssec-enforcer-sqlite3) != /usr/share/doc/opendnssec-common/copyright (opendnssec-common) /usr/share/doc/opendnssec-enforcer-sqlite3 - opendnssec-common 1m13.3s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/opendnssec-enforcer-mysql/NEWS.Debian.gz (opendnssec-enforcer-mysql) != /usr/share/doc/opendnssec-common/NEWS.Debian.gz (opendnssec-common) /usr/share/doc/opendnssec-enforcer-mysql - opendnssec-common /usr/share/doc/opendnssec-enforcer-mysql/changelog.Debian.gz (opendnssec-enforcer-mysql) != /usr/share/doc/opendnssec-common/changelog.Debian.gz (opendnssec-common) /usr/share/doc/opendnssec-enforcer-mysql - opendnssec-common /usr/share/doc/opendnssec-enforcer-mysql/changelog.gz (opendnssec-enforcer-mysql) != /usr/share/doc/opendnssec-common/changelog.gz (opendnssec-common) /usr/share/doc/opendnssec-enforcer-mysql - opendnssec-common /usr/share/doc/opendnssec-enforcer-mysql/copyright (opendnssec-enforcer-mysql) != /usr/share/doc/opendnssec-common/copyright (opendnssec-common) /usr/share/doc/opendnssec-enforcer-mysql - opendnssec-common There is also a file being left after purge: 1m18.8s INFO: Warning: Package purging left files on system: /etc/opendnssec/zonefetch.xmlnot owned Andreas Email had 1 attachment: + opendnssec-enforcer-sqlite3_1:1.4.6-5.log.gz 39k (application/gzip) -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775259: code-saturne: fails to upgrade from 'wheezy' - trying to overwrite /usr/lib/python2.7/dist-packages/code_saturne/cs_config.py
Package: code-saturne Version: 3.3.2-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'wheezy'. It installed fine in 'wheezy', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Preparing to replace code-saturne 2.1.7-1 (using .../code-saturne_3.3.2-3_amd64.deb) ... Unpacking replacement code-saturne ... Preparing to replace code-saturne-include 2.1.7-1 (using .../code-saturne-include_3.3.2-3_amd64.deb) ... Unpacking replacement code-saturne-include ... dpkg: error processing /var/cache/apt/archives/code-saturne-include_3.3.2-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python2.7/dist-packages/code_saturne/cs_config.py', which is also in package code-saturne-data 2.1.7-1 Preparing to replace libhdf5-openmpi-dev 1.8.8-9+b1 (using .../libhdf5-openmpi-dev_1.8.13+docs-15_amd64.deb) ... Unpacking replacement libhdf5-openmpi-dev ... Preparing to replace code-saturne-bin 2.1.7-1 (using .../code-saturne-bin_3.3.2-3_amd64.deb) ... Unpacking replacement code-saturne-bin ... Errors were encountered while processing: /var/cache/apt/archives/code-saturne-include_3.3.2-3_amd64.deb cheers, Andreas code-saturne_3.3.2-3.log.gz Description: application/gzip
Processed: found 769775 in 0.0.12-2, found 679691 in 0.6.21+nmu6, found 749317 in 2014.12.17 ..., affects 706298 ...
Processing commands for cont...@bugs.debian.org:
found 769775 0.0.12-2
Bug #769775 [tlsdate] tlsdate: unowned files after purge (policy 6.8, 10.8):
/var/cache/tlsdated/timestamp
Marked as found in versions tlsdate/0.0.12-2.
found 679691 0.6.21+nmu6
Bug #679691 [dhelp] dhelp: unowned files after purge (policy 6.8, 10.8):
/etc/apt/apt.conf.d/35dhelp
Marked as found in versions dhelp/0.6.21+nmu6.
found 749317 2014.12.17
Bug #749317 [debian-security-support] debian-security-support: unowned files
after purge (policy 6.8, 10.8)
Marked as found in versions debian-security-support/2014.12.17.
retitle 749317 debian-security-support: unowned directory after purge:
/var/lib/debian-security-support/
Bug #749317 [debian-security-support] debian-security-support: unowned files
after purge (policy 6.8, 10.8)
Changed Bug title to 'debian-security-support: unowned directory after purge:
/var/lib/debian-security-support/' from 'debian-security-support: unowned files
after purge (policy 6.8, 10.8)'
found 769766 0.12
Bug #769766 [debci] debci: unowned files after purge (policy 6.8, 10.8):
/var/lib/debci/*
Marked as found in versions debci/0.12.
found 670437 2.0.18.3+nmu4
Bug #670437 [pygopherd] pygopherd: unowned files after purge (policy 6.8,
10.8): /var/gopher/gophermap
Marked as found in versions pygopherd/2.0.18.3+nmu4.
found 664754 1.7+nmu1
Bug #664754 [gnuspool] gnuspool: removal of gnuspool makes files disappear from
lpr
Marked as found in versions gnuspool/1.7+nmu1.
found 531133 1:2008.05.17.1
Bug #531133 [lpr] unowned files after purge (policy 6.8)
Marked as found in versions lpr/1:2008.05.17.1.
retitle 531133 unowned files after purge (policy 6.8): /var/log/lp-{acct,errs}
Bug #531133 [lpr] unowned files after purge (policy 6.8)
Changed Bug title to 'unowned files after purge (policy 6.8):
/var/log/lp-{acct,errs}' from 'unowned files after purge (policy 6.8)'
found 668735 1.1-3.2
Bug #668735 [darcsweb] darcsweb: unowned files after purge (policy 6.8, 10.8):
/etc/apache2/conf.d/darcsweb.conf
Marked as found in versions darcsweb/1.1-3.2.
user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
usertags 774282 piuarts
There were no usertags set.
Usertags are now: piuarts.
usertags 706298 piuparts
There were no usertags set.
Usertags are now: piuparts.
affects 706298 + sugar-jigsawpuzzle-activity sugar-poll-activity
sugar-write-activity-0.86
Bug #706298 [python-abiword] python-abiword: missing python-gobject-2 dependency
Bug #706493 [python-abiword] python-abiword: missing python-gtk2 dependency
Added indication that 706298 affects sugar-jigsawpuzzle-activity,
sugar-poll-activity, and sugar-write-activity-0.86
Added indication that 706493 affects sugar-jigsawpuzzle-activity,
sugar-poll-activity, and sugar-write-activity-0.86
found 706298 sugar-write-activity-0.86/70-2.1
Bug #706298 [python-abiword] python-abiword: missing python-gobject-2 dependency
Bug #706493 [python-abiword] python-abiword: missing python-gtk2 dependency
Marked as found in versions sugar-write-activity-0.86/70-2.1.
Marked as found in versions sugar-write-activity-0.86/70-2.1.
found 706298 sugar-poll-activity/26+git20100521.d4def0b6-1.1
Bug #706298 [python-abiword] python-abiword: missing python-gobject-2 dependency
Bug #706493 [python-abiword] python-abiword: missing python-gtk2 dependency
Marked as found in versions sugar-poll-activity/26+git20100521.d4def0b6-1.1.
Marked as found in versions sugar-poll-activity/26+git20100521.d4def0b6-1.1.
found 706298 sugar-jigsawpuzzle-activity/8-1.1
Bug #706298 [python-abiword] python-abiword: missing python-gobject-2 dependency
Bug #706493 [python-abiword] python-abiword: missing python-gtk2 dependency
Marked as found in versions sugar-jigsawpuzzle-activity/8-1.1.
Marked as found in versions sugar-jigsawpuzzle-activity/8-1.1.
tags 775252 + sid
Bug #775252
[icinga-web-config-icinga2-ido-mysql,icinga-web-config-icinga2-ido-pgsql]
icinga-web-config-icinga2-ido-mysql, icinga-web-config-icinga2-ido-pgsql: fails
to install: icinga2-enable-feature: command not found
Added tag(s) sid.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
531133: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=531133
664754: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664754
668735: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668735
670437: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670437
679691: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679691
706298: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706298
706493: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706493
749317: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749317
769766: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769766
769775: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769775
775252: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775252
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To
Processed: Re: Bug#775067: systemd: journald doesn't forward messages to syslog w/o CAP_SYS_ADMIN (LXC)
Processing control commands: forwarded -1 http://lists.freedesktop.org/archives/systemd-devel/2015-January/026987.html Bug #775067 [systemd] systemd: journald doesn't forward messages to syslog w/o CAP_SYS_ADMIN (LXC) Set Bug forwarded-to-address to 'http://lists.freedesktop.org/archives/systemd-devel/2015-January/026987.html'. -- 775067: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775067 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775067: systemd: journald doesn't forward messages to syslog w/o CAP_SYS_ADMIN (LXC)
Control: forwarded -1 http://lists.freedesktop.org/archives/systemd-devel/2015-January/026987.html Hello Christian, Christian Seiler [2015-01-10 23:42 +0100]: when using LXC containers without CAP_SYS_ADMIN, journald fails to forward any messages to syslog by default. Thank you for the patch! I massaged it a bit and forwarded it to the upstream mailing list. Note that I consider grave quite inflated, severity normal or important would be more appropriate IMHO. But either way, I'll try to get this into jessie. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#769328: marked as done (plinth: no web page when started form boot, work when started from command line)
Your message dated Tue, 13 Jan 2015 11:19:01 + with message-id e1yazuz-zb...@franck.debian.org and subject line Bug#769328: fixed in plinth 0.4.4-1 has caused the Debian Bug report #769328, regarding plinth: no web page when started form boot, work when started from command line to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 769328: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769328 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: plinth Version: 0.4.1-1 Severity: serious I installed an unstable based FreedomBox using d-i and preseeding, but the resulting installation do not give me a working plinth. I installed using 'url=http://www.reinholdtsen.name/freedombox/unstable.dat' which I believe can be used to recreate the problem. Running the test suite show that http://freedombox/plinth/ do not work for IPv4 and IPv6. There are also several problems with the tor service. I suspect the init.d script starting plinth isn't working as well as it should. When I start plinth with --debug --no-daemon as root from the command line, it work and I could access the web pages. When it is started as a service, it do not work. :( I tried both using sysvinit and systemd, and both gave me a non-working plinth installation. -- Happy hacking Petter Reinholdtsen ---End Message--- ---BeginMessage--- Source: plinth Source-Version: 0.4.4-1 We believe that the bug you reported is fixed in the latest version of plinth, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 769...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bdale Garbee bd...@gag.com (supplier of updated plinth package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 13 Jan 2015 22:25:07 +1300 Source: plinth Binary: plinth Architecture: source all Version: 0.4.4-1 Distribution: unstable Urgency: low Maintainer: Tzafrir Cohen tzaf...@debian.org Changed-By: Bdale Garbee bd...@gag.com Description: plinth - web front end for administering every aspect of a Freedom Box Closes: 737456 741919 755619 765916 768666 769328 Changes: plinth (0.4.4-1) unstable; urgency=low . [ Sunil Mohan Adapa ] * New upstream version 0.4.4. Closes: #769328, #755619, #765916, #768666, #737456, #741919. * Update dependencies as per upstream changes. * Require Django 1.7 reflecting upstream changes. * Remove patches that have been upstreamed. * Update standards version to 3.9.6. * Properly remove obsolete module configuration. * Remove upstream install documentation. Checksums-Sha1: 77b0d68a3ad097a40a97ea1db9de91a1a855f6e6 2232 plinth_0.4.4-1.dsc 12dfdf68f93578cff3a22430e295cad76f87aef1 1803540 plinth_0.4.4.orig.tar.gz fdee6408f88469ecda09628a0d064b3606269cb8 5528 plinth_0.4.4-1.debian.tar.xz 39c259906642cf38a5bd6a80bcc8b055524470c7 1759476 plinth_0.4.4-1_all.deb Checksums-Sha256: a7d7af62c2f927366c45a79b6e605f7814199c7d068657ff110fdc3cac93c9b6 2232 plinth_0.4.4-1.dsc 9c97b2f95dc13c76c864bbcce927ddcc92426e345302fce35968ee2470c1fae0 1803540 plinth_0.4.4.orig.tar.gz 73b9947eb34fdac3d57ba0552416869e9a916100d7ee41265cacdf6ed780 5528 plinth_0.4.4-1.debian.tar.xz ad9b82e957cae4da58af824a8a163774945f412083481e9b1e1f3e276787bdf6 1759476 plinth_0.4.4-1_all.deb Files: 7e2dced6aee0474d279c85be9ef0c8de 2232 python optional plinth_0.4.4-1.dsc ee5b45f67ab68fb17c6c35ae6f13a2dc 1803540 python optional plinth_0.4.4.orig.tar.gz 1df59244b2f74995ec5862faa711dfe0 5528 python optional plinth_0.4.4-1.debian.tar.xz 04fa08d200e229d285a9fe792b957082 1759476 python optional plinth_0.4.4-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIVAwUBVLT8FzqTYZbAldlBAQpFXxAAtOuc2+OXKiJTATn2YZ7JKqDov5eiQqNU yufRDr+9F+Io51UDdJ+Eg1+xnI/IVs9e6+8YjaEt/wXxhhOUqK4e+tIBBtjjmu6C C1Zl/i0OKeUoUovtvYk3FqFUi+ijmYvYJU0n/iNhzIMARC0RrO5fYrAQXS+C+H39 8PILQUxltNyIb8THxk9kCawlswd/RLn2FLNfpcObe8FgW30UQu7RNoGGVOG+cqkp JyJ1LMauhTEGmZEcGP1e+0zLD+VNvjVXh6BgnefmuLD80drGMJFaG6VyEwVryEMZ vC0LiYYeiTwGG4D5hgBIeOSUBSpGmhHxKXdl0COGQfZTT06mV2u8oHD6xiRI1jy7 eAYs6x48eO0ECAClSHyuVsreEd3NqQkuYjil3mauz2i5LtwEuvs9yOS0CAoeHCZq
Bug#775257: libiomp5: missing SONAME link /usr/lib/libiomp5.so - libiomp5.so.5
Package: libiomp5 Version: 0.20141212-1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi Sylvestre, libiomp5 in experimental misses the SONAME link, this must be shipped. There are also no preinst/prerm scripts that would trigger ldconfig, sounds like a missing debhelper call ... Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774328: [Pkg-samba-maint] Bug#774328: ctdb: Failed to start ctdb.service: Unit ctdb.service failed to load: No such file or directory.
2014-12-31 23:16 GMT+01:00 Martin Schwenke mar...@meltin.net:
Package: ctdb
Version: 2.5.4+debian0-3
Severity: grave
Justification: renders package unusable
Dear Maintainer,
# systemctl start ctdb
Failed to start ctdb.service: Unit ctdb.service failed to load: No such file
or directory.
[...]
Couldn't reproduce here. But I need to test again in a clean VM.
Anything relevant in /var/log/{syslog,ctdb/log.ctdb}? journalctl -u
ctdb.service?
Was this machine migrated from wheezy? Do you have rsyslog installed?
Regards
--
Mathieu
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774335: marked as done (Provides: in SysV init scripts are not handled correctly, leading to wrong orderings)
Your message dated Tue, 13 Jan 2015 10:49:08 + with message-id e1yaz24-0005lx...@franck.debian.org and subject line Bug#774335: fixed in systemd 215-9 has caused the Debian Bug report #774335, regarding Provides: in SysV init scripts are not handled correctly, leading to wrong orderings to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 774335: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774335 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: systemd-sysv Version: 218-3 Severity: important Tags: upstream Dear Maintainer, I'm finding that autofs mounts which come from NIS maps don't show up when using systemd. I have a VM with an amd64 install of Jessie which uses autofs with a NIS map. Booting up, and the autofs mount points do not show up. If I restart autofs manually they then start working properly. I have an almost identical VM which has sysvinit instead of systemd where autofs works just fine. Looking at the logging in journalctl, it looks like autofs is being started before NIS (or possibly at exactly the same time). Jan 01 00:49:41 jessie-test systemd[1]: Inserted module 'autofs4' Jan 01 00:49:43 jessie-test nis[435]: Setting NIS domainname to: local.diamand.org. Jan 01 00:49:43 jessie-test autofs[436]: Starting automount Jan 01 00:49:44 jessie-test nis[435]: Starting NIS services: ypbind. sysv-generator seems to correctly generate an autofs.service file which has a dependency on NIS, specifically, ypbind: $ grep After autofs.service After=network-online.target remote-fs.target systemd-journald-dev-log.socket ypbind.service nslcd.service slapd.service But nothing in the nis.service file mentions ypbind, and so the dependency never gets setup, and the ordering isn't reliable. $ grep ypbind nis.service -- nothing -- Probably this means that if you're lucky, the timing will work out, and if you're not, it won't! I'm using systemd-syv version 218-3 from experimental on top of Jessie. -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd-sysv depends on: ii systemd 218-3 systemd-sysv recommends no packages. systemd-sysv suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: systemd Source-Version: 215-9 We believe that the bug you reported is fixed in the latest version of systemd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 774...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martin Pitt mp...@debian.org (supplier of updated systemd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 13 Jan 2015 11:24:43 +0100 Source: systemd Binary: systemd systemd-sysv libpam-systemd libsystemd0 libsystemd-dev libsystemd-login0 libsystemd-login-dev libsystemd-daemon0 libsystemd-daemon-dev libsystemd-journal0 libsystemd-journal-dev libsystemd-id128-0 libsystemd-id128-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb libgudev-1.0-0 gir1.2-gudev-1.0 libgudev-1.0-dev python3-systemd systemd-dbg Architecture: source amd64 Version: 215-9 Distribution: unstable Urgency: medium Maintainer: Debian systemd Maintainers pkg-systemd-maintain...@lists.alioth.debian.org Changed-By: Martin Pitt mp...@debian.org Description: gir1.2-gudev-1.0 - libgudev-1.0 introspection data libgudev-1.0-0 - GObject-based wrapper library for libudev libgudev-1.0-dev - libgudev-1.0 development files libpam-systemd - system and service manager - PAM module libsystemd-daemon-dev - systemd utility library (transitional package) libsystemd-daemon0 - systemd utility library (deprecated) libsystemd-dev - systemd utility library - development files libsystemd-id128-0 - systemd 128 bit ID utility library (deprecated) libsystemd-id128-dev - systemd 128 bit ID utility library (transitional package)
Bug#763327: marked as done ([systemd] FAILED to remount /)
Your message dated Tue, 13 Jan 2015 10:49:08 + with message-id e1yaz24-0005lf...@franck.debian.org and subject line Bug#742048: fixed in systemd 215-9 has caused the Debian Bug report #742048, regarding [systemd] FAILED to remount / to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 742048: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742048 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: systemd Version: 215-5 Severity: normal --- Please enter the report below this line. --- Since recent upgrade to 215-5 (maybe previous as well), get one or two FAILED to remount / message at the very startup. At this point, boot leaves the silent mode, shows all the messages, proceeds without any problems. System is running normally. Note: Had this on the 3.16 kernel. Tried 3.14 to see if the problem is with initramfs-tools which only updated 3.16. Error occurs here as well. --- System information. --- Architecture: amd64 Kernel: Linux 3.14-2-amd64 Debian Release: jessie/sid 500 unstableftp.us.debian.org 500 testing ftp.us.debian.org 500 sid linux.dropbox.com --- Package information. --- Depends(Version) | Installed -+-= libacl1(= 2.2.51-8) | 2.2.52-2 libaudit1 (= 1:2.2.1) | 1:2.4-1 libc6 (= 2.17) | libcap2(= 2.10) | libcryptsetup4 (= 2:1.4.3) | libdbus-1-3 (= 1.1.1) | libgcrypt11 (= 1.5.1) | libkmod2 (= 5~) | liblzma5(= 5.1.1alpha+20120614) | libpam0g (= 0.99.7.1) | libselinux1 (= 2.1.9) | libsystemd-daemon0(= 204-14) | libsystemd-journal0 (= 204-14) | libudev1(= 189) | libwrap0 (= 7.6-4~) | libsystemd-login0 (= 204-14) | util-linux (= 2.19.1-2) | initscripts (= 2.88dsf-17) | sysv-rc | udev | acl | adduser | libcap2-bin | Recommends (Version) | Installed =-+-=== libpam-systemd| 215-5 Suggests(Version) | Installed =-+-=== systemd-ui| 3-2 --- Output from package bug script --- ---End Message--- ---BeginMessage--- Source: systemd Source-Version: 215-9 We believe that the bug you reported is fixed in the latest version of systemd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 742...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martin Pitt mp...@debian.org (supplier of updated systemd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 13 Jan 2015 11:24:43 +0100 Source: systemd Binary: systemd systemd-sysv libpam-systemd libsystemd0 libsystemd-dev libsystemd-login0 libsystemd-login-dev libsystemd-daemon0 libsystemd-daemon-dev libsystemd-journal0 libsystemd-journal-dev libsystemd-id128-0 libsystemd-id128-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb libgudev-1.0-0 gir1.2-gudev-1.0 libgudev-1.0-dev python3-systemd systemd-dbg Architecture: source amd64 Version: 215-9 Distribution: unstable Urgency: medium Maintainer: Debian systemd Maintainers pkg-systemd-maintain...@lists.alioth.debian.org Changed-By: Martin Pitt mp...@debian.org Description: gir1.2-gudev-1.0 - libgudev-1.0 introspection data libgudev-1.0-0 - GObject-based wrapper library for libudev libgudev-1.0-dev - libgudev-1.0 development files libpam-systemd - system and service manager - PAM module libsystemd-daemon-dev - systemd utility library (transitional package)
Processed: tagging 774891
Processing commands for cont...@bugs.debian.org: tags 774891 + pending Bug #774891 [gtkpod] gtkpod: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 774891: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774891 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#773749: [pkg-dhcp-devel] Bug#773749: Bug#773749: isc-dhcp-client: no longer updates /etc/resolv.conf
Processing commands for cont...@bugs.debian.org: found 773749 1.76 Bug #773749 [resolvconf] resolvconf prevents dhclient-script from updating /etc/resolv.conf Marked as found in versions resolvconf/1.76. End of message, stopping processing here. Please contact me if you need assistance. -- 773749: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773749 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775252: [Pkg-nagios-devel] Bug#775252: icinga-web-config-icinga2-ido-mysql, icinga-web-config-icinga2-ido-pgsql: fails to install: icinga2-enable-feature: command not found
On Tue, 13 Jan 2015, Andreas Beckmann wrote: Hi, Package: icinga-web-config-icinga2-ido-mysql,icinga-web-config-icinga2-ido-pgsql Version: 1.11.2+dfsg1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package icinga-web-config-icinga2-ido-mysql. (Reading database ... 19829 files and directories currently installed.) Preparing to unpack .../icinga-web-config-icinga2-ido-mysql_1.11.2+dfsg1-1_all.deb ... Unpacking icinga-web-config-icinga2-ido-mysql (1.11.2+dfsg1-1) ... Setting up icinga-web-config-icinga2-ido-mysql (1.11.2+dfsg1-1) ... Configuration IDO database for the MySQL IDO of Icinga 2... Creating config file /etc/icinga-web/conf.d/database-ido.xml with new version database config successful: /etc/icinga-web/conf.d/database-ido.xml enabling icinga2 features for classicui /var/lib/dpkg/info/icinga-web-config-icinga2-ido-mysql.postinst: line 33: icinga2-enable-feature: command not found dpkg: error processing package icinga-web-config-icinga2-ido-mysql (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: icinga-web-config-icinga2-ido-mysql Selecting previously unselected package icinga-web-config-icinga2-ido-pgsql. (Reading database ... 20687 files and directories currently installed.) Preparing to unpack .../icinga-web-config-icinga2-ido-pgsql_1.11.2+dfsg1-1_all.deb ... Unpacking icinga-web-config-icinga2-ido-pgsql (1.11.2+dfsg1-1) ... Setting up icinga-web-config-icinga2-ido-pgsql (1.11.2+dfsg1-1) ... Configuration IDO database for the PostgreSQL IDO of Icinga 2... Creating config file /etc/icinga-web/conf.d/database-ido.xml with new version database config successful: /etc/icinga-web/conf.d/database-ido.xml enabling icinga2 features for classicui /var/lib/dpkg/info/icinga-web-config-icinga2-ido-pgsql.postinst: line 33: icinga2-enable-feature: command not found dpkg: error processing package icinga-web-config-icinga2-ido-pgsql (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: icinga-web-config-icinga2-ido-pgsql Is this a pure testing, or am unstable chroot? This particular problem should only happen in unstable (icinga 2.2 changed the syntax of the icinga2-enable-feature). If this is the case the problem isn't relevant for testing and I would therefore lower the severity and tag the bug as sid. Thanks in advance Alex -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775254: python-mysqldb-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Package: python-mysqldb-dbg
Version: 1.3.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.
This was observed on the following upgrade paths:
sid - experimental
For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile
For other overwritten locations anything interesting may happen.
Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase
It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.mainstscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.
From the attached log (usually somewhere in the middle...):
2m59.1s ERROR: FAIL: silently overwrites files via directory symlinks:
/usr/share/doc/python-mysqldb-dbg/changelog.Debian.gz (python-mysqldb-dbg) !=
/usr/share/doc/python-mysqldb/changelog.Debian.gz (python-mysqldb)
/usr/share/doc/python-mysqldb-dbg - python-mysqldb
/usr/share/doc/python-mysqldb-dbg/copyright (python-mysqldb-dbg) !=
/usr/share/doc/python-mysqldb/copyright (python-mysqldb)
/usr/share/doc/python-mysqldb-dbg - python-mysqldb
cheers,
Andreas
python-mysqldb-dbg_1.3.4-1.log.gz
Description: application/gzip
Bug#775255: fetchmail: Fails to start when libssl has SSLv3 disabled
Package: fetchmail Version: 6.3.26-1+b1 Severity: grave Justification: renders package unusable Dear Maintainer, When the latest version of libssl1.0.0 is installed from experimental (which has SSLv3 disabled), Fetchmail exits with the following error: fetchmail: relocation error: fetchmail: symbol SSLv3_client_method, version OPENSSL_1.0.0 not defined in file libssl.so.1.0.0 with link time reference Fetchmail should be rebuilt to not require SSLv3. -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.18.0-chiraag (SMP w/8 CPU cores; PREEMPT) 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 fetchmail depends on: ii adduser 3.113+nmu3 ii debianutils 4.4+b1 ii libc6 2.19-13 ii libcomerr21.42.12-1 ii libgssapi-krb5-2 1.13~alpha1+dfsg-1 ii libkrb5-3 1.13~alpha1+dfsg-1 ii libssl1.0.0 1.0.2~beta3-1 ii lsb-base 4.1+Debian13+nmu1 Versions of packages fetchmail recommends: ii ca-certificates 20141019 Versions of packages fetchmail suggests: pn default-mta | mail-transport-agent none pn fetchmailconf none pn resolvconf none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775255: Fixed socket.c attached
I have attached the fixed socket.c - as far as I can tell, that appears to fix
the problem. The only change I made was to remove lines 916 and 917.
Sincerely,
Chiraag
--
Chiraag M Nataraj
Senior at the California Institute of Technology
Email: chiraag.nata...@gmail.com
Phone: 610-350-6329
Website: http://chiraag.nataraj.us
/*
* socket.c -- socket library functions
*
* Copyright 1998 by Eric S. Raymond.
* For license terms, see the file COPYING in this directory.
*/
#include config.h
#include stdio.h
#include errno.h
#include string.h
#include ctype.h /* isspace() */
#ifdef HAVE_MEMORY_H
#include memory.h
#endif /* HAVE_MEMORY_H */
#include sys/types.h
#include sys/stat.h
#ifndef HAVE_NET_SOCKET_H
#include sys/socket.h
#else
#include net/socket.h
#endif
#include sys/un.h
#include netinet/in.h
#ifdef HAVE_ARPA_INET_H
#include arpa/inet.h
#endif
#include netdb.h
#if defined(STDC_HEADERS)
#include stdlib.h
#endif
#if defined(HAVE_UNISTD_H)
#include unistd.h
#endif
#if defined(HAVE_STDARG_H)
#include stdarg.h
#else
#include varargs.h
#endif
#if TIME_WITH_SYS_TIME
# include sys/time.h
# include time.h
#else
# if HAVE_SYS_TIME_H
# include sys/time.h
# else
# include time.h
# endif
#endif
#include socket.h
#include fetchmail.h
#include getaddrinfo.h
#include i18n.h
#include sdump.h
/* Defines to allow BeOS and Cygwin to play nice... */
#ifdef __BEOS__
static char peeked;
#define fm_close(a) closesocket(a)
#define fm_write(a,b,c) send(a,b,c,0)
#define fm_peek(a,b,c) recv(a,b,c,0)
#define fm_read(a,b,c) recv(a,b,c,0)
#else
#define fm_close(a) close(a)
#define fm_write(a,b,c) write(a,b,c)
#define fm_peek(a,b,c) recv(a,b,c, MSG_PEEK)
#ifdef __CYGWIN__
#define fm_read(a,b,c) cygwin_read(a,b,c)
static ssize_t cygwin_read(int sock, void *buf, size_t count);
#else /* ! __CYGWIN__ */
#define fm_read(a,b,c) read(a,b,c)
#endif /* __CYGWIN__ */
#endif
/* We need to define h_errno only if it is not already */
#ifndef h_errno
# if !HAVE_DECL_H_ERRNO
extern int h_errno;
# endif
#endif /* ndef h_errno */
#ifdef HAVE_SOCKETPAIR
static char *const *parse_plugin(const char *plugin, const char *host, const char *service)
{
char **argvec;
const char *c, *p;
char *cp, *plugin_copy;
unsigned int plugin_copy_len;
unsigned int plugin_offset = 0, plugin_copy_offset = 0;
unsigned int i, s = 2 * sizeof(char*), host_count = 0, service_count = 0;
unsigned int plugin_len = strlen(plugin);
unsigned int host_len = strlen(host);
unsigned int service_len = strlen(service);
for (c = p = plugin; *c; c++)
{ if (isspace((unsigned char)*c) !isspace((unsigned char)*p))
s += sizeof(char*);
if (*p == '%' *c == 'h')
host_count++;
if (*p == '%' *c == 'p')
service_count++;
p = c;
}
plugin_copy_len = plugin_len + host_len * host_count + service_len * service_count;
plugin_copy = (char *)malloc(plugin_copy_len + 1);
if (!plugin_copy)
{
report(stderr, GT_(fetchmail: malloc failed\n));
return NULL;
}
while (plugin_copy_offset plugin_copy_len)
{ if ((plugin[plugin_offset] == '%') (plugin[plugin_offset + 1] == 'h'))
{ strcpy(plugin_copy + plugin_copy_offset, host);
plugin_offset += 2;
plugin_copy_offset += host_len;
}
else if ((plugin[plugin_offset] == '%') (plugin[plugin_offset + 1] == 'p'))
{ strcpy(plugin_copy + plugin_copy_offset, service);
plugin_offset += 2;
plugin_copy_offset += service_len;
}
else
{ plugin_copy[plugin_copy_offset] = plugin[plugin_offset];
plugin_offset++;
plugin_copy_offset++;
}
}
plugin_copy[plugin_copy_len] = 0;
argvec = (char **)malloc(s);
if (!argvec)
{
free(plugin_copy);
report(stderr, GT_(fetchmail: malloc failed\n));
return NULL;
}
memset(argvec, 0, s);
for (p = cp = plugin_copy, i = 0; *cp; cp++)
{ if ((!isspace((unsigned char)*cp)) (cp == p ? 1 : isspace((unsigned char)*p))) {
argvec[i] = cp;
i++;
}
p = cp;
}
for (cp = plugin_copy; *cp; cp++)
{ if (isspace((unsigned char)*cp))
*cp = 0;
}
return argvec;
}
static int handle_plugin(const char *host,
const char *service, const char *plugin)
/* get a socket mediated through a given external command */
{
int fds[2];
char *const *argvec;
/*
* The author of this code, Felix von Leitner fe...@convergence.de, says:
* he chose socketpair() instead of pipe() because socketpair creates
* bidirectional sockets while allegedly some pipe() implementations don't.
*/
if (socketpair(AF_UNIX,SOCK_STREAM,0,fds))
{
report(stderr, GT_(fetchmail: socketpair failed\n));
return -1;
}
switch (fork()) {
case -1:
/* error */
report(stderr, GT_(fetchmail: fork failed\n));
return -1;
case 0: /* child */
/* fds[1] is the parent's end; close it for proper EOF
** detection */
(void) close(fds[1]);
if ( (dup2(fds[0],0) == -1) || (dup2(fds[0],1) == -1) ) {
report(stderr, GT_(dup2 failed\n));
_exit(EXIT_FAILURE);
}
/* fds[0] is now connected to 0 and 1; close it */
(void) close(fds[0]);
Bug#772902: marked as done (src:python-ghost: build-depend on python-django and python3-django to fix tests)
Your message dated Tue, 13 Jan 2015 09:34:02 + with message-id e1yaxro-0004it...@franck.debian.org and subject line Bug#772902: fixed in python-ghost 0.1.1-2 has caused the Debian Bug report #772902, regarding src:python-ghost: build-depend on python-django and python3-django to fix tests to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 772902: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772902 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:python-ghost Version: 0.1b6+git20141209-1 Severity: serious Justification: fails to build from source Dear Maintainer, Please build-depend on python-django and python3-django to fix the tests that are currently erroring out on a build in a clean chroot. Here is the relevant tail of the build log (the Python 3 test errors out with the same message): == ERROR: tests.ghost.ext.django.test (unittest.loader.ModuleImportFailure) -- ImportError: Failed to import test module: tests.ghost.ext.django.test Traceback (most recent call last): File /usr/lib/python2.7/unittest/loader.py, line 254, in _find_tests module = self._get_module_from_name(name) File /usr/lib/python2.7/unittest/loader.py, line 232, in _get_module_from_name __import__(name) File tests/ghost/ext/django/test.py, line 5, in module raise Exception(Ghost.py django extension requires django...) Exception: Ghost.py django extension requires django... Thanks, Logan Rosen -- System Information: Debian Release: jessie/sid APT prefers vivid-updates APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), (100, 'vivid-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-25-generic (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: python-ghost Source-Version: 0.1.1-2 We believe that the bug you reported is fixed in the latest version of python-ghost, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 772...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. W. Martin Borgert deba...@debian.org (supplier of updated python-ghost package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 13 Jan 2015 09:20:21 + Source: python-ghost Binary: python-ghost python3-ghost Architecture: source all Version: 0.1.1-2 Distribution: unstable Urgency: low Maintainer: Debian Python Modules Team python-modules-t...@lists.alioth.debian.org Changed-By: W. Martin Borgert deba...@debian.org Description: python-ghost - webkit web client library python3-ghost - webkit web client library Closes: 772902 Changes: python-ghost (0.1.1-2) unstable; urgency=low . * Build-dep on Django (Closes: #772902). Checksums-Sha1: 57e751f0ed7475a489769300870796377afd262d 2162 python-ghost_0.1.1-2.dsc 0c9239fb95cdb14500eedeb1ab97888a97fd2149 2512 python-ghost_0.1.1-2.debian.tar.xz 465f565999dacf8c5a5099d6d9b0c23a7f7036a7 13932 python-ghost_0.1.1-2_all.deb 32741eb701e362f4ac982c116cae8693ef2152e1 13672 python3-ghost_0.1.1-2_all.deb Checksums-Sha256: 676e35c8520d3802f4cc07e935cdc62e3820b83d7a92858b0b4338c0b2ac1de0 2162 python-ghost_0.1.1-2.dsc be635926d3f42ef9bb58f315d713b1b1251caf1d2f4a3cc790bf18b1c97e2bcb 2512 python-ghost_0.1.1-2.debian.tar.xz 96e058dc467b68ad2ebec6e55a993ea78869df02ce08b25a89df373ba079ebbc 13932 python-ghost_0.1.1-2_all.deb 5a8cf53aecce3a1e3314693aa68e8af63a7d299e6b125df15516e56ec91a6d2a 13672 python3-ghost_0.1.1-2_all.deb Files: 6337ca985b1df2497abd6e2c5aef8d71 2162 python optional python-ghost_0.1.1-2.dsc 2674aa79d24d2ecc1be7508b5adb43e9 2512 python optional python-ghost_0.1.1-2.debian.tar.xz 353c25a6c9553285b40f769e71056900 13932 python optional python-ghost_0.1.1-2_all.deb 20ee2b52558f8b8b21ef24603e2849ee 13672 python optional python3-ghost_0.1.1-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1
Bug#775189: mate-session spawns gnome-keyring unconditionally
HI Infirit, hi Faidon, On Mo 12 Jan 2015 21:25:47 CET, infirit wrote: On Mon, 12 Jan 2015 13:37:29 + Mike Gabriel mike.gabr...@das-netzwerkteam.de wrote: On Mo 12 Jan 2015 13:38:40 CET, Faidon Liambotis wrote: Since upstream commit[1] 8a20baf39f781184d6126e0947e9fd4d9a115fab, mate-session-manager spawns gnome-keyring-daemon, with no option to turn it off, or pass arguments to it (such as --components). While this is bad in itself, it gets worse: keyring is spawned *after* the regular user-configured autostart programs are run. gnome-keyring's default set of components includes a GPG a SSH agent and rightfully exports SSH_AUTH_SOCK and GPG_AGENT_INFO. The gnome compat code is one of the first things to run, even before the main manager is started that handles autostart. I am surpised you see it being run after autostart... Start mate-session with --debug and look for MsmGnome in the log to see when it is run. The clobbering could be disabled via gconf in GNOMEv2 and I am pretty sure there is something similar possible by manipulating with dconf-editor. There is no way to disable it atm other than removing gnome-keyring. The reason it is run this way is that MATE relies on gnome-keyring/libsecret instead of the forked 2.32 versions. And as gnome-keyring does not export the env variables we run gnome-keyring which outputs the variables that mate-session then exports them before autostarting the wm, desktop etc etc.. Attached is a preliminary patch that uses a gsettings key to determine which parts of the gnome compat should be started. Modify the list in gnome-compat-startup and remove the 'keyring' value. This should stop the clobbering of the variables. ~infirit I have tested infirit's patch and it seems to work, at least for the gnome-keyring part. I could not manage to find gnome-smproxy in Debian, so I presume that part of the switch is useless, but relevant to other distros, probably. I will proceed with retrieving an unblock confirmation for planned upload of mate-session-manager 1.8.1-6 which will fix this issue. 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 pgpZVxCHRo76a.pgp Description: Digitale PGP-Signatur
Bug#774461: Bug#775059: linux-image-3.2.0-4-amd64: suspend to ram regression in 3.2.65-1
Hello, i can confirm the bug and had the similar problem here on a HP Z220 workstation and the test kernel from Ben fixed the problem. Thank you very much and kind regards, Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775267: ERROR: dictionaries-common is broken - called emacs-package-remove as a new-style add-on, but has no compat file.
Package: dictionaries-common Version: 1.23.17 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, noticed this during a piuparts test (wheezy2jessie-rcmd, gnumed-client): Preparing to replace dictionaries-common 1.12.11 (using .../dictionaries-common_1.23.17_all.deb) ... ERROR: dictionaries-common is broken - called emacs-package-remove as a new-style add-on, but has no compat file. Leaving 'diversion of /usr/share/dict/words to /usr/share/dict/words.pre-dictionaries-common by dictionaries-common' Unpacking replacement dictionaries-common ... It does not fail (in d-c) but this sounds scary. Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774794: dpkg: Add breaks for new trigger cycles
Followup-For: Bug #774794 Hi, found another loop in a wheezy - wheezy-backports - jessie upgrade of debian-security-support, full log attached: Preparing to unpack .../libudev1_215-8_amd64.deb ... Unpacking libudev1:amd64 (215-8) ... Processing triggers for debian-security-support (2014.09.07~bpo70+1) ... Setting up libudev1:amd64 (215-8) ... Processing triggers for libc-bin (2.19-13) ... (Reading database ... 6958 files and directories currently installed.) Preparing to unpack .../debconf_1.5.55_all.deb ... Unpacking debconf (1.5.55) over (1.5.49) ... Setting up debconf (1.5.55) ... (Reading database ... 6953 files and directories currently installed.) Preparing to unpack .../libpam0g_1.1.8-3.1_amd64.deb ... Unpacking libpam0g:amd64 (1.1.8-3.1) over (1.1.3-7.1) ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: debian-security-support - debian-security-support packages' pending triggers which are or may be unresolvable: debian-security-support: /usr dpkg: error processing package debian-security-support (--configure): triggers looping, abandoned Setting up libpam0g:amd64 (1.1.8-3.1) ... Processing triggers for libc-bin (2.19-13) ... Errors were encountered while processing: debian-security-support Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775067: systemd: journald doesn't forward messages to syslog w/o CAP_SYS_ADMIN (LXC)
Hi Martin, (bugtracker CC changed to -quiet to not spam other people) Note that I consider grave quite inflated, severity normal or important would be more appropriate IMHO. According to the descriptions reportbug gave me, it was the lowest severity that fit IMHO, since I would consider not having persistent logs to be considered 'data loss', especially since one does not immediately notice this because no error is thrown. (And because errno is not EAGAIN, not even the 'could not forward X messages to syslog' or so journal message is generated.) On the other hand, I consider it to be a package maintainer's perogative to adjust the severity field, so if you think my reasoning really does not justify this bug being classified as 'grave', I won't object to you changing it. But either way, I'll try to get this into jessie. Thanks a lot! Christian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775276: condor: CVE-2014-8126
Package: condor Severity: grave Tags: security Justification: user security hole Hi, please see https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2014-8126 for details and a patch. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774794: dpkg: Add breaks for new trigger cycles
Followup-For: Bug #774794 full log, this time :-) debian-security-support_2014.12.17.log.gz Description: application/gzip
Bug#768245: opendnssec-enforcer-{sqlite3, mysql}: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Hi Andreas, oh my... Somehow I with the dh_installdoc --link-doc= was never introduced :). Building fixed package right now. I have tidied the others as well and bumped required dpkg to 1.17.14. O. On Tue, Jan 13, 2015, at 13:47, Andreas Beckmann wrote: Followup-For: Bug #768245 Control: found -1 1:1.4.6-5 Hi Ondrey, are you up for another iteration? The packages in wheezy-backports have yet another symlink - pointing to opendnssec-common (which was already once in your maintscripts, but we replaced it by another target). I think the approach of listing them all in the .maintscript should work here, too. (Don't forget the version bump to -6~ for the newly added ones). After an upgrade wheezy - wheezy-backports - jessie I get: 1m7.8s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/opendnssec-enforcer-sqlite3/NEWS.Debian.gz (opendnssec-enforcer-sqlite3) != /usr/share/doc/opendnssec-common/NEWS.Debian.gz (opendnssec-common) /usr/share/doc/opendnssec-enforcer-sqlite3 - opendnssec-common /usr/share/doc/opendnssec-enforcer-sqlite3/changelog.Debian.gz (opendnssec-enforcer-sqlite3) != /usr/share/doc/opendnssec-common/changelog.Debian.gz (opendnssec-common) /usr/share/doc/opendnssec-enforcer-sqlite3 - opendnssec-common /usr/share/doc/opendnssec-enforcer-sqlite3/changelog.gz (opendnssec-enforcer-sqlite3) != /usr/share/doc/opendnssec-common/changelog.gz (opendnssec-common) /usr/share/doc/opendnssec-enforcer-sqlite3 - opendnssec-common /usr/share/doc/opendnssec-enforcer-sqlite3/copyright (opendnssec-enforcer-sqlite3) != /usr/share/doc/opendnssec-common/copyright (opendnssec-common) /usr/share/doc/opendnssec-enforcer-sqlite3 - opendnssec-common 1m13.3s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/opendnssec-enforcer-mysql/NEWS.Debian.gz (opendnssec-enforcer-mysql) != /usr/share/doc/opendnssec-common/NEWS.Debian.gz (opendnssec-common) /usr/share/doc/opendnssec-enforcer-mysql - opendnssec-common /usr/share/doc/opendnssec-enforcer-mysql/changelog.Debian.gz (opendnssec-enforcer-mysql) != /usr/share/doc/opendnssec-common/changelog.Debian.gz (opendnssec-common) /usr/share/doc/opendnssec-enforcer-mysql - opendnssec-common /usr/share/doc/opendnssec-enforcer-mysql/changelog.gz (opendnssec-enforcer-mysql) != /usr/share/doc/opendnssec-common/changelog.gz (opendnssec-common) /usr/share/doc/opendnssec-enforcer-mysql - opendnssec-common /usr/share/doc/opendnssec-enforcer-mysql/copyright (opendnssec-enforcer-mysql) != /usr/share/doc/opendnssec-common/copyright (opendnssec-common) /usr/share/doc/opendnssec-enforcer-mysql - opendnssec-common There is also a file being left after purge: 1m18.8s INFO: Warning: Package purging left files on system: /etc/opendnssec/zonefetch.xmlnot owned Andreas Email had 1 attachment: + opendnssec-enforcer-sqlite3_1:1.4.6-5.log.gz 39k (application/gzip) -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#774598: maildrop: Maildrop package is not build with authlib support.
Processing control commands: severity 774598 serious Bug #774598 [maildrop] maildrop: Maildrop package is not build with authlib support. Severity set to 'serious' from 'normal' -- 774598: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774598 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774213: your mail
On Mon, Jan 12, 2015 at 03:40:36PM -0500, Barry Warsaw wrote: Something else must still be going on. I have the following zope packages installed: % aptitude search zope | grep ^i i python-zope.component - Zope Component Architecture i python-zope.configuration - Zope Configuration Markup Language (ZCML) i python-zope.deprecation - Zope Deprecation Infrastructure i python-zope.event - Very basic event publishing system i python-zope.exceptions - Zope exceptions for Python i python-zope.i18nmessageid - Message Identifiers for internationalizati i A python-zope.interface - Interfaces for Python i python-zope.location- Tools for working with object locations i python-zope.proxy - Generic transparent proxies for Python i python-zope.schema - zope.interface extension for defining data i python-zope.security- Zope Security Framework i python-zope.testing - Zope testing helpers i python-zope.testrunner - Flexible test runner with layer support fo i python3-zope.component - Zope Component Architecture i python3-zope.configuration - Zope Configuration Markup Language (ZCML) i python3-zope.deprecation- Zope Deprecation Infrastructure i python3-zope.event - Very basic event publishing system i python3-zope.exceptions - Zope exceptions for Python 3 i python3-zope.i18nmessageid - Message Identifiers for internationalizati i python3-zope.interface - Interfaces for Python3 i python3-zope.location - Tools for working with object locations i python3-zope.proxy - Generic transparent proxies for Python i python3-zope.schema - zope.interface extension for defining data i python3-zope.testing- Zope testing helpers for Python 3 i python3-zope.testrunner - Flexible test runner with layer support fo i A zope-common - common settings and scripts for Zope insta i zope2.13- Open Source Web Application Server so definitely python-zope.security, python-zope.proxy, and zope2.13. and yet... % /usr/lib/zope2.13/bin/python import zope.security._proxy zope.security._proxy.__file__ '/usr/lib/python2.7/dist-packages/zope/security/_proxy.x86_64-linux-gnu.so' I think I'm starting to understand: I do _not_ have python-zope.security installed (because nothing depends on it including zope2.13). clean@teco:~$ dpkg -l |grep zope ii python-zope.interface 4.1.1-3.1 ii python-zope.proxy 4.1.4-2 ii zope-common 0.5.54 ii zope2.13 2.13.22-1 If I install python-zope.security, then import goes ok: clean@teco:~$ dpkg -l |grep zope ii python-zope.component 4.2.1-2 ii python-zope.event 4.0.3-2 ii python-zope.i18nmessageid 4.0.3-1 ii python-zope.interface 4.1.1-3.1 ii python-zope.location 4.0.3-1 ii python-zope.proxy 4.1.4-2 ii python-zope.schema4.4.2-1 ii python-zope.security 4.0.1-1 ii zope-common 0.5.54 ii zope2.13 2.13.22-1 clean@teco:~$ /usr/lib/zope2.13/bin/python import zope.security._proxy zope.security._proxy.__file__ '/usr/lib/python2.7/dist-packages/zope/security/_proxy.x86_64-linux-gnu.so' but the imported module is NOT from zope2.13 package, as it should be: clean@teco:~$ dpkg -L zope2.13 |grep security |grep proxy.so /usr/lib/zope2.13/lib/python/zope.security-3.7.4.egg/zope/security/_proxy.so after purging python-zope.security import fails, but in a new way: clean@teco:~$ dpkg -l |grep zope ii python-zope.interface 4.1.1-3.1 ii python-zope.proxy 4.1.4-2 ii zope-common 0.5.54 ii zope2.13 2.13.22-1 clean@teco:~$ /usr/lib/zope2.13/bin/python import zope.security._proxy Traceback (most recent call last): File console, line 1, in module ImportError: No module named security._proxy and if I remove and then install zope2.13 (with python-zope.security still being removed) it is still the same: clean@teco:~$ dpkg -l |grep zope ii python-zope.interface 4.1.1-3.1 ii python-zope.proxy 4.1.4-2 ii
Bug#774794: dpkg: Add breaks for new trigger cycles
Hi! On Tue, 2015-01-13 at 13:08:08 +0100, Andreas Beckmann wrote: Followup-For: Bug #774794 found another loop in a wheezy - wheezy-backports - jessie upgrade of debian-security-support, full log attached: Preparing to unpack .../libudev1_215-8_amd64.deb ... Unpacking libudev1:amd64 (215-8) ... Processing triggers for debian-security-support (2014.09.07~bpo70+1) ... Setting up libudev1:amd64 (215-8) ... Processing triggers for libc-bin (2.19-13) ... (Reading database ... 6958 files and directories currently installed.) Preparing to unpack .../debconf_1.5.55_all.deb ... Unpacking debconf (1.5.55) over (1.5.49) ... Setting up debconf (1.5.55) ... (Reading database ... 6953 files and directories currently installed.) Preparing to unpack .../libpam0g_1.1.8-3.1_amd64.deb ... Unpacking libpam0g:amd64 (1.1.8-3.1) over (1.1.3-7.1) ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: debian-security-support - debian-security-support packages' pending triggers which are or may be unresolvable: debian-security-support: /usr dpkg: error processing package debian-security-support (--configure): triggers looping, abandoned Setting up libpam0g:amd64 (1.1.8-3.1) ... Processing triggers for libc-bin (2.19-13) ... Errors were encountered while processing: debian-security-support Ah, indeed, did not add packages not present in wheezy. I'll also include this one, and check if I filed other bugs for packages not in wheezy. Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764138: marked as done (fails to create new wallet or recover from seed)
Your message dated Tue, 13 Jan 2015 12:18:24 + with message-id e1yb0qs-0007hk...@franck.debian.org and subject line Bug#764138: fixed in electrum 1.9.8-4 has caused the Debian Bug report #764138, regarding fails to create new wallet or recover from seed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 764138: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764138 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: electrum Version: 1.9.8-1 Severity: normal I have no .electrum directory, and would like to recover a wallet from a seed. So I start electrum. It displays a Electrum could not find an existing wallet dialog. I pick an option (which one doesn't matter) and click Next. It then displays the same dialog again. I click Next again. Now it fails with No seed. What does still work is: electrum -g text with the create or restore commands. Also, the electrum gui seems to work once a wallet is in place, it's just the wizard to create/recover a wallet that has a busted interface. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages electrum depends on: ii python 2.7.8-1 ii python-electrum 1.9.8-1 electrum recommends no packages. electrum suggests no packages. -- no debconf information -- see shy jo signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: electrum Source-Version: 1.9.8-4 We believe that the bug you reported is fixed in the latest version of electrum, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 764...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tristan Seligmann mithra...@debian.org (supplier of updated electrum package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 13 Jan 2015 13:29:08 +0200 Source: electrum Binary: python-electrum electrum Architecture: source all Version: 1.9.8-4 Distribution: unstable Urgency: medium Maintainer: Debian Bitcoin Packaging Team pkg-bitcoin-de...@lists.alioth.debian.org Changed-By: Tristan Seligmann mithra...@debian.org Description: electrum - Easy to use bitcoin client python-electrum - Easy to use Bitcoin client - Python module Closes: 764138 Changes: electrum (1.9.8-4) unstable; urgency=medium . [ Tristan Seligmann ] * Backport upstream patch fixing wallet wizard (closes: #764138). Checksums-Sha1: 6bb89c46f7c455b73bdca2b61c8e2790ebc6c8dc 2262 electrum_1.9.8-4.dsc 3fd878eff52a79d805ffa75c51b0640681504183 497724 electrum_1.9.8-4.debian.tar.xz d94b59107ae60ae45f6aa1455fc0acb06b5779d0 231786 python-electrum_1.9.8-4_all.deb 03393d3742354eaf90ae1c8bfc154e97d917beb6 124958 electrum_1.9.8-4_all.deb Checksums-Sha256: 628e08e968b84bc1c4bdc8023e00632b04830d417afc823258a8978731e64d80 2262 electrum_1.9.8-4.dsc eac3ede5102e9546f4a184db013e4b537767571780b5c946ab73ec2454e4f744 497724 electrum_1.9.8-4.debian.tar.xz 2975b2bcd91fd377682e7e22afa5d05051f4f8f3b49d1ebc3eb20d6e2ccd0551 231786 python-electrum_1.9.8-4_all.deb c733d9c3d02799af8d0de5b76e22631bae8fd8469b41fc7c8a29b89ccb409ef2 124958 electrum_1.9.8-4_all.deb Files: daa87f3413dda95768c7fe551a8c00d7 2262 utils optional electrum_1.9.8-4.dsc e696c69dee4376cb42fbc1cda9afd52f 497724 utils optional electrum_1.9.8-4.debian.tar.xz d1a20c9e75342eb3a8676ab8d2cee9f3 231786 python optional python-electrum_1.9.8-4_all.deb f05d6a100d222a373c7886f18649b969 124958 utils optional electrum_1.9.8-4_all.deb -BEGIN PGP SIGNATURE- iQJ8BAEBCgBmBQJUtQsQXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREQjI0RTMxNUVEQUFBQzEzRDY0NjcwOTk1 OEMwRkIxQ0RFM0I3NjAwAAoJEFjA+xzeO3YA35IQALvgDKiSSJE2WK1omX/Mzbt7 ikqKUpUIeI8qbNTWfZWDekaDWXIja91aXMEei1r7rYFx9EXIjJu1gjB7mjTnLfnl PyN7VmhW20r8wP2y8Ftj2jt4whnQFemBy0L22+VRKOETBW7SkTlJQbSOCqrqJahF QJoGPCAdGTT5Bv4E3PCaREIz107GCP/k55/BVICI4VtFEaVTofOi8zqigk9M+dFV
Processed: unarchiving 768245
Processing commands for cont...@bugs.debian.org:
unarchive 768245
Bug #768245 {Done: Ondřej Surý ond...@debian.org}
[opendnssec-enforcer-sqlite3,opendnssec-enforcer-mysql]
opendnssec-enforcer-{sqlite3, mysql}: unhandled symlink to directory
conversion: /usr/share/doc/PACKAGE
Unarchived Bug 768245
thanks
Stopping processing here.
Please contact me if you need assistance.
--
768245: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768245
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: opendnssec-enforcer-{sqlite3, mysql}: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Processing control commands:
found -1 1:1.4.6-5
Bug #768245 {Done: Ondřej Surý ond...@debian.org}
[opendnssec-enforcer-sqlite3,opendnssec-enforcer-mysql]
opendnssec-enforcer-{sqlite3, mysql}: unhandled symlink to directory
conversion: /usr/share/doc/PACKAGE
Marked as found in versions opendnssec/1:1.4.6-5; no longer marked as fixed in
versions opendnssec/1:1.4.6-5 and reopened.
--
768245: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768245
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768245: opendnssec-enforcer-{sqlite3, mysql}: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Followup-For: Bug #768245 Control: found -1 1:1.4.6-5 Hi Ondrey, are you up for another iteration? The packages in wheezy-backports have yet another symlink - pointing to opendnssec-common (which was already once in your maintscripts, but we replaced it by another target). I think the approach of listing them all in the .maintscript should work here, too. (Don't forget the version bump to -6~ for the newly added ones). After an upgrade wheezy - wheezy-backports - jessie I get: 1m7.8s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/opendnssec-enforcer-sqlite3/NEWS.Debian.gz (opendnssec-enforcer-sqlite3) != /usr/share/doc/opendnssec-common/NEWS.Debian.gz (opendnssec-common) /usr/share/doc/opendnssec-enforcer-sqlite3 - opendnssec-common /usr/share/doc/opendnssec-enforcer-sqlite3/changelog.Debian.gz (opendnssec-enforcer-sqlite3) != /usr/share/doc/opendnssec-common/changelog.Debian.gz (opendnssec-common) /usr/share/doc/opendnssec-enforcer-sqlite3 - opendnssec-common /usr/share/doc/opendnssec-enforcer-sqlite3/changelog.gz (opendnssec-enforcer-sqlite3) != /usr/share/doc/opendnssec-common/changelog.gz (opendnssec-common) /usr/share/doc/opendnssec-enforcer-sqlite3 - opendnssec-common /usr/share/doc/opendnssec-enforcer-sqlite3/copyright (opendnssec-enforcer-sqlite3) != /usr/share/doc/opendnssec-common/copyright (opendnssec-common) /usr/share/doc/opendnssec-enforcer-sqlite3 - opendnssec-common 1m13.3s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/opendnssec-enforcer-mysql/NEWS.Debian.gz (opendnssec-enforcer-mysql) != /usr/share/doc/opendnssec-common/NEWS.Debian.gz (opendnssec-common) /usr/share/doc/opendnssec-enforcer-mysql - opendnssec-common /usr/share/doc/opendnssec-enforcer-mysql/changelog.Debian.gz (opendnssec-enforcer-mysql) != /usr/share/doc/opendnssec-common/changelog.Debian.gz (opendnssec-common) /usr/share/doc/opendnssec-enforcer-mysql - opendnssec-common /usr/share/doc/opendnssec-enforcer-mysql/changelog.gz (opendnssec-enforcer-mysql) != /usr/share/doc/opendnssec-common/changelog.gz (opendnssec-common) /usr/share/doc/opendnssec-enforcer-mysql - opendnssec-common /usr/share/doc/opendnssec-enforcer-mysql/copyright (opendnssec-enforcer-mysql) != /usr/share/doc/opendnssec-common/copyright (opendnssec-common) /usr/share/doc/opendnssec-enforcer-mysql - opendnssec-common There is also a file being left after purge: 1m18.8s INFO: Warning: Package purging left files on system: /etc/opendnssec/zonefetch.xml not owned Andreas opendnssec-enforcer-sqlite3_1:1.4.6-5.log.gz Description: application/gzip
Processed (with 1 errors): Re: Bug#775267: ERROR: dictionaries-common is broken - called emacs-package-remove as a new-style add-on, but has no compat file.
Processing control commands:
reassign -1 emacsen-common
Bug #775267 [dictionaries-common] ERROR: dictionaries-common is broken - called
emacs-package-remove as a new-style add-on, but has no compat file.
Bug reassigned from package 'dictionaries-common' to 'emacsen-common'.
No longer marked as found in versions dictionaries-common/1.23.17.
Ignoring request to alter fixed versions of bug #775267 to the same values
previously set
forcemerge 736062 775267
Bug #736062 {Done: Rob Browning r...@defaultvalue.org} [emacsen-common]
emacsen-common: emacs-package-install --preinst displays incorrect error message
Bug #775267 [emacsen-common] ERROR: dictionaries-common is broken - called
emacs-package-remove as a new-style add-on, but has no compat file.
Severity set to 'normal' from 'serious'
Failed to forcibly merge 736062: Not altering archived bugs; see unarchive.
--
736062: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736062
775267: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775267
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775267: ERROR: dictionaries-common is broken - called emacs-package-remove as a new-style add-on, but has no compat file.
Control: reassign -1 emacsen-common Control: forcemerge 736062 775267 On Tue, Jan 13, 2015 at 12:49:37PM +0100, Andreas Beckmann wrote: Package: dictionaries-common Version: 1.23.17 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, noticed this during a piuparts test (wheezy2jessie-rcmd, gnumed-client): Preparing to replace dictionaries-common 1.12.11 (using .../dictionaries-common_1.23.17_all.deb) ... ERROR: dictionaries-common is broken - called emacs-package-remove as a new-style add-on, but has no compat file. Leaving 'diversion of /usr/share/dict/words to /usr/share/dict/words.pre-dictionaries-common by dictionaries-common' Unpacking replacement dictionaries-common ... It does not fail (in d-c) but this sounds scary. Hi, Andreas, Do not worry, this is emacsen-common testing things in the wrong place and issuing a far too scary message. See [emacsen-common: emacs-package-install --preinst displays incorrect error message] https://bugs.debian.org/736062 Old emacs-package-install tests for a compat file during its invocation from dictionaries-common preinst, when the updated add-on is not yet unpacked. And at that time fixed emacsen-common (2.0.8) seems not yet installed, so old script is used. Normal dependencies will only help sorting configure stage. Note that you might see this message in other emacsen add-ons. Reassigning to emacsen-common (Hi, Rob) and forcemerging with closed #736062. Regards, -- Agustin -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768245: opendnssec-enforcer-{sqlite3, mysql}: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
1:1.4.6-6 was uploaded right now. Please retest when you have a time and I will fill an unblock request. O. On Tue, Jan 13, 2015, at 14:49, Ondřej Surý wrote: Hi Andreas, oh my... Somehow I with the dh_installdoc --link-doc= was never introduced :). Building fixed package right now. I have tidied the others as well and bumped required dpkg to 1.17.14. O. On Tue, Jan 13, 2015, at 13:47, Andreas Beckmann wrote: Followup-For: Bug #768245 Control: found -1 1:1.4.6-5 Hi Ondrey, are you up for another iteration? The packages in wheezy-backports have yet another symlink - pointing to opendnssec-common (which was already once in your maintscripts, but we replaced it by another target). I think the approach of listing them all in the .maintscript should work here, too. (Don't forget the version bump to -6~ for the newly added ones). After an upgrade wheezy - wheezy-backports - jessie I get: 1m7.8s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/opendnssec-enforcer-sqlite3/NEWS.Debian.gz (opendnssec-enforcer-sqlite3) != /usr/share/doc/opendnssec-common/NEWS.Debian.gz (opendnssec-common) /usr/share/doc/opendnssec-enforcer-sqlite3 - opendnssec-common /usr/share/doc/opendnssec-enforcer-sqlite3/changelog.Debian.gz (opendnssec-enforcer-sqlite3) != /usr/share/doc/opendnssec-common/changelog.Debian.gz (opendnssec-common) /usr/share/doc/opendnssec-enforcer-sqlite3 - opendnssec-common /usr/share/doc/opendnssec-enforcer-sqlite3/changelog.gz (opendnssec-enforcer-sqlite3) != /usr/share/doc/opendnssec-common/changelog.gz (opendnssec-common) /usr/share/doc/opendnssec-enforcer-sqlite3 - opendnssec-common /usr/share/doc/opendnssec-enforcer-sqlite3/copyright (opendnssec-enforcer-sqlite3) != /usr/share/doc/opendnssec-common/copyright (opendnssec-common) /usr/share/doc/opendnssec-enforcer-sqlite3 - opendnssec-common 1m13.3s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/opendnssec-enforcer-mysql/NEWS.Debian.gz (opendnssec-enforcer-mysql) != /usr/share/doc/opendnssec-common/NEWS.Debian.gz (opendnssec-common) /usr/share/doc/opendnssec-enforcer-mysql - opendnssec-common /usr/share/doc/opendnssec-enforcer-mysql/changelog.Debian.gz (opendnssec-enforcer-mysql) != /usr/share/doc/opendnssec-common/changelog.Debian.gz (opendnssec-common) /usr/share/doc/opendnssec-enforcer-mysql - opendnssec-common /usr/share/doc/opendnssec-enforcer-mysql/changelog.gz (opendnssec-enforcer-mysql) != /usr/share/doc/opendnssec-common/changelog.gz (opendnssec-common) /usr/share/doc/opendnssec-enforcer-mysql - opendnssec-common /usr/share/doc/opendnssec-enforcer-mysql/copyright (opendnssec-enforcer-mysql) != /usr/share/doc/opendnssec-common/copyright (opendnssec-common) /usr/share/doc/opendnssec-enforcer-mysql - opendnssec-common There is also a file being left after purge: 1m18.8s INFO: Warning: Package purging left files on system: /etc/opendnssec/zonefetch.xmlnot owned Andreas Email had 1 attachment: + opendnssec-enforcer-sqlite3_1:1.4.6-5.log.gz 39k (application/gzip) -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775250: marked as done (wicd: modifies isc-dhcp conffile)
Your message dated Tue, 13 Jan 2015 14:52:18 +0100 with message-id 20150113135217.ga15...@sym.noone.org and subject line Re: Bug#775250: wicd: modifies isc-dhcp conffile has caused the Debian Bug report #775250, regarding wicd: modifies isc-dhcp conffile to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 775250: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775250 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- package: src:wicd version: 1.7.2.4-4 severity: serious According to [0] wicd modifies /etc/dhcp/dhclient.conf, which is a policy violation. Best wishes, Mike [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773749#10 ---End Message--- ---BeginMessage--- Control: notfound -1 1.7.2.4-4 Michael Gilbert wrote: According to [0] wicd modifies /etc/dhcp/dhclient.conf, which is a policy violation. [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773749#10 Please explain which part of the policy is violated. This editing of /etc/dhcp/dhclient.conf has not happened in the maintainer scripts, but only because the user instructed wicd via one of its user interfaces to do so. That's a feature, not a bug. From my point of view this puts wicd in the same position as any file or configuration editor and hence can't be a policy violation -- because otherwise vim or emacs would be a huge policy violation, too. Hence closing this bug report. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE---End Message---
Bug#769685: marked as done (awscli: FTBFS: ImportError: Failed to import test module: awscli.testutils)
Your message dated Tue, 13 Jan 2015 15:24:02 +
with message-id e1yb3k6-0003s1...@franck.debian.org
and subject line Bug#769685: fixed in python-botocore 0.81.0-1
has caused the Debian Bug report #769685,
regarding awscli: FTBFS: ImportError: Failed to import test module:
awscli.testutils
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
769685: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769685
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: awscli
Version: 1.5.5-1
Severity: serious
From my pbuilder build log:
...
dh_auto_test -O--buildsystem=pybuild
I: pybuild base:170: cd /tmp/buildd/awscli-1.5.5/.pybuild/pythonX.Y_3.4/build;
python3.4 -m unittest discover -v
awscli.testutils (unittest.loader.ModuleImportFailure) ... ERROR
==
ERROR: awscli.testutils (unittest.loader.ModuleImportFailure)
--
Traceback (most recent call last):
File /usr/lib/python3.4/unittest/case.py, line 58, in testPartExecutor
yield
File /usr/lib/python3.4/unittest/case.py, line 577, in run
testMethod()
File /usr/lib/python3.4/unittest/loader.py, line 32, in testFailure
raise exception
ImportError: Failed to import test module: awscli.testutils
Traceback (most recent call last):
File /usr/lib/python3.4/unittest/loader.py, line 312, in _find_tests
module = self._get_module_from_name(name)
File /usr/lib/python3.4/unittest/loader.py, line 290, in
_get_module_from_name
__import__(name)
File
/tmp/buildd/awscli-1.5.5/.pybuild/pythonX.Y_3.4/build/awscli/testutils.py,
line 47, in module
from botocore.session import Session
File /usr/lib/python3/dist-packages/botocore/session.py, line 29, in
module
from botocore.endpoint import EndpointCreator
File /usr/lib/python3/dist-packages/botocore/endpoint.py, line 28, in
module
from botocore.awsrequest import AWSRequest
File /usr/lib/python3/dist-packages/botocore/awsrequest.py, line 27, in
module
from requests.packages.urllib3.connection import HTTPConnection
ImportError: cannot import name 'HTTPConnection'
--
Ran 1 test in 0.001s
FAILED (errors=1)
E: pybuild pybuild:256: test: plugin distutils failed with: exit code=1: cd
/tmp/buildd/awscli-1.5.5/.pybuild/pythonX.Y_3.4/build; python3.4 -m unittest
discover -v
dh_auto_test: pybuild --test -i python{version} -p 3.4 --dir . returned exit
code 13
debian/rules:8: recipe for target 'build' failed
make: *** [build] Error 13
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--
Daniel Schepler
---End Message---
---BeginMessage---
Source: python-botocore
Source-Version: 0.81.0-1
We believe that the bug you reported is fixed in the latest version of
python-botocore, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 769...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
TANIGUCHI Takaki tak...@debian.org (supplier of updated python-botocore
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 13 Jan 2015 23:06:39 +0900
Source: python-botocore
Binary: python-botocore python3-botocore
Architecture: source all
Version: 0.81.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team
python-modules-t...@lists.alioth.debian.org
Changed-By: TANIGUCHI Takaki tak...@debian.org
Description:
python-botocore - Low-level, data-driven core of boto 3 (Python 2)
python3-botocore - Low-level, data-driven core of boto 3 (Python 3)
Closes: 769685
Changes:
python-botocore (0.81.0-1) unstable; urgency=medium
.
* New upstream release
* Refresh patch. (Closes: #769685)
Checksums-Sha1:
252ddfea598e305e9ec7de902947b6b90af5324b 2157 python-botocore_0.81.0-1.dsc
1320641df25ef12ea9487d021cade0fd59f0e96f 903736
python-botocore_0.81.0.orig.tar.gz
957c5c5c8218b958999a0b733135595d658b5656 3360
python-botocore_0.81.0-1.debian.tar.xz
241063875d03fe5055fd1dff5e79d310bcbc90f0 542374
python-botocore_0.81.0-1_all.deb
Bug#768245: marked as done (opendnssec-enforcer-{sqlite3, mysql}: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)
Your message dated Tue, 13 Jan 2015 15:23:52 +
with message-id e1yb3jw-0003pm...@franck.debian.org
and subject line Bug#768245: fixed in opendnssec 1:1.4.6-6
has caused the Debian Bug report #768245,
regarding opendnssec-enforcer-{sqlite3, mysql}: unhandled symlink to directory
conversion: /usr/share/doc/PACKAGE
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
768245: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768245
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: opendnssec-enforcer-sqlite3,opendnssec-enforcer-mysql
Version: 1:1.4.6-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.
This was observed on the following upgrade paths:
wheezy - jessie
For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile
For other overwritten locations anything interesting may happen.
Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase
It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.2)
to perform the conversion, ideally using d/$PACKAGE.mainstscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.
From the attached log (usually somewhere in the middle...):
1m5.2s ERROR: FAIL: silently overwrites files via directory symlinks:
/usr/share/doc/opendnssec-enforcer-sqlite3/NEWS.Debian.gz
(opendnssec-enforcer-sqlite3) !=
/usr/share/doc/opendnssec-enforcer/NEWS.Debian.gz (opendnssec-enforcer)
/usr/share/doc/opendnssec-enforcer-sqlite3/changelog.Debian.gz
(opendnssec-enforcer-sqlite3) !=
/usr/share/doc/opendnssec-enforcer/changelog.Debian.gz (opendnssec-enforcer)
/usr/share/doc/opendnssec-enforcer-sqlite3/changelog.gz
(opendnssec-enforcer-sqlite3) !=
/usr/share/doc/opendnssec-enforcer/changelog.gz (opendnssec-enforcer)
/usr/share/doc/opendnssec-enforcer-sqlite3/copyright
(opendnssec-enforcer-sqlite3) != /usr/share/doc/opendnssec-enforcer/copyright
(opendnssec-enforcer)
1m9.5s ERROR: FAIL: silently overwrites files via directory symlinks:
/usr/share/doc/opendnssec-enforcer-mysql/NEWS.Debian.gz
(opendnssec-enforcer-mysql) !=
/usr/share/doc/opendnssec-enforcer/NEWS.Debian.gz (opendnssec-enforcer)
/usr/share/doc/opendnssec-enforcer-mysql/changelog.Debian.gz
(opendnssec-enforcer-mysql) !=
/usr/share/doc/opendnssec-enforcer/changelog.Debian.gz (opendnssec-enforcer)
/usr/share/doc/opendnssec-enforcer-mysql/changelog.gz
(opendnssec-enforcer-mysql) != /usr/share/doc/opendnssec-enforcer/changelog.gz
(opendnssec-enforcer)
/usr/share/doc/opendnssec-enforcer-mysql/copyright
(opendnssec-enforcer-mysql) != /usr/share/doc/opendnssec-enforcer/copyright
(opendnssec-enforcer)
cheers,
Andreas
opendnssec-enforcer-sqlite3_1:1.4.6-2.log.gz
Description: application/gzip
---End Message---
---BeginMessage---
Source: opendnssec
Source-Version: 1:1.4.6-6
We believe that the bug you reported is fixed in the latest version of
opendnssec, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 768...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ondřej Surý ond...@debian.org (supplier of updated opendnssec package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 13 Jan 2015 14:25:18
Processed: tagging 768076
Processing commands for cont...@bugs.debian.org:
tags 768076 + pending
Bug #768076 {Done: Andreas Metzler ametz...@debian.org} [abcde] abcde: latest
upstream version breaks eyeD3 usage
Bug #772778 {Done: Andreas Metzler ametz...@debian.org} [abcde] abcde:
Tagging mp3 fails with eyeD3 - version conflict
Added tag(s) pending.
Added tag(s) pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
768076: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768076
772778: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772778
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775102: bitcoin: OpenSSL 1.0.1k incompatibility with Bitcoin Core
This bug also makes bitcoin FTBFS: http://mitya57.me/builds/bitcoin_0.9.3-1_amd64.build -- Dmitry Shachnev signature.asc Description: OpenPGP digital signature
Processed: tagging 775276
Processing commands for cont...@bugs.debian.org: tags 775276 + upstream fixed-upstream Bug #775276 [condor] condor: CVE-2014-8126 Added tag(s) upstream and fixed-upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 775276: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775276 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: tags 775102 upstream fixed-upstream Bug #775102 [bitcoin] bitcoin: OpenSSL 1.0.1k incompatibility with Bitcoin Core Added tag(s) upstream and fixed-upstream. End of message, stopping processing here. Please contact me if you need assistance. -- 775102: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775102 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773749: Resolvconf vs wicd
I just read bug report #514597 entitled wicd does not work properly with resolvconf which was closed in version 1.5.9-2 with the message that 07-add_resolvconf_support.patch added. Although I don't see this patch in the current source tree, I do see references to the resolvconf program which indicate that resolvconf is supported by wicd to some extent. $ grep -r resolvconf . [...] wicd-1.7.2.4/wicd/wnettools.py: Checks for the existence of resolvconf. wicd-1.7.2.4/wicd/wnettools.py:self.resolvconf_cmd = self._find_program_path(resolvconf) wicd-1.7.2.4/wicd/wnettools.py:if self.resolvconf_cmd: wicd-1.7.2.4/wicd/wnettools.py:cmd = [self.resolvconf_cmd, '-a', self.iface] We can at least conclude that the problem isn't that wicd has never been adapted to cooperate with resolvconf. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773749: Resolvconf vs wicd
Hi Thomas, Thomas Hood wrote: I just read bug report #514597 entitled wicd does not work properly with resolvconf which was closed in version 1.5.9-2 with the message that 07-add_resolvconf_support.patch added. Although I don't see this patch in the current source tree, I do see references to the resolvconf program which indicate that resolvconf is supported by wicd to some extent. Yes, the patch has been removed with the 1.6.0-1 upload with the following changelog entry: * debian/patches/: - 01-fix_desktop_file.patch, 07-add_resolvconf_support.patch removed, fixed upstream Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): merging 774461 775188
Processing commands for cont...@bugs.debian.org: merge 774461 775188 Bug #774461 [src:linux] linux-image-3.2.0-4-amd64: suspend triggers reboot Bug #774436 [src:linux] linux-image-3.2.0-4-amd64: suspend to ram regression in 3.2.65-1 Bug #774526 [src:linux] linux-image-3.2.0-4-amd64: system crash with sudden reboot when hotplugging a CPU - suspend functionality broken Bug #775059 [src:linux] linux-image-3.2.0-4-amd64: kernel update broke suspend to ram - system crashes instead Bug #775123 [src:linux] (no subject) Bug #775154 [src:linux] linux-image-3.2.0-4-amd64: Wake/suspend-to-ram loop in 3.2.65-1 Bug #775157 [src:linux] base: Crash on resume after suspend-to-ram Bug #775178 [src:linux] linux-image-3.2.0-4-amd64: linux-image-3.2.0-4-amd64: regression: suspend/resume not working after update (again) Bug #775246 [src:linux] general: Debian does wake from suspend. It either hard reboots or remains unresponsive. Unable to merge bugs because: severity of #775188 is 'normal' not 'serious' affects of #775188 is '' not 'release.debian.org' Failed to merge 774461: Did not alter merged bugs thanks Stopping processing here. Please contact me if you need assistance. -- 774436: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774436 774461: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774461 774526: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774526 775059: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775059 775123: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775123 775154: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775154 775157: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775157 775178: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775178 775188: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775188 775246: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775246 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reassign 775188 to src:linux, merging 774461 774461
Processing commands for cont...@bugs.debian.org: reassign 775188 src:linux Bug #775188 [linux-image] Resume from suspend is not working after kernel upgrading Warning: Unknown package 'linux-image' Bug reassigned from package 'linux-image' to 'src:linux'. Ignoring request to alter found versions of bug #775188 to the same values previously set Ignoring request to alter fixed versions of bug #775188 to the same values previously set merge 774461 774461 Bug #774461 [src:linux] linux-image-3.2.0-4-amd64: suspend triggers reboot Bug #774436 [src:linux] linux-image-3.2.0-4-amd64: suspend to ram regression in 3.2.65-1 Bug #774526 [src:linux] linux-image-3.2.0-4-amd64: system crash with sudden reboot when hotplugging a CPU - suspend functionality broken Bug #775059 [src:linux] linux-image-3.2.0-4-amd64: kernel update broke suspend to ram - system crashes instead Bug #775123 [src:linux] (no subject) Bug #775154 [src:linux] linux-image-3.2.0-4-amd64: Wake/suspend-to-ram loop in 3.2.65-1 Bug #775157 [src:linux] base: Crash on resume after suspend-to-ram Bug #775178 [src:linux] linux-image-3.2.0-4-amd64: linux-image-3.2.0-4-amd64: regression: suspend/resume not working after update (again) Bug #775246 [src:linux] general: Debian does wake from suspend. It either hard reboots or remains unresponsive. Bug #774436 [src:linux] linux-image-3.2.0-4-amd64: suspend to ram regression in 3.2.65-1 Bug #774526 [src:linux] linux-image-3.2.0-4-amd64: system crash with sudden reboot when hotplugging a CPU - suspend functionality broken Bug #775059 [src:linux] linux-image-3.2.0-4-amd64: kernel update broke suspend to ram - system crashes instead Bug #775123 [src:linux] (no subject) Bug #775154 [src:linux] linux-image-3.2.0-4-amd64: Wake/suspend-to-ram loop in 3.2.65-1 Bug #775157 [src:linux] base: Crash on resume after suspend-to-ram Bug #775178 [src:linux] linux-image-3.2.0-4-amd64: linux-image-3.2.0-4-amd64: regression: suspend/resume not working after update (again) Bug #775246 [src:linux] general: Debian does wake from suspend. It either hard reboots or remains unresponsive. Merged 774436 774461 774526 775059 775123 775154 775157 775178 775246 thanks Stopping processing here. Please contact me if you need assistance. -- 774436: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774436 774461: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774461 774526: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774526 775059: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775059 775123: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775123 775154: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775154 775157: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775157 775178: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775178 775188: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775188 775246: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775246 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: forcibly merging 774461 775188
Processing commands for cont...@bugs.debian.org: forcemerge 774461 775188 Bug #774461 [src:linux] linux-image-3.2.0-4-amd64: suspend triggers reboot Bug #774436 [src:linux] linux-image-3.2.0-4-amd64: suspend to ram regression in 3.2.65-1 Bug #774526 [src:linux] linux-image-3.2.0-4-amd64: system crash with sudden reboot when hotplugging a CPU - suspend functionality broken Bug #775059 [src:linux] linux-image-3.2.0-4-amd64: kernel update broke suspend to ram - system crashes instead Bug #775123 [src:linux] (no subject) Bug #775154 [src:linux] linux-image-3.2.0-4-amd64: Wake/suspend-to-ram loop in 3.2.65-1 Bug #775157 [src:linux] base: Crash on resume after suspend-to-ram Bug #775178 [src:linux] linux-image-3.2.0-4-amd64: linux-image-3.2.0-4-amd64: regression: suspend/resume not working after update (again) Bug #775246 [src:linux] general: Debian does wake from suspend. It either hard reboots or remains unresponsive. Bug #775188 [src:linux] Resume from suspend is not working after kernel upgrading Severity set to 'serious' from 'normal' Added indication that 775188 affects release.debian.org Marked as found in versions linux/3.2.65-1. Added tag(s) confirmed and patch. Bug #774436 [src:linux] linux-image-3.2.0-4-amd64: suspend to ram regression in 3.2.65-1 Bug #774526 [src:linux] linux-image-3.2.0-4-amd64: system crash with sudden reboot when hotplugging a CPU - suspend functionality broken Bug #775059 [src:linux] linux-image-3.2.0-4-amd64: kernel update broke suspend to ram - system crashes instead Bug #775123 [src:linux] (no subject) Bug #775154 [src:linux] linux-image-3.2.0-4-amd64: Wake/suspend-to-ram loop in 3.2.65-1 Bug #775157 [src:linux] base: Crash on resume after suspend-to-ram Bug #775178 [src:linux] linux-image-3.2.0-4-amd64: linux-image-3.2.0-4-amd64: regression: suspend/resume not working after update (again) Bug #775246 [src:linux] general: Debian does wake from suspend. It either hard reboots or remains unresponsive. Merged 774436 774461 774526 775059 775123 775154 775157 775178 775188 775246 thanks Stopping processing here. Please contact me if you need assistance. -- 774436: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774436 774461: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774461 774526: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774526 775059: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775059 775123: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775123 775154: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775154 775157: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775157 775178: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775178 775188: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775188 775246: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775246 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773749: Resolvconf vs wicd
Hi, Thomas Hood wrote: 1. When (if ever) does wicd modify dhclient.conf? I claim that it doesn't touch the one at /etc/dhcp/dhclient.conf at all. From the bug report and the logic (you can set things like search domains and DNS servers statically per configured connection, e.g. per WLAN), I would have had expected that it does so always after the user requested to connect to a network, but before it starts dhclient for this connection. But it doesn't use /etc/dhcp/dhclient.conf for that (probably because it should also work when using static IPs) but (without having resolvconf installed) modifies /etc/resolv.conf directly as it seems. At least for a short moment the message Modifying /etc/resolv.conf or similar was shown in wicd-curses' status line. According to /etc/wicd/dhclient.conf.template.default the idea is to generate a dhclient.conf somewhere under /var/run/, but actually and according to /usr/share/pyshared/wicd/wnettools.py it's at /var/lib/wicd/dhclient.conf. Here are the wicd related files under /var on one of my systems: ~ → tree /var/lib/wicd /var/run/wicd /var/lib/wicd ├── configurations │ ├── 000f66a720db │ ├── […] │ └── f02572ca7274 ├── dhclient.conf └── resolv.conf.orig /var/run/wicd └── wicd.pid Additionally I found no evidence in the code at all that wicd accesses /etc/dhcp/dhclient.conf -- and it didn't look as if it did that on my machines. But then again, I stopped using resolvconf years ago, so my machines may not be the proper examples since this bug report is now against resolvconf. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774014: marked as done (Segfault after testing connectivity)
Your message dated Tue, 13 Jan 2015 23:18:32 +
with message-id e1ybaji-kv...@franck.debian.org
and subject line Bug#774014: fixed in concordance 1.1-3
has caused the Debian Bug report #774014,
regarding Segfault after testing connectivity
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
774014: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774014
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: python-libconcord
Version: 1.1-2
Severity: grave
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi!
After testing connectivity, python-libconcord segfaults:
*** buffer overflow detected ***: python terminated
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x7303f)[0x7f097257f03f]
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7f0972602147]
/lib/x86_64-linux-gnu/libc.so.6(+0xf4360)[0x7f0972600360]
/lib/x86_64-linux-gnu/libc.so.6(+0xf3869)[0x7f09725ff869]
/lib/x86_64-linux-gnu/libc.so.6(_IO_default_xsputn+0x89)[0x7f0972582109]
/lib/x86_64-linux-gnu/libc.so.6(_IO_vfprintf+0x1ca2)[0x7f0972553ec2]
/lib/x86_64-linux-gnu/libc.so.6(__vsprintf_chk+0x88)[0x7f09725ff8f8]
/lib/x86_64-linux-gnu/libc.so.6(__sprintf_chk+0x7d)[0x7f09725ff84d]
/usr/lib/libconcord.so.3(_Z4PostPhjPKcR11TRemoteInfobbbPSsS4_+0x375)[0x7f0966b2a985]
/usr/lib/libconcord.so.3(post_connect_test_success+0x77)[0x7f0966b27407]
/usr/lib/x86_64-linux-gnu/libffi.so.6(ffi_call_unix64+0x4c)[0x7f0972089dc0]
/usr/lib/x86_64-linux-gnu/libffi.so.6(ffi_call+0x2f8)[0x7f0972089828]
/usr/lib/python2.7/lib-dynload/_ctypes.x86_64-linux-gnu.so(_ctypes_callproc+0x495)[0x7f09722f6055]
/usr/lib/python2.7/lib-dynload/_ctypes.x86_64-linux-gnu.so(+0x119b2)[0x7f09722fa9b2]
python(PyEval_EvalFrameEx+0xfe9)[0x4cb879]
python(PyEval_EvalFrameEx+0xb2a)[0x4cb3ba]
python[0x4e6cf0]
python[0x5052e8]
python(PyEval_CallObjectWithKeywords+0x6b)[0x4d28cb]
python[0x5bd472]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x80a4)[0x7f09731e00a4]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f09725f1ccd]
This is quite recent. I have used congruity without a problem one or
two months ago.
Here is a full backtrace:
#0 0x7fae55716107 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
resultvar = 0
pid = 21355
selftid = 21362
#1 0x7fae557174e8 in __GI_abort () at abort.c:89
save_stage = 2
act = {
__sigaction_handler = {
sa_handler = 0x2d303030,
sa_sigaction = 0x2d303030
},
sa_mask = {
__val = {3474076752553600614, 8659703141076316209,
3472328296227676272, 3472339291342909488, 2314885530818457632,
2314885530818453536, 8751468634664083488, 7568964844005712755,
3689962539751649127, 7292506702445175650, 3689072854590436406,
7291662475097157987, 3329345833768138338, 735262552734523747,
7149242536436000311, 0}
},
sa_flags = 52,
sa_restorer = 0x7fae4831a8a0
}
sigs = {
__val = {32, 0 repeats 15 times}
}
#2 0x7fae55754044 in __libc_message (do_abort=do_abort@entry=2,
fmt=fmt@entry=0x7fae558446ab *** %s ***: %s terminated\n) at
../sysdeps/posix/libc_fatal.c:175
ap = {{
gp_offset = 32,
fp_offset = 0,
overflow_arg_area = 0x7fae4831a8b0,
reg_save_area = 0x7fae4831a840
}}
fd = 14
on_2 = optimized out
list = optimized out
nlist = optimized out
cp = optimized out
written = optimized out
#3 0x7fae557d7147 in __GI___fortify_fail (msg=msg@entry=0x7fae55844642
buffer overflow detected) at fortify_fail.c:31
No locals.
#4 0x7fae557d5360 in __GI___chk_fail () at chk_fail.c:28
No locals.
#5 0x7fae557d4869 in _IO_str_chk_overflow (fp=optimized out,
c=optimized out) at vsprintf_chk.c:33
No locals.
#6 0x7fae55757109 in __GI__IO_default_xsputn (f=0x7fae4831aee0,
data=optimized out, n=848) at genops.c:480
s = 0x7fae40003ba0
AUSER=vincent%2Ebernat;CookieKeyValue={----, 'E' repeats
12 times,
}{F46BFA72-E0D5-4D14-84DF-3C0CCF64A22B}{C5783AFA-710E-48B6-91B4-A2A48C169F37}
more = 153
#7 0x7fae55728ec2 in _IO_vfprintf_internal (s=s@entry=0x7fae4831aee0,
format=optimized out, format@entry=0x7fae49cfffc0 POST /%s
HTTP/1.1\r\nUser-Agent: HarmonyBrowser/7.3.0 (Build 15; UpdatedFrom 7.3.0.15;
Skin logitech; Windows XP 5.1; x86; en; rv: 1.8.0.2)
Gecko/20060125\r\nContent-Type: application/x-www-form-urlencod...,
ap=ap@entry=0x7fae4831b018) at vfprintf.c:1636
len =
Bug#775313: debsums -c don't report all changed files
Package: debsums
Version: 2.0.52+deb7u1
Severity: serious
Tags: patch
Justification: required
Hi,
I'd like to notice, than the patch [2.0.52+nmu2 from Axel Beckert, see:
https://launchpadlibrarian.net/176696862/debsums_2.0.52%2Bnmu1_2.0.52%2Bnmu2.diff.gz]
creates this issue:
when there are two (or more) files (starting with the same string in the path),
so the changes of the shorter files are not reported
by debsums -c ... .
In my case for example:
# dpkg-query --admindir=/var/lib/dpkg -S bin/ls
util-linux: /bin/lsblk
syslinux-common: /usr/bin/lss16toppm
kmod: /bin/lsmod
e2fsprogs: /usr/bin/lsattr
lsb-release: /usr/bin/lsb_release
pciutils: /usr/bin/lspci
lsof: /usr/bin/lsof
usbutils: /usr/bin/lsusb
gnupg: /usr/bin/lspgpot
klibc-utils: /usr/lib/klibc/bin/ls
coreutils: /bin/ls
util-linux: /usr/bin/lscpu
initramfs-tools: /usr/bin/lsinitramfs
kmod: /sbin/lsmod
# dpkg-query --admindir=/var/lib/dpkg -S bin/ls| awk -F: '{print $1}'
util-linux
syslinux-common
kmod
e2fsprogs
lsb-release
pciutils
lsof
usbutils
gnupg
klibc-utils
coreutils
util-linux
initramfs-tools
kmod
So then $correct_package =
util-linux\nsyslinux-common\nkmod\ne2fsprogs\nlsb-release\npciutils\nlsof\nusbutils\ngnupg\nklibc-utils\ncoreutils\nutil-linux\ninitramfs-tools\nkmod
These files are silently skipped by the check:
if ($pack ne $correct_package) {
# print $pack != $correct_package\n;
return 0;
}
The starting slash of the '-S' argument can repare the main bug (this will not
use pattern *usr/sbin/inchange-reporting* is used):
# dpkg-query --admindir=/var/lib/dpkg -S /bin/ls| awk -F: '{print $1}'
coreutils
For example, change of /bin/ls will report nothing in wheeze, ..., unstable
will not report anything:
# cp -a /bin/ls /tmp/ls ; echo bad addon /bin/ls; debsums -c coreutils; cp
-a /tmp/ls /bin/ls
Since patched version report it:
# cp -a /bin/ls /tmp/ls ; echo bad addon /bin/ls; debsums.new -c
coreutils; cp -a /tmp/ls /bin/ls
/bin/ls
Please aply this patch to fix this issue:
# diff -Nu /usr/bin/debsums /usr/bin/debsums.new
--- /usr/bin/debsums2014-09-01 20:47:24.0 +0200
+++ /usr/bin/debsums.new2015-01-13 08:20:17.0 +0100
@@ -462,7 +462,7 @@
return 0;
}
- my $correct_package = `dpkg-query --admindir=$DPKG -S $path | awk -F:
'{print \$1}'`;
+ my $correct_package = `dpkg-query --admindir=$DPKG -S /$path | awk -F:
'{print \$1}'`;
chomp($correct_package);
if ($pack ne $correct_package) {
#print $pack != $correct_package\n;
Please fix it in wheeze, ...
With regards
-- Marek Veber
-- System Information:
Debian Release: 7.8
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-686-pae (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages debsums depends on:
ii dpkg 8:1.16.9+nmu1
ii libdpkg-perl 8:1.16.9+nmu1
ii libfile-fnmatch-perl 0.02-1+b2
ii perl 5.14.2-21+deb7u2
ii ucf 8:3.0025+nmu4.1
debsums recommends no packages.
debsums suggests no packages.
-- debconf information excluded
--- /usr/bin/debsums 2015-01-13 15:26:23.0 +0100
+++ /usr/bin/debsums.new 2015-01-13 08:20:17.0 +0100
@@ -462,7 +462,7 @@
return 0;
}
- my $correct_package = `dpkg-query --admindir=$DPKG -S $path | awk -F: '{print \$1}'`;
+ my $correct_package = `dpkg-query --admindir=$DPKG -S /$path | awk -F: '{print \$1}'`;
chomp($correct_package);
if ($pack ne $correct_package) {
#print $pack != $correct_package\n;
Bug#775255: [pkg-fetchmail-maint] Bug#775255: fetchmail: Fails to start when libssl has SSLv3 disabled
Hi,
* Chiraag Nataraj chiraag.nata...@gmail.com [2015-01-13 12:22]:
Package: fetchmail
Version: 6.3.26-1+b1
Severity: grave
Justification: renders package unusable
You filed a bug against a version that works absolutely fine with the openssl
version it is supposed to work with. Hence, I'm inclined to close that bug or
downgrade it to wishlist in favor of removing/disabling sslv3 support in
fetchmail.
When the latest version of libssl1.0.0 is installed from experimental (which
has SSLv3 disabled), Fetchmail exits with the following error:
fetchmail: relocation error: fetchmail: symbol SSLv3_client_method, version
OPENSSL_1.0.0 not defined in file libssl.so.1.0.0 with link time reference
See above
Fetchmail should be rebuilt to not require SSLv3.
The patch you included simply removes this feature entirely:
--- fetchmail-6.3.26/socket.c 2013-04-23 22:00:45.0 +0200
+++ socket.c2015-01-14 00:29:53.412608735 +0100
@@ -913,8 +913,6 @@
report(stderr, GT_(Your operating system does not
support SSLv2.\n));
return -1;
#endif
- } else if(!strcasecmp(ssl3,myproto)) {
- _ctx[sock] = SSL_CTX_new(SSLv3_client_method());
} else if(!strcasecmp(tls1,myproto)) {
_ctx[sock] = SSL_CTX_new(TLSv1_client_method());
} else if (!strcasecmp(ssl23,myproto)) {
In the current git version of fetchmail, sslv3 is not negotiated by default,
unless a user explicitly requests to do so. As such I'm not sure how useful
this patch is as well.
Matthias, do you mind weighing in on this?
Thanks
Nico
--
Nico Golde - XMPP: n...@jabber.ccc.de - GPG: 0xA0A0
pgpm4RkxJdrGf.pgp
Description: PGP signature
