Bug#854106: speech-dispatcher: must now default to espeak-ng

[Samuel Thibault]

Package: speech-dispatcher
Version: 0.8.6-2
Severity: serious
Justification: Makes system unaccessible after installation
Tags: patch

Hello,

Now that speech-dispatcher only pulls the espeak-ng module by default,
the default synthesis must also be switched to espeak-ng, otherwise it
would remain silent, and make the installed system completely
unaccessible.  The attached patch fixes this.

Samuel

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

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

Versions of packages speech-dispatcher depends on:
ii  adduser  3.115
ii  libc62.24-9
ii  libdotconf0  1.3-0.2
ii  libglib2.0-0 2.50.2-2
ii  libltdl7 2.4.6-2
ii  libsndfile1  1.0.27-1
ii  libspeechd2  0.8.6-2
ii  lsb-base 9.20161125
ii  speech-dispatcher-audio-plugins  0.8.6-2

Versions of packages speech-dispatcher recommends:
pn  pulseaudio   
ii  speech-dispatcher-espeak-ng  0.8.6-2

Versions of packages speech-dispatcher suggests:
ii  libttspico-utils1.0+git20130326-5
pn  speech-dispatcher-cicero
pn  speech-dispatcher-doc-cs
pn  speech-dispatcher-espeak
pn  speech-dispatcher-festival  
pn  speech-dispatcher-flite 

-- Configuration Files:
/etc/default/speech-dispatcher changed [not included]
/etc/speech-dispatcher/speechd.conf changed [not included]

-- no debconf information

-- 
Samuel
 M.  MIMRAM  Samuel Antonin
 en voila un qui etait predestiné
 -+- #ens-mim - Quelles gueules qu'ils ont les ptits nouveaux ? -+-
commit 1e500060fbe1e08fa840bae81637884abefa4bbd
Author: Luke Yelavich 
Date:   Tue Jan 24 06:19:42 2017 +1100

Set the default output module to espeak-ng

diff --git a/debian/patches/change-default-module.patch 
b/debian/patches/change-default-module.patch
new file mode 100644
index 000..2f4efc4
--- /dev/null
+++ b/debian/patches/change-default-module.patch
@@ -0,0 +1,13 @@
+Index: speech-dispatcher/config/speechd.conf
+===
+--- speech-dispatcher.orig/config/speechd.conf
 speech-dispatcher/config/speechd.conf
+@@ -240,7 +240,7 @@ DefaultVolume 100
+ # The DefaultModule selects which output module is the default.  You
+ # must use one of the names of the modules loaded with AddModule.
+ 
+-DefaultModule espeak
++DefaultModule espeak-ng
+ 
+ # The LanguageDefaultModule selects which output modules are prefered
+ # for specified languages.
diff --git a/debian/patches/series b/debian/patches/series
index cac9c02..acbf68d 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1,3 @@
 pulse-default-latency.patch
 doc-figures
+change-default-module.patch

Bug#853902: icinga-web: Can't locate CGI/Util.pm in @INC during installation

[Chris Lamb]

Hi,

> icinga-web: Can't locate CGI/Util.pm in @INC during installation

Can't seem to reproduce this with a:

  $ sudo env DEBIAN_FRONTEND=noninteractive apt-get install icinga-web

Any ideas? :)


Regards,

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

Bug#853970: marked as done (errors during update: updmap missing maps otf-@jaEmbed@.map etc)

[Debian Bug Tracking System]

Your message dated Sat, 4 Feb 2017 15:44:13 +0900
with message-id <20170204064413.jd6mzrox5grxd...@burischnitzel.preining.info>
and subject line Re: Bug#853970: tex-common: Can't update conffile when apt 
update in stretch
has caused the Debian Bug report #853970,
regarding errors during update: updmap missing maps otf-@jaEmbed@.map etc
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
853970: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853970
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tex-common
Version: 6.06
Severity: important

Dear Maintainer,

   * What led up to the situation?
   apt dist-upgrade

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   I didn't change the default tex configs.

   * What was the outcome of this action?

Setting up tex-common (6.06) ...
Running mktexlsr. This may take some time... done.
Running updmap-sys. This may take some time...
updmap-sys failed. Output has been stored in
/tmp/updmap.RsRHP64d
Please include this file if you report a bug.

Sometimes, not accepting conffile updates in /etc/texmf/updmap.d
causes updmap-sys to fail.  Please check for files with extension
.dpkg-dist or .ucf-dist in this directory

dpkg: error processing package tex-common (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of texlive-lang-japanese:
 texlive-lang-japanese depends on tex-common (>= 6); however:
  Package tex-common is not configured yet.

dpkg: error processing package texlive-lang-japanese (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of texlive-lang-other:
 texlive-lang-other depends on tex-common (>= 6); however:
  Package tex-common is not configured yet.

dpkg: error processing package texlive-lang-other (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of texlive-lang-chinese:
 texlive-lang-chinese depends on tex-common (>= 6); however:
  Package tex-common is not configured yet.

dpkg: error processing package texlive-lang-chinese (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of texlive-lang-korean:
 texlive-lang-korean depends on tex-common (>= 6); however:
  Package tex-common is not configured yet.

dpkg: error processing package texlive-lang-korean (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 tex-common
 texlive-lang-japanese
 texlive-lang-other
 texlive-lang-chinese
 texlive-lang-korean
E: Sub-process /usr/bin/dpkg returned an error code (1)


/tmp/updmap.RsRHP64d reads:

updmap will read the following updmap.cfg files (in precedence order):
  /usr/share/texmf/web2c/updmap.cfg
  /usr/share/texlive/texmf-dist/web2c/updmap.cfg
updmap may write changes to the following updmap.cfg file:
  /etc/texmf/web2c/updmap.cfg
dvips output dir: "/var/lib/texmf/fonts/map/dvips/updmap"
pdftex output dir: "/var/lib/texmf/fonts/map/pdftex/updmap"
dvipdfmx output dir: "/var/lib/texmf/fonts/map/dvipdfmx/updmap"
updmap [ERROR]: The following map file(s) couldn't be found:
updmap [ERROR]: otf-@jaEmbed@.map (in /usr/share/texlive/texmf-
dist/web2c/updmap.cfg)
updmap [ERROR]: otf-ko-@koEmbed@.map (in /usr/share/texlive/texmf-
dist/web2c/updmap.cfg)
updmap [ERROR]: otf-sc-@scEmbed@.map (in /usr/share/texlive/texmf-
dist/web2c/updmap.cfg)
updmap [ERROR]: otf-tc-@tcEmbed@.map (in /usr/share/texlive/texmf-
dist/web2c/updmap.cfg)
updmap [ERROR]: otf-up-@jaEmbed@.map (in /usr/share/texlive/texmf-
dist/web2c/updmap.cfg)
updmap [ERROR]: ptex-@jaEmbed@@jaVariant@.map (in
/usr/share/texlive/texmf-dist/web2c/updmap.cfg)
updmap [ERROR]: uptex-@jaEmbed@@jaVariant@.map (in
/usr/share/texlive/texmf-dist/web2c/updmap.cfg)
updmap [ERROR]: uptex-ko-@koEmbed@.map (in /usr/share/texlive/texmf-
dist/web2c/updmap.cfg)
updmap [ERROR]: uptex-sc-@scEmbed@.map (in /usr/share/texlive/texmf-
dist/web2c/updmap.cfg)
updmap [ERROR]: uptex-tc-@tcEmbed@.map (in /usr/share/texlive/texmf-
dist/web2c/updmap.cfg)
updmap [ERROR]: Did you run mktexlsr?

You can disable non-existent map entries using the option
  --syncwithtrees.

   * What outcome did you expect instead?
   updates successfully.



-- System Information:
Debian Release: 9.0
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing'), (1, 

Bug#852109: marked as done (ntopng: CVE-2017-5473)

[Debian Bug Tracking System]

Your message dated Sat, 04 Feb 2017 04:18:32 +
with message-id 
and subject line Bug#852109: fixed in ntopng 2.4+dfsg1-3
has caused the Debian Bug report #852109,
regarding ntopng: CVE-2017-5473
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
852109: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852109
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ntopng
Severity: grave
Tags: security
Justification: user security hole

Please see https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5473

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: ntopng
Source-Version: 2.4+dfsg1-3

We believe that the bug you reported is fixed in the latest version of
ntopng, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 852...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ludovico Cavedon  (supplier of updated ntopng package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 03 Feb 2017 19:43:00 -0800
Source: ntopng
Binary: ntopng ntopng-data
Architecture: source all amd64
Version: 2.4+dfsg1-3
Distribution: unstable
Urgency: high
Maintainer: Ludovico Cavedon 
Changed-By: Ludovico Cavedon 
Description:
 ntopng - High-Speed Web-based Traffic Analysis and Flow Collection Tool
 ntopng-data - High-Speed Web-based Traffic Analysis and Flow Collection Tool (d
Closes: 852109
Changes:
 ntopng (2.4+dfsg1-3) unstable; urgency=high
 .
   * Import upstream patches fixing CVE-2017-5473. (Closes: #852109)
Checksums-Sha1:
 4e6654c8d1b71c3aecd9172c46adcb6b549d62ef 2208 ntopng_2.4+dfsg1-3.dsc
 66cae040f4d136515cf4ce2f36085ca511165e40 26488 ntopng_2.4+dfsg1-3.debian.tar.xz
 5febda8f6ba3150a95196e364ce91c5ef0f527c3 1273792 
ntopng-data_2.4+dfsg1-3_all.deb
 5472d789263c91343a871c238e85f8b9025ec70c 2118192 
ntopng-dbgsym_2.4+dfsg1-3_amd64.deb
 462b08c6829d43fd317dfce2726b10208cdcf721 7808 
ntopng_2.4+dfsg1-3_amd64.buildinfo
 cc9f2a83b9c9baecaca128cdfe256a089fbdd700 242372 ntopng_2.4+dfsg1-3_amd64.deb
Checksums-Sha256:
 d70cf4b226701a6d02d861873b37ff843f6f5c1e2143f29588d57f563f4278e9 2208 
ntopng_2.4+dfsg1-3.dsc
 e956358e1187e138ab2c0255a208cb5570eaea14017cc7bb1c9fe8db68764f74 26488 
ntopng_2.4+dfsg1-3.debian.tar.xz
 3e40b26051a288641da10e71a10cb135d656c3e3f427457aa817e407a3c070ee 1273792 
ntopng-data_2.4+dfsg1-3_all.deb
 37f147e46aa611b2607ac67e3510d320c070737f6bf0de4f3300cad645b926f1 2118192 
ntopng-dbgsym_2.4+dfsg1-3_amd64.deb
 db618b2e3ce083857804c6db7cf098d1c4b95412b59d824e006362d5d0399264 7808 
ntopng_2.4+dfsg1-3_amd64.buildinfo
 d5ebc62714a7e85276e528b9b45e71f443ce0b14467af282dd967c37740692ca 242372 
ntopng_2.4+dfsg1-3_amd64.deb
Files:
 043e810bf2777823a61deeb0acb7820d 2208 net extra ntopng_2.4+dfsg1-3.dsc
 8abd10150f7835d4c16405ed92a5a155 26488 net extra 
ntopng_2.4+dfsg1-3.debian.tar.xz
 06ec3f745992ee174a3e61c22ba2738a 1273792 net extra 
ntopng-data_2.4+dfsg1-3_all.deb
 ab9ce203415d82b390b8cdcb86b87d81 2118192 debug extra 
ntopng-dbgsym_2.4+dfsg1-3_amd64.deb
 82efccec762681df3e60365da9fe9309 7808 net extra 
ntopng_2.4+dfsg1-3_amd64.buildinfo
 993d3a81c64f4149a227d0d7dae5aa01 242372 net extra ntopng_2.4+dfsg1-3_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEExi9RJLiVCtv386tME8C1Zno4sLAFAliVUHMACgkQE8C1Zno4
sLCang/+NQScsGBD25JU9Q+0gXiWU1ev3u0/HlmXecdv/fFrYfyp7agda7Pqi+Ga
BLVRIHXMsgDnf4m8raWeg4FpCPgtE7xJ0xAoZJqAKnp1xYZeUReQSUjJUAQWHlU0
15n/blEDUOjxucrELM4OieDWqM9V9Gq589yR3ngku7kNj90hE1Ztxxxm+tjkOxiP
Ku4XGE3lwajrU8K7jPuL8p7FAipOuA9NZucX222edx4RyRi3vhRnR8S8Zzgo8U5d
NQExfX76sGYijknFbjiRVK8A9B1DI3yDoUtyQ2bmL1uMOYRMQKu4Te2/U4upmCGQ
sfPuEmFR/wLDDZwGqEuxuoSP/dDlHm+JUlVSrk8bIf2Nbnv+q3LfQdgXq8KORhLo
PyMvmIeV0bephi6EQSTuSepBX3BPwPOa8Wk3SddQC+IWveIYT5T7QdN/i2D4lpTF
PR6LxElGeNH5q9G/o9cgyH+9rHmBcoxAKMiFkxB8RyucObZtMzvarKXT+COqUcpf
DN/7TEBOMlmmsXkystE1A6W902eOzG6KBCD+kuG98NE4ZukwEK6imx8qTwu6QXV8
MIxbu7ChQdRFbGjd9ryq0Dfn34cV1ZpcoegRKkfrOC451uQG8Tke/Q3SKCUPotNE
doqPfQ0Z2UC1bwXw/WAqv9Qiwhp8bxexG4FWBPVXjthTqlLduaA=
=dDic
-END PGP SIGNATURE End Message ---

Bug#851384: closing 851384

[Daniel Kahn Gillmor]

close 851384 0.8.2-1
thanks

This error in ocsp testing for mod_gnutls was dealt with upstream in
version 0.8.2.  Sorry i didn't mention it in debian/changelog during
the upload!

--dkg

Processed: closing 851384

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 851384 0.8.2-1
Bug #851384 [src:mod-gnutls] mod-gnutls: FTBFS on big endian, 
test-27_OCSP_server.bash fails
Marked as fixed in versions mod-gnutls/0.8.2-1.
Bug #851384 [src:mod-gnutls] mod-gnutls: FTBFS on big endian, 
test-27_OCSP_server.bash fails
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
851384: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851384
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#853864: sed-4.4 released (with bugfix)

[Assaf Gordon]

Hello,

sed-4.4 with the segfault bugfix has been released:
 https://lists.gnu.org/archive/html/info-gnu/2017-02/msg1.html

Available here:
 https://ftp.gnu.org/gnu/sed/sed-4.4.tar.xz


regards,
- assaf

Bug#853935: rephrase: No more works with gpg2 and causes one pinentry popup per guess

[Daniel Kahn Gillmor]

On Fri 2017-02-03 14:46:43 -0500, Axel Beckert wrote:
> The attached patch works for me with gpg aka gpg2.
>
> I'd also upload it as NMU in case I don't hear from the Debian
> Forensics team in time before a potential removal from testing (or if
> the team prefers the NMU).

Awesome.  This is very much appreciated, Axel!

 --dkg


signature.asc
Description: PGP signature

Bug#854091: speech-dispatcher-pico cannot be installed in unstable

[Adrian Bunk]

Package: speech-dispatcher-pico
Version: 0.8.6-1
Severity: serious


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

The following packages have unmet dependencies:
 speech-dispatcher-pico : Depends: speech-dispatcher (= 0.8.6-1) but it is not 
going to be installed
E: Unable to correct problems, you have held broken packages.
#


This dependency seems far to strict, it would even break on a binNMU
of either package.

Bug#854082: grub-installer: grub-xen fails to install on i386 or amd64 PV guest

[Cyril Brulebois]

Cyril Brulebois  (2017-02-03):
> Would you be interested in helping test an image with this fix
> included? I can build an amd64 netinst and upload that for your to
> try.

If you're so inclined, here's an image with grub-installer 1.137,
including the change you've suggested:
  https://mraw.org/~kibi/debian-stretch-rc2+xen.iso (~ 300 MB)

sha1sum: 61cca963a5d3bf3cbb33d802b2e337be0f16f643

[Note: This image will be removed from my server once the bug has been
addressed.]

BTW, I think the issue might have been triggered by having the following
line as the first entry of the “case” statement:

*:grub|*:grub-pc|*:grub-efi*|sparc:grub-ieee1275|ppc64el/*:grub-ieee1275)

One might not realize the first part is an “full” architecture,
following the arch/subarch formatn.

Speaking of which, the “sparc:grub-ieee1275” part probably doesn't work…


KiBi.


signature.asc
Description: Digital signature

Processed: severity of 854066 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 854066 important
Bug #854066 [src:linux] linux-image-4.9.0-1-amd64: Several HP desktops do not 
wake up anymore since 4.9
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
854066: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854066
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#854082: grub-installer: grub-xen fails to install on i386 or amd64 PV guest

[Cyril Brulebois]

Hi Sergio,

Sergio Gelato  (2017-02-03):
> Package: grub-installer
> Version: 1.136
> Severity: serious
> 
> The grub installation step reproducibly fails using the latest stretch d-i
> on both i386 and amd64 Xen PV guests. The logs indicate that grub-install is
> looking for /usr/lib/grub/i386-pc instead of /usr/lib/grub/i386-xen, and
> similarly on amd64.
> 
> I think the problem was introduced by
> commit 66f75b7069aeba05eab776b5ac18dffa6874b5f3 .
> 
> Shouldn't amd64:grub-xen and i386:grub-xen read amd64/*:grub-xen and
> i386/*:grub-xen, respectively, when matching against $ARCH:$grub_package ?

Since ARCH is set through archdetect, and since archdetect.c (in
hw-detect) has this as final code:

printf("%s/%s\n", CPU_TEXT, subarch);

… it seems to me we really should be checking for something like what
you're suggesting.

Would you be interested in helping test an image with this fix included?
I can build an amd64 netinst and upload that for your to try.


KiBi.


signature.asc
Description: Digital signature

Bug#851667: #851667 "fix" breaks openjdk 8 on Jessie

[DJDavid98]

​For anyone else having issues with installing Java 8 now, I managed to get
back up and running by using Oracle's official version of Java.

​For convenience here's a list of commands one has to run to get Java 8
working on their Debian Jessie machine​ (until this issue gets resolved):

echo -e "deb http://ppa.launchpad.net/webupd8team/java/ubuntu xenial
main\ndeb-src http://ppa.launchpad.net/webupd8team/java/ubuntu xenial main"
> /etc/apt/sources.list.d/webupd8team-java.list
sudo apt-get update
sudo apt-get install oracle-java8-installer
echo "JAVA_HOME=\"/usr/lib/jvm/java-8-oracle\"" > /etc/environment
source /etc/environment

Bug#851585: [Pkg-nagios-devel] Bug#851585: icinga2-ido-mysql: fails to upgrade from 'jessie': mysql said: ERROR 1067 (42000) at line 10: Invalid default value for 'status_update_time'

[Emilio Pozuelo Monfort]

Control: severity -1 important

On 31/01/17 17:41, Markus Frosch wrote:
> Hello Release team
> - top post for referencing-
> 
> I'd like to ask you about views of this bug.
> 
> We can do the following:
> 
> 1) Update icinga2 to 2.6.1 which includes some other useful changes (see 
> below)
> 2) stretch-ignore the bug, since MySQL 5.7 won't be included in stretch
>(Problem: backports might make a problem then)

If this only happens with mysql-5.7 but not with mariadb-10.1, then this is not
RC. Downgrading. Please bump again if it also happens with mariadb.

It would still be nice to fix this, obviously.

> I could also patch some of the crashing issues, but would rather prefer 2.6.1
> as a cleaner update to maintain in stretch.

Please file an unblock bug with a debdiff or a diff to the new upstream version.

Thanks,
Emilio

Processed: Re: [Pkg-nagios-devel] Bug#851585: icinga2-ido-mysql: fails to upgrade from 'jessie': mysql said: ERROR 1067 (42000) at line 10: Invalid default value for 'status_update_time'

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #851585 [icinga2-ido-mysql] icinga2-ido-mysql: fails to upgrade from 
'jessie': mysql said: ERROR 1067 (42000) at line 10: Invalid default value for 
'status_update_time'
Severity set to 'important' from 'serious'

-- 
851585: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851585
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: found 853864 in 4.3-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 853864 4.3-1
Bug #853864 [sed] sed-4.3 in 'stretch' can segfault - planned upgrade
Marked as found in versions sed/4.3-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
853864: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853864
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#851667: #851667 "fix" breaks openjdk 8 on Jessie

[David Joseph Guzsik]

It's not like me or my users wanted to use ElasticSearch anyway...
Who on earth thought this was a good idea?!

Processed: Re: [pkg-go] Bug#852959: prometheus FTBFS on armhf: github.com/prometheus/prometheus/storage/local fails

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 852959 important
Bug #852959 [src:prometheus] prometheus FTBFS on armhf: 
github.com/prometheus/prometheus/storage/local fails
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
852959: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852959
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#852959: [pkg-go] Bug#852959: prometheus FTBFS on armhf: github.com/prometheus/prometheus/storage/local fails

[Martín Ferrari]

severity 852959 important
thanks


So I finally asked ftpmaster to remove the armhf packages (#848357), to
allow prometheus to migrate and be released with Stretch. This bug still
exists, and I will fix it as soon as the current version migrates to
testing, but it does not affect the architectures that are going to be
released. So I am lowering the severity for now.

Thanks for reporting.


On 28/01/17 11:58, Adrian Bunk wrote:
> Source: prometheus
> Version: 1.5.0+ds-1
> Severity: serious
> 
> https://buildd.debian.org/status/fetch.php?pkg=prometheus=armhf=1.5.0%2Bds-1=1485604675=0
> 
> ...
> goroutine 10024 [chan receive]:
> github.com/prometheus/prometheus/storage/local.(*MemorySeriesStorage).handleEvictList.func1(0x4b165ad0)
>   
> /«BUILDDIR»/prometheus-1.5.0+ds/build/src/github.com/prometheus/prometheus/storage/local/storage.go:1075
>  +0x30
> created by 
> github.com/prometheus/prometheus/storage/local.(*MemorySeriesStorage).handleEvictList
>   
> /«BUILDDIR»/prometheus-1.5.0+ds/build/src/github.com/prometheus/prometheus/storage/local/storage.go:1077
>  +0x358
> exit status 2
> FAIL  github.com/prometheus/prometheus/storage/local  288.359s
> ...
> ___
> Pkg-go-maintainers mailing list
> pkg-go-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
> 


-- 
Martín Ferrari (Tincho)

Bug#852880: marked as done (commons-math3: FTBFS: find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such file or directory)

[Debian Bug Tracking System]

Your message dated Fri, 03 Feb 2017 21:18:35 +
with message-id 
and subject line Bug#852880: fixed in commons-math3 3.6.1-2
has caused the Debian Bug report #852880,
regarding commons-math3: FTBFS: find: 
'/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such 
file or directory
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
852880: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852880
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: commons-math3
Version: 3.6.1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170128 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=maven
>dh_testdir -O--buildsystem=maven
>dh_update_autotools_config -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
> such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
> No such file or directory
>   mh_patchpoms -plibcommons-math3-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>dh_auto_build -O--buildsystem=maven
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
>  -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo package javadoc:jar 
> javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US
> [INFO] Scanning for projects...
> [INFO]
>  
> [INFO] 
> 
> [INFO] Building Apache Commons Math 3.6.1
> [INFO] 
> 
> [INFO] 
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ 
> commons-math3 ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 2 resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.2:compile (default-compile) @ 
> commons-math3 ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 990 source files to /<>/target/classes
> [INFO] 
> /<>/src/main/java/org/apache/commons/math3/optim/BaseOptimizer.java:
>  Some input files use or override a deprecated API.
> [INFO] 
> /<>/src/main/java/org/apache/commons/math3/optim/BaseOptimizer.java:
>  Recompile with -Xlint:deprecation for details.
> [INFO] 
> [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ 
> commons-math3 ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 38 resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.2:testCompile (default-testCompile) @ 
> commons-math3 ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 611 source files to /<>/target/test-classes
> [INFO] 
> /<>/src/test/java/org/apache/commons/math3/optimization/univariate/BrentOptimizerTest.java:
>  Some input files use or override a deprecated API.
> [INFO] 
> /<>/src/test/java/org/apache/commons/math3/optimization/univariate/BrentOptimizerTest.java:
>  Recompile with -Xlint:deprecation for details.
> [INFO] 
> [INFO] --- maven-surefire-plugin:2.17:test (default-test) @ commons-math3 ---
> [INFO] Tests are skipped.
> [INFO] 
> [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ commons-math3 ---
> [INFO] Building jar: /<>/target/commons-math3-3.6.1.jar
> [INFO] 
> [INFO] --- maven-javadoc-plugin:2.10.4:jar (default-cli) @ commons-math3 ---
> [INFO] 
> Loading source files for package org.apache.commons.math3.dfp...
> Loading source files for package 
> org.apache.commons.math3.geometry.partitioning...
> Loading source files for package 
> org.apache.commons.math3.geometry.partitioning.utilities...
> Loading source files for package org.apache.commons.math3.geometry...
> Loading source files for package 
> org.apache.commons.math3.geometry.spherical.twod...
> Loading source files for 

Bug#851819: ERROR: wget failed to download http://people.debian.org/~bartm/...

[Leo L. Schwab]

Package: flashplugin-nonfree
Version: 1:3.7
Followup-For: Bug #851819

  ___ _   _   _ 
|  _ \_ _| \ | |/ ___| |
| |_) | ||  \| | |  _| |
|  __/| || |\  | |_| |_|
|_|  |___|_| \_|\(_)


$ sudo update-flashplugin-nonfree --install --verbose
options :  --install --verbose --
temporary directory: /tmp/flashplugin-nonfree.S4CJ9z75AC
importing public key ...
selected action = --install
installed version = 24.0.0.186
upstream version = 24.0.0.194
wgetoptions= -nd -P .   -v --progress=dot:default 
downloading 
http://people.debian.org/~bartm/flashplugin-nonfree/D5C0FC14/fp.24.0.0.194.sha512.amd64.pgp.asc
 ...
URL transformed to HTTPS due to an HSTS policy
--2017-02-03 12:42:35--  
https://people.debian.org/~bartm/flashplugin-nonfree/D5C0FC14/fp.24.0.0.194.sha512.amd64.pgp.asc
Resolving people.debian.org (people.debian.org)... 5.153.231.30, 
2001:41c8:1000:21::21:30
Connecting to people.debian.org (people.debian.org)|5.153.231.30|:443... 
connected.
HTTP request sent, awaiting response... 404 Not Found
2017-02-03 12:42:36 ERROR 404: Not Found.

cleaning up temporary directory /tmp/flashplugin-nonfree.S4CJ9z75AC ...
ERROR: wget failed to download 
http://people.debian.org/~bartm/flashplugin-nonfree/D5C0FC14/fp.24.0.0.194.sha512.amd64.pgp.asc
More information might be available at:
  http://wiki.debian.org/FlashPlayer




-- Package-specific info:
Debian version: 9.0
Architecture: amd64
Package version: 1:3.7
Adobe Flash Player version: LNX 24,0,0,186
MD5 checksums:
a618a20ef0bf4f463960134486a2ed7b  
/var/cache/flashplugin-nonfree/flash_player_npapi_linux.x86_64.tar.gz
29c85bc8504422120cf89702986ff8e1  
/var/cache/flashplugin-nonfree/get-upstream-version.pl
82cd4f82b2023fad1d43092de8e002a7  
/var/cache/flashplugin-nonfree/install_flash_player_11_linux.x86_64.tar.gz
52d5e951bafcdb493d1a980a62c0f80e  
/usr/lib/flashplugin-nonfree/libflashplayer.so
Alternatives:
flash-mozilla.so - auto mode
  link best version is /usr/lib/flashplugin-nonfree/libflashplayer.so
  link currently points to 
/usr/lib/flashplugin-nonfree/libflashplayer.so
  link flash-mozilla.so is /usr/lib/mozilla/plugins/flash-mozilla.so
/usr/lib/flashplugin-nonfree/libflashplayer.so - priority 50
lrwxrwxrwx 1 root root 34 Aug  4  2016 
/usr/lib/mozilla/plugins/flash-mozilla.so -> /etc/alternatives/flash-mozilla.so
/usr/lib/mozilla/plugins/flash-mozilla.so: symbolic link to 
/etc/alternatives/flash-mozilla.so

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

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

Versions of packages flashplugin-nonfree depends on:
ii  binutils   2.27.90.20170124-2
ii  ca-certificates20161130
ii  debconf [debconf-2.0]  1.5.60
ii  gnupg  2.1.18-3
ii  gnupg2 2.1.18-3
ii  libatk1.0-02.22.0-1
ii  libcairo2  1.14.8-1
ii  libcurl3-gnutls7.52.1-2
ii  libfontconfig1 2.11.0-6.7
ii  libfreetype6   2.6.3-3+b1
ii  libgcc11:6.3.0-5
ii  libglib2.0-0   2.50.2-2
ii  libgtk2.0-02.24.31-2
ii  libnspr4   2:4.12-6
ii  libnss32:3.26.2-1
ii  libpango1.0-0  1.40.3-3
ii  libstdc++6 6.3.0-5
ii  libx11-6   2:1.6.4-3
ii  libxext6   2:1.3.3-1
ii  libxt6 1:1.1.5-1
ii  wget   1.18-4

flashplugin-nonfree recommends no packages.

Versions of packages flashplugin-nonfree suggests:
pn  firefox-esr
ii  fonts-dejavu   2.37-1
pn  hal-flash  
pn  iceweasel  
pn  konqueror-nsplugins
ii  ttf-mscorefonts-installer  3.6
pn  ttf-xfree86-nonfree

-- no debconf information

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 854085 yash: FTBFS: ../yash: parameter `LANG' is not set
Bug #854085 [src:yash] yash: FTBFS: 
Changed Bug title to 'yash: FTBFS: ../yash: parameter `LANG' is not set' from 
'yash: FTBFS: '.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
854085: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854085
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#854085: yash: FTBFS:

[Chris Lamb]

Source: yash
Version: 2.44-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

yash fails to build from source in unstable/amd64:

  […]

 dh_auto_test
make -j1 test VERBOSE=1
  make[1]: Entering directory '«BUILDDIR»'
  make[2]: Entering directory '«BUILDDIR»/builtins'
  make[2]: Nothing to be done for 'all'.
  make[2]: Leaving directory '«BUILDDIR»/builtins'
  make[2]: Entering directory '«BUILDDIR»/lineedit'
  make[2]: Nothing to be done for 'all'.
  make[2]: Leaving directory '«BUILDDIR»/lineedit'
  make[2]: Entering directory '«BUILDDIR»/tests'
  rm -rf alias-p.trs andor-p.trs arith-p.trs async-p.trs bg-p.trs break-p.trs 
builtins-p.trs case-p.trs cd-p.trs cmdsub-p.trs command-p.trs comment-p.trs 
continue-p.trs dot-p.trs errexit-p.trs error-p.trs eval-p.trs exec-p.trs 
exit-p.trs export-p.trs fg-p.trs fnmatch-p.trs for-p.trs fsplit-p.trs 
function-p.trs getopts-p.trs grouping-p.trs if-p.trs input-p.trs job-p.trs 
kill-p.trs lineno-p.trs nop-p.trs option-p.trs param-p.trs path-p.trs 
pipeline-p.trs ppid-p.trs quote-p.trs read-p.trs readonly-p.trs redir-p.trs 
return-p.trs set-p.trs shift-p.trs signal-p.trs simple-p.trs test-p.trs 
testtty-p.trs tilde-p.trs trap-p.trs umask-p.trs unset-p.trs until-p.trs 
wait-p.trs while-p.trs alias-y.trs andor-y.trs arith-y.trs array-y.trs 
async-y.trs bg-y.trs bindkey-y.trs brace-y.trs break-y.trs builtins-y.trs 
case-y.trs cd-y.trs cmdsub-y.trs command-y.trs complete-y.trs continue-y.trs 
dirstack-y.trs disown-y.trs dot-y.trs echo-y.trs errexit-y.trs error-y.trs 
eval-y.trs exec-y.trs exit-y.trs export-y.trs fc-y.trs fg-y.trs for-y.trs 
fsplit-y.trs function-y.trs getopts-y.trs grouping-y.trs hash-y.trs help-y.trs 
history-y.trs historyx-y.trs if-y.trs job-y.trs jobs-y.trs kill-y.trs 
lineno-y.trs option-y.trs param-y.trs pipeline-y.trs printf-y.trs prompt-y.trs 
pwd-y.trs quote-y.trs random-y.trs read-y.trs readonly-y.trs redir-y.trs 
return-y.trs set-y.trs settty-y.trs shift-y.trs signal-y.trs simple-y.trs 
startup-y.trs suspend-y.trs test-y.trs tilde-y.trs times-y.trs trap-y.trs 
typeset-y.trs ulimit-y.trs umask-y.trs unset-y.trs until-y.trs wait-y.trs 
while-y.trs
  make[3]: Entering directory '«BUILDDIR»/tests'
  ./resetsig ../yash ./run-test.sh ../yash alias-p.tst
  ../yash: parameter `LANG' is not set
  Makefile:65: recipe for target 'alias-p.trs' failed
  make[3]: *** [alias-p.trs] Error 2
  make[3]: Leaving directory '«BUILDDIR»/tests'
  Makefile:45: recipe for target 'test' failed
  make[2]: *** [test] Error 2
  make[2]: Leaving directory '«BUILDDIR»/tests'
  Makefile:116: recipe for target 'test' failed
  make[1]: *** [test] Error 2
  make[1]: Leaving directory '«BUILDDIR»'
  dh_auto_test: make -j1 test VERBOSE=1 returned exit code 2
  debian/rules:16: recipe for target 'build' failed
  make: *** [build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  […]

The full build log is attached.


Regards,

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


yash.2.44-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#854084: binaryornot: Non-determistically FTBFS due to unreliable timing in tests

[Chris Lamb]

Source: binaryornot
Version: 0.4.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

binaryornot's testsuite appears to use method timing/benchmarking in
such a way that it will non-deterministically FTBFS:

  […]
  
  ==
  ERROR: test_never_crashes (tests.test_check.TestDetectionProperties)
  --
  Traceback (most recent call last):
File "«BUILDDIR»/tests/test_check.py", line 180, in test_never_crashes
  def test_never_crashes(self, data):
File "/usr/lib/python2.7/dist-packages/hypothesis/core.py", line 438, in 
wrapped_test
  HealthCheck.too_slow,
File "/usr/lib/python2.7/dist-packages/hypothesis/core.py", line 306, in 
fail_health_check
  raise FailedHealthCheck(message)
  FailedHealthCheck: Data generation is extremely slow: Only produced 10 valid 
examples in 0.33 seconds (0 invalid ones and 1 exceeded maximum size). Try 
decreasing size of the data you're generating (with e.g.average_size or 
max_leaves parameters).
  See https://hypothesis.readthedocs.io/en/latest/healthchecks.html for more 
information about this. If you want to disable just this health check, add 
HealthCheck.too_slow to the suppress_health_check settings for this test.
  
  --
  Ran 43 tests in 0.557s
  
  FAILED (errors=1, expected failures=1)
  Test failed: 
  error: Test failed: 
  E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: 
python2.7 setup.py test 
  dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
  debian/rules:7: recipe for target 'build' failed
  make: *** [build] Error 25
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  […]

The full build log is attached.


Regards,

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


binaryornot.0.4.0-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#854082: grub-installer: grub-xen fails to install on i386 or amd64 PV guest

[Sergio Gelato]

Package: grub-installer
Version: 1.136
Severity: serious

The grub installation step reproducibly fails using the latest stretch d-i
on both i386 and amd64 Xen PV guests. The logs indicate that grub-install is
looking for /usr/lib/grub/i386-pc instead of /usr/lib/grub/i386-xen, and
similarly on amd64.

I think the problem was introduced by
commit 66f75b7069aeba05eab776b5ac18dffa6874b5f3 .
Shouldn't amd64:grub-xen and i386:grub-xen read amd64/*:grub-xen and
i386/*:grub-xen, respectively, when matching against $ARCH:$grub_package ?

Bug#853935: rephrase: No more works with gpg2 and causes one pinentry popup per guess

[Axel Beckert]

Control: tags -1 + patch

Hi,

Axel Beckert wrote:
> > the 2.1.x version of GnuPG (which is what will offer /usr/bin/gpg in
> > debian stretch) stores its secret key material in a different way
> > (~/.gnupg/private-keys-v1.d) than gpg1 does (~/.gnupg/secring.gpg).  If
> > you want rephrase to recover a partially-known passphrase against gpg
> > 2.1.x, having one that "works" against gpg1 isn't going to be useful at
> > all.
[...]
> > A better short-term fix would be to add "--pinentry-mode", "loopback" to
> > the arguments passed to the gpg invocations in rephrase.c.
> 
> I'll try to come up with a patch for that.

The attached patch works for me with gpg aka gpg2.

I'd also upload it as NMU in case I don't hear from the Debian
Forensics team in time before a potential removal from testing (or if
the team prefers the NMU).

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
commit befaa3010553b8b3046481487200a17e560e509c
Author: Axel Beckert 
Date:   Fri Feb 3 20:22:30 2017 +0100

Add patch to unconditionally call gpg with "--pinentry-mode loopback"

Closes: #853935

diff --git a/debian/changelog b/debian/changelog
index c75e1c0..51db79c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+rephrase (0.2-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add patch to unconditionally call gpg with "--pinentry-mode loopback".
+(Closes: #853935)
+
+ -- Axel Beckert   Thu, 02 Feb 2017 11:29:59 +0100
+
 rephrase (0.2-1) unstable; urgency=medium
 
   * Team upload.
diff --git a/debian/patches/02_minimal_gpg2_support.patch b/debian/patches/02_minimal_gpg2_support.patch
new file mode 100644
index 000..47f1b47
--- /dev/null
+++ b/debian/patches/02_minimal_gpg2_support.patch
@@ -0,0 +1,23 @@
+Description: Make rephrase working with gpg2
+Author: Axel Beckert  after an idea by Daniel Kahn Gillmor 
+Bug-Debian: https://bugs.debian.org/853935
+
+--- a/rephrase.c
 b/rephrase.c
+@@ -63,14 +63,14 @@
+ struct profile profiles[] = {
+   {
+ "--gpg-key",
+-{ GPG, "--default-key", "%1", "--passphrase-fd", "0", "--batch", "--no-tty", "--dry-run", "--clearsign", "/dev/null", NULL },
++{ GPG, "--pinentry-mode", "loopback", "--default-key", "%1", "--passphrase-fd", "0", "--batch", "--no-tty", "--dry-run", "--clearsign", "/dev/null", NULL },
+ 1,
+ 0,
+ -1
+   },
+   {
+ "--gpg-symmetric",
+-{ GPG, "--passphrase-fd", "0", "--batch", "--no-tty", "--decrypt", "%1", NULL },
++{ GPG, "--pinentry-mode", "loopback", "--passphrase-fd", "0", "--batch", "--no-tty", "--decrypt", "%1", NULL },
+ 1,
+ 0,
+ -1
diff --git a/debian/patches/series b/debian/patches/series
index 99e88ef..96f7bb0 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1 +1,2 @@
 01_fix_bin_path.patch
+02_minimal_gpg2_support.patch


signature.asc
Description: Digital signature

Processed: Re: Bug#853935: rephrase: No more works with gpg2 and causes one pinentry popup per guess

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #853935 [rephrase] rephrase: No more works with gpg2 and causes one 
pinentry popup per guess
Added tag(s) patch.

-- 
853935: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853935
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#854078: network-manager: nm-online returns before network devices got an address

[Uwe Kleine-König]

Package: network-manager
Version: 1.4.4-1
Severity: serious
Tags: upstream
Justification: affects other packages
Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=777831

Hello,

this is to track this bug in the Debian BTS. It is already reported
upstream.

tftpd-hpa has in it's init script

Required-Start:   $local_fs $remote_fs $syslog $network

Still adding to it in do_start()

ip a > /tmp/tftpd-addr-info

results in this content of the above file

1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: wlp2s0:  mtu 1500 qdisc mq state DOWN 
group default qlen 1000
link/ether e6:82:ab:03:8f:6c brd ff:ff:ff:ff:ff:ff

That is, tftpd is started before network is ready. When I log into the
machine, network is available, so the problem is really that nm-online
doesn't block long enough.

Best regards
Uwe

Processed: network-manager: nm-online returns before network devices got an address

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=777831
Bug #854078 [network-manager] network-manager: nm-online returns before network 
devices got an address
Set Bug forwarded-to-address to 
'https://bugzilla.gnome.org/show_bug.cgi?id=777831'.

-- 
854078: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854078
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#845084: marked as done (pylucene FTBFS on mips, mipsel: [compile] Segmentation fault)

[Debian Bug Tracking System]

Your message dated Fri, 03 Feb 2017 19:03:56 +
with message-id 
and subject line Bug#845084: fixed in pylucene 4.10.1+dfsg-2
has caused the Debian Bug report #845084,
regarding pylucene FTBFS on mips, mipsel: [compile] Segmentation fault
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
845084: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845084
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pylucene
Version: 4.10.1+dfsg-1
Severity: serious

https://buildd.debian.org/status/package.php?p=pylucene=sid

...
rm -f lucene-java-4.10.x/lucene/expressions/lib/asm-commons-4.x.jar
find /usr/share/maven-repo -name `basename 
lucene-java-4.10.x/lucene/expressions/lib/asm-commons-4.x.jar` -exec ln -s {} 
lucene-java-4.10.x/lucene/expressions/lib/asm-commons-4.x.jar \;
test -e lucene-java-4.10.x/lucene/expressions/lib/asm-commons-4.x.jar
python2.7 -m jcc.__main__ --jar 
lucene-java-4.10.x/lucene/build/core/lucene-core-4.10.x.jar --jar 
lucene-java-4.10.x/lucene/build/analysis/common/lucene-analyzers-common-4.10.x.jar
 --jar lucene-java-4.10.x/lucene/build/memory/lucene-memory-4.10.x.jar --jar 
lucene-java-4.10.x/lucene/build/highlighter/lucene-highlighter-4.10.x.jar --jar 
build/jar/extensions.jar --jar 
lucene-java-4.10.x/lucene/build/queries/lucene-queries-4.10.x.jar --jar 
lucene-java-4.10.x/lucene/build/queryparser/lucene-queryparser-4.10.x.jar --jar 
lucene-java-4.10.x/lucene/build/sandbox/lucene-sandbox-4.10.x.jar --jar 
lucene-java-4.10.x/lucene/build/analysis/stempel/lucene-analyzers-stempel-4.10.x.jar
 --jar lucene-java-4.10.x/lucene/build/grouping/lucene-grouping-4.10.x.jar 
--jar lucene-java-4.10.x/lucene/build/join/lucene-join-4.10.x.jar --jar 
lucene-java-4.10.x/lucene/build/facet/lucene-facet-4.10.x.jar --jar 
lucene-java-4.10.x/lucene/build/suggest/lucene-suggest-4.10.x.jar --jar 
lucene-java-4.10.x/lucene/build/exp
 ressions/lucene-expressions-4.10.x.jar --output build-python2.7 --debug 
--use_full_names --include 
lucene-java-4.10.x/lucene/build/misc/lucene-misc-4.10.x.jar --include 
lucene-java-4.10.x/lucene/expressions/lib/antlr-runtime-3.x.jar --include 
lucene-java-4.10.x/lucene/expressions/lib/asm-4.x.jar --include 
lucene-java-4.10.x/lucene/expressions/lib/asm-commons-4.x.jar --package 
java.lang java.lang.System java.lang.Runtime --package java.util 
java.util.Arrays java.util.Collections java.util.HashMap java.util.HashSet 
java.util.TreeSet java.lang.IllegalStateException 
java.lang.IndexOutOfBoundsException java.util.NoSuchElementException 
java.text.SimpleDateFormat java.text.DecimalFormat java.text.Collator --package 
java.util.concurrent java.util.concurrent.Executors --package java.util.regex 
--package java.io java.io.StringReader java.io.InputStreamReader 
java.io.FileInputStream java.io.DataInputStream --exclude 
org.apache.lucene.sandbox.queries.regex.JakartaRegexpCapabilities --exclude or
 g.apache.regexp.RegexpTunnel --python lucene --mapping 
org.apache.lucene.document.Document 
'get:(Ljava/lang/String;)Ljava/lang/String;' --mapping java.util.Properties 
'getProperty:(Ljava/lang/String;)Ljava/lang/String;' --sequence 
java.util.AbstractList 'size:()I' 'get:(I)Ljava/lang/Object;' 
org.apache.lucene.index.IndexWriter:getReader --version 4.10.x --module 
python/collections.py --module python/ICUNormalizer2Filter.py --module 
python/ICUFoldingFilter.py --module python/ICUTransformFilter.py  --files 16 
--build 
Makefile:393: recipe for target 'compile' failed
make[2]: *** [compile] Segmentation fault
make[2]: Leaving directory '/«BUILDDIR»/pylucene-4.10.1+dfsg'
debian/rules:38: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/«BUILDDIR»/pylucene-4.10.1+dfsg'
debian/rules:21: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
--- End Message ---
--- Begin Message ---
Source: pylucene
Source-Version: 4.10.1+dfsg-2

We believe that the bug you reported is fixed in the latest version of
pylucene, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 845...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dmitry Nezhevenko  (supplier of updated pylucene package)

Bug#845083: marked as done (pylucene FTBFS on armel, armhf: python2.7 test/test_TermRangeQuery.py terminated by signal 11)

[Debian Bug Tracking System]

Your message dated Fri, 03 Feb 2017 19:03:56 +
with message-id 
and subject line Bug#845083: fixed in pylucene 4.10.1+dfsg-2
has caused the Debian Bug report #845083,
regarding pylucene FTBFS on armel, armhf: python2.7 test/test_TermRangeQuery.py 
terminated by signal 11
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
845083: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845083
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pylucene
Version: 4.10.1+dfsg-1
Severity: serious

https://buildd.debian.org/status/package.php?p=pylucene=sid

...
python2.7 test/test_TermRangeQuery.py 
xargs: python2.7: terminated by signal 11
Makefile:434: recipe for target 'test' failed
make[2]: *** [test] Error 125
--- End Message ---
--- Begin Message ---
Source: pylucene
Source-Version: 4.10.1+dfsg-2

We believe that the bug you reported is fixed in the latest version of
pylucene, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 845...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dmitry Nezhevenko  (supplier of updated pylucene package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 03 Feb 2017 15:10:46 +0200
Source: pylucene
Binary: python-lucene
Architecture: source
Version: 4.10.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Nezhevenko 
Changed-By: Dmitry Nezhevenko 
Description:
 python-lucene - Python extension for accessing Java Lucene
Closes: 839722 845083 845084
Changes:
 pylucene (4.10.1+dfsg-2) unstable; urgency=medium
 .
   * Add wrapper around jcc to avoid build failure on armel, armhf, mips,
 mipsel (Closes: #845083, #845084)
   * Change Build-Depends to libasm-java (Closes: #839722)
   * Update debian/watch
Checksums-Sha1:
 3eb0e0735428423e499572379e5ed353cd93d114 1880 pylucene_4.10.1+dfsg-2.dsc
 425fd800f8fcaf6f43534a1ecdbb4d46ebb26220 9584 
pylucene_4.10.1+dfsg-2.debian.tar.xz
Checksums-Sha256:
 5d798e0bf856afa82c1e6a2636d0f64a47d8efd36139b522dcf6a06965b2b70d 1880 
pylucene_4.10.1+dfsg-2.dsc
 1afa6bf5301f86856afe3eeb3446f9e5346fb5e55380bf45b45c0a9be3133639 9584 
pylucene_4.10.1+dfsg-2.debian.tar.xz
Files:
 dae78f9943e3924693b97e7508e5d2d5 1880 python optional 
pylucene_4.10.1+dfsg-2.dsc
 2306a22162ef75e109b05c87abea0a93 9584 python optional 
pylucene_4.10.1+dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJYlNF8AAoJEPNPCXROn13ZwikQANRcsr1ntl34Jpr6X13Rt9QN
/QG1xafoEGhrFZr9yUT4v1p1kgYEsHO1K46sB8VyeNbwqZ97F5hse7MHY++fuYfO
54X5yVGkBXj6oeJYB6kKA3rOiI/hFAJcA94WccAuU+I7klv6gze2Jszr5yl5C2Bt
FofghsLFQiYdEtgHZH1KsQqoAnkb5HF2QmJyy8JYHQ++MOfkbowE1KbHZ8G1dESu
9bLv3DuE6tmaCVDXC3JOj2d3l/cVtYxH4RYOFSIFjtHXORQMZirp8AjhoT9fbQsy
ZwqBTf4ZRGTqW0YraMp18OTKlX4c0WBJ9Y1LVWKmD8bHsRZwdfgQSdiozXc9oK4s
G9qiNSepXOnTU09GpAwZMDsEc2scaBkwd5YtkAJzymnM3kMjjYpPEX7UNj/Vi0XY
G+jwgLGez5Bi2c6AMa+yWkoupt/ajUPbVJzwOP9KdEgBu6YAvE28Phc51UmSYp2T
p0txTfWbyLA6WOTJLl9GaveTxbKVjS1Db1MF1JcsJM79wcexaf0JwcZfjL9yFR0+
QVfiqglGftwfMEk8Q2fsP9OPdw5OUwcrUQf82Lj3ktmFQAUTaIx2AH8oz58uWkOY
zRGXL26k+9oQxGrv0w6IQlmyxWAsqy5izFBFjyqFBgfYlLD5qetenn0jBhq6iiHE
awkocybom8P69gDDr80+
=z8fZ
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#836862: libreswan: /etc/ipsec.conf is already shipped by strongswan-starter

[Debian Bug Tracking System]

Processing control commands:

> clone 836862 -1
Bug #836862 {Done: Daniel Kahn Gillmor } [libreswan] 
libreswan: /etc/ipsec.conf is already shipped by strongswan-starter
Bug 836862 cloned as bug 854076
> reassign -1 src:strongswan
Bug #854076 {Done: Daniel Kahn Gillmor } [libreswan] 
libreswan: /etc/ipsec.conf is already shipped by strongswan-starter
Bug reassigned from package 'libreswan' to 'src:strongswan'.
No longer marked as found in versions libreswan/3.19-1 and libreswan/3.18-1.
No longer marked as fixed in versions libreswan/3.19-2.
> retitle -1 strongswan-starter should Provide: ike-server, not 
> strongswan-charon
Bug #854076 {Done: Daniel Kahn Gillmor } 
[src:strongswan] libreswan: /etc/ipsec.conf is already shipped by 
strongswan-starter
Changed Bug title to 'strongswan-starter should Provide: ike-server, not 
strongswan-charon' from 'libreswan: /etc/ipsec.conf is already shipped by 
strongswan-starter'.

-- 
836862: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836862
854076: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854076
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#836862: libreswan: /etc/ipsec.conf is already shipped by strongswan-starter

[Daniel Kahn Gillmor]

Control: clone 836862 -1
Control: reassign -1 src:strongswan
Control: retitle -1 strongswan-starter should Provide: ike-server, not 
strongswan-charon

On Tue 2016-09-06 11:46:29 -0400, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package fails to upgrade from
> 'sid' to 'experimental'.
> It installed fine in 'sid', then the upgrade to 'experimental' fails
> because it tries to overwrite other packages files.
>
> See policy 7.6 at
> https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces
>
>>From the attached log (scroll to the bottom...):
>
>   Selecting previously unselected package libreswan.
>   Preparing to unpack .../43-libreswan_3.18-1_amd64.deb ...
>   Unpacking libreswan (3.18-1) ...
>   dpkg: error processing archive 
> /tmp/apt-dpkg-install-za7Gyz/43-libreswan_3.18-1_amd64.deb (--unpack):
>trying to overwrite '/etc/ipsec.conf', which is also in package 
> strongswan-starter 5.5.0-1
>   dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
>
>
> Using Breaks+Replaces would most likely be the wrong solution here.
> If the conffile can be shared by both packages (hopefully it does),
> it should be factored out into a separate package instead and both
> users should add a dependency on this new package.

I'd have expected strongswan-starter to declare itself an "ike-server"
package, so that the existing breaks/replaces/provides trio would here.

ike-server is a virtual package like mail-transport-agent which is
provided by the packages:

 ike
 racoon
 isakmpd
 strongswan-charon
 libreswan

only one of these can be functional on a system at any time anyway.

I'm suprised to see that strongswan-charon is the package providing
ike-server, if stronswan-starter is the package that contains the system
integration.

Here's the current contents of strongswan-charon:

usr/share/strongswan/templates/config/strongswan.d/charon.conf
usr/share/strongswan/templates/config/strongswan.d/charon-logging.conf
usr/share/doc/strongswan-charon/copyright
usr/share/doc/strongswan-charon/changelog.gz
usr/share/doc/strongswan-charon/changelog.Debian.gz
usr/share/doc/strongswan-charon/NEWS.Debian.gz
usr/lib/ipsec/charon
etc/strongswan.d/charon.conf
etc/strongswan.d/charon-logging.conf
etc/apparmor.d/usr.lib.ipsec.charon

None of these are system integration bits, and i don't think this
package should be labeled as the thing that Provides: ike-server.  (i
note that strongswan-charon Depends: strongswan-starter, but i'm not
sure i understand why those deps are in that order instead of the other
way around.

Anyway, i'll make libreswan explicitly conflict with strongswan-starter
to resolve 836862, but hopefully this cloned bug can be resolved on the
strongswan side.

Regards,

-dkg


signature.asc
Description: PGP signature

Bug#851841: marked as done (xonsh: jobs and backgrounding broken)

[Debian Bug Tracking System]

Your message dated Fri, 03 Feb 2017 18:48:46 +
with message-id 
and subject line Bug#851841: fixed in xonsh 0.5.3+dfsg-1
has caused the Debian Bug report #851841,
regarding xonsh: jobs and backgrounding broken
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
851841: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851841
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xonsh
Version: 0.5.2+dfsg-1
Severity: important

Hi,

This is about https://github.com/xonsh/xonsh/issues/2071

>From a comment in there:

  I think there are two separate issues here (that I've noticed).  One is that
  backgrounding doesn't seem to work (the big issue). The other is that while
  the SIGSTOP is sent by Ctrl-Z, the prompt doesn't always return control to
  the user.

This makes xonsh almost unusable, and this version shouldn't migrate to
testing. (imo)


Thanks,
Frederic

-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (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=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xonsh depends on:
ii  python3-pkg-resources  32.3.1-1
ii  python3-ply3.9-1
ii  python3-venv   3.5.1-4
pn  python3:any

Versions of packages xonsh recommends:
ii  python3-prompt-toolkit  1.0.9-1
ii  python3-pygments2.1.3+dfsg-1
ii  python3-setproctitle1.1.10-1

Versions of packages xonsh suggests:
ii  xonsh-doc  0.5.2+dfsg-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: xonsh
Source-Version: 0.5.3+dfsg-1

We believe that the bug you reported is fixed in the latest version of
xonsh, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 851...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gordon Ball  (supplier of updated xonsh package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 10 Jan 2017 18:13:41 +0100
Source: xonsh
Binary: xonsh xonsh-doc
Architecture: source
Version: 0.5.3+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Gordon Ball 
Changed-By: Gordon Ball 
Description:
 xonsh  - Python-ish, BASHwards looking shell
 xonsh-doc  - Python-ish, BASHwards looking shell (documentation)
Closes: 851841
Changes:
 xonsh (0.5.3+dfsg-1) UNRELEASED; urgency=medium
 .
   * Re-enable building documentation with cloud-sptheme, and version the
 build-dependency
   * Update docs-no-imgmath.patch to also fix URL and privacy (external font)
 issues, rename to documentation-fixes.patch
   * Remove unnecessary dependency on python3-pkg-resources
   * Backgrounding fixed upstream (closes: #851841)
Checksums-Sha1:
 be536b04ca9696a4b5b4e4784a6642f5143fadd2 2163 xonsh_0.5.3+dfsg-1.dsc
 45c4b709b65f0c1ac0238507cf663e2219343810 436394 xonsh_0.5.3+dfsg.orig.tar.gz
 286d5c1f3d00d47aaa2167d8f2c1d202a7fffee8 6084 xonsh_0.5.3+dfsg-1.debian.tar.xz
 ac5936743da3515e92797556fe920d1ca0f3bd2a 6497 
xonsh_0.5.3+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 93f2e356bb17b885433b7f684923dac3908d2e26186fed25fa065095f19f316c 2163 
xonsh_0.5.3+dfsg-1.dsc
 9e2d4c4ac0369011fe438bcb918258cd24c0b25a37cd30def46581da35775a02 436394 
xonsh_0.5.3+dfsg.orig.tar.gz
 98d8828cb90f3738a4945a5ecbb85c64b1338dadd65f545b424ef5aea3c3c786 6084 
xonsh_0.5.3+dfsg-1.debian.tar.xz
 c1a464c8031d3b8974da67b747de6c10ba62459d4185e9cea06112360094fdd5 6497 
xonsh_0.5.3+dfsg-1_amd64.buildinfo
Files:
 c65670e2913565acbe5303c65ec3d285 2163 shells optional xonsh_0.5.3+dfsg-1.dsc
 2b5a66484b14311c2a22a6214dfeb2e4 436394 shells optional 
xonsh_0.5.3+dfsg.orig.tar.gz
 e04a4f34d6ed15a7d6217c0e853bd3c5 6084 shells optional 
xonsh_0.5.3+dfsg-1.debian.tar.xz
 59bf12828ee6f62207e99327b5105392 6497 shells optional 
xonsh_0.5.3+dfsg-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 851052 serious
Bug #851052 [abiword] abiword: Work area flickers up to 30 thimes on every 
Charachter input
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
851052: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851052
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#836862: marked as done (libreswan: /etc/ipsec.conf is already shipped by strongswan-starter)

[Debian Bug Tracking System]

Your message dated Fri, 03 Feb 2017 18:03:34 +
with message-id 
and subject line Bug#836862: fixed in libreswan 3.19-2
has caused the Debian Bug report #836862,
regarding libreswan: /etc/ipsec.conf is already shipped by strongswan-starter
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
836862: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836862
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libreswan
Version: 3.18-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package libreswan.
  Preparing to unpack .../43-libreswan_3.18-1_amd64.deb ...
  Unpacking libreswan (3.18-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-za7Gyz/43-libreswan_3.18-1_amd64.deb (--unpack):
   trying to overwrite '/etc/ipsec.conf', which is also in package 
strongswan-starter 5.5.0-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)


Using Breaks+Replaces would most likely be the wrong solution here.
If the conffile can be shared by both packages (hopefully it does),
it should be factored out into a separate package instead and both
users should add a dependency on this new package.


cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: libreswan
Source-Version: 3.19-2

We believe that the bug you reported is fixed in the latest version of
libreswan, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 836...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Kahn Gillmor  (supplier of updated libreswan 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 03 Feb 2017 12:22:16 -0500
Source: libreswan
Binary: libreswan
Architecture: source
Version: 3.19-2
Distribution: unstable
Urgency: medium
Maintainer: Daniel Kahn Gillmor 
Changed-By: Daniel Kahn Gillmor 
Description:
 libreswan  - Internet Key Exchange daemon
Closes: 836862
Changes:
 libreswan (3.19-2) unstable; urgency=medium
 .
   * more fixes from upstream
   * Test proposal for mips and mipsel builds (trying to fix: #853947)
   * conflict directly with strongswan-starter (Closes: #836862)
Checksums-Sha1:
 772815e32a8c091564dac3d0099178af60cdc982 2220 libreswan_3.19-2.dsc
 27e024e18c4bc4f6629432faf5d336573aba8be3 15072 libreswan_3.19-2.debian.tar.xz
Checksums-Sha256:
 3deb501f14d45742044f7b4e57fb597daf45ba1edcc2719685b140cba4ec5167 2220 
libreswan_3.19-2.dsc
 aa2cbca31bc78f28a2a126237cd723910e23b4e0d0ff833ecc090625be3810c8 15072 
libreswan_3.19-2.debian.tar.xz
Files:
 e82c14347d02a0a900455df9956c3817 2220 net optional libreswan_3.19-2.dsc
 68472ae547489240fee64b5e7455879c 15072 net optional 
libreswan_3.19-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJKBAEBCgA0FiEEOCdgUepHf6PklTkyFJitxsGSMjcFAliUwUUWHGRrZ0BmaWZ0
aGhvcnNlbWFuLm5ldAAKCRAUmK3GwZIyNynbEADM0nJbUfzxQifkq2kAXMU1R13y
CMAR6um9SgzH8pXdBbm/o6tIt9F4MDjTP9tBn2mCQMougj7smYdxzcywcgbNVbrT
L6oEcVQJeL+3NHYBbSCYDCwdVJyWEsKjZWA7ijOrmKPUJNgTEqsPAHlaI40mv9SO
r6kGNUqbDPqvw8oChzYDtkec0qsam7V2TbIaE5au49CtbsSgqHKBdFXIxxrtMhFj
/FQt6tg2SqGvdR/2x3NGebm92dCZ46QOin2romrMaXyTSuh/pP4NI1HeZkmnpBk1
ocVTDQbveJvjKxgx16YHr7F20uS+v+CeOqwdjuc2lH3PemfZv3k5qN72jvvN22AS
MhRcAe2bN+o2CKf9Ar+RhT9d0TIqW1THKvXEWVZYrJWpIP534uHifvU9wbGryvLG
C/VTwA8vgD7f3VAhUYhfjrwsAUb1oqvwhszY/dofGQ9gvty4xmdnDxsmj16QwnkM
O+4P3GrmkmOSJPODxDDidDTxVdv0G7vPn0WJv4pYy/K/GxE00OtIAS8zZoHJEjOM
AydcaluSiw5wZRXYyDLjtdaPy2VV2FDwT41YX+eSzHJzRu5HjbivCpFAxs4v9Zte
wvcmrrZ2+I5bBVlinPUHLq7mF3d6wrnV3kUNRuu3W39lO/+5jyvhmAkRBf22i5ON
KlRK0jdM9+bxAQrTBA==
=CzCo
-END PGP SIGNATURE End Message ---

Bug#853935: rephrase: No more works with gpg2 and causes one pinentry popup per guess

[Axel Beckert]

Control: tags -1 - patch

Hi Daniel,

thanks for your insight on that topic.

Daniel Kahn Gillmor wrote:
> > I think to solve this issue for Debian Stretch in the short term,
> > rephrase needs to
> >
> > 1) depend on "gnupg1" instead of "gnupg", and
> > 2) replace all calls to "gpg" with "gpg1".
> >
> > The following patch fixes the issue for me and also reports the correct
> > passphrase if it was under the given variants.
> 
> I don't think this is a sensible change, given the purpose of rephrase.
> 
> the 2.1.x version of GnuPG (which is what will offer /usr/bin/gpg in
> debian stretch) stores its secret key material in a different way
> (~/.gnupg/private-keys-v1.d) than gpg1 does (~/.gnupg/secring.gpg).  If
> you want rephrase to recover a partially-known passphrase against gpg
> 2.1.x, having one that "works" against gpg1 isn't going to be useful at
> all.

I see that one of my assumptions was wrong:

I do seem to be able to do --export-secret-subkeys without a
passphrase in some cases and can import those again with gpg1, but I
can't do that with --export-secret-keys. So my idea to export them
with gpg2 and import them with gpg1 and then use rephrase won't work.

> A better short-term fix would be to add "--pinentry-mode", "loopback" to
> the arguments passed to the gpg invocations in rephrase.c.

I'll try to come up with a patch for that.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Processed: Re: Bug#853935: rephrase: No more works with gpg2 and causes one pinentry popup per guess

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - patch
Bug #853935 [rephrase] rephrase: No more works with gpg2 and causes one 
pinentry popup per guess
Removed tag(s) patch.

-- 
853935: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853935
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#756253: Data in /sys/fs/pstore

[Paolo Cavallini]

I have this [0]. Should/can I remove something?
Please let me know if I can be of help.
All the best.
===
[0]
-r--r--r-- 1 root root 1740 mag 23  2015 dmesg-efi-143240377201001
-r--r--r-- 1 root root 1796 mag 23  2015 dmesg-efi-143240377302001
-r--r--r-- 1 root root 1714 mag 23  2015 dmesg-efi-143240377303001
-r--r--r-- 1 root root 1765 mag 23  2015 dmesg-efi-143240377304001
-r--r--r-- 1 root root 1787 mag 23  2015 dmesg-efi-143240377305001
-r--r--r-- 1 root root 1807 mag 23  2015 dmesg-efi-143240377306001
-r--r--r-- 1 root root 1779 mag 23  2015 dmesg-efi-143240377307001
-r--r--r-- 1 root root 1797 mag 23  2015 dmesg-efi-143240377308001
-r--r--r-- 1 root root 1746 mag 23  2015 dmesg-efi-143240377309001
-r--r--r-- 1 root root 1771 mag 23  2015 dmesg-efi-143240377310001
-r--r--r-- 1 root root 1824 mag 23  2015 dmesg-efi-143240377311001
-r--r--r-- 1 root root 1817 mag 23  2015 dmesg-efi-143240377312001
-r--r--r-- 1 root root 1818 mag 23  2015 dmesg-efi-143240377313001
-r--r--r-- 1 root root 1771 mag 23  2015 dmesg-efi-143240377314001
-r--r--r-- 1 root root 1772 mag 23  2015 dmesg-efi-143240377315001
-r--r--r-- 1 root root  994 ott 16  2015 dmesg-efi-144499093501001
-r--r--r-- 1 root root 1768 ott 16  2015 dmesg-efi-144499093501002
-r--r--r-- 1 root root 1019 ott 16  2015 dmesg-efi-144499093502001
-r--r--r-- 1 root root 1576 ott 16  2015 dmesg-efi-144499093502002
-r--r--r-- 1 root root  942 ott 16  2015 dmesg-efi-144499093503001
-r--r--r-- 1 root root 1267 ott 16  2015 dmesg-efi-144499093503002
-r--r--r-- 1 root root  758 ott 16  2015 dmesg-efi-144499093504001
-r--r--r-- 1 root root 1785 ott 16  2015 dmesg-efi-144499093504002
-r--r--r-- 1 root root  973 ott 16  2015 dmesg-efi-144499093505001
-r--r--r-- 1 root root 1823 ott 16  2015 dmesg-efi-144499093505002
-r--r--r-- 1 root root  935 ott 16  2015 dmesg-efi-144499093506001
-r--r--r-- 1 root root 1773 ott 16  2015 dmesg-efi-144499093506002
-r--r--r-- 1 root root  962 ott 16  2015 dmesg-efi-144499093507001
-r--r--r-- 1 root root 1821 ott 16  2015 dmesg-efi-144499093507002
-r--r--r-- 1 root root  994 ott 16  2015 dmesg-efi-144499093508001
-r--r--r-- 1 root root 1810 ott 16  2015 dmesg-efi-144499093508002
-r--r--r-- 1 root root  940 ott 16  2015 dmesg-efi-144499093509001
-r--r--r-- 1 root root 1814 ott 16  2015 dmesg-efi-144499093509002
-r--r--r-- 1 root root  934 ott 16  2015 dmesg-efi-144499093510001
-r--r--r-- 1 root root 1785 ott 16  2015 dmesg-efi-144499093510002
-r--r--r-- 1 root root  947 ott 16  2015 dmesg-efi-144499093511001
-r--r--r-- 1 root root 1820 ott 16  2015 dmesg-efi-144499093511002
-r--r--r-- 1 root root 1786 ott 16  2015 dmesg-efi-144499093512002
-r--r--r-- 1 root root 1780 ott 16  2015 dmesg-efi-144499093513002
-r--r--r-- 1 root root 1812 ott 16  2015 dmesg-efi-144499093514002
-r--r--r-- 1 root root 1748 ott 16  2015 dmesg-efi-144499093515002
-r--r--r-- 1 root root 1789 ott 16  2015 dmesg-efi-144499093516002
-r--r--r-- 1 root root  945 ott 19  2015 dmesg-efi-144526454201001
-r--r--r-- 1 root root 1017 ott 19  2015 dmesg-efi-144526454202001
-r--r--r-- 1 root root  816 ott 19  2015 dmesg-efi-144526454203001
-r--r--r-- 1 root root  548 ott 19  2015 dmesg-efi-144526454204001
-r--r--r-- 1 root root 1007 ott 19  2015 dmesg-efi-144526454205001
-r--r--r-- 1 root root  959 ott 19  2015 dmesg-efi-144526454206001
-r--r--r-- 1 root root  953 ott 19  2015 dmesg-efi-144526454207001
-r--r--r-- 1 root root  979 ott 19  2015 dmesg-efi-144526454208001
-r--r--r-- 1 root root 1018 ott 19  2015 dmesg-efi-144526454209001
-r--r--r-- 1 root root  986 ott 19  2015 dmesg-efi-144526454210001
-r--r--r-- 1 root root  991 ott 19  2015 dmesg-efi-144526454211001
-r--r--r-- 1 root root 1760 ott 22  2015 dmesg-efi-144549255204002

-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
https://www.google.com/trends/explore?date=all=IT=qgis,arcgis

Processed: Re: Processed (with 1 error): Re: Bug#854059: texlive-base: failure during texlive-lang-japanese jessie->stretch upgrade test

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 852611 854059 853937
Bug #852611 [texlive-lang-japanese] needs stricter dependency on new 
texlive-base for ptex-fontmap changes
Bug #853939 [texlive-lang-japanese] upgrade failed
Bug #853946 [texlive-lang-japanese] tex-common: apt upgrade fails for tex-common
Bug #853948 [texlive-lang-japanese] tex-common: aptitude dist-upgrade and 
install fails with tex-common updmap-sys failed
Bug #854059 [texlive-lang-japanese] texlive-base: failure during 
texlive-lang-japanese jessie->stretch upgrade test
853970 was blocked by: 853946 853939 853948 852611
853970 was not blocking any bugs.
Added blocking bug(s) of 853970: 854059
Bug #853937 [texlive-lang-japanese] [package:tex-common] dist-upgrade fails on 
ann error of updmap-sys, teaving tex-common unconfigured
853970 was blocked by: 853948 854059 853946 853939 852611
853970 was not blocking any bugs.
Added blocking bug(s) of 853970: 853937
Bug #853939 [texlive-lang-japanese] upgrade failed
Bug #853946 [texlive-lang-japanese] tex-common: apt upgrade fails for tex-common
Bug #853948 [texlive-lang-japanese] tex-common: aptitude dist-upgrade and 
install fails with tex-common updmap-sys failed
Merged 852611 853937 853939 853946 853948 854059
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
852611: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852611
853937: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853937
853939: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853939
853946: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853946
853948: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853948
853970: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853970
854059: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854059
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#854059: texlive-base: failure during texlive-lang-japanese jessie->stretch upgrade test

[Karl Fogel]

Norbert Preining  writes:
>reassign 854059 texlive-lang-japanese
>reassign 853937 texlive-lang-japanese
>severity 854059 serious
>severity 853937 serious
>merge 852611 854059 853937
>thanks
>
>Hi Andreas, hi Karl,
>
>already reported and will hopefully be fixed by src:texlive-base
>transitioning to testing soon.

Thank you, Norbert.  Will keep an eye out for it.

Processed (with 1 error): Re: Bug#854059: texlive-base: failure during texlive-lang-japanese jessie->stretch upgrade test

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 854059 texlive-lang-japanese
Bug #854059 [texlive-base] texlive-base: failure during texlive-lang-japanese 
jessie->stretch upgrade test
Bug reassigned from package 'texlive-base' to 'texlive-lang-japanese'.
No longer marked as found in versions texlive-base/2016.20161130-1.
Ignoring request to alter fixed versions of bug #854059 to the same values 
previously set
> reassign 853937 texlive-lang-japanese
Bug #853937 [tex-common] [package:tex-common] dist-upgrade fails on ann error 
of updmap-sys, teaving tex-common unconfigured
Bug reassigned from package 'tex-common' to 'texlive-lang-japanese'.
No longer marked as found in versions tex-common/6.06.
Ignoring request to alter fixed versions of bug #853937 to the same values 
previously set
> severity 854059 serious
Bug #854059 [texlive-lang-japanese] texlive-base: failure during 
texlive-lang-japanese jessie->stretch upgrade test
Ignoring request to change severity of Bug 854059 to the same value.
> severity 853937 serious
Bug #853937 [texlive-lang-japanese] [package:tex-common] dist-upgrade fails on 
ann error of updmap-sys, teaving tex-common unconfigured
Ignoring request to change severity of Bug 853937 to the same value.
> merge 852611 854059 853937
Bug #852611 [texlive-lang-japanese] needs stricter dependency on new 
texlive-base for ptex-fontmap changes
Bug #853939 [texlive-lang-japanese] upgrade failed
Bug #853946 [texlive-lang-japanese] tex-common: apt upgrade fails for tex-common
Bug #853948 [texlive-lang-japanese] tex-common: aptitude dist-upgrade and 
install fails with tex-common updmap-sys failed
Unable to merge bugs because:
blocks of #853937 is '' not '853970'
blocks of #854059 is '' not '853970'
Failed to merge 852611: Did not alter merged bugs.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
852611: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852611
853937: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853937
853939: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853939
853946: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853946
853948: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853948
854059: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854059
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#853937: Bug#854059: texlive-base: failure during texlive-lang-japanese jessie->stretch upgrade test

[Norbert Preining]

reassign 854059 texlive-lang-japanese
reassign 853937 texlive-lang-japanese
severity 854059 serious
severity 853937 serious
merge 852611 854059 853937
thanks

Hi Andreas, hi Karl,

already reported and will hopefully be fixed by src:texlive-base
transitioning to testing soon.

Norbert

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

Bug#852751: [cryptkeeper] Sets the same password "p" for everything independently of user input

[Tony Sultana]

Will a conflict encfs still permit use of cryptkeeper with existing encfs 
folders?  If yes, then that may be a good approach. 

Another approach, probably out of scope, would be to disable New Folder 
functionality in cryptkeeper and instruct users to the shell with encfs.⁣

Tony

On Feb 1, 2017, 3:57 PM, at 3:57 PM, Eduard Bloch  wrote:
>Hallo,
>* Francesco Namuri [Tue, Jan 31 2017, 06:06:01PM]:
>
>> > Yes, I agree that it's easily discoverable--which is why I'm
>concerned
>> > that simply removing the entire functionality of the package
>without
>> > any kind of notification to the user isn't the best way to address
>the
>> > problem. Again: removing the package simply ensures that people
>> > upgrading to stretch will either end up with a cryptkeeper package
>> > that exhibits this bug, or will remove their cryptkeeper package
>and
>> > not know how to access their stored data, right?
>> > 
>> > Mike Stone
>> 
>> Hello Mike,
>> thanks for the comments.
>> 
>> This issue only affectes the cryptkeeper working with encfs 1.9.1-3,
>in
>> stable we have 1.7.4-5 that works as cryptkeeper expects.
>> 
>> People that upgrades from jessie to stretch simple "loses"
>cryptkeeper,
>> package, of course they are still able to access their stored data
>using
>> encfs or any other frontend to it.
>> 
>> IMHO it's better to remove the program in any envrionment that is
>affected
>> by this issue, putting a note in the README or also on the debconf
>isn't
>> enough to balance the gravity of the issue. Users can think they lost
>data
>> because of a wrong password, or even worst they can trust on a
>worthless
>> data encryption.
>
>Also many thanks from my side...
>
>So I guess I better upload an encfs package which simply conflicts with
>cryptkeeper or does anyone have a better idea?
>
>Best Regards,
>Eduard.

Bug#848574: openmpi: frequent segfault in linker on mips64el

[James Cowgill]

Hi,

So I have been looking at this on and off for some time now but I've
been unable to make much progress on it.

Whatever the bug is, it's causing heap corruption which causes
things to segfault before MPI_Init returns. While most of the time it
segfaults, sometimes it prints other openmpi errors, and sometimes
glibc aborts due to detecting heap corruption.

There is probably a threading data race issue here as well. If I run
the test program on an idle machine with "taskset 1" (so it only runs
on 1 CPU) then the errors go away. I expect this is the reason why the
specific error message is not 100% reproducible for me.

On Mon, 23 Jan 2017 23:20:23 +0800 YunQiang Su  wrote:
> It is quite strange that it won't fail if run with gdb.

I guess this is due to gdb slowing down certain threads.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#853937: [package:tex-common] dist-upgrade fails on ann error of updmap-sys, teaving tex-common unconfigured

[Karl Fogel]

I'm also experiencing this bug, FWIW.  This is on a Deban GNU/Linux 'testing' 
distro system, dist-upgraded daily:

  Linux kwork 4.9.0-1-amd64 #1 SMP Debian 4.9.2-2 (2017-01-12) x86_64 GNU/Linux

At the end of this mail, I'll include the full output of 'apt-get 
dist-upgrade', but first here's the file '/tmp/updmap.75oY5hgf', which was 
given when 'updmap-sys' failed:

  updmap will read the following updmap.cfg files (in precedence order):
/usr/share/texmf/web2c/updmap.cfg
/usr/share/texlive/texmf-dist/web2c/updmap.cfg
  updmap may write changes to the following updmap.cfg file:
/etc/texmf/web2c/updmap.cfg
  dvips output dir: "/var/lib/texmf/fonts/map/dvips/updmap"
  pdftex output dir: "/var/lib/texmf/fonts/map/pdftex/updmap"
  dvipdfmx output dir: "/var/lib/texmf/fonts/map/dvipdfmx/updmap"
  updmap [ERROR]: The following map file(s) couldn't be found:
  updmap [ERROR]:   otf-@jaEmbed@.map (in 
/usr/share/texlive/texmf-dist/web2c/updmap.cfg)
  updmap [ERROR]:   otf-ko-@koEmbed@.map (in 
/usr/share/texlive/texmf-dist/web2c/updmap.cfg)
  updmap [ERROR]:   otf-sc-@scEmbed@.map (in 
/usr/share/texlive/texmf-dist/web2c/updmap.cfg)
  updmap [ERROR]:   otf-tc-@tcEmbed@.map (in 
/usr/share/texlive/texmf-dist/web2c/updmap.cfg)
  updmap [ERROR]:   otf-up-@jaEmbed@.map (in 
/usr/share/texlive/texmf-dist/web2c/updmap.cfg)
  updmap [ERROR]:   ptex-@jaEmbed@@jaVariant@.map (in 
/usr/share/texlive/texmf-dist/web2c/updmap.cfg)
  updmap [ERROR]:   uptex-@jaEmbed@@jaVariant@.map (in 
/usr/share/texlive/texmf-dist/web2c/updmap.cfg)
  updmap [ERROR]:   uptex-ko-@koEmbed@.map (in 
/usr/share/texlive/texmf-dist/web2c/updmap.cfg)
  updmap [ERROR]:   uptex-sc-@scEmbed@.map (in 
/usr/share/texlive/texmf-dist/web2c/updmap.cfg)
  updmap [ERROR]:   uptex-tc-@tcEmbed@.map (in 
/usr/share/texlive/texmf-dist/web2c/updmap.cfg)
  updmap [ERROR]: Did you run mktexlsr?
  
You can disable non-existent map entries using the option
  --syncwithtrees.
  
Here's the output of 'apt-get update' and 'apt-get dist-upgrade':

  # date
  Fri Feb  3 10:30:30 CST 2017
  # apt-get update
  Hit:1 http://debian.csail.mit.edu/debian testing InRelease
  Hit:2 http://debian.csail.mit.edu/debian testing-updates InRelease
  Hit:3 http://security.debian.org testing/updates InRelease
  Reading package lists... Done
  # apt-get dist-upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following packages have been kept back:
libboost-date-time-dev libboost-dev libboost-filesystem-dev
libboost-iostreams-dev libboost-system-dev
  0 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.
  17 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Setting up tex-common (6.06) ...
  debconf: unable to initialize frontend: Dialog
  debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell 
buffer, or without a controlling terminal.)
  debconf: falling back to frontend: Readline
  Running mktexlsr. This may take some time... done.
  Running mtxrun --generate. This may take some time... done.
  Running updmap-sys. This may take some time... 
  updmap-sys failed. Output has been stored in
  /tmp/updmap.75oY5hgf
  Please include this file if you report a bug.
  
  Sometimes, not accepting conffile updates in /etc/texmf/updmap.d
  causes updmap-sys to fail.  Please check for files with extension
  .dpkg-dist or .ucf-dist in this directory
  
  dpkg: error processing package tex-common (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of texlive-lang-arabic:
   texlive-lang-arabic depends on tex-common (>= 6); however:
Package tex-common is not configured yet.
  
  dpkg: error processing package texlive-lang-arabic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of texlive-lang-spanish:
   texlive-lang-spanish depends on tex-common (>= 6); however:
Package tex-common is not configured yet.
  
  dpkg: error processing package texlive-lang-spanish (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of texlive-lang-european:
   texlive-lang-european depends on tex-common (>= 6); however:
Package tex-common is not configured yet.
  
  dpkg: error processing package texlive-lang-european (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of texlive-lang-italian:
   texlive-lang-italian depends on tex-common (>= 6); however:
Package tex-common is not configured yet.
  
  dpkg: error processing package texlive-lang-italian (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent 

Bug#853998: marked as done (CVE-2017-3250 / CVE-2017-3249 / CVE-2017-3247 / CVE-2016-5528 / CVE-2016-5519)

[Debian Bug Tracking System]

Your message dated Fri, 3 Feb 2017 17:25:57 +0100
with message-id <20170203162557.nqyxbmc6lqdebwjm@pisco.westfalen.local>
and subject line Re: Bug#853998: CVE-2017-3250 / CVE-2017-3249 / CVE-2017-3247 
/ CVE-2016-5528 / CVE-2016-5519
has caused the Debian Bug report #853998,
regarding CVE-2017-3250 / CVE-2017-3249 / CVE-2017-3247 / CVE-2016-5528 / 
CVE-2016-5519
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
853998: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853998
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glassfish
Severity: grave
Tags: security

So Oracle has these lovely, unspecified vulnerabilities reported against 
Glassfish,
but it's my understanding that the Debian package only provides a minor subset
what usually constitutes Java, so could you have a look, which of 

http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html

might possibly affect the Debian package?

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
On Fri, Feb 03, 2017 at 12:16:07AM +0100, Emmanuel Bourg wrote:
> Le 2/02/2017 à 23:08, Moritz Muehlenhoff a écrit :
> 
> > So Oracle has these lovely, unspecified vulnerabilities reported against 
> > Glassfish,
> > but it's my understanding that the Debian package only provides a minor 
> > subset
> > what usually constitutes Java, so could you have a look, which of 
> > 
> > http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html
> > 
> > might possibly affect the Debian package?
> 
> I think this is unlikely to affect our packages. We only have two
> specification packages (glassfish-javaee and glassfish-jmac-api) and an
> Object/Relational mapper (glassfish-toplink-essentials) that is never
> used at runtime.

OK, I've marked these as not-affected in the security tracker, then.

Cheers,
Moritz--- End Message ---

Bug#854066: linux-image-4.9.0-1-amd64: Several HP desktops do not wake up anymore since 4.9

[Patrick Matthäi]

Package: src:linux
Version: 4.9.2-2
Justification: causes non-serious data loss
Severity: grave

Dear Maintainer,

*** Reporter, please consider answering these questions, where
appropriate ***

Since we have upgraded several HP desktops (Prodesk G400 G1,G2,G3 and a
Z220 from that I am writing),
the desktops do not wake up anymore if they go into standbye.
I also already tested 4.9.6-3 from unstable, which is also affected.

All PCs do have got the same GPU and they are working fine again if we
switch them back to
linux-image-4.8.0-2-amd64 (4.8.15-2).

I cant find any crash information or debug output to provide more
information about this yet..


*** End of the template - remove these template lines ***


-- Package-specific info:
** Version:
Linux version 4.9.0-1-amd64 (debian-ker...@lists.debian.org) (gcc
version 6.3.0 20170124 (Debian 6.3.0-5) ) #1 SMP Debian 4.9.6-3 (2017-01-28)

** Command line:
BOOT_IMAGE=/vmlinuz-4.9.0-1-amd64 root=/dev/mapper/LEOPC40--vg-root ro quiet

** Tainted: OE (12288)
 * Out-of-tree module has been loaded.
 * Unsigned module has been loaded.

** Kernel log:

** Model information
[2.479586] Adding 16719868k swap on /dev/mapper/LEOPC40--vg-swap_1. 
Priority:-1 extents:1 across:16719868k SSFS
[2.488264] intel_rapl: Found RAPL domain package
[2.488265] intel_rapl: Found RAPL domain core
[2.488266] intel_rapl: Found RAPL domain uncore
[2.488270] intel_rapl: RAPL package 0 domain package locked by BIOS
[2.494958] [drm] UVD initialized successfully.
[2.500473] EXT4-fs (sdb2): mounting ext3 file system using the ext4
subsystem
[2.604214] [drm] ring test on 6 succeeded in 15 usecs
[2.604224] [drm] ring test on 7 succeeded in 3 usecs
[2.604225] [drm] VCE initialized successfully.
[2.605801] [drm] ib test on ring 0 succeeded in 0 usecs
[2.607045] EXT4-fs (sdb2): mounted filesystem with ordered data
mode. Opts: (null)
[2.752710] clocksource: Switched to clocksource tsc
[2.767265] random: crng init done
[2.838322] EXT4-fs (sda1): mounted filesystem with ordered data
mode. Opts: errors=remount-ro
[3.124753] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[3.136582] [drm] ib test on ring 1 succeeded in 0 usecs
[3.327708] vboxdrv: loading out-of-tree module taints kernel.
[3.327874] vboxdrv: module verification failed: signature and/or
required key missing - tainting kernel
[3.329836] vboxdrv: Found 4 processor cores
[3.352808] vboxdrv: TSC mode is Invariant, tentative frequency
3192672901 Hz
[3.352810] vboxdrv: Successfully loaded version 5.1.14_Debian
(interface 0x0028)
[3.355952] VBoxNetFlt: Successfully started.
[3.358502] VBoxNetAdp: Successfully started.
[3.361119] VBoxPciLinuxInit
[3.362107] vboxpci: IOMMU not found (not registered)
[3.362939] scsi 6:0:0:0: Direct-Access Generic- Compact Flash   
1.00 PQ: 0 ANSI: 0 CCS
[3.364931] scsi 6:0:0:1: Direct-Access Generic- SM/xD-Picture   
1.00 PQ: 0 ANSI: 0 CCS
[3.366800] scsi 6:0:0:2: Direct-Access Generic- SD/MMC  
1.00 PQ: 0 ANSI: 0 CCS
[3.368823] scsi 6:0:0:3: Direct-Access Generic- M.S./M.S.Pro/HG 
1.00 PQ: 0 ANSI: 0 CCS
[3.370814] scsi 6:0:0:4: Direct-Access Generic- SD/MMC/M.S.PRO  
1.00 PQ: 0 ANSI: 0 CCS
[3.371161] sd 6:0:0:0: Attached scsi generic sg3 type 0
[3.371300] sd 6:0:0:1: Attached scsi generic sg4 type 0
[3.371410] sd 6:0:0:2: Attached scsi generic sg5 type 0
[3.371511] sd 6:0:0:3: Attached scsi generic sg6 type 0
[3.371617] sd 6:0:0:4: Attached scsi generic sg7 type 0
[3.485729] sd 6:0:0:0: [sdc] Attached SCSI removable disk
[3.487588] sd 6:0:0:1: [sdd] Attached SCSI removable disk
[3.489746] sd 6:0:0:2: [sde] Attached SCSI removable disk
[3.491558] sd 6:0:0:3: [sdf] Attached SCSI removable disk
[3.493588] sd 6:0:0:4: [sdg] Attached SCSI removable disk
[3.648608] [drm] ib test on ring 2 succeeded in 0 usecs
[3.648660] [drm] ib test on ring 3 succeeded in 0 usecs
[3.648729] [drm] ib test on ring 4 succeeded in 0 usecs
[4.192562] [drm] ib test on ring 5 succeeded
[4.213285] [drm] ib test on ring 6 succeeded
[4.213998] [drm] ib test on ring 7 succeeded
[4.215139] [drm] Radeon Display Connectors
[4.215140] [drm] Connector 0:
[4.215140] [drm]   DP-3
[4.215141] [drm]   HPD2
[4.215142] [drm]   DDC: 0x6540 0x6540 0x6544 0x6544 0x6548 0x6548
0x654c 0x654c
[4.215142] [drm]   Encoders:
[4.215143] [drm] DFP1: INTERNAL_UNIPHY2
[4.215143] [drm] Connector 1:
[4.215144] [drm]   HDMI-A-3
[4.215144] [drm]   HPD3
[4.215145] [drm]   DDC: 0x6550 0x6550 0x6554 0x6554 0x6558 0x6558
0x655c 0x655c
[4.215145] [drm]   Encoders:
[4.215146] [drm] DFP2: INTERNAL_UNIPHY2
[4.215146] [drm] Connector 2:
[4.215146] [drm]   DVI-D-1
[4.215147] [drm]   HPD1
[4.215148] [drm]   DDC: 0x6560 0x6560 0x6564 0x6564 0x6568 0x6568
0x656c 0x656c
[4.215148] [drm]   

Bug#854042: db insert crashes

[Jörg Frings-Fürst]

Hello Carsten,


Am Freitag, den 03.02.2017, 15:31 +0100 schrieb Carsten Leonhardt:
> Control: reassign -1 bacula-director-mysql
> 
> Hi,
[...]

> while you didn't say so in your bug report, I suppose you are using a
> MySQL-Database.
> 
> Your problem is discussed here:
> 
> https://sourceforge.net/p/bacula/mailman/bacula-users/thread/30db3ed3-64e9-53f6-8b65-8147a9575776%40caerllewys.net/#msg35406296
> 
> So, did you upgrade your MySQL-Server just before the errors started
> occuring? If yes, from which version to which? Or did you maybe purge
> your MySQL-Server and then reinstalled a newer version or something like
> that?
> 
Yes. The update was at 2017-02-01 from version 5.6.35-1 to 5.7.17-1.



>  - Carsten
> 

CU
Jörg
-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser

Threema: SYR8SJXB

IRC: j_...@freenode.net
 j_...@oftc.net

My wish list: 
 - Please send me a picture from the nature at your home.


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

Bug#843251: udev i386 232-15 . .

[Ola Dunk]

Not a smooth upgrade but better than udev i386 232-1[3,4].
Both left my  test system unbootable

Cut from the upgrade terminal.

Setting up udev (232-15) ...
addgroup: The group `input' already exists as a system group. Exiting.
Job for systemd-udevd.service failed because a timeout was exceeded.
See "systemctl status systemd-udevd.service" and "journalctl -xe" for
details.
invoke-rc.d: initscript udev, action "restart" failed.
● systemd-udevd.service - udev Kernel Device Manager
   Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static;
vendor preset: enabled)
   Active: activating (start) since Fri 2017-02-03 14:32:57 UTC; 18ms ago
 Docs: man:systemd-udevd.service(8)
   man:udev(7)
 Main PID: 26844 (systemd-udevd)
Tasks: 1
   CGroup: /system.slice/systemd-udevd.service
   └─26844 /lib/systemd/systemd-udevd

Feb 03 14:32:57 unassigned-hostname systemd[1]: Starting udev Kernel Device
…...
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error processing package udev (--configure):
 subprocess installed post-installation script returned error exit status 1

To get it right I had to

root@unassigned-hostname:/home/datb# dpkg -i udev_232-15_i386.deb
(Reading database ... 170141 files and directories currently installed.)
Preparing to unpack udev_232-15_i386.deb ...
Unpacking udev (232-15) over (232-15) ...
Setting up udev (232-15) ...
addgroup: The group `input' already exists as a system group. Exiting.
update-initramfs: deferring update (trigger activated)
Processing triggers for systemd (232-15) ...
Processing triggers for man-db (2.7.6.1-2) ...
Processing triggers for initramfs-tools (0.120) ...
update-initramfs: Generating /boot/initrd.img-4.10.0-041000rc4-generic

Bug#853892: marked as done (bedops: /usr/bin/starch is already used by coop-computing-tools)

[Debian Bug Tracking System]

Your message dated Fri, 03 Feb 2017 15:03:33 +
with message-id 
and subject line Bug#853892: fixed in bedops 2.4.20+dfsg-2
has caused the Debian Bug report #853892,
regarding bedops: /usr/bin/starch is already used by coop-computing-tools
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
853892: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853892
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bedops
Version: 2.4.20+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.
Since coop-computing-tools has been in the archive for several years
already, bedops will have to rename the conflicting program.

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

  Selecting previously unselected package bedops.
  Preparing to unpack .../5-bedops_2.4.20+dfsg-1_amd64.deb ...
  Unpacking bedops (2.4.20+dfsg-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-W94bnb/5-bedops_2.4.20+dfsg-1_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/starch', which is also in package 
coop-computing-tools 4.0-1.1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-W94bnb/5-bedops_2.4.20+dfsg-1_amd64.deb


cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: bedops
Source-Version: 2.4.20+dfsg-2

We believe that the bug you reported is fixed in the latest version of
bedops, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 853...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Olivier Sallou  (supplier of updated bedops package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 03 Feb 2017 11:26:22 +
Source: bedops
Binary: bedops
Architecture: source amd64
Version: 2.4.20+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Olivier Sallou 
Description:
 bedops - high-performance genomic feature operations
Closes: 853892 854003
Changes:
 bedops (2.4.20+dfsg-2) unstable; urgency=medium
 .
   * avoid underlinking when linking with --as-needed (Closes: #854003)
 Thanks to gin...@debian.org
   * rename starch binary to bedops-starch (Closes: #853892)
Checksums-Sha1:
 eefa8e10ccad3cb36d53a67405e6527a56494989 1999 bedops_2.4.20+dfsg-2.dsc
 0a40796c25046e77bbb263ad6e55dfe5cdfa5742 5340 
bedops_2.4.20+dfsg-2.debian.tar.xz
 808abe430a465e7a465a4e27b6c5d739c436d592 3772 
bedops-dbgsym_2.4.20+dfsg-2_amd64.deb
 e6cbf5ef8dad8149a07ec61207b034c6dc6832a7 5756 
bedops_2.4.20+dfsg-2_amd64.buildinfo
 ac9ae123093d841307e30302552f85f59ad30ec9 12524842 
bedops_2.4.20+dfsg-2_amd64.deb
Checksums-Sha256:
 6f10a72834134d1aaa49d5d64f2b577badcb673fdc6d0bc465bbd60d27bb2e4f 1999 
bedops_2.4.20+dfsg-2.dsc
 882479241291630984a27a3c7183a6a593024d4dab85a60c66a929460add 5340 
bedops_2.4.20+dfsg-2.debian.tar.xz
 0f54aab8ba12a39eccec77e4ae29fc0ba9b6aa1d5d27a01601c1e3cc6d2dbd4b 3772 
bedops-dbgsym_2.4.20+dfsg-2_amd64.deb
 07f1eecdad4c1343283c7abfd7d39297d629a1e5bc583cd4f3cfd729ba218743 5756 
bedops_2.4.20+dfsg-2_amd64.buildinfo
 8bd94ff15a23b486d85621a5f4c70ad4712af980f08722411b94a81608650b10 12524842 
bedops_2.4.20+dfsg-2_amd64.deb
Files:
 999ddf6510ea342452c5b61dc5f6c308 1999 science optional bedops_2.4.20+dfsg-2.dsc
 4d483bedbe9dfe2e1bdb555eff31776a 5340 science optional 
bedops_2.4.20+dfsg-2.debian.tar.xz
 1d4ddf6074bd1072b05d6aa09d4000a3 3772 debug extra 
bedops-dbgsym_2.4.20+dfsg-2_amd64.deb
 1dec25cb11d02ba0610e30ba092a0d27 5756 science optional 
bedops_2.4.20+dfsg-2_amd64.buildinfo
 b55dabfc829553bdef06cbf4fcf9cf96 12524842 science optional 
bedops_2.4.20+dfsg-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYlJS7AAoJEHjcaNsybYQ4M8AP/AsVsM+AVZjYN8tMlLDpMaZ9
l2IdqyxntYxWc50B7dlCBvZ39vDEnW/Y7P+pFAtA7qVTGNkUEUEJnGqHUpihx7vV

Bug#831956: marked as done (yocto-reader: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: binary build with no binary artifacts found; cannot distribute)

[Debian Bug Tracking System]

Your message dated Fri, 03 Feb 2017 15:02:36 +
with message-id 
and subject line Bug#854029: Removed package(s) from unstable
has caused the Debian Bug report #831956,
regarding yocto-reader: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: 
error: binary build with no binary artifacts found; cannot distribute
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
831956: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831956
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yocto-reader
Version: 0.9.4+nmu1
Severity: important
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160720 qa-ftbfs qa-indep
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.  This rebuild was done by building only the architecture-independent
packages.  At the same time, a normal build succeeded, which points the
problem specifically to build-indep/binary-indep targets.


The specific error below usually happens there is a binary-indep target in
debian/rules which is either empty or does not do anything useful.

If all the arch-independent packages are dummy transitional packages released
with jessie, the easy fix is to drop them now. If not, debian/rules should be
modified so that the binary-indep target generates the architecture independent
packages (and only those).

After checking that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B" work
properly, this package will be suitable to be uploaded in source-only form if
you wish.

I file this bug as severity: important, but Santiago Vila, who led this
effort (kudos to him), got approval from the release team to consider those
bugs RC for stretch. The severity will be increased to 'serious' shortly.
See #830997 for details.

Relevant part (hopefully):
> make[1]: Entering directory '/<>/yocto-reader-0.9.4+nmu1'
> 1997 blocks
> mkdir -p 
> /<>/yocto-reader-0.9.4+nmu1/debian/yocto-reader/usr/share/yocto-reader
> cp -r \
>   feedread.html permalinks.html reader themes \
>   
> /<>/yocto-reader-0.9.4+nmu1/debian/yocto-reader/usr/share/yocto-reader
> (cd 
> /<>/yocto-reader-0.9.4+nmu1/debian/yocto-reader/usr/share/yocto-reader;
>  /bin/ln -s feedread.html index.html)
> mkdir -p 
> /<>/yocto-reader-0.9.4+nmu1/debian/yocto-reader/etc/yocto-reader
> mv 
> /<>/yocto-reader-0.9.4+nmu1/debian/yocto-reader/usr/share/yocto-reader/reader/mockapi.js
>  \
>   
> /<>/yocto-reader-0.9.4+nmu1/debian/yocto-reader/etc/yocto-reader
> ln -s /etc/yocto-reader/mockapi.js \
>   
> /<>/yocto-reader-0.9.4+nmu1/debian/yocto-reader/usr/share/yocto-reader/reader/mockapi.js
> (VERSION=`dpkg-parsechangelog -S version`; /bin/cp 
> yocto-reader-$VERSION.tar.gz 
> /<>/yocto-reader-0.9.4+nmu1/debian/yocto-reader/usr/share/yocto-reader;
>  cd 
> /<>/yocto-reader-0.9.4+nmu1/debian/yocto-reader/usr/share/yocto-reader;
>  /bin/ln -s yocto-reader-$VERSION.tar.gz yocto-reader.tar.gz)
> make[1]: Leaving directory '/<>/yocto-reader-0.9.4+nmu1'
>  dpkg-genchanges --build=all >../yocto-reader_0.9.4+nmu1_all.changes
> dpkg-genchanges: error: binary build with no binary artifacts found; cannot 
> distribute

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/20/yocto-reader_0.9.4+nmu1_unstable_archallonly.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Version: 0.9.4+nmu1+rm

Dear submitter,

as the package yocto-reader has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/854029

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#854059: texlive-base: failure during texlive-lang-japanese jessie->stretch upgrade test

[Andreas Beckmann]

Package: texlive-base
Version: 2016.20161130-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', then the upgrade to 'stretch' fails.

This was observed during an jessie->stretch upgrade of
texlive-lang-japanese, targetting version 2016.20170123-1 in stretch.
I don't know if this is a known issue ... you mentioned some on
debian-release, but this was the only new failure I observed in texlive
packages recently.

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

[...]
  Setting up x11-common (1:7.7+18) ...
  Installing new version of config file /etc/init.d/x11-common ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  Running in chroot, ignoring request.
  invoke-rc.d: policy-rc.d denied execution of restart.
  Processing triggers for tex-common (6.06) ...
  update-language: texlive-base not installed and configured, doing nothing!
  texlive-base is not ready, skipping fmtutil --all call
  Setting up texlive-base (2016.20161130-1) ...
  Installing new version of config file /etc/libpaper.d/texlive-base ...
  Installing new version of config file /etc/texmf/texdoctk/texdocrc.defaults 
...
  /usr/bin/tl-paper: setting paper size for dvips to a4.
  /usr/bin/tl-paper: setting paper size for dvipdfmx to a4.
  /usr/bin/tl-paper: setting paper size for xdvi to a4.
  /usr/bin/tl-paper: setting paper size for pdftex to a4.
  Removing obsolete conffile /etc/texmf/fmt.d/10texlive-base.cnf ...
  Processing triggers for tex-common (6.06) ...
  Running updmap-sys. This may take some time... 
  updmap-sys failed. Output has been stored in
  /tmp/updmap.X6FTDFyz
  Please include this file if you report a bug.
  
  Sometimes, not accepting conffile updates in /etc/texmf/updmap.d
  causes updmap-sys to fail.  Please check for files with extension
  .dpkg-dist or .ucf-dist in this directory
  
  dpkg: error processing package tex-common (--configure):
   subprocess installed post-installation script returned error exit status 1


The updmap logfile contains:

updmap will read the following updmap.cfg files (in precedence order):
  /usr/share/texmf/web2c/updmap.cfg
  /usr/share/texlive/texmf-dist/web2c/updmap.cfg
updmap may write changes to the following updmap.cfg file:
  /etc/texmf/web2c/updmap.cfg
dvips output dir: "/var/lib/texmf/fonts/map/dvips/updmap"
pdftex output dir: "/var/lib/texmf/fonts/map/pdftex/updmap"
dvipdfmx output dir: "/var/lib/texmf/fonts/map/dvipdfmx/updmap"
updmap [ERROR]: The following map file(s) couldn't be found:
updmap [ERROR]: otf-@jaEmbed@.map (in 
/usr/share/texlive/texmf-dist/web2c/updmap.cfg)
updmap [ERROR]: otf-ko-@koEmbed@.map (in 
/usr/share/texlive/texmf-dist/web2c/updmap.cfg)
updmap [ERROR]: otf-sc-@scEmbed@.map (in 
/usr/share/texlive/texmf-dist/web2c/updmap.cfg)
updmap [ERROR]: otf-tc-@tcEmbed@.map (in 
/usr/share/texlive/texmf-dist/web2c/updmap.cfg)
updmap [ERROR]: otf-up-@jaEmbed@.map (in 
/usr/share/texlive/texmf-dist/web2c/updmap.cfg)
updmap [ERROR]: ptex-@jaEmbed@@jaVariant@.map (in 
/usr/share/texlive/texmf-dist/web2c/updmap.cfg)
updmap [ERROR]: uptex-@jaEmbed@@jaVariant@.map (in 
/usr/share/texlive/texmf-dist/web2c/updmap.cfg)
updmap [ERROR]: uptex-ko-@koEmbed@.map (in 
/usr/share/texlive/texmf-dist/web2c/updmap.cfg)
updmap [ERROR]: uptex-sc-@scEmbed@.map (in 
/usr/share/texlive/texmf-dist/web2c/updmap.cfg)
updmap [ERROR]: uptex-tc-@tcEmbed@.map (in 
/usr/share/texlive/texmf-dist/web2c/updmap.cfg)
updmap [ERROR]: Did you run mktexlsr?

You can disable non-existent map entries using the option
  --syncwithtrees.


I have the chroot still available ...


cheers,

Andreas


texlive-lang-japanese_2016.20170123-1.log.gz
Description: application/gzip

Bug#853898: pgplot5: FTBFS after zlib moved zconf.h back to /usr/include

[Carlo Segre]

Thanks

On Fri, 3 Feb 2017, Andreas Beckmann wrote:


Followup-For: Bug #853898
Control: tag -1 patch pending

Hi,

I just uploaded the NMU to DELEAYED/2, will ask for an unblock once this
is in unstable.


Andreas



--
Carlo U. Segre -- Duchossois Leadership Professor of Physics
Interim Chair, Department of Chemistry
Director, Center for Synchrotron Radiation Research and Instrumentation
Illinois Institute of Technology
Voice: 312.567.3498Fax: 312.567.3494
se...@iit.edu   http://phys.iit.edu/~segre   se...@debian.org

Bug#854042: db insert crashes

[Carsten Leonhardt]

Control: reassign -1 bacula-director-mysql

Hi,

> since some days I get this and all job fails:
>
> [quote]
> 03-Feb 12:05 merkur.jff-webhosting.net-dir JobId 0: Fatal error:
> sql_create.c:86 Create DB Job record INSERT INTO Job
> (Job,Name,Type,Level,JobStatus,SchedTime,JobTDate,ClientId,Comment) VALUES
> ('merkur-data.2017-02-03_12.05.01_04','merkur-data','B','I','C','2017-02-03
> 12:05:01',1486119901,2,'') failed. ERR=Incorrect datetime value: '-00-00
> 00:00:00' for column 'StartTime' at row 1
> [/quote]
>
> I you need more infos pleas ask.

while you didn't say so in your bug report, I suppose you are using a
MySQL-Database.

Your problem is discussed here:

https://sourceforge.net/p/bacula/mailman/bacula-users/thread/30db3ed3-64e9-53f6-8b65-8147a9575776%40caerllewys.net/#msg35406296

So, did you upgrade your MySQL-Server just before the errors started
occuring? If yes, from which version to which? Or did you maybe purge
your MySQL-Server and then reinstalled a newer version or something like
that?

 - Carsten

Processed: Re: Bug#854042: db insert crashes

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 bacula-director-mysql
Bug #854042 [bacula] db insert crashes
Bug reassigned from package 'bacula' to 'bacula-director-mysql'.
No longer marked as found in versions bacula/7.4.4+dfsg-5.
Ignoring request to alter fixed versions of bug #854042 to the same values 
previously set

-- 
854042: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854042
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: pgplot5: FTBFS after zlib moved zconf.h back to /usr/include

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch pending
Bug #853898 [pgplot5] pgplot5: FTBFS after zlib moved zconf.h back to 
/usr/include
Added tag(s) pending and patch.

-- 
853898: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#853898: pgplot5: FTBFS after zlib moved zconf.h back to /usr/include

[Andreas Beckmann]

Followup-For: Bug #853898
Control: tag -1 patch pending

Hi,

I just uploaded the NMU to DELEAYED/2, will ask for an unblock once this
is in unstable.


Andreas
diff -Nru pgplot5-5.2.2/debian/changelog pgplot5-5.2.2/debian/changelog
--- pgplot5-5.2.2/debian/changelog	2016-01-07 13:47:52.0 +0100
+++ pgplot5-5.2.2/debian/changelog	2017-02-03 15:07:35.0 +0100
@@ -1,3 +1,12 @@
+pgplot5 (5.2.2-19.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Search zconf.h in non-multiarch and multiarch locations. (Closes: #853898)
+  * Drop obsolete override for lintian false-positive.
+  * Drop superfluous prerm and postinst script.
+
+ -- Andreas Beckmann   Fri, 03 Feb 2017 15:07:35 +0100
+
 pgplot5 (5.2.2-19.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru pgplot5-5.2.2/debian/dirs pgplot5-5.2.2/debian/dirs
--- pgplot5-5.2.2/debian/dirs	2007-04-21 20:24:55.0 +0200
+++ pgplot5-5.2.2/debian/dirs	2017-02-01 21:43:12.0 +0100
@@ -3,5 +3,3 @@
 usr/bin
 usr/include
 usr/share/doc/pgplot5
-usr/share/lintian/overrides/
-
diff -Nru pgplot5-5.2.2/debian/overrides pgplot5-5.2.2/debian/overrides
--- pgplot5-5.2.2/debian/overrides	2007-04-21 20:20:49.0 +0200
+++ pgplot5-5.2.2/debian/overrides	1970-01-01 01:00:00.0 +0100
@@ -1,4 +0,0 @@
-# The name PGPLOT in the debian/copyright file causes lintian to assume that
-# this package has a GPL license.
-pgplot5 binary: copyright-should-refer-to-common-license-file-for-gpl
-
diff -Nru pgplot5-5.2.2/debian/patches/linker-specific-changes pgplot5-5.2.2/debian/patches/linker-specific-changes
--- pgplot5-5.2.2/debian/patches/linker-specific-changes	2015-09-10 18:36:43.0 +0200
+++ pgplot5-5.2.2/debian/patches/linker-specific-changes	2017-02-01 21:31:05.0 +0100
@@ -75,7 +75,7 @@
  grtv00.o : $(DRVDIR)/imdef.h
  pgxwin.o : $(DRVDIR)/pgxwin.h
 -pndriv.o : ./png.h ./pngconf.h ./zlib.h ./zconf.h
-+pndriv.o : /usr/include/png.h /usr/include/pngconf.h /usr/include/zlib.h /usr/include/$(DEB_HOST_MULTIARCH)/zconf.h
++pndriv.o : /usr/include/png.h /usr/include/pngconf.h /usr/include/zlib.h $(or $(wildcard /usr/include/zconf.h),/usr/include/$(DEB_HOST_MULTIARCH)/zconf.h)
  
  x2driv.o figdisp_comm.o: $(DRVDIR)/commands.h
  
diff -Nru pgplot5-5.2.2/debian/postinst pgplot5-5.2.2/debian/postinst
--- pgplot5-5.2.2/debian/postinst	2006-07-15 20:18:19.0 +0200
+++ pgplot5-5.2.2/debian/postinst	1970-01-01 01:00:00.0 +0100
@@ -1,18 +0,0 @@
-#!/bin/sh
-set -e
-
-#DEBHELPER#
-
-# Automatically added by dh_installdocs
-if [ "$1" = "configure" ]; then
-#if [ -d /usr/doc -a ! -e /usr/doc/pgplot5 -a -d /usr/share/doc/pgplot5 ]; then
-#ln -sf ../share/doc/pgplot5 /usr/doc/pgplot5
-#	fi
-ldconfig	
-fi
-# End automatically added section
-# Automatically added by dh_installmenu
-#if test -x /usr/bin/update-menus ; then update-menus ; fi
-# End automatically added section
-
-
diff -Nru pgplot5-5.2.2/debian/prerm pgplot5-5.2.2/debian/prerm
--- pgplot5-5.2.2/debian/prerm	2006-07-15 20:18:19.0 +0200
+++ pgplot5-5.2.2/debian/prerm	1970-01-01 01:00:00.0 +0100
@@ -1,10 +0,0 @@
-#!/bin/sh
-set -e
-
-#DEBHELPER#
-
-# Automatically added by dh_installdocs
-if [ \( "$1" = "upgrade" -o "$1" = "remove" \) -a -L /usr/doc/pgplot5 ]; then
-rm -f /usr/doc/pgplot5
-fi
-# End automatically added section
diff -Nru pgplot5-5.2.2/debian/rules pgplot5-5.2.2/debian/rules
--- pgplot5-5.2.2/debian/rules	2011-11-19 07:30:49.0 +0100
+++ pgplot5-5.2.2/debian/rules	2017-02-01 21:43:27.0 +0100
@@ -89,7 +89,7 @@
 install-stamp: build-stamp $(64-BIT_CLEAN_STAMP)
 	dh_testdir	
 	dh_testroot
-	dh_clean -k
+	dh_prep
 	dh_installdirs
 	$(INSTALL_DATA) $(bdir)/libpgplot.a  $(packagedir)/usr/lib/
 	$(INSTALL_DATA) $(bdir)/libcpgplot.a  $(packagedir)/usr/lib/
@@ -112,8 +112,6 @@
 	$(INSTALL_DATA) $(bdir)/grexec.f $(packagedir)/usr/lib/$(npackage)
 	$(INSTALL_DATA) $(bdir)/rgb.txt $(packagedir)/usr/lib/$(npackage)
 	$(INSTALL_DATA) $(bdir)/grpckg1.inc $(packagedir)/usr/lib/$(npackage)
-# Install the overrides file for lintian
-	cp -a debian/overrides $(packagedir)/usr/share/lintian/overrides/pgplot5
 
 	#dh_movefiles
 	touch install-stamp

Bug#854058: elserv: non-functional with emacs24 & emacs25

[Sean Whitton]

Package: elserv
Version: 0.4.0+0.20011203cvs-17.2
Severity: grave
Justification: renders package unusable

Dear maintainer,

This package doesn't work with Emacs 24 or Emacs 25, the versions
currently included in Debian.

Steps to reproduce (extracted from [1]):

emacs24 -q or emacs25 -q
M-: (require 'elserv) RET
M-x elserv-start
open a web browser and browse to http://localhost:8000

Expected result:

See a web page.

Actual result:

Nothing is listening on that port.

[1] http://web.archive.org/web/20111206151155/http://www.gohome.org/elserv

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

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

Versions of packages elserv depends on:
ii  emacs  46.1
ii  emacs24 [emacsen]  24.5+1-7.1+b1
ii  emacs25 [emacsen]  25.1+1-3+b1
ii  flim   1:1.14.9+0.20120428-17
ii  ruby   1:2.3.3

elserv recommends no packages.

Versions of packages elserv suggests:
pn  emacs-wiki  
pn  mhc 

-- no debconf information

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#851671: Alternate fix

[Eneko Lacunza]

Hi dears,

I changed columns character set instead:
from
", session_id VARCHAR(255) NOT NULL"
to
", session_id VARCHAR(255) CHARACTER SET latin1 NOT NULL"

I think this should be more reliable.

Cheers

--
Zuzendari Teknikoa / Director Técnico
Binovo IT Human Project, S.L.
Telf. 943493611
  943324914
Astigarraga bidea 2, planta 6 dcha., ofi. 3-2; 20180 Oiartzun (Gipuzkoa)
www.binovo.es

Bug#852991: marked as done (gnocchi: FTBFS (failing tests))

[Debian Bug Tracking System]

Your message dated Fri, 03 Feb 2017 13:48:42 +
with message-id 
and subject line Bug#852991: fixed in gnocchi 3.0.4-1
has caused the Debian Bug report #852991,
regarding gnocchi: FTBFS (failing tests)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
852991: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852991
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gnocchi
Version: 3.0.0-2
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh build-indep --buildsystem=python_distutils --with python2,sphinxdoc
   dh_testdir -i -O--buildsystem=python_distutils
   dh_update_autotools_config -i -O--buildsystem=python_distutils
   dh_auto_configure -i -O--buildsystem=python_distutils
   dh_auto_build -i -O--buildsystem=python_distutils
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
python setup.py build --force
running build
running build_py

[... snipped ...]

 (datetime.datetime(2014, 1, 1, 
12, 0, tzinfo=),
  300,
  69),
 (datetime.datetime(2014, 1, 1, 
12, 10, tzinfo=),
  300,
  42)],
 : []}
actual= defaultdict(, {: [], : []})


==
FAIL: gnocchi.tests.test_storage.TestStorageDriver.test_updated_measures
gnocchi.tests.test_storage.TestStorageDriver.test_updated_measures
--
_StringException: Empty attachments:
  stderr
  stdout

Traceback (most recent call last):
  File "gnocchi/tests/base.py", line 55, in skip_if_not_implemented
return func(*args, **kwargs)
  File "gnocchi/tests/test_storage.py", line 325, in test_updated_measures
], self.storage.get_measures(self.metric))
  File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 350, in 
assertEqual
self.assertThat(observed, matcher, message)
  File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 435, in 
assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: !=:
reference = [(datetime.datetime(2014, 1, 1, 0, 0, tzinfo=), 
86400.0, 55.5),
 (datetime.datetime(2014, 1, 1, 12, 0, tzinfo=), 3600.0, 55.5),
 (datetime.datetime(2014, 1, 1, 12, 0, tzinfo=), 300.0, 69),
 (datetime.datetime(2014, 1, 1, 12, 5, tzinfo=), 300.0, 42.0)]
actual= []


--
Ran 304 tests in 55.760s

FAILED (failures=44, skipped=24)
debian/rules:44: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


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

I've put several build logs here:

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

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.

Note: My build history is like this:

[...]
Status: successful  gnocchi_3.0.0-2_amd64-20170122T094410Z
Status: failed  gnocchi_3.0.0-2_amd64-20170126T170124Z
[...]

where every previous build was ok and now it always fail. Maybe some
build-dependency entered testing between 2017-01-22 and 2017-01-26
which is related to this failure.

Thanks.
--- End Message ---
--- Begin Message ---
Source: gnocchi
Source-Version: 3.0.4-1

We believe that the bug you reported is fixed in the latest version of
gnocchi, which is due to be installed in the Debian 

Bug#854048: sssd: Socket activation of SSSD doesn't work and leads to chaos

[Tomas Forsman]

Package: sssd
Version: 1.15.0-2
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

Updated to sssd 1.15.0-2 from sid into stretch, which is heading for stretch

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

Tried rebooting.

   * What was the outcome of this action?

Errors about lots of unrelated services. Slow boot. Slow logging in.
Trouble rebooting again.

   * What outcome did you expect instead?

Working system.


I tried installing sssd 1.15.0-2 in Debian Stretch (packages from sid),
which uses socket activation. 1.14.2 without socket activation works
fine, but with socket activation - systemd is not happy at all about
lots of services. Starting up a basic image can take 5 minutes. Logging
in with root on console on a local-only machine can take a few minutes.
Examples:
Feb  3 09:16:29 test-vm systemd[1]: Failed to subscribe to NameOwnerChanged 
signal for 'org.freedesktop.Accounts': Connection timed out
Feb  3 09:16:29 test-vm systemd[1]: Failed to register name: Connection timed 
out
Feb  3 09:16:29 test-vm systemd[1]: Failed to set up API bus: Connection timed 
out
Feb  3 09:16:30 test-vm systemd[1]: Failed to register Manager vtable: File 
exists
...
Feb  3 09:21:30 test-vm dbus[659]: [system] Failed to activate service 
'org.freedesktop.ColorManager': timed out
Feb  3 09:21:30 test-vm dbus[659]: [system] Failed to activate service 
'org.freedesktop.systemd1': timed out
Feb  3 09:21:30 test-vm systemd-logind[1040]: Failed to enable subscription: 
Failed to activate service 'org.freedesktop.systemd1': timed out
Feb  3 09:21:30 test-vm systemd-logind[1040]: Failed to fully start up daemon: 
Connection timed out
Feb  3 09:21:30 test-vm systemd[1]: Failed to start Login Service.

This with both trivial config from
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/about-sssd.conf.html
and also an ldaps+autofs based one.


fidencio@redhat verified the problem both under Debian Stretch and some version 
of Fedora.

(Re)moving /etc/systemd/system/sssd.service.wants/sssd-*.socket makes the 
problems go away.
Replacing all of /lib/systemd/system/sssd* (type=notify) with the ones from 
1.14.2 (type=forking) also makes the problems go away. 

Upstreams bug: https://fedorahosted.org/sssd/ticket/3298

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

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

Versions of packages sssd depends on:
ii  python-sss   1.15.0-2
ii  sssd-ad  1.15.0-2
ii  sssd-common  1.15.0-2
ii  sssd-ipa 1.15.0-2
ii  sssd-krb51.15.0-2
ii  sssd-ldap1.15.0-2
ii  sssd-proxy   1.15.0-2

sssd recommends no packages.

sssd suggests no packages.

-- no debconf information

Bug#851707: [pkg-gnupg-maint] Bug#851707: pinentry-gtk-2 frequently fails to grab the keyboard under awesome

[Vincent Bernat]

 ❦  3 février 2017 12:14 +0100, Werner Koch  :

>> I am fixing with this patch. Only lightly tested.
>
> FWIW, I forgot to push a fix I had in my local repo.  Just did this, put
> also not tested.  This is basically the same as yours but w/o any
> delay.

I think your patch is about #850708. In #851707, I don't get the
"already grabbed" error, I get:

** (pinentry-gtk-2:21583): CRITICAL **: could not grab keyboard: not viewable 
(3)
** (pinentry-gtk-2:21583): WARNING **: it took 4097 tries to grab the keyboard
-- 
Keep it right when you make it faster.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature

Bug#853931: marked as done (FTBFS: dh_install: debian/suricata-hyperscan.install returned exit code 127)

[Debian Bug Tracking System]

Your message dated Fri, 3 Feb 2017 13:29:29 +0100
with message-id 

Bug#853931: Processed: Problem is also in the version in stretch

[Arturo Borrero Gonzalez]

Control: notfound -1 3.2-2

On 3 February 2017 at 13:14, Adrian Bunk  wrote:
>>
>> Do you mean that the same source package FTBFS using debian stretch only?
>
> The "build dependencies are not strict enough" problem is also in 3.2-2.
>
> stretch might happen to have recent enough versions, but this doesn't
> change the fact that the build dependencies are not strict enough.
>

I just tested the arm64 stretch build, with no issues. This bug
doesn't affect stretch.
I think we are not in position of doing a upload targeting stretch a this point.

Closing this bug now.

Please, feel free to reopen if you would like to further discuss this.

best regards.

Processed: Re: Processed: Problem is also in the version in stretch

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 3.2-2
Bug #853931 [src:suricata] FTBFS: dh_install: debian/suricata-hyperscan.install 
returned exit code 127
No longer marked as found in versions suricata/3.2-2.

-- 
853931: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853931
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#853931: Processed: Problem is also in the version in stretch

[Adrian Bunk]

On Fri, Feb 03, 2017 at 12:58:21PM +0100, Arturo Borrero Gonzalez wrote:
> On 2 February 2017 at 19:54, Debian Bug Tracking System
>  wrote:
> > Processing commands for cont...@bugs.debian.org:
> >
> >> found 853931 3.2-2
> 
> Hi Adrian,
> 
> could you please elaborate a bit more?
> 
> suricata version 3.2-2 was uploaded source-only, and it seems it was
> build just fine by all the buildds in all arches:
> https://buildd.debian.org/status/package.php?p=suricata=sid
> 
> Do you mean that the same source package FTBFS using debian stretch only?

The "build dependencies are not strict enough" problem is also in 3.2-2.

stretch might happen to have recent enough versions, but this doesn't 
change the fact that the build dependencies are not strict enough.

> best regards.

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#854033: marked as done (libflickcurl-dev: depends on libraptor1-dev but needs libraptor2)

[Debian Bug Tracking System]

Your message dated Fri, 03 Feb 2017 12:03:32 +
with message-id 
and subject line Bug#854033: fixed in flickcurl 1.26-2
has caused the Debian Bug report #854033,
regarding libflickcurl-dev: depends on libraptor1-dev but needs libraptor2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
854033: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854033
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libflickcurl-dev
Version: 1.26-1.1
Severity: serious
Justification: Policy §8.4
Tags: patch
Control: block 850840 by -1

Raptor 1.x has not had an upstream release in 6 years and is superseded by
Raptor 2.x. flickcurl is one of two packages for which the migration to
Raptor 2.x was not complete, which is blocking Raptor 1.x from being
removed from the next stable release (see #850840).

Emilio Pozuelo Monfort has indicated that non-intrusive changes to fix
this would be given a freeze exception. I believe the necessary change
in this case is trivial: replace libraptor1-dev in the -dev package's
Depends by libraptor2-dev.

This dependency mistake also means that installing libflickcurl-dev is not
sufficient to link a trivial program to libflickcurl with pkg-config,
which is why I'm filing this as serious:

(sid-amd64)~/tmp% cat > noop.c
int main(void) {return 0;}
(sid-amd64)~/tmp% gcc noop.c `pkg-config --cflags --libs flickcurl`
Package raptor2 was not found in the pkg-config search path.
Perhaps you should add the directory containing `raptor2.pc'
to the PKG_CONFIG_PATH environment variable
Package 'raptor2', required by 'flickcurl', not found

I don't know how to smoke-test this package, so I would appreciate an
upload by a maintainer. However, I'd be happy to arrange the request
for a freeze exception if that would help.

Regards,
S
diffstat for flickcurl-1.26 flickcurl-1.26

 changelog |8 
 control   |2 +-
 2 files changed, 9 insertions(+), 1 deletion(-)

diff -Nru flickcurl-1.26/debian/changelog flickcurl-1.26/debian/changelog
--- flickcurl-1.26/debian/changelog	2017-01-10 14:08:00.0 +
+++ flickcurl-1.26/debian/changelog	2017-02-03 09:56:16.0 +
@@ -1,3 +1,11 @@
+flickcurl (1.26-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * libflickcurl-dev: depend on libraptor2-dev, not obsolete
+libraptor1-dev (Closes: #nn)
+
+ -- Simon McVittie   Fri, 03 Feb 2017 09:56:16 +
+
 flickcurl (1.26-1) unstable; urgency=medium
 
   * New upstream release (Closes: #850725)
diff -Nru flickcurl-1.26/debian/control flickcurl-1.26/debian/control
--- flickcurl-1.26/debian/control	2017-01-10 14:08:00.0 +
+++ flickcurl-1.26/debian/control	2017-02-03 09:56:16.0 +
@@ -12,7 +12,7 @@
 Package: libflickcurl-dev
 Section: libdevel
 Architecture: any
-Depends: libflickcurl0 (= ${binary:Version}), libxml2-dev, libraptor1-dev, ${misc:Depends}
+Depends: libflickcurl0 (= ${binary:Version}), libxml2-dev, libraptor2-dev, ${misc:Depends}
 Description: C library for accessing the Flickr API - development files
  Flickcurl is a C library for the Flickr API, handling creating the
  requests, signing, token management, calling the API, marshalling
--- End Message ---
--- Begin Message ---
Source: flickcurl
Source-Version: 1.26-2

We believe that the bug you reported is fixed in the latest version of
flickcurl, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 854...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Kumar Appaiah  (supplier of updated flickcurl package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 03 Feb 2017 16:42:40 +0530
Source: flickcurl
Binary: libflickcurl-dev libflickcurl0 libflickcurl0-dbg flickcurl-utils 
flickcurl-doc
Architecture: source all amd64
Version: 1.26-2
Distribution: unstable
Urgency: medium
Maintainer: Kumar Appaiah 
Changed-By: Kumar Appaiah 
Description:
 flickcurl-doc - utilities to call the Flickr API from command line - 
documentatio
 flickcurl-utils - 

Bug#853931: Processed: Problem is also in the version in stretch

[Arturo Borrero Gonzalez]

On 2 February 2017 at 19:54, Debian Bug Tracking System
 wrote:
> Processing commands for cont...@bugs.debian.org:
>
>> found 853931 3.2-2

Hi Adrian,

could you please elaborate a bit more?

suricata version 3.2-2 was uploaded source-only, and it seems it was
build just fine by all the buildds in all arches:
https://buildd.debian.org/status/package.php?p=suricata=sid

Do you mean that the same source package FTBFS using debian stretch only?

best regards.

Bug#853997: CVE-2017-5849

[Guido Günther]

On Thu, Feb 02, 2017 at 11:03:59PM +0100, Moritz Muehlenhoff wrote:
> Source: netpbm-free
> Severity: grave
> Tags: security
> 
> Please see http://www.openwall.com/lists/oss-security/2017/02/02/2

I can't reproduce with the provided crasher and to

http://bugzilla.maptools.org/show_bug.cgi?id=2654#c8

we're not affected so I think this can be closed but it would be awesome
for the maintainer to confirm.
Cheers
 -- Guido

Processed: 853119 affects sphinx

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 853119 src:sphinx
Bug #853119 [texlive-luatex] texlive-luatex: basic lualatex document does not 
compile anymore without additionnal dependencies
Added indication that 853119 affects src:sphinx
> kthxbye
Stopping processing here.

Please contact me if you need assistance.
-- 
853119: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853119
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#851667: #851667 "fix" breaks openjdk 8 on Jessie

[Christian Reitz]

Same here. 

Was fine 2 days ago (while I initially installed openjdk-8-jre-headless
including ca-certficates-java) and is now broken after update yesterday.

Bug#854033: libflickcurl-dev: depends on libraptor1-dev but needs libraptor2

[Kumar Appaiah]

On Fri, Feb 03, 2017 at 10:20:50AM +, Simon McVittie wrote:
> Package: libflickcurl-dev
> Version: 1.26-1.1
> Severity: serious
> Justification: Policy §8.4
> Tags: patch
> Control: block 850840 by -1
> 
> Raptor 1.x has not had an upstream release in 6 years and is superseded by
> Raptor 2.x. flickcurl is one of two packages for which the migration to
> Raptor 2.x was not complete, which is blocking Raptor 1.x from being
> removed from the next stable release (see #850840).
> 
> Emilio Pozuelo Monfort has indicated that non-intrusive changes to fix
> this would be given a freeze exception. I believe the necessary change
> in this case is trivial: replace libraptor1-dev in the -dev package's
> Depends by libraptor2-dev.

This is correct. I will fix this and upload it. Sorry for the
carelessness on my part, and thanks for noticing it.

> This dependency mistake also means that installing libflickcurl-dev is not
> sufficient to link a trivial program to libflickcurl with pkg-config,
> which is why I'm filing this as serious:
> 
> (sid-amd64)~/tmp% cat > noop.c
> int main(void) {return 0;}
> (sid-amd64)~/tmp% gcc noop.c `pkg-config --cflags --libs flickcurl`
> Package raptor2 was not found in the pkg-config search path.
> Perhaps you should add the directory containing `raptor2.pc'
> to the PKG_CONFIG_PATH environment variable
> Package 'raptor2', required by 'flickcurl', not found
> 
> I don't know how to smoke-test this package, so I would appreciate an
> upload by a maintainer. However, I'd be happy to arrange the request
> for a freeze exception if that would help.

I'll handle this shortly.

Kumar
-- 
Kumar Appaiah

Processed: Debian bugs: #854042

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 854042 db insert crashes
Bug #854042 [bacula] db insert cashes
Changed Bug title to 'db insert crashes' from 'db insert cashes'.
> --
Stopping processing here.

Please contact me if you need assistance.
-- 
854042: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854042
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#854020: Wine does not longer work with OSS

[Simon McVittie]

Control: severity 854020 important

On Fri, 03 Feb 2017 at 08:09:33 +0100, Klaus Ethgen wrote:
> OSS is the only sound system working. (Currently oss4 4.2-build2010-5)

It seems you have chosen to use an out-of-tree audio driver that is
not part of the Linux kernel. I'm pretty sure this does not make
wine unusable in general, so it is at most 'important' severity
(and I'm being generous there).

Linux's platform-native API for audio is ALSA, so I would recommend
using ALSA and the in-tree drivers, together with a user-space audio
mixer such as PulseAudio or dmix. If ALSA does not work for you, please
open a bug in an appropriate package (probably not wine, unless the
issue is Wine-specific and general audio playback using ALSA works
as expected).

The oss4 package has unfixed release-critical bugs that make it very
likely to be excluded from the next stable release of Debian; OSS4
support was removed because the alternative would have been to
exclude wine and wine-development from the next stable release as
well, which I hope you would agree does not provide a solution for
your use-case either.

If you must use OSS, using it via its libasound compatibility layer would
not put key packages like wine in danger of being removed when oss4 has
release-critical bugs. Unfortunately, that compatibility layer does
not seem to be very well-integrated in the Debian packaging (#703843,
#770491, #668812, #614765, which are all bugs in the oss4 source package).

If you are using oss4 successfully, your help with the maintenance of
the oss4 source package would probably be appreciated.

Regards,
S

Processed: Re: Bug#854020: Wine does not longer work with OSS

[Debian Bug Tracking System]

Processing control commands:

> severity 854020 important
Bug #854020 [wine64-development] Wine does not longer work with OSS
Severity set to 'important' from 'grave'

-- 
854020: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854020
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#853940: systemd: RestrictAddressFamilies causes services to fail to start on powerpc

[Phil Armstrong]

On 02/02/17 22:37, Phil Armstrong wrote:

On 02/02/17 21:50, Michael Biebl wrote:


Are you absolutely sure? We had another bug report who said that
downgrading systemd+udev to 232-1 did fix the problem on ppc(64).


This is a ppc32 system, so maybe that makes the difference? I’ll test 
it again over the weekend.


I must have made an error before: After carefully binary chopping the 
systemd package versions from snapshot.debian.org, I can report that the 
last version to work correctly is systemd 232-10. 232-11 fails.


Looking at the changelog & the service files, this is kind of 
unsurprising: the service files for 232-10 don’t contain any 
RestrictAddressFamilies entries on my system, whereas the ones for 
232-11 do & the changelog for 232-11 contains this entry:


 * Fix RestrictAddressFamilies=
Backport upstream fix for setting up seccomp filters to fix
RestrictAddressFamilies= on non-amd64 architectures. Drop the hack from
debian/rules to remove this property from unit files.
See #843160

So either the upstream fix doesn’t work on powerpc32 or the backport is 
broken somehow. I appreciate that ppc32 is a minority platform at this 
point.


cheers, Phil

Bug#851707: [pkg-gnupg-maint] Bug#851707: pinentry-gtk-2 frequently fails to grab the keyboard under awesome

[Werner Koch]

On Thu,  2 Feb 2017 19:29, ber...@debian.org said:

> I am fixing with this patch. Only lightly tested.

FWIW, I forgot to push a fix I had in my local repo.  Just did this, put
also not tested.  This is basically the same as yours but w/o any delay.

Shalom-Salam,

   Werner


commit b0e0bdeac5d40ca645afc9017778b39a26303523
Author: Werner Koch 
Date:   Wed Jan 11 18:40:17 2017 +0100

gtk2: Fix a problem with fvwm

* gtk+-2/pinentry-gtk-2.c (grab_pointer): Take care of
GDK_GRAB_ALREADY_GRABBED.
--

Debian-bug-id: 850708
Co-authored-by: Vincent Lefevre 
Signed-off-by: Werner Koch 

Modified   gtk+-2/pinentry-gtk-2.c
diff --git a/gtk+-2/pinentry-gtk-2.c b/gtk+-2/pinentry-gtk-2.c
index 473c4aa..e37601f 100644
--- a/gtk+-2/pinentry-gtk-2.c
+++ b/gtk+-2/pinentry-gtk-2.c
@@ -203,7 +203,12 @@ grab_pointer (GtkWidget *win, GdkEvent *event, gpointer 
data)
   (void)data;
 
   /* Change the cursor for the duration of the grab to indicate that
- something is going on.  */
+   * something is going on.  The fvwm window manager grabs the pointer
+   * for a short time and thus we may end up with the already grabbed
+   * error code.  Actually this error code should be used to detect a
+   * malicious grabbing application but with fvwm this renders
+   * Pinentry only unusable.  Thus we try again several times also for
+   * that error code.  See Debian bug 850708 for details.  */
   /* XXX: It would be nice to have a key cursor, unfortunately there
  is none readily available.  */
   cursor = gdk_cursor_new_for_display (gtk_widget_get_display (win),
@@ -215,7 +220,8 @@ grab_pointer (GtkWidget *win, GdkEvent *event, gpointer 
data)
 NULL /* confine to */,
 cursor,
 gdk_event_get_time (event));
-  while (tries++ < max_tries && err == GDK_GRAB_NOT_VIEWABLE);
+  while (tries++ < max_tries && (err == GDK_GRAB_NOT_VIEWABLE
+ || err == GDK_GRAB_ALREADY_GRABBED));
 
   if (err)
 {


-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.


pgpkegKbC5D6l.pgp
Description: PGP signature

Bug#854042: db insert cashes

[Jörg Frings-Fürst]

Package: bacula
Version: 7.4.4+dfsg-5
Severity: grave

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello,

since some days I get this and all job fails:

[quote]
03-Feb 12:05 merkur.jff-webhosting.net-dir JobId 0: Fatal error:
sql_create.c:86 Create DB Job record INSERT INTO Job
(Job,Name,Type,Level,JobStatus,SchedTime,JobTDate,ClientId,Comment) VALUES
('merkur-data.2017-02-03_12.05.01_04','merkur-data','B','I','C','2017-02-03
12:05:01',1486119901,2,'') failed. ERR=Incorrect datetime value: '-00-00
00:00:00' for column 'StartTime' at row 1
[/quote]

I you need more infos pleas ask.

CU
Jörg





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

Kernel: Linux 4.9.0-1-amd64 (SMP w/6 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)

Versions of packages bacula depends on:
ii  bacula-client  7.4.4+dfsg-5
ii  bacula-server  7.4.4+dfsg-5

bacula recommends no packages.

bacula suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAliUZV8ACgkQCfifPIyh
0l2uoQ/+N/sQq0kclUEO2CU0NZPLZ63343riTPvc8ugEYZjuXpk7fwAu2nOlGHLI
USOZqnzV1kStAcMJxRGjKrBc+B1y23eQqXXWbqczKRDjMnyIASgsyR50M1boslfe
jD9nysJe+C9FTHWX674KGbPbj6U4OKLI5CclHN11m0i1mPES8jipJbXrjecsK07p
pwMPI92EeedW6RXuO85IqSr+YNjc9ucg6BMYh358Sn8Qqyc64fUQNwCtuu6a8Qjx
R6f+OiRmGDbk1AOGZ2oAV9KYyg91YO3GgM3g7MJY6fJK7sZFJqCDNh83FOsMpRMe
uE82CFi6QMB9yI7wc9MXLY2G5Sr/lNieJmCd69HxT06P0Y2I0Q5T880ZbSfba3Sw
5O4ZqYNoPIAzwb8c9hVk6x+/1ipil3lKWHTw6+ZAgyD6Uv8V0ctA76qUV5svr+Ut
3rUwvG2G8IULqlm6jRFYchJPWka7f1wNOvtEIkmzHxZkkh5OKUmpmQZcPXRfcSwk
qX2XKEjvvNQM+ln9zBkykUYQUzq7aQc0JZb8krrOtfoPF+y0s7RyfbfYdbTZ+Ii3
cV5PawwuBxWFmNKdsT5z7hVdwIy1eUUHhG7d8AykXuPlvfA3jowyk4PwAXUgLguF
kDkVLot80vuIRhbnjYzLd0iK4iMFth+M1cFLy6rbVomtiTrcLnI=
=3xTE
-END PGP SIGNATURE-

Bug#852250: [lua-socket] luasocket was not compiled with UNIX sockets support

[Michael Meskes]

> Here is an updated version of the patch, targeting upstream.
> 
> Can you try the attached patch with both lua-socket versions?
> - 3.0~rc1+git+321c0c9-2
> - 3.0~rc1+git+ac3201d-3

Both seem to work, i.e. I can re-start and login to the server both
times. Great work!

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

Bug#851667: #851667 "fix" breaks openjdk 8 on Jessie

[Corentin FOUCAULT]

We have the problem too.
We would appreciate a fix.

Bug#831245: marked as done (gts: FTBFS: Tests failures)

[Debian Bug Tracking System]

Your message dated Fri, 03 Feb 2017 10:33:40 +
with message-id 
and subject line Bug#831245: fixed in gts 0.7.6+darcs121130-4
has caused the Debian Bug report #831245,
regarding gts: FTBFS: Tests failures
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
831245: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831245
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gts
Version: 0.7.6+darcs121130-1.2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160714 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> Makefile:693: recipe for target 'test-suite.log' failed
> make[6]: Leaving directory '/«BUILDDIR»/gts-0.7.6+darcs121130/test/boolean'
> Makefile:799: recipe for target 'check-TESTS' failed
> make[5]: Leaving directory '/«BUILDDIR»/gts-0.7.6+darcs121130/test/boolean'
> make[4]: *** [check-am] Error 2
> Makefile:872: recipe for target 'check-am' failed
> make[4]: Leaving directory '/«BUILDDIR»/gts-0.7.6+darcs121130/test/boolean'
> make[3]: *** [check-recursive] Error 1
> Makefile:372: recipe for target 'check-recursive' failed
> make[3]: Leaving directory '/«BUILDDIR»/gts-0.7.6+darcs121130/test'
> make[2]: *** [check-recursive] Error 1
> Makefile:475: recipe for target 'check-recursive' failed
> make[2]: Leaving directory '/«BUILDDIR»/gts-0.7.6+darcs121130'
> dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
> make[1]: *** [override_dh_auto_test] Error 2
> debian/rules:18: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/14/gts_0.7.6+darcs121130-1.2_unstable_gcc5.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: gts
Source-Version: 0.7.6+darcs121130-4

We believe that the bug you reported is fixed in the latest version of
gts, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 831...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated gts package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 03 Feb 2017 11:04:42 +0100
Source: gts
Binary: libgts-0.7-5 libgts-dev libgts-dbg libgts-bin
Architecture: source amd64
Version: 0.7.6+darcs121130-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Andreas Tille 
Description:
 libgts-0.7-5 - library to deal with 3D computational surface meshes
 libgts-bin - utility binaries for libgts
 libgts-dbg - debugging symbols for libgts
 libgts-dev - development files for libgts
Closes: 831245
Changes:
 gts (0.7.6+darcs121130-4) unstable; urgency=medium
 .
   * Team upload
   * Remove further tests failing for i386 and x32
 Closes: #831245 (for i386 and x32)
Checksums-Sha1:
 e2137248ac56951c9b7b76cdd7bb483c0aada38c 2170 gts_0.7.6+darcs121130-4.dsc
 abff82278f9c783383d6951a790d9ca5306cc6ad 13837 
gts_0.7.6+darcs121130-4.debian.tar.bz2
 158a94684a9e10eadaa19b3895cbdf53c982974e 6452 
gts_0.7.6+darcs121130-4_amd64.buildinfo
 bb7e65e0bda428aa3034a003d881b73cd30161fe 157550 
libgts-0.7-5_0.7.6+darcs121130-4_amd64.deb
 f9742134014858624227fefbb4b06a65864cdc4f 105148 
libgts-bin-dbgsym_0.7.6+darcs121130-4_amd64.deb
 41b4c34d3211db573a61811f46689fb73024c956 50750 
libgts-bin_0.7.6+darcs121130-4_amd64.deb
 e1b6c4be5d72893b2b81865da8d741af4108329f 531986 
libgts-dbg_0.7.6+darcs121130-4_amd64.deb
 786cdfaa6bf12a9771e519676ac3b6f6357e6685 178424 
libgts-dev_0.7.6+darcs121130-4_amd64.deb
Checksums-Sha256:
 3d7dbf72a2194891a485d03f8a002e8d149dc59a915a7bbf36b42c53408ef733 2170 

Bug#850840: raptor: Please don't release this package with Stretch: Abandoned and unused

[Simon McVittie]

On Tue, 31 Jan 2017 at 18:27:46 +0100, Emilio Pozuelo Monfort wrote:
> soprano build-deps on libraptor1-dev but is actually using and linking against
> raptor2, so the build-dep can probably be changed to libraptor2-dev safely.

I have opened an 'important' bug with the obvious 1-character patch.
It builds successfully, although I don't know how to smoke-test the
resulting binaries. The bug should shortly appear as a blocker for this one.

> flickcurl seems to be using raptor2 as well (build-deps on libraptor2-dev,
> libflickcurl0 depends on libraptor2-0), but libflickcurl-dev still depends on
> libraptor1-dev, probably a mistake from the raptor1 -> raptor2 port. I assume
> that dependency can be safely changed to libraptor2-dev.

I have opened a 'serious' bug with the obvious 1-character patch
(severity justified by the dependencies being insufficient to link
a trivial executable to the library using pkg-config, which I have
verified is fixed by my change; probably also insufficient to link against
it statically by using flickcurl-config, but I didn't test that). The
bug should shortly appear as a blocker for this one.

If those patches are uploaded soon and the maintainer doesn't have any
particular objection, I am inclined to ask for src:raptor to be removed
from unstable rather than just testing, so we don't have to care about
it again in 2 years.

S

Bug#854033: libflickcurl-dev: depends on libraptor1-dev but needs libraptor2

[Simon McVittie]

Package: libflickcurl-dev
Version: 1.26-1.1
Severity: serious
Justification: Policy §8.4
Tags: patch
Control: block 850840 by -1

Raptor 1.x has not had an upstream release in 6 years and is superseded by
Raptor 2.x. flickcurl is one of two packages for which the migration to
Raptor 2.x was not complete, which is blocking Raptor 1.x from being
removed from the next stable release (see #850840).

Emilio Pozuelo Monfort has indicated that non-intrusive changes to fix
this would be given a freeze exception. I believe the necessary change
in this case is trivial: replace libraptor1-dev in the -dev package's
Depends by libraptor2-dev.

This dependency mistake also means that installing libflickcurl-dev is not
sufficient to link a trivial program to libflickcurl with pkg-config,
which is why I'm filing this as serious:

(sid-amd64)~/tmp% cat > noop.c
int main(void) {return 0;}
(sid-amd64)~/tmp% gcc noop.c `pkg-config --cflags --libs flickcurl`
Package raptor2 was not found in the pkg-config search path.
Perhaps you should add the directory containing `raptor2.pc'
to the PKG_CONFIG_PATH environment variable
Package 'raptor2', required by 'flickcurl', not found

I don't know how to smoke-test this package, so I would appreciate an
upload by a maintainer. However, I'd be happy to arrange the request
for a freeze exception if that would help.

Regards,
S
diffstat for flickcurl-1.26 flickcurl-1.26

 changelog |8 
 control   |2 +-
 2 files changed, 9 insertions(+), 1 deletion(-)

diff -Nru flickcurl-1.26/debian/changelog flickcurl-1.26/debian/changelog
--- flickcurl-1.26/debian/changelog	2017-01-10 14:08:00.0 +
+++ flickcurl-1.26/debian/changelog	2017-02-03 09:56:16.0 +
@@ -1,3 +1,11 @@
+flickcurl (1.26-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * libflickcurl-dev: depend on libraptor2-dev, not obsolete
+libraptor1-dev (Closes: #nn)
+
+ -- Simon McVittie   Fri, 03 Feb 2017 09:56:16 +
+
 flickcurl (1.26-1) unstable; urgency=medium
 
   * New upstream release (Closes: #850725)
diff -Nru flickcurl-1.26/debian/control flickcurl-1.26/debian/control
--- flickcurl-1.26/debian/control	2017-01-10 14:08:00.0 +
+++ flickcurl-1.26/debian/control	2017-02-03 09:56:16.0 +
@@ -12,7 +12,7 @@
 Package: libflickcurl-dev
 Section: libdevel
 Architecture: any
-Depends: libflickcurl0 (= ${binary:Version}), libxml2-dev, libraptor1-dev, ${misc:Depends}
+Depends: libflickcurl0 (= ${binary:Version}), libxml2-dev, libraptor2-dev, ${misc:Depends}
 Description: C library for accessing the Flickr API - development files
  Flickcurl is a C library for the Flickr API, handling creating the
  requests, signing, token management, calling the API, marshalling

Processed: libflickcurl-dev: depends on libraptor1-dev but needs libraptor2

[Debian Bug Tracking System]

Processing control commands:

> block 850840 by -1
Bug #850840 [src:raptor] raptor: Please don't release this package with 
Stretch: Abandoned and unused
850840 was not blocked by any bugs.
850840 was not blocking any bugs.
Added blocking bug(s) of 850840: 854033

-- 
850840: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850840
854033: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854033
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: soprano: build-depends on libraptor1-dev but uses libraptor2

[Debian Bug Tracking System]

Processing control commands:

> block 850840 by -1
Bug #850840 [src:raptor] raptor: Please don't release this package with 
Stretch: Abandoned and unused
850840 was blocked by: 854033
850840 was not blocking any bugs.
Added blocking bug(s) of 850840: 854034

-- 
850840: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850840
854034: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854034
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: found 852513 in 2.02~beta3-3

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # happened to be triggered by an upgrade, but not a new issue
> found 852513 2.02~beta3-3
Bug #852513 [grub-efi-amd64] updated renders system unbootable
Marked as found in versions grub2/2.02~beta3-3.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
852513: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852513
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#853970: Is there a workaround ?

[Norbert Preining]

Install texlive-base from Sid or wait one day, the package should migrate to 
testing soon.

On February 3, 2017 10:44:47 AM GMT+01:00, CHARPENTIER Emmanuel 
 wrote:
>I'm blocked by this bug (in fact, I filed #853937, which was merged
>with 
>#853970, which points to #852611...).
>
>- Re-running the command doesn't work (contrary to what suggested the
>   first post in #852611).
>
>- Re-installing tex-common (ot texlive) doesn't work either.
>
>- The problem is bound to the system-installed 
>/usr/share/texlive/texmf-dist/web2c/updmap.cfg, which I didn't ever 
>touch (of course...).
>
>- It seems that I still can dis-upgrade my system, but the same
>error(s) 
>happen on tex-common and texlive-lang-* packages.
>
>Any workaround would be welcome...
>
>--
>Emmanuel Charpentier

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

Bug#852611: Is there a workaround ?

[CHARPENTIER Emmanuel]

I'm blocked by this bug (in fact, I filed #853937, which was merged with 
#853970, which points to #852611...).

- Re-running the command doesn't work (contrary to what suggested the
   first post in #852611).

- Re-installing tex-common (ot texlive) doesn't work either.

- The problem is bound to the system-installed 
/usr/share/texlive/texmf-dist/web2c/updmap.cfg, which I didn't ever 
touch (of course...).

- It seems that I still can dis-upgrade my system, but the same error(s) 
happen on tex-common and texlive-lang-* packages.

Any workaround would be welcome...

--
Emmanuel Charpentier

Bug#850764: marked as done (zoph: fails to remove: post-removal script returned error exit status 30)

[Debian Bug Tracking System]

Your message dated Fri, 03 Feb 2017 09:34:41 +
with message-id 
and subject line Bug#850764: fixed in zoph 0.9.4-2
has caused the Debian Bug report #850764,
regarding zoph: fails to remove: post-removal script returned error exit status 
30
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
850764: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850764
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: zoph
Version: 0.9.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to remove.

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

  Removing zoph (0.9.4-1) ...
  Conf zoph disabled.
  To activate the new configuration, you need to run:
service apache2 reload
  dpkg: error processing package zoph (--remove):
   subprocess installed post-removal script returned error exit status 30


This looks like a debconf question not being asked in noninteractive mode.


cheers,

Andreas


zoph_0.9.4-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: zoph
Source-Version: 0.9.4-2

We believe that the bug you reported is fixed in the latest version of
zoph, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 850...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
John Lines  (supplier of updated zoph package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 03 Feb 2017 08:59:42 +
Source: zoph
Binary: zoph
Architecture: source all
Version: 0.9.4-2
Distribution: unstable
Urgency: medium
Maintainer: John Lines 
Changed-By: John Lines 
Description:
 zoph   - Web based digital image presentation and management system
Closes: 850739 850764 851939 851972
Changes:
 zoph (0.9.4-2) unstable; urgency=medium
 .
   * Only ask about removal of /var/lib/zoph if it was not empty
 Fix piuparts issue (Closes: #850764)
   * Dutch debconf translation (Closes: #850739)
   * French debconf translation (Closes: #851939)
   * German debconf translation (Closes: #851972)
Checksums-Sha1:
 0434101bef2e83d9643a730773188d51bf91c060 1706 zoph_0.9.4-2.dsc
 ee37eb309ecbce08041067be2eb7345315131d3e 9676 zoph_0.9.4-2.debian.tar.xz
 bcde1c0ac3553e7aa18eccdae3f891aeeaf9017f 9333250 zoph_0.9.4-2_all.deb
 63d5423cecc66047f4ebdd00d7add7fd767edece 4692 zoph_0.9.4-2_amd64.buildinfo
Checksums-Sha256:
 9acc0a91d41fd308d8caa6ab3694ebf3737ba062987c27b3d04db024c870104c 1706 
zoph_0.9.4-2.dsc
 463e139175956e8beac535587fcd24184ac9d2868b1cd3b28ddb32cc3176d3f7 9676 
zoph_0.9.4-2.debian.tar.xz
 7a90e0e0ecd229f6da41999fd06d757ec449ed5d4b4d3329611d2ed964e83dab 9333250 
zoph_0.9.4-2_all.deb
 6d81a8da30dcfb0df7f2b39da5a1992471b54a310b47d44d7157a251ef6458da 4692 
zoph_0.9.4-2_amd64.buildinfo
Files:
 a5e556b0fef117a493e9e30dbdaad13b 1706 web optional zoph_0.9.4-2.dsc
 1e61d053b4743766bdae248c7e8f53c3 9676 web optional zoph_0.9.4-2.debian.tar.xz
 b4eb95fd79e122e68b0ecc57f90c6a6a 9333250 web optional zoph_0.9.4-2_all.deb
 2cb39d8452b02fb85d22861e60702ad0 4692 web optional zoph_0.9.4-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEEqH8J6LTFSJCxem30HxJlOZZGhecFAliUSE0RHGpvaG5AcGFs
YWR5bi5vcmcACgkQHxJlOZZGhedzKBAAmBj3XC2YAjK0FrQ1Yd+DyBq6vK5XkJiA
KFxMuJVnYV05Z3X8geHNBIcWqRUSD3vzeApy76eOnImlqUO0oiKE55SIINgbED5A
ooCD0OIlGHn/7V8Ko0yLOTr2TuYerYHvvVT5wTzjMHZkIa1mlrY9NYJ1OjrxB/KN
82PQxr5G+iFCRMNxMmxnlUVPc5R3/VVmLKNJ5NSCFnEZnl1Sy8Pka1v3SooPahYl
LkHcqUHBRg1KCoG+qo5xbdwH7+fnC8uxbuPjGADA9k6yQ6lfUv1PCN10DtQGakVB
IxT62dFdg5OsguYvAdh0FxJiDzimFm5Zi+BTw5p7o0sDKd9Hn0ujnO3oiBMn+nc9
AHETeXpK/kA3gXqbBRp1Q5MamD7mn66K0OSbuzXUNQeySllWxKFUYTCSaSUWI+Dw
3cgnpqixslRX8BjJmpr09LCGtbWP1EWGLNGCr7DK4SuBOrXLn/VWblTAMSMw64HP
lok12pLn6UTwqkOslT7WZyxJriVKNOaVN20FVOO1WelVqYntb4pvtlrRwuqEwQh9
bE0ONPtS0KYO83JCVMsRJbEYsCHXmSFtDViyCJnn/MtmR6VzzZS37xhbyt9Zg8vJ
2xFTeG5pJb/bx3Ag5aC7BPqgBniI3cWn02eolV0tPQuNC3uZDkkNp6sVh+hy1vVI
b4Yidnvm8UM=
=mTSq
-END PGP SIGNATURE End Message ---

Processed: Help needed

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 848574 help
Bug #848574 [libopenmpi-dev] openmpi: frequent segfault in linker on mips64el
Added tag(s) help.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
848574: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#839444: libgda5: FTBFS randomly (failing tests)

[Santiago Vila]

retitle 839444 libgda5: FTBFS randomly (failing tests)
severity 839444 important
thanks

Building libgda5 100 times as I write this.
Will let you know about the results.

I'm retitling the bug and downgrading to be in line with this:

https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=sanv...@debian.org;tag=ftbfs-randomly

but as far as I remember, this one was one of the most failing
packages in the list, so I would really expect the flaky tests to be
disabled for the release.

BTW: If you are going to FOSDEM, I'd like to share my ideas about what
we could do with the above list of random bugs with some Release Manager.

Thanks.

Processed: Re: Bug#839444: libgda5: FTBFS randomly (failing tests)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 839444 libgda5: FTBFS randomly (failing tests)
Bug #839444 [src:libgda5] libgda5: FTBFS sometimes (check_data_proxy fails)
Changed Bug title to 'libgda5: FTBFS randomly (failing tests)' from 'libgda5: 
FTBFS sometimes (check_data_proxy fails)'.
> severity 839444 important
Bug #839444 [src:libgda5] libgda5: FTBFS randomly (failing tests)
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
839444: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839444
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#853082: dfvfs

[Sébastien Delafond]

Hello,

I think this should be tracked as an upstream wishlist bug in dfvfs, so
it supports construct >= 2.8.8. Do you want to file that upstream ?

As for the freeze, I definitely agree python-construct 2.8.8 shouldn't
enter stretch.

Cheers,

--Seb

Bug#851667: #851667 "fix" breaks openjdk 8 on Jessie

[Boris De Vloed]

Installing openjdk-8-jre-headless via jessie-backports on a vanilla Debian 
Jessie is impossible now.


The following packages have unmet dependencies:
 openjdk-8-jre-headless : Depends: ca-certificates-java but it is not 
going to be installed
E: Unable to correct problems, you have held broken packages.

Bug#851667: shifted bug in openjdk-8 8u121-b13-1

[Mark Evenson]

On 2/3/17 08:52, Jesse Lopez wrote:
> This update has completely broken the installation of openjdk-8-j* on
> Jessie via backports.
> 
> The bug report needs to be reopened.
> 

For exact reproduction please see [an example of a Dockerfile][1] that
is broken by this issue.

[1]: https://github.com/easye/openjdk8/blob/master/Dockerfile

-- 
"No, this is not a disentanglement, but a progressive /knotting-into/."

Processed: found 853887 in 2.1.5-1, severity of 853887 is serious, tagging 853887

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 853887 2.1.5-1
Bug #853887 [ruby-uuidtools] ruby-signet: conflicts with ruby-uuidtools over 
securerandom.rb
Marked as found in versions ruby-uuidtools/2.1.5-1.
> severity 853887 serious
Bug #853887 [ruby-uuidtools] ruby-signet: conflicts with ruby-uuidtools over 
securerandom.rb
Severity set to 'serious' from 'important'
> tags 853887 + sid
Bug #853887 [ruby-uuidtools] ruby-signet: conflicts with ruby-uuidtools over 
securerandom.rb
Added tag(s) sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
853887: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853887
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems