Bug#880293: Pending fixes for bugs in the golang-github-fsouza-go-dockerclient package

[pkg-go-maintainers]

tag 880293 + pending
thanks

Some bugs in the golang-github-fsouza-go-dockerclient package are
closed in revision 7efea7e1c0c443d2abffd51efdec46579ef2f21a in branch
'master' by Michael Stapelberg

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-fsouza-go-dockerclient.git/commit/?id=7efea7e

Commit message:

fix FTBFS by applying upstream certificate update (Closes: #880293)

Bug#890356: lintian.d.o: maintainer reports (particular "full" ones) grows without bounds in size

[Niels Thykier]

Russ Allbery:
> Niels Thykier  writes:
> 
>> While these changes are impressive, a 20MB HTML file is still a pain to
>> load and process.
> 
> I agree that the page for pkg-perl-maintainers is probably not useful and
> probably not used by anyone.  But that's also an extreme outlier, I would
> assume?
>> I think my personal maintainer page is probably more typical.
> 


Data:
=
3645 out of 3708 reports are less than 1MB (A bit below 99% of all full
reports).  So far so good.  However, these 99% accounts for 202MB where
the last 1% accounts for 206 MB of the total size (i.e. the last 1% is
>= 50% of the disk usage).
  The regular maintainer reports also have this problem - just a much
narrower scope with 13 reports out of 3708 (<0.5%) and 22MB out of 103MB
(~21% rather than ~50%).

My take:

I am fine with saying that the full report is the current style full
report for the 99% percentile, but I am missing something for the last
1% (where the page is >= 1MB).
  I do not think it is reasonable that >= 25% (35%[1]) of the size of
the website is "dead waste no one could possible use for any purpose".

When I see something like the "privacy-breach-generic" in love-doc[2], I
cannot help but see it as "an unhelpful wall of text that no one can
comprehend".  That particular "wall" accounts for something 85% of the
visual part Miriam's report.  I think this report would go from "useless
to probably useful" if we clamped that wall, so the reader does not
drown in it (after the third "page-down" it just gets boring).


Note: I have used 1MB as the "pain threshold" (although ideally, I would
like the pages to be smaller than that).

Thanks,
~Niels

[1] Increases to 35% when we kill off the uncompressed log.

[2] https://lintian.debian.org/maintainer/mir...@debian.org.html#love

Bug#890360: RFP: vlc-plugin-bittorrent -- Bittorrent plugin for VLC

[Petter Reinholdtsen]

I created a proof of concept Debian package in the debian branch on
https://github.com/petterreinholdtsen/vlc-bittorrent >.  It
hardcodes the amd64 arch, but could serve as inspiration for a official
Debian package, which perhaps should be maintained as part of the Debian
multimedia team or on collab-maint, not github.

--
Happy hacking
Petter Reinholdtsen

Bug#890483: bind9: compile with dnstap support

[Richard James Salts]

Package: bind9
Version: 1:9.11.2.P1-1
Severity: wishlist
Tags: patch

It would be nice to enable the dnstap functionality included in bind
9.11 for detailed logging of dns queries going throught bind.
It would pull in extra dependencies on libfstrm0, libprotobuf-c1 and
zlib1g, however this might be worth it.

I've created a patch to the debian packaging that I used to compile
a deb with this option added. I think it's more or less correct.
diff -ur orig/debian/changelog diff/debian/changelog
--- orig/debian/changelog   2018-01-17 07:06:04.0 +0100
+++ diff/debian/changelog   2018-01-22 05:40:20.0 +0100
@@ -1,3 +1,9 @@
+bind9 (1:9.11.2.P1-1spectralmud1) unstable; urgency=medium
+
+  *  Compile with support for dnstap
+
+ -- Richard James Salts   Mon, 22 Jan 2018 
05:40:20 +0100
+
 bind9 (1:9.11.2.P1-1) unstable; urgency=medium
 
   * New upstream version 9.11.2-P1
diff -ur orig/debian/control diff/debian/control
--- orig/debian/control 2018-01-17 07:06:04.0 +0100
+++ diff/debian/control 2018-01-22 05:40:20.0 +0100
@@ -23,7 +23,9 @@
libtool,
libxml2-dev,
python3,
-   python3-ply
+   python3-ply,
+   protobuf-c-compiler,
+   libfstrm-dev
 Standards-Version: 4.1.2
 Vcs-Browser: https://anonscm.debian.org/git/pkg-dns/bind9.git
 Vcs-Git: git://anonscm.debian.org/git/pkg-dns/bind9.git
diff -ur orig/debian/dnsutils.install diff/debian/dnsutils.install
--- orig/debian/dnsutils.install2018-01-17 07:06:04.0 +0100
+++ diff/debian/dnsutils.install2018-01-22 05:39:12.0 +0100
@@ -3,8 +3,10 @@
 usr/bin/mdig
 usr/bin/nslookup
 usr/bin/nsupdate
+usr/bin/dnstap-read
 usr/share/man/man1/delv.1
 usr/share/man/man1/dig.1
 usr/share/man/man1/mdig.1
 usr/share/man/man1/nslookup.1
 usr/share/man/man1/nsupdate.1
+usr/share/man/man1/dnstap-read.1
diff -ur orig/debian/libdns169.symbols diff/debian/libdns169.symbols
--- orig/debian/libdns169.symbols   2018-01-17 07:06:04.0 +0100
+++ diff/debian/libdns169.symbols   2018-01-22 05:39:41.0 +0100
@@ -356,6 +356,21 @@
  dns_dsdigest_format@Base 1:9.10.6+dfsg
  dns_dsdigest_fromtext@Base 1:9.10.6+dfsg
  dns_dsdigest_totext@Base 1:9.10.6+dfsg
+ dns_dt_attach@Base 1:9.11.2+dfsg7
+ dns_dt_close@Base 1:9.11.2+dfsg
+ dns_dt_create@Base 1:9.11.2+dfsg
+ dns_dt_datatotext@Base 1:9.11.2+dfsg
+ dns_dt_detach@Base 1:9.11.2+dfsg
+ dns_dt_getframe@Base 1:9.11.2+dfsg
+ dns_dt_getstats@Base 1:9.11.2+dfsg
+ dns_dt_open@Base 1:9.11.2+dfsg
+ dns_dt_parse@Base 1:9.11.2+dfsg
+ dns_dt_reopen@Base 1:9.11.2+dfsg
+ dns_dt_send@Base 1:9.11.2+dfsg
+ dns_dt_setidentity@Base 1:9.11.2+dfsg
+ dns_dt_setversion@Base 1:9.11.2+dfsg
+ dns_dt_shutdown@Base 1:9.11.2+dfsg
+ dns_dtdata_free@Base 1:9.11.2+dfsg
  dns_dumpctx_attach@Base 1:9.10.6+dfsg
  dns_dumpctx_cancel@Base 1:9.10.6+dfsg
  dns_dumpctx_db@Base 1:9.10.6+dfsg
@@ -1407,6 +1422,24 @@
  dns_zt_loadnew@Base 1:9.10.6+dfsg
  dns_zt_mount@Base 1:9.10.6+dfsg
  dns_zt_unmount@Base 1:9.10.6+dfsg
+ dnstap__dnstap__descriptor@Base 1:9.11.2+dfsg
+ dnstap__dnstap__free_unpacked@Base 1:9.11.2+dfsg
+ dnstap__dnstap__get_packed_size@Base 1:9.11.2+dfsg
+ dnstap__dnstap__init@Base 1:9.11.2+dfsg
+ dnstap__dnstap__pack@Base 1:9.11.2+dfsg
+ dnstap__dnstap__pack_to_buffer@Base 1:9.11.2+dfsg
+ dnstap__dnstap__type__descriptor@Base 1:9.11.2+dfsg
+ dnstap__dnstap__unpack@Base 1:9.11.2+dfsg
+ dnstap__message__descriptor@Base 1:9.11.2+dfsg
+ dnstap__message__free_unpacked@Base 1:9.11.2+dfsg
+ dnstap__message__get_packed_size@Base 1:9.11.2+dfsg
+ dnstap__message__init@Base 1:9.11.2+dfsg
+ dnstap__message__pack@Base 1:9.11.2+dfsg
+ dnstap__message__pack_to_buffer@Base 1:9.11.2+dfsg
+ dnstap__message__type__descriptor@Base 1:9.11.2+dfsg
+ dnstap__message__unpack@Base 1:9.11.2+dfsg
+ dnstap__socket_family__descriptor@Base 1:9.11.2+dfsg
+ dnstap__socket_protocol__descriptor@Base 1:9.11.2+dfsg
  dst__entropy_getdata@Base 1:9.10.6+dfsg
  dst__entropy_status@Base 1:9.10.6+dfsg
  dst__gssapi_init@Base 1:9.10.6+dfsg
@@ -1883,6 +1916,21 @@
  dns_dsdigest_format@Base 1:9.10.6+dfsg
  dns_dsdigest_fromtext@Base 1:9.10.6+dfsg
  dns_dsdigest_totext@Base 1:9.10.6+dfsg
+ dns_dt_attach@Base 1:9.11.2+dfsg
+ dns_dt_close@Base 1:9.11.2+dfsg
+ dns_dt_create@Base 1:9.11.2+dfsg
+ dns_dt_datatotext@Base 1:9.11.2+dfsg
+ dns_dt_detach@Base 1:9.11.2+dfsg
+ dns_dt_getframe@Base 1:9.11.2+dfsg
+ dns_dt_getstats@Base 1:9.11.2+dfsg
+ dns_dt_open@Base 1:9.11.2+dfsg
+ dns_dt_parse@Base 1:9.11.2+dfsg
+ dns_dt_reopen@Base 1:9.11.2+dfsg
+ dns_dt_send@Base 1:9.11.2+dfsg
+ dns_dt_setidentity@Base 1:9.11.2+dfsg
+ dns_dt_setversion@Base 1:9.11.2+dfsg
+ dns_dt_shutdown@Base 1:9.11.2+dfsg
+ dns_dtdata_free@Base 1:9.11.2+dfsg
  dns_dumpctx_attach@Base 1:9.10.6+dfsg
  dns_dumpctx_cancel@Base 1:9.10.6+dfsg
  dns_dumpctx_db@Base 1:9.10.6+dfsg
@@ -2934,6 +2982,24 @@
  dns_zt_loadnew@Base 1:9.10.6+dfsg
  dns_zt_mount@Base 1:9.10.6+dfsg
  dns_zt_unmount@Ba

Bug#890482: mednaffe: Won't launch mednafen

[Nacho]

Package: mednaffe
Version: 0.8.4-1+b1
Severity: important

Dear Maintainer,

I'm having troubles launching the GUI for mednafen (mednaffe).
Whenever I launch mednaffe, an error prompt reports: "Error: Mednafen version 
is not compatible. You need 0.9.41 version or above.
But then, mednafen --version reports that the version installed from the 
stretch repository is 0.9.41.

I've tried also launching it from the commandline to see if there was an error 
preventing it from starting, but nothing to report there.

If you have the time, please check it.

Best Regards,

Nacho

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

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

Versions of packages mednaffe depends on:
ii  libc6   2.24-11+deb9u1
ii  libgdk-pixbuf2.0-0  2.36.5-2+deb9u2
ii  libglib2.0-02.50.3-2
ii  libgtk-3-0  3.22.11-1
ii  mednafen0.9.41+dfsg-2+b1

mednaffe recommends no packages.

mednaffe suggests no packages.

-- no debconf information

Bug#890480: RFS: groonga/8.0.0-1

[Kentaro Hayashi]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "groonga"

* Package name: groonga
  Version : 8.0.0-1
  Upstream Author : Groonga Project 
* Url : http://groonga.org/
* Licenses: LGPL-2.1
  Section : database

It builds those binary packages:

  * groonga
  * groonga-server-common
  * groonga-server-gqtp
  * libgroonga-dev
  * libgroonga0
  * groonga-tokenizer-mecab
  * groonga-token-filter-stem
  * groonga-plugin-suggest
  * groonga-bin
  * groonga-httpd
  * groonga-doc
  * groonga-examples
  * groonga-munin-plugins

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

https://mentors.debian.net/package/groonga

Alternatively, one can download the package with dget using this command:
dget -x 
https://mentors.debian.net/debian/pool/main/g/groonga/groonga_8.0.0-1.dsc


More information about groonga can be obtained from
http://groonga.org/

Changes since last upload:

  * New upstream release.


pgpU__1aQOmzu.pgp
Description: PGP signature

Bug#890481: RFS: fcitx-cloudpinyin/0.3.6-1

[Boyuan Yang]

Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: debian-input-met...@lists.debian.org

Dear mentors and debian-input-method members,

I am looking for a sponsor for team package "fcitx-cloudpinyin"

 * Package name: fcitx-cloudpinyin
   Version : 0.3.6-1
   Upstream Author : Weng Xuetian 
 * URL : https://github.com/fcitx/fcitx-cloudpinyin
 * License : GPL-2+
   Section : utils

  It builds those binary packages:

fcitx-module-cloudpinyin - Flexible Input Method Framework - cloudpinyin 
module

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

  https://mentors.debian.net/package/fcitx-cloudpinyin

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

dget -x 
https://mentors.debian.net/debian/pool/main/f/fcitx-cloudpinyin/fcitx-cloudpinyin_0.3.6-1.dsc

  Git packaging repository:

http://anonscm.debian.org/git/pkg-ime/fcitx-cloudpinyin.git

...and I'm looking for a DD to help migrate this repository to Salsa platform 
under
Debian group.

  Changes since the last upload:

 fcitx-cloudpinyin (0.3.6-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release.
   * Bump Standards-Version to 4.1.3.
   * Bump debhelper compat version to v11.
   * Remove trailing spaces in d/changelog and d/rules.
   * d/control: Use debian-input-method maillist in maintainer field.
   * d/control: Use Salsa platform in Vcs fields.
   * d/rules: Use "dh_missing --fail-missing".

--
Regards,
Boyuan Yang

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

Bug#890479: pytz can't find any time zones

[Evgeny Kapun]

Package: python3-tz
Version: 2018.3-1
Severity: grave

After upgrade to version 2018.3-1:

>>> import pytz
>>> pytz.all_timezones
[]

This is caused by this line in /usr/lib/python3/dist-packages/pytz/__init__.py:

filename = os.path.join('usr','share'
'zoneinfo', *name_parts)

So, instead of looking at /usr/share/zoneinfo/$time_zone_name, it is looking at 
(relative path) usr/sharezoneinfo/$time_zone_name (note the lack of comma after 
'share', which leads 'share' and 'zoneinfo' to be merged into a single string 
literal). This code is horribly broken, but it worked because it fell back to 
using time zone files bundled with the package. Now that these files are not 
included anymore (see bug #884079), this package doesn't work!

Bug#890473: Fix missing description in title

[Brett Johnson]

Control: retitle -1 ITP: lunarg-vulkan-tutorial -- LunarG Vulkan API
Samples Tutorial

Bug#890469: [Aptitude-devel] Bug#890469: aptitude: sometimes fails to resolve dependencies in a good way with '+' in the UI

[Vincent Lefevre]

On 2018-02-15 01:48:46 +0100, Axel Beckert wrote:
> Vincent Lefevre wrote:
> >   --\ Recommends (1)
> > --- stardict-gnome (>= 3.0.1-9.4) | stardict-gtk (>= 3.0.1-9.4)
[...]
> > This choice is surprising.
> 
> Not really. At that moment neither of the two alternative versioned
> dependencies are fulfilled, hence it tries to fulfill the first
> alternative dependency. The remainder seems to be a "local optimum"
> issue it doesn't find to escape itself in time. It probably will find
> the right solution later if you continue to request alternative
> dependency solutions with ".".

IMHO, when there is a OR'ed dependency, aptitude should first
consider already installed packages and see if an upgrade of
such a package would resolve the dependency, as this is what
the user would probably prefer. I also suppose that this is
what the user would obtain with full-upgrade.

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

Bug#890470: stretch-pu: package systemd/232-25+deb9u1

[Cyril Brulebois]

Hi Michael,

Michael Biebl  (2018-02-15):
> systemd (232-25+deb9u2) stretch; urgency=medium
> 
>   * networkd: Handle MTU field in IPv6 RA (Closes: #878162)
> 
> https://salsa.debian.org/systemd-team/systemd/commit/9f134218fa5ed60a4d7b0a2282d86ab56f52a3e9
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878162
> 
> It's a cherry-pick of an upstream commit which is already in
> unstable/testing.
> 
> This change was requested by Julien Cristau who already confirmed that
> it fixes the issue for stretch.

I'm not Julien. :)

> The changes don't affect the installer. That said I've CCed
> debian-boot for their ack.

Thanks; that looks fine to me on the d-i side, but I'd be happy to get a
ping when the package gets accepted into s-p-u, so that I have a chance
of triggering a few tests before it's point release time.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#890466: gcc isinf(1.0/0.0) fails on m68k

[Finn Thain]

On Sun, 11 Feb 2018, Jean-Michel Vourg?re wrote:

> Hi
> 
> Last build of rrdtool failed on m68k, because gcc IEEE stack pre-check fails 
> [1].
> 
> The autoconf runs this:
> 
> #include 
> int main(void){
>double rrdnan,rrdinf,rrdc,rrdzero;
>;
>/* some math to see if we get a floating point exception */
>rrdzero=sin(0.0); /* don't let the compiler optimize us away */
>rrdnan=0.0/rrdzero; /* especially here */
>rrdinf=1.0/rrdzero; /* and here. I want to know if it can do the magic */
> /* at run time without sig fpe */
>rrdc = rrdinf + rrdnan;
>rrdc = rrdinf / rrdnan;
>if (! isnan(rrdnan)) {printf ("not isnan(NaN) ... "); return 1;}
>if (rrdnan == rrdnan) {printf ("nan == nan ... "); return 1;}
>if (! isinf(rrdinf)) {printf ("not isinf(oo) ... "); return 1;}
>if (! isinf(-rrdinf)) {printf ("not isinf(-oo) ... "); return 1;}
>if (! rrdinf > 0) {printf ("not inf > 0 ... "); return 1;}
>if (! -rrdinf < 0) {printf ("not -inf < 0 ... "); return 1;}
>return 0;
> }
> 
> This returned 0 in previous builds [2], but now we get
> "not isinf(oo)"
> 
> I can't find anything changed upstream in these tests compared to last 
> successfull build.
> 
> Any ideas/thoughts?
> 

This seems to be a regression in Debian's C compiler. I came across a 
similar failure recently, which we found using the 'paranoia' floating 
point test suite from netlib.org.

The C version of 'paranoia' when run on a machine with physical 68882 
works fine when built with an old compiler. And the Fortran version 
(dpara.f) built with a recent f77 compiler also works fine on physical 
68882.

But recent Debian C compilers for m68k don't give the expected results.

BTW, it could be that running test suites on 680x0 emulators is 
contributing to the problem. For example, dpara.f under Qemu prints some 
weird output:

 Searching for overflow threshold:
 Can " z = -y " overflow?  trying it on  y =  -i.f^@^@^@^D^@^@^@E+00
 Seems O.K.
 Overflow threshold is  v =   1.79769313+308
 Overflow saturates at  sat =   i.f^@769313+308

I haven't tried this under Aranym.

[Jean-Michel, Stan, please note that there is a bug tracker entry for this 
issue now, #890466, Cc'd].

> 
> 
> [1] Last failed build:
> https://buildd.debian.org/status/fetch.php?
> pkg=rrdtool&arch=m68k&ver=1.7.0-1&stamp=1518247574&raw=0
> 
> [2] Previous build, sucessfull:
> https://buildd.debian.org/status/fetch.php?
> pkg=rrdtool&arch=m68k&ver=1.6.0-1%2Bb3&stamp=1500859583&raw=0

-- 

Bug#890478: pidof.8: Some corrections to the manual

[Bjarni Ingi Gislason]

Package: sysvinit-utils
Version: 2.88dsf-59.10
Severity: minor
Tags: patch

Dear Maintainer,

Test nr. 17: Start an empty line with ".sp 1".

84:

#

Test nr. 25: Find a repeated word

! 56 --> the
! 81 --> that   fixes bug #815 839 from 24 February 2016

#

Test nr. 27: Wrong distance between sentences or protect the indicator.

1) Separate the sentences; each begins on a new line.
See man-pages(7) and "info groff".

Or

2) Adjust space between sentences (two spaces),

3) or protect the indicator by adding "\&" after it.
The "indicator" is an "end-of-sentence character" (.!?).

35:finds the process id's (pids) of the named programs. It prints those
36:id's on the standard output. This program is on some systems used in
38:\fISystem-V\fP like \fIrc\fP structure. In that case these scripts are
39:located in /etc/rc?.d, where ? is the runlevel. If the system has
63:Tells \fIpidof\fP to omit processes with that process id. The special
78:should find the pid of, it is reasonably safe. Otherwise it is possible
80:as the program you're after but are actually other programs. Note that

#

  NO PATCH IS PROVIDED FOR THIS

Test nr. 29: Surround a block of comments with the macros ".ig" and "..".
The .\" at the beginning of each line is then not needed.

  Lines 2-17

#

Test nr. 33: Three periods for an ellipsis

28:.IR omitpid[,omitpid..] ]
30:.IR omitpid[,omitpid..].. ]
32:.RB [ program.. ]

#

  The patch:

--- pidof.8 2017-09-08 19:18:37.0 +
+++ pidof.8.new 2018-02-15 00:39:48.0 +
@@ -25,19 +25,19 @@ pidof -- find the process ID of a runnin
 .RB [ \-n ]
 .RB [ \-x ]
 .RB [ \-o
-.IR omitpid[,omitpid..] ]
-.RB [ \-o
-.IR omitpid[,omitpid..].. ]
+.IR omitpid [, omitpid "...] ]"
 .B program
-.RB [ program.. ]
+.RB [ program ...]
 .SH DESCRIPTION
 .B Pidof
-finds the process id's (pids) of the named programs. It prints those
-id's on the standard output. This program is on some systems used in
-run-level change scripts, especially when the system has a
-\fISystem-V\fP like \fIrc\fP structure. In that case these scripts are
-located in /etc/rc?.d, where ? is the runlevel. If the system has
-a
+finds the process id's (pids) of the named programs.
+It prints those id's on the standard output.
+This program is on some systems used in run-level change scripts,
+especially when the system has a \fISystem-V\fP like \fIrc\fP
+structure.
+In that case these scripts are located in /etc/rc?.d,
+where ? is the runlevel.
+If the system has a
 .B start-stop-daemon
 (8) program that should be used instead.
 .SH OPTIONS
@@ -53,16 +53,17 @@ Avoid
 system function call on all binaries which are located on network
 based file systems like
 .BR NFS .
-Instead of using this option the the variable
+Instead of using this option the variable
 .B PIDOF_NETFS
 may be set and exported.
 .IP \-x
 Scripts too - this causes the program to also return process id's of
 shells running the named scripts.
 .IP "-o \fIomitpid\fP"
-Tells \fIpidof\fP to omit processes with that process id. The special
-pid \fB%PPID\fP can be used to name the parent process of the \fIpidof\fP
-program, in other words the calling shell or shell script.
+Tells \fIpidof\fP to omit processes with that process id.
+The special pid \fB%PPID\fP can be used to name the parent process of
+the \fIpidof\fP program,
+in other words the calling shell or shell script.
 .SH "EXIT STATUS"
 .TP
 .B 0
@@ -75,13 +76,14 @@ No program was found with the requested
 the program behaves according to the name under which it is called.
 .PP
 When \fIpidof\fP is invoked with a full pathname to the program it
-should find the pid of, it is reasonably safe. Otherwise it is possible
-that it returns pids of running programs that happen to have the same name
-as the program you're after but are actually other programs. Note that
-that the executable name of running processes is calculated with
+should find the pid of, it is reasonably safe.
+Otherwise it is possible that it returns pids of running programs that
+happen to have the same name as the program you're after but are
+actually other programs.
+Note that the executable name of running processes is calculated with
 .BR readlink (2),
 so symbolic links to executables will also match.
-
+.sp 1
 .SH SEE ALSO
 .BR shutdown (8),
 .BR init (8),

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

Kernel: Linux 4.9.80-2 (SMP w/2 CPU cores)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE=is_IS.iso88591 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages sysvinit-utils depends on:
ii  init-system-helpers  1.51
ii  libc62.26-6
ii  util-linux   2.30.2-0.3

sysvinit-utils recommends no packages.

sysvinit-utils suggests no packages.

--

Bug#890477: ITP: lunarg-vulkan-sdk-docs -- LunarG Vulkan SDK Documentation

[Brett Johnson]

Package: wnpp
Severity: wishlist
Owner: Brett Johnson 

* Package name: lunarg-vulkan-sdk-docs
  Version : 1.0.68
  Upstream Author : LunarG Inc.
* URL : https://github.com/linuxturtle/lunarg-vulkan-sdk-docs
* License : Apache 2.0
  Description : LunarG Vulkan SDK Documentation

Various documentation provided by LunarG for the Vulkan API.  Includes the
current Vulkan specification, as well as the Vulkan API Reference Pages
from the Khronos Group. Also includes documentation regarding various
tools, layers, and example code provided by LunarG.

Bug#890476: ITP: lunarg-via -- LunarG Vulkan Installation Analyzer

[Brett Johnson]

Package: wnpp
Severity: wishlist
Owner: Brett Johnson 

* Package name: lunarg-via
  Version : 1.0.68
  Upstream Author : LunarG Inc
* URL : https://github.com/LunarG/VulkanTools
* License : Apache 2.0
  Programming Lang: C
  Description :  LunarG Vulkan Installation Analyzer

 VIA is a tool that can:
 1. Determine the state of Vulkan components on your system
 2. Validate that your Vulkan Loader and drivers are installed properly
 3. Capture your system state in a form that can be used as an attachment
when submitting bugs

Bug#890475: ITP: lunarg-vktrace -- LunarG vulkan API capture and replay tools

[Brett Johnson]

Package: wnpp
Severity: wishlist
Owner: Brett Johnson 

* Package name: lunarg-vktrace
  Version : 1.0.68
  Upstream Author : LunarG Inc
* URL : https://github.com/LunarG/VulkanTools
* License : Apache 2.0
  Programming Lang: C
  Description : LunarG vulkan API capture and replay tools

 This package contains the vktrace and vkreplay tools, used to capture and
 replay vulkan API calls from an application.

Bug#890474: ITP: lunarg-vulkan-layers -- Extra vulkan development layers from LunarG

[Brett Johnson]

Package: wnpp
Severity: wishlist
Owner: Brett Johnson 

* Package name: lunarg-vulkan-layers
  Version : 1.0.68
  Upstream Author : LunarG Inc
* URL : https://github.com/LunarG/VulkanTools
* License : Apache 2.0
  Programming Lang: C
  Description : Extra vulkan development layers from LunarG

 This package contains extra development layers for Vulkan from LunarG.
These
 include Api_dump, screenshot, device_simulation, and vktrace layers.

Bug#890473: ITP: lunarg-vulkan-tutorial

[Brett Johnson]

Package: wnpp
Severity: wishlist
Owner: Brett Johnson 

* Package name: lunarg-vulkan-tutorial
  Version : 1.0.68
  Upstream Author : LunarG Inc.
* URL : https://github.com/LunarG/VulkanSamples
* License : Apache 2.0
  Description : LunarG Vulkan API Samples Tutorial

 This tutorial is organized into sections that walk you through the steps to
 create a simple Vulkan program. Each tutorial section corresponds directly
to a
 sample program in the LunarG samples progression and is designed to be
read as
 you look at and experiment with real code from the progression.

Bug#890472: ITP: shaderc -- A collection of tools, libraries and tests for shader compilation

[Brett Johnson]

Package: wnpp
Severity: wishlist
Owner: Brett Johnson 

* Package name: shaderc
  Version : untagged
  Upstream Author : The Shaderc Authors (Google Inc)
* URL : https://github.com/google/shaderc
* License : Apache 2.0
  Programming Lang: C
  Description : A collection of tools, libraries and tests for shader
compilation

Shaderc wraps around core functionality in glslang and SPIRV-Tools.
 At the moment it includes:
 - glslc, a command line compiler for GLSL/HLSL to SPIR-V, and
 - libshaderc, a library API for doing the same.

Bug#890469: [Aptitude-devel] Bug#890469: aptitude: sometimes fails to resolve dependencies in a good way with '+' in the UI

[Axel Beckert]

Control: tag -1 + confirmed

Vincent Lefevre wrote:
> The immediate solution should be to type '+' over "utils/main".
> But this yields:
> 
>   --\ utils  Various system utilities (5)
> --\ main   The main Debian archive (5)
>   
> iuA stardict-common3.0.1-9.33.0.1-9.4 
>   
> iB  stardict-gtk -4096 B   3.0.1-9.33.0.1-9.4 
>   
> iuA stardict-plugin  -8192 B   3.0.1-9.33.0.1-9.4 
>   
> iuA stardict-plugin-espeak 3.0.1-9.33.0.1-9.4 
>   
> iuA stardict-plugin-festival   3.0.1-9.33.0.1-9.4 
>   
> 
> and for the broken stardict-gtk:
> 
> Some dependencies of stardict-gtk (broken, 3.0.1-9.3) are not satisfied:  
>  ▒
>   
>  ▒
>   * stardict-gtk (upgrade, 3.0.1-9.3 -> 3.0.1-9.4) conflicts with 
>  ▒
> stardict-gnome
>  ▒
>   
>  ▒
> The following packages conflict with stardict-gtk (broken, 3.0.1-9.3):
>  ▒
>   
>  ▒
>   * stardict-gnome (install, 3.0.1-9.4) conflicts with stardict-gtk   
>  ▒
> 
> Note that stardict-gnome is not currently installed. The problem is
> that aptitude chooses to install it, hence the conflict. The same
> problem occurs when I hit '+' over "stardict-common". I suspect
> that aptitude tries to upgrade one package after the other, with a
> suboptimal resolution of OR'ed dependencies: stardict-com 3.0.1-9.4
> has:
> 
>   --\ Recommends (1)
> --- stardict-gnome (>= 3.0.1-9.4) | stardict-gtk (>= 3.0.1-9.4)
> 
> So, when aptitude chooses to upgrade stardict-com, it wants
> to install stardict-gnome (not currently installed) instead
> of upgrading stardict-gtk.

Sounds familiar, yes. Happens occassionally, probably only if
versioned alternative dependencies in combination with conflicts are
involved. Which exists a bunch of times in Debian, but you probably
can count the cases on two hands.

(IMHO only a minor issue easy to workaround interactively, but I'll
leave it on normal and would like to hear Manuel's opinion on it.)

> This choice is surprising.

Not really. At that moment neither of the two alternative versioned
dependencies are fulfilled, hence it tries to fulfill the first
alternative dependency. The remainder seems to be a "local optimum"
issue it doesn't find to escape itself in time. It probably will find
the right solution later if you continue to request alternative
dependency solutions with ".".

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

Bug#890430: make: warning: -jN forced in submake: disabling jobserver mode.

[Manoj Srivastava]

Hi,

Unfortunately, the fix is not as simple as just  cherry-picking
 the related commit (there are earlier changes, and at least one part of
 the commit is later reverted).

Since we already have a RC bug on make, I’ll wait until there is
 a fix for that (since current HEAD reorganizes the source tree, which
 makes carrying patches ickier)

manoj
-- 
"Cogito ergo I'm right and you're wrong." Blair Houghton
Manoj Srivastava  
4096R/C5779A1C E37E 5EC5 2A01 DA25 AD20  05B6 CF48 9438 C577 9A1C


smime.p7s
Description: S/MIME cryptographic signature

Bug#890471: ITP: spirv-cross -- A tool for cross-compiling SPIR-V to other shader formats

[Brett Johnson]

Package: wnpp
Severity: wishlist
Owner: Brett Johnson 

* Package name: spirv-cross
  Version : untagged
  Upstream Author : Khronos Group
* URL : https://github.com/KhronosGroup/SPIRV-Cross
* License : Apache 2.0
  Programming Lang: C
  Description : A tool for cross-compiling SPIR-V to other shader formats

 SPIRV-Cross is a tool designed for parsing and converting SPIR-V to other
 shader languages.

 FEATURES:
 - Convert SPIR-V to readable, usable and efficient GLSL
 - Convert SPIR-V to readable, usable and efficient Metal Shading
Language (MSL) [EXPERIMENTAL]
 - Convert SPIR-V to readable, usable and efficient HLSL [EXPERIMENTAL]
 - Convert SPIR-V to debuggable C++ [EXPERIMENTAL]
 - Reflection API to simplify the creation of Vulkan pipeline layouts
 - Reflection API to modify and tweak OpDecorations
 - Supports "all" of vertex, fragment, tessellation, geometry and
compute shaders

Bug#890430: make: warning: -jN forced in submake: disabling jobserver mode.

[Manoj Srivastava]

Hi,

While you do not explicitly mention it, I suspect you have -jN
 specified in  MAKEFLAGS variable. his is a known issue in make 4.2.1;
 the fix is in upstream commit
 0c5a9f9b92af1634dc60fa21e9ac86ed50e5d595.

Please also see https://savannah.gnu.org/bugs/?48274

manoj
-- 
When asked, "If you find so much that is unworthy of reverence in the
United States, then why do you live here?" Mencken replied, "Why do men
go to zoos?"
Manoj Srivastava  
4096R/C5779A1C E37E 5EC5 2A01 DA25 AD20  05B6 CF48 9438 C577 9A1C


smime.p7s
Description: S/MIME cryptographic signature

Bug#890470: stretch-pu: package systemd/232-25+deb9u1

[Michael Biebl]

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

Hi,

I'd like to make a stable upload for systemd fixing a couple of issues.

An annotated changelog follows.
Full debdiff is attached.

systemd (232-25+deb9u2) stretch; urgency=medium

  * networkd: Handle MTU field in IPv6 RA (Closes: #878162)

https://salsa.debian.org/systemd-team/systemd/commit/9f134218fa5ed60a4d7b0a2282d86ab56f52a3e9
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878162

It's a cherry-pick of an upstream commit which is already in
unstable/testing.
This change was requested by Julien Cristau who already confirmed that it
fixes the issue for stretch.

  * shared: Add a linker script so that all functions are tagged @SD_SHARED
instead of @Base.
This helps prevent symbol collisions with other programs and libraries.
In particular, because PAM modules are loaded into the process that is
creating the session, and systemd creates PAM sessions, the potential
for collisions is high. (Closes: #873708)

https://salsa.debian.org/systemd-team/systemd/commit/bd33312f7fcf660f568bf2bac288b5ceec6981ab
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873708

It's a backport of an upstream commit which is already in
unstable/testing.

I'd consider this the most important fix, as we have seen segfaults in
systemd when e.g. libpam-heimdal was used.

  * resolved: Fix loop on packets with pseudo dns types.
CVE-2017-15908 (Closes: #880026)

https://salsa.debian.org/systemd-team/systemd/commit/5a469751160af8334ca4748ee00ee9b7e1a3efe3
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880026

It's a cherry-pick of an upstream commit which is already in
unstable/testing.
The security team suggested to fix this via a stable upload, as the
issue was not considered severe enough for a security upload (resolved
is not enabled by default in Debian)

  * machinectl: Don't output "No machines." with --no-legend option
(Closes: #880158)

https://salsa.debian.org/systemd-team/systemd/commit/9c22320c9d012bb515fb91752795fa4a6649dc5f
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880158

It's a cherry-pick of an upstream commit which is already in
unstable/testing.

The fix is trivial and has very low regression potential, so I decided
to include this patch as well. I'm fine with dropping it though, if you
have concerns.


The changes don't affect the installer. That said I've CCed debian-boot
for their ack.

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

Regards,
Michael

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

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

Bug#890447: www.debian.org: Reorganise /News/index page, and add info about other news channels (bits, micronews...)

[Paul Wise]

On Thu, Feb 15, 2018 at 4:40 AM, Laura Arjona Reina wrote:

> or https://micronews.debian.org";>micronews.debian.org

I would replace "micronews.debian.org" in the text with "Debian
micronews", since that is the title and heading on the micronews.d.o
site.

> which RSS-feeds the @debian profile in several social networks."

I wonder if we need to mention external social networks at all.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#890355: man: nroff: Bad system call

[Colin Watson]

On Wed, Feb 14, 2018 at 03:26:31AM +0100, Thorsten Glaser wrote:
> Hrm.…
> 
> > Sure, it’s attached, and it seems really weird…
> 
> … I had thought someone had defined NULL as just 0
> (although dalias makes a good argument for it) and
> it was passed as a too-short sentinel, but it uses
> execve, so that was not it.
> 
> But I see a lot of seccomp stuff in there, which,
> obviously, is not there when I just run it from the
> shell. Syscall numbers on x32 differ, so perhaps,
> that is already the culprit?

I have a feeling that this is basically another iteration of
https://bugs.debian.org/850047.  While building a system to test it,
though, I ran into apt's seccomp sandbox also being broken on x32 (very
likely for the same kind of reason), so I'm yak-shaving my way towards
this ...

-- 
Colin Watson   [cjwat...@debian.org]

Bug#890294: asymptote: complex eval-using code triggers assert failure

[Norbert Preining]

forwarded 890294 https://github.com/vectorgraphics/asymptote/issues/59
thanks

On Wed, 14 Feb 2018, kact...@gnu.org wrote:
> Yes, we definitely should send it upstream. You will do it, don't you?

Done now https://github.com/vectorgraphics/asymptote/issues/59

Norbert

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

Bug#890469: aptitude: sometimes fails to resolve dependencies in a good way with '+' in the UI

[Vincent Lefevre]

Package: aptitude
Version: 0.8.10-6
Severity: normal

Contrary to apt, aptitude sometimes fails to resolve dependencies
in a good way with '+' in the UI. Here's an example.

With the UI, I currently have:

  --\ utils  Various system utilities (5)
--\ main   The main Debian archive (5)
i A stardict-common3.0.1-9.33.0.1-9.4   

i   stardict-gtk   3.0.1-9.33.0.1-9.4
i A stardict-plugin3.0.1-9.33.0.1-9.4
i A stardict-plugin-espeak 3.0.1-9.33.0.1-9.4
i A stardict-plugin-festival   3.0.1-9.33.0.1-9.4

I wish to upgrade all these packages at once.

The immediate solution should be to type '+' over "utils/main".
But this yields:

  --\ utils  Various system utilities (5)
--\ main   The main Debian archive (5)  

iuA stardict-common3.0.1-9.33.0.1-9.4   

iB  stardict-gtk -4096 B   3.0.1-9.33.0.1-9.4   

iuA stardict-plugin  -8192 B   3.0.1-9.33.0.1-9.4   

iuA stardict-plugin-espeak 3.0.1-9.33.0.1-9.4   

iuA stardict-plugin-festival   3.0.1-9.33.0.1-9.4   


and for the broken stardict-gtk:

Some dependencies of stardict-gtk (broken, 3.0.1-9.3) are not satisfied:   ▒
   ▒
  * stardict-gtk (upgrade, 3.0.1-9.3 -> 3.0.1-9.4) conflicts with  ▒
stardict-gnome ▒
   ▒
The following packages conflict with stardict-gtk (broken, 3.0.1-9.3): ▒
   ▒
  * stardict-gnome (install, 3.0.1-9.4) conflicts with stardict-gtk▒

Note that stardict-gnome is not currently installed. The problem is
that aptitude chooses to install it, hence the conflict. The same
problem occurs when I hit '+' over "stardict-common". I suspect
that aptitude tries to upgrade one package after the other, with a
suboptimal resolution of OR'ed dependencies: stardict-com 3.0.1-9.4
has:

  --\ Recommends (1)
--- stardict-gnome (>= 3.0.1-9.4) | stardict-gtk (>= 3.0.1-9.4)

So, when aptitude chooses to upgrade stardict-com, it wants
to install stardict-gnome (not currently installed) instead
of upgrading stardict-gtk. This choice is surprising.

There is no such problem with apt when I choose to upgrade the
exactly same packages:

$ apt install -s stardict-common stardict-gtk stardict-plugin \
stardict-plugin-espeak stardict-plugin-festival
[...]
The following additional packages will be installed:
  libestools2.5
Suggested packages:
  ttf-freefont ttf-arphic-uming
The following NEW packages will be installed:
  libestools2.5
The following packages will be upgraded:
  stardict-common stardict-gtk stardict-plugin stardict-plugin-espeak
  stardict-plugin-festival
5 upgraded, 1 newly installed, 0 to remove and 34 not upgraded.
[...]

There is no such problem with aptitude either when I use 'U' instead
of '+' (except that here, 'U' will upgrade unrelated packages). So it
seems that the strategy for '+' is not as good as the one for 'U'.

-- Package-specific info:
Terminal: xterm-debian
$DISPLAY is set.
which aptitude: /usr/bin/aptitude

aptitude version information:
aptitude 0.8.10
Compiler: g++ 7.2.0
Compiled against:
  apt version 5.0.2
  NCurses version 6.0
  libsigc++ version: 2.10.0
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.1.20180127
  cwidget version: 0.5.17
  Apt version: 5.0.2

aptitude linkage:
linux-vdso.so.1 (0x7fff5499a000)
libgtk3-nocsd.so.0 => /usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0 
(0x7f037854a000)
libapt-pkg.so.5.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 
(0x7f037818b000)
libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 
(0x7f0377f5b000)
libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 
(0x7f0377d31000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7f0377b2a000)
libcwidget.so.3 => /usr/lib/x86_64-linux-gnu/libcwidget.so.3 
(0x7f0377832000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7f0377527000)
libboost_iostreams.so.1.62.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.62.0 (0x7f037730f000)
libboost_filesystem.so.1.62.0 => 
/usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.62.0 (0x7f03770f6000)
libboost_system.so.1.62.0 => 
/usr/lib/x86_64-linux-gnu/libboost_system.so.1.62.0 (0x7f0376ef2000)
libxapian.so.30

Bug#889932: salt-formula-kubernetes: FTBFS and Debci failure with salt 2017.7.2

[Benjamin Drung]

forwarded 889932 
https://github.com/salt-formulas/salt-formula-kubernetes/pull/12
thanks

Hi,

the build failure is caused by missing Python 3 support. I created a
upstream pull request and backported that commit for the Debian package.
An attached patch that I applied for the Ubuntu package is attached.

On Thu, 08 Feb 2018 23:08:57 +0200 Adrian Bunk  wrote:
> Source: salt-formula-kubernetes
> Version: 2016.12.1-1
> Severity: serious
> Tags: buster sid
> 
> https://ci.debian.net/packages/s/salt-formula-kubernetes/unstable/amd6
4/
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sal
t-formula-kubernetes.html
> 
> ...
>dh_auto_test
>   make -j15 test
> make[1]: Entering directory '/build/1st/salt-formula-kubernetes-
2016.12.1'
> [ ! -d tests ] || (cd tests; ./run_tests.sh)
> /usr/bin/salt-call
> [ERROR   ] Rendering exception occurred: Jinja variable
'salt.utils.odict.OrderedDict object' has no attribute 'iteritems'
> [CRITICAL] Rendering SLS 'base:kubernetes.master.controller' failed:
Jinja variable 'salt.utils.odict.OrderedDict object' has no attribute
'iteritems'
> [ERROR   ] Rendering exception occurred: Jinja variable
'salt.utils.odict.OrderedDict object' has no attribute 'iteritems'
> [CRITICAL] Rendering SLS 'base:kubernetes.master.setup' failed: Jinja
variable 'salt.utils.odict.OrderedDict object' has no attribute
'iteritems'
> local:
> - Rendering SLS 'base:kubernetes.master.controller' failed: Jinja
variable 'salt.utils.odict.OrderedDict object' has no attribute
'iteritems'
> - Rendering SLS 'base:kubernetes.master.setup' failed: Jinja
variable 'salt.utils.odict.OrderedDict object' has no attribute
'iteritems'
> [ERROR] Execution of kubernetes.master_cluster failed
> [ERROR] Execution failed
> Makefile:22: recipe for target 'test' failed
> make[1]: *** [test] Error 1
> 
> 
-- 
Benjamin Drung
Debian & Ubuntu Developerdiff -Nru salt-formula-kubernetes-2016.12.1/debian/changelog salt-formula-kubernetes-2016.12.1/debian/changelog
--- salt-formula-kubernetes-2016.12.1/debian/changelog	2016-12-25 17:05:59.0 +0100
+++ salt-formula-kubernetes-2016.12.1/debian/changelog	2018-02-15 00:34:06.0 +0100
@@ -1,3 +1,9 @@
+salt-formula-kubernetes (2016.12.1-1ubuntu1) bionic; urgency=medium
+
+  * Support Python 3 (Closes: #889932)
+
+ -- Benjamin Drung   Thu, 15 Feb 2018 00:34:06 +0100
+
 salt-formula-kubernetes (2016.12.1-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru salt-formula-kubernetes-2016.12.1/debian/control salt-formula-kubernetes-2016.12.1/debian/control
--- salt-formula-kubernetes-2016.12.1/debian/control	2016-11-21 16:06:19.0 +0100
+++ salt-formula-kubernetes-2016.12.1/debian/control	2018-02-15 00:34:06.0 +0100
@@ -1,5 +1,6 @@
 Source: salt-formula-kubernetes
-Maintainer: PKG OpenStack 
+Maintainer: Ubuntu Developers 
+XSBC-Original-Maintainer: PKG OpenStack 
 Uploaders: Filip Pytloun ,
Ondřej Nový ,
 Section: admin
diff -Nru salt-formula-kubernetes-2016.12.1/debian/patches/0001-Support-Python-3.patch salt-formula-kubernetes-2016.12.1/debian/patches/0001-Support-Python-3.patch
--- salt-formula-kubernetes-2016.12.1/debian/patches/0001-Support-Python-3.patch	1970-01-01 01:00:00.0 +0100
+++ salt-formula-kubernetes-2016.12.1/debian/patches/0001-Support-Python-3.patch	2018-02-15 00:34:06.0 +0100
@@ -0,0 +1,204 @@
+From 8af2fa9672fd2a3f0045465b24738206e8f8d552 Mon Sep 17 00:00:00 2001
+From: Benjamin Drung 
+Date: Thu, 15 Feb 2018 00:08:00 +0100
+Subject: [PATCH] Support Python 3
+
+Bug-Debian: https://bugs.debian.org/889932
+Forwarded: https://github.com/salt-formulas/salt-formula-kubernetes/pull/12
+---
+ kubernetes/control/configmap.sls   |  4 ++--
+ kubernetes/control/job.sls |  2 +-
+ kubernetes/control/role.sls|  4 ++--
+ kubernetes/control/service.sls |  4 ++--
+ kubernetes/files/basic_auth.csv|  2 +-
+ kubernetes/files/collectd_calico_bird.conf |  2 +-
+ kubernetes/files/configmap.yml |  2 +-
+ kubernetes/files/dockershim/default.master |  2 +-
+ kubernetes/files/dockershim/default.pool   |  2 +-
+ kubernetes/files/job.yml   |  6 +++---
+ kubernetes/files/known_tokens.csv  |  2 +-
+ kubernetes/files/kube-addons/dns/kubedns-rc.yaml   |  2 +-
+ kubernetes/files/kubelet/default.master|  2 +-
+ kubernetes/files/kubelet/default.pool  |  2 +-
+ kubernetes/files/manifest/kube-apiserver.manifest  |  2 +-
+ kubernetes/files/manifest/kube-controller-manager.manifest |  2 +-
+ kubernetes/files/manifest/kube-proxy.manifest.pool |  2 +-
+ kubernetes/files/manifest/kube-scheduler.manifest  |  2 +-
+ kubernetes/files/rc.yml|

Bug#888897: enigmail: please package recent 2.0x version of enigmail for experimental

[Daniel Kahn Gillmor]

Control: retitle 97 package 2.0.x version of enigmail for unstable

On Wed 2018-01-31 14:38:21 -0500, Daniel Kahn Gillmor wrote:
> enigmail 2.0.x embeds a minified version of OpenPGP.js split across the
> following two files:
>
>stdlib/openpgp-lib.js
>stdlib/openpgp.worker.min.js
>
> Those files are missing their source in the enigmail git repo, and i
> think the best DFSG way to handle that is to get the package available
> directly in debian (https://bugs.debian.org/787774).

having failed to make headway on the OpenPGP.js packaging yet, i've gone
ahead with an ugly workaround for now of shipping openpgp.js sources in
debian/missing-sources/.  I did this because i want it to be possible
for people to try enigmail and the newer thunderbird from debian
repositories for now.

fwiw, I don't think this is the Right Thing for inclusion in debian
unstable, and i won't be uploading enigmail to unstable until we've got
the rest of the openpgp.js packaging is sorted out, though.

I'm retitling this bug report to correspond to moving it to unstable.

i welcome any help on 787774.

--dkg


signature.asc
Description: PGP signature

Bug#889929: salt-formula-keyston: FTBFS and Debci failure with salt 2017.7.2

[Benjamin Drung]

forwarded 889929 https://github.com/salt-formulas/salt-formula-keystone/pull/21
thanks

Hi,

the build failure is caused by missing Python 3 support. I created a
upstream pull request and backported that commit for the Debian package.
An attached patch that I applied for the Ubuntu package is attached.

On Thu, 08 Feb 2018 23:05:23 +0200 Adrian Bunk  wrote:
> Source: salt-formula-keystone
> Version: 2016.12.1-1
> Severity: serious
> Tags: buster sid
> 
> https://ci.debian.net/packages/s/salt-formula-keystone/unstable/amd64/
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sal
t-formula-keystone.html
> 
> ...
>dh_auto_test
>   make -j15 test
> make[1]: Entering directory '/build/1st/salt-formula-keystone-
2016.12.1'
> [ ! -d tests ] || (cd tests; ./run_tests.sh)
> /usr/bin/salt-call
> [ERROR   ] Rendering exception occurred: Jinja variable 'dict object'
has no attribute 'iteritems'
> [CRITICAL] Rendering SLS 'base:keystone.server' failed: Jinja variable
'dict object' has no attribute 'iteritems'
> local:
> - Rendering SLS 'base:keystone.server' failed: Jinja variable
'dict object' has no attribute 'iteritems'
> [ERROR] Execution of keystone.cluster failed
> [ERROR] Execution failed
> Makefile:22: recipe for target 'test' failed
> make[1]: *** [test] Error 1
> 
> 
-- 
Benjamin Drung
Debian & Ubuntu Developerdiff -Nru salt-formula-keystone-2016.12.1/debian/changelog salt-formula-keystone-2016.12.1/debian/changelog
--- salt-formula-keystone-2016.12.1/debian/changelog	2016-12-25 17:05:55.0 +0100
+++ salt-formula-keystone-2016.12.1/debian/changelog	2018-02-15 00:32:55.0 +0100
@@ -1,3 +1,9 @@
+salt-formula-keystone (2016.12.1-1ubuntu1) bionic; urgency=medium
+
+  * Support Python 3 (Closes: #889929)
+
+ -- Benjamin Drung   Thu, 15 Feb 2018 00:32:55 +0100
+
 salt-formula-keystone (2016.12.1-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru salt-formula-keystone-2016.12.1/debian/control salt-formula-keystone-2016.12.1/debian/control
--- salt-formula-keystone-2016.12.1/debian/control	2016-11-21 15:56:04.0 +0100
+++ salt-formula-keystone-2016.12.1/debian/control	2018-02-15 00:32:55.0 +0100
@@ -1,5 +1,6 @@
 Source: salt-formula-keystone
-Maintainer: PKG OpenStack 
+Maintainer: Ubuntu Developers 
+XSBC-Original-Maintainer: PKG OpenStack 
 Uploaders: Filip Pytloun ,
Ondřej Nový ,
 Section: admin
diff -Nru salt-formula-keystone-2016.12.1/debian/patches/0001-Support-Python-3.patch salt-formula-keystone-2016.12.1/debian/patches/0001-Support-Python-3.patch
--- salt-formula-keystone-2016.12.1/debian/patches/0001-Support-Python-3.patch	1970-01-01 01:00:00.0 +0100
+++ salt-formula-keystone-2016.12.1/debian/patches/0001-Support-Python-3.patch	2018-02-15 00:32:55.0 +0100
@@ -0,0 +1,177 @@
+From 5fe8041e1b29c067fb38d8b98f6f7f5ef0b239c8 Mon Sep 17 00:00:00 2001
+From: Benjamin Drung 
+Date: Wed, 14 Feb 2018 23:55:54 +0100
+Subject: [PATCH] Support Python 3
+
+json.dumps() and yaml.safe_dump() return a str object on Python 2 and Python 3.
+Therefore the unicode conversion is only needed for Python 2.
+
+Bug-Debian: https://bugs.debian.org/889929
+Forwarded: https://github.com/salt-formulas/salt-formula-keystone/pull/21
+---
+ _modules/keystone_policy.py | 13 ++---
+ keystone/client/project.sls |  4 ++--
+ keystone/client/server.sls  | 10 +-
+ keystone/control.sls|  2 +-
+ keystone/files/kilo/keystone.conf.Debian|  2 +-
+ keystone/files/liberty/keystone.conf.Debian |  2 +-
+ keystone/files/mitaka/keystone.conf.Debian  |  6 +++---
+ keystone/files/newton/keystone.conf.Debian  |  6 +++---
+ keystone/files/ocata/keystone.conf.Debian   |  6 +++---
+ keystone/files/ocata/keystone.conf.RedHat   |  6 +++---
+ keystone/files/pike/keystone.conf.Debian|  6 +++---
+ keystone/files/pike/keystone.conf.RedHat|  6 +++---
+ keystone/meta/salt.yml  |  2 +-
+ keystone/meta/sphinx.yml|  2 +-
+ keystone/server.sls | 10 +-
+ 15 files changed, 45 insertions(+), 38 deletions(-)
+
+--- a/keystone/client/project.sls
 b/keystone/client/project.sls
+@@ -20,7 +20,7 @@
+   - require:
+ - file: keystone_salt_config
+ 
+-{%- for tenant_name, tenant in client.get('tenant', {}).iteritems() %}
++{%- for tenant_name, tenant in client.get('tenant', {}).items() %}
+ 
+ keystone_tenant_{{ tenant_name }}:
+   keystone.tenant_present:
+@@ -32,7 +32,7 @@
+   - require:
+ - keystone: keystone_client_roles
+ 
+-{%- for user_name, user in tenant.get('user', {}).iteritems() %}
++{%- for user_name, user in tenant.get('user', {}).items() %}
+ 
+ keystone_{{ tenant_name }}_user_{{ user_name }}:
+   keystone.user_present:
+--- a/keystone/client/server.sls
 b/keystone/client/server.sls
+@@ -1,7 +1,7 @@
+ {%- from "keystone/map.jinja" import client with context %}
+ {%- if client.enabled %}
+

Bug#889933: salt-formula-glance: FTBFS and Debci failure with salt 2017.7.2

[Benjamin Drung]

forwarded 889933 https://github.com/salt-formulas/salt-formula-glance/pull/23
thanks

Hi,

the build failure is caused by missing Python 3 support. I created a
upstream pull request and backported that commit for the Debian package.
An attached patch that I applied for the Ubuntu package is attached.

On Thu, 08 Feb 2018 23:10:25 +0200 Adrian Bunk  wrote:
> Source: salt-formula-glance
> Version: 2016.12.1-1
> Severity: serious
> Tags: buster sid
> 
> https://ci.debian.net/packages/s/salt-formula-glance/unstable/amd64/
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sal
t-formula-glance.html
> 
> ...
>dh_auto_test
>   make -j15 test
> make[1]: Entering directory '/build/1st/salt-formula-glance-2016.12.1'
> [ ! -d tests ] || (cd tests; ./run_tests.sh)
> /usr/bin/salt-call
> [WARNING ] Failed to open log file, do you have permission to write to
/var/log/salt/minion?
> [ERROR   ] Rendering exception occurred: Jinja variable 'dict object'
has no attribute 'iteritems'
> [CRITICAL] Rendering SLS 'base:glance.server' failed: Jinja variable
'dict object' has no attribute 'iteritems'
> local:
> - Rendering SLS 'base:glance.server' failed: Jinja variable 'dict
object' has no attribute 'iteritems'
> [ERROR] Execution of glance.cluster failed
> [ERROR] Execution failed
> Makefile:22: recipe for target 'test' failed
> make[1]: *** [test] Error 1
> 
> 
-- 
Benjamin Drung
Debian & Ubuntu Developerdiff -Nru salt-formula-glance-2016.12.1/debian/changelog salt-formula-glance-2016.12.1/debian/changelog
--- salt-formula-glance-2016.12.1/debian/changelog	2016-12-25 17:05:47.0 +0100
+++ salt-formula-glance-2016.12.1/debian/changelog	2018-02-15 00:30:56.0 +0100
@@ -1,3 +1,9 @@
+salt-formula-glance (2016.12.1-1ubuntu1) bionic; urgency=medium
+
+  * Support Python 3 (Closes: #889933)
+
+ -- Benjamin Drung   Thu, 15 Feb 2018 00:30:56 +0100
+
 salt-formula-glance (2016.12.1-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru salt-formula-glance-2016.12.1/debian/control salt-formula-glance-2016.12.1/debian/control
--- salt-formula-glance-2016.12.1/debian/control	2016-11-21 15:55:48.0 +0100
+++ salt-formula-glance-2016.12.1/debian/control	2018-02-15 00:30:56.0 +0100
@@ -1,5 +1,6 @@
 Source: salt-formula-glance
-Maintainer: PKG OpenStack 
+Maintainer: Ubuntu Developers 
+XSBC-Original-Maintainer: PKG OpenStack 
 Uploaders: Filip Pytloun ,
Ondřej Nový ,
 Section: admin
diff -Nru salt-formula-glance-2016.12.1/debian/patches/0001-Support-Python-3.patch salt-formula-glance-2016.12.1/debian/patches/0001-Support-Python-3.patch
--- salt-formula-glance-2016.12.1/debian/patches/0001-Support-Python-3.patch	1970-01-01 01:00:00.0 +0100
+++ salt-formula-glance-2016.12.1/debian/patches/0001-Support-Python-3.patch	2018-02-15 00:30:56.0 +0100
@@ -0,0 +1,34 @@
+From 35de76452ffa540decd2b158bb33a42cebf3314d Mon Sep 17 00:00:00 2001
+From: Benjamin Drung 
+Date: Wed, 14 Feb 2018 23:54:30 +0100
+Subject: [PATCH] Support Python 3
+
+Bug-Debian: https://bugs.debian.org/889933
+Forwarded: https://github.com/salt-formulas/salt-formula-glance/pull/23
+---
+ _states/glanceng.py| 2 +-
+ glance/client.sls  | 4 ++--
+ glance/files/_backends/_swift.conf | 2 +-
+ glance/server.sls  | 4 ++--
+ 4 files changed, 6 insertions(+), 6 deletions(-)
+
+--- a/glance/server.sls
 b/glance/server.sls
+@@ -121,7 +121,7 @@
+ 
+ {%- endfor %}
+ 
+-{%- for image_name, image in server.get('image', {}).iteritems() %}
++{%- for image_name, image in server.get('image', {}).items() %}
+ 
+ glance_download_{{ image_name }}:
+   cmd.run:
+@@ -144,7 +144,7 @@
+ 
+ {%- if server.policy is defined %}
+ 
+-{%- for key, policy in server.policy.iteritems() %}
++{%- for key, policy in server.policy.items() %}
+ 
+ policy_{{ key }}:
+   file.replace:
diff -Nru salt-formula-glance-2016.12.1/debian/patches/series salt-formula-glance-2016.12.1/debian/patches/series
--- salt-formula-glance-2016.12.1/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ salt-formula-glance-2016.12.1/debian/patches/series	2018-02-15 00:30:35.0 +0100
@@ -0,0 +1 @@
+0001-Support-Python-3.patch

Bug#889927: salt-formula-ceilometer: FTBFS and Debci failure with salt 2017.7.2

[Benjamin Drung]

forwarded 889927 https://github.com/salt-formulas/salt-formula-ceilometer/pull/6
thanks

Hi,

the build failure is caused by missing Python 3 support. I created a
upstream pull request and backported that commit for the Debian package.
An attached patch that I applied for the Ubuntu package is attached.

On Thu, 08 Feb 2018 22:58:19 +0200 Adrian Bunk  wrote:
> Source: salt-formula-ceilometer
> Version: 2016.12.1-1
> Severity: serious
> Tags: buster sid
> 
> https://ci.debian.net/packages/s/salt-formula-ceilometer/unstable/amd6
4/
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sal
t-formula-ceilometer.html
> 
> ...
>dh_auto_test
>   make -j15 test
> make[1]: Entering directory '/build/1st/salt-formula-ceilometer-
2016.12.1'
> [ ! -d tests ] || (cd tests; ./run_tests.sh)
> /usr/bin/salt-call
> [ERROR   ] Rendering exception occurred: Jinja variable
'salt.utils.odict.OrderedDict object' has no attribute 'iteritems'
> [CRITICAL] Rendering SLS 'base:ceilometer.agent' failed: Jinja
variable 'salt.utils.odict.OrderedDict object' has no attribute
'iteritems'
> local:
> - Rendering SLS 'base:ceilometer.agent' failed: Jinja variable
'salt.utils.odict.OrderedDict object' has no attribute 'iteritems'
> [ERROR] Execution of ceilometer.agent_cluster failed
> [ERROR] Execution failed
> Makefile:22: recipe for target 'test' failed
> make[1]: *** [test] Error 1
> 
> 
-- 
Benjamin Drung
Debian & Ubuntu Developerdiff -Nru salt-formula-ceilometer-2016.12.1/debian/changelog salt-formula-ceilometer-2016.12.1/debian/changelog
--- salt-formula-ceilometer-2016.12.1/debian/changelog	2016-12-25 17:05:26.0 +0100
+++ salt-formula-ceilometer-2016.12.1/debian/changelog	2018-02-15 00:18:13.0 +0100
@@ -1,3 +1,9 @@
+salt-formula-ceilometer (2016.12.1-1ubuntu1) bionic; urgency=medium
+
+  * Support Python 3 (Closes: #889927)
+
+ -- Benjamin Drung   Thu, 15 Feb 2018 00:18:13 +0100
+
 salt-formula-ceilometer (2016.12.1-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru salt-formula-ceilometer-2016.12.1/debian/control salt-formula-ceilometer-2016.12.1/debian/control
--- salt-formula-ceilometer-2016.12.1/debian/control	2016-11-21 15:55:36.0 +0100
+++ salt-formula-ceilometer-2016.12.1/debian/control	2018-02-15 00:18:13.0 +0100
@@ -1,5 +1,6 @@
 Source: salt-formula-ceilometer
-Maintainer: PKG OpenStack 
+Maintainer: Ubuntu Developers 
+XSBC-Original-Maintainer: PKG OpenStack 
 Uploaders: Filip Pytloun ,
Ondřej Nový ,
 Section: admin
diff -Nru salt-formula-ceilometer-2016.12.1/debian/patches/0001-Support-Python-3.patch salt-formula-ceilometer-2016.12.1/debian/patches/0001-Support-Python-3.patch
--- salt-formula-ceilometer-2016.12.1/debian/patches/0001-Support-Python-3.patch	1970-01-01 01:00:00.0 +0100
+++ salt-formula-ceilometer-2016.12.1/debian/patches/0001-Support-Python-3.patch	2018-02-15 00:18:13.0 +0100
@@ -0,0 +1,227 @@
+From d473ad28bc38e2152f77c8b50133e65e458776d1 Mon Sep 17 00:00:00 2001
+From: Benjamin Drung 
+Date: Tue, 13 Feb 2018 23:39:58 +0100
+Subject: [PATCH] Support Python 3
+
+Bug-Debian: https://bugs.debian.org/889927
+Forwarded: https://github.com/salt-formulas/salt-formula-ceilometer/pull/6
+---
+ ceilometer/agent.sls   | 2 +-
+ ceilometer/files/juno/ceilometer-server.conf.Debian| 2 +-
+ ceilometer/files/juno/pipeline.yaml| 8 
+ ceilometer/files/kilo/ceilometer-server.conf.Debian| 2 +-
+ ceilometer/files/kilo/pipeline.yaml| 8 
+ ceilometer/files/liberty/ceilometer-server.conf.Debian | 2 +-
+ ceilometer/files/liberty/pipeline.yaml | 8 
+ ceilometer/files/mitaka/ceilometer-server.conf.Debian  | 2 +-
+ ceilometer/files/mitaka/compute_pipeline.yaml  | 2 +-
+ ceilometer/files/mitaka/pipeline.yaml  | 2 +-
+ ceilometer/files/newton/compute_pipeline.yaml  | 2 +-
+ ceilometer/files/newton/pipeline.yaml  | 2 +-
+ ceilometer/files/ocata/compute_pipeline.yaml   | 2 +-
+ ceilometer/files/ocata/pipeline.yaml   | 2 +-
+ ceilometer/server.sls  | 4 ++--
+ 15 files changed, 25 insertions(+), 25 deletions(-)
+
+--- a/ceilometer/agent.sls
 b/ceilometer/agent.sls
+@@ -12,7 +12,7 @@
+   - require:
+ - pkg: ceilometer_agent_packages
+ 
+-{%- for publisher_name, publisher in agent.get('publisher', {}).iteritems() %}
++{%- for publisher_name, publisher in agent.get('publisher', {}).items() %}
+ 
+ {%- if publisher_name != "default" %}
+ 
+--- a/ceilometer/files/juno/ceilometer-server.conf.Debian
 b/ceilometer/files/juno/ceilometer-server.conf.Debian
+@@ -928,7 +928,7 @@
+ #metering_secret=change this or be hacked
+ metering_secret={{ server.secret }}
+ 
+-{%- for publisher_name, publisher in server.get('publisher', {}).iteritems() %}
++{%- for publisher_name, publisher in server.get('publisher', {}).items() %}
+ 

Bug#889928: salt-formula-cinder: FTBFS and Debci failure with salt 2017.7.2

[Benjamin Drung]

forwarded 889928 https://github.com/salt-formulas/salt-formula-cinder/pull/23
thanks

Hi,

the build failure is caused by missing Python 3 support. I created a
upstream pull request and backported that commit for the Debian package.
An attached patch that I applied for the Ubuntu package is attached.

On Thu, 08 Feb 2018 23:03:43 +0200 Adrian Bunk  wrote:
> Source: salt-formula-cinder
> Version: 2016.12.1-1
> Severity: serious
> 
> https://ci.debian.net/packages/s/salt-formula-cinder/unstable/amd64/
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sal
t-formula-cinder.html
> 
> ...
>dh_auto_test
>   make -j15 test
> make[1]: Entering directory '/build/1st/salt-formula-cinder-2016.12.1'
> [ ! -d tests ] || (cd tests; ./run_tests.sh)
> /usr/bin/salt-call
> [WARNING ] Failed to open log file, do you have permission to write to
/var/log/salt/minion?
> [ERROR   ] Rendering exception occurred: Jinja variable
'salt.utils.odict.OrderedDict object' has no attribute 'iteritems'
> [CRITICAL] Rendering SLS 'base:cinder.controller' failed: Jinja
variable 'salt.utils.odict.OrderedDict object' has no attribute
'iteritems'
> [ERROR   ] Rendering exception occurred: Jinja variable
'salt.utils.odict.OrderedDict object' has no attribute 'iteritems'
> [CRITICAL] Rendering SLS 'base:cinder.volume' failed: Jinja variable
'salt.utils.odict.OrderedDict object' has no attribute 'iteritems'
> local:
> - Rendering SLS 'base:cinder.controller' failed: Jinja variable
'salt.utils.odict.OrderedDict object' has no attribute 'iteritems'
> - Rendering SLS 'base:cinder.volume' failed: Jinja variable
'salt.utils.odict.OrderedDict object' has no attribute 'iteritems'
> [ERROR] Execution of cinder.ceph_single failed
> [ERROR] Execution failed
> Makefile:22: recipe for target 'test' failed
> make[1]: *** [test] Error 1
> 
> 
-- 
Benjamin Drung
Debian & Ubuntu Developerdiff -Nru salt-formula-cinder-2016.12.1/debian/changelog salt-formula-cinder-2016.12.1/debian/changelog
--- salt-formula-cinder-2016.12.1/debian/changelog	2016-12-25 17:05:43.0 +0100
+++ salt-formula-cinder-2016.12.1/debian/changelog	2018-02-15 00:25:17.0 +0100
@@ -1,3 +1,9 @@
+salt-formula-cinder (2016.12.1-1ubuntu1) bionic; urgency=medium
+
+  * Support Python 3 (Closes: #889928)
+
+ -- Benjamin Drung   Thu, 15 Feb 2018 00:25:17 +0100
+
 salt-formula-cinder (2016.12.1-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru salt-formula-cinder-2016.12.1/debian/control salt-formula-cinder-2016.12.1/debian/control
--- salt-formula-cinder-2016.12.1/debian/control	2016-11-21 15:55:43.0 +0100
+++ salt-formula-cinder-2016.12.1/debian/control	2018-02-15 00:25:17.0 +0100
@@ -1,5 +1,6 @@
 Source: salt-formula-cinder
-Maintainer: PKG OpenStack 
+Maintainer: Ubuntu Developers 
+XSBC-Original-Maintainer: PKG OpenStack 
 Uploaders: Filip Pytloun ,
Ondřej Nový ,
 Section: admin
diff -Nru salt-formula-cinder-2016.12.1/debian/patches/0001-Support-Python-3.patch salt-formula-cinder-2016.12.1/debian/patches/0001-Support-Python-3.patch
--- salt-formula-cinder-2016.12.1/debian/patches/0001-Support-Python-3.patch	1970-01-01 01:00:00.0 +0100
+++ salt-formula-cinder-2016.12.1/debian/patches/0001-Support-Python-3.patch	2018-02-15 00:25:17.0 +0100
@@ -0,0 +1,270 @@
+From c5ea00cd7379b8a1dfcdc224c4a8de81553a8f28 Mon Sep 17 00:00:00 2001
+From: Benjamin Drung 
+Date: Wed, 14 Feb 2018 23:44:07 +0100
+Subject: [PATCH] Support Python 3
+
+Bug-Debian: https://bugs.debian.org/889928
+Forwarded: https://github.com/salt-formulas/salt-formula-cinder/pull/23
+---
+ cinder/client.sls  | 4 ++--
+ cinder/controller.sls  | 4 ++--
+ cinder/files/juno/cinder.conf.controller.Debian| 4 ++--
+ cinder/files/juno/cinder.conf.volume.Debian| 4 ++--
+ cinder/files/kilo/cinder.conf.controller.Debian| 4 ++--
+ cinder/files/kilo/cinder.conf.volume.Debian| 4 ++--
+ cinder/files/liberty/cinder.conf.controller.Debian | 4 ++--
+ cinder/files/liberty/cinder.conf.volume.Debian | 4 ++--
+ cinder/files/mitaka/cinder.conf.controller.Debian  | 4 ++--
+ cinder/files/mitaka/cinder.conf.volume.Debian  | 4 ++--
+ cinder/files/newton/cinder.conf.controller.Debian  | 4 ++--
+ cinder/files/newton/cinder.conf.volume.Debian  | 4 ++--
+ cinder/files/ocata/cinder.conf.controller.Debian   | 4 ++--
+ cinder/files/ocata/cinder.conf.volume.Debian   | 4 ++--
+ cinder/files/pike/cinder.conf.controller.Debian| 4 ++--
+ cinder/files/pike/cinder.conf.volume.Debian| 4 ++--
+ cinder/meta/sphinx.yml | 4 ++--
+ cinder/volume.sls  | 2 +-
+ 18 files changed, 35 insertions(+), 35 deletions(-)
+
+--- a/cinder/controller.sls
 b/cinder/controller.sls
+@@ -51,7 +51,7 @@
+ 
+ {# new way #}
+ 
+-{%- for backend_name, backend in controller.get('backend', {}).iteritems() %}
++{%- for backend_name, b

Bug#890364: pybind11-dev: Request migration to unstable

[Shane Loretz]

Hi Ghis,

Thank you!

What is the likelihood of migration before March 1st (date of ubuntu Bionic
Debian import freeze)?


Cheers,
Shane

On Wed, Feb 14, 2018 at 1:34 AM, Ghislain Vaillant 
wrote:

> Hi Shane, thanks for reaching out,
>
> On Wed, 14 Feb 2018 00:48:14 + Shane Loretz  rg> wrote:
> > Would the maintainer be willing to migrate 2.2.1 from experimental to
> unstable? I'm a user of a distribution based on debian unstable. I have
> been using pybind11 from pip previously. The package in experimental
> appears to be working flawlessly for my usecase and has some nice new
> features not in the version currently in unstable.
>
> There are a few rdpends I have got to test first to guarantee a smooth
> upgrade. But yes, I intend to migrate the new version to unstable soon.
>
> Cheers,
> Ghis
>

Bug#890406: linux-image-4.14.0-0.bpo.3-amd64: Installing kernel fails to build broadcom-sta

[Ben Hutchings]

On Wed, 2018-02-14 at 20:19 +0100, Steve wrote:
> Hi,
> 
> Le 14-02-2018, à 18:52:16 +, Ben Hutchings a écrit :
> 
> > If an external module is not compatible with a new kernel version, that
> > is not a bug in the new kernel version.
> 
> Which I perfectly understand. 
> 
> But as a user, I'm stuck with a broken system (no wireless) after
> choosing to update my kernel by regular means. What should be my next
> steps?

Boot the old kernel version.

Ben.

> > As it happens, this has just been fixed in a new version of
> > broadcom-sta in unstable.
> 
> Good to hear that. I'll give it a try even though I'm running stable.
> 
> Thanks for the quick answer.
> 
> Steve
-- 
Ben Hutchings
Beware of programmers who carry screwdrivers. - Leonard Brandwein



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

Bug#890468: lintian: source-is-missing false positive when d/missing-sources/foo is a symlink

[Daniel Kahn Gillmor]

Package: lintian
Version: 2.5.75
Severity: normal

consider a package whose upstream ships two binaries, ./foo and ./bar

those two binaries are generated from the same source code, perhaps
compiled in different ways (in my silly example, "make foo" and "make
bar" apply different build flags to the same source tree)

a reasonable configuration for the debian repository is:

  debian/missing-sources/bar/
  debian/missing-sources/bar/Makefile
  debian/missing-sources/bar/main.c
  debian/missing-sources/foo → bar

However, in this case, lintian will complain with:

 package: source-is-missing foo

It doesn't make sense to encourage the package maintainer to ship two
copies of the same source.

   --dkg

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

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

Versions of packages lintian depends on:
ii  binutils  2.30-4
ii  bzip2 1.0.6-8.1
ii  diffstat  1.61-1+b1
ii  dpkg  1.19.0.5
ii  file  1:5.32-1
ii  gettext   0.19.8.1-4
ii  intltool-debian   0.35.0+20060710.4
ii  libapt-pkg-perl   0.1.33
ii  libarchive-zip-perl   1.60-1
ii  libclass-accessor-perl0.51-1
ii  libclone-perl 0.39-1
ii  libdpkg-perl  1.19.0.5
ii  libemail-valid-perl   1.202-1
ii  libfile-basedir-perl  0.07-1
ii  libipc-run-perl   0.96-1
ii  liblist-moreutils-perl0.416-1+b3
ii  libparse-debianchangelog-perl 1.2.0-12
ii  libperl5.24 [libdigest-sha-perl]  5.24.1-7
ii  libperl5.26 [libdigest-sha-perl]  5.26.1-4
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.73-1
ii  libxml-simple-perl2.24-1
ii  libyaml-libyaml-perl  0.69+repack-1
ii  man-db2.7.6.1-4
ii  patchutils0.3.4-2
ii  perl  5.26.1-4
ii  t1utils   1.41-2
ii  xz-utils  5.2.2-1.3

Versions of packages lintian recommends:
pn  libperlio-gzip-perl  

Versions of packages lintian suggests:
pn  binutils-multiarch 
ii  dpkg-dev   1.19.0.5
ii  libhtml-parser-perl3.72-3+b2
ii  libtext-template-perl  1.47-1

-- no debconf information

Bug#890467: sssd: upgrade from 1.16.0-3 to 1.16.0-5 causes total failure of sssd to work, can not log into machine

[Daniel Lakeland]

Package: sssd
Version: 1.16.0-3
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

   * What led up to the situation?

I had a working system with sssd providing my users and authentication
using an openldap and kerberos backend. I upgraded from 1.16.0-3 to
1.16.0-5 and the system could not find any users or allow anyone to
login.


I downgraded sssd an associated packages to 1.16.0-3 and rebooted, all 
services were fully restored


Please note, the problem also occurred when I tried to install a brand
new machine based on stable, and then dist-upgraded it to current
testing, which pulled in sssd 1.16.0-5


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (750, 'testing'), (500, 'unstable'), (500, 'stable'), 
(102, 'experimental')

Architecture: amd64 (x86_64)

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

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages sssd depends on:
ii  python3-sss  1.16.0-3
ii  sssd-ad  1.16.0-3
ii  sssd-common  1.16.0-3
ii  sssd-ipa 1.16.0-3
ii  sssd-krb5    1.16.0-3
ii  sssd-ldap    1.16.0-3
ii  sssd-proxy   1.16.0-3

sssd recommends no packages.

sssd suggests no packages.

-- no debconf information

Bug#890466: rrdtool: FTBFS on m68k: math not IEEE-compliant

[Aaron M. Ucko]

Source: rrdtool
Version: 1.7.0-1
Severity: normal
User: debian-...@lists.debian.org
Usertags: m68k

The build of rrdtool 1.7.0-1 for m68k (admittedly not a release
architecture) failed, per the below excerpt from
https://buildd.debian.org/status/fetch.php?pkg=rrdtool&arch=m68k&ver=1.7.0-1&stamp=1518247574&raw=0:

  IEEE Math Checks
  checking for fpclassify... no
  checking for fpclassify with ... yes
  checking for isinf... yes
  checking whether isfinite is broken... no
  checking if IEEE math works out of the box... not isinf(oo) ... no
  checking if IEEE math works with the -ieee switch... no
  checking if IEEE math works with the -qfloat=nofold switch... no
  checking if IEEE math works with the -w -qflttrap=enable:zerodivide... no
  checking if IEEE math works with the -mieee switch... no
  checking if IEEE math works with the -q float=rndsngl switch... no
  checking if IEEE math works with the -OPT:IEEE_NaN_inf=ON switch... no
  checking if IEEE math works with the -OPT:IEEE_comparisons=ON switch... no
  checking if IEEE math works with fpsetmask(0)... no
  checking if IEEE math works with signal(SIGFPE,SIG_IGN)... not isinf(oo) ... 
no
  configure: error: 
  Your Compiler does not do proper IEEE math ... Please find out how to
  make IEEE math work with your compiler and let me know (t...@oetiker.ch).
  Check config.log to see what went wrong ...

Could you (or the porters, X-Debbugs-Cc:ed) please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#890465: pioneers: Depends on libgnome

[Jeremy Bicha]

Package: pioneers
Version: 15.4-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnome
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

pioneers Build-Depends on libgnome2-dev (which adds a libgnome2-0
Depends). That seems wrong because libgnome is a gtk2 library but
pioneers is built with gtk3.

Without that build dependency, pioneers doesn't offer user help which
seems really wrong.

[1] https://lists.debian.org/debian-devel/2018/02/msg00169.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#853991: bts: Patches for smtp+starttls:// & Net::SMTP::TLS

[Pali Rohár]

On Thursday 02 February 2017 22:25:47 Pali Rohár wrote:
> Package: devscripts
> 
> Hi! I'm sending two patches for bts to bugs as Mattia Rizzolo wanted. 
> Originally I sent those patches to devscripts-devel mailing list.

PING, more then year passed... can somebody review/comment these
patches? Mattia?

-- 
Pali Rohár
pali.ro...@gmail.com


signature.asc
Description: PGP signature

Bug#890444: Does not support voice/video calling

[Hubert Chathi]

forwarded 890444 https://github.com/aperezdc/revolt/issues/73
thanks

On Thu, 15 Feb 2018 09:20:17 +1300, martin f krafft  said:

> I cannot initiate or receive voice or video calls using revolt.  I get
> an error "VoIP is unsupported; You cannot place VoIP calls in this
> browser."

This is because WebKitGTK+ currently does not support WebRTC, and should
be fixed when WebRTC support is added.

-- 
Hubert Chathi  -- https://www.uhoreg.ca/
Jabber: hub...@uhoreg.ca -- Matrix: @uhoreg:matrix.org
PGP/GnuPG key: 4096R/F24C F749 6C73 DDB8 DCB8  72DE B2DE 88D3 113A 1368

Bug#890464: RM: lat -- RoM; RoQA; depends on deprecated GNOME 2 libraries

[Jeremy Bicha]

Package: ftp.debian.org
X-Debbugs-Cc: l...@packages.debian.org

Please remove lat from Debian.

lat's last upstream release was 5 years ago. It depends on multiple
deprecated GNOME2 libraries that the Debian GNOME team is trying to
remove from Debian.

I got approval from the Debian maintainer Eric Dorland before filing this bug.

Thanks,
Jeremy Bicha

Bug#868404: libswt-gnome-gtk-3-jni: Raising severity of libgnome rdepends bugs

[Jeremy Bicha]

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. As part of this process, I
am now raising the severity of this bug.

libswt-gnome-gtk3-jni has only 2 rdepends in Debian: eclipse-rcp and
zekr. eclipse-rcp only recommends libswt-gnom3-gtk3-jni and zekr was
removed from Testing last year because it depends on the old
webkitgtk. So maybe this bug can be fixed by dropping the
libswt-gnome-gtk3-jni package.

libswt-gnome-gtk-4-jni still has no rdepends in Debian.

[1] https://lists.debian.org/debian-devel/2018/02/msg00169.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#584882: devscripts: [build-rdeps] should offer a list-only output of packages, too

[殷啟聰 | Kai-Chung Yan]

I believe the "--quiet" option in at least 2.17.12 (currently in Buster) solves 
this issue.



signature.asc
Description: OpenPGP digital signature

Bug#890282: getmail: please ship with shebang line of #!/usr/bin/env python2

[Daniel Kahn Gillmor]

On Wed 2018-02-14 01:15:17 +0900, Osamu Aoki wrote:
> YES #!/usr/bin/python2
>
> NO  #!/usr/bin/env python2

Works for me, thanks!

All the best,

--dkg

Bug#885027: stretch-pu: package mosquitto/1.4.10-3+deb9u1

[Gianfranco Costamagna]

Hello,
>This is. :-)


thanks and sorry for using it in the wrong way!
G.

Bug#890463: Issue allowing DMs to change username

[Jonathan McDowell]

Package: nm.debian.org

Users who are not yet in LDAP are allowed to edit their LDAP
information, such as username. This means you can sign up as a DM with
one username and then change it before applying to be a DD (see
kaction/iu for an example), which leads to confusion. Either we
shouldn't pay any attention to the username before it is set in stone in
LDAP (i.e. don't include it in account requests etc) or, preferably,
once someone becomes a DM they shouldn't be able to edit it any more.

J.

-- 
Evil will always triumph over Good, because Good is dumb.

Bug#885744: mdbtools-gmdb: Raising severity of libgnome rdepends bugs

[Jeremy Bicha]

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. As part of this process, I
am now raising the severity of this bug.

[1] https://lists.debian.org/debian-devel/2018/02/msg00169.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#890462: Don't allow DMs to change their fingerprint

[Jonathan McDowell]

Package: nm.debian.org

Fingerprint changes are currently allowed for anyone who doesn't have an
account in LDAP, which includes DMs without a guest account. However
this means that the DM keyring gets out of sync with what nm.debian.org
thinks is the state of the world. "hibby" is a good example of this.

We shouldn't allow DMs to change their fingerprint via nm.debian.org;
once you're part of the project you should go through the usual keyring
replacement process.

J.

-- 
... One of the nice things about standards is that there are so many of
them.

Bug#890460: Issue with updating email on retired/emeritus accounts

[Jonathan McDowell]

Package: nm.debian.org

There is an issue when accounts go emeritus/removed and the email
address has been updated by MIA in the nm.debian.org interface; the site
tries to update back to the details from LDAP and at the same time sets
the user status back to unretired. Seen recently on hattas, rogerso +
pstorralba. Hopefully fixed manually for these instances (assuming
housekeeping doesn't revert back tonight) but housekeeping needs fixed
not to do this.

J.

-- 
The more things change the more things suck.

Bug#890459: orbit2: Don't release with Debian Buster

[Jeremy Bicha]

Package: orbit2
Version: 1:2.14.19-4
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs
Tags: sid buster

orbit2 is unmaintained and is only kept in Debian because it's used by
obsolete libgnome libraries that the Debian GNOME team is trying to
remove from Debian Buster. [1] Therefore, I am filing this bug so that
this package can be removed soon.

[1] https://lists.debian.org/debian-devel/2018/02/msg00169.html

Thanks,
Jeremy Bicha

Bug#890461: RFS: igmpproxy/0.2.1-1

[Pali Rohár]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "igmpproxy"

 * Package name: igmpproxy
   Version : 0.2.1-1
   Upstream Author : Pali Rohár 
 * URL : https://github.com/pali/igmpproxy
 * License : BSD-3-clause and GPL-2+
   Section : net

It builds those binary packages:

  igmpproxy  - IGMP multicast routing daemon

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

  https://mentors.debian.net/package/igmpproxy


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

  dget -x 
https://mentors.debian.net/debian/pool/main/i/igmpproxy/igmpproxy_0.2.1-1.dsc

More information about igmpproxy can be obtained from 
https://github.com/pali/igmpproxy.

Changes since the last upload:

  * New upstream release
  * Update Standards-Version to 4.1.3
  * Update to debhelper 10
  * Use https links in copyright

Regards,
 Pali Rohár


signature.asc
Description: PGP signature

Bug#873613: systemd gets confused at shutdown time

[Michael Biebl]

On Fri, 1 Dec 2017 10:39:33 +0100 Harald Dunkel
 wrote:
> Hi Felipe,
> 
> sorry for the delay.
> 
> On 9/5/17 10:09 PM, Felipe Sateler wrote:
> > 
> > 
> > On Mon, Sep 4, 2017 at 3:26 AM, Harald Dunkel  > > wrote:
> > 
> > If there is already a patch 6588, then would you mind to include
> > it for Stretch?
> > 
> > 
> > Before this is considered, we need confirmation it fixes the issue. Could 
> > you try that patch?
> > 
> 
> I applied 9cbc4547702aac28466c497f720038b9e2dc510c to 232-25+deb9u1:
> No luck. It still gets stuck at shutdown time for about 3 minutes.
> 
> Attached you can find 2 screenshots I managed to take. The list-open.service
> was in place. Please note the "nfs-data not responding" due to the lost
> network connection. "nfs-data" is a CNAME for the NFServer for both
> /home and /data.
> 
> Maybe its an option to not shutdown the network at all?

That's up to the network config system.

NetworkManager e.g. does not shut down ethernet connections when being
stoppend.

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



signature.asc
Description: OpenPGP digital signature

Bug#890457: latrace FTBFS with flex 2.6.4-2

[Adrian Bunk]

Source: latrace
Version: 0.5.11-1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/latrace.html

...
  LD latrace
src/config-flex.o: In function `lt_config_lex':
latrace_0.5.11-1/:1481: undefined reference to `lt_config_wrap'
collect2: error: ld returned 1 exit status
make[1]: *** [src/Makefile:87: latrace] Error 1

Bug#868401: oregano: Raising severity of libgnome rdepends bugs

[Jeremy Bicha]

Control: severity -1 serious

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package depends and or build-depends on these libraries:

- gconf
- libart-2.0-2
- libbonobo2-0
- libbonoboui2-0
- libgnomecanvas2-0
- libgnomeui-0
- libgnome2-0
- libgnomevfs2-0
- liborbit-2-0

Please port your package to GTK3 and related maintained libraries.
Otherwise, please consider requesting that your package be removed from
Debian to help us complete this goal.

[1] https://lists.debian.org/debian-devel/2018/02/msg00169.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#890458: RFS: udftools/2.0-1

[Pali Rohár]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "udftools"

 * Package name: udftools
   Version : 2.0-2
   Upstream Author : Pali Rohár 
 * URL : https://github.com/pali/udftools
 * License : GPL-2+
   Section : otherosfs

It builds those binary packages:

  udftools   - tools for UDF filesystems and DVD/CD-R(W) drives

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

  https://mentors.debian.net/package/udftools


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

  dget -x 
https://mentors.debian.net/debian/pool/main/u/udftools/udftools_2.0-2.dsc

More information about udftools can be obtained from 
https://github.com/pali/udftools.

Changes since the last upload:

 * Fix installation in chroot (Closes: #890224)

Regards,
 Pali Rohár


signature.asc
Description: PGP signature

Bug#890455: xpp: segfault due to buffer overflow

[Attila Kinali]

Package: xpp
Version: 1.5-cvs20081009-3
Severity: important
Tags: patch

xpp allocates a 128 byte buffers for the printer selection menu and writes
to the allocated space using unchecked sprintf. It is easy to see
that this may lead to a buffer overflow and subsequent heap corruption.

The following patch fixes a crash due to the above mentioned heap corruption
by replacing malloc+sprintf by asprintf:

--- xpp-1.5-cvs20081009.orig/xpp.cxx
+++ xpp-1.5-cvs20081009/xpp.cxx
@@ -311,7 +311,7 @@ printFiles::printFiles(int  argc, /* I -
 
 // Set up text for menu entry
 
-menu_strs[i]=(char *)calloc(sizeof(char),128);
+//menu_strs[i]=(char *)calloc(sizeof(char),128);
 
 // Get printer information to show in the menu entry
 
@@ -366,25 +366,25 @@ printFiles::printFiles(int  argc, /* I -
 int prtype = CupsHelper::printerType(dests[i].name);
 if ( prtype < 0 ) {
   if ( dests[i].instance != NULL )
-sprintf(menu_strs[i], "%s on %s: Destination not available",
+asprintf(&menu_strs[i], "%s on %s: Destination not available",
 dests[i].instance, dests[i].name);
   else
-sprintf(menu_strs[i], "%s: Destination not available",
+asprintf(&menu_strs[i], "%s: Destination not available",
 dests[i].name);
 } else if ((prtype & CUPS_PRINTER_CLASS) || 
(prtype & CUPS_PRINTER_IMPLICIT)) {
   if ( dests[i].instance != NULL )
-sprintf(menu_strs[i], "%s on %s: %s (printer class)",
+asprintf(&menu_strs[i], "%s on %s: %s (printer class)",
 dests[i].instance, dests[i].name, comment);
   else
-sprintf(menu_strs[i], "%s: %s (printer class)",
+asprintf(&menu_strs[i], "%s: %s (printer class)",
dests[i].name, comment);
 } else {
   if ( dests[i].instance != NULL )
-sprintf(menu_strs[i], "%s on %s: %s (single printer)",
+asprintf(&menu_strs[i], "%s on %s: %s (single printer)",
 dests[i].instance, dests[i].name, comment);
   else
-sprintf(menu_strs[i], "%s: %s (single printer)",
+asprintf(&menu_strs[i], "%s: %s (single printer)",
 dests[i].name, comment);
 }


There are more places where sprintf is used, so I would guess there are
also more places where buffer overflows can occur, but I have not checked them.

I am not sure whether this has any security implications, but I would
not be surprised if.

Attila Kinali

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

Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages xpp depends on:
ii  libc6   2.26-4
ii  libcups22.2.6-4
ii  libfltk1.1  1.1.10-23
ii  libgcc1 1:7.2.0-19
ii  libstdc++6  7.2.0-19

xpp recommends no packages.

xpp suggests no packages.

-- no debconf information

Bug#890456: pike7.8-gtk: Depends on old GNOME libraries

[Jeremy Bicha]

Package: pike7.8-gtk
Version: 7.8.866-8
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnomecanvas libgnomeui libgnome gtksourceview2
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

pike7.8-gtk depends on these:

- libgnome-2-0
- libgnomecanvas2-0
- libgnomeui-0
- libgtksourceview2.0-0

As far as I can tell, Pike doesn't offer GTK3 support yet. I think
you're going to need to drop this package.

See also https://bugs.debian.org/885673 for Pike 8.

[1] https://lists.debian.org/debian-devel/2018/02/msg00169.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#890454: nmu: dogecoin_1.10.0-5

[Thomas Goirand]

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

nmu dogecoin_1.10.0-5 . ANY . unstable . -m "Rebuild against miniupnpc 
2.0.20171212 (transition to libminiupnpc16)."


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

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

Bug#885673: pike8.0-gtk: Raising severity of libgnome rdepends bugs

[Jeremy Bicha]

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. As part of this process, I
am now raising the severity of this bug.

[1] https://lists.debian.org/debian-devel/2018/02/msg00169.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#890260: gap FTCBFS: does not honour DEB_BUILD_OPTIONS=nocheck

[Bill Allombert]

On Mon, Feb 12, 2018 at 04:10:45PM +0100, Helmut Grohne wrote:
> Source: gap
> Version: 4r8p8-2
> Tags: patch
> User: helm...@debian.org
> Usertags: rebootstrap
> 
> gap fails to cross build from source, because it fails running tests
> even when tests are supposed to be disabled via
> DEB_BUILD_OPTIONS=nocheck. It happens to search for the non-standard
> "notest" rather than the policy-documented "nocheck". Please switch to
> the common flag.

Hello Helmut

At some point during the policy discussion, notest was propose and it
stucks in my mind. Now all my packages have this bug...

Sorry about this and thanks for the patch.

Cheers,
Bill.

Bug#886187: zapping: Raising severity of libgnome rdepends bugs

[Jeremy Bicha]

Control: severity -1 serious

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. As part of this process, I
am now raising the severity of this bug.

[1] https://lists.debian.org/debian-devel/2018/02/msg00169.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885751: teg: Raising severity of libgnome rdepends bugs

[Jeremy Bicha]

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. As part of this process, I
am now raising the severity of this bug.

[1] https://lists.debian.org/debian-devel/2018/02/msg00169.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#890452: nmu: 0ad_0.0.22-4

[Thomas Goirand]

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

nmu 0ad_0.0.22-4 . ANY . unstable . -m "Rebuild against miniupnpc 2.0.20171212 
(transition to libminiupnpc16)."


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

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

Bug#890453: nmu: classified-ads_0.12-1

[Thomas Goirand]

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

nmu classified-ads_0.12-1 . ANY . unstable . -m "Rebuild against miniupnpc 
2.0.20171212 (transition to libminiupnpc16)."


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

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

Bug#868398: Raising severity of libgnome perl rdepends bugs

[Jeremy Bicha]

Control: severity -1 serious

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. As part of this process, I
am now raising the severity of these bugs.

A separate warning email for Shutter was sent to debian-devel. [2]

[1] https://lists.debian.org/debian-devel/2018/02/msg00169.html
[2] https://lists.debian.org/debian-devel/2017/12/msg00605.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#883529: ITA: buildbot,buildbot-slave -- Build automation system

[W. Martin Borgert]

Robin, many thanks for working on buildbot!
Very much appreciated!

On 2018-02-14 21:38, Robin Jarry wrote:
> This is hard for me to estimate the repercussions as I lack good
> knowledge of the JS ecosystem. It does not look like a trivial task in
> any case :)

At least for Node I reject the term ecosystem. Toxic waste dump?

Sorry, just kidding.

> For now, I am focusing in having only the server and worker packages
> (without any web ui) updated in debian with the latest upstream release.

Very good! If server and web ui are separated cleanly, it should
be possible to write alternative UIs, right? Like a console one
for us terminal aficionados.

> There is a small limitation in pybuild regarding building multiple
> binary packages from the same source package (each located in
> subdirectories). I talked with p1otr on #debian-python and he told me he
> may have a fix uploaded soon(tm).

That's good news!

> In the meantime, I am struggling to make the tests run and docs build
> with only debian dependencies.

If there are Python depends, that are not in Debian or too old,
do not hesitate to ask me, maybe I can burn some time.

Btw. maybe you want to maintain buildbot (at least the parts mainly
written in Python) within the Python Applications Packaging Team
? It is also at salsa:
https://salsa.debian.org/python-team/applications, but the packages
have not yet been migrated.


signature.asc
Description: PGP signature

Bug#890373: debhelper: Please fix indendation in postinst-systemd-restart

[Christoph Biedl]

Niels Thykier wrote...

> AFAICT from that output, the file is correctly indented in 11.1.4.

Please check using the attached .tar.xz and .dsc. When building with
current sid (i.e. debhelper = 11.1.4), I get in DEBIAN/postinst:

(ca. line 20)
| # Automatically added by dh_systemd_start/11.1.4
| if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = 
"abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then
+   if [ -d /run/systemd/system ]; then
+   systemctl --system daemon-reload >/dev/null || true
|   if [ -n "$2" ]; then

 Christoph
Format: 3.0 (native)
Source: demo
Binary: demo
Architecture: all
Version: 2018.02.14
Maintainer: Christoph Biedl 
Standards-Version: 4.1.3
Build-Depends: debhelper (>= 11~)
Package-List:
 demo deb net optional arch=all
Checksums-Sha1:
 1e162fa034811efe614fa824cad82bd20b039753 708 demo_2018.02.14.tar.xz
Checksums-Sha256:
 583b340a2340cfadd790220fcc04c1b8f42c9c11f209f41052b3d8d8ed9bfdbf 708 
demo_2018.02.14.tar.xz
Files:
 5aa326d831c65dee3fa739670bb79eb3 708 demo_2018.02.14.tar.xz


demo_2018.02.14.tar.xz
Description: application/xz


signature.asc
Description: PGP signature

Bug#868417: gnome-commander: Raising severity of libgnome rdepends bugs

[Jeremy Bicha]

Control: severity -1 serious

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. As part of this process, I
am now raising the severity of this bug.

[1] https://lists.debian.org/debian-devel/2018/02/msg00169.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885736: ggcov: Raising severity of libgnome rdepends bugs

[Jeremy Bicha]

Control: severity -1 serious

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. As part of this process, I
am now raising the severity of this bug.

[1] https://lists.debian.org/debian-devel/2018/02/msg00169.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#868413: gbonds: Raising severity of libgnome rdepends

[Jeremy Bicha]

Control: severity -1 serious

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package depends and or build-depends on these libraries:

- gconf
- libbonobo2-0
- libbonoboui2-0
- libgnomeui-0
- libgnome2-0
- libgnomevfs2-0

Please port your package to GTK3 and related maintained libraries.
Otherwise, please consider requesting that your package be removed from
Debian to help us complete this goal.

[1] https://lists.debian.org/debian-devel/2018/02/msg00169.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#884111: stretch-pu: package vdirsyncer/0.14.1-1

[Adam D. Barratt]

Control: tags -1 + pending

On Tue, 2018-01-16 at 16:01 +0100, Filip Pytloun wrote:
> Thank you, uploaded and waiting in stable-new.
> 

Flagged for acceptance.

Regards,

Adam

Bug#890451: Generate a skeleton of README.source about rda and rdata files

[Dylan Aïssi]

Package: dh-r
Severity: wishlist


Hi,

dh-make-R (and dh-update-R) could generate (and update) a
README.source file or at least a skeleton with relevant information
for .rda (and *.Rda, *.rdata, *.Rdata, etc.) files, see [2] for more
information. Andreas already wrote a shell script [2] to do this.

Best,
Dylan

[1] https://lintian.debian.org/tags/r-data-without-readme-source.html
[2] https://lists.debian.org/debian-science/2017/10/msg00070.html

Bug#885531: stretch-pu: package soundtouch/1.9.2-2+deb9u1

[Adam D. Barratt]

Control: tags -1 + pending

On Sat, 2018-02-10 at 11:03 +0100, Julien Cristau wrote:
> Control: tag -1 confirmed
> 
> On Wed, Dec 27, 2017 at 17:14:59 +, James Cowgill wrote:
> 
> > This soundtouch update fixes 3 no-DSA security bugs: #870854,
> > #870856,
> > and #870857. I have tested the package on stretch and with the
> > attached
> > debdiff, soundstretch still works and the proof of concepts for the
> > 3
> > security issues behave correctly now.
> > 
> > The patch under debian/patches uses DOS line endings because the
> > file it
> > modifies also uses DOS line endings.
> > 
> 
> Go ahead, thanks.

Uploaded and flagged for acceptance.

Regards,

Adam

Bug#882434: stretch-pu: package ust/2.9.0-2+deb9u1

[Adam D. Barratt]

Control: tags -1 + pending

On Sat, 2018-01-13 at 17:29 +0100, Julien Cristau wrote:
> Control: tag -1 confirmed
> 
> On Wed, Nov 22, 2017 at 15:05:52 -0500, Michael Jeanson wrote:
> 
> > The attached diff fixes a bug that makes the python3-lttngust
> > package
> > completely broken unless the corresponding liblttng-ust-dev is also
> > installed.
> > 
> > The original python code load the library using ctypes without
> > specifying a
> > soname. This fix was reported and merged upstream.
> > 
> 
> Anything using ctypes for library bindings should be taken out back
> and
> shot.
> 
> However, this seems like an improvement over the previous
> even-more-buggy state, so go ahead.

Uploaded and flagged for acceptance.

Regards,

Adam

Bug#882827: stretch-pu: package python-mimeparse/0.1.4-3.1~deb9u1

[Adam D. Barratt]

Control: tags -1 + pending

On Sat, 2018-01-13 at 17:52 +0100, Julien Cristau wrote:
> Control: tag -1 = confirmed stretch
> 
> On Sat, Jan 13, 2018 at 17:44:10 +0100, Julien Cristau wrote:
> 
> > Control: tag -1 moreinfo
> > 
> 
> Woops wrong tag.
> 

Uploaded and flagged for acceptance.

Regards,

Adam

Bug#882813: stretch-pu: package python-pyperclip/1.5.27-3~deb9u1

[Adam D. Barratt]

Control: tags -1 + pending

On Sat, 2018-01-13 at 17:30 +0100, Julien Cristau wrote:
> Control: tag -1 confirmed
> 
> On Mon, Nov 27, 2017 at 01:14:27 +0100, Andreas Beckmann wrote:
> 
> > python3-pyperclip misses a proper python3 dependency.
> > 
> > $ debdiff python3-pyperclip_1.5.27-2_all.deb python3-
> > pyperclip_1.5.27-3~deb9u1_all.deb
> > File lists identical (after any substitutions)
> > 
> > Control files: lines which differ (wdiff format)
> > 
> > Depends: {+python3:any (>= 3.4~),+} xclip | xsel | python3-pyqt4
> > Version: [-1.5.27-2-] {+1.5.27-3~deb9u1+}
> > 
> 
> Go ahead, thanks.
> 

Uploaded and flagged for acceptance.

Regards,

Adam

Bug#882819: stretch-pu: package python-spake2/0.7-3~deb9u1

[Adam D. Barratt]

Control: tags -1 + pending

On Sat, 2018-01-13 at 17:36 +0100, Julien Cristau wrote:
> Control: tag -1 confirmed
> 
> On Mon, Nov 27, 2017 at 02:00:48 +0100, Andreas Beckmann wrote:
> 
> > Package: release.debian.org
> > Severity: normal
> > Tags: stretch
> > User: release.debian@packages.debian.org
> > Usertags: pu
> > 
> > Let's fix the python3 dependencies. #867457
> > 
> 
> OK.
> 

Uploaded and flagged for acceptance.

Regards,

Adam

Bug#884452: stretch-pu: package python-evtx/0.5.3b-3+deb9u1

[Adam D. Barratt]

Control: tags -1 + pending

On Sat, 2018-01-13 at 18:22 +0100, Julien Cristau wrote:
> Control: tag -1 confirmed
> 
> On Fri, Dec 15, 2017 at 11:28:21 +0100, Hilko Bengen wrote:
> 
> > Package: release.debian.org
> > Severity: normal
> > Tags: stretch
> > User: release.debian@packages.debian.org
> > Usertags: pu
> > 
> > Dear release team,
> > 
> > please consider allowing an update to the python-evtx package in
> > stretch. It fixes Python3 dependencies (RC bug #867428).
> > 
> 
> Please go ahead.
> 

Uploaded and flagged for acceptance.

Regards,

Adam

Bug#882822: stretch-pu: package python-hkdf/0.0.3-3~deb9u1

[Adam D. Barratt]

Control: tags -1 + pending

On Sat, 2018-01-13 at 17:40 +0100, Julien Cristau wrote:
> Control: tag -1 confirmed
> 
> On Mon, Nov 27, 2017 at 02:22:54 +0100, Andreas Beckmann wrote:
> 
> > Let's fix the python3 dependencies. #867433
> > (And by just rebuilding the package from sid,
> > we get some metadata updates as well.)
> > 
> 
> Please go ahead.
> 

Uploaded and flagged for acceptance.

Regards,

Adam

Bug#890225: reopening RFS: flake8-polyfill/1.0.2-1

[Jeremy Bicha]

Control: reopen -1

Sorry about the typo.

Thanks,
Jeremy Bicha

Bug#877593: stretch-pu: package ocfs2-tools/1.8.4-4+deb9u1

[Adam D. Barratt]

Control: tags -1 + pending

On Sat, 2018-02-10 at 11:44 +0100, Valentin Vidic wrote:
> On Sat, Feb 10, 2018 at 09:39:09AM +0100, Julien Cristau wrote:
> > OK, please go ahead.
> 
> Thanks, uploaded.

Flagged for acceptance.

Regards,

Adam

Bug#885582: stretch-pu: package ncurses/6.0+20161126-1+deb9u2

[Adam D. Barratt]

Control: tags -1 + pending

On Sun, 2018-02-11 at 10:35 +0100, Sven Joachim wrote:
> On 2018-02-11 09:45 +0100, Julien Cristau wrote:
> 
> > Control: tag -1 - moreinfo
> > Control: tag -1 confirmed
> > 
> > On Sat, Feb 10, 2018 at 11:08:37 +0100, Julien Cristau wrote:
> > 
> > > Control: tag -1 moreinfo
> > > 
> > 
> > Got that one wrong, sorry.
> 
> Thanks, uploaded.

Flagged for acceptance.

Regards,

Adam

Bug#882826: stretch-pu: package python-hacking/0.11.0-2.1~deb9u1

[Adam D. Barratt]

Control: tags -1 + pending

On Sat, 2018-01-13 at 17:43 +0100, Julien Cristau wrote:
> Control: tag -1 confirmed
> 
> On Mon, Nov 27, 2017 at 03:51:31 +0100, Andreas Beckmann wrote:
> 
> > Package: release.debian.org
> > Severity: normal
> > Tags: stretch
> > User: release.debian@packages.debian.org
> > Usertags: pu
> > 
> > Let's fix the python3 dependencies. #867431
> > 
> > $ debdiff python3-hacking_0.11.0-2_all.deb python3-hacking_0.11.0-
> > 2.1~deb9u1_all.deb
> > File lists identical (after any substitutions)
> > 
> > Control files: lines which differ (wdiff format)
> > 
> > Depends: [-pyflakes,-] {+pyflakes3,+} python3-flake8 (>= 3.0.0),
> > python3-pbr (>= 1.8), python3-pep8 (>= 1.5.7), python3-six (>= [-
> > 1.9.0)-] {+1.9.0), flake8, python3-mccabe, python3-pycodestyle,
> > python3-pyflakes, python3:any (>= 3.3.2-2~)+}
> > Version: [-0.11.0-2-] {+0.11.0-2.1~deb9u1+}
> > 
> 
> 
OK, please go ahead.
> 

Uploaded and flagged for acceptance.

Regards,

Adam

Bug#889855: apticron: on each run, getting twice: W: --force-yes is deprecated

[Tiago Bortoletto Vaz]

Thanks Gabriel, I'm closing it right now :)

(see the magic in cc:)

Bests,

On Wed, Feb 14, 2018 at 08:32:00PM +, Gabriel Filion wrote:
> Gah!
> 
> I did a little bit more research and found out that the warning was not
> replicating on stretch hosts managed elsewhere. This led me to find that
> the warning was *not* caused by aptitude itself but rather by an option
> in apt.conf.d/ that was configured by our configuration management (e.g.
> it was configuring "APT::Get::force-yes true;"
> 
> I've removed this from the configuration that is being pushed by our
> configuration management and the warning is gone.
> 
> So I'm really sorry for creating noise here and not having
> investigated a bit more! I thought that since I could replicate on more
> than one host it was a problem with the software but it was rather a
> configuration problem.
> 
> This bug report can be closed (sorry don't know the magic email line
> that does this)
> 




-- 
tiago

Bug#890373: debhelper: Please fix indendation in postinst-systemd-restart

[Niels Thykier]

Control: tags -1 moreinfo

On Wed, 14 Feb 2018 08:32:31 +0100 Christoph Biedl
 wrote:
> Package: debhelper
> Version: 11.1.4
> Severity: minor
> 
> Dear Maintainer,
> 
> while checking the debhelper sniplets created by dh_systemd_* I got
> quite confused by the indentation, making me believe it's some
> malformatted or even invalid shell script.
> 
> Please apply the attached (as it contains tab characters) diff when
> convenient.
> 
> Regards,
> 
> Christoph

Hi,

The patch does not apply cleanly to 11.1.4 and nor does the problem
appear to be present in 11.1.4:

"""
$ cat -vT autoscripts/postinst-systemd-restart
if [ "$1" = "configure" ] || [...] ; then
^Iif [ -d /run/systemd/system ]; then
^I^Isystemctl --system daemon-reload >/dev/null || true
^I^Iif [ -n "$2" ]; then
^I^I^I_dh_action=restart
^I^Ielse
^I^I^I_dh_action=start
^I^Ifi
^I^Ideb-systemd-invoke $_dh_action #UNITFILES# >/dev/null || true
^Ifi
fi
"""

AFAICT from that output, the file is correctly indented in 11.1.4.

Thanks,
~Niels

Bug#890225: Bug #890225 in vala marked as pending

[Jeremy Bicha]

Control: tags -1 -pending

Oops, I meant to mark #890255 as pending instead. Sorry about that!

Thanks,
Jeremy Bicha

Bug#890450: freetype: CVE-2018-6942: NULL pointer dereference in the Ins_GETVARIATION() function

[Salvatore Bonaccorso]

Source: freetype
Version: 2.8.1-1
Severity: important
Tags: security upstream

Hi,

the following vulnerability was published for freetype.

CVE-2018-6942[0]:
| An issue was discovered in FreeType 2 through 2.9. A NULL pointer
| dereference in the Ins_GETVARIATION() function within ttinterp.c could
| lead to DoS via a crafted font file.

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-2018-6942
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6942
[1] 
https://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=29c759284e305ec428703c9a5831d0b1fc3497ef

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#884451: stretch-pu: package libvhdi/20160424-1+deb9u1

[Adam D. Barratt]

Control: tags -1 + pending

On Sat, 2018-01-13 at 18:21 +0100, Julien Cristau wrote:
> Control: tag -1 confirmed
> 
> On Fri, Dec 15, 2017 at 11:28:16 +0100, Hilko Bengen wrote:
> 
> > Package: release.debian.org
> > Severity: normal
> > Tags: stretch
> > User: release.debian@packages.debian.org
> > Usertags: pu
> > 
> > Dear release team,
> > 
> > please consider allowing an update to the libvhi package in
> > stretch. It
> > fixes missing Python3 dependencies (RC bug #867409).
> > 
> 
> Looks ok, please go ahead.

Uploaded and (finally) flagged for acceptance.

Regards,

Adam

Bug#882158: stretch-pu: package glibc/2.24-11+deb9u2

[Adam D. Barratt]

Control: tags -1 + pending

On Sun, 2018-01-14 at 11:52 +0100, Aurelien Jarno wrote:
> On 2018-01-13 17:26, Julien Cristau wrote:
> > Control: tag -1 confirmed
> > 
> > On Sat, Dec  9, 2017 at 14:22:45 +0100, Aurelien Jarno wrote:
> > 
> > > Unfortunately it didn't make in 9.3 due to the regression
> > > introduced wrt
> > > /etc/ld.so.nohwcap (see bug#883394). The issue is due to the
> > > conversion
> > > of libc6-i686 into a transitional package between jessie and
> > > stretch, and
> > > dropping the postinst and postrm script handling the removal of
> > > /etc/ld.so.nohwcap after the upgrade. The problem always existed
> > > in
> > > stretch, but the probability for it to happen has been greatly
> > > increased
> > > by the fix for #882272. The issue doesn't affect buster/sid as
> > > the
> > > transitional package has been removed.
> > > 
> > > I have fixed the issue in version 2.24-11+deb9u3 by reintroducing
> > > the
> > > postinst and postrm scripts in the transitional package. You will
> > > find
> > > below the corresponding patch.
> > > 
> > > Thanks for considering it for 9.4.
> > > 
> > 
> > Assuming that's been tested in all the various scenarios, please go
> > ahead.
> 
> Thanks, I have just uploaded it. Note that the issue with the nvidia
> drivers has been found (providing the default version of the
> libraries
> without TLS) and has already been fixed in sid.

Flagged for acceptance; sorry for the delay.

Regards,

Adam

Bug#885027: stretch-pu: package mosquitto/1.4.10-3+deb9u1

[Adam D. Barratt]

Control: tags -1 + pending

On Wed, 2018-02-14 at 20:11 +, Adam D. Barratt wrote:
> Control: tags -1 - pending
> 
> On Wed, 2018-02-14 at 19:49 +0100, Gianfranco Costamagna wrote:
> > control: tags -1 pending
> > On Sat, 10 Feb 2018 14:47:51 + Holger Levsen  > .o
> > rg> wrote:
> > > On Sat, Feb 10, 2018 at 01:39:12PM +, Roger Light wrote:
> > > > I'm neither a DD nor a DM, should I just get my normal sponsor
> > > > to
> > > > upload or if not then who?
> > > 
> > > yes, ask your usual sponsor to upload.
> > > 
> > 
> > doing it in a few minutes
> > 

Flagged for acceptance.

> That's not what the pending tag means for a p-u bug.

This is. :-)

Regards,

Adam

Bug#883483: stretch-pu: package flatpak/0.8.8-0+deb9u1

[Adam D. Barratt]

Control: tags -1 + pending

On Sat, 2018-01-13 at 16:53 +, Simon McVittie wrote:
> On Sat, 13 Jan 2018 at 17:51:04 +0100, Julien Cristau wrote:
> > On Mon, Dec  4, 2017 at 15:45:40 +, Simon McVittie wrote:
> > > The upstream maintainer of Flatpak has made a 0.8.8 release
> > > 
> > 
> > Assuming this has been tested on stretch, please go ahead.
> 
> Thanks, uploaded.

(Somewhat belatedly) flagged for acceptance.

Regards,

Adam

Bug#884606: stretch-pu: package espeakup/1:0.80-5+b2

[Adam D. Barratt]

Control: tags -1 + pending

On Sat, 2018-02-10 at 14:05 +0100, Samuel Thibault wrote:
> Julien Cristau, on sam. 10 févr. 2018 10:55:09 +0100, wrote:
> > Control: tag -1 confirmed
> > 
> > On Thu, Dec 21, 2017 at 15:44:56 +0100, Samuel Thibault wrote:
> > 
> > > Samuel Thibault, on jeu. 21 déc. 2017 15:42:13 +0100, wrote:
> > > > Cyril Brulebois, on jeu. 21 déc. 2017 15:37:00 +0100, wrote:
> > > > > I don't think that's an issue with cherry-picking the
> > > > > relevant commit,
> > > > > since it doesn't seem to contain any indications the default
> > > > > voice is
> > > > > getting set to English?
> > > > 
> > > > IIRC I had issues without it, so it was on purpose, and just
> > > > missed
> > > > documenting it.
> > > 
> > > Here is the fixed patch.
> > 
> > If kibi's happy, I'm happy.  Go ahead and upload.
> 
> Uploaded, thanks!
> 

Flagged for acceptance.

Regards,

Adam

Bug#883952: stretch-pu: package activity-log-manager/0.8.0-1.2~deb9u1

[Adam D. Barratt]

Control: tags -1 + pending

On Sat, 2018-01-13 at 18:12 +0100, Julien Cristau wrote:
> Control: tag -1 confirmed
> 
> On Sat, Dec  9, 2017 at 20:23:18 +0100, Andreas Beckmann wrote:
> 
> > Package: release.debian.org
> > Severity: normal
> > Tags: stretch
> > User: release.debian@packages.debian.org
> > Usertags: pu
> > 
> > Let's fix the missing dependency on python-zeitgeist, #881438, by
> > rebuilding the corresponding fixed package from sid.
> > 
> 
> Go ahead.
> 

Uploaded and flagged for acceptance.

Regards,

Adam

Bug#885184: stretch-pu: package agenda.app/0.42.2-1+deb9u1

[Adam D. Barratt]

Control: tags -1 + pending

On Sat, 2018-02-10 at 10:28 +0100, Julien Cristau wrote:
> Control: tag -1 confirmed
> 
> On Mon, Dec 25, 2017 at 22:53:57 +0200, Yavor Doganov wrote:
> 
> > Package: release.debian.org
> > Severity: normal
> > Tags: stretch
> > User: release.debian@packages.debian.org
> > Usertags: pu
> > 
> > Hi SRMs,
> > 
> > Would you approve an update for agenda.app to fix #884098?
> > Proposed change was tested on a stretch machine; debdiff attached.
> > 
> 
> OK, go ahead.
> 

Uploaded and flagged for acceptance.

Regards,

Adam

Bug#885735: gamazons: Raising severity for libgnome dependencies

[Jeremy Bicha]

Control: severity -1 serious

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package depends and or build-depends on these libraries:

- libgnomecanvas2-0
- libgnomeui-0
- libgnome2-0

Please port your package to GTK3 and related maintained libraries.
Otherwise, please consider requesting that your package be removed from
Debian to help us complete this goal.

[1] https://lists.debian.org/debian-devel/2018/02/msg00169.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#868388: camorama: Raising severity for libgnome dependencies

[Jeremy Bicha]

Control: severity -1 serious

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package depends and or build-depends on these libraries:

- gconf
- libgnomeui-0
- libgnome2-0
- libgnomevfs2-0

Please port your package to GTK3 and related maintained libraries.
Otherwise, please consider requesting that your package be removed from
Debian to help us complete this goal.

[1] https://lists.debian.org/debian-devel/2018/02/msg00169.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#890449: RFS: engauge-digitizer/10.4+ds.1-2

[Tobias Winchen]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "engauge-digitizer"

 * Package name: engauge-digitizer
   Version : 10.4+ds.1-2
  Upstream Author : Mark Mitchell 
 * URL : https://github.com/markummitchell/engauge6
 * License : GPL-2+
   Section : science

 It builds those binary packages:

engauge-digitizer - interactively extracts numbers from bitmap graphs or 
maps
 engauge-digitizer-doc - engauge-digitizer user manual and tutorial

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

  https://mentors.debian.net/package/engauge-digitizer

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

dget -x https://mentors.debian.net/debian/pool/main/e/engauge-digitizer/
engauge-digitizer_10.4+ds.1-2.dsc

  Changes since the last upload:
   
 [ Helmut Grohne ]
  * Fix FTCBFS: Let dh_auto_configure pass cross flags to qmake.
(Closes: #889801)

  [Tobias Winchen]
  * Update to ch compat 10
- Drop --parallel from dh $@
  * Install icons in usr/share/icons instead of usr/share/pixmaps\
- Install SVG icon using engauge-digitizer.install


Bests,
   Tobias Winchen

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

Bug#890448: transition: mbedtls

[James Cowgill]

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

Hi,

mbedtls bumped the SONAME of one of its libraries (libmbedcrypto) so it
needs a transition. The new version is currently in experimental.

These reverse dependencies built successfully first time:
charybdis
dislocker
dolphin-emu
gatling
ncbi-vdb
neko
shadowsocks-libev

bctoolbox was fixed about an hour ago (#890417).

mongrel2 still fails, but this is caused by an mbedtls bug which I have
queued up ready to upload (the fix is obvious):
https://salsa.debian.org/debian/mbedtls/commit/f2769d8c7cb1edb2a8e6fb3e6d8527638550927d

Thanks,
James

Ben file:

title = "mbedtls";
is_affected = .depends ~ "libmbedcrypto0" | .depends ~ "libmbedcrypto1";
is_good = .depends ~ "libmbedcrypto1";
is_bad = .depends ~ "libmbedcrypto0";


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

Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled



signature.asc
Description: OpenPGP digital signature