Bug#863198: Xen compiling with XSM on

[Herve Moris]

Hi Hans,

As far as I remember Mark Pryor managed to compile it and made a debian
package with XSM enabled.

So I think you can indeed close this bug :)

Fun fact, I just compiled compiled the new stable version (4.11.1)
yesterday successfully.

If anyone crossing these reports wants to know the process (build in a
Docker container, default flask policy):

/# In an updated Debian 9 docker /

/echo "deb-src http://ftp.be.debian.org/debian/ testing main" >>
/etc/apt/sources.list//
//apt update && apt upgrade -y/

///# install testing apt sources//
//apt-get source xen//
//
//# or just use ://
//apt-get build-dep xen//
//
//apt install checkpolicy texinfo fakeroot libpci-dev pandoc
libsystemd-dev fig2dev markdown devscripts rdfind//
//
//cd $(find $(pwd) -maxdepth 1 -type d -name "xen-*")//
//
//cat <> //
//
//# Enableling and configuring XSM and FLASK//
//XSM_ENABLE=y//
//FLASK_ENABLE=y//
//CONFIG_XSM=y//
//CONFIG_FLASK=y//
//CONFIG_FLASK_AVC_STATS=y//
//CONFIG_XSM_POLICY=y//
//
//EOF//
//
//cd ..//
//
//dpkg-buildpackage -rfakeroot -us -uc -b//
//
//mkdir ../deb_files//
//mv ../*.deb /../deb_files//
//
//# Copy what is under ./deb_files to the server (docker cp ... &&
scp -r ...)//
//
//
//## Installation notes//
//# Install the deb files//
//dpkg -i *.deb//
//
//# set GRUB_CMDLINE_XEN_DEFAULT="flask=permissive" and
GRUB_CMDLINE_XEN=""//
//# in /etc/default/grub.d/xen.cfg//
//
//update-grub//
//
//# if grub doesn't want to start XEN kernel because of xenpolicy
multiboot header bla bla - Li'l Bug with Grub integration//
//# change //
//# for i in /boo/xen*; do ...    to    for i in /boo/xen-*; do
...  (line 180)//
//# in vim /etc/grub.d/20_linux_xen//
//
//update-grub/


Best Regards,

Hervé


*Hervé Moris*
System Administrator / Backend developer

*Loyaltek*
Cantersteen 47
1000 - Brussels
Tel : +32 2 808.07.58
Fax : +32 2 706.56.84

www.loyaltek.com 
On 1/23/19 11:41 PM, Hans van Kranenburg wrote:
> tags 863198 + moreinfo
> thanks
>
> Hi Hervé,
>
> I'm hunting down old bug reports in the Xen packages, and also ran into
> this one:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863198
>
> Like John Keates already answered in there, when dealing with the source
> of a debian package, you're also expected to use the debian packaging
> way of building it. When just issuing make commands, you're dealing with
> the upstream source in a way that we cannot support in Debian.
>
> Since there has been no more activity on the report, I might close it in
> a while if there's no response, since it's not something we can act on.
>
> Have fun,
> Hans

Bug#920326: augeas ftbfs from source

[Matthias Klose]

Package: src:augeas
Version: 1.11.0-2
Severity: serious
Tags: sid buster

[...]
make[3]: Leaving directory '/<>'
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
dh_install -X.la -Xusr/bin/fadot -Xusr/bin/dump
make[1]: Leaving directory '/<>'
   dh_installdocs -i
dh_installdocs: Cannot find (any matches for) "doc/*.pdf" (tried in ., 
debian/tmp)

make: *** [debian/rules:8: binary-indep] Error 9

Bug#916256: [pkg-go] Bug#916256: gitlab-runner fails when it tries to pull docker image gitlab-runner-helper:11.2.0

[Dmitry Smirnov]

On Thursday, 24 January 2019 11:01:03 AM AEDT Dean Hamstead wrote:
> Seems to be the same as:
> https://gitlab.com/gitlab-org/gitlab-runner/issues/3441

Probably not the same...
Debian package works very different in regards to gitlab-runner-helper image.
>From post-install docker build command is executed to prepare an image which 
is then stored into "/var/lib/gitlab-runner/". By definition, prebuilt image 
is local and it should never be downloaded.

Do you have "/var/lib/gitlab-runner/gitlab-runner-prebuilt.tar.xz" file?

I test every upload of Gitlab Runner (and I use this very version all the 
time) so I suspect that the problem might be somewhere in configuration...

Could you try "sudo dpkg-reconfigure gitlab-runner"?

There are few patches to force use of local prebuilt image -- maybe we miss 
one code path that should be patched but package passed Docker tests before 
upload so prebuilt image should work...

-- 
All the best,
 Dmitry Smirnov.

---

In individuals, insanity is rare; but in groups, parties, nations and
epochs, it is the rule.
-- Friedrich Nietzsche


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

Bug#920325: python3-mypy: Depends: python3-mypy-extenions but it is not installable

[Adrian Bunk]

Package: python3-mypy
Version: 0.660-2
Severity: serious

The following packages have unmet dependencies:
 python3-mypy : Depends: python3-mypy-extenions but it is not installable


It's python3-mypy-exten*s*ions.

Bug#918764: udev: "udevadm control --reload-rules" kills all processes except init

[Gedalya]

Hi,

With the help of snapshot.d.o, I've found that the problem first appeared in 
239-8.

I've also been able to trigger it by restarting udev and running 'udevadm 
control --log-priority=debug'.

Still no insight on what is the factor causing this to happen on some machines 
and not on others.

Regards,

Gedalya

Bug#916772: pkg-config: missing Depends: dpkg-dev

[Tollef Fog Heen]

severity 916772 normal
thanks

]] Helmut Grohne 

> # i686-linux-gnu-pkg-config --libs libssl

This is a supported, but non-standard configuration, so I'm downgrading
this from serious.

> If adding dpkg-dev to Depends is not desired, the cross-wrapper could be
> extended to give a useful error message in case $multiarch is empty:
> 
> --- /usr/share/pkg-config-crosswrapper
> +++ /usr/share/pkg-config-crosswrapper
> @@ -11,6 +11,10 @@
>triplet="${basename%-pkg-config}"
># Normalized multiarch path if any, e.g. i386-linux-gnu for i386
>multiarch="`dpkg-architecture -t"${triplet}" -qDEB_HOST_MULTIARCH 
> 2>/dev/null`"
> +  if test "$?" != 0; then
> +echo "Please apt install dpkg-dev to use this program." 1>&2
> +exit 1
> +  fi
># Native multiarch path
>native_multiarch="$(cat /usr/lib/pkg-config.multiarch)"

This looks reasonable.

> dpkg-dev should be added to Recommends in that case.

Suggests seems more appropriate here.

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

Bug#920324: plasma-workspace: device notifier turn off the external hard disk when it is dismounted

[Antonio]

Package: plasma-workspace
Version: 4:5.14.3-1+b1
Severity: normal

Dear Maintainer,
after updating to the 5.54 framework, the dismounted USB hard drive via the
device notifier is automatically turned off.
This is a different behavior than the previous framework 5.51 and for me it
is a problem, because in the procedures of daily use I need the hard disk
to remain accessible and ready for next mounts ... otherwise I have to
remove the cable from the USB port every time and then reinsert it so that
it is detected again.
Note that if I run mount/unmount from the command line, the disk remains
properly powered.
Thanks,
Antonio


-- DETAILS --

umount with framework 5.51:
...
gen 24 07:25:27 OFFICE systemd[1]: Stopping Clean the /media/root/MOBILE
mount point...
gen 24 07:25:27 OFFICE systemd[1]:
clean-mount-point@media-root-MOBILE.service: Succeeded.
gen 24 07:25:27 OFFICE systemd[1]: Stopped Clean the /media/root/MOBILE
mount point.
gen 24 07:25:27 OFFICE udisksd[1329]: Unmounted /dev/sdc1 on behalf of uid 0
...

umount with framework 5.54:
...
gen 24 07:29:05 OFFICE systemd[1]: Stopping Clean the /media/root/MOBILE
mount point...
gen 24 07:29:05 OFFICE systemd[1]:
clean-mount-point@media-root-MOBILE.service: Succeeded.
gen 24 07:29:05 OFFICE systemd[1]: Stopped Clean the /media/root/MOBILE
mount point.
gen 24 07:29:05 OFFICE udisksd[1329]: Unmounted /dev/sdc1 on behalf of uid 0
gen 24 07:29:05 OFFICE udisksd[1329]: Successfully sent SCSI command
SYNCHRONIZE CACHE to /dev/sdc
gen 24 07:29:05 OFFICE udisksd[1329]: Successfully sent SCSI command START
STOP UNIT to /dev/sdc
gen 24 07:29:05 OFFICE udisksd[1329]: Powered off /dev/sdc - successfully
wrote to sysfs path
/sys/devices/pci:00/:00:1c.4/:03:00.0/usb6/6-2/remove
gen 24 07:29:05 OFFICE kernel: usb 6-2: USB disconnect, device number 2
gen 24 07:29:06 OFFICE kernel: usb usb6-port2: config error
...

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

Kernel: Linux 4.20.4-custom (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=it_IT, LC_CTYPE=it_IT (charmap=ISO-8859-1) (ignored: LC_ALL
set to it_IT), LANGUAGE=it (charmap=ISO-8859-1) (ignored: LC_ALL set to
it_IT)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages plasma-workspace depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.12.12-1
ii  dbus-x11 [dbus-session-bus]   1.12.12-1
ii  drkonqi   5.14.3-1
ii  frameworkintegration  5.54.0-1
ii  gdb   8.2-1
ii  iso-codes 4.1-1
ii  kactivitymanagerd 5.14.3-1
ii  kded5 5.54.0-1
ii  kinit 5.54.0-1
ii  kio   5.54.1-1
ii  kpackagetool5 5.54.0-1
ii  kwin-common   4:5.14.3-2+b1
ii  libappstreamqt2   0.12.4-2
ii  libc6 2.28-5
ii  libcolorcorrect5  4:5.14.3-1+b1
ii  libgcc1   1:8.2.0-14
ii  libgps23  3.17-5+b1
ii  libice6   2:1.0.9-2
ii  libkf5activities5 5.54.0-1
ii  libkf5auth5   5.54.0-1
ii  libkf5baloo5  5.54.0-1
ii  libkf5bookmarks5  5.54.0-1
ii  libkf5calendarevents5 5.54.0-1
ii  libkf5completion5 5.54.0-1
ii  libkf5config-bin  5.54.0-1
ii  libkf5configcore5 5.54.0-1
ii  libkf5configgui5  5.54.0-1
ii  libkf5configwidgets5  5.54.0-1
ii  libkf5coreaddons5 5.54.0-1
ii  libkf5crash5  5.54.0-1
ii  libkf5dbusaddons5 5.54.0-1
ii  libkf5declarative55.54.0-1
ii  libkf5globalaccel-bin 5.54.0-1
ii  libkf5globalaccel55.54.0-1
ii  libkf5guiaddons5  5.54.0-1
ii  libkf5holidays5   1:5.54.0-1
ii  libkf5i18n5   5.54.0-1
ii  libkf5iconthemes5 5.54.0-1
ii  libkf5idletime5   5.54.0-1
ii  libkf5itemviews5  5.54.0-1
ii  libkf5jobwidgets5 5.54.0-1
ii  libkf5js5 5.54.0-1
ii  libkf5jsembed5 

Bug#920229: ocaml-mode: Please convert to use dh-elpa

[Ralf Treinen]

On Tue, Jan 22, 2019 at 03:51:47PM -0700, Nicholas D Steeves wrote:

> While working on #905940 I discovered that this package also needs to
> be elpafied.  Please see that MR linked to from that bug for the
> steps, documented as one-operation-per-commit and also in the
> changelog.
> 
> The new bin:pkg name should be elpa-caml, and ocaml-mode should become
> a dummy transitional package.

I do not think that we want to rename our packages.

> Please let me know at your earliest convenience if you will be able to
> do this before the end of January.

We are already in the transition freeze for buster, so uploading
a new vesion of ocaml is probably not a good idea at this point.

-Ralf.

Bug#919856: [pkg-gnupg-maint] Bug#919856: gpg-agent: agent refuses operation again

[Norbert Preining]

Hi Yutaka,


> "no-allow-external-cache" in your .gnupg/gpg-agent.conf.

Confirmed, that made it work.

> This means cache hits, and passphrase is "" (empty).  This is wrong.
> 
> I guess, for some unknow reason, secret_password_lookup_nonpageable_sync
> seems to return "", where NULL is expected (because of no cache hit).
> Something is going wrong in libsecret, it is related to gnome-keyring
> service.

Around 12/28 there was an update of libsecret in unstable, that was more
or less when it started - hard to say, I wasn't online for some time
around new year etc.

For testing, I reverted to 0.18.6-3 by checking out the git sources and
building from source this release (already disappeared from testing,
too).

But, unfortunately, it didn't help. Even with downgraded libsecret it
still didn't work.

> In GNOME Desktop, it is gnome-keyring-daemon which handles secret store.
> Please check your gnome-keyring-daemon is running correctly.  It's in
> gnome-keyring package.

How do I check that it is running correctly? It is running, and it
serves secrets, because my offlineimap client gets them via a python
module from the store for mail sync. Any other tests I should/can do?

> You are using gpg-agent as ssh-agent.  Please don't activate
> gnome-keyring-daemon's feature as ssh-agent.

Where would I check/configure that? I have the following gnome processes
running:
$ ps ax | grep gnome
 2330 ?SLl0:00 /usr/bin/gnome-keyring-daemon --daemonize --login
 2452 ?Sl 0:00 /usr/lib/at-spi2-core/at-spi2-registryd 
--use-gnome-session
 2612 ?SLl0:00 /usr/lib/gnome-online-accounts/goa-daemon
 2619 ?Sl 0:00 /usr/lib/gnome-online-accounts/goa-identity-service
 2678 ?Sl 0:00 
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
 3835 pts/2S+ 0:00 grep gnome
$

I checked dconf-editor and gconf-editor for something suspicious, but
didn't see anything. Also below ~/.config there wasn't anything I felt
connected.

Sorry for all the complications, and thanks for your great support

Best

Norbert

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

Bug#905940: Please resolve failing autopkgtests, preferably by converting to dh-elpa

[Ralf Treinen]

Hi Nicholas,

thanks for working on this package.

On Tue, Jan 22, 2019 at 03:45:40PM -0700, Nicholas D Steeves wrote:

> Done.  Here's the MR:
> 
>   https://salsa.debian.org/ocaml-team/tuareg-mode/merge_requests/1
> 
> Please note that autopkgtests for Tuareg require one of:
> 
> 1. ocaml-mode being elpafied too.
> 2. a manual workaround to pull in ocaml-mode to the autopkgtestbed.

I will look to your proposed changes soon. Though I do not see
why you mixed this up with unrelated cosmetic modifications. Renaming
tuareg-mode, however, is out of question.

-Ralf.

Bug#920323: initscripts: /dev/shm mounting failure on stale static /dev

[Pierre Ynard]

Package: initscripts
Version: 2.93-5
Severity: normal
Tags: patch

I haven't actually confirmed the bug, but just reading the code I
think there's a problem. After 2.93-4 resolved #851427 by reversing
the /dev/shm -> /run/shm symlink to /run/shm -> /dev/shm, on a system
running a static /dev, the following /lib/init/mount-functions.sh
mount_shm() code should hit the previous /dev/shm symlink:

> if [ ! -d "$SHMDIR" ]
> then
> mkdir --mode=755 "$SHMDIR"
> [ -x /sbin/restorecon ] && /sbin/restorecon "$SHMDIR"
> fi

There is no clean-up so mkdir will fail. Then mounting on /dev/shm will
also fail because it's a dangling symlink. Then run_migrate() will
symlink /run/shm to /dev/shm. There will be a symlink loop and no shm
tmpfs.

Perhaps the attached patch removing stale $SHMDIR symlinks could be an
appropriate trade-off.

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

Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages initscripts depends on:
ii  coreutils   8.30-1
ii  debianutils 4.8.6.1
ii  lsb-base10.2018112800
ii  mount   2.33.1-0.1
ii  sysv-rc 2.93-1
ii  sysvinit-utils  2.93-1

Versions of packages initscripts recommends:
ii  e2fsprogs  1.44.5-1
ii  psmisc 23.2-1

initscripts suggests no packages.

-- Configuration Files:
/etc/default/rcS changed [not included]
/etc/default/tmpfs changed [not included]

-- no debconf information
--- sysvinit-2.93/debian/src/initscripts/lib/init/mount-functions.sh	2019-01-19 22:28:14.0 +0100
+++ sysvinit-2.93/debian/src/initscripts/lib/init/mount-functions.sh	2019-01-24 07:14:18.734999072 +0100
@@ -579,6 +579,10 @@
 
 	if [ ! -d "$SHMDIR" ]
 	then
+		# Remove possible previous reverse symlink.
+		if [ -h "$SHMDIR" ] ; then
+			rm -f "$SHMDIR"
+		fi
 		mkdir --mode=755 "$SHMDIR"
 		[ -x /sbin/restorecon ] && /sbin/restorecon "$SHMDIR"
 	fi

Bug#912780: Line numbers not printed on error despite XML_LIBXML_LINENUMBERS => 1

[積丹尼 Dan Jacobson]

Wow that Carp::Always makes things much better. Do make a note about it
on the man page or something, at the same time mentioning how it is
different that other thing... Thanks.

Bug#920322: No DHCP client software found!

[Harald Dunkel]

Package: dhcpcd5
Version: 7.0.8-1
Severity: Grave

After the upgrade dhcpcd5 appears to be broken:


# dpkg -i ~/dhcpcd5_7.0.8-1_amd64.deb
(Reading database ... 276261 files and directories currently installed.)
Preparing to unpack .../root/dhcpcd5_7.0.8-1_amd64.deb ...
Unpacking dhcpcd5 (7.0.8-1) over (7.0.8-0.1) ...
dpkg: warning: unable to delete old directory '/var/lib/dhcpcd5': Directory not 
empty
Setting up dhcpcd5 (7.0.8-1) ...
Installing new version of config file /etc/init.d/dhcpcd ...
update-alternatives: warning: alternative /sbin/dhcpcd5 (part of link group 
dhcpcd) doesn't exist; removing from list of alternatives
update-alternatives: warning: /etc/alternatives/dhcpcd is dangling; it will be 
updated with best choice
Processing triggers for man-db (2.8.5-1) ...
# ifup br0

Waiting for br0 to get ready (MAXWAIT is 1 seconds).
No DHCP client software found!
ifup: failed to bring up br0


Moving back to version 7.0.8-0.1 fixes the problem, but without
network you cannot.


Regards
Harri

Bug#920321: lua5.3: CVE-2019-6706

[Salvatore Bonaccorso]

Source: lua5.3
Version: 5.3.3-1.1
Severity: important
Tags: security upstream
Control: found -1 5.3.3-1

Hi,

The following vulnerability was published for lua5.3.

CVE-2019-6706[0]:
| Lua 5.3.5 has a use-after-free in lua_upvaluejoin in lapi.c. For
| example, a crash outcome might be achieved by an attacker who is able
| to trigger a debug.upvaluejoin call in which the arguments have certain
| relationships.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-6706
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6706

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#919856: [pkg-gnupg-maint] Bug#919856: gpg-agent: agent refuses operation again

[NIIBE Yutaka]

Thanks for your patience.

I think I identified an issue in your debug log.  Not yet catch the bug,
though.

The problem is caching passphrase by libsecret using
gnome-keyring-daemon.  I believe that possible workaround is having
"no-allow-external-cache" in your .gnupg/gpg-agent.conf.


Let me explain, following the log...

> 2019/01/24 12:02:47.157702  length=37 from=15 to=51
OPTION allow-external-password-cache
< 2019/01/24 12:02:47.157773  length=3 from=40 to=42
OK

Here, gpg-agent sets allow-external-password-cache option.

> 2019/01/24 12:02:47.159062  length=54 from=536 to=589
SETKEYINFO s/A337DE390143074C6DBFEA64224359B9859B02FC
< 2019/01/24 12:02:47.159127  length=3 from=193 to=195
OK

Here, gpg-agent informs pinentry for keyinfo (it works as cache
identifier).  "s/" stands for SSH, and A3...FC is the keygrip.

And then, GETPIN is issued from gpg-agent, (I think) pinentry must
examine the cache by the function
secret_password_lookup_nonpageable_sync in libsecret.

> 2019/01/24 12:02:47.159342  length=7 from=723 to=729
GETPIN
< 2019/01/24 12:02:47.175799  length=25 from=202 to=226
S PASSWORD_FROM_CACHE
OK

This means cache hits, and passphrase is "" (empty).  This is wrong.

I guess, for some unknow reason, secret_password_lookup_nonpageable_sync
seems to return "", where NULL is expected (because of no cache hit).
Something is going wrong in libsecret, it is related to gnome-keyring
service.


In GNOME Desktop, it is gnome-keyring-daemon which handles secret store.
Please check your gnome-keyring-daemon is running correctly.  It's in
gnome-keyring package.

You are using gpg-agent as ssh-agent.  Please don't activate
gnome-keyring-daemon's feature as ssh-agent.
-- 

Bug#920320: initscripts: Inverted check in /run symlink logic

[Pierre Ynard]

Package: initscripts
Version: 2.88dsf-59
Severity: normal
Tags: patch

It seems to me that the function run_migrate() in /lib/init/mount-functions.sh
has an inverted check:

> # Create symlink if not already present.
> if [ -L "$OLD" ] && [ "$(readlink "$OLD")" != "$RUN" ]; then
> :
> else
> rm -f "$OLD"
> ln -fs "$RUN" "$OLD"
> [ -x /sbin/restorecon ] && /sbin/restorecon "$OLD"
> fi

This will attempt to correct the symlink if $OLD and $RUN already match,
instead of the contrary. This seems to have got broken in:

https://salsa.debian.org/debian/sysvinit/commit/097799738cf971fac9928e84bcdb6f4b916ce021#3c02e03bae53ff69719346b21039033d8f9809ed_279_277

The impact is uncertain since there's a piece of code already doing
something similar above it. This is rather awkward and the code has
apparently evolved into that cruft after two changes of mind during the
migration.

Personally I noticed it because despite having a correct symlink on my
system, I get a visible error log that removing /dev/shm is impossible
because the file system is read-only (#818442). And also that code is
reached only after the stat checks fail because /usr isn't available.

I suppose it should be looked into whether the redundant transition
logic is still needed or going to be needed, but I guess that inverted
check should at least be fixed with the attached patch.

-- System Information:
Debian Release: 8.11
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable-proposed-updates'), 
(500, 'oldstable')
Architecture: i386 (i586)

Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages initscripts depends on:
ii  coreutils   8.23-4
ii  debianutils 4.4+b1
ii  libc6   2.19-18+deb8u10
ii  lsb-base4.1+Debian13+nmu1
ii  mount   2.25.2-6
ii  sysv-rc 2.88dsf-59
ii  sysvinit-utils  2.88dsf-59

Versions of packages initscripts recommends:
ii  e2fsprogs  1.42.12-2+b1
ii  psmisc 22.21-2

initscripts suggests no packages.

-- Configuration Files:
/etc/default/rcS changed [not included]

-- no debconf information
--- sysvinit-2.93/debian/src/initscripts/lib/init/mount-functions.sh	2019-01-19 22:28:14.0 +0100
+++ sysvinit-2.93/debian/src/initscripts/lib/init/mount-functions.sh	2019-01-24 03:43:29.889549393 +0100
@@ -378,7 +378,7 @@
 		mount -t $FSTYPE "$RUN" "$OLD" $OPTS
 	else
 		# Create symlink if not already present.
-		if [ -L "$OLD" ] && [ "$(readlink "$OLD")" != "$RUN" ]; then
+		if [ -L "$OLD" ] && [ "$(readlink "$OLD")" = "$RUN" ]; then
 			:
 		else
 			rm -f "$OLD"

Bug#911734: yubikey-luks: enrolling yubikey does not work

[Norbert Preining]

Hi Markus,

> Should be fixed with 0.5.1+29.g5df2b95-1.

Confirmed. Thanks a lot for fixing that.

Sooner or later I will play around with the suspend thingy and will
report my experiences.

All the best

Norbert

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

Bug#920319: boost1.67: outdated embedded data copy: unicode-data

[Paul Wise]

Source: boost1.67
Severity: normal
Usertags: embed

Unicode 11.0 was released and unicode-data 11.0.0-1 was uploaded.

The boost1.67 source package contains embedded data copies of several
files from the unicode-data package:

libs/spirit/include/boost/spirit/home/support/char_encoding/unicode/UnicodeData.txt
libs/spirit/include/boost/spirit/home/support/char_encoding/unicode/DerivedCoreProperties.txt
libs/spirit/include/boost/spirit/home/support/char_encoding/unicode/Scripts.txt
libs/spirit/include/boost/spirit/home/support/char_encoding/unicode/PropList.txt

Upstream appears to have converted those files into these files before
releasing the tarball. One of those files (query.hpp) is generated by a
python script that is not available in the source package, I think this
is therefore a severity serious bug but I'm not sure.

libs/spirit/include/boost/spirit/home/support/char_encoding/unicode/script_table.hpp
libs/spirit/include/boost/spirit/home/support/char_encoding/unicode/uppercase_table.hpp
libs/spirit/include/boost/spirit/home/support/char_encoding/unicode/category_table.hpp
libs/spirit/include/boost/spirit/home/support/char_encoding/unicode/query.hpp
libs/spirit/include/boost/spirit/home/support/char_encoding/unicode/lowercase_table.hpp

These files are then shipped in the libboost1.67-dev binary package.

Please ask upstream to remove the above files from the source package
and instead build-depend on the unicode-data binary package and convert
the relevant files to headers at build time.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#920318: bugs.debian.org: Keyboard and Touchpad Not working after Kernel Upgrade

[Steve]

Package: bugs.debian.org
Severity: important

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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

An automatic Debian upgrade notification came through and I rebooted for the
upgrade to take effect.  After reboot the mouse and keyboard did not work on my
laptop.

The keyboard did work in the boot loader and I was able to boot to the old
version and everything worked as expected.  Linux Visio-Laptop 4.9.0-7-amd64 is
the working version.   When booting to Linux Visio-Laptop 4.9.0-8-amd64 the
keyboard and touchpad do not work.

Laptop information:
CPU
Intel Core i7 3517U @ 1.90GHz   56 °C
Ivy Bridge 22nm Technology
RAM
4.00GB Dual-Channel DDR3 @ 665MHz (9-9-9-24)
Motherboard
Quanta VZ1 (SOCKET 0)
Graphics
Intel HD Graphics 4000 (QUANTA Computer)
Storage
238GB TOSHIBA THNSNS256GMCP (SSD)
Optical Drives
No optical disk drives detected
Audio
Intel Display Audio



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

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

Bug#920317: DEB822 .sources confused by comment-only paragraph

[Trent W. Buck]

Package: apt
Version: 1.8.0~alpha3.1
Severity: minor

When using the new DEB822 .sources format,
if you have a paragraph with only comments in it,
apt interprets this as a stanza with no values in it.
An example "broken.sources" is attached.



-- Package-specific info:

-- apt-config dump --

APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "true";
APT::Install-Suggests "0";
APT::Sandbox "";
APT::Sandbox::User "_apt";
APT::Authentication "";
APT::Authentication::TrustCDROM "true";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*$";
APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*-[a-z0-9]*$";
APT::NeverAutoRemove:: "^linux-image-4\.18\.0-3-amd64$";
APT::NeverAutoRemove:: "^linux-image-4\.19\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-headers-4\.18\.0-3-amd64$";
APT::NeverAutoRemove:: "^linux-headers-4\.19\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-4\.18\.0-3-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-4\.19\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-modules-4\.18\.0-3-amd64$";
APT::NeverAutoRemove:: "^linux-modules-4\.19\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-modules-extra-4\.18\.0-3-amd64$";
APT::NeverAutoRemove:: "^linux-modules-extra-4\.19\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-4\.18\.0-3-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-4\.19\.0-1-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-4\.18\.0-3-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-4\.19\.0-1-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-4\.18\.0-3-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-4\.19\.0-1-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-4\.18\.0-3-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-4\.19\.0-1-amd64$";
APT::NeverAutoRemove:: "^.*-modules-4\.18\.0-3-amd64$";
APT::NeverAutoRemove:: "^.*-modules-4\.19\.0-1-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-4\.18\.0-3-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-4\.19\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.18\.0-3-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.19\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-modules-.*-4\.18\.0-3-amd64$";
APT::NeverAutoRemove:: "^linux-modules-.*-4\.19\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-tools-4\.18\.0-3-amd64$";
APT::NeverAutoRemove:: "^linux-tools-4\.19\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-cloud-tools-4\.18\.0-3-amd64$";
APT::NeverAutoRemove:: "^linux-cloud-tools-4\.19\.0-1-amd64$";
APT::VersionedKernelPackages "";
APT::VersionedKernelPackages:: "linux-image";
APT::VersionedKernelPackages:: "linux-headers";
APT::VersionedKernelPackages:: "linux-image-extra";
APT::VersionedKernelPackages:: "linux-modules";
APT::VersionedKernelPackages:: "linux-modules-extra";
APT::VersionedKernelPackages:: "linux-signed-image";
APT::VersionedKernelPackages:: "kfreebsd-image";
APT::VersionedKernelPackages:: "kfreebsd-headers";
APT::VersionedKernelPackages:: "gnumach-image";
APT::VersionedKernelPackages:: ".*-modules";
APT::VersionedKernelPackages:: ".*-kernel";
APT::VersionedKernelPackages:: "linux-backports-modules-.*";
APT::VersionedKernelPackages:: "linux-modules-.*";
APT::VersionedKernelPackages:: "linux-tools";
APT::VersionedKernelPackages:: "linux-cloud-tools";
APT::Never-MarkAuto-Sections "";
APT::Never-MarkAuto-Sections:: "metapackages";
APT::Never-MarkAuto-Sections:: "contrib/metapackages";
APT::Never-MarkAuto-Sections:: "non-free/metapackages";
APT::Never-MarkAuto-Sections:: "restricted/metapackages";
APT::Never-MarkAuto-Sections:: "universe/metapackages";
APT::Never-MarkAuto-Sections:: "multiverse/metapackages";
APT::Move-Autobit-Sections "";
APT::Move-Autobit-Sections:: "oldlibs";
APT::Move-Autobit-Sections:: "contrib/oldlibs";
APT::Move-Autobit-Sections:: "non-free/oldlibs";
APT::Move-Autobit-Sections:: "restricted/oldlibs";
APT::Move-Autobit-Sections:: "universe/oldlibs";
APT::Move-Autobit-Sections:: "multiverse/oldlibs";
APT::Default-Release "buster";
APT::Periodic "";
APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Unattended-Upgrade "1";
APT::Update "";
APT::Update::Post-Invoke "";
APT::Update::Post-Invoke:: "[ ! -x /usr/bin/debtags ] || debtags update || 
true";
APT::Architectures "";
APT::Architectures:: "amd64";
APT::Compressor "";
APT::Compressor::. "";
APT::Compressor::.::Name ".";
APT::Compressor::.::Extension "";
APT::Compressor::.::Binary "";
APT::Compressor::.::Cost "0";
APT::Compressor::zstd "";
APT::Compressor::zstd::Name "zstd";
APT::Compressor::zstd::Extension ".zst";
APT::Compressor::zstd::Binary "false";
APT::Compressor::zstd::Cost "60";
APT::Compressor::lz4 "";
APT::Compressor::lz4::Name "lz4";
APT::Compressor::lz4::Extension ".lz4";
APT::Compressor::lz4::Binary "lz4";
APT::Compressor::lz4::Cost "50";
APT::Compressor::lz4::CompressArg "";
APT::Compressor::lz4::CompressArg:: "-1";

Bug#901365: inform6-library: Inform6 Library has been updated to 6.12.2

[Ben Finney]

On 08-Jul-2018, David Griffith wrote:
> On Tue, 12 Jun 2018, Ben Finney wrote:
> 
> > I also saw you announce that the releases will now be somewhere
> > other than GitHub? What URL should recipients watch for future
> > source releases?
> 
> The Library is now at https://gitlab.com/DavidGriffith/inform6lib

At that URL the “Releases” link leads to a page
https://gitlab.com/DavidGriffith/inform6lib/releases>
that shows there are no releases yet. Can you arrange to have each
release, past and when each one is released, appear there for download
as a tarball whose name contains the version?

Once there is a page that can be automatically polled for new
predictably-named release tarballs, I can update the Debian packaging
to poll the Releases URL.

-- 
 \   “When I was little, my grandfather used to make me stand in a |
  `\   closet for five minutes without moving. He said it was elevator |
_o__)practice.” —Steven Wright |
Ben Finney 

Bug#920316: RM: ifpgui -- ROM; abandoned upstream; Qt4 removal

[tony mancill]

Package: ftp.debian.org
Severity: normal

Requesting removal as per #920280 [1].  ifpgui is for ancient
hardware and is no longer supported upstream.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920280


signature.asc
Description: PGP signature

Bug#920280: ifpgui: Shall we remove this package?

[tony mancill]

On Wed, Jan 23, 2019 at 10:09:10AM -0500, Boyuan Yang wrote:
> Package: ifpgui
> Severity: important
> X-Debbugs-CC: ja...@gnifty.net tmanc...@debian.org
> 
> Dear ifpgui maintainers,
> 
> I found package package ifpgui inactive for several years and now it is
> affected by Qt4 Removal in the Debian Archive [1]. It seems that upstream has
> stopped development since 2013 as well. As a result, I'm wondering if we could
> remove this package from the archive soon.
> 
> If there's no response, I will file a Removal bug to FTP Masters 28 days
> later.

Hello Boyuan Yang,

No concerns from me either.  Since Jacob is busy, I'll file the removal
request.

Thank you,
tony


signature.asc
Description: PGP signature

Bug#919856: [pkg-gnupg-maint] Bug#919856: gpg-agent: agent refuses operation again

[Norbert Preining]

Hi,

thanks for your detailed explanations and help!

I followed your procedure to the point (besides location of mypinentry
and the respective setting in gpg-agent.conf).

I attach the two files that are generated in /run/user/1000

The output on screen was as ususal 
sign_and_send_pubkey: signing failed: agent refused operation
sign_and_send_pubkey: signing failed: agent refused operation

In the log there is the following finish:

> 2019/01/24 12:02:47.159342  length=7 from=723 to=729
GETPIN
< 2019/01/24 12:02:47.175799  length=25 from=202 to=226
S PASSWORD_FROM_CACHE
OK

I hope you can make something out of all that.

Thanks a lot

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Thu 24 Jan 2019 12:02:47 PM JST
lrwxrwxrwx 1 root root 24 Jan 24 12:01 /etc/alternatives/pinentry -> 
/usr/bin/pinentry-gnome3
--display \:0
LANGUAGE=en_US:en
USER=norbert
XDG_SEAT=seat0
XDG_SESSION_TYPE=x11
HOME=/home/norbert
QT4_IM_MODULE=fcitx
LISTEN_PID=3343
LISTEN_FDS=4
DESKTOP_SESSION=cinnamon
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
MANAGERPID=2300
GSM_SKIP_SSH_AGENT_WORKAROUND=true
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
IM_CONFIG_PHASE=1
QT_QPA_PLATFORMTHEME=qt5ct
LOGNAME=norbert
GTK_IM_MODULE=fcitx
JOURNAL_STREAM=9:40941
XDG_SESSION_CLASS=user
GTK_OVERLAY_SCROLLING=0
XDG_SESSION_ID=2
GNOME_DESKTOP_SESSION_ID=this-is-deprecated
PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
GDM_LANG=en_US.utf8
SESSION_MANAGER=local/bulldog:@/tmp/.ICE-unix/2318,unix/bulldog:/tmp/.ICE-unix/2318
INVOCATION_ID=b1ed65195af44acf8a15ad708d1c8431
XDG_RUNTIME_DIR=/run/user/1000
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
LISTEN_FDNAMES=browser:ssh:std:extra
LANG=en_US.UTF-8
XDG_CURRENT_DESKTOP=X-Cinnamon
XAUTHORITY=/home/norbert/.Xauthority
XDG_SESSION_DESKTOP=cinnamon
XMODIFIERS=@im=fcitx
SSH_AUTH_SOCK=/run/user/1000/gnupg/S.gpg-agent.ssh
XDG_GREETER_DATA_DIR=/var/lib/lightdm/data/norbert
SHELL=/bin/bash
_assuan_pipe_connect_pid=3343
GDMSESSION=cinnamon
QT_ACCESSIBILITY=1
GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
QT_IM_MODULE=fcitx
XDG_VTNR=7
PWD=/home/norbert
CLUTTER_IM_MODULE=xim
XDG_DATA_DIRS=/usr/share/gnome:/usr/local/share/:/usr/share/
< 2019/01/24 12:02:47.157402  length=37 from=0 to=36
OK Pleased to meet you, process 3343
> 2019/01/24 12:02:47.157570  length=15 from=0 to=14
OPTION no-grab
< 2019/01/24 12:02:47.157656  length=3 from=37 to=39
OK
> 2019/01/24 12:02:47.157702  length=37 from=15 to=51
OPTION allow-external-password-cache
< 2019/01/24 12:02:47.157773  length=3 from=40 to=42
OK
> 2019/01/24 12:02:47.157843  length=22 from=52 to=73
OPTION default-ok=_OK
< 2019/01/24 12:02:47.157932  length=3 from=43 to=45
OK
> 2019/01/24 12:02:47.157967  length=30 from=74 to=103
OPTION default-cancel=_Cancel
< 2019/01/24 12:02:47.158014  length=3 from=46 to=48
OK
> 2019/01/24 12:02:47.158039  length=24 from=104 to=127
OPTION default-yes=_Yes
< 2019/01/24 12:02:47.158085  length=39 from=49 to=87
ERR 83886254 Unknown option 
> 2019/01/24 12:02:47.158136  length=22 from=128 to=149
OPTION default-no=_No
< 2019/01/24 12:02:47.158177  length=39 from=88 to=126
ERR 83886254 Unknown option 
> 2019/01/24 12:02:47.158228  length=27 from=150 to=176
OPTION default-prompt=PIN:
< 2019/01/24 12:02:47.158271  length=3 from=127 to=129
OK
> 2019/01/24 12:02:47.158292  length=48 from=177 to=224
OPTION default-pwmngr=_Save in password manager
< 2019/01/24 12:02:47.158354  length=3 from=130 to=132
OK
> 2019/01/24 12:02:47.158375  length=89 from=225 to=313
OPTION default-cf-visi=Do you really want to make your passphrase visible on 
the screen?
< 2019/01/24 12:02:47.158496  length=3 from=133 to=135
OK
> 2019/01/24 12:02:47.158520  length=47 from=314 to=360
OPTION default-tt-visi=Make passphrase visible
< 2019/01/24 12:02:47.158580  length=3 from=136 to=138
OK
> 2019/01/24 12:02:47.158602  length=39 from=361 to=399
OPTION default-tt-hide=Hide passphrase
< 2019/01/24 12:02:47.158655  length=3 from=139 to=141
OK
> 2019/01/24 12:02:47.158677  length=51 from=400 to=450
OPTION touch-file=/run/user/1000/gnupg/S.gpg-agent
< 2019/01/24 12:02:47.158740  length=3 from=142 to=144
OK
> 2019/01/24 12:02:47.158762  length=26 from=451 to=476
OPTION owner=3336 bulldog
< 2019/01/24 12:02:47.158807  length=3 from=145 to=147
OK
> 2019/01/24 12:02:47.158825  length=15 from=477 to=491
GETINFO flavor
< 2019/01/24 12:02:47.158861  length=12 from=148 to=159
D gnome3
OK
> 2019/01/24 12:02:47.158886  length=16 from=492 to=507
GETINFO version
< 2019/01/24 12:02:47.158918  length=11 from=160 to=170
D 1.1.0
OK
> 2019/01/24 12:02:47.158942  length=16 from=508 to=523
GETINFO ttyinfo
< 2019/01/24 12:02:47.158977  length=12 from=171 to=182
D - - :0
OK
> 2019/01/24 12:02:47.159002  length=12 from=524 

Bug#920136: __gmpz_limbs_write

[James Van Zandt]

>I suspect second local installation of gmp/nettle/gnutls in /usr/local.

You're right!

root@home:/usr/local/lib# ls -l libgmp*
  -rw-r--r-- 1 root root 1188388 Jul 22  2017 libgmp.a
  -rwxr-xr-x 1 root root 914 Jul 22  2017 libgmp.la
  lrwxrwxrwx 1 root root  16 Jul 22  2017 libgmp.so -> libgmp.so.10.0.5
  lrwxrwxrwx 1 root root  16 Jul 22  2017 libgmp.so.10 ->
libgmp.so.10.0.5
  -rwxr-xr-x 1 root root  482920 Jul 22  2017 libgmp.so.10.0.5
  -rw-r--r-- 1 root root   39660 Jul 22  2017 libgmpxx.a
  -rwxr-xr-x 1 root root 949 Jul 22  2017 libgmpxx.la
  lrwxrwxrwx 1 root root  17 Jul 22  2017 libgmpxx.so ->
libgmpxx.so.4.2.5
  lrwxrwxrwx 1 root root  17 Jul 22  2017 libgmpxx.so.4 ->
libgmpxx.so.4.2.5
  -rwxr-xr-x 1 root root   24704 Jul 22  2017 libgmpxx.so.4.2.5

I have no idea how or why they got installed.  Regardless, I've removed
them, and "apt --fix-broken install" worked.

Thanks!

and please close the bug.

Bug#893227: libbluray FTBFS with openjdk-9

[Reinhard Tartler]

Hi Adrian,

On Wed, Jan 23, 2019 at 12:54 PM Adrian Bunk  wrote:

> Due to popcon (and reverse dependencies) libbluray is a key package
> that won't be autoremoved (otherwise it would have been autoremoved
> from buster 9 months ago).
>

That's good to know, thanks for pointing it out.


> A lowered severity only hides the problem, and the later it gets brought
> up the fewer changes are permitted for fixing - until the end of February
> you could even upload a new upstream version, but after that it will be
> unlikely that this will be approved by the release team.
>

Well, the question is whether a new upstream version becomes
available in time. The current version does simply not work
at all with OpenJDK11. Given that we need a new upstream release,
which I expect to introduce significant changes, we may run
into trouble with qualifying for a "soft-freeze" update. It
seems safer to upload (and test, i.e., have it migrated to testing),
way before Feb 12 2019.

The libbluray-bdj binary package has no reverse dependencies,
> so removing it might be a Plan B if no better option would
> be available.
>

I just looked at the code, and it doesn't look like it is
possible to build it without OpenJDK-8 at all. There are files
unconditionally built that #include .

You might be suggesting to use OpenJDK-8 to build, but "simply"
not ship the libbluray-bdj package. That would effectively
drop support for BD menus from Debian, which is why I wouldn't
consider this as a viable plan B.

-- 
regards,
Reinhard

Bug#907041: please also build libmtd-dev/mtd-dev and a shared library package

[林上智]

On Thu, 25 Oct 2018 09:51:02 +0200 =?UTF-8?Q?G=C3=BCrkan_Myczko?=
 wrote:
> Package: mtd-utils
> Version: 1:2.0.1-1
> Severity: wishlist
>
> For swupdate[1] be able to get built. mtd-utils needs to also build -dev
> and shared library packages
>
Hi Riku,

Do you have the plan for adding -dev package? I would like to assist
in this part if you don't mind.

Since you're in the list of LowThresholdNmu [1], I will upload it
directly afterwards.

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

SZ

Bug#919856: [pkg-gnupg-maint] Bug#919856: gpg-agent: agent refuses operation again

[NIIBE Yutaka]

Hello,

This is a report of my case.  Sorry, it doesn't have a solution for you
(yet).  I hope you can find some information to try.


I usually invoke gpg-agent manually (because I use my own development
version).  This time, I enable systemd socket activation. 

I did test with installed gnupg together with systemd, so that
/usr/bin/gpg-agent is invoked with --supervised option.

In my case (xfce4 desktop), the first invocation of ssh in terminal on
the desktop (which lets start gpg-agent), pinentry-gnome3 and
pinentry-gtk-2 work fine, while pinentry-qt doesn't.

Perhaps, I need to open another bug report for my use case.  I found
that Qt5 doesn't support application having -display option any more.
This is the cause of my own problem.  I think Qt5 application requires
DISPLAY environment variable (instead of command line option).


What I did is following.

To debug pinentry session, I added this line in my .gnupg/gpg-agent.conf:
==
pinentry-program /home/gniibe/tmp/mypinentry
==


I installed socat by 'apt install socat'.

Using socat, I create /home/gniibe/tmp/mypinentry, having +x:
==
#! /bin/sh

PINENTRY_ARGS=$(echo $@ | sed -e 's/:/\\:/g')

ENV_LOG=/run/user/1000/pinentry-env.txt
date > $ENV_LOG
ls -l /etc/alternatives/pinentry >> $ENV_LOG
/bin/echo -e "$PINENTRY_ARGS" >> $ENV_LOG
env >> $ENV_LOG

exec socat -v STDIO "SYSTEM:/usr/bin/pinentry $PINENTRY_ARGS" 2> 
/run/user/1000/pinentry-log.txt
==

In the file of /run/user/1000/pinentry-env.txt, we can see the
environment variables of pinentry process.

In the file of /run/user/1000/pinentry-log.txt, we can observe the
session of gpg-agent <-> pinentry.  I tweak (escape for ':') the
argument of pinentry, so that it can be in the expression of socat.

Please be aware that this is for debugging.  The session log
may include your passphrase in clear text.


I confirmed that there is no DISPLAY in the environment variables (when
--supervised option).  The pinentry process is invokde with --display
option (when gpg-agent has DISPLAY setting). 
-- 

Bug#618576: xen-3.2-1: VNC display over HVM XEN 3/Lenny AMD64

[Diego Dave]

Hi Hans,

We had this problem a long time ago, and we solved it by using XCP, later
Xenserver and nowadays XCP-ng.

Please close it, thanks.

Diego


Libre
de virus. www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

El dom., 20 ene. 2019 a las 20:10, Hans van Kranenburg ()
escribió:

> tags 618576 + moreinfo
> thanks
>
> Hi Diego,
>
> This is about the bug report about VNC access to a virtual machine that
> you filed before in the Debian bug tracker, against the Xen packages.
>
> Your bug report was targeted at a Xen package in a Debian distribution
> older than the current stable (Stretch).
>
> Can you please help us by confirming that any of the following scenarios
> does apply to your situation?
>
> * I had this problem a long time ago. It was never solved, but I found a
> workaround, which is ...
> * I had this problem a long time ago, and I solved it by not using Xen
> any more, but by doing ...
> * I still experience this problem, and I'm still using Xen
> 3.2/4.1/4.4/etc. I cannot upgrade to Debian Stretch or Buster because ...
> * I had this problem, and since upgrading to Stretch / Buster / ? it
> seems it was solved, and I forgot to report it again. Please close it,
> thanks.
> * Other: ...
>
> Note that even if you found a solution, it's still very useful to report
> it back to our bug tracker. There might be someone else running into the
> same problem, who can be helped with your information.
>
> Please note that unless there's a response within a month from now, we
> will close the bug report. If you discover this message later, and this
> case is important to you, then you can try unarchiving the bug and
> replying to it, or reach out to the maintainers email list at
> pkg-xen-devel at lists.alioth.debian.org (no subscription required) and
> post a message.
>
> Thanks,
> Hans van Kranenburg
>

Bug#920315: openjdk-11: Please cherry-pick sparc64 optimization patch from openjdk-12

[John Paul Adrian Glaubitz]

Source: openjdk-11
Version: 11.0.2+9-2
Severity: normal
Tags: patch
User: debian-sp...@lists.debian.org
Usertags: sparc64

Hello!

Recent upstream changes to the openjdk-11 package have resulted in
Zero segfaulting on sparc64. This can be fixed by cherry-pick the
same fix that we are already using in openjdk-12 to address the
issue [1].

Please include the patch from [1] in the next openjdk-11 upload.

Thanks,
Adrian

> [1] 
> https://git.launchpad.net/~openjdk/ubuntu/+source/openjdk/+git/openjdk/tree/debian/patches/Don-t-optimize-fdlibm-fork-for-Zero-on-linux-sparc-Z.patch

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
>From 7ce2609d6ff5299f2ed3ff6850a3cab4a16125f8 Mon Sep 17 00:00:00 2001
From: John Paul Adrian Glaubitz 
Date: Fri, 21 Dec 2018 15:18:17 +0300
Subject: [PATCH] Don't optimize fdlibm-fork for Zero on linux-sparc (Zero)

---
 make/hotspot/lib/JvmOverrideFiles.gmk | 9 +
 1 file changed, 9 insertions(+)

diff --git a/make/hotspot/lib/JvmOverrideFiles.gmk 
b/make/hotspot/lib/JvmOverrideFiles.gmk
index 7d45dd331a..79c014e82a 100644
--- a/make/hotspot/lib/JvmOverrideFiles.gmk
+++ b/make/hotspot/lib/JvmOverrideFiles.gmk
@@ -49,6 +49,15 @@ LIBJVM_FDLIBM_COPY_OPT_FLAG := $(CXX_O_FLAG_NONE)
 # by using -ffp-contract=off on GCC/Clang platforms.
 ifneq ($(FDLIBM_CFLAGS), )
   LIBJVM_FDLIBM_COPY_OPT_FLAG := $(CXX_O_FLAG_NORM)
+  # Don't optimize fdlibm-fork for Zero on Linux sparc
+  # See JDK-
+  ifeq ($(call check-jvm-feature, zero), true)
+ifeq ($(OPENJDK_TARGET_OS), linux)
+  ifeq ($(OPENJDK_TARGET_CPU_ARCH), sparc)
+LIBJVM_FDLIBM_COPY_OPT_FLAG := $(CXX_O_FLAG_NONE)
+  endif
+endif
+  endif
 endif
 
 ifeq ($(OPENJDK_TARGET_OS), linux)
-- 
2.19.1

Bug#920314: lintian: vcs-field-has-unexpected-spaces has false positives

[Jeremy Bicha]

Source: lintian
Version: 2.5.123

I think all of these are false positives except for rust-num-cpus.

https://lintian.debian.org/tags/vcs-field-has-unexpected-spaces.html

In particular, -b or --branch should be allowed for Vcs-Git (but not
Vcs-Browser). One usecase is tot have a separate branch for each
Debian series.

Because you can then use
git clone https://salsa.debian.org/gnome-team/atk.git -B debian/jessie

It looks like hg works the same way.

Thanks,
Jeremy Bicha

Bug#920288: bfs: acl/libcap dependencies are optional

[Tavian Barnes]

On Wed, 23 Jan 2019 at 17:24, Chris Lamb  wrote:
> Hi Tavian,
>
> > Those dependencies are not required however -- if the headers
> > aren't there, the relevant functionality will be stubbed out
> > automatically.
>
> I'm not actually seeing that; for example, when I build without the
> libacl1-dev and libcap-dev packages installed:
> [snip]

Did you build that on Linux?  -lacl -lcap is added only if $(uname) == Linux:
https://github.com/tavianator/bfs/blob/master/Makefile#L54

Bug#887399: stretch-pu: package python-certbot/0.10.2-1

[Harlan Lieberman-Berg]

Indeed -- sorry about that, everyone!  I intended for that to go out
before I went on vacation (and didn't have email access), but it looks
like I didn't quite manage it.

I'm doing the uploads again now.

On Mon, Jan 21, 2019 at 6:05 AM Julien Cristau  wrote:
>
> On Thu, Jan 17, 2019 at 01:48:24PM -0800, Brad Warren wrote:
> > I just wanted to make sure this was still on everyone’s radar. The
> > change server side where tens of thousands of Debian users will begin
> > being unable to renew their certificates is in less than a month.
> >
> It is, but the initial uploads used the wrong version numbers and had to
> be rejected.  AIUI Harlan should be back this week, hopefully he can get
> to this.
>
> Cheers,
> Julien
>
> > > On Jan 8, 2019, at 4:24 PM, Harlan Lieberman-Berg  
> > > wrote:
> > >
> > > Hello Julien, everyone,
> > >
> > > I've uploaded the relevant packages for your examination.  The
> > > packages uploaded are:
> > >
> > > - python-acme_0.28.0-1+deb9u1
> > > - python-certbot_0.28.0-1+deb9u1
> > > - python-certbot-nginx_0.28.0-1+deb9u1
> > > - python-certbot-apache_0.28.0-1+deb9u1
> > > - python-josepy_1.1.0-2+deb9u1
> > > - parsedatetime_2.1-3+deb9u1
> > >
> > > On Sun, Dec 2, 2018 at 7:55 PM Harlan Lieberman-Berg
> > >  wrote:
> > >>
> > >> On Sun, Dec 2, 2018 at 10:48 AM Julien Cristau  
> > >> wrote:
> > >>> OK, let's do that then.  Sorry for not getting back to this sooner.
> > >>
> > >> Sounds good.  I'm preparing the uploads now.
> > >>
> > >> It looks like I will need to rebuild the version of
> > >> python-parsedatetime in stable to also build the python3 version.  I
> > >> could also backport a newer version that builds python3.  Let me know.
> > >>
> > >> Sincerely,
> > >> --
> > >> Harlan Lieberman-Berg
> > >> ~hlieberman
> > >
> > >
> > >
> > > --
> > > Harlan Lieberman-Berg
> > > ~hlieberman
> > >
> > > --
> > > To unsubscribe, send mail to 887399-unsubscr...@bugs.debian.org.
> > >



-- 
Harlan Lieberman-Berg
~hlieberman

Bug#920313: kbd: kbdrate man page on boot-time setting

[Kevin Ryde]

Package: kbd
Version: 2.0.4-2
Severity: wishlist
Tags: patch
File: /usr/share/man/man8/kbdrate.8.gz

I see the kbdrate man page has FILES /etc/rc.local, which I presume is
for the suggested place of boot-time keyboard rate.  A couple of words
perhaps like below could make that clearer (assuming it's right!).

--- kbdrate.8.orig	2017-09-15 18:33:29.0 +1000
+++ kbdrate.8	2019-01-17 15:55:53.0 +1100
@@ -66,6 +66,11 @@
 (The former usually works on an m68k machine, the latter for SPARC.)
 When these ioctls fail an ioport interface as on i386 is assumed.
 .SH FILES
+.TP
 .I /etc/rc.local
-.br
+Boot-time settings can be made by running
+.B kbdrate
+from
+.IR /etc/rc.local .
+.TP
 .I /dev/port

Bug#915426: git breaks git-remote-hg autopkgtest

[Jonathan Nieder]

Hi Jonas,

Jonas Smedegaard wrote:

> I can do yet another NMU to fix this, but am hesitating as I worry if
> that will masquerade a lack of responsive maintenance.
>
> Please tell if it is sensible that I take over maintenance of this
> package, or join as co-maintainer, or however is appreciated.

I'd be happy if you take over as maintainer.  Sorry for the slow
reply.

When the package was first uploaded, I agreed to be a co-maintainer as
a way to notice issues with Git's remote helper infrastructure.  It
was a bad idea --- I should have just subscribed through the PTS
without being a co-maintainer.

Please feel free to take the package as new sole maintainer, with my
blessing (or even better, to set up a team list to maintain it with
you).

Sincerely,
Jonathan

Bug#840874: O: tint -- TINT Is Not Tetris(tm) ...at least the name isn't

[Ricardo Mones]

control: retitle -1 ITA: tint -- TINT Is Not Tetris(tm) ...at least the name 
isn't
control: owner -1 !

On Sat, 15 Oct 2016 19:23:49 +0200
Tobias Frost  wrote:

> Package: wnpp
> Severity: normal
> 
> The current maintainer of tint, Mario Lang ,
> has retired.  Therefore, I orphan this package now.

Hopefully I'll maintain this package within the Games Team.

regards,
-- 
 Ricardo Mones
 http://people.debian.org/~mones
 «All generalisations are dangerous, including this one.»


pgpFCpMrzc8aK.pgp
Description: Firma digital OpenPGP

Bug#911045: xenstore-utils: removal of xenstore-utils makes files disappear from xen-utils-common

[Hans van Kranenburg]

tags 911045 + pending
thanks

Ok, now this is confusing. For a moment I was thinking that this bug was
cloned because of the "Similar problems in..." and then I couldn't find
the other one.

I just added the Breaks for xenstore-utils jftfoi, so this one is now
both wontfix and pending.

https://salsa.debian.org/xen-team/debian-xen/commit/a8ba67214681b6c5a5d7486550585116f1690ed0

Hans

Bug#916256: gitlab-runner fails when it tries to pull docker image gitlab-runner-helper:11.2.0

[Dean Hamstead]

Seems to be the same as: 
https://gitlab.com/gitlab-org/gitlab-runner/issues/3441

Bug#915426: git breaks git-remote-hg autopkgtest

[Jeremy Bicha]

Jonathan,

Could you please reply to Jonas' message? The deadline for
git-remote-hg to re-enter Testing to be in this year's Debian 10
"Buster" release is February 12.

Thanks,
Jeremy Bicha

> Wed, 02 Jan 2019 13:50:54 +0100
> I can do yet another NMU to fix this, but am hesitating as I worry if
> that will masquerade a lack of responsive maintenance.
>
> Please tell if it is sensible that I take over maintenance of this
> package, or join as co-maintainer, or however is appreciated.
>
> Kind regards,
>
>  - Jonas

Bug#908216: btrfs blocked for more than 120 seconds

[Russell Mosemann]

Package: src:linux
Version: 4.19.12-1~bpo9+1
Severity: important
 
Jan 23 17:16:23 vhost002 kernel: INFO: task btrfs-transacti:638 blocked for 
more than 120 seconds.
Jan 23 17:16:23 vhost002 kernel:   Tainted: GE 
4.19.0-0.bpo.1-amd64 #1 Debian 4.19.12-1~bpo9+1
Jan 23 17:16:23 vhost002 kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 23 17:16:23 vhost002 kernel: btrfs-transacti D0   638  2 0x8000
Jan 23 17:16:23 vhost002 kernel: Call Trace:
Jan 23 17:16:23 vhost002 kernel:  ? __schedule+0x3f5/0x880
Jan 23 17:16:23 vhost002 kernel:  schedule+0x32/0x80
Jan 23 17:16:23 vhost002 kernel:  btrfs_start_ordered_extent+0xed/0x120 [btrfs]
Jan 23 17:16:23 vhost002 kernel:  ? remove_wait_queue+0x60/0x60
Jan 23 17:16:23 vhost002 kernel:  btrfs_wait_ordered_range+0xa0/0x100 [btrfs]
Jan 23 17:16:23 vhost002 kernel:  __btrfs_wait_cache_io+0x46/0x1c0 [btrfs]
Jan 23 17:16:23 vhost002 kernel:  btrfs_start_dirty_block_groups+0x1ad/0x4b0 
[btrfs]
Jan 23 17:16:23 vhost002 kernel:  btrfs_commit_transaction+0xc8/0x8a0 [btrfs]
Jan 23 17:16:23 vhost002 kernel:  ? start_transaction+0x8f/0x3e0 [btrfs]
Jan 23 17:16:23 vhost002 kernel:  transaction_kthread+0x157/0x180 [btrfs]
Jan 23 17:16:23 vhost002 kernel:  kthread+0xf8/0x130
Jan 23 17:16:23 vhost002 kernel:  ? btrfs_cleanup_transaction+0x500/0x500 
[btrfs]
Jan 23 17:16:23 vhost002 kernel:  ? kthread_create_worker_on_cpu+0x70/0x70
Jan 23 17:16:23 vhost002 kernel:  ret_from_fork+0x35/0x40
Jan 23 17:16:24 vhost002 su[24190]: Successful su for nobody by root
Jan 23 17:16:24 vhost002 su[24190]: + ??? root:nobody

Jan 23 17:18:24 vhost002 kernel: INFO: task btrfs-transacti:638 blocked for 
more than 120 seconds.
Jan 23 17:18:24 vhost002 kernel:   Tainted: GE 
4.19.0-0.bpo.1-amd64 #1 Debian 4.19.12-1~bpo9+1
Jan 23 17:18:24 vhost002 kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 23 17:18:24 vhost002 kernel: btrfs-transacti D0   638  2 0x8000
Jan 23 17:18:24 vhost002 kernel: Call Trace:
Jan 23 17:18:24 vhost002 kernel:  ? __schedule+0x3f5/0x880
Jan 23 17:18:24 vhost002 kernel:  schedule+0x32/0x80
Jan 23 17:18:24 vhost002 kernel:  btrfs_start_ordered_extent+0xed/0x120 [btrfs]
Jan 23 17:18:24 vhost002 kernel:  ? remove_wait_queue+0x60/0x60
Jan 23 17:18:24 vhost002 kernel:  btrfs_wait_ordered_range+0xa0/0x100 [btrfs]
Jan 23 17:18:24 vhost002 kernel:  __btrfs_wait_cache_io+0x46/0x1c0 [btrfs]
Jan 23 17:18:24 vhost002 kernel:  btrfs_start_dirty_block_groups+0x1ad/0x4b0 
[btrfs]
Jan 23 17:18:24 vhost002 kernel:  btrfs_commit_transaction+0xc8/0x8a0 [btrfs]
Jan 23 17:18:24 vhost002 kernel:  ? start_transaction+0x8f/0x3e0 [btrfs]
Jan 23 17:18:24 vhost002 kernel:  transaction_kthread+0x157/0x180 [btrfs]
Jan 23 17:18:24 vhost002 kernel:  kthread+0xf8/0x130
Jan 23 17:18:24 vhost002 kernel:  ? btrfs_cleanup_transaction+0x500/0x500 
[btrfs]
Jan 23 17:18:24 vhost002 kernel:  ? kthread_create_worker_on_cpu+0x70/0x70
Jan 23 17:18:24 vhost002 kernel:  ret_from_fork+0x35/0x40
Jan 23 17:20:25 vhost002 kernel: INFO: task btrfs-transacti:638 blocked for 
more than 120 seconds.
Jan 23 17:20:25 vhost002 kernel:   Tainted: GE 
4.19.0-0.bpo.1-amd64 #1 Debian 4.19.12-1~bpo9+1
Jan 23 17:20:25 vhost002 kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 23 17:20:25 vhost002 kernel: btrfs-transacti D0   638  2 0x8000
Jan 23 17:20:25 vhost002 kernel: Call Trace:
Jan 23 17:20:25 vhost002 kernel:  ? __schedule+0x3f5/0x880
Jan 23 17:20:25 vhost002 kernel:  schedule+0x32/0x80
Jan 23 17:20:25 vhost002 kernel:  btrfs_start_ordered_extent+0xed/0x120 [btrfs]
Jan 23 17:20:25 vhost002 kernel:  ? remove_wait_queue+0x60/0x60
Jan 23 17:20:25 vhost002 kernel:  btrfs_wait_ordered_range+0xa0/0x100 [btrfs]
Jan 23 17:20:25 vhost002 kernel:  __btrfs_wait_cache_io+0x46/0x1c0 [btrfs]
Jan 23 17:20:25 vhost002 kernel:  btrfs_start_dirty_block_groups+0x1ad/0x4b0 
[btrfs]
Jan 23 17:20:25 vhost002 kernel:  btrfs_commit_transaction+0xc8/0x8a0 [btrfs]
Jan 23 17:20:25 vhost002 kernel:  ? start_transaction+0x8f/0x3e0 [btrfs]
Jan 23 17:20:25 vhost002 kernel:  transaction_kthread+0x157/0x180 [btrfs]
Jan 23 17:20:25 vhost002 kernel:  kthread+0xf8/0x130
Jan 23 17:20:25 vhost002 kernel:  ? btrfs_cleanup_transaction+0x500/0x500 
[btrfs]
Jan 23 17:20:25 vhost002 kernel:  ? kthread_create_worker_on_cpu+0x70/0x70
Jan 23 17:20:25 vhost002 kernel:  ret_from_fork+0x35/0x40

Jan 23 17:22:26 vhost002 kernel: INFO: task btrfs-transacti:638 blocked for 
more than 120 seconds.
Jan 23 17:22:26 vhost002 kernel:   Tainted: GE 
4.19.0-0.bpo.1-amd64 #1 Debian 4.19.12-1~bpo9+1
Jan 23 17:22:26 vhost002 kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 23 17:22:26 vhost002 kernel: btrfs-transacti D0   638  2 0x8000
Jan 23 17:22:26 vhost002 kernel: Call Trace:
Jan 23 17:22:26 vhost002 kernel:  ? 

Bug#911045: xen-hypervisor should declare Breaks

[Hans van Kranenburg]

tags 911045 + wontfix
thanks

Hi,

Like Ian said, the upgrade scenario here is to install the new Xen
hypervisor packages, then reboot. If something horrible happens, it's
possible to boot again with the previous Xen and try fix it and retry
the reboot. If successful, remove the 4.8-related packages.

So, the addition of a Breaks that will forcibly remove the 4.8
hypervisor boot option here is not in the interest of the end user at all.

I nonetheless fully agree that there has been a mistake made in the past
by having the grub.d/xen.cfg been addded into the hypervisor
version-specific package, instead of a -common one.

-- 
Hans van Kranenburg

Bug#920311: ITP: connman-gtk -- fully-featured GUI for ConnMan with systray support

[Nick Morrott]

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

* Package name: connman-gtk
  Version : 1.1.1+git20180626.b72c6ab
  Upstream Author : Jaakko Hannikainen 
* URL : https://github.com/jgke/connman-gtk
* License : GPL-2.0+
  Programming Lang: C
  Description : fully-featured GUI for ConnMan with systray support

connman-gtk is a fully-featured GTK3 GUI for ConnMan with system tray
support.

connman-gtk targets all WMs/DMs. It works on any Linux WM/DM which
provides a freedesktop-compliant system tray. (GNOME, KDE, Xfce,
i3, awesome...)

It supports the following features provided by the ConnMan API:

 * enable/disable a technology (Wired, Wi-Fi, Bluetooth, Cellular, P2P)
 * connect to/disconnect from a service
 * configure a service (IPv4, IPv6, DNS, NTP, proxies)
 * share current connection (tethering)

connman-gtk is intended as the de-facto replacement for connman-ui.

Bug#916256: gitlab-runner fails when it tries to pull docker image gitlab-runner-helper:11.2.0

[Dean Hamstead]

This is doomed to fail with the default logic for the helper_image 
default


Per 
https://docs.gitlab.com/runner/configuration/advanced-configuration.html#helper-image


and

https://docs.gitlab.com/runner/configuration/advanced-configuration.html#overriding-the-helper-image

Bug#920310: quagga: unnecessary Build-Depends on pcre3

[Jeremy Bicha]

Source: quagga
Version: 1.2.4-2
Severity: minor

While investigating packages in Ubuntu main that use pcre3, I noticed
that quagga Build-Depends on libpcre3-dev. However, it is not actually
used during the build since quagga defaults to using the GNU regexp
library unless we used --enable-pcreposix which we don't.

pcre3 is the older library (despite its confusing name) and we're
trying to use pcre2 instead.

So I recommend just dropping libpcre3-dev from your Build-Depends.

Thanks,
Jeremy Bicha

Bug#915063: xen-hypervisor-4.8-amd64: xen 4.8 fails to boot

[Hans van Kranenburg]

tags 915063 + moreinfo
thanks

Hi Gregory,

I'm tagging this report moreinfo now, since it clearly needs your
cooperation to advance.

Please let us know if you have addition information on what you were
trying to do, and which exact error messages you encoutered etc...

We might close this bug in the future if there's no response any more.

Thanks,
Hans

Bug#911046: xen-utils-common: broken symlink: /usr/share/doc/xen-utils-common/html -> ../xen/html

[Hans van Kranenburg]

tags 911046 + pending
thanks

Hi Andreas,

Yes, you're right. I just added a Suggests: xen-doc to it, I hope that
will alleviate the issue:

https://salsa.debian.org/xen-team/debian-xen/commit/b6909b92f28cd388f390f1c99c2f3f1e06b59cfa

Thanks,
Hans

Bug#901602: xen-system-amd64: AMD Epyc firmware bug, try to use APIC520

[Hans van Kranenburg]

tags 901602 + moreinfo
thanks

Hi Stefan,

I'm going over open bug reports for the Xen packages in Debian, and I
ran into this one.

I think you might at least want to try out Debian Buster with the Xen
4.11 packages which might provide better support for your hardware.

However, I think you might even be better of searching the upstream
xen-users and xen-devel mailing lists archive about epyc, and maybe
subscribing to them instead to join discussions.

I don't think any of the users in the debian xen packages maintainer
team is actively using this hardware now, and for solving the issues you
will likely need help from upstream Xen developers. So, it might be
possible we would only be slowing you down.

Thanks,
Hans

Bug#915133: python-coverage: autopkgtest needs update for new version of python3-defaults

[Ben Finney]

On 23-Jan-2019, Paul Gevers wrote:
> I only know the above because I had ~25 package failing in a very
> similar way. Apart from adding a test dependency on python3-all to
> install all versions, I don't know how to test for all installed
> versions. Maybe ask the maintainers of python3-defaults?

No worries, thanks for the response. I will ask in the
‘debian-python’ forum.

-- 
 \  “On the internet you simply can't outsource parenting.” —Eliza |
  `\  Cussen, _Top 10 Internet Filter Lies_, The Punch, 2010-03-25 |
_o__)  |
Ben Finney 

Bug#908771: HP Proliant iLO Virtual Serial Port gets stuck during Xen boot at "Brought up "

[Hans van Kranenburg]

tags 908771 + moreinfo
thanks

Hi Hans,

This is about the bug report about the serial console getting stuck with
HP proliant servers that you filed before in the Debian bug tracker,
against the Xen packages.

Your bug report was targeted at a Xen package in a Debian distribution
older than the current stable (Stretch).

Can you please help us by confirming that any of the following scenarios
does apply to your situation?

* I had this problem a long time ago. It was never solved, but I found a
workaround, which is ...
* I had this problem a long time ago, and I solved it by not using Xen
any more, but by doing ...
* I still experience this problem, and I'm still using Xen
3.2/4.1/4.4/etc. I cannot upgrade to Debian Stretch or Buster because ...
* I had this problem, and since upgrading to Stretch / Buster / ? it
seems it was solved, and I forgot to report it again. Please close it,
thanks.
* Other: ...

Note that even if you found a solution, it's still very useful to report
it back to our bug tracker. There might be someone else running into the
same problem, who can be helped with your information.

Please note that unless there's a response within a month from now, we
will close the bug report. If you discover this message later, and this
case is important to you, then you can try unarchiving the bug and
replying to it, or reach out to the maintainers email list at
pkg-xen-devel at lists.alioth.debian.org (no subscription required) and
post a message.

Thanks,
Hans van Kranenburg

Bug#869123: task xenconsoled blocked in state D after reboot

[Hans van Kranenburg]

tags 869123 + moreinfo
thanks

Hi Hans,

This is about the bug report about xenconsoled ending up in state D that
you filed before in the Debian bug tracker, against the Xen packages.

Your bug report was targeted at a Xen package in a Debian distribution
older than the current stable (Stretch).

Can you please help us by confirming that any of the following scenarios
does apply to your situation?

* I had this problem a long time ago. It was never solved, but I found a
workaround, which is ...
* I had this problem a long time ago, and I solved it by not using Xen
any more, but by doing ...
* I still experience this problem, and I'm still using Xen
3.2/4.1/4.4/etc. I cannot upgrade to Debian Stretch or Buster because ...
* I had this problem, and since upgrading to Stretch / Buster / ? it
seems it was solved, and I forgot to report it again. Please close it,
thanks.
* Other: ...

Note that even if you found a solution, it's still very useful to report
it back to our bug tracker. There might be someone else running into the
same problem, who can be helped with your information.

Please note that unless there's a response within a month from now, we
will close the bug report. If you discover this message later, and this
case is important to you, then you can try unarchiving the bug and
replying to it, or reach out to the maintainers email list at
pkg-xen-devel at lists.alioth.debian.org (no subscription required) and
post a message.

Thanks,
Hans van Kranenburg

Bug#821408: Pam 1.3.0

[Florian Vessaz]

Hello Andreas and Steve,

On Wed, Jan 23, 2019 at 01:29:07PM +0100, Andreas Henriksson wrote:
> Hello Florian and Steve,
> 
> On Tue, Jan 22, 2019 at 02:40:00PM -0800, Steve Langasek wrote:
> > On Tue, Jan 22, 2019 at 09:12:31PM +0100, Florian Vessaz wrote:
> > > We've got no reply from the current maintainers to this bug report since
> > > the approximately 2 and a half years it has been opened. I thus think
> > > it's safe to presume the current maintainers have no interest in keeping
> > > PAM up-to-date in Debian.
> 
> Sorry for not having found time to look at this. I'm still very
> interested in seeing improvements on the PAM side, I'm just very short
> on spare time.
> 
> FWIW I think the chance for getting changes into buster has most likely
> passed already. Atleast I wouldn't feel comfortable introducing alot
> of changes this late in the release cycle. I think it's better to target
> experimental now and then upload to unstable early in the bullseye
> cycle.

I'll see what happens when Buster is released, but it currently appears
to me that not having a reasonably up-to-date version of PAM available
might, for me, be a deal breaker that will make me reconsider my usage
and support of Debian.

> > Wow, that's an incredible conclusion less than 2 weeks after a maintainer
> > upload.
> > 
[...]
> > (I appreciate your past efforts to handle this migration, but in your own
> > words "the history of the packaging is not pretty" and I was unwilling to
> > accept an incomplete history of the packaging.)
> 
> Thanks for joining the discussion. I'm sure we can elaborate eternally
> on our definitions of "properly maintaining" and the tradeoffs between
> pretty git histories and having users suffer the consequenses of
> the outstanding bugs for yet another release cycle, but lets proceed
> to something more productive.

Thank you for joining, I'm glad that it finally looks possible to get
an up-to-date PAM version included in Debian.

I would have greatly appreciated to have gotten a feedback on my
contribution from 2 years ago instead of it being totally ignored.
During those two years, I had more than enough time that would have
enabled me to improve my contribution if I had received a feedback.

I'm also sure everyone who took the time to open bug reports would
appreciate for those bug reports to be followed up.

Anyway, let's focus on the present.

> [...]
> > Anyway, consider this an objection to salvaging of the pam package.
Is this a confirmation from your part that you now have the motivation
and time available in order to upload up-to-date PAM versions and
properly answer the bug reports that pilled up over the years?

> > I am happy to take a look at your work to forward-port the patches onto pam
> > 1.3.  Would you be willing to rebase
> > https://gitlab.gnugen.ch/fvessaz/pkg-pam.git onto
> > https://salsa.debian.org/vorlon/pam.git ?
> 
> As it's not a trivial rebase to do I've "recreated" much of it on top
> of the new git repo. Cherry-picking from Florians tree where possible,
> reimporting the upstream release from scratch, using my own tree
> of patches from my previous effort[1], and resolved conflicts where
> they appeared when cherry-picking, added some new commits as well.
> In other words, credits to Florian and blame for breakage should
> likely be assigned to me.
> 
> My result is thus not exactly equivalent to Florians tree. Diffing
> debian/patches between our trees can be an interesting read as it's
> two independent rebasing of the existing patches.
> 
> Please see https://salsa.debian.org/ah/pam/commits/ah/master
> 
> (see also the ah/upstream branch.)

I also took the time to work on my branch in order to get something to
compare and to ensure I have an understanding of the changes. I also
included the commit you added to update debian/watch.

See https://gitlab.gnugen.ch/fvessaz/pkg-pam, the master branch is the
updated one and 2018/master is the one from December.

I did not update the changelog entry I previously added; yours might be
more appropriate.

I only took the time to have a cursory look at the differences today.
However, it currently appears that they are relatively small and
contained in debian/patches. I'll take the time to review those
differences tomorrow or Friday night.

> Hoping we can make progress here because the things I'm interested
> in seeing fixed are still to come (but to find motivation to try to
> allocate the time there needs to be some signs of it having a chance
> to be a useful investment).

I'm, also hoping we can make progress. :-)

Cheers,
-- Florian


signature.asc
Description: PGP signature

Bug#866380: xen-bugtool: missing xen.util python module

[Hans van Kranenburg]

tags 866380 + upstream
thanks

Hi,

xen-bugtool seems to be a tool to collect some system information for a
bug report.

I can confirm that in the 4.11 packaging it gives the same result:

-# xen-bugtool
Traceback (most recent call last):
  File "/usr/sbin/xen-bugtool", line 9, in 
from xen.util import bugtool
ImportError: No module named xen.util

When looking at the upstream source, I can find a
docs/README.xen-bugtool about it, and this little script trying to
import it, but nothing else.

So, if anyone feels like sending an upstream PATCH to remove it... :)

For now, tagging upstream here,
Hans

Bug#877783: spyne: Please provide python3-spyne

[Bastian Germann]

I uploaded a source package of the current version to
https://mentors.debian.net/package/spyne

You can download it via
dget -x
https://mentors.debian.net/debian/pool/main/s/spyne/spyne_2.13.4a0-1.dsc

Bug#920296: Installs /etc/systemd/system/dbus-org.freedesktop.timesync1.service identical to /lib/systemd/system/systemd-timesyncd.service

[Josh Triplett]

On Wed, Jan 23, 2019 at 07:52:24PM -0300, Felipe Sateler wrote:
> On Wed, Jan 23, 2019 at 4:15 PM Josh Triplett  wrote:
> > Package: systemd
> > Severity: normal
> >
> > I installed using the Buster Alpha 4 installer, and for some reason I
> > ended up with a file
> > /etc/systemd/system/dbus-org.freedesktop.timesync1.service, identical to
> > /lib/systemd/system/systemd-timesyncd.service. dpkg -S shows it not
> > owned by any package, and searching through maintainer scripts pointed
> > to systemd's postinst. systemd shouldn't install a service in /etc
> > identical to the one already installed in /lib.
> >
> 
> All systemd does is enable the service. On my system that leaves a symlink,
> not a regular file.
> Is  /etc/systemd/system/dbus-org.freedesktop.timesync1.service a regular
> file or a symlink?

It was a regular file.

Bug#920299: lintian: warning for dh_runit usage

[Chris Lamb]

tags 920299 + moreinfo
thanks

Dmitry,

> please add warning for packages, that use dh_runit(1) debhelper (file
> debian/.runit exists), but do not have Breaks: ${runit:Breaks}.

Please elaborate why a `Breaks: ${runit:Breaks}` is needed; I will
need this for the tag long description.


Regards,

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

Bug#920296: Installs /etc/systemd/system/dbus-org.freedesktop.timesync1.service identical to /lib/systemd/system/systemd-timesyncd.service

[Felipe Sateler]

Control: tags -1 moreinfo

On Wed, Jan 23, 2019 at 4:15 PM Josh Triplett  wrote:

> Package: systemd
> Severity: normal
>
> I installed using the Buster Alpha 4 installer, and for some reason I
> ended up with a file
> /etc/systemd/system/dbus-org.freedesktop.timesync1.service, identical to
> /lib/systemd/system/systemd-timesyncd.service. dpkg -S shows it not
> owned by any package, and searching through maintainer scripts pointed
> to systemd's postinst. systemd shouldn't install a service in /etc
> identical to the one already installed in /lib.
>

All systemd does is enable the service. On my system that leaves a symlink,
not a regular file.
Is  /etc/systemd/system/dbus-org.freedesktop.timesync1.service a regular
file or a symlink?
-- 

Saludos,
Felipe Sateler

Bug#920308: compiz-core: compiz-decorator test is inverted, thus can't supply a config

[nick black]

Package: compiz-core
Version: 2:0.8.16.1-4
Severity: normal
Tags: patch

Dear Maintainer,

The script /usr/bin/compiz-decorator has two clearly erroneous tests
near the beginning. XDG_CONFIG_DIRS and XDG_CONFIG_HOME are both checked
for emptiness, and if they are *not* empty, they are assigned values.
Included is a patch to fix this; please apply.


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

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

Versions of packages compiz-core depends on:
ii  libc6 2.28-5
ii  libgl11.1.0-1
ii  libice6   2:1.0.9-2
ii  libsm62:1.2.2-1+b3
ii  libstartup-notification0  0.12-6
ii  libx11-6  2:1.6.7-1
ii  libxcomposite11:0.4.4-2
ii  libxcursor1   1:1.1.15-2
ii  libxdamage1   1:1.1.4-3
ii  libxext6  2:1.3.3-1+b2
ii  libxfixes31:5.0.3-1
ii  libxi62:1.7.9-1
ii  libxinerama1  2:1.1.4-1
ii  libxml2   2.9.4+dfsg1-7+b3
ii  libxrandr22:1.5.1-1
ii  mesa-utils8.4.0-1+b1

Versions of packages compiz-core recommends:
ii  compiz-plugins   2:0.8.16.1-4
ii  compiz-plugins-main  2:0.8.16-2+b1

Versions of packages compiz-core suggests:
ii  nvidia-driver  410.93-1

-- no debconf information
diff -ur compiz-0.8.16.1.orig/plugins/compiz-decorator 
compiz-0.8.16.1/plugins/compiz-decorator
--- compiz-0.8.16.1.orig/plugins/compiz-decorator   2019-01-23 
17:45:23.311674363 -0500
+++ compiz-0.8.16.1/plugins/compiz-decorator2019-01-23 17:45:38.831472785 
-0500
@@ -27,10 +27,10 @@
 }
 
 # Create env variables if empty.
-if [ ! -z "$XDG_CONFIG_DIRS" ]; then
+if [ -z "$XDG_CONFIG_DIRS" ]; then
 XDG_CONFIG_DIRS="/etc/xdg"
 fi
-if [ ! -z "$XDG_CONFIG_HOME" ]; then
+if [ -z "$XDG_CONFIG_HOME" ]; then
 XDG_CONFIG_HOME="$HOME/.config"
 fi
 

Bug#863198: Xen compiling with XSM on

[Hans van Kranenburg]

tags 863198 + moreinfo
thanks

Hi Hervé,

I'm hunting down old bug reports in the Xen packages, and also ran into
this one:

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

Like John Keates already answered in there, when dealing with the source
of a debian package, you're also expected to use the debian packaging
way of building it. When just issuing make commands, you're dealing with
the upstream source in a way that we cannot support in Debian.

Since there has been no more activity on the report, I might close it in
a while if there's no response, since it's not something we can act on.

Have fun,
Hans

Bug#910627: xul-ext-nostalgy: Please update to upstream 0.2.36 to be compatible with TB 60+

[Louis-Philippe Véronneau]

On 1/23/19 5:14 PM, Moritz Mühlenhoff wrote:
> I'm moderately familiar with our procedures of updating stable...

Oh, sorry, I didn't know you were a DD! I'm actually really not familiar
with the stable-proposed-updates procedures :D

> If noone fixes that in stable, I'll request removal of the broken package
> by the next point release.

Please do!

Are you using this package? If you have some time, I'm looking for
someone to upload a fix I pushed to Salsa [1] to make this package
reproducible.

Cheers,

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836609#25

-- 
  ,''`.
 : :'  : Louis-Philippe Véronneau
 `. `'`  po...@debian.org / veronneau.org
   `-



signature.asc
Description: OpenPGP digital signature

Bug#902115: Fails to handle file names containing '\x2'

[Tomasz Buchert]

On 23/01/19 14:54, Chris Lamb wrote:
> retitle 902115 Fails to handle file names containing '\x2'
> tags 902115 + patch
> thanks
>
> Hi,
>
> > Fails to handle file names containing '\x2'
>
> Patch attached with (minimised) testcase. I can confirm this
> successfully re-generates:
>
>   8803baa484cbe36680463c8c5e6febeff074b8e7  
> /tmp/buildd/systemd_239.orig.tar.gz
>
>
> Regards,

Thanks Chris!
Uploading a new release just now!


signature.asc
Description: PGP signature

Bug#920288: bfs: acl/libcap dependencies are optional

[Chris Lamb]

tags 920288 + moreinfo
thanks

Hi Tavian,

> Those dependencies are not required however -- if the headers
> aren't there, the relevant functionality will be stubbed out
> automatically.

I'm not actually seeing that; for example, when I build without the
libacl1-dev and libcap-dev packages installed:

cc -D__EXTENSIONS__ -D_ATFILE_SOURCE -D_BSD_SOURCE -D_DARWIN_C_SOURCE 
-D_DEFAULT_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -DBFS_VERSION=\"1.3.2\" 
-Wdate-time -D_FORTIFY_SOURCE=2 -std=c99 -g -O2 
-fdebug-prefix-map=/tmp/buildd/bfs-1.3.2=. -fstack-protector-strong -Wformat 
-Werror=format-security -MD -MP -MF bfs  -Wl,--as-needed -Wl,-z,relro 
-Wl,-z,now bftw.o color.o diag.o dstring.o eval.o exec.o main.o mtab.o opt.o 
parse.o posix1e.o printf.o spawn.o stat.o typo.o util.o  -lacl -lcap -lrt  -o 
bfs
/usr/bin/ld: cannot find -lacl
/usr/bin/ld: cannot find -lcap

A full build log is available here:

  https://gist.githubusercontent.com/lamby/298c1614207c4a1ecb17e65e22f4bfba/raw


Regards,

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

Bug#920307: kodi: Kodi crashes when attempting to play video via VDPAU

[Vroomfondel]

Package: kodi
Version: 2:17.6+dfsg1-4
Severity: normal

Dear Maintainer,

Following what looks like an upgrade of mesa earlier today, XBMC/kodi started 
crashing when attempting to play videos; disabling VDPAU allowed the videos to 
play, although hardware decoding is then not used (kodi shows ff-h264 in use as 
the decoder). Kodi starts up fine but when you attempt to play a video it 
crashes straight back to desktop and there's no explicit error message in the 
log. This error only seems to occur in kodi - for instance mpv is able to play 
back via VDPAU just fine if I use the --hwdec switch.


Hardware involves an AMD 2400G (Raven Ridge) with the VCN hardware decode block 
which was working fine up until this morning.


21:00:47.939 T:139828740391680  NOTICE: Running on Debian GNU/Linux buster/sid 
testing, kernel: Linux x86 64-bit version 4.19.0-1-amd64
21:00:47.939 T:139828740391680  NOTICE: Host CPU: AMD Ryzen 5 2400G with Radeon 
Vega Graphics, 8 cores available
21:00:48.640 T:139828740391680  NOTICE: GL_RENDERER = AMD RAVEN (DRM 3.27.0, 
4.19.0-1-amd64, LLVM 7.0.1)


Not a big problem as falling back to software decode is a viable option for me 
but it might cause grief for others.


Attached are:
1) excerpt from kodi.log showing a crash when VDPAU is enabled
2) another log showing the same file being played through software when VDPAU is 
disabled and VAAPI is enabled

3) aptitude log detailing the upgrades prior to this problem appearing


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

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

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

Versions of packages kodi depends on:
ii  kodi-bin   2:17.6+dfsg1-4
ii  kodi-data  2:17.6+dfsg1-4

Versions of packages kodi recommends:
ii  kodi-repository-kodi [kodi-repository]  2:17.6+dfsg1-4
pn  kodi-visualization-spectrum 

kodi suggests no packages.

-- no debconf information
20:17:27.581 T:140632108638976  NOTICE: VideoPlayer: Opening: 
/srv/Calibration.mkv
20:17:27.581 T:140632108638976 WARNING: CDVDMessageQueue(player)::Put 
MSGQ_NOT_INITIALIZED
20:17:27.582 T:140629224969984  NOTICE: Creating InputStream
20:17:27.628 T:140629224969984  NOTICE: Creating Demuxer
20:17:27.634 T:140629224969984  NOTICE: Opening stream: 0 source: 256
20:17:27.634 T:140629224969984  NOTICE: Creating video codec with codec id: 27
20:17:27.634 T:140629224969984  NOTICE: CDVDVideoCodecFFmpeg::Open() Using 
codec: H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10
20:17:27.635 T:140629224969984  NOTICE: Creating video thread
20:17:27.635 T:140629224969984  NOTICE: Opening stream: 1 source: 256
20:17:27.635 T:140629224969984  NOTICE: Finding audio codec for: 86076
20:17:27.635 T:140629224969984  NOTICE: Creating audio thread
20:17:27.635 T:140629224969984  NOTICE: Opening stream: 2 source: 256
20:17:27.635 T:140628604204800  NOTICE: running thread: 
CVideoPlayerAudio::Process()
20:17:27.635 T:140628092503808  NOTICE: running thread: video_thread
20:17:27.635 T:140628092503808  NOTICE: VAAPI::Close
20:17:27.640 T:140628092503808  NOTICE: CDVDVideoCodecFFmpeg::Open() Using 
codec: H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10
20:17:27.645 T:140628604204800  NOTICE: Creating audio stream (codec id: 86076, 
channels: 2, sample rate: 48000, no pass-through)
20:17:27.711 T:140632108638976  NOTICE: GL: Selecting Single Pass YUV 2 RGB 
shader
20:17:27.711 T:140632108638976  NOTICE: GL: NPOT texture support detected
20:17:27.711 T:140632108638976  NOTICE: GL: Using GL_ARB_pixel_buffer_object
20:17:27.711 T:140632108638976  NOTICE: Using GL_TEXTURE_2D
20:17:27.718 T:140632108638976  NOTICE: GL: Selecting Single Pass YUV 2 RGB 
shader
20:17:27.718 T:140632108638976  NOTICE: GL: NPOT texture support detected
20:17:27.718 T:140632108638976  NOTICE: GL: Using GL_ARB_pixel_buffer_object
20:17:28.277 T:140628092503808  NOTICE: CDVDVideoCodecFFmpeg::CDropControl: 
calculated diff time: 4
20:17:47.377 T:140632108638976  NOTICE: CVideoPlayer::CloseFile()
20:17:47.377 T:140632108638976  NOTICE: VideoPlayer: waiting for threads to exit
20:17:47.377 T:140629224969984  NOTICE: CVideoPlayer::OnExit()
20:17:47.377 T:140629224969984  NOTICE: Closing stream player 1
20:17:47.377 T:140629224969984  NOTICE: Waiting for audio thread to exit
20:17:47.415 T:140628604204800  NOTICE: thread end: CVideoPlayerAudio::OnExit()
20:17:47.415 T:140629224969984  NOTICE: Closing audio device
20:17:47.465 T:140629224969984  NOTICE: Deleting audio codec
20:17:47.465 T:140629224969984  NOTICE: Closing stream player 2
20:17:47.465 T:140629224969984  NOTICE: waiting for video thread to exit
20:17:47.476 T:140628092503808  NOTICE: thread end: video_thread
20:17:47.477 T:140629224969984  NOTICE: deleting video codec

Bug#920018: Please give this bug attention.

[Nye Liu]

Please apply https://github.com/systemd/systemd/pull/11527
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#866952: Xen 4.8 crashes...

[Radoslav Bodó]

thanks for your concern.

Currently I'm fine with the workaround I've right now. Debian Buster
(and new xen version) will be released sometimes this year, so I would
reopen a new bug if the problem persist on the server after upgrade ...

Thank you and best regards
bodik

Dne 01/23/2019 v 09:31 PM Hans van Kranenburg napsal(a):
> tags 866952 + moreinfo
> thanks
> 
> Hi Bill, Thomas, Joachim, Maxime and Radoslav,
> 
> I'm hunting down old bug reports in the Xen packages, and also ran into
> this one:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866952
> 
> The bug report is a collection of seemingly similar problems with a
> bunch of proposed solutions, but the end result is a pile of things that
> can't really be acted on.
> 
> I suggest to close it, and will do so soon, unless there's someone who
> still has a clear reproducable problem. But, even in that case I'd
> recommend starting a new separate one.

Bug#919824: clblas: under pocl-opencl-icd, aborts with !"PIC Level"

[Rebecca N. Palmer]

Andreas Beckmann wrote:

I need more instructions to reproduce this ...


# apt-get install python3-pygpu python3-nose python3-scipy libclblas-dev 
ocl-icd-opencl-dev pocl-opencl-icd

$ DEVICE=opencl0:0 python3 /usr/bin/nosetests3 -v pygpu.tests.test_blas

You may need to run the second one twice (if it gets to test_ger and 
fails with "free(): invalid next size (normal)" or similar memory 
corruption errors, that's a different bug, which I am currently 
investigating), but do not need any source packages: the pygpu tests are 
included in the binary.



please try pocl from experimental which is built against llvm-7


Doesn't fix it but possibly makes it rarer (the pygpu case now requires 
running the test suite twice).


Using LLVM 7 also avoids #914021, allowing a backtrace:

$ DEVICE=opencl0:0  gdb --args python3 /usr/bin/nosetests3 -v 
pygpu.tests.test_blas

(gdb) break lib/IR/Verifier.cpp:1397
No source file named lib/IR/Verifier.cpp.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (lib/IR/Verifier.cpp:1397) pending.
(gdb) bt full
#0  visitModuleFlag ()
at 
/build/llvm-toolchain-7-Ael5Ob/llvm-toolchain-7-7.0.1/lib/IR/Verifier.cpp:1398

No locals.
#1  visitModuleFlags ()
at 
/build/llvm-toolchain-7-Ael5Ob/llvm-toolchain-7-7.0.1/lib/IR/Verifier.cpp:1306

No locals.
#2  verify ()
at 
/build/llvm-toolchain-7-Ael5Ob/llvm-toolchain-7-7.0.1/lib/IR/Verifier.cpp:384

No locals.
#3  0x70db15db in verifyModule ()
at 
/build/llvm-toolchain-7-Ael5Ob/llvm-toolchain-7-7.0.1/lib/IR/Verifier.cpp:4689

No locals.
#4  0x70cbcf5d in UpgradeDebugInfo ()
at 
/build/llvm-toolchain-7-Ael5Ob/llvm-toolchain-7-7.0.1/lib/IR/AutoUpgrade.cpp:3521

No locals.
#5  0x712c001f in materializeModule ()
at 
/build/llvm-toolchain-7-Ael5Ob/llvm-toolchain-7-7.0.1/lib/Bitcode/Reader/BitcodeReader.cpp:4803

No locals.
#6  0x70d890ea in materializeAll ()
at 
/build/llvm-toolchain-7-Ael5Ob/llvm-toolchain-7-7.0.1/lib/IR/Module.cpp:397

No locals.
#7  0x712b806e in getModuleImpl ()
at 
/build/llvm-toolchain-7-Ael5Ob/llvm-toolchain-7-7.0.1/lib/Bitcode/Reader/BitcodeReader.cpp:5769

No locals.
#8  0x712bd562 in parseModule ()
at 
/build/llvm-toolchain-7-Ael5Ob/llvm-toolchain-7-7.0.1/lib/Bitcode/Reader/BitcodeReader.cpp:5883

No locals.
#9  parseBitcodeFile ()
at 
/build/llvm-toolchain-7-Ael5Ob/llvm-toolchain-7-7.0.1/lib/Bitcode/Reader/BitcodeReader.cpp:5894

No locals.
#10 0x70ddb2cf in parseIR ()
at 
/build/llvm-toolchain-7-Ael5Ob/llvm-toolchain-7-7.0.1/lib/IRReader/IRReader.cpp:79

No locals.
#11 0x70ddb693 in parseIRFile ()
at 
/build/llvm-toolchain-7-Ael5Ob/llvm-toolchain-7-7.0.1/lib/IRReader/IRReader.cpp:108

No locals.
#12 0x73f93f6b in parseModuleIR (
path=path@entry=0x7fff9360 
"/home/test1/.cache/pocl/kcache/JG/ABBLKFOBNDALGEFMHDFBNNLBFBJABFEGHNMOO/program.bc")

at /usr/lib/llvm-7/include/llvm/ADT/StringRef.h:85
Err = {SM = 0x0, Loc = {Ptr = 0x0}, Filename = "", LineNo = 0,
  ColumnNo = 0, Kind = llvm::SourceMgr::DK_Error, Message = "",
  LineContents = "", Ranges = std::vector of length 0, capacity 0,
  FixIts = {> = 
{> = 
{> = 
{ = {BeginX = 0x7fff9268, Size = 0,
Capacity = 4}, }, fields>}, }, 4>> = {InlineElts = {

{> = {
buffer = 
"@\223\377\377\377\177\000\000\200\222\377\377\377\177\000\000\000\261\245\353\227\346\350\327\020\223\377\377\377\177\000\000\321\223T\366\377\177\000\000\020\000\000\000\000\000\000"}, 
},

{> = {
buffer = 
"\002\000\000\000\000\000\000\000\000\000\022@\000\000\022@\300\v(\365\377\177\000\000\060\222\377\377\377\177\000\000\000\261\245\353\227\346\350\327\340\370S\a\000\000\000"}, 
},

{> = {
buffer = 
"\260\226\377\377\377\177\000\000\002\000\000\000\000\000\000\000\360\276\352\000\000\000\000\000\320\206P\a\000\000\000\000\340\206P\a\000\000\000\000\260\225\377\377\377\177\000"}, 
},

{> = {
buffer = "J\206W\366\377\177", '\000' times>, 
"`\223\377\377\377\177\000\000\353\375\365\363\377\177\000\000\001\000\000\000\000\000\000"}, 
}}}, }}

#13 0x73f95d2d in pocl_update_program_llvm_irs_unlocked (
program=program@entry=0x750fe50, device_i=device_i@entry=0)
at ./lib/CL/pocl_llvm_wg.cc:516
program_bc_path = 
"/home/test1/.cache/pocl/kcache/JG/ABBLKFOBNDALGEFMHDFBNNLBFBJABFEGHNMOO/program.bc", 
'\000' ...
__PRETTY_FUNCTION__ = "int 
pocl_update_program_llvm_irs_unlocked(cl_program, unsigned int)"

#14 0x73f95e3d in pocl_update_program_llvm_irs (
program=program@entry=0x750fe50, device_i=device_i@entry=0)
at ./lib/CL/pocl_llvm_wg.cc:526
lockHolder = {}
#15 0x73f1b04b in compile_and_link_program (
compile_program=compile_program@entry=1,
link_program=link_program@entry=1, 

Bug#910627: xul-ext-nostalgy: Please update to upstream 0.2.36 to be compatible with TB 60+

[Moritz Mühlenhoff]

On Wed, Jan 23, 2019 at 12:46:08AM -0500, Louis-Philippe Véronneau wrote:
> On 1/21/19 4:33 PM, Moritz Mühlenhoff wrote:
> > On Sat, Jan 19, 2019 at 04:18:06PM -0500, Louis-Philippe Véronneau wrote:
> >> Hello from the Montreal BSP!
> >>
> >> I tested the latest release of the upstream version (0.2.36) and it
> >> worked fine for me on the latest Thunderbird in testing.
> >>
> >> I migrated the nostalgy VCS from the Alioth archive to Salsa and updated
> >> it to the latest release: https://salsa.debian.org/webext-team/nostalgy
> >>
> >> After testing it, everything seems to work for me. I asked
> >> anar...@debian.org to upload it to the archive.
> > 
> > Note that the original bug report is for Stretch. Are you also planning
> > to update stable as well?
> 
> Hi!
> 
> Sadly, one cannot simply update a package in Stretch (the current stable
> version) that easily. What makes Debian Stable is that packages aren't
> updated but for security reasons.

I'm moderately familiar with our procedures of updating stable...

If noone fixes that in stable, I'll request removal of the broken package
by the next point release.

Cheers,
Moritz

Bug#862408: Xen should trigger reboot-required notification on hypervisor upgrade

[Hans van Kranenburg]

reassign 862408 src:xen 4.4.1-9+deb8u8
tags 862408 + wishlist
thanks

Hi Sébastien,

I'm hunting down old bug reports in the Xen packages, and also ran into
this one:

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

I see why your suggestion would be a nice feature.

Just to set expectations, adding it would require a user who is actually
using Xen together with a gnome desktop to actively participate in
figuring out how this should happen, and do upgrade and reboot testing etc.

I had a quick look at update-notifier and it seems there are more ways
to do the same and it's already deprecated, and...

So, I'm moving it to the wishlist category now.

Thanks,
Hans

Bug#919628: Apply Julia's LLVM patches

[Sylvestre Ledru]

Le 19/01/2019 à 03:20, Lumin a écrit :


I think the best documentation about these patches are git commit
messages following git blame. For example

https://github.com/JuliaLang/julia/commit/e99204b52be23c49b5185d270b6697b097b16513

refers to a bug:

https://github.com/JuliaLang/julia/issues/28726

I'm glad to assemble a detailed list of patches and their corresponding bugs
if you ask. And note that I'm traveling tomorrow (Jan 20) so please don't
expect response from me on that day.


if you could do that, this would be great! thanks.

S

Bug#915527: closed by Debian FTP Masters (Bug#915526: Removed package(s) from unstable)

[Philip Rinn]

Hi,

I don't think the package is removed from backports, at least it's still on the
server:

http://ftp.debian.org/debian/pool/main/c/corebird/

and tracker.d.o shows it also:

https://tracker.debian.org/pkg/corebird

Could you please remove it from backports?

Thanks,
Philip





signature.asc
Description: OpenPGP digital signature

Bug#863172: Xen crash when rebooting

[Hans van Kranenburg]

tags 863172 + moreinfo
thanks

Hi Nicolas,

This is about the bug report about Xen crashing during a reboot that you
filed before in the Debian bug tracker, against the Xen packages.

I see that unfortunately nobody responded on it. A possible reason is
that there was no overly active Xen maintainer team at the moment.

Your bug report was targeted at a Xen package in a Debian distribution
older than the current stable (Stretch).

Can you please help us by confirming that any of the following scenarios
does apply to your situation?

* I had this problem a long time ago. It was never solved, but I found a
workaround, which is ...
* I had this problem a long time ago, and I solved it by not using Xen
any more, but by doing ...
* I still experience this problem, and I'm still using Xen
3.2/4.1/4.4/etc. I cannot upgrade to Debian Stretch or Buster because ...
* I had this problem, and since upgrading to Stretch / Buster / ? it
seems it was solved, and I forgot to report it again. Please close it,
thanks.
* Other: ...

Note that even if you found a solution, it's still very useful to report
it back to our bug tracker. There might be someone else running into the
same problem, who can be helped with your information.

Please note that unless there's a response within a month from now, we
will close the bug report. If you discover this message later, and this
case is important to you, then you can try unarchiving the bug and
replying to it, or reach out to the maintainers email list at
pkg-xen-devel at lists.alioth.debian.org (no subscription required) and
post a message.

Thanks,
Hans van Kranenburg

Bug#914541: [libpam-modules-bin] unix_chkpwd should be SUID instead of SGID, otherwise kscreen_locker does not work

[Maximiliano Curia]

Control: tag -1 + unreproducible

¡Hola Steve!

Please whenever you reassign a bug CC the receiving maintainers so we get an 
useful mail about it, thanks.


El 2019-01-23 a las 08:38 -0800, Steve Langasek escribió:

Control: reassign -1 libkscreenlocker5



That said, the problem could also be in the code of the screen locker.



It could; so let's reassign this bug to the KDE package, whose maintainers
may have more insight into specific configurations that may cause this
screenlocker to fail.


hg42: I haven't heard of a pam issue when using kscreenlocker, thus I'm tagging 
this bug as non reproducible, you might want to test this again with a new 
user or in a new installation without any specific configuration to find the 
real root of the problem you are seeing. To do that I would recommend you 
using a virtual machine with a vanilla Debian Kde installation.


Some other things to consider: are you using selinux rules that might be 
taking effect? any custom apparmor rule? Does your filesystem tweak the file 
permissions? Are you using a remote filesystem?


Happy hacking,
--
"There are two major products that come out of Berkeley: LSD and BSD. 
We don't believe this to be a coincidence."

-- Jeremy S. Anderson
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#917582: Looks like a pandoc bug

[Fiona Klute]

That looks like a bug in pandoc to me. There's no PDF template
configuration in mod_gnutls, so this seems to affect PDF generation with
pandoc's default settings.

The easiest solution for the mod-gnutls package should be to remove the
PDF documentation, and maybe replace it with the manual page available
in 0.9.0. I added that because I consider it more useful on a server
system anyway. ;-)

Regards,
Fiona

Bug#920305: ITP: popper.js -- Javascript library to position poppers in web applications

[Xavier Guimard]

Package: wnpp
Severity: wishlist
Owner: Xavier Guimard 

* Package name: popper.js
  Version : 1.14.6
  Upstream Author : Federico Zivolo 
* URL : https://popper.js.org/
* License : Expat
  Programming Lang: Javascript
  Description : Javascript library to position poppers in web applications

A popper is an element on the screen which "pops out" from the natural flow
of your application.
Common examples of poppers are tooltips, popovers and drop-downs.

This library is a dependency of twitter-bootstrap4 (RC bug #920188)

Bug#866952: Xen 4.8 crashes...

[Thomas Stegbauer]

Hi Hans, 

thank you for the response. 
As the server at this time was already end of support, we switched to VMware 
ESXi free 

regards 
Thomas 

-- 
Firma Stegbauer datawork GmbH & Co. KG 
Oberjulbachring 9 
84387 Julbach 

Tel.: +49 (8571) 9251222 
E-Mail: thomas.stegba...@stegbauer.info 
Internet: www.stegbauer.info 

Unternehmenssitz: Julbach 
Handelsregister beim Amtsgericht: Landshut 
Handelsregister-Nummer: HRA 10671 

Persönlich haftende Gesellschafterin: 
Firma Stegbauer datawork Verwaltungs GmbH - Sitz: Julbach 
Handelsregister beim Amtsgericht: Landshut 
Handelsregisternummer: HRB 9147 
Geschäftsführer: Thomas Stegbauer 

> Von: "Hans van Kranenburg" 
> An: "866952" <866...@bugs.debian.org>, "bill" , "Thomas
> Stegbauer" , "Joachim Braun"
> , "Berillions" , "Radoslav 
> Bodó"
> 
> Gesendet: Mittwoch, 23. Januar 2019 21:31:10
> Betreff: Re: Xen 4.8 crashes...

> tags 866952 + moreinfo
> thanks

> Hi Bill, Thomas, Joachim, Maxime and Radoslav,

> I'm hunting down old bug reports in the Xen packages, and also ran into
> this one:

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

> The bug report is a collection of seemingly similar problems with a
> bunch of proposed solutions, but the end result is a pile of things that
> can't really be acted on.

> I suggest to close it, and will do so soon, unless there's someone who
> still has a clear reproducable problem. But, even in that case I'd
> recommend starting a new separate one.

> Thanks,
> Hans

Bug#918106: logrotate: segfaults in rotateLogSet

[Bernhard Übelacker]

Hello marc, dear Maintainer,

a workaround could be to just to change the default stack
size in the script calling logrotate which is on stretch
maybe /etc/cron.daily/logrotate.

So maybe following line before calling
logrotate could be sufficient?

ulimit -s 16384

(I have not tested this.)

Kind regards,
Bernhard

Bug#911189: src:gpgme1.0: please ship gpgme-json with native messaging hooks for chromium and firefox

[Dr. Oliver Muth]

Package: libgpgme11
Version: 1.12.0-4~bpo9+1
Followup-For: Bug #911189

Dear Maintainer,

the Firefox and Chrome extension Mailvelope needs gpgme-json.
The extension provides GPG encryption/decryption via webmail.



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

Kernel: Linux 4.18.0-0.bpo.1-amd64 (SMP w/3 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de_DE:de 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libgpgme11 depends on:
ii  gnupg  2.2.12-1~bpo9+1
ii  gpg2.2.12-1~bpo9+1
ii  libassuan0 2.5.2-1~bpo9+1
ii  libc6  2.24-11+deb9u3
ii  libgpg-error0  1.26-2

Versions of packages libgpgme11 recommends:
ii  dirmngr 2.2.12-1~bpo9+1
ii  gpg-agent   2.2.12-1~bpo9+1
ii  gpg-wks-client  2.2.12-1~bpo9+1
ii  gpgsm   2.2.12-1~bpo9+1

libgpgme11 suggests no packages.

-- no debconf information

Bug#916604: qmmp: sound files won't be played

[Matteo Cypriani]

Control: tags -1 unreproducible

On Sun, 16 Dec 2018 15:03:33 +0100
bitfreak25  wrote:
> Package: qmmp
> Version: 1.2.2-1+b2
> Severity: important
> 
> Dear Maintainer,
> 
>* What led up to the situation?
> 
> I try to play a sound file by using qmmp.
> 
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>* What was the outcome of this action?
> 
> The program doesn't play the accessed sound file. The GUI is still
> reacting after that, so the program doesn't crash itself.
> 
> 
>* What outcome did you expect instead?
> 
> The program plays the sound file.
> 
> Further information:
> The output when opening an mp3-file in the command-line like "qmmp
> *.mp3" is attached.

Could you please try reproducing with version 1.2.6 that I just
uploaded?

This looks like a misconfiguration of your audio output ("OutputALSA:
Failed to find mixer element"), so if you still have the issue, maybe
check your output plugin in the configuration. If you use PulseAudio,
pick it instead of ALSA.

Thanks,
  Matteo


pgp7Cs5Vq69NB.pgp
Description: PGP signature

Bug#917584: Should be fixed in mod_gnutls 0.9.0

[Fiona Klute]

These test failures look like they are due to the switch to GnuTLS 3.6
(different default algorithms, OpenPGP removal), and should be fixed in
mod_gnutls 0.9.0 (released today).

Bug#896981: [qmmp] gui hang on move equalizer sliders

[Matteo Cypriani]

Control: tags -1 unreproducible

On Sun, 6 May 2018 10:12:31 +0200
Matteo Cypriani  wrote:
> Hi Fernando,
> 
> On Thu, 26 Apr 2018 10:58:10 -0300
> Fernando Toledo  wrote:
> > Package: qmmp
> > Version: 1.1.6-1.1
> > Severity: normal
> > 
> > [...]
> > 
> > to reproduce:
> > * open and play mp3 file
> > * open equilizer.
> > * move some slider
> > * application hang.
> > * console do not show any error
> > 
> > i try run it from gdb, when hang, i send ctrl+c  and get backtrace.
> > if i can do something to get better debug, please let me know.
> > thanks!
> 
> Thanks for your report. I can't reproduce here on unstable. Could you
> please try to reproduce this issue with qmmp 1.2.0-1 (from unstable or
> testing)?
> 
> Cheers,
>   Matteo

qmmp 1.2.6 is now in Debian. Any chance you could try reproducing your
issue?

Thanks,
  Matteo


pgpAM_y3iSXVM.pgp
Description: PGP signature

Bug#908453: xen-utils-common: README.comet seems to no longer apply to the current Xen packages

[Hans van Kranenburg]

tags 908453 + pending
thanks

Hi Keith,

I added a change in the packaging that removed the misleading text about
PVH from the README.comet:

https://salsa.debian.org/xen-team/debian-xen/commit/f7f02e1b2ba0dd6464b53f134f9ca13c5a5550e8

Hans

Bug#913138: many processes hanging in D state on RAID + LVM + ext4fs

[Thorsten Glaser]

Dixi quod…

>I’ve managed to write 'w' to sysctl during this,

Interestingly enough, the system recovered in the meantime,
but dmesg doesn’t have anything new.

This is really annoying!

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

Bug#920304: mailman3-web: mailman3web / django does not like python3-pymysql

[Bjoern Franke]

Package: mailman3-web
Version: 0+20180916-2~bpo9+1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

upgrading mailman3-web lead to
  File
  "/usr/lib/python3/dist-packages/django/db/backends/mysql/base.py",
  line 30, in 
  'Did you install mysqlclient or MySQL-python?' % e
  django.core.exceptions.ImproperlyConfigured: Error loading MySQLdb
  module: No module named 'MySQLdb'.
  Did you install mysqlclient or MySQL-python?

Somehow python3-pymysql does not provide the required module.


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

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

Versions of packages mailman3-web depends on:
ii  dbconfig-sqlite3   2.0.8
ii  debconf [debconf-2.0]  1.5.61
ii  lsb-base   9.20161125
ii  node-less  1.6.3~dfsg-2
ii  python33.5.3-1
ii  python3-django-hyperkitty  1.2.1-4~bpo9+1
ii  python3-django-postorius   1.2.2-4~bpo9+2
ii  python3-psycopg2   2.6.2-1
ii  python3-pymysql0.7.10-1
ii  python3-whoosh 2.7.0-2
ii  ruby-sass  3.4.23-1
ii  ucf3.0036
ii  uwsgi  2.0.14+20161117-3+deb9u2
ii  uwsgi-plugin-python3   2.0.14+20161117-3+deb9u2

Versions of packages mailman3-web recommends:
ii  nginx   1.10.3-1+deb9u2
ii  nginx-full [nginx]  1.10.3-1+deb9u2

Versions of packages mailman3-web suggests:
pn  postgresql | default-mysql-server | virtual-mysql-server  

-- Configuration Files:
/etc/mailman3/uwsgi.ini changed [not included]

-- debconf information:
  mailman3-web/install-error: abort
  mailman3-web/remote/host: localhost
  mailman3-web/emailname: localhost.local
  mailman3-web/pgsql/method: TCP/IP
  mailman3-web/pgsql/authmethod-admin: ident
  mailman3-web/pgsql/no-empty-passwords:
  mailman3-web/remote/newhost:
  mailman3-web/configure-webserver: none
  mailman3-web/mysql/admin-user:
  mailman3-web/missing-db-package-error: abort
  mailman3-web/remote/port:
  mailman3-web/internal/reconfiguring: false
  mailman3-web/restart-webserver: true
  mailman3-web/dbconfig-upgrade: true
  mailman3-web/django-site: lists.ffnw.de
  mailman3-web/nginx-choice:
  mailman3-web/db/app-user: mailman3web@localhost
  mailman3-web/db/dbname: mailman3web
  mailman3-web/db/basepath: /var/lib/mailman3/web
  mailman3-web/dbconfig-reinstall: false
  mailman3-web/upgrade-backup: true
  mailman3-web/database-type:
  mailman3-web/upgrade-error: abort
  mailman3-web/superuser-mail: root@localhost
  mailman3-web/internal/skip-preseed: false
  mailman3-web/pgsql/manualconf:
  mailman3-web/purge: false
  mailman3-web/pgsql/authmethod-user: password
  mailman3-web/dbconfig-remove: true
  mailman3-web/remove-error: abort
* mailman3-web/dbconfig-install: false
  mailman3-web/pgsql/admin-user: postgres
  mailman3-web/mysql/method: Unix socket
  mailman3-web/pgsql/changeconf: false
  mailman3-web/passwords-do-not-match:
  mailman3-web/superuser-name: admin

Bug#920220: apache2: CVE-2019-0190: mod_ssl 2.4.37 remote DoS when used with OpenSSL 1.1.1

[Salvatore Bonaccorso]

Hi Xavier,

On Wed, Jan 23, 2019 at 09:54:29PM +0100, Xavier wrote:
> Le 23/01/2019 à 21:50, Salvatore Bonaccorso a écrit :
> > Hi Xavier,
> > 
> > On Wed, Jan 23, 2019 at 09:46:44PM +0100, Xavier wrote:
> >> Le 23/01/2019 à 20:57, Salvatore Bonaccorso a écrit :
> >>> Control: tags -1 + fixed-upstream
> >>> Control: tags -1 - patch
> >>>
> >>> Hi Xavier,
> >>>
> >>> On Wed, Jan 23, 2019 at 09:18:36AM +0100, Xavier wrote:
>  Hello,
> 
>  Debian bug is tagged as "patch", but I didn't find any patch in the
>  related documents. Can you give me the link to patch ?
> >>>
> >>> Well you are right, not a patch per se, maybe fixed-upstream and
> >>> "there is a patch" would have been better. Let me fix that.
> >>>
> >>> If feasible possibly updating to the new upstream version fixing this
> >>> CVE (and two other) would be better if still feasible so short before
> >>> the soft freeze.
> >>>
> >>> Regards,
> >>> Salvatore
> >>
> >> Hello,
> >>
> >> looking at last release changelog, bug seems not fixed
> > 
> > Cf. https://www.openwall.com/lists/oss-security/2019/01/22/4, where it
> > is fixed in 2.4.38 upstream.
> > 
> > HTH,
> > 
> > Regards,
> > Salvatore
> 
> I see that but the provided link [1] doesn't mention it, neither apache2
> changelog.

I'm almost sure this is just because the respective vulnerabilities_24
page has just not yet been updated accordingly. The fixes are
mentioned already in the upstream changelog at
https://www.apache.org/dist/httpd/CHANGES_2.4.38 .

Regards,
Salvatore

Bug#920179: Buster: klavaro crashes with segmentation fault?

[Bernhard Übelacker]

Control: tags 920179 + upstream patch


Dear Maintainer,
I tried to have a look at this and think I found something.

This seems to be a case of implicit function declaration
defaulting to int as return type but real function returns
a pointer. Therefore an invalid pointer gets later used.

This shows also up as gcc warnings:

warning: implicit declaration of function ‘dngettext’

Attached patch includes libintl.h before usage of dngettext.
That solves the crash but creates some new warnings
about redefinition of gettext and dgettext, where I cannot
say if that has a negative consequence.

Kind regards,
Bernhard




Thread 1 "klavaro" hit Breakpoint 2, 0x55565032 in main_window_init () 
at main.c:317
317 tmp = dngettext (PACKAGE, "Dictation mode (depends on this 
speech synthesizer: %s)",
1: x/i $pc
=> 0x55565032 :  callq  0x55563590 
2: /x $eax = 0x0
3: /x $rdi = 0x5558928b
(gdb) nexti
[Thread 0x725b3700 (LWP 5290) exited]
319 ttip = g_strdup_printf (tmp, "Espeak");
1: x/i $pc
=> 0x55565037 :  lea0x2406e(%rip),%rsi# 
0x555890ac
2: /x $eax = 0xf3732349
3: /x $rdi = 0x7703fa60
(gdb) 
0x5556503e  319 ttip = g_strdup_printf (tmp, "Espeak");
1: x/i $pc
=> 0x5556503e :  movslq %eax,%rdi
2: /x $eax = 0xf3732349
3: /x $rdi = 0x7703fa60
(gdb) 
0x55565041  319 ttip = g_strdup_printf (tmp, "Espeak");
1: x/i $pc
=> 0x55565041 :  xor%eax,%eax
2: /x $eax = 0xf3732349
3: /x $rdi = 0xf3732349 
   < $rdi should equal here $eax
(gdb) 
0x55565043  319 ttip = g_strdup_printf (tmp, "Espeak");
1: x/i $pc
=> 0x55565043 :  callq  0x555632f0 
2: /x $eax = 0x0
3: /x $rdi = 0xf3732349
(gdb) 
[Thread 0x72db4700 (LWP 5289) exited]

Thread 1 "klavaro" received signal SIGSEGV, Segmentation fault.
__strchrnul_sse2 () at ../sysdeps/x86_64/multiarch/../strchr.S:32
32  movdqu  (%rdi), %xmm0
1: x/i $pc
=> 0x76f1af33 <__strchrnul_sse2+35>:movdqu (%rdi),%xmm0
2: /x $eax = 0x349
3: /x $rdi = 0xf3732349
(gdb) bt
#0  0x76f1af33 in __strchrnul_sse2 () at 
../sysdeps/x86_64/multiarch/../strchr.S:32
#1  0x76ed2c49 in __find_specmb (format=0xf3732349 ) at printf-parse.h:108
#2  0x76ed2c49 in _IO_vfprintf_internal (s=s@entry=0x7fffe1e0, 
format=format@entry=0xf3732349 , ap=ap@entry=0x7fffe350) at vfprintf.c:1315
#3  0x76f8d408 in __GI___vasprintf_chk 
(result_ptr=result_ptr@entry=0x7fffe330, flags=flags@entry=1, 
format=0xf3732349 , format@entry=0x7fffe330 "", args=0x7fffe350) at 
vasprintf_chk.c:66
#4  0x7730bef9 in vasprintf (__ap=, __fmt=, __ptr=0x7fffe330) at /usr/include/x86_64-linux-gnu/bits/stdio2.h:213
#5  0x7730bef9 in g_vasprintf (string=string@entry=0x7fffe330, 
format=, args=args@entry=0x7fffe350) at 
../../../glib/gprintf.c:330
#6  0x772e555d in g_strdup_vprintf (format=, 
args=args@entry=0x7fffe350) at ../../../glib/gstrfuncs.c:514
#7  0x772e5619 in g_strdup_printf (format=) at 
../../../glib/gstrfuncs.c:540
#8  0x55565048 in main_window_init () at main.c:319
#9  0x55565048 in main (argc=, argv=) at 
main.c:475
Description: Include libintl.h to avoid default int for dngettext

Bug-Debian: https://bugs.debian.org/920179
Forwarded: no
Last-Update: 2019-01-23

--- klavaro-3.03.orig/src/main.c
+++ klavaro-3.03/src/main.c
@@ -18,6 +18,7 @@
 #include 
 #include 
 #include 
+#include 
 
 #include "auxiliar.h"
 #include "callbacks.h"
--- klavaro-3.03.orig/src/tutor.c
+++ klavaro-3.03/src/tutor.c
@@ -23,6 +23,7 @@
 #include 
 #include 
 #include 
+#include 
 
 #include "main.h"
 #include "auxiliar.h"

# Buster amd64 qemu VM 2019-01-23

apt update
apt dist-upgrade


apt install xserver-xorg lightdm openbox klavaro
apt install systemd-coredump gdb valgrind binutils mc klavaro-dbgsym 
libglib2.0-0-dbgsym
apt install dpkg-dev devscripts
apt build-dep klavaro


systemctl start lightdm



mkdir source/klavaro/orig -p
cdsource/klavaro/orig
apt source klavaro
cd


mkdir source/glibc/orig -p
cdsource/glibc/orig
apt source glibc
cd




export DISPLAY=:0
klavaro


##


benutzer@debian:~$ klavaro
Speicherzugriffsfehler (Speicherabzug geschrieben)


root@debian:~# coredumpctl list
TIMEPID   UID   GID SIG COREFILE  EXE
Wed 2019-01-23 15:35:13 CET7166  1000  1000  11 present   /usr/bin/klavaro

root@debian:~# coredumpctl gdb 7166
   PID: 7166 (klavaro)
   UID: 1000 (benutzer)
   GID: 1000 (benutzer)
Signal: 11 (SEGV)
 Timestamp: Wed 2019-01-23 15:35:13 CET (34s ago)
  Command Line: klavaro
Executable: /usr/bin/klavaro
 Control Group: /user.slice/user-1000.slice/session-3.scope
  Unit: session-3.scope
 Slice: user-1000.slice
   Session: 3

Bug#920188: Proposed fix

[Xavier]

Hi all,

to fix missing popper.js, I propose to embed it for now in
twitter-bootstrap4 (done in salsa repo but not pushed). After buster
release, we could split it in a separate package.

Please review this.

Cheers,
Xavier

Bug#920220: apache2: CVE-2019-0190: mod_ssl 2.4.37 remote DoS when used with OpenSSL 1.1.1

[Xavier]

Le 23/01/2019 à 21:50, Salvatore Bonaccorso a écrit :
> Hi Xavier,
> 
> On Wed, Jan 23, 2019 at 09:46:44PM +0100, Xavier wrote:
>> Le 23/01/2019 à 20:57, Salvatore Bonaccorso a écrit :
>>> Control: tags -1 + fixed-upstream
>>> Control: tags -1 - patch
>>>
>>> Hi Xavier,
>>>
>>> On Wed, Jan 23, 2019 at 09:18:36AM +0100, Xavier wrote:
 Hello,

 Debian bug is tagged as "patch", but I didn't find any patch in the
 related documents. Can you give me the link to patch ?
>>>
>>> Well you are right, not a patch per se, maybe fixed-upstream and
>>> "there is a patch" would have been better. Let me fix that.
>>>
>>> If feasible possibly updating to the new upstream version fixing this
>>> CVE (and two other) would be better if still feasible so short before
>>> the soft freeze.
>>>
>>> Regards,
>>> Salvatore
>>
>> Hello,
>>
>> looking at last release changelog, bug seems not fixed
> 
> Cf. https://www.openwall.com/lists/oss-security/2019/01/22/4, where it
> is fixed in 2.4.38 upstream.
> 
> HTH,
> 
> Regards,
> Salvatore

I see that but the provided link [1] doesn't mention it, neither apache2
changelog.

[1] https://httpd.apache.org/security/vulnerabilities_24.html

Bug#909667: FTBFS depending on source tree timestamps

[Hans van Kranenburg]

tags 909667 + moreinfo
thanks

Hi Ian,

is this one still relevant, especially after the packaging rewrite?

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

The text in also doesn't really contain a question or a copy of the
error message, or point out what would need to be done, so I'm moving it
to the 'moreinfo' department of the list.

Hans

Bug#920220: apache2: CVE-2019-0190: mod_ssl 2.4.37 remote DoS when used with OpenSSL 1.1.1

[Salvatore Bonaccorso]

Hi Xavier,

On Wed, Jan 23, 2019 at 09:46:44PM +0100, Xavier wrote:
> Le 23/01/2019 à 20:57, Salvatore Bonaccorso a écrit :
> > Control: tags -1 + fixed-upstream
> > Control: tags -1 - patch
> > 
> > Hi Xavier,
> > 
> > On Wed, Jan 23, 2019 at 09:18:36AM +0100, Xavier wrote:
> >> Hello,
> >>
> >> Debian bug is tagged as "patch", but I didn't find any patch in the
> >> related documents. Can you give me the link to patch ?
> > 
> > Well you are right, not a patch per se, maybe fixed-upstream and
> > "there is a patch" would have been better. Let me fix that.
> > 
> > If feasible possibly updating to the new upstream version fixing this
> > CVE (and two other) would be better if still feasible so short before
> > the soft freeze.
> > 
> > Regards,
> > Salvatore
> 
> Hello,
> 
> looking at last release changelog, bug seems not fixed

Cf. https://www.openwall.com/lists/oss-security/2019/01/22/4, where it
is fixed in 2.4.38 upstream.

HTH,

Regards,
Salvatore

Bug#920220: apache2: CVE-2019-0190: mod_ssl 2.4.37 remote DoS when used with OpenSSL 1.1.1

[Xavier]

Le 23/01/2019 à 20:57, Salvatore Bonaccorso a écrit :
> Control: tags -1 + fixed-upstream
> Control: tags -1 - patch
> 
> Hi Xavier,
> 
> On Wed, Jan 23, 2019 at 09:18:36AM +0100, Xavier wrote:
>> Hello,
>>
>> Debian bug is tagged as "patch", but I didn't find any patch in the
>> related documents. Can you give me the link to patch ?
> 
> Well you are right, not a patch per se, maybe fixed-upstream and
> "there is a patch" would have been better. Let me fix that.
> 
> If feasible possibly updating to the new upstream version fixing this
> CVE (and two other) would be better if still feasible so short before
> the soft freeze.
> 
> Regards,
> Salvatore

Hello,

looking at last release changelog, bug seems not fixed

Bug#883826: Intent to initiate a L10N-NMU for libvisual-plugins on/after 2019-02-01

[Helge Kreutzmann]

Hello Eriberto,
On Mon, Jan 21, 2019 at 10:06:45AM -0200, Eriberto wrote:
> Em qui, 10 de jan de 2019 às 16:25, Helge Kreutzmann
>  escreveu:
> 
> > libvisual-plugins has a open translation without any activity.
> > To ensure that this translation hits the archive before the
> > freeze I intend to NMU on/after February 1st.
> >
> > Of course, a maintainer upload would be much preferred. If you have
> > troubles integrating the translation please let me know for
> > assistance.
> >
> > If you have any resons for not including this translation please
> > let me know so that I can skip the NMU.
> 
> I am not much familiar with L10N. Can you send me a patch or do a push
> request in Salsa? I can upload the package quickly.

I attached the change in patch format, simply put this file into
debian/patches and add it to debian/patches/series.

Unfortunately there is a bug in the build system I could not figure
out. Therefore please also update debian/rules as attached.

Finally you need to update debian/copyright and debian/changelog.

Thanks for the uplaod.

> Thanks for your interest and your help.

You are welcome, thanks for the upload and maintianing
libvisual-plugins. 

Greetings

  Helge

-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/
Description: Add German translation
 This patch adds the German translation.
 .
 libvisual-plugins (1:0.4.0+dfsg1-12) unstable; urgency=medium
Author: Chris Leick , 2017
Origin: other, https://bugs.debian.org/cgi-bin/bugreport.cgi?att=2;bug=883826;filename=de.po.gz;msg=5
Bug-Debian: https://bugs.debian.org/883826
Forwarded: 
Reviewed-By: Helge Kreutzmann 
Last-Update: 2019-01-23

--- /dev/null
+++ libvisual-plugins-0.4.0+dfsg1/po/de.po
@@ -0,0 +1,533 @@
+# Translation of libvisual-plugins to German
+# Copyright (C) 1999-2000 Christopher Wilson, 1999-2001 Zinx Verituse,
+#   2000-2001 Remi Arquier, 2000-2001 Richard Ashburn,
+#   2002-2006 Dennis Smit, 2004-2006 Antti Silvast,
+#   2005 yodor, Andrew Birck, Jean-Christophe Hoelt.
+# This file is distributed under the same license as
+# the libvisual-plugins package.
+# Chris Leick , 2017.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: libvisual-plugins 0.4.0\n"
+"Report-Msgid-Bugs-To: libvisual-plug...@packages.debian.org\n"
+"POT-Creation-Date: 2006-03-21 02:50+0800\n"
+"PO-Revision-Date: 2017-11-23 18:08:07+0200\n"
+"Last-Translator: Chris Leick \n"
+"Language-Team: German \n"
+"Language: de\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: plugins/actor/bumpscope/actor_bumpscope.c:62
+msgid ""
+"Original by: Zinx Verituse , Port by: Dennis Smit "
+msgstr ""
+"Original von Zinx Verituse , Portierung durch Dennis Smit "
+""
+
+#: plugins/actor/bumpscope/actor_bumpscope.c:64
+# Bumpscope ist ein Visualisierungs-Plugin für XMMS
+msgid "Bumpscope visual plugin"
+msgstr "visuelle Bumpscope-Erweiterung"
+
+#: plugins/actor/bumpscope/actor_bumpscope.c:65
+msgid "This is the libvisual port of the xmms Bumpscope plugin"
+msgstr "Dies ist die Libvisual-Portierung der XMMS-Erweiterung Bumpscore"
+
+#: plugins/actor/bumpscope/actor_bumpscope.c:126
+msgid "The color of the light"
+msgstr "die Farbe des Lichts"
+
+#: plugins/actor/bumpscope/actor_bumpscope.c:132
+#: plugins/actor/bumpscope/actor_bumpscope.c:140
+msgid "The size of the light"
+msgstr "die Größe des Lichts"
+
+#: plugins/actor/bumpscope/actor_bumpscope.c:148
+msgid "Cycling colors"
+msgstr "periodisch durchlaufende Farben"
+
+#: plugins/actor/bumpscope/actor_bumpscope.c:149
+msgid "Automatic cycling through colors"
+msgstr "automatisch Farben durchlaufen"
+
+#: plugins/actor/bumpscope/actor_bumpscope.c:152
+msgid "Moving light"
+msgstr "bewegtes Licht"
+
+#: plugins/actor/bumpscope/actor_bumpscope.c:154
+# FIXME: s/itusing/it's using/
+msgid ""
+"Automatic movement of the light, when disabled it's possible to select "
+"itusing the mouse cursor"
+msgstr ""
+"automatisches Bewegen des Lichts, wenn es deaktiviert ist, ist es möglich, es "
+"mittels des Maus-Cursors auszuwählen"
+
+#: plugins/actor/bumpscope/actor_bumpscope.c:158
+msgid "Diamond"
+msgstr "Diamant"
+
+#: plugins/actor/bumpscope/actor_bumpscope.c:159
+msgid "Diamond shaped light"
+msgstr "diamantförmiges Licht"
+
+#: plugins/actor/corona/actor_corona.cpp:103
+msgid "Libvisual corona plugin"
+msgstr "Libvisual-Corona-Erweiterung"
+
+#: plugins/actor/corona/actor_corona.cpp:104
+# https://corona-renderer.com/resources/plugins-scripts
+msgid "This plugin adds support for the neat corona plugin"
+msgstr ""
+"Diese Erweiterung fügt Unterstützung für die nette Erweiterung »Corona« hinzu."
+
+#: plugins/actor/gdkpixbuf/actor_gdkpixbuf.c:86
+msgid "GdkPixbuf image loader for 

Bug#864082: [Fontconfig] Next steps for a reproducible Fontconfig?

[Keith Packard]

Akira TAGOH  writes:

> Keith,
>
> I'm fine with it. do you have a time to work on it? or already started 
> working?
> If not, please let me know.

I've been at a conference all week, but hope to have time next
week. Would be happy to see others get this started, or collaborate in
any way. If I do get started, I'll be pushing stuff frequently and
posting mail so I don't block others.

Would be awesome to get this done in the next couple of weeks...

-- 
-keith


signature.asc
Description: PGP signature

Bug#919296: git-daemon-run: fails with 'warning: git-daemon: unable to open supervise/ok: file does not exist'

[Jonathan Nieder]

Dmitry Bogatov wrote:
>> Jonathan Nieder wrote:

>>> +  * git-daemon-run: pre-create supervise directory so that postinst
>>> +can start the service (thx Celejar and Dmitry Bogatov; closes:
>>> +#919296).
[...]
> Wierd. It should work. /etc/sv/git-daemon/supervise is not dangling, is
> it? Tell me which git commit I should build and test, in effort to help
> debugging?

It's not dangling.

I tested with the debian-sid branch, with the patch in the message I
sent applied on top.  That said:

[...]
> It is my fault. I dropped /var/lib/supervise directory in runit=2.1.2-4,
> which was expected by git-daemon-run.
>
> Today runit packaging underwent quite a rework, and packages, providing
> runscripts are encouraged to use dh_runit(1). It manages creation of
> apporiate directories and symbolic links. If you have any issues, do not
> hezitate to ask -- runit is my top priority.

Thanks, these are two good starting points.  I'll take a look at the
2.1.2-4 changes and into whether it's simple to use dh_runit.  Hopefully
the latter will take care of everything. :)

Jonathan

Bug#920303: apache2: CVE-2018-17199: mod_session_cookie does not respect expiry time

[Salvatore Bonaccorso]

Source: apache2
Version: 2.4.37-1
Severity: important
Tags: security upstream fixed-upstream
Control: found -1 2.4.25-3+deb9u6
Control: found -1 2.4.25-3

Hi,

The following vulnerability was published for apache2.

CVE-2018-17199[0]:
mod_session_cookie does not respect expiry time

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-17199
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-17199
[1] https://www.openwall.com/lists/oss-security/2019/01/22/3

Regards,
Salvatore

Bug#866952: Xen 4.8 crashes...

[Hans van Kranenburg]

tags 866952 + moreinfo
thanks

Hi Bill, Thomas, Joachim, Maxime and Radoslav,

I'm hunting down old bug reports in the Xen packages, and also ran into
this one:

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

The bug report is a collection of seemingly similar problems with a
bunch of proposed solutions, but the end result is a pile of things that
can't really be acted on.

I suggest to close it, and will do so soon, unless there's someone who
still has a clear reproducable problem. But, even in that case I'd
recommend starting a new separate one.

Thanks,
Hans

Bug#920301: indicator bar too small on HIDPI display

[Toni]

Package: fcitx
Version: 1:4.2.9.6-5
Severity: normal
Tags: upstream



Hi,

on my 15" laptop with 294 dpi, the indicator bar which shows the
currently active input method and details (full-width characters etc.)
is so small that I can not really read things. It's also hard to click
on, for the same reason. Please see the attached screenshot, which
represents about 2-3mm in height.


Cheers,
Toni



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

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

Versions of packages fcitx depends on:
ii  fcitx-bin  1:4.2.9.6-5
ii  fcitx-data 1:4.2.9.6-5
ii  fcitx-modules  1:4.2.9.6-5

Versions of packages fcitx recommends:
ii  fcitx-config-gtk0.4.10-2
ii  fcitx-frontend-all  1:4.2.9.6-5
ii  fcitx-ui-classic1:4.2.9.6-5
ii  fcitx-ui-light  0.1.3-3
ii  im-config   0.38-1

Versions of packages fcitx suggests:
pn  fcitx-m17n   
pn  fcitx-tools  

-- no debconf information

Bug#920302: apache2: CVE-2018-17189: mod_http2, DoS via slow, unneeded request bodies

[Salvatore Bonaccorso]

Source: apache2
Version: 2.4.37-1
Severity: important
Tags: security upstream fixed-upstream
Control: found -1 2.4.25-3+deb9u6
Control: found -1 2.4.25-3

Hi,

The following vulnerability was published for apache2.

CVE-2018-17189[0]:
mod_http2, DoS via slow, unneeded request bodies

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-17189
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-17189
[1] https://www.openwall.com/lists/oss-security/2019/01/22/2

Regards,
Salvatore

Bug#864657: ca-certificates-java: Can we have fix for this in Stretch as well, please.

[Markus Koschany]

Of course I meant default-jre-headless | java7-runtime-headless.



signature.asc
Description: OpenPGP digital signature

Bug#864657: ca-certificates-java: Can we have fix for this in Stretch as well, please.

[Markus Koschany]

On Wed, 23 Jan 2019 19:08:27 + Marcin Kulisz  wrote:
> Package: ca-certificates-java
> Followup-For: Bug #864657
> 
> Hi I just want to add that at the moment Stretch current stable has this 
> broken
> to the point that neither openjdk nor ca-certificates-java packages can be
> installed making all java dependant apps useless.
> 
> It's due to ca-certificates-java dependencies be:
> openjdk-7-jre-headless | java7-runtime-headless
> and those packages are not available anymore in Stretch.
> 
> Instead only openjdk for java8 is available so please provide update to stable
> fixing those dependencies by replacing:
> openjdk-7-jre-headless | java7-runtime-headless
> with
> openjdk-8-jre-headless


java7-runtime-headless is provided by openjdk-8-jre-headless. The
alternative dependency is satisfied when you install
openjdk-8-jre-headless. The dependency should have been default-jre |
java7-runtime-headless but I don't think this is a major problem for
Stretch. However we should fix it for Buster.

Markus



signature.asc
Description: OpenPGP digital signature

Bug#920300: no way to "close" without exiting the program

[Toni]

Package: screengrab
Version: 1.99-1
Severity: normal



Hello,

I just started to use 'screengrab', but the program has a very strong
tendency to quit. At least, there is no, or no obvious way to "close"
the program in a way that it does not occypy space in the taskbar, and
just stays in the systray, despite the documentation suggesting that
the program might just sit in the systray and only pop up when needed.

Steps to reproduce:

1. Start 'screengrab --minimized' (I'm running it from my .xsessionrc).
2. Take a screenshot.
3. Try to close/minimize the window.

In this case, it takes up a slot in my taskbar and has a systray icon,
whereas it shoud only have a systray icon.

I am using awesome 4.2 without Gnome or other such stuff.


Cheers,
Toni


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

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

Versions of packages screengrab depends on:
ii  libc62.28-5
ii  libgcc1  1:8.2.0-14
ii  libkf5windowsystem5  5.51.0-1
ii  libqt5core5a 5.11.3+dfsg-2
ii  libqt5dbus5  5.11.3+dfsg-2
ii  libqt5gui5   5.11.3+dfsg-2
ii  libqt5network5   5.11.3+dfsg-2
ii  libqt5widgets5   5.11.3+dfsg-2
ii  libqt5x11extras5 5.11.3-2
ii  libqt5xdg3   3.2.0-2+b3
ii  libstdc++6   8.2.0-14
ii  libx11-xcb1  2:1.6.7-1
ii  libxcb-xfixes0   1.13.1-2

screengrab recommends no packages.

screengrab suggests no packages.

-- no debconf information

Bug#920257: Structure of the file ...

[Jérôme Kieffer]

Hi,

The structure of the dataset in the file is "entry/data/data_01",
not "entry/data_01".

Moreover the bug you reported should be in h5py, not fabio as you don't
use fabio in your code snippet.

This bug has probably nothing to do the debian packaging, so it is
probably better to discuss with the development bug-tacker:
https://github.com/silx-kit/fabio/issues

Cheers,

Jérôme (also maitainer for fabio over the last decade)