Bug#797773: proftpd-basic: Problem with mod_sql (no queries sent)

[Hilmar Preuße]

On 02.09.2015 14:51, Michal Rydlikowski wrote:

Hi Michael,

> mod_sql doesn't work with odbc and postgresql, there is connection
> with database, but no querys are sent.
> It works on the same configuration with the wheezy package (I builded
> package with wheezy version of proftpd)
> 
Between 1.3.5 and 1.3.5d a few bugs in this area where fixed. Do you
have the chance to test w/ Debian unstable or to compile the 1.3.5.d
package on stable to test if the problem is solved?

Moreover 1.3.6 was uploaded for testing.

Thanks,
  Hilmar
-- 
#206401 http://counter.li.org

Bug#892252: src:python-bleach: URI values with character entities not properly sanitized

[Scott Kitterman]

Package: src:python-bleach
Version: 2.1.2-1
Severity: important
Tags: upstream, security


Version 2.1.3 (March 5th, 2018)
---

**Security fixes**

* Attributes that have URI values weren't properly sanitized if the
  values contained character entities. Using character entities, it
  was possible to construct a URI value with a scheme that was not
  allowed that would slide through unsanitized.

  This security issue was introduced in Bleach 2.1. Anyone using
Bleach 2.1 is highly encouraged to upgrade.

Bug#892251: dovecot: fails to build from source twice in a row (unclean tree)

[Christian Hofstaedtler]

Source: dovecot
Version: 1:2.2.34-2
Severity: normal

Hi,

thanks for maintaining the dovecot packages.

While rebuilding dovecot from source, I've noticed that doing this twice
in a row fails:

~/dovecot-2.2.34 % debuild -us -uc
[..]
~/dovecot-2.2.34 % debuild -us -uc
[..]
dpkg-source: info: local changes detected, the modified files are:
 dovecot-2.2.34/dovecot.service
 dovecot-2.2.34/src/config/all-settings.c
dpkg-source: error: aborting due to unexpected upstream changes, see 
/tmp/dovecot_2.2.34-2.diff.KZl62_
[..]

Please see the diff below.

Thanks,
Chris



--- /dev/null
+++ dovecot-2.2.34/dovecot.service
@@ -0,0 +1,32 @@
+# This file is part of Dovecot
+#
+# If you want to pass additionally command line options to the dovecot
+# binary, create the file:
+#  `/etc/systemd/system/dovecot.service.d/service.conf'.
+
+[Unit]
+Description=Dovecot IMAP/POP3 email server
+Documentation=man:dovecot(1)
+Documentation=http://wiki2.dovecot.org/
+After=local-fs.target network-online.target
+
+[Service]
+Type=simple
+ExecStart=/usr/sbin/dovecot -F
+PIDFile=/var/run/dovecot/master.pid
+ExecReload=/usr/bin/doveadm reload
+ExecStop=/usr/bin/doveadm stop
+PrivateTmp=true
+NonBlocking=yes
+# Enable this if your systemd is new enough to support it:
+ProtectSystem=full
+
+# You can add environment variables with e.g.:
+#Environment='CORE_OUTOFMEM=1'
+# If you have trouble with `Too many open files' you may set:
+#LimitNOFILE=8192
+# If you want to allow the Dovecot services to produce core dumps, use:
+#LimitCORE=infinity
+
+[Install]
+WantedBy=multi-user.target
--- dovecot-2.2.34.orig/src/config/all-settings.c
+++ dovecot-2.2.34/src/config/all-settings.c
@@ -1068,7 +1068,7 @@ static const struct setting_define mbox_
 };
 static const struct mbox_settings mbox_default_settings = {
.mbox_read_locks = "fcntl",
-   .mbox_write_locks = "dotlock fcntl",
+   .mbox_write_locks = "fcntl dotlock",
.mbox_lock_timeout = 5*60,
.mbox_dotlock_change_timeout = 2*60,
.mbox_min_index_size = 0,
@@ -2910,7 +2910,7 @@ struct master_settings master_default_se
.state_dir = PKG_STATEDIR,
.libexec_dir = PKG_LIBEXECDIR,
.instance_name = PACKAGE,
-   .protocols = "imap pop3 lmtp",
+   .protocols = "",
.listen = "*, ::",
.ssl = "yes:no:required",
.default_internal_user = "dovecot",
@@ -2997,7 +2997,7 @@ static const struct setting_define login
 static const struct login_settings login_default_settings = {
.login_trusted_networks = "",
.login_source_ips = "",
-   .login_greeting = PACKAGE_NAME" ready.",
+   .login_greeting = DOVECOT_NAME" ready.",
.login_log_format_elements = "user=<%u> method=%m rip=%r lip=%l mpid=%e 
%c session=<%{session}>",
.login_log_format = "%$: %s",
.login_access_sockets = "",
@@ -3154,7 +3154,7 @@ static const struct lmtp_settings lmtp_d
.lmtp_user_concurrency_limit = 0,
.lmtp_address_translate = "",
.lmtp_hdr_delivery_address = "final:none:original",
-   .login_greeting = PACKAGE_NAME" ready.",
+   .login_greeting = DOVECOT_NAME" ready.",
.login_trusted_networks = ""
 };
 static const struct setting_parser_info *lmtp_setting_dependencies[] = {
@@ -4802,34 +4802,34 @@ buffer_t config_all_services_buf = {
 const struct setting_parser_info *all_default_roots[] = {
_service_setting_parser_info,
_service_ssl_setting_parser_info,
-   _storage_setting_parser_info, 
-   _setting_parser_info, 
+   _setting_parser_info, 
+   _setting_parser_info, 
_params_setting_parser_info, 
-   _user_setting_parser_info, 
-   _setting_parser_info, 
-   _setting_parser_info, 
-   _urlauth_setting_parser_info, 
+   _setting_parser_info, 
+   _storage_setting_parser_info, 
_urlauth_login_setting_parser_info, 
-   _login_setting_parser_info, 
-   _crypt_setting_parser_info, 
-   _login_setting_parser_info, 
-   _setting_parser_info, 
_setting_parser_info, 
-   _setting_parser_info, 
-   _setting_parser_info, 
_setting_parser_info, 
-   _urlauth_worker_setting_parser_info, 
-   _setting_parser_info, 
-   _status_setting_parser_info, 
-   _setting_parser_info, 
+   _crypt_setting_parser_info, 
_setting_parser_info, 
-   _setting_parser_info, 
+   _setting_parser_info, 
+   _setting_parser_info, 
+   _setting_parser_info, 
+   _setting_parser_info, 
_setting_parser_info, 
-   _setting_parser_info, 
+   _setting_parser_info, 
+   _login_setting_parser_info, 
+   _urlauth_worker_setting_parser_info, 
+   _status_setting_parser_info, 
+   _login_setting_parser_info, 
_setting_parser_info, 
+   _urlauth_setting_parser_info, 
+   _setting_parser_info, 
_setting_parser_info, 
-   _setting_parser_info, 
-   _setting_parser_info, 
+   

Bug#892197: lintian: fpos for debian-changelog-line-too-short

[Chris Lamb]

tags 892197 + pending
thanks

Fixed in Git, pending upload:

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


Regards,

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

Bug#892227: [Pkg-javascript-devel] Bug#892227: node-backbone: dependencies fail to resolve when jQuery not installed

[Jonas Smedegaard]

Quoting Ben Finney (2018-03-07 02:51:55)
> On 07-Mar-2018, Jonas Smedegaard wrote:
> > Quoting Ben Finney (2018-03-07 01:04:19)
> > > $ cat ./source/foo.js
> > > "use strict";
> > > import 'backbone';
> > > 
> > > So the Debian package dependencies are all satisfied, but these are
> > > not sufficient for Webpack to resolve the Backbone dependencies.
> > 
> > Backbone by design avoids dependency on jQuery.
> 
> And yet, a very simple application that *only* requests ‘backbone’
> will fail to build with Webpack because Backbone tries to find jQuery.
> 
> In other words: The expectation is that installing Debian packages
> ‘webpack’ ands ‘node-backbone’ should allow the above application to
> build with Webpack.
> 
> So, something is wrong with the Debian Backbone, or the Debian
> Webpack, or something else.

I slept on it, and realized this morning¹ that you are right: This is a 
bug in Debian packaging of Backbone: It should recommend node-jquery.

Similarly it should recommend node-underscore | node-lodash.

I will make that happen. Thanks!


 - Jonas


¹ ...before reading your reply above, but that helps too: Your emails 
are in general easy to comprehend and quite often enlightening. Thanks!

-- 
 * 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#892136: /usr/bin/loimpress: Libreoffice Impress sometimes silently deletes a slide from the presentation

[Rene Engelhard]

On Tue, Mar 06, 2018 at 03:44:00PM +0100, Wojtek Zabolotny wrote:
> On 06.03.2018 10:01, Rene Engelhard wrote:
> > tag 892136 + moreinfo
> > thanks
> > Would you also file the same bug if people using vi would do 1dd
> > or %y or so blindly in command mode and wondering whether 1 lines or 
> > your
> > file contents are gone?
> No, however if deletion occurs during normal edition (scrolling, entering of 
> normal characters) it is obviously a reason to fill the bug report.

You yourself said:

"Probably certain user activity (a special dragging the slides in the
left
pannel, or using a special key sequence?) causes Impress to delete a
slide without any warning or confirmation request."

"special key sequence" is not the same as "entering of normal
characters", neither is "a special dragging" the same as scrolling.

Regards,

Rene

Bug#892245: pkg-config: /usr/lib/x86_64-linux-gnu/pkgconfig is not searched on amd64

[Helmut Grohne]

Control: tags -1 + moreinfo unreproducible

On Wed, Mar 07, 2018 at 12:42:28AM -0500, Alexis Hunt wrote:
> I'm running Debian testing and was trying to use a package reliant on
> libncursesw. The libncursesw5-dev package installs ncursesw.pc into
> /usr/lib/x86_64-linux-gnu/pkgconfig, alongside many other pkg-config files. 
> Upon
> configuring, however, an error was reported from pkg-config that it could not
> find ncursesw.pc. Investigation shows that this is because it is no loading 
> from
> /usr/lib/x86_64-linux-gnu/pkgconfig, which means that any -dev package which
> installs to that directory won't work correctly with pkg-config unless the 
> user
> explicitly specifies PKG_CONFIG_PATH (as I did to work around this).

I cannot reproduce this at all. In a fresh sid debootstrap after
installing libncursesw5-dev and pkg-config,

pkg-config --exists ncursesw

gives a successful exit code. I conclude that the behaviour you are
reporting is not reproducible in general and that you need to provide
further information on how to reproduce it. Please remove the moreinfo
tag (by starting your reply with "Control: tags -1 - moreinfo") when
doing so.

Helmut

Bug#892249: lintian: detect broken ftp://ftp.debian.org and ftp://security.debian.org links

[Paul Wise]

Package: lintian
Version: 2.5.78
Severity: wishlist

Please detect packages that use the following links (or any subdirs):

ftp://ftp.debian.org
ftp://security.debian.org

Debian dropped support for the FTP protocol on these sites last year:

https://lists.debian.org/msgid-search/20170425131901.f64ltdn2p6677...@shiraz.lpma-paris.fr

A list of packages affected can be found via codesearch:

(this URL only works with JavaScript off)
https://codesearch.debian.net/search?q=ftp%3A%2F%2F%28security%7Cftp%29%5C.debian%5C.org

I assume lintian will not search through all files in the source
package, but it could at least do the same as is done for the
obsolete-sites tests.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#892250: ruby-rack-protection: CVE-2018-1000119: Timing attack in authenticity_token.rb

[Salvatore Bonaccorso]

Source: ruby-rack-protection
Version: 1.5.2-1
Severity: grave
Tags: patch security upstream

Hi,

the following vulnerability was published for ruby-rack-protection.

CVE-2018-1000119[0]:
Timing attack in authenticity_token.rb

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-1000119
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000119
[1] 
https://github.com/sinatra/sinatra/commit/8aa6c42ef724f93ae309fb7c5668e19ad547eceb
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1534027

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#892248: libfftw3-dbg: please drop -dbg package in favour of automatic -dbgsym packages

[Paul Wise]

Package: libfftw3-dbg
Version: 3.3.7-1
Severity: wishlist

Please drop the -dbg package in favour of automatic -dbgsym packages:

https://wiki.debian.org/AutomaticDebugPackages

I don't think there needs to be a transitional -dbg package either.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#892244: debian-www: doc-debian package page contains invalid URL

[Paul Wise]

Control: reopen -1 
Control: clone -1 -2
Control: reassign -2 debian-faq 8.1

On Wed, 2018-03-07 at 13:37 +0800, Paul Wise wrote:
> On Wed, 07 Mar 2018 00:25:13 -0500 annadane wrote:
> 
> > On https://packages.debian.org/sid/doc-debian the 
> > "All of these files are available at
> > fttp://ftp.debian.org/debian/doc/" text is an invalid url.
> 
> This text does not appear on that page, please reload.

Woops, it does appear, I got confused by fttp, sorry about that!

The problem is that Debian dropped ftp support for the mirrors:

https://lists.debian.org/msgid-search/20170425131901.f64ltdn2p6677...@shiraz.lpma-paris.fr

This issue also exists in the debian-faq package, cloned the bug.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#892245: pkg-config: /usr/lib/x86_64-linux-gnu/pkgconfig is not searched on amd64

[Alexis Hunt]

Package: pkg-config
Version: 0.29-4+b1
Severity: important

Dear Maintainer,

I'm running Debian testing and was trying to use a package reliant on
libncursesw. The libncursesw5-dev package installs ncursesw.pc into
/usr/lib/x86_64-linux-gnu/pkgconfig, alongside many other pkg-config files. Upon
configuring, however, an error was reported from pkg-config that it could not
find ncursesw.pc. Investigation shows that this is because it is no loading from
/usr/lib/x86_64-linux-gnu/pkgconfig, which means that any -dev package which
installs to that directory won't work correctly with pkg-config unless the user
explicitly specifies PKG_CONFIG_PATH (as I did to work around this).

I believe that pkg-config should look there by default, or else all -dev
packages installing there need to be updated to install somewhere in the default
path.

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

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

Versions of packages pkg-config depends on:
ii  libc6 2.26-6
ii  libdpkg-perl  1.19.0.5
ii  libglib2.0-0  2.54.3-2

pkg-config recommends no packages.

pkg-config suggests no packages.

-- no debconf information

Bug#892244: debian-www: doc-debian package page contains invalid URL

[Paul Wise]

Control: reassign -1 doc-debian
Control: close -1

On Wed, 07 Mar 2018 00:25:13 -0500 annadane wrote:

> Package: debian-www

This should have been filed against the doc-debian package, since
packages.debian.org only has descriptions from packages themselves
rather than from the Debian website.

PS: the correct pseudo-package for the website is www.debian.org:

https://www.debian.org/Bugs/pseudo-packages

> On https://packages.debian.org/sid/doc-debian the 
> "All of these files are available at
> fttp://ftp.debian.org/debian/doc/" text is an invalid url.

This text does not appear on that page, please reload.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#892244: debian-www: doc-debian package page contains invalid URL

[annadane]

Package: debian-www
Severity: minor

Dear Maintainer,

On https://packages.debian.org/sid/doc-debian the "All of these files are 
available at fttp://ftp.debian.org/debian/doc/" text is an invalid url. This is 
solved by chanting it to http://ftp.debian.org/debian/doc/

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

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

Bug#892243: systemsettings: Settings in Monitor and Display Crashes on Wayland

[Jajo]

Package: systemsettings
Version: 4:5.12.2-1
Severity: normal
Tags: a11y

Dear Maintainer,

This works well in X display but on Wayland I get this error when I click on
any settings under Monitor and Display

wl_display@1: error 0: invalid object 86

Running Systemsettings on shell has this full debug:

$ systemsettings5
Using Wayland-EGL
Using the 'xdg-shell-v6' shell integration
kscreen.kwayland: Loading Wayland backend.
wl_display@1: error 0: invalid object 86
The Wayland connection experienced a fatal error (Invalid argument)



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

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

Versions of packages systemsettings depends on:
ii  kio   5.42.0-3
ii  kpackagetool5 5.42.0-2
ii  libc6 2.27-1
ii  libkf5activities5 5.42.0-2
ii  libkf5activitiesstats15.42.0-2
ii  libkf5auth5   5.42.0-2
ii  libkf5completion5 5.42.0-4
ii  libkf5configcore5 5.42.0-2
ii  libkf5configgui5  5.42.0-2
ii  libkf5configwidgets5  5.42.0-2
ii  libkf5coreaddons5 5.42.0-2
ii  libkf5crash5  5.42.0-2
ii  libkf5dbusaddons5 5.42.0-2
ii  libkf5declarative55.42.0-2
ii  libkf5i18n5   5.42.0-3
ii  libkf5iconthemes5 5.42.0-2
ii  libkf5itemviews5  5.42.0-2
ii  libkf5kcmutils5   5.42.0-2
ii  libkf5khtml5  5.42.0-2
ii  libkf5kiowidgets5 5.42.0-3
ii  libkf5package55.42.0-2
ii  libkf5service-bin 5.42.0-2
ii  libkf5service55.42.0-2
ii  libkf5widgetsaddons5  5.42.1-2
ii  libkf5windowsystem5   5.42.0-2
ii  libkf5xmlgui5 5.42.0-2
ii  libqt5core5a  5.9.2+dfsg-12
ii  libqt5dbus5   5.9.2+dfsg-12
ii  libqt5gui55.9.2+dfsg-12
ii  libqt5qml55.9.2-3
ii  libqt5quick5  5.9.2-3
ii  libqt5quickwidgets5   5.9.2-3
ii  libqt5widgets55.9.2+dfsg-12
ii  libstdc++68-20180218-1
ii  qml-module-org-kde-kcm5.42.0-2
ii  qml-module-org-kde-kirigami2  5.42.0-3
ii  qml-module-qtquick-controls   5.9.2-2
ii  qml-module-qtquick-layouts5.9.2-3
ii  qml-module-qtquick2   5.9.2-3

systemsettings recommends no packages.

systemsettings suggests no packages.

-- no debconf information

Bug#892237: [Freewx-maint] Bug#892237: wxpython4.0: FTBFS on hurd-i386: wx*FSW* undeclared

[Scott Talbert]

On Tue, 6 Mar 2018, Aaron M. Ucko wrote:


 ../../../../sip/cpp/sip_corecmodule.cpp:15517:51: error: 
'::wxFSW_EVENT_ACCESS' has not been declared
 [...]
 ../../../../sip/cpp/sip_corecmodule.cpp:15529:55: error: 
'::wxFSW_WARNING_OVERFLOW' has not been declared
 ../../../../sip/cpp/sip_corecmodule.cpp:17889:31: error: 'wxEVT_FSWATCHER' was 
not declared in this scope

Could you please take a look?


Yep, it looks like this is because the wxwidgets3.0 build doesn't have 
wxFileSystemWatcher support, which is because it couldn't find inotify. 
It looks like inotify isn't available on Hurd?


Scott

Bug#892203: kwayland: Implement zwp_linux_dmabuf_v1

[Chris Lamb]

severity 892203 wishlist
severity 892204 wishlist
thanks

Downgrading these to wishlist; "important" is generally reserved for really
major bugs.  :)


Best wishes,

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

Bug#892242: calibre: E-book viewer: use JSON to prevent malicious bookmark files from causing code execution

[Jonatan Nyberg]

package: calibre
severity: high

Change the file format used to import/export bookmarks to use JSON in
the E-book viewer. This prevents malicious bookmarks files from causing
code execution.

Commit: https://github.com/kovidgoyal/calibre/commit/aeb5b036a0bf657951
756688b3c72bd68b6e4a7d

Regards,
Jonatan

Bug#892241: gnustep-back: add gnustep-back package (without version in name)

[tedge]

Source: gnustep-back
Severity: wishlist

After installing the libgnustep-gui-dev package, a gnustep backend package must
also be installed in order to run the built GNUstep GUI apps.

Currently, the gnustep-backend packages are only available with versions in
their name (i.e. "gnustep-back0.26", "gnustep-back0.26-cairo", etc.) which
means that scripts & written instructions for installing a 'libgnustep-gui-
dev'-based build environment have to know the version of the available gnustep-
back package, or have extra steps/logic to figure it out.

If there was a "gnustep-back" package without a version in its name,
instructions & scripts for installing a libgnustep-gui-dev build environment
could simply use the "apt-get install libgnustep-gui-dev gnustep-back" command,
and that command would work with future versions of the gnustep back packages,
without additional logic for finding the versioned package name.



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

Kernel: Linux 4.9.0-3-amd64 (SMP w/1 CPU core)
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)

Bug#892173: e2fsprogs: Bug in German l10n of "Inode 529618 extent tree (at level 1) could be shorter"

[Theodore Y. Ts'o]

To the German, Dutch, and Vietnamese translators of e2fsprogs's po
file, --- I've added you to the cc list because Martin von Wittich has
pointed out the following error in your translation files.  Please
read on

On Tue, Mar 06, 2018 at 01:15:56PM +0100, Martin von Wittich wrote:
> the German localization of the following message:
> 
> some-server ~ # LANG=C e2fsck -f /dev/vg/some-lv
> e2fsck 1.43.4 (31-Jan-2017)
> Pass 1: Checking inodes, blocks, and sizes
> Inode 529618 extent tree (at level 1) could be shorter.  Fix?
> 
> contains uninterpreted escape sequences instead of the actual values:
> 
> some-server ~ # LANG=de_DE.UTF-8 e2fsck -f /dev/vg/some-lv
> e2fsck 1.43.4 (31-Jan-2017)
> Durchgang 1: Inodes, Blöcke und Größen werden geprüft
> Der Erweiterungsbaum von Inode %$i (auf Ebene %$b) könnte kürzer sein.  
> Reparieren?
> 
> If I understand the issue correctly, the translations are attempting to use a
> printf escape that might not be supported by the compiler...? Wikipedia says
> "Parameter field - This is a POSIX extension and not in C99."

Thanks for pointing out the problem.  The issue is that the
translators how they should handle positional ordering issues when
translating e2fsck's message.

This is what is in po/de.po in the e2fsprogs sources:

#. @-expanded: inode %i extent tree (at level %b) could be shorter.  
#: e2fsck/problem.c:1301
msgid "@i %i @x tree (at level %b) could be shorter.  "
msgstr ""
"Der Erweiterungsbaum von Inode %1$i (auf Ebene %2$b) könnte kürzer sein.  "

This is wrong.  It should have simply been:

"Der Erweiterungsbaum von Inode %i (auf Ebene %b) könnte kürzer sein.  "

That's because how e2fsck interprets its own error messages, and it
does its own specialized %-expansion.   From e2fsck/message.c:

 *  %b block number
 *  %Binterpret blkcount as blkcount
 *  %cblock number
 *  %Di ->ino   inode number
 *  %Dn ->name  string
 *  %Dr ->rec_len
 *  %Dl ->name_len
 *  %Dt ->filetype

etc.  So the translators don't need to play magical games with
positional arguments.  They just need to use %i when they want to
print the inode number from the problem context structure.  And they
can use %p if they want e2fsck to try to take a directory inode number
and turn it into a pathname, and print the pathname.  If there is a
timestamp in the num field in the problem context, %t will print it as
a human-readiable date/time stamp.  Ordering doesn't matter, so the
attempt to use %1$i, %2$b, is Just Wrong.

> The following *.po files might be affected:
> 
> martin@dogmeat ~/Projects/e2fsprogs/po % grep -lP '\d\$' *.po
> cs.po
> de.po
> hu.po
> nl.po
> pl.po
> tr.po
> vi.po
> zh_CN.po

Actually, not all of these are buggy.  Using positional arguments is
the right thing to do for messages that are *not* from
e2fsck/problem.c.  It's only the messages from e2fsck/problem.c which
are use the the %-expansion in e2fsck/message.c.  From examination,
the only other languages that are buggy in this way are the Dutch and
Vietnamese translations.  I've cc'ed their translators above.

Thanks again for pointing this out.

Cheers,

- Ted

Bug#892205: marked as done (ITP: magic-wormhole-transit-server -- Transit Relay server for Magic-Wormhole)

[STEPHANIE MANZANO]

how do I unsubscribe…..

On Tue, Mar 6, 2018 at 8:03 PM, Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Your message dated Wed, 07 Mar 2018 04:00:09 +
> with message-id 
> and subject line Bug#892205: fixed in magic-wormhole-transit-relay 0.1.1-1
> has caused the Debian Bug report #892205,
> regarding ITP: magic-wormhole-transit-server -- Transit Relay server for
> Magic-Wormhole
> to be marked as done.
>
> This means that you claim that the problem has been dealt with.
> If this is not the case it is now your responsibility to reopen the
> Bug report if necessary, and/or fix the problem forthwith.
>
> (NB: If you are a system administrator and have no idea what this
> message is talking about, this may indicate a serious mail system
> misconfiguration somewhere. Please contact ow...@bugs.debian.org
> immediately.)
>
>
> --
> 892205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892205
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
> -- Forwarded message --
> From: Antoine Beaupre 
> To: Debian Bug Tracking System 
> Cc:
> Bcc:
> Date: Tue, 06 Mar 2018 13:45:34 -0500
> Subject: ITP: magic-wormhole-transit-server -- Transit Relay server for
> Magic-Wormhole
> Package: wnpp
> Severity: wishlist
> Owner: Antoine Beaupre 
>
> * Package name: magic-wormhole-transit-server
>   Version : 0.1.1
>   Upstream Author : Brian Werner
> * URL : https://github.com/warner/magic-wormhole-transit-relay
> * License : MIT
>   Programming Lang: Python
>   Description : Transit Relay server for Magic-Wormhole
>
> This repository implements the Magic-Wormhole "Transit Relay", a
> server that helps clients establish bulk-data transit connections even
> when both are behind NAT boxes. Each side makes a TCP connection to
> this server and presents a handshake. Two connections with identical
> handshakes are glued together, allowing them to pretend they have a
> direct connection.
>
> This server used to be included in the magic-wormhole repository, but
> was split out into a separate repo to aid deployment and development.
>
> --
>
> will be in collab-maint, new dependency for wormhole.
>
>
> -- Forwarded message --
> From: "Antoine Beaupré" 
> To: 892205-cl...@bugs.debian.org
> Cc:
> Bcc:
> Date: Wed, 07 Mar 2018 04:00:09 +
> Subject: Bug#892205: fixed in magic-wormhole-transit-relay 0.1.1-1
> Source: magic-wormhole-transit-relay
> Source-Version: 0.1.1-1
>
> We believe that the bug you reported is fixed in the latest version of
> magic-wormhole-transit-relay, which is due to be installed in the Debian
> FTP archive.
>
> A summary of the changes between this version and the previous one is
> attached.
>
> Thank you for reporting the bug, which will now be closed.  If you
> have further comments please address them to 892...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Debian distribution maintenance software
> pp.
> Antoine Beaupré  (supplier of updated
> magic-wormhole-transit-relay package)
>
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)
>
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Format: 1.8
> Date: Tue, 06 Mar 2018 18:34:10 +
> Source: magic-wormhole-transit-relay
> Binary: magic-wormhole-transit-relay
> Architecture: source all
> Version: 0.1.1-1
> Distribution: unstable
> Urgency: low
> Maintainer: Antoine Beaupré 
> Changed-By: Antoine Beaupré 
> Description:
>  magic-wormhole-transit-relay - Transit Relay server for Magic-Wormhole
> Closes: 892205
> Changes:
>  magic-wormhole-transit-relay (0.1.1-1) unstable; urgency=low
>  .
>* New magic-wormhole dependency (Closes: #892205)
>* Autogenerated by py2dsp v1.20151008
> Checksums-Sha1:
>  70b5d40fd2d1af9e42b6051ea8f547afdac12a0b 1798
> magic-wormhole-transit-relay_0.1.1-1.dsc
>  87cac3927fd5d5c7767b49a172792d3c675bbefa 37842
> magic-wormhole-transit-relay_0.1.1.orig.tar.gz
>  3fa77d23dcff9f0f79b6e92ef3d480542c0a05c5 5140
> magic-wormhole-transit-relay_0.1.1-1.debian.tar.xz
>  1ffb38d757f7e4549201f407d7885d58acb90674 15560
> magic-wormhole-transit-relay_0.1.1-1_all.deb
>  6cd32503159cd62cd999377ded06de67dca558f5 6472
> magic-wormhole-transit-relay_0.1.1-1_amd64.buildinfo
> Checksums-Sha256:
>  44ff4bab61b2bdbfd5e1bb31a35c05350d976c73677de51ceb11f4b3bf11fa2f 1798
> magic-wormhole-transit-relay_0.1.1-1.dsc
>  faac36266c72745102a1a8b93abc5b25feed1be5bca7b29968a156966c312567 37842
> magic-wormhole-transit-relay_0.1.1.orig.tar.gz
>  0732c7b24226e1d3b08e9fbb445593f7e6b6cf8efb6c2e82e5adecefe115830e 5140
> magic-wormhole-transit-relay_0.1.1-1.debian.tar.xz
>  

Bug#883379: RFS: deepin-voice-recorder/1.3.6-1 [ITP]

[Paul Wise]

On Tue, Mar 6, 2018 at 11:08 PM, Boyuan Yang wrote:

> As previously explained by Yangfl, files in /usr/share/dman/ are
> richtext manuals intended to be read by deepin-manual (which is not in
> Debian Archive yet).

Is there any possibility of renaming this directory to deepin-manual
or deepin-manuals (if deepin-manual is already taken by the
deepin-manual package)? I think dman is too generic and likely to be
confused for something related to man-db.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#887873: linux-image-4.9.0-5-marvell: frequent "usercopy: kernel memory overwrite attempt detected" on QNAP NAS (ARM)

[Menno Finlay-Smits]

On Tue, 6 Mar 2018, at 13:54, Menno Finlay-Smits wrote:
> On Tue, 6 Mar 2018, at 04:57, Yves-Alexis Perez wrote:
> > On Mon, 2018-03-05 at 15:28 +0100, Andrew Lunn wrote:
> > > Would it be possible to try to reproduce this problem with 4.9.86 on
> > > the hardware reporting the issue?
> > 
> > 4.9.82-1+deb9u3 is currently in the archive. Menno, could you give it a 
> > shot?
> 
> Will do. I need to get the NAS back to running Scratch as I went back to 
> Jessie for comparison (similar looking problems there too) but I'll get 
> it done as soon as I can.
> 
> Also, I can confirm that I was indeed copying from an external USB disk 
> with just "rsync -av  ".

The problem still happens with 4.9.82-1+deb9u3.

Here's the dump:

[  675.800163] usercopy: kernel memory overwrite attempt detected to c08f83a0 
() (4294933600 bytes)
[  675.810513] [ cut here ]
[  675.815144] kernel BUG at /build/linux-nLLkbA/linux-4.9.82/mm/usercopy.c:75!
[  675.822215] Internal error: Oops - BUG: 0 [#1] ARM
[  675.827020] Modules linked in: ses enclosure scsi_transport_sas uas 
usb_storage marvell ehci_orion mv643xx_eth mvmdio of_mdio ehci_hcd fixed_phy 
marvell_cesa libphy des_generic xhci_pci xhci_hcd sg usbcore orion_wdt 
usb_common m25p80 spi_nor kirkwood_thermal evdev gpio_keys sunrpc ip_tables 
x_tables ipv6 autofs4 ext4 crc16 jbd2 crc32c_generic fscrypto ecb mbcache 
sd_mod sata_mv libata scsi_mod
[  675.862376] CPU: 0 PID: 2050 Comm: rsync Not tainted 4.9.0-6-marvell #1 
Debian 4.9.82-1+deb9u3
[  675.871022] Hardware name: Marvell Kirkwood (Flattened Device Tree)
[  675.877310] task: c0af32c0 task.stack: c0a7e000
[  675.881857] PC is at __check_object_size+0x120/0x1d8
[  675.886840] LR is at __check_object_size+0x120/0x1d8
[  675.891821] pc : []lr : []psr: 6013
   sp : c0a7fdb8  ip :   fp : c0a7ff08
[  675.903339] r10: c0a7e000  r9 : 7c60  r8 : c08f83a0
[  675.908579] r7 : c08f  r6 :   r5 : 7c60  r4 : c08f83a0
[  675.915128] r3 : c0555080  r2 : c055a3a4  r1 : c05509f0  r0 : 0065
[  675.921677] Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment none
[  675.928835] Control: 0005397f  Table: 00b44000  DAC: 0051
[  675.934599] Process rsync (pid: 2050, stack limit = 0xc0a7e190)
[  675.940538] Stack: (0xc0a7fdb8 to 0xc0a8)
[  675.944908] fda0:   
c04634c4 7c60
[  675.953116] fdc0: 000103a8 7c60 8000 c0a7fec0 c08f83a0 c0202dd0 
0008 00cfbff0
[  675.961329] fde0: dfc09d00 c08e8000 0051 0008 c0a7fec0 8000 
0008 0008
[  675.969535] fe00: 8000  dead4e40 8008 c0496ed1 c02fcf5c 
dead4e40 c0a7fec0
[  675.977749] fe20: c0a7fec0  8008 dead4e40 c08be920 c0a7feb8 
0001 
[  675.985964] fe40: c08beb60 c03a2f80 c0a7fe64 0003 dec8e2e0 8000 
0008 8008
[  675.994178] fe60: 5a9f1704      
 
[  676.002392] fe80: c0ace700 c0a7feb8 dec8e2e0 dec8e2e0 c0a892a0 00cebc48 
c0a7e000 
[  676.010607] fea0: 00511e6c c02ef4a8 c0a7ff10 c0a7ff28 dec8e2e0 c02ef548 
 
[  676.018821] fec0: 0001 0008 8000 c0a7ff08 0001 3b9a9904 
 
[  676.027035] fee0: 0040 c0a7ff28   c0a892a0 c0a7ff88 
8008 c01144c0
[  676.035249] ff00: 8008  00cebc48 8008 0001  
8008 c0a7ff08
[  676.043454] ff20: 0001 3b9a9904 c0a892a0    
 
[  676.051660] ff40:    c0a892a0 8008  
c0a7ff88 c011512c
[  676.059865] ff60: c0a892a0 00cebc48 8008 c0a892a0 c0a892a0 00cebc48 
8008 c000f724
[  676.068071] ff80: c0a7e000 c0115fe0   8008 00511e6c 
bef86848 bef867c8
[  676.076277] ffa0: 0004 c000f560 00511e6c bef86848 0004 00cebc48 
8008 00cebc48
[  676.084490] ffc0: 00511e6c bef86848 bef867c8 0004 0051fa80 00511e84 
0050f95c 00511e6c
[  676.092696] ffe0:  bef8666c 004c5978 b6ef7d1c 4010 0004 
1fffd871 1fffdc71
[  676.100910] [] (__check_object_size) from [] 
(copy_page_from_iter+0x2e8/0x3d0)
[  676.109915] [] (copy_page_from_iter) from [] 
(skb_copy_datagram_from_iter+0xfc/0x188)
[  676.119524] [] (skb_copy_datagram_from_iter) from [] 
(unix_stream_sendmsg+0x208/0x2f8)
[  676.129218] [] (unix_stream_sendmsg) from [] 
(sock_sendmsg+0x3c/0x50)
[  676.137430] [] (sock_sendmsg) from [] 
(sock_write_iter+0x8c/0xb4)
[  676.145297] [] (sock_write_iter) from [] 
(new_sync_write+0xc0/0xe4)
[  676.153337] [] (new_sync_write) from [] 
(vfs_write+0xc0/0x194)
[  676.160941] [] (vfs_write) from [] (SyS_write+0x44/0x7c)
[  676.168023] [] (SyS_write) from [] 
(ret_fast_syscall+0x0/0x44)
[  676.175625] Code: e59f10a0 01a01000 e59f009c ebff0495 (e7f001f2)
[  676.181748] ---[ end trace 09357b62c70de3ea ]---

What else can I try? There doesn't appear to be a newer kernel in proposed 

Bug#892145: undertime enhancement: different start/end times for each timezone

[Paul Wise]

On Tue, 2018-03-06 at 09:22 -0500, Antoine Beaupré wrote:

> How does that sound?

That sounds like you would get someone filing a bug about it :)

It might be best to avoid implementing this until argparse can do it,
or until we figure out how to do it with argparse.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#892240: diffoscope: crashes comparing directories with python3-xattr installed

[Paul Wise]

Package: diffoscope
Version: 91
Severity: wishlist 
Usertags: crash

diffoscope crashes when comparing directories when the python3-xattr
package is installed but the python3-pyxattr package is not installed.

I would suggest that diffoscope should either conflict with the
incompatible python3-xattr package (as python3-pyxattr does), or
add support for the API provided by the python3-xattr package.

Personally I would prefer the latter, since python3-xattr has a
useful command-line tool in the xattr package that I sometimes use.

$ mkdir foo bar
$ diffoscope foo bar
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/diffoscope/main.py", line 422, in main
sys.exit(run_diffoscope(parsed_args))
  File "/usr/lib/python3/dist-packages/diffoscope/main.py", line 394, in 
run_diffoscope
difference = compare_root_paths(path1, path2)
  File 
"/usr/lib/python3/dist-packages/diffoscope/comparators/utils/compare.py", line 
62, in compare_root_paths
return compare_directories(path1, path2)
  File "/usr/lib/python3/dist-packages/diffoscope/comparators/directory.py", 
line 165, in compare_directories
return FilesystemDirectory(path1).compare(FilesystemDirectory(path2))
  File "/usr/lib/python3/dist-packages/diffoscope/comparators/directory.py", 
line 216, in compare
differences.extend(compare_meta(self.name, other.name))
  File "/usr/lib/python3/dist-packages/diffoscope/comparators/directory.py", 
line 161, in compare_meta
differences.append(xattr(path1, path2))
  File "/usr/lib/python3/dist-packages/diffoscope/comparators/directory.py", 
line 124, in xattr
fn(path1), fn(path2), path1, path2, source='extended file attributes',
  File "/usr/lib/python3/dist-packages/diffoscope/comparators/directory.py", 
line 121, in fn
) for k, v in sorted(xattr.get_all(x)))
AttributeError: module 'xattr' has no attribute 'get_all'

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages diffoscope depends on:
ii  python33.6.4-1
ii  python3-distro 1.0.1-2
ii  python3-libarchive-c   2.1-3.1
ii  python3-magic  2:0.4.15-1
ii  python3-pkg-resources  38.4.0-1

Versions of packages diffoscope recommends:
ii  abootimg 0.6-1+b2
ii  acl  2.2.52-3+b1
ii  apktool  2.3.1+dfsg-1
ii  binutils-multiarch   2.30-5
ii  bzip21.0.6-8.1
ii  caca-utils   0.99.beta19-2+b2
ii  colord   1.3.3-2
ii  db-util  5.3.1
ii  default-jdk [java-sdk]   2:1.8-59
ii  default-jdk-headless 2:1.8-59
pn  device-tree-compiler 
pn  docx2txt 
ii  e2fsprogs1.43.9-2
ii  enjarify 1:1.0.3-3
ii  fontforge-extras 0.3-4
pn  fp-utils 
ii  genisoimage  9:1.1.11-3+b2
ii  gettext  0.19.8.1-4
ii  ghc  8.0.2-11
ii  ghostscript  9.22~dfsg-2
ii  giflib-tools 5.1.4-2
ii  gnupg2.2.5-1
ii  imagemagick  8:6.9.9.34+dfsg-3
ii  imagemagick-6.q16 [imagemagick]  8:6.9.9.34+dfsg-3
ii  jsbeautifier 1.6.4-6
pn  libarchive-tools 
ii  llvm 1:4.0-40
pn  mono-utils   
pn  odt2txt  
pn  oggvideotools
ii  openjdk-8-jdk [java-sdk] 8u151-b12-1
ii  openssh-client   1:7.6p1-4
ii  pdftk2.02-4+b2
ii  pgpdump  0.31-0.2
ii  poppler-utils0.61.1-2
pn  procyon-decompiler   
ii  python3-argcomplete  1.8.1-1
ii  python3-binwalk  2.1.1-16
ii  python3-debian   0.1.32
pn  python3-defusedxml   
pn  python3-guestfs  
ii  python3-jsondiff 1.1.1-1
ii  python3-progressbar  2.3-4
ii  python3-rpm  4.14.0+dfsg1-2
ii  python3-tlsh 3.4.4+20151206-1+b3
ii  python3-xattr [python3-pyxattr]  0.9.3-1
pn  r-base-core  
ii  rpm2cpio 4.14.0+dfsg1-2
ii  sng  1.1.0-1+b1
ii  sqlite3  3.22.0-1
ii  squashfs-tools  

Bug#892239: ki18n: please version doxygen B-D per upstream

[Aaron M. Ucko]

Source: ki18n
Version: 5.42.0-3
Severity: important
Justification: fails to build from source (but built successfully in the past)
User: debian-powe...@lists.debian.org
Usertags: powerpcspe

Builds of ki18n for powerpcspe (admittedly not a release architecture)
have been failing lately:

  CMake Error at 
/usr/share/cmake-3.9/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
Could NOT find Doxygen: Found unsuitable version "1.8.12", but required is
at least "1.8.13" (found /usr/bin/doxygen)

(Doxygen is out of date on this architecture, apparently due to Ruby
stack issues.)

Could you please version the build dependency on doxygen to (>= 1.8.13~)
to match upstream's requirements?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#892238: gegl: FTBFS on hurd-i386: test-buffer-sharing failure (timeout?)

[Aaron M. Ucko]

Source: gegl
Version: 0.3.28-2
Severity: important
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
User: debian-h...@lists.debian.org
Usertags: hurd

Builds of gegl for hurd-i386 (admittedly not a release architecture)
have been failing lately, as detailed in [1]:

  timeout!
  FAIL
  ./test-buffer-sharing
  FAIL test-buffer-sharing

Could you please take a look?

Thanks!

[1] 
https://buildd.debian.org/status/fetch.php?pkg=gegl=hurd-i386=0.3.28-2=1519292905=0

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#892237: wxpython4.0: FTBFS on hurd-i386: wx*FSW* undeclared

[Aaron M. Ucko]

Source: wxpython4.0
Version: 4.0.1+dfsg-1
Severity: normal
Tags: upstream
User: debian-h...@lists.debian.org
Usertags: hurd

The build of wxpython4.0 for hurd-i386 (admittedly not a release
architecture) failed, as detailed in [1]:

  ../../../../sip/cpp/sip_corecmodule.cpp:15517:51: error: 
'::wxFSW_EVENT_ACCESS' has not been declared
  [...]
  ../../../../sip/cpp/sip_corecmodule.cpp:15529:55: error: 
'::wxFSW_WARNING_OVERFLOW' has not been declared
  ../../../../sip/cpp/sip_corecmodule.cpp:17889:31: error: 'wxEVT_FSWATCHER' 
was not declared in this scope

Could you please take a look?

Thanks!

[1] 
https://buildd.debian.org/status/fetch.php?pkg=wxpython4.0=hurd-i386=4.0.1%2Bdfsg-1=1519216613=0

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#892236: ruby-grpc: FTBFS on powerpc (big-endian): Unable to add defs to DescriptorPool

[Aaron M. Ucko]

Source: ruby-grpc
Version: 1.3.2+debian-4
Severity: normal
Tags: upstream
User: debian-powe...@lists.debian.org
Usertags: powerpc

Builds of ruby-grpc for powerpc (the only big-endian architecture on
which its build dependencies are all available, though admittedly not
a release architecture) have been failing, as detailed in [1]:

  An error occurred while loading 
/«BUILDDIR»/ruby-grpc-1.3.2+debian/src/ruby/spec/pb/health/checker_spec.rb.
  Failure/Error:
Google::Protobuf::DescriptorPool.generated_pool.build do
  add_message "grpc.health.v1.HealthCheckRequest" do
optional :service, :string, 1
  end
  add_message "grpc.health.v1.HealthCheckResponse" do
optional :status, :enum, 1, 
"grpc.health.v1.HealthCheckResponse.ServingStatus"
  end
  add_enum "grpc.health.v1.HealthCheckResponse.ServingStatus" do
value :UNKNOWN, 0
value :SERVING, 1
  
  RuntimeError:
Unable to add defs to DescriptorPool: couldn't resolve name 
'.grpc.health.v1.HealthCheckResponse.ServingStatus' in message 
'grpc.health.v1.HealthCheckResponse'

Could you please take a look?

Thanks!

[1] 
https://buildd.debian.org/status/fetch.php?pkg=ruby-grpc=powerpc=1.3.2%2Bdebian-4=1519229357=0

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#892234: nut: FTBFS on ia64: symbols not as expected

[James Clarke]

On 7 Mar 2018, at 02:15, Aaron M. Ucko  wrote:
> Source: nut
> Version: 2.7.4-7
> Severity: normal
> User: debian-i...@lists.debian.org
> Usertags: ia64
> 
> Builds of nut for ia64 (admittedly not a release architecture) have
> been failing with .symbols discrepancies, as detailed at [1].  Could
> you please take a look?

Dear maintainer,
SymbolsHelper is a useful tool but, but most of the time is unnecessary and
leads to a whole load of extra work, since it only whitelists/blacklists
architectures rather than looking for patterns. In this case, it looks like a
lot of these symbols should be using arch-bits=32 and arch-bits=64 rather than
whitelisting or blacklisting all the 64-bit architectures.

Regards,
James

Bug#892235: conman: Please update Conman to the latest version: 0.2.9

[Bryan Seitz]

Package: conman
Version: 0.2.7-1+b1
Severity: wishlist
Tags: upstream

Dear Maintainer,

Report is to request an upgrade to latest version, package functionality is ok 
currently.

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

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

Versions of packages conman depends on:
ii  libc62.26-6
pn  libipmiconsole2  
ii  libwrap0 7.6.q-27

conman recommends no packages.

Versions of packages conman suggests:
pn  expect  

Bug#892234: nut: FTBFS on ia64: symbols not as expected

[Aaron M. Ucko]

Source: nut
Version: 2.7.4-7
Severity: normal
User: debian-i...@lists.debian.org
Usertags: ia64

Builds of nut for ia64 (admittedly not a release architecture) have
been failing with .symbols discrepancies, as detailed at [1].  Could
you please take a look?

Thanks!

[1] 
https://buildd.debian.org/status/fetch.php?pkg=nut=ia64=2.7.4-7=1519214125=0

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#892233: guile-2.2: FTBFS on x32: meta/guile test times out with no output

[Aaron M. Ucko]

Source: guile-2.2
Version: 2.2.3+1-3
Severity: important
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
User: debian-...@lists.debian.org
Usertags: x32

Hi, Rob.

Builds of guile-2.2 for x32 (admittedly not a release architecture)
have been failing lately:

  Testing /<>/guile-2.2-2.2.3+1/meta/guile ...
  with GUILE_LOAD_PATH=/<>/guile-2.2-2.2.3+1/test-suite
  E: Build killed with signal TERM after 600 minutes of inactivity

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#892232: guile-2.2: FTBFS on alpha: test-conversion fails

[Aaron M. Ucko]

Source: guile-2.2
Version: 2.2.3+1-3
Severity: normal
Tags: upstream

Hi, Rob.

Builds of guile-2.2 for alpha (admittedly not a release architecture)
have been failing:

  fail: scm_to_double (12) = -3.58805e+199
  FAIL: test-conversion
  [...]
  ==
  1 of 39 tests failed
  Please report to bug-gu...@gnu.org
  ==

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#892231: sdformat: FTBFS on hurd-i386: PATH_MAX undeclared

[Aaron M. Ucko]

Source: sdformat
Version: 6.0.0+dfsg-4
Severity: important
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
User: debian-h...@lists.debian.org
Usertags: hurd

The latest build of sdformat for hurd-i386 (admittedly not a release
architecture) failed:

  /<>/sdformat-6.0.0+dfsg/src/Filesystem.cc:133:21: error: 'PATH_MAX' 
was not declared in this scope

The Hurd notoriously has no static PATH_MAX.  Best practice is to
accommodate whatever you actually encounter, since fixed-size buffers
generally either waste memory or risk being too small.  In particular,
I would suggest taking advantage of realpath's policy of allocating
memory itself if you pass a NULL buffer.  (You'll of course need to
free the resolved path when you're done with it.)

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#892227: [Pkg-javascript-devel] Bug#892227: node-backbone: dependencies fail to resolve when jQuery not installed

[Ben Finney]

On 07-Mar-2018, Jonas Smedegaard wrote:
> Quoting Ben Finney (2018-03-07 01:04:19)
> > $ cat ./source/foo.js
> > "use strict";
> > import 'backbone';
> > 
> > So the Debian package dependencies are all satisfied, but these are
> > not sufficient for Webpack to resolve the Backbone dependencies.
> 
> Backbone by design avoids dependency on jQuery.

And yet, a very simple application that *only* requests ‘backbone’
will fail to build with Webpack because Backbone tries to find jQuery.

In other words: The expectation is that installing Debian packages
‘webpack’ ands ‘node-backbone’ should allow the above application to
build with Webpack.

So, something is wrong with the Debian Backbone, or the Debian
Webpack, or something else.

-- 
 \ “Are you pondering what I'm pondering?” “I think so, Brain, but |
  `\why would anyone want a depressed tongue?” —_Pinky and The |
_o__)   Brain_ |
Ben Finney 


signature.asc
Description: PGP signature

Bug#892229: wireless-regdb: incompatible with Linux kernel 4.15

[Ben Hutchings]

Control: retitle -1 wireless-regdb: Missing support for kernel direct loading
Control: severity -1 normal

On Wed, 07 Mar 2018 09:04:22 +0800 Paul Wise  wrote:
> Package: wireless-regdb
> Version: 2016.06.10-1
> Severity: serious
> 
> When I booted Debian's package of Linux kernel 4.15 I noticed this in
> my dmesg and systemd journal, it appears that the Linux kernel has
> changed the name (and possibly format) of the regulatory database from
> regulatory.bin to regulatory.db, making the current wireless-regdb
> incompatible with Linux 4.15.
> 
> kernel: cfg80211: failed to load regulatory.db
> kernel: platform regulatory.0: Direct firmware load for regulatory.db failed 
> with error -2
> kernel: platform regulatory.0: firmware: failed to load regulatory.db (-2)
> kernel: cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
> kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory 
> database

wireless-regdb works in conjunction with crda, and that's still
supported (so far as I can see).

The kernel can also now load a signed db without the need for crda. 
That's what's failing.  Unfortunately this was introduced without a
config option, so it will keep producing these error messages until
wireless-regdb is updated.

Ben.

-- 
Ben Hutchings
Never attribute to conspiracy what can adequately be explained
by stupidity.



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

Bug#892226: [Pkg-fonts-devel] Bug#892226: fonts-noto-unhinted: mathematical and arrow symbols missing, that existed previously

[Jonas Smedegaard]

Quoting Ciarán Power (2018-03-07 01:00:27)
> I used the "Noto Sans Symbols" font last year (I think on Debian stretch, but 
> I'm not sure) to generate png output using libmakick++. It worked fine for 
> various arrow and mathematical symbols e.g.:
> the integral symbol: ∫ (U+222B INTEGRAL)
> rightwards double arrow: ⇒ (U+21D2 RIGHTWARDS DOUBLE ARROW)
> 
> I wanted to make some changes, and noticed that I now get empty rectangles in 
> my output, where I had symbols before.
> 
> I tried using "gnome-thumbnail-font" and "font-manager" to search for these 
> symbols, but was unable to find them.
> 
> I looked through the archive of fonts-noto on snapshot.debian.org*. 
> fonts-noto-unhinted_20161116-1_all.deb seems to contain all the symbols I was 
> using in "NotoSansSymbols-Regular.ttf". The current symbols ttf 
> (NotoSansSymbols-Regular & NotoSansSymbols2-Regular) don't seem to contain 
> them.
> 
> *http://snapshot.debian.org/archive/debian/20171029T215600Z/pool/main/f/fonts-noto/
> 
> 
> I think this was broken by commit bc9353da6f625b7a47035de952c2e8fd9e3ae889 in 
> https://github.com/googlei18n/noto-fonts. I don't understand how google's 
> noto-fonts is organized, but it seems that a number of useful symbols were 
> dropped in this commit.
> 
> 
> These are my installed noto fonts:
> ii  fonts-noto-hinted 20171026-2  
> all  "No Tofu" font families with large Unicode coverage 
> (hinted)
> ii  fonts-noto-mono   20171026-2  
> all  "No Tofu" monospaced font family with large Unicode 
> coverage
> ii  fonts-noto-unhinted   20171026-2  
> all  "No Tofu" font families with large Unicode coverage 
> (unhinted)

Hi Ciarán,

Thanks for a well-written bugreport!

Upstream collection of Noto font files include some available both 
hinted and unhinted, and my packaging routines for Debian simply skips 
the unhinted files where both hinted and unhinted exists, by the 
assumptions that the unhinted files contain no additional information 
but are only slimmed down versions of the hinted ones.  Maybe that 
assumpltion is wrong.

Since you mention previously using unhinted fonts, could you please try 
fetch the current _unhinted_ fonts from upstream and check if the 
symbols are missing there as well?  If so, then we should maybe consider 
packaging the unhinted fonts too.


 - 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#892227: [Pkg-javascript-devel] Bug#892227: node-backbone: dependencies fail to resolve when jQuery not installed

[Jonas Smedegaard]

Quoting Ben Finney (2018-03-07 01:04:19)
> Package: node-backbone
> Version: 1.3.3~dfsg-3
> Severity: normal
> 
> The dependencies for ‘node-backbone’ do not allow a Backbone
> application to be built with Webpack.
> 
> =
> $ dpkg --list webpack
> […]
> ii  webpack3.5.6-1  all  Packs CommonJs/AMD modules for 
> the browser
> 
> $ webpack --version
> 3.5.6
> 
> $ cat ./webpack.config.js
> "use strict";
> const path = require('path');
> module.exports = {
> entry: './source/foo.js',
> output: {
> path: path.resolve(__dirname, 'dist'),
> filename: 'app.js',
> },
> resolve: {
> modules: ['/usr/lib/nodejs', '.'],
> },
> resolveLoader: {
> modules: ['/usr/lib/nodejs'],
> },
> };
> 
> $ cat ./source/foo.js
> "use strict";
> import 'backbone';
> 
> $ webpack --config webpack.config.js
> Hash: a9597112585b9ca5fb40
> Version: webpack 3.5.6
> Time: 209ms
>  AssetSize  Chunks Chunk Names
> app.js  129 kB   0  [emitted]  main
>[0] ./source/foo.js 34 bytes {0} [built]
>[1] /usr/share/javascript/backbone/backbone.js 72.2 kB {0} [built]
>[2] (webpack)/buildin/global.js 488 bytes {0} [built]
>[3] /usr/share/javascript/underscore/underscore.js 52.9 kB {0} [built]
> 
> ERROR in /usr/share/javascript/backbone/backbone.js
> Module not found: Error: Can't resolve 'jquery' in 
> '/usr/share/javascript/backbone'
>  @ /usr/share/javascript/backbone/backbone.js 17:4-21:6
>  @ ./source/foo.js
> =
> 
> So the Debian package dependencies are all satisfied, but these are
> not sufficient for Webpack to resolve the Backbone dependencies.

Backbone by design avoids dependency on jQuery.  Applications may use 
jQuery via Backbone, or may choose to instead use Zepto or Lodash, and 
then need themselves to make sure the chosen helper is available.

At http://backbonejs.org/ is listed a few projects choosing to use 
Backbone with Zepto instead of jQuery.


 - 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#852436: delete prior message

[Norman Ramsey]

I spoke too soon.  Going back and bumping the new HTTP timeouts
up to larger values allowed the system to settle down after a few minutes.

I set

HttpLocalTimeout 10
HttpRemoteTimeout 50


and this seems to have done the trick.  There are still occasional bursts
of 100% CPU usage, but they pass quickly.

Thanks, Louis!

Bug#852436: followup---patches not improving issue

[Norman Ramsey]

I downloaded the two patches provided by Louis Rilling, and I applied
them to version 1.11.6-3 to create a non-maintainer upload 1.11.6-3.1,
which I then installed (and all the related .deb) files.  But this did
not resolve the issue.  Status of the related packages is as follows:

ii  cups-browsed   1.11.6-3.1   i386 OpenPrinting CUPS Filters - cups-
ii  cups-browsed-d 1.11.6-3.1   i386 Debug symbols for cups-browsed
ii  cups-filters   1.11.6-3.1   i386 OpenPrinting CUPS Filters - Main 
ii  cups-filters-c 1.11.6-3.1   i386 OpenPrinting CUPS Filters - PPD-l
ii  cups-filters-c 1.11.6-3.1   i386 Debug symbols for cups-filters-co
ii  cups-filters-d 1.11.6-3.1   i386 Debug symbols for cups-filters
ii  libcupsfilters 1.11.6-3.1   i386 OpenPrinting CUPS Filters - Devel
ii  libcupsfilters 1.11.6-3.1   i386 OpenPrinting CUPS Filters - Share
ii  libcupsfilters 1.11.6-3.1   i386 Debug symbols for libcupsfilters1


Could there be some other package I have failed to install?
Or something else I might need to do?


Norman Ramsey

Bug#892230: man.1: Some minor typographic changes in the manual

[Bjarni Ingi Gislason]

Package: man-db
Version: 2.8.2-1
Severity: minor
Tags: patch

Dear Maintainer,

Input file is man.1

Test nr. 1: Remove space at end of lines to simplify other automatic tests to 
improve
typesetting.

173:directive in 

#

Test nr. 2: Enable and fix warnings from 'test-groff'.

Input file is /tmp/man.1

:169 (macro IR): only 1 argument, but more are expected
:330 (macro BR): only 1 argument, but more are expected
:916 (macro IR): only 1 argument, but more are expected
:1180 (macro BR): only 1 argument, but more are expected
:1402 (macro BR): only 1 argument, but more are expected

chk_manuals: Output is from: test-groff -Tutf8 -b -e -mandoc -rF0 -t -w w -z 

Test nr. 15:   Change the name of a macro for two fonts (e.g., BR and IR) to 
one letter,
if there is only one argument.
Add the second argument if needed.  It is sometimes part of the first one.

169:.IR sections
330:.BR dvips.
916:.IR x
1180:.BR \-\-usage
1402:.BR FSSTND

#

Test nr. 8: Protect a full stop (.) with \&, if it has a blank (white-space) in 
front
of or (ignoring transparent characters to the full stop) after it, and it does
not mean an end of a sentence.

1409:30th April 1994 \(en 23rd February 2000: Wilf. (g.wilf...@ee.surrey.ac.uk)

#

Test nr. 20: Use a macro to change to the italic font, instead of \fI [1], if
possible.
The macros have the italic corrections.
[1] man-pages(7)

291:from section \fI7\fR.

#

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

1110:.I groff -mandoc
1167:.I groff -mandoc

#

Test nr. 27: Split lines longer than 80 characters into two or more
lines.

man.1: line 170 length 108
man.1: line 1232length 85

#

Test nr. 28: The "indicator" is an "end-of-sentence character" (.!?).

  The space between sentences in "roff" is two spaces.
Better is to begin each sentence on a new line to avoid different
writers' conventions.

  References:

  1) man-pages(7) from package \"man-pages\" or
\"www.kernel.org/doc/man-pages\" section 7 or
\"man7.org/linux/man-pages/man7/man-pages.7.html\":

\"New sentences should be started on new lines.
This makes it easier to see the effect of patches,
which often operate at the level of individual sentences.\"

  2) groff_diff(7) in package \"groff\":

\"In GNU troff, as in UNIX troff, you should always follow a sentence
with either a newline or two spaces.\"

  3) \"info groff\":

  Search for the word \"sentence\" in the output to get more hints about input
conventions.

480:database caches. If the
1409:30th April 1994 \(en 23rd February 2000: Wilf. (g.wilf...@ee.surrey.ac.uk)

#

  NO PATCH

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

2:.\" ** The above line should force tbl to be a preprocessor **
3:.\" Man page for man
4:.\"
5:.\" Copyright (C) 1994, 1995, Graeme W. Wilford. (Wilf.)
6:.\" Copyright (C) 2001, 2002, 2003, 2006, 2007, 2008 Colin Watson.
7:.\"
8:.\" You may distribute under the terms of the GNU General Public
9:.\" License as specified in the file COPYING that comes with the
10:.\" man-db distribution.
11:.\"
12:.\" Sat Oct 29 13:09:31 GMT 1994  Wilf. (g.wilf...@ee.surrey.ac.uk)
13:.\"
19:.\" The general command line
66:.\" The apropos command line
74:.\" The --global-apropos command line
85:.\" The whatis command line
93:.\" The --local command line
126:.\" The --where/--where-cat command line
136:.\" The --catman command line
146:.\" --help and --version
414:.\"`User' manual page hierarchies will have
415:.\".B index
416:.\"caches created `on the fly'.
451:.\"
452:.\" Need a \c to make sure we don't get a space where we don't want one
453:.\"
557:.\" 
635:.\" Compressed nroff source files with a supported compression
636:.\" extension will be decompressed by man prior to being displaying via the
637:.\" usual filters.
688:.\"
689:.\" Due to the rather silly limit of 6 args per request in some `native'
690:.\" *roff compilers, we have do the following to get the two-line
691:.\" hanging tag on one line. .PP to begin a new paragraph, then the
692:.\" tag, then .RS (start relative indent), the text, finally .RE
693:.\" (end relative indent).
694:.\"
918:.\"The default options are
919:.\".BR \-six8 .
923:.\"The actual default will depend on your chosen
924:.\".BR locale .
929:.\"You may need to do this if your
930:.\"version of
931:.\".B less
932:.\"rejects the default options or if you prefer a different prompt.
1202:.\".TP \w'MANROFFSEQ\ \ 'u

#

Test nr. 35: Add a space around "|" to increases readability

1375:.I /usr/share/man/index.(bt|db|dir|pag)
1380:.I /var/cache/man/index.(bt|db|dir|pag)

#

  The patch is in the attachment.

-- System Information:
Debian Release: buster/sid
  APT prefers stable-updates
  APT policy: (500, 

Bug#892229: wireless-regdb: incompatible with Linux kernel 4.15

[Paul Wise]

Package: wireless-regdb
Version: 2016.06.10-1
Severity: serious

When I booted Debian's package of Linux kernel 4.15 I noticed this in
my dmesg and systemd journal, it appears that the Linux kernel has
changed the name (and possibly format) of the regulatory database from
regulatory.bin to regulatory.db, making the current wireless-regdb
incompatible with Linux 4.15.

kernel: cfg80211: failed to load regulatory.db
kernel: platform regulatory.0: Direct firmware load for regulatory.db failed 
with error -2
kernel: platform regulatory.0: firmware: failed to load regulatory.db (-2)
kernel: cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

wireless-regdb depends on no packages.

wireless-regdb recommends no packages.

Versions of packages wireless-regdb suggests:
ii  crda  3.18-1

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#886326: stretch-pu: package zssh/1.5c.debian.1-3.2+deb9u1

[Boyuan Yang]

2018-02-10 19:20 GMT+08:00 Boyuan Yang <073p...@gmail.com>:
> 2018-02-10 19:08 GMT+08:00 Julien Cristau :
>> Control: tag -1 moreinfo
>>
>> On Thu, Jan  4, 2018 at 21:51:12 +0800, Boyuan Yang wrote:
>>
>>> After adoption of package zssh, I'm looking to fix the RC bug #769366 in 
>>> Debian Stretch.
>>> A simple rebuild solved the problem, thus requesting a pre-approval from 
>>> the release team.
>>>
>> What is the issue and how does a rebuild solve it?
>>
>> Thanks,
>> Julien
>
> The issue: zssh on Debian Stretch (at least on amd64 architecture)
> will not start at all and the
> symptom is the same as what happened in Debian Bug #769366.
>
> As described in
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769366#61 , Current
> version
> of zssh in Debian Stretch (on amd64 architecture, versioned
> 1.5c.debian.1-3.2+b4) suffers from
> RC bug #769366. I had little idea why this happened because a
> no-change rebuild on Debian
> Stretch would make zssh fully functional. I tried gdb but the result
> was not helpful.
>
> The previous packager said he once solved this problem in a previous
> upload so the problem
> might have been introduced in one of the latter binNMUs.
>
> How does a rebuild solve it? I have no idea currently: It Just Works™.
> I could have digged into
> the problem but the time to be spent would not be efficient when a
> simple rebuild solves it.
>
> I think those described above should make a stretch-pu for zssh reasonable.
>
> --
> Regards,
> Boyuan Yang

Hi Julien,

A gentle ping on this bug -- wondering if you (or the Release Team) is
going to accept
this solution or not. After all Debian 9.4 is coming and I'd like to
see this fix included
in the next point release.

--
Thanks,
Boyuan Yang

Bug#892224: load error: libIlmImf-2_2.so.22: cannot open shared object file: No such file or directory

[積丹尼 Dan Jacobson]

I could still use the program, but I only tested for a minute.

> "AP" == Ari Pollak  writes:
AP> Is this causing any problems or just a message? 

Bug#892224: load error: libIlmImf-2_2.so.22: cannot open shared object file: No such file or directory

[Ari Pollak]

Is this causing any problems or just a message?

Bug#892228: libsphinxbase3: Causes pocketsphinx to FTBFS on 64-bit big-endian architectures (fills testsuite logs on disk with errors)

[James Clarke]

Package: libsphinxbase3
Version: 0.8+5prealalpha+1-1
Severity: important
Tags: upstream
Control: affects -1 src:pocketsphinx

Hi,
The build for pocketsphinx fails on 64-bit big-endian architectures, failing
with "No space left on device", as the testsuite log files fill up with
hundreds of gigabytes of warnings. The first indication of the problem in the
log files is:

> Sorry, this does not support more than 33554432 n-grams of a particular 
> order.  Edit util/bit_packing.hh and fix the bit packing functions

where 33554432 is 0x200, i.e. 32 byte-swapped. This error isn't fatal
though, and libsphinxbase3 continues to try to build the trie, with tons of
duplicate word warnings, as it's reading all kinds of garbage. The issues stem
from a widespread use of using fread to read multi-byte values with no regard
for their endianness, with the first error, the wrong number of n-grams, coming
from reading into the "counts" array in ngram_model_trie_read_bin. The library
has functions like bio_fread which can do the byte-swapping for the caller, so
presumably these should be used instead, though for this file format there does
not seem to be an easy way to determine the endianness of the file based on
some header magic like for some of the others (but maybe it's intended to
always be little-endian).

32-bit big-endian architectures have the same underlying bugs, but it seems
they die a lot earlier, failing to calloc huge sizes (presumably these same
calls are made on 64-bit architectures but can be satisfied thanks to
overcommitting) and thus don't actually try to build the trie and spew all the
warnings.

There are "only" 62 calls to fread in sphinxbase (and a further 45 in
pocketsphinx) so it shouldn't be too hard for someone with knowledge of the
codebase to audit their uses, especially since my guess is that most of them
can be turned into something like `bio_fread(..., IS_BIG_ENDIAN)`. Similarly,
the corresponding fwrite calls should be audited too.

Regards,
James

Bug#886769: Pending fixes for bugs in the golang-github-go-debos-fakemachine package

[pkg-go-maintainers]

tag 886769 + pending
thanks

Some bugs in the golang-github-go-debos-fakemachine package are
closed in revision ce5b81bf63762b51b546e79f7bfd6e71087c5a44 in branch
'master' by Héctor Orón Martínez

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-go-debos-fakemachine.git/commit/?id=ce5b81b

Commit message:

Import Debian changes 0.0~git20180126.e307c2f-1

golang-github-go-debos-fakemachine (0.0~git20180126.e307c2f-1) unstable; 
urgency=medium

  * Initial release (Closes: #886769)

Bug#892227: node-backbone: dependencies fail to resolve when jQuery not installed

[Ben Finney]

Package: node-backbone
Version: 1.3.3~dfsg-3
Severity: normal

The dependencies for ‘node-backbone’ do not allow a Backbone
application to be built with Webpack.

=
$ dpkg --list webpack
[…]
ii  webpack3.5.6-1  all  Packs CommonJs/AMD modules for the 
browser

$ webpack --version
3.5.6

$ cat ./webpack.config.js
"use strict";
const path = require('path');
module.exports = {
entry: './source/foo.js',
output: {
path: path.resolve(__dirname, 'dist'),
filename: 'app.js',
},
resolve: {
modules: ['/usr/lib/nodejs', '.'],
},
resolveLoader: {
modules: ['/usr/lib/nodejs'],
},
};

$ cat ./source/foo.js
"use strict";
import 'backbone';

$ webpack --config webpack.config.js
Hash: a9597112585b9ca5fb40
Version: webpack 3.5.6
Time: 209ms
 AssetSize  Chunks Chunk Names
app.js  129 kB   0  [emitted]  main
   [0] ./source/foo.js 34 bytes {0} [built]
   [1] /usr/share/javascript/backbone/backbone.js 72.2 kB {0} [built]
   [2] (webpack)/buildin/global.js 488 bytes {0} [built]
   [3] /usr/share/javascript/underscore/underscore.js 52.9 kB {0} [built]

ERROR in /usr/share/javascript/backbone/backbone.js
Module not found: Error: Can't resolve 'jquery' in 
'/usr/share/javascript/backbone'
 @ /usr/share/javascript/backbone/backbone.js 17:4-21:6
 @ ./source/foo.js
=

So the Debian package dependencies are all satisfied, but these are
not sufficient for Webpack to resolve the Backbone dependencies.


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

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

Versions of packages node-backbone depends on:
ii  libjs-backbone   1.3.3~dfsg-3
ii  node-underscore  1.8.3~dfsg-1
ii  nodejs   8.9.3~dfsg-12

node-backbone recommends no packages.

Versions of packages node-backbone suggests:
ii  libjs-jquery-lazyload  1.7.2-1

-- no debconf information

-- 
 \  “When we talk to God, we're praying. When God talks to us, |
  `\ we're schizophrenic.” —Jane Wagner, via Lily Tomlin, 1985 |
_o__)  |
Ben Finney 


signature.asc
Description: PGP signature

Bug#892226: fonts-noto-unhinted: mathematical and arrow symbols missing, that existed previously

[Ciarán Power]

Package: fonts-noto-unhinted
Version: 20171026-2
Severity: normal
Tags: upstream

Dear Maintainer,

I used the "Noto Sans Symbols" font last year (I think on Debian stretch, but 
I'm not sure) to generate png output using libmakick++. It worked fine for 
various arrow and mathematical symbols e.g.:
the integral symbol: ∫ (U+222B INTEGRAL)
rightwards double arrow: ⇒ (U+21D2 RIGHTWARDS DOUBLE ARROW)

I wanted to make some changes, and noticed that I now get empty rectangles in 
my output, where I had symbols before.

I tried using "gnome-thumbnail-font" and "font-manager" to search for these 
symbols, but was unable to find them.

I looked through the archive of fonts-noto on snapshot.debian.org*. 
fonts-noto-unhinted_20161116-1_all.deb seems to contain all the symbols I was 
using in "NotoSansSymbols-Regular.ttf". The current symbols ttf 
(NotoSansSymbols-Regular & NotoSansSymbols2-Regular) don't seem to contain them.

*http://snapshot.debian.org/archive/debian/20171029T215600Z/pool/main/f/fonts-noto/


I think this was broken by commit bc9353da6f625b7a47035de952c2e8fd9e3ae889 in 
https://github.com/googlei18n/noto-fonts. I don't understand how google's 
noto-fonts is organized, but it seems that a number of useful symbols were 
dropped in this commit.


These are my installed noto fonts:
ii  fonts-noto-hinted 20171026-2
  all  "No Tofu" font families with large Unicode coverage (hinted)
ii  fonts-noto-mono   20171026-2
  all  "No Tofu" monospaced font family with large Unicode coverage
ii  fonts-noto-unhinted   20171026-2
  all  "No Tofu" font families with large Unicode coverage 
(unhinted)

Thanks,
Ciarán


-- Package-specific info:
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version   Architecture 
 Description
+++--=-=-==
ii  fontconfig   2.12.6-0.1amd64
 generic font configuration library - support binaries
ii  libfreetype6:amd64   2.8.1-2   amd64
 FreeType 2 font engine, shared library files
ii  libxft2:amd642.3.2-1+b2amd64
 FreeType-based font drawing library for X

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

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

-- no debconf information

Bug#891855: fonts-monoid: installs no less than 4000 font files!

[Jan Claeys]

On Sun, 2018-03-04 at 15:16 +0100, Fabian Greffrath wrote:
> I am already done with implementing my suggested changes. While at
> it, does it make any sense at all to include the variants which
> differ only in line hight? I mean, line hight is usually defined by
> the application rendering the font and it is not that we have any
> means to influence that by explicitely selecting a different font
> style, anyway?

Line height is usually not configurable in a terminal, and for
characters in e.g. the "Box Drawing" & "Block Elements" ranges there is
also the issue that they need to connect.  That's probably why the
different styles exist?  (I didn't check if they actually do that.)


I wonder if it would be better to build them on-demand, using debconf
to select what variant(s) is/are wanted...  But then you'd need all the
dependencies to build them installed to use the font, of course.


-- 
Jan Claeys

Bug#892221: python-jpype: FTBFS on hurd-i386: jni_md_platform is not defined

[James Clarke]

Control: clone -1 -2
Control: reassign -2 gcj-6 6.4.0-12
Control: retitle -2 gcj-6: jawt_md.h and jni_md.h are in linux subdirectory on 
kFreeBSD and GNU/Hurd

On 6 Mar 2018, at 22:50, Aaron M. Ucko  wrote:
> 
> Source: python-jpype
> Version: 0.6.2+dfsg-2
> Severity: normal
> Tags: upstream
> User: debian-h...@lists.debian.org
> Usertags: hurd
> 
> Builds of python-jpype for hurd-i386 (admittedly not a release
> architecture) have been failing, as most recently seen in [1]:
> 
>  setup.py:91: UserWarning: Your platform is not being handled explicitly. It 
> may work or not!
>" It may work or not!", UserWarning)
>  Traceback (most recent call last):
>File "setup.py", line 95, in 
>  [os.path.join(java_home, 'include', jni_md_platform)]
>  NameError: name 'jni_md_platform' is not defined
> 
> Per [2], the appropriate directory name here appears to be linux(!).
> Also, sys.platform starts with "gnu" on the Hurd.

I personally think this is a bug in GCJ. OpenJDK puts them in the
$(OPENJDK_TARGET_OS) subdirectory[0] (except Windows uses win32 and macOS uses
darwin), so if it were ported to the Hurd it would presumably use either "gnu"
or "hurd" as the subdirectory name. FreeBSD's fork of OpenJDK uses "freebsd"
for the directory name[1], but GCJ also puts the files in "linux" there[2]. I
guess GCJ should be patched (and the Hurd porters should decide on a directory
name to use).

Regards,
James

[0] 
http://hg.openjdk.java.net/jdk10/jdk10/jdk/file/777356696811/make/copy/CopyCommon.gmk#l31
[1] 
https://svnweb.freebsd.org/ports/head/java/openjdk8/files/patch-bsd?view=markup=460849#l8874
[2] https://github.com/gcc-mirror/gcc/blob/gcc-6-branch/libjava/Makefile.am#L907

https://github.com/gcc-mirror/gcc/blob/gcc-6-branch/libjava/Makefile.am#L942-L945

Bug#892142: debian-policy: update example to use default-mta instead of exim

[Sean Whitton]

control: tag -1 +pending

Hello,

On Mon, Mar 05 2018, Jonathan Nieder wrote:

> This is non-normative, so a policy editor can just make the change.

Indeed.

> How about this patch?  It should be possible to apply by downloading
> this message as an mbox and using "git am --scissors mbox-file".

Or `M-x notmuch-pipe ( cd ~/src/debian-policy && git am --scissors )` :)

... except that it doesn't actually apply to the changelog because there
is fuzz, and `git am` is apparently intolerant of any fuzz.

`patch -p1 <.git/rebase-apply/patch && git add . && git am --continue`
did the trick.

Thank you for the patch.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#892224: load error: libIlmImf-2_2.so.22: cannot open shared object file: No such file or directory

[積丹尼 Dan Jacobson]

Package: gimp
Version: 2.8.20-2

# su - nobody
No directory, logging in with HOME=/
nobody@jidanni6:/$ HOME=/tmp gimp
GEGL-Message: 07:35:05.564: Module 
'/usr/lib/x86_64-linux-gnu/gegl-0.3/exr-save.so' load error: 
libIlmImf-2_2.so.22: cannot open shared object file: No such file or directory
GEGL-Message: 07:35:05.800: Module 
'/usr/lib/x86_64-linux-gnu/gegl-0.3/exr-load.so' load error: 
libIlmImf-2_2.so.22: cannot open shared object file: No such file or directory

(gimp:14150): GLib-GObject-WARNING **: 07:35:07.131: 
g_object_set_is_valid_property: object class 'GeglConfig' has no property named 
'cache-size'

Bug#891963: [Ceph-maintainers] Bug#891963: ceph: CVE-2018-7262

[Gaudenz Steinlin]

Hi 

Salvatore Bonaccorso  writes:
> Hi,
>
> the following vulnerability was published for ceph.
>
> CVE-2018-7262[0]:
> |Malformed HTTP requests handled in rgw_civetweb.cc:RGW::init_env() can
> |lead to NULL pointer dereference

Thanks for the information. I backported the upstream fix to the version
in stretch and I'm currently in the process of building the package
(takes several hours). How do you want me to proceed if the package
builds fine and testing does not result in any errors?

This may lead to a crash of the RGW process if sent a malformed HTTP
header which could result in a denial of service. Does this warrant an
upload to security or should this only be fixed via a stable point
release? Do you want to review the debdiff before the upload? The
debdiff of the test package I'm currently building is attached to this
mail.

FYI RGW is the part of Ceph which implements the Amazon S3 API on top of
the Ceph distributed storage.

Gaudenz



ceph_10.2.5-7.2+deb9u1.debdiff
Description: Binary data

-- 
PGP: 836E 4F81 EFBB ADA7 0852 79BF A97A 7702 BAF9 1EF5


signature.asc
Description: PGP signature

Bug#892223: seqan2: FTBFS on sparc64: 39 tests failed out of 403

[Aaron M. Ucko]

Source: seqan2
Version: 2.4.0+dfsg-8
Severity: normal
Tags: upstream
User: debian-sp...@lists.debian.org
Usertags: sparc64

Builds of seqan2 for sparc64 (admittedly not a release architecture)
have been failing lately, per the below excerpt from [1].  The tests
that "Failed" generally if not always returned -10, presumably
corresponding to having encountered SIGBUS (10 on this architecture)
-- no surprise, since sparc64 is notoriously strict about memory
access alignment.

Could you please take a look?

Thanks!

[1] 
https://buildd.debian.org/status/fetch.php?pkg=seqan2=sparc64=2.4.0%2Bdfsg-8=1519554692=0

--

90% tests passed, 39 tests failed out of 403

Total Test time (real) = 324.89 sec

The following tests FAILED:
 15 - test_test_bam_io (SEGFAULT)
 43 - test_test_index_creation (SEGFAULT)
 44 - test_test_index_crosscompare_char (SEGFAULT)
 46 - test_test_index_crosscompare_dna (SEGFAULT)
 52 - test_test_index_fm_rank_dictionary (SEGFAULT)
 54 - test_test_index_base (SEGFAULT)
 55 - test_test_index_fm (SEGFAULT)
 56 - test_test_index_bifm (SEGFAULT)
 57 - test_test_index_vstree (SEGFAULT)
 58 - test_test_index_stree_iterators (SEGFAULT)
 60 - test_test_index_finder (SEGFAULT)
 79 - test_reduced_aminoacid (SEGFAULT)
 93 - test_test_seq_io (SEGFAULT)
101 - test_test_store (SEGFAULT)
102 - test_test_stream (SEGFAULT)
104 - test_test_tabix_io (SEGFAULT)
119 - test_demo_dox_find_finder_index (Failed)
138 - test_demo_dox_index_getOccurrences_getFrequency_range_getFibre 
(Failed)
141 - test_demo_dox_index_length_countSequences (Failed)
143 - test_demo_dox_index_open_save (Failed)
204 - test_demo_tutorial_file_io_overview_example1 (Failed)
205 - test_demo_tutorial_file_io_overview_solution1 (Failed)
206 - test_demo_tutorial_file_io_overview_solution2 (Failed)
207 - test_demo_tutorial_file_io_overview_solution3 (Failed)
230 - test_demo_tutorial_index_iterators_index_assignment1 (Failed)
231 - test_demo_tutorial_index_iterators_index_assignment2 (Failed)
232 - test_demo_tutorial_index_iterators_index_bidirectional_search 
(Failed)
238 - test_demo_tutorial_index_iterators_iterator_solution1 (Failed)
246 - test_demo_tutorial_indices_base (Failed)
304 - test_demo_tutorial_pattern_matching_find_index_multiple (Failed)
314 - test_demo_tutorial_sam_and_bam_io_example7 (Failed)
378 - app_test_bs_tools (Failed)
383 - app_test_mason2 (Failed)
385 - app_test_ngs_roi (Failed)
388 - app_test_rabema (Failed)
390 - app_test_razers3 (Failed)
391 - app_test_razers3_sequential (Failed)
394 - app_test_samcat (Failed)
397 - app_test_seqcons2 (Failed)
Errors while running CTest

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#829589: RFP: jedi-el -- Python auto-completion package for Emacs

[Francois Marier]

> This package needs other software, that is not yet in Debian:
> 
>  - EPC (https://github.com/kiwanami/emacs-epc)

Now available as elpa-epc.

>  - deferred.el (https://github.com/kiwanami/emacs-deferred)

elpa-deferred

>  - python-environment.el (https://github.com/tkf/emacs-python-environment)

elpa-python-environment

>  - python-epc (https://github.com/tkf/python-epc)

That one is still not available in Debian.

Francois

-- 
https://fmarier.org/

Bug#892222: seqan2: FTBFS on hppa: app_test_seqan_tcoffee fails on 2trx.mlcs.fasta

[Aaron M. Ucko]

Source: seqan2
Version: 2.4.0+dfsg-8
Severity: normal
Tags: upstream
User: debian-h...@lists.debian.org
Usertags: hppa

Greetings.

Builds of seqan2 for hppa (admittedly not a release architecture) have
been failing lately, per the below excerpts from [1].

Could you please take a look?

Thanks!

[1] 
https://buildd.debian.org/status/fetch.php?pkg=seqan2=hppa=2.4.0%2Bdfsg-8=1519074087=0

--

392/401 Test #395: app_test_seqan_tcoffee 
***Failed   20.75 
sec
Comparing 
/<>/seqan2-2.4.0+dfsg/apps/seqan_tcoffee/tests/2trx.mlcs.fasta 
against /tmp/tmp1bkmRo/2trx.mlcs.fasta
--- 

+++ 

@@ -1,24 +1,24 @@

 >1thx
-AE-QPVL---V--YFWA-S--WCGPCQ---LM---SPLIN--LA
-ANT-YSD-R---L---KV--V--KLE-IDP--NPTTVKKYK--VE---
-GV-PA--LRL--V-K-GEQILD-STE--
--G--V---IS--K--DKLLSFLDTH--LN---
---
+AE-QPVL---V--YFWA-S--WCGPCQL-MS--PLINLAANTY---SD
+-R---L---KV---VK--L-EI--DPNPTTVKKYK---V-
+-EG-V-PA-LRL--V-K---GE---Q-ILDSTE---
+-G--VI-SK---DKLLSF-LD---TH---LN-
+
 >1grx
---MQ---T--V-I-FG-RSG-C--P---
-YS-VRAKDLA-EK-L-SN---ER-D-DFQ--Y-QYV
--DIRA-EGITK-ED---LQQ--KAG-K--PVET-VPQIFVDQQH
-IG---GYTD-FAAWV-KEN--LD---A-
---
+--MQ---T--V-I-FG-RSG-C---PY---S-
+VRAKDL-AEKLSN---E-R-D-DFQY---Q-Y--VD
+-IRA-EGITKED---LQQ--KA--GKPV-ETVPQ-I---F
+VDQQHIGGYT--DF---AAW--VKEN-LDA--
+
 >1erv
-A-GDK-L---VVVDF---SATWCGPC-K---MIK--PFFH
--S--L-SEK--YSN--VIF-LE-VD--V-DDC
-QD---V--ASECE---V-KSMP--T-F---Q-
--FFKKGQKVG---EF--SG-A--NKE--KLE-A--T-I--NE--
-LV
+A-GDK-L---VVVDF---SATWCGPC--KM-IKP-FFHS-
+-LS-EK-YSNV-IFL-E--VDVDDCQ-DV---
+---ASEC---E---V-K-SM--P---TF
+QFFKKGQKV--G--E--FSG--A-N--KE-KL--EAT-I---NE
+--LV
 >2trcP
-KV-TTIV---VNIY---EDGVR-G-C--DAL---NSSL--ECLA
-A--EY-PMV--KFCKI-RASN--T
-GAGDRFSSDVLP--TL-L--VYK-
--G---G---ELISNF-IS-VAE-QFAEDF--FAADVESFLNEYG
-L-LPER
+KV-TTIV---VNIY---EDGVR-G-C--
+D--A--L-NSSLE-CLAAEYPMV--KFC
+KIRA---SNTG-AGDRFSSDVLP-TL-L--VYK---G---GELI-SNF
+-I-S-VAEQFAEDF--FAA--DV-E--SFLNE
+YGL-LPER
Executing test for seqan_tcoffee

[...]
==
 total tests: 66
failed tests: 1
successful tests: 65
==
[...]
99% tests passed, 1 tests failed out of 401

Total Test time (real) = 894.07 sec

The following tests FAILED:
395 - app_test_seqan_tcoffee (Failed)
Errors while running CTest

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#889732: libconfig-model-dpkg-perl: Does not recognize Salsa platform in Vcs field

[gregor herrmann]

On Sat, 03 Mar 2018 18:08:59 +0100, Andreas Tille wrote:

> > - update the hardcoded values for the perl, ruby, and javascript
> >   teams
> If you could add med-team and r-pkg-team which both have a flat
> package structure that would be great.  The science-team has in
> most cases a flat structure but (IMHO unfortunately) some people
> decided to create subdirs ...

I think that's fine, and I'm happy to add them unless Dominique has
some objections.

Currently we have for Vcs-Git:

  'formula' => '  $maintainer =~ /pkg-perl/? 
"https://salsa.debian.org/perl-team/modules/packages/$pkgname.git;
: $maintainer =~ /pkg-ruby-extras/ ? 
"https://salsa.debian.org/ruby-team/$pkgname.git;
: $maintainer =~ /pkg-javascript/ ? 
"https://salsa.debian.org/js-team/$pkgname.git;
:\'\' ;',

(And the same for Vcs-Browser minus the trailing .git)

So for the med-team and the r-pkg-team we would need a string for the
maintainer address, and the base git URL at salsa.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: [DKP]: Lied vom Frieden (Portugal)


signature.asc
Description: Digital Signature

Bug#889732: libconfig-model-dpkg-perl: Does not recognize Salsa platform in Vcs field

[gregor herrmann]

On Mon, 05 Mar 2018 18:55:15 +0100, Dominique Dumont wrote:

> On Saturday, 3 March 2018 17:56:11 CET gregor herrmann wrote:
> > Please review/merge/improve/ignore at your discretion 
> Merged. Thanks for the update :-)

Thanks to you :)


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Bettina Wegner: Man sagt (The Rose)


signature.asc
Description: Digital Signature

Bug#892221: python-jpype: FTBFS on hurd-i386: jni_md_platform is not defined

[Aaron M. Ucko]

Source: python-jpype
Version: 0.6.2+dfsg-2
Severity: normal
Tags: upstream
User: debian-h...@lists.debian.org
Usertags: hurd

Builds of python-jpype for hurd-i386 (admittedly not a release
architecture) have been failing, as most recently seen in [1]:

  setup.py:91: UserWarning: Your platform is not being handled explicitly. It 
may work or not!
" It may work or not!", UserWarning)
  Traceback (most recent call last):
File "setup.py", line 95, in 
  [os.path.join(java_home, 'include', jni_md_platform)]
  NameError: name 'jni_md_platform' is not defined

Per [2], the appropriate directory name here appears to be linux(!).
Also, sys.platform starts with "gnu" on the Hurd.

Could you please take a look?

Thanks!

[1] 
https://buildd.debian.org/status/fetch.php?pkg=python-jpype=hurd-i386=0.6.2%2Bdfsg-2=1518954986=0
[2] https://packages.debian.org/sid/hurd-i386/gcj-6-jdk/filelist

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#882322: Another bug fixed upstream

[Francois Marier]

The new upstream release also fixes #871249.

-- 
https://fmarier.org/

Bug#892220: libcrypt-u2f-server-perl: Incomplete documentation

[Xavier Guimard]

Package: libcrypt-u2f-server-perl
Version: 0.40-1
Severity: minor
Tags: upstream
Forwarded: https://rt.cpan.org/Ticket/Display.html?id=124702

POD documentation is incomplete: some important functions are not
mentioned. For example, setChallenge is required to use this library in
a web process but neither synopsis nor POD explain that it's required to
check or register a key.

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

Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libcrypt-u2f-server-perl depends on:
ii  libc6   2.26-6
ii  libjson-xs-perl 3.040-1
ii  libu2f-server0  1.1.0-1
ii  perl5.26.1-5
ii  perl-base [perlapi-5.26.0]  5.26.1-5

libcrypt-u2f-server-perl recommends no packages.

libcrypt-u2f-server-perl suggests no packages.

-- no debconf information

Bug#792513: openssh-client: Please support using multiple CPUs/cores for ssh-keygen -T

[Brian Minton]

Package: openssh-client
Version: 1:7.6p1-4
Followup-For: Bug #792513

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear Maintainer,

I just verified that the behavior is the same in the current version.

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

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

Versions of packages openssh-client depends on:
ii  adduser   3.117
ii  dpkg  1.19.0.5
ii  libbsd0   0.8.7-1
ii  libc6 2.26-6
ii  libedit2  3.1-20170329-1
ii  libgssapi-krb5-2  1.16-2
ii  libselinux1   2.7-2+b1
ii  libssl1.0.2   1.0.2n-1
ii  passwd1:4.5-1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages openssh-client recommends:
ii  xauth  1:1.0.10-1

Versions of packages openssh-client suggests:
ii  keychain 2.8.2-0.1
ii  ksshaskpass [ssh-askpass]4:5.12.1-1
ii  libpam-ssh   2.1+ds1-2
ii  monkeysphere 0.41-1
ii  ssh-askpass  1:1.2.4.1-10
ii  ssh-askpass-gnome [ssh-askpass]  1:7.6p1-4

- -- Configuration Files:
/etc/ssh/moduli changed [not included]
/etc/ssh/ssh_config changed [not included]

- -- no debconf information

-BEGIN PGP SIGNATURE-

iHUEAREIAB0WIQT5xLt2Dng/DewQpoprjrOgZc+6qQUCWp8LMwAKCRBrjrOgZc+6
qR/GAP9vTzVfyuWTbI9IryiLINwiKD5SN0SWroOnVrYWJeFk6AD+PgxKfKiSgbAC
Bu43fUfmqVkdlsmjBO4xTa57jL3UKayIdQQBFggAHRYhBO7QFYAT3C5tbgAepDe5
UHrP8gFuBQJanws6AAoJEDe5UHrP8gFuLHoBAIPHOJw9qTcuHk32p8EOfja+xNjZ
zUYnRinDi9iBieP9AP9DqPE6VbQCEif71Gi41+IueOuwjqtmEG0sOTDzx7RxCw==
=bC+5
-END PGP SIGNATURE-

Bug#892219: gmp: Please update symbols file for new architecture "riscv64" (RISC-V 64 bits little-endian)

[Manuel A. Fernandez Montecelo]

Source: gmp
Version: 2:6.1.2+dfsg-2
Severity: wishlist
Tags: patch
User: debian-ri...@lists.debian.org
Usertags: riscv64

Hello,

We need changes in this package to bootstrap the riscv64 architecture, in
particular we need an updated symbols file.

I am attaching a patch that allowed me to compile the package.

It would be great if you could include these changes and release a new version
for unstable.

If we can do something to speed-up this process, please let me/us know.


Thanks and cheers.
--
Manuel A. Fernandez Montecelo 
--- ../libgmp10.symbols.orig2018-03-06 15:44:17.633015980 +
+++ debian/libgmp10.symbols 2018-03-06 15:44:22.576939680 +
@@ -215,7 +215,7 @@
  (arch=any-i386)__gmpn_add_n_pentium@Base 2:5.1.1
  __gmpn_add_n_sub_n@Base 2:5.1.1
  (arch=any-i386)__gmpn_add_n_x86@Base 2:5.1.1
- (arch=!hppa !mips !mipsel !m68k !nios2 !s390x !sh3 !sh4 !sparc !sparc64 
!tilegx !any-i386)__gmpn_add_nc@Base 0
+ (arch=!hppa !mips !mipsel !m68k !nios2 !riscv64 !s390x !sh3 !sh4 !sparc 
!sparc64 !tilegx !any-i386)__gmpn_add_nc@Base 0
  (arch=any-i386)__gmpn_add_nc_atom@Base 2:5.1.1
  (arch=any-i386)__gmpn_add_nc_k6@Base 2:5.1.1
  (arch=any-i386)__gmpn_add_nc_k7@Base 2:5.1.1
@@ -224,9 +224,9 @@
  (arch=any-i386)__gmpn_add_nc_pentium@Base 2:5.1.1
  (arch=any-i386)__gmpn_add_nc_x86@Base 2:5.1.1
  (arch=any-amd64)__gmpn_addaddmul_1msb0@Base 0
- (arch=!arm64 !hppa !mips !mipsel !mips64 !mips64el !m68k !nios2 !sparc 
!sparc64 !sh3 !sh4 !tilegx)__gmpn_addlsh1_n@Base 0
+ (arch=!arm64 !hppa !mips !mipsel !mips64 !mips64el !m68k !nios2 !riscv64 
!sparc !sparc64 !sh3 !sh4 !tilegx)__gmpn_addlsh1_n@Base 0
  (arch=any-i386)__gmpn_addlsh1_n_init@Base 2:5.1.1
- (arch=!arm64 !armel !armhf !hppa !mips !mipsel !mips64 !mips64el !m68k !nios2 
!powerpc !powerpcspe !s390x !sh3 !sh4 !sparc !sparc64 
!tilegx)__gmpn_addlsh2_n@Base 0
+ (arch=!arm64 !armel !armhf !hppa !mips !mipsel !mips64 !mips64el !m68k !nios2 
!powerpc !powerpcspe !riscv64 !s390x !sh3 !sh4 !sparc !sparc64 
!tilegx)__gmpn_addlsh2_n@Base 0
  (arch=any-i386)__gmpn_addlsh2_n_init@Base 2:5.1.1
  (arch=any-amd64)__gmpn_addlsh_n@Base 0
  __gmpn_addmul_1@Base 0
@@ -394,7 +394,7 @@
  __gmpn_hgcd_reduce_itch@Base 2:5.1.1
  __gmpn_hgcd_step@Base 2:5.1.1
  __gmpn_invert@Base 0
- (arch=!hppa !mips !mipsel !mips64 !mips64el !m68k !nios2 !sparc !sparc64 !sh3 
!sh4 !tilegx !any-i386)__gmpn_invert_limb@Base 0
+ (arch=!hppa !mips !mipsel !mips64 !mips64el !m68k !nios2 !riscv64 !sparc 
!sparc64 !sh3 !sh4 !tilegx !any-i386)__gmpn_invert_limb@Base 0
  __gmpn_invertappr@Base 0
  __gmpn_ior_n@Base 0
  __gmpn_iorn_n@Base 0
@@ -507,7 +507,7 @@
  (arch=any-i386)__gmpn_mul_1_pentium@Base 2:5.1.1
  (arch=any-i386)__gmpn_mul_1_pentium_mmx@Base 2:5.1.1
  (arch=any-i386)__gmpn_mul_1_x86@Base 2:5.1.1
- (arch=!arm64 !armel !armhf !hppa !mips !mipsel !mips64 !mips64el !m68k !nios2 
!powerpc !powerpcspe !s390x !sh3 !sh4 !sparc !sparc64 !tilegx 
!any-i386)__gmpn_mul_1c@Base 0
+ (arch=!arm64 !armel !armhf !hppa !mips !mipsel !mips64 !mips64el !m68k !nios2 
!powerpc !powerpcspe !riscv64 !s390x !sh3 !sh4 !sparc !sparc64 !tilegx 
!any-i386)__gmpn_mul_1c@Base 0
  (arch=any-i386)__gmpn_mul_1c_atom_sse2@Base 2:5.1.1
  (arch=any-i386)__gmpn_mul_1c_k6@Base 2:5.1.1
  (arch=any-i386)__gmpn_mul_1c_k7@Base 2:5.1.1
@@ -571,13 +571,13 @@
  __gmpn_redc_n@Base 0
  __gmpn_remove@Base 0
  __gmpn_rootrem@Base 0
- (arch=!alpha !arm64 !armel !armhf !hppa !mips !mipsel !mips64 !mips64el !m68k 
!nios2 !powerpc !powerpcspe !sh3 !sh4 !sparc !sparc64 !tilegx 
!any-i386)__gmpn_rsblsh1_n@Base 0
- (arch=!alpha !arm64 !armel !armhf !hppa !mips !mipsel !mips64 !mips64el !m68k 
!nios2 !powerpc !powerpcspe !s390x !sh3 !sh4 !sparc !sparc64 !tilegx 
!any-i386)__gmpn_rsblsh2_n@Base 0
- (arch=!alpha !arm64 !armel !armhf !hppa !ia64 !mips !mipsel !mips64 !mips64el 
!m68k !nios2 !powerpc !powerpcspe !ppc64 !ppc64el !s390x !sh3 !sh4 !sparc 
!sparc64 !tilegx !any-i386)__gmpn_rsblsh_n@Base 0
- (arch=!alpha !arm64 !hppa !mips !mipsel !mips64 !mips64el !m68k !nios2 
!powerpc !powerpcspe !s390x !sh3 !sh4 !sparc !sparc64 !tilegx 
!any-i386)__gmpn_rsh1add_n@Base 0
- (arch=!alpha !arm64 !armel !armhf !hppa !ia64 !mips !mipsel !mips64 !mips64el 
!m68k !nios2 !powerpc !powerpcspe !ppc64 !ppc64el !s390x !sh3 !sh4 !sparc 
!sparc64 !tilegx !any-i386)__gmpn_rsh1add_nc@Base 0
- (arch=!alpha !arm64 !hppa !mips !mipsel !mips64 !mips64el !m68k !nios2 
!powerpc !powerpcspe !s390x !sh3 !sh4 !sparc !sparc64 !tilegx 
!any-i386)__gmpn_rsh1sub_n@Base 0
- (arch=!alpha !arm64 !armel !armhf !hppa !ia64 !mips !mipsel !mips64 !mips64el 
!m68k !nios2 !powerpc !powerpcspe !ppc64 !ppc64el !s390x !sh3 !sh4 !sparc 
!sparc64 !tilegx !any-i386)__gmpn_rsh1sub_nc@Base 0
+ (arch=!alpha !arm64 !armel !armhf !hppa !mips !mipsel !mips64 !mips64el !m68k 
!nios2 !powerpc !powerpcspe !riscv64 !sh3 !sh4 !sparc !sparc64 !tilegx 
!any-i386)__gmpn_rsblsh1_n@Base 0
+ (arch=!alpha !arm64 !armel !armhf !hppa !mips !mipsel !mips64 !mips64el !m68k 
!nios2 !powerpc 

Bug#892177: gnucash: Please package latest 2.7 release

[Dmitry Smirnov]

On Wednesday, 7 March 2018 12:12:03 AM AEDT Jeremy Bicha wrote:
> 2.7.5 was released. Please package it.
> 
> https://github.com/Gnucash/gnucash/releases

I'm working on it but

https://bugzilla.gnome.org/show_bug.cgi?id=793900
https://bugzilla.gnome.org/show_bug.cgi?id=793941
https://bugzilla.gnome.org/show_bug.cgi?id=794137

Regards,
 Dmitry Smirnov.

---

If liberty means anything at all, it means the right to tell people what
they do not want to hear.
-- George Orwell



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

Bug#892218: postfix: Upgrading to 3.3.0 missed important settings for smtpd_relay_restrictions or smtpd_recipient_restrictions

[Adrien CLERC]

Package: postfix
Version: 3.3.0-1
Severity: important

Hi,

After upgrading from 3.2.5 to 3.3.0, the following line appears in
/var/log/mail.log:

postfix/smtpd[11716]: fatal: in parameter smtpd_relay_restrictions or
smtpd_recipient_restrictions, specify at least one working instance of:
reject_unauth_destination, defer_unauth_destination, reject, defer,
defer_if_permit or check_relay_domains

There is no default value for this in provided configuration file.
However, the online documentation (at
http://www.postfix.org/postconf.5.html#smtpd_recipient_restrictions)
clearly mention that.

Is it an "upgrade" mistake, or a real error?

In any case, email are deferred until the admin read logs.


Adrien


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

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

Versions of packages postfix depends on:
ii  adduser    3.117
ii  cpio   2.12+dfsg-6
ii  debconf [debconf-2.0]  1.5.66
ii  dpkg   1.19.0.5
ii  e2fsprogs  1.43.9-2
ii  libc6  2.26-6
ii  libdb5.3   5.3.28-13.1+b1
ii  libicu57   57.1-8
ii  libsasl2-2 2.1.27~101-g0780600+dfsg-3
pn  libssl1.1  
ii  lsb-base   9.20170808
ii  netbase    5.4
ii  ssl-cert   1.0.39

Versions of packages postfix recommends:
ii  python3  3.6.4-1

Versions of packages postfix suggests:
ii  bsd-mailx [mail-reader]    8.1.2-0.20160123cvs-4
ii  dovecot-core [dovecot-common]  1:2.2.34-2
ii  libsasl2-modules   2.1.27~101-g0780600+dfsg-3
pn  postfix-cdb    
pn  postfix-doc    
pn  postfix-ldap   
pn  postfix-lmdb   
pn  postfix-mysql  
ii  postfix-pcre   3.3.0-1
pn  postfix-pgsql  
ii  postfix-sqlite 3.3.0-1
pn  procmail   
pn  resolvconf 
pn  sasl2-bin  
pn  ufw    

-- debconf information:
  postfix/chattr: false
  postfix/main_cf_conversion_warning: true
  postfix/lmtp_retired_warning: true
  postfix/protocols:
  postfix/destinations:
  postfix/mailname: /etc/mailname
  postfix/sqlite_warning:
  postfix/mynetworks: 127.0.0.0/8 [:::127.0.0.0]/104 [::1]/128
  postfix/bad_recipient_delimiter:
  postfix/relay_restrictions_warning:
  postfix/dynamicmaps_conversion_warning:
  postfix/kernel_version_warning:
  postfix/newaliases: false
  postfix/mailbox_limit: 0
  postfix/procmail:
  postfix/recipient_delim: +
  postfix/root_address:
  postfix/relayhost:
  postfix/retry_upgrade_warning:
* postfix/main_mailer_type: No configuration
  postfix/mydomain_warning:
  postfix/rfc1035_violation: false
  postfix/not_configured:
  postfix/tlsmgr_upgrade_warning:
  postfix/compat_conversion_warning: true

Bug#892216: libwebkit2gtk-4.0-37: Does not install. Dependecy conflict

[Alberto Garcia]

Control: tags -1 moreinfo

On Tue, Mar 06, 2018 at 05:57:51PM -0300, Patrick Davis Naylor Gonzalez wrote:

> I tried to install Zenity and Shotwell, which both have
> libwebkit2gtk-4.0-37 as a dependency, but it is not possible
> because of a dependency problem with libwebkit2gtk-4.0-37: Depends:
> libgstreamer-plugins-bad1.0-0 (<1.10.5) but 1:1.10.4-dmo2 will be
> installed.

> ii  libgstreamer-plugins-bad1.0-0   1:1.10.4-dmo2

It seems that the version of libgstreamer-plugins-bad1.0-0 that you
have installed is not from Debian, isn't that from deb-multimedia.org?

I don't know why they added an epoch (the "1:" part) to their version
number, but that's what's causing this.

So basically it seems that the gstreamer version from deb-multimedia
is incompatible with the one from Debian, you're using the former and
webkit2gtk was linked against the latter.

Can you try installing libgstreamer-plugins-bad1.0-0 from Debian and
see if that solves your problem?

Berto

Bug#892217: [PATCH] libffi: Please add support for the riscv64 architecture

[Karsten Merker]

Source: libffi
Version: 3.3~20180131
Severity: wishlist
X-Debbugs-CC: debian-ri...@lists.debian.org
Tags: patch
User: debian-ri...@lists.debian.org
Usertags: riscv64

Hello,

we are in the process of bootstrapping a Debian port for the
riscv64 architecture (https://wiki.debian.org/RISC-V).  The
libffi package is part of the build-dependency chain for the
essential package set, so we need to build it for riscv64 to be
able to complete the bootstrap process.

Current upstream libffi doesn't yet have support for the RISC-V
architecture, but a pull request to add it has been submitted:

  https://github.com/libffi/libffi/pull/281/ respectively
  https://patch-diff.githubusercontent.com/raw/libffi/libffi/pull/281.patch

The pull request has been authored by one of the Fedora riscv64
porters and the Fedora riscv64 port already uses this patchset. 
It would be great if you could add the patchset to the Debian
libffi package as well.

The RISC-V support provided by the patchset is not all-encompassing
(please cf. the last comment from Stefan O'Rear in the pull
request), but it provides the same amount of features that libffi
has for a number of other Debian-supported architectures, so that
shouldn't be a problem.  The symbols file would need to be
adjusted, though:

dh_makeshlibs -plibffi7 --add-udeb=libffi7-udeb
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libffi7/DEBIAN/symbols doesn't match 
completely debian/libffi7.symbols
--- debian/libffi7.symbols (libffi7_3.3~20180131-2_riscv64)
+++ dpkg-gensymbols50ytax   2018-03-06 21:11:57.533480937 +
@@ -2,5 +2,5 @@
  (symver)LIBFFI_BASE_7.0 3.3~20170512
  (symver)LIBFFI_BASE_7.1 3.3~20170512
  (symver)LIBFFI_CLOSURE_7.0 3.3~20170512
- (symver|arch=!hppa !ia64 !m68k !mips !mipsel !mips64el !powerpc !powerpcspe 
!ppc64 !ppc64el !sh4)LIBFFI_COMPLEX_7.0 3.3~20170512
- (symver|arch=!hppa !ia64 !m68k !sh4)LIBFFI_GO_CLOSURE_7.0 3.3~20170512
+#MISSING: 3.3~20180131-2# (symver|arch=!hppa !ia64 !m68k !mips !mipsel 
!mips64el !powerpc !powerpcspe !ppc64 !ppc64el !sh4)LIBFFI_COMPLEX_7.0 
3.3~20170512
+#MISSING: 3.3~20180131-2# (symver|arch=!hppa !ia64 !m68k 
!sh4)LIBFFI_GO_CLOSURE_7.0 3.3~20170512

Regards,
Karsten
-- 
Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung
sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der
Werbung sowie der Markt- oder Meinungsforschung.

Bug#890944: new packages should not receive emails before email alias is created

[Thorsten Alteholz]

Hi everybody,

On Mon, 5 Mar 2018, Luca Falavigna wrote:

OK. Can you please indicate which header is used to reference the
source package when sending mails to dispatch@tracker.d.o?


does [1] make sense for this?

  Thorsten


[1] https://salsa.debian.org/ftp-team/dak/merge_requests/9

Bug#892216: libwebkit2gtk-4.0-37: Does not install. Dependecy conflict

[Patrick Davis Naylor Gonzalez]

Package: libwebkit2gtk-4.0-37
Version: 2.18.6-1~deb9u1
Severity: normal

Dear Maintainer,

I tried to install Zenity and Shotwell, which both have libwebkit2gtk-4.0-37 as
a dependency, but it is not possible because of a dependency problem with
libwebkit2gtk-4.0-37:Depends: libgstreamer-plugins-bad1.0-0 (<1.10.5) but
1:1.10.4-dmo2 will be installed.
Hoping this information can be useful to solve the problem,

Patrick


*** 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: 9.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 
'stable'), (2, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages libwebkit2gtk-4.0-37 depends on:
ii  libatk1.0-0 2.22.0-1
ii  libc6   2.24-11+deb9u3
ii  libcairo2   1.14.8-1
pn  libegl1 
ii  libegl1-mesa [libegl1-x11]  13.0.6-1+b2
ii  libenchant1c2a  1.6.0-11+b1
ii  libfontconfig1  2.12.6-0.1
ii  libfreetype62.6.3-3.2
ii  libgcc1 1:6.3.0-18+deb9u1
ii  libgcrypt20 1.7.6-2+deb9u2
ii  libgdk-pixbuf2.0-0  2.36.5-2+deb9u2
ii  libgl1-mesa-glx [libgl1]13.0.6-1+b2
ii  libglib2.0-02.50.3-2
ii  libgstreamer-plugins-bad1.0-0   1:1.10.4-dmo2
ii  libgstreamer-plugins-base1.0-0  1.10.4-1
ii  libgstreamer1.0-0   1.10.4-1
ii  libgtk-3-0  3.22.11-1
ii  libharfbuzz-icu01.4.2-1
ii  libharfbuzz0b   1.4.2-1
ii  libhyphen0  2.8.8-5
ii  libicu5757.1-6+deb9u1
ii  libjavascriptcoregtk-4.0-18 2.18.6-1~deb9u1
ii  libjpeg62-turbo 1:1.5.1-2
ii  libnotify4  0.7.7-2
ii  libpango-1.0-0  1.40.5-1
ii  libpng16-16 1.6.28-1
ii  libsecret-1-0   0.18.5-3.1
ii  libsoup2.4-12.56.0-2+deb9u1
ii  libsqlite3-03.16.2-5+deb9u1
ii  libstdc++6  6.3.0-18+deb9u1
ii  libtasn1-6  4.10-1.1+deb9u1
ii  libwayland-client0  1.12.0-1
ii  libwayland-egl1-mesa [libwayland-egl1]  13.0.6-1+b2
ii  libwayland-server0  1.12.0-1
ii  libwebp60.5.2-1
ii  libx11-62:1.6.4-3
ii  libxcomposite1  1:0.4.4-2
ii  libxdamage1 1:1.1.4-2+b3
ii  libxml2 2.9.4+dfsg1-2.2+deb9u2
ii  libxslt1.1  1.1.29-2.1
ii  zlib1g  1:1.2.8.dfsg-5

Versions of packages libwebkit2gtk-4.0-37 recommends:
ii  gstreamer1.0-plugins-base  1.10.4-1
ii  gstreamer1.0-plugins-good  1.10.4-1
ii  gstreamer1.0-pulseaudio1.10.4-1
ii  libgl1-mesa-dri13.0.6-1+b2

Versions of packages libwebkit2gtk-4.0-37 suggests:
pn  libwebkit2gtk-4.0-37-gtk2  

Bug#892215: libxcb FTBFS: KeyError: 'eventstruct'

[Helmut Grohne]

Source: libxcb
Version: 1.12-1
Severity: serious
Justification: FTBFS
User: helm...@debian.org
Usertags: rebootstrap

Since a few days(?), libxcb FTBFS. The build ends with:

| make[1]: Entering directory '/<>/build'
| Making all in src
| make[2]: Entering directory '/<>/build/src'
| /usr/bin/python ../../src/c_client.py   -c "libxcb 1.12" -l "X Version 11" \
| -s "3" -p /usr/lib/python2.7/dist-packages \
|  \
| /usr/share/xcb/xproto.xml
| Traceback (most recent call last):
|   File "../../src/c_client.py", line 3294, in 
| from xcbgen.state import Module
|   File "/usr/lib/python2.7/dist-packages/xcbgen/state.py", line 7, in 
| from xcbgen import matcher
|   File "/usr/lib/python2.7/dist-packages/xcbgen/matcher.py", line 12, in 

| from xcbgen.xtypes import *
|   File "/usr/lib/python2.7/dist-packages/xcbgen/xtypes.py", line 1221, in 

| class EventStruct(Union):
|   File "/usr/lib/python2.7/dist-packages/xcbgen/xtypes.py", line 1239, in 
EventStruct
| out = __main__.output['eventstruct']
| KeyError: 'eventstruct'
| make[2]: *** [Makefile:1290: xproto.c] Error 1
| make[2]: Leaving directory '/<>/build/src'
| make[1]: *** [Makefile:787: all-recursive] Error 1
| make[1]: Leaving directory '/<>/build'
| dh_auto_build: cd build && make -j1 returned exit code 2
| make: *** [debian/rules:17: build-arch] Error 2
| dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

libxcb wasn't uploaded in a while. Very likely, the cause lies
elsewhere. The earliest failure I have seen was Tue, 6 Mar 2018 06:31:35
(UTC), so it should be close to the dinstall prior to that. Could it be
the xcb-proto/1.13-1 upload?

Helmut

Bug#892214: unblock: rocksndiamonds/4.0.1.3+dfsg-1

[Stephen Kitt]

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

Hi,

rocksndiamonds currently has a manual block in Adam’s hints file,
related to #879667 which caused the package to end up in main and
contrib. The package has been rebuilt since (a binNMU first, and a
recent source upload), and rmadison tells me the current version is
only in contrib.

Would it be possible to lift the block?

Thanks,

Stephen

Bug#694068: (solved) Re: wireless fail after stretch installation

[Brian]

On Tue 06 Mar 2018 at 18:34:27 +, Ian Jackson wrote:

> bw writes ("Re: (solved) Re: wireless fail after stretch installation"):
> > I think the idea needs to be talked over a little better, because using 
> > e/n/i for wireless by default after first boot has implications if the 
> > user (who is clueless) later installs a desktop environment.
> 
> If installing a desktop environment, after putting the wireless in
> /e/n/i, does not work, then that is a bug in the desktop environment,
> surely ?

Most probably. But desktop environments were not the subject of this
thread. (Sorry for trying to keep on-topic).

> In practice I would expect the config in /e/n/i to keep working
> because nowadays network-manager will ignore things in /e/n/i.  The
> difficulty would only come if you
>   - used the installer to install a bare system over wifi

That difficulty is  exactly the subject of this thread. The rest of this
post is snipped because it side-steps addressing the issue. What is put
in /e/n/i ceases to work because it is obliterated by the installer for
reasons unknown.

One user calls it a "sick joke". After five years and with no attempt
to rectify the situation, I'm beginning to have sympathy with that view.

(Yes, I know we are all volunteers).

-- 
Brian.




>   - later install network-manager or wicd
>   - then expect the system to give you a gui prompt for new wifi
> networks, rather than expect to have to edit /e/n/i
> 
> It would be possible for the n-m and wicd packages to spot when this
> is happening and offer to take over the interface.  And I do think
> that in the absence of code to do that, it would be more important to
> make the barebones system work in the first place, than to improve the
> behaviour you later install n-m.
> 
> (I'm not sure if what I say about wicd is right.  I use n-m on
> machines I have where the user needs to switch between various network
> connections, wifi networks, etc.)
> 
> > I'd hate to see the bug tracker turned into a discussion forum though.  
> 
> The bug tyracker is precisely the right place to discuss how to solve
> a particular bug.  So I have CC'd it.
> 
> Ian.
> 
> -- 
> Ian Jackson    These opinions are my own.
> 
> If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
> a private address which bypasses my fierce spamfilter.
> 

Bug#892213: RFS: bali-phy/3.0.1-1 [ITP]

[Benjamin Redelings]

Package: sponsorship-requests
Severity: wishlist

  Dear mentors,

  I am looking for a sponsor for my package "bali-phy"

 * Package name    : bali-phy
   Version : 3.0.1-1
   Upstream Author : Benjamin Redelings 
 * URL : http://www.bali-phy.org
 * License : GPL2+
   Section : science

  It builds those binary packages:

    bali-phy   - Bayesian Inference of Alignment and Phylogeny

  To access further information about this package, please visit the 
following URL:


  https://mentors.debian.net/package/bali-phy


  Alternatively, one can download the package with dget using this 
command:


    dget -x 
https://mentors.debian.net/debian/pool/main/b/bali-phy/bali-phy_3.0.1-1.dsc


  More information about hello can be obtained from 
https://www.example.com.


  Changes since the last upload:

  * Initial release (Closes: #891971).
  * Handle meson 0.44.1 since meson 0.45 is not out yet.
  * Use system copy of boost, eigen, and nlohmann::json by default.
  * Add basic meson unit tests.
  * Add autopkgtest tests.
  * Add watch file.
  * Add man pages for all tools (generated with pandoc).
  * Enable hardened build.
  * Remove unused python bytecode files.
  * Fix typos in man pages.
  * Versioned depends on debhelper.
  * Set buildsystem to meson the correct way.
  * Add revision number.
  * Update copyright file.
  * Update compat to 11.
  * Update standards version to 4.1.3.
  * Fix day of week.
  * Remove trailing whitespace from control file.

Bug#858936: [Pkg-kannel-devel] Bug#858936: kannel: Please migrate to openssl1.1 in buster [patch]

[Jonas Smedegaard]

Quoting Frans van Berckel (2018-03-06 20:49:14)
> Nice to know, upstream officially changed the sources
> 
> * added support for openssl version > 1.1
> 
> https://redmine.kannel.org/projects/kannel/repository/revisions/5201

Great!  thanks for pointing it out!

 - 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#892179: code execution in bash-completion for umount

[Salvatore Bonaccorso]

Control: reassign -1 src:util-linux 2.29.2-1
Control: tags -1 + upstream fixed-upstream

Hi Björn

Thanks for reporting the issue!

On Tue, Mar 06, 2018 at 02:44:39PM +0100, Björn Bosselmann wrote:
> Package: bash-completion
> Version: 1:2.1-4.3
> Severity: grave
> Tags: security
> 
> Hi,
> 
> when bash-completion is installed, it uses
> /usr/share/bash-completion/completions/umount from umount package to
> provide autocompletion. This script does not escape mount paths
> correctly, so it allows a local user with rights to mount filesystems to
> execute commands in the context of the umount user (probably root).
> Unprivileged users can mount filesystems with custom mountpoints using
> udisks2, FUSE or with the help of desktop environments.

The umount completion is actually provided by util-linux (since 2.28-1
where it took over from bash-completion itself). I'm thus reassigning
it to src:util-linux. Then if the issue is present as well in
bash-completion earlier than 1:2.1-4.3, then 1:2.1-4.3 removed the
completion and would not be affected in the resulting binary packages
(source still might be).

Regards,
Salvatore

Bug#891957: netbeans no starting "loading module" modules.netbinox NullPointerException

[Patrick Häcker]

Hi,

> I suspect this is because of the recent update of libequinox-osgi-java.
your suspicion is correct. Downgrading libequinox-osgi-java with
> apt install libequinox-osgi-java/stable
fixes the issue (although it removes eclipse if that is not downgraded as 
well).

Kind regards
Patrick

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

Bug#891114: Pending fixes for bugs in the activemq package

[pkg-java-maintainers]

tag 891114 + pending
thanks

Some bugs in the activemq package are closed in revision
2b45bbb3a1fc853f48cf68fdf6e396d9c1b3da8f in branch 'master' by Markus
Koschany

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

Commit message:

Remove libjosql-java-doc from B-D because it is gone.

Closes: #891114
Thanks: Andreas Beckmann for the report.

Bug#858936: kannel: Please migrate to openssl1.1 in buster [patch]

[Frans van Berckel]

Nice to know, upstream officially changed the sources

* added support for openssl version > 1.1

https://redmine.kannel.org/projects/kannel/repository/revisions/5201

Thanks,

-- 
Frans van Berckel
Media Engineer / Linux Master
LinkedIn: https://www.linkedin.com/in/fransvberckel/

Bug#892212: nmu: otb_6.4.0+dfsg-1

[Bas Couwenberg]

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

Please rebuild otb (6.4.0+dfsg-1) with ossim (2.3.0-1) in unstable.

nmu otb_6.4.0+dfsg-1 . ANY . unstable . -m "Rebuild with libossim-dev (>= 
2.3.0)"

The rebuild is required to fix symbol lookup errors, see:

 https://lists.debian.org/debian-gis/2018/03/msg1.html

Kind Regards,

Bas

Bug#892211: [debian-goodies] debmany: support gzip compressed text files

[Marcel Partap]

Package: debian-goodies
Version: 0.79
Severity: normal

About a third of all files in /usr/share/doc/ are gzipped. Patch adds support, 
please review : )
--- debmany.orig	2018-03-06 20:18:57.011490293 +0100
+++ debmany	2018-03-06 20:19:22.838676740 +0100
@@ -413,7 +413,12 @@ do
 else
   # other file (usr/share/doc)
   debug "Opening other file: "`printf "$othercmdline" "$PWD/$return"` # comment
-  eval $(printf "$othercmdline" "$PWD/$return")
+  if [[ "$return" =~ \.gz$ ]]
+  then
+  eval $(printf "gzip -dc < $PWD/$return | $othercmdline")
+  else
+  eval $(printf "$othercmdline" "$PWD/$return")
+  fi
 fi
   else
 cd "$curdir"

Bug#892210: marble-qt: Bookmark editing broken

[Pelle Hjek]

Package: marble-qt
Version: 4:17.08.3-3
Severity: normal

Dear Maintainer,

Bookmark editing is broken. In the top menu, I click Bookmarks -> Manage
Boomarks -> Default (in the Bookmarks column) -> Edit.

When I click Edit, nothing happens. I expected to see a menu, where I
would be able to modify or remove bookmarks.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 4.14.0-3-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages marble-qt depends on:
ii  libc6   2.26-6
ii  libgcc1 1:8-20180218-1
ii  libmarblewidget-qt5-28  4:17.08.3-3
ii  libqt5core5a5.9.2+dfsg-12
ii  libqt5dbus5 5.9.2+dfsg-12
ii  libqt5gui5  5.9.2+dfsg-12
ii  libqt5network5  5.9.2+dfsg-12
ii  libqt5printsupport5 5.9.2+dfsg-12
ii  libqt5widgets5  5.9.2+dfsg-12
ii  libstdc++6  8-20180218-1

marble-qt recommends no packages.

marble-qt suggests no packages.

-- no debconf information

Bug#892209: mc should allow rubbish bin

[Pelle Hjek]

Package: mc
Version: 3:4.8.19-1
Severity: wishlist

Dear Maintainer,

mc should allow putting files in the rubbish bin, like most other file
managers, to prevent accidental deletions.

trash-cli on the command line implements this functionality, so it
might be trivial to add to mc.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 4.14.0-3-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mc depends on:
ii  e2fslibs  1.43.9-2
ii  libc6 2.26-6
ii  libglib2.0-0  2.54.3-2
ii  libgpm2   1.20.7-5
ii  libslang2 2.3.1a-3
ii  libssh2-1 1.8.0-1
ii  mc-data   3:4.8.19-1

Versions of packages mc recommends:
ii  mime-support  3.60
ii  perl  5.26.1-5
ii  unzip 6.0-21

Versions of packages mc suggests:
ii  arj  3.10.22-17
ii  bzip21.0.6-8.1
pn  dbview   
pn  djvulibre-bin
ii  evince [pdf-viewer]  3.26.0-3
ii  file 1:5.32-2
ii  genisoimage  9:1.1.11-3+b2
pn  gv   
ii  imagemagick  8:6.9.9.34+dfsg-3
ii  imagemagick-6.q16 [imagemagick]  8:6.9.9.34+dfsg-3
pn  libaspell-dev
ii  lynx 2.8.9dev16-3
ii  odt2txt  0.5-1+b2
ii  poppler-utils0.61.1-2
ii  python   2.7.14-4
pn  python-boto  
pn  python-tz
ii  texlive-binaries 2017.20170613.44572-8+b1
ii  zip  3.0-11+b1

-- no debconf information

Bug#892208: Command line documentation missing

[Enrico Zini]

Package: qweborf
Version: 0.14-1
Severity: normal

Hello,

I tried weborf. The Advanced tab says "Advanced users are supposed to
use the terminal".

Good.

I tried to use the terminal.

man qweborf is useless

qweborf --help just starts the GUI

dpkg -L qweborf does not show a single file of documentation, not even a
README.

I feel like someone's having fun of me.

I'd suggest to either remove the Advanced tab altogether, or to document
how to use it from the terminal.


Enrico


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

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

Versions of packages qweborf depends on:
ii  python33.6.4-1
ii  python3-pyqt5  5.9.2+dfsg-1
ii  weborf 0.14-1

Versions of packages qweborf recommends:
ii  miniupnpc  2.0.20171212-3

qweborf suggests no packages.

-- no debconf information

Bug#892158: RFS: gnustep-gui/0.26.2-3

[Yavor Doganov]

Yavor Doganov wrote:
>  * Package name: gnustep-gui
>Version : 0.26.2-3

>   * debian/patches/gstheme-nssegmentedcontrol.patch: New,

The patch was missing the important hunk so I've updated it and
reuploaded the package.

Bug#892206: Seagate: LUMP not started?

[Martin Michlmayr]

Package: debian-installer
Version: 20170615
Severity: important

Some users have reported that they cannot connect to the u-boot on
their Seagate NAS anymore using clunc after installing Debian.

I'll add more information about the investigation Simon Guinot did
later.  We're not sure this really is a bug since all released version
of u-boot should listen for the magic packet (LUMP).  However, there
are version of u-boot that don't automatically do this (probably not
released, but not 100% sure about this).

In any case, we should modify the debian_boot variable so start lump
directly (run start_lump or lump 3).  The only downside is that the
startup prcoess is 3 seconds longer.

I'll add a patch soon and more info to this bug report.

-- 
Martin Michlmayr
http://www.cyrius.com/

Bug#892207: blender: fails to start

[Pelle Hjek]

Package: blender
Version: 2.79+dfsg0-3+b2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After upgrading to Buster, Blender fails to start, and reports this
message:
```
Error! Blender requires OpenGL 2.1 to run. Try updating your drivers.
```

Blender worked fine just before in Stretch on the same computer.

Here is the output of `glxinfo`:

```
name of display: :0
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
server glx extensions:
GLX_ARB_create_context, GLX_ARB_create_context_profile, 
GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample, 
GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, 
GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, 
GLX_EXT_import_context, GLX_EXT_libglvnd, GLX_EXT_texture_from_pixmap, 
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, 
GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, 
GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, 
GLX_SGI_make_current_read, GLX_SGI_swap_control
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
client glx extensions:
GLX_ARB_create_context, GLX_ARB_create_context_profile, 
GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, 
GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, 
GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, 
GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, 
GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, 
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, 
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, 
GLX_SGI_swap_control, GLX_SGI_video_sync
GLX version: 1.4
GLX extensions:
GLX_ARB_create_context, GLX_ARB_create_context_profile, 
GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, 
GLX_ARB_get_proc_address, GLX_ARB_multisample, 
GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, 
GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, 
GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, 
GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, 
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, 
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, 
GLX_SGI_swap_control, GLX_SGI_video_sync
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Intel Open Source Technology Center (0x8086)
Device: Mesa DRI Intel(R) 945GME x86/MMX/SSE2 (0x27ae)
Version: 17.3.6
Accelerated: yes
Video memory: 192MB
Unified memory: yes
Preferred profile: compat (0x2)
Max core profile version: 0.0
Max compat profile version: 1.4
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 2.0
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) 945GME x86/MMX/SSE2
OpenGL version string: 1.4 Mesa 17.3.6
OpenGL extensions:
GL_3DFX_texture_compression_FXT1, GL_AMD_shader_trinary_minmax, 
GL_ANGLE_texture_compression_dxt3, GL_ANGLE_texture_compression_dxt5, 
GL_APPLE_object_purgeable, GL_APPLE_packed_pixels, 
GL_ARB_ES2_compatibility, GL_ARB_clear_buffer_object, 
GL_ARB_compressed_texture_pixel_storage, GL_ARB_copy_buffer, 
GL_ARB_debug_output, GL_ARB_depth_texture, GL_ARB_draw_buffers, 
GL_ARB_draw_elements_base_vertex, GL_ARB_explicit_attrib_location, 
GL_ARB_explicit_uniform_location, GL_ARB_fragment_program, 
GL_ARB_fragment_shader, GL_ARB_framebuffer_object, 
GL_ARB_get_program_binary, GL_ARB_get_texture_sub_image, 
GL_ARB_half_float_pixel, GL_ARB_internalformat_query, 
GL_ARB_invalidate_subdata, GL_ARB_map_buffer_alignment, 
GL_ARB_map_buffer_range, GL_ARB_multi_bind, GL_ARB_multisample, 
GL_ARB_multitexture, GL_ARB_pixel_buffer_object, GL_ARB_point_parameters, 
GL_ARB_point_sprite, GL_ARB_program_interface_query, 
GL_ARB_provoking_vertex, GL_ARB_robustness, GL_ARB_sampler_objects, 
GL_ARB_separate_shader_objects, GL_ARB_shader_objects, 
GL_ARB_shading_language_100, GL_ARB_shadow, GL_ARB_sync, 
GL_ARB_texture_border_clamp, GL_ARB_texture_compression, 
GL_ARB_texture_cube_map, GL_ARB_texture_env_add, 
GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, 
GL_ARB_texture_env_dot3, GL_ARB_texture_mirrored_repeat, 
GL_ARB_texture_non_power_of_two, GL_ARB_texture_rectangle, 
GL_ARB_texture_storage, 

Bug#892205: ITP: magic-wormhole-transit-server -- Transit Relay server for Magic-Wormhole

[Antoine Beaupre]

Package: wnpp
Severity: wishlist
Owner: Antoine Beaupre 

* Package name: magic-wormhole-transit-server
  Version : 0.1.1
  Upstream Author : Brian Werner
* URL : https://github.com/warner/magic-wormhole-transit-relay
* License : MIT
  Programming Lang: Python
  Description : Transit Relay server for Magic-Wormhole

This repository implements the Magic-Wormhole "Transit Relay", a
server that helps clients establish bulk-data transit connections even
when both are behind NAT boxes. Each side makes a TCP connection to
this server and presents a handshake. Two connections with identical
handshakes are glued together, allowing them to pretend they have a
direct connection.

This server used to be included in the magic-wormhole repository, but
was split out into a separate repo to aid deployment and development.

--

will be in collab-maint, new dependency for wormhole.

Bug#694068: (solved) Re: wireless fail after stretch installation

[Ian Jackson]

bw writes ("Re: (solved) Re: wireless fail after stretch installation"):
> I think the idea needs to be talked over a little better, because using 
> e/n/i for wireless by default after first boot has implications if the 
> user (who is clueless) later installs a desktop environment.

If installing a desktop environment, after putting the wireless in
/e/n/i, does not work, then that is a bug in the desktop environment,
surely ?

In practice I would expect the config in /e/n/i to keep working
because nowadays network-manager will ignore things in /e/n/i.  The
difficulty would only come if you
  - used the installer to install a bare system over wifi
  - later install network-manager or wicd
  - then expect the system to give you a gui prompt for new wifi
networks, rather than expect to have to edit /e/n/i

It would be possible for the n-m and wicd packages to spot when this
is happening and offer to take over the interface.  And I do think
that in the absence of code to do that, it would be more important to
make the barebones system work in the first place, than to improve the
behaviour you later install n-m.

(I'm not sure if what I say about wicd is right.  I use n-m on
machines I have where the user needs to switch between various network
connections, wifi networks, etc.)

> I'd hate to see the bug tracker turned into a discussion forum though.  

The bug tyracker is precisely the right place to discuss how to solve
a particular bug.  So I have CC'd it.

Ian.

-- 
Ian Jackson    These opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#892204: kwin-common: add support for zwp_linux_dmabuf

[Heather Ellsworth]

Package: kwin-common
Version: 4:5.12.1-1
Severity: important

Dear Maintainer,

zwp_linux_dmabuf protocol support is needed to properly work with the drm
backend to display Plasma Mobile on the Librem 5 development board.

This support is being tracked by KDE in https://phabricator.kde.org/D10750

Also see relating email thread for complete details:
https://www.mail-archive.com/plasma-devel@kde.org/msg81108.html

The proposed patches attached to D10750 (and this bug report) do indeed
fix the display issue.

Please consider carrying the kwin patch ahead of the Plasma 5.13 release
(scheduled for June 2018).

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

Kernel: Linux 4.15.0-g837bff1 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot
set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ANSI_X3.4-1968), LANGUAGE=en_US.UTF-8 (charmap=locale: Cannot set
LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kwin-common depends on:
ii  kio  5.42.0-3
ii  kpackagetool55.42.0-2
ii  kwin-data4:5.12.1-1
ii  libc62.26-6
ii  libepoxy01.4.3-1
ii  libgcc1  1:8-20180218-1
ii  libice6  2:1.0.9-2
ii  libinput10   1.10.0-1
ii  libkdecorations2-5v5 4:5.12.1-1
ii  libkdecorations2private5v5   4:5.12.1-1
ii  libkf5activities55.42.0-2
ii  libkf5auth5  5.42.0-2
ii  libkf5completion55.42.0-4
ii  libkf5configcore55.42.0-2
ii  libkf5configgui5 5.42.0-2
ii  libkf5configwidgets5 5.42.0-2
ii  libkf5coreaddons55.42.0-2
ii  libkf5declarative5   5.42.0-2
ii  libkf5globalaccel5   5.42.0-2
ii  libkf5globalaccelprivate55.42.0-2
ii  libkf5i18n5  5.42.0-3
ii  libkf5kcmutils5  5.42.0-2
ii  libkf5kiowidgets55.42.0-3
ii  libkf5newstuff5  5.42.0-2
ii  libkf5notifications5 5.42.0-2
ii  libkf5package5   5.42.0-2
ii  libkf5plasma55.42.0-3
ii  libkf5service-bin5.42.0-2
ii  libkf5service5   5.42.0-2
ii  libkf5textwidgets5   5.42.0-2
ii  libkf5waylandclient5 4:5.42.0-2
ii  libkf5waylandserver5 4:5.42.0-2
ii  libkf5widgetsaddons5 5.42.1-2
ii  libkf5windowsystem5  5.42.0-2
ii  libkf5xmlgui55.42.0-2
ii  libkscreenlocker55.12.2-1
ii  libkwin4-effect-builtins14:5.12.1-1
ii  libkwineffects11 4:5.12.1-1
ii  libkwinglutils11 4:5.12.1-1
ii  libkwinxrenderutils114:5.12.1-1
ii  libqt5core5a 5.9.2+dfsg-12
ii  libqt5dbus5  5.9.2+dfsg-12
ii  libqt5gui5   5.9.2+dfsg-12
ii  libqt5qml5   5.9.2-3
ii  libqt5quick5 5.9.2-3
ii  libqt5script55.9.2+dfsg-2
ii  libqt5sensors5   5.9.2-2
ii  libqt5widgets5   5.9.2+dfsg-12
ii  libqt5x11extras5 5.9.2-1
ii  libsm6   2:1.2.2-1+b3
ii  libstdc++6   8-20180218-1
ii  libudev1 237-3
ii  libwayland-cursor0   1.14.0-1+b1
ii  libx11-6 2:1.6.4-3
ii  libxcb-composite01.12-1
ii  libxcb-cursor0   0.1.1-4
ii  libxcb-damage0   1.12-1
ii  libxcb-glx0  1.12-1
ii  libxcb-icccm40.4.1-1+b1
ii  libxcb-keysyms1  0.4.0-1+b2
ii  libxcb-randr01.12-1
ii  libxcb-render0   1.12-1
ii  libxcb-shape01.12-1
ii  libxcb-shm0  1.12-1
ii  libxcb-sync1  

Bug#892203: kwayland: Implement zwp_linux_dmabuf_v1

[Heather Ellsworth]

Source: kwayland
Version: 5.12.1-1
Severity: important

Dear Maintainer,

zwp_linux_dmabuf protocol support is needed to properly work with the drm
backend to display Plasma Mobile on the Librem 5 development board.

The implementation of zwp_linux_dmabuf support is being tracked by KDE in
https://phabricator.kde.org/D10747

Also see relating email thread for complete details:
https://www.mail-archive.com/plasma-devel@kde.org/msg81108.html

The proposed patches attached to D10747 (and this bug report) do indeed
fix the display issue.

Please consider carrying the kwin patch ahead of the Plasma 5.13 release
(scheduled for June 2018).

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

Kernel: Linux 4.15.0-g837bff1 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot
set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ANSI_X3.4-1968), LANGUAGE=en_US.UTF-8 (charmap=locale: Cannot set
LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff --git a/src/client/protocols/linux-dmabuf-unstable-v1.xml b/src/client/protocols/linux-dmabuf-unstable-v1.xml
new file mode 100644
--- /dev/null
+++ b/src/client/protocols/linux-dmabuf-unstable-v1.xml
@@ -0,0 +1,348 @@
+
+
+
+  
+Copyright © 2014, 2015 Collabora, Ltd.
+
+Permission is hereby granted, free of charge, to any person obtaining a
+copy of this software and associated documentation files (the "Software"),
+to deal in the Software without restriction, including without limitation
+the rights to use, copy, modify, merge, publish, distribute, sublicense,
+and/or sell copies of the Software, and to permit persons to whom the
+Software is furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice (including the next
+paragraph) shall be included in all copies or substantial portions of the
+Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
+THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
+DEALINGS IN THE SOFTWARE.
+  
+
+  
+
+  Following the interfaces from:
+  https://www.khronos.org/registry/egl/extensions/EXT/EGL_EXT_image_dma_buf_import.txt
+  and the Linux DRM sub-system's AddFb2 ioctl.
+
+  This interface offers ways to create generic dmabuf-based
+  wl_buffers. Immediately after a client binds to this interface,
+  the set of supported formats and format modifiers is sent with
+  'format' and 'modifier' events.
+
+  The following are required from clients:
+
+  - Clients must ensure that either all data in the dma-buf is
+coherent for all subsequent read access or that coherency is
+correctly handled by the underlying kernel-side dma-buf
+implementation.
+
+  - Don't make any more attachments after sending the buffer to the
+compositor. Making more attachments later increases the risk of
+the compositor not being able to use (re-import) an existing
+dmabuf-based wl_buffer.
+
+  The underlying graphics stack must ensure the following:
+
+  - The dmabuf file descriptors relayed to the server will stay valid
+for the whole lifetime of the wl_buffer. This means the server may
+at any time use those fds to import the dmabuf into any kernel
+sub-system that might accept it.
+
+  To create a wl_buffer from one or more dmabufs, a client creates a
+  zwp_linux_dmabuf_params_v1 object with a zwp_linux_dmabuf_v1.create_params
+  request. All planes required by the intended format are added with
+  the 'add' request. Finally, a 'create' or 'create_immed' request is
+  issued, which has the following outcome depending on the import success.
+
+  The 'create' request,
+  - on success, triggers a 'created' event which provides the final
+wl_buffer to the client.
+  - on failure, triggers a 'failed' event to convey that the server
+cannot use the dmabufs received from the client.
+
+  For the 'create_immed' request,
+  - on success, the server immediately imports the added dmabufs to
+create a wl_buffer. No event is 

Bug#888515: debian-installer: UEFI boot menu (grub) misses the help screen

[Samuel Thibault]

Hello,

Samuel Thibault, on lun. 05 févr. 2018 10:31:40 +0100, wrote:
> I have reported the feature request to http://savannah.gnu.org/bugs/?53065

Here is an answer:

“
the solution which is available atm is:

set pager=1
cat ($root)/boot/grub/MESSAGE.txt
unset pager
echo -n "-- Press ESC or wait 60 sec to continue: "
sleep --verbose --interruptible  60

There is no pause command. To stop for a minute before showing the menu: sleep
continues on Escape key only.
”

Samuel

Bug#891907: memcached should disable UDP by default

[Guillaume Delacour]

Hi,

Le 02/03/2018 à 12:39, Hanno Böck a écrit :
> Package: memcached
> Version: 1.4.33-1
> 
> Memcached is currently involved in some massive ddos attacks, see e.g.:
> https://blog.cloudflare.com/memcrashed-major-amplification-attacks-from-port-11211/
> 
> The UDP protocol of memcached can be abused for very effective DDoS
> amplification attacks and should therefore be considered dangerous.
> Upstream memcached has reacted to this by disabling UDP by default:
> https://github.com/memcached/memcached/wiki/ReleaseNotes156
> 
> In Debian memcached by default only listens to 127.0.0.1, but enables
> UDP. While the localhost-only protects default settings, it's still
> only a minor change away from creating an effective DDoS tool for a
> protocol that is hardly in use today. I recommend that you backport
> the upstream change and disable UDP by default.
> 

The version 1.5.6 will be uploaded in the archive in a few days.
I'll try to propose a backport patch at least for versions in stretch
and jessie (with upstream review, if possible).

-- 
Guillaume Delacour



signature.asc
Description: OpenPGP digital signature

Bug#892163: Acknowledgement (fai-setup-storage fails with "Invalid dev children setting")

[Matthew Vernon]

Hi,

For reference, the underlying issue was that there was some stray md
metadata left on one of the devices (which I think was meaning md was
incorrectly trying to build the wrong array); deleting it with
--zero-superblock let FAI continue successfully.

While spotting that might be a bit more than you could expect from
setup-storage, I think it's error handling could be a bit more robust
(which is presumably why it said "please open a bug report" :-) )

Regards,

Matthew


-- 
 The Wellcome Sanger Institute is operated by Genome Research 
 Limited, a charity registered in England with number 1021457 and a 
 company registered in England with number 2742969, whose registered 
 office is 215 Euston Road, London, NW1 2BE. 

Bug#892175: pycryptodome FTBFS on 32bit big endian: src/montgomery.c:245: mont_mult: Assertion `t[2*abn_words] <= 1' failed

[James Cowgill]

On Tue, 06 Mar 2018 14:26:31 +0200 Adrian Bunk  wrote:
> Source: pycryptodome
> Version: 3.4.11-1
> Severity: serious
> 
> https://buildd.debian.org/status/package.php?p=pycryptodome=sid
> 
> ...
>debian/rules override_dh_auto_test
> make[1]: Entering directory '/<>'
> PYBUILD_SYSTEM=custom \
> PYBUILD_TEST_ARGS="python{version} -m Cryptodome.SelfTest 
> {build_dir}/" dh_auto_test
> I: pybuild base:184: python2.7 -m Cryptodome.SelfTest 
> /<>/.pybuild/pythonX.Y_2.7/build/
> Skipping AESNI tests
> python2.7: src/montgomery.c:245: mont_mult: Assertion `t[2*abn_words] <= 1' 
> failed.
> Aborted

I've only had a brief look, but there are some (uint64_t*) to
(uint32_t*) casts in src/multiply_32.c addmul128 which look like
undefined behavior to me (strict aliasing rule).

I notice BEBIT which looks like an attempt at big-endian support which
clearly hasn't worked.

A recent commit I noticed:
https://github.com/Legrandin/pycryptodome/commit/aa5fac10a1c3a5f2b98c35954ae74207d545ec13

James



signature.asc
Description: OpenPGP digital signature

Bug#892201: nlohmann-json build issues with gcc 7.2

[Dominique Belhachemi]

Package: nlohmann-json
Version: 2.1.1-1
Severity: grave

Some applications don't compile with nlohmann-json 2.1.1 and gcc 7.2 .

You can find details here:

https://github.com/nlohmann/json/issues/742

Please update the package.

Thanks
-Dominique

Bug#887243: qa upload of gfxboot

[Andreas Henriksson]

Debdiff attached.

diff -Nru gfxboot-4.5.2-1.1/debian/changelog gfxboot-4.5.2-1.1/debian/changelog
--- gfxboot-4.5.2-1.1/debian/changelog  2014-07-25 20:58:48.0 +0200
+++ gfxboot-4.5.2-1.1/debian/changelog  2018-03-06 17:08:15.0 +0100
@@ -1,3 +1,14 @@
+gfxboot (4.5.2-1.1-6) unstable; urgency=medium
+
+  * QA Upload.
+  * Add e2fsprogs to Recommends, also add reiserfsprogs and xfsprogs to
+Suggests. (Closes: #887243)
+  * Add debian/watch pointing to https://github.com/OpenSUSE/gfxboot
+  * Do dbgsym migration and drop gfxboot-dbg package.
+  * Switch from deprecated Priority: extra to optional.
+
+ -- Andreas Henriksson   Tue, 06 Mar 2018 17:08:15 +0100
+
 gfxboot (4.5.2-1.1-5) unstable; urgency=low
 
   * I don't care anymore, not worth it.. orphaning.
diff -Nru gfxboot-4.5.2-1.1/debian/control gfxboot-4.5.2-1.1/debian/control
--- gfxboot-4.5.2-1.1/debian/control2014-07-25 20:58:37.0 +0200
+++ gfxboot-4.5.2-1.1/debian/control2018-03-06 17:08:15.0 +0100
@@ -1,6 +1,6 @@
 Source: gfxboot
 Section: misc
-Priority: extra
+Priority: optional
 Maintainer: Debian QA Group 
 Build-Depends:
  debhelper (>= 9),
@@ -20,27 +20,14 @@
 Depends:
  ${misc:Depends},
  ${shlibs:Depends},
-Suggests: gfxboot-themes
+Recommends: e2fsprogs
+Suggests: gfxboot-themes, reiserfsprogs, xfsprogs
 Description: tool to test and create graphical boot logos (runtime)
  gfxboot is a tool to test and create graphical boot logos for gfxboot 
compliant
  boot loaders. Currently, this includes grub, lilo, and syslinux (all 
payloads).
  .
  This package contains the runtime utility.
 
-Package: gfxboot-dbg
-Section: debug
-Priority: extra
-Architecture: any-amd64 any-i386
-Depends:
- ${misc:Depends},
- gfxboot (= ${binary:Version}),
- gfxboot-dev (= ${binary:Version}),
-Description: tool to test and create graphical boot logos (debug)
- gfxboot is a tool to test and create graphical boot logos for gfxboot 
compliant
- boot loaders. Currently, this includes grub, lilo, and syslinux (all 
payloads).
- .
- This package contains the debugging symbols.
-
 Package: gfxboot-dev
 Architecture: any-amd64 any-i386
 Depends:
diff -Nru gfxboot-4.5.2-1.1/debian/rules gfxboot-4.5.2-1.1/debian/rules
--- gfxboot-4.5.2-1.1/debian/rules  2014-06-24 16:43:33.0 +0200
+++ gfxboot-4.5.2-1.1/debian/rules  2018-03-06 17:08:15.0 +0100
@@ -93,4 +93,4 @@
dh_install --fail-missing
 
 override_dh_strip:
-   dh_strip --dbg-package=gfxboot-dbg
+   dh_strip --dbgsym-migration='gfxboot-dbg (<< 4.5.2-1.1-6~)'
diff -Nru gfxboot-4.5.2-1.1/debian/watch gfxboot-4.5.2-1.1/debian/watch
--- gfxboot-4.5.2-1.1/debian/watch  1970-01-01 01:00:00.0 +0100
+++ gfxboot-4.5.2-1.1/debian/watch  2018-03-06 17:08:15.0 +0100
@@ -0,0 +1,3 @@
+version=4
+opts=filenamemangle=s/.+\/v?(\d\S+)\.tar\.gz/gfxboot-$1\.tar\.gz/ \
+  https://github.com/OpenSUSE/gfxboot/tags .*/v?(\d\S+)\.tar\.gz

Bug#892200: qdbm: FTBFS on arches without openjdk

[Jason Duerstock]

Source: qdbm
Severity: normal
Tags: patch
User: debian-i...@lists.debian.org
Usertags: ia64

Dear Maintainer,

As currently configured, gcc-7 does not know where to find the Java jni.h 
headers if the arch is
using gcj rather than openjdk. [1]  The attached patch should clean up the Java 
detection and set
the relevant environment variables correctly.

[1] 
https://buildd.debian.org/status/fetch.php?pkg=qdbm=ia64=1.8.78-6.2=1518046955=0


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

Kernel: Linux 3.14-0.bpo.2-mckinley (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)
--- qdbm-1.8.78/debian/rules2018-02-06 10:12:44.0 -0500
+++ qdbm-1.8.78-new/debian/rules2018-03-06 11:19:25.125571799 -0500
@@ -43,13 +43,12 @@
--includedir=\$${prefix}/include/qdbm \
--enable-pthread --enable-zlib --enable-iconv
 
-DEFAULT_JAVA ?= $(shell readlink /etc/alternatives/java | sed 
s@/jre/bin/java@@)
-ifneq (,$(findstring /usr/bin/gij,$(DEFAULT_JAVA)))
+JAVA_HOME = /usr/lib/jvm/default-java
+CONFIGURE_VARS += JAVA_HOME="$(JAVA_HOME)"
+DEFAULT_JAVA ?= $(shell readlink -f $(JAVA_HOME)/bin/java)
+ifneq (,$(filter /usr/bin/%gij%, $(DEFAULT_JAVA)))
 CONFIGURE_VARS += JAVAC="gcj-wrapper" JAR="fastjar"
 CONFIGURE_SWITCHES += --with-gcj
-else
-JAVA_HOME = $(DEFAULT_JAVA)
-CONFIGURE_VARS += JAVA_HOME="$(JAVA_HOME)"
 endif
 
 build: build-arch build-indep

Bug#892199: r-cran-knitr: autopkgtest failure

[Graham Inggs]

Source: r-cran-knitr
Version: 1.20-1
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic autopkgtest

Hi Andreas

Since the upload of 1.20-1, r-cran-knitr's autopkgtests have been
failing [1].  There are new tests that require r-cran-tinytex which is
not yet packaged in Debian.

Regards
Graham


[1] https://ci.debian.net/packages/r/r-cran-knitr/unstable/amd64/