Bug#893156: Request to reset src:mariadb-10.1 to previous known working state in Debian testing/unstable archives

[Otto Kekäläinen]

tags 893156 - moreinfo
reopen 893156

Hello!

> Please elaborate why you can't revert all the changes to 10.1.28-2 and
> then upload that as 1:10.1.29+really10.1.28-1 until you are ready to
> upload 10.1.29 again? Failing that, you will also need to really justify
> why you cannot bump the epoch again.

The epoch was introduced by another DD who uploaded a very bad 10.2
and then used the epoch to downgrade the package back to 10.1. Such
use of the epoch is not what the policy states as valid use cases for
the epoch (https://www.debian.org/doc/debian-policy/#version) and the
policy in particular forbids 'silly orderings' which this now is.

Such a change was done in a panic by the other DD and without thinking
of the consequences.

This will result in wide spread breakage when apt starts to upgrade
all previous 10.1, 10.2 and 10.3 installs into this 1:10.1 version as
I explained in my first mail. I tried my best to be very elaborate in
the first mail.

If the epoch isn't removed, then somebody needs to fix the world
around us and introduce the epoch in all previous and future packages
of any 10.1+ MariaDB in any repository out there. Coordinating such a
thing is too much work for me, sorry. I don't want to accept the
situation that this single change done by one DD is completely
irreversible with the cost that everybody else in the world need to do
a lot of work and adapt to it. At that point I'd rather give up and
let somebody else deal with the fallout.

> Manually modifying dak's records to fix his is, err, unlikely to happen.

Yes, I know, but I have to try. I feel I should try to do something to
save this package after this "sabotage" and not directly orphan it.


Thanks for the polite answer,

- Otto

Bug#893465: gnome-shell-extension-tilix-dropdown: New version of tilix does not support quake mode on Wayland

[Mattia Monga]

Package: gnome-shell-extension-tilix-dropdown
Version: 5.1-1
Severity: important
Tags: patch

Since version 1.7.7 tilix does not support quake mode on Wayland (see
https://github.com/gnunn1/tilix/issues/1314), but Wayland is the default on
Gnome.

I think this package should (1) depend on an older version of tilix or (2)
execute tilix on the x11 backend. The attached patch implements solution (2),
however having it as preference option would be better.


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

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

Versions of packages gnome-shell-extension-tilix-dropdown depends on:
ii  gnome-shell  3.28.0-1
ii  tilix1.7.7-1

gnome-shell-extension-tilix-dropdown recommends no packages.

gnome-shell-extension-tilix-dropdown suggests no packages.

-- no debconf information

-- debsums errors found:
debsums: changed file 
/usr/share/gnome-shell/extensions/TilixDropdown@ivku...@gmail.com/extension.js 
(from gnome-shell-extension-tilix-dropdown package)
--- 
/usr/share/gnome-shell/extensions/TilixDropdown@ivku...@gmail.com/extension.js.orig
 2018-03-19 07:26:05.766147868 +0100
+++ 
/usr/share/gnome-shell/extensions/TilixDropdown@ivku...@gmail.com/extension.js  
2018-03-19 07:21:38.88143 +0100
@@ -40,7 +40,7 @@
 
 function _startTilix() {
 try {
-Main.Util.trySpawnCommandLine('tilix --quake');
+Main.Util.trySpawnCommandLine('env GDK_BACKEND=x11 tilix --quake');
 } catch(err) {
 Main.notify("Couldn't start tilix, is it installed?");
 }

Bug#893464: RM: gcompris -- RoQA; dead upstream, replaced by src:gcompris-qt

[Pino Toscano]

Package: ftp.debian.org
Severity: normal

Hi,

src:gcompris represents the old version, based on GTK, which is no more
developed upstream -- all the efforts are now on the Qt version, which
is the one that gets new features and such. Shipping the old version
in Buster is IMHO not a good idea.

Hence, I request the removal of src:gcompris, which cannot be even
uploaded now in unstable, since src:gcompris-qt took over the gcompris
binary as transitional package.

Thanks,
-- 
Pino

Bug#893463: libmail-dkim-perl: Mail::DKIM does not enforce minimum RSA key sizes

[Scott Kitterman]

Package: libmail-dkim-perl
Version: 0.44-1
Severity: important
Tags: upstream

The IETF recently published updated guidance on minimum RSA key sizes for use
with DKIM[1].  I decided to check in Debian to see what packages might need to
be updated as a result.  I've looked and I can't find where Mail::DKIM checks
key size at all.  This is a security concern since it allows trivially
factorable keys to produce apparently valid signatures (just last year I ran
into a consulting client with a 384 bit key that was surprised his DKIM wasn't
working very well anymore).

Note, I'm not a Perl person, so I may have missed it when I read the code.
Assuming I'm right though, while I'm not sure what the best approach to
resolve this is, but I do think it's concerning and needs to be fixed.

Scott K


[1] https://tools.ietf.org/html/rfc8301

Bug#893462: fritzing: crashes after long showing splash

[treaki]

Package: fritzing
Version: 0.9.3b+dfsg-4.1
Severity: important

Dear Maintainer,

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


   * What led up to the situation?
apt install fritzing
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
$ fritzing
** (fritzing:24990): WARNING **: Couldn't register with accessibility 
bus: Did not receive a reply. Possible causes include: the remote 
application did not send a reply, the message bus security policy 
blocked the reply, the reply timeout expired, or the network connection 
was broken.

Segmentation fault

   * What was the outcome of this action?
ive seen the fritzing splash long long long time and then ive got a crash
   * What outcome did you expect instead?
some main window of fritzing i guess ;)

thanks in advance, keep up the good work


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

Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)

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

Versions of packages fritzing depends on:
ii  fritzing-data0.9.3b+dfsg-4.1
ii  libc62.27-2
ii  libgcc1  1:8-20180207-2
ii  libgit2-26   0.26.0+dfsg.1-1.1+b1
ii  libgl1   1.0.0-2
ii  libqt5concurrent55.9.2+dfsg-12
ii  libqt5core5a 5.9.2+dfsg-10
ii  libqt5gui5   5.9.2+dfsg-10
ii  libqt5network5   5.9.2+dfsg-10
ii  libqt5printsupport5  5.9.2+dfsg-10
ii  libqt5serialport55.9.2-2
ii  libqt5sql5   5.9.2+dfsg-10
ii  libqt5sql5-sqlite5.9.2+dfsg-10
ii  libqt5svg5   5.9.2-3
ii  libqt5widgets5   5.9.2+dfsg-10
ii  libqt5xml5   5.9.2+dfsg-10
ii  libstdc++6   8-20180207-2
ii  zlib1g   1:1.2.8.dfsg-5

fritzing recommends no packages.

Versions of packages fritzing suggests:
pn  fritzing-parts  

-- no debconf information

Bug#893460: mbuffer: make autopkgtests pass on all archs

[Steve Langasek]

Package: mbuffer
Version: 20171011-1
Severity: minor
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic ubuntu-patch autopkgtest

Dear Peter,

With mbuffer 20171011-1, while the autopkgtests continue to pass fine on
amd64 as seen at ,
one of the tests fails on armhf and i386 as seen in Ubuntu at
.

I don't understand why the filename output of the tests is different on
armhf and i386 vs. other architectures, but I can confirm that a slight
change to the globbing in the test itself allows the test to pass.  The
attached patch has been uploaded to Ubuntu to fix this test failure.

Please consider applying this change in Debian as well.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru mbuffer-20171011/debian/patches/fix-upstream-test.patch 
mbuffer-20171011/debian/patches/fix-upstream-test.patch
--- mbuffer-20171011/debian/patches/fix-upstream-test.patch 1969-12-31 
16:00:00.0 -0800
+++ mbuffer-20171011/debian/patches/fix-upstream-test.patch 2018-03-18 
22:43:08.0 -0700
@@ -0,0 +1,33 @@
+Description: fix a test case whose file glob fails on some archs
+ For whatever reason, on armhf and i386, mbuffer outputs a single file named
+ 'output-test4' or 'output-test5' in its tests, whereas on other archs it
+ outputs multiple files matching the pattern "output-testN.*".  This is not
+ the purpose of the test, and tests 4 and 5 in fact handle the output
+ filenames inconsistently; so fix the test so that it works on all archs.
+Author: Steve Langasek 
+Last-Updated: 2018-03-18
+
+Index: mbuffer-20171011/Makefile.in
+===
+--- mbuffer-20171011.orig/Makefile.in
 mbuffer-20171011/Makefile.in
+@@ -118,7 +118,7 @@
+   rm -f output-$@.tar.*
+   cat mbuffer | LD_PRELOAD=./tapetest.so ./mbuffer -f -o output-$@ -H -A 
"echo '[$@] Replacing tape'"
+   cat output-$@* | openssl md5 > $@.md5
+-  rm -f output-$@.*
++  rm -f output-$@*
+   sync
+   diff $@.md5 mbuffer.md5 > $@
+ 
+@@ -126,8 +126,8 @@
+ test5: test.md5 tapetest.so mbuffer.md5
+   rm -f output-$@.tar.*
+   cat mbuffer | LD_PRELOAD=./tapetest.so ./mbuffer -f -o output-$@ -H -A 
"echo '[$@] Replacing tape'" --tapeaware
+-  cat output-$@.* | openssl md5 > $@.md5
+-  rm -f output-$@.*
++  cat output-$@* | openssl md5 > $@.md5
++  rm -f output-$@*
+   sync
+   diff $@.md5 mbuffer.md5 > $@
+ 
diff -Nru mbuffer-20171011/debian/patches/series 
mbuffer-20171011/debian/patches/series
--- mbuffer-20171011/debian/patches/series  2017-10-29 13:12:08.0 
-0700
+++ mbuffer-20171011/debian/patches/series  2018-03-18 22:38:13.0 
-0700
@@ -5,3 +5,4 @@
 close-errno.patch
 test-library.patch
 config-mbuffer.patch
+fix-upstream-test.patch

Bug#893461: libdkim does not enforce minimum RSA key sizes

[Scott Kitterman]

Package: libdkim
Version: 1:1.0.21-3
Severity: important
Tags: upstream

The IETF recently published updated guidance on minimum RSA key sizes for use
with DKIM[1].  I decided to check in Debian to see what packages might need to
be updated as a result.  I've looked and I can't find where libdkim checks the
key size at all.  This is a security concern since it allows trivially
factorable keys to produce apparently valid signatures (just last year I ran
into a consulting client with a 384 bit key that was surprised his DKIM wasn't
working very well anymore).

Given this looks pretty dead upstream and only has one user, I'm not sure what
the best approach to resolve this is, but I do think it's concerning.

Scott K


[1] https://tools.ietf.org/html/rfc8301

Bug#883569: libpam-systemd: Prefer systemd-sysv over systemd-shim

[Michael Biebl]

On Thu, 8 Mar 2018 12:47:22 +0100 Martin Pitt  wrote:
> Hello Michael,
> 
> Michael Biebl [2018-03-08 12:16 +0100]:
> > Am 08.03.2018 um 09:22 schrieb Martin Pitt:
> > There is one case: someone installs a minimal system without
> > libpam-systemd, then switches to sysvinit-core, then installs a desktop
> > environment which pulls libpam-systemd (via polkit in most cases). In
> > that specific scenario, apt will uninstall sysvinit-core and install
> > systemd-sysv again.
> 
> Good point. The same in the other direction (install minimal system, then a
> desktop which pulls in libpam-systemd) ought to be satisfied with the already
> installed systemd-sysv, so that should work (modulo apt getting confused).
> 
> > Is this something the TC has considered and is ok with?
> 
> I don't think they considered this at all. They simply said that there is no
> longer an ordering requirement from their side, and it's back to us
> maintainer's consideration.

So, what are we going to do now then?



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



signature.asc
Description: OpenPGP digital signature

Bug#893459: RM: ruby-flipper-active-record -- ROM; ruby-flipper now provides ruby-flipper-active-record

[Pirate Praveen]

Package: ftp.debian.org
Severity: normal

From 0.13-2, ruby-flipper now provides ruby-flipper-active-record also.
Source package now takes github tarballs which includes all flipper-*
gems instead of separate source packages made from their corresponding
gems.

This was done since gitlab 10 required yet another flipper gem
(flipper-active_support_cache_store) and we realized creating even more
source packages could be avoided since github contains all gems in a
single repo.



signature.asc
Description: OpenPGP digital signature

Bug#893208: Pending fixes for bugs in the dbus-java package

[pkg-java-maintainers]

tag 893208 + pending
thanks

Some bugs in the dbus-java package are closed in revision
32e719f0448abd72d25d04f2b8aa69080049aabf in branch 'master' by tony
mancill

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

Commit message:

Update no-translations.patch to ignore resources bundle (Closes: #893208)

Bug#893208: dbus-java-bin: java.lang.ExceptionInInitializerError and hang when invoking ListDBus

[tony mancill]

On Sat, Mar 17, 2018 at 09:13:23AM +, Daniel Kahn Gillmor wrote:
> Package: dbus-java-bin
> Version: 2.8-8
> Severity: normal
> 
> 1 dkg@alice:~$ ListDBus 
>
> (snip)
>
> Exception in thread "main" java.lang.ExceptionInInitializerError
>   at 
> org.freedesktop.dbus.DBusConnection.disconnect(DBusConnection.java:759)
>   at org.freedesktop.dbus.bin.ListDBus.main(ListDBus.java:72)
> Caused by: java.util.MissingResourceException: Can't find bundle for base 
> name dbusjava_localized, locale en_US
> 
> (snip)
> 
> at this point, it hangs until i hit ctrl-C.
> 
> this is pretty opaque to me, but i can provide you with more
> information for debuggin if you tell me specifically what you're
> looking for.

Hi Daniel,

Thank you for reporting this issue.  There is a resources bundle that
was intended to contain translations, but only en_GB was ever included,
and so the translations were dropped in a previous upload.  However,
there is one piece of the code that is still trying to load them.

We'll get it fixed.

Cheers,
tony


signature.asc
Description: PGP signature

Bug#893458: libundead depends on cruft packages.

[peter green]

Package: libundead
Version: 1.0.9-1
Severity: serious

libundead-dev depends on libphobos2-ldc-dev
libundead0 depends on libphobos2-ldc76

Neither of these packages is built by ldc anymore. They seem to have been 
replaced by  libphobos2-ldc-shared-dev and libphobos2-ldc-shared78

It seems there has not been an attempt to been an attempt to binnmu libundead 
for this transition in Debian. When we binnmu'd it in raspbian the dependency 
on libphobos2-ldc76 was replaced by libphobos2-ldc-shared78 but the dependency 
on libphobos2-ldc-dev remained.

Please update your package.

Bug#893424: Cannot uninstall package

[Ryan Kavanagh]

On Mon, Mar 19, 2018 at 01:42:09AM +0100, Andreas Beckmann wrote:
> Interesting. The empty directory shows up with size 0.
> What filesystem do you use for / ?

Similarly here:

rak@zeta:~$ ls -lashR /etc/mail
/etc/mail:
total 24K
   0 drwxr-xr-x 1 root root  138 Mar 18 14:32 .
   0 drwxr-xr-x 1 root root 5.3K Mar 18 17:51 ..
4.0K -rw-r--r-- 1 root root  281 Jan 13 17:43 address.resolve
   0 drwxr-xr-x 1 root root0 Jan 13 17:43 m4
   0 drwxr-xr-x 1 root root   16 Mar 18 13:30 peers
 12K -rw-r--r-- 1 root root  12K Mar 18 13:33 sendmail.conf
4.0K -rw-r--r-- 1 root root  148 Jan 13 17:43 service.switch
4.0K -rw-r--r-- 1 root root  179 Jan 13 17:43 service.switch-nodns

/etc/mail/m4:
total 0
0 drwxr-xr-x 1 root root   0 Jan 13 17:43 .
0 drwxr-xr-x 1 root root 138 Mar 18 14:32 ..

/etc/mail/peers:
total 4.0K
   0 drwxr-xr-x 1 root root  16 Mar 18 13:30 .
   0 drwxr-xr-x 1 root root 138 Mar 18 14:32 ..
4.0K -rw-r--r-- 1 root root 328 Jan 13 17:43 provider

> What filesystem do you use for / ?

/dev/sda1 on / type btrfs (rw,relatime,ssd,space_cache,subvolid=5,subvol=/)

> The error should be triggered by this line in the prerm:
> # Remove empty files (probably touched databases)
> find /etc/mail -maxdepth 1 -size 0 | xargs -r rm;

Yeah, I think the problem is that it's calling 'rm' on directories. Tacking on a
'-type f' like you suggested (and perhaps even a '-delete' to skip the xargs
bit) would likely do the trick.

> $ find /etc/mail -maxdepth 1 -size 0
> $ find /etc/mail -maxdepth 1 -type f -size 0

rak@zeta:~$ find /etc/mail -maxdepth 1 -size 0
/etc/mail/m4
rak@zeta:~$ find /etc/mail -maxdepth 1 -type f -size 0
rak@zeta:~$

> The first should output /etc/mail/m4, the second should output nothing.

Your hunch on the error was right. I tried adding "set -x" to the top of the
prerm file, and got the following output:

rak@zeta:~$ sudo vim /var/lib/dpkg/info/sendmail-base.prerm
No protocol specified
rak@zeta:~$ sudo apt-get remove sendmail-base
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libxfont1 lockfile-progs
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  sendmail-base
0 upgraded, 0 newly installed, 1 to remove and 57 not upgraded.
After this operation, 867 kB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 389313 files and directories currently installed.)
Removing sendmail-base (8.15.2-10) ...
+ PACKAGE=sendmail-base
+ [ remove = remove ]
+ [ -x /usr/sbin/update-inetd ]
+ update-inetd --group MAIL --disable smtp,smtps,submission
+ [ -L /etc/mail/aliases ]
+ [ -f /etc/mail/aliases ]
+ rm -f /etc/cron.d/sendmail
+ rm -f /usr/lib/sasl/Sendmail.conf
+ rm -rf /var/lib/sendmail
+ rm -rf /var/run/sendmail
+ [ -x /etc/init.d/sendmail ]
+ [ -L /var/spool/mqueue ]
+ [ -d /var/spool/mqueue ]
+ [ -L /var/spool/mqueue-client ]
+ [ -d /var/spool/mqueue-client ]
+ rm -f /etc/mail/*.db /etc/mail/*.dir /etc/mail/*.pag
+ rm -f /etc/mail/sendmail.cf /etc/mail/sendmail.cf.old 
/etc/mail/sendmail.cf.errors /etc/mail/sendmail.mc.old /etc/mail/submit.cf 
/etc/mail/submit.cf.errors /etc/mail/submit.mc.old /etc/mail/databases 
/etc/mail/Makefile
+ rm -rf /etc/mail/smrsh /etc/mail/sasl /etc/mail/tls
+ find /etc/mail -maxdepth 1 -size 0
+ xargs -r rm
rm: cannot remove '/etc/mail/m4': Is a directory
dpkg: error processing package sendmail-base (--remove):
 installed sendmail-base package pre-removal script subprocess returned error 
exit status 123
Errors were encountered while processing:
 sendmail-base
E: Sub-process /usr/bin/dpkg returned an error code (1)

Hope this helps,
Ryan

-- 
|)|/  Ryan Kavanagh  | GPG: 4E46 9519 ED67 7734 268F
|\|\  https://rak.ac |  BD95 8F7B F8FC 4A11 C97A


signature.asc
Description: PGP signature

Bug#893457: skill.1: Some fixes in the manual

[Bjarni Ingi Gislason]

Package: procps
Version: 2:3.3.12-4
Severity: minor
Tags: patch

Dear Maintainers (also sent to pro...@freelist.org),

Input file is skill.1

mandoc: skill.1:9:13: WARNING: cannot parse date, using it verbatim: October 
2011
mandoc: skill.1:120:2: WARNING: empty block: UR

###

Test nr. 20:

Use a macro to change to the italic font, instead of \fI [1], if
possible.
The macros have the italic corrections, but "\c" removes them.
[1] man-pages(7)

84:\fB\-\-nslist \fIns,...\fR

#

Test nr. 24:

Change a HYPHEN-MINUS (code 0x55, 2D) to a minus (\-), if in front of a
name for an option.

94:.B snice -c seti -c crack +7

#

Test nr. 30:

Surround a block of comments with the macros ".ig" and "..".
The .\" (\#) at the beginning of each line is then not needed.
Makes it easier to add and remove text and adjust length of lines.

NO PATCH

2:.\" (The preceding line is a note to broken versions of man to tell
3:.\" them to pre-process this man page with tbl)
4:.\" Man page for skill and snice.
5:.\" Licensed under version 2 of the GNU General Public License.
6:.\" Written by Albert Cahalan, converted to a man page by
7:.\" Michael K. Johnson
8:.\"

#

Test nr. 38:

Email addresses use the macro ".MT" and end with ".ME".

113:.UR alb...@users.sf.net
120:.UR pro...@freelists.org

#

  Patch:

--- skill.1 2018-02-09 23:59:11.0 +
+++ skill.1.new 2018-03-19 01:58:50.0 +
@@ -81,7 +81,7 @@ The next expression is a command name.
 \fB\-\-ns \fIpid\fR
 Match the processes that belong to the same namespace as pid.
 .TP
-\fB\-\-nslist \fIns,...\fR
+\fB\-\-nslist \fIns\/\fR,\,\fI...\/\fR
 list which namespaces will be considered for the --ns option.
 Available namespaces: ipc, mnt, net, pid, user, uts.
 .PD
@@ -91,7 +91,7 @@ The behavior of signals is explained in
 manual page.
 .SH EXAMPLES
 .TP
-.B snice -c seti -c crack +7
+.B snice \-c seti \-c crack +7
 Slow down seti and crack commands.
 .TP
 .B skill \-KILL \-t /dev/pts/*
@@ -110,12 +110,12 @@ Stop three users.
 .SH STANDARDS
 No standards apply.
 .SH AUTHOR
-.UR alb...@users.sf.net
+.MT alb...@users.sf.net
 Albert Cahalan
-.UE
+.ME
 wrote skill and snice in 1999 as a replacement for a non-free
 version.
 .SH "REPORTING BUGS"
 Please send bug reports to
-.UR pro...@freelists.org
-.UE
+.MT pro...@freelists.org
+.ME


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

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

Versions of packages procps depends on:
ii  init-system-helpers  1.51
ii  libc62.27-2
ii  libncurses5  6.1-1
ii  libncursesw5 6.1-1
ii  libprocps6   2:3.3.12-4
ii  libtinfo56.1-1
ii  lsb-base 9.20170808

Versions of packages procps recommends:
ii  psmisc  23.1-1

procps suggests no packages.

-- Configuration Files:
/etc/init.d/procps changed [not included]

-- no debconf information

-- 
Bjarni I. Gislason

Bug#890751: rake FTBFS with Ruby 2.5: cannot load such file -- ubygems (LoadError)

[Georg Faerber]

I'll work on this today.

Cheers,
Georg


signature.asc
Description: Digital signature

Bug#893223: ruby: gem2.5 doesn't find anything on rubygems.org

[Antonio Terceiro]

Control: tag -1 + unreproducible moreinfo

Hello,

On Sat, Mar 17, 2018 at 12:58:22PM +0100, dimmie wrote:
> Package: ruby
> Version: 1:2.5.0
> Severity: important
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>* What led up to the situation?
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>* What was the outcome of this action?
>* What outcome did you expect instead?
> 
> Tried
> # gem2.5 list rmail --remote
>   (nothing found)
> # gem install rmail --remote
> ERROR:  Could not find a valid gem 'rmail' (>= 0), here is why:
>   Unable to download data from 
> http://production.s3.rubygems.org/latest_specs.4.8 - no such name 
> (http://production.s3.rubygems.org/specs.4.8.gz)
> [ downloaded the gem from rubygems.org and installed with
>   # gem install 
> ]
> ** End of the template - remove these template lines ***

I can't reproduce this locally. can you please ellaborate? can you still
reproduce this on your side? maybe this was a temporary issue with
rubygems.org, or with your network.


signature.asc
Description: PGP signature

Bug#886096: lintian: Emit warnings for Alioth URLs in packaging (migration to Salsa)

[Chris Lamb]

tags 886096 + pending
thanks

Thanks! Fixed in Git, pending upload:

  
https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=04f5f6facceb9c51502f066f82a14d30472eb962


Regards,

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

Bug#893451: Acknowledgement (linux: Build module for GPD Pocket fan support)

[Jeremy Stanley]

Tags: +patch

Proposed https://salsa.debian.org/kernel-team/linux/merge_requests/1
for this.

Bug#893456: jawn: FTBFS with java 9

[Andreas Beckmann]

Source: jawn
Version: 0.10.4-1
Severity: serious
Justification: fails to build from source

Hi,

jawn FTBFS with openjdk-9 as the default jdk:

...
# Executing command line:
java
-Xms1024m
-Xmx1024m
-XX:ReservedCodeCacheSize=128m
-XX:MaxMetaspaceSize=256m
-Dsbt.ivy.home=/build/jawn-0.10.4/debian/sbt_home/.ivy2
-Dsbt.override.build.repos=true
-Dsbt.global.base=/build/jawn-0.10.4/debian/sbt_home/.sbt
-jar
/build/jawn-0.10.4/bootstrapsbt/bin/sbt-launch.jar
"set offline := true"
packageBin
make-pom

Getting org.scala-sbt sbt 0.13.12 ...
:: retrieving :: org.scala-sbt#boot-app
confs: [default]
49 artifacts copied, 0 already retrieved (17462kB/94ms)
Getting Scala 2.10.6 (for sbt)...
:: retrieving :: org.scala-sbt#boot-scala
confs: [default]
5 artifacts copied, 0 already retrieved (24494kB/39ms)
error: error while loading package, Missing dependency 'object java.lang.Object 
in compiler mirror', required by 
/build/jawn-0.10.4/debian/sbt_home/.sbt/boot/scala-2.10.6/lib/scala-library.jar(scala/package.class)
error: error while loading package, Missing dependency 'object java.lang.Object 
in compiler mirror', required by 
/build/jawn-0.10.4/debian/sbt_home/.sbt/boot/scala-2.10.6/lib/scala-library.jar(scala/runtime/packag
e.class)
scala.reflect.internal.MissingRequirementError: object java.lang.Object in 
compiler mirror not found.
at 
scala.reflect.internal.MissingRequirementError$.signal(MissingRequirementError.scala:16)
at 
scala.reflect.internal.MissingRequirementError$.notFound(MissingRequirementError.scala:17)
...


Andreas


jawn_0.10.4-1.log.gz
Description: application/gzip

Bug#893455: Cannot configure network when installing ubuntu server in language other than English

[윤영수]

Package: netcfg
Version: 1.142
Severity: normal

Dear Maintainer,

We cannot configure network when installing ubuntu server in language other 
than English.

We finded that the reason is related to the source code of the network package 
‘netcfg’.

In dhcp.c of netcfg-1.142ubuntu5(netcfg package source code directory), the 
ubuntu server installer identifies the four network configuration methods by 
checking whether they begins with the letter ‘R’ or ‘C’ or ends in ‘k’ at line 
361~376(strcmp sucks), when we choose one of them.

Thus the four network configuration methods cannot be identified when 
installing in language other than English.

We hope that we can configure network when installing ubuntu server even in 
language other than English.

Please check the bug.

Regards,

Yeongsoo Yoon.

Bug#893454: libjloda-java: FTBFS with java 9

[Andreas Beckmann]

Source: libjloda-java
Version: 0.0+20170502-1
Severity: serious
Justification: fails to build from source

Hi,

libjloda-java FTBFS with openjdk-9 as default jdk:

compile:
[javac] Compiling 265 source files to 
/build/libjloda-java-0.0+20170502/antbuild/class
[javac] 
/build/libjloda-java-0.0+20170502/antbuild/src/jloda/phylo/PhyloTree.java:30: 
error: package com.sun.istack.internal is not visible
[javac] import com.sun.istack.internal.Nullable;
[javac]  ^
[javac]   (package com.sun.istack.internal is declared in module 
java.xml.bind, which is not in the module graph)
[javac] 
/build/libjloda-java-0.0+20170502/antbuild/src/jloda/graphview/NodeView.java:258:
 warning: [dep-ann] deprecated item is not annotated with @Deprecated
[javac] public void setShape(byte a) {
[javac] ^
[javac] 
/build/libjloda-java-0.0+20170502/antbuild/src/jloda/graphview/NodeView.java:268:
 warning: [dep-ann] deprecated item is not annotated with @Deprecated
[javac] public byte getShape() {
[javac] ^
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 1 error
[javac] 2 warnings


Andreas


libjloda-java_0.0+20170502-1_indep.log.gz
Description: application/gzip

Bug#893453: json4s: FTBFS with java 9

[Andreas Beckmann]

Source: json4s
Version: 3.5.0-1
Severity: serious
Justification: fails to build from source

Hi,

json4s started to FTBFS since the default jdk ws changed to openjdk 9.

...
# Executing command line:
java
-Xms1024m
-Xmx1024m
-XX:ReservedCodeCacheSize=128m
-XX:MaxMetaspaceSize=256m
-Dsbt.ivy.home=/build/json4s-3.5.0/debian/sbt_home/.ivy2
-Dsbt.override.build.repos=true
-Dsbt.global.base=/build/json4s-3.5.0/debian/sbt_home/.sbt
-jar
/build/json4s-3.5.0/bootstrapsbt/bin/sbt-launch.jar
"set offline := true"
packageBin
make-pom

Getting org.scala-sbt sbt 0.13.12 ...
:: retrieving :: org.scala-sbt#boot-app
confs: [default]
49 artifacts copied, 0 already retrieved (17462kB/172ms)
Getting Scala 2.10.6 (for sbt)...
:: retrieving :: org.scala-sbt#boot-scala
confs: [default]
5 artifacts copied, 0 already retrieved (24494kB/38ms)
error: error while loading package, Missing dependency 'object java.lang.Object 
in compiler mirror', required by 
/build/json4s-3.5.0/debian/sbt_home/.sbt/boot/scala-2.10.6/lib/scala-library.jar(scala/package.class)
error: error while loading package, Missing dependency 'object java.lang.Object 
in compiler mirror', required by 
/build/json4s-3.5.0/debian/sbt_home/.sbt/boot/scala-2.10.6/lib/scala-library.jar(scala/runtime/package.class)
scala.reflect.internal.MissingRequirementError: object java.lang.Object in 
compiler mirror not found.
at 
scala.reflect.internal.MissingRequirementError$.signal(MissingRequirementError.scala:16)
...


Andreas


json4s_3.5.0-1_indep.log.gz
Description: application/gzip

Bug#893452: kill.1: Some fixes in the manual

[Bjarni Ingi Gislason]

Package: procps
Version: 2:3.3.12-4
Severity: minor
Tags: patch

Dear Maintainers (also sent to pro...@freelist.org),

(the patch is in the attachment)

mandoc: kill.1:36:2: ERROR: skipping unknown macro: .TQ
mandoc: kill.1:38:2: ERROR: skipping unknown macro: .TQ
mandoc: kill.1:53:2: WARNING: line scope broken: SH breaks TP
mandoc: kill.1:8:12: WARNING: cannot parse date, using it verbatim: October 2011
mandoc: kill.1:92:2: WARNING: empty block: UR

###

Input file is kill.1


Test nr. 20:

Use a macro to change to the italic font, instead of \fI [1], if
possible.
The macros have the italic corrections, but "\c" removes them.
[1] man-pages(7)

47:\fB\-l\fR, \fB\-\-list\fR [\fIsignal\fR]

#

Test nr. 24:

Change a HYPHEN-MINUS (code 0x55, 2D) to a minus (\-), if in front of a
name for an option.

67:.B kill -L

#

Test nr. 28:

Wrong distance between sentences or protect the indicator.

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

Or

2) Adjust space between sentences (two spaces),

3) or protect the indicator by adding "\&" after it.

The "indicator" is an "end-of-sentence character" (.!?).

81:This command meets appropriate standards. The

#

Test nr. 30:

Surround a block of comments with the macros ".ig" and "..".
The .\" (\#) at the beginning of each line is then not needed.
Makes it easier to add and remove text and adjust lenght of lines.

NO PATCH

2:.\" (The preceding line is a note to broken versions of man to tell
3:.\" them to pre-process this man page with tbl)
4:.\" Man page for kill.
5:.\" Licensed under version 2 of the GNU General Public License.
6:.\" Written by Albert Cahalan; converted to a man page by
7:.\" Michael K. Johnson

#

  The patch is in the attachment.


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

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

Versions of packages procps depends on:
ii  init-system-helpers  1.51
ii  libc62.27-2
ii  libncurses5  6.1-1
ii  libncursesw5 6.1-1
ii  libprocps6   2:3.3.12-4
ii  libtinfo56.1-1
ii  lsb-base 9.20170808

Versions of packages procps recommends:
ii  psmisc  23.1-1

procps suggests no packages.

-- Configuration Files:
/etc/init.d/procps changed [not included]

-- no debconf information

-- 
Bjarni I. Gislason
mandoc: kill.1:36:2: ERROR: skipping unknown macro: .TQ
mandoc: kill.1:38:2: ERROR: skipping unknown macro: .TQ
mandoc: kill.1:53:2: WARNING: line scope broken: SH breaks TP
mandoc: kill.1:8:12: WARNING: cannot parse date, using it verbatim: October 2011
mandoc: kill.1:92:2: WARNING: empty block: UR

###

Test nr. 20:

Use a macro to change to the italic font, instead of \fI [1], if
possible.
The macros have the italic corrections, but "\c" removes them.
[1] man-pages(7)

47:\fB\-l\fR, \fB\-\-list\fR [\fIsignal\fR]

#

Test nr. 24:

Change a HYPHEN-MINUS (code 0x55, 2D) to a minus (\-), if in front of a
name for an option.

67:.B kill -L

#

Test nr. 28:

Wrong distance between sentences or protect the indicator.

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

Or

2) Adjust space between sentences (two spaces),

3) or protect the indicator by adding "\&" after it.

The "indicator" is an "end-of-sentence character" (.!?).

81:This command meets appropriate standards. The

#

Test nr. 30:

Surround a block of comments with the macros ".ig" and "..".
The .\" (\#) at the beginning of each line is then not needed.
Makes it easier to add and remove text and adjust lenght of lines.

NO PATCH

2:.\" (The preceding line is a note to broken versions of man to tell
3:.\" them to pre-process this man page with tbl)
4:.\" Man page for kill.
5:.\" Licensed under version 2 of the GNU General Public License.
6:.\" Written by Albert Cahalan; converted to a man page by
7:.\" Michael K. Johnson

#

Bug#886096: lintian: Emit warnings for Alioth URLs in packaging (migration to Salsa)

[Stuart Prescott]

On Sunday, 18 March 2018 17:15:12 AEDT Chris Lamb wrote:
> tags 886096 + patch
> thanks
> 
> Hi Stuart
> 
> > [..]
> 
> Thanks! Can you check the attached draft patch? Note that I hijacked
> te "vcs-deprecated-in-debian-infrastructure" tag instead of adding a
> new one as that had 99% overlap..
> 
> I'd love to get this applied and uploaded today. :)
> 
>   commit ce133079d182f8005e8896da2c9215057304bc89
>   Author: Chris Lamb 
>   Date:   Sun Mar 18 13:11:21 2018 -0400

Looks good to me!

thanks
Stuart

-- 
Stuart Prescotthttp://www.nanonanonano.net/   stu...@nanonanonano.net
Debian Developer   http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7

Bug#893451: linux: Build module for GPD Pocket fan support

[Jeremy Stanley]

Package: linux
Version: 4.16~rc5-1~exp1
Severity: wishlist

Support for the fan controller on GPD pocket systems has merged to
mainline for 4.16, but is not yet configured to be built in the latest
kernel packages.

Bug#893424: Cannot uninstall package

[Andreas Beckmann]

On 2018-03-18 19:43, Ryan Kavanagh wrote:
> Removing sendmail-base (8.15.2-10) ...
> rm: cannot remove '/etc/mail/m4': Is a directory
> dpkg: error processing package sendmail-base (--remove):
>  installed sendmail-base package pre-removal script subprocess returned error 
> exit status 123

> ls -alR /etc/mail:
> /etc/mail:
> total 24
> drwxr-xr-x 1 root root   138 Mar 18 14:32 .
> drwxr-xr-x 1 root root  5364 Mar 18 13:50 ..
> -rw-r--r-- 1 root root   281 Jan 13 17:43 address.resolve
> drwxr-xr-x 1 root root 0 Jan 13 17:43 m4

Interesting. The empty directory shows up with size 0.
What filesystem do you use for / ?

The error should be triggered by this line in the prerm:
# Remove empty files (probably touched databases)
find /etc/mail -maxdepth 1 -size 0 | xargs -r rm;

Please run these two commands:

$ find /etc/mail -maxdepth 1 -size 0
$ find /etc/mail -maxdepth 1 -type f -size 0

The first should output /etc/mail/m4, the second should output nothing.


Andreas

Bug#893324: diffoscope: terminology used in docs about exclusion options

[Chris Lamb]

Dear Paul,

> Yep. I realised I had commit access so I took the liberty of adding it
> to all the other --exclude-* option documentation too. Hope that is OK.

Perfect, thanks! :)


Best wishes,

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

Bug#893393: linux-image-amd64: Kernel panic on active outgoing traffic through Huawei E173 modem in NDIS (CDC) mode

[Bjørn Mork]

Горбешко Богдан  writes:

> vboxdrv(O)
> binder_linux(O)
> ashmem_linux(O)

Can you reproduce the problem without these modules loaded?

AFAICS there is no way the only memset in cdc_ncm can be called with
crashing input parameters. Unless something is scribbling over the
driver's data.


Bjørn

Bug#893324: diffoscope: terminology used in docs about exclusion options

[Paul Wise]

On Sun, 2018-03-18 at 15:47 +0100, Mattia Rizzolo wrote:

> Please check out the latest commit, I added 'ignore' to help grepping
> through the manpage.  Hopefully that's enough to cover your wish :)

Yep. I realised I had commit access so I took the liberty of adding it
to all the other --exclude-* option documentation too. Hope that is OK.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#893450: gitlab: fresh install have no root account, default root password does not work

[Dmitry Smirnov]

Package: gitlab
Version: 9.5.4+dfsg-7
Severity: normal

It is impossible to log in to fresh install of Gitlab using default root
password as per "/usr/share/doc/gitlab/README.md.gz" line 63.

Could it be because root account does not exist?

Although eventually it would be nice to fix the problem in the meantime
this issue should be documented in README.Debian...

Thanks,
  Dmitry Smirnov.

Bug#893444: mandoc.1: Some fixes in the manual

[Ingo Schwarze]

Upstream maintainer talking here.

This utterly unhelpful.

First of all, please don't commit Debian-specific patches fixing
trivial and minor style issues in manual pages to the Debian packaging
systems.  Report them upstream *instead* of bothering downstream,
and they will automatically get fixed after a normal release and
version update.

Second aspect, reporting such minor nits against an utterly outdated
release - the current release is 1.14.3, released more than half a
year ago, and there were three more releases in between - isn't all
that helpful either.

Third aspect, for some of the "issues", it is quite unclear to
me what Bjarni is doing.  Having seen low-quality bug reports
from Bjani before, i doubt that he can explain it better, so please
don't bother.

Bjarni Ingi Gislason wrote on Sun, Mar 18, 2018 at 09:29:37PM +:

> mandoc: mandoc.1:838:4: STYLE: unterminated quoted argument
> mandoc: mandoc.1:852:4: STYLE: unterminated quoted argument
[...]
> mandoc: mandoc.1:2433:4: STYLE: unterminated quoted argument
> mandoc: mandoc.1:2441:4: STYLE: unterminated quoted argument

Cannot reproduce, even though i spent the time of extracting an
old tarball, building from it, and checking the file.  The above
errors simply do not happen.  Neither with the mandoc-1.13.3
release version nor with mandoc-current.

> Test nr. 2:
> Enable and fix warnings from 'test-groff'.
> Input file is /tmp/mandoc.1
> 'R' is a string (producing the registered sign), not a macro.
> chk_manuals: Output is from: test-groff -Tutf8 -b -e -mandoc -rF0 -t -w w -z 

That makes no sense whatsoever.  The file mandoc.1 doesn't even
use the man(7) language, it uses the mdoc(7) language, so there is
certainly no .R macro inside.

> troff: :849: warning: can't find special character 'Lq'
> troff: :849: warning: can't find special character 'Rq'

The file mandoc.1 cotains neither the string "Lq" nor "Rq".

> Test nr. 7:
> Change (or include a "FIXME" paragraph about) misused SI (metric)
> numeric prefixes (or names) to the binary ones, like Ki (kibi), Mi
> (mebi), Gi (gibi), or Ti (tebi), if indicated.
> If the metric prefixes are correct, add the definitions or an explanation
> to avoid misunderstanding.
> 
> 2403:of 2^31 bytes (2 Gigabytes).

That is completely irrelevant.  The full paragraph reads:

   Unsupported features
 *input too large*
 (mdoc, man) Currently, mandoc cannot handle input files larger than its
 arbitrary size limit of 2^31 bytes (2 Gigabytes).  Since useful manuals
 are always small, this is not a problem in practice.  Parsing is aborted
 as soon as the condition is detected.

Obviously, it doesn't matter at all whether these are GB or GiB,
it's just a rough hint for a human reader regarding the order of
magnitude of the limit.  The largest real-world manuals are barely
larger than 1 Megabyte, e.g. perltoc(1).

Nothing to fix here.

> Test nr. 8:
> 
> Protect a full stop (.) with "\&", if it has a blank (white-space) in front
> of or (ignoring transparent characters to the full stop) after it, and it does
> not mean an end of a sentence.
> 
> 1654:The first argument, i.e. the name, is printed, but without subsequent

That is bogus advice.
  The first argument, i.e.\& the name, is printed, ...
would be completely pointless.
That kind of escaping only makes sense when the abbreviation
happens to appear at the end of an input line.

> Test nr. 17:
> Change - to \- if it means a minus sign.
> 715:$ mandoc \-T lint \(gafind /usr/src -name \e*\e.[1-9]\(ga

That is true, and at some point in the future, i'm going to fix
these issues in the OpenBSD tree, including mandoc.
It's a known task, it was discussed at length on ,
where the discussion belongs, and i said that i'm going to do it.
But it can't be done overnight.

A patch fixing one out of 5000 files completely misses the point.
And no, please don't send a patch touching 5000 files either.

> Test nr. 20:
> Use a macro to change to the italic font, instead of \fI [1], if
> possible.
> The macros have the italic corrections, but "\c" removes them.
> [1] man-pages(7)
> 
> 11:[\fB\-I\fR\ \fBos\fR=\fIname\fR]
> 12:[\fB\-K\fR\ \fIencoding\fR]

I have no idea what this is.  A file called man-pages.* doesn't
even exist in the mandoc distribution.  The content has some
similarities with the mandoc(1) manual page, but i haven't the
slightest idea what is going on here.

> Test nr. 24:
> Change a HYPHEN-MINUS (code 0x55, 2D) to a minus (\-), if in front of a
> name for an option.

See test 17 above.

> Test nr. 26:
> Find a repeated word
> ! 123 --> the

That was in a source code comment(!) and was fixed almost two years
ago:

  http://mandoc.bsd.lv/cgi-bin/cvsweb/term.c.diff?r1=1.256&r2=1.257

The file in question has 18 newer commits by now.

> Test nr. 27:
> 
> Split lines longer than 80 characters into two or more
> lines.  Apropriate break points are the end of a sentence or subordinate
> clause.
> 
> mandoc.1: line 995length 95

Obviously a bogu

Bug#893449: override: nanoc:web/optional

[Georg Faerber]

Package: ftp.debian.org

Hi,

As per #884936: Please override the section of nanoc, it should be 'web'
instead of 'ruby'. This change was pushed to git [1], and mentioned in
the upload of 4.1.2-1~exp1 [2].

Thanks,
cheers,
Georg


[1]
https://salsa.debian.org/ruby-team/nanoc/commit/c3c331f61e58b580824674b4523b5589c79a4a10
[2]
https://tracker.debian.org/news/749815/accepted-nanoc-412-1exp1-source-all-into-experimental/


signature.asc
Description: Digital signature

Bug#893326: lintian: check that patch licenses are compatible with licenses of files they modify

[Paul Wise]

On Sun, 2018-03-18 at 18:10 +0200, Adrian Bunk wrote:

> What is supposed to be checked here,

That debian/patches/foo and the upstream files that it touches have
compatible or incompatible licenses.

> and how should that be fixed outside

The person who owns debian/patches/foo should be contacted to relicense
the patch, or the patch should be dropped.

> DEP-5 listing of every patch, and for patches like the example above a 
> detailed explanation which parts of a patch are under which licence?

DEP-5 specifies that there should be license information for every file
in the source package, including all of the debian/patches/ directory.

> IMHO it would be more reasonable to treat debian/patches/
> as special case, defaulting to "same licence as the patched code".

While that would be nice, it isn't always what Debian contributors do. 

The aim of this request is to mitigate serious fallout from that.

I plan to submit additional feature requests for other fallout, the
next one would be patches that mix GPL changes with permissive code.

There could also be a pedantic complaint for the general case of
debian/* using a different license to upstream.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#874870: Version 2.x is qt5-based

[Lisandro Damián Nicanor Pérez Meyer]

Hi! Version 2.x is qt5-based. Please check if you can update this game. Feel 
free to ask for help with Qt5 if needed.


Thanks!

-- 
Theory and practice sometimes clash. And when that happens, theory loses.
Every single time.
  Linus Benedict Torvalds.

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#891060: Atheros AR9271 ath9k_htc USB WiFi connected but IP traffic stops

[Ben Caradoc-Davies]

Patch revised to add debugfs support for the new flag:
https://patchwork.kernel.org/patch/10291439/

Revised patches for master and 4.15.4 attached.

Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand
>From e12b85d240009a96593a239bbdeca40bb38ea24f Mon Sep 17 00:00:00 2001
From: Ben Caradoc-Davies 
Date: Mon, 19 Mar 2018 12:52:53 +1300
Subject: [PATCH] mac80211: add ieee80211_hw flag for QoS NDP support

Commit 7b6ddeaf27ec ("mac80211: use QoS NDP for AP probing") adds an
argument qos_ok to ieee80211_nullfunc_get to support QoS NDP. Despite
the claim in the commit log "Change all the drivers to *not* allow
QoS NDP for now, even though it looks like most of them should be OK
with that", this commit enables QoS NDP in response to beacons (see
change to mlme.c:ieee80211_send_nullfunc), causing ath9k_htc to lose
IP connectivity. See:
https://patchwork.kernel.org/patch/10241109/
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891060

This patch replaces the argument qos_ok of ieee80211_nullfunc_get
with an ieee80211_hw flag that drivers can use to declare support for
QoS NDP, allowing consistent behaviour between mlme.c and drivers.

Signed-off-by: Ben Caradoc-Davies 
---
 drivers/net/wireless/ath/ath9k/channel.c |  2 +-
 drivers/net/wireless/st/cw1200/sta.c |  4 ++--
 drivers/net/wireless/ti/wl1251/main.c|  2 +-
 drivers/net/wireless/ti/wlcore/cmd.c |  5 ++---
 include/net/mac80211.h   | 12 +---
 net/mac80211/debugfs.c   |  1 +
 net/mac80211/mlme.c  |  2 +-
 net/mac80211/tx.c|  5 ++---
 8 files changed, 15 insertions(+), 18 deletions(-)

diff --git a/drivers/net/wireless/ath/ath9k/channel.c b/drivers/net/wireless/ath/ath9k/channel.c
index 1b05b5d7a038..dfb26f03c1a2 100644
--- a/drivers/net/wireless/ath/ath9k/channel.c
+++ b/drivers/net/wireless/ath/ath9k/channel.c
@@ -1113,7 +1113,7 @@ ath_chanctx_send_vif_ps_frame(struct ath_softc *sc, struct ath_vif *avp,
 		if (!avp->assoc)
 			return false;
 
-		skb = ieee80211_nullfunc_get(sc->hw, vif, false);
+		skb = ieee80211_nullfunc_get(sc->hw, vif);
 		if (!skb)
 			return false;
 
diff --git a/drivers/net/wireless/st/cw1200/sta.c b/drivers/net/wireless/st/cw1200/sta.c
index 38678e9a0562..03687a80d6e9 100644
--- a/drivers/net/wireless/st/cw1200/sta.c
+++ b/drivers/net/wireless/st/cw1200/sta.c
@@ -198,7 +198,7 @@ void __cw1200_cqm_bssloss_sm(struct cw1200_common *priv,
 
 		priv->bss_loss_state++;
 
-		skb = ieee80211_nullfunc_get(priv->hw, priv->vif, false);
+		skb = ieee80211_nullfunc_get(priv->hw, priv->vif);
 		WARN_ON(!skb);
 		if (skb)
 			cw1200_tx(priv->hw, NULL, skb);
@@ -2265,7 +2265,7 @@ static int cw1200_upload_null(struct cw1200_common *priv)
 		.rate = 0xFF,
 	};
 
-	frame.skb = ieee80211_nullfunc_get(priv->hw, priv->vif, false);
+	frame.skb = ieee80211_nullfunc_get(priv->hw, priv->vif);
 	if (!frame.skb)
 		return -ENOMEM;
 
diff --git a/drivers/net/wireless/ti/wl1251/main.c b/drivers/net/wireless/ti/wl1251/main.c
index 037defd10b91..99a6889a6540 100644
--- a/drivers/net/wireless/ti/wl1251/main.c
+++ b/drivers/net/wireless/ti/wl1251/main.c
@@ -566,7 +566,7 @@ static int wl1251_build_null_data(struct wl1251 *wl)
 		size = sizeof(struct wl12xx_null_data_template);
 		ptr = NULL;
 	} else {
-		skb = ieee80211_nullfunc_get(wl->hw, wl->vif, false);
+		skb = ieee80211_nullfunc_get(wl->hw, wl->vif);
 		if (!skb)
 			goto out;
 		size = skb->len;
diff --git a/drivers/net/wireless/ti/wlcore/cmd.c b/drivers/net/wireless/ti/wlcore/cmd.c
index 761cf8573a80..2bfc12fdc929 100644
--- a/drivers/net/wireless/ti/wlcore/cmd.c
+++ b/drivers/net/wireless/ti/wlcore/cmd.c
@@ -1069,8 +1069,7 @@ int wl12xx_cmd_build_null_data(struct wl1271 *wl, struct wl12xx_vif *wlvif)
 		ptr = NULL;
 	} else {
 		skb = ieee80211_nullfunc_get(wl->hw,
-	 wl12xx_wlvif_to_vif(wlvif),
-	 false);
+	 wl12xx_wlvif_to_vif(wlvif));
 		if (!skb)
 			goto out;
 		size = skb->len;
@@ -1097,7 +1096,7 @@ int wl12xx_cmd_build_klv_null_data(struct wl1271 *wl,
 	struct sk_buff *skb = NULL;
 	int ret = -ENOMEM;
 
-	skb = ieee80211_nullfunc_get(wl->hw, vif, false);
+	skb = ieee80211_nullfunc_get(wl->hw, vif);
 	if (!skb)
 		goto out;
 
diff --git a/include/net/mac80211.h b/include/net/mac80211.h
index c96511fa9198..985f32c76ba9 100644
--- a/include/net/mac80211.h
+++ b/include/net/mac80211.h
@@ -2063,6 +2063,9 @@ struct ieee80211_txq {
  * @IEEE80211_HW_SUPPORTS_TDLS_BUFFER_STA: Hardware supports buffer STA on
  *	TDLS links.
  *
+ * @IEEE80211_HW_SUPPORTS_QOS_NDP: The driver (or firmware) supports QoS NDP
+ *	for AP probing.
+ *
  * @NUM_IEEE80211_HW_FLAGS: number of hardware flags, used for sizing arrays
  */
 enum ieee80211_hw_flags {
@@ -2106,6 +2109,7 @@ enum ieee80211_hw_flags {
 	IEEE80211_HW_REPORTS_LOW_ACK,
 	IEEE80211_HW_SUPPORTS_TX_FRAG,
 	IEEE80211_HW_SUPPORTS_TDLS_BUFFER_STA,
+	IEEE80211_HW_SUPPORTS_QOS_NDP,
 
 	/* keep 

Bug#893326: lintian: check that patch licenses are compatible with licenses of files they modify

[Paul Wise]

On Sun, 2018-03-18 at 16:33 +, Chris Lamb wrote:

> How would we even know the license of a file under debian/patches? Looking
> DEP-3 [0] it does not have a `License` field.

DEP-5 lists license information for all of debian/ including patches.
DEP-5 lists license information for all files debian/patches/* touch.

> Perhaps you could mock up an offending entry here so we are 100% certain
> we are talking about the same things.

debian/copyright:
Files: foo.c
License: Apache2

Files: debian/*
License: GPLv2

debian/patches/foo:
--- a/foo.c
+++ b/foo.c

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#844939: Yup, fixed.

[Gilles Filippini]

On Sat, 17 Mar 2018 17:00:08 +0100 Gilles Filippini  wrote:
> Hi,
> 
> I've just tried to build your package and it fails the tests:
> # still have 3 known breakage(s)
> # failed 18 among remaining 36 test(s)
> 1..39

Actually, after upgrading against [1] it builds fine.

[1] https://github.com/mnauw/git-remote-hg/issues/11

Thanks,

_g.



signature.asc
Description: OpenPGP digital signature

Bug#873283: Bug

[Lisandro Damián Nicanor Pérez Meyer]

Control: reopen -1

Hi Georges!

Yes, there are apps like discover that would certainly work better if at very 
least the binaries are called falkon.

You *might* want to keep qupzilla as source name, but in the long term it will 
only confuse both users and upstreams alike.

So yes, I'm reopening the bug and asking you to please consider going for the 
full renaming job.

I'm CCing Simon Quigley as he has showed interest in (co)maintaining falko. He 
is a very capable maintainer and currently help us the Qt/KDE team a lot.

Thanks for your work!!!

-- 
Why should I care about my chatter from yesterday?
Nothing prevents me from becoming wiser.
  Konrad Adenauer, former German chancellor.
  http://lwn.net/SubscriberLink/397422/60a270d48f933c67/

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#892848: closed by Matthias Klose (Bug#892848: fixed in gcc-7 7.3.0-12)

[John David Anglin]

On 2018-03-18 11:09 AM, Debian Bug Tracking System wrote:

This is an automatic notification regarding your Bug report
which was filed against the src:gcc-7 package:

#892848: gcc-7: OpenMP support is broken on hppa in gcc-7 and earlier

Oops, caller copies patch wasn't installed in gcc-6.  It's installed now.

--
John David Anglin  dave.ang...@bell.net

Bug#893151: xapers: cannot import PDF filenames with multiple consecutive spaces

[Jameson Graef Rollins]

On Fri, Mar 16 2018, Nathaniel Morck Beaver  wrote:
> Some filenames have multiple consecutive spaces. For example:
>
> 'this  filename   ismultiply spaced.pdf'
>
> Pybtex, like BibTeX, removes multiple consecutive spaces:
>
> 'this filename is multiply spaced.pdf'
>
> This means that xapers cannot import a BibTeX file containing paths with 
> multiple consecutive spaces.

Hi, Nathaniel.  Thanks for the bug report and sorry for the trouble.

> If the file is imported using "xapers add" instead of "xapers import", 
> the bibtex file in the subdirectory of ~/.xapers/docs/ will contain the 
> wrong path, since the consecutive spaces have been removed.

This is obviously a bug.

I'll investigate better file name encoding (although multiple spaces in
file names is quite perverse and pathological!).

jamie.


signature.asc
Description: PGP signature

Bug#893054: systemd: System failed to boot after upgrade/install systemd from systemd:i386

[Michael Biebl]

Am 15.03.2018 um 23:31 schrieb Jeff Ketchum:
> I upgraded systemd, and after a failure to boot, realized it was on
> systemd:i386.
> I went into a recovery environment and removed systemd:i386 and
> installed systemd.
> After that It failed to boot at a different location.
> I was able to get it to boot by removing the kernel parameter
> for the nouveau driver to use the binary firmware.

Just to be clear: What is this bug report about?
About the first issue, where systemd:i386 was installed on a amd64
system (and you probably ran into #869719)
or the second issue? The log you posted, is that with systemd:amd64 or
systemd:i386?
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#893448: please add a chromium-source binary package

[Steinar H. Gunderson]

Source: chromium-browser
Version: 65.0.3325.146-4
Severity: wishlist
Tags: patch

Hi,

As mentioned on pkg-chromium-browser@, it would be useful if chromium-browser
shipped a chromium-browser source package; it would allow packaging and building
CEF (Chromium Embedded Framework) against Debian's (patched) sources instead of
off some random git checkout. I've added a patch.

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

Kernel: Linux 4.16.0-rc1 (SMP w/40 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NO:en_US:en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru chromium-browser-65.0.3325.146/debian/changelog 
chromium-browser-65.0.3325.146/debian/changelog
--- chromium-browser-65.0.3325.146/debian/changelog 2018-03-05 
02:26:31.0 +0100
+++ chromium-browser-65.0.3325.146/debian/changelog 2018-03-11 
00:43:35.0 +0100
@@ -1,3 +1,10 @@
+chromium-browser (65.0.3325.146-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add a chromium-source binary package. 
+
+ -- Steinar H. Gunderson   Sun, 11 Mar 2018 00:43:35 +0100
+
 chromium-browser (65.0.3325.146-1) unstable; urgency=medium
 
   * New upstream stable release release.
diff -Nru chromium-browser-65.0.3325.146/debian/chromium-source.install 
chromium-browser-65.0.3325.146/debian/chromium-source.install
--- chromium-browser-65.0.3325.146/debian/chromium-source.install   
1970-01-01 01:00:00.0 +0100
+++ chromium-browser-65.0.3325.146/debian/chromium-source.install   
2018-03-09 22:47:59.0 +0100
@@ -0,0 +1,3 @@
+out/chromium-src.tar.xz /usr/src/chromium
+out/chromium-src.flags /usr/src/chromium
+
diff -Nru chromium-browser-65.0.3325.146/debian/control 
chromium-browser-65.0.3325.146/debian/control
--- chromium-browser-65.0.3325.146/debian/control   2018-03-05 
02:26:31.0 +0100
+++ chromium-browser-65.0.3325.146/debian/control   2018-03-09 
22:46:54.0 +0100
@@ -189,3 +189,12 @@
  .
  This package contains resources that are in common to different chromium
  packages.
+
+Package: chromium-source
+Architecture: all
+Recommends: xz-utils
+Description: web browser - source code
+ Web browser that aims to build a safer, faster, and more stable internet
+ browsing experience.
+ .
+ This package contains the patched source code used to build the packages.
diff -Nru chromium-browser-65.0.3325.146/debian/rules 
chromium-browser-65.0.3325.146/debian/rules
--- chromium-browser-65.0.3325.146/debian/rules 2018-03-05 02:26:31.0 
+0100
+++ chromium-browser-65.0.3325.146/debian/rules 2018-03-10 14:58:29.0 
+0100
@@ -113,6 +113,14 @@
./out/Release/gn gen out/Release --args="$(defines)"
ninja $(njobs) -C out/Release packed_resources
rm -f out/Release/locales/en-US.pak
+   echo "$(defines)" | sed 's/host_cpu=[^ ]*//' > 
$(CURDIR)/out/chromium-src.flags
+   find . '(' -path ./debian -or -path ./out ')' -prune -or -print0 | \
+   LC_ALL=C sort -z | \
+   tar -c -vv -J --null --no-recursion --transform 
's,^\./,chromium/,' -T - \
+   --mode=go=rX,u+rw,a-s \
+   --clamp-mtime --mtime "@$(SOURCE_DATE_EPOCH)" \
+   --owner=root --group=root --numeric-owner \
+   -f $(CURDIR)/out/chromium-src.tar.xz
 
 override_dh_auto_install-arch:
dh_auto_install

Bug#893143: Pending fixes for bugs in the easyconf package

[pkg-java-maintainers]

tag 893143 + pending
thanks

Some bugs in the easyconf package are closed in revision
4010904deb4748d81df544a9a4a8950ee5899861 in branch 'master' by
Emmanuel Bourg

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

Commit message:

Fixed the build failure with Java 9 (Closes: #893143)

Bug#893447: nanoc: autopkgtest fails with local firewall

[Steve Langasek]

Package: nanoc
Version: 4.8.10-1
Severity: minor
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic ubuntu-patch autopkgtest

Dear Cédric,

In Ubuntu, the nanoc autopkgtests have been failing, which is a blocker for
inclusion of the new version in the upcoming Ubuntu release:

  1) Nanoc::CLI::Commands::View#run does not listen on non-local interfaces
 Failure/Error: expect { Net::HTTP.get(non_local_addresses[0], '/', 50_385) 
}.to raise_error(Errno::ECONNREFUSED)

   expected Errno::ECONNREFUSED, got # w
ith backtrace:
 # ./spec/nanoc/cli/commands/view_spec.rb:71:in `block (5 levels) in '
 # ./spec/nanoc/cli/commands/view_spec.rb:71:in `block (4 levels) in '
 # ./spec/nanoc/cli/commands/view_spec.rb:21:in `run_nanoc_cmd'
 # ./spec/nanoc/cli/commands/view_spec.rb:70:in `block (3 levels) in '
 # ./spec/spec_helper.rb:52:in `block (2 levels) in '
 # ./spec/spec_helper.rb:30:in `block (4 levels) in '
 # ./spec/spec_helper.rb:30:in `block (3 levels) in '
 # ./spec/spec_helper.rb:29:in `block (2 levels) in '
 # ./spec/spec_helper.rb:24:in `block (2 levels) in '
 # ./spec/nanoc/cli/commands/view_spec.rb:71:in `block (4 levels) in '
 # ./spec/nanoc/cli/commands/view_spec.rb:21:in `run_nanoc_cmd'
 # ./spec/nanoc/cli/commands/view_spec.rb:70:in `block (3 levels) in '
 # ./spec/spec_helper.rb:52:in `block (2 levels) in '
 # ./spec/spec_helper.rb:30:in `block (4 levels) in '
 # ./spec/spec_helper.rb:30:in `block (3 levels) in '
 # ./spec/spec_helper.rb:29:in `block (2 levels) in '
 # ./spec/spec_helper.rb:24:in `block (2 levels) in '

Progress: ||

Finished in 2 minutes 26.6 seconds (files took 1.86 seconds to load)
2228 examples, 1 failure

  http://autopkgtest.ubuntu.com/packages/n/nanoc/bionic/amd64

This test assumes that an attempt to connect to the port will fail with
ECONNREFUSED, but on a system with a firewall it may instead fail with a
timeout.  So even though the test passes fine in Debian, I think the test is
buggy.

I have uploaded the attached patch to Ubuntu to fix this test failure. 
Please consider applying a change like this in Debian as well.

(Of course, even with the test fixed, nanoc will be blocked from inclusion
in the next release until Debian bug #892195 is also fixed, solving the
build failure against ruby2.5.)

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru nanoc-4.8.10/debian/patches/series nanoc-4.8.10/debian/patches/series
--- nanoc-4.8.10/debian/patches/series  2017-10-17 12:49:22.0 -0700
+++ nanoc-4.8.10/debian/patches/series  2018-03-18 15:43:14.0 -0700
@@ -7,3 +7,4 @@
 encoding.patch
 skip_tests_autopkgtest.patch
 no_simplecov.patch
+skip-network-test.patch
diff -Nru nanoc-4.8.10/debian/patches/skip-network-test.patch 
nanoc-4.8.10/debian/patches/skip-network-test.patch
--- nanoc-4.8.10/debian/patches/skip-network-test.patch 1969-12-31 
16:00:00.0 -0800
+++ nanoc-4.8.10/debian/patches/skip-network-test.patch 2018-03-18 
15:46:49.0 -0700
@@ -0,0 +1,31 @@
+Description: skip test that tries to connect to server on non-loopback address
+ nanoc tests check to make sure nanoc is not listening on non-loopback
+ addresses by trying to connect to the port and expecting connection refused.
+ However, local configuration can cause a different failure to be returned,
+ such as a timeout due to a DROP rule in a firewall.  Skip this test, which
+ is exceedingly unlikely to ever regress in the distro.
+Author: Steve Langasek 
+Last-Updated: 2018-03-18
+
+Index: nanoc-4.8.10/spec/nanoc/cli/commands/view_spec.rb
+===
+--- nanoc-4.8.10.orig/spec/nanoc/cli/commands/view_spec.rb
 nanoc-4.8.10/spec/nanoc/cli/commands/view_spec.rb
+@@ -59,17 +59,5 @@
+   end
+ end
+ 
+-it 'does not listen on non-local interfaces' do
+-  addresses = 
Socket.getifaddrs.map(&:addr).select(&:ipv4?).map(&:ip_address)
+-  non_local_addresses = addresses - ['127.0.0.1']
+-
+-  if non_local_addresses.empty?
+-skip 'Need non-local network interfaces for this spec'
+-  end
+-
+-  run_nanoc_cmd(['view', '--port', '50385']) do
+-expect { Net::HTTP.get(non_local_addresses[0], '/', 50_385) }.to 
raise_error(Errno::ECONNREFUSED)
+-  end
+-end
+   end
+ end

Bug#883541: git-buildpackage: gbp pq export should default to content-transfer-encoding: 8bit

[Michael Biebl]

On Wed, 20 Dec 2017 13:22:34 +0100 Guido =?iso-8859-1?Q?G=FCnther?=
 wrote:
> control: tags -1 -patch
> 
> Hi Carlos,
> thanks for having a look!
> 
> On Wed, Dec 20, 2017 at 09:56:20PM +1100, Carlos Maddela wrote:
> > diff --git a/gbp/scripts/common/pq.py b/gbp/scripts/common/pq.py
> > index 004c231..d092565 100644
> > --- a/gbp/scripts/common/pq.py
> > +++ b/gbp/scripts/common/pq.py
> > @@ -177,7 +177,7 @@ def write_patch_file(filename, commit_info, diff):
> >  msg.set_payload(body.encode('us-ascii'))
> >  except (UnicodeEncodeError):
> >  msg.set_payload(body, charset)
> > -patch.write(msg.as_string(unixfrom=False, 
> > maxheaderlen=77).encode('utf-8'))
> > +patch.write(msg.as_bytes(unixfrom=False))
> 
> Good catch but we need to keep breaking headers at that value to not
> introduce further diff noise. Looking at the docs max_line_length is
> there as well which could work.

I've just been bitten by this as well, so I was wondering what the
current state of this bug report is.

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



signature.asc
Description: OpenPGP digital signature

Bug#893446: xserver-xorg-video-intel: Video playback with tearing artefacts due to video sync

[Marco]

Package: xserver-xorg-video-intel
Version: 2:2.99.917+git20171229-1
Severity: important

Dear Maintainer,

   * What led up to the situation?
Playing video, either on MPlayer or VLC. You get parts of the video 
that are not synced with the rest. Here there is a picture: 
https://i.imgur.com/ctsXLLT.jpg
You can see that pattern which happens on different parts of the video, 
when there's a lot of movement.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Tried many different things. I was able to verify that this problem is 
not present on a live CD of Linux Mint Debian Edition. Then I tried a live CD 
version of Debian: debian-live-9.3.0-amd64-xfce. The problem was present on 
Debian live CD, but not on LMDE.

These errors listed in Xorg's log is present on my Debian installation. They 
were not present in LMDE

cat /var/log/Xorg.0.log | grep EE
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[51.808] (EE) intel(0): failed to set mode: Input/output error [5]
[54.608] (EE) synaptics: ETPS/2 Elantech Touchpad: Synaptics driver unable 
to detect protocol
[54.608] (EE) PreInit returned 11 for "ETPS/2 Elantech Touchpad"
[54.623] (EE) intel(0): Detected a hung GPU, disabling acceleration.
[  8753.929] (EE) 
[  8753.929] (EE) xf86CloseConsole: VT_ACTIVATE failed: Input/output error
[  8753.929] (EE) 
[  8753.929] (EE) 
[  8753.929] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
[  8753.929] (EE) 
[  8753.929] (EE) 
[  8753.929] (EE) xf86CloseConsole: VT_ACTIVATE failed: Input/output error
[  8753.929] (EE) 
 


-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Mar 19  2011 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 274 Jan 18 09:11 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor 
Integrated Graphics Controller [8086:0046] (rev 02)

Xorg X server configuration file status:

-rw-r--r-- 1 root root 805 Mar 23  2011 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
---
Section "InputDevice"
Identifier  "Touchpad"
Driver  "synaptics"
Option  "Protocol"  "auto-dev"
Option  "MinSpeed"  "0.5"
Option  "MaxSpeed"  "1.0"
Option  "AccelFactor"   "0.075"
Option  "VertTwoFingerScroll"   "1"
Option  "HorizTwoFingerScroll"  "1"
Option  "TapButton1""1"
Option  "TapButton2""2"
Option  "TapButton3""3"
Option  "LockedDrags"   "1"
Option  "VertEdgeScroll""1"
Option  "HorizEdgeScroll"   "1"
EndSection


Section "ServerLayout"
Identifier  "Default Layout"
#Screen  "Default Screen"
#InputDevice "Generic Keyboard"
InputDevice "Touchpad"
EndSection

/etc/X11/xorg.conf.d does not exist.

KMS configuration files:

/etc/modprobe.d/i915-kms.conf:
  #options i915 modeset=0

Kernel version (/proc/version):
---
Linux version 4.14.0-3-amd64 (debian-ker...@lists.debian.org) (gcc version 
7.2.0 (Debian 7.2.0-19)) #1 SMP Debian 4.14.13-1 (2018-01-14)

Xorg X server log files on system:
--
-rw-r--r-- 1 root  root  30567 Oct 13  2015 /var/log/Xorg.0.log
-rw-r--r-- 1 the98 the98  5845 Jan 14 19:27 
/home/the98/.local/share/xorg/Xorg.1.log
-rw-r--r-- 1 the98 the98 46028 Mar 18 17:48 
/home/the98/.local/share/xorg/Xorg.0.log

Contents of most recent Xorg X server log file 
(/home/the98/.local/share/xorg/Xorg.0.log):
--
[89.750] 
X.Org X Server 1.19.6
Release Date: 2017-12-20
[89.750] X Protocol Version 11, Revision 0
[89.750] Build Operating System: Linux 4.9.0-5-amd64 x86_64 Debian
[89.750] Current Operating System: Linux g560 4.14.0-3-amd64 #1 SMP Debian 
4.14.13-1 (2018-01-14) x86_64
[89.750] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.14.0-3-amd64 
root=UUID=095e0d3b-db34-4564-bcd1-0768f602acae ro quiet
[89.750] Build Date: 26 January 2018  04:30:21PM
[89.750] xorg-server 2:1.19.6-1 (https://www.debian.org/support) 
[89.750] Current version of pixman: 0.34.0
[89.750]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[89.750] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[89.751] (==) 

Bug#893426: Processed: Re: Processed: Re: Bug#893426: systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN

[Michael Biebl]

Control: tags -1 fixed-upstream patch
Control: forwarded -1 https://github.com/systemd/systemd/pull/8456

Fixed upstream by
https://github.com/systemd/systemd/commit/848e863acc51ecfb0f3955c498874588201d9130



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



signature.asc
Description: OpenPGP digital signature

Bug#893369: systemd-udevd is killed at startup

[Michael Biebl]

Am 18.03.2018 um 22:41 schrieb LEDUQUE Mickaël:
> No I don't think I have one
> dpkg -l udev only shows udev and64

what about systemd? i386 or amd64


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



signature.asc
Description: OpenPGP digital signature

Bug#893156: Request to reset src:mariadb-10.1 to previous known working state in Debian testing/unstable archives

[Chris Lamb]

tags 893156 + moreinfo
thanks

Hi Otto,

> [..]

Please elaborate why you can't revert all the changes to 10.1.28-2 and
then upload that as 1:10.1.29+really10.1.28-1 until you are ready to
upload 10.1.29 again? Failing that, you will also need to really justify
why you cannot bump the epoch again.

Manually modifying dak's records to fix his is, err, unlikely to happen.


Regards,

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

Bug#789802: lintian: False positive source-contains-prebuilt-java-object reported against jar files without classes

[Chris Lamb]

tags 789802 + pending
thanks

Thanks Emmanuel. Fixed in Git, pending upload:

  
https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=f0e60714b87403db6478fae7f8e3671430fa393f


Regards,

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

Bug#893105: Pending fixes for bugs in the clirr package

[pkg-java-maintainers]

tag 893105 + pending
thanks

Some bugs in the clirr package are closed in revision
0cf56abff475d627ca5da729a8c0c32e87afbf5d in branch 'master' by
Emmanuel Bourg

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

Commit message:

Build with maven-debian-helper instead of maven-ant-helper (Closes: #893105)

Bug#892080: bash-completion: cvs log ($mode=log) case disappeared?

[Gabriel F. T. Gomes]

On 05 Mar 2018, Tim Connors wrote:

>I'm sure 'cvs log ' use to tab-complete , but it's
>clear why it doesn't:
>
>log|lo|rlog|rl)
>mode=log
>;;
>
>But then no corresponding case for $mode=log.

Thanks for pointing this out.  I sent a patch for upstream review at:
https://github.com/scop/bash-completion/pull/194.

Bug#893369: systemd-udevd is killed at startup

[LEDUQUE Mickaël]

No I don't think I have one
dpkg -l udev only shows udev and64

2018-03-18 22:39 GMT+01:00 Michael Biebl :

> Am 18.03.2018 um 22:33 schrieb LEDUQUE Mickaël:
> > Looks like commenting out
> >
> > SystemCallArchitectures=native
> >
> > fixes  the issue.
>
> Does that mean you have a udev:i386 installed on a amd64 system?
>
>
>
> If so, that would basically be a duplicate of #869719
>
>
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
>
>

Bug#893445: RM: libxfont1 -- ROM; obsolete library with no reverse dependencies

[Julien Cristau]

Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: libxfo...@packages.debian.org

as of xfonts-utils 1:7.7+6 there are no reverse dependencies for
libxfont1 left (ignoring kbsd).  It's time to remove it.

Cheers,
Julien

Bug#838372: stterm: New upstream version

[Paride Legovini]

FYI: st-0.8 has been released.

This package requires some love.

Paride

Bug#893369: systemd-udevd is killed at startup

[Michael Biebl]

Am 18.03.2018 um 22:33 schrieb LEDUQUE Mickaël:
> Looks like commenting out
> 
> SystemCallArchitectures=native
> 
> fixes  the issue.

Does that mean you have a udev:i386 installed on a amd64 system?



If so, that would basically be a duplicate of #869719


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



signature.asc
Description: OpenPGP digital signature

Bug#893426: Processed: Re: Bug#893426: systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN

[Michael Biebl]

Control: reassign -1 systemd
Control: found -1 238-1

It was correctly pointed out by Andreas Henriksson, that redefining
noreturn is probably not such a good idea, so let's reassign this back. 

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



signature.asc
Description: OpenPGP digital signature

Bug#893369: systemd-udevd is killed at startup

[LEDUQUE Mickaël]

Looks like commenting out

SystemCallArchitectures=native

fixes  the issue.

2018-03-18 22:27 GMT+01:00 LEDUQUE Mickaël :

> I disabled them all and got a normal startup.
> Now I'll try to find the one (or more) that causes the problem.
> Thanks.
>
> 2018-03-18 21:48 GMT+01:00 Michael Biebl :
>
>> Am 18.03.2018 um 20:38 schrieb Mickaël Leduque:
>> > Package: systemd
>> > Version: 238-2
>> > Followup-For: Bug #893369
>> >
>> > It didn't work so I just added the options in /etc/default/grub.
>> > Here are the journal and the systemctl list-jobs output (which is just
>> "no jobs").
>> >
>>
>> Ok, thanks.
>> Once you are dropped into the rescue shell, can you try running
>> systemd-udevd manually, via
>> /lib/systemd/systemd-udevd
>>
>> If that works, you can try disabling the security features in
>> /lib/systemd/system/systemd-udevd.service
>> by commenting out the lines
>>
>> MemoryDenyWriteExecute=yes
>> RestrictRealtime=yes
>> RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6
>> SystemCallArchitectures=native
>> LockPersonality=yes
>>
>> one by one and test if that makes a difference.
>>
>>
>> --
>> Why is it that all of the instruments seeking intelligent life in the
>> universe are pointed away from Earth?
>>
>>
>

Bug#893444: mandoc.1: Some fixes in the manual

[Bjarni Ingi Gislason]

Package: mandoc
Version: 1.14.3-3
Severity: minor
Tags: patch

Dear Maintainers (also sent to "schwa...@openbsd.org"),

  A patch is in the attachment.

  NO PATCH

mandoc: mandoc.1:838:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:852:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:863:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:871:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:879:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:889:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:900:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:915:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:924:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:931:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:938:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:948:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:959:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:971:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:980:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:991:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1002:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1010:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1019:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1028:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1038:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1045:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1055:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1064:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1071:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1080:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1087:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1105:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1114:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1124:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1129:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1138:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1148:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1154:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1160:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1171:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1183:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1192:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1199:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1206:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1214:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1221:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1229:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1239:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1246:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1251:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1257:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1277:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1287:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1297:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1306:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1313:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1322:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1369:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1377:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1387:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1407:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1422:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1432:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1440:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1448:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1456:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1490:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1495:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1510:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1521:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1528:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1540:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1551:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1560:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1568:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1584:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1599:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1612:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1620:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1628:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1638:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1648:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1657:4: STYLE: unterminated quoted argument
mandoc: mandoc.1:1673:4: STYLE:

Bug#893369: systemd-udevd is killed at startup

[LEDUQUE Mickaël]

I disabled them all and got a normal startup.
Now I'll try to find the one (or more) that causes the problem.
Thanks.

2018-03-18 21:48 GMT+01:00 Michael Biebl :

> Am 18.03.2018 um 20:38 schrieb Mickaël Leduque:
> > Package: systemd
> > Version: 238-2
> > Followup-For: Bug #893369
> >
> > It didn't work so I just added the options in /etc/default/grub.
> > Here are the journal and the systemctl list-jobs output (which is just
> "no jobs").
> >
>
> Ok, thanks.
> Once you are dropped into the rescue shell, can you try running
> systemd-udevd manually, via
> /lib/systemd/systemd-udevd
>
> If that works, you can try disabling the security features in
> /lib/systemd/system/systemd-udevd.service
> by commenting out the lines
>
> MemoryDenyWriteExecute=yes
> RestrictRealtime=yes
> RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6
> SystemCallArchitectures=native
> LockPersonality=yes
>
> one by one and test if that makes a difference.
>
>
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
>
>

Bug#893443: diffoscope: please make it easier to see supported file formats

[Chris Lamb]

tags 893443 + pending
thanks

Fixed in Git, pending upload:

  
https://anonscm.debian.org/git/reproducible/diffoscope.git/commit/?id=1375ec5bc1f653c4588ac503f45a8c2fcb87ab58


Regards,

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

Bug#893426: systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN

[Michael Biebl]

Control: reassign -1 libgpg-error-dev
Control: found -1 1.28-1
Control: affects -1 + systemd

Am 18.03.2018 um 19:54 schrieb Helmut Grohne:
> Package: systemd
> Version: 238-2
> Severity: serious
> User: helm...@debian.org
> Usertags: rebootstrap
> 
> systemd fails to build from source on amd64. Here is a tail of the build
> log.
> 
> | FAILED: journal-core@sta/src_journal_journald-context.c.o 
> | cc  -Ijournal-core@sta -I. -I.. -I../ -Isrc/libsystemd-network 
> -I../src/libsystemd-network -I../src/libsystemd/sd-network 
> -I../src/libsystemd/sd-netlink -I../src/libsystemd/sd-id128 
> -I../src/libsystemd/sd-hwdb -I../src/libsystemd/sd-device 
> -I../src/libsystemd/sd-bus -Isrc/core -I../src/core -Isrc/libudev 
> -I../src/libudev -Isrc/udev -I../src/udev -Isrc/login -I../src/login 
> -Isrc/timesync -I../src/timesync -Isrc/resolve -I../src/resolve -Isrc/journal 
> -I../src/journal -Isrc/systemd -I../src/systemd -Isrc/shared -I../src/shared 
> -Isrc/basic -I../src/basic -flto -fdiagnostics-color=always -pipe 
> -D_FILE_OFFSET_BITS=64 -std=gnu99 -Wextra -Werror=undef -Wlogical-op 
> -Wmissing-include-dirs -Wold-style-definition -Wpointer-arith -Winit-self 
> -Wdeclaration-after-statement -Wfloat-equal -Wsuggest-attribute=noreturn 
> -Werror=missing-prototypes -Werror=implicit-function-declaration 
> -Werror=missing-declarations -Werror=return-type 
> -Werror=incompatible-pointer-types -Werror=format=2 -Wstrict-prototypes 
> -Wredundant-decls -Wmissing-noreturn -Wimplicit-fallthrough=5 -Wshadow 
> -Wendif-labels -Wstrict-aliasing=2 -Wwrite-strings -Werror=overflow 
> -Wdate-time -Wnested-externs -ffast-math -fno-common 
> -fdiagnostics-show-option -fno-strict-aliasing -fvisibility=hidden 
> -fstack-protector -fstack-protector-strong --param=ssp-buffer-size=4 -fPIE 
> -Wno-unused-parameter -Wno-missing-field-initializers -Wno-unused-result 
> -Wno-format-signedness -Wno-error=nonnull -Werror=shadow -ffunction-sections 
> -fdata-sections -include config.h -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -MD -MQ 
> 'journal-core@sta/src_journal_journald-context.c.o' -MF 
> 'journal-core@sta/src_journal_journald-context.c.o.d' -o 
> 'journal-core@sta/src_journal_journald-context.c.o' -c 
> ../src/journal/journald-context.c
> | In file included from ../src/basic/alloc-util.h:28:0,
> |  from ../src/journal/journald-context.c:25:
> | ../src/basic/macro.h:423:18: error: expected ‘)’ before ‘__attribute__’
> |  #define noreturn __attribute__((noreturn))
> |   ^
> | In file included from /usr/include/gcrypt.h:30:0,
> |  from ../src/journal/journal-file.h:26,
> |  from ../src/journal/journald-server.h:31,
> |  from ../src/journal/journald-context.h:30,
> |  from ../src/journal/journald-context.c:33:
> | /usr/include/x86_64-linux-gnu/gpg-error.h:1545:46: error: expected ‘,’ or 
> ‘;’ before ‘)’ token
> |  void gpgrt_log_bug (const char *fmt, ...)GPGRT_ATTR_NR_PRINTF(1,2);
> |   ^
> | In file included from ../src/basic/alloc-util.h:28:0,
> |  from ../src/journal/journald-context.c:25:
> | ../src/basic/macro.h:423:18: error: expected ‘)’ before ‘__attribute__’
> |  #define noreturn __attribute__((noreturn))
> |   ^
> | In file included from /usr/include/gcrypt.h:30:0,
> |  from ../src/journal/journal-file.h:26,
> |  from ../src/journal/journald-server.h:31,
> |  from ../src/journal/journald-context.h:30,
> |  from ../src/journal/journald-context.c:33:
> | /usr/include/x86_64-linux-gnu/gpg-error.h:1546:46: error: expected ‘,’ or 
> ‘;’ before ‘)’ token
> |  void gpgrt_log_fatal (const char *fmt, ...)  GPGRT_ATTR_NR_PRINTF(1,2);
> |   ^
> | In file included from ../src/basic/alloc-util.h:28:0,
> |  from ../src/journal/journald-context.c:25:
> | ../src/basic/macro.h:423:18: error: expected ‘)’ before ‘__attribute__’
> |  #define noreturn __attribute__((noreturn))
> |   ^
> | In file included from /usr/include/gcrypt.h:30:0,
> |  from ../src/journal/journal-file.h:26,
> |  from ../src/journal/journald-server.h:31,
> |  from ../src/journal/journald-context.h:30,
> |  from ../src/journal/journald-context.c:33:
> | /usr/include/x86_64-linux-gnu/gpg-error.h:1558:43: error: expected ‘,’ or 
> ‘;’ before ‘)’ token
> |  const char *func) GPGRT_ATTR_NORETURN;
> |^
> | [231/1523] /usr/bin/python3 /usr/bin/meson --internal exe 
> /<>/build-deb/meson-private/meson_exe_awk_ec289b1578d245bbf1d8589a5ea437fc6525ccd3.dat
> | ninja: build stopped: subcommand failed.
> | dh_auto_build: cd build-deb && LC_ALL=C.UTF-8 ninja 

Bug#893122: Pending fixes for bugs in the cronometer package

[pkg-java-maintainers]

tag 893122 + pending
thanks

Some bugs in the cronometer package are closed in revision
db2620d0ca8afa07f8d1c68f5ef01f28f4ad57c2 in branch 'master' by
Emmanuel Bourg

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

Commit message:

Fixed the build failure with Java 9 (Closes: #893122)

Bug#868314: not the same problem

[Cédric Boutillier]

Hi Federico,

Thank you for your additional comment on this bug.

I don't think it is the same problem as in the original report. The
error you see in irb comes from the fact that you run your session in a
directory which doesn't contain a Gemfile to describe the dependencies
of your project. In particular it is not the same error as the one in
the initial bug report, where I suppose that a Gemfile was present with
dependencies not corresponding to installed packages/gems.

If you want to start jekyll, invoking bundler is not needed. You should
be able to start a new site by just typing:

$ jekyll new foo

in the terminal. Can you confirm that you can start a new site, or can
you be more specific in what you were expecting from the Bundler.setup
command?

Best wishes,

Cédric


signature.asc
Description: PGP signature

Bug#893369: systemd-udevd is killed at startup

[Michael Biebl]

Am 18.03.2018 um 20:38 schrieb Mickaël Leduque:
> Package: systemd
> Version: 238-2
> Followup-For: Bug #893369
> 
> It didn't work so I just added the options in /etc/default/grub.
> Here are the journal and the systemctl list-jobs output (which is just "no 
> jobs").
> 

Ok, thanks.
Once you are dropped into the rescue shell, can you try running
systemd-udevd manually, via
/lib/systemd/systemd-udevd

If that works, you can try disabling the security features in
/lib/systemd/system/systemd-udevd.service
by commenting out the lines

MemoryDenyWriteExecute=yes
RestrictRealtime=yes
RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6
SystemCallArchitectures=native
LockPersonality=yes

one by one and test if that makes a difference.


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



signature.asc
Description: OpenPGP digital signature

Bug#789802: lintian: False positive source-contains-prebuilt-java-object reported against jar files without classes

[Emmanuel Bourg]

Control: tag -1 - moreinfo

On 24/12/2017 21:33, Chris Lamb wrote:

> Do you have any up-to-date false-positives? The ones you listed
> are now not showing up for me :)

cronometer is another example. Lintian reports two jar files that only
contain xml files and no compiled Java files:

P: cronometer source: source-contains-prebuilt-java-object lib/crdb_005.jar
P: cronometer source: source-contains-prebuilt-java-object lib/usda_sr24.jar

Bug#893360: python3-tornado 5.0.0 breaks python3-zmq

[Rebecca N. Palmer]

This is because tornado 5.0 deliberately removed 
ioloop.IOLoop.initialized() because "It is no longer possible to provide 
this method with reasonable semantics": 
https://github.com/tornadoweb/tornado/commit/426b3812b9dd21ae0bac19d4146c6952816c7bfe#diff-1d4144f0ef561b7c18c7fe438816e1f5


This bug probably doesn't affect pyzmq 17 (since
https://github.com/zeromq/pyzmq/commit/f24a264094c6aae2587279c052fcbe242dd9d157#diff-079289d3903c2adcc75b3beb3458a2cf 
), but I don't know whether upgrading Debian's pyzmq to that would break 
anything else.


Another option is to remove this assert() (zmq/eventloop/ioloop.py:210) 
or move it inside a tornado_version check.


It is likely that both Python 2 and 3 are affected, but I have not tried 
to verify this.  At least Jupyter/ipykernel (via 
python3-jupyter-client), sagemath, circus and salt-{master,minion} 
Depend: on both python(3)-tornado and python(3)-zmq, but I have only 
tested the first.


Stack trace (this input file is 
https://salsa.debian.org/science-team/theano/blob/master/doc/library/d3viz/index.ipynb 
, but any .ipynb file would probably do):


# apt-get install jupyter-nbconvert python3-ipykernel
$ jupyter-nbconvert --to notebook --execute --allow-errors index.ipynb
[NbConvertApp] Converting notebook index.ipynb to notebook
[NbConvertApp] Executing notebook with kernel: python3
Traceback (most recent call last):
  File "/usr/lib/python3.6/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
  File "/usr/lib/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
  File "/usr/lib/python3/dist-packages/ipykernel_launcher.py", line 16, 
in 

app.launch_new_instance()
  File 
"/usr/lib/python3/dist-packages/traitlets/config/application.py", line 
657, in launch_instance

app.initialize(argv)
  File "", line 2, in initialize
  File 
"/usr/lib/python3/dist-packages/traitlets/config/application.py", line 
87, in catch_config_error

return method(app, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/ipykernel/kernelapp.py", line 
452, in initialize

zmq_ioloop.install()
  File "/usr/lib/python3/dist-packages/zmq/eventloop/ioloop.py", line 
210, in install

assert (not ioloop.IOLoop.initialized()) or \
AttributeError: type object 'IOLoop' has no attribute 'initialized'
Traceback (most recent call last):
  File "/usr/bin/jupyter-nbconvert", line 11, in 
load_entry_point('nbconvert==5.3.1', 'console_scripts', 
'jupyter-nbconvert')()
  File "/usr/lib/python3/dist-packages/jupyter_core/application.py", 
line 266, in launch_instance

return super(JupyterApp, cls).launch_instance(argv=argv, **kwargs)
  File 
"/usr/lib/python3/dist-packages/traitlets/config/application.py", line 
658, in launch_instance

app.start()
  File "/usr/lib/python3/dist-packages/nbconvert/nbconvertapp.py", line 
325, in start

self.convert_notebooks()
  File "/usr/lib/python3/dist-packages/nbconvert/nbconvertapp.py", line 
493, in convert_notebooks

self.convert_single_notebook(notebook_filename)
  File "/usr/lib/python3/dist-packages/nbconvert/nbconvertapp.py", line 
464, in convert_single_notebook
output, resources = self.export_single_notebook(notebook_filename, 
resources, input_buffer=input_buffer)
  File "/usr/lib/python3/dist-packages/nbconvert/nbconvertapp.py", line 
393, in export_single_notebook
output, resources = self.exporter.from_filename(notebook_filename, 
resources=resources)
  File 
"/usr/lib/python3/dist-packages/nbconvert/exporters/exporter.py", line 
174, in from_filename

return self.from_file(f, resources=resources, **kw)
  File 
"/usr/lib/python3/dist-packages/nbconvert/exporters/exporter.py", line 
192, in from_file
return self.from_notebook_node(nbformat.read(file_stream, 
as_version=4), resources=resources, **kw)
  File 
"/usr/lib/python3/dist-packages/nbconvert/exporters/notebook.py", line 
31, in from_notebook_node
nb_copy, resources = super(NotebookExporter, 
self).from_notebook_node(nb, resources, **kw)
  File 
"/usr/lib/python3/dist-packages/nbconvert/exporters/exporter.py", line 
134, in from_notebook_node

nb_copy, resources = self._preprocess(nb_copy, resources)
  File 
"/usr/lib/python3/dist-packages/nbconvert/exporters/exporter.py", line 
311, in _preprocess

nbc, resc = preprocessor(nbc, resc)
  File 
"/usr/lib/python3/dist-packages/nbconvert/preprocessors/base.py", line 
47, in __call__

return self.preprocess(nb, resources)
  File 
"/usr/lib/python3/dist-packages/nbconvert/preprocessors/execute.py", 
line 257, in preprocess

cwd=path)
  File 
"/usr/lib/python3/dist-packages/nbconvert/preprocessors/execute.py", 
line 241, in start_new_kernel

kc.wait_for_ready(timeout=startup_timeout)
  File 
"/usr/lib/python3/dist-packages/jupyter_client/blocking/client.py", line 
120, in wait_for_ready

raise RuntimeError('Kernel died before replying to kernel_info')
RuntimeError: Kernel died before replying to kernel_info
$

Bug#893443: diffoscope: please make it easier to see supported file formats

[Chris Lamb]

Package: diffoscope
Version: 91
Severity: wishlist
X-Debbugs-CC: Jonathan Dowland 

Hi,

  < Jon> lamby, https://diffoscope.org/ should link to or provide (more
 easily) a list of supported archive types

Great idea. :)


Best wishes,

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

Bug#893442: lynkeos.app: FTBFS on ppc64el: AltiVec argument passed to unprototyped function

[Yavor Doganov]

Source: lynkeos.app
Version: 2.10+dfsg1-2
Severity: serious
Tags: patch
User: debian-powe...@lists.debian.org
Usertags: ppc64el

I would appreciate if someone knowledgeable from -powerpc confirms
that the attached patch is correct.  The build failure is:

gcc /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m 
-c \
  -MMD -MP -Wdate-time -D_FORTIFY_SOURCE=2 -I. -I.. 
-I/<>/lynkeos.app-2.10+dfsg1/GNUstep.. 
-I/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources 
-I/<>/lynkeos.app-2.10+dfsg1/GNUstep/../ThreadConnectionSources 
-I/<>/lynkeos.app-2.10+dfsg1/GNUstep/../ThirdPartySources/SMDoubleSlider
 -DNO_FRAMEWORK_CHECK=1 -DGNUSTEP -DGNUSTEP_BASE_LIBRARY=1 -DGNU_GUI_LIBRARY=1 
-DGNU_RUNTIME=1 -DGNUSTEP_BASE_LIBRARY=1 -fno-strict-aliasing -fexceptions 
-fobjc-exceptions -D_NATIVE_OBJC_EXCEPTIONS -pthread -fPIC -Wall -DGSWARN 
-DGSDIAGNOSE -Wno-import -g -O2 -g -O2 
-fdebug-prefix-map=/<>/lynkeos.app-2.10+dfsg1=. 
-fstack-protector-strong -Wformat -Werror=format-security -fgnu-runtime 
-Wno-unknown-pragmas -Wno-cpp -fconstant-string-class=NSConstantString -I. 
-I/usr/local/include/GNUstep -I/usr/include/GNUstep \
   -o obj/Lynkeos.obj/MyDeconvolution.m.o
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m: In 
function 'vector_Process_One_line':
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:72:44:
 warning: excess elements in vector initializer
0x04050607, 0x04050607 };
^~
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:72:44:
 note: (near initialization for 'Vperma')
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:72:56:
 warning: excess elements in vector initializer
0x04050607, 0x04050607 };
^~
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:72:56:
 note: (near initialization for 'Vperma')
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:74:44:
 warning: excess elements in vector initializer
0x0C0D0E0F, 0x0C0D0E0F };
^~
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:74:44:
 note: (near initialization for 'Vpermb')
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:74:56:
 warning: excess elements in vector initializer
0x0C0D0E0F, 0x0C0D0E0F };
^~
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:74:56:
 note: (near initialization for 'Vpermb')
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:88:13:
 warning: implicit declaration of function 'vec_madd' 
[-Wimplicit-function-declaration]
   Vdx = vec_madd( vec_ld(0,expXptr), Vdy, Vzero );
 ^~~~
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:88:23:
 warning: implicit declaration of function 'vec_ld'; did you mean 'vector'? 
[-Wimplicit-function-declaration]
   Vdx = vec_madd( vec_ld(0,expXptr), Vdy, Vzero );
   ^~
   vector
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:88:7: 
error: AltiVec argument passed to unprototyped function
   Vdx = vec_madd( vec_ld(0,expXptr), Vdy, Vzero );
   ^~~
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:89:41:
 warning: implicit declaration of function 'vec_cmplt' 
[-Wimplicit-function-declaration]
   const __vector __bool int Vmask = vec_cmplt(Vdx,Vthr);
 ^
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:89:7: 
error: AltiVec argument passed to unprototyped function
   const __vector __bool int Vmask = vec_cmplt(Vdx,Vthr);
   ^
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:90:27:
 warning: implicit declaration of function 'vec_and'; did you mean 'vscanf'? 
[-Wimplicit-function-declaration]
   __vector REAL Vge = vec_and(Vdx,Vmask);
   ^~~
   vscanf
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:90:7: 
error: AltiVec argument passed to unprototyped function
   __vector REAL Vge = vec_and(Vdx,Vmask);
   ^~~~
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:91:27:
 warning: implicit declaration of function 'vec_andc'; did you mean 'vscanf'? 
[-Wimplicit-function-declaration]
   __vector REAL Vlt = vec_andc(Vthr,Vmask);
   ^~~~
   vscanf
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:91:7: 
error: AltiVec argument passed to unprototyped function
   __vector REAL Vlt = vec_andc(Vthr,Vmask);
   ^~~~
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:92:13

Bug#891407: httping: diff for NMU version 2.5-1.1

[Adrian Bunk]

Control: tags 891407 + patch
Control: tags 891407 + pending

Dear maintainer,

I've prepared an NMU for httping (versioned as 2.5-1.1) and uploaded
it to DELAYED/14. Please feel free to tell me if I should cancel it.

cu
Adrian

-- 

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

diff -Nru httping-2.5/debian/changelog httping-2.5/debian/changelog
--- httping-2.5/debian/changelog	2016-09-12 18:34:13.0 +0300
+++ httping-2.5/debian/changelog	2018-03-18 22:14:33.0 +0200
@@ -1,3 +1,10 @@
+httping (2.5-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Build-depend on clang-tools. (Closes: #891407)
+
+ -- Adrian Bunk   Sun, 18 Mar 2018 22:14:33 +0200
+
 httping (2.5-1) unstable; urgency=low
 
   * New upstream release
diff -Nru httping-2.5/debian/control httping-2.5/debian/control
--- httping-2.5/debian/control	2016-09-12 18:34:13.0 +0300
+++ httping-2.5/debian/control	2018-03-18 22:14:33.0 +0200
@@ -5,6 +5,7 @@
 Build-Depends: debhelper (>= 9), 
libssl-dev, 
clang, 
+   clang-tools,
libncursesw5-dev, 
libncurses5-dev, 
libfftw3-dev,

Bug#893441: kdeplasma-addons: do you really need scim-dev?

[Helmut Grohne]

Source: kdeplasma-addons
Version: 4:5.12.3-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

Like in #893435, the scim-dev dependency is problematic for cross
building and likely unnecessary. Indeed, building kdeplasma-addons with
libscim-dev is successful. Please consider demoting the build
dependency.

Helmut
diff --minimal -Nru kdeplasma-addons-5.12.3/debian/changelog 
kdeplasma-addons-5.12.3/debian/changelog
--- kdeplasma-addons-5.12.3/debian/changelog2018-03-07 19:14:04.0 
+0100
+++ kdeplasma-addons-5.12.3/debian/changelog2018-03-18 21:04:06.0 
+0100
@@ -1,3 +1,10 @@
+kdeplasma-addons (4:5.12.3-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Demote scim-dev build dependency to libscim-dev. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 18 Mar 2018 21:04:06 +0100
+
 kdeplasma-addons (4:5.12.3-1) sid; urgency=medium
 
   * New upstream release (5.12.3).
diff --minimal -Nru kdeplasma-addons-5.12.3/debian/control 
kdeplasma-addons-5.12.3/debian/control
--- kdeplasma-addons-5.12.3/debian/control  2018-03-07 19:14:04.0 
+0100
+++ kdeplasma-addons-5.12.3/debian/control  2018-03-18 21:04:03.0 
+0100
@@ -28,6 +28,7 @@
libkf5sysguard-dev,
libkf5unitconversion-dev (>= 5.42.0~),
libqt5x11extras5-dev (>= 5.9.0~),
+   libscim-dev,
libx11-dev,
libxcb-image0-dev,
libxcb-keysyms1-dev,
@@ -39,7 +40,6 @@
qtbase5-dev (>= 5.9.0~),
qtdeclarative5-dev (>= 5.9.0~),
qtwebengine5-dev (>= 5.9.0~) [amd64 arm64 armhf i386 mipsel],
-   scim-dev,
shared-mime-info,
 Standards-Version: 4.1.3
 Homepage: https://projects.kde.org/projects/kde/workspace/kdeplasma-addons

Bug#893440: xfce4-terminal tabs always require confirmation of closure

[nekit]

Package: xfce4-terminal
Version: 0.8.7.1-1

When you use multiple tabs (for example, 2) and try to close one tab with the 
program running (for example, bash), the terminal ignores the already marked 
"Do not ask anymore" check box and still asks to confirm the tab closing.

$ uname -a
Linux *** 4.14.0-3-686 #1 SMP Debian 4.14.17-1 (2018-02-14) i686 GNU/Linux

PRETTY_NAME from the /etc/os-release: "Debian GNU/Linux buster/sid"

All packages are updated at the time of detection of the bug.

Bug#893439: stretch-pu: package gnucash/1:2.6.15-1+deb9u1

[Adrian Bunk]

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

libdbi 0.9.0-4+deb9u1 broke gnucash tests, runtime issues
with this backend were so far not reported but are not unlikely.
diff -Nru gnucash-2.6.15/debian/changelog gnucash-2.6.15/debian/changelog
--- gnucash-2.6.15/debian/changelog 2016-12-21 23:24:13.0 +0200
+++ gnucash-2.6.15/debian/changelog 2018-03-18 21:22:16.0 +0200
@@ -1,3 +1,11 @@
+gnucash (1:2.6.15-1+deb9u1) stretch; urgency=medium
+
+  * Non-maintainer upload.
+  * Add upstream fix for building with libdbi 0.9.0-4+deb9u1,
+thanks to Morham Malpense for the bug report. (Closes: #893077)
+
+ -- Adrian Bunk   Sun, 18 Mar 2018 21:22:16 +0200
+
 gnucash (1:2.6.15-1) unstable; urgency=medium
 
   * New upstream release [December 2016].
diff -Nru gnucash-2.6.15/debian/patches/789928u.patch 
gnucash-2.6.15/debian/patches/789928u.patch
--- gnucash-2.6.15/debian/patches/789928u.patch 1970-01-01 02:00:00.0 
+0200
+++ gnucash-2.6.15/debian/patches/789928u.patch 2018-03-18 21:21:48.0 
+0200
@@ -0,0 +1,75 @@
+Forwarded: not-needed
+Origin: upstream, 
https://github.com/Gnucash/gnucash/commit/45bab93613e6a93b206b74ffc18f63708b07293b.patch
+From 45bab93613e6a93b206b74ffc18f63708b07293b Mon Sep 17 00:00:00 2001
+From: John Ralls 
+Date: Tue, 7 Nov 2017 18:06:04 -0800
+Subject: Bug 789928 - FTBFS with libdbi 0.9.0-5 on Debian
+
+Commit 88b8477 on libdbi calls the error handler if one attempts to run
+off the end of a result set. Since we often loop on
+dbi_result_next_row() returning 0 this breaks our logic in several
+places. This change simply returns from the error handler on a
+DB_ERROR_BADIDX allowing the logic to work as before.
+
+--- a/src/backend/dbi/gnc-backend-dbi.c
 b/src/backend/dbi/gnc-backend-dbi.c
+@@ -395,10 +395,15 @@
+ {
+ const gchar* msg;
+ GncDbiBackend *be = (GncDbiBackend*)user_data;
+ GncDbiSqlConnection *dbi_conn = (GncDbiSqlConnection*)(be->sql_be.conn);
+-
+-(void)dbi_conn_error( conn, &msg );
++int err_num = dbi_conn_error( conn, &msg );
++/* BADIDX is raised if we attempt to seek outside of a result. We
++ * handle that possibility after checking the return value of the
++ * seek. Having this raise a critical error breaks looping by
++ * testing for the return value of the seek.
++ */
++if (err_num == DBI_ERROR_BADIDX) return;
+ PERR( "DBI error: %s\n", msg );
+ gnc_dbi_set_error( dbi_conn, ERR_BACKEND_MISC, 0, FALSE );
+ }
+ 
+@@ -610,16 +615,20 @@
+ {
+ GncDbiBackend *be = (GncDbiBackend*)user_data;
+ GncDbiSqlConnection *dbi_conn = (GncDbiSqlConnection*)be->sql_be.conn;
+ const gchar* msg;
+-gint err_num;
+ #ifdef G_OS_WIN32
+ const guint backoff_msecs = 1;
+ #else
+ const guint backoff_usecs = 1000;
+ #endif
+-
+-err_num = dbi_conn_error( conn, &msg );
++int err_num = dbi_conn_error( conn, &msg );
++/* BADIDX is raised if we attempt to seek outside of a result. We
++ * handle that possibility after checking the return value of the
++ * seek. Having this raise a critical error breaks looping by
++ * testing for the return value of the seek.
++ */
++if (err_num == DBI_ERROR_BADIDX) return;
+ 
+ /* Note: the sql connection may not have been initialized yet
+  *   so let's be careful with using it
+  */
+@@ -1330,10 +1339,16 @@
+ const guint backoff_msecs = 1;
+ #else
+ const guint backoff_usecs = 1000;
+ #endif
++int err_num = dbi_conn_error( conn, &msg );
++/* BADIDX is raised if we attempt to seek outside of a result. We
++ * handle that possibility after checking the return value of the
++ * seek. Having this raise a critical error breaks looping by
++ * testing for the return value of the seek.
++ */
++if (err_num == DBI_ERROR_BADIDX) return;
+ 
+-(void)dbi_conn_error( conn, &msg );
+ if ( g_str_has_prefix( msg, "FATAL:  database" ) &&
+ g_str_has_suffix( msg, "does not exist\n" ) )
+ {
+ PINFO( "DBI error: %s\n", msg );
diff -Nru gnucash-2.6.15/debian/patches/series 
gnucash-2.6.15/debian/patches/series
--- gnucash-2.6.15/debian/patches/series2016-12-21 23:24:13.0 
+0200
+++ gnucash-2.6.15/debian/patches/series2018-03-18 21:22:16.0 
+0200
@@ -1 +1,2 @@
+789928u.patch
 hardening-fortify.patch

Bug#893437: ITP: golang-github-vividcortex-godaemon -- Daemonize Go applications deviously.

[Eric Dorland]

Package: wnpp
Severity: wishlist
Owner: Eric Dorland 

* Package name: golang-github-vividcortex-godaemon
  Version : 0.0~git20150910.3d9f6e0-1
  Upstream Author : VividCortex
* URL : https://github.com/VividCortex/godaemon
* License : MIT
  Programming Lang: Go
  Description : Daemonize Go applications deviously

 Daemonize Go applications with exec() instead of fork().
 .
 You can't daemonize the usual way in Go. Daemonizing is a Unix concept
 that requires some specific things (http://goo.gl/vTUsVy) you can't do
 easily in Go. But you can still accomplish the same goals if you don't
 mind that your program will start copies of itself several times, as
 opposed to using fork() the way many programmers are accustomed to doing.

Bug#893438: mark kwin-data Multi-Arch: foreign

[Helmut Grohne]

Package: kwin-data
Version: 4:5.12.3-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
Control: affects -1 + src:apper src:khotkeys src:oxygen src:plasma-workspace 
src:powerdevil

The affected packages cannot satisfy their cross Build-Depends, because
their transitive dependency on kwin-data is unsatisfiable. In general,
Architecture: all packages can never satisfy cross Build-Depends unless
marked Multi-Arch: foreign. In this case, such a marking is correct,
because kwin-data entirely lacks dependencies and maintainer scripts.
Please consider applying the attached patch.

Helmut
diff --minimal -Nru kwin-5.12.3/debian/changelog kwin-5.12.3/debian/changelog
--- kwin-5.12.3/debian/changelog2018-03-07 19:14:08.0 +0100
+++ kwin-5.12.3/debian/changelog2018-03-18 20:59:47.0 +0100
@@ -1,3 +1,10 @@
+kwin (4:5.12.3-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Mark kwin-data Multi-Arch: foreign. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 18 Mar 2018 20:59:47 +0100
+
 kwin (4:5.12.3-1) sid; urgency=medium
 
   * New upstream release (5.12.2).
diff --minimal -Nru kwin-5.12.3/debian/control kwin-5.12.3/debian/control
--- kwin-5.12.3/debian/control  2018-03-07 19:14:08.0 +0100
+++ kwin-5.12.3/debian/control  2018-03-18 20:58:59.0 +0100
@@ -117,6 +117,7 @@
 
 Package: kwin-data
 Architecture: all
+Multi-Arch: foreign
 Depends: ${misc:Depends}, ${shlibs:Depends}
 Recommends: plasma-framework,
 qml-module-qtmultimedia,

Bug#893436: jupyter-notebook: CVE-2018-8768

[Salvatore Bonaccorso]

Source: jupyter-notebook
Version: 4.2.3-4
Severity: grave
Tags: patch security upstream

Hi,

the following vulnerability was published for jupyter-notebook.

CVE-2018-8768[0]:
| In Jupyter Notebook before 5.4.1, a maliciously forged notebook file
| can bypass sanitization to execute JavaScript in the notebook context.
| Specifically, invalid HTML is 'fixed' by jQuery after sanitization,
| making it dangerous.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-8768
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-8768
[1] http://www.openwall.com/lists/oss-security/2018/03/15/2
[2] 
https://github.com/jupyter/notebook/commit/4e79ebb49acac722b37b03f1fe811e67590d3831

Regards,
Salvatore

Bug#893435: plasm-desktop: do you really need scim-dev?

[Helmut Grohne]

Source: plasma-desktop
Version: 4:5.12.3-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

The scim-dev Build-Dependency of plasma-desktop is not satisfiable for
cross compilation. Now scim-dev is supposed to be a meta package pulling
libscim-dev and scim-dev-doc. Is there any reason to need scim-dev-doc?
I think using libscim-dev in Build-Depends should be sufficient. In
deed, comparing a build with just libscim-dev shows little differences
to one without beyond build paths and build ids. Can you demote the
dependency?

Helmut
diff --minimal -Nru plasma-desktop-5.12.3/debian/changelog 
plasma-desktop-5.12.3/debian/changelog
--- plasma-desktop-5.12.3/debian/changelog  2018-03-07 19:14:09.0 
+0100
+++ plasma-desktop-5.12.3/debian/changelog  2018-03-18 20:18:21.0 
+0100
@@ -1,3 +1,10 @@
+plasma-desktop (4:5.12.3-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Demote scim-dev build dependency to libscim-dev. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 18 Mar 2018 20:18:21 +0100
+
 plasma-desktop (4:5.12.3-1) sid; urgency=medium
 
   * New upstream release (5.12.3).
diff --minimal -Nru plasma-desktop-5.12.3/debian/control 
plasma-desktop-5.12.3/debian/control
--- plasma-desktop-5.12.3/debian/control2018-03-07 19:14:09.0 
+0100
+++ plasma-desktop-5.12.3/debian/control2018-03-18 20:18:21.0 
+0100
@@ -53,6 +53,7 @@
libpulse-dev (>= 0.9.16),
libqt5svg5-dev (>= 5.9.0~),
libqt5x11extras5-dev (>= 5.9.0~),
+   libscim-dev,
libudev-dev,
libx11-dev,
libx11-xcb-dev,
@@ -72,7 +73,6 @@
plasma-workspace-dev (>= 4:5.12~),
qtbase5-dev (>= 5.9.0~),
qtdeclarative5-dev (>= 5.9.0~),
-   scim-dev,
xauth,
xserver-xorg-dev,
xserver-xorg-input-evdev-dev,

Bug#893434: Please build python3-bpfcc

[debian]

Source: bpfcc
Version: 0.5.0-4
Priority: wishlist

Hi,

Upstream appear to support python3. Please ship the python3 version of
the bindings!

Cheers,
Chris.

Bug#893433: libegl1-mesa-dev: File conflicts with libwayland-dev:amd64 1.14.91-1

[Lisandro Damián Nicanor Pérez Meyer]

Package: libegl1-mesa-dev
Version: 18.0.0~rc4-1
Severity: serious
Justification: File conflicts

Hi! While trying to build qtwayland I ran across:

dpkg: error processing archive 
/tmp/apt-dpkg-install-VBKAMl/062-libegl1-mesa-dev_18.0.0~rc4-1_amd64.deb 
(--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which 
is also in package libwayland-dev:amd64 1.14.91-1

Admitedly I'm using a build against experimental using aspcud as dep resolver, 
as I need to build Qt in experimental, so maybe this is related.

Thanks, Lisandro.

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

Kernel: Linux 4.15.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_AR:es (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libegl1-mesa-dev depends on:
ii  libdrm-dev2.4.91-1
ii  libglvnd-dev  1.0.0-2
pn  libwayland-dev
ii  libwayland-egl1-mesa  17.3.6-1
ii  libx11-dev2:1.6.4-3
ii  libx11-xcb-dev2:1.6.4-3
ii  libxcb-dri2-0-dev 1.13-1
ii  libxcb-dri3-dev   1.13-1
ii  libxcb-glx0-dev   1.13-1
ii  libxcb-present-dev1.13-1
ii  libxcb-sync-dev   1.13-1
ii  libxdamage-dev1:1.1.4-3
ii  libxext-dev   2:1.3.3-1+b2
ii  libxfixes-dev 1:5.0.3-1
ii  libxshmfence-dev  1.2-1+b2
ii  libxxf86vm-dev1:1.1.4-1+b2
ii  x11proto-dri2-dev 2.8-2
ii  x11proto-gl-dev   1.4.17-1

libegl1-mesa-dev recommends no packages.

libegl1-mesa-dev suggests no packages.

Bug#893431: libevt: CVE-2018-8754

[Salvatore Bonaccorso]

Source: libevt
Version: 20170120-1
Severity: important
Tags: patch security upstream

Hi,

the following vulnerability was published for libevt.

CVE-2018-8754[0]:
| The libevt_record_values_read_event() function in
| libevt_record_values.c in libevt before 2018-03-17 does not properly
| check for out-of-bounds values of user SID data size, strings size, or
| data size.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-8754
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-8754
[1] 
https://github.com/libyal/libevt/commit/444ca3ce7853538c577e0ec3f6146d2d65780734

Regards,
Salvatore

Bug#893369: systemd-udevd is killed at startup

[Mickaël Leduque]

Package: systemd
Version: 238-2
Followup-For: Bug #893369

It didn't work so I just added the options in /etc/default/grub.
Here are the journal and the systemctl list-jobs output (which is just "no 
jobs").

-- Package-specific info:

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

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

Versions of packages systemd depends on:
ii  adduser  3.117
ii  libacl1  2.2.52-3+b1
ii  libapparmor1 2.12-3
ii  libaudit11:2.8.2-1
ii  libblkid12.31.1-0.5
ii  libc62.27-2
ii  libcap2  1:2.25-1.2
ii  libcryptsetup12  2:2.0.2-1
ii  libgcrypt20  1.8.1-4
ii  libgpg-error01.28-1
ii  libidn11 1.33-2.1
ii  libip4tc01.6.2-1
ii  libkmod2 25-1
ii  liblz4-1 0.0~r131-2+b1
ii  liblzma5 5.2.2-1.3
ii  libmount12.31.1-0.5
ii  libpam0g 1.1.8-3.7
ii  libseccomp2  2.3.1-2.1
ii  libselinux1  2.7-2+b1
ii  libsystemd0  238-2
ii  mount2.31.1-0.5
ii  procps   2:3.3.12-4
ii  util-linux   2.31.1-0.5

Versions of packages systemd recommends:
ii  dbus1.12.6-2
ii  libpam-systemd  238-2

Versions of packages systemd suggests:
ii  policykit-10.113-2
pn  systemd-container  

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.130
ii  udev 238-2

-- no debconf information
-- Logs begin at Fri 2017-10-06 17:03:19 CEST, end at Sun 2018-03-18 20:32:15 
CET. --
mars 18 20:30:14 falkynkip kernel: microcode: microcode updated early to 
revision 0x1f, date = 2018-02-07
mars 18 20:30:14 falkynkip kernel: Linux version 4.15.0-1-amd64 
(debian-ker...@lists.debian.org) (gcc version 7.3.0 (Debian 7.3.0-3)) #1 SMP 
Debian 4.15.4-1 (2018-02-18)
mars 18 20:30:14 falkynkip kernel: Command line: 
BOOT_IMAGE=/boot/vmlinuz-4.15.0-1-amd64 
root=UUID=5fe70463-3aae-4be3-ac38-9a92ac404edb ro quiet 
init=/lib/systemd/systemd
mars 18 20:30:14 falkynkip kernel: x86/fpu: Supporting XSAVE feature 0x001: 
'x87 floating point registers'
mars 18 20:30:14 falkynkip kernel: x86/fpu: Supporting XSAVE feature 0x002: 
'SSE registers'
mars 18 20:30:14 falkynkip kernel: x86/fpu: Supporting XSAVE feature 0x004: 
'AVX registers'
mars 18 20:30:14 falkynkip kernel: x86/fpu: xstate_offset[2]:  576, 
xstate_sizes[2]:  256
mars 18 20:30:14 falkynkip kernel: x86/fpu: Enabled xstate features 0x7, 
context size is 832 bytes, using 'standard' format.
mars 18 20:30:14 falkynkip kernel: e820: BIOS-provided physical RAM map:
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0x-0x0009d7ff] usable
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0x0009d800-0x0009] reserved
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0x000e-0x000f] reserved
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0x0010-0x1fff] usable
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0x2000-0x201f] reserved
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0x2020-0x40003fff] usable
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0x40004000-0x40004fff] reserved
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0x40005000-0xcced8fff] usable
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0xcced9000-0xcd7fafff] reserved
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0xcd7fb000-0xcd884fff] usable
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0xcd885000-0xcd923fff] ACPI NVS
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0xcd924000-0xce163fff] reserved
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0xce164000-0xce164fff] usable
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0xce165000-0xce1a7fff] ACPI NVS
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0xce1a8000-0xcebfbfff] usable
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0xcebfc000-0xceff1fff] reserved
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0xceff2000-0xceff] usable
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0xcf80-0xdf9f] reserved
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0xf800-0xfbff] reserved
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0xfec0-0xfec00fff] reserved
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0xfed0-0xfed03fff] reserved
mars 18 20:30:14 falkynkip kernel: BIOS-e82

Bug#893387: qtwayland-opensource-src: Qt5 Wayland Client Dev Package missing

[Lisandro Damián Nicanor Pérez Meyer]

On 18 March 2018 at 15:45, Lisandro Damián Nicanor Pérez Meyer
 wrote:
[snip]
>> If I remember correctly we removed the libraries that do not provide
>> stable API. I'll recheck the packaging to see what needs to get
>> removed, but if it depends on private API we have a big issue here.
>
> Please tell me which are the exact files missing and/or the debian
> rules entries that remove them.

Found them! With a build at hand it's easier to detect them ;-)

Thanks for your bug report, this will hit the archive (hopefully) soon.

-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

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

[Jonathan McDowell]

On Thu, Mar 15, 2018 at 11:59:25AM +0100, Mattia Rizzolo wrote:
> On Wed, Feb 14, 2018 at 10:06:24PM +, Jonathan McDowell wrote:
> > Fingerprint changes are currently allowed for anyone who doesn't have an
> > account in LDAP, which includes DMs without a guest account. However
> > this means that the DM keyring gets out of sync with what nm.debian.org
> > thinks is the state of the world. "hibby" is a good example of this.
> 
> I changed hibby back to the key he had before.  He clearly wasn't using
> his new one, and his change was fairly old.  The most similar case now
> is tkren, see below.
> 
> We have 3 other cases right now:

[snip 2 DM -> DD cases]
> * weinholt:
>   DD returning from retirement; he had to add a new 4096R key as his
>   past 1024D was no good anymore.  We will have just to wait for this,
>   but how would you have handled it from the keyring-maint side?  I
>   don't believe you'd have liked a "emeritus key rollover" :P

This is an emeritus DD to DD status and is explicitly allowed by the
site - I agree this should be the case. The case I'm interested in
preventing is someone with a key in an active keyring managing to change
the fingerprint nm.d.o thinks is authoritative for them without it
having first been updated in the active keyring.

> > We shouldn't allow DMs to change their fingerprint via nm.debian.org;
> > once you're part of the project you should go through the usual keyring
> > replacement process.
> 
> Enrico told me that the ability to becoming a DD with a key different
> than the one used while being a DM is a feature (i.e., on the
> keyring-maint side it looks like "add new dd key + remove dm key"
> instead of "move key from dm to dd"), and it has been done in the past.

I don't think it's a useful feature, I think it's just one that happened
to exist as a result of the way things worked before DM was folded into
nm.debian.org.

> I'm not sure it's a good excuse, and I kind of agree with noodles here;
> however, I also don't think prospective applicants should need to wait
> for the monthly update to start a process if they want or need a new
> key

The instances I've seen of people changing keys would not have resulted
in processes being held up due to the monthly update. If a key is
compromised the update happens much faster (and should be done via that
method), if it's a case of the applicant moving to a different key but
the old one is still fine then they can continue to use the old key if
they don't want extra delay. And realistically the shortage of AMs is
more likely to cause a delay than the keyring-maint update time.

I also think there's a slight argument that allowing a backdoor key
change as part of an application process theoretically reduces security.
There is no signed statement of movement from one key to another which
would normally exist, it's just an update in the website.

J.

-- 
Where's your fishing rod, lawn ornament?
This .sig brought to you by the letter B and the number 19
Product of the Republic of HuggieTag


signature.asc
Description: PGP signature

Bug#893120: debian-edu-install: uninstallable on ahrd disk thrice the size mentioned in manual

[Dominik George]

Hi,

>I figure you used 'desktop=kde' (default kernel command line entry,
>common for
>all profiles); in this single case LTSP installation fails
>reproducibly.

Yeah, well, that's what I meant by "default".

A diversion from defaults is a diversion from defaults, even if some text 
contradicts the defaults.

Why wasn't desktop=lxde made the default if it is the default?

-nik

Bug#893430: clang: scan-build-4.0 is not installed

[Sylvestre Ledru]

Le 18/03/2018 à 20:13, Michael Becker a écrit :
> Package: clang
> Version: 1:4.0-40
> Severity: normal
>
> a symbolic link /usr/bin/scna-build --> /usr/bin/scan-build-4.0 is created 
> but scan-build-4.0 does not exist

This will be fixed when llvm-defauts from experimental will be uploaded
in unstable.

It is because scan-build is now provided by clang-tools

S

Bug#893111: debian-edu-install: Consider LTSP PnP

[Wolfgang Schweer]

On Fri, Mar 16, 2018 at 04:42:40PM +0100, Dominik George wrote:

> LTSP got a new mode called LTSP-PnP, where the image for clients is not
> built from a debootstrapped chroot, but rather from the host filesystem,
> with ways to strip unwanted contents and change details before packing
> the squashfs.

As far as I remember this has been developped some years ago for single purpose
LTSP installation (mostly at Greek schools). 

> That would make Debain Edu a lot more easy on disk resources and the
> installation a lot quicker, an also ease updates and changes to the
> environment.

It doesn't fit the Debian Edu case and is way to unflexible, i.e. 
doesn't allow to serve LTSP clients with different archs. 

Wolfgang


signature.asc
Description: PGP signature

Bug#893409: pixelmed FTBFS with openjdk-9

[Andreas Tille]

Control: tags -1 help

On Sun, Mar 18, 2018 at 07:54:32PM +0200, Adrian Bunk wrote:
> Source: pixelmed
> Version: 20150917-2
> Severity: serious
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pixelmed.html
> 
> ...
> ../../../../com/pixelmed/display/SourceImage.java:1626: error: cannot find 
> symbol
>   sun.misc.Cleaner cleaner = 
> (sun.misc.Cleaner)getCleanerMethod.invoke(object,new Object[0]);
>   ^
>   symbol:   class Cleaner
>   location: package sun.misc
> ../../../../com/pixelmed/display/SourceImage.java:1626: error: cannot find 
> symbol
>   sun.misc.Cleaner cleaner = 
> (sun.misc.Cleaner)getCleanerMethod.invoke(object,new Object[0]);
>   
> ^
>   symbol:   class Cleaner
>   location: package sun.misc

Unfortunately I have no idea how to fix this.  Any hint?

Kind regards

   Andreas. 

-- 
http://fam-tille.de

Bug#893430: clang: scan-build-4.0 is not installed

[Michael Becker]

Package: clang
Version: 1:4.0-40
Severity: normal

a symbolic link /usr/bin/scna-build --> /usr/bin/scan-build-4.0 is created but 
scan-build-4.0 does not exist

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

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

Versions of packages clang depends on:
ii  clang-4.0  1:4.0.1-10

clang recommends no packages.

clang suggests no packages.

-- no debconf information

Bug#893284: vlc: VLC segfaults on highlight of Playback>Renderer menu option

[Sebastian Ramacher]

Control: reassign -1 libmicrodns0 0.0.9-1
Control: tags -1 = fixed-upstream upstream

On 2018-03-18 18:20:03, Hibby wrote:
> Hi Sebastian - 
> 
> > Please provide a backtrace of the crash. See
> > https://wiki.debian.org/HowToGetABacktrace for details.
> 
> No problems. There are two traces below, and I have reproduced this on two 
> different machines to check it's not my specific config.
> 
> First time round, I hit this:
> Starting program: /usr/bin/vlc vlc
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> VLC media player 3.0.1 Vetinari (revision 3.0.1-0-gec0f700fcc)
> [New Thread 0x7fff94402700 (LWP 18431)]
> [New Thread 0x7fff8fc01700 (LWP 18432)]
> [New Thread 0x7fff8fb00700 (LWP 18433)]
> [New Thread 0x7fff8f9ff700 (LWP 18434)]
> [55759570] main libvlc: Running vlc with the default interface. Use 
> 'cvlc' to use vlc without interface.
> [New Thread 0x7fff8f8fe700 (LWP 18435)]
> [New Thread 0x7fff8f7fd700 (LWP 18436)]
> [Thread 0x7fff8f8fe700 (LWP 18435) exited]
> [New Thread 0x7fff8f8fe700 (LWP 18437)]
> [New Thread 0x7fff8f6fc700 (LWP 18438)]
> [New Thread 0x7fff8f3f8700 (LWP 18439)]
> [Thread 0x7fff8f6fc700 (LWP 18438) exited]
> [New Thread 0x7fff8efcf700 (LWP 18440)]
> [Thread 0x7fff8efcf700 (LWP 18440) exited]
> [New Thread 0x7fff8d7f4700 (LWP 18441)]
> [Thread 0x7fff8f3f8700 (LWP 18439) exited]
> [Thread 0x7fff8f8fe700 (LWP 18437) exited]
> [Thread 0x7fff8f9ff700 (LWP 18434) exited]
> [New Thread 0x7fff62ce7700 (LWP 18442)]
> [New Thread 0x7fff8f3f8700 (LWP 18443)]
> [New Thread 0x7fff8f8fe700 (LWP 18444)]
> [New Thread 0x7fff8f9ff700 (LWP 18445)]
> [New Thread 0x7fff8efcf700 (LWP 18446)]
> [New Thread 0x7fff8f6fc700 (LWP 18447)]
> [Thread 0x7fff8efcf700 (LWP 18446) exited]
> [New Thread 0x7fff8efcf700 (LWP 18448)]
> [Thread 0x7fff8efcf700 (LWP 18448) exited]
> [7fff540015b0] filesystem stream error: cannot open file /home/hibby/vlc 
> (No such file or directory)
> [Thread 0x7fff8f8fe700 (LWP 18444) exited]
> [Thread 0x7fff8f9ff700 (LWP 18445) exited]
> [Thread 0x7fff8f6fc700 (LWP 18447) exited]
> 
> Thread 7 "vlc" received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7fff8f7fd700 (LWP 18436)]
> 0x7fffa5d07b64 in mdns_init () from 
> /usr/lib/x86_64-linux-gnu/libmicrodns.so.0
> 
> after installing `libmicrodns0-dbgsym` I got the following trace:
> 
> (gdb) run vlc
> Starting program: /usr/bin/vlc vlc
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> VLC media player 3.0.1 Vetinari (revision 3.0.1-0-gec0f700fcc)
> [New Thread 0x7fff94402700 (LWP 18681)]
> [New Thread 0x7fff8fc01700 (LWP 18682)]
> [New Thread 0x7fff8fb00700 (LWP 18683)]
> [New Thread 0x7fff8f9ff700 (LWP 18684)]
> [55759570] main libvlc: Running vlc with the default interface. Use 
> 'cvlc' to use vlc without interface.
> [New Thread 0x7fff8f8fe700 (LWP 18685)]
> [Thread 0x7fff8f8fe700 (LWP 18685) exited]
> [New Thread 0x7fff8f8fe700 (LWP 18686)]
> [New Thread 0x7fff8f7fd700 (LWP 18687)]
> [New Thread 0x7fff8f6fc700 (LWP 18688)]
> [New Thread 0x7fff8f5fb700 (LWP 18689)]
> [Thread 0x7fff8f7fd700 (LWP 18687) exited]
> [New Thread 0x7fff8f4fa700 (LWP 18690)]
> [Thread 0x7fff8f4fa700 (LWP 18690) exited]
> [New Thread 0x7fff8d7f4700 (LWP 18691)]
> [Thread 0x7fff8f5fb700 (LWP 18689) exited]
> [Thread 0x7fff8f8fe700 (LWP 18686) exited]
> [Thread 0x7fff8f9ff700 (LWP 18684) exited]
> [New Thread 0x7fff62ce7700 (LWP 18692)]
> [New Thread 0x7fff8f5fb700 (LWP 18693)]
> [New Thread 0x7fff8f8fe700 (LWP 18694)]
> [7fff78000fe0] filesystem stream error: cannot open file /home/hibby/vlc 
> (No such file or directory)
> [New Thread 0x7fff8f9ff700 (LWP 18695)]
> [Thread 0x7fff8f8fe700 (LWP 18694) exited]
> [New Thread 0x7fff8f8fe700 (LWP 18696)]
> [New Thread 0x7fff8f4fa700 (LWP 18697)]
> [Thread 0x7fff8f8fe700 (LWP 18696) exited]
> [New Thread 0x7fff8f8fe700 (LWP 18698)]
> [Thread 0x7fff8f8fe700 (LWP 18698) exited]
> [Thread 0x7fff8f9ff700 (LWP 18695) exited]
> [Thread 0x7fff8f4fa700 (LWP 18697) exited]
> 
> Thread 9 "vlc" received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7fff8f6fc700 (LWP 18688)]
> 0x7fffa5d07b64 in mdns_list_interfaces (ai_family=2, 
> p_nb_intf=0x7fff6800a958, pp_intfs=) at src/mdns.c:120
> 120 src/mdns.c: No such file or directory.
> 
> Perhaps this should be forwarded to the libmicrodns0 maintainers...

Looks like it's fixed already:
https://github.com/videolabs/libmicrodns/commit/efdf2754f9f8b801048b8fdae2b269f091128193

Will be fixed with the next upload.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#893429: mark osinfo-db Multi-Arch: foreign

[Helmut Grohne]

Source: osinfo-db
Version: 0.20180226-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
Control: affects -1 + src:tracker-miners

tracker-miners cannot satisfy its cross Build-Depends, because its
dependency on osinfo-db is unsatisfiable. In general Architecture: all
packages can never satisfy cross Build-Depends unless marked Multi-Arch:
foreign. In this case, such a marking is correct, because osinfo-db
entirely lacks maintainer scripts and dependencies. Please consider
applying the attached patch.

Helmut
diff --minimal -Nru osinfo-db-0.20180226/debian/changelog 
osinfo-db-0.20180226/debian/changelog
--- osinfo-db-0.20180226/debian/changelog   2018-02-26 10:21:37.0 
+0100
+++ osinfo-db-0.20180226/debian/changelog   2018-03-18 20:06:47.0 
+0100
@@ -1,3 +1,10 @@
+osinfo-db (0.20180226-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Mark osinfo-db Multi-Arch: foreign. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 18 Mar 2018 20:06:47 +0100
+
 osinfo-db (0.20180226-1) unstable; urgency=medium
 
   * Test that we can generate install scripts
diff --minimal -Nru osinfo-db-0.20180226/debian/control 
osinfo-db-0.20180226/debian/control
--- osinfo-db-0.20180226/debian/control 2017-09-25 12:19:12.0 +0200
+++ osinfo-db-0.20180226/debian/control 2018-03-18 20:06:47.0 +0100
@@ -14,6 +14,7 @@
 
 Package: osinfo-db
 Architecture: all
+Multi-Arch: foreign
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Description: Operating system database files
  libosinfo is a GObject based library API for managing information about

Bug#893120: debian-edu-install: uninstallable on ahrd disk thrice the size mentioned in manual

[Wolfgang Schweer]

On Fri, Mar 16, 2018 at 05:19:01PM +0100, Dominik George wrote:
> I spent two days trying to install Debian Edu (combined server) in a
> virtual machine. I started with 100 GiB hard disk, then tried 150 GiB,
> and finally 220 GiB. The LTSP chroot installation always fails with no
> space left in /opt/var/cache/apt.
>
> Installing Debain Edu is not possible.

I was unable to reproduce it (recommended 'desktop=lxde' setting, see manual).

I figure you used 'desktop=kde' (default kernel command line entry, common for
all profiles); in this single case LTSP installation fails reproducibly.

In the past I've tested also this case taking into account that reading a
manual isn't fun for most people and thus will simply hit return; back then
the KDE variant used to work as well, enough space was left.

Now, the netinstall ISO image being outdated and a lot of updated packages
getting installed after point release 9.4, /var/cache/apt/archives is filled
up and about 100 MiB space is missing.

(As LTSP mounts the server Apt cache and arch=i386 is the LTSP default, a whole
bunch of unneeded packages plus the updated ones show up.)

That said, a simple workaround is (if someone really wants KDE for LTSP 
clients):

After the Debian installer reported the LTSP menu item as failed:

(1) Activate a Debian installer shell.
(2) Run 'rm target/opt/ltsp -rf'
(3) Run 'rm target/var/cache/apt/archive/*_amd64.deb'
(4) Go back to the installer gui.
(5) Choose the LTSP menu item again.

One could use an even simpler solution:
Once the LTSP changeroot installation has started, do steps (1) and (3); the
installation will run without issues.

As far as Buster is concerned, the cache issue won't show up as the LTSP chroot
arch will be the same as the server one.


Wolfgang


signature.asc
Description: PGP signature

Bug#893394: debian-edu-install: FQDN wrongly ends up in /etc/hostname on tjener

[Dominik George]

Hi,

>Why do you believe this to be true?  The /etc/hostname in Skolelinux /
>Debian Edu is intentionally FQDN.  Personally, based on many years of
>large scale *nix system administration, I believe it is the only
>sensible thing to store there.
>
>In short, it is no mistake the FQDN is stored there.

Depends how you define "mistake".

You are right for pretty much everything except Debian. Debian has always had 
the short name in there, c.f. 
https://manpages.debian.org/stretch/hostname/hostname.1.en.html

This also states that "most software can cope" with an FQDN there, but 
primarily it documents that the short name is the right thing to put there. We 
should work with documented behaviour rather than a hope involving the terms 
"most" and "cope with" rather than "all" and "expect".

-nik

Bug#887922: libfuture-asyncawait-perl FTBFS on s390x: test failure

[gregor herrmann]

Version: 0.15-1

On Sun, 21 Jan 2018 20:10:47 +0200, Adrian Bunk wrote:

> Source: libfuture-asyncawait-perl
> Version: 0.13-1
> Severity: important
> 
> https://buildd.debian.org/status/fetch.php?pkg=libfuture-asyncawait-perl&arch=s390x&ver=0.13-1&stamp=1516518213&raw=0
> 
> ...
> Test Summary Report
> ---
> t/22context-foreach.t (Wstat: 11 Tests: 0 Failed: 0)
>   Non-zero wait status: 11
>   Parse errors: No plan found in TAP output
> Files=15, Tests=71,  1 wallclock secs ( 0.03 usr  0.01 sys +  0.48 cusr  0.05 
> csys =  0.57 CPU)
> Result: FAIL
> Failed 1/15 test programs. 0/71 subtests failed.
> dh_auto_test: perl Build test --verbose 1 returned exit code 255
> debian/rules:6: recipe for target 'build-arch' failed
> make: *** [build-arch] Error 2

0.15-1 built on s390x.

https://buildd.debian.org/status/fetch.php?pkg=libfuture-asyncawait-perl&arch=s390x&ver=0.15-1&stamp=1521396804&raw=0

Closing this bug.


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: Rolling Stones


signature.asc
Description: Digital Signature

Bug#893109: debian-edu-install: use cached apt archives when building chroot

[Wolfgang Schweer]

On Fri, Mar 16, 2018 at 04:40:52PM +0100, Dominik George wrote:
> LTSP offers a config option to ltsp-build-client that mounts the
> /var/cache/apt/archives directory to the target. This is helpful when
> building aa chroot on an LTSP server, where all packages used in the
> chroot were already downloaded on the host. It would also save space in
> /opt on installation.

This option actually is in use (and has been so since ages). 

Wolfgang


signature.asc
Description: PGP signature

Bug#893428: ITP: golang-github-facebookgo-pidfile -- Package pidfile manages pid files.

[Eric Dorland]

Package: wnpp
Severity: wishlist
Owner: Eric Dorland 

* Package name: golang-github-facebookgo-pidfile
  Version : 0.0~git20150612.f242e29-1
  Upstream Author : Facebook Go
* URL : https://github.com/facebookgo/pidfile
* License : MIT
  Programming Lang: Go
  Description : Go library for managing pid files

 Package pidfile manages pid files.

Bug#893108: debian-edu-install: please do not force complex partitioning scheme

[Wolfgang Schweer]

On Fri, Mar 16, 2018 at 04:37:13PM +0100, Dominik George wrote:

> The Skolelinux installer enforces a micropartitioning theme, splitting
> all parts of the filesystem into several volumes.

It's proposed, not enforced; a user can choose a different partion recipe
after declining to use automatic partitioning. 

> I propose compeltely dropping Edu's own partitioning scheme and simply
> using the corresponding step from the Debian installer, or defaulting to
> jsut one partition or at most three (root, home and backup).

IMO this change would reduce the existing flexibility to rather simple 
use cases.

Wolfgang


signature.asc
Description: PGP signature

Bug#893426: systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN

[Helmut Grohne]

Package: systemd
Version: 238-2
Severity: serious
User: helm...@debian.org
Usertags: rebootstrap

systemd fails to build from source on amd64. Here is a tail of the build
log.

| FAILED: journal-core@sta/src_journal_journald-context.c.o 
| cc  -Ijournal-core@sta -I. -I.. -I../ -Isrc/libsystemd-network 
-I../src/libsystemd-network -I../src/libsystemd/sd-network 
-I../src/libsystemd/sd-netlink -I../src/libsystemd/sd-id128 
-I../src/libsystemd/sd-hwdb -I../src/libsystemd/sd-device 
-I../src/libsystemd/sd-bus -Isrc/core -I../src/core -Isrc/libudev 
-I../src/libudev -Isrc/udev -I../src/udev -Isrc/login -I../src/login 
-Isrc/timesync -I../src/timesync -Isrc/resolve -I../src/resolve -Isrc/journal 
-I../src/journal -Isrc/systemd -I../src/systemd -Isrc/shared -I../src/shared 
-Isrc/basic -I../src/basic -flto -fdiagnostics-color=always -pipe 
-D_FILE_OFFSET_BITS=64 -std=gnu99 -Wextra -Werror=undef -Wlogical-op 
-Wmissing-include-dirs -Wold-style-definition -Wpointer-arith -Winit-self 
-Wdeclaration-after-statement -Wfloat-equal -Wsuggest-attribute=noreturn 
-Werror=missing-prototypes -Werror=implicit-function-declaration 
-Werror=missing-declarations -Werror=return-type 
-Werror=incompatible-pointer-types -Werror=format=2 -Wstrict-prototypes 
-Wredundant-decls -Wmissing-noreturn -Wimplicit-fallthrough=5 -Wshadow 
-Wendif-labels -Wstrict-aliasing=2 -Wwrite-strings -Werror=overflow -Wdate-time 
-Wnested-externs -ffast-math -fno-common -fdiagnostics-show-option 
-fno-strict-aliasing -fvisibility=hidden -fstack-protector 
-fstack-protector-strong --param=ssp-buffer-size=4 -fPIE -Wno-unused-parameter 
-Wno-missing-field-initializers -Wno-unused-result -Wno-format-signedness 
-Wno-error=nonnull -Werror=shadow -ffunction-sections -fdata-sections -include 
config.h -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -MD -MQ 
'journal-core@sta/src_journal_journald-context.c.o' -MF 
'journal-core@sta/src_journal_journald-context.c.o.d' -o 
'journal-core@sta/src_journal_journald-context.c.o' -c 
../src/journal/journald-context.c
| In file included from ../src/basic/alloc-util.h:28:0,
|  from ../src/journal/journald-context.c:25:
| ../src/basic/macro.h:423:18: error: expected ‘)’ before ‘__attribute__’
|  #define noreturn __attribute__((noreturn))
|   ^
| In file included from /usr/include/gcrypt.h:30:0,
|  from ../src/journal/journal-file.h:26,
|  from ../src/journal/journald-server.h:31,
|  from ../src/journal/journald-context.h:30,
|  from ../src/journal/journald-context.c:33:
| /usr/include/x86_64-linux-gnu/gpg-error.h:1545:46: error: expected ‘,’ or ‘;’ 
before ‘)’ token
|  void gpgrt_log_bug (const char *fmt, ...)GPGRT_ATTR_NR_PRINTF(1,2);
|   ^
| In file included from ../src/basic/alloc-util.h:28:0,
|  from ../src/journal/journald-context.c:25:
| ../src/basic/macro.h:423:18: error: expected ‘)’ before ‘__attribute__’
|  #define noreturn __attribute__((noreturn))
|   ^
| In file included from /usr/include/gcrypt.h:30:0,
|  from ../src/journal/journal-file.h:26,
|  from ../src/journal/journald-server.h:31,
|  from ../src/journal/journald-context.h:30,
|  from ../src/journal/journald-context.c:33:
| /usr/include/x86_64-linux-gnu/gpg-error.h:1546:46: error: expected ‘,’ or ‘;’ 
before ‘)’ token
|  void gpgrt_log_fatal (const char *fmt, ...)  GPGRT_ATTR_NR_PRINTF(1,2);
|   ^
| In file included from ../src/basic/alloc-util.h:28:0,
|  from ../src/journal/journald-context.c:25:
| ../src/basic/macro.h:423:18: error: expected ‘)’ before ‘__attribute__’
|  #define noreturn __attribute__((noreturn))
|   ^
| In file included from /usr/include/gcrypt.h:30:0,
|  from ../src/journal/journal-file.h:26,
|  from ../src/journal/journald-server.h:31,
|  from ../src/journal/journald-context.h:30,
|  from ../src/journal/journald-context.c:33:
| /usr/include/x86_64-linux-gnu/gpg-error.h:1558:43: error: expected ‘,’ or ‘;’ 
before ‘)’ token
|  const char *func) GPGRT_ATTR_NORETURN;
|^
| [231/1523] /usr/bin/python3 /usr/bin/meson --internal exe 
/<>/build-deb/meson-private/meson_exe_awk_ec289b1578d245bbf1d8589a5ea437fc6525ccd3.dat
| ninja: build stopped: subcommand failed.
| dh_auto_build: cd build-deb && LC_ALL=C.UTF-8 ninja -j8 -v returned exit code 
1
| make[1]: *** [debian/rules:161: override_dh_auto_build] Error 1
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:294: binary-arch] Error 2
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2

This issue might be related to the libgp

Bug#893427: tunnelx FTBFS with openjdk-9

[Adrian Bunk]

Source: tunnelx
Version: 20170928-1
Severity: serious

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

...
jh_build
find src -name *.java -and -type f -print0 | xargs -s 512000 -0 
/usr/lib/jvm/default-java/bin/javac -g -cp :debian/_jh_build.tunnelx -d 
debian/_jh_build.tunnelx -source 1.7 -target 1.7 -encoding ISO8859-1
warning: [options] bootstrap class path not set in conjunction with -source 1.7
src/SelectedSubsetsStructure.java:260: error: incompatible types: 
Enumeration cannot be converted to Enumeration
Enumeration 
tnenum = tn.depthFirstEnumeration(); 

 ^
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
1 warning
make[1]: *** [debian/rules:21: override_jh_build] Error 123

Bug#893425: nordugrid-arc FTBFS with openjdk-9

[Adrian Bunk]

Source: nordugrid-arc
Version: 5.4.2-1
Severity: serious

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

...
/usr/lib/jvm/java-1.9.0-openjdk-amd64/bin/javac -J-Xms50M -J-Xmx50M -source 1.5 
-target 1.5 -cp . nordugrid/arc/arc.java
warning: [options] bootstrap class path not set in conjunction with -source 1.5
error: Source option 1.5 is no longer supported. Use 1.6 or later.
error: Target option 1.5 is no longer supported. Use 1.6 or later.
make[4]: *** [Makefile:1110: nordugrid/arc/arc.class] Error 2

Bug#893387: qtwayland-opensource-src: Qt5 Wayland Client Dev Package missing

[Lisandro Damián Nicanor Pérez Meyer]

On 18 March 2018 at 15:31, Lisandro Damián Nicanor Pérez Meyer
 wrote:
> Hi Andreas!
>
> On 18 March 2018 at 10:44, Andreas Cord-Landwehr  wrote:
>> Source: qtwayland-opensource-src
>> Version: 5.9.2
>> Severity: important
>>
>> Dear Maintainer,
>>
>> the qtwayland5-dev-tools package provides the qtwaylandscanner binary, which
>> generates server side and client side headers and implementations for Wayland
>> extension protocols. Specifically, the qtwaylandscanner tool takes XML
>> definition files as input and generates C++ header and sources. These
>> sources depend on headers that are shipped with qtwayland-opensource-src.
>> All headers for the Wayland server side (AKA compositor) are provided with 
>> the
>> libqt5waylandcompositor5-dev package, yet the client side headers are not 
>> provided
>> and makes it impossible to generate both Wayland client and server 
>> implementations
>> with qtwaylandscanner.
>>
>> Right now, the client side headers are removed in debian/rules and I would 
>> like
>> to request them added again as a *-dev package; possible with a Suggests to
>> qtwayland5-dev-tools for this package, too.
>
> If I remember correctly we removed the libraries that do not provide
> stable API. I'll recheck the packaging to see what needs to get
> removed, but if it depends on private API we have a big issue here.

Please tell me which are the exact files missing and/or the debian
rules entries that remove them.