Bug#921555: unblock: ciftilib/1.5.3-2
Hi, I'm very sorry to not have checked that the upload included an upstream version bump before sponsering the package. Ghislain, can you please prepare a package that fits freeze policy? I'm fine with uploading version 1.5.3 to experimental if that might help. Kind regards Andreas. On Thu, Apr 04, 2019 at 09:23:48PM +0200, Ivo De Decker wrote: > Control: tags -1 moreinfo > > Hi Andreas, > > On Wed, Apr 03, 2019 at 08:40:59AM +0200, Andreas Tille wrote: > > Please unblock package ciftilib > > You included the diff between 1.5.3-1 and 1.5.3-2. However, testing currently > has 1.5.1-3. The diff beween 1.5.1-3 and 1.5.3-2 is much bigger, and doesn't > look like something that is acceptable during the freeze. > > Version 1.5.3-1 didn't migrate due to the missing builds (which are fixed by > the patch in -2). > > Ivo > > -- http://fam-tille.de
Bug#892070: obs-build 20160921-1+deb9u1 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: obs-build Version: 20160921-1+deb9u1 Explanation: do not allow writing to files in the host system [CVE-2017-14804]
Bug#910805: dnsruby 1.54-2+deb9u1 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: dnsruby Version: 1.54-2+deb9u1 Explanation: add new root key (KSK-2017); ruby 2.3.0 deprecates TimeoutError, use Timeout::Error
Bug#925351: dns-root-data 2019031302~deb9u1 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: dns-root-data Version: 2019031302~deb9u1 Explanation: update root data to 2019031302
Bug#924945: edk2 0~20161202.7bbe0b3e-1+deb9u1 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: edk2 Version: 0~20161202.7bbe0b3e-1+deb9u1 Explanation: fix buffer overflow in BlockIo service [CVE-2018-12180]; DNS: Check received packet size before using [CVE-2018-12178]; fix stack overflow with corrupted BMP [CVE-2018-12181]
Bug#926432: apache2: Internal error: error fetching from cache 'dbm:/var/cache/apache2/gnutls_cache'
Le 03/04/2019 à 14:40, Damir R. Islamov a écrit : > Package: apache2 > Version: 2.4.38-2 > Severity: normal > > Dear Maintainer, > > After update to aapche 2.4.38-1 /var/log/apache2/error.log has a lot of > errors like > > [gnutls:warn] [pid 6466:tid 140230002730752] (20014)Internal error (specific > information not available): error fetching from cache > 'dbm:/var/cache/apache2/gnutls_cache' > > One string per virtual host, every 10 minutes. Hello, could you try with apache-2.4.39 (https://people.debian.org/~yadd/apache/) ? It seems that this has been fixed. Cheers, Xavier
Bug#915103: Apache2 HTTP/2 connection problems with Safari clients
Looks like this is fixed in 2.4.25-3+deb9u7. Safari is not dropping http2 requests any more. > This update also contains bug fixes that were scheduled for inclusion in the > next stable point release. This includes a fix for a regression caused by a > security fix in version 2.4.25-3+deb9u6. https://www.debian.org/security/2019/dsa-4422
Bug#924397: corekeeper: insecure use of world-writable /var/crash
On Thu, 21 Mar 2019 10:17:30 +0800 Paul Wise wrote: > Do you have any suggestions for how to deal with the postinst > permissions update? I'm guessing it should just update the permissions > on upgrade between the two versions and not if a statoverride is set? I've done that in the attached patch. -- bye, pabs https://wiki.debian.org/PaulWise From e950969719df3e796cc9b5e9dc5c7bbf4bf26a51 Mon Sep 17 00:00:00 2001 From: Paul Wise Date: Wed, 13 Mar 2019 14:10:36 +0800 Subject: [PATCH 01/16] Do not use a world-writable /var/crash with the dumper script Suggested-by: lintian Fixes: https://bugs.debian.org/924397 See-also: https://bugs.debian.org/515211 Reported-by: Jakub Wilk Reported-in: <20190312145027.7npetzqs3hwlk...@jwilk.net> --- debian/changelog| 8 debian/corekeeper.lintian-overrides | 2 +- debian/corekeeper.postinst.linux| 7 +++ debian/rules| 2 +- debian/sysctl-linux/corekeeper.conf | 5 - 5 files changed, 21 insertions(+), 3 deletions(-) diff --git a/debian/changelog b/debian/changelog index 43ec51f..20d7bb1 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +corekeeper (1.7) UNRELEASED; urgency=medium + + * Do not use a world-writable /var/crash with the dumper script +and fix the permissions on upgrade as dpkg doesn't do that. +(Closes: #924397) (See-also: #515211) + + -- Paul Wise Wed, 13 Mar 2019 14:09:50 +0800 + corekeeper (1.6) unstable; urgency=medium * Prevent installation with other core dump handlers: diff --git a/debian/corekeeper.lintian-overrides b/debian/corekeeper.lintian-overrides index 1e248d9..955d7e6 100644 --- a/debian/corekeeper.lintian-overrides +++ b/debian/corekeeper.lintian-overrides @@ -1,6 +1,6 @@ # /var/crash is intentionally world-writable to allow for # centralized core dumps. -non-standard-dir-perm +[kfreebsd-any]: non-standard-dir-perm # The postrm script checks if systemd is running before # using the systemctl command diff --git a/debian/corekeeper.postinst.linux b/debian/corekeeper.postinst.linux index a345931..2f56a92 100644 --- a/debian/corekeeper.postinst.linux +++ b/debian/corekeeper.postinst.linux @@ -4,4 +4,11 @@ set -e # Activate the sysctl settings [ $1 != configure ] || sysctl --quiet --load="/etc/sysctl.d/corekeeper.conf" +# Set /var/crash to not be world writable +# to prevent crashes being able to write arbitrary files +[ "$1" = configure ] && +dpkg --compare-versions "$2" le-nl 1.6 && +! dpkg-statoverride --list /var/crash && +chmod 0755 /var/crash + #DEBHELPER# diff --git a/debian/rules b/debian/rules index a44b38b..6d52c95 100755 --- a/debian/rules +++ b/debian/rules @@ -10,7 +10,7 @@ script=debian/corekeeper/usr/lib/corekeeper/dump override_dh_fixperms: dh_fixperms - chmod 1777 debian/corekeeper/var/crash + if [ ! -e $(script) ] ; then chmod 1777 debian/corekeeper/var/crash ; fi if [ -e $(script) ] ; then chmod 0755 $(script) ; fi override_dh_installinit: diff --git a/debian/sysctl-linux/corekeeper.conf b/debian/sysctl-linux/corekeeper.conf index e6fcb90..66bebb4 100644 --- a/debian/sysctl-linux/corekeeper.conf +++ b/debian/sysctl-linux/corekeeper.conf @@ -4,8 +4,11 @@ # Non-root users can see that something crashed, no way to fix that. # It requires Linux 3.7-rc1, see v3.6-6800-g12a2b4b in linux.git for info. # If you use it with an earlier kernel then only root can access core dumps. -# If you don't want to use it, comment core_pattern below and uncomment this: +# If you don't want to use it, comment core_pattern below, dpkg-statoverride +# /var/crash to mode 1777 and uncomment this alternate core_pattern: #kernel.core_pattern = /var/crash/%p-%u-%g-%s-%t-%h-%E.core +# When switching back to the default core pattern use mode 0755 for /var/crash +# as it is unsafe to use the dumper with a world-writable directory. kernel.core_pattern = |/usr/lib/corekeeper/dump %d %u %p-%u-%g-%s-%t-%h-%E.core kernel.core_uses_pid = 1 fs.suid_dumpable = 2 -- 2.20.1 signature.asc Description: This is a digitally signed message part
Bug#926297: duplicity: azure dependency broken?
tags 926297 + upstream forwarded 926297 https://bugs.launchpad.net/duplicity/+bug/1694770 thanks On Wed, 03 Apr 2019 14:27:31 +1100, Dean Hamstead writes: >Similarly, if i do a 'pip install azure' i get the same error. that's an api incompatibility problem known to upstream (see the launchpad tracker link above). a comment on that bug report indicates that forcing the installation of an older azure api version with pip install azure-storage==0.20.0 should provide a workaround for now (you may also have to ditch the python-azure-storage debian package). regards az -- Alexander Zangerl + GPG Key 2FCCF66BB963BD5F + http://snafu.priv.at/ AA - American Association Against Acronym Abuse Anonymous. signature.asc Description: Digital Signature
Bug#926432: apache2: Internal error: error fetching from cache 'dbm:/var/cache/apache2/gnutls_cache'
Package: apache2 Version: 2.4.38-2 Severity: normal Dear Maintainer, After update to aapche 2.4.38-1 /var/log/apache2/error.log has a lot of errors like [gnutls:warn] [pid 6466:tid 140230002730752] (20014)Internal error (specific information not available): error fetching from cache 'dbm:/var/cache/apache2/gnutls_cache' One string per virtual host, every 10 minutes. $ ls -l /var/cache/apache2/gnutls_cache -rw-r--r-- 1 www-data root 12288 апр 3 19:36 /var/cache/apache2/gnutls_cache $ file /var/cache/apache2/gnutls_cache /var/cache/apache2/gnutls_cache: Berkeley DB (Hash, version 9, native byte-order) $ db_dump /var/cache/apache2/gnutls_cache VERSION=3 format=bytevalue type=hash h_nelem=6 db_pagesize=4096 HEADER=END . DATA IS HERE . DATA=END Removing the file with the following restart does not help. Used configuration: /etc/apache2/conf-enabled/: apache2-doc.conf charset.conf javascript-common.conf jsmath.conf localized-error-pages.conf other-vhosts-access-log.conf php7.3-fpm.conf phppgadmin.conf security.conf serve-cgi-bin.conf servername.conf /etc/apache2/mods-enabled/: access_compat.load actions.conf actions.load alias.conf alias.load auth_basic.load authn_core.load authn_file.load authz_core.load authz_groupfile.load authz_host.load authz_user.load autoindex.conf autoindex.load cgi.load deflate.conf deflate.load dir.conf dir.load env.load fcgid.conf fcgid.load filter.load gnutls.conf gnutls.load headers.load include.load mime.conf mime.load mime_magic.conf mime_magic.load mpm_event.conf mpm_event.load negotiation.conf negotiation.load perl.load proxy.conf proxy_fcgi.load proxy.load reqtimeout.conf reqtimeout.load rewrite.load setenvif.conf setenvif.load socache_dbm.load socache_shmcb.load status.conf status.load substitute.load userdir.conf userdir.load xsendfile.load -- Package-specific info: -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-3-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages apache2 depends on: ii apache2-bin2.4.38-2 ii apache2-data 2.4.38-2 ii apache2-utils 2.4.38-2 ii dpkg 1.19.6 ii lsb-base 10.2019031300 ii mime-support 3.62 ii perl 5.28.1-6 ii procps 2:3.3.15-2 Versions of packages apache2 recommends: ii ssl-cert 1.0.39 Versions of packages apache2 suggests: ii apache2-doc 2.4.38-2 pn apache2-suexec-pristine | apache2-suexec-custom ii chromium [www-browser] 73.0.3683.75-1 ii elinks [www-browser] 0.13~20190125-3 ii firefox [www-browser]66.0.1-1 ii konqueror [www-browser] 4:18.12.0-1 ii links [www-browser] 2.18-1+b10 ii lynx [www-browser] 2.8.9rel.1-3 ii w3m [www-browser]0.5.3-37 Versions of packages apache2-bin depends on: ii libapr1 1.6.5-1+b1 ii libaprutil1 1.6.1-3+b2 ii libaprutil1-dbd-sqlite3 1.6.1-3+b2 ii libaprutil1-ldap 1.6.1-3+b2 ii libbrotli1 1.0.7-2 ii libc62.28-8 ii libcurl4 7.64.0-2 ii libjansson4 2.12-1 ii libldap-2.4-22.4.47+dfsg-3 ii liblua5.2-0 5.2.4-1.1+b2 ii libnghttp2-141.37.0-1 ii libpcre3 2:8.39-12 ii libssl1.11.1.1b-1 ii libxml2 2.9.4+dfsg1-7+b3 ii perl 5.28.1-6 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages apache2-bin suggests: ii apache2-doc 2.4.38-2 pn apache2-suexec-pristine | apache2-suexec-custom ii chromium [www-browser] 73.0.3683.75-1 ii elinks [www-browser] 0.13~20190125-3 ii firefox [www-browser]66.0.1-1 ii konqueror [www-browser] 4:18.12.0-1 ii links [www-browser] 2.18-1+b10 ii lynx [www-browser] 2.8.9rel.1-3 ii w3m [www-browser]0.5.3-37 Versions of packages apache2 is related to: ii apache2 2.4.38-2 ii apache2-bin 2.4.38-2 -- Configuration Files: /etc/apache2/apache2.conf changed [not included] /etc/logrotate.d/apache2 changed [not included] -- no debconf information
Bug#926433: apache2: Invalid HTTP request to ocsp.int-x3.letsencrypt.org
Package: apache2 Version: 2.4.38-2 Severity: normal Dear Maintainer, After apache update to 2.4.38-1 /var/log/apache2/error.log has a lot of errors on each vhost like: [gnutls:error] [pid 6466:tid 140231699207936] Invalid HTTP response status from ocsp.int-x3.letsencrypt.org: HTTP/1.0 400 Bad Request [gnutls:warn] [pid 6466:tid 140231699207936] (104)Connection reset by peer: Async OCSP update failed for www.hostname.com:443, next update in 300 seconds. Using configuration: /etc/apache2/conf-enabled/: apache2-doc.conf charset.conf javascript-common.conf jsmath.conf localized-error-pages.conf other-vhosts-access-log.conf php7.3-fpm.conf phppgadmin.conf security.conf serve-cgi-bin.conf servername.conf /etc/apache2/mods-enabled/: access_compat.load actions.conf actions.load alias.conf alias.load auth_basic.load authn_core.load authn_file.load authz_core.load authz_groupfile.load authz_host.load authz_user.load autoindex.conf autoindex.load cgi.load deflate.conf deflate.load dir.conf dir.load env.load fcgid.conf fcgid.load filter.load gnutls.conf gnutls.load headers.load include.load mime.conf mime.load mime_magic.conf mime_magic.load mpm_event.conf mpm_event.load negotiation.conf negotiation.load perl.load proxy.conf proxy_fcgi.load proxy.load reqtimeout.conf reqtimeout.load rewrite.load setenvif.conf setenvif.load socache_dbm.load socache_shmcb.load status.conf status.load substitute.load userdir.conf userdir.load xsendfile.load *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-3-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages apache2 depends on: ii apache2-bin2.4.38-2 ii apache2-data 2.4.38-2 ii apache2-utils 2.4.38-2 ii dpkg 1.19.6 ii lsb-base 10.2019031300 ii mime-support 3.62 ii perl 5.28.1-6 ii procps 2:3.3.15-2 Versions of packages apache2 recommends: ii ssl-cert 1.0.39 Versions of packages apache2 suggests: ii apache2-doc 2.4.38-2 pn apache2-suexec-pristine | apache2-suexec-custom ii chromium [www-browser] 73.0.3683.75-1 ii elinks [www-browser] 0.13~20190125-3 ii firefox [www-browser]66.0.1-1 ii konqueror [www-browser] 4:18.12.0-1 ii links [www-browser] 2.18-1+b10 ii lynx [www-browser] 2.8.9rel.1-3 ii w3m [www-browser]0.5.3-37 Versions of packages apache2-bin depends on: ii libapr1 1.6.5-1+b1 ii libaprutil1 1.6.1-3+b2 ii libaprutil1-dbd-sqlite3 1.6.1-3+b2 ii libaprutil1-ldap 1.6.1-3+b2 ii libbrotli1 1.0.7-2 ii libc62.28-8 ii libcurl4 7.64.0-2 ii libjansson4 2.12-1 ii libldap-2.4-22.4.47+dfsg-3 ii liblua5.2-0 5.2.4-1.1+b2 ii libnghttp2-141.37.0-1 ii libpcre3 2:8.39-12 ii libssl1.11.1.1b-1 ii libxml2 2.9.4+dfsg1-7+b3 ii perl 5.28.1-6 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages apache2-bin suggests: ii apache2-doc 2.4.38-2 pn apache2-suexec-pristine | apache2-suexec-custom ii chromium [www-browser] 73.0.3683.75-1 ii elinks [www-browser] 0.13~20190125-3 ii firefox [www-browser]66.0.1-1 ii konqueror [www-browser] 4:18.12.0-1 ii links [www-browser] 2.18-1+b10 ii lynx [www-browser] 2.8.9rel.1-3 ii w3m [www-browser]0.5.3-37 Versions of packages apache2 is related to: ii apache2 2.4.38-2 ii apache2-bin 2.4.38-2 -- no debconf information
Bug#926431: cifs-utils: Password containing special character "$" (dollar) only works with prepended backslash
Package: cifs-utils
Version: 2:6.8-2
Severity: normal
Dear Maintainer,
recently I changed my LDAP password to a new one, that contains a "$" character.
Afterwards I failed to mount shares with this new password.
I tried the following approaches:
* interactive mount (e.g. "mount -t cifs -o user=foo //example/share /mnt")
* credential file
(e.g. "mount -t cifs -o user=foo,credentials=bar //example/share /mnt")
* indirect mount via "pam_mount"
In the first two cases I succeed to mount the share, if I prepend the
special character ("$") with a backslash. Thus "pass\$word" works, while
the real password is "pass$word".
The last case ("pam_mount") was obviously impossible to test this way.
I observed the same behaviour with a client on jessie (2:6.4-1) and on
stretch (2:6.7-1).
Thank you for your time!
Cheers,
Lars
PS: this issue does not seem to be related to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775051
(I failed to reproduce its problem on my hosts)
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 4.19.0-3-686-pae (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
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 /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled
Versions of packages cifs-utils depends on:
ii libc6 2.28-8
ii libcap-ng00.7.9-2
ii libkeyutils1 1.6-6
ii libkrb5-3 1.17-2
ii libpam0g 1.3.1-5
ii libtalloc22.1.14-2
ii libwbclient0 2:4.9.5+dfsg-2
cifs-utils recommends no packages.
Versions of packages cifs-utils suggests:
ii keyutils 1.6-6
pn smbclient
pn winbind
-- no debconf information
Bug#926415: unblock: debian-edu-config/2.10.64
On Thu, Apr 04, 2019 at 09:14:41PM +0200, Ivo De Decker wrote: > Unblocked based on #926269, right when you submitted this bug :) *g* & thank you! :) -- 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#926286: unblock: wxpython4.0/4.0.4+dfsg-2
Control: tags -1 - moreinfo On Wed, 3 Apr 2019, Paul Gevers wrote: There were two causes of FTBFS with SIP 4.19.14 that are fixed in my pending upload: 1) Addition of SIP_OVERRIDE 2) Addition of a mapped type for size_t The rollback of SIP_OVERRIDE in the sip4 package technically removes the need for the SIP_OVERRIDE FTFBS fixes in wxpython4.0, but my preference would be to leave them in because they appear to be fix actual bugs, even though they are no longer FTBFS bugs. Do you have any opinion on that? Ok, so there remains a FTBFS problem. Then yes, please proceed with uploading your fix, remove the moreinfo tag and we will check again. Are the patches known upstream? The build (wxpython4.0/4.0.4+dfsg-2) is now in unstable. The patches have been submitted upstream, but they are not all merged. Some background info on the patches, of which there are three: Patch 1 is submitted as pull request upstream. It is not yet merged. Patch 2 is not submitted upstream because it wouldn't be merged until upstream officially switches its build to SIP 4.19.14. It's a trivial patch anyway. Patch 3 is actually to the wxWidgets (the C++ library that wxPython wraps) public interface headers. This has been submitted to wxWidgets upstream and merged. Thanks, Scott
Bug#841762: kdeconnectd dies as soon as mobile device tries to connect
Package: kdeconnect Version: 1.3.3-2 Followup-For: Bug #841762 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I've reproduced this crash today. One factor - which may merely be a red herring - is that my devices on the network didn't have Internet access. They were both blocked by network login pages, but connect fine with that mitigated. - -- System Information: Debian Release: buster/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kdeconnect depends on: ii kde-cli-tools 4:5.14.5-1 ii kio 5.54.1-1 ii libc6 2.28-8 ii libfakekey0 0.1-10 ii libkf5configcore5 5.54.0-1 ii libkf5configwidgets5 5.54.0-1 ii libkf5coreaddons5 5.54.0-1 ii libkf5dbusaddons5 5.54.0-1 ii libkf5i18n5 5.54.0-1 ii libkf5iconthemes5 5.54.0-1 ii libkf5kcmutils5 5.54.0-1 ii libkf5kiocore55.54.1-1 ii libkf5kiofilewidgets5 5.54.1-1 ii libkf5kiowidgets5 5.54.1-1 ii libkf5notifications5 5.54.0-1 ii libkf5service-bin 5.54.0-1 ii libkf5service55.54.0-1 ii libkf5waylandclient5 4:5.54.0-1 ii libkf5widgetsaddons5 5.54.0-1 ii libqca-qt5-2 2.1.3-2 ii libqca-qt5-2-plugins 2.1.3-2 ii libqt5core5a 5.11.3+dfsg1-1 ii libqt5dbus5 5.11.3+dfsg1-1 ii libqt5gui55.11.3+dfsg1-1 ii libqt5network55.11.3+dfsg1-1 ii libqt5qml55.11.3-4 ii libqt5widgets55.11.3+dfsg1-1 ii libqt5x11extras5 5.11.3-2 ii libstdc++68.3.0-4 ii libx11-6 2:1.6.7-1 ii libxtst6 2:1.2.3-1 ii plasma-framework 5.54.0-1 ii qml-module-qtquick-controls 5.11.3-2 ii qml-module-qtquick-controls2 5.11.3+dfsg-2 ii qml-module-qtquick-layouts5.11.3-4 ii qml-module-qtquick2 5.11.3-4 ii sshfs 2.10+repack-2 kdeconnect recommends no packages. Versions of packages kdeconnect suggests: ii plasma-workspace 4:5.14.5.1-1 ii python-nautilus 1.2.2-2 - -- no debconf information -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEEAXEkn09uX7g8Tv8W3qerYfa4vJcFAlymqokACgkQ3qerYfa4 vJe+QQf/ZII7l3IPFY1DSNxz4WXqsk/qVyMrTEk6bZgmaKHIvPlzTCyUU1Ew4+mM c19zZuHLLhRQKSNU6uHQWqLTkrbw72EEHxJUhNiRQ/9fopbDzl/jHOyM3ERkZWpV 3VaV3kjaOwz0mKkZF+z5en0DCz2/C4YNkDKWlmN/+uUkuXuzN28k//SPHRM7ZaDp /rGBFyTSFRe4fndQw8yskhCszJ07R0ecofZM+E2cLjEeicJLbErQnDAllXjf6bhD 8w9iVYYlI742E69CKcmyCmxtFYkOlG3p7ggqVyKuVy6TiDue6sqmAqEqIf2lSs7h o1hopa99IbHgQbFe/OOyXNqU9ofRyw== =gH2z -END PGP SIGNATURE- Application: kdeconnectd (kdeconnectd), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbe18519840 (LWP 860))] Thread 4 (Thread 0x7fbe15199700 (LWP 925)): #0 0x7ffdf03a9b6a in clock_gettime () #1 0x7fbe1d9f2386 in __GI___clock_gettime (clock_id=clock_id@entry=1, tp=tp@entry=0x7fbe15198aa0) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7fbe1deeb1a1 in qt_clock_gettime (ts=0x7fbe15198aa0, clock=1) at kernel/qelapsedtimer_unix.cpp:175 #3 do_gettime (frac=, sec=) at kernel/qelapsedtimer_unix.cpp:166 #4 qt_gettime () at kernel/qelapsedtimer_unix.cpp:175 #5 0x7fbe1dee99d9 in QTimerInfoList::updateCurrentTime (this=this@entry=0x7fbe0c0048f0) at kernel/qtimerinfo_unix.cpp:91 #6 0x7fbe1dee9fd5 in QTimerInfoList::timerWait (this=0x7fbe0c0048f0, tm=...) at kernel/qtimerinfo_unix.cpp:388 #7 0x7fbe1deeb5fe in timerSourcePrepareHelper (timeout=0x7fbe15198b84, src=) at kernel/qeventdispatcher_glib.cpp:161 #8 timerSourcePrepare (source=, timeout=timeout@entry=0x7fbe15198b84) at kernel/qeventdispatcher_glib.cpp:165 #9 0x7fbe1beba669 in g_main_context_prepare (context=context@entry=0x7fbe0c000bf0, priority=priority@entry=0x7fbe15198c10) at ../../../glib/gmain.c:3492 #10 0x7fbe1bebb06b in g_main_context_iterate (context=context@entry=0x7fbe0c000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:3900 #11 0x7fbe1bebb25c in g_main_context_iteration (context=0x7fbe0c000bf0, may_block=may_block@entry=1) at ../../../glib/gmain.c:3981 #12 0x7fbe1deeb87b in QEventDispatcherGlib::processEvents (this=0x7fbe0c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #13 0x7fbe1de9927b in QEventLoop::exec (this=this@entry=0x7fbe15198d60, flags=..., flags@entry=...) at
Bug#926429: uscan: --skip-signature blocks --force-download from downloading the upstream package
Package: devscripts Version: 2.19.2 Severity: important Usertags: uscan Hi, While playing around with uscan, I found that using both '--skip-signature' and '--force-download' nullifies the effect of '--force-download'. For example: - emiliano@zapata:~/git/foo/firmware-tomu$ uscan --force-download --verbose uscan info: uscan (version 2.19.2) See uscan(1) for help uscan info: Scan watch files in . uscan info: Check debian/watch and debian/changelog in . uscan info: package="firmware-tomu" version="2.0~rc7-1" (as seen in debian/changelog) uscan info: package="firmware-tomu" version="2.0~rc7" (no epoch/revision) uscan info: Check debian/watch and debian/changelog in ./.git/logs/refs/remotes/origin uscan info: Check debian/watch and debian/changelog in ./.git/logs/refs/heads uscan info: Check debian/watch and debian/changelog in ./.git/refs/remotes/origin uscan info: Check debian/watch and debian/changelog in ./.git/refs/heads uscan info: ./debian/changelog sets package="firmware-tomu" version="2.0~rc7" uscan info: Process watch file at: debian/watch package = firmware-tomu version = 2.0~rc7 pkg_dir = . uscan info: opts: filenamemangle=s/.+\/v?(\d\S+)\.tar\.gz/firmware-tomu-$1\.tar\.gz/,uversionmangle=s/(\d)[_\.\-\+]?((RC|rc|pre|dev|beta|alpha)\d*)$/$1~$2/ uscan info: line: https://github.com/im-tomu/tomu-bootloader/tags .*/v?(\d[\d\.\-rc]+)\.tar\.gz uscan info: Parsing filenamemangle=s/.+\/v?(\d\S+)\.tar\.gz/firmware-tomu-$1\.tar\.gz/ uscan info: Parsing uversionmangle=s/(\d)[_\.\-\+]?((RC|rc|pre|dev|beta|alpha)\d*)$/$1~$2/ uscan info: line: https://github.com/im-tomu/tomu-bootloader/tags .*/v?(\d[\d\.\-rc]+)\.tar\.gz uscan info: Last orig.tar.* tarball version (from debian/changelog): 2.0~rc7 uscan info: Last orig.tar.* tarball version (dversionmangled): 2.0~rc7 uscan info: Requesting URL: https://github.com/im-tomu/tomu-bootloader/tags uscan info: Matching pattern: (?:(?:https://github.com)?\/im\-tomu\/tomu\-bootloader\/tags)?.*/v?(\d[\d\.\-rc]+)\.tar\.gz uscan info: Found the following matching hrefs on the web page (newest first): /im-tomu/tomu-bootloader/archive/v2.0-rc7.tar.gz (2.0~rc7) index=2.0~rc7-1 /im-tomu/tomu-bootloader/archive/v2.0-rc6.tar.gz (2.0~rc6) index=2.0~rc6-1 /im-tomu/tomu-bootloader/archive/v2.0-rc5.tar.gz (2.0~rc5) index=2.0~rc5-1 /im-tomu/tomu-bootloader/archive/v2.0-rc4.tar.gz (2.0~rc4) index=2.0~rc4-1 /im-tomu/tomu-bootloader/archive/v2.0-rc3.tar.gz (2.0~rc3) index=2.0~rc3-1 /im-tomu/tomu-bootloader/archive/v2.0-rc2.tar.gz (2.0~rc2) index=2.0~rc2-1 /im-tomu/tomu-bootloader/archive/v2.0-rc1.tar.gz (2.0~rc1) index=2.0~rc1-1 uscan info: Looking at $base = https://github.com/im-tomu/tomu-bootloader/tags with $filepattern = .*/v?(\d[\d\.\-rc]+)\.tar\.gz found $newfile = /im-tomu/tomu-bootloader/archive/v2.0-rc7.tar.gz $newversion = 2.0~rc7 which is newer than $lastversion = 2.0~rc7 uscan info: Matching target for downloadurlmangle: https://github.com/im-tomu/tomu-bootloader/archive/v2.0-rc7.tar.gz uscan info: Upstream URL(+tag) to download is identified as https://github.com/im-tomu/tomu-bootloader/archive/v2.0-rc7.tar.gz uscan info: Matching target for filenamemangle: /im-tomu/tomu-bootloader/archive/v2.0-rc7.tar.gz uscan info: Filename (filenamemangled) for downloaded file: firmware-tomu-2.0-rc7.tar.gz uscan info: Newest version of firmware-tomu on remote site is 2.0~rc7, local version is 2.0~rc7 uscan info:=> Package is up to date for from https://github.com/im-tomu/tomu-bootloader/archive/v2.0-rc7.tar.gz uscan info:=> Forcing download as requested uscan info: Downloading upstream package: firmware-tomu-2.0-rc7.tar.gz uscan info: Requesting URL: https://github.com/im-tomu/tomu-bootloader/archive/v2.0-rc7.tar.gz uscan info: Successfully downloaded package: firmware-tomu-2.0-rc7.tar.gz uscan info: Start checking for common possible upstream OpenPGP signature files uscan info: End checking for common possible upstream OpenPGP signature files uscan info: Missing OpenPGP signature. uscan info: New orig.tar.* tarball version (oversionmangled): 2.0~rc7 uscan info: Launch mk-origtargz with options: --package firmware-tomu --version 2.0~rc7 --compression default --directory .. --copyright-file debian/copyright ../firmware-tomu-2.0-rc7.tar.gz Successfully repacked ../firmware-tomu-2.0-rc7.tar.gz as ../firmware-tomu_2.0~rc7.orig.tar.xz, deleting 11 files from it. uscan info: New orig.tar.* tarball version (after mk-origtargz): 2.0~rc7 uscan info: Scan finished - The upstream package is downloaded and repacked as intended. Now with '--skip-signature': - emiliano@zapata:~/git/foo/firmware-tomu$ uscan --force-download --skip-signature --verbose uscan info: uscan (version 2.19.2) See uscan(1) for help uscan info:
Bug#926335: closed by Joao Eriberto Mota Filho (Bug#926335: fixed in forensics-extra 2.8)
Em qui, 4 de abr de 2019 às 05:35, Andreas Beckmann escreveu: > > Thanks. > > Unblock request filed: #926374 Thanks a lot Andreas! Eriberto
Bug#926149: Subject: Re: Bug#926149: AMD: Add nomodeset kernel parameter to avoid black screen
B> However it might be reasonable to add "nomodeset" to the command line B> in GRUB's "recovery" boot menu items. OK, great. Now all that is left is for me to help you figure out why the installer incorrectly detects that the drivers are available, etc. I am able to workaround all this, I just want to help you finish testing before I finish installing my system and thus will not be able to help anymore.
Bug#926428: mate-panel: shotwell take over mate-panel menu items
Package: mate-panel Version: 1.20.5-1 Severity: important Tags: a11y Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.0.6 (SMP w/24 CPU cores; PREEMPT) Kernel taint flags: TAINT_CRAP, TAINT_UNSIGNED_MODULE Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8), LANGUAGE=sv_SE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mate-panel depends on: ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2 ii libatk1.0-0 2.30.0-2 ii libc62.28-8 ii libcairo-gobject21.16.0-4 ii libcairo21.16.0-4 ii libdbus-1-3 1.12.12-1 ii libdbus-glib-1-2 0.110-4 ii libdconf10.30.1-2 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 libice6 2:1.0.9-2 ii libmate-desktop-2-17 1.20.4-2 ii libmate-menu21.20.2-1 ii libmate-panel-applet-4-1 1.20.5-1 ii libmateweather1 1.20.2-1 ii libpango-1.0-0 1.42.4-6 ii libpangocairo-1.0-0 1.42.4-6 ii librda0 0.0.5-1 ii librsvg2-2 2.44.10-1 ii libsm6 2:1.2.3-1 ii libstartup-notification0 0.12-6 ii libwnck-3-0 3.30.0-2 ii libx11-6 2:1.6.7-1 ii libxau6 1:1.0.8-1+b2 ii libxrandr2 2:1.5.1-1 ii mate-desktop 1.20.4-2 ii mate-menus 1.20.2-1 ii mate-panel-common1.20.5-1 ii mate-polkit 1.20.2-1 ii menu-xdg 0.6 mate-panel recommends no packages. mate-panel suggests no packages. -- no debconf information Debian Buster. I don't know if it is a mate-menu issue, or a shotwell issue. I think menu items should not be overwritten like that. Shotwell is taking over menuitems in mate-panel Places menu. On my system the items are Homedir, Desktop dir google drive dir and another dir. It shows shotwell on this four items. Uninstall shotwell will show the correct menu items. I don't know where the panel save its data or how deb packages install themselves so i can check who is responsible. Don't know where to look. The system is a ROG strix X399-E GAMING with Ryzen 12 core cpu and 5.0.6 kernel, I need a newer kernel for the rtl 8822 (wi-fi bluetooth). Custom kernel needed for the 1000 Hz timer freq. and KVM for AMD.
Bug#926427: unblock: astroidmail/0.14-2.1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Dear Release Team,
Please unblock astroidmail 0.14-2.1. This upload fixes the RC bug
https://bugs.debian.org/924818 , which is caused by the compatibility
issue between this software and the newer ronn 0.8.x introduced in the
Buster cycle. The solution is to use the alternative tool (scdoc) as
preferred by upstream to generate the man page. A patch onto
CMakeLists.txt is also applied to fix the ronn compatibility issue
itself.
--
Thanks,
Boyuan Yang
Full source diff is also provided here:
diff -Nru astroidmail-0.14/debian/changelog astroidmail-
0.14/debian/changelog
--- astroidmail-0.14/debian/changelog 2018-11-30 15:54:19.0
-0500
+++ astroidmail-0.14/debian/changelog 2019-04-04 19:03:52.0
-0400
@@ -1,3 +1,13 @@
+astroidmail (0.14-2.1) unstable; urgency=high
+
+ * Non-maintainer upload.
+ * debian/patches: Add a patch to fix compatibility with
+newer ronn and solve the FTBFS. (Closes: #924818)
+ * debian/control: Add build-dependency on scdoc in order to
+generate man pages with higher quality.
+
+ -- Boyuan Yang Thu, 04 Apr 2019 19:03:52 -0400
+
astroidmail (0.14-2) unstable; urgency=medium
* Add patch cherry-picked upstream
diff -Nru astroidmail-0.14/debian/control astroidmail-
0.14/debian/control
--- astroidmail-0.14/debian/control 2018-10-01 04:27:05.0
-0400
+++ astroidmail-0.14/debian/control 2019-04-04 19:03:50.0
-0400
@@ -28,6 +28,7 @@
pkg-config,
protobuf-compiler,
python3-gi,
+ scdoc,
ronn,
xauth,
xvfb,
diff -Nru astroidmail-0.14/debian/patches/1002-CMakeLists.txt-Update-
ronn-parameters-for-compat-wit.patch astroidmail-
0.14/debian/patches/1002-CMakeLists.txt-Update-ronn-parameters-for-
compat-wit.patch
--- astroidmail-0.14/debian/patches/1002-CMakeLists.txt-Update-ronn-
parameters-for-compat-wit.patch 1969-12-31 19:00:00.0 -0500
+++ astroidmail-0.14/debian/patches/1002-CMakeLists.txt-Update-ronn-
parameters-for-compat-wit.patch 2019-04-04 19:01:03.0 -0400
@@ -0,0 +1,25 @@
+From: Boyuan Yang
+Date: Thu, 4 Apr 2019 18:44:22 -0400
+Subject: CMakeLists.txt: Update ronn parameters for compat with new
ronn
+
+The newer versions of ronn no longer accepts the -p option.
+Using the long option ("--pipe") instead.
+
+Forwarded: https://github.com/astroidmail/astroid/issues/627
+---
+ CMakeLists.txt | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/CMakeLists.txt b/CMakeLists.txt
+index 99b38e4..d1de553 100644
+--- a/CMakeLists.txt
b/CMakeLists.txt
+@@ -410,7 +410,7 @@ if (NOT DISABLE_DOCS)
+ message (WARNING "Falling back to 'ronn' for man page
generation.")
+ add_custom_command (
+ TARGET astroid
+-COMMAND ${RONN} -rp ${CMAKE_SOURCE_DIR}/doc/astroid.1.scd |
gzip > ${CMAKE_BINARY_DIR}/astroid.1.gz
++COMMAND ${RONN} -r --pipe
${CMAKE_SOURCE_DIR}/doc/astroid.1.scd | gzip >
${CMAKE_BINARY_DIR}/astroid.1.gz
+ COMMENT "Generating man page (ronn)")
+ else ()
+ message (FATAL_ERROR "Neither 'scdoc' nor 'ronn' installed. One
is required for man page generation.")
diff -Nru astroidmail-0.14/debian/patches/series astroidmail-
0.14/debian/patches/series
--- astroidmail-0.14/debian/patches/series 2018-11-30
15:50:50.0 -0500
+++ astroidmail-0.14/debian/patches/series 2019-04-04
18:50:50.0 -0400
@@ -1 +1,2 @@
020181123~83c03f4.patch
+1002-CMakeLists.txt-Update-ronn-parameters-for-compat-wit.patch
signature.asc
Description: This is a digitally signed message part
Bug#926317: [Debian-iot-maintainers] Bug#926317: Bug#926317: libyder.pc Requires.private systemd, but systemd not in debian/control
Hello Harald, IIRC, I put this patch in the first place because of compilation errors at the time, the errors were fixed only after patching the cmake script like this. But your bug made me check again and it seems that it's no longer necessary. So I'll remove the patch and push a new package soon. Thanks Le 19-04-04 à 10 h 25, Harald Welte a écrit : > Hi Nicolas, > > thanks for your response. > > On Thu, Apr 04, 2019 at 09:10:10AM -0400, Nicolas Mora wrote: >> Libyder relies on libsystemd to write logs in journald, but it's one of the >> log output available, like syslog, a file, a callback or the console. But >> you can use libyder without systemd if you don't use it as log output. > > This is great, > > but then why do you have the following patch in the yder debian package? > > Description: soname is still 2.0, fix PKGCONF_REQ_PRIVATE > Author: Nicolas Mora > Index: yder-1.4.4/CMakeLists.txt > === > --- yder-1.4.4.orig/CMakeLists.txt > +++ yder-1.4.4/CMakeLists.txt > @@ -135,7 +135,7 @@ endif () > > if (WITH_JOURNALD) >set(PKGCONF_REQ "") > - set(PKGCONF_REQ_PRIVATE "libsystemd, liborcania") > + set(PKGCONF_REQ_PRIVATE "systemd, liborcania") > else () >set(PKGCONF_REQ "") >set(PKGCONF_REQ_PRIVATE "liborcania") > > This patch does the *exact opposite* of what you described in your > e-mail. It causes the libyder.pc contain a Requires.private on > 'systemd', and not on 'libsytemd'. > > This means you can build + install they libyder + libyder-dev package just > fine > on a system without systemd. But then, when you actually want to build any > application against libyder, its autoconf/cmake step will fail as > 'systemd.pc' is > not available but listed in Requires.private. > > So if you really only need libsystemd, why change from libsystemd to > systemd in the patch above? > > Regards, > Harald >
Bug#784479: Bug#876905: qtwebkit should not be release with buster
Control: tags -1 buster-ignore
On Thu, Apr 04, 2019 at 10:39:25PM +0200, Ivo De Decker wrote:
> On Tue, Apr 02, 2019 at 11:30:44PM +0200, Moritz Muehlenhoff wrote:
> > Sure, if the release team agrees with that approach, the canonical way to do
> > that would be to tag the bug as "buster-ignore".
>
> OK, tagging 876905 ("qtwebkit should not be released with buster") and 784477
> ("[kde-runtime] Qt4's WebKit removal").
Also tagging #784479.
Ivo
Bug#926426: unblock: python-smoke-zephyr/1.4.1-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hello, I'm asking for the unblock of python-smoke-zephyr because a critical bug was solved upstream. This bug was detected in the past and me and upstream thought it was fixed already[0], then after it was reported again recently[1] we found out that the problem still persisted. This time I first tried to fix the problem by uploading 1.4.0-2, and while it was on Unstable I think somebody else filled an unblock request and it was granted, but before this version hit testing I uploaded the correct fix (1.4.1-1) to unstable, that's why you can see two changelog entries on the debdiff. Thanks [0]https://github.com/zeroSteiner/smoke-zephyr/issues/4 [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925208 -- Samuel Henrique python-smoke-zephyr.debdiff Description: Binary data
Bug#925227: closed by Boyuan Yang (Bug#925227: fixed in biabam 0.9.7-7.1)
On 2019-04-05 00:36, Debian Bug Tracking System wrote: > + debian/compat: Bump to 9. > + debian/control: Build-depend on debhelper (>= 9). That will not get unblocked during the freeze. Andreas
Bug#918578: ping this bug again
Ping this bug again to keep the chance to fix it. Wolfgang signature.asc Description: PGP signature
Bug#926407: [l10n] Updated Czech translation of apt-listbugs
On Thu, 4 Apr 2019 17:53:40 +0200 Miroslav Kure wrote: > Package: apt-listbugs > Severity: wishlist > Tags: l10n, patch > > Hi, > > in attachement there is updated Czech (cs.po) translation of > apt-listbugs. Please include it with the package. Hi Miroslav! Thanks for the updated translation: I will take a look at it soon, in order to include it in the package. Unfortunately Debian buster is already in full freeze, hence this updated translation won't make it in the next stable release. It will be included in the upload to Debian unstable that will be done *after* the buster release... Bye. -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgpghNdttNv1h.pgp Description: PGP signature
Bug#926425: facilitate usage of cachefilesd for NFS mount points
Package: debian-edu-config Severity: wishlist Hi all, another idea / request for bullseye... We have one school where 2 notebooks and 4 notebooks are each behind a very low bandwith line (on-site VDSL modem bridges, wired over underground telephone cable, 20MBit/s synchronous max speed). On these network endpoints, NFS performance is really really poor. So, today I played with the FS-cache kernel implementation underneath the NFS file system. A running stretch setup needed three things to get FS-cache working: * 'fsc' extra mount option for the autofs'ed NFS mount points in LDAP * apt-get install cachefilesd * enable cachefilesd in /etc/default/cachefilesd After I had these bits set up, I could observe a softer usability of the notebook I was sitting in front of. While I had to wait for several tasks irregularly during normal operation (browser, libreoffice), I could subjectively work much smoother with FS-cache up and running. I also tested, if 'fsc' is painful to systems that don't have the cachefilesd service running. It is not. It is a no-op parameter then. Unfortunately, the cachefilesd DEB package has fallen out of buster due to apparmor incompatibility. So, this bug report is for bullseye, I supppose. (However, we could use 'fsc' as a mount option already, so buster's edu LDAP is bootstrapped correctly for this already). Greets, Mike -- DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4354) 8390 139 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de pgp9IWc4Q7SDG.pgp Description: Digitale PGP-Signatur
Bug#926423: webext-https-everywhere: Possible issue with https-everywhere crashing Firefox-ESR tabs.
Hi, Am 04.04.19 um 23:32 schrieb Damon Thomas: > Package: webext-https-everywhere > Version: 2019.1.31-2 > Severity: normal > > Dear Maintainer, > > I was having issues with frequent "Gah. Your Tab Just Crashed" Firefox-ESR > errors. > This persisted through the recent FF-ESR point upgrade. After disabling > https-everywhere this issue has stopped. I had no similar problems with > Chromium > using this package. > > Damon Thomas > I think those issues are not Debian specific. We don't make any changes to the upstream code. Could you please report a new issue here: https://github.com/EFForg/https-everywhere/issues/ and then also include the information on which sites this occurred and how it is reproducible. The developers of https-everywhere are more able to track this down. Then just send us the link to the upstream bug report, so that we can follow up if necessary. Thanks Markus signature.asc Description: OpenPGP digital signature
Bug#926388: let Firefox trust /etc/ssl/certs/ca-certificates.crt
Hi Wolfgang.
On Do 04 Apr 2019 17:18:38 CEST, Wolfgang Schweer wrote:
On Thu, Apr 04, 2019 at 01:03:50PM +, Mike Gabriel wrote:
Feel free to keep this bug open for bullseye, so we can re-discuss this
approach or close it.
Yes, let's consider this for bullseye.
Yep.
Just for the record:
[ pkcs11.txt ]
On a 64-bit PC Buster system this is working ok:
library=/usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so
name=PKCS#11 Trust Module
NSS=trustOrder=100
Nice.
To get it working for a mixed 64-bit / 32-bit setup this content
seems to work:
library=/usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so
library=/usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so
name=PKCS#11 Trust Module
NSS=trustOrder=100
Nice add-on information.
For already existing accounts:
[ Firefox-ESR ]
Checking the existence and then removing
~/.mozilla/firefox/debian-edu.default/{cert8.db,key3.db,cert9.db,key4.db}
after replacing the exsting pkcs11.txt file seems to work.
That is not necessary IMHO. If pkcs11.txt exists, the above text
config block needs to be appended to it. If it does not exist, copying
over the above pkcs11.txt is sufficient.
[ Thunderbird ]
Similar to Firefox-ESR; location:
~/.thunderbird/debian-edu.default/{cert8.db,key3.db,cert9.db,key4.db}
Same here. The .db files can stay. If pkcs11.txt exists, append the
above config block.
[ Chromium, Konqueror, and others using PKI ]
Check the existence and then remove
~/.pki/{cert9.db,key4.db}
after replacing the exsting pkcs11.txt file
Same here. Again, not replacing pkcs11.txt, but appending to it, if it
exists. The .db files can stay.
Mike
--
DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139
GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de
pgpNRw998Klis.pgp
Description: Digitale PGP-Signatur
Bug#871792: wait a little
On 2018-07-17, Josua Mayer wrote: > Sorry for the quick addition: a secodn uncertainty lies in the name of > the boot script. > We currently search for a bootargs.scr which was supposed to let distros > set a few boot options, and then return control back to the menu. > > So maybe the name should be boot.scr instead. I will update once this > has been decided. Any status update? Not much time left to get into the next release... live well, vagrant signature.asc Description: PGP signature
Bug#924255: systemd 232-25+deb9u10 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: systemd Version: 232-25+deb9u10 Explanation: journald: fix assertion failure on journal_file_link_data; tmpfiles: fix "e" to support shell style globs; mount-util: accept that name_to_handle_at() might fail with EPERM; automount: ack automount requests even when already mounted [CVE-2018-1049]; fix potential root privilege escalation [CVE-2018-15686]
Bug#924145: vips 8.4.5-1+deb9u1 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: vips Version: 8.4.5-1+deb9u1 Explanation: fix NULL function pointer dereference [CVE-2018-7998], uninitialised memory access [CVE-2019-6976]
Bug#922918: twitter-bootstrap3 3.3.7+dfsg-2+deb9u2 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: twitter-bootstrap3 Version: 3.3.7+dfsg-2+deb9u2 Explanation: fix XSS in tooltip or popover [CVE-2019-8331]
Bug#926423: webext-https-everywhere: Possible issue with https-everywhere crashing Firefox-ESR tabs.
Package: webext-https-everywhere Version: 2019.1.31-2 Severity: normal Dear Maintainer, I was having issues with frequent "Gah. Your Tab Just Crashed" Firefox-ESR errors. This persisted through the recent FF-ESR point upgrade. After disabling https-everywhere this issue has stopped. I had no similar problems with Chromium using this package. Damon Thomas -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled webext-https-everywhere depends on no packages. Versions of packages webext-https-everywhere recommends: ii chromium 73.0.3683.75-1 ii firefox-esr 60.6.1esr-1 webext-https-everywhere suggests no packages. -- no debconf information
Bug#926424: cloud-init: No log rotation
Package: cloud-init
Version: 18.3
Severity: wishlist
Tags: patch
Dear Maintainer,
The cloud-init system logs to the follow files:
- /var/log/cloud-init-output.log
- /var/log/cloud-init.log
There is nothing shipped which rotates these log files, which is a shame
as they'll grow everytime an instance is rebooted. We have some customers
with reasonably large log files now...
Please find attached a proposed logrotate file.
Cheers,
Andrew
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.0.0-trunk-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8),
LANGUAGE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages cloud-init depends on:
ii cloud-guest-utils 0.29-1
ii fdisk 2.33.1-0.1
ii gdisk 1.0.3-1.1
ii ifupdown0.8.35
ii locales 2.28-8
ii lsb-base10.2019031300
ii lsb-release 10.2019031300
ii net-tools 1.60+git20180626.aebd88e-1
ii procps 2:3.3.15-2
ii python3 3.7.3-1
pn python3-configobj
ii python3-jinja2 2.10-1
pn python3-jsonpatch
pn python3-jsonschema
pn python3-oauthlib
ii python3-requests2.21.0-1
ii python3-six 1.12.0-1
ii python3-yaml3.13-2
ii util-linux 2.33.1-0.1
Versions of packages cloud-init recommends:
ii eatmydata 105-7
ii sudo 1.8.27-1
Versions of packages cloud-init suggests:
ii btrfs-progs 4.20.2-1
ii e2fsprogs1.45.0-1
ii xfsprogs 4.20.0-1
/var/log/cloud-init.log
/var/log/cloud-init-output.log
{
weekly
rotate 4
compress
delaycompress
missingok
notifempty
}
Bug#926422: unblock: java-atk-wrapper/0.33.3-22
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Hello,
Please unblock package java-atk-wrapper. As shown in Bug#926420, it has
a strong memory leak and performance issue, as raised upstream on
https://bugzilla.gnome.org/show_bug.cgi?id=791970 and
https://issues.apache.org/jira/browse/NETBEANS-861
It does not make applications really crash, but the latter report says
it makes the netbeans UI really unresponsive.
unblock java-atk-wrapper/0.33.3-22
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500,
'proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500,
'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'),
(1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.0.0 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru java-atk-wrapper-0.33.3/debian/changelog
java-atk-wrapper-0.33.3/debian/changelog
--- java-atk-wrapper-0.33.3/debian/changelog2018-05-02 23:06:45.0
+0200
+++ java-atk-wrapper-0.33.3/debian/changelog2019-04-04 22:51:05.0
+0200
@@ -1,3 +1,9 @@
+java-atk-wrapper (0.33.3-22) unstable; urgency=medium
+
+ * patches/remove_component_listener: Fix memory leak (Closes: Bug#926420)
+
+ -- Samuel Thibault Thu, 04 Apr 2019 22:51:05 +0200
+
java-atk-wrapper (0.33.3-21) unstable; urgency=medium
* Bump Standards-Version to 4.1.4 (no changes).
diff -Nru java-atk-wrapper-0.33.3/debian/patches/remove_component_listener
java-atk-wrapper-0.33.3/debian/patches/remove_component_listener
--- java-atk-wrapper-0.33.3/debian/patches/remove_component_listener
1970-01-01 01:00:00.0 +0100
+++ java-atk-wrapper-0.33.3/debian/patches/remove_component_listener
2019-04-04 22:50:49.0 +0200
@@ -0,0 +1,23 @@
+commit f9faf04a88685d6759c18572988876215332086a
+Author: Samuel Thibault
+Date: Tue Apr 2 19:55:13 2019 +0200
+
+Fix removing component listener
+
+instead of adding it again.
+
+Fixes https://bugzilla.gnome.org/show_bug.cgi?id=791970
+
+diff --git a/wrapper/org/GNOME/Accessibility/AtkWrapper.java.in
b/wrapper/org/GNOME/Accessibility/AtkWrapper.java.in
+index 0fbb196..3463a59 100644
+--- a/wrapper/org/GNOME/Accessibility/AtkWrapper.java.in
b/wrapper/org/GNOME/Accessibility/AtkWrapper.java.in
+@@ -306,7 +306,7 @@ public class AtkWrapper {
+ case ContainerEvent.COMPONENT_REMOVED:
+ {
+ java.awt.Component c = ((ContainerEvent)e).getChild();
+-c.addComponentListener(componentAdapter);
++c.removeComponentListener(componentAdapter);
+ break;
+ }
+
diff -Nru java-atk-wrapper-0.33.3/debian/patches/series
java-atk-wrapper-0.33.3/debian/patches/series
--- java-atk-wrapper-0.33.3/debian/patches/series 2018-05-02
22:58:28.0 +0200
+++ java-atk-wrapper-0.33.3/debian/patches/series 2019-04-04
22:51:05.0 +0200
@@ -19,4 +19,6 @@
GC
parameters
coords
+remove_component_listener
+
nojavah
Bug#926421: netcdf-parallel: please make the build reproducible
Source: netcdf-parallel Version: 1:4.6.2-1 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: buildpath X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Hi, Whilst working on the Reproducible Builds effort [0], we noticed that netcdf-parallel could not be built reproducibly. This is because it includes the CFLAGS and, as this includes -fdebug- prefix-map with the absolute build directory, it renders the package unreproducible. Patch attached that updates the existing reproducibility patch. :) [0] https://reproducible-builds.org/ Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- --- a/debian/patches/reproducible-settings.patch2019-04-04 22:53:53.561465325 +0200 --- b/debian/patches/reproducible-settings.patch2019-04-04 23:05:55.547074168 +0200 @@ -1,11 +1,9 @@ Description: Remove settings that make the build unreproducible. Author: Bas Couwenberg -Index: netcdf-parallel-4.6.2/libnetcdf.settings.in -=== --- netcdf-parallel-4.6.2.orig/libnetcdf.settings.in +++ netcdf-parallel-4.6.2/libnetcdf.settings.in -@@ -4,8 +4,6 @@ +@@ -4,15 +4,12 @@ # General --- NetCDF Version: @PACKAGE_VERSION@ @@ -14,3 +12,10 @@ Build Directory: @abs_top_builddir@ Install Prefix: @prefix@ + # Compiling Options + - + C Compiler: @CC_VERSION@ +-CFLAGS: @CFLAGS@ + CPPFLAGS: @CPPFLAGS@ + LDFLAGS: @LDFLAGS@ + AM_CFLAGS:@AM_CFLAGS@ --- a/libnetcdf.settings.in 2019-04-04 22:53:53.653466909 +0200 --- b/libnetcdf.settings.in 2019-04-04 23:06:19.635334510 +0200 @@ -10,7 +10,6 @@ # Compiling Options - C Compiler:@CC_VERSION@ -CFLAGS:@CFLAGS@ CPPFLAGS: @CPPFLAGS@ LDFLAGS: @LDFLAGS@ AM_CFLAGS: @AM_CFLAGS@
Bug#925939: jupyter-notebook: CVE-2019-10255: open redirect vulnerability
On Thu, Mar 28, 2019 at 10:54:17PM +0100, Salvatore Bonaccorso wrote: > Source: jupyter-notebook > Version: 5.7.4-2 > Severity: important > Tags: patch security upstream > > Hi, > > The following vulnerability was published for jupyter-notebook. > > CVE-2019-10255[0]: > | An Open Redirect vulnerability for all browsers in Jupyter Notebook > | before 5.7.7 and some browsers (Chrome, Firefox) in JupyterHub before > | 0.9.5 allows crafted links to the login page, which will redirect to a > | malicious site after successful login. Servers running on a base_url > | prefix are not affected. > > > If you fix the vulnerability please also make sure to include the > CVE (Common Vulnerabilities & Exposures) id in your changelog entry. > > For further information see: > > [0] https://security-tracker.debian.org/tracker/CVE-2019-10255 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10255 > > Please adjust the affected versions in the BTS as needed. When fixing this issue actually make sure that not only the incomplete fix is applied, cf. https://blog.jupyter.org/open-redirect-vulnerability-in-jupyter-jupyterhub-adf43583f1e4 (adressed in 5.7.8). Regards, Salvatore
Bug#926420: java-atk-wrapper: memory leak and performance issue
Source: java-atk-wrapper
Version: 0.33.3-13
Severity: important
Tags: patch upstream a11y
Forwarded: https://bugzilla.gnome.org/show_bug.cgi?id=791970
Hello,
As reported upstream
https://bugzilla.gnome.org/show_bug.cgi?id=791970
there is a memory leak within java-atk-wrapper, which in the bug report
case triggers a performance issue, and on
https://issues.apache.org/jira/browse/NETBEANS-861
triggers UI responsiveness issues, making it barely usable.
The attached patch fixes this: java-atk-wrapper adds the component
listener again instead of removing it.
Samuel
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500,
'proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500,
'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'),
(1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.0.0 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
commit f9faf04a88685d6759c18572988876215332086a
Author: Samuel Thibault
Date: Tue Apr 2 19:55:13 2019 +0200
Fix removing component listener
instead of adding it again.
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=791970
diff --git a/wrapper/org/GNOME/Accessibility/AtkWrapper.java.in
b/wrapper/org/GNOME/Accessibility/AtkWrapper.java.in
index 0fbb196..3463a59 100644
--- a/wrapper/org/GNOME/Accessibility/AtkWrapper.java.in
+++ b/wrapper/org/GNOME/Accessibility/AtkWrapper.java.in
@@ -306,7 +306,7 @@ public class AtkWrapper {
case ContainerEvent.COMPONENT_REMOVED:
{
java.awt.Component c = ((ContainerEvent)e).getChild();
-c.addComponentListener(componentAdapter);
+c.removeComponentListener(componentAdapter);
break;
}
Bug#926419: abiword: When logged in with wayland session you can not see what you type with out having to scroll screen.
Package: abiword Version: 3.0.2-8 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (1000, 'unstable'), (500, 'stable-updates'), (100, 'testing'), (100, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/1 CPU core) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages abiword depends on: ii abiword-common 3.0.2-8 ii gsfonts 1:8.11+urwcyr1.0.7~pre44-4.4 ii libabiword-3.0 3.0.2-8 ii libc6 2.28-8 ii libdbus-1-3 1.12.12-1 ii libdbus-glib-1-20.110-4 ii libgcc1 1:8.3.0-5 ii libgcrypt20 1.8.4-5 ii libglib2.0-02.58.3-1 ii libgnutls30 3.6.7-2 ii libgoffice-0.10-10 0.10.44-1 ii libgsf-1-1141.14.45-1 ii libgtk-3-0 3.24.5-1 ii libjpeg62-turbo 1:1.5.2-2+b1 ii libloudmouth1-0 1.5.3-5 ii libots0 0.5.0-3 ii libpng16-16 1.6.36-5 ii librdf0 1.0.17-1.1+b1 ii libreadline77.0-5 ii librevenge-0.0-00.0.4-6 ii libsoup2.4-12.64.2-2 ii libstdc++6 8.3.0-5 ii libtelepathy-glib0 0.24.1-2 ii libtidy5deb12:5.6.0-10 ii libwmf0.2-7 0.2.8.4-14 ii libwpd-0.10-10 0.10.3-1 ii libwpg-0.3-30.3.3-1 ii libxml2 2.9.4+dfsg1-7+b3 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages abiword recommends: ii abiword-plugin-grammar 3.0.2-8 ii aspell-en [aspell-dictionary] 2018.04.16-0-1 ii fonts-liberation 1:1.07.4-9 ii poppler-utils 0.71.0-3 abiword suggests no packages. -- no debconf information
Bug#784477: Bug#876905: qtwebkit should not be release with buster
Control: tags -1 buster-ignore
Hi,
On Tue, Apr 02, 2019 at 11:30:44PM +0200, Moritz Muehlenhoff wrote:
> Sure, if the release team agrees with that approach, the canonical way to do
> that would be to tag the bug as "buster-ignore".
OK, tagging 876905 ("qtwebkit should not be released with buster") and 784477
("[kde-runtime] Qt4's WebKit removal").
Thanks,
Ivo
Bug#921284: build-using should only include copylefted files
Control: tags -1 buster-ignore Hi, On Thu, Feb 07, 2019 at 12:54:59PM +1300, Michael Hudson-Doyle wrote: > It's true, however, that the Debian policy specifies built-using is for > copyright reasons. Please note that policy says 'license or DFSG requirements to provide full source code', not only license. But policy doesn't clarify what that means in practice. > https://www.debian.org/doc/debian-policy/ch-relationships.html# > additional-source-packages-used-to-build-the-binary-built-using > > Specifically, the last pargraph reads: > > > This field should not be added solely for purposes other than > > satisfying license or DFSG requirements to provide full source > > code. In particular, it should not be added solely to enable finding > > packages that should be rebuilt against newer versions of their build > > dependencies. > > Yet, from what I understand, that is *exactly* how that field is used in > the golang team. Is that correct? > > It should be noted this is a SHOULD NOT and not a MUST NOT, so it's a > little more relaxed - may we are allowed to abuse it like this. > > I do wonder if it's deliberate, however. It seems to me this should be > clarified, both in dh-golang and in policy, either way. > > > It's a pretty recent change in policy to clarify that how go packages use it > is > not the intended use. When go packages started using Built-Using, they were > 100% compliant with the wording (if not the intent) of policy :) Whatever the outcome of this discussion, changing something for buster is too late, so I'm tagging this bug buster-ignore. Thanks, Ivo
Bug#926418: libvirt: CVE-2019-3886: virsh domhostname command discloses guest hostname in readonly mode
Source: libvirt Version: 5.0.0-1 Severity: important Tags: security upstream Forwarded: https://www.redhat.com/archives/libvir-list/2019-April/msg00339.html Hi, The following vulnerability was published for libvirt. CVE-2019-3886[0]: | An incorrect permissions check was discovered in libvirt 4.8.0 and | above. The readonly permission was allowed to invoke APIs depending on | the guest agent, which could lead to potentially disclosing unintended | information or denial of service by causing libvirt to block. I'm filling it here as well for ruther investigation. Is this only affecting versions >= 4.8.0? If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-3886 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3886 [1] https://www.redhat.com/archives/libvir-list/2019-April/msg00339.html [2] https://bugzilla.redhat.com/show_bug.cgi?id=1694880 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#926417: ITP: firmware-tomu -- Bootloader for the EFM32HG Tomu Board
Package: wnpp Severity: whislist Owner: Louis-Philippe Véronneau * Package name: firmware-tomu Version : 2.0~rc7-1 Upstream Author : Sean Cross * URL : https://github.com/im-tomu/tomu-bootloader * License : GPL-3 Description : Bootloader for the EFM32HG Tomu Board The Tomu is a tiny ARM microprocessor which fits in your USB port. It has two buttons and two LEDs! The board is fully open source and is buildable by hobbyists! Designed for 2-factor authentication, usb experiments, or anything else you can think of. This package provides the bootloader for the Tomu board to make flashing it easier. The work I've done on this package can be found here: https://salsa.debian.org/debian/firmware-tomu -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ signature.asc Description: OpenPGP digital signature
Bug#887042: updated repo link
looks like the work in making a buildable branch was lost when github was lost. the new link is at : https://salsa.debian.org/themusicgod1-guest/py-async_lru
Bug#926416: ITP: conda -- OS-agnostic, system-level binary package manager and ecosystem
Package: wnpp Severity: wishlist Subject: ITP: conda -- OS-agnostic, system-level binary package manager and ecosystem Package: wnpp Owner: Andreas Tille Severity: wishlist * Package name: conda Version : 4.6.10 Upstream Author : xx-20yy * URL : https://conda.io/ * License : Programming Lang: Python Description : OS-agnostic, system-level binary package manager and ecosystem Conda is a cross-platform, language-agnostic binary package manager. It is the package manager used by Anaconda installations, but it may be used for other systems as well. Conda makes environments first-class citizens, making it easy to create independent environments even for C libraries. Remark: This package is maintained by Debian Med Packaging Team at https://salsa.debian.org/med-team/conda
Bug#926409: lintian: autopkgtest takes very long to finish
On Thu, Apr 4, 2019 at 12:19 PM Chris Lamb wrote: > > Felix Lechner wrote: > > > About 95% of the time is spent building packages, even though they > > almost never change. The tests would run much faster if we shipped > > pre-built packages. > > Another way to accomplish this could be that we could cache/store them > across autopkgtest runs? IIRC (at least) Gitlab supports caching stuff > like this. > Upon reflection, each test should be packaged separately. That way I no longer have to worry about using chroot to build tests with potentially conflicting build dependencies.
Bug#925982: pretty useless without local_scan
On Thu, Apr 04, 2019 at 07:08:53PM +0200, Andreas Metzler wrote: > On 2019-04-03 Adam Borowski wrote: > > (Justification: exim is nearly completely useless for receiving mails for > > an Internet domain -- there's ~100 spams per day per address.) > > > I've wasted time concurrently coming up with Andreas' findings -- and > > indeed, rebuilding with HAVE_LOCAL_SCAN=yes makes spam filtering work again. > > I am yet undecided whether it is better to hotfix this bug or do the > right thing and drop the dynamic local_scan patch and adding a > Breaks: sa-exim Well, but in that case, what are we supposed to use for spam filtering? I did not have the time to look at alternatives. and probably same applies to many other people for whom keeping a mail server running is not a primary task. Just "apt install exim4 sa-exim" is/was a nice instant setup, requiring no maintenance other than some adjustments to handle whatever new spam campaign some miscreants launched. On today's Internet, a receiving MTA without spam filtering is simply not an option. > sa-exim is dead upstream since 2006 and seems to be really broken > now. See > https://lists.exim.org/lurker/message/20180726.113354.6d03efde.en.html Haven't seen this -- and I'm using btrfs on all machines I control. > and #879687 Seems like I have "chunking_advertise_hosts =" on my primary server but I don't recall configuring it manually -- so no idea where it came from. Installing buster's exim4 on a fresh container doesn't have this setting -- regression? Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Did ya know that typing "test -j8" instead of "ctest -j8" ⢿⡄⠘⠷⠚⠋⠀ will make your testsuite pass much faster, and fix bugs? ⠈⠳⣄
Bug#926337: unblock: notary/0.6.1~ds1-3
Control: tags -1 moreinfo Hi, On Thu, Apr 04, 2019 at 01:00:00AM +0800, Shengjing Zhu wrote: > Please unblock package notary > > * Regenerate some test certs since they are expired (Closes: #924119) > > unblock notary/0.6.1~ds1-3 The build failed on mips. This will block migration, even if the package is unblocked. https://buildd.debian.org/status/package.php?p=notary Ivo
Bug#926328: [Pkg-utopia-maintainers] Bug#926328: network-manager-gnome: nm-applet crashes with a coredump when try to create a new WiFi network
在 2019-04-03三的 18:06 +0200，Michael Biebl写道：
> Am 03.04.19 um 17:15 schrieb Jiang Jun:
> > Package: network-manager-gnome
> > Version: 1.8.20-1
> > Severity: normal
> >
> > Dear Maintainer,
> >
> > I am experiencing a crash every time I try to create a hot-spot WiFi using
> > nm-
> > applet menu. The steps were:
> >
> > 1. Click nm-applet(I am using Xfce4 and xfce-panel, BTW), in the drop down
> > menu, click Creat New WiFi Network...
> > 2. In the pop up window, fill in Network Name and Key.
> > 3. In the WiFi security drop down menu, select None or WEP 128bit
> > Passphrase or
> > WEP 40/128, doesn't matter, the result will be the same (a crash).
> > 4. Click Create. And nm-applet will disappear from the panel Notification
> > Area.
> >
> > In journalctl you'll see: https://cfp.vim-cn.com/cbfwN
> >
> >
> > And there will be a new coredump in coredumpctl list like:
> >
> > Wed 2019-04-03 23:06:44 CST 19318 1000 1000 6 present /usr/bin/nm-
> > applet
> >
> > coredumpctl info shows this: https://cfp.vim-cn.com/cbfwP
>
> Please install the dbgsym packages to get a more meaningful backtrace.
>
> https://wiki.debian.org/HowToGetABacktrace
(gdb) bt full
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
set = {__val = {0, 140737488338656, 93824995100192, 140737338632479,
206158430232, 140737488338336, 140737488338144, 3183187818398167296, 16,
140737337394940, 0, 93824995100192, 0, 93824992545728, 8, 16}}
pid =
tid =
ret =
#1 0x76e2a535 in __GI_abort () at abort.c:79
save_stage = 1
act = {__sigaction_handler = {sa_handler = 0x7fffbee0,
sa_sigaction = 0x7fffbee0}, sa_mask = {__val = {140737337714966,
93824995199008, 140737338535127, 140737488338832, 140737488338688,
93825001527808, 140737338708600, 0, 140737338547241, 4607182418800017408,
140737488338624, 140737488338656, 93824994476944, 4294967296, 140737488338672,
140737488338928}}, sa_flags = -16656, sa_restorer = 0x1000}
sigs = {__val = {32, 0 }}
#2 0x76e81778 in __libc_message (action=action@entry=do_abort,
fmt=fmt@entry=0x76f8c28d "%s\n") at ../sysdeps/posix/libc_fatal.c:181
ap = {{gp_offset = 24, fp_offset = 21845, overflow_arg_area =
0x7fffc000, reg_save_area = 0x7fffbf90}}
fd = 2
list =
nlist =
cp =
written =
#3 0x76e87e6a in malloc_printerr (str=str@entry=0x76f8dff8
"double free or corruption (out)") at malloc.c:5341
No locals.
#4 0x76e89980 in _int_free (av=0x76fc3c40 ,
p=0x7fffe404c6f0, have_lock=) at malloc.c:4306
size = 93824993664576
fb =
nextchunk = 0xd555396fe530
nextsize =
nextinuse =
prevsize =
bck =
fwd =
__PRETTY_FUNCTION__ = "_int_free"
#5 0x77f57938 in nma_wifi_dialog_get_connection () from /lib/x86_64-
linux-gnu/libnma.so.0
No symbol table info available.
#6 0x55574b2d in wifi_dialog_response_cb (foo=0x55c9c450,
response=-5, user_data=0x558c61c0) at src/applet-device-wifi.c:1464
dialog = 0x55c9c450
applet = 0x558c61c0
connection = 0x0
fuzzy_match = 0x0
device = 0x0
ap = 0x0
all =
i =
__func__ = "wifi_dialog_response_cb"
#7 0x77119c7d in g_closure_invoke (closure=0x55e16720,
return_value=0x0, n_param_values=2, param_values=0x7fffc340,
invocation_hint=0x7fffc2c0) at ../../../gobject/gclosure.c:810
marshal = 0x7711c0a0
marshal_data = 0x0
in_marshal = 0
real_closure = 0x55e16700
__FUNCTION__ = "g_closure_invoke"
#8 0x7712d345 in signal_emit_unlocked_R (node=node@entry=0x557510
80, detail=detail@entry=0, instance=instance@entry=0x55c9c450,
emission_return=emission_return@entry=0x0,
instance_and_params=instance_and_params@entry=0x7fffc340) at
../../../gobject/gsignal.c:3635
tmp =
handler = 0x55dfc640
accumulator = 0x0
emission = {next = 0x7fffc710, instance = 0x55c9c450, ihint =
{signal_id = 180, detail = 0, run_type = G_SIGNAL_RUN_FIRST}, state =
EMISSION_RUN, chain_type = 4}
class_closure = 0x55759170
hlist =
handler_list = 0x55dfc640
return_accu = 0x0
accu = {g_type = 0, data = {{v_int = 0, v_uint = 0, v_long = 0,
v_ulong = 0, v_int64 = 0, v_uint64 = 0, v_float = 0, v_double = 0, v_pointer =
0x0}, {v_int = 0, v_uint = 0, v_long = 0, v_ulong = 0, v_int64 = 0, v_uint64 =
0, v_float = 0, v_double = 0, v_pointer = 0x0}}}
signal_id = 180
max_sequential_handler_number = 2310
return_value_altered = 0
#9 0x7713625e in g_signal_emit_valist (instance=,
signal_id=, detail=, var_args=var_args@entry=0x7
fffc510) at ../../../gobject/gsignal.c:3391
instance_and_params = 0x7fffc340
signal_return_type =
Bug#926302: unblock: ciftilib/1.5.3-2
Control: tags -1 moreinfo Hi Andreas, On Wed, Apr 03, 2019 at 08:40:59AM +0200, Andreas Tille wrote: > Please unblock package ciftilib You included the diff between 1.5.3-1 and 1.5.3-2. However, testing currently has 1.5.1-3. The diff beween 1.5.1-3 and 1.5.3-2 is much bigger, and doesn't look like something that is acceptable during the freeze. Version 1.5.3-1 didn't migrate due to the missing builds (which are fixed by the patch in -2). Ivo
Bug#884796: update repo link
looks like the work in making a debian packaging branch was lost when github was lost. https://salsa.debian.org/themusicgod1-guest/py-evm is what remains
Bug#926409: lintian: autopkgtest takes very long to finish
On Thu, Apr 4, 2019 at 11:24 AM Balint Reczey wrote: > > One criterion that came to my mind is filtering by severity, including > errors for sure, but not pedantic ones. The pedantic setting may become the default for tests, but very little time is spent running Lintian. Things may speed up a little if we run only the checks being tested (using the '-C' option), but that won't make much of a difference in the overall run time of the tests, which is primarily spent building packages.
Bug#926409: lintian: autopkgtest takes very long to finish
Balint Reczey wrote: > One criterion that came to my mind is filtering by severity, including > errors for sure, but not pedantic ones. Mmm, unfortunately I think we would still want to know if, for example, the runtime toolchain changes such that a pedantic tag changes behaviour. :( Felix Lechner wrote: > About 95% of the time is spent building packages, even though they > almost never change. The tests would run much faster if we shipped > pre-built packages. Another way to accomplish this could be that we could cache/store them across autopkgtest runs? IIRC (at least) Gitlab supports caching stuff like this. Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org chris-lamb.co.uk `-
Bug#926409: lintian: autopkgtest takes very long to finish
On Thu, Apr 4, 2019 at 10:42 AM Chris Lamb wrote: > > * I'm not sure *how* we can speed up the tests. I mean, they all >essentially involve building Debian packages with all the usual >debhelper calls, etc. Speeding *this* up is somewhat out-of-scope >of this Lintian wishlist issue, alas. > > However, perhaps Felix has some input here as he has been doing a lot > of work on the test suite recently? About 95% of the time is spent building packages, even though they almost never change. The tests would run much faster if we shipped pre-built packages. One way to accomplish that would be to package the tests separately.
Bug#827861: Please add coq-8.5 to jessie-backports
Control: tags 827861 wontfix jessie has entered LTS, and LTS distributions no longer receive backports (see https://backports.debian.org/news/stretch-backports/), so this almost certainly isn’t going to happen.
Bug#926415: unblock: debian-edu-config/2.10.64
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package debian-edu-config, it fixes three important bugs.
These changes also only affect Debian Edu:
$ debdiff debian-edu-config_2.10.63.dsc debian-edu-config_2.10.64.dsc
diff -Nru debian-edu-config-2.10.63/debian/changelog
debian-edu-config-2.10.64/debian/changelog
--- debian-edu-config-2.10.63/debian/changelog 2019-03-21 12:57:41.0
+0100
+++ debian-edu-config-2.10.64/debian/changelog 2019-04-02 10:54:26.0
+0200
@@ -1,3 +1,16 @@
+debian-edu-config (2.10.64) unstable; urgency=medium
+
+ [ Wolfgang Schweer ]
+ * etc/ltsp/ltsp-build-client.conf: Add DIST="buster". (Closes: #926183)
+- Make sure the LTSP chroot installation works for all possible scenarios.
+ * cf3/cf.finalize: Use XDG instead of desktop-profiles. (Closes: #926184)
+- Make sure desktop-profiles are disabled and use XDG as a more general
+ approach. This is needed for LXQt to work without user interaction.
+ * tools/gosa-sync-dns-nfs: Make tool more robust. (Closes: #926186)
+- Invalidate the nscd netgroup cache to make NFS homedir mount more robust.
+
+ -- Holger Levsen Tue, 02 Apr 2019 10:54:26 +0200
+
debian-edu-config (2.10.63) unstable; urgency=medium
[ Wolfgang Schweer ]
diff -Nru debian-edu-config-2.10.63/cf3/cf.finalize
debian-edu-config-2.10.64/cf3/cf.finalize
--- debian-edu-config-2.10.63/cf3/cf.finalize 2019-02-15 11:58:02.0
+0100
+++ debian-edu-config-2.10.64/cf3/cf.finalize 2019-04-02 10:53:51.0
+0200
@@ -14,13 +14,44 @@
link_from => ln_s("/usr/share/debian-edu-config/lightdm-gtk-greeter.conf"),
move_obstructions => "true";
- # Make sure menu overrides are enabled in each case.
+ # Make sure desktop-profiles are disabled, use XDG instead for all DEs. This
+ # more general approach is needed because otherwise the user is prompted to
+ # set up the LXQt session manually (x-window-manager, panel config) now that
+ # lxqt depends on the 'lxqt-branding-debian' package.
debian.installation::
"/etc/default/desktop-profiles"
edit_line => profile;
+"/etc/xdg/menus/applications-merged"
+link_from => ln_s("/usr/share/debian-edu/menu/menus/applications-merged"),
+move_obstructions => "true";
+
+"/etc/xdg/menus/gnome-applications.menu"
+link_from =>
ln_s("/usr/share/debian-edu/menu/menus/gnome-applications.menu"),
+move_obstructions => "true";
+
+"/etc/xdg/menus/kf5-applications.menu"
+link_from =>
ln_s("/usr/share/debian-edu/menu/menus/kf5-applications.menu"),
+move_obstructions => "true";
+
+"/etc/xdg/menus/lxde-applications.menu"
+link_from =>
ln_s("/usr/share/debian-edu/menu/menus/lxde-applications.menu"),
+move_obstructions => "true";
+
+"/etc/xdg/menus/lxqt-applications.menu"
+link_from =>
ln_s("/usr/share/debian-edu/menu/menus/lxqt-applications.menu"),
+move_obstructions => "true";
+
+"/etc/xdg/menus/mate-applications.menu"
+link_from =>
ln_s("/usr/share/debian-edu/menu/menus/mate-applications.menu"),
+move_obstructions => "true";
+
+"/etc/xdg/menus/xfce-applications.menu"
+link_from =>
ln_s("/usr/share/debian-edu/menu/menus/xfce-applications.menu"),
+move_obstructions => "true";
+
commands:
debian.server.installation::
@@ -73,7 +104,9 @@
replace_patterns:
- "PERSONALITY=polite" replace_with => value("PERSONALITY=rude");
+ "PERSONALITY=polite" replace_with => value("PERSONALITY=sheep");
+ # Needed if upgrading from 10+edu~a0
+ "PERSONALITY=rude" replace_with => value("PERSONALITY=sheep");
}
bundle agent editline_finalize
diff -Nru debian-edu-config-2.10.63/etc/ltsp/ltsp-build-client.conf
debian-edu-config-2.10.64/etc/ltsp/ltsp-build-client.conf
--- debian-edu-config-2.10.63/etc/ltsp/ltsp-build-client.conf 2019-02-15
11:58:02.0 +0100
+++ debian-edu-config-2.10.64/etc/ltsp/ltsp-build-client.conf 2019-04-01
19:49:41.0 +0200
@@ -15,3 +15,5 @@
# Set the next entry if the sources.list file should be copied from the server
# instead of being generated at chroot installation time.
#COPY_SOURCES_LIST="True"
+
+DIST="buster"
diff -Nru
debian-edu-config-2.10.63/share/debian-edu-config/tools/gosa-sync-dns-nfs
debian-edu-config-2.10.64/share/debian-edu-config/tools/gosa-sync-dns-nfs
--- debian-edu-config-2.10.63/share/debian-edu-config/tools/gosa-sync-dns-nfs
2014-09-04 21:01:59.0 +0200
+++ debian-edu-config-2.10.64/share/debian-edu-config/tools/gosa-sync-dns-nfs
2019-04-01 19:49:41.0 +0200
@@ -2,9 +2,11 @@
#
# Update DNS and NFS export when a new host is created, to allow
# changes in DNS and netgroup membership to take effect imediately.
+# Invalidate the nscd netgroup cache to make NFS homedir mounting more robust.
PATH=/usr/sbin:/sbin:$PATH
export PATH
su -s /bin/sh -c "PATH=$PATH /usr/sbin/ldap2bind" bind
exportfs -a
+nscd -i netgroup
unblock
Bug#892503: tmux: display garbling with nested sessions
Package: tmux Version: 2.3-4 Followup-For: Bug #892503 (Note that I'm reporting the bug as found in the older tmux that is the outer tmux of a tmux-in-tmux situation, though the proposed work-around is to be applied to the newer tmux that is the inner tmux. This is to (hopefully) properly mark the problem as being with the older tmux, as it was reported before that the bug vanishes with tmux >= 2.6 as outer tmux.) Hi, the tmux-in-tmux screen garbling hit me, too. It was also with an outer tmux 2.3 (in my case: 2.3-4) from stable, and a newer inner tmux (in my case: 2.8-3) from testing (buster). On IRC, upstream suggested the work-around to do this in the inner tmux: set -as terminal-overrides ',*:indn@' Then, detach and attach again. This seems to have fixed it, for me. Apparently this cancels the capability "scroll forward #1 lines" for all terminal types. It's not needed in any further inner tmuxes. Regards, Fabian -- Fabian "canvon" Pietsch - https://www.canvon.de/
Bug#923181: Please add support for reporting mouse button presses to console programs which support mouse trackingo
On 22/03/2019 21.33, Bill Allombert wrote:
>> I'm not sure what the best course of action is. Some possibilities are:
>> * If it isn't too much of a problem, we could just leave it how it is.
>> * We could disable selections while mouse tracking is active
>
> If this can be done on a per tty basis, this might be the best course of
> action.
Ok, I've now created patch for this. This time, I've based the patch on
the current master branch (commit
c12a8c2d0cf72a340b13b00e6d4b98bfed57ce01) of the salsa.debian.org git repo.
Regards,
Daniel Abrecht
diff --git a/src/action.c b/src/action.c
index 5c47fda..58d8af0 100644
--- a/src/action.c
+++ b/src/action.c
@@ -19,6 +19,7 @@
static double xx=1, yy=1, x0=-1, y0=-1, x1=-1, y1=-1;
static int mode = 0;
+static enum current_button button = BUTTON_RELEASED;
void
set_pointer(double x, double y)
@@ -26,6 +27,11 @@ set_pointer(double x, double y)
xx = x+1; yy = y+1;
if (xx < 1) xx = 1; else if (xx > screen_width) xx = screen_width;
if (yy < 1) yy = 1; else if (yy > screen_height) yy = screen_height;
+ if (mouse_reporting != MOUSE_REPORTING_OFF)
+ {
+x0 = -1; y0 = -1;
+mode = 0;
+ }
if (x0 >= 0 && y0 >= 0)
select_region((int)xx,(int)yy,(int)x0,(int)y0);
else
@@ -55,6 +61,11 @@ move_pointer(double x, double y)
xx += x/20; yy += y/20;
if (xx < 1) xx = 1; else if (xx > screen_width) xx = screen_width;
if (yy < 1) yy = 1; else if (yy > screen_height) yy = screen_height;
+ if (mouse_reporting != MOUSE_REPORTING_OFF)
+ {
+x0 = -1; y0 = -1;
+mode = 0;
+ }
if (x0 >= 0 && y0 >= 0)
select_mode(mode,(int)xx,(int)yy,(int)x0,(int)y0);
else
@@ -64,36 +75,85 @@ move_pointer(double x, double y)
void
press_left_button(void)
{
- if ((int)x1==(int)xx && (int)y1==(int)yy)
+ if (mouse_reporting != MOUSE_REPORTING_OFF)
{
-mode = (mode+1)%3;
-select_mode(mode,(int)xx,(int)yy,(int)xx,(int)yy);
+button = BUTTON_LEFT;
+report_pointer((int)xx,(int)yy,button);
}
else
{
-mode = 0;
-select_region((int)xx,(int)yy,(int)xx,(int)yy);
+if ((int)x1==(int)xx && (int)y1==(int)yy)
+{
+ mode = (mode+1)%3;
+ select_mode(mode,(int)xx,(int)yy,(int)xx,(int)yy);
+}
+else
+{
+ mode = 0;
+ select_region((int)xx,(int)yy,(int)xx,(int)yy);
+}
+x0=xx; y0=yy; x1=x0; y1=y0;
}
- x0=xx; y0=yy; x1=x0; y1=y0;
}
void
release_left_button(void)
{
+ if (mouse_reporting == MOUSE_REPORTING_X11)
+ {
+button = BUTTON_RELEASED;
+report_pointer((int)xx,(int)yy,button);
+ }
x0=-1; y0=-1;
}
void
press_middle_button(void)
{
- paste();
+ if (mouse_reporting != MOUSE_REPORTING_OFF)
+ {
+button = BUTTON_MIDDLE;
+report_pointer((int)xx,(int)yy,button);
+ }
+ else
+ {
+paste();
+ }
+}
+
+void
+release_middle_button(void)
+{
+ if (mouse_reporting == MOUSE_REPORTING_X11)
+ {
+button = BUTTON_RELEASED;
+report_pointer((int)xx,(int)yy,button);
+ }
}
void
press_right_button(void)
{
- if (x1>=0 && y1>=0)
-select_region((int)xx,(int)yy,(int)x1,(int)y1);
+ if (mouse_reporting != MOUSE_REPORTING_OFF)
+ {
+button = BUTTON_RIGHT;
+report_pointer((int)xx,(int)yy,button);
+ }
+ else
+ {
+if (x1>=0 && y1>=0)
+ select_region((int)xx,(int)yy,(int)x1,(int)y1);
+ }
+}
+
+void
+release_right_button(void)
+{
+ if (mouse_reporting == MOUSE_REPORTING_X11)
+ {
+button = BUTTON_RELEASED;
+report_pointer((int)xx,(int)yy,button);
+ }
}
void
diff --git a/src/consolation.h b/src/consolation.h
index f907906..5290d65 100644
--- a/src/consolation.h
+++ b/src/consolation.h
@@ -19,14 +19,30 @@
extern int nodaemon;
+enum current_button {
+ BUTTON_LEFT,
+ BUTTON_MIDDLE,
+ BUTTON_RIGHT,
+ BUTTON_RELEASED
+};
+
+enum mouse_reporting_mode {
+ MOUSE_REPORTING_OFF,
+ MOUSE_REPORTING_X10,
+ MOUSE_REPORTING_X11,
+ MOUSE_REPORTING_MODE_COUNT
+};
+
/* global state */
extern unsigned int screen_width;
extern unsigned int screen_height;
+extern enum mouse_reporting_mode mouse_reporting;
/* selection.c */
-void set_screen_size(void);
+void set_screen_size_and_mouse_reporting(void);
+void report_pointer(int x, int y, enum current_button button);
void draw_pointer(int x, int y);
void select_region(int x, int y, int x2, int y2);
void select_words(int x, int y, int x2, int y2);
@@ -42,7 +58,9 @@ void move_pointer(double x, double y);
void press_left_button(void);
void release_left_button(void);
void press_middle_button(void);
+void release_middle_button(void);
void press_right_button(void);
+void release_right_button(void);
void vertical_axis(double v);
/* input.c */
diff --git a/src/input.c b/src/input.c
index 74ec072..4a6f99a 100644
--- a/src/input.c
+++ b/src/input.c
@@ -46,6 +46,7 @@
int nodaemon = false;
unsigned int screen_width;
unsigned int screen_height;
+enum mouse_reporting_mode mouse_reporting = MOUSE_REPORTING_OFF;
static struct tools_options options;
static unsigned int
Bug#926409: lintian: autopkgtest takes very long to finish
Hi Chris, On Thu, Apr 4, 2019 at 7:30 PM Chris Lamb wrote: > > tags 926409 + moreinfo > thanks > > Hi Balint, > > > Lintian has a lot of tests which is great for coverage, but maybe some > > of them could be skipped in autopkgtest runs. > > Interesting. I guess I would have three follow-up questions here: > > * On what criterion or criteria could we include or exclude tests >from the autopkgtest runs? Whilst we could skip the unit tests (as >these are "just" Perl that is unlikely to vary) the most >interesting ones to run in terms of detecting regressions in an >real-world environment (the entire point of autopkgtests from my >point of view) would be the tests of the checks themselves and >these likely constitute the vast majority of the total time. One criterion that came to my mind is filtering by severity, including errors for sure, but not pedantic ones. The full suite can run during the build thus we don't loose a lot of coverage. I hoped to rely on Lintian maintainer's judgement about what to omit. > * I'm not sure *how* we can speed up the tests. I mean, they all >essentially involve building Debian packages with all the usual >debhelper calls, etc. Speeding *this* up is somewhat out-of-scope >of this Lintian wishlist issue, alas. A profiling round with perf would point out a few things IMO, but as a start I did a timestamped run here to find slowest tests: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco-rbalint-scratch/disco/arm64/l/lintian/20190404_002129_96f0c@/log.gz If there many package builds in the tests just changing the faster compression helps, a lot with little effort (until zstd becomes the default ;-)). > * Why not simply increase Ubuntu's timeout? I would concede this is >not the best use of CI resources, but the trade-off with "human" >time would appear to be worth it here. I agree, and we may increase the timeout, but the running the tests seems to take longer in general than seems reasonable. Cheers, Balint > However, perhaps Felix has some input here as he has been doing a lot > of work on the test suite recently? > > > Best wishes, > > -- > ,''`. > : :' : Chris Lamb > `. `'` la...@debian.org chris-lamb.co.uk >`- -- Balint Reczey Ubuntu & Debian Developer
Bug#926345: isync: Fails to sync Maildir++ subfolders after initial sync
Ah, that string must be coming from mswatch. I forgot that that's the program actually kicking off multiple rounds of mbsync. Perhaps the bug is over there? -- Nik On Thu, Apr 04, 2019 at 07:24:59PM +0200, Oswald Buddenhagen wrote: > On Wed, Apr 03, 2019 at 03:19:57PM -0400, Nik A. Melchior wrote: > > + mbsync hostname:lists.ip > > Maildir error: store 'local', folder 'lists.ip': SubFolders style Maildir++ > > does not support dots in mailbox names > > > you need to use the canonical mailbox name, so hostname:lists/ip >
Bug#926414: python3-grapefruit: Can't load python3-grapefruit under python 3.7.3
Package: python3-grapefruit Version: 0.1~a3+dfsg-6 Severity: important bpython version 0.17.1 on top of Python 3.7.3 /usr/bin/python3 >>> import grapefruit Traceback (most recent call last): File "", line 1, in import grapefruit File "/usr/lib/python3/dist-packages/bpython/curtsiesfrontend/repl.py", line 251, in load_module module = self.loader.load_module(name) File "/usr/lib/python3/dist-packages/grapefruit.py", line 22, in from past.builtins import xrange ModuleNotFoundError: No module named 'past' -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-grapefruit depends on: ii python33.7.3-1 ii python3-pkg-resources 40.8.0-1 python3-grapefruit recommends no packages. Versions of packages python3-grapefruit suggests: pn python-grapefruit-doc -- no debconf information
Bug#926413: unblock: simbody/3.6.1+dfsg-7
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock simbody 3.6.1+dfsg-7. The new upload was made to solve
https://bugs.debian.org/926358 , an RC bug that causes upgrade failure from
Debian 9.
The full diff is pasted here.
--
Regards,
Boyuan Yang
diff --git a/debian/changelog b/debian/changelog
index 2998081..cb3d34d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+simbody (3.6.1+dfsg-7) unstable; urgency=high
+
+ * Team upload.
+ * libsimbody-dev: Add 'Breaks: libsimbody3.5v5' for smooth upgrades
+from stretch. (Closes: #926358)
+
+ -- Boyuan Yang Thu, 04 Apr 2019 11:47:09 -0400
+
simbody (3.6.1+dfsg-6) unstable; urgency=medium
* Add mips exclusions to the testsuite (timeout errors in buildfarm)
diff --git a/debian/control b/debian/control
index 0869337..1a525c5 100644
--- a/debian/control
+++ b/debian/control
@@ -41,6 +41,7 @@ Depends: freeglut3-dev,
liblapack-dev,
libsimbody3.6 (= ${binary:Version}),
${misc:Depends}
+Breaks: libsimbody3.5v5
Multi-Arch: same
Description: SimTK multibody dynamics API - development files
Simbody is a SimTK toolset providing general multibody dynamics capability,
signature.asc
Description: This is a digitally signed message part
Bug#926412: unblock: gnutls28/3.6.7-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package gnutls28. This is a upstream bugfix release featuring two security fixes + Fixes a memory corruption (double free) vulnerability in the certificate verification API. https://gitlab.com/gnutls/gnutls/issues/694 CVE-2019-3829 GNUTLS-SA-2019-03-27 + Fixes an invalid pointer access via malformed TLS1.3 async messages; https://gitlab.com/gnutls/gnutls/issues/704 CVE-2019-3836 GNUTLS-SA-2019-03-27 One of these is fixed by a hardening measure (gnutls_free() will automatically set the free'd pointer to NULL.) It also unbreaks vlc (#922879) and has some TLS1.3 related changes. The straight debdiff is huge, because of a) usual release updates of autogenerated files and b) because it includes a global 's/http:/https:/'. Stripped down debdiff is attached. unblock gnutls28/3.6.7-2 cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' smaller.debdiff.diff.xz Description: application/xz signature.asc Description: PGP signature
Bug#926409: lintian: autopkgtest takes very long to finish
tags 926409 + moreinfo thanks Hi Balint, > Lintian has a lot of tests which is great for coverage, but maybe some > of them could be skipped in autopkgtest runs. Interesting. I guess I would have three follow-up questions here: * On what criterion or criteria could we include or exclude tests from the autopkgtest runs? Whilst we could skip the unit tests (as these are "just" Perl that is unlikely to vary) the most interesting ones to run in terms of detecting regressions in an real-world environment (the entire point of autopkgtests from my point of view) would be the tests of the checks themselves and these likely constitute the vast majority of the total time. * I'm not sure *how* we can speed up the tests. I mean, they all essentially involve building Debian packages with all the usual debhelper calls, etc. Speeding *this* up is somewhat out-of-scope of this Lintian wishlist issue, alas. * Why not simply increase Ubuntu's timeout? I would concede this is not the best use of CI resources, but the trade-off with "human" time would appear to be worth it here. However, perhaps Felix has some input here as he has been doing a lot of work on the test suite recently? Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org chris-lamb.co.uk `-
Bug#926345: isync: Fails to sync Maildir++ subfolders after initial sync
On Wed, Apr 03, 2019 at 03:19:57PM -0400, Nik A. Melchior wrote: > + mbsync hostname:lists.ip > Maildir error: store 'local', folder 'lists.ip': SubFolders style Maildir++ > does not support dots in mailbox names > you need to use the canonical mailbox name, so hostname:lists/ip
Bug#923891: Attachments also broken
I just noticed that attaching files to issues is currently broken. I haven't spent enough time to dig into the problem, so I don't know if was caused by this issue, caused by a different issue, or caused by the workaround of replacing /app and /public from the upstream tarball. -- Soren Stoutner Small Business Tech Solutions so...@smallbusinesstech.net 623-262-6169
Bug#925982: pretty useless without local_scan
On Thu, Apr 04, 2019 at 07:08:53PM +0200, Andreas Metzler wrote: > I am yet undecided whether it is better to hotfix this bug or do the > right thing and drop the dynamic local_scan patch and adding a > Breaks: sa-exim > > sa-exim is dead upstream since 2006 and seems to be really broken > now. See > https://lists.exim.org/lurker/message/20180726.113354.6d03efde.en.html > and #879687 I would vouch for the Breaks: _and_ a mention in the Release notes. Exim is still Debian's default MTA, isn't it? Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
Bug#926411: Export to json/xml doesn't work
Package: nftables
Version: 0.9.0-2
Severity: normal
Hello,
according to the nft man page, it is possible to export current ruleset
to JSON or XML format using this command:
nft export [ruleset] format
where format is a mandatory parameter and "may be either xml or json".
Using
the export command without format indeed raises an error:
# nft export
Error: syntax error, unexpected newline, expecting ruleset or xml or
json or vm
However, adding the format does not work either:
# nft export json
Error: this output type is not supported
This used to work in nftables 0.7-1 in Stretch (example with no rules
present)
# nft export json
{"nftables":[]}
Export to JSON allows automated processing of the ruleset and it would
be nice
to have it functional. Or - if the current state is not a regression but
an intentional change - it should be reflected in the man page.
Thanks
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores)
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: sysvinit (via /sbin/init)
Versions of packages nftables depends on:
ii dpkg 1.19.5
ii libc6 2.28-8
ii libgmp10 2:6.1.2+dfsg-4
ii libjansson4 2.12-1
ii libnftables0 0.9.0-2
ii libreadline7 7.0-5
nftables recommends no packages.
nftables suggests no packages.
-- no debconf information
Bug#926116: cross build failing - update-binfmts: warning: qemu-i386 not in database of installed binary formats.
No more issues since I upgraded to buster. mmdebstrap is awesome! Thank you! Cheers, Patrick
Bug#926311: soundscaperenderer-nox: leaves alternatives after upgrade and purge: /usr/bin/ssr-*
Followup-For: Bug #926311 Control: severity -1 serious Hi, the handling of the alternatives seems to be broken, which probably makes the package unusable: Setting up soundscaperenderer-nox (0.5.0~dfsg-3) ... cat: /usr/share/soundscaperenderer-nox/alternatives: No such file or directory Removing soundscaperenderer-nox (0.5.0~dfsg-3) ... cat: /usr/share/soundscaperenderer-nox/alternatives: No such file or directory The install/remove actions don't fail, but no alternatives are set up after installation. Andreas
Bug#925982: pretty useless without local_scan
On 2019-04-03 Adam Borowski wrote: > Control: severity -1 important > (Justification: exim is nearly completely useless for receiving mails for > an Internet domain -- there's ~100 spams per day per address.) > I've wasted time concurrently coming up with Andreas' findings -- and > indeed, rebuilding with HAVE_LOCAL_SCAN=yes makes spam filtering work again. Hello, I am yet undecided whether it is better to hotfix this bug or do the right thing and drop the dynamic local_scan patch and adding a Breaks: sa-exim sa-exim is dead upstream since 2006 and seems to be really broken now. See https://lists.exim.org/lurker/message/20180726.113354.6d03efde.en.html and #879687 cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#926410: general: report general status
Package: general Severity: wishlist Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Distributor ID: Devuan Description:Devuan GNU/Linux 9 (n/a) Release:9 Codename: n/a Architecture: i686 Kernel: Linux 4.9.166-0409166-generic (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init)
Bug#926260: debian-history: DebConf2 mistakenly referred to as the second DebConf
On Fri, Apr 05, 2019 at 01:02:13AM +0900, Osamu Aoki wrote:
> * definitive reference information. I.e., PROOF.
>("My understanding" is too weak.)
> * Endorsement by DEBCONF active organizer is nice to have as a
>supporting evidence.
I'm "just" a former organizer but I can 100% assure you, that DebConf0
was the 0th Debconf, Debconf1 was the first one, etc - if you start
counting at 0.
;)
However, if you start counting at 1, DebConf0 in 2000 was the first
DebConf, DebConf1 in 2001 was the 2nd DebConf, [...], DebConf18 in
2018 was the 19th DebConf and this year the 20th DebConf will take place
as DebConf19 in Brasil.
It's confusing.
For referenence:
https://debconf1.debconf.org/ says: "The Debian people start counting
from zero. Debian Conference 1 was the second big international meeting
for this voluntary, at the same time anarchistic but focused group of
developers."
Also, see https://debconf0.debconf.org/ - look at the title of that
page! https://debconf2.debconf.org does not exist, while the rest is
there too.
HTH.
--
tschau,
Holger
---
holger@(debian|reproducible-builds|layer-acht).org
PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C
Dance like no one's watching. Encrypt like everyone is.
signature.asc
Description: PGP signature
Bug#926409: lintian: autopkgtest takes very long to finish
Package: lintian Version: 2.11.0 Severity: wishlist Hi, Lintian has a lot of tests which is great for coverage, but maybe some of them could be skipped in autopkgtest runs. Currently autopkgtest takes ~1 wall clock hours on Debian's amd64 CI [1], but Ubuntu runs autopkgtest on all architectures and arm64 runs for example take more than 3 hours [2]. Setting the tests to run in parallel helps with the wall clock time, but still this may not be the best use of CI CPU resources or if all tests are needed, maybe lintian itself could be sped up a bit. Cheers, Balint [1] https://ci.debian.net/packages/l/lintian/unstable/amd64/ [2] http://autopkgtest.ubuntu.com/packages/l/lintian/disco/arm64 -- Balint Reczey Ubuntu & Debian Developer
Bug#915030: virt-viewer: leaves alternatives after purge: /usr/bin/spice-xpi-client
Followup-For: Bug #915030 Control: tag -1 patch Hi, attached is a tested patch the takes care of removing the alternative on upgrades from stretch to buster. I'm considering doing a NMU got get this fixed for buster. Andreas diff -Nru virt-viewer-7.0/debian/changelog virt-viewer-7.0/debian/changelog --- virt-viewer-7.0/debian/changelog2018-09-06 21:57:54.0 +0200 +++ virt-viewer-7.0/debian/changelog2019-04-04 16:56:48.0 +0200 @@ -1,3 +1,11 @@ +virt-viewer (7.0-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Remove obsolete /usr/bin/spice-xpi-client alternative on upgrades. +(Closes: #915030) + + -- Andreas Beckmann Thu, 04 Apr 2019 16:56:48 +0200 + virt-viewer (7.0-1) unstable; urgency=medium * [62b4ac8] New upstream version 7.0 diff -Nru virt-viewer-7.0/debian/postinst virt-viewer-7.0/debian/postinst --- virt-viewer-7.0/debian/postinst 1970-01-01 01:00:00.0 +0100 +++ virt-viewer-7.0/debian/postinst 2019-04-04 16:56:48.0 +0200 @@ -0,0 +1,10 @@ +#!/bin/sh +set -e + +# remove obsolete alternative from stretch +if [ "$1" = "configure" ] ; then +update-alternatives --remove spice-xpi-client \ + /usr/bin/spice-xpi-client-remote-viewer +fi + +#DEBHELPER#
Bug#924591: fastboot format:ext4 misses /usr/lib/android-sdk/platform-tools/mke2fs
Control: reopen -1 Hello, Hans-Christoph Steiner: > circular Depends:/Recommends: are easy, circular Build-Depends: are > what's hard. Plus using the /usr/bin/ method, that will make fastboot > require e2fsprogs and other packages, rather than just recommend. Unfortunately, the bug is not really fixed. The symlinks exist now, but apparently /usr/bin/mke2fs doesn't work for fastboot format: $ fastboot format:ext4:0xcd3771e00 userdata Warning: userdata size is0xcd3779e00, but 0xcd3771e00 was requested for formatting. Invalid erase-block-size 512: must be a power of 2 and at least 4096. Invalid logical-block-size 512: must be a power of 2 and at least 4096. mke2fs 1.44.5 (15-Dec-2018) /tmp/TemporaryFile-YMROG8: Unimplemented ext2 library function while setting up superblock /usr/lib/android-sdk/platform-tools/mke2fs failed with status 1 mke2fs failed: 1 error: Cannot generate image for userdata Cheers, jonas signature.asc Description: OpenPGP digital signature
Bug#926342: libprotobuf17: I was forced to download libprotobuf17 on this site: https://packages.debian.org/buster/amd64/libprotobuf17/download
Control: tags -1 +moreinfo On Wed, Apr 3, 2019 at 9:15 PM Gilles CHARABOT wrote: > I wanted to update libphonenumber7 but I couldn't, I was blocked with > libprotobuf10. I have then download libprotobuf17 directly on this website > https://packages.debian.org/buster/amd64/libprotobuf17/download and then I > could update libphonenumber7. > Today, several months after I performed this operation, there is now no > candidate version for libprotobuf17 in Buster. There is [1]. Something wrong with your setup. > # apt-cache policy libprotobuf17 > libprotobuf17: > Installé : 3.6.1.3-1 > Candidat : (aucun) > Table de version : > *** 3.6.1.3-1 -3 > 500 http://ftp.de.debian.org/debian buster/main amd64 Packages > 100 /var/lib/dpkg/status This seems wrong. Your network mirror has priority 500 but somehow the package priority went to -3. :-? Anything below zero means do not install. Do you use pinning? What's in /etc/apt/preferences and/or under /etc/apt/preferences.d/ ? How your sources.list looks like and what's the output of 'apt update'? Do you have libprotobuf10 installed? Regards, Laszlo/GCS [1] http://ftp.de.debian.org/debian/pool/main/p/protobuf/
Bug#920530: apparmor: Apparmour breaks bind/named DLZ with samba
Steven Monai writes: >So far, my buster Samba AD controller appears to be working correctly with the >'usr.sbin.named' profile in 'complain' mode. I will monitor the logs for a >while to see if any further apparmor-related issues appear during my testing. Some new apparmor "complaint" logs regarding the 'usr.sbin.named' profile have appeared on my buster Samba AD controller. Here are two representative log lines: Apr 3 14:25:40 dc1 kernel: [19735.831647] audit: type=1400 audit(1554326740.971:14): apparmor="ALLOWED" operation="file_lock" profile="/usr/sbin/named" name="/var/lib/samba/bind-dns/dns.keytab" pid=421 comm="isc-worker" requested_mask="k" denied_mask="k" fsuid=108 ouid=0 Apr 3 14:25:40 dc1 kernel: [19735.832328] audit: type=1400 audit(1554326740.971:15): apparmor="ALLOWED" operation="open" profile="/usr/sbin/named" name="/dev/urandom" pid=421 comm="isc-worker" requested_mask="wc" denied_mask="wc" fsuid=108 ouid=0 In response to the first log, I have appended the following line to '/etc/apparmor.d/local/usr.sbin.named': /var/lib/samba/bind-dns/dns.keytab k, For the second log, I am unsure how to provide appropriate access to '/dev/urandom', as I don't understand what the denied_mask="wc" means. Maybe simple "read" (r) access would cover it, like this (?): /dev/urandom r, Anyway, testing continues. I have promoted a second Samba AD controller (again, buster) to the same AD domain in my testing environment. I have given DC2 the same apparmor configuration for the 'usr.sbin.named' profile (i.e.: complain mode, with 'local/usr.sbin.named' set identical to that of DC1). -S.M.
Bug#923711: mksquashfs: Leaks memory in deflate code; memory limits ineffective
Hi Chris, On Thu, Apr 4, 2019 at 1:04 PM Chris Lamb wrote: > > We believe that the bug you reported is fixed in the latest version of > > squashfs-tools, which is due to be installed in the Debian FTP archive. > […] > > squashfs-tools (1:4.3-12) unstable; urgency=medium > > . > > [ Alexander Couzens ] > > * Fix compressor initialization in frag_deflator() (closes: #923711). > > First, thank you all for getting this fixed in sid. It's the work of Lynxis and indeed, thanks to him. > Would anyone object to me making an unblock request for buster? This > would be the only diff/change required. You don't have to. Everything have been taken care of. It's going to migrate to Buster tomorrow (ie, unblock is already in place). Regards, Laszlo/GCS
Bug#926392: licensecheck chokes on long lines
control: tag -1 confirmed Quoting Sandro Mani (2019-04-04 13:36:28) > $ wget > https://files.pythonhosted.org/packages/source/x/xonsh/xonsh-0.8.12.tar.gz > $ tar xf xonsh-0.8.12.tar.gz > $ licensecheck xonsh-0.8.12/xonsh/parser_table.py > > => Licensecheck hangs eating cpu cycles (the file has lines with 33k and > 71k characters). Indeed. Thanks for reporting! - 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#926408: Scrolling makes kdiff3 crash
Package: kdiff3 Version: 1.7.90-3 Severity: important Dear maintainer I do the following $mkdir test1 test2 $kdiff3 test1 test2 and it crashes with the following message: $ kdiff3 test1 test2 QMainWindow::addToolBar: invalid 'area' argument KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kdiff3 path = /usr/bin pid = 21417 KCrash: Arguments: /usr/bin/kdiff3 test1 test2 KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 BTW the new version shows identical directories as different while version 0.98 showed identical directories as green which makes the program much harder to use. Regards Gudjon -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kdiff3 depends on: ii kio 5.54.1-1 ii libc6 2.28-8 ii libkf5configcore5 5.54.0-1 ii libkf5configwidgets5 5.54.0-1
Bug#926407: [l10n] Updated Czech translation of apt-listbugs
Package: apt-listbugs Severity: wishlist Tags: l10n, patch Hi, in attachement there is updated Czech (cs.po) translation of apt-listbugs. Please include it with the package. Cheers -- Miroslav Kure # Czech translation of apt-listbugs. # Copyright (C) 2002-2016 Masato Taruishi et al. # This file is distributed under the same license as the apt-listbugs package. # Miroslav Kure , 2005, 2009, 2012, 2014, 2016, 2019. # msgid "" msgstr "" "Project-Id-Version: apt-listbugs 0.1.21\n" "Report-Msgid-Bugs-To: invernom...@paranoici.org\n" "POT-Creation-Date: 2018-12-21 22:53+0100\n" "PO-Revision-Date: 2019-04-04 17:46+0200\n" "Last-Translator: Miroslav Kure \n" "Language-Team: Czech \n" "Language: cs\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=3; plural=(n==1) ? 0 : (n>=2 && n<=4) ? 1 : 2;\n" #. TRANSLATORS: "E: " is a label for error messages; you may translate it with a suitable abbreviation of the word "error" #: ../bin/apt-listbugs:421 ../bin/apt-listbugs:454 ../bin/apt-listbugs:459 #: ../bin/apt-listbugs:465 ../bin/apt-listbugs:479 ../bin/apt-listbugs:509 #: ../bin/apt-listbugs:540 ../bin/apt-listbugs:589 ../bin/apt-listbugs:602 #: ../lib/aptlistbugs/aptcleanup:52 ../lib/aptlistbugs/aptcleanup:55 #: ../lib/aptlistbugs/logic.rb:302 ../lib/aptlistbugs/logic.rb:312 #: ../lib/aptlistbugs/logic.rb:1001 ../lib/aptlistbugs/logic.rb:1013 #: ../lib/aptlistbugs/logic.rb:1026 ../lib/aptlistbugs/migratepins:52 #: ../lib/aptlistbugs/migratepins:55 msgid "E: " msgstr "E: " #: ../bin/apt-listbugs:422 msgid "" "This may be caused by a package lacking support for the ruby interpreter in " "use. Try to fix the situation with the following commands:" msgstr "" "To může být způsobeno balíkem bez podpory použitého interpretru ruby. Zkuste " "vzniklou situaci vyřešit těmito příkazy:" #: ../bin/apt-listbugs:454 msgid "" "APT_HOOK_INFO_FD is undefined.\n" msgstr "" "APT_HOOK_INFO_FD není definovaná.\n" #: ../bin/apt-listbugs:459 msgid "" "APT_HOOK_INFO_FD is not correctly defined.\n" msgstr "" "APT_HOOK_INFO_FD není definovaná správně.\n" #: ../bin/apt-listbugs:465 msgid "Cannot read from file descriptor %d" msgstr "Nelze číst z deskriptoru souboru %d" #: ../bin/apt-listbugs:479 msgid "" "APT Pre-Install-Pkgs is not giving me expected 'VERSION 3' string.\n" msgstr "" "APT Pre-Install-Pkgs nevrací očekávaný řetězec „VERSION 3“.\n" #: ../bin/apt-listbugs:509 msgid "" "APT Pre-Install-Pkgs is giving me fewer fields than expected.\n" msgstr "" "APT Pre-Install-Pkgs vrací méně polí, než je očekáváno.\n" #: ../bin/apt-listbugs:540 msgid "" "APT Pre-Install-Pkgs is giving me an invalid direction of version change.\n" msgstr "" "APT Pre-Install-Pkgs vrací neplatný směr změny verze.\n" #: ../bin/apt-listbugs:619 msgid "** Exiting with an error in order to stop the installation. **" msgstr "** Ukončeno s chybou s cílem ukončit instalaci. **" #: ../lib/aptlistbugs/aptcleanup:52 ../lib/aptlistbugs/logic.rb:405 #: ../lib/aptlistbugs/migratepins:52 msgid "Cannot read from %s" msgstr "Nelze číst z %s" #: ../lib/aptlistbugs/aptcleanup:123 msgid "Fixed packages : " msgstr "Opravené balíky: " #: ../lib/aptlistbugs/logic.rb:50 msgid "Usage: " msgstr "Použití: " #: ../lib/aptlistbugs/logic.rb:51 msgid " [options] [arguments]" msgstr " [volby] [argumenty]" #: ../lib/aptlistbugs/logic.rb:53 msgid "" "Options:\n" msgstr "" "Volby:\n" #. TRANSLATORS: the colons (:) in the following strings are vertically aligned, please keep their alignment consistent #. TRANSLATORS: the \"all\" between quotes should not be translated #: ../lib/aptlistbugs/logic.rb:56 msgid "" " -s : Filter bugs by severities you want to see\n" "(or \"all\" for all)\n" "[%s].\n" msgstr "" " -s : Zobrazí jen chyby daných závažností\n" "(nebo „all“ pro všechny)\n" "[%s].\n" #: ../lib/aptlistbugs/logic.rb:57 msgid "" " -T : Filter bugs by tags you want to see.\n" msgstr "" " -T <štítky> : Zobrazí jen chyby s danými štítky.\n" #: ../lib/aptlistbugs/logic.rb:58 msgid "" " -S : Filter bugs by pending-state categories you want to see\n" "[%s].\n" msgstr "" " -S: Zobrazí jen chyby daných stavů\n" "[%s].\n" #: ../lib/aptlistbugs/logic.rb:59 msgid "" " -B : Filter bugs by number, showing only the specified bugs.\n" msgstr "" " -B : Zobrazí pouze chyby daných čísel.\n" #: ../lib/aptlistbugs/logic.rb:60 msgid "" " -D : Show downgraded packages, too.\n" msgstr "" " -D : Vypíše také chyby v degradovaných balících.\n" #: ../lib/aptlistbugs/logic.rb:61 msgid "" " -H : Hostname of Debian Bug Tracking System [%s].\n" msgstr "" " -H : Jméno počítače na němž běží debianí BTS [%s].\n" #: ../lib/aptlistbugs/logic.rb:62 msgid "" " -p : Port number of the server [%s].\n"
Bug#926260: debian-history: DebConf2 mistakenly referred to as the second DebConf
Hi,
Thanks.
On Tue, Apr 02, 2019 at 08:09:17PM +0200, Rafa wrote:
> Package: debian-history
> Severity: normal
>
> Dear Maintainers,
>
> File project-history.en.dbk, as of commit 176f60e3, refers to DebConf2
> as the "second" Debconf in line 814. It is my understanding that it
> should be referred to as the "third" Debconf instead.
>
> Also, only the starting date is given (July 5th). I would suggest to
> mention the ending date as well (July 7th).
I am aware of the fact that there has been some confusing numbering
situation on DEBCONF.
In order to change current text, we need 2 things:
* definitive reference information. I.e., PROOF.
("My understanding" is too weak.)
* Endorsement by DEBCONF active organizer is nice to have as a
supporting evidence.
* Exact text to be uised to replace section.
Osamu
Bug#926406: ITP: effcee -- C++ library for stateful pattern matching of strings
Package: wnpp Severity: wishlist Owner: Yangfl Control: block 909156 by -1 * Package name: effcee Version : 2018.1 Upstream Author : Google * URL : https://github.com/google/effcee * License : Apache2 Programming Lang: C++ Description : C++ library for stateful pattern matching of strings
Bug#926317: [Debian-iot-maintainers] Bug#926317: libyder.pc Requires.private systemd, but systemd not in debian/control
Hi Nicolas, thanks for your response. On Thu, Apr 04, 2019 at 09:10:10AM -0400, Nicolas Mora wrote: > Libyder relies on libsystemd to write logs in journald, but it's one of the > log output available, like syslog, a file, a callback or the console. But you > can use libyder without systemd if you don't use it as log output. This is great, but then why do you have the following patch in the yder debian package? Description: soname is still 2.0, fix PKGCONF_REQ_PRIVATE Author: Nicolas Mora Index: yder-1.4.4/CMakeLists.txt === --- yder-1.4.4.orig/CMakeLists.txt +++ yder-1.4.4/CMakeLists.txt @@ -135,7 +135,7 @@ endif () if (WITH_JOURNALD) set(PKGCONF_REQ "") - set(PKGCONF_REQ_PRIVATE "libsystemd, liborcania") + set(PKGCONF_REQ_PRIVATE "systemd, liborcania") else () set(PKGCONF_REQ "") set(PKGCONF_REQ_PRIVATE "liborcania") This patch does the *exact opposite* of what you described in your e-mail. It causes the libyder.pc contain a Requires.private on 'systemd', and not on 'libsytemd'. This means you can build + install they libyder + libyder-dev package just fine on a system without systemd. But then, when you actually want to build any application against libyder, its autoconf/cmake step will fail as 'systemd.pc' is not available but listed in Requires.private. So if you really only need libsystemd, why change from libsystemd to systemd in the patch above? Regards, Harald -- - Harald Weltehttp://laforge.gnumonks.org/ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)
Bug#926405: www.debian.org: Debian logos - PDF conversion is pixelated
Package: www.debian.org Severity: wishlist Tags: patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear Maintainer, I've found a problem when I convert the Debian logos to PDF format in Buster. The render is pixelated. If you want convert the logo to PDF format: rsvg-convert -f pdf -o openlogo-nd.pdf openlogo-nd.svg If we disable the 'enable-background="[...]"' property in 'svg' tag the conversion to PDF file work. This problem is present with the following Debian logos: - - https://www.debian.org/logos/openlogo.svg - - https://www.debian.org/logos/openlogo-nd.svg - - openlogo-nd-alpha.svg (available in Debian Flyers repository) In W3C website, this property seems deprecated: https://www.w3.org/TR/filter-effects/#AccessBackgroundImage Does we can remove this property in Debian logos? Regards, Alban -BEGIN PGP SIGNATURE- iQJLBAEBCAA1FiEErkjA9ZsZmKBikqaZlr1P9k5wn94FAlymI+IXHGFsYmFuLnZp ZGFsQHpvcmRoYWsuZnIACgkQlr1P9k5wn977hxAAozk9ONPhaOYqGFJ4rRDSVMeG OE8Cur2WFtKngtSx3fGAlIxyJW5lkwMtswFCds0igk+3+K2E38XMHN9WL2Ubh32r jtDHZSHFmIxKxE6v7k9QvYr1wa/o9cEdZfA4ykRFvuBuL8VOpRMGDu5Lbi+dvsaK FKx8Y7potNQIN9lTd/moa4dRX19qNMQ7rsNM9+dxGcQzmHUoNCv+RX3j2HS8oxhM G1LIqGCy8cx0YuDBdJvpPkaHuPyEIsTiqTe/IDjueBjsV1nQMa8M3C8Hf2kuORdC UKc8u8C+ZPE/yecZfJNQtmhLdewTgsusYnOhxMWvYqyZQrL1gdapJdU4gfciEFCC rm7PVTKZKHaYaPPlOLCeMo8jtbsYtmuvD3XYDce6kpXQklEgQGeAa/DLyjHrdZDZ TFf50+9NvKYhuQet0KQ4XnHWix6aZ6XyWUkZ+BLy/3foRgoL3BxCWKJgctad9qup B+3YixgMXAAwOuJQkpHU4EIJy6A0edJ+w8dAHYi5BBDlKNVzolH3peoPezfK5bjw 1WzMc46jsLWxKQsL1/ugdvfUWxmDO3o+dHU7pbMPWzz5RPEEJ7yJ6uAwps+3vW9+ imcFvcsKEUxxdrTFulB9ue2pUqIEga7DL0NRAmxVaUgWXBq+Glw5pZSB3oM25yfH QLPoDEP8C2XBidtj6bA= =ixsG -END PGP SIGNATURE- --- openlogo.svg2019-04-04 15:46:24.060790251 +0200 +++ openlogo-fixed.svg 2019-04-04 15:36:00.140879770 +0200 @@ -1,6 +1,6 @@ -http://ns.adobe.com/Extensibility/1.0/; xmlns:i="http://ns.adobe.com/AdobeIllustrator/10.0/; xmlns:graph="http://ns.adobe.com/Graphs/1.0/; xmlns="http://www.w3.org/2000/svg; xmlns:xlink="http://www.w3.org/1999/xlink; xmlns:a="http://ns.adobe.com/AdobeSVGViewerExtensions/3.0/; i:viewOrigin="251 467" i:rulerOrigin="0 0" i:pageBounds="0 792 612 0" width="108.758" height="144.133" viewBox="0 0 108.758 144.133" overflow="visible" enable-background="new 0 0 108.758 144.133" xml:space="preserve"> +http://ns.adobe.com/Extensibility/1.0/; xmlns:i="http://ns.adobe.com/AdobeIllustrator/10.0/; xmlns:graph="http://ns.adobe.com/Graphs/1.0/; xmlns="http://www.w3.org/2000/svg; xmlns:xlink="http://www.w3.org/1999/xlink; xmlns:a="http://ns.adobe.com/AdobeSVGViewerExtensions/3.0/; i:viewOrigin="251 467" i:rulerOrigin="0 0" i:pageBounds="0 792 612 0" width="108.758" height="144.133" viewBox="0 0 108.758 144.133" overflow="visible" xml:space="preserve"> http://ns.adobe.com/Variables/1.0/;> --- openlogo-nd.svg 2019-04-04 15:46:27.628812155 +0200 +++ openlogo-nd-fixed.svg 2019-04-04 15:35:49.756813726 +0200 @@ -16,7 +16,7 @@ http://ns.adobe.com/AdobeSVGViewerExtensions/3.0/; -width="87.041" height="108.445" viewBox="0 0 87.041 108.445" overflow="visible" enable-background="new 0 0 87.041 108.445" +width="87.041" height="108.445" viewBox="0 0 87.041 108.445" overflow="visible" xml:space="preserve">
Bug#926388: let Firefox trust /etc/ssl/certs/ca-certificates.crt
On Thu, Apr 04, 2019 at 01:03:50PM +, Mike Gabriel wrote:
> Feel free to keep this bug open for bullseye, so we can re-discuss this
> approach or close it.
Yes, let's consider this for bullseye.
Just for the record:
[ pkcs11.txt ]
On a 64-bit PC Buster system this is working ok:
> library=/usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so
> name=PKCS#11 Trust Module
> NSS=trustOrder=100
To get it working for a mixed 64-bit / 32-bit setup this content
seems to work:
library=/usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so
library=/usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so
name=PKCS#11 Trust Module
NSS=trustOrder=100
For already existing accounts:
[ Firefox-ESR ]
Checking the existence and then removing
~/.mozilla/firefox/debian-edu.default/{cert8.db,key3.db,cert9.db,key4.db}
after replacing the exsting pkcs11.txt file seems to work.
[ Thunderbird ]
Similar to Firefox-ESR; location:
~/.thunderbird/debian-edu.default/{cert8.db,key3.db,cert9.db,key4.db}
[ Chromium, Konqueror, and others using PKI ]
Check the existence and then remove
~/.pki/{cert9.db,key4.db}
after replacing the exsting pkcs11.txt file
Wolfgang
signature.asc
Description: PGP signature
Bug#925514: updated archive.debian.org snapshot?
On Mon, 25 Mar 2019 at 21:06, Tianon Gravi wrote: > It would seem https://snapshot.debian.org/archive/debian-archive/ hasn't > had a snapshot since 2016, which is especially relevant now given that > wheezy and jessie have been removed from the mirrors. https://snapshot.debian.org/archive/debian-archive/20190328T105444Z/ ! Thank you! :) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4
Bug#926149: AMD: Add nomodeset kernel parameter to avoid black screen
On Thu, 2019-04-04 at 09:22 +0800, 積丹尼 Dan Jacobson wrote:
> > > > > > "BH" == Ben Hutchings writes:
>
> BH> The installer normally uses a dumb framebuffer driver (probably efifb
> BH> on this system) that is built into the kernel. This is too low-
> BH> performance for a proper desktop.
>
> OK, the installer could first double check that the framebuffer driver
> it intends to write to the installation really will work, by telling the
> user:
>
> "5 seconds please, while we test your framebuffer ability."
>
> During which it could launch its proposed framebuffer,
> see if /proc/sys/.../{voltage or number of lit pixels, etc.} has
> suddenly dropped to zero, indicating a black screen, and then back out
> of that choice. Or simply ask the user "in a moment you will be asked if
> you saw a black screen".
[...]
There is generally no way to back out of changing the framebuffer
driver, other than to reboot. So we would have to implement some
ability for the installer to checkpoint its progress and then continue
after a reboot. I suspect that that would require a pretty major
architectural change and is unlikely to happen any time soon.
However it might be reasonable to add "nomodeset" to the command line
in GRUB's "recovery" boot menu items.
Ben.
--
Ben Hutchings
Any smoothly functioning technology is indistinguishable
from a rigged demo.
signature.asc
Description: This is a digitally signed message part
Bug#926306: RFS: socklog/2.1.0-9
On Thu, Apr 04, 2019 at 01:40:16PM +0200, Mathieu Mirmont wrote: > On Thu, Apr 04, 2019 at 12:48:43PM +0200, Adam Borowski wrote: > > A nice new process is described here: > >https://wiki.debian.org/PackageSalvaging > > but it's probably an overkill for a clear case like here. But, the old > > maintainer being the upstream means you need to at least communicate with > > him beforehand. > > I did reach out to Gerrit Pape (previous maintainer & upstream) of > course before doing anything. I offered to help and he was happy to hand > over the package to me. I'll file an ITS if you guys think I should. > > Adding Gerrit Pape to CC. Hi all, this is okay with me! I'm happy to hand over the package, sorry for not making this clear in advance. Best Regards, and have fun, Mathieu, with maintaining socklog.
Bug#926404: /usr/bin/pdfsig: pdfsig: segfaults with "couldn't find default Firefox Folder"
Package: poppler-utils Version: 0.71.0-3 Severity: normal File: /usr/bin/pdfsig Dear Maintainers, when running pdfsig on a system, without Firefox, it segfaults: $ pdfsig A_signed.pdf Digital Signature Info of: A_signed.pdf Internal Error (0): couldn't find default Firefox Folder Segmentation fault Expected is that it does not segfault or the installations gives a hint. Proposed fix is to depend on or recommend the necessary firefox packages. Best Regards, Bernhard -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/1 CPU core) Kernel taint flags: TAINT_CRAP 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 /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages poppler-utils depends on: ii libc6 2.28-8 ii libcairo2 1.16.0-4 ii libfreetype6 2.9.1-3 ii liblcms2-22.9-3 ii libpoppler82 0.71.0-3 ii libstdc++68.3.0-4 poppler-utils recommends no packages. poppler-utils suggests no packages. -- no debconf information
Bug#926385: kalarm does not show details of errors, for the error about missing akonadi
Note that the error message and the button "Details" are provided automatically by the Akonadi library if Akonadi fails to start up. AFAIK, you would see exactly the same display in any other Akonadi-dependent application if Akonadi failed to start. So, although you see the fault in KAlarm, the bug actually lies in the relevant Akonadi library package. -- David Jarvie. KDE developer. KAlarm author -- http://www.astrojar.org.uk/kalarm
Bug#926403: ITP: python-fhirclient -- Python 3 SMART on FHIR client
Package: wnpp Severity: wishlist Subject: ITP: python-fhirclient -- Python 3 SMART on FHIR client Package: wnpp Owner: Andreas Tille Severity: wishlist * Package name: python-fhirclient Version : 3.0.0 Upstream Author : Boston Children's Hospital * URL : https://github.com/smart-on-fhir/client-py * License : Apache-2.0 Programming Lang: Python Description : Python 3 SMART on FHIR client This is fhirclient, a flexible Python client for FHIR servers supporting the SMART on FHIR protocol. . Client versioning is not identical to FHIR versioning. The master branch is usually on the latest version of the client as shown below, possibly on bugfix releases thereof. The develop branch should be on recent freezes, and the feature/latest-ci branch is periodically updated to the latest FHIR continuous integration builds. . This is the client for Python 3. Remark: This package is maintained by Debian Med Packaging Team at https://salsa.debian.org/med-team/python-fhirclient
Bug#926306: RFS: socklog/2.1.0-9
On Thu, Apr 04, 2019 at 01:30:30PM +0200, Mathieu Mirmont wrote: > On Thu, Apr 04, 2019 at 10:20:47AM +, Dmitry Bogatov wrote: > > * I know, it is pain, but there should be init.d script. You may want to > > take a look at bcron=0.11-8. > > Sure, no worries. How about systemd service files? It makes little sense > to run socklog along with systemd I think, but for the principle it may > be required to profile service files. What do you think? No point in adding .service if you already have an init script; that'd be useful only if you want to do something _different_ when running under systemd, or when you hit a systemd bug that makes it unable to handle a regular init script. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Did ya know that typing "test -j8" instead of "ctest -j8" ⢿⡄⠘⠷⠚⠋⠀ will make your testsuite pass much faster, and fix bugs? ⠈⠳⣄
Bug#926306: RFS: socklog/2.1.0-9
On Thu, Apr 04, 2019 at 01:40:16PM +0200, Mathieu Mirmont wrote: > I did reach out to Gerrit Pape (previous maintainer & upstream) of > course before doing anything. I offered to help and he was happy to hand > over the package to me. Cool, that answers my question. It'll be enough to write "New maintainer" in the changelog then. > I'll file an ITS if you guys think I should. No point, you already have Gerrit's consent. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Did ya know that typing "test -j8" instead of "ctest -j8" ⢿⡄⠘⠷⠚⠋⠀ will make your testsuite pass much faster, and fix bugs? ⠈⠳⣄
Bug#926402: mirror submission for mirror-debian.usetelecom.com.br
Package: mirrors Severity: wishlist User: mirr...@packages.debian.org Usertags: mirror-submission Submission-Type: new Site: mirror-debian.usetelecom.com.br Type: leaf Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x Archive-http: /debian/ Archive-rsync: debian/ Maintainer: Cleriston Santos Country: BR Brazil Location: Salvador-BA Sponsor: Use Telecom https://www.usetelecom.com.br/ Trace Url: http://mirror-debian.usetelecom.com.br/debian/project/trace/ Trace Url: http://mirror-debian.usetelecom.com.br/debian/project/trace/ftp-master.debian.org Trace Url: http://mirror-debian.usetelecom.com.br/debian/project/trace/mirror-debian.usetelecom.com.br
Bug#920665: xwayland: Crash with external display, notifications, and screen idle [upstream patch attached]
I see that this landed in unstable (in the next upstream release) but testing is still affected, as it's frozen. I installed testing in a new machine and I have hit this crasher again. I think this should be considered serious enough to be fixed in testing/upcoming stable.
Bug#901940: Updated the merge request
Hi, looking ahead in preparation to post-buster being more open for such changes I updated the merge request. Is is rebased to match latest git and further has: - adapted the dropping of xen.so - added a news file as requested - separated qemu.so as well as requested - made qemu a depends and lxc a recommends as requested I have not yet opened any bugs with the consuming packages as I wanted to hear your current feedback on that last update first.
Bug#926317: [Debian-iot-maintainers] Bug#926317: libyder.pc Requires.private systemd, but systemd not in debian/control
Hello, I'm not sure I understand the problem. Libyder relies on libsystemd to write logs in journald, but it's one of the log output available, like syslog, a file, a callback or the console. But you can use libyder without systemd if you don't use it as log output. Also, in Debian packages, libsystemd0 doesn't have systemd as a dependency. This may be for a reason. I will try and see what happens if you use libyder with libsystemd and without systemd. But besides the probable fact that a journald log will be unavailable if set, I don't think there will be bad consequences. Le 3 avril 2019 06 h 02 min 22 s HAE, Harald Welte a écrit : >Package: libyder-dev >Version: 1.4.4-4 >Severity: normal > >I'm experiencing problems building yder-based applications:, >libyder.pc (after applying debian/cmake.patch) has a Requires.private >to >the pacakge 'systemd'. However, 'systemd' is not listed in the >'Depends' line of debian/control. > >This leads to the absurd situation that I can build + install >libyder-dev, but other yder-using applications will not get past their >cmaake/autoconf step as 'systemd' is not neccessarily installed. > >So at the very least, 'systemd' should be listed in 'Depends'. > >I'm somewhat doubtful about this entire method of using pkg-config >'Requires.private'. It may make sense in the absence of a package >manager. But as we're talking about a Debian package here: >Dependencies >should be tracked at package installation time using dpkg/apt, and not >some pkg-config private mechanism, IMHO. > >Also, I'm not entirely sure why there's a dependency on 'systemd', and >not 'libsystemd' as in the upstream source. The Debian changelog >unfortunately doesn't explain why that cmake.patch is used. > >Thanks in advance. > >-- System Information: >Debian Release: buster/sid > APT prefers unstable > APT policy: (500, 'unstable') >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=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), >LANGUAGE=en_US.UTF-8 (charmap=UTF-8) >Shell: /bin/sh linked to /bin/bash >Init: systemd (via /run/systemd/system) >LSM: AppArmor: enabled > >Versions of packages libyder-dev depends on: >ii libjansson-dev 2.12-1 >ii liborcania-dev 1.2.9-5 >ii libsystemd-dev 241-2 >ii libyder2.0 1.4.4-4 > >libyder-dev recommends no packages. > >libyder-dev suggests no packages. > >-- no debconf information > >___ >Debian-iot-maintainers mailing list >debian-iot-maintain...@alioth-lists.debian.net >https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-iot-maintainers
