Bug#861514: radicale: htpasswd authentication vulnerable to timing-based bruteforce attacks

[Salvatore Bonaccorso]

Hi Jonas,

On Sun, Apr 30, 2017 at 12:40:27AM +0200, Jonas Smedegaard wrote:
> Package: radicale
> Version: 2.0.0~rc1-1

Quickly checked and at least the version in stretch is affected as
well (not done triage on older versions yet). There is a fix for the
1.1.x branch at:

https://github.com/Kozea/Radicale/commit/190b1dd795f0c552a4992445a231da760211183b

FTR, I have requested a CVE for this issue via https://cveform.mitre.org

Regards,
Salvatore

Bug#861520: DMD: do not complain about migration of new packages in unstable during the freeze

[Paul Wise]

Package: qa.debian.org
Severity: wishlist
User: qa.debian@packages.debian.org
Usertags: udd

I sponsored a package and it reached unstable after the soft freeze. I
now get warnings daily in my DMD RSS feed about it. It would be nice if
this warning were silenced when the package is blocked by the freeze.

open-ath9k-htc-firmware: Migration: Has been in Debian for 31 days, but 
never migrated to testing

The excuses for the package clearly indicate it is blocked by the freeze:

https://qa.debian.org/excuses.php?package=open-ath9k-htc-firmware

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#779400: tracker.debian.org: add a patches panel

[Paul Wise]

On Sun, Apr 30, 2017 at 3:24 AM, Scott Kitterman wrote:

> I can see some utility in this, but think it should definitely be below bugs.

Could you explain your reasoning here?

> I suspect with django you'll be able to allow users to turn different sources
> on or off, so they can customize to taste (there's definitely more there than
> I'd care to see, but if I can set it up once and not worry about it, then I
> don't care).

That would definitely be useful, but AFAICT tracker.d.o doesn't yet
support user customisation of the pages.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#861204: deb-systemd-invoke: fails to handle units with escaped characters

[Bernd Zeimetz]

Hi Michael,

any news on that? I could upload an NMU if you thats okay for you.
Or is there anything else I can help with?

Thanks,

Bernd


On 04/26/2017 12:26 PM, Bernd Zeimetz wrote:
> On 2017-04-26 01:01, Michael Biebl wrote:
> 
>> Hm, but #856429 is severity minor. Something doesn't compute here.
> 
> Take #860861 instead - copy fail, sorry.
> 

-- 
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F

Bug#861387: fails to open applet menu

[Scott Leggett]

forwarded 861387 https://github.com/christophgysin/pasystray/issues/88
tags 861387 - moreinfo unreproducible
--

> Here is how to reproduce this bug:
> 
> 1) install Orca screen reader
> 2) activate Orca
> 3) go to Gnome desktop legacy icon tray by pressing  ctrl-alt-tab from
> keyboard
> 4) select the pasystray applet by using left and right arrow keys from
> keyboard
> 5( click the  pasystray by pressing enter or space from keyboard

Hi Mika,

Thanks for the instructions, I can reproduce the problem. From what I
can see the reason that the menu doesn't appear is that the icon only
responds to mouse input - pressing enter or space does nothing.

I've forwarded the bug upstream but unfortunately, given that we are
currently in release-freeze, this is not likely to be fixed for Stretch.

I'll update the bug report once upstream responds.

-- 
Regards,
Scott.


signature.asc
Description: PGP signature

Bug#861368: RFS: helm/2.5.0-2 [Team Upload]

[Sean Whitton]

On Fri, Apr 28, 2017 at 05:47:13AM +, Gianfranco Costamagna wrote:
> in deferred/2, so Sean can review changes if needed :)

LGTM.  Rescheduled to 0-day.  Thanks again.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#861485: unblock: espeak-ng/1.49.0+dfsg-10

[Cyril Brulebois]

Niels Thykier  (2017-04-29):
> Samuel Thibault:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: unblock
> > 
> > Hello,
> > 
> > It was reported in Bug#860891 that the espeak-ng synthesis does
> > not work any more with at least some mbrola voices, making mbrola
> > voices useless since mbrola by itself does not take text directly,
> > but phonemes produced by espeak-ng.  Upstream already fixed it just
> > by increasing the buffer size to 60ms, which I have now uploaded as
> > espeak-ng=1.49.0+dfsg-10 (see attached debdiff)
> > 
> > Samuel
> > 
> > unblock espeak-ng/1.49.0+dfsg-10
> > 
> > [...]
> 
> Ack with me, CC'ing KiBi for a d-i ack.

Sure, please go ahead.


KiBi.


signature.asc
Description: Digital signature

Bug#861519:

[Hayden Briese]

This is an accidental duplicate, please remove.

Bug#861519: ITP: fancon -- High performance system & NVIDIA fan controller

[Hayden Briese]

Package: wnpp
Severity: wishlist
Owner: Hayden Briese 

* Package name: fancon
  Version : 0.11.2
  Upstream Author : Hayden Briese 
* URL : https://github.com/hbriese/fancon
* License : Apache v2
  Programming Lang: C++
  Description : High performance, configurable system & NVIDIA fan
controller

fancon is a multi-threaded, high performance fan control daemon
written in C++ aimed at low overhead, and configurability.
It provides meaningful configuration through PWM, RPM or percentage
speed control.
Support for both system (lm-sensors supported) & NVIDIA fans.

I am the developer for fancon, and developed it as an
alternative/replacement to the `fancontrol` package.
Please keep in mind that I appreciate the work the lm-sensors team has
done on `fancontrol`, and wish to improve Linux fan control in part
through use of their library `libsensors`.

fancon provides several key improvements over `fancontrol`:
- meaningful configuration - RPM & percentage speed control, not just
  PWM control as `fancontrol` provides (e.g. 5% or 600RPM vs 125PWM);
  note. PWM control is still supported.
- simpler configuration - greater readability and ease of use (a serious
  issue for `fancontrol` in my opinion).
- support for stopping fans with gauranteed start (minimum PWM is
  almost always lower than the starting PWM meaning you can't go
  from 0RPM -> 400RPM, but instead from 0 -> 500 -> 400),
  not supported by `fancontrol`.
- user doesn't require knowledge detailed knowledge of each fan as
  they do with `fancontrol` due to 'meaningful configuration' support
  (120PWM does not result in the same RPM for even the same
  model of fan).
- no limit on the number of configuration points,
  where as `fancontrol` has a limit of 3.
- no limit on the number of configuration points,
  where as `fancontrol` has a limit of 3.

I will maintain the package, which will be very frictionless - as both a
debian user, and the package's developer.
I am looking looking for a sponsor; you may contact me via email for
more information. The package has been built and is working well, just
requring finishing details such as the man doc.

Thanks,
Hayden

Bug#861300: cdrom-detect: Please merge changes from Ubuntu

[Colin Watson]

On Thu, Apr 27, 2017 at 09:42:47AM +0200, Balint Reczey wrote:
> Please merge changes from the delta carried by Ubuntu:

For the record, this does not have my approval even though some of the
commits are in my name.  It would generally be polite to at least try to
ask people named as committers before you send patches attributed to
them (and also e.g. ask what email addresses they prefer to be used for
the patches you've generated in their name: I never use
colin.wat...@canonical.com except in situations where it's been chosen
for me and I have no alternative).

> commit 44dc46c133fa5e87d27eeef4c936e44cb886602b
> Author: Balint Reczey 
> Date:   Wed Apr 26 21:07:42 2017 +0200
> 
> Show Ubuntu name on Ubuntu
> 
> Build depend on dpkg-dev (>= 1.15.1) and patch to do so.

This is thoroughly gross in a native package, and I don't think it
should be accepted.  Branding patches are annoying but basically a
necessary reality.

The only sensible way to avoid carrying these patches in downstream
distributions is to debrand altogether, i.e. not mention Debian in d-i
strings.  In some cases that's reasonable, but I don't think it can be
done everywhere.

(And no, db_subst isn't a solution in the general case: while it isn't a
problem in this specific case, in general, different proper names are
translated in various ways in different languages, may undergo
declension, etc.  My stock example of this is "a Debian image" vs. "an
Ubuntu image", but there's a wide range of complexity here.)

If I were putting the effort into figuring out how to merge this
properly rather than just forwarding patches directly, I'd work out a
rephrasing of the log messages that was more generic and didn't require
branding, and I'd generate the cdrom/suite template at build time in a
way that's reasonably easy to maintain (.in files or similar).
Committing a patch file like this is right out: not only are they highly
unconventional in native packages but in practice they're a pain to
maintain and tend to bitrot.

> commit 08cfa29937f3dfbe796cab4d7e05bf2dd8808f40
> Author: Colin Watson 
> Date:   Wed Apr 26 20:08:41 2017 +0200
> 
> Update translations for using hdparm
> 
> Those changes should be done in d-i master po files

This should be disregarded and should not have been sent.  These are
translations I fetched from Launchpad, and they may have different
vocabulary standards etc.  d-i manages its own translations, and d-i
translators are unlikely to thank you for committing unchecked
translations to their languages.

If the underlying hdparm change were committed (but see below), then it
might make sense to send copies of the various translated strings to the
list as a courtesy so that translators could use them as a reference if
they wanted to, but not to commit them.

> commit 5f509c6af43f90f8800490ae87287d69678c5445
> Author: Colin Watson 
> Date:   Wed Apr 26 20:02:14 2017 +0200
> 
> Optionally set CD-ROM drive parameters with hdparm

I have mixed feelings about this.  It's a low-priority question,
probably of pretty limited use nowadays as apparently nobody ever
thought to enable it on amd64, and I suspect it's largely unused.  It
made some difference in 2004 but now it's 2017.  My inclination would be
to just drop this from Ubuntu, which would substantially reduce the size
of our delta.

> commit c061fc52c2b5ff1dc2f720df7dc795d0e0b121a9
> Author: Colin Watson 
> Date:   Wed Apr 26 19:10:44 2017 +0200
> 
> Extend device-scan delay to wait for usb-partition and mmc-partition
> 
> commit 2ea63bb2703436cfa7695fe27ce5042d1eaf67fd
> Author: Loïc Minier 
> Date:   Wed Apr 26 19:08:40 2017 +0200
> 
> Also check SD/MMC partitions ("list-devices mmc-partition")
> 
> Closes: LP: #364604

These rely (in part in the case of c061fc52, and in its entirety in the
case of 2ea63bb2) on a change to debian-installer-utils, which you
haven't forwarded.

> commit 5414150bde29d7f1432ae91eeb62c5dad8e0e3a2
> Author: Colin Watson 
> Date:   Wed Apr 26 18:37:29 2017 +0200
> 
> Copy /cdrom/.disk/info to /var/log/media-info
> 
> in order that we get /var/log/installer/media-info on the installed
> system; doing this in save-logs is too late because /cdrom is already
> unmounted by that point.
> 
> Closes: LP: #364649

This is probably vaguely reasonable.

-- 
Colin Watson   [cjwat...@ubuntu.com]

Bug#861313: kernel BUG with kvm

[Ben Hutchings]

On Sat, 2017-04-29 at 19:28 +0200, I. Schrey wrote:
> Greetings,
> 
> I'm having a similar issue on a kvm hypervisor running Debian Jessie.
> 
> It is running a vanilla kernel though, but it started hitting
> a similar BUG today, after I upgraded from 3.12 to 3.16 series.
> 
> 3.16.42 seems to be the first affected version.
> 3.16.41 is working without problems so far.
> 
> 
> Also I can confirm that Debian kernel 3.16.39-1+deb8u2 works
> and 3.16.43-1 does have the issue described.
> 
> 
> I might try and git bisect the kernel, today or tomorrow,
> unless someone else beats me to it.
[...]

Thanks for this information.  I can reproduce the regression and am now
doing the bisection.

Ben.

-- 
Ben Hutchings
This sentence contradicts itself - no actually it doesn't.



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

Bug#861518: libc6-dev: The newest libc6-dev (2.24-10) badly depends on kernel, particularly linux-libc-dev (>= 4.9.18-1)

[Laci Tele]

Package: libc6-dev
Version: 2.24-10
Severity: important

Dear Maintainer,


   * What led up to the situation?
   
I tried to install libc6-dev on my armhf embedded hardware.
Its not possible, because dependencies are not met.
Because the newest libc6-dev depends particularly on linux-kernel 
(>= 4.9.18-1), and this is an error, at least I hope its not intentional.
Because many embedded armhf devices use older kernels, 4.1 , 4.4 ... so on
, it depends on BSP what you can get from the HW vendor. Usually they have no 
4.9 or any near to mainline kernel.
So they have no linux-libc-dev (>= 4.9.18-1)
So they cant install libc6-dev (2.24-10)
So actually they can't develop.

Earlier libc6-dev (<=2.24-9) depended only on linux-libc-dev (without version), 
so it was installable.


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

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

Versions of packages libc6-dev depends on:
ii  libc-dev-bin2.24-10
ii  libc6   2.24-10
ii  linux-libc-dev  4.9.18-1

libc6-dev recommends no packages.

Versions of packages libc6-dev suggests:
pn  glibc-doc 
ii  manpages-dev  4.10-2

-- no debconf information

Bug#861237: main-menu: Please show "Ubuntu installer ..." on ubuntu

[Colin Watson]

On Wed, Apr 26, 2017 at 01:59:37PM +0200, Balint Reczey wrote:
> Please show "Ubuntu installer ..." or the localized string when
> building the package for Ubuntu.
> Please find the attached patches solving this.

I don't think this is OK.  Patch files committed to native packages tend
to bitrot quite quickly because there's little in the way of tooling to
support them, so instead of a three-minute merge job (seriously, I've
done this a lot and with practice that's what it is) suddenly it's a
longer and much less predictable/automatable job of figuring out what's
gone wrong with the patch and fixing it up.  Not a great tradeoff.

It's also actively worse in the long run to have the Ubuntu translations
*added* to the Debian translations as you've done, rather than being
in-place modifications.  This means that Ubuntu translations will fail
to pick up corrections to the Debian translations: even in a string as
simple as this, that can and does happen.

> Maybe Debian could provide the localized strings.

I don't think that's a fair request to make of Debian translators, which
is why I never made it in over ten years of carrying forward this patch.

I'm not going to close this with my Ubuntu hat on, but I think that d-i
folks should decline this patch.  For the reasons given above, it's
worse for both Debian and Ubuntu.

-- 
Colin Watson   [cjwat...@ubuntu.com]

Bug#861513: [Letsencrypt-devel] Bug#861513: python-certbot: Missing dependency on python-ndg-httpsclient from jessie-backports

[Harlan Lieberman-Berg]

Hm.  Yes, that's true.  This is because the python-requests dependency
on python-ndg-httpsclient is only a Recommends, but the part of the
code that certbot depends on (the requests "security" extra) has a
hard dependency.

I'll add a patch to put it in our dependencies for now; because of the
freeze, it'll take several days or longer to make it into
jessie-backports and stretch.  I've also opened up a wishlist item
against python-requests to ship something that we can add a Depends on
to help prevent this in the future.  (That's bug #861517, if you want
to follow along at home.)

That being said... there's a sense these days that systems which don't
install Recommends' may be subject to breakage.  I know a lot of
support channels will simply refuse to help on systems without
recommends enabled, just because of the bizarre behavior that can
result.  I agree this case a Depends is certainly the right
designation, but... in general, hic sunt draconis.

Sincerely,

-- 
Harlan Lieberman-Berg
~hlieberman

Bug#861050: [pkg-gnupg-maint] Bug#861050: gnupg-agent: GPG_AGENT_INFO is not set according to /etc/X11/Xsession.d/90gpg-agent

[Daniel Kahn Gillmor]

On Fri 2017-04-28 18:09:52 +0200, Marek Straka wrote:
> I have adapted script /etc/X11/Xsession.d/90gpg-agent to:
>
> agent_sock=$(gpgconf --list-dirs agent-socket)
> export GPG_AGENT_INFO2=${agent_sock}:0:1
> if [ -n "$(gpgconf --list-options gpg-agent | \
>   awk -F: '/^enable-ssh-support:/{ print $10 }')" ]; then
> export SSH_AUTH_SOCK=$(gpgconf --list-dirs agent-ssh-socket)
> fi
>
> ...and after Xsession starts
>
> :~$ echo $GPG_AGENT_INFO2
> /run/user/1000/gnupg/S.gpg-agent:0:1

You seem to be saying that you're only changing GPG_AGENT_INFO to
GPG_AGENT_INFO2 and that works for you.  is that correct?

is anything unsetting GPG_AGENT_INFO anywhere in your startup scripts,
either in Xsession.d, or in your homedir?

   --dkg

Bug#841155: 841155 - Lynx browser: Typing utf-8 2-byte characters only diplays first

[Thomas Dickey]

On Sat, Apr 29, 2017 at 08:04:01AM -0400, Thomas Dickey wrote:

...hmm - too much cut/paste (I made code-changes for this one, since
there actually was a bug to report).

-- 
Thomas E. Dickey 
http://invisible-island.net
ftp://invisible-island.net


signature.asc
Description: Digital signature

Bug#861517: python-requests: add virtual package python3?-requests-security with added dependencies

[Harlan Lieberman-Berg]

Package: python-requests
Version: 2.12.4-1
Severity: wishlist

Dear Maintainer,

Python requests ships with a "security" extra that requires an enlarged set
of dependencies (with python-ndg-httpsclient being the current stone in my
metaphorical shoe).

It would be awesome if there was a virtual package that I could depend on
that would include not just python-requests, but also all the extra
dependencies that the extra needs.



Thoughts?
-- 
Harlan Lieberman-Berg
~hlieberman

Bug#861180: shc: infinite loop does not work properly

[Eriberto]

Hi,

2017-04-29 16:58 GMT-03:00 Eriberto :
> Hi,
>
> Searching inside Repology.org[1], I found a fork with a new upstream
> and new versions[2]. However, the newest version (3.9.3) has the same
> issue[3].
>
> Regards,
>
> Eriberto
>
> [1] https://repology.org/metapackage/shc/versions
> [2] https://github.com/neurobin/shc
> [3] https://github.com/neurobin/shc/issues/23


I did some tests and I have news. I downloaded the versions 3.8.6 and
3.8.7 from upstream homepage and I did a 'make' inside a Sid jail.
After this, I compiled a shell script. The script compiled by 3.8.6
version worked fine, but the script from 3.8.7 (and newer) fails
(infinite loop).

Cheers,

Eriberto

Bug#861516: release-notes: Emacs, GCC and Kernel version

[Hideki Yamane]

Package: release-notes
Severity: normal
Tags: patch

Dear Maintainer,

 Could you update version numbers in release note as below, please?

 - Emacs in stretch are both 24 and 25
 - GCC is 6.3, not 6.2
 - Linux kernel is 4.9 series


--- en/whats-new.dbk.orig   2017-04-30 08:37:02.018738923 +0900
+++ en/whats-new.dbk2017-04-30 08:42:07.547701243 +0900
@@ -250,8 +250,8 @@
 -->
   
Emacs
-   24
-   25
+   24.4
+   24.5 and 25.1
   
   
EximExim default 
e-mail server
@@ -266,7 +266,7 @@
   
GNU Compiler Collection as default 
compilerGCC
4.9
-   6.2
+   6.3
   
 

Bug#861515: src:node-grunt-contrib-copy: FTBFS on armhf i386: test failure: ✖ copy - timestamp_equal

[Adam Borowski]

Package: src:node-grunt-contrib-copy
Version: 1.0.0-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi!
I'm afraid your package fails to build on at least armhf and i386.

The test that fails is:
✖ copy - timestamp_equal

Architectures I've tested:
✖ armhf (native)
✖ armhf (arm64)
✔ armhf (qemu-user on amd64)
✔ amd64
✖ i386 (native)
✖ i386 (amd64)
✔ arm64 (native)
✔ arm64 (qemu-user on amd64)

It doesn't seem to be filesystem related: all but one were done on btrfs,
but that i386 machine uses ext4.  That machine also uses stretch's official
kernel; the rest are on current mainline.

It's 1.0.0-2, so the previous FTBFS (#860634) is apparently fixed (and the
error is different).


Meow!
-- System Information:
Debian Release: 9.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental')
Architecture: armhf (armv7l)

Kernel: Linux 4.11.0-rc7-00021-gc7b52626967a (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#861514: radicale: htpasswd authentication vulnerable to timing-based bruteforce attacks

[Jonas Smedegaard]

Package: radicale
Version: 2.0.0~rc1-1
Severity: grave
Tags: security patch
Justification: user security hole

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Upstream has issued a security release:

> Add a random timer to avoid timing oracles and simple bruteforce
> attacks when using the htpasswd authentication method.

Actual patch:

commit 190b1dd795f0c552a4992445a231da760211183b
Author: Guillaume Ayoub 
Date:   Wed Apr 19 14:02:51 2017 +0200

Random timer to avoid timing oracles and simple bruteforce attacks

Important note: this is a security fix.

diff --git a/radicale/auth/htpasswd.py b/radicale/auth/htpasswd.py
index 2c73f23..7cd7342 100644
- --- a/radicale/auth/htpasswd.py
+++ b/radicale/auth/htpasswd.py
@@ -56,7 +56,8 @@ following significantly more secure schemes are parsable by 
Radicale:
 import base64
 import hashlib
 import os
- -
+import random
+import time
 
 from .. import config
 
@@ -161,7 +162,10 @@ def is_authenticated(user, password):
 if strippedline:
 login, hash_value = strippedline.split(":")
 if login == user:
- -# Allow encryption method to be overridden at runtime.
- -return _verifuncs[ENCRYPTION](hash_value, password)
+if _verifuncs[ENCRYPTION](hash_value, password):
+# Allow encryption method to be overridden at runtime.
+return True
+# Random timer to avoid timing oracles and simple bruteforce attacks
+time.sleep(1 + random.random())
 return False
 


 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlkFFlgACgkQLHwxRsGg
ASGQqQ//R1opffxilx3a60NOJffpD/2LCp0jecAd2hVeeTIwI8BcwEg4nY8jpCXo
6z7Y2ay758etRyJ54Jwga53PKqijHFrtLhL+oUyPebtMfWqtoR5cZhTvD9IC4GFP
bqK4ZVsop9lyvjD9+TdGAAL3/4FsQnYJctYvbWoTcSr+BcAvgmSgarxGiCr/jw2Z
iCMSi/0bcBoG4j19BrrAydP/l06yC5t8Mee3UmpswTNL3bTVqXN/zT81koy9m08a
1R9bKcggwQCQNtYXXtKkS545NuXdePpAoCo4ss67GjgwQoEua+GIMbR0KOLsGQoy
Fg7Nlc/a/UzZLy1OZgLSOV6Y5QvJHcNJY1hTGiKihgLI4uUso+wJbTMvrJhxlrQ3
IgzgKFqnySwLkxkXlA12pJK5pQL3kfxwXwf9otgOfsXcod9eMwuweLC088y3KXxN
ooNSxiJsFPoUU1C4oNczA/W+/O0EIZcYu4E9H9F9pR1SC3/YXylPySOUo6kVTRzf
Ggi+gSJE6pg5QmKLUqTV44RARSwaUbH8jVaS1SPZWIa+fzzbcIZmBF3ZKfA17ddk
k1bHHkVDtsQs7vn7l4ahQHR0izkciU8VkkUL3AFvtIv8PvhJtxpWihc8ewLVfoyC
Aej4omZuxTT3kXbO4aAkzeuKnsyTa20CRHNE6MHQUCVEHw6cN4U=
=HguT
-END PGP SIGNATURE-

Bug#861495: plasma-discover: recommend apt-config-auto-update instead of software-properties-kde

[Matthias Klumpp]

2017-04-30 0:16 GMT+02:00 Francesco De Vita :
> On 29/04/17 20:23:58 CEST, Matthias Klumpp wrote:
>> The apt-config-auto-update package enables automatic periodic cache
>> updates on systems that *do not* use PackageKit. For systems where
>> PackageKit is installed, the PK frontend uses PackageKit to request
>> update information.
>
> About the package cache, isn't it in common between apt and PackageKit based
> tools? If I issue an "apt update" I see that discover sees the updated cache.
> If so, I don't see why not use apt-config-auto-update, it provides a useful
> feature that I think many users expect by default.

PackageKit aleady updates the cache periodically, there is no point in
having another tool trying to do the same in the background. The only
thing that this might end in is two things fighting over the APT
database lock in the background, which is undesired.

>> The software-properties-kde application allows configuring the update
>> interval (does nothing here...) but also allows people to edit the
>> software sources installed on the system. It's basically a GUI editor
>> for /etc/apt/sources.list. And that is the reason why Discover depends
>> on it.
>
> But plasma-discover already has this feature, I can edit my sources.list with
> it and without software-properties-kde being installed.

You can only remove sources, not edit them or add new ones.

>> Granted, software-properties-kde has quite some flaws [...]
>> Regardless of that, having it brings enough benefit to the users that
>> it is included here. [...]
>> The periodic updates / automatic updates function in software-properties-kde
>> is broken if you use Discover, but its other functions warrant its inclusion
>> still.
>
> What benefits if I may ask? The sources.list can be edited already in
> plasma-discover without s-p-kde,

You can only remove sources, you can't add or edit them or look at
which GPG keys ou have installed for them on your system. You can also
not enable/disable backports or updates via a simple click.


> the periodic updates are broken if I use
> discover as you say

No, they work just fine. I didn't say that.

> and what remains is the possibility to choose if
> automatically install security updates (but I suppose unattended-upgrades does
> exactly that) or download all the updates in background or just notify about
> it.

These are exactly the features that might be broken, as they rely on
other tools and s-p-kde doesn't interface well with PackageKit.
Everything else works.

Cheers,
Matthias

-- 
Debian Developer | Freedesktop-Developer
I welcome VSRE emails. See http://vsre.info/

Bug#861495: plasma-discover: recommend apt-config-auto-update instead of software-properties-kde

[Francesco De Vita]

On 29/04/17 20:23:58 CEST, Matthias Klumpp wrote:
> The apt-config-auto-update package enables automatic periodic cache
> updates on systems that *do not* use PackageKit. For systems where
> PackageKit is installed, the PK frontend uses PackageKit to request
> update information.

About the package cache, isn't it in common between apt and PackageKit based 
tools? If I issue an "apt update" I see that discover sees the updated cache. 
If so, I don't see why not use apt-config-auto-update, it provides a useful 
feature that I think many users expect by default.

> The software-properties-kde application allows configuring the update
> interval (does nothing here...) but also allows people to edit the
> software sources installed on the system. It's basically a GUI editor
> for /etc/apt/sources.list. And that is the reason why Discover depends
> on it.

But plasma-discover already has this feature, I can edit my sources.list with 
it and without software-properties-kde being installed.

> Granted, software-properties-kde has quite some flaws [...]
> Regardless of that, having it brings enough benefit to the users that
> it is included here. [...]
> The periodic updates / automatic updates function in software-properties-kde
> is broken if you use Discover, but its other functions warrant its inclusion
> still.

What benefits if I may ask? The sources.list can be edited already in
plasma-discover without s-p-kde, the periodic updates are broken if I use 
discover as you say, and what remains is the possibility to choose if 
automatically install security updates (but I suppose unattended-upgrades does 
exactly that) or download all the updates in background or just notify about 
it.

Thank you.

Regards
Francesco

Bug#861415: virtualbox: Virtualbox 5.1.20: No audio devices could be opened. Error ID: HostAudioNotResponding.

[Gianfranco Costamagna]

control: fixed -1 5.1.22-dfsg-1
control: close -1

>After the last virtualbox update (version  5.1.22-dfsg-1),
>the application starts normally with working audio.
>You can close this bug as it was also solved upstream:


wonderful, closing then!

thanks for checking

G.

Bug#859475: jessie-pu: package ndisc6/1.0.1-1+deb8u1

[Bernhard Schmidt]

On Fri, Apr 28, 2017 at 05:45:17PM +0100, Adam D. Barratt wrote:

Hi Adam,

> On Tue, 2017-04-04 at 00:40 +0200, Bernhard Schmidt wrote:
> > the package rdnssd (from src:ndisc6) provides a daemon that listens to IPv6 
> > RA
> > messages containing RDNSS (recursive DNS servers) information, and adds this
> > information to /etc/resolv.conf. It is automatically installed by d-i if 
> > this
> > information is found during installation.
> > 
> > If resolvconf is installed managing and merging of /etc/resolv.conf is 
> > handed
> > over to it. However, if it is not installed the version in Jessie simply
> > overwrites /etc/resolv.conf, which drops all search list information as 
> > well as
> > IPv4 nameservers. This often leads to severe breakage of the installed 
> > system.
> > This is tracked in Bug#767071
> > 
> > The proposed fix for Jessie will adjust the merge script to be the same as 
> > in
> > current upstream and Stretch.
> 
> Please go ahead, bearing in mind that the window for the 8.8 point
> release closes during the weekend.

Thanks, uploaded and accepted.

Regards,
Bernhard


signature.asc
Description: Digital signature

Bug#860898: [Tts-project] Bug#860898: (no subject)

[Luke Yelavich]

On Sun, Apr 30, 2017 at 12:25:39AM AEST, Samuel Thibault wrote:
> Well, AIUI this has been broken for a long time without being reported.
> And thus AIUI people just configure speech-dispatcher with the config
> files and don't use spd-conf. Again, this is just my understanding, I'm
> not a user of speech-dispatcher, so users should say so if it's really a
> problem.

Speech Dispatcher should also just work with the default config. If it 
doesn't, then we should tweak the defaults so that it does. I think people 
are just used to using spd-conf from when it may have been more of a hard 
requirement in the past.

Luke

Bug#860970: [debian-mysql] FWD [Re: Bug#860970: release-notes: MariaDB vs MySQL section 2.2.3 needs clarifying on how to perform the upgrade]

[Ondřej Surý]

You don't have to run apt-get upgrade first. Just running apt install 
default-mysql-server should do the job.



On 29 April 2017 22:30:40 Paul Gevers  wrote:


Hi,

As a starter, I have been mixing 'apt-get update' and 'apt-get upgrade'
in my previous e-mails. Of course one always runs 'apt-get update'
before anything, I always meant 'apt(-get) upgrade' where 'update' is
mentioned. The release-notes propose to upgrade in two steps, first with
apt-get upgrade and then apt-get dist-upgrade. @Otto, did you also mean
the two step when you talked about "The upgrade has been
designed to work correctly by simply running 'apt-get update' and
'apt-get dist-upgrade'" or did you really mean upgrading in one step?

On 29-04-17 21:38, Ondřej Surý wrote:

Andreas,

I believe that your observation is in fact correct and the `apt-get
dist-upgrade` path will not upgrade mysql-5.5 to mariadb-10.1 if no
other package depends on default-mysql-server.

I had this conversation with Robbie when default-mysql-server was
introduced, and I argued that it would be much simpler to reuse the
original mysql-server name, but I wasn't able to convince him that
'mysql-server' should install mariadb-server-10.1, and there's a grain
of truth that people might expect to have Oracle's MySQL server
installed when they install 'mysql-server' package, so I stopped
pursuing the matter.

I don't think there's a better way how to approach the issue than in the
release note so deep in the freeze.


Ack.


What we could do (with the blessing of the release team) - is to
introduce the default-mysql-server into the jessie where it would just
simply mimic the existing setup, e.g. default-mysql-server would depend
on mysql-server and default-mysql-client would depend on mysql-client.
People could be then recommended to install default-mysql-server and
default-mysql-client prior to jessie->stretch upgrade, and in turn
having a smooth upgrade experience because mariadb-server-10.1 would
then installed during apt-get dist-upgrade step.


Sounds like a plan. But still, would my proposal for the text in the
release-notes not achieving nearly this without changes required in
jessie? My proposal being: run apt-get upgrade, apt-get install
default-mysql-server, apt-get dist-upgrade. I must admit I haven't
tested this and there may be issues I don't see.

Paul




--
___
pkg-mysql-maint mailing list
pkg-mysql-ma...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint

Bug#861480: ImportError: No module named QtWebKit

[Michal Čihař]

Hi

Dejan Muhamedagic píše v So 29. 04. 2017 v 22:21 +0200:
> On Sat, Apr 29, 2017 at 05:58:58PM +0200, Michal Čihař wrote:
> > 
> > Apparently this has been broken for almost year, since following
> > bug
> > has been fixed:
> > 
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784513
> 
> I see.
> 
> > As there is no active upstream and I don't have time to port this
> > to
> > qt5, the only reasonable way is probably to remove this package.
> 
> To the best of my knowledge there is no other software supporting
> S60. Or not in the way that this package does. I have no
> experience with webkit, but will take a look at porting.

Gammu/Wammu should work as well [1], though the GUI is probably not
that nice.

[1]:https://wammu.eu/docs/manual/protocol/s60.html

-- 
Michal Čihař | https://cihar.com/ | https://weblate.org/


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

Bug#861474: slim: Session restarts in a loop renedering whole system useless.

[HJ]

I have exact the same issue with the new version, I also reinstalled the
lenny *-4 version - no restarts anymore.

Bug#860805: [Pkg-opencl-devel] Bug#860805: beignet-opencl-icd: OpenCL fails with: drm_intel_gem_bo_context_exec() failed: Device or resource busy

[Andreas Beckmann]

On 2017-04-29 13:43, Rebecca N. Palmer wrote:
>> Depends: beignet-opencl-icd|mesa-opencl-icd|opencl-icd
> 
> I'd suggest just Depends: opencl-icd, as which one will actually work is
> hardware dependent.

Nope, opencl-icd should *never* occur as the first alternative, since it
could pull in a non-free ICD (and corresponding non-free driver etc.).

I vaguely remember we had discussions about providing some
meta-packages, but I don't think anything was ever implemented.
We should pick this up again for buster :-)


Andreas

Bug#851359: diffoscope: Improve support for comparing images

[Chris Lamb]

tags 851359 + pending
thanks

Chris Lamb wrote:

> Looks great, please go ahead and rebase onto the experimental
> branch :)

Looks pushed and the tests are passing, so marking as `pending`. Thanks
again!


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#829143: Acknowledgement (python-demgengeo: FTBFS on hppa and others - error: cannot find the flags to link with Boost system)

[John David Anglin]

The attached change fixes the FTBFS.  Please add hppa directories to possible 
paths.

Dave
--
John David Anglin   dave.ang...@bell.net


--- ./m4/boost.m4.save  2017-04-29 13:10:31.371082667 -0400
+++ ./m4/boost.m4   2017-04-29 13:14:33.212306455 -0400
@@ -484,17 +484,17 @@
   possible_paths="${with_boost}/lib ${with_boost}"
 else
   possible_paths="${boost_cv_inc_path%/include}/lib \
-/usr/lib*/x86_64* /usr/lib*/i386* /usr/lib*/aarch64* /usr/lib*/arm* 
/usr/lib*/mips* \
+/usr/lib*/x86_64* /usr/lib*/i386* /usr/lib*/aarch64* /usr/lib*/arm* 
/usr/lib*/hppa* /usr/lib*/mips* \
   /usr/lib*/powerpc* /usr/lib*/ppc64* /usr/lib*/s390* /usr/lib*/sh4* 
/usr/lib*/sparc* /usr/lib* \
 /usr/local/lib*/x86_64* /usr/local/lib*/i386* /usr/local/lib*/aarch64* 
/usr/local/lib*/arm* \
-  /usr/local/lib*/mips* /usr/local/lib*/powerpc* 
/usr/local/lib*/ppc64* /usr/local/lib*/s390* \
+  /usr/local/lib*/hppa* /usr/local/lib*/mips* /usr/local/lib*/powerpc* 
/usr/local/lib*/ppc64* /usr/local/lib*/s390* \
   /usr/local/lib*/sh4* /usr/local/lib*/sparc* /usr/local/lib* \
-/opt/lib*/x86_64* /opt/lib*/i386* /opt/lib*/aarch64* /opt/lib*/arm* 
/opt/lib*/mips* \
+/opt/lib*/x86_64* /opt/lib*/i386* /opt/lib*/aarch64* /opt/lib*/arm* 
/opt/lib*/hppa* /opt/lib*/mips* \
   /opt/lib*/powerpc* /opt/lib*/ppc64* /opt/lib*/s390* /opt/lib*/sh4* 
/opt/lib*/sparc* /opt/lib* \
 /opt/local/lib*/x86_64* /opt/local/lib*/i386* /opt/local/lib*/aarch64* 
/opt/local/lib*/arm* \
-  /opt/local/lib*/mips* /opt/local/lib*/powerpc* 
/opt/local/lib*/ppc64* /opt/local/lib*/s390* \
+  /opt/local/lib*/hppa* /opt/local/lib*/mips* /opt/local/lib*/powerpc* 
/opt/local/lib*/ppc64* /opt/local/lib*/s390* \
   /opt/local/lib*/sh4* /opt/local/lib*/sparc* /opt/local/lib* \
-/lib*/x86_64* /lib*/i386* /lib*/aarch64* /lib*/arm* /lib*/mips* \
+/lib*/x86_64* /lib*/i386* /lib*/aarch64* /lib*/arm* /lib*/hppa* 
/lib*/mips* \
   /lib*/powerpc* /lib*/ppc64* /lib*/s390* /lib*/sh4* /lib*/sparc* 
/lib* \
 C:/Boost/lib"
 fi

Bug#861513: python-certbot: Missing dependency on python-ndg-httpsclient from jessie-backports

[John Morahan]

Package: python-certbot
Version: 0.10.2-1~bpo8+1
Severity: important

Dear Maintainer,

Some certbot users reported errors after installing from jessie-backports:

$ certbot --help
Traceback (most recent call last):
  File "/usr/bin/certbot", line 6, in 
from pkg_resources import load_entry_point
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3019, 
in 
@_call_aside
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3003, 
in _call_aside
f(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3032, 
in _initialize_master_working_set
working_set = WorkingSet._build_master()
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 655, 
in _build_master
ws.require(__requires__)
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 963, 
in require
needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 849, 
in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'ndg-httpsclient; extra == "security"' 
distribution was not found and is required by requests

I noticed that python-requests recommends python-ndg-httpsclient but neither
it nor any certbot package explicitly depends on it. However certbot appears
to be completely unusable without it.
I was able to reproduce these errors by installing with:
sudo apt install certbot -t jessie-backports --no-install-recommends

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

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

Versions of packages python-certbot depends on:
ii  python-acme0.10.2-1~bpo8+1
ii  python-configargparse  0.11.0-1~bpo8+1
ii  python-configobj   5.0.6-1
ii  python-cryptography1.3.4-1~bpo8+2
ii  python-mock1.0.1-3
ii  python-openssl 16.0.0-1~bpo8+1
ii  python-parsedatetime   1.4-1
ii  python-requests2.11.1-1~bpo8+1
ii  python-rfc3339 1.0-4~bpo8+1
ii  python-setuptools  33.1.1-1~bpo8+1
ii  python-six 1.8.0-1
ii  python-tz  2012c+dfsg-0.1
ii  python-zope.component  4.2.1-2
ii  python-zope.interface  4.1.1-3.1
pn  python:any 

Versions of packages python-certbot recommends:
ii  certbot0.10.2-1~bpo8+1
pn  python-psutil  

Versions of packages python-certbot suggests:
pn  python-certbot-doc  

-- no debconf information

Bug#861507: Pending fixes for bugs in the libatteanx-endpoint-perl package

[pkg-perl-maintainers]

tag 861507 + pending
thanks

Some bugs in the libatteanx-endpoint-perl package are closed in
revision 4b142b3d0b41e30f119aae3dedcdd6770fca2ef0 in branch 'master'
by Jonas Smedegaard

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libatteanx-endpoint-perl.git/commit/?id=4b142b3

Commit message:

Fix broken symlink. Closes: Bug#861507. Thanks to Andreas Beckmann.

Bug#860970: [debian-mysql] FWD [Re: Bug#860970: release-notes: MariaDB vs MySQL section 2.2.3 needs clarifying on how to perform the upgrade]

[Paul Gevers]

Hi,

As a starter, I have been mixing 'apt-get update' and 'apt-get upgrade'
in my previous e-mails. Of course one always runs 'apt-get update'
before anything, I always meant 'apt(-get) upgrade' where 'update' is
mentioned. The release-notes propose to upgrade in two steps, first with
apt-get upgrade and then apt-get dist-upgrade. @Otto, did you also mean
the two step when you talked about "The upgrade has been
designed to work correctly by simply running 'apt-get update' and
'apt-get dist-upgrade'" or did you really mean upgrading in one step?

On 29-04-17 21:38, Ondřej Surý wrote:
> Andreas,
> 
> I believe that your observation is in fact correct and the `apt-get
> dist-upgrade` path will not upgrade mysql-5.5 to mariadb-10.1 if no
> other package depends on default-mysql-server.
> 
> I had this conversation with Robbie when default-mysql-server was
> introduced, and I argued that it would be much simpler to reuse the
> original mysql-server name, but I wasn't able to convince him that
> 'mysql-server' should install mariadb-server-10.1, and there's a grain
> of truth that people might expect to have Oracle's MySQL server
> installed when they install 'mysql-server' package, so I stopped
> pursuing the matter.
> 
> I don't think there's a better way how to approach the issue than in the
> release note so deep in the freeze.

Ack.

> What we could do (with the blessing of the release team) - is to
> introduce the default-mysql-server into the jessie where it would just
> simply mimic the existing setup, e.g. default-mysql-server would depend
> on mysql-server and default-mysql-client would depend on mysql-client.
> People could be then recommended to install default-mysql-server and
> default-mysql-client prior to jessie->stretch upgrade, and in turn
> having a smooth upgrade experience because mariadb-server-10.1 would
> then installed during apt-get dist-upgrade step.

Sounds like a plan. But still, would my proposal for the text in the
release-notes not achieving nearly this without changes required in
jessie? My proposal being: run apt-get upgrade, apt-get install
default-mysql-server, apt-get dist-upgrade. I must admit I haven't
tested this and there may be issues I don't see.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#861511: mysql-connector-python: CVE-2017-3590

[Salvatore Bonaccorso]

Source: mysql-connector-python
Version: 2.1.5-1
Severity: important
Tags: upstream security

Hi,

the following vulnerability was published for mysql-connector-python.

CVE-2017-3590[0]:
| Vulnerability in the MySQL Connectors component of Oracle MySQL
| (subcomponent: Connector/Python). Supported versions that are affected
| are 2.1.5 and earlier. Easily "exploitable" vulnerability allows low
| privileged attacker with logon to the infrastructure where MySQL
| Connectors executes to compromise MySQL Connectors. Successful attacks
| of this vulnerability can result in unauthorized update, insert or
| delete access to some of MySQL Connectors accessible data. CVSS 3.0
| Base Score 3.3 (Integrity impacts). CVSS Vector:
| (CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N).

According to the Oracle advisory fixed in 2.1.6.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-3590
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3590
[1] http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#861480: ImportError: No module named QtWebKit

[Dejan Muhamedagic]

On Sat, Apr 29, 2017 at 05:58:58PM +0200, Michal Čihař wrote:
> 
> Apparently this has been broken for almost year, since following bug
> has been fixed:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784513

I see.

> As there is no active upstream and I don't have time to port this to
> qt5, the only reasonable way is probably to remove this package.

To the best of my knowledge there is no other software supporting
S60. Or not in the way that this package does. I have no
experience with webkit, but will take a look at porting.

Bug#860691: Pending fixes for bugs in the jnr-posix package

[pkg-java-maintainers]

tag 860691 + pending
thanks

Some bugs in the jnr-posix package are closed in revision
1bf135f9a7562dd646a3c8bdfe98f67a4bbfd743 in branch 'master' by Markus
Koschany

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/jnr-posix.git/commit/?id=1bf135f

Commit message:

Import Debian changes 3.0.12-3

jnr-posix (3.0.12-3) unstable; urgency=medium

  * Team upload.
  * Ignore all test failures for now to prevent a build failure on i386 
which
upstream has not commented on yet. (Closes: #860691)

Bug#858996: jessie-pu: package mariadb-10.0/10.0.30-0+deb8u2

[Adam D. Barratt]

Control: tags -1 + confirmed

On Sat, 2017-04-29 at 22:00 +0200, Ondřej Surý wrote:
> Control: tags 858996 -moreinfo
> 
> JFTR mariadb-server-10.1 10.1.22-3 that contained the same change has
> migrade to testing on 2017-04-06 and nobody has complained since, so I
> am humbly asking for review of this change in jessie.

Please feel free to upload, but bear in mind that the window for 8.8 is
closing during this weekend.

Regards,

Adam

Bug#861492: [pkg-go] Bug#861492: hugo: New upstream versions of Hugo are available

[Dr. Tobias Quathamer]

Am 29.04.2017 um 18:46 schrieb Michael Berg:

Package: hugo
Version: 0.18.1-1+b2
Severity: wishlist

Dear Maintainer,

Debian unstable and testing currently package Hugo 0.18.1.

Hugo 0.19 through 0.20.6 have been released upstream since February.
https://github.com/spf13/hugo/releases

Given some of the bug fixes, new features, and optimizations,
it would be nice to have native Debian packages for a newer version.


Hi,

thanks for the bug report. Debian is currently frozen, in order to 
prepare a new release of the distribution.


When Debian is released, we'll upload a new version of hugo.

Regards,
Tobias




signature.asc
Description: OpenPGP digital signature

Bug#861510: unblock (pre-approval): systemd/232-23

[Michael Biebl]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Hi,

I'd like to make another upload of systemd.

An annotated debdiff follows. None of those changes touches udev, so
this should not affect debian-installer. That said, I've CCed KiBi for
his ack.

systemd (232-23) unstable; urgency=medium

  [ Michael Biebl ]
  * journal: fix up syslog facility when forwarding native messages.
Native journal messages (_TRANSPORT=journal) typically don't have a
syslog facility attached to it. As a result when forwarding the
messages to syslog they ended up with facility 0 (LOG_KERN).
Apply syslog_fixup_facility() so we use LOG_USER instead. (Closes: #837893)

https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=stretch=fc4d0e3e41dd0c22c4928a3265bd7cefd8074ef6

This is probably the bug with the widest impact, as it at least affects
all users of gdm/GNOME, where user log messages end up in kern.log. I
would definitely like to see this fix in stretch.
This patch has already been applied to the package in experimental


  * nspawn: Support ephemeral boots from images (Closes: #858149)

https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=stretch=59b525375fe98618d7cd487c0e8d38f5472a52b4

This fix was requested by a user. It's a backport of a fix which is
already in v233 (experimental) and limited to systemd-nspawn, so has
very low regression potential.

  * Exclude test binaries from dh_shlibdeps.
The test binaries in libsystemd-dev require libsystemd-shared which is
shipped in the systemd package. Those test binaries are primarily meant
to be run via autopkgtest. As the libsystemd-dev package is not supposed
to depend on systemd, exclude the tests from dh_shlibdeps and instead
update the autopkgtest dependencies to pull in the systemd package.
(Closes: #859152)

https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=stretch=cf16a5ad620bfd9ab26e1a47d3e074e6286d3f90

I'm a bit unsure about this one and would like the input of the release
team. The proper fix for this bug report is to split of the tests into a
separate package. This has been done in experimental. But I assume it is
to late to do that for stretch. The test binaries require
libsystemd-shared, which is provided by systemd. By not enforcing the
installation of systemd, we potentially have a policy violation. That
said, those test binaries are primarily meant to be run via autopkgtest,
and debian/tests/control has been updated to explicitly pull in systemd.

So we can either
a/ do nothing, ie. keep the status quo, which probably makes the
sysvinit users unhappy
b/ split the tests into the systemd-tests package as done in
experimental
c/ apply the compromise to exclude the tests from dh_shlibdeps.

Please let me know what you'd prefer.


  [ Felipe Sateler ]
  * Backport patch to make inability to get OS version nonfatal in machinectl.
Otherwise machinectl list breaks when there are libvirt machines
(Closes: #849316)

https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=stretch=b396e05f2d451070c085e121230f693dcf1c2079

We decided to pull this patch into stretch, as otherwise the combination
of libvirt and machinectl would be broken. I expect libvirt/virt-manager
to become more popular during the life-time of stretch with virtualbox
being removed from stretch.

  [ Sjoerd Simons ]
  * init-functions: Only call daemon-reload when planning to redirect.
systemctl daemon-reload is a quite a heavy operation, it will re-parse
all configuration and re-run all generators. This should only be done
when strictly needed. (Closes: #861158)

https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=stretch=57439b82c28e684faaec7773ea54eb3acd97ab1c

We were calling daemon-reload a bit too aggressively unnecessarily which
could lead to nasty side-effects, like in #861157. The change is
straightforward.


Please let me know if I can proceed with the upload.

Regards,
Michael

unblock systemd/232-23

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

Kernel: Linux 4.9.0-2-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)
diff --git a/debian/changelog b/debian/changelog
index 4af7f8a..2c670e7 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,33 @@
+systemd (232-23) unstable; urgency=medium
+
+  [ Michael Biebl ]
+  * journal: fix up syslog facility when forwarding native messages.
+Native journal messages (_TRANSPORT=journal) typically don't have a
+syslog facility attached to it. As a result when forwarding the
+messages to syslog they ended up with facility 0 (LOG_KERN).
+Apply syslog_fixup_facility() so we use 

Bug#858996: jessie-pu: package mariadb-10.0/10.0.30-0+deb8u2

[Ondřej Surý]

Control: tags 858996 -moreinfo

JFTR mariadb-server-10.1 10.1.22-3 that contained the same change has
migrade to testing on 2017-04-06 and nobody has complained since, so I
am humbly asking for review of this change in jessie.

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver

On Wed, Mar 29, 2017, at 15:13, Ondřej Surý wrote:
> Hi Adam,
> 
> On Wed, Mar 29, 2017, at 14:59, Adam D. Barratt wrote:
> > Control: tags -1 + moreinfo
> > 
> > On 2017-03-29 13:03, Ondřej Surý wrote:
> > > in order to fix #858941 for mariadb-10.0 (and #852495 for mariadb-10.1)
> > > I did couple of changes to both mariadb-10.0 and mariadb-10.1 (I will
> > > fill unblock later).
> > 
> > It's not clear to me from looking at the BTS as to whether the relevant 
> > changes affect the packages in unstable and are already included there; 
> > please could you clarify?
> 
> The same changes have been included in mariadb-10.1_10.1.22-3, but these
> changes should only affect the upgrades between mariadb-10.0 to
> mariadb-10.1[*], and so in unstable they will get relevant only on
> update from mariadb-10.1 to mariadb-10.[23].
> 
> I will fill unblock later today (or this week) as I am trying to whip-up
> mariadb-10.1 to shape ready for release, there's more changes than this
> (mostly) related to fixing FTBFS on non-release archs.
> 
> > In any case, please could we have a debdiff of the proposed upload to 
> > jessie.
> 
> Sorry, my mistake - I prepared all the files to be attached and forgot
> to attach them. Attached all relevant files now.
> 
> * - probably from mysql-server-5.5 - I'll have to speak with Robbie to
> get the same change into mysql-server-5.5 package
> 
> Cheers,
> -- 
> Ondřej Surý 
> Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
> Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
> fast DNS(SEC) resolver
> Email had 4 attachments:
> + mariadb-10.0_10.0.30-0+deb8u2.debdiff
>   8k (application/octet-stream)
> + mariadb-10.0_10.0.30-0+deb8u2.dsc
>   3k (application/octet-stream)
> + mariadb-10.0_10.0.30-0+deb8u2.debian.tar.xz
>   260k (application/octet-stream)
> + mariadb-10.0_10.0.30-0+deb8u2_amd64.changes
>   8k (application/octet-stream)

Bug#861180: shc: infinite loop does not work properly

[Eriberto]

Hi,

Searching inside Repology.org[1], I found a fork with a new upstream
and new versions[2]. However, the newest version (3.9.3) has the same
issue[3].

Regards,

Eriberto

[1] https://repology.org/metapackage/shc/versions
[2] https://github.com/neurobin/shc
[3] https://github.com/neurobin/shc/issues/23

Bug#861508: zatacka: broken symlink: /usr/share/games/zatacka/font.ttf -> ../../fonts/truetype/ttf-dejavu/DejaVuSans.ttf

[Andreas Beckmann]

Package: zatacka
Version: 0.1.8-5
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m33.1s ERROR: FAIL: Broken symlinks:
  /usr/share/games/zatacka/font.ttf -> 
../../fonts/truetype/ttf-dejavu/DejaVuSans.ttf


Is zatacka missing a Depends/Recommends/Suggests: ttf-dejavu-core ?


cheers,

Andreas


zatacka_0.1.8-5+b3.log.gz
Description: application/gzip

Bug#861509: lintian: Please support 'devel' as an Ubuntu release

[Unit 193]

Package: lintian
Version: 2.5.50.1
Severity: normal

Dear Maintainer,

In Ubuntu, 'devel' is an alias to the current development release,
it would be nice if changes-file/known-dists reflected this.

diff --git a/vendors/ubuntu/main/data/changes-file/known-dists 
b/vendors/ubuntu/main/data/changes-file/known-dists
index bf8f163..70f7250 100644
--- a/vendors/ubuntu/main/data/changes-file/known-dists
+++ b/vendors/ubuntu/main/data/changes-file/known-dists
@@ -1,5 +1,8 @@
 # List of ubuntu distributions
 
+# Alias
+devel
+
 dapper
 hardy
 karmic

Bug#861507: libatteanx-endpoint-perl: broken symlink: /usr/share/perl5/auto/share/dist/AtteanX-Endpoint/endpoint/www/js/codemirror -> ../../../../../../../javascript/codemirror

[Andreas Beckmann]

Package: libatteanx-endpoint-perl
Version: 0.001-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

1m23.7s ERROR: FAIL: Broken symlinks:
  /usr/share/perl5/auto/share/dist/AtteanX-Endpoint/endpoint/www/js/codemirror 
-> ../../../../../../../javascript/codemirror


You are probably missing another level of .. (the target
currently evaluates to /usr/share/perl5/javascript/codemirror)


cheers,

Andreas


libatteanx-endpoint-perl_0.001-2.log.gz
Description: application/gzip

Bug#861506: liballjoynservices-dev-1504: broken symlinks: /usr/lib/x86_64-linux-gnu/liballjoyn_{time, config}.so -> liballjoyn_{time, config}.so.1504

[Andreas Beckmann]

Package: liballjoynservices-dev-1504
Version: 15.04-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m31.6s ERROR: FAIL: Broken symlinks:
  /usr/lib/x86_64-linux-gnu/liballjoyn_time.so -> liballjoyn_time.so.1504
  /usr/lib/x86_64-linux-gnu/liballjoyn_config.so -> liballjoyn_config.so.1504


liballjoyn_time.so.1504 and liballjoyn_config.so.1504
do not seem to be shipped in any package.


cheers,

Andreas


liballjoynservices-dev-1504_15.04-5.log.gz
Description: application/gzip

Bug#860254:

[Jonathon Delgado]

I would be most grateful if you could drop the perl dependency for stretch.

From: Kurt Roeckx 
Sent: 27 April 2017 19:32
To: Sebastian Andrzej Siewior
Cc: 860...@bugs.debian.org; Jonathon Delgado
Subject: Re: Bug#860254:
    
On Thu, Apr 27, 2017 at 09:25:33PM +0200, Sebastian Andrzej Siewior wrote:
> On 2017-04-27 18:18:50 [+0200], Kurt Roeckx wrote:
> > 
> > Yes, so perl-base should be find for c_rehash and CA.pl, but tsget
> > requires libwww-curl-perl and we already don't depend on it.
> 
> So what is that you are saying? We keep perl as is and add
> libwww-curl-perl (and if so is it RC and so testing metrial)?
> Or do we move tsget somehwere under docs/examples as .gz or split it
> into its package like openssl-perl or so? I can't find if it is used
> somewhere / by something. It is in a non-standard location (not under a
> bin directory).

I'm not suggesting to add libwww-curl-perl.

I'm not sure why we have things in /usr/lib/ssl/misc/, which
doesn't sound like a useful place to put things.

Note that there are actually manpages for them, so maybe we should
move them to /usr/bin/?

We should probaby get rid of the whole /usr/lib/ssl/

But I think we shouldn't change anything for stretch, except maybe
changing from perl to perl-base.

Bug#851262: jessie-pu: package transmissionrpc/0.11-1

[Adam D. Barratt]

Control: tags -1 + pending

On Sat, 2017-04-29 at 12:43 +0200, Ondrej Novy wrote:
> Hi,
> 
> 2017-04-28 18:57 GMT+02:00 Adam D. Barratt :
> I'm not really sure how that wasn't spotted earlier, but
> please go
> ahead. :-(
> 
> 
> np,

In case of any doubt, I meant why the bug in transmissionrpc wasn't
spotted earlier, not why the p-u request wasn't...

>  uploaded.

Flagged for acceptance.

Regards,

Adam

Bug#859262: Re: freezes Orca screen reader

[Mika Hanhijärvi]

Hello




On 04/29/2017 09:42 PM, Paul Gevers wrote:

Hi Mika, Tim,

On 29-04-17 17:51, Joanmarie Diggs wrote:

And to prepare for fixes of the package in Debian (which is 3.22.2 and
will be extremely hard convince the release managers to update in this
stage due to the freeze), which fixes would we need to backport to fix
the issues identified so far?

commit ea02cc2d268348c22ffe8c23099f6b023d4c90a7
commit 382c5408afc7dd25f9b477a5e30c50ba917155c0
commit d51f87a7f000d099da98247dc7ca337b2b5483be
commit edbfafbd89409bfb1e4a4e3a9339c0b2de7435d6

I prepared and build¹ a Debian gnome-orca package with the above
mentioned upstream commits that should prevent Orca from freezing (or
appearing to do so). It would be great if you could install the deb²
(checksum below³) and report if it resolves your issues with Synaptic
(as my Orca installation isn't set-upped properly, I don't hear anything).

Paul

¹
http://debomatic-amd64.debian.net/distribution#testing/gnome-orca/3.22.2-3~debo1
²
http://debomatic-amd64.debian.net/debomatic/testing/pool/gnome-orca_3.22.2-3~debo1/gnome-orca_3.22.2-3~debo1_all.deb
³
paul@testavoira ~ $ sha256sum gnome-orca_3.22.2-3~debo1_all.deb
6d9c8bca6b211ac1570792dd66fde8a46cdf59a038b87a0d9bf16a43822e1887
gnome-orca_3.22.2-3~debo1_all.deb





Ok. I will try it now, thanks.

Bug#861505: jupyter-sphinx-theme-doc: broken symlink: /usr/share/doc/jupyter-sphinx-theme-doc/examples/demo/source/_themes/bootstrap -> ../../../bootstrap

[Andreas Beckmann]

Package: jupyter-sphinx-theme-doc
Version: 0.0.6+ds1-2
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

4m26.4s ERROR: FAIL: Broken symlinks:
  
/usr/share/doc/jupyter-sphinx-theme-doc/examples/demo/source/_themes/bootstrap 
-> ../../../bootstrap


The target /usr/share/doc/jupyter-sphinx-theme-doc/examples/bootstrap
does not seem to exist in any package in Debian sid.


cheers,

Andreas


jupyter-sphinx-theme-doc_0.0.6+ds1-2.log.gz
Description: application/gzip

Bug#857468: jessie-pu: package lxc/1:1.0.6-6+deb8u6

[Adam D. Barratt]

Control: tags -1 + pending

On Sat, 2017-04-29 at 09:38 +0200, Evgeni Golov wrote:
> On Sun, Mar 19, 2017 at 05:12:01PM +, Adam D. Barratt wrote:
> > Control: tags -1 + confirmed
> > 
> > On Sat, 2017-03-11 at 18:53 +0100, Evgeni Golov wrote:
> > > I would like to upload lxc/1:1.0.6-6+deb8u6 for Jessie and seek your 
> > > (pre-)approval.
> > > 
> > > The reason for the upload is to fix #857295 aka
> > >  CVE-2017-5985: lxc-user-nic didn't verify network namespace ownership
> > > The patch for that is straight from upstream's stable-1.0 branch.
> > 
> > Please go ahead.
> 
> And uploaded. Sorry for the delay, it somehow slipped my todo.

No worries. Flagged for acceptance.

Regards,

Adam

Bug#853965: jessie-pu: package installation-guide/20150423+deb8u3

[Adam D. Barratt]

Control: tags -1 + pending

On Sat, 2017-04-29 at 18:00 +0200, Samuel Thibault wrote:
> Hello,
> 
> Adam D. Barratt, on dim. 19 févr. 2017 20:35:11 +, wrote:
> > Control: tags -1 + confirmed
> > 
> > On Thu, 2017-02-02 at 15:36 +0100, Cyril Brulebois wrote:
> > > We're getting more reports from people failing to deal with syslinux
> > > settings for debian-installer; we've had a fix in the installation guide
> > > for quite a while but it wasn't propagated to jessie yet, meaning the
> > > website still has faulty instructions for jessie (4.3.3.2):
> > >   https://www.debian.org/releases/jessie/amd64/ch04s03.html.en
> > >   https://www.debian.org/releases/stretch/amd64/ch04s03.html.en
> > > 
> > > Samuel already cherry-picked the changes in the jessie branch, but that
> > > wasn't submitted yet. You'll find attached a quasi minimal patch against
> > > jessie (yay svn…). Changelog:
> > > | installation-guide (20150423+deb8u3) jessie; urgency=medium
> > > | 
> > > |   [ Matt Kraai ]
> > > |   * Fix Instructions for creating syslinux.cfg according to syslinux 
> > > 5.00
> > > | change. Closes: #803267.
> > 
> > Please go ahead.
> 
> I have now uploaded them, see attached debdiff.

Thanks, flagged for acceptance.

Regards,

Adam

Bug#861489: jessie-pu: package debian-edu-doc/1.6~20170429+deb8u4

[Adam D. Barratt]

Control: tags -1 + pending

On Sat, 2017-04-29 at 17:43 +0200, Holger Levsen wrote:
> Please accept debian-edu-doc/1.6~20170429+deb8u4 into the next Jessie point
> release, the update just contains documentation and translation updates.

Done.

Regards,

Adam

Bug#852040: jessie-pu: package ca-certificates/20141019+deb8u3

[Adam D. Barratt]

Control: tags -1 + pending

On Sat, 2017-04-29 at 01:27 +0200, Andreas Beckmann wrote:
> On 2017-04-28 18:53, Michael Shuler wrote:
> > On 04/28/2017 11:39 AM, Adam D. Barratt wrote:
> >> On Fri, 2017-04-28 at 00:58 +0200, Andreas Beckmann wrote:
> >>>
> >>> Attached is the combined debdiff of the commits backported by Michael
> >>> and me. I verified in piuparts that "running update-certificates without
> >>> hooks initially" now actually works as intended.
> >>
> >> That looks okay, thanks.
> >>
> >> Please feel free to upload, bearing in mind that the window for 8.8
> >> closes over the weekend.
> > 
> > Thank you so much. I'm sorry I've been ridiculously busy, and "I'll get
> > to it this weekend" repeatedly hasn't materialized for me.
> 
> Just built and uploaded.

Flagged for acceptance.

Regards,

Adam

Bug#861504: jsdoc-toolkit: broken symlink: /usr/share/jsdoc-toolkit/app/test/prototype.js -> ../../../javascript/prototype/prototype.js

[Andreas Beckmann]

Package: jsdoc-toolkit
Version: 2.4.0+dfsg-6.log.gz
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m52.7s ERROR: FAIL: Broken symlinks:
  /usr/share/jsdoc-toolkit/app/test/prototype.js -> 
../../../javascript/prototype/prototype.js


Is jsdoc-toolkit missing a Depends/Recommends/Suggests: libjs-prototype ?


cheers,

Andreas


jsdoc-toolkit_2.4.0+dfsg-6.log.gz
Description: application/gzip

Bug#861503: jing-trang-doc: broken symlink: /usr/share/doc/jing-trang-doc/doc/xhtml -> ../../../xml/xhtml-relaxng

[Andreas Beckmann]

Package: jing-trang-doc
Version: 20131210+dfsg+1-6
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m31.0s ERROR: FAIL: Broken symlinks:
  /usr/share/doc/jing-trang-doc/doc/xhtml -> ../../../xml/xhtml-relaxng


Is jing-trang-doc missing a Depends/Recommends/Suggests: xhtml-relaxng ?


cheers,

Andreas


jing-trang-doc_20131210+dfsg+1-6.log.gz
Description: application/gzip

Bug#779400: tracker.debian.org: add a patches panel

[Scott Kitterman]

On Sat, 29 Apr 2017 20:08:01 +0800 Paul Wise  wrote:
> On Sat, 28 Feb 2015 13:38:28 +0800 Paul Wise wrote:
> 
> > I would like to have a patches panel on the distro-tracker that might
> > look something like the attached mockup for Debian. The possible fields
> > of the Debian version of the panel are as follows, many of them can't be
> > implemented right now but are still interesting to mention for future
> > work once the services backing them exist.
> 
> I've created a patch for the PTS as a proof of concept, examples:
> 
> https://packages.qa.debian.org/~pabs/g/glibc.html
> https://packages.qa.debian.org/~pabs/n/nsis.html
> https://packages.qa.debian.org/~pabs/0/0x.html
> 
> Note that some changes are needed to external services to make it more
> useful, for example the debsources patches API (see 861379).
> 
> I did it with the PTS because XSLT was easier for me than Django, once
> it is implemented in the PTS it could be re-implemented for tracker.

I can see some utility in this, but think it should definitely be below bugs.

I suspect with django you'll be able to allow users to turn different sources 
on or off, so they can customize to taste (there's definitely more there than 
I'd care to see, but if I can set it up once and not worry about it, then I 
don't care).

Scott K

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

Bug#861502: intercal: broken symlink: /usr/share/doc/intercal/examples/lib -> ../../../../include/ick

[Andreas Beckmann]

Package: intercal
Version: 30:0.30-1
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m26.5s ERROR: FAIL: Broken symlinks:
  /usr/share/doc/intercal/examples/lib -> ../../../../include/ick


intercal ships some files in /usr/include/ick-0.29/, though.

Which sounds great for a package with version 0.30.
And there is /usr/share/ick-0.29, too.


cheers,

Andreas


intercal_30:0.30-1.log.gz
Description: application/gzip

Bug#859262: Re: freezes Orca screen reader

[Paul Gevers]

Samuel,

On 29-04-17 17:51, Joanmarie Diggs wrote:
> I believe I've already said this, but I'll say it again: Getting to the
> bottom of the Synaptic and/or AT-SPI problem(s) should be done.

Do you think we should clone/open a bug for atspi? If so, what severity
level (assuming we can get orca in shape to behave in the current case)?
I would think the answer to the first question is yes, and to the second
question normal (at least < RC if we can fix Orca).

Do you think we should get Synaptic to behave better? I.e. file a bug
there? If so, do we (you?) understand the issue well enough to describe
it properly?

Paul



signature.asc
Description: OpenPGP digital signature

Bug#861501: klog: broken symlink: /usr/share/doc/klog/html -> ../kde4/HTML/en/klog

[Andreas Beckmann]

Package: klog
Version: 0.9.2.5.1-2
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m51.0s ERROR: FAIL: Broken symlinks:
  /usr/share/doc/klog/html -> ../kde4/HTML/en/klog

The target /usr/share/doc/kde4/HTML/en/klog does not
exist in any package in the archive.


cheers,

Andreas


klog_0.9.2.5.1-2.log.gz
Description: application/gzip

Bug#861500: graphite-api: broken symlinks: /usr/share/doc/graphite-api/html/_static/*/* -> ../../../../../sphinx_rtd_theme/static/*/*

[Andreas Beckmann]

Package: graphite-api
Version: 1.1.3-2
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m58.3s ERROR: FAIL: Broken symlinks:
  /usr/share/doc/graphite-api/html/_static/js/theme.js -> 
../../../../../sphinx_rtd_theme/static/js/theme.js
  /usr/share/doc/graphite-api/html/_static/js/modernizr.min.js -> 
../../../../../sphinx_rtd_theme/static/js/modernizr.min.js
  /usr/share/doc/graphite-api/html/_static/fonts/fontawesome-webfont.woff -> 
../../../../../sphinx_rtd_theme/static/fonts/fontawesome-webfont.woff
  /usr/share/doc/graphite-api/html/_static/fonts/fontawesome-webfont.ttf -> 
../../../../../sphinx_rtd_theme/static/fonts/fontawesome-webfont.ttf
  /usr/share/doc/graphite-api/html/_static/fonts/fontawesome-webfont.svg -> 
../../../../../sphinx_rtd_theme/static/fonts/fontawesome-webfont.svg
  /usr/share/doc/graphite-api/html/_static/fonts/fontawesome-webfont.eot -> 
../../../../../sphinx_rtd_theme/static/fonts/fontawesome-webfont.eot
  /usr/share/doc/graphite-api/html/_static/fonts/RobotoSlab-Regular.ttf -> 
../../../../../sphinx_rtd_theme/static/fonts/RobotoSlab-Regular.ttf
  /usr/share/doc/graphite-api/html/_static/fonts/RobotoSlab-Bold.ttf -> 
../../../../../sphinx_rtd_theme/static/fonts/RobotoSlab-Bold.ttf
  /usr/share/doc/graphite-api/html/_static/fonts/Lato-Regular.ttf -> 
../../../../../sphinx_rtd_theme/static/fonts/Lato-Regular.ttf
  /usr/share/doc/graphite-api/html/_static/fonts/Lato-Bold.ttf -> 
../../../../../sphinx_rtd_theme/static/fonts/Lato-Bold.ttf
  /usr/share/doc/graphite-api/html/_static/fonts/Inconsolata-Regular.ttf -> 
../../../../../sphinx_rtd_theme/static/fonts/Inconsolata-Regular.ttf
  /usr/share/doc/graphite-api/html/_static/fonts/Inconsolata-Bold.ttf -> 
../../../../../sphinx_rtd_theme/static/fonts/Inconsolata-Bold.ttf
  /usr/share/doc/graphite-api/html/_static/css/theme.css -> 
../../../../../sphinx_rtd_theme/static/css/theme.css
  /usr/share/doc/graphite-api/html/_static/css/badge_only.css -> 
../../../../../sphinx_rtd_theme/static/css/badge_only.css


Is graphite-api missing a Depends/Recommends/Suggests: sphinx-rtd-theme-common ?


cheers,

Andreas


graphite-api_1.1.3-2.log.gz
Description: application/gzip

Bug#861030: gfsview: broken symlink: /usr/share/gfsview/fonts/Garuda.ttf -> ../../fonts/opentype/tlwg/Garuda.otf

[Andreas Beckmann]

Followup-For: Bug #861030
Control: found -1 20121130+dfsg-3

Hi,

you only updated the Build-Depends, but not the Depends.


Andreas

Bug#861387: fails to open applet menu

[Mika Hanhijärvi]

Hello
On 04/29/2017 06:35 PM, Scott Leggett wrote:

tags 861387 + moreinfo unreproducible
severity 861387 important
--

Hello Mika,

On 2017-04-28.13:17, Mika Hanhijärvi wrote:

Package: pasystray
Version: 0.6.0-1
Severity: grave

Hello

pasystray applet is visible in the Gnome's legacy icon tray but when I click
the  icon then applet menu does not open. This makes pasystray unusable,
atleast on Gnome, I do not know if the problem happens on other desktops too.


Thanks for the bug report.

I have tried to reproduce your issue by downloading the latest live-cd
of Strech with Gnome, and installing pasystray. As you can see in the
attached screenshot, the menu does work for me (both right-click and
left-click).

Could you provide any more information about your Gnome configuration
that is different from the default?

You could also try running `pasystray -d` in a terminal to print debug
information that may help figure out what's going on.

In the meantime, I have downgraded the severity of the bug as I cannot
reproduce it on a default Gnome desktop.





I can not see the screenshot because I am blind. If the pasystray menu 
opens then atleast it does not work with Orca screen reader. Note that I 
use the computer using keyboard whithout using mouse. Blind users like 
me can not use mouse. So  when I say that  i click the pasystray icon, I 
mean that I select the icon using left and right arrow keys from 
keyboard and then I click the icon using enter or space from keyboard.


When I click the pasystray icon Orca screen reader says something like 
"shshshsh" or something like that, but  the pasystray menu can not be 
accessed from keyboard. The menu may be accessible using mouse, but as I 
said I am blind and I can not use mouse.


I am using the Gnome desktop installed by Debian. This problem happens 
on both of my laptops running Debian Stretch. Both laptops have been 
upgraded from Jessie to Stretch  The only package that I have installed 
from outside of debian is Skype.


I have still the padevchooser installed, because pasystray does not 
work. I do not know if that could  cause problems. I would like to 
uninstall padevchooser because it is not in Debian anymore, but if If I 
uninstall it and pasystray does anot work then I have no Pulseaudio 
applet at all...


Here is how to reproduce this bug:

1) install Orca screen reader
2) activate Orca
3) go to Gnome desktop legacy icon tray by pressing  ctrl-alt-tab from 
keyboard
4) select the pasystray applet by using left and right arrow keys from 
keyboard

5( click the  pasystray by pressing enter or space from keyboard

Bug#861499: python-pygame-doc: broken symlink: /usr/share/doc/python-pygame-doc/examples/data/sans.ttf -> ../../../../fonts/truetype/freefont/FreeSansBold.ttf

[Andreas Beckmann]

Package: python-pygame-doc
Version: 1.9.3+dfsg-2
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m23.2s ERROR: FAIL: Broken symlinks:
  /usr/share/doc/python-pygame-doc/examples/data/sans.ttf -> 
../../../../fonts/truetype/freefont/FreeSansBold.ttf


Is python-pygame-doc missing a Depends/Recommends/Suggests: fonts-freefont-ttf ?


cheers,

Andreas


python-pygame-doc_1.9.3+dfsg-2.log.gz
Description: application/gzip

Bug#861498: python-skimage-doc: broken symlinks: /usr/share/doc/python-skimage-doc/html/_static/*/*.* -> ../../../../../twitter-bootstrap/files/*/*.*

[Andreas Beckmann]

Package: python-skimage-doc
Version: 0.12.3-9
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m31.2s ERROR: FAIL: Broken symlinks:
  /usr/share/doc/python-skimage-doc/html/_static/js/bootstrap.min.js -> 
../../../../../twitter-bootstrap/files/js/bootstrap.min.js
  /usr/share/doc/python-skimage-doc/html/_static/css/bootstrap.min.css -> 
../../../../../twitter-bootstrap/files/css/bootstrap.min.css
  /usr/share/doc/python-skimage-doc/html/_static/css/bootstrap-responsive.css 
-> ../../../../../twitter-bootstrap/files/css/bootstrap-responsive.css


Is python-skimage-doc missing a Depends/Recommends/Suggests: 
libjs-twitter-bootstrap ?


cheers,

Andreas


python-skimage-doc_0.12.3-9.log.gz
Description: application/gzip

Bug#859262: Re: freezes Orca screen reader

[Paul Gevers]

Hi Mika, Tim,

On 29-04-17 17:51, Joanmarie Diggs wrote:
>> And to prepare for fixes of the package in Debian (which is 3.22.2 and
>> will be extremely hard convince the release managers to update in this
>> stage due to the freeze), which fixes would we need to backport to fix
>> the issues identified so far?

> commit ea02cc2d268348c22ffe8c23099f6b023d4c90a7

> commit 382c5408afc7dd25f9b477a5e30c50ba917155c0

> commit d51f87a7f000d099da98247dc7ca337b2b5483be

> commit edbfafbd89409bfb1e4a4e3a9339c0b2de7435d6

I prepared and build¹ a Debian gnome-orca package with the above
mentioned upstream commits that should prevent Orca from freezing (or
appearing to do so). It would be great if you could install the deb²
(checksum below³) and report if it resolves your issues with Synaptic
(as my Orca installation isn't set-upped properly, I don't hear anything).

Paul

¹
http://debomatic-amd64.debian.net/distribution#testing/gnome-orca/3.22.2-3~debo1
²
http://debomatic-amd64.debian.net/debomatic/testing/pool/gnome-orca_3.22.2-3~debo1/gnome-orca_3.22.2-3~debo1_all.deb
³
paul@testavoira ~ $ sha256sum gnome-orca_3.22.2-3~debo1_all.deb
6d9c8bca6b211ac1570792dd66fde8a46cdf59a038b87a0d9bf16a43822e1887
gnome-orca_3.22.2-3~debo1_all.deb



signature.asc
Description: OpenPGP digital signature

Bug#851359: diffoscope: Improve support for comparing images

[Chris Lamb]

Hey Maria,

> […]

Looks great, please go ahead and rebase onto the experimental
branch :)

> >   a) We should rename this global variable to something that reflects
> >  this usage.

Thank for changing this. One thing I might fix up around here is that the
following code in main.py:

Config().compute_visual_diffs = any((
parsed_args.html_output,
parsed_args.html_output_directory,
))

.. violates the abstraction layer. I would probably do this by returning
splitting presenters.formats.output_all into two methods, one returning
the presenters we *plan* to execute later, and one then acting on that.
Or something.

That way, we can define something like "supports_visual_diffs" in the
FORMATS dictionary, and simply check for any existence of that instead.
No need to do this to merge , mostly braindumping for myself... :)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#861495: plasma-discover: recommend apt-config-auto-update instead of software-properties-kde

[Matthias Klumpp]

2017-04-29 19:40 GMT+02:00 Francesco De Vita :
> Package: plasma-discover
> Version: 5.8.5-3
> Severity: wishlist
>
> Dear Maintainer,
>
> plasma-discover recommends software-properties-kde, a package that allows via
> GUI to:
> - manage the entries in the sources.list
> - set periodic update and automatic upgrades
> - opt in/out from the popularity contest
>
> However the software-properties-* packages still have important and old bugs
> unresolved that undermine the user experience and, by default, do not enable
> automatic updates when installed.
>
> A better alternative could be the installation of plasma-discover with
> apt-config-auto-update instead, which provides "configuration snippets for the
> Apt package manager to have it automatically update its package cache".
>
> In this way:
> - the sources.list can still be managed using plasma-discover directly
> - automatic updates are enabled by default
>
> Despite the lack of a couple of features provided by software-properties-kde,
> this configuration could be better for a basic installation.

software-properties-kde and apt-config-auto-update do different things.

The apt-config-auto-update package enables automatic periodic cache
updates on systems that *do not* use PackageKit. For systems where
PackageKit is installed, the PK frontend uses PackageKit to request
update information. By doing that, downloads of updates or update
information can be avoided on a metered connection and generally be
planned better by the system.

The software-properties-kde application allows configuring the update
interval (does nothing here...) but also allows people to edit the
software sources installed on the system. It's basically a GUI editor
for /etc/apt/sources.list. And that is the reason why Discover depends
on it.

Granted, software-properties-kde has quite some flaws, some of them
are addressed at the moment, but in general this tool is
undermaintained in Debian, some help with updating it would be nice.
Regardless of that, having it brings enough benefit to the users that
it is included here.

tl;dr: To get automatic updates, you don't need apt-config-auto-update
at all as long as you have Discover installed. The periodic updates /
automatic updates function in software-properties-kde is broken if you
use Discover, but its other functions warrant its inclusion still.
Help to get s-p-kde to behave better would be appreciated.

Cheers,
   Matthias

-- 
Debian Developer | Freedesktop-Developer
I welcome VSRE emails. See http://vsre.info/

Bug#861037: [Pkg-swan-devel] Bug#861037: Bug#861037: Bug#861037: Bug#861037: Bug#861037: [PATCH 00/12] New upstream release 5.5.2

[Alex Hürter]

Thanks!

Best Regards

2017-04-29 19:45 GMT+02:00 Yves-Alexis Perez :

> On Sat, 2017-04-29 at 19:30 +0200, Alex Hürter wrote:
> > Could at least the plugins be enabled that are in the Strongswan
> > configuration
> > examples on the homepage (e.g. ntru and curve25519)?
>
> curve25519 is (will be) enabled, ntru see the PQ bug report.
>
> Regards,
> --
> Yves-Alexis
> ___
> Pkg-swan-devel mailing list
> pkg-swan-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-swan-devel
>



-- 
Alex Hürter
Cert. IT-Systems Manager

+49 2462 995 0537 (H)
+49 179  4503914 (M)
alex.huer...@gmx.net (gesch.)
shorty1...@googlemail.com  (privat)

Bug#176698: Verifique su correo electrónico

[WebAdmin]

Estimado usuario de correo electrónico,

Algunos de sus mensajes entrantes han sido suspendidos debido a la reciente 
actualización de nuestra base de datos. Para recibir mensajes, asegúrese de 
hacer clic en el enlace de abajo para actualizar su cuenta de correo 
electrónico. Si el clic no funciona, copie y pegue la URL a continuación en un 
navegador web para comprobarlo.

Haga clic aquí: http://goo.gl/aBDfRF

Pedimos disculpas por cualquier inconveniente y agradecemos su comprensión.

2017 © Gracias por el administrador del sistema
Número de registro 98708409H) Todos los derechos reservados

Bug#861497: gcc-6-cross: FTBFS in stretch

[Santiago Vila]

Package: src:gcc-6-cross
Version: 21
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
gcc: 6.3.0-14 / 6.3.0-12cross1

old gcc version: 6.3.0-12 / 1

new gcc version: 6.3.0-14cross1
START stamp-dir/init-gcc
mkdir -p gcc
set -ex; \
cd gcc ; \
ln -sf /usr/src/gcc-6/gcc-6.3.0.tar.xz gcc-6.3.0.tar.xz ;\
cp -a  /usr/src/gcc-6/debian/ . ; \
if [ -n "$(grep -v '^\#' /<>/debian/patches/gcc-6/series)" ]; then 
\
  QUILT_PATCHES=/<>/debian/patches/gcc-6 quilt push --quiltrc 
/dev/null -a ; \

[... snipped ...]

#define HAVE_DECL_ABORT 1
#define HAVE_DECL_ASPRINTF 1
#define HAVE_DECL_BASENAME 1
#define HAVE_DECL_ERRNO 0
#define HAVE_DECL_GETOPT 1
#define HAVE_DECL_VASPRINTF 1
#define HAVE_DECL_CLEARERR_UNLOCKED 1
#define HAVE_DECL_FEOF_UNLOCKED 1
#define HAVE_DECL_FERROR_UNLOCKED 1
#define HAVE_DECL_FFLUSH_UNLOCKED 1
#define HAVE_DECL_FGETC_UNLOCKED 1
#define HAVE_DECL_FGETS_UNLOCKED 1
#define HAVE_DECL_FILENO_UNLOCKED 1
#define HAVE_DECL_FPRINTF_UNLOCKED 0
#define HAVE_DECL_FPUTC_UNLOCKED 1
#define HAVE_DECL_FPUTS_UNLOCKED 1
#define HAVE_DECL_FREAD_UNLOCKED 1
#define HAVE_DECL_FWRITE_UNLOCKED 1
#define HAVE_DECL_GETCHAR_UNLOCKED 1
#define HAVE_DECL_GETC_UNLOCKED 1
#define HAVE_DECL_PUTCHAR_UNLOCKED 1
#define HAVE_DECL_PUTC_UNLOCKED 1
#define HAVE_ALLOCA_H 1
#define HAVE_ALLOCA 1
#define STDC_HEADERS 1
#define HAVE_LANGINFO_CODESET 1
#define ENABLE_NLS 1
#define HAVE_ICONV 1
#define ICONV_CONST 
#define PACKAGE "cpplib"
#define CHECKING_P 0
#define ENABLE_CANONICAL_SYSTEM_HEADERS 1

configure: exit 0
LOGFILE END /<>/gcc/build/libcpp/config.log
debian/rules2:1224: recipe for target 'stamps/05-build-stamp' failed
make[2]: *** [stamps/05-build-stamp] Error 1
make[2]: Leaving directory '/<>/gcc'
debian/rules:40: recipe for target 'build' failed
make[1]: *** [build] Error 2
make[1]: Leaving directory '/<>/gcc'
dpkg-buildpackage: error: debian/rules build gave error exit status 2
debian/rules:240: recipe for target 'stamp-dir/build-gcc.armhf' failed
make: *** [stamp-dir/build-gcc.armhf] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


This is just how the build ends, not necessarily the relevant part.

I've put the full build log here:

https://people.debian.org/~sanvila/build-logs/gcc-6-cross/

I've also triggered a rebuild (for testing/amd64) in the reproducible builds 
autobuilders and it also fails:

https://tests.reproducible-builds.org/debian/rb-pkg/testing/amd64/gcc-6-cross.html

Thanks.

Bug#859262: Re: freezes Orca screen reader

[Joanmarie Diggs]

On 04/29/2017 10:55 AM, Paul Gevers wrote:

> And to prepare for fixes of the package in Debian (which is 3.22.2 and
> will be extremely hard convince the release managers to update in this
> stage due to the freeze), which fixes would we need to backport to fix
> the issues identified so far?

-
commit ea02cc2d268348c22ffe8c23099f6b023d4c90a7
Author: Joanmarie Diggs 
Date:   Sat Apr 29 11:38:17 2017 -0400

Handle yet another Atspi "The process appears to be hung" exception

commit 382c5408afc7dd25f9b477a5e30c50ba917155c0
Author: Joanmarie Diggs 
Date:   Sat Apr 29 11:28:17 2017 -0400

Add check for dead accessibles before attempting to generate
presentation

commit d51f87a7f000d099da98247dc7ca337b2b5483be
Author: Joanmarie Diggs 
Date:   Fri Apr 28 15:35:39 2017 -0400

Handle another Atspi "The process appears to be hung" exception

commit edbfafbd89409bfb1e4a4e3a9339c0b2de7435d6
Author: Joanmarie Diggs 
Date:   Thu Apr 27 06:35:11 2017 -0400

Return immediately in isLayoutOnly() if obj is dead
-

Note that 382c540 may need to be reverted. Hopefully not. But rather
than playing endless whac-a-mole with Atspi errors resulting from
whatever it is Synaptic is doing, I am sanity checking much earlier on
in the process. There is the possibility that doing so will cause other
badly-behaved apps to not be presented. :-/

I've asked on the Orca list for testing, and we have enough users that
use master and respond quite quickly to calls for testing, that we
should know soon enough.

I believe I've already said this, but I'll say it again: Getting to the
bottom of the Synaptic and/or AT-SPI problem(s) should be done.
(Something I'm afraid I don't have time for. Sorry!)

--joanie

Bug#861037: [Pkg-swan-devel] Bug#861037: Bug#861037: Bug#861037: Bug#861037: [PATCH 00/12] New upstream release 5.5.2

[Yves-Alexis Perez]

On Sat, 2017-04-29 at 19:30 +0200, Alex Hürter wrote:
> Could at least the plugins be enabled that are in the Strongswan
> configuration
> examples on the homepage (e.g. ntru and curve25519)?

curve25519 is (will be) enabled, ntru see the PQ bug report.

Regards,
-- 
Yves-Alexis

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

Bug#861496: python-pysam: accesses network during build

[Santiago Vila]

Package: src:python-pysam
Version: 0.10.0+ds-1

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3 --buildsystem=pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py config 
# pysam: cython is available - using cythonize if necessary
# pysam: htslib mode is external
# pysam: HTSLIB_CONFIGURE_OPTIONS=None
running config
I: pybuild base:184: python3.5 setup.py config 
# pysam: cython is available - using cythonize if necessary
# pysam: htslib mode is external
# pysam: HTSLIB_CONFIGURE_OPTIONS=None

[... snipped ...]

testParsing (tabix_test.VCFFromVCFTest_3) ... ok
testConnecting (tabix_test.VCFFromVCFTest_4) ... ok
testParsing (tabix_test.VCFFromVCFTest_4) ... ok
testConnecting (tabix_test.VCFFromVCFTest_5) ... ok
testParsing (tabix_test.VCFFromVCFTest_5) ... ok
testConnecting (tabix_test.VCFFromVCFTest_6) ... ok
testParsing (tabix_test.VCFFromVCFTest_6) ... ok
testConnecting (tabix_test.VCFFromVCFTest_7) ... ok
testParsing (tabix_test.VCFFromVCFTest_7) ... ok
testConnecting (tabix_test.VCFFromVCFTest_8) ... ok
testParsing (tabix_test.VCFFromVCFTest_8) ... ok
testConnecting (tabix_test.VCFFromVCFTest_9) ... ok
testParsing (tabix_test.VCFFromVCFTest_9) ... ok
testConnecting (tabix_test.VCFFromVCFTest_issue85) ... ok
testParsing (tabix_test.VCFFromVCFTest_issue85) ... ok
testConnecting (tabix_test.VCFFromVCFTest_vcf_v42) ... ok
testParsing (tabix_test.VCFFromVCFTest_vcf_v42) ... ok
test_samtools_python.test_idxstats_parse_split_lines ... ok
test_samtools_python.test_bedcov_split_lines ... ok
test_samtools_python.test_idxstats_parse ... ok
test_samtools_python.test_bedcov ... ok

==
ERROR: testFTPView (faidx_test.TestRemoteFileFTP)
--
Traceback (most recent call last):
  File "/<>/python-pysam-0.10.0+ds/tests/faidx_test.py", line 229, in 
testFTPView
with pysam.Fastafile(self.url) as f:
  File "pysam/libcfaidx.pyx", line 114, in pysam.libcfaidx.FastaFile.__cinit__ 
(pysam/libcfaidx.c:2349)
  File "pysam/libcfaidx.pyx", line 155, in pysam.libcfaidx.FastaFile._open 
(pysam/libcfaidx.c:3205)
OSError: could not open file 
`ftp://ftp-trace.ncbi.nih.gov/1000genomes/ftp/technical/reference/GRCh38_reference_genome/GRCh38_full_analysis_set_plus_decoy_hla.fa`

--
Ran 918 tests in 1230.931s

FAILED (errors=1)
(0, 0)
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd 
/<>/python-pysam-0.10.0+ds/.pybuild/pythonX.Y_3.5/build; python3.5 -m 
nose 
dh_auto_test: pybuild --test -i python{version} -p 3.5 returned exit code 13
debian/rules:38: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>/python-pysam-0.10.0+ds'
debian/rules:32: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Maybe this usually works because the ftp server is usually up,
but in either case, packages must not try network access during build.

Thanks.

Bug#851359: diffoscope: Improve support for comparing images

[Maria Glukhova]

Hi Chris,

Thanks again for your guidance and help!


On 24.04.2017 19:13, Chris Lamb wrote:
> So, I think…
>
> if get_image_size(self.path) != get_image_size(other.path):
> raise AssertionError
>
> … are better written as:
>
> assert get_image_size(self.path) == get_image_size(other.path)
>
> Or at least it is more Pythonic…  However, we should definitely *not*
> be catching AssertionError like that for control flow, so either we need
> to raise a different exception or find some other way of doing this.

Yes, I was looking at assert, but specification around it being ignored
when -O option is passed to Python scared me off. Anyway, thanks for
pointing out that AssertionError should not be handled like that.
I moved the try/except for the image size and number of frames into the
corresponding functions and removed that AssertionError.

>   a) We should rename this global variable to something that reflects
>  this usage.

Thanks, renamed.

>   b) We could always just calculate the visual diffs and simply not
>  render them in the presenter backends that do not support them.
>  Are they remarkably slow, for example?

Well, enabling them makes comparing test images around 1.5 times slower.
I wanted to avoid this increase when possible. Don't know if it worths it.

Regards,
Maria

Bug#861495: plasma-discover: recommend apt-config-auto-update instead of software-properties-kde

[Francesco De Vita]

Package: plasma-discover
Version: 5.8.5-3
Severity: wishlist

Dear Maintainer,

plasma-discover recommends software-properties-kde, a package that allows via 
GUI to:
- manage the entries in the sources.list
- set periodic update and automatic upgrades
- opt in/out from the popularity contest

However the software-properties-* packages still have important and old bugs 
unresolved that undermine the user experience and, by default, do not enable 
automatic updates when installed.

A better alternative could be the installation of plasma-discover with
apt-config-auto-update instead, which provides "configuration snippets for the 
Apt package manager to have it automatically update its package cache".

In this way:
- the sources.list can still be managed using plasma-discover directly
- automatic updates are enabled by default

Despite the lack of a couple of features provided by software-properties-kde, 
this configuration could be better for a basic installation.

Regards


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

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

Versions of packages plasma-discover depends on:
ii  appstream0.10.6-2
ii  kio  5.28.0-2
ii  libappstreamqt2  0.10.6-2
ii  libc62.24-10
ii  libkf5archive5   5.28.0-2
ii  libkf5attica55.28.0-1
ii  libkf5configcore55.28.0-2
ii  libkf5configgui5 5.28.0-2
ii  libkf5configwidgets5 5.28.0-2
ii  libkf5coreaddons55.28.0-2
ii  libkf5crash5 5.28.0-1
ii  libkf5dbusaddons55.28.0-1
ii  libkf5declarative5   5.28.0-1
ii  libkf5i18n5  5.28.0-2
ii  libkf5kiocore5   5.28.0-2
ii  libkf5kiowidgets55.28.0-2
ii  libkf5newstuff5  5.28.0-1
ii  libkf5notifications5 5.28.0-1
ii  libkf5service-bin5.28.0-1
ii  libkf5service5   5.28.0-1
ii  libkf5widgetsaddons5 5.28.0-2
ii  libkf5xmlgui55.28.0-1
ii  libpackagekitqt5-0   0.9.6-1
ii  libqt5core5a 5.7.1+dfsg-3+b1
ii  libqt5dbus5  5.7.1+dfsg-3+b1
ii  libqt5gui5   5.7.1+dfsg-3+b1
ii  libqt5qml5   5.7.1-2+b2
ii  libqt5quick5 5.7.1-2+b2
ii  libqt5widgets5   5.7.1+dfsg-3+b1
ii  libqt5xml5   5.7.1+dfsg-3+b1
ii  libstdc++6   6.3.0-14
ii  packagekit   1.1.5-2
ii  plasma-discover-common   5.8.5-3
ii  qml-module-org-kde-kirigami  1.1.0-1

Versions of packages plasma-discover recommends:
pn  software-properties-kde  

plasma-discover suggests no packages.

-- no debconf information

Bug#861037: [Pkg-swan-devel] Bug#861037: Bug#861037: Bug#861037: [PATCH 00/12] New upstream release 5.5.2

[Alex Hürter]

>As you're already aware, I'm not a huge fan of multiplying plugins
packages.
>And while I can understand (and really feel sorry for them) people might
have
>requirements, I'm not personally interested at all with complex plugins.
IPsec
>is often considered complex, and I'm pretty sure having a gazillion plugin
>won't help. I really think have a simple install anyone can setup would
help a
>lot more.

>At the end of the day, I'm not really interested in spending time on this.
I
>won't prevent anyone to work on this provided the integration is simple
and I
>doesn't waste my time.

Could at least the plugins be enabled that are in the Strongswan
configuration
examples on the homepage (e.g. ntru and curve25519)?

Regards
Alex

2017-04-28 21:28 GMT+02:00 Yves-Alexis Perez :

> On Fri, 2017-04-28 at 09:44 -0700, Gerald Turner wrote:
> > Among the flurry of BTS mail I triggered last Sunday, did you happen to
> > catch my offers to:
>
> Honestly I'm a bit behind schedule so I noticed mails but didn't read them
> yet, sorry. Thanks for your work anyway.
> >
> >   1. Work on debian/copyright until it's near-perfect (I'm confident the
> >  work on I did on 5.5.1->5.5.2 delta is correct, but while working
> >  on that I noticed inconsistencies since older releases, which I
> >  mostly ignored).  I had done something similar with hostapd/
> >  wpa_supplicant a few years ago with guidance from Stefan
> >  Lippers-Hollmann.
>
> Looks interesting at first sight, yes.
> >
> >   2. Create separate packages per plugin (with extra attention paid to
> >  Depends, Recommends, Suggests fields), at a minimum create separate
> >  attr-sql/sqlite/mysql plugin packages (bug #718302), or maximally
> >  create a separate package for every plugin, or something in
> >  between.  Ultimately enabling additional plugins that myself and
> >  several other users have been requesting.
>
> As you're already aware, I'm not a huge fan of multiplying plugins
> packages.
> And while I can understand (and really feel sorry for them) people might
> have
> requirements, I'm not personally interested at all with complex plugins.
> IPsec
> is often considered complex, and I'm pretty sure having a gazillion plugin
> won't help. I really think have a simple install anyone can setup would
> help a
> lot more.
>
> At the end of the day, I'm not really interested in spending time on this.
> I
> won't prevent anyone to work on this provided the integration is simple
> and I
> doesn't waste my time.
>
> Also, like for all the work Christian Ehrhardt did (and I hope you checked
> it), nothing here matter until Stretch is released, so there's really no
> rush.
>
> Regards,
> --
> Yves-Alexis
> ___
> Pkg-swan-devel mailing list
> pkg-swan-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-swan-devel
>



-- 
Alex Hürter
Cert. IT-Systems Manager

+49 2462 995 0537 (H)
+49 179  4503914 (M)
alex.huer...@gmx.net (gesch.)
shorty1...@googlemail.com  (privat)

Bug#861313: kernel BUG with kvm

[I. Schrey]

Greetings,

I'm having a similar issue on a kvm hypervisor running Debian Jessie.

It is running a vanilla kernel though, but it started hitting
a similar BUG today, after I upgraded from 3.12 to 3.16 series.

3.16.42 seems to be the first affected version.
3.16.41 is working without problems so far.


Also I can confirm that Debian kernel 3.16.39-1+deb8u2 works
and 3.16.43-1 does have the issue described.


I might try and git bisect the kernel, today or tomorrow,
unless someone else beats me to it.


Side note: the same 3.16.43 vanilla kernel has been working
fine on two Wheezy kvm hypervisors for more than a week now.



Regards
Ingmar

Bug#861494: libunwind: Please enable sh4 in debian/control

[John Paul Adrian Glaubitz]

Source: libunwind
Version: 1.1-4.1
Severity: normal
User: debian-sup...@lists.debian.org
Usertags: sh4

Hi!

Although libunwind has upstream support for SuperH (SH), sh4 is
not enabled in the Architecture fields in debian/control.

I just did a quick build test and enabled sh4 with a simple regexp:

  $ sed -i 's/mips64el/sh4/g' debian/control

After that, the package built just fine on sh4.

Can you please append "sh4" to all Architecture fields in
debian/control?

Thanks,
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

Bug#861493: README: typo in architecture

[Héctor Orón Martínez]

Package: jenkins.debian.org
Severity: minor

Hello,

  While reading README documentation, I found a typo in the architecture
  description in the reproducible builds section. It describes amd64, while
  it really is arm64.

Regards

-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (900, 'unstable'), (500, 'buildd-unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-2-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)
From 96b08f18581d944a5c6f89bb351913881ed0edd7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?H=C3=A9ctor=20Or=C3=B3n=20Mart=C3=ADnez?= 
Date: Sat, 29 Apr 2017 19:01:26 +0200
Subject: [PATCH] README: fix typo
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Signed-off-by: Héctor Orón Martínez 
---
 README | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README b/README
index 0a5610a4..477c4043 100644
--- a/README
+++ b/README
@@ -140,7 +140,7 @@ Installation tests inside chroot environments.
 * These builds on remote nodes run on very different hardware:
 ** for 'amd64' we are using four virtual machines, 
profitbricks-build(1+5+11+15)-amd64, which have 15 or 16 cores and 48gb ram 
each. These nodes are sponsored by 
link:https://jenkins.debian.net/userContent/thanks.html[Profitbricks].
 ** for 'i386' we are also using four virtual machines, 
profitbricks-build(2+6+12+16)-i386, which have 10 or 9 cores and 36gb ram each. 
pb2+12 run emulated AMD Opteron CPUs and pb6+16 Intel Xeon CPUs. These nodes 
are also sponsored by 
link:https://jenkins.debian.net/userContent/thanks.html[Profitbricks].
-** for 'amd64' we are using eight "moonshot" sleds, codethink-sled9-15-arm64, 
which have 8 cores and 64gb ram each. These nodes are sponsored by 
link:https://jenkins.debian.net/userContent/thanks.html[Codethink].
+** for 'arm64' we are using eight "moonshot" sleds, codethink-sled9-15-arm64, 
which have 8 cores and 64gb ram each. These nodes are sponsored by 
link:https://jenkins.debian.net/userContent/thanks.html[Codethink].
 ** To test 'armhf' we are using 24 small boards donated by vagrant@d.o:
 *** three quad-cores (cbxi4a, cbxi4b, and ff4a) with 4gb ram,
 *** three octo-cores (odxu4, odxu4b and odxu4c) with 2gb ram,
-- 
2.11.0

Bug#861479: quantlib-swig: Missing call to dh_md5sums causes a dbgsym package without a md5sums file

[Niels Thykier]

Dirk Eddelbuettel:
> 
> On 29 April 2017 at 16:29, Niels Thykier wrote:
> | Source: quantlib-swig
> | Version: 1.9-1
> | Severity: important
> | User: debhelper-de...@lists.alioth.debian.org
> | Usertags: dbgsyms-package-with-issues
> | 
> | Hi,
> | 
> | Due to dh_md5sums being commented out in d/rules, the generated dbgsym
> | package for quantlib-python has no md5sums control file.
> 
> Sorry about that, will fix.
> 
> I may have more debian/rules files with commented-out dh_md5sums because at
> one point way back when these were optional.  Is this now mandatory?


They are "optional" in the sense that the package will still work.  I
don't remember if dpkg just computes it on the fly now or just creates
an empty md5sums file.  Anyway, they are useful for detecting corruption
(e.g. via dpkg --verify or debsums)

> Should lintian check?
> 
> Dirk
> 

There is a lintian check for it, but it is a "I:" tag, so you won't see
it unless you run lintian with --display-info.

Thanks,
~Niels

Bug#861492: hugo: New upstream versions of Hugo are available

[Michael Berg]

Package: hugo
Version: 0.18.1-1+b2
Severity: wishlist

Dear Maintainer,

Debian unstable and testing currently package Hugo 0.18.1.

Hugo 0.19 through 0.20.6 have been released upstream since February.
https://github.com/spf13/hugo/releases

Given some of the bug fixes, new features, and optimizations,
it would be nice to have native Debian packages for a newer version.

Note that there were some regressions in the early 0.20.x line,
which appear to have been fixed in 0.20.6.

Thank you for your work in maintain the Debian Hugo package.

-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64
 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-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: systemd (via /run/systemd/system)

Versions of packages hugo depends on:
ii  libc6  2.24-10

hugo recommends no packages.

hugo suggests no packages.

-- no debconf information

Bug#861479: quantlib-swig: Missing call to dh_md5sums causes a dbgsym package without a md5sums file

[Dirk Eddelbuettel]

On 29 April 2017 at 16:29, Niels Thykier wrote:
| Source: quantlib-swig
| Version: 1.9-1
| Severity: important
| User: debhelper-de...@lists.alioth.debian.org
| Usertags: dbgsyms-package-with-issues
| 
| Hi,
| 
| Due to dh_md5sums being commented out in d/rules, the generated dbgsym
| package for quantlib-python has no md5sums control file.

Sorry about that, will fix.

I may have more debian/rules files with commented-out dh_md5sums because at
one point way back when these were optional.  Is this now mandatory?  Should
lintian check?

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#860955: poppler: please package new upstream version 0.54.0 as soon as possible

[Francesco Poli]

On Mon, 24 Apr 2017 23:17:00 +0200 Pino Toscano wrote:

> In data lunedì 24 aprile 2017 22:42:06 CEST, Francesco Poli ha scritto:
[...]
> > That's fully understandable! If an upload had been made one month ago,
> > I wouldn't have asked for another upload now!
> 
> I don't see what would have changed then: the feature you referred to
> when opening this bug was committed less than a month ago upstream,
> and 0.54.0 (released few days ago) is the first version providing it.
> So even if experimental had 0.53.0, it wouldn't be usable for your
> needs.

In terms of final result, it would have basically changed nothing.
But I would have understood your refusal much more easily!   ;-)

That's it.


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpUA6OuyL45K.pgp
Description: PGP signature

Bug#737491: eterm: Occurs on upgrade to Jessie from Wheezy

[Andy Bennett]

Package: eterm
Version: 0.9.6-1
Followup-For: Bug #737491

Dear Maintainer,

Since updating my machine from Wheezy to Jessie, Eterm now uses 100% CPU
when started.

I've tried starting Eterm manually with no command line arguments and it
never gets as far as displaying a bash prompt.

I'm not really sure how to debug this further; please let me know
anything I can do to find out more information.


Thanks for your help.



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

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

Versions of packages eterm depends on:
ii  libast20.7-7
ii  libc6  2.19-18+deb8u7
ii  libfreetype6   2.5.2-3+deb8u1
ii  libice62:1.0.9-1+b1
ii  libimlib2  1.4.6-2+deb8u2
ii  libsm6 2:1.2.2-1+b1
ii  libx11-6   2:1.6.2-3
ii  libxext6   2:1.3.3-1
ii  multiarch-support  2.19-18+deb8u7
ii  zlib1g 1:1.2.8.dfsg-2+b1

eterm recommends no packages.

eterm suggests no packages.

-- no debconf information

Bug#861491: unblock: emacs24/24.5+1-11

[Rob Browning]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package emacs24

This upload is intended to fix two dependency problems and the ppc64(el)
memory exhaustion issue.

diff -Nru emacs24-24.5+1/debian/.git-dpm emacs24-24.5+1/debian/.git-dpm
--- emacs24-24.5+1/debian/.git-dpm	2017-04-22 12:32:14.0 -0500
+++ emacs24-24.5+1/debian/.git-dpm	2017-04-29 10:23:13.0 -0500
@@ -1,6 +1,6 @@
 # see git-dpm(1) from git-dpm package
-088b2e039897fcf9e2eea00f580a2c5d87eba781
-088b2e039897fcf9e2eea00f580a2c5d87eba781
+d1daaa0d464b4610e0f74553c5a91d1e5193c2ab
+d1daaa0d464b4610e0f74553c5a91d1e5193c2ab
 62bc68f777c532a970566625e315d68bf0ab4eee
 62bc68f777c532a970566625e315d68bf0ab4eee
 emacs24_24.5+1.orig.tar.bz2
diff -Nru emacs24-24.5+1/debian/changelog emacs24-24.5+1/debian/changelog
--- emacs24-24.5+1/debian/changelog	2017-04-22 12:33:05.0 -0500
+++ emacs24-24.5+1/debian/changelog	2017-04-29 10:23:47.0 -0500
@@ -1,3 +1,24 @@
+emacs24 (24.5+1-11) unstable; urgency=medium
+
+  * emacs-common: add "Breaks: mell (<= 1.0.0-7)".  Apparently it was
+removed from the archive in 2011 and can no longer install.
+Thanks to Andreas Beckmann for reporting the problem.
+(Closes: 860858)
+
+  * emacs-common: add "Breaks: prom-mew (<= 2.00+3.2am01-1)".
+Apparently it was removed from the archive in 2009 and can no
+longer install.  Thanks to Andreas Beckmann for reporting the
+problem. (Closes: 851604)
+
+  * Add additional fix for memory exhaustion on ppc64el.  Add
+0030-Emacs-should-really-work-with-glibc-2.24-on-ppc64.patch to
+augment the previous fix for memory exhaustion on ppc64(el).
+Thanks to Adrian Bunk and Iain Lane for reporting the problem and
+Iain Lane for backporting and providing the fix.
+(Closes: 854799, 861032)
+
+ -- Rob Browning   Sat, 29 Apr 2017 10:23:47 -0500
+
 emacs24 (24.5+1-10) unstable; urgency=medium
 
   * Don't segfault if gcc expects -nopie instead of -no-pie.
diff -Nru emacs24-24.5+1/debian/control emacs24-24.5+1/debian/control
--- emacs24-24.5+1/debian/control	2017-04-22 12:33:05.0 -0500
+++ emacs24-24.5+1/debian/control	2017-04-29 10:23:47.0 -0500
@@ -105,7 +105,9 @@
 Suggests: emacs24-el, emacs24-common-non-dfsg, ncurses-term
 Conflicts: emacs24-el (<< ${source:Version}), cedet, eieio, speedbar, gnus-bonus-el
 Breaks: apel (<< 10.8+0.20120427-4),
-oneliner-el (<= 0.3.6-7.1)
+mell (<= 1.0.0-7),
+oneliner-el (<= 0.3.6-7.1),
+prom-mew (<= 2.00+3.2am01-1)
 Description: GNU Emacs editor's shared, architecture independent infrastructure
  GNU Emacs is the extensible self-documenting text editor.
  This package contains the architecture independent infrastructure
diff -Nru emacs24-24.5+1/debian/control.in emacs24-24.5+1/debian/control.in
--- emacs24-24.5+1/debian/control.in	2017-04-22 12:32:11.0 -0500
+++ emacs24-24.5+1/debian/control.in	2017-04-29 10:23:13.0 -0500
@@ -105,7 +105,9 @@
 Suggests: @DEB_FLAVOR@-el, @DEB_FLAVOR@-common-non-dfsg, ncurses-term
 Conflicts: @DEB_FLAVOR@-el (<< ${source:Version}), cedet, eieio, speedbar, gnus-bonus-el
 Breaks: apel (<< 10.8+0.20120427-4),
-oneliner-el (<= 0.3.6-7.1)
+mell (<= 1.0.0-7),
+oneliner-el (<= 0.3.6-7.1),
+prom-mew (<= 2.00+3.2am01-1)
 Description: GNU Emacs editor's shared, architecture independent infrastructure
  GNU Emacs is the extensible self-documenting text editor.
  This package contains the architecture independent infrastructure
diff -Nru emacs24-24.5+1/debian/patches/0030-Emacs-should-really-work-with-glibc-2.24-on-ppc64.patch emacs24-24.5+1/debian/patches/0030-Emacs-should-really-work-with-glibc-2.24-on-ppc64.patch
--- emacs24-24.5+1/debian/patches/0030-Emacs-should-really-work-with-glibc-2.24-on-ppc64.patch	1969-12-31 18:00:00.0 -0600
+++ emacs24-24.5+1/debian/patches/0030-Emacs-should-really-work-with-glibc-2.24-on-ppc64.patch	2017-04-29 10:23:13.0 -0500
@@ -0,0 +1,59 @@
+From d1daaa0d464b4610e0f74553c5a91d1e5193c2ab Mon Sep 17 00:00:00 2001
+From: Paul Eggert 
+Date: Tue, 19 Jul 2016 15:23:14 +0200
+Subject: Emacs should (really) work with glibc 2.24 on ppc64
+
+Apparently the earlier fix in 3a838494fc769f1ae39adf20325869331f0c300d
+("Emacs should work with glibc 2.24 on ppc64") was incomplete.
+
+This patch, backported to Debian/Ubuntu by Iain Lane
+, has been added to address a remaining
+memory exhaustion problem:
+
+  Backport from master (Bug#24033).
+  Inspired by a suggestion by Florian Weimer in:
+  https://sourceware.org/ml/libc-alpha/2016-07/msg00425.html
+  * src/emacs.c (main) [__PPC64__]:
+  Special case for __PPC64__, which needs ASLR disabled in
+  dumped Emacs too.
+
+Origin: backport, commit: ff3fc21e24edffccce0d42065833e852a6792bd2
+Bug-Debian: http://bugs.debian.org/861032
+Bug-Debian: 

Bug#861415: virtualbox: Virtualbox 5.1.20: No audio devices could be opened. Error ID: HostAudioNotResponding.

[felipe]

After the last virtualbox update (version  5.1.22-dfsg-1),
the application starts normally with working audio.

You can close this bug as it was also solved upstream:

https://www.virtualbox.org/ticket/16667
Status changed from new to closed
Resolution set to fixed
Fixed in 5.1.22.

Bug#845641:

[Dio Putra]

Sorry, been busy for a week. I dunno too anyway, since Debian Unstable 
update is untraceable. Maybe some dependency libraries upgrade cause my 
problem is solved.

But anyway, sometimes it's need to re-"repairing mode" again in blueman. :(

Bug#858986: systemd-container: systemd-nspawn fails to spawn container from a read-only image

[Felix Wiedemann]

On 28.04.2017 22:16, Michael Biebl wrote:
> Hi Felix
> 
Hi Michael,

> On Wed, 29 Mar 2017 12:20:52 +0200 Felix Wiedemann
> <1wied...@informatik.uni-hamburg.de> wrote:
>> Package: systemd-container
>> Version: 232-19
>> Severity: normal
>>
>> Dear Maintainer,
>>
>> systemd-nspawn fails to spawn a container from an image which has a
>> read-only file system as root partition (SquashFS):
>>
>>   $ systemd-nspawn -i foo.img
>>   Spawning container foo.img on /home/felix/foo.img.
>>   Press ^] three times within 1s to kill container.
>>   Failed to create directory /tmp/nspawn-root-jvD8mU/sys: Read-only file 
>> system
>>
>> I filed the bug upstream [0] and it was fixed in systemd v233 [1].
>> Please consider backporting the patch to stretch.
>>
>> [0]: https://github.com/systemd/systemd/issues/4711
>> [1]: 
>> https://github.com/systemd/systemd/commit/acbbf69b718260755a5dff60dd68ba239ac0d61b
> 
> Have you confirmed that applying this commit on top of v232 fixes the
> issue you have? Otherwise, can you give me instructions how to create
> such a read-only image or provide one for me, so I can test it myself.
> 
I have a script attached to this mail which builds such a disk image.
Also, I verfied that `systemd-nspawn -i $IMAGE` with such a disk image
fails on stretch/v232 and on jessie-backports/v230. It works on jessie/v215.

I just tried to build systemd v232 with the commit applied on top, but
it does not compile because it's missing the type 'MountSettingsMask'. I
have not looked into that any further.

> Regards,
> Michael
> 
Thanks,
Felix



build-ro-disk-image.sh
Description: application/shellscript

Bug#861490: RFS: xf86-input-tslib/0.0.7-1

[Martin Kepplinger]

Package: sponsorship-requests
Severity: whishlist

Dear mentors,

I am looking for a sponsor for my package "xf86-input-tslib"

 * Package name: xf86-input-tslib
   Version : 0.0.7-1
   Upstream Author : Martin Kepplinger 
 * URL : https://github.com/merge/xf86-input-tslib-debian
 * License : MIT
   Section : x11

It builds those binary packages:

  xserver-xorg-input-tslib - tslib touchscreen driver for X.Org/XFree86
server

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/xf86-input-tslib


Alternatively, one can download the package with dget using this command:

  dget -x
https://mentors.debian.net/debian/pool/main/x/xf86-input-tslib/xf86-input-tslib_0.0.7-1.dsc

The package had been in Debian, see
https://tracker.debian.org/pkg/xf86-input-tslib but the packaging is
rewritten; the package is up to date.

tslib is often used in embedded systems without an X server, but since
tslib itself is in unstable, this would simply make it more easily
usable when running Xorg.

  Changes since the last upload:

xf86-input-tslib (0.0.7-1) unstable; urgency=low

  * upgrade to upstream 0.0.7 (Closes: #861455)
  * rewrite and simplify the packaging code for up-to-date Debian build
system

 -- Martin Kepplinger   Sat, 29 Apr 2017 12:07:58 +0100


  Regards,
   Martin Kepplinger

Bug#855179: [Hosted Weblate] please notic one debian bugreport

[Michal Čihař]

Hello

Beatrice Torracca píše v So 29. 04. 2017 v 15:34 +0200:
> Anyway that would not be a problem, as long as the Language-Team
> header had the email of the Debian localization mailing-list for that
> specific language. As far as I could see Weblate changes this header
> too, to some specific Weblate address. I think that it would be
> better
> if the Language-Team header of the Debian-specific weblate projects
> would point to the official Debian localization mailing list for each
> specific language. In this way the mailing-list and the language
> coordinator would be notified of any work that needs to be done.

Indeed this is the default setup as this is what makes sense for most
projects I'm hosting. I've just disabled this for Debian Reference (and
made that setting available to project admins as well).

-- 
Michal Čihař | https://cihar.com/ | https://weblate.org/


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

Bug#860969: Switching to ITA

[Ghislain Vaillant]

control: owner -1 !
control: retitle -1 ITA: pybtex -- BibTeX-compatible bibliography processor

On Sat, 22 Apr 2017 22:42:13 +0200 Daniel Stender  
wrote:
> I request an adopter for the pybtex package.

I intend to help maintaining this package as part of my effort to
package sphinxcontrib-bibtex, which pybtex is a dependency of.

Ghis

Bug#860234: redmine: various issues on jessie -> stretch upgrade

[Antonio Terceiro]

Control: tag -1 + moreinfo

On Thu, Apr 13, 2017 at 03:21:44AM -0400, Brad Barnett wrote:
> Package: redmine
> Version: 3.3.1-4
> Severity: normal
> 
> During a jessie to stretch upgrade:
> 
> 1)
> 
> ln: /var/lib/redmine/default/log: cannot overwrite directory
> dpkg: error processing package redmine (--configure):
> 
> A rm of existing log dir, then allowed the link to be created..

can you reproduce this in a clean install? (i.e. install on jessie, then
upgrade)

> 2)
> 
> The DB install prompt is missing the word 'database' everywhere.  EG:
> 
>  ┌───┤ Configuring redmine 
> ├┐
>  │ Please provide the hostname of a remote  server.   
>   │
>  │
>   │
>  │ You must have already arranged for the administrative account to be able 
> to remotely create databases and grant privileges.  │
>  │
>   │
>  │ Host running the  server for redmine/instances/default:
>   │
>  │
>   │
>  │ 
> 
>  │
>  │
>   │
>  │
>   │
>  │
>   │
>  
> └──┘

this dialog is provided by dbconfig-common, there is nothing that can be
fixed in redmine.

> 3) There are 'other issues', including a slew of gem issues .. but, I'm 
> unsure if that was user issue, or install issue.

in order to know what exactly is going on, I need more information from
you, such as

- did you install stuff by hand (e.g. redmine plugins using `bundle
  install`)? when you do that, pretty much everything goes bananas.

- details on what customizations were done to the install before the
  upgrade

- do you still have the log from the upgrade?


signature.asc
Description: PGP signature

Bug#861480: ImportError: No module named QtWebKit

[Michal Čihař]

Hi

Dejan Muhamedagic píše v So 29. 04. 2017 v 16:40 +0200:
> Package: series60-remote
> Version: 0.4.80+dfsg.1-2
> Severity: critical
> 
> ImportError: No module named QtWebKit

Apparently this has been broken for almost year, since following bug
has been fixed:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784513

As there is no active upstream and I don't have time to port this to
qt5, the only reasonable way is probably to remove this package.

-- 
Michal Čihař | https://cihar.com/ | https://weblate.org/


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

Bug#853965: jessie-pu: package installation-guide/20150423+deb8u3

[Samuel Thibault]

Hello,

Adam D. Barratt, on dim. 19 févr. 2017 20:35:11 +, wrote:
> Control: tags -1 + confirmed
> 
> On Thu, 2017-02-02 at 15:36 +0100, Cyril Brulebois wrote:
> > We're getting more reports from people failing to deal with syslinux
> > settings for debian-installer; we've had a fix in the installation guide
> > for quite a while but it wasn't propagated to jessie yet, meaning the
> > website still has faulty instructions for jessie (4.3.3.2):
> >   https://www.debian.org/releases/jessie/amd64/ch04s03.html.en
> >   https://www.debian.org/releases/stretch/amd64/ch04s03.html.en
> > 
> > Samuel already cherry-picked the changes in the jessie branch, but that
> > wasn't submitted yet. You'll find attached a quasi minimal patch against
> > jessie (yay svn…). Changelog:
> > | installation-guide (20150423+deb8u3) jessie; urgency=medium
> > | 
> > |   [ Matt Kraai ]
> > |   * Fix Instructions for creating syslinux.cfg according to syslinux 5.00
> > | change. Closes: #803267.
> 
> Please go ahead.

I have now uploaded them, see attached debdiff.

Samuel
diff -Nru installation-guide-20150423+deb8u2/debian/changelog 
installation-guide-20150423+deb8u3/debian/changelog
--- installation-guide-20150423+deb8u2/debian/changelog 2016-01-21 
20:24:13.0 +0100
+++ installation-guide-20150423+deb8u3/debian/changelog 2017-04-29 
17:20:16.0 +0200
@@ -1,3 +1,15 @@
+installation-guide (20150423+deb8u3) jessie; urgency=medium
+
+  [ Matt Kraai ]
+  * Fix Instructions for creating syslinux.cfg according to syslinux 5.00
+  change. Closes: #803267.
+
+  [ Cyril Brulebois ]
+  * Mass-update po translations (install-methods.po) so that the syslinux
+example is correct (see #803267): el es fi hu ko ru sv vi zh_CN zh_TW
+
+ -- Samuel Thibault   Sat, 29 Apr 2017 17:20:16 +0200
+
 installation-guide (20150423+deb8u2) jessie; urgency=medium
 
   [ Martin Michlmayr ]
diff -Nru 
installation-guide-20150423+deb8u2/en/install-methods/usb-setup/x86.xml 
installation-guide-20150423+deb8u3/en/install-methods/usb-setup/x86.xml
--- installation-guide-20150423+deb8u2/en/install-methods/usb-setup/x86.xml 
2014-08-26 22:40:15.0 +0200
+++ installation-guide-20150423+deb8u3/en/install-methods/usb-setup/x86.xml 
2016-11-11 20:49:54.0 +0100
@@ -1,5 +1,5 @@
 
-
+
 

Partitioning the USB stick
@@ -93,17 +93,16 @@
 
 
 Next you should create a syslinux.cfg configuration
-file, which at a bare minimum should contain the following two lines (change
+file, which at a bare minimum should contain the following line (change
 the name of the kernel binary to linux
 if you used a netboot image):
 
 
-default vmlinuz
-append initrd=initrd.gz
+default vmlinuz initrd=initrd.gz
 
 
 For the graphical installer you should add vga=788 to 
the
-second line. Other parameters can be appended as desired.
+line. Other parameters can be appended as desired.
 
 
 
diff -Nru installation-guide-20150423+deb8u2/po/el/install-methods.po 
installation-guide-20150423+deb8u3/po/el/install-methods.po
--- installation-guide-20150423+deb8u2/po/el/install-methods.po 2015-05-27 
23:29:21.0 +0200
+++ installation-guide-20150423+deb8u3/po/el/install-methods.po 2017-04-29 
17:20:08.0 +0200
@@ -1284,8 +1284,7 @@
 "ακόλουθες δύο γραμμές (αλλάξτε το όνομα του εκτελέσιμου του πυρήνα σε "
 "linux αν χρησιμοποιείτε μια εικόνα "
 "netboot): \n"
-"default vmlinuz\n"
-"append initrd=initrd.gz\n"
+"default vmlinuz initrd=initrd.gz\n"
 " Για τον γραφικό εγκαταστάτη θα πρέπει να "
 "προσθέσετε τις παραμέτρους vga=788 στη δεύτερη "
 "γραμμή. Μπορείτε να προσθέσετε και άλλες παραμέτρους σύμφωνα με τις "
diff -Nru installation-guide-20150423+deb8u2/po/es/install-methods.po 
installation-guide-20150423+deb8u3/po/es/install-methods.po
--- installation-guide-20150423+deb8u2/po/es/install-methods.po 2015-04-17 
16:28:47.0 +0200
+++ installation-guide-20150423+deb8u3/po/es/install-methods.po 2017-04-29 
17:20:08.0 +0200
@@ -1279,8 +1279,7 @@
 "(cambie el nombre del núcleo binario a linux si ha usado una imagen netboot): "
 "\n"
-"default vmlinuz\n"
-"append initrd=initrd.gz\n"
+"default vmlinuz initrd=initrd.gz\n"
 " Para el uso del instalador gráfico añada  "
 "vga=788 a la segunda línea. Puede añadir otros "
 "parámetros al final."
diff -Nru installation-guide-20150423+deb8u2/po/fi/install-methods.po 
installation-guide-20150423+deb8u3/po/fi/install-methods.po
--- installation-guide-20150423+deb8u2/po/fi/install-methods.po 2015-04-17 
17:11:30.0 +0200
+++ installation-guide-20150423+deb8u3/po/fi/install-methods.po 2017-04-29 
17:20:08.0 +0200
@@ -1234,8 +1234,7 @@
 "linux jos käytit netboot-otosta):\n"
 "\n"
-"default vmlinuz\n"
-"append initrd=initrd.gz\n"
+"default vmlinuz initrd=initrd.gz\n"
 " \n"
 "Asentimen graafista käyttöliittymää varten olisi toiseen riviin\n"
 "lisättävä vga=788."
diff -Nru installation-guide-20150423+deb8u2/po/hu/install-methods.po 

Bug#771806: confirmed in april 2017

[Marc Haber]

Package: avahi-daemon
Version: 0.6.32-2
Followup-For: Bug #771806

Hi,

I can confirm this behavior on current unstable.

Greetings
Marc

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

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

Versions of packages avahi-daemon depends on:
ii  adduser  3.115
ii  dbus 1.10.18-1
ii  init-system-helpers  1.47
ii  knot-host [host] 2.4.3-1
ii  libavahi-common3 0.6.32-2
ii  libavahi-core7   0.6.32-2
ii  libc62.24-10
ii  libcap2  1:2.25-1
ii  libdaemon0   0.14-6
ii  libdbus-1-3  1.10.18-1
ii  libexpat12.2.0-2
ii  lsb-base 9.20161125

Versions of packages avahi-daemon recommends:
ii  libnss-mdns  0.10-8

Versions of packages avahi-daemon suggests:
pn  avahi-autoipd  

-- no debconf information

Bug#861489: jessie-pu: package debian-edu-doc/1.6~20170429+deb8u4

[Holger Levsen]

Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu

Please accept debian-edu-doc/1.6~20170429+deb8u4 into the next Jessie point
release, the update just contains documentation and translation updates.

 debian-edu-doc (1.6~20170429+deb8u4) jessie; urgency=medium
 .
   [ Jessie Manual translation updates ]
   * Norwegian Bokmål: Ingrid Yrvin, Ole-Erik Yrvin, Petter Reinholdtsen.
   * German: Wolfgang Schweer.
   * Dutch: Frans Spiesschaert.
 .
   [ Wheezy Manual translation updates ]
   * Norwegian Bokmål: Petter Reinholdtsen.
 .
   [ Holger Levsen ]
   * Merge Jessie and Wheezy manual translation from master branch (which is
 maintained and uploaded to Stretch now). Starting 2017-03-25, the jessie
 branch is also the only one where we still maintain the Wheezy manual.

$ debdiff debian-edu-doc_1.6~20161129+deb8u3.dsc 
debian-edu-doc_1.6~20170429+deb8u4.dsc |diffstat
 debian/changelog   |   17 
 documentation/debian-edu-jessie/debian-edu-jessie-manual.da.po |   24 
 documentation/debian-edu-jessie/debian-edu-jessie-manual.de.po |   34 
 documentation/debian-edu-jessie/debian-edu-jessie-manual.es.po |   18 
 documentation/debian-edu-jessie/debian-edu-jessie-manual.fr.po |   25 
 documentation/debian-edu-jessie/debian-edu-jessie-manual.it.po |   33 
 documentation/debian-edu-jessie/debian-edu-jessie-manual.nb.po |  574 
+-
 documentation/debian-edu-jessie/debian-edu-jessie-manual.nl.po |   46 
 documentation/debian-edu-jessie/debian-edu-jessie-manual.pot   |   18 
 documentation/debian-edu-jessie/debian-edu-jessie-manual.xml   |4 
 documentation/debian-edu-wheezy/debian-edu-wheezy-manual.da.po |2 
 documentation/debian-edu-wheezy/debian-edu-wheezy-manual.de.po |2 
 documentation/debian-edu-wheezy/debian-edu-wheezy-manual.es.po |2 
 documentation/debian-edu-wheezy/debian-edu-wheezy-manual.fr.po |2 
 documentation/debian-edu-wheezy/debian-edu-wheezy-manual.it.po |2 
 documentation/debian-edu-wheezy/debian-edu-wheezy-manual.nb.po |  180 +--
 documentation/debian-edu-wheezy/debian-edu-wheezy-manual.nl.po |   28 
 documentation/debian-edu-wheezy/debian-edu-wheezy-manual.pot   |2 
 18 files changed, 545 insertions(+), 468 deletions(-)

And even though the compressed debdiff this time is just 30K I wont attach it 
;-p

Thanks for your work on Jessie!

-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#861488: unblock: debian-edu-doc/1.919~20170429

[Holger Levsen]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package debian-edu-doc, it just contains documentation and
translation updates, plus it also removes an alternative build-dependency
on ttf-wqy-zenhei as that's also an transitional package.

 debian-edu-doc (1.919~20170429) unstable; urgency=medium
 .
   [ Stretch Manual translation updates ]
   * Simplified Chinese: Roy Zhang, Ma Yong.
   * Norwegian Bokmål: Ingrid Yrvin, Ole-Erik Yrvin, Petter Reinholdtsen.
   * German: Wolfgang Schweer.
   * Dutch: Frans Spiesschaert.
   * Polish: Stanisław Krukowski.
 .
   [ Jessie Manual translation updates ]
   * Norwegian Bokmål: Ingrid Yrvin, Ole-Erik Yrvin, Petter Reinholdtsen.
   * Polish: Stanisław Krukowski.
 .
   [ ITIL Manual translation updates ]
   * Norwegian Bokmål: Ingrid Yrvin, Ole-Erik Yrvin.
 .
   [ Holger Levsen ]
   * Update Debian Edu Stretch manual from the wiki.
   * Remove alternative build-dependency ttf-wqy-zenhei as it's also a
 transitional package.
   * Update debian/copyright.

$ debdiff debian-edu-doc_1.918~20170326.dsc  
debian-edu-doc_1.919~20170429.dsc|diffstat
 debian/changelog |   24 
 debian/control   |2 
 documentation/audacity/audacity-manual.fr.po |2 
 documentation/audacity/audacity-manual.nb.po |2 
 documentation/audacity/audacity-manual.nl.po |5 
 documentation/audacity/audacity-manual.pl.po |   14 
 documentation/audacity/audacity-manual.pot   |2 
 documentation/audacity/audacity-manual.sv.po |2 
 documentation/debian-edu-itil/debian-edu-itil-manual.nb.po   | 1328 ++---
 documentation/debian-edu-itil/debian-edu-itil-manual.pot |2 
 documentation/debian-edu-jessie/debian-edu-jessie-manual.da.po   |2 
 documentation/debian-edu-jessie/debian-edu-jessie-manual.de.po   |2 
 documentation/debian-edu-jessie/debian-edu-jessie-manual.es.po   |2 
 documentation/debian-edu-jessie/debian-edu-jessie-manual.fr.po   |2 
 documentation/debian-edu-jessie/debian-edu-jessie-manual.it.po   |2 
 documentation/debian-edu-jessie/debian-edu-jessie-manual.nb.po   |  458 -
 documentation/debian-edu-jessie/debian-edu-jessie-manual.nl.po   |   13 
 documentation/debian-edu-jessie/debian-edu-jessie-manual.pl.po   |  119 
 documentation/debian-edu-jessie/debian-edu-jessie-manual.pot |2 
 documentation/debian-edu-stretch/debian-edu-stretch-manual.da.po |  427 +
 documentation/debian-edu-stretch/debian-edu-stretch-manual.de.po |  529 +-
 documentation/debian-edu-stretch/debian-edu-stretch-manual.es.po |  338 +
 documentation/debian-edu-stretch/debian-edu-stretch-manual.fr.po |  482 +
 documentation/debian-edu-stretch/debian-edu-stretch-manual.it.po |  506 +
 documentation/debian-edu-stretch/debian-edu-stretch-manual.ja.po |  451 +
 documentation/debian-edu-stretch/debian-edu-stretch-manual.nb.po | 2607 
+++---
 documentation/debian-edu-stretch/debian-edu-stretch-manual.nl.po |  598 +-
 documentation/debian-edu-stretch/debian-edu-stretch-manual.pl.po |  401 +
 documentation/debian-edu-stretch/debian-edu-stretch-manual.pot   |  307 +
 documentation/debian-edu-stretch/debian-edu-stretch-manual.xml   |  183 
 documentation/debian-edu-stretch/debian-edu-stretch-manual.zh.po |  792 +--
 documentation/rosegarden/rosegarden-manual.nb.po |   11 
 documentation/rosegarden/rosegarden-manual.pl.po |6 
 33 files changed, 5760 insertions(+), 3863 deletions(-)

I won't include the full debdiff as even gzip compressed its 175K, but you'll
find it in sid as described above.

Thanks for your work on Stretch!


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#861481: unblock: weechat/1.6-1+deb9u1

[Salvatore Bonaccorso]

Control: tags -1 - moreinfo

Hi,

On Sat, Apr 29, 2017 at 03:23:00PM +, Niels Thykier wrote:
> Control: tags -1 confirmed moreinfo
> 
> Salvatore Bonaccorso:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: unblock
> > 
> > Hi
> > 
> > Disclaimer: please note, not the maintainer here, but Emmanuel is
> > X-Debbug-CC'ed.
> > 
> > Please unblock package weechat
> > 
> > I guess 1.7-3 as in unstable, fixing CVE-2017-8073, #861121 cannot be
> > unblocked, since the changes to 1.6-1 are way to much (if yes, though,
> > that would great). If not, I propose a targeted fix to fix this CVE:
> > 
> > +weechat (1.6-1+deb9u1) stretch; urgency=medium
> > +
> > +  * Non-maintainer upload.
> > +  * irc: fix parsing of DCC filename (CVE-2017-8073) (Closes: #861121)
> > +
> > + -- Salvatore Bonaccorso   Sat, 29 Apr 2017 16:31:58 
> > +0200
> > 
> > The issue is as well fixed already in stable via a DSA.
> > 
> > unblock weechat/1.6-1+deb9u1
> > 
> > Regards
> > Salvatore
> > 
> 
> Ack, please ago ahead with the tpu upload.

Thanks, uploaded.

Salvatore