Bug#761909: systemd does not unmount nfs shares before bringing down the network interface

2015-12-18 Thread Martin Pitt
Control: tag -1 upstream

Martin Pitt [2015-12-18  9:06 +0100]:
> Apparently 228 (or perhaps 227) changed behaviour so that
> ifup@.service always gets stopped, even if they have
> DefaultDependencies=no and thus no Conflicts=shutdown.target.

This applies to any instantiated unit apparenlty. Easily reproducible
in nspawn with

cat < /etc/systemd/system/letmelive@.service
[Unit]
Description=@@@ Let me live %i
DefaultDependencies=no

[Service]
RemainAfterExit=yes
StandardOutput=journal+console
ExecStart=/bin/true
ExecStop=/usr/bin/touch /nooo
ExecStop=/bin/echo "!!! I GOT KILLED !"
EOF
systemctl daemon-reload
systemctl start letmelive@1.service

and then reboot -- you will see that letmelive@1 gets stopped.

Martin
-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)


signature.asc
Description: Digital signature


Bug#801441: Upcoming stable point release (8.3)

2015-12-18 Thread Arto Jantunen
"Adam D. Barratt"  writes:

> Hi,
>
> The next point release for "jessie" (8.3) is scheduled for Saturday,
> January 23rd. Processing of new uploads into jessie-proposed-updates
> will be frozen during the preceding weekend.

Has the deadline already been missed for reviewing #801441?

-- 
Arto Jantunen



Bug#807343: RM: ghc [armel] -- ROM; Not supported on armel any more

2015-12-18 Thread John Paul Adrian Glaubitz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 12/17/2015 08:55 PM, Joachim Breitner wrote:
>> Neverthess, please actually hold this bug for a moment, Adrian
>> Glaubitz wants to give fixing ghc on armel a shot. Marking the
>> bug as moreinfo.
> 
> any progress so far?

Not yet. I have postponed it to the weekend. I was busy with fixing up
ghc on sparc64 and was also a bit overwhelmed by the Perl transition.

Matthias Klose also asked me to build Ada for m68k, sh4 and sparc64
which I have now commenced with.

Adrian

- -- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWc8uLAAoJEHQmOzf1tfkTbbQP/iYuwZYkVLT6gHr5DUG+NllU
isLp1h94aVtVuRYjvY2+MusdnRXuR1HBCsppFcVG3DyAnWzsME4F8wuSzy4ii//C
i9VhD7LJ5Dj0HCyyHrLiUpGIn+T4o9uqFnHXYVLw46vS4pJ21Y1+S8YR+CH3uFkw
IsmMTPGVFcF8p+I30nSv6yuf2hdWE6Yz4B9/czXVAQXb1j3hoK88x3F6R+ceE/GN
eyjHj7n3lGM/IMK1g+hNDh6cQTPqqKIonG3emN7I5fFDZ0H29ttAX9D3zaiJWec3
R0sNKPXKZ8DTKPiosF2HmM3+3/vP6eq4ZYvHWwUeJfvGccCR3qTGhu2MdHON2dK5
R0jePII9LGsRowl7HX//PiMNGk0Jscld8H1Nh7sFgGFlm5/8AUqepccOmOZRPNhu
nflC7xecxRxtS831Sz9xkVW3Nr1+iB8wfBMl6S2NolvY1F8PVvlpkqScvKdHU9+G
K7E7bGex1uwykksFYa+sPEEIqfftV5gSsuYahLMx1+MEK+BkE5LNlw3qTTKz41En
jcuq6xZUm+C6Umt7CQKp5W3Noo85GgPNL6+9c3PMaZa53vCk2mI6xpcTNwtw8lBZ
amps6WYrL61OnvJyvY/WmbW/R+UAFfgoXxiHiRUTMno8CV68vtqCku2Ei44D04Sn
PH7NkrHr4wsqk2lawPEg
=xPvH
-END PGP SIGNATURE-



Bug#808258: libreoffice-writer: libreoffice worst than microsoft word?

2015-12-18 Thread Rene Engelhard
retitle 808258 crash when pasting copied table from a website
tag 808258 + moreinfo
thanks

Hi,

I am actually not sure whether it's worth answering to this report with this 
subject
and "WTF?!! " /
"Is this WINDOWS 98 ???!!!".

Anyway.

On Thu, Dec 17, 2015 at 10:11:07PM +0100, Ara Keary wrote:
>downgrading ot testing or stable does not change anything
>How  can this happen???

Then it probably has to do with external libraries. We already had that in the 
past.
(And how did you downgrade to testing and/or stable? I mean for stable you'd 
need
other libs which shouldn't be installable in sid)

>A simple copy-paste  breaks a full document?
>Is this WINDOWS 98 ???!!!

No, but this is a bug and exactly this scenario made problems in the past too.

If you want your bug report taken seriously, you should stop with accusations 
and your
immense usage of punctuation and be concerete.

What exactly (example?) did you cut'n'paste? Can you get a backtrace?
See 
https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace

Regards,

Rene



Bug#807823: Patch to fix the issue

2015-12-18 Thread Joël Krähemann
Hi

I have just found the dead-lock. The issue should be fixed.

cheers,
Joël
Index: libinstpatch-1.0.0/libinstpatch/IpatchBase.c
===
--- libinstpatch-1.0.0.orig/libinstpatch/IpatchBase.c	2010-10-25 21:03:42.0 +0200
+++ libinstpatch-1.0.0/libinstpatch/IpatchBase.c	2015-12-18 10:01:02.384180605 +0100
@@ -231,7 +231,7 @@
   IPATCH_ITEM_RLOCK (base);
   file = base->file;
   if (file) g_object_ref (file);
-  IPATCH_ITEM_RLOCK (base);
+  IPATCH_ITEM_RUNLOCK (base);
 
   return (file);
 }


Bug#808275: kopete: Kopete crashes every time a message window is closed

2015-12-18 Thread Nicos Gollan
Package: kopete
Version: 4:15.08.3-1+b1
Severity: important

Dear Maintainer,

* What led up to the situation?
With kdelibs 4.14.14, Kopete is affected by upstream bug 355275
https://bugs.kde.org/show_bug.cgi?id=355275
effectively rendering it highly annoying to use since it has become
impossible to close message windows without crashing the entire
application. This affects versions from unstable and testing.

* What exactly did you do (or not do) that was effective (or
  ineffective)?
Tried to close a message window.

* What was the outcome of this action?
Kopete crashes.

* What outcome did you expect instead?
The message window should close without crashing the application.


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (950, 'testing'), (900, 'unstable'), (500, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kopete depends on:
ii  kde-runtime 4:15.08.3-1
ii  libc6   2.19-22
ii  libexpat1   2.1.0-7
ii  libgadu31:1.12.1-2
ii  libgif7 5.1.1-0.2
ii  libglib2.0-02.46.2-1
ii  libidn111.32-3
ii  libjasper1  1.900.1-debian1-2.4
ii  libkabc44:4.14.10-1
ii  libkcmutils44:4.14.14-1
ii  libkde3support4 4:4.14.14-1
ii  libkdecore5 4:4.14.14-1
ii  libkdeui5   4:4.14.14-1
ii  libkdnssd4  4:4.14.14-1
ii  libkemoticons4  4:4.14.14-1
ii  libkhtml5   4:4.14.14-1
ii  libkio5 4:4.14.14-1
ii  libkmime4   4:4.14.10-1
ii  libknewstuff2-4 4:4.14.14-1
ii  libknotifyconfig4   4:4.14.14-1
ii  libkopete4  4:15.08.3-1
ii  libkparts4  4:4.14.14-1
ii  libkpimidentities4  4:4.14.10-1
ii  libmeanwhile1   1.0.2-5
ii  libmediastreamer-base3  3.6.1-2.4+b4
ii  libmsn0.3v5 4.2.1+dfsg-1+b1
ii  libortp93.6.1-2.4+b4
ii  libotr5 4.1.0-2
ii  libphonon4  4:4.8.3-2
ii  libqca2 2.1.1-2
ii  libqimageblitz4 1:0.0.6-4
ii  libqt4-dbus 4:4.8.7+dfsg-5
ii  libqt4-network  4:4.8.7+dfsg-5
ii  libqt4-qt3support   4:4.8.7+dfsg-5
ii  libqt4-sql  4:4.8.7+dfsg-5
ii  libqt4-xml  4:4.8.7+dfsg-5
ii  libqtcore4  4:4.8.7+dfsg-5
ii  libqtgui4   4:4.8.7+dfsg-5
ii  libsolid4   4:4.14.14-1
ii  libsrtp01.4.5~20130609~dfsg-1.1
ii  libssl1.0.2 1.0.2d-3
ii  libstdc++6  5.2.1-23
ii  libv4l-01.8.0-1
ii  libx11-62:1.6.3-1
ii  libxml2 2.9.2+zdfsg1-4
ii  libxslt1.1  1.1.28-2.1
ii  perl5.20.2-6
ii  phonon  4:4.8.3-2
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages kopete recommends:
ii  kdepim-runtime   4:4.14.10-2
ii  libqca2-plugin-ossl  2.1.1-2
ii  libqt4-sql-sqlite4:4.8.7+dfsg-5

Versions of packages kopete suggests:
ii  imagemagick   8:6.8.9.9-6
pn  kdeartwork-emoticons  
ii  khelpcenter   4:5.4.3-1
ii  texlive-latex-base2015.20151116-1

-- no debconf information



Bug#767024: tracker.debian.org: Reports wrong new upstream for a native package

2015-12-18 Thread Lucas Nussbaum
Hi,

UDD has the correct info, as you can check with:
select * from upstream where source ='mini-buildd';

udd-dehs seems to use mole.watch, according to the code.

I would recommend switching to udd's upstream table, given it's also
used for DMD. So problems would be easier to notice.

Lucas


On 18/12/15 at 10:12 +0100, Raphael Hertzog wrote:
> Control: reassign -1 qa.debian.org
> Control: retitle -1 udd-dehs: Report wrong new upstream version for a native 
> package
> Control: user qa.debian@packages.debian.org
> Control: usertag -1 + udd
> Control: affects -1 tracker.debian.org
> 
> Hello Lucas,
> 
> is there any chance that you can fix the problem below? I don't know
> if you just need to drop old data or if you have to teach the tool to ignore
> old watch files...
> 
> On Sat, 06 Dec 2014, Bart Martens wrote:
> > The same problem is on https://packages.qa.debian.org/m/mini-buildd.html .
> > 
> > The output of https://qa.debian.org/cgi-bin/udd-dehs contains this:
> > 
> >   |  debian-mangled-uversion: 0.8.20
> >   |  debian-uversion: 0.8.20
> >   |  messages: Not downloading as --package was used.  Use --download to 
> > force downloading.
> >   |  package: mini-buildd
> >   |  status: Newer version available
> >   |  upstream-url: 
> > http://ftp.debian.org/debian/pool/main/m/mini-buildd/mini-buildd_1.0.0~alpha.8.tar.gz
> >   |  upstream-version: 1.0.0~alpha.8
> > 
> > And mini-buildd 1.0.5 does not contain a debian/watch file (which is good!).
> > 
> > Current versions of mini-buildd in Debian are:
> > 
> >   oldstable 0.8.15+nmu1 
> >   testing 1.0.5 
> >   unstable 1.0.5 
> > 
> > So the problem seems to be that UDD contains outdated information.
> 
> -- 
> Raphaël Hertzog ◈ Debian Developer
> 
> Support Debian LTS: http://www.freexian.com/services/debian-lts.html
> Learn to master Debian: http://debian-handbook.info/get/
> 



Bug#796345: [Debian-ha-maintainers] Bug#796345: redhat-cluster/libdlm + lvm + perl transition

2015-12-18 Thread Emilio Pozuelo Monfort
On 17/12/15 14:09, Ferenc Wagner wrote:
> Ferenc Wagner  writes:
> 
>> Emilio Pozuelo Monfort  writes:
>>
>>> On 16/12/15 00:12, Ferenc Wagner wrote:
>>>
 Niko Tyni  writes:

> So the proper way out seems to be a separate libdlm source package, as
> discussed in [1]. Ferenc, do I understand right that a new pacemaker
> package is a blocker for this? Is that because the current pacemaker
> would be broken by the libdlm update?

 No: the new DLM package depends on the new Pacemaker package.  I'm
 already testing them, there's only some cleanup remaining before they
 can be uploaded.  Both will go through NEW though, so it will take some
 time.
>>>
>>> I can speed things up if they block a transition... Got an eta for this?
>>
>> That sounds useful!  I expect to get pacemaker_1.1.13-1 ready for upload
>> today, taking some shortcuts.
> 
> Now the Perl transition is rolling and I can't build Pacemaker anymore,
> because some of its build dependencies are broken.  Is there still a
> reason to hurry the uploads?

Yes, it'd be good to get this fixed ASAP, so that we can rebuild or remove
redhat-cluster.

The perl rdeps should be installable again at some point today, hopefully.

Cheers,
Emilio



Bug#808239: perl-base: Also it uninstalls GNOME, but gnome requires. Please, upgrade package perl-base in repos

2015-12-18 Thread Nickolay Ilyushin
Package: perl-base
Version: 5.22.1-1
Followup-For: Bug #808239



-- System Information:
Debian Release: stretch/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.3.0-1-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages perl-base depends on:
ii  dpkg   1.18.3
ii  libc6  2.21-4

perl-base recommends no packages.

Versions of packages perl-base suggests:
ii  perl  5.22.1-1

-- no debconf information



Bug#801441: Upcoming stable point release (8.3)

2015-12-18 Thread Arto Jantunen
"Adam D. Barratt"  writes:

> On 2015-12-18 8:20, Arto Jantunen wrote:
>> "Adam D. Barratt"  writes:
>>
>>> Hi,
>>>
>>> The next point release for "jessie" (8.3) is scheduled for Saturday,
>>> January 23rd. Processing of new uploads into jessie-proposed-updates
>>> will be frozen during the preceding weekend.
>>
>> Has the deadline already been missed for reviewing #801441?
>
> The only deadline that exists is the one mentioned in the quote you
> included.

So I can expect a review (from you?) and possible ack before that
deadline?

-- 
Arto Jantunen



Bug#761909: systemd does not unmount nfs shares before bringing down the network interface

2015-12-18 Thread Martin Pitt
Control: forwarded -1 https://github.com/systemd/systemd/issues/2189

I now bisected this and understand what's going on. Further details
are in the upstream issue.

If this was really deliberate and we can't prevent instantiated units
from getting stopped during shutdown, then I propose as a fallback we
just drop the ExecStop=ifdown (or replace it with some "echo not
supported blabla, please use ifdown directly"). Michael, any
objections to that? This is just an internal helper unit for the udev
rule, after all.

Martin

-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)



Bug#808279: Patch for python-pil bug #808238

2015-12-18 Thread Eric Soroos

Package: tilestache
Version: 1.49.8-1
Severity: normal

This is a fix for bug #808238 from Python-pil

Tilestache uses PIL.Image.fromstring, which has been deprecated in 
Pillow since 2.0.0, and has now been removed in 3.0.0.


Patch follows:

diff --git a/TileStache/Mapnik.py b/TileStache/Mapnik.py
index 24120a8..64d74bf 100644
--- a/TileStache/Mapnik.py
+++ b/TileStache/Mapnik.py
@@ -128,7 +128,12 @@ class ImageProvider:
 # always release the lock
 global_mapnik_lock.release()

-img = Image.fromstring('RGBA', (width, height), img.tostring())
+if hasattr(Image, 'frombytes'):
+# Image.fromstring is deprecated past Pillow 2.0
+img = Image.frombytes('RGBA', (width, height), img.tostring())
+else:
+# PIL still uses Image.fromstring
+img = Image.fromstring('RGBA', (width, height), img.tostring()

 logging.debug('TileStache.Mapnik.ImageProvider.renderArea() 
%dx%d in %.3f from %s', width, height, time() - start_time, self.mapfile)


diff --git a/TileStache/Pixels.py b/TileStache/Pixels.py
index d17faa0..bfebbb0 100644
--- a/TileStache/Pixels.py
+++ b/TileStache/Pixels.py
@@ -100,7 +100,13 @@ def apply_palette(image, palette, t_index):

 indexes.append(mapping[(r, g, b)])

-output = Image.fromstring('P', image.size, ''.join(indexes))
+if hasattr(Image, 'frombytes'):
+# Image.fromstring is deprecated past Pillow 2.0
+output = Image.frombytes('P', image.size, ''.join(indexes))
+else:
+# PIL still uses Image.fromstring
+output = Image.fromstring('P', image.size, ''.join(indexes))
+
 bits = int(ceil(log(len(palette)) / log(2)))

 palette += [(0, 0, 0)] * (256 - len(palette))



Bug#808280: apcupsd: illogical log levels

2015-12-18 Thread Andreas
Package: apcupsd
Version: 3.14.10-2
Severity: normal
Tags: patch upstream

Dear Maintainer,

I noticed apcupsd logs more important messages with lower log level than less 
important ones.
e.g.
LOG_CRIT  "Power failure."
LOG_ALERT "Power is back. UPS running on mains."
Alert is higher than critical according to RFC 5424 p. 6.2.1.

I suggest this patch:

--- action.c.orig   2015-12-18 11:19:29.281371201 +0100
+++ action.c2015-12-18 11:20:54.453372964 +0100
@@ -61,17 +61,17 @@
  * and the defines in include/apc_defines.h 
  */
 UPSCMDMSG event_msg[] = {
-   {LOG_CRIT,"Power failure."},
+   {LOG_ALERT,   "Power failure."},
{LOG_CRIT,"Running on UPS batteries."},
{LOG_ALERT,   "Battery power exhausted."},
{LOG_ALERT,   "Reached run time limit on batteries."},
{LOG_ALERT,   "Battery charge below low limit."},
{LOG_ALERT,   "Reached remaining time percentage limit on batteries."},
{LOG_ALERT,   "Initiating system shutdown!"},
-   {LOG_ALERT,   "Power is back. UPS running on mains."},
-   {LOG_ALERT,   "Users requested to logoff."},
+   {LOG_CRIT,"Power is back. UPS running on mains."},
+   {LOG_CRIT,"Users requested to logoff."},
{LOG_ALERT,   "Battery failure. Emergency."},
-   {LOG_CRIT,"UPS battery must be replaced."},
+   {LOG_ALERT,   "UPS battery must be replaced."},
{LOG_CRIT,"Remote shutdown requested."},
{LOG_WARNING, "Communications with UPS lost."},
{LOG_WARNING, "Communications with UPS restored."},



-- System Information:
Debian Release: 7.9
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=hu_HU.UTF-8, LC_CTYPE=hu_HU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages apcupsd depends on:
ii  libc6 2.13-38+deb7u8
ii  libgcc1   1:4.7.2-5
ii  libwrap0  7.6.q-24

Versions of packages apcupsd recommends:
ii  apcupsd-doc  3.14.10-2

Versions of packages apcupsd suggests:
pn  apcupsd-cgi  
ii  udev 175-7.2

-- Configuration Files:
/etc/apcupsd/apcupsd.conf changed [not included]
/etc/apcupsd/killpower changed [not included]
/etc/default/apcupsd changed [not included]

-- no debconf information



Bug#808228: iceweasel disables unsigned addons installed via xul-ext packages

2015-12-18 Thread Martin Steigerwald
Am Donnerstag, 17. Dezember 2015, 19:57:20 CET schrieb Daniel Kahn Gillmor:
> On Thu 2015-12-17 18:44:26 -0500, Mike Hommey  wrote:
> > On Thu, Dec 17, 2015 at 06:29:35PM -0500, Daniel Kahn Gillmor wrote:
> >> On Thu 2015-12-17 07:53:43 -0500, Martin Steigerwald wrote:
> >> > xpinstall.signatures.required is set to true here.
> >> > 
> >> > I set to false for now in order to use the addons again. This works.
> >> 
> >> fwiw, i also needed to set xpinstall.whitelist.required to false to use
> >> the system-installed addons on iceweasel 43.0.
> > 
> > Can you both check what happens with a new profile? This might be an
> > issue on upgrade, but not on fresh install.
> 
> I can confirm that a with a new profile, the system-installed extensions
> are functional.  The problem i had was with an existing (upgraded)
> profile.

Indeed. They are all functional with a new test profile.

Thanks and a merry, joyful, relaxing holidays,
-- 
Martin



Bug#808281: tracker.debian.org: UpdateRepositoriesTask error

2015-12-18 Thread Christophe Siraut
Package: tracker.debian.org
Severity: normal
Tags: patch

Dear Maintainer,

Trying to build a Tracker database from scratch, using the repositories fixture
as descibed in the documentation, I get the following:

2015-12-18 08:54:11,265 INFO: Starting task UpdateRepositoriesTask
2015-12-18 08:54:11,265 INFO: UpdateRepositoriesTask Updating apt's 
cache
2015-12-18 08:54:15,313 INFO: UpdateRepositoriesTask Updating data from 
Sources files
None
2015-12-18 08:54:15,313 ERROR: Problem processing a task.
Traceback (most recent call last):
  File 
"/home/tobald/packages/distro-tracker/distro_tracker/core/tasks.py", line 518, 
in run
task.execute()
  File 
"/home/tobald/packages/distro-tracker/distro_tracker/core/tasks.py", line 548, 
in wrapper
six.reraise(*sys.exc_info())
  File 
"/home/tobald/packages/distro-tracker/distro_tracker/core/tasks.py", line 545, 
in wrapper
func(self)
  File 
"/home/tobald/packages/distro-tracker/distro_tracker/core/retrieve_data.py", 
line 818, in execute
self.update_sources_files(updated_sources)
  File 
"/home/tobald/packages/distro-tracker/distro_tracker/core/retrieve_data.py", 
line 584, in update_sources_files
repository.shorthand)
AttributeError: 'NoneType' object has no attribute 'shorthand'

The attached naïve patch fixes the issue here.

Cheers,
Christophe

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (600, 'experimental'), (500, 
'testing-updates')
Architecture: amd64 (x86_64)

Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
>From 898e7e20bbe33630e752b1a55ce72f57c6f32b80 Mon Sep 17 00:00:00 2001
From: Christophe Siraut 
Date: Fri, 18 Dec 2015 11:20:33 +0100
Subject: [PATCH] utils.AptCache: fix component_url

---
 distro_tracker/core/utils/packages.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/distro_tracker/core/utils/packages.py b/distro_tracker/core/utils/packages.py
index 12c28a1..5321dd6 100644
--- a/distro_tracker/core/utils/packages.py
+++ b/distro_tracker/core/utils/packages.py
@@ -318,7 +318,7 @@ class AptCache(object):
 for index_file in entry.index_files:
 if os.path.basename(sources_file) in index_file.describe:
 split_description = index_file.describe.split()
-component_url = split_description[0] + split_description[1]
+component_url = split_description[0] + '/' + split_description[1]
 break
 for repository in Repository.objects.all():
 if component_url in repository.component_urls:
-- 
2.6.4



Bug#807860: publican: Images not added to PDF, [ERROR] FOUserAgent - Image not found.

2015-12-18 Thread Raphael Hertzog
Control: forwarded -1 https://bugzilla.redhat.com/show_bug.cgi?id=1290423
Control: tags -1 + confirmed upstream

Hello,

On Sun, 13 Dec 2015, Petr Vanek wrote:
> This problem started ever since fop 2 came out several months ago so i
> am not sure where the problem is, perhaps publican needs different
> configuration for fop 2.x then previous fop 1.x.  Please note that i use
> slightly modified pdf template called pdf-custom, but standard pdf
> format produces same result, i just don't have any example document with
> it.

I can reproduce the problem, as do others.

However the fop backend is deprecated in Publican and does not get much
love. They recommend the use of wkhtmltopdf (which gets used by default
when available).

I did not add this package to Depends or Recommends before because
publican needed a patched version in the past. I think this is no longer
the case and I should probably replace the fop dependency with
wkhtmltopdf.

Can you try it out and let me know how well Debian's wkhtmltopdf works
with publican? (I don't use the PDF output at all, as I rely on dblatex
for the PDF output for my own books)

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/



Bug#808274: ieee-data: please fix #779543 in stable

2015-12-18 Thread Sandro Tosi
Package: ieee-data
Version: 20141019.1
Severity: important

Hello,
thanks for fixing #779543 in sid/testing, but this needs fixing in stable as
well. The next point release is scheduled for late January, can you please
prepare a s-p-u for this package addressing #779543 ?

Thanks!

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.0.0-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)



Bug#767024: tracker.debian.org: Reports wrong new upstream for a native package

2015-12-18 Thread Raphael Hertzog
Control: reassign -1 qa.debian.org
Control: retitle -1 udd-dehs: Report wrong new upstream version for a native 
package
Control: user qa.debian@packages.debian.org
Control: usertag -1 + udd
Control: affects -1 tracker.debian.org

Hello Lucas,

is there any chance that you can fix the problem below? I don't know
if you just need to drop old data or if you have to teach the tool to ignore
old watch files...

On Sat, 06 Dec 2014, Bart Martens wrote:
> The same problem is on https://packages.qa.debian.org/m/mini-buildd.html .
> 
> The output of https://qa.debian.org/cgi-bin/udd-dehs contains this:
> 
>   |  debian-mangled-uversion: 0.8.20
>   |  debian-uversion: 0.8.20
>   |  messages: Not downloading as --package was used.  Use --download to 
> force downloading.
>   |  package: mini-buildd
>   |  status: Newer version available
>   |  upstream-url: 
> http://ftp.debian.org/debian/pool/main/m/mini-buildd/mini-buildd_1.0.0~alpha.8.tar.gz
>   |  upstream-version: 1.0.0~alpha.8
> 
> And mini-buildd 1.0.5 does not contain a debian/watch file (which is good!).
> 
> Current versions of mini-buildd in Debian are:
> 
>   oldstable 0.8.15+nmu1 
>   testing 1.0.5 
>   unstable 1.0.5 
> 
> So the problem seems to be that UDD contains outdated information.

-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/



Bug#808276: marisa: typo in package description (conteins -> contains)

2015-12-18 Thread Ansgar Burchardt
Source: marisa
Version: 0.2.4-8+b3
Severity: minor

Hi,

there's a small typo in the package description for marisa: "conteins"
should be "contains".

Ansgar



Bug#808278: fglrx-driver: X fails to load, tty console repeatedly flashes

2015-12-18 Thread Peter Murdoch
Package: fglrx-driver
Version: 1:15.9-2 
Severity: normal
Tags: upstream

Dear Maintainer,

It seems that the latest fglrx-driver is producing the same symptom as
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739054, resulting in a
segfault and X does not start.

After exhibiting the symptom described in 739054, I ran apt-get purge fglrx*
and attempted to deploy the source package 15.30.1025 from amd's website, but
this did not yield success.  The logs in Xorg did change at this point and
stated that there was no module for fglrx even though it was present in lsmod.

There were some other issues from the amd installer I had to troubleshoot to
get that far, as apparently something was linking for 32bit libraries that
would prevent glxinfo/glxgears/aticonfig from executing.  Following some other
threads I purged i386 mesa and ran ldconfig to resolve, but was never able to
get Xorg log to indicate anything other than module fglrx not found.

Not sure what else I can do to help, My card is [Radeon R7 260X/360] per lspci.

I was able to bring X back with radeon driver from testing repo.



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages fglrx-driver depends on:
ii  debconf [debconf-2.0]1.5.58
pn  glx-alternative-fglrx
ii  libc62.21-4
pn  libfglrx 
ii  libgl1-mesa-glx [libgl1] 11.0.7-1
ii  libx11-6 2:1.6.3-1
ii  libxext6 2:1.3.3-1
ii  libxrandr2   2:1.5.0-1
ii  libxrender1  1:0.9.9-2
pn  xorg-video-abi-15 | xorg-video-abi-14 | xorg-video-abi-13 | xor  
ii  xserver-xorg-core2:1.17.3-2

Versions of packages fglrx-driver recommends:
pn  fglrx-atieventsd 
pn  fglrx-modules-dkms | fglrx-kernel-14.6-betav1.0  
pn  libgl1-fglrx-glx 
pn  libgl1-fglrx-glx-i386

Versions of packages fglrx-driver suggests:
ii  amd-opencl-icd  1:15.9-2
pn  fglrx-control   
pn  xvba-va-driver  



Bug#808273: CVE-2015-5313: storage: don't allow '/' in filesystem volume names

2015-12-18 Thread Guido Günther
Source: libvirt
Version: 1.3.0-1
Severity: important

Hi,

see

https://libvirt.org/git/?p=libvirt.git;a=commit;h=034e47c338b13a95cf02106a3af912c1c5f818d7

we have ACLs disabled by default so the default configuration is not
affected.
Cheers,
 -- Guido

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'unstable'), 
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)



Bug#808277: Fails with filenames which contain spaces

2015-12-18 Thread Gaudenz Steinlin
Package: ucf
Version: 3.0031
Severity: normal

UCF fails for files which contain spaces. See the test case below. It also 
fails if only the source 
or destination file contain spaces.

gaudenz@moebius:~/tmp/ucf-test$ tree
.
├── dest
├── lib
│   └── cache
└── source
└── file with space

4 directories, 1 file
gaudenz@moebius:~/tmp/ucf-test$ sudo ucf --debug=5 --state-dir ./lib 
source/file\ with\ space dest/file\ with\ space
The new start file is  `/home/gaudenz/tmp/ucf-test/source/file
/home/gaudenz/tmp/ucf-test/with
/home/gaudenz/tmp/ucf-test/space\'
The destination is `/home/gaudenz/tmp/ucf-test/dest/file
/home/gaudenz/tmp/ucf-test/with
/home/gaudenz/tmp/ucf-test/space\' 
(`\/home\/gaudenz\/tmp\/ucf\-test\/dest\/file\ 
\/home\/gaudenz\/tmp\/ucf\-test\/with\ \/home\/gaudenz\/tmp\/ucf\-test\/space\')
The history is kept under  \'/home/gaudenz/tmp/ucf-test/source/file\'
The file may be cached at \'./lib/cache/:home:gaudenz:tmp:ucf-test:dest:file 
:home:gaudenz:tmp:ucf-test:with :home:gaudenz:tmp:ucf-test:space\'
The destination file does not exist.
The old md5sum does not exist.
The new file does not exist.
Historical md5sums are not available
The new start file is  `/home/gaudenz/tmp/ucf-test/source/file
/home/gaudenz/tmp/ucf-test/with
/home/gaudenz/tmp/ucf-test/space\'
The destination is `/home/gaudenz/tmp/ucf-test/dest/file
/home/gaudenz/tmp/ucf-test/with
/home/gaudenz/tmp/ucf-test/space\' 
(`\/home\/gaudenz\/tmp\/ucf\-test\/dest\/file\ 
\/home\/gaudenz\/tmp\/ucf\-test\/with\ \/home\/gaudenz\/tmp\/ucf\-test\/space\')
The history is kept under  \'/home/gaudenz/tmp/ucf-test/source/file\'
The file may be cached at \'./lib/cache/:home:gaudenz:tmp:ucf-test:dest:file 
:home:gaudenz:tmp:ucf-test:with :home:gaudenz:tmp:ucf-test:space\'


-- System Information:
Debian Release: stretch/sid
  APT prefers testing-proposed-updates
  APT policy: (500, 'testing-proposed-updates'), (500, 'testing'), (100, 
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages ucf depends on:
ii  coreutils  8.23-4
ii  debconf1.5.58

ucf recommends no packages.

ucf suggests no packages.

-- debconf information:
* ucf/changeprompt_threeway: keep_current
  ucf/conflicts_found:
  ucf/title:
* ucf/changeprompt: keep_current
* ucf/show_diff:



Bug#801441: Upcoming stable point release (8.3)

2015-12-18 Thread Adam D. Barratt

On 2015-12-18 8:20, Arto Jantunen wrote:

"Adam D. Barratt"  writes:


Hi,

The next point release for "jessie" (8.3) is scheduled for Saturday,
January 23rd. Processing of new uploads into jessie-proposed-updates
will be frozen during the preceding weekend.


Has the deadline already been missed for reviewing #801441?


The only deadline that exists is the one mentioned in the quote you 
included.


Regards,

Adam



Bug#808259: RFS: abi-monitor/1.6-1 ITP

2015-12-18 Thread 陳昌倬
On Fri, Dec 18, 2015 at 08:46:52AM +0100, Peter Spiess-Knafl wrote:
> I modified it and re-uploaded the package to mentors.
> 
> Do you consider sponsoring it? As you might have seen in the ITP/RFS,
> I plan to bring the whole abi-tracker of Andrey to Debian.

Uploaded. Thanks for contributing Debian.

-- 
ChangZhuo Chen (陳昌倬) 
Debian Developer (https://nm.debian.org/public/person/czchen)
Key fingerprint = EC9F 905D 866D BE46 A896  C827 BE0C 9242 03F4 552D


signature.asc
Description: PGP signature


Bug#808003: [Reproducible-builds] Bug#808003: diffoscope: Comparing directories shouldn't care about file order

2015-12-18 Thread Jérémy Bobbio
Control: tag -1 + pending

Mike Hommey:
>* What led up to the situation?
> 
> Comparing two directories
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> 
> Ran `diffoscope --html output.html a b` where a and b are directories 
> containing
> more or less the same thing.
> 
>* What was the outcome of this action?
> 
> The output contained differences in the output for find due to
> filesystem-dependent behavior wrt file ordering in readdir(3).
> 
>* What outcome did you expect instead?
> 
> The sorted list should be compared instead.

I've just commited a fix. Thanks for the report.

-- 
Lunar.''`. 
lu...@debian.org: :Ⓐ  :  # apt-get install anarchism
`. `'` 
  `-   



Bug#734688: Logs are not rotated for a month

2015-12-18 Thread Michael Gebetsroither
Package: logrotate
Version: 3.8.7-1+b1
Followup-For: Bug #734688

Dear Maintainer,

Seconded, the problem still persists in jessie.
Logrotate was practically broken after /var/log got full a month ago.

There where various .log.1.gz files, most of which where 0 bytes which
stopped logrotate to act on those files completely.

# grep 'error creating output file' logrotate_force_20151216.log
error: error creating output file /var/log/dpkg.log.1.gz: File exists
error: error creating output file /var/log/alternatives.log.1.gz: File exists
error: error creating output file /var/log/nginx/error.log.1.gz: File exists
error: error creating output file /var/log/nginx/access.log.1.gz: File exists
error: error creating output file /var/log/php5-fpm.log.1.gz: File exists
error: error creating output file /var/log/syslog.1.gz: File exists
error: error creating output file /var/log/daemon.log.1.gz: File exists
error: error creating output file /var/log/auth.log.1.gz: File exists
error: error creating output file /var/log/messages.1.gz: File exists

# ls -lah daemon.log*
-rw-r- 1 root adm 3.1G Dec 16 19:07 daemon.log
-rw-r- 1 root adm 600K Sep 28 06:17 daemon.log.1
-rw-r- 1 root adm0 Oct  4 06:25 daemon.log.1.gz
-rw-r- 1 root adm  43K Sep 20 06:03 daemon.log.2.gz
-rw-r- 1 root adm 111K Sep 13 05:55 daemon.log.3.gz
-rw-r- 1 root adm  480 Sep  6 22:45 daemon.log.4.gz

# log from logrotate -f -v for daemon.log
rotating log /var/log/daemon.log, log->rotateCount is 4
dateext suffix '-20151216'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
compressing log with: /bin/gzip
error: error creating output file /var/log/daemon.log.1.gz: File exists
log /var/log/daemon.log.5.gz doesn't exist -- won't try to dispose of it

michael

-- System Information:
Debian Release: 8.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

-- no debconf information



Bug#808003: [Reproducible-builds] Bug#808003: Bug#808003: diffoscope: Comparing directories shouldn't care about file order

2015-12-18 Thread Holger Levsen
Hi,

FWIW, this commit message convinced me that I was wrong here initially :)

commit f12ad6df800d6728d43b09086c2cb07137c8245d
Author: Jérémy Bobbio 
Date:   Fri Dec 18 11:41:09 2015 +0100

Sort the file list in directory comparator

When we compare which files are in directories, we are not interested in
comparing the order in which the filesystem returns them as we have
no power over it.

Thanks Mike Hommey for reporting the issue.

Closes: #808003


thanks & cheers,
Holger


signature.asc
Description: This is a digitally signed message part.


Bug#808283: /usr/sbin/airmon-ng: Despues de seguir la recomendación de http://www.aircrack-ng.org/doku.php?id=airmon-ng}

2015-12-18 Thread helio
Package: aircrack-ng
Version: 1:1.2-0~rc2-0kali5
Severity: normal
File: /usr/sbin/airmon-ng

Dear Maintainer,


Al arrancar la aplicación
prueba de aplicación

#airmon-ng start 

Found 1 processes that could cause trouble.
If airodump-ng, aireplay-ng or airtun-ng stops working after
a short period of time, you may want to kill (some of) them!

  PID Name
 3317 wpa_supplicant

PHY Interface   Driver  Chipset

phy0eth1ipw2200 Intel Corporation PRO/Wireless 2200BG 
[Calexico2] (rev 05)
Failed to set eth1mon up using ip
command failed: No such device (-19)

(mac80211 monitor mode vif enabled for [phy0]eth1 on 
[phy0]eth1mon)
command failed: Operation not supported (-95)
(mac80211 station mode vif disabled for [phy0]eth1)

El programa se bloquea obligando a reinizializar la conexion de red.


-- System Information:
Distributor ID: Kali
Description:Kali GNU/Linux 2.0
Release:2.0
Codename:   sana
Architecture: i686

Kernel: Linux 4.0.0-kali1-686-pae (SMP w/1 CPU core)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages aircrack-ng depends on:
ii  ethtool   1:3.16-1
ii  iw3.17-1
ii  libc6 2.19-18
ii  libgcrypt20   1.6.3-2
ii  libnl-3-200   3.2.24-2
ii  libnl-genl-3-200  3.2.24-2
ii  libpcap0.81.6.2-2
ii  libpcre3  2:8.35-3.3
ii  libsqlite3-0  3.8.7.1-1+deb8u1
ii  wireless-tools30~pre9-8
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages aircrack-ng recommends:
ii  ieee-data  20150531.1

aircrack-ng suggests no packages.

-- no debconf information



Bug#808285: tracker.debian.org: Subscription keywords management is over-complex

2015-12-18 Thread Christophe Siraut
Package: tracker.debian.org
Severity: wishlist

Dear contributors,

Keywords management is currently done using extensive javascript and
ajax requests. As the rest of the application is using Django, we could
gain reliability and simplicity using Django forms. We should not
require javascript IMHO, better use it unobstrusively instead.

This would requires a few core/models simplifications, remove the
r'^api/' urls, and loose the fancy modal windows, what do you think?

Cheers,
Christophe



Bug#808284: libalien-wxwidgets-perl: Broken dependencies in binary package after BinNMU

2015-12-18 Thread Axel Beckert
Package: libalien-wxwidgets-perl
Version: 0.67+dfsg-2
Severity: serious

The following line shows the relevant differences in the dependencies of
the binary packages 0.67+dfsg-2 and 0.67+dfsg-2+b1:

0.67+dfsg-2:Depends: ..., libwxgtk3.0-dev (<< 3.0.3~), ..., 
libwxgtk-media3.0-dev (<< 3.0.3~), ...
0.67+dfsg-2+b1: Depends: ..., libwxgtk3.0-dev (<< 3.0.~),  ..., 
libwxgtk-media3.0-dev (<< 3.0.~),  ...

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (600, 'testing'), (500, 'buildd-unstable'), 
(400, 'stable'), (110, 'experimental'), (1, 'buildd-experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-trunk-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libalien-wxwidgets-perl depends on:
ii  clang-3.6 [c-compiler]  1:3.6.2-3
ii  gcc [c-compiler]4:5.3.1-1
ii  gcc-4.9 [c-compiler]4.9.3-10
ii  gcc-5 [c-compiler]  5.3.1-3
ii  libmodule-pluggable-perl5.2-1
ii  libwxgtk-media3.0-dev   3.0.2+dfsg-1.2
ii  libwxgtk3.0-dev 3.0.2+dfsg-1.2
ii  perl5.20.2-6
ii  perl-base [perlapi-5.20.2]  5.20.2-6
ii  tcc [c-compiler]0.9.27~git20140923.9d7fb33-3

libalien-wxwidgets-perl recommends no packages.

libalien-wxwidgets-perl suggests no packages.

-- no debconf information



Bug#808286: linux-image-4.3.0-1-amd64: IP assigned to interface in DOWN state is reachable.

2015-12-18 Thread Paweł Różański
Package: src:linux
Version: 4.3.3-1
Severity: normal

Dear Maintainer,

It looks like general problem with Linux kernel (tested on different versions 
with different
distributions - 2.x, 3.x, sometimes bug is present, sometimes not), but when I 
tested on
linux-image-4.2.0-1-amd64 4.2.6-3 (kernel from unstable) and was 
OK, and now on
linux-image-4.3.0-1-amd64 4.3.3-1 (current from unstable) bug 
returned.
This bug is also present in:
linux-image-3.16.0-4-amd64 3.16.7-ckt11-1+deb8u6 (Debian stable)

Steps to reproduce:
ip link add name eth0.3713 link eth0 type vlan id 3713
ip link set eth0.3713 up
ip a a 192.168.67.67/24 dev eth0.3713
fping 192.168.67.67
(is alive)
ip link set eth0.3713 down
fping 192.168.67.67
(is still alive!)

ip a output:
5: eth0.3713@eth0:  mtu 1500 qdisc noqueue state DOWN 
group default qlen 1000
link/ether 5c:f9:dd:40:d3:38 brd ff:ff:ff:ff:ff:ff
inet 192.168.67.67/24 scope global eth0.3713
   valid_lft forever preferred_lft forever

I expect interface in DOWN state to be inactive (in any way), so IP assigned to 
this interface
should not be reachable.

Doesn't matter if iface is physical (eth1) or vlan-interface. But some people 
reported different results.

This check was made on Jessie with kernel from unstable, but also is present on 
full stable (with stable kernel,
as mentioned before).

Regards,
Paweł

-- Package-specific info:
** Version:
Linux version 4.3.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.3.1 
20151207 (Debian 5.3.1-3) ) #1 SMP Debian 4.3.3-1 (2015-12-15)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.3.0-1-amd64 
root=UUID=8e32ea56-95cb-4eb0-9099-8a59ed3f1ce2 ro quiet

** Not tainted

** Kernel log:
[2.085956] [drm] Driver supports precise vblank timestamp query.
[2.086055] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[2.107573] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[2.107723] input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input11
[2.107906] [drm] Initialized i915 1.6.0 20150731 for :00:02.0 on minor 0
[2.122710] iTCO_vendor_support: vendor-support=0
[2.124667] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[2.124720] iTCO_wdt: Found a Panther Point TCO device (Version=2, 
TCOBASE=0x0460)
[2.124934] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[2.141794] fbcon: inteldrmfb (fb0) is primary device
[2.146651] cfg80211: World regulatory domain updated:
[2.146653] cfg80211:  DFS Master region: unset
[2.146653] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp), (dfs_cac_time)
[2.146656] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 
mBm), (N/A)
[2.146658] cfg80211:   (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 
mBm), (N/A)
[2.146659] cfg80211:   (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 
mBm), (N/A)
[2.146661] cfg80211:   (517 KHz - 525 KHz @ 8 KHz, 16 KHz 
AUTO), (N/A, 2000 mBm), (N/A)
[2.146663] cfg80211:   (525 KHz - 533 KHz @ 8 KHz, 16 KHz 
AUTO), (N/A, 2000 mBm), (0 s)
[2.146664] cfg80211:   (549 KHz - 573 KHz @ 16 KHz), (N/A, 2000 
mBm), (0 s)
[2.14] cfg80211:   (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 
mBm), (N/A)
[2.146667] cfg80211:   (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 0 
mBm), (N/A)
[2.240075] intel_rapl: Found RAPL domain package
[2.240076] intel_rapl: Found RAPL domain core
[2.240078] intel_rapl: Found RAPL domain uncore
[2.243522] ath9k :01:00.0 wlan1: renamed from wlan0
[2.246140] input: Dell WMI hotkeys as /devices/virtual/input/input12
[2.255815] systemd-udevd[260]: renamed network interface wlan0 to wlan1
[2.503769] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
[2.503807] [drm:cpt_irq_handler [i915]] *ERROR* PCH transcoder A FIFO 
underrun
[2.652201] clocksource: Switched to clocksource tsc
[2.925724] input: AlpsPS/2 ALPS GlidePoint as 
/devices/platform/i8042/serio1/input/input7
[2.968486] usbcore: registered new interface driver rtsx_usb
[3.043187] Console: switching to colour frame buffer device 170x48
[3.078304] i915 :00:02.0: fb0: inteldrmfb frame buffer device
[3.324768] Process accounting resumed
[3.385281] random: nonblocking pool is initialized
[3.417447] zram: Added device: zram0
[3.418846] zram: Added device: zram1
[3.421456] zram: Added device: zram2
[3.422368] zram0: detected capacity change from 0 to 1048576000
[3.423040] zram1: detected capacity change from 0 to 1048576000
[3.423736] zram2: detected capacity change from 0 to 1048576000
[3.951352] Adding 1023996k swap on /dev/zram0.  Priority:60 extents:1 
across:1023996k SSFS
[3.968390] Adding 1023996k swap on 

Bug#761909: systemd does not unmount nfs shares before bringing down the network interface

2015-12-18 Thread Martin Pitt
Control: reopen -1
Control: found -1 228-2

This bug is back in 228-2, ifup@.service now again gets stopped during
shutdown.

Apparently 228 (or perhaps 227) changed behaviour so that
ifup@.service always gets stopped, even if they have
DefaultDependencies=no and thus no Conflicts=shutdown.target. I tried
to remove all dependencies from ifup@.service and then it gets stopped
as pretty much the last thing, but it still gets stopped. This will
again break root partition on NFS or iSCSI or similar setups.

Martin
-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)


signature.asc
Description: Digital signature


Bug#808288: ITP: profitbricks-sdk-python -- ProfitBricks REST API client library for Python

2015-12-18 Thread Benjamin Drung
Package: wnpp
Severity: wishlist
Owner: Benjamin Drung 

* Package name: profitbricks-sdk-python
  Version : 2.2
  Upstream Author : Matt Baldwin 
* URL : https://github.com/profitbricks/profitbricks-sdk-python
* License : Apache-2.0
  Programming Lang: Python 2 & 3
  Description : ProfitBricks REST API client library for Python

The ProfitBricks client library for Python provides you with access to the
ProfitBricks representational state transfer (REST) application programming
interface (API). The client library supports both simple and complex requests.
It is designed for developers who are building applications in Python.

The source package will provide the two binary packages python-profitbricks
and python3-profitbricks. I'll probably put the package under collab-maint.

-- 
Benjamin Drung
System Developer
Debian & Ubuntu Developer

ProfitBricks GmbH
Greifswalder Str. 207
D - 10405 Berlin

Email: benjamin.dr...@profitbricks.com
URL:  http://www.profitbricks.com

Sitz der Gesellschaft: Berlin.
Registergericht: Amtsgericht Charlottenburg, HRB 125506B.
Geschäftsführer: Andreas Gauger, Achim Weiss.



Bug#778240: tracker.debian.org has much worse display clarity

2015-12-18 Thread Ian Jackson
Raphael Hertzog writes ("Re: Bug#778240: tracker.debian.org has much worse 
display clarity"):
> However the spacing is unlikely to evolve significantly... many people
> enjoy its "lighter" aspect too.

Thanks for your reply.  I'm sorry to argue, but:

I don't know which these "many people" are.  This bug report seems
mostly to contain comments from people who preferred the old style.

For me the "lighter" aspect is not a question of "liking" or
"disliking".  It makes the page significantly less useable.

Perhaps some kind of semiformal survey would be in order ?  I'd be
happy to help organise that.  Or we could mail debian-devel and ask
people to comment here on this bug report.

Ian.



Bug#808289: proposed RM: upstart -- RoQA; unmaintained

2015-12-18 Thread Ansgar Burchardt
Source: upstart
Source-Version: 1.11-5

The upstart package seems both unmaintained in Debian[1] and upstream.
It also has open RC bugs and was removed from stretch five months ago.
I therefore suggest to remove the package.

If there are no objections, I'll reassign this bug report to ftp.d.o in
a week or so.

Ansgar

  [1] The current version in Debian is 1.11 which was released in 2013.
      There have been 5 upstream releases since then, the last in 2014.



Bug#808291: pxz ignores -Ccrc32; cannot build kernel ramdisks

2015-12-18 Thread Holger Levsen
control: severity -1 normal
control: tags -1 + upstream

Hi Trent,

thanks for your bug report.

On Freitag, 18. Dezember 2015, Trent W. Buck wrote:
> pxz accepts the equivalent option, but ignores it:
[...]
> Please make pxz honor -Ccrc32,
> or at least stop accepting it (exit non-zero instead).

I agree and am sure upstream would appreciate a patch as well. Could you maybe  
provide one?


cheers,
Holger




signature.asc
Description: This is a digitally signed message part.


Bug#770087: ITP: corebird -- Native Gtk+ Twitter client for the Linux desktop

2015-12-18 Thread Philip Rinn
Hi,

to give people the chance to build corebird themselves I prepared a package and
uploaded it to mentors:

http://mentors.debian.net/package/corebird

From my point of view this could be uploaded right away - Adnan, could you 
please
comment if you plan to make an upload soon or if you are willing to hand over 
this
ITP. You last comment on this ITP was over seven month ago.

Best,
Philip



signature.asc
Description: OpenPGP digital signature


Bug#808293: freeradius stopped working after kernel upgrade

2015-12-18 Thread Francesco Politi
Package: freeradius
Version: 2.1.12+dfsg-1.2
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

I just upgraded libc and kernel image:
# tail /var/log/apt/history.log

Start-Date: 2015-12-18  09:22:57
Commandline: apt-get upgrade -y
Upgrade: linux-libc-dev:i386 (3.2.68-1+deb7u6, 3.2.73-2+deb7u1), 
linux-image-3.2.0-4-686-pae:i386 (3.2.68-1+deb7u6, 3.2.73-2+deb7u1)
End-Date: 2015-12-18  09:23:15

Start-Date: 2015-12-18  10:30:59
Commandline: apt-get install strace
Install: strace:i386 (4.5.20-2.3)
End-Date: 2015-12-18  10:31:04

After reboot, I noticed that freeradius stopped processing requests.
This is freeradius -X output:
# freeradius -X
FreeRADIUS Version 2.1.12, for host i486-pc-linux-gnu, built on Dec 16 2012 at 
22:03:33
Copyright (C) 1999-2009 The FreeRADIUS server project and contributors.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
You may redistribute copies of FreeRADIUS under the terms of the
GNU General Public License v2.
Starting - reading configuration files ...
including configuration file /etc/freeradius/radiusd.conf
including configuration file /etc/freeradius/proxy.conf
including configuration file /etc/freeradius/clients.conf
including files in directory /etc/freeradius/modules/
including configuration file /etc/freeradius/modules/preprocess
including configuration file /etc/freeradius/modules/redis
including configuration file /etc/freeradius/modules/ippool
including configuration file /etc/freeradius/modules/expiration
including configuration file /etc/freeradius/modules/detail.log
including configuration file /etc/freeradius/modules/expr
including configuration file /etc/freeradius/modules/digest
including configuration file /etc/freeradius/modules/files
including configuration file /etc/freeradius/modules/attr_filter
including configuration file /etc/freeradius/modules/linelog
including configuration file /etc/freeradius/modules/echo
including configuration file /etc/freeradius/modules/detail.example.com
including configuration file /etc/freeradius/modules/chap
including configuration file /etc/freeradius/modules/soh
including configuration file /etc/freeradius/modules/passwd
including configuration file /etc/freeradius/modules/rediswho
including configuration file /etc/freeradius/modules/dynamic_clients
including configuration file /etc/freeradius/modules/checkval
including configuration file /etc/freeradius/modules/mschap
including configuration file /etc/freeradius/modules/acct_unique
including configuration file /etc/freeradius/modules/perl
including configuration file /etc/freeradius/modules/detail
including configuration file /etc/freeradius/modules/attr_rewrite
including configuration file /etc/freeradius/modules/sql_log
including configuration file /etc/freeradius/modules/replicate
including configuration file /etc/freeradius/modules/smbpasswd
including configuration file /etc/freeradius/modules/mac2ip
including configuration file /etc/freeradius/modules/etc_group
including configuration file /etc/freeradius/modules/pam
including configuration file /etc/freeradius/modules/mac2vlan
including configuration file /etc/freeradius/modules/unix
including configuration file /etc/freeradius/modules/policy
including configuration file /etc/freeradius/modules/always
including configuration file /etc/freeradius/modules/exec
including configuration file /etc/freeradius/modules/pap
including configuration file /etc/freeradius/modules/opendirectory
including configuration file /etc/freeradius/modules/counter
including configuration file /etc/freeradius/modules/ldap
including configuration file /etc/freeradius/modules/ntlm_auth
including configuration file /etc/freeradius/modules/realm
including configuration file /etc/freeradius/modules/smsotp
including configuration file /etc/freeradius/modules/cui
including configuration file /etc/freeradius/modules/radutmp
including configuration file /etc/freeradius/modules/krb5
including configuration file /etc/freeradius/modules/wimax
including configuration file /etc/freeradius/modules/inner-eap
including configuration file /etc/freeradius/modules/otp
including configuration file /etc/freeradius/modules/logintime
including configuration file /etc/freeradius/modules/sradutmp
including configuration file /etc/freeradius/modules/sqlcounter_expire_on_login
including configuration file /etc/freeradius/eap.conf
including configuration file /etc/freeradius/sql.conf
including configuration file /etc/freeradius/sql/mysql/dialup.conf
including configuration file /etc/freeradius/policy.conf
including files in directory /etc/freeradius/sites-enabled/
including configuration file /etc/freeradius/sites-enabled/default
main {
user = "freerad"
group = "freerad"
allow_core_dumps = no
}
including dictionary file /etc/freeradius/dictionary
main {
name = "freeradius"
prefix = "/usr"
localstatedir = "/var"
sbindir = "/usr/sbin"

Bug#808291: pxz ignores -Ccrc32; cannot build kernel ramdisks

2015-12-18 Thread Trent W. Buck
Holger Levsen wrote:
> On Freitag, 18. Dezember 2015, Trent W. Buck wrote:
> > pxz accepts the equivalent option, but ignores it:
> [...]
> > Please make pxz honor -Ccrc32,
> > or at least stop accepting it (exit non-zero instead).
>
> I agree and am sure upstream would appreciate a patch as well.
> Could you maybe provide one?

Thanks for the quick reply.



I glanced at the source, but my C skills are weak.
I probably can't provide a patch.

Also I found that even though pixz has no -C/--check option, it works by 
default!
So my immediate needs are met, though I'd prefer pxz because it's smaller and 
simpler.



"Just don't honor -C" part should be a simple matter of commenting out
that part of the getopts block, as pxz already does for filter options:

diff --git a/pxz.c b/pxz.c
index 23f819a..496be75 100644
--- a/pxz.c
+++ b/pxz.c
@@ -103,7 +103,7 @@ const struct option long_opts[] = {
 // { "files0", optional_argument, NULL,  OPT_FILES0 },
// Basic compression settings
{ "format", required_argument, NULL,  'F' },
-   { "check",  required_argument, NULL,  'C' },
{ "memory", required_argument, NULL,  'M' },
{ "threads",required_argument, NULL,  'T' },
{ "context-size",   required_argument, NULL,  'D' },

I suppose fixing it properly involves adding a 'C' case to parse_args(),
and fiddling with lzma_options after lzma_lzma_preset in main().

While we're at it, you/I/upstream should check that the rest of
long_opts[] array matches the dispatch in parse_args :-)

PS: I tested pxz on jessie, but not sid.
I suppose it's possible a commit since pxz/jessie has fixed this already.



Bug#808287: Application: konsole (konsole), signal: Segmentation fault

2015-12-18 Thread lukash
Package: libc6
Version: 2.21-4
Severity: normal

Dear Maintainer,

DEV Info:
Application: konsole (konsole), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x7f2d55a391b3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7f2d55a2f5dd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#8  0x7f2d55a2fc79 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#9  0x7f2d55a242ed in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#10 0x7f2d55a24399 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#11 0x7f2d55368f52 in __run_exit_handlers (status=0, listp=0x7f2d556d1698
<__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82
#12 0x7f2d55368fa5 in __GI_exit (status=) at exit.c:104
#13 0x7f2d55353877 in __libc_start_main (main=0x400710 , argc=1,
argv=0x7fff22f82d48, init=, fini=,
rtld_fini=, stack_end=0x7fff22f82d38) at libc-start.c:325
#14 0x00400749 in _start ()


gdb output:
GNU gdb (Debian 7.10-1) 7.10
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/konsole...(no debugging symbols found)...done.
Attaching to program: /usr/bin/konsole, process 3941
Reading symbols from /usr/lib/x86_64-linux-gnu/libkdeinit5_konsole.so...(no
debugging symbols found)...done.
Reading symbols from /lib/x86_64-linux-gnu/libc.so.6...Reading symbols from
/usr/lib/debug/.build-
id/72/277f734c48f21879d7b256859ec8f9225a1da6.debug...done.
done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libkonsoleprivate.so.15...(no
debugging symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libKF5NotifyConfig.so.5...(no
debugging symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libKF5KDELibs4Support.so.5...(no
debugging symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5...(no
debugging symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5...(no
debugging symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libKF5WindowSystem.so.5...(no
debugging symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libKF5Completion.so.5...(no
debugging symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libKF5IconThemes.so.5...(no
debugging symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libKF5ConfigWidgets.so.5...(no
debugging symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libKF5I18n.so.5...(no debugging
symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libKF5ConfigGui.so.5...(no
debugging symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libKF5ConfigCore.so.5...(no
debugging symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libKF5WidgetsAddons.so.5...(no
debugging symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5...(no
debugging symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5...(no
debugging symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5...(no debugging
symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5...(no debugging
symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libstdc++.so.6...(no debugging
symbols found)...done.
Reading symbols from /lib64/ld-linux-x86-64.so.2...Reading symbols from
/usr/lib/debug/.build-
id/eb/de43e93a1e82174c392efa8ea37d6522fa054b.debug...done.
done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libKF5Notifications.so.5...(no
debugging symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libKF5Bookmarks.so.5...(no
debugging symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libKF5Pty.so.5...(no debugging
symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libQt5PrintSupport.so.5...(no
debugging symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libKF5TextWidgets.so.5...(no
debugging symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libKF5GuiAddons.so.5...(no
debugging symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5...(no
debugging symbols 

Bug#808290: sbuild: sbuild-update gives "Can't locate object method "throw"" when passing an unknown chroot name

2015-12-18 Thread Ansgar Burchardt
Package: sbuild
Version: 0.66.0-5
Severity: minor

sbuild-update throws an unfriendly error message when called with an
unknown chroot:

  # sbuild-update -ugd unknown
  Can't locate object method "throw" via package "Sbuild::Exception::Build" 
(perhaps you forgot to load "Sbuild::Exception::Build"?) at 
/usr/share/perl5/Sbuild/ChrootInfo.pm line 140.

Ansgar

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (300, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages sbuild depends on:
ii  adduser 3.113+nmu3
ii  apt-utils   1.1.4
ii  libsbuild-perl  0.66.0-5
ii  perl5.20.2-6

Versions of packages sbuild recommends:
ii  debootstrap  1.0.75
pn  fakeroot 

Versions of packages sbuild suggests:
pn  deborphan  
ii  wget   1.17-1

-- no debconf information



Bug#808291: pxz ignores -Ccrc32; cannot build kernel ramdisks

2015-12-18 Thread Trent W. Buck
Package: pxz
Version: 4.999.99~beta3+git659fc9b-3
Severity: minor

I build Debian Live images.  A lot.
Waiting for update-initramfs is boring.
I want to speed it up using pxz or pixz (not xz).

The kernel's XZ decompressor does not support CRC64, xz's default.
When using COMPRESS=xz, mkinitramfs (initramfs-tools) passes --check=crc32 to 
fix this.
(Reference: https://www.kernel.org/doc/Documentation/xz.txt)

pxz accepts the equivalent option, but ignores it:

(bootstrap)root@zygon:/boot# xzcat initrd.img | datefudge 2000-01-01 pxz 
-0Ccrc32   -T1 >a
(bootstrap)root@zygon:/boot# xzcat initrd.img | datefudge 2000-01-01 pxz 
-0Ccrc64   -T1 >b
(bootstrap)root@zygon:/boot# xzcat initrd.img | datefudge 2000-01-01 pxz 
-0Cwaffles -T1 >c
(bootstrap)root@zygon:/boot# sha1sum a b c
8df3800e37881acd3b4c79e76f793dc290a69958  a
8df3800e37881acd3b4c79e76f793dc290a69958  b
8df3800e37881acd3b4c79e76f793dc290a69958  c

If the option was working, the checksums would be different (I think).

The kernel becomes sad:

(bootstrap)root@zygon:/boot# qemu-system-x86_64 -nographic -kernel vmlinuz 
-initrd initrd.img -append console=ttyS0
[...works...]

(bootstrap)root@zygon:/boot# qemu-system-x86_64 -nographic -kernel vmlinuz 
-initrd a -append console=ttyS0
[...]
[0.653683] Initramfs unpacking failed: Input was encoded with settings 
that are not supported by this XZ decoder
[...]

Please make pxz honor -Ccrc32,
or at least stop accepting it (exit non-zero instead).



Bug#808292: fvwm: Replace fvwm-menu-desktop with upstream version (they rewrite from Perl to Python XDG library).

2015-12-18 Thread Oleksandr Gavenko
Package: fvwm
Version: 1:2.6.5.ds-4
Severity: normal

I build menu by my own scripts:

  http://hg.defun.work/skel/file/tip/.fvwm/xdg2fvwm.py

because package included `fvwm-menu-desktop' have problems (see my post and
followups):

  http://thread.gmane.org/gmane.comp.window-managers.fvwm.general/8341

Upstream developers say that `fvwm-menu-desktop' was rewritten in Python and
resolve my problem (with icons).

I check upstream version and confirm that newer version satisfy my needs.

There are also issues this package provided man page.

So I strongly recommend to include upstream version of `fvwm-menu-desktop'.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (200, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

-- 
Best regards!



Bug#808174: jemalloc FTCBFS for {hur,kfreebs}d-i386 m68k sparc{,64}: mistakes build architecture for host architecture

2015-12-18 Thread Stig Sandbeck Mathisen
Helmut Grohne  writes:

> The intention behind all of these checks is to match the architecture
> that is being built for, which is called host architecture and not
> build architecture.

So the builder architecture is is DEB_HOST_, and while the target host
architecture is is DEB_BUILD_, or the other way around?  I obviously got
them mixed around in my head. :)

> The fix is simple:
>
> sed -i s/DEB_BUILD_/DEB_HOST_/g debian/rules

Thanks.  Upload coming soon.

-- 
Stig Sandbeck Mathisen 



Bug#808295: general: sound and locale dependency

2015-12-18 Thread lukash
Package: general
Severity: important

Dear Maintainer,

realy funny bug

KDE5
there is no sound in system when Region settings->Formats->Region: en_US setted
but when other for example tt_RU everything is OK :)



-- System Information:
Debian Release: stretch/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.2.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=tt_RU.UTF-8, LC_CTYPE=tt_RU.UTF-8 (charmap=locale: Cannot set 
LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)



Bug#808294: libtext-iconv-perl: Should not depend on perlapi-5.20.0 on amd64

2015-12-18 Thread José de Paula Rodrigues N . Assis

Package: libtext-iconv-perl
Version: 1.7-5+b2
Severity: important

Dear Maintainer,

When doing my daily dist-upgrade, I stumbled upon this uninstallable
package, because perlapi-5.20.0 doesn't exist anymore on Deban Sid; it
is provided by perl-base. I believe that if the explicit dependence is
removed, the package will be installed fine. It is important because
without it, I cannot install several important KDE apps further up on
the dependency chain.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.3atena (SMP w/2 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libtext-iconv-perl depends on:
ii  libc6   2.21-4
ii  perl-base   5.22.1-1
pn  perlapi-5.18.1  

libtext-iconv-perl recommends no packages.

libtext-iconv-perl suggests no packages.



Bug#796798: perl: FTBFS on kfreebsd-*: t/op/stat.t failure

2015-12-18 Thread Niko Tyni
On Thu, Dec 17, 2015 at 02:41:30AM +, Steven Chamberlain wrote:

> The problem is with mtime.  It seems to be not calculated immediately,
> but deferred until the next stat, after the hard link is created, such
> that mtime=ctime and so the test fails.  A stat() right before the
> sleep, or a much longer sleep (~30s), causes mtime to be calculated
> earlier and so fixes it.
> 
> It's obviously a kernel behaviour, its unclear if it's a bug (it may be
> an expected quirk of softupdates), and in any case definitely not a Perl
> bug.  Might we please add a stat() to work around it, as attached;  that
> would allow the test to still run, and still return a meaningful result
> rather than skipping/ignoring the test on kfreebsd.

Thanks. I've modified this to only call the added stat() on kfreebsd and
applied it. Will upload soon so kfreebsd-* can join the binNMU party.

It would be nice if you could follow up when you know if this is a
permanent thing that should go upstream or just a temporary workaround.
-- 
Niko Tyni   nt...@debian.org
>From 78c55bc50e62a3371bdf14eb02882d833738a165 Mon Sep 17 00:00:00 2001
From: Steven Chamberlain 
Date: Thu, 17 Dec 2015 02:15:58 +
Subject: Work around Debian Bug#796798

kFreeBSD 10 (possibly only with softupdates enabled) may defer
calculating the mtime for more than 2 seconds.  Work around this
with a stat() call to calculate the mtime immediately.

(Modified to only stat() on kfreebsd by Niko Tyni)

Bug-Debian: https://bugs.debian.org/796798
Patch-Name: debian/kfreebsd-softupdates.diff
---
 t/op/stat.t | 1 +
 1 file changed, 1 insertion(+)

diff --git a/t/op/stat.t b/t/op/stat.t
index ad94b3f..469f8ba 100644
--- a/t/op/stat.t
+++ b/t/op/stat.t
@@ -96,6 +96,7 @@ sleep 3 if $funky_FAT_timestamps;
 print FOO "Now is the time for all good men to come to.\n";
 close(FOO);
 
+stat($tmpfile) if $^O =~ /^gnukfreebsd/;	# Work around Debian Bug#796798
 sleep 2;
 
 my $has_link = 1;


Bug#802552: [pkg-cinnamon] Bug#802552: cinnamon: battery status is not updated

2015-12-18 Thread Fabio Fantoni
Control: tag -1 + pending

Il 21/10/2015 01:19, Norbert Preining ha scritto:
> Package: cinnamon
> Version: 2.6.13-1
> Severity: important
>
> Dear all
>
> it seems that at some point the cinnamon power applet stopped working.
> Well, it works, but it does *NOT* update the power status.
>
> I just realized that my power button was blinking crazily at me,
> while the power applet showed me a full battery ... plugging in the
> power cord and whms, the battery applet showed an exhausted
> battery being charged.
>
> So it seems that some notifications are getting lost, or the screen
> not updated.
>
> Thanks a lot
>
> Norbert
>

I'm unable to reproduce it with cinnamon 2.8.6, and in upstream
same/similar bug seems solved in 2.8:
https://github.com/linuxmint/Cinnamon/issues/4735
I'll mark this solved in 2.8.




smime.p7s
Description: Firma crittografica S/MIME


Bug#808151: systemd: failed to start remount root and kernel file system

2015-12-18 Thread Frank B. Brokken
Dear Michael Biebl, you wrote:

> Well, /usr is mounted by the initramfs these days. So it should already
> be available when systemd is started. If that fails, this is a bug which
> needs to be addressed by initramfs-tools (or one of the hook scripts).
> It wasn't clear so far that /usr hasn't been mounted at all.
> 
> Is /usr on LVM, RAID, etc?

No, nothing like that. And for what it's worth: the problem only appeared
after I upgraded systemd last week. The laptop has nothing special in its
setup, and has been working perfectly for years, until last week when systemd
was renwed. I think in my bugreport I mentioned the problem that /usr wasn't
mounted.

In your next reply you wrote:

> I'm a bit confused by those logs. They show that sda5 have been mounted.
> 
> Dec 17 15:44:29 localhost.localdomain kernel: EXT4-fs (sda5): mounting
> ext3 file system using the ext4 subsystem
> Dec 17 15:44:29 localhost.localdomain kernel: EXT4-fs (sda5): mounted
> filesystem with ordered data mode. Opts: (null)
> 
> I figure /dev/sda5 is your /usr partition? Just to be sure, please
> attach ls -la /dev/disk/by-uuid/

I seem to remember that message, in particular the Opts: (null) remark, and I
think at that point /usr was mounted by me fron the systemd shell. Also,
couldn't it be that initramfs *did* do the mount, but that remounting it rw,
als reported in the error message is the problem? Also, to me it appears
remarkable that by removing the 'quiet' from the kernel parameters, so that
things go a bit slower because of the extra messages that are displayed the
frequency of failing boot procedures is greatly diminished. I'm considering
trying to add 'verbose' to grub's parameters to see if that produces more
output and maybe further reduces the frequency, but I haven't had the time to
do that yet. Something on the TODO list :-)

Anyway, here's the ls -la output:

total 0
drwxr-xr-x 2 root root 200 Dec 18 13:05 ./
drwxr-xr-x 5 root root 100 Dec 18 13:02 ../
lrwxrwxrwx 1 root root  10 Dec 18 13:02 04b82e8b-f871-4abb-978a-44ae44c5d1f7
-> ../../sda1
lrwxrwxrwx 1 root root  10 Dec 18 13:02 595bcdbf-6436-45a7-99d2-297a3dd85930
-> ../../sda6
lrwxrwxrwx 1 root root  10 Dec 18 13:02 693c71eb-d411-4ee0-a1b3-c577df02e01b
-> ../../sda9
lrwxrwxrwx 1 root root  10 Dec 18 13:02 6bcb2a05-33c9-402b-8093-e6a35ffd7aa1
-> ../../sda8
lrwxrwxrwx 1 root root  11 Dec 18 13:05 82e52787-6072-4af9-a5e6-2d88c365e62b
-> ../../loop0
lrwxrwxrwx 1 root root  10 Dec 18 13:02 c5591eff-0a6c-4310-bb11-7d5535f7da7b
-> ../../sda7
lrwxrwxrwx 1 root root  10 Dec 18 13:05 e289e4ad-be1d-42a8-9b38-f4dad9473520
-> ../../dm-0
lrwxrwxrwx 1 root root  10 Dec 18 13:02 ea8202e7-4564-424c-af70-a6a640fafb65
-> ../../sda5
~

I'll do the 'debug' addition later this weekend, like you requested.

Finally, you asked:

> Do you have any custom udev rules in /etc/udev/rules.d?

I don't think so, looking at the time stamps nothing has been changed there for 
years:

total 10
drwxr-xr-x 2 root root 3072 Dec  6  2014 ./
drwxr-xr-x 4 root root 1024 Dec  3 08:34 ../
-rw-r--r-- 1 root root  115 Dec  6  2014 70-automount.rules
-rw-r--r-- 1 root root 3841 Dec  6  2014 70-persistent-cd.rules
-rw-r--r-- 1 root root  895 Feb 26  2013 70-persistent-net.rules

And I definitely didn't recently change there any files, so again: the problem
appeared out of the blue since last weeks upgrade. 

I hope the above gives you at least some additional info. As I wrote: I'll do
the 'debug' addition tomorrow.

Cheers,

-- 
Frank B. Brokken
Center for Information Technology, University of Groningen
(+31) 50 363 9281 
Public PGP key: http://pgp.surfnet.nl
Key Fingerprint: DF32 13DE B156 7732 E65E  3B4D 7DB2 A8BE EAE4 D8AA



Bug#808296: tor: Latest version doesn't start

2015-12-18 Thread Michael Meskes
Package: tor
Version: 0.2.7.6-1
Severity: normal

On a fresh unstable installation tor refuses to do anything. The situation
seems to be different from #802521, hence a new bug report. If it turns out to
be the same bug, feel free to merge.

Dez 18 13:16:08 feivel tor[1349]: Dec 18 13:16:08.001 [notice] Read 
configuration file "/usr/share/tor/tor-service-defaults-torrc".
Dez 18 13:16:08 feivel systemd[1356]: tor@default.service: Failed at step 
APPARMOR spawning /usr/bin/tor: No such file or directory
Dez 18 13:16:08 feivel systemd[1]: tor@default.service: Main process exited, 
code=exited, status=231/APPARMOR
Dez 18 13:16:08 feivel systemd[1]: tor@default.service: Unit entered failed 
state.
Dez 18 13:16:08 feivel systemd[1]: tor@default.service: Failed with result 
'exit-code'.
Dez 18 13:16:08 feivel systemd[1]: tor@default.service: Service hold-off time 
over, scheduling restart.

Manually downgrading to 0.2.5.12-1 solved the problem for now.

Michael
-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-rc4-next-20151211-1.g34634ae-vanilla (SMP w/4 CPU cores; 
PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages tor depends on:
ii  adduser 3.113+nmu3
ii  libc6   2.21-4
ii  libevent-2.0-5  2.0.21-stable-2+b1
ii  libseccomp2 2.2.3-2
ii  libssl1.0.0 1.0.2d-1
ii  lsb-base9.20150917
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages tor recommends:
ii  logrotate3.8.7-2
ii  tor-geoipdb  0.2.5.12-1
ii  torsocks 2.1.0-1

Versions of packages tor suggests:
pn  apparmor-utils 
pn  mixmaster  
pn  obfsproxy  
pn  polipo | privoxy   
pn  socat  
pn  tor-arm
pn  xul-ext-torbutton  

-- no debconf information



Bug#808279: Patch for python-pil bug #808238

2015-12-18 Thread Sebastiaan Couwenberg
Control: tags -1 pending

Hi Eric,

Thanks for the patch, it will be included in the next tilestache upload
to unstable and I've also forwarded it upstream.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1



Bug#808297: update gawk to version 4.1.3

2015-12-18 Thread Matthias Klose

Package: src:gawk
Version: 1:4.1.1+dfsg-1
Severity: minor
Tags: sid stretch
X-Debbugs-CC: Jeroen Schot 

Please update gawk to version 4.1.3.  I already emailed the package maintainers 
in private, but didn't get any reply. Will now prepare an update as a NMU and 
upload that to the delayed queue.




Bug#808266: linux-image-3.2.0-4-686-pae: i386 Wheezy JFS broken in 3.2.73-2+deb7u1 security update

2015-12-18 Thread Robert Henney
On Fri, Dec 18, 2015 at 04:20:49AM +, Ben Hutchings wrote:
> Control: tag -1 moreinfo
> 
> On Thu, 2015-12-17 at 19:20 -0500, Robert Henney wrote:
> > Package: src:linux
> > Version: 3.2.73-2+deb7u1
> > Severity: important
> > 
> > Today's kernel security update appears to have broken JFS support on i386, 
> > though JFS
> > still appears to be working on x86_64.
> [...]
> 
> I don't think so.  Have you rebooted the i386 system yet?
> 
> Ben.

When I said i386 earlier, I probably mean 686.

I rebooted following each of the re-installs of the linux-image-3.2.0-4-686-pae 
package,
switching between versions 3.2.68-1+deb7u3 and 3.2.73-2+deb7u1 of it.  Changing 
nothing
else, the jfs module loads and jfs partitions mount at boot with the earlier 
package
version, and with the latest package the jfs module fails to load and dmesg 
contains
those errors I mentioned.  Reproducable every time here, as I've switched the 
package 
between versions several times (rebooting after each) to confirm.



Bug#808129: Additional information

2015-12-18 Thread Damien Martins

Hi,

Now I can confirm that samba issue is raised when a client is trying to 
use shared printer.


--
Regards,
Damien Martins



Bug#801441: Upcoming stable point release (8.3)

2015-12-18 Thread Adam D. Barratt

On 2015-12-18 9:45, Arto Jantunen wrote:

"Adam D. Barratt"  writes:


On 2015-12-18 8:20, Arto Jantunen wrote:

"Adam D. Barratt"  writes:


Hi,

The next point release for "jessie" (8.3) is scheduled for Saturday,
January 23rd. Processing of new uploads into jessie-proposed-updates
will be frozen during the preceding weekend.


Has the deadline already been missed for reviewing #801441?


The only deadline that exists is the one mentioned in the quote you
included.


So I can expect a review (from you?) and possible ack before that
deadline?


That would be the hope, yes.

(In practice, there's a small number of people reviewing or otherwise 
handling updates, and a not-so-small number and size of updates to 
review.)


Regards,

Adam



Bug#808266: linux-image-3.2.0-4-686-pae: i386 Wheezy JFS broken in 3.2.73-2+deb7u1 security update

2015-12-18 Thread Ben Hutchings
On Fri, 2015-12-18 at 07:46 -0500, Robert Henney wrote:
> On Fri, Dec 18, 2015 at 04:20:49AM +, Ben Hutchings wrote:
> > Control: tag -1 moreinfo
> > 
> > On Thu, 2015-12-17 at 19:20 -0500, Robert Henney wrote:
> > > Package: src:linux
> > > Version: 3.2.73-2+deb7u1
> > > Severity: important
> > > 
> > > Today's kernel security update appears to have broken JFS support on 
> > > i386, though JFS
> > > still appears to be working on x86_64.
> > [...]
> > 
> > I don't think so.  Have you rebooted the i386 system yet?
> > 
> > Ben.
> 
> When I said i386 earlier, I probably mean 686.
> 
> I rebooted following each of the re-installs of the 
> linux-image-3.2.0-4-686-pae package,
> switching between versions 3.2.68-1+deb7u3 and 3.2.73-2+deb7u1 of it.  
> Changing nothing
> else, the jfs module loads and jfs partitions mount at boot with the earlier 
> package
> version, and with the latest package the jfs module fails to load and dmesg 
> contains
> those errors I mentioned.  Reproducable every time here, as I've switched the 
> package 
> between versions several times (rebooting after each) to confirm.

Which boot loader are you using?  Your report doesn't list any:

Versions of packages linux-image-3.2.0-4-686-pae suggests:
pn  debian-kernel-handbook 
pn  grub-pc | extlinux | lilo  
ii  linux-doc-3.2  3.2.73-2+deb7u1

Ben.

-- 
Ben Hutchings
Kids!  Bringing about Armageddon can be dangerous.  Do not attempt it in
your own home. - Terry Pratchett and Neil Gaiman, `Good Omens'

signature.asc
Description: This is a digitally signed message part


Bug#802552: [pkg-cinnamon] Bug#802552: cinnamon: battery status is not updated

2015-12-18 Thread Norbert Preining
> I'm unable to reproduce it with cinnamon 2.8.6, and in upstream
> same/similar bug seems solved in 2.8:
> https://github.com/linuxmint/Cinnamon/issues/4735
> I'll mark this solved in 2.8.

Good to see. Thanks. Any timeline about cinnamon 2.8 in unstable?

Norbert


PREINING, Norbert   http://www.preining.info
JAIST, Japan TeX Live & Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13




Bug#808151: systemd: failed to start remount root and kernel file system

2015-12-18 Thread Michael Biebl
Am 18.12.2015 um 13:34 schrieb Frank B. Brokken:
>> I'm a bit confused by those logs. They show that sda5 have been mounted.
>>
>> Dec 17 15:44:29 localhost.localdomain kernel: EXT4-fs (sda5): mounting
>> ext3 file system using the ext4 subsystem
>> Dec 17 15:44:29 localhost.localdomain kernel: EXT4-fs (sda5): mounted
>> filesystem with ordered data mode. Opts: (null)
> 
> I seem to remember that message, in particular the Opts: (null) remark, and I
> think at that point /usr was mounted by me fron the systemd shell. Also,
> couldn't it be that initramfs *did* do the mount, but that remounting it rw,
> als reported in the error message is the problem? Also, to me it appears

The verbose debug log from the initramfs and systemd can maybe tell us
more. But looking at https://www.icce.rug.nl/systemd/journalctl, the
sda5 mount happens at line 773, the first errors start at line 785 and
the remount is at line 802.
So it looks like /usr is not mounted at the time
systemd-remount-fs.service is run.

What's also curious is, that the log doesn't seem to be complete.
Usually systemd's first log line is something like

> Dez 18 07:03:47 pluto systemd[1]: systemd 228 running in system mode. (+PAM 
> +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT 
> +GNUTLS +ACL +X
> Dez 18 07:03:47 pluto systemd[1]: Detected architecture x86-64.

Those early boot messages seem to be missing completely.


Btw, you mentioned that this happened after an upgrade. Which previous
version did you run which worked fine? Which other packages were
upgraded along with it?
If you downgrade systemd/udev, does the problem go away?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



Bug#778240: tracker.debian.org has much worse display clarity

2015-12-18 Thread Raphael Hertzog
On Fri, 18 Dec 2015, Ian Jackson wrote:
> Raphael Hertzog writes ("Re: Bug#778240: tracker.debian.org has much worse 
> display clarity"):
> > However the spacing is unlikely to evolve significantly... many people
> > enjoy its "lighter" aspect too.
> 
> Thanks for your reply.  I'm sorry to argue, but:
> 
> I don't know which these "many people" are.  This bug report seems
> mostly to contain comments from people who preferred the old style.

Sure, the congratulations do not come through bug reports but I got
positive comments by email and on IRC...

That said I'm not opposed to try to do something more dense but the layout
is handled via bootstrap and reducing the spacing in a consistent manner
probably requires to rebuild bootstrap with different settings in terms
of spacing.

Or maybe we should not rebuild bootstrap but just have very specific CSS
for the package page which needs more density as it has lots of contents
to show.

In any case, this is not the kind of work that motivates me a lot and I
would love if someone who is really unhappy about it could give it a
try and make propositions. :-)

Right now, the main thing to try to tweak is probably everything that is
related to "list-group" and "list-group-item" as the content of all panels
on that page use those classes.

> Perhaps some kind of semiformal survey would be in order ?  I'd be
> happy to help organise that.  Or we could mail debian-devel and ask
> people to comment here on this bug report.

I would certainly welcome feedback once we have alternatives to show off.
Right now it's rather useless (unless you manage to find volunteers to
tweak the CSS while doing that).

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/



Bug#808310: libchemistry-formula-perl: bogus dependency on perlapi-5.20.2

2015-12-18 Thread gregor herrmann
Package: libchemistry-formula-perl
Version: 3.0.1-1.1
Severity: serious
Justification: interfers with perl transition

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi Carlo!

libchemistry-formula-perl is an arch:all package and still has
perlapi-5.20.2 in Depends. Therefor it shows up on the perl 5.22
transition tracker and causes grief.

The reason is probably that it installs
libchemistry-formula-perl: 
/usr/lib/x86_64-linux-gnu/perl5/5.20/auto/Chemistry/Formula/.packlist
which shouldn't happen. Ah yes, here's the error in debian/rules:

rm -rf $(TMP)/usr/lib/perl5/auto
[ ! -d $(TMP)/usr/lib/perl5 ] || rmdir --parents --ignore-fail-on-non-empty 
--verbose $(TMP)/usr/lib/perl5

Since perl is multiarched, this should be $Config{vendorarch}.

I'm going to NMU this now, hope this is ok.
What do you think about moving the package to pkg-perl?


Cheers,
gregor

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJWdB9VXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoG7XYP/1Sa4wTvc+a2O9R/QbaPEypE
Navz5b01xcMcDqGSrL8GxnkNiJt9WcyZnopRxSRqkJNHTJ2Xezz463ZmfiqOzMyl
s0//66/iQQrUWqmAdJsEY16ecGlUP+zQ81ZbqIFvecNQJA09/+OBCa0c1mIseAOv
dyKaKmnrPDhtmkqac5uW2O9LoftK3MADQzwbS97D3AjRf879RLfNQhck23qfn7Hk
UHW+feWzUmUXJb/VlC0FwBJUhLtk7wtfFQnR9sUTgnG9IY2Z8ed5/G0xsGmvnIZ+
EAwDyEm134LdBrlR9CBJIpQTX4zJPfufFtA1uWxz7QQINAuLMeNLLs8NxT2LNHxU
Se1KiLGxL/igHWZVqsThZGwfhwWufr3dWJINJpziFRUXuLQPob9jh9bWiVVay/Fc
JGDJ9JJ4nAgRKq3Kv1UgQa16yYbpirwZ5K1aipHH72iv1m1yrTj24pb1lXcJ08hN
1sGZ1TVTT6wp5PojBreCrS5HaTJtMIIEo0uFeSGViN1jNYk+jfmRNhHt2ByZjDNr
GPWlOQZiO+cG7WmtdOvLpvMzSieyT2wfet6MSBdMm0mGPxR3SpddnrYGka6+mscj
g+272SbmDgWZ+uGESf6swFve31+ZIMBGrIjRIAkQVcb80Ol8558N4gjspXR8wDJP
Xi5P3qReveXecZYihe1D
=06N1
-END PGP SIGNATURE-



Bug#808151: systemd: failed to start remount root and kernel file system

2015-12-18 Thread Frank B. Brokken
Dear Michael Biebl, you wrote:

> The verbose debug log from the initramfs and systemd can maybe tell us
> more. But looking at https://www.icce.rug.nl/systemd/journalctl, the
> sda5 mount happens at line 773, the first errors start at line 785 and
> the remount is at line 802.
> So it looks like /usr is not mounted at the time
> systemd-remount-fs.service is run.

Right. That's consistent with the impression I got from the error messages.
*Why* that is true, however, eludes me.

> 
> What's also curious is, that the log doesn't seem to be complete.
> Usually systemd's first log line is something like
> 
> > Dez 18 07:03:47 pluto systemd[1]: systemd 228 running in system mode. (+PAM 
> > +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
> > +GCRYPT +GNUTLS +ACL +X
> > Dez 18 07:03:47 pluto systemd[1]: Detected architecture x86-64.
> 
> Those early boot messages seem to be missing completely.

Well, I didn't edit anything. The information I generated is passed to you the
way it was made available by the various programs/commands.


> Btw, you mentioned that this happened after an upgrade. Which previous
> version did you run which worked fine? Which other packages were
> upgraded along with it?

Is there a way to determine that? What I do to upgrade the system is run
'aptitude update' and then 'aptitude upgrade'. Is there a log somewhere that
tells me what packages and versions were updated at what moments in time?


> If you downgrade systemd/udev, does the problem go away?

I thought about doing that, but was afraid for an avalanche of forced
downgrades of packages that might now depend on the most recent udev and
systemd versions. But I'll give it a try asap and let you know the results.

-- 
Frank B. Brokken
Center for Information Technology, University of Groningen
(+31) 50 363 9281 
Public PGP key: http://pgp.surfnet.nl
Key Fingerprint: DF32 13DE B156 7732 E65E  3B4D 7DB2 A8BE EAE4 D8AA



Bug#808298: fonts-roboto: messed up package relations, and a typo

2015-12-18 Thread Norbert Preining
Package: fonts-roboto
Version: 2:0~20151012-1
Severity: important

Dear all,

something is not quite right with the roboto fonts:

Package: fonts-roboto
Version: 2:0~20151012-1
Depends: fonts-roboto-hinted
Recommends: fonts-roboto-unhinted

Package: fonts-roboto-hinted
Version: 2:0~20151012-1
Conflicts: fonts-roboto-unhinted

Package: fonts-roboto-unhinted
Version: 2:0~20151012-1
Conflicts: fonts-roboto-hinted

>From the descriptions and the recommends/depends of fonts-roboto, it
seems that the hinted/unhinted are complementary sets, but they have
conflicts, which is strange.

Furthermore, the description of fonts-roboto-unhinted has a typo:
This package contain*s* Roboto font families ...


Thanks

Norbert

-- Package-specific info:
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  fontconfig 2.11.0-6.3   amd64generic font configuration librar
ii  libfreetype6:a 2.6.1-0.1amd64FreeType 2 font engine, shared li
ii  libfreetype6:i 2.6.1-0.1i386 FreeType 2 font engine, shared li
ii  libxft2:amd64  2.3.2-1  amd64FreeType-based font drawing libra

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-rc5 (SMP w/4 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 fonts-roboto depends on:
ii  dpkg  1.18.3

fonts-roboto recommends no packages.

fonts-roboto suggests no packages.

-- no debconf information



Bug#808303: mc: filtered view does not work

2015-12-18 Thread Stanislav Vlasov
Package: mc
Version: 3:4.8.13-3
Severity: normal

Dear Maintainer,

I'm run mc, choose file, type esc-! and enter command like `cat
filename | grep some`.
Filtered view show me error box "Cannot create pipe streams", which is
not expected.
This is upstream bug and was patched in 4.8.15:

---cut---
--- lib/utilunix.c.orig 2015-04-12 03:04:27 UTC
+++ lib/utilunix.c
@@ -528,7 +528,7 @@ mc_popen (const char *command, GError **
 goto ret_err;
 }

-if (!g_spawn_async_with_pipes (NULL, argv, NULL,
G_SPAWN_DO_NOT_REAP_CHILD, NULL, NULL,
+if (!g_spawn_async_with_pipes (NULL, argv, NULL,
G_SPAWN_DO_NOT_REAP_CHILD | G_SPAWN_SEARCH_PATH, NULL, NULL,
>child_pid, NULL, >out.fd,
>err.fd, error))
 {
 mc_replace_error (error, MC_PIPE_ERROR_CREATE_PIPE_STREAM, "%s",
---cut---

Please fix it in stable.

-- System Information:
Debian Release: 8.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages mc depends on:
ii  e2fslibs  1.42.12-1.1
ii  libc6 2.19-18+deb8u1
ii  libglib2.0-0  2.42.1-1
ii  libgpm2   1.20.4-6.1+b2
ii  libslang2 2.3.0-2
ii  libssh2-1 1.4.3-4.1
ii  mc-data   3:4.8.13-3

Versions of packages mc recommends:
ii  mime-support  3.58
ii  perl  5.20.2-3+deb8u1
ii  unzip 6.0-16+deb8u2

Versions of packages mc suggests:
ii  arj  3.10.22-13
ii  bzip21.0.6-7+b3
pn  catdvi | texlive-binaries
pn  dbview   
ii  djvulibre-bin3.5.25.4-4+b1
ii  evince-gtk [pdf-viewer]  3.14.1-2
ii  file 1:5.22+15-2
ii  genisoimage  9:1.1.11-3
ii  graphicsmagick-imagemagick-compat [imagemagick]  1.3.20-3+deb8u1
pn  gv   
ii  lynx 2.8.9dev1-2+deb8u1
ii  mupdf [pdf-viewer]   1.5-1+b2
ii  odt2txt  0.4+git20140608-1
ii  poppler-utils0.26.5-2
ii  python   2.7.9-1
ii  python-boto  2.34.0-2
pn  python-tz
ii  w3m  0.5.3-19
ii  zip  3.0-8

-- no debconf information


-- 
Stanislav



Bug#778240: tracker.debian.org has much worse display clarity

2015-12-18 Thread Ian Jackson
Raphael Hertzog writes ("Re: Bug#778240: tracker.debian.org has much worse 
display clarity"):
> I would certainly welcome feedback once we have alternatives to show off.

If you'd welcom contributions, I can certainly try to help this way.

> That said I'm not opposed to try to do something more dense but the layout
> is handled via bootstrap and reducing the spacing in a consistent manner
> probably requires to rebuild bootstrap with different settings in terms
> of spacing.

I have to confess that I have no idea what `bootstrap' is.

I'm not scared of unfamiliar code but it would probably save me a lot
of effort if you could sketch out for me how I would go about getting
the source code for bootstrap and trying out a modified version of
either that or with of
  https://anonscm.debian.org/cgit/qa/distro-tracker.git.

Is the bootstrap you are referring to `libjs-twitter-bootstrap' ?

Ian.



Bug#808199: [Reproducible-builds] Bug#808199: diffoscope: Weird line numbering in diff output

2015-12-18 Thread Jérémy Bobbio
Control: tag -1 + pending

Mike Hommey:
> Attached here is two files that can be compared directly, exposing the
> same problem. That's essentially the output of tar --full-time -tvf on
> both tarballs from the original bug report.
> 
> The following patch fixes the numbering issue:
> […]

Commited, thanks. The bug was around since the very first version of
the current HTML presenter code!

> However, there's another issue, that the diff is actually incomplete:
> the right hand side stops 3 lines too early.

I've fixed this as well.  The 'lines skipped' message was not written
when we were skipping lines at the end of the diff.

-- 
Lunar.''`. 
lu...@debian.org: :Ⓐ  :  # apt-get install anarchism
`. `'` 
  `-   


signature.asc
Description: Digital signature


Bug#759725: [Pkg-postgresql-public] #759725: postgresql-common: non-synchronous service postgresql stop

2015-12-18 Thread Christoph Berg
Control: retitle -1 postgresql-common: non-synchronous service postgresql stop

Hi,

an update here: unfortunately it seems rather involved to have an
umbrella service such as postgresql.service wait both for sub-service
start and stop. Achieving one or the other is rather easy, we can just
put "Before=postgresql.service" into postgresql@.service (sync start,
this is what we have now), or "After=..." (sync stop), but not both.

It might be possible to hack stop (or start) to wait for the
sub-services to finish, but all solutions Martin and I could think of
at the moment are rather ugly.

We'd really like to get this fixed, but at the moment it looks like
synchronous start will have to do for now...

Christoph
-- 
c...@df7cb.de | http://www.df7cb.de/



Bug#808312: chemps2: fails to upgrade from 'testing' - trying to overwrite /usr/share/man/man1/chemps2.1.gz

2015-12-18 Thread Andreas Beckmann
Package: chemps2
Version: 1.6-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', 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 unpack .../chemps2_1.6-2_amd64.deb ...
  Unpacking chemps2 (1.6-2) over (1.6-1+b1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/chemps2_1.6-2_amd64.deb (--unpack):
   trying to overwrite '/usr/share/man/man1/chemps2.1.gz', which is also in 
package libchemps2-1 1.6-1+b1
  Preparing to unpack .../libchemps2-1_1.6-2_amd64.deb ...
  Unpacking libchemps2-1 (1.6-2) over (1.6-1+b1) ...
  Processing triggers for libc-bin (2.21-4) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/chemps2_1.6-2_amd64.deb


cheers,

Andreas


chemps2_1.6-2.log.gz
Description: application/gzip


Bug#808287: Application: konsole (konsole), signal: Segmentation fault

2015-12-18 Thread Aurelien Jarno
control: reassign -1 qtbase-opensource-src
control: tag -1 + upstream
control: tag -1 + patch

On 2015-12-18 14:02, lukash wrote:
> Package: libc6
> Version: 2.21-4
> Severity: normal
> 
> Dear Maintainer,
> 
> DEV Info:
> Application: konsole (konsole), signal: Segmentation fault
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> [KCrash Handler]
> #6  0x7f2d55a391b3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
> #7  0x7f2d55a2f5dd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
> #8  0x7f2d55a2fc79 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
> #9  0x7f2d55a242ed in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
> #10 0x7f2d55a24399 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
> #11 0x7f2d55368f52 in __run_exit_handlers (status=0, listp=0x7f2d556d1698
> <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82
> #12 0x7f2d55368fa5 in __GI_exit (status=) at exit.c:104
> #13 0x7f2d55353877 in __libc_start_main (main=0x400710 , argc=1,
> argv=0x7fff22f82d48, init=, fini=,
> rtld_fini=, stack_end=0x7fff22f82d38) at libc-start.c:325
> #14 0x00400749 in _start ()

This is not related to the libc, the crash happens in the libQT5DBus
library. This bug is in qtbase-opensource-src and is fixed by the
following upstream commit:

https://github.com/qtproject/qtbase/commit/041fae00351164fbd72763e4bd947fdeb9956a5d

I am therefore reassigning the bug.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net



Bug#808266: linux-image-3.2.0-4-686-pae: i386 Wheezy JFS broken in 3.2.73-2+deb7u1 security update

2015-12-18 Thread Robert Henney
On Fri, Dec 18, 2015 at 01:34:28PM +, Ben Hutchings wrote:

> 
> Well it doesn't seem to be doing the right thing any more.  The error
> messages you got indicate that the old kernel is being used with new
> modules, i.e. the boot loader is not loading the upgraded kernel.
> Please check the grub configuration.

The grub configuration looks alright, and basically untouched from 
defaults.  But what you said about looking as if old modules were
being loaded got me thinking, so I recreated the initramfs image..

  update-initramfs -d -k 3.2.0-4-686-pae
  update-initramfs -c -k 3.2.0-4-686-pae

and now jfs is working.  So that means that the new kernel build 
isn't the problem as I had believed.

Not sure why the normal package upgrade process wasn't creating/updating 
the initramfs image properly, but it could certainly be grub-legacy
at fault, if it isn't due to something unique about this particular 
system's configuration (it's been dist-upgraded many times, starting
as etch or sarge).

This bug report can be closed.  If I find time to do some more 
investigation later and determine grub-legacy to be the actual culprit 
I'll file a bug report against that package.



Bug#800151: freeradius: Freeradius refuses to start with old libssl

2015-12-18 Thread Herwin Weststrate
This has been fixed in the version in Jessie (2.2.5+dfsg-0.2, see
#765871). Building a new backport would fix this problem.

Another option is to edit radiusd.conf, in the section security, add the
following line:

  allow_vulnerable_openssl = yes

You can limit this to a list with just the known vulnerabilities, but I
don't really see the point in doing that at a Debian system.

-- 
Herwin Weststrate



Bug#808314: developers-reference: maintainer scripts: /usr is always there

2015-12-18 Thread Ansgar Burchardt
Source: developers-reference
Severity: normal

Section 6.4 "Nest practices for maintainer script" has a pathfind()
function which it suggests copy & pasting into maintainer scripts.  It
suggests "which" as an alternative that requires /usr.

I think "best practices" and "copy and paste this function" are
contradictionary.  Given that /usr is *always* available when
maintainer scripts are run, using `which` should be just fine.

Ansgar



Bug#788160: elinks: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

2015-12-18 Thread Andreas Beckmann
Followup-For: Bug #788160
Control: found -1 0.12~pre6-11

>  elinks (0.12~pre6-11) unstable; urgency=medium
> .
>* Add maint script for dir_to_symlink (Closes: #788160)

You probably wanted it the other way around: symlink_to_dir
Don't forget to bump the version in elinks.maintscript.


Andreas


elinks_0.12~pre6-11.log.gz
Description: application/gzip


Bug#808318: icedove: pop server will only be polled after restart

2015-12-18 Thread Charles
Package: icedove
Version: 38.4.0-1~deb8u1
Severity: normal

Dear Maintainer,

I've configured a pop-account, the polling of which I need to turn on/off on a 
day by day
basis (depending on where I am). For this I change the 2 fields in the Server 
Settings dialog:
Check for new messages every ... minutes
Automatically download new messages

The problem is: After I've enabled polling, icedove does not fetch mails
unless I restart it.

I observed this behaviour before in an older version of thunderbird, so
it may be an upstream issue.


-- System Information:
Debian Release: 8.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages icedove depends on:
ii  debianutils   4.4+b1
ii  fontconfig2.11.0-6.3
ii  libasound21.0.28-1
ii  libatk1.0-0   2.14.0-1
ii  libc6 2.19-18+deb8u1
ii  libcairo2 1.14.0-2.1
ii  libdbus-1-3   1.8.20-0+deb8u1
ii  libdbus-glib-1-2  0.102-1
ii  libevent-2.0-52.0.21-stable-2
ii  libffi6   3.1-2+b2
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.5.2-3+deb8u1
ii  libgcc1   1:4.9.2-10
ii  libgdk-pixbuf2.0-02.31.1-2+deb8u4
ii  libglib2.0-0  2.42.1-1
ii  libgtk2.0-0   2.24.25-3
ii  libhunspell-1.3-0 1.3.3-3
ii  libpango-1.0-01.36.8-3
ii  libpangocairo-1.0-0   1.36.8-3
ii  libpangoft2-1.0-0 1.36.8-3
ii  libpixman-1-0 0.32.6-3
ii  libsqlite3-0  3.8.7.1-1+deb8u1
ii  libstartup-notification0  0.12-4
ii  libstdc++64.9.2-10
ii  libx11-6  2:1.6.2-3
ii  libxcomposite11:0.4.4-1
ii  libxdamage1   1:1.1.4-2+b1
ii  libxext6  2:1.3.3-1
ii  libxfixes31:5.0.1-2+b2
ii  libxrender1   1:0.9.8-1+b1
ii  libxt61:1.1.4-1+b1
ii  psmisc22.21-2
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages icedove recommends:
ii  hunspell-de-at [hunspell-dictionary]  20131206-5
ii  hunspell-de-ch [hunspell-dictionary]  20131206-5
ii  hunspell-de-de [hunspell-dictionary]  20131206-5
ii  hunspell-en-us [hunspell-dictionary]  20070829-6
ii  iceowl-extension  38.4.0-1~deb8u1

Versions of packages icedove suggests:
pn  fonts-lyx 
ii  libgssapi-krb5-2  1.12.1+dfsg-19+deb8u1

-- no debconf information



Bug#807651: nmu: systemd_228-2

2015-12-18 Thread Andreas Beckmann
(resending so that this makes it to -release, the bug was already
reassigned+retitled)

>> Am 11.12.2015 um 11:21 schrieb Andreas Beckmann:
>>> 0m44.8s ERROR: FAIL: Package purging left files on system:
>>>   /etc/init/udev.overridenot owned
> 
> On 2015-12-11 11:47, Michael Biebl wrote:
>> From a cursory glance, that seems to be duplicate of
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806276
> 
> Let me try to rebuild udev with a recent debhelper ...
> this does no longer create that file upon removal.
> 
> So, let's binNMU it:

nmu systemd_228-2 . ANY . unstable . -m "Rebuild with debhelper 9.20151126"


Andreas



Bug#808308: ca-certificates-mono: unowned files after purge (policy 6.8, 10.8): /usr/share/.mono/certs/Trust/*.cer (and the whole /usr/share/.mono tree)

2015-12-18 Thread Andreas Beckmann
Package: ca-certificates-mono
Version: 4.2.1.102+dfsg2-5
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package left unowned files on
the system after purge, which is a violation of policy 6.8 (or 10.8):

https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails

Filing this as important as having a piuparts clean archive is a release
goal since lenny.

>From the attached log (scroll to the bottom...):

1m53.8s ERROR: FAIL: Package purging left files on system:
  /usr/share/.mono/  not owned
  /usr/share/.mono/certs/not owned
  /usr/share/.mono/certs/Trust/  not owned
  /usr/share/.mono/certs/Trust/ski-03252FDE6F82013A5C2CDC2BA169B567D48CD3FD.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-03DE503556D14CBB66F0A3E21B1BC397B23DD155.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-04AA7A47A3E489AF1ACF0A40A7183F6FEFE97DBE.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-071FD2E79CDAC26EA240B4B07A50105074C4C8BD.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-07C35130A4AAE945AE3524FAFF242C33D0B19D8C.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-0876CDCB07FF24F6C5CDEDBB90BCE284374675F7.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-096A621692B05ABB550ECB75323A32E5B221C928.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-0972064E18430FE5D6CCC36A8B317B788FA883B8.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-0A85A9776505987C4081F80F972C38F10AEC3CCF.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-0B58E58BC64C1537A440A930A921BE47365A56FF.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-0D8CB661DA44B8D1147DC3BE7D5E48F0CECA6AB0.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-0FCA1E5C79E0A2F329B6D285B30B4AB565EC6B52.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-12F25A3EEA561CBFCD06ACF1F125C9A94BD41499.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-1538830F3F2C3F70331ECD46FE078C20E0D7C3B7.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-155F35575155FB25B2AD0369FC01A3FABE1155D5.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-17A0CDC1E441B63A5B3BCB459DBD1CC298FA8658.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-1A8462BC484C332504D4EED0F603C41946D1946B.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-1AEDFE413990B42459BE01F252D545F65A39DC11.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-1D1C650EA8F2257BB491CFE4B1B1E6BD55746C05.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-1E0CF7B667F2E192260945C055392E773F424AA2.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-1E824D2865803CC9416EAC352E5ACBDEEEF8395B.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-2130C9FB00D74E98DA87AA2AD0A72EB14031A74C.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-26951910D9E8A19791FFDC19D9B5043ED2730A6A.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-2920CBF1C30FDA068E139387FE5F601A29BBF3B6.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-29C590AB25AF11E461BFA3FF886191E60EFE9C81.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-2CD5504197158BF08F36615B4AFB6BD999C93392.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-2EE3DBB249D09C54795CFA272AFECC4ED2E84E54.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-31C3791BBAF553D717E0897A2D176C0AB32B9D33.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-3471D138D7153683476BD73764423B8E8D529DAB.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-354AF54DAF3FD78238ACAB716517758C9D5593E6.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-3814E6C8F0A9A403F44E3E22A35BF2D6E0AD4074.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-39958B628B5CC9D480BA580F973F150843CC98A7.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-3A9A8507106728B6EFF6BD05416E20C194DA0FDE.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-3AE10986D4CF19C29676744976DCE035C663639A.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-3CD89388C2C08209CC0199069320E99E7009634F.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-3DE629489BEA07CA21444A26DE6EDED283D09F59.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-3F8D9A598BFC7B7B9CA3AF38B039ED907180D6C8.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-410F1938AA997F420BA4D7279854A2174C2D5154.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-4232B616FA04FDFE5D4B7AC3FDF74C401D5A43AF.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-439C369FB09E304DC6CE5FAD10ABE503A5FAA914.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-446A95675579114F.cer  not owned
  /usr/share/.mono/certs/Trust/ski-45D9A5816E3D884D8D71D246C16E451EF3C4809D.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-45EBA2AFF492CB82312D518BA7A7219DF36DC80F.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-47B8CDFFE56FEEF8B2EC2F4E0EF925B08E3C6BC3.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-47E20C8BF6538852.cer  not owned
  /usr/share/.mono/certs/Trust/ski-48E668F92BD2B295D747D82320104F3398909FD4.cer 
 not owned
  /usr/share/.mono/certs/Trust/ski-4A78325211DB5916365EDFC11436406A477C4CA1.cer 
 not owned
  

Bug#808317: zsh: Update apt command completion

2015-12-18 Thread Felipe Sateler
Package: zsh
Version: 5.2-2
Severity: minor
Tags: patch


The apt completion is missing purge and autoremove commands. Attached
patch adds them.


Saludos

-- Package-specific info:

Packages which provide vendor completions:

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version
Architecture   Description
+++-==-==-==-=
ii  awscli 1.9.9-2all   
 Universal Command Line Environment for AWS
ii  docker-compose 1.5.2-1all   
 Punctual, lightweight development environments using Docker
ii  docker.io  1.8.3~ds1-2amd64 
 Linux container runtime
ii  git-buildpackage   0.7.0  all   
 Suite to help with Debian packages in Git repositories
ii  mpv0.12.0-1   amd64 
 video player based on MPlayer/mplayer2
ii  pulseaudio 7.1-2  amd64 
 PulseAudio sound server
ii  reprepro   4.16.0-1   amd64 
 Debian package repository producer
ii  systemd228-2  amd64 
 system and service manager
ii  systemd-container  228-2  amd64 
 systemd container/nspawn tools
ii  systemd-coredump   228-2  amd64 
 tools for storing and retrieving coredumps
ii  udev   228-2  amd64 
 /dev/ and hotplug management daemon
ii  vcsh   1.20150502-1   all   
 Version Control System for $HOME - multiple Git 
repositories in $HOME
ii  vlc-nox2.2.1-5+b1 amd64 
 multimedia player and streamer (without X support)

The following files were modified:

/etc/systemd/journald.conf
/etc/pulse/daemon.conf
/etc/pulse/default.pa
/etc/default/docker

dpkg-query: no path found matching pattern /usr/share/zsh/vendor-functions/


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages zsh depends on:
ii  dpkg1.18.3
ii  libc6   2.21-4
ii  libcap2 1:2.24-12
ii  libtinfo5   6.0+20151024-2
ii  zsh-common  5.2-2

Versions of packages zsh recommends:
ii  libncursesw5  6.0+20151024-2
ii  libpcre3  2:8.35-8

Versions of packages zsh suggests:
pn  zsh-doc  

-- no debconf information
--- /usr/share/zsh/functions/Completion/Debian/_apt	2015-12-03 20:44:53.0 -0300
+++ .zsh/functions/_apt	2015-12-18 12:36:49.326848831 -0300
@@ -407,10 +407,12 @@
 /$'install\0'/ /$'[^\0]#\0'/ ':packages::_deb_packages "$expl_packages[@]" avail' \# \
 /$'[^\0/]#/'/ /$'[^\0/]#\0'/ ':release name::_apt_releases' \) \| \
 /$'remove\0'/ /$'[^\0]#\0'/ ':packages::_deb_packages "$expl_packages[@]" installed' \# \| \
+/$'purge\0'/ /$'[^\0]#\0'/ ':packages::_deb_packages "$expl_packages[@]" installed' \# \| \
 /$'upgrade\0'/ \| \
+/$'autoremove\0'/ \| \
 /$'full-upgrade\0'/ \| \
 /$'edit-sources\0'/ \| \
-/"[]"/	':argument-1::compadd "$expl_action[@]" list search show update install remove upgrade full-upgrade edit-sources'
+/"[]"/	':argument-1::compadd "$expl_action[@]" list search show update install remove upgrade full-upgrade edit-sources autoremove purge'
 
   _apt-cmd () {
 local expl_action expl_packages


Bug#808319: britney: Allow skipping the second (upgrade testing) stage

2015-12-18 Thread Martin Pitt
Package: release.debian.org
Severity: normal
Tags: patch
User: release.debian@packages.debian.org
Usertags: britney

Hello,

It's sometimes useful to run britney in "dry mode" to run tests on the
unstable packages, but not the full second-stage upgrade test. This is
even more useful if/once britney can trigger and evaluate
autopkgtests, but even the current Debian ones are interesting.

Support this by skipping the upgrade test instead of crashing if the
UPGRADE_OUTPUT option in britney.conf is empty or absent.

Thanks for considering,

Martin

-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
From 95d3c01daa2f8ee2dd6daeecfbb652ad3fdac0d9 Mon Sep 17 00:00:00 2001
From: Martin Pitt 
Date: Fri, 18 Dec 2015 16:51:06 +0100
Subject: [PATCH] Skip upgrade testing if UPGRADE_OUTPUT option is absent or
 empty

It's sometimes useful to run britney in "dry mode" to run tests on the unstable
packages, but not the full second-stage upgrade test.

Support this by skipping the upgrade test instead of crashing if the
UPGRADE_OUTPUT option is empty or absent.
---
 britney.py | 7 +++
 1 file changed, 7 insertions(+)

diff --git a/britney.py b/britney.py
index 86158fe..cec4ee0 100755
--- a/britney.py
+++ b/britney.py
@@ -2891,6 +2891,13 @@ class Britney(object):
 else:
 self.upgrade_me = self.options.actions.split()
 
+# skip upgrade testing if UPGRADE_OUTPUT option is absent or empty
+try:
+if not self.options.upgrade_output:
+return
+except AttributeError:
+return
+
 with open(self.options.upgrade_output, 'w', encoding='utf-8') as f:
 self.__output = f
 
-- 
2.6.4



signature.asc
Description: Digital signature


Bug#808307: ifeffit: needs manual rebuild for Perl 5.22 transition

2015-12-18 Thread gregor herrmann
Source: ifeffit
Version: 2:1.2.11d-10
Severity: serious
Tags: sid stretch
Justification: fails to build from source on buildds
User: debian-p...@lists.debian.org
Usertags: perl-5.22-transition

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Since ifeffit build depends on the non-free pgplot5, it needs a
manual rebuild+upload for the ongoing perl 5.22 transition.

Cf. https://buildd.debian.org/status/package.php?p=ifeffit which
shows the failed automated binNMUs.

Cheers,
gregor


-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJWdBnYXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGKdUQAJfPJV0V9a8OuDjIWMKFsbPm
vq1/UviNLIMkCM8f1FNjZBcBWLFipcMipJp9dXKTZYRMCjCdXDnUupXj7Y8Q2OKh
2dajmqwAaXcMWkVjqH2skIA3kMWGnOr7f1j1Uugmy52vFOYcYtsYSDN8FufAyYjm
PqycbZwHJSZxoQyHBmATQidzaxbDZ9DhGDgjG6luOstVa14l+GjCTqF6xkv/5d0k
ac0e4xFVUGK4+a4r22Bw2IanLApjwJ5VrzECtgwQihvBxwTbpBm80JhZAJ9ELsFy
UdxNaHXuVtqD7TX4MPc3EShmI6j13KJrj14fOASyyrco1+f53wPZvS7tkVMbuyDq
doOTSikEa+zMJ2KSZGOgeOS+CGPYbAyoJHODIYnHTysnkxzSmj/gX/kBm74W7qs1
iBvuvjtC/wqErc/mCQ9t4c3juFqdoVCUILomWnVHVydhvXuNX47cYYw+TA+RGNBH
zx+F+jy9r6lSAJkD3b93df9ZJ5ohkGJPcdqnYdMVpJBHygnHGWZS1/cT1YcHII6D
g7EuBk0kBpNEiDjysSBIR2VCeaL5XdsyiBB3KgBRyc5wlO7Q5TOH63YVe5DdH7ut
3UjmH8U3nklu2Uo9KyngHXs6bnY75r5qYW4AQJyS3N/GnXSu5IlEW2F5N5iU86wN
rLuM+8HFuwVgIUknlKcH
=pfr/
-END PGP SIGNATURE-



Bug#806336: rpcbind: socket activation miss DefauiltDependencies=no - systemd detected sysinit cycle

2015-12-18 Thread Matthias Dellweg
Control: Severity important


Hi all!
I have the same problem and adding the two lines

After=systemd-tmpfiles-setup.service
DefaultDependencies=no

to the first section of /lib/systemd/system/rpcbind.socket solves the
problem.

I guess 'After=systemd-tmpfiles-setup.service' is needed, because /run
is a tmpfs. Have not tested it without though.

In my case console-setup, kbd and nfs-common got kicked out due to
dependency cycles, which then lead to a missing rpc.idmapd and
pulseaudio not beeing started due to wrong user and group ids on the home
directory.

Since this bug is actually able to break other Packages, i raise the
severity to important.

best regards
 M. Dellweg



Bug#808296: tor: Latest version doesn't start

2015-12-18 Thread Peter Palfrader
On Fri, 18 Dec 2015, Michael Meskes wrote:

> On a fresh unstable installation tor refuses to do anything. The situation
> seems to be different from #802521, hence a new bug report. If it turns out to
> be the same bug, feel free to merge.
> 
> Dez 18 13:16:08 feivel tor[1349]: Dec 18 13:16:08.001 [notice] Read 
> configuration file "/usr/share/tor/tor-service-defaults-torrc".
> Dez 18 13:16:08 feivel systemd[1356]: tor@default.service: Failed at step 
> APPARMOR spawning /usr/bin/tor: No such file or directory
> Dez 18 13:16:08 feivel systemd[1]: tor@default.service: Main process exited, 
> code=exited, status=231/APPARMOR
> Dez 18 13:16:08 feivel systemd[1]: tor@default.service: Unit entered failed 
> state.
> Dez 18 13:16:08 feivel systemd[1]: tor@default.service: Failed with result 
> 'exit-code'.
> Dez 18 13:16:08 feivel systemd[1]: tor@default.service: Service hold-off time 
> over, scheduling restart.
> 
> Manually downgrading to 0.2.5.12-1 solved the problem for now.

Can you tell me more about the system?  My guess is, this is an lxc
container.  Am I right?  If not, what's the kernel?  Some other kind of
virtualization going on?

weasel
-- 
|  .''`.   ** Debian **
  Peter Palfrader   | : :' :  The  universal
 https://www.palfrader.org/ | `. `'  Operating System
|   `-https://www.debian.org/



Bug#808299: emacs24: skeleton input captures '?' (question mark) key

2015-12-18 Thread David Madore
Package: emacs24
Version: 24.4+1-5

To reproduce: create an empty .html file (touch /tmp/blah.html) then
open it with Emacs in a terminal (emacs -q -nw /tmp/blah.html).  Now
type C-c C-c h to insert a link and try entering a URL with a '?'
(question mark), say "https://www.google.com/search?q=emacs;.
Expected behavior: '?' simply inserts a '?'.  Observed behavior: '?'
conjures some useless and totally uninformative help.  Worse, since
this help disappears as soon as any other character is entered, when
copy-pasting such a link, the '?' character simply disappears.
(Indeed, I discovered this bug because I found a huge number of broken
links in HTML pages I had written, all with a missing '?'.)

I don't know if the problem is that sgml-mode.el badly uses the
define-skeleton function or that the define-skeleton function is bad,
but this is clearly wrong, extremely annoying, and a regression
w.r.t. emacs23, or even w.r.t. Ubuntu's emacs24 24.3+1-2ubuntu1 for
some reason.  (I was unable to read the code to figure out where this
capture of '?' takes place or why the difference between Debian and
Ubuntu packages.)

Suggestions on how to work around this would be very much welcome!

-- 
 David A. Madore
   ( http://www.madore.org/~david/ )



Bug#807392: libsendmail-milter-perl: FTBFS: Segmentation fault (core dumped)

2015-12-18 Thread gregor herrmann
Control: tag -1 - unreproducible

On Wed, 16 Dec 2015 17:48:44 +0100, gregor herrmann wrote:

> On Tue, 08 Dec 2015 15:12:41 +0100, gregor herrmann wrote:
> 
> > > libsendmail-milter-perl fails to build from source in unstable/amd64:
> [..]
> > This builds fine for me (cowbuilder sid amd64):
> Can anyone else reproduce or not reproduce this issue?

The buildds could reproduce the problem:

https://buildd.debian.org/status/logs.php?pkg=libsendmail-milter-perl=0.18-8%2Bb1


Cheers,
gregor

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Arik Brauer: Sie hab'n a Haus baut


signature.asc
Description: Digital Signature


Bug#761909: systemd does not unmount nfs shares before bringing down the network interface

2015-12-18 Thread Michael Biebl
Am 18.12.2015 um 11:12 schrieb Martin Pitt:
> If this was really deliberate and we can't prevent instantiated units
> from getting stopped during shutdown, then I propose as a fallback we
> just drop the ExecStop=ifdown (or replace it with some "echo not
> supported blabla, please use ifdown directly"). Michael, any
> objections to that? This is just an internal helper unit for the udev
> rule, after all.

The stop action is there, so the device is properly stopped on unplug.
And if we don't stop the unit, it wouldn't work if we re-plugin the
hardware. So I don't think we can easily drop the stop action.

I agree that this sounds like an upstream bug. If there is not explicit
Conflicts=shutdown.target, I don't see why the instance should be
stopped. That would be very inconsistent and unexpected behaviour.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



Bug#807473: Potential data loss and security breach when used with nfs server

2015-12-18 Thread Andreas Beckmann
Control: tag -1 upstream

On 2015-12-09 10:12, Nick Koretsky wrote:
> When this driver is used on the machine which acts as nfs server you can
> mount shares, filesystem looks ok, but attempt to read any file produces
> random garbage (i suspect parts of the server memory). Writing to files
> works - this is a source for data loss, because a lot of programs will
> attempt to override "incorrect" files. 
> I am 100% sure this is caused by this driver: rmmod r8168 insmod r8169
> corrects this, rmmod r8169 insmod r8168 brings it back.

That sounds weird, but I cannot help debugging this.

I just uploaded a new upstream release. Unfortunately there is no
upstream changelog available. Please try it, maybe it fixes your issue.


Andreas



Bug#808306: xfonts-kappa20: ships /usr/share/fonts/X11/misc/fonts.alias

2015-12-18 Thread Andreas Beckmann
Package: xfonts-kappa20
Version: 1:0.396-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package modifies a file it
ships.

>From the attached log (scroll to the bottom...):

0m30.7s ERROR: FAIL: debsums reports modifications inside the chroot:
  /usr/share/fonts/X11/misc/fonts.alias
  

Shipping this file seems utterly wrong, since that file is used by many
fonst and is managed by some helpers which are usually run from the
maintainer scripts.


cheers,

Andreas


xfonts-kappa20_1:0.396-1.log.gz
Description: application/gzip


Bug#778240: tracker.debian.org has much worse display clarity

2015-12-18 Thread Raphael Hertzog
On Fri, 18 Dec 2015, Ian Jackson wrote:
> > That said I'm not opposed to try to do something more dense but the layout
> > is handled via bootstrap and reducing the spacing in a consistent manner
> > probably requires to rebuild bootstrap with different settings in terms
> > of spacing.
> 
> I have to confess that I have no idea what `bootstrap' is.

http://v4-alpha.getbootstrap.com/
https://github.com/twbs/bootstrap/tree/v4-dev

I use v4 alpha2 currently. I have no experience rebuilding bootstrap
currently but there are some docs:
http://v4-alpha.getbootstrap.com/getting-started/build-tools/

> I'm not scared of unfamiliar code but it would probably save me a lot
> of effort if you could sketch out for me how I would go about getting
> the source code for bootstrap and trying out a modified version of
> either that or with of
>   https://anonscm.debian.org/cgit/qa/distro-tracker.git.

Once rebuilt you just have to put the .css file in
distro_tracker/html/static/css/bootstrap.min.css and you should be able to
try it out rather quickly with a local instance.

See https://tracker.debian.org/docs/contributing.html for details.

> Is the bootstrap you are referring to `libjs-twitter-bootstrap' ?

Yes. Except that the Debian package is outdated and not maintained.

But before spending lots of time with bootstrap, have a try by tweaking
distro_tracker/core/static/css/style.css and adding CSS for the list-group
and list-group-item classes to reduce the vertical padding and margin...
maybe that will be enough to please you.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/



Bug#808311: bareos-storage-tape: fails to upgrade from 'testing' - trying to overwrite /usr/sbin/bscrypto

2015-12-18 Thread Andreas Beckmann
Package: bareos-storage-tape
Version: 14.2.6-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', 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 unpack .../bareos-storage-tape_14.2.6-1_amd64.deb ...
  Unpacking bareos-storage-tape (14.2.6-1) over (14.2.5-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/bareos-storage-tape_14.2.6-1_amd64.deb (--unpack):
   trying to overwrite '/usr/sbin/bscrypto', which is also in package 
bareos-storage 14.2.5-2
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)


cheers,

Andreas


bareos-storage-tape_14.2.6-1.log.gz
Description: application/gzip


Bug#805894: jessie-pu: package mdadm/3.3.2-5+deb8u1

2015-12-18 Thread Adam D. Barratt

On 2015-12-18 14:13, Yann Soubeyrand wrote:

Hi,

Is there any blocker for this update?


As with every other update, person time.

Regards,

Adam



Bug#808314: developers-reference: maintainer scripts: /usr is always there

2015-12-18 Thread Jakub Wilk

* Ansgar Burchardt , 2015-12-18, 16:24:
Section 6.4 "Nest practices for maintainer script" has a pathfind() 
function which it suggests copy & pasting into maintainer scripts. It 
suggests "which" as an alternative that requires /usr.


I think "best practices" and "copy and paste this function" are 
contradictionary. Given that /usr is *always* available when 
maintainer scripts are run, using `which` should be just fine.


Also, which(1) has been available in /bin for a while:
| debianutils (2.12.0) unstable; urgency=medium
|
[...]
|   * debian/rules: move which to /bin and leave a compatibility
| symlink in /usr/bin.  The symlink will be dropped at a
| later date.  closes: #295058.
|
|  -- Clint Adams   Sun, 13 Feb 2005 10:01:09 -0500

--
Jakub Wilk



Bug#808296: tor: Latest version doesn't start

2015-12-18 Thread Michael Meskes
> Can you tell me more about the system?  My guess is, this is an lxc
> container.  Am I right?  If not, what's the kernel?  Some other kind of

Nope, Debian unstable on a new laptop. However, the kernel is *not* a
Debian one. The laptop needs the latest development version to enable
touchpad and the like. Could any kernel feature make a difference? If so
which?

> virtualization going on?

No, just a straight desktop usage.

But is tor supposed to not work in virtualization?

Michael
-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael.meskes at gmail dot com
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL



Bug#808275: kopete: Kopete crashes every time a message window is closed

2015-12-18 Thread Diederik de Haas
forwarded 808275 https://bugs.kde.org/show_bug.cgi?id=355275
thanks

On Friday 18 December 2015 09:58:11 Nicos Gollan wrote:
> With kdelibs 4.14.14, Kopete is affected by upstream bug 355275
> https://bugs.kde.org/show_bug.cgi?id=355275

Updated the Debian BTS accordingly

signature.asc
Description: This is a digitally signed message part.


Bug#808305: Missing fwupd breaks upgrade functionality

2015-12-18 Thread Michael Biebl
Package: gnome-software
Version: 3.18.3-2
Severity: serious


Since upgrading to the version which enabled fwupd support, the upgrade
functionality is broken when fwupd is not installed.

I no longer get any notifications when new packages are awailable and
when opening the Updates tab in the main software just shows an error
messages that the fwupd D-Bus service is not available.

Dez 18 14:59:41 pluto gnome-session[15771]: (org.gnome.Software:15979):
Gs-WARNING **: failed to get updates:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.fwupd was not provided by any .service files

I'm marking this as RC since this breaks essential functionality of
gnome-software and I think it shouldn't migrate to testing until we have
a solution for that.

Installing fwupd makes gnome-software work again, so it's clearly a
problem of it not dealing with the case gracefully when fwupd is not
available.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-software depends on:
ii  appstream0.9.0-2
ii  dconf-gsettings-backend [gsettings-backend]  0.24.0-2
ii  gnome-software-common3.18.3-2
ii  gsettings-desktop-schemas3.18.1-1
ii  libappstream-glib8   0.5.5-1
ii  libatk1.0-0  2.18.0-1
ii  libc62.21-4
ii  libcairo-gobject21.14.4-1
ii  libcairo21.14.4-1
ii  libfwupd10.6.0-1
ii  libgdk-pixbuf2.0-0   2.32.3-1
ii  libglib2.0-0 2.46.2-1
ii  libgnome-desktop-3-123.18.2-1
ii  libgtk-3-0   3.18.6-1
ii  liblimba00.5.4-1
ii  libpackagekit-glib2-18   1.0.11-1
ii  libpango-1.0-0   1.38.1-1
ii  libpangocairo-1.0-0  1.38.1-1
ii  libpolkit-gobject-1-00.105-14
ii  libsoup2.4-1 2.52.2-1
ii  libsqlite3-0 3.9.2-1
ii  packagekit   1.0.11-1

gnome-software recommends no packages.

Versions of packages gnome-software suggests:
pn  fwupd  
pn  limba  

-- no debconf information



Bug#808151: systemd: failed to start remount root and kernel file system

2015-12-18 Thread Michael Biebl
Am 18.12.2015 um 15:59 schrieb Frank B. Brokken:
> Is there a way to determine that? What I do to upgrade the system is run
> 'aptitude update' and then 'aptitude upgrade'. Is there a log somewhere that
> tells me what packages and versions were updated at what moments in time?

/var/log/dpkg.log is a low-level log.

and then there is one for aptitude at /var/log/aptitude

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Bug#808266: linux-image-3.2.0-4-686-pae: i386 Wheezy JFS broken in 3.2.73-2+deb7u1 security update

2015-12-18 Thread Robert Henney
On Fri, Dec 18, 2015 at 01:20:16PM +, Ben Hutchings wrote:

> 
> Which boot loader are you using?  Your report doesn't list any:
> 
> Versions of packages linux-image-3.2.0-4-686-pae suggests:
> pn  debian-kernel-handbook 
> pn  grub-pc | extlinux | lilo  
> ii  linux-doc-3.2  3.2.73-2+deb7u1

grub-legacy

grub v2 had some issue detecting my raid configuration years back so I stuck
with the older grub.  never investigated if the issue I ran into with it
was fixed, but since the old grub was meeting my needs I continued using it. 



Bug#808301: login: package description review

2015-12-18 Thread Justin B Rye
Package: login
Version: 1:4.2-3.1
Severity: wishlist
Tags: patch

The long package description for login features some distinctly
non-native-speakerish grammar and some out-of-date assumptions.  It's
still perfectly comprehensible, and a case could be made for the
argument that descriptions for "Essential: yes" packages don't much
matter (as no user ever needs to decide whether or not to install
login).  On the other hand it's a high-profile package, so I thought
I'd submit a wishlist patch.

# Description: system login tools

A perfectly good synopsis.

#  These tools are required to be able to login and use your system.

I see three problems here.
 * This sentence starts awkwardly by luring readers up a garden-path
   parsing involving a requirement that these tools should behave in a
   certain way.  There's no need for any phrasing this convoluted when
   it could just say "You need these tools to..."
 * "To login" is wrong.  The noun and of course the executable may be
   single words, but what's needed here is the verb, which is two
   words - it's "I logged myself in", not "I logined myself".
 * It's not true!  Running "rm /bin/login" doesn't stop me logging in
   and using my system via an SSH connection or an X display manager.

Next we run straight into a list of three executables in the package
and their functions.  (The lack of context gives the impression that
it is intended as an exhaustive list of "these tools".)

#The
#  login program invokes your user shell and enables command execution.

Since these three programs are being introduced here the more natural
English word-order would be "The program 'login'..." (though this
would be barely noticeable if it wasn't repeated).

But then the rest of the sentence is misleading.  I don't need to use
login to get a shell - I get one free with every xterm; and executing
/bin/login achieves nothing, so from a user's point of view it's not
much of a "tool".  The description omits the important thing about
login, which is that it's invoked by the getty process running on a
TTY (or these days by a systemd getty@.service, however that works
exactly).

#   The
#  newgrp program is used to change your effective group ID (useful for
#  workgroup type situations).

That's "The program 'newgrp'..."; then "workgroup-type situations"
needs a hyphen and is oddly informal alongside the complex impersonal
phrasing of these sentences (besides which, thanks to Microsoft the
word "workgroup" is hopelessly ambiguous).  But more importantly, how
is "newgrp" important enough to deserve a mention here?  Does anybody
ever use it?  Instead I would suggest introducing /usr/sbin/nologin
here and leaving out newgrp along with sg, faillog, and lastlog.

(And in fact rather than this exclusive focus on the tools - i.e.
executables - in the package, it might also make sense to hint at the
presence of things like /etc/securetty and /etc/pam.d/login by saying
that the package provides "infrastructure".)

#  The su program allows changing your effective
#  user ID (useful being able to execute commands as another user).

First there's the repeated word-order niggle, then an unclear use of
"allow" (su doesn't just render EUID changes permissible, it directly
changes your EUID).  And as for the part in parentheses... well, I
think it's just trying to say "useful for executing commands...", but
with entirely broken syntax.

This is also a bit dated, since I'm more likely these days to switch
UIDs with sudo (or pkexec or runuser) than with su.

My suggested thoroughly revised version:

 Description: system login tools
  This package provides some required infrastructure for logins and for
  changing effective user or group IDs, including:
   * login, the program that invokes a user shell on a virtual terminal;
   * nologin, a dummy shell for disabled user accounts;
   * su, a basic tool for executing commands as root or another user.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (50, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 4.4.0-rc4-686-pae (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages login depends on:
ii  libaudit1   1:2.4.4-4
ii  libc6   2.19-22
ii  libpam-modules  1.1.8-3.1
ii  libpam-runtime  1.1.8-3.1
ii  libpam0g1.1.8-3.1

login recommends no packages.

login suggests no packages.

-- no debconf information
-- 
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
diff -ru shadow-4.2.pristine/debian/control shadow-4.2/debian/control
--- shadow-4.2.pristine/debian/control	2014-11-19 20:49:09.0 +
+++ 

Bug#808300: sogo-openchange: Please remove dependency on openchange

2015-12-18 Thread Jelmer Vernooij
Package: sogo-openchange
Severity: normal

Dear Maintainer,

OpenChange is slated for removal from the archive (#804335). Please
remove the dependency of SOGo on OpenChange. I have attached a patch
that does this and removes the sogo-openchange binary package.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
commit 73d4cadb935df3c99e6e8af4403465c046dec4cb
Author: Jelmer Vernooij 
Date:   Fri Dec 18 13:04:49 2015 +

Remove sogo-openchange, as OpenChange is being removed from the archive.

diff --git a/debian/changelog b/debian/changelog
index e9e1e1f..0f989a5 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+sogo (2.2.14-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Remove sogo-openchange, as OpenChange is being removed from the
+archive.
+
+ -- Jelmer Vernooij   Fri, 18 Dec 2015 13:04:34 +
+
 sogo (2.2.14-1) experimental; urgency=medium
 
   * [e1c02cf9] New upstream release
diff --git a/debian/control b/debian/control
index ab0874a..1e646dd 100644
--- a/debian/control
+++ b/debian/control
@@ -8,14 +8,10 @@ Build-Depends: debhelper (>= 9),
  libgnutls28-dev,
  liblasso3-dev,
  libldap2-dev,
- libmapi-dev (>= 1:2.2),
- libmapiproxy-dev (>= 1:2.2),
- libmapistore-dev (>= 1:2.2),
  libmemcached-dev,
  libsbjson-dev,
  libsope-dev (>= 2.2.14),
- libxml2-dev,
- python-samba
+ libxml2-dev
 Section: mail
 Standards-Version: 3.9.6
 Homepage: http://www.sogo.nu/
@@ -62,13 +58,3 @@ Description: Scalable groupware server - debugging symbols
  the SOPE application server with focus on scalability.
  .
  This package contains the debugging symbols for SOGo.
-
-Package: sogo-openchange
-Architecture: any
-Depends: sogo (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}
-Description: Scalable groupware server - OpenChange backend
- SOGo is a groupware server built around OpenGroupware.org (OGo) and
- the SOPE application server with focus on scalability.
- .
- This package contains the plugin for using SOGo as a backend to
- OpenChange.
diff --git a/debian/rules b/debian/rules
index a11ea6e..0a93c9f 100755
--- a/debian/rules
+++ b/debian/rules
@@ -9,19 +9,16 @@ DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
 
 override_dh_auto_clean:
 	[ ! -f config.make ] || $(MAKE) distclean
-	[ ! -f config.make ] ||	$(MAKE) -C OpenChange distclean
 	rm -f config.make
 
 override_dh_auto_build:
 	dh_auto_build -- OBJCFLAGS="$(CFLAGS)" CPPFLAGS="$(CPPFLAGS)" LDFLAGS="$(LDFLAGS)" messages=yes
-	$(MAKE) -C OpenChange OBJCFLAGS="$(CFLAGS)" CPPFLAGS="$(CPPFLAGS)" LDFLAGS="$(LDFLAGS)" messages=yes
 
 override_dh_auto_configure:
 	./configure --with-ssl=gnutls --enable-saml2 --prefix=/usr/System
 
 override_dh_auto_install:
 	$(MAKE) DESTDIR=$(CURDIR)/debian/tmp GNUSTEP_INSTALLATION_DOMAIN=SYSTEM OBJCFLAGS="$(CFLAGS)" CPPFLAGS="$(CPPFLAGS)" LDFLAGS="$(LDFLAGS)" messages=yes install
-	$(MAKE) -C OpenChange DESTDIR=$(CURDIR)/debian/tmp GNUSTEP_INSTALLATION_DOMAIN=SYSTEM OBJCFLAGS="$(CFLAGS)" CPPFLAGS="$(CPPFLAGS)" LDFLAGS="$(LDFLAGS)" messages=yes install
 	mkdir -p debian/tmp/etc/default debian/tmp/etc/cron.d debian/tmp/etc/logrotate.d debian/tmp/usr/share/doc/sogo debian/tmp/usr/lib/tmpfiles.d
 	cp Scripts/sogo-default debian/tmp/etc/default/sogo
 	cp Scripts/sogo.cron debian/tmp/etc/cron.d/sogo
@@ -52,9 +49,6 @@ override_dh_auto_install:
 	mkdir -p debian/tmp/usr/share/GNUstep/Libraries/Resources
 	mv debian/tmp/usr/lib/GNUstep/Libraries/Resources/NGCards debian/tmp/usr/share/GNUstep/Libraries/Resources
 	rmdir debian/tmp/usr/lib/GNUstep/Libraries/Resources debian/tmp/usr/lib/GNUstep/Libraries
-	rm debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)/mapistore_backends/libMAPIStoreSOGo.so.1
-	rm debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)/mapistore_backends/libMAPIStoreSOGo.so
-	mv debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)/mapistore_backends/libMAPIStoreSOGo.so.1.0.0 debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)/mapistore_backends/SOGo.so
 
 override_dh_install:
 	dh_install --list-missing --fail-missing


Bug#808302: not installable on sid: Depends: perlapi-5.20.2 which is a virtual package and is not provided by any available package

2015-12-18 Thread Yaroslav Halchenko
Package: libxml-libxml-perl
Version: 2.0123+dfsg-1
Severity: critical

Causes FTBFS of packages build-depending on this one thus critical.

in a clean docker looks like:

root@306c98029745:/# apt-get install libxml-libxml-perl
Reading package lists... Done
Building dependency tree... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libxml-libxml-perl : Depends: perl (>= 5.20.2-6) but it is not going to be 
installed
  Depends: libxml-namespacesupport-perl but it is not going 
to be installed
  Depends: libxml-sax-perl but it is not going to be 
installed
E: Unable to correct problems, you have held broken packages.


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-rc1+ (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libxml-libxml-perl depends on:
ii  libc6 2.19-22
ii  libxml-namespacesupport-perl  1.11-1
ii  libxml-sax-perl   0.99+dfsg-2
ii  libxml2   2.9.2+zdfsg1-4
ii  perl  5.20.2-6
ii  perl-base [perlapi-5.20.2]5.20.2-6
ii  zlib1g1:1.2.8.dfsg-2+b1

libxml-libxml-perl recommends no packages.

libxml-libxml-perl suggests no packages.

-- no debconf information



Bug#808304: rancid: Rancid in backports

2015-12-18 Thread Dean Hamstead
Source: rancid
Severity: wishlist

Dear Maintainer,
Thank you for all your hard work in keeping this package updated in
debian. Would it be possible to have 3.2 in backports?

Cheers



Bug#805894: jessie-pu: package mdadm/3.3.2-5+deb8u1

2015-12-18 Thread Yann Soubeyrand
Hi,

Is there any blocker for this update? Do you think it could be included
in the coming point release? This would be great as it is a rather
ancient and annoying bug and there seems to be some expectation on this
update
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784070#303) ;-) If
the package has to be reworked, let me know and I'll try to do the
necessary.

Regards,

Yann



Bug#808316: grub-common: Grub supports running the system even if you forget the password

2015-12-18 Thread Himanshu Shekhar
Package: grub-common
Version: 2.02~beta2-22+deb8u1
Severity: important

Dear Maintainer,

* What led up to the situation?

There are tons of articles available on the internet which detail about the
steps in case you forget the password, you can find one here
(http://www.howtogeek.com/howto/linux/reset-your-forgotten-ubuntu-password-in-2
-minutes-or-less/ ).

Articles like the above, say to add the text "mount -rw -o remount /" to the
kernel line, after pressing e in the grub menu, after which the person having
the physical possession of the system has the root access.

Physical possession is bit difficult in case of servers and desktops, but is
very easy in today's world where laptop users are also loving Linux on their
portable systems.

* What exactly did you do (or not do) that was effective (or ineffective)?

There were concerns on the internet about the bug that gave root access after
pressing backspace 28 times, which was considered threat.
However, I knew this from long and considered this method also as a security
threat.

There should be some way to give the user the method to recover the lost
password in worst cases, but prevent any such unauthorised user with physical
possession of systems gain root access within a minute and mess up everything.



-- Package-specific info:

*** BEGIN /proc/mounts
/dev/sda1 / ext3 rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/sda5 /media/himanshu/himanshu fuseblk 
rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096 0 0
*** END /proc/mounts

*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
  fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
insmod all_video
  else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_gpt
insmod ext2
set root='hd0,gpt1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 
--hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1  
c5c12eeb-c91b-4dc0-9bf0-be761e43af8f
else
  search --no-floppy --fs-uuid --set=root c5c12eeb-c91b-4dc0-9bf0-be761e43af8f
fi
font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_IN
  insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
  set timeout=-1
else
  if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
  # Fallback normal timeout code in case the timeout_style feature is
  # unavailable.
  else
set timeout=5
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_gpt
insmod ext2
set root='hd0,gpt1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 
--hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1  
c5c12eeb-c91b-4dc0-9bf0-be761e43af8f
else
  search --no-floppy --fs-uuid --set=root c5c12eeb-c91b-4dc0-9bf0-be761e43af8f
fi
insmod png
if background_image /usr/share/images/desktop-base/lines-grub.png; then
  set color_normal=white/black
  set color_highlight=black/white
else
  set menu_color_normal=cyan/blue
  set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu 
--class os $menuentry_id_option 
'gnulinux-simple-c5c12eeb-c91b-4dc0-9bf0-be761e43af8f' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
set root='hd0,gpt1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 
--hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1  
c5c12eeb-c91b-4dc0-9bf0-be761e43af8f
else
  search --no-floppy 

  1   2   3   >