Bug#901148: timidity: upgrading to 2.14.0-2 broke sound in KDE plasma

[Arthur Marsh]

Package: timidity
Version: 2.14.0-3
Followup-For: Bug #901148

Dear Maintainer,

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

   * What led up to the situation?

restarting pc, starting KDE plasma desktop - no sound in KDE plasma desktop

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

service timidity restart 

from within KDE plasma desktop

   * What was the outcome of this action?
   * What outcome did you expect instead?

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


-- System Information:
Debian Release: buster/sid
  APT prefers experimental
  APT policy: (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.17.0+ (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages timidity depends on:
ii  libasound21.1.6-1
ii  libaudio2 1.9.4-6
ii  libc6 2.27-3
ii  libflac8  1.3.2-3
ii  libice6   2:1.0.9-2
ii  libjack0 [libjack-0.125]  1:0.125.0-3
ii  libncurses6   6.1+20180210-4
ii  libogg0   1.3.2-1+b1
ii  libpng16-16   1.6.34-1
ii  libsm62:1.2.2-1+b3
ii  libspeex1 1.2~rc1.2-1+b2
ii  libtinfo6 6.1+20180210-4
ii  libvorbis0a   1.3.6-1
ii  libvorbisenc2 1.3.6-1
ii  libx11-6  2:1.6.5-1
ii  libxaw7   2:1.0.13-1+b2
ii  libxext6  2:1.3.3-1+b2
ii  libxmu6   2:1.1.2-2
ii  libxt61:1.1.5-1
ii  lsb-base  9.20170808
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages timidity recommends:
ii  fluid-soundfont-gm  3.1-5.1
ii  timidity-daemon 2.14.0-3

Versions of packages timidity suggests:
ii  fluid-soundfont-gs  3.1-5.1
ii  freepats20060219-1
pn  pmidi   

-- no debconf information

Bug#884440: zimlib: Please package new 3.1.0 upstream version

[Vasudev Kamath]

On Mon, 11 Jun 2018 at 05:24, Kunal Mehta  wrote:
>
> retitle 884440 Please package new 3.3.0 upstream version
> thanks
>
> upstream is now at 3.3.0. I went ahead and prepared most of the
> packaging for this at
> . Would it
> help if I created a merge request on salsa?

Yes Please and add yourself to uploaders list. I can give out active
maintenance to you as I don't have
time to spend on the package and I don't really use kiwix.

> The remaining tasks should
> be to generate the rest of the symbols files (I'm not sure how to do
> that), and update the changelog.

Please update the symbols file first for your architecture and then
please upload to experimental, once its built on all architectures
please download logs and update symbols for remaining architecture.
[1] should give some idea.

[1]  https://www.eyrie.org/~eagle/journal/2012-01/008.html

>
> This is needed so I can upgrade libkiwix and start packaging the rest of
> the kiwix suite.

Understand.. That's why I'm asking take over the maintenance


-- 

Vasudev Kamath
http://copyninja.info

Bug#901296: luabind is outdated, please fix it with one or more of the forks with a recent version

[shirish शिरीष]

Source: luabind
Severity: wishlist

Dear Maintainer,

There are number of issues with the version of luabind in Debian. The
homepage given is no longer available and hence I guess even the
upstream sources are no longer available.

I have been trying to work with couple of upstream games which use
liblua and have been made aware of few different forks which would be
more preferable to the current one available in Debian.

See 
https://bitbucket.org/allacrost/allacrost/issues/55/luabind-uses-deprecated-auto_ptr
for details.

It may also prove to be helpful in removing some of the lintian errors
as can be seen
in https://lintian.debian.org/maintainer/robe...@connexer.com.html#luabind

It may also be profitable as far as maintainance is concerned if
liblua was part of the debian-devel-games team and you being part of
the team.

I  took the liberty of see if there were any reverse-builds of the
various build-depends which may hinder having conflicts but didn't see
anything which might make it difficult, at least to my untrained eye.

I used apt-rdepends --build-depends libluabind* | less basically all
the differnt libluabind library binaries to see if I could find
anything but seems it would be a self-contained transition without any
huge transition costs as can be seen in
https://release.debian.org/transitions/

Look forward to the new version in Debian soonish (hopefully with the
auto_ptr patches done).


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

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

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#891706: #891706 ITP: golang-github-tonistiigi-fsutil -- Incremental file directory sync tools in golang

[Dmitry Smirnov]

On Monday, 11 June 2018 2:53:12 PM AEST Arnaud Rebillout wrote:
> I didn't push this package to salsa yet. The issue I have is that it
> depends on docker-dev, and it doesn't have any vendoring, so I can't
> keep the vendored directory with a smart "Files-Excluded" field. The
> solution I came up with was to make a patch that creates a vendor
> directory and adds the bits we need from docker-dev.
> 
> With time I realized how super ugly and bad this kind of thing is.
> 
> So vendoring this one in docker looks like a much better approach.
> 

Of course, never mind then... We need to break circular dependencies with 
Docker, not to introduce new ones... Thanks.


> > Also could you please ask upstream to tag releases?
> 
> Sure.

Thanks.

-- 
Regards,
 Dmitry Smirnov.



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

Bug#901148: timidity: upgrading to 2.14.0-2 broke sound in KDE plasma

[Arthur Marsh]

Package: timidity
Followup-For: Bug #901148

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Upgrading to timidity 2.14.0-3 and running 

service timidity restart 

worked, but I am at a loss as to why timidity could stop all sound working
in KDE plasma and not just software MIDI playback.

   * What was the outcome of this action?
   * What outcome did you expect instead?

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


-- System Information:
Debian Release: buster/sid
  APT prefers experimental
  APT policy: (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.17.0+ (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages timidity depends on:
ii  libasound21.1.6-1
ii  libaudio2 1.9.4-6
ii  libc6 2.27-3
ii  libflac8  1.3.2-3
ii  libice6   2:1.0.9-2
ii  libjack0 [libjack-0.125]  1:0.125.0-3
ii  libncurses6   6.1+20180210-4
ii  libogg0   1.3.2-1+b1
ii  libpng16-16   1.6.34-1
ii  libsm62:1.2.2-1+b3
ii  libspeex1 1.2~rc1.2-1+b2
ii  libtinfo6 6.1+20180210-4
ii  libvorbis0a   1.3.6-1
ii  libvorbisenc2 1.3.6-1
ii  libx11-6  2:1.6.5-1
ii  libxaw7   2:1.0.13-1+b2
ii  libxext6  2:1.3.3-1+b2
ii  libxmu6   2:1.1.2-2
ii  libxt61:1.1.5-1
ii  lsb-base  9.20170808
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages timidity recommends:
ii  fluid-soundfont-gm  3.1-5.1
ii  timidity-daemon 2.14.0-3

Versions of packages timidity suggests:
ii  fluid-soundfont-gs  3.1-5.1
ii  freepats20060219-1
pn  pmidi   

-- no debconf information

Bug#901274: [lintian] warn about *.md,.eslintrc, .npmignore, LICENSE, CHANGES, PATENTS, *.woff, *.ttf, *.woff.? under /usr/lib/node (may be /usr/lib ?)

[Bastien ROUCARIES]

On Mon, Jun 11, 2018 at 1:05 AM, Chris Lamb  wrote:
>
>
> Hi Bastien ROUCARIES,
>
>> On Mon, Jun 11, 2018 at 12:07 AM, Chris Lamb  wrote:
>> > Hi Bastien,
>> >
>> >> > Unfortunately, I don't think these commits reach the level of quality
>> >> > that Debian Developers would expect from Lintian.
>> >>
>> >> Ok could you get a glimpse at README branch
>> >
>> > Could you move the other changes to this branch too (or a "901274"
>> > branch/MR or something?)  :)
>>
>> Did you prefer a reset or reset of master ?
>
> A reset or a reset?
A reset or a revert...
>
>> Bastien
>> >
>> >
>> > Best wishes,
>> >
>> > --
>> >   ,''`.
>> >  : :'  : Chris Lamb
>> >  `. `'`  la...@debian.org / chris-lamb.co.uk
>> >`-
>
>
> Regards,
>
> --
>   ,''`.
>  : :'  : Chris Lamb
>  `. `'`  la...@debian.org / chris-lamb.co.uk
>`-

Bug#891706: #891706 ITP: golang-github-tonistiigi-fsutil -- Incremental file directory sync tools in golang

[Arnaud Rebillout]

On 06/11/2018 11:47 AM, Dmitry Smirnov wrote:
> Also could you please ask upstream to tag releases?

https://github.com/tonistiigi/fsutil/issues/43

Bug#891706: #891706 ITP: golang-github-tonistiigi-fsutil -- Incremental file directory sync tools in golang

[Arnaud Rebillout]

Hi !


On 06/11/2018 11:47 AM, Dmitry Smirnov wrote:
> There is no repository under 
>
>  https://salsa.debian.org/go-team/packages?filter=fsutil

I didn't push this package to salsa yet. The issue I have is that it
depends on docker-dev, and it doesn't have any vendoring, so I can't
keep the vendored directory with a smart "Files-Excluded" field. The
solution I came up with was to make a patch that creates a vendor
directory and adds the bits we need from docker-dev.

With time I realized how super ugly and bad this kind of thing is.

So vendoring this one in docker looks like a much better approach.

> Also could you please ask upstream to tag releases?

Sure.

Bug#901295: apt-cacher-ng.8: typo: that vs those

[Paul Wise]

Package: apt-cacher-ng
Version: 3.1-1
Severity: minor
File: /usr/share/man/man8/apt-cacher-ng.8.gz

There is a typo in the manual page, it uses the word 'that' where the
word 'those' should be used instead.

$ man apt-cacher-ng | grep -C1 that
   Variables can override previously  configured  settings  from
   other files, sometimes that settings are merged (depending on
   the variable).
  

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages apt-cacher-ng depends on:
ii  adduser3.117
ii  debconf [debconf-2.0]  1.5.66
ii  dpkg   1.19.0.5+b1
ii  libbz2-1.0 1.0.6-8.1
ii  libc6  2.27-3
ii  libgcc11:8.1.0-5
ii  liblzma5   5.2.2-1.3
ii  libssl1.1  1.1.0h-4
ii  libstdc++6 8.1.0-5
ii  libsystemd0238-5
ii  libwrap0   7.6.q-27
ii  lsb-base   9.20170808
ii  zlib1g 1:1.2.11.dfsg-1

apt-cacher-ng recommends no packages.

Versions of packages apt-cacher-ng suggests:
ii  avahi-daemon  0.7-4
pn  doc-base  
ii  libfuse2  2.9.7-1

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#901293: matrix-synapse: Improper event filtering in get_missing_events handler

[Salvatore Bonaccorso]

Source: matrix-synapse
Version: 0.30.0+dfsg-1
Severity: grave
Tags: patch security upstream
Forwarded: https://github.com/matrix-org/synapse/pull/3371
Control: fixed -1 0.31.1+dfsg-1

From

https://matrix.org/blog/2018/06/08/synapse-0-31-1-released/

> v0.31.1 fixes a security bug in the get_missing_events federation API
> where event visibility rules were not applied correctly.

Regards,
Salvatore

Bug#901294: apt-cacher-ng.8: typo: find vs found

[Paul Wise]

Package: apt-cacher-ng
Version: 3.1-1
Severity: minor
File: /usr/share/man/man8/apt-cacher-ng.8.gz

There is a typo in the manual page, it uses 'find' where the past
tense equivalent 'found' should be used instead:

$ man apt-cacher-ng | grep -B1 find
  Scan the  specified  configuration  directory
  and interpret configuration files find there.


-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages apt-cacher-ng depends on:
ii  adduser3.117
ii  debconf [debconf-2.0]  1.5.66
ii  dpkg   1.19.0.5+b1
ii  libbz2-1.0 1.0.6-8.1
ii  libc6  2.27-3
ii  libgcc11:8.1.0-5
ii  liblzma5   5.2.2-1.3
ii  libssl1.1  1.1.0h-4
ii  libstdc++6 8.1.0-5
ii  libsystemd0238-5
ii  libwrap0   7.6.q-27
ii  lsb-base   9.20170808
ii  zlib1g 1:1.2.11.dfsg-1

apt-cacher-ng recommends no packages.

Versions of packages apt-cacher-ng suggests:
ii  avahi-daemon  0.7-4
pn  doc-base  
ii  libfuse2  2.9.7-1

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#644998: iftop: chooses eth0 as the default interface instead of the default route

[Shawn Landden]

Package: iftop
Version: 1.0~pre4-4
Followup-For: Bug #644998

New version of the patch that supports ipv6-only hosts
-- System Information:
Debian Release: 9.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-6-amd64 (SMP w/1 CPU core)
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 iftop depends on:
ii  libc62.24-11+deb9u3
ii  libncurses5  6.0+20161126-1+deb9u2
ii  libpcap0.8   1.8.1-3
ii  libtinfo56.0+20161126-1+deb9u2

iftop recommends no packages.

iftop suggests no packages.

-- no debconf information
>From 90ce46be76f1ed558a88448d730a47ad31a18b92 Mon Sep 17 00:00:00 2001
From: Shawn Landden 
Date: Sun, 10 Jun 2018 18:33:56 -0700
Subject: [PATCH] options: select interface that is default route (Closes:
 #644998)

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

IPv4 detection first, cause iftop does not work with v4tunnel
---
 options.c | 83 ++-
 1 file changed, 82 insertions(+), 1 deletion(-)

diff --git a/options.c b/options.c
index a075357..0654d46 100644
--- a/options.c
+++ b/options.c
@@ -6,8 +6,13 @@
 
 #include "config.h"
 
+#ifdef __linux__
+#define _GNU_SOURCE
+#endif
+
 #include 
 
+#include 
 #include 
 #include 
 #include 
@@ -90,6 +95,75 @@ static int is_bad_interface_name(char *i) {
 return 0;
 }
 
+/* none of these errors are expected, so I think it is OK to print them */
+static char *get_interface_for_default_route(int ipv6) {
+#ifdef __linux__
+pid_t pid;
+int fds[2];
+int r;
+char buf[4096];
+char *p, *q;
+
+r = pipe2(fds, O_CLOEXEC);
+if (r < 0) {
+fprintf(stderr, "get_interface_for_default_ipv4_route: pipe() failed: 
%s, continuing...", strerror(r));
+return NULL;
+}
+pid = fork();
+if (pid < 0) {
+fprintf(stderr, "get_interface_for_default_ipv4_route: fork() failed: 
%s, continuing...", strerror(r));
+return NULL;
+} else if (pid == 0) {
+/* child */
+r = dup2(fds[0], STDOUT_FILENO);
+if (r < 0) {
+char buf[1] = {'\n'};
+
+/* we have to write something as the other end is expecting 
something */
+r = write(fds[0], &buf, sizeof(buf));
+_exit(EXIT_FAILURE);
+}
+
+if (ipv6)
+execlp("ip", "-6", "route", NULL);
+else
+execlp("ip", "route", NULL);
+char buf[1] = {'\n'};
+
+/* we have to write something as the other end is expecting something 
*/
+r = write(fds[0], &buf, sizeof(buf));
+_exit(EXIT_FAILURE);
+}
+/* parent */
+close(fds[1]);
+r = read(fds[1], &buf, sizeof(buf));
+if (r < 0) {
+fprintf(stderr, "get_interface_for_default_ipv4_route: read() failed: 
%s, continuing...", strerror(r));
+return NULL;
+}
+
+p = strstr((char *)&buf, "default via ");
+if (!p)
+return NULL;
+p += strlen("default via ");
+q = p;
+for (;*p != '\n' && *p; p++)
+;
+*p = '\0';
+p = strstr(q, " dev ");
+if (!p)
+return NULL;
+p += strlen(" dev ");
+q = p;
+for (;*p != ' ' && *p; p++)
+;
+*p = '\0';
+return xstrdup(q);
+#else
+return NULL;
+#endif
+}
+
 /* This finds the first interface which is up and is not the loopback
  * interface or one of the interface types listed in bad_interface_names. */
 static char *get_first_interface(void) {
@@ -123,9 +197,16 @@ static char *get_first_interface(void) {
 
 void options_set_defaults() {
 char *s;
+
+if (!options.interface) /* IPv4. Must come first because iftop does not 
work with v4tunnels.
+
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901283 */
+options.interface = get_interface_for_default_route(0);
+if (!options.interface) /* IPv6*/
+options.interface = get_interface_for_default_route(1);
 /* Should go through the list of interfaces, and find the first one which
  * is up and is not lo or dummy*. */
-options.interface = get_first_interface();
+if (!options.interface)
+options.interface = get_first_interface();
 if (!options.interface)
 options.interface = "eth0";
 
-- 
2.17.1

Bug#891706: #891706 ITP: golang-github-tonistiigi-fsutil -- Incremental file directory sync tools in golang

[Dmitry Smirnov]

There is no repository under 

 https://salsa.debian.org/go-team/packages?filter=fsutil

Also could you please ask upstream to tag releases?

Thanks.

-- 
All the best,
 Dmitry Smirnov

---

Human beings, who are almost unique in having the ability to learn from the
experience of others, are also remarkable for their apparent disinclination
to do so.
-- Mahatma Gandhi

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

Bug#901292: apt-cacher-ng.8: typo: -c vs -C

[Paul Wise]

Package: apt-cacher-ng
Version: 3.1-1
Severity: minor
File: /usr/share/man/man8/apt-cacher-ng.8.gz

There is a typo in the manual page, it says -C is used for adjusting
the configuration directory but earlier in the manual page it says -c
is used for that. Running the binary confirms that the -C option does not exist 
but the -c option does exist and changes the config dir.

$ man apt-cacher-ng  | grep -iP -- '-c\b'
   apt-cacher-ng [-c confdir] [-h] [optname=optvalue ...]
   -c confdir
   be adjusted with the -C option (see systemd service file for details or

$ /usr/sbin/apt-cacher-ng -h | grep -iP -- '-c\b'
Usage: apt-cacher-ng [options] [ -c configdir ] 
-c: configuration directory

$ /usr/sbin/apt-cacher-ng -c tmp-acng
Failed to open config directory

$ /usr/sbin/apt-cacher-ng -C tmp-acng
Not a valid configuration directive: -C
Usage: apt-cacher-ng [options] [ -c configdir ] 

Options:
-h: this help message
-c: configuration directory
-e: on startup, run expiration once
-p: print configuration and exit
-i: ignore configuration loading errors

Most interesting variables:
ForeGround: Don't detach (default: 0)
Port: TCP port number (default: 3142)
CacheDir: /directory/for/storage
LogDir: /directory/for/logfiles

See configuration examples for all directives.

$ mkdir tmp-acng ; /usr/sbin/apt-cacher-ng -c tmp-acng
Error opening file /home/pabs/tmp-acng/*.conf (No such file or directory), 
terminating.

$ mkdir tmp-acng ; /usr/sbin/apt-cacher-ng -C tmp-acng
Not a valid configuration directive: -C
Usage: apt-cacher-ng [options] [ -c configdir ] 

Options:
-h: this help message
-c: configuration directory
-e: on startup, run expiration once
-p: print configuration and exit
-i: ignore configuration loading errors

Most interesting variables:
ForeGround: Don't detach (default: 0)
Port: TCP port number (default: 3142)
CacheDir: /directory/for/storage
LogDir: /directory/for/logfiles

See configuration examples for all directives.

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages apt-cacher-ng depends on:
ii  adduser3.117
ii  debconf [debconf-2.0]  1.5.66
ii  dpkg   1.19.0.5+b1
ii  libbz2-1.0 1.0.6-8.1
ii  libc6  2.27-3
ii  libgcc11:8.1.0-5
ii  liblzma5   5.2.2-1.3
ii  libssl1.1  1.1.0h-4
ii  libstdc++6 8.1.0-5
ii  libsystemd0238-5
ii  libwrap0   7.6.q-27
ii  lsb-base   9.20170808
ii  zlib1g 1:1.2.11.dfsg-1

apt-cacher-ng recommends no packages.

Versions of packages apt-cacher-ng suggests:
ii  avahi-daemon  0.7-4
pn  doc-base  
ii  libfuse2  2.9.7-1

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#901291: RFA: pynliner -- CSS-to-inline-styles conversion tool for HTML - Python 2.x

[Sandro Tosi]

Package: wnpp
Severity: normal

I request an adopter for the pynliner package.

The package description is:
 Because Pynliner uses BeautifulSoup to find the tags specified in the CSS it
 aggressively converts to HTML. This means that templating languages like Mako,
 Genshi, and Jinja will be pounded into valid HTML in the process of applying
 styles.
 .
 This package contains the Python 2 version of pynliner

Bug#901290: chromium: version 68 arm build causes internal compiler error

[Michael Gilbert]

package: src:chromium-browser
severity: grave
version: 68.0.3440.7-1

The version just uploaded to experimental causes an internal compiler
error in gcc on arm [0].

Best wishes,
Mike

[0]https://buildd.debian.org/status/package.php?p=chromium-browser&suite=experimental

Bug#901021: Provide a GTK+ 2 version of Chromium.

[Michael Gilbert]

On Sun, Jun 10, 2018 at 11:34 PM, Gong S wrote:
>>This is normal. GTK2 will eventually be deprecated, just like GTK1
> But GTK3 is dumbed down and lacks many configurations present in GTK2. Also, 
> it uses `dconf` and has no bitmap font support.
> Also, existing GTK2 themes cannot be used in GTK3 (so no Mist theme). And 
> existing GTK3 theme is clearly not designed to be used on a PC.

The livelihood of gtk2 is not my call.  You would need to take that
discussion to the gnome team.

Best wishes,
Mike

Bug#901289: Drop the `logsave` requirement in `/etc/init.d/checkfs.sh`.

[Gong S____]

Package: initscripts
Version: 2.88dsf-59.10

The current version used `logsave` to save `fsck` results.
When `logsave` is not present, the script will fail regardless of the actual FS 
state.
/etc/init.d/checkfs.sh line 101 and 121:
logsave -s $FSCK_LOGFILE fsck $spinner -M -A $fix $force $FSCKTYPES_OPT
`logsave` is a part of `e2fsprogs`. If I do not use EXT filesystems (I use JFS 
on my PC) I can purge this package.

My suggestion:
1. Do not use `logsave`. The process is not there in previous versions.or:
2. If `logsave` is not found just check the FS without using `logsave`.

Bug#901254: gnome-terminal: unable to init server, failed with result 'signal', segfault at 8

[Ernesto Alfonso]

I'm not aware of using broadway. I don't have a broadway service based on
service --status-all, a broadwayd executable, nor either of the
packages libgtk-3-bin libgtk-3-0-dbg installed in my system.

On Sun, Jun 10, 2018 at 7:27 PM Jason Crain  wrote:

> On 2018-06-10, Ernesto Alfonso  wrote:
> > I'm suddenly unable to start gnome terminal after an unexpected shutdown
> due to a hard-disk being
> > removed while the system was running.
> >
> > Looking at the logs, I see the following:
> >
> > >Jun 10 09:26:21 debian-x1 systemd[1008]: Starting GNOME Terminal
> Server...
> > >Jun 10 09:26:21 debian-x1 gnome-terminal-server[20909]: Unable to
> init server: Could not connect: Connection refused
> ...
>
> Are you using broadway? I looked for the source of that error message.
> The most likely place I found is in GTK when it is trying to initialize
> the broadway backend.
>

Bug#901041: libviennacl-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc/libviennacl-dev/README.gz

[Andreas Beckmann]

Followup-For: Bug #901041
Control: found -1 1.7.1+dfsg1-4

You fixed the wrong problem. The Breaks+Replaces may still be needed,
but the underlying problem is not fixed - both libviennacl-dev and
libviennacl-doc ship these files:

  usr/share/doc/libviennacl-dev/README.gz
  usr/share/doc/libviennacl-dev/changelog.gz

This is most likely caused by a behavioral change in dh_installdocs
in debhelper compat level 11.

(Due to upload+testing timing I saw the buster->sid failure before the
sid+sid failure).


Andreas

Bug#901048: gnat-*-x86-64-linux-gnu: missing Conflicts: gnat-5, gnat-6

[Andreas Beckmann]

On 2018-06-08 17:51, Matthias Klose wrote:
> you should not run piuparts against outdated binaries.

These tests take everything available in the Packages files ...

>  I filed #899045
> to remove these packages, but that didn't get yet processed.  Closing
> this issue now.

Interestingly these packages still don't show up in the ftp-master cruft
report ... (otherwise I might have spotted their cruftness).


Andreas

Bug#901185: remove unlisted bash dependecy

[積丹尼 Dan Jacobson]

Why use bash at all if e.g.,

$ checkbashisms /usr/sbin/update-exim4.conf.template
could not find any possible bashisms in bash script 
/usr/sbin/update-exim4.conf.template

means one can just use #!/bin/sh ?

Bug#901220: libreoffice-dictionaries: FTBFS: can't cd to /<>/debian/hunspell-es/usr/share/hunspell

[Andreas Beckmann]

Hi Rene,

On 2018-06-10 11:10, Rene Engelhard wrote:
> On Sun, Jun 10, 2018 at 10:56:31AM +0200, Andreas Beckmann wrote:
>> libreoffice-dictionaries/experimental FTBFS:
> Yes, I have seen this. I *do* look at buildlogs after uploads.

Unfortunately not everone does ... Anyway, I just needed a bug number to
tag a failed rebuild test in experimental :-)

> Will be fixed with a subsequent upload, whenever this will happen.
> Probably with beta2.

No hurry needed, I don't need the package.


Andreas

Bug#901254: gnome-terminal: unable to init server, failed with result 'signal', segfault at 8

[Jason Crain]

On 2018-06-10, Ernesto Alfonso  wrote:
> I'm suddenly unable to start gnome terminal after an unexpected shutdown due 
> to a hard-disk being
> removed while the system was running.
> 
> Looking at the logs, I see the following:
> 
> >Jun 10 09:26:21 debian-x1 systemd[1008]: Starting GNOME Terminal 
> > Server...
> >Jun 10 09:26:21 debian-x1 gnome-terminal-server[20909]: Unable to init 
> > server: Could not connect: Connection refused
...

Are you using broadway? I looked for the source of that error message.
The most likely place I found is in GTK when it is trying to initialize
the broadway backend.

Bug#901283: iftop: v4tunnel support (IPv6 tunnels like Hurricane Electric)

[Shawn Landden]

Package: iftop
Version: 1.0~pre4-4
Followup-For: Bug #901283


Dear Maintainer,

submitted upstream: https://github.com/the-tcpdump-group/libpcap/issues/725

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

Kernel: Linux 4.9.0-6-amd64 (SMP w/1 CPU core)
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 iftop depends on:
ii  libc62.24-11+deb9u3
ii  libncurses5  6.0+20161126-1+deb9u2
ii  libpcap0.8   1.8.1-3
ii  libtinfo56.0+20161126-1+deb9u2

iftop recommends no packages.

iftop suggests no packages.

-- no debconf information

Bug#644998: iftop: chooses eth0 as the default interface instead of the default route

[Shawn Landden]

>
> Here is a patch to fix the problem.
>

 This will make iftop (soft) depend on "iproute2"

Bug#644998: iftop: chooses eth0 as the default interface instead of the default route

[Shawn Landden]

Package: iftop
Version: 1.0~pre4-4
Followup-For: Bug #644998

tags 644998 patch

Dear Maintainer,

Here is a patch to fix the problem.

submitted upstream: 
http://lists.beasts.org/pipermail/iftop-users/2018-June/000472.html

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

Kernel: Linux 4.9.0-6-amd64 (SMP w/1 CPU core)
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 iftop depends on:
ii  libc62.24-11+deb9u3
ii  libncurses5  6.0+20161126-1+deb9u2
ii  libpcap0.8   1.8.1-3
ii  libtinfo56.0+20161126-1+deb9u2

iftop recommends no packages.

iftop suggests no packages.

-- no debconf information
>From cdc0e3de74f529ff7c1fbc5648a9b09d1ada998a Mon Sep 17 00:00:00 2001
From: Shawn Landden 
Date: Sun, 10 Jun 2018 18:33:56 -0700
Subject: [PATCH] options: select interface that is IPv4 default route (Closes:
 #644998)

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644998
---
 options.c | 77 ++-
 1 file changed, 76 insertions(+), 1 deletion(-)

diff --git a/options.c b/options.c
index a075357..efff2c7 100644
--- a/options.c
+++ b/options.c
@@ -6,8 +6,13 @@
 
 #include "config.h"
 
+#ifdef __linux__
+#define _GNU_SOURCE
+#endif
+
 #include 
 
+#include 
 #include 
 #include 
 #include 
@@ -90,6 +95,72 @@ static int is_bad_interface_name(char *i) {
 return 0;
 }
 
+/* none of these errors are expected, so I think it is OK to print them */
+static char *get_interface_for_default_ipv4_route(void) {
+#ifdef __linux__
+pid_t pid;
+int fds[2];
+int r;
+char buf[4096];
+char *p, *q;
+
+r = pipe2(fds, O_CLOEXEC);
+if (r < 0) {
+fprintf(stderr, "get_interface_for_default_ipv4_route: pipe() failed: 
%s, continuing...", strerror(r));
+return NULL;
+}
+pid = fork();
+if (pid < 0) {
+fprintf(stderr, "get_interface_for_default_ipv4_route: fork() failed: 
%s, continuing...", strerror(r));
+return NULL;
+} else if (pid == 0) {
+/* child */
+r = dup2(fds[0], STDOUT_FILENO);
+if (r < 0) {
+char buf[1] = {'\n'};
+
+/* we have to write something as the other end is expecting 
something */
+r = write(fds[0], &buf, sizeof(buf));
+_exit(EXIT_FAILURE);
+}
+
+execlp("ip", /* add "-6", here to make default IPv6 route */ "route", 
NULL);
+char buf[1] = {'\n'};
+
+/* we have to write something as the other end is expecting something 
*/
+r = write(fds[0], &buf, sizeof(buf));
+_exit(EXIT_FAILURE);
+}
+/* parent */
+close(fds[1]);
+r = read(fds[1], &buf, sizeof(buf));
+if (r < 0) {
+fprintf(stderr, "get_interface_for_default_ipv4_route: read() failed: 
%s, continuing...", strerror(r));
+return NULL;
+}
+
+p = strstr((char *)&buf, "default via ");
+if (!p)
+return NULL;
+p += strlen("default via ");
+q = p;
+for (;*p != '\n' && *p; p++)
+;
+*p = '\0';
+p = strstr(q, " dev ");
+if (!p)
+return NULL;
+p += strlen(" dev ");
+q = p;
+for (;*p != ' ' && *p; p++)
+;
+*p = '\0';
+return xstrdup(q);
+#else
+return NULL;
+#endif
+}
+
 /* This finds the first interface which is up and is not the loopback
  * interface or one of the interface types listed in bad_interface_names. */
 static char *get_first_interface(void) {
@@ -123,9 +194,13 @@ static char *get_first_interface(void) {
 
 void options_set_defaults() {
 char *s;
+
+if (!options.interface)
+options.interface = get_interface_for_default_ipv4_route();
 /* Should go through the list of interfaces, and find the first one which
  * is up and is not lo or dummy*. */
-options.interface = get_first_interface();
+if (!options.interface)
+options.interface = get_first_interface();
 if (!options.interface)
 options.interface = "eth0";
 
-- 
2.17.1

Bug#867461: Bug#858539: should ca-certificates certdata.txt synchronize across all suites?

[Michael Shuler]

On 06/08/2018 03:37 PM, Adam D. Barratt wrote:


Ping? We're a week away from the final chance to get an update into
jessie-as-oldstable before it becomes jessie-lts.


Thanks for the ping. I updated the debian-jessie branch of 
ca-certificates with mozilla bundle 2.22, and it's ready to be uploaded.


Thijs, might you have a chance to upload 20141019+deb8u4 to 
jessie-updates? If not, perhaps we can wrangle someone else to help.


commit: ce1498e496b749f71fd96d60942d2c2aa7fdf0ca

$ git diff --stat debian/20141019+deb8u3 debian-jessie
 debian/changelog |74 +
 debian/control   | 1 -
 mozilla/certdata.txt | 28220 
+--

 mozilla/nssckbi.h|39 +-
 4 files changed, 10787 insertions(+), 17547 deletions(-)

Thanks all!
--
Kind regards,
Michael

Bug#901287: RFS: deepin-qt5dxcb-plugin/1.1.8.8-1

[Yanhao Mo]

Package: sponsorship-requests
Severity: normal

  Dear mentors,

  I am looking for a sponsor for my package "deepin-qt5dxcb-plugin"

 * Package name: deepin-qt5dxcb-plugin
   Version : 1.1.8.8-1
   Upstream Author : Deepin Technology Co., Ltd.
 * URL : https://github.com/linuxdeepin/qt5dxcb-plugin
 * License : GPL-3+
   Section : libs

  It builds those binary packages:

qt5dxcb-plugin - Qt platform theme integration plugin for DDE

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

  https://mentors.debian.net/package/deepin-qt5dxcb-plugin


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

dget -x 
https://mentors.debian.net/debian/pool/main/d/deepin-qt5dxcb-plugin/deepin-qt5dxcb-plugin_1.1.8.8-1.dsc

  More information about hello can be obtained from 
https://salsa.debian.org/pkg-deepin-team/deepin-qt5dxcb-plugin .

  Changes since the last upload:

  deepin-qt5dxcb-plugin (1.1.8.8-1) unstable; urgency=medium

  * New upstream version 1.1.8.8
  * Use pkg-deepin-de...@lists.alioth.debian.org in maintainer field.
  * d/control: Add new uploader Yanhao Mo .
  * d/copyright: Drop Files-Excluded filed.

 -- Yanhao Mo   Sun, 10 Jun 2018 10:45:12 +0800

-- 
Yanhao Mo


signature.asc
Description: PGP signature

Bug#901286: RFS: deepin-screenshot/4.0.15-1

[Yanhao Mo]

Package: sponsorship-requests
Severity: normal

  Dear mentors,

  I am looking for a sponsor for my package "deepin-screenshot"

 * Package name: deepin-screenshot
   Version : 4.0.15-1
   Upstream Author : Deepin Technology Co., Ltd.
 * URL : https://github.com/linuxdeepin/deepin-screenshot
 * License : GPL-3+
   Section : utils

  It builds those binary packages:

deepin-screenshot - Advanced screen shoting tool

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

  https://mentors.debian.net/package/deepin-screenshot


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

dget -x 
https://mentors.debian.net/debian/pool/main/d/deepin-screenshot/deepin-screenshot_4.0.15-1.dsc

  More information about hello can be obtained from 
https://salsa.debian.org/pkg-deepin-team/deepin-screenshot

  Changes since the last upload:

deepin-screenshot (4.0.15-1) unstable; urgency=medium

  * New upstream version 4.0.15

 -- Yanhao Mo   Sun, 10 Jun 2018 10:22:47 +0800


-- 
Yanhao Mo


signature.asc
Description: PGP signature

Bug#901284: RFS: deepin-movie-reborn/3.2.7-1

[Yanhao Mo]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "deepin-movie-reborn"

* Package name: deepin-movie-reborn
  Version : 3.2.7-1
  Upstream Author : Deepin Technology Co., Ltd.
* URL : https://github.com/linuxdeepin/deepin-movie-reborn
* License : GPL-3+
  Section : video

It builds those binary packages:

  deepin-movie - Deepin movie player
  libdmr-dev - Deepin movie player - widget library (development files)
  libdmr0.1  - Deepin movie player - widget library

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

  https://mentors.debian.net/package/deepin-movie-reborn

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

  dget -x 
https://mentors.debian.net/debian/pool/main/d/deepin-movie-reborn/deepin-movie-reborn_3.2.7-1.dsc

More information about hello can be obtained from 
https://salsa.debian.org/pkg-deepin-team/deepin-movie-reborn

Changes since the last upload:

deepin-movie-reborn (3.2.7-1) unstable; urgency=medium

  * New upstream version 3.2.7
+ Run async append job conditionally.
+ libdmr: Support pause on start.

 -- Yanhao Mo   Sun, 10 Jun 2018 10:30:00 +0800

-- 
Yanhao Mo


signature.asc
Description: PGP signature

Bug#901285: RFS: deepin-notifications/3.3.3-1

[Yanhao Mo]

Package: sponsorship-requests
Severity: normal

  Dear mentors,

  I am looking for a sponsor for my package "deepin-notifications"

 * Package name: deepin-notifications
   Version : 3.3.3-1
   Upstream Author : Deepin Technology Co., Ltd.
 * URL : https://github.com/linuxdeepin/deepin-notifications
 * License : GPL-3+
   Section : x11

  It builds those binary packages:

deepin-notifications - System notifications for Deepin Desktop Environment

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

  https://mentors.debian.net/package/deepin-notifications


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

dget -x 
https://mentors.debian.net/debian/pool/main/d/deepin-notifications/deepin-notifications_3.3.3-1.dsc

  More information about hello can be obtained from 
https://salsa.debian.org/pkg-deepin-team/deepin-notifications

  Changes since the last upload:

deepin-notifications (3.3.3-1) unstable; urgency=medium

  * New upstream version 3.3.3

 -- Yanhao Mo   Sun, 10 Jun 2018 10:21:08 +0800

-- 
Yanhao Mo


signature.asc
Description: PGP signature

Bug#899267: Reopen: Bug#899267: ruby2.5: FTBFS on kfreebsd-any

[Antonio Terceiro]

On Sun, 10 Jun 2018 23:38:18 +0200 Svante Signell  
wrote:
> reopen -1
> found 899267 2.5.1-2
> thanks
> 
> Hello,
> 
> Unfortunately the patch 0006-fix-kfreebsd-build.patch was not applied,
> resulting in a failing build. I'm attaching that file again, now named 
> 0007-fix-kfreebsd-build.patch

Was this patch submitted upstream?


signature.asc
Description: PGP signature

Bug#884484: python-cryptography-vectors/2.2.2-1 appears to break python-cryptography in testing

[Tristan Seligmann]

On Sun, 10 Jun 2018 at 21:57 Paul Gevers  wrote:

> Hi
>
> On 10-06-18 21:34, Tristan Seligmann wrote:
> > -vectors exists purely for the benefit of the tests, nothing outside the
> > tests uses the vectors. If you are not running the tests, having a
> > mismatched version of -vectors will have no effect.
>
> Thanks for clarifying. Just for my understanding, did you ever
> considered to add these vectors (as a second tar ball in the source 3
> format) to the source package of python-cryptography?
>

I think this might actually be the ideal solution, all else being equal,
but a lot of the tooling in use (dh_python, pybuild, git-dpm, etc.)
unfortunately does not handle this scenario well, so I haven't attempted it.

Bug#901283: iftop: v4tunnel support (IPv6 tunnels like Hurricane Electric)

[Shawn Landden]

Package: iftop
Version: 1.0~pre4-4
Severity: wishlist

Dear Maintainer,

It would be nice if you could attach iftop to v4tunnels. Instead iftop
reports nothing for such interfaces, and reports the traffic under the ipv4 
interface
as a single connection to the ipv4 end of the tunnel. Here is my 
/etc/network/interfaces:

 auto lo
  iface lo inet loopback

 auto eth0
  iface eth0 inet static
   address 198.46.198.198
   gateway 198.46.198.1
   netmask 255.255.255.0
   dns-nameservers 8.8.8.8 8.8.4.4

iface he-ipv6 inet6 v4tunnel
address 2001:470:c:238::2
netmask 64
#LA 0.5ms
endpoint 66.220.18.42
local 198.46.198.198
ttl 255
gateway 2001:470:c:238::1
up ip addr add 2001:470:d:238::1 dev he-ipv6

Thanks,

Shawn Landden

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

Kernel: Linux 4.9.0-6-amd64 (SMP w/1 CPU core)
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 iftop depends on:
ii  libc62.24-11+deb9u3
ii  libncurses5  6.0+20161126-1+deb9u2
ii  libpcap0.8   1.8.1-3
ii  libtinfo56.0+20161126-1+deb9u2

iftop recommends no packages.

iftop suggests no packages.

-- no debconf information

Bug#884440: zimlib: Please package new 3.1.0 upstream version

[Kunal Mehta]

retitle 884440 Please package new 3.3.0 upstream version
thanks

upstream is now at 3.3.0. I went ahead and prepared most of the
packaging for this at
. Would it
help if I created a merge request on salsa? The remaining tasks should
be to generate the rest of the symbols files (I'm not sure how to do
that), and update the changelog.

This is needed so I can upgrade libkiwix and start packaging the rest of
the kiwix suite.

-- Kunal



signature.asc
Description: OpenPGP digital signature

Bug#901274: [lintian] warn about *.md,.eslintrc, .npmignore, LICENSE, CHANGES, PATENTS, *.woff, *.ttf, *.woff.? under /usr/lib/node (may be /usr/lib ?)

[Chris Lamb]

Hi Bastien, 

> On Mon, Jun 11, 2018 at 12:07 AM, Chris Lamb  wrote:
> > Hi Bastien,
> >
> >> > Unfortunately, I don't think these commits reach the level of quality
> >> > that Debian Developers would expect from Lintian.
> >>
> >> Ok could you get a glimpse at README branch
> >
> > Could you move the other changes to this branch too (or a "901274"
> > branch/MR or something?)  :)
> 
> Did you prefer a reset or reset of master ?

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


Regards,

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

Bug#901274: [lintian] warn about *.md,.eslintrc, .npmignore, LICENSE, CHANGES, PATENTS, *.woff, *.ttf, *.woff.? under /usr/lib/node (may be /usr/lib ?)

[Chris Lamb]

Hi Bastien ROUCARIES,

> On Mon, Jun 11, 2018 at 12:07 AM, Chris Lamb  wrote:
> > Hi Bastien,
> >
> >> > Unfortunately, I don't think these commits reach the level of quality
> >> > that Debian Developers would expect from Lintian.
> >>
> >> Ok could you get a glimpse at README branch
> >
> > Could you move the other changes to this branch too (or a "901274"
> > branch/MR or something?)  :)
> 
> Did you prefer a reset or reset of master ?

A reset or a reset? 
 
> Bastien
> >
> >
> > Best wishes,
> >
> > --
> >   ,''`.
> >  : :'  : Chris Lamb
> >  `. `'`  la...@debian.org / chris-lamb.co.uk
> >`-


Regards,

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

Bug#901274: [lintian] warn about *.md,.eslinltrc, .npmignore, LICENSE, CHANGES, PATENTS, *.woff, *.ttf, *.woff.? under /usr/lib/node (may be /usr/lib ?)

[Chris Lamb]

Hi Bastien ROUCARIES,

> On Mon, Jun 11, 2018 at 12:07 AM, Chris Lamb  wrote:
> > Hi Bastien,
> 
> >> > Unfortunately, I don't think these commits reach the level of quality
> >> > that Debian Developers would expect from Lintian.
> >>
> >> Ok could you get a glimpse at README branch
> >
> > Could you move the other changes to this branch too (or a "901274"
> > branch/MR or something?)  :)
> 
> Did you prefer a reset or reset of master ?
> 
> Bastien
> >
> >
> > Best wishes,
> >
> > --
> >   ,''`.
> >  : :'  : Chris Lamb
> >  `. `'`  la...@debian.org / chris-lamb.co.uk
> >`-


Regards,

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

Bug#901185: [Debconf-devel] Bug#901185: me too

[Colin Watson]

On Sun, Jun 10, 2018 at 04:04:13PM +0200, Andreas Metzler wrote:
> On 2018-06-10 Colin Watson  wrote:
> > On Sun, Jun 10, 2018 at 03:03:28PM +0200, Andreas Metzler wrote:
> >> I have tried debugging the issue to get a minimal testcase. I have had
> >> some success. The issue is triggered by debconf.
> >> /usr/share/debconf/confmodule changes IFS to \n and with bash5 this
> >> change is persistent and breaks the maintainerscript.
> 
> > Does this patch help?
> 
> yes, resetting IFS to its default value in confmodule helps.

Thanks.  For completeness, could you try this variant patch?  If shells
are going to be unreliable about setting IFS in this way, then I'd
rather just separate out the assignments altogether.

diff --git a/confmodule b/confmodule
index 8347c0b0..3ef7a309 100644
--- a/confmodule
+++ b/confmodule
@@ -42,10 +42,11 @@ _db_cmd () {
_db_internal_IFS="$IFS"
IFS=' '
printf '%s\n' "$*" >&3
-   IFS="$_db_internal_IFS"
# Set to newline to get whole line.
IFS='
-' read -r _db_internal_line
+'
+   read -r _db_internal_line
+   IFS="$_db_internal_IFS"
# Disgusting, but it's the only good way to split the line,
# preserving all other whitespace.
RET="${_db_internal_line#[! ][  ]}"

(This does still seem like a bash bug though, unless there's some arcane
interpretation of the standards that I'm unaware of.)

Cheers,

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

Bug#899006: stretch-pu: package intel-microcode/3.20180425.1~deb9u1

[Henrique de Moraes Holschuh]

On Sat, 09 Jun 2018, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Fri, 2018-05-18 at 10:32 -0300, Henrique de Moraes Holschuh wrote:
> > I'd like to update the intel-microcode package in Debian stretch.
> > 
> > This update adds the microcode-side fix for CVE-2017-5715 aka Spectre
> > v2.
> > 
> 
> Please go ahead.

Uploaded.  Thank you!

-- 
  Henrique Holschuh

Bug#901243: nm-applet

[Le Déchaîné]

I'm guessing it's the same for nm-applet. I got no network manager
applet and trash applet either. System/Preferences is kinda empty too.

It may be the reason why I have to login and "startx" now (well...
sudo ifconfig eth0 up, sudo dhclient, and then startx).

Some interesting logs/crash.

Syslog:
Jun 10 06:48:26 symphony systemd[1]: Reloading.
Jun 10 06:48:27 symphony systemd[1]: Stopping Light Display Manager...
Jun 10 06:48:27 symphony at-spi-bus-launcher[1407]: XIO:  fatal IO
error 11 (Resource temporarily unavailable) on X server ":0"
Jun 10 06:48:27 symphony at-spi-bus-launcher[1407]:   after 82277
requests (82277 known processed) with 0 events remaining.
Jun 10 06:48:27 symphony pulseaudio[1446]: ICE default IO error
handler doing an exit(), pid = 1446, errno = 11
Jun 10 06:48:27 symphony trashapplet[1468]: trashapplet: Fatal IO
error 11 (Ressource temporairement non disponible) on X server :0.
Jun 10 06:48:27 symphony systemd[1361]: pulseaudio.service: Main
process exited, code=exited, status=1/FAILURE
Jun 10 06:48:27 symphony systemd[1361]: pulseaudio.service: Failed
with result 'exit-code'.
Jun 10 06:48:27 symphony [1469]: wnck-applet: Fatal IO error 11
(Ressource temporairement non disponible) on X server :0.
Jun 10 06:48:27 symphony mate-multiload-[1559]: mate-multiload-applet:
Fatal IO error 11 (Ressource temporairement non disponible) on X
server :0.
Jun 10 06:48:27 symphony notification-ar[1560]:
notification-area-applet: Fatal IO error 11 (Ressource temporairement
non disponible) on X server :0.
Jun 10 06:48:27 symphony clock-applet[1561]: clock-applet: Fatal IO
error 11 (Ressource temporairement non disponible) on X server :0.
Jun 10 06:48:27 symphony systemd[1361]: pulseaudio.service: Service
hold-off time over, scheduling restart.
Jun 10 06:48:27 symphony systemd[1361]: pulseaudio.service: Scheduled
restart job, restart counter is at 1.
Jun 10 06:48:27 symphony systemd[1361]: Stopped Sound Service.
Jun 10 06:48:27 symphony systemd[1361]: Starting Sound Service...
Jun 10 06:48:27 symphony rtkit-daemon[745]: Successfully made thread
15179 of process 15179 (n/a) owned by '1000' high priority at nice
level -11.
Jun 10 06:48:27 symphony rtkit-daemon[745]: Supervising 1 threads of 1
processes of 1 users.
Jun 10 06:48:27 symphony pulseaudio[15179]: W: [pulseaudio] pid.c:
Stale PID file, overwriting.
Jun 10 06:48:27 symphony systemd[1]: Stopped Light Display Manager.
Jun 10 06:48:27 symphony rtkit-daemon[745]: Supervising 1 threads of 1
processes of 1 users.
Jun 10 06:48:27 symphony rtkit-daemon[745]: Successfully made thread
15180 of process 15179 (n/a) owned by '1000' RT at priority 5.
Jun 10 06:48:27 symphony rtkit-daemon[745]: Supervising 2 threads of 1
processes of 1 users.
Jun 10 06:48:27 symphony rtkit-daemon[745]: Supervising 2 threads of 1
processes of 1 users.
Jun 10 06:48:27 symphony rtkit-daemon[745]: Successfully made thread
15181 of process 15179 (n/a) owned by '1000' RT at priority 5.
Jun 10 06:48:27 symphony rtkit-daemon[745]: Supervising 3 threads of 1
processes of 1 users.
Jun 10 06:48:27 symphony pulseaudio[15179]: E: [pulseaudio]
bluez5-util.c: GetManagedObjects() failed:
org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 2
matched rules; type="method_call", sender=":1.338" (uid=1000 pid=15179
comm="/usr/bin/pulseaudio --daemonize=no ")
interface="org.freedesktop.DBus.ObjectManager"
member="GetManagedObjects" error name="(unset)" requested_reply="0"
destination="org.bluez" (bus)
Jun 10 06:48:27 symphony systemd[1361]: Started Sound Service.
(...)
Messages:
Jun 10 06:49:49 symphony NetworkManager[764]: 
[1528627789.7842] caught SIGTERM, shutting down normally.
Jun 10 06:49:49 symphony NetworkManager[764]: 
[1528627789.8243] exiting (success)

(Also in syslog...)
Jun 10 10:37:20 symphony dhclient[18150]: execve
(/usr/lib/NetworkManager/nm-dhcp-helper, ...): No such file or
directory
(...)
Jun 10 16:56:52 symphony kernel: [196727.991463] traps:
mate-settings-d[18477] trap int3 ip:7f4e5abb1c41 sp:7ffcaa1aa750
error:0 in libglib-2.0.so.0.5600.1[7f4e5ab6+113000]
Jun 10 16:56:53 symphony kernel: [196728.900334] traps:
mate-settings-d[18495] trap int3 ip:7f2a4f869c41 sp:7ffe5a9e7d00
error:0 in libglib-2.0.so.0.5600.1[7f2a4f818000+113000]
Jun 10 16:56:54 symphony wnck-applet[18502]: g_object_set: assertion
'G_IS_OBJECT (object)' failed
Jun 10 16:56:54 symphony clock-applet[18575]: Negative content width
-1 (allocation 1, extents 1x1) while allocating gadget (node button,
owner GtkToggleButton)
Jun 10 16:56:56 symphony notification-ar[18576]:
GDBus.Error:org.freedesktop.DBus.Error.UnknownObject: No such object
path '/NO_DBUSMENU'

Bug#901274: [lintian] warn about *.md,.eslintrc, .npmignore, LICENSE, CHANGES, PATENTS, *.woff, *.ttf, *.woff.? under /usr/lib/node (may be /usr/lib ?)

[Bastien ROUCARIES]

On Mon, Jun 11, 2018 at 12:07 AM, Chris Lamb  wrote:
> Hi Bastien,
>
>> > Unfortunately, I don't think these commits reach the level of quality
>> > that Debian Developers would expect from Lintian.
>>
>> Ok could you get a glimpse at README branch
>
> Could you move the other changes to this branch too (or a "901274"
> branch/MR or something?)  :)

Did you prefer a reset or reset of master ?

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

Bug#901274: [lintian] warn about *.md,.eslintrc, .npmignore, LICENSE, CHANGES, PATENTS, *.woff, *.ttf, *.woff.? under /usr/lib/node (may be /usr/lib ?)

[Chris Lamb]

Hi Bastien,

> > Unfortunately, I don't think these commits reach the level of quality
> > that Debian Developers would expect from Lintian.
> 
> Ok could you get a glimpse at README branch

Could you move the other changes to this branch too (or a "901274"
branch/MR or something?)  :)


Best wishes,

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

Bug#901274: [lintian] warn about *.md,.eslintrc, .npmignore, LICENSE, CHANGES, PATENTS, *.woff, *.ttf, *.woff.? under /usr/lib/node (may be /usr/lib ?)

[Bastien ROUCARIES]

On Sun, Jun 10, 2018 at 11:09 PM, Chris Lamb  wrote:
> Hi Bastien
>
>> Just see it. Will corects thanks
>
> May I kindly suggest doing this work on a branch?
>
> I am happy to review your grammar and spelling but I would very much
> like to keep the "master" branch releasable at any time.
>
> Unfortunately, I don't think these commits reach the level of quality
> that Debian Developers would expect from Lintian.

Ok could you get a glimpse at README branch

Bastien
>
>> Sorry for the delay I was removing a scratch on my screen with
>> toothpaste...
>
> Uhh.
>
>
> Regards,
>
> --
>   ,''`.
>  : :'  : Chris Lamb
>  `. `'`  la...@debian.org / chris-lamb.co.uk
>`-

Bug#898809: lintian -F internal error: cannot run shared-libs check on package binary

[Chris Lamb]

tags 898809 + pending
thanks

Fixed in Git, pending upload:

  
https://salsa.debian.org/lintian/lintian/commit/b8e38a685f1bd13217c7ae7e89b455a296177b33

  debian/changelog | 5 +
  helpers/coll/objdump-info-helper | 3 ++-
  2 files changed, 7 insertions(+), 1 deletion(-)


Regards,

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

Bug#777439: Hello..........

[Rosita]

Hello my dear
My name is Rosita i am interested in you please i will like us to know
much better if you don't mind you can reply me in this
email,(rosita.di...@yahoo.com)so that i can send you my picture and
tell you more about myself, i will wait for your reply thank
you,from
Rosita

Bug#901021: Provide a GTK+ 2 version of Chromium.

[Michael Gilbert]

control: tag -1 wontfix
control: severity -1 wishlist

On Fri, Jun 8, 2018 at 12:51 AM, USER 65534 wrote:
> Starting from version 63.0.3239.84-1, Chromium is compiled against GKT+ 3.
> This is a bad idea.
> I have noticed the huge trend in Debian's repo. More and more packages are 
> compiled against GTK3 instead of GTK2.

This is normal.  GTK2 will eventually be deprecated, just like GTK1
long ago.  In fact, its already started [0].

> GTK+3 is not an upgrade from GTK+ 2, it is a bastardization.

Wasn't GTK2 also a bastardization of GTK1?

> My suggestion is provide two packages, "chromium-gtk2" and "chromium-gtk3", 
> compiled against GTK2 and GTK3 respectively.

This would require building from source twice (and keeping chromium
buildable with gtk2, which upstream cares little about now).  It
already takes way too much time to build chromium once.

That said, a binary package containing chromium's source has been
requested and may happen.  Many kinds of alternative chromium builds
could be done if that were available.

Best wishes,
Mike

[0] https://lists.debian.org/debian-devel/2017/10/msg00299.html
[1] https://bugs.debian.org/893448

Bug#901269: radeontop FTCBFS: uses the build architecture pkg-config

[John Paul Adrian Glaubitz]

Hi Helmut!

On 06/10/2018 08:55 PM, Helmut Grohne wrote:
> Please consider applying the attached patch.

Thanks for the patch. Wouldn't it make more sense though to just send the
patch upstream? Upstream has a github repository, so opening a pull request
should be easy. I can do that if you don't have the time though.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#899267: Reopen: Bug#899267: ruby2.5: FTBFS on kfreebsd-any

[Svante Signell]

reopen -1
found 899267 2.5.1-2
thanks

Hello,

Unfortunately the patch 0006-fix-kfreebsd-build.patch was not applied,
resulting in a failing build. I'm attaching that file again, now named 
0007-fix-kfreebsd-build.patch

Thanks!
On Mon, 2018-05-21 at 21:45 +, Debian Bug Tracking System wrote:
> Thank you for filing a new Bug report with Debian.
> 
> If you wish to submit further information on this problem, please
> send it to 899...@bugs.debian.org.
Index: ruby2.5-2.5.1/ext/socket/option.c
===
--- ruby2.5-2.5.1.orig/ext/socket/option.c
+++ ruby2.5-2.5.1/ext/socket/option.c
@@ -10,6 +10,7 @@ VALUE rb_cSockOpt;
 #if defined(__linux__) || \
 defined(__GNU__) /* GNU/Hurd */ || \
 defined(__FreeBSD__) || \
+defined(__FreeBSD_kernel__) || \
 defined(__DragonFly__) || \
 defined(__APPLE__) || \
 defined(_WIN32) || \
Index: ruby2.5-2.5.1/ext/socket/raddrinfo.c
===
--- ruby2.5-2.5.1.orig/ext/socket/raddrinfo.c
+++ ruby2.5-2.5.1/ext/socket/raddrinfo.c
@@ -1670,10 +1670,21 @@ addrinfo_mload(VALUE self, VALUE ary)
 INIT_SOCKADDR_UN(&uaddr, sizeof(struct sockaddr_un));
 
 StringValue(v);
+#ifdef __FreeBSD_kernel__
+	/* sys/un.h defines struct sockaddr_un as:
+	   char sun_path[104];
+	   char __sun_user_compat[4];
+	*/
+if (sizeof(uaddr.sun_path) + 4 < (size_t)RSTRING_LEN(v))
+rb_raise(rb_eSocket,
+"too long AF_UNIX path (%"PRIuSIZE" bytes given but %"PRIuSIZE" bytes max)",
+(size_t)RSTRING_LEN(v), sizeof(uaddr.sun_path) + 4);
+#else
 if (sizeof(uaddr.sun_path) < (size_t)RSTRING_LEN(v))
 rb_raise(rb_eSocket,
 "too long AF_UNIX path (%"PRIuSIZE" bytes given but %"PRIuSIZE" bytes max)",
 (size_t)RSTRING_LEN(v), sizeof(uaddr.sun_path));
+#endif
 memcpy(uaddr.sun_path, RSTRING_PTR(v), RSTRING_LEN(v));
 len = (socklen_t)sizeof(uaddr);
 memcpy(&ss, &uaddr, len);
@@ -2319,10 +2330,21 @@ addrinfo_unix_path(VALUE self)
 if (e < s)
 rb_raise(rb_eSocket, "too short AF_UNIX address: %"PRIuSIZE" bytes given for minimum %"PRIuSIZE" bytes.",
 (size_t)rai->sockaddr_len, (size_t)(s - (char *)addr));
+#ifdef __FreeBSD_kernel__
+	/* sys/un.h defines struct sockaddr_un as:
+	   char sun_path[104];
+	   char __sun_user_compat[4];
+	*/
+if (addr->sun_path + sizeof(addr->sun_path) + 4 < e)
+rb_raise(rb_eSocket,
+"too long AF_UNIX path (%"PRIuSIZE" bytes given but %"PRIuSIZE" bytes max)",
+(size_t)(e - addr->sun_path), sizeof(addr->sun_path) + 4);
+#else
 if (addr->sun_path + sizeof(addr->sun_path) < e)
 rb_raise(rb_eSocket,
 "too long AF_UNIX path (%"PRIuSIZE" bytes given but %"PRIuSIZE" bytes max)",
 (size_t)(e - addr->sun_path), sizeof(addr->sun_path));
+#endif
 while (s < e && *(e-1) == '\0')
 e--;
 return rb_str_new(s, e-s);
Index: ruby2.5-2.5.1/test/fiddle/test_handle.rb
===
--- ruby2.5-2.5.1.orig/test/fiddle/test_handle.rb
+++ ruby2.5-2.5.1/test/fiddle/test_handle.rb
@@ -169,6 +169,7 @@ module Fiddle
 end unless /mswin|mingw/ =~ RUBY_PLATFORM
 
 def test_dlerror
+  return /kfreebsd/ =~ RUBY_PLATFORM
   # FreeBSD (at least 7.2 to 7.2) calls nsdispatch(3) when it calls
   # getaddrinfo(3). And nsdispatch(3) doesn't call dlerror(3) even if
   # it calls _nss_cache_cycle_prevention_function with dlsym(3).
@@ -177,7 +178,7 @@ module Fiddle
   require 'socket'
   Socket.gethostbyname("localhost")
   Fiddle.dlopen("/lib/libc.so.7").sym('strcpy')
-end if /freebsd/=~ RUBY_PLATFORM
+end if /freebsd/ =~ RUBY_PLATFORM
 
 def test_no_memory_leak
   assert_no_memory_leak(%w[-W0 -rfiddle.so], '', '100_000.times {Fiddle::Handle.allocate}; GC.start', rss: true)
Index: ruby2.5-2.5.1/test/socket/test_socket.rb
===
--- ruby2.5-2.5.1.orig/test/socket/test_socket.rb
+++ ruby2.5-2.5.1/test/socket/test_socket.rb
@@ -507,7 +507,7 @@ class TestSocket < Test::Unit::TestCase
   end
 
   def test_bintime
-return if /freebsd/ !~ RUBY_PLATFORM
+return if /freebsd/ !~ RUBY_PLATFORM || /kfreebsd/ =~ RUBY_PLATFORM
 t1 = Time.now.strftime("%Y-%m-%d")
 stamp = nil
 Addrinfo.udp("127.0.0.1", 0).bind {|s1|

Bug#901282: anarchism: typo in section C9

[Jeff Cliff]

Package: anarchism
Version: 15.0-2
Severity: minor
Tags: patch

Dear Maintainer,

as per ubuntu bug 
https://bugs.launchpad.net/ubuntu/+source/anarchism/+bug/1412104

in both 15.0-2 and 15.1-6, there is an extra 'e' in 'meet'
( Expectations are not "meet", expectations are met ) in section C9

patch:

diff -rupN anarchism-14.0/html/secC9.html anarchism-14.0-patch/html/secC9.html
--- anarchism-14.0/html/secC9.html2008-10-16 21:34:44.0 -0400
+++ anarchism-14.0-patch/html/secC9.html  2015-01-17 22:54:39.12346 -0500
@@ -91,7 +91,7 @@ full unemployment would cause inflation
 rises onto consumers. This class based analysis, obviously, did not fit
  in well with the panglossian assumptions of neo-classical economics. Yet
   basing an analysis on individual expectations does not answer the question
   -whether these expectations are meet. With strong organisation and a 
willingness
   +whether these expectations are met. With strong organisation and a 
willingness
to act, workers can increase their wages
 to counteract inflation. This means that there are two main options within
  capitalism. The first option is to use price controls to stop capitalists
  @@ -2430,4 +2430,4 @@ cycle and so unemployment).
   

 
 -
 \ No newline at end of file
 +



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

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

Versions of packages anarchism depends on:
ii  xdg-utils  1.1.1-1+deb9u1

anarchism recommends no packages.

Versions of packages anarchism suggests:
ii  elinks [www-browser] 0.12~pre6-12
ii  sugar-browse-activity [www-browser]  200+20170502-1

-- no debconf information
diff -rupN anarchism-14.0/html/secC9.html anarchism-14.0-patch/html/secC9.html
--- anarchism-14.0/html/secC9.html  2008-10-16 21:34:44.0 -0400
+++ anarchism-14.0-patch/html/secC9.html2015-01-17 22:54:39.12346 
-0500
@@ -91,7 +91,7 @@ full unemployment would cause inflation
 rises onto consumers. This class based analysis, obviously, did not fit
 in well with the panglossian assumptions of neo-classical economics. Yet 
 basing an analysis on individual expectations does not answer the question 
-whether these expectations are meet. With strong organisation and a 
willingness 
+whether these expectations are met. With strong organisation and a willingness 
 to act, workers can increase their wages 
 to counteract inflation. This means that there are two main options within 
 capitalism. The first option is to use price controls to stop capitalists 
@@ -2430,4 +2430,4 @@ cycle and so unemployment).
 
 
 
-
\ No newline at end of file
+

Bug#898024: [Pkg-javascript-devel] Bug#898024: Bug#898024: trying to overwrite '/usr/include/nodejs/common.gypi', which is also in package nodejs-dev 10.0.0~dfsg-2

[Jonas Smedegaard]

Quoting Jérémy Lal (2018-06-10 22:04:43)
> 2018-06-10 20:14 GMT+02:00 Jonas Smedegaard :
> > Quoting Jérémy Lal (2018-06-10 16:51:14)
> > > 2018-06-10 10:26 GMT+02:00 Andreas Beckmann :
> > > > The 8 -> 10 upgrade path does not work either:
> > > >
> > > >   Selecting previously unselected package libnode64-dev.
> > > >   Preparing to unpack .../libnode64-dev_10.3.0~dfsg-1_amd64.deb ...
> > > >   Unpacking libnode64-dev (10.3.0~dfsg-1) ...
> > > >   dpkg: error processing archive 
> > > > /var/cache/apt/archives/libnode64-dev_10.3.0~dfsg-1_amd64.deb 
> > > > (--unpack):
> > > >trying to overwrite '/usr/include/nodejs/common.gypi', which is also 
> > > > in package nodejs-dev 8.11.2~dfsg-1
> > > >   dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
> > > >   Errors were encountered while processing:
> > > >/var/cache/apt/archives/libnode64-dev_10.3.0~dfsg-1_amd64.deb
> > > >
> > > > You probably need to add
> > > >   Breaks+Replaces: nodejs-dev (<< 10.0.0~dfsg1-3)
> > > > to libnode64-dev for properly taking over /usr/include/nodejs/*
> > > >
> > >
> > > Hi Jonas,
> > >
> > > to do it i'm trying
> > > CDBS_BREAKS_libnode$(ABI)-dev = nodejs-dev (<< 10.0.0~dfsg1-3)
> > > CDBS_REPLACES_libnode$(ABI)-dev = nodejs-dev (<< 10.0.0~dfsg1-3)
> > >
> > > but it does not generate the expected fields.
> > > Did i make some mistake here ?
> >
> > Sorry, I don't locate those strings - which branch of which git are 
> > you trying out the above?
> >
> > It looks correct - but works only in concert with corresponding 
> > hints in control{.in.in} file.  See e.g. git commit f31d94a (i.e. 
> > _reverse_ of that, and adding Replaces: ${cdbs:Replaces}).
> >
> 
> i did not push it because it's w.i.p.
> and yet you're right, i forgot those hints. Thanks !

Good.  Please do ping me if there are any other issues you want me to 
investigate!

 - Jonas

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

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


signature.asc
Description: signature

Bug#901281: O: doschk -- SYSV and DOS filename conflicts check

[Ben Pfaff]

Package: wnpp
Severity: normal

This package has no reported bugs, the last upstream release was in
1993, and zero recent users according to popularity-contest
(https://qa.debian.org/popcon.php?package=doschk).  It has questionable
value these days.  If no one wants to adopt it, it can probably be
removed from Debian.

Bug#873456: Bug#876075: Bug#879048: Bug#876075: Anchors are non-unique in the single-HTML version

[Bill Allombert]

On Sun, Jun 10, 2018 at 03:01:51PM +0200, Bill Allombert wrote:
> On Sun, Jun 10, 2018 at 01:37:11PM +0100, Sean Whitton wrote:
> > Hello all,
> > 
> > On Mon, Dec 25 2017, Russ Allbery wrote:
> > 
> > > I'm not sure where we landed with this, but it feels like the
> > > single-HTML output from Sphnix is kind of broken, and publishing that
> > > on the web site has caused various problems.  I'm not sure how to get
> > > to the multi-page version on www.debian.org, and indeed the anchors
> > > and table of contents in Policy are not working right now on the web
> > > site because of this problem.
> > >
> > > I feel like the single-page HTML version may have been a failed
> > > experiment, at least pending further work on Sphinx, and we should
> > > just publish the multi-page version.  What do other people think?
> > > (Adding debian-www for their opinion as well.)
> > >
> > > Not having working footnotes feels to me like kind of a showstopper.
> > 
> > It's been sixty days since I reported one of these bugs upstream and
> > there has been no response from upstream.  So I think it is time to undo
> > our failed experiment.
> > 
> > We have a choice between dropping policy-1.html altogether, or instead
> > switching the www.debian.org copy to use the multi-page version and not
> > modifying the debian-policy package.
> > 
> > We have three separate bugs (see Cc header) about the singlepage output:
> > the gap in quality between singlepage and multipage is rather wide.  So
> > I am favour of dropping policy-1.html altogether.  I just don't think
> > it's good enough to include in our package.  Further, now that
> > policy.txt.gz has proper section numbering again, it can replace a lot
> > of the uses that there were for policy-1.html.
> > 
> > Any objections to dropping singlepage html output completely, until a
> > future date at which Sphinx upstream has improved it?
> 
> If you do that, then do not close the bugs related to policy-1.html
> because they will still be valid, and report a bug 'policy-1.html is
> missing'.

Maybe it sound harsher than what I wanted to say.
I have no problem with policy-1.html to be dropped as a stop-gap
measure. However this is not a good long term solution. If sphynx cannot
do it then we should consider a better technology. 

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 

Bug#901274: [lintian] warn about *.md,.eslintrc, .npmignore, LICENSE, CHANGES, PATENTS, *.woff, *.ttf, *.woff.? under /usr/lib/node (may be /usr/lib ?)

[Chris Lamb]

Hi Bastien

> Just see it. Will corects thanks

May I kindly suggest doing this work on a branch?

I am happy to review your grammar and spelling but I would very much
like to keep the "master" branch releasable at any time.

Unfortunately, I don't think these commits reach the level of quality
that Debian Developers would expect from Lintian.

> Sorry for the delay I was removing a scratch on my screen with
> toothpaste...

Uhh.


Regards,

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

Bug#900838: menu: Use noawait triggers

[Bill Allombert]

On Thu, Jun 07, 2018 at 02:23:15PM -0700, Julian Andres Klode wrote:
> On Thu, Jun 07, 2018 at 10:57:54PM +0200, Bill Allombert wrote:
> > On Thu, Jun 07, 2018 at 09:57:51AM -0700, Julian Andres Klode wrote:
> > > > Are you sure the upgrade failure are not caused by another patch that it
> > > > applied by ubuntu ?
> > > 
> > > Reasonably.
> > > 
> > > > I have yet to see a single upgrade failure in Debian proper.
> > > 
> > > It's still broken. Let's say you have foo shipping a menu file, and an 
> > > upgrade for
> > > menu. APT might schedule it like this:
> > > 
> > >   unpack foo
> > >   unpack menu
> > >   configure foo
> > 
> > So ? If menu is not configured, then update-menus is not executable, so
> > test -x update-menus return false.
> 
> So? The file trigger gets activated by the package being installed, so:
> 
>   unpack foo
>   unpack menu
>   
> 
> And dpkg then fails because menu is not configured. Though, I don't know,
> maybe it only fails if a dependency of menu is not configured, like in
> the bug report:
> 
> dpkg: dependency problems prevent processing triggers for menu:
>  menu depends on libstdc++6 (>= 4.6); however:
>   Package libstdc++6:amd64 is not configured yet.

What prevent dpkg to configure libstdc++6 in the first place ?

The problem might be some package that menu depend on.
I did not change the menu trigger code for a long time and nobody
reported upgrade problems, so the change must be in some other
package (or maybe this is a change in dpkg ?).

In any case, you are welcome to do the change in Ubuntu. This way we
will know if that breaks something.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 

Bug#901185: Checkbashisms

[積丹尼 Dan Jacobson]

I also note /etc/exim4/update-exim4.conf.conf got overwritten without
asking the user Y/N.
I also note exim4-config contains #!/bin/bash scripts without Depends: bash.

D>  Be sure the package passes Checkbashisms!

JN> Which package? Is there a particular bashism you noticed?

All the shell scripts in the exim* packages.

Anyway please declare a Conflict with bash5, or better yet make the
package finally installable. Thank you.

Bug#901274: [lintian] warn about *.md,.eslintrc, .npmignore, LICENSE, CHANGES, PATENTS, *.woff, *.ttf, *.woff.? under /usr/lib/node (may be /usr/lib ?)

[Bastien ROUCARIES]

On Sun, Jun 10, 2018 at 10:59 PM, Chris Lamb  wrote:
> Hi Bastien,
>
>> Will begin to wrok on this bug
>
> (I trust you are seeing my comments on salsa.)

Just see it. Will corects thanks

Sorry for the delay I was removing a scratch on my screen with toothpaste...

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

Bug#900545: dput: Emit error response body as a debug message

[Alexandre Viau]

On Sun, 10 Jun 2018 14:41:59 +1000 Ben Finney  wrote:
> I have an implementation of this feature, that is awaiting review at
> https://salsa.debian.org/debian/dput/merge_requests/1>.

Thank you for your work!

I have tested and reviewed your merge request[1].

1. https://salsa.debian.org/debian/dput/merge_requests/1#note_28311

Cheers,

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#901274: [lintian] warn about *.md,.eslintrc, .npmignore, LICENSE, CHANGES, PATENTS, *.woff, *.ttf, *.woff.? under /usr/lib/node (may be /usr/lib ?)

[Chris Lamb]

Hi Bastien,

> Will begin to wrok on this bug

(I trust you are seeing my comments on salsa.)


Regards,

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

Bug#901280: Hangs when creating a new files or opening an existing file

[Gaudenz Steinlin]

Package: quickroute-gps
Version: 2.4-15
Severity: important

Hi

If I create a new file, select a map image and GPX route and then click
on OK, quickroute just hangs indefinitely without using much CPU. The
same happens when I open a QRT file created on Windows. The same map
image and GPX track work just fine in the Windows version of Quickroute.

There is an exception stacktrace in .config/QuickRoute/QuickRoute.log
(attached).

If you need the map image and GPX track to reproduce the bug I can send
them to you by private mail or upload them somewhere. 

Opening the JPG exported from Quickroute on Windows to our DOMA
archive [1] works also on Debian.

Gaudenz

[1] https://www.ubol.ch/DOMA/show_map.php?user=gaudenz&map=42

P.S.: Thanks for packageing Quickroute. I was very pleasantly surprised
when I discovered that it's now available in Debian. I hope this issue
can be resolved. And as you seem to know .Net and Mono I would also be
very pleased if you would package PurplePen. If you need help with
packageing or a sponsor for an upload I would be glad to assist.

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

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

Versions of packages quickroute-gps depends on:
ii  libc62.27-3
ii  liblog4net1.2-cil1.2.10+dfsg-7
ii  libmono-corlib4.5-cil4.6.2.7+dfsg-1
ii  libmono-system-configuration4.0-cil  4.6.2.7+dfsg-1
ii  libmono-system-drawing4.0-cil4.6.2.7+dfsg-1
ii  libmono-system-web-services4.0-cil   4.6.2.7+dfsg-1
ii  libmono-system-web4.0-cil4.6.2.7+dfsg-1
ii  libmono-system-windows-forms4.0-cil  4.6.2.7+dfsg-1
ii  libmono-system-xml4.0-cil4.6.2.7+dfsg-1
ii  libmono-system4.0-cil4.6.2.7+dfsg-1
ii  mono-mcs 4.6.2.7+dfsg-1
ii  mono-runtime 4.6.2.7+dfsg-1

quickroute-gps recommends no packages.

quickroute-gps suggests no packages.

-- no debconf information
2018-06-10 22:06:25,463 INFO  
QuickRoute.BusinessEntities.Importers.Garmin.ANTAgent.AntpmImporter - 
1528661185.000 0.000 .ctor: AntpmImporter: /home/gaudenz/.config/antpm/
2018-06-10 22:06:41,300 ERROR QuickRoute.UI.Main - 1528661201.000 16.000 
Application_ThreadException: The type initializer for 'System.Console' threw an 
exception.   at (wrapper managed-to-native) 
System.Drawing.GDIPlus:GdipCreateFromXDrawable_linux (intptr,intptr,intptr&)
  at System.Drawing.Graphics.FromXDrawable (System.IntPtr drawable, 
System.IntPtr display) [0x0] in <1917aa1c39d94b1a91807b8cd9f03350>:0 
  at System.Drawing.Graphics.FromHwnd (System.IntPtr hwnd) [0x000fb] in 
<1917aa1c39d94b1a91807b8cd9f03350>:0 
  at System.Windows.Forms.Control.CreateGraphics () [0x0001c] in 
:0 
  at QuickRoute.Controls.ScrollableLabel.DrawText () [0x0] in 
<2cb7f5b7a9564c53bb101661c5f86a21>:0 
  at QuickRoute.Controls.ScrollableLabel.ScrollableLabel_LocationChanged 
(System.Object sender, System.EventArgs e) [0x0] in 
<2cb7f5b7a9564c53bb101661c5f86a21>:0 
  at (wrapper delegate-invoke) :invoke_void_object_EventArgs 
(object,System.EventArgs)
  at System.Windows.Forms.Control.OnLocationChanged (System.EventArgs e) 
[0x00023] in :0 
  at System.Windows.Forms.Control.UpdateBounds (System.Int32 x, System.Int32 y, 
System.Int32 width, System.Int32 height, System.Int32 clientWidth, System.Int32 
clientHeight) [0x000b0] in :0 
  at System.Windows.Forms.Control.UpdateBounds () [0x0002c] in 
:0 
  at System.Windows.Forms.Control.WmWindowPosChanged 
(System.Windows.Forms.Message& m) [0x00012] in 
:0 
  at System.Windows.Forms.Control.WndProc (System.Windows.Forms.Message& m) 
[0x00157] in :0 
  at System.Windows.Forms.ScrollableControl.WndProc 
(System.Windows.Forms.Message& m) [0x0] in 
:0 
  at System.Windows.Forms.ContainerControl.WndProc 
(System.Windows.Forms.Message& m) [0x0003c] in 
:0 
  at System.Windows.Forms.UserControl.WndProc (System.Windows.Forms.Message& m) 
[0x00036] in :0 
  at System.Windows.Forms.Control+ControlWindowTarget.OnMessage 
(System.Windows.Forms.Message& m) [0x0] in 
:0 
  at System.Windows.Forms.Control+ControlNativeWindow.WndProc 
(System.Windows.Forms.Message& m) [0xb] in 
:0 
  at System.Windows.Forms.NativeWindow.WndProc (System.IntPtr hWnd, 
System.Windows.Forms.Msg msg, System.IntPtr wParam, System.IntPtr lParam) 
[0x0008e] in :0 
2018-06-10 22:32:05,829 INFO  
QuickRoute.BusinessEntities.Importers.Garmin.ANTAgent.AntpmImporter - 
1528662725.000 0.000 .ctor: AntpmImporter: /home/gaudenz/.config/antpm/
2018-06-10 22:39:19,916 DEBUG QuickRoute.Common.LogUtil - 1528663159.000 
434.000 MonoFixMe:

Bug#897242:

[Michael Gilbert]

version: 67.0.3396.62-2

Bug#901255: netcfg-static: Unable to configure fe80::1 as a gateway

[Philipp Kern]

On 6/10/18 7:25 PM, Samuel Thibault wrote:
> Igor Scheller, le dim. 10 juin 2018 18:57:50 +0200, a ecrit:
>> When I try to configure fe80::1 (next router) as a gateway in an IPv6 only
>> network the installer stops with an "Unreachable gateway" error.
>>
>> Looking at netcfg-common.c:netcfg_gateway_reachable its checked by comparing
>> bytes. Imho a better way would be to configure the interface and ping the
>> gateway?
> Well, the gateway has no obligation to respond to pings, so it's not a
> proper way.
> 
> Checking that the prefix matches however makes complete sense, and
> should just work.  Provided that the network prefix length is correct,
> of course, but it has to be otherwise it's a configuration error. I
> guess the problem is rather there.

Well, the gateway may as well be link-local and not be in the assigned
prefix. That's unfortunately a valid configuration. I wouldn't call
fe80::1 "next router", though. It's not a well-known address. ff02::2
(all routers) would be, in a way. But alas.

I guess the answer here is that if the gateway is in fe80::/10 the route
needs to be added with the interface's name, just like pointopoint does it.

The better setup is to use autoconfiguration and let the router announce
itself. That's how most production IPv6 setups work because the standard
calls for that. But I know that especially providers like Hetzner are
notorious for requiring their users to use a hard-coded fe80::1 default
gateway. (And ifupdown supports this correctly.)

Kind regards
Philipp Kern

Bug#901215: mirror submission for freedom.dicea.unifi.it

[Leonardo Boselli]

On Sun, 10 Jun 2018, Marco d'Itri wrote:


On Jun 10, Leonardo Boselli  wrote:


Archive-http: /ftp/pub/linux/debian/

We are trying not to add new mirrors that do not use the standard
/debian/ path.
I see that it works, would it be OK for you to advertise it?


non posso dirtelo ora, e comunque sarebbe una cosa lunga da organizzare 
(_non_ dal punto di vista tecnico)
E  non sarebbe un nuovo mirror, ma uno che avete tolto due giorni fa 
perché non era aggiornato e a causa del particolare errore che aveva 
provocato il mancato aggiornamento non arrivavano 
segnalazioni fino a che non me lo avete detto



BTW, I see some packet loss (over IPv6) when downloading files from your
servers: can you check that the network can support it?


la rete normalmente lo supporta, ma mi potresti dire quale è il routing 
(da traceroute) che ha dato il problema ?




--
ciao,
Marco



--
Leonardo Boselli
Dipartimento Ingegneria Civile e Ambientale UNIFI
tel +39 0552758808  +39 3488605348

Bug#901257: Please consider adopting zchunk for efficient updates

[David Kalnischkies]

On Sun, Jun 10, 2018 at 07:14:55PM +0200, Michael Stapelberg wrote:
> The zchunk format, outlined in the post, is being introduced in Fedora for
> efficient metadata transfer.

As I understand it, zchunk isn't competition for pdiff (per se), but
competition for the compressed files xz/bz2/gz as files aren't only
downloaded in zchunk format but also stored in that format. So what we
(can) do at the moment with downloading the smallest files (like xz) and
store it in a format for fastest access vs. space usage like
uncompressed or lz4 compressed wouldn't be possible anymore.

It therefore also pre-depends on people and programs stopping to access
files in /var/lib/apt/lists directly, which we would like to reach some
point, but aren't there yet.

This format also depends on having random access to remote files aka
HTTP range requests – suprising as it sounds, some users in the wild
interact with servers who do not support this feature & support for
having multiple ranges in the request is another beast to implement in
both server and client. For those users the format would combine all
disadvantages – and these users happen to be the ones where download
metrics matter the most (at least in my experience).


That is entirely ignoring if that has any actual benefits as I haven't
tried it at all, which would probably be the very first step – to
actually verify that there is a point in all this.

Judging just by the text, it seems to combine all the worst aspects it
can in the worst case and seems to have only marginal benefits above
what we have¹ in the best case, but a reality check might provide
another/better view (not volunteering myself).


Best regards

David Kalnischkies

¹ which is different from Fedora both in that they have no pdiff and
that they don't keep indexes in a as central location as we do (from my
limited understanding of never actually having used yum/dnf).


signature.asc
Description: PGP signature

Bug#901279: grub-common: update-grub overwrites /boot/grub/grub.cfg

[Greg Alexander]

Package: grub-common
Version: 2.02+dfsg1-4
Severity: important

Dear Maintainer,

I upgraded from an old version of grub using Debian's
"apt-get install grub-pc", and it overwrote my /boot/grub/grub.cfg
without prompting me, and without making a backup copy.  My old grub.cfg
was hand-crafted, simple, concise.  The new one is not. I don't know if I
would be better off with the older grub.cfg, but I do know I would like
to have it for reference!

Inspecting after the fact, I believe the specific steps were:
grub-pc.postinst script ran update-grub, which then ran grub-mkconfig -o
/boot/grub/grub.cfg.

At a minimum, update-grub must make a backup copy of the original
grub.cfg.

Thanks!

-- Package-specific info:

*** BEGIN /proc/mounts
/dev/root / ext3 rw,relatime,errors=remount-ro,barrier=1,data=ordered 0 0
/dev/md0 /big ext3 rw,relatime,errors=continue,barrier=1,data=ordered 0 0
/dev/sda4 /scratch ext3 rw,relatime,errors=continue,barrier=1,data=ordered 0 0
*** END /proc/mounts

*** BEGIN /boot/grub/device.map
(hd0)   /dev/disk/by-id/ata-WDC_WD30EZRZ-00WN9B0_WD-WCC4E6DCS427
(hd1)   /dev/disk/by-id/ata-ST2000DL004_HD204UI_S2H7J9GC303676
*** END /boot/grub/device.map

*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
  fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
insmod all_video
  else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_msdos
insmod part_gpt
insmod diskfilter
insmod mdraid1x
insmod ext2
set root='mduuid/8ecd869162cee1e9f73c365688306c0e'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root 
--hint='mduuid/8ecd869162cee1e9f73c365688306c0e'  
7a3cb040-495b-4c5e-896d-f59fba6a3243
else
  search --no-floppy --fs-uuid --set=root 7a3cb040-495b-4c5e-896d-f59fba6a3243
fi
font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
  set timeout=30
else
  if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
  # Fallback normal timeout code in case the timeout_style feature is
  # unavailable.
  else
set timeout=5
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu 
--class os $menuentry_id_option 
'gnulinux-simple-8013aa3b-fcf2-46b1-ac0c-ecf2be63d5a3' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 
--hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 --hint='hd0,gpt2'  
8013aa3b-fcf2-46b1-ac0c-ecf2be63d5a3
else
  search --no-floppy --fs-uuid --set=root 
8013aa3b-fcf2-46b1-ac0c-ecf2be63d5a3
fi
echo'Loading Linux 4.1.46-20171117 ...'
linux   /boot/vmlinuz-4.1.46-20171117 root=/dev/sda2 ro  
}
submenu 'Advanced options for Debian GNU/Linux' $menuentry_id_option 
'gnulinux-advanced-8013aa3b-fcf2-46b1-ac0c-ecf2be63d5a3' {
menuentry 'Debian GNU/Linux, with Linux 4.1.46-20171117' --class debian 
--class gnu-linux --class gnu --class os $menuentry_id_option 
'gnulinux-4.1.46-20171117-advanced-8013aa3b-fcf2-46b1-ac0c-ecf2be63d5a3' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; 
fi
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
i

Bug#895868: munin-cron: Fontconfig error: failed reading config file

[Lars Kruse]

Source: munin
Followup-For: Bug #895868

Hello,

I took a look at the bugs reported for fontconfig [1].  I did not find a
description of this problem.  Maybe someone could report it there?

Since munin is likely only affected indirectly by this problem, we
should probably solve it in fontconfig, instead of here.

Or is this only a local customization / configuration issue?

Cheers,
Lars

[1]
https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=fontconfig;dist=unstable

Bug#900203: guile-2.2 FTCBFS for mipsel: In procedure load-thunk-from-memory: No such file or directory

[Rob Browning]

[If possible, please preserve the 900203-forwarded address in replies]

We're currently unable to cross-build guile 2.2 on all of the debian
release architectures, which is important given that through make, etc.,
guile's now part of the core bootstrap set for new architectures.

You can see additional information here

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

and I have been able to reproduce the failure on a debian buster
(testing) amd64 host by adding armhf as root:

  # dpkg --add-architecture armhf
  # apt build-dep -t buster guile-2.2
  # apt install -t buster \
fakeroot \
dpkg-dev \
binutils:armhf \
crossbuild-essential-armhf \
gcc-arm-linux-gnueabihf \
libc-dev:armhf
libncurses5-dev:armhf

and then building the package as not-root:

  $ apt source guile-2.2=2.2.3+1-4
  $ cd guile-2.2-2.2.3+1
  $ DEB_BUILD_PROFILES="cross nocheck" \
DEB_BUILD_OPTIONS="parallel=2 nocheck" \
fakeroot dpkg-buildpackage -B --host-arch=armhf

...which fails with the same error reported in the debian bug:

  guild compile --target="arm-unknown-linux-gnueabihf" -Wunbound-variable 
-Wmacro-use-before-definition -Warity-mismatch -Wformat\
-L "/home/rlb/deb/guile/main/module" -L "/home/rlb/deb/guile/main/module"   
  \
-L "/home/rlb/deb/guile/main/guile-readline"  \
--from=elisp -o "language/elisp/boot.go" "language/elisp/boot.el"
  Backtrace:
  In srfi/srfi-1.scm:
  640:9 19 (for-each # ?)
  In scripts/compile.scm:
 251:26 18 (_ _)
  In system/base/target.scm:
   57:6 17 (with-target _ _)
  In system/base/compile.scm:
 139:28 16 (compile-file "language/elisp/boot.el" #:output-file _ # ?)
  In system/base/language.scm:
 110:30 15 (default-environment _)
  62:11 14 (lookup-language elisp)
  In ice-9/boot-9.scm:
2714:10 13 (_ (language elisp spec) _ _ #:ensure _)
2982:16 12 (try-module-autoload _ _)
 2312:4 11 (save-module-excursion _)
3002:22 10 (_)
  In unknown file:
 9 (primitive-load-path "language/elisp/spec" #)
  In system/base/compile.scm:
  165:4  8 (compile-and-load _ #:from _ #:to _ #:env _ #:opts _ # _)
 235:18  7 (read-and-compile # # ?)
 183:32  6 (compile-fold (#) ?)
  In language/elisp/compile-tree-il.scm:
  805:5  5 (compile-tree-il (defmacro @ (module symbol) (#{`}# ?)) ?)
 705:11  4 (_ _ _)
  In system/base/compile.scm:
  255:6  3 (compile _ #:from _ #:to _ #:env _ #:opts _)
 183:32  2 (compile-fold _ # ?)
  In language/bytecode/spec.scm:
  28:15  1 (bytecode->value #vu8(127 69 76 70 1 1 1 255 0 0 0 0 ?) ?)
  In unknown file:
 0 (load-thunk-from-memory #vu8(127 69 76 70 1 1 1 255 0 ?))

  ERROR: In procedure load-thunk-from-memory:
  In procedure load-thunk-from-memory: No such file or directory
  Makefile:2267: recipe for target 'language/elisp/boot.go' failed

Please let me know if I can help test anything further, and note that it
appears possible that the the architecture may be relevant, i.e. from
the debian bug:

Helmut Grohne  writes:

> Initially, I thought the failure was 100% reproducible for any
> architecture. That doesn't seem to be the case. Let me try building
> guile-2.2 for most release architecture with sbuild:
>
> arm64: successful
> armel: ftcbfs, ftcbfs
> armhf: ftcbfs, ftcbfs
> mips: multiarch skew linux-libc-dev
> mips64el: successful
> mipsel: multiarch skew linux-libc-dev
> powerpc: ftcbfs, ftcbfs
> ppc64el: successful
> s390x: ftcbfs
>
> I ran each ftcbfs build twice to rule out the possibility of a random
> ftcbfs. So we have a non-random ftcbfs for some architectures. I'm a bit
> surprised about s390x here as it is the only failing 64bit architecture.

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Bug#901278: apt removing packages: Depends: xorg-video-abi-23 which is a virtual package...

[積丹尼 Dan Jacobson]

Package: xserver-xorg-video-nvidia-legacy-304xx
Version: 304.137-5

Every day apt(itude) asks me to remove the package:

 xserver-xorg-video-nvidia-legacy-304xx : Depends: xorg-video-abi-23 which is a 
virtual package, provided by:
   - xserver-xorg-core 
(2:1.19.6-1), but 2:1.20.0-2 is to be installed

The following actions will resolve these dependencies:

  Remove the following packages:
1)  nvidia-legacy-304xx-driver [304.137-5 (now, unstable)]
2)  xserver-xorg-video-nvidia-legacy-304xx [304.137-5 (now, unstable)]

  APT policy: (990, 'experimental'), (500, 'unstable')

Bug#898024: [Pkg-javascript-devel] Bug#898024: Bug#898024: trying to overwrite '/usr/include/nodejs/common.gypi', which is also in package nodejs-dev 10.0.0~dfsg-2

[Jérémy Lal]

2018-06-10 20:14 GMT+02:00 Jonas Smedegaard :

> Hi Jérémy,
>
> Quoting Jérémy Lal (2018-06-10 16:51:14)
> > 2018-06-10 10:26 GMT+02:00 Andreas Beckmann :
> > > The 8 -> 10 upgrade path does not work either:
> > >
> > >   Selecting previously unselected package libnode64-dev.
> > >   Preparing to unpack .../libnode64-dev_10.3.0~dfsg-1_amd64.deb ...
> > >   Unpacking libnode64-dev (10.3.0~dfsg-1) ...
> > >   dpkg: error processing archive /var/cache/apt/archives/
> libnode64-dev_10.3.0~dfsg-1_amd64.deb (--unpack):
> > >trying to overwrite '/usr/include/nodejs/common.gypi', which is
> also in package nodejs-dev 8.11.2~dfsg-1
> > >   dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
> > >   Errors were encountered while processing:
> > >/var/cache/apt/archives/libnode64-dev_10.3.0~dfsg-1_amd64.deb
> > >
> > > You probably need to add
> > >   Breaks+Replaces: nodejs-dev (<< 10.0.0~dfsg1-3)
> > > to libnode64-dev for properly taking over /usr/include/nodejs/*
> > >
> >
> > Hi Jonas,
> >
> > to do it i'm trying
> > CDBS_BREAKS_libnode$(ABI)-dev = nodejs-dev (<< 10.0.0~dfsg1-3)
> > CDBS_REPLACES_libnode$(ABI)-dev = nodejs-dev (<< 10.0.0~dfsg1-3)
> >
> > but it does not generate the expected fields.
> > Did i make some mistake here ?
>
> Sorry, I don't locate those strings - which branch of which git are you
> trying out the above?
>
> It looks correct - but works only in concert with corresponding hints in
> control{.in.in} file.  See e.g. git commit f31d94a (i.e. _reverse_ of
> that, and adding Replaces: ${cdbs:Replaces}).
>

i did not push it because it's w.i.p.
and yet you're right, i forgot those hints. Thanks !

Jérémy

Bug#901277: node-mime: CVE-2017-16138

[Salvatore Bonaccorso]

Source: node-mime
Version: 1.3.4-1
Severity: important
Tags: security upstream
Forwarded: https://github.com/broofa/node-mime/issues/167

Hi,

The following vulnerability was published for node-mime.

CVE-2017-16138[0]:
| The mime module is vulnerable to regular expression denial of service
| when a mime lookup is performed on untrusted user input.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-16138
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16138
[1] https://github.com/broofa/node-mime/issues/167
[2] https://nodesecurity.io/advisories/535

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#884484: python-cryptography-vectors/2.2.2-1 appears to break python-cryptography in testing

[Paul Gevers]

Hi

On 10-06-18 21:34, Tristan Seligmann wrote:
> -vectors exists purely for the benefit of the tests, nothing outside the
> tests uses the vectors. If you are not running the tests, having a
> mismatched version of -vectors will have no effect.

Thanks for clarifying. Just for my understanding, did you ever
considered to add these vectors (as a second tar ball in the source 3
format) to the source package of python-cryptography?

> Currently this regression is delaying the migration of both packages to
> testing by 10 days. I can help speed it up a bit if this regression is
> really only a TEST dependency restriction.
> 
> 
> Sounds good to me!

I triggered a combined test. Once that passes, autopkgtest should not
delay the packages anymore. I'll keep an eye on it. Unfortunately for
python-cryptography, the migration will not be earlier than the default
5 days, because it has to wait for -vectors, which doesn't get a reduced
age because it doesn't contain an autopkgtest. (Please don't abuse the
system and add a dummy test).

Paul



signature.asc
Description: OpenPGP digital signature

Bug#898809: lintian -F internal error: cannot run shared-libs check on package binary

[Chris Lamb]

atthias Klose wrote:

> This causes the gcc-8-cross packages built on amd64 and i386 failing the 
> lintian
> -F check during upload (packages at p.d.o/~d.../tmp).
> 
> $ lintian -F ../gcc-8-cross_16_amd64.changes 2>&1 | tee ../log.lintian
> Use of uninitialized value $lib in pattern match (m//) at
> /usr/share/lintian/checks/files.pm line 339.
> Use of uninitialized value $val in split at
> /usr/share/perl5/Lintian/Collect/Binary.pm line 423, <$_[...]> line 22776.
> Use of uninitialized value $val in split at
> /usr/share/perl5/Lintian/Collect/Binary.pm line 423, <$_[...]> line 22776.
> internal error: shlib usr/lib/gcc-cross/arm-linux-gnueabi/8/libgo.a(log.o) not
> found in package (should not happen!) at
> /usr/share/lintian/checks/shared-libs.pm line 198.
> internal error: cannot run shared-libs check on package
> binary:gccgo-8-arm-linux-gnueabi/8.1.0-3cross2/amd64
> warning: skipping check of 
> binary:gccgo-8-arm-linux-gnueabi/8.1.0-3cross2/amd64

Full --debug output attached from current Git HEAD.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
N: Lintian v2.5.89-25-g95eaa1261
N: Lintian root directory: /home/lamby/git/debian/lintian/lintian
N: Configuration file: /home/lamby/.config/lintian/lintianrc
N: Laboratory: 
N: UTF-8: ✓ (☃)
N: 
N: Using profile debian/main.
N: Setting up lab in /tmp/temp-lintian-lab-pRx5iKY_dM ...
N: Selected action: check
N: Selected checks: 
apache2,application-not-library,appstream-metadata,automake,binaries,changelog-file,changes-file,conffiles,control-file,control-files,copyright-file,cruft,dbus,deb-format,debconf,debhelper,debian-readme,debian-source-dir,description,duplicate-files,elpa,fields,filename-length,files,gir,group-checks,huge-usr-share,infofiles,init.d,java,manpages,md5sums,menu-format,menus,nmu,obsolete-sites,ocaml,patch-systems,pe,phppear,po-debconf,python,rules,scripts,shared-libs,source-changelog,source-copyright,standards-version,symlinks,systemd,testsuite,triggers,udev,upstream-metadata,usrmerge,version-substvars,watch-file
N: Parallelization limit: 5
N: Starting on group gcc-8-cross/16
N: Unpacking packages in group gcc-8-cross/16
N: Collecting info: bin-pkg-control for 
binary:gccgo-8-arm-linux-gnueabi/8.1.0-3cross2/amd64 ...
N: Collecting info: unpacked for 
binary:gccgo-8-arm-linux-gnueabi/8.1.0-3cross2/amd64 ...
N: Collection script bin-pkg-control for 
binary:gccgo-8-arm-linux-gnueabi/8.1.0-3cross2/amd64 done (0.032s)
N: Collection script unpacked for 
binary:gccgo-8-arm-linux-gnueabi/8.1.0-3cross2/amd64 done (4.096s)
N: Collecting info: override-file for 
binary:gccgo-8-arm-linux-gnueabi/8.1.0-3cross2/amd64 ...
N: Collecting info: scripts for 
binary:gccgo-8-arm-linux-gnueabi/8.1.0-3cross2/amd64 ...
N: Collecting info: file-info for 
binary:gccgo-8-arm-linux-gnueabi/8.1.0-3cross2/amd64 ...
N: Collecting info: md5sums for 
binary:gccgo-8-arm-linux-gnueabi/8.1.0-3cross2/amd64 ...
N: Collecting info: changelog-file for 
binary:gccgo-8-arm-linux-gnueabi/8.1.0-3cross2/amd64 ...
N: Collection script override-file for 
binary:gccgo-8-arm-linux-gnueabi/8.1.0-3cross2/amd64 done (0.008s)
N: Collecting info: ar-info for 
binary:gccgo-8-arm-linux-gnueabi/8.1.0-3cross2/amd64 ...
N: Collection script changelog-file for 
binary:gccgo-8-arm-linux-gnueabi/8.1.0-3cross2/amd64 done (0.004s)
N: Collecting info: copyright-file for 
binary:gccgo-8-arm-linux-gnueabi/8.1.0-3cross2/amd64 ...
N: Collection script copyright-file for 
binary:gccgo-8-arm-linux-gnueabi/8.1.0-3cross2/amd64 done (0.003s)
N: Collection script scripts for 
binary:gccgo-8-arm-linux-gnueabi/8.1.0-3cross2/amd64 done (0.047s)
N: Collection script ar-info for 
binary:gccgo-8-arm-linux-gnueabi/8.1.0-3cross2/amd64 done (0.068s)
N: Collection script file-info for 
binary:gccgo-8-arm-linux-gnueabi/8.1.0-3cross2/amd64 done (0.079s)
N: Collecting info: objdump-info for 
binary:gccgo-8-arm-linux-gnueabi/8.1.0-3cross2/amd64 ...
N: Collecting info: strings for 
binary:gccgo-8-arm-linux-gnueabi/8.1.0-3cross2/amd64 ...
N: Collecting info: java-info for 
binary:gccgo-8-arm-linux-gnueabi/8.1.0-3cross2/amd64 ...
N: Collection script java-info for 
binary:gccgo-8-arm-linux-gnueabi/8.1.0-3cross2/amd64 done (0.029s)
N: Collection script md5sums for 
binary:gccgo-8-arm-linux-gnueabi/8.1.0-3cross2/amd64 done (0.681s)
N: Collection script strings for 
binary:gccgo-8-arm-linux-gnueabi/8.1.0-3cross2/amd64 done (3.696s)
N: Collection script objdump-info for 
binary:gccgo-8-arm-linux-gnueabi/8.1.0-3cross2/amd64 done (11.204s)
N: Unpack of gcc-8-cross/16 done (15.396s)
N: 
N: Processing binary package gccgo-8-arm-linux-gnueabi (version 8.1.0-3cross2, 
arch amd64) ...
N: Base directory in lab: 
/tmp/temp-lintian-lab-pRx5iKY_dM/pool/g/gcc-8-cross/gccgo-8-arm-linux-gnueabi_8.1.0-3cross2_amd64_binary
N: Loading overrides file (if any) ...
N: Running check: apache2 on 
binary:gccgo-8-arm-linux-gnueabi/8.1.0-3cross2/amd64  ...
N: Check script apac

Bug#901274: [lintian] warn about *.md,.eslintrc, .npmignore, LICENSE, CHANGES, PATENTS, *.woff, *.ttf, *.woff.? under /usr/lib/node (may be /usr/lib ?)

[Bastien ROUCARIES]

On Sun, Jun 10, 2018 at 9:33 PM, Bastien ROUCARIES
 wrote:
> On Sun, Jun 10, 2018 at 9:31 PM, Chris Lamb  wrote:
>> Hi Bastien,
>>
>>> > (This seems like a candidate for data/files/fnames.)
>>>
>>> Will add the fonts name ASAP, thanks
>>
>> I don't understand this, sorry... My remark about data/files/fnames
>> refers to this entire bug report, not to the fonts specifically.
>
> Ok, I had understood that your remark apply only to last paragraph.
> Will begin to wrok on this bug


Last but not least, the woff.* and eot file are serious (at least
now). Tools to create does not yet exist (I am packaging it, Waiting
in NEWS node-microbuffer and node-svgpath, will need svg2ttf, ttf2woff
and ttf2eot)

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

Bug#884484: python-cryptography-vectors/2.2.2-1 appears to break python-cryptography in testing

[Tristan Seligmann]

On Sun, 10 Jun 2018 at 21:06 Paul Gevers  wrote:

> need to stay in lock step. In this bug (#884484) the solution was to
> tighten the test dependencies, which is one way to achieve this (albeit
> it will only work for the next time without the help of the RT or me),
> but I wonder if this dependency is only for the test, or really needed
> for python-cryptography. If the latter, to guarantee that the archive
>

-vectors exists purely for the benefit of the tests, nothing outside the
tests uses the vectors. If you are not running the tests, having a
mismatched version of -vectors will have no effect.


> Currently this regression is delaying the migration of both packages to
> testing by 10 days. I can help speed it up a bit if this regression is
> really only a TEST dependency restriction.
>

Sounds good to me!

Bug#901274: [lintian] warn about *.md,.eslintrc, .npmignore, LICENSE, CHANGES, PATENTS, *.woff, *.ttf, *.woff.? under /usr/lib/node (may be /usr/lib ?)

[Bastien ROUCARIES]

On Sun, Jun 10, 2018 at 9:31 PM, Chris Lamb  wrote:
> Hi Bastien,
>
>> > (This seems like a candidate for data/files/fnames.)
>>
>> Will add the fonts name ASAP, thanks
>
> I don't understand this, sorry... My remark about data/files/fnames
> refers to this entire bug report, not to the fonts specifically.

Ok, I had understood that your remark apply only to last paragraph.
Will begin to wrok on this bug

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

Bug#901274: [lintian] warn about *.md,.eslintrc, .npmignore, LICENSE, CHANGES, PATENTS, *.woff, *.ttf, *.woff.? under /usr/lib/node (may be /usr/lib ?)

[Chris Lamb]

Hi Bastien,

> > (This seems like a candidate for data/files/fnames.)
> 
> Will add the fonts name ASAP, thanks

I don't understand this, sorry... My remark about data/files/fnames
refers to this entire bug report, not to the fonts specifically.


Regards,

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

Bug#901274: [lintian] warn about *.md,.eslintrc, .npmignore, LICENSE, CHANGES, PATENTS, *.woff, *.ttf, *.woff.? under /usr/lib/node (may be /usr/lib ?)

[Bastien ROUCARIES]

On Sun, Jun 10, 2018 at 9:25 PM, Chris Lamb  wrote:
> Bastien,
>
>> Documentation file (*.md, LICENSE, CHANGES, PATENTS) do not belong to this 
>> dir
>>
>> .eslintrc are jslint config file and should not be installed
>>
>> .npmignore is used in order to publish file under npm so do not install
>>
>> *.woff, *.ttf, *.woff. are fonts so go to fonts package
>
> (This seems like a candidate for data/files/fnames.)

Will add the fonts name ASAP, thanks

Bug#900410: mtools: please make the output reproducible (directory timestamps)

[Chris Lamb]

Dear Vagrant,

> > +   else if (*endptr != '\0')
> > +   fprintf(stderr, "SOURCE_DATE_EPOCHh has 
> > trailing garbage\n");
> 
> 
> Minor typo in error message? Or is the error message trying to indicate
> the problem by example? :)

Very well spotted. I'll leave the hermeneutics of my original
intentions ambiguous for comedic effect ;-)

Updated patch attached..


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/misc.c b/misc.c
index 6adf33b..d6bcee1 100644
--- a/misc.c
+++ b/misc.c
@@ -109,7 +109,8 @@ FILE *open_mcwd(const char *mode)
 * Ignore the info, if the file is more than 6 hours old
 */
getTimeNow(&now);
-   if (now - sbuf.st_mtime > 6 * 60 * 60) {
+   if (now - sbuf.st_mtime > 6 * 60 * 60
+   && getenv("SOURCE_DATE_EPOCH") == NULL) {
fprintf(stderr,
"Warning: \"%s\" is out of date, removing it\n",
file);
@@ -159,11 +160,33 @@ void print_sector(const char *message, unsigned char 
*data, int size)
 
 time_t getTimeNow(time_t *now)
 {
+   char *endptr;
+   char *source_date_epoch;
+   unsigned long long epoch;
static int haveTime = 0;
static time_t sharedNow;
 
if(!haveTime) {
-   time(&sharedNow);
+   source_date_epoch = getenv("SOURCE_DATE_EPOCH");
+   if (source_date_epoch) {
+   epoch = strtoull(source_date_epoch, &endptr, 10);
+
+   if (endptr == source_date_epoch)
+   fprintf(stderr, "SOURCE_DATE_EPOCH invalid\n");
+   else if ((errno == ERANGE && (epoch == ULLONG_MAX || 
epoch == 0))
+   || (errno != 0 && epoch == 0))
+   fprintf(stderr, "SOURCE_DATE_EPOCH: strtoull: 
%s: %llu\n",
+   strerror(errno), epoch);
+   else if (*endptr != '\0')
+   fprintf(stderr, "SOURCE_DATE_EPOCH has trailing 
garbage\n");
+   else if (epoch > ULONG_MAX)
+   fprintf(stderr, "SOURCE_DATE_EPOCH must be <= 
%lu but saw: %llu\n", ULONG_MAX, epoch);
+   else {
+   sharedNow = epoch;
+   }
+   } else {
+   time(&sharedNow);
+   }
haveTime = 1;
}
if(now)

Bug#900410: mtools: please make the output reproducible (directory timestamps)

[Vagrant Cascadian]

On 2018-05-30, Chris Lamb wrote:
> Chris Lamb wrote:
> Updated patch attached - I left a debug "printf" call in there by
> accident.
...
> + else if (*endptr != '\0')
> + fprintf(stderr, "SOURCE_DATE_EPOCHh has 
> trailing garbage\n");


Minor typo in error message? Or is the error message trying to indicate
the problem by example? :)


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#901274: [lintian] warn about *.md,.eslintrc, .npmignore, LICENSE, CHANGES, PATENTS, *.woff, *.ttf, *.woff.? under /usr/lib/node (may be /usr/lib ?)

[Chris Lamb]

Bastien,

> Documentation file (*.md, LICENSE, CHANGES, PATENTS) do not belong to this dir
> 
> .eslintrc are jslint config file and should not be installed
> 
> .npmignore is used in order to publish file under npm so do not install
> 
> *.woff, *.ttf, *.woff. are fonts so go to fonts package

(This seems like a candidate for data/files/fnames.)


Regards,

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

Bug#901275: ipvsadm FTCBFS: uses the build architecture pkg-config

[Helmut Grohne]

Source: ipvsadm
Version: 1:1.28-3
Tags: patch upstream
User: helm...@debian.org
Usertags: rebootstrap

ipvsadm fails to cross build from source, because the upstream build
system hard codes the build architecture pkg-config. After making it
substitutable, ipvsadm cross builds successfully. Please consider
applying the attached patch.

Helmut
--- ipvsadm-1.28.orig/Makefile
+++ ipvsadm-1.28/Makefile
@@ -36,6 +36,7 @@
 RPMSPECDIR	= $(shell rpm --eval '%_specdir')
 
 CC		= gcc
+PKG_CONFIG	?= pkg-config
 INCLUDE		=
 SBIN		= $(BUILD_ROOT)/sbin
 MANDIR		= usr/man
@@ -66,10 +67,10 @@
 LIBS		= -lpopt
 ifneq (0,$(HAVE_NL))
 LIBS		+= $(shell \
-		if which pkg-config > /dev/null 2>&1; then \
-		  if   pkg-config --libs libnl-genl-3.0  2> /dev/null; then :;\
-		  elif pkg-config --libs libnl-2.0   2> /dev/null; then :;\
-		  elif pkg-config --libs libnl-1 2> /dev/null; then :;\
+		if which $(PKG_CONFIG) > /dev/null 2>&1; then \
+		  if   $(PKG_CONFIG) --libs libnl-genl-3.0  2> /dev/null; then :;\
+		  elif $(PKG_CONFIG) --libs libnl-2.0   2> /dev/null; then :;\
+		  elif $(PKG_CONFIG) --libs libnl-1 2> /dev/null; then :;\
 		  fi; \
 		else echo "-lnl"; fi)
 endif
--- ipvsadm-1.28.orig/libipvs/Makefile
+++ ipvsadm-1.28/libipvs/Makefile
@@ -1,14 +1,15 @@
 # Makefile for libipvs
 
 CC		= gcc
+PKG_CONFIG	?= pkg-config
 CFLAGS		= -Wall -Wunused -Wstrict-prototypes -g -fPIC
 ifneq (0,$(HAVE_NL))
 CFLAGS		+= -DLIBIPVS_USE_NL
 CFLAGS		+= $(shell \
-		if which pkg-config > /dev/null 2>&1; then \
-		  if   pkg-config --cflags libnl-3.0  2> /dev/null; then :; \
-		  elif pkg-config --cflags libnl-2.0  2> /dev/null; then :; \
-		  elif pkg-config --cflags libnl-12> /dev/null; then :; \
+		if which $(PKG_CONFIG) > /dev/null 2>&1; then \
+		  if   $(PKG_CONFIG) --cflags libnl-3.0  2> /dev/null; then :; \
+		  elif $(PKG_CONFIG) --cflags libnl-2.0  2> /dev/null; then :; \
+		  elif $(PKG_CONFIG) --cflags libnl-12> /dev/null; then :; \
 		  fi; \
 		fi)
 endif
@@ -17,10 +18,10 @@
 		 echo "-I../../."; fi;)
 DEFINES		= $(shell if [ ! -f ../../ip_vs.h ]; then	\
 		echo "-DHAVE_NET_IP_VS_H"; fi;)
-DEFINES		+= $(shell if which pkg-config > /dev/null 2>&1; then \
-			 if   pkg-config --exists libnl-3.0; then :; \
-			 elif pkg-config --exists libnl-2.0; then :; \
-			 elif pkg-config --exists libnl-1; \
+DEFINES		+= $(shell if which $(PKG_CONFIG) > /dev/null 2>&1; then \
+			 if   $(PKG_CONFIG) --exists libnl-3.0; then :; \
+			 elif $(PKG_CONFIG) --exists libnl-2.0; then :; \
+			 elif $(PKG_CONFIG) --exists libnl-1; \
 			 then echo "-DFALLBACK_LIBNL1"; fi; fi)
 
 .PHONY		= all clean install dist distclean rpm rpms

Bug#901276: jessie-pu: package lame/3.99.5+repack1-7+deb8u2

[Hugo Lefeuvre]

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

Hi,

lame 3.99.5+repack1-7+deb8u1 is affected by several vulnerabilities in
the code used to read the input file. These issues are not present in
any Debian release after Jessie because the package switched to
libsndfile to read and write audio files. The upstream code itself was
recently fixed in 3.100.

Following advices from lame's upstream and from lame's maintainer I
proposed the attached patch. In this patch we modify the Jessie
package to use libsndfile instead of the internal code. The security
team considers these issues not worth a DSA but recommended me to
submit this patch as jessie-pu.

You can find more detailed information about this patch on the
debian-lts ML[0].

Thanks !

Regards,
 Hugo

[0] https://lists.debian.org/debian-lts/2018/05/msg00081.html

-- 
 Hugo Lefeuvre (hle)|www.owl.eu.com
4096/ 9C4F C8BF A4B0 8FC5 48EB 56B8 1962 765B B9A8 BACA
diff -Nru lame-3.99.5+repack1/debian/changelog lame-3.99.5+repack1/debian/changelog
--- lame-3.99.5+repack1/debian/changelog	2015-06-15 09:05:28.0 -0400
+++ lame-3.99.5+repack1/debian/changelog	2018-05-27 17:30:02.0 -0400
@@ -1,3 +1,16 @@
+lame (3.99.5+repack1-7+deb8u2) oldstable; urgency=high
+
+  [ Fabian Greffrath ]
+
+  * Build the frontend with the sndfile io routines, RAW PCM and WAV can be
+read from stdin since at least 3.99.0 (Closes: #867725).
+- Add Build-Depends: libsndfile1-dev.
+
+Addressed CVEs: CVE-2017-9872, CVE-2017-9871, CVE-2017-9870, CVE-2017-9869,
+CVE-2017-15046, CVE-2017-15045, CVE-2017-15018.
+
+ -- Hugo Lefeuvre   Sun, 27 May 2018 17:30:02 -0400
+
 lame (3.99.5+repack1-7+deb8u1) jessie; urgency=medium
 
   * debian/patches/force_align_arg_pointer.patch: Enable functions with SSE
diff -Nru lame-3.99.5+repack1/debian/control lame-3.99.5+repack1/debian/control
--- lame-3.99.5+repack1/debian/control	2015-06-15 09:03:04.0 -0400
+++ lame-3.99.5+repack1/debian/control	2018-05-27 17:16:42.0 -0400
@@ -9,6 +9,7 @@
  debhelper (>= 9),
  dh-autoreconf,
  libncurses5-dev,
+ libsndfile1-dev,
  pkg-config,
  nasm [i386]
 Standards-Version: 3.9.5
diff -Nru lame-3.99.5+repack1/debian/rules lame-3.99.5+repack1/debian/rules
--- lame-3.99.5+repack1/debian/rules	2015-06-15 09:03:04.0 -0400
+++ lame-3.99.5+repack1/debian/rules	2018-05-27 17:16:42.0 -0400
@@ -9,4 +9,4 @@
 		--enable-dynamic-frontends \
 		--enable-expopt=full \
 		--enable-nasm \
-		--with-fileio=lame
+		--with-fileio=sndfile


signature.asc
Description: PGP signature

Bug#900918: debian-installer: Please make the generated images reproducible

[Vagrant Cascadian]

Control: block 900918 by 900409 900410

This requires fixes to mtools, marked as blocking bugs.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#901273: bootpc FTCBFS: does not pass cross tools to make

[Helmut Grohne]

Source: bootpc
Version: 0.64-7
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

bootpc fails to cross build from source, because it does not pass cross
tools to make. After indirecting make through dh_auto_build, bootpc
cross builds successfully. Please consider applying the attached patch.

Helmut
diff -u bootpc-0.64/debian/changelog bootpc-0.64/debian/changelog
--- bootpc-0.64/debian/changelog
+++ bootpc-0.64/debian/changelog
@@ -1,3 +1,10 @@
+bootpc (0.64-7.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_build pass cross tools to make. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 10 Jun 2018 21:14:41 +0200
+
 bootpc (0.64-7) unstable; urgency=low
 
   * Bumped Standards-Version to 3.7.3 
diff -u bootpc-0.64/debian/control bootpc-0.64/debian/control
--- bootpc-0.64/debian/control
+++ bootpc-0.64/debian/control
@@ -3,7 +3,7 @@
 Priority: extra
 Maintainer: Anibal Monsalve Salazar 
 Standards-Version: 3.7.3
-Build-Depends: debhelper (>= 5)
+Build-Depends: debhelper (>= 7)
 
 Package: bootpc
 Architecture: any
diff -u bootpc-0.64/debian/rules bootpc-0.64/debian/rules
--- bootpc-0.64/debian/rules
+++ bootpc-0.64/debian/rules
@@ -9,7 +9,7 @@
 build-stamp:
dh_testdir
 
-   $(MAKE) CFLAGS="-O2 -g -Wall"
+   dh_auto_build -- CFLAGS="-O2 -g -Wall"
 
touch build-stamp
 

Bug#901274: [lintian] warn about *.md,.eslintrc, .npmignore, LICENSE, CHANGES, PATENTS, *.woff, *.ttf, *.woff.? under /usr/lib/node (may be /usr/lib ?)

[Bastien ROUCARIÈS]

Package: lintian
Version: 2.5.89
Severity: normal

Hi,

Documentation file (*.md, LICENSE, CHANGES, PATENTS) do not belong to this dir

.eslintrc are jslint config file and should not be installed

.npmignore is used in order to publish file under npm so do not install

*.woff, *.ttf, *.woff. are fonts so go to fonts package

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

Bug#901256: dak: dakweb: allow for looking up files by sha256sum

[Chris Lamb]

forwarded 901256 https://salsa.debian.org/ftp-team/dak/merge_requests/76
thanks

Hi Alexandre et al.,

> Please consider applying the attached patch which also fixes an error in
> the docstring of file_in_archive.

Just to close the loop, this was "forwarded" as an MR here.

  https://salsa.debian.org/ftp-team/dak/merge_requests/76


Best wishes,

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

Bug#901272: atomix FTCBFS: configures for the build architecture

[Helmut Grohne]

Source: atomix
Version: 3.22.0-2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

atomix fails to cross build from source, because it configures for the
build architecture. It actually configures twice. Once through
autogen.sh and another time through dh_auto_configure. The first
configure lacks any options and thus is for the build architecture.
After disabling the first configuration, atomix cross builds
successfully. Please consider applying the attached patch.

Helmut
diff --minimal -Nru atomix-3.22.0/debian/changelog 
atomix-3.22.0/debian/changelog
--- atomix-3.22.0/debian/changelog  2017-11-17 15:28:42.0 +0100
+++ atomix-3.22.0/debian/changelog  2018-06-10 21:10:24.0 +0200
@@ -1,3 +1,10 @@
+atomix (3.22.0-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Configure only once through dh_auto_configure. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 10 Jun 2018 21:10:24 +0200
+
 atomix (3.22.0-2) unstable; urgency=medium
 
   * Declare compliance with Debian Policy 4.1.1.
diff --minimal -Nru atomix-3.22.0/debian/rules atomix-3.22.0/debian/rules
--- atomix-3.22.0/debian/rules  2017-11-17 15:28:42.0 +0100
+++ atomix-3.22.0/debian/rules  2018-06-10 21:10:22.0 +0200
@@ -6,7 +6,7 @@
dh $@
 
 override_dh_auto_configure:
-   ./autogen.sh
+   NOCONFIGURE=1 ./autogen.sh
dh_auto_configure -- \
--prefix=/usr \
--bindir=\$${prefix}/games \

Bug#901271: ntpstat FTCBFS: does not pass cross tools to make

[Helmut Grohne]

Source: ntpstat
Version: 0.0.0.1-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

ntpstat fails to cross build from source, because it does not pass cross
tools to make. The easiest way to fix that is removing the
override_dh_auto_build, because dh_auto_build does what is needed for
you. Please consider applying the attached patch.

Helmut
diff --minimal -Nru ntpstat-0.0.0.1/debian/changelog 
ntpstat-0.0.0.1/debian/changelog
--- ntpstat-0.0.0.1/debian/changelog2014-09-12 16:07:30.0 +0200
+++ ntpstat-0.0.0.1/debian/changelog2018-06-10 21:05:08.0 +0200
@@ -1,3 +1,10 @@
+ntpstat (0.0.0.1-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Remove override_dh_auto_build. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 10 Jun 2018 21:05:08 +0200
+
 ntpstat (0.0.0.1-1) unstable; urgency=medium
 
   * Initial release. (Closes: #761289)
diff --minimal -Nru ntpstat-0.0.0.1/debian/rules ntpstat-0.0.0.1/debian/rules
--- ntpstat-0.0.0.1/debian/rules2014-09-12 16:07:30.0 +0200
+++ ntpstat-0.0.0.1/debian/rules2018-06-10 21:05:00.0 +0200
@@ -6,8 +6,5 @@
 %:
dh $@
 
-override_dh_auto_build:
-   $(MAKE)
-
 override_dh_auto_clean:
rm -f ntpstat

Bug#884484: python-cryptography-vectors/2.2.2-1 appears to break python-cryptography in testing

[Paul Gevers]

Dear maintainers,

With a recent upload of python-cryptography-vectors the autopkgtest of
python-cryptography version 2.1.4-1 started to fail in testing. See:
https://ci.debian.net/packages/p/python-cryptography/testing/amd64/
and
https://qa.debian.org/excuses.php?package=python-cryptography-vectors

Looking at the error message (copied below) it seems the to packages
need to stay in lock step. In this bug (#884484) the solution was to
tighten the test dependencies, which is one way to achieve this (albeit
it will only work for the next time without the help of the RT or me),
but I wonder if this dependency is only for the test, or really needed
for python-cryptography. If the latter, to guarantee that the archive
knows, I believe some binary packages from python-cryptography-vectors
should contain a "Breaks" relation with the older version of the right
binary packages from python-cryptography instead of just test dependency
restrictions.

Currently this regression is delaying the migration of both packages to
testing by 10 days. I can help speed it up a bit if this regression is
really only a TEST dependency restriction.

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-cryptography/437150/log.gz

=== FAILURES
===
_ test_vector_version
__

def test_vector_version():
>   assert cryptography.__version__ == cryptography_vectors.__version__
E   AssertionError: assert '2.1.4' == '2.2.2'
E - 2.1.4
E + 2.2.2

tests/test_utils.py:3798: AssertionError
 1 failed, 93357 passed, 4177 skipped in 310.20 seconds




signature.asc
Description: OpenPGP digital signature

Bug#901270: trickle FTCBFS: configures for the build architecture

[Helmut Grohne]

Source: trickle
Version: 1.07-10.1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

trickle fails to cross build from source, because it configures for the
build architecture. The easiest way of fixing that is using
dh_auto_configure. After doing so trickle continues to fail due to its
use of AC_TRY_RUN. I have no fix for that to offer. Please consider
fixing the --host part anyway. The attached patch implements that.
Please close this bug when trickle passes --host to ./configure. That
will make the next failure more visible to interested cross builders.

Helmut
diff -u trickle-1.07/debian/changelog trickle-1.07/debian/changelog
--- trickle-1.07/debian/changelog
+++ trickle-1.07/debian/changelog
@@ -1,3 +1,10 @@
+trickle (1.07-10.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Address FTCBFS: Let dh_auto_configure pass --host to ./configure. (Closes: 
#-1)
+
+ -- Helmut Grohne   Sun, 10 Jun 2018 20:57:14 +0200
+
 trickle (1.07-10.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u trickle-1.07/debian/rules trickle-1.07/debian/rules
--- trickle-1.07/debian/rules
+++ trickle-1.07/debian/rules
@@ -9,8 +9,7 @@
dh_testdir
dh_autoreconf
CPPFLAGS="$(CPPFLAGS)" CFLAGS="$(CFLAGS)" CXXFLAGS="$(CXXFLAGS)" \
-LDFLAGS="$(LDFLAGS)" ./configure --prefix=/usr \
---mandir=/usr/share/man --sysconfdir=/etc --with-pic
+LDFLAGS="$(LDFLAGS)" dh_auto_configure -- --with-pic
 
 build: build-arch build-indep
 build-arch: build-stamp

Bug#900552: Bug #900552: Add privacy policy to the Debian website

[Laura Arjona Reina]

Hello all
I have read the document and I have some questions and comments.

1.- Once that we publish a "Privacy Policy" document in the website, if
there are changes to the text, do we need to do something "special"?
(e.g. put a banner in the site saying "we have updated our privacy
policy", or informing some mailing list...). I'd also like to know if we
need to "version" this document (in similar way as we do with the Debian
Constitution, for example: 1.0, 1.1, etc).

2.- We need to know if translations of the document need to clarify that
the translation is only informative and has no legal value and people
should look at the original English for that. We put such a note in the
translations of /trademark and /license, for example.

3.- About where it should go, my proposal is:

* Place the document under /legal/privacy.wml
* On top of the  /legal/index.wml document, create a new section "Legal
information" with links to /privacy, /trademark and /license (maybe more)
* In the menu of the homepage (and the menu at the footer of every
page), in the section "About Debian", place links to "Legal info" and
"Data privacy".

I will create a branch in the webwml repo named
"bug900552-privacypolicy", and upload the privacy.wml file there.

This way we can work there  (e.g. I would submit obvious fixes as 
->  etc) and the document will not be shown in the Debian website,
at least until my question 1 and/or 2 are clarified.

4.- About the content of the document, I have some comments but I prefer
to send diffs as patches in separate messages, so they can discussed or
merged individually.

Thanks!
-- 
Laura Arjona Reina
https://wiki.debian.org/LauraArjona

Bug#901269: radeontop FTCBFS: uses the build architecture pkg-config

[Helmut Grohne]

Source: radeontop
Version: 1.0-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

radeontop fails to cross build from source, because the upstream
Makefile hard codes the build architecture pkg-config. After making it
substitutable, it still fails, because make install insists on
rebuilding radeontop, but dh_auto_install does not supply cross tools
(unlike dh_auto_build). This is because it expects a .git directory to
derive the version from. The embedded version for Debian builds will
always be "unknown". I didn't figure out how to fix that, but simply
passing cross tools there as well works. Please consider applying the
attached patch.

Helmut
diff --minimal -Nru radeontop-1.0/debian/changelog 
radeontop-1.0/debian/changelog
--- radeontop-1.0/debian/changelog  2017-04-08 19:26:11.0 +0200
+++ radeontop-1.0/debian/changelog  2018-06-10 20:47:20.0 +0200
@@ -1,3 +1,10 @@
+radeontop (1.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ cross.patch: make pkg-config substitutable
++ Use dpkg's buildtools.mk to supply cross tools for make install.
+
+ -- Helmut Grohne   Sun, 10 Jun 2018 20:47:20 +0200
+
 radeontop (1.0-1) unstable; urgency=medium
 
   * New upstream release.
diff --minimal -Nru radeontop-1.0/debian/patches/cross.patch 
radeontop-1.0/debian/patches/cross.patch
--- radeontop-1.0/debian/patches/cross.patch1970-01-01 01:00:00.0 
+0100
+++ radeontop-1.0/debian/patches/cross.patch2018-06-10 20:47:17.0 
+0200
@@ -0,0 +1,47 @@
+--- radeontop-1.0.orig/Makefile
 radeontop-1.0/Makefile
+@@ -27,17 +27,18 @@
+ CFLAGS_SECTIONED = -ffunction-sections -fdata-sections
+ LDFLAGS_SECTIONED = -Wl,-gc-sections
+ 
++PKG_CONFIG ?= pkg-config
+ CFLAGS ?= -Os
+ CFLAGS += -Wall -Wextra -pthread
+ CFLAGS += -Iinclude
+ CFLAGS += $(CFLAGS_SECTIONED)
+-CFLAGS += $(shell pkg-config --cflags pciaccess)
+-CFLAGS += $(shell pkg-config --cflags libdrm)
++CFLAGS += $(shell $(PKG_CONFIG) --cflags pciaccess)
++CFLAGS += $(shell $(PKG_CONFIG) --cflags libdrm)
+ ifeq ($(xcb), 1)
+-  CFLAGS += $(shell pkg-config --cflags xcb xcb-dri2)
++  CFLAGS += $(shell $(PKG_CONFIG) --cflags xcb xcb-dri2)
+   CFLAGS += -DENABLE_XCB=1
+ endif
+-CFLAGS += $(shell pkg-config --cflags ncurses 2>/dev/null)
++CFLAGS += $(shell $(PKG_CONFIG) --cflags ncurses 2>/dev/null)
+ 
+ # Comment this if you don't want translations
+ ifeq ($(nls), 1)
+@@ -58,16 +59,16 @@
+ 
+ LDFLAGS ?= -Wl,-O1
+ LDFLAGS += $(LDFLAGS_SECTIONED)
+-LIBS += $(shell pkg-config --libs pciaccess)
+-LIBS += $(shell pkg-config --libs libdrm)
++LIBS += $(shell $(PKG_CONFIG) --libs pciaccess)
++LIBS += $(shell $(PKG_CONFIG) --libs libdrm)
+ ifeq ($(xcb), 1)
+-  xcb_LIBS += $(shell pkg-config --libs xcb xcb-dri2)
++  xcb_LIBS += $(shell $(PKG_CONFIG) --libs xcb xcb-dri2)
+   LIBS += -ldl
+ endif
+ 
+ # On some distros, you might have to change this to ncursesw
+-LIBS += $(shell pkg-config --libs ncursesw 2>/dev/null || \
+-  shell pkg-config --libs ncurses 2>/dev/null || \
++LIBS += $(shell $(PKG_CONFIG) --libs ncursesw 2>/dev/null || \
++  $(PKG_CONFIG) --libs ncurses 2>/dev/null || \
+   echo "-lncurses")
+ 
+ .PHONY: all clean install man dist
diff --minimal -Nru radeontop-1.0/debian/patches/series 
radeontop-1.0/debian/patches/series
--- radeontop-1.0/debian/patches/series 1970-01-01 01:00:00.0 +0100
+++ radeontop-1.0/debian/patches/series 2018-06-10 20:46:34.0 +0200
@@ -0,0 +1 @@
+cross.patch
diff --minimal -Nru radeontop-1.0/debian/rules radeontop-1.0/debian/rules
--- radeontop-1.0/debian/rules  2017-04-08 19:03:34.0 +0200
+++ radeontop-1.0/debian/rules  2018-06-10 20:47:20.0 +0200
@@ -1,6 +1,9 @@
 #!/usr/bin/make -f
 # -*- makefile -*-
 
+DPKG_EXPORT_BUILDTOOLS=1
+-include /usr/share/dpkg/buildtools.mk
+
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 export debug=1

Bug#901268: libsoil FTCBFS: uses the build architecture compiler

[Helmut Grohne]

Source: libsoil
Version: 1.07~20080707.dfsg-4
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

libsoil fails to cross build from source, because it does not pass cross
tools to make. Using dh_auto_build is the easiest way to fix that. Still
the alternate makefile hard codes gcc in one places. The attached patch
fixes both and makes libsoil cross build successfully. Please consider
applying it.

Helmut
diff --minimal -Nru libsoil-1.07~20080707.dfsg/debian/changelog 
libsoil-1.07~20080707.dfsg/debian/changelog
--- libsoil-1.07~20080707.dfsg/debian/changelog 2017-11-09 22:12:08.0 
+0100
+++ libsoil-1.07~20080707.dfsg/debian/changelog 2018-06-10 20:06:07.0 
+0200
@@ -1,3 +1,12 @@
+libsoil (1.07~20080707.dfsg-4.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ Let dh_auto_build pass cross tools to make.
++ cross.patch: make gcc substitutable
+
+ -- Helmut Grohne   Sun, 10 Jun 2018 20:06:07 +0200
+
 libsoil (1.07~20080707.dfsg-4) unstable; urgency=medium
 
   * Add dependency from -dev to library package (Closes: #881071)
diff --minimal -Nru libsoil-1.07~20080707.dfsg/debian/patches/cross.patch 
libsoil-1.07~20080707.dfsg/debian/patches/cross.patch
--- libsoil-1.07~20080707.dfsg/debian/patches/cross.patch   1970-01-01 
01:00:00.0 +0100
+++ libsoil-1.07~20080707.dfsg/debian/patches/cross.patch   2018-06-10 
20:06:07.0 +0200
@@ -0,0 +1,11 @@
+--- libsoil-1.07~20080707.dfsg.orig/projects/makefile/alternate Makefile.txt   
 libsoil-1.07~20080707.dfsg/projects/makefile/alternate Makefile.txt
+@@ -29,7 +29,7 @@
+   # create static library
+   # ar -cvq $(LIBNAME).a $(OFILES)
+   # create shared library
+-  gcc -shared -Wl,-soname,$(LIBNAME).so.$(MAJOR) -o 
$(LIBNAME).so.$(VERSION) $(OFILES) -lGL -lm
++  $(CC) -shared -Wl,-soname,$(LIBNAME).so.$(MAJOR) -o 
$(LIBNAME).so.$(VERSION) $(OFILES) -lGL -lm
+ 
+ install:
+   $(INSTALL_DIR) $(DESTDIR)/$(INCLUDEDIR)
diff --minimal -Nru libsoil-1.07~20080707.dfsg/debian/patches/series 
libsoil-1.07~20080707.dfsg/debian/patches/series
--- libsoil-1.07~20080707.dfsg/debian/patches/series2017-11-09 
22:04:17.0 +0100
+++ libsoil-1.07~20080707.dfsg/debian/patches/series2018-06-10 
20:06:07.0 +0200
@@ -1 +1,2 @@
 linking_correctly.patch
+cross.patch
diff --minimal -Nru libsoil-1.07~20080707.dfsg/debian/rules 
libsoil-1.07~20080707.dfsg/debian/rules
--- libsoil-1.07~20080707.dfsg/debian/rules 2017-11-09 22:04:17.0 
+0100
+++ libsoil-1.07~20080707.dfsg/debian/rules 2018-06-10 20:06:04.0 
+0200
@@ -1,17 +1,16 @@
 #!/usr/bin/make -f
 
 %:
-   dh $@
+   dh $@ --sourcedirectory=src --buildsystem=makefile
 
 override_dh_auto_build:
-   cd src && $(MAKE) -f ../projects/makefile/alternate\ Makefile.txt
-
+   dh_auto_build -- -f ../projects/makefile/alternate\ Makefile.txt
 
 override_dh_auto_clean:
-   cd src && $(MAKE) -f ../projects/makefile/alternate\ Makefile.txt clean
+   dh_auto_clean -- -f ../projects/makefile/alternate\ Makefile.txt
 
 override_dh_auto_install:
-   cd src && $(MAKE) -f ../projects/makefile/alternate\ Makefile.txt 
DESTDIR=$(CURDIR)/debian/tmp install
+   dh_auto_install -- -f ../projects/makefile/alternate\ Makefile.txt 
DESTDIR=$(CURDIR)/debian/tmp
 
 override_dh_strip:
dh_strip --dbgsym-migration='libsoil1-dbg (<< 1.07~20080707.dfsg-2~)'

Bug#899384: vlc: Hardware acceleration fails after upgrade to 3.0.2

[Antoni Marcinek]

OK. So basically this means 3 possible upstreams: optirun, Qt or VLC, since
I guess this is beyond Debian.

I think you can close the issue.

Actually I managed to find a workaround that I will report at
https://forum.videolan.org/viewtopic.php?f=13&t=144411 as I still believe
that there is a regression in VLC 3.0.2.


2018-06-10 18:42 GMT+02:00 Sebastian Ramacher :

> On 2018-06-05 10:13:19, Antoni Marcinek wrote:
> > > VA-API was not automatically probed in VLC 2.2. This is expected.
> > > VDPAU fails, and then VLC falls back to software decoding.
> > >
> > > In VLC 3.0, VA-API probing fails due to insufficient hardware
> > capabilities, so
> > > VLC uses software decoding as well. So no differences.
> > >
> > > --
> > > Rémi Denis-Courmont
> >
> > Sorry, I didn't notice this message earlier. Thank you.
> >
> > OK, so it is not about hardware acceleration. However something did
> change
> > between VLC versions in Debian what changes behaviour of software
> decoding.
> > The title of the bug report is wrong now, but I guess the issue of
> software
> > decoding should still be addressed. Should I send output of vlc -vvv for
> > VLC 3.0.2?
> >
> >
> > Still it is not clear who should address the problem of optirun + VLC-Qt.
>
> As mentioned in another subthread: please seek help from someone who's
> familiar
> with optirun, ideally someone who's also familiar with Qt and VLC.
>
> Cheers
> --
> Sebastian Ramacher
>

Bug#901085: libur-perl: FTBFS with Perl 5.28: test failures

[gregor herrmann]

On Sun, 10 Jun 2018 16:45:06 +0300, Niko Tyni wrote:

> > > > Confirmed, and I can offer even more failures:
> > > > # died: Error while autoloading with 'use 
> > > > CmdTest::Thing::/build/libur-perl-0.460+ds/t//CmdTest/Thing/Create': 
> > > > Unknown regexp modifier "/b" at (eval 234) line 1, at end of line
> > > You seem to be testing 0.460+ds while sid has 0.450?
> > Oh, right, I was just building from what we have in git, sorry for
> > not checking the versions.
> These were #901241, should be fixed in 0.460+ds-1 I just uploaded.

Ack, thanks!
I can confirm that 0.460+ds-1 builds with 5.26 and has the same
errors as in your original report with 5.28.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: David Bowie: Starman


signature.asc
Description: Digital Signature

Bug#901228: lintian: False positive for "r => littler (usr/lib/R/site-library/rjson/rpc_server/server.r) #!/usr/bin/r"

[Chris Lamb]

tags 901228 + pending
thanks

Fixed in Git, pending upload:

  
https://salsa.debian.org/lintian/lintian/commit/95eaa1261286f18a8e286cec184f5f1a970336c3

  data/scripts/interpreters | 2 +-
  debian/changelog  | 4 
  2 files changed, 5 insertions(+), 1 deletion(-)


Regards,

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

Bug#901264: mirror submission for mirror.yannic-bonenberger.com

[Marco d'Itri]

On Jun 10, Yannic Bonenberger  wrote:

> Country: DE Germany
It looks in Switzerland to me. Can you clarify this please?

Also, please remove the 6to4 address from the 
mirror.yannic-bonenberger.com name: it does not help anybody and does 
not not work anyway.

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#901252: vlc: Fail to launch, QPainter not active

[Sebastian Ramacher]

[Please keep the bug in CC]

On 2018-06-10 17:50:20, John Hendricks wrote:
> I apologize, this is the first bug report I've ever filed. I'm not sure where 
> VLC keeps the log file, so I will attach the output of vlc -vvv in a text 
> file.
> I am unable to produce output from the given reportbug -n command. Anything I 
> can do to help just please let me know and please be patient with me, I will 
> do whatever I can.

Please start a new bug report against vlc, copy the complete dependency
information and send it to this report.

For the log, please run vlc as:

vlc -vv >log.txt 2>&1

and then attach log.txt.

Cheers

> 
> On Sunday, June 10, 2018, 12:39:33 PM EDT, Sebastian Ramacher 
>  wrote:  
>  
>  Control: tags -1 + moreinfo unpreoducible
> 
> Hi
> 
> On 2018-06-10 11:52:47, John Hendricks wrote:
> > Source: vlc
> > Version: 3
> > Severity: grave
> > Tags: upstream
> > Justification: renders package unusable
> > 
> > Dear Maintainer,
> > 
> > I upgraded to VLC3 from Synaptic's Mark All Updates option, the bug started
> > here.
> > 
> > I ran a complete purge of all VLC packages and reinstall via rebuild from
> > source.
> > 
> > No results, bug persisted
> 
> This bug lacks many details which make this report unactionable. Please, while
> having vlc installed, run reportbug -N NN vlc (replace the bug number with
> the number of this bug) and let us know all the data that reportbug generates
> (dependencies and versions, correct vlc version and so on). Also, please
> reproduce the problem using vlc -vvv and attach the log output to the bug
> report.
> 
> Cheers
> 
> > 
> > 
> > 
> > -- System Information:
> > Debian Release: 9.4
> >  APT prefers stable-updates
> >  APT policy: (500, 'stable-updates'), (500, 'stable')
> > Architecture: i386 (i686)
> > 
> > Kernel: Linux 4.9.0-3-686-pae (SMP w/4 CPU cores)
> > Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
> > LANGUAGE=en_US.utf8 (charmap=UTF-8)
> > Shell: /bin/sh linked to /bin/dash
> > Init: systemd (via /run/systemd/system)
> > 
> > ___
> > pkg-multimedia-maintainers mailing list
> > pkg-multimedia-maintain...@alioth-lists.debian.net
> > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
> 
> -- 
> Sebastian Ramacher  



-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#898024: [Pkg-javascript-devel] Bug#898024: Bug#898024: trying to overwrite '/usr/include/nodejs/common.gypi', which is also in package nodejs-dev 10.0.0~dfsg-2

[Jonas Smedegaard]

Hi Jérémy,

Quoting Jérémy Lal (2018-06-10 16:51:14)
> 2018-06-10 10:26 GMT+02:00 Andreas Beckmann :
> > The 8 -> 10 upgrade path does not work either:
> >
> >   Selecting previously unselected package libnode64-dev.
> >   Preparing to unpack .../libnode64-dev_10.3.0~dfsg-1_amd64.deb ...
> >   Unpacking libnode64-dev (10.3.0~dfsg-1) ...
> >   dpkg: error processing archive 
> > /var/cache/apt/archives/libnode64-dev_10.3.0~dfsg-1_amd64.deb (--unpack):
> >trying to overwrite '/usr/include/nodejs/common.gypi', which is also in 
> > package nodejs-dev 8.11.2~dfsg-1
> >   dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
> >   Errors were encountered while processing:
> >/var/cache/apt/archives/libnode64-dev_10.3.0~dfsg-1_amd64.deb
> >
> > You probably need to add
> >   Breaks+Replaces: nodejs-dev (<< 10.0.0~dfsg1-3)
> > to libnode64-dev for properly taking over /usr/include/nodejs/*
> >
> 
> Hi Jonas,
> 
> to do it i'm trying
> CDBS_BREAKS_libnode$(ABI)-dev = nodejs-dev (<< 10.0.0~dfsg1-3)
> CDBS_REPLACES_libnode$(ABI)-dev = nodejs-dev (<< 10.0.0~dfsg1-3)
> 
> but it does not generate the expected fields.
> Did i make some mistake here ?

Sorry, I don't locate those strings - which branch of which git are you 
trying out the above?

It looks correct - but works only in concert with corresponding hints in 
control{.in.in} file.  See e.g. git commit f31d94a (i.e. _reverse_ of 
that, and adding Replaces: ${cdbs:Replaces}).


Hope that helps,

 - Jonas

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

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


signature.asc
Description: signature