Bug#415396: [debhelper-devel] Bug#415396: "dh_install --list-missing" should ignore manpages and other installed files

[Niels Thykier]

Michael Stapelberg:
> On Mon, Apr 3, 2017 at 1:07 PM, Niels Thykier  wrote:
> 
>> [...]
> 
> 
> Thanks a lot!
> 
> In turn, I created a branch in the freeradius packaging:
> https://anonscm.debian.org/cgit/pkg-freeradius/freeradius.git/log/?h=dh_missing
> 

Thanks for trying it out. :)

> Maybe I did the wrong changes (?), but when building, I get an error:
> 
> [...]
> 
> Can you reproduce the issue?
> 
> 
> 
> [...]

I think it is a bug in the freeradius changes.  In this commit:

https://anonscm.debian.org/cgit/pkg-freeradius/freeradius.git/commit/?h=dh_missing=58e693ff7dd6603598cb132d44c9e9a547f099ed

The dh_install call is replaced by dh_missing, but AFAICT that
dh_install is inside an override_dh_install, so dh_install is never called.

 * Does it work if you add a dh_install in the bottom of the dh_install
   override target?

Thanks,
~Niels

Bug#859758: pulseaudio: Occasional audio stutter

[Vladimir K]

> This looks like a kernel problem. There is a related redhat bug log[1]
> and a kernel one[2], that suggests disabling the wireless interface
> might avoid the problem. Could you try that?
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1262957
> [2] https://bugzilla.kernel.org/show_bug.cgi?id=108461


I have no rtl8821ae module loaded, no Realtek devices in the system even.
Yet again, sound is glitching only with pulseaudio installed and running.

Bug#631991: libmaven-ant-tasks-java is missing all its dependencies.

[Emmanuel Bourg]

On 04/05/2017 05:00 PM, Adrian Bunk wrote:

> Can a user use the generated jar after
>   apt-get install libmaven-ant-tasks-java
> when installing nothing else?
> 
> Does e.g. libthrift-java in experimental work when libclassworlds-java 
> is not installed?

I think so considering the output of the following command:

$ jar -tf /usr/share/java/maven-ant-tasks.jar | grep classworld

META-INF/maven/classworlds/
META-INF/maven/classworlds/classworlds/
META-INF/maven/classworlds/classworlds/pom.properties
META-INF/maven/classworlds/classworlds/pom.xml
org/codehaus/classworlds/
org/codehaus/classworlds/BytesURLConnection.class
org/codehaus/classworlds/BytesURLStreamHandler.class
org/codehaus/classworlds/ClassRealm.class
org/codehaus/classworlds/ClassWorld.class
org/codehaus/classworlds/ClassWorldException.class
org/codehaus/classworlds/ConfigurationException.class
org/codehaus/classworlds/Configurator$1.class
org/codehaus/classworlds/Configurator$2.class
org/codehaus/classworlds/Configurator.class
org/codehaus/classworlds/DefaultClassRealm.class
org/codehaus/classworlds/DuplicateRealmException.class
org/codehaus/classworlds/EmbeddedLauncher.class
org/codehaus/classworlds/Entry.class
org/codehaus/classworlds/Launcher.class
org/codehaus/classworlds/NoSuchRealmException.class
org/codehaus/classworlds/RealmClassLoader.class
org/codehaus/classworlds/RealmDelegatingClassLoader.class
org/codehaus/classworlds/UberJarRealmClassLoader.class
org/codehaus/classworlds/UrlUtils.class
org/codehaus/classworlds/uberjar/
org/codehaus/classworlds/uberjar/boot/
org/codehaus/classworlds/uberjar/boot/Bootstrapper.class
org/codehaus/classworlds/uberjar/boot/InitialClassLoader.class
org/codehaus/classworlds/uberjar/protocol/
org/codehaus/classworlds/uberjar/protocol/jar/
org/codehaus/classworlds/uberjar/protocol/jar/Handler.class
org/codehaus/classworlds/uberjar/protocol/jar/JarUrlConnection.class

Emmanuel Bourg

Bug#857852: dpkg-maintscript-helper: symlink_to_dir in maintscript file should act on specified package name

[Guillem Jover]

On Fri, 2017-03-17 at 16:31:27 +0100, Markus Koschany wrote:
> Am 15.03.2017 um 22:05 schrieb Andreas Beckmann:
> > The "package" argument is not about the package that makes the changes,
> > but about the package owning the stuff being acted upon. Usually both
> > are the same and the "package" argument can be omitted.
> > I think the "package" argument is not used for symlink_to_dir, but
> > needed for dir_to_symlink ("Is all the stuff found in dir owned by
> > $package?"). Or for rm_conffile/mv_conffile cases where the conffile was
> > previously owned by a *different* package.
> 
> I would expect that this kind of information should be part of 
> dpkg-maintscript-helper's
> man page. At least I would like a clarification about the "I think the 
> "package" argument
> is not used for symlink_to_dir" part.

The man page already mentions that the package argument is always
used, and if it is empty it will get inferred from the environment set
up by dpkg itself. The only thing that might be missing (or at least
might need to be made more explicit) is that the package is the one
owning the file, but from the context and from the prior-version
descrption it seems rather obvious to me. But I can add the "owns the
involved pathnames" or similar to the package argument description.

> It should be more obvious why the package argument is
> needed at all when you have to create one $PACKAGE.maintscript file per 
> package anyway.

This is rather confused, and has nothing to do with how
dpkg-maintscript-helper operates, but rather how debhelper uses its
files and how it might or might not add the package arguments on its
own.

> Please also clarify that [package] does not imply that a single maintscript
> file will act on the binary[package].

I'm no sure what you mean here exactly, but this seems to me it's
something for debhelper to document if at all.

> I think an example how to use dpkg-maintscript-helper with debhelper's
> maintscript files would also be appreciated.

This would be a layer violation, I'm not planning on documenting how
upper layers are using dpkg in this way. Please get debhelper to
clarify any of this if it's not yet clear.

Thanks,
Guillem

Bug#858476: RFS: wolfssl/3.10.2+dfsg-1 [RC] -- wolfSSL encryption library

[Adam Borowski]

On Wed, Mar 22, 2017 at 12:15:49PM -0700, Felix Lechner wrote:
> I am looking for a sponsor for my package "wolfssl":
> 
>   * Package name: wolfssl
> Version : 3.10.2+dfsg-1

> It builds those binary packages:
> 
> libwolfssl10 - wolfSSL encryption library
   vs libwolfssl3 in unstable, but as there are no rdepends, no transition
is needed, so that's ok
> libwolfssl-dev - Development files for the wolfSSL encryption library

>   Changes since the last upload:
> 
>   * New upstream release.
>   * New major version is 10
>   * New maintainer email address
>   * Fixes a low level vulnerability for buffer overflow when loading a
> malformed temporary DH file
>   * Fixes a medium level vulnerability for processing of OCSP response
>   * Fixes CVE-2017-6076, a low level vulnerability for a potential cache 
> attack
> on RSA operations (Closes: #856114)

I'm afraid it FTBFSes due to missing symbols on many architectures: out of
those I tried, it succeeds on amd64 and x32, fails on armhf, arm64 and i386.


--- debian/libwolfssl10.symbols (libwolfssl10_3.10.2+dfsg-1_armhf)
+++ dpkg-gensymbolsptZH0b   2017-04-08 02:31:07.803935398 +
@@ -135,7 +135,7 @@
  wc_InitRng_ex@Base 3.10.2
  wc_InitRsaKey@Base 3.10.2
  wc_InitRsaKey_ex@Base 3.10.2
- wc_InitSha224@Base 3.10.2
+#MISSING: 3.10.2+dfsg-1# wc_InitSha224@Base 3.10.2
  wc_InitSha256@Base 3.10.2
  wc_InitSha384@Base 3.10.2
  wc_InitSha512@Base 3.10.2
@@ -209,10 +209,10 @@
  wc_SetSubjectBuffer@Base 3.10.2
  wc_SetSubjectKeyId@Base 3.10.2
  wc_SetSubjectKeyIdFromPublicKey@Base 3.10.2
- wc_Sha224Final@Base 3.10.2
- wc_Sha224GetHash@Base 3.10.2
- wc_Sha224Hash@Base 3.10.2
- wc_Sha224Update@Base 3.10.2
+#MISSING: 3.10.2+dfsg-1# wc_Sha224Final@Base 3.10.2
+#MISSING: 3.10.2+dfsg-1# wc_Sha224GetHash@Base 3.10.2
+#MISSING: 3.10.2+dfsg-1# wc_Sha224Hash@Base 3.10.2
+#MISSING: 3.10.2+dfsg-1# wc_Sha224Update@Base 3.10.2
  wc_Sha256Final@Base 3.10.2
  wc_Sha256GetHash@Base 3.10.2
  wc_Sha256Hash@Base 3.10.2
@@ -749,7 +749,7 @@
  wolfSSL_EVP_rc4@Base 3.10.2
  wolfSSL_EVP_ripemd160@Base 3.10.2
  wolfSSL_EVP_sha1@Base 3.10.2
- wolfSSL_EVP_sha224@Base 3.10.2
+#MISSING: 3.10.2+dfsg-1# wolfSSL_EVP_sha224@Base 3.10.2
  wolfSSL_EVP_sha256@Base 3.10.2
  wolfSSL_EVP_sha384@Base 3.10.2
  wolfSSL_EVP_sha512@Base 3.10.2
@@ -885,9 +885,9 @@
  wolfSSL_SHA1_Final@Base 3.10.2
  wolfSSL_SHA1_Init@Base 3.10.2
  wolfSSL_SHA1_Update@Base 3.10.2
- wolfSSL_SHA224_Final@Base 3.10.2
- wolfSSL_SHA224_Init@Base 3.10.2
- wolfSSL_SHA224_Update@Base 3.10.2
+#MISSING: 3.10.2+dfsg-1# wolfSSL_SHA224_Final@Base 3.10.2
+#MISSING: 3.10.2+dfsg-1# wolfSSL_SHA224_Init@Base 3.10.2
+#MISSING: 3.10.2+dfsg-1# wolfSSL_SHA224_Update@Base 3.10.2
  wolfSSL_SHA256_Final@Base 3.10.2
  wolfSSL_SHA256_Init@Base 3.10.2
  wolfSSL_SHA256_Update@Base 3.10.2

--- debian/libwolfssl10.symbols (libwolfssl10_3.10.2+dfsg-1_arm64)
+++ dpkg-gensymbolsUx3QLk   2017-04-08 02:39:25.711217905 +
@@ -135,7 +135,7 @@
  wc_InitRng_ex@Base 3.10.2
  wc_InitRsaKey@Base 3.10.2
  wc_InitRsaKey_ex@Base 3.10.2
- wc_InitSha224@Base 3.10.2
+#MISSING: 3.10.2+dfsg-1# wc_InitSha224@Base 3.10.2
  wc_InitSha256@Base 3.10.2
  wc_InitSha384@Base 3.10.2
  wc_InitSha512@Base 3.10.2
@@ -209,10 +209,10 @@
  wc_SetSubjectBuffer@Base 3.10.2
  wc_SetSubjectKeyId@Base 3.10.2
  wc_SetSubjectKeyIdFromPublicKey@Base 3.10.2
- wc_Sha224Final@Base 3.10.2
- wc_Sha224GetHash@Base 3.10.2
- wc_Sha224Hash@Base 3.10.2
- wc_Sha224Update@Base 3.10.2
+#MISSING: 3.10.2+dfsg-1# wc_Sha224Final@Base 3.10.2
+#MISSING: 3.10.2+dfsg-1# wc_Sha224GetHash@Base 3.10.2
+#MISSING: 3.10.2+dfsg-1# wc_Sha224Hash@Base 3.10.2
+#MISSING: 3.10.2+dfsg-1# wc_Sha224Update@Base 3.10.2
  wc_Sha256Final@Base 3.10.2
  wc_Sha256GetHash@Base 3.10.2
  wc_Sha256Hash@Base 3.10.2
@@ -749,7 +749,7 @@
  wolfSSL_EVP_rc4@Base 3.10.2
  wolfSSL_EVP_ripemd160@Base 3.10.2
  wolfSSL_EVP_sha1@Base 3.10.2
- wolfSSL_EVP_sha224@Base 3.10.2
+#MISSING: 3.10.2+dfsg-1# wolfSSL_EVP_sha224@Base 3.10.2
  wolfSSL_EVP_sha256@Base 3.10.2
  wolfSSL_EVP_sha384@Base 3.10.2
  wolfSSL_EVP_sha512@Base 3.10.2
@@ -885,9 +885,9 @@
  wolfSSL_SHA1_Final@Base 3.10.2
  wolfSSL_SHA1_Init@Base 3.10.2
  wolfSSL_SHA1_Update@Base 3.10.2
- wolfSSL_SHA224_Final@Base 3.10.2
- wolfSSL_SHA224_Init@Base 3.10.2
- wolfSSL_SHA224_Update@Base 3.10.2
+#MISSING: 3.10.2+dfsg-1# wolfSSL_SHA224_Final@Base 3.10.2
+#MISSING: 3.10.2+dfsg-1# wolfSSL_SHA224_Init@Base 3.10.2
+#MISSING: 3.10.2+dfsg-1# wolfSSL_SHA224_Update@Base 3.10.2
  wolfSSL_SHA256_Final@Base 3.10.2
  wolfSSL_SHA256_Init@Base 3.10.2
  wolfSSL_SHA256_Update@Base 3.10.2

-- 
⢀⣴⠾⠻⢶⣦⠀ Meow!
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ Collisions shmolisions, let's see them find a collision or second
⠈⠳⣄ preimage for double rot13!

Bug#854554: dpkg: trigger problem with cracklib-runtime while upgrading libcrypt-cracklib-perl from jessie to stretch

[Guillem Jover]

Control: reassign -1 apt

[ Please see the bug archive for more context. ]

Hi!

On Wed, 2017-04-05 at 22:01:17 +0200, Andreas Beckmann wrote:
> On 2017-04-02 01:37, Guillem Jover wrote:
> > My expectation is that after the reported state is found on piuparts,
> > running:
> > 
> >   $ dpkg --configure --pending
> > 
> > or even something like:
> > 
> >   $ dpkg --configure cracklib-runtime libcrack2
> > 
> > would let dpkg configure that package correctly w/o complaining about
> > the unsatisfiable dependency. Andreas, is that indeed the case? If it
> > is then this needs to be reassigned to apt.
> 
> OK, let's try that in the chroot after the failure occurred:
> 
> # # just verify that the problem is still there
> # dpkg --configure cracklib-runtime
> dpkg: dependency problems prevent processing triggers for cracklib-runtime:
>  cracklib-runtime depends on libcrack2 (>= 2.9.2-1); however:
>   Package libcrack2:i386 is not configured yet.
> 
> dpkg: error processing package cracklib-runtime (--configure):
>  dependency problems - leaving triggers unprocessed
> Errors were encountered while processing:
>  cracklib-runtime
> 
> # dpkg --configure cracklib-runtime libcrack2
> Setting up libcrack2:i386 (2.9.2-3+b1) ...
> Processing triggers for cracklib-runtime (2.9.2-1) ...
> Processing triggers for libc-bin (2.24-9) ...
> 
> # dpkg --configure --pending
> Setting up perl-modules-5.24 (5.24.1-2) ...
> Setting up libgdbm3:i386 (1.8.3-14) ...
> Setting up libperl5.24:i386 (5.24.1-2) ...
> Setting up bash (4.4-4+b1) ...
> [...]
> 
> 
> So the fault is in apt ... and that's jessie's version of apt that is
> running the upgrade :-(
> 
> If I start the upgrade with upgrading only apt (and its dependencies)
> and thereafter running the dist-upgrade (with squeeze's version of apt),
> I cannot reproduce the bug.

Thanks for verifying! Reassigned now to apt.

Regards,
Guillem

Bug#859861: transcriber: Waveform cursor is invisible (patch included)

[Teddy Hogeborn]

Package: transcriber
Version: 1.5.1.1-10
Severity: important
Tags: patch

Dear Maintainer,

In olden times, lo, many Debian releases ago, when playing audio in
transcriber, a dashed red line was visible in the audio waveform at the
point where the audio was playing or paused.  The line is no longer
visible, which sadly makes the entire program almost completely
unusable.  I have investigated and, without fully understanding the
mechanisms, have written a patch to fix the problem (also attached):

--- transcriber-1.5.1.1/src/wavfm.c.~1~ 2017-04-08 04:07:20.0 +0200
+++ transcriber-1.5.1.1/src/wavfm.c 2017-04-08 04:07:53.350918541 +0200
@@ -508,8 +508,8 @@
 
/* Cursor graphic context */
gcValues.foreground = w->cursorcolor->pixel;
-   gcValues.line_style = LineOnOffDash;
-   gcValues.dashes = 3;
+   gcValues.line_style = LineSolid;
+   gcValues.dashes = 2;
newGC = Tk_GetGC(w->tkwin,
  GCBackground|GCForeground|GCLineStyle|GCDashList|GCGraphicsExposures,
  );

(This makes it a solid red line instead of a dashed red line, but I
think it is not an important difference.)

/Teddy Hogeborn

-- System Information:
Debian Release: 8.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 
'stable')
Architecture: i386 (i686)

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

Versions of packages transcriber depends on:
ii  libc6  2.19-18+deb8u7
ii  libtcl8.6  8.6.2+dfsg-2
ii  libtk8.6   8.6.2-1
ii  libx11-6   2:1.6.2-3
ii  sox14.4.1-5
ii  tcl-snack  2.2.10.20090623-dfsg-4
ii  tcl-tclex  1.2a1-16
ii  tk 8.6.0+8

transcriber recommends no packages.

transcriber suggests no packages.

-- no debconf information

--- transcriber-1.5.1.1/src/wavfm.c.~1~	2017-04-08 04:07:20.0 +0200
+++ transcriber-1.5.1.1/src/wavfm.c	2017-04-08 04:07:53.350918541 +0200
@@ -508,8 +508,8 @@
 
/* Cursor graphic context */
gcValues.foreground = w->cursorcolor->pixel;
-   gcValues.line_style = LineOnOffDash;
-   gcValues.dashes = 3;
+   gcValues.line_style = LineSolid;
+   gcValues.dashes = 2;
newGC = Tk_GetGC(w->tkwin,
  GCBackground|GCForeground|GCLineStyle|GCDashList|GCGraphicsExposures,
  );


signature.asc
Description: PGP signature

Bug#833930: reproduced bug by removing xserver-xorg-video-intel

[Mark Kohler]

I was able to reproduce this bug, that is make it gitk look like the
broken.jpg screenshot, by:

1. Removing xserver-xorg-video-intel
2. Logging out and logging back in again.

At that point, it looked like broken.jpg.

Then I installed xserver-xorg-video-intel, logged out, logged back in
again, and gitk was drawing happy little circles again.

This is on Ubuntu 16.04. The xserver-xorg-video-intel driver is
2:2.99.917+git20160325-1ubuntu1.2.

xserver-xorg-video-all is 1:7.7+13ubuntu3

Bug#858556: Ready for -3 I believe

[Santiago Garcia Mantinan]

Hi!

I have just pushed some changes to Amos fix and other fixes for some "dirty"
test cases I had found.

Please test and report back, tomorrow I'll do some final tests and upload if
nobody sees any problem.

Regards.
-- 
Manty/BestiaTester -> http://manty.net

Bug#859845: yarssr: Segmentation Fault on Quit

[Sebastian Wyngaard]

Hi Joachim,

Thanks for the response.

I'd be happy to create patch at some point. I have no experience with
Debian packaging so I think it will be a good learning exercise. It may
take a while but I'm definitely interested.

I really like yarssr's simple design.

Regards,
Sebastian

On 7 April 2017 at 17:18, Joachim Breitner  wrote:

> Dear Sebastian,
>
> thanks for reporting this bug. I have not used yarssr myself in years,
> and I believe upstream is not active either. If you (or someone else)
> wants to get this bug fixed, a patch would be required.
>
> I’d also be happy to let someone else take over this package.
>
> Greetings,
> Joachim
>
> Am Freitag, den 07.04.2017, 13:18 -0400 schrieb Sebastian Wyngaard:
> > Package: yarssr
> > Version: 0.2.2-9
> > Severity: normal
> >
> > Dear Maintainer,
> >
>
> > * What led up to the situation?
> > I started yarssr from the command-line. Once started, if I quit yarssr
> through
> > the context menu (right click) the application segfaults.
> >
> > I was trying to debug why yarssr loses all my configuration settings and
> feeds
> > after rebooting sometimes and noticed this segfault. I will submit a
> separate
> > bug report for that since I'm not sure if it is related.
> >
> > This is the output when I run "yarssr --debug" and then quit:
> >
> > GdkPixbuf-LOG **: gdk_pixbuf_from_pixdata() called on: at
> > /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> > GdkPixbuf-LOG **:   Encoding raw at /usr/share/yarssr/Yarssr.pm
> > line 37,
> >  line 1.
> > GdkPixbuf-LOG **:   Dimensions: 24 x 24 at
> > /usr/share/yarssr/Yarssr.pm line
> > 37,  line 1.
> > GdkPixbuf-LOG **:   Rowstride: 96, Length: 2328 at
> > /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> > GdkPixbuf-LOG **:   Copy pixels == false at
> > /usr/share/yarssr/Yarssr.pm
> > line 37,  line 1.
> > GdkPixbuf-LOG **: gdk_pixbuf_from_pixdata() called on: at
> > /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> > GdkPixbuf-LOG **:   Encoding raw at /usr/share/yarssr/Yarssr.pm
> > line 37,
> >  line 1.
> > GdkPixbuf-LOG **:   Dimensions: 24 x 24 at
> > /usr/share/yarssr/Yarssr.pm line
> > 37,  line 1.
> > GdkPixbuf-LOG **:   Rowstride: 96, Length: 2328 at
> > /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> > GdkPixbuf-LOG **:   Copy pixels == false at
> > /usr/share/yarssr/Yarssr.pm
> > line 37,  line 1.
> > GdkPixbuf-LOG **: gdk_pixbuf_from_pixdata() called on: at
> > /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> > GdkPixbuf-LOG **:   Encoding raw at /usr/share/yarssr/Yarssr.pm
> > line 37,
> >  line 1.
> > GdkPixbuf-LOG **:   Dimensions: 24 x 24 at
> > /usr/share/yarssr/Yarssr.pm line
> > 37,  line 1.
> > GdkPixbuf-LOG **:   Rowstride: 96, Length: 2328 at
> > /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> > GdkPixbuf-LOG **:   Copy pixels == false at
> > /usr/share/yarssr/Yarssr.pm
> > line 37,  line 1.
> > GdkPixbuf-LOG **: gdk_pixbuf_from_pixdata() called on: at
> > /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> > GdkPixbuf-LOG **:   Encoding raw at /usr/share/yarssr/Yarssr.pm
> > line 37,
> >  line 1.
> > GdkPixbuf-LOG **:   Dimensions: 24 x 24 at
> > /usr/share/yarssr/Yarssr.pm line
> > 37,  line 1.
> > GdkPixbuf-LOG **:   Rowstride: 96, Length: 2328 at
> > /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> > GdkPixbuf-LOG **:   Copy pixels == false at
> > /usr/share/yarssr/Yarssr.pm
> > line 37,  line 1.
> > GdkPixbuf-LOG **: gdk_pixbuf_from_pixdata() called on: at
> > /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> > GdkPixbuf-LOG **:   Encoding raw at /usr/share/yarssr/Yarssr.pm
> > line 37,
> >  line 1.
> > GdkPixbuf-LOG **:   Dimensions: 24 x 24 at
> > /usr/share/yarssr/Yarssr.pm line
> > 37,  line 1.
> > GdkPixbuf-LOG **:   Rowstride: 96, Length: 2328 at
> > /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> > GdkPixbuf-LOG **:   Copy pixels == false at
> > /usr/share/yarssr/Yarssr.pm
> > line 37,  line 1.
> > GdkPixbuf-LOG **: gdk_pixbuf_from_pixdata() called on: at
> > /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> > GdkPixbuf-LOG **:   Encoding raw at /usr/share/yarssr/Yarssr.pm
> > line 37,
> >  line 1.
> > GdkPixbuf-LOG **:   Dimensions: 24 x 24 at
> > /usr/share/yarssr/Yarssr.pm line
> > 37,  line 1.
> > GdkPixbuf-LOG **:   Rowstride: 96, Length: 2328 at
> > /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> > GdkPixbuf-LOG **:   Copy pixels == false at
> > /usr/share/yarssr/Yarssr.pm
> > line 37,  line 1.
> > GdkPixbuf-LOG **: gdk_pixbuf_from_pixdata() called on: at
> > /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> > GdkPixbuf-LOG **:   Encoding raw at /usr/share/yarssr/Yarssr.pm
> > line 37,
> >  line 1.
> > GdkPixbuf-LOG **:   Dimensions: 24 x 24 at
> > /usr/share/yarssr/Yarssr.pm line
> > 37,  line 1.
> > GdkPixbuf-LOG **:   Rowstride: 96, Length: 2328 at
> > /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> > GdkPixbuf-LOG **:   Copy pixels == false at
> > 

Bug#856335: python-pyftpdlib: FTBFS, unittests error: error_temp: 426 Internal error; transfer aborted

[W. Martin Borgert]

Control: forwarded 856335 https://github.com/giampaolo/pyftpdlib/issues/420

I cannot reproduce the test failures, neither on single core nor
quad core amd64.

Bug#859860: diodon: The program will not start and syslog records segfault

[Marc Bonnor]

Package: diodon
Version: 1.3.0-1
Severity: important

Dear Maintainer,

I installed the program.

The program does not start via GUI or command line.

The syslog records this error.

debian kernel: [  224.612026] diodon[17445]: segfault at 41 ip 7f331d497074 
sp 7ffd47bdcbe0 error 6 in libX11.so.6.3.0[7f331d3ff000+13a000]


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

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

Versions of packages diodon depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2+b1
ii  libappindicator3-1   0.4.92-4
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-9
ii  libcairo-gobject21.14.8-1
ii  libcairo21.14.8-1
ii  libdbusmenu-glib412.10.2-2
ii  libdiodon0   1.3.0-1
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libgee-0.8-2 0.18.1-1
ii  libgirepository-1.0-11.50.0-1+b1
ii  libglib2.0-0 2.50.3-2
ii  libgtk-3-0   3.22.11-1
ii  libpango-1.0-0   1.40.4-1
ii  libpangocairo-1.0-0  1.40.4-1
ii  libpeas-1.0-01.20.0-1+b1
ii  libx11-6 2:1.6.4-3
ii  libxtst6 2:1.2.3-1
ii  libzeitgeist-2.0-0   0.9.16-0.2+b1
ii  zeitgeist-core   0.9.16-0.2+b1

diodon recommends no packages.

diodon suggests no packages.

-- no debconf information

Bug#855845: [Pkg-tigervnc-devel] Bug#855845: Bug#855845: Bug#855845: tigervnc-viewer: Option -LowColourLevel doesn't seem functional

[Joachim Falk]

Hi Ola and Celelibi,

Am 01.03.2017 um 17:44 schrieb Ola Lundqvist:
> Hi
> 
> I see. Point taken.
> 
> / Ola
> 
> Sent from a phone
> 
> Den 1 mar 2017 14:27 skrev "Celelibi"  >:
> 
> 2017-02-28 23:07 UTC+01:00, Ola Lundqvist  >:
> > Is it possible to set a lower color level on the server side? Or do you
> > want this on only certain clients?
> > I'm quite sure you can set the color depth on the server side.
this seems to be just bad documentation. Please use

xtigervncviewer -FullColor=0 -LowColorLevel=0 : to get it working.
However, the -LowColorLevel in isolation does indeed have no impact.

> It is probably possible to set the clolor level on the server, but I
> would like to set it myself depending on where I connect
> from.Especially because I'm better than vnc at determining whether the
> connection is slow or fast.

Regards,

Joachim Falk



signature.asc
Description: OpenPGP digital signature

Bug#857343: Pending fixes for bugs in the logback package

[pkg-java-maintainers]

tag 857343 + pending
thanks

Some bugs in the logback package are closed in revision
febe22ba76de74fbf5238b5f245dcb3fcf151d0d in branch '  wheezy' by
Markus Koschany

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/logback.git/commit/?id=febe22b

Commit message:

Import Debian changes 1:1.0.4-1+deb7u1

logback (1:1.0.4-1+deb7u1) wheezy-security; urgency=high

  * Team upload.
  * Fix CVE-2017-5929:
It was discovered that logback, a flexible logging library for Java, 
would
deserialize data from untrusted sockets. This issue has been resolved by
adding a whitelist to use only trusted classes. (Closes: #857343)

logback (1:1.0.4-1) unstable; urgency=low

  * New upstream release.
  * d/control: Update Standards-Version to 3.9.3: no changes needed.
  * d/copyright: Upgrade to copyright-format 1.0.

Bug#855344: thunderbird: retains mails from removed IMAP accounts

[Carsten Schoenert]

Hi,

On Sat, Mar 11, 2017 at 07:07:46PM +0100, John Paul Adrian Glaubitz wrote:
> Hi Adam!
> 
> > I'm afraid that, similar to the current debian-devel thread about leaving
> > old (possibly subsequently purged) mails on .icedove->.thunderbird
> > transition, Icedove/Thunderbird leaves the whole IMAP cache on the disk
> > when you delete an account.
> 
> I suggest reporting this bug upstream as this would probably require some more
> involved changes to Thunderbird itself and I'm not sure whether the 
> maintainers
> of the package in Debian can or want to do that.

it looks like Mozilla is suprising all of us, at least me on this
specific issue. There is obviously no need to open a upstream bug on
this issue, Mozilla has fixed this by adding a option to remove all
relevant files if you want to remove a whole account in your Thunderbird
with the release of version 52.0.

https://www-dev.allizom.org/en-US/thunderbird/52.0/releasenotes/

Note the second NEWS phrase.

So we can close this report once we have a successful build and upload
of the upstream version 52.0.

Regards
Carsten

Bug#859859: ITP: node-acorn-jsx -- JSX parser based on node-acorn

[Bastien ROUCARIES]

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

* Package name: node-acorn-jsx
  Version : 3.0.1
  Upstream Author : Ingvar Stepanyan
* URL : https://github.com/RReverser/acorn-jsx
* License : Expat
  Programming Lang: JavaScript
  Description : JSX parser based on node-acorn

This pure javascript module based on node-acorn parses JSX file.
.
JSX, a JavaScript extension syntax allowing quoting of HTML
and using HTML tag syntax to render subcomponents.
 .
 Node.js is an event-based server-side JavaScript engine.

Bug#859858: ITP: node-retape -- CommonJS test to tape adapter

[Bastien ROUCARIES]

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

* Package name: node-retape
  Version : 0.0.3
  Upstream Author : Irakli Gozalishvili 
(http://jeditoolkit.com)
* URL : https://github.com/Gozala/retape
* License : Expat
  Programming Lang: JavaScript
  Description : CommonJS test to tape adapter

 This module allow to use tape module for running commonJS test.
 .
 You can also mix with this module commonJS testsuite and tape testsuite.
 .
 Node.js is an event-based server-side JavaScript engine.

Bug#859857: ITP: node-static-eval -- evaluate statically-analyzable expressions

[Bastien ROUCARIES]

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

* Package name: node-static-eval
  Version : 1.1.1
  Upstream Author : James Halliday  (http://substack.net)
* URL : https://github.com/substack/static-eval
* License : Expat
  Programming Lang: JavaScript
  Description : evaluate statically-analyzable expressions

 This javascript module decompose expression in abstract tree and try
to evaluate
 the static evaluable expressions.
.
This module could be used in order to simplify expression or partial
compilation of javascript.
 .
 Node.js is an event-based server-side JavaScript engine.

Bug#859845: yarssr: Segmentation Fault on Quit

[Joachim Breitner]

Dear Sebastian,

thanks for reporting this bug. I have not used yarssr myself in years,
and I believe upstream is not active either. If you (or someone else)
wants to get this bug fixed, a patch would be required.

I’d also be happy to let someone else take over this package.

Greetings,
Joachim

Am Freitag, den 07.04.2017, 13:18 -0400 schrieb Sebastian Wyngaard:
> Package: yarssr
> Version: 0.2.2-9
> Severity: normal
> 
> Dear Maintainer,
> 

> * What led up to the situation?
> I started yarssr from the command-line. Once started, if I quit yarssr through
> the context menu (right click) the application segfaults.
> 
> I was trying to debug why yarssr loses all my configuration settings and feeds
> after rebooting sometimes and noticed this segfault. I will submit a separate
> bug report for that since I'm not sure if it is related.
> 
> This is the output when I run "yarssr --debug" and then quit:
> 
> GdkPixbuf-LOG **: gdk_pixbuf_from_pixdata() called on: at
> /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> GdkPixbuf-LOG **:   Encoding raw at /usr/share/yarssr/Yarssr.pm
> line 37,
>  line 1.
> GdkPixbuf-LOG **:   Dimensions: 24 x 24 at
> /usr/share/yarssr/Yarssr.pm line
> 37,  line 1.
> GdkPixbuf-LOG **:   Rowstride: 96, Length: 2328 at
> /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> GdkPixbuf-LOG **:   Copy pixels == false at
> /usr/share/yarssr/Yarssr.pm
> line 37,  line 1.
> GdkPixbuf-LOG **: gdk_pixbuf_from_pixdata() called on: at
> /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> GdkPixbuf-LOG **:   Encoding raw at /usr/share/yarssr/Yarssr.pm
> line 37,
>  line 1.
> GdkPixbuf-LOG **:   Dimensions: 24 x 24 at
> /usr/share/yarssr/Yarssr.pm line
> 37,  line 1.
> GdkPixbuf-LOG **:   Rowstride: 96, Length: 2328 at
> /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> GdkPixbuf-LOG **:   Copy pixels == false at
> /usr/share/yarssr/Yarssr.pm
> line 37,  line 1.
> GdkPixbuf-LOG **: gdk_pixbuf_from_pixdata() called on: at
> /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> GdkPixbuf-LOG **:   Encoding raw at /usr/share/yarssr/Yarssr.pm
> line 37,
>  line 1.
> GdkPixbuf-LOG **:   Dimensions: 24 x 24 at
> /usr/share/yarssr/Yarssr.pm line
> 37,  line 1.
> GdkPixbuf-LOG **:   Rowstride: 96, Length: 2328 at
> /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> GdkPixbuf-LOG **:   Copy pixels == false at
> /usr/share/yarssr/Yarssr.pm
> line 37,  line 1.
> GdkPixbuf-LOG **: gdk_pixbuf_from_pixdata() called on: at
> /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> GdkPixbuf-LOG **:   Encoding raw at /usr/share/yarssr/Yarssr.pm
> line 37,
>  line 1.
> GdkPixbuf-LOG **:   Dimensions: 24 x 24 at
> /usr/share/yarssr/Yarssr.pm line
> 37,  line 1.
> GdkPixbuf-LOG **:   Rowstride: 96, Length: 2328 at
> /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> GdkPixbuf-LOG **:   Copy pixels == false at
> /usr/share/yarssr/Yarssr.pm
> line 37,  line 1.
> GdkPixbuf-LOG **: gdk_pixbuf_from_pixdata() called on: at
> /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> GdkPixbuf-LOG **:   Encoding raw at /usr/share/yarssr/Yarssr.pm
> line 37,
>  line 1.
> GdkPixbuf-LOG **:   Dimensions: 24 x 24 at
> /usr/share/yarssr/Yarssr.pm line
> 37,  line 1.
> GdkPixbuf-LOG **:   Rowstride: 96, Length: 2328 at
> /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> GdkPixbuf-LOG **:   Copy pixels == false at
> /usr/share/yarssr/Yarssr.pm
> line 37,  line 1.
> GdkPixbuf-LOG **: gdk_pixbuf_from_pixdata() called on: at
> /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> GdkPixbuf-LOG **:   Encoding raw at /usr/share/yarssr/Yarssr.pm
> line 37,
>  line 1.
> GdkPixbuf-LOG **:   Dimensions: 24 x 24 at
> /usr/share/yarssr/Yarssr.pm line
> 37,  line 1.
> GdkPixbuf-LOG **:   Rowstride: 96, Length: 2328 at
> /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> GdkPixbuf-LOG **:   Copy pixels == false at
> /usr/share/yarssr/Yarssr.pm
> line 37,  line 1.
> GdkPixbuf-LOG **: gdk_pixbuf_from_pixdata() called on: at
> /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> GdkPixbuf-LOG **:   Encoding raw at /usr/share/yarssr/Yarssr.pm
> line 37,
>  line 1.
> GdkPixbuf-LOG **:   Dimensions: 24 x 24 at
> /usr/share/yarssr/Yarssr.pm line
> 37,  line 1.
> GdkPixbuf-LOG **:   Rowstride: 96, Length: 2328 at
> /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> GdkPixbuf-LOG **:   Copy pixels == false at
> /usr/share/yarssr/Yarssr.pm
> line 37,  line 1.
> GdkPixbuf-LOG **: gdk_pixbuf_from_pixdata() called on: at
> /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> GdkPixbuf-LOG **:   Encoding raw at /usr/share/yarssr/Yarssr.pm
> line 37,
>  line 1.
> GdkPixbuf-LOG **:   Dimensions: 24 x 24 at
> /usr/share/yarssr/Yarssr.pm line
> 37,  line 1.
> GdkPixbuf-LOG **:   Rowstride: 96, Length: 2328 at
> /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> GdkPixbuf-LOG **:   Copy pixels == false at
> /usr/share/yarssr/Yarssr.pm
> line 37,  line 1.
> GdkPixbuf-LOG **: gdk_pixbuf_from_pixdata() 

Bug#857803: [Pkg-shadow-devel] Bug#857803: shadow: Make the sp_lstchg shadow field reproducible.

[Serge E. Hallyn]

Quoting Chris Lamb (la...@debian.org):
> Package: shadow
> Severity: wishlist
> Version: 1:4.4-4
> Tags: patch
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: toolchain
> X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
> 
> Hi,
> 
> Attached is the following:
> 
>   commit 2dd84b0ee31e44dc51cba7b7cdc8657bf9ff0a31
>   Author: Chris Lamb 
>   Date:   Wed Mar 15 11:35:35 2017 +0100
>   
>   Make the sp_lstchg shadow field reproducible.
>   
>   The third field in the /etc/shadow file (sp_lstchg) contains the date of
>   the last password change expressed as the number of days since Jan 1, 
> 1970.
>   As this is a relative time, creating a user today will result in:
>   
>  username:17238:0:9:7:::
>   
>   whilst creating the same user tomorrow will result in:
>   
>  username:17239:0:9:7:::
>   
>   This has an impact for the Reproducible Builds[0] project where we aim 
> to
>   be independent of as many elements the build environment as possible,
>   including the current date.
>   
>   This patch changes the behaviour to use the SOURCE_DATE_EPOCH[1]
>   environment variable (instead of Jan 1, 1970) if available.
>   
>[0] https://reproducible-builds.org/
>[1] https://reproducible-builds.org/specs/source-date-epoch/
>   
>   Signed-off-by: Chris Lamb 
>   
>lib/prototypes.h|  3 ++
>libmisc/Makefile.am |  1 +
>libmisc/gettime.c   | 86 
> +
>src/chpasswd.c  |  2 +-
>src/newusers.c  |  4 +--
>src/passwd.c|  2 +-
>src/useradd.c   |  2 +-
>src/usermod.c   |  4 +--
>8 files changed, 97 insertions(+), 7 deletions(-)
> 
> 
> Regards,

Hi,

looks ok to me, although, would it be better to fall back to time(NULL)
if the env variable is invalid?

Do you want to submit this as a patch to upstream at
github.com/shadow-maint/shadow ?

-serge

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

> >From 2dd84b0ee31e44dc51cba7b7cdc8657bf9ff0a31 Mon Sep 17 00:00:00 2001
> From: Chris Lamb 
> Date: Wed, 15 Mar 2017 11:35:35 +0100
> Subject: [PATCH] Make the sp_lstchg shadow field reproducible.
> 
> The third field in the /etc/shadow file (sp_lstchg) contains the date of
> the last password change expressed as the number of days since Jan 1, 1970.
> As this is a relative time, creating a user today will result in:
> 
>username:17238:0:9:7:::
> 
> whilst creating the same user tomorrow will result in:
> 
>username:17239:0:9:7:::
> 
> This has an impact for the Reproducible Builds[0] project where we aim to
> be independent of as many elements the build environment as possible,
> including the current date.
> 
> This patch changes the behaviour to use the SOURCE_DATE_EPOCH[1]
> environment variable (instead of Jan 1, 1970) if available.
> 
>  [0] https://reproducible-builds.org/
>  [1] https://reproducible-builds.org/specs/source-date-epoch/
> 
> Signed-off-by: Chris Lamb 
> ---
>  lib/prototypes.h|  3 ++
>  libmisc/Makefile.am |  1 +
>  libmisc/gettime.c   | 86 
> +
>  src/chpasswd.c  |  2 +-
>  src/newusers.c  |  4 +--
>  src/passwd.c|  2 +-
>  src/useradd.c   |  2 +-
>  src/usermod.c   |  4 +--
>  8 files changed, 97 insertions(+), 7 deletions(-)
>  create mode 100644 libmisc/gettime.c
> 
> diff --git a/lib/prototypes.h b/lib/prototypes.h
> index 7aaf1a6..4808d5d 100644
> --- a/lib/prototypes.h
> +++ b/lib/prototypes.h
> @@ -179,6 +179,9 @@ extern int getrange (char *range,
>   unsigned long *min, bool *has_min,
>   unsigned long *max, bool *has_max);
>  
> +/* gettime.c */
> +extern time_t gettime ();
> +
>  /* get_uid.c */
>  extern int get_uid (const char *uidstr, uid_t *uid);
>  
> diff --git a/libmisc/Makefile.am b/libmisc/Makefile.am
> index 76f3c05..e691dac 100644
> --- a/libmisc/Makefile.am
> +++ b/libmisc/Makefile.am
> @@ -31,6 +31,7 @@ libmisc_a_SOURCES = \
>   getdate.y \
>   getgr_nam_gid.c \
>   getrange.c \
> + gettime.c \
>   hushed.c \
>   idmapping.h \
>   idmapping.c \
> diff --git a/libmisc/gettime.c b/libmisc/gettime.c
> new file mode 100644
> index 000..b0c539b
> --- /dev/null
> +++ b/libmisc/gettime.c
> @@ -0,0 +1,86 @@
> +/*
> + * Copyright (c) 2017, Chris Lamb
> + * All rights reserved.
> + *
> + * Redistribution and use in source and binary forms, with or without
> + * modification, are permitted provided that the following conditions
> + * are met:
> + * 1. Redistributions of source code must retain the above copyright
> + *notice, this list of conditions and the following disclaimer.
> + * 2. Redistributions in binary form must reproduce the 

Bug#832132: /etc/init.d/radicale start does not work

[Jonas Smedegaard]

Hi Slavko,

Quoting Slavko (2017-04-07 20:18:13)
> On Mon, 1 Aug 2016 21:04:02 +0100 D McA  wrote:
> > I am also affected by this bug. I installed Radicale with apt-get 
> > and did not suppress any package recommendations.

> today i install stretch's radicale in virtualbox:
> 
> dpkg -l radicale
> ii  radicale  1.1.1+20160115-3
> 
> and because i want to play with config i run it from console (not as
> daemon) without any config change yet:
[...]
> And yes, there is missing /var/log/radicale/ directory. I am not sure, 
> if it is original poster problem too, but it seems as some small 
> packaging mistake, because there is a logrotate's config for radicale 
> to work with logs in this directory:

When you sidestep the init script then it is your responsibility to 
ensure that the environment is aligned with however you want to use the 
package.

This bugreport concerns the issue of init script provided as part of the 
package not working correctly - deliberately avoiding the init script is 
not this bug (and is not a bug at all).

Thanks for your input anyway.  Hope you got it working the way you 
wanted.


 - Jonas

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

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


signature.asc
Description: signature

Bug#415396: [debhelper-devel] Bug#415396: "dh_install --list-missing" should ignore manpages and other installed files

[Michael Stapelberg]

On Mon, Apr 3, 2017 at 1:07 PM, Niels Thykier  wrote:

> Niels Thykier:
> > Michael Stapelberg:
> >> On Sun, Mar 26, 2017 at 2:54 PM, Niels Thykier 
> wrote:
> >>
> >> [...]
> >>
> >> Great. Find attached an updated patch including documentation.
> >>
> >
> > Thanks.  I am a bit busy this week, so odds are I will not have time to
> > look at it until the weekend at the earliest.  Please ping me if you
> > have not heard from me on this by Tuesday.
> >
>
> Created a branch for it:
>
> https://anonscm.debian.org/git/debhelper/debhelper.git/
> log/?h=bug-415396-dh_missing


Thanks a lot!

In turn, I created a branch in the freeradius packaging:
https://anonscm.debian.org/cgit/pkg-freeradius/freeradius.git/log/?h=dh_missing

Maybe I did the wrong changes (?), but when building, I get an error:

$ dpkg-buildpackage -b
[…]
dh_missing: etc/freeradius/3.0/mods-available/pam exists in debian/tmp but
is not installed to anywhere
dh_missing: etc/freeradius/3.0/mods-available/sradutmp exists in debian/tmp
but is not installed to anywhere
dh_missing: etc/freeradius/3.0/mods-available/idn exists in debian/tmp but
is not installed to anywhere
dh_missing: etc/freeradius/3.0/mods-available/ntlm_auth exists in
debian/tmp but is not installed to anywhere
The following debhelper tools have reported what they installed
* dh_installman
If the missing files are installed by another tool, please file a bug
against it
For a short-term work-around: Add the files to debian/not-installed
dh_missing: missing files, aborting
debian/rules:41: recipe for target 'override_dh_missing' failed
make[1]: *** [override_dh_missing] Error 255
make[1]: Leaving directory '/home/michael/d/pkg/freeradius'
debian/rules:86: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit
status 2
dpkg-buildpackage -b  60,34s user 7,70s system 165% cpu 41,147 total

Can you reproduce the issue?



>
>
> Review welcome.  Note that the "installed-by" files work differently
> than documented.  I have opted for keeping the behaviour and correcting
> the documentation.
>
> > If you got time to spare and want to keep things moving, I got some
> > things I am considering to change:
> >
> >  * Make log_installed_files use "basename($0)" rather than taking an
> >argument for the "helper name".  The actual file name is an
> >implementation-detail anyway, and tool writers do not benefit from
> >the addition complexity
> >
>
> Done.
>
> >  * Make log_installed_files support being called multiple times from
> >the same helper to make it easier for tool writers.  Most of them
> >probably don't need to accumulate their set of installed/processed
> >files.  dh_install basically only does it because it was implementing
> >the "missing" feature AFAICT.
> >
>
> Done.  This will probably come in handby due to the next item and the
> following call pattern.
>
>  dh_install -ppkg foo bar
>  dh_install --remaining
>
> > If you want to start on dh_installman (or other tools):
> >
> >  * CAVEAT: The tools have to start acting on *all* packages but
> >"do nothing" for "uninteresting packages" like dh_install does.
> >Otherwise, the user will see "missing" entries when doing an
> >dpkg-buildpackage -B build (or -A).
> >
>
>
> Did a prototype for dh_installman, which seems to be working (with the
> above CAVEAT)
>
> NB: Due to how this is implemented, the "install-by" files will get
> duplicates when you do:
>
>   dh_install -a # first copy
>   dh_install -i # second copy
>
> It does not appear to be a problem atm., so I have left it at that.
>
> > The debhelper API here is probably horribly lacking IRT making this
> > easy.  So far, it has only been done in dh_install, but it is a
> > necessity for this feature to work correctly (Especially with
> > --fail-missing).  Bonus points for improving that. :)
> >
>
> Still lacking.
>
> >> Is there any large-scale testing that debhelper has, to confirm that my
> >> change doesn’t break things so far?
> >>
> >
> > No.  But I suppose we could do an upload to experimental and ask if
> > Lucas have time to do a mass-rebuild.
> >
> > ~Niels
> >
>
> I might do the upload "soon" (before the release), but lets keep the
> mass-rebuild for post-freeze to avoid diverting peoples attention.
>
> Thanks,
> ~Niels
>
>
>


-- 
Best regards,
Michael

Bug#800016: lists.debian.org: mungs e-mail contents by added ">" in front of "From"

[Vincent Lefevre]

Hi,

On 2017-03-19 10:23:59 +, Cord Beermann wrote:
> Hallo! Du (Vincent Lefevre) hast geschrieben:
> 
> > The Debian mailing-list software mungs e-mail contents by adding a
> > ">" character in front of "From" at the beginning of a line. This
> > can confuse users since it is similar to the quote prefix. And this
> > is not needed at all (it can be needed by the mbox format, but this
> > format shouldn't be used for mailing-list handling).
> > 
> > An example: https://lists.debian.org/debian-user/2015/08/msg01470.html
> > 
> > This isn't specific to the mail archive since the ">" character
> > was also present in the mail copy from debian-user. But it wasn't
> > present in the mail copy I received as a Bcc user; so, this didn't
> > come from my side.
> 
> Our system uses mbox-files on many stages, for instance when we hand
> mails over to the Mailarchive, or if a mail qualifies for special handling
> inside the mail-distribution. 
> 
> so before a major rewrite (which will most likely never will happen)
> this is a wontfix. 

I think this should be partially reconsidered. The "From" line of
a mbox file as a special format. So, the ">" could be added only
to such lines. This would avoid almost all of the false positives
(and in particular the most annoying ones).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#859793: fluidsynth: Package has infringed GPL

[Javier Serrano Polo]

Regarding SoX and Debian bug #92969, the copyright handling in wav.c is
dubious.[5] Assuming this modification is allowed, wav.c changes the
notice

XAnim Copyright (C) 1990-1997 by Mark Podlipec.
[...]
This software may be freely copied, modified and redistributed
without fee for non-commerical purposes

which is clearly incompatible with the original license, to

Thanks goes to Mark Podlipec's XAnim code.  It gave some real
life understanding of how the ADPCM format is processed.  Actual
code was implemented based off of various sources from the net.

So the code was from Mark Podlipec, but now it is only an inspiration
for Chris Bagwell, yet various sources from the net are needed? Or Mark
Podlipec's code was inspired by those sources from the net? Chris
Bagwell should clarify the origin of the code.

--
[5] 
https://sourceforge.net/p/sox/code/ci/613f50d018d73308428dda8c610066a726e1a95e/


smime.p7s
Description: S/MIME cryptographic signature

Bug#859854: qemu: CVE-2017-7377

[Michael Tokarev]

commit 39ac9c9574ccf0be731be5f1d1dfe0e5f065ca48
Author: Michael Tokarev 
Date:   Mon Apr 3 14:15:41 2017 +0300

9pfs-fix-file-descriptor-leak-CVE-2017-7377.patch

pending d-release review (#859599)
I'll add bug# reference.

/mjt

Bug#859856: 4.9.13-1~bpo8+1 and SuperMicro X10DRT-PT kernel trace

[Rumen Telbizov]

Package: linux-image-4.9.0-0.bpo.2-amd64
Version: 4.9.13-1~bpo8+1
Severity: important

Dear Debian maintainers,

I would like to report a reproducible kernel stack trace that we started to
experience after we upgraded the kernel on some of our hosts running a
specific motherboard/CPU model.

*OS:* Debian 8.7 Jessie (up-to-date)
*Offending kernel:* 4.9.13-1~bpo8+1 (from jessie-backports)
*Motherboard:* X10DRT-PT (SuperMicro)
*CPU:* 2 x E5-2620 v4 @ 2.10GHz
*RAM:* 128GB

The stack trace is:

[  245.006408] INFO: task systemd-udevd:552 blocked for more than 120
seconds.
[  245.006467]   Not tainted 4.9.0-0.bpo.2-amd64 #1
[  245.006501] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[  245.006552] systemd-udevd   D0   552547 0x0004
[  245.006557]  95a5744f7800  95b578530100
95a577ade100
[  245.006561]  95b57f458700 b8bc0d7a3b50 aa1f668d
1257
[  245.006565]  95a577ade100 a9c2476b 95a50001
95a577ade100
[  245.006569] Call Trace:
[  245.006579]  [] ? __schedule+0x23d/0x6d0
[  245.006594]  [] ? uncore_pci_remove+0x160/0x160
[intel_uncore]
[  245.006597]  [] ? schedule+0x32/0x80
[  245.006599]  [] ? schedule_timeout+0x249/0x300
[  245.006602]  [] ? __schedule+0x245/0x6d0
[  245.006609]  [] ? uncore_alloc_box+0x74/0xd0
[intel_uncore]
[  245.006615]  [] ? sched_clock+0x5/0x10
[  245.006622]  [] ? uncore_pci_remove+0x160/0x160
[intel_uncore]
[  245.006633]  [] ? wait_for_completion+0xfa/0x130
[  245.006640]  [] ? wake_up_q+0x60/0x60
[  245.006644]  [] ? cpuhp_issue_call+0x96/0xc0
[  245.006646]  [] ? __cpuhp_setup_state+0xca/0x200
[  245.006656]  [] ? intel_uncore_init+0x1c1/0xeaa
[intel_uncore]
[  245.006665]  [] ? uncore_type_init+0x156/0x156
[intel_uncore]
[  245.006670]  [] ? do_one_initcall+0x4c/0x180
[  245.006676]  [] ? do_init_module+0x5a/0x1f1
[  245.006679]  [] ? load_module+0x23c9/0x28f0
[  245.006682]  [] ? __symbol_put+0x60/0x60
[  245.006687]  [] ? vfs_read+0x114/0x130
[  245.006693]  [] ? security_capable+0x41/0x60
[  245.006696]  [] ? SYSC_finit_module+0x8e/0xe0
[  245.006700]  [] ? system_call_fast_compare_end+0xc/0x9b



The above occurs briefly after boot and leaves systemd-udevd stuck in 'D'
state. It is worth mentioning that we tried running the above kernel on a
bunch of different SuperMicro motherboards (X8/X9 generation) without any
problems.

Let me know if I can provide additional information.

Thank you,
-- 
Rumen Telbizov
Unix Systems Administrator 

Bug#859758: pulseaudio: Occasional audio stutter

[Felipe Sateler]

Control: tags -1 moreinfo

On Thu, Apr 6, 2017 at 11:47 PM, Vladimir K  wrote:
> Package: pulseaudio
> Version: 10.0-1
> Severity: normal
>
> Dear Maintainer, sound is interrupted occasionally when pulseaudio is 
> installed.
> Every 1-10 minutes there is an audible glitch. Playback source does not 
> matter,
> it happens with mpv, firefox, wine and other applications.
>
> The problem does not correlate with CPU usage or anything visibly happening 
> in the
> system. It happens both with and without rtkit installed.
>
> Also I should point out that this bug never ever occurred without pulseaudio,
> so hardware or ALSA issue is highly unlikely.
>
> Output of 'pulseaudio - --log-time=1' at the time of stutter:
>
> (1372.884| 584.857) I: [alsa-sink-92HD93BXX Analog] alsa-sink.c: Scheduling 
> delay of 153.11 ms > 15.01 ms, you might want to investigate this to improve 
> latency...
> (1372.884|   0.000) I: [alsa-sink-92HD93BXX Analog] ratelimit.c: 109 events 
> suppressed
> (1372.884|   0.000) I: [alsa-sink-92HD93BXX Analog] alsa-sink.c: Underrun!
> (1372.884|   0.000) I: [alsa-sink-92HD93BXX Analog] alsa-sink.c: Increasing 
> minimal latency to 1.00 ms
> (1372.884|   0.000) D: [alsa-sink-92HD93BXX Analog] alsa-sink.c: Latency set 
> to 25.01ms
> (1372.884|   0.000) D: [alsa-sink-92HD93BXX Analog] alsa-sink.c: 
> hwbuf_unused=61124
> (1372.884|   0.000) D: [alsa-sink-92HD93BXX Analog] alsa-sink.c: setting 
> avail_min=15723
> (1372.884|   0.000) D: [alsa-sink-92HD93BXX Analog] alsa-sink.c: Latency set 
> to 25.01ms
> (1372.884|   0.000) D: [alsa-sink-92HD93BXX Analog] alsa-sink.c: 
> hwbuf_unused=61124
> (1372.884|   0.000) D: [alsa-sink-92HD93BXX Analog] alsa-sink.c: setting 
> avail_min=15723
> (1372.884|   0.000) D: [alsa-sink-92HD93BXX Analog] protocol-native.c: 
> Implicit underrun of 'AudioStream'
> (1372.885|   0.000) D: [alsa-sink-92HD93BXX Analog] protocol-native.c: 
> Requesting rewind due to end of underrun.
> (1372.885|   0.000) D: [alsa-sink-92HD93BXX Analog] alsa-sink.c: Requested to 
> rewind 15540 bytes.
> (1372.885|   0.000) D: [alsa-sink-92HD93BXX Analog] alsa-sink.c: Limited to 
> 4060 bytes.
> (1372.885|   0.000) D: [alsa-sink-92HD93BXX Analog] alsa-sink.c: before: 1015
> (1372.885|   0.000) D: [alsa-sink-92HD93BXX Analog] alsa-sink.c: after: 1015
> (1372.885|   0.000) D: [alsa-sink-92HD93BXX Analog] alsa-sink.c: Rewound 4060 
> bytes.
> (1372.885|   0.000) D: [alsa-sink-92HD93BXX Analog] sink.c: Processing 
> rewind...
> (1372.885|   0.000) D: [alsa-sink-92HD93BXX Analog] sink.c: latency = 2322
> (1372.885|   0.000) D: [alsa-sink-92HD93BXX Analog] sink-input.c: Have to 
> rewind 4060 bytes on render memblockq.
> (1372.885|   0.000) D: [alsa-sink-92HD93BXX Analog] sink-input.c: Have to 
> rewind 4060 bytes on render memblockq.
> (1372.885|   0.000) D: [alsa-sink-92HD93BXX Analog] source.c: Processing 
> rewind...
>

This looks like a kernel problem. There is a related redhat bug log[1]
and a kernel one[2], that suggests disabling the wireless interface
might avoid the problem. Could you try that?


[1] https://bugzilla.redhat.com/show_bug.cgi?id=1262957
[2] https://bugzilla.kernel.org/show_bug.cgi?id=108461

-- 

Saludos,
Felipe Sateler

Bug#859855: systemd-container - machinectl fails to display list

[Felipe Sateler]

Control: forcemerge 849316 -1

On Fri, Apr 7, 2017 at 4:56 PM, Bastian Blank  wrote:
> Package: systemd-container
> Version: 232-22
> Severity: important
> Forwarded: https://github.com/systemd/systemd/issues/4918
>
> machinectl fails to display a list if one of the machines comes from
> libvirt/qemu.  This problem is fixed upstream.

This was already filed as #849316 , where I posted a backported patch
for testing. Could you test that please?


-- 

Saludos,
Felipe Sateler

Bug#859855: systemd-container - machinectl fails to display list

[Bastian Blank]

Package: systemd-container
Version: 232-22
Severity: important
Forwarded: https://github.com/systemd/systemd/issues/4918

machinectl fails to display a list if one of the machines comes from
libvirt/qemu.  This problem is fixed upstream.

Bastian

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

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

Bug#859854: qemu: CVE-2017-7377

[Salvatore Bonaccorso]

Source: qemu
Version: 1:2.8+dfsg-3
Severity: important
Tags: security patch upstream fixed-upstream

Hi,

the following vulnerability was published for qemu.

CVE-2017-7377[0]:
9pfs: host memory leakage via v9fs_create

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-7377
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7377
[1] https://lists.gnu.org/archive/html/qemu-devel/2017-03/msg05449.html
[2] 
http://git.qemu-project.org/?p=qemu.git;a=commitdiff;h=d63fb193e71644a073b77ff5ac6f1216f2f6cf6e

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#859611: linux-image-4.9.0-0.bpo.2-amd64: ipsec gre tunnel not receiving packets

[Ben Hutchings]

Control: tag -1 moreinfo

On Wed, 2017-04-05 at 18:22 +1000, Russell Stuart wrote:
> Package: src:linux
> Version: 4.9.13-1~bpo8+1
> Severity: normal
> 
> Dear Maintainer,
> 
> We have a IPSec tunnel.  It works under 3.16, and doesn't work under
> 4.9.13.  Under 4.9.13 racoon reports the isakmp setup is successfull.
> Looking at it with tcdump (I've got captures, with xfrm keys) 
> under 4.9.13 I see ESP packets going out, but none coming in.
[...]

Does the affected system have a firewall?  If so, you might need to
load nf_conntrack_proto_gre explicitly now (explained in
).
Although it isn't obvious why only some of the GRE tunnels would be
affected.

Ben.

-- 
Ben Hutchings
Never attribute to conspiracy what can adequately be explained by
stupidity.


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

Bug#859634: nvidia-driver: 5-8 second freeze

[Xavier Ortiz]

Luca,

Thank you for the reply. Really appreciate it.

I will definitely be posting logs there. Will add link information once
posted.

Best,

--Xavier

On Wed, Apr 5, 2017 at 7:07 PM, Luca Boccassi 
wrote:

> On Wed, 2017-04-05 at 08:24 -0400, Xavier Ortiz wrote:
> > Package: nvidia-driver
> > Version: 375.39-1
> > Severity: important
> >
> > Dear Maintainer,
> >
> > *** Reporter, please consider answering these questions, where
> > appropriate ***
> >
> >* What led up to the situation?
> >* What exactly did you do (or not do) that was effective (or
> >  ineffective)?
> >* What was the outcome of this action?
> >* What outcome did you expect instead?
> >
> > *** End of the template - remove these template lines ***
> >
> > was browsing on chrome, whole system froze for a couple of seconds.
> > Spotify in
> > the background continued with audio.
> >
> > This was the journalctl output.
> >
> > Apr 05 08:20:53 DebianDesktop /usr/lib/gdm3/gdm-x-session[1469]: (WW)
> > NVIDIA(0): WAIT (2, 8, 0x8000, 0x4bfc, 0x4c04)
> > Apr 05 08:20:59 DebianDesktop kernel: NVRM: GPU at PCI::01:00:
> > GPU-7005a340-d9d1-0a70-4742-2697dbda6882
> > Apr 05 08:20:59 DebianDesktop kernel: NVRM: Xid (PCI::01:00): 8,
> > Channel
> > 0038
> > Apr 05 08:21:00 DebianDesktop /usr/lib/gdm3/gdm-x-session[1469]: (WW)
> > NVIDIA(0): WAIT (1, 8, 0x8000, 0x4bfc, 0x4c04)
> > Apr 05 08:21:02 DebianDesktop kernel: NVRM: os_schedule: Attempted to
> > yield the
> > CPU while in atomic or interrupt context
> > Apr 05 08:21:04 DebianDesktop /usr/lib/gdm3/gdm-x-session[1469]: (II)
> > SYN_DROPPED event from "Microsoft Microsoft® 2.4GHz Transceiver v9.0"
> > - some
> > input events have been lost.
>
> Hi,
>
> The nvidia kernel module is a binary blob, so there it is most likely
> nothing we can do about it.
>
> It was already reported upstream:
>
> https://devtalk.nvidia.com/default/topic/903841/linux/nvrm-os_schedule-
> attempted-to-yield-the-cpu-while-in-atomic-or-interrupt-context-/
>
> https://devtalk.nvidia.com/default/topic/912392/-solved-xserver-freezes
> -during-gaming-attempted-to-yield-the-cpu-while-in-atomic-or-interrupt-
> con/
>
> So I would recommend reporting this to the upstream developers.
>
> Could you please post your logs on one of those threads?
>
> Kind regards,
> Luca Boccassi

Bug#859704: (no subject)

[Michael Lustfield]

After taking a second look, I'm assuming this report comes from reproducible
builds.

From the log:
  Get:13 http://httpredir.debian.org/debian sid/main amd64 
golang-github-syndtr-goleveldb-dev all 0.0~git20170302.0.3c5717c-2 [3790 B]

This FTBFS occurs because this specific version of the packaging did not play
well with dh-golang. A corrected version of this package has been uploaded and
is now in unstable.

I'm looking into kicking off another rebuild test and will close this if it
succeeds.
-- 
Michael Lustfield

Bug#859793: fluidsynth: Package has infringed GPL

[Javier Serrano Polo]

El dv 07 de 04 de 2017 a les 19:13 +0100, James Cowgill va escriure:
> FYI the license in question is the SoX license which has been in Debian
> and basically all distributions for 20 years (as part of SoX)...

So SoX and derivatives are affected too. The problem was not
detected.[3]

> The SoX project relicensed some time ago to GPL so if you are to believe
> that that was OK, then there are no licensing problems with this file
> (but the copyright header should be updated to reflect that).

Upstream file still has the old copyright.[4] Where is this relicensing
process documented?

--
[3] https://bugs.debian.org/92969
[4] https://sourceforge.net/p/sox/code/ci/master/tree/src/chorus.c


smime.p7s
Description: S/MIME cryptographic signature

Bug#859853: khtml: Please migrate to openssl1.1 in Buster

[Sebastian Andrzej Siewior]

Package: khtml
Version: 5.28.0-2
Severity: important
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1-trans

Please migrate to libssl-dev in the Buster cycle. It was switched to
libssl1.0-dev in order to follow QT (the bug report was #856004).

Sebastian

Bug#854604: 854604: CVE-2017-5886: fixed upstream

[Mattia Rizzolo]

Control: tag -1 fixed-upstream

https://sourceforge.net/p/podofo/code/1837

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#854600: #854600: CVE-2017-5852: fixed upstream

[Mattia Rizzolo]

Control: tag -1 fixed-upstream

https://sourceforge.net/p/podofo/code/1835

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#854602: 854602: CVE-2017-5854: fixed upstream

[Mattia Rizzolo]

Control: tag -1 fixed-upstream

https://sourceforge.net/p/podofo/code/1836

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#859852: telegram-desktop: Please migrate to openssl1.1 in Buster

[Sebastian Andrzej Siewior]

Package: telegram-desktop
Version: 1.0.14-1
Severity: important
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1-trans

Please migrate to libssl-dev in the Buster cycle.

Sebastian

Bug#859851: bind9: Please migrate to openssl1.1 in Buster

[Sebastian Andrzej Siewior]

Package: bind9
Version: 1:9.10.4-P5-1
Severity: important
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1-trans

Please migrate to libssl-dev in the Buster cycle. The bug report about
the FTBFS is #828082.

Sebastian

Bug#859739: RFP: pm-graph -- performance analysis of boot, suspend, and resume

[Todd Brandt]

On Thu, 06 Apr 2017 22:20:04 + Bart Martens 
 wrote:

noowner 859739
stop

A wnpp bug of type RFP should not have an owner.


I understand. I originally tagged it as ITP because I wanted to own it 
but require a sponsor. If you require a sponsor is ITP even allowed?

Bug#859849: /usr/share/doc/netcf/changelog.gz empty

[Marc Haber]

Package: netcf
Version: 1:0.2.8-1+b2
Severity: wishlist

Hi,

/usr/share/doc/netcf/changelog.gz is 20 bytes long, which is probably
the result of gzipping the empty ChangeLog from the upstream tarball.

Greetings
Marc

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

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

Versions of packages netcf depends on:
ii  libc6 2.24-9
ii  libnetcf1 1:0.2.8-1+b2
ii  libreadline7  7.0-2

netcf recommends no packages.

netcf suggests no packages.

-- no debconf information

Bug#859850: should support systemd-networkd

[Marc Haber]

Package: netcf
Version: 1:0.2.8-1+b2
Severity: wishlist
Tags: upstream

Please consider asking upstream to implement a driver for
systemd-networkd, and to automatically choose between traditional /e/n/i
- /e/s/n-s configuration and /etc/systemd/network.

Greetings
Marc

Bug#859848: upstream URL gone

[Marc Haber]

Package: netcf
Version: 1:0.2.8-1+b2
Severity: minor

Homepage: https://fedorahosted.org/netcf/

forwards to
https://fedoraproject.org/wiki/Infrastructure/Fedorahosted-retirement

The field needs to be updated.

Greetings
Marc

Bug#859033: pg_dump: creates dumps that cannot be restored

[Thorsten Glaser]

Hi *,

I’ve tried both setting the constraints temporarily to invalid (works)
and converting (painstakingly slow, as this is new for me) to triggers
(also works). Both can be dumped and restored.

I’ve also found out that I probably can ship the schema update that
converts the CHECK constraint to a trigger to the customer Right Now™
so I’ll fix this actual schema bug. I still find the CHECK constraint
to be a more natural way to express what I want, though.

I’m attaching the trigger conversion to help anyone else who does this
(and to invite feedback should there be anything I could improve).

Thanks,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

testcase.sql
Description: application/sql

Bug#859793: fluidsynth: Package has infringed GPL

[James Cowgill]

Hi,

On 07/04/17 19:01, Jaromír Mikeš wrote:
> 2017-04-07 14:16 GMT+02:00 Javier Serrano Polo  >:
> 
> Source: fluidsynth
> Version: 1.1.6-4
> Severity: wishlist
> 
> fluid_chorus.c is under a custom license, granting the following:
> 
> This source code is freely redistributable and may be used for
> any purpose.
> 
> 
> Hi fluidsynth devs,
> 
> we serious licensing issue in debian in fluid_chorus.c file.
> Is there any chance to relicense this file with some GPL friendly license?
> Full bug report here:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859793

FYI the license in question is the SoX license which has been in Debian
and basically all distributions for 20 years (as part of SoX)...

I assume the file is based on this:
https://sources.debian.net/src/sox/14.4.1-5/src/chorus.c/

The SoX project relicensed some time ago to GPL so if you are to believe
that that was OK, then there are no licensing problems with this file
(but the copyright header should be updated to reflect that).

James



signature.asc
Description: OpenPGP digital signature

Bug#859751: xtrs: please pass buildflags

[Graham Inggs]

On 7 April 2017 at 19:06, G. Branden Robinson
 wrote:
> All of this hardening stuff, as I understand it, involves mitigation
> strategies for unsafe memory usage in the C language family in the ELF
> object file format.

It's not only hardening stuff, it's whatever flags someone building
the package locally would like, e.g.
one could 'export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed' from
debian/rules and expect everything to be linked with that option.

Bug#859847: yagf: YAGF hangs opening image files with space in path

[Cyril Sluchanko]

Package: yagf
Version: 0.9.3.2-1
Severity: important
Tags: upstream

Dear Maintainer,

YAGF silently hangs on openig image file(s) with space in path. Moving files to
directory without spaces in it's name solves the problem.

Best regards,
Cyril Sluchanko



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

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

Versions of packages yagf depends on:
ii  cuneiform1.1.0+dfsg-5
ii  libaspell15  0.60.7~20110707-1.3
ii  libc62.19-18+deb8u7
ii  libgcc1  1:4.9.2-10
ii  libqtcore4   4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqtgui44:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libstdc++6   4.9.2-10

Versions of packages yagf recommends:
ii  xsane  0.998-6+b1

yagf suggests no packages.

-- no debconf information

Bug#859793: fluidsynth: Package has infringed GPL

[Jaromír Mikeš]

2017-04-07 14:16 GMT+02:00 Javier Serrano Polo :

> Source: fluidsynth
> Version: 1.1.6-4
> Severity: wishlist
>
> fluid_chorus.c is under a custom license, granting the following:
>
> This source code is freely redistributable and may be used for
> any purpose.
>

Hi fluidsynth devs,

we serious licensing issue in debian in fluid_chorus.c file.
Is there any chance to relicense this file with some GPL friendly license?
Full bug report here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859793

best regards

mira

Bug#859776: sponsorship-requests: vis/0.3 [ITP] -- A a modern and legacy free Vim-like text editor

[Adam Borowski]

On Fri, Apr 07, 2017 at 05:52:21PM +0200, Paride Legovini wrote:
> On 2017-04-07 15:39, Adam Borowski wrote:
> > On Fri, Apr 07, 2017 at 12:54:22PM +0200, Paride Legovini wrote:
> >>  * Package name: vis
> >>Version : 0.3

Seems to be fine, except for two error messages I get:

/usr/share/vis/themes/default-256.lua:23: attempt to index a nil value (local 
'lexers')
WARNING: could not find lpeg module

-- 
⢀⣴⠾⠻⢶⣦⠀ Meow!
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ Collisions shmolisions, let's see them find a collision or second
⠈⠳⣄ preimage for double rot13!

Bug#198765: Batch modify: #448, #502

[Xiph]

Batch modification to #448, #502 by ePirat:
component to Vorbis Tools

--
Tickets URL: 
Xiph 
building a new era of Open multimedia

Bug#859845: yarssr: Segmentation Fault on Quit

[Sebastian Wyngaard]

Package: yarssr
Version: 0.2.2-9
Severity: normal

Dear Maintainer,

* What led up to the situation?
I started yarssr from the command-line. Once started, if I quit yarssr through
the context menu (right click) the application segfaults.

I was trying to debug why yarssr loses all my configuration settings and feeds
after rebooting sometimes and noticed this segfault. I will submit a separate
bug report for that since I'm not sure if it is related.

This is the output when I run "yarssr --debug" and then quit:

GdkPixbuf-LOG **: gdk_pixbuf_from_pixdata() called on: at
/usr/share/yarssr/Yarssr.pm line 37,  line 1.
GdkPixbuf-LOG **:   Encoding raw at /usr/share/yarssr/Yarssr.pm line 37,
 line 1.
GdkPixbuf-LOG **:   Dimensions: 24 x 24 at /usr/share/yarssr/Yarssr.pm line
37,  line 1.
GdkPixbuf-LOG **:   Rowstride: 96, Length: 2328 at
/usr/share/yarssr/Yarssr.pm line 37,  line 1.
GdkPixbuf-LOG **:   Copy pixels == false at /usr/share/yarssr/Yarssr.pm
line 37,  line 1.
GdkPixbuf-LOG **: gdk_pixbuf_from_pixdata() called on: at
/usr/share/yarssr/Yarssr.pm line 37,  line 1.
GdkPixbuf-LOG **:   Encoding raw at /usr/share/yarssr/Yarssr.pm line 37,
 line 1.
GdkPixbuf-LOG **:   Dimensions: 24 x 24 at /usr/share/yarssr/Yarssr.pm line
37,  line 1.
GdkPixbuf-LOG **:   Rowstride: 96, Length: 2328 at
/usr/share/yarssr/Yarssr.pm line 37,  line 1.
GdkPixbuf-LOG **:   Copy pixels == false at /usr/share/yarssr/Yarssr.pm
line 37,  line 1.
GdkPixbuf-LOG **: gdk_pixbuf_from_pixdata() called on: at
/usr/share/yarssr/Yarssr.pm line 37,  line 1.
GdkPixbuf-LOG **:   Encoding raw at /usr/share/yarssr/Yarssr.pm line 37,
 line 1.
GdkPixbuf-LOG **:   Dimensions: 24 x 24 at /usr/share/yarssr/Yarssr.pm line
37,  line 1.
GdkPixbuf-LOG **:   Rowstride: 96, Length: 2328 at
/usr/share/yarssr/Yarssr.pm line 37,  line 1.
GdkPixbuf-LOG **:   Copy pixels == false at /usr/share/yarssr/Yarssr.pm
line 37,  line 1.
GdkPixbuf-LOG **: gdk_pixbuf_from_pixdata() called on: at
/usr/share/yarssr/Yarssr.pm line 37,  line 1.
GdkPixbuf-LOG **:   Encoding raw at /usr/share/yarssr/Yarssr.pm line 37,
 line 1.
GdkPixbuf-LOG **:   Dimensions: 24 x 24 at /usr/share/yarssr/Yarssr.pm line
37,  line 1.
GdkPixbuf-LOG **:   Rowstride: 96, Length: 2328 at
/usr/share/yarssr/Yarssr.pm line 37,  line 1.
GdkPixbuf-LOG **:   Copy pixels == false at /usr/share/yarssr/Yarssr.pm
line 37,  line 1.
GdkPixbuf-LOG **: gdk_pixbuf_from_pixdata() called on: at
/usr/share/yarssr/Yarssr.pm line 37,  line 1.
GdkPixbuf-LOG **:   Encoding raw at /usr/share/yarssr/Yarssr.pm line 37,
 line 1.
GdkPixbuf-LOG **:   Dimensions: 24 x 24 at /usr/share/yarssr/Yarssr.pm line
37,  line 1.
GdkPixbuf-LOG **:   Rowstride: 96, Length: 2328 at
/usr/share/yarssr/Yarssr.pm line 37,  line 1.
GdkPixbuf-LOG **:   Copy pixels == false at /usr/share/yarssr/Yarssr.pm
line 37,  line 1.
GdkPixbuf-LOG **: gdk_pixbuf_from_pixdata() called on: at
/usr/share/yarssr/Yarssr.pm line 37,  line 1.
GdkPixbuf-LOG **:   Encoding raw at /usr/share/yarssr/Yarssr.pm line 37,
 line 1.
GdkPixbuf-LOG **:   Dimensions: 24 x 24 at /usr/share/yarssr/Yarssr.pm line
37,  line 1.
GdkPixbuf-LOG **:   Rowstride: 96, Length: 2328 at
/usr/share/yarssr/Yarssr.pm line 37,  line 1.
GdkPixbuf-LOG **:   Copy pixels == false at /usr/share/yarssr/Yarssr.pm
line 37,  line 1.
GdkPixbuf-LOG **: gdk_pixbuf_from_pixdata() called on: at
/usr/share/yarssr/Yarssr.pm line 37,  line 1.
GdkPixbuf-LOG **:   Encoding raw at /usr/share/yarssr/Yarssr.pm line 37,
 line 1.
GdkPixbuf-LOG **:   Dimensions: 24 x 24 at /usr/share/yarssr/Yarssr.pm line
37,  line 1.
GdkPixbuf-LOG **:   Rowstride: 96, Length: 2328 at
/usr/share/yarssr/Yarssr.pm line 37,  line 1.
GdkPixbuf-LOG **:   Copy pixels == false at /usr/share/yarssr/Yarssr.pm
line 37,  line 1.
GdkPixbuf-LOG **: gdk_pixbuf_from_pixdata() called on: at
/usr/share/yarssr/Yarssr.pm line 37,  line 1.
GdkPixbuf-LOG **:   Encoding raw at /usr/share/yarssr/Yarssr.pm line 37,
 line 1.
GdkPixbuf-LOG **:   Dimensions: 24 x 24 at /usr/share/yarssr/Yarssr.pm line
37,  line 1.
GdkPixbuf-LOG **:   Rowstride: 96, Length: 2328 at
/usr/share/yarssr/Yarssr.pm line 37,  line 1.
GdkPixbuf-LOG **:   Copy pixels == false at /usr/share/yarssr/Yarssr.pm
line 37,  line 1.
GdkPixbuf-LOG **: gdk_pixbuf_from_pixdata() called on: at
/usr/share/yarssr/Yarssr.pm line 37,  line 1.
GdkPixbuf-LOG **:   Encoding raw at /usr/share/yarssr/Yarssr.pm line 37,
 line 1.
GdkPixbuf-LOG **:   Dimensions: 24 x 24 at /usr/share/yarssr/Yarssr.pm line
37,  line 1.
GdkPixbuf-LOG **:   Rowstride: 96, Length: 2328 at
/usr/share/yarssr/Yarssr.pm line 37,  line 1.
GdkPixbuf-LOG **:   Copy pixels == false at /usr/share/yarssr/Yarssr.pm
line 37,  line 1.
GdkPixbuf-LOG **: gdk_pixbuf_from_pixdata() called on: at
/usr/share/yarssr/Yarssr.pm line 37,  line 1.
GdkPixbuf-LOG **:   Encoding raw at /usr/share/yarssr/Yarssr.pm line 

Bug#858304: vim-runtime: markdown syntax highlighting (and possibly others) goes crazy and drives the terminal crazy

[Francesco Poli]

On Fri, 7 Apr 2017 12:08:58 -0400 James McCoy wrote:

> On Fri, Apr 07, 2017 at 07:23:39AM -0400, G. Branden Robinson wrote:
[...]
> > However, my xterms are somewhat customized.  I'm attaching my
> > .Xresources file.
> 
> Perfect! That seems to be the difference.  I, and presumably Francesco, aren't
> using TTF fonts.

Well presumed: my .Xresources file is described in a [document] on my
web site (and also attached for completeness' sake).

[document]: 





-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE
! set a nice font
UXTerm*Font: -misc-fixed-medium-*-*-*-15-*-*-*-*-*-iso10646-*
UXTerm*wideFont: -misc-fixed-medium-*-*-ja-18-*-*-*-*-*-iso10646-*
UXTerm*scaleHeight: 1.2
UXTerm*utf8Title: true

! set my favorite colors
UXTerm*background: black
UXTerm*foreground: white
UXTerm*colorBDMode: off
UXTerm*colorULMode: off

! no scrollbar
UXTerm*scrollBar: off

! set cursor blinking
UXTerm*cursorBlink: on

! set buffer size
UXTerm*saveLines: 1000

! configure selection rules
UXTerm*on2Clicks: regex [^/@ \n]+
UXTerm*on3Clicks: regex [^ \n]+
UXTerm*on4Clicks: regex [^#$]+
UXTerm*on5Clicks: line


pgpCZ739FwxRv.pgp
Description: PGP signature

Bug#859753: RFS:gnss-sdr/0.0.9-1 -- Global navigation satellite systems software defined receiver

[Iain R. Learmonth]

Hi,

On Fri, Apr 07, 2017 at 02:23:08PM +, Gianfranco Costamagna wrote:
> (I see you cc'd Iain, so in case feel free to sponsor the package or
> require more/less changes from him :) )

My workload is quite heavy at the moment, thanks for taking a look at this
Gianfranco. I had planned to not look at this until after the freeze, but I
have no objections to this being uploaded to experimental as long as the
changelog is updated to show the packaging changes.

Thanks,
Iain.



signature.asc
Description: PGP signature

Bug#859751: xtrs: please pass buildflags

[G. Branden Robinson]

At 2017-04-07T14:10:06+0200, Graham Inggs wrote:
> On 07/04/2017 13:12, G. Branden Robinson wrote:
> > compile_rom is an utility internal to the build.  It's not shipped and
> > thus not subject to attacks.  I'm considering adding an --ignore-line
> > for it, but I need to figure out how to embed this information in the
> > package itself so the buildd log scanner knows to use this flag itself.
> 
> Is there any harm in linking compile_rom with those flags?

Probably not, but what's the use case?

This compile_rom utility is only useful for, and only used to, embed
Z-80 instructions into the memory map of an emulated TRS-80 computer;
specifically _this_ emulator, xtrs.

All of this hardening stuff, as I understand it, involves mitigation
strategies for unsafe memory usage in the C language family in the ELF
object file format.

Again, the tool is not shipped.  I am having trouble thinking of any
attack vector involving compile_rom that isn't dwarfed by the fact that
it would have to be expoited during a package build, at which time there
are much simpler and nastier ways to attack a host, such as by embedding
hostile code into a maintainer script.  Those kinds of exploits are much
easier to write and we don't really screen for them.  Just the other I
saw on #debian-devel that we had a package that goofed up an rm -rf
command in its postinst and trashed /usr/bin or something like that.

My preference is to be fastidious about things, but I also have a strong
antipathy towards cargo-cult software engineering.  I cannot think of
any benefit of hardening compile_rom that is not extremely speculative.

Can you?

> > Please advise if you think the attachments don't address the issue.
> 
> All looks good, thanks!  I see the 'format not a string literal and no
> format arguments' errors are already fixed in upstream 4.9d.

Yes, and in the forthcoming -3 I fixed a bunch more that were exposed
when I compiled with -std=c11.

See attached patch.

Regards,
Branden
Align build with the ISO C11 standard.

-- Branden Robinson, 2017-04-04T09:40:13-0400
--- a/debug.c
+++ b/debug.c
@@ -18,6 +18,8 @@
$Id: debug.c,v 1.28 2009/06/16 00:10:39 mann Exp $
 */
 
+#define _POSIX_C_SOURCE 200112L /* signal.h: sigemptyset(), ... */
+
 #include "z80.h"
 #include "trs.h"
 
@@ -25,6 +27,7 @@
 #include 
 #include 
 #include 
+#include  /* strcasecmp() */
 
 #ifdef READLINE
 #include 
@@ -318,7 +321,7 @@
 int i;
 
 traps = (Uchar *) malloc(ADDRESS_SPACE * sizeof(Uchar));
-bzero(traps, ADDRESS_SPACE * sizeof(Uchar));
+memset(traps, 0, ADDRESS_SPACE * sizeof(Uchar));
 
 for(i = 0; i < MAX_TRAPS; ++i) trap_table[i].valid = 0;
 
--- a/cmddump.c
+++ b/cmddump.c
@@ -27,6 +27,9 @@
  *-p foo  select PDS entry "foo" (padded to 8 bytes with spaces)
  *-x  ignore anything after the first xfer address
  */
+
+#define _XOPEN_SOURCE /* unistd.h: getopt(), optarg, optind, opterr */
+
 #include 
 #include 
 #include 
--- a/mkdisk.c
+++ b/mkdisk.c
@@ -15,6 +15,8 @@
 /* If available, use C11 fopen()'s exclusive open flag.  Option -f overrides. */
 #define _ISOC11_SOURCE 1
 
+#define _XOPEN_SOURCE 500 /* unistd.h: getopt(), ...; sys/stat.h: fchmod() */
+
 #include 
 #include 
 #include 
--- a/trs_cassette.c
+++ b/trs_cassette.c
@@ -50,6 +50,9 @@
  *   Fabio Ferrari contributed the SB_SOUND implementation.  
  */
 
+#define _POSIX_C_SOURCE 200112L /* signal.h: sigemptyset(), ...
+   stdio.h: fileno() */
+
 #if __linux
 #define HAVE_OSS 1
 #define OSS_SOUND 1
--- a/trs_disk.c
+++ b/trs_disk.c
@@ -26,6 +26,8 @@
 #define SIZERETRY 1   /* Retry in different sizes on real_read */
 #define DMK_MARK_IAM 0/* Mark IAMs in track header; poor idea */
 
+#define _XOPEN_SOURCE 500 /* signal.h: SA_RESTART */
+
 #include "z80.h"
 #include "trs.h"
 #include "trs_disk.h"
--- a/trs_imp_exp.c
+++ b/trs_imp_exp.c
@@ -13,6 +13,8 @@
  *  easier.  
  */
 
+#define _XOPEN_SOURCE 500 /* ftruncate(), strdup() */
+
 #include 
 #include 
 #include 
--- a/trs_interrupt.c
+++ b/trs_interrupt.c
@@ -10,6 +10,8 @@
  * Emulate interrupts
  */
 
+#define _XOPEN_SOURCE 500 /* signal.h: SA_RESTART */
+
 #include "z80.h"
 #include "trs.h"
 #include 
--- a/trs_uart.c
+++ b/trs_uart.c
@@ -10,6 +10,8 @@
  * Emulation of the Radio Shack TRS-80 Model I/III/4/4P serial port.
  */
 
+#define _POSIX_C_SOURCE 200112L /* signal.h: sigemptyset(), ... */
+
 #include 
 #include 
 #include 
--- a/trs_xinterface.c
+++ b/trs_xinterface.c
@@ -28,6 +28,9 @@
  * X Windows interface for TRS-80 simulator
  */
 
+#define _DEFAULT_SOURCE /* string.h: strcasecmp() */
+#define _XOPEN_SOURCE 500 /* string.h: strdup() */
+
 #include 
 #include 
 #include 
--- a/Makefile
+++ b/Makefile
@@ -149,7 +149,7 @@
 include Makefile.local
 
 CFLAGS += $(DEBUG) $(ENDIAN) $(DEFAULT_ROM) $(READLINE) $(DISKDIR) $(IFLAGS) \
-   $(APPDEFAULTS) -DKBWAIT
+   $(APPDEFAULTS) -DKBWAIT -std=c11
 LIBS = $(XLIB) $(READLINELIBS) $(EXTRALIBS)
 
 ZMACFLAGS = 

Bug#859704:

[Michael Lustfield]

Thanks for reporting this error! I checked reverse deps of this build
dependency, but neglected to check newer packages such as this.
Hopefully this was the only package missed, but I will spend some time
making sure. I'll get this bug report resolved today.

Bug#859809: debian-edu-config: broken symlink: /etc/apache2/mods-available/debian-edu-userdir.load -> userdir.load

[Wolfgang Schweer]

On Fri, Apr 07, 2017 at 05:12:53PM +0200, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package ships (or creates)
> a broken symlink.

Hi Andreas,
thanks for the report.
 
> >From the attached log (scroll to the bottom...):
> 
> 2m7.2s ERROR: FAIL: Broken symlinks:
>   /etc/apache2/mods-available/debian-edu-userdir.load -> userdir.load
> 
> Are you perhaps missing a Depends/Recommends/Suggests: apache2 ?
 
Adding apache2 would fix it, I guess. I'm just wondering why this error
didn't show up with older versions of the d-e-config.

Another solution might be to drop said symlinking from 
d/debian-edu-config.links and to add it to cf/apache2.cf.
 
Wolfgang


signature.asc
Description: PGP signature

Bug#859779: BUG: unable to handle kernel paging request at 6f697468

[Ben Hutchings]

Control: tag -1 moreinfo

On Fri, 2017-04-07 at 13:47 +0200, Leo Weppelman wrote:
> Package: linux-source-3.16
> Version: 3.16.7-ckt20-1+deb8u4
> Severity: important
> Tags: upstream
> 
> Dear Maintainer,
> 
> We are running this system under KVM. The KVM host is running:
>   3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 
> 
> The client is running:
>   3.16.0-4-686-pae #1 SMP Debian 3.16.7-ckt20-1+deb8u4
[...]

Try upgrading the clients and report back if that doesn't fix this.

Ben.

-- 
Ben Hutchings
Never attribute to conspiracy what can adequately be explained by
stupidity.



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

Bug#859667: [Pkg-d-devel] Bug#859667: libundead: FTBFS on armhf and ppc64el: tests fail

[Konstantinos Margaritis]

Στις 07-04-2017, ημέρα Παρ, και ώρα 18:03 +0200, ο/η Iain Buclaw
έγραψε:
> On 7 April 2017 at 16:02, Andreas Tille  wrote:
> > On Wed, Apr 05, 2017 at 10:22:28PM +0200, Iain Buclaw wrote:
> > > Which compiler?
> > 
> > $ LANG=C apt-cache policy ldc
> > ldc:
> >   Installed: 1:1.1.1-1
> > 
> > > Are NaNs being honoured?
> > 
> > Hmmm, no idea how to check this.
> > 
> 
> Someone who maintains ldc might know. :-)

Hi Andreas, long time :)

There are some issues with ldc on arm/ppc64le ports currently and I
would like to build a new ldc package based on a 1.2 beta which is out
now as it seems to fix most of those -no idea if that's also the case
with libundead, but it's possible, some of them are math related.

I hope to do that in the next days, but time is really short these
days, I apologize for the delay :)

Regards

Konstantinos

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

Bug#858304: vim-runtime: markdown syntax highlighting (and possibly others) goes crazy and drives the terminal crazy

[G. Branden Robinson]

At 2017-04-07T12:08:58-0400, James McCoy wrote:
> On Fri, Apr 07, 2017 at 07:23:39AM -0400, G. Branden Robinson wrote:
> > However, my xterms are somewhat customized.  I'm attaching my
> > .Xresources file.
> 
> Perfect! That seems to be the difference.  I, and presumably Francesco, aren't
> using TTF fonts.  If I change your Xresources to use
> 
> XTerm.*.VT100.Font: 
> -misc-fixed-medium-r-normal--18-120-100-100-c-90-iso10646-1
> 
> instead of the FaceName/FaceSize resources, then playing the recording
> reproduces the problem.

I agree that we're narrowing it down.  I commented out my *.face*
resources, xrdb -merged .Xresources, ran xterms from other xterms, and
got some intriguing stuff on stderr.

$ xterm
xterm: cannot load font '-Misc-Fixed-Bold-o-*-*-13-120-75-75-C-60-ISO10646-1'
$ xterm -fn '-misc-fixed-medium-r-normal--18-120-100-100-c-90-iso10646-1'
xterm: cannot load font 
'-Misc-Fixed-Medium-o-*-*-18-120-100-100-C-90-ISO10646-1'
xterm: cannot load font '-Misc-Fixed-Bold-o-*-*-18-120-100-100-C-90-ISO10646-1'
xterm: cannot load font 
'-Misc-Fixed-Medium-o-*-*-18-120-100-100-C-180-ISO10646-1'
xterm: cannot load font 
'-Misc-Fixed-Medium-o-*-*-18-120-100-100-C-180-ISO10646-1'

To me, this implicates something at or near the bold font emulation
stuff that xterm does.  This may be enough for Thomas Dickey to locate
the bug.

There's some pretty complicated logic involved; from xterm(1):

alwaysBoldMode (class AlwaysBoldMode)
   Specifies whether xterm should check if the normal and bold
   fonts are distinct before deciding whether to use overstriking
   to simulate bold fonts.  If this resource is true, xterm does
   not make the check for distinct fonts when deciding how to
   handle the boldMode resource.  The default is "false".

   boldMode   alwaysBoldMode   Comparison   Action
   
   false  falseignored  use font
   false  true ignored  use font
   true   falsesame overstrike
   true   falsedifferentuse font
   true   true ignored  overstrike

   This resource is used only for bitmap fonts:

   ·   When using bitmap fonts, it is possible that the font
   server will approximate the bold font by rescaling it from
   a different font size than expected.  The alwaysBoldMode
   resource allows the user to override the (sometimes poor)
   resulting bold font with overstriking (which is at least
   consistent).

   ·   The problem does not occur with TrueType fonts (though
   there can be other unnecessary issues such as different
   coverage of the normal and bold fonts).

   As an alternative, setting the allowBoldFonts resource to false
   overrides both the alwaysBoldMode and the boldMode resources.

Regards,
Branden


signature.asc
Description: PGP signature

Bug#859577:

[Michael Lustfield]

Thanks for looking over my changes and catching this mistake!
I'll get a correction uploaded today.

Bug#859841: zurl: Please migrate to openssl1.1 in Buster

[Sebastian Andrzej Siewior]

Package: zurl
Version: 1.7.1-4
Severity: important
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1-trans
control: block -1 by 858398

Please migrate to libssl-dev in the Buster cycle. The package switch to
libssl1.0-dev due to curl, see #850881.

Sebastian

Bug#859843: unblock:mistral/3.0.0-4

[David Rabel]

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

Please unblock package mistral

We need the dependency on openstack-pkg-tools (>= 54~) to install correctly.

unblock mistral/3.0.0-4

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

Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
diff -Nru mistral-3.0.0/debian/changelog mistral-3.0.0/debian/changelog
--- mistral-3.0.0/debian/changelog  2016-10-06 17:56:44.0 +0200
+++ mistral-3.0.0/debian/changelog  2017-04-03 18:07:09.0 +0200
@@ -1,3 +1,33 @@
+mistral (3.0.0-4) unstable; urgency=medium
+
+  * Add allow-sqla-1.1.patch to allow SQLA transition.
+  * German debconf translation update (Closes: #842487).
+
+ -- Thomas Goirand   Mon, 03 Apr 2017 18:07:09 +0200
+
+mistral (3.0.0-3) unstable; urgency=medium
+
+  * Team upload.
+  * Bump build dependency on openstack-pkg-tools (Closes: #858705).
+
+ -- David Rabel   Sat, 01 Apr 2017 11:54:37 +0200
+
+mistral (3.0.0-2) unstable; urgency=medium
+
+  [ Corey Bryant ]
+  * d/rules, d/mistral-common.postinst.in, d/mistral-common.postrm:
+Install missing json files (LP: #1634475).
+  * d/control: Add python-pep8 to Build-Depends.
+
+  [ Thomas Goirand ]
+  * Fixed lsb-base depends.
+
+  [ Gauvain Pocentek ]
+  * d/rules: install missing resources directory, needed when populating the
+mistral DB
+
+ -- Thomas Goirand   Wed, 19 Oct 2016 11:05:37 +0200
+
 mistral (3.0.0-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru mistral-3.0.0/debian/control mistral-3.0.0/debian/control
--- mistral-3.0.0/debian/control2016-10-06 17:56:44.0 +0200
+++ mistral-3.0.0/debian/control2017-04-03 18:07:09.0 +0200
@@ -6,7 +6,7 @@
 Build-Depends: debhelper (>= 9),
dh-python,
dh-systemd,
-   openstack-pkg-tools (>= 53~),
+   openstack-pkg-tools (>= 54~),
po-debconf,
python-all,
python-pbr (>= 1.8),
@@ -55,6 +55,7 @@
  python-osprofiler (>= 1.4.0),
  python-paramiko (>= 2.0),
  python-pecan (>= 1.0.0),
+ python-pep8,
  python-requests (>= 2.10.0),
  python-requests-mock (>= 1.0),
  python-retrying (>= 1.2.3),
diff -Nru mistral-3.0.0/debian/debian_control_vars 
mistral-3.0.0/debian/debian_control_vars
--- mistral-3.0.0/debian/debian_control_vars1970-01-01 01:00:00.0 
+0100
+++ mistral-3.0.0/debian/debian_control_vars2017-04-03 18:07:09.0 
+0200
@@ -0,0 +1 @@
+ostack-lsb-base= lsb-base (>= 3.0.6)
diff -Nru mistral-3.0.0/debian/mistral-common.postinst.in 
mistral-3.0.0/debian/mistral-common.postinst.in
--- mistral-3.0.0/debian/mistral-common.postinst.in 2016-10-06 
17:56:44.0 +0200
+++ mistral-3.0.0/debian/mistral-common.postinst.in 2017-04-03 
18:07:09.0 +0200
@@ -14,6 +14,7 @@
 
pkgos_write_new_conf mistral mistral.conf
pkgos_write_new_conf mistral logging.conf
+   pkgos_write_new_conf mistral policy.json
pkgos_write_new_conf mistral wf_trace_logging.conf
db_get mistral/configure_db
if [ "$RET" = "true" ]; then
diff -Nru mistral-3.0.0/debian/mistral-common.postrm 
mistral-3.0.0/debian/mistral-common.postrm
--- mistral-3.0.0/debian/mistral-common.postrm  2016-10-06 17:56:44.0 
+0200
+++ mistral-3.0.0/debian/mistral-common.postrm  2017-04-03 18:07:09.0 
+0200
@@ -24,6 +24,7 @@
 
rm -f /etc/mistral/mistral.conf
rm -f /etc/mistral/logging.conf
+   rm -f /etc/mistral/policy.json
rm -f /etc/mistral/wf_trace_logging.conf
rm -rf /var/log/mistral
[ -d /etc/mistral ] && rmdir --ignore-fail-on-non-empty /etc/mistral
diff -Nru mistral-3.0.0/debian/patches/allow-sqla-1.1.patch 
mistral-3.0.0/debian/patches/allow-sqla-1.1.patch
--- mistral-3.0.0/debian/patches/allow-sqla-1.1.patch   1970-01-01 
01:00:00.0 +0100
+++ mistral-3.0.0/debian/patches/allow-sqla-1.1.patch   2017-04-03 
18:07:09.0 +0200
@@ -0,0 +1,16 @@
+Description: Allow SQLA 1.1
+Author: Thomas Goirand 
+Forwarded: not-needed
+Last-Update: 2017-04-03
+
+--- mistral-3.0.0.orig/requirements.txt
 mistral-3.0.0/requirements.txt
+@@ -48,7 +48,7 @@ requests>=2.10.0 # Apache-2.0
+ retrying!=1.3.0,>=1.2.3 # Apache-2.0
+ setuptools!=24.0.0,>=16.0 # PSF/ZPL
+ six>=1.9.0 # MIT
+-SQLAlchemy<1.1.0,>=1.0.10 # MIT
++SQLAlchemy>=1.0.10 # MIT
+ stevedore>=1.16.0 # Apache-2.0
+ WSME>=0.8 # MIT
+ yaql>=1.1.0 # Apache 2.0 License
diff -Nru mistral-3.0.0/debian/patches/series 
mistral-3.0.0/debian/patches/series
--- mistral-3.0.0/debian/patches/series 

Bug#859842: unblock:watcher/0.30.0-5

[David Rabel]

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

Please unblock package watcher

We need the dependency on openstack-pkg-tools (>= 54~) to install correctly.

unblock watcher/0.30.0-5

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

Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
diff -Nru watcher-0.30.0/debian/changelog watcher-0.30.0/debian/changelog
--- watcher-0.30.0/debian/changelog 2017-01-16 13:20:05.0 +0100
+++ watcher-0.30.0/debian/changelog 2017-04-01 12:39:26.0 +0200
@@ -1,3 +1,11 @@
+watcher (0.30.0-5) unstable; urgency=medium
+
+  * Team upload.
+  * Delete wrong net-tools dependency.
+  * Bump build dependency on openstack-pkg-tools (Closes: #858713). 
+
+ -- David Rabel   Sat, 01 Apr 2017 12:39:26 +0200
+
 watcher (0.30.0-4) unstable; urgency=medium
 
   * Team upload.
diff -Nru watcher-0.30.0/debian/control watcher-0.30.0/debian/control
--- watcher-0.30.0/debian/control   2017-01-16 13:20:05.0 +0100
+++ watcher-0.30.0/debian/control   2017-04-01 12:39:26.0 +0200
@@ -6,7 +6,7 @@
 Build-Depends: debhelper (>= 10),
dh-python,
dh-systemd,
-   openstack-pkg-tools (>= 53~),
+   openstack-pkg-tools (>= 54~),
po-debconf,
python-all,
python-pbr (>= 1.8),
@@ -146,7 +146,6 @@
 Depends: adduser,
  watcher-common (= ${binary:Version}),
  debconf,
- net-tools,
  python-keystoneclient,
  python-openstackclient,
  q-text-as-data,

Bug#859844: vmtk: Please migrate to openssl1.1 in Buster

[Sebastian Andrzej Siewior]

Package: vmtk
Version: 1.3+dfsg-2.1
Severity: important
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1-trans

Please migrate to libssl-dev in the Buster cycle. The bug report about
the FTBFS is #850026.

Sebastian

Bug#859840: zorp: Please migrate to openssl1.1 in Buster

[Sebastian Andrzej Siewior]

Package: zorp
Version: 6.0.10-2
Severity: important
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1-trans

Please migrate to libssl-dev in the Buster cycle. The bug report about
the FTBFS is #828620.

Sebastian

Bug#859838: yubico-piv-tool: Please migrate to openssl1.1 in Buster

[Sebastian Andrzej Siewior]

Package: yubico-piv-tool
Version: 1.4.2-2
Severity: important
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1-trans
control: forwarded -1 https://github.com/Yubico/yubico-piv-tool/issues/104

Please migrate to libssl-dev in the Buster cycle. The bug report about
the FTBFS is #828616. The log of the FTBFS can be found at

https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/yubico-piv-tool_1.0.3-1_amd64-20160529-1559

Sebastian

Bug#859839: unblock:senlin/2.0.0-3

[David Rabel]

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

Please unblock package senlin

We need the dependency on openstack-pkg-tools (>= 54~) to install correctly.

unblock unblock:senlin/2.0.0-3

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

Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
diff -Nru senlin-2.0.0/debian/changelog senlin-2.0.0/debian/changelog
--- senlin-2.0.0/debian/changelog   2017-01-20 13:02:01.0 +0100
+++ senlin-2.0.0/debian/changelog   2017-04-01 12:35:16.0 +0200
@@ -1,3 +1,10 @@
+senlin (2.0.0-3) unstable; urgency=medium
+
+  * Team upload.
+  * Bump build dependency on openstack-pkg-tools (Closes: #858712).
+
+ -- David Rabel   Sat, 01 Apr 2017 12:35:16 +0200
+
 senlin (2.0.0-2) unstable; urgency=medium
 
   * Team upload.
diff -Nru senlin-2.0.0/debian/control senlin-2.0.0/debian/control
--- senlin-2.0.0/debian/control 2017-01-20 13:02:01.0 +0100
+++ senlin-2.0.0/debian/control 2017-04-01 12:35:16.0 +0200
@@ -6,7 +6,7 @@
 Build-Depends: debhelper (>= 10),
dh-python,
dh-systemd,
-   openstack-pkg-tools (>= 53~),
+   openstack-pkg-tools (>= 54~),
po-debconf,
python-all,
python-pbr (>= 1.8),

Bug#859832: unblock:magnum/3.1.1-4

[David Rabel]

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

Please unblock package magnum

We need the dependency on openstack-pkg-tools (>= 54~) to install correctly.

unblock magnum/3.1.1-4

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

Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
diff -Nru magnum-3.1.1/debian/changelog magnum-3.1.1/debian/changelog
--- magnum-3.1.1/debian/changelog   2016-12-07 16:53:30.0 +0100
+++ magnum-3.1.1/debian/changelog   2017-04-04 17:31:50.0 +0200
@@ -1,3 +1,17 @@
+magnum (3.1.1-4) unstable; urgency=medium
+
+  * Brazilian Portuguese debconf templates (Closes: #852444).
+  * German debconf translation update (Closes: #842486).
+
+ -- Thomas Goirand   Tue, 04 Apr 2017 17:31:50 +0200
+
+magnum (3.1.1-3) unstable; urgency=medium
+
+  * Team upload.
+  * Bump build dependency on openstack-pkg-tools (Closes: #858703).
+
+ -- David Rabel   Sat, 01 Apr 2017 11:49:48 +0200
+
 magnum (3.1.1-2) unstable; urgency=medium
 
   [ Ondřej Nový ]
diff -Nru magnum-3.1.1/debian/control magnum-3.1.1/debian/control
--- magnum-3.1.1/debian/control 2016-12-07 16:53:30.0 +0100
+++ magnum-3.1.1/debian/control 2017-04-04 17:31:50.0 +0200
@@ -6,7 +6,7 @@
 Build-Depends: debhelper (>= 10),
dh-python,
dh-systemd,
-   openstack-pkg-tools (>= 53~),
+   openstack-pkg-tools (>= 54~),
po-debconf,
python-all,
python-pbr (>= 1.8),
diff -Nru magnum-3.1.1/debian/po/de.po magnum-3.1.1/debian/po/de.po
--- magnum-3.1.1/debian/po/de.po2016-12-07 16:53:30.0 +0100
+++ magnum-3.1.1/debian/po/de.po2017-04-04 17:31:50.0 +0200
@@ -1,14 +1,14 @@
 # German debconf translation of magnum.
 # This file is distributed under the same license as the magnum package.
 # Copyright (C) 2010 United States Government,2010-2011 OpenStack LLC.
-# Copyright (C) of this file 2012-2014 Chris Leick .
+# Copyright (C) of this file 2012-2016 Chris Leick .
 #
 msgid ""
 msgstr ""
-"Project-Id-Version: magnum 2013.2.1-1\n"
+"Project-Id-Version: magnum 3.1.1-1\n"
 "Report-Msgid-Bugs-To: mag...@packages.debian.org\n"
 "POT-Creation-Date: 2016-03-29 13:38+\n"
-"PO-Revision-Date: 2014-01-09 22:51+0100\n"
+"PO-Revision-Date: 2016-10-28 18:11+0100\n"
 "Last-Translator: Chris Leick \n"
 "Language-Team: German \n"
 "Language: de\n"
@@ -25,18 +25,13 @@
 #. Type: boolean
 #. Description
 #: ../magnum-common.templates:2001
-#, fuzzy
-#| msgid ""
-#| "No database has been set up for magnum-registry or glance-api to use. "
-#| "Before continuing, you should make sure you have the following "
-#| "information:"
 msgid ""
 "No database has been set up for Magnum to use. Before continuing, you should "
 "make sure you have the following information:"
 msgstr ""
-"Es wurde keine Datenbank für die Benutzung mit der Magnum-Registry oder das "
-"Magnum-API eingerichtet. Bevor Sie fortfahren, sollten Sie sicherstellen, "
-"dass Sie die folgenden Informationen haben:"
+"Es wurde keine Datenbank für die Benutzung mit Magnum eingerichtet. Bevor Sie 
"
+"fortfahren, sollten Sie sicherstellen, dass Sie die folgenden Informationen "
+"haben:"
 
 #. Type: boolean
 #. Description
@@ -83,16 +78,11 @@
 #. Type: string
 #. Description
 #: ../magnum-common.templates:3001
-#, fuzzy
-#| msgid ""
-#| "Please specify the hostname of the authentication server for Magnum. "
-#| "Typically this is also the hostname of the OpenStack Identity Service "
-#| "(Keystone)."
 msgid ""
 "Please specify the hostname of the authentication server. Typically this is "
 "also the hostname of the OpenStack Identity Service (Keystone)."
 msgstr ""
-"Bitte geben Sie den Rechnernamen des Magnum-Authentifizierungsservers an. "
+"Bitte geben Sie den Rechnernamen des Authentifizierungsservers an. "
 "Typischerweise ist das gleichzeitig der Rechnername Ihres OpenStack-"
 "Identitätsdienstes (Keystone)."
 
@@ -226,18 +216,15 @@
 #. Type: boolean
 #. Description
 #: ../magnum-api.templates:2001
-#, fuzzy
-#| msgid ""
-#| "Note that you will need to have an up and running Keystone server on "
-#| "which to connect using the Keystone authentication token."
 msgid ""
 "Note that you will need to have an up and running Keystone server on which "
 "to connect using a known admin project name, admin username and password. "
 "The admin auth token is not used anymore."
 msgstr ""
-"Beachten Sie, dass Sie einen gestarteten und laufenden Keystone-Server haben "
-"müssen, mit dem Sie sich anhand des Keystone-Authentifizierungs-Tokens "
-"verbinden."
+"Beachten Sie, dass Sie einen konfigurierten und laufenden 

Bug#859835: unblock:murano/3.0.0-6

[David Rabel]

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

Please unblock package murano

We need the dependency on openstack-pkg-tools (>= 54~) to install correctly.

unblock murano/3.0.0-6

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

Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
diff -Nru murano-3.0.0/debian/changelog murano-3.0.0/debian/changelog
--- murano-3.0.0/debian/changelog   2016-12-18 11:32:17.0 +0100
+++ murano-3.0.0/debian/changelog   2017-04-03 17:46:45.0 +0200
@@ -1,3 +1,40 @@
+murano (1:3.0.0-6) unstable; urgency=medium
+
+  * Re-incorporate NMU from piotr fixing SQLA depends.
+  * Danish translation of the debconf templates (Closes: #849983).
+
+ -- Thomas Goirand   Mon, 03 Apr 2017 17:46:45 +0200
+
+murano (1:3.0.0-5) unstable; urgency=medium
+
+  * Team upload.
+  * Revert net-tools dependency.
+  * Bump build dependency on openstack-pkg-tools (Closes: #858707).
+
+ -- David Rabel   Sat, 01 Apr 2017 11:55:59 +0200
+
+murano (1:3.0.0-4) unstable; urgency=medium
+
+  * Team upload.
+  * Add missing dependency net-tools (Closes: #858707).
+
+ -- David Rabel   Sat, 25 Mar 2017 13:13:14 +0100
+
+murano (1:3.0.0-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Patch requirements.txt to drop SQLAlchemy << 1.1 dependency
+
+ -- Piotr Ożarowski   Sun, 05 Feb 2017 12:46:10 +0100
+
+murano (1:3.0.0-3) unstable; urgency=medium
+
+  * Fix murano-cfapi startup (LP: 1659270):
+- Correctly loads murano-cfapi.conf instead of murano.conf.
+- Package and install murano-cfapi-paste.ini.
+
+ -- Thomas Goirand   Wed, 25 Jan 2017 22:16:32 +0100
+
 murano (1:3.0.0-2) unstable; urgency=medium
 
   [ Ondřej Nový ]
diff -Nru murano-3.0.0/debian/control murano-3.0.0/debian/control
--- murano-3.0.0/debian/control 2016-12-18 11:32:17.0 +0100
+++ murano-3.0.0/debian/control 2017-04-03 17:46:45.0 +0200
@@ -8,7 +8,7 @@
 Build-Depends: debhelper (>= 10),
dh-python,
dh-systemd,
-   openstack-pkg-tools (>= 53~),
+   openstack-pkg-tools (>= 54~),
po-debconf,
python-all,
python-pbr (>= 1.8),
diff -Nru murano-3.0.0/debian/murano-cfapi.init.in 
murano-3.0.0/debian/murano-cfapi.init.in
--- murano-3.0.0/debian/murano-cfapi.init.in2016-12-18 11:32:17.0 
+0100
+++ murano-3.0.0/debian/murano-cfapi.init.in2017-04-03 17:46:45.0 
+0200
@@ -15,3 +15,4 @@
 DESC="OpenStack Murano CF API"
 PROJECT_NAME=murano
 NAME=${PROJECT_NAME}-cfapi
+CONFIG_FILE=/etc/${PROJECT_NAME}/${PROJECT_NAME}-cfapi.conf
diff -Nru murano-3.0.0/debian/murano-common.postinst.in 
murano-3.0.0/debian/murano-common.postinst.in
--- murano-3.0.0/debian/murano-common.postinst.in   2016-12-18 
11:32:17.0 +0100
+++ murano-3.0.0/debian/murano-common.postinst.in   2017-04-03 
17:46:45.0 +0200
@@ -20,6 +20,8 @@
# Manage the configuration file
pkgos_write_new_conf ${PROJECT_NAME} ${PROJECT_NAME}.conf
pkgos_write_new_conf ${PROJECT_NAME} murano-cfapi.conf
+   pkgos_write_new_conf ${PROJECT_NAME} murano-cfapi-paste.ini
+
pkgos_rabbit_write_conf ${PROJECT_CONF} oslo_messaging_rabbit 
${PROJECT_NAME}
pkgos_write_admin_creds ${PROJECT_CONF} keystone_authtoken 
${PROJECT_NAME}
 db_get ${PROJECT_NAME}/configure_db
diff -Nru 
murano-3.0.0/debian/patches/patch-requirements.txt-to-allow-sqla-1.1.patch 
murano-3.0.0/debian/patches/patch-requirements.txt-to-allow-sqla-1.1.patch
--- murano-3.0.0/debian/patches/patch-requirements.txt-to-allow-sqla-1.1.patch  
1970-01-01 01:00:00.0 +0100
+++ murano-3.0.0/debian/patches/patch-requirements.txt-to-allow-sqla-1.1.patch  
2017-04-03 17:46:45.0 +0200
@@ -0,0 +1,13 @@
+Index: murano-3.0.0/requirements.txt
+===
+--- murano-3.0.0.orig/requirements.txt
 murano-3.0.0/requirements.txt
+@@ -3,7 +3,7 @@
+ # process, which may cause wedges in the gate later.
+ pbr>=1.6 # Apache-2.0
+ Babel>=2.3.4 # BSD
+-SQLAlchemy<1.1.0,>=1.0.10 # MIT
++SQLAlchemy>=1.0.10 # MIT
+ stevedore>=1.16.0 # Apache-2.0
+ alembic>=0.8.4 # MIT
+ eventlet!=0.18.3,>=0.18.2 # MIT
diff -Nru murano-3.0.0/debian/patches/series murano-3.0.0/debian/patches/series
--- murano-3.0.0/debian/patches/series  1970-01-01 01:00:00.0 +0100
+++ murano-3.0.0/debian/patches/series  2017-04-03 17:46:45.0 +0200
@@ -0,0 +1 @@
+patch-requirements.txt-to-allow-sqla-1.1.patch
diff -Nru murano-3.0.0/debian/po/da.po murano-3.0.0/debian/po/da.po
--- murano-3.0.0/debian/po/da.po1970-01-01 01:00:00.0 +0100
+++ murano-3.0.0/debian/po/da.po

Bug#859833: unblock:manila/3.0.0-5

[David Rabel]

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

Please unblock package manila

We need the dependency on openstack-pkg-tools (>= 54~) to install correctly.

unblock manila/3.0.0-5

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

Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
diff -Nru manila-3.0.0/debian/changelog manila-3.0.0/debian/changelog
--- manila-3.0.0/debian/changelog   2017-01-20 11:36:39.0 +0100
+++ manila-3.0.0/debian/changelog   2017-04-03 18:15:18.0 +0200
@@ -1,3 +1,24 @@
+manila (1:3.0.0-5) unstable; urgency=medium
+
+  * German debconf translation update (Closes: #842485).
+
+ -- Thomas Goirand   Mon, 03 Apr 2017 18:15:18 +0200
+
+manila (1:3.0.0-4) unstable; urgency=medium
+
+  * Team upload.
+  * Revert net-tools dependency.
+  * Bump build dependency on openstack-pkg-tools (Closes: #858704).
+
+ -- David Rabel   Sat, 01 Apr 2017 11:51:11 +0200
+
+manila (1:3.0.0-3) unstable; urgency=medium
+
+  * Team upload.
+  * Add missing dependency (Closes: #858704).
+
+ -- David Rabel   Sat, 25 Mar 2017 12:46:57 +0100
+
 manila (1:3.0.0-2) unstable; urgency=medium
 
   * Team upload.
diff -Nru manila-3.0.0/debian/control manila-3.0.0/debian/control
--- manila-3.0.0/debian/control 2017-01-20 11:36:39.0 +0100
+++ manila-3.0.0/debian/control 2017-04-03 18:15:18.0 +0200
@@ -8,7 +8,7 @@
 Build-Depends: debhelper (>= 10),
dh-python,
dh-systemd,
-   openstack-pkg-tools (>= 53~),
+   openstack-pkg-tools (>= 54~),
po-debconf,
python-all,
python-pbr (>= 1.8),
diff -Nru manila-3.0.0/debian/po/de.po manila-3.0.0/debian/po/de.po
--- manila-3.0.0/debian/po/de.po2017-01-20 11:35:56.0 +0100
+++ manila-3.0.0/debian/po/de.po2017-04-03 18:15:18.0 +0200
@@ -1,14 +1,14 @@
 # German debconf translation of manila.
 # This file is distributed under the same license as the manila package.
 # Copyright (C) 2010 United States Government,2010-2011 OpenStack LLC.
-# Copyright (C) of this file 2012-2014 Chris Leick .
+# Copyright (C) of this file 2012-2016 Chris Leick .
 #
 msgid ""
 msgstr ""
-"Project-Id-Version: manila 2013.2.1-1\n"
+"Project-Id-Version: manila 3.0.0-1\n"
 "Report-Msgid-Bugs-To: man...@packages.debian.org\n"
 "POT-Creation-Date: 2016-03-29 13:41+\n"
-"PO-Revision-Date: 2014-01-09 22:51+0100\n"
+"PO-Revision-Date: 2016-10-28 21:51+0100\n"
 "Last-Translator: Chris Leick \n"
 "Language-Team: German \n"
 "Language: de\n"
@@ -25,18 +25,12 @@
 #. Type: boolean
 #. Description
 #: ../manila-common.templates:2001
-#, fuzzy
-#| msgid ""
-#| "No database has been set up for manila-registry or glance-api to use. "
-#| "Before continuing, you should make sure you have the following "
-#| "information:"
 msgid ""
 "No database has been set up for Manila to use. Before continuing, you should "
 "make sure you have the following information:"
 msgstr ""
-"Es wurde keine Datenbank für die Benutzung mit der Manila-Registry oder das "
-"Manila-API eingerichtet. Bevor Sie fortfahren, sollten Sie sicherstellen, "
-"dass Sie die folgenden Informationen haben:"
+"Es wurde keine Datenbank für die Benutzung mit Manila. Bevor Sie fortfahren, "
+"sollten Sie sicherstellen, dass Sie die folgenden Informationen haben:"
 
 #. Type: boolean
 #. Description
@@ -67,16 +61,12 @@
 #. Type: boolean
 #. Description
 #: ../manila-common.templates:2001
-#, fuzzy
-#| msgid ""
-#| "You can change this setting later on by running \"dpkg-reconfigure -plow "
-#| "manila-common\"."
 msgid ""
 "You can change this setting later on by running \"dpkg-reconfigure -plow "
 "manila\"."
 msgstr ""
 "Sie können diese Einstellung später ändern, indem Sie »dpkg-reconfigure -"
-"plow manila-common« ausführen."
+"plow manila« ausführen."
 
 #. Type: string
 #. Description
@@ -87,16 +77,11 @@
 #. Type: string
 #. Description
 #: ../manila-common.templates:3001
-#, fuzzy
-#| msgid ""
-#| "Please specify the hostname of the authentication server for Manila. "
-#| "Typically this is also the hostname of the OpenStack Identity Service "
-#| "(Keystone)."
 msgid ""
 "Please specify the hostname of the authentication server. Typically this is "
 "also the hostname of the OpenStack Identity Service (Keystone)."
 msgstr ""
-"Bitte geben Sie den Rechnernamen des Manila-Authentifizierungsservers an. "
+"Bitte geben Sie den Rechnernamen des Authentifizierungsservers an. "
 "Typischerweise ist das gleichzeitig der Rechnername Ihres OpenStack-"
 "Identitätsdienstes (Keystone)."
 
@@ -230,18 +215,15 @@
 #. Type: boolean
 #. Description
 

Bug#859836: unblock:neutron/9.1.1-3

[David Rabel]

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

Please unblock package neutron

We need the dependency on openstack-pkg-tools (>= 54~) to install correctly.

unblock neutron/9.1.1-3

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

Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
diff -Nru neutron-9.1.1/debian/changelog neutron-9.1.1/debian/changelog
--- neutron-9.1.1/debian/changelog  2016-12-03 18:16:52.0 +0100
+++ neutron-9.1.1/debian/changelog  2017-04-03 18:11:13.0 +0200
@@ -1,3 +1,16 @@
+neutron (2:9.1.1-3) unstable; urgency=medium
+
+  * Dutch translation of debconf messages (Closes: #841651).
+
+ -- Thomas Goirand   Mon, 03 Apr 2017 18:11:13 +0200
+
+neutron (2:9.1.1-2) unstable; urgency=medium
+
+  * Team upload.
+  * Bump build dependency on openstack-pkg-tools (Closes: #858706).
+
+ -- David Rabel   Sat, 01 Apr 2017 11:57:49 +0200
+
 neutron (2:9.1.1-1) unstable; urgency=medium
 
   [ Ondřej Nový ]
diff -Nru neutron-9.1.1/debian/control neutron-9.1.1/debian/control
--- neutron-9.1.1/debian/control2016-12-03 18:16:52.0 +0100
+++ neutron-9.1.1/debian/control2017-04-03 18:11:13.0 +0200
@@ -8,7 +8,7 @@
 Build-Depends: debhelper (>= 10),
dh-python,
dh-systemd,
-   openstack-pkg-tools (>= 53~),
+   openstack-pkg-tools (>= 54~),
po-debconf,
python-all,
python-pbr (>= 1.8),
diff -Nru neutron-9.1.1/debian/po/nl.po neutron-9.1.1/debian/po/nl.po
--- neutron-9.1.1/debian/po/nl.po   2016-12-03 18:16:52.0 +0100
+++ neutron-9.1.1/debian/po/nl.po   2017-04-03 18:11:13.0 +0200
@@ -5,10 +5,10 @@
 #
 msgid ""
 msgstr ""
-"Project-Id-Version: neutron_2_8.0.0-1\n"
-"Report-Msgid-Bugs-To: neut...@packages.debian.org\n"
-"POT-Creation-Date: 2016-06-06 00:25+0200\n"
-"PO-Revision-Date: 2016-04-19 15:57+0200\n"
+"Project-Id-Version: neutron_2_9.0.0-1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2016-10-07 14:28+\n"
+"PO-Revision-Date: 2016-10-10 18:04+0200\n"
 "Last-Translator: Frans Spiesschaert \n"
 "Language-Team: Debian Dutch l10n Team \n"
 "Language: nl\n"
@@ -76,86 +76,46 @@
 #. Type: select
 #. Choices
 #: ../neutron-common.templates:6001
-msgid "OpenVSwitch"
-msgstr "OpenVSwitch"
-
-#. Type: select
-#. Choices
-#: ../neutron-common.templates:6001
-msgid "LinuxBridge"
-msgstr "LinuxBridge"
-
-#. Type: select
-#. Choices
-#: ../neutron-common.templates:6001
 msgid "ml2"
 msgstr "ml2"
 
 #. Type: select
 #. Choices
 #: ../neutron-common.templates:6001
-msgid "Brocade"
-msgstr "Brocade"
-
-#. Type: select
-#. Choices
-#: ../neutron-common.templates:6001
-msgid "Nicira"
-msgstr "Nicira"
-
-#. Type: select
-#. Choices
-#: ../neutron-common.templates:6001
-msgid "Midonet"
-msgstr "Midonet"
-
-#. Type: select
-#. Choices
-#: ../neutron-common.templates:6001
-msgid "NEC"
-msgstr "NEC"
+msgid "plumgrid"
+msgstr "plumgrid"
 
 #. Type: select
 #. Choices
 #: ../neutron-common.templates:6001
-msgid "Mellanox"
-msgstr "Mellanox"
+#| msgid "Midonet"
+msgid "midonet"
+msgstr "midonet"
 
 #. Type: select
 #. Choices
 #: ../neutron-common.templates:6001
-msgid "Hyper-V"
-msgstr "Hyper-V"
+#| msgid "Midonet"
+msgid "midonet_v2"
+msgstr "midonet_v2"
 
 #. Type: select
 #. Choices
 #: ../neutron-common.templates:6001
-msgid "RYU"
-msgstr "RYU"
+msgid "nec"
+msgstr "nec"
 
 #. Type: select
 #. Choices
 #: ../neutron-common.templates:6001
-msgid "MetaPlugin"
-msgstr "MetaPlugin"
+msgid "vmware"
+msgstr "vmware"
 
 #. Type: select
 #. Choices
 #: ../neutron-common.templates:6001
-msgid "BigSwitch"
-msgstr "BigSwitch"
-
-#. Type: select
-#. Choices
-#: ../neutron-common.templates:6001
-msgid "Cisco"
-msgstr "Cisco"
-
-#. Type: select
-#. Choices
-#: ../neutron-common.templates:6001
-msgid "PLUMgrid"
-msgstr "PLUMgrid"
+msgid "other"
+msgstr "andere"
 
 #. Type: select
 #. Description
@@ -671,6 +631,42 @@
 "voor metagegevens van Nova. Hetzelfde gedeelde wachtwoord moet gebruikt "
 "worden bij het instellen van het pakket nova-common."
 
+#~ msgid "OpenVSwitch"
+#~ msgstr "OpenVSwitch"
+
+#~ msgid "LinuxBridge"
+#~ msgstr "LinuxBridge"
+
+#~ msgid "Brocade"
+#~ msgstr "Brocade"
+
+#~ msgid "Nicira"
+#~ msgstr "Nicira"
+
+#~ msgid "NEC"
+#~ msgstr "NEC"
+
+#~ msgid "Mellanox"
+#~ msgstr "Mellanox"
+
+#~ msgid "Hyper-V"
+#~ msgstr "Hyper-V"
+
+#~ msgid "RYU"
+#~ msgstr "RYU"
+
+#~ msgid "MetaPlugin"
+#~ msgstr "MetaPlugin"
+
+#~ msgid "BigSwitch"
+#~ msgstr "BigSwitch"
+
+#~ msgid "Cisco"
+#~ msgstr "Cisco"
+
+#~ msgid "PLUMgrid"
+#~ msgstr "PLUMgrid"
+
 #~ msgid "Auth server username:"
 #~ msgstr "Gebruikersnaam op de authenticatieserver:"
 

Bug#859837: unblock:sahara/5.0.0-3

[David Rabel]

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

Please unblock package sahara

We need the dependency on openstack-pkg-tools (>= 54~) to install correctly.

unblock sahara/5.0.0-3

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

Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
diff -Nru sahara-5.0.0/debian/changelog sahara-5.0.0/debian/changelog
--- sahara-5.0.0/debian/changelog   2017-01-20 14:59:11.0 +0100
+++ sahara-5.0.0/debian/changelog   2017-03-25 13:30:26.0 +0100
@@ -1,3 +1,10 @@
+sahara (1:5.0.0-3) unstable; urgency=medium
+
+  * Team upload.
+  * Add missing dependency net-tools (Closes: #858711).
+
+ -- David Rabel   Sat, 25 Mar 2017 13:30:26 +0100
+
 sahara (1:5.0.0-2) unstable; urgency=medium
 
   * Team upload.
diff -Nru sahara-5.0.0/debian/control sahara-5.0.0/debian/control
--- sahara-5.0.0/debian/control 2017-01-20 14:56:44.0 +0100
+++ sahara-5.0.0/debian/control 2017-03-25 13:30:26.0 +0100
@@ -159,6 +159,7 @@
 Section: python
 Depends: adduser,
  dbconfig-common,
+ net-tools,
  python-openstackclient,
  q-text-as-data,
  sahara-common (= ${source:Version}),

Bug#859834: yafc: Please migrate to openssl1.1 in Buster

[Sebastian Andrzej Siewior]

Package: yafc
Version: 1.3.7-3
Severity: important
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1-trans

Please migrate to libssl-dev in the Buster cycle.

Sebastian

Bug#859831: xmltooling: Please migrate to openssl1.1 in Buster

[Sebastian Andrzej Siewior]

Package: xmltooling
Version: 1.6.0-4
Severity: important
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1-trans

Please migrate to libssl-dev in the Buster cycle. The bug report about
the FTBFS is #828608. The log of the FTBFS can be found at

https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/xmltooling_1.5.6-2_amd64-20160529-1555

Sebastian

Bug#859828: unblock:heat/7.0.0-4

[David Rabel]

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

Please unblock package heat

We need the dependency on openstack-pkg-tools (>= 54~) to install correctly.

unblock heat/7.0.0-4

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

Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Bug#859826: xca: Please migrate to openssl1.1 in Buster

[Sebastian Andrzej Siewior]

Package: xca
Version: 1.3.2-2
Severity: important
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1-trans

Please migrate to libssl-dev in the Buster cycle. The bug report about
the FTBFS is #828604. The log of the FTBFS can be found at

https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/xca_1.3.2-1_amd64-20160529-1554

Sebastian

Bug#859830: unblock:ironic/6.2.0-3

[David Rabel]

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

Please unblock package ironic

We need the dependency on openstack-pkg-tools (>= 54~) to install correctly.

unblock ironic/6.2.0-3

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

Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Bug#859827: opendkim: refile documentation in opendkim.conf(5) is misleading

[Russell Coker]

Package: opendkim
Version: 2.11.0~alpha-9
Severity: normal
Tags: upstream

  If this table specifies a regular  expression  file  ("refile"),
  then the keys are wildcard patterns that are matched against the
  address found in the From: header field.  Entries are checked in
  the order in which they appear in the file.

The above section from opendki.conf(5) can be interpreted to mean that such
files take regular expressions which would mean that it would take
".*@example.com" as the version of OpenDKIM in Jessie did.  An interpretation
of that which might be more common among people who are less familiar with
regular expressions is that it means it would take wildcard glob patterns like
in filenames on the commandline, so it would take "*@example.com" which isn't
the way it worked in Jessie.

It turns out that the latter interpretation is how the code works.  Either the
man page needs to be changed to note that it doesn't take regular expressions
at all, or the code needs to be changed to make it take regular expressions
and the phrase "wildcard patterns" needs to be removed from the man page.

This is actually a serious issue, if you get this wrong mail just doesn't
get signed and there seems to be no way to get opendkim to tell you why.

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

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

Versions of packages opendkim depends on:
ii  adduser  3.115
ii  dns-root-data2015052300+h+1
ii  init-system-helpers  1.47
ii  libbsd0  0.8.3-1
ii  libc62.24-9
ii  libdb5.3 5.3.28-12+b1
ii  libldap-2.4-22.4.44+dfsg-3
ii  liblua5.1-0  5.1.5-8.1+b2
ii  libmemcached11   1.0.18-4.1
ii  libmemcachedutil21.0.18-4.1
ii  libmilter1.0.1   8.15.2-8
ii  libopendbx1  1.4.6-11
ii  libopendkim112.11.0~alpha-9
ii  librbl1  2.11.0~alpha-9
ii  libssl1.11.1.0e-1
ii  libunbound2  1.6.0-3
ii  libvbr2  2.11.0~alpha-9
ii  lsb-base 9.20161125

opendkim recommends no packages.

Versions of packages opendkim suggests:
ii  opendkim-tools  2.11.0~alpha-9
pn  unbound 

-- Configuration Files:
/etc/default/opendkim [Errno 2] No such file or directory: 
'/etc/default/opendkim'
/etc/opendkim.conf changed [not included]

-- no debconf information

Bug#859829: xml-security-c: Please migrate to openssl1.1 in Buster

[Sebastian Andrzej Siewior]

Package: xml-security-c
Version: 1.7.3-4
Severity: important
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1-trans

Please migrate to libssl-dev in the Buster cycle. The bug report about
the FTBFS is #828607. The log of the FTBFS can be found at

https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/xml-security-c_1.7.3-1_amd64-20160529-1555

Sebastian

Bug#859825: zfs-initramfs: finding root by bootfs or mountpoint properties broken

[Andreas Korsten]

Package: zfs-initramfs
Version: 0.6.5.9-5
Severity: important

Dear Maintainer,

according to line 765 of the file
/usr/share/initramfs-tools/scripts/zfs
it should be possible for the initramfs to detect the root file system
by the zpool's bootfs property.  This fails because in line 838 IFS is
redefined.  A simple fix would be something like this:


--- /usr/share/initramfs-tools/scripts/zfs  2017-03-19 11:14:57.0 
+0100
+++ /etc/initramfs-tools/scripts/zfs2017-04-07 17:10:56.304513058 +0200
@@ -840,8 +840,8 @@
do
[ -z "$pool" ] && continue
 
-   import_pool "$pool"
-   find_rootfs "$pool"
+   IFS="$OLD_IFS" import_pool "$pool"
+   IFS="$OLD_IFS" find_rootfs "$pool"
done
IFS="$OLD_IFS"
 

If you set boot=zfs and omit root=zfs:AUTO, this will work (tested
with a single zpool and the bootfs and mountpoint properties set).
However, setting root=zfs:AUTO still fails because in line 790
ZFS_BOOTFS is set to zfs:AUTO and subsequently in line 930 it is
attempted to look up a dataset with the name zfs:AUTO (not even the
zfs: part will be stripped in this case).



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

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

Versions of packages zfs-initramfs depends on:
ii  busybox 1:1.22.0-19+b2
ii  initramfs-tools 0.127
ii  zfs-dkms [zfs-modules]  0.6.5.9-5
ii  zfsutils-linux  0.6.5.9-5

zfs-initramfs recommends no packages.

zfs-initramfs suggests no packages.

-- no debconf information

Bug#681510: debhelper: dh_install --fail-missing defaults to . as sourcedir even when install itself uses debian/tmp

[Luk Claes]

Hi Niels

I haven't noticed it anymore, so I guess it's fixed.

Luk

On Fri, Apr 7, 2017 at 4:01 PM, Niels Thykier  wrote:
> Control: tags -1 moreinfo
>
> On Fri, 13 Jul 2012 19:29:38 +0200 Luk Claes  wrote:
>> Package: debhelper
>> Version: 9.20120608
>> Severity: normal
>>
>> dh_install --fail-missing complains about not installed files even if they 
>> got installed. This only happens when not specifying sourcedir explicitly 
>> when invoking dh_install. It seems it also does happen only when using v7 or 
>> higher and not specifying explicitly where the files should be installed to 
>> in the .install files. According to the documentation it uses 
>> debian/tmp by default as sourcedir in that case. As the installation itself 
>> worked, it seems there is only something missing in keeping track of what 
>> got installed.
>>
>> Cheers
>>
>> Luk
>>
>>
>>
>
> Hi Luk,
>
> Do you still experience this issue?  My gut feeling is that this bug
> probably have been fixed already by now (due to some recent experiments
> with moving --fail-missing to a separate helper, where I did not notice
> this issue).
>
> Thanks,
> ~Niels
>

Bug#858304: vim-runtime: markdown syntax highlighting (and possibly others) goes crazy and drives the terminal crazy

[James McCoy]

On Fri, Apr 07, 2017 at 07:23:39AM -0400, G. Branden Robinson wrote:
> At 2017-04-06T21:56:13-0400, James McCoy wrote:
> > On Fri, Apr 07, 2017 at 12:54:19AM +0200, Francesco Poli wrote:
> > > On Thu, 6 Apr 2017 15:06:17 -0400 G. Branden Robinson wrote:
> > > 
> > > > At 2017-04-06T13:33:58-0400, James McCoy wrote:
> > > > > On Thu, Apr 06, 2017 at 01:17:55PM -0400, G. Branden Robinson wrote:
> > > > > > The below is not a sufficient reproduction receipe for me.
> > > > > > 
> > > > > > I'm running Debian Stretch (testing).
> > > > > > 
> > > > > > Things do not go wrong at step #5, nor afterward.
> > > > > 
> > > > > Make sure the terminal is sized small enough (80x24).  That causes the
> > > > > syntax highlighting in Vim to get a little confused and enable some 
> > > > > bold
> > > > > highlighting, which then causes the visual bell to turn everything 
> > > > > bold.
> > > > 
> > > > It was.
> > > 
> > > Hello Branden!
> > > Thanks for trying to reproduce the bug.
> > > 
> > > Does it help to know that I have:
> > > 
> > >   xset b off
> > > 
> > > in my ~/.xsession script?
> > 
> > I don't think that's relevant.  My bell is on.  I was also able to
> > reproduce it without causing the bell.
> > 
> > I've attached an asciinema recording of me reproducing the problem.
> > When I replay the recording, it causes the same problem to the xterm in
> > which it is running, so hopefully this helps debug the problem.
> 
> That's really interesing.  I _still_ can't repro this, even playing back
> James's demo with asciinema--a tool of which I wasn't aware, thanks!
> 
> I'm launching xterm in GNOME with the GNOME command runner, whatever
> that's called--the Alt+F2 thing.
> 
> However, my xterms are somewhat customized.  I'm attaching my
> .Xresources file.

Perfect! That seems to be the difference.  I, and presumably Francesco, aren't
using TTF fonts.  If I change your Xresources to use

XTerm.*.VT100.Font: -misc-fixed-medium-r-normal--18-120-100-100-c-90-iso10646-1

instead of the FaceName/FaceSize resources, then playing the recording
reproduces the problem.

Cheers,
James

Bug#859823: unblock:glance/13.0.0-4

[David Rabel]

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

Please unblock package glance

We need the dependency on openstack-pkg-tools (>= 54~) to install correctly.

unblock glance/13.0.0-4

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

Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Bug#859824: unblock:gnocchi/3.0.4-4

[David Rabel]

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

Please unblock package gnocchi

We need the dependency on openstack-pkg-tools (>= 54~) to install correctly.

unblock gnocchi/3.0.4-4

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

Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
diff -Nru gnocchi-3.0.4/debian/changelog gnocchi-3.0.4/debian/changelog
--- gnocchi-3.0.4/debian/changelog  2017-04-01 11:35:30.0 +0200
+++ gnocchi-3.0.4/debian/changelog  2017-04-03 18:13:32.0 +0200
@@ -1,3 +1,9 @@
+gnocchi (3.0.4-4) unstable; urgency=medium
+
+  * German debconf translation update (Closes: #842481).
+
+ -- Thomas Goirand   Mon, 03 Apr 2017 18:13:32 +0200
+
 gnocchi (3.0.4-3) unstable; urgency=medium
 
   * Team upload.
diff -Nru gnocchi-3.0.4/debian/po/de.po gnocchi-3.0.4/debian/po/de.po
--- gnocchi-3.0.4/debian/po/de.po   2017-04-01 11:35:30.0 +0200
+++ gnocchi-3.0.4/debian/po/de.po   2017-04-03 18:13:32.0 +0200
@@ -1,14 +1,14 @@
-# German debconf translation of glance.
-# This file is distributed under the same license as the glance package.
+# German debconf translation of gnocchi.
+# This file is distributed under the same license as the gnocchi package.
 # Copyright (C) 2010 United States Government,2010-2011 OpenStack LLC.
-# Copyright (C) of this file 2012-2014 Chris Leick .
+# Copyright (C) of this file 2012-2016 Chris Leick .
 #
 msgid ""
 msgstr ""
-"Project-Id-Version: glance 2013.2.1-1\n"
+"Project-Id-Version: gnocchi 3.0.0-2\n"
 "Report-Msgid-Bugs-To: gnoc...@packages.debian.org\n"
 "POT-Creation-Date: 2016-03-29 13:10+\n"
-"PO-Revision-Date: 2014-01-09 22:51+0100\n"
+"PO-Revision-Date: 2016-10-29 18:15+0100\n"
 "Last-Translator: Chris Leick \n"
 "Language-Team: German \n"
 "Language: de\n"
@@ -25,17 +25,12 @@
 #. Type: string
 #. Description
 #: ../gnocchi-common.templates:2001
-#, fuzzy
-#| msgid ""
-#| "Please specify the hostname of the authentication server for Glance. "
-#| "Typically this is also the hostname of the OpenStack Identity Service "
-#| "(Keystone)."
 msgid ""
 "Please specify the hostname of the authentication server for Gnocchi. "
 "Typically this is also the hostname of the OpenStack Identity Service "
 "(Keystone)."
 msgstr ""
-"Bitte geben Sie den Rechnernamen des Glance-Authentifizierungsservers an. "
+"Bitte geben Sie den Rechnernamen des Gnocci-Authentifizierungsservers an. "
 "Typischerweise ist das gleichzeitig der Rechnername Ihres OpenStack-"
 "Identitätsdienstes (Keystone)."
 
@@ -96,26 +91,19 @@
 #. Type: boolean
 #. Description
 #: ../gnocchi-common.templates:6001
-#, fuzzy
-#| msgid "Set up a database for Glance?"
 msgid "Set up a database for Gnocchi?"
-msgstr "Eine Datenbank für Glance einrichten?"
+msgstr "Eine Datenbank für Gnocci einrichten?"
 
 #. Type: boolean
 #. Description
 #: ../gnocchi-common.templates:6001
-#, fuzzy
-#| msgid ""
-#| "No database has been set up for glance-registry or glance-api to use. "
-#| "Before continuing, you should make sure you have the following "
-#| "information:"
 msgid ""
 "No database has been set up for Gnocchi to use. Before continuing, you "
 "should make sure you have the following information:"
 msgstr ""
-"Es wurde keine Datenbank für die Benutzung mit der Glance-Registry oder das "
-"Glance-API eingerichtet. Bevor Sie fortfahren, sollten Sie sicherstellen, "
-"dass Sie die folgenden Informationen haben:"
+"Es wurde keine Datenbank für die Benutzung mit Gnocci eingerichtet. Bevor Sie 
"
+"fortfahren, sollten Sie sicherstellen, dass Sie die folgenden Informationen "
+"haben:"
 
 #. Type: boolean
 #. Description
@@ -146,24 +134,18 @@
 #. Type: boolean
 #. Description
 #: ../gnocchi-common.templates:6001
-#, fuzzy
-#| msgid ""
-#| "You can change this setting later on by running \"dpkg-reconfigure -plow "
-#| "glance-common\"."
 msgid ""
 "You can change this setting later on by running \"dpkg-reconfigure -plow "
 "gnocchi-common\"."
 msgstr ""
 "Sie können diese Einstellung später ändern, indem Sie »dpkg-reconfigure -"
-"plow glance-common« ausführen."
+"plow gnocci-common« ausführen."
 
 #. Type: boolean
 #. Description
 #: ../gnocchi-api.templates:2001
-#, fuzzy
-#| msgid "Register Glance in the Keystone endpoint catalog?"
 msgid "Register Gnocchi in the Keystone endpoint catalog?"
-msgstr "Glance im Keystone-Endpunktkatalog registrieren?"
+msgstr "Gnocci im Keystone-Endpunktkatalog registrieren?"
 
 #. Type: boolean
 #. Description
@@ -180,18 +162,15 @@
 #. Type: boolean
 #. Description
 #: ../gnocchi-api.templates:2001
-#, fuzzy
-#| msgid ""
-#| "Note that you will need to have an up and running Keystone server on "
-#| "which to connect using the 

Bug#859822: unblock:congress/4.0.0+dfsg1-3

[David Rabel]

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

Please unblock package congress

We need the dependency on openstack-pkg-tools (>= 54~) to install correctly.

unblock congress/4.0.0+dfsg1-3

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

Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Bug#859821: CVE-2017-5923 CVE-2017-5924 CVE-2016-10210 CVE-2016-10211

[Moritz Muehlenhoff]

Source: yara
Severity: important
Tags: security

Hi,
please see
https://security-tracker.debian.org/tracker/CVE-2017-5924
https://security-tracker.debian.org/tracker/CVE-2017-5923
https://security-tracker.debian.org/tracker/CVE-2016-10210
https://security-tracker.debian.org/tracker/CVE-2016-10211

Cheers,
Moritz

Bug#859818: unblock:ceilometer/7.0.1-3

[David Rabel]

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

Please unblock package ceilometer

We need the dependency on openstack-pkg-tools (>= 54~) to install correctly.

unblock ceilometer/7.0.1-3

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

Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Bug#859815: CVE-2017-7572

[Moritz Muehlenhoff]

Source: backintime
Severity: important
Tags: security

Hi,
please see http://www.openwall.com/lists/oss-security/2017/04/07/2

Cheers,
Moritz

Bug#859819: unblock: nova/14.0.0-4 (CVE-2017-7214)

[Thomas Goirand]

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

Please unblock package nova

This upload fixes CVE-2017-7214, and bumps openstack-pkg-tools build-depends
to >= 54~, to make sure the nova-api config script doesn't use /sbin/route
and /bin/ip if they aren't available (as they aren't essential packages).

Please unblock nova/14.0.0-4,
Cheers,

Thomas Goirand (zigo)
diff -Nru nova-14.0.0/debian/changelog nova-14.0.0/debian/changelog
--- nova-14.0.0/debian/changelog	2016-12-09 16:40:19.0 +
+++ nova-14.0.0/debian/changelog	2017-04-02 10:52:50.0 +
@@ -1,3 +1,14 @@
+nova (2:14.0.0-4) unstable; urgency=medium
+
+  [ David Rabel ]
+  * Team upload.
+  * Bump build dependency on openstack-pkg-tools (Closes: #858708, #858710).
+
+  [ Thomas Goirand ]
+  * CVE-2017-7214: apply upstream patch (Closes: 858568).
+
+ -- Thomas Goirand   Sun, 02 Apr 2017 12:52:50 +0200
+
 nova (2:14.0.0-3) unstable; urgency=medium
 
   [ Ondřej Nový ]
diff -Nru nova-14.0.0/debian/control nova-14.0.0/debian/control
--- nova-14.0.0/debian/control	2016-12-09 16:40:19.0 +
+++ nova-14.0.0/debian/control	2017-04-02 10:52:50.0 +
@@ -7,7 +7,7 @@
 Build-Depends: debhelper (>= 10),
dh-python,
dh-systemd,
-   openstack-pkg-tools (>= 52~),
+   openstack-pkg-tools (>= 54~),
po-debconf,
python-all,
python-pbr (>= 1.8),
diff -Nru nova-14.0.0/debian/patches/CVE-2017-7214_do_not_include_context_to_exception_notification.patch nova-14.0.0/debian/patches/CVE-2017-7214_do_not_include_context_to_exception_notification.patch
--- nova-14.0.0/debian/patches/CVE-2017-7214_do_not_include_context_to_exception_notification.patch	1970-01-01 00:00:00.0 +
+++ nova-14.0.0/debian/patches/CVE-2017-7214_do_not_include_context_to_exception_notification.patch	2017-04-02 10:52:50.0 +
@@ -0,0 +1,50 @@
+Description: CVE-2017-7214: do not include context to exception notification
+ The wrap_exception decorator optionally emited a notification.
+ Based on the code comments the original intention was not to include the
+ context to that notification due to security reasons. However the
+ implementation did included the context to the payload of the legacy
+ notification.
+ .
+ Recently we saw circural reference errors during the payload serialization
+ of this notification. Based on the logs the only complex data structure
+ that could cause circural reference is the context. So this patch
+ removes the context from the legacy exception notification.
+ .
+ The versioned exception notification is not affected as it does not
+ contain the args of the decorated function.
+Author: Balazs Gibizer 
+Date: Fri, 17 Mar 2017 10:24:49 + (+0100)
+X-Git-Tag: 14.0.5~1
+X-Git-Url: https://review.openstack.org/gitweb?p=openstack%2Fnova.git;a=commitdiff_plain;h=d0ee248bab672761c15998c58a0f11a5351b
+Origin: https://review.openstack.org/447072
+Bug-Ubuntu: https://bugs.launchpad.net/nova/+bug/1673569
+Bug-Debian: https://bugs.debian.org/858568
+Change-Id: I1d217620e52d45595a3e0e49ed57b4ab33cd1688
+Last-Update: 2017-04-02
+
+diff --git a/nova/exception_wrapper.py b/nova/exception_wrapper.py
+index 5b74c3b..5051b83 100644
+--- a/nova/exception_wrapper.py
 b/nova/exception_wrapper.py
+@@ -86,6 +86,9 @@ def _get_call_dict(function, self, context, *args, **kw):
+ # self can't be serialized and shouldn't be in the
+ # payload
+ call_dict.pop('self', None)
++# NOTE(gibi) remove context as well as it contains sensitive information
++# and it can also contain circular references
++call_dict.pop('context', None)
+ return _cleanse_dict(call_dict)
+ 
+ 
+diff --git a/nova/tests/unit/test_exception.py b/nova/tests/unit/test_exception.py
+index a9bada1..55478a6 100644
+--- a/nova/tests/unit/test_exception.py
 b/nova/tests/unit/test_exception.py
+@@ -61,6 +61,7 @@ class WrapExceptionTestCase(test.NoDBTestCase):
+ self.assertEqual(3, notification.payload['args']['extra'])
+ for key in ['exception', 'args']:
+ self.assertIn(key, notification.payload.keys())
++self.assertNotIn('context', notification.payload['args'].keys())
+ 
+ self.assertEqual(1, len(fake_notifier.VERSIONED_NOTIFICATIONS))
+ notification = fake_notifier.VERSIONED_NOTIFICATIONS[0]
diff -Nru nova-14.0.0/debian/patches/series nova-14.0.0/debian/patches/series
--- nova-14.0.0/debian/patches/series	2016-12-09 16:40:19.0 +
+++ nova-14.0.0/debian/patches/series	2017-04-02 10:52:50.0 +
@@ -4,3 +4,4 @@
 fix-requirements.txt.patch
 clean-up-build_requests-table-on-upgrades.patch
 allow-using-sqla-1.1.patch
+CVE-2017-7214_do_not_include_context_to_exception_notification.patch

Bug#859820: unblock:cinder/9.0.0-4

[David Rabel]

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

Please unblock package cinder

We need the dependency on openstack-pkg-tools (>= 54~) to install correctly.

unblock cinder/9.0.0-4

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

Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Bug#859817: unblock:barbican/3.0.0-3

[David Rabel]

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

Please unblock package barbican

We need the dependency on openstack-pkg-tools (>= 54~) to install correctly.

unblock barbican/3.0.0-3

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

Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Bug#859816: unblock:aodh/3.0.0-4

[David Rabel]

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

Please unblock package aodh

We need the dependency on openstack-pkg-tools (>= 54~) to install correctly.

unblock aodh/3.0.0-4

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

Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Bug#859814: unblock: designate/3.0.0-4 (not using net-tools and iproute2 in config script anymore)

[Thomas Goirand]

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

Please unblock package designate,

The last upload bumps openstack-pkg-tools build-dependency to >= 54~. This
avoids using /sbin/route, and /bin/ip (if that last one isn't available), as
these packages aren't essential packages.

The debdiff is very small (one line in debian/control if you don't count the
updated debconf translation).

Please unblock designate/3.0.0-4,
Cheers,

Thomas Goirand (zigo)
diff -Nru designate-3.0.0/debian/changelog designate-3.0.0/debian/changelog
--- designate-3.0.0/debian/changelog	2016-12-13 16:23:04.0 +
+++ designate-3.0.0/debian/changelog	2017-04-04 15:29:47.0 +
@@ -1,3 +1,16 @@
+designate (1:3.0.0-4) unstable; urgency=medium
+
+  * Updated German debconf translation (Closes: #857524).
+
+ -- Thomas Goirand   Tue, 04 Apr 2017 17:29:47 +0200
+
+designate (1:3.0.0-3) unstable; urgency=medium
+
+  * Build-depends on openstack-pkg-tools >= 54~ to ensure config script doesn't
+use net-tools or iproute2, which aren't essential (Closes: #859443).
+
+ -- Thomas Goirand   Mon, 03 Apr 2017 16:50:31 +0200
+
 designate (1:3.0.0-2) unstable; urgency=medium
 
   [ Ondřej Nový ]
diff -Nru designate-3.0.0/debian/control designate-3.0.0/debian/control
--- designate-3.0.0/debian/control	2016-12-13 16:23:04.0 +
+++ designate-3.0.0/debian/control	2017-04-04 15:29:47.0 +
@@ -6,7 +6,7 @@
 Build-Depends: debhelper (>= 10),
dh-python,
dh-systemd,
-   openstack-pkg-tools (>= 53~),
+   openstack-pkg-tools (>= 54~),
po-debconf,
python-all,
python-pbr (>= 1.8),
diff -Nru designate-3.0.0/debian/po/de.po designate-3.0.0/debian/po/de.po
--- designate-3.0.0/debian/po/de.po	2016-12-13 16:23:04.0 +
+++ designate-3.0.0/debian/po/de.po	2017-04-04 15:29:47.0 +
@@ -1,13 +1,13 @@
 # Translation of designate debconf templates to German
-# Copyright (C) Helge Kreutzmann , 2014.
+# Copyright (C) Helge Kreutzmann , 2014, 2017.
 # This file is distributed under the same license as the designate package.
 #
 msgid ""
 msgstr ""
-"Project-Id-Version: designate 2014.1-10\n"
-"Report-Msgid-Bugs-To: design...@packages.debian.org\n"
-"POT-Creation-Date: 2016-03-29 12:52+\n"
-"PO-Revision-Date: 2014-09-27 14:38+0200\n"
+"Project-Id-Version: designate 1:3.0.0-2\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2016-12-15 14:26+\n"
+"PO-Revision-Date: 2017-03-12 06:38+0100\n"
 "Last-Translator: Helge Kreutzmann \n"
 "Language-Team: de \n"
 "Language: \n"
@@ -215,17 +215,15 @@
 #. Type: boolean
 #. Description
 #: ../designate-api.templates:2001
-#, fuzzy
-#| msgid ""
-#| "Note that you will need to have an up and running Keystone server on "
-#| "which to connect using the Keystone authentication token."
 msgid ""
 "Note that you will need to have an up and running Keystone server on which "
 "to connect using a known admin project name, admin username and password. "
 "The admin auth token is not used anymore."
 msgstr ""
 "Beachten Sie, dass ein laufender Keystone-Server benötigt wird, bei dem Sie "
-"sich mit einem Keystone-Authentifizierungs-Token verbinden können."
+"sich mit einem bekannten Projektnamen, Administrator-Benutzernamen und "
+"Passwort verbinden können. Der Administrations-Authentifizierungs-Token wird "
+"nicht mehr verwandt."
 
 #. Type: string
 #. Description
@@ -247,26 +245,30 @@
 #. Type: string
 #. Description
 #: ../designate-api.templates:4001
-#, fuzzy
-#| msgid "Keystone authentication token:"
 msgid "Keystone admin name:"
-msgstr "Keystone-Authentifizierungs-Token:"
+msgstr "Keystone-Administratorname:"
 
 #. Type: string
 #. Description
 #. Type: string
 #. Description
+#. Type: password
+#. Description
 #: ../designate-api.templates:4001 ../designate-api.templates:5001
+#: ../designate-api.templates:6001
 msgid ""
 "To register the service endpoint, this package needs to know the Admin "
 "login, name, project name, and password to the Keystone server."
 msgstr ""
+"Um den Diensteendpunkt zu registrieren, muss dieses Paket den Anmeldenamen "
+"des Administrators, den Namen, den Projektnamen und das Passwort für den "
+"Keystone-Server kennen."
 
 #. Type: string
 #. Description
 #: ../designate-api.templates:5001
 msgid "Keystone admin project name:"
-msgstr ""
+msgstr "Keystone-Administratorprojektname:"
 
 #. Type: password
 #. Description
@@ -274,16 +276,6 @@
 msgid "Keystone authentication token:"
 msgstr "Keystone-Authentifizierungs-Token:"
 
-#. Type: password
-#. Description
-#: ../designate-api.templates:6001
-msgid ""
-"To configure its endpoint in Keystone, designate-api needs the Keystone "
-"authentication token."
-msgstr ""
-"Um seine Endpunkte in 

Bug#859423:

[Tony Stoneley]

Completely out of my depth (and not really seeing why it should help),
I have nevertheless tried blacklisting the mga module on my system
also, but here it made no discernible difference. The system still hangs. 

Bug#859667: [Pkg-d-devel] Bug#859667: libundead: FTBFS on armhf and ppc64el: tests fail

[Iain Buclaw]

On 7 April 2017 at 16:02, Andreas Tille  wrote:
> On Wed, Apr 05, 2017 at 10:22:28PM +0200, Iain Buclaw wrote:
>> Which compiler?
>
> $ LANG=C apt-cache policy ldc
> ldc:
>   Installed: 1:1.1.1-1
>
>> Are NaNs being honoured?
>
> Hmmm, no idea how to check this.
>

Someone who maintains ldc might know. :-)

>> What if you were to replace
>> the `(x != x && f != f)` comparison with `(isNaN(x) && isNaN(f))` ?
>
> If I apply the following patch
>
> --- a/src/undead/stream.d
> +++ b/src/undead/stream.d
> @@ -1455,7 +1455,7 @@ class Stream : InputStream, OutputStream
>
>float f;
>assert(s.readf());
> -  assert(x == f || (x != x && f != f)); //either equal or both NaN
> +  assert(x == f || (isNaN(x) && isNaN(f))); //either equal or both NaN
>  }
>
>  tryFloatRoundtrip(1.0);
>
>
> I get
>
> ...
> [12/25] ldc2  '-Iundead_test@exe' '-I.' '-I..' '-I../src/' '-enable-color' 
> '-O' '-release' '-g' '-unittest'  -of 'undead_test@exe/src_undead_stream.d.o' 
> -c ../src/undead/stream.d
> FAILED: undead_test@exe/src_undead_stream.d.o
> ldc2  '-Iundead_test@exe' '-I.' '-I..' '-I../src/' '-enable-color' '-O' 
> '-release' '-g' '-unittest'  -of 'undead_test@exe/src_undead_stream.d.o' -c 
> ../src/undead/stream.d
> ../src/undead/stream.d(1458): Error: undefined identifier 'isNaN'
> ../src/undead/stream.d(1458): Error: undefined identifier 'isNaN'
>
>
> I have the feelingt that this meand "no" to your second question.
>

isNaN is from the std.math module.

http://dlang.org/phobos/std_math.html#.isNaN

You would need to import it. ;-)

Bug#859813: samba-vfs-modules: segfault after upgrade to 2:4.2.14+dfsg-0+deb8u4 with vfs_gluster (package rebuild from sources)

[Laurent Bardi]

Package: samba-vfs-modules
Version: 2:4.2.14+dfsg-0+deb8u5
Severity: normal

Dear Maintainer,

A)

I was using samba 2:4.2.10+dfsg-0+deb8u3


With the glusterfs package from glusterfs site
(https://download.gluster.org/pub/gluster/glusterfs/LTM-3.10/Debian/jessie/apt/
) gluster version 3.10 installed, i can do :

apt-get source samba
apt-get -y build-dep samba
cd sambaXXX
debuild -us -uc
# in order to have the vfs shared lib
install  via dpkg samba 4.2.10 and use for a share in smb.conf

kernel share modes = No
vfs objects = glusterfs
path = /%U
glusterfs:loglevel = 1
glusterfs:logfile = /var/log/samba/glusterfs-homes.log
glusterfs:volume = vnas_gluster_users

All fine;

B)
if i do this with samba 2:4.2.14+dfsg-0+deb8u5
smbd craches with :
[2017/04/07 11:15:04.003562,  0] ../source3/lib/dumpcore.c:318(dump_core)
  dumping core in /var/log/samba/cores/smbd
[2017/04/07 11:15:25.372344,  0]
.../source3/modules/vfs_glusterfs.c:257(vfs_gluster_connect)
  vnas_gluster_users: Initialized volume from server localhost
*** Error in `/usr/sbin/smbd': free(): invalid pointer: 0x7fdf8c79dd40 ***
[2017/04/07 11:15:25.375346,  0] ../lib/util/fault.c:78(fault_report)
  ===
[2017/04/07 11:15:25.375444,  0] ../lib/util/fault.c:79(fault_report)
  INTERNAL ERROR: Signal 6 in pid 13189 (4.2.14-Debian)
  Please read the Trouble-Shooting section of the Samba HOWTO
[2017/04/07 11:15:25.375501,  0] ../lib/util/fault.c:81(fault_report)
  ===
[2017/04/07 11:15:25.375535,  0] ../source3/lib/util.c:788(smb_panic_s3)
  PANIC (pid 13189): internal error
[2017/04/07 11:15:25.376597,  0] ../source3/lib/util.c:899(log_stack_trace)
  BACKTRACE: 31 stack frames:
   #0 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(log_stack_trace+0x1a)
[0x7fdf88a2ff8a]
   #1 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(smb_panic_s3+0x20)
[0x7fdf88a30070]
   #2 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(smb_panic+0x2f)
[0x7fdf8a6ebe5f]
   #3 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(+0x2407f) [0x7fdf8a6ec07f]
   #4 /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890) [0x7fdf8a90d890]
   #5 /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37) [0x7fdf870d7067]
   #6 /lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0x7fdf870d8448]
   #7 /lib/x86_64-linux-gnu/libc.so.6(+0x731b4) [0x7fdf871151b4]
   #8 /lib/x86_64-linux-gnu/libc.so.6(+0x7898e) [0x7fdf8711a98e]
   #9 /lib/x86_64-linux-gnu/libc.so.6(+0x79696) [0x7fdf8711b696]
   #10 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(+0x12b565)
[0x7fdf8a2be565]
   #11 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(+0x12c464)
[0x7fdf8a2bf464]
   #12 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(+0x12cf24)
[0x7fdf8a2bff24]
   #13 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(make_connection+0xf4)
[0x7fdf8a2c02f4]
   #14 /usr/lib/x86_64-linux-gnu/samba/libsmbd-
base.so.0(reply_tcon_and_X+0x65d) [0x7fdf8a26d22d]
   #15 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(+0x126953)
[0x7fdf8a2b9953]
   #16 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(+0x1286f2)
[0x7fdf8a2bb6f2]
   #17 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(+0x129e2d)
[0x7fdf8a2bce2d]
   #18 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(run_events_poll+0x171)
[0x7fdf88a503a1]
   #19 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(+0x4a617) [0x7fdf88a50617]
   #20 /usr/lib/x86_64-linux-gnu/libtevent.so.0(_tevent_loop_once+0x8d)
[0x7fdf8745143d]
   #21 /usr/lib/x86_64-linux-gnu/libtevent.so.0(tevent_common_loop_wait+0x1b)
[0x7fdf874515db]
   #22 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(smbd_process+0x718)
[0x7fdf8a2be188]
   #23 /usr/sbin/smbd(+0xadd0) [0x7fdf8ad48dd0]
   #24 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(run_events_poll+0x171)
[0x7fdf88a503a1]
   #25 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(+0x4a617) [0x7fdf88a50617]
   #26 /usr/lib/x86_64-linux-gnu/libtevent.so.0(_tevent_loop_once+0x8d)
[0x7fdf8745143d]
   #27 /usr/lib/x86_64-linux-gnu/libtevent.so.0(tevent_common_loop_wait+0x1b)
[0x7fdf874515db]
   #28 /usr/sbin/smbd(main+0x17e5) [0x7fdf8ad455e5]
   #29 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7fdf870c3b45]
   #30 /usr/sbin/smbd(+0x76e4) [0x7fdf8ad456e4]


I suspect it is like bug https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=858590















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

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

Versions of packages samba-vfs-modules depends on:
ii  libaio1 0.3.110-1
ii  libattr11:2.4.47-2
ii  libbsd0 0.7.0-2
ii  libc6   2.19-18+deb8u7
ii  libtalloc2  2.1.2-0+deb8u1
ii  libtdb1 1.3.6-0+deb8u1
ii  libtevent0  0.9.28-0+deb8u1
ii  samba-libs  2:4.2.14+dfsg-0+deb8u5

samba-vfs-modules 

Bug#859812: atom4: Exception: Unable to load tile pixmap from: (null)

[Andrew J. Buehler]

Package: atom4
Version: 4.1-7
Severity: grave

Dear Maintainer,

After upgrading atom4 following the fix for bug 859498, the package
files are now present.

However, when I attempt to launch the program, I get:

$ atom4
Exception: Unable to load tile pixmap from: (null)

An strace run reveals (among other things) that shortly before the
exception message is printed, the following call occurs:
open("debian/atom4/usr/share/games/atom4/tritile12.xpm", O_RDONLY) =
-1 ENOENT (No such file or directory)
which seems to indicate that the hardcoded pixmap paths in the built
executable are relative to the build directory, rather than pointing to
the location where the package actually installs those files. (strings
on the binary confirms that those paths are present there.) The file
/usr/share/games/atom4/tritile12.xpm does exist.

I am reporting this as grave, because I can't see how this can work on
any computer. If it does/can on some, please feel free to downgrade to
important.


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

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

Versions of packages atom4 depends on:
ii  libc62.24-9
ii  libgcc1  1:6.3.0-11
ii  libncurses5  6.0+20161126-1
ii  libstdc++6   6.3.0-11
ii  libtinfo56.0+20161126-1
ii  libx11-6 2:1.6.4-3
ii  libxpm4  1:3.5.12-1

atom4 recommends no packages.

atom4 suggests no packages.

-- debconf-show failed

Bug#859776: sponsorship-requests: vis/0.3 [ITP] -- A a modern and legacy free Vim-like text editor

[Paride Legovini]

On 2017-04-07 15:39, Adam Borowski wrote:
> On Fri, Apr 07, 2017 at 12:54:22PM +0200, Paride Legovini wrote:
>>  * Package name: vis
>>Version : 0.3
> 
>> It's my main editor, so I'm willing to keep the package well maintained and 
>> up
>> to date.
> 
> If, per the home page, it's not fully vi compatible, it can't be entirely
> bad :p  Let's see how it fares, especially with basic vi tests like no other
> way to exit it than kill -9 on another terminal. :)

Let's see :)

> I'm afraid I didn't get that far with review, though:
> 
> creating config.mk... done
> checking for pkg-config... no
> checking for libcurses...
>  checking for ncursesw... no
>  checking for ncurses... no
>  checking for libcurses... no
> ./configure: cannot find libcurses
> debian/rules:7: recipe for target 'override_dh_auto_configure' failed

Should be fixed now: I added a build-dependency to pkg-config.

> Also, the distribution is set to UNRELEASED.  For an actual upload (even if
> just to mentors if it's meant for sponsoring rather than review only),
> please change it to "unstable".

Done, thank you for your feedback.

Paride

Bug#859577: golang-github-syndtr-goleveldb-dev: file conflict with golang-goleveldb-dev

[Andreas Beckmann]

Followup-For: Bug #859577
Control: found -1 0.0~git20170302.0.3c5717c-3
Control: found -1 0.0~git20170302.0.3c5717c-2

Hi,

you are still missing 
  Breaks+Replaces: golang-goleveldb-dev (<< 0.0~git20170302.0.3c5717c)
to properly take over the files from the old package.


Andreas