Bug#933930: [Pkg-utopia-maintainers] Bug#933930: Bug#933930: network-manager: Ethernet connection no longer works

[Vincent Lefevre]

On 2019-08-06 22:24:49 +0200, Michael Biebl wrote:
> Ok, so the current state of affairs is:
> 
> dhcp=dhclient works always
> dhcp=internal (the default) fails (sometimes)
> 
> ?

That's right.

Here are more complete logs for dhcp=internal, first those
corresponding to a success, then those corresponding to a
failure.

cventin:~> journalctl -b -11 -u NetworkManager
-- Logs begin at Tue 2016-04-19 07:35:01 CEST, end at Wed 2019-08-07 11:15:01 
CEST. --
Aug 06 15:00:21 cventin systemd[1]: Starting Network Manager...
Aug 06 15:00:21 cventin NetworkManager[766]:   [1565096421.8155] 
NetworkManager (version 1.19.90) is starting... (for the first time)
Aug 06 15:00:21 cventin NetworkManager[766]:   [1565096421.8156] Read 
config: /etc/NetworkManager/NetworkManager.conf (lib: no-mac-addr-change.conf)
Aug 06 15:00:21 cventin NetworkManager[766]:   [1565096421.8157] config: 
unknown key 'wifi.cloned-mac-address' in section [device-mac-addr-change-wifi] 
of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'
Aug 06 15:00:21 cventin NetworkManager[766]:   [1565096421.8157] config: 
unknown key 'ethernet.cloned-mac-address' in section 
[device-mac-addr-change-wifi] of file 
'/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'
Aug 06 15:00:21 cventin NetworkManager[766]:   [1565096421.8183] 
bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Aug 06 15:00:21 cventin NetworkManager[766]:   [1565096421.8244] 
manager[0x558e247f6020]: monitoring kernel firmware directory '/lib/firmware'.
Aug 06 15:00:21 cventin NetworkManager[766]:   [1565096421.8245] 
monitoring ifupdown state file '/run/network/ifstate'.
Aug 06 15:00:23 cventin systemd[1]: Started Network Manager.
Aug 06 15:00:23 cventin NetworkManager[766]:   [1565096423.8146] 
hostname: hostname: using hostnamed
Aug 06 15:00:23 cventin NetworkManager[766]:   [1565096423.8147] 
hostname: hostname changed from (none) to "cventin"
Aug 06 15:00:23 cventin NetworkManager[766]:   [1565096423.8153] 
dns-mgr[0x558e247d2240]: init: dns=default,systemd-resolved 
rc-manager=resolvconf
Aug 06 15:00:24 cventin NetworkManager[766]:   [1565096424.4806] Loaded 
device plugin: NMWifiFactory 
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.19.90/libnm-device-plugin-wifi.so)
Aug 06 15:00:24 cventin NetworkManager[766]:   [1565096424.5546] Loaded 
device plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.19.90/libnm-device-plugin-bluetooth.so)
Aug 06 15:00:24 cventin NetworkManager[766]:   [1565096424.5610] Loaded 
device plugin: NMWwanFactory 
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.19.90/libnm-device-plugin-wwan.so)
Aug 06 15:00:24 cventin NetworkManager[766]:   [1565096424.5843] Loaded 
device plugin: NMTeamFactory 
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.19.90/libnm-device-plugin-team.so)
Aug 06 15:00:24 cventin NetworkManager[766]:   [1565096424.5884] Loaded 
device plugin: NMAtmManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.19.90/libnm-device-plugin-adsl.so)
Aug 06 15:00:24 cventin NetworkManager[766]:   [1565096424.5887] manager: 
rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Aug 06 15:00:24 cventin NetworkManager[766]:   [1565096424.5889] manager: 
rfkill: WWAN enabled by radio killswitch; enabled by state file
Aug 06 15:00:24 cventin NetworkManager[766]:   [1565096424.5891] manager: 
Networking is enabled by state file
Aug 06 15:00:24 cventin NetworkManager[766]:   [1565096424.5893] 
dhcp-init: Using DHCP client 'internal'
Aug 06 15:00:24 cventin NetworkManager[766]:   [1565096424.6139] 
settings: Loaded settings plugin: ifupdown 
("/usr/lib/x86_64-linux-gnu/NetworkManager/1.19.90/libnm-settings-plugin-ifupdown.so")
Aug 06 15:00:24 cventin NetworkManager[766]:   [1565096424.6139] 
settings: Loaded settings plugin: keyfile (internal)
Aug 06 15:00:24 cventin NetworkManager[766]:   [1565096424.6139] 
ifupdown: management mode: unmanaged
Aug 06 15:00:24 cventin NetworkManager[766]:   [1565096424.6140] 
ifupdown:   interface-parser: parsing file /etc/network/interfaces
Aug 06 15:00:24 cventin NetworkManager[766]:   [1565096424.6140] 
ifupdown:   interface-parser: source line includes interfaces file(s) 
/etc/network/interfaces.d/*
Aug 06 15:00:24 cventin NetworkManager[766]:   [1565096424.6141] 
ifupdown: interfaces file /etc/network/interfaces.d/* doesn't exist
Aug 06 15:00:24 cventin NetworkManager[766]:   [1565096424.6141] 
ifupdown:   interface-parser: finished parsing file /etc/network/interfaces
Aug 06 15:00:24 cventin NetworkManager[766]:   [1565096424.6479] device 
(lo): carrier: link connected
Aug 06 15:00:24 cventin NetworkManager[766]:   [1565096424.6483] manager: 
(lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Aug 06 15:00:24 cventin NetworkManager[766]:   [1565096424.6495] manager: 
(enp0s25): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Aug 06 15:00:24 cventin NetworkManager[766]:   [1565096424.6544] 
settings: (enp0s25): created default 

Processed: Not fixed

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #931714 {Done: Ying-Chun Liu (PaulLiu) } 
[node-request-promise] node-request-promise: autopkgtest fails
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions node-request-promise/4.2.4-2.

-- 
931714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#931714: Not fixed

[Xavier]

Control: reopen -1

Adding node-request in recommended dependencies is not enough: package
is unusable without it

Processed: notfound 934033 in 4.0.4-5

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> notfound 934033 4.0.4-5
Bug #934033 [src:mitmproxy] mitmproxy: FTBFS in stretch (failing tests, expired 
certificate)
Ignoring request to alter found versions of bug #934033 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
934033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934033
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#934116: nose2: Requires mock 2.0 (for python < 3.6) but 3.0 is in unstable

[Bas Couwenberg]

Source: nose2
Version: 0.9.1-1
Severity: serious
Justification: makes the package in question unusable or mostly so
Control: affects -1 src:python-pyproj

Dear Maintainer,

The rebuild on the buildd of python-pyproj failed [0] due to a version
mismatch between nose2 & python-mock:

 pkg_resources.DistributionNotFound: The 'mock==2.0.0' distribution was not 
found and is required by nose2

The setup.py for nose2 contains:

install_requires=[
"six>=1.7",
"coverage>=4.4.1",
# mock on py2, py3.4 and py3.5
# not just py2: py3 versions of mock don't all have the same
# interface and this can cause issues
'mock==2.0.0;python_version<"3.6"',
],

But the dependencies of python-nose2 don't reflect this version constraint:

 Depends: python-mock, [...]

Until 2019-07-16 python-mock was at version 2.0.0, but has since
upgraded to 3.0.5.

Please make nose2 work for Python < 3.6 again.

[0] 
https://buildd.debian.org/status/fetch.php?pkg=python-pyproj=amd64=1.9.6-1%2Bb1=1565162830=0

Kind Regards,

Bas

Processed: nose2: Requires mock 2.0 (for python < 3.6) but 3.0 is in unstable

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:python-pyproj
Bug #934116 [src:nose2] nose2: Requires mock 2.0 (for python < 3.6) but 3.0 is 
in unstable
Added indication that 934116 affects src:python-pyproj

-- 
934116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934116
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: [Pkg-utopia-maintainers] Bug#933930: Bug#933930: network-manager: Ethernet connection no longer works

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 933930 network-manager: Ethernet connection sometimes fails with 
> internal dhcp client
Bug #933930 [network-manager] network-manager: Ethernet connection no longer 
works
Changed Bug title to 'network-manager: Ethernet connection sometimes fails with 
internal dhcp client' from 'network-manager: Ethernet connection no longer 
works'.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
933930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933930
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: fixed 934033 in 4.0.4-4

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 934033 4.0.4-4
Bug #934033 [src:mitmproxy] mitmproxy: FTBFS in stretch (failing tests, expired 
certificate)
Marked as fixed in versions mitmproxy/4.0.4-4.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
934033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934033
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#934111: jython: add explicit dependency on openjdk-11-jre-headless

[Emmanuel Bourg]

Hi Andreas,

Le 07/08/2019 à 08:08, Andreas Beckmann a écrit :

> in order to fix some upgrade issues from stretch to buster due to the
> dependency cycle between default-jre-headless, openjdk-11-jre-headless
> and ca-certificates-java (#929685), please add an explicit dependency on
> openjdk-11-jre-headless to jython as a workaround.

Could you elaborate a bit on the upgrade issue you encountered? It looks
a bit arbitrary to change the JRE dependency on jython to work around
the ca-certificates-java dependency cycle, and not on the other
applications depending on the JRE.


> I'm attaching a patch and the piuparts log showing the failure.
> The relevant diff of the upgrade test with the fixed package available
> is:
> 

> @@ -22494,23 +22486,6 @@
>Removing obsolete conffile 
> /etc/dbus-1/system.d/org.freedesktop.resolve1.conf ...^M
>Removing obsolete conffile 
> /etc/dbus-1/system.d/org.freedesktop.systemd1.conf ...^M
>Removing obsolete conffile 
> /etc/dbus-1/system.d/org.freedesktop.timedate1.conf ...^M
> -  Setting up jython-stilts (3.1.5-1) ...^M
> -  Exception in thread "main" java.lang.NoSuchMethodError: 
> java.nio.ByteBuffer.clear()Ljava/nio/ByteBuffer;^M
> -   at org.python.core.io.BufferedReader.clear(BufferedReader.java:147)^M
> -   at org.python.core.io.BufferedReader.(BufferedReader.java:27)^M

How did you get this exception? This was triggered by running Java 11
compiled code on Java 8, it's another issue we have to fix.

Emmanuel Bourg

Bug#934095: marked as pending in python-os-testr

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #934095 in python-os-testr reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/openstack-team/libs/python-os-testr/commit/1653e1fe95bebfb2f2402f6435a50b678805a146


Removed Python 2 support (Closes: #934095).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/934095

Processed: Bug#934095 marked as pending in python-os-testr

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #934095 [python-os-testr] python-os-testr (build-)depends on cruft package.
Added tag(s) pending.

-- 
934095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934095
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#931507: kernel-wedge: HDA sound board detection takes 60s in d-i

[Samuel Thibault]

Samuel Thibault, le ven. 26 juil. 2019 16:53:37 +0200, a ecrit:
> Indeed.  I can confirm that the attached patch fixes that.  I can look
> at the submission to upstream.

FTR, this was included in 4.19.65.

Samuel

Bug#934095: marked as done (python-os-testr (build-)depends on cruft package.)

[Debian Bug Tracking System]

Your message dated Wed, 07 Aug 2019 08:43:55 +
with message-id 
and subject line Bug#934095: fixed in python-os-testr 1.0.0-5
has caused the Debian Bug report #934095,
regarding python-os-testr (build-)depends on cruft package.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
934095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934095
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: python-os-testr
Version: 1.0.0-4
Severity: serious
Tags: bullseye, sid

The python-os-testr source package build-depends on the python-stestr binary 
package and the python-os-testdir binary package depends on it. The 
python-stestr binary package is no longer built by the python-stestr source 
package.

It's probably time to drop the python-os-testr binary package.
--- End Message ---
--- Begin Message ---
Source: python-os-testr
Source-Version: 1.0.0-5

We believe that the bug you reported is fixed in the latest version of
python-os-testr, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 934...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-os-testr package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 07 Aug 2019 09:04:40 +0200
Source: python-os-testr
Architecture: source
Version: 1.0.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 934095
Changes:
 python-os-testr (1.0.0-5) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Use team+openst...@tracker.debian.org as maintainer
   * Running wrap-and-sort -bast.
   * Use debhelper-compat instead of debian/compat.
 .
   [ Thomas Goirand ]
   * Removed Python 2 support (Closes: #934095).
   * Add Default_concurrency_to_0_to_avoid_TypeError_in_stestr.patch taken from
 upstream.
Checksums-Sha1:
 101f0bfb5ff14d18a31b01c02ff49e091e60ed86 2492 python-os-testr_1.0.0-5.dsc
 6171e2004d0bd4ee2d18ee50098a4a2d85200ab8 5500 
python-os-testr_1.0.0-5.debian.tar.xz
 de5e59bb6cfa4efe3158d83bfeac6e07947c92bd 10513 
python-os-testr_1.0.0-5_amd64.buildinfo
Checksums-Sha256:
 4cca7328ce0d4af4b28b7ce748e5e48ce37d14bf1034278ffd4cc359db702a3c 2492 
python-os-testr_1.0.0-5.dsc
 6bd050b80ce0d5a23ceb1580d8da4f05431f3cae5fe2dfe28831199553c160a2 5500 
python-os-testr_1.0.0-5.debian.tar.xz
 248da27ea6d27273ec49d6fa41a71206a7a9dfc0cb7b8d1686b11dde5faea344 10513 
python-os-testr_1.0.0-5_amd64.buildinfo
Files:
 f82dab2033d5c401cd14b65b88b284e8 2492 python optional 
python-os-testr_1.0.0-5.dsc
 55fcd63e37f4b3c0f6f6d52c94da7587 5500 python optional 
python-os-testr_1.0.0-5.debian.tar.xz
 14ff0ea2dea48cf1628caeb7b1601fda 10513 python optional 
python-os-testr_1.0.0-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAl1KgMsACgkQ1BatFaxr
Q/4cWA/+K2rCU7vqAqFC+V8j/C3gxfiOUDbI6xGfFG1YgUFtuZH2fEkKp5SfTJkh
2XXrRW/0bthi2U1Jq93NJsVHxlPTqctRYUksZxeP/xJFIGptQnvsnm0OZB+19O3I
ty7VrbINW2VOOkg/EUptElj/6dcgQjcud0DIZL6Gs/KBeolXeFoZjUHWoS+VzhlX
/apOW0+lyDo3chuNFAf+7RiYATee4X26robhiYOQ7CgNqM7ZbrTu2GaQV9c6/Rdy
2SdZtwaaji6Z307eKgpx8xeCdSlAy8n8y6xkroH+tw2G3Y4Huaog90k7dT1Min+n
7ZVMa+a2xfjqt/qLLypZst/b3weipHK3mujN6eWTyLV+twCfQHYEg0/e6qO8MX1r
FL/RPCM3niRUH9gon+K19ygt23fDiUWGsAsVxFC6UrjhoWY2cK2anADAvtJ9MiDH
02ptYNOgBiF9Ks0VNaNouvNLFEVELFhs/gl0/BB4C8IEETaY3gajEoOBncvr3JIY
pAYFiNguwP7FxgSSI9hPH70/3/95FtP0RwGC2VvczW3DwexLK0+5BBjycjMa2c2d
vc2dYvaKHVlDomh+IGZPSxfTPVzyz8EhIu115z+dZugS/ybl+g9F2beLoRnzI5nh
XZjviTEUsG0z4YObBC50BXUqk5c85TC/PeMs3vDEQPiMldxqxmM=
=VY5O
-END PGP SIGNATURE End Message ---

Processed: jython: add explicit dependency on openjdk-11-jre-headless

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + science-astronomy
Bug #934111 [jython] jython: add explicit dependency on openjdk-11-jre-headless
Added indication that 934111 affects science-astronomy

-- 
934111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934111
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#934108: marked as done (icinga2-bin fails to install)

[Debian Bug Tracking System]

Your message dated Wed, 07 Aug 2019 13:36:01 +
with message-id 
and subject line Bug#934108: fixed in icinga2 2.11.0~rc1-1~exp2
has caused the Debian Bug report #934108,
regarding icinga2-bin fails to install
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
934108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934108
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: icinga2
Version: 2.11.0~rc1-1~exp1
Severity: serious

Hi,

icinga2 fails to install due to a permission issue
(/etc/icinga2/features-* should be owned by nagios:nagions).

--snip--
Setting up icinga2-bin (2.11.0~rc1-1~exp1) ...
enabling default icinga2 features
Enabling feature checker. Make sure to restart Icinga 2 for these
changes to take effect.
critical/cli: Cannot enable feature 'checker'. Linking source
'../features-available/checker.conf' to target file
'/etc/icinga2/features-enabled/checker.conf' failed with error code 13,
"Permission denied".
Enabling feature notification. Make sure to restart Icinga 2 for these
changes to take effect.
critical/cli: Cannot enable feature 'notification'. Linking source
'../features-available/notification.conf' to target file
'/etc/icinga2/features-enabled/notification.conf' failed with error code
13, "Permission denied".
Enabling feature mainlog. Make sure to restart Icinga 2 for these
changes to take effect.
critical/cli: Cannot enable feature 'mainlog'. Linking source
'../features-available/mainlog.conf' to target file
'/etc/icinga2/features-enabled/mainlog.conf' failed with error code 13,
"Permission denied".
critical/cli: Cannot enable feature(s): checker notification mainlog
dpkg: error processing package icinga2-bin (--configure):
 installed icinga2-bin package post-installation script subprocess
returned error exit status 1
dpkg: dependency problems prevent configuration of icinga2:
 icinga2 depends on icinga2-bin (= 2.11.0~rc1-1~exp1); however:
  Package icinga2-bin is not configured yet.

dpkg: error processing package icinga2 (--configure):
 dependency problems - leaving unconfigured
Processing triggers for systemd (241-7) ...
Processing triggers for man-db (2.8.6-1) ...
Processing triggers for libc-bin (2.28-10) ...
Errors were encountered while processing:
 icinga2-bin
 icinga2
E: Sub-process /usr/bin/dpkg returned an error code (1)
--snap--

Regards,
Daniel
--- End Message ---
--- Begin Message ---
Source: icinga2
Source-Version: 2.11.0~rc1-1~exp2

We believe that the bug you reported is fixed in the latest version of
icinga2, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 934...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated icinga2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 07 Aug 2019 14:50:58 +0200
Source: icinga2
Architecture: source
Version: 2.11.0~rc1-1~exp2
Distribution: experimental
Urgency: medium
Maintainer: Debian Nagios Maintainer Group 

Changed-By: Bas Couwenberg 
Closes: 934108
Changes:
 icinga2 (2.11.0~rc1-1~exp2) experimental; urgency=medium
 .
   * Team upload.
   * Use /run instead of /var/run.
   * Set ownership of /etc/icinga2/features-enabled to nagios:nagios.
 (closes: #934108)
Checksums-Sha1:
 97202b219c192b1d4625440083a449c8585a783a 2838 icinga2_2.11.0~rc1-1~exp2.dsc
 c19f1663c33e389bd73ccb75fe4a7dead986cb8c 23040 
icinga2_2.11.0~rc1-1~exp2.debian.tar.xz
 412347fb78b4f4538c9b10cdcdbc05a85adb2ea6 16274 
icinga2_2.11.0~rc1-1~exp2_amd64.buildinfo
Checksums-Sha256:
 2bbfbb9ab3f6227ef06cf19108dd42a52c80dc24c4c7356042cedb7108e8a245 2838 
icinga2_2.11.0~rc1-1~exp2.dsc
 a982ec564aab5ac45b10833bc5b165d8d0ecca681fb9ee9f05f67827103461ad 23040 
icinga2_2.11.0~rc1-1~exp2.debian.tar.xz
 f656ff78e2e496413b90100f26a584c9eb65a4bddaaea4f2723cf42e9eb7dab9 16274 
icinga2_2.11.0~rc1-1~exp2_amd64.buildinfo
Files:
 c722058ccbab176f3d71013407af7031 2838 admin optional 
icinga2_2.11.0~rc1-1~exp2.dsc
 28fe45410cfd93613539edb6d03d3ab5 23040 admin optional 
icinga2_2.11.0~rc1-1~exp2.debian.tar.xz
 28027c6c8f266684ad251c4a4a68a6d9 16274 admin optional 
icinga2_2.11.0~rc1-1~exp2_amd64.buildinfo

-BEGIN PGP 

Processed: Bug#932247 marked as pending in postgresql

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #932247 [postgresql-11] ALTER TABLE statements causing "relation already 
exists" errors when some indexes exist
Ignoring request to alter tags of bug #932247 to the same tags previously set

-- 
932247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932247
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Bug#932247 marked as pending in postgresql

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #932247 [postgresql-11] ALTER TABLE statements causing "relation already 
exists" errors when some indexes exist
Ignoring request to alter tags of bug #932247 to the same tags previously set

-- 
932247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932247
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Bug#932247 marked as pending in postgresql

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #932247 [postgresql-11] ALTER TABLE statements causing "relation already 
exists" errors when some indexes exist
Ignoring request to alter tags of bug #932247 to the same tags previously set

-- 
932247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932247
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#932247: marked as pending in postgresql

[Christoph Berg]

Control: tag -1 pending

Hello,

Bug #932247 in postgresql reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/postgresql/postgresql/commit/0a93a35aa4354c3c383080a35672330f81c09eec


New upstream version.

* New upstream version.
  + Fixes regression in ALTER TABLE on multiple columns. (Closes: #932247)
  + Require schema qualification to cast to a temporary type when using
functional cast syntax (Noah Misch)
We have long required invocations of temporary functions to explicitly
specify the temporary schema, that is pg_temp.func_name(args). Require
this as well for casting to temporary types using functional notation,
for example pg_temp.type_name(arg). Otherwise it's possible to capture a
function call using a temporary object, allowing privilege escalation in
much the same ways that we blocked in CVE-2007-2138. (CVE-2019-10208)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/932247

Bug#932247: marked as pending in postgresql

[Christoph Berg]

Control: tag -1 pending

Hello,

Bug #932247 in postgresql reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/postgresql/postgresql/commit/69bff3c1e0f35486835e2a6dcb3307cfc0eabe26


New upstream version.

* New upstream version.
  + Fixes regression in ALTER TABLE on multiple columns. (Closes: #932247)
  + Require schema qualification to cast to a temporary type when using
functional cast syntax (Noah Misch)
We have long required invocations of temporary functions to explicitly
specify the temporary schema, that is pg_temp.func_name(args). Require
this as well for casting to temporary types using functional notation,
for example pg_temp.type_name(arg). Otherwise it's possible to capture a
function call using a temporary object, allowing privilege escalation in
much the same ways that we blocked in CVE-2007-2138. (CVE-2019-10208)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/932247

Bug#932247: marked as pending in postgresql

[Christoph Berg]

Control: tag -1 pending

Hello,

Bug #932247 in postgresql reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/postgresql/postgresql/commit/2d7e14938d972bf2385e90908fcf4dd22f24a3f3


New upstream version.

* New upstream version.
  + Fixes regression in ALTER TABLE on multiple columns. (Closes: #932247)
  + Require schema qualification to cast to a temporary type when using
functional cast syntax (Noah Misch)
We have long required invocations of temporary functions to explicitly
specify the temporary schema, that is pg_temp.func_name(args). Require
this as well for casting to temporary types using functional notation,
for example pg_temp.type_name(arg). Otherwise it's possible to capture a
function call using a temporary object, allowing privilege escalation in
much the same ways that we blocked in CVE-2007-2138. (CVE-2019-10208)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/932247

Bug#933128: Would you be willing to pass Parse::DebianChangelog upstream development to someone else?

[Axel Beckert]

Hi Guillem,

Guillem Jover wrote:
> > So some of us wonder if you would generally allow Debian Perl Team
> > members (or maybe even someone else) to also officially take over the
> > upstream development of Parse::DebianChangelog — as you seem to have
> > done for the packaging back in 2015. 
> 
> I'm not sure this makes much sense TBH? The modules in libdpkg-perl
> (Dpkg::Changelog) are the direct successors of the
> libparse-debianchangelog-perl codebase [C],

Oh, ok. I wasn't aware of this at all. And probably many more, too,
otherwise there wouldn't be so many packages around using 
libparse-debianchangelog-perl

> Some of the features got removed, to trim down dependencies, and the
> API adapted to match the rest of the libdpkg-perl codebase, but if
> the removed output formats are needed, or anything else seems
> suboptimal or worth improving/adding, I'm happy to work on those.

What I quickly checked a few weeks ago was if libdpkg-perl has an
equivalent of parsechangelog which is used in aptitude. But it hasn't,
so I didn't consider it to be a suitable replacement.

And your patch against aptitude (see https://bugs.debian.org/934135)
uses "perl -MDpkg::Changelog::Parse -e …" which probably works well,
but having a drop-in replacement for /usr/bin/parsechangelog which is
not in dpkg-dev would be nice.

Hmmm, what if we move dpkg-parsechangelog from dpkg-dev to
libdpkg-perl? I initially thought it would have a rather big impact
since many dependencies need to be changed from dpkg-dev to
libdpkg-perl, but actually dpkg-dev has a hard dependency on
libdpkg-perl. If that dependency is not only for dpkg-parsechangelog
(and hence would be gone with the move), the move probably could be a
rather smooth one.

Anyway, sounds as if a continuation of libparse-debianchangelog-perl
is indeed unnecessary if Dpkg::Changelog::Parse is that close.

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#934140: brightd does not fade

[Michael Gebetsroither]

Package: brightd
Version: 0.4.1-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

brightd does not fade because it wrongly thinks laptop is always on AC.

The problem is in the patch 
0002-Don-t-use-deprecated-proc-acpi-for-AC-detection.patch
|   FILE *ac = fopen("/sys/class/power_supply/AC/online", "r");
| ...
|   ac_state = fgetc(ac);
|   fclose(ac);
|   return ac_state;

In the kernel from debian buster the file opened contains '0' or '1',
the patch does not parse the character '0' but simple returns the
character casted to an int.
Which means the function isOnAC always returns true, which means brightd
currently does nothing, it never fades.

Output of brightd when on battery (or on AC, doesn't matter)
|brightd -w 5 -v
|Maximum brightness is 4437
|Opened X11 Display from ENV{DISPLAY}
|Opened a connection
|Would fade, but on AC
|Would fade, but on AC
|Would fade, but on AC
| ...

best regards,
gebi

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

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

Versions of packages brightd depends on:
ii  libc6 2.28-10
ii  libx11-6  2:1.6.7-1
ii  libxss1   1:1.2.3-1

brightd recommends no packages.

brightd suggests no packages.

-- no debconf information

Processed: malfunctions due to being confused about git repository

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 9.5
Bug #934126 [dgit] malfunctions due to being confused about git repository
Marked as fixed in versions dgit/9.5.

-- 
934126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934126
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#934126: malfunctions due to being confused about git repository

[Ian Jackson]

Package: dgit
Version: 9.6
Control: fixed -1 9.5
Severity: serious

check_for_git always returns falseish for the Debian repos because of
a bug in dgit's handling of WWW::Curl's (correct) behaviour with
CURLOPT_NOBODY.

As a result, dgit fetch/clone sometimes fails to stitch in the earlier
dgit push history from dgit-repos:

One possible symptom is this something like this:

synthesised git commit from .dsc 16.3.0-2.1
3ace5cdf35eed10c4a0b83b3f2804882b6343840 
a330c7d56988941b518afbd479563698e3056d85 dgit repo server tip (last push) ? at 
/usr/bin/dgit line 3467.
main::__ANON__("3ace5cdf35eed10c4a0b83b3f2804882b6343840", "dgit repo 
server tip (last push)") called at /usr/bin/dgit line 3470
main::fetch_from_archive() called at /usr/bin/dgit line 3898
main::fetch_one() called at /usr/bin/dgit line 3918
main::dofetch() called at /usr/bin/dgit line 4886
main::cmd_fetch() called at /usr/bin/dgit line 7798

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#932584: Epydoc and Pydoctor

[Ian Jackson]

Kenneth Pronovici writes ("Re: Epydoc and Pydoctor"):
> I decided to NMU and uploaded a few days ago, so things are in good
> shape now, I think.  You can integrate my changes whenever you have
> time.  Thanks for confirming that your ok with the NMU.  I was
> hoping you would be.

Thank you for this.  However, you did an upload with binaries and it
therefore isn't migrating.  I will do a source-only upload right away.

Regards,
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.

Processed: Re: biobambam2: /usr/bin/fastaexplode is already provided by exonerate

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream
Bug #933937 [biobambam2] biobambam2: /usr/bin/fastaexplode is already provided 
by exonerate
Added tag(s) upstream.
> forwarded -1 https://gitlab.com/german.tischler/biobambam2/issues/83, Guy 
> St.C. Slater 
Bug #933937 [biobambam2] biobambam2: /usr/bin/fastaexplode is already provided 
by exonerate
Set Bug forwarded-to-address to 
'https://gitlab.com/german.tischler/biobambam2/issues/83, Guy St.C. Slater 
'.

-- 
933937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933937
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#933937: biobambam2: /usr/bin/fastaexplode is already provided by exonerate

[Andreas Tille]

Control: tags -1 upstream
Control: forwarded -1 https://gitlab.com/german.tischler/biobambam2/issues/83, 
Guy St.C. Slater 

Hi Guy,

as you can read in the bug report[1] against exonerate and biobambam2
there is a name space conflict between these two packages and thus the
Debian packages can not be installed simultaneously.  I have reported
that issue to biobambam2[2] to enable some educated decision between you
two parties what might be the best solution to solve the name space
conflict.

Kind regards

   Andreas.

[1] https://bugs.debian.org/933937
[2] https://gitlab.com/german.tischler/biobambam2/issues/83

-- 
http://fam-tille.de

Bug#933930: [Pkg-utopia-maintainers] Bug#933930: Bug#933930: Bug#933930: network-manager: Ethernet connection no longer works

[Michael Biebl]

Am 07.08.19 um 11:24 schrieb Vincent Lefevre:
> On 2019-08-06 22:24:49 +0200, Michael Biebl wrote:
>> Ok, so the current state of affairs is:
>>
>> dhcp=dhclient works always
>> dhcp=internal (the default) fails (sometimes)
>>
>> ?
> 
> That's right.
> 
> Here are more complete logs for dhcp=internal, first those
> corresponding to a success, then those corresponding to a
> failure.


I quickly pinged upstream about this. His reply:


 mbiebl_, Unclear what is not working. Could you ask for
level=TRACE logs? See
https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/contrib/fedora/rpm/NetworkManager.conf#n28
, preferably without ratelimiting from journal (see also the comment)

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



signature.asc
Description: OpenPGP digital signature

Bug#931896: grub-efi-amd64: symbol `grub_file_filters` not found

[J. Pietschmann]

Hi,

I have a similar problem with plain grub-pc (no EFI)
I use the first two HDD as an MDM array and installed grub
on both /dev/sda and /dev/sdb. A few weeks ago the first HDD
failed and was replaced, and I used
 update-grub
 grub-install /dev/sda
afterwards and could reboot the computer without problems. The next
reboot after the upgrade to grub 2.04 failed with
 symbol `grub_file_filters` not found
The grub update didn't show anything interesting on the console or
dpgk.log
The problem appears to be that grub 2.04 uses only devices by disk-id
and didn't install on /dev/sda even though grub 2.02 did.
Fortunately
 dpkg-reconfigure grub-pc
fixes the calamity.
What's the preferred way to reinstall grub on a new disk with 2.04?
Preferrably non-interactive/scriptable.

Cheers

Bug#931714: marked as done (node-request-promise: autopkgtest fails)

[Debian Bug Tracking System]

Your message dated Wed, 07 Aug 2019 09:51:22 +
with message-id 
and subject line Bug#931714: fixed in node-request-promise 4.2.4-3
has caused the Debian Bug report #931714,
regarding node-request-promise: autopkgtest fails
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
931714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-request-promise
Version: 4.2.4-1
Severity: important

Both autopkgtest tests fail with the following message:

8<
autopkgtest [16:10:50]: test require: [---

###
### The "request" library is not installed automatically anymore.
### But is a dependency of "request-promise".
### Please install it with:
### npm install request --save
###

/usr/share/nodejs/request-promise/lib/rp.js:23
throw err;
^

Error: Cannot find module 'request'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:581:15)
at Function.Module._load (internal/modules/cjs/loader.js:507:25)
at Module.require (internal/modules/cjs/loader.js:637:17)
at require (internal/modules/cjs/helpers.js:22:18)
at /usr/share/nodejs/request-promise/lib/rp.js:11:16
at module.exports (/usr/lib/nodejs/stealthy-require/lib/index.js:62:23)
at Object. (/usr/share/nodejs/request-promise/lib/rp.js:10:19)
at Module._compile (internal/modules/cjs/loader.js:689:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
at Module.load (internal/modules/cjs/loader.js:599:32)
at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
at Function.Module._load (internal/modules/cjs/loader.js:530:3)
at Module.require (internal/modules/cjs/loader.js:637:17)
at require (internal/modules/cjs/helpers.js:22:18)
at [eval]:1:1
at Script.runInThisContext (vm.js:96:20)
at Object.runInThisContext (vm.js:303:38)
at Object. ([eval]-wrapper:6:22)
at Module._compile (internal/modules/cjs/loader.js:689:30)
at evalScript (internal/bootstrap/node.js:587:27)
at startup (internal/bootstrap/node.js:265:9)
at bootstrapNodeJSCore (internal/bootstrap/node.js:743:3)
>8

Please fix it
--- End Message ---
--- Begin Message ---
Source: node-request-promise
Source-Version: 4.2.4-3

We believe that the bug you reported is fixed in the latest version of
node-request-promise, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 931...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated node-request-promise 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 07 Aug 2019 11:28:57 +0200
Source: node-request-promise
Architecture: source
Version: 4.2.4-3
Distribution: unstable
Urgency: medium
Maintainer: Xavier Guimard 
Changed-By: Xavier Guimard 
Closes: 931714
Changes:
 node-request-promise (4.2.4-3) unstable; urgency=medium
 .
   * Team upload
   * Patch upstream test to call mocha directly
   * Switch install to pkg-js-tools and enable upstream test
   * Add debian/nodejs/build to avoid future failure with pkg-js-tools auto
 build
   * Move node-request in dependencies (Closes: #931714)
   * Drop unneeded version constraints from (build) dependencies
Checksums-Sha1: 
 117fdf2c982ef445f43f14e251ed5cd1e1300685 2518 node-request-promise_4.2.4-3.dsc
 40fd5841f544c467e0cddc01962520463f0d5c06 2976 
node-request-promise_4.2.4-3.debian.tar.xz
Checksums-Sha256: 
 fbc954167e6a1a651f58fc6a8b4be23fa5a61139073617c97091b4222f2aa0be 2518 
node-request-promise_4.2.4-3.dsc
 52350ae57de151e1a22d1f8cf6f6d9cb25f42cbaeaa6e356c4dab1d8f6c209cc 2976 
node-request-promise_4.2.4-3.debian.tar.xz
Files: 
 c03b780064209f583a17583e7f80332c 2518 javascript optional 
node-request-promise_4.2.4-3.dsc
 7be2d555324720fe690d58352bdca496 2976 javascript optional 
node-request-promise_4.2.4-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl1KmnEACgkQ9tdMp8mZ
7umc1A/9F/VjOSZKooAG6zHnLvVqsJ2KKg5uchm2/r823B3JjG+r/Xwilp4I+3eT

Bug#934111: jython: add explicit dependency on openjdk-11-jre-headless

[Andreas Beckmann]

On 07/08/2019 10.02, Emmanuel Bourg wrote:
> Hi Andreas,
> 
> Le 07/08/2019 à 08:08, Andreas Beckmann a écrit :
> 
>> in order to fix some upgrade issues from stretch to buster due to the
>> dependency cycle between default-jre-headless, openjdk-11-jre-headless
>> and ca-certificates-java (#929685), please add an explicit dependency on
>> openjdk-11-jre-headless to jython as a workaround.
> 
> Could you elaborate a bit on the upgrade issue you encountered? It looks

see #929685 for details

configuration order is

  ca-certificates-java
  default-jre-headless
  jython
  jython-stilts (FAILS)
  openjdk-11-jre-headless

> a bit arbitrary to change the JRE dependency on jython to work around
> the ca-certificates-java dependency cycle, and not on the other
> applications depending on the JRE.

jython bumped the java dependency to >= 9 which is not satisfiable in
stretch, while other packages seem to still work with java 8

There are no other packages triggering this problem in piuparts.
Given that noone reacted to #929685, I'm trying to find a minimal
workaround suitable for stable.

> How did you get this exception? This was triggered by running Java 11
> compiled code on Java 8, it's another issue we have to fix.

default-jre-headless being configured, providing java-9,
while the openjdk links still point to java-8

Andreas

Bug#931896: grub-efi-amd64: symbol `grub_file_filters` not found

[Colin Watson]

On Wed, Aug 07, 2019 at 11:19:55AM +0200, J. Pietschmann wrote:
> The problem appears to be that grub 2.04 uses only devices by disk-id
> and didn't install on /dev/sda even though grub 2.02 did.

No, that's incorrect.  GRUB 2.02 behaved just the same way; you just
didn't notice the problem because you happened to have a GRUB core image
installed on /dev/sda that was compatible with the GRUB modules that you
had installed at the time.  Things were already broken but you just
didn't know it yet.

I've said this in this bug already, but I'll keep repeating it: this is
*not* a behaviour change in GRUB 2.04.

> Fortunately
>  dpkg-reconfigure grub-pc
> fixes the calamity.
> What's the preferred way to reinstall grub on a new disk with 2.04?
> Preferrably non-interactive/scriptable.

"dpkg-reconfigure grub-pc" is preferred.  Doing this noninteractively is
possible but fiddly: you'd need to figure out the by-id paths for your
disks and then do something like this (obviously substituting the
correct by-id paths rather than the example ones I've used):

  echo 'grub-pc grub-pc/install_devices multiselect /dev/disk/by-id/ata-foo 
/dev/disk/by-id/ata-bar' | sudo debconf-set-selections
  sudo dpkg-reconfigure --unseen-only grub-pc

(I would not disagree that this should be easier; but this has been the
case for a long time, and isn't new in 2.04.)

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

Bug#932247: marked as pending in postgresql

[Christoph Berg]

Control: tag -1 pending

Hello,

Bug #932247 in postgresql reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/postgresql/postgresql/commit/ce4e5d84424158a6d30ab2b16d091ae4af37c2f0


New upstream version.

* New upstream version.
  + Fixes regression in ALTER TABLE on multiple columns. (Closes: #932247)
  + Require schema qualification to cast to a temporary type when using
functional cast syntax (Noah Misch)
We have long required invocations of temporary functions to explicitly
specify the temporary schema, that is pg_temp.func_name(args). Require
this as well for casting to temporary types using functional notation,
for example pg_temp.type_name(arg). Otherwise it's possible to capture a
function call using a temporary object, allowing privilege escalation in
much the same ways that we blocked in CVE-2007-2138. (CVE-2019-10208)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/932247

Processed: Bug#932247 marked as pending in postgresql

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #932247 [postgresql-11] ALTER TABLE statements causing "relation already 
exists" errors when some indexes exist
Added tag(s) pending.

-- 
932247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932247
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#931875: ping for autorm

[Jonathan Carter]

This was a mistake on my part, this package should have been uploaded to
experimental. Pinging to avoid autorm in meantime.

Bug#934026: python-django: CVE-2019-14232 CVE-2019-14233 CVE-2019-14234 CVE-2019-14235

[Sébastien Delafond]

On 06/08 10:20, Chris Lamb wrote:
> Security team (added to CC), would you be interested in uploads for
> buster (currently 1:1.11.22-1~deb10u1) and stretch (currently
> 1:1.10.7-2+deb9u5)?

Hi Chris,

yes, thank you. Can you email us debdiffs ? I'll then take care of the
review and DSAs.

Cheers,

-- 
Seb

Bug#933930: [Pkg-utopia-maintainers] Bug#933930: Bug#933930: Bug#933930: network-manager: Ethernet connection no longer works

[Vincent Lefevre]

On 2019-08-07 12:57:37 +0200, Michael Biebl wrote:
>  mbiebl_, Unclear what is not working. Could you ask for
> level=TRACE logs? See
> https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/contrib/fedora/rpm/NetworkManager.conf#n28
> , preferably without ratelimiting from journal (see also the comment)

I've attached an archive with 3 log files of tests with the
internal dhcp client:

  * nm-1.19.90-failing (with network-manager 1.19.90-2).
I had to wait for more that one minute to get an IP address, and this
was not even the correct one (I normally have a fixed IP address).
Sometimes, this is worse, e.g. after each of the following reboots
  REBOOT in 1s
  REBOOT in 2s
  REBOOT in 4s
  REBOOT in 8s
  REBOOT in 16s
  REBOOT in 32s
  REBOOT in 1min 4s
I got "NAK: requested address not available". I did not wait longer.

  * nm-1.19.90-working (with network-manager 1.19.90-2).
I got the correct IP address (140.77.13.17) after 5 seconds.
This is OK.

  * nm-1.20.0-failing (with network-manager 1.20.0-1).
After each of the following reboots
  REBOOT in 1s
  REBOOT in 2s
  REBOOT in 4s
  REBOOT in 8s
  REBOOT in 16s
  REBOOT in 32s
  REBOOT in 1min 4s
I got "NAK: requested address not available". I did not wait longer.
I tried several times and could not make it work.
Still no issues with dhcp=dhclient.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


nm-dhcp.tar.xz
Description: Binary data

Bug#933128: libparse-debianchangelog-perl: Unsuitable for Bullseye unless someone becomes upstream

[Guillem Jover]

Hi!

On Sat, 2019-07-27 at 12:20:00 -0300, intrigeri wrote:
> gregor herrmann:
> > In dpt-new-upstream we're using Dpkg::Changelog::Debian from
> > libdpkg-perl, which might help here as well.

> Oh, this is very interesting, thanks! I had taken a look at that
> module, but from the documentation I understood it only gives us "the
> number of changelog entries that have been parsed with success", so
> I had discarded this option.

If the documantion was not clear, I'd be happy to try to improve it so
that other people do not get this impression too. Could you cover a bit
what lead you to that conclusion?

> I'm very glad I was mislead. It looks like Dpkg::Changelog{,::*} are
> sufficient for many, if not most, use cases of Parse::DebianChangelog :)
> We might have to check what API is public and supported, and improve
> the documentation accordingly: for example, the "load" method that
> our new-upstream script uses does not seem to be documented anywhere.

Right (see my other mail), given that it's a direct successor, it
should cover almost everything, except for example the output formats
that got axed.

Hmm about the load() method, it seems I removed that because this
class does not implement the parse() method which load() requires,
when trying to clarify and document all the inherited methods in
commit 853f59ec0468f72fa29811a8fe48fad91fab6083. Thanks, will fix! :)

BTW, currently the preferred way to parse a changelog file is IMO to
use Dpkg::Changelog::Parse, as that will make sure to handle possible
custom formatters. I'm not entirely happy with this interface, because
it seems obviously less discoverable than just creating a new
Dpkg::Changelog (or Dpkg::Changelog::Debian), but merging it into the
base class' new() does not seem right either, but maybe as another
constructor method… :)

Thanks,
Guillem

Bug#933128: Would you be willing to pass Parse::DebianChangelog upstream development to someone else?

[Guillem Jover]

Hi!

On Sun, 2019-07-28 at 22:38:29 +0200, Axel Beckert wrote:
> the Debian Perl Team maintained libparse-debianchangelog-perl for
> quite some years now using debian-specific patches against your
> upstream version 1.2.0 from http://www.djpig.de/software/.
> 
> Being sick of doing upstream work in form of debian-specific patches,
> the Debian Perl Team is currently trying to get rid of
> libparse-debianchangelog-perl completely (see
> https://bugs.debian.org/933128) which again requires changes in quite
> some other packages including prominent ones like lintian,
> dh-make-perl and aptitude, see
> https://udd.debian.org/cgi-bin/bts-usertags.cgi?tag=libparse-debian-changelog-perl-removal=debian-perl%40lists.debian.org
> (aptitude still missing there).
> 
> So some of us wonder if you would generally allow Debian Perl Team
> members (or maybe even someone else) to also officially take over the
> upstream development of Parse::DebianChangelog — as you seem to have
> done for the packaging back in 2015. 

I'm not sure this makes much sense TBH? The modules in libdpkg-perl
(Dpkg::Changelog) are the direct successors of the
libparse-debianchangelog-perl codebase [C], and is the code that has
seen continued development.

Some of the features got removed, to trim down dependencies, and the
API adapted to match the rest of the libdpkg-perl codebase, but if
the removed output formats are needed, or anything else seems
suboptimal or worth improving/adding, I'm happy to work on those.

  [C] 


Thanks,
Guillem

Bug#933585: marked as done (BD on texlive-generic-extra which isn't build anymore and isn't in bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 07 Aug 2019 14:49:40 +
with message-id 
and subject line Bug#933585: fixed in pyx3 0.15-2
has caused the Debian Bug report #933585,
regarding BD on texlive-generic-extra which isn't build anymore and isn't in 
bullseye
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
933585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933585
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: breathe
Version: 4.11.1-1
Severity: serious
Tags: ftbfs sid bullseye

Recently the texlive-base package has stopped building the transitional
package texlive-generic-extra. This is an issue for your package as it
build-depends on it. Please update the building of your package to use
texlive-plain-generic instead.

Unfortunately the migration software doesn't detected this kind of
situation yet, so your package also FTBFS in bullseye since 2019-07-16.

Paul





signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: pyx3
Source-Version: 0.15-2

We believe that the bug you reported is fixed in the latest version of
pyx3, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 933...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stuart Prescott  (supplier of updated pyx3 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 08 Aug 2019 00:28:17 +1000
Source: pyx3
Architecture: source
Version: 0.15-2
Distribution: unstable
Urgency: medium
Maintainer: Stuart Prescott 
Changed-By: Stuart Prescott 
Closes: 933585
Changes:
 pyx3 (0.15-2) unstable; urgency=medium
 .
   * Stop build-depending on texlive-generic-extra which has vanished
 (Closes: #933585).
Checksums-Sha1:
 94eac890773be8469808aa974dcade967b971809 2287 pyx3_0.15-2.dsc
 b28c407d9b7a22c64cd3dd788fe5ed82dca86fbb 17660 pyx3_0.15-2.debian.tar.xz
 4d913264ea11669234b00356267000f048c11ced 10907 pyx3_0.15-2_amd64.buildinfo
Checksums-Sha256:
 96db05aa1f4f49b201ed2b85de4a8d21597f12c8cf3118603fb8f354b186dc7d 2287 
pyx3_0.15-2.dsc
 ace88bc14b9ec0483c18df0662fdb76ce5581306c57eaf8ceb8ddfc60097c12f 17660 
pyx3_0.15-2.debian.tar.xz
 14e7e972319f32a50409e26dc3761e3747e7313b564263c06fdd33947d3dccab 10907 
pyx3_0.15-2_amd64.buildinfo
Files:
 75ad606ee450c6436508eedef795dca4 2287 python optional pyx3_0.15-2.dsc
 2a647a2930b00e67e93e13397d4a7d1d 17660 python optional 
pyx3_0.15-2.debian.tar.xz
 fde129b36645a5487af48b4dae38f62d 10907 python optional 
pyx3_0.15-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkOLSwa0Uaht+u4kdu8F+uxOW8vcFAl1K4NEACgkQu8F+uxOW
8vddiQ//TSfug0VJM/z+yxiycOX4LqhXrSvk4ulTNE246iJG/feAf2IVa9nTB1LM
JxRLq9ABRdGiR9In78sIVsZFmbAPLVh+BmDw8F4JruHLa8pw1ndUta+84WITpTGr
aa+vD0k9VjCHRneBSpah+boGYR0mskTLkaib14x1iawkkZM5eFu66DuMIP1WqVeB
gjecFz3uuIPpSdBqdL9+T5W+Xn90No1R1Xz09diRz0vN509dTu2MYCNKbDczXu/B
jXTRbnmQpoMH6BOWR3PZhW1py8J8s+oMMyGZaE6kaJgpOQafqTauzzLcJaeW0ucm
CtJBBhda8+XOt7LSMyGIWvUETb4AL8Oi48TMXtIuSMoJdQGKu8HD849OlPP3e6gE
NTfEIV9CAHfUcQR2ToACB0Ollgf4ILva7Z6B1MRGpHQutZtc8e9hB/WkdoqBROFX
zoPS8yv3lQe9//YZeAYsUN0mGq5/+6jYCqyw2zVUzCfH419Cz9k2ZoVupSckAQR0
MoHp2KDMCrA3cCUd7moBLTvaYWTHT/PnrqHLf3zAu/3pDNLtWP7V3v9cfXCBgmqV
bIIMtGD+iY5vuMsl3amDOpDF8jlISKaF+FHHn1fBUysaZlEvxUOVWsHvbbP4WXsn
ytF2+SUPUyYET48x0ynylw1aetI278gnTrtoAKId2s9fS451qWE=
=/7gD
-END PGP SIGNATURE End Message ---

Bug#934167: php-oauth 2.0.2 is incompatible with PHP 7.3: signature_invalid errors

[Christian Weiske]

Package: php-oauth
Version: 2.0.2+1.2.3-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Debian unstable currently ships PHP 7.3, and php-oauth 2.0.2.
With PHP 7.3, internal structures changed and their use needs to be adjusted
in the oauth extension.

There is a fix for this already in php-oauth 2.0.4:
http://git.php.net/?p=pecl/web_services/oauth.git;a=commit;h=0828b70df7606b599785b3de1c15248d3e463b95

The problem that actually occurs is the following:
When validating an incoming OAuth request with 
OAuthProvider:checkOAuthRequest(),
it will always return a failure:

oauth_problem=signature_invalid_sbs=POST&%01%3A%2F%2F%01%01_callback...

"debug_sbs" shows the data that are used for signature creation, and the second 
part
(after the first &) should be host + path of the request.
Here we see NUL byte, ://, and another NUL byte.

Please provide php-oauth versino 2.0.4.

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

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

Versions of packages php-oauth depends on:
ii  libapache2-mod-php7.3 [phpapi-20180731]  7.3.6-1
ii  libc62.28-10
ii  php-common   2:69
ii  php7.3-cli [phpapi-20180731] 7.3.6-1
ii  php7.3-phpdbg [phpapi-20180731]  7.3.6-1

php-oauth recommends no packages.

php-oauth suggests no packages.

-- no debconf information

Bug#911078: triplea: Fails to start with NullPointerException

[Dan Van Atta]

Apologies for the long delay, updates to Debian are a deeper issue than I
initially realized. TripleA has had a history of maintenance overhead
problems, seeing the Debian fork has me realize that it is a fork with its
own unique code and in effect would be a second codebase to maintain. I do
not think it's sustainable to maintain two code bases as has been done. Of
note, it's difficult sustaining development in the core codebase itself and
there's been a lot of effort to improve efficiency there in order to make
progress in substantially improving the game.

With that said, I think the solution is to try and incorporate the Debian
patches into the main codebase to the largest extent possible. In that case
the Debian version could be a clean fork of the main codebase and would
remove the second maintenance effort. I've opened a tracking issue in the
Github issue queue to discuss this amongst the TripleA developers and
greater community: https://github.com/triplea-game/triplea/issues/4933.
Input and coordination on that effort from the Debian side would be very
welcome. While I'm not sure if we can make the Debian version a 'true'
fork, having the main repo and Debian fork mirror as closely as possible
should reduce redundant maintenance efforts and make this process more
sustainable.

Bug#934160: nfs-common: Umask ignored, all files created world-writable on NFS

[John Goerzen]

Package: nfs-common
Version: 1:1.3.4-2.5
Severity: grave
Tags: security
Justification: user security hole

I have an NFS client and server both running Debian.  I recently
upgraded them both to buster.

I discovered today that the regular process umask has been ignored on
my nfs mounts since the upgrade, and all files and directories are
being created a+rw.

On the client, the fstab fstype is nfs4 and the mount options are
hard,intr,bg,noatime.  The relevant datasets are exported
rw,no_root_squash,no_subtree_check from the server.

In researching this, I stumbled across
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1779736 and
https://bugzilla.redhat.com/show_bug.cgi?id=1667761 which indicate the
problem is present elsewhere as well.  Adding vers=4.1 to my client's
mount options completely resolved the problem.  (Though now I have a
couple weeks' worth of files with unintentionally open permissions to
wade through.)

I tagged this as security and grave because it opens up quite a few
scenarios for users to receive privileges they shouldn't, and for
other potential mischief (placing malicious executables in
world-writable directories, etc).

The server is indeed running zfs with its default acltype setting
(off).  As the Ubuntu bug report shows, mounting with noacl doesn't
resolve the behavior either.  The RedHat bug occurred with an OpenWRT
server, unlikely to be running zfs.  I do not believe this bug should
be pinned down to ZFS; a filesystem not supporting ACLs should not
result in umask 0 for all clients in any scenario.

-- Package-specific info:
-- rpcinfo --
   program vers proto   port  service
104   tcp111  portmapper
103   tcp111  portmapper
102   tcp111  portmapper
104   udp111  portmapper
103   udp111  portmapper
102   udp111  portmapper
-- /etc/default/nfs-common --
NEED_STATD=
STATDOPTS=
NEED_IDMAPD=
NEED_GSSD=
-- /etc/idmapd.conf --
[General]
Verbosity = 0
Pipefs-Directory = /run/rpc_pipefs
[Mapping]
Nobody-User = nobody
Nobody-Group = nogroup

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

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

Versions of packages nfs-common depends on:
ii  adduser 3.118
ii  keyutils1.6-6
ii  libc6   2.28-10
ii  libcap2 1:2.25-2
ii  libcom-err2 1.44.5-1
ii  libdevmapper1.02.1  2:1.02.155-3
ii  libevent-2.1-6  2.1.8-stable-4
ii  libgssapi-krb5-21.17-3
ii  libk5crypto31.17-3
ii  libkeyutils11.6-6
ii  libkrb5-3   1.17-3
ii  libmount1   2.33.1-0.1
ii  libnfsidmap20.25-5.1
ii  libtirpc3   1.1.4-0.4
ii  libwrap07.6.q-28
ii  lsb-base10.2019051400
ii  rpcbind 1.2.5-0.3
ii  ucf 3.0038+nmu1

Versions of packages nfs-common recommends:
ii  python  2.7.16-1

Versions of packages nfs-common suggests:
pn  open-iscsi  
pn  watchdog

-- no debconf information

Bug#934159: metview: FTBFS after new magics++

[Gianfranco Costamagna]

Source: metview
Version: 5.3.0-3
Severity: serious
tags: patch

Hello, magics++ changed interpretAsMatrix prototype, and now metview is FTBFS.

The new upstream release has already a fix, but I'm posting a minimal debdiff 
here.

Also, new metview changed the METVIEW_EXTRA_INCLUDES variable, so also a change 
in rules file is needed now.


diff -Nru metview-5.3.0/debian/changelog metview-5.3.0/debian/changelog
--- metview-5.3.0/debian/changelog  2019-07-18 16:30:29.0 +0200
+++ metview-5.3.0/debian/changelog  2019-08-07 17:13:08.0 +0200
@@ -1,3 +1,10 @@
+metview (5.3.0-4) unstable; urgency=medium
+
+  * debian/rules: fixup includes directive for terralib
+  * Cherry-pick upstream build fix (Closes: #-1)
+
+ -- Gianfranco Costamagna   Wed, 07 Aug 2019 
17:13:08 +0200
+
 metview (5.3.0-3) unstable; urgency=medium

   * Standards-Version: 4.4.0
diff -Nru metview-5.3.0/debian/patches/fix-build-new-magics.patch 
metview-5.3.0/debian/patches/fix-build-new-magics.patch
--- metview-5.3.0/debian/patches/fix-build-new-magics.patch 1970-01-01 
01:00:00.0 +0100
+++ metview-5.3.0/debian/patches/fix-build-new-magics.patch 2019-08-07 
17:13:07.0 +0200
@@ -0,0 +1,16 @@
+Description: Cherry-pick upstream fix for the metview build.
+
+Last-Update: 2019-08-07
+
+--- metview-5.3.0.orig/src/Reprojection/ReprojectService.cc
 metview-5.3.0/src/Reprojection/ReprojectService.cc
+@@ -57,7 +57,8 @@ ReprojectService::execute()
+ 
+ 
+ magics::Matrix *matrix = 0;
+-gribInterpreter.interpretAsMatrix(grib, );
++gribInterpreter.interpretAsMatrix(grib);
++matrix = grib.u();
+ if (!matrix)
+ {
+ MagLog::dev() << "ERROR: interpretAsMatrix failed on file " << 
gribIn_ << "\n";
diff -Nru metview-5.3.0/debian/patches/series 
metview-5.3.0/debian/patches/series
--- metview-5.3.0/debian/patches/series 2019-07-18 16:30:29.0 +0200
+++ metview-5.3.0/debian/patches/series 2019-08-07 17:12:51.0 +0200
@@ -12,3 +12,4 @@
 syserrlist.patch
 qt5-transition.patch
 g++14.patch
+fix-build-new-magics.patch
diff -Nru metview-5.3.0/debian/rules metview-5.3.0/debian/rules
--- metview-5.3.0/debian/rules  2019-07-18 16:30:29.0 +0200
+++ metview-5.3.0/debian/rules  2019-08-07 17:13:08.0 +0200
@@ -72,7 +72,7 @@
-DMETVIEW_SITE=debian  \
-DCMAKE_BUILD_TYPE=Release \
-DMETVIEW_EXTRA_LIBRARIES='terralib -lemosR64 -leccodes 
-leckit' \
-   -DMETVIEW_EXTRA_INCLUDES='/usr/include/terralib/kernel' \
+   -DMETVIEW_EXTRA_INCLUDE_DIRS='/usr/include/terralib/kernel' \
-DMAGICS_HAVE_METVIEW=True \
diff -Nru metview-5.3.0/debian/changelog metview-5.3.0/debian/changelog
--- metview-5.3.0/debian/changelog  2019-07-18 16:30:29.0 +0200
+++ metview-5.3.0/debian/changelog  2019-08-07 17:13:08.0 +0200
@@ -1,3 +1,10 @@
+metview (5.3.0-4) unstable; urgency=medium
+
+  * debian/rules: fixup includes directive for terralib
+  * Cherry-pick upstream build fix (Closes: #-1)
+
+ -- Gianfranco Costamagna   Wed, 07 Aug 2019 
17:13:08 +0200
+
 metview (5.3.0-3) unstable; urgency=medium

   * Standards-Version: 4.4.0
diff -Nru metview-5.3.0/debian/patches/fix-build-new-magics.patch 
metview-5.3.0/debian/patches/fix-build-new-magics.patch
--- metview-5.3.0/debian/patches/fix-build-new-magics.patch 1970-01-01 
01:00:00.0 +0100
+++ metview-5.3.0/debian/patches/fix-build-new-magics.patch 2019-08-07 
17:13:07.0 +0200
@@ -0,0 +1,16 @@
+Description: Cherry-pick upstream fix for the metview build.
+
+Last-Update: 2019-08-07
+
+--- metview-5.3.0.orig/src/Reprojection/ReprojectService.cc
 metview-5.3.0/src/Reprojection/ReprojectService.cc
+@@ -57,7 +57,8 @@ ReprojectService::execute()
+ 
+ 
+ magics::Matrix *matrix = 0;
+-gribInterpreter.interpretAsMatrix(grib, );
++gribInterpreter.interpretAsMatrix(grib);
++matrix = grib.u();
+ if (!matrix)
+ {
+ MagLog::dev() << "ERROR: interpretAsMatrix failed on file " << 
gribIn_ << "\n";
diff -Nru metview-5.3.0/debian/patches/series 
metview-5.3.0/debian/patches/series
--- metview-5.3.0/debian/patches/series 2019-07-18 16:30:29.0 +0200
+++ metview-5.3.0/debian/patches/series 2019-08-07 17:12:51.0 +0200
@@ -12,3 +12,4 @@
 syserrlist.patch
 qt5-transition.patch
 g++14.patch
+fix-build-new-magics.patch
diff -Nru metview-5.3.0/debian/rules metview-5.3.0/debian/rules
--- metview-5.3.0/debian/rules  2019-07-18 16:30:29.0 +0200
+++ metview-5.3.0/debian/rules  2019-08-07 17:13:08.0 +0200
@@ -72,7 +72,7 @@
-DMETVIEW_SITE=debian  \
-DCMAKE_BUILD_TYPE=Release \
-DMETVIEW_EXTRA_LIBRARIES='terralib -lemosR64 -leccodes 
-leckit' \
-   -DMETVIEW_EXTRA_INCLUDES='/usr/include/terralib/kernel' \
+   -DMETVIEW_EXTRA_INCLUDE_DIRS='/usr/include/terralib/kernel' \

Bug#914333: pdfproctools: fails to install (conflict with origami-pdf)

[Thomas Dreibholz]

Hi,

the bug is fixed in the current version of NetPerfMeter. I created an
up-to-date package on the mentors.debian.net:
https://mentors.debian.net/package/netperfmeter . It needs a Debian
sponsor for upload.

On Thu, 22 Nov 2018 09:37:31 +0100 Jacek Politowski  wrote:

> Package: pdfproctools
> Version: 1.8.0-1
> Severity: important
>
> Dear Maintainer,
>
> pdfproctools fails to install due to conflicting
"/usr/bin/pdfmetadata" file
> which exists also in "origami-pdf" package.
>
> -- 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=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8),
LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages pdfproctools depends on:
> ii ghostscript 9.26~dfsg-1
> ii libpdf-api2-perl 2.033-1
> ii perl 5.28.0-4
> ii qpdf 8.2.1-1
>
> pdfproctools recommends no packages.
>
> pdfproctools suggests no packages.
>
>

-- 
Best regards / Mit freundlichen Grüßen / Med vennlig hilsen

===
 Thomas Dreibholz

 Simula Research Laboratory A/S
 SimulaMet — Simula Metropolitan Centre for Digital Engineering
 Centre for Resilient Networks and Applications
 Pilestredet 52
 0167 Oslo, Norway
---
 E-Mail: dre...@simula.no
 Homepage:   http://simula.no/people/dreibh
===




signature.asc
Description: OpenPGP digital signature

Processed: tagging 934171

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 934171 + sid bullseye
Bug #934171 [src:sagemath] sagemath: FTFBS with libreadline8
Added tag(s) bullseye and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
934171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934171
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#933785: gitlab: CVE-2019-5470 CVE-2019-5469 CVE-2019-5468 CVE-2019-5466 CVE-2019-5465 CVE-2019-5464 CVE-2019-5463 CVE-2019-5462 CVE-2019-5461

[Pirate Praveen]

I have uploaded 11.11.7 in my personal repo [1]. Since grpc and protobuf 
updates are not in the archive I cannot upload it to archive right now.


[1] people.debian.org/~praveen/gitlab

Processed: block 933685 with 933684

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 933685 with 933684
Bug #933685 [release.debian.org] transition: http-parser
933685 was not blocked by any bugs.
933685 was not blocking any bugs.
Added blocking bug(s) of 933685: 933684
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
933685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933685
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#934185: libkscreenlocker5: fails to accept correct pin after entering pin less than 6 chars with libpam-poldi

[Jason Franklin]

Package: libkscreenlocker5
Version: 5.14.5-1
Severity: grave
Justification: causes non-serious data loss

Greetings,

I am working on a machine that is configured to use libpam-poldi for
user authentication with GPG smart cards.

When the screen locker is engaged and the user enters a PIN that is under
six characters in length, two things happen:

  1. The screen locker will no longer accept a valid PIN.
  2. The /var/log/auth.log file fills up with "PIN too short" messages.

The messages in auth.log appear as below:

  Aug  2 09:10:46 hostname kcheckpass[9734]: PIN too short
  Aug  2 09:10:46 hostname kcheckpass[9734]: PIN too short
  Aug  2 09:10:46 hostname kcheckpass[9734]: PIN too short
  ...

This problem is clearly due to some issue at the boundary of kcheckpass
and libpam-poldi.  However, I am not yet able to determine which of the
two is responsible.

I have pulled down the source code of both packages, and I am actively
working on fixing the problem.  I can see where libpam-poldi obviously
will not accept a PIN less than 6 chars in length.  Refer to the
libpam-poldi source tree in the file...

  src/pam/auth-support/getpin-cb.c

to confirm this. 

Ideally, I would need to do the following to fix this issue:

  1. Compile libpam-poldi with debugging support.
  2. Compile kcheckpass with debugging support.
  3. Run kcheckpass with GDB to find where the conversation breaks down
 when a short PIN is provided.

This would tell us if the bug is with kcheckpass or with libpam-poldi.
Let me know if you can help me implement the plan of attack above,
especially if you can offer or refer me to instructions on building and
running kcheckpass from the shell.  That would be very helpful!

I am quite invested in fixing this, and I'll gladly help in any way
I can.  Please advise on a course of action.

Best wishes,
Jason Franklin

-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (500, 'stable'), (100, 'unstable'), (10, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages libkscreenlocker5 depends on:
ii  kpackagetool5  5.54.0-1
ii  libc6  2.28-10
ii  libkf5configcore5  5.54.0-1
ii  libkf5configgui5   5.54.0-1
ii  libkf5coreaddons5  5.54.0-1
ii  libkf5crash5   5.54.0-1
ii  libkf5declarative5 5.54.0-1
ii  libkf5globalaccel-bin  5.54.0-1
ii  libkf5globalaccel5 5.54.0-1
ii  libkf5i18n55.54.0-1
ii  libkf5idletime55.54.0-1
ii  libkf5notifications5   5.54.0-1
ii  libkf5package5 5.54.0-1
ii  libkf5quickaddons5 5.54.0-1
ii  libkf5waylandclient5   4:5.54.0-1
ii  libkf5waylandserver5   4:5.54.0-1
ii  libkf5windowsystem55.54.0-1
ii  libpam0g   1.3.1-5
ii  libqt5core5a   5.11.3+dfsg1-1
ii  libqt5dbus55.11.3+dfsg1-1
ii  libqt5gui5 5.11.3+dfsg1-1
ii  libqt5network5 5.11.3+dfsg1-1
ii  libqt5qml5 5.11.3-4
ii  libqt5quick5   5.11.3-4
ii  libqt5widgets5 5.11.3+dfsg1-1
ii  libqt5x11extras5   5.11.3-2
ii  libseccomp22.3.3-4
ii  libstdc++6 8.3.0-6
ii  libwayland-client0 1.16.0-1
ii  libwayland-server0 1.16.0-1
ii  libx11-6   2:1.6.7-1
ii  libxcb-keysyms10.4.0-1+b2
ii  libxcb11.13.1-2
ii  libxi6 2:1.7.9-1

Versions of packages libkscreenlocker5 recommends:
ii  kde-config-screenlocker  5.14.5-1

libkscreenlocker5 suggests no packages.

-- no debconf information

Processed: severity of 920147 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 920147 serious
Bug #920147 [sagemath] sagemath FTBFS on mipsel and mips64el
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
920147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920147
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#934182: kubernetes: CVE-2019-11248

[Salvatore Bonaccorso]

Hi 

Apologies, my fingers were to fast to send out the report:

On Wed, Aug 07, 2019 at 09:47:39PM +0200, Salvatore Bonaccorso wrote:
> CVE-2019-11248[0]:
> No description was found (try on a search engine)

... if I use a templating then maybe I should have added a sensible
description here. This is about the /debug/pprof endopoit beeing
exposed on kubelet's healthz port.

Regards,
Salvatore

Processed: fixed 933536 in satpy/0.16.1-2

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 933536 satpy/0.16.1-2
Bug #933536 [src:satpy] FTBFS: PYGAC_CONFIG_FILE is not a file or does not exist
Marked as fixed in versions satpy/0.16.1-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
933536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933536
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#934171: sagemath: FTFBS with libreadline8

[Jonathan Wiltshire]

Source: sagemath
Version: 8.6-6
Severity: serious
Tags: ftbfs
Justification: FTBFS

In a rebuild for the readline transition sagemath fails to build
with the following error:

| Error: 22979 tests failed, up to 50 failures are tolerated

I tried to capture some of the log but it's so vast I gave up waiting
for it to download. You can see the full logs on the buildd page,
https://buildd.debian.org/status/package.php?p=sagemath


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

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

Bug#934180: wpa: CVE-2019-13377: Timing-based side-channel attack against WPA3's Dragonfly handshake when using Brainpool curves

[Salvatore Bonaccorso]

Source: wpa
Version: 2:2.8-3
Severity: grave
Tags: security upstream

Hi,

The following vulnerability was published for wpa.

CVE-2019-13377[0]:
| Timing-based side-channel attack against WPA3's Dragonfly handshake when using
| Brainpool curves

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-13377
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13377
[1] https://w1.fi/security/2019-6/

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Processed: reassign 933536 to src:satpy, notfound 933536 in pygac/1.1.0-2, found 933536 in satpy/0.16.1-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 933536 src:satpy
Bug #933536 {Done: Antonio Valentino } 
[src:pygac] FTBFS: PYGAC_CONFIG_FILE is not a file or does not exist
Bug reassigned from package 'src:pygac' to 'src:satpy'.
No longer marked as found in versions pygac/1.1.0-2.
No longer marked as fixed in versions satpy/0.16.1-2.
> notfound 933536 pygac/1.1.0-2
Bug #933536 {Done: Antonio Valentino } 
[src:satpy] FTBFS: PYGAC_CONFIG_FILE is not a file or does not exist
Ignoring request to alter found versions of bug #933536 to the same values 
previously set
> found 933536 satpy/0.16.1-1
Bug #933536 {Done: Antonio Valentino } 
[src:satpy] FTBFS: PYGAC_CONFIG_FILE is not a file or does not exist
Marked as found in versions satpy/0.16.1-1 and reopened.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
933536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933536
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#934182: kubernetes: CVE-2019-11248

[Salvatore Bonaccorso]

Source: kubernetes
Version: 1.7.16+dfsg-1
Severity: grave
Tags: security upstream
Forwarded: https://github.com/kubernetes/kubernetes/issues/81023

Hi,

The following vulnerability was published for kubernetes.

CVE-2019-11248[0]:
No description was found (try on a search engine)

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-11248
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11248
[1] https://github.com/kubernetes/kubernetes/issues/81023

Regards,
Salvatore

Bug#934188: s3cmd: move to contrib. Depends on a non-free service with no free implementations

[Shawn Landden]

Package: s3cmd
Severity: serious
Justification: Policy 2.2.1

Hi,

This package depends on a non-free service (Amazon S3), but is in the main 
section of the archive.
This is a violation of 2.2.1:
must not require or recommend a package outside of main for compilation or 
execution

This program is useless without Amazon S3, and thus should be moved to the 
contrib section of the archive.

>From 2.2.2:
 
Examples of packages which would be included in contrib are:
 - wrapper packages or other sorts of free accessories for non-free programs.

-Shawn Landden

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: arm64 (aarch64)
Foreign Architectures: armel, armhf

Kernel: Linux 4.15.11-mainline-rev1 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages s3cmd depends on:
ii  python3   3.7.3-1
ii  python3-dateutil  2.7.3-3
pn  python3-magic 

s3cmd recommends no packages.

s3cmd suggests no packages.

Bug#934188: s3cmd: move to contrib. Depends on a non-free service with no free implementations

[Shawn Landden]

close -1
Message-ID: <156521345030.31452.11950702444220692635.report...@scaleway.git.icu>
X-Mailer: reportbug 7.5.2
Date: Wed, 07 Aug 2019 21:30:50 +
X-Debbugs-Cc: sh...@git.icu

Package: s3cmd
Followup-For: Bug #934188

It appears this is very common

https://packages.debian.org/search?keywords=twitter




-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: arm64 (aarch64)
Foreign Architectures: armel, armhf

Kernel: Linux 4.15.11-mainline-rev1 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages s3cmd depends on:
ii  python3   3.7.3-1
ii  python3-dateutil  2.7.3-3
pn  python3-magic 

s3cmd recommends no packages.

s3cmd suggests no packages.

Bug#933054: gnome-disks: segfault error 4 in libgobject-2.0.so.0.5800.3

[Bernhard Übelacker]

Hello Damon Anton Permezel,
this USB disk, has it a gpt or msdos partition table?

Also, maybe if it is possible, you could install
the package systemd-coredump.
Then some more information about a crash would be
collected in the journal, and a the process state would
be saved into /var/lib/systemd/coredump/.

Without that, I guess, there is not much the maintainer can
do about this issue, if it could not be reproduced by them.

Kind regards,
Bernhard

Bug#934191: ftp.debian.org: Should reject/ignore/auto-binNMU binary uploads

[Robert Luberda]

Package: ftp.debian.org
Severity: serious
Justification: common sense

As the binary uploads are usually pretty much useless, because they cannot
migrate to testing anymore [1], ftp.debian.org should do one of the
following things:
 - reject them (what seems the least preferred option to me);
 - ignore them (i.e. accept upload, but copy all included *.deb files to 
/dev/null);
 - automatically schedule binNMU;
 - or anything other that won't force developers to waste their time on 
   preparing another upload with no real changes, only to have their packages
   migrated to testing.

Regards,
robert

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

Bug#934188: marked as done (s3cmd: move to contrib. Depends on a non-free service with no free implementations)

[Debian Bug Tracking System]

Your message dated Wed, 07 Aug 2019 16:34:03 -0500
with message-id <1500331565213...@sas1-8cb08f430ac1.qloud-c.yandex.net>
and subject line closing
has caused the Debian Bug report #934188,
regarding s3cmd: move to contrib. Depends on a non-free service with no free 
implementations
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
934188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934188
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: s3cmd
Severity: serious
Justification: Policy 2.2.1

Hi,

This package depends on a non-free service (Amazon S3), but is in the main 
section of the archive.
This is a violation of 2.2.1:
must not require or recommend a package outside of main for compilation or 
execution

This program is useless without Amazon S3, and thus should be moved to the 
contrib section of the archive.

>From 2.2.2:
 
Examples of packages which would be included in contrib are:
 - wrapper packages or other sorts of free accessories for non-free programs.

-Shawn Landden

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: arm64 (aarch64)
Foreign Architectures: armel, armhf

Kernel: Linux 4.15.11-mainline-rev1 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages s3cmd depends on:
ii  python3   3.7.3-1
ii  python3-dateutil  2.7.3-3
pn  python3-magic 

s3cmd recommends no packages.

s3cmd suggests no packages.
--- End Message ---
--- Begin Message ---
closing this bug

debbugs

-- 
Shawn Landden--- End Message ---