Bug#902884: [Pkg-utopia-maintainers] Bug#902884: upowerd fails to start

[Michael Biebl]

Control: forcemerge 902411 -1

Am 02.07.2018 um 22:45 schrieb Eric Valette:
> Package: upower
> Version: 0.99.8-1
> Severity: grave
> Justification: renders package unusable
> 
> I had no upowerd daemon running on all my boxes:
> 
> Jul 02 20:52:00 htpc1 systemd[1]: Starting Daemon for power management...
> Jul 02 20:52:01 htpc1 upowerd[1106]: /usr/lib/upower/upowerd: error
> while loading shared libraries: libffi.so.6: cannot enable executable
> stack as shared object requires: O

Duplicate of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902411

-- 
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

Processed: Re: [Pkg-utopia-maintainers] Bug#902884: upowerd fails to start

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 902411 -1
Bug #902411 {Done: Jan Gerber } [upower] upower fails to start 
with MemoryDenyWriteExecute=true
Bug #902884 [upower] upowerd fails to start
Severity set to 'important' from 'grave'
Marked Bug as done
Merged 902411 902884

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

Bug#902895: ant: Automatically setting the value of the javac --release attribute breaks josm build.

[Bas Couwenberg]

Source: ant
Version: 1.10.3-2
Severity: serious
Justification: makes the package in question unusable or mostly so
Control: affects -1 src:josm

Dear Maintainer,

As mentioned on the list [0], the change in ant (1.10.3-2) to
automatically set the value of the javac --release attribute breaks the
josm build.

Please revent this change which is not included upstream.

IMHO it's perfectly fine to require JRE 9 or later when building with
JDK 9 or later. JDK 8 is EOL for ordinary humans.

[0] https://lists.debian.org/debian-java/2018/07/msg6.html

Kind Regards,

Bas

Processed: ant: Automatically setting the value of the javac --release attribute breaks josm build.

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:josm
Bug #902895 [src:ant] ant: Automatically setting the value of the javac 
--release attribute breaks josm build.
Added indication that 902895 affects src:josm

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

Bug#902766: marked as done (python3-twisted fails in the post-installation script when doing a first-time install)

[Debian Bug Tracking System]

Your message dated Tue, 03 Jul 2018 04:34:44 +
with message-id 
and subject line Bug#902766: fixed in twisted 18.4.0-2
has caused the Debian Bug report #902766,
regarding python3-twisted fails in the post-installation script when doing a 
first-time 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.)


-- 
902766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-twisted
Version: 18.4.0-1
Severity: serious
Justification: Policy 5.2 (package remains in unconfigured state)

Dear Maintainer,

When doing a fresh install the post-installation script fails with 

Setting up python3-twisted (18.4.0-1) ...
  File "/usr/lib/python3/dist-packages/twisted/conch/manhole.py", line
154
def write(self, data, async=False):
  ^
SyntaxError: invalid syntax

  File "/usr/lib/python3/dist-packages/twisted/mail/imap4.py", line
1093
def sendUntaggedResponse(self, message, async=False
^
SyntaxError: invalid syntax

dpkg: error processing package python3-twisted (--configure):
 installed python3-twisted package post-installation script subprocess
returned error exit status 1

This leaves the package itself and dependend packages un-configured. 

Apparently with the latest python-3.6 "async" can no longer be used as
a variable name because it is a keyword. 

Best, 
Gert

-- 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.14.44-gentoo (SMP w/6 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: unable to detect

Versions of packages python3-twisted depends on:
ii  python3   3.6.6-1
ii  python3-automat   0.6.0-1
ii  python3-constantly15.1.0-1
ii  python3-hyperlink 17.3.1-2
ii  python3-incremental   16.10.1-3
ii  python3-openssl   18.0.0-1
ii  python3-service-identity  16.0.0-2
ii  python3-twisted-bin   18.4.0-1
ii  python3-zope.interface4.3.2-1+b2

Versions of packages python3-twisted recommends:
pn  python3-pam 
ii  python3-serial  3.4-3
-- 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.14.44-gentoo (SMP w/6 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: unable to detect

Versions of packages python3-twisted depends on:
ii  python3   3.6.6-1
ii  python3-automat   0.6.0-1
ii  python3-constantly15.1.0-1
ii  python3-hyperlink 17.3.1-2
ii  python3-incremental   16.10.1-3
ii  python3-openssl   18.0.0-1
ii  python3-service-identity  16.0.0-2
ii  python3-twisted-bin   18.4.0-1
ii  python3-zope.interface4.3.2-1+b2

Versions of packages python3-twisted recommends:
pn  python3-pam 
ii  python3-serial  3.4-3

Versions of packages python3-twisted suggests:
pn  python3-glade2
pn  python3-gtk2  
pn  python3-qt4   
ii  python3-tk3.6.6-1
pn  python3-wxgtk2.8  

-- no debconf information
Versions of packages python3-twisted suggests:
pn  python3-glade2
pn  python3-gtk2  
pn  python3-qt4   
ii  python3-tk3.6.6-1
pn  python3-wxgtk2.8  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: twisted
Source-Version: 18.4.0-2

We believe that the bug you reported is fixed in the latest version of
twisted, 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 902...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated twisted package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 03 Jul 2018 05:50:32 +0200
Source: twisted
Binary: python3-twisted python3-twisted-bin 

Bug#866122: slapd-mtread crash on ppc64{,el} in stretch/sid

[Ryan Tandy]

Control: found -1 4.9.88-1+deb9u1

Hi,

On Sun, Jul 01, 2018 at 03:42:12AM +0100, Ben Hutchings wrote:

Is this bug still present?


It still reproduces with the current stretch kernel:

debian@debian:~/openldap-2.4.44+dfsg/debian/build/tests$ ./run -b mdb 
test060-mt-hot
Cleaning up test run directory leftover from previous run.
Running ../../../tests/scripts/test060-mt-hot for mdb...
running defines.sh
Running slapadd to build slapd database...
Running slapindex to index slapd database...
Starting slapd on TCP/IP port 9011...
/home/debian/openldap-2.4.44+dfsg/debian/build/tests/../servers/slapd/slapd -s0 
-f /home/debian/openldap-2.4.44+dfsg/debian/build/tests/testrun/slapd.1.conf -h 
ldap://localhost:9011/ -d stats
Testing basic monitor search...
Monitor searches
Testing basic mt-hot search: 1 threads (1 x 5) loops...
./progs/slapd-mtread -H ldap://localhost:9011/ -D cn=Manager,dc=example,dc=com 
-w secret -e cn=Monitor -m 1 -L 1 -l 5
Testing basic mt-hot search: 5 threads (1 x 1) loops...
./progs/slapd-mtread -H ldap://localhost:9011/ -D cn=Manager,dc=example,dc=com 
-w secret -e cn=Monitor -m 5 -L 1 -l 1
Testing basic mt-hot search: 100 threads (5 x 100) loops...
./progs/slapd-mtread -H ldap://localhost:9011/ -D cn=Manager,dc=example,dc=com 
-w secret -e cn=Monitor -m 100 -L 5 -l 100
Random searches
Testing random mt-hot search: 1 threads (1 x 5) loops...
./progs/slapd-mtread -H ldap://localhost:9011/ -D cn=Manager,dc=example,dc=com 
-w secret -e dc=example,dc=com -f (objectclass=*) -m 1 -L 1 -l 5
Testing random mt-hot search: 5 threads (1 x 1) loops...
./progs/slapd-mtread -H ldap://localhost:9011/ -D cn=Manager,dc=example,dc=com 
-w secret -e dc=example,dc=com -f (objectclass=*) -m 5 -L 1 -l 1
slapd-mtread failed (139)!
debian@debian:~/openldap-2.4.44+dfsg/debian/build/tests$ uname -a
Linux debian 4.9.0-6-powerpc64le #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) 
ppc64le GNU/Linux

However it looks like it might be resolved with the kernel in unstable. 
I will run some more iterations and let you know.


a7771176 (4.15) looks interesting - it's specifically tagged as fixing 
the commit I isolated as the broken one (dc16b553), and the message 
sounds relevant. If the unstable kernel survives multiple runs I'll see 
what this does on 4.9.


https://patchwork.ozlabs.org/patch/833190/

Processed: Re: Bug#866122: slapd-mtread crash on ppc64{,el} in stretch/sid

[Debian Bug Tracking System]

Processing control commands:

> found -1 4.9.88-1+deb9u1
Bug #866122 [src:linux] test060-mt-hot failing on ppc64el buildd
Bug #866371 [src:linux] openldap FTBFS on ppc64{,el}: slapd-mtread failed (139)
Marked as found in versions linux/4.9.88-1+deb9u1.
Marked as found in versions linux/4.9.88-1+deb9u1.

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

Processed: Re: Bug#902788: python3-minimal needs Breaks for software/modules broken by 3.7

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 python3.7
Bug #902788 [python3-minimal] python3-minimal needs Breaks for software/modules 
broken by 3.7
Bug reassigned from package 'python3-minimal' to 'python3.7'.
No longer marked as found in versions python3-defaults/3.6.6-1.
Ignoring request to alter fixed versions of bug #902788 to the same values 
previously set

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

Bug#902788: python3-minimal needs Breaks for software/modules broken by 3.7

[Matthias Klose]

Control: reassign -1 python3.7

On 30.06.2018 22:58, Adrian Bunk wrote:

Package: python3-minimal
Version: 3.6.6-1
Severity: serious
Control: block -1 by 902757 902631 902766 902646 902715 902650
Control: block 902582 by -1

Plenty of packages fail to work or even install with Python 3.7
for reasons like 'async' now being a keyword.

python3-minimal needs Breaks for against all versions of other
packages in stretch or buster that don't work with 3.7.


if at all, python3.7 needs these breaks, not the dependency packages.

Bug#902892: plinth: Any change to user account will lock out user

[James Valleroy]

Package: plinth
Version: 0.33.0
Severity: grave
Justification: renders package unusable

If plinth has a single admin user account, and any changes are made to
that user account, the user will be locked out of plinth.

More information and logs:
https://salsa.debian.org/freedombox-team/plinth/issues/1314

Bug#902883: [Pkg-samba-maint] Bug#902883: FTBFS on arch != amd64 because different libpytalloc-util.*.so name

[Andrew Bartlett]

On Mon, 2018-07-02 at 22:15 +0200, Mathieu Parent wrote:
> Package: src:talloc
> Version: 2.1.13-1
> Severity: serious
> 
> Regression since python3 support:
> 
> [...]
> dh_makeshlibs -ppython-talloc -ppython3-talloc -Xtalloc. -- -c3
> dpkg-gensymbols: warning: new libraries appeared in the symbols file: 
> libpytalloc-util.cpython-36m-aarch64-linux-gnu.so.2
> dpkg-gensymbols: warning: some libraries disappeared in the symbols file: 
> libpytalloc-util.cpython-36m-x86-64-linux-gnu.so.2
> dpkg-gensymbols: warning: debian/python3-talloc/DEBIAN/symbols doesn't match 
> completely debian/python3-talloc.symbols

See also https://github.com/samba-team/samba/pull/110 for BaT trying to
fix this kind of thing on FreeBSD.

Andrew Bartlett
-- 
Andrew Bartlett
https://samba.org/~abartlet/
Authentication Developer, Samba Team https://samba.org
Samba Development and Support, Catalyst IT   
https://catalyst.net.nz/services/samba

Processed (with 1 error): reassign 902868 to src:nvidia-graphics-drivers, forcibly merging 902661 902868

[Debian Bug Tracking System]

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

> reassign 902868 src:nvidia-graphics-drivers
Bug #902868 [src:linux] linux-image-4.16.0-2-amd64 fails to boot
Bug reassigned from package 'src:linux' to 'src:nvidia-graphics-drivers'.
No longer marked as found in versions linux/4.16.16-2.
Ignoring request to alter fixed versions of bug #902868 to the same values 
previously set
> forcemerge 902661 902868
Bug #902661 [nvidia-driver] linux-image-4.16.0-2-amd64: kernel BUG at 
/build/linux-uwVqDp/linux-4.16.16/mm/usercopy.c:100!
Bug #901919 [nvidia-driver] nvidia-driver: black screen with the latest Linux 
kernel - general protection fault
Bug #901932 [nvidia-driver] linux-image-4.16.0-2-amd64: Blank screen after 
update kernel 4.16.16
Bug #901990 [nvidia-driver] linux-image-4.16.0-2-amd64: kernel BUG at startup 
in usercopy.c ; impossible to boot
Bug #902248 [nvidia-driver] linux-image-4.16.0-2-amd64: General protection 
fault (with nvidia driver) redulting in Xork proces hanging in "D" state
Bug #902773 [nvidia-driver] nvidia-driver: Kernel BUG on 4.16.16 with 390.67-1, 
crashes on desktop boot
Bug #902819 [nvidia-driver] system freeze (hang task) when launching Xorg(1) 
after a new version of linux-image installed
Unable to merge bugs because:
package of #902868 is 'src:nvidia-graphics-drivers' not 'nvidia-driver'
Failed to forcibly merge 902661: Did not alter merged bugs.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
901919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901919
901932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901932
901990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901990
902248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902248
902661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902661
902773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902773
902819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902819
902868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902868
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#901110: marked as done (libgdamm5.0: FTBFS when built with dpkg-buildpackage -A)

[Debian Bug Tracking System]

Your message dated Mon, 02 Jul 2018 22:49:13 +
with message-id 
and subject line Bug#901110: fixed in libgdamm5.0 4.99.11-2
has caused the Debian Bug report #901110,
regarding libgdamm5.0: FTBFS when built with dpkg-buildpackage -A
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.)


-- 
901110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901110
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libgdamm5.0
Version: 4.99.11-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with gnome
   dh_update_autotools_config -i
   dh_autoreconf -i
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build'.
libtoolize: copying file 'build/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'build'.
libtoolize: copying file 'build/libtool.m4'
libtoolize: copying file 'build/ltoptions.m4'
libtoolize: copying file 'build/ltsugar.m4'
libtoolize: copying file 'build/ltversion.m4'
libtoolize: copying file 'build/lt~obsolete.m4'
configure.ac:47: installing 'build/compile'
configure.ac:38: installing 'build/missing'

[... snipped ...]

/usr/bin/make -C examples clean
make[2]: Entering directory '/<>/examples'
 rm -f config/example simple/example sqlbuilder/example
rm -rf .libs _libs
rm -rf config/.libs config/_libs
rm -rf simple/.libs simple/_libs
rm -rf sqlbuilder/.libs sqlbuilder/_libs
rm -f *.o
rm -f config/*.o
rm -f simple/*.o
rm -f sqlbuilder/*.o
rm -f *.lo
make[2]: Leaving directory '/<>/examples'
dh_installexamples -X.deps -X.dirstamp -XMakefile
make[1]: Leaving directory '/<>'
   dh_gnome -i
   dh_perl -i
   dh_link -i
   dh_strip_nondeterminism -i
   debian/rules override_dh_compress
make[1]: Entering directory '/<>'
dh_compress -X reference -X examples
make[1]: Leaving directory '/<>'
   dh_fixperms -i
   debian/rules override_dh_missing
make[1]: Entering directory '/<>'
dh_missing --fail-missing
dh_missing: usr/lib/x86_64-linux-gnu/libgdamm-5.0.la exists in debian/tmp but 
is not installed to anywhere
dh_missing: missing files, aborting
The following debhelper tools have reported what they installed (with 
files per package)
 * dh_install: libgdamm-5.0-13 (2), libgdamm5.0-dev (4), 
libgdamm5.0-doc (2)
 * dh_installdocs: libgdamm-5.0-13 (1), libgdamm5.0-dev (0), 
libgdamm5.0-doc (0)
 * dh_installexamples: libgdamm-5.0-13 (0), libgdamm5.0-dev (0), 
libgdamm5.0-doc (7)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper itself, 
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
For a short-term work-around: Add the files to debian/not-installed
debian/rules:30: recipe for target 'override_dh_missing' failed
make[1]: *** [override_dh_missing] Error 255
make[1]: Leaving directory '/<>'
debian/rules:13: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


To reproduce, please try "dpkg-buildpackage -A".
(The error does not happen with "dpkg-buildpackage").

Thanks.
--- End Message ---
--- Begin Message ---
Source: libgdamm5.0
Source-Version: 4.99.11-2

We believe that the bug you reported is fixed in the latest version of
libgdamm5.0, 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 901...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated libgdamm5.0 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: Mon, 02 Jul 2018 11:17:24 +0100
Source: libgdamm5.0

Bug#792205: closed by Guillaume Bougard (Re: fusioninventory-agent: modifies conffiles (policy 10.7.3): /etc/fusioninventory/agent.cfg)

[Andreas Beckmann]

On 2018-07-02 20:10, gregor herrmann wrote:
> On Mon, 02 Jul 2018 09:19:11 +0200, Guillaume Bougard wrote:
> 
>> in fact, and regarding the package history, the bug should have
>> been opened with 2.3.10 and closed with not releases 2.3.15...
>>
>> How to avoid this case becomes blocking for the migration to
>> testing planned in 8 days now ?
> 
> Technically, I suppose that "resetting" the affected versions [0]
> should do it. I'm just a bit reluctant to do or recommend it since
> there must have been a reason why Andreas filed the bug against
> 1:2.3.16-1.

even if 1:2.3.16-1 fixed it for new installations, it didn't clean up
after upgrades from older versions. Not sure whether it exploded with a
dpkg prompt about modified conffiles ...

> OTOH, I guess it's a bit hard to test the complete upgrade path any
> longer [1], and I'm not sure how much it matters at this point.

That's still easily possible - needs 4 -d options for piuparts.

> We could also (temporarily?) lower the severity of the bug; but I'd
> rather wait for Andreas' opinion on the issue.

That's probably OK, or rather remove the fixed version.


Andreas

Bug#902884: upowerd fails to start

[Eric Valette]

Package: upower
Version: 0.99.8-1
Severity: grave
Justification: renders package unusable

I had no upowerd daemon running on all my boxes:

Jul 02 20:52:00 htpc1 systemd[1]: Starting Daemon for power management...
Jul 02 20:52:01 htpc1 upowerd[1106]: /usr/lib/upower/upowerd: error 
while loading shared libraries: libffi.so.6: cannot enable executable 
stack as shared object requires: O
Jul 02 20:52:01 htpc1 systemd[1]: upower.service: Main process exited, 
code=exited, status=127/n/a
Jul 02 20:52:01 htpc1 systemd[1]: upower.service: Failed with result 
'exit-code'.
Jul 02 20:52:01 htpc1 systemd[1]: Failed to start Daemon for power 
management.
Jul 02 20:52:01 htpc1 systemd[1]: upower.service: Service 
RestartSec=100ms expired, scheduling restart.
Jul 02 20:52:01 htpc1 systemd[1]: upower.service: Scheduled restart job, 
restart counter is at 1.

Jul 02 20:52:01 htpc1 systemd[1]: Stopped Daemon for power management.
Jul 02 20:52:01 htpc1 systemd[1]: Starting Daemon for power management...
Jul 02 20:52:01 htpc1 upowerd[1109]: /usr/lib/upower/upowerd: error 
while loading shared libraries: libffi.so.6: cannot enable executable 
stack as shared object requires: O
Jul 02 20:52:01 htpc1 systemd[1]: upower.service: Main process exited, 
code=exited, status=127/n/a
Jul 02 20:52:01 htpc1 systemd[1]: upower.service: Failed with result 
'exit-code'.
Jul 02 20:52:01 htpc1 systemd[1]: Failed to start Daemon for power 
management.
Jul 02 20:52:01 htpc1 systemd[1]: upower.service: Service 
RestartSec=100ms expired, scheduling restart.
Jul 02 20:52:01 htpc1 systemd[1]: upower.service: Scheduled restart job, 
restart counter is at 2.

Jul 02 20:52:01 htpc1 systemd[1]: Stopped Daemon for power management.
Jul 02 20:52:01 htpc1 systemd[1]: Starting Daemon for power management...
lines 1249-1287

execstack -c /usr/lib/x86_64-linux-gnu/libffi.so.6.0.4 clear the problem.



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

Kernel: Linux 4.14.52 (SMP w/4 CPU cores; PREEMPT)
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)

Versions of packages upower depends on:
ii  dbus   1.13.4-3
ii  libc6  2.27-3
ii  libglib2.0-0   2.56.1-2
ii  libgudev-1.0-0 232-2
ii  libimobiledevice6  1.2.1~git20180302.3a37a4e-1
ii  libplist3  2.0.0-3
ii  libupower-glib30.99.8-1
ii  libusb-1.0-0   2:1.0.22-2
ii  udev   239-3

Versions of packages upower recommends:
ii  policykit-1  0.114-1

upower suggests no packages.

-- no debconf information


-- eric

Processed: found 902786 in 0.7.3-7

[Debian Bug Tracking System]

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

> found 902786 0.7.3-7
Bug #902786 {Done: Andreas Tille } [src:libquazip] 
CVE-2018-1002209
Marked as found in versions libquazip/0.7.3-7.
> thanks
Stopping processing here.

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

Bug#902883: FTBFS on arch != amd64 because different libpytalloc-util.*.so name

[Mathieu Parent]

Package: src:talloc
Version: 2.1.13-1
Severity: serious

Regression since python3 support:

[...]
dh_makeshlibs -ppython-talloc -ppython3-talloc -Xtalloc. -- -c3
dpkg-gensymbols: warning: new libraries appeared in the symbols file: 
libpytalloc-util.cpython-36m-aarch64-linux-gnu.so.2
dpkg-gensymbols: warning: some libraries disappeared in the symbols file: 
libpytalloc-util.cpython-36m-x86-64-linux-gnu.so.2
dpkg-gensymbols: warning: debian/python3-talloc/DEBIAN/symbols doesn't match 
completely debian/python3-talloc.symbols
--- debian/python3-talloc.symbols (python3-talloc_2.1.13-1_arm64)
+++ dpkg-gensymbolsYed6IE   2018-07-02 13:59:00.845850036 +
@@ -1,26 +1,26 @@
-libpytalloc-util.cpython-36m-x86-64-linux-gnu.so.2 python3-talloc #MINVER#
- 
PYTALLOC_UTIL.CPYTHON_36M_X86_64_LINUX_GNU_2.1.13@PYTALLOC_UTIL.CPYTHON_36M_X86_64_LINUX_GNU_2.1.13
 2.1.13
- PYTALLOC_UTIL.PY3_2.1.10@PYTALLOC_UTIL.PY3_2.1.10 2.1.11
- PYTALLOC_UTIL.PY3_2.1.11@PYTALLOC_UTIL.PY3_2.1.11 2.1.11
- PYTALLOC_UTIL.PY3_2.1.12@PYTALLOC_UTIL.PY3_2.1.12 2.1.12
- PYTALLOC_UTIL.PY3_2.1.13@PYTALLOC_UTIL.PY3_2.1.13 2.1.13
- PYTALLOC_UTIL.PY3_2.1.5@PYTALLOC_UTIL.PY3_2.1.5 2.1.11
- PYTALLOC_UTIL.PY3_2.1.6@PYTALLOC_UTIL.PY3_2.1.6 2.1.11
- PYTALLOC_UTIL.PY3_2.1.7@PYTALLOC_UTIL.PY3_2.1.7 2.1.11
- PYTALLOC_UTIL.PY3_2.1.8@PYTALLOC_UTIL.PY3_2.1.8 2.1.11
- PYTALLOC_UTIL.PY3_2.1.9@PYTALLOC_UTIL.PY3_2.1.9 2.1.11
- _pytalloc_check_type@PYTALLOC_UTIL.PY3_2.1.9 2.1.11
- _pytalloc_get_mem_ctx@PYTALLOC_UTIL.PY3_2.1.6 2.1.11
- _pytalloc_get_ptr@PYTALLOC_UTIL.PY3_2.1.6 2.1.11
- _pytalloc_get_type@PYTALLOC_UTIL.PY3_2.1.6 2.1.11
- pytalloc_BaseObject_PyType_Ready@PYTALLOC_UTIL.PY3_2.1.6 2.1.11
- pytalloc_BaseObject_check@PYTALLOC_UTIL.PY3_2.1.6 2.1.11
- pytalloc_BaseObject_size@PYTALLOC_UTIL.PY3_2.1.6 2.1.11
- pytalloc_Check@PYTALLOC_UTIL.PY3_2.1.5 2.1.11
- pytalloc_GenericObject_reference_ex@PYTALLOC_UTIL.PY3_2.1.9 2.1.11
- pytalloc_GenericObject_steal_ex@PYTALLOC_UTIL.PY3_2.1.9 2.1.11
- pytalloc_GetBaseObjectType@PYTALLOC_UTIL.PY3_2.1.6 2.1.11
- pytalloc_GetObjectType@PYTALLOC_UTIL.PY3_2.1.5 2.1.11
- pytalloc_reference_ex@PYTALLOC_UTIL.PY3_2.1.5 2.1.11
- pytalloc_steal@PYTALLOC_UTIL.PY3_2.1.5 2.1.11
- pytalloc_steal_ex@PYTALLOC_UTIL.PY3_2.1.5 2.1.11
+libpytalloc-util.cpython-36m-aarch64-linux-gnu.so.2 python3-talloc #MINVER#
+ 
PYTALLOC_UTIL.CPYTHON_36M_AARCH64_LINUX_GNU_2.1.13@PYTALLOC_UTIL.CPYTHON_36M_AARCH64_LINUX_GNU_2.1.13
 2.1.13-1
+ PYTALLOC_UTIL.PY3_2.1.10@PYTALLOC_UTIL.PY3_2.1.10 2.1.13-1
+ PYTALLOC_UTIL.PY3_2.1.11@PYTALLOC_UTIL.PY3_2.1.11 2.1.13-1
+ PYTALLOC_UTIL.PY3_2.1.12@PYTALLOC_UTIL.PY3_2.1.12 2.1.13-1
+ PYTALLOC_UTIL.PY3_2.1.13@PYTALLOC_UTIL.PY3_2.1.13 2.1.13-1
+ PYTALLOC_UTIL.PY3_2.1.5@PYTALLOC_UTIL.PY3_2.1.5 2.1.13-1
+ PYTALLOC_UTIL.PY3_2.1.6@PYTALLOC_UTIL.PY3_2.1.6 2.1.13-1
+ PYTALLOC_UTIL.PY3_2.1.7@PYTALLOC_UTIL.PY3_2.1.7 2.1.13-1
+ PYTALLOC_UTIL.PY3_2.1.8@PYTALLOC_UTIL.PY3_2.1.8 2.1.13-1
+ PYTALLOC_UTIL.PY3_2.1.9@PYTALLOC_UTIL.PY3_2.1.9 2.1.13-1
+ _pytalloc_check_type@PYTALLOC_UTIL.PY3_2.1.9 2.1.13-1
+ _pytalloc_get_mem_ctx@PYTALLOC_UTIL.PY3_2.1.6 2.1.13-1
+ _pytalloc_get_ptr@PYTALLOC_UTIL.PY3_2.1.6 2.1.13-1
+ _pytalloc_get_type@PYTALLOC_UTIL.PY3_2.1.6 2.1.13-1
+ pytalloc_BaseObject_PyType_Ready@PYTALLOC_UTIL.PY3_2.1.6 2.1.13-1
+ pytalloc_BaseObject_check@PYTALLOC_UTIL.PY3_2.1.6 2.1.13-1
+ pytalloc_BaseObject_size@PYTALLOC_UTIL.PY3_2.1.6 2.1.13-1
+ pytalloc_Check@PYTALLOC_UTIL.PY3_2.1.5 2.1.13-1
+ pytalloc_GenericObject_reference_ex@PYTALLOC_UTIL.PY3_2.1.9 2.1.13-1
+ pytalloc_GenericObject_steal_ex@PYTALLOC_UTIL.PY3_2.1.9 2.1.13-1
+ pytalloc_GetBaseObjectType@PYTALLOC_UTIL.PY3_2.1.6 2.1.13-1
+ pytalloc_GetObjectType@PYTALLOC_UTIL.PY3_2.1.5 2.1.13-1
+ pytalloc_reference_ex@PYTALLOC_UTIL.PY3_2.1.5 2.1.13-1
+ pytalloc_steal@PYTALLOC_UTIL.PY3_2.1.5 2.1.13-1
+ pytalloc_steal_ex@PYTALLOC_UTIL.PY3_2.1.5 2.1.13-1
dh_makeshlibs: failing due to earlier errors
debian/rules:72: recipe for target 'override_dh_makeshlibs' failed


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

Kernel: Linux 4.16.0-1-amd64 (SMP w/2 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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#902709: diffoscope: test failures everywhere

[Mattia Rizzolo]

On Mon, Jul 02, 2018 at 08:43:04PM +0100, Chris Lamb wrote:
> > This particular error is fixed by d6f1d04 (and I did include the bug
> > number in the commit).
> 
> Are we talking about the right commit? I only ask because I do not see
> the bug number in the commit... :)
> 
>https://salsa.debian.org/reproducible-builds/diffoscope/commit/
>  d6f1d04b3dbc3f350f50a798979e1501a8cb89f3

Oops, copy-paste error.  Indeed, I'm referring to this other commit:
https://salsa.debian.org/reproducible-builds/diffoscope/commit/a6b4effcfb24780d9d2d1b76efa33132381f76eb

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#902709: diffoscope: test failures everywhere

[Mattia Rizzolo]

Control: owner -1 !
Control: tag -1 pending

On Mon, Jul 02, 2018 at 06:52:15PM +0100, Chris Lamb wrote:
> Are we still seeing this on current master? (As-of writing, that is
> a6b4effc).  I ask because, as mentioned previously, I cannot reproduce
> this. :)

This particular error is fixed by d6f1d04 (and I did include the bug
number in the commit).

However, in the process of fixing this I also configure gitlab CI, which
is reporting 4 more errors (look at salsa.d.o, or IRC yesterday).

> Happy to upload if your recent changes (d6f1d04 looks promising?)
> fix it.

I'll take care of it once I can debug the other 4 errors (tbh, I didn't
try to reproduce them locally).

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Processed: Re: Bug#902709: diffoscope: test failures everywhere

[Debian Bug Tracking System]

Processing control commands:

> owner -1 !
Bug #902709 [diffoscope] diffoscope: FTBFS: /usr/lib/python3.6/tempfile.py:509: 
FileNotFoundError
Owner recorded as Mattia Rizzolo .
> tag -1 pending
Bug #902709 [diffoscope] diffoscope: FTBFS: /usr/lib/python3.6/tempfile.py:509: 
FileNotFoundError
Added tag(s) pending.

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

Bug#902709: diffoscope: test failures everywhere

[Chris Lamb]

Hi Mattia,

> This particular error is fixed by d6f1d04 (and I did include the bug
> number in the commit).

Are we talking about the right commit? I only ask because I do not see
the bug number in the commit... :)

   https://salsa.debian.org/reproducible-builds/diffoscope/commit/
 d6f1d04b3dbc3f350f50a798979e1501a8cb89f3


Best wishes,

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

Bug#902881: [debian-installer] Cannot partition disk in Testing installer

[Alexander Kernozhitsky]

Package: debian-installer
Version: 20180610
Severity: grave

I tried to install Debian Testing on VirtualBox using a weekly build of Debian 
Installer. Everything went OK until the disk partitioning stage. In this 
stage, installer warned me that the kernel doesn't support LVM and I should 
load lvm-mod. Then, I didn't found an option to format a partition as Ext4 
filesystem. Automatical installation allowed to create an Ext4 root partition, 
but after writing the changes to disk it says something like "cannot mount /".

--- System information. ---
Architecture: 
Kernel:   Linux 4.16.0-2-amd64

Debian Release: buster/sid
  990 testing ftp.by.debian.org 
  500 unstableftp.by.debian.org 

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.
-- 
-
Alexander Kernozhitsky

Processed: found 902726 in 10.7.5+dfsg-1

[Debian Bug Tracking System]

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

> found 902726 10.7.5+dfsg-1
Bug #902726 [gitlab] 2018/06/25 security release
There is no source info for the package 'gitlab' at version '10.7.5+dfsg-1' 
with architecture ''
Unable to make a source version for version '10.7.5+dfsg-1'
Marked as found in versions 10.7.5+dfsg-1.
> thanks
Stopping processing here.

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

Processed: found 902726 in 10.7.5+dfsg-3

[Debian Bug Tracking System]

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

> found 902726 10.7.5+dfsg-3
Bug #902726 [gitlab] 2018/06/25 security release
Marked as found in versions gitlab/10.7.5+dfsg-3.
> thanks
Stopping processing here.

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

Bug#874526: Keyboard grab doesn't work under Wayland

[Josh Triplett]

On Mon, Jul 02, 2018 at 06:36:54PM +0100, Simon McVittie wrote:
> On Wed, 06 Sep 2017 at 14:58:37 -0700, Josh Triplett wrote:
> > (It might also help to add Ctrl-Alt-Delete to the list of shortcuts
> > provided in the gnome-boxes keyboard menu, alongside Ctrl-Alt-Backspace
> > and similar.)
> 
> This is now provided in the keyboard menu for both gnome-boxes and
> virt-manager.

I appreciate that, thank you. That will help heavily as a workaround.

Bug#874526: Keyboard grab doesn't work under Wayland

[Josh Triplett]

On Mon, Jul 02, 2018 at 06:14:44PM +0100, Simon McVittie wrote:
> On Mon, 02 Jul 2018 at 01:39:24 -0700, Josh Triplett wrote:
> > On Mon, Jul 02, 2018 at 08:14:48AM +0100, Simon McVittie wrote:
> > > This seems to work under GNOME 3.28 (probably also 3.26). I'm prompted
> > > while starting up the VM for whether to allow gnome-boxes to grab the
> > > keyboard. I haven't tried a Windows VM, but if I use the keyboard menu to
> > > switch to a text-mode VT for a Linux VM with Ctrl+Alt+F$n, then either
> > > press Ctrl+Alt+Del or send it via the keyboard menu, the VM reboots
> > > as expected.
> > 
> > I can confirm that I can still reproduce this with current GNOME and
> > gnome-boxes; Ctrl+Alt+Del still goes to GNOME and not to the VM.
> 
> Which versions of gnome-shell, libmutter-2-0, gnome-boxes do you have?

gnome-boxes 3.28.5-1
gnome-shell 3.28.2-1
libmutter-2-0:amd64 3.28.2-2

> Are you prompted for whether to let gnome-boxes inhibit shortcuts? You
> should get a system-modal dialog (the sort that dims the entire screen,
> like the Shut Down dialog you get from Ctrl+Alt+Del itself) something
> like this:
> 
> |--|
> |  Boxes wants to inhibit shortcuts|
> | /!\  |
> |  You can restore shortcuts by pressing Super+Escape. |
> |  |
> |[ Deny ][ Allow ]-|
> 
> (If you don't click Allow then this feature is not expected to work.)

No, I don't get that prompt from gnome-boxes. (I've seen it before from
other applications.)

> Does it help to click inside the virtual machine window before pressing
> Ctrl+Alt+Del?

If I'm in windowed mode, yes.

As far as I can tell, it's possible to end up in a state in which the VM
has the focus but gnome-boxes doesn't have a grab on Ctrl+Alt+Del. This
can happen both in windowed mode and in fullscreen mode. In windowed
mode, if I click in gnome-boxes then a grab takes place and Ctrl+Alt+Del
works.

This may also have something to do with switching windows (via the
overview) away from a VM.

> Does sending Ctrl+Alt+Del via the keyboard menu work?

Yes.

Processed: found 902721 in 1.7.2-1

[Debian Bug Tracking System]

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

> found 902721 1.7.2-1
Bug #902721 [ruby-json-jwt] CVE-2018-1000539
Marked as found in versions ruby-json-jwt/1.7.2-1.
> thanks
Stopping processing here.

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

Processed: bug 902721 is forwarded to https://github.com/nov/json-jwt/pull/62

[Debian Bug Tracking System]

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

> forwarded 902721 https://github.com/nov/json-jwt/pull/62
Bug #902721 [ruby-json-jwt] CVE-2018-1000539
Set Bug forwarded-to-address to 'https://github.com/nov/json-jwt/pull/62'.
> thanks
Stopping processing here.

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

Processed: bug 902723 is forwarded to https://github.com/gosa-project/gosa-core/issues/14

[Debian Bug Tracking System]

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

> forwarded 902723 https://github.com/gosa-project/gosa-core/issues/14
Bug #902723 {Done: Mike Gabriel } [src:gosa] 
CVE-2018-1000528
Set Bug forwarded-to-address to 
'https://github.com/gosa-project/gosa-core/issues/14'.
> thanks
Stopping processing here.

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

Processed: found 902723 in 2.7.4+reloaded3-1

[Debian Bug Tracking System]

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

> found 902723 2.7.4+reloaded3-1
Bug #902723 {Done: Mike Gabriel } [src:gosa] 
CVE-2018-1000528
Marked as found in versions gosa/2.7.4+reloaded3-1.
> thanks
Stopping processing here.

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

Bug#792205: closed by Guillaume Bougard (Re: fusioninventory-agent: modifies conffiles (policy 10.7.3): /etc/fusioninventory/agent.cfg)

[gregor herrmann]

On Mon, 02 Jul 2018 09:19:11 +0200, Guillaume Bougard wrote:

> in fact, and regarding the package history, the bug should have
> been opened with 2.3.10 and closed with not releases 2.3.15...
> 
> How to avoid this case becomes blocking for the migration to
> testing planned in 8 days now ?

Technically, I suppose that "resetting" the affected versions [0]
should do it. I'm just a bit reluctant to do or recommend it since
there must have been a reason why Andreas filed the bug against
1:2.3.16-1.

OTOH, I guess it's a bit hard to test the complete upgrade path any
longer [1], and I'm not sure how much it matters at this point.

We could also (temporarily?) lower the severity of the bug; but I'd
rather wait for Andreas' opinion on the issue.

The current piuparts results look good:
https://piuparts.debian.org/sid/source/f/fusioninventory-agent.html
but AFAICS they only test install and removal of the current version
and no upgrades ...


Cheers,
gregor


[0]
notfound 792205 1:2.3.16-1
found 792205 1:2.3.10.1-1

[1]
"This problem was observed after an squeeze -> wheezy -> jessie ->
stretch upgrade."
 

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Tom Waits: Step Right Up


signature.asc
Description: Digital Signature

Processed: tagging 902720

[Debian Bug Tracking System]

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

> tags 902720 + upstream
Bug #902720 [ruby-zip] CVE-2018-1000544
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Processed: bug 902720 is forwarded to https://github.com/rubyzip/rubyzip/issues/369

[Debian Bug Tracking System]

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

> forwarded 902720 https://github.com/rubyzip/rubyzip/issues/369
Bug #902720 [ruby-zip] CVE-2018-1000544
Set Bug forwarded-to-address to 'https://github.com/rubyzip/rubyzip/issues/369'.
> thanks
Stopping processing here.

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

Processed: found 902720 in 1.2.1-1

[Debian Bug Tracking System]

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

> found 902720 1.2.1-1
Bug #902720 [ruby-zip] CVE-2018-1000544
Marked as found in versions ruby-zip/1.2.1-1.
> thanks
Stopping processing here.

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

Bug#902709: diffoscope: test failures everywhere

[Chris Lamb]

Hi Mattia,

> So, autopkgtest is failing
[…]
> The ubuntu build also failed with a very similar error
[…]
> And also the reproducible builds build FTBFS with the same errors.

Are we still seeing this on current master? (As-of writing, that is
a6b4effc).  I ask because, as mentioned previously, I cannot reproduce
this. :)

Happy to upload if your recent changes (d6f1d04 looks promising?)
fix it.


Regards,

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

Processed: found 902774 in 9.2.24-1

[Debian Bug Tracking System]

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

> found 902774 9.2.24-1
Bug #902774 [jetty9] jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2017-7658 
CVE-2018-12536
Marked as found in versions jetty9/9.2.24-1.
> thanks
Stopping processing here.

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

Processed: retitle 902774 to jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2017-7658 CVE-2018-12536

[Debian Bug Tracking System]

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

> retitle 902774 jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2017-7658 
> CVE-2018-12536
Bug #902774 [jetty9] jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2017-7658 
CVE-2018-12536 CVE-2018-12538
Changed Bug title to 'jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2017-7658 
CVE-2018-12536' from 'jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2017-7658 
CVE-2018-12536 CVE-2018-12538'.
> thanks
Stopping processing here.

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

Bug#902868: [src:linux] linux-image-4.16.0-2-amd64 fails to start X-Server

[Leo]

Package: src:linux
Version: 4.16.16-2

--- Please enter the report below this line. ---
Ich kann den Fehler bestätigen und weiter eingrenzen. Ich komme bis zum
Start des X-Servers und dann kommt erst der Fehler. Ein neu kompilieren
des NVIDIA Treibers brachte keinen erfolgt. Mein System friert
vollkommen ein (kein "NUM" mehr möglich)
-
I can confirm the error and narrow it down further. I come to the start
of the X server and then comes first the error. A recompilation of the
NVIDIA driver did not take place. My system freezes completely (no "NUM"
possible anymore)

/var/log/kern.log
Jul 2 19:19:22 APC kernel: [ 15.41] [ cut here ]
Jul 2 19:19:22 APC kernel: [ 15.45] Bad or missing usercopy
whitelist? Kernel memory exposure attempt detected from SLUB object
'nvidia_stack_cache' (offset 11440, size 3)!
Jul 2 19:19:22 APC kernel: [ 15.57] WARNING: CPU: 1 PID: 804 at
/build/linux-hny3SU/linux-4.16.5/mm/usercopy.c:81 usercopy_warn+0x7e/0xa0
Jul 2 19:19:22 APC kernel: [ 15.58] Modules linked in: pci_stub
vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) iptable_filter cmac
uinput bnep binfmt_misc fuse xfs snd_hda_codec_hdmi tda18212dd(O)
snd_hda_codec_realtek sn
d_hda_codec_generic joydev snd_hda_intel snd_hda_codec snd_hda_core
iTCO_wdt iTCO_vendor_support intel_powerclamp snd_hwdep kvm_intel kvm
btusb btrtl btbcm btintel bluetooth drbg evdev ansi_cprng serio_raw
pcspkr ecdh_generic rfkill irqb
ypass intel_cstate intel_uncore stv0367dd(O) i7core_edac snd_pcm_oss
ddbridge(O) snd_mixer_oss cxd2099(O) snd_pcm dvb_core(O) snd_timer snd
shpchp soundcore sg lpc_ich button acpi_cpufreq nvidia_drm(PO) sunrpc
drm_kms_helper drm nvidia_m
odeset(PO) nvidia(PO) ipmi_devintf ipmi_msghandler it87 hwmon_vid
coretemp loop parport_pc ppdev lp parport ip_tables x_tables autofs4
Jul 2 19:19:22 APC kernel: [ 15.97] ext4 crc16 mbcache jbd2 fscrypto
ecb crypto_simd cryptd glue_helper aes_x86_64 raid10 raid456
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq
libcrc32c crc32c_gene
ric raid0 multipath linear raid1 md_mod sr_mod cdrom sd_mod hid_generic
usbhid hid ahci libahci libata crc32c_intel scsi_mod ehci_pci xhci_pci
i2c_i801 uhci_hcd xhci_hcd ehci_hcd r8169 mii usbcore usb_common
Jul 2 19:19:22 APC kernel: [ 15.222321] CPU: 1 PID: 804 Comm: Xorg
Tainted: P O 4.16.0-1-amd64 #1 Debian 4.16.5-1
Jul 2 19:19:22 APC kernel: [ 15.222322] Hardware name: Gigabyte
Technology Co., Ltd. P55A-UD3/P55A-UD3, BIOS F11 08/10/2010
Jul 2 19:19:22 APC kernel: [ 15.222325] RIP: 0010:usercopy_warn+0x7e/0xa0
Jul 2 19:19:22 APC kernel: [ 15.222326] RSP: 0018:a44f82babb60
EFLAGS: 00010282
Jul 2 19:19:22 APC kernel: [ 15.222328] RAX:  RBX:
988a8a142cb0 RCX: 0006
Jul 2 19:19:22 APC kernel: [ 15.222330] RDX: 0007 RSI:
0096 RDI: 988aafc56730
Jul 2 19:19:22 APC kernel: [ 15.222331] RBP: 0003 R08:
03b6 R09: 0007
Jul 2 19:19:22 APC kernel: [ 15.222333] R10: 89a769d0 R11:
8a1a8dcd R12: 0001
Jul 2 19:19:22 APC kernel: [ 15.222334] R13: 988a8a142cb3 R14:
 R15: 988a8a142cf8
Jul 2 19:19:22 APC kernel: [ 15.222336] FS: 7f64dcc796c0()
GS:988aafc4() knlGS:
Jul 2 19:19:22 APC kernel: [ 15.222338] CS: 0010 DS:  ES:  CR0:
80050033
Jul 2 19:19:22 APC kernel: [ 15.222339] CR2: 7f64d4d65010 CR3:
00020f29 CR4: 06e0
Jul 2 19:19:22 APC kernel: [ 15.222341] Call Trace:
Jul 2 19:19:22 APC kernel: [ 15.222346] __check_object_size+0x9c/0x1a0
Jul 2 19:19:22 APC kernel: [ 15.222581] os_memcpy_to_user+0x21/0x40 [nvidia]
Jul 2 19:19:22 APC kernel: [ 15.222759] _nv009377rm+0xbf/0xe0 [nvidia]
Jul 2 19:19:22 APC kernel: [ 15.222918] ? _nv028067rm+0x79/0x90 [nvidia]
Jul 2 19:19:22 APC kernel: [ 15.223077] ? _nv028067rm+0x55/0x90 [nvidia]
Jul 2 19:19:22 APC kernel: [ 15.223227] ? _nv013694rm+0xee/0x100 [nvidia]
Jul 2 19:19:22 APC kernel: [ 15.223377] ? _nv015342rm+0x154/0x270 [nvidia]
Jul 2 19:19:22 APC kernel: [ 15.223552] ? _nv008310rm+0x134/0x1a0 [nvidia]
Jul 2 19:19:22 APC kernel: [ 15.223727] ? _nv008289rm+0x29c/0x2b0 [nvidia]
Jul 2 19:19:22 APC kernel: [ 15.223903] ? _nv001072rm+0xe/0x20 [nvidia]
Jul 2 19:19:22 APC kernel: [ 15.224080] ? _nv007316rm+0xd8/0x100 [nvidia]
Jul 2 19:19:22 APC kernel: [ 15.224236] ? _nv001171rm+0x627/0x830 [nvidia]
Jul 2 19:19:22 APC kernel: [ 15.224388] ? rm_ioctl+0x73/0x100 [nvidia]
Jul 2 19:19:22 APC kernel: [ 15.224499] ? nvidia_ioctl+0xf0/0x720 [nvidia]
Jul 2 19:19:22 APC kernel: [ 15.224609] ? nvidia_ioctl+0x519/0x720 [nvidia]
Jul 2 19:19:22 APC kernel: [ 15.224613] ? kmem_cache_free+0x19c/0x1d0
Jul 2 19:19:22 APC kernel: [ 15.224722] ?
nvidia_frontend_unlocked_ioctl+0x3e/0x50 [nvidia]
Jul 2 19:19:22 APC kernel: [ 15.224725] ? do_vfs_ioctl+0xa4/0x630
Jul 2 19:19:22 APC kernel: [ 15.224727] ? __fput+0x164/0x1e0
Jul 2 

Bug#874526: Keyboard grab doesn't work under Wayland

[Simon McVittie]

On Wed, 06 Sep 2017 at 14:58:37 -0700, Josh Triplett wrote:
> (It might also help to add Ctrl-Alt-Delete to the list of shortcuts
> provided in the gnome-boxes keyboard menu, alongside Ctrl-Alt-Backspace
> and similar.)

This is now provided in the keyboard menu for both gnome-boxes and
virt-manager.

smcv

Processed: Re: Bug#874526: Keyboard grab doesn't work under Wayland

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 Keyboard grab doesn't (always?) work under Wayland
Bug #874526 {Done: Simon McVittie } [gnome-boxes] Keyboard 
grab doesn't work under Wayland
Changed Bug title to 'Keyboard grab doesn't (always?) work under Wayland' from 
'Keyboard grab doesn't work under Wayland'.
> reopen -1
Bug #874526 {Done: Simon McVittie } [gnome-boxes] Keyboard 
grab doesn't (always?) work under Wayland
'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 3.28.5-1.
> tags -1 + moreinfo
Bug #874526 [gnome-boxes] Keyboard grab doesn't (always?) work under Wayland
Added tag(s) moreinfo.

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

Bug#874526: Keyboard grab doesn't work under Wayland

[Simon McVittie]

Control: retitle -1 Keyboard grab doesn't (always?) work under Wayland
Control: reopen -1
Control: tags -1 + moreinfo

On Mon, 02 Jul 2018 at 01:39:24 -0700, Josh Triplett wrote:
> On Mon, Jul 02, 2018 at 08:14:48AM +0100, Simon McVittie wrote:
> > This seems to work under GNOME 3.28 (probably also 3.26). I'm prompted
> > while starting up the VM for whether to allow gnome-boxes to grab the
> > keyboard. I haven't tried a Windows VM, but if I use the keyboard menu to
> > switch to a text-mode VT for a Linux VM with Ctrl+Alt+F$n, then either
> > press Ctrl+Alt+Del or send it via the keyboard menu, the VM reboots
> > as expected.
> 
> I can confirm that I can still reproduce this with current GNOME and
> gnome-boxes; Ctrl+Alt+Del still goes to GNOME and not to the VM.

Which versions of gnome-shell, libmutter-2-0, gnome-boxes do you have?

Are you prompted for whether to let gnome-boxes inhibit shortcuts? You
should get a system-modal dialog (the sort that dims the entire screen,
like the Shut Down dialog you get from Ctrl+Alt+Del itself) something
like this:

|--|
|  Boxes wants to inhibit shortcuts|
| /!\  |
|  You can restore shortcuts by pressing Super+Escape. |
|  |
|[ Deny ][ Allow ]-|

(If you don't click Allow then this feature is not expected to work.)

Does it help to click inside the virtual machine window before pressing
Ctrl+Alt+Del?

If you try using virt-manager instead of gnome-boxes (the same machines
should appear in both), does that work any better?

Does sending Ctrl+Alt+Del via the keyboard menu work?

Thanks,
smcv

Bug#901110: Bug #901110 in libgdamm5.0 marked as pending

[Simon McVittie]

Control: tag -1 pending

Hello,

Bug #901110 in libgdamm5.0 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/gnome-team/libgdamm5.0/commit/5cf9e8d11d5d6a397978a5b3b4c9f03801e63eb3


Delete *.la in override_dh_auto_install, not override_dh_install-arch

This means *.la are deleted in both arch-dep and arch-indep builds,
fixing FTBFS in dh_missing --fail-missing with dpkg-buildpackage -A.

For symmetry, also delete jquery.js in override_dh_auto_install, and
print their names as we delete them.

Closes: #901110



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/901110

Processed: Bug #901110 in libgdamm5.0 marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #901110 [src:libgdamm5.0] libgdamm5.0: FTBFS when built with 
dpkg-buildpackage -A
Added tag(s) pending.

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

Bug#895599: marked as done (ganeti-2.15 - Fails to export vm: certificate is valid but its commonName does not match hostname)

[Debian Bug Tracking System]

Your message dated Mon, 02 Jul 2018 16:47:12 +
with message-id 
and subject line Bug#895599: fixed in ganeti 2.15.2-7+deb9u2
has caused the Debian Bug report #895599,
regarding ganeti-2.15 - Fails to export vm: certificate is valid but its 
commonName does not match hostname
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.)


-- 
895599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895599
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ganeti
Version: 2.15.2-7+deb9u1
Severity: grave

All vm exports fail with:

| 2018-04-13 09:23:25,650: socat: E certificate is valid but its commonName 
does not match hostname

This is fixed in 2.16.

Bastian

-- 
Bastian Blank
Berater
Telefon: +49 2166 9901-194
E-Mail: bastian.bl...@credativ.de
credativ GmbH, HRB Mönchengladbach 12080, USt-ID-Nummer: DE204566209
Trompeterallee 108, 41189 Mönchengladbach
Geschäftsführung: Dr. Michael Meskes, Jörg Folz, Sascha Heuer
--- End Message ---
--- Begin Message ---
Source: ganeti
Source-Version: 2.15.2-7+deb9u2

We believe that the bug you reported is fixed in the latest version of
ganeti, 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 895...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Apollon Oikonomopoulos  (supplier of updated ganeti 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: Mon, 11 Jun 2018 17:42:10 +0300
Source: ganeti
Binary: ganeti2 ganeti ganeti-2.15 ganeti-haskell-2.15 ganeti-htools 
ganeti-htools-2.15 ganeti-doc python-ganeti-rapi
Architecture: source all amd64
Version: 2.15.2-7+deb9u2
Distribution: stretch
Urgency: medium
Maintainer: Debian Ganeti Team 
Changed-By: Apollon Oikonomopoulos 
Description:
 ganeti - cluster virtualization manager
 ganeti-2.15 - cluster virtualization manager - Python components
 ganeti-doc - cluster virtualization manager - documentation
 ganeti-haskell-2.15 - cluster virtualization manager - Haskell components
 ganeti-htools - cluster virtualization manager - tools (stand-alone)
 ganeti-htools-2.15 - cluster virtualization manager - tools for Ganeti 2.15
 ganeti2- transitional dummy package
 python-ganeti-rapi - cluster virtualization manager - RAPI client library
Closes: 895599
Changes:
 ganeti (2.15.2-7+deb9u2) stretch; urgency=medium
 .
   * Properly verify SSL certificates during VM export (Closes: #895599)
Checksums-Sha1:
 7aed8d8bea1ac8fabebfd7631b8f80bd452a9f0a 3430 ganeti_2.15.2-7+deb9u2.dsc
 7681c1e99ac4a74874eb68e980f4ef1464f95a19 70376 
ganeti_2.15.2-7+deb9u2.debian.tar.xz
 23bcd2d20bf9e5406f8d3e24ea04238ad6b1819e 866946 
ganeti-2.15_2.15.2-7+deb9u2_all.deb
 d853014ee74c59ee23eff3374413b9708e846a3b 961794 
ganeti-doc_2.15.2-7+deb9u2_all.deb
 02df14d7f782dd1e78d255f081d052bc466e9a09 7523124 
ganeti-haskell-2.15-dbgsym_2.15.2-7+deb9u2_amd64.deb
 5c5aa5e2ccfd0bb5be01152f07a80b2c0e721572 14175794 
ganeti-haskell-2.15_2.15.2-7+deb9u2_amd64.deb
 e540c4c01d9c743e9014cf04787a14bbe7166861 1624814 
ganeti-htools-2.15-dbgsym_2.15.2-7+deb9u2_amd64.deb
 34ab100f9302d54b504f242d88af5dc441a11708 2695606 
ganeti-htools-2.15_2.15.2-7+deb9u2_amd64.deb
 a3477aeb6d093ca5230c84d80c35103f7270a0dd 21214 
ganeti-htools_2.15.2-7+deb9u2_all.deb
 d1ee61b6c1c6677b1d7104597fe8f090ca33f2ba 77442 ganeti2_2.15.2-7+deb9u2_all.deb
 3057bf5286cc833ac6f34bb6e9c8a42710d44d31 98082 ganeti_2.15.2-7+deb9u2_all.deb
 7a8c8670dd540add3b0b53fe91610a283ebd18ac 15885 
ganeti_2.15.2-7+deb9u2_amd64.buildinfo
 2a55d8bf61b1537cccaf3d6486304186131f7290 33728 
python-ganeti-rapi_2.15.2-7+deb9u2_all.deb
Checksums-Sha256:
 783fafd14f28e60d4e848064a003707e751466463f60a656b6d7a9494e295b2e 3430 
ganeti_2.15.2-7+deb9u2.dsc
 a6f4cfcbb1528cf4eab6173e2cb3c9e567615d367521172f86d105268bd7be05 70376 
ganeti_2.15.2-7+deb9u2.debian.tar.xz
 26a46ca3b080a2c2f33443959a326aaa2000d0c591b8865d3796c83937cef9d6 866946 
ganeti-2.15_2.15.2-7+deb9u2_all.deb
 bbd7d29cffa4ef52688e91ca84723b2469e206a7fede2f776cc97e14b2ced9ca 961794 
ganeti-doc_2.15.2-7+deb9u2_all.deb
 11172cf405c94d73f6c078e0434005bf1af57ca9973d635d0a83a8b6a6781f95 7523124 
ganeti-haskell-2.15-dbgsym_2.15.2-7+deb9u2_amd64.deb
 

Bug#897429: marked as done (ppc64el: Shared Object not available in the platform)

[Debian Bug Tracking System]

Your message dated Mon, 02 Jul 2018 16:47:13 +
with message-id 
and subject line Bug#897429: fixed in tclreadline 2.1.0-15+deb9u1
has caused the Debian Bug report #897429,
regarding ppc64el: Shared Object not available in the platform
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.)


-- 
897429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897429
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tclreadline
Version: 2.1.0-15
Severity: critical
Tags: patch

Dear maintainer,

I just found that this package is not generating the shared object for
ppc64el platform, as showed below:

  dpkg -c tcl-tclreadline_2.1.0-15_ppc64el.deb | grep lib/powerpc64le-linux-gnu
  drwxr-xr-x root/root 0 2016-10-08 05:04 
./usr/lib/powerpc64le-linux-gnu/
  -rw-r--r-- root/root 25340 2016-10-08 05:04 
./usr/lib/powerpc64le-linux-gnu/libtclreadline.a

Looking at the 'configure' process, I see the failure on detecting if
the shared object should be built. This is the build log line and
explains the problem.

  checking whether to build shared libraries... no

I checked against unstable/buster version (2.3) and this problem does
not happen anymore. So, this fix will only need to make Stretch.

The real cause of this problem is realted to the following exemption of
powerpc, which might be removed.

   case "$host_cpu" in
powerpc*) dynamic_linker=no ;
*) dynamic_linker='Linux ld.so' ;;


With the patch above, I can see the shared objects being generated:

  dpkg -c tcl-tclreadline_2.1.0-15+deb9u1_ppc64el.deb  | grep \.so
  -rw-r--r-- root/root 67664 2018-05-02 10:05 
./usr/lib/powerpc64le-linux-gnu/libtclreadline-2.1.0.so
  lrwxrwxrwx root/root 0 2018-05-02 10:05 
./usr/lib/powerpc64le-linux-gnu/libtclreadline.so -> libtclreadline-2.1.0.so
--- End Message ---
--- Begin Message ---
Source: tclreadline
Source-Version: 2.1.0-15+deb9u1

We believe that the bug you reported is fixed in the latest version of
tclreadline, 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 897...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sergei Golovan  (supplier of updated tclreadline 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: Mon, 02 Jul 2018 09:33:03 +0300
Source: tclreadline
Binary: tcl-tclreadline
Architecture: source amd64
Version: 2.1.0-15+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian Tcl/Tk Packagers 
Changed-By: Sergei Golovan 
Description:
 tcl-tclreadline - GNU Readline Extension for Tcl/Tk
Closes: 897429
Changes:
 tclreadline (2.1.0-15+deb9u1) stretch; urgency=medium
 .
   * Add a patch by Breno Leitao which fixes building the shared library for
the ppc64el architecture (closes: #897429).
Checksums-Sha1:
 241405780838ffadff47b90a507573c694cfae74 1939 tclreadline_2.1.0-15+deb9u1.dsc
 814585ca78d28705044ded14a210d1c2a8345182 10316 
tclreadline_2.1.0-15+deb9u1.debian.tar.xz
 1aa6fc780ba393470c437dcf4c319ebd6223739a 33888 
tcl-tclreadline-dbgsym_2.1.0-15+deb9u1_amd64.deb
 bc80b0b883524294146d47c75deebc6f890f8625 56554 
tcl-tclreadline_2.1.0-15+deb9u1_amd64.deb
 de5a8dfa1e93e207257f79137d834d47cbe85d60 6373 
tclreadline_2.1.0-15+deb9u1_amd64.buildinfo
Checksums-Sha256:
 5136ddee2a244e71436192d2f9fdff1e6c5c75dc3c4785f7d89b852101d3dfa9 1939 
tclreadline_2.1.0-15+deb9u1.dsc
 412c7858fd03d6b3ce256ee0ed2afba423bc97ba3697a42a2c356cd5333f02cf 10316 
tclreadline_2.1.0-15+deb9u1.debian.tar.xz
 909acb617b962b7166d88a8ee371b954c8e2f84f356b2bef092cb8d5dc462a0c 33888 
tcl-tclreadline-dbgsym_2.1.0-15+deb9u1_amd64.deb
 677928c3707b23d398c8d8d96ba7e28d6ae503fd2f6d58b1a2ef2f735046b1d0 56554 
tcl-tclreadline_2.1.0-15+deb9u1_amd64.deb
 70fdcbe7a06f8d0807e6cc83321b0c28aa03f5438388783659f81ae77ab0fba4 6373 
tclreadline_2.1.0-15+deb9u1_amd64.buildinfo
Files:
 0360ce7a2051c1a5e2dcbf8e8e7941de 1939 devel optional 
tclreadline_2.1.0-15+deb9u1.dsc
 651cead42f802d4f1f5edb1767b313b8 10316 devel optional 
tclreadline_2.1.0-15+deb9u1.debian.tar.xz
 7d09c9e733fa6335edb48be848044a54 33888 debug extra 
tcl-tclreadline-dbgsym_2.1.0-15+deb9u1_amd64.deb
 91c50549eaccc1aacf0aa1b363423479 56554 devel 

Bug#902872: sagemath: sage fails to start with 'undefined symbol acb_calc_integrate error

[Rann Bar-On]

Package: sagemath
Version: 8.2-5
Severity: grave
Justification: renders package unusable

Dear Maintainer,

see sage crash log below.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (800, 'testing'), (750, 'unstable'), (500, 'unstable-debug'), 
(500, 'testing-debug'), (500, 'stable-updates'), (500, 'proposed-updates'), 
(500, 'oldstable-updates'), (500, 'stable'), (500, 'oldstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.16.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)

Versions of packages sagemath depends on:
ii  cysignals-tools  1.6.7+ds-1
ii  cython   0.28.2-4
ii  ecl  16.1.2-4+b1
ii  eclib-tools  20171002-1+b2
ii  f2c  20160102-1
ii  fflas-ffpack 2.3.2-2
ii  flintqs  1:1.0-1+b1
ii  gap-core 4r8p8-3
ii  gfan 0.5+dfsg-6
ii  gmp-ecm  7.0.4+ds-2
ii  ipython  5.5.0-1
ii  iso-codes3.79-1
ii  jmol 14.6.4+2016.11.05+dfsg1-3.1
ii  lcalc1.23+dfsg-6+b1
ii  less 487-0.1+b1
ii  libatlas3-base [liblapack.so.3]  3.10.3-7
ii  libblas3 [libblas.so.3]  3.8.0-1
ii  libbrial-groebner3   1.2.0-2
ii  libbrial31.2.0-2
ii  libc62.27-3
ii  libcdd-tools 094h-1+b1
ii  libcliquer1  1.21-2
ii  libec3   20171002-1+b2
ii  libecm1  7.0.4+ds-2
ii  libflint-2.5.2   2.5.2-18
ii  libflint-arb22.11.1-2+b1
ii  libgap-sage-44.8.8+3+20160327g69a66f0+dsx-1
ii  libgcc1  1:8.1.0-9
ii  libgd3   2.2.5-4
ii  libgivaro9   4.0.4-2
ii  libglpk404.65-2
ii  libgmp10 2:6.1.2+dfsg-3
ii  libgmpxx4ldbl2:6.1.2+dfsg-3
ii  libgsl23 2.5+dfsg-4
ii  libgslcblas0 2.5+dfsg-4
ii  libiml0  1.0.4-1+b2
ii  libjs-mathjax2.7.4+dfsg-1
ii  libjs-three  80+dfsg2-2
ii  liblapack3 [liblapack.so.3]  3.8.0-1
ii  liblfunction01.23+dfsg-6+b1
ii  liblinbox-1.5.2-01.5.2-1
ii  liblinboxsage-1.5.2-01.5.2-1
ii  liblrcalc1   1.2-2+b1
ii  libm4ri-0.0.20140914 20140914-2+b1
ii  libm4rie-0.0.2015090820150908-1
ii  libmpc3  1.1.0-1
ii  libmpfi0 1.5.3+ds-2
ii  libmpfr6 4.0.1-1
ii  libntl35 10.5.0-2
ii  libpari-gmp-tls5 2.9.5-1
ii  libplanarity03.0.0.5-1+b1
ii  libpng16-16  1.6.34-1
ii  libppl14 1:1.2-3
ii  libpynac17   0.7.19-2
ii  libratpoints-2.1.3   1:2.1.3-1+b2
ii  libreadline7 7.0-5
ii  librw0   0.8+ds-1
ii  libsingular4 1:4.1.0-p3+ds-2+b3
ii  libstdc++6   8.1.0-9
ii  libsymmetrica2   2.0+ds-5
ii  libzn-poly-0.9   0.9-3+b2
ii  maxima-sage  5.39.0+ds-3
ii  maxima-sage-doc  5.39.0+ds-3
ii  maxima-sage-share5.39.0+ds-3
ii  nauty2.6r10+ds-1
ii  octave   4.4.0-3
ii  palp 2.1-4
ii  pari-doc 2.9.5-1
ii  pari-galdata 0.20080411-2
ii  pari-gp  2.9.5-1
ii  pari-seadata   

Bug#902866: flameshot: Will not run, exits with error "Could not connect to display"

[Boyuan Yang]

Control: severity -1 important
Control: tag -1 + moreinfo

在 2018年7月2日星期一 CST 下午10:33:29，Prescott 写道：
> Package: flameshot
> Version: 0.5.1+git20180601-1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
>Upgraded to testing from stable for help in bugs finding and for
>some newer packages I needed from Buster.
> 
>I originally used my sxhkd keybinding "flameshot gui -p
>~/path/to/file", and when the usual action of the gui selection
>screen did not appear, I ran flameshot gui through the terminal. The
>following is the error messages in syslog.
> 
> Jul  2 09:17:12 plaptop dbus-daemon[2082]: [session uid=1000 pid=2082]
> Activating service name='org.dharkael.Flameshot' requested by ':1.1310'
> (uid=1000 pid=22598 comm="flameshot gui ") Jul  2 09:17:12 plaptop
> org.dharkael.Flameshot[2082]: qt.qpa.screen: QXcbConnection: Could not
> connect to display Jul  2 09:17:12 plaptop org.dharkael.Flameshot[2082]:
> Could not connect to any X display. Jul  2 09:17:12 plaptop
> dbus-daemon[2082]: [session uid=1000 pid=2082] Activated service
> 'org.dharkael.Flameshot' failed: Process org.dharkael.Flameshot exited with
> status 1 Jul  2 09:17:45 plaptop dbus-daemon[2082]: [session uid=1000
> pid=2082] Activating service name='org.dharkael.Flameshot' requested by
> ':1.1315' (uid=1000 pid=23133 comm="flameshot gui ") Jul  2 09:17:45
> plaptop org.dharkael.Flameshot[2082]: qt.qpa.screen: QXcbConnection: Could
> not connect to display Jul  2 09:17:45 plaptop
> org.dharkael.Flameshot[2082]: Could not connect to any X display. Jul  2
> 09:17:45 plaptop dbus-daemon[2082]: [session uid=1000 pid=2082] Activated
> service 'org.dharkael.Flameshot' failed: Process org.dharkael.Flameshot
> exited with status 1 cat: m: No such file or directory
> 
>The same QXcbConnection message appears when running a CLI command
>(e.g. flameshot screen -c).
> 
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (900, 'testing')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.16.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 flameshot depends on:
> ii  libc6   2.27-3
> ii  libgcc1 1:8.1.0-8
> ii  libqt5core5a5.10.1+dfsg-7
> ii  libqt5dbus5 5.10.1+dfsg-7
> ii  libqt5gui5  5.10.1+dfsg-7
> ii  libqt5network5  5.10.1+dfsg-7
> ii  libqt5widgets5  5.10.1+dfsg-7
> ii  libstdc++6  8.1.0-8
> 
> flameshot recommends no packages.
> 
> Versions of packages flameshot suggests:
> ii  ca-certificates  20170717
> ii  openssl  1.1.0h-4
> 
> -- no debconf information

Hi,

This look quite weird and I could not reproduce it on my laptop. I need some 
extra information for your environment:

* What Desktop Environment / Window Manager are you using?
* Are you trying to run flameshot remotely? (e.g., via ssh -X X-forwarding or 
RDP)?

--
Thanks,
Boyuan Yang

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

Processed: Re: Bug#902866: flameshot: Will not run, exits with error "Could not connect to display"

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #902866 [flameshot] flameshot: Will not run, exits with error "Could not 
connect to display"
Severity set to 'important' from 'grave'
> tag -1 + moreinfo
Bug #902866 [flameshot] flameshot: Will not run, exits with error "Could not 
connect to display"
Added tag(s) moreinfo.

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

Bug#902868: linux-image-4.16.0-2-amd64 fails to boot

[Andy Wood]

Package: src:linux
Version: 4.16.16-2
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

   * What led up to the situation?

Up to date Debian testing on 2 July 2018
apt-get update
apt-get upgrade
   linux-image-4.16.0-2-amd64 updated (I think)
reboot

   * What was the outcome of this action?

System did not boot
Re-booted into previous kernel version and reviewed system logs
The following seems to indicate the fault:

Jul  2 09:04:31 kernel: [   15.055880] [ cut here ]
Jul  2 09:04:31 kernel: [   15.055881] kernel BUG at 
/build/linux-uwVqDp/linux-4.16.16/mm/usercopy.c:100!
Jul  2 09:04:31 kernel: [   15.055888] invalid opcode:  [#1] SMP PTI
Jul  2 09:04:31 kernel: [   15.055890] Modules linked in: intel_rapl sb_edac 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_hda_codec_hdmi 
irqbypass iTCO_wdt iTCO_vendor_support crct10dif_pclmul crc32_pclmul mxm_wmi 
evdev ghash_clmulni_intel intel_cstate intel_uncore intel_rapl_perf pcspkr 
serio_raw snd_hda_codec_realtek snd_hda_codec_generic sg lpc_ich snd_hda_intel 
snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_timer ioatdma snd mei_me mei 
soundcore shpchp dca wmi button nvidia_drm(PO) drm_kms_helper drm 
nvidia_modeset(PO) nvidia(PO) ipmi_devintf ipmi_msghandler parport_pc ppdev lp 
parport ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic 
fscrypto ecb sr_mod cdrom sd_mod hid_generic usbhid hid crc32c_intel ahci isci 
aesni_intel libahci libsas aes_x86_64 crypto_simd cryptd glue_helper psmouse
Jul  2 09:04:31 kernel: [   15.055943]  sym53c8xx scsi_transport_spi xhci_pci 
i2c_i801 libata ehci_pci xhci_hcd ehci_hcd scsi_transport_sas e1000e usbcore 
scsi_mod usb_common
Jul  2 09:04:31 kernel: [   15.055954] CPU: 2 PID: 1184 Comm: Xorg Tainted: P   
O 4.16.0-2-amd64 #1 Debian 4.16.16-2
Jul  2 09:04:31 kernel: [   15.055956] Hardware name: Viglen VIG430P/X9DAL, 
BIOS 3.0 01/02/2014
Jul  2 09:04:31 kernel: [   15.055963] RIP: 0010:usercopy_abort+0x69/0x80
Jul  2 09:04:31 kernel: [   15.055965] RSP: 0018:b81543c9bb50 EFLAGS: 
00010282
Jul  2 09:04:31 kernel: [   15.055967] RAX: 006f RBX: 
0003 RCX: 
Jul  2 09:04:31 kernel: [   15.055969] RDX:  RSI: 
8d90ffd16738 RDI: 8d90ffd16738
Jul  2 09:04:31 kernel: [   15.055971] RBP: 0003 R08: 
03ac R09: 0004
Jul  2 09:04:31 kernel: [   15.055972] R10: ad877e48 R11: 
adfa8dcd R12: 0001
Jul  2 09:04:31 kernel: [   15.055974] R13: 8d90d828dcb3 R14: 
 R15: 8d90d828dcf8
Jul  2 09:04:31 kernel: [   15.055977] FS:  7f841b5f96c0() 
GS:8d90ffd0() knlGS:
Jul  2 09:04:31 kernel: [   15.055979] CS:  0010 DS:  ES:  CR0: 
80050033
Jul  2 09:04:31 kernel: [   15.055981] CR2: 7f8413711010 CR3: 
0004583c8005 CR4: 000606e0
Jul  2 09:04:31 kernel: [   15.055982] Call Trace:
Jul  2 09:04:31 kernel: [   15.055992]  __check_heap_object+0xe7/0x120
Jul  2 09:04:31 kernel: [   15.055995]  __check_object_size+0x9c/0x1a0
Jul  2 09:04:31 kernel: [   15.056199]  os_memcpy_to_user+0x21/0x40 [nvidia]
Jul  2 09:04:31 kernel: [   15.056416]  _nv009377rm+0xbf/0xe0 [nvidia]
Jul  2 09:04:31 kernel: [   15.056600]  ? _nv028067rm+0x79/0x90 [nvidia]
Jul  2 09:04:31 kernel: [   15.056780]  ? _nv028067rm+0x55/0x90 [nvidia]
Jul  2 09:04:31 kernel: [   15.056950]  ? _nv013694rm+0xee/0x100 [nvidia]
Jul  2 09:04:31 kernel: [   15.057120]  ? _nv015342rm+0x154/0x270 [nvidia]
Jul  2 09:04:31 kernel: [   15.057336]  ? _nv008310rm+0x134/0x1a0 [nvidia]
Jul  2 09:04:31 kernel: [   15.057548]  ? _nv008289rm+0x29c/0x2b0 [nvidia]
Jul  2 09:04:31 kernel: [   15.057759]  ? _nv001072rm+0xe/0x20 [nvidia]
Jul  2 09:04:31 kernel: [   15.057972]  ? _nv007316rm+0xd8/0x100 [nvidia]
Jul  2 09:04:31 kernel: [   15.058181]  ? _nv001171rm+0x627/0x830 [nvidia]
Jul  2 09:04:31 kernel: [   15.058389]  ? rm_ioctl+0x73/0x100 [nvidia]
Jul  2 09:04:31 kernel: [   15.058507]  ? nvidia_ioctl+0xf0/0x720 [nvidia]
Jul  2 09:04:31 kernel: [   15.058623]  ? nvidia_ioctl+0x519/0x720 [nvidia]
Jul  2 09:04:31 kernel: [   15.058627]  ? kmem_cache_free+0x19c/0x1d0
Jul  2 09:04:31 kernel: [   15.058743]  ? 
nvidia_frontend_unlocked_ioctl+0x3e/0x50 [nvidia]
Jul  2 09:04:31 kernel: [   15.058746]  ? do_vfs_ioctl+0xa4/0x630
Jul  2 09:04:31 kernel: [   15.058750]  ? __audit_syscall_entry+0xbc/0x110
Jul  2 09:04:31 kernel: [   15.058754]  ? syscall_trace_enter+0x1df/0x2e0
Jul  2 09:04:31 kernel: [   15.058757]  ? SyS_ioctl+0x74/0x80
Jul  2 09:04:31 kernel: [   15.058760]  ? do_syscall_64+0x6c/0x130
Jul  2 09:04:31 kernel: [   15.058764]  ? 
entry_SYSCALL_64_after_hwframe+0x3d/0xa2
Jul  2 09:04:31 kernel: [   15.058767] Code: 0f 44 d0 53 48 c7 c0 41 de 83 ad 
51 48 c7 c6 dd d3 82 ad 41 53 48 89 f9 48 0f 45 f0 4c 89 d2 48 c7 c7 28 df 83 
ad e8 f1 2e ea ff <0f> 0b 49 c7 c1 ac de 84 ad 4d 89 cb 4d 

Bug#899704: marked as done (sympa: Invalid maintainer address pkg-sympa-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Mon, 02 Jul 2018 14:39:20 +
with message-id 
and subject line Bug#899704: fixed in sympa 6.2.32~dfsg-2
has caused the Debian Bug report #899704,
regarding sympa: Invalid maintainer address 
pkg-sympa-de...@lists.alioth.debian.org
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.)


-- 
899704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899704
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sympa
Version: 6.2.32~dfsg-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of sympa,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package sympa since the list address
pkg-sympa-de...@lists.alioth.debian.org used in the Maintainer: field
was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-sympa-de...@lists.alioth.debian.org is 2.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: sympa
Source-Version: 6.2.32~dfsg-2

We believe that the bug you reported is fixed in the latest version of
sympa, 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 899...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Emmanuel Bouthenot  (supplier of updated sympa 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: Tue, 26 Jun 2018 17:46:40 +
Source: sympa
Binary: sympa
Architecture: source amd64
Version: 6.2.32~dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Sympa team 
Changed-By: Emmanuel Bouthenot 
Description:
 sympa  - Modern mailing list manager
Closes: 899704
Changes:
 sympa (6.2.32~dfsg-2) unstable; urgency=medium
 .
   * Update Maintainer email to use sy...@packages.debian.org
   (Closes: #899704)
Checksums-Sha1:
 63f91d9c2f635c112422654d0d11ee0e3fdde30c 2460 sympa_6.2.32~dfsg-2.dsc
 8176ed864d1a4026b68f1bab50928818424c7a75 171764 
sympa_6.2.32~dfsg-2.debian.tar.xz
 96a51dcf2393822995770d2ca23ab7e9218444b8 18312 
sympa-dbgsym_6.2.32~dfsg-2_amd64.deb
 ec8782253df1cd74499efb976d3ae825d5d3b8f8 7542 
sympa_6.2.32~dfsg-2_amd64.buildinfo
 aa5b100b9df9e44b5a82517d7505b12e50f46513 2658504 sympa_6.2.32~dfsg-2_amd64.deb
Checksums-Sha256:
 565c29aa4eb59484be672d1d25596d6c4adf64ee14c9e23849bd4e6ff89437ee 2460 
sympa_6.2.32~dfsg-2.dsc
 37be367c7d17baac4f79364f0f797ecf9fe241ec8023532f16b916744145d10e 171764 
sympa_6.2.32~dfsg-2.debian.tar.xz
 29969537a7f66d5abd56882998c863b6083646f1aefdf55b9b0c58f4695cdc80 18312 
sympa-dbgsym_6.2.32~dfsg-2_amd64.deb
 e3097c0b75bb1a40503419b5e86a1141e5a39d7ad273f06b74244060ea240ea0 7542 

Bug#899765: marked as done (libmime-lite-html-perl: Invalid maintainer address pkg-sympa-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Mon, 02 Jul 2018 14:35:30 +
with message-id 
and subject line Bug#899765: fixed in libmime-lite-html-perl 1.24-3
has caused the Debian Bug report #899765,
regarding libmime-lite-html-perl: Invalid maintainer address 
pkg-sympa-de...@lists.alioth.debian.org
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.)


-- 
899765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899765
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libmime-lite-html-perl
Version: 1.24-2
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of libmime-lite-html-perl,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package libmime-lite-html-perl since the list address
pkg-sympa-de...@lists.alioth.debian.org used in the Maintainer: field
was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-sympa-de...@lists.alioth.debian.org is 2.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: libmime-lite-html-perl
Source-Version: 1.24-3

We believe that the bug you reported is fixed in the latest version of
libmime-lite-html-perl, 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 899...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Emmanuel Bouthenot  (supplier of updated 
libmime-lite-html-perl 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: Mon, 02 Jul 2018 12:37:24 +
Source: libmime-lite-html-perl
Binary: libmime-lite-html-perl
Architecture: source all
Version: 1.24-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Sympa Team 
Changed-By: Emmanuel Bouthenot 
Description:
 libmime-lite-html-perl - Transform HTML page into MIME email
Closes: 899765
Changes:
 libmime-lite-html-perl (1.24-3) unstable; urgency=medium
 .
   * Update Maintainer email to use libmime-lite-html-p...@packages.debian.org
 (Closes: #899765)
   * Update d/watch to use a secure source (https)
   * Fix d/copyright Format URI to use https
   * Update homepage in d/control and d/copyright
   * Update Vcs-Git and Vcs-Browser with new repository on salsa.debian.org
   * Bump Standards-Version to 4.1.4
   * Switch debhelper compatibility to 11
   * Fix d/rules to take into account DEB_BUILD_OPTIONS=nocheck
   * Add d/upstream/metadata
Checksums-Sha1:
 988d4865843fbc596d620e681a3e0318ee179bab 2199 libmime-lite-html-perl_1.24-3.dsc
 76f23b671d3fb912336b0556cbe4a61edd51ee61 3792 
libmime-lite-html-perl_1.24-3.debian.tar.xz
 f1ff396b94875007a35fc5995d61ca9437c37b32 26952 

Bug#902866: flameshot: Will not run, exits with error "Could not connect to display"

[Prescott]

Package: flameshot
Version: 0.5.1+git20180601-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   Upgraded to testing from stable for help in bugs finding and for
   some newer packages I needed from Buster.

   I originally used my sxhkd keybinding "flameshot gui -p
   ~/path/to/file", and when the usual action of the gui selection
   screen did not appear, I ran flameshot gui through the terminal. The
   following is the error messages in syslog.
   
Jul  2 09:17:12 plaptop dbus-daemon[2082]: [session uid=1000 pid=2082] 
Activating service name='org.dharkael.Flameshot' requested by ':1.1310' 
(uid=1000 pid=22598 comm="flameshot gui ")
Jul  2 09:17:12 plaptop org.dharkael.Flameshot[2082]: qt.qpa.screen: 
QXcbConnection: Could not connect to display
Jul  2 09:17:12 plaptop org.dharkael.Flameshot[2082]: Could not connect to any 
X display.
Jul  2 09:17:12 plaptop dbus-daemon[2082]: [session uid=1000 pid=2082] 
Activated service 'org.dharkael.Flameshot' failed: Process 
org.dharkael.Flameshot exited with status 1
Jul  2 09:17:45 plaptop dbus-daemon[2082]: [session uid=1000 pid=2082] 
Activating service name='org.dharkael.Flameshot' requested by ':1.1315' 
(uid=1000 pid=23133 comm="flameshot gui ")
Jul  2 09:17:45 plaptop org.dharkael.Flameshot[2082]: qt.qpa.screen: 
QXcbConnection: Could not connect to display
Jul  2 09:17:45 plaptop org.dharkael.Flameshot[2082]: Could not connect to any 
X display.
Jul  2 09:17:45 plaptop dbus-daemon[2082]: [session uid=1000 pid=2082] 
Activated service 'org.dharkael.Flameshot' failed: Process 
org.dharkael.Flameshot exited with status 1
cat: m: No such file or directory

   The same QXcbConnection message appears when running a CLI command
   (e.g. flameshot screen -c).

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

Kernel: Linux 4.16.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 flameshot depends on:
ii  libc6   2.27-3
ii  libgcc1 1:8.1.0-8
ii  libqt5core5a5.10.1+dfsg-7
ii  libqt5dbus5 5.10.1+dfsg-7
ii  libqt5gui5  5.10.1+dfsg-7
ii  libqt5network5  5.10.1+dfsg-7
ii  libqt5widgets5  5.10.1+dfsg-7
ii  libstdc++6  8.1.0-8

flameshot recommends no packages.

Versions of packages flameshot suggests:
ii  ca-certificates  20170717
ii  openssl  1.1.0h-4

-- no debconf information

Bug#902715: marked as done (python3-psycopg2 fails to install with Python 3.7)

[Debian Bug Tracking System]

Your message dated Mon, 02 Jul 2018 13:34:45 +
with message-id 
and subject line Bug#902715: fixed in psycopg2 2.7.5-2
has caused the Debian Bug report #902715,
regarding python3-psycopg2 fails to install with Python 3.7
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.)


-- 
902715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902715
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-psycopg2
Version: 2.7.5-1
Severity: serious

Setting up python3-psycopg2 (2.7.5-1+b1) ...
  File "/usr/lib/python3/dist-packages/psycopg2/tests/test_async_keyword.py", 
line 43
self.conn = self.connect(async=True)
 ^
SyntaxError: invalid syntax

dpkg: error processing package python3-psycopg2 (--configure):
 installed python3-psycopg2 package post-installation script subprocess 
returned error exit status 1
--- End Message ---
--- Begin Message ---
Source: psycopg2
Source-Version: 2.7.5-2

We believe that the bug you reported is fixed in the latest version of
psycopg2, 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 902...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nicolas Dandrimont  (supplier of updated psycopg2 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: Mon, 02 Jul 2018 14:58:20 +0200
Source: psycopg2
Binary: python-psycopg2 python-psycopg2-dbg python3-psycopg2 
python3-psycopg2-dbg python-psycopg2-doc
Architecture: source
Version: 2.7.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Nicolas Dandrimont 
Description:
 python-psycopg2 - Python module for PostgreSQL
 python-psycopg2-dbg - Python module for PostgreSQL (debug extension)
 python-psycopg2-doc - Python module for PostgreSQL (documentation package)
 python3-psycopg2 - Python 3 module for PostgreSQL
 python3-psycopg2-dbg - Python 3 module for PostgreSQL (debug extension)
Closes: 902715
Changes:
 psycopg2 (2.7.5-2) unstable; urgency=medium
 .
   * Team upload.
   * Do not install tests/test_async_keyword.py, incompatible with
 Python3.7 (Closes: #902715)
Checksums-Sha1:
 fd5625c044e200e0fc30e6648da5b27b2fe75174 2460 psycopg2_2.7.5-2.dsc
 b76e8ff146b651bf4b64bd461c98fb008f994e4a 12376 psycopg2_2.7.5-2.debian.tar.xz
 3c6b71e1aace35a2d30755323a44453950090384 10645 psycopg2_2.7.5-2_amd64.buildinfo
Checksums-Sha256:
 6d081bfbc3596eb2a5f452c52552bf803c05d3d040de3ea13f488f2a0ccaba10 2460 
psycopg2_2.7.5-2.dsc
 11324136ef712b73d5c22dde78e01b6103e13dae64c8a156fa0d1c43e3ed1aca 12376 
psycopg2_2.7.5-2.debian.tar.xz
 9821a05d3d811ebe9c070bf81b05d76e11604054ca87002cbe0935fb39782673 10645 
psycopg2_2.7.5-2_amd64.buildinfo
Files:
 acc43d9fc5a8d5935dde0a9220505477 2460 python optional psycopg2_2.7.5-2.dsc
 b89ab5e7021dd1fa07c98f2b58fa06bb 12376 python optional 
psycopg2_2.7.5-2.debian.tar.xz
 3523d0315c4a93bee75dfe7f9b07a4ce 10645 python optional 
psycopg2_2.7.5-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEeR8SOWYw3XH9NkN1uOUId2ZHWq8FAls6JIgACgkQuOUId2ZH
Wq9Jyg/+J4PxRzX9MHyWjGQA3ldXInIFfkIc5uqeUWBCFaZknIB8I7ZZmVsdjSLf
Nkzf8gJ2/zfi2wo1OVaWVFhIJjMhFBxkT9ae3NtJbvBbgJg/m16c8AEnY0a38wz5
A6W0ueiy0FRNzyC8IzLEEeRFU/b2p4UWuvWzELKAenlRmz+ndXG0sOIXMad6lWH0
iyc/0uM0uFuBlbulvZEJaDkhyr+jZ0YsQmWLooMTfHqQlnlzdTGTZKrdShTmZ7G9
bUBmH0n8QOVuZ5ZZUrdhyd0qNga1Dq0EMJQCzplKzAP6qNROGdhOHs/WKHIkzXV3
XhiMI58KfZDDjX/jVB5Pu4K9FnaTImhEdYpPYwi0osCCX2xzadqNIUsXyNCBpzos
pwKauw0JRYGdINo7r1PBP6M2k3RVM4ZUSwOFmoswXkeY7JjzytTIjtjziGDeZizI
ksQVevXDfayYuzOTRqR28bVB53xwsBJM3tHRMHDtEbdObLnCC5M4CygtvxNqi3zH
rOKpCNEzbHY9sDWLSPXSUVGbzDSzi/fJMK+ohAii33TDvtlhB3ugrj0GRSWDg29e
WqHKi6TX7ZIUx87cnzA9OgvhCVFvtbEcsxzwJnsbpMdO32wlpHhW39Wm6w0Pe63G
oGEiTl4ePFAmx5afmttzF3/PcEewd9+Rik7Xa13NNWUb/44Vfwg=
=oomN
-END PGP SIGNATURE End Message ---

Bug#902861: axis: FTBFS with Java 10 due to com.sun.net.ssl removal

[Emmanuel Bourg]

Le 02/07/2018 à 14:51, Emmanuel Bourg a écrit :

> axis fails to build with Java 10 due to the removal of the com.sun.net.ssl 
> API:
> 
>   
> ./axis/src/org/apache/axis/components/net/SunFakeTrustSocketFactory.java:24: 
> error: package com.sun.net.ssl does not exist
>   import com.sun.net.ssl.SSLContext;

It looks like this error has been triggered by the upload of
ant/1.10.3-2 and the added --release parameter on javac invocations. The
same error can be seen on other Ant based packages using the com.sun APIs.

It turns out that using "--release 7" when compiling renders the
com.sun.* packages unavailable, but with "-source 7 -target 7" it works
fine.

Bug#902715: Bug #902715 in psycopg2 marked as pending

[Nicolas Dandrimont]

Control: tag -1 pending

Hello,

Bug #902715 in psycopg2 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/python-team/modules/psycopg2/commit/44e26ac9a3854a2f7719cdbbc658f48d439b8f05


Do not install tests/test_async_keyword.py, incompatible with Python3.7

Closes: #902715



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/902715

Processed: Bug #902715 in psycopg2 marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #902715 [python3-psycopg2] python3-psycopg2 fails to install with Python 3.7
Added tag(s) pending.

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

Bug#902861: axis: FTBFS with Java 10 due to com.sun.net.ssl removal

[Emmanuel Bourg]

Source: axis
Severity: serious
Tags: sid buster
User: debian-j...@lists.debian.org
Usertags: default-java10

axis fails to build with Java 10 due to the removal of the com.sun.net.ssl API:

  ./axis/src/org/apache/axis/components/net/SunFakeTrustSocketFactory.java:24: 
error: package com.sun.net.ssl does not exist
  import com.sun.net.ssl.SSLContext;
^
  ./axis/src/org/apache/axis/components/net/SunFakeTrustSocketFactory.java:25: 
error: package com.sun.net.ssl does not exist
  import com.sun.net.ssl.TrustManager;
^
  ./axis/src/org/apache/axis/components/net/SunFakeTrustSocketFactory.java:26: 
error: package com.sun.net.ssl does not exist
  import com.sun.net.ssl.X509TrustManager;
^
  ./axis/src/org/apache/axis/components/net/SunJSSESocketFactory.java:26: 
error: package com.sun.net.ssl does not exist
  import com.sun.net.ssl.SSLContext;
^

Bug#902410: closing 902410

[Salvatore Bonaccorso]

close 902410 5:4.0.10-1
# for the BTS graph
found 902410 2:2.8.17-1 
thanks

Processed: closing 902410

[Debian Bug Tracking System]

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

> close 902410 5:4.0.10-1
Bug #902410 [redis] redis: CVE-2018-12326
Marked as fixed in versions redis/5:4.0.10-1.
Bug #902410 [redis] redis: CVE-2018-12326
Marked Bug as done
> # for the BTS graph
> found 902410 2:2.8.17-1
Bug #902410 {Done: Salvatore Bonaccorso } [redis] redis: 
CVE-2018-12326
There is no source info for the package 'redis' at version '2:2.8.17-1' with 
architecture ''
Unable to make a source version for version '2:2.8.17-1'
Marked as found in versions 2:2.8.17-1.
> thanks
Stopping processing here.

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

Processed: retitle 902644 to upower: no longer emits plug/unplug events after upgrade to 0.99.8

[Debian Bug Tracking System]

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

> retitle 902644 upower: no longer emits plug/unplug events after upgrade to 
> 0.99.8
Bug #902644 [upower] upower: Upower breaks power saving settings after upgrade 
to 0.99.8-1
Changed Bug title to 'upower: no longer emits plug/unplug events after upgrade 
to 0.99.8' from 'upower: Upower breaks power saving settings after upgrade to 
0.99.8-1'.
> thanks
Stopping processing here.

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

Processed: severity of 902644 is serious

[Debian Bug Tracking System]

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

> severity 902644 serious
Bug #902644 [upower] upower: Upower breaks power saving settings after upgrade 
to 0.99.8-1
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#901043: marked as done (vkd3d-demos: /usr/bin/triangle is already shipped by the triangle-bin package)

[Debian Bug Tracking System]

Your message dated Mon, 02 Jul 2018 10:00:37 +
with message-id 
and subject line Bug#901043: fixed in vkd3d 1.0-3
has caused the Debian Bug report #901043,
regarding vkd3d-demos: /usr/bin/triangle is already shipped by the triangle-bin 
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.)


-- 
901043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901043
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vkd3d-demos
Version: 1.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package vkd3d-demos.
  Preparing to unpack .../vkd3d-demos_1.0-2_amd64.deb ...
  Unpacking vkd3d-demos (1.0-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/vkd3d-demos_1.0-2_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/triangle', which is also in package 
triangle-bin 1.6-2
  Errors were encountered while processing:
   /var/cache/apt/archives/vkd3d-demos_1.0-2_amd64.deb

I don't think a -demos package should ship binaries with generic
names in /usr/bin - and maybe not in /usr/bin at all.

This is *not* to be solved with Breaks+Replaces!


cheers,

Andreas


triangle-bin=1.6-2_vkd3d-demos=1.0-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: vkd3d
Source-Version: 1.0-3

We believe that the bug you reported is fixed in the latest version of
vkd3d, 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 901...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated vkd3d 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: Sun, 24 Jun 2018 04:08:32 +
Source: vkd3d
Binary: libvkd3d-dev libvkd3d1 libvkd3d1-utils vkd3d-demos
Architecture: source amd64
Version: 1.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Wine Party 
Changed-By: Michael Gilbert 
Description:
 libvkd3d-dev - Direct3D 12 to Vulkan translation - development files
 libvkd3d1  - Direct3D 12 to Vulkan translation - library
 libvkd3d1-utils - Direct3D 12 to Vulkan translation - utilities library
 vkd3d-demos - Direct3D 12 to Vulkan translation - demos
Closes: 901043
Changes:
 vkd3d (1.0-3) unstable; urgency=medium
 .
   * Add manpages for the demos.
   * Append lib to library package names.
   * Append vkd3d to the demo files (closes: #901043).
Checksums-Sha1:
 ff1d485bbb4b52e59902deb38d4751a808dca3a8 2941 vkd3d_1.0-3.dsc
 34334e3473f78540b6b72fd01da3ab4b003c4617 4728 vkd3d_1.0-3.debian.tar.xz
 378c2f3c8ddfa602b777010944846c70d0f0c234 152056 libvkd3d-dev_1.0-3_amd64.deb
 c7577d1ee90b1af419ce6d79bc525f5ae1b096ad 559984 
libvkd3d1-dbgsym_1.0-3_amd64.deb
 41a689d2da49f377f5519e237759c7c726e33b34 16380 
libvkd3d1-utils-dbgsym_1.0-3_amd64.deb
 efc1b4e14f292c85c12a474e7cd491690c5ace93 7008 libvkd3d1-utils_1.0-3_amd64.deb
 0248eb5b564c8fce6640f3581e776f3c4884455a 105828 libvkd3d1_1.0-3_amd64.deb
 cd39a85f79390c1cc90b66d9f775baa0e409a58b 36 
vkd3d-demos-dbgsym_1.0-3_amd64.deb
 99b768aca9961ac3b34546608707a78ab3dbd438 16716 vkd3d-demos_1.0-3_amd64.deb
 1c17bc2f5dc987973ee617b94cb960bfe42d10ec 8702 vkd3d_1.0-3_amd64.buildinfo
Checksums-Sha256:
 1e8d5682126e86a0fd49a7d348530839da8703a491442b325919fe9e836b2baf 2941 
vkd3d_1.0-3.dsc
 175e6400362e8a9fa08cab23e514201e1fdcc43c591bfd31f1b4f80c010a6859 4728 
vkd3d_1.0-3.debian.tar.xz
 0d878c9556c34ae4c59bf114fa7e16d090bb3196b1254db480d16bfa9ef4785a 152056 
libvkd3d-dev_1.0-3_amd64.deb
 9abd2b1d0080e00ec41d35b35a206c1ff936fad42b40a18c60ef5455ac6671c0 559984 
libvkd3d1-dbgsym_1.0-3_amd64.deb
 97cebdaf718b0278e651d5b3fe9ed99852ada20915242f674c07694fa2234e89 16380 
libvkd3d1-utils-dbgsym_1.0-3_amd64.deb
 e6ce24784931d97773e04769d0e773e87075ff03f4cc2d4c21123693048e1e58 7008 
libvkd3d1-utils_1.0-3_amd64.deb
 030b4a5385f007206f949823babb94192ffb22bf583470d5eb8bd4e60020433b 105828 
libvkd3d1_1.0-3_amd64.deb
 

Bug#899684: marked as done (reportbug: Invalid maintainer address reportbug-ma...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Mon, 02 Jul 2018 10:00:30 +
with message-id 
and subject line Bug#899684: fixed in reportbug 7.5.0
has caused the Debian Bug report #899684,
regarding reportbug: Invalid maintainer address 
reportbug-ma...@lists.alioth.debian.org
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.)


-- 
899684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899684
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:reportbug
Version: 7.1.10
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of reportbug,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package reportbug since the list address
reportbug-ma...@lists.alioth.debian.org used in the Maintainer: field
was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
reportbug-ma...@lists.alioth.debian.org is 1.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: reportbug
Source-Version: 7.5.0

We believe that the bug you reported is fixed in the latest version of
reportbug, 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 899...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated reportbug 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: Sun, 01 Jul 2018 14:37:45 -0400
Source: reportbug
Binary: reportbug python3-reportbug reportbug-gtk
Architecture: source all
Version: 7.5.0
Distribution: unstable
Urgency: medium
Maintainer: Reportbug Maintainers 
Changed-By: Sandro Tosi 
Description:
 python3-reportbug - Python modules for interacting with bug tracking systems
 reportbug  - reports bugs in the Debian distribution
 reportbug-gtk - reports bugs in the Debian distribution (GTK+ UI)
Closes: 502860 564112 842018 865812 867337 872300 876373 880857 885959 891144 
894208 894972 899684 900254 902379 902417 902593
Changes:
 reportbug (7.5.0) unstable; urgency=medium
 .
   * debian/control
 - update Vcs-* to point to salsa; drop Homepage pointing to alioth
   * migrate to debian-report...@lists.debian.org; Closes: #899684
   * reportbug/debbugs.py
 - fix a typo in the serious severity description; Closes: #894972
 - add contributors.debian.org to pseudo-packages list
 - since it's now in LTS status, comment out jessie-pu from the list of
   suites presented for release.debian.org; Closes: #902379
   * replace 99@b.d.o with a more generic nn@b.d.o; Closes: #891144
   * reportbug-gtk package created
 - a new package now installs the desktop file only along with 

Bug#896619: marked as done (FTBFS with sphinx 1.7.2: exception: cannot import name 'Directive')

[Debian Bug Tracking System]

Your message dated Mon, 02 Jul 2018 10:00:10 +
with message-id 
and subject line Bug#896619: fixed in bottleneck 1.2.1+ds1-1
has caused the Debian Bug report #896619,
regarding FTBFS with sphinx 1.7.2: exception: cannot import name 'Directive'
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.)


-- 
896619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896619
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sphinx
Version: 1.7.2-1
Severity: serious
Control: affects -1 src:alembic src:bcfg2 src:bottleneck src:dipy src:heat 
src:julia src:mako src:prospector src:pyevolve src:pymvpa2 
src:python-cryptography src:python-expyriment src:python-numpy src:python-scipy

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/alembic.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/bcfg2.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/bottleneck.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dipy.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/heat.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/julia.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mako.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/prospector.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pyevolve.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pymvpa2.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/python-cryptography.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-expyriment.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-numpy.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-scipy.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/sqlalchemy.html

Example (from alembic):

...
   debian/rules override_dh_sphinxdoc
make[1]: Entering directory '/build/1st/alembic-0.9.7'
sphinx-build -b html docs/build 
/build/1st/alembic-0.9.7/debian/alembic/usr/share/doc/alembic/html
Running Sphinx v1.7.2

Extension error:
Could not import extension changelog (exception: cannot import name 'Directive')
make[1]: *** [debian/rules:13: override_dh_sphinxdoc] Error 2
--- End Message ---
--- Begin Message ---
Source: bottleneck
Source-Version: 1.2.1+ds1-1

We believe that the bug you reported is fixed in the latest version of
bottleneck, 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 896...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dmitry Shachnev  (supplier of updated bottleneck 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: Sun, 01 Jul 2018 19:03:32 +0300
Source: bottleneck
Binary: python-bottleneck python-bottleneck-dbg python3-bottleneck 
python3-bottleneck-dbg python-bottleneck-doc
Architecture: source amd64 all
Version: 1.2.1+ds1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Dmitry Shachnev 
Description:
 python-bottleneck - Fast NumPy array functions written in C (Python 2)
 python-bottleneck-dbg - debug extensions for bottleneck (Python 2)
 python-bottleneck-doc - documentation for bottleneck
 python3-bottleneck - Fast NumPy array functions written in C (Python 3)
 python3-bottleneck-dbg - debug extensions for bottleneck (Python 3)
Closes: 880678 880679 896619
Changes:
 bottleneck (1.2.1+ds1-1) unstable; urgency=medium
 .
   * Team upload
 .
   [ Ghislain Antony Vaillant ]
   * Update the gbp configuration
   * Filter the vendored copy of numpydoc (Closes: 896619)
   * Repack the upstream tarball
   * New upstream version 1.2.1+ds1
   * Drop the patch queue, applied upstream
   * Update copyright information
   * Run cme fix on control file
 - Overall reordering of fields
 - Drop superfluous versioning:
   - python-all-dev
   - python-setuptools
 - Wrap and sort dependencies
 - Use a secure Vcs-Git URI
   * Run cme fix on copyright file
 - Use a secure Format URI
   * Fix build of documentation
 

Bug#893953: marked as done (imagemagick: FTBFS on i386: testsuite failure in Magick++/tests/tests.tap 2)

[Debian Bug Tracking System]

Your message dated Mon, 02 Jul 2018 10:00:21 +
with message-id 
and subject line Bug#893953: fixed in imagemagick 8:6.9.10.2+dfsg-1
has caused the Debian Bug report #893953,
regarding imagemagick: FTBFS on i386: testsuite failure in 
Magick++/tests/tests.tap 2
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.)


-- 
893953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893953
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: imagemagick
Version: 8:6.9.9.39+dfsg-1
Severity: serious

Your package FTBFS on i386 due to a testsuite failure, here is a
hopefully relevant excerpt from the build log[1]:

,
| Line: 160, backgroundColor default (#) is incorrect
| Testing throwing and catching exceptions. A program crash or a message
| that the exception was not caught indicates a test failure.  A properly
| formatted exception message indicates success:
| Caught exception, good!:
|   "attributes: unable to open image `foo': No such file or directory @ 
error/blob.c/OpenBlob/2761"
| Line: 1074, pixelColor default (#) is not canvas color 
(#) as expected
| 2 failures
| not ok
| FAIL: Magick++/tests/tests.tap 2
`


1. 
https://buildd.debian.org/status/fetch.php?pkg=imagemagick=i386=8%3A6.9.9.39%2Bdfsg-1=1521546513=0
--- End Message ---
--- Begin Message ---
Source: imagemagick
Source-Version: 8:6.9.10.2+dfsg-1

We believe that the bug you reported is fixed in the latest version of
imagemagick, 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 893...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastien Roucariès  (supplier of updated imagemagick 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: Mon, 25 Jun 2018 14:29:02 +0200
Source: imagemagick
Binary: imagemagick-6-common imagemagick-6-doc libmagickcore-6-headers 
libmagickwand-6-headers libmagick++-6-headers libimage-magick-perl 
libmagickcore-6-arch-config imagemagick-6.q16 libmagickcore-6.q16-6 
libmagickcore-6.q16-6-extra libmagickcore-6.q16-dev libmagickwand-6.q16-6 
libmagickwand-6.q16-dev libmagick++-6.q16-8 libmagick++-6.q16-dev 
libimage-magick-q16-perl imagemagick-6.q16hdri libmagickcore-6.q16hdri-6 
libmagickcore-6.q16hdri-6-extra libmagickcore-6.q16hdri-dev 
libmagickwand-6.q16hdri-6 libmagickwand-6.q16hdri-dev libmagick++-6.q16hdri-8 
libmagick++-6.q16hdri-dev libimage-magick-q16hdri-perl imagemagick-common 
imagemagick-doc perlmagick libmagickcore-dev libmagickwand-dev libmagick++-dev 
imagemagick
Architecture: source all i386
Version: 8:6.9.10.2+dfsg-1
Distribution: experimental
Urgency: medium
Maintainer: ImageMagick Packaging Team 

Changed-By: Bastien Roucariès 
Description:
 imagemagick - image manipulation programs -- binaries
 imagemagick-6-common - image manipulation programs -- infrastructure
 imagemagick-6-doc - document files of ImageMagick
 imagemagick-6.q16 - image manipulation programs -- quantum depth Q16
 imagemagick-6.q16hdri - image manipulation programs -- quantum depth Q16HDRI
 imagemagick-common - image manipulation programs -- infrastructure dummy 
package
 imagemagick-doc - document files of ImageMagick -- dummy package
 libimage-magick-perl - Perl interface to the ImageMagick graphics routines
 libimage-magick-q16-perl - Perl interface to the ImageMagick graphics routines 
-- Q16 versio
 libimage-magick-q16hdri-perl - Perl interface to the ImageMagick graphics 
routines -- Q16HDRI ve
 libmagick++-6-headers - object-oriented C++ interface to ImageMagick - header 
files
 libmagick++-6.q16-8 - C++ interface to ImageMagick -- quantum depth Q16
 libmagick++-6.q16-dev - C++ interface to ImageMagick - development files (Q16)
 libmagick++-6.q16hdri-8 - C++ interface to ImageMagick -- quantum depth Q16HDRI
 libmagick++-6.q16hdri-dev - C++ interface to ImageMagick - development files 
(Q16HDRI)
 libmagick++-dev - object-oriented C++ interface to ImageMagick -- dummy package
 libmagickcore-6-arch-config - low-level image manipulation library - 
architecture header files
 libmagickcore-6-headers - low-level image manipulation library - header files
 libmagickcore-6.q16-6 - 

Bug#898914: marked as done (imagemagick: FTBFS on any-i386)

[Debian Bug Tracking System]

Your message dated Mon, 02 Jul 2018 10:00:21 +
with message-id 
and subject line Bug#893953: fixed in imagemagick 8:6.9.10.2+dfsg-1
has caused the Debian Bug report #893953,
regarding imagemagick: FTBFS on any-i386
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.)


-- 
893953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893953
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: imagemagick
Version: 6.9.9.39+dfsg-1
Severity: important
Tags: patch, i386
User: debian-h...@lists.debian.org, debian-...@lists.debian.org
Usertags: hurd

Hi,

imagemagick currently FTBFS on any-i386 architectures:
i386, hurd-i386 and kfrebsd-i386. 

The attached patch: 0019-Fix-FTBFS-on-any-i386.patch
makes the tests succeed so that the build completes.

The attached patch has been used to successfully build packages for linux-i386,
linux-amd64 and hurd-i386. The reason to build on linux-amd64 is to check that
the patch does not affect 64-bit architectures.

Thanks!--- a/Magick++/tests/attributes.cpp.orig	2018-03-18 15:15:56.0 +0100
+++ b/Magick++/tests/attributes.cpp	2018-05-08 16:06:41.820001000 +0200
@@ -154,7 +154,7 @@
 //
 
 // Test default value.
-if ( image.backgroundColor() != ColorRGB("white") )
+if ( image.backgroundColor() != string(ColorRGB("white")) )
   {
 	++failures;
 	cout << "Line: " << __LINE__ << ", backgroundColor default ("
@@ -1068,7 +1068,7 @@
 // pixelColor
 //
 // Test default
-if ( image.pixelColor(40,60) != canvasColor )
+if ( image.pixelColor(40,60) != string(canvasColor) )
   {
 	++failures;
 	cout << "Line: " << __LINE__ << ", pixelColor default ("
--- End Message ---
--- Begin Message ---
Source: imagemagick
Source-Version: 8:6.9.10.2+dfsg-1

We believe that the bug you reported is fixed in the latest version of
imagemagick, 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 893...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastien Roucariès  (supplier of updated imagemagick 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: Mon, 25 Jun 2018 14:29:02 +0200
Source: imagemagick
Binary: imagemagick-6-common imagemagick-6-doc libmagickcore-6-headers 
libmagickwand-6-headers libmagick++-6-headers libimage-magick-perl 
libmagickcore-6-arch-config imagemagick-6.q16 libmagickcore-6.q16-6 
libmagickcore-6.q16-6-extra libmagickcore-6.q16-dev libmagickwand-6.q16-6 
libmagickwand-6.q16-dev libmagick++-6.q16-8 libmagick++-6.q16-dev 
libimage-magick-q16-perl imagemagick-6.q16hdri libmagickcore-6.q16hdri-6 
libmagickcore-6.q16hdri-6-extra libmagickcore-6.q16hdri-dev 
libmagickwand-6.q16hdri-6 libmagickwand-6.q16hdri-dev libmagick++-6.q16hdri-8 
libmagick++-6.q16hdri-dev libimage-magick-q16hdri-perl imagemagick-common 
imagemagick-doc perlmagick libmagickcore-dev libmagickwand-dev libmagick++-dev 
imagemagick
Architecture: source all i386
Version: 8:6.9.10.2+dfsg-1
Distribution: experimental
Urgency: medium
Maintainer: ImageMagick Packaging Team 

Changed-By: Bastien Roucariès 
Description:
 imagemagick - image manipulation programs -- binaries
 imagemagick-6-common - image manipulation programs -- infrastructure
 imagemagick-6-doc - document files of ImageMagick
 imagemagick-6.q16 - image manipulation programs -- quantum depth Q16
 imagemagick-6.q16hdri - image manipulation programs -- quantum depth Q16HDRI
 imagemagick-common - image manipulation programs -- infrastructure dummy 
package
 imagemagick-doc - document files of ImageMagick -- dummy package
 libimage-magick-perl - Perl interface to the ImageMagick graphics routines
 libimage-magick-q16-perl - Perl interface to the ImageMagick graphics routines 
-- Q16 versio
 libimage-magick-q16hdri-perl - Perl interface to the ImageMagick graphics 
routines -- Q16HDRI ve
 libmagick++-6-headers - object-oriented C++ interface to ImageMagick - header 
files
 libmagick++-6.q16-8 - C++ interface to ImageMagick -- quantum depth Q16
 libmagick++-6.q16-dev - C++ interface to ImageMagick - development files (Q16)
 libmagick++-6.q16hdri-8 - C++ interface to ImageMagick -- quantum depth Q16HDRI
 

Bug#892574: marked as done (pike8.0 FTBFS with glibc 2.27)

[Debian Bug Tracking System]

Your message dated Mon, 02 Jul 2018 10:00:29 +
with message-id 
and subject line Bug#892574: fixed in pike8.0 8.0.610-1
has caused the Debian Bug report #892574,
regarding pike8.0 FTBFS with glibc 2.27
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.)


-- 
892574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pike8.0
Version: 8.0.498-1
Severity: serious

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

...
 Making dynamic: modules/Fuse
Compiling modules/Fuse/fuse.c
gcc -I. -I/build/1st/pike8.0-8.0.498/src/modules/Fuse 
-I/build/1st/pike8.0-8.0.498/build/linux-4.9.0-6-amd64-x86_64 
-I/build/1st/pike8.0-8.0.498/src -Wdate-time -D_FORTIFY_SOURCE=2 -DDEBIAN 
-I/usr/local/include -DHAVE_CONFIG_H -Wformat -Werror=format-security -ggdb 
-m64 -mrdrnd -O2 -fstack-protector-strong -fvisibility=hidden -pipe 
-fvar-tracking-assignments -funswitch-loops -W -Wall -Wno-unused -Wcomment 
-Wformat -Wformat-security -Wimplicit-function-declaration -Wmultichar 
-Wunused-function -Wswitch -Wuninitialized -Wpointer-arith -Wchar-subscripts 
-Wno-long-long -Wdeclaration-after-statement -fPIC -DDYNAMIC_MODULE -c 
/build/1st/pike8.0-8.0.498/src/modules/Fuse/fuse.c -o fuse.o -g -g
Linking Fuse
gcc -shared -nostartfiles -o module.so fuse.o -Wl,-z,relro -Wl,--as-needed 
-L/usr/local/lib -L/usr/lib/gcc/x86_64-linux-gnu/7 -L/usr/lib/x86_64-linux-gnu 
-L/lib/x86_64-linux-gnu -ldl -lrt -lnsl -lm -lpthread -lcrypt -lfuse 
/usr/lib/gcc/x86_64-linux-gnu/7/libgcc.a -lc 
/usr/lib/gcc/x86_64-linux-gnu/7/libgcc.a
/usr/lib/x86_64-linux-gnu/libc_nonshared.a(atexit.oS): In function `atexit':
(.text+0x3): undefined reference to `__dso_handle'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libc_nonshared.a(atexit.oS): relocation 
R_X86_64_PC32 against undefined hidden symbol `__dso_handle' can not be used 
when making a shared object
/usr/bin/ld: final link failed: Bad value
collect2: error: ld returned 1 exit status
Linking failed:
/build/1st/pike8.0-8.0.498/bin/smartlink gcc -shared -nostartfiles -o module.so 
fuse.o -Wl,-z,relro -Wl,--as-needed -L/usr/local/lib 
-L/usr/lib/gcc/x86_64-linux-gnu/7 -R/usr/lib/gcc/x86_64-linux-gnu/7 
-L/usr/lib/x86_64-linux-gnu -R/usr/lib/x86_64-linux-gnu -L/lib/x86_64-linux-gnu 
-R/lib/x86_64-linux-gnu -ldl -lrt -lnsl -lm -lpthread -lcrypt -lfuse 
/usr/lib/gcc/x86_64-linux-gnu/7/libgcc.a -lc 
/usr/lib/gcc/x86_64-linux-gnu/7/libgcc.a
make[7]: *** [Makefile:422: module.so] Error 1


This can be fixed by removing the -nostartfiles from src/configure.in.
--- End Message ---
--- Begin Message ---
Source: pike8.0
Source-Version: 8.0.610-1

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

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

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

Debian distribution maintenance software
pp.
Magnus Holmgren  (supplier of updated pike8.0 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: Sun, 24 Jun 2018 01:07:57 +0200
Source: pike8.0
Binary: pike8.0-core pike8.0 pike8.0-dev pike8.0-manual pike8.0-reference 
pike8.0-doc pike8.0-full pike8.0-mysql pike8.0-pg pike8.0-odbc pike8.0-svg 
pike8.0-image pike8.0-sdl pike8.0-gdbm pike8.0-gl pike8.0-sane pike8.0-pcre 
pike8.0-bzip2 pike8.0-fuse pike8.0-sqlite pike8.0-dnssd pike8.0-kerberos 
pike8.0-web-sass
Architecture: source amd64 all
Version: 8.0.610-1
Distribution: unstable
Urgency: low
Maintainer: Magnus Holmgren 
Changed-By: Magnus Holmgren 
Description:
 pike8.0- Recommended metapackage for Pike 8.0
 pike8.0-bzip2 - Bzip2 module for Pike
 pike8.0-core - Powerful interpreted programming language
 pike8.0-dev - Development files for Pike 8.0
 pike8.0-dnssd - DNS Service Discovery (DNS-SD) for Pike
 pike8.0-doc - Pike 8.0 documentation
 pike8.0-full - Metapackage for Pike 8.0
 pike8.0-fuse - Filesystem in USErspace support for Pike
 pike8.0-gdbm - Gdbm module for Pike
 pike8.0-gl - Mesa modules for Pike
 pike8.0-image - Image modules for Pike
 pike8.0-kerberos - Kerberos and GSSAPI modules for Pike
 pike8.0-manual - transitional package for 

Bug#885673: marked as done (pike8.0-gtk: Depends on old GNOME libraries)

[Debian Bug Tracking System]

Your message dated Mon, 02 Jul 2018 10:00:29 +
with message-id 
and subject line Bug#885673: fixed in pike8.0 8.0.610-1
has caused the Debian Bug report #885673,
regarding pike8.0-gtk: Depends on old GNOME libraries
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.)


-- 
885673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885673
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pike8.0-gtk
Version: 8.0.498-1
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnomecanvas libgnomeui libgnome gtksourceview2
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

pike8.0-gtk depends on these:

- libgnome-2-0
- libgnomecanvas2-0
- libgnomeui-0
- libgtksourceview2.0-0

As far as I can tell, Pike doesn't offer GTK3 support yet. I think
you're going to need to eventually drop this package.

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: pike8.0
Source-Version: 8.0.610-1

We believe that the bug you reported is fixed in the latest version of
pike8.0, 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 885...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Magnus Holmgren  (supplier of updated pike8.0 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: Sun, 24 Jun 2018 01:07:57 +0200
Source: pike8.0
Binary: pike8.0-core pike8.0 pike8.0-dev pike8.0-manual pike8.0-reference 
pike8.0-doc pike8.0-full pike8.0-mysql pike8.0-pg pike8.0-odbc pike8.0-svg 
pike8.0-image pike8.0-sdl pike8.0-gdbm pike8.0-gl pike8.0-sane pike8.0-pcre 
pike8.0-bzip2 pike8.0-fuse pike8.0-sqlite pike8.0-dnssd pike8.0-kerberos 
pike8.0-web-sass
Architecture: source amd64 all
Version: 8.0.610-1
Distribution: unstable
Urgency: low
Maintainer: Magnus Holmgren 
Changed-By: Magnus Holmgren 
Description:
 pike8.0- Recommended metapackage for Pike 8.0
 pike8.0-bzip2 - Bzip2 module for Pike
 pike8.0-core - Powerful interpreted programming language
 pike8.0-dev - Development files for Pike 8.0
 pike8.0-dnssd - DNS Service Discovery (DNS-SD) for Pike
 pike8.0-doc - Pike 8.0 documentation
 pike8.0-full - Metapackage for Pike 8.0
 pike8.0-fuse - Filesystem in USErspace support for Pike
 pike8.0-gdbm - Gdbm module for Pike
 pike8.0-gl - Mesa modules for Pike
 pike8.0-image - Image modules for Pike
 pike8.0-kerberos - Kerberos and GSSAPI modules for Pike
 pike8.0-manual - transitional package for merging into pike8.0-doc
 pike8.0-mysql - MySQL modules for Pike
 pike8.0-odbc - ODBC modules for Pike
 pike8.0-pcre - PCRE module for Pike
 pike8.0-pg - PostgreSQL modules for Pike
 pike8.0-reference - transitional package for merging into pike8.0-doc
 pike8.0-sane - SANE module for Pike
 pike8.0-sdl - SDL module for Pike
 pike8.0-sqlite - SQLite module for Pike
 pike8.0-svg - SVG format support for Pike
 pike8.0-web-sass - Sass CSS precompiler modules for Pike
Closes: 885673 892574
Changes:
 pike8.0 (8.0.610-1) unstable; urgency=low
 .
   * New upstream release.
   * New package pike8.0-web-sass for the new Web.Sass module, which links
 with libsass.
   * Drop misplaced_MAXPATHLEN.patch; obsolete.
   * Drop support for GTK+ 2 (Closes: #885673).
   * no_nostartfiles.patch: Don't use -nostartfiles when linking shared
 modules (Closes: #892574). Thanks to Adrian Bunk.
   * postgres_10_detect.patch (from upstream): Detect Postgres 10.x and
 later.
   * Switch VCS URLs after Alioth decommissioned.
   * Add lib-dev as build dependency so that Image.WebP can actually work.
   * Exclude modules FSEvents (only works on MacOS X), COM (only works on
 Windows), and VCDiff (requires the open-vcdiff library).
   * Bump Standards-Version to 4.1.4.
   * Remove inactive uploader from debian/control.
Checksums-Sha1:
 fe3f67363fcb17ce89e3f16fb86300f64982909c 3732 pike8.0_8.0.610-1.dsc
 8f7f736d52cc2dd60694b72d818df4ff827e9660 18834215 

Processed: Re: Bug#895025: deprecate/remove libindicate in Debian

[Debian Bug Tracking System]

Processing control commands:

> block 895025 by 857260
Bug #895025 [src:libindicate] deprecate/remove libindicate in Debian
895025 was blocked by: 895027 895031 895026
895025 was not blocking any bugs.
Added blocking bug(s) of 895025: 857260
> severity 857260 serious
Bug #857260 [src:libappindicator] libappindicator: please do not build-depend 
on libindicate
Severity set to 'serious' from 'normal'

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

Bug#895025: deprecate/remove libindicate in Debian

[Simon McVittie]

Control: block 895025 by 857260
Control: severity 857260 serious

On Mon, 02 Jul 2018 at 10:38:53 +0100, Simon McVittie wrote:
> On Fri, 06 Apr 2018 at 10:58:00 +, Mike Gabriel wrote:
> > So, in a nutshell, these packages need to be addressed: smuxi,
> > pidgin-libnotify and mopidy-mpris require changes to have libindicate
> > removed from Debian.
> 
> If you do not intend to ship libindicate in buster, should the remaining
> bugs blocking #895025 (#895027 in smuxi and #895026 in pidgin-libnotify)
> inherit RC severity from this one?

dak says libappindicator also needs changes if you want to
remove libindicate from buster (I already opened #857260 some time
ago). libappindicator is RC-buggy already, so escalating #857260 to RC
severity doesn't seem harmful; but there are rather more packages that
depend on libappindicator, so it will probably take longer to remove than
libindicate, and it might be worthwhile for people with an interest in
indicators to do a QA upload to fix #857260.

smcv@coccia ~ % dak rm -R -n -s testing libindicate
...
# Broken Depends:
pidgin-libnotify: pidgin-libnotify
smuxi: smuxi-frontend-gnome

# Broken Build-Depends:
libappindicator: libindicate-dev (>= 0.2.0)
 libindicate-gtk-dev (>= 0.2.0)
pidgin-libnotify: libindicate-dev (>= 0.6.90)
  libindicate-gtk-dev (>= 0.6.90)

(I get the same report for removal from unstable.)

Regards,
smcv

Bug#895025: deprecate/remove libindicate in Debian

[Simon McVittie]

On Fri, 06 Apr 2018 at 10:58:00 +, Mike Gabriel wrote:
> So, in a nutshell, these packages need to be addressed: smuxi,
> pidgin-libnotify and mopidy-mpris require changes to have libindicate
> removed from Debian.

If you do not intend to ship libindicate in buster, should the remaining
bugs blocking #895025 (#895027 in smuxi and #895026 in pidgin-libnotify)
inherit RC severity from this one?

smcv

Processed: tagging 895599

[Debian Bug Tracking System]

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

> tags 895599 + pending
Bug #895599 [ganeti] ganeti-2.15 - Fails to export vm: certificate is valid but 
its commonName does not match hostname
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#902810: user-mode-linux: FTBFS in stretch (Hunk #1 FAILED in 07-remove-rpath.patch)

[Ritesh Raj Sarraf]

On Sun, 2018-07-01 at 13:05 +, Santiago Vila wrote:
> Dear maintainer:
> 
> I tried to build this package in stretch + security + stretch-
> proposed-updates but it failed:

Must be some very minor delta in the path. We don't really have any big
patches. I'll look into it over the weekend.

Ritesh

-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System

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

Processed: Re: Bug#901462: seabios: SeaBIOS fails to build from source on sid and testing

[Debian Bug Tracking System]

Processing control commands:

> tag -1 - patch
Bug #901462 [seabios] seabios: SeaBIOS fails to build from source on sid and 
testing
Removed tag(s) patch.

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

Bug#901462: seabios: SeaBIOS fails to build from source on sid and testing

[Michael Tokarev]

Control: tag -1 - patch

Apparently this is not so simple. As per upstream,
https://mail.coreboot.org/pipermail/seabios/2018-July/012353.html
- they say only particular versions of IASL produce correct code,
more recent IASL produces instructions not understood by older
OSes (which is what qemu about, too) - so instead of fixing seabios
code to comply with modern IASL requirimens, we either have to
use older IASL or to turn off this ACPI tables stuff completely
and remove iasl build-dependency (which is actually not that
bad idea).

So un-tagging as "patch" for now.

Thanks,

/mjt

Bug#881835: mbr FTBFS on !amd64 !i386: debhelper got stricter

[Simon McVittie]

Control: tags -1 + patch

On Wed, 15 Nov 2017 at 18:16:17 +0100, Helmut Grohne wrote:
> | cp `pwd`/debian/mbr/sbin/install-mbr `pwd`/debian/mbr-udeb/sbin/
> | cp: cannot create regular file '/<>/debian/mbr-udeb/sbin/': No 
> such file or directory
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/mbr.html
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/armhf/mbr.html
> 
> This is likely because debhelper became more strict recently. You cannot
> reproduce this on amd64 or i386 (except by cross building).

The attached patch seems to fix this in a cross-build with -aarm64.

Regards,
smcv
>From 172c4f28fb3f1bf4ab38e7b69378415bca951705 Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Mon, 2 Jul 2018 08:27:13 +0100
Subject: [PATCH] Only copy install-mbr into mbr-udeb if we will build that
 package

This fixes FTBFS on non-x86 architectures. In recent debhelper versions,
dh_installdirs does not create directories for binary packages that are
not applicable to the current architecture.
---
 debian/changelog | 11 +++
 debian/rules |  4 
 2 files changed, 15 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index 90fe3c1..e83dd11 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,14 @@
+mbr (1.1.11-5.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Only copy install-mbr to debian/mbr-udeb/sbin if we are going to
+build the mbr-udeb package, fixing FTBFS on non-x86 architectures.
+In recent debhelper versions, dh_installdirs does not create
+directories for binary packages that are not applicable to the
+current architecture.
+
+ -- Simon McVittie   Mon, 02 Jul 2018 08:24:52 +0100
+
 mbr (1.1.11-5.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff --git a/debian/rules b/debian/rules
index cebafe2..6761009 100755
--- a/debian/rules
+++ b/debian/rules
@@ -1,5 +1,7 @@
 #!/usr/bin/make -f
 
+binaries := $(shell dh_listpackages)
+
 CC := gcc -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64
 
 CFLAGS := -g -Wall -W
@@ -38,7 +40,9 @@ install: build
 	dh_installdocs -p mbr debian/README-1st.Debian NEWS README AUTHORS
 	dh_installchangelogs
 	$(MAKE) install INSTALL_PROGRAM="$(INSTALL_PROGRAM)"
+ifneq ($(filter mbr-udeb,$(binaries)),)
 	cp `pwd`/debian/mbr/sbin/install-mbr `pwd`/debian/mbr-udeb/sbin/
+endif
 
 binary-indep: build
 	dh_testdir
-- 
2.18.0

Processed: Re: Bug#881835: mbr FTBFS on !amd64 !i386: debhelper got stricter

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #881835 [src:mbr] mbr FTBFS on !amd64 !i386: debhelper got stricter
Added tag(s) patch.

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

Bug#792205: closed by Guillaume Bougard (Re: fusioninventory-agent: modifies conffiles (policy 10.7.3): /etc/fusioninventory/agent.cfg)

[Guillaume Bougard]

Hi,

in fact, and regarding the package history, the bug should have been opened 
with 2.3.10 and closed with not releases 2.3.15...

How to avoid this case becomes blocking for the migration to testing planned in 
8 days now ?

Kind regards,

Guillaume Bougard 
Ingénieur R 
gboug...@teclib.com 

TECLIB' Montpellier 
3 rue Doria, 
34000 Montpellier, France 

- Mail original -
De: "gregor herrmann" 
À: 792...@bugs.debian.org, "Andreas Beckmann" 
Cc: "Guillaume Bougard" 
Envoyé: Samedi 30 Juin 2018 19:26:29
Objet: Re: Bug#792205 closed by Guillaume Bougard  (Re: 
fusioninventory-agent: modifies conffiles (policy 10.7.3): 
/etc/fusioninventory/agent.cfg)

On Tue, 26 Jun 2018 08:45:05 +, Debian Bug Tracking System wrote:

> Version: 1:2.3.16-1
> 
> Hi,
> 
> I'm the upstream maintainer.
> 
> As I said before, ucf is used since 2.3.10. So the problem shouldn't occur in 
> later releases.
> 
> So this bug should be closed.

> From: Andreas Beckmann 
> To: Debian Bug Tracking System 
> Subject: fusioninventory-agent: modifies conffiles (policy 10.7.3):
>  /etc/fusioninventory/agent.cfg
> Date: Sun, 12 Jul 2015 18:23:06 +0200
> X-Spam-Level: 
> X-Spam-Status: No, score=-11.9 required=4.0 tests=BAYES_00,FOURLA,
>  FROMDEVELOPER,HAS_PACKAGE autolearn=ham autolearn_force=no
>  version=3.4.0-bugs.debian.org_2005_01_02
> 
> Package: fusioninventory-agent
> Version: 1:2.3.16-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts


Looks like we have a BTS issue here. The bug was reported against 1:2.3.16-1
and closed in the same 1:2.3.16-1 version which confused the BTS (cf.
the version graph in the web interface). As I don't know enough about
the bug itself, I'm not changing anything; but something needs to be
done as this will block the migration of the new upload to testing.

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Neil Young: Oh, Lonesome Me

Bug#874526: marked as done (Keyboard grab doesn't work under Wayland)

[Debian Bug Tracking System]

Your message dated Mon, 2 Jul 2018 08:14:48 +0100
with message-id <20180702071448.ga7...@espresso.pseudorandom.co.uk>
and subject line Re: Bug#874526: Keyboard grab doesn't work under Wayland
has caused the Debian Bug report #874526,
regarding Keyboard grab doesn't work under Wayland
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.)


-- 
874526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-boxes
Version: 3.25.91-1
Severity: serious

[I don't know whether this bug lies in gnome-boxes or gnome-shell or
some combination of both. Release-critical because this completely
breaks the ability to log into many Windows VMs with gnome-boxes under
the default GNOME Wayland session.]

The mechanism gnome-boxes uses to grab the keyboard doesn't work under
the default GNOME Wayland session. This makes it impossible to send
Ctrl-Alt-Delete; it always goes to gnome-shell instead.

(It might also help to add Ctrl-Alt-Delete to the list of shortcuts
provided in the gnome-boxes keyboard menu, alongside Ctrl-Alt-Backspace
and similar.)

-- 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.12.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-boxes depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2+b1
ii  libarchive13 3.2.2-2
ii  libc62.24-17
ii  libcairo-gobject21.14.10-1
ii  libcairo21.14.10-1
ii  libgdk-pixbuf2.0-0   2.36.5-4
ii  libglib2.0-0 2.53.6-1
ii  libgovirt2   0.3.4-2
ii  libgtk-3-0   3.22.19-1
ii  libgtk-vnc-2.0-0 0.7.1-1
ii  libgudev-1.0-0   232-1
ii  libosinfo-1.0-0  1.1.0-1
ii  libosinfo-bin1.1.0-1
ii  libpango-1.0-0   1.40.11-1
ii  libpangocairo-1.0-0  1.40.11-1
ii  librest-0.7-00.8.0-2
ii  libsecret-1-00.18.5-3.1
ii  libsoup2.4-1 2.59.90.1-1
ii  libspice-client-glib-2.0-8   0.34-1.1
ii  libspice-client-gtk-3.0-50.34-1.1
ii  libtracker-sparql-1.0-0  1.12.1-1
ii  libusb-1.0-0 2:1.0.21-2
ii  libvirt-daemon   3.6.0-1
ii  libvirt-glib-1.0-0   1.0.0-1
ii  libxml2  2.9.4+dfsg1-4
ii  mtools   4.0.18-2+b1
ii  tracker  1.12.1-1

Versions of packages gnome-boxes recommends:
ii  qemu-system-x86  1:2.8+dfsg-7

gnome-boxes suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 3.28.5-1

On Sat, 21 Oct 2017 at 04:55:29 +0200, Michael Biebl wrote:
> On Sat, 14 Oct 2017 15:12:34 -0400 Jeremy Bicha  wrote:
> > Please verify whether you can still reproduce this bug after updating
> > to gnome-shell and gnome-control-center 3.26 which are now in Debian
> > unstable.
> 
> Josh, can you please re-test with an up-to-date sid system.
> According to a comment in the upstream bug tracker, this should be fixed.

This seems to work under GNOME 3.28 (probably also 3.26). I'm prompted
while starting up the VM for whether to allow gnome-boxes to grab the
keyboard. I haven't tried a Windows VM, but if I use the keyboard menu to
switch to a text-mode VT for a Linux VM with Ctrl+Alt+F$n, then either
press Ctrl+Alt+Del or send it via the keyboard menu, the VM reboots
as expected.

smcv--- End Message ---

Bug#902646: marked as done (python3-pexpect: Failure to install with Python 3.7)

[Debian Bug Tracking System]

Your message dated Mon, 02 Jul 2018 06:19:04 +
with message-id 
and subject line Bug#902646: fixed in pexpect 4.6.0-1
has caused the Debian Bug report #902646,
regarding python3-pexpect: Failure to install with Python 3.7
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.)


-- 
902646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902646
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pexpect
Version: 4.2.1-1
Severity: serious

Installation fails with python3.7 installed:

Setting up python3-pexpect (4.2.1-1) ...
  File "/usr/lib/python3/dist-packages/pexpect/spawnbase.py"
def expect(self, pattern, timeout=-1, searchwindowsize=-1, async=False):
SyntaxError: invalid syntax

'async' is a reserved keyword in Python 3.7. This issue has been
previously reported upstream, and was fixed in version 4.3 of
pexpect.[1] The current upstream version is 4.6.

[1] https://github.com/pexpect/pexpect/issues/453
--- End Message ---
--- Begin Message ---
Source: pexpect
Source-Version: 4.6.0-1

We believe that the bug you reported is fixed in the latest version of
pexpect, 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 902...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Diane Trout  (supplier of updated pexpect 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: Sun, 01 Jul 2018 19:56:20 -0700
Source: pexpect
Binary: python-pexpect python3-pexpect python-pexpect-doc
Architecture: source
Version: 4.6.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Diane Trout 
Description:
 python-pexpect - Python module for automating interactive applications
 python-pexpect-doc - Python module for automating interactive applications 
(documentat
 python3-pexpect - Python 3 module for automating interactive applications
Closes: 890967 902646
Changes:
 pexpect (4.6.0-1) unstable; urgency=medium
 .
   * Team upload.
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/watch: Use https protocol
   * d/changelog: Remove trailing whitespaces
   * d/control: Remove ancient X-Python-Version field
   * d/control: Remove ancient X-Python3-Version field
 .
   [ Diane Trout ]
   * New upstream release. (Closes: #890967)
 - Upstream renamed async to _async (Closes: #902646)
   * d/control: Update Standards-Version, no changes needed.
   * d/rules: remove _async.py for python2.7 (Thanks: Neil Williams)
   * d/control: Switch to python3-sphinx for documentation build
   * Update debhelper version to 11
Checksums-Sha1:
 eca509acf259b0fdff8e0738ee36a536f6b855ed 2215 pexpect_4.6.0-1.dsc
 3d79bb7de5436cd0a8417a6249c765595a33abcf 148966 pexpect_4.6.0.orig.tar.gz
 9188816b345fe8b29540b896d96c1fd3c7de6888 5164 pexpect_4.6.0-1.debian.tar.xz
 2c689cee10dd551ae01482a3bb26fd11ec38e3e9 7982 pexpect_4.6.0-1_source.buildinfo
Checksums-Sha256:
 d02dfb29591f2190c0e8258b6fa3091bf2439f38e2539c40968bf65ad35f2a85 2215 
pexpect_4.6.0-1.dsc
 2a8e88259839571d1251d278476f3eec5db26deb73a70be5ed5dc5435e418aba 148966 
pexpect_4.6.0.orig.tar.gz
 5ee6cf48a24f1b090e9eb0bb1a9ccd19c678c460dea66dea23a04f13ce3ef70c 5164 
pexpect_4.6.0-1.debian.tar.xz
 80fab40ecd8110986d552a89dd889bb838673336767f762ed79ede27b0d62ec9 7982 
pexpect_4.6.0-1_source.buildinfo
Files:
 f78635b7238924fc69e519c93f843e07 2215 python optional pexpect_4.6.0-1.dsc
 d4f3372965a996238d57d19b95d2e03a 148966 python optional 
pexpect_4.6.0.orig.tar.gz
 ba62e0c41057fd4ba95978967e3f1ecb 5164 python optional 
pexpect_4.6.0-1.debian.tar.xz
 335025f11edcd8142dc0d2817381b70c 7982 python optional 
pexpect_4.6.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQVcMeSBIEX5AQ11mQ04NnM013AFAls5v9IACgkQmQ04NnM0
13BwgQ//THByYgSTKw8I6v36tKBTUzX4/zH1KcfNoxJWXI2RyVhXMxRa3tSGxjdd
e1cIFxEqDvIlf5kT4G1ugi1XTmXQYyQZfZnIHfnKoOws0l/IVILDnXRNLRde/zT4
H/u+7AlHwUQl3KepcADGy+CyLJvJ9gARGvFcSGLtaPqAMARNpkc64dYgQBjTfw9J
pUN52gbMu/mlSBbMXQ/1QiUdZOg2ras7kgxpsHyz6H/xlc2h4A1lCx3OLQZl7sGe
DavmQA25lww7XdOmQmE6OdrtD3UyvrIuNqp/JTQmv2JkFMBgY2AKF0UsgFG9g3pw