Bug#927515: Updating the talloc Uploaders list

[Tobias Frost]

Source: talloc
Version: 2.1.14-2
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the talloc package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#927502: Updating the lvmcfg Uploaders list

[Tobias Frost]

Source: lvmcfg
Version: 1.50
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the lvmcfg package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#927510: Updating the di-netboot-assistant Uploaders list

[Tobias Frost]

Source: di-netboot-assistant
Version: 0.62
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the di-netboot-assistant package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#927500: Updating the partman-auto-raid Uploaders list

[Tobias Frost]

Source: partman-auto-raid
Version: 41
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the partman-auto-raid package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#927509: Updating the arcboot-installer Uploaders list

[Tobias Frost]

Source: arcboot-installer
Version: 1.38
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the arcboot-installer package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#927511: Updating the console-setup Uploaders list

[Tobias Frost]

Source: console-setup
Version: 1.172 1.188 1.191
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the console-setup package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#927259: release.debian.org: unblock request: nheko

[Niels Thykier]

Control: tags -1 moreinfo confirmed

Hubert Chathi:
> Package: release.debian.org
> Severity: normal
> 
> Hello release team.
> 
> I would like to upload a new version of nheko to fix #926671.  It is an
> "important" bug (though in reality, it could be argued that it is
> "serious", as Matrix will be bumping the default room version soon,
> which will cause the bug to manifest much more commonly, making the
> program less usable).
> 
> The fix is to apply a small patch from upstream.  Attached is a debdiff.
> 
> In addition to the above issue, I would like to also include fixes for
> the following bugs, which are not included in the attached debdiff, but
> are fairly trivial:
> 
> - #926659 - incorrectly named file (debian/README.sources instead of
>   debian/README.source) -- has an obvious fix
> - #926680 - a working directory is not properly cleaned up if the build
>   fails -- I would just add the working directory to the list of files
>   that are "rm -rf"-ed in override_dh_auto_clean.
> 
> [...]
> 

Hi,

Please go ahead with the upload including the two extra changes you
mentioned above and remove the moreinfo tag when it is in unstable and
ready to be unblocked.

For future reference: We generally prefer seeing the debdiff before
approving the changes.  Had the two extra changes not been obvious from
your description, then it would have been necessary for me to ask you
for the full debdiff.  Please make it easier for us by always including
the changes you want us to consider (modulo filterdiff of auto-generated
files).

Thanks,
~Niels

Bug#927504: Updating the hw-detect Uploaders list

[Tobias Frost]

Source: hw-detect
Version: 1.127 1.134 1.137
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the hw-detect package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#927501: Updating the partman-auto-lvm Uploaders list

[Tobias Frost]

Source: partman-auto-lvm
Version: 75
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the partman-auto-lvm package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#927512: Updating the partman-lvm Uploaders list

[Tobias Frost]

Source: partman-lvm
Version: 130
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the partman-lvm package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#927514: Updating the partman-base Uploaders list

[Tobias Frost]

Source: partman-base
Version: 208
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the partman-base package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#927513: Updating the zipl-installer Uploaders list

[Tobias Frost]

Source: zipl-installer
Version: 0.0.39
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the zipl-installer package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#927508: Updating the nobootloader Uploaders list

[Tobias Frost]

Source: nobootloader
Version: 1.56
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the nobootloader package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#927491: Updating the grub-installer Uploaders list

[Tobias Frost]

Source: grub-installer
Version: 1.165
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the grub-installer package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#927498: Updating the netcfg Uploaders list

[Tobias Frost]

Source: netcfg
Version: 1.147 1.157 1.160
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the netcfg package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#927490: Updating the pkgsel Uploaders list

[Tobias Frost]

Source: pkgsel
Version: 0.65
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the pkgsel package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#927506: Updating the s390-netdevice Uploaders list

[Tobias Frost]

Source: s390-netdevice
Version: 0.0.68
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the s390-netdevice package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#927505: Updating the cdebconf Uploaders list

[Tobias Frost]

Source: cdebconf
Version: 0.235 0.246 0.248 0.249
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the cdebconf package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#927495: Updating the partman-iscsi Uploaders list

[Tobias Frost]

Source: partman-iscsi
Version: 61
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the partman-iscsi package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#927492: Updating the cdrom-detect Uploaders list

[Tobias Frost]

Source: cdrom-detect
Version: 1.72 1.81 1.83
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the cdrom-detect package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#927503: Updating the iso-scan Uploaders list

[Tobias Frost]

Source: iso-scan
Version: 1.72 1.75
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the iso-scan package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#927494: Updating the apt-setup Uploaders list

[Tobias Frost]

Source: apt-setup
Version: 1:0.149
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the apt-setup package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#927499: Updating the partman-target Uploaders list

[Tobias Frost]

Source: partman-target
Version: 113
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the partman-target package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#927496: Updating the partman-partitioning Uploaders list

[Tobias Frost]

Source: partman-partitioning
Version: 130
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the partman-partitioning package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#927493: Updating the base-installer Uploaders list

[Tobias Frost]

Source: base-installer
Version: 1.188
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the base-installer package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#927497: Updating the partman-crypto Uploaders list

[Tobias Frost]

Source: partman-crypto
Version: 103
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the partman-crypto package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#927487: Updating the partman-basicfilesystems Uploaders list

[Tobias Frost]

Source: partman-basicfilesystems
Version: 146 147
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the partman-basicfilesystems package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#927488: Updating the flash-kernel Uploaders list

[Tobias Frost]

Source: flash-kernel
Version: 3.98
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the flash-kernel package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#927489: Updating the tasksel Uploaders list

[Tobias Frost]

Source: tasksel
Version: 3.52
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the tasksel package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#927486: Updating the rootskel Uploaders list

[Tobias Frost]

Source: rootskel
Version: 1.124 1.126 1.128
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the rootskel package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#927485: Updating the choose-mirror Uploaders list

[Tobias Frost]

Source: choose-mirror
Version: 2.85 2.96 2.98 2.99
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the choose-mirror package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#927484: CVE-2018-12179 CVE-2018-12182

[Moritz Muehlenhoff]

Source: edk2
Severity: important
Tags: security

CVE-2018-12179:
https://bugzilla.tianocore.org/show_bug.cgi?id=1133

CVE-2018-12182:
https://bugzilla.tianocore.org/show_bug.cgi?id=1136

Cheers,
Moritz
   
 

Bug#927483: unblock: wireshark/2.6.8-1

[Moritz Muehlenhoff]

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

Please unblock package wireshark. It fixes the recent security issues by
updating to the latest 2.6.x

(Wireshark in stretch-security also follows upstream releases (as will
buster-security)

unblock wireshark/2.6.8-1

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

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

Bug#925552: release-notes: document problems with hidepid vs Buster systemd

[Justin B Rye]

Andrei POPESCU wrote:
> Justin B Rye wrote:
>> The "hidepid" mount-options for /proc (as recommended by various
> 
> Why plural? Both the wiki and proc(5) are using singular.

You're right - I was thinking of "hidepid=0/1/2" as separate options,
but yes, the approved terminology is to call it one option with
multiple possible arguments.  I suppose I could argue that it's 
only the non-zero arguments that cause problems rather than the 
hidepid option itself, but no, here's a patch making it singular.
-- 
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
diff --git a/en/issues.dbk b/en/issues.dbk
index 39d27b25..81ed5863 100644
--- a/en/issues.dbk
+++ b/en/issues.dbk
@@ -41,15 +41,15 @@ information mentioned in .
 
   
 
-Hidepid mount options for procfs unsupported
+Hidepid mount option for procfs unsupported
 
-  The hidepid mount options for
-  /proc are known to cause problems with current
-  versions of systemd, and are considered by systemd upstream to be an
+  Using the hidepid mount option for
+  /proc is known to cause problems with current
+  versions of systemd, and is considered by systemd upstream to be an
   unsupported configuration. Users who have modified
-  /etc/fstab to enable these options are advised to
-  disable them before the upgrade, to ensure login sessions work on
-  . (A possible route to re-enabling them is outlined on the
+  /etc/fstab to enable this option are advised to
+  disable it before the upgrade, to ensure login sessions work on
+  . (A possible route to re-enabling it is outlined on the
   wiki's https://wiki.debian.org/Hardening#Mounting_.2Fproc_with_hidepid;>Hardening
   page.)

Bug#927482: unblock: u-boot/2019.01+dfsg-5

[Vagrant Cascadian]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: debian-b...@lists.debian.org

Please unblock package u-boot

This upload is adds support for two more systems; orangepi_zero_plus2
was simply a matter of enabling the target, while the teres_i laptop
also required backporting a fix from upstream and adding a configuration
and device-tree for the board. The u-boot-install-sunxi64 helper script
was modified to auto-detect both of these boards.

All changes should be low risk for regressions in other boards.


diff -Nru u-boot-2019.01+dfsg/debian/bin/u-boot-install-sunxi64 
u-boot-2019.01+dfsg/debian/bin/u-boot-install-sunxi64
--- u-boot-2019.01+dfsg/debian/bin/u-boot-install-sunxi64   2019-04-08 
14:01:19.0 -0700
+++ u-boot-2019.01+dfsg/debian/bin/u-boot-install-sunxi64   2019-04-19 
15:21:52.0 -0700
@@ -7,6 +7,8 @@
Pinebook) TARGET="/usr/lib/u-boot/pinebook" ;;
Pine64+) TARGET="/usr/lib/u-boot/pine64_plus" ;;
"Olimex A64-Olinuxino") TARGET="/usr/lib/u-boot/a64-olinuxino/" 
;;
+   "Olimex A64 Teres-I") TARGET="/usr/lib/u-boot/teres_i/" ;;
+   "OrangePi Zero Plus2") 
TARGET="/usr/lib/u-boot/orangepi_zero_plus2/" ;;
esac
 fi

diff -Nru u-boot-2019.01+dfsg/debian/changelog 
u-boot-2019.01+dfsg/debian/changelog
--- u-boot-2019.01+dfsg/debian/changelog2019-04-08 19:47:02.0 
-0700
+++ u-boot-2019.01+dfsg/debian/changelog2019-04-19 16:43:08.0 
-0700
@@ -1,3 +1,15 @@
+u-boot (2019.01+dfsg-5) unstable; urgency=medium
+
+  [ Jonas Smedegaard ]
+  * Add patch cherry-picked upstream to add i2c initialization for sun50i.
+  * Add patch by Vasily Khoruzhick to support Olimex Teres-I DIY laptop.
+  * Enable teres_i target in u-boot-sunxi (Closes: #926040).
+
+  [ Frédéric Danis ]
+  * Enable orangepi_zero_plus2 target in u-boot-sunxi (Closes: #927224).
+
+ -- Vagrant Cascadian   Fri, 19 Apr 2019 16:43:08 -0700
+
 u-boot (2019.01+dfsg-4) unstable; urgency=medium

   [ Martyn Welch ]
diff -Nru u-boot-2019.01+dfsg/debian/patches/series 
u-boot-2019.01+dfsg/debian/patches/series
--- u-boot-2019.01+dfsg/debian/patches/series   2019-04-08 14:01:19.0 
-0700
+++ u-boot-2019.01+dfsg/debian/patches/series   2019-04-19 15:21:52.0 
-0700
@@ -26,3 +26,6 @@
 # Patches to fix https://bugs.debian.org/923379
 dreamplug/ARM-kirkwood-add-spi0-alias-for-dreamplug.patch
 dreamplug/Commit-ARM-CPU-arm926ejs-Consolidate-cache-routines-.patch
+
+sunxi/sun50i_i2c_init.patch
+sunxi/teres-i.patch
diff -Nru u-boot-2019.01+dfsg/debian/patches/sunxi/sun50i_i2c_init.patch
u-boot-2019.01+dfsg/debian/patches/sunxi/sun50i_i2c_init.patch
--- u-boot-2019.01+dfsg/debian/patches/sunxi/sun50i_i2c_init.patch  
1969-12-31 16:00:00.0 -0800
+++ u-boot-2019.01+dfsg/debian/patches/sunxi/sun50i_i2c_init.patch  
2019-04-19 15:21:52.0 -0700
@@ -0,0 +1,71 @@
+Description: add i2c initialization for sun50i
+ To use TWI0/1/2 the user can select CONFIG_I2C#_ENABLE.
+ However even the controller is enabled, the mux for the pins
+ are not set.
+ .
+ This patch follows the existing mux method. Since the pads are
+ different, separate check is added for each i2c.
+ .
+ Tested with A64-SOM204 board.
+Author: Stefan Mavrodiev 
+Tested-by: Jonas Smedegaard 
+Origin: https://git.denx.de/?p=u-boot.git;a=commit;h=da1ae59
+Last-Update: 2019-04-14
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/arch/arm/include/asm/arch-sunxi/gpio.h
 b/arch/arm/include/asm/arch-sunxi/gpio.h
+@@ -176,6 +176,7 @@
+ 
+ #define SUN5I_GPE_SDC23
+ #define SUN8I_GPE_TWI23
++#define SUN50I_GPE_TWI2   3
+ 
+ #define SUNXI_GPF_SDC02
+ #define SUNXI_GPF_UART0   4
+@@ -193,8 +194,10 @@
+ #define SUN4I_GPH_SDC15
+ #define SUN6I_GPH_TWI02
+ #define SUN8I_GPH_TWI02
++#define SUN50I_GPH_TWI0   2
+ #define SUN6I_GPH_TWI12
+ #define SUN8I_GPH_TWI12
++#define SUN50I_GPH_TWI1   2
+ #define SUN6I_GPH_TWI22
+ #define SUN6I_GPH_UART0   2
+ #define SUN9I_GPH_UART0   2
+--- a/board/sunxi/board.c
 b/board/sunxi/board.c
+@@ -98,6 +98,10 @@
+   sunxi_gpio_set_cfgpin(SUNXI_GPH(2), SUN8I_GPH_TWI0);
+   sunxi_gpio_set_cfgpin(SUNXI_GPH(3), SUN8I_GPH_TWI0);
+   clock_twi_onoff(0, 1);
++#elif defined(CONFIG_MACH_SUN50I)
++  sunxi_gpio_set_cfgpin(SUNXI_GPH(0), SUN50I_GPH_TWI0);
++  sunxi_gpio_set_cfgpin(SUNXI_GPH(1), SUN50I_GPH_TWI0);
++  clock_twi_onoff(0, 1);
+ #endif
+ #endif
+ 
+@@ -120,6 +124,10 @@
+   sunxi_gpio_set_cfgpin(SUNXI_GPH(4), SUN8I_GPH_TWI1);
+   sunxi_gpio_set_cfgpin(SUNXI_GPH(5), SUN8I_GPH_TWI1);
+   clock_twi_onoff(1, 1);
++#elif defined(CONFIG_MACH_SUN50I)
++  

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

[Gilles Filippini]

Adam D. Barratt a écrit le 20/04/2019 à 12:41 :
> On Sat, 2019-04-20 at 10:43 +0100, Adam D. Barratt wrote:
>> On Tue, 2019-04-16 at 19:37 +0200, Gilles Filippini wrote:
>>> Adam D. Barratt a écrit le 14/04/2019 à 22:48 :
 Control: tags -1 + confirmed

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

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

 Please use "stretch" rather than "stable-proposed-updates" and go
 ahead.
>>>
>>> Done.
>>
>> Unfortunately, the arm64 build appears to be hitting #863152 in
>> binutils. I'm not sure if there's anything that can be done to work
>> around this in cernlib, but noting it here in any case, as it means
>> that cernlib won't be getting into 9.9.
> 
> For the record, if a fix for cernlib can get sorted before the 9.9
> window closes later this weekend (e.g. simply disabling PIE on arm64
> may be sufficient) then getting the updates in should be OK.

The cernlib build system is far from easy to understand and patch. I
don't think I'll be able to find a solution in time for 9.9.

_g.



signature.asc
Description: OpenPGP digital signature

Bug#925552: release-notes: document problems with hidepid vs Buster systemd

[Andrei POPESCU]

On Ma, 26 mar 19, 18:12:38, Justin B Rye wrote:
> 
> The "hidepid" mount-options for /proc (as recommended by various

Why plural? Both the wiki and proc(5) are using singular.

Thanks,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Bug#927428: arbtt-recover leaks memory

[Joey Hess]

Joachim Breitner wrote:
> is that on a broken log file, or one that has errors?

The file does have a lot of problems:

Found header, continuing... (146048068 bytes to go)
Failed to read value at position 74939844:
   Unsupported TimeLogEntry version tag 0
CallStack (from HasCallStack):
  error, called at src/Data.hs:90:15 in main:Data
Failed to read value at position 74939845:
   Unsupported TimeLogEntry version tag 0
CallStack (from HasCallStack):
  error, called at src/Data.hs:90:15 in main:Data
Failed to read value at position 74939846:
   Unsupported TimeLogEntry version tag 0
CallStack (from HasCallStack):
  error, called at src/Data.hs:90:15 in main:Data
Failed to read value at position 74939847:
   Unsupported TimeLogEntry version tag 0
CallStack (from HasCallStack):
  error, called at src/Data.hs:90:15 in main:Data
Failed to read value at position 74939848:
   Unsupported TimeLogEntry version tag 0
CallStack (from HasCallStack):
  error, called at src/Data.hs:90:15 in main:Data
Failed to read value at position 74939849:
   Unsupported TimeLogEntry version tag 0
CallStack (from HasCallStack):
  error, called at src/Data.hs:90:15 in main:Data
Failed to read value at position 74939850:
   Unsupported TimeLogEntry version tag 0
CallStack (from HasCallStack):
  error, called at src/Data.hs:90:15 in main:Data
Failed to read value at position 74939851:
   Unsupported TimeLogEntry version tag 0
CallStack (from HasCallStack):
  error, called at src/Data.hs:90:15 in main:Data
Failed to read value at position 74939852:
   Unsupported TimeLogEntry version tag 0
CallStack (from HasCallStack):
  error, called at src/Data.hs:90:15 in main:Data
Failed to read value at position 74939853:
   Unsupported TimeLogEntry version tag 0
CallStack (from HasCallStack):
  error, called at src/Data.hs:90:15 in main:Data
Failed to read value at position 74939854:
   Unsupported TimeLogEntry version tag 0
CallStack (from HasCallStack):
  error, called at src/Data.hs:90:15 in main:Data
Failed to read value at position 74939855:
   Unsupported TimeLogEntry version tag 0
CallStack (from HasCallStack):
  error, called at src/Data.hs:90:15 in main:Data
Failed to read value at position 74939856:
   Unsupported TimeLogEntry version tag 0
CallStack (from HasCallStack):
  error, called at src/Data.hs:90:15 in main:Data
Failed to read value at position 74939857:
   Unsupported TimeLogEntry version tag 0
CallStack (from HasCallStack):
  error, called at src/Data.hs:90:15 in main:Data
Failed to read value at position 74939858:
   Unsupported TimeLogEntry version tag 0
CallStack (from HasCallStack):
  error, called at src/Data.hs:90:15 in main:Data
Failed to read value at position 74939859:
   Unsupported TimeLogEntry version tag 0
CallStack (from HasCallStack):
  error, called at src/Data.hs:90:15 in main:Data
Failed to read value at position 74939860:
   Unsupported TimeLogEntry version tag 0
CallStack (from HasCallStack):
  error, called at src/Data.hs:90:15 in main:Data
Failed to read value at position 74939861:
   Unsupported TimeLogEntry version tag 0
CallStack (from HasCallStack):
  error, called at src/Data.hs:90:15 in main:Data
Failed to read value at position 74939862:
   Unsupported TimeLogEntry version tag 0
CallStack (from HasCallStack):
  error, called at src/Data.hs:90:15 in main:Data
Failed to read value at position 74939863:
   Unsupported TimeLogEntry version tag 0
CallStack (from HasCallStack):
  error, called at src/Data.hs:90:15 in main:Data
Failed to read value at position 74939864:
   Unsupported TimeLogEntry version tag 0
CallStack (from HasCallStack):
  error, called at src/Data.hs:90:15 in main:Data
Failed to read value at position 74939865:
   Unsupported TimeLogEntry version tag 0
CallStack (from HasCallStack):
  error, called at src/Data.hs:90:15 in main:Data
Failed to read value at position 74939866:
   Unsupported TimeLogEntry version tag 0
CallStack (from HasCallStack):
  error, called at src/Data.hs:90:15 in main:Data
Failed to read value at position 74939867:
   Unsupported TimeLogEntry version tag 0
CallStack (from HasCallStack):
  error, called at src/Data.hs:90:15 in main:Data
Failed to read value at position 74939868:
   Unsupported TimeLogEntry version tag 0
CallStack (from HasCallStack):
  error, called at src/Data.hs:90:15 in main:Data
Failed to read value at position 74939869:
   Unsupported TimeLogEntry version tag 0
CallStack (from HasCallStack):
  error, called at src/Data.hs:90:15 in main:Data
Failed to read value at position 74939870:
   Unsupported TimeLogEntry version tag 0
CallStack (from HasCallStack):
  error, called at src/Data.hs:90:15 in main:Data
Failed to read value at position 74939871:
   Unsupported TimeLogEntry version tag 0
CallStack (from HasCallStack):
  error, called at src/Data.hs:90:15 in main:Data
Failed to read value at position 74939872:
   Unsupported TimeLogEntry version tag 0
CallStack (from HasCallStack):
  error, called at src/Data.hs:90:15 in main:Data
Failed to 

Bug#927481: .help fails with "Sorry! Something went wrong."

[Antoine Beaupre]

Package: sopel
Version: 6.6.2-1
Severity: grave

Sopel, in stable and testing right now, cannot provide a "help" to its
users. It makes it really hard to use (hence the "grave" severity). I'm
also marking this as grave because upstream keeps on churning out
"patch" releases (according to semver) that are really "minor" releases
(according to semver again), so they are not suitable for stable
updates. For example right now there is 6.6.4 release that fixes this
bug:

https://sopel.chat/changelog/6.6.4/

... but it also includes changes like:

 * Cleaned up code in instagram and unicode modules
 * Core modules now use bot.channels instead of deprecated bot.privileges

Which couldn't be eligible for a stable update.

Because I do not want to maintain a fork of 6.6.3 the way I will
probably have to do with 6.5.0 in stretch (argh), i think it's better to
remove sopel from buster and maintain it from backports in the future
(if at all).

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

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

Versions of packages sopel depends on:
ii  adduser3.115
ii  lsb-base   9.20161125
ii  python33.5.3-1
ii  python3-geoip2 2.4.2+dfsg1-1
ii  python3-praw   3.3.0-1
ii  python3-requests   2.12.4-1
ii  python3-tz 2016.7-0.3
ii  python3-xmltodict  0.10.2-1

Versions of packages sopel recommends:
ii  ipython35.1.0-3
ii  python3-enchant 1.6.7-1
ii  python3-feedparser  5.1.3-3
ii  python3-lxml3.7.1-1

sopel suggests no packages.

-- Configuration Files:
/etc/sopel.cfg changed [not included]

-- no debconf information

Bug#927480: Performance: if an fs reports EOPNOTSUPP for xattr/acl calls, don't keep trying

[Andras Korn]

Package: rsync
Version: 3.1.3-6
Severity: wishlist
Tags: upstream

Hi,

according to strace -c, getxattr() and similar calls can take up a lot of
runtime (around ten percent) if there are many files to be synced and other
stuff (I/O, network) is reasonably fast.

It would make sense for rsync to skip such calls for files on a filesystem
that replied with EOPNOTSUPP and save some time.

The stat() family of calls tell rsync which fs the file is on, so that you
just need to wrap the ACL/xattr calls in a wrapper that checks whether the
fs in question is known to not support ACLs/xattrs before calling the actual
syscall/library function.

Counterarguments:

1. "don't call rsync with -AX if your fs doesn't support ACLs/xattrs".
Apparently valid, but maybe I'm syncing a huge tree with more than one
mountpoint, and some of the mounted filesystems support ACLs/xattrs while
others don't.

2. it's possible for an fs to be remounted with ACL/xattr support while
rsync is running; if my suggestion were implemented, rsync could miss some
ACLs/xattrs. My response to that is "don't do that then". :)

András

-- 
 I spilled spot remover on my dog, and now he's gone!

Bug#927479: ITP: node-stealthy-require -- require something bypassing require cache

[Ying-Chun Liu (PaulLiu)]

Package: wnpp
Severity: wishlist
Owner: Ying-Chun Liu (PaulLiu) 

* Package name: node-stealthy-require
  Version : 1.1.1
  Upstream Author : Nicolai Kamenzky (https://github.com/analog-nico)
* URL : https://github.com/analog-nico/stealthy-require#readme
* License : ISC
  Programming Lang: JavaScript
  Description : require something bypassing require cache.
 This is probably the closest you can currently get to require something
 in node.js with completely bypassing the require cache.
 .
 stealthy-require works like this:
 .
 * It clears the require cache.
 * It calls a callback in which you require your module(s) without the cache
   kicking in.
 * It clears the cache again and restores its old state.
 .
 Node.js is an event-based server-side JavaScript engine.

This package is a dependency of request-promise. And request-promise
is a dependency of telegram-bot-api.

This package will be group maintained by Debian Javascript team.


-- 
PaulLiu (劉穎駿)
E-mail: Ying-Chun Liu (PaulLiu) 



signature.asc
Description: OpenPGP digital signature

Bug#924040: ITP: archivebox -- open source self-hosted web archive

[Antoine Beaupré]

On 2019-04-20 11:34:00, W. Martin Borgert wrote:
> On 2019-03-08 13:39, Antoine Beaupre wrote:
>> There are, as far as I know, no similar tool in Debian right
>> now. There are web crawlers and grabbers, but nothing as comprehensive
>> as this.
>
> Many people use xul-ext-scrapbook, but this means, they are
> stuck with firefox 52.9.0esr-1. I proposed packaging
> webext-scrapbookq (#898545), but TBH it does not seem to be an
> adequate replacement. At first sight, archivebox looks better.
>
>> I'd be happy to co-maintain this or delegate to whoever is interested.
>
> I'm willing to help under the PAPT (or other team) umbrella.

That would be great. I have very little time to work on this right now
but would be available to test a package.

Upstream did get their act together to fix Python packaging to be more
standard, I believe. There are talks of uploading to PyPI and using
setup.py properly, and I think it might be time to give it another try,
for what that's worth.

A.
-- 
I believe that love is a better teacher than a sense of duty.
   - Albert Einstein

Bug#820153:

[ND Nuevos Dinamico,Shino Medrano Alonso medrano ND]

Wep

Bug#927191: stretch-pu: package python-django-casclient/1.2.0-2

[William Blough]

Uploaded.  Thanks!

Bug#927139: [src:wine-development] wineserver doens't work when /run/user/pid is not available

[Jens Reyer]

cotrol: tags -1 + moreinfo


Hi Konstantin,

On 15.04.19 15:11, Konstantin Demin wrote:
> Source: wine-development
> Version: 4.2-2
> 
> wineserver fails to setup it's directory when /run/user/${pid} is not
> available due to buggy patch.
> please fix debian/patches/fixes/temporary-directory.patch:
> 
> line 65:
> -+tmp_dir = xmalloc( sizeof(tmp_env) );
> ++tmp_dir = xmalloc( strlen(tmp_env) + 1 );
> 
> line 110:
> -+n = fputs( root + sizeof(tmp_dir) + 1, stream );
> ++n = fputs( root + strlen(tmp_dir) + 1, stream );
> 
> bug is caused by copy-paste mistake, because tmp_env and tmp_dir are
> type of "char *", not "char []", therefore sizeof() isn't equal to
> strlen() + 1.

Thanks for your report.  I can' reproduce the issue here, but
/run/user/$uid exists here (btw: typo pid/uid in your mail).  So can you
please explain more specifically how to trigger this bug?  I'd like to
know if this needs to be fixed for buster.

Besides that, I rebuilt Wine with your fixes and all seems fine.  Your
explanations sound good, but I have to admit I can't really verify them
due to lack of C skills, and in-depth Wine code knowledge.

Greets
jre

Bug#924591: this requires linking in libsparse, which is from Android sources

[殷啟聰 | Kai-Chung Yan]

> So your choice --- we can either reassign this bug back to fastboot or
> android-sdk-platforms-tools, or I can downgrade the severity of this
> bug for e2fsprogs down to wishlist[1].  Let me know how you want to
> handle this.

I would say downgrade it for the moment. We can deal with it after Buster.

Indeed this is quite tricky. I agree that `e2fsprogs` shouldn't depend on 
`libsparse`. I like the `dlopen` approach but it increases the maintenance 
burden a little bit. But anyway I am too mentally tired of yet another AOSP 
fork making into Debian's archive...



signature.asc
Description: OpenPGP digital signature

Bug#927477: ITS: fluxbox -- low resource X11 Window manager

[Tong Sun]

Thanks Paul, for the fast response, as always.

> I say just add yourself and go ahead!

I'm not a DD yet, only a DM. Anyway,

I'll try packing it first, and we'll deal with the upload situation
when we get there.

Thanks again

On Sat, Apr 20, 2019 at 10:49 AM Paul Tagliamonte  wrote:
>
> As an uploader - I'm happy to just mark you as an uploader without all this 
> paperwork. I say just add yourself and go ahead!
>
> Paul
>
>
> On Sat, Apr 20, 2019, 10:42 AM Tong Sun  
> wrote:
>>
>> Package: fluxbox
>> Severity: important
>> Owner:  Dmitry E. Oboukhov 
>>
>> (closed #927457 & redoing it again)
>>
>> * Package name: fluxbox
>> * URL : http://git.fluxbox.org/fluxbox.git
>> * License : MIT
>>   Programming Lang: C++
>>   Description : Highly configurable and low resource X11 Window manager
>>
>> Reason to pack: to salvage the package, because
>>
>> - The last version is over 5 years old
>> - There are
>>   * 3 action needed that are "high"
>>   * 4 bugs tagged patch in the BTS
>>   * 13 lintian warnings
>>
>> I contacted the package owner more than 2 years ago:
>>
>> -- Forwarded message -
>> From: Tong Sun 
>> Date: Sat, May 27, 2017 at 11:31 AM
>> Subject: Re: About Fluxbox
>> To: Dmitry E. Oboukhov 
>>
>>
>> Hi Dmitry,
>>
>> I'd like to push forward the Fluxbox version in Debian to the
>> latest. If you are too busy, I can take a stab.
>>
>> If so, will you sponsor me to review & upload it when I'm
>> done? (I'm currently maintaining two Debian packages and am in
>> the process of getting being officially recognized as DM)
>> -- Forwarded message -
>>
>> but didn't get any reply until now.
>>
>> Thus, I'm officially requesting to salvage the package now,
>> taking over the maintainership.
>>
>> Thanks
>>

Bug#927477: ITS: fluxbox -- low resource X11 Window manager

[Paul Tagliamonte]

As an uploader - I'm happy to just mark you as an uploader without all this
paperwork. I say just add yourself and go ahead!

Paul


On Sat, Apr 20, 2019, 10:42 AM Tong Sun 
wrote:

> Package: fluxbox
> Severity: important
> Owner:  Dmitry E. Oboukhov 
>
> (closed #927457 & redoing it again)
>
> * Package name: fluxbox
> * URL : http://git.fluxbox.org/fluxbox.git
> * License : MIT
>   Programming Lang: C++
>   Description : Highly configurable and low resource X11 Window manager
>
> Reason to pack: to salvage the package, because
>
> - The last version is over 5 years old
> - There are
>   * 3 action needed that are "high"
>   * 4 bugs tagged patch in the BTS
>   * 13 lintian warnings
>
> I contacted the package owner more than 2 years ago:
>
> -- Forwarded message -
> From: Tong Sun 
> Date: Sat, May 27, 2017 at 11:31 AM
> Subject: Re: About Fluxbox
> To: Dmitry E. Oboukhov 
>
>
> Hi Dmitry,
>
> I'd like to push forward the Fluxbox version in Debian to the
> latest. If you are too busy, I can take a stab.
>
> If so, will you sponsor me to review & upload it when I'm
> done? (I'm currently maintaining two Debian packages and am in
> the process of getting being officially recognized as DM)
> -- Forwarded message -
>
> but didn't get any reply until now.
>
> Thus, I'm officially requesting to salvage the package now,
> taking over the maintainership.
>
> Thanks
>
>

Bug#927478: rust-doc: font-awesome not picked up by Firefox

[Shai Berger]

Package: rust-doc
Version: 1.32.0+dfsg1-3
Severity: minor

Dear Maintainer,

I like to browse the rust book using my locally installed
copy of the Rust documentation. Also, I use Firefox.

I've noticed for a long time that some icons in the book
web pages, like the "previous" and "next" buttons, are not
displayed as proper characters, and instead are showing just
a hexadecimal character code.

Today I checked and found:
- These symbols are created by use of Font Awesome
- Chromium, unlike Firefox, does show the correct symbols
- Firefox does show the symbols in the online version
  of the book

So I think that the problem is that the packaging somehow
prevents Firefox from picking up the correct fonts.

Thanks,
Shai.



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

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

Versions of packages rust-doc depends on:
ii  fonts-font-awesome  5.0.10+really4.7.0~dfsg-1
ii  fonts-open-sans 1.11-1
ii  libjs-highlight.js  9.12.0+dfsg1-4
ii  libjs-jquery3.3.1~dfsg-1
ii  libjs-mathjax   2.7.4+dfsg-1

Versions of packages rust-doc recommends:
ii  cargo-doc  0.33.0-1

rust-doc suggests no packages.

-- no debconf information

Bug#927477: ITS: fluxbox -- low resource X11 Window manager

[Tong Sun]

Package: fluxbox
Severity: important
Owner:  Dmitry E. Oboukhov 

(closed #927457 & redoing it again)

* Package name: fluxbox
* URL : http://git.fluxbox.org/fluxbox.git
* License : MIT
  Programming Lang: C++
  Description : Highly configurable and low resource X11 Window manager

Reason to pack: to salvage the package, because

- The last version is over 5 years old
- There are
  * 3 action needed that are "high"
  * 4 bugs tagged patch in the BTS
  * 13 lintian warnings

I contacted the package owner more than 2 years ago:

-- Forwarded message -
From: Tong Sun 
Date: Sat, May 27, 2017 at 11:31 AM
Subject: Re: About Fluxbox
To: Dmitry E. Oboukhov 


Hi Dmitry, 

I'd like to push forward the Fluxbox version in Debian to the
latest. If you are too busy, I can take a stab.

If so, will you sponsor me to review & upload it when I'm
done? (I'm currently maintaining two Debian packages and am in
the process of getting being officially recognized as DM)
-- Forwarded message -

but didn't get any reply until now.

Thus, I'm officially requesting to salvage the package now,
taking over the maintainership.

Thanks

Bug#923962: 923962: tigervnc-standalone-server: crashes on ARM after VncAuth

[Bernhard Übelacker]

Control: reassign 923962 libunwind8 1.2.1-9
Control: affects 923962 tigervnc


Dear Maintainer,
I guess this could be a problem in libunwind8 at aarch64.
Please find in message #15 some more details.

Kind regards,
Bernhard


#15  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923962#15

Bug#927457: ITP: fluxbox -- low resource X11 Window manager

[Tong Sun]

close 927457
stop

Redoing it again...

On Sat, Apr 20, 2019 at 10:20 AM Tong Sun
 wrote:
>
> reassign 927457 fluxbox
> stop
>
> On Sat, Apr 20, 2019 at 6:10 AM Tobias Frost  wrote:
> >
> > Hi Tong,
> >
> > On Fri, Apr 19, 2019 at 11:53:54PM -0400, Tong Sun wrote:
> > >
> > > * Package name: fluxbox
> >
> > > Reason to pack: to salvage the package, because
> >
> > when you want to salvage the package, you should follow the ITS
> > procedure and not filing an ITP bug.
> >
> > (ITS procedure is documented here:)
> > https://wiki.debian.org/PackageSalvaging and
> > https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#package-salvaging
> >
> > Cheers,
> > tobi

Bug#926386: free(): double free detected in tcache 2

[Bernhard Übelacker]

Dear Maintainer,
I just tried to collect some more info from this crash.

I got this by using "peek --backend=gnome-shell"
inside a gnome/wayland session.

Using some reverse debugging, I guess all happens below function
peek_post_processing_ffmpeg_post_processor_generate_animation_async_co,
that seems to translate to function generate_animation_async
in ffmpeg-post-processor.vala.

As I have near to no knowledge of vala I just guess,
that the args array gets automatically destructed at function end.
But before the content gets appended to argv.
There function append_vals may not do a deep copy,
which leads then at argv destruction to the double free.

This should be checked by someone with more vala
knowledge than me.
At least a package built with attached patch does
not crash and could produce a animated gif.
Also attached some more details on the debugging.

Kind regards,
Bernhard


benutzer@debian:~/source/peek/orig3/peek-1.3.1$ cat -n 
./src/post-processing/ffmpeg-post-processor.vala | grep -E "^   100" -B24 -A12
76
77  private async File? generate_animation_async (File input_file, File 
palette_file) throws RecordingError {
78try {
79  var extension = Utils.get_file_extension_for_format 
(config.output_format);
80  var output_file = Utils.create_temp_file (extension);
81
82  string[] args = {
83"ffmpeg", "-y",
84"-i", input_file.get_path (),
85"-i", palette_file.get_path (),
86"-filter_complex", "fps=%d,paletteuse".printf 
(config.framerate)
87  };
88
89  var argv = new Array ();
90  argv.append_vals (args, args.length);
91
92  if (config.output_format == OutputFormat.APNG) {
93argv.append_val ("-plays");
94argv.append_val ("0");
95  }
96
97  argv.append_val (output_file);
98
99  try {
   100yield spawn_command_async (argv.data);
   101  } catch (RecordingError e) {
   102FileUtils.remove (output_file);
   103throw e;
   104  }
   105
   106  return File.new_for_path (output_file);
   107} catch (FileError e) {
   108  throw new RecordingError.POSTPROCESSING_ABORTED (e.message);
   109}
   110  }
   111}
   112  }


(rr) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x7fcc71571535 in __GI_abort () at abort.c:79
#2  0x7fcc715c8778 in __libc_message (action=action@entry=do_abort, 
fmt=fmt@entry=0x7fcc716d328d "%s\n") at ../sysdeps/posix/libc_fatal.c:181
#3  0x7fcc715cee6a in malloc_printerr (str=str@entry=0x7fcc716d4f58 
"free(): double free detected in tcache 2") at malloc.c:5341
#4  0x7fcc715d094d in _int_free (av=0x7fcc7170ac40 , 
p=0x55c5839da7a0, have_lock=) at malloc.c:4193
#5  0x55c5815ab82e in _vala_array_destroy (destroy_func=, 
array_length=, array=0x55c5839da760) at 
./obj-x86_64-linux-gnu/src/post-processing/ffmpeg-post-processor.c:1103
#6  _vala_array_free (destroy_func=, array_length=, array=0x55c5839da760) at 
./obj-x86_64-linux-gnu/src/post-processing/ffmpeg-post-processor.c:1115
#7  peek_post_processing_ffmpeg_post_processor_generate_animation_async_co 
(_data_=0x55c5839f20c0) at 
./obj-x86_64-linux-gnu/src/post-processing/ffmpeg-post-processor.c:1010
#8  0x55c5815a9912 in 
peek_post_processing_cli_post_processor_spawn_command_async_async_ready_wrapper 
(source_object=0x55c5837482a0, res=0x55c583742110, 
user_data=user_data@entry=0x55c5839f20c0) at 
./obj-x86_64-linux-gnu/src/post-processing/cli-post-processor.c:147
#9  0x7fcc71b2b719 in g_task_return_now (task=0x55c583742110) at 
../../../gio/gtask.c:1148
#10 0x7fcc71b2c196 in g_task_return (task=0x55c583742110, type=) at ../../../gio/gtask.c:1206
#11 0x55c5815a9bc4 in 
peek_post_processing_cli_post_processor_spawn_command_async_co 
(_data_=0x55c58347d7b0) at 
./obj-x86_64-linux-gnu/src/post-processing/cli-post-processor.c:310
#12 0x7fcc71b2b719 in g_task_return_now (task=0x55c583710a70) at 
../../../gio/gtask.c:1148
#13 0x7fcc71b2b759 in complete_in_idle_cb (task=0x55c583710a70) at 
../../../gio/gtask.c:1162
#14 0x7fcc71961dd8 in g_main_dispatch (context=0x55c58346d320) at 
../../../glib/gmain.c:3182
#15 g_main_context_dispatch (context=context@entry=0x55c58346d320) at 
../../../glib/gmain.c:3847
#16 0x7fcc719621c8 in g_main_context_iterate (context=0x55c58346d320, 
block=block@entry=1, dispatch=dispatch@entry=1, self=) at 
../../../glib/gmain.c:3920
#17 0x7fcc719624c2 in g_main_loop_run (loop=0x55c583931e80) at 
../../../glib/gmain.c:4116
#18 0x7fcc72052583 in gtk_dialog_run (dialog=dialog@entry=0x55c58387e2d0) 
at ../../../../gtk/gtkdialog.c:1398
#19 0x55c5815b67df in peek_ui_application_window_show_file_chooser 
(self=0x55c58376e4f0) at 

Bug#927457: ITP: fluxbox -- low resource X11 Window manager

[Tong Sun]

reassign 927457 fluxbox
stop

On Sat, Apr 20, 2019 at 6:10 AM Tobias Frost  wrote:
>
> Hi Tong,
>
> On Fri, Apr 19, 2019 at 11:53:54PM -0400, Tong Sun wrote:
> >
> > * Package name: fluxbox
>
> > Reason to pack: to salvage the package, because
>
> when you want to salvage the package, you should follow the ITS
> procedure and not filing an ITP bug.
>
> (ITS procedure is documented here:)
> https://wiki.debian.org/PackageSalvaging and
> https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#package-salvaging
>
> Cheers,
> tobi

Bug#927457: ITP: fluxbox -- low resource X11 Window manager

[Tong Sun]

Ops, missed that one too -- now I know what "against the package in
question" really means now. thx!

On Sat, Apr 20, 2019 at 9:27 AM Tobias Frost  wrote:
>
> Hi Tong Sun,
>
> On Sat, Apr 20, 2019 at 08:55:54AM -0400, Tong Sun wrote:
> > On Sat, Apr 20, 2019 at 6:10 AM Tobias Frost wrote:
> >
> > > > Reason to pack: to salvage the package, because
> > >
> > > when you want to salvage the package, you should follow the ITS
> > > procedure and not filing an ITP bug.
> >
> > Oh, thanks Tobi, I was, at least I was trying to, but missed one detail, :-)
> > The title is fixed now.
> > thanks again
>
> thanks for this, but please note that the ITS package should be filed
> against the package in question, not against wnpp.
>
> Cheers,
> tobi

Bug#927476: lintian: Please add --onlyrun examples

[Niels Thykier]

Chris Lamb:
> Package: lintian
> Version: 2.12.0
> Severity: wishlist
> X-Debbugs-CC: Felix Lechner 
> 
> Hi,
> 
> I'm currently really failing to understand how --onlyrun works. For
> example:
> 
>   $ t/bin/runtests 
> --onlyrun=test:control-file-rules-requires-root-binary-targets
> 
> ... does not run any tests.
> 
> I'm sure I'm just calling it wrong and, to be clear, this bug report
> is not about this issue but rather could you please add some concrete
> examples to the manual page for each selector type (script, tag, etc.)
> 
> 
> Best wishes,
> 

We already examples in Lintian::Tutorial::TestSuite
(doc/tutorial/Lintian/Tutorial/TestSuite.pod).  However, I suspect they
have not been updated to reflect the "recent" changes to the test suite
and its runner.  I guess Lintian::Tutorial::WritingTests is equally out
of date.

Note: I am fine with removing those POD documents if we now prefer to
keep this documentation elsewhere.  However, if they remain, they should
be updated to reflect the reality.

Thanks,
~Niels

Bug#927457: ITP: fluxbox -- low resource X11 Window manager

[Tobias Frost]

Hi Tong Sun,

On Sat, Apr 20, 2019 at 08:55:54AM -0400, Tong Sun wrote:
> On Sat, Apr 20, 2019 at 6:10 AM Tobias Frost wrote:
> 
> > > Reason to pack: to salvage the package, because
> >
> > when you want to salvage the package, you should follow the ITS
> > procedure and not filing an ITP bug.
> 
> Oh, thanks Tobi, I was, at least I was trying to, but missed one detail, :-)
> The title is fixed now.
> thanks again

thanks for this, but please note that the ITS package should be filed
against the package in question, not against wnpp.

Cheers,
tobi

Bug#927476: lintian: Please add --onlyrun examples

[Chris Lamb]

Package: lintian
Version: 2.12.0
Severity: wishlist
X-Debbugs-CC: Felix Lechner 

Hi,

I'm currently really failing to understand how --onlyrun works. For
example:

  $ t/bin/runtests 
--onlyrun=test:control-file-rules-requires-root-binary-targets

... does not run any tests.

I'm sure I'm just calling it wrong and, to be clear, this bug report
is not about this issue but rather could you please add some concrete
examples to the manual page for each selector type (script, tag, etc.)


Best wishes,

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

Bug#927475: [xpra]

[Antonio Russo]

Package: xpra
Version: 2.5+dfsg1-1
Severity: important

--- Please enter the report below this line. ---

The port to python3 has resulted in different packages being
required to run xpra (in particular, python-gtk2 has no
corresponding python3-gtk{2,3} analogue).

A fresh install of xpra wont open, because gir1.2-gtk-3.0 is
not recommended/required by python3-gi(-cairo), or any other
recursive dependency of xpra for that matter.

There may be some other way to load an appropriate python3 UI
module, but a requires (or at least recommends) on gir1.2-gtk-3.0
would massively improve user experience.

Thanks!

Bug#927457: ITP: fluxbox -- low resource X11 Window manager

[Tong Sun]

On Sat, Apr 20, 2019 at 6:10 AM Tobias Frost wrote:

> > Reason to pack: to salvage the package, because
>
> when you want to salvage the package, you should follow the ITS
> procedure and not filing an ITP bug.

Oh, thanks Tobi, I was, at least I was trying to, but missed one detail, :-)
The title is fixed now.
thanks again

Bug#927474: [xpra] Does not start (LOCAL_MODIFICATIONS is not an integer)

[Antonio Russo]

Package: xpra
Version: 2.5+dfsg1-1
Severity: grave

--- Please enter the report below this line. ---
Thanks for packaging the new xpra release! It does not start, because
LOCAL_MODIFICATIONS in /usr/lib/python3/dist-packages/xpra/src_info.py
is a string, but /usr/lib/python3/dist-packages/xpra/version_utils.py
line 30 compares that variable to the integer 0.

The rest of the xpra stack seems to expect LOCAL_MODIFICATIONS to be
an integer. For instance, on the client, in
/usr/lib/python3/dist-packages/xpra/client/gtk_base/session_info.py
at lines 169/191/200.

Bug#927473: dpkg: warning: while removing fonts-noto-core, directory '/usr/share/fonts/truetype/noto' not empty so not removed

[積丹尼 Dan Jacobson]

Package: fonts-noto-core
Version: 20181227-1

Purging configuration files for fonts-noto-core (20181227-1) ...
dpkg: warning: while removing fonts-noto-core, directory 
'/usr/share/fonts/truetype/noto' not empty so not removed

-rw-r--r--  1 root root36 2018-04-12  .uuid

Bug#910999: RFP: mxisd -- Federated Matrix Identity Server

[Linda Lapinlampi]

On Sun, Oct 14, 2018 at 03:54:16PM +, Johannes Keyser wrote:
> * Package name: mxisd
>   Version : 1.2.0
>   Upstream Author : Max Dor 
> * URL : https://github.com/kamax-matrix/mxisd
> * License : AGPL-3.0
>   Programming Lang: Java
>   Description : Federated Matrix Identity Server

As of mxisd 1.3.1, mxisd depends on undertow (libundertow-java) instead
of Spring Boot. undertow is not going to be included in Buster release:
https://bugs.debian.org/903916

I also looked at the potential dependencies required.

> mxisd dependencies missing from Debian GNU/Linux:
>
> * matrix-java-sdk
> * ormlite-jdbc
> * eddsa
> * libphonenumber-java (`8.7.1`) – there is `7.1.0` available, and a
>   newer Python package for `8.9.10`
> * firebase-admin
> * sqlite-jdbc (?)
> * twilio (Java)
> * sendgrid
> * zt-exec
>
> Testing stuff missing:
>
> * wiremock
> * unboundid
> * greenmail
>
> Other stuff:
>
> * `libc3p0-java` exists, but an older verison: `0.9.1.2`. mxisd
>depends on version `0.9.5.2` it seems.
> * `libmariadb-java` is quite much (?) newer in Debian than what mxisd
>depends on.
> *  libundertow-java is `1.4.25` in Debian, mxisd depends on
>`2.0.16.Final`

I've also understood from a conversation with the upstream author he's
not very interested to spend a lot of time on mxisd after the upcoming
1.4.0 release, but focus on gridepo stuff instead. Rewriting mxisd from
undertow to some other HTTP library (e.g. Jetty) is unlikely at this
time.

Attached is the output of gradle dependencies from mxisd 1.3.1 (current
stable version).
:dependencies


Root project


apiElements - API elements for main. (n)
No dependencies

archives - Configuration for archive artifacts.
No dependencies

compile - Dependencies for source set 'main' (deprecated, use 'implementation ' 
instead).
+--- org.slf4j:slf4j-simple:1.7.25
|\--- org.slf4j:slf4j-api:1.7.25
+--- commons-io:commons-io:2.5
+--- org.yaml:snakeyaml:1.23
+--- io.kamax:matrix-java-sdk:0.0.14-8-g0e57ec6
|+--- org.slf4j:log4j-over-slf4j:1.7.25
||\--- org.slf4j:slf4j-api:1.7.25
|+--- org.apache.commons:commons-lang3:3.7
|+--- commons-io:commons-io:2.5
|+--- commons-codec:commons-codec:1.11
|+--- com.squareup.okhttp3:okhttp:3.11.0
||\--- com.squareup.okio:okio:1.14.0
|+--- com.google.code.gson:gson:2.8.0
|\--- net.i2p.crypto:eddsa:0.1.0
+--- com.j256.ormlite:ormlite-jdbc:5.0
|\--- com.j256.ormlite:ormlite-core:5.0
+--- net.i2p.crypto:eddsa:0.1.0
+--- org.apache.directory.api:api-all:1.0.0
|+--- org.slf4j:slf4j-api:1.7.25
|+--- 
org.apache.servicemix.bundles:org.apache.servicemix.bundles.xpp3:1.1.4c_7
|+--- 
org.apache.servicemix.bundles:org.apache.servicemix.bundles.dom4j:1.6.1_5
||\--- xml-apis:xml-apis:1.0.b2
|+--- xml-apis:xml-apis:1.0.b2
|+--- commons-pool:commons-pool:1.6
|+--- org.apache.mina:mina-core:2.0.16
||\--- org.slf4j:slf4j-api:1.7.21 -> 1.7.25
|+--- commons-lang:commons-lang:2.6
|+--- commons-collections:commons-collections:3.2.2
|+--- 
org.apache.servicemix.bundles:org.apache.servicemix.bundles.antlr:2.7.7_5
|\--- commons-codec:commons-codec:1.10 -> 1.11
+--- dnsjava:dnsjava:2.1.8
+--- org.apache.httpcomponents:httpclient:4.5.3
|+--- org.apache.httpcomponents:httpcore:4.4.6
|+--- commons-logging:commons-logging:1.2
|\--- commons-codec:commons-codec:1.9 -> 1.11
+--- com.googlecode.libphonenumber:libphonenumber:8.7.1
+--- javax.mail:javax.mail-api:1.6.2
+--- com.sun.mail:javax.mail:1.6.2
|\--- javax.activation:activation:1.1
+--- com.google.firebase:firebase-admin:5.3.0
|+--- com.google.api-client:google-api-client:1.22.0
||+--- com.google.oauth-client:google-oauth-client:1.22.0
|||+--- com.google.http-client:google-http-client:1.22.0
||||+--- com.google.code.findbugs:jsr305:1.3.9 -> 3.0.0
||||\--- org.apache.httpcomponents:httpclient:4.0.1 -> 4.5.3 (*)
|||\--- com.google.code.findbugs:jsr305:1.3.9 -> 3.0.0
||+--- com.google.http-client:google-http-client-jackson2:1.22.0
|||+--- com.google.http-client:google-http-client:1.22.0 (*)
|||\--- com.fasterxml.jackson.core:jackson-core:2.1.3 -> 2.8.7
||\--- com.google.guava:guava-jdk5:17.0
|+--- com.google.api-client:google-api-client-gson:1.22.0
||+--- com.google.api-client:google-api-client:1.22.0 (*)
||\--- com.google.http-client:google-http-client-gson:1.22.0
|| +--- com.google.http-client:google-http-client:1.22.0 (*)
|| \--- com.google.code.gson:gson:2.1 -> 2.8.0
|+--- com.google.http-client:google-http-client:1.22.0 (*)
|+--- org.json:json:20160810
|+--- com.google.guava:guava:20.0
|+--- com.google.cloud:google-cloud-storage:1.2.1
||+--- 

Bug#927472: The units of duration are not explained. Microseconds?

[積丹尼 Dan Jacobson]

Package: grub2-common
Version: 2.02+dfsg1-16
Severity: wishlist
File: grub2-common

(info "(grub) play")

 -- Command: play file | tempo [pitch1 duration1] [pitch2 duration2] ...

The units of duration are not explained. Microseconds?

Bug#927471: curl: Regression that fails to exhaust socket data

[Guillem Jover]

Source: curl
Source-Version: 7.64.0-2
Severity: serious
Control: affects -1 rtorrent

Hi!

I've started noticing rtorrent busy-looping at some points after
finishing a torrent. stracing and gdb'ing the process it was doing
that in its main loop, spamming on gettimeofday() and epoll_wait().

Checking the rtorrent dependencies I've not seen much suspicious
updated recently, except for curl. I checked then the upstream bug
trackers and noticed quite many instances of "100% cpu usage" reports,
such as . And that
one points to old and new curl issue. The last instance of it appears
to have been fixed with 
in 7.64.1.

So I think curl should be either upgraded to that release, or the
relevant commits cherry-picked.

Thanks,
Guillem

Bug#927470: zsh: Segfault on completion menu in large git repo's

[Wesley Schwengle]

Package: zsh
Version: 5.7.1-1
Severity: important
Tags: upstream

Dear Maintainer,

ZSH seems to segfault in the following scenario in larger git
repositories:

```
vi Zaaksysteem::Bar::voo::vooo::voo
# you'll receive the following message: Killed by signal in compadd after 0s
vi 
# segfault
```

Steps to reproduce this:

* cd /tmp
* git clone g...@github.com:git/git.git
* cd git
* zsh -f
* Set the following options:

```
autoload -Uz compinit

zstyle ':completion:*' completer _complete _match _approximate
zstyle ':completion:*:match:*' original only
zstyle ':completion:*:approximate:*' max-errors 1 numeric
zstyle ':completion:*' menu select
zstyle -e ':completion:*:approximate:*' \
max-errors 'reply=($((($#PREFIX+$#SUFFIX)/3))numeric)'

zstyle ':completion:*' squeeze-slashes true

_ZCOMP=${ZDOTDIR:-$HOME}/.zcompdump
today=$(date --date '00:00 today' +%s)
if [[ ! -e $_ZCOMP || $today -gt $(stat --format %Y $_ZCOMP) ]];
then
compinit -i
touch ${_ZCOMP}
else
compinit -C;
fi
unset _ZCOMP
```

* now execute the following commands
```
vi Zaaksysteem::Bar::voo::vooo::voo
# you'll receive the following message: Killed by signal in compadd after 0s
vi 
# segfault
```

I've submitted this bug already to upstream[1].

Cheers,
Wesley


[1]: http://www.zsh.org/mla/workers/2019/msg00251.html


-- Package-specific info:

Packages which provide vendor completions:

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++--===--
ii  curl 7.64.0-2amd64command line tool 
for transferring data with URL syntax
ii  docker-ce-cli5:18.09.5~3-0~debian-buster amd64Docker CLI: the 
open-source application container engine
ii  git-buildpackage 0.9.14  all  Suite to help 
with Debian packages in Git repositories
ii  lastpass-cli 1.3.2-1 amd64command line 
interface to LastPass.com
ii  mpv  0.29.1-1amd64video player 
based on MPlayer/mplayer2
ii  pulseaudio   12.2-4  amd64PulseAudio sound 
server
ii  systemd  241-3   amd64system and 
service manager
ii  udev 241-3   amd64/dev/ and hotplug 
management daemon
ii  vlc-bin  3.0.6-1 amd64binaries from VLC
ii  youtube-dl   2019.01.17-1all  downloader of 
videos from YouTube and other sites

dpkg-query: no path found matching pattern /usr/share/zsh/vendor-functions/


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

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

Versions of packages zsh depends on:
ii  libc6   2.28-8
ii  libcap2 1:2.25-2
ii  libtinfo6   6.1+20181013-2
ii  zsh-common  5.7.1-1

Versions of packages zsh recommends:
ii  libc6 2.28-8
ii  libncursesw6  6.1+20181013-2
ii  libpcre3  2:8.39-12

Versions of packages zsh suggests:
pn  zsh-doc  

-- no debconf information

Bug#927226: Additional Information

[Voip Gainer]

I did some additional work to narrow down the problem by installing alpha
candidates offline. The last working version was alpha 4, the first version
which does not set papersize to A4 is alpha 5.
I also tried other locales such as Italian/Italy with the same result.

I used the DVD images from http://cdimage.debian.org/cdimage/

Bug#926980: Considering to close this thread due to my testing hw rotation.

[hoxp18]

Dear maintainers,

I reported resume-blank-screen issue on this thread,
but I've already lost the env. to do another stuffs
on that machine.

FYI:

* The issue might have common root with the two reports
  Bug#927094 and Bug#927324,
  which is actually on the same hw.

* I'll clean install the next Buster image on
  my H110 machine, and keep the machine above,
  which is Stretch -> dist-upgrade -> Buster,
  since it has LVM-over-LUKS,
  and Buster introduced LUKS2.

  It seems nothing LUKS related problem on my tests.

Regards.

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

[Adam D. Barratt]

On Sat, 2019-04-20 at 10:43 +0100, Adam D. Barratt wrote:
> On Tue, 2019-04-16 at 19:37 +0200, Gilles Filippini wrote:
> > Adam D. Barratt a écrit le 14/04/2019 à 22:48 :
> > > Control: tags -1 + confirmed
> > > 
> > > On Fri, 2019-02-22 at 17:29 +0100, Gilles Filippini wrote:
> > > > Because RC bug #922453 affects Stretch as well, I propose a
> > > > stable
> > > > update
> > > > for cernlib. Debdiff attached.
> > > 
> > > cernlib (20061220+dfsg3-4.3+deb9u1) stable-proposed-updates;
> > > urgency=medium
> > > 
> > > Please use "stretch" rather than "stable-proposed-updates" and go
> > > ahead.
> > 
> > Done.
> 
> Unfortunately, the arm64 build appears to be hitting #863152 in
> binutils. I'm not sure if there's anything that can be done to work
> around this in cernlib, but noting it here in any case, as it means
> that cernlib won't be getting into 9.9.

For the record, if a fix for cernlib can get sorted before the 9.9
window closes later this weekend (e.g. simply disabling PIE on arm64
may be sufficient) then getting the updates in should be OK.

Regards,

Adam

Bug#927468: Debian 10 RC1 successfully installed at HP 17-by Notebook

[Bernhard]

Package: installation-reports

Boot method: USB-drive
Image version: Self-made installation image with Debian 10 RC1
Date: 2019-04-20

Machine: HP Notebook 17" by-Series
Processor: Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
Memory: 8GB
Partitions: -

Output of lspci -knn:

> 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
> Processor Host Bridge/DRAM Registers [8086:5914] (rev 08)
>   Subsystem: Hewlett-Packard Company Xeon E3-1200 v6/7th Gen Core 
> Processor Host Bridge/DRAM Registers [103c:84cb]
>   Kernel driver in use: skl_uncore
> 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 
> [8086:5917] (rev 07)
>   Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:84cb]
>   Kernel driver in use: i915
>   Kernel modules: i915
> 00:04.0 Signal processing controller [1180]: Intel Corporation Skylake 
> Processor Thermal Subsystem [8086:1903] (rev 08)
>   Subsystem: Hewlett-Packard Company Xeon E3-1200 v5/E3-1500 v5/6th Gen 
> Core Processor Thermal Subsystem [103c:84cb]
>   Kernel driver in use: proc_thermal
>   Kernel modules: processor_thermal_device
> 00:08.0 System peripheral [0880]: Intel Corporation Skylake Gaussian Mixture 
> Model [8086:1911]
>   Subsystem: Hewlett-Packard Company Xeon E3-1200 v5/v6 / E3-1500 v5 / 
> 6th/7th Gen Core Processor Gaussian Mixture Model [103c:84cb]
> 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 
> xHCI Controller [8086:9d2f] (rev 21)
>   Subsystem: Hewlett-Packard Company Sunrise Point-LP USB 3.0 xHCI 
> Controller [103c:84cb]
>   Kernel driver in use: xhci_hcd
>   Kernel modules: xhci_pci
> 00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise 
> Point-LP Thermal subsystem [8086:9d31] (rev 21)
>   Subsystem: Hewlett-Packard Company Sunrise Point-LP Thermal subsystem 
> [103c:84cb]
>   Kernel driver in use: intel_pch_thermal
>   Kernel modules: intel_pch_thermal
> 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP 
> CSME HECI #1 [8086:9d3a] (rev 21)
>   Subsystem: Hewlett-Packard Company Sunrise Point-LP CSME HECI 
> [103c:84cb]
>   Kernel driver in use: mei_me
>   Kernel modules: mei_me
> 00:17.0 RAID bus controller [0104]: Intel Corporation 82801 Mobile SATA 
> Controller [RAID mode] [8086:282a] (rev 21)
>   Subsystem: Hewlett-Packard Company 82801 Mobile SATA Controller [RAID 
> mode] [103c:84cb]
>   Kernel driver in use: ahci
>   Kernel modules: ahci
> 00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express 
> Root Port [8086:9d10] (rev f1)
>   Kernel driver in use: pcieport
> 00:1c.4 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express 
> Root Port #5 [8086:9d14] (rev f1)
>   Kernel driver in use: pcieport
> 00:1c.5 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express 
> Root Port #6 [8086:9d15] (rev f1)
>   Kernel driver in use: pcieport
> 00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point LPC 
> Controller/eSPI Controller [8086:9d4e] (rev 21)
>   Subsystem: Hewlett-Packard Company Sunrise Point LPC Controller/eSPI 
> Controller [103c:84cb]
> 00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-LP PMC 
> [8086:9d21] (rev 21)
>   Subsystem: Hewlett-Packard Company Sunrise Point-LP PMC [103c:84cb]
> 00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio 
> [8086:9d71] (rev 21)
>   Subsystem: Hewlett-Packard Company Sunrise Point-LP HD Audio [103c:84cb]
>   Kernel driver in use: snd_hda_intel
>   Kernel modules: snd_hda_intel, snd_soc_skl
> 00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-LP SMBus [8086:9d23] 
> (rev 21)
>   Subsystem: Hewlett-Packard Company Sunrise Point-LP SMBus [103c:84cb]
>   Kernel driver in use: i801_smbus
>   Kernel modules: i2c_i801
> 01:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Jet 
> PRO [Radeon R5 M230] [1002:6665] (rev c3)
>   Subsystem: Hewlett-Packard Company Jet PRO [Radeon R5 M230 / R7 M260DX 
> / Radeon 520 Mobile] [103c:84cb]
>   Kernel driver in use: radeon
>   Kernel modules: radeon, amdgpu
> 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
> RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
>   Subsystem: Hewlett-Packard Company RTL8111/8168/8411 PCI Express 
> Gigabit Ethernet Controller [103c:84cb]
>   Kernel driver in use: r8169
>   Kernel modules: r8169
> 03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8821CE 
> 802.11ac PCIe Wireless Network Adapter [10ec:c821]
>   Subsystem: Hewlett-Packard Company RTL8821CE 802.11ac PCIe Wireless 
> Network Adapter [103c:831a]

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

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD: 

Bug#925178: closed by Utkarsh Gupta (Bug#925178: fixed in ruby-globalid 0.4.2-1)

[Santiago Vila]

severity 925178 serious
tags 925178 + ftbfs
thanks

On Sun, 24 Mar 2019, Paul Gevers wrote:

> Hi all,
> 
> On 24-03-2019 07:21, Debian Bug Tracking System wrote:
> >  ruby-globalid (0.4.2-1) unstable; urgency=medium
> >  .
> >* Team upload
> >* New upstream version 0.4.2
> >* Add patch to fix regression (Closes: #925178)
> >* Drop patches that are merged in upstream
> >* Bump debhelper compatibility level to 11
> >* Bump Standards-Version to 4.3.0 (no changes needed)
> >* Fix insecure URL
> 
> Thanks for the quick fix for this issue. However, due to the new
> upstream version and the debhelper compatibility bump this version is
> not eligible [1] for an unblock for buster.
> 
> Did rails 2:5.2.2.1+dfsg-1 break ruby-globalid or did it only break the
> autopkgtest of it?

In this case, breaking the tests is the same as breaking the package,
because the tests are part of the package build and the package
currently FTBFS in buster with the same ENOENT error:

https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/ruby-globalid.html

Raising to serious, since this is also a FTBFS problem.

Thanks.

Bug#912784: stretch-pu: package davix/0.6.4-1.1+deb9u1

[Adam D. Barratt]

On Tue, 2019-01-08 at 09:50 +0100, Mattias Ellert wrote:
> Davix implements (among other things) a client to a gridsite
> > service
> (a
> SOAP web service based file server protocol). It queries the server
> for
> what version it is running in order to know which credential
> delegation
> method to use.
> 
> The old code used the "getVersion" call to get the version, which
> returns the software version of the server. However, there exists
> several different implementations of the server, so the version of
> the
> server software is not indicative on what credential delegation
> method
> it implements.
> 
> What determines which delegation method to use is the interface
> version implemented by the server, not the version number of the
> server software. By using the getInterfaceVersion call instead the
> davix client will use the correct delegation method.
> 
> https://its.cern.ch/jira/browse/DMC-1047
> 

Sorry for not getting back to you again sooner.

The bug fix sounds OK. What's the d/rules change about? It's not
mentioned in the changelog.

+   rm -rf debian/tmp/usr/share/doc/davix/html/.doctrees

Regards,

Adam

Bug#927422: stretch-pu: package jquery/3.1.1-2+deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Sat, 2019-04-20 at 08:10 +0200, Salvatore Bonaccorso wrote:
> Hi,
> 
> On Fri, Apr 19, 2019 at 03:01:16PM +0200, Xavier Guimard wrote:
> > I fixed https://snyk.io/vuln/SNYK-JS-JQUERY-174006 vulnerability
> > for
> > Buster. Here is the fix for Stretch. It just avoid Object.prototype
> > pollution without chnaging behavior. Could you insert it in next
> > stretch
> > update ?
> 
> CVE-2019-11358 was assigned for the respective issue.

Please add that to the changelog and go ahead with the upload, bearing
in mind that the window for 9.9 closes during this weekend.

Regards,

Adam

Bug#927378: stretch-pu: package node-superagent/0.20.0+dfsg-1+deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Thu, 2019-04-18 at 20:44 +0200, Xavier Guimard wrote:
> I updated node-superagent for Buster. Now I would like to propose the
> security fix for stretch. This fixes CVE-2017-16129 (ZIP bomb
> attacks).

++if (buffer) {
++  // Protectiona against zip bombs and other nuisance

The indentation on that first line looks a bit odd, and I assume
"protectiona" is either typoed or untranslated.

Please go ahead, bearing in mind that the window for getting fixes into
 9.9 closes during this weekend.

Regards,

Adam

Bug#925401: stretch-pu: package psk31lx/2.1-1+deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Sun, 2019-03-24 at 12:46 +0100, Andreas Beckmann wrote:
> the version of the psk31lx binary package in stretch (2.1-1) is lower
> than the version in lenny (2.1+2.2beta1-8) which was built from
> src:twpsk. Buster is fine with 2.2-1.
> There was no psk31lx package in squeeze, wheezy or jessie.
> 
> Let's tune the version of the binary package to be
> 2.1+2.2really2.1-1+deb9u1 which nicely sorts between lenny and buster
> and makes upgrades of grown systems work as intended.

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

Regards,

Adam

Bug#927191: stretch-pu: package python-django-casclient/1.2.0-2

[Adam D. Barratt]

Control: tags -1 + confirmed

On Tue, 2019-04-16 at 00:13 -0400, William Blough wrote:
> Hi.  I would like to update python-django-casclient in the next
> stable point release.
> 
> Per [1], the version currently in Stretch is not functional due to
> middleware API changes in Django 1.10 and above.  Unfortunately, this
> breakage went unnoticed prior to the release of Stretch.
> 

That does make me wonder if anyone actually uses the package... :-|

Please go ahead, bearing in mind that the window for getting fixes in
to the 9.9 point release closes during this weekend.

Regards,

Adam

Bug#922930: stretch-pu: package slurm-llnl/16.05.9-1+deb9u2

[Adam D. Barratt]

Control: tags -1 + confirmed

On Thu, 2019-02-21 at 22:56 +0100, Gennaro Oliva wrote:
> I'd like to update slurm-llnl in the next stable point release to
> fix a security vulnerability (CVE-2019-6438) on 32-bit systems that
> would potentially allow heap-overflow.
> 

Sorry for not getting back to you sooner.

Please go ahead, bearing in mind that the window for getting fixes in
to the 9.9 point release closes over this weekend.

Regards,

Adam

Bug#927094: Additional Reports: Intel iGPU resume blank, LVM, ALPM.

[hoxp18]

Dear maintainers,

I confirmed this thread is alive, by sending my report just before.

Here's some more.

About Video Issue
=

* Bug#927324: I also reported there. sorry for the dup.

* Reproduction is unstable; sometimes it works. sometimes it fails.

  There are "I2C i2c-1: sendbytes: NAK bailout" log
  on the syslog during the blank issue,
  But I have no idea about it.

ALPM, LVM, data-loss


* At least "debsums -s" does not claim anything wrong.

* process "lvm" does not claim anything particular.
  process "lvm2-activation-generator" says,
  "lvmconfig failed" and "Activation generator failed".

  This Buster upgrade from Stretch machine is almost
  same configurations with my main Stretch machine.
  LVM-over-LUKS, separated mount points, on single NVMe.

Sorry for messy verbose reports.

Regards.

Bug#924569: kopano-server: SysV init scripts use wrong pid files

[Richard Lucassen]

On Sat, 20 Apr 2019 08:10:02 +0200
Carsten Schoenert  wrote:

> > Workaround is to set PIDFILE:
> > 
> > PIDFILE=/var/run/kopano/server.pid
> 
> good catch. Thanks. Remarked for one of the next uploads.
> 
> > Other SysV instances of kopano-* suffer from this issue as well.
> 
> Could you please elaborate this a bit more?

Well, quite simple: all other /etc/init.d/kopano-* init scripts have a
wrong PIDFILE= path.

At the moment I have no kopano server running here.

R.

-- 
___
It is better to remain silent and be thought a fool, than to speak
aloud and remove all doubt.

+--+
| Richard Lucassen, Utrecht|
+--+

Bug#927165: debian-installer: improve support for LUKS

[Guilhem Moulin]

Hi kibi,

On Mon, 15 Apr 2019 at 23:24:19 +0200, Cyril Brulebois wrote:
> I'm also immensely grateful for all the security-related work Matthew
> Garrett puts everywhere he goes, but I'm not sure that MR qualifies as
> “requested by d-i [0]” as you mentioned in [2].

Just to state that publicly: now that you point that out, I agree with
you and I'm unsure how I convinced myself otherwise through 2018.  The
only other related message I found is your ack of the libcryptsetup
transition [0], which doesn't count either.  I might have wrongly
assumed that someone involved in the early discussion was a member of
d-i, I dunno.  Anyway in this new light the communication was indeed on
the weak side from our (cryptsetup packaging team) side, apologies for
the late rush and extra work.

Cheers,
-- 
Guilhem.

[0] https://lists.debian.org/debian-boot/2017/12/msg00231.html


signature.asc
Description: PGP signature

Bug#927094: Additional reports; especially LVM and ALPM issues.

[hoxp18]

Dear maintainers,

Fortunately, this thread seems still alive.

So I send this report.

Video
=

* Removed GeForce 1030, now Intel CORE iGPU -> HDMI.
  It's fine.

* Intel iGPU resume display blank, still. tty switching solve it.

LVM
===

* LVM error messages still left; on cold boot, on apt upgrade.

Firefox
===

* Mozilla Firefox ESR boot up seems a bit slow;
  2~3 secs of right-bottom area blank, then it displays fine.

  It seems no problem on browsing, with Squid proxy on
  the other machine.


ALPM


* I have no idea how I could test potential data-loss due to
  enabling ALPM on BIOS.

  I guess it works fine, since this LVM-over-LUKS system
  keep running for a week with multiple upgrades,
  with suspend-to-RAM, cold boots.

  However, I am not sure since the LVM error messages kept.
  I also simply not sure because I did not test something
  properly.

Thank you for reading this.

Regards.

Bug#924569: kopano-server: SysV init scripts use wrong pid files

[Carsten Schoenert]

Hi,

please use 'Reply All' so the BTS is getting the information as well.

Am 20.04.19 um 10:46 schrieb Richard Lucassen:
> On Sat, 20 Apr 2019 08:10:02 +0200
> Carsten Schoenert  wrote:
> 
>>> Workaround is to set PIDFILE:
>>>
>>> PIDFILE=/var/run/kopano/server.pid
>>
>> good catch. Thanks. Remarked for one of the next uploads.
>>
>>> Other SysV instances of kopano-* suffer from this issue as well.
>>
>> Could you please elaborate this a bit more?
> 
> Well, quite simple: all other /etc/init.d/kopano-* init scripts have a
> wrong PIDFILE= path.
> 
> At the moment I have no kopano server running here.

It's not that simple.
I don't know at what time Kopano has changed here anything but the old
style was to use a full name of the service to mark the PID file.

kopano-server
kopano-search
...

If I read your previous email correctly the PIF files are now living in
/var/run/kopano/

As I normally don't use SysV scripts anymore and also don't do any
testing of the Kopano packages in this regard and I'm not sure what the
correct naming now is.
I guess the new behavior is dropping the prefix name 'kopano' and only
use the service name as PID file name within /var/run/kopano/. But
without some verification it's not clear what we need to adjust in the
packaging. If someone will come up with a validated checking I'm happy
to adjust this into the packaging.

-- 
Regards
Carsten Schoenert

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

[Adam D. Barratt]

On Tue, 2019-04-16 at 19:37 +0200, Gilles Filippini wrote:
> Adam D. Barratt a écrit le 14/04/2019 à 22:48 :
> > Control: tags -1 + confirmed
> > 
> > On Fri, 2019-02-22 at 17:29 +0100, Gilles Filippini wrote:
> > > Because RC bug #922453 affects Stretch as well, I propose a
> > > stable
> > > update
> > > for cernlib. Debdiff attached.
> > 
> > cernlib (20061220+dfsg3-4.3+deb9u1) stable-proposed-updates;
> > urgency=medium
> > 
> > Please use "stretch" rather than "stable-proposed-updates" and go
> > ahead.
> 
> Done.

Unfortunately, the arm64 build appears to be hitting #863152 in
binutils. I'm not sure if there's anything that can be done to work
around this in cernlib, but noting it here in any case, as it means
that cernlib won't be getting into 9.9.

Regards,

Adam

Bug#924040: ITP: archivebox -- open source self-hosted web archive

[W. Martin Borgert]

On 2019-03-08 13:39, Antoine Beaupre wrote:
> There are, as far as I know, no similar tool in Debian right
> now. There are web crawlers and grabbers, but nothing as comprehensive
> as this.

Many people use xul-ext-scrapbook, but this means, they are
stuck with firefox 52.9.0esr-1. I proposed packaging
webext-scrapbookq (#898545), but TBH it does not seem to be an
adequate replacement. At first sight, archivebox looks better.

> I'd be happy to co-maintain this or delegate to whoever is interested.

I'm willing to help under the PAPT (or other team) umbrella.

Bug#927091:

[Marcelo Terres]

Hello.

This is happening on Ubuntu 19.04 using kernel 5.0 (package 5.0.0-13.14).

Maybe something related with Kernel not with Debian and/or Ubuntu.

Regards,

Marcelo H. Terres 
https://www.mundoopensource.com.br
https://twitter.com/mhterres
https://linkedin.com/in/marceloterres

Bug#927457: ITP: fluxbox -- low resource X11 Window manager

[Tobias Frost]

Hi Tong,

On Fri, Apr 19, 2019 at 11:53:54PM -0400, Tong Sun wrote:
> 
> * Package name: fluxbox

> Reason to pack: to salvage the package, because

when you want to salvage the package, you should follow the ITS
procedure and not filing an ITP bug.

(ITS procedure is documented here:)
https://wiki.debian.org/PackageSalvaging and
https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#package-salvaging

Cheers,
tobi

Bug#927467: dput-ng: FTBFS (failing tests)

[Santiago Vila]

Package: src:dput-ng
Version: 1.24
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules binary-indep
dh binary-indep --with bash-completion,python3,sphinxdoc --buildsystem pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python3.7 setup.py config 
running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
I: pybuild base:217: /usr/bin/python3 setup.py build 
running build
running build_py
creating /<>/.pybuild/cpython3_3.7_dput/build/dput
copying dput/command.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput
copying dput/config.py -> /<>/.pybuild/cpython3_3.7_dput/build/dput
copying dput/core.py -> /<>/.pybuild/cpython3_3.7_dput/build/dput
copying dput/interface.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput
copying dput/uploader.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput
copying dput/__init__.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput
copying dput/logger.py -> /<>/.pybuild/cpython3_3.7_dput/build/dput
copying dput/changes.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput
copying dput/exceptions.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput
copying dput/util.py -> /<>/.pybuild/cpython3_3.7_dput/build/dput
copying dput/hook.py -> /<>/.pybuild/cpython3_3.7_dput/build/dput
copying dput/dsc.py -> /<>/.pybuild/cpython3_3.7_dput/build/dput
copying dput/profile.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput
copying dput/overrides.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput
creating /<>/.pybuild/cpython3_3.7_dput/build/dput/hooks
copying dput/hooks/impatient.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput/hooks
copying dput/hooks/distro_info_checks.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput/hooks
copying dput/hooks/checksum.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput/hooks
copying dput/hooks/deb.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput/hooks
copying dput/hooks/lintian.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput/hooks
copying dput/hooks/__init__.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput/hooks
copying dput/hooks/gpg.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput/hooks
copying dput/hooks/distribution.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput/hooks
creating /<>/.pybuild/cpython3_3.7_dput/build/dput/configs
copying dput/configs/dputng.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput/configs
copying dput/configs/__init__.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput/configs
copying dput/configs/dputcf.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput/configs
creating /<>/.pybuild/cpython3_3.7_dput/build/dput/commands
copying dput/commands/cancel.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput/commands
copying dput/commands/reschedule.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput/commands
copying dput/commands/__init__.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput/commands
copying dput/commands/dm.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput/commands
copying dput/commands/rm.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput/commands
copying dput/commands/breakthearchive.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput/commands
copying dput/commands/upload.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput/commands
creating /<>/.pybuild/cpython3_3.7_dput/build/dput/commands/contrib
copying dput/commands/contrib/debomatic.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput/commands/contrib
copying dput/commands/contrib/__init__.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput/commands/contrib
creating /<>/.pybuild/cpython3_3.7_dput/build/dput/uploaders
copying dput/uploaders/secure_sftp.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput/uploaders
copying dput/uploaders/local.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput/uploaders
copying dput/uploaders/__init__.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput/uploaders
copying dput/uploaders/http.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput/uploaders
copying dput/uploaders/sftp.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput/uploaders
copying dput/uploaders/scp.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput/uploaders
copying dput/uploaders/ftp.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput/uploaders
creating /<>/.pybuild/cpython3_3.7_dput/build/dput/interfaces
copying dput/interfaces/__init__.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput/interfaces
copying dput/interfaces/cli.py -> 
/<>/.pybuild/cpython3_3.7_dput/build/dput/interfaces
make -C docs html
make[2]: Entering directory '/<>/docs'
sphinx-build -b html -W -d _build/doctrees   . _build/html
Running Sphinx v1.8.4
making output directory...
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 36 source files that are out of date
updating environment: 36 added, 0 changed, 0 removed

Bug#923675: debian-installer: consider using haveged to gather entropy

[Holger Levsen]

On Sat, Apr 20, 2019 at 02:39:49AM +0200, Cyril Brulebois wrote:
> I've tweaked it a little so that we log whether haveged is available,
> and whether it should be started, in case we need to investigate:
>   
> https://salsa.debian.org/installer-team/rootskel/blob/master/src/lib/debian-installer-startup.d/S50entropy-source

nice work!

does that also mean that haveged get's installed on the final system if
it's deemed to be useful in d-i or is that still missing?


-- 
tschau,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C


signature.asc
Description: PGP signature

Bug#927434: unblock: network-manager-applet/1.8.20-1.1 (pre-approval)

[Michael Biebl]

Hi
Am 19.04.19 um 19:56 schrieb Boyuan Yang:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> X-Debbugs-CC: bi...@debian.org pkg-utopia-maintain...@lists.alioth.debian.org
> 
> This is a pre-approval for NMU that would fix https://bugs.debian.org/926328 .
> 
> The one-liner patch is taken from commits in upstream git trunk.
> 
> I haven't make any upload yet. Michael, please let me know if this
> patch looks okay for you. I can open a Merge Request for this NMU on
> Salsa if necessary.


Looks fine to me, thanks.
A MR would be great.

Regards,
Michael

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



signature.asc
Description: OpenPGP digital signature

Bug#927465: Unable to save to database mariadb

[Mechtilde]

Package: gnucash
Version: 1:3.4-1+b10
Severity: important
Tags: upstream

Since the update to version 3.4 I am unable to use gnucash with mariadb
as the backend. It isn't possible anymore to save a transaction with the 
corresponding account others than "Imbalance"

I also fill a bugreport to upstream. 

https://bugs.gnucash.org/show_bug.cgi?id=797121

Regards
Mechtilde


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

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

Versions of packages gnucash depends on:
ii  gnucash-common   1:3.4-1
ii  guile-2.22.2.4+1-1
ii  guile-2.2-libs   2.2.4+1-1
ii  libaqbanking35   5.7.8-3
ii  libaqbanking35-plugins   5.7.8-3
ii  libatk1.0-0  2.30.0-2
ii  libboost-date-time1.67.0 1.67.0-13
ii  libboost-filesystem1.67.01.67.0-13
ii  libboost-locale1.67.01.67.0-13
ii  libboost-regex1.67.0 1.67.0-13
ii  libboost-system1.67.01.67.0-13
ii  libc62.28-8
ii  libcairo-gobject21.16.0-4
ii  libcairo21.16.0-4
ii  libcrypt-ssleay-perl 0.73.06-1+b1
ii  libdate-manip-perl   6.76-1
ii  libdbi1  0.9.0-5
ii  libfinance-quote-perl1.47-1
ii  libgc1c2 1:7.6.4-0.4
ii  libgcc1  1:8.3.0-6
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libglib2.0-0 2.58.3-1
ii  libgtk-3-0   3.24.5-1
ii  libgwenhywfar60  4.20.0-9
ii  libhtml-tableextract-perl2.15-1
ii  libhtml-tree-perl5.07-2
ii  libicu63 63.1-6
ii  libjavascriptcoregtk-4.0-18  2.24.1-1
ii  libktoblzcheck1v51.49-5
ii  libofx7  1:0.9.14-1
ii  libpango-1.0-0   1.42.4-6
ii  libpangocairo-1.0-0  1.42.4-6
ii  libpython3.7 3.7.3~rc1-1
ii  libsecret-1-00.18.7-1
ii  libsoup2.4-1 2.64.2-2
ii  libstdc++6   8.3.0-6
ii  libwebkit2gtk-4.0-37 2.24.1-1
ii  libwww-perl  6.36-1
ii  libxml2  2.9.4+dfsg1-7+b3
ii  libxslt1.1   1.1.32-2
ii  perl 5.28.1-6
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages gnucash recommends:
ii  gnucash-docs 3.4-1
ii  python3-gnucash  1:3.4-1+b10
ii  yelp 3.31.90-1

Versions of packages gnucash suggests:
ii  libdbd-mysql0.9.0-6+b1
pn  libdbd-pgsql
pn  libdbd-sqlite3  

-- no debconf information

Bug#927450: base-files: breaks debian-security-support, which then breaks package installations

[Santiago Vila]

reassign 927450 debian-security-support
retitle 927450 debian-security-support should know that the next stable is 
Debian 10
affects 927450 base-files
thanks

On Sat, Apr 20, 2019 at 04:01:05AM +0200, Christoph Anton Mitterer wrote:
> Yeah it's definitely that strange hardcoded part in:
> /usr/bin/check-support-status:
> 
> > DEB_LOWEST_VER_ID=7
> > # Version ID for next Debian stable
> > DEB_NEXT_VER_ID=9

This is clearly wrong and not a bug in base-files. The next Debian
stable is Debian 10.

> > …
> > if [ "$DEBIAN_VERSION" -lt "$DEB_LOWEST_VER_ID" ] || [ "$DEBIAN_VERSION" 
> > -gt "$DEB_NEXT_VER_ID" ] ; then
> > eval_gettext "Unknown DEBIAN_VERSION \$DEBIAN_VERSION. Valid values 
> > from \$DEB_LOWEST_VER_ID and \$DEB_NEXT_VER_ID"; echo
> > exit 1
> > fi
> 
> if one makes something like this one should have probably declared a
> Conflicts against any base-files package >9.
> 
> 
> Not sure what the correct is to handle this in the BTS... of course it
> should be assigned to debian-security-support,

Done with this message.

> but then people who
> upgrade won't notice the problem... "affects base-files" isn't the case
> and wouldn't probably make it show up either.

I'm adding "affect base-files" so that people see this bug in the BTS
page for base-files and nobody thinks the problem is in base-files,
but just for that.

> Guess the only thing the BTS allows is to have a 2nd bug at debian-
> security-support and make this one a dummy-bug (which also block
> transition to testing) blocked by the other.

No need, this bug is enough once reassigned.

Thanks a lot for the report.

Bug#927464: unblock: sbsigntool/0.9.2-2

[Steve McIntyre]

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

Please unblock package sbsigntool

I've fixed a bug that I *would* have filed as RC, if I hadn't just
fixed it. :-) Patch sent upstream for a subtle bug breaking checksum
calculation in the PE/COFF binaries that are used for UEFI Secure
Boot.

This package is needed as part of the build process for our
shim-signed packages.

debdiff:

diff -Nru sbsigntool-0.9.2/debian/changelog sbsigntool-0.9.2/debian/changelog
--- sbsigntool-0.9.2/debian/changelog   2019-01-21 20:20:40.0 +
+++ sbsigntool-0.9.2/debian/changelog   2019-04-19 22:41:15.0 +0100
@@ -1,3 +1,13 @@
+sbsigntool (0.9.2-2) unstable; urgency=medium
+
+  * Change Maintainer to be the EFI team, with Pierre and me as Uploaders
+  * Remove the old alignment patch, looks to be un-needed now
+  * Fix PE/COFF checksum calculation - only count the cert_table
+struct once when performing the calculation and counting buffer
+sizes.
+
+ -- Steve McIntyre <93...@debian.org>  Fri, 19 Apr 2019 23:41:15 +0200
+
 sbsigntool (0.9.2-1) unstable; urgency=medium
 
   * Add watch file
diff -Nru sbsigntool-0.9.2/debian/control sbsigntool-0.9.2/debian/control
--- sbsigntool-0.9.2/debian/control 2019-01-21 20:16:08.0 +
+++ sbsigntool-0.9.2/debian/control 2019-04-19 15:54:34.0 +0100
@@ -1,7 +1,9 @@
 Source: sbsigntool
 Section: utils
 Priority: optional
-Maintainer: Pierre Chifflier 
+Maintainer: Debian EFI Team 
+Uploaders: Pierre Chifflier ,
+  Steve McIntyre <93...@debian.org>
 Build-Depends: debhelper (>= 9.0.0),
   dh-autoreconf,
   gcc-multilib [amd64 i386 kfreebsd-amd64],
diff -Nru sbsigntool-0.9.2/debian/patches/Align-signature-data-to-8-bytes.patch 
sbsigntool-0.9.2/debian/patches/Align-signature-data-to-8-bytes.patch
--- sbsigntool-0.9.2/debian/patches/Align-signature-data-to-8-bytes.patch   
2019-01-21 19:59:31.0 +
+++ sbsigntool-0.9.2/debian/patches/Align-signature-data-to-8-bytes.patch   
1970-01-01 01:00:00.0 +0100
@@ -1,26 +0,0 @@
-From 8b6b7a9904881757254b92a928b95dfb8634605b Mon Sep 17 00:00:00 2001
-From: Steve Langasek 
-Date: Fri, 12 Oct 2012 16:27:13 -0700
-Subject: [PATCH] Align signature data to 8 bytes
-
-Before appending the signature data to our binary, pad the file out to
-8-byte alignment.  This matches the Microsoft signing implementation, which
-enables us to use sbattach to verify the integrity of the binaries returned
-by the SysDev signing service.

- src/image.c | 2 ++
- 1 file changed, 2 insertions(+)
-
-Index: sbsigntool/src/image.c
-===
 sbsigntool.orig/src/image.c
-+++ sbsigntool/src/image.c
-@@ -495,6 +495,8 @@ reparse:
-* we've calculated during the pecoff parsing, so we need to redo that
-* too.
-*/
-+  image->data_size = align_up(image->data_size, 8);
-+
-   if (image->data_size > image->size) {
-   image->buf = talloc_realloc(image, image->buf, uint8_t,
-   image->data_size);
diff -Nru sbsigntool-0.9.2/debian/patches/fix_checksum_calc.patch 
sbsigntool-0.9.2/debian/patches/fix_checksum_calc.patch
--- sbsigntool-0.9.2/debian/patches/fix_checksum_calc.patch 1970-01-01 
01:00:00.0 +0100
+++ sbsigntool-0.9.2/debian/patches/fix_checksum_calc.patch 2019-04-19 
22:41:15.0 +0100
@@ -0,0 +1,37 @@
+Author: Steve McIntyre <93...@debian.org>
+Date: Fri, 19 Jun 2019 23:35:44 +0200
+Description: Fix PE/COFF checksum calculation
+ Upstream reconfigured the code to allow for multiple checksums to be
+ included on a binary, but mis-handled the change to buffer and
+ checksum handling such that the cert_table header was now being
+ counted twice. Fix that.
+diff --git a/src/image.c b/src/image.c
+index 745191f..3ada37b 100644
+--- a/src/image.c
 b/src/image.c
+@@ -162,7 +162,6 @@ static void image_pecoff_update_checksum(struct image 
*image)
+ {
+   bool is_signed = image->sigsize && image->sigbuf;
+   uint32_t checksum;
+-  struct cert_table_header *cert_table = image->cert_table;
+ 
+   /* We carefully only include the signature data in the checksum (and
+* in the file length) if we're outputting the signature.  Otherwise,
+@@ -180,16 +179,13 @@ static void image_pecoff_update_checksum(struct image 
*image)
+   (void *)(image->checksum + 1));
+ 
+   if (is_signed) {
+-  checksum = csum_bytes(checksum,
+-  cert_table, sizeof(*cert_table));
+-
+   checksum = csum_bytes(checksum, image->sigbuf, image->sigsize);
+   }
+ 
+   checksum += image->data_size;
+ 
+   if (is_signed)
+-  checksum += sizeof(*cert_table) + image->sigsize;
++  checksum += image->sigsize;
+ 
+   *(image->checksum) = cpu_to_le32(checksum);
+ }
diff -Nru 

Bug#852241: beets fails to move album when modifying artist

[Carl Suster]

Is this an issue you still observe in the latest version of beets?

This is pretty difficult to help with without having more details. The 
verbose log output of beets for the relevant command, and the full 
configuration file would be a good start.

Bug#687849: beets: silently fails to rewrite tags

[Carl Suster]

This bug is pretty much impossible to investigate without having more 
information, such as the actual files that exhibit the issue, verbose 
output from beets, the output of `beet info` for the relevant files, etc..


I think this should be closed. If it can be reproduced on a modern 
version of beets with more details then that can be a new bug report, 
but in any case it's probably better off being reported upstream.

Bug#926514: brltty: FTBFS on ia64 because the link check doesn't account for libunwind

[John Paul Adrian Glaubitz]

Hi Samuel!

On 4/7/19 12:15 AM, Samuel Thibault wrote:
>> # Check that we didn't accidentally link against something outside of
>> # d-i world
>> grep Depends: debian/brltty-udeb/DEBIAN/control | perl -ne 'map {unless 
>> (/-udeb/ or /^ ?preseed-common$/) {print $_; exit 1}} split /,/'
>>  libunwind8make: *** [debian/rules:257: brltty-udeb] Error 1
>> dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess 
>> returned exit status 2
>>
>> Adding a "or /libunwind.*/" should be able to fix the problem though. Will 
>> test
>> later and attach a tested patch.
> 
> Err, but is the libunwind8 package really available in the d-i image?
> AIUI we'd need a udeb for it, not just ignore the issue.

You are right and sorry for the late response. Indeed, d-i build is asking
for a libunwind-udeb now after I made this change.

I will send in a patch for src:libunwind to create a udeb, although I'm a bit
surprised that we haven't run into this problem before with other d-i 
components.

Adrian

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

Bug#927429: ghostscript: incorrect bbox is produced in pdfcrop

[Jonas Smedegaard]

control: forwarded -1 https://bugs.ghostscript.com/show_bug.cgi?id=700988

Quoting Kenshi Muto (2019-04-20 00:32:33)
> On Sat, 20 Apr 2019 01:18:50 +0900,
> Jonas Smedegaard wrote:
> > Can you pass this upstream?  Otherwise I will do that.
> 
> Well, it's hard for me to follow upstream discussion...
> I'd like to ask you to send, I really appreciate it :)

Perfectly fine - I've passed it upstream now. :-)

Thanks again for reporting this,

 - Jonas

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

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


signature.asc
Description: signature

Bug#925379: linux-base: linux-version vmlinuz/vmlinux dichotomy, breaks at least m68k

[John Paul Adrian Glaubitz]

Hi!

On 4/17/19 10:48 PM, Ben Hutchings wrote:
>> Just as a heads-up: I'm going to switch sparc and sparc64 over to an
>> uncompressed kernel as well since compressed kernels are not
>> officially
>> supported and actually don't work with GRUB 2.04~rc1 when I tested
>> on sparc64 [1].
> 
> It might be worth adding a versioned dependency on linux-base for the
> affected architectures.

Sure. I'm just waiting for the Buster release now before I'll be pushing
changes to debian-installer and components and sending merge requests
for src:linux and src:linux-base. I have already accumulated a couple
of patches.

Adrian

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

Bug#927434: unblock: network-manager-applet/1.8.20-1.1 (pre-approval)

[Niels Thykier]

Control: tags -1 confirmed moreinfo

Boyuan Yang:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> X-Debbugs-CC: bi...@debian.org pkg-utopia-maintain...@lists.alioth.debian.org
> 
> This is a pre-approval for NMU that would fix https://bugs.debian.org/926328 .
> 
> The one-liner patch is taken from commits in upstream git trunk.
> 
> I haven't make any upload yet. Michael, please let me know if this
> patch looks okay for you. I can open a Merge Request for this NMU on
> Salsa if necessary.
> 
> The full debdiff is pasted here.
> 
> --
> Thanks,
> Boyuan Yang
> 
> [...]
> 

Hi,

>From a release team PoV, the change looks fine.

Please remove the moreinfo tag when the upload is in sid and ready to be
unblocked.

Thanks,
~Niels

Bug#924569: kopano-server: SysV init scripts use wrong pid files

[Carsten Schoenert]

Hello Richard,

Am 14.03.19 um 14:08 schrieb Richard Lucassen:
> Package: kopano-server
> Version: 8.7.0-2
> Severity: normal
> 
> Dear Maintainer,
> 
> Running e.g. "service kopano-server stop" results in:
> 
> [] Stopping Kopano server: kopano-server
> No /usr/sbin/kopano-server found running; none killed.
> failed!
> 
> The PIDFILE variable in "/etc/init.d/kopano-server":
> 
> PIDFILE=/var/run/$NAME.pid
> 
> (where NAME=`basename /usr/sbin/kopano-server`)
> 
> does not correspond to the real pid file:
> 
> /var/run/kopano/server.pid
> 
> Workaround is to set PIDFILE:
> 
> PIDFILE=/var/run/kopano/server.pid

good catch. Thanks. Remarked for one of the next uploads.

> Other SysV instances of kopano-* suffer from this issue as well.

Could you please elaborate this a bit more?
It would be helpful if you can provide the needed changes to the other
SysV init scripts somehow. We have the following other init scripts
within the packaging.

> ./kopano-monitor.init
> ./kopano-ical.init
> ./kopano-presence.init
> ./kopano-search.init
> ./kopano-dagent.init
> ./kopano-spooler.init
> ./kopano-server.init
> ./kopano-gateway.init
> ./kopano-spamd.init

Thanks!

-- 
Regards
Carsten Schoenert

Bug#927462: megadown: Does not download anything

[jim_p]

Package: megadown
Version: 0~20180705+git83c53dd-1
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

When trying to download a file from mega, which is the sole reason this script
exists, megadown fails like so

$ megadown
'https://mega.nz/#!3QsG0IDJ!wnEhMRAj1UsXvH3BmWKfr5Z4wqMD2c5ru4iWgFzJmO0'
   Reading link metadata...
MEGA bad link

I reported the issue to the project's github page, because it happened with
other mega links as well, and its dev issued a patch that restores the intended
functionality, here

https://github.com/tonikelope/megadown/commit/734e46fec67a2798bfbb5e21a75f04b90afafd65

So please update the package on the repo, which by the way is numerous minor
versions behind.



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

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

Versions of packages megadown depends on:
ii  bash 5.0-3
ii  curl 7.64.0-2
ii  openssl  1.1.1b-1
ii  pv   1.6.6-1
ii  python3  3.7.2-1
ii  wget 1.20.1-1

megadown recommends no packages.

megadown suggests no packages.

-- no debconf information