Bug#853016: even stops apt

[Arto Jantunen]

Control: severity -1 important

積丹尼 Dan Jacobson  writes:
> severity 853016 grave
> thanks
> In fact, you terminate the window the aptitude upgrade was running.
> The next time the user runs apt/aptitude, he will be met with
> E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to 
> correct the problem. 
> W: Could not lock the cache file; this usually means that dpkg or another apt
> tool is already installing packages.  Opening in read-only mode; any changes
> you make to the states of packages will NOT be preserved!
> E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to 
> correct the problem. 

This is documented behaviour and thus not RC, please see the release notes:

"You should not upgrade using telnet, rlogin, rsh, or from an X
session managed by xdm, gdm or kdm etc. on the machine you are
upgrading. That is because each of those services may well be terminated
during the upgrade, which can result in an inaccessible system that is
only half-upgraded."

The package has logic to not restart nodm if the user is logged in (I
think this was copied from gdm3):

if [ "$1" = "remove" ]; then
  if [ -x /etc/init.d/nodm ]; then
nostop=
for hostname in "" "localhost" "$(hostname)" "$(hostname -f)"; do
  if echo $DISPLAY | grep -q "^$hostname:0.*"; then
nostop=yes
  fi
done
if [ -z $nostop ]; then
  invoke-rc.d nodm stop
fi
  fi
fi

It seems that this didn't work for you for one reason or the other. I'll
look into this.

-- 
Arto Jantunen

Bug#853004: security: javascript in the book can access files on the computer using XMLHttpRequest?

[Martin Pitt]

Control: notfound -1 2.75.1+dfsg-1

Hello Antoine,

Antoine Beaupre [2017-01-28 15:56 -0500]:
> Someone pointed me to this note in the 2.75.1 changelog:
> 
> E-book viewer: Prevent javascript in the book from accessing files
> on the computer using XMLHttpRequest.

I did mention this in the 2.75.1 changelog
(https://tracker.debian.org/news/827355), so marking as fixed in the current
testing/unstable version.

The corresponding upstream commit is:
https://github.com/kovidgoyal/calibre/commit/3a89718664cb8c

Martin

Bug#853039: fontypython: please make the build reproducible

[Chris Lamb]

Source: fontypython
Version: 0.4.6-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: locale
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0], we noticed
that fontypython could not be built reproducibly.

Patch attached that exports LANG=C to ensure that we do not end up
with translated strings in the .egg-info.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/rules  2017-01-29 21:29:44.518412978 +1300
--- b/debian/rules  2017-01-29 21:36:47.894617183 +1300
@@ -3,6 +3,10 @@
 %:
dh $@ --with python2
 
+override_dh_auto_install:
+   # Ensure we do not end up with translated strings in .egg-info
+   LANG=C dh_auto_install
+
 override_dh_install:
dh_installchangelogs CHANGELOG
dh_python2

Bug#852816: ITP: node-home-path -- Cross-platform home directory retriever

[Pirate Praveen]

On ഞായര്‍ 29 ജനുവരി 2017 01:20 വൈകു, Tollef Fog Heen wrote:
> Do we need a fourth node.js package to do this?  We already have
> node-resolve-dir, node-expand-tilde and node-osenv which all seems to do
> the same.
> 

Tollef,

We'll use os.homedir() instead.

Tushar,

You can close this ITP.



signature.asc
Description: OpenPGP digital signature

Bug#796116: RM: fontforge-doc -- ROM; No longer needed with newer fontforge upstream version

[Hideki Yamane]

control: clone -1 -3
control: reassign -3 fontforge
control: reassign -1 ftp.debian.org
control: retitle -1 -- ROM; No longer needed with newer fontforge version

On Wed, 19 Aug 2015 17:20:31 +0200 Hideki Yamane  wrote:
> Package: fontforge-doc
> 
>  Just a notice, fontforge upstream now includes docs director, and
>  it contains files that fontforge-doc package has.
> 
>  So, after fontforge 1:20150612-1, it should be removed (in the future).
>  Also fontforge should have "Breaks: fontforge-doc"

 Now it's time to remove fontforge-doc.
 Could you do it, please?

-- 
Regards,

 Hideki Yamane henrich @ debian.or.jp/org
 http://wiki.debian.org/HidekiYamane

Bug#853041: general: Blank screen after suspend on acer laptop (only if logged on)

[antoine]

Package: general
Severity: important

Dear Maintainer,

I have a Debian 8 on my laptop since several months now and it worked all fine.

However, since about 2 weeks, the laptop freezes when I suspend a logged-on
session.

My informations :
- I can successfully do CTR+ALT+F1 after resume, only the display is
broken.
- I tried to uninstall nvidia drivers and backlisting nouveau : nothing
changed
- It only happens when there is a session logged on. If I logout before
suspend, the computer can resume normally.
- I tried to suspend both by closing the lid of the laptop and by
pressing ALT while clicking on the shutdown button in the top right corner :
same bug

I don't "hack" with the system a lot. I mostly browse the internet and do a
weekly "apt-get update && install".

Best Regards,
Antoine



-- 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=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#852596: iio-sensor-proxy: spams syslog with an error message every second

[Ritesh Raj Sarraf]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On Fri, 2017-01-27 at 22:04 +0100, iqwue Wabv wrote:
> upstream of i-s-p suggests that this bug should be reassigned to kernel 
> package.
> ps.
> said 27.01.2017 on https://github.com/hadess/iio-sensor-proxy/issues/134

Yes. I am aware of that. The Debian Kernel Policy, usually, is to not include
changes that aren't in the kernel already. And this fix seems to have gone for
4.10 or 4.11, whereas the Debian Stretch kernel will be based on 4.9 LTS.

I'm adding debian-kernel to this reply, in case the policy has changed.

If this fix gets included in the Linux 4.9 LTS tree upstream, then Debian would
automatically pull it for Stretch inclusion. But, at this moment, this isn't
even in Linus's tree.


- -- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEQCVDstmIVAB/Yn02pjpYo/LhdWkFAliNrzsACgkQpjpYo/Lh
dWmWfg/+KT0juLnQNJ0A+197TAI9S2R/igTb1BqMlyxjGb6/XIygiRgW0M6w0se3
MeH+3ucyhQJiHLsnuS/7hTvq2AzQpLriR5xI8Me/MIWm27queUcUmbe5FYjNM9ER
HL93nJ0ahtw6PojxeAigJpB0237PIrcDjvP9Krw5h5quUJYc92QVbRm3ZQ2CTap+
+pZ1ZXAGiLpZNgqy3/Z6YPY/o4bfL1puFPrqF1ZHUEKhvdAPZ+XFXhsb3yI7qeZu
OVAZyTO6dpN9sdF+3qt40okLrc2C4/BZRGaS19Dc9yWBXePRYYElQkl32uWSwiBK
bqZ6pqs4MRBeg3USAxTqHzH/JeaCUZuUJRHg21zFnM/p5bN2exWyeyH6HLSUQLlx
epSGXPpnILnsJTYyayz0dvCmomTb+A6urS0CpaebmGqAwhzI9qdZ2cbLY6cK2cOj
AKs+5D0iYRkuoBqtBK90kkpDg1L5CTcZ47Tcy4nBRhbZjBXda5OrXIiNgdM1pv+u
UDhuvbueQKBi24lQEoeG26aP7PKcCpz0/qfKYfjYjJ2Jv+UYp7/nDXWLvrDPK8ra
Ohw2FCAt0145YVECUFazh6xqQyr3xS2hljcHeF7WaBvxSiay8M2wQ9rDmPrP827U
MYNYcx6Jh6w5OAFZSiZVg4R5REZYzdp6WUvRttleDKbZJ+UnqNk=
=trfY
-END PGP SIGNATURE-

Bug#852771: sash FTCBFS: uses build architecture build tools

[Tollef Fog Heen]

]] Helmut Grohne 

> sash fails to cross build from source, because it uses build
> architecture build tools (cc, strip). Having dh_auto_build supply cross
> compilers to make and removing the explicit strip invocation (dh_strip
> still strips), makes a cross build succeed. Please consider applying the
> attached patch. It also fixed -dbgsym generation.

This looks quite reasonable.  Since it's not particularly urgent, I'll
leave it until we've released stretch so as to keep unstable open in
the unlikely case an upload is needed.

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are

Bug#852596: iio-sensor-proxy: spams syslog with an error message every second

[Ian Campbell]

On Sun, 2017-01-29 at 14:30 +0530, Ritesh Raj Sarraf wrote:
> On Fri, 2017-01-27 at 22:04 +0100, iqwue Wabv wrote:
> > upstream of i-s-p suggests that this bug should be reassigned to kernel 
> > package.
> > ps.
> > said 27.01.2017 on https://github.com/hadess/iio-sensor-proxy/issues/134
> 
> Yes. I am aware of that. The Debian Kernel Policy, usually, is to not include
> changes that aren't in the kernel already. And this fix seems to have gone for
> 4.10 or 4.11, whereas the Debian Stretch kernel will be based on 4.9 LTS.
> 
> I'm adding debian-kernel to this reply, in case the policy has changed.

It has never been as strict as you suggest, backports from mainline are
ok too (and always have been AFAIK) if justified. For especially urgent
or important fixes then "in a maintainers tree and so well on the way
to mainline" can be the minimum necessary bar.

> If this fix gets included in the Linux 4.9 LTS tree upstream, then Debian 
> would
> automatically pull it for Stretch inclusion.

This is true too, but there's no particular need to wait for that
process to unfold.

> But, at this moment, this isn't even in Linus's tree.

Can you point to the commit in the relevant upstream kernel maintainer's tree?

Ian.

Bug#852841: voro++: FTBFS: symbols not as expected

[Chris Lamb]

Hi,

> voro++: FTBFS: symbols not as expected

Out of interest, why is this not RC? :)


Regards,

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

Bug#853042: mdadm: Cron comment doesn't match code

[Olaf van der Spek]

Package: mdadm
Version: 3.3.2-5+deb8u2
Severity: normal

Dear Maintainer,

52 1 28 doesn't seem to match 00:57 every Sunday..

# By default, run at 00:57 on every Sunday, but do nothing unless the day of
# the month is less than or equal to 7. Thus, only run on the first Sunday of
# each month. crontab(5) sucks, unfortunately, in this regard; therefore this
# hack (see #380425).
52 1 28

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

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

Versions of packages mdadm depends on:
ii  debconf [debconf-2.0]  1.5.56
ii  initscripts2.88dsf-59
ii  libc6  2.19-18+deb8u7
ii  lsb-base   4.1+Debian13+nmu1
ii  udev   215-17+deb8u6

Versions of packages mdadm recommends:
ii  exim4-daemon-heavy [mail-transport-agent]  4.84.2-2+deb8u3
ii  kmod   18-3
ii  module-init-tools  18-3

mdadm suggests no packages.

-- debconf information:
* mdadm/boot_degraded: true
  mdadm/start_daemon: true
  mdadm/autostart: true
  mdadm/autocheck: true
  mdadm/initrdstart_msg_errconf:
  mdadm/mail_to: root
  mdadm/initrdstart_msg_intro:
  mdadm/initrdstart_notinconf: false
* mdadm/initrdstart: all
  mdadm/initrdstart_msg_errexist:
  mdadm/initrdstart_msg_errblock:
  mdadm/initrdstart_msg_errmd:

Bug#852013: Patch to prevent segfaults on signal

[Mattia Rizzolo]

On Sat, Jan 28, 2017 at 04:35:47PM -0500, Brett Smith wrote:
> I'm not complaining, just checking: my patch got reverted about twenty
> minutes after it got committed to master.  Are you sure you were testing
> in that time before it got reverted?

Yes.
Chris reverted it after my email.

> Earlier I was able to reproduce what was in your original report: same
> basic flow of debug messages, same issue of tempfiles not going away.
> The only difference I saw was that it segfaulted.  I thought maybe that
> wasn't included in the original report just because your shell didn't
> report it, or something like that.

As I wrote somewhere (but only on IRC maybe), I also noticed segfaults
while trying to reproduce it, but not so often.  It appeared to not
cleanup also when it didn't segfault.

> And it seemed to explain why the
> cleanup code wasn't running: the whole Python process was dying before
> it could get to the `finally` block that does the cleanup.  On my host,
> fixing this segfault and fixing the cleanup code went hand in hand,
> because now diffoscope could reliably get to the cleanup code.


Yesterday I tried several times with what was HEAD (with your patch) and
before that, and appeared to not clean up in both cases, without
sefualt reported.  Today it seem to always clean up with your patches
but always segfault (which is weird, as it never segfaulted reliably for
me) without.  meh.
OTOH, I now realized that somehow my shell might have eaten the
"Segmentation fault" message (although it doesn't do that usually), as I
just had a run terminated with code 139 without said message.
I'll report back once it does not segfault and not clean up.


BTW, I've committed your patche in a separated branch, as it deserves
to get in at some point (pity also because Debian is now freezing, and
we need to get the package into stretch, etc...

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#853043: ITP: node-term-size -- Reliably get the terminal window size

[Aarti Kashyap]

Package: wnpp
Severity: wishlist
Owner: Aarti Kashyap 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-term-size
  Version : 0.1.0
  Upstream Author : Sindre Sorhus  (sindresorhus.com
)
* URL : https://github.com/sindresorhus/term-size#readme
* License : Expat
  Programming Lang: JavaScript
  Description : Reliably get the terminal window size

Bug#852596: iio-sensor-proxy: spams syslog with an error message every second

[Ritesh Raj Sarraf]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Control: tag -1 -wontfix
Control: reassign -1 linux

On Sun, 2017-01-29 at 09:10 +, Ian Campbell wrote:
> > I'm adding debian-kernel to this reply, in case the policy has changed.
> 
> It has never been as strict as you suggest, backports from mainline are
> ok too (and always have been AFAIK) if justified. For especially urgent
> or important fixes then "in a maintainers tree and so well on the way
> to mainline" can be the minimum necessary bar.
> 

Well. That is good then.

> > If this fix gets included in the Linux 4.9 LTS tree upstream, then Debian
> > would
> > automatically pull it for Stretch inclusion.
> 
> This is true too, but there's no particular need to wait for that
> process to unfold.
> 
> > But, at this moment, this isn't even in Linus's tree.
> 
> Can you point to the commit in the relevant upstream kernel maintainer's tree?

This should be the one:
http://git.infradead.org/users/dvhart/linux-platform-drivers-x86.git/commit/25a7c6f172af2a3187147c0ad4880c0968de3f02


- -- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEQCVDstmIVAB/Yn02pjpYo/LhdWkFAliNtYEACgkQpjpYo/Lh
dWnH5w//VpCKHZMpjgeBq4WMgdjKcgHwZnJmz01tNxnjpddTcOqZf7HlHgS8a6Zo
2JZNAuzYlrxJD9yrIP7+Lk9hWuAXtOHfmFLhV9h2A3dmG43D0asII2dyVrukQrKZ
Sm1JbkfyCnxK5H8nNgV+u25uEfU6cpFRScv2kdIAHKAdHhp3oNh2iqAJcvPlTZ6s
DlgizhT02kgyT6fobVR02Jc8HNxMEV9LBS50Xt0exhXQ25Qtx1TJShqwM1vtKZn7
Qd11duDZSUH98Qw500n3RNXJdyPNGFN3xqJeKxVw4mhiZtUqD66kB+wlMu25vmSE
9YVJ3BinxGdetWH1cJrANxGLxksmic3UzbSRGbQ0fPjfJao5rQMxlQVK5A7w1jdJ
jVSKV2Xtt4Trck5XKNPXtVMTEO+F4tgER8GXoxQ4kziMvyAhQGKQ+nobraKCnGWy
zVJ5+PlDtEe8vT/XkFxqyc/H1H8svD4AQLm9bvzuLDYigPWCS0H1Lm++hv0B2Ubg
9bjiMCKCWlgpCI/USaY71omWjAnz6Lr/g3ZoQqw9FEvOZk4ijzjbTaY75Aku
H8kJIHPz+JRXi35EthOXlMR6xRJlhRxCIYjj0C235Szdz5UgkFQMxauso8KzPQgq
5isLdzTrUklFC0/Tuub+Kbac7sHAfaNNBAKgH1nZlBAoeP6cMRE=
=7w0f
-END PGP SIGNATURE-

Bug#852709: [debian-mysql] Bug#852709: Patch

[Otto Kekäläinen]

Hello!

2017-01-28 3:32 GMT+02:00 James Clarke :
> Are you using a very old chroot? You need dpkg-dev (>= 1.18.11) to support
> quadruplets in the Architecture field, though that was uploaded on the 6th
> November...

No TokuDB in unstable now:
https://packages.debian.org/unstable/mariadb-plugin-tokudb
This problably due to me uploading binaries, and as other no than
amd64 will build TokuDB, and the amd64 had no reason to trigger a
rebuild, so only my binaries (without TokuDB) are in the repositories
now.

I am using pbuilder to build, and I updated the chroots just a few
days ago (http://labs.seravo.fi/~otto/debian/update-chroots.sh), so it
is unlikely the dpkg versio was old, unless the pbuilder update is
somehow broken. If it worked for you on barreire, then I don't know
what caused it here.

- Otto

Bug#853044: gnome-themes-standard-data: Adwaita Dark is missing gtk.css for gkt3

[Pr0metheus]

Package: gnome-themes-standard-data
Version: 3.22.2-1
Severity: important

Dear Maintainer,

   * What led up to the situation?

I changed my theme to Adwaita Dark

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

I noticed that sometimes strange things happen to the programs especially when
switching, like activity bar going black but I cannot suggest how to reproduce
this. As the Adwaita (not Dark) works with no problems, I believe the change to
Adwaita dark caused these. This happened at least 3 times with Evolution (mail
client) after hitting Super or changing with other windows

   * What was the outcome of this action?

Activity bar randomly goes black.

   * What outcome did you expect instead?

Normal.

Other notes:

I did a search in the folders of /usr/share/themes/Adwaita-dark and compared
with Adawaita, I noticed that the gtk3 files are missing. I then went to github
and saw that there are gtk3 files for Adwaita dark (gtk.css).



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

Kernel: Linux 4.9.0-1-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)

-- no debconf information

Bug#752485: libp11-kit0:amd64: Please create /etc/pkcs11 directory structure

[Laurent Bigonville]

On Tue, 24 Jun 2014 01:40:55 +0200 Laurent Bigonville  
wrote:

> Hi,
>
> p11-kit is using /etc/pkcs11(/modules) directories to store its
> configuration files but the directory structure is not created by the
> package.
>
> Could you please create this (empty) directory structure from the
> package, this would make it a bit easier for a local admin to add a
> configuration file there.

Ping?

Any remarks concerning this bug and my patch?

Regards,

Laurent Bigonville

Bug#846256: Confirm

[moldev]

I confirm the same error on boot. Not sure what the implications are, the 
system seems to work, even when I go to the console.
Cheers,

-- Miguel

Bug#853045: pkg-perl-tools: Broken link for repack.sh in examples/repack.stub

[Christopher Hoskin]

Package: pkg-perl-tools
Version: 0.36
Severity: minor

Dear Maintainer,

examples/repack.stub displays a message if repack.sh cannot be found in one of
the expected locations. It says that repack.sh can be downloaded from:

http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/pkg-perl-tools.git;a=blob_plain;f=scripts/repack.sh;hb=HEAD

This link returns a 404. I think the correct link should be:

https://anonscm.debian.org/cgit/pkg-perl/packages/pkg-perl-tools.git/plain/scripts/repack.sh

Thanks.

Christopher Hoskin

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

Kernel: Linux 4.8.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)

Versions of packages pkg-perl-tools depends on:
ii  debhelper  10.2.3
ii  devscripts 2.17.0
ii  dh-make-perl   0.92
ii  dpkg-dev   1.18.18
ii  git1:2.11.0-2
ii  git-buildpackage   0.8.10
ii  libdatetime-perl   2:1.42-1
ii  libdpkg-perl   1.18.18
ii  libipc-run-perl0.94-1
ii  libparse-debianchangelog-perl  1.2.0-12
ii  libproc-invokeeditor-perl  1.07-1
ii  librt-client-rest-perl 1:0.50-1
ii  lintian2.5.50
ii  openssh-client [ssh-client]1:7.4p1-5
pn  perl:any   
ii  pristine-tar   1.37
ii  quilt  0.63-8

Versions of packages pkg-perl-tools recommends:
ii  autodep8   0.8
ii  autopkgtest4.3
ii  libconfig-model-dpkg-perl  2.090
ii  libconfig-model-perl   2.097-1
ii  libdebian-copyright-perl   0.2-4
ii  libfile-slurp-perl .19-6
ii  libmime-lite-perl  3.030-2
ii  libmodule-inspector-perl   1.05-2
ii  libnet-github-perl 0.86-1
ii  libsoap-lite-perl  1.20-1
ii  libwww-mechanize-perl  1.83-1
ii  libyaml-libyaml-perl   0.63-2
ii  lintian2.5.50
ii  myrepos [mr]   1.20160123

Versions of packages pkg-perl-tools suggests:
ii  bc   1.06.95-9+b2
ii  cdbs 0.4.150
pn  duck 
pn  moreutils
pn  perl-depends 
ii  python   2.7.13-1
ii  python-launchpadlib  1.10.4-1

-- no debconf information

Bug#852925: r-cran-zelig_5.0-13-1_amd64.changes is NEW

[Andreas Tille]

Hi ftpmasters,

it seemed this mail slipped through.  You kindly accepted r-cran-zelig
but r-cran-survey and r-cran-aer remain in new queue.  It would be nice
if you could consider the latter two soon to not let r-cran-zelig
uninstallable in unstable and keeping QA-people busy filing bug reports
about this.

Kind regards

   Andreas.

On Mon, Jan 09, 2017 at 10:49:26AM +0100, Andreas Tille wrote:
> Hi ftpmasters,
> 
> just a note for this package:  Despite this package is not new and you
> might consider fastprocessing please note that it needs two
> (Build-)Depends that are currently in the new queue (r-cran-survey and
> r-cran-aer).
> 
> The package somehow escaped my general overhaul of all R packages -
> possibly since it was not (yet) team maintained and the source package
> name did not followed the r-cran-* naming scheme.  Both is fixed now.
> 
> I confirm that I understand that its to late for the next stable release
> I just want to make sure that the dependencies will be accepted before
> this package.
> 
> Happy new year to all ftpmasters and thanks for your work
> 
>   Andreas.
> 
> On Mon, Jan 09, 2017 at 09:34:04AM +, Debian FTP Masters wrote:
> > source:r-cran-zelig is NEW.
> > 
> > Your package has been put into the NEW queue, which requires manual action
> > from the ftpteam to process. The upload was otherwise valid (it had a good
> > OpenPGP signature and file hashes are valid), so please be patient.
> > 
> > Packages are routinely processed through to the archive, and do feel
> > free to browse the NEW queue[1].
> > 
> > If there is an issue with the upload, you will receive an email from a
> > member of the ftpteam.
> > 
> > If you have any questions, you may reply to this email.
> > 
> > [1]: https://ftp-master.debian.org/new.html
> >  or https://ftp-master.debian.org/backports-new.html for *-backports
> > 
> > -- 
> > debian-science-maintainers mailing list
> > debian-science-maintain...@lists.alioth.debian.org
> > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
> > 
> 
> -- 
> http://fam-tille.de
> 
> -- 
> debian-science-maintainers mailing list
> debian-science-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
> 

-- 
http://fam-tille.de

Bug#853045: Pending fixes for bugs in the pkg-perl-tools package

[pkg-perl-maintainers]

tag 853045 + pending
thanks

Some bugs in the pkg-perl-tools package are closed in revision
7fe6bf8df5cff11c338b13251990a45c58bfea95 in branch 'master' by
Christopher Hoskin

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/pkg-perl-tools.git/commit/?id=7fe6bf8

Commit message:

Fix broken link in examples/repack.stub
* Fix "Broken link for repack.sh in examples/repack.stub" Changed broken 
link
  to working link (Closes: #853045)

Bug#852941: kernel oops in module igb

[Anton Gorlov]

Control: tag -1 moreinfo

I cannot keep full kernel core dump.
after install kdebug* and enable it, after kernel error  /var/crash is
empty.

Bug#853047: unblock: pysal/1.13.0-3

[Bas Couwenberg]

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

Please unblock package pysal

It contains an upstream patch to fix #848783 (FTBFS with NumPy 1.12),
instead of just ignoring the test failure.

unblock pysal/1.13.0-3

Kind Regards,

Bas
diff -Nru pysal-1.13.0/debian/changelog pysal-1.13.0/debian/changelog
--- pysal-1.13.0/debian/changelog   2016-12-19 22:45:24.0 +0100
+++ pysal-1.13.0/debian/changelog   2017-01-28 12:38:13.0 +0100
@@ -1,3 +1,12 @@
+pysal (1.13.0-3) unstable; urgency=medium
+
+  * Team upload.
+  * Add upstream patch to fix FTBFS with NumPy 1.12.
+(closes: #848783)
+  * Don't ignore test failures, numpy compatibility has been fixed.
+
+ -- Bas Couwenberg   Sat, 28 Jan 2017 12:38:13 +0100
+
 pysal (1.13.0-2) unstable; urgency=medium
 
   * Team upload.
diff -Nru pysal-1.13.0/debian/patches/fix-for-numpy-bump-induced-breakage.patch 
pysal-1.13.0/debian/patches/fix-for-numpy-bump-induced-breakage.patch
--- pysal-1.13.0/debian/patches/fix-for-numpy-bump-induced-breakage.patch   
1970-01-01 01:00:00.0 +0100
+++ pysal-1.13.0/debian/patches/fix-for-numpy-bump-induced-breakage.patch   
2017-01-28 12:36:03.0 +0100
@@ -0,0 +1,346 @@
+Description: Fix for numpy bump induced breakage.
+ - casting index to int
+ - casting to ints
+ - fix for numpy bump (casting and reshape behavior)
+Author: Serge Rey 
+Bug: https://github.com/pysal/pysal/issues/896
+Bug-Debian: https://bugs.debian.org/848783
+
+--- a/pysal/esda/smoothing.py
 b/pysal/esda/smoothing.py
+@@ -555,11 +555,11 @@ def assuncao_rate(e, b):
+ class _Smoother(object):
+ """
+ This is a helper class that implements things that all smoothers should 
do.
+-Right now, the only thing that we need to propagate is the by_col 
function. 
++Right now, the only thing that we need to propagate is the by_col 
function.
+ 
+ TBQH, most of these smoothers should be functions, not classes (aside from
+ maybe headbanging triples), since they're literally only inits + one
+-attribute. 
++attribute.
+ """
+ def __init__(self):
+ pass
+@@ -567,7 +567,7 @@ class _Smoother(object):
+ @classmethod
+ def by_col(cls, df, e,b, inplace=False, **kwargs):
+ """
+-Compute smoothing by columns in a dataframe. 
++Compute smoothing by columns in a dataframe.
+ 
+ Parameters
+ ---
+@@ -582,15 +582,15 @@ class _Smoother(object):
+ inplace :  bool
+a flag denoting whether to output a copy of `df` with the
+relevant smoothed columns appended, or to append the 
columns
+-   directly to `df` itself. 
++   directly to `df` itself.
+ **kwargs:  optional keyword arguments
+optional keyword options that are passed directly to the
+-   smoother. 
++   smoother.
+ 
+ Returns
+ -
+ a copy of `df` containing the columns. Or, if `inplace`, this returns
+-None, but implicitly adds columns to `df`.  
++None, but implicitly adds columns to `df`.
+ """
+ if not inplace:
+ new = df.copy()
+@@ -718,13 +718,13 @@ class Empirical_Bayes(_Smoother):
+ class _Spatial_Smoother(_Smoother):
+ """
+ This is a helper class that implements things that all the things that
+-spatial smoothers should do. 
++spatial smoothers should do.
+ .
+-Right now, the only thing that we need to propagate is the by_col 
function. 
++Right now, the only thing that we need to propagate is the by_col 
function.
+ 
+ TBQH, most of these smoothers should be functions, not classes (aside from
+ maybe headbanging triples), since they're literally only inits + one
+-attribute. 
++attribute.
+ """
+ def __init__(self):
+ pass
+@@ -732,7 +732,7 @@ class _Spatial_Smoother(_Smoother):
+ @classmethod
+ def by_col(cls, df, e,b, w=None, inplace=False, **kwargs):
+ """
+-Compute smoothing by columns in a dataframe. 
++Compute smoothing by columns in a dataframe.
+ 
+ Parameters
+ ---
+@@ -748,19 +748,19 @@ class _Spatial_Smoother(_Smoother):
+the spatial weights object or objects to use with the
+event-population pairs. If not provided and a weights 
object
+is in the dataframe's metadata, that weights object will be
+-   used. 
++   used.
+ inplace :  bool
+a flag denoting whether to output a copy of `df` with the
+relevant smoothed columns appended, or to append the 
columns
+-   directly to `df` itself. 
++   directly to `df` itself.
+ **kwargs:  optional keyword arguments
+optional keyword options th

Bug#853046: xserver-xorg-video-modesetting dependency issues

[Hans-J. Ullrich]

Source: xserver-xorg-video-modesetting
Severity: important

Dear Maintainer,

as xserver-xorg-video-modestting shall be the successor to 
xserver-xorg-video-intel, I am wondering, why it can not be installed.

I tried to install it, but due to several dependencies it will deinstall 
several applications (like Imagemagick). So, tI do not believe, the package is 
broken, just more are the dependencies.

My computer is running an Intel I945 graphics card, which is working with the 
xserver-xorg-video-intel driver, but as documented, this driver is declared as 
old and should be successed, with the modesetting one.

It would be nice, if you could take a look at that.

If you think (or define)  this is not a bug, please inform me and close this 
bugreport.

Thank you for your work.

Best regards

Hans


-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

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

Bug#852935: RFS: gnome-shell-extension-dash-to-panel/3-1 ITP: 852164 -- combines the dash and the GNOME main panel into a single panel

[Tobias Frost]

Control: tags -1 moreinfo

Hi Jonathan,

some work to be done... 

- the extension claims compatiblity with gnome-shell >=  3.18,
d/control says >= 3.16
- the license is GPL-2+ according to README.md and the source files.
- I think the people mentioned in the credits section of e.g panel.js
should also be mentioned as copyright owners, especially if code was
copied from them.
- The lintian override sounds actually like being an upstream bug: SW
should not crash when there is a directory missing. Please do not
override it but report it. Best thing, of course, patch it :)

--
tobi 

Bug#853048: O: socnetv -- social network analysis and visualisation application

[Serafeim Zanikolas]

Package: wnpp
Severity: normal

I intend to orphan the socnetv package.

The socnetv package has not been updated by its nominal maintainer in more
than three years, during which time there have been two NMUs (and I'm about to
make a third one).

The package description is:
 SocNetV is a graphical application designed to be an easy tool for Social
 Networks Analysis and Visualisation (not to be confused with social
 networking, as in online communities). With it, one can load and visualise
 networks of various formats (GraphViz, Adjacency, Pajek, etc), and/or visually
 create and modify a network in a point and click fashion.
 .
 The program can also compute network statistics and properties (such as
 distances, centralities, diameter) and apply some layout algorithms for more
 meaningful visualisation of your networks. Furthermore, socnetv can create
 simple random networks (lattice, same degree, etc).

Bug#853016: even stops apt

[Holger Levsen]

On Sun, Jan 29, 2017 at 09:57:02AM +0200, Arto Jantunen wrote:
> "You should not upgrade using telnet, rlogin, rsh, or from an X
> session managed by xdm, gdm or kdm etc. on the machine you are
> upgrading. 
 
noone should be using telnet, rlogin or rsh in 2017.

SCNR.


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#852936: RFS: catimg/2.2.1-1 ITP: 852878 -- fast image printing in to your terminal

[Tobias Frost]

Control: tags -1 moreinfo

Hi Jonathan,


- d/control Homepage field points to the tar.gz.. ;-)
- stb_image.h is public domain -- not mentioned in d/copyrihgt.

Otherwise it looks fine!

--
tobi

Bug#852732: [Pkg-privacy-maintainers] Bug#852732: torbrowser-launcher: upon upggrade 6.0.8 to 6.5: "SIGNATURE VERIFICATION FAILED: You might be under attack ..."

[Holger Levsen]

control: severity -1 serious
# completely breaks the package
control: found -1 0.1.9-1+deb8u3~bpo70+1
control: found -1 0.2.6-2~bpo8+1
control: found -1 0.2.6-3
control: forwarded -1 
https://github.com/micahflee/torbrowser-launcher/issues/260
thanks

Hi,

gpg --homedir "$HOME/.local/share/torbrowser/gnupg_homedir/" --refresh-keys 
--keyserver pgp.mit.edu

is a workaround, but I still think this is RC because how is a normal
user supposed to find this workaround… feel free to downgrade if you
disagree…


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#847700: kdenlive: I can't render ANY format

[Patrick Matthäi]

Am 24.01.2017 um 11:47 schrieb david:
> El martes 24 de enero, Patrick Matthäi escribió:
>> Hum. Could you please move away your cache and config data from kdenlive
>> (should be located in ~/.kdenlive ~/.cache ~/.local).
> I have deleted all kdenlive stuff inside .cache and .local. I don't see
> anything .kdenlive related; instead, I have deleted too .kde/share/apps.
>
> After all this, try with a render and this is kdenlive terminal output:
>
> --
> //STARTING RENDERING:  true , false , "/usr/bin/melt" , "dv_pal" , "avformat" 
> , "-" , "/tmp/kdenlive_rendering_Z30204.mlt" , 
> "/home/david/Documentos/marcoto.mp4" , () , ("glsl.=1", 
> "properties=x264-medium", "f=mp4", "vcodec=libx264", "acodec=aac", "g=120", 
> "crf=23", "ab=160k", "preset=faster", "progressive=1", "threads=4", 
> "real_time=-4") , 0 , 1545
> Skipped method "slotGotProgressInfo" : Type not registered with QtDBus in 
> parameter list: MessageType
> Skipped method "slotTimelineClipSelected" : Pointers are not supported: 
> ClipItem*
> Skipped method "slotTimelineClipSelected" : Pointers are not supported: 
> ClipItem*
> Unsupported return type 65 QPixmap in method "grab"
> Unsupported return type 65 QPixmap in method "grab"
> --
>
> Process seems locked with a "Remaining time 00:00:00". I can't see the result
> video.
>
>

If you save the project and then execute this:
$ melt ~/path/to/yourprojectfile/project.kdenlive

Does it play the whole project and what are the outputs of melt? You may
also use the -debug option



signature.asc
Description: OpenPGP digital signature

Bug#847700: kdenlive: I can't render ANY format

[david]

El domingo 29 de enero, Patrick Matthäi escribió:
> If you save the project and then execute this:
> $ melt ~/path/to/yourprojectfile/project.kdenlive
> 
> Does it play the whole project and what are the outputs of melt? You may
> also use the -debug option

It doesn't play it.

Here is the output:

--
+-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+
|1=-10| |2= -5| |3= -2| |4= -1| |5=  0| |6=  1| |7=  2| |8=  5| |9= 10|
+-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+
+-+
|   H = back 1 minute,  L = forward 1 minute  |
| h = previous frame,  l = next frame |
|   g = start of clip, j = next clip, k = previous clip   |
|0 = restart, q = quit, space = play  |
+-+
[mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0.
[mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0.
[mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0.
[mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0.
[mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0.
[mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0.
[mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0.
[mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0.
[mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0.
[mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0.
[mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0.
[mpegts @ 0x7f2f7000a040] Could not find codec parameters for stream 2 
(Unknown: none ([160][0][0][0] / 0x00A0)): unknown codec
Consider increasing the value for the 'analyzeduration' and 'probesize' options
[mpegts @ 0x7f2f7000a040] Could not find codec parameters for stream 3 
(Unknown: none ([161][0][0][0] / 0x00A1)): unknown codec
Consider increasing the value for the 'analyzeduration' and 'probesize' options
[mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0.
[mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0.
[mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0.
[mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0.
[mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0.
[mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0.
[mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0.
[mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0.
[mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0.
[mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0.
[mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0.
[mpegts @ 0x7f2f7002cbe0] Could not find codec parameters for stream 2 
(Unknown: none ([160][0][0][0] / 0x00A0)): unknown codec
Consider increasing the value for the 'analyzeduration' and 'probesize' options
[mpegts @ 0x7f2f7002cbe0] Could not find codec parameters for stream 3 
(Unknown: none ([161][0][0][0] / 0x00A1)): unknown codec
Consider increasing the value for the 'analyzeduration' and 'probesize' options
[mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0.
[mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0.
[mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0.
[mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0.
[mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0.
[mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0.
[mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0.
[mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0.
[mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0.
[mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0.
[mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0.
[mpegts @ 0x7f2f70045ce0] Could not find codec parameters for stream 2 
(Unknown: none ([160][0][0][0] / 0x00A0)): unknown codec
Consider increasing the value for the 'analyzeduration' and 'probesize' options
[mpegts @ 0x7f2f70045ce0] Could not find codec parameters for stream 3 
(Unknown: none ([161][0][0][0] / 0x00A1)): unknown codec
Consider increasing the value for the 'analyzeduration' and 'probesize' options
[filter avcolor_space] Invalid format glsl
[filter avcolor_space] Invalid format glsl
[filter avcolor_space] Invalid format glsl
Violación de segmento
--

-- 
David

Bug#853049: kded5 crashes nearly every time on copying files with dolphin

[Patrick Matthäi]

Subject: kded5 crashes nearly every time on copying files with dolphin
Package: kded5
Version: 5.28.0-1
Severity: important

Dear Maintainer,

nearly every time I'm moving/copying etc files with dolphin (so that the
activity manager starts working), kded5 crashes, which results in a not
working
(unresponsive) taskbar. To get it work again I always have to switch to
VT1 and
then back to VT7 (so a new kded5 spawns). I have got this issue now
since november.
Starting with a fresh profile or removing caches and settings does not help.
The only useful output is this from xsession-errors:

QXcbConnection: XCB error: 3 (BadWindow), sequence: 26736, resource id:
106954752, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 26757, resource id:
106954753, major code: 18 (ChangeProperty), minor code: 0
kdeinit5: Got EXEC_NEW
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so' from launcher.
kdeinit5: preparing to launch
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so'
kdeinit5: PID 2046 terminated.
QXcbConnection: XCB error: 3 (BadWindow), sequence: 28026, resource id:
106954758, major code: 15 (QueryTree), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 28160, resource id:
106954771, major code: 18 (ChangeProperty), minor code: 0
kdeinit5: PID 2234 terminated.
kdeinit5: PID 2241 terminated.
ark.main: "image/jpeg" is not a supported mimetype
ark.main: "image/jpeg" is not a supported mimetype
ark.main: "" is not a supported mimetype
QXcbConnection: XCB error: 3 (BadWindow), sequence: 42287, resource id:
96469035, major code: 2 (ChangeWindowAttributes), minor code: 0
kdeinit5: Got EXEC_NEW
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/thumbnail.so' from launcher.
kdeinit5: preparing to launch
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/thumbnail.so'
Qt: Session management error: networkIdsList argument is NULL
Wanting MIME Type: "image/jpeg"
Guess plugin:  "jpegthumbnail"
Wanting MIME Type: "image/jpeg"
Guess plugin:  "jpegthumbnail"
ark.main: "" is not a supported mimetype
Wanting MIME Type: "image/jpeg"
Guess plugin:  "jpegthumbnail"
Wanting MIME Type: "image/jpeg"
Guess plugin:  "jpegthumbnail"
Wanting MIME Type: "inode/directory"
Wanting MIME Type: "inode/directory"
Wanting MIME Type: "inode/directory"
Wanting MIME Type: "inode/directory"
Wanting MIME Type: "image/jpeg"
Guess plugin:  "jpegthumbnail"
Wanting MIME Type: "image/jpeg"
Guess plugin:  "jpegthumbnail"
kdeinit5: Got EXEC_NEW
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so' from launcher.
kdeinit5: preparing to launch
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so'
Wanting MIME Type: "image/jpeg"
Guess plugin:  "jpegthumbnail"
Wanting MIME Type: "image/jpeg"
Guess plugin:  "jpegthumbnail"
Wanting MIME Type: "image/jpeg"
Guess plugin:  "jpegthumbnail"
Wanting MIME Type: "image/jpeg"
Guess plugin:  "jpegthumbnail"
Wanting MIME Type: "inode/directory"
Wanting MIME Type: "inode/directory"
Wanting MIME Type: "inode/directory"
Wanting MIME Type: "inode/directory"
Wanting MIME Type: "inode/directory"
ark.main: "inode/directory" is not a supported mimetype
Wanting MIME Type: "inode/directory"
Wanting MIME Type: "inode/directory"
Wanting MIME Type: "inode/directory"
Wanting MIME Type: "inode/directory"
Wanting MIME Type: "inode/directory"
Wanting MIME Type: "inode/directory"
kdeinit5: PID 2049 terminated.
kdeinit5: PID 2249 terminated.
QXcbConnection: XCB error: 3 (BadWindow), sequence: 2780, resource id:
102767248, major code: 18 (ChangeProperty), minor code: 0
kdeinit5: PID 2047 terminated.
kdeinit5: PID 2107 terminated.
QXcbConnection: XCB error: 3 (BadWindow), sequence: 2785, resource id:
98566148, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 3619, resource id:
96469064, major code: 18 (ChangeProperty), minor code: 0
kdeinit5: PID 1597 terminated.
QXcbConnection: XCB error: 3 (BadWindow), sequence: 3627, resource id:
106954756, major code: 18 (ChangeProperty), minor code: 0
kdeinit5: PID 1648 terminated.
kdeinit5: PID 2115 terminated.
kdeinit5: PID 2233 terminated.
kdeinit5: PID 2246 terminated.
QXcbConnection: XCB error: 3 (BadWindow), sequence: 5519, resource id:
39890793, major code: 20 (GetProperty), minor code: 0
QDBusAbstractAdaptor: Cannot relay signal
KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported:
KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal
KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported:
KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal
KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported:
KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal
KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported:
KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal
KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported:
KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal
KDEDModule::moduleDeleted(KDEDModule*): Pointers are not 

Bug#852811: udev: Doesn't start after upgrade

[Teemu Ikonen]

Package: udev
Version: 232-14
Followup-For: Bug #852811

I got same behaviour from udev as Christian on i386 (Apple MacBook2,1).
Commenting out the lines mentioned above in systemd-udevd.service made
udev start.

The problem was version mismatch with udev (232-14) and systemd (232-8).
systemd upgrade was for some reason kept back by 'apt upgrade'. When I
installed the systemd 232-14, udev started with the original service
file.

Maybe udev should depend on the exact same version of systemd?

-- Package-specific info:

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)

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

Versions of packages udev depends on:
ii  adduser  3.115
ii  dpkg 1.18.18
ii  libacl1  2.2.52-3
ii  libblkid12.29-1
ii  libc62.24-8
ii  libgcc1  1:6.2.1-5
ii  libkmod2 23-2
ii  libselinux1  2.6-3
ii  libudev1 232-14
ii  lsb-base 9.20161125
ii  procps   2:3.3.12-3
ii  util-linux   2.29-1

udev recommends no packages.

udev suggests no packages.

Versions of packages udev is related to:
ii  systemd  232-8

-- debconf information:
  udev/sysfs_deprecated_incompatibility:
  udev/title/upgrade:
  udev/new_kernel_needed: false
  udev/reboot_needed:
P: /devices/LNXSYSTM:00
E: DEVPATH=/devices/LNXSYSTM:00
E: ID_VENDOR_FROM_DATABASE=The Linux Foundation
E: MODALIAS=acpi:LNXSYSTM:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=4662992

P: /devices/LNXSYSTM:00/LNXCPU:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:00
E: ID_VENDOR_FROM_DATABASE=The Linux Foundation
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=4724576

P: /devices/LNXSYSTM:00/LNXCPU:01
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:01
E: ID_VENDOR_FROM_DATABASE=The Linux Foundation
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=4670326

P: /devices/LNXSYSTM:00/LNXPWRBN:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00
E: DRIVER=button
E: ID_VENDOR_FROM_DATABASE=The Linux Foundation
E: MODALIAS=acpi:LNXPWRBN:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=4664493

P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input6
E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input6
E: EV=3
E: ID_FOR_SEAT=input-acpi-LNXPWRBN_00
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=acpi-LNXPWRBN:00
E: ID_PATH_TAG=acpi-LNXPWRBN_00
E: KEY=10 0 0 0
E: MODALIAS=input:b0019vp0001e-e0,1,k74,ramlsfw
E: NAME="Power Button"
E: PHYS="LNXPWRBN/button/input0"
E: PRODUCT=19/0/1/0
E: PROP=0
E: SUBSYSTEM=input
E: TAGS=:seat:
E: USEC_INITIALIZED=5344727

P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input6/event6
N: input/event6
E: BACKSPACE=guess
E: DEVNAME=/dev/input/event6
E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input6/event6
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=acpi-LNXPWRBN:00
E: ID_PATH_TAG=acpi-LNXPWRBN_00
E: LIBINPUT_DEVICE_GROUP=19/0/1/0:LNXPWRBN/button
E: MAJOR=13
E: MINOR=70
E: SUBSYSTEM=input
E: TAGS=:power-switch:
E: USEC_INITIALIZED=5458202
E: XKBLAYOUT=fi
E: XKBMODEL=pc105

P: /devices/LNXSYSTM:00/LNXSYBUS:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00
E: ID_VENDOR_FROM_DATABASE=The Linux Foundation
E: MODALIAS=acpi:LNXSYBUS:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=4669272

P: /devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0003:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0003:00
E: DRIVER=ac
E: ID_VENDOR_FROM_DATABASE=The Linux Foundation
E: MODALIAS=acpi:ACPI0003:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=4679822

P: /devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0003:00/power_supply/ADP1
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0003:00/power_supply/ADP1
E: POWER_SUPPLY_NAME=ADP1
E: POWER_SUPPLY_ONLINE=1
E: SUBSYSTEM=power_supply

P: /devices/LNXSYSTM:00/LNXSYBUS:00/APP0002:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/APP0002:00
E: ID_VENDOR_FROM_DATABASE=Apple Computer Inc
E: MODALIAS=acpi:APP0002:BACKLIGHT:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=4690649

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00
E: ID_VENDOR_FROM_DATABASE=The Linux Foundation
E: MODALIAS=acpi:PNP0A08:PNP0A03:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=4682175

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00
E: DRIVER=video
E: ID_VENDOR_FROM_DATABASE=The Linux Foundation
E: MODALIAS=acpi:LNXVIDEO:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=4683460

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/device:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/device:00
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/device:01
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/device:01
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/device:02
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0

Bug#847700: kdenlive: I can't render ANY format

[Patrick Matthäi]

Could you send me the project (short clip and the project file) so I can
test it?

Did you ever installed something from other sources then Debian itself?
Most bugs like this come from faulty external libs..

And the full output of "dpkg -l" and "apt-cache policy" would be good


Am 29.01.2017 um 11:54 schrieb david:
> El domingo 29 de enero, Patrick Matthäi escribió:
>> If you save the project and then execute this:
>> $ melt ~/path/to/yourprojectfile/project.kdenlive
>>
>> Does it play the whole project and what are the outputs of melt? You may
>> also use the -debug option
> It doesn't play it.
>
> Here is the output:
>
> --
> +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+
> |1=-10| |2= -5| |3= -2| |4= -1| |5=  0| |6=  1| |7=  2| |8=  5| |9= 10|
> +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+
> +-+
> |   H = back 1 minute,  L = forward 1 minute  |
> | h = previous frame,  l = next frame |
> |   g = start of clip, j = next clip, k = previous clip   |
> |0 = restart, q = quit, space = play  |
> +-+
> [mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0.
> [mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0.
> [mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0.
> [mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0.
> [mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0.
> [mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0.
> [mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0.
> [mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0.
> [mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0.
> [mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0.
> [mpeg2video @ 0x7f2f7000eb40] Invalid frame dimensions 0x0.
> [mpegts @ 0x7f2f7000a040] Could not find codec parameters for stream 2 
> (Unknown: none ([160][0][0][0] / 0x00A0)): unknown codec
> Consider increasing the value for the 'analyzeduration' and 'probesize' 
> options
> [mpegts @ 0x7f2f7000a040] Could not find codec parameters for stream 3 
> (Unknown: none ([161][0][0][0] / 0x00A1)): unknown codec
> Consider increasing the value for the 'analyzeduration' and 'probesize' 
> options
> [mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0.
> [mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0.
> [mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0.
> [mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0.
> [mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0.
> [mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0.
> [mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0.
> [mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0.
> [mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0.
> [mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0.
> [mpeg2video @ 0x7f2f70031380] Invalid frame dimensions 0x0.
> [mpegts @ 0x7f2f7002cbe0] Could not find codec parameters for stream 2 
> (Unknown: none ([160][0][0][0] / 0x00A0)): unknown codec
> Consider increasing the value for the 'analyzeduration' and 'probesize' 
> options
> [mpegts @ 0x7f2f7002cbe0] Could not find codec parameters for stream 3 
> (Unknown: none ([161][0][0][0] / 0x00A1)): unknown codec
> Consider increasing the value for the 'analyzeduration' and 'probesize' 
> options
> [mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0.
> [mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0.
> [mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0.
> [mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0.
> [mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0.
> [mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0.
> [mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0.
> [mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0.
> [mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0.
> [mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0.
> [mpeg2video @ 0x7f2f70040920] Invalid frame dimensions 0x0.
> [mpegts @ 0x7f2f70045ce0] Could not find codec parameters for stream 2 
> (Unknown: none ([160][0][0][0] / 0x00A0)): unknown codec
> Consider increasing the value for the 'analyzeduration' and 'probesize' 
> options
> [mpegts @ 0x7f2f70045ce0] Could not find codec parameters for stream 3 
> (Unknown: none ([161][0][0][0] / 0x00A1)): unknown codec
> Consider increasing the value for the 'analyzeduration' and 'probesize' 
> options
> [filter avcolor_space] Invalid format glsl
> [filter avcolor_space] Invalid format glsl
> [filter avcolor_space] Invalid format glsl
> Violación de segmento
> --
>

Bug#851742: unblock: libhttp-daemon-ssl-perl/1.04-3.1

[Jonathan Wiltshire]

Control: tag -1 moreinfo

Hi,

On Wed, Jan 18, 2017 at 12:28:03PM +0100, Mike Gabriel wrote:
> Please unblock package libhttp-daemon-ssl-perl.

I'm not wild about it. What is the impact on Fusion Directory?

Thanks,

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

Bug#853028: [Pkg-cmake-team] Bug#853028: cmake does not find bzip2 (libbz2)

[Felix Geyer]

Hi,

On 29.01.2017 02:45, enrico wrote:
> Package: cmake
> Version: 3.7.2-1
> Severity: normal
> 
> Dear Maintainer,
> 
> Cmake can't find libbz2, nor by using find_package(BZip2) nor using 
> find_library(). The cmake module is is the one shipped with cmake-data I 
> think.
> libbz2 is found at /lib/x86_64-linux-gnu/ and linking the so manually into 
> /usr/lib/x86_64-linux-gnu/ seems to work.
> 
> Look at CMakeFiles/CMakeOutput.txt,the LIBRARY_PATH variable seems to be 
> correct
> 
> LIBRARY_PATH=/usr/lib/gcc/x86_64-linux-gnu/6/:/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/6/../../../../lib/:/lib/x86_64-linux-gnu/:/lib/../lib/:/usr/lib/x86_64-linux-gnu/:/usr/lib/../lib/:/usr/lib/gcc/x86_64-linux-gnu/6/../../../:/lib/:/usr/lib/
> 
> I guess that something is wrong with find_library.
> What would be the preferred work around for this?

Works fine here (and in the automated tests).

Can you please test this in a fresh project that just contains 
"find_package(BZip2)"?

Felix

Bug#844146: libmicrohttpd: FTBFS: Tests failures

[Simon McVittie]

Control: tags 844146 + buster
Control: tags 844146 - stretch

On Sat, 12 Nov 2016 at 21:08:02 +0100, Lucas Nussbaum wrote:
> This failure happens on a CPU with TSX extensions available, but is not
> reproducible on a machine without them.

If my understanding of TSX (as discussed with the Cambridge BSP) is
correct, this is not release-critical for stretch, because glibc/2.24-9
has disabled lock elision and is meant to migrate to stretch soon. It is
likely to be release-critical for buster (assuming the glibc maintainers
want to re-enable that feature as hardware supporting it becomes more
common) so I'm tagging it buster,sid with release team approval (jmw).

Lucas, would it be possible for you to retry your test-build of
libmicrohttpd on a TSX machine, and perhaps also the other packages that
had failures on TSX machines that were not reproducible without TSX?
You will need to either do the build in sid, or wait for glibc (>= 2.24-9)
to hit stretch.

Thanks,
S
at the distributed version of the Cambridge BSP

Bug#771441: [PATCH tftpd-hpa] tftpd: don't use AI_CANONNAME and AI_ADDRCONFIG to resolve addresses for bind

[Uwe Kleine-König]

AI_CANONNAME is only relevant when the resulting official name is used,
which is not the case in tftpd for the address to bind to. Also
AI_ADDRCONFIG isn't helpful. This flag is good for sockets used to
connect(2) somewhere. But for listening sockets it makes tftpd fail to
start when -a 0.0.0.0:69 is passed and no network device is up yet.

This addresses Debian bug https://bugs.debian.org/771441
---
 common/tftpsubs.c | 4 ++--
 common/tftpsubs.h | 2 +-
 tftp/main.c   | 9 ++---
 tftpd/tftpd.c | 6 --
 4 files changed, 13 insertions(+), 8 deletions(-)

diff --git a/common/tftpsubs.c b/common/tftpsubs.c
index 8c999f66eed8..344c74b3d78c 100644
--- a/common/tftpsubs.c
+++ b/common/tftpsubs.c
@@ -300,7 +300,7 @@ int pick_port_bind(int sockfd, union sock_addr *myaddr,
 }
 
 int
-set_sock_addr(char *host,union sock_addr  *s, char **name)
+set_sock_addr(char *host, union sock_addr *s, char **name, int ai_flags)
 {
 struct addrinfo *addrResult;
 struct addrinfo hints;
@@ -308,7 +308,7 @@ set_sock_addr(char *host,union sock_addr  *s, char **name)
 
 memset(&hints, 0, sizeof(hints));
 hints.ai_family = s->sa.sa_family;
-hints.ai_flags = AI_CANONNAME | AI_ADDRCONFIG;
+hints.ai_flags = ai_flags;
 hints.ai_socktype = SOCK_DGRAM;
 hints.ai_protocol = IPPROTO_UDP;
 err = getaddrinfo(strip_address(host), NULL, &hints, &addrResult);
diff --git a/common/tftpsubs.h b/common/tftpsubs.h
index b3a3bf3c95e1..0edda03a514c 100644
--- a/common/tftpsubs.h
+++ b/common/tftpsubs.h
@@ -98,7 +98,7 @@ static inline int sa_set_port(union sock_addr *s, u_short 
port)
return 0;
 }
 
-int set_sock_addr(char *, union sock_addr *, char **);
+int set_sock_addr(char *, union sock_addr *, char **, int);
 
 struct tftphdr;
 
diff --git a/tftp/main.c b/tftp/main.c
index b2f90593ed31..4aebe630af1e 100644
--- a/tftp/main.c
+++ b/tftp/main.c
@@ -414,7 +414,8 @@ void setpeer(int argc, char *argv[])
 }
 
 peeraddr.sa.sa_family = ai_fam;
-err = set_sock_addr(argv[1], &peeraddr, &hostname);
+err = set_sock_addr(argv[1], &peeraddr, &hostname,
+AI_CANONNAME | AI_ADDRCONFIG);
 if (err) {
 printf("Error: %s\n", gai_strerror(err));
 printf("%s: unknown host\n", argv[1]);
@@ -557,7 +558,8 @@ void put(int argc, char *argv[])
 targ = strchr(cp, ':');
 *targ++ = 0;
 peeraddr.sa.sa_family = ai_fam;
-err = set_sock_addr(cp, &peeraddr,&hostname);
+err = set_sock_addr(cp, &peeraddr, &hostname,
+AI_CANONNAME | AI_ADDRCONFIG);
 if (err) {
 printf("Error: %s\n", gai_strerror(err));
 printf("%s: unknown host\n", argv[1]);
@@ -648,7 +650,8 @@ void get(int argc, char *argv[])
 
 *src++ = 0;
 peeraddr.sa.sa_family = ai_fam;
-err = set_sock_addr(argv[n], &peeraddr, &hostname);
+err = set_sock_addr(argv[n], &peeraddr, &hostname,
+AI_CANONNAME | AI_ADDRCONFIG);
 if (err) {
 printf("Warning: %s\n", gai_strerror(err));
 printf("%s: unknown host\n", argv[1]);
diff --git a/tftpd/tftpd.c b/tftpd/tftpd.c
index 364e7d2303e0..db22426edbb9 100644
--- a/tftpd/tftpd.c
+++ b/tftpd/tftpd.c
@@ -638,7 +638,8 @@ int main(int argc, char **argv)
 if (fd4 >= 0) {
 bindaddr4.sin_family = AF_INET;
 err = set_sock_addr(address,
-(union sock_addr *)&bindaddr4, NULL);
+(union sock_addr *)&bindaddr4, NULL,
+AI_PASSIVE);
 if (err) {
 syslog(LOG_ERR,
"cannot resolve local IPv4 bind address: %s, 
%s",
@@ -650,7 +651,8 @@ int main(int argc, char **argv)
 if (fd6 >= 0) {
 bindaddr6.sin6_family = AF_INET6;
 err = set_sock_addr(address,
-(union sock_addr *)&bindaddr6, NULL);
+(union sock_addr *)&bindaddr6, NULL,
+AI_PASSIVE);
 if (err) {
 if (fd4 >= 0) {
 syslog(LOG_ERR,
-- 
2.11.0

Bug#852008: Bug#853008: mysql-server-5.7: purge could delete mariadb-server files with inadequate warning

[Julian Gilbey]

On Sat, Jan 28, 2017 at 09:21:13PM +, Julian Gilbey wrote:
> Package: mysql-server-5.7
> Version: 5.7.16-2
> Severity: serious
> 
> Hello!
> 
> I'm really confused by the change in the postrm introduced in response
> to LP: #1602945, and I simply do not understand the rationale of the
> original bug report, and the comment there (and in the git commit log)
> that "Remove the check on the server binary, since it shouldn't be
> possible for another package to own that file anyway" is clearly
> incorrect: during a postrm remove|purge run, if that file exists -
> which it may well do, it will certainly belong to a different package,
> such as mysql-server-5.8 or mariadb-server-10.1.

And looking at the existing postrms, I see that this is effectively
just Debian bug #307473 reopened.  That was regarded as critical!

Best wishes,

   Julian

Bug#853050: unblock: botch/0.21-3

[Johannes Schauer]

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

Please unblock package botch

Yesterday, an FTBFS bug against botch was reported: #852917

I fixed the problem and uploaded to unstable. Since it's too late for
the 10 day package transition to testing until February 5, I hereby
request its unblock.

Attached is the patch that fixes the FTBFS bug. It makes botch
compatible with changes introduced by a dose3 upload 10 days ago. This
is why the problem with botch wasn't spotted earlier. The patch seems
long but it only touches the relevant parts. Despite its size I think
it's safe because:

 - buildcheck-more-problems.ml: that file is a copy of a file from dose3
   with custom changes which just needed rebasing
 - bin2src.ml, src2bin.ml: just blacklisted an otherwise auto-generated
   command line option
 - doc/man/botch-*.pod: just updates to man pages which are necessary
   because the test suite checks that the --help output of the
   respective programs agrees with the man page. The --help output is
   autogenerated and was influenced by said dose3 upload.
 - tools/debarch.py: update to support dpkg debtuples. This file is a
   copy from a test suite I maintain that checks dpkg architecture
   wildcard matching between dpkg, dose3 and apt on the basis of
   17591105 testcases. I thus have reason to believe that its behaviour
   is correct.

Furthermore, the following datapoints:

 - the package built successfully on all architectures
   https://buildd.debian.org/status/package.php?p=botch
 - the package succeeds its autopkgtests
   https://ci.debian.net/packages/b/botch/unstable/amd64/
 - the compile time checks and runtime tests are very extensive (take 40
   minutes each on my machine). That the former succeed on all
   architectures and that the latter succeed on the Debian ci
   infrastructure give me reason to believe that the patch doesn't break
   anything important in the package itself.
 - the package has no reverse dependencies so it cannot break anything
   anywhere else

Lastly, botch is currently blocking the transition of the new dose3
version. Because botch and dose3 are written in OCaml botch depends on
the exact version of dose3. Thus, since botch in testing would become
uninstallable if dose3 from unstable transitioned, dose3 is currently
blocked from transitioning even though its 10 day delay is over. Making
a binNMU of botch against the new dose3 version was impossible due to
this FTBFS bug.

If this patch making botch 0.21-3 become part of testing cannot be
accepted, then it makes sense to remove botch from testing so that dose3
can be part of it.

unblock botch/0.21-3
diff -Nru botch-0.21/debian/changelog botch-0.21/debian/changelog
--- botch-0.21/debian/changelog 2017-01-09 13:16:33.0 +0100
+++ botch-0.21/debian/changelog 2017-01-28 23:32:39.0 +0100
@@ -1,3 +1,10 @@
+botch (0.21-3) unstable; urgency=medium
+
+  * Add patch to fix FTBFS due to API breakage introduced by src:dose3 5.0.1-8
+(closes: #852917)
+
+ -- Johannes Schauer   Sat, 28 Jan 2017 23:32:39 +0100
+
 botch (0.21-2) unstable; urgency=medium
 
   * python3-pygraphviz dropped the file attribute. Thus adapting the code
diff -Nru botch-0.21/debian/patches/add-patch-to-fix-ftbfs-due-to-api-breaka 
botch-0.21/debian/patches/add-patch-to-fix-ftbfs-due-to-api-breaka
--- botch-0.21/debian/patches/add-patch-to-fix-ftbfs-due-to-api-breaka  
1970-01-01 01:00:00.0 +0100
+++ botch-0.21/debian/patches/add-patch-to-fix-ftbfs-due-to-api-breaka  
2017-01-28 22:47:50.0 +0100
@@ -0,0 +1,336 @@
+From: Johannes Schauer 
+Date: Sat, 28 Jan 2017 10:26:13 +0100
+X-Dgit-Generated: 0.21-3 e3fbc643e6af55da3b9b547e41d6189a7fed4c7e
+Subject: Add patch to fix FTBFS due to API breakage introduced by src:dose3 
5.0.1-8 (closes: #852917)
+
+
+---
+
+--- botch-0.21.orig/bin2src.ml
 botch-0.21/bin2src.ml
+@@ -49,7 +49,7 @@ module Options = struct
+   StdOptions.OutputOptions.add_options ~default options;;
+ 
+   include StdOptions.DistribOptions;;
+-  let default = List.filter (fun e -> not (List.mem e ["deb-drop-b-d-indep"; 
"deb-profiles"; "deb-ignore-essential"; "deb-builds-from"])) 
StdOptions.DistribOptions.default_options in
++  let default = List.filter (fun e -> not (List.mem e ["deb-drop-b-d-indep"; 
"deb-drop-b-d-arch"; "deb-profiles"; "deb-ignore-essential"; 
"deb-builds-from"])) StdOptions.DistribOptions.default_options in
+   StdOptions.DistribOptions.add_debian_options ~default options ;;
+ end
+ 
+--- botch-0.21.orig/buildcheck-more-problems.ml
 botch-0.21/buildcheck-more-problems.ml
+@@ -32,7 +32,7 @@ module Options = struct
+   let dump = StdOpt.str_option ()
+   let maforeign = StdOpt.store_true ()
+   let includextra = StdOpt.store_true ()
+-  let triplettable = StdOpt.str_option ()
++  let tupletable = StdOpt.str_option ()
+   let cputable = StdOpt.str_option ()
+   let dropalternatives = StdOpt.store_true ()
+ 
+@@ -54,8 +54,8 @@ mo

Bug#848574: mpgrafic-0.3.7.8-1 and 0.3.10-1 mips64el builds seg-faulted too

[Boud Roukema]

This may affect mpgrafic, which depends on mpi-default-dev and
mpi-default-bin, i.e. effectively on openmpi.

mipsel-manda-01 (mips64el) had a segmentation violation fault for the
code regression test on mpgrafic-0.3.10-1 and 0.3.7.8-1:

https://buildd.debian.org/status/logs.php?pkg=mpgrafic&arch=mips64el

but two other mipsel/mips64el machines built successfully with
mpgrafic-0.3.8-1 and mpgrafic-0.3.9-1.

https://buildd.debian.org/status/fetch.php?pkg=mpgrafic&arch=mips64el&ver=0.3.10-1&stamp=1485682537&raw=0

This looks like a debian openmpi system.

Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

Backtrace for this error:
#0  0xffe95a70a3 in ???
--
mpirun noticed that process rank 0 with PID 0 on node mipsel-manda-01 exited on 
signal 11 (Segmentation fault).

Bug#796636: oss4-base: Has init script in runlevel S but no matching service file

[Simon McVittie]

Control: tags 796636 + patch

On Sat, 22 Aug 2015 at 22:52:00 -0300, fsate...@debian.org wrote:
> Please add a systemd unit for the given service with the appropriate
> dependencies, which most of the time will be less strict than
> Before=sysinit.target.

The attached (which also includes Andy Whitcroft's patch for #829255)
seems to load modules as desired, and preserves the spirit of being an
rcS (early-boot) service. No debian/rules changes are necessary for
dh_systemd, since cdbs uses it automatically if present.

However, on my test system (a Lenovo X200s with Intel 82801I (ICH9) HD Audio)
I was unable to get ossplay to produce sounds via OSS4; it pauses for
about the right length of time for the length of the audio clip
(I used /usr/share/sounds/alsa/Front_Center.wav, which is 48kHz 16-bit mono)
but I don't hear anything. The same hardware using aplay and ALSA was fine,
and produced a sound.

I am *not* going to NMU this, because I wasn't able to test it successfully
on this very common laptop hardware.

I discussed this with release team members and we reached consensus
that Linux packages should not build-depend on OSS4, taking OSS4 out
of the key packages set. If OSS4 is useful on kFreeBSD and/or Hurd, it can
be used there; but Linux has an in-tree kernel API (ALSA) that works,
and sticking to what's in-tree will give us a less fragile release process.

Regards,
S
non-geographically at the Cambridge BSP

Bug#653263: lilypond: list lilypond-doc as suggested, not recommended, package

[Anthony Fok]

Control: tags -1 - wontfix + pending

Hello Bill and Petter,

Thank you for your suggestion and the patch.

I agree with you, as I often find myself searching on Google and
reaching LilyPond's on-line documentation, and seldom, if ever,
consult the locally installed LilyPond documentation.

So yes, let's change "Recommends: lilypond-doc" to "Suggests: lilypond-doc"!

Cheers,
Anthony

Bug#851909: (no subject)

[Nicola Mori]

--
Nicola Mori, Ph.D.
University of Florence and INFN Florence
Via Bruno Rossi 1, 50019 Sesto F.no (Italy)
+390554572660
m...@fi.infn.it



smime.p7s
Description: S/MIME Cryptographic Signature

Bug#665334: non-DFSG & Type 1 Postscript embedded fonts

[Andy Simpkins]

Hi Karen,

At the Cambridge BSP (Jan 27/28 2017) we have been looking at the
following bugs pertaining to non-DFSG compliance with fonts embedded
with non-free code:
 * http://bugs.debian.org/665334
 opened 23 Mar 2012, last update 01 Aug 2016 modulo spam
 * http://bugs.debian.org/694320
 opened 25 Nov 2012, last update 30 Aug 2014
 blocked by #665334
 * http://bugs.debian.org/694323
 opened 25 Nov 2012, last update 30 Aug 2014
 blocked by #665334

Synopsis:
  Type 1 fonts that are made using the package FontForge include font
hinting code which is marked "copyright Adobe all rights reserved".
This issue logically extends to every package that contains fonts that
have been made using FontForge.

Current State
  Reading #665334 it appears that FontForge historically contained
fragments of code with Adobe asserted rights.  We believe that this is
now resolved with "autohint code is now all open source".  The github
repo is top licensed Apache 2.0  [1]

  It is our belief that this is sufficient; that the package FontForge,
and type 1 fonts generated by this package are now DFSG compliant
because Apache 2.0 is GPL2+ compatible.

* Is our understanding of the above correct? i.e. Does the github
repository top-licensing (to Apache) of the Adobe 'hinting' properly apply?

* Are the font hinting fragments, that are Adobe copyright, embedded
into fonts produced in FontForge, the same code as in the above
repository (we *think* that this is the case)?

* Thus, are these fonts (generated by the above) now covered by Apache 2.0?

* And, consequently: are the fonts in the Debian archive, produced by
FontForge, now to be considered under Apache 2.0; and is this sufficient
to cover the embedded fragments under Apache 2.0?

Assuming the above is all correct then, in order to resolve this issue,
we believe that all packages that contain fonts that are generated using
FontForge should contain an appropriate licence text for the font.  A
Mass bug filing could then be made against these packages requesting the
appropriate update to the licence file.


However we see this a potential minefield, and therefore seek
clarification and advice before we continue.


/Andy
PP Debian BSP Cambridge Jan 2017 [2]


[1]  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665334#168
[2]  https://wiki.debian.org/BSP/2017/01/gb/Cambridge



signature.asc
Description: OpenPGP digital signature

Bug#853051: electric-fence FTCBFS: uses the build architecture compiler, runs tests despite DEB_BUILD_OPTIONS=nocheck

[Helmut Grohne]

Source: electric-fence
Version: 2.2.4
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

electric-fence fails to cross build from source, because it uses the
build architecture compiler and runs test despite setting
DEB_BUILD_OPTIONS=nocheck. The attached patch solves both issues (the
former by deferring to dh_auto_build, which knows how to pass cross
compilers for the makefile buildsystem). Please consider applying it.

Helmut
diff --minimal -Nru electric-fence-2.2.4/debian/changelog 
electric-fence-2.2.4+nmu1/debian/changelog
--- electric-fence-2.2.4/debian/changelog   2012-07-17 19:40:21.0 
+0200
+++ electric-fence-2.2.4+nmu1/debian/changelog  2017-01-29 11:10:54.0 
+0100
@@ -1,3 +1,12 @@
+electric-fence (2.2.4+nmu1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ Let dh_auto_build pass cross compilers
++ Honour DEB_BUILD_OPTIONS=nocheck
+
+ -- Helmut Grohne   Sun, 29 Jan 2017 11:10:54 +0100
+
 electric-fence (2.2.4) unstable; urgency=medium (high for hurd users)
 
   * Patch from Richard Kettlewell to improve the semaphore strategy of
diff --minimal -Nru electric-fence-2.2.4/debian/rules 
electric-fence-2.2.4+nmu1/debian/rules
--- electric-fence-2.2.4/debian/rules   2012-07-02 19:57:37.0 +0200
+++ electric-fence-2.2.4+nmu1/debian/rules  2017-01-29 11:10:54.0 
+0100
@@ -17,7 +17,10 @@
 build: build-stamp
 build-stamp:
dh_testdir
-   make
+   dh_auto_build -- libefence.a libefence.so.0.0
+ifeq ($(filter nocheck,$(DEB_BUILD_OPTIONS)),)
+   dh_auto_build # default make target runs tests
+endif
touch build-stamp
 
 clean:

Bug#853050: unblock: botch/0.21-3

[Mattia Rizzolo]

On Sun, Jan 29, 2017 at 12:22:30PM +0100, Johannes Schauer wrote:
> Yesterday, an FTBFS bug against botch was reported: #852917
> 
> I fixed the problem and uploaded to unstable. Since it's too late for
> the 10 day package transition to testing until February 5, I hereby
> request its unblock.

the last dose3 upload didn't migrate until now due to botch not being
rebuilt.  Due to this botch upload an unblock is necessary for dose3
too.

> unblock botch/0.21-3
unblock dose3/5.0.1-8

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#852013: Patch to prevent segfaults on signal

[Ximin Luo]

Brett Smith:
> [..]
> 
> I've also attached a script I used to help reproduce the issue.  It
> doesn't do so reliably, and it's not totally robust itself, but I found
> it more reliable than trying to time timeout or a ^C right.
> 
> [..]

Hey Brett, could you also upload the ink*.tar files somewhere please? I'll try 
to investigate this in more detail next week as well.

X

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Bug#853050: unblock: botch/0.21-3

[Jonathan Wiltshire]

On 2017-01-29 11:44, Mattia Rizzolo wrote:

On Sun, Jan 29, 2017 at 12:22:30PM +0100, Johannes Schauer wrote:

Yesterday, an FTBFS bug against botch was reported: #852917

I fixed the problem and uploaded to unstable. Since it's too late for
the 10 day package transition to testing until February 5, I hereby
request its unblock.


the last dose3 upload didn't migrate until now due to botch not being
rebuilt.  Due to this botch upload an unblock is necessary for dose3
too.



No, it is not required.

--
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

 i have six years of solaris sysadmin experience, from
8->10. i am well qualified to say it is made from bonghits
layered on top of bonghits

Bug#828376: OpenSSL: The LCMAPS/VOMS/Globus cluster

[Dennis van Dok]

On 28-01-17 14:38, Adrian Bunk wrote:
> Hi,
> 
> #828375 lcmaps-plugins-verify-proxy: FTBFS with openssl 1.1.0
> #828376 lcmaps-plugins-voms: FTBFS with openssl 1.1.0
> 
> When trying to fix these FTBFS with OpenSSL 1.1 by switching LCMAPS to 
> 1.0.2 I end up also moving VOMS and Globus to OpenSSL 1.0.2
> 
> Is this the way to forward, or is there a better solution available
> for lcmaps-plugins-verify-proxy and lcmaps-plugins-voms in stretch?

It's not the way forward; globus has already been updated for openssl
1.1 and everything that uses it (voms, lcmaps) needs to be on the same
version or there will be runtime mayhem.

The fix for voms came just a few days ago, but now at least
lcmaps-plugins-verify proxy should be fixed as well. If it's not in
unstable yet it's there on Debian Mentors[1].

1. https://mentors.debian.net/package/lcmaps-plugins-verify-proxy

I've contacted our regular sponsor to upload it.

Cheers,

Dennis

Bug#851742: unblock: libhttp-daemon-ssl-perl/1.04-3.1

[Mike Gabriel]

Hi Jonathan,

On  So 29 Jan 2017 12:01:35 CET, Jonathan Wiltshire wrote:


Control: tag -1 moreinfo

Hi,

On Wed, Jan 18, 2017 at 12:28:03PM +0100, Mike Gabriel wrote:

Please unblock package libhttp-daemon-ssl-perl.


I'm not wild about it. What is the impact on Fusion Directory?


Thanks for even considering an unblock. The impact on FD is that  
Debian 9 will ship an old Argonaut version. I have Cc:ed upstream via  
our maintenance mailing list and leave it to Benoit giving a detailed  
answer to your question.


In general, Fusion Directory and Argonaut development happens hand in  
hand in the same upstream context. For projects being co-developed in  
such a way, my overall experience is to always ship the versions that  
have been released together. For FD/Argonaut as of now, this is: FD  
1.0.19 +  Argonaut 1.0.


Expecting an answer given in more technical depth from Benoit (Fusion  
Directoy / Argonaut upstream lead).


Greets,
Mike

--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgp4MoXplfgfL.pgp
Description: Digitale PGP-Signatur

Bug#853008: mysql-server-5.7: purge could delete mariadb-server files with inadequate warning

[Julian Gilbey]

On Sat, Jan 28, 2017 at 09:21:13PM +, Julian Gilbey wrote:
> Package: mysql-server-5.7
> Version: 5.7.16-2
> Severity: serious
> 
> Hello!
> 
> I'm really confused by the change in the postrm introduced in response
> to LP: #1602945, and I simply do not understand the rationale of the
> original bug report, and the comment there (and in the git commit log)
> that "Remove the check on the server binary, since it shouldn't be
> possible for another package to own that file anyway" is clearly
> incorrect: during a postrm remove|purge run, if that file exists -
> which it may well do, it will certainly belong to a different package,
> such as mysql-server-5.8 or mariadb-server-10.1.

And looking at the existing postrms, I see that this is effectively
just Debian bug #307473 reopened.  That was regarded as critical!

Best wishes,

   Julian

Bug#852008: gprolog: non-standard gcc/g++ used for build (gcc-5)

[Adrian Bunk]

On Fri, Jan 27, 2017 at 11:14:23AM +, James Cowgill wrote:
> On Fri, 20 Jan 2017 18:21:39 +0100 Matthias Klose  wrote:
> > Package: src:gprolog
> > Version: 1.4.5-4
> > Severity: serious
> > Tags: sid stretch
> > User: debian-...@lists.debian.org
> > Usertags: non-standard-compiler, gcc-5, gcc-5-legacy
> > 
> > This package builds with a non standard compiler version; please check
> > if this package can be built with the default version of gcc/g++, or
> > with gcc-6/g++-6.
> 
> It looks like the original GCC ICE (which is the reason gcc-5 is used)
> might be this upstream bug:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78580
> 
> However it is only fixed in gcc-7 at the moment.

You found the correct upstream bug (thanks!), but it seems this is not
sufficient for building gprolog with gcc 6 on i386.

After applying the pr78580 fix to gcc 6, the build fails later with:
...
gplc -c --fast-math fd2c.pl
compilation failed
Makefile:10: recipe for target 'fd2c.o' failed

As a workaround, the build succeeds on i386 (even without the pr78580 fix)
when I configure with --disable-regs.

> James

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#840733: Please remove...

[Andy Simpkins]

Hi Ted,

I am currently sat at the Cambridge BSP looking at Debian RC bugs [1].

Looking at this bug report we believe that on balance the best course of
action would be to remove lib/et/test_cases/imap_err.et from e2fsprogs.
As you have offered to do this in your capacity as "upstream" [2]
may we please ask you to do this at your earliest opportunity.
Would you mind performing this as an atomic operation as this would make
the process of freeze exception straight forwards.

Many thanks in advance,
/Andy

[1]  https://wiki.debian.org/BSP/2017/01/gb/Cambridge#Attendees
[2]  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840733#10



signature.asc
Description: OpenPGP digital signature

Bug#802954: gnu-smalltalk-el: Prevents upgrade of emacs24

[Hilko Bengen]

* Adrian Bunk:

> Are you able to reproduce this?

No.

> My first guess whould be that something went wrong with the removal,
> and that the actual problem might be there?

I don't recall specifics, but yes, something about removing source
symlinks and compiled Lisp files had not been completed. This should
howver not have prevented the install phase.

Cheers,
-Hilko

Bug#852495: [debian-mysql] Bug#852495: Bug#852495: Bug#852495: mariadb-server-10.[01]: purging old mariadb-server shuts down mariadb-server and removes init.d links

[Julian Gilbey]

On Fri, Jan 27, 2017 at 11:52:34AM +0200, Otto Kekäläinen wrote:
> Thanks Julian, you've done a very thorough job in producing and
> documenting the patch.

And here is the patch for mysql-5.6, against the current git version
on alioth (so diff against commit e6f3b698).

Incidentally, the build give a lintian error (as well as numerous
lintian warnings, which are easily fixed):
E: mysql-server-5.6: depends-on-essential-package-without-using-version 
depends: bsdutils

This can presumably be fixed by simply dropping the dependency on
bsdutils; likewise the dependency on initscripts seems redundant.

Best wishes,

   Julian
diff --git a/debian/mysql-server-5.6.lintian-overrides b/debian/mysql-server-5.6.lintian-overrides
index e8c27b76..6f34209a 100644
--- a/debian/mysql-server-5.6.lintian-overrides
+++ b/debian/mysql-server-5.6.lintian-overrides
@@ -1,3 +1,5 @@
 # These long lines reproduce actual output and to reformat them
 # would damage the integrity of the man page.
 mysql-server-5.6: manpage-has-errors-from-man usr/share/man/man1/mysqlbinlog.1.gz 1880: warning [p 12, 5.7i, div `3tbd3,2', 0.8i]: can't break line
+# the second update-rc.d is informational only: see postrm for details
+mysql-server-5.6: duplicate-updaterc.d-calls-in-postrm mysql
diff --git a/debian/mysql-server-5.6.postinst b/debian/mysql-server-5.6.postinst
old mode 100644
new mode 100755
index 0b552740..f8d77433
--- a/debian/mysql-server-5.6.postinst
+++ b/debian/mysql-server-5.6.postinst
@@ -12,14 +12,6 @@ export PATH=$PATH:/sbin:/usr/sbin:/bin:/usr/bin
 # This command can be used as pipe to syslog. With "-s" it also logs to stderr.
 ERR_LOGGER="logger -p daemon.err -t mysqld_safe -i"
 
-invoke() {
-  if [ -x /usr/sbin/invoke-rc.d ]; then
-invoke-rc.d mysql $1
-  else
-/etc/init.d/mysql $1
-  fi
-}
-
 MYSQL_BOOTSTRAP="/usr/sbin/mysqld --bootstrap --user=mysql --skip-grant-tables"
 
 test_mysql_access() {
@@ -60,7 +52,9 @@ EOF
 # and because changed configuration options should take effect immediately.
 # In case the server wasn't running at all it should be ok if the stop
 # script fails. I can't tell at this point because of the cleaned /var/run.
-set +e; invoke stop; set -e
+set +e
+invoke-rc.d mysql stop
+set -e
 
 case "$1" in
   configure)
@@ -231,6 +225,24 @@ if [ "$1" = "configure" ]; then
db_go
fi
 
+   # Fix broken postrms in mysql-server-5.[1-5] and mariadb-server-10.[01]
+   # packages to prevent purging these packages from breaking our package.
+   # (See #852495)  It is unlikely that a user would have mariadb-server
+   # postrm files lying around, but we aim to be safe.  We do not touch
+   # mysql-server-5.7 postrm files, though, as we assume the sysadmin
+   # has not done a downgrade from mysql-server-5.7; if they have, they
+   # will probably have to have done a purge anyway.
+   
+   # We comment out all of the commands which assume that there is no other
+   # mysql server installed.
+   # (Because of the Conflicts in the control file for this package, they can
+   # only possibly be in a configuration-only state at this point.  And this
+   # cannot harm even if the system is in a very broken state and we are being
+   # configured in spite of those packages being in a different state.)
+   olds=$(ls /var/lib/dpkg/info/mysql-server-5.[1-5].postrm /var/lib/dpkg/info/mariadb-server-10.[01].postrm 2>/dev/null || true)
+   if [ -n "$olds" ]; then
+   perl -i -pe 's/stop_server(?=\s|$)/# stop_server/; s/^(\s*)((?:update|invoke)-rc\.d.*$)/$1# $2\n$1true/; s/^(\s*)(deb-systemd-helper.*$)/$1# $2\n$1true/; s%rm -f "/etc/apparmor.d%# rm -f "/etc/apparmor.d%' $olds
+   fi
 fi
 
 db_stop # in case invoke failes
diff --git a/debian/mysql-server-5.6.postrm b/debian/mysql-server-5.6.postrm
old mode 100644
new mode 100755
index e3d5c887..41b402ff
--- a/debian/mysql-server-5.6.postrm
+++ b/debian/mysql-server-5.6.postrm
@@ -11,34 +11,11 @@ if [ -n "$DEBIAN_SCRIPT_DEBUG" ]; then set -v -x; DEBIAN_SCRIPT_TRACE=1; fi
 ${DEBIAN_SCRIPT_TRACE:+ echo "#42#DEBUG# RUNNING $0 $*" 1>&2 }
 
 mysql_cfgdir=/etc/mysql
-MYADMIN="/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf"
-
-# Try to stop the server in a sane way. If it does not success let the admin
-# do it himself. No database directories should be removed while the server
-# is running!
-stop_server() {
-  set +e
-  if [ -x /usr/sbin/invoke-rc.d ]; then
-invoke-rc.d mysql stop
-  else
-/etc/init.d/mysql stop
-  fi
-  errno=$?
-  set -e
-
-  if [ "$?" != 0 ]; then
-echo "Trying to stop the MySQL server resulted in exitcode $?." 1>&2
-echo "Stop it yourself and try again!" 1>&2
-exit 1
-  fi
-}
 
 case "$1" in
   purge|remove|upgrade|failed-upgrade|abort-install|abort-upgrade|disappear)
-if [ -n "`$MYADMIN ping 2>/dev/null`" ]; then
-  stop_server
-  sleep 2
-fi
+# We handle purge actions below.  The server has already been stopp

Bug#850679: etckeeper cron job fails (if no domain name is set)

[Ralf Jung]

Hi,

> On 2017-01-16 16:27:22, Ralf Jung wrote:
>> "dnsdomainname" outputs just nothing here.  So something later in the
>> pipeline seems to convert the empty string to "(none)"... or so.
> 
> I haven't seen anything do that in the source - can you run etckeeper
> under bash -x?

I am not exactly sure what you mean.  I am so far unable to even trigger
the issue interactively, the error only occurs when etckeeper is ran by
cron.  I guess I should edit some file to add "bash -x"?

Kind regards,
Ralf

Bug#852318: lightning: Fake mtime in packaged files

[Peter Lebbing]

On 28/01/17 20:42, Carsten Schoenert wrote:
> then I don't understand your first email.

Do I need to clarify more or did my follow-up mail already do that?

> So I have currently no clue where the timestamps with *.0 are
> coming from.

Maybe I'm nitpicking, maybe I'm pointing out something relevant. I think
all files in a .deb binary package have a 0 fractional seconds part. I
think they are stored with one second resolution. But the problematic
files have a fake mtime of 2010-01-01 0:00 UTC that is the same over
different .deb binary packages.

> But this looks like something that could be come from the
> tools the reproducibly team is using and creating.

That does sound like a clue!

> Next we need to clarify with which package version such timestamps are
> shipped for the first time.

Done!

Using my backups, I could trivially deduce which stable package
introduced the change. In 38.8.0-1~deb8u1, the times are still recent.
In 1:45.1.0-1~deb8u1, the 2010-01-01 times show up.

Next using snapshot.debian.org[1], using a manual binary search through
the .deb files, I could pinpoint that

41.0~b2-1

is the first version where the 2010-01-01 times show up. The one before
that, 40.0~b1-1, still has recent mtimes.

HTH,

Peter.

[1] http://snapshot.debian.org/package/icedove/

-- 
I use the GNU Privacy Guard (GnuPG) in combination with Enigmail.
You can send me encrypted mail if you want some privacy.
My key is available at 

Bug#853052: widelands: Wrong names for some buildings (e.g. Ranger's Hut)

[Elena ``of Valhalla'']

Package: widelands
Version: 1:19+repack-2
Severity: important

Dear Maintainer,

After the save format change, I've restarted playing the widelands
campaigns from the beginning and got stuck on the start of the first one
at not being able to build a Ranger's Hut, the only ones available being
Quarry, Woodcutter's Hut and Fishermanr's Hut (sic).

Trying to start from the tutorial (where all of the barbarian building
are available, and the actual Fisherman's Hut is there), I've then
realized that the Fishermanr's Hut icon was actually the one of the
Ranger's Hut, and that only the name was wrong.

Looking around further, I also found that the basic Coal Mine is called
Deep Coal Mine (but works as the right one, and can then be updated to
Deep Coal Mine as it should).

I'm giving this an important severity because a new player wouldn't know
the icon for a Ranger's Hut in advance, and thus would easily get stuck
and be unable to learn the basics of the game.

I will now play a bit further, *purely* for QA reasons, and I will add
to this bug if I notice other wrong names.

(just before sending this bug I realised that maybe this was because of
the en_GB locale, and indeed setting it to en_US I had the correct
names).

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

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

Versions of packages widelands depends on:
ii  fonts-dejavu-core 2.37-1
ii  fonts-dejavu-extra2.37-1
ii  fonts-freefont-ttf20120503-6
ii  fonts-hosny-amiri 0.107-1
ii  fonts-lklug-sinhala   0.6-3
ii  fonts-nakula  1.0-3
ii  fonts-wqy-microhei0.2.0-beta-2
ii  libboost-regex1.62.0  1.62.0+dfsg-4
ii  libboost-test1.62.0   1.62.0+dfsg-4
ii  libc6 2.24-8
ii  libgcc1   1:6.2.1-5
ii  libgl1-mesa-glx [libgl1]  13.0.3-1
ii  libglew2.02.0.0-3
ii  libicu57  57.1-5
ii  libminizip1   1.1-8
ii  libpng16-16   1.6.28-1
ii  libsdl2-2.0-0 2.0.5+dfsg1-2
ii  libsdl2-image-2.0-0   2.0.1+dfsg-2+b2
ii  libsdl2-mixer-2.0-0   2.0.1+dfsg1-1
ii  libsdl2-net-2.0-0 2.0.1+dfsg1-2
ii  libsdl2-ttf-2.0-0 2.0.14+dfsg1-1
ii  libstdc++66.2.1-5
ii  widelands-data1:19+repack-2
ii  zlib1g1:1.2.8.dfsg-4

widelands recommends no packages.

widelands suggests no packages.

-- no debconf information

Bug#853053: ITP: emacs-bind-map -- bind personal keymaps in multiple locations

[Lev Lamberov]

Package: wnpp
Severity: wishlist
Owner: Lev Lamberov 

* Package name: emacs-bind-map
  Version : 1.1.1
  Upstream Author : Justin Burkett 
* URL : https://github.com/justbur/emacs-bind-map
* License : GPL-3+
  Programming Lang: Emacs Lisp
  Description : bind personal keymaps in multiple locations

`bind-map' is an Emacs package providing the macro bind-map which can
be used to make a keymap available across different "leader keys"
including ones tied to evil states. It is essentially a
generalization of the idea of a leader key as used in vim or the
Emacs `evil-leader' package, and allows for an arbitrary number of
"leader keys". This is probably best explained with an example.

Bug#852817: [git-buildpackage/master] pq: Filter out comments from series diff

[Guido Günther]

tag 852817 pending
thanks

Date:   Sun Jan 29 13:42:38 2017 +0100
Author: Guido Günther 
Commit ID: 22013adfd525378a278676b5f0b4d66834f17afa
Commit URL: 
https://git.sigxcpu.org/cgit/git-buildpackage//commit/?id=22013adfd525378a278676b5f0b4d66834f17afa
Patch URL: 
https://git.sigxcpu.org/cgit/git-buildpackage//patch/?id=22013adfd525378a278676b5f0b4d66834f17afa

pq: Filter out comments from series diff

When creating the delta of added and dropped pachtches ignore comment
lines in the series file.

Closes: #852817

  

Bug#853054: unblock: debian-edu-install/1.913

[Holger Levsen]

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

Please unblock package debian-edu-install, it's blocked because it has
an udeb (which is not used by d-i by default).

+debian-edu-install (1.913) unstable; urgency=medium
+
+  [ Wolfgang Schweer ]
+  * Adjust main-server preseeding to match the Icinga2 -> Icinga change.
+
+ -- Holger Levsen   Tue, 17 Jan 2017 22:02:53 +0100
+
+debian-edu-install (1.912) unstable; urgency=medium
+
+  * Translation updates:
+- Basque, thanks to Iñaki Larrañaga (Dooteo). (Closes: #850045)
+- Romanian, thanks to Ionel Mugurel Ciobîcă.
+- Swedisch, thanks to Martin Bagge. (Closes: #851167)
+- French, thanks to Jean-Pierre Giraud. (Closes: #851327)
+
+ -- Holger Levsen   Sun, 15 Jan 2017 10:28:26 +0100

$ git diff 1.911..1.913 | diffstat
 debian/changelog|   17 +++
 debian/po/eu.po |   29 ++---
 debian/po/fr.po |   20 -
 debian/po/ro.po |3 -
 debian/po/sv.po |   78 ++--
 preseed-values/defaults.main-server |7 +--
 6 files changed, 83 insertions(+), 71 deletions(-)

--- a/preseed-values/defaults.main-server
+++ b/preseed-values/defaults.main-server
 
-# Provide a default icingaadmin password
-icinga2-classicui icinga2-classicui/adminpassword password skolelinux
-icinga2-classicui icinga2-classicui/adminpassword-repeat password skolelinux
+# Provide a default icingaadmin password, enable cgi
+icinga-common icinga/check_external_commands boolean true
+icinga-cgi icinga/adminpassword password skolelinux
+icinga-cgi icinga/adminpassword-repeat password skolelinux

Not sure if I should have filed a bug for this. And also KiBi said in
https://lists.debian.org/msgid-search/20170108185821.gb25...@mraw.org:
"Further updates can probably go through without having to block on me,
but I don't mind either way."

However, filing+closing bugs is easy so here we go… :)


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#852975: linux-image-4.9.0-1-amd64: [Regression] Geniatech T220 DVB-T2 TV Stick stopped to work

[Philip Rinn]

Hi,

here some additional info:

The crash with this dvb stick seems to be related:
https://bugzilla.kernel.org/show_bug.cgi?id=191891

And also the problem with some usb sound card seems to be the same:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852749

Seems to affect more devices :(

Best,
Philip



signature.asc
Description: OpenPGP digital signature

Bug#853055: ITP: mmllib -- library for handling Music Macro Language

[Dominik George]

Package: wnpp
Severity: wishlist
Owner: Dominik George 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

* Package name: mmllib
  Version : 0.3.0
  Upstream Author : Dominik George 
* URL : https://github.com/Natureshadow/mmllib
* License : MirOS
  Programming Lang: Python
  Description : library for handling Music Macro Language

 MMLlib is a pure Python implementation of functionality related to the
 Music Macro Language as implemented by Microsoft® GW-BASIC® and
 compatibles, which is its most common form, also implemented by the PC
 speaker driver in Linux and BSD, with a number of extensions and
 changes.

-BEGIN PGP SIGNATURE-

iQJ4BAEBCABiFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAliN5TgxGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYxIcbmlrQG5h
dHVyYWxuZXQuZGUACgkQt5o8FqDE8pa59hAAzfi4K/XkxBiQCBP/4mQd3mUYSNea
Dx+vOyU+DpnvWm/oURgsXlWMz8HkwMYwUq185RPyiUh4vg3pUHzCoSH3/y/pQPoB
hBHZfvntzNnr3X8PZd4LfX8ESGvs7U5A7ruOzD4iv/xK0jxvvH+7zyTWo17AH7cn
Mc21jky4zWWnmQya+/w5ejArvqRvwydRIPSZeb9n3heOgW+TUWPVvsD6pd0qnEes
DYntEbJznC7U6ifY5VUPGZt0NO7pkjoKTxI0uKO/V+lN7Qp3r53huYyc0e02uQ6G
w2EeYxs3M6gceDNmcvAQBfPJ8CpMMdORt04F1hQ0xdg0cQ0MHL6BC1ihRwvCEg0c
ZjgHJM+tI6b74l5dndlLL5alMsUaKUW3gfS/EIPz9pWm2MO7pievfP4JR2yjW4jk
PNAhinole9br9jEqo6IqRa+9IK1BY44eEJgQ09YCEyrgpG57aMsiigcIjxR6H87J
VE/X2qVxKsJQyFL/UjU5Ic9BCGKE1Kn8E1zu+b9KHj99IlqnQw5k+f9OvnPUxllD
0Gx8HPsrUBqFsw+YY5aBHu2lf1E8zI4/kkFVcn8ZZ46/SmJYh0IiIPtssum6WPMN
e3ogcp9rYnIIPlUvRAFJrQY8EYPd7kiKP4Zt/KFM9IQqdjIIObFyMTfUK2cjtiUZ
2Nsvtm14OXov7Hc=
=gEh9
-END PGP SIGNATURE-

Bug#849504: Data corruption with copy-on-write and multiple threads

[Jonathan Wiltshire]

Hi,

On Wed, Dec 28, 2016 at 12:33:51AM +0100, Wouter Verhelst wrote:
> We should not release Debian with this bug present; however, I don't
> want to fix this right now, or 1:3.15.1-1 will miss the freeze cutoff.
> I'll upload a package as soon as that version migrates to testing.

nbd 1:3.15.1-1 and then 1:3.15.1-2 migrated on 2016-12-31, so that should
leave the way clear to fixing this.

Thanks,

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

Bug#852437: qcontrold fails starting

[Ian Campbell]

tag -1 +moreinfo

On Tue, 2017-01-24 at 13:39 +0100, Michaël Marchegay wrote:
> Package: qcontrol
> Version: 0.5.5-2
> 
> After a fresh install of stretch, qcontrold won't start on TS-410.
> 
> I had to apply the following patch in order to make it working :
> 
> root@qnap:/etc/qcontrol# diff -u ts41x.lua.orig ts41x.lua
> --- ts41x.lua.orig 2017-01-24 13:28:27.532867707 +0100
> +++ ts41x.lua 2017-01-24 13:18:19.346032258 +0100
> @@ -117,7 +117,7 @@
>   return evalfn(results[3])
>   end
> 
> - local v=gpio:read("*n")
> + local v=gpio.read("*n")

I'm not sure what is wrong with your system but I am pretty sure the
above is not the fix since it is not a valid operation on a Lua file
descriptor object (i.e. something returned by io.open() which gpio is
here).

For example on my TS-419 after running:
# echo -n 42 > /sys/class/gpio/export

Then from a Lua repl I get:
# lua5.1 
Lua 5.1.5  Copyright (C) 1994-2012 Lua.org, PUC-Rio
> path=string.format("/sys/class/gpio/gpio%d/value", 42)
> =path
/sys/class/gpio/gpio42/value
> gpio=io.open(path)
> =gpio
file (0x80d10bb0)
> v = gpio.read("*n")
stdin:1: bad argument #1 to 'read' (FILE* expected, got string)
stack traceback:
[C]: in function 'read'
stdin:1: in main chunk
[C]: ?
> v = gpio:read("*n")
> =v
1

This is exactly what I would expect since the gpio.read function
expects gpio itself as the first argument -- which is what the
gpio:read syntax does:
gpio:read(args)
is equivalent to:
gpio.read(gpio, args)

I'm not sure how the change you made fixed things, perhaps by throwing
the exception it skipped all the rest.

Please could you provide more info about the failure you are seeing
with your ts41x.lua unmodified, i.e. logs etc.

Ian.

Bug#853056: txfixtures: FTBFS randomly (failing tests)

[Santiago Vila]

Package: src:txfixtures
Version: 0.2.6-1
Severity: important

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 
running config
I: pybuild base:184: python3.5 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:184: /usr/bin/python setup.py build 
running build
running build_py
creating /<>/.pybuild/pythonX.Y_2.7/build/txfixtures

[... snipped ...]

test_reset_hung_thread (txfixtures.tests.test_reactor.ReactorTest)
txfixtures.tests.test_reactor.ReactorTest.test_reset_hung_thread ... ok
test_reset_thread_and_reactor_died (txfixtures.tests.test_reactor.ReactorTest)
txfixtures.tests.test_reactor.ReactorTest.test_reset_thread_and_reactor_died 
... ok
test_reset_thread_died_but_reactor_is_running 
(txfixtures.tests.test_reactor.ReactorTest)
txfixtures.tests.test_reactor.ReactorTest.test_reset_thread_died_but_reactor_is_running
 ... ok
test_fail 
(txfixtures._twisted.tests.test_threading.InterruptableCallFromThreadTest)
txfixtures._twisted.tests.test_threading.InterruptableCallFromThreadTest.test_fail
 ... ok
test_success 
(txfixtures._twisted.tests.test_threading.InterruptableCallFromThreadTest)
txfixtures._twisted.tests.test_threading.InterruptableCallFromThreadTest.test_success
 ... ok
test_timeout 
(txfixtures._twisted.tests.test_threading.InterruptableCallFromThreadTest)
txfixtures._twisted.tests.test_threading.InterruptableCallFromThreadTest.test_timeout
 ... ok

==
ERROR: test_no_min_uptime (tests.test_service.ServiceProtocolIntegrationTest)
tests.test_service.ServiceProtocolIntegrationTest.test_no_min_uptime
--
_StringException: Empty attachments:
  fake-process
  twisted-log

pythonlogging:'': {{{
Service process spawned
Service process exited: A process has ended with a probable error condition: 
process ended with exit code 1.
Give up waiting for the service to be ready: minimum uptime not yet elapsed
}}}

Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/testtools/deferredruntest.py", line 
206, in _log_user_exception
raise e
testtools.deferredruntest.UncleanReactorError: The reactor still thinks it 
needs to do things. Close all connections, kill all processes and make sure all 
delayed calls have either fired or been cancelled:
  
  
  


--
Ran 71 tests in 8.644s

FAILED (errors=1, skipped=2)
E: pybuild pybuild:276: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/pythonX.Y_2.7/build; python2.7 -m unittest discover 
-v 
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
debian/rules:9: recipe for target 'build-indep' failed
make: *** [build-indep] Error 25
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 several build logs here:

https://people.debian.org/~sanvila/build-logs/txfixtures/

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

The bug should be reproducible with sbuild on a single CPU virtual machine,
provided you try enough times (as the failure happens randomly).

Thanks.

Bug#853057: ITP: node-path-key -- Get the PATH environment variable key cross-platform

[Aarti Kashyap]

Package: wnpp
Severity: wishlist
Owner: Aarti Kashyap 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-path-key
  Version : 2.0.1
  Upstream Author : Sindre Sorhus  (sindresorhus.com
)
* URL : https://github.com/sindresorhus/path-key#readme
* License : Expat
  Programming Lang: JavaScript
  Description : Get the PATH environment variable key cross-platform

Bug#852437: qcontrold fails starting

[Ian Campbell]

On Sun, 2017-01-29 at 13:03 +, Ian Campbell wrote:
> 

In response to this I got:

  ch...@free.fr
SMTP error from remote mail server after end of data:
host mx1.free.fr [212.27.48.6]: 550 spam detected

I'm sending you this from a different address, if this doesn't get
through then I will likely close for the time being until your anti-
SPAM measures are fixed, sorry.

Ian.

> tag -1 +moreinfo
> 
> On Tue, 2017-01-24 at 13:39 +0100, Michaël Marchegay wrote:
> > Package: qcontrol
> > Version: 0.5.5-2
> > 
> > After a fresh install of stretch, qcontrold won't start on TS-410.
> > 
> > I had to apply the following patch in order to make it working :
> > 
> > root@qnap:/etc/qcontrol# diff -u ts41x.lua.orig ts41x.lua
> > --- ts41x.lua.orig 2017-01-24 13:28:27.532867707 +0100
> > +++ ts41x.lua 2017-01-24 13:18:19.346032258 +0100
> > @@ -117,7 +117,7 @@
> >   return evalfn(results[3])
> >   end
> > 
> > - local v=gpio:read("*n")
> > + local v=gpio.read("*n")
> 
> I'm not sure what is wrong with your system but I am pretty sure the
> above is not the fix since it is not a valid operation on a Lua file
> descriptor object (i.e. something returned by io.open() which gpio is
> here).
> 
> For example on my TS-419 after running:
> # echo -n 42 > /sys/class/gpio/export
> 
> Then from a Lua repl I get:
> # lua5.1 
> Lua 5.1.5  Copyright (C) 1994-2012 Lua.org, PUC-Rio
> > path=string.format("/sys/class/gpio/gpio%d/value", 42)
> > =path
> /sys/class/gpio/gpio42/value
> > gpio=io.open(path)
> > =gpio
> file (0x80d10bb0)
> > v = gpio.read("*n")
> stdin:1: bad argument #1 to 'read' (FILE* expected, got string)
> stack traceback:
>   [C]: in function 'read'
>   stdin:1: in main chunk
>   [C]: ?
> > v = gpio:read("*n")
> > =v
> 1
> 
> This is exactly what I would expect since the gpio.read function
> expects gpio itself as the first argument -- which is what the
> gpio:read syntax does:
> gpio:read(args)
> is equivalent to:
> gpio.read(gpio, args)
> 
> I'm not sure how the change you made fixed things, perhaps by
> throwing
> the exception it skipped all the rest.
> 
> Please could you provide more info about the failure you are seeing
> with your ts41x.lua unmodified, i.e. logs etc.
> 
> Ian.

Bug#853058: ITP: node-async-each -- No-bullshit, ultra-simple, 35-lines-of-code async parallel forEach / map function for JavaScript.

[nikhil gawande]

Package: wnpp
Severity: wishlist
Owner: Nikhil Gawande 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-async-each
  Version : 1.0.1
  Upstream Author : Paul Miller (http://paulmillr.com/)
* URL : https://github.com/paulmillr/async-each/
* License : Expat
  Programming Lang: JavaScript
  Description : No-bullshit, ultra-simple, 35-lines-of-code async
parallel forEach / map function for JavaScript.

 .
 Node.js is an event-based server-side JavaScript engine.

Bug#850660: nodejs-dev: npm conflicts transitively with libssl-dev since nodejs-dev 4.7.2~dfsg-1

[anomie]

I've been unable to upgrade nodejs and nodejs-dev thanks to this issue:
I need npm for some things, but also php7.0-dev (which depends on
libssl-dev) for something else.

Bug#853057: ITP: node-path-key -- Get the PATH environment variable key cross-platform

[Pirate Praveen]

On ഞായര്‍ 29 ജനുവരി 2017 06:37 വൈകു, Aarti Kashyap wrote:
>   Description : Get the PATH environment variable key cross-platform

You can just patch term-size to directly read the PATH variable instead
of using path-key




signature.asc
Description: OpenPGP digital signature

Bug#852975: linux-image-4.9.0-1-amd64: [Regression] Geniatech T220 DVB-T2 TV Stick stopped to work

[Ben Hutchings]

On Sun, 2017-01-29 at 13:49 +0100, Philip Rinn wrote:
> Hi,
> 
> here some additional info:
> 
> The crash with this dvb stick seems to be related:
> https://bugzilla.kernel.org/show_bug.cgi?id=191891
> 
> And also the problem with some usb sound card seems to be the same:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852749
> 
> Seems to affect more devices :(

These are latent bugs in various USB drivers that were exposed by a
change to memory mapping on amd64 in Linux 4.9.

I expect them to be fixed upstream fairly soon.

Ben.

-- 
Ben Hutchings
All the simple programs have been written, and all the good names
taken.



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

Bug#853059: Confusing theme choosing interface when no previews are available

[Margarita Manterola]

Package: cinnamon-common
Version: 3.2.7-1
Severity: important

The new theme choosing interface in cinnamon has buttons that are 
supposed to show a preview of what the theme will look like so that the 
user has a bit more to go on when choosing than just the name of the 
theme.  This is nice but it has the problem that if there is no preview 
available, it shows just a gray rectangle that gives the impression that 
something is broken (i.e. it's not clear at all that this means "no 
preview available").


This happens on both the window manager ("metacity-1" theme directory) 
and the controls ("gtk-3.0" theme directory) options.  The other options 
get previews rendered automatically from the themes, so they are ok.


The solution to this is to include the thumbnails for the themes.  
Cinnamon already includes some thumbnails, e.g.:


/usr/share/cinnamon/thumbnails/metacity-1/Adwaita.png
/usr/share/cinnamon/thumbnails/metacity-1/AgingGorilla.png
/usr/share/cinnamon/thumbnails/metacity-1/Atlanta.png
/usr/share/cinnamon/thumbnails/metacity-1/Box.png
/usr/share/cinnamon/thumbnails/metacity-1/Bright.png
/usr/share/cinnamon/thumbnails/metacity-1/Crux.png
/usr/share/cinnamon/thumbnails/metacity-1/Esco.png
/usr/share/cinnamon/thumbnails/metacity-1/HighContrast.png
/usr/share/cinnamon/thumbnails/metacity-1/Metabox.png
/usr/share/cinnamon/thumbnails/metacity-1/README
/usr/share/cinnamon/thumbnails/metacity-1/Simple.png
/usr/share/cinnamon/thumbnails/metacity-1/unknown.png

Unfortunately, most of the themes shipped by Debian are not listed 
there. All themes shipped in Debian should have a thumbnail included.


--
Regards,
Marga

Bug#694320: [Pkg-fonts-devel] Bug#665334: non-DFSG & Type 1 Postscript embedded fonts

[Paul Wise]

On Sun, Jan 29, 2017 at 7:35 PM, Andy Simpkins wrote:

>   It is our belief that this is sufficient; that the package FontForge,
> and type 1 fonts generated by this package are now DFSG compliant
> because Apache 2.0 is GPL2+ compatible.

The FSF believes that Apache 2.0 is only compatible with GPLv3+ not GPLv2.

https://www.gnu.org/licenses/license-list.html#apache2
https://www.apache.org/licenses/GPL-compatibility.html

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#852484: screen: Privilege escalation in Screen 4.5.0

[Salvatore Bonaccorso]

Control: retitle -1 screen: CVE-2017-5618: Privilege escalation in Screen 4.5.0

A CVE has been assigned for this issue on oss-security
(CVE-2017-5618):

http://www.openwall.com/lists/oss-security/2017/01/29/3

Regards,
Salvatore

Bug#853060: unblock: gdm3/3.22.1-2

[Simon McVittie]

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

Please unblock package gdm3 and/or set a shorter time delay.
This fixes RC bug #789118, one of two root causes for inability to
unlock the lock screen if a user fails to read the release notes and
carries out the upgrade from within the GNOME GUI (the other is in
gnome-shell and will be requested separately).

unblock gdm3/3.22.1-2

>+  [ Simon McVittie ]
>+  * Work around upgrades not being done offline:
>+- Add a non-upstreamable patch to edit D-Bus messages from libgdm
>+  to the session worker and adapt them from the pre-3.16 interface
>+  to the post-3.16 interface. Only do this if a flag file in /run
>+  has been created, so that this workaround will only be active
>+  until the next reboot.
>+- gdm3.preinst: Create that flag file on upgrades. (Closes: #789118)

The RC bug fix.

>+  [ Jeremy Bicha ]
>+  * debian/greeter.dconf-defaults:
>+- Use the new emblem-debian-white.png for default login screen logo
>+  (Closes: #833529)

Was already in pkg-gnome svn, targeting stretch. If desktop-base 9.0.3
is allowed to migrate, this puts Debian branding on the login screen
(which was previously only present if deprecated theme packages were
installed). If not, the missing file is harmlessly ignored. I've
tested both ways.

>+  [ Michael Biebl ]
>+  * Stop setting authdir, has been dropped upstream in favour of xauthdir.

Was already in pkg-gnome svn. Non-critical, but I have verified that it is
harmless (there is no mention of authdir in the source tree, except as a
substring of xauthdir, which is set by --with-xauth-dir=/var/run/gdm3 on the
configure command-line).

Regards,
S
diffstat for gdm3-3.22.1 gdm3-3.22.1

 changelog  |   23 +
 gdm3.preinst   |5 
 greeter.dconf-defaults |4 
 patches/Hack-D-Bus-messages-from-Debian-8-libgdm-to-work-wit.patch |  118 ++
 patches/series |1 
 rules  |2 
 6 files changed, 150 insertions(+), 3 deletions(-)

diff -Nru gdm3-3.22.1/debian/changelog gdm3-3.22.1/debian/changelog
--- gdm3-3.22.1/debian/changelog	2016-10-16 23:17:17.0 +0100
+++ gdm3-3.22.1/debian/changelog	2017-01-29 11:07:50.0 +
@@ -1,3 +1,26 @@
+gdm3 (3.22.1-2) unstable; urgency=medium
+
+  * Team upload.
+
+  [ Michael Biebl ]
+  * Stop setting authdir, has been dropped upstream in favour of xauthdir.
+
+  [ Jeremy Bicha ]
+  * debian/greeter.dconf-defaults:
+- Use the new emblem-debian-white.png for default login screen logo
+  (Closes: #833529)
+
+  [ Simon McVittie ]
+  * Work around upgrades not being done offline:
+- Add a non-upstreamable patch to edit D-Bus messages from libgdm
+  to the session worker and adapt them from the pre-3.16 interface
+  to the post-3.16 interface. Only do this if a flag file in /run
+  has been created, so that this workaround will only be active
+  until the next reboot.
+- gdm3.preinst: Create that flag file on upgrades. (Closes: #789118)
+
+ -- Simon McVittie   Sun, 29 Jan 2017 11:07:50 +
+
 gdm3 (3.22.1-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru gdm3-3.22.1/debian/gdm3.preinst gdm3-3.22.1/debian/gdm3.preinst
--- gdm3-3.22.1/debian/gdm3.preinst	2016-10-16 21:58:13.0 +0100
+++ gdm3-3.22.1/debian/gdm3.preinst	2017-01-29 01:59:22.0 +
@@ -9,4 +9,9 @@
 fi
 fi
 
+if [ -n "$2" ] && dpkg --compare-versions "$2" lt 3.22; then
+echo "Enabling compatibility workaround for upgrades from Debian 8..."
+touch "/run/gdm3-upgraded-from-debian-8"
+fi
+
 #DEBHELPER#
diff -Nru gdm3-3.22.1/debian/greeter.dconf-defaults gdm3-3.22.1/debian/greeter.dconf-defaults
--- gdm3-3.22.1/debian/greeter.dconf-defaults	2015-07-09 12:03:14.0 +0100
+++ gdm3-3.22.1/debian/greeter.dconf-defaults	2017-01-26 22:27:50.0 +
@@ -23,8 +23,8 @@
 # Login manager options
 # =
 [org/gnome/login-screen]
-logo='/usr/share/icons/gnome/48x48/places/debian-swirl.png'
-fallback-logo='/usr/share/icons/gnome/48x48/places/debian-swirl.png'
+logo='/usr/share/icons/hicolor/48x48/emblems/emblem-debian-white.png'
+fallback-logo='/usr/share/icons/hicolor/48x48/emblems/emblem-debian-white.png'
 
 # - Disable user list
 # disable-user-list=true
diff -Nru gdm3-3.22.1/debian/patches/Hack-D-Bus-messages-from-Debian-8-libgdm-to-work-wit.patch gdm3-3.22.1/debian/patches/Hack-D-Bus-messages-from-Debian-8-libgdm-to-work-wit.patch
--- gdm3-3.22.1/debian/patches/Hack-D-Bus-messages-from-Debian-8-libgdm-to-work-wit.patch	1970-01-01 01:00:00.0 +0100
+++ gdm3-3.22.1/debian/patches/Hack-D-Bus-messages-from-Debian-8-libgdm-to-work-wit.patch	2017-01-29 01:59:22.0 

Bug#853063: unblock: gnome-shell/3.22.2-4

[Simon McVittie]

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

Please unblock package gnome-shell and/or set a shorter time delay.
This fixes RC bug #853018, one of two root causes for inability to
unlock the lock screen if a user fails to read the release notes and
carries out the upgrade from within the GNOME GUI (the other is in
gdm3 and has a separate unblock request).

unblock gnome-shell/3.22.2-4

>+- Ship a copy of the process-working spinner animation from Shell
>+  3.14.x, and install it where Shell 3.14.x would expect to find it.
>+  This avoids a code path where the lock screen would fail to unlock
>+  because the animation code didn't cope with inability to load the
>+  animation. (Closes: #853018)

The RC bug fix. We were lucky here: gnome-shell 3.22 has an incompatible
(different size) animation of the same name, but it compiles it into a
GResource file for faster access instead of shipping a "loose" file on
disk, so it doesn't actually try to read this one.

>+- d/p/animations-Guard-against-empty-animations.patch,
>+  d/p/texture-cache-Warn-when-loading-sliced-image-fails.patch:
>+  Add two patches from upstream 3.22 branch to harden the same part
>+  of the lock screen code against hitting a similar issue, and
>+  issue warnings to the system log if it happens.

Make sure a similar thing won't happen when upgrading from stretch to
buster.

Regards,
S
at the southernmost point of the Cambridge BSP
diffstat for gnome-shell-3.22.2 gnome-shell-3.22.2

 changelog|   17 
 gnome-shell-common.install   |3 
 jessie-upgrade/process-working.svg   |  261 ++
 patches/animations-Guard-against-empty-animations.patch  |   33 +
 patches/series   |2 
 patches/texture-cache-Warn-when-loading-sliced-image-fails.patch |   61 ++
 6 files changed, 377 insertions(+)

diff -Nru gnome-shell-3.22.2/debian/changelog gnome-shell-3.22.2/debian/changelog
--- gnome-shell-3.22.2/debian/changelog	2017-01-20 09:48:04.0 +
+++ gnome-shell-3.22.2/debian/changelog	2017-01-29 11:45:16.0 +
@@ -1,3 +1,20 @@
+gnome-shell (3.22.2-4) unstable; urgency=medium
+
+  * Team upload.
+  * Work around upgrades not being done offline:
+- Ship a copy of the process-working spinner animation from Shell
+  3.14.x, and install it where Shell 3.14.x would expect to find it.
+  This avoids a code path where the lock screen would fail to unlock
+  because the animation code didn't cope with inability to load the
+  animation. (Closes: #853018)
+- d/p/animations-Guard-against-empty-animations.patch,
+  d/p/texture-cache-Warn-when-loading-sliced-image-fails.patch:
+  Add two patches from upstream 3.22 branch to harden the same part
+  of the lock screen code against hitting a similar issue, and
+  issue warnings to the system log if it happens.
+
+ -- Simon McVittie   Sun, 29 Jan 2017 11:45:16 +
+
 gnome-shell (3.22.2-3) unstable; urgency=medium
 
   * Team upload.
diff -Nru gnome-shell-3.22.2/debian/gnome-shell-common.install gnome-shell-3.22.2/debian/gnome-shell-common.install
--- gnome-shell-3.22.2/debian/gnome-shell-common.install	2013-06-29 15:23:02.0 +0100
+++ gnome-shell-3.22.2/debian/gnome-shell-common.install	2017-01-29 02:00:14.0 +
@@ -5,3 +5,6 @@
 usr/share/gnome-shell
 usr/share/gtk-doc
 usr/share/locale
+
+# This is a hack for #853018. Remove this after Debian stretch is released.
+debian/jessie-upgrade/process-working.svg /usr/share/gnome-shell/theme
diff -Nru gnome-shell-3.22.2/debian/jessie-upgrade/process-working.svg gnome-shell-3.22.2/debian/jessie-upgrade/process-working.svg
--- gnome-shell-3.22.2/debian/jessie-upgrade/process-working.svg	1970-01-01 01:00:00.0 +0100
+++ gnome-shell-3.22.2/debian/jessie-upgrade/process-working.svg	2017-01-29 02:00:14.0 +
@@ -0,0 +1,261 @@
+
+
+
+http://purl.org/dc/elements/1.1/";
+   xmlns:cc="http://creativecommons.org/ns#";
+   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#";
+   xmlns:svg="http://www.w3.org/2000/svg";
+   xmlns="http://www.w3.org/2000/svg";
+   xmlns:xlink="http://www.w3.org/1999/xlink";
+   xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd";
+   xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape";
+   id="svg5369"
+   version="1.1"
+   inkscape:version="0.48+devel r10053 custom"
+   width="96"
+   height="48"
+   sodipodi:docname="process-working.svg"
+   style="display:inline">
+  
+
+  
+image/svg+xml
+http://purl.org/dc/dcmitype/StillImage"; />
+
+  
+
+  
+  
+  
+
+  
+  
+
+
+
+
+
+
+
+
+  
+  
+
+  
+  
+  
+  
+  
+  
+  
+  
+
+
+   

Bug#853062: ITP: node-is-obj -- Check if a value is an object

[Akash Sarda]

Package: wnpp
Severity: wishlist
Owner: akash 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-is-obj
  Version : 1.0.1
  Upstream Author : Sindre Sorhus  (sindresorhus.com)
* URL : https://github.com/sindresorhus/is-obj#readme
* License : Expat
  Programming Lang: JavaScript
  Description : Check if a value is an object
 .
 Node.js is an event-based server-side JavaScript engine.

Bug#853064: Upgrading to cinnamon-screensaver 3.2 causes the running screensaver to misbehave until restarted

[Margarita Manterola]

Package: cinnamon-screensaver
Version: 3.2.6-1
Severity: important

With the upgrade to cinnamon-screensaver 3.2 a severe bad experience is 
triggered when the user upgrades a machine that is already running 
cinnamon-screensaver from any previous cinnamon version.


If the screensaver locks and the user wants to enter their password, the 
running screensaver from a previous version tries to execute 
cinnamon-screensaver-dialog.  However, this command doesn't exist 
anymore which causes the screensaver dialog to not turn up and thus the 
user is not able to unlock their computer until they kill the 
screensaver or reboot the machine.


This is a one time only hassle, but it's a pretty pretty bad user 
experience. I don't think we should release stretch with such an issue 
in it.


The solution is to have the new screensaver ship a compatibility 
cinnamon-screensaver-dialog that allows for the old screensaver to be 
killed and a new one to be started.


--
Regards,
Marga

Bug#853065: ITP: node-md5-hex -- Create a MD5 hash with hex encoding

[Akash Sarda]

Package: wnpp
Severity: wishlist
Owner: akash 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-md5-hex
  Version : 2.0.0
  Upstream Author : Sindre Sorhus  (sindresorhus.com)
* URL : https://github.com/sindresorhus/md5-hex#readme
* License : Expat
  Programming Lang: JavaScript
  Description : Create a MD5 hash with hex encoding

Bug#853066: gnupg-agent: opens dialog on the wrong computer.

[Charles Plessy]

Package: gnupg-agent
Version: 2.1.18-3
Severity: normal

Hello,

when I am logged on my desktop computer directly with a GNOME shell
session, and remotly via SSH, attempts to use gpg from the SSH session
will open a popup on my desktop computer's screen to enter the
passphrase, which obviously prevents me from entering the passphrase
when I am far from the desktopp computer (which is why I connect to it
via SSH).  This happens when I have used gpg in the GNOME shell session
directly, and enough time lapsed so that the agent wants the passphrase
again.  Otherwise, gpg in the SSH session just runs without asking the
passphrase.

I am not completely sure if it is the same as with #559101, therefore
I open a new bug.

Have a nice day,

-- Charles

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (800, 'testing'), (700, 'unstable'), (500, 'stable-updates'), 
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages gnupg-agent depends on:
ii  libassuan0  2.4.3-2
ii  libc6   2.24-8
ii  libgcrypt20 1.7.5-3
ii  libgpg-error0   1.26-1
ii  libnpth01.3-1
ii  libreadline77.0-1
ii  pinentry-gnome3 [pinentry]  1.0.0-1
ii  pinentry-gtk2 [pinentry]1.0.0-1

Versions of packages gnupg-agent recommends:
ii  gnupg  2.1.18-3

Versions of packages gnupg-agent suggests:
ii  dbus-user-session  1.10.14-1
ii  libpam-systemd 232-14
ii  pinentry-gnome31.0.0-1
pn  scdaemon   

-- no debconf information

Bug#850660: nodejs-dev: npm conflicts transitively with libssl-dev since nodejs-dev 4.7.2~dfsg-1

[Jonas Smedegaard]

Quoting ano...@users.sourceforge.net (2017-01-29 14:12:59)
> I've been unable to upgrade nodejs and nodejs-dev thanks to this issue:
> I need npm for some things, but also php7.0-dev (which depends on
> libssl-dev) for something else.

Please share what it is that - transitively or not but _concurrently_ -
needs both libssl-dev.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#853062: ITP: node-is-obj -- Check if a value is an object

[Jonas Smedegaard]

Hi Akash,

Quoting Akash Sarda (2017-01-29 14:24:30)

>   Description : Check if a value is an object
>  .
>  Node.js is an event-based server-side JavaScript engine.

Thanks for your interest in packaging this Nodejs module.

Please mention in short description that this is a nodejs module.

Please mention in long description what this is at all.

Beware that long description is *not* a continuation of short 
description - please read Debian Policy § 3.4 and § 5.6.13.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#852574: snapper: Update udevadm path

[Michael Biebl]

Am 29.01.2017 um 08:43 schrieb Hideki Yamane:
> Hi,
> 
> On Wed, 25 Jan 2017 14:42:36 +0100

>> According to codesearch [1] your package snapper does hard-code the
>> udevadm path as /sbin/udevadm.
>>
>> Please change that to /bin/udevadm.
> 
>  Useful codesearch! :)
>  
>  Just a question for this change, openSUSE and Fedora uses
>  /usr/sbin/udevadm. Does Debian move udevadm as same as those
>  distros in Buster? (/usr Merge?)

The /usr merge change wouldn't affect /bin and /sbin, at least the
current plans are not to merge /bin and /sbin.


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



signature.asc
Description: OpenPGP digital signature

Bug#853058: ITP: node-async-each -- No-bullshit, ultra-simple, 35-lines-of-code async parallel forEach / map function for JavaScript.

[Jonas Smedegaard]

Hi Nikhil,

Quoting nikhil gawande (2017-01-29 14:12:45)
>   Description : No-bullshit, ultra-simple, 35-lines-of-code async
> parallel forEach / map function for JavaScript.

Thanks for your work packaging Nodejs libraries for Debian.

Please elaborate in long description on unclear (to me, at least) parts 
of short description - the keywords "no-bullshit" and "ultra-simple" and 
"35-lines-of-code".

Either that, or - if not really _descriptive_ features of this library 
but just fun buzz - then please omit them from short description.


Regards,

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#852815: [Pkg-utopia-maintainers] Bug#852815: /usr/bin/nm-online: "nm-online -x -q" always exits 1 (offline)

[Michael Biebl]

Am 28.01.2017 um 17:20 schrieb James McCoy:
> Control: tags -1 fixed-upstream
> 
> On Fri, Jan 27, 2017 at 04:21:35PM -0500, James McCoy wrote:
>> On Fri, Jan 27, 2017 at 01:20:06PM -0500, James McCoy wrote:
>>> Attached patch explicitly returns from quit_if_connected after setting
>>> retval.  This fixes the behavior for me.
>>
>> I've forwarded the patch upstream, too.  Just waiting for my message to
>> be moderated.
> 
> It's now fixed --
> https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=6419d2462049a9e263b59462a6ade646a9b49ee2

Thanks a lot James.
I plan to cherry-pick that change once 1.6.0-1 has migrated to testing.


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



signature.asc
Description: OpenPGP digital signature

Bug#853060: unblock: gdm3/3.22.1-2

[Aurélien COUDERC]

Le 29 janvier 2017 14:20:25 GMT+01:00, Simon McVittie  a écrit 
:

>>+  [ Jeremy Bicha ]
>>+  * debian/greeter.dconf-defaults:
>>+- Use the new emblem-debian-white.png for default login screen
>logo
>>+  (Closes: #833529)
>
>Was already in pkg-gnome svn, targeting stretch. If desktop-base 9.0.3
>is allowed to migrate, this puts Debian branding on the login screen
>(which was previously only present if deprecated theme packages were
>installed). If not, the missing file is harmlessly ignored. I've
>tested both ways.

This would be desktop-base 9.0.2 that was uploaded to sid a few days ago and is 
expected to migrate to testing before the freeze if no RC bug is raised.


Cheers,
--Aurélien

Bug#850660: [Pkg-javascript-devel] Bug#850660: nodejs-dev: npm conflicts transitively with libssl-dev since nodejs-dev 4.7.2~dfsg-1

[Sebastiaan Couwenberg]

On 01/29/2017 02:31 PM, Jonas Smedegaard wrote:
> Quoting ano...@users.sourceforge.net (2017-01-29 14:12:59)
>> I've been unable to upgrade nodejs and nodejs-dev thanks to this issue:
>> I need npm for some things, but also php7.0-dev (which depends on
>> libssl-dev) for something else.
> 
> Please share what it is that - transitively or not but _concurrently_ -
> needs both libssl-dev.

A system with (build) dependencies for multiple packages installed.

My unstable system is also affect by this issue, it has php7.0-dev
installed as part of the php-geos build dependencies. Those packages
need to be removed to allow the upgrade of nodejs & nodejs-dev.

Because of the unholy mess that is the OpenSSL 1.1.0 transition and the
complications it brings for the upcoming freeze, Julien Cristau has
suggested to "go back to shipping libssl-dev as 1.0.2 for stretch, and
rebuild the world" [0].

I hope that this happens so that we get rid of issues like this one
caused by libssl-dev and libssl1.0-dev conflicting.

[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827061#1427

Kind Regards,

Bas

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



signature.asc
Description: OpenPGP digital signature

Bug#851261: more tests

[Adam Borowski]

The freeze unblock has been denied.


Some extra data points:
* the patch fixes FTBFS on powerpc too, and on a 32-bit kernel the ioctls
  work (as expected).  I suspect m68k should be same.
* armhf userspace on an arm64 kernel builds but doesn't work

Ie, the build failure and ioctls not working seem to be orthogonal.

-- 
Autotools hint: to do a zx-spectrum build on a pdp11 host, type:
  ./configure --host=zx-spectrum --build=pdp11

Bug#795055: Any progress or updates?

[Andy Simpkins]

Hi Anibal,


It has been a long time since we last caught up!
As part of the Cambridge BSP this weekend [1] I have been looking at
lisence violations such as the one in this bug that is marked as RC.

It is my understanding that there is no problems with the "All rights
reserved" statement included in many of the files without then including
the 3-clause BSD licence text as there is no requirement (only a
recommendation) for licences to appear inside each file only an
overriding external licence text.  This is present.

HOWEVER

Dmitry also points out that there are several files with 4-Clause BSD
licences explicit within them, namely:
 src/crypt_client.c
 tirpc/rpcsvc/crypt.x

As Dmitry points out that this is non-DFSG compliant, so it is these two
files that are the cause for concern


This bug was raised August 2015, and I have not been able to find any
activity since.  Do you have a plan of how to deal with this issue prior
to the release of Stretch?



[1] https://wiki.debian.org/BSP/2017/01/gb/Cambridge



signature.asc
Description: OpenPGP digital signature

Bug#849969: [Pkg-zfsonlinux-devel] Bug#849969: root zpool broken on Debian stretch

[Fabian Grünbichler]

> Lukas Wunner  hat am 28. Januar 2017 um 21:59 geschrieben:
> 
> There are two unrelated glitches though:
> 
> (1) systemd complains on boot:
> 
> "systemd[2234]: zfs-share.service: Failed at step EXEC spawning
>  /usr/sbin/rm: No such file or directory"
> 
> This was introduced by b83d293b8d8d ("Change utilities path (bindir)
> to /usr/sbin (Closes: #832938)").  Adding Eric Desrochers to cc.
> I think fumbling bindir to point to /usr/sbin isn't a good idea,
> instead the three Python scripts should be moved to /usr/sbin in a
> debhelper override.

That's https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842237 - which might 
be nice to tackle with the next upload as well? Simply hardcoding the (correct 
;)) path of 'rm' is the easiest, most straight-forward way IMHO.

Bug#852811: udev: Doesn't start after upgrade

[Michael Biebl]

Am 29.01.2017 um 11:53 schrieb Teemu Ikonen:
> Package: udev
> Version: 232-14
> Followup-For: Bug #852811
> 
> I got same behaviour from udev as Christian on i386 (Apple MacBook2,1).
> Commenting out the lines mentioned above in systemd-udevd.service made
> udev start.
> 
> The problem was version mismatch with udev (232-14) and systemd (232-8).
> systemd upgrade was for some reason kept back by 'apt upgrade'. When I
> installed the systemd 232-14, udev started with the original service
> file.
> 
> Maybe udev should depend on the exact same version of systemd?

According to the reportbug information from Christian, he had 232-14
installed. Which means ppc64 seccomp support being broken is something
different then your issue.

We can't make udev depend on systemd(-sysv) and making systemd depend on
udev is no solution either (it wouldn't prevent such a partial upgrade).
We could however bump the versioned Breaks in udev to systemd (<< 232-11).

This should be tracked as a different bug report though.


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



signature.asc
Description: OpenPGP digital signature

Bug#839048: couchjs crashes on ARM64

[Julien Cristau]

Control: tag -1 stretch-ignore

On Wed, Sep 28, 2016 at 14:51:23 +0800, Zheng Xu wrote:

> Package: libmozjs185-1.0
> 
> root@3aeb83a7878f:~# cat a.js
> print("hello")
> root@3aeb83a7878f:~# couchjs a.js
> Segmentation fault (core dumped)
> 
AIUI this can't be fixed without an ABI bump.  And couchdb is not in
stretch.  So we'll have to ignore this bug for the upcoming release.

Cheers,
Julien

Bug#770369: bug fix for i386

[narf]

Hello,

I have the same problem on debian jessie in i386 architecture.
When will the fixed version (ß-9-6-4) are available i386?

regards
Andy

Bug#850679: etckeeper cron job fails (if no domain name is set)

[Ralf Jung]

I added "bash -x" in /etc/etckeeper/daily in front of the call to
etckeeper itself.  The log doesn't seem very informative to me; it is
included below.
Next, I will add "set -x" to the top of
/etc/etckeeper/commit.d/50vcs-commit.

; Ralf

/etc/cron.hourly/etckeeper:
+ set -e
+ '[' -z '' ']'
+ ETCKEEPER_CONF_DIR=/etc/etckeeper
+ conf=/etc/etckeeper/etckeeper.conf
+ '[' -e /etc/etckeeper/etckeeper.conf ']'
+ . /etc/etckeeper/etckeeper.conf
++ VCS=git
++ GIT_COMMIT_OPTIONS=
++ HG_COMMIT_OPTIONS=
++ BZR_COMMIT_OPTIONS=
++ DARCS_COMMIT_OPTIONS=-a
++ HIGHLEVEL_PACKAGE_MANAGER=apt
++ LOWLEVEL_PACKAGE_MANAGER=dpkg
++ PUSH_REMOTE=
+ '[' -n '' ']'
+ '[' -n '' ']'
+ program_directory=etckeeper
+ '[' -n etckeeper ']'
+
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:etckeeper
+ export PATH
+ '[' '!' -z '' ']'
+ '[' '!' -z '' ']'
+ '[' '!' -z '' ']'
+ '[' '!' -z -a ']'
+ export DARCS_COMMIT_OPTIONS
+ '[' '!' -z apt ']'
+ export HIGHLEVEL_PACKAGE_MANAGER
+ '[' '!' -z dpkg ']'
+ export LOWLEVEL_PACKAGE_MANAGER
+ '[' '!' -z '' ']'
+ '[' '!' -z 1 ']'
+ export AVOID_SPECIAL_FILE_WARNING
+ '[' '!' -z '' ']'
+ '[' -z /root ']'
+ '[' -z commit ']'
+ '[' xcommit = x-h ']'
+ '[' xcommit = x--help ']'
+ '[' xcommit = x-v ']'
+ '[' xcommit = x--version ']'
+ command=commit
+ shift 1
+ '[' commit = post-apt ']'
+ '[' commit = pre-apt ']'
+ echo commit
+ LANG=C
+ egrep -q '[^-a-z_]'
+ '[' '!' -d /etc/etckeeper/commit.d ']'
+ '[' 'xdaily autocommit' = x-d ']'
+ '[' -z '' ']'
+ ETCKEEPER_DIR=/etc
+ cd /etc
+ export ETCKEEPER_DIR
+ '[' -d .git ']'
+ VCS=git
+ '[' -z git ']'
+ export VCS
++ lsscripts /etc/etckeeper/commit.d
++ LANG=C
++ perl -e '
$dir=shift;
print join "\n", grep { ! -d $_ && -x $_ }
grep /^\Q$dir\/\E[-a-zA-Z0-9]+$/,
glob "$dir/*";
' /etc/etckeeper/commit.d
+ for script in $(lsscripts "$ETCKEEPER_CONF_DIR/$command.d")
+ /etc/etckeeper/commit.d/10vcs-test 'daily autocommit'
+ for script in $(lsscripts "$ETCKEEPER_CONF_DIR/$command.d")
+ /etc/etckeeper/commit.d/20store-metadata 'daily autocommit'
+ for script in $(lsscripts "$ETCKEEPER_CONF_DIR/$command.d")
+ /etc/etckeeper/commit.d/30bzr-add 'daily autocommit'
+ for script in $(lsscripts "$ETCKEEPER_CONF_DIR/$command.d")
+ /etc/etckeeper/commit.d/30darcs-add 'daily autocommit'
+ for script in $(lsscripts "$ETCKEEPER_CONF_DIR/$command.d")
+ /etc/etckeeper/commit.d/30git-add 'daily autocommit'
+ for script in $(lsscripts "$ETCKEEPER_CONF_DIR/$command.d")
+ /etc/etckeeper/commit.d/30hg-addremove 'daily autocommit'
+ for script in $(lsscripts "$ETCKEEPER_CONF_DIR/$command.d")
+ /etc/etckeeper/commit.d/50vcs-commit 'daily autocommit'

*** Please tell me who you are.

Run

  git config --global user.email "y...@example.com"
  git config --global user.name "Your Name"

to set your account's default identity.
Omit --global to set the identity only in this repository.

fatal: unable to auto-detect email address (got
'root@r-schwarzschild.(none)')
run-parts: /etc/cron.hourly/etckeeper exited with return code 128

On 16.01.2017 17:13, Antoine Beaupré wrote:
> On 2017-01-16 16:27:22, Ralf Jung wrote:
>> "dnsdomainname" outputs just nothing here.  So something later in the
>> pipeline seems to convert the empty string to "(none)"... or so.
> 
> I haven't seen anything do that in the source - can you run etckeeper
> under bash -x?
> 
> thanks
> 
> a.
> 

Bug#852317: Patch tested with debian package

[Michael Stapelberg]

control: severity -1 serious

Upgraded severity to serious because this issue renders other packages
(e.g. irssi-plugin-robustirc) entirely unusable.

[+cc ghedo directly]

Hi Jan,

Jan Niehusmann  writes:
> the upstream patch (also included in
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852317#5 ) applies to
> the debian package, and fixes the issue.

Thanks for the patch. I can confirm that it fixes the issue and applies
cleanly to the curl packaging as-is.

ghedo, do you need any help with uploading this? I’ll be happy to do an
NMU if you wish. If I don’t hear back from you within the next few days,
I’ll go ahead and do an NMU — this issue is critical enough that we
cannot release stretch without the fix.

-- 
Best regards,
Michael

Bug#852811: udev: Doesn't start after upgrade powerpc

[Michael Biebl]

Am 27.01.2017 um 15:27 schrieb Christian Marillat:
> On 27 janv. 2017 15:16, m...@linux.it (Marco d'Itri) wrote:
> 
>> On Jan 27, Christian Marillat  wrote:
>>
>>> Maybe the problem is because / is a RAID0 ?
>>>
>>> Setting up udev (232-14) ...
>> No. This is the problem:
>>
>>> addgroup: The group `input' already exists as a system group. Exiting.
> 
> I see also this problem on my main machine (i386) but udev don't fail to
> upgrade :
> 
> ,
> | Unpacking udev (232-14) over (232-14) ...
> | Setting up udev (232-14) ...
> | addgroup: The group `input' already exists as a system group. Exiting.
> `


This is not a problem at all, fwiw. It's just adduser being a bit too
verbose, telling you that the input group already exists and that there
is nothing to do.


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



signature.asc
Description: OpenPGP digital signature

Bug#832858: symfony: diff for NMU version 2.8.7+dfsg-1.1

[James Clarke]

Control: tags 832858 + patch

Dear maintainer,

I've prepared an NMU for symfony (versioned as 2.8.7+dfsg-1.1). The diff
is attached to this message. I have uploaded directly to unstable since
there has been no maintainer activity on this bug.

Regards,
James
diff -Nru symfony-2.8.7+dfsg/debian/changelog symfony-2.8.7+dfsg/debian/changelog
--- symfony-2.8.7+dfsg/debian/changelog	2016-06-08 01:52:05.0 +0100
+++ symfony-2.8.7+dfsg/debian/changelog	2017-01-29 13:54:28.0 +
@@ -1,3 +1,12 @@
+symfony (2.8.7+dfsg-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix PHP 7.0/7.1 related failures (Closes: #832858)
+  * Do not depend on a fixed date in layout tests (fixes FTBFS in 2017 and
+beyond)
+
+ -- James Clarke   Sun, 29 Jan 2017 13:54:28 +
+
 symfony (2.8.7+dfsg-1) unstable; urgency=medium
 
   [ Fabien Potencier ]
diff -Nru symfony-2.8.7+dfsg/debian/patches/do-not-depend-on-a-fixed-date-in-layout- symfony-2.8.7+dfsg/debian/patches/do-not-depend-on-a-fixed-date-in-layout-
--- symfony-2.8.7+dfsg/debian/patches/do-not-depend-on-a-fixed-date-in-layout-	1970-01-01 01:00:00.0 +0100
+++ symfony-2.8.7+dfsg/debian/patches/do-not-depend-on-a-fixed-date-in-layout-	2017-01-29 13:54:28.0 +
@@ -0,0 +1,163 @@
+From: Christian Flothmann 
+Date: Sun, 1 Jan 2017 13:18:05 +0100
+X-Dgit-Generated: 2.8.7+dfsg-1.1 804ee09c5a98f4ff4ed1132b68bf4c4afa17facc
+Subject: Do not depend on a fixed date in layout tests
+
+By default, the `DateType` as well as the `DateTimeType` set the choices
+being available for the year to a range starting five years in the past.
+After some time, this will make tests fail when the year of the fixed
+date being used as the initial data is before the first year being part
+of the choices.
+
+Origin: backport, https://github.com/symfony/symfony/commit/97b7fabf519b48333b772924b141f84efdb44c1e
+
+---
+
+--- symfony-2.8.7+dfsg.orig/src/Symfony/Component/Form/Tests/AbstractBootstrap3LayoutTest.php
 symfony-2.8.7+dfsg/src/Symfony/Component/Form/Tests/AbstractBootstrap3LayoutTest.php
+@@ -1346,7 +1346,7 @@ abstract class AbstractBootstrap3LayoutT
+ 
+ public function testDateTime()
+ {
+-$form = $this->factory->createNamed('name', 'Symfony\Component\Form\Extension\Core\Type\DateTimeType', '2011-02-03 04:05:06', array(
++$form = $this->factory->createNamed('name', 'Symfony\Component\Form\Extension\Core\Type\DateTimeType', date('Y').'-02-03 04:05:06', array(
+ 'input' => 'string',
+ 'with_seconds' => false,
+ ));
+@@ -1365,7 +1365,7 @@ abstract class AbstractBootstrap3LayoutT
+ /following-sibling::select
+ [@id="name_date_year"]
+ [@class="form-control"]
+-[./option[@value="2011"][@selected="selected"]]
++[./option[@value="'.date('Y').'"][@selected="selected"]]
+ /following-sibling::select
+ [@id="name_time_hour"]
+ [@class="form-control"]
+@@ -1420,7 +1420,7 @@ abstract class AbstractBootstrap3LayoutT
+ 
+ public function testDateTimeWithHourAndMinute()
+ {
+-$data = array('year' => '2011', 'month' => '2', 'day' => '3', 'hour' => '4', 'minute' => '5');
++$data = array('year' => date('Y'), 'month' => '2', 'day' => '3', 'hour' => '4', 'minute' => '5');
+ 
+ $form = $this->factory->createNamed('name', 'Symfony\Component\Form\Extension\Core\Type\DateTimeType', $data, array(
+ 'input' => 'array',
+@@ -1442,7 +1442,7 @@ abstract class AbstractBootstrap3LayoutT
+ /following-sibling::select
+ [@id="name_date_year"]
+ [@class="form-control"]
+-[./option[@value="2011"][@selected="selected"]]
++[./option[@value="'.date('Y').'"][@selected="selected"]]
+ /following-sibling::select
+ [@id="name_time_hour"]
+ [@class="form-control"]
+@@ -1459,7 +1459,7 @@ abstract class AbstractBootstrap3LayoutT
+ 
+ public function testDateTimeWithSeconds()
+ {
+-$form = $this->factory->createNamed('name', 'Symfony\Component\Form\Extension\Core\Type\DateTimeType', '2011-02-03 04:05:06', array(
++$form = $this->factory->createNamed('name', 'Symfony\Component\Form\Extension\Core\Type\DateTimeType', date('Y').'-02-03 04:05:06', array(
+ 'input' => 'string',
+ 'with_seconds' => true,
+ ));
+@@ -1479,7 +1479,7 @@ abstract class AbstractBootstrap3LayoutT
+ /following-sibling::select
+ [@id="name_date_year"]
+ [@class="form-control"]
+-[./option[@value="2011"][@selected="selected"]]
++[./option[@value="'.date('Y').'"][@selected="selected"]]
+ /following-sibling::select
+ [@id="name_time_hour"]
+ [@class="form-control"]
+@@ -1569,7 +1569,7 @@ abstract class AbstractBootstrap3LayoutT
+ 
+ public function testDateChoice()
+ {
+-$form = $this->factory->create

Bug#849504: Data corruption with copy-on-write and multiple threads

[Wouter Verhelst]

Hi,

On Sun, Jan 29, 2017 at 12:59:35PM +, Jonathan Wiltshire wrote:
> Hi,
> 
> On Wed, Dec 28, 2016 at 12:33:51AM +0100, Wouter Verhelst wrote:
> > We should not release Debian with this bug present; however, I don't
> > want to fix this right now, or 1:3.15.1-1 will miss the freeze cutoff.
> > I'll upload a package as soon as that version migrates to testing.
> 
> nbd 1:3.15.1-1 and then 1:3.15.1-2 migrated on 2016-12-31, so that should
> leave the way clear to fixing this.

Yes; a fix has been committed upstream. I was waiting for the reporter
to help check it, but haven't gotten any response so far.

I'm currently swamped with helping organize FOSDEM (which is next
weekend), but I'll do those tests myself after that if it hasn't
happened yet, and then do the upload.

(I'm also an idiot, in that I filed this bug again, but ah well, I'll
just merge them before uploading)

-- 
< ron> I mean, the main *practical* problem with C++, is there's like a dozen
   people in the world who think they really understand all of its rules,
   and pretty much all of them are just lying to themselves too.
 -- #debian-devel, OFTC, 2016-02-12