Bug#912087: openssh-server: Slow startup after the upgrade to 7.9p1

[jim_p]

Package: openssh-server
Version: 1:7.9p1-1
Severity: normal

Dear Maintainer,

After yesterdays upgrade to 7.9p1 in testing, openssh-server delays my system's
boot by quite some time.
In fact, it is always the first and slowest to start process in systemd-analyze
blame, with times varying from < 20 seconds most of the time

 19.044s ssh.service
  2.083s ifupdown-wait-online.service

to this insane 100+ second delay I found out yesterday

1min 24.779s ssh.service
  1.120s ifupdown-wait-online.service

Even those 20 seconds are a lot, because due to its delay, my boot time (as
mentioned by systemd-analyze) increased from 5-7 seconds to 20+. The os is on
an ssd drive obviously.

If it helps, I have ipv6 disabled system-wide with this kernel parameter:
ipv6.disable=1.



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

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

Versions of packages openssh-server depends on:
ii  adduser3.118
ii  debconf [debconf-2.0]  1.5.69
ii  dpkg   1.19.2
ii  libaudit1  1:2.8.4-2
ii  libc6  2.27-6
ii  libcom-err21.44.4-2
ii  libgssapi-krb5-2   1.16.1-1
ii  libkrb5-3  1.16.1-1
ii  libpam-modules 1.1.8-3.8
ii  libpam-runtime 1.1.8-3.8
ii  libpam0g   1.1.8-3.8
ii  libselinux12.8-1+b1
ii  libssl1.1  1.1.1-1
ii  libsystemd0239-10
ii  libwrap0   7.6.q-27
ii  lsb-base   9.20170808
ii  openssh-client 1:7.9p1-1
ii  openssh-sftp-server1:7.9p1-1
ii  procps 2:3.3.15-2
ii  ucf3.0038
ii  zlib1g 1:1.2.11.dfsg-1

Versions of packages openssh-server recommends:
ii  libpam-systemd  239-10
ii  ncurses-term6.1+20181013-1
ii  xauth   1:1.0.10-1

Versions of packages openssh-server suggests:
pn  molly-guard   
pn  monkeysphere  
pn  rssh  
pn  ssh-askpass   
pn  ufw   

-- debconf information:
  openssh-server/password-authentication: true
  openssh-server/permit-root-login: true

Bug#912084: (python3.7: Upgrade to python3.7 changes string/byte processing, breaks rdepends)

[Scott Kitterman]

It looks like it's the combination of these two changes:

https://bugs.python.org/issue25054
https://bugs.python.org/issue32308

No idea what else that broke.

Scott K

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

Bug#911976: bind-dyndb-ldap FTBFS with bind 9.11.5

[peter green]

Tags 911976 +patch
Thanks

This seems to be a simple case of a missing include, I just uploaded a fix to 
raspbian. A debdidf should appear soon at 
https://debdiffs.raspbian.org/main/b/bind-dyndb-ldap . No intent to NMU in 
Debian.

Bug#912086: ibus-chewing: Cannot commit text under libvte-based terminal

[魏銘廷]

Package: ibus-chewing
Version: 1.5.1-3
Severity: important

Hi,

While bopomofo does type, I cannot commit the text into the terminal
by pressing enter.  The text in the buffer disappears and does not
commit into the terminal.

It seems it happens in any libvte-based terminal (tested gnome-terminal
and lxterminal).

Other input methods under ibus could work (tested ibus-mozc).

The desktop environment I am using is GNOME3 with Wayland.

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

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

Versions of packages ibus-chewing depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.0-1
ii  ibus 1.5.19-1
ii  libc62.27-6
ii  libchewing3  0.5.1-4
ii  libglib2.0-0 2.58.1-2
ii  libgtk2.0-0  2.24.32-3
ii  libibus-1.0-51.5.19-1
ii  libx11-6 2:1.6.7-1

ibus-chewing recommends no packages.

ibus-chewing suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature

Bug#911739: Acknowledgement (mirrors: Debian mirror ftp.utexas.edu: HTTP 403 on everything for about 5 days)

[Matt Roberds]

All,

This problem seems to have resolved itself.  As of 2018-10-26 02:25,
mirror-master.debian.org reports ftp.utexas.edu as being up and current
again.

As of 2018-10-28 03:15 UTC, the University of Texas has a related
message on their status site:

https://ut.service-now.com/utss/outage.do?sysparam_sys_id=950a4caadbddab8c819ec443059619f4


Campus Public FTP Server Outage

OUTAGE: ftp.utexas.edu - 403 forbidden

The server for ftp.utexas.edu has suffered irrecoverable hardware
failure. Networking is investigating options for bringing up an
alternate host/VM to function as ftp.utexas.edu. There is not a
current estimated time to recovery, as the mirrors will also need to
be re-built after the server is brought back online.

Latest Update: 2018-10-24 12:04:22 -


There is no update or resolution notice posted, but the mirror seems
to have been up and running for a little over 48 hours now.

I added ftp.utexas.edu back to my sources.list and tried aptitude; it
worked and is able to download and install packages from that mirror.

I also tried manually downloading a couple of files from the mirror in
Firefox and those worked OK.

This report can probably be closed.

Thanks!

Matt Roberds

Bug#586709: closed by Thomas Goirand

[Daniel Richard G.]

Arrgh, my apologies, everyone. Despite being the reporter, I have not
been receiving any messages on this thread save for those Cc'ed to me.

I have re-subscribed to my own bug and will hopefully not miss any
further updates.

On Sat, 2018 Oct 27 22:53+0100, Ian Jackson wrote:
>
> That it's a bug in just that one package is good because if halt
> sometimes does its work by indirecting via init(8) and
> /etc/init.d/halt, then it is more convenient to improve the
> communication if both things are in the same package.

Certainly. I'm not clear on how the communication was originally
intended to work, but what's there now does not appear to support the
expected behavior (or documented behavior, at least for one reasonable
interpretation of the docs).

The /run solution sounds quite reasonable to me.


--Daniel

Bug#907335: similar issue

[Yaroslav Halchenko]

thanks!  upstream says the issue was fixed in
https://github.com/pydata/patsy/pull/131
so I will just build a fresh snapshot

Cheers!

On Sat, 27 Oct 2018, Julian Taylor wrote:

> this problem probably has the same python change as cause as this issue:

> https://github.com/PyCQA/pycodestyle/issues/786
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908700


-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik


signature.asc
Description: PGP signature

Bug#912085: linux-image-4.18.0-0.bpo.1-amd64: boot error: [ 0.004000] do_IRQ: 1.55 No irq handler for vector

[Costas Ganis]

Package: src:linux
Version: 4.18.6-1~bpo9+1
Severity: normal

Dear Maintainer,

on boot it displays:

[0.004000] do_IRQ: 1.55 No irq handler for vector

I tried several solutions found on the web mainly editing /etc/default/grub but
nothing works.



-- Package-specific info:
** Version:
Linux version 4.18.0-0.bpo.1-amd64 (debian-ker...@lists.debian.org) (gcc 
version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 SMP Debian 4.18.6-1~bpo9+1 
(2018-09-13)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.18.0-0.bpo.1-amd64 
root=UUID=8a914cf3-ceb4-4516-8b12-3a8e26416737 ro quiet pci=direct 
acpi_osi=Linux acpi_backlight=video

** Not tainted

** Kernel log:
[   37.130552] audit: type=1400 audit(1540694659.115:10): apparmor="STATUS" 
operation="profile_load" profile="unconfined" 
name="/usr/bin/evince//sanitized_helper" pid=602 comm="apparmor_parser"
[   37.134701] audit: type=1400 audit(1540694659.119:11): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/bin/evince-previewer" 
pid=602 comm="apparmor_parser"
[   37.135701] audit: type=1400 audit(1540694659.119:12): apparmor="STATUS" 
operation="profile_load" profile="unconfined" 
name="/usr/bin/evince-previewer//sanitized_helper" pid=602 
comm="apparmor_parser"
[   37.139300] audit: type=1400 audit(1540694659.123:13): apparmor="STATUS" 
operation="profile_load" profile="unconfined" 
name="/usr/bin/evince-thumbnailer" pid=602 comm="apparmor_parser"
[   37.140287] audit: type=1400 audit(1540694659.127:14): apparmor="STATUS" 
operation="profile_load" profile="unconfined" 
name="/usr/bin/evince-thumbnailer//sanitized_helper" pid=602 
comm="apparmor_parser"
[   52.194970] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   52.471030] r8169 :04:00.0: firmware: direct-loading firmware 
rtl_nic/rtl8106e-1.fw
[   52.684264] r8169 :04:00.0 eth0: link down
[   52.684431] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   52.736446] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   52.751855] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   52.780635] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   54.756652] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   55.919843] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   55.995685] wlan0: authenticate with 88:d2:74:b8:dc:61
[   56.010135] wlan0: send auth to 88:d2:74:b8:dc:61 (try 1/3)
[   56.012484] wlan0: authenticated
[   56.016244] wlan0: associate with 88:d2:74:b8:dc:61 (try 1/3)
[   56.025656] wlan0: RX AssocResp from 88:d2:74:b8:dc:61 (capab=0x411 status=0 
aid=1)
[   56.025824] wlan0: associated
[   56.157575] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   58.273914] NET: Registered protocol family 3
[   58.685000] NET: Registered protocol family 5
[   72.051337] wlan0: deauthenticating from 88:d2:74:b8:dc:61 by local choice 
(Reason: 3=DEAUTH_LEAVING)
[   72.107209] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   72.735189] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   73.148216] r8169 :04:00.0 eth0: link down
[   73.148444] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   73.472261] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   76.924882] wlan0: authenticate with 88:d2:74:b8:dc:61
[   76.947508] wlan0: send auth to 88:d2:74:b8:dc:61 (try 1/3)
[   76.949495] wlan0: authenticated
[   76.952229] wlan0: associate with 88:d2:74:b8:dc:61 (try 1/3)
[   76.956352] wlan0: RX AssocResp from 88:d2:74:b8:dc:61 (capab=0x411 status=0 
aid=1)
[   76.956521] wlan0: associated
[   76.968741] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   79.394676] wlan0: deauthenticating from 88:d2:74:b8:dc:61 by local choice 
(Reason: 3=DEAUTH_LEAVING)
[   80.980543] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   81.051446] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   81.070643] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   81.129689] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   82.216246] wlan0: authenticate with 88:d2:74:b8:dc:61
[   82.234275] wlan0: send auth to 88:d2:74:b8:dc:61 (try 1/3)
[   82.238759] wlan0: authenticated
[   82.240433] wlan0: associate with 88:d2:74:b8:dc:61 (try 1/3)
[   82.244510] wlan0: RX AssocResp from 88:d2:74:b8:dc:61 (capab=0x411 status=0 
aid=1)
[   82.244683] wlan0: associated
[   82.244716] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[  100.528744] fuse init (API version 7.27)
[  112.214491] random: crng init done
[  112.214501] random: 7 urandom warning(s) missed due to ratelimiting
[  139.164586] wlan0: deauthenticating from 88:d2:74:b8:dc:61 by local choice 
(Reason: 3=DEAUTH_LEAVING)
[  140.706443] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[  140.746195] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  140.769634] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  140.798355] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  141.893318] wlan0: authenticate with 88:d2:74:b8:dc:61
[  141.913596] 

Bug#912084: python3.7: Upgrade to python3.7 changes string/byte processing, breaks rdepends

[Scott Kitterman]

Package: python3.7
Version: 3.7.1-1
Severity: important
Tags: upstream

Dear Maintainer,


   * What led up to the situation?

I ran the dkimpy test suite with both python3.6 and python3.7.

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

Running the test suite with python3.6 (and 2.7) results in all tests passing.
Runngin the test suite with python3.7 causes a large number of failures.

   * What was the outcome of this action?

See the upstream bug report for details:
https://bugs.launchpad.net/dkimpy/+bug/1800313

   * What outcome did you expect instead?

I expected stuff not to break with the new python3 version.

I suspect something has changed in how newlines are processed (which may, in
the end, account for all the failures), specifically these test results point
in that direction:

FAIL: test_adds_crlf (dkim.tests.test_canonicalization.TestRelaxedAlgorithmBody)
--
Traceback (most recent call last):
  File "/home/dkimpy.upstream/dkim/tests/test_canonicalization.py", line 124, 
in test_adds_crlf
b'Foo bar')
  File "/home/dkimpy.upstream/dkim/tests/test_canonicalization.py", line 32, in 
assertCanonicalForm
self.assertEqual(expected, self.func(expected))
AssertionError: b'Foo bar\r\n' != b'Foo bar\r\n\r\n'

FAIL: test_multiple_crlf_body 
(dkim.tests.test_canonicalization.TestRelaxedAlgorithmBody)
--
Traceback (most recent call last):
  File "/home/dkimpy.upstream/dkim/tests/test_canonicalization.py", line 139, 
in test_multiple_crlf_body
b'\r\n\r\n')
  File "/home/dkimpy.upstream/dkim/tests/test_canonicalization.py", line 33, in 
assertCanonicalForm
self.assertEqual(expected, self.func(input))
AssertionError: b'' != b'\r\n\r\n'

FAIL: test_single_crlf_body 
(dkim.tests.test_canonicalization.TestRelaxedAlgorithmBody)
--
Traceback (most recent call last):
  File "/home/dkimpy.upstream/dkim/tests/test_canonicalization.py", line 134, 
in test_single_crlf_body
b'\r\n')
  File "/home/dkimpy.upstream/dkim/tests/test_canonicalization.py", line 33, in 
assertCanonicalForm
self.assertEqual(expected, self.func(input))
AssertionError: b'' != b'\r\n\r\n'

FAIL: test_strips_trailing_empty_lines 
(dkim.tests.test_canonicalization.TestRelaxedAlgorithmBody)
--
Traceback (most recent call last):
  File "/home/dkimpy.upstream/dkim/tests/test_canonicalization.py", line 119, 
in test_strips_trailing_empty_lines
b'Foo\r\nbar\r\n\r\n\r\n')
  File "/home/dkimpy.upstream/dkim/tests/test_canonicalization.py", line 32, in 
assertCanonicalForm
self.assertEqual(expected, self.func(expected))
AssertionError: b'Foo\r\nbar\r\n' != b'Foo\r\nbar\r\n\r\n'

and many more similar.

Scott K

Bug#893685: Segfault after higher number of connections

[Víctor Martínez]

Package: siege
Version: 4.0.2-1.1+b1
Followup-For: Bug #893685

Dear Maintainer,

I have the same problem, attached is a strace of the program in the hope that 
could be useful. I was able to replicate on my three machines at work on ovh 
vps and home currently the strace is from work.

vicm3@janus:~$ siege -c 10 http://blografia.net/vicm3 -t 1m  -q
New configuration template added to /home/vicm3/.siege
Run siege -C to view the current settings in that file
[alert] Zip encoding disabled; siege requires zlib support to enable it: No 
such file or directory
^C
Lifting the server siege...*** Error in `siege': munmap_chunk(): invalid 
pointer: 0x55de77ebf440 ***
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x70bfb)[0x7f00b248fbfb]
/lib/x86_64-linux-gnu/libc.so.6(+0x76fc6)[0x7f00b2495fc6]
/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1(OPENSSL_sk_free+0x1e)[0x7f00b297ba1e]
/usr/lib/x86_64-linux-gnu/libssl.so.1.1(+0x2cb29)[0x7f00b2c7db29]
/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1(OPENSSL_cleanup+0x52)[0x7f00b2926242]
/lib/x86_64-linux-gnu/libc.so.6(+0x35940)[0x7f00b2454940]
/lib/x86_64-linux-gnu/libc.so.6(+0x3599a)[0x7f00b245499a]
siege(+0x651f)[0x55de7666e51f]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f00b243f2e1]
siege(+0x682a)[0x55de7666e82a]
=== Memory map: 
55de76668000-55de7668e000 r-xp  08:04 526238 
/usr/bin/siege
55de7688e000-55de7689 r--p 00026000 08:04 526238 
/usr/bin/siege
55de7689-55de76891000 rw-p 00028000 08:04 526238 
/usr/bin/siege
55de76891000-55de76892000 rw-p  00:00 0 
55de77eba000-55de77efa000 rw-p  00:00 0  [heap]
7f007c00-7f007c065000 rw-p  00:00 0 
7f007c065000-7f008000 ---p  00:00 0 
7f008000-7f0080021000 rw-p  00:00 0 
7f0080021000-7f008400 ---p  00:00 0 
7f008400-7f0084065000 rw-p  00:00 0 
7f0084065000-7f008800 ---p  00:00 0 
7f008b5c1000-7f008b5d7000 r-xp  08:02 393900 
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f008b5d7000-7f008b7d6000 ---p 00016000 08:02 393900 
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f008b7d6000-7f008b7d7000 r--p 00015000 08:02 393900 
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f008b7d7000-7f008b7d8000 rw-p 00016000 08:02 393900 
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f008b7d8000-7f008b7ec000 r-xp  08:02 393976 
/lib/x86_64-linux-gnu/libresolv-2.24.so
7f008b7ec000-7f008b9eb000 ---p 00014000 08:02 393976 
/lib/x86_64-linux-gnu/libresolv-2.24.so
7f008b9eb000-7f008b9ec000 r--p 00013000 08:02 393976 
/lib/x86_64-linux-gnu/libresolv-2.24.so
7f008b9ec000-7f008b9ed000 rw-p 00014000 08:02 393976 
/lib/x86_64-linux-gnu/libresolv-2.24.so
7f008b9ed000-7f008b9ef000 rw-p  00:00 0 
7f008b9ef000-7f008b9f4000 r-xp  08:02 393969 
/lib/x86_64-linux-gnu/libnss_dns-2.24.so
7f008b9f4000-7f008bbf3000 ---p 5000 08:02 393969 
/lib/x86_64-linux-gnu/libnss_dns-2.24.so
7f008bbf3000-7f008bbf4000 r--p 4000 08:02 393969 
/lib/x86_64-linux-gnu/libnss_dns-2.24.so
7f008bbf4000-7f008bbf5000 rw-p 5000 08:02 393969 
/lib/x86_64-linux-gnu/libnss_dns-2.24.so
7f008bbf5000-7f008bbf7000 r-xp  08:02 397949 
/lib/x86_64-linux-gnu/libnss_mdns4_minimal.so.2
7f008bbf7000-7f008bdf6000 ---p 2000 08:02 397949 
/lib/x86_64-linux-gnu/libnss_mdns4_minimal.so.2
7f008bdf6000-7f008bdf7000 r--p 1000 08:02 397949 
/lib/x86_64-linux-gnu/libnss_mdns4_minimal.so.2
7f008bdf7000-7f008bdf8000 rw-p 2000 08:02 397949 
/lib/x86_64-linux-gnu/libnss_mdns4_minimal.so.2
7f008bdf8000-7f008bdff000 r-xp  08:02 393977 
/lib/x86_64-linux-gnu/librt-2.24.so
7f008bdff000-7f008bffe000 ---p 7000 08:02 393977 
/lib/x86_64-linux-gnu/librt-2.24.so
7f008bffe000-7f008bfff000 r--p 6000 08:02 393977 
/lib/x86_64-linux-gnu/librt-2.24.so
7f008bfff000-7f008c00 rw-p 7000 08:02 393977 
/lib/x86_64-linux-gnu/librt-2.24.so
7f008c00-7f008c065000 rw-p  00:00 0 
7f008c065000-7f009000 ---p  00:00 0 
7f009000-7f0090063000 rw-p  00:00 0 
7f0090063000-7f009400 ---p  00:00 0 
7f009400-7f0094067000 rw-p  00:00 0 
7f0094067000-7f009800 ---p  00:00 0 
7f009800-7f0098065000 rw-p  00:00 0 
7f0098065000-7f009c00 ---p  00:00 0 
7f009c00-7f009c045000 rw-p  00:00 0 
7f009c045000-7f00a000 ---p  00:00 0 
7f00a000-7f00a0065000 rw-p  00:00 0 
7f00a0065000-7f00a400 ---p  00:00 0 
7f00a400-7f00a4065000 rw-p  00:00 0 

Bug#894675: Info received (gdebi-gtk is not installing packages)

[Cagla Alican]

Opening

Bug#912083: nmudiff: please support also neomutt

[Reiner Herrmann]

Package: devscripts
Version: 2.18.7
Severity: wishlist
User: debian-rele...@lists.debian.org
Usertags: bsp-2018-10-de-karlsruhe

Dear Maintainer,

nmudiff is currently only able to use mutt for sending mails,
not neomutt, so it was falling back to using sendmail:

$ nmudiff
nmudiff: can't find mutt, falling back to sendmail instead

It would be nice if it could detect and use neomutt as well.

Kind regards,
   Reiner

Bug#912082: aptitude: use apt-file and dpkg -L to add list of files to the UI for each source/binary package

[Paul Wise]

Package: aptitude
Version: 0.8.11-3+b1
Severity: wishlist

In the UI for individual source/binary packages when apt-file is
installed it would be nice to have a listing of the files that are
available in the package.

For packages that are installed, the `dpkg-query --listfiles` command
will be faster than apt-file and available when it isn't installed.

It might also be interesting to highlight files that are missing from
the system (such as via dpkg excludes) or modified from the package
(using the debsums input files).

-- 
bye,
pabs

https://bonedaddy.net/pabs3/


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

Bug#894675: gdebi-gtk is not installing packages

[Cagla Alican]

Opening

23 Eki 2018 ÖS 10:40 tarihinde cagla.bak...@hotmail.com yazdı:

On Sat, 23 Jun 2018 20:58:59 +0800 Boyuan Yang <073p...@gmail.com> wrote:
> Version: 0.9.5.7+nmu2
>
> On Tue, 3 Apr 2018 08:59:52 +0200 Narcis Garcia  wrote:
> > Package: gdebi
> > Version: 0.9.5.7+nmu1
> > Severity: grave
> >
> > Package structure interface appears and it's usable; if user tries
> > button [Install Package], gksu asks for authorisation and nothing more:
> > package is not installed and gdebi-gtk disappears.
> >
> > $ gdebi-gtk AnyPackage.deb
> > /home/user/.gtkrc-2.0:38: Unable to find include file: "main.rc"
> > /home/user/.gtkrc-2.0:39: Unable to find include file: "apps.rc"
> > /home/user/.gtkrc-2.0:40: Unable to find include file: "hacks.rc"
> > /home/user/.gtkrc-2.0:41: Unable to find include file: "hacks-dark.rc"
> > $ echo $?
> > 1
> >
> >
> > *.rc messages appear just when pressing [Install Package] button
> > Execution ends just after gksu authorisation.
>
> With the migration away from gksu in v0.9.5.7+nmu2, this bug should be fixed.
> I have tested installation with new version and no error took place. Closing
> this bug now.
>
> Please feel free to reopen this bug and provide with more information if you
> consider this bug still exists.
>
> --
> Regards,
> Boyuan Yang

Watch entire
The following URL
Lenovo TAB 2 A8-50

Bug#912081: Why/how is this package even in Debian?

[Steve McIntyre]

Package: mpi-testsuite
Version: 3.2+dfsg-1
Severity: grave

I've been trying to debug why this package is *semi-randomly* failing
for me when attempting to rebuild it for armel and armhf on arm64
systems. Looking at failed build logs, I can see lots and lots of
nasty-looking error messages warning about segmentation faults,
floating point exceptions etc. Then I checked in the "successful"
build logs and I'm seeing exactly the same stuff.

So I've just checked in the logs from Debian's buildds and I'm seeing
exactly the same kind of thing. These errors are not being picked up
on at all in the "successful" builds. Failed builds are typically
being failed for timing out, not for any error checking in the build.

What is this package even for? Why should it be in Debian in this state?

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

Kernel: Linux 4.9.0-8-amd64 (SMP w/4 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)

Bug#778889: wine dont find mono-complete package

[Alexandre Viau]

Just to clarify, wine dosen't fine mono-complete because it isn't
looking for it.

Instead, wine requires a windows build of mono.

I have begun working on this.

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#778889: wine dont find mono-complete package

[Alexandre Viau]

Just to clarify, wine dosen't find mono-complete because it isn't
looking for it.

Instead, wine requires a windows build of mono.

I have begun working on this.

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#630661: Applied upstream

[Jesse Smith]

This patch has been applied upstream. Can close this bug as the updated
documentation will appear in SysV init 2.92.

- Jesse (upstream dev)

Bug#912080: vlc GUI does not start

[Sergey Spiridonov]

Package: src:vlc
Version: 3.0.3-1-0+deb9u1
Severity: important

Dear Maintainer,

   * What led up to the situation?

aptitude upgrade some weeks or months ago.

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

Just start vlc

   * What was the outcome of this action?

vlc runs, but no GUI appears. It is consuming CPU. Seems something is wrong 
withthe Qt initialization

There are other reports with same problem:

https://forum.videolan.org/viewtopic.php?t=144780
https://forum.videolan.org/viewtopic.php?f=13=144430
https://forum.mxlinux.org/viewtopic.php?f=104=45284

I tried rm -rf ~/.config/vlc without success

If I start cvlc movie.avi, it works without problem. The problem is only with 
vlc.

Downgrading to 3.0.2 does not help - probably some library problem.

I have intel gc

VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller (rev 06) (prog-if 00 [VGA controller])

In attachment you can find output of vlc -vvv

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

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

Versions of packages vlc depends on:
ii  dpkg 1.18.25
ii  vlc-bin  3.0.3-1-0+deb9u1
ii  vlc-l10n 3.0.3-1-0+deb9u1
ii  vlc-plugin-base  3.0.3-1-0+deb9u1
ii  vlc-plugin-qt3.0.3-1-0+deb9u1
ii  vlc-plugin-video-output  3.0.3-1-0+deb9u1

Versions of packages vlc recommends:
pn  vlc-plugin-notify  
pn  vlc-plugin-samba   
pn  vlc-plugin-skins2  
pn  vlc-plugin-video-splitter  
pn  vlc-plugin-visualization   

vlc suggests no packages.

Versions of packages libvlc-bin depends on:
ii  libc62.24-11+deb9u3
ii  libvlc5  3.0.3-1-0+deb9u1

Versions of packages libvlc5 depends on:
ii  dpkg 1.18.25
ii  libc62.24-11+deb9u3
ii  libvlccore9  3.0.3-1-0+deb9u1

Versions of packages libvlc5 recommends:
ii  libvlc-bin  3.0.3-1-0+deb9u1

Versions of packages vlc-bin depends on:
ii  libc6   2.24-11+deb9u3
ii  libvlc-bin  3.0.3-1-0+deb9u1
ii  libvlc5 3.0.3-1-0+deb9u1

Versions of packages vlc-plugin-base depends on:
ii  dpkg 1.18.25
ii  liba52-0.7.4 0.7.4-19
ii  libarchive13 3.2.2-2
ii  libasound2   1.1.3-5
ii  libass5  1:0.13.4-2
ii  libavahi-client3 0.6.32-2
ii  libavahi-common3 0.6.32-2
ii  libavc1394-0 0.5.4-4+b1
ii  libavcodec57 7:3.2.12-1~deb9u1
ii  libavformat577:3.2.12-1~deb9u1
ii  libavutil55  7:3.2.12-1~deb9u1
ii  libbasicusageenvironment12016.11.28-1
ii  libbluray1   1:0.9.3-3
ii  libc62.24-11+deb9u3
ii  libcairo21.14.8-1
ii  libcddb2 1.3.2-5
ii  libchromaprint1  1.4.2-1
ii  libcrystalhd31:0.0~git20110715.fdd2f19-12
ii  libdbus-1-3  1.10.26-0+deb9u1
ii  libdc1394-22 2.2.5-1
ii  libdca0  0.0.5-10
ii  libdvbpsi10  1.3.0-5
ii  libdvdnav4   5.0.3-3
ii  libdvdread4  5.0.3-2
ii  libebml4v5   1.3.4-1
ii  libfaad2 2.8.0~cvs20161113-1+deb9u1
ii  libflac8 1.3.2-1
ii  libfontconfig1   2.11.0-6.7+b1
ii  libfreetype6 2.6.3-3.2
ii  libfribidi0  0.19.7-1+b1
ii  libgcc1  1:6.3.0-18+deb9u1
ii  libgcrypt20  1.7.6-2+deb9u3
ii  libglib2.0-0 2.50.3-2
ii  libgnutls30  3.5.8-5+deb9u3
ii  libgpg-error01.32-1~bpo9+1
ii  libgroupsock82016.11.28-1
ii  libharfbuzz0b1.4.2-1
ii  libjpeg62-turbo  1:1.5.1-2
ii  libkate1 0.4.1-7+b1
ii  liblirc-client0  0.9.4c-9
ii  liblivemedia57   2016.11.28-1
ii  liblua5.2-0  5.2.4-1.1+b2
ii  libmad0  0.15.1b-8+deb9u1
ii  libmatroska6v5   1.4.5-2
ii  libmicrodns0 0.0.3-3
ii  libmpcdec6   2:0.1~r495-1+b1
ii  libmpeg2-4   0.5.1-7+b2
ii  libmpg123-0  1.23.8-1+b1
ii  libmtp9 

Bug#912079: progress: monitoring overall progress of commands with multiple file arguments

[Paul Wise]

Package: progress
Version: 0.14-2
Severity: wishlist

When I am copying multiple large files I am interested in not only the
progress of the current file but also the overall progress of copying
all of the files. It would be nice if progress could detect when a
command uses multiple file arguments, get the sizes of all of them, get
the location in the sequence from the open files of the command and
then calculate the overall progress based on the location in the
sequence (assuming items before the current one are completed) and the
progress of the current item.

-- 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.18.0-2-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)
LSM: AppArmor: enabled

Versions of packages progress depends on:
ii  libc62.27-6
ii  libncurses6  6.1+20181013-1
ii  libtinfo66.1+20181013-1

progress recommends no packages.

progress suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#719273: Patch applied upstream

[Jesse Smith]

The patch for killall5.c (pidof) has been applied upstream. Assuming
testing goes well, it'll be included in version 2.92 of sysvinit.

- Jesse (upstream dev)

Bug#879756: marble: diff for NMU version 4:17.08.3-3.1

[reiner]

Control: tags 879756 + pending

Dear maintainer,

I've prepared an NMU for marble (versioned as 4:17.08.3-3.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru marble-17.08.3/debian/changelog marble-17.08.3/debian/changelog
--- marble-17.08.3/debian/changelog 2018-01-11 14:31:18.0 +0100
+++ marble-17.08.3/debian/changelog 2018-10-27 13:38:29.0 +0200
@@ -1,3 +1,11 @@
+marble (4:17.08.3-3.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Add missing qml-module dependencies for marble-maps. (Closes: #879756)
+  * Add patch to build with Qt 5.11 by including missing headers.
+
+ -- Reiner Herrmann   Sat, 27 Oct 2018 13:38:29 +0200
+
 marble (4:17.08.3-3) unstable; urgency=medium
 
   * Team upload.
diff -Nru marble-17.08.3/debian/control marble-17.08.3/debian/control
--- marble-17.08.3/debian/control   2018-01-02 20:00:03.0 +0100
+++ marble-17.08.3/debian/control   2018-10-27 13:37:34.0 +0200
@@ -145,7 +145,12 @@
 Section: misc
 Depends: marble-data (>= ${source:Version}),
  marble-plugins (= ${binary:Version}),
+ qml-module-qtgraphicaleffects,
  qml-module-qtmultimedia,
+ qml-module-qtquick-dialogs,
+ qml-module-qtquick-controls,
+ qml-module-qtquick-controls2,
+ qml-module-qtquick-window2,
  ${misc:Depends},
  ${shlibs:Depends},
 Suggests: gosmore, monav-routing-daemon, routino
diff -Nru marble-17.08.3/debian/patches/qt5.11.patch 
marble-17.08.3/debian/patches/qt5.11.patch
--- marble-17.08.3/debian/patches/qt5.11.patch  1970-01-01 01:00:00.0 
+0100
+++ marble-17.08.3/debian/patches/qt5.11.patch  2018-10-27 13:38:29.0 
+0200
@@ -0,0 +1,58 @@
+Author: Reiner Herrmann 
+Description: Fix build with Qt 5.11
+
+--- a/src/plugins/render/gpsinfo/GpsInfo.cpp
 b/src/plugins/render/gpsinfo/GpsInfo.cpp
+@@ -21,6 +21,8 @@
+ #include "ViewportParams.h"
+ #include "GeoDataAccuracy.h"
+ 
++#include 
++
+ namespace Marble
+ {
+ 
+--- a/src/plugins/render/speedometer/Speedometer.cpp
 b/src/plugins/render/speedometer/Speedometer.cpp
+@@ -19,6 +19,8 @@
+ #include "MarbleGraphicsGridLayout.h"
+ #include "ViewportParams.h"
+ 
++#include 
++
+ namespace Marble
+ {
+ 
+--- a/src/lib/marble/RenderPlugin.h
 b/src/lib/marble/RenderPlugin.h
+@@ -14,6 +14,9 @@
+ #ifndef MARBLE_RENDERPLUGIN_H
+ #define MARBLE_RENDERPLUGIN_H
+ 
++#include 
++#include 
++#include 
+ #include 
+ #include 
+ #include 
+@@ -22,10 +25,6 @@
+ #include "marble_export.h"
+ 
+ 
+-class QAction;
+-class QActionGroup;
+-class QStandardItem;
+-
+ namespace Marble
+ {
+ 
+--- a/src/plugins/render/satellites/SatellitesPlugin.cpp
 b/src/plugins/render/satellites/SatellitesPlugin.cpp
+@@ -25,6 +25,7 @@
+ 
+ #include "ui_SatellitesConfigDialog.h"
+ 
++#include 
+ #include 
+ #include 
+ 
diff -Nru marble-17.08.3/debian/patches/series 
marble-17.08.3/debian/patches/series
--- marble-17.08.3/debian/patches/series2016-06-04 10:59:56.0 
+0200
+++ marble-17.08.3/debian/patches/series2018-10-27 13:38:29.0 
+0200
@@ -1,2 +1,3 @@
 do_not_install_private_headers
 kubuntu_disable-MarbleRunnerManagerTest.diff
+qt5.11.patch

Bug#912057: getting winehq's wine-mono to work

[Alexandre Viau]

Hello,

Before further work on packaging wine-mono, I wanted to get winehq's
wine-mono build to work.

Does one of you have happen to know an example of a program that does
not work using Debian's wine but works when installing the wine-mono
.msi at:
 - https://dl.winehq.org/wine/wine-mono/ ?

I have been trying to find an example for a while now, without success.
Most installers that I have tried do not detect dotnet as already
installed and claim it is missing.

Also, I notice that C:\\windows\mono exists in prefixes by default, even
when wine-mono is not installed. That is expected?

On a side note, Wine has a feature that installs mono automatically when
it is in /usr/share/wine-development/mono. However it checks for shasums
and exact filenames so we will probably have to patch it in Debian.
(dlls/appwiz.cpl/addons.c). That said, it shouldn't prevent us from
installing it manually with ``wine64 msiexec /i winemono.msi``.

Cheers,

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#912078: libbenchmark-dev: libbenchmark_main.a referenced by benchmarkTargets-none.cmake is not shipped

[Adrian Bunk]

Package: libbenchmark-dev
Version: 1.4.1-1
Severity: serious
Control: affects -1 src:cctz

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/cctz.html

...
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/build/1st/cctz-2.2+dfsg1'
dh_auto_configure -- -DVERSION="2.2+dfsg1" -DSOVERSION="2"
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
-DVERSION=2.2\+dfsg1 -DSOVERSION=2 ..
-- The C compiler identification is GNU 8.2.0
-- The CXX compiler identification is GNU 8.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Error at /usr/lib/cmake/benchmark/benchmarkTargets.cmake:96 (message):
  The imported target "benchmark::benchmark_main" references the file

 "/usr/lib/x86_64-linux-gnu/libbenchmark_main.a"

  but this file does not exist.  Possible reasons include:

  * The file was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and contained

 "/usr/lib/cmake/benchmark/benchmarkTargets.cmake"

  but not all the files it references.

Call Stack (most recent call first):
  /usr/lib/cmake/benchmark/benchmarkConfig.cmake:1 (include)
  CMakeLists.txt:16 (find_package)


-- Configuring incomplete, errors occurred!

Bug#912067: [Pkg-openssl-devel] Bug#912067: libssl1.1: please add getmail/getmail4 to the dependencies to check

[ant]

On Sat, Oct 27, 2018 at 11:51:15PM +0200, Kurt Roeckx wrote:
... 
> That server only supports TLS1, and is using a 1024 bit DHE key.
> 
> I suggest you talk to the adminstrator to upgrade that server so
> that at least TLS 1.2 is supported.
> 
> As workaround you can change /etc/ssl/openssl.cnf. At the end of
> the file it has:
> MinProtocol = TLSv1.2
> CipherString = DEFAULT@SECLEVEL=2
> 
> It should work again if you change that to:
> MinProtocol = TLSv1
> CipherString = DEFAULT@SECLEVEL=1
> 
> It could be that you can also configure some of that in getmail,
> in which case I would recommend that you configure it there.

  ok, thanks, i'll look into those if i have to, in 
the mean time i've asked the ISP what the plans were
for TLSv1.2

  and i've passed along that other link for the
information so perhaps they can fix some of the
other issues.  i don't have high expectations given
the setup, but we'll see.

  thanks again,


  ant

Bug#906855: gnome-chemistry-utils: diff for NMU version 0.14.17-1.1

[Adrian Bunk]

Control: tags 890980 + pending
Control: tags 906855 + patch
Control: tags 906855 + pending

Dear maintainer,

I've prepared an NMU for gnome-chemistry-utils (versioned as 0.14.17-1.1) and
uploaded it to DELAYED/15. Please feel free to tell me if I
should cancel it.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

diff -Nru gnome-chemistry-utils-0.14.17/debian/changelog gnome-chemistry-utils-0.14.17/debian/changelog
--- gnome-chemistry-utils-0.14.17/debian/changelog	2018-01-14 01:50:37.0 +0200
+++ gnome-chemistry-utils-0.14.17/debian/changelog	2018-10-28 01:35:58.0 +0300
@@ -1,3 +1,11 @@
+gnome-chemistry-utils (0.14.17-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Add upstream fix for FTBFS with gnumeric >= 1.12.42.
+  * Drop the obsolete gcu-plugin. (Closes: #906855, #890980)
+
+ -- Adrian Bunk   Sun, 28 Oct 2018 01:35:58 +0300
+
 gnome-chemistry-utils (0.14.17-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru gnome-chemistry-utils-0.14.17/debian/control gnome-chemistry-utils-0.14.17/debian/control
--- gnome-chemistry-utils-0.14.17/debian/control	2018-01-14 01:50:31.0 +0200
+++ gnome-chemistry-utils-0.14.17/debian/control	2018-10-28 01:35:58.0 +0300
@@ -27,7 +27,6 @@
libtool (>= 2.2.6),
libx11-dev (>= 1.0.0),
libxml2-dev (>= 2.4.16),
-   npapi-sdk-dev,
shared-mime-info (>= 0.12),
xsltproc,
zlib1g-dev | libz-dev
@@ -69,20 +68,6 @@
   * a periodic table of the elements (GChemTable)
   * a spectra viewer (GSpectrum)
 
-Package: gcu-plugin
-Architecture: any
-Depends: libgcu0v5 (= ${binary:Version}),
- ${misc:Depends},
- ${shlibs:Depends},
- ${vendor:Browser}
-Description: GNOME chemistry utils (browser plugin)
- The GNOME Chemistry Utils provide C++ classes and Gtk+-2 widgets
- related to chemistry. They will be used in future versions of both
- gcrystal and gchempaint.
- .
- This package provides a browser plugin for Gecko-based browsers.
- It does not (yet) work with WebKit-based browsers.
-
 Package: gcrystal
 Architecture: any
 Depends: chemical-mime-data,
diff -Nru gnome-chemistry-utils-0.14.17/debian/gcu-plugin.install gnome-chemistry-utils-0.14.17/debian/gcu-plugin.install
--- gnome-chemistry-utils-0.14.17/debian/gcu-plugin.install	2016-10-03 13:58:51.0 +0300
+++ gnome-chemistry-utils-0.14.17/debian/gcu-plugin.install	1970-01-01 02:00:00.0 +0200
@@ -1,2 +0,0 @@
-usr/lib/*/gchemutils/chem-viewer
-usr/lib/*/mozilla/plugins/*.so
diff -Nru gnome-chemistry-utils-0.14.17/debian/patches/gnumeric-ftbfs.patch gnome-chemistry-utils-0.14.17/debian/patches/gnumeric-ftbfs.patch
--- gnome-chemistry-utils-0.14.17/debian/patches/gnumeric-ftbfs.patch	1970-01-01 02:00:00.0 +0200
+++ gnome-chemistry-utils-0.14.17/debian/patches/gnumeric-ftbfs.patch	2018-10-28 01:35:58.0 +0300
@@ -0,0 +1,47 @@
+Index: gchemutils/configure.ac
+===
+--- gchemutils/configure.ac	(revision 2072)
 gchemutils/configure.ac	(revision 2073)
+@@ -352,7 +352,7 @@
+   libspreadsheet=libspreadsheet-1.12
+ fi
+ 
+-PKG_CHECK_MODULES(gnumeric, [$libspreadsheet >= 1.11.6], [build_gnumeric_plugin=yes],
++PKG_CHECK_MODULES(gnumeric, [$libspreadsheet >= 1.12.42], [build_gnumeric_plugin=yes],
+ 		[build_gnumeric_plugin=no])
+ dnl --without is not handled
+ 
+Index: gchemutils/gnumeric/functions.cc
+===
+--- gchemutils/gnumeric/functions.cc	(revision 2072)
 gchemutils/gnumeric/functions.cc	(revision 2073)
+@@ -195,23 +195,23 @@
+ const GnmFuncDescriptor Chemistry_functions[] = {
+ 
+ { N_("molarmass"),   "s",
+-			help_molarmass, gnumeric_molarmass, NULL, NULL, NULL,
++			help_molarmass, gnumeric_molarmass, NULL,
+ 			GNM_FUNC_SIMPLE, GNM_FUNC_IMPL_STATUS_COMPLETE, GNM_FUNC_TEST_STATUS_NO_TESTSUITE},
+ { N_("monoisotopicmass"),   "s",
+-			help_monoisotopicmass, gnumeric_monoisotopicmass, NULL, NULL, NULL,
++			help_monoisotopicmass, gnumeric_monoisotopicmass, NULL,
+ 			GNM_FUNC_SIMPLE, GNM_FUNC_IMPL_STATUS_COMPLETE, GNM_FUNC_TEST_STATUS_NO_TESTSUITE},
+ { N_("chemcomposition"),   "ss",
+-			help_chemcomposition, gnumeric_chemcomposition, NULL, NULL, NULL,
++			help_chemcomposition, gnumeric_chemcomposition, NULL,
+ 			GNM_FUNC_SIMPLE, GNM_FUNC_IMPL_STATUS_COMPLETE, GNM_FUNC_TEST_STATUS_NO_TESTSUITE},
+ { N_("elementnumber"),   "s",
+-			help_elementnumber, gnumeric_elementnumber, NULL, NULL, NULL,
++			help_elementnumber, gnumeric_elementnumber, NULL,
+ 			GNM_FUNC_SIMPLE, GNM_FUNC_IMPL_STATUS_COMPLETE, GNM_FUNC_TEST_STATUS_NO_TESTSUITE},
+ 

Bug#909266: git-buildpackage: support %(version)s substitution in tarball-dir; preexport hooks

[Luca Boccassi]

On Sat, 29 Sep 2018 10:48:49 +0200 Guido =?iso-8859-1?Q?G=FCnther?=  wrote:
> Hi,
> On Fri, Sep 21, 2018 at 03:07:19PM +0200, Andreas Beckmann wrote:
> > On 2018-09-21 13:44, Guido Günther wrote:
> > >> In 'features' I've implemented two things:
> > >> * %(version)s substitution for tarball-dir
> > >> * preexport hooks that run before the tarballs get selected from
the
> > >>   tarball-dir (the hook can so some magic to bring the tarballs
into
> > >>   existence)
> > >> These are at least proof-of-concept implementations, they may
lack
> > >> proper documentation etc.
> > 
> > > The preexport and version substitution stuff looks good as well
and I'm
> > > happy to pull it in if it gets tests and doc updates (as you
> > > suggested).
> > 
> > I can write documentation if you point me to the correct files ...
> 
> Docs:
> 
> docs/manpages/gbp-buildpackage.xml
> 
> If you want to add more details see
> 
> docs/chapters/building.xml
> 
> Docs can be built with
> 
>  make -C docs
> 
> if you have gbp's build-deps installed.
> 
> > but I'm not sure how to write proper tests for these things.
> 
> For the preexport hook just extend
> 
> https://git.sigxcpu.org/cgit/git-buildpackage/tree/tests/componen
t/deb/test_buildpackage.py#n53

Hi,

I've sent a PR with the preexport implementation (for RPM too), test
and documentation:

https://github.com/agx/git-buildpackage/pull/62

-- 
Kind regards,
Luca Boccassi

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

Bug#811377: closed by Dmitry Bogatov (Bug#811377: fixed in sysvinit 2.88dsf-60)

[Ian Jackson]

Axel Beckert writes ("Re: Bug#811377: closed by Dmitry Bogatov 
 (Bug#811377: fixed in sysvinit 2.88dsf-60)"):
> Yes, by default all DDs, but only DDs can push to a repo under
> /debian/. But in comparison to Alioth, it's easy to add write access
> for single guest accounts to a single repo.
> 
> If Ian and Benda don't oppose, I'd give Dmitry write access to
> /debian/sysvinit/.

Please do.

I dont have time right now but can you please introduce Dmitry for me
on debian-init-diversity ?  AIUI he's subscribed to the list.

It might be worth mentioning that he did an upload to experimental
intending to adopt the package, unaware of our efforts (in part
because we failed to write to this RFA bug about them), but that we
are welcoming him, or some such.

Ian.

-- 
Ian JacksonThese 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#586709: closed by Thomas Goirand

[Ian Jackson]

Jesse Smith writes ("Bug#586709: closed by Thomas Goirand"):
> That's just the thing, it is not a bug in this package. The bug exists
> in the init scripts, not in the sysvinit package.

On my stretch system here /etc/init.d/halt is in the `initscripts'
package which comes from the `sysvinit' source package.  So I think
this is a bug in the sysvinit source package, in Debian, at least.

That it's a bug in just that one package is good because if halt
sometimes does its work by indirecting via init(8) and
/etc/init.d/halt, then it is more convenient to improve the
communication if both things are in the same package.

/etc/init.d/halt is a conffile so if we extend the protocol by which
it receives its instructions we also need to think about backward
compatibility in some sense.

Ian.

Bug#811377: closed by Dmitry Bogatov (Bug#811377: fixed in sysvinit 2.88dsf-60)

[Axel Beckert]

Hi,

Dmitry Bogatov wrote:
> > Then you should probably use the common (debian group) repository...
> 
> Somewhy GitLab does not allow me to push into debian/sysvinit, so I
> pushed to my branch.

>From that and from my past contact with Dmitry (sponsoring uploads,
etc.), I assumed he's (still) a DM.

Axel Beckert wrote:
> If Ian and Benda don't oppose, I'd give Dmitry write access to
> /debian/sysvinit/.

Hence I offered to add him as additional non-DD "member" of the
sysvinit repo.

Ian Jackson wrote:
> Please do.

No more needed. Dmitry is a DD since one week ago:
https://nm.debian.org/process/448

Actually I even replied to his new @debian.org address without
noticing. :-)

Dmitry: Welcome! I'm really happy to see you on board!

Dmitry: Please try again to push to
https://salsa.debian.org/debian/sysvinit/ — your account is listed as
"Given access 2 days ago". So I assume the user database wasn't synced
as quickly as you gained traction. :-)

> I dont have time right now but can you please introduce Dmitry for me
> on debian-init-diversity ?

I'm sorry, but I'm not sure what you ask me for. I'm not subscribed to
that list, I'm just subscribed to (and mostly lurking on)
pkg-sysvinit-devel and subscribed to #811377.

> It might be worth mentioning that he did an upload to experimental
> intending to adopt the package, unaware of our efforts (in part
> because we failed to write to this RFA bug about them),

At least from lurking on pkg-sysvinit-devel I wasn't aware of any work
done on the package either with the exception of the stated ITA quite
some time (a year?) ago. The only thing I saw was the scaring amount
NMUs.

So hearing that not only Dmitry is active now but that Ian and Benda
also have something in the pipeline is great!

> but that we are welcoming him, or some such.

Great! Looking forward to the results of that grown team! And thanks
for all your efforts to keep sysvinit usable in Debian.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#912076: kodiplatform FTBFS with debhelper 11.4

[Adrian Bunk]

Source: kodiplatform
Version: 17.1.0-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/kodiplatform.html

...
   dh_auto_install
cd obj-x86_64-linux-gnu && make -j1 install 
DESTDIR=/build/1st/kodiplatform-17.1.0/debian/tmp AM_UPDATE_INFO_DIR=no
make[1]: Entering directory 
'/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu'
/usr/bin/cmake -H/build/1st/kodiplatform-17.1.0 
-B/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu --check-build-system 
CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start 
/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu/CMakeFiles 
/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu/CMakeFiles/progress.marks
make -f CMakeFiles/Makefile2 all
make[2]: Entering directory 
'/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu'
make -f CMakeFiles/kodiplatform.dir/build.make 
CMakeFiles/kodiplatform.dir/depend
make[3]: Entering directory 
'/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu'
cd /build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu && /usr/bin/cmake -E 
cmake_depends "Unix Makefiles" /build/1st/kodiplatform-17.1.0 
/build/1st/kodiplatform-17.1.0 
/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu 
/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu 
/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu/CMakeFiles/kodiplatform.dir/DependInfo.cmake
 --color=
make[3]: Leaving directory '/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu'
make -f CMakeFiles/kodiplatform.dir/build.make CMakeFiles/kodiplatform.dir/build
make[3]: Entering directory 
'/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu'
make[3]: Nothing to be done for 'CMakeFiles/kodiplatform.dir/build'.
make[3]: Leaving directory '/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu'
[100%] Built target kodiplatform
make[2]: Leaving directory '/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu'
/usr/bin/cmake -E cmake_progress_start 
/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu/CMakeFiles 0
make -f CMakeFiles/Makefile2 preinstall
make[2]: Entering directory 
'/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu'
make[2]: Nothing to be done for 'preinstall'.
make[2]: Leaving directory '/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu'
Install the project...
/usr/bin/cmake -P cmake_install.cmake
-- Install configuration: "None"
-- Installing: 
/build/1st/kodiplatform-17.1.0/debian/tmp/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu/libkodiplatform.so.16.0.0
-- Installing: 
/build/1st/kodiplatform-17.1.0/debian/tmp/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu/libkodiplatform.so.16
-- Installing: 
/build/1st/kodiplatform-17.1.0/debian/tmp/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu/libkodiplatform.so
-- Installing: 
/build/1st/kodiplatform-17.1.0/debian/tmp/usr/include/kodi/util/XMLUtils.h
-- Installing: 
/build/1st/kodiplatform-17.1.0/debian/tmp/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu/pkgconfig/kodiplatform.pc
-- Installing: 
/build/1st/kodiplatform-17.1.0/debian/tmp/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu/kodiplatform/kodiplatform-config.cmake
make[1]: Leaving directory '/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu'
   dh_install
dh_install: Cannot find (any matches for) "usr/lib/*/*.so" (tried in ., 
debian/tmp)

dh_install: libkodiplatform-dev missing files: usr/lib/*/*.so
dh_install: Cannot find (any matches for) "usr/lib/*/pkgconfig/*.pc" (tried in 
., debian/tmp)

dh_install: libkodiplatform-dev missing files: usr/lib/*/pkgconfig/*.pc
dh_install: Cannot find (any matches for) "usr/lib/*/kodiplatform/*" (tried in 
., debian/tmp)

dh_install: libkodiplatform-dev missing files: usr/lib/*/kodiplatform/*
dh_install: Cannot find (any matches for) "usr/lib/*/*.so.*" (tried in ., 
debian/tmp)

dh_install: libkodiplatform16 missing files: usr/lib/*/*.so.*
dh_install: missing files, aborting
make: *** [debian/rules:16: binary] Error 25

Bug#912077: libbiod FTBFS on i386: Error: cannot implicitly convert expression

[Adrian Bunk]

Source: libbiod
Version: 0.2.1-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=libbiod=i386=0.2.1-1=1539070612=0

...
[77/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g 
-release -wi -relocation-model=pic   -of='biod@sha/bio2_bgzf.d.o' -c 
../bio2/bgzf.d
FAILED: biod@sha/bio2_bgzf.d.o 
ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g -release -wi 
-relocation-model=pic   -of='biod@sha/bio2_bgzf.d.o' -c ../bio2/bgzf.d
../bio2/bgzf.d(214): Error: cannot implicitly convert expression 
`tuple(Nullable(0LU, true), compressed_buf, 0LU, crc32)` of type 
`Tuple!(Nullable!ulong, ubyte[], ulong, immutable(uint))` to 
`Tuple!(Nullable!ulong, ubyte[], uint, immutable(uint))`
...

Bug#910128: bash-completion: diff for NMU version 1:2.1-4.4

[Emmanouil Kampitakis]

Control: tags 910128 + pending
Control: user debian-rele...@lists.debian.org
Control: usertags -1 + bsp-2018-10-de-karlsruhe

Dear maintainer,

I've prepared an NMU for bash-completion (versioned as 1:2.1-4.4) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards,
 Emmanouil

diff -Nru bash-completion-2.1/debian/changelog
bash-completion-2.1/debian/changelog ---
bash-completion-2.1/debian/changelog2016-04-12
14:06:38.0 + +++
bash-completion-2.1/debian/changelog2018-10-27
21:53:12.0 + @@ -1,3 +1,10 @@ +bash-completion (1:2.1-4.4)
unstable; urgency=medium +
+  * Non-maintainer upload.
+  * Use install-data-hook, not install-data-local (Closes: #910128) 
+
+ -- Emmanouil Kampitakis   Sat, 27 Oct 2018
21:53:12 + +
 bash-completion (1:2.1-4.3) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru
bash-completion-2.1/debian/patches/99-use-install-data-hook.patch
bash-completion-2.1/debian/patches/99-use-install-data-hook.patch ---
bash-completion-2.1/debian/patches/99-use-install-data-hook.patch
1970-01-01 00:00:00.0 + +++
bash-completion-2.1/debian/patches/99-use-install-data-hook.patch
2018-10-27 21:48:09.0 + @@ -0,0 +1,28 @@ +From:
=?UTF-8?q?Ville=20Skytt=C3=A4?=  +Date: Fri, 25
May 2018 17:38:59 +0200 +Subject: [PATCH] completions/Makefile.am: Use
install-data-hook, not
+ install-data-local
+Bug-Debian: https://bugs.debian.org/910128
+Forwarded: https://github.com/scop/bash-completion/issues/212
+Origin:
https://github.com/scop/bash-completion/commit/ee6b37ad7ff5b309cbb9b886a871252abd9398fa
+ +-hook is run after the main rule, while -local might end up before.
+https://www.gnu.org/software/automake/manual/html_node/Extending.html#index-hook-targets
+
+Closes #212
+---
+ completions/Makefile.am | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+Index: bash-completion-2.1/completions/Makefile.am
+===
+--- bash-completion-2.1.orig/completions/Makefile.am
 bash-completion-2.1/completions/Makefile.am
+@@ -869,5 +869,5 @@ symlinks: $(targetdir) $(DATA)
+ all-local: targetdir = .
+ all-local: symlinks
+ 
+-install-data-local: targetdir = $(DESTDIR)$(bashcompdir)
+-install-data-local: symlinks
++install-data-hook: targetdir = $(DESTDIR)$(bashcompdir)
++install-data-hook: symlinks
diff -Nru bash-completion-2.1/debian/patches/series
bash-completion-2.1/debian/patches/series ---
bash-completion-2.1/debian/patches/series   2014-03-22
20:57:44.0 + +++
bash-completion-2.1/debian/patches/series   2018-10-27
20:38:29.0 + @@ -11,3 +11,4 @@ 10-ifconfig_locale.patch
11-dont_return_from_sourced_script.patch 12-look_for_pod.patch
+99-use-install-data-hook.patch


pgpZn6LJQ49zl.pgp
Description: OpenPGP digital signature

Bug#912075: ayatana-indicator-power FTBFS with googletest 1.8.1-1

[Adrian Bunk]

Source: ayatana-indicator-power
Version: 2.0.93-3
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ayatana-indicator-power.html

...
[ 99%] Linking CXX executable test-notify
cd /build/1st/ayatana-indicator-power-2.0.93/obj-x86_64-linux-gnu/tests && 
/usr/bin/cmake -E cmake_link_script CMakeFiles/test-notify.dir/link.txt 
--verbose=1
/usr/bin/c++  -g -O2 
-ffile-prefix-map=/build/1st/ayatana-indicator-power-2.0.93=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=c++11  -Wall -Wextra -Wpedantic -Wformat=2 
-Wno-missing-field-initializers -Wno-weak-vtables -Wno-global-constructors  
-Wl,-z,relro -Wl,-z,now -rdynamic CMakeFiles/test-notify.dir/test-notify.cc.o  
-o test-notify ../src/libayatanaindicatorpowerservice.a -ldbustest -lglib-2.0 
-lgio-2.0 -lnotify -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 
-lgio-2.0 -lnotify -lgdk_pixbuf-2.0 -lgobject-2.0 gmock/gtest/libgtest.a 
-lpthread gmock/libgmock.a gmock/libgmock_main.a 
/usr/bin/ld: gmock/libgmock_main.a(gmock_main.cc.o): in function `main':
/usr/src/googletest/googlemock/src/gmock_main.cc:52: undefined reference to 
`testing::InitGoogleMock(int*, char**)'
collect2: error: ld returned 1 exit status
make[3]: *** [tests/CMakeFiles/test-notify.dir/build.make:91: 
tests/test-notify] Error 1

Bug#188731: debian-policy: "strip --strip-unneeded" is insufficient

[Russ Allbery]

Sean Whitton  writes:

> Thank you for following up.

> Here is a minimal patch, for which I am seeking seconds.  I didn't
> include a recommendation to use dh_strip because we generally keep such
> recommendations in footnotes rather than the text of Policy, and we are
> trying to reduce the number of footnotes -- but I don't mind adding it
> if others think it would be a good idea (and it wouldn't need
> seconding).

Looks good to me.  Seconded.

On an entirely unrelated note (and probably a larger project than anyone
will be able to tackle any time soon), I think it would be very helpful if
we had some way of annotating what parts of Policy are just handled for
you if you use debhelper in the normal way (perhaps with references to the
tools involved).  Maybe with background shading or an icon or something?
I think Policy needs to state all of the rules, including the ones
implemented by other tools, but at the same time nearly everyone doing
Debian packaging is using debhelper (either directly or indirectly), so
it's a bit of a disservice to people to ask them to wade through a bunch
of specifications for stuff that normally they don't and shouldn't think
about.

-- 
Russ Allbery (r...@debian.org)   

Bug#912067: [Pkg-openssl-devel] Bug#912067: Bug#912067: libssl1.1: please add getmail/getmail4 to the dependencies to check

[Sebastian Andrzej Siewior]

On 2018-10-27 17:18:22 [-0400], ant wrote:
>   here is the message:
> 
> =
> getmail version 5.6
> Copyright (C) 1998-2012 Charles Cazabon.  Licensed under the GNU GPL version 
> 2.
> SimplePOP3SSLRetriever:a...@anthive.com@mail.anthive.com:995:
> rc-03ant: socket error ([SSL: UNSUPPORTED_PROTOCOL] unsupported protocol 
> (_ssl.c:726))
>   0 messages (0 bytes) retrieved, 0 skipped
> =

from https://www.htbridge.com/ssl/?id=0v7rEeNT
|The server's Diffie-Hellman parameter is too small.
|The server supports protocols that have known weaknesses and are considered 
unsafe.
|The server supports cipher suites that are not approved by PCI DSS 
requirements, NIST guidelines and HIPAA guidance.
|The TLS engine does not support newer version than TLSv1.0 and seems outdated.
|The server's certificate is untrusted.
|The server has TLS 1.0 enabled. Since the 30th of June 2018 it is 
non-compliant with PCI DSS 3.2.1.
|The server is vulnerable to POODLE over SSL.
…
|List of all SSL/TLS protocols supported by the server:
|
|SSLv3
|TLSv1.0
|DIFFIE-HELLMAN PARAMETER WEAK
|The Diffie-Hellman parameter's size is only 1024 bits . A longer one must be 
generated to prevent Logjam vulnerability.Non-compliant with PCI DSS 
requirements
|POODLE OVER SSL 
|The server is vulnerable to POODLE over SSL. SSLv3 should be 
disabled.Non-compliant with PCI DSS requirements

>   thanks for your response,
> 
> 
>   ant

Sebastian

Bug#912067: [Pkg-openssl-devel] Bug#912067: libssl1.1: please add getmail/getmail4 to the dependencies to check

[Kurt Roeckx]

On Sat, Oct 27, 2018 at 05:18:22PM -0400, ant wrote:
> 
> =
> getmail version 5.6
> Copyright (C) 1998-2012 Charles Cazabon.  Licensed under the GNU GPL version 
> 2.
> SimplePOP3SSLRetriever:a...@anthive.com@mail.anthive.com:995:
> rc-03ant: socket error ([SSL: UNSUPPORTED_PROTOCOL] unsupported protocol 
> (_ssl.c:726))
>   0 messages (0 bytes) retrieved, 0 skipped
> =

That server only supports TLS1, and is using a 1024 bit DHE key.

I suggest you talk to the adminstrator to upgrade that server so
that at least TLS 1.2 is supported.

As workaround you can change /etc/ssl/openssl.cnf. At the end of
the file it has:
MinProtocol = TLSv1.2
CipherString = DEFAULT@SECLEVEL=2

It should work again if you change that to:
MinProtocol = TLSv1
CipherString = DEFAULT@SECLEVEL=1

It could be that you can also configure some of that in getmail,
in which case I would recommend that you configure it there.


Kurt

Bug#912074: libboost-stacktrace1.67-dev: header boost/stacktrace.hpp not included in libboost-stacktrace1.67-dev

[Martin Quinson]

Package: libboost-stacktrace1.67-dev
Version: 1.67.0-7
Severity: grave
Justification: renders package unusable

Dear maintainers,

I'm really pleased that this new stacktrace library made its way into boost and
into debian, but it seems that something went wrong when packaging it because
the header files seem to be missing.

Here is the content of my version:
$ dpkg -L libboost-stacktrace1.67-dev
/.
/usr
/usr/lib
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libboost_stacktrace_addr2line.a
/usr/lib/x86_64-linux-gnu/libboost_stacktrace_backtrace.a
/usr/lib/x86_64-linux-gnu/libboost_stacktrace_basic.a
/usr/lib/x86_64-linux-gnu/libboost_stacktrace_noop.a
/usr/share
/usr/share/doc
/usr/share/doc/libboost-stacktrace1.67-dev
/usr/share/doc/libboost-stacktrace1.67-dev/changelog.Debian.gz
/usr/share/doc/libboost-stacktrace1.67-dev/copyright
/usr/lib/x86_64-linux-gnu/libboost_stacktrace_addr2line.so
/usr/lib/x86_64-linux-gnu/libboost_stacktrace_backtrace.so
/usr/lib/x86_64-linux-gnu/libboost_stacktrace_basic.so
/usr/lib/x86_64-linux-gnu/libboost_stacktrace_noop.so

As you can see, there is no headerfile while upstream seem to distribute some:
https://github.com/boostorg/stacktrace

Or maybe I missed something obvious?

Many thanks for your work,
Mt



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

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

Versions of packages libboost-stacktrace1.67-dev depends on:
ii  libboost-stacktrace1.67.0  1.67.0-7
ii  libboost1.67-dev   1.67.0-7

libboost-stacktrace1.67-dev recommends no packages.

libboost-stacktrace1.67-dev suggests no packages.

-- no debconf information

-- 
The great thing about TCP jokes is that you always get them.


signature.asc
Description: PGP signature

Bug#912073: No initramfs generated if new kernel package installed by upgrade

[Ben Hutchings]

Package: pkgsel
Version: 0.60
Severity: serious

While testing a fix for #908711, I found that pkgsel diverts
update-initramfs during the upgrade and installation process
and runs it once at the end.

By default, "update-initramfs -u" updates the new initramfs for the
newest kernel version that update-initramfs was previously run for.
If a new kernel package was installed due to an ABI bump, no new
initramfs will be generated.  This causes the system to fail to
boot.

Ben.

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

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 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

Bug#912067: [Pkg-openssl-devel] Bug#912067: libssl1.1: please add getmail/getmail4 to the dependencies to check

[ant]

On Sat, Oct 27, 2018 at 10:38:40PM +0200, Kurt Roeckx wrote:
> On Sat, Oct 27, 2018 at 04:30:13PM -0400, ant wrote:
> > Package: libssl1.1
> > Version: 1.1.0h-4
> > Severity: wishlist
> > 
> > Dear Maintainer,
> > 
> >   hi,
> > 
> >   last year an upgrade of libssl1.1 ended up breaking
> >   getmail/getmail4.  the maintainer suggested a blocking
> >   bug or something informational, but i failed to file one.
> > 
> >   this year same situation again.  upgrade breaks getmail/
> >   getmail4 upon upgrade to libssl1.1.1-1 - reverting the
> >   upgrade restores the system so it can be used again.
> > 
> >   i'll put this as wishlist bug for those who might run into
> >   the same thing,


hello, thank you for your quick reply,  :)

 
> Can you please clarify what stopped working, what error did you
> get?

  see below...

 
> Are you asking to restart getmail on upgrade? Does that actually
> fix your problem?

  no, i usually restart my machine from scratch after upgrades
just to make sure there aren't any odd things hanging around.
with SSD it's quick enough.

 
> The new 1.1.1-1 version might break some things because for
> various reasons. So if you get an error, please report it.

  here is the message:

=
getmail version 5.6
Copyright (C) 1998-2012 Charles Cazabon.  Licensed under the GNU GPL version 2.
SimplePOP3SSLRetriever:a...@anthive.com@mail.anthive.com:995:
rc-03ant: socket error ([SSL: UNSUPPORTED_PROTOCOL] unsupported protocol 
(_ssl.c:726))
  0 messages (0 bytes) retrieved, 0 skipped
=

  thanks for your response,


  ant

Bug#912072: srg: FTBFS with GCC 8

[Reiner Herrmann]

Source: srg
Version: 1.3.6-2
Severity: serious
Tags: ftbfs
User: debian-rele...@lists.debian.org
Usertags: bsp-2018-10-de-karlsruhe

Dear maintainer,

srg fails to build with GCC 8:

g++ -DHAVE_CONFIG_H -I. -I..  -I../include -I../libconfig 
-DDATADIR=\"/usr/share\" -DSYSCONFDIR=\"/etc\" -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/tmp/debian/srg/tmp/srg-1.3.6=. 
-fstack-protector-strong -Wformat -Werror=format-security -MT srg-output.o -MD 
-MP -MF .deps/srg-output.Tpo -c -o srg-output.o `test -f 'output.cc' || echo 
'./'`output.cc
output.cc: In function ‘void init_file(const char*)’:
output.cc:101:26: error: invalid conversion from ‘char’ to ‘char*’ 
[-fpermissive]
   char *buf[4096] = {'\0'};
  ^
output.cc: In function ‘void html_header(FILE*, const char*)’:
output.cc:121:13: warning: ISO C++ forbids converting a string constant to 
‘char*’ [-Wwrite-strings]
  char *base="";
 ^~
output.cc: In function ‘void html_footer(FILE*, const char*)’:
output.cc:176:13: warning: ISO C++ forbids converting a string constant to 
‘char*’ [-Wwrite-strings]
  char *base="";
 ^~

A complete build log is also available on 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/srg.html

Kind regards,
  Reiner


signature.asc
Description: PGP signature

Bug#912071: gcl: FTBFS on hppa - segmentation fault assembling gbc.s

[John David Anglin]

Source: gcl
Version: 2.6.12
Severity: normal

Dear Maintainer,

Build fails here:
gcc -c -g -fdebug-prefix-map=/<>=. -Wformat 
-Werror=format-security -fsigned-char -pipe -fno-builtin-malloc 
-fno-builtin-free -fno-PIE -fno-pie -fno-PIC -fno-pic -Wall -Wno-empty-body 
-Wno-unused-but-set-variable -Wno-misleading-indentation -mlong-calls -fPIC  
-Wdate-time -D_FORTIFY_SOURCE=2 -O2 -I/<>/o -I../h -I../gcl-tk 
gbc.c  
{standard input}: Assembler messages:
{standard input}: Internal error (Segmentation fault).
Please report this bug.

Mostly the error is due to a bug in gbc.c but recent changes to gas likely
cause the segmentation fault.  See following report for details:
https://sourceware.org/bugzilla/show_bug.cgi?id=23837

Regards,
Dave Anglin


-- System Information:
Debian Release: buster/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: hppa (parisc64)

Kernel: Linux 4.14.78+ (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C 
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#912070: xserver-xorg-input-synaptics: Tap-to-Click suddenly fails with SynPS2 after last upgrade

[Eduard Bloch]

Package: xserver-xorg-input-synaptics
Version: 1.9.1-1
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?

I dist-upgraded recently, now having X.org 1.20 instead of 1.19

   * What was the outcome of this action?

After reboot, single or douple tapping the touchpad does not produce any
click-like activity! I see no click events in the xev output whatsoever!

Before, it worked just fine.

   * What outcome did you expect instead?

NOT BREAKING existing functionality.

I will attach the Xorg.log from the old version. You can see clearly
that in the end there was some special setup for the IBM trackpoint, and
for the current version, that initialation part is no longer executed.

The hardware is a Thinkpad X250 (older revision).

Best regards,
Eduard.


-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Jul 24  2014 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 274 Oct 10 18:23 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 5500 
[8086:1616] (rev 09)

Xorg X server configuration file status:

-rw-r--r-- 1 root root 187 Mar  1  2018 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
---
Section "Device"
Identifier  "Intel Graphics"
Driver  "intel"
Option  "AccelMethod" "sna"
Option  "SwapbuffersWait"   "false"
Option "TearFree" "true"
EndSection

/etc/X11/xorg.conf.d does not exist.

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 4.18.0-trunk-amd64 (debian-ker...@lists.debian.org) (gcc version 
7.3.0 (Debian 7.3.0-28)) #1 SMP Debian 4.18.5-1~exp1 (2018-08-26)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 45504 Jan 12  2015 /var/log/Xorg.1.log
-rw-r--r-- 1 ed   ed   31588 Aug 14  2016 /home/ed/.local/share/xorg/Xorg.0.log
-rw-r--r-- 1 ed   ed5189 Sep 10  2017 /home/ed/.local/share/xorg/Xorg.2.log
-rw-r--r-- 1 ed   ed   52090 Sep 10  2017 /home/ed/.local/share/xorg/Xorg.1.log
-rw-r--r-- 1 root root 31601 Sep 11  2017 /var/log/Xorg.2.log
-rw-r--r-- 1 root root 24902 Oct 27 23:02 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[15.515] 
X.Org X Server 1.20.1
X Protocol Version 11, Revision 0
[15.515] Build Operating System: Linux 4.9.0-8-amd64 x86_64 Debian
[15.515] Current Operating System: Linux amerix 4.18.0-trunk-amd64 #1 SMP 
Debian 4.18.5-1~exp1 (2018-08-26) x86_64
[15.515] Kernel command line: BOOT_IMAGE=/vmlinuz-4.18.0-trunk-amd64 
root=/dev/mapper/default-root ro init=/bin/systemd i915.enable_rc6=0 
iwlwifi.power_save=Y iwlwifi.power_level=3
[15.515] Build Date: 10 October 2018  04:23:15PM
[15.515] xorg-server 2:1.20.1-5 (https://www.debian.org/support) 
[15.515] Current version of pixman: 0.34.0
[15.515]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[15.515] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[15.515] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Oct 27 23:01:10 
2018
[15.521] (==) Using config file: "/etc/X11/xorg.conf"
[15.521] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[15.535] (==) No Layout section.  Using the first Screen section.
[15.535] (==) No screen section available. Using defaults.
[15.535] (**) |-->Screen "Default Screen Section" (0)
[15.535] (**) |   |-->Monitor ""
[15.538] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[15.538] (**) |   |-->Device "Intel Graphics"
[15.538] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[15.538] (==) Automatically adding devices
[15.538] (==) Automatically enabling devices
[15.538] (==) Automatically adding GPU devices
[15.538] (==) Max clients allowed: 256, resource mask: 0x1f
[15.542] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[15.542]Entry deleted from font path.
[15.547] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[15.547] (==) ModulePath set to "/usr/lib/xorg/modules"
[15.547] 

Bug#912069: flask-wtf FTBFS: FAIL: test_i18n_enabled (tests.test_i18n.TestI18NCase)

[Adrian Bunk]

Source: flask-wtf
Version: 0.14.2-2
Severity: serious
Tags: ftbfs

Some recent change in unstable makes flask-wtf FTBFS:

https://tests.reproducible-builds.org/debian/history/flask-wtf.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/flask-wtf.html

...

==
FAIL: test_i18n_enabled (tests.test_i18n.TestI18NCase)
--
Traceback (most recent call last):
  File 
"/build/1st/flask-wtf-0.14.2/.pybuild/cpython2_2.7_flaskext.wtf/build/tests/test_i18n.py",
 line 32, in test_i18n_enabled
assert '\u8be5\u5b57\u6bb5\u662f' in to_unicode(response.data)
AssertionError

--
Ran 52 tests in 0.661s

FAILED (failures=1)
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd 
/build/1st/flask-wtf-0.14.2/.pybuild/cpython2_2.7_flaskext.wtf/build; python2.7 
-m nose -v tests
dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned 
exit code 13
make: *** [debian/rules:11: build] Error 25

Bug#881845: rustc: FTBFS on mips*: test failures

[John Paul Adrian Glaubitz]

Package: src:rustc
Followup-For: Bug #881845
User: debian-m...@lists.debian.org
Usertags: mips

Hi!

Attaching a cleaned-up patch for rustc_1.29.

Could you include it in the next upload to fix rustc on mips*?

Additionally, we will need to backport the LLVM atomics fixes for
MIPS for llvm-toolchain-6.0 [1]. I'm working on this but it's a
bit involved.

After that, we need to move the generation of doc files to the
binary-indep target such that "rustdoc" is not run on 32-Bit MIPS
targets which fails with an out-of-memory error.

Adrian

> [1] https://reviews.llvm.org/rL336328

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
Description: Various fixes for Rust on MIPS
Author: Dragan Mladjenovic 
Bug-Debian: https://bugs.debian.org/881845
Last-Update: 2018-10-24

--- rustc-1.29.0+dfsg1.orig/src/librustc_codegen_llvm/llvm_util.rs
+++ rustc-1.29.0+dfsg1/src/librustc_codegen_llvm/llvm_util.rs
@@ -66,6 +66,8 @@ unsafe fn configure_llvm(sess: )
 add("-disable-preinline");
 }
 
+   if sess.target.target.arch == "mips" || sess.target.target.arch == 
"mips64" { add("-fast-isel=0"); }
+
 for arg in _args {
 add(&(*arg));
 }
--- rustc-1.29.0+dfsg1.orig/src/test/run-pass/invalid_const_promotion.rs
+++ rustc-1.29.0+dfsg1/src/test/run-pass/invalid_const_promotion.rs
@@ -33,7 +33,8 @@ fn check_status(status: std::process::Ex
 use std::os::unix::process::ExitStatusExt;
 
 assert!(status.signal() == Some(libc::SIGILL)
-|| status.signal() == Some(libc::SIGABRT));
+|| status.signal() == Some(libc::SIGABRT)
+   || status.signal() == Some(libc::SIGTRAP));
 }
 
 #[cfg(not(unix))]
--- rustc-1.29.0+dfsg1.orig/src/test/ui/asm-out-assign-imm.rs
+++ rustc-1.29.0+dfsg1/src/test/ui/asm-out-assign-imm.rs
@@ -10,6 +10,8 @@
 
 // ignore-s390x
 // ignore-emscripten
+// ignore-mips
+// ignore-mips64
 // ignore-powerpc
 // ignore-powerpc64
 // ignore-powerpc64le
--- rustc-1.29.0+dfsg1.orig/src/test/ui/target-feature-gate.rs
+++ rustc-1.29.0+dfsg1/src/test/ui/target-feature-gate.rs
@@ -12,6 +12,8 @@
 // ignore-aarch64
 // ignore-wasm
 // ignore-emscripten
+// ignore-mips
+// ignore-mips64
 // ignore-powerpc64
 // ignore-powerpc64le
 // gate-test-sse4a_target_feature
--- rustc-1.29.0+dfsg1.orig/src/test/ui/target-feature-wrong.rs
+++ rustc-1.29.0+dfsg1/src/test/ui/target-feature-wrong.rs
@@ -13,6 +13,7 @@
 // ignore-wasm
 // ignore-emscripten
 // ignore-mips
+// ignore-mips64
 // ignore-powerpc
 // ignore-powerpc64
 // ignore-powerpc64le

Bug#904495: openjdk-10: Please update patch for m68k support

[John Paul Adrian Glaubitz]

Hi!

On 7/24/18 9:55 PM, John Paul Adrian Glaubitz wrote:
> Please use this patch to update the m68k support in the next
> upload of openjdk-10.

openjdk-10 is still shipping with the outdated patch hence openjdk-10
still FTBFS on m68k. Could you please refresh the m68k patch in the
openjdk-10 package with the patch from this bug report?

Thanks,
Adrian

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

Bug#901416: Suggests: apparmor-profiles-extra is insufficient

[Reiner Herrmann]

Hi intrigeri,

thank you for your surf patches!

I'm a bit hesitant to introduce a new binary package for the AppArmor
profile.
What do you think about dropping/commenting the gstreamer part of the
profile, so there is no longer a dependency to apparmor-profiles-extra.
This would break some sites with multimedia content when AppArmor is
enabled, but could also be re-enabled by the user if required.
Or as an alternative (that I would prefer) to merge the content from
abstractions/gstreamer into the surf profile?

Regards,
  Reiner


signature.asc
Description: PGP signature

Bug#911220: jhead 3.00-4+deb9u1 flagged for acceptance

[Adam D Barratt]

Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian stretch.

Thanks for your contribution!

Upload details
==

Package: jhead
Version: 3.00-4+deb9u1

Explanation: fix security issues [CVE-2018-17088 CVE-2018-16554]

Bug#911494: systraq 20160803-1+deb9u1 flagged for acceptance

[Adam D Barratt]

Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian stretch.

Thanks for your contribution!

Upload details
==

Package: systraq
Version: 20160803-1+deb9u1

Explanation: invert logic in order to exit successfully in case /e/s/Makefile 
is missing

Bug#910371: lxcfs 2.0.7-1+deb9u1 flagged for acceptance

[Adam D Barratt]

Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian stretch.

Thanks for your contribution!

Upload details
==

Package: lxcfs
Version: 2.0.7-1+deb9u1

Explanation: revert uptime virtualiziation, fixing process start times

Bug#911992: spice-gtk 0.33-3.3+deb9u1 flagged for acceptance

[Adam D Barratt]

Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian stretch.

Thanks for your contribution!

Upload details
==

Package: spice-gtk
Version: 0.33-3.3+deb9u1

Explanation: fix flexible array buffer overflow [CVE-2018-10873]

Bug#910629: network-manager-applet 1.4.4-1+deb9u1 flagged for acceptance

[Adam D Barratt]

Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian stretch.

Thanks for your contribution!

Upload details
==

Package: network-manager-applet
Version: 1.4.4-1+deb9u1

Explanation: libnma/pygobject: libnma/NMA must use libnm/NM instead of legacy 
libraries

Bug#911244: publicsuffix 20181003.1334-0+deb9u1 flagged for acceptance

[Adam D Barratt]

Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian stretch.

Thanks for your contribution!

Upload details
==

Package: publicsuffix
Version: 20181003.1334-0+deb9u1

Explanation: update included data

Bug#910445: gnutls28 3.5.8-5+deb9u4 flagged for acceptance

[Adam D Barratt]

Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian stretch.

Thanks for your contribution!

Upload details
==

Package: gnutls28
Version: 3.5.8-5+deb9u4

Explanation: fix security issues [CVE-2018-10844 CVE-2018-10845]

Bug#910628: network-manager 1.6.2-3+deb9u1 flagged for acceptance

[Adam D Barratt]

Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian stretch.

Thanks for your contribution!

Upload details
==

Package: network-manager
Version: 1.6.2-3+deb9u1

Explanation: libnm: Fix accessing enabled and metered properties

Bug#909007: stretch-pu: package firetray/0.6.1+dfsg-1

[Adam Borowski]

On Sat, Oct 27, 2018 at 04:21:09PM +0100, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Mon, 2018-09-17 at 13:09 +0200, Adam Borowski wrote:
> > I'm afraid that the security update of thunderbird from 52 to 60
> > broke firetray, which, despite being a mere "extension", includes
> > some quite essential functionality for thunderbird (described below).
> 
> Apologies for the delay in getting back to you regarding this. The
> general response so far from the Security Team has been that they see
> these as stable issues, so let's go with fixing it via p-u. Please use
> the version suggested later in the thread, if the package is
> essentially a backport from unstable.

In the meantime, another upload of thunderbird broken the version check,
which was "up to 60.0".  Turns out 60.2.1 does not match that anymore. :/
Details in #910973; no one from the maintainer team responded thus I
scheduled a NMU, it'll go in tomorrow evening.

Unlike the first patch which required quite large code changes, this is just
a version bump.  I guess you have no problems with that, but stretch-pu bugs
are version-marked so we'd still need to coordinate on it.


And wrt the future: some people went angry about Thunderbird breaking
extensions again and again, and made https://github.com/gyunaev/birdtray
Obviously, it's not an option for Stretch, but there's hope we'll avoid this
unpleasantness for Buster.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢰⠒⠀⣿⡁ 10 people enter a bar: 1 who understands binary,
⢿⡄⠘⠷⠚⠋⠀ 1 who doesn't, D who prefer to write it as hex,
⠈⠳⣄ and 1 who narrowly avoided an off-by-one error.

Bug#909007: stretch-pu: package firetray/0.6.1+dfsg-1

[Adam D. Barratt]

On Sat, 2018-10-27 at 22:44 +0200, Adam Borowski wrote:
> On Sat, Oct 27, 2018 at 04:21:09PM +0100, Adam D. Barratt wrote:
> > Control: tags -1 + confirmed
> > 
> > On Mon, 2018-09-17 at 13:09 +0200, Adam Borowski wrote:
> > > I'm afraid that the security update of thunderbird from 52 to 60
> > > broke firetray, which, despite being a mere "extension", includes
> > > some quite essential functionality for thunderbird (described
> > > below).
> > 
> > Apologies for the delay in getting back to you regarding this. The
> > general response so far from the Security Team has been that they
> > see
> > these as stable issues, so let's go with fixing it via p-u. Please
> > use
> > the version suggested later in the thread, if the package is
> > essentially a backport from unstable.
> 
> In the meantime, another upload of thunderbird broken the version
> check,
> which was "up to 60.0".  Turns out 60.2.1 does not match that
> anymore. :/
> Details in #910973; no one from the maintainer team responded thus I
> scheduled a NMU, it'll go in tomorrow evening.
> 
> Unlike the first patch which required quite large code changes, this
> is just a version bump.  I guess you have no problems with that, but
> stretch-pu bugs are version-marked so we'd still need to coordinate
> on it.

It sounds fine, as long as it's uploaded in time.

> And wrt the future: some people went angry about Thunderbird breaking
> extensions again and again, and made https://github.com/gyunaev/birdt
> ray
> Obviously, it's not an option for Stretch, but there's hope we'll
> avoid this
> unpleasantness for Buster.

Fingers crossed...

Regards,

Adam

Bug#903377: convert-from-gbp: `diverged', --overwrite if no previous dgit push

[Sean Whitton]

control: tag -1 +patch

Hello,

On Mon 09 Jul 2018 at 10:48AM +0100, Ian Jackson wrote:

> My fix for #903132

(which is really nice, thank you)

> has arguably made things worse for a different use case: if the user
> goes straight from (i) gbp without dgit, to (ii) gdr with dgit, then
> the new pseudomerge generation cannot work.  So there will be a new
> message about that.

How offputting will this message be?  Sorry, I don't have a convenient
test case, since I always upload with dgit ;)

I don't think we need to document the expected message explicitly if
there is no action the user needs to take other than using --overwrite
and possibly -fdiverged.

> But also, there will be a new `diverged' snag at the time of git
> debrebase convert-from-gbp, if the user has ever done dgit fetch sid.
> In that case the user of gdr 5.8 will have to specify -fdiverged to
> convert-from-gbp.
>
> In both cases they will also have to tell dgit --overwrite, just as
> they would for 5.7 and earlier.
>
> It might be possible to find a suitable parent to overwrite with a
> pseudomerge, provided the user has done `dgit fetch sid'.  The
> basic recipe would be to check that the last maintainer view tag
> corresponds to dgit/dgit/sid (except for debian/patches).
>
> But this is complicated and fiddly.  I suggest that we document this
> problem, instead.

Attached patch does this.  Since the case is so precisely specified, I
opted not to clutter the manpage with an explanation of exactly why
-fdiverged is needed.

-- 
Sean Whitton
From 2c7d02ff627caaf687e3486d4203e921da88d686 Mon Sep 17 00:00:00 2001
From: Sean Whitton 
Date: Sat, 27 Oct 2018 13:40:26 -0700
Subject: [PATCH] dgit-maint-debrebase(7): account for case discussed in
 #903377

Signed-off-by: Sean Whitton 
---
 dgit-maint-debrebase.7.pod | 11 +++
 1 file changed, 11 insertions(+)

diff --git a/dgit-maint-debrebase.7.pod b/dgit-maint-debrebase.7.pod
index e5abe17..e3d557a 100644
--- a/dgit-maint-debrebase.7.pod
+++ b/dgit-maint-debrebase.7.pod
@@ -269,6 +269,11 @@ patches applied.  Use
 
 =back
 
+If you were not previously using dgit to upload your package (i.e. you
+were not using the workflow described in dgit-maint-gbp(7)), and you
+happen to have run B in this clone of the repository,
+you will need to pass I<--fdiverged> to this command.
+
 =item (C) There is a delta queue, and patches are applied.
 
 Use
@@ -442,6 +447,12 @@ cowbuilder>.
 Upload with B or B.  Remember to pass
 I<--new> if the package is new in the target suite.
 
+In some cases where you used B since
+the last upload, it is not possible for dgit to make your history
+fast-forwarding from the history on B.  In such cases you
+will require I<--overwrite>.  Try pushing without this option first,
+and then dgit will suggest using it if it is needed.
+
 Right before uploading, if you did not just already do so, you might
 want to have git-debrebase(1) shuffle your branch such that the Debian
 delta queue appears right at the tip of the branch you will push:
-- 
2.11.0



signature.asc
Description: PGP signature

Bug#912067: [Pkg-openssl-devel] Bug#912067: libssl1.1: please add getmail/getmail4 to the dependencies to check

[Kurt Roeckx]

On Sat, Oct 27, 2018 at 04:30:13PM -0400, ant wrote:
> Package: libssl1.1
> Version: 1.1.0h-4
> Severity: wishlist
> 
> Dear Maintainer,
> 
>   hi,
> 
>   last year an upgrade of libssl1.1 ended up breaking
>   getmail/getmail4.  the maintainer suggested a blocking
>   bug or something informational, but i failed to file one.
> 
>   this year same situation again.  upgrade breaks getmail/
>   getmail4 upon upgrade to libssl1.1.1-1 - reverting the
>   upgrade restores the system so it can be used again.
> 
>   i'll put this as wishlist bug for those who might run into
>   the same thing,

Can you please clarify what stopped working, what error did you
get?

Are you asking to restart getmail on upgrade? Does that actually
fix your problem?

The new 1.1.1-1 version might break some things because for
various reasons. So if you get an error, please report it.


Kurt

Bug#912068: stretch-pu: package apache-directory-server/2.0.0~M15-4

[Dominik George]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

I would like to upload fixes for two RC bugs that affect stretch and make
the package uninstallable and, after manually fixing that, unusable:

 #909063 - apacheds: package installation fails due to incorrect 
apacheds.service unit
 #911557 - apacheds: broken symlinks: 
/usr/share/apacheds/lib/{log4j-1.2,commons-io,antlr}.jar

Find attached the diff between the version now in stretch and the proposed
version.

-BEGIN PGP SIGNATURE-

iQKJBAEBCABzFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAlvUzCUxGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYyMcZG9taW5p
ay5nZW9yZ2VAaXQucGlyYXRlbnBhcnRlaS5kZQAKCRC3mjwWoMTylrCFD/0QUhlM
ijX+9V3iHy8/j5T/jsLB5jyOcYuuFofC1vucHN9IQAx809U002X1ODYwicydkXcq
wpo9RAvPqJr1zYO47p9O8M/qj0wf1r4g/avZRH0rJbf1n0I8O8yJAUvTHtKjQXub
sARZm3HmZ/axSES281IzBthvjmPnMMJR6347irFrTIemgvBO84yxTw6n4qHMD+uc
hJPfjJ0bYuk+db0zv99QG8cSfGJoZG5IxpasIQKFvkBzj147EW+uzEahy/UxnqUw
kUobzzsviLR9qh2R2Rf8RlIIuKsfP9Fvdtf4aUwd00XpsW6nk3O37Rrlz/ZeWosP
RPEizy0cwaFYWxlTwVRd/2Gj6wKnGVHbNBU6x++XRGEae5nyFB5AnQcbWw8Zoj+M
Q4Cgfh07RtN5nu9o07MNrorr1ks/2muDFp+0Mu8T2inQ4p0V9Wf2RFEEJy/BPZMX
p7/h+4iP5CO2vtT130zhZhbj0laxdQ1HRVIjAmknSrYHF5QAY3BNINHiYp4YjfTH
piIGjddlW+DDwNvN/UXIAOtmxJlfpB/pcblSzzMLnTnxgNoxXxfPVN2qYQDJznvf
vk9yx1t2P829QE09eeOpR9TQnujU6uwN5rOosTw8mv4oH2Z7YOcJQ3V7otMUCXp4
Z3IfnTn+Cyj1HBMixuPc4KduGAufG6mdvX2Osw==
=oswM
-END PGP SIGNATURE-
diff --git a/debian/apacheds.service b/debian/apacheds.service
index e6de514..23efa17 100644
--- a/debian/apacheds.service
+++ b/debian/apacheds.service
@@ -8,14 +8,15 @@ Type=simple
 User=apacheds
 Group=apacheds
 EnvironmentFile=/etc/default/apacheds
-ExecStart=${JAVA_HOME}/bin/java ${JAVA_OPTS} \
--Dapacheds.controls=${ADS_CONTROLS} \
--Dapacheds.extendedOperations=${ADS_EXTENDED_OPERATIONS} \
-
-Dlog4j.configuration=file:${ADS_INSTANCES}/${ADS_INSTANCE}/conf/log4j.properties
 \
--Dapacheds.log.dir=${ADS_INSTANCES}/${ADS_INSTANCE}/log \
--cp '${ADS_HOME}/lib/*' \
-org.apache.directory.server.UberjarMain \
-${ADS_INSTANCES}/${ADS_INSTANCE}/
+ExecStart=/bin/sh -c "exec \
+${JAVA_HOME}/bin/java ${JAVA_OPTS} \
+  -Dapacheds.controls=${ADS_CONTROLS} \
+  -Dapacheds.extendedOperations=${ADS_EXTENDED_OPERATIONS} \
+  
-Dlog4j.configuration=file:${ADS_INSTANCES}/${ADS_INSTANCE}/conf/log4j.properties
 \
+  -Dapacheds.log.dir=${ADS_INSTANCES}/${ADS_INSTANCE}/log \
+  -cp '${ADS_HOME}/lib/*' \
+  org.apache.directory.server.UberjarMain \
+  ${ADS_INSTANCES}/${ADS_INSTANCE}/"
 PrivateTmp=true
 
 [Install]
diff --git a/debian/changelog b/debian/changelog
index 62c6358..bdfa64f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+apache-directory-server (2.0.0~M15-4+deb9u1) stretch; urgency=medium
+
+  * Team upload.
+  * Fix command in systemd service file. (Closes: #909063)
+  * Add missing dependencies to libraries. (Closes: #911557)
+
+ -- Dominik George   Sat, 27 Oct 2018 15:32:48 +0200
+
 apache-directory-server (2.0.0~M15-4) unstable; urgency=medium
 
   * Transition to Jetty 9
diff --git a/debian/control b/debian/control
index 0b02379..31df170 100644
--- a/debian/control
+++ b/debian/control
@@ -30,7 +30,14 @@ Homepage: http://directory.apache.org
 
 Package: libapacheds-java
 Architecture: all
-Depends: ${maven:Depends}, ${misc:Depends}, libapacheds-i18n-java (= 
${source:Version}), libapacheds-kerberos-codec-java (= ${source:Version})
+Depends:
+ libantlr-java,
+ libapacheds-i18n-java (= ${source:Version}),
+ libapacheds-kerberos-codec-java (= ${source:Version}),
+ libcommons-io-java,
+ liblog4j1.2-java,
+ ${maven:Depends},
+ ${misc:Depends},
 Suggests: ${maven:OptionalDepends}
 Description: Apache Directory Server (Libraries)
  ApacheDS is an embbedable directory server entirely written in Java, which

Bug#912067: libssl1.1: please add getmail/getmail4 to the dependencies to check

[ant]

Package: libssl1.1
Version: 1.1.0h-4
Severity: wishlist

Dear Maintainer,

  hi,

  last year an upgrade of libssl1.1 ended up breaking
  getmail/getmail4.  the maintainer suggested a blocking
  bug or something informational, but i failed to file one.

  this year same situation again.  upgrade breaks getmail/
  getmail4 upon upgrade to libssl1.1.1-1 - reverting the
  upgrade restores the system so it can be used again.

  i'll put this as wishlist bug for those who might run into
  the same thing,


thanks,

  ant


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

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

Versions of packages libssl1.1 depends on:
ii  debconf [debconf-2.0]  1.5.69
ii  libc6  2.27-6

libssl1.1 recommends no packages.

libssl1.1 suggests no packages.

-- debconf information:
  libssl1.1/restart-failed:
  libssl1.1/restart-services:

Bug#902309: [zebmccor...@asymptote.club: Re: Bug#902309: ITP: zeyple -- Automatically encrypt outgoing emails]

[Piper McCorkle]

- Forwarded message from Piper McCorkle  -

Date: Sat, 27 Oct 2018 19:03:27 +
From: Piper McCorkle 
To: Mike Gabriel 
Subject: Re: Bug#902309: ITP: zeyple -- Automatically encrypt outgoing emails
User-Agent: Mutt/1.9.4 (2018-02-28)

On Sat, Jun 30, 2018 at 09:07:23PM +, Mike Gabriel wrote:
> Ping me when you have the uploadable package ready and I step up as a sponsor.

So sorry to take so long to get back to you - apparently I skimmed right
past your email in my inbox. Bug #902324 is my RFS. Based on the input
from message #10 on it, I'll probably get a new version out in the next
couple of days.

-- 
Piper McCorkle (transitioning s/Zeb(ulon)?/Piper/)
zebmccor...@asymptote.club | https://keybase.io/zebMcCorkle
803A 0F47 82AD DDEA 46BE  055F F8F9 DB8C 1A54 6398

   |
   |
__/
  __  Asymptote Club
 /(bad ASCII graph by yours truly)
 |
 |



- End forwarded message -


signature.asc
Description: PGP signature

Bug#882424: rsh-command

[Joey Hess]

Ok, it always runs the rsh-command, but if it outputs anything to
stderr, even a minor warning, it seems that alpine then gives up on it
and falls back to imap.

In my case, /usr/lib/dovecot/imap was displaying this, but otherwise
working:

imap(,)Error: net_connect_unix(/var/run/dovecot/stats-writer) failed: 
Permission denied

What worked for me:

root@kite:~>cat /usr/local/bin/imap-for-alpine
#!/bin/sh
exec /usr/lib/dovecot/imap 2>/dev/null
root@kite:~>cat /etc/pine.conf
inbox-path={localhost}inbox
rsh-command=/usr/local/bin/imap-for-alpine

-- 
see shy jo


signature.asc
Description: PGP signature

Bug#912066: linux-igd: FTBFS with upnp 1.8.4

[James Cowgill]

Source: linux-igd
Version: 1.0+cvs20070630-6
Severity: important
Tags: sid buster
User: jcowg...@debian.org
Usertags: upnp-1.8-transition
Control: block 884635 by -1

Hi,

linux-idg FTBFS with upnp 1.8.4 (in experimental) with this error:
> gatedevice.c:10:10: fatal error: TimerThread.h: No such file or directory
>  #include 
>   ^~~
> compilation terminated.

The threadutil library is no longer shipped with upnp 1.8 since it's an
implementation detail which has nothing to do with upnp itself.

Unfortunately it looks like a lot of code needs rewriting to use
pthreads directly or another threading library (which can cope with some
of the extra features of threadutil like thread pooling).

James



signature.asc
Description: OpenPGP digital signature

Bug#905433: git-debrebase: debrebase new-upstream fails with "uninitialized value"

[Sean Whitton]

Hello,

On Fri 05 Oct 2018 at 01:34PM +0100, Ian Jackson wrote:

> To me "unpatched" is ambiguous: it can mean that the delta queue does
> not exist, or that it exists but has not been applied.  But luckily
> that doesn't matter ...

Ah, I was missing that this ambiguity is not a problem.

>> > Maybe the answer is to provide aliases.
>> >   convert-from-gbp
>> >   convert-from-unpatched
>> > ?
>>
>> I.e. these would both be aliases for a command called
>> convert-from-unapplied?
>
> Right.  The key points are that:
>
>  * gbp format is the same as package-with-unapplied-delta-queue
>format, modulo .gitignore (which apparently most people don't
>touch).
>
>  * If there is no delta queue then the algorithm for converting a
>package-with-unapplied-delta-queue will DTRT.

Okay, let's have convert-from-unpatches be an alias for
convert-from-gbp.

(One other option that has just occurred to me would be
'convert-from-pristine' since the upstream is pristine in the sense of
being untouched by Debian.)

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#910705: Bug#910687: dgit: build-source and push-source disregard -wc

[Sean Whitton]

Hello,

On Wed 10 Oct 2018 at 11:14PM +0100, Ian Jackson wrote:

> But I'm not really convinced that push-source and build-source ought
> ever to run rules clean.  So I think we need a new interpretation of
> clean modes: ie, the source builds should look at the clean mode and
> do *something*: and that something will be to check that it doesn't
> look like a git-add was forgotten.

Right.  Lots of checking is good, git cleaning is fine, but these
commands should not be invoking any rules targets.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#910705: Bug#910687: dgit: build-source and push-source disregard -wc

[Sean Whitton]

Hello,

On Wed 10 Oct 2018 at 11:24PM +0100, Ian Jackson wrote:

> There are three levels of dirtiness: contains uncommitted changes to
> tracked files; contains untracked but ignored files; contains
> untracked and un-ignored files.
>
> Currently dgit only *complains* about uncommitted changes to tracked
> files.
>
> Untracked files of both kinds are deleted by -wg[f] - except that if
> dgit uses a playtree it doesn't need to clean at all so it doesn't and
> the files are not included but also not deleted.
>
> That -wc does not spot untracked files is clearly a bug.  But it would
> be sensible to have a variant that tolerates ignored untracked files.
>
> What -wd[d] ought to do about untracked files - especially un-ignored
> ones - is far from clear.  It runs rules clean and then hopefully the
> build products are deleted, but clean targets are often buggy.
> gitignore files are often missing or incomplete.
>
> Hence my suggestion for -wd[d] by default to trip on untracked
> unignored files, but to ignore untracked ignored ones.  An ignored
> file has been deliberately marked to be excluded from the source
> code.  And there should be an option to allow un-ignored ones too.
>
> The underlying thing going on here is that when making a source
> package the user might reasonably want to simply not include the junk
> that is cluttering their tree, rather than having dgit insist on it
> being either deleted or included in the output.

Okay, I well enough follow now.

Thank you for sorting all this out in the latest release of dgit.  A
very nice improvement.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#912065: RFP: golang-notabug-makenotabuggreatagain-git-module-dev -- Package git-module is a Go module for Git access through shell commands

[Jeff Cliff]

Package: wnpp
Severity: wishlist

* Package name: golang-notabug-makenotabuggreatagain-git-module-dev
  Version : c64f3cabc8 
  Upstream Author : Unknwon 无闻 
* URL : https://notabug.org/makenotabuggreatagain/git-module/
* License : mit
  Programming Lang: go
  Description : Package git-module is a Go module for Git access through 
shell commands

Package git-module is a Go module for Git access through shell commands.

vendored dependency of gogs ( #911419 )

Bug#882424: rsh-command

[Joey Hess]

Unfortunately alpine sometimes does not use rsh-command when configured
to do so, and connects to the imap server itself. I don't know why.
I had this working for some period of time as documented in my previous
message, and then it stopped working, though alpine is still at version 
2.21+dfsg1-1

-- 
see shy jo


signature.asc
Description: PGP signature

Bug#912064: O: openvpn-auth-radius -- OpenVPN RADIUS authentication module

[Helmut Grohne]

Package: wnpp

I am orphaning openvpn-auth-radius on behalf of Torge with his consent.

The package description is:
 A plugin for OpenVPN 2.x that implements authentication of users against a
 RADIUS server. It features:
 * RADIUS authentication and accounting support for OpenVPN
 * analysis of RADIUS attributes:
   o framed ip address
   o framed routes
   o acct interim interval
   o vendor specific attributes by additional scripts

The package hasn't seen a maintainer upload in almost five years. It
presently needs packaging a new upstream release, going through the
reported bugs and some basic updating to the current packaging practise.

That said, the package does have a small and growing user base and is
basically working. It generally doesn't need that much attention to
keep it in a working state.

Even though I am a former contributor to the package myself, I am not
going to step up, because I have no deployment anymore and thus am
unable to test it.

I would like to thank Andreas for taking care with his NMU. Please feel
free to turn it into a QA upload or lowering the delay.

Helmut

Bug#906603: Can't reproduce.

[Santiago Vila]

On Sat, 27 Oct 2018, Hilko Bengen wrote:

> control: user debian-rele...@lists.debian.org
> control: usertags -1 + bsp-2018-10-de-karlsruhe
> control: tag -1 moreinfo
> control: tag -1 unreproducible
> 
> Hi Santiago,
> 
> greetings from the BSP in Karlsruhe.
> 
> I was going to try if the the FTBFS you reported might have been fixed
> in the new upstream version (0.12.5), but I cannot even reproduce it at
> all.

Thanks for testing. I can't reproduce this anymore, but this used to
fail all the time in August when I reported it:

https://tests.reproducible-builds.org/debian/history/joblib.html

> I have tried 0.12.1-1 (the version you reported against) and
> 0.12.3-1 (the version currently in unstable) on clean sid-amd64 and
> buster-amd64 chroots.

I guess then that the blame is likely to be on some of the build-depends.
To be sure, I would try next a chroot of buster in August from
snapshot.debian.org.

Thanks.

Bug#907335: similar issue

[Julian Taylor]

this problem probably has the same python change as cause as this issue:

https://github.com/PyCQA/pycodestyle/issues/786
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908700

Bug#909928: Marking as pending

[Hilko Bengen]

control: tag -1 pending

The sn package is being adopted and this bug has already been addressed;
see .

Cheers,
-Hilko

Bug#912063: RFP: golang-notabug-makenotabuggreatagain-ldap-dev -- Basic LDAP v3 functionality for the GO programming language.

[Jeff Cliff]

Package: wnpp
Severity: wishlist

* Package name: golang-notabug-makenotabuggreatagain-ldap-dev
  Version : 3
  Upstream Author : John Weldon 
* URL : https://notabug.org/makenotabuggreatagain/ldap
* License : MIT
  Programming Lang: go
  Description : Basic LDAP v3 functionality for the GO programming language.

Features:
Connecting to LDAP server (non-TLS, TLS, STARTTLS)
Binding to LDAP server
Searching for entries
Filter Compile / Decompile
Paging Search Results
Modify Requests / Responses
Add Requests / Responses
Delete Requests / Responses

(vendored) prerequisite for gogs ( #911419 )

Bug#869138: fonts-sil-tagmukay stuck in NEW?

[Fabian Greffrath]

Hi Daniel,

welcome to the team!

Am Samstag, den 27.10.2018, 00:10 +0700 schrieb Daniel Glassey:
> This font has been in the NEW queue along with fonts-sil-awami-
> nastaliq for over 1 year without any problems being reported to this
> ITP.

Indeed, I am also confused by this and asked FTP-Master not too long
ago if there was a reason for this delay - but yet without a reply.

> The maintainer needs to be changed to the debian-fonts list at some
> point. Should we make that change and upload again or is there
> anything else to be done?

No, the package is considered ready and is really only waiting to get
accepted. If you would like to re-upload with some detail changes,
please feel free, I see no objections.

Thank you!

 - Fabian



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

Bug#907199: Should the weboob package stay in Debian?

[Martín Ferrari]

Chris et al,

On 26/10/18 15:31, Chris Lamb wrote:

>> I am concerned about the lack of progress.  I would be grateful
>> for advice on what I should do next.
> 
> I was led to believe — althought naturally feel very free to correct
> me — that the AH team were (quite correctly,) handling this issue and
> thus I have not been taking action on it myself as leader@.

We were asked for an opinion on this matter, which we expressed about a
month ago in the BTS.

We think we should not get involved in the minutiae of how this is
solved, but our original recommendation still remains (quoting from our
previous email):

> We believe the next release should not contain the package in
> question in its current state

[..]

> If this dispute cannot be resolved amicably and timely, we believe 
> the FTP-master team can -and should- unilaterally remove the package
> from the archive.
For further clarification, this means that we believe there is time
until the freeze to solve this issue, and if it is not solved by then,
the package should be removed from testing and unstable.

-- 
Martín



signature.asc
Description: OpenPGP digital signature

Bug#912059: debian-policy: please increase ToC depth (for Lintian's benefit)

[Sean Whitton]

control: tag -1 +pending

Hello,

On Sat 27 Oct 2018 at 05:48PM +0100, Colin Watson wrote:

> I think it would be much simpler to just increase the Policy ToC's
> section depth.  That would seem generally slightly more useful (there
> isn't so much noise at the fourth level that it would make the ToC
> substantially harder to read), and would relieve Lintian from having to
> do this hack.

Indeed, we do not have many fourth level headings.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#887602: details for test case crash

[Hilko Bengen]

user debian-rele...@lists.debian.org
usertags 887602 + bsp-2018-10-de-karlsruhe
thank you

Hi,

I am able to reproduce the mentioned test case crash when building dia
with freetype 2.9.1-2.

Running the test ("dia ../samples/render-test.dia --export=rt.shape")
after building, installing dia with freetype 2.9.1-2 also crashes.

Running the test after building, installing dia with freetype 2.9.1-2
and downgrading freetype to 2.8.1-2 also crashes.

Running the test after building, installing dia with freetype 2.8.1-2
does *not* crash.

Running the test after building, installing dia with freetype 2.8.1-2
and upgrading freetype to 2.9.1-2 does *not* crash.

Cheers,
-Hilko

Bug#912043: RE: mono: please upload mono v5

[Jo Shields]

Good steps: join #debian-cli on Freenode, and bug Meebey to give you
access to the Salsa group (I don't think I have sufficient rights to do it).

One thing that would help lighten the load is for someone to take care
of the ancillary repos - libgdiplus, mod-mono, mono-vbnc, xsp, fsharp
etc. I can go into more detail on the release process in IRC, if we want
to be sure to pick versions with something approaching "LTS" status.

On 27/10/2018 14:21, Alexandre Viau wrote:
> On 2018-10-27 2:16 p.m., Jo Shields wrote:
>> Mostly https://github.com/mono/mono/issues/7445#issuecomment-409363281
>> is the state of the art on the topic.
> 
> Ah! I found it just after my last post on this bug.
> 
>> I will be spending all of next week working on this, but I have no idea
>> how ftpmaster will react to some of the necessary changes (e.g. BTLS)
> 
> Great! I am very happy to hear this.
> 
> Let me know if I can help in any way.
> 



signature.asc
Description: OpenPGP digital signature

Bug#912043: RE: mono: please upload mono v5

[Jo Shields]

Mostly https://github.com/mono/mono/issues/7445#issuecomment-409363281
is the state of the art on the topic.

I will be spending all of next week working on this, but I have no idea
how ftpmaster will react to some of the necessary changes (e.g. BTLS)

On 27/10/2018 13:27, Alexandre Viau wrote:
> Hello Jo,
> 
> I notice that you are working on Mono's official packaging for Mono v5 here:
>  - https://github.com/mono/linux-packaging-mono
> 
> Is there any reason why you are not uploading to Debian?
> 
> Would you please document your blockers, if any, in this bug?
> 
> I'd love to see Mono v5 in Debian but the packaging looks very
> complicated and I would prefer if somebody with your experienced worked
> on it. However, I might be able to help on some blockers that you may have.
> 
> Thank you in advance,
> 



signature.asc
Description: OpenPGP digital signature

Bug#912043: RE: mono: please upload mono v5

[Alexandre Viau]

On 2018-10-27 2:16 p.m., Jo Shields wrote:
> Mostly https://github.com/mono/mono/issues/7445#issuecomment-409363281
> is the state of the art on the topic.

Ah! I found it just after my last post on this bug.

> I will be spending all of next week working on this, but I have no idea
> how ftpmaster will react to some of the necessary changes (e.g. BTLS)

Great! I am very happy to hear this.

Let me know if I can help in any way.

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#872754: fetchmail: tls_process_server_hello:unsupported protocol

[Nicolas Boulenguez]

Package: fetchmail
Followup-For: Bug #872754

Hello.
I have tried 6.4.0~beta4-1 in experimental.
This resulted in:

reading message for *:1 among * flushed
(maybe unrelated) show_signal_msg: 1 callbacks suppressed
fetchmail: segfault at 14 ip 560d2f73a718 sp 7ffe8242c790 error 6 in 
fetchmail[560d2f716000+44000]

Feel free to contact me if you want to reproduce the issue.

ii  libgssapi-krb5-2  1.16.1-1
ii  libk5crypto3  1.16.1-1
ii  libkrb5-3 1.16.1-1
ii  libssl1.1 1.1.1-1
ii  ca-certificates  20170717
pn  fetchmailconf  
pn  resolvconf 

/etc/default/fetchmail changed

set no bouncemail
defaults:
  antispam -1
  batchlimit 100

poll *
 protocol pop3
user "*" there password "*"
 is  "*" here
 options fetchall ssl sslcertck

Bug#909835: mailscripts: Uninitialized value warnings from notmuch-slurp-debbug

[Sean Whitton]

control: tag -1 +pending

Hello,

On Sat 29 Sep 2018 at 08:08AM -0300, David Bremner wrote:

> % notmuch-slurp-debbug 727708
> 1000
> Use of uninitialized value $mid in substitution (s///) at 
> /usr/bin/notmuch-slurp-debbug line 92.
> Use of uninitialized value $mid in concatenation (.) or string at 
> /usr/bin/notmuch-slurp-debbug line 93.
> [repeats a total of 11 times]
>
> As you can see below I am running notmuch from master, so that is conceivably 
> a factor.

Thank you again for the report.

Some of the messages in that bug, after processing by mbox2maildir, do
not have any headers; they seem to be chunks of messages.  I don't know
how that happens nor what notmuch would do with such a file, but it
seems that notmuch-slurp-debbug should simply skip over them.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#897496: python-pathlib: diff for NMU version 1.0.1-2.1

[Julian Taylor]

Control: tags 897496 + pending
Control: tags 897496 + patch
Control: user debian-rele...@lists.debian.org
Control: usertags 897496 + bsp-2018-10-de-karlsruhe

Dear maintainer,

I've prepared an NMU for python-pathlib (versioned as 1.0.1-2.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards,
diff -Nru python-pathlib-1.0.1/debian/changelog
python-pathlib-1.0.1/debian/changelog
--- python-pathlib-1.0.1/debian/changelog   2015-06-25 10:02:25.0
+0200
+++ python-pathlib-1.0.1/debian/changelog   2018-10-27 19:02:33.0
+0200
@@ -1,3 +1,11 @@
+python-pathlib (1.0.1-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * socket-test-fix.patch:
+Adapt testcase to work with python2 exception type (Closes: #897496)
+
+ -- Julian Taylor   Sat, 27 Oct 2018
19:02:33 +0200
+
 python-pathlib (1.0.1-2) unstable; urgency=medium

   * Enable reproducible build py patching generation of manpage
diff -Nru python-pathlib-1.0.1/debian/patches/series
python-pathlib-1.0.1/debian/patches/series
--- python-pathlib-1.0.1/debian/patches/series  1970-01-01
01:00:00.0 +0100
+++ python-pathlib-1.0.1/debian/patches/series  2018-10-27
18:59:43.0 +0200
@@ -0,0 +1 @@
+socket-test-fix.patch
diff -Nru python-pathlib-1.0.1/debian/patches/socket-test-fix.patch
python-pathlib-1.0.1/debian/patches/socket-test-fix.patch
--- python-pathlib-1.0.1/debian/patches/socket-test-fix.patch   1970-01-01
01:00:00.0 +0100
+++ python-pathlib-1.0.1/debian/patches/socket-test-fix.patch   2018-10-27
19:02:33.0 +0200
@@ -0,0 +1,18 @@
+Description: adapt test exception to python2
+Author: Julian Taylor 
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897496
+Bug: https://bitbucket.org/pitrou/pathlib/issues/32
+
+Index: python-pathlib-1.0.1/test_pathlib.py
+===
+--- python-pathlib-1.0.1.orig/test_pathlib.py
 python-pathlib-1.0.1/test_pathlib.py
+@@ -1687,7 +1687,7 @@ class _BasePathTest(object):
+ self.addCleanup(sock.close)
+ try:
+ sock.bind(str(P))
+-except OSError as e:
++except (OSError, socket.error) as e:
+ if "AF_UNIX path too long" in str(e):
+ self.skipTest("cannot bind Unix socket: " + str(e))
+ self.assertTrue(P.is_socket())

Bug#886872: agrep: does not properly clean after build

[Reiner Herrmann]

Control: severity -1 important

Lowering the severity as it doesn't FTBFS on the first build.
Failing to build the second time is not RC.


signature.asc
Description: PGP signature

Bug#912062: fontforge: segfaults when opening some UFO fonts

[Thibaut Girka]

Package: fontforge
Version: 1:20170731~dfsg-1
Severity: normal

When trying to open some UFO fonts, fontforge segfaults with the following
trace:

#0  0x7f2746c6e5aa in SPLFindOrder (ss=0x21) at ././fontforge/svg.c:3453
#1  0x7f2746c793fe in SFLFindOrder (sf=sf@entry=0x55e103d80d10,
layerdest=layerdest@entry=2) at ././fontforge/svg.c:3492
#2  0x7f2746cb7aa1 in SFReadUFO (basedir=basedir@entry=0x55e103d10eb0
"/home/thib/tmp/fonts-cantarell-0.111/master_ufo/Cantarell-Regular.ufo",
flags=flags@entry=0)
at ././fontforge/ufo.c:4221
#3  0x7f2746bf4fb0 in _ReadSplineFont (file=0x55e103c9dc50, file@entry=0x0,
filename=,
filename@entry=0x55e103cc0730 "/home/thib/tmp/fonts-
cantarell-0.111/master_ufo/Cantarell-Regular.ufo/",
openflags=openflags@entry=(unknown: 0)) at ././fontforge/splinefont.c:1086
#4  0x7f2746bf5a9c in ReadSplineFont
(filename=filename@entry=0x55e103cc0730 "/home/thib/tmp/fonts-
cantarell-0.111/master_ufo/Cantarell-Regular.ufo/", openflags=openflags@entry=
(unknown: 0)) at ././fontforge/splinefont.c:1288
#5  0x7f2746bf5c30 in LoadSplineFont (filename=,
openflags=openflags@entry=(unknown: 0)) at ././fontforge/splinefont.c:1346
#6  0x7f2746aaf39c in ViewPostScriptFont (filename=,
openflags=0) at ././fontforge/fontviewbase.c:1341
#7  0x7f2747a58023 in fontforge_main (argc=2, argv=0x7ffeb49c01d8) at
././fontforgeexe/startui.c:1353
#8  0x7f2746241b17 in __libc_start_main (main=
0x55e1023687b0 , argc=2, argv=0x7ffeb49c01d8, init=,
fini=, rtld_fini=, stack_end=0x7ffeb49c01c8) at
../csu/libc-start.c:310
#9  0x55e1023687ea in _start ()


This can be reproduced by trying to open the UFO fonts generated from the
fonts-cantarell package:
$ apt source fonts-cantarell
$ cd fonts-cantarell-0.111/
$ fontmake -g src/Cantarell.glyphs -o ufo
$ fontforge master_ufo/Cantarell-Regular.ufo/



-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (990, 'testing-debug'), (990, 'testing'), (120, 
'unstable-debug'), (120, 'unstable'), (105, 'experimental-debug'), (105, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.17.0-3-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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages fontforge depends on:
ii  fontforge-common  1:20170731~dfsg-1
ii  libc6 2.27-6
ii  libfontforge2 1:20170731~dfsg-1
ii  libgdraw5 1:20170731~dfsg-1
ii  libltdl7  2.4.6-6
ii  libx11-6  2:1.6.7-1

fontforge recommends no packages.

Versions of packages fontforge suggests:
pn  autotrace 
pn  fontforge-doc 
pn  fontforge-extras  
pn  potrace   
pn  python-fontforge  

-- no debconf information

Bug#910031: fuse3: Incomplete debian/copyright?

[Fabio Pedretti]

It looks like this is fixed in 3.2.6-1 :
https://metadata.ftp-master.debian.org/changelogs/main/f/fuse3/fuse3_3.2.6-1_copyright
but missed closing this bug?

fuse3 (3.2.6-1) unstable; urgency=medium

  * New upstream release:
- fix CVE-2018-10906, restriction bypass of the allow_other option when
  SELinux is active (closes: #911343).
  * Honor nocheck in DEB_BUILD_OPTIONS (closes: #910029).
  * Don't force xz compression for source and binaries (closes: #910030).
  * Update copyright file.

 -- Laszlo Boszormenyi (GCS)   Thu, 18 Oct 2018 21:36:00 +

Bug#912043: mono: please upload mono v5

[Alexandre Viau]

Hello Jo,

I notice that you are working on Mono's official packaging for Mono v5 here:
 - https://github.com/mono/linux-packaging-mono

Is there any reason why you are not uploading to Debian?

Would you please document your blockers, if any, in this bug?

I'd love to see Mono v5 in Debian but the packaging looks very
complicated and I would prefer if somebody with your experienced worked
on it. However, I might be able to help on some blockers that you may have.

Thank you in advance,

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#911996: libqt5serialport5 version in Debian stable is wrong

[Lisandro Damián Nicanor Pérez Meyer]

Hi Rudolf!

El vie., 26 oct. 2018 20:09, Rudolf Polzer 
escribió:

> Package: libqt5serialport5
> Version: 5.7.1 is available, 5.9.x is missing
>
> I run Debian stable and need libqt5serialport5 version 5.9 instead of
> 5.7 - other parts of Debian stable do not accept qt5 version lower than 5.9
>

Actually stable only has 5.7. Due to the nature of Qt we can't provide
backports. And sadly we do not have PPA-like infrastructure like Ubuntu
does, so we can't provide unofficial backports.

I'm so closing this bug.

>

Bug#912061: msgpack-c FTBFS with googletest 1.8.1-1

[Adrian Bunk]

Source: msgpack-c
Version: 3.0.1-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/msgpack-c.html

...
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/build/1st/msgpack-c-3.0.1'
mkdir build-gtest
cd build-gtest && \
  cmake -Wno-dev 
-DCMAKE_INSTALL_PREFIX=/build/1st/msgpack-c-3.0.1/build-gtest/install 
/usr/src/googletest/googletest && \
  make install
CMake Warning at CMakeLists.txt:47 (project):
  VERSION keyword not followed by a value or was followed by a value that
  expanded to nothing.


-- The CXX compiler identification is GNU 8.2.0
-- The C compiler identification is GNU 8.2.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Found PythonInterp: /usr/bin/python (found version "2.7.15") 
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Check if compiler accepts -pthread
-- Check if compiler accepts -pthread - yes
-- Found Threads: TRUE  
-- Configuring done
-- Generating done
-- Build files have been written to: /build/1st/msgpack-c-3.0.1/build-gtest
make[2]: Entering directory '/build/1st/msgpack-c-3.0.1/build-gtest'
make[2]: *** No rule to make target 'install'.  Stop.

Bug#188731: debian-policy: "strip --strip-unneeded" is insufficient

[Sean Whitton]

control: tag -1 +patch

Hello,

On Fri 28 Sep 2018 at 05:38AM GMT, Niels Thykier wrote:

>  * We now have auto-generated dbgsym packages by dh_strip (which were
>just an idea when Bill wrote that answer).
>
>  * Policy mentions "--remove-section=.comment --remove-section=.note" in
>a footnote as a "You might also want to use ...".
>
>  * Policy section 10.1 implies that "INSTALL = install -s" is a useful
>way of stripping binaries (both in text and examples).  Besides not
>covering the .comment + .note sections it also neuters dh_strip's
>ability to create dbgsym packages.
>
>
> I think we should update the policy to say that you should use
> "--strip-unneeded --remove-section=.comment --remove-section=.note" and
> maybe recommend delegating that task (where possible) to dh_strip as it
> provide dbgsym packages.

Thank you for following up.

Here is a minimal patch, for which I am seeking seconds.  I didn't
include a recommendation to use dh_strip because we generally keep such
recommendations in footnotes rather than the text of Policy, and we are
trying to reduce the number of footnotes -- but I don't mind adding it
if others think it would be a good idea (and it wouldn't need
seconding).

diff --git a/policy/ch-files.rst b/policy/ch-files.rst
index 21c4c37..7106afe 100644
--- a/policy/ch-files.rst
+++ b/policy/ch-files.rst
@@ -48,12 +48,20 @@ used:
 CC = gcc
 CFLAGS = -O2 -g -Wall # sane warning options vary between programs
 LDFLAGS = # none
-INSTALL = install -s # (or use strip on the files in debian/tmp)

-Note that by default all installed binaries should be stripped, either
-by using the ``-s`` flag to ``install``, or by calling ``strip`` on the
-binaries after they have been copied into ``debian/tmp`` but before the
-tree is made into a package.
+By default all installed binaries should be stripped by calling
+
+::
+
+strip --strip-unneeded --remove-section=.comment --remove-section=.note 
binaries
+
+on the binaries after they have been copied into ``debian/tmp`` but
+before the tree is made into a package.
+
+It is not recommended to strip binaries by passing the ``-s`` flag to
+``install``, because this fails to remove .comment and .note sections,
+and also prevents the automatic creation of dbgsym binary packages by
+tools like ``dh_strip``.

 Although binaries in the build tree should be compiled with debugging
 information by default, it can often be difficult to debug programs if
@@ -114,7 +122,7 @@ All installed shared libraries should be stripped with

 ::

-strip --strip-unneeded your-lib
+strip --strip-unneeded --remove-section=.comment --remove-section=.note 
your-lib

 (The option ``--strip-unneeded`` makes ``strip`` remove only the symbols
 which aren't needed for relocation processing.) Shared libraries can
@@ -123,7 +131,8 @@ linking are in a separate part of the ELF object file.  [#]_

 Note that under some circumstances it may be useful to install a shared
 library unstripped, for example when building a separate package to
-support debugging.
+support debugging.  The debhelper `dh_strip`` tool can create such
+packages automatically.

 Shared object files (often ``.so`` files) that are not public
 libraries, that is, they are not meant to be linked to by third party
@@ -741,9 +750,8 @@ restricted to ASCII when it is possible to do so.
shared library, like ``mklibs`` does in the Debian installer project.

 .. [#]
-   You might also want to use the options ``--remove-section=.comment``
-   and ``--remove-section=.note`` on both shared libraries and
-   executables, and ``--strip-debug`` on static libraries.
+   You might also want to use the option ``--strip-debug`` on static
+   libraries.

 .. [#]
A common example are the so-called "plug-ins", internal shared

=

To obtain a side-by-side diff:

% git clone salsa.debian.org:dbnpolicy/policy.git debian-policy
% cd debian-policy
% git difftool -y -x icdiff master..origin/bug188731-spwhitton

Alternatively, visit

https://salsa.debian.org/dbnpolicy/policy/commit/3cc86484767ac0aead9b7466c074ade5021ef225?view=parallel

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#912032: libdatetime-timezone-perl 2.09-1+2018g flagged for acceptance

[Adam D Barratt]

Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian .

Thanks for your contribution!

Upload details
==

Package: libdatetime-timezone-perl
Version: 2.09-1+2018g

Explanation: update included data

Bug#912060: botch FTBFS: W504 line break after binary operator

[Adrian Bunk]

Source: botch
Version: 0.21-6
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/botch.html

...
   debian/rules override_dh_auto_test-arch
make[1]: Entering directory '/build/1st/botch-0.21'
/usr/bin/make test
make[2]: Entering directory '/build/1st/botch-0.21'
# FIXME: add more tests
#./tests.py
#OCAMLPATH=/build/1st/botch-0.21/dose/_build ocamlbuild -classic-display 
-use-ocamlfind -cflags "-w +a-4-9-24" tests.native
#./tests.native
pyflakes3 tools/*.py
# E402 is triggered by the sys.path.append() statement in front of import of 
utils
# see https://github.com/PyCQA/pycodestyle/issues/264
pycodestyle --ignore=E402,E722 tools/*.py
tools/add-arch.py:33:22: W504 line break after binary operator
tools/build-order-from-zero.py:170:27: W504 line break after binary operator
tools/build-order-from-zero.py:203:27: W504 line break after binary operator
tools/buildgraph2packages.py:46:22: W504 line break after binary operator
tools/calcportsmetric.py:56:22: W504 line break after binary operator
tools/calcportsmetric.py:57:22: W504 line break after binary operator
tools/calcportsmetric.py:58:22: W504 line break after binary operator
tools/calcportsmetric.py:59:22: W504 line break after binary operator
tools/calcportsmetric.py:63:14: W504 line break after binary operator
tools/calcportsmetric.py:64:14: W504 line break after binary operator
tools/calcportsmetric.py:68:14: W504 line break after binary operator
tools/calcportsmetric.py:69:14: W504 line break after binary operator
tools/check-ma-same-versions.py:49:22: W504 line break after binary operator
tools/check-ma-same-versions.py:50:22: W504 line break after binary operator
tools/checkfas.py:31:22: W504 line break after binary operator
tools/checkfas.py:32:22: W504 line break after binary operator
tools/checkfas.py:35:30: W504 line break after binary operator
tools/checkfas.py:38:30: W504 line break after binary operator
tools/checkfas.py:39:30: W504 line break after binary operator
tools/convert-arch.py:34:22: W504 line break after binary operator
tools/dose2html.py:111:15: W504 line break after binary operator
tools/dose2html.py:112:15: W504 line break after binary operator
tools/dose2html.py:114:15: W504 line break after binary operator
tools/dose2html.py:115:15: W504 line break after binary operator
tools/dose2html.py:116:15: W504 line break after binary operator
tools/dose2html.py:139:11: W504 line break after binary operator
tools/dose2html.py:140:11: W504 line break after binary operator
tools/dose2html.py:141:11: W504 line break after binary operator
tools/dose2html.py:142:11: W504 line break after binary operator
tools/dose2html.py:143:11: W504 line break after binary operator
tools/dose2html.py:147:11: W504 line break after binary operator
tools/dose2html.py:174:19: W504 line break after binary operator
tools/dose2html.py:206:11: W504 line break after binary operator
tools/dose2html.py:207:11: W504 line break after binary operator
tools/dose2html.py:208:11: W504 line break after binary operator
tools/dose2html.py:209:11: W504 line break after binary operator
tools/dose2html.py:210:11: W504 line break after binary operator
tools/dose2html.py:216:9: W504 line break after binary operator
tools/dose2html.py:258:19: W504 line break after binary operator
tools/dose2html.py:340:11: W504 line break after binary operator
tools/dose2html.py:341:11: W504 line break after binary operator
tools/dose2html.py:348:15: W504 line break after binary operator
tools/dose2html.py:366:15: W504 line break after binary operator
tools/dose2html.py:521:25: W504 line break after binary operator
tools/dose2html.py:527:30: W504 line break after binary operator
tools/dose2html.py:530:30: W504 line break after binary operator
tools/dose2html.py:569:13: W504 line break after binary operator
tools/dose2html.py:570:13: W504 line break after binary operator
tools/droppable-diff.py:11:22: W504 line break after binary operator
tools/droppable-union.py:10:51: W504 line break after binary operator
tools/droppable-union.py:11:51: W504 line break after binary operator
tools/droppable-union.py:12:51: W504 line break after binary operator
tools/extract-scc.py:33:50: W504 line break after binary operator
tools/extract-scc.py:34:50: W504 line break after binary operator
tools/extract-scc.py:39:45: W504 line break after binary operator
tools/extract-scc.py:42:43: W504 line break after binary operator
tools/fix-cross-problems.py:73:22: W504 line break after binary operator
tools/fix-cross-problems.py:76:30: W504 line break after binary operator
tools/graph-difference.py:89:11: W504 line break after binary operator
tools/graph-difference.py:107:15: W504 line break after binary operator
tools/graph-difference.py:111:11: W504 line break after binary operator
tools/graph-info.py:12:22: W504 line break after binary operator
tools/latest-version.py:30:22: W504 line break after binary operator
tools/multiarch-interpreter-problem.py:164:22: W504 line break 

Bug#912057: wine: please add a new wine-mono source package

[Alexandre Viau]

Hello,

I have decided to work on this.

I have opened an ITP here:
 - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912058

Cheers,

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#911864: lintian gives E: statically-linked-binary for golang project's binary

[Jeffrey Cliff]

I just spun up a new amd64 sid vm and replicated.

1) install buster
2) change /etc/apt/sources.list to sid
3) apt-get update, apt-get ugprade, apt-get dist-upgrade
4) reboot
5) apt-get install (tor, git, aptitude) dh-golang, gccgo golang-go
golang-github-mattn-go-colorable-dev golang-github-mattn-go-isatty-dev
oglang-golang-x-net-dev golang-github-mgutz-ansi-dev
golang-golang-x-sys-dev (ie the prerequisites)
6) git clone https://notabug.org/themusicgod1/panicparse
7) remove the comment so it's dependent upon 'golang-go'
8) debuild -uc -us -b

-> gets the error

On Fri, 26 Oct 2018 at 16:41, Chris Lamb  wrote:

> Jeffrey,
>
> > I had tried with golang-go, with gcc-go, same thing happens. I haven't
> > tried golang-any though.
>
> I just tried building package after uncommenting out "golang-go"
> from the Build-Depends.
>
> This silenced the warning for me, so I suggest there is something
> amiss with your testcase.
>
>
> Best wishes,
>
> --
>   ,''`.
>  : :'  : Chris Lamb
>  `. `'`  la...@debian.org / chris-lamb.co.uk
>`-
>


-- 
GENERATION 26: The first time you see this, copy it into your sig on any
forum and add 1 to the generation

Bug#912058: ITP: wine-mono - replacement for the .NET runtime and class libraries in Wine

[Alexandre Viau]

Package: wnpp
Severity: wishlist
Owner: Alexandre Viau 
X-Debbugs-CC: debian-w...@lists.debian.org

* Package name: wine-mono
  Version : 0.90-1
  Upstream Author : Vincent Povirk
* URL : https://github.com/madewokherd/wine-mono
* License : Expat
  Programming Lang: Shell
  Description : Wine Mono is a package containing Mono and other
projects, intended as a replacement for the .NET runtime and class
libraries in Wine. It works in conjunction with Wine's builtin
mscoree.dll, and it is not intended to be useful for any other purpose.

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#912059: debian-policy: please increase ToC depth (for Lintian's benefit)

[Colin Watson]

Package: debian-policy
Version: 4.2.1.3
Severity: normal
Tags: patch

I recently noticed some outdated links generated by Lintian, which led
me to look into how they're generated.  Lintian has a script
(private/refresh-manual-refs) to grab references from the tables of
contents of various Debian documents, which it then uses in some of its
tags.  That currently has a hack for the main Policy document, dating
from last year:

'policy' => [
'/usr/share/doc/debian-policy/policy.html/index.html',
'https://www.debian.org/doc/debian-policy/',
# $index_re would match the Policy's TOC and work otherwise, but
# the TOC is generated only up to 3 levels deep as of 4.1.1.1, and
# we want refs to all levels.
qr{
  <(h[2-5])>\s*
  ([A-Z]|[A-Z]?[\d\.]+?)
  \.?\s+
  ([\w\s[:punct:]]+?)
  ]*?)\bhref="([^"]+)".+?
  
}x,
[['_ignored'], ['section'], ['title'], ['url']]
],

But this doesn't actually work at the moment: when I run this script it
loses all the policy entries from the output file.  There is some
support for extracting additional subsection references from other
files, but it would take some effort to get this to work for policy,
because the order of fields in the regex would need to be a bit
different when parsing the primary index versus when parsing individual
ch-* files.

I think it would be much simpler to just increase the Policy ToC's
section depth.  That would seem generally slightly more useful (there
isn't so much noise at the fourth level that it would make the ToC
substantially harder to read), and would relieve Lintian from having to
do this hack.

(See also #912055, a similar problem in doc-base.)

diff --git a/policy/index.rst b/policy/index.rst
index aa3fecd..b38e8c3 100644
--- a/policy/index.rst
+++ b/policy/index.rst
@@ -12,7 +12,7 @@ that each package must satisfy to be included in the 
distribution.
 This is Debian Policy version |policy_version|, released on |policy_date|.
 
 .. toctree::
-   :maxdepth: 3
+   :maxdepth: 4
:numbered:

ch-scope
@@ -31,7 +31,7 @@ This is Debian Policy version |policy_version|, released on 
|policy_date|.
 .. toctree::
:caption: Appendices
:name: appendix
-   :maxdepth: 3
+   :maxdepth: 4
:numbered:
 
ap-pkg-scope

Thanks,

-- 
Colin Watson   [cjwat...@debian.org]

Bug#910823: docker-compose: remove broken dependency on golang-docker-credential-helpers or fix golang-docker-credential-helpers

[Nye Liu]

See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910822

Is there anyone actually maintaining this package?

Bug#910822: golang-docker-credential-helpers: headless gnome-keyring failure

[Nye Liu]

See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910823

Is there anyone actually maintaining this package?

Bug#912057: wine: please add a new wine-mono source package

[Alexandre Viau]

Package: wine
Severity: wishlist
X-Debbugs-CC: sk...@debian.org

Hello,

As of wine 1.5.3, it is recommended to use wine-mono, which allows users
to run .NET apps without installing Microsoft's .NET implementation.

Installing Microsoft's dotnet is one of winetrick's most used features.
It would be great if Debian users wouldn't have to rely on it to run
dotnet apps.

Cheers,

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature