Bug#927107: unblock: openvswitch/2.10.0+2018.08.28+git.8ca7c82b7d+ds1-12

[Thomas Goirand]

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

Please unblock package openvswitch

As per the one liner attached debdiff, this Debian release -12 fixes
the debian/ifupdown.sh script which ends up in:
/etc/network/if-{pre-up,post-down}.d/openvswitch

When using an OVSBond interface, the script wasn't using --may-exist,
and as a consequence, may fail setting-up network interfaces in case
the bond already exists.

Note that the same change was commited upstream recently.

unblock openvswitch/2.10.0+2018.08.28+git.8ca7c82b7d+ds1-12
diff -Nru openvswitch-2.10.0+2018.08.28+git.8ca7c82b7d+ds1/debian/changelog 
openvswitch-2.10.0+2018.08.28+git.8ca7c82b7d+ds1/debian/changelog
--- openvswitch-2.10.0+2018.08.28+git.8ca7c82b7d+ds1/debian/changelog   
2019-03-31 00:50:26.0 +0100
+++ openvswitch-2.10.0+2018.08.28+git.8ca7c82b7d+ds1/debian/changelog   
2019-04-14 00:25:19.0 +0200
@@ -1,3 +1,10 @@
+openvswitch (2.10.0+2018.08.28+git.8ca7c82b7d+ds1-12) unstable; urgency=medium
+
+  * Add --may-exist in debian/ifupdown.sh as per upstream commit. Without it,
+networking service may fail (Closes: #926942).
+
+ -- Thomas Goirand   Sun, 14 Apr 2019 00:25:19 +0200
+
 openvswitch (2.10.0+2018.08.28+git.8ca7c82b7d+ds1-11) unstable; urgency=medium
 
   * Removes network.service from openvswitch-switch.service to avoid a
diff -Nru openvswitch-2.10.0+2018.08.28+git.8ca7c82b7d+ds1/debian/ifupdown.sh 
openvswitch-2.10.0+2018.08.28+git.8ca7c82b7d+ds1/debian/ifupdown.sh
--- openvswitch-2.10.0+2018.08.28+git.8ca7c82b7d+ds1/debian/ifupdown.sh 
2019-03-31 00:50:26.0 +0100
+++ openvswitch-2.10.0+2018.08.28+git.8ca7c82b7d+ds1/debian/ifupdown.sh 
2019-04-14 00:25:19.0 +0200
@@ -67,7 +67,7 @@
 ip link set "${IFACE}" up
 ;;
 OVSBond)
-ovs_vsctl -- --fake-iface add-bond "${IF_OVS_BRIDGE}"\
+ovs_vsctl -- --fake-iface --may-exist add-bond 
"${IF_OVS_BRIDGE}"\
 "${IFACE}" ${IF_OVS_BONDS} ${IF_OVS_OPTIONS} \
 ${OVS_EXTRA+-- $OVS_EXTRA}
 

Bug#926915: RFS: fossology/3.5.0-1 [ITP] -- OSS license compliance tool

[Andrey Rahmatullin]

On Mon, Apr 15, 2019 at 06:40:41AM +, Mishra, Gaurav wrote:
> FOSSology currently supports Debian Jessie and Stretch both. And Jessie still 
> have a year left to meet its end of life that is the reason we still support 
> it. And that is the reason php5-cli is still there.
Please keep in the official packages only stuff needed by the official
packages.
You will need to maintain a separate changelog anyway.

> And for Stretch, we have added the regex `php5-cli|php7.0-cli|php7.2-cli` in 
> the control file.
It's not a regex. And only the first alternative is considered by the
official buildds.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#927106: thunderbird: cannot find calender and todo/event-list icon in the new update

[Abhijith PA]

Package: thunderbird
Version: 1:60.6.1-1
Severity: important

Hello, after updating. I couldn't find the calendar and event list icons
in thunderbird. It used to be in right corner. I have enabled my
'lighting' calender add on.

--abhijith.

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

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

Versions of packages thunderbird depends on:
ii  debianutils   4.8.6.1
ii  fontconfig2.13.1-2
ii  libatk1.0-0   2.30.0-2
ii  libc6 2.28-8
ii  libcairo-gobject2 1.16.0-4
ii  libcairo2 1.16.0-4
ii  libdbus-1-3   1.12.12-1
ii  libdbus-glib-1-2  0.110-4
ii  libevent-2.1-62.1.8-stable-4
ii  libffi6   3.2.1-9
ii  libfontconfig12.13.1-2
ii  libfreetype6  2.9.1-3
ii  libgcc1   1:8.3.0-6
ii  libgdk-pixbuf2.0-02.38.1+dfsg-1
ii  libglib2.0-0  2.58.3-1
ii  libgtk-3-03.24.5-1
ii  libgtk2.0-0   2.24.32-3
ii  libhunspell-1.7-0 1.7.0-2
ii  libicu63  63.1-6
ii  libjsoncpp1   1.7.4-3
ii  libnspr4  2:4.20-1
ii  libnss3   2:3.42.1-1
ii  libpango-1.0-01.42.4-6
ii  libsqlite3-0  3.27.2-2
ii  libstartup-notification0  0.12-6
ii  libstdc++68.3.0-6
ii  libvpx5   1.7.0-3
ii  libx11-6  2:1.6.7-1
ii  libx11-xcb1   2:1.6.7-1
ii  libxcb-shm0   1.13.1-2
ii  libxcb1   1.13.1-2
ii  libxext6  2:1.3.3-1+b2
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1+b3
ii  psmisc23.2-1
ii  x11-utils 7.7+4
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages thunderbird recommends:
ii  hunspell-en-us [hunspell-dictionary]  1:2018.04.16-1
ii  lightning 1:60.6.1-1

Versions of packages thunderbird suggests:
ii  apparmor  2.13.2-10
pn  fonts-lyx 
ii  libgssapi-krb5-2  1.17-2

-- no debconf information

Bug#926915: RFS: fossology/3.5.0-1 [ITP] -- OSS license compliance tool

[Mishra, Gaurav]

Hello Adam,

FOSSology currently supports Debian Jessie and Stretch both. And Jessie still 
have a year left to meet its end of life that is the reason we still support 
it. And that is the reason php5-cli is still there.

And for Stretch, we have added the regex `php5-cli|php7.0-cli|php7.2-cli` in 
the control file.

Thanks and Regards,
Gaurav Mishra

From: Adam Borowski 
Sent: 14 April 2019 03:14
To: Mishra, Gaurav (IOT DS AA DTS CNP CT); 926...@bugs.debian.org
Subject: Re: Bug#926915: RFS: fossology/3.5.0-1 [ITP] -- OSS license compliance 
tool

On Fri, Apr 12, 2019 at 06:59:12AM +, Mishra, Gaurav wrote:
> Package name: fossology
> Version : 3.5.0-1

Alas, it fails to build: it build-depends on php5-cli which is gone for two
releases already (was in jessie, your package can get to bullseye at the
soonest).


[I won't likely be reviewing this package any further, though -- web stuff
is not my strength.]

Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Did ya know that typing "test -j8" instead of "ctest -j8"
⢿⡄⠘⠷⠚⠋⠀ will make your testsuite pass much faster, and fix bugs?
⠈⠳⣄

Bug#927104: criu: Please update to python3

[Salvatore Bonaccorso]

Control: tags -1 + confirmed

On Mon, Apr 15, 2019 at 02:14:22AM -0400, Scott Kitterman wrote:
> Package: criu
> Version: 3.11-2
> Severity: important
> 
> Python2.7 will go out of upstream security support during the Bullseye
> development cycle.  It is not safe to assume it will be included in the
> next release, so if you want to be sure criu can stay in Debian, please
> update it to the python3 version available from upstream..
> 
> Personally, I want to remove some packages I maintain, particularly python-
> ipaddr, which criu depends on during the Bullseye cycle, regardless of what
> happens to python2.7, so please update (python3 includes the ipaddress module,
> which was developed from ipaddr, in the standard library).

Thanks, indeed we should switch to use python3 in criu. Will try to do
that early during the Bullseye cycle or before so to at least on my
end not block you from removing python-ipaddr.

Regards,
Salvatore

Bug#914591: stretch-pu: package python-cryptography/1.7.1-3

[Sebastian Andrzej Siewior]

On 2019-04-14 21:08:46 [+0100], Adam D. Barratt wrote:
> On Sun, 2018-11-25 at 13:49 +0100, Sebastian Andrzej Siewior wrote:
> > With the intention of pushing OpenSSL 1.1.0j into Stretch here is the
> > proposed change for python-cryptography.
> > The package python-cryptography fails to build due to an API change
> > of BIO_callback_ctrl() in OpenSSL. While this is a no-no in a stable
> > release, it has been explained [0] that the function / callback was
> > always used with a different prototype. I fixed this by removing the
> > function / prototype from the python wrapper while upstream removed
> > the almost all BIO related wrappers [1].
> > I did a rebuild of python-cryptography's rdeps in Stretch against
> > OpenSSL 1.1.0i and the proposed package with no fallout [2].
> 
> Just to be 100% sure on the scope here, those rebuilds were just for
> confirmation? i.e. they are not required if we go ahead.

Excatly. I just wanted to makes sure that this change (this update of
python-cryptography) did not break any of its users / reverse
dependecies.

> Regards,
> 
> Adam

Sebastian

Bug#926624: Please drop Recommends against ibus-qt4

[Laurent Bigonville]

Le 14/04/19 à 20:33, Osamu Aoki a écrit :

On Mon, Apr 08, 2019 at 08:22:32AM +0200, Laurent Bigonville wrote:

Package: ibus
Version: 1.5.19-4
Severity: normal

Hi,

Apparently, ibus-qt4 has been removed from the archive.

Please drop the Recommends against that package

If RM agree to accept package, this is a good idea.

Do you know?

Osamu

PS: Except for cosmetic problem, this doesn't cause problem I think.
 Maybe system with old QT4 apps may be better off this way.

Indeed, it's just cosmetic. Just that it might prevent the auto-removal 
of QT4 packages on user's systems when upgrading from stretch to buster.


Not sure if that warrants to bother the release team about that though

Bug#927105: pinentry-gnome3: No proper curses fallback.

[Zephaniah E. Loss-Cutler-Hull]

Package: pinentry-gnome3
Version: 1.1.0-1+b1
Severity: normal

When using a standard gnome session, all invocations of pinentry-gnome3 
attempt to prompt via a GUI popup on that session, even if the specific 
instance has no DISPLAY set.


As an example use case, you boot your system, login to your gnome 
session, and then leave the house, realize you need something, and ssh 
home.  Then you proceed to try and decrypt a file with gpg.


No DISPLAY is set, but at this point everything fails, pinentry-gnome3 
tries to prompt on the desktop, and since you're not at the desktop, you 
can't use gpg.


If you are instead using pinentry-gtk-2 it correctly detects that you 
don't have a DISPLAY, and falls back to the curses interface.


Looking at the code, it sure looks like it tries to handle this, by 
checking to see if there is a DBUS_SESSION_BUS_ADDRESS (which there is, 
inherited from the gpg-agent), if a gcr system prompt is available, and 
trying to see if the screen is locked, however in my testing none of 
these actually seem to work to detect that, indeed, the screen is locked 
and the user isn't at the desktop any more.


To me the obvious solution is to also check and see if there is a 
display set, using the same logic as pinentry-gtk-2, I have some fear 
that this will break a pure wayland environment (one with no xwayland 
involved), however I don't actually have one of those handy to test 
with.  If someone with a wayland environment could test this that would 
be appreciated.


A proposed patch which works for me is attached.

(Note: It's hard to tell if some of the reports in #801247 would be 
fixed by this patch or not, there seems to be multiple issues going on 
in there.)


Regards,
Zephaniah E. Loss-Cutler-Hull.
Description: Check for a DISPLAY for pinentry-gnome3.
 With pinentry-gnome3, it will attempt to unconditionally prompt on the
 session's GUI for all cases, even if the actual session trying to decrypt
 something has no DISPLAY set.
 .
 This can break horribly when, for example, you ssh into your box and try to
 decrypt something with ssh.
 .
 The gtk2 varient handles this gracefully, and so we should too.
Author: Zephaniah E. Loss-Cutler-Hull 

---
The information above should follow the Patch Tagging Guidelines, please
checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:

Origin: , 
Bug: 
Bug-Debian: https://bugs.debian.org/
Bug-Ubuntu: https://launchpad.net/bugs/
Forwarded: 
Reviewed-By: 
Last-Update: 2019-04-15

--- pinentry-1.1.0.orig/gnome3/pinentry-gnome3.c
+++ pinentry-1.1.0/gnome3/pinentry-gnome3.c
@@ -518,7 +518,13 @@ main (int argc, char *argv[])
   pinentry_init (PGMNAME);
 
 #ifdef FALLBACK_CURSES
-  if (!getenv ("DBUS_SESSION_BUS_ADDRESS"))
+  if (!pinentry_have_display (argc, argv))
+{
+  fprintf (stderr, "No display found, falling back to curses\n");
+  pinentry_cmd_handler = curses_cmd_handler;
+  pinentry_set_flavor_flag ("curses");
+}
+  else if (!getenv ("DBUS_SESSION_BUS_ADDRESS"))
 {
   fprintf (stderr, "No $DBUS_SESSION_BUS_ADDRESS found,"
" falling back to curses\n");

Bug#927100: bley: Please port to python3

[Scott Kitterman]

On Mon, 15 Apr 2019 02:00:36 -0400 Scott Kitterman  
wrote:
> Package: bley
> Version: 2.0.0-2
> Severity: important
> 
> Python2.7 will go out of upstream security support during the Bullseye
> development cycle.  It is not safe to assume it will be included in the
> next release, so if you want to be sure bley can stay in Debian, please port
> it to python3.
> 
> Personally, I want to remove some packages I maintain, particularly python-
> ipaddr, which bley depends on during the Bullseye cycle, regardless of what
> happens to python2.7, so please update (python3 includes the ipaddress 
module,
> which was developed from ipaddr, in the standard library).

I also plan to remove python-spf (python3-spf has been available for several 
releases).  Yet another reason for bley to move to python3.

Scott K

Bug#927104: criu: Please update to python3

[Scott Kitterman]

Package: criu
Version: 3.11-2
Severity: important

Python2.7 will go out of upstream security support during the Bullseye
development cycle.  It is not safe to assume it will be included in the
next release, so if you want to be sure criu can stay in Debian, please
update it to the python3 version available from upstream..

Personally, I want to remove some packages I maintain, particularly python-
ipaddr, which criu depends on during the Bullseye cycle, regardless of what
happens to python2.7, so please update (python3 includes the ipaddress module,
which was developed from ipaddr, in the standard library).

Bug#926625: Please drop the Recommends against libqt5gui5

[Laurent Bigonville]

Le 14/04/19 à 20:30, Osamu Aoki a écrit :

Hi,


On Mon, Apr 08, 2019 at 08:37:20AM +0200, Laurent Bigonville wrote:

Package: ibus
Version: 1.5.19-4
Severity: wishlist

Hi,

Could you please remove the Recommends against libqt5gui5?

My rational is, if I'm correct, that any package that require QT5 will
already depend against this package making this dependency redundant and
forcing QT5 libraries on desktops not using QT (GNOME,...)

I think this is bad idea.

If Qt apps are used without this, then xim based input causes lost key
stroke etc.  Qt apps are not only for KDE people.  QCAD, ...


Like I said, as far as I can see, almost all packages that are using Qt 
and have a GUI are already pulling libqt5gui5:


bigon@fornost:~$ apt-cache rdepends libqt5core5a |grep -v -E '\|'|grep 
-v -E '^ *lib'|grep -v 'python'| sort -u|wc -l

1026
bigon@fornost:~$ apt-cache rdepends libqt5gui5 |grep -v -E '\|'|grep -v 
-E '^ *lib'|grep -v 'python'| sort -u|wc -l

906

So in the big majority of the cases, libqt5gui5 will be installed at the 
same time the application is installed. The remaining packages seem to 
be CLI, daemons or plugins, so no GUI.



You are saving tiny disk space.

Also this is recommend.  You can override.


The problem is that the last upload (in experimental, so this is not 
really a concern for buster) of gnome-shell recommends ibus. That means 
that you are pulling Qt libraries when you are installing a default 
GNOME desktop, which is not nice (tasksel is enabling the Recommends by 
default)


On a default installation with the task-desktop and task-desktop-gnome 
installed:


# apt-get install libqt5gui5
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  libdouble-conversion1 libpcre2-16-0 libqt5core5a libqt5dbus5 libqt5network5 
libqt5svg5 libqt5widgets5 libxcb-xinerama0 qt5-gtk-platformtheme 
qttranslations5-l10n
Suggested packages:
  qt5-image-formats-plugins qtwayland5
The following NEW packages will be installed:
  libdouble-conversion1 libpcre2-16-0 libqt5core5a libqt5dbus5 libqt5gui5 
libqt5network5 libqt5svg5 libqt5widgets5 libxcb-xinerama0 qt5-gtk-platformtheme 
qttranslations5-l10n
0 upgraded, 11 newly installed, 0 to remove and 3 not upgraded.
Need to get 10.1 MB of archives.
After this operation, 42.5 MB of additional disk space will be used.

That's 43MB extra



Regards,

Osamu

Bug#927102: EFI bootloader setup problems after installation using calamares

[Steve McIntyre]

Package: calamares-settings-debian
Version: 10.0.18-1
Severity: normal

[ I'm guessing as to the right package for this bug report, please
  reassign as appropriate! ]

Hi Jonathan,

I've just tested an installation using calamares from the latest
weekly live build (13th April, amd64, xfce). The installation went
well and worked ok for me in a qemu/kvm VM, but the bootloader setup
that it left behind is a little buggy - it looks like it's maybe(?)
just inheriting the setup directly from the live image. After booting
the installed system and looking in /boot/efi, I can see:

1. We have all the signed packages installed, which is good - yay!

However:

2. It has a copy of the (signed) grub bootloader in
   /boot/efi/EFI/boot/bootx64.efi (i.e. the removable media path),
   which is not ideal for a number of reasons:

   a) Debian does not default to putting anything there on *installed*
  systems, only on installer media. I'd prefer to keep things that
  way...

   b) We do have an option in our grub packages to *also* install to
  the removable media path (e.g. for people plagued by broken
  firmware which won't boot otherwise), but that has not been set
  in the debconf database on this installed system.

  That means this installed file is basically orphaned: it won't
  ever be upgraded on the installed system by default. This can
  cause problems down the line as and when Grub change might cause
  incompatibility and unexpected boot failure.

   c) If this setup is deliberate, it also won't work with Secure Boot
  - we'd need shim installed to the removable media path instead,
  and then:
  i)  this signed grub binary as grubx64.efi in the same directory
  instead, ready to be chainloaded by shim
  ii) a grub.cfg in /boot/efi/EFI/boot/debian/grub.cfg with config
  to find the real grub.cfg. I can see a "Debian" directory
  with a grub.cfg (capital D) which *might* work, but for
  maximum compatibility this should probably be lower case

This is just a brain dump for now - happy to talk about this more when
we're both online. EFI bootloader setup with SB can get a bit
involved... :-)

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

Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN
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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages calamares-settings-debian depends on:
pn  calamares
ii  cryptsetup   2:2.1.0-2
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  keyutils 1.6-6
ii  qml-module-qtquick-window2   5.11.3-4
ii  qml-module-qtquick2  5.11.3-4

calamares-settings-debian recommends no packages.

calamares-settings-debian suggests no packages.

Bug#927103: RM: blockfinder -- RoQA; Orphaned three years, uses obsolete libraries (python2.7), dead upstream

[Scott Kitterman]

Package: ftp.debian.org
Severity: normal

Note: This shouldn't be done until after Buster releases.  Python2.7 is
supported in Buster and there are no significant bugs that would suggest the
package shouldn't be in Buster.

Scott K

Bug#927101: automx: Please update to python3

[Scott Kitterman]

Package: automx
Version: 0.10.0-2.1
Severity: important

Python2.7 will go out of upstream security support during the Bullseye
development cycle.  It is not safe to assume it will be included in the
next release, so if you want to be sure automx can stay in Debian, please
update it to the python3 version available from upstream..

Personally, I want to remove some packages I maintain, particularly python-
ipaddr, which bley depends on during the Bullseye cycle, regardless of what
happens to python2.7, so please update (python3 includes the ipaddress module,
which was developed from ipaddr, in the standard library).

Bug#927100: bley: Please port to python3

[Scott Kitterman]

Package: bley
Version: 2.0.0-2
Severity: important

Python2.7 will go out of upstream security support during the Bullseye
development cycle.  It is not safe to assume it will be included in the
next release, so if you want to be sure bley can stay in Debian, please port
it to python3.

Personally, I want to remove some packages I maintain, particularly python-
ipaddr, which bley depends on during the Bullseye cycle, regardless of what
happens to python2.7, so please update (python3 includes the ipaddress module,
which was developed from ipaddr, in the standard library).

Scott K

Bug#927092: release-notes: document removal of ipsec-tools in buster

[Andrei POPESCU]

control -1 moreinfo

On Du, 14 apr 19, 19:00:04, Noah Meyerhans wrote:
> Package: release-notes
> Severity: normal
> 
> Ipsec-tools has been removed from buster. As a security-sensitive package,
> active upstream involvement is essential for this package, but it has been
> lacking for some time.

Would you mind elaborating a bit on this part? It would help to come up 
with an adequate entry explaining the issue without stepping on anyone's 
toes.

> Users are encouraged to migrate to Libreswan, which has
> broader protocol compatibility and an active upstream.

Is Libreswan a drop-in replacement or is a migration necessary? In case 
of a migration, is it possible to describe it in a few sentences and 
maybe point to some other resource (e.g. a wiki)?

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Bug#927059: [Pkg-javascript-devel] Bug#927059: npm: npm npm does not support Node.js v10.15.2

[Janusz S. Bień]

On Sun, Apr 14 2019 at 19:21 +02, Jérémy Lal wrote:
> Le dim. 14 avr. 2019 à 14:33, Janusz S. Bień  a écrit :

[...]

> I doubt the issue is with npm in debian.
> Using npm 6.9.0:
> npm install biiif
> does not install a "biiif" executable in node_modules/.bin
>
> In my opinion the problem comes from the software you're trying to use, not 
> from here.
> Please lower the severity.

[...]

> https://github.com/edsilv/biiif
> does not distribute an executable.
>
> biiif-cli does.

Thank you very much for your tests.

Best regards

Janusz

P.S. I was unable to install biiif, but this is a separate problem.

-- 
 ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

Bug#927077: plymouth: futureprototype theme has no feedback when performing system updates

[Laurent Bigonville]

reassign 927077 desktop-base 10.0.0
affects 927077 plymouth
thanks

Le 14/04/19 à 22:14, Andrew Hayzen a écrit :

When using the new futureprototype plymouth theme, there is no feedback
to the user of any offline updates being applied.

With other plymouth themes (eg spinner) when offline systemd updates
occur text appears in the top left corner with "Installing updates...
NN%" etc. This is useful to the user as they are then informed that the
system is doing something and has not blocked.

I think this is a bug in the theme itself, reassigning

Bug#927068: stretch-pu: package vcftools/0.1.14+dfsg-4+deb9u1

[Dylan Aïssi]

Le dim. 14 avr. 2019 à 20:56, Adam D. Barratt
 a écrit :
>
> Please go ahead.
>

Thanks, uploaded!

Best,
Dylan

Bug#907907: golang-google-cloud: FTBFS randomly (failing tests)

[Stephen Gelman]

FYI, unblock request filed as #927099.

Stephen

Bug#927098: unblock: node-serve-static/1.6.4-3

[Xavier Guimard]

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

Please unblock package node-serve-static

Hi all,

due to dependency upgrade and lack of autopkgtest real test,
node-serve-static has not been upgraded and has a little bug with recent
node-send. To avoid upgrade, I just disable the relevant test. The bug
is limited: node-serve-static returns 500 instead of 404 if a redirection
is activated in configuration and disabled in options.
I also updated debian/* files.

Reverse dependency: node-express

Since no installed files are modified but only tests, I think it is not
risky to unblock node-serve-static.

Full changes:
  * Disable one failing test (Closes: #927015)
  * Enable upstream test in autopkgtest using pkg-js-tools
  * Declare compliance with policy 4.3.0
  * Change section to javascript
  * Change priority to optional
  * Fix VCS fields
  * Fix debian/copyright format URL
  * Add upstream/metadata

Cheers,
Xavier

unblock node-serve-static/1.6.4-3

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

Kernel: Linux 4.19.0-4-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff --git a/debian/changelog b/debian/changelog
index 364c416..83ce702 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,17 @@
+node-serve-static (1.6.4-3) unstable; urgency=medium
+
+  * Team upload
+  * Disable one failing test (Closes: #927015)
+  * Enable upstream test in autopkgtest using pkg-js-tools
+  * Declare compliance with policy 4.3.0
+  * Change section to javascript
+  * Change priority to optional
+  * Fix VCS fields
+  * Fix debian/copyright format URL
+  * Add upstream/metadata
+
+ -- Xavier Guimard   Mon, 15 Apr 2019 07:05:03 +0200
+
 node-serve-static (1.6.4-2) unstable; urgency=medium
 
   * Team upload.
@@ -43,4 +57,3 @@ node-serve-static (1.1.0-1) unstable; urgency=low
   * Initial release (Closes: #746231)
 
  -- Leo Iannacone   Mon, 28 Apr 2014 12:10:16 +0200
-
diff --git a/debian/control b/debian/control
index 7cfb377..e7029c1 100644
--- a/debian/control
+++ b/debian/control
@@ -1,8 +1,9 @@
 Source: node-serve-static
-Section: web
-Priority: extra
+Section: javascript
+Priority: optional
 Maintainer: Debian Javascript Maintainers 

 Uploaders: Leo Iannacone 
+Testsuite: autopkgtest-pkg-nodejs
 Build-Depends:
  debhelper (>= 8)
  , dh-buildinfo
@@ -14,11 +15,11 @@ Build-Depends:
  , node-should
  , node-mocha
  , node-supertest
-Standards-Version: 3.9.6
+ , pkg-js-tools
+Standards-Version: 4.3.0
+Vcs-Browser: https://salsa.debian.org/js-team/node-serve-static
+Vcs-Git: https://salsa.debian.org/js-team/node-serve-static.git
 Homepage: https://github.com/expressjs/serve-static
-Vcs-Git: git://anonscm.debian.org/pkg-javascript/node-serve-static.git
-Vcs-Browser: 
http://anonscm.debian.org/gitweb/?p=pkg-javascript/node-serve-static.git
-XS-Testsuite: autopkgtest
 
 Package: node-serve-static
 Architecture: all
diff --git a/debian/copyright b/debian/copyright
index 05cefc2..506bff4 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -1,4 +1,4 @@
-Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
 Upstream-Name: serve-static
 Upstream-Contact: https://github.com/expressjs/serve-static/issues
 Source: https://github.com/expressjs/serve-static
@@ -34,4 +34,3 @@ License: Expat
  ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
  CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
  SOFTWARE.
-
diff --git a/debian/patches/disable-failing-test.diff 
b/debian/patches/disable-failing-test.diff
new file mode 100644
index 000..59b6b09
--- /dev/null
+++ b/debian/patches/disable-failing-test.diff
@@ -0,0 +1,28 @@
+Description: Disable failing test
+ Due to node-send update, node-serve-static now returns a 500 code instead
+ of 404 on redirect conflict.
+ .
+ Upgrade is not possible for now due to Buster freeze.
+Author: Xavier Guimard 
+Bug-Debian: https://bugs.debian.org/927015
+Forwarded: not-needed
+Last-Update: 2019-04-15
+
+--- a/test/test.js
 b/test/test.js
+@@ -272,6 +272,7 @@
+   .expect(404, done)
+ })
+ 
++/*
+ describe('when false', function () {
+   var server;
+   before(function () {
+@@ -284,6 +285,7 @@
+ .expect(404, done)
+   })
+ })
++*/
+   })
+ 
+   describe('setHeaders', function () {
diff --git a/debian/patches/series b/debian/patches/series
index 3181459..313a2c7 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1 +1,2 @@
 CVE-2015-1164.patch
+disable-failing-test.diff
diff --git a/debian/rules b/debian/rules

Bug#927099: unblock: golang-google-cloud/0.9.0-10

[Stephen Gelman]

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

Please unblock package golang-google-cloud

Fixes intermittent FTBFS (tests that fail more than 90% of the time).
More info in bug #907907

unblock golang-google-cloud/0.9.0-10

Thanks!

Stephen


diff -Nru golang-google-cloud-0.9.0/debian/changelog 
golang-google-cloud-0.9.0/debian/changelog
--- golang-google-cloud-0.9.0/debian/changelog  2019-02-06 19:02:17.0 
-0600
+++ golang-google-cloud-0.9.0/debian/changelog  2019-04-14 23:59:37.0 
-0500
@@ -1,3 +1,11 @@
+golang-google-cloud (0.9.0-10) unstable; urgency=medium
+
+  * Team upload.
+  * Skip very flaky test (Closes: #907907)
+Thanks to Santiago Vila for the patch
+
+ -- Stephen Gelman   Sun, 14 Apr 2019 23:59:37 -0500
+
 golang-google-cloud (0.9.0-9) unstable; urgency=high

   * Team upload.
diff -Nru golang-google-cloud-0.9.0/debian/patches/0012-skip-flaky-test.patch 
golang-google-cloud-0.9.0/debian/patches/0012-skip-flaky-test.patch
--- golang-google-cloud-0.9.0/debian/patches/0012-skip-flaky-test.patch 
1969-12-31 18:00:00.0 -0600
+++ golang-google-cloud-0.9.0/debian/patches/0012-skip-flaky-test.patch 
2019-04-14 23:59:37.0 -0500
@@ -0,0 +1,18 @@
+From: Stephen Gelman 
+Date: Sun, 14 Apr 2019 23:57:00 -0500
+Subject: skip flaky test
+
+We are way behind on upstream so no benefit to filing a bug on this until we 
get there.
+
+Forwarded: no
+---
+--- a/bigtable/bttest/inmem_test.go
 b/bigtable/bttest/inmem_test.go
+@@ -30,6 +30,7 @@
+ )
+
+ func TestConcurrentMutationsReadModifyAndGC(t *testing.T) {
++  t.Skip("test is extremely flaky")
+   s := &server{
+   tables: make(map[string]*table),
+   }
diff -Nru golang-google-cloud-0.9.0/debian/patches/series 
golang-google-cloud-0.9.0/debian/patches/series
--- golang-google-cloud-0.9.0/debian/patches/series 2019-02-05 
02:10:24.0 -0600
+++ golang-google-cloud-0.9.0/debian/patches/series 2019-04-14 
23:54:44.0 -0500
@@ -9,3 +9,4 @@
 0009-bigtable-fix-client-changes.patch
 0010-profiler-add-createofflineprofile-mock.patch
 0011-spanner-fix-tests.patch
+0012-skip-flaky-test.patch

Bug#927097: unblock: simile-timeline/2.3.0+dfsg1-4

[Xavier Guimard]

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

Please unblock package simile-timeline

Hi all,

due to Japan's Era change, simile-timeline has to be updated (#927034).
I also updated debian files without changes on installed files, except
new era of course. Full changes:

  * Add Japan's new Reiwa area (Closes: #927034)
  * Ignore some lintian false positive
  * Declare compliance with policy 4.3.0
  * Change section to javascript
  * Fix VCS fields
  * Switch debian/copyright to format 1.0
  * Update debian/watch to new repository
  * Add upstream/metadata

simile-timeline has one reverse dependency: debian-timeline which has no
reverse dependencies.

Since change is minimal on installed files, I think it is now risky to
update simile-timeline.

Cheers,
Xavier

unblock simile-timeline/2.3.0+dfsg1-4
diff --git a/debian/changelog b/debian/changelog
index a6a3f75..933bb5b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,24 @@
+simile-timeline (2.3.0+dfsg1-4) unstable; urgency=medium
+
+  * Team upload
+  * Fix error in reiwa.diff patch
+
+ -- Xavier Guimard   Sun, 14 Apr 2019 23:02:19 +0200
+
+simile-timeline (2.3.0+dfsg1-3) unstable; urgency=medium
+
+  * Team upload
+  * Add Japan's new Reiwa area (Closes: #927034)
+  * Ignore some lintian false positive
+  * Declare compliance with policy 4.3.0
+  * Change section to javascript
+  * Fix VCS fields
+  * Switch debian/copyright to format 1.0
+  * Update debian/watch to new repository
+  * Add upstream/metadata
+
+ -- Xavier Guimard   Sun, 14 Apr 2019 22:50:28 +0200
+
 simile-timeline (2.3.0+dfsg1-2) unstable; urgency=low
 
   * Re-upload to unstable.
diff --git a/debian/control b/debian/control
index f08bc6f..bd0fb56 100644
--- a/debian/control
+++ b/debian/control
@@ -1,13 +1,13 @@
 Source: simile-timeline
-Section: web
+Section: javascript
 Priority: optional
 Maintainer: Debian Javascript Maintainers 

 Uploaders: Chris Lamb , W. Martin Borgert 

 Build-Depends: debhelper (>= 7), ant, yui-compressor
-Standards-Version: 3.9.6
-Homepage: http://www.simile-widgets.org/
-Vcs-Browser: 
http://anonscm.debian.org/gitweb/?p=pkg-javascript/simile-timeline.git
-Vcs-Git: git://anonscm.debian.org/pkg-javascript/simile-timeline.git
+Standards-Version: 4.3.0
+Vcs-Browser: https://salsa.debian.org/js-team/simile-timeline
+Vcs-Git: https://salsa.debian.org/js-team/simile-timeline.git
+Homepage: https://www.simile-widgets.org/
 
 Package: libjs-simile-timeline
 Architecture: all
diff --git a/debian/copyright b/debian/copyright
index 5ac123f..f7095d8 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -1,21 +1,25 @@
-Author: David François Huynh 
-Download: http://www.simile-widgets.org/
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Upstream-Name: simile-ajax-bundle
+Upstream-Contact: David François Huynh 
+Source: https://github.com/simile-widgets/timeline
 
 Files: *
 Copyright: © 2006 The SIMILE Project 2006
-License: BSD
+License: BSD-3-Clause
 
-Files: timeline_ajax/simile-ajax-bundle.js
+Files: src/ajax/api/simile-ajax-bundle.js
 Copyright:
  © The SIMILE Project 2006. All rights reserved.
  © 2008 John Resig
-License: BSD / MIT / GPL
+License: BSD-3-Clause or Expat or GPL-2
+Comment: JQuery, www.jquery.com is included in the Ajax section of this
+ distribution. It is covered by its own license
 
 Files: debian/*
 Copyright: © 2009 Chris Lamb 
-License: GPL-3
+License: GPL-3+
 
-License: BSD
+License: BSD-3-Clause
  Redistribution and use in source and binary forms, with or without
  modification, are permitted provided that the following conditions
  are met:
@@ -40,24 +44,8 @@ License: BSD
  THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
  (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
  THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-License: GPL-3
- This program is free software: you can redistribute it and/or modify
- it under the terms of the GNU General Public License as published by
- the Free Software Foundation, either version 3 of the License, or
- (at your option) any later version.
- .
- This program is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
- GNU General Public License for more details.
- .
- You should have received a copy of the GNU General Public License
- along with this program.  If not, see .
- .
- On Debian systems the full text of the GPL-3 may be found in the file
- `/usr/share/common-licenses/GPL-3`.
 
-License: MIT
+License: Expat
  Permission is hereby granted, free of charge, to any person obtaining a copy
  of this software and associated documentation files (the "Software"), to deal
  in the Software without restriction, including without limitation the rights
@@ -75,3 +63,36 @@ License: MIT
  LIAB

Bug#927096: redmine/4.0.1-2

[duck]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-CC: Lucas Kanashiro 


Quack,

This is a follow-up on #923256. RC bugs were discovered and are now 
fixed (debdiff attached).


Please,
  unblock redmine/4.0.1-2

Regards.
\_o<

--
Marc Dequènesdiff -Nru redmine-4.0.1/debian/changelog redmine-4.0.1/debian/changelog
--- redmine-4.0.1/debian/changelog	2019-02-18 22:03:45.0 +0900
+++ redmine-4.0.1/debian/changelog	2019-04-15 12:47:36.0 +0900
@@ -1,3 +1,16 @@
+redmine (4.0.1-2) unstable; urgency=medium
+
+  * fix use_system_jquery_libs.patch (Closes: #923891):
++ avoid loading libs multiple times
++ correct event loading for JQuery 3
+  * conflicts with incompatible plugins (Closes: #923843):
++ redmine-plugin-pretend: unmaintained, no replacement
++ redmine-plugin-recaptcha: unmaintained, another fork may work
++ redmine-plugin-local-avatars: unmaintained, pending PR may work,
+see #924110
+
+ -- Marc Dequènes (Duck)   Mon, 15 Apr 2019 12:47:36 +0900
+
 redmine (4.0.1-1) unstable; urgency=medium
 
   [ Marc Dequènes (Duck) ]
diff -Nru redmine-4.0.1/debian/control redmine-4.0.1/debian/control
--- redmine-4.0.1/debian/control	2019-02-18 22:03:45.0 +0900
+++ redmine-4.0.1/debian/control	2019-04-15 12:45:55.0 +0900
@@ -78,6 +78,9 @@
  ${misc:Depends}
 Breaks: redmine-plugin-botsfilter (<=1.02-2),
 redmine-plugin-recaptcha (<=0.1.0+git20121018)
+Conflicts: redmine-plugin-pretend (<= 0.0.2+git20130821-4),
+   redmine-plugin-recaptcha (<= 0.1.0+git20121018-3),
+   redmine-plugin-local-avatars (<= 1.0.1-1)
 Recommends: passenger
 Suggests: bzr,
   cvs,
diff -Nru redmine-4.0.1/debian/patches/use_system_jquery_libs.patch redmine-4.0.1/debian/patches/use_system_jquery_libs.patch
--- redmine-4.0.1/debian/patches/use_system_jquery_libs.patch	2019-02-18 22:03:45.0 +0900
+++ redmine-4.0.1/debian/patches/use_system_jquery_libs.patch	2019-04-15 12:45:55.0 +0900
@@ -1,15 +1,14 @@
-Index: redmine/app/helpers/application_helper.rb
-===
 redmine.orig/app/helpers/application_helper.rb
-+++ redmine/app/helpers/application_helper.rb
-@@ -1502,7 +1502,9 @@ module ApplicationHelper
+--- a/app/helpers/application_helper.rb
 b/app/helpers/application_helper.rb
+@@ -1502,9 +1502,9 @@
  
# Returns the javascript tags that are included in the html layout head
def javascript_heads
 -tags = javascript_include_tag('jquery-1.11.1-ui-1.11.0-ujs-4.3.1', 'application', 'responsive')
-+tags = javascript_include_tag('jquery.min.js', 'application', 'responsive')
-+tags << javascript_include_tag('jquery_ujs.js', 'application', 'responsive')
-+tags << javascript_include_tag('jquery-ui.min.js', 'application', 'responsive')
++tags = javascript_include_tag('jquery.min.js', 'jquery-ui.min.js', 'jquery_ujs.js', 'application', 'responsive')
  unless User.current.pref.warn_on_leaving_unsaved == '0'
-   tags << "\n".html_safe + javascript_tag("$(window).load(function(){ warnLeavingUnsaved('#{escape_javascript l(:text_warn_on_leaving_unsaved)}'); });")
+-  tags << "\n".html_safe + javascript_tag("$(window).load(function(){ warnLeavingUnsaved('#{escape_javascript l(:text_warn_on_leaving_unsaved)}'); });")
++  tags << "\n".html_safe + javascript_tag("$(window).on('load', function(){ warnLeavingUnsaved('#{escape_javascript l(:text_warn_on_leaving_unsaved)}'); });")
  end
+ tags
+   end

Bug#907907: golang-google-cloud: FTBFS randomly (failing tests)

[Stephen Gelman]

> On Apr 14, 2019, at 4:04 PM, Santiago Vila  wrote:
> 
> Please, please, please, let us not release buster with packages
> failing randomly like this.

Santiago,

I agree with you that this should not ship with this issue in buster and will 
upload a new release with your patch (and then request an unblock).  Sorry for 
ignoring this bug for so long - I remember looking at this months ago but 
managed to forget about it.

Stephen

Bug#924110: redmine-plugin-local-avatars: fails to install: NoMethodError: undefined method `to_prepare' for ActionDispatch::Callbacks:Class

[duck]

Quack,

This PR may help:
  https://github.com/ncoders/redmine_local_avatars/pull/21
There is a typo though: s/prepere/prepare/

You may wish to give it a try. At the moment I'm going to add a conflict 
on the current version from the redmine package to avoid migration 
failures.


Regards.
\_o<

--
Marc Dequènes

Bug#927095: mediaconch FTCBFS: hard codes the build architecture pkg-config

[Helmut Grohne]

Source: mediaconch
Version: 18.03.2-1
Tags: patch upstream
User: helm...@debian.org
Usertags: rebootstrap

mediaconch fails to cross build from source, because its upstream build
system (both autoconf and qmake) hard code the build architecture
pkg-config rather than using the supplied one. Thus it fails finding
relevant libraries that are only requested for the host architecture by
Build-Depends. The attached patch fixes the relevant pkg-config
invocations in a minimal manner. For autotools, it would be better to
use the PKG_CHECK_MODULES_MACRO. Still the patch makes mediaconch cross
buildable. Please consider applying it as an incremental step with low
risk of breakage.

Helmut
--- mediaconch-18.03.2.orig/Project/GNU/CLI/configure.ac
+++ mediaconch-18.03.2/Project/GNU/CLI/configure.ac
@@ -28,6 +28,7 @@
 AC_PROG_CXX
 AC_PROG_INSTALL
 LT_INIT
+PKG_PROG_PKG_CONFIG
 
 dnl #
 dnl ### Options
@@ -74,8 +75,8 @@
 elif test "$(libzen-config Exists)" = "yes" ; then
 	enable_unicode="$(libzen-config Unicode)"
 else
-	if pkg-config --exists libzen; then
-		enable_unicode="$(pkg-config --variable=Unicode libzen)"
+	if $PKG_CONFIG --exists libzen; then
+		enable_unicode="$($PKG_CONFIG --variable=Unicode libzen)"
 	else
 		AC_MSG_ERROR([libzen configuration is not found])
 	fi
@@ -181,14 +182,14 @@
 			LIBS="$LIBS $(libmediainfo-config LIBS)"
 		fi
 	else
-		if pkg-config --exists lib$with_libmediainfo_name; then
-			CXXFLAGS="$CXXFLAGS $(pkg-config --cflags libmediainfo)"
+		if $PKG_CONFIG --exists lib$with_libmediainfo_name; then
+			CXXFLAGS="$CXXFLAGS $($PKG_CONFIG --cflags libmediainfo)"
 			if test "$enable_staticlibs" = "yes"; then
 with_mediainfolib="system (static)"
-LIBS="$LIBS $(pkg-config --variable=Libs_Static lib$with_libmediainfo_name)"
+LIBS="$LIBS $($PKG_CONFIG --variable=Libs_Static lib$with_libmediainfo_name)"
 			else
 with_mediainfolib="system"
-LIBS="$LIBS $(pkg-config --libs lib$with_libmediainfo_name)"
+LIBS="$LIBS $($PKG_CONFIG --libs lib$with_libmediainfo_name)"
 			fi
 		else
 			AC_MSG_ERROR([libmediainfo configuration is not found])
@@ -222,15 +223,15 @@
 		LIBS="$LIBS $(libzen-config LIBS)"
 	fi
 else
-	if pkg-config --exists libzen; then
-		CXXFLAGS="$CXXFLAGS $(pkg-config --cflags libzen)"
-		MediaInfoLib_CXXFLAGS="$MediaInfoLib_CXXFLAGS $(pkg-config --cflags libzen)"
+	if $PKG_CONFIG --exists libzen; then
+		CXXFLAGS="$CXXFLAGS $($PKG_CONFIG --cflags libzen)"
+		MediaInfoLib_CXXFLAGS="$MediaInfoLib_CXXFLAGS $($PKG_CONFIG --cflags libzen)"
 		if test "$enable_staticlibs" = "yes"; then
 			with_zenlib="system (static)"
-			LIBS="$LIBS $(pkg-config --variable=Libs_Static libzen)"
+			LIBS="$LIBS $($PKG_CONFIG --variable=Libs_Static libzen)"
 		else
 			with_zenlib="system"
-			LIBS="$LIBS $(pkg-config --libs libzen)"
+			LIBS="$LIBS $($PKG_CONFIG --libs libzen)"
 		fi
 	else
 		AC_MSG_ERROR([libzen configuration is not found])
@@ -251,25 +252,25 @@
 		LIBS="$LIBS  -L../../../../libxml2/.libs -lxml2"
 	fi
 else
-	if pkg-config --exists libxml2; then
-		CXXFLAGS="$CXXFLAGS $(pkg-config --cflags libxml2)"
-		MediaInfoLib_CXXFLAGS="$MediaInfoLib_CXXFLAGS $(pkg-config --cflags libxml2)"
+	if $PKG_CONFIG --exists libxml2; then
+		CXXFLAGS="$CXXFLAGS $($PKG_CONFIG --cflags libxml2)"
+		MediaInfoLib_CXXFLAGS="$MediaInfoLib_CXXFLAGS $($PKG_CONFIG --cflags libxml2)"
 		if test "$enable_staticlibs" = "yes"; then
 			with_libxml2="system (static)"
-			LIBS="$LIBS $(pkg-config --static --libs libxml2)"
+			LIBS="$LIBS $($PKG_CONFIG --static --libs libxml2)"
 		else
 			with_libxml2="system"
-			LIBS="$LIBS $(pkg-config --libs libxml2)"
+			LIBS="$LIBS $($PKG_CONFIG --libs libxml2)"
 		fi
-	elif pkg-config --exists libxml-2.0; then
-		CXXFLAGS="$CXXFLAGS $(pkg-config --cflags libxml-2.0)"
-		MediaInfoLib_CXXFLAGS="$MediaInfoLib_CXXFLAGS $(pkg-config --cflags libxml-2.0)"
+	elif $PKG_CONFIG --exists libxml-2.0; then
+		CXXFLAGS="$CXXFLAGS $($PKG_CONFIG --cflags libxml-2.0)"
+		MediaInfoLib_CXXFLAGS="$MediaInfoLib_CXXFLAGS $($PKG_CONFIG --cflags libxml-2.0)"
 		if test "$enable_staticlibs" = "yes"; then
 			with_libxml2="system (static)"
-			LIBS="$LIBS $(pkg-config --static --libs libxml-2.0)"
+			LIBS="$LIBS $($PKG_CONFIG --static --libs libxml-2.0)"
 		else
 			with_libxml2="system"
-			LIBS="$LIBS $(pkg-config --libs libxml-2.0)"
+			LIBS="$LIBS $($PKG_CONFIG --libs libxml-2.0)"
 		fi
 	else
 		AC_MSG_ERROR([libxml2 configuration is not found])
@@ -293,19 +294,19 @@
 		LIBS="$LIBS  -L../../../../libxslt/libexslt/.libs -lexslt"
 	fi
 else
-	if pkg-config --exists libxslt; then
-		CXXFLAGS="$CXXFLAGS $(pkg-config --cflags libxslt)"
-		CXXFLAGS="$CXXFLAGS $(pkg-config --cflags libexslt)"
-		MediaInfoLib_CXXFLAGS="$MediaInfoLib_CXXFLAGS $(pkg-config --cflags libxslt)"
-		MediaInfoLib_CXXFLAGS="$MediaInfoLib_CXXFLAGS $(pkg-config --cflags libexslt)"
+	if $PKG_CONFIG --exists libxslt; then
+		CXXFLAGS="$CXXFLAGS 

Bug#927094: upgrade-reports: Kaby Lake with GeForce 1030, "main" only is not practical. It does need "nvidia-driver", non-free.

[hoxp18]

Package: upgrade-reports
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: tester 
To: Debian Bug Tracking System 
Subject: upgrade-reports: Kaby Lake with GeForce 1030, "main" only is 
not practical. It does need "nvidia-driver", non-free.

Bcc: tester 

Package: upgrade-reports
Severity: normal

Dear Maintainer,

I did some tests on amd64 (Kaby Lake) machine,

With "main" section only, then add "non-free".

Summary
===

* Stretch clean install, LVM over LUKS on NVMe,
  separated file system, with AppArmor enabled.

* After GNOME and Firefox, etc settings' had done,
  Rewrote sources.list into buster and "apt dist-upgrade"

* No upgrade trouble. Boot normally, LVM over LUKS,
  AppArmor seems OK, though I did not test so much by now.

* Both PAM su restriction and securetty work.

* Problem around GNOME, nouveau, and especially Firefox.

* Sound output initial setting become on-board S/PDIF.
  Need to change to the GeForce 1030 one.

* LVM may have some issue; error logs appear.

* "nvidia-driver" makes ttys' resolutions worse.

* (logcheck summary) mails are okay,
  provided I fix the owner and permission on /var/mail.

dist-upgrade before-after
=

Firmware
* syslog says "Firmware Bug: TSC_DEADLINE disabled
  due to Errata; please update microcode to version:
  0.52 (or later)

  (cf. the CPU has no HT and VT features are off.)

LVM
* lvm2-activation-generator: lvmconfig failed.
  Activation generator failed.
  /lib/systemd/system-generators/lvm2-activation-generator
  failed with exit code 1.

nouveau
* firmware: failed to load nvidia/gp108/gr/sw_nonctx.bin (-2)
* DRM: failed to create kernel channel, -22

gnome-session-binary
* Unrecoverable failure in required component org.gnome.Shell.desktop

Video by GeForce 1030
* Stretch nouveau: low resolution.
  Buster: LCD max, 1920x1080.

AppArmor
* aa-enabled kept "Yes"

fstrim
* TRIM is okay on both cases.

exfat-fuse
* both okay; mounted automatically.

suspend-to-RAM and resume.
* both okay.

1st cold boot after the dist-upgrade


Video motion quality
* On the first cold boot after dist-upgrade,

* GDM shows slow response but recovers in 20 secs.
  Both mouse and keyboard response on GDM are bad,
  but once login, GNOME desktop itself is okay.

* Buster GNOME shows slow response with Firefox.
  Around 2-5 fps.

* "top" says "gnome-shell" consuming %CPU about 50%.

Sound
* Mozilla Firefox can barely browse Youtube
  except fps and sound initial settings.

  Sound setting became on-board, not GeForce.

  After changing from on-board S/PDIF to
  GP108 (GeForce 1030), it plays sound.

byobu(-terminal) on GNOME
* works fine; splitting, moving, there are no corruption.

byobu on ttys
* screen size small; it says "size 211x53 from a smaller
  client", w/ GeForce 1030 - HDMI - FullHD LCD.
  split, move, and rendering are okay.

  tty itself is FullHD size; right and bottom area are
  filled by purple dots "."

  status bar display is okay.

Misc.
* GNOME terminal shortcut option turned back ON.

2nd cold boot
=

Video motion quality

* GDM is same; slow.

* GNOME itself is okay.

* "gnome-shell" is still consuming %CPU, 30-100% always.

* Mozilla Firefox is especially heavy.
  It did not improved by simple reboot.

byobu
* GNOME terminal, it is okay.

* ttys got less display area;
  It says "size 80x23 from a smaller client".
  tty size is FullHD resolution,
  there are more purple "." filled area on
  right and bottom. status bar is fine.

with non-free packages
==

After the installation of "intel-microcode"
---

3rd cold boot.

* TSC_DEADLINE error log gone.

* lvm2-activation-generator fail log continued.

* GDM response improved.

* gnome-shell still consuming CPU.

* Firefox still slow.

After the installation of "nvidia-driver"
-

4th cold boot.

* GDM response improved more.

* GNOME desktop animation got more smooth.

* gnome-shell CPU consumption improved.

* Firefox is now FINE.
  It plays Youtube both in windows and full screen.
  Sound is okay.

* ttys resolution DECREASED; 800x600 now.

About This Report
=

Due to the desktop response troubles,
I did "reportbug upgrade-reports" after "nvidia-driver" installation.

Overall
===

I did not tested so much,
but I can say something around nouveau and/or gnome-shell
w/o non-free firmwares and drivers.

* LVM might have some issue on this LVM-over-LUKS.

* Maybe I should update BIOS, at least about microcode.

* "main" only, Firefox is not practical by nouveau.

* "byobu" seems funny at ttys in this GeForce 1030 box.

* "nvidia-driver" makes tty console resolution worse.

I will keep 4 cold boot syslogs.

If you are interested, please contact me.

Thank you, dear Debian team.

Regards.

-- Hardware and Filesystem Information:

Intel Core i5-7500 on Z270 M/B, with W

Bug#907907: golang-google-cloud: FTBFS randomly (failing tests)

[Santiago Vila]

severity 907907 serious
tags 907907 + patch
thanks

Hi.

I did a "grep FAIL:" on the build logs and found that there is a single
failing test which is to blame for most of the build failures, namely:

--- FAIL: TestConcurrentMutationsReadModifyAndGC (2.39s)

If the package is useful "as is" and it's not broken because of this
test failing randomly, then disabling it is the only sensible thing
to do.

By taking "0003-skip-random-failed-test" as an example, I believe
the patch below is the right way to disable it, and in fact after
applying the patch I see this in the build logs instead:

--- SKIP: TestConcurrentMutationsReadModifyAndGC (0.00s)

Additionally, I've setup a Jenkins job here so you can see the sorry
state of the package in its current version:

https://jenkins-1.reliable-builds.org/job/golang-google-cloud/

Please, please, please, let us not release buster with packages
failing randomly like this.

[ Note: If you still think the failing test should be debugged and not
  disabled for buster, please contact me privately and I will gladly
  offer a test machine where this happens a lot ].

Thanks.

--- a/bigtable/bttest/inmem_test.go
+++ b/bigtable/bttest/inmem_test.go
@@ -30,6 +30,7 @@ import (
 )
 
 func TestConcurrentMutationsReadModifyAndGC(t *testing.T) {
+   t.Skip("skip random failed tests")
s := &server{
tables: make(map[string]*table),
}

Bug#927093: the netstat plugin fails with current versions of netstat

[Marco d'Itri]

Package: munin-plugins-core
Version: 2.0.47-1
Severity: normal
Tags: upstream newcomer patch

The netstat plugin does not report anymore the value of active.value 
because the output of netstat has changed.

Pseudo-patch:

-/active connections ope/  { print "active.value " $1 }
+/active connections? ope/  { print "active.value " $1 }

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#926586: ublock-origin: separate packages for Firefox and Chromium may be necessary

[Paul Wise]

On Sun, 07 Apr 2019 13:46:33 +0200 Markus Koschany wrote:

> Upstream maintains the webext version of uBo because we asked him to
> do that. I assume it was to simplify the Debian packaging, creating
> one package that works for both browsers. This is obviously extra work
> for upstream. Now we have a situation where we can't work around the
> problem. The Firefox web browser does not support the ingocnito:split
> option while Chromium does. Upstream told me that the alternative
> option which is supported by both browsers, incognito:spanning,
> breaks Chromium for certain use cases.

PS: I think these incompatibilities should be communicated to the
Chromium and Firefox developers so they can do something about it.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#926586: ublock-origin: separate packages for Firefox and Chromium may be necessary

[Paul Wise]

On Sun, 07 Apr 2019 13:46:33 +0200 Markus Koschany wrote:

> Thoughts?

There is a better option for this:

Keep the one package but install a different manifest.json into the
Firefox and Chrome extension directories. This should work since
Firefox and Chrome look for their extensions in different directories.
The only issue with this workaround is that it involves instead of just
symlinking the directory, symlinking every file except manifest.json.
The per-browser manifest.json should probably be created at build time.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#927092: release-notes: document removal of ipsec-tools in buster

[Noah Meyerhans]

Package: release-notes
Severity: normal

Ipsec-tools has been removed from buster. As a security-sensitive package,
active upstream involvement is essential for this package, but it has been
lacking for some time. Users are encouraged to migrate to Libreswan, which has
broader protocol compatibility and an active upstream.

Thanks
noah

Bug#927082: a bit more info

[Alison Chaiken]

After rebooting, the occur recur:

$ sudo systemctl -l status ntp
[sudo] password for alison:
● ntp.service - Network Time Service
   Loaded: loaded (/lib/systemd/system/ntp.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Sun 2019-04-14 14:49:30 PDT; 3h 40min 
ago

 Docs: man:ntpd(8)
  Process: 596 ExecStart=/usr/lib/ntp/ntp-systemd-wrapper (code=exited, 
status=0/SUCCESS)

 Main PID: 615 (ntpd)
Tasks: 2 (limit: 4915)
   Memory: 2.5M
   CGroup: /system.slice/ntp.service
   └─615 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 119:126

Apr 14 15:07:46 bonnet ntpd[615]: Soliciting pool server 72.30.35.88
Apr 14 15:07:50 bonnet ntpd[615]: Soliciting pool server 199.180.133.100
Apr 14 15:29:18 bonnet ntpd[615]: receive: Unexpected origin timestamp 
0xe05e32bd.764ac9aa does not ma
Apr 14 15:41:44 bonnet ntpd[615]: receive: Unexpected origin timestamp 
0xe05e35a7.cd542580 does not ma
Apr 14 16:02:55 bonnet ntpd[615]: 54.236.224.171 local addr 
192.168.42.66 -> 

Apr 14 16:04:10 bonnet ntpd[615]: Soliciting pool server 64.147.157.6
Apr 14 17:35:37 bonnet ntpd[615]: receive: Unexpected origin timestamp 
0xe05e5058.5f1ad4a3 does not ma
Apr 14 18:18:04 bonnet ntpd[615]: receive: Unexpected origin timestamp 
0xe05e5a4b.747218e9 does not ma
Apr 14 18:18:04 bonnet ntpd[615]: receive: Unexpected origin timestamp 
0xe05e5a4b.74727efc does not ma
Apr 14 18:23:16 bonnet ntpd[615]: receive: Unexpected origin timestamp 
0xe05e5b83.40a6d698 does not ma


and in daemon.log:

Apr 14 18:36:42 bonnet ntpd[615]: receive: Unexpected origin timestamp 
0xe05e5ea9.93b21b00 does not match aorg 00. from 
server@69.89.207.199 xmt 0xe05e5eaa.bd3dca44
Apr 14 18:36:42 bonnet ntpd[615]: receive: Unexpected origin timestamp 
0xe05e5ea9.93b27b43 does not match aorg 00. from 
server@64.113.44.54 xmt 0xe05e5eaa.be924553


But as the above systemd output shows, ntpd is still running, and 
nothing this time has sent it a SIGTERM.


I also checked my laptop which is NAT'ed to the same router.   On that 
system, ntpd looks normal.   I have never (intentionally) modified any 
configuration related to NTP.


Thanks,
Alison Chaiken

---
Alison Chaiken   ali...@she-devel.com
http://she-devel.com
The real trolley problem is that trolleys are underfunded.  -- Alex Roy

Bug#583644: Uzenetkuldés jovahagyasa

[no-reply]

Tisztelt 583...@bugs.debian.org!

Adataink szerint Ön üzenetet kívánt küldeni a(z) kulcs.kepeslap.com oldal 
karbantartója számára.

Amennyiben Ön indította ezt a kérést, kérjük klikkeljen jóváhagyólag a 
következõ linkre:
http://kulcs.kepeslap.com/concon.asp?code=2191418X315ddad53031f42c1f64c3e09c7033b3

Amennyiben valaki rosszindulatúan az Ön nevében próbált meg üzenetet küldeni, 
nincs semmi teendõje: az üzenetet az Ön jóváhagyása nélkül nem továbbítjuk.



A kepeslap.com szolgáltatása.
A kepeslap.com nem vállal felelõsséget a képeslapok tartalmáért.
Lásd: http://www.kepeslap.com/info.asp
Refill Stúdió ingyenes nyílt nap december 7-én! Gyere el te is! 
http://goo.gl/AqoR9D 
---

Bug#927091: linux-image-5.0.0-trunk-amd64: Broken scrollwheel after upgrade

[Octavio Alvarez]

Package: src:linux
Version: 5.0.2-1~exp1
Severity: normal

Dear Maintainer,

After upgrading from 4.19 to 5.0 (experimental) the scrollwheel is
slow. It takes about 20 steps to get the equivalent of a single step
from 4.19.

The mouse is a USB Microsft Wireless Mobile Mouse 3000:

Bus 002 Device 003: ID 045e:00e1 Microsoft Corp. Wireless Laser Mouse
6000 Receiver

(Please find lsusb -vvv information after the evtest info for the mouse)

I tried solaar, imwheel, resetmsmice, none worked. I ran evtest in both
versions and did two steps down and then two steps up:

Version 4.19:
$ sudo evtest
[sudo] password for alvarezp:
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:  AT Translated Set 2 keyboard
/dev/input/event1:  Microsoft Microsoft Notebook Receiver v2.0 Consumer
Control
/dev/input/event2:  Microsoft Microsoft Notebook Receiver v2.0 Mouse
/dev/input/event3:  ETPS/2 Elantech Touchpad
/dev/input/event4:  PC Speaker
/dev/input/event5:  Lid Switch
/dev/input/event6:  Power Button
/dev/input/event7:  Sleep Button
/dev/input/event8:  Power Button
/dev/input/event9:  Video Bus
/dev/input/event10: HDA Intel MID Mic
/dev/input/event11: HDA Intel MID Headphone
/dev/input/event12: HDA Intel MID HDMI/DP,pcm=3
/dev/input/event13: USB 2.0 PC Camera: WebCam SCB-0
Select the device event number [0-13]: 2
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x45e product 0xe1 version 0x111
Input device name: "Microsoft Microsoft Notebook Receiver v2.0 Mouse"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
Event code 272 (BTN_LEFT)
Event code 273 (BTN_RIGHT)
Event code 274 (BTN_MIDDLE)
Event code 275 (BTN_SIDE)
Event code 276 (BTN_EXTRA)
  Event type 2 (EV_REL)
Event code 0 (REL_X)
Event code 1 (REL_Y)
Event code 6 (REL_HWHEEL)
Event code 8 (REL_WHEEL)
  Event type 4 (EV_MSC)
Event code 4 (MSC_SCAN)
Properties:
Testing ... (interrupt to exit)
Event: time 1555288252.603793, type 2 (EV_REL), code 8 (REL_WHEEL), value -1
Event: time 1555288252.603793, -- SYN_REPORT 
Event: time 1555288252.667781, type 2 (EV_REL), code 8 (REL_WHEEL), value -1
Event: time 1555288252.667781, -- SYN_REPORT 
Event: time 1555288253.275651, type 2 (EV_REL), code 8 (REL_WHEEL), value 1
Event: time 1555288253.275651, -- SYN_REPORT 
Event: time 1555288253.427623, type 2 (EV_REL), code 8 (REL_WHEEL), value 1
Event: time 1555288253.427623, -- SYN_REPORT 


5.0:

$ sudo evtest
[sudo] password for alvarezp:
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:  AT Translated Set 2 keyboard
/dev/input/event1:  Microsoft Microsoft Notebook Receiver v2.0 Consumer
Control
/dev/input/event2:  Microsoft Microsoft Notebook Receiver v2.0 Mouse
/dev/input/event3:  ETPS/2 Elantech Touchpad
/dev/input/event4:  Lid Switch
/dev/input/event5:  Power Button
/dev/input/event6:  Sleep Button
/dev/input/event7:  Power Button
/dev/input/event8:  PC Speaker
/dev/input/event9:  Video Bus
/dev/input/event10: HDA Intel MID Mic
/dev/input/event11: HDA Intel MID Headphone
/dev/input/event12: HDA Intel MID HDMI/DP,pcm=3
/dev/input/event13: USB 2.0 PC Camera: WebCam SCB-0
Select the device event number [0-13]: 2
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x45e product 0xe1 version 0x111
Input device name: "Microsoft Microsoft Notebook Receiver v2.0 Mouse"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
Event code 272 (BTN_LEFT)
Event code 273 (BTN_RIGHT)
Event code 274 (BTN_MIDDLE)
Event code 275 (BTN_SIDE)
Event code 276 (BTN_EXTRA)
  Event type 2 (EV_REL)
Event code 0 (REL_X)
Event code 1 (REL_Y)
Event code 6 (REL_HWHEEL)
Event code 8 (REL_WHEEL)
Event code 11 (?)
Event code 12 (?)
  Event type 4 (EV_MSC)
Event code 4 (MSC_SCAN)
Properties:
Testing ... (interrupt to exit)
Event: time 1555289094.577076, type 2 (EV_REL), code 11 (?), value -7
Event: time 1555289094.577076, -- SYN_REPORT 
Event: time 1555289094.841059, type 2 (EV_REL), code 11 (?), value -7
Event: time 1555289094.841059, -- SYN_REPORT 
Event: time 1555289095.273039, type 2 (EV_REL), code 11 (?), value 7
Event: time 1555289095.273039, -- SYN_REPORT 
Event: time 1555289095.481020, type 2 (EV_REL), code 11 (?), value 7
Event: time 1555289095.481020, -- SYN_REPORT 


lsusb -vvv information for this device:
Bus 002 Device 003: ID 045e:00e1 Microsoft Corp. Wireless Laser Mouse
6000 Receiver
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   2.00
  bDeviceClass0
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMa

Bug#927090: [ilwmvm] Recurent kernel panic crash at iwl_mvm_async_handlers_wk+0xba/0x160

[Simon Désaulniers]

Hi,

Something went wrong with `reportbug`. Here is the complete journal log attached
to this mail.

Regards,

-- 
Simon Désaulniers
sim.desaulni...@gmail.com
-- Logs begin at Fri 2019-02-08 12:50:34 EST, end at Sun 2019-04-14 19:59:22 
EDT. --
avr 12 22:18:32 haxorz kernel: thinkpad_acpi: battery 1 registered (start 0, 
stop 100)
avr 12 22:18:32 haxorz kernel: battery: new extension: ThinkPad Battery 
Extension
avr 12 22:18:32 haxorz kernel: input: ThinkPad Extra Buttons as 
/devices/platform/thinkpad_acpi/input/input8
avr 12 22:18:32 haxorz kernel: pstore: crypto_comp_decompress failed, ret = -22!
avr 12 22:18:32 haxorz kernel: pstore: decompression failed: -22
avr 12 22:18:32 haxorz kernel: pstore: crypto_comp_decompress failed, ret = -22!
avr 12 22:18:32 haxorz kernel: pstore: decompression failed: -22
avr 12 22:18:32 haxorz kernel: pstore: crypto_comp_decompress failed, ret = -22!
avr 12 22:18:32 haxorz kernel: checking generic (e000 7f) vs hw 
(e000 1000)
avr 12 22:18:32 haxorz kernel: fb: switching to inteldrmfb from EFI VGA
avr 12 22:18:32 haxorz kernel: pstore: decompression failed: -22
avr 12 22:18:32 haxorz kernel: Console: switching to colour dummy device 80x25
avr 12 22:18:32 haxorz kernel: pstore: crypto_comp_decompress failed, ret = -22!
avr 12 22:18:32 haxorz kernel: pstore: decompression failed: -22
avr 12 22:18:32 haxorz kernel: pstore: crypto_comp_decompress failed, ret = -22!
avr 12 22:18:32 haxorz kernel: pstore: decompression failed: -22
avr 12 22:18:32 haxorz kernel: pstore: crypto_comp_decompress failed, ret = -22!
avr 12 22:18:32 haxorz kernel: pstore: decompression failed: -22
avr 12 22:18:32 haxorz kernel: pstore: crypto_comp_decompress failed, ret = -22!
avr 12 22:18:32 haxorz kernel: pstore: decompression failed: -22
avr 12 22:18:32 haxorz kernel: pstore: crypto_comp_decompress failed, ret = -22!
avr 12 22:18:32 haxorz kernel: pstore: decompression failed: -22
avr 12 22:18:32 haxorz kernel: pstore: crypto_comp_decompress failed, ret = -22!
avr 12 22:18:32 haxorz kernel: pstore: decompression failed: -22
avr 12 22:18:32 haxorz kernel: pstore: crypto_comp_decompress failed, ret = -22!
avr 12 22:18:32 haxorz kernel: pstore: decompression failed: -22
avr 12 22:18:32 haxorz kernel: pstore: crypto_comp_decompress failed, ret = -22!
avr 12 22:18:32 haxorz kernel: pstore: decompression failed: -22
avr 12 22:18:32 haxorz kernel: pstore: crypto_comp_decompress failed, ret = -22!
avr 12 22:18:32 haxorz kernel: pstore: decompression failed: -22
avr 12 22:18:32 haxorz kernel: pstore: crypto_comp_decompress failed, ret = -22!
avr 12 22:18:32 haxorz kernel: pstore: decompression failed: -22
avr 12 22:18:32 haxorz kernel: pstore: crypto_comp_decompress failed, ret = -22!
avr 12 22:18:32 haxorz kernel: pstore: decompression failed: -22
avr 12 22:18:32 haxorz kernel: pstore: crypto_comp_decompress failed, ret = -22!
avr 12 22:18:32 haxorz kernel: pstore: decompression failed: -22
avr 12 22:18:32 haxorz kernel: pstore: crypto_comp_decompress failed, ret = -22!
avr 12 22:18:32 haxorz kernel: pstore: decompression failed: -22
avr 12 22:18:32 haxorz kernel: pstore: crypto_comp_decompress failed, ret = -22!
avr 12 22:18:32 haxorz kernel: pstore: decompression failed: -22
avr 12 22:18:32 haxorz kernel: pstore: crypto_comp_decompress failed, ret = -22!
avr 12 22:18:32 haxorz kernel: pstore: decompression failed: -22
avr 12 22:18:32 haxorz kernel: pstore: crypto_comp_decompress failed, ret = -22!
avr 12 22:18:32 haxorz kernel: pstore: decompression failed: -22
avr 12 22:18:32 haxorz kernel: pstore: crypto_comp_decompress failed, ret = -22!
avr 12 22:18:32 haxorz kernel: pstore: decompression failed: -22
avr 12 22:18:32 haxorz kernel: pstore: crypto_comp_decompress failed, ret = -22!
avr 12 22:18:32 haxorz kernel: pstore: decompression failed: -22
avr 12 22:18:32 haxorz kernel: pstore: crypto_comp_decompress failed, ret = -22!
avr 12 22:18:32 haxorz kernel: pstore: decompression failed: -22
avr 12 22:18:32 haxorz kernel: pstore: crypto_comp_decompress failed, ret = -22!
avr 12 22:18:32 haxorz kernel: pstore: decompression failed: -22
avr 12 22:18:32 haxorz kernel: pstore: crypto_comp_decompress failed, ret = -22!
avr 12 22:18:32 haxorz kernel: pstore: decompression failed: -22
avr 12 22:18:32 haxorz kernel: pstore: crypto_comp_decompress failed, ret = -22!
avr 12 22:18:32 haxorz kernel: pstore: decompression failed: -22
avr 12 22:18:32 haxorz kernel: pstore: crypto_comp_decompress failed, ret = -22!
avr 12 22:18:32 haxorz kernel: pstore: decompression failed: -22
avr 12 22:18:32 haxorz kernel: pstore: crypto_comp_decompress failed, ret = -22!
avr 12 22:18:32 haxorz kernel: pstore: decompression failed: -22
avr 12 22:18:32 haxorz kernel: pstore: crypto_comp_decompress failed, ret = -22!
avr 12 22:18:32 haxorz kernel: pstore: decompression failed: -22
avr 12 22:18:32 haxorz kernel: pstore: crypto_comp_decompress failed, ret = -22!
avr 12 22:18:32 haxorz kernel: pstore: decompression failed:

Bug#927090: [ilwmvm] Recurent kernel panic crash at iwl_mvm_async_handlers_wk+0xba/0x160

[Simon Désaulniers]

Package: src:linux
Version: 4.19.28-2
Severity: important
File: 
/lib/modules/4.19.0-4-amd64/kernel/drivers/net/wireless/intel/iwlwifi/mvm/iwlmvm.ko

Dear Maintainer,

I have been having recurrent kernel panic crashes with iwlmvm module. I can't
say how it happens. It seems random from my standpoint of view. Here is the
complete kernel crash backtrace:

avr 14 17:23:24 haxorz kernel: mmc0: cannot verify signal voltage switch
avr 14 17:23:24 haxorz kernel: e1000e: enp0s31f6 NIC Link is Down
avr 14 17:23:25 haxorz kernel: WARNING: CPU: 0 PID: 28576 at 
drivers/net/wireless/intel/iwlwifi/mvm/scan.c:1786 
iwl_mvm_rx_umac_scan_complete_notif+0x158/0x170 [iwlmvm]
avr 14 17:23:25 haxorz kernel: Modules linked in: ses enclosure 
scsi_transport_sas uas usb_storage hid_generic usbhid hid snd_usb_audio 
snd_usbmidi_lib snd_rawmidi snd_seq_device ipt_MASQUERADE nf_conntrack_netli
avr 14 17:23:25 haxorz kernel:  coretemp kvm_intel snd_soc_skl 
snd_soc_skl_ipc iwlmvm snd_soc_sst_ipc kvm snd_soc_sst_dsp irqbypass mac80211 
snd_hda_ext_core intel_cstate snd_soc_acpi_intel_match snd_soc_acpi int
avr 14 17:23:25 haxorz kernel:  crc32c_intel ghash_clmulni_intel pcbc 
rtsx_pci_sdmmc mmc_core aesni_intel ahci xhci_pci aes_x86_64 crypto_simd 
libahci cryptd glue_helper xhci_hcd libata psmouse e1000e usbcore scs
avr 14 17:23:25 haxorz kernel: CPU: 0 PID: 28576 Comm: kworker/0:1 Tainted: 
GW  OE 4.19.0-4-amd64 #1 Debian 4.19.28-2
avr 14 17:23:25 haxorz kernel: Hardware name: LENOVO 20F9003CCA/20F9003CCA, 
BIOS N1CET74W (1.42 ) 02/07/2019
avr 14 17:23:25 haxorz kernel: Workqueue: events iwl_mvm_async_handlers_wk 
[iwlmvm]
avr 14 17:23:25 haxorz kernel: RIP: 
0010:iwl_mvm_rx_umac_scan_complete_notif+0x158/0x170 [iwlmvm]
avr 14 17:23:25 haxorz kernel: Code: 39 ff ff ff 48 8b 7f 28 e8 b5 76 04 00 
8b 95 98 18 00 00 c7 85 b8 18 00 00 00 00 00 00 41 8b 84 24 1c 19 00 00 e9 13 
ff ff ff <0f> 0b e9 35 ff ff ff e8 ac c3 cd ce 66 66 2e 0f
avr 14 17:23:25 haxorz kernel: RSP: 0018:a55f49c8fe10 EFLAGS: 00010246
avr 14 17:23:25 haxorz kernel: RAX: 0100 RBX: 9a0d12079000 
RCX: c0f9eb80
avr 14 17:23:25 haxorz kernel: RDX:  RSI: 9a0cbbef1c50 
RDI: 9a0d1a999548
avr 14 17:23:25 haxorz kernel: RBP: a55f49c8fe50 R08: 9a0d1d222620 
R09: 
avr 14 17:23:25 haxorz kernel: R10:  R11: 9a0d1d220be8 
R12: 9a0d1a999548
avr 14 17:23:25 haxorz kernel: R13: 9a0cbbef1c40 R14: dead0100 
R15: 9a0cbbef1c40
avr 14 17:23:25 haxorz kernel: FS:  () 
GS:9a0d1d20() knlGS:
avr 14 17:23:25 haxorz kernel: CS:  0010 DS:  ES:  CR0: 
80050033
avr 14 17:23:25 haxorz kernel: CR2: 7f88cc10 CR3: 7b40a002 
CR4: 003606f0
avr 14 17:23:25 haxorz kernel: Call Trace:
avr 14 17:23:25 haxorz kernel:  iwl_mvm_async_handlers_wk+0xba/0x160 
[iwlmvm]
avr 14 17:23:25 haxorz kernel:  process_one_work+0x1a7/0x3a0
avr 14 17:23:25 haxorz kernel:  worker_thread+0x30/0x390
avr 14 17:23:25 haxorz kernel:  ? create_worker+0x1a0/0x1a0
avr 14 17:23:25 haxorz kernel:  kthread+0x112/0x130
avr 14 17:23:25 haxorz kernel:  ? kthread_bind+0x30/0x30
avr 14 17:23:25 haxorz kernel:  ret_from_fork+0x35/0x40
avr 14 17:23:25 haxorz kernel: ---[ end trace 457db209ade39170 ]---

You can read the whole journal log file in the attached files section.

I know. That hostname though. Anyway. ;)

Regards,

-- Package-specific info:
** Version:
Linux version 4.19.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 
8.3.0 (Debian 8.3.0-2)) #1 SMP Debian 4.19.28-2 (2019-03-15)

** Command line:
BOOT_IMAGE=/vmlinuz-4.19.0-4-amd64 root=/dev/mapper/haxorz--vg-root ro quiet

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

** Kernel log:
[   12.144820] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
[   12.148357] Bluetooth: hci0: Applying Intel DDC parameters completed
[   12.164687] Console: switching to colour frame buffer device 240x67
[   12.199141] i915 :00:02.0: fb0: inteldrmfb frame buffer device
[   12.228416] new mount options do not match the existing superblock, will be 
ignored
[   12.248829] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC293: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[   12.248832] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[   12.248834] snd_hda_codec_realtek hdaudioC0D0:hp_outs=2 
(0x16/0x15/0x0/0x0/0x0)
[   12.248835] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[   12.248837] snd_hda_codec_realtek hdaudioC0D0:inputs:
[   12.248838] snd_hda_codec_realtek hdaudioC0D0:  Dock Mic=0x19
[   12.248840] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a
[   12.248842] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12
[   12.337131] 

Bug#927089: dicomscope-doc: error merging doc-base files: format pdf already defined

[Julian Gilbey]

Package: dicomscope-doc
Version: 3.6.0-20
Severity: normal

During an upgrade, I just received the following error:

Processing triggers for doc-base (0.10.8) ...
Processing 3 changed doc-base files, 2 added doc-base files...
Error while merging /usr/share/doc-base/dicomscope-doc-dscs with 
/usr/share/doc-base/dicomscope-doc-dsum: format pdf already defined.

Not sure exactly what is wrong here; presumably the Document ID should
be different in the two different files, and that might solve the
issue?

Best wishes,

   Julian

Bug#927088: unblock: sitesummary/0.1.43

[Wolfgang Schweer]

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

Please unblock package sitesummary

It fixes an important bug¹, the change is minimal. 
Holger Levsen has already uploaded the package.

Full source debdiff against the package in testing attached.

¹https://bugs.debian.org/924451

unblock sitesummary/0.1.43

Regards,
Wolfgang
diff -Nru sitesummary-0.1.42/collect.d/system 
sitesummary-0.1.43/collect.d/system
--- sitesummary-0.1.42/collect.d/system 2019-01-26 23:37:09.0 +0100
+++ sitesummary-0.1.43/collect.d/system 2019-04-06 16:01:45.0 +0200
@@ -44,7 +44,7 @@
 
 # Collect hard disk information
 for diskdev in $(grep 'sd.$' /proc/partitions|awk '{print $4}'|sort); do
-hdparm -I /dev/$diskdev || true
+hdparm -I /dev/$diskdev 2>/dev/null || true
 done > hdparm-I
 
 # Collect zfs hard disk information too
diff -Nru sitesummary-0.1.42/debian/changelog 
sitesummary-0.1.43/debian/changelog
--- sitesummary-0.1.42/debian/changelog 2019-01-26 23:37:09.0 +0100
+++ sitesummary-0.1.43/debian/changelog 2019-04-06 16:01:45.0 +0200
@@ -1,3 +1,11 @@
+sitesummary (0.1.43) unstable; urgency=medium
+
+  [ Petter Reinholdtsen ]
+  * collect.d/system: throw away errors from hdparm to reduce noise from some
+HW RAID machines. Closes: #924451
+
+ -- Holger Levsen   Sat, 06 Apr 2019 16:01:45 +0200
+
 sitesummary (0.1.42) unstable; urgency=medium
 
   * Remember to include ipmi collector in client package.


signature.asc
Description: PGP signature

Bug#926967: Don't recommend irqbalance (was: Re: Handling irqbalance in virtual environments)

[Nicholas D Steeves]

On Fri, Apr 12, 2019 at 10:56:29PM +0200, Bastian Blank wrote:
> > On Fri, 2019-04-12 at 10:53 +0200, Bastian Blank wrote:
> > > It turns out we got again problems with irqbalance.
> > > 
> > > It was added as recommends of the main image in 3.16, as it was reported
> > > that older kernels move all interrupts to CPU 0 without help.[1]
> > > 
> > > In the meantime the kernel can do balancing on it's own.  In 4.9, I've
> > > seen it working with aacraid, each queue gets hard pinned to it's own
> > > CPU from 0 to $NRCPUS.  In 4.19 I've seen the same working properly with
> > > virtio-net.
> > > 
> > > With 4.19, even on real hardware, where interrupts have an affinity for
> > > all cpus, each interrupt is actually delivered to different cpu.
> > > 
> > > Random example for this, it even selects only one thread of each core:
> > > 
> > > >  26:0000   92000  IR-PCI-MSI 3670017-edge   
> > > >eno1-TxRx-0
> > > >  27:00000  16700  IR-PCI-MSI 3670018-edge   
> > > >eno1-TxRx-1
> > > >  28:000000  4670  IR-PCI-MSI 3670019-edge   
> > > >eno1-TxRx-2
> > > >  29:0000000  454  IR-PCI-MSI 3670020-edge   
> > > >eno1-TxRx-3
> > > 
> > > Now irqbalance comes to re-do the existing pinning, and the result is not
> > > longer correct but $RANDOM for the hard queue-to-cpu case of virtio.
> > 
> > Then let's drop the recommendation.
> 
> Okay.

+1 !  On what appears to be a related note, irqbalance + linux-4.19
appears to cause a 1.5-to-2.5w power regression on my Thinkpad X220 vs
irqbalance + linux-4.9, even when no VMs are running.

Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#927087: unblock: debian-edu-config/2.10.65

[Wolfgang Schweer]

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

Please unblock package debian-edu-config

It fixes an important bug¹ that has been detected while testing various 
Debian Edu installation scenarios. Holger Levsen has already uploaded 
the package.

Full source debdiff against the package in testing attached.

¹https://bugs.debian.org/926949 

unblock debian-edu-config/2.10.65

Regards,
Wolfgang
diff -Nru debian-edu-config-2.10.64/debian/changelog 
debian-edu-config-2.10.65/debian/changelog
--- debian-edu-config-2.10.64/debian/changelog  2019-04-02 10:54:26.0 
+0200
+++ debian-edu-config-2.10.65/debian/changelog  2019-04-12 22:13:55.0 
+0200
@@ -1,3 +1,10 @@
+debian-edu-config (2.10.65) unstable; urgency=medium
+
+  [ Wolfgang Schweer ]
+  * Depend on gnutls-bin. (Closes: #926949)
+
+ -- Holger Levsen   Fri, 12 Apr 2019 22:13:55 +0200
+
 debian-edu-config (2.10.64) unstable; urgency=medium
 
   [ Wolfgang Schweer ]
diff -Nru debian-edu-config-2.10.64/debian/control 
debian-edu-config-2.10.65/debian/control
--- debian-edu-config-2.10.64/debian/control2019-03-04 11:06:04.0 
+0100
+++ debian-edu-config-2.10.65/debian/control2019-04-12 18:11:27.0 
+0200
@@ -30,6 +30,7 @@
  e2fsprogs,
  education-tasks,
  fping,
+ gnutls-bin,
  isenkram-cli,
  ldap-utils,
  ldapscripts,


signature.asc
Description: PGP signature

Bug#926326: elpa-elpy: configuration issues

[Nicholas D Steeves]

Dear Faheem,

Thank you for filing an excellent bug report that includes all
relevant information.  Reply follows in-line, but please take care to
reply to the appropriate sub-bugs that will be momentarily created:
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=elpa-elpy

  elpa-elpy: README.Debian misleads users into enabling nonexistent Python 2 
support
* Concerning points: #1, #5, #6, #7
  elpa-elpy: Please provide a QuickStart page
* Concerning point #4
  elpa-elpy: Please enable Python 2 support
* Concerning points: #1, #5, #6, #7

Bug#926326: elpa-elpy: configuration issues is now
  * Concerning points: #2, #3

I've split the aggregate into discrete bugs, because some of these
issues will not receive an unblock for buster.

On Wed, Apr 03, 2019 at 08:39:35PM +0530, Faheem Mitha wrote:
> Package: elpa-elpy
> Version: 1.28.0-1
> Severity: normal
> 
> Dear Maintainer,
> 
> I've been struggling with getting elpy to work on Debian stable.
>

Thank you for letting me know, and sorry it wasn't easy.  Let's fix
this! :-)

> For right now, some comments and suggestions about README.Debian.
> 
> 1) There's a typo in your code:
> 
> (setq python-shell-interpreter "python"
>   python-shell-interpreter-args "-i")
>   elpy-rpc-python-command "python")
> 
> It should be:
> 
> (setq python-shell-interpreter "python"
>   python-shell-interpreter-args "-i"
>   elpy-rpc-python-command "python")
>

Good catch, thanks!

> 2) You should mention that elpy isn't loaded by default, and indicate
> how to load it. Historically, Debian packages autoload modes once
> installed, and personally I find that more convenient. But I
> understand if you don't load it to preserce compatibility with
> upstream EPLA.
>

Yes, for simple packages this is absolutely the way to go.  I chose to
leave (elpa-enable) up to the user because on my system it doubles
Emacs startup time, because elpa-enable is unconditionally executed.
Also, a user may choose to enable Elpy using an alternative
(conditional) method.

> The elpy manual mentions in
> https://elpy.readthedocs.io/en/latest/introduction.html that elpy
> should be enabled with
> 
> (package-initialize)
> (elpy-enable)
> 
> Just the second line works for me here. I'm not sure what the first
> part does. Some sort of global enable, apparently.
>

For info about package-initialize, see the Emacs manual §48.2 "Package
Installation".  Also, your init file may have already had the following
automatically added to the top of it:

  ;; Added by Package.el.  This must come before configurations of  
  
  ;; installed packages.  Don't delete this line.  If you don't want it,
  
  ;; just comment it out by adding a semicolon to the start of the line.
  
  ;; You may delete these explanatory comments. 
  
  (package-initialize)

> 3) I suggest mentioning the upstream manual in README.Debian. Namely,
> https://elpy.readthedocs.io/en/latest/
>

Unfortunately this will not provide accurate documentation for users
of Debian buster in the coming months, because that URL will document
a newer version of Elpy, and buster is shipping with 1.28.0.  Also, a
link is useless for users who are offline.

Would you please comment on your experience with "info elpy" or "man
elpy"?  P.S. The sphinx-generated info page is much nicer than the
the man page it generates, and the following is nicer still:

  emacs --eval '(info "elpy")'
  # or M-x info, C-s elpy

> 4) And if I were writing the README.Debian, I'd also mention that C-c
> C-c runs the buffer, and that you need C-c C-z to open up a Python
> interpreter buffer. This would help people to get going quickly,
> instead of flailing around trying to figure out what to do.
> 
> These commands are both in
> https://elpy.readthedocs.io/en/latest/ide.html
> 
> C-c C-y r (elpy-shell-send-region-or-buffer)
> [...]
> Also bound to C-c C-c.
> 
> and
> 
> C-c C-z (elpy-shell-switch-to-shell)
> 
> There are a ton of commands in that manual, and it's really
> confusing. But you really only need a couple to get going. That manual
> really needs a quickstart page.
>

I agree!  With more info about the proposed enhancements I'll open an
upstream pull request and investigate filing an unblock for Elpy so
that users of buster can benefit.  So far, for the QuickStart we have
1) document shortcuts for elpy-shell-send-region-or-buffer and
elpy-shell-switch-to-shell 2) possibly a solution to the question
below 3) Anything else?

> Do you happen to know if it is possible to configure emacs to open a
> Python buffer in elpy mode by default and skip the C-c C-z?
>

It is :-)  Have you tried using an add-hook in your init file?  Is
this also an item for the QuickStart section of upstream docs?

> 5) I'm also running into the error message mentioned in
> https://github.com/jorgenschaefer/elpy/issues/1521
> 
> Should I report it here? Or 

Bug#926326: elpa-elpy: configuration issues

[Nicholas D Steeves]

clone 926326 -1 -2 -3
retitle -1 elpa-elpy: README.Debian misleads users into enabling nonexistent 
Python 2 support
severity -1 important
retitle -2 elpa-elpy: Please provide a QuickStart page
retitle -3 elpa-elpy: Please enable Python 2 support
severity -3 wishlist


signature.asc
Description: PGP signature

Bug#647053: Reverse dependencies of virtual package not handled correctly

[Dmitry Katsubo]

I've hit the same problem when listing dependencies for package tomcat8, which 
depends on tomcat8-common, which depends on "default-jre-headless | 
java8-runtime-headless | java8-runtime,
libtomcat8-java" but java8-runtime-headless is not shown:

# apt-rdepends --state-follow=Installed --state-show=Installed tomcat8

tomcat8
  Depends: tomcat8-common (>= 8.5.38-2)
...
tomcat8-common
  Depends: libtomcat8-java (>= 8.5.38-2)


# apt-cache showpkg java8-runtime-headless
...
Reverse Provides:
openjdk-8-jre-headless 8u212-b01-1~deb9u1 (= )
openjdk-11-jre-headless 11.0.3+1-1~bpo9+1 (= )
openjdk-8-jre-headless 8u181-b13-2~deb9u1 (= )
default-jre-headless 2:1.8-58 (= )
openjdk-11-jre-headless 11.0.3+1-1 (= )
default-jre-headless 2:1.11-71 (= )

-- 
With best regards,
Dmitry

Bug#927083: RFS: golang-github-heroku-rollrus/0.0~git20190402.fde2a6b-1

[Dawid Dziurla]

Dear Go team,

I am looking for a sponsor for the package "golang-github-heroku-rollrus".
This package is a prerequisite for upcoming package "lazygit" (#908894).

I pushed to our team's Salsa:

  https://salsa.debian.org/go-team/packages/golang-github-heroku-rollrus

This package depends on "golang-github-stvp-roll" (#924918)

Could you please reviewing/sponsoring this?
Any kind of reviews and suggestions are appreciated.

Bug#926603: Debian fails to start after installation into Virtualbox

[Michael Biebl]

On Mon, 8 Apr 2019 01:10:28 +0200 Michael Biebl  wrote:
> Control: tags -1 moreinfo
> 
> Am 07.04.19 um 18:51 schrieb Andy Ruddock:
> > Package: systemd
> > Severity: critical
> > 
> > I'm running Windows 10 (Home edition - up to date) on the desktop, with
> > Virtualbox (v6.0.4).
> > I've used both the netinst CD & the testing DVD (downloaded today -
> > 07/Apr/2019) to install Buster.
> > After installation the system fails to start with many errors.
> > The first is :
> > 
> > systemd[1]: user.slice: Failed to set inovcation ID for unit: File
> > exists
> > [FAILED]: Failed to start User and Session Slice.
> > 
> > other services then fail to start :
> > 
> > [FAILED] Failed to start Slices.
> > [FAILED] Failed to listen on udev Kernel Socket.
> > [FAILED] Failed to start Remote File Systems.
> > [FAILED] Failed to listen on Syslog Socket.
> > 
> > and many more, followed by
> > 
> > systemd[1]: Timed out waiting for device /dev/disk/by-uuid/2cb
> > 
> > finally
> > 
> > [FAILED] Failed to start Network.
> > 
> > At which point there is no more, the system just halts.
> > 
> > Starting with "quiet" removed from linux invocation in grub, I see
> > 
> > systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX
> > +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS
> > +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2
> > default-hierarchy=hybrid)
> > systemd[1]: Detected virtualization oracle.
> > systemd[1]: Detected architecture x86-64.
> > 
> > Welcome to Debian GNU/Linux buser/sid!
> 
> Please follow the instructions at
> https://freedesktop.org/wiki/Software/systemd/Debugging/ and get us a
> verbose debug log from the complete boot.
> Please also attach the output of "reportbug --template systemd" on the
> affected system.

Any updates here? Can you provide the requested information`

-- 
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#927083: ITP: golang-github-heroku-rollrus -- Logrus Rollbar Hook

[Dawid Dziurla]

Package: wnpp
Severity: wishlist
Owner: Dawid Dziurla 

* Package name: golang-github-heroku-rollrus
  Version : 0.0~git20190402.fde2a6b-1
  Upstream Author : Heroku
* URL : https://github.com/heroku/rollrus
* License : Expat
  Programming Lang: Go
  Description : Logrus Rollbar Hook

 Rollrus is what happens when Logrus (https://github.com/sirupsen/logrus)
 meets Roll (https://github.com/stvp/roll).
 .
 When a .Error, .Fatal or .Panic logging function is called, report the
 details to rollbar via a Logrus hook.
 .
 Delivery is synchronous to help ensure that logs are delivered.
 .
 If the error includes a StackTrace, that StackTrace is reported to rollbar.

This package is in the dependency tree of Lazygit (#908894)

Depends on "golang-github-stvp-roll" (#924918)

Bug#923773: logind sessions are ended immediately after login

[Steinar H. Gunderson]

On Mon, Apr 15, 2019 at 12:05:37AM +0200, Michael Biebl wrote:
>> Should that really stop logind sessions from activating? Nevertheless,
>> downgrading.
> 
> Yes, pretty much so.
> session scopes have a
> RequiresMountsFor=/home/$user (or whatever the home dir is set to)

Again, note that this also happened for another user (which I created just
for this test). So it's a bit odd.

/* Steinar */
-- 
Homepage: https://www.sesse.net/

Bug#888547: CVE-2017-1000190

[Emmanuel Bourg]

Le 14/04/2019 à 23:27, Markus Koschany a écrit :

> Simple-xml is only required to build carrotsearch-randomizedtesting. It
> is not a test-dependency though.

> Apparently the removal makes no difference for lucene4.10.

Indeed, because carrotsearch-randomizedtesting is just a test dependency
of lucene4.10.

Emmanuel Bourg

Bug#924687: akregator: tabs crash interacting with particular sites

[John Scott]

Package: akregator
Version: 4:18.08.3-2
Followup-For: Bug #924687

It appears for the crash to happen that the site must be loaded in a
tab. Even if the site is loaded in full, the crash doesn't occur if
using it from the Articles tab.

That being said, disabling JavaScript doesn't make a difference. It
appears that clicking on the link alone makes it crash. I've found
a site with a feed [1] such that clicking seemingly any link makes
Akregator crash, and I'm including my much more lengthy backtrace
from that.

[1] https://retractionwatch.com/feed/

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

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

Versions of packages akregator depends on:
ii  kinit5.54.0-1
ii  kio  5.54.1-1
ii  libc62.28-8
ii  libgcc1  1:8.3.0-5
ii  libkf5codecs55.54.0-1
ii  libkf5completion55.54.0-1
ii  libkf5configcore55.54.0-1
ii  libkf5configgui5 5.54.0-1
ii  libkf5configwidgets5 5.54.0-1
ii  libkf5coreaddons55.54.0-1
ii  libkf5crash5 5.54.0-1
ii  libkf5grantleetheme-plugins  18.08.3-1
ii  libkf5grantleetheme5 18.08.3-1
ii  libkf5i18n5  5.54.0-1
ii  libkf5iconthemes55.54.0-1
ii  libkf5jobwidgets55.54.0-1
ii  libkf5kcmutils5  5.54.0-1
ii  libkf5kiocore5   5.54.1-1
ii  libkf5kiogui55.54.1-1
ii  libkf5kiowidgets55.54.1-1
ii  libkf5kontactinterface5  18.08.3-1
ii  libkf5libkdepim-plugins  4:18.08.3-2
ii  libkf5libkdepim5 4:18.08.3-2
ii  libkf5messageviewer5abi1 4:18.08.3-2
ii  libkf5mimetreeparser5abi14:18.08.3-2
ii  libkf5notifications5 5.54.0-1
ii  libkf5notifyconfig5  5.54.0-1
ii  libkf5parts5 5.54.0-1
ii  libkf5pimcommon5abi2 4:18.08.3-2
ii  libkf5pimtextedit5abi2   18.08.3-1
ii  libkf5service-bin5.54.0-1
ii  libkf5service5   5.54.0-1
ii  libkf5syndication5abi1   18.08.3-1
ii  libkf5textwidgets5   5.54.0-1
ii  libkf5webengineviewer5abi1   4:18.08.3-2
ii  libkf5widgetsaddons5 5.54.0-1
ii  libkf5xmlgui55.54.0-1
ii  libqt5core5a 5.11.3+dfsg1-1
ii  libqt5dbus5  5.11.3+dfsg1-1
ii  libqt5gui5   5.11.3+dfsg1-1
ii  libqt5network5   5.11.3+dfsg1-1
ii  libqt5printsupport5  5.11.3+dfsg1-1
ii  libqt5webenginecore5 5.11.3+dfsg-2+b1
ii  libqt5webenginewidgets5  5.11.3+dfsg-2+b1
ii  libqt5widgets5   5.11.3+dfsg1-1
ii  libqt5xml5   5.11.3+dfsg1-1
ii  libstdc++6   8.3.0-5

akregator recommends no packages.

akregator suggests no packages.

-- no debconf information
Application: Akregator (akregator), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6db689bf00 (LWP 3114))]

Thread 27 (Thread 0x7f6da4ff9700 (LWP 3248)):
#0  futex_reltimed_wait_cancelable (private=0, reltime=0x7f6da4ff8400, 
expected=0, futex_word=0x7f6da4ff85e8) at 
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  __pthread_cond_wait_common (abstime=0x7f6da4ff84a0, mutex=0x7f6da4ff8598, 
cond=0x7f6da4ff85c0) at pthread_cond_wait.c:533
#2  __pthread_cond_timedwait (cond=0x7f6da4ff85c0, mutex=0x7f6da4ff8598, 
abstime=0x7f6da4ff84a0) at pthread_cond_wait.c:667
#3  0x7f6dc7d2fa37 in base::ConditionVariable::TimedWait(base::TimeDelta 
const&) () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f6dc7d3230a in base::WaitableEvent::TimedWaitUntil(base::TimeTicks 
const&) () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f6dc7d323f2 in base::WaitableEvent::TimedWait(base::TimeDelta 
const&) () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7f6dc7d36981 in 
base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () 
from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7f6dc7d37c7f in base::internal::SchedulerWorker::Thread::ThreadMain() 
() from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#8  0x7f6dc7d40c81 in base::(anonymous namespace)::ThreadFunc(void*) () 
from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#9  0x7f6dc5210fa3 in start_thread (arg=) at 
pthread_create.c:486
#10 0x7f6dcc9dc82f in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 26 (Thread 0x7f6d4f2de700 (LWP 3175)):
#0  futex_wait_cancelable (private=0, expected=0, futex_word=0x7f6d4f2dd5f8) at 
../sysdeps

Bug#926901: bcron: init.d script and runit service conflict

[Mathieu Mirmont]

On Sun, Apr 14, 2019 at 10:52:42AM +, Dmitry Bogatov wrote:
> [2019-04-12 01:32] Mathieu Mirmont 
> > [...]
>
> I believe this bug will be fixed as effect of #924769 (not marked as
> resolved, due my typo in changelog), which is now in Archives as
> runit=2.1.2-28/experimental. With #924769 in effect, runscript will stop
> init.d instance before starting its own. Mind to check?

Yes that fixes the bug indeed, thanks.

Generally speaking, for packages that use dh_runit I suppose that it
is fine because the order of execution in the postinst script is
deterministic: the init.d script will always be started first.
Hopefully this is by far the most common case.

It is quite brittle to rely on a side effect of how the postinst files
are generated though, but without invoke-rc.d or the init.d script
being aware of runsvdir I don't see a simple solution that would be
guaranteed to work everywhere, unfortunately.

> > I suspect that a fix could be implemented in invoke-rc.d by making it
> > aware of runsvdir, similarly to how it is already aware of systemd and
> > openrc?
> 
> Yes, it is planned, but pushing changes to init-system-helpers is quite
> long and painful process for me for social reasons. If you are willing
> to help, you are more then welcome.

Hmm.. I'm generally happy to help, but not very much really looking
forward to long and (socially) painful processes.

> Take a look at #924132.

Interesting, though quite a number of changes. I only quickly looked
at the sources, I'll have a better look at it at some point. I am
hoping that there is a simpler solution out there.

One issue I notice is that it only considers runit services if runit
is the init system (by looking for /run/runit.stopit). However
runsvdir can also be run under sysvinit and systemd.

-- 
Mathieu Mirmont 


signature.asc
Description: PGP signature

Bug#927082: ntpd exits after "receive: Unexpected origin timestamp"

[Alison Chaiken]

Package: ntp
Version: 1:4.2.8p12+dfsg-3
Severity: normal

Dear Maintainer,

   * What led up to the situation?

I noticed that system clock was off by minutes and ntpd was not
running, nor was systemd-timesyncd.   Here's what syslog showed for
Apr 11, the day that ntp stopped:

Apr 11 08:43:08 bonnet kernel: [1033254.722518] systemd: 54 output lines 
suppressed due to ratelimiting
Apr 11 08:43:08 bonnet systemd[1]: Stopping Network Time Service...
Apr 11 08:43:08 bonnet ntpd[611]: ntpd exiting on signal 15 (Terminated)
Apr 11 08:43:08 bonnet ntpd[611]: 72.5.72.15 local addr 192.168.42.66 -> 
Apr 11 08:43:08 bonnet ntpd[611]: 192.207.62.39 local addr 192.168.42.66 -> 

Apr 11 08:43:08 bonnet ntpd[611]: 184.105.182.7 local addr 192.168.42.66 -> 

Apr 11 08:43:08 bonnet ntpd[611]: 104.168.88.15 local addr 192.168.42.66 -> 

Apr 11 08:43:08 bonnet ntpd[611]: 69.89.207.199 local addr 192.168.42.66 -> 

Apr 11 08:43:08 bonnet ntpd[611]: 208.75.89.4 local addr 192.168.42.66 -> 
Apr 11 08:43:08 bonnet systemd[1]: Stopping Network Time Synchronization...
Apr 11 08:43:08 bonnet systemd[1]: ntp.service: Succeeded.
Apr 11 08:43:08 bonnet systemd[1]: Stopped Network Time Service.
Apr 11 08:43:08 bonnet systemd[1]: systemd-timesyncd.service: Succeeded.
Apr 11 08:43:08 bonnet systemd[1]: Stopped Network Time Synchronization.
Apr 11 08:43:08 bonnet systemd[1]: Condition check resulted in Network Time 
Synchronization being skipped.

There is no coredump file.

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

I started ntp with systemd.   The time synced, as desired, but it
exits again.   Here's what daemon.log show from today:

Apr 14 09:12:37 bonnet ntpd[30901]: 129.250.35.250 local addr 192.168.42.66 -> 

Apr 14 09:14:26 bonnet ntpd[30901]: receive: Unexpected origin timestamp 
0xe05ddae1.a4519274 does not match aorg 00. from 
server@45.56.118.161 xmt 0xe05ddae2.6856ffbc
Apr 14 09:14:26 bonnet ntpd[30901]: receive: Unexpected origin timestamp 
0xe05ddae1.a4544e2f does not match aorg 00. from 
server@192.111.144.114 xmt 0xe05ddae2.697c8478

   * What was the outcome of this action?

ntp won't run for very long without exiting.

   * What outcome did you expect instead?

I was hoping that ntp would be stable once it was restarted.

I see that packagekit is also failing, but perhaps ntp's failure is
causing it:

Apr 14 09:10:33 bonnet PackageKit: refresh-cache transaction /186129_aceadcdd 
from uid 1000 finished with success after 29419ms
Apr 14 09:10:35 bonnet PackageKit: get-updates transaction /186130_acda 
from uid 1000 finished with success after 2267ms
Apr 14 09:10:36 bonnet PackageKit: get-updates transaction /186131_bebabcaa 
from uid 1000 finished with success after 822ms
Apr 14 09:10:37 bonnet PackageKit: get-updates transaction /186132_dcbcabce 
from uid 1000 finished with success after 802ms
Apr 14 09:15:39 bonnet systemd[1]: packagekit.service: Main process exited, 
code=killed, status=15/TERM

Thanks for volunteering with Debian,
Alison Chaiken
ali...@she-devel.com

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

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

Versions of packages ntp depends on:
ii  adduser3.118
ii  libc6  2.28-8
ii  libcap21:2.25-2
ii  libedit2   3.1-20181209-1
ii  libopts25  1:5.18.12-4
ii  libssl1.1  1.1.1b-1
ii  lsb-base   10.2019031300
ii  netbase5.6
ii  tzdata 2019a-1

Versions of packages ntp recommends:
ii  perl  5.28.1-6
ii  sntp  1:4.2.8p12+dfsg-3

Versions of packages ntp suggests:
ii  ntp-doc  1:4.2.8p12+dfsg-3

-- no debconf information

Bug#923773: logind sessions are ended immediately after login

[Steinar H. Gunderson]

On Sun, Apr 14, 2019 at 11:15:46PM +0200, Steinar H. Gunderson wrote:
> I think maybe I found it; it seems that there was a bad entry in fstab:

Evidently, this is what it looks like. I don't know where it came from
(it is possible I wrote it myself, but if so, I forgot):

  fake  /home/sesse autonoauto  1   0

I don't know what would try to mount noauto mounts at login (even for users
that are not sesse!) and why that would fail sessions. But commenting it out
really fixed the issue.

/* Steinar */
-- 
Homepage: https://www.sesse.net/

Bug#888547: CVE-2017-1000190

[Markus Koschany]

Hi,

Am 13.04.19 um 11:31 schrieb Ivo De Decker:
[...]
> It is possible to remove the test-dependency (probably by disabling the
> tests)? That way simple-xml could be removed from buster. Even if we don't do
> this for buster, it might be good to do this for bullseye anyway, if the
> package isn't really maintained.

Simple-xml is only required to build carrotsearch-randomizedtesting. It
is not a test-dependency though. However I have just disabled the only
module in carrotsearch-randomizedtesting that uses simple-xml, which is
junit4-ant.

If we do that then lucene4.10 will FTBFS but it requires only a simple
patch to tell the build system not to look for the now missing
junit4-ant dependency. Apparently the removal makes no difference for
lucene4.10. I can implement those changes in the coming days.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#923773: logind sessions are ended immediately after login

[Steinar H. Gunderson]

severity 923773 normal
retitle 923773 broken fstab entries stop logind sessions in X
thanks

On Sun, Apr 14, 2019 at 10:56:17PM +0200, Michael Biebl wrote:
> Could you also please paste the output of
> grep pam_systemd /etc/pam.d/*

I think maybe I found it; it seems that there was a bad entry in fstab:

  april 14 23:08:08 klump systemd[1]: home-sesse.mount: Directory /home/sesse 
to mount over is not empty, mounting anyway.
  april 14 23:08:08 klump systemd[1]: Mounting /home/sesse...
  april 14 23:08:08 klump mount[781]: mount: /home/sesse: special device fake 
does not exist.
  april 14 23:08:08 klump systemd[1]: home-sesse.mount: Mount process exited, 
code=exited, status=32/n/a
  april 14 23:08:08 klump systemd[1]: home-sesse.mount: Failed with result 
'exit-code'.
  april 14 23:08:08 klump systemd[1]: Failed to mount /home/sesse.
  april 14 23:08:08 klump systemd[1]: Dependency failed for Session 2 of user 
sesse.

Should that really stop logind sessions from activating? Nevertheless,
downgrading.

/* Steinar */
-- 
Homepage: https://www.sesse.net/

Bug#927081: gnome-shell: FTBFS on s390x: crash in throw_property_lookup_error()

[Simon McVittie]

Package: libmozjs-60-dev
Version: 60.2.3-3
Severity: important
Tags: help
Control: affects -1 src:gnome-shell src:gjs
X-Debbugs-Cc: debian-s...@lists.debian.org

mozjs60 and gjs now pass most of their tests on s390x, but there seems
to be some problem when gjs' debug output prints the JS::HandleId
representing a property name as a JSFlatString*, which is causing
gnome-shell to fail tests there. I don't know whether this is related to
whatever bug makes non262/extensions/clone-errors.js fail during mozjs60
unit tests, or to the many test failures seen in gjs (but gjs doesn't
FTBFS because, perhaps unwisely, build-time test failures are ignored).

I suspect that the root cause of all these bugs might be more instances
of mozjs60 casting struct types to other struct types and making
assumptions about which struct fields coincide.

% gdb obj-s390x-linux-gnu/src/run-js-test tests/core
...
Core was generated by 
`/home/smcv/gnome-shell-3.30.2/obj-s390x-linux-gnu/tests/../src/run-js-test 
unit'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x03ffb23eddfc in gjs_debug_flat_string (fstr=) at 
gjs/jsapi-util-string.cpp:392
392 gjs/jsapi-util-string.cpp: No such file or directory.
[Current thread is 1 (Thread 0x3ffb34bdcc0 (LWP 57720))]
(gdb) bt
#0  0x03ffb23eddfc in gjs_debug_flat_string(JSFlatString*) (fstr=)
at gjs/jsapi-util-string.cpp:392
#1  0x03ffb23ef4c4 in gjs_debug_id[abi:cxx11](jsid) (id=...) at 
/usr/include/mozjs-60/jsapi.h:4843
#2  0x03ffb23e8f8c in throw_property_lookup_error(JSContext*, 
JS::HandleObject, char const*, JS::HandleId, char const*) 
(cx=cx@entry=0x169770d60, obj=..., 
obj@entry=..., description=description@entry=0x3ffb24184ee "GI repository 
object", property_name=..., 
property_name@entry=..., reason=reason@entry=0x3ffb241b3b8 "it was not an 
object") at gjs/jsapi-util.cpp:143
#3  0x03ffb23e9908 in gjs_object_require_property(JSContext*, 
JS::Handle, char const*, JS::Handle, 
JS::MutableHandle)
(cx=cx@entry=0x169770d60, obj=obj@entry=..., 
description=description@entry=0x3ffb24184ee "GI repository object", 
property_name=..., value=..., value@entry=...) at gjs/jsapi-util.cpp:251
#4  0x03ffb23d83d6 in lookup_override_function (function=..., ns_name=..., 
cx=0x169770d60)
at /usr/include/mozjs-60/js/RootingAPI.h:1152
#5  0x03ffb23d83d6 in resolve_namespace_object(JSContext*, 
JS::HandleObject, JS::HandleId, char const*)
(context=context@entry=0x169770d60, repo_obj=..., repo_obj@entry=..., 
ns_id=..., 
ns_id@entry=..., ns_name=0x169879b40 "Clutter") at gi/repo.cpp:135
#6  0x03ffb23d8864 in repo_resolve(JSContext*, JS::HandleObject, 
JS::HandleId, bool*)
(context=0x169770d60, obj=..., id=..., resolved=0x3ffc9bfb8e0) at 
./gjs/jsapi-util.h:117
#7  0x03ffaf53b78a in js::CallResolveOp
(recursedp=, propp=..., id=..., obj=..., cx=0x169770d60)
at ./debian/build/dist/include/js/RootingAPI.h:545
...
(gdb) info locals
c = 
ix = 0
str = 
len = 
nogc = 
out = 
chars = 0x436c757474657200 

Note that if you interpret the big-endian integer 0x436c757474657200 as
ASCII, it reads "Clutter", suggesting that the bytes at the beginning
of a char[] containing "Clutter" have been interpreted as though they
were a pointer - possibly a JSInlineString being misinterpreted as
a JSFlatString?

Regards,
smcv

Bug#927080: unblock: links2/2.18-2

[Axel Beckert]

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

Please unblock links2/2.18-2:

It fixes a crash on invalid IDN URLs (e.g. http://test,ï.com/) which
is currently present and easily reproducible in Debian Buster. See
https://bugs.debian.org/926674 for the according Debian bug report.

The patch has been provided by upstream to Debian and is part of
upstream's 2.19 release (currently in Debian Experimental).

Full debdiff between 2.18-1 and 2.18-2:

diff -Nru links2-2.18/debian/changelog links2-2.18/debian/changelog
--- links2-2.18/debian/changelog2019-01-23 01:58:22.0 +0100
+++ links2-2.18/debian/changelog2019-04-08 21:28:08.0 +0200
@@ -1,3 +1,10 @@
+links2 (2.18-2) unstable; urgency=low
+
+  * Cherry-pick patch from upstream to fix crash on invalid IDN
+URL. (Closes: #926674)
+
+ -- Axel Beckert   Mon, 08 Apr 2019 21:28:08 +0200
+
 links2 (2.18-1) unstable; urgency=medium
 
   * Import new upstream release 2.18.
diff -Nru links2-2.18/debian/patches/fix-crash-on-invalid-idn-url.patch 
links2-2.18/debian/patches/fix-crash-on-invalid-idn-url.patch
--- links2-2.18/debian/patches/fix-crash-on-invalid-idn-url.patch   
1970-01-01 01:00:00.0 +0100
+++ links2-2.18/debian/patches/fix-crash-on-invalid-idn-url.patch   
2019-04-08 21:28:08.0 +0200
@@ -0,0 +1,20 @@
+Description: Fix a crash on invalid IDN URL
+ Example: http://test,ï.com/
+ .
+ Found by lsxv...@gmail.com.
+Origin: commit 9dc711da9b61431f83f863920583d4c9d3bea26d
+Author: Mikulas Patocka 
+Date: Sat Mar 30 22:36:43 2019 +0100
+Bug-Debian: https://bugs.debian.org/926674
+
+--- a/url.c
 b/url.c
+@@ -1153,6 +1153,8 @@
+   url_enc = idn_encode_url(url_conv2, 0);
+   else
+   url_enc = idn_encode_host(url_conv2, 
(int)strlen(cast_const_char url_conv2), separator, 0);
++  if (!url_enc)
++  url_enc = stracpy(url_conv2), is_idn = 1;
+   mem_free(url_conv2);
+   if (!strcmp(cast_const_char url_enc, cast_const_char url)) {
+   if (is_idn && warn_idn) {
diff -Nru links2-2.18/debian/patches/series links2-2.18/debian/patches/series
--- links2-2.18/debian/patches/series   2018-03-29 01:51:56.0 +0200
+++ links2-2.18/debian/patches/series   2019-04-08 21:28:08.0 +0200
@@ -5,3 +5,4 @@
 use-local-calibration-files.diff
 use-packaged-publicsuffix.diff
 fix-FTBFS-with-autoreconf-enabled.diff
+fix-crash-on-invalid-idn-url.patch

So please unblock links2/2.18-2

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

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

Bug#921977: stretch-pu: package unzip/6.0-21+deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Sun, 2019-02-10 at 21:02 +0100, Santiago Vila wrote:
> Hello. Security team tells me this does not deserve a DSA but it's ok
> for stable-proposed-updates.
> 
> (I know it's a little bit late for 9.8. Sorry for that, and no
> problem if this is for 9.9 instead).

Apologies for not getting back to you sooner.

Please go ahead, bearing in mind that the window for 9.9 closes next
weekend.

Regards,

Adam

Bug#924783: RFS: golang-github-anmitsu-go-shlex/0.0~git20161002.648efa6-1

[Thorsten Alteholz]

On Sun, 14 Apr 2019, Dawid Dziurla wrote:

Anyway. Done.


... and uploaded.

  Thorsten

Bug#927079: libpam-script: Filters environment variables

[Tollef Fog Heen]

Package: libpam-script
Severity: normal

It seems like libpam-script filters the set of environment variables
that are set, and there is no way to either turn this off or add extra
environment variables that are passed through.

I'm interested in inspecting the SSH_AUTH_INFO_0 environment variable
set by newer versions of OpenSSH, but as this is not on the list of
variables that are passed through, I can't.

This greatly reduces the usefulness of libpam-script for me, so if this
could either be optional or the list of variables could be added to,
that'd be great.

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are

Bug#923773: logind sessions are ended immediately after login

[Michael Biebl]

Am 14.04.19 um 14:51 schrieb Steinar H. Gunderson:
> On Sun, Apr 14, 2019 at 01:33:43PM +0200, Michael Biebl wrote:
>> What's the output of
>> reportbug --template systemd
>> reportbug --template libpam-systemd
> 
> Attaching.

Hm, something is borked in the encoding, making the log a bit hard to read.

That said, I'm wondering if this is really from the same system (seeing
that the kernel information differs).

Could you also please paste the output of
grep pam_systemd /etc/pam.d/*

and a full "journalctl -alb" log after a reboot and then a failed login.


-- 
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#922385: stretch-pu: package gsoap/2.8.35-4+deb9u2

[Adam D. Barratt]

Control: tags -1 + confirmed

On Mon, 2019-02-18 at 18:12 +0100, Mattias Ellert wrote:
> fre 2019-02-15 klockan 13:06 + skrev Adam D. Barratt:
> > Control: tags -1 + moreinfo
> > 
> > On 2019-02-15 10:12, Mattias Ellert wrote:
> > > This is a proposal to fix CVE-2019-7659 in stretch.
> > > 
> > > The update also addresses one additional advisory published by
> > > the
> > > upstream developers.
> > 
> > +-soap_encode_url(const char *s, char *t, size_t len)
> > ++soap_encode_url(const char *s, char *t, int len)
> > 
> > If soap_encode_url is a public symbol, that's an ABI break - int
> > and 
> > size_t may well not be the same size, but they're definitely
> > different 
> > signedness.
[...]
> > The outcome of the discussion was that using ssize_t instead of int
> in the patch was a better idea, and that version was accepted.
> 
> I propose the same change for stretch.

Please go ahead; sorry for the delay.

Regards,

Adam

Bug#922987: stretch-pu: package cernlib/20061220+dfsg3-4.3

[Adam D. Barratt]

Control: tags -1 + confirmed

On Fri, 2019-02-22 at 17:29 +0100, Gilles Filippini wrote:
> Because RC bug #922453 affects Stretch as well, I propose a stable
> update
> for cernlib. Debdiff attached.

cernlib (20061220+dfsg3-4.3+deb9u1) stable-proposed-updates; urgency=medium

Please use "stretch" rather than "stable-proposed-updates" and go
ahead.

Regards,

Adam

Bug#924893: RFS: golang-github-emirpasic-gods/1.12.0-1

[Dawid Dziurla]

Done.

niedz., 14 kwi 2019 o 20:20 Thorsten Alteholz  napisał(a):
>
>
>
> On Sun, 14 Apr 2019, Dawid Dziurla wrote:
> > Changes pushed to salsa.
>
> Can you please also take care of:
>   I: golang-github-emirpasic-gods-dev: 
> description-synopsis-might-not-be-phrased-properly "Implementation of various 
> data structures and algorithms in Go."
>
>Thorsten
>

Bug#924786: RFS: golang-github-michaeltjones-walk/0.0~git20161122.4748e29-1

[Dawid Dziurla]

Done.

niedz., 14 kwi 2019 o 20:05 Thorsten Alteholz  napisał(a):
>
> Hi Dawid
>
> On Sun, 14 Apr 2019, Dawid Dziurla wrote:
> > It should be fixed now.
>
> yes, great, but please take care of:
>   I: golang-github-michaeltjones-walk-dev: using-first-person-in-description 
> line 2: my
>   I: golang-github-michaeltjones-walk-dev: using-first-person-in-description 
> line 4: we
> as well.
>
>Thorsten
>

Bug#925251: stretch-pu: package file/1:5.30-1+deb9u2

[Adam D. Barratt]

On Thu, 2019-03-21 at 20:28 +0100, Christoph Biedl wrote:
> for an upcoming stretch point release, I'd like to contribute a new
> version of the file package. This got a bit bigger so I'm using the
> old style of seeking approval before uploading.
[...]
> So this escalated at little, and instead of picking a single commit,
> I ended with the number of 26 ... But I am certain it's worth it.
> 
> Still there is an increased risk of introducing regressions,
> therefore I'd like to give that package some time to mature. Hence no
> security release, and if there are major concerns I might agree to
> wait until the second-next point release if the next one is less then
> four weeks in the future.

Apologies for not getting back to you sooner.

Assuming I count correctly, your mail was from approximately 6 weeks
before the date of the upcoming 9.9 point release.

> For my side, I did my usual checks, they all passed: The output of
> file on a huge collection (>> 100k) of various files, diffing the
> buildlogs, checking some packages that heavily depend on
> file/libmagic. So I'm optimistic there is no change for worse.

That sounds promising. Has the package been tested on any further
systems in the meantime?

Regards,

Adam

Bug#924783: RFS: golang-github-anmitsu-go-shlex/0.0~git20161002.648efa6-1

[Dawid Dziurla]

So, I just learned that lintian's '-I' flag is very useful.

Anyway. Done.

niedz., 14 kwi 2019 o 20:00 Thorsten Alteholz  napisał(a):
>
>
>
> On Sun, 14 Apr 2019, Dawid Dziurla wrote:
>
> > Fix pushed to salsa.
>
> ok, better, but now lintian complains about:
> I: golang-github-anmitsu-go-shlex-dev: 
> description-synopsis-might-not-be-phrased-properly "Library to make a lexical 
> analyzer like Unix shell for golang."
> I: golang-github-anmitsu-go-shlex-dev: 
> extended-description-is-probably-too-short
>
>Thorsten
>

Bug#927078: linux-image-4.19.0-4-amd64: B43 wireless forced into non-working PIO mode with latest kernel

[Stuart Read]

Package: src:linux
Version: 4.19.28-2
Severity: normal

Dear Maintainer,

   * What led up to the situation?

Upgraded to latest set of package in Testing. After this my B43 wireless card
failed to connect. The driver reported a warning:

b43-phy0 warning: Forced PIO by use_pio module parameter. This should not be 
needed and will result in lower performance.

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

Booting with kernel parameter "intel-iommu=off" solved the problem.


-- Package-specific info:
** Version:
Linux version 4.19.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 
8.3.0 (Debian 8.3.0-2)) #1 SMP Debian 4.19.28-2 (2019-03-15)

** Command line:
BOOT_IMAGE=/root/boot/vmlinuz-4.19.0-4-amd64 
root=UUID=9febe37f-1974-414a-97cd-5e3249c39291 ro rootflags=subvol=root quiet

** Not tainted

** Kernel log:

** Model information
[6.711836] b43 ssb0:0: firmware: direct-loading firmware b43/ucode16_mimo.fw
[6.715796] b43 ssb0:0: firmware: direct-loading firmware b43/n0initvals16.fw
[6.717533] b43 ssb0:0: firmware: direct-loading firmware 
b43/n0bsinitvals16.fw
[6.742872] Bluetooth: hci0: BCM: chip id 254 build 0522
[6.745796] Bluetooth: hci0: BCM: product 05ac:8213
[6.778263] Bluetooth: hci0: BCM: features 0x00
[6.795868] Bluetooth: hci0: isbjorn
[6.824440] applesmc: key=271 fan=1 temp=14 index=14 acc=1 lux=2 kbd=1
[6.831783] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[6.858783] ACPI Warning: \_SB.PCI0.IXVE.IGPU._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20180810/nsarguments-66)
[6.858810] ACPI: \_SB_.PCI0.IXVE.IGPU: failed to evaluate _DSM
[6.858950] nouveau :02:00.0: enabling device (0002 -> 0003)
[6.859211] PCI Interrupt Link [LGPU] enabled at IRQ 20
[6.859396] checking generic (c001 64) vs hw (c000 1000)
[6.859397] fb: switching to nouveaufb from EFI VGA
[6.859453] Console: switching to colour dummy device 80x25
[6.871615] Adding 14679836k swap on /dev/sda4.  Priority:-2 extents:1 
across:14679836k SSFS
[6.878926] nouveau :02:00.0: NVIDIA MCP79/MCP7A (0ac180b1)
[6.907803] pstore: Registered efi as persistent store backend
[6.947520] nouveau :02:00.0: bios: version 62.79.40.00.01
[6.950279] input: applesmc as /devices/platform/applesmc.768/input/input9
[6.968848] applesmc applesmc.768: hwmon_device_register() is deprecated. 
Please convert the driver to use hwmon_device_register_with_info().
[6.979148] nouveau :02:00.0: fb: 256 MiB stolen system memory
[7.016102] snd_hda_codec_realtek hdaudioC0D0: ALC889A: SKU not ready 
0x40f0
[7.102992] audit: type=1400 audit(1555273331.408:2): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-oopslash" 
pid=449 comm="apparmor_parser"
[7.104451] [TTM] Zone  kernel: Available graphics memory: 3954374 kiB
[7.104453] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
[7.104454] [TTM] Initializing pool allocator
[7.104460] [TTM] Initializing DMA pool allocator
[7.104489] nouveau :02:00.0: DRM: VRAM: 256 MiB
[7.104491] nouveau :02:00.0: DRM: GART: 1048576 MiB
[7.104496] nouveau :02:00.0: DRM: TMDS table version 2.0
[7.104499] nouveau :02:00.0: DRM: DCB version 4.0
[7.104502] nouveau :02:00.0: DRM: DCB outp 00: 01000123 00010014
[7.104505] nouveau :02:00.0: DRM: DCB outp 01: 02021232 0010
[7.104508] nouveau :02:00.0: DRM: DCB outp 02: 02021286 0f220010
[7.104510] nouveau :02:00.0: DRM: DCB conn 00: 0040
[7.104512] nouveau :02:00.0: DRM: DCB conn 01: a146
[7.106141] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[7.106142] [drm] Driver supports precise vblank timestamp query.
[7.108267] audit: type=1400 audit(1555273331.416:3): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-senddoc" 
pid=451 comm="apparmor_parser"
[7.109585] nouveau :02:00.0: DRM: MM: using M2MF for buffer copies
[7.115991] audit: type=1400 audit(1555273331.424:4): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=448 
comm="apparmor_parser"
[7.115997] audit: type=1400 audit(1555273331.424:5): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="man_filter" pid=448 
comm="apparmor_parser"
[7.115999] audit: type=1400 audit(1555273331.424:6): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="man_groff" pid=448 
comm="apparmor_parser"
[7.123196] audit: type=1400 audit(1555273331.432:7): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-xpdfimport" 
pid=454 comm="apparmor_parser"
[7.139098] audit: type=1400 audit(1555273331.448:8): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-soffice" 
pid=453 comm="apparmor_par

Bug#925936: release.debian.org: Would v4l-utils 1.16.5 match unblocking criteria?

[Niels Thykier]

Control: tags -1 moreinfo confirmed

Gregor Jasny:
> Control: tags -1 - moreinfo
> 
> Hello,
> 
> A new patch turned up and I decided to only cherry-pick the three most
> important patches from the stable-1.16 tree.
> 
> Debdiff is attached.
> 
> If you agree on the changes I will upload via unstable.
> 
> Thanks,
> Gregor

Hi Gregor,

Please go ahead with this patch and remove the moreinfo tag once it has
been fixed.

Please note that you may want to inform upstream of the following
possible bug:

"""
+-  parms->fname = fname;
++  parms->fname = strdup(fname);
++  if (!parms->fname) {
++  dvb_logerr(_("fname calloc: %s"), strerror(errno));
++  return -errno;
++  }
++
"""

Please note that *any* call to a library function (e.g. strerror or _,
which I presume is gettext, or dvb_logerr which sounds like it will do
IO operations) may alter errno.  I.e. the errno returned may no longer
be from the failing strdup.

AFAICT, this is a consistent issue through out the diff and therefore
not really a regression:

"""
+   if (xioctl(fd, FE_GET_PROPERTY, &dtv_prop) == -1) {
+   dvb_perror("FE_GET_PROPERTY");
+-  dvb_v5_free(parms);
+   close(fd);
+   return -errno;
+   }
"""

Which is why I am ok with accepting it as it is.  For reference, the
solution is to store "errno" in a local variable immediately after the
failing call.

Thanks,
~Niels

Bug#926199: stretch-pu: package libreoffice/1:5.2.7-1+deb9u6

[Adam D. Barratt]

Control: tags -1 + moreinfo

On Mon, 2019-04-01 at 21:43 +0200, Rene Engelhard wrote:
> now that https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911925
> is finally fixed in stretch-p-u I think it's time to fix
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913641 in the sense
> that we conflict against the "broken" OpenJDK (and build-conflict
> against it. So we can remove the "build hack" needed to be introduced
> in the +deb9u5 security update).

How much has the upgrade path from current stable been tested? e.g.
what happens if APT decides to upgrade LO before openjdk-8 and for some
reason the system does not have the security.d.o package installed?

Regards,

Adam

Bug#925506: stretch-pu: package java-common/0.58+deb9u1

[Adam D. Barratt]

Control: tags -1 + moreinfo

On Mon, 2019-03-25 at 22:35 +0100, Moritz Muehlenhoff wrote:
> How about the following debdiff to address the fallout of
> the Xul deprecation in icedtea-web (#921748) for the next
> point update?
> 
> default-jre is the only reverse dependency of
> default-java-plugin, so the patch also removes default-java-plugin
> along.

I assume the upgrade path from systems with the packages already
installed has been tested without issue?

Regards,

Adam

Bug#927062: ddupdate: autoupdate shouldn't be systemd-only

[Alec Leamas]

On 14/04/2019 21:22, Adam Borowski wrote:
> On Sun, Apr 14, 2019 at 08:02:45PM +0200, Alec Leamas wrote:
>> No. ddupdate uses systemd --user to setup and run  the service without
>> root permissions. So it's not comparable in this respect.
> 
> It is called by the main blob itself, which runs as root, and sheds
> permissions only to execute user services.

Indeed. Stili, ddupfdate users can setuo and run their service without
root permissions; IIRC cron et. el. does not offer this option.


>>> You have two timers: one every 1h (the usual cron way), and another 2min
>>> after boot.  What's the point of the second if you already have an oneshot
>>> service?

Because it's very likely you have a new address after boot which need to
be registered


> But today, any consumer ISP at any of three places I have non-hosted
> machines at doesn't even support inbound IPv4 anymore, making tunnels
> the way to go for me.

Well, that's you. Other users have inbound connections for various reasons.

> A "must" requirement of the policy:

> §9.11:
> # [...] any package integrating with other init systems
> # must also be backwards-compatible with sysvinit by providing a SysV-
> # style init script with the same name as and equivalent functionality
> # to any init-specific job, as this is the only start-up configuration
> # method guaranteed to be supported by all init implementations.

It's interesting -- but it does not take the fact that systemd is the
default init system into account (per TC decision etc, you know this
better than me I guess). The Debian wiki [1] tells us:

# Since jessie, only systemd is fully supported; sysvinit is mostly
# supported, but Debian packages are not required to provide sysvinit
# start scripts.

I will not take part in any systemd  war here. Given the complete
context,  I think this is an RFE.


--alec

[1] https://wiki.debian.org/Init

Bug#927077: plymouth: futureprototype theme has no feedback when performing system updates

[Andrew Hayzen]

Package: plymouth
Version: 0.9.4-1.1

When using the new futureprototype plymouth theme, there is no feedback
to the user of any offline updates being applied.

With other plymouth themes (eg spinner) when offline systemd updates
occur text appears in the top left corner with "Installing updates...
NN%" etc. This is useful to the user as they are then informed that the
system is doing something and has not blocked.

Bug#914591: stretch-pu: package python-cryptography/1.7.1-3

[Adam D. Barratt]

On Sun, 2018-11-25 at 13:49 +0100, Sebastian Andrzej Siewior wrote:
> With the intention of pushing OpenSSL 1.1.0j into Stretch here is the
> proposed change for python-cryptography.
> The package python-cryptography fails to build due to an API change
> of BIO_callback_ctrl() in OpenSSL. While this is a no-no in a stable
> release, it has been explained [0] that the function / callback was
> always used with a different prototype. I fixed this by removing the
> function / prototype from the python wrapper while upstream removed
> the almost all BIO related wrappers [1].
> I did a rebuild of python-cryptography's rdeps in Stretch against
> OpenSSL 1.1.0i and the proposed package with no fallout [2].

Just to be 100% sure on the scope here, those rebuilds were just for
confirmation? i.e. they are not required if we go ahead.

Regards,

Adam

Bug#820036: Debian does not run on systems with Secure Boot enabled

[Ben Hutchings]

Control: summary -1

GRUB and Linux images are now signed by the production key trusted by
shim-signed.  Debian-installer apparently installs the signed packages,
but other installation systems are not yet ready.

Ben.

-- 
Ben Hutchings
Quantity is no substitute for quality, but it's the only one we've got.




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

Bug#821088: vmdebootstrap: Missing UEFI Secure Boot support

[Ben Hutchings]

Control: found 1.11-1

I can confirm that this still doesn't work.

Ben.

-- 
Ben Hutchings
Quantity is no substitute for quality, but it's the only one we've got.




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

Bug#927076: RFP: xournalpp -- hand note taking software

[Carlo Segre]

It is my plan to package this as well.  Once I get some time...

Carlo

On Sun, 14 Apr 2019, Elena ``of Valhalla'' wrote:


Package: wnpp
Severity: wishlist

* Package name: xournalpp
 Version : 1.0.10
 Upstream Author : ?
* URL : https://github.com/xournalpp/xournalpp
* License : GPL
 Programming Lang: C++
 Description : hand note taking software

Xournal++ is an application for notetaking, sketching and
keeping a journal using a stylus. It can also be used to
add annotations to PDF files.

This is a rewrite of xournal which maintains a decent amount of
backwards compatibility and is currently under active development.
It is mentioned on the xournal homepage itself.

It would be nice to have it in Debian together with xournal (or instead
of xournal, in case the latter will end up being removed because of its
age).



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

Bug#927062: ddupdate: autoupdate shouldn't be systemd-only

[Adam Borowski]

On Sun, Apr 14, 2019 at 08:02:45PM +0200, Alec Leamas wrote:
> No. ddupdate uses systemd --user to setup and run  the service without
> root permissions. So it's not comparable in this respect.

It is called by the main blob itself, which runs as root, and sheds
permissions only to execute user services.

But I'm definitely not an expert on systemd -- heck, I can't even run it on
the machine I'm sitting at right now as it won't complete boot...

> >> And, cron jobs are nowhere as flexible as systemd timers.
> > 
> > You have two timers: one every 1h (the usual cron way), and another 2min
> > after boot.  What's the point of the second if you already have an oneshot
> > service?
> 
> 
> It's about having a dynamic (e. g., dhcp) address which could change
> anytime. That's why services like this kind periodically checks if the
> address has changed and updates the involved DNS entry if so.

Yeah, that's what the 1h cronjob is for.  You also have one at boot.  What
I'm pointing at is the second timer that runs 2min after boot -- it's
redundant with the service you already have.

> > I don't use ddupdate myself anymore (I don't even remember if I used
> > ddupdate or one of the alternatives), thus it might be more for an actual
> > user.
> 
> You have probably never used it then, it's a pretty new tool. You might,
> however, have used ddclient which is sort of similar (and widespread).

There's a large number of such clients, yeah.

Heck, I once wrote such a script for an own DNS server myself, even...

But today, any consumer ISP at any of three places I have non-hosted
machines at doesn't even support inbound IPv4 anymore, making tunnels
the way to go for me.


Meow.
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Did ya know that typing "test -j8" instead of "ctest -j8"
⢿⡄⠘⠷⠚⠋⠀ will make your testsuite pass much faster, and fix bugs?
⠈⠳⣄

Bug#926735: Set severity

[Kai Lüke]

Control: severity -1 serious

Bug#927062: ddupdate: autoupdate shouldn't be systemd-only

[Adam Borowski]

On Sun, Apr 14, 2019 at 08:12:30PM +0200, Alec Leamas wrote:
> BTW: Given that the systemd stuff is part of the upstream package

Ah right, I've confused this with another package I was reviewing at the
same time, where the .service file came from the debian/ dir.  My bad.

On the other hand, I see that your "ddupdate" is a clean reimplementation
with no relation to the ddupdate I had been using over a decade ago, thus
this is not a regression either.

> on what grounds could you state that "autoupdate shouldn't be
> systemd-only"?  Is there a Debian policy or something similar I have
> missed?
> 
> TL;DR Isn't this a plain RFE?

A "must" requirement of the policy:

§9.11:
# [...] any package integrating with other init systems
# must also be backwards-compatible with sysvinit by providing a SysV-
# style init script with the same name as and equivalent functionality
# to any init-specific job, as this is the only start-up configuration
# method guaranteed to be supported by all init implementations.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Did ya know that typing "test -j8" instead of "ctest -j8"
⢿⡄⠘⠷⠚⠋⠀ will make your testsuite pass much faster, and fix bugs?
⠈⠳⣄

Bug#821051: Need support for uploading and signing EFI executables

[Ben Hutchings]

On Fri, 03 Aug 2018 21:49:19 +0800 Ben Hutchings  wrote:
> Control: retitle -1 ftp.debian.org: Get signing service running
> 
> At the Secure Boot sprint
>  a new
> architecture for code signing was agreed, and the implementation now
> exists at ;.
> 
> This bug should stay open until the signing service is in production.

The signing service is in production, with a production key.  However,
signing currently has to be approved manually, whereas in the long term
it's intended to be automatic.

Ben.

-- 
Ben Hutchings
Quantity is no substitute for quality, but it's the only one we've got.




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

Bug#918393: opensips FTBFS with MariaDB 10.3

[Otto Kekäläinen]

su 14. huhtik. 2019 klo 14.06 peter green (plugw...@p10link.net) kirjoitti:
>
> Could you please check if it is still valid and happening in Debian
> unstable there has had several updates MariaDB client libraries /
> connector C libraries recently?
>
> According to 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/opensips.html
>  it is still failing in the same way.

For the records, failing lines from
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/opensips_2.2.2-3.rbuild.log.gz
***
In file included from my_con.c:25:
/usr/include/mysql/mysql_version.h:3:2: warning: #warning This file
should not be included by clients, include only  [-Wcpp]
 #warning This file should not be included by clients, include only 
  ^~~
my_con.c: In function 'db_mysql_connect':
my_con.c:68:10: error: 'MYSQL' {aka 'struct st_mysql'} has no member
named 'reconnect'
  ptr->con->reconnect = 0;
***

>From https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919395#36 :
***

error: 'MYSQL' {aka 'struct st_mysql'} has no member named 'reconnect'

   This is not a bug. MYSQL.reconnect was not part of the API, even in 5.5
   https://dev.mysql.com/doc/refman/5.5/en/c-api-auto-reconnect.html
***


Forwarded at https://github.com/OpenSIPS/opensips/issues/1589 and
following it one can find
https://github.com/farcepest/MySQLdb1/issues/146 stating that OpenSIPS
depends on an Python MySQL connector that is not maintained anymore...

Bug#927068: stretch-pu: package vcftools/0.1.14+dfsg-4+deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Sun, 2019-04-14 at 18:24 +0200, Dylan Aïssi wrote:
> Upstream has fixed CVE-2018-11099, CVE-2018-11129 and CVE-2018-11130
> which are non-dsa.
> The fix is already applied in unstable/testing and now I would like
> to
> fix the Stretch version.
> 

Please go ahead.

Regards,

Adam

Bug#927072: stretch-pu: package jabref/3.8.1+ds-3

[Adam D. Barratt]

Control: tags -1 + confirmed

On Sun, 2019-04-14 at 10:47 -0700, tony mancill wrote:
> This proposed update for jabref addresses CVE-2018-1000652 [1], which
> will not be issued a DSA [2].  The debdiff is attached.
> 
> Thank you,
> tony
> 
> [1] https://security-tracker.debian.org/tracker/CVE-2018-1000652
> [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921772#48

Please go ahead.

Regards,

Adam

Bug#927064: unblock: synaptic/0.84.5+nmu1

[Paul Gevers]

Control: tags -1 moreinfo confirmed

On 14-04-2019 16:27, Shengjing Zhu wrote:
> As discussed in #818366
> 
>> If somebody comes up with a decent Wayland detection and (also
>> graphical) error message to the user explaining how to get a working
>> synaptic, the release team is considering letting synaptic back in if
>> this happens soon.
> 
> I'd like to ask RT to unblock this NMU. It adds both console and GUI warning
> to user who want to run synaptic as root on Wayland.
> 
> Full changelog is:
> 
>  * Non-maintainer upload.
>  * configure.in: Miss bumping version str to 0.84.5.
>  * synaptic-pkexec: Do not use pkexec under Wayland; warn users instead.
>  * gsynaptic: Show possible reason when failed to init gtk
> 
> debdiff is in attachment, and can also be viewed at:
> 
> https://github.com/mvo5/synaptic/pull/39
> 
> I'll only upload after ack, and downgrade the severity of #818366.

From our perspective, please upload. Unless the maintainer disagrees
with the NMU (in CC). Remove the moreinfo tag once the package build
everywhere to trigger us to proceed with unblocking.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#927076: RFP: xournalpp -- hand note taking software

[Elena ``of Valhalla'']

Package: wnpp
Severity: wishlist

* Package name: xournalpp
  Version : 1.0.10
  Upstream Author : ?
* URL : https://github.com/xournalpp/xournalpp
* License : GPL
  Programming Lang: C++
  Description : hand note taking software

Xournal++ is an application for notetaking, sketching and
keeping a journal using a stylus. It can also be used to
add annotations to PDF files.

This is a rewrite of xournal which maintains a decent amount of
backwards compatibility and is currently under active development.
It is mentioned on the xournal homepage itself.

It would be nice to have it in Debian together with xournal (or instead
of xournal, in case the latter will end up being removed because of its
age).

Bug#926952: sa-exim: Unbuildable/uninstallable in sid

[Magnus Holmgren]

fredag 12 april 2019 kl. 19:23:40 CEST skrev du:
> The dlopen localscan patch in exim4 has been nonfunctional in unstable
> for quite some time (4.92~RC2-1/experimental/18 Dec, 4.92~RC3-1
> unstable/26 Dec and buster/03 Jan). The issue only popped up end of
> March on the upstream user support ML.
>
> At this time I opened a tracking bug in exim #925982 and looked at
> sa-exim. It is dead upstream since 2006 and buggy:
> * https://lists.exim.org/lurker/message/20180726.113354.6d03efde.en.html
> * #879687

I've seen reports of bugs, but I didn't realise it was that bad. sa-exim 
hasn't exactly changed; has the way local_scan() is called changed? It's 
supposed to get an fd, read a message from it, and possibly write an altered 
message back (after piping it through spamc). What can "Format error in spool 
file" mean?

-- 
Magnus Holmgrenholmg...@debian.org
Debian Developer 

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

Bug#926624: Please drop Recommends against ibus-qt4

[Osamu Aoki]

On Mon, Apr 08, 2019 at 08:22:32AM +0200, Laurent Bigonville wrote:
> Package: ibus
> Version: 1.5.19-4
> Severity: normal
> 
> Hi,
> 
> Apparently, ibus-qt4 has been removed from the archive.
> 
> Please drop the Recommends against that package

If RM agree to accept package, this is a good idea.

Do you know?

Osamu

PS: Except for cosmetic problem, this doesn't cause problem I think.
Maybe system with old QT4 apps may be better off this way.  

Bug#927075: installation-report amd64 Buster 20190410, segv in gen-crypt

[Aaron D. Johnson]

Package: installation-reports

Boot method: network
Image version: 
http://http.us.debian.org/debian/dists/buster/main/installer-amd64/20190410/images/netboot/netboot.tar.gz
Date: 20190413T130500

Machine: Sun Microsystems SunFire x4170
Partitions:
$ lsblk -i
NAMEMAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda   8:01 111.8G  0 disk  
|-sda18:11 1G  0 part  
|-sda28:21 1G  0 part  
| `-md127 9:127  0  1022M  0 raid1 /boot
`-sda38:31 109.8G  0 part  
  `-md126 9:126  0 109.7G  0 raid1 
|-vg00-root 253:00 1G  0 lvm   /
|-vg00-swap 253:1016G  0 lvm   [SWAP]
|-vg00-usr  253:20 4G  0 lvm   /usr
|-vg00-tmp  253:30 4G  0 lvm   /tmp
|-vg00-var  253:40 8G  0 lvm   /var
|-vg00-home 253:50 4G  0 lvm   /home
`-vg00-srv  253:60 1G  0 lvm   /srv
sr0  11:01  1024M  0 rom   
$ cat /proc/mdstat
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] 
[raid4] [raid10] 
md126 : active raid1 sda3[0]
  115056064 blocks super 1.2 [2/1] [U_]
  bitmap: 1/1 pages [4KB], 65536KB chunk

md127 : active raid1 sda2[0]
  1046528 blocks super 1.2 [2/1] [U_]
  
unused devices: 
$

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [E]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

  I performed a network booted, serial console installation, and
  attempted to use the Network Console (SSH) option for finishing the
  install.  It seems that gen-crypt, used to set the shadow entry for
  the installer user, is segfaulting when run.  Attempts to SSH in
  because the installer environment's encrypted password field was
  blank.

  itops@snowman-0:/var/log/installer$ sudo grep -B 4 -A 10 -i gen-crypt syslog
  Apr 13 18:40:40 main-menu[324]: INFO: Falling back to the package description 
for brltty-udeb
  Apr 13 18:40:40 main-menu[324]: INFO: Falling back to the package description 
for mdcfg
  Apr 13 18:40:43 main-menu[324]: INFO: Falling back to the package description 
for brltty-udeb
  Apr 13 18:40:43 main-menu[324]: INFO: Menu item 'network-console' selected
  Apr 13 18:40:52 kernel: [  196.753006] gen-crypt[3532]: segfault at 
f7bf0260 ip 7fddf7dc3436 sp 7fffa186b5d8 error 5 in 
libc.so.6[7fddf7d4d000+148000]
  Apr 13 18:40:52 kernel: [  196.753012] Code: 0f 1f 40 00 66 0f ef c0 66 0f ef 
c9 66 0f ef d2 66 0f ef db 48 89 f8 48 89 f9 48 81 e1 ff 0f 00 00 48 81 f9 cf 
0f 00 00 77 6a  0f 6f 20 66 0f 74 e0 66 0f d7 d4 85 d2 74 04 0f bc c2 c3 48 
83
  Apr 13 18:40:52 sshd[3541]: Server listening on 0.0.0.0 port 22.
  Apr 13 18:40:52 sshd[3541]: Server listening on :: port 22.
  Apr 13 18:40:52 apt-install: Queueing package openssh-server for later 
installation
  Apr 13 18:43:15 sshd[3558]: Failed password for installer from 172.17.0.32 
port 52138 ssh2
  Apr 13 18:43:18 sshd[3558]: Failed password for installer from 172.17.0.32 
port 52138 ssh2
  Apr 13 18:43:19 sshd[3558]: Connection closed by authenticating user 
installer 172.17.0.32 port 52138 [preauth]
  Apr 13 18:44:58 sshd[3564]: Failed password for installer from 172.17.0.32 
port 52140 ssh2
  Apr 13 18:45:01 sshd[3564]: Failed password for installer from 172.17.0.32 
port 52140 ssh2
  Apr 13 18:46:36 sshd[3564]: Connection closed by authenticating user 
installer 172.17.0.32 port 52140 [preauth]
  itops@snowman-0:/var/log/installer$ 

  I was able to work around this using `mkpasswd' on another system
  and constructing a working /etc/shadow entry.  (Many thanks to
  whoever came up with the idea of running the installer under
  screen.  It's awesome!)

Please feel free to let me know if any additional details are needed.

Thanks!

- Aaron

Bug#926625: Please drop the Recommends against libqt5gui5

[Osamu Aoki]

Hi,


On Mon, Apr 08, 2019 at 08:37:20AM +0200, Laurent Bigonville wrote:
> Package: ibus
> Version: 1.5.19-4
> Severity: wishlist
> 
> Hi,
> 
> Could you please remove the Recommends against libqt5gui5?
> 
> My rational is, if I'm correct, that any package that require QT5 will
> already depend against this package making this dependency redundant and
> forcing QT5 libraries on desktops not using QT (GNOME,...)

I think this is bad idea.

If Qt apps are used without this, then xim based input causes lost key
stroke etc.  Qt apps are not only for KDE people.  QCAD, ... 

You are saving tiny disk space.

Also this is recommend.  You can override.

Regards,

Osamu

Bug#927074: UTF-8 conversion broke code base

[Osamu Aoki]

Package: src:anthy
Version: 1:0.3-8
Severity: important
Tags: patch

NOTE: 
 * src-util/input.c and src-worddic/word_lookup.c may deserve further check
   (git commit message in attached file needs to be corrected)
 * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923948 is addressed
   again in the patch series attached here against 1:0.3-8.

Attached patch:
   You need to package the patch series applied source.  This is not
   ready for release as is.  Patch base is salsa debian branch.

Question: How should we proceed from here.  Should we make upstream
tarball?  Who updates upstream now?  Who knows dictionary building 
  
== PROBLEM1: DEBUG code is broken

After building the source with debuild, you can run debug code as:
  $ test/checklib
  checking
  (あいうえお)
  (アイウエオ)
  (あいうえお)
  (ｱｲｳｴｵ)
  ��
  done
The last line before "done" should print NTH_HALFKANA_CANDIDATE thus
broken.

== PROBLEM 2: ZIPCODE

7 digits number returns odd choice.
  * 100 -> 〓延根〓遵〓篁ｇ〓〓〓
  * 227 -> 腑〓〓綏〓〓罔〓〓絽〓
  * 2270001 -> No problem
  * ...
  * 2270030 -> No problem
  * 2270031 -> 腑〓〓綏〓〓罔〓〓絽〓絲阪〓〓〓
  * 2270032 -> 腑〓〓綏〓〓罔〓〓絽〓〓
  * ...
  * 2270044 -> 腑〓〓綏〓〓罔〓〓絽〓〓

ZIPCODE to address conversion seems to have problem.

== PROBLEM3: Anthy seems stupid recently.

Unlike above 2 clear reproducible bugs, many people seem to think recent
anthy is stupid.  They seems to suspect UTF-8 transition has problem.

See patch for technical details to be addressed.

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

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


patch.tar.gz
Description: application/gzip

Bug#921266: linphone: Segfault and crash with "error 4 in libc-2.28.so" on password entry

[Alf]

Am 13.04.19 um 14:30 schrieb Bernhard Übelacker:
> Hello Alf,
>
> Am 12.04.19 um 22:10 schrieb Alf:
>> I am prepared to test your patch as soon as I get a binary of the
>> patched lib.
>
> please find attached some commands to build the package
> with the patches in question by yourself.
>

Hello Bernhard,

!! Success !!

It works as expected - no more crashes, dialing out and accepting
incoming calls, all works fine.

I think, the problem was that Telekon/t-online does not supply a nonce
after initial registering. At the beginning a nonce is sent once or
twice to stay compatible with the old procedure (before transition to
BNG). I found some figures indicating that some 15% of Users are still
not converted, while 85% are on "BNG", which uses authentication by
hardware (the port on the DSLAM).

Here part of the debug output as logged by linphone with your patches,
see the line with
>>> "error: ... [nonce]not found.. 
which I suppose caused to the crash.

message: 2019-04-14 19:01:54:880 channel [0x55e37bc52800]: keep alive
sent to [UDP://tel.t-online.de:5060]
message: 2019-04-14 19:02:04:909 channel [0x55e37bc52800]: keep alive
sent to [UDP://tel.t-online.de:5060]
message: 2019-04-14 19:02:08:614 linphone_core_find_auth_info():
returning auth info username=061234567818, realm=tel.t-online.de
message: 2019-04-14 19:02:08:614 Auth info found for [061234567818]
realm [tel.t-online.de]
error: 2019-04-14 19:02:08:614 parameter [nonce]not found for header
[authorization]
message: 2019-04-14 19:02:08:614 Transaction [0x55e37bb11cb0] deleted
message: 2019-04-14 19:02:08:615 Changing [client] [REGISTER]
transaction [0x55e37bd3ec00], from state [INIT] to [TRYING]
message: 2019-04-14 19:02:08:615 channel [0x55e37bc52800]: message sent
to [UDP://tel.t-online.de:5060], size: [571] bytes
REGISTER sip:tel.t-online.de SIP/2.0
Via: SIP/2.0/UDP 192.168.33.12:5060;branch=z9hG4bK.GfqS~Yviw;rport
From: ;tag=PdBaldvNc
To: sip:061234567...@tel.t-online.de
CSeq: 22 REGISTER
Call-ID: kNvTHMUU1E
Max-Forwards: 70
Supported: replaces, outbound
.

If you need more information, please let me know, I can generate a debug
log over a longer time period including incoming and outgoing calls.

Again myany thanks for your great help and patience.
Kind regards,
Alf

Bug#924893: RFS: golang-github-emirpasic-gods/1.12.0-1

[Thorsten Alteholz]

On Sun, 14 Apr 2019, Dawid Dziurla wrote:

Changes pushed to salsa.


Can you please also take care of:
 I: golang-github-emirpasic-gods-dev: description-synopsis-might-not-be-phrased-properly 
"Implementation of various data structures and algorithms in Go."

  Thorsten

Bug#927062: ddupdate: autoupdate shouldn't be systemd-only

[Alec Leamas]

Hi again, one more thing:

On 14/04/2019 20:02, Alec Leamas wrote:
> 
> Hi again,
> 
[lot's of stuff]


BTW: Given that the systemd stuff is part of the upstream package, on
what grounds could you state that "autoupdate shouldn't be
systemd-only"? Is there a Debian policy or something similar I have missed?

TL;DR Isn't this a plain RFE?

--alec

Bug#924786: RFS: golang-github-michaeltjones-walk/0.0~git20161122.4748e29-1

[Thorsten Alteholz]

Hi Dawid

On Sun, 14 Apr 2019, Dawid Dziurla wrote:

It should be fixed now.


yes, great, but please take care of:
 I: golang-github-michaeltjones-walk-dev: using-first-person-in-description 
line 2: my
 I: golang-github-michaeltjones-walk-dev: using-first-person-in-description 
line 4: we
as well.

  Thorsten

Bug#916375: [debian-mysql] Bug#916375: Bug#916375: apache2: Segmentation fault when mod_perl.so is loaded

[Otto Kekäläinen]

Control: severity important
Severity: important

> Can you still reproduce this with latest versions of MariaDB 10.3.13
> and mod_perl ?

Downgrading severity since no more info has been provided in past
month and there are no new reports that somebody would be affected.

Bug#927070: ITP: ledger2beancount -- Convert Ledger-based textual ledgers to Beancount ones

[Stefano Zacchiroli]

Thanks Jelmer !  :-)

On April 14, 2019 6:49:26 PM GMT+02:00, Jelmer Vernooij  
wrote:
>Package: wnpp
>Severity: wishlist
>Owner: Jelmer Vernooij 
>
>* Package name: ledger2beancount
>  Version : 1.6
>  Upstream Author : Stefano Zacchiroli 
>Martin Michlmayr 
>* URL : https://github.com/zacchiro/ledger2beancount
>* License : GPLv3
>  Programming Lang: Perl
>Description : Convert Ledger-based textual ledgers to Beancount
>ones
>
>A script to automatically convert Ledger-based textual ledgers to
>Beancount
>ones.
>
>Conversion is based on (concrete) syntax, so that information that is
>not
>meaningful for accounting reasons but still valuable (e.g., comments,
>formatting, etc.) can be preserved.

-- 
Sent from my mobile phone. Please excuse my brevity and top-posting.

Bug#927062: ddupdate: autoupdate shouldn't be systemd-only

[Alec Leamas]

Hi again,

On 14/04/2019 18:49, Adam Borowski wrote:
> On Sun, Apr 14, 2019 at 05:20:08PM +0200, Alec Leamas wrote:
>> On 14/04/2019 16:22, Adam Borowski wrote:
>>> Hi!
>>> The auto-update functionality is for some reason systemd only, despite not
>>> actually using any systemd features.  This makes it broken on any other
>>> init/rc system for no gain.
>>>
>>> Could you please convert the .service/.timer to a init script and/or cron
>>> job?
>>>
>> Anything is possible but... in this case ddupdate installs as a user program
>> without anything running as root. Things like cron or init scripts are
>> requires root permissions
> 
> It's same as for systemd, which also runs as root -- only the syntax is
> different.  There's "runuser"; on a default install exim4 and popcon use it.


No. ddupdate uses systemd --user to setup and run  the service without
root permissions. So it's not comparable in this respect.

>> And, cron jobs are nowhere as flexible as systemd timers.
> 
> You have two timers: one every 1h (the usual cron way), and another 2min
> after boot.  What's the point of the second if you already have an oneshot
> service?


It's about having a dynamic (e. g., dhcp) address which could change
anytime. That's why services like this kind periodically checks if the
address has changed and updates the involved DNS entry if so.


>> OTOH, it would of course be possible to add alternative solutions like cron
>> jobs to the package. This would requires patches to ddupdate-config, but
>> should otherwise be trivial. But to be honest, I'm more in a "patches
>> welcome" state on this -- I'm just not motivated to make such fixes myself.
> 
> I don't use ddupdate myself anymore (I don't even remember if I used
> ddupdate or one of the alternatives), thus it might be more for an actual
> user.


You have probably never used it then, it's a pretty new tool. You might,
however, have used ddclient which is sort of similar (and widespread).

> thus it might be more for an actual user.

Agreed.

Bug#924783: RFS: golang-github-anmitsu-go-shlex/0.0~git20161002.648efa6-1

[Thorsten Alteholz]

On Sun, 14 Apr 2019, Dawid Dziurla wrote:


Fix pushed to salsa.


ok, better, but now lintian complains about:
I: golang-github-anmitsu-go-shlex-dev: description-synopsis-might-not-be-phrased-properly 
"Library to make a lexical analyzer like Unix shell for golang."
I: golang-github-anmitsu-go-shlex-dev: 
extended-description-is-probably-too-short

  Thorsten